37852532 GSM Overview

CHAPTER 2INTRODUCTION TOMOTOROLA GSM

CHAPTER 3BSS GENERALDESCRIPTION

CHAPTER 4OMC-R OVERVIEW

CHAPTER 5BSS SOFTWARE RELEASE

FEATURES

CHAPTER 1 GSM SYSTEM MANUAL

INTRODUCTION

CHAPTER 7GLOSSARY

CHAPTER 6OMC-R SOFTWARE RELEASE

FEATURES

INDEX

SYSTEM INFORMATIONGSM OVERVIEW

GSM SOFTWARE RELEASE 6 (Horizon II)

GSR6 (Horizon II)

68P02901W01-M

SYSTEM INFORMATIONGSM OVERVIEW

GSM SOFTWARE RELEASE 6 (Horizon II)

GS

R6

(Ho

rizo

nII

)68

P02

901W

01-M

02 May 2003

System Information: GSM Overview

68P02901W01-M i

Software Release GSR6 (Horizon II)

System InformationGSM Overview

E Motorola 1993-2003All Rights ReservedPrinted in the UK.

GSR6 (Horizon II)

02 May 2003ii


68P02901W01-M

Copyrights, notices and trademarks

CopyrightsThe Motorola products described in this document may include copyrighted Motorola computerprograms stored in semiconductor memories or other media. Laws in the United States and othercountries preserve for Motorola certain exclusive rights for copyright computer programs, including theexclusive right to copy or reproduce in any form the copyright computer program. Accordingly, anycopyright Motorola computer programs contained in the Motorola products described in this documentmay 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 byimplication, estoppel or otherwise, any license under the copyrights, patents or patent applications ofMotorola, except for the rights that arise by operation of law in the sale of a product.

RestrictionsThe software described in this document is the property of Motorola. It is furnished under a licenseagreement 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 bylaw. No part of the software or documentation may be reproduced, transmitted, transcribed, storedin a retrieval system, or translated into any language or computer language, in any form or by anymeans, without prior written permission of Motorola.

AccuracyWhile reasonable efforts have been made to assure the accuracy of this document, Motorolaassumes no liability resulting from any inaccuracies or omissions in this document, or from the useof the information obtained herein. Motorola reserves the right to make changes to any productsdescribed herein to improve reliability, function, or design, and reserves the right to revise thisdocument and to make changes from time to time in content hereof with no obligation to notify anyperson of revisions or changes. Motorola does not assume any liability arising out of the applicationor use of any product or circuit described herein; neither does it convey license under its patentrights 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.

.

.

.

GSR6 (Horizon II)

02 May 2003


68P02901W01-M iii

Contents

Issue status of this manual 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General information 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reporting safety issues 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Warnings and cautions 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General warnings 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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 1�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to Motorola GSM documentation 1�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this chapter 1�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of GSM customer support manuals 1�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Documentation coding 1�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual coding system 1�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Order number 1�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Distribution of Motorola manuals 1�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating manuals 1�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering manuals 1�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Available formats 1�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Motorola manuals 1�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual types 1�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Summary of Motorola manuals 1�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service manuals - BSS 1�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service manuals - GPRS 1�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System information manuals 1�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating information manuals 1�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical description manuals 1�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation and configuration manuals 1�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance information manuals 1�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software release notes 1�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Other manuals 1�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 1�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SPARC E3000/E3500 1�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SPARCstation manuals 1�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INFORMIX manuals 1�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer manuals 1�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.25 manuals 1�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2Introduction to Motorola GSM 2�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview 2�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to GSM system information 2�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003iv


68P02901W01-M

Overview of the Motorola GSM system 2�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Motorola GSM system 2�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network element overview 2�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical GSM system 2�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Unique features of Motorola GSM 2�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the unique features of Motorola GSM 2�9 . . . . . . . . . . . . . . . . . . . . . . . Systems advantages 2�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System planning 2�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault tolerance 2�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance 2�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Future system 2�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Motorola network specifications 2�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Motorola network elements 2�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R specifications 2�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functions of the OMC-R 2�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System processor 2�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operator workstations 2�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional processors 2�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC configuration 2�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data communication 2�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver specifications 2�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmitter specifications 2�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Security management 2�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Password levels 2�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Option level 3 control 2�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Releated commands and parameters 2�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System impact 2�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile station 2�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to mobile stations 2�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile station components 2�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber Interface Module (SIM) 2�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hand portable viability 2�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment identity number 2�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber identification 2�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSM network specifications and recommendations 2�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM advantages 2�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital networks 2�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Increase capacity 2�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency reuse 2�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audio capacity 2�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link integrity 2�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber services 2�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data communications 2�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Teleservices 2�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security features 2�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSM network elements 2�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to GSM network elements 2�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network managment centre functions 2�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . National management 2�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring equipment 2�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring routes 2�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing traffic 2�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simulating the OMC-R 2�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface 2�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M v

Operations and maintenance centre 2�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the OMC 2�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile services switching centre 2�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the MSC 2�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC functions 2�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gateway MSC 2�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC flexible design 2�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interfaces 2�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A interface 2�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location register interfaces 2�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message transfer link 2�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call control 2�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Emergency calls 2�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Short message service 2�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security procedures 2�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local registration and call handover 2�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-MSC handovers 2�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment identity register 2�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Home location register 2�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HLR master database 2�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HLR data 2�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authentication centre 2�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authentication key 2�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Visitor location register 2�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling LAIs 2�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling MSRNs 2�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating handover numbers 2�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocating TMSI numbers 2�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call handling 2�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS to PSTN subscriber 2�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PSTN subscriber to MS 2�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS to MS calls 2�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base station system 2�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the BSS 2�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS configurations 2�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software functions 2�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola BSS 2�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection of MSC 2�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Speech transcoding 2�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS application part 2�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS interfaces 2�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical channels 2�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical channels 2�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical channel types 2�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control channels 2�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic channels 2�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSM subsystems (non-network elements) 2�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to GSM non- network element subsystems 2�46 . . . . . . . . . . . . . . . . . . . . Interworking function 2�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Echo canceller 2�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Billing centre 2�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell broadcast centre 2�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003vi


68P02901W01-M

GSM system features and goals 2�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to GSM system features and goals 2�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . Technological requirements 2�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM goals 2�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . European standardization 2�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standardized electrical interfaces 2�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM interfaces 2�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISDN compatibility 2�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signalling system 7 2�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hierarchical network architecture 2�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber services 2�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security 2�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handovers 2�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link integrity 2�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tracking 2�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power saving 2�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Increased capacity 2�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use of low bit rates for non-voice data 2�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lower cost infrastructure 2�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site size definitions 2�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing adjustment 2�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Echo cancellers 2�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronization 2�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Noise robustness 2�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Location Services support 2�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LCS positioning mechanisms 2�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time of arrival positioning procedure 2�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing Advance positioning (TA) 2�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E1/T1 links 2�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link types 2�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 link 2�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 link 2�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC daisy chain 2�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Standardized interfaces 2�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface types 2�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM functional layering 2�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSAP messaging 2�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISDN messaging 2�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC to MS 2�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location register interfaces 2�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC interfaces 2�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NMC interface 2�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface summary 2�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signalling links 2�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A interface 2�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abis interface 2�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Air interface 2�59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lb interface 2�60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network protocols 2�62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol types 2�62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OSI/protocol relationship 2�62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ITU-TSS signalling system 7 2�64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.25 2�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAPDm 2�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signalling link protocols 2�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M vii

GSM frequencies and channels 2�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to frequencies and channels 2�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM850 frequencies 2�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM850 channels 2�67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Primary GSM900 frequencies 2�74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Primary GSM900 channels 2�75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EGSM frequencies 2�82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EGSM channels 2�83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DCS1800 frequencies and channels 2�86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCS1800 frequencies 2�86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCS1800 channels 2�86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCS1900 frequencies and channels 2�106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCS1900 frequencies 2�106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCS1900 channels 2�106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3BSS general description 3�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview 3�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS information 3�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base station system 3�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS purpose and functions 3�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Links 3�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS network elements 3�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical BSS layout 3�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSC description 3�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC purpose and functions 3�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to MSC interaction 3�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital switching matrix 3�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terrestrial circuit device management 3�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC capacity 3�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS description 3�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS purpose and functions 3�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency reuse plan 3�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF coverage areas 3�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna systems 3�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transcoder description 3�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder purpose and functions 3�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote transcoder 3�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding location 3�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS site configuration 3�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS site configuration 3�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS configurations 3�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flexibility 3�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definitions 3�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS maximum capacity 3�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS cabinet 3�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSC cabinet 3�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS/MSC configurations 3�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS with more than one BTS 3�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flexible neighbour cell processing 3�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003viii


68P02901W01-M

Network topology 3�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic configurations 3�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Topology model 3�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Star (spoke) 3�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open-ended daisy chain 3�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daisy chain with fork and return loop to chain 3�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daisy chain with fork and return loop to BSC 3�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drop and insert BTS site configuration 3�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS standardized interfaces 3�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS standardized interfaces 3�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol layering 3�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A interface 3�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abis interface 3�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Air interface 3�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lb interface 3�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Radio system and control functions 3�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to radio system and control functions 3�21 . . . . . . . . . . . . . . . . . . . . . . . . . Handover 3�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic power control 3�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discontinuous transmission 3�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discontinuous reception 3�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing adjustment 3�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency synchronization 3�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell system radio channel reuse 3�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to cell system radio channel reuse 3�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-site reuse pattern 3�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-site 3-sector reuse pattern 3�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-site reuse pattern 3�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-site 6-sector reuse pattern 3�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-site 6-sector reuse pattern 3�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell pattern reuse comparisons 3�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS redundancy 3�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS redundancy 3�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS fault management 3�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failed modules 3�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF carrier redundancy 3�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface redundancy 3�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS redundancy 3�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC redundancy 3�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR redundancy 3�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General Packet Radio Service (GPRS) 3�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to GPRS 3�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet control unit 3�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSN complex 3�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM/GPRS network architecture 3�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet control unit 3�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the PCU 3�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU information 3�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU overview 3�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU summary 3�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU environment 3�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M ix

PCU features 3�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of PCU features 3�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Point-to-point GPRS service 3�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS radio channel allocation 3�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Medium access control mode � dynamic allocation 3�36 . . . . . . . . . . . . . . . . . . . . . . . . Support of MS classes 3�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding schemes 3�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic adaptation of coding schemes 3�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two phase packet access 3�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One phase access 3�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced one phase access 3�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency hopping of PDCH 3�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power control uplink/downlink 3�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb interface 3�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU load balancing and sharing (Gb and BTS) 3�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . MS flow control 3�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU description 3�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU purpose 3�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU management 3�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU devices and equippage 3�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU architecture 3�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to PCU architecture 3�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MPROC 3�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bridge (PPB) 3�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DPROC 3�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 PMC module 3�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chassis 3�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault tolerance 3�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU interfaces 3�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to GPRS BSS interfaces 3�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU interfaces 3�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU system and control functions 3�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System and control functions 3�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU processes 3�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4OMC-R Overview 4�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introducing the Motorola OMC-R 4�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of OMC-R 4�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming conventions 4�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication with GSM network 4�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R network management functions 4�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management 4�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm management 4�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management 4�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management 4�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load management 4�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The OMC-R in GSM network management architecture 4�7 . . . . . . . . . . . . . . . . . . . . . . . . . . Network hierarchy 4�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network levels 4�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003x


68P02901W01-M

The OMC-R system 4�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R content 4�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The system processor 4�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GUI clients and servers 4�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional processors 4�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R configuration summary 4�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable configuration details 4�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The OMC-R user interfaces 4�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User interfaces 4�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GUI interface 4�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command line interface 4�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R front panel 4�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The command line interface 4�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX-based utilities 4�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The OMC-R in a GSM network 4�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A typical GSM network 4�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R functions 4�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR functions 4�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurations 4�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS and RXCDR configuration (SITES) 4�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS configuration 4�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR configuration 4�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NE device containment 4�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Containment relationship 4�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ports 4�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site configuration 4�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CELL resources 4�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS hardware relating to traffic 4�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS software relating to traffic 4�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DRI/RTF groups - transceiving 4�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transceiving functionality 4�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of RTF 4�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy (within a cell) 4�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CELL configuration 4�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical devices 4�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover control 4�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power control 4�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Links in a GSM network: overview 4�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information on links 4�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SITE link requirements 4�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link types 4�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Physical links - PATH 4�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection 4�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical link requirements 4�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATH devices 4�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logical links 4�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to links 4�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of link 4�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements 4�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M xi

OMC-R connection to the network 4�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transferring data 4�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.21 connection configuration 4�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operations and maintenance of a BSS or RXCDR 4�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simplified network 4�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

O&M information flow between OMC-R and NEs 4�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of information flow 4�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information flow 4�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R system configuration 4�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola OMC-R 4�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical hardware configuration 4�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Communications handling 4�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications software 4�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet switch/multiplexer 4�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connections 4�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet switch 4�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

O&M network traffic capacity 4�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Peak traffic capacities 4�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R system processor 4�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the system processor 4�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System processor 4�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature description 4�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration 4�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R GSM application software: overview 4�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R processes 4�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System processor software elements 4�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UNIX: Solaris 2.5.1 operating system 4�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Platform 4�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advantages 4�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features 4�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools and applications 4�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The OMC-R database 4�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RDBMS 4�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database schema: defined 4�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database size 4�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applications and utilities 4�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The SPARCstation configuration 4�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the OMC-R GUI 4�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The network file system 4�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN configurations 4�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other configurations 4�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GUI processor 4�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server client relationship 4�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The network status summary (NSS) feature 4�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maps 4�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features 4�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The CM MIB 4�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of the CM MIB 4�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Populating the CM MIB 4�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003xii


68P02901W01-M

GUI Client - SPARCstation 5 4�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software configuration 4�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware features 4�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Night concentration 4�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How the network status summary feature works 4�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map process 4�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration data 4�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The EM proxy process 4�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GUI clients and servers: overview 4�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client/server system 4�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GUI servers and GUI clients 4�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network maps 4�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functionality 4�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Different maps available 4�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map modes 4�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm report 4�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map configuration 4�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The map display 4�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map backgrounds 4�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map links 4�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm reporting 4�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State changes 4�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information 4�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How administrative and operational state changes work 4�57 . . . . . . . . . . . . . . . . . . . . . . . . . . State changes 4�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How alarms work 4�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm icons 4�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Colours 4�59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How maps are configured 4�60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the CM MIB 4�60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two object groups 4�60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Graphic objects 4�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphic objects 4�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map 4�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MapNode 4�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MapLink 4�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration objects 4�62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration objects 4�62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware devices 4�64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software functions 4�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical links 4�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio frequency 4�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ProxyCell 4�67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UserProfile 4�67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatically created network objects 4�67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatically created map display objects 4�68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Periodic Supervision of Accessibility (PSA) 4�69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of PSA 4�69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PSA failure 4�69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M xiii

Disk usage exceeded 4�70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System processor partition full 4�70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information 4�70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DataGen 4�71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to DataGen 4�71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataGen configuration management 4�72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Off-line MIB 4�72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5BSS software release features 5�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to BSS software release features 5�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In this chapter 5�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS software release 1.1.1.0 5�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 1.1.1.0 features 5�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .









BSS software release 1.2.2.3 5�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reason for this release 5�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS software release 1.2.3.0 5�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important information 5�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 1.2.3.0 features 5�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS software release 1.3.0.x 5�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 1.3.0.x features 5�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .






GSR6 (Horizon II)

02 May 2003xiv


68P02901W01-M

BSS software release GSR2 5�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR2 features 5�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



BSS software release GSR4.1 5�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR4.1 features 5�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

BSS software release GSR5.1 5�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR5.1 features 5�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS processing of suspend message 5�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CS3, CS4 and 32 kbits/s TRAU 5�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC fast reset 5�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unequip of TCU/CTU cabinets 5�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850 MHz frequency range 5�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1900 MHz Horizonmacro 5�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single BCCH for dual band cells 5�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M xv

BSS software release GSR6 5�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR6 features 5�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Circuit Error Rate Monitor 5�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple GPRS carriers per Cell 5�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced GDP provisioning 5�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call downgrade on CIC capability mismatch 5�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS PCU recovery on last GSL failure 5�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Controlled (NC1 and NC2) cell reselection 5�54 . . . . . . . . . . . . . . . . . . . . . . . . Location services 5�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic MPROC redundancy 5�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced BSC capacity phase 2 5�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Improved MPROC software failures detection and recovery 5�58 . . . . . . . . . . . . . . . . . Inter Radio Access Technology (RAT) 2-G to 3-G handover 5�59 . . . . . . . . . . . . . . . . . Clean install (E3x00) 5�60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS interleaving TBFs 5�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link utilization improvements 5�63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced load management for EGSM carriers 5�64 . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced GPRS One Phase Access 5�64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remove support for collocated BSC 5�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compress all BTS objects at the BSC 5�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS software release GSR6 (Horizon II) 5�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR6 (Horizon II) features 5�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizon II 5�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced two uplink timeslots 5�68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removal of support for Horizonoffice 5�70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6OMC-R software release features 6�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to OMC-R software release features 6�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

In this chapter 6�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R software release 1.1.2.0 6�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration 6�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 1.1.2.0 features 6�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



OMC-R software release 1.1.2.3 6�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration 6�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 1.1.2.3 features 6�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional features 6�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




GSR6 (Horizon II)

02 May 2003xvi


68P02901W01-M

OMC-R software release 1.2.2.2 6�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 1.2.2.2 features 6�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




OMC-R software release 1.4.0.1 6�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 1.4.0.1 features 6�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further features of OMC-R software release 1.4.0.1 6�23 . . . . . . . . . . . . . . . . . . . . . . .

OMC-R software release 1.4.0.6 6�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 1.4.0.6 feature support 6�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R software release 1.4.0.7 6�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 1.4.0.7 feature support 6�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


OMC-R software release GSR2 6�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR2 features 6�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



OMC-R software release GSR4.1 6�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR4.1 features 6�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M xvii

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

OMC-R software release GSR5.1 6�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR5.1 features 6�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WebMMI 6�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CS3, CS4 and 32 kbits/s TRAU 6�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC fast reset 6�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unequip of TCU/CTU cabinets 6�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R software release GSR6 6�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR6 features 6�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Geographic command partitioning and region support 6�47 . . . . . . . . . . . . . . . . . . . . . . Enhanced circuit error rate monitor 6�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R GUI usability for large network support 6�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable cyclic neighbour statistics 6�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online network expansion - phase 3 6�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Xchange 6�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003xviii


68P02901W01-M

OMC-R software release GSR6 (Horizon II) 6�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR6 (Horizon II) features 6�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support for new UNIX server 6�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7Glossary of technical terms 7�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary of technical terms 7�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A Interface - AUTO 7�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B Interface - Byte 7�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C - CW 7�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D Interface - DYNET 7�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E - EXEC 7�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F Interface - Full Rate 7�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G Interface - GWY 7�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H Interface - Hyperframe 7�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I - IWU 7�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . k - KW 7�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . L1 - LV 7�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M - MUX 7�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NACK - nW 7�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O - Overlap 7�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PA - PXPDN 7�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QA- Quiesent mode 7�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R - RXU 7�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S7- SYSGEN 7�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T -TxBPF 7�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . U - UUS 7�70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V - VTX host 7�71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W - WWW 7�73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X - X Window 7�74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZC 7�74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index I�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M xix

List of Figures

Figure 2-1 GSM and GPRS Architecuture (GSN Complex) 2�7 . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-2 Typical GSM system layout � Dual BSS system 2�8 . . . . . . . . . . . . . . . . . . . . . .

Figure 2-3 Four cell frequency reuse pattern 2�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-4 A interface protocols 2�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-5 Handover control 2�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-6 Database list summary 2�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-7 HLR configuration 2�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-8 Authentification centre configuration 2�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-9 Visitor location register configuration 2�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-10 MS to PSTN subscriber call 2�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-11 PSTN subscriber to MS call 2�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-12 MS to MS call (same PLMN) 2�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-13 MS to MS call (different PLMN) 2�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-14 MS to MS call (different PLMN/different country) 2�41 . . . . . . . . . . . . . . . . . . . . .

Figure 2-15 BSS configuration examples 2�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-16 GSM functional layering 2�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-17 GSM interface summary 2�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-18 OSI layers � main protocol relationships 2�62 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-19 Network protocols 2�63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-20 GSM850 frequency range 2�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-21 GSM900 frequency range 2�74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-22 EGSM frequency range 2�82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-23 DCS1800 frequency range 2�86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-24 PCS1900 frequency range 2�106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-1 Dual BSS system 3�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-2 Multiple BTS sites per BSS 3�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-3 Topology model 3�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-4 Handover measurements 3�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-5 9-site reuse pattern cellular system 3�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-6 3-site (sectored) cellular system 3�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-7 The GPRS network 3�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-8 GPRS network architecture showing the PCU and GSN complex 3�31 . . . . . . .

Figure 3-9 PCU within the GSM/GPRS network 3�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-10 PCU managed from the OMC-R 3�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-11 Device and equipment hierarchy for the PCU device 3�43 . . . . . . . . . . . . . . . . . .

Figure 3-12 BSS functional blocks 3�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-13 Data and signalling paths between the PCU and MS 3�48 . . . . . . . . . . . . . . . . .

Figure 3-14 PCU to BSC connection utilizing E1 links (four shown) 3�49 . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003xx


68P02901W01-M

Figure 3-15 Data and signalling paths between the PCU and SGSN 3�49 . . . . . . . . . . . . . . .

Figure 4-1 The OMC-R in a GSM system 4�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-2 GSM network management architecture 4�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-3 Typical scaleable OMC-R system configuration 4�9 . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-4 The OMC-R GUI front panel 4�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-5 The Expert OMC-R GUI Front Panel 4�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-6 The OMC-R in a GSM network 4�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-7 The naming convention and physical links of BSS 4�17 . . . . . . . . . . . . . . . . . . . . .

Figure 4-8 Site configuration 4�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-9 Example of path settings within a BSS 4�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-10 The different logical links in a GSM network 4�26 . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-11 Communication between the OMC-R and other network elements 4�28 . . . . . .

Figure 4-12 Simplified GSM network showing devices and links at BSSs 4�29 . . . . . . . . . . .

Figure 4-13 Information flow between the OMC-R and BSSs 4�30 . . . . . . . . . . . . . . . . . . . . .

Figure 4-14 An example Motorola OMC-R system configuration 4�31 . . . . . . . . . . . . . . . . . .

Figure 4-15 Example Packet switch / multiplexer connections 4�33 . . . . . . . . . . . . . . . . . . . .

Figure 4-16 Scaleable OMC-R - high-end system processor 4�35 . . . . . . . . . . . . . . . . . . . . .

Figure 4-17 System processor software configuration 4�37 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-18 OMC-R GSM (System processor) software components 4�38 . . . . . . . . . . . . . .

Figure 4-19 OMC-R database - database schema breakdown 4�41 . . . . . . . . . . . . . . . . . . . .

Figure 4-20 OMC-R SPARCstation configuration 4�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-21 Maps icon 4�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-22 The network status summary options on the GUI front panel 4�46 . . . . . . . . . .

Figure 4-23 SPARCstation 5/IPX hardware and software configuration 4�48 . . . . . . . . . . . .

Figure 4-24 Night concentration configuration 4�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-25 Map processes 4�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-26 Map icons 4�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-27 State changes on the map 4�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-28 Alarms and how they change on the map 4�58 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-29 The CM MIB showing the different groups of managed objects 4�60 . . . . . . . .

Figure 4-30 The containment relationship for the graphic objects 4�61 . . . . . . . . . . . . . . . . .

Figure 4-31 The containment relationship for the configuration objects 4�62 . . . . . . . . . . . . .

Figure 4-32 DataGen in a GSM environment. 4�71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-33 DataGen main window 4�72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-34 Off-line MIB front panel 4�72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-1 Example of Interleaving DL TBFs 5�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-2 Multi-slot class 6 uplink/downlink bias timeslot allocation 5�69 . . . . . . . . . . . . . . .

Figure 5-3 Multi-slot class 10 uplink/downlink bias timeslot allocation 5�69 . . . . . . . . . . . . . .

Figure 6-1 GSM OMC-R hardware configuration for up to 45k TCH 6�53 . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M xxi

Figure 6-2 GSM OMC-R hardware configuration for up to 60k TCH 6�54 . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003xxii


68P02901W01-M

List of Tables

Table 1-1 Typical manual history 1�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 1-2 Types of Motorola manuals 1�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-1 OMC-R functions and GSM & ITU-TSS references 2�11 . . . . . . . . . . . . . . . . . . . . .

Table 2-2 OMC configurations (maximum values) 2�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-3 OMC-R/X.25 capacities 2�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-4 Receiver specifications 2�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-5 Transmitter specifications 2�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-6 BSS software function 2�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-7 Network element signalling links 2�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-8 GSM Frequency types 2�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-9 GSM850 channels 128 to 130 2�67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-10 GSM850 channels 131 to 140 2�67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .












Table 2-22 PGSM channels 1 to 10 2�75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-23 PGSM channels 11 to 20 2�75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .








Table 2-31 PGSM channels 91 to 100 2�79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-32 PGSM channels 101 to 110 2�80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



Table 2-35 EGSM channels 975 to 984 2�83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-36 EGSM channels 985 to 994 2�83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M xxiii

Table 2-37 EGSM channels 995 to 1004 2�84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-38 EGSM channels 1005 to 1014 2�84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-39 EGSM channels 1015 to 0 2�85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-40 DCS 1800 channels 512 to 520 2�86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .










Table 2-50 DCS 1800 channels 611 to 620 2�91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


























GSR6 (Horizon II)

02 May 2003xxiv


68P02901W01-M



Table 2-78 PCS 1900 channels 512 to 520 2�106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .






















Table 2-100 PCS 1900 channels 731 to 740 2�117 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .








Table 3-1 BSC maximum capacities 3�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-2 BTS - BSC main and alternate paths (fork with return loop) 3�17 . . . . . . . . . . . . .

Table 3-3 BTS - BSC main and alternate paths (chain with return loop) 3�17 . . . . . . . . . . . .

Table 3-4 Sector re-use pattern features 3�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-5 Failed module situations 3�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-6 Cell reselection modes 3�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-7 MS multi-slot class mapping for all GPRS multi-slot classes 3�37 . . . . . . . . . . . . .

GSR6 (Horizon II)

02 May 2003


68P02901W01-M xxv

Table 3-8 GPRS coding scheme characteristics 3�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4-1 Front panel icon description 4�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4-2 Scaleable OMC-R configurations (maximum values) 4�36 . . . . . . . . . . . . . . . . . . .

Table 4-3 GUI processor hardware specifications 4�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4-4 GUI processor software specifications 4�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4-5 Alarm icon colours 4�59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-1 Release 1.1.1.0 features 5�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-2 Software release 1.1.2.0 features 5�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .








Table 5-10 Release 1.2.3.0 features 5�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-11 Release 1.3.0.x features 5�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Table 5-13 Release1.4.0.1 features 5�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




Table 5-17 Release GSR2 features 5�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



Table 5-20 Release GSR4.1 features 5�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




Table 5-24 Multiple GPRS carriers configured for performance (Default) 5�49 . . . . . . . . . . .

Table 5-25 Operator specified options 5�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-26 Cell reselection modes 5�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-27 Release GSR6 (Horizon II) features 5�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-28 CTU and CTU2 output power capabilities 5�67 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-29 MS multi-slot class mapping for all GPRS multi-slot classes 5�68 . . . . . . . . . . . .





GSR6 (Horizon II)

02 May 2003xxvi


68P02901W01-M

Table 6-5 Release1.2.2.2 features 6�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .













Table 6-18 Release GSR6 (Horizon II) features 6�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II) Issue status of this manual

02 May 2003


68P02901W01-M 1

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:

Manualissue

Date ofissue

Remarks

O 03 Oct 1994 Issue O Original issue - Software release 1.2.2.x

A 30 Dec 1994 Issue A Software release 1.2.3.x

B 10 Sep 1995 Issue B Software release 1.3.0.x

C 31 May 1996 Issue C Software release 1.4.0.x

D 28 Mar 1997 Issue D Software release 1.4.1.x

E 29 Aug 1997 Issue E GSM Software Release 2

F 27 Apr 1998 Issue F GSM Software Release 3

G 12 Mar 1999 Issue G GSM Software Release 4

H 14 Jul 2000 Issue H GSM Software Release 4.1

J 31 Jul 2001 Issue J GSM Software Release 5

K 31 May 2002 Issue K GSM Software Release 5.1

L 30 Nov 2002 Issue L GSM Software Release 6

M 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:

ServiceRequest

GMRNumber

Remarks

N/A N/A

GSR6 (Horizon II)General information

02 May 20032


68P02901W01-M

General information

Important notice

If this manual was obtained when attending a Motorola training course, it will not beupdated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If itwas supplied under normal operational circumstances, to support a major softwarerelease, then corrections will be supplied automatically by Motorola in the form ofGeneral Manual Revisions (GMRs).

Purpose

Motorola cellular communications manuals are intended to instruct and assist personnelin the operation, installation and maintenance of the Motorola cellular infrastructureequipment and ancillary devices. It is recommended that all personnel engaged in suchactivities be properly trained by Motorola.

WARNING Failure to comply with Motorola�s operation, installation andmaintenance instructions may, in exceptional circumstances,lead to serious injury or death.

These manuals are not intended to replace the system and equipment training offered byMotorola, although they can be used to supplement and enhance the knowledge gainedthrough 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) asimplemented by Motorola, and includes:

S Chapter 1, Introduction to GSM system information.

S Chapter 2, Introduction to Motorola GSM.

S Chapter 3, BSS general information.

S Chapter 4, OMC-R overview.

S Chapter 5, BSS software release features.

S Chapter 6, OMC-R software release features.

S Chapter 7, Glossary of terms, acronyms and abbreviations.

S Index

The information is intended for use by GSM operations and maintenance staff.

GSR6 (Horizon II) General information

02 May 2003


68P02901W01-M 3

Cross references

Throughout this manual, cross references are made to the chapter numbers and sectionnames. The section name cross references are printed bold in text.

This manual is divided into uniquely identified and numbered chapters that, in turn, aredivided into sections. Sections are not numbered, but are individually named at the top ofeach page, and are listed in the table of contents.

Text conventions

The following conventions are used in the Motorola cellular infrastructure manuals torepresent 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, andenvironmental variables that appear on the screen are shown likethis.

Special key sequences

Special key sequences are represented as follows:

CTRL�c Press the Control and c keys at the same time.

ALT�f 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 isidentified by the ↵ symbol on both the PC and the Sunkeyboards. The keyboard Return key may also be identifiedby the word Return.

GSR6 (Horizon II)General information

02 May 20034


68P02901W01-M

Feature references

Throughout this manual new and amended features are tagged to help users to assessthe impact on installed networks. The tags are the appropriate Motorola RoadmapDataBase (RDB) numbers. The tags include index references which are listed in themanual Index. The Index includes the entry feature which is followed by a list of the RDBnumbers 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:

New and amended feature information Tag position in text

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

S Full paragraphs under subheadings

Immediately after the headings as follows:

S Main heading

S Subheading

New or amended complete Figures andTables

After the Figure or Table number andbefore the title text.

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

General command syntax, operator inputor displays (in special fonts).

On a separate line immediately above theaffected item.

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

GSR6 (Horizon II) Reporting safety issues

02 May 2003


68P02901W01-M 5

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 awritten report by fax, Swindon +44 (0)1793 430987 or China +86 1068423633 (fax).

4. Collect evidence from the equipment under the guidance of the Customer NetworkResolution Centre.

GSR6 (Horizon II)Warnings and cautions

02 May 20036


68P02901W01-M

Warnings and cautions

Introduction

The following describes how warnings and cautions are used in this manual and in allmanuals 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, forexample, 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/outconnectors. Laser radiation can come from either the data in/outconnectors or unterminated fibre optic cables connected to datain/out connectors.

Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of theequipment described in the Motorola manuals. Failure to comply with these warnings,or with specific warnings elsewhere in the Motorola manuals, or on the equipmentitself, violates safety standards of design, manufacture and intended use of theequipment. Motorola assumes no liability for the customer�s failure to complywith these requirements.

Cautions

Definition of Caution

A caution means that there is a possibility of damage to systems, software or individualitems 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.

GSR6 (Horizon II) General warnings

02 May 2003


68P02901W01-M 7

General warnings

Introduction

Observe the following specific warnings during all phases of operation, installation andmaintenance of the equipment described in the Motorola manuals:

S Potentially hazardous voltage

S Electric shock

S RF radiation

S Laser radiation

S Heavy equipment

S Parts substitution

S Battery supplies

S Lithium batteries

Failure to comply with these warnings, or with specific warnings elsewhere in theMotorola manuals, violates safety standards of design, manufacture and intended use ofthe equipment. Motorola assumes no liability for the customer�s failure to comply withthese 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 warninglabels fitted to the equipment. Warning labels must not be removed, painted over orobscured in any way.

GSR6 (Horizon II)General warnings

02 May 20038


68P02901W01-M

Specific warnings

Specific warnings used throughout the GSM manual set are shown below, and will beincorporated 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 Vac single phase or 415 V ac three phase supply. To achieveisolation of the equipment from the ac supply, the ac inputisolator must be set to off and locked.

When working with electrical equipment, reference must be made to the Electricity atWork Regulations 1989 (UK), or to the relevant electricity at work legislation for thecountry in which the equipment is used.

NOTE Motorola GSM equipment does not utilise high voltages.

Electric shock

WARNING Do not touch the victim with your bare hands until theelectric circuit is broken.Switch off. If this is not possible, protect yourself with dryinsulating material and pull or push the victim clear of theconductor.ALWAYS send for trained first aid or medical assistanceIMMEDIATELY.

In cases of low voltage electric shock (including public supply voltages), serious injuriesand even death, may result. Direct electrical contact can stun a casualty causingbreathing, and even the heart, to stop. It can also cause skin burns at the points of entryand 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 inthis equipment when in operation. Ensure that alltransmitters are switched off when any antenna connectionshave to be changed. Do not key transmitters connected tounterminated cavities or feeders.

Relevant standards (USA and EC), to which regard should be paid when working with RFequipment are:

S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to HumanExposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.

S CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields HighFrequency (10 kHz to 300 GHz).

GSR6 (Horizon II) General warnings

02 May 2003


68P02901W01-M 9

Laser radiation

WARNING Do not look directly into fibre optic cables or optical datain/out connectors. Laser radiation can come from either thedata in/out connectors or unterminated fibre optic cablesconnected to data in/out connectors.

Lifting equipment

WARNING When dismantling heavy assemblies, or removing orreplacing equipment, a competent responsible person mustensure that adequate lifting facilities are available. Whereprovided, lifting frames must be used for these operations.

When dismantling heavy assemblies, or removing or replacing equipment, the competentresponsible person must ensure that adequate lifting facilities are available. Whereprovided, lifting frames must be used for these operations. When equipments have to bemanhandled, reference must be made to the Manual Handling of Loads Regulations1992 (UK) or to the relevant manual handling of loads legislation for the country in whichthe equipment is used.

Parts substitution

WARNING Do not install substitute parts or perform any unauthorizedmodification of equipment, because of the danger ofintroducing additional hazards. Contact Motorola if in doubtto ensure that safety features are maintained.

Battery supplies

WARNING Do not wear earth straps when working with standby batterysupplies.

Lithium batteries

WARNING Lithium batteries, if subjected to mistreatment, may burstand ignite. Defective lithium batteries must not be removedor replaced. Any boards containing defective lithiumbatteries must be returned to Motorola for repair.

Contact your local Motorola office for how to return defective lithium batteries.

GSR6 (Horizon II)General cautions

02 May 200310


68P02901W01-M

General cautions

Introduction

Observe the following cautions during operation, installation and maintenance of theequipment described in the Motorola manuals. Failure to comply with these cautions orwith specific cautions elsewhere in the Motorola manuals may result in damage to theequipment. Motorola assumes no liability for the customer�s failure to comply with theserequirements.

Caution labels

Personnel working with or operating Motorola equipment must comply with any cautionlabels fitted to the equipment. Caution labels must not be removed, painted over orobscured in any way.

Specific cautions

Cautions particularly applicable to the equipment are positioned within the text of thismanual. These must be observed by all personnel at all times when working with theequipment, as must any other cautions given in text, on the illustrations and on theequipment.

Fibre optics

CAUTION Fibre optic cables must not be bent in a radius of less than30 mm.

Static discharge

CAUTION Motorola equipment contains CMOS devices. These metaloxide semiconductor (MOS) devices are susceptible todamage from electrostatic charge. See the section Devicessensitive to static in the preface of this manual for furtherinformation.

GSR6 (Horizon II) Devices sensitive to static

02 May 2003


68P02901W01-M 11

Devices sensitive to static

Introduction

Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer ofinsulation that is susceptible to damage from electrostatic charge. Such a charge appliedto the leads of the device could cause irreparable damage.

These charges can be built up on nylon overalls, by friction, by pushing the hands intohigh insulation packing material or by use of unearthed soldering irons.

MOS devices are normally despatched from the manufacturers with the leads shortedtogether, for example, by metal foil eyelets, wire strapping, or by inserting the leads intoconductive 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 followingprecautions when handling the replacement:

S Always wear an earth strap which must be connected to the electrostatic point(ESP) on the equipment.

S Leave the short circuit on the leads until the last moment. It may be necessary toreplace the conductive foam by a piece of wire to enable the device to be fitted.

S Do not wear outer clothing made of nylon or similar man made material. A cottonoverall is preferable.

S If possible work on an earthed metal surface or anti-static mat. Wipe insulatedplastic work surfaces with an anti-static cloth before starting the operation.

S All metal tools should be used and when not in use they should be placed on anearthed surface.

S Take care when removing components connected to electrostatic sensitivedevices. These components may be providing protection to the device.

When mounted onto printed circuit boards (PCBs), MOS devices are normally lesssusceptible to electrostatic damage. However PCBs should be handled with care,preferably by their edges and not by their tracks and pins, they should be transferreddirectly from their packing to the equipment (or the other way around) and never leftexposed on the workbench.

GSR6 (Horizon II)Motorola manual set

02 May 200312


68P02901W01-M

Motorola manual set

Introduction

The following manuals provide the information needed to operate, install and maintain theMotorola equipment. CD-ROMs are available, with full navigation, for GSM, and GPRSmanual sets.Each CD-ROM includes all manuals related to a specified main GSM or GPRS softwarerelease, together with current versions of appropriate hardware manuals. A snapshotcopy of online documentation is also included, though it will not be updated in line withsubsequent point releases.The CD-ROM does not include Release Notes or documentation supporting specialistproducts such as MARS or COP.

Generic GSM manuals

The following are the generic manuals in the GSM manual set, these manuals arerelease dependent:

Identification/Order number Name

68P02901W01 System Information: GSM Overview68P02901W14 * Operating Information: GSM System Operation68P02901W19 Operating Information: OMC-R System Administration68P02901W34** Technical Description: OMC-R Database Schema68P02901W36 Technical Description: BSS Implementation68P02901W23 Technical Description: BSS Command Reference68P02901W17 Installation & Configuration: GSM System Configuration68P02901W43 Installation & Configuration: BSS Optimization68P02901W47 Installation & Configuration: OMC-R Clean Install68P02901W26 Maintenance Information: Alarm Handling at the OMC-R68P02901W58 Maintenance Information: BSS Timers68P02901W57 Maintenance Information: Device State Transitions68P02901W51 Maintenance Information: BSS Field Troubleshooting68P02901W56 Maintenance Information: GSM Statistics Application68P02901W72 Software Release Notes: BSS/RXCDR68P02901W74 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.

GSR6 (Horizon II) Motorola manual set

02 May 2003


68P02901W01-M 13

Related GSM manuals

The following are related Motorola GSM manuals:


68P02900W21 System Information: BSS Equipment Planning68P02900W22 System Information: DataGen68P02900W76 Software Release Notes: DataGen68P02900W25 System Information: GSM Advance Operational Impact68P02900W36 System Information: Network Health Analyst68P02900W77 Software Release Notes: Network Health Analyst68P02900W90 System Information: Cell Optimization (COP)68P02900W94 System Information: Motorola Analysis and Reporting System

(MARS)68P02900W69 Software Release Notes: Cell Optimization (COP)68P02900W68 Software Release Notes: Motorola Analysis and Reporting System

(MARS)68P02901W10 Operating Information: OMC-R System Administration (OSI)68P02901W39 Installation & Configuration: OSI Clean Install68P02901W70 Software Release Notes: OMC-R OSI System

Generic GPRS manuals

The following are the generic manuals in the GPRS manual set, these manuals arerelease dependent:


68P02903W01 System Information: GPRS Overview68P02903W03 Operating Information: OMC-G System Administration68P02903W37 Operating Information: GSN System Administration68P02903W46 Technical Description: OMC-G Database Schema68P02903W18 * Technical Description: GSN Command Reference68P02903W47 Installation & Configuration: GSN Clean Install68P02903W04 Installation & Configuration: OMC-G Clean Install68P02903W19 * Maintenance Information: Alarm Handling at the OMC-G68P02903W20 Maintenance Information: GSN Statistics Application68P02903W76 Software Release Notes: GSN System68P02903W70 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:


68P02903W02 System Information: GPRS Equipment Planning68P02903W38 System Information: GSN Advance Operational Impact

GSR6 (Horizon II)Motorola manual set

02 May 200314


68P02901W01-M

BSS service manuals

The following are the Motorola Base Station Subsystem service manuals, these manualsare not release dependent. The internal organization and makeup of service manual setsmay vary, they may consist of from one to four separate manuals, but they can all beordered using the overall catalogue number shown below:


68P02901W37 Service Manual: BTS68P02901W38 Service Manual: BSC/RXCDR68P02901W75 Service Manual: M-Cell268P02901W85 Service Manual: M-Cell668P02901W95 Service Manual: M-Cellcity and M-Cellcity+68P02901W65 Service Manual: M-Cellaccess68P02901W90 Service Manual: M-Cellmicro68P02902W36 Service Manual: Horizonmicro68P02902W15 Service Manual: Horizoncompact68P02902W06 Service Manual: Horizonmacro Indoor68P02902W12 Service Manual: Horizonmacro Outdoor68P02902W61 Service Manual: Horizonmicro2 Horizoncompact268P02902W66 Service Manual: Horizonmacro 12 Carrier Outdoor68P02902W96 Service Manual:Horizon II macro68P02902W97 Installation & Configuration: Horizon II macro

GPRS service manuals

The following are the Motorola GPRS service manuals, these manuals include thePacket Control Unit (PCU) service manual which becomes part of the BSS for GPRS:


68P02903W05 Service Manual: GPRS Support Node (GSN)68P02903W07 Installation & Configuration: GSN (legacy cabinets)68P02903W23 Installation & Configuration: GSN (common data cabinets)68P02903W10 Service Manual: Packet Control Unit (PCU)68P02903W12 Installation & Configuration: PCU (legacy cabinets)68P02903W24 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 orRepresentative. Manuals are ordered using the order (catalogue) number.

Manuals are available on the following media:

Printed hard copy

Electronic:

S On the Motorola service web.

S CD-ROM library produced in support of a major system software release.

GSR6 (Horizon II) GMR amendment

02 May 2003


68P02901W01-M 15

GMR amendment

Introduction to GMRs

Changes to a manual that occur after the printing date are incorporated into the manualusing General Manual Revisions (GMRs). GMRs are issued to correct Motorola manualsas and when required. A GMR has the same identity as the target manual. Each GMR isidentified 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 withamendment list.

� Remove and replace pages in this manual, as detailed on the GMRinstruction sheet.

S Motorola service web - Updated at the same time as hard copies.

S CD-ROM - Updated periodically as required.

GSR6 (Horizon II)GMR amendment record

02 May 200316


68P02901W01-M

GMR amendment record

GMR instructions

When a GMR is inserted in this manual, the amendment record below is completed torecord the GMR. Retain the instruction sheet that accompanies each GMR and insert itin 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 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 . .

02 May 2003


68P02901W01-M 1�1

Chapter 1

GSM system manual introduction

GSR6 (Horizon II)

02 May 20031�2


68P02901W01-M

GSR6 (Horizon II) Introduction to Motorola GSM documentation

02 May 2003


68P02901W01-M 1�3

Introduction to Motorola GSM documentation

About this chapter

This chapter contains listings of Motorola GSM manuals supplied to customers. Thechapter also includes a description of the Motorola documentation system and includes abrief summary of the contents of each manual. Other documents available to Motorolacustomers are also listed.

Overview of GSM customer support manuals

This manual is a guide to the Motorola GSM manuals customer support manuals, itdescribes how the manuals are referenced, what manuals are available and how toobtain them.

The Motorola system and hardware product manuals provide the required information fora customer to manage, operate and maintain the GSM system, as implemented byMotorola.

Further details of the Motorola GSM customer support manuals are provided in thefollowing sections:

S Documentation coding.

S Distribution of Motorola manuals.

S Overview of Motorola manuals.

S Summary of Motorola manuals.

S Other manuals.

GSR6 (Horizon II)Documentation coding

02 May 20031�4


68P02901W01-M

Documentation coding

Manual coding system

All manuals have a 68P... catalogue number which is a unique identifier, used forordering purposes.

Order number

The order number is an eleven character Motorola code, that starts with 68P... fortechnical manuals. It is the part number used when ordering Motorola hardcopymanuals. An additional suffix letter indicates the issue status of the manual. Note thatthis starts at O for original then A, B, C and so on. For software dependent manuals, theissue 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 containcumulative release information that is backward compatible, or cover more than onerelease. 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 theidentifying 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 Software Release 1.2.3.x

68P02900W15-B 01 Sep 1995 Software Release 1.3.0.x

68P02900W15-C 31 May 1996 Software Release 1.4.0.x

68P02900W15-D 17 Dec 1996 Software Release 1.4.1.x

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:

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 ofnumbers, which are in effect unique identity numbers.

3. The final letter is the issue suffix as described above.

GSR6 (Horizon II) Distribution of Motorola manuals

02 May 2003


68P02901W01-M 1�5

Distribution of Motorola manuals

Updating manuals

Up-issuing a manual

For each new major software release, affected release dependent manuals are revisedand re-issued. When this happens, the issue suffix letter of the Order numberincrements by one letter of the alphabet, for example, release GSR3 manuals have thesuffix -F and release GSR4 manuals have the suffix -G.

Other manuals, such as hardware service manuals, are up-issued as and when requiredand do not follow the above suffix letter rules, but are sequentially lettered from O forOriginal, followed by A, B and so on.

General Manual Revisions (GMRs)

GMRs are produced to update and correct manuals when required between majorreleases. A GMR may be produced for release dependent manuals when a softwarepoint release is issued. For all manuals, GMRs are produced to incorporate minortechnical changes and to correct any errors. An updated version of the documentationCD-ROM is produced when the GMRs are incorporated in the manuals.

Motorola Order Fulfilment maintain a database of customers. Any customer who hasordered manuals for a particular release will be supplied automatically with GMRs, asand when they are produced. Similarly, any customer who has ordered a documentationCD-ROM for a particular software load will be supplied automatically with the GMRversion of that CD-ROM.

Where a documentation CD-ROM is supplied free of charge, as part of the software loadpackage, an updated CD-ROM will be supplied, when available, by Motorola ControlledRoll Out (CRO) Group.

Ordering manuals Motorola manuals for customers must be ordered through the Motorola Local Office orRepresentative. Manuals are ordered using the Order number. Remember to specifythe manual issue required by quoting the correct suffix letter, which relates to thesoftware load supported.

Available formatsMotorola manuals are available in the following formats:

S Hardcopy

Motorola manuals are available in A4 and A5 paper sizes, also some manuals areavailable in Wire bound.

S CD-ROM

A CD-ROM containing all the GSM manuals. The data is structured in a navigablePortable Document Format (PDF) to facilitate ease of search and location ofspecific blocks of information.

S Extranet

This facility offers direct online accessibility of Motorola manuals. The dataavailable is the same structured PDFs which are available on the CD-ROM

GSR6 (Horizon II)Overview of Motorola manuals

02 May 20031�6


68P02901W01-M

Overview of Motorola manuals

A further listing of the Motorola manuals showing the various catagories can be found inthe 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 Description

Service 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 toperform:

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.

GSR6 (Horizon II) Overview of Motorola manuals

02 May 2003


68P02901W01-M 1�7

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

GSR6 (Horizon II)Summary of Motorola manuals

02 May 20031�8


68P02901W01-M

Summary of Motorola manualsThese 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 stationequipments BTS4, BTS5, and BTS6. It consists of one loose leaf binder containing thefollowing:

S 68P02901W02 General Information.

S 68P02901W03 Technical Description.

S 68P02901W04 Installation and Configuration.

S 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 bindercontaining the following:






The manual contains hardware service information for the base station controller 2(BSC2) and remote transcoder 2 (RXCDR 2) equipment, comprising the following.





The manual contains hardware installation and configuration information for the GPRSbase 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 containsthe following:





GSR6 (Horizon II) Summary of Motorola manuals

02 May 2003


68P02901W01-M 1�9

68P02901W85 M-Cell6

The Service Manual contains details of the M-Cell6 base station equipment. It containsthe following:





68P02901W95 M-Cellcity and M-Cellcity+

The Service Manual contains details of the M-Cellcity and M-Cellcity+ micro GSM basestation equipment. It comprises one binder containing the following:





68P02901W65 M-Cellaccess

The manual contains hardware service information for the M-Cellaccess GSM basetransceiver station equipment. It comprises one loose leaf binder containing thefollowing:




S 68P02901W69 Parts Information.

68P02901W90: M-Cellmicro Documentation Set

The documentation set contains details of the M-Cellmicro base station equipment. It isnot a single manual, but comprises three loose leaf binders (each of which may beordered separately) containing the following:


S 68P02901W93 Installation and Commissioning.


68P02902W36 Horizonmicro

The Service Manual contains details of the Horizonmicro (formerly M-Cellarena) GSMbase transceiver station equipment. It comprises one binder containing the following:






02 May 20031�10


68P02901W01-M

68P02902W15 Horizoncompact

The Service Manual contains details of the Horizoncompact (formerly M-Cellarenamacro)and RF Booster, which together form a macro GSM transceiver base station equipment.It comprises one binder containing the following:





68P02902W06 Horizonmacro Indoor

The Service Manual contains details of the six carrier Horizonmacro indoor BTSequipment. It comprises one binder containing the following:





68P02902W12 Horizonmacro Outdoor

The Service Manual contains details of the six carrier Horizonmacro outdoor BTSequipment. It comprises one binder containing the following:





68P02902W61 Horizonmicro2 and Horizoncompact2

The Service Manual contains details of the Horizonmicro2 and Horizoncompact2 basetransceiver station equipment. It comprises one binder containing the following:





68P02902W66 Horizonmacro 12 Carrier Outdoor

The Service Manual contains details of the Horizonmacro 12 Carrier Outdoor basetransceiver station, which is an outdoor enclosure into which one or two standard sixcarrier Horizonmacro indoor cabinets are fitted. It comprises one binder containing thefollowing:






02 May 2003


68P02901W01-M 1�11

68P02902W96 Horizon II macroThe Service Manual contains details of the Horizon II macro base transceiver station,comprising the following information.

S Technical Description.

S Maintenance Information.

S Parts Information.

68P02902W97 Horizon II macroThe Service Manual contains installation and configuration details for theHorizon 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 theOMC-G. It comprises one binder containing the following:





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 theOMC-G. It comprises one binder containing the following:




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

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

68P02903W10-A Packet Control Unit (PCU)The Service Manual contains hardware service information for the GPRS packet controlunit (PCU). The PCU is connected to the BSS and is controlled from the OMC-R. Itcomprises one binder containing the following:






02 May 20031�12


68P02901W01-M

68P02903W10-B Packet Control Unit (PCU)The Service Manual contains hardware service information for the GPRS packet controlunit (PCU). The PCU is connected to the BSS and is controlled from the OMC-R. Themanual comprises one binder containing the following:




68P02903W12-B Packet Control Unit (PCU)The Service Manual contains legacy installation and configuration information for theGPRS packet control unit (PCU). The PCU is connected to the BSS and is controlledfrom the OMC-R.

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

System information manuals

68P02900W21 BSS Equipment PlanningThe manual contains information about planning a GSM network using Motorolaequipment. The manual includes all the M-Cell planning information from 68P02900W31,which is now discontinued.

68P02900W22: DataGenThe manual contains information on how to install and use DataGen. It also containsdetails of the offline MIB.

68P02900W25 Advance Operational ImpactThe manual provides a single source of information on the impact of a new GSMsoftware load. The purpose of the manual is two-fold:

S It provides advance information on a per feature basis for planning purposes.

S It provides a library of feature specific information for reference purposes.

The manual is available some time before the general availability of the featuresdescribed.

68P02900W36 Network Health AnalystThe manual outlines the Network Health Analyst (NHA) staging procedures and thecustomer site installation procedures. The procedures consist of preparation of thehardware platform, interconnection of the processor via ethernet, loading andconfiguration of the system software. Details of the site requirements, on site installationprocedures, system start-up procedures and system backup and recovery proceduresare included.

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


02 May 2003


68P02901W01-M 1�13

Operating information manuals

68P02901W10 OMC-R System Administration (OSI)

The manual provides information on procedures required to perform managementfunctions on the Motorola OSI. The OSI feature is an option of the OMC-R. The OSIProcessor is added to the OMC network configuration and hosts most of the processesof the OSI feature. The OSI feature contains the Mediation Device (MD) application andthe optional Security Application (SA).

68P02901W14 GSM System Operation

The manual contains the information required for a GSM operator to perform the generalprocedures required for the day-to-day operation of the network at the MotorolaOperation and Maintenance Centre � Radio (OMC-R).

NOTE Only available as part of the OMC-R on-line help information.

68P02901W19 OMC-R System Administration

The manual provides information on procedures required to perform managementfunctions on the Motorola Operation and Maintenance Centre � Radio (OMC-R).Procedures to manage the OMC-R system, the users, the database, X.25 and performtroubleshooting are described.

Technical description manuals

68P02901W23 BSS Command Reference

The manual contains descriptions of the BSS MMI commands and parameters usedwithin the Motorola GSM system.

68P02901W34 OMC-R Database Schema

The manual is a technical reference to support the procedures provided in the GSMOperation and Administration manuals. It contains a complete description of the OMCdatabase 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 thatare controlled by the BSS. Information is provided on implementation and equippage ofthe devices, functions and links required to facilitate BSS operation.


02 May 20031�14


68P02901W01-M

Installation and configuration manuals

68P02901W17 GSM System ConfigurationThe manual provides information on procedures to configure the Motorola GSM NetworkElements (NEs) and thus populate the Configuration Management database.

68P02901W39 OSI Clean Install

The manual describes the staging and on site procedures for the installation andconfiguration of the optional OSI Processor at the OMC-R. The procedures consist ofthe preparation of the hardware, and the loading and configuration of the systemsoftware. It also describes the installation, configuration and start-up of the OSIProcessor specific software.

68P02901W43 BSS Optimization

The manual contains configuration and optimization information for the BSSC and thevarious BTS cabinets in Motorola GSM, EGSM, DCS1800 and PCS 1900 systems. Themanual contains details of the optimization and base site integration.

68P02901W47 Scaleable OMC-R Clean InstallThe manual outlines the Scaleable OMC system staging procedures and the customersite installation procedures. The staging procedures consist of preparation of thehardware platform, interconnection of the processors and printer via ethernet, andloading and configuration of the system software. Details of the site requirements, onsite installation procedures, system start-up procedures, and system backup andrecovery procedures are included.

Use with systems deploying Scaleable OMC.

Maintenance information manuals

68P02901W26 Alarm Handling at the OMC-RThe manual includes GSM alarm reference information. In addition, alarm diagnosticsinformation and procedures are included to resolve fault conditions from the Operationsand Maintenance Centre-Radio (OMC-R).

68P02901W51: BSS Field Troubleshooting

The manual contained troubleshooting and diagnostic procedures for field engineers ortechnicians to follow at Base Station System (BSS) or Remote Transcoder (RXCDR)sites. These procedures presume that operators at the Operations and MaintenanceCentre � Radio (OMC-R) have diagnosed a problem, and have dispatched the engineeror 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. Itprovides a detailed description of all the statistics and their uses. A brief description ofthe network interfaces, links, and protocols is also provided. The MMI commands usedto perform statistical operations (enabling, disabling and displaying) are also identifiedand described.

68P02901W57 Device State Transitions

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


02 May 2003


68P02901W01-M 1�15

68P02901W58 BSS Timers

The manual contains information on the timer based software parameters within theMotorola 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.

GSR6 (Horizon II)Other manuals

02 May 20031�16


68P02901W01-M

Other manuals

IntroductionThe manuals listed in the following sections are supplied to customers whereappropriate.

SPARC E3000/E3500The SPARC E3000/E3500 and associated equipment is supplied with the relevantmanuals.

SPARCstation manualsThe SPARCstation is supplied with AnswerBook CD-ROM based on-line documentation.This typically includes the following:

S Release and Install binder.

S User�s Guide books.

S Systems and Network Administration binder.

S SunOS Reference Manual binder (three volumes).

S Global Index binder.

S SunOS Documentation Tools binder.

S Programmer�s Guides binder.

S Programmer�s Overview Utilities and Libraries binder.

S Network Programming Guide binder.

S Writing Device Drivers/STREAMS Programming binder.

S SunView Programmer�s Guide binder.

S SunView 1 System Programmer�s Guide binder.

INFORMIX manuals INFORMIX 7 documentation may be obtained by ordering the following :

S Part Number: SWDN5378.

Printer manualsThe 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:

S 6250 Operator�s Guide/Installation Guide.

S 6500 Series Product Documentation.

S 6560 Operator�s Guide/Installation Guide.

02 May 2003


68P02901W01-M 2�1

Chapter 2

Introduction to Motorola GSM

GSR6 (Horizon II)

02 May 20032�2


68P02901W01-M

GSR6 (Horizon II) Chapter overview

02 May 2003


68P02901W01-M 2�3

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), DigitalCommunications 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 alsoincludes 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 inthe BSS system.

Mobile station

This section provides an introduction to the mobile station and descriptions ofcomponents and mobile equipmnent.

GSM network specifications and recommendations

This section introduces the GSM specifications and recommendations for cellulartelephone 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 forGSM 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.

GSR6 (Horizon II)Chapter overview

02 May 20032�4


68P02901W01-M

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.

GSR6 (Horizon II) Overview of the Motorola GSM system

02 May 2003


68P02901W01-M 2�5

Overview of the Motorola GSM system

The Motorola GSM system

Motorola�s GSM cellular system provides radio coverage for communications with GSMsubscribers in a defined area. Its principle role is to support signalling and traffic channelsfor 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 mobiletelephones 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 toprovide operations and maintenance at the network level. Figure 2-1 shows the NMCrelationship to the other network elements.

Operations and Maintenance Centre-Radio

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

Mobile services Switching Centre

The Mobile services Switching Centre (MSC) is a telephone switching office for handlingcalls to and from the MSs within a defined geographical area. The MSC also providesthe interface between the cellular network and the ordinary land-based Public SwitchedTelephone Network (PSTN), allowing the GSM cellular system to function as anextension 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-1shows the MSC releationship to the other network elements.

Locaton registers

Three Location Register (LR) network elements may be collocated with the MSC. Theseare database-oriented processing nodes that manage subscriber data and keep track ofthe location of an MS as it roams around the network. For detailed information regardingLRs see the Mobile services Switching Centre section in this chapter.

The following are the LRs in the GSM Network:

S Equipment Idnetity Register (EIR)

S Home Location Register (HLR)

S Visitor Location Register (VLR)

GSR6 (Horizon II)Overview of the Motorola GSM system

02 May 20032�6


68P02901W01-M

Base Station System

The Base Station System (BSS) is the fixed end of the radio interface that providescontrol and radio coverage functions for one or more cells and their associated MSs. It isthe link between the MS and the MSC. The BSS comprises one or more BaseTransceiver Stations (BTSs), each containing the radio components that communicatewith MSs in a given area, and a Base Site Controller (BSC) which supports callprocessing functions and the interfaces to the MSC. Digital radio techniques are used forthe 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 thedigital processing interface between the BTS and the MSC. Detailed informationregarding the BSC can be found in Chapter 3 BSC description of this manual.

S Base Transceiver Station (BTS)

The BTS contains the radio components that provide the interface to MobileStations for one or more coverage areas or cells. Detailed information regardingthe BTS can be found in Chapter 3 BTS description of this manual.

S Full-rate Transcoder (XCDR) and Remote Transcoder (RXCDR)

The Full-rate Transcoder (XCDR) is the digital signal processing equipmentrequired to perform GSM-defined speech encoding and decoding. In terms of datatransmission, the speech transcoder interfaces the 64 kbit/s PCM in the landnetwork to the 13 kbit/s vocoder format used on the Air Interface.

The Remote Transcoder (RXCDR) is used when the transcoding is performed at asite away from the BSC, which is at or near the MSC. This enables 4:1multiplexing in which the transcoded data for four logical channels is combinedonto one 64 kbit/s link, thus reducing the number of links required forinterconnection to the BSCs. Detailed information regarding the XCDR andRXCDR can be found in Chapter 3 Transcoder description of this manual.

S Packet Control Unt (PCU)

The PCU is an interface adaptor handler unit that permits the Motorola GSMfacility access to the packet network. As such the PCU needs interfaces with theBSC on the GSM side, and the SGSN on the packet network side. The PCUmanages the packet radio interface and also enables the interface from the BSS tothe SGSN. The PCU itself, is managed by the existing OMC-R. Detailedinformation regarding the PCU can be found in Chapter 3 Packet Control Unit ofthis manual.

GSR6 (Horizon II) Overview of the Motorola GSM system

02 May 2003


68P02901W01-M 2�7

The Motorola GSM equipment architecture is shown in Figure 2-1 with other associatednetwork elements. The BSS components are shown shaded. Also shown is the GPRSnetwork architecture.

Figure 2-1 GSM and GPRS Architecuture (GSN Complex)

MSC HLR

OMC-G (Including Shelf

Manager)

RADIUS SERVER(NON-TRANSPARENT

MODE)

PDN

OMC-R

BILLINGSYSTEM

PCU ISS SGSN GGSN

GSNCOMMHUB

OPERATOR SERVERCOMPLEX - RADIUS SERVER(OPERATOR IS ISP,TRANSPARENT MODE)- DHCP SERVER- DNS SERVER

GSM EQUIPMENT GSN EQUIPMENT

BSS1

BSS2

BSSn

GSN1

GSNnBTSs

BSC

RXCDR

GSR6 (Horizon II)Overview of the Motorola GSM system

02 May 20032�8


68P02901W01-M

Typical GSM system

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

Figure 2-2 Typical GSM system layout � Dual BSS system

EC

NMC

OMC-S

MSC

PSTNand

ISDN

HLRAUC

VLR VLR

EIR

MOBILE n

EIR

MOBILE n

EC

MS

XCDR

MSC

IWF

MODEMS TO OTHER NETWORKS

BTS

BSC

BTS

BTSBTS BTS

BSS

BSS

BTS

BSC

BTS

1001101 1001101

XCDR

OMC-R

MS

GSR6 (Horizon II) Unique features of Motorola GSM

02 May 2003


68P02901W01-M 2�9

Unique features of Motorola GSM

Introduction to the unique features of Motorola GSM

The following describes aspects of GSM equipment that are unique to Motorola. SeeChapter overview in Chapter 3 of this manual for a general description of the MotorolaBSS.

Systems advantagesFeatures of Motorola systems that can be used to maximise GSM capacity includeunique reuse patterns, sector sharing, and equipment sharing. Many of these featuresare ideal for the system operator who has a limited number of radio channels with whichto 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 alsoprovides enhanced frequency hopping and flexible traffic channel allocation when alimited number of GSM channels is available. Enhanced algorithms and techniques willimprove handover decisions and minimise handover traffic loading on the system.

System planningA system planning capability, currently under development, is a computer program (usingartificial intelligence techniques) to assist and provide a degree of automation forfrequency planning. A plan checker capability will be included. The system includesfacilities for user interaction and user friendly (graphical) presentation of plan results andsystem statistics. Future interconnection with the OMC to provide a feedback path forperformance assessment and learning is also anticipated.

Fault tolerance

All Motorola network equipment is designed with inherent fault tolerance. All networkelements except the BTS are designed to be fault tolerant to any single point failure. TheBTS is designed to provide redundancy economically, as required.

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

S An extensive variety of alarms and indicators throughout the equipment.

S Self-calibrating subsystems, including PA and Receiver (Rx) sensitivity.

S Circuit designs that do not require tuning and are immune to drift. (For example,direct digital synthesis for the modulation, etc).

S Remotely and software controllable parameters, including transmitter power andcavity frequency.

S High-performance circuit and system designs that meet the intent of the GSMrecommendations. (For example, a low noise figure receiver achieving GSMintermodulation rejection and spurious response rejection specifications).

GSR6 (Horizon II)Unique features of Motorola GSM

02 May 20032�10


68P02901W01-M

Future system

Note that a number of GSM services are not completely specified. As GSMrecommendations mature, Motorola intends to support them. Motorola anticipates acontinual system upgrade process which includes new feature introductions and systemevolution.

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 andfacilities, Motorola will keep pace by providing interconnection to these services; andthereafter, make these services available to GSM subscribers.

GSR6 (Horizon II) Motorola network specifications

02 May 2003


68P02901W01-M 2�11

Motorola network specifications

Introduction to Motorola network elements

The following sections provide specifications for the Motorola Network Elements (NEs) inthe GSM system (including EGSM, DCS1800 and PCS1900). Specifications describedin this secton are:

S OMC-R.

S Receiver.

S Transmitter.

OMC-R specifications

The Motorola Operations and Maintenance Centre - Radio (OMC-R) is a UNIX-basedsystem. Specifications and performance data are provided in the following sections. TheOMC-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 referencesappropriate 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-TSSE.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 ofOMC operation

ITU-TSS E.410.

GSR6 (Horizon II)Motorola network specifications

02 May 20032�12


68P02901W01-M

System processorThe SUN ULTRA ENTERPRISE 3500/3000 system processor is a UNIX system. Actingas the OMC system processor, it runs the OMC application software which handles allO&M communication with the NE. It processes all incoming events, alarms,uploads/downloads, and performance statistics, and the setting up of remote loginsessions to different NEs. The system processor contains a database based on anINFORMIX Database Management System (DBMS), configured for storing performancestatistics, subscription lists, and network and map configuration data, enabling operatorsto monitor incoming events and alarms.

System processor configurationsTable 2-2 provides a comparison between the Low-End (5 k TCH), mid range (10 k and30 k TCH) and High-End (45 k TCH) OMC configurations.

Table 2-2 OMC configurations (maximum values)

Feature OMCLow-End

(5 k)

OMCMid-Range

(10 k)

OMCMid-Range

(30 k)

OMCHigh-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 GUIProcessor

1 1 1 1

Total remote dial-up sessions 2 2 2 2

Remote login sessions 6 6 20 30

Simultaneous downloads 6 6 12 12

Simultaneous uploads 4 4 16 32

Sustained event rate 8 alarms +2 state

changes

8 alarms +2 state

changes

12 alarms+ 3 statechanges

12 alarms+ 3 statechanges

Maximum event burst 20 events/sover 20

mins

60 events/sover 20

mins

60 events/sover 20

mins

60 events/sover 20

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 workstationsThe remainder of the OMC is made up of operator workstations, and is primarilyconcerned with running the OMC operator interface, known as the OMC Graphical UserInterface (GUI). Typically the OMC configuration will contain a single application GUIserver, and several ULTRA/SPARCstation 5 workstations as GUI clients. Alternativelynewer workstations can be connected directly as GUI servers. Each operatorworkstation is a complete UNIX system.

The operator workstations execute the OMC GUI software.

Optional processorsOptional processors, such as those for Mediation Device (OSI), Remote Login, OfflineBSS Configurator, can be included in the basic OMC configuration.


02 May 2003


68P02901W01-M 2�13

OMC configuration

The OMC, a system configuration based on SUN E3500/E3000 System Processorhardware, 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) variesdepending on the version and System Processor in use, as does the disk partitioning.This section describes the hardware architecture requirements for each SystemProcessor and each version, and the common software requirements.

Data communication

The OMC-R uses standard X.25 communication protocols on the interfaces with otherentities in the network.

For example, the NMC-OMC interface is defined in GSM 12.01 and corresponds to theQ3 type of interface according to ITU-TSS M.30 [1]. The OMC-R X.25 capacities are inTable 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 theScaleable 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 20032�14


68P02901W01-M

Receiver specifications

Table 2-4 lists the specifications for the receiver.

Table 2-4 Receiver specifications

Functionality Specification

Frequency range GSM850 824 to 849 MHz

GSM900 890 to 915 MHz.

Extended GSM900 880 to 915 MHz.

DCS1800 1710 to 1785 MHz.

PCS1900 1850 to 1910 MHz.

Channel spacing 200 kHz.

Frequency stability � 0.05 ppm.

RF sensitivity(reference sensitivity)

CTU, DRCU, SCU, TCU

TCU-B

The Receiver minimum sensitivity levels for GSM850,GSM900/EGSM900, DCS1800 and PCS1900 are asfollows.

Each receiver input shall have a minimum sensitivity of�104 dBm complying with GSM 05.05, section 6.2, asmeasured according to the method of GSM 11.20/11.21.

As above, but minimum sensitivity of �108.5 dBm.

Diversity gain(DRCU models only)

Both branches meet performance specifications statedabove.

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 onthe individual system and measurement conditions.

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

S 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 levelof the poorest RX branch at any given time.

For channel type specifications, see GSM 05.05, section6.2; refer to table 1 corresponding to section 6.2.


02 May 2003


68P02901W01-M 2�15


Nominal error rates There are three additional Residual Bit Error Rates(RBER): TCH/FS Class II RBER as a function ofpropagation condition.

The RBER values vary depending the RBER type andpower 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 signalinput level between �85 dBm and �40 dBm. The staticperformance shall be maintained for signal level up to�15 dBm for GSM850/900 and �23 dBm for DCS1800 orPCS1900.

Intermodulation rejection The Intermodulation Rejection power levels forGSM850/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, asmeasured according to the method of GSM 11.20/11.21.

Spurious response rejection The Spurious Response Rejection power levels forGSM850, GSM900, DCS1800 and PCS1900 are asfollows.

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, asmeasured according to the method of GSM 11.20/11.21.(See the Note).

Blocking (GSM850) The In-Band Blocking Signal Frequency Range is 804 to869 MHz for GSM850.

Minimum power levels are as follows.

S 600 kHz < |� � �0| < 800 kHz: �26 dBm.

S 800 kHz < |� � �0| < 1 GHz: �16 dBm.

S 1 GHz < |� � �0| < 3 MHz: �16 dBm.

S 3 MHz < |� � �0|: �13 dBm.

Out-of-Band Blocking Signal Frequency Range:

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

S 925 MHz < � < 12.75 GHz: 8 dBm.

These blocking characteristics comply with GSM 05.05,section 5.1, as measured according to the method ofGSM 11.20/11.21. (See the Note).


02 May 20032�16


68P02901W01-M


Blocking (GSM900) The In-Band Blocking Signal Frequency Range is 870 to935 MHz for GSM900; and 860 to 925 for EGSM900.


S 600 kHz < |� � �0| < 800 kHz: �26 dBm.

S 800 kHz < |� � �0| < 1 GHz: �16 dBm.

S 1 GHz < |� � �0| < 3 MHz: �16 dBm.

S 3 MHz < |� � �0|: �13 dBm.


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

S 925 MHz < � < 12.75 GHz: 8 dBm.

These blocking characteristics comply with GSM 05.05,section 5.1, as measured according to the method ofGSM 11.20/11.21. (See the Note).

Blocking (DCS1800) The In-Band Blocking Signal Frequency Range 1690 to1805 MHz.


S 600 kHz < |� � �0| < 800 kHz: �35 dBm.

S 800 kHz < |� � �0|: �25 dBm.


S 100 kHz < � < 1690 MHz: 0 dBm.

S 1805 MHz < � < 12.75 GHz: 0 dBm.

The blocking characteristics comply with GSM 05.05,section 5.1, as measured according to the method ofGSM 11.20/11.21. (See the Note).

Blocking (PCS1900) The In-Band Blocking Signal Frequency Range is1830 to1930 MHz.


S 600 kHz < |� � �0| < 800 kHz: �35 dBm.

S 800 kHz < |� � �0|: �25 dBm.


S 100 kHz < � < 1690 MHz: 0 dBm.

S 1805 MHz < � < 12.75 GHz: 0 dBm.

The blocking characteristics comply with GSM 05.05,section 5.1, as measured according to the method ofGSM 11.20/11.21. (See the Note).

Interference performance The Interference Performance is as specified inGSM 05.05, section 6.3, as measured according to themethod of GSM 11.20/11.21.

The following refer to the C/I ratios:

S Co-Channel Interference: 9 dB.

S Adjacent Channel Interference: �9 dB (TU50 only).

S Alternate Channel Interference: �41 dB (TU50 only).


02 May 2003


68P02901W01-M 2�17

NOTE For information regarding the exceptions that are related to theblocking and spurious response rejection test, consult GSM05.05, section 5.1 as per GSM 11.20/11.21.

Transmitter specifications

Table 2-5 lists the specifications for the transmitter.

Table 2-5 Transmitter specifications


Frequency range GSM850 869 to 894 MHz

GSM900 935 to 960 MHz.

Extended GSM900 925 to 960 MHz.

DCS1800 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 withinTimeslot

5 degrees rms, 20 degrees peak within useful part of burst.

Mean carrier outputpower

CTU, DRCU, SCU,TCU

CTU, SCU, TCU

TCU-B

During useful part of burst, measured at the top of the cabinetafter one stage of combining.

20 W � 1 dB (GSM850/900).

8 W � 1 dB (DCS1800, PCS1900).

16 W � 1 dB.16 W � 1 dB (DCS1800, PCS1900)If there is no combining, 32 W � 1 dB.

Output power adjustrange

12 dB in 2 dB steps. The tolerance is as stated in GSM05.05, section 4.1.2, as tested according to the method ofGSM 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 andPCS1900).

Modulation type GMSK BT = 0.3.

Dynamic power controlrange

30 dB, complying with GSM 05.05, section 4.1.2, asmeasured according to the method of GSM 11.20/11.21.

Intermodulationattenuation

Complies with GSM 05.05, section 4.7.1, as measuredaccording to the method of GSM 11.20/11.21.

Intra-BTSintermodulationattenuation


Spectrum due tomodulation



02 May 20032�18


68P02901W01-M


Spurious emissionsfrom antennaconnector


Spurious Signal Frequency100 kHz to 1 GHz1 GHz to 12.75 GHz890 MHz to 915 MHz

Radiated spuriousemissions


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

GSR6 (Horizon II) Security management

02 May 2003


68P02901W01-M 2�19

Security management

Password levels

Passwords are required to access some commands in the BSS system. There are threelevels of security in the BSS system:

Level 1 - Permits only the display of certain system elements. This is the entrance levelafter boot has completed.

Level 2 - Permits access to all user-visible system commands, including changingpasswords for Levels 1 and 2.

Level 3 - Permits access as for level 2, and access to the executive monitor. Twopasswords are required at this level. Only users who have purchased the level 3password 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 thatcan be changed by the customer. Level 3 access is normally protected by twopasswords that cannot be changed by the customer. Purchasing this feature allows thecustomer to change the Level 3 passwords (and access the Exec Monitor emon) usingthe chg_password command, so limiting the distribution of the Level 3 passwords to aselected group of people.

Releated commands and parameters

The chg_password command can be used to change the two Level 3 passwords, aswell as the Level 2 password.

System impact

At the OMC-R GUI, the TTY (rlogin) and FORMS interfaces support the modifiedchg_password MMI command.

A password is no longer required for Level 1 access to the BSS.

GSR6 (Horizon II)Mobile station

02 May 20032�20


68P02901W01-M

Mobile station

Introduction to mobile stations

The subscriber uses the Mobile Station (MS) to access the services provided by thePLMN. MSs can be installed in vehicles or can be portable or hand held stations. TheMS can include provisions for data communication as well as voice communication.

Different types of MSs can provide different types of data interfaces. To provide acommon model for describing these different MS configurations, GSM defines referenceconfigurations for MSs similar to those defined for ISDN land stations.

The Mobile Station (MS) together with the Subscriber Identity Module (SIM) are definedas the radio equipment and Man-Machine Interface (MMI) that a subscriber needs toaccess PLMN services. Typically, this is a mobile telephone though it may also be amobile data communications unit.

Mobile station components

The Mobile Station consists of the Mobile Equipment (ME) and the Subscriber IdentityModule (SIM).

Mobile equipment

The Mobile Equipment is the hardware used by the subscriber to access the network.There are three types:

S Vehicle mounted, with the antenna physically mounted on the outside of thevehicle.

S Portable mobile unit, which can be hand held, but the antenna is not on thehandset.

S Hand portable unit, which consists of a small handset with the antenna attachedto the handset.

Subscriber Interface Module (SIM)

The SIM is a removable card that plugs into the ME. It identifies the mobile subscriberand 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 bydesign features such as:

S Discontinuous transmission (DTx). This ensures that the hand portabletransmitter is energised only when there is speech or data traffic to transmit.

S Discontinuous reception (DRx). This is a group paging technique that allows thehand portable to cycle to a low drain standby mode as much as 98% of the time.

S Active power control. As the hand portable gets closer to the BTS, it uses lesspower to transmit. This saves on battery life.

GSM hand portables also incorporate digital signal processing.

GSR6 (Horizon II) Mobile station

02 May 2003


68P02901W01-M 2�21

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 MSsends this number over the signalling channel to the MSC. The IMEI can be used toidentify 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 IdentityRegister (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 themobile subscriber. Different subscriber identities are used in different phases of call setup. The International Mobile Subscriber Identity (IMSI) is the primary identity of thesubscriber 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). Afterthe subscriber�s IMSI has been initialized on the system, the TMSI can be used forsending backwards and forwards across the network to identify the subscriber. Thesystem automatically changes the TMSI at regular intervals, thus protecting thesubscriber from being identified by someone attempting to monitor the radio channels.The TMSI is a local number and is always transmitted with the Location AreaIdentification (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 landnetwork 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 equipmentidentity, a GSM PLMN can route calls and perform billing based on the identity of thesubscriber rather than the mobile equipment being used. This can be done using aremovable Subscriber Information Module (SIM). A smart card is one possibleimplementation of a SIM module.

The following information is stored in the SIM:

S IMSI. This is transmitted at initialization of the mobile equipment.

S TMSI. This is updated periodically by the PLMN.

S MSISDN. This is made up of a country code, a national code and a subscribernumber.

S Local Area Identity (LAI). This identifies the current location of the subscriber.

S Subscriber Authentication Key (Ki). This is used to authenticate the SIM.

When the SIM is inserted in the mobile equipment, a location update procedure registersthe subscriber�s new location, allowing the correct routeing of incoming calls.

GSR6 (Horizon II)GSM network specifications and recommendations

02 May 20032�22


68P02901W01-M

GSM network specifications and recommendations

GSM advantages

The advantages of GSM flow from the standardization of the GSM specifications, thedigital nature of the GSM network, and the increased capacity and low error ratescompared with analogue networks.

Digital networks

GSM networks are digital and can cater for high system capacities. They are consistentwith the world-wide digitization of the telephone network, and are an extension of theIntegrated Services Digital Network (ISDN), using a digital radio interface between thecellular network and the mobile subscriber equipment.

Increase capacity

The GSM system provides a greater subscriber capacity than analogue systems. GSMallows 25 kHz per user, that is, eight conversations per 200 kHz channel pair (a paircomprising one transmit channel and one receive channel). Digital channel coding andthe modulation used makes the signal resistant to interference from cells where the samefrequencies 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. Thisallows increased geographic reuse by permitting a reduction in the number of cells in thereuse pattern. Since this number is directly controlled by the amount of interference, theradio transmission design can deliver acceptable performance.

GSR6 (Horizon II) GSM network specifications and recommendations

02 May 2003


68P02901W01-M 2�23

Frequency reuse

Cellular networks were developed to circumvent the problems of needing increasinglypowerful radio equipment and having to use a greater number of individual frequenciesas usage increased. With a GSM cellular network, the mobile equipment is not morethan a few kilometres from the transceiver, therefore pairs of frequencies (one fortransmit, one for receive), called reuse groups, can be reused in a geographic repeatpattern across the network. Figure 2-3 shows a four-cell frequency reuse pattern.

Figure 2-3 Four cell frequency reuse pattern

FREQUENCYREUSE

GROUP 1

FREQUENCYREUSE

GROUP 2

FREQUENCYREUSE

GROUP 3

FREQUENCYREUSE

GROUP 4

FREQUENCYREUSE

GROUP 1REUSED

Audio capacity

Digital transmission of speech and high performance digital signal processors providegood quality speech transmission. In regions of interference or noise-limited operationthe speech quality is noticeably better than analogue. Where noise or interferenceobliterate speech frames, error correction is used to put back some of the missinginformation, and if too much information is lost, a digital extrapolation algorithm is used tofill the gap. While the precise implementation of the extrapolation algorithm is up to themanufacturer, GSM recommends minimum and maximum permitted extrapolations.

Link integrity

GSM incorporates several features to achieve a high-integrity communication link and toensure high quality signalling performance. Call re-establishment procedures allow lostsubscribers to reconnect to an interrupted connection. These procedures reduce thenumber of dropped or lost calls.

A unique feature of digital communication is the use of the error control coding toestimate the bit error rate of the channel being used. In this way the system evaluateslink quality and can take action on co-channel and adjacent channel interference, evenwhen signal levels are relatively high. A subscriber is handed over to a different cell orchannel if detrimental interference is sensed.

GSR6 (Horizon II)GSM network specifications and recommendations

02 May 20032�24


68P02901W01-M

Subscriber services

Under GSM, subscriber services similar to those provided by an ISDN land network canbe made available to mobile and hand portable Mobile Stations. The Mobile Station isprovided with control channels (similar to the D channel on ISDN) and a traffic channelfor user data or digitized voice (similar to the ISDN B channel). Both data and voice arecarried in digital form on the radio interface, allowing end-to-end digital connectionsthrough the land and GSM networks. The control channels also provide the mobilesubscriber with supplementary services similar to those in the ISDN land network, suchas calling number presentation, closed user groups, and in-call modifications.

Data communications

In addition to provisions for voice communication, GSM MSs can provide either anISDN S interface point, or an ITU-TSS X or V-series interface, to connect standard dataterminal equipment. A data interworking function allows interworking with other datanetworks such as the ISDN land network. For interworking with an analogue-orientedPublic Switched Telephone Network (PSTN), the function connects data from the mobilethrough 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 beprovided, 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 capabilityto indicate which type of data call is being set up.

Teleservices

GSM provides several categories of teleservices, including basic speech, Short MessageService (SMS) (for messages such as those sent to a pager built into the MS), messagehandling service, facsimile, videotex, and teletext. Data services are also available inboth circuit and packet modes and with a diversity of interworking functions to supportinterfaces between the PSTN and the ISDN. This includes traditional land line analoguemodems provided for interface to the land network. Transparent transmission can beused, which includes error correction. Data rates from 300 to 12,000 bits per second areprovided. If improved error control is desired, data services using a non-transparentprotocol can be invoked. This error detection/retransmission scheme provides for muchreduced net error rates, though the throughput rate is dependent on the radio channelquality and is not affected by the error control.

Security features

Security features of GSM protect both users and operators against eavesdropping andthe misuse of valuable resources. Specific provisions protect subscriber identity andauthentication, user data, and elements of the signalling information.

GSR6 (Horizon II) GSM network elements

02 May 2003


68P02901W01-M 2�25

GSM network elements

Introduction to GSM network elementsThe GSM network incorporates a number of network elements to support mobiletelephones and other mobile equipment (known collectively as Mobile Stations, or MSs).These elements form the major components of the GSM network.

Network managment centre functionsThe Network Management Centre (NMC) is an element defined by the GSMrecommendations for managing an entire GSM cellular network to provide operationsand maintenance at the network level..

The NMC performs the following functions:

S Monitors trunk routes between nodes on the network.

S Monitors high level alarms.

S Monitors OMC-R regions and provides assistance to OMC-R staff.

S Passes information from one OMC-R region to another to improve problem solvingstrategies.

S Enables long-term planning for the entire network.

National managementThe NMC performs overall management of the PLMN, being responsible for operationsand maintenance at the network level and managing traffic on the network. It is a singlecontrol point in systems with multiple MSCs, with the ability to co-ordinate interconnectsto networks such as alternative PSTNs.

Monitoring equipmentBoth the OMC-S and OMC-R systems provide the NMC with information about thenetwork equipment. The NMC monitors this information for high level alarms, such as afailed or overloaded network node, and also monitors the status of automatic controlsapplied at the network equipment in response to conditions such as overload. NMCoperators monitor the network status, and in the event of a problem are able to giveguidance to staff at the appropriate OMC, according to the ability of other regions tohandle traffic flow increases.

Monitoring routesThe NMC monitors the signalling and trunk routes between nodes to prevent an overloadcondition propagating through the network. Routes between the PLMN and the PSTNare also monitored to avoid propagation of overload conditions between networks. NMCstaff are able to co-ordinate network management controls with the NMC facilitiessupporting the other networks.

Managing trafficThe NMC also manages traffic on BSS network equipment. In extreme circumstancesNMC operators are able to invoke controls such as priority access, as described in GSMrecommendation 2.11. The control of traffic on the signalling and traffic routes betweenthe MSC and BSS can be used to isolate overloading problems within a region. TheNMC provides its operators with the ability to reconfigure cell parameters as needed andto force handovers.

GSR6 (Horizon II)GSM network elements

02 May 20032�26


68P02901W01-M

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. Inthis instance, the NMC can provide operators with functions equivalent to those availableat the OMC-R. The NMC also supports planned changes to, or expansion of thenetwork.

Interface

The interface between the NMC and OMC-R is defined by GSM to use Q3 protocol on a 64 kbit/s digital link.

GSR6 (Horizon II) Operations and maintenance centre

02 May 2003


68P02901W01-M 2�27

Operations and maintenance centre

Introduction to the OMC

The GSM recommendations identify an element that controls and monitors the othernetwork elements within a region. In the Motorola GSM network, the Operations andMaintenance Centre (OMC-R) performs this function. The OMC-R also monitors thequality of service being provided by the network. The OMC-R is connected to the othernetwork elements via an X.25 packet network, and sends and receives control andnetwork information only, not speech or data traffic.

More detailed information on the OMC-R is given in Chapter 4 OMC-R Overview.

GSR6 (Horizon II)Mobile services switching centre

02 May 20032�28


68P02901W01-M

Mobile services switching centre

Introduction to the MSCThe Mobile services Switching Centre (MSC) coordinates the setting up of calls to andfrom GSM users within a defined geographical area. It is the telephone switching officefor 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 subsystemaccess to the subscriber and equipment databases.

The MSC also provides the interface between the cellular network and the ordinaryland-based Public Switched Telephone Network (PSTN), allowing the GSM cellularsystem to function as an extension of the PSTN. It also allows the GSM network tointerface to other PLMNs. There can be a number of MSCs within the region controlledby an OMC.

The MSC controls the call set up and routeing procedures in a similar way to a landnetwork end office controlling land line calls. On the land network side, the MSCperforms call signalling functions using the ITU-TSS C7 communications protocol. Theforms of the protocol used are Telephone User Parts (TUPs) on the interface to thePSTN and ISDN User Part (ISUP) on the interface to the ISDN.

MSC functionsThe MSC acts as an exchange for all types of mobile calls: local, national, andinternational. The following are mobile-specific call processing functions in the MSC:

S Provision of access to the VLR and HLR.

S Provision of access to the EIR.

S Processing of telecommunication services and supplementary services. (Forexample, Short Message Service).

S Mobility management, for example:

� Interrogation of MS.

� Paging.

� Handover.

� Call re-establishment.

� Location updating: interrogation and updating of VLR and HLR.

S Interworking between the signalling systems of fixed networks and the signallingsystem of the BSS.

S Resource handling:

� Queuing.

� Off-air call set up.

S Mobile subscriber charging.

S Inter-administrative revenue accounting.

S Security functions.

S Simultaneous and alternate use of services.

S Interworking for dual tone multifrequency signals.

S User information language. (For example, recorded announcements).

GSR6 (Horizon II) Mobile services switching centre

02 May 2003


68P02901W01-M 2�29

Gateway MSCWhen the MSC provides the interface between the fixed and mobile networks, it is knownas the Gateway MSC (GMSC), since it gives the mobile network access to the land linesof the PSTN, ISDN and data networks. It may also provide specific InterWorkingFunctions (IWFs) to other networks.

MSC flexible designThe GSM recommendations define the functions of the MSC, but allow flexibility in itsdesign.

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 dynamicload, caused for example by interworking through C7 signalling links, is kept to aminimum.

S Another approach is to separate all functional elements into separate networknodes.

S A third solution consists of combining functional elements in accordance with therequirements of the operating company. For example, the MSC and VLR can becombined, as can the HLR and AUC.

In practice, due to the transmission capacity of C7, the MSC should not be separatedfrom the VLR, nor the HLR from the AUC.

InterfacesThe MSC has interfaces to the following:

S OMC-R.

S Other MSCs within the same PLMN.

S BSSs.

S Location registers: HLR, VLR and EIR.

S Emergency Service Centre.

S Service Centre (SC) - Used for Short Message Service.

S Other networks, including the PSTN/ISDN, PDN and other PLMNs.

A interfaceThis interface between the MSC and the BSS is defined as the A Interface. Theinterface is based on the use of one or more E1/T1 digital links. The channels on theselinks can be used for traffic or signalling.

The A Interface provides facilities to the traffic channels and signalling links for thefollowing functions:

S Terrestrial management: allocation and blocking of the terrestrial traffic channels.

S Radio channel management: BSS management � radio channelallocations/control.

S Mobility management: location update � transparency between the MS and MSC.

S Call control: set up for mobile originating/terminating calls.

S Supplementary services: transparency through the BSS.


02 May 20032�30


68P02901W01-M

Layered signallingThe signalling is layered, similar to that in the OSI reference model. However, the layersreferred to are not identical but are specified by ITU-TSS C7.

BSSMAP and DTAPThe 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 thegeneral BSC BSSMAP messages must be distinguished from the DTAP messagesspecific to the mobile station connection, with the DTAP messages identified betweenthemselves. For the DTAP messages the virtual circuit approach is used withindependent connections established and released.

ProtocolsFigure 2-4 shows how the signalling messages are transferred between the BSC (ordifferent mobile stations) and the MSC by using the C7 MTP-SCCP stack and protocols:

Figure 2-4 A interface protocols

BSSMAP DTAP

DISTRIBUTION LAYER

SCCP

MTP

PHYSICAL LAYER

The SCCP defines several classes of services, of which only two are used in the GSM AInterface: the basic connectionless mode and a connection orientated mode. Thesemodes 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 ITU�TSS recommendations for C7. At the application level, themessages used on these interfaces are specified by GSM as the Mobile Application Part,or MAP.

Message transfer linkThe Message Transfer Link (MTL) is the Motorola name given to the signalling linkbetween the MSC and BSC.

It takes up one timeslot on the E1/T1 link.

Call controlThe MSC performs call control functions such as number translations and routeing,matrix path control, and allocation of outgoing trunks. It maintains PLMN synchronizationand provides synchronization to its BSSs. The MSC also collects traffic statistics forperformance management purposes.

Emergency callsAn international emergency number allows GSM subscribers to make emergency callswherever they are. The MSC receives the emergency call set up message, and routesthe call to the appropriate emergency centre.


02 May 2003


68P02901W01-M 2�31

Short message service

The Service Centre (SC) sends point-to-point short messages destined for an MS to theGMSC.

S The GMSC checks for errors, interrogates the HLR to determine the location of theMS and transfers the message to the appropriate MSC. (The GMSC and the MSCmay be the same equipment.) The MSC uses call set up parameters from the VLRto establish the call, and reports the outcome back to the GMSC which in turnreports to the MSC.

S If the message is unsuccessful, the GMSC requests the HLR to store the SCaddress as a Message Waiting Data for the MSISDN. The HLR determines whenthe MS is next ready to receive a message, and informs the MSC that has theinterworking interface with the SC. (The interworking MSC and the MSC may bethe same equipment.) The interworking MSC in turn informs the SC so that afurther attempt to send the message can be made.

S MSCs also handle short messages sent from an MS. The MSC local to the MSchecks the message for errors and transfers it to the appropriate interworkingMSC. 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 MSsin 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 MSCsupports the security procedures used to control access to the radio channels. Theseprocedures include:

S Passing keys to the BSS which are used to validate the identity of the mobileequipment and the subscriber.

S 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 andsome handover procedures. Location registration (and location update) allows MSs toreport changes in their locations, enabling automatic completion of MS terminated calls.The handover procedure preserves call connections as MSs move from one radiocoverage area to another during an established call. Handovers within cells controlled bya single BSC are controlled by that BSC. When handovers are between cells controlledby different BSCs, the primary control is at the MSC. Figure 2-5 shows how the twotypes of handover are achieved.


02 May 20032�32


68P02901W01-M

Figure 2-5 Handover control

BSC

MS

BSC CONTROLS BOTHCELLS, SO IT CONTROLS

HANDOVER

HANDOVER

MSC

BSC

MS

BTSBTS

BSC

EACH CELL CONTROLLED BY ADIFFERENT BSC, SO MSCCONTROLS HANDOVER

BTS

HANDOVER

BTS

Inter-MSC handovers

Handovers between MSCs can also be performed between BSSs connected to twodifferent MSCs. In these handovers, the MSC where the call originates functions as theprimary MSC, and retains ultimate control of the call through out its duration, eventhough the call processing tasks are handed over to another MSC.


02 May 2003


68P02901W01-M 2�33

Equipment identity registerThe Equipment Identity Register (EIR) option, is a centralized database for validating theInternational Mobile station Equipment Identity (IMEI).

The database contains three lists:

S The white list contains the IMEIs of valid MSs.

S The grey list contains IMEIs of equipment to be monitored and observed forlocation and correct function.

S The black list contains IMEIs of MSs which have been reported stolen or are to bedenied service.

The EIR database is remotely accessed by the MSCs in the network. The EIR can alsobe accessed by an MSC in a different PLMN. A given PLMN may contain more than oneEIR, in which case each EIR controls certain blocks of IMEI numbers. The MSCcontains a translation facility, which, when given an IMEI, returns the address of theproper EIR to access. Figure 2-6 summarises the three database lists.

Figure 2-6 Database list summary

ALL VALIDASSIGNED IDs

WHITE LIST

MOBILE 1MOBILE 2MOBILE n

MOBILE 5

MOBILE 6

MOBILE n

GREY LIST

SERVICE ALLOWED BUT NOTED

BLACK LIST

MOBILE 9

SERVICEDENIED

MOBILE 10

MOBILE n

Home location registerFigure 2-7 shows the Home Location Register (HLR), which is a database of subscriberinformation used in setting up calls. Various identification numbers and addresses arestored as well as authentication parameters, services subscribed, special routeinginformation. The current status of the subscriber is maintained.

Figure 2-7 HLR configuration

HLRHOME LOCATION

REGISTER

MSISDN

MSC

VLR

EXTERNAL PLMN

BASIC SERVICE LISTSUPPL. SERVICE LIST

CURRENT VLRCALL FORWARD

NUMBERetc. IMSI

MSISDN

IMSI

MSISDNor IMSI

MSC

VLR


02 May 20032�34


68P02901W01-M

HLR master databaseThe HLR contains the master database of the subscribers to a PLMN. This data isremotely accessed by the MSCs and VLRs in the network. A PLMN may include morethan one HLR, in which case each HLR contains a portion of the total subscriberdatabase. The subscriber data may be accessed by either the IMSI or the mobilesubscriber ISDN number. The data can also be accessed by an MSC or a VLR in adifferent PLMN to allow inter-system and inter-country roaming.

HLR dataThe data stored in the HLR indicates which basic and supplementary services a givensubscriber is allowed to use. This data is changed only when new subscribers are addedor deleted, or the specific services they subscribe to are changed. The HLR data alsoincludes temporary information related to supplementary services such as the current callforwarding number.

A subscriber�s 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 mobilesubscriber.

Authentication centreThe HLR function may also include the Authentication Centre (AUC) as shown inFigure 2-8. The AUC generates and stores the parameters necessary to authenticate asubscriber�s identity so as to guard against fraudulent system use.

Figure 2-8 Authentification centre configuration

AUTHENTICATIONCENTRE

REQUEST FORAUTHENTICATION

AUTHENTICATIONKEY

ONE PERSUBSCRIBER

RANDOMNUMBER

GENERATOR

ALGORITHMPROCESS

SIGNEDRESPONSE

RANDOMNUMBER

To MS

To VLR

Authentication keyTo support the authentication process, each subscriber is assigned an authenticationkey (Ki) which is stored only in the SIM of the MS and at the authentication centre. TheAUC generates a random number that is input to the authentication algorithm along withthe authentication key. The algorithm produces a new number called the signedresponse. To authenticate a subscriber, the random number is sent to the MS. Themobile, if it is a valid one, executes the same authentication algorithm as the AUC andusing its known Ki produces the same signed response that is sent back on the signallingchannel. Producing the same signed response from the same random number provesthe authenticity of the subscriber. This method provides increased security because nofixed keys can be acquired by anyone monitoring the radio channel.


02 May 2003


68P02901W01-M 2�35

Visitor location registerFigure 2-9 shows the Visitor Location Register (VLR), which is a local subscriberdatabase, holding details on those subscribers who enter the area of the network that itcovers. The details are held in the VLR until the subscriber moves into the area servicedby another VLR. The data includes most of the information stored at the HLR, as well asmore precise location and status information. The VLR provides the system elementslocal to the subscriber, with basic information on that subscriber, thus removing the needto access the HLR every time subscriber information is required.

Figure 2-9 Visitor location register configuration

VLRVISITOR LOCATION

REGISTER

COPY OF SELECTEDDATA FROM HLR

DATABASE FOR ALLSUBSCRIBERS

CURRENTLY IN AREASERVICED BY THIS

VLRNEW TMSI

VLR Database

MSRN (MOBILE STATION

ROAMINGNUMBER)

GENERATOR

HANDOVERNUMBER

GENERATOR

TMSI(TEMPORARY MOBILE

SUBSCRIBER IDENTITY)GENERATOR

HANDOVERNUMBER

MSRN

MSRN

IMSI

TMSIINTERROGATIONACCESS MODES

Controlling LAIsCells in the PLMN are grouped into geographic areas and each is assigned a LocationArea Identification (LAI). Each VLR controls a certain set of LAIs. When a mobilesubscriber roams from one LAI to another, the current location is updated in his VLRentry using the location validate procedure. If the old and new LAIs are under control oftwo different VLRs, the entry on the old VLR is deleted and a new entry is created at thenew VLR by copying the basic data from the HLR entry. The subscriber�s current VLRaddress, stored at the HLR, is also updated. This provides the information necessary tocomplete calls to the mobile subscriber.

Controlling MSRNsThe 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 initiallyhandled the call. The call is then forwarded using the MSRN as the called address. TheMSRN causes the call to be routed to the MSC which controls the base stations in thearea where the MS is currently located.

Allocating handover numbersThe VLR also allocates handover numbers for use in inter-MSC handovers. Thesehandovers require the call to be re-routed from the source MSC to the target MSC. Thehandover number functions similarly to an MSRN, in that it allows the required trunkconnection to be set up by routeing the call through the land network.


02 May 20032�36


68P02901W01-M

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 subscriber�sidentity. The system configuration database controls when the TMSIs are changed.Options include changing the TMSI during each location update procedure or changing itwithin each call set up procedure.

The database in the VLR can be accessed by IMSI, TMSI, or MSRN. Typically, there willbe one VLR per MSC, but other configurations are possible.


02 May 2003


68P02901W01-M 2�37

Call handling

The following figures illustrate the functions of the MSC in handling mobile originated orterminated traffic.

MS to PSTN subscriber

Figure 2-10 shows a call from an MS to a subscriber in the land network (that is, thePSTN). The MSC acts as an outgoing exchange. If the call is directed to anothercountry, the MSC routes it to the International Switching Centre. If the call is to asubscriber on the national network, the call is routed to the PSTN, which sets up theconnection to the PSTN subscriber. The MSC performs the same function for a calldirected to the ISDN.

Figure 2-10 MS to PSTN subscriber call

PSTN/ISDN

MSC

VLR

PLMN

MSBSS


02 May 20032�38


68P02901W01-M

PSTN subscriber to MS

Figure 2-11 shows a call from a subscriber in the land network (that is, the PSTN) to anMS. The assumption is that the PSTN cannot interrogate the HLR, so the call has to bedirected to the Gateway MSC which performs the interrogation. The MSRN is then usedto route the call to MSC-B which pages MS-B and sets up the call to it. The connectionbetween the Gateway MSC and MSC-B may be routed through one or more transitexchanges of the national ISDN/PSTN.

Figure 2-11 PSTN subscriber to MS call

PSTN/ISDN

HLR

MS-B

GMSC

PLMN

VLR

MSC-BBSS


02 May 2003


68P02901W01-M 2�39

MS to MS calls The scenarios covered include:

S A call between MSs in the same PLMN.

S A call between MSs in different PLMNs in the same country.

S 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 thesame PLMN. MSC-A analyses the called number for MS-B, via the VLR. It interrogatesthe HLR to retrieve the MSRN which it uses to route the call to MSC-B. MSC-B acts asan incoming exchange and establishes the call to MS-B. The connection between thetwo MSCs may be routed through one or more transit exchanges of the nationalISDN/PSTN.

Figure 2-12 MS to MS call (same PLMN)

MSC-A

HLR

MS-A

VLR

VLR

MS-B

MSC-B

PLMN

MSRN of MS-BRETRIEVED

PSTN/ISDN

BSS

BSS


02 May 20032�40


68P02901W01-M

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 interrogatesthe HLR of the other PLMN to retrieve the MSRN which it uses to route the call toMSC-B. MSC-B acts as an incoming exchange and establishes the call to MS-B.

Figure 2-13 MS to MS call (different PLMN)

MSC-A

HLR

VLR

MS-B

MSC-B

PLMN

PSTN/ISDN

PLMN

VLR

MS-A

BSS

BSS


02 May 2003


68P02901W01-M 2�41

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 PLMNin another country. MSC-A determines from the international prefix that the call isdirected to another country but cannot determine the location of the called MS. The callis therefore routed to the Gateway MSC in the other country which interrogates the HLRto discover the MSC area where MS-B is currently located. The HLR returns the MSRNand the call is routed to MSC-B. MSC-B acts as an incoming exchange and establishesthe call to MS-B. The connection between the GMSC and whichever MSC area MS-Broams 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)

MSC-A

HLR

VLR

MS-B

GMSC

PLMN 1

PSTN/ISDN

VLR

MS-A

PSTN/ISDN

MSC-B

BSS

BSS

PLMN 2

GSR6 (Horizon II)Base station system

02 May 20032�42


68P02901W01-M

Base station system

Introduction to the BSS

The Base Station System (BSS) is the fixed end of the radio interface that providescontrol and radio coverage functions for one or more cells and their associated MSs. It isthe interface between the MS and the MSC. The BSS comprises one or more BaseTransceiver Stations (BTSs), each containing the radio components that communicatewith MSs in a given area, and a Base Site Controller (BSC) which supports callprocessing functions and the interfaces to the MSC. Digital radio techniques are used forthe 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 Systemsection of Chapter 3.

BSS configurations

Physically, a BTS may either be remote from its BSC. Where BTSs are remote from theBSC, they may be linked in a variety of ways. Three possible configurations are shownin Figure 2-15.

S BSS 1 is a simple configuration, with a direct link from the BSC to a single BTS.

S BSS 2 shows a spoke configuration, where each of the BTSs has its own link tothe BSC.

S BSS 3 shows a closed loop configuration, with each BTS linked to the next, and alink from the last BTS back to the BSC.

Figure 2-15 BSS configuration examples

BSC

BSS 1

MSs

LINK to MSC

BTS

BSC

BSS 2

LINK to MSC

BTS BTS

BSC

BSS 3

LINK to MSC

BTS BTS

MSs MSs MSs MSs

The configuration used at any particular site depends on a number of factors, and amixture of configurations can be used within a single BSS. BTS configurations aredescribed in greater detail in the appropriate Service Manual.

GSR6 (Horizon II) Base station system

02 May 2003


68P02901W01-M 2�43

Software functions

Table 2-6 summarizes the software functions of the BSS.

Table 2-6 BSS software function

Executive/OperatingSystem

Operations &Maintenance

Radio Subsystem Call Processing

TTY DLSPTerminal Data LinkService Process

Fault TranslationProcess

LAYER 2 INTERFACEMobile SignallingTranslation, LAPDmprotocol, and ShortMessage Servicefunctions

CMConnectionlessManager

TDM DLSPTime Division MultiplexData Link Service Process

CMConfigurationManager

Abis INTERFACEInterface betweenBSC and BTS

SCCP STATEMACHINE Signalling ConnectionControl Part

EXEC DLSPExecutive/Process Data Link Service Process

MMIMan-MachineInterface

Handover andPower Control

RRSMRadio ResourceState Machine

Initialization Process SMSwitch Manager

Process Control

Motorola BSS

In Motorola systems, the BSS equipment can be used both as a concentrator hub, as asingle site. The Motorola add and delete option allows BTSs to be strung one to anotherin an open or closed loop topology. This enhancement provides reduced line charges inlow density coverage regions such as sparse rural areas or along roads.

The BSC controls the selection of signalling channels and speech channels andmanages the radio channels. It transfers signalling information to and from MSs via theBTS.

Connection of MSC

The relationship between the radio channels at the BSS and the terrestrial circuits whichconnect the BSS to the MSC is not fixed: a radio channel and terrestrial circuit must beselected 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 switchingmatrix to connect the two together. The switching matrix also allows the BSS to performinter-BSS handovers without involving the MSC.

Speech transcoding

Speech transmitted on the GSM radio channel needs to be transcoded to reduce thebandwidth 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 inwhich the data for four logical channels is combined onto one 64 kbit/s link, thus reducingthe number of links required for interconnection to the BSCs.


02 May 20032�44


68P02901W01-M

BSS application part

At the application levels of the C7 communications protocol, GSM defines a special set ofmessages, 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.

S The Direct Transfer Application Part (DTAP) which is used over the radio interfaceto 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 topurchase 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 AbisInterface). However, Motorola offers a unique Motorola Abis Interface, called Mobis,which reduces the amount of message traffic and thus the number of E1/T1 linksrequired between BSC and BTS.

Air interface

The radio communications link between the BSS and the MS is known as the AirInterface.

The GSM Air Interface is a noise-robust transmission medium. The speed of a radiochannel used in GSM is 270.833 kbit/s. The modulation is 0.3 BT Gaussian MinimumShift Keying (GMSK).

Physical channels

The Air Interface is capable of handling simultaneous calls: any call sent on an RF carriercan share that carrier with up to seven other calls. GSM systems achieve this by virtueof the high speed of digital radio communication, which allows each call to take its turn onthe carrier with no loss of transmission quality.

Logical channels

The different types of information sent over GSM physical channels are called logicalchannels. The term �channel� is therefore used differently when applied to logicalchannels: the physical channel is a pathway for the information; the logical channel is thetype of information sent.

Logical channel types

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


02 May 2003


68P02901W01-M 2�45

Control channelsThe 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.

S Frequency Correction CHannel (FCCH). Used by the MS to correct the frequencyof its internal time base.

S Synchronization CHannel (SCH). Used by the MS to synchronize to the TDMAframe structure in the cell.

Common control channels

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

S Paging CHannel (PCH). Transmitted by the BTS to contact a specific MS.

S Access Grant CHannel (AGCH). Transmitted by the BTS to grant or refuse aspecific MS access to the system.

S Cell Broadcast CHannel (CBCH). Used to broadcast messages to all MSs in aspecific cell.

Dedicated control channels

Stand-alone Dedicated Control CHannel (SDCCH). Used during call set-up or to transmitshort messages.

Associated control channels

S Slow Associated Control CHannel (SACCH). Used by the BSS to transmit powerand timing information to the MS and to receive measurement reports from theMS.

S Fast Associated Control CHannel (FACCH). Used to transmit signallinginformation between the MS and BSS. The FACCH is used when informationmust be passed quickly, for example, during a handover.

Traffic channelsThese 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.

S 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 itsupports:

� 9.6 kbit/s.

� 4.8 kbit/s.

� 2.4 kbit/s.

GSR6 (Horizon II)GSM subsystems (non-network elements)

02 May 20032�46


68P02901W01-M

GSM subsystems (non-network elements)

Introduction to GSM non- network element subsystems

The GSM network also includes the following additional subsystems, which are notformally recognised as network elements.

Interworking function

The the Interworking Function (IWF) performs the data rate adaptation between thePLMN and networks such as the PSTN, the Integrated Services Digital Network (ISDN),and packet networks. Other functions of the IWF include provisions for mobilesubscribers to communicate with a PSTN-based modem, or to connect directly tocustomer 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 thePLMN has to be transformed from the 4-wire PLMN circuit to the 2-wire circuit on theland network. If it were not cancelled, the total round-trip delay introduced by the GSMsystem (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 thebilling data from the GSM network elements and applies the billing data to subscribers�accounts. The details of the billing centre�s operation are not addressed by GSM, and thebilling 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 thecompleted call records, as well as forwarding them to the billing centre. Therecords are stored in a disk file as they are being generated. In this case, the filehas a fixed size and when the file becomes full, it is automatically closed and anew one opened. The completed file is then automatically transferred to the billingcentre using X.25 communication links and the File Transfer, Access, andManagement (FTAM) file transfer protocol. A backup copy of the completed billingfiles can be manually copied to magnetic tape. These same storage andcommunication facilities can also be provided at HLRs and VLRs for the handlingof event records.

S Event records

These are produced by the HLRs and VLRs. An event records the locationupdates 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 ShortMessage Service (CBSMS) messages, which are unacknowledged short messages (128bytes maximum) that are broadcast to all MSs in a particular cell.

GSR6 (Horizon II) GSM system features and goals

02 May 2003


68P02901W01-M 2�47

GSM system features and goals

Introduction to GSM system features and goalsThe following describes GSM features and the technology requirements for GSM in moredetail, and summarizes the goals of the GSM specifications.

Technological requirementsMotorola participated in the GSM validation exercise by providing an extensive validationsystem, and in the process identified further technological requirements for GSMsystems, including:

S A fast, highly reliable Automatic Gain Control (AGC) to facilitate capture of theshort random access burst.

S Selection of proper filters to minimize spurious emissions without corrupting thedesired signal.

S Stable quasi-linear RF PA to provide the rapid ramping needed to achieve GSMspecified time and spectral masks.

S Adequate power supply decoupling and regulation to reduce transmitter pulsingtransients.

S Proper distribution of gain and AGC receiver stages to achieve the necessary100 dB of dynamic range.

S Self calibrating techniques for generating and demodulating Gaussian MinimumShift Keying (GMSK) that do not require tuning and are immune to drift or ageing.

S Adequate diagnostic capability, fault analysis tools, test equipment, and keyservicing test points.

S Synthesizer technology that meets the very high switching speeds required forfrequency hopping.

GSM goalsThe GSM digital cellular system is the culmination of years of concerted effort bygovernment, industry, and academic institutions to provide a fully digital, cellularradio-telephone system.

The GSM digital cellular system provides:

S European standardization.

S Good audio quality and link Integrity.

S Features supplying:

� Subscriber services.

� System-related features.

� Increased capacity.

� Lower cost infrastructure.

� Hand portable viability.

European standardizationBefore the introduction of GSM, most of the cellular networks used in Europe wereincompatible with one another. GSM aimed to provide a common European system, sothat a subscriber could be provided with uninterrupted service, regardless of the countryin 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 frequencybands. This technology is now being employed world-wide.

GSR6 (Horizon II)GSM system features and goals

02 May 20032�48


68P02901W01-M

Standardized electrical interfaces

GSM defines standardized electrical interfaces and communications protocols for boththe fixed and subscriber equipment. This guarantees compatibility and interworkingbetween systems designed by different manufacturers and also allows the user tochoose 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).

S MSC � MSC (of National concern).

S MSC � BSC (of National concern).

S BSC � BTS (not used by Motorola).

S BTS � MS.

S MSC � All LRs.

S LR � LR.

S Subscriber ISDN Interfaces.

ISDN compatibility

GSM is compatible with the Integrated Services Digital Network (ISDN) which will carryboth voice and data on standard telephone lines. This is the telecommunicationsnetwork that many countries are committed to implement.

Signalling system 7

As an extension of the land line telephone network, GSM clearly relies heavily onsignalling 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 bysystem designers and individual equipment providers to reduce the operating cost,particularly in line charges. A hierarchical network architecture employs intermediateBSC controllers between the MSC and the radio channel equipment.


02 May 2003


68P02901W01-M 2�49

Subscriber servicesGSM systems can offer an enhanced range of services, such as teleservices, data andspeech services. These services can be augmented with a variety of supplementarysubscriber services

The following are examples of some of the supplementary subscriber services:

S Number identification services.

S Call forwarding services.

S Charging services.

S Call barring services.

S Emergency services.

S Mobile access hunting.

S Call forwarding.

S Call queuing.

S Conference calls.

S An international emergency call number.

S Point-to-point and broadcast Short Message Services.

S Separate personal and business numbers for a single subscriber.

S Videotex, teletex and fax.

SecurityGSM security features include the authentication of the mobile equipment and thesubscriber. Control information is encrypted, and speech is digitally encoded. Thesefeatures provide confidentiality and prevent stolen equipment from being used.

HandoversGSM handovers are more tightly controlled than analogue handovers. MSs have built-inintelligence to assist in the handovers, which ensures that the network is relieved ofunnecessary measurement reporting and associated overheads.

During the handover procedures, extensive measurements are made both by the MS andthe BSS of such parameters as uplink (MS-to-BSS) and downlink (BSS-to-MS) signallevels, downlink signal levels of adjacent cells, BSS-to-MS distance, and so on. Many ofthese measurements are cross-checked to ensure trustworthiness. For example, notonly is the received level of adjacent cells measured, but the associated control channelID is also received, decoded, and reported together with the quality of reception (bit errorrate). 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 integrityGSM incorporates several features to achieve a high-integrity communication link and toensure high quality signalling performance. Call re-establishment procedures allow lostsubscribers to reconnect to an interrupted connection. These procedures reduce thenumber of dropped or lost calls.

A unique feature of digital communication is the use of the error control coding toestimate the bit error rate of the channel being used. In this way the system evaluateslink quality and can take action on co-channel and adjacent channel interference, evenwhen signal levels are relatively high. A subscriber is handed over to a different cell orchannel if detrimental interference is sensed.


02 May 20032�50


68P02901W01-M

Tracking

GSM systems keep track of the MS better than analogue systems because GSM useslocation updating. When the MS moves to a new location area, the VLR is updated. Thesystem also knows whether or not an MS is switched off, so does not waste resourcestrying 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.

S DTx (Discontinuous Transmission).

S DRx (Discontinuous Reception).

Increased capacity

GSM systems have more capacity than analogue systems. Eight simultaneous calls canbe active on one RF carrier (as opposed to one call per carrier in analogue). Less RFhardware is therefore required to expand a GSM system. GSM uses a radio channelstructure (TDMA) that will lead to an increased capacity of 16 simultaneous calls percarrier 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 radiospectrum to data rate. GSM provides specialized data and message services, such as apoint-to-point Short Message Service (for messages such as those sent to a pager builtinto the MS). The call lengths of these data services average much less than thecorresponding speech calls.

Lower cost infrastructure

GSM design is intended to minimize the cost of the service provided. For example, thesignalling rate and Time Division Multiplexing Access (TDMA) structure of 8 was selectedas a compromise between equipment complexity, system issues, and performance. Theuse 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 degreesector arrangement, which provides about a 12 dB Carrier to Interference Ratio (C/I) for90% location reliability.

In addition, a unique Motorola design proposes a 2-site (6-sectored) repeat pattern using60 degree sectors. The capacity of this pattern is 40% greater than the 3-site repeatgeneric pattern and provides nearly equivalent C/I performance. This capacityimprovement is further influenced by a trunking efficiency factor due to the fact that thereduced cell reuse patterns allow a smaller number of frequency groups. The improvedC/I, in conjunction with the more accurate and sophisticated handover technique, allowsmicrocells to be used.


02 May 2003


68P02901W01-M 2�51

Timing adjustment

The further the MS is from the base station, the longer it takes for the bursts oftransmission to travel the distance between them. The short duration of the TDMA burstdemands a high degree of accuracy, so the problem of a varying time lag has to beovercome by timing corrections performed by the MS. The distance between the MSand the base station is measured and used by the base station to calculate a timingadvance which the MS is instructed to use for all uplink transmissions. This timingadvance information is sent to the MS twice a second using the SACCH. The advance issuperimposed on the 3-timeslot offset of the frame structure which the MS uses whentransmitting.

Echo cancellers

Another problem is that of echo, which is made noticeable by hybrid transformersconverting the signal from 4-wire circuits in the PLMN to the traditional 2-wire circuits inthe land telephone network. High-performance echo cancellers are therefore providedfor 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 highstability (0.05 ppm) reference which can be referenced to a system-wide standard. MSslock 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 GSMrecommendations.

Synchronization also allows the effective number of channels available for frequencyhopping to be increased and the capacity of a limited number of radio channels to bedistributed more evenly. Both these enhancements are useful where a limited spectrumis 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 encodingscheme, the information is spread out by being interleaved, and the decodingmethods allow error detection and correction.

S Each burst carrying encoded information includes a training sequence. Anequalizer in the receiver uses this to synchronize to the burst and then measuressignal distortion and calculates from that the most probable transmitted sequenceof bits.

S Frequency hopping, as well as providing security, makes GSM systems moreresistant to the effects of multipath fading.

S The use of two antennas at the BTS, placed several wavelengths apart, createsdiversity of radio paths from the MS, leading to improved reception.


02 May 20032�52


68P02901W01-M

BSS Location Services supportThe Location Services (LCS) feature implements emergency services functionality inGSM systems (compliant with the Federal Communications Commission (FCC) 911requirements) 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).

S Phase 2

To transmit the emergency caller�s estimated position, expressed in latitude andlongitude coordinates within specified limits of accuracy.

Applications that request location estimates from location services can be located in theMS, the network, or externally to the PLMN.

LCS positioning mechanismsLocations services currently specify three positioning mechanisms in order to determinethe location of a Mobile Station. These positioning processes involve two main steps:signal measurement and position computation based on the measured signals. Thestandard SMG (Special Mobile Group) positioning mechanisms are:

S Network-based uplink Time of Arrival (TOA) - not implemented by Motorola

S Enhanced Observed Time Difference (E-OTD) - not implemented in this release,

S Assisted GPS (A-GPS) - not implemented in this release.

Conventional GSM Timing Advance (TA) measurements can also be used in conjunctionwith Cell ID determination to provide a coarser, lower quality location estimate.

Examples of applications to which LCS MS position determination can be applied are todeliver tailored content to MSs in a physical locality (location specific advertising), or todetermine the routing of voice traffic (location sensitive routing). Motorola supportsTiming Advance (TA), Enhanced Observed Time Difference (E-OTD) and Assisted GPS(A-GPS) positioning mechanisms.

Time of arrival positioning procedureThe BSS does not handle the Time of Arrival (TOA) positioning procedure, and thereforemust reject requests for this positioning method.

If the BSS receives a BSSLAP TOA Request from the BSS-based SMLC, the BSSsends a BSSLAP Reject message to the BSS-based SMLC with cause value set topositioning procedure not supported.

If the BSS receives a BSSLAP TOA Request from the MSC, the BSS sends a BSSLAPeject message to the MSC with cause value set to positioning procedure notsupported.

NOTE Motorola does not support the TOA method.

Timing Advance positioning (TA)The Timing Advance positioning mechanism is based on the existing GSM timingadvance measurements, the frequency of sending of which is specified by thetiming_advance_period parameter. The timing advance value is known for the servingBTS and when returned to the requesting LCS client, with the cell ID, provides theapproximate physical position of the MS.

GSR6 (Horizon II) E1/T1 links

02 May 2003


68P02901W01-M 2�53

E1/T1 links

Link types

GSM uses two types of operating links, E1 and T1, to provide the physical links on thenetwork. Communication between the PSTN, MSC and BSS equipment is over E1/T1links. 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. Readthe 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/stimeslots, of which 30 are generally available:

S Timeslot 0 is always reserved for synchronization purposes.

S Although the remaining 31 are available for PCM or data channels, one is normallyreserved 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/stimeslots, all of which are available for PCM or data channels:

S Synchronization uses an additional bit, therefore one frame of data comprises 193bits (24 timeslots of 8 bits, plus 1 synchronization bit).

S Control information is either multiplexed with the PCM (bit stealing) or performedvia a 64 kbit/s timeslot.

NOTE The T1 link is sometimes referred to as a 1.5 Mbit/s link orbearer.

BSC daisy chain

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

GSR6 (Horizon II)Standardized interfaces

02 May 20032�54


68P02901W01-M

Standardized interfaces

Interface types

A major portion of GSM recommendations deals with standards for interfaces betweennetwork elements. Communication between the PSTN, MSC, and BSS equipment isover 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).

S Abis Interface: Remote BTS-to-BSC.

S A Interface: BSC-to-MSC.

S B Interface: MSC-to-VLR.

S C Interface: MSC-to-HLR/AUC.

S E Interface: MSC-to-MSC.

S F Interface: MSC-to-EIR.

S G Interface: VLR-to-VLR.

S H Interface: HLR-to-AUC.

S Lb Interface: BSS-to-BSS-based SMLC.

The use of these standardized interfaces throughout the mobile network allowscompatibility between network elements from different manufacturers.

For example, ITU-TSS Signalling System 7 (C7) is extensively used as thecommunications 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 StandardsOrganization (ISO) have been followed for the protocol layers of the Open SystemsInterconnection (OSI) seven layer model. The system can be changed from the ISOstandard C7 to the ANSI standard SS#7 for PCS1900.

GSR6 (Horizon II) Standardized interfaces

02 May 2003


68P02901W01-M 2�55

GSM functional layeringThe layering of GSM functions is partially based on the seven layer model for opensystems interconnection suggested by the ISO. Each layer performs a specific set offunctions that are isolated and enhances those performed by the lower layers. Thisphilosophy facilitates a modular approach to implementation. The functions occurring atone layer have only limited interaction with those at another. This provides a degree offlexibility for future improvements without redesigning the entire system.

Layer 1 � Physical

Layer 1 comprises the physical channel layer and is concerned with transmitting andreceiving coded information symbols over the radio link. Layer 1 features include theTDMA 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).

S Mobility management (authorization, location updating, IMSI attach/detach,periodic registration, ID confidentiality and so on).

S Call management (control, supplementary services, Dual Tone Multi�Frequency(DTMF), Short Message Service and so on).

Figure 2-16 shows the GSM functional layering.

Figure 2-16 GSM functional layering

Layer 1 Physical Channel Layer

Transmits and receives coded information symbols over the radio link

Transport Layer

Multiplexes and demultiplexes logical channels:

Traffic Signalling SynchronizationControl

Management Layer

Radio Resource Management

MobilityManagement

CallManagement

For example:PagingCipher mode setFrequency redefinitionAssignmentsHandoverMeasurementsReports

For example:AuthenticationLocation updatingIMSI attachIMSI detachPeriodic registrationID confidentiality

For example:ControlSupplementary servicesDTMFShort Message Service

Layer 2

Layer 3


02 May 20032�56


68P02901W01-M

BSSAP messaging

The A�interface and Lb-interface carry C7 BSSAP messaging. The four types of BSSAPmessaging on these interfaces are:

S BSSMAP(-LE) on the BSS-based SMLC-BSS link (Lb Interface, a two-waySMLC�BSS protocol).

S BSSMAP on the MSC-BSS link (A-interface, a two-way MSC-BSS protocol).

S 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 SMLCand LMU use to communicate with each other. There is, however, no direct linkbetween BSS-based SMLC and LMU.

S DTAP on the BSS-MS link (Air Interface, a two-way MSC-MS protocol). The BSStransparently forwards DTAP messages which the MSC and MS use tocommunicate with each other. There is, however, no direct link between MSC andMS.

ISDN messaging

Integrated Services Digital Network (ISDN) messaging is provided from the mobilesubscribers 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 twotypes of BSSAP messaging on these interfaces are:

S BSSMAP on the MSC-BSS link (A Interface).

S DTAP on the BSS-MS link (Air Interface).

Location register interfaces

For the interfaces between the MSC, VLR, HLR, and EIR, the lower level communicationfunctions also follow ITU-TSS recommendations for C7. At the application level, themessages 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 OSIupper 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 a64 kbit/s digital link.


02 May 2003


68P02901W01-M 2�57

Interface summary

Figure 2-17 summarizes the GSM Interfaces:

Figure 2-17 GSM interface summary

OMC to all network elements OMAP on X25

MSC to PSTN TUP on C7

MSC to ISDN ISUP on C7

InterfaceName

Interfacing network elements

Air Interface

MSC to HLR/AUC

Main messaging protocols used

Abis Interface

A Interface

B Interface

C Interface

D Interface

E Interface MSC to MSC

VLR to HLR

MSC to VLR

BSC to MSC

BSC to remote BTS

BTS to MS

BSSMAP/SCCP on C7, X25

MAP/TCAP/SCCP on C7

MAP/TCAP/SCCP on C7

MAP/TCAP/SCCP on C7

MAP/TCAP/SCCP on C7

GSMinterfaces

Externalinterfaces

F Interface

G Interface

H Interface

MSC to EIR

VLR to VLR

MAP/TCAP/SCCP on C7

MAP on C7

DTAP/LAPDm

DTAP/LAPD

��

Lb Interface

HLR to AUC No specified protocol

BSS to BSS-based SMLC BSSLAP/BSSMAP/SCCP on C7

�

�

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 20032�58


68P02901W01-M

A interface

The interface between the MSC and the BSS is a standard interface, called the AInterface. The A Interface is fully defined in the GSM recommendations.

The signalling portion of the interface between the MSC and the BSC uses the C7protocol, for which application parts are defined, for example the Base Station SystemApplication Part (BSSAP).

The A Interface allows customers to purchase the switching equipment (for example theMSC) from one supplier, and the radio equipment (such as the BSS) from anothersupplier, and still have equipment compatibility.

For support of location services there are modifications to the A-interface: changes tovarious protocols to support SMLC-BSS signalling through the MSC when the SMLC isNSS-based.

The new messages for the Motorola implementation of location services for the BSSMAPprotocol are:

S BSSMAP Connection Oriented Information

S BSSMAP Connectionless Information

A new protocol, BSSLAP, has also been added. This protocol is used for SMLC-BSScommunication as well as a carrier for SMLC-MS messages. The BSSLAP messageswhich are supported are:

S BSSLAP TA Request

S BSSLAP TA Response

S BSSLAP MS Position Command

S BSSLAP MS Position Response

S BSSLAP Abort

S BSSLAP Reset

S BSSLAP Reject

Abis interface

The GSM defined interface between the BSC and the remotely located BTS equipment iscalled the Abis interface. It uses Link Access Procedure D (LAPD).

At the application levels, GSM defines a special set of messages unique to the mobileapplication.


02 May 2003


68P02901W01-M 2�59

MobisThe Motorola defined BSC-to-BTS interface is a modification of the Abis standard calledMobis. It distributes functionality between the BSC and the remote BTS equipment, andoffers several advantages:

S Reduced signalling link traffic, which permits efficient use of E1/T1 links. The BTSperforms handover data processing. This reduces the amount of data sent to theBSC over the signalling link. This significantly reduces the amount of processingrequired in the BSC.

S Better synchronization of the BSC and BTS. This ensures better handover fromone traffic channel to another.

S Improved overload control and fault recovery algorithms.

S Efficient use of the paging and access grant channels.

S 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-BTSsignalling for location services. The following messages are new for this interface:

S ta request

S ta response

S application information

Air interfaceThe GSM recommendations include detailed specifications for the radio channel (AirInterface) 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 codedinformation symbols over the radio link. Layer 1 provides the basic time divisionmultiplexing (TDM) frame structure including timeslot, frame, multiframe, and so on.Layer 1 also provides for multiplexing and demultiplexing (channel encoding/decoding) ofthe 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 errorfree 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).

S Mobility management (authentication, location updating, International MobileSubscriber Identity (IMSI) attach/detach, periodic registration, ID confidentiality).

S Call management (call set up, supplementary services, dual tone multifrequency(DTMF), short message service).

Support for location servicesA new message has been added to the RR protocol for transport of SMLC-MSmessages. 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 20032�60


68P02901W01-M

Lb interfaceThe Lb-interface is a new interface for support of location services. It is located betweenthe 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 theSMLC is NSS-based.

At the physical level, the interface supports one or multiple 64kbit/s signalling timeslotson E1 signalling link. By convention, these timeslots are typically placed only on timeslot16 of a given E1 signalling link. The Lb-interface, like the A-interface, may consist of oneor multiple E1s between the BSS and the BSS-based SMLC. However, unlike theA-Interface, no traffic carriers (CICs) are present on the E1 links (this could change in thefuture if LMUs on a TCH were to be supported).

The Lb-interface fully supports all procedures in the MTPL2, MTPL3, and SCCPprotocols.

BSSMAP messages supported

For BSSMAP, the following messages are supported:

S BSSMAP Clear Command

S BSSMAP Clear Complete

S BSSMAP Clear Request

S BSSMAP Complete Layer 3 Information

S BSSMAP Paging

S BSSMAP Confusion

S BSSMAP Classmark Update

S BSSMAP Handover Required

S BSSMAP Handover Required Reject

S 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

S BSSMAP-LE Perform Location Response

S BSSMAP-LE Perform Location Abort

S BSSMAP-LE Connection Oriented Information

S BSSMAP-LE Connectionless Information

S BSSMAP-LE Reset

S BSSMAP-LE Reset Acknowledge

DTAP messages supported

For DTAP, the following messages are supported:

S RR Paging Response

S All MM messages


02 May 2003


68P02901W01-M 2�61

DTAP enhancements

An enhancement to DTAP has been created for the Lb-interface called DTAP-LE. This isused for SMLC-LMU communication. The messages used for DTAP-LE are:

S DTAP-LE Register

S DTAP-LE Facility

S DTAP-LE Release Complete

BSSLAP protocol

A new protocol, BSSLAP, has been created for direct SMLC-BSS communication, as wellas a carrier for SMLC-MS messages. The messages used for BSSLAP are:

S BSSLAP TA Request

S BSSLAP TA Response

S BSSLAP MS Position Command

S BSSLAP MS Position Response

S BSSLAP Abort

S BSSLAP Reset

S BSSLAP Reject

GSR6 (Horizon II)Network protocols

02 May 20032�62


68P02901W01-M

Network protocols

Protocol types

The network protocols define the format of communication between two network entities.

The network protocols are:

S E1/T1 PCM.

S X.25.

S ITU-TSS Signalling System 7 (C7).

NOTE ITU-TSS was previously known as CCITT. Signalling System 7(C7) is sometimes referred to as SS7.

S Link Access Procedure D (LAPD).

S 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

Physical

Link

G.732

Network MTP Level 3

MTP Level 2

MTP Level 1

TUP

Transport

Session

Presentation

ApplicationMAP

BSSAP(DTAP+BSSAP)

1

4

3

2

C7 Levels

TCAP

7

6

5

4

3

2

1

X25

X25Applications

Abis

LAPD

C7 X25 Others

ISUP

SCCP

GSR6 (Horizon II) Network protocols

02 May 2003


68P02901W01-M 2�63

Figure 2-19 Network protocols

NMC

OMC-S OMC-R

BTS

ÄÄÄÄÄÄ

PSTN

CBC

RXCDR

BSC

MSC

SIM

BTS

EIR EC

IWF

VLRHLR

AUC

MEMobile Station (MS)

Base Station System

CBE

X.25

LAPD LAPD

LAPDm

LAPD

X.25

C7

C7

LAPB

GSR6 (Horizon II)Network protocols

02 May 20032�64


68P02901W01-M

ITU-TSS signalling system 7The ITU-TSS signalling system 7 (C7) protocol is composed of several parts: theMessage Transfer Part (MTP), the Signalling Connection Control Part (SCCP), the X.25link, 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 layers1, 2 and 3 of the seven layer model. MTP is the transport system for reliable transfer ofmessages between users.

The three functions involved in MTP are:

S MTP1 � Signalling data link functions.

Physical, electrical and mechanical specifications for the interface.

S MTP2 � Signalling link functions.

Defines the functions and procedures for controlling the transfer of signallingmessages over a signalling link.

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

S LSSU � Link Status Signalling Unit.

S 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. Protocolclass numbers carried in the mandatory fixed field of the SCCP message indicate whichmode is being used. The two modes used for GSM are:

S Connectionless. Protocol Class 0 � Single messages are sent to other SCCPusers. The Unit Data (UDT) is the only type of message sent in connectionlessmode.

S Connection-oriented. Protocol Class 2 � A signalling connection is establishedbefore messages are sent. The following SCCP message types must be passedto 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 SCCPmessage types are used to release the connection:

S RLSD � Released.

S RLC � Release Complete.

GSR6 (Horizon II) Network protocols

02 May 2003


68P02901W01-M 2�65

X.25

The X.25 link uses LAPB and LAPD protocols for layer 2 messaging. Both LAPB andLAPD protocols are variants of HDLC:

S LAPB is used on the OML.

S 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 AirInterface.

Signalling link protocols

The link protocols used on the signalling links are listed below:

S RSL (Remote BTS-to-BSC) LAPD.

S MTL (BSC-to-MSC) C7 MTP-SCCP.

S OML (OMC(R)-to-BSS) X.25 LAPB.

S XBL (RXCDR-to-BSC) X.25 LAPD.

S CBL (CBC-to-BSC) X.25.

GSR6 (Horizon II)GSM frequencies and channels

02 May 20032�66


68P02901W01-M

GSM frequencies and channels

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 bothdecimal 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 frequencyrange.

EGSM The Extended GSM frequency range(additional 10 Mhz of bandwidth).

DCS1800 The standard DCS1800 MHz frequencyrange.

PCS1900 The higher frequency range allocated incountries such as the USA

GSM850 frequencies

GSM850 systems use radio frequencies between 824-849 MHz for receive and between869-894 MHz for transmit, as shown in Figure 2-20. RF carriers are spaced every200 kHz, allowing a total of 124 carriers for use. Other frequencies between 851 MHzand 869 MHz are available for use by other (non-GSM) cellular systems. A guard bandof 2 MHz of unused frequencies between 849 and 851 MHz protects against interferencebetween the transmit and receive frequencies. Guard bands between GSM andnon-GSM frequencies depend on the prevailing standards in the country concerned andon agreements reached by network operators. Any such guard bands are likely to bequite 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 gapreduces the possibility of interference.

Figure 2-20 GSM850 frequency range

824 839 849 851 869 884 894

GSM GSM

MHz

2 MHz GUARD BAND

OTHER CELLULARSYSTEMS

TRANSMIT AND RECEIVE FREQUENCIESALWAYS 45 MHz APART IN ANY CALL

RECEIVE FREQUENCIES TRANSMIT FREQUENCIES

GSR6 (Horizon II) GSM frequencies and channels

02 May 2003


68P02901W01-M 2�67

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





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 20032�68


68P02901W01-M

Channels 141-150





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





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


02 May 2003


68P02901W01-M 2�69

Channels 161-170





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





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 20032�70


68P02901W01-M

Channels 181-190





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





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


02 May 2003


68P02901W01-M 2�71

Channels 201-210





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





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 20032�72


68P02901W01-M

Channels 221-230





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





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


02 May 2003


68P02901W01-M 2�73

Channels 241-251





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 20032�74


68P02901W01-M

Primary GSM900 frequencies

This section lists all the frequencies used in Primary GSM (PGSM), with their channelnumbers in both decimal and hexadecimal notation.

GSM900 systems use radio frequencies between 890-915 MHz for receive and between935-960 MHz for transmit, as shown in Figure 2-21. RF carriers are spaced every200 kHz, allowing a total of 124 carriers for use. Other frequencies between 917 MHzand 935 MHz are available for use by other (non-GSM) cellular systems. A guard bandof 2 MHz of unused frequencies between 915 and 917 MHz protects against interferencebetween the transmit and receive frequencies. Guard bands between GSM andnon-GSM frequencies depend on the prevailing standards in the country concerned andon agreements reached by network operators. Any such guard bands are likely to bequite small; for example, the last carrier of the frequency range may be left unused.


Figure 2-21 GSM900 frequency range

890 905 915 917 935 950 960

GSM GSM

MHz

2 MHz GUARD BAND





02 May 2003


68P02901W01-M 2�75

Primary GSM900 channels

Channels 1�10

Table 2-22 shows the frequencies for Primary GSM (PGSM) channels 1 to 10.

Table 2-22 PGSM channels 1 to 10



1 01 890.20 935.20

2 02 890.40 935.40

3 03 890.60 935.60

4 04 890.80 935.80

5 05 891.00 936.00

6 06 891.20 936.20

7 07 891.40 936.40

8 08 891.60 936.60

9 09 891.80 936.80

10 0A 892.00 937.00

Channels 11�20

Table 2-23 shows the frequencies for PGSM channels 11 to 20.




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 20032�76


68P02901W01-M

Channels 21�30





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 31�40





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


02 May 2003


68P02901W01-M 2�77

Channels 41�50





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 51�60





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 20032�78


68P02901W01-M

Channels 61�70





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 71�80





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


02 May 2003


68P02901W01-M 2�79

Channels 81�90





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 91�100





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 20032�80


68P02901W01-M

Channels 101�110





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 111�120





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


02 May 2003


68P02901W01-M 2�81

Channels 121�124





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 20032�82


68P02901W01-M

EGSM frequencies

This section lists all the extra frequencies used in Extended GSM (EGSM), with theirchannel numbers in both decimal and hexadecimal notation. EGSM also uses allfrequencies listed in PGSM frequencies and PGSM channels.

Figure 2-22 shows that further 10MHz of bandwidth on both transmit and receiveallocations has now extended the GSM900 bandwidth.

Figure 2-22 EGSM frequency range

890 905 915 917 935 950 960

GSM GSM

MHz

2 MHz GUARD BAND



ÈÈ ÈÈ

ÈÈÈÈ

880 925

EXTRA 10 MHz BANDWIDTH

BCCH frequency, SDCCH in EGSM

The following configurations are supported by this feature:

S Stand alone extension band system.

S Dual band system with EGSM and DCS1800.

S Extension band system with originations across the entire 35MHz (BCCH+SDCCHin EGSM).

Ensuring handovers stay on EGSM band

The advanced load handover management function offers the operator the ability tospecify EGSM band handovers only to other EGSM bands. Otherwise EGSM handoverscan occur to neighbouring cells that may not have an EGSM band available. DCS1800bands may be used wastefully, particularly if the band_preference parameter is set, forexample, to DCS1800. A new parameter bss_egsm_alm_allowed enables the featureand EGSM handovers will occur only to EGSM sites, whatever the setting ofband_preference.


02 May 2003


68P02901W01-M 2�83

EGSM channels

Channels 975�984

Table 2-35 shows the frequencies for EGSM channels 975 to 984.

Table 2-35 EGSM channels 975 to 984



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 985�994





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 20032�84


68P02901W01-M

Channels 995�1004





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 1005�1014





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


02 May 2003


68P02901W01-M 2�85

Channels 1015�0





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

0 0 890.00 935.00

GSR6 (Horizon II)DCS1800 frequencies and channels

02 May 20032�86


68P02901W01-M

DCS1800 frequencies and channels

DCS1800 frequencies

This section lists the frequencies used in Digital Cellular System (DCS)1800, with theirchannel numbers in both decimal and hexadecimal notation.

DCS1800 systems use radio frequencies between 1710-1785 MHz for receive andbetween 1805-1880 MHz for transmit, as shown in Figure 2-23. RF carriers are spacedevery 200 kHz, allowing a total of 373 carriers for use, with one used as a guard band. Aguard band of 20 MHz of unused frequencies between 1785 and 1805 MHz protectsagainst interference between the transmit and receive frequencies. There is a 100 kHzguard band between 1710.0 MHz and 1710.1 MHz and between 1784.9 MHz and 1785.0MHz for receive, and between 1805.0 MHz and 1805.1 MHz and between 1879.9 MHzand 1880.0 MHz for transmit.


Figure 2-23 DCS1800 frequency range

1710 1735 1760 1785 1805 1830 1855 1880 MHz

20 MHz GUARD BAND



DCS1800 channels

Channels 512�520

Table 2-40 shows the frequencies for DCS1800 channels 512 to 520.

Table 2-40 DCS 1800 channels 512 to 520



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

GSR6 (Horizon II) DCS1800 frequencies and channels

02 May 2003


68P02901W01-M 2�87


Decimal TransmitReceiveHex.

519 207 1711.6 1806.6

520 208 1711.8 1806.8

Channels 521�530





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 531�540





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 20032�88


68P02901W01-M

Channels 541�550





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 551�560





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


02 May 2003


68P02901W01-M 2�89

Channels 561�570





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 571�580





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 20032�90


68P02901W01-M

Channels 581�590





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 591�600





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 601�610


02 May 2003


68P02901W01-M 2�91





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 611�620





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 20032�92


68P02901W01-M

Channels 621�630





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 631�640





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


02 May 2003


68P02901W01-M 2�93

Channels 641�650





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 651�660





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 20032�94


68P02901W01-M

Channels 661�670





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 671�680





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


02 May 2003


68P02901W01-M 2�95

Channels 681�690





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 691�700





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 20032�96


68P02901W01-M

Channels 701�710





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 711�720





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


02 May 2003


68P02901W01-M 2�97

Channels 721�730





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 731�740





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 20032�98


68P02901W01-M

Channels 741�750





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 751�760





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


02 May 2003


68P02901W01-M 2�99

Channels 761�770





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 771�780





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 20032�100


68P02901W01-M

Channels 781�790





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 791�800





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


02 May 2003


68P02901W01-M 2�101

Channels 801�810





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 811�820





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 20032�102


68P02901W01-M

Channels 821�830





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 831�840





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


02 May 2003


68P02901W01-M 2�103

Channels 841�850





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 851�860





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 20032�104


68P02901W01-M

Channels 861�870





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 871�880





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


02 May 2003


68P02901W01-M 2�105

Channels 881�885





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

GSR6 (Horizon II)PCS1900 frequencies and channels

02 May 20032�106


68P02901W01-M

PCS1900 frequencies and channels

PCS1900 frequencies

This section lists the frequencies used in PCS1900, with their channel numbers in bothdecimal and hexadecimal notation.

PCS1900 systems use radio frequencies between 1850-1910 MHz for receive andbetween 1930-1990 MHz for transmit, as shown in Figure 2-24. RF carriers are spacedevery 200 kHz, allowing a total of 299 carriers for use. A guard band of 20 MHz ofunused frequencies between 1910 and 1930 MHz protects against interference betweenthe transmit and receive frequencies. There is a 100 kHz guard band between 1850.0MHz and 1850.1 MHz and between 1909.9 MHz and 1910.0 MHz for receive, andbetween 1930.0 MHz and 1930.1 MHz and between 1989.9 MHz and 1990.0 MHz fortransmit.


Figure 2-24 PCS1900 frequency range

1850 1870 1895 1910 1930 1950 1975 1990 MHz

20 MHz GUARD BAND



PCS1900 channels

Channels 512�520

Table 2-78 shows the frequencies for PCS1900 channels 512 to 520.

Table 2-78 PCS 1900 channels 512 to 520



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

GSR6 (Horizon II) PCS1900 frequencies and channels

02 May 2003


68P02901W01-M 2�107


Decimal TransmitReceiveHex.

519 207 1851.6 1931.6

520 208 1851.8 1931.8

Channels 521�530





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 531�540





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 20032�108


68P02901W01-M

Channels 541�550





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 551�560





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 561�570


02 May 2003


68P02901W01-M 2�109





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 571�580





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 20032�110


68P02901W01-M

Channels 581�590





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 591�600





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


02 May 2003


68P02901W01-M 2�111

Channels 601�610





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 611�620





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 20032�112


68P02901W01-M

Channels 621�630





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 631�640





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


02 May 2003


68P02901W01-M 2�113

Channels 641�650





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 651�660





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 20032�114


68P02901W01-M

Channels 661�670





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 671�680





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


02 May 2003


68P02901W01-M 2�115

Channels 681�690





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 691�700





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 20032�116


68P02901W01-M

Channels 701�710





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 711�720





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


02 May 2003


68P02901W01-M 2�117

Channels 721�730





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 731�740





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 20032�118


68P02901W01-M

Channels 741�750





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 751�760





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


02 May 2003


68P02901W01-M 2�119

Channels 761�770





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 771�780





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 20032�120


68P02901W01-M

Channels 781�790





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 791�800





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


02 May 2003


68P02901W01-M 2�121

Channels 801�810





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 20032�122


68P02901W01-M

02 May 2003


68P02901W01-M 3�1

Chapter 3

BSS general description

GSR6 (Horizon II)

02 May 20033�2


68P02901W01-M

GSR6 (Horizon II) Chapter overview

02 May 2003


68P02901W01-M 3�3

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

S BSC description.

S BTS description.

S XCDR description.

S BSS site configuration.

S Network topology.

S BSS standardized interfaces.

S Radio system and control functions.

S Cell system radio channel reuse.

S BSS redundancy.

S Motorola PCU general description.


02 May 20033�4


68P02901W01-M

Base station system

BSS purpose and functions

The BSS is the interface between the Mobile Station (MS) and the Mobile servicesSwitching Centre (MSC) elements of the network.

The purpose of the BSS is to perform a variety of functions. The following comprise thefunctions provided by the BSS:

S Radio coverage areas and control functions for one or more cells.

S Radio coverage areas and control functions for the MSs in the cells.

S Signalling data processing and routing of the traffic data exchanged between theMS and the MSC.

S 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 linkcontains a multiplexed E1/T1 serial data stream. The BSS places MS originated, or MSterminated subscriber (signalling or traffic) data in a timeslot (channel) on a serial datastream.

Air interface link

The communication link, or Air Interface, between the BSS and the MS uses digital radiotechniques.

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 thenetwork elements:

S Base Station Controller (BSC).

S Base Transceiver Stations (BTSs) assigned to the BSC.

S Speech transcoder (XCDR) or remote speech transcoder (RXCDR) assigned tothe BSC.


02 May 2003


68P02901W01-M 3�5

Typical BSS layout

Figure 3-1 shows the layout of a typical system with two BSSs. Each BSS containsseveral components to make the link between the MS and the MSC. The BSScomponents are described in more detail in the following sections.

Figure 3-1 Dual BSS system

PSTN/ISDN/PUBLIC DATA NETWORK

BTSSITE

BSCSITEWITHXCDR

BSS #1

BTSSITE

BTSSITE

BTSSITE

BTSSITE

RXCDR(NOTE 2)

MSC

BTSSITE

BSS #2

BSCSITE

A

A

MS

Air Interface

A Interface

LEGEND

A

NOTES(1) DASHED LINES ENCLOSE NETWORK COMPONENTSOF A PARTICULAR BSS AND DO NOT SHOW THE BSSSERVICE AREA.(2) REMOTE TRANSCODING (RXCDR) IS LOCATED ATMSC SITE, BUT IS PART OF BSS #2.

BTSSITE

MS MS

MS

MS

GSR6 (Horizon II)BSC description

02 May 20033�6


68P02901W01-M

BSC description

BSC purpose and functions

The BSC network element provides the control for the BSS. It controls and manages theassociated 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 thefunctions provided by the BSC:

S Controls the BTS components.

S Performs Call Processing.

S Performs Operations and Maintenance (O & M).

S Provides the O & M link (OML) between the BSS and the OMC.

S Provides the A Interface between the BSS and the MSC.

S Manages the radio channels.

S 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 BSCsprovide 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, theBSC 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 betweenthe radio channels at the BSS and the terrestrial circuits (trunks) which connect the BSSto 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 trunkassigned by the MSC.

The switching matrix also lets the BSS perform handovers within a single BSS withoutinvolving the MSC.

Terrestrial circuit device management

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

GSR6 (Horizon II) BSC description

02 May 2003


68P02901W01-M 3�7

BSC capacity

Scaleable BSC capacity is enabled through the further exploitation of the increasedprocessing performance and memory of the GPROC2. As a result GPROC2s arerequired for use throughout the BSC. The BSC maximum capacity is increased asshown 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 eachfunction at the BSC, including Base Station Processor (BSP) and Link Control Function(LCF). BSCs for a given capacity are available, with hardware and software, accordingto the required capacity.

GSR6 (Horizon II)BTS description

02 May 20033�8


68P02901W01-M

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 BSSand 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 frequenciessection 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. Theradio channel is the communication link between the MSs within an RF coverage areaand the BSS. A single BTS site contains all the BTS network components that provideRF channels for the same geographic area.

The BTS also has a limited amount of control functionality which reduces the amount oftraffic 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.

S The number of RF channels in each cell.

S The RF frequency of the channels that each BTS site in the network will provide.

S 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 multidirectionaland 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.

S 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 followingtypes of antenna systems for RF coverage areas:

S 1 omnidirectional sector.

S 2 directional sectors (for use along highways).

S 3 directional sectors (120_ or alternate 60_).

S 6 directional sectors (60_).

GSR6 (Horizon II) Transcoder description

02 May 2003


68P02901W01-M 3�9

Transcoder description

Transcoder purpose and functions

The speech transcoder (XCDR) is the digital signal processing equipment that performsGSM defined speech encoding and decoding within the network.

The speech transcoder is the interface between the 64 kbit/s PCM channel in the landnetwork and the 13 kbit/s vocoder (actually 22.8 kbit/s after channel coding) channelused on the Air Interface. This reduces the amount of information carried on the AirInterface and hence, its bandwidth.

NOTE 13 kbit/s is the data rate of speech. This is mapped onto 16kbit/s Transcoder Rate Adaption Unit (TRAU) frames and thenchannel 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. Thiscan reduce the number of E1/T1 leased lines required to connect remotely locatedequipment.

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 toconnect 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 theMSC (RXCDR) to the BSC is also reduced, thus providing an even greater savings.

GSR6 (Horizon II)BSS site configuration

02 May 20033�10


68P02901W01-M

BSS site configuration

Introduction to BSS site configuration

The Motorola BSS uses a variety of BSC, BTS and RXCDR site configurations to meet awide range of requirements.

The following items must be considered when meeting requirements for cell siteconfiguration:

S The number of RF carriers.

S The distribution of the RF carriers at a site.

S The type of transmit channel combining.

S The number of RF carriers configured for frequency hopping.

S The antenna configuration.

S The number of E1/T1 links for traffic/signalling channels.

S The speech transcoder location.

S The equipment redundancy provided for the site(s).

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.

S Up to 100 BTS sites.

S 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 ofthe BSS.

Flexibility

Motorola BSS equipment uses a flexible architecture that expands easily. The BSC, BTSand RXCDR can start small and expand incrementally. The size of the Motorola BSCprovides significant switching capability to handle a variety of different BTS sites andnetwork configurations.

GSR6 (Horizon II) BSS site configuration

02 May 2003


68P02901W01-M 3�11

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 interfaceand for the BSC-to-MSC line interface, acting as different BSCs. Alternatively, theequipment 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 speechtranscoder modules as part of the line interface to the MSC. Alternatively, the twoshelves can be combined for more capacity.

Combined BSC and XCDR

The BSSC2 cabinet is equipped to provide both the BSC function for controlling BTSsites and the XCDR function for speech transcoding within one shelf. Alternatively, itcould have the BSC in one shelf and the XCDR in the other. This cabinet contains themodules 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 isindependent of the number of BTS sites.

In order to achieve 384 carriers for the BSC on the Dense Urban Call model (the primarymotivation for this feature), the following assumptions regarding the BSC are made:

S Support of two Message Transfer Links (MTLs) per Link Control Function (LCF) at40% MTL link utilization.

S Support of: 25 LCFs.

S GPROC2 processing is approximately four times that of a GPROC.

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


02 May 20033�12


68P02901W01-M

BTS cabinet

A BTS cabinet contains the radio transceivers and associated Air Interface modules thatmake up the BTS function. The BTS cabinet can contain equipment for up to 6 RFcarriers 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 ofcabinet, the following are the BTS functions provided:

S The Air Interface to the MSs.

S The line interface to a remote BSC.

BSSC cabinet

A single Base Station System Control (BSSC) cabinet can provide:

S The BSC function.

S The RXCDR function.

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

S A BSSC2 cabinet with the XCDR speech transcoding function.

If a BSSC2 cabinet with the XCDR is not implemented, speech transcoding can beintegrated into the BSSC2 cabinet with the BSC function.


02 May 2003


68P02901W01-M 3�13

BSS with more than one BTSFigure 3-2 shows examples of two BSSs, designated BSS #1 and #2, with more than oneBTS site. The BTS sites in these BSSs contain BTS cabinets that perform the BTSfunction 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 forthis 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 islocated remotely in a BSSC2 cabinet at the MSC site.

Figure 3-2 Multiple BTS sites per BSS

PSTN/ISDN/PUBLIC DATA NETWORK

BTSSITE

BSCSITEWITHXCDR

BSS #1

BTSSITE

BTSSITE

BTSSITE

BTSSITE

BTSSITE

MSC

BTSSITE

BSS #2

BSCSITE

A

A

MS

MS MS

MS

MS

Air Interface

A Interface

LEGEND NOTES(1) DASHED LINES ENCLOSE NETWORK COMPONENTSOF A PARTICULAR BSS AND DO NOT SHOW THE BSSSERVICE AREA.(2) REMOTE TRANSCODING (RXCDR) IS LOCATED ATMSC SITE, BUT IS PART OF BSS #2.

A

RXCDR(NOTE 2)


02 May 20033�14


68P02901W01-M

For correct implementation of the multiple BTS feature, the BSS supports the followingfunctionality:

Non-imperative handover rejection

The BSS rejects an incoming non-imperative handover if it will cause congestion reliefprocedures to be triggered. The BSS does not allow an incoming handover if the reasonfor that handover is congestion relief and the handover itself will lead to the invocation ofcongestion relief procedures. Should such a handover be allowed, then the net resultwould 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 atarget cell which had rejected a previous handover attempt, both imperative andcongestion 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 takeplace 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 triggercongestion relief procedures, the target cell attempts to inform the source cell of itsfuture, intra-BSS only, accessibility status. If the target cell is configured to optionallyinvoke congestion relief procedures after rejecting the handover request, then it may becapable of handling the necessary handovers.

If a BSS target cell accepts an incoming handover due to congestion relief, and thishandover itself triggers the target cell congestion relief procedures, the target cell doesnot trigger any handover attempts back to the source cell which triggered the congestionrelief to begin with.

Handover retry

The source cell optionally retries an imperative, intra-BSS only, handover to target cellswhich 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 ofthat handover cause this percentage to be exceeded. If such a handover is allowed tobe serviced, the net result would simply be the movement of a Multiband congestionproblem from one cell to another.


02 May 2003


68P02901W01-M 3�15

Flexible neighbour cell processing

This feature enhances the existing handover decision process by adding more flexibilityin 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 candidatesfor handovers.

Neighbours with low disuse counts

Neighbour cells whose disuse count is less than equal to the maximum disuse count arevalid candidates for handovers.

Disuse count is defined as the number of consecutive measurement reports a previouslyreported 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 theMobile is at full power. This feature removes all candidates for interference handoversuntil 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 powerbudget calculations begin immediately.

This feature uses an RXLEV of 0 if missing a measurement report.

GSR6 (Horizon II)Network topology

02 May 20033�16


68P02901W01-M

Network topology

Basic configurationsThere are three basic ways to configure BSS sites:

S Star (spoke) configuration.

S Daisy chain configuration.

S Fork configuration (used in conjunction with a daisy chain configuration).

Combinations of these configurations can be used to connect the BSC-to-remote BTSsites.

Topology modelNetwork topology is specified in terms of the continuous traffic routes between the BSCand 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 basicconfigurations. Site interconnections in the figure represent E1/T1 links, not trafficroutes. The actual connections between network sites may consist of single or multipleE1/T1 links.

Figure 3-3 Topology model

BSC

BTS 5

MSC

BTS 9

BTS 6

BTS 7

BTS 8

BTS 1

BTS 2

BTS 3

BTS 10

BTS 11

BTS 12 BTS 13 BTS 14

Daisy chain with a fork.Fork has a return-loopback to the chain.

Open-ended daisy chain.

Daisy chain with a fork.Daisy chain has a return-loopback to the BSC.

Star

BTS 4

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 chainOpen-ended daisy chain traffic routes comprise the following:

S The BSC site to terminating site BTS 12.

S The BSC site through intermediate site BTS 12 to terminating site BTS 13.

S The BSC site through intermediate sites BTS 12 and BTS 13 to terminating siteBTS 14.

GSR6 (Horizon II) Network topology

02 May 2003


68P02901W01-M 3�17

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

5 Direct ��

6 BTS 5 ��

7 BTS 6 and BTS 5 BTS 8, BTS 9, BTS 6 and BTS 5

8 BTS 7, BTS 6 and BTS 5 BTS 9, BTS 6 and BTS 5

9 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 alternativecommunications 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 chainallowing 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 existsto the BSC.

Table 3-3 BTS - BSC main and alternate paths (chain with return loop)

BTS site Main path via... Alternate path via...

1 Direct BTS 2, BTS 3 and BTS 4

2 BTS 1 BTS 3 and BTS 4

3 BTS 4 BTS 2 and BTS 1

4 Direct BTS 3, BTS 2 and BTS 1

11 BTS 2 and BTS 1 BTS 2, BTS 3 and BTS 4

Fault condition

In the event of a fault anywhere in the chain, the alternate paths provide each BTS siteon 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 andBTS 3. Sites BTS 11, BTS 2, and BTS 1 function like an open-ended chain andcommunicate with the BSC via the traffic routes on the operational part of the loop. SitesBTS 3 and BTS 4 function like an open-ended chain and communicate with the BSC viathe traffic routes on the operational part of the loop.

GSR6 (Horizon II)Network topology

02 May 20033�18


68P02901W01-M

Drop and insert BTS site configuration

The drop and insert option enhances the flexibility of Motorola BSS equipmentconfiguration. This option allows a single E1/T1 circuit to connect several BTS sites ineither a linear daisy chain or a ring topology. The closing end of the ring of BTS sitesconnects to a BSC.

Fault tolerance

A closed-loop or closed-ring topology enhances the fault tolerance of the drop and insertconfiguration. This topology prevents any single line fault from interruptingcommunication to any site.

Leased line saving

The Motorola drop and insert option for BTS sites saves on leased line costs whenaddressing 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 complywith GSM system timing and delay recommendations.

Maximum size

Each BTS site in the drop and insert configuration has one or more BTS cabinets. In thecase of chaining the maximum number of BTS sites together, each BTS cabinet in thedrop and insert configuration contains one radio transceiver and associated air interfacemodules, 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 chainedtogether should be reduced, proportionately.

GSR6 (Horizon II) BSS standardized interfaces

02 May 2003


68P02901W01-M 3�19

BSS standardized interfaces

Introduction to BSS standardized interfacesMany GSM recommendations deal with standards for interfaces between networkelements. Motorola employs internationally recognized standards for most of thenetwork 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 ensurescompatibility of network elements from different manufacturers.

Protocol layeringThe functional layering of protocols is based in part on the seven layer model for opensystems 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 lowerlayers.

The following subsections detail the BSS related equipment-to-equipment interfaces thatare standardized and specified by GSM.

A interfaceThe interface between the MSC and the BSS is a standard interface, called the AInterface. The A Interface is fully defined in the GSM recommendations.

The signalling portion of the interface between the MSC and the BSC uses the C7protocol, for which application parts are defined (for example the base station systemapplication part (BSSAP)).

The A Interface allows customers to purchase the switching equipment (for example theMSC) from one supplier, and the radio equipment (such as the BSS) from anothersupplier, and still have equipment compatibility.

Abis interfaceThe GSM defined interface between the BSC and the remotely located BTS equipment iscalled the Abis interface. It uses Link Access Procedure D (LAPD).

At the application levels, GSM defines a special set of messages unique to the mobileapplication.

MobisThe Motorola defined BSC-to-BTS interface is a modification of the Abis standard calledMobis. It distributes functionality between the BSC and the remote BTS equipment, andoffers several advantages:

S Reduced signalling link traffic, which permits efficient use of E1/T1 links. The BTSperforms handover data processing. This reduces the amount of data sent to theBSC over the signalling link. This significantly reduces the amount of processingrequired in the BSC.

S Better synchronization of the BSC and BTS. This ensures better handover fromone traffic channel to another.

S Improved overload control and fault recovery algorithms.

S Efficient use of the paging and access grant channels.

S Control of more than one BTS (sectors) on a single control link.

GSR6 (Horizon II)BSS standardized interfaces

02 May 20033�20


68P02901W01-M

Air interface

The GSM recommendations include detailed specifications for the radio channel (AirInterface) 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 codedinformation symbols over the radio link. Layer 1 provides the basic time divisionmultiplexing (TDM) frame structure including timeslot, frame, multiframe, and so on.Layer 1 also provides for multiplexing and demultiplexing (channel encoding/decoding) ofthe 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 errorfree 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).

S Mobility management (authentication, location updating, International MobileSubscriber Identity (IMSI) attach/detach, periodic registration, ID confidentiality).

S 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 betweenthe 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 theSMLC is NSS-based.

GSR6 (Horizon II) Radio system and control functions

02 May 2003


68P02901W01-M 3�21

Radio system and control functions

Introduction to radio system and control functionsThe Air Interface provides an associated control channel. This allows communication ofsignalling control channel data simultaneously with (and transparent to) user trafficchannel (TCH) data.

The associated control channel is available for both the uplink and the downlink. It allowscontinuous information reporting from the MS to the BSS, and continuous control of theMS from the BSS.

HandoverThe GSM handover process uses a mobile assisted technique for accurate and fasthandovers, in order to:

S Maintain the user connection link quality.

S Minimize interference.

S Manage traffic distribution.

3-timeslot offset

The TDMA frame structure for uplink transmission is offset by three timeslots from thedownlink frame structure; this interval allows the MS to have only one synthesizer toassess the signal level of adjacent cells. SACCH and other signalling information, whichis sent transparently with user traffic, allows continuous reporting of information from thesubscriber 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. Theability of the MS to change frequency and monitor a neighbour channel while engaged ina speech or data conversation is important for the high performance MS assistedhandover scheme employed.

MS assisted techniqueThe 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 TDMAframe 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 radiochannel frequency and monitors and measures the signal level of the six best adjacentcells.

Handover decision processMeasurements which feed the handover decision algorithm are made at both ends of theradio link.

MS endAt the MS end, measurements are continuously signalled, via the associated controlchannel, to the BSS where the decision for handover is ultimately made.

MS measurements include:

S Serving cell downlink quality (bit error rate (BER) estimate).

S Serving cell downlink received signal level, and adjacent cells downlink receivedsignal 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.

GSR6 (Horizon II)Radio system and control functions

02 May 20033�22


68P02901W01-M

BTS endAt the BTS site end, measurements which are available to the handover algorithminvolve only the uplink communication path, link quality, received signal level, and MS toBTS site distance. The MS RF transmit output power budget is also considered in thehandover decision. If the MS could be served by an adjacent cell at a lower power, thehandover is recommended. From a system perspective, handover may be considereddue to loading or congestion conditions. In this case, the MSC or BSC tries to balancechannel usage among cells.

Handover measurement summaryFigure 3-4 shows the measurements made for handovers.

Figure 3-4 Handover measurements

HandoverControl

DownlinkQuality (BER)

Downlink(Received) Level

Adjacent ChannelDownlink Level

Adjacent ChannelCell ID

MS(MobileStation)

UplinkQuality (BER)

Uplink (Received) Level

BTS(Base

TransceiverStation) Subscriber-to-Base

Distance

Dynamic power controlAs 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 withother calls and also extends the battery life in MSs, which is particularly important inhand portables.

Discontinuous transmissionThe speech transcoder is equipped with a Voice Activity Detector (VAD) that detects thepresence of speech data. Transmission is stopped in the intervals when speech isabsent. This is called Discontinuous Transmission (DTx) of speech. The feature iscontrolled 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 forspeech or data.

S The potential for interference is reduced since transmitters are only energizedwhen needed. This has the side-effect of improving the system spectrumefficiency.

The algorithm used to calculate DTx maximises the amount of off-time, while avoidingspeech clipping or distortion. Silences in the speech pattern are encoded by the VAD ata rate of 500 bit/s rather than the full 13 kbit/s, producing background noise calledcomfort noise which reduces noise contrast effects. The continuous transmission ofsignalling information is unaffected by DTx.

Discontinuous receptionOnce the MS is in synchronization with the BTS (it uses the FCCH and SCH channels toget into synchronization), it monitors two control channels: the Broadcast ControlChannel (BCCH) and the Paging Channel (PCH). If the MS is not in use, it candetermine when control information is next due, and switch off between signals. This iscalled Discontinuous Reception (DRx). The potential for 2% power cycling in standbyextends battery life in MSs.

GSR6 (Horizon II) Radio system and control functions

02 May 2003


68P02901W01-M 3�23

Timing adjustment

The TDMA bursts transmitted by MSs over the same radio channel must be kept apartfor proper recovery of received data at the BTS site. The MSs are not stationary,therefore propagation delay of MS transmissions can vary. Sometimes the delaybecomes significantly long and a burst overlaps into the next timeslot. This causesundesirable errors in the recovered data.

Timing correction is provided to maintain the guard time needed between bursts. Aclosed loop mechanism provides timing correction for the MS. The BSS detects (via atiming advance algorithm) changes in timing and if necessary the BSS sends timingadvance messages to the MS, commanding it to transmit earlier or later, as required, tooffset the modified propagation delay.

In addition, the timing advance algorithm provides an estimation of the distance betweenthe MS and the BTS site. This distance estimation can be a valuable parameter inhandover decision algorithms.

Frequency synchronization

All BSS frequencies and timing signals are synchronized to a high stability referenceoscillator in the BSS. This oscillator can free run or be synchronized to the recoveredclock signal from a selected E1/T1 serial link. Either case provides better than 0.05 ppmstability. MSs lock to a reference contained in a synchronization burst transmitted fromthe 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 equippingone cabinet with reference clock circuits and distributing the synchronized referencesignals to other cabinets eliminating their need for clock circuits. This distribution is viafibre optic cables.

GSR6 (Horizon II)Cell system radio channel reuse

02 May 20033�24


68P02901W01-M

Cell system radio channel reuse

Introduction to cell system radio channel reuseEach MS is assigned to one of eight traffic channels (timeslots) carried on an RF channeltransmit/receive frequency pair 200 kHz wide. The combination of digital channel codingand GMSK modulation provides robust radio channel transmissions and the ability tooperate with a carrier/interference (C/I) level of 9 dB. The RF frequency reuse distancebetween cells (or sectors) is directly proportional to the C/I level. Reuse distance is theminimum distance that can separate co-channel cells or sectors and still deliveracceptable 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 inother cells that are a relatively small distance away. Thus, the frequency reuse patternsare 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. A2-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, isbeing used here. In analogue systems the term cell is normallyused for a site.

9-site reuse patternFigure 3-5 shows how GSM cellular systems using a 9-site reuse pattern, are configuredwith sites providing omni-directional RF coverage areas. These sites provide about a 15dB 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

FREQUENCYREUSE

GROUP 1

FREQUENCYREUSE

GROUP 2

FREQUENCYREUSE

GROUP 3

FREQUENCYREUSE

GROUP 4

FREQUENCYREUSE

GROUP 1RE-USED

FREQUENCYREUSE

GROUP 7

FREQUENCYREUSE

GROUP 5

FREQUENCYREUSE

GROUP 6

9-SITE (OMNI) REUSE

FREQUENCYREUSE

GROUP 8

FREQUENCYREUSE

GROUP 9

GSR6 (Horizon II) Cell system radio channel reuse

02 May 2003


68P02901W01-M 3�25

3-site 3-sector reuse pattern

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

Figure 3-6 3-site (sectored) cellular system

b2

b3

a2

a3

a1

c3

c1

c2b1

a2

a1

B

C

a3

A

A

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 for90% location reliability. This arrangement requires dividing the allocated frequencies intonine reuse groups.


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


The Motorola unique 2-site reuse pattern is a 4-site repeat pattern that reuses eachfrequency group twice. Therefore, this plan is an effective 2-site repeat pattern. Eachsite is sectored into six 60° RF coverage areas. This pattern�s capacity is 40% greaterthan the generic 3-site reuse pattern using cells sectored into three 120° RF coverageareas, and provides an equivalent C/I performance.

In this arrangement, the allocated frequencies are divided into 12 reuse groups.

GSR6 (Horizon II)Cell system radio channel reuse

02 May 20033�26


68P02901W01-M

Cell pattern reuse comparisons

Table 3-4 compares the features of the various reuse patterns.

Table 3-4 Sector re-use pattern features

Reusepattern

No. of sectorsper site

C/I ratio No. of frequencyreuse groups

Comments

9-site 1 omnidirectional 15 dB for 90%location reliability

9

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

9

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

18

2-site 6 of 60_ Equivalent to the3 site/3 sectorpattern

12 40% greatercapacity than3 site/3 sectorpattern

GSR6 (Horizon II) BSS redundancy

02 May 2003


68P02901W01-M 3�27

BSS redundancy

Introduction to BSS redundancyRedundancy can optionally be added to prevent single faults from producing a capacityloss.

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 afailed module. Fault management of the redundant modules minimizes the number ofadditional modules the system requires to provide full redundancy. This design isachieved by using N+1 redundancy wherever possible.

BSS fault managementWhen failures occur, the BSS software fault diagnostics can usually isolate the failuredown to a replaceable module. Fault Management (FM) classifies failures as type Aor 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 OfService (OOS).

S Type B failures cause an alarm at the OMC and/or TTY, but the module is nottaken OOS.

Failed modulesTable 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 automaticallyswitches over to theredundant module...

No call capacity is lost;service continuesuninterrupted.

RF carrier redundancyAll RF carrier equipment can provide both signalling and traffic channels. Redundancycan be provided by equipping the cell/sector with more carrier equipment than trafficrequirements dictate:

S If additional radio channel frequencies for the cell/sector are available, theredundant carrier can provide additional capacity until a carrier or associatedequipment fails.

S If additional radio channel frequencies for the cell/sector are not available, theredundant carrier is only switched into service in response to a failure.

Interface redundancyEach 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 Abisinterface). 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 additionalinterface module are added.

GSR6 (Horizon II)BSS redundancy

02 May 20033�28


68P02901W01-M

BTS redundancy

To provide BTS redundancy, one set of RF carrier modules and associated digitalmodules for each cell or sector RF coverage area within one or more BTS cabinets at asite are required.

BSC redundancy

To provide BSC redundancy, duplicate digital modules within the same BTS/BSSCcabinet 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 thesame BSSC cabinet are required.

N+1 redundancy is available for the processing and power supply modules.

GSR6 (Horizon II) General Packet Radio Service (GPRS)

02 May 2003


68P02901W01-M 3�29

General Packet Radio Service (GPRS)

Introduction to GPRS

GPRS is a packet radio system that allows mobile subscriber (MS) units to access dataservices (such as World Wide Web (WWW) or email) using a modified GSM air interfaceprotocol. The modified air interface protocol allows multiple MS units to share a singletimeslot, 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.

S 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

Mobis

BTS

MS

BSC MSC HLR

PCU SGSN GGSN

GGSN

PDN

OtherPLMN

SMC-GMSCSMC-IWMSC

BSS-PCUinterface

A interface

GsGc

Gr

Gn Gi

GdGp

Gb

Um

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 facilityaccess to the packet network. As such the PCU needs interfaces with the BSC on theGSM side, and the SGSN on the packet network side. The PCU manages the packetradio interface and also enables the interface from the BSS to the SGSN. The PCUitself, is managed by the existing OMC-R.

See Introduction to the Motorola Packet Control Unit (PCU) section for full details.

GSR6 (Horizon II)General Packet Radio Service (GPRS)

02 May 20033�30


68P02901W01-M

GSN complex

Network elements

GPRS introduces the following new network elements, as shown in Figure 3-8:

S The Serving GPRS Support Node (SGSN).

S The Gateway GPRS Support Node (GGSN).

S The Shelf Manager (at the OMC-G).

S The GSN Complex.

The SGSN keeps track of the individual MS locations, and performs security functionsand access control. The SGSN is connected to the BSS via a Frame Relay network.

The GGSN provides interworking with external packet-switched networks and isconnected with SGSNs via an IP-based GPRS backbone network. This backbonenetwork 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 thesame level as SGSN, GGSN, and so on.

NOTE A shelf is an entity housing 16 cPCI slots plus cooling fans andpower supply units. Four of the slots are taken up by systemcards leaving 12 of the slots free for SGSNs (each SGSN is atwo-card unit in release 1.6.1.3, one for the Control Function(CF) and the other for the Transmission Function (TF) function).

GSN complex

A GSN complex comprises the following:

S Communications cabinet � housing the CommHub and the Internet SupportServices (ISS) (consisting of Domain Name Server (DNS), Network Time Protocol(NTP), Charging Gateway (CG), and Network File System (NFS)).

S GGSN cabinet � housing one or more GGSNs.

S GSN cabinet housing a cPCI shelf.

NOTE The GSN complex is not described in this manual. For furtherinformation on the GSN complex, see the Motorola GSN ServiceManual.

Operations and Maintenance (O&M) applications

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

GSR6 (Horizon II) General Packet Radio Service (GPRS)

02 May 2003


68P02901W01-M 3�31

GSM/GPRS network architecture

The Motorola specific implementation of GPRS, as integrated with the existing GSMinfrastructure 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 complexequipment.

Each BSC has a dedicated PCU, and multiple BSSs can be attached to one GSNcomplex. Several GSN complexes can be networked together to serve one PLMN. OneOMC-G can manage several GSN complexes.

Figure 3-8 GPRS network architecture showing the PCU and GSN complex

MSC HLR

RXCDR OMC-G(including Shelf

Manager)

RADIUS SERVER(NON-TRANSPARENT

MODE)

PDN

OMC-R

BILLINGSYSTEM

PCUBSC ISS SGSN GGSN

GSNCOMMHUB

OPERATOR SERVERCOMPLEX - RADIUS SERVER(OPERATOR IS ISP,TRANSPARENT MODE)- DHCP SERVER- DNS SERVER

GSM EQUIPMENT GPRS EQUIPMENT

BSS1

BSS2

BSSn

GSN1

GSNnBTSs

GSR6 (Horizon II)Packet control unit

02 May 20033�32


68P02901W01-M

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 itsdesign 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:

S PCU overview.

S PCU features.

S PCU description.

S PCU architecture

S PCU interfaces.

S PCU system and control of functions.

GSR6 (Horizon II) PCU overview

02 May 2003


68P02901W01-M 3�33

PCU overview

PCU summary

The PCU is a collection of high-performance processors that are responsible for:

S Packet scheduling on the air interface.

S Ensuring that efficient use is made of the air interface.

S Taking small uplink packets from the E1 links connected to the BSS that arecarrying user data from the MS units, and forming larger uplink packets to be sentover the E1 links to the SGSN.

S Packet segmentation and packetization on the frame relay link to the SGSNnetwork entity.

S Taking downlink packets from the SGSN and segmenting these packets into smallpackets 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

MSC SGSN GGSN

BSC GGSN

BTSMS

MAP-G

OTHERPLMN

PDN

Gi

Gn

Gr

Gb

Um

Gs Gn

Abis

SIGNALLING

SIGNALLING AND DATA TRANSFER

TE

PCU

GSR6 (Horizon II)PCU features

02 May 20033�34


68P02901W01-M

PCU features

List of PCU features

The PCU features are described in the following sections:

S Point-to-point GPRS service.

S GPRS radio channel allocation.

S Medium Access Control mode - dynamic allocation.

S Support of MS classes.

S GPRS coding schemes.

S Dynamic adaption of coding schemes.

S Two phase packet access.

S Enhanced GPRS one phase access.

S Frequency hopping of PDCH.

S Power control for uplink/downlink.

S Gb interface.

S PCU load balancing and sharing (Gb and BTS).

S MS flow control

GSR6 (Horizon II) PCU features

02 May 2003


68P02901W01-M 3�35

Point-to-point GPRS service

GPRS provides a new set of bearer services supporting packet mode transmission. Thissupporting low-speed and high-speed signalling, a data transmission technique withimproved efficiency compared with circuit based techniques.

GPRS enables the subscriber to send and receive data in an end-to-end packet transfermode, without utilizing circuit switched network resources. General characteristics whereGPRS offers superior performance compared with circuit technology include applicationswhere:

S The transmission of small volumes of data is frequent.

S The transmission of large volumes of data is infrequent.

S The time between successive transmissions greatly exceeds the average transferdelay.

The network operator can size the network optimally for efficient support of a mix ofGPRS and voice traffic. To support this mix, each timeslot on a GPRS carrier can beconfigured as dedicated to circuit traffic, or GPRS traffic, or can be configured asswitchable between the two. In the case of switchable timeslots, GPRS traffic hasprecedence 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) withinformation regarding the quality and signal strength of the link. The MS then uses thisinformation to determine whether to perform a cell reselection based upon signal strengthof neighbour cells. GPRS carriers can also be configured to support the GSMdiscontinuous transmission feature, defined for circuit switched traffic in an effort toconserve MS battery life. In network operation mode 2 the network uses the CCCHpaging channel for both CS and GPRS paging.

Table 3-6 Cell reselection modes

Cellreselection

mode

Controlelement

Functionality

NC0 MS control Normal GPRS MS control:

Autonomous cell reselection.

EnhancedNC0

MS control Functionality in NC0 mode plus:

BSS sends cell reselection commands to GPRS MS tochange cell reselection mode.


Autonomous cell reselection, MS sends measurementreports to BSS.

EnhancedNC1

MS control Functionality in NC1 mode plus:

BSS sends cell reselection commands to GPRS MS tochange cell reselection mode.

NC2 Networkcontrol

MS sends measurement reports to BSS,

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


02 May 20033�36


68P02901W01-M

GPRS radio channel allocation

Dynamic allocation of radio resources allows an operator to configure the radio resourcesof a cell as dedicated circuit switched, dedicated GPRS, or switchable between circuitswitched and GPRS. This enables efficient use of air interface resources, and allows anoperator to tailor the cellular network to the packet data traffic requirements of theoperator.

This feature provides the flexibility for a cell supporting GPRS to allocate a given radioresource to handle circuit switched voice/data or packet data, as required. A radioresource can be configured as dedicated to circuit switched traffic, packet data traffic, orswitchable between the two. In the latter case, the traffic demands of the networkdetermine the type of traffic handled by the air interface timeslot. This provides theoperator with a degree of flexibility when configuring a GPRS capable network, and alsofacilitates maximum utilization of resources. In a GPRS capable cell approachingcongestion, GPRS traffic can be given preference over the last switchable radioresource, by setting a database parameter.

Originally the Motorola GPRS product offered the capability to configure up to eightGPRS timeslots on a single carrier in a cell. The network operator can now configuremultiple GPRS carriers per cell for increased GPRS traffic handling capability to meet theincrease in packet data traffic and the expanding base of GPRS subscribers withincreased data throughput.

Medium access control mode � dynamic allocation

Medium Access Control (MAC) includes the functions related to the management of thecommon transmission resources. These include the packet data physical channels andthe radio link connections on packet data physical channels.

MAC supports the assignment of radio resources to MSs for transmission of GPRSprotocol data units (PDUs). In all cases, the network determines the assignment andtransmits 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 thepoint-to-point transfer of signalling and user data between the network and an MS. Atemporary block flow is a physical connection used by the two entities to support thetransfer of GPRS protocol data units (PDUs) on packet data channels (PDCH). A TBF istemporary 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 networkinstructs one of the MSs sharing a timeslot to transmit data on the uplink. MSs monitorthe channel for their instruction to transmit. The advantage offered by dynamic allocationmode is flexibility in the assignment of the air interface resource.


02 May 2003


68P02901W01-M 3�37

Support of MS classes

The GPRS network currently provides some form of support for all 29 multi-slot classMSs, supporting multiple timeslot allocations in the UL and DL directions. An MS thatsupports multiple UL timeslot allocation is always allocated a maximum of two ULtimeslots, for multi-slot classes mapped to GPRS classes 5, 6, 9, or 10. All other mappedclasses only allow allocation of one UL timeslot. Table 3-7 shows the mobile multi-slotclass 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 alternatesrapidly, 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 significantproportion of time switching directions, which significantly limits their total throughput.For example, the most capable semi-duplex MS can receive 4 timeslots whiletransmitting 1 timeslot, or receive 3 timeslots while transmitting 2.


02 May 20033�38


68P02901W01-M

Coding schemes

Four separate coding schemes, CS-1, 2, 3 and 4, are supported. These schemes providediffering throughput rates, as shown in Table 3-8.

Table 3-8 GPRS coding scheme characteristics

Coding scheme Throughput/TimeSlot

( k bits/s)

Effective approximateconvolutional coding rate

CS-1 9.05 1/2

CS-2 13.4 2/3

CS-3* 15.6 3/4

CS-4* 21.4 1

* 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 codingschemes, a higher throughput is enabled for MSs operating in those areas of the networkwith excellent RF coverage, based upon reduced requirement for error correction. Inthose 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 codersin the BTS to the PCU is currently implemented using 16 kbits/s TRAU-like links. Theselinks are carried over sub-rate switched E1 timeslots which have some signaling includedto ensure the link is synchronized between the channel coders and the PCU.

As additional protection and identification bits are included in the transmitted frame, thereis not enough bandwidth available on a 16 k bits/s link to carry CS-3 and CS-4. Thus anew mechanism for associating two 16 k bits/s TRAU channels together, giving an32 k bits/s TRAU, must be implemented to provide the bandwidth necessary toimplement CS-3 and CS-4.

Dynamic adaptation of coding schemes

This feature enables the network to change the coding scheme between MStransmissions 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 codingscheme in use in order to maximize throughput of the link. As an example, a MS with afairly 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 requiredwould begin to increase due to the lack of of forward error correction. In this case, therewould eventually be a point at which the throughput enabled by CS-3 would exceed thatof CS-4, based upon the fact that the added error correction would reduce the number ofretransmissions. Similarly, if the link quality deteriorates still further, CS-2 would becomethe better option.


02 May 2003


68P02901W01-M 3�39

Two phase packet access

GPRS supports two phase packet access. This feature allows an exchange ofinformation to take place between the MS and the network prior to assignment ofresources.

The purpose of the packet access procedure is to establish an uplink transmission tosupport the transfer of packet data units from the MS to the network. The packet accessprocedure can take place in either one or two phases. Two phase packet access avoidscontention. In this procedure, the MS requests a packet resource on the random accessburst. The network provides an immediate assignment of a single block, to which the MSresponds with its radio access capability (classmark) and MS ID, and the number ofoctets of user data. Based upon this information, the network assigns a resource for theuplink transmission.

One phase access

GPRS one phase uplink TBF access is an improvement over the two phase uplink TBFaccess procedure.

In a GPRS one phase uplink TBF access, the MS initiates an uplink TBF by sending aRandom Access Channel (RACH) to the BSS. The RACH is received at the BTS, whichis then forwarded to the PCU. The PCU responds to the RACH with an ImmediateAssignment message containing an uplink assignment. The MS moves to the assignedPacket Data (Traffic) Channel (PDTCH) and begins its uplink data transfer. Thisprocedure allows the MS to gain access to the network much quicker when comparingagainst the two phase establishment procedure.

Enhanced one phase access

The enhanced GPRS one phase uplink TBF access procedure speeds up the one phasepacket access procedure even further.

The enhanced GPRS one phase access procedure improves PCU assignment ofresources for a one phase uplink TBF, by enabling the BTS to react more quickly to aone phase RACH without forwarding the RACH to the PCU. This obviates RSL delay andincreasing RSL load. Depending on the RSL load, the RACH to Immediate Assignmentdelay 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 isnot in the USF active state, the timeslot broadcasts the corresponding UplinkStage Flag (USF), once the MS has moved to the pre-allocated timeslot.

S If the TS that was pre-allocated by the PCU is in the USF active state, the timeslotbroadcasts a valid USF continuously. Once an MS moves to the pre-allocatedtimeslot (after the MS receives the Immediate Assignment message), the MSreceives the assigned USF immediately. This is the earliest possible opportunityfor the MS to transmit in the uplink. The only delay between the ImmediateAssignment message and the uplink data transmission is the MS reaction time.

Refer to Technical Description: BSS Implementation (68P02901W36) for a full descriptionof the differences between the two access methods.


02 May 20033�40


68P02901W01-M

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 qualityin a highly loaded GSM network. These same benefits are realized when frequencyhopping is implemented on GPRS carriers. For GPRS, all packet data channelsassigned to a single MS are included in the same frequency hopping system, whichspecifies the frequencies over which the timeslots hop and the hopping sequence.

The principle of frequency hopping is as simple as changing the frequency used intransmission at regular intervals. It has been included in GSM specifications mainly inorder to deal with two specific problems which can affect transmission quality:

S Multipath fading.

S Interference.

Multipath fading immunity can be increased by exploiting its frequency selectivity. Byusing different frequencies, the probability of being continuously affected by fading isreduced, so the transmission link quality is improved. This improvement is much morenoticeable for slow moving MSs.

Interference coming from neighbour cells transmitting the same or adjacent frequenciescan be reduced by using frequency hopping. This is because calls are moving throughdifferent 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 thecharacteristics 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 characteristicsof 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 ofsignalling information and user data. The Gb interface allows many users to share thesame physical resource. To facilitate cost-effective transmission, the Motorola GPRSoffering also supports infrastructure sharing, which allows the operator to carryA interface (CS) and Gb interface (packet) traffic on a single E1 using the nailedconnections capability. These two features enable a cost-effective transmission solutionin a GPRS capable network. As GPRS traffic increases, it may become appropriate todedicate one or more E1 link lines to GPRS traffic and to accommodate this scenario, thenetwork 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 areestablished between the SGSN and BSS, where PDUs from many users are multiplexedon these virtual circuits. The virtual circuits may be multi-hop, and traverse a network offrame relay switching nodes. Frame relay is used for both signalling and datatransmission.


02 May 2003


68P02901W01-M 3�41

PCU load balancing and sharing (Gb and BTS)

This feature provides high reliability through efficient resource management. It alsomanages the movement of resources from one part of a BSS to another to meet varyingpeak capacity requirements in a network designed primarily for coverage.

The primary objective of this feature is to economically support the use of multipletimeslots per cell, with no delay penalty, in a BSS configured for coverage rather thancapacity. A coverage based GPRS network provides coverage over a large number ofcells, and assumes a low average throughput per cell. This feature allows a network toeffectively move or enable resources as needed throughout a BSS, to handle trafficpeaks.

Another objective of this feature is to provide high reliability. During periods when thedesignated resource is not required due to a failure, the spare resource can be used tomanage peak loads. This is accomplished by means of load sharing of E1 link lines andother key components within the BSS. A BSS/PCU can be configured to support amaximum capacity of 270 active timeslots.

In the case of link line or equipment failures, the BSS provides load sharing of thefollowing resources:

S E1 link lines on the BTS-BSC link.

S E1 links on the BSS-PCU link.

S PRP (RLC/MAC) boards within the PCU.

S 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 bysending a message containing the MSs logical identifier (TLLI), the current maximumbuffer depth (MS_Bmax) and the current buffer leak rate (MS_R). The flow of data isthen controlled on a per MS basis.

The BSS attempts a preset maximum number of times to send the message, in case it isnot acknowledged by the SGSN within the maximum time allowed. Successivemessages are sent a pre-defined delay (C) apart, unless the messages areunacknowledged.

The MS flow control functionality complies to GSM 08.18.

GSR6 (Horizon II)PCU description

02 May 20033�42


68P02901W01-M

PCU description

PCU purposeThe 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, BSSGPsignalling, routeing of signalling messages, Radio Link Control (RLC), and MediumAccess 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 tothe BSC and then over E1 to the PCU. At the PCU the RLC blocks are reformulated inLogical Link Control (LLC) frames and forwarded to the SGSN.

BSSGP signalling and NS signalling occur between the PCU and the SGSN using framerelay protocol. There is also signalling between existing functional process at the BSCsuch as the between the Base Station control Processor (BSP) at the BSC and the PCUvia 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 thefollowing GPRS MAC and RLC layer functions:

S LLC layer PDU segmentation into RLC blocks for downlink transmission.

S LLC layer PDU re-assembly from RLC blocks for uplink transmissions.

S PDCH scheduling functions for the uplink and downlink data transfers.

S PDCH uplink ARQ functions, including RLC block ack/nak.

S PDCH downlink ARQ function, including buffering and retransmission of RLCblocks.

S Channel access control functions, such as access requests and grants.

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

S Radio channel measurement functions, including received quality level, receivedsignal level, and information related to timing advance measurements.

The BSS is responsible for allocation and de-allocation of radio resources. A PCU framecan be transferred between the PCU and the CCU every 20 ms.

PCU managementThe PCU is managed, including software download and operations, by the OMC-R as anextension to the BSS. The OMC information destined for the PCU is passed through theBSC. The Common Management Information Protocol (CMIP) interface is modified onthe 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 GSL

X.25 64 kbit/sE1

OMC-R PCUBSC

GSR6 (Horizon II) PCU description

02 May 2003


68P02901W01-M 3�43

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

PSP DPROC(PRP)

BSC

PCU

CAB 1

CAGE 1

(LAPD) GDS

MSI

DPROC(PICP)

GSL

MMS 2

GBL

1 indicates automatically equipped devices, when a PCU is equipped. 2 indicates automatically equipped device, when an MSI is equipped.

NOTES:

(TRAU)GDS

MSI

MMS

(TRAU)GDS

GSR6 (Horizon II)PCU architecture

02 May 20033�44


68P02901W01-M

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, powersupplies, and processor boards.

There are four cPCI board types:

S The Master Processor (MPROC).

S The Bridge (PPB).

S 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 (theDPROC), but in the long term they may be different hardware platforms.

There is a single PCI Mezzanine Card (PMC) module currently planned, the dual E1PMC. 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 CPCIclock generation. It contains interface and BSSGP protocol functions, and is called thePCU 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 withthe PPB. It acts as PCI system host, and in conjunction with the PPB supports hotremoval control for all board slots. It performs resource allocation, fault management,and gateway management functions (such as control of allocation of cells to PRPboards). These functions comprise the PSP, which resides on the MPROC.

The MPROC requires a high-performance processor system such as the 266 MHzMPC750 with an 83 MHz bus for the memory subsystem. A minimum of 128 M bytes ofDRAM is supported, upgradeable to 256 Mbytes.

Bridge (PPB)

The bridge, also referred to as the PCI to PCI Bridge (PPB), allows an MPROC to belinked 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 thehost PROC access to all boards in the system. It supports control of hot swap for allboards, and a communication link between bridge boards to allow checkpointing andheartbeat messages between MPROC boards. This allows migration to a fully hot swap,redundant, high-availability system, including hot standby/load sharing between MPROCboards in the future, if required.

GSR6 (Horizon II) PCU architecture

02 May 2003


68P02901W01-M 3�45

DPROC

The DPROC boards are non-system slot boards that have two PMC sockets and canhost 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 theE1 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 PMCsockets can be used to support TRAU GDS devices. A single processor can support apool 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 anddata to/from these interfaces passes through the on-board processor. This processorhas different functions dependent on the interface type, but includes features such aspacket routeing on an incoming SGSN link, and packet scheduling to an outgoing SGSNlink.

DPROC (PRP)

The DPROC (PRP) is the processor where all of the radio related processing takesplace. Each of the GPRS channels is routed to a PRP, which performs all of theRLC/MAC processing, air interface scheduling, and frame synchronization on BTS facingchannels.

The performance required from this board is such that it supports a minimum of 30 activeair interface timeslots, with the ability to monitor another 90 timeslots. A future tripling ofthis capacity is envisaged. The PRP maintains synchronization to the air interface by theexchange of the PCU-CCU frames (which is transmitted even on inactive timeslots).

GSR6 (Horizon II)PCU architecture

02 May 20033�46


68P02901W01-M

E1 PMC moduleThe E1/T1 interfaces to both the BSS and the SGSN are provided by PMC modules thatreside on a PMC carrier board. The PMC board has a MPC 750 processor and two PMCsites. These PMC modules are currently available with dual E1 ports and an 860 PPCprocessor on�board.

This on�board processor is used for frame relay termination on the Gb link and containsa small process to route the Gb interface signalling (control) information to the Gbmanager on the MPROC. E1 links are also used to interface the PCU to the BSC fortransfer of signaling information via LAPD protocol, as well as serial user data in theremaining timeslots. The clock on the PMC module is free run and not synchronized toan external signal from E1/T1 interface. The memory on the PMC module is used for thecode object storage of the frame relay protocol as well as the buffers which arenecessary 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 TCLand is used to manage and control the PCU/BSC system. Multiple GSLs can be used tomanage and control the PCU/BSC system. Figure 3-14 shows a system where E1PMCs are used to connect the TDM data to the BSC. The MSIs used for these links canbe equipped in any chassis of a multi-chassis BSC system.

A PMC module can support only one of the following:

S (LAPD) GDS.

S (TRAU) GDS.

S Gb interface.

Additionally, if one span of the PMC module is used for a (TRAU) GDS, then the otherspan is unusable.

ChassisThe chassis houses a maximum of 16 cPCI boards, with the ability to support redundanthost processors. The power supply system is part of this OEM solution. The hostprocessor, redundant host processor, and their associated bridge boards occupy four ofthe slots, leaving 12 generic slots for the remaining boards. Hot removal of all boards issupported.

The PCU is an additional chassis that is collocated with any BSC that supports GPRSfunctionalityand interfaces to the BSC, utilizing E1 PMC modules on a DPROC (PICP)board. This requires corresponding Multiple Serial Interface boards (MSIs) to be presentin the BSC.

The chassis is a19-inch rack-mounting module supporting sixteen 6U PCI slots, four ofthese slots are taken by the two MPROC/bridge pairs for redundant systems. Thisleaves 12 generic slots that can be populated by any combination of PICP, and PRPboards with their associated PMC modules. It supports front access for all replaceablemodules, redundant/load sharing PSU system, and status LEDs. The interconnectcabling is routeable from the rear, front, or bottom of the chassis.

Fault toleranceThe PCU supports load sharing across the PRP, PICP, and E1 PMC. The hardware canbe N+M redundant (and would generally be equipped as N+1 when load sharing isactive), but software loads share across all installed boards, with any failures causing aloss in total capacity capability. The operator determines whether the hardware isprovisioned for greater capacity than required, such that failures do not affect the systemcapabilities.

GSR6 (Horizon II) PCU interfaces

02 May 2003


68P02901W01-M 3�47

PCU interfaces

Introduction to GPRS BSS interfaces

The Motorola GPRS BSS includes the:

S Base Station Controller (BSC).

S Base Transceiver Station (BTS).

S Operations and Management Centre-Radio (OMC-R).

S Packet Control Unit (PCU).

Figure 3-12 shows these components and their interfaces.

Figure 3-12 BSS functional blocks

RXCDR SGSN

PCU

BTS

X.25

Gb

Abis

Um

A

optionalKEY:

BSC

MS

OMC-R

The BSC supports the following interfaces as illustrated in Figure 3-12:

S BSC-BTS (Abis).

S BSC-OMC-R (X.25).

S BSC-RXCDR (A).

S BSC-PCU.

S PCU-SGSN (Gb).

This section defines the interfaces the PCU has with other elements of the GPRS.

GSR6 (Horizon II)

02 May 20033�48


68P02901W01-M

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 PCUand BTS. The GPRS Signalling Links (GSL) carry signalling information on 64 kbit/s E1timeslots 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 betweenthe BSC and BTS.

Another 16 kbit/s E1 TS or channel carries the TRAU-like framed data between the BSCand 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 CS4encoded PDCHs (see Figure 3-13).

Figure 3-13 Data and signalling paths between the PCU and MS

PCU BSC BTS MS

GDS16 kbit/s TS

16 kbit/s TRAU

UmPDCH

CS1, CS2,CS3 or CS4

GSL 64 kbit/s TS

LAPD

UmBCCHCCCH

RSL 16/64 kbit/s TS

LAPD

SIGNALLING SIGNALLING SIGNALLING SIGNALLING

DATA DATA DATA DATA

GSR6 (Horizon II)

02 May 2003


68P02901W01-M 3�49

Figure 3-14 provides more detail of the E1 physical links.

Figure 3-14 PCU to BSC connection utilizing E1 links (four shown)

The number of MSI linksneeded is dependent on thePCU capacity. All MSIs canreside in a single BSCchassis even in expandedsystems.

BSC

PCU

MS

I

MS

I

E1P

MC

E1P

MC

DP

RO

C(P

ICP

)

DP

RO

C(P

ICP

)

E1 LINKS

E1 LINKS

Gb interface

The Gb traffic, user data and signalling, can take different paths between the PCU andSGSN depending upon the needs of the voice and data networks. In all cases, the Gbtraffic is always carried over 64 kbit/s E1 channels. See Figure 3-15 for a summary of thethree connection methods. Option C, routeing a connection through the transcoder, is aconvenient way to bring GPRS traffic from multiple PCUs to a single SGSN.

Figure 3-15 Data and signalling paths between the PCU and SGSN

OPTION A: DIRECT

PCU

OPTION B: BSCPASS-THROUGH

OPTION C: BSC ANDRXCDR

PASS-THROUGH

ALL INTERFACES ARE Gb nx64kbit/s E1 CHANNELS LAPF

SGSN

PCU

BSC

SGSN

PCU

SGSN

RXCDR

BSC

GSR6 (Horizon II)PCU system and control functions

02 May 20033�50


68P02901W01-M

PCU system and control functions

System and control functions

The Packet Control Unit (PCU) performs:

S Radio functions.

S GPRS network functions.

The PCU has interfaces to:

S An OMC-R.

S BSC.

S SGSN.

Radio functions

The PCU is responsible for the following GPRS MAC and RLC layer functions, asdefined in GSM 03.64:

S LLC layer PDU segmentation into RLC blocks for downlink transmission.

S LLC layer PDU re-assembly from RLC blocks for uplink transmissions.

S PDCH scheduling functions for the up-link and downlink data transfers.

S PDCH up-link ARQ functions, including RLC block ack/nak.

S PDCH down-link ARQ function, including buffering and retransmissions of RLCblocks.

S Channel access control functions, such as access requests and grants.

S Radio channel management functions, such as power control, congestion control,broadcast control information.

S Interacting with existing BSS software for allocation/de-allocation of radioresources for GPRS.

S 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 relaynetwork can be point-to-point or an actual network. Signalling data, used for flow controland congestion management, is exchanged between the PCU and SGSN.

GSR6 (Horizon II) PCU system and control functions

02 May 2003


68P02901W01-M 3�51

PCU processes

There are three PCU functional areas:

S PRP processes.

S Gb processes.

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

S The DownLink Segmentator (DLS) segments LLC frames into RLC data blocks tobe transmitted over the air interface

S The UpLink Concatenator (ULC) concatenates RLC data blocks into LLC frames.

S The SYstem information Manager (SYM) builds and sends GPRS systeminformation messages over the BCCH.

S CCCH Paging Manager (CPGM) processes the paging messages coming from theSGSN to the BSC/BTS.

Gb processes

The Gb processes are:

S The Gb router (GR) routes incoming BSSGP PDUs from the SGSN to the relevantSW process in the PCU.

S The Flow control Buffer Manager (FBM) controls buffer capacity for each cell andeach mobile so that the incoming data from the SGSN matches the air throughput.

S The Gb Manager (GBM) manages the state of all cell and signalling links betweenthe PCU and the SGSN.

S The Gb Transmit Manager GTM) collects all UL frames from various ULCs andsends them on the appropriate NS-VC.

S The Network Service Tester (NST) periodically tests all alive NetworkService-Virtual Circuit (NS-VC) on a PICP board.

S The Frame Relay (FR) performs the frame relay protocol functions.

GSR6 (Horizon II)PCU system and control functions

02 May 20033�52


68P02901W01-M

02 May 2003


68P02901W01-M 4�1

Chapter 4

OMC-R Overview

GSR6 (Horizon II)

02 May 20034�2


68P02901W01-M

GSR6 (Horizon II) Introducing the Motorola OMC-R

02 May 2003


68P02901W01-M 4�3

Introducing the Motorola OMC-R

Definition of OMC-RA simplified GSM network is shown in Figure 4-1. The OMC-R supports the day to dayoperations and maintenance of network components within a GSM network. It alsoprovides a configuration interface to set up and modify the radio part of the system andto model the network to an interactive graphical map display.

NOTE The zoom feature may be used while working on-line to makethe text easier to read. For information regarding on-line helpclick on the on-line help icon located on the OMC-R front panel.The OMC-R front panel section can be found later in thischapter.

Figure 4-1 The OMC�R in a GSM system

MobileSwitching

CentreMSC

RemoteTranscoder

RXCDR

OMC-S

Base StationController

BSC

BTSBTS BTS

Packet Control UnitPCU

(optional GPRS interface)

Operation &Maintenance Centre

OMC-R

Base TransmitterStations

(Radio Part)

(Switch Part)

BTS

Mobile Stations(Phones)

BaseStationSystem

BSS

MSMS MS

GSR6 (Horizon II)Introducing the Motorola OMC-R

02 May 20034�4


68P02901W01-M

Naming conventions

The Operations and Maintenance Centre (OMC) designed to manage the radio part ofthe system is referred to as the OMC-Radio (OMC-R) in this manual to prevent confusionwith other types of OMC.

A Network Element (NE) is a specific term used to represent various network itemsincluding the BSS, RXCDR, MSC, OMC-R and OMC-S, but not lower level items, suchas SITE, PCU, DynetGroup and devices.

The BSS is a NE which includes the Base Station Controller (BSC) and Base TransceiverStation (BTS) functions and can also include a local transcoding function.

S site - normally refers to one or more physical pieces of equipment at a BSSlocation.

S 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.25communications protocol to exchange Operation and Maintenance (O&M) data with theBSSs and speech Transcoders (RXCDRs or XCDRs) via a Private or Public SwitchedPacket Data Network (PSPDN). The Transcoder (XCDR) is the digital signal processingequipment required to perform GSM�defined speech encoding and decoding. In terms ofdata transmission, the transcoder interfaces the 64 kbit/s PCM in the land network to the13 kbit/s vocoder format used on the Air Interface. The Remote Trancoder (RXCDR) isused when the transcoding is performed at a site away from the BSC, which is at or nearthe MSC. This enables 4:1 multiplexing in which the transcoded data for four logicalchannels is combined onto one 64 kbit/s link, thus reducing the number of links requiredfor 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 Q3interface) allows the OSI Processor to communicate between the Network ManagementCentre (NMC) and OMC-R for network configuration, events and alarms. The optional SAsoftware 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 fromthe OSI to the SMC.

DataGen is an optional UNIX platform which can either be run from the OMC-R LAN or instandalone mode. Datagen is designed to support large offline changes to a BSSconfiguration database which can then be downloaded to the BSS when required.

GSR6 (Horizon II) OMC-R network management functions

02 May 2003


68P02901W01-M 4�5

OMC-R network management functions

Fault managementFault management provides the facility to change the status of any device using faulthandling procedures. From the OMC-R, the GSM network operator can react to changesin 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 taskscan be performed from the map, the alarm window, Navigation Tree and throughcontained devices.

Event/alarm managementA primary function of an OMC-R is to maintain the quality of service to customers/usersof the GSM network by monitoring the state of Motorola equipment in the network. Eventor alarm messages containing information on the state of the network, devices and linksin the system are sent, via the X.25 network, to the OMC-R. These messages notify theoperators of any potential problems occurring in the network. There is the optional Alarmnotification via Paging feature which automatically notifies key personnel of certain alarmor state changes.

Operators can filter and select the way in which alarms are displayed and handled; forexample, alarms which have been handled, but not yet cleared, can be deferred. Toassist an operator in diagnosing specific events (and alarms) in the network, the NetworkAvailability Monitor provides an overview and allows trends to be identified. An optionalNetwork Health Analyst (NHA) provides a means by which operators can move frombeing purely reactive to a more proactive role by observing a combination of events,statistical information and configuration data that notifies them of network problemsbefore any faults are raised.

Performance managementPerformance management provides collection and reporting of network performancestatistics. The OMC-R collects, processes and stores performance statistics on thedifferent NEs in the network, and provides reporting facilities for the presentation andprinting of the processed statistics. These statistics can be then used to analyse networkperformance and aid long term planning.

Configuration managementThe OMC-R provides the configuration management facilities for a scaleable system thatcan cater for an expanding GSM network. The System Processor can be configured for avariety of expandable traffic channel capacities on the same basic platform. The OMC-Rsystem allows customers to expand their network operations and maintenance support inline with their business growth and provide orderly migration for existing users and rapiddeployment for new users. Network Expansion and Cell Parameter Import/Export underthe control of the OMC-R enables rapid and widescale network expansion. The OMC-Ralso includes the Call Trace function. Optional tools may also include the IntelligentOptimisation 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-Rprovides facilities to initiate uploads and downloads of NE operating software, or toback-up or download configuration databases for the different NEs. The OMC-R alsoprovides the facilities to reconfigure the operating parameters of NEs using the remotelogin 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 logicalconnections and devices.

GSR6 (Horizon II)OMC-R network management functions

02 May 20034�6


68P02901W01-M

Load management

Load Management forms part of the Configuration Management and provides theoperator with a central location to remotely load all the NEs with the latest compatibleversion of operating software. New software loads are installed at the OMC-R and laterdownloaded to the NEs under the OMC-Rs control.

GSR6 (Horizon II) The OMC-R in GSM network management architecture

02 May 2003


68P02901W01-M 4�7

The OMC-R in GSM network management architecture

Network hierarchyThe position of the OMC-R within the GSM network management hierarchy, is shown inFigure 4-2.

Figure 4-2 GSM network management architecture

NMC

OMC-ROMC-R

NE

PHYSICAL IMPLEMENTATION OF THE LOWER THREE LAYERS

FIVE-LAYER TMN MODEL (DEFINED IN ITU M.3010)

NETWORKMANAGEMENT

NETWORKELEMENT

MANAGEMENT

NETWORK ELEMENTLEVEL

SERVICESMANAGEMENT

BUSINESSMANAGEMENT

NE NE NE NE NE

Network levelsOperation and Maintenance (O&M) management of the BSS and RXCDR can beperformed at several network levels:

Local levelLocal level monitoring, where reconfiguration, and software loading can be performed byconnecting a personal computer to the BSC or RXCDR (Remote Transcoder).

Regional levelThe OMC-R provides facilities for performing functions on NEs at a regional level.Built-in alarm and event management, configuration management, and fault handlingfacilities enable operators at remote OMC-R sites to manage O&M in a consistent andstandardized manner. The OMC-R provides monitoring and control for a number of BSSsin a specific geographical area. The prime function of the OMC-R, is to maintain thequality of service to customers/users by monitoring the performance of the radioequipment. Procedures are provided by which the radio resources can be dynamicallyreconfigured, and faults rectified from a single remote location. Additionally, the OMC-Rprovides databases for O&M data and system performance statistics.

Top levelThe top level of network management is implemented by the Network ManagementCentre (NMC). An NMC could perform O&M functions at a network-wide level withOMC-Rs as its subordinates.

GSR6 (Horizon II)The OMC-R system

02 May 20034�8


68P02901W01-M

The OMC-R system

OMC-R content

The OMC-R system configuration is shown in Figure 4-3. It is suitable for GSM networkswith low-end (10k) to high-end (45k) traffic channels (TCHs). Each processor is acomplete UNIX system, comprising the following:

S A system processor.

S A database/memory to store configuration settings

S GUI clients(i.e. the Graphical User Interface used by operators ).

S One or more GUI servers.

S A laser printer.

The system processor

The system processor is a UNIX system that runs the OMC-R application software tohandle all O&M communications with the NE. It processes all incoming events, alarms,uploads/downloads, and performance statistics. It also processes the setting up ofremote login sessions to different NEs. The system processor contains a database basedon an INFORMIX Database Management System (DBMS), configured for storingperformance statistics and subscription lists, enabling operators to monitor incomingevents and alarms.

The system processor contains the Configuration Management Information Base (CMMIB) 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 isprimarily 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. TheGUI server handles the more intensive GUI processing tasks and network messagesfrom the system. The GUI client handles the operator display and data entry tasks andsends information requests to the GUI server. The GUI server responds by sending orreceiving information or by performing the required action.

Typically the OMC-R configuration contains several SPARCstation 5s, which run the GUIclients. The faster ULTRA or SPARCstation 20 can run either the GUI server or clientprocesses.

Optional processors

Optional processors, such as those for OSI stack, remote login, and DataGen can beincluded into the basic OMC-R configuration. The processors that can be used areSPARCstation 20s or ULTRAs. The Network Health Analyst (NHA) can be used on a SunEnterprise 3000 or 3500, and WWW Server on a SPARCstation 5.

GSR6 (Horizon II) The OMC-R system

02 May 2003


68P02901W01-M 4�9

Figure 4-3 Typical scaleable OMC-R system configuration

CONSOLE FOROMC-R SYSTEMADMINISTRATOR

GUI PROCESSORGUI

Applix

LaserPrinter

SYSTEMPROCESSOR

OMC-RApplicationSoftware

Lexmark Optra RN+printer (with software)

OMC-RDATABASE(DBMS)

GUI PROCESSORGUI

cm_mibGUI

LOC

AL

AR

EA

NE

TW

OR

K (

LAN

)

SUN SPARCstation 5*

SUN SPARCstation 5*

TO GSMNETWORK

X.25

System Processor

Sunlink X.25 package

SUN HSI/S card (4-port HSI / interface )

Workstation

Workstation

*Optional

WWW SERVERPROCESSOR (optional)

OSI PROCESSOR (G3)(optional)

Network Health AnalystPROCESSOR (optional)

SUN SPARCstation 5*

NHA processor*

SUN SPARCstation 20 orSUN Ultra 200E*

CMMIB

Ultra 5

Ultra 200E

GSR6 (Horizon II)OMC-R configuration summary

02 May 20034�10


68P02901W01-M

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 for45,000 TCHs with a maximum of 120 NEs.

The GUI interface is provided on a SPARCstation 5/20 machine or a SUN ULTRA. Oneof the high end machines must be configured as a GUI server. A second can beconfigured as a GUI server when the two will share the load of the clients forredundancy purposes should one server fail. Up to 10 GUI interfaces may be used in theOMC-R system. The GUI servers run the GUI sessions while the GUI clients run thedisplay software only. The total number of GUI sessions supported is 10, as on thestandard 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,000TCHs with a maximum of 120 NEs.

The GUI interface is provided on a SPARCstation 5/20 or SUN ULTRA 5/1 machine. Asecond 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 GUIsessions supported is 10, as on the standard OMC-R. Each machine can support oneGUI session.

Low-capacity TCH scaleable OMC-R

The minimum configuration of the scaleable OMC-R provides support for up to 5,000 or10,000 TCHs with a maximum of 15 NEs.

For very small systems the GUI interface is provided on an ULTRA 200E or ULTRA 5/1machine. 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 GUIsessions supported is 5. Each machine can support one GUI session.

GSR6 (Horizon II) The OMC-R user interfaces

02 May 2003


68P02901W01-M 4�11

The OMC-R user interfaces

User interfaces

The OMC-R has two user interfaces to operate the OMC-R system:

S The Graphical User Interface (GUI).

S Command line interface.

The OMC-R GUI provides a Graphical User Interface (GUI), based on the OpenSoftware Foundation Motif (OSF-Motif).

GUI interface

The GUI presents the user with a Front Panel displaying icons that represent all themodules of the OMC-R, shown in Figure 4-4. A smaller expert front panel, which doesnot have icon titles, is also available for experienced personal. The expert front panelprevents 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 networkmanagement functions. All maintenance, network reconfiguration, troubleshooting, andnetwork administration, apart from equipment repair and replacement, can be executedthrough a single interface.

Command line interface

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

GSR6 (Horizon II)The OMC-R user interfaces

02 May 20034�12


68P02901W01-M

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 handside of the GUI front panel. Figure 4-4 shows the OMC-R front panel and Figure 4-5shows the expert OMC-R GUI front panel.

Figure 4-4 The OMC-R GUI front panel

1

1615 14 11

9

13

42

8

56

7

10

1

3

12

Figure 4-5 The Expert OMC-R GUI Front Panel

GSR6 (Horizon II) The OMC-R user interfaces

02 May 2003


68P02901W01-M 4�13

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

GSR6 (Horizon II)The command line interface

02 May 20034�14


68P02901W01-M

The command line interface

UNIX-based utilities

UNIX-based utilities are provided to give additional network management functionality tothe OMC-R GUI in the following functional areas:

S Remote login.

S Synchronization of time with the OMC-BSS.

S Event management.

S Event log processing, searching and filtering event logs.

S Performance management.

S NE database management.

S System administration utilities.

GSR6 (Horizon II) The OMC-R in a GSM network

02 May 2003


68P02901W01-M 4�15

The OMC-R in a GSM network

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 moreNetwork Elements (NE or nodes), which may be a Base Station System (BSS), aRemote Transcoder (RXCDR), Mobile Switching Centre (MSC) or Cell Broadcast Centre(CBC).

Figure 4-6 The OMC�R in a GSM network

MS

MS

MS

MS

MS

RXCDR

MS

OMC-RMSC

BTS

BTS

BTS

BSC

BSSn

BTS BTS

BSC/BTS

BSS1

X.25

O&M DATA FROM BSS1, BSSn, &RXCDR

64 kbit/s

16 kbit/s traffic

VOICETRAFFICFROMBSS1 ANDBSSn

64 kbit/s

64 kbit/s

64 kbit/s

64 kbit/s

64 kbit/s4x16 kbit/s

64 kbit/s4x16 kbit/s

64 kbit/s

64 kbit/s

2 Mbit/s link 2 Mbit/s link

2 Mbit/s link

2 Mbit/s link

ÑÑÑ

CBC

X.25

MESSAGE INFO

2 Mbit/s

CBL

CBL

TRAFFIC TRAFFICO&M DATAO&M DATA

link

GSR6 (Horizon II)The OMC-R in a GSM network

02 May 20034�16


68P02901W01-M

OMC-R functions

The OMC-R performs the following functions:

S Direct management of BSS and RXCDR and the links between them.

S 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 datapackets sent to/from the NE.

S Monitoring of events and alarms, performing fault handling, NE re-configuration,NE software uploading and downloading, and performance data collection andreporting for all the NE under its control.

S Provides a centralized facility for network management of up to 120 NEs with up to45,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 trafficchannels (voice) between the BSS and MSC. The O&M data packets are routed betweenthe 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/sO&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 areaas the MSC. This is the most efficient arrangement, as the primary feature of the RXCDRis that it converts the 64 kbit/s PCM output of the MSC to a 16 kbit/s rate required fortransmission over the air interface (between the BSS and the MS). Thus, four 16 kbit/schannels 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 obviouscost savings.

Configurations

A BSS consists of a Base Site Controller (BSC) and one or more remote BaseTransceiver Stations (BTS). Every BTS must be physically connected to its controllingBSC using a 2 Mbit/s link. A BTS can also be located in a BSC cabinet, thus creating acollocated BSC/BTS, usually connected using a LAN. A BSS configuration may have allBTS directly connected to the controlling BSC (spoke connection) or the BSS may beconnected via another BTS (daisy chaining). A BTS may also have more than oneconnection to its controlling BSC for redundancy. The GPROC2 (second generationprocessor board) allows the BSC to support 100 sites.

GSR6 (Horizon II) BSS and RXCDR configuration (SITES)

02 May 2003


68P02901W01-M 4�17

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 Sites1 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 alsoprovides the interface between the MSC and the remote BTS sites.

S Remote BTS site � This site forms the remote part of a BSS which is controlled bythe 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

2 Mbit/s TERRESTRIAL OR MICROWAVE LINK TO/FROM RXCDR

REDUNDANT LINK � 2 Mbit/s TERRESTRIAL OR MICROWAVE LINK

2 Mbit/slink

SITE 0 (BSC) SITE 1 (BTS) SITE 2 (BTS) SITE 3 (BTS)

MSIBOARD

2 MMSPORTS

RXCDR configuration

An XCDR placed at the MSC is known as a Remote Transcoder (RXCDR), and isregarded as a separate NE (or node). Sometimes the transcoding functionality is locatedwithin a BSC. In the example above, (Figure 4-7), the transcoding hardware is regardedas a subset of the BSS SITE 0 configuration.

GSR6 (Horizon II)NE device containment

02 May 20034�18


68P02901W01-M

NE device containment

Containment relationship

There is a containment relationship between each entity in the GSM Network that ismodelled 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 entityknown as containees. For example, an MMS (the Multiple Serial interface link) iscontained within an MSI (the Multiple Serial Interface board), which, in turn, is containedwithin a SITE. This containment relationship is used for logical naming, configurationpurposes 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 SITEand up to 100 SITEs in a BSS. An instance of an MMS can be uniquely identified to anMSI/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 isthe parent MSI card, the second refers to the port number and the third is not required.

GSR6 (Horizon II) Site configuration

02 May 2003


68P02901W01-M 4�19

Site configuration

CELL resources

In the Motorola implementation of GSM, a single BTS consists of one or more cabinetsand controls one or more CELLs. The Motorola term CELL is equivalent to the GSM termBTS, since Motorola BTS sites can contain more than one cell. GSM requirementsspecify one cell per BTS.

The different related resources of a CELL configuration are shown in Figure 4-8.

Figure 4-8 Site configuration

SITE

CELL

Neighbour HandoverControl

PowerControl

DRI Group RTF Group

DRI RTF

RadioFrequency

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

S Receive Transmit Function (RTF) Groups, which contain a number of (RTFs).

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

S CELLs.

GSR6 (Horizon II)DRI/RTF groups - transceiving

02 May 20034�20


68P02901W01-M

DRI/RTF groups - transceiving

Transceiving functionality

Motorola has implemented transceiving functionality using the DRIs and RTFs. Thisprovides the radio carrier which, in a GSM digital system, consists of eight TDMAtimeslots. These digital channels carry speech and various control data. One of the moreimportant of these control channels is the Broadcast Control Channel (BCCH). EveryCELL 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 asfunctions rather than devices as they are a logical representation of the traffic, ratherthan relating to a physical piece of hardware. An RTF contains eight digital channels, onefor each timeslot on the air interface.

There are two types of RTF:

S BCCH (one of the timeslots is used as a BCCH).

S Non-BCCH.

To provide redundancy of RTF traffic, it is possible to specify two routes or PATHs thatare potentially able to carry the RTF traffic from the BTS to the BSC. These are calledthe Primary and Secondary PATHs. If two PATHs are available, the shorter will be theconnected PATH and the longer will be the redundant PATH. If the PATH availabilitychanges and a shorter PATH becomes available to the RTF, then a switchover will occurso that the RTF starts to use this new PATH. Refer to Physical links - PATH for moredetails 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 RTFLimit, and is set by Motorola engineers during staging. Each OMC-R has a thresholdRTF 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 transceivingfunctionality to the CELL.

GSR6 (Horizon II) CELL configuration

02 May 2003


68P02901W01-M 4�21

CELL configuration

Logical devices

A CELL contains the following logical devices:

S Neighbour.

S Handover control.

S Power control.

Handover control

Handover means switching a call from a channel in a given CELL, to another channel ineither 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 neighborbasis. The adaptive handover methodology allows handovers to be recognized based ona cumulative area rather than a vote. At each measurement report the cumulative area isupdated and compared to a cumulative trigger. If the power budget (pbgt) dips below thehandover margin temporarily the cumulative area will be decremented by the differenceand not reset. If this cumulative area is then greater than the cumulative pbgt trigger, aneed for a handover will be recognized. The cumulative area is based on either a percell or a per neighbor basis as decided by the operator.

Handover control, is the functionality required to detect and effect a handover, in order tomaintain acceptable service to the user.

Handover detection algorithm

There are a number of parameters used to detect when a handover should occur. Anumber of factors are input to this algorithm. These factors are as follows:

S Uplink and downlink receive signal strength.

S Uplink and downlink receive signal quality.

S Power budget.

When a power budget handover is enabled, the call will hand to a neighbouring cellat the point where a lower power budget can be achieved (both the MS and theBTS can reduce their TX power).

S Interference.

S Distance (between the BTS and the MS).

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

There are thresholds supported for each measurement and when a threshold isexceeded, a handover may occur.

GSR6 (Horizon II)CELL configuration

02 May 20034�22


68P02901W01-M

Power control

In order to reduce Radio Frequency interference in the network, and increase battery lifeon MSs, it is desirable to run all the BTSs and MSs in the network at the minimum TXpower that provides adequate rxqual (quality) and rxlev (level) for a call.

Power control is the functionality to detect and effect the modification of transmissionpower, 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 powercontrol algorithm. In the event that the power level exceeds the upper level threshold thealgorithm will allow the decrement step size to change dynamically based on theproximity to the upper power threshold and will be used to reduce the power level to oneunder the threshold level. The calculations will be made for both uplink and downlinkpower 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.

S Uplink and downlink receive signal quality.

There are thresholds supported for each measurement. When a threshold is exceededtransmission power modification may occur.

GSR6 (Horizon II) Links in a GSM network: overview

02 May 2003


68P02901W01-M 4�23

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

S A link to a BSS, is a link to the SITE configured as a BSC within the BSS.

S Similarly, links within a BSS, those between the BSC and BTSs and between oneBTS and another, are all links between SITEs.

SITE link requirements

Every SITE must contain at least one Multiple Serial Interface (MSI) board (NIU forM-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.

S Logical links.

GSR6 (Horizon II)Physical links - PATH

02 May 20034�24


68P02901W01-M

Physical links - PATH

Connection

A physical link between two SITEs is made by connecting one MMS port of an MSI (NIUfor M-Cell) card on one SITE, to one MMS port of an MSI (NIU for M-Cell) card onanother 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 directlyconnected to the OMC-R, or via the RXCDR or MSC.

S Similarly, every BSC must be physically connected to its controlling MSC. A BSCmay be directly connected to its controlling MSC or it may be connected via anRXCDR.

S Every BTS must be physically connected to its controlling BSC. A BTS may bedirectly 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 connectionto its controlling BSC giving load sharing and redundancy.

PATH devices

A PATH device defines the connectivity between a BSC site and BTS sites under itscontrol. It is a logical representation of a 2 Mbit/s route between the BSC and adestination BTS. This connectivity specifies the physical route from the BSC, throughintermediary BTSs to the destination BTS. A PATH may contain a route through amaximum of 10 BTS sites. The connection information between any two sites consists ofan 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 andBTS 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

BTS 3

BTS 2

BTS 1

BSC 0

PATH 1 = A-B-CPATH 2 = D

D

C

B

A

BSS

GSR6 (Horizon II) Logical links

02 May 2003


68P02901W01-M 4�25

Logical links

Introduction to linksThe 2 Mbit/s physical links in the GSM network, are configured to carry (as well as thevoice traffic channels) many logical links containing signalling information or O&M data.These links are monitored by the OMC-R.

Types of linkThe 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. Theseare 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 orRXCDR for transferring network management (O&M) data. Up to four OML links can beconfigured 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 BSCand the MSC. In the Motorola system, when local transcoding is used, this is a physicalconnection between the BSC and the MSC. When a Remote Transcoder is used, thelogical MTL is made up of two physical parts; the connection between the BSC and theRXCDR and the connection between the RXCDR and the MSC.

S When more than one MTL is configured between the BSC and MSC, both loadsharing and redundancy are present. Up to 16 MTLs may be configured betweena 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 remoteBTS. The timeslots used, are chosen automatically by the Motorola software. This is toensure that new BTSs, added to the network, can be communicated with on defaulttimeslots.

S Each RSL link is associated with a PATH. It is possible to have multiple (up toeight) 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 thedaisy chain connection in the BSS. The two RSLs provide both load sharing andredundancy functions for the signalling link.

RXCDR to BSC Link (XBL)An XBL link may be configured between the BSC and the RXCDR for exchanginginternal Fault Management (FM) data between them. An Enhanced XBL (EXBL) willallow generic messaging between the RXCDR and BSC in support of current and futureoperator 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 withother necessary information such as repetition rate and number of broadcasts.

GSR6 (Horizon II)Logical links

02 May 20034�26


68P02901W01-M

RequirementsFigure 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 orXBL/EXBL (depending on how it is connected to the MSC) and at least one RSLfor each remote BTS under its control.

S An RXCDR will always contain at least one OML, and at least one XBL/EXBL.

S A BTS will always contain at least one RSL.

Figure 4-10 The different logical links in a GSM network

MTL2

RXCDR

OMC-RMSC

BTS2

BTS1

BSC

BTS2

X.25

2 Mbit/s link

2 Mbit/s link

2 Mbit/s link

ÑÑÑ

ÑÑÑ

RSL11

(BTS1 to BSC )

OML1

ËËXBL1

OML2

OML2

ËËËXBL2 OML1

ÑÑ

ÑÑ

MTL2

MTL1

RSL22ÀÀ

RSL12

(BTS1 to BSC )

ÀÀ

RSL21

(BTS2 to BSC)

MTL 1

CBL:BSC�CBC Link

(MESSAGE INFORMATION)

BTS3

BSC/BTS1

VOICE TRAFFIC

VOICE TRAFFIC

2 Mbit/s link

Different logical links:ÑÑÑÑ

ËËËËÀÀÀÀ

OML3

RSL22

(BTS2 to BSC) ÀÀ

ÀÀÀ

RSL12

ÀÀÀ

RSL11

ÀÀÀÀÀ

2 Mbit/s link

ÍÍVoice Traffic

ÍÍCBL

CBCÍÍÍÍ

CBL CBC

ÀÀ

MTL:MSC�BSC LINK

(C7 SIGNALLING INFORMATION)

OML:OMC-R�BSC LINK

(O&M DATA)

XBL:RXCDR�BSC LINK

(FAULT MANAGEMENT DATA)

RSL:BTS�BSC LINK

(SIGNALLING INFORMATION))

GSR6 (Horizon II) OMC-R connection to the network

02 May 2003


68P02901W01-M 4�27

OMC-R connection to the network

Transferring data

For every BSC in the network, one or two timeslots (64 kbit/s) on a 2 Mbit/s link is usedto carry the O&M data between the BSC and RXCDR. All the timeslots from the differentBSC-RXCDR links are grouped onto one or more 2 Mbit/s links by the RXCDR or theMSC. 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 andOMC-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 cansupport up to 256 virtual circuits. There are four types of virtual circuits that can be madeon the OML:

S Event Interface (EI) transfers data packets (events and alarms), plus theOMC-BSS message from a NE (e.g. a BSS) to the OMC-R. The circuit is made bythe NE calling the OMC-R.

S Bootload (BL), also called Download, transfers BSS software and BSS databasesto the NE. The circuit is made by the NE calling the OMC-R.

S Upload (UL) transfers BSS database back-ups and raw statistics (performancedata) to the OMC-R. The circuit is made by the OMC-R calling a NE.

S Remote login (RL) provides sessions for transfer of BSS GUIcommands/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 theOMC-R. Normally two connections are set up for EI and BL. If a given port is notworking, then the packet switch / multiplexer will switch to a different port. The ULcircuits 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.

GSR6 (Horizon II)OMC-R connection to the network

02 May 20034�28


68P02901W01-M

Figure 4-11 Communication between the OMC-R and other network elements

OMC-RSYSTEMPROCESSOR

O&M DataPackets

ÎÎÎÎ

ÑÑÑÑÑ

Packet switch /multiplexer

X.21 connections (two to seven physicalconnections)

ÑÑÑÑÍÍÍÍÍ

ÎÎÎÎ

ÑÑÑÑÑ

Ñ

ÑÑÑÑÑÍÍÍÍ

NAILED CONNECTIONS(ONE PER O&M TIMESLOT)

BSSn

64 kbit/sO&MTIMESLOT

2 Mbit/s link

64 kbit/sO&MTIMESLOT

2 Mbit/s link

2 Mbit/slink

ÑÑÑÑ

RXCDR

ÎÎÎÎÎÑÑÑÑÍÍÍÍ

BSS1

BSS2BSS3

BSS4

OMC-R

X.25

RXCDR

ÑÑÑÑ

GSR6 (Horizon II) Operations and maintenance of a BSS or RXCDR

02 May 2003


68P02901W01-M 4�29

Operations and maintenance of a BSS or RXCDR

Simplified network

A simplified network showing some of the hardware devices in the different sites, and thelinks between them, is shown in Figure 4-12. BSS1 from Figure 4-11 is used as theexample BSS.

Figure 4-12 Simplified GSM network showing devices and links at BSSs

RSLLINKS

MSI

MSI

MTLLINK

XBLLINK

RXCDR

BTS

COLLOCATEDBSC/BTS

BSS1: SITE0

X.25

MSI MSI

MSI

DRCU

MCU

NIU

TCU

BSS1: SITE1 BSS1: SITE2MCell

BTS

RXCDR:SITE0

KSW

KSW

XCDR

BSS

KSW

MSI

DRCU +

DRI

OML

DRI

OMC-R

MSC

+

GSR6 (Horizon II)O&M information flow between OMC-R and NEs

02 May 20034�30


68P02901W01-M

O&M information flow between OMC-R and NEs

Summary of information flowA summary of the information flow between the OMC-R and other NEs (e.g. RXCDR andBSS) is shown in Figure 4-13. The primary function of the OMC-R is to monitor thehealth of the radio network.

Figure 4-13 Information flow between the OMC�R and BSSs

OMC-R

1. EVENTS & ALARMS2. NE RESPONSES TO GUI COMMANDS3. PERFORMANCE DATA (RAW STATISTICS)4. NE DATABASE UPLOADS

NE TO OMC-R

1. GUI COMMANDS (VIA GUI OR REMOTE LOGIN) � FAULT HANDLING � SITE CONFIGURATION � SITE RESETS2. SOFTWARE and NE DATABASE DOWNLOADS3. NE DATABASE DOWNLOADS

OMC-R TO NE

NE NE NENENE

Information flowAll events (changes of state of a hardware device, link, or function) and alarms (changeswhich could be service affecting) are sent to the OMC-R, via the RXCDR and the X.25packet switch, where they are processed into a standard format. The alarms can beconfigured to update a network map, which will give the operator a visual warning bycausing the appropriate BTS or BSC to flash. The alarms or events can also bedisplayed on the operator terminals, within different windows, depending on how thenetwork operator (or OMC-R administrator) has configured them.

The RXCDR contains several of the same devices, links and functions as the BSS, andgenerates events and alarms in the same way.

The network operator then takes action to handle the reported fault, by remote logging into 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 onlyone software load, for example BSSGSM 1.6.0.x. When loading a BSS, the entire loadis first sent to the BSC which then distributes the appropriate load objects to theconfigured BTSs. A copy of the active BSS load is stored at the OMC-R as is a copy ofthe previous version of the BSS software. These software loads must be compatible withthe load installed on the OMC-R. The RXCDR receives the same software load as aBSS, it just implements a different part of it.

Each BSS and RXCDR contains an operational database, in which the configuration datafor all the devices and links in the SITES within the NE is stored. A backup copy of theactive database is kept at the OMC-R.

Performance measurements for the different BSS and RXCDR are periodically routedevery 30 or 60 minutes to the OMC-R as raw statistics in a data file. This data is storedin a database at the OMC-R, and processed into statistics which provide valuableinformation for efficient network management and planning.

GSR6 (Horizon II) OMC-R system configuration

02 May 2003


68P02901W01-M 4�31

OMC-R system configuration

Motorola OMC-R

A typical hardware configuration of a Motorola OMC-R, is shown in Figure 4-14.

Figure 4-14 An example Motorola OMC�R system configuration

X.25 PACKET SWITCH

Laser Printer

X.25 INTERFACE

TO GSMNETWORK

OMC-R GUI processors � Operator Workstations + GUI ServerOSI processor(optional)

LOCAL AREANETWORK (LAN)

X.25PACKET SWITCH& MULTIPLEXER

ÓÓÓÓÓÓÓÓ

ÓÓÓÓÓÓÓÓÓÓÓÓ

OMC-R SYSTEMPROCESSOR

Typical hardware configuration

An OMC-R comprises a central System Processor and several GUI processors. Eachprocessor is a complete UNIX system which provides a GUI interface presented on acolour monitor. The system is connected via a LAN allowing all workstations access to alaser printer. The GUI server is a server that allows the GUI processes to be run on afast machine while using the slower machine for the display process.

NOTE Some systems may be configured differently; for specificinformation the OMC-R Bill Of Materials (BOM) should beconsulted.

GSR6 (Horizon II)Communications handling

02 May 20034�32


68P02901W01-M

Communications handling

Communications software

The OMC-R communications software, provides control and support for the protocolstacks which interface the OMC-R with the following:

S Internal OMC-R communications:

� TCP/IP.

� Ethernet.

� X.11.

S The NEs in the GSM network - X.25.

The X.25 software is loaded in the System Processor, and the X.11 driver software isloaded in the GUI Processors. The remaining communication software is shared betweenthe two processors. The operating processes are linked between machines byInterprocess Communication (IPC). The OMC-R network can be extended to includefurther GUI Processors, or secondary GUI servers, connected either locally or via a WideArea Network (WAN). Bridges and gateways can also be used to connect to othercomputer systems such as an NMC, or other OMC-Rs.

GSR6 (Horizon II) Packet switch/multiplexer

02 May 2003


68P02901W01-M 4�33

Packet switch/multiplexer

Connections

The OMC-R is connected to the GSM Network, to receive O&M data using a packetswitch / multiplexer, (as shown in Figure 4-15). The Packet Switch makes a maximum of256 x X.25 virtual circuits available for the exchange of O&M data between the OMC-Rand the NEs.

Figure 4-15 Example Packet switch / multiplexer connections

HSI Connections

2 Mbit/sLinks

Packet Switch / multiplexer

OMC-Rsystemprocessor

System processor

2 Mbit/sLinks

HSI Card

Packet switch

The connection between the System Processor and the Packet Switch could be direct orconnected through a Private eXchange Public Data Network (PXPDN).

GSR6 (Horizon II)O&M network traffic capacity

02 May 20034�34


68P02901W01-M

O&M network traffic capacity

Peak traffic capacities

The System Processor supports the following O&M peak network traffic capacities:

S 100 x X.25 packets per second, with a packet length of 128 bytes, aggregate.

S 100 kbit/s aggregate.

S 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 NEsvia the 256 x X.25 virtual circuits.

GSR6 (Horizon II) OMC-R system processor

02 May 2003


68P02901W01-M 4�35

OMC-R system processor

Introduction to the system processor

The hardware configuration of the system processor (for example, the number of CPUprocessors, memory, disk capacity) can be varied depending on whether thelow-capacity, mid-capacity or high-capacity TCH OMC-R is chosen. Thus, the scaleableOMC-R provides easy and cost effective expansion/de-expansion from low-capacity TCHthrough mid-capacity TCH to high-capacity TCH configuration. The softwarerequirements 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 onthe 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

OMC-R System Processor

System Processor

4 (or 7) x 2.1/4.2 Gb disks(Internal and External)

SUN HSI/S card (4-portHSI interface)

GraphicsHead

OMC-R System Processor

4 (or 8) x 9.1 Gb disks (Internal)

GraphicsHead

Or E3500

E3000

The system processor running Solaris 2.5.1 handles hardware failure by rebooting onfailure, and configuring out the broken hardware.

Connection to GSM network

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

OMC-R application software impact

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

GSR6 (Horizon II)OMC-R system processor

02 May 20034�36


68P02901W01-M

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 ScaleableOMC-Rlow-end

ScaleableOMC-R

midrange

ScaleableOMC-R

midrange

ScaleableOMC-R

high-end

RTFs supported 714 1430 4285 6000

NEs supported 15 30 120 120

Total GUI sessions supported 5 10 10 10

Dial-up sessions per GUIprocessor

1 1 1 1

Total remote dial-up sessions 2 2 2 2

Remote login sessions 6 6 20 30

Simultaneous downloads 6 6 12 12

Simultaneous uploads 4 4 16 32

Sustained event rate 8 alarms+2 statechanges

8 alarms+2 statechanges

12 alarms+3 state

changes

12 alarms+3 state

changes

Maximum event burst 20 events/sover 20

mins

60 events/sover 20

mins

60 events/sover 20

mins

60 events/sover 20

mins

External interface (OMC-R to BSS)

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

GSR6 (Horizon II) OMC-R system processor

02 May 2003


68P02901W01-M 4�37

Configuration

The configuration of the system processor is shown in Figure 4-17. It uses a Solaris 2.5.1UNIX operating system and contains a DataBase Management System (DBMS) fromInformix (which is configured for storing the performance statistics). There is an EventManagement Information Base (EM MIB) that contains the incoming events and alarmswhich update the map displays to present the operator with visual indication of alarms inthe network. The System processor also contains the CM MIB which holds theconfiguration data required to run the network maps.

Figure 4-17 System processor software configuration

CONSOLEFORSYSTEMADMINISTRATOR

SYSTEMPROCESSOR

OMC-R GSMGSR 4

OMC-R DATABASE

[Informix]

Event Log ETHERNETCONTROLLER

SOLARIS(2.5.1)

X.25HANDLER

Applix

CMMIB cm_mib

GUI

GSR6 (Horizon II)OMC-R GSM application software: overview

02 May 20034�38


68P02901W01-M

OMC-R GSM application software: overview

OMC-R processesThe functional software areas of the OMC-R are split between the OMC-R systemprocessor and the GUI processor. The processes of the OMC-R application softwareinstalled on the OMC-R system processor are shown in Figure 4-18. The operator isprovided with a front end to all these processes at the OMC-R GUI, and additional frontend functionality is provided by command line utilities.

Figure 4-18 OMC-R GSM (System processor) software components

OMC-R (System Processor)

Event/AlarmManagement

ConfigurationManagement

SW LoadManagement

PerformanceManagement

EventInterface

RemoteLogin

DeviceManagement

System processor software elements

The software elements that constitute the system processor software, perform thenetwork element O&M management tasks, provide database storage facilities, andprovide the interface to the network elements via the X.25 network. The OMC-R systemprocessor software elements are as follows:

Configuration management

Configuration management allows the operator to perform network configurationtasks, and to maintain all details of the network configuration at the OMC-R.

Performance management

Performance management controls the collection, administration, processing, andstorage of NE performance statistics.

Software load management

Load management provides a facility for uploading and downloading NE softwareloads, and NE operational databases. It also provides a means of managingmultiple copies of software loads for back-up purposes.

Event/alarm management

Event/Alarm management provides a mechanism at the OMC-R for alarmsurveillance. It manages events and alarms routed to the OMC-R from other NEs,or generated within the OMC-R.

GSR6 (Horizon II) OMC-R GSM application software: overview

02 May 2003


68P02901W01-M 4�39

Remote login

The remote login software manages the X.25 connection for remote login tonetwork elements from the OMC-R. Remote login is a means by which theoperator performs configuration management, fault management, and someperformance 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/AlarmManagement functional software.

Device management

Device management allows the operator to perform fault management andconfiguration management at the OMC-R. The OMC-R supports most hardwaredevices and software functions located at the remote network elements.

GSR6 (Horizon II)UNIX: Solaris 2.5.1 operating system

02 May 20034�40


68P02901W01-M

UNIX: Solaris 2.5.1 operating system

Platform

The SUN system processor operates under the Solaris 2.5.1 operating system. Thisprovides the platform for the OMC-R software applications and provides facilities forsystem 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/Intranetconnectivity.

S A system offering a scaleable, secure and reliable operating environment.

Features

The Solaris 2.5.1 release contains several 64-bit features, including KernelAsynchronous Input/Output (KAIO), which facilitates the fast asynchronous transfer oflarge amounts of data between memory and disk.

Included with this release is the Common Desktop Environment (CDE). This providesusers with a flexible open user environment that has a common look and feel across allmajor UNIX desktops. This environment allows transparent access to network resources;and allows frequently used UNIX commands to be iconized. It is also possible to dragand 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 provideautomated, high performance backup, recovery and storage management servicesto machines on the network.

S Solstice backup provides simple centralized administration, through a single unifiedview of the entire data management operation from any point on the network.Intuitive user interfaces simplify administrative tasks such as configuring clientsand servers, and setting up backup schedules for file systems and databases.

Solstice AdminSuite 2.3

Solstice AdminSuite software provides an integrated collection of graphical userinterfaces 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 UNIXsystem.

GSR6 (Horizon II) The OMC-R database

02 May 2003


68P02901W01-M 4�41

The OMC-R database

RDBMSThe OMC-R database, maintained at the system processor, uses an industry standardRelational Database Management System (RDBMS) known as INFORMIX. The DBMSmanages access to its own stored data and provides its own data protection. It is madeup of a PM sub-schema and an EM sub-schema. The PM sub-schema is used for storingprocessed performance statistics from the GSM Network, while the EM sub-schemastores the subscription lists used to subscribe to incoming events and alarms (seeFigure 4-19).

Database schema: definedThe OMC-R database may be thought of as a centralized data store for data that willneed to be further manipulated, either by system users or other OMC-R applicationareas. A database schema is a data model of a precise, complete definition of the datato 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 theirphysical structure cannot be altered, only their contents can be manipulated.

Figure 4-19 OMC-R database - database schema breakdown

PM SUB-SCHEMA

EM SUB-SCHEMA

RAWSTATISTICS

TABLES

NETWORKCONFIGURATION

TABLES

PM REPORTTABLES

EM SUBSCRIPTION LISTS

Database sizeThe 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 incase of hardware failure.

Applications and utilitiesThe management of the OMC-R database is accomplished using INFORMIX-OnLineutilities and OMC-R applications built around them. The OMC-R database supports thefollowing applications:

GSR6 (Horizon II)The OMC-R database

02 May 20034�42


68P02901W01-M

Structured Query Language (SQL) and Applix access for customreporting

SQL and Applix are industry standard languages, which can be used to writeapplications 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 ofthe OMC-R database. This avoids halting the OMC-R during routine back-upoperations.

GSR6 (Horizon II) The SPARCstation configuration

02 May 2003


68P02901W01-M 4�43

The SPARCstation configuration

Running the OMC-R GUIULTRA 5/1 and SPARCstation 20/5s are primarily concerned with running the OMC-RGUI. Typically the OMC-R configuration contains two ULTRA 5/1s or SPARCstation 20sand several SPARCstation 5s. One of the ULTRA/SPARCstation 20s machines must beconfigured as a GUI Server. A second can be configured as a GUI server or the systemprocessor can fulfil this GUI server role. Two GUI servers are the preferred arrangementand each will support half of the GUI clients. This arrangement allows system operationto continue should one of the GUI servers fail. The ULTRA machine configured as a GUIserver allows the slower SPARCstation 5 machines to run the GUI display tasks while theserver runs the GUI processes.

Each SPARCstation is a complete UNIX system, which runs the same GUI version. Atypical configuration is shown in Figure 4-20.

Figure 4-20 OMC-R SPARCstation configuration

GUI

GUI

GUI

GUI

SPARCUltra 5/1

GUI

GUI SERVER

TO SYSTEM PROCESSOR

LOCAL AREA NETWORK (LAN)

GUI

SPARCUltra 5/1

GUI CLIENT

GUI CLIENT

GUI CLIENT

GUI CLIENT

SPARCstation 5SPARCstation 5/10/20

SPARCstation 5 SPARCstation 5

GUI SERVER

The network file systemThe OMC-R GUI expects all the SPARCstations to be configured as standalone NFS(Network File System) machines. This configuration allows each SPARC some degreeof independence while still allowing resources to be shared.

LAN configurationsThe SPARCstation 5s execute the display process and function as operator workstations.The OMC-R GUI software is made accessible over the LAN by configuring theSPARCstations in the following way:

S An ULTRA 5/1 or SPARCstation 20 is installed as a GUI Server to theSPARCstation 5s.

This configuration allows the use of slower, older machines and the OMC-R GUI is madeaccessible to the 5s through NFS.

GSR6 (Horizon II)The SPARCstation configuration

02 May 20034�44


68P02901W01-M

Other configurations

Other network configurations may also exist, such as a GUI processor configured to runthe OMC-R GUI from a remote site. In networks containing two OMC-Rs, a GUIprocessor in the local OMC-R is configured to monitor a remote OMC-R during the nightshift (the local OMC-R is known as the night concentration centre).

GSR6 (Horizon II) GUI processor

02 May 2003


68P02901W01-M 4�45

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 machinesmount the display software from the GUI server. The total number of GUI sessionssupported is 10, as on the standard OMC-R. Each processor will support one GUIsession.

An example of a GUI processor hardware configuration is shown in Table 4-3. The GUIprocessor 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.1Solaris 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

GSR6 (Horizon II)The network status summary (NSS) feature

02 May 20034�46


68P02901W01-M

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 performnetwork management functions to ensure that the network operates efficiently, and toensure that the service to the customer is maintained. The OMC-R acts as a centralcollection point for measurement data used in the analysis of current performance andfuture planning of the network.

Features

The NSS features are as follows (refer to Figure 4-22):

S Network maps.

S Alarms icon.

S Alarm summary.

Figure 4-22 The network status summary options on the GUI front panel

Launches networkmaps

Incoming alarmsindicator

GSR6 (Horizon II) The CM MIB

02 May 2003


68P02901W01-M 4�47

The CM MIB

Description of the CM MIB

The system processor contains the CM Management Information Base (CM MIB) thatholds all the configuration data needed for the network maps of the OMC-R GUI and forcell parameter optimization. Information in the CM MIB includes lists of the various typesof nodes in the GSM network, with their attributes and interconnections, as well as lists ofmaps containing nodes and connections on each map. All the GUI processors which runthe NSS feature, communicate with the CM MIB using an internal process calledcm_mib.

Populating the CM MIB

The CM MIB can be populated with NE data by selecting:

S Audit.

or

S Detailed View Forms (for each object).

GSR6 (Horizon II)GUI Client - SPARCstation 5

02 May 20034�48


68P02901W01-M

GUI Client - SPARCstation 5

Software configuration

The Sun Microsystems SPARCstation 5s (the operator workstations) displays the GUIdata. This GUI client may be installed on either the System processor, or on one of theSPARCUltra 5/1 stations. In all cases the OMC-R GUI Client software is executed on thelocal SPARCUltra or SPARCstation 5. One of the SPARCUltra machines is alsodesignated as a GUI server to half the GUI clients, giving redundancy should one of theGUI 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

GUI Client

OPERATORWORKSTATION

SunOS

Hardware features

The SPARCstation 5s contain the following hardware features:

S Local Disk 535/424 Mb (minimum configuration).

S 20 inch colour terminal.

The SPARCstation 5s are complete UNIX systems and are loaded with the same UNIXoperating system as the SPARCUltras. They are usually configured as standalone NFS(Network File System) machines.

GSR6 (Horizon II) GUI Client - SPARCstation 5

02 May 2003


68P02901W01-M 4�49

Night concentration

Figure 4-24 shows a night concentration centre with one SPARCUltra configured as aGUI Server for both region A and region B. This means that only one SPARCUltra isrequired during the quiet night periods enabling a reduction in operating personnel.

Figure 4-24 Night concentration configuration

SYSTEMProcESSOR

Regional OMC-R A (local)

Printer

Bridge/Router

Router

Concentration centre

Regional OMC-R B(Remote)

GUI Server(region A)

GUI Server(region B)

LeasedLine

Printer

SYSTEMProcESSOR

GUI Server

GUI Server

GUI Client

Bridge/Router

Printer

GUI Server

GUI Client

GUI Client

X.21

X.21LAN

LAN

LAN

GSR6 (Horizon II)How the network status summary feature works

02 May 20034�50


68P02901W01-M

How the network status summary feature works

Map processWhen a network map, for example, Network 1600b: Device Mode (see Figure 4-25), isselected via the Maps icon on the OMC-R front panel, a map process is invoked on theGUI processor.

Figure 4-25 Map processes

GUI front panel

Test-Network mapMAPNODESMAPLINKS

GUI PROCESSOR

EM ProxyAlarm events

State change eventsCMMIB

SYSTEM PROCESSOR

Active NSSsubscription list

MAP_ALARMSMAP_EVENTSALM_ALARMS

FROM NETWORK

Configuration dataAll 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 ofmanaged objects to which relevant network configuration data and data needed toconfigure maps are assigned. For example, both a BSS and a Map are regarded asmanaged objects with different data. All the GUI processors that run the network mapscommunicate with the CM MIB using an internal process called cm_mib.

GSR6 (Horizon II) How the network status summary feature works

02 May 2003


68P02901W01-M 4�51

The EM proxy process

The EM Proxy process contains a list of all NEs, SITEs, cells, and links. The processexamines the incoming alarm messages and compares it to the list. It updates the list if achange has occurred. Every two seconds a changed list is forwarded to the GUIprocessor. The list contains attributes which reflect the severity of the alarm and itshandling state. These in turn update the Alarm Summary on the GUI front panel, and theattributes of the links and nodes on the active map, as configured in the CM MIB. TheContained Devices form and alarm icons are also updated. Similarly, incomingStateChangedEvents from SITEs and MMSs change the state of the attributes in the CMMIB. This reflects the administrative and operational states of the different SITE andCommsLink configuration objects, representing the physical devices in the network.

GSR6 (Horizon II)GUI clients and servers: overview

02 May 20034�52


68P02901W01-M

GUI clients and servers: overview

Client/server system

The client/server concept is a common form of distributed system in which softwareprocesses are split between server tasks and client tasks. A client sends requests to aserver, according to a standard protocol, asking for information or action, and the serverresponds 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 orderform to a supplier (the server) who despatches the goods and an invoice (response). Theorder 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 messagepassing, which may be over a network or even within a single machine. For example, theSPARC ULTRA 5 with the client and Sserver on the same machine. There may be asingle centralised server or several distributed Servers, depending on workloads. Thismodel 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 thehigh end MMI server (Ultra 5) have the power to run as a GUI server.

GSR6 (Horizon II) Network maps

02 May 2003


68P02901W01-M 4�53

Network maps

Functionality

Network maps show status information on the network and enable the following differenttypes of functionality to be invoked for a selected NE:

Current network configuration

Network maps present the current network topology. Network configurations can beupdated using the Detailed Views and an Audit, initiated to ensure consistency betweenthe MIB and the Network. A full network map, which displays all NEs and links in thenetwork is available. Each NE can be expanded to show the SITEs and links within theNE. Maps can be zoomed or expanded when displayed, (refer to Figure 4-25). If thesystem 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 anaudible 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). Referto 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 andadministrative 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 alarmmessages for selected NEs or SITEs. This window allows standard alarm handling to beperformed.

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 besent 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 anystate changes that have occurred since the previous Resync operation.

GSR6 (Horizon II)Network maps

02 May 20034�54


68P02901W01-M

Different maps available

The following maps are available for selection:

S One map showing the full network configuration, containing all configured nodesand links.

S 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. Forexample, a critical redundant device will produce a critical severity.

S Subscriber Mode displays severities according to the impact of faults onsubscribers. For example, service, capacity or redundancy loss.

Consolidated alarm report

Consolidated alarm reports provide information about the OMC-R map so that theoperator can identify problems in the network. This feature reduces the amount of alarmsreported to the operator, and consolidates all the information relating to a failure in areport.

Map configuration

Different maps of the network can be displayed, depending on what type of informationthe operator needs to monitor. This is achieved by adding the new map configurationdata to the CM MIB through the Detailed View forms and Audit. The OMC-R GUIprovides facilities for the automated process, followed by operator input for longitude andlatitude data.

When the MIB is initially populated with data from configuration files, default maps arecreated. In the absence of any geographical map background files, the maps aredisplayed on a default map background consisting of a single solid colour. To use mapbackgrounds other than the default, a background map, usually a geographical map, isassigned to the map object which configures the network map.

GSR6 (Horizon II) The map display

02 May 2003


68P02901W01-M 4�55

The map display

Map backgrounds

When maps are initially configured they are displayed on a default map background of asingle solid colour. A background, usually a geographical map background, is assigned tothe 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 thenetwork. This is set when the map is configured. A cluster icon is used to represent agroup 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 deviceor devices it contains. Alarms from links cause both the link and the node, where thefaulty MSI/MMS is contained, to flash. The icon colour will automatically be reset to thecolour representing Clear (defaulted to green) when the operator clears the alarm, or analarm 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, itis unable to support user traffic. The device status is determined by the administrativestate (controlled by the operator) and the operational state (controlled by the NE faultmanagement application).

The different combinations of operational and administrative states determine whetherthe node or link is INS, OOS, or has an unknown state. For example, a SITE is INS if itsoperational 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 redundantdevice). An operator or the NE fault management software can take a device OOS byissuing a LOCK command, or a SHUT-DOWN command in the case of a transceiver. ALOCK is intrusive as it terminates all activity on the device when the command isexecuted. The SHUTDOWN command permits the operator to specify a time intervalbefore 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 mapdisplay, the subscription lists that control alarm and state changes, and icon colours.

GSR6 (Horizon II)The map display

02 May 20034�56


68P02901W01-M

Pending stateAn asterisk, , on a node icon represents nodes in a pending state. Figure 4-26 showsthe map icons.

Figure 4-26 Map icons

INS

RXCDR

BSS

BSC site

BTS site

BSC�BTSsite

Link

UNKNOWN OOS

OMC

RXCDR−Site

MSC

OpState:

AdminState:

Options: OpState: Enabled | Disabled | Busy | UnknownAdminState: Locked | Unlocked | Shutting Down | Not Equipped | Unknown

Enabled

Unlocked

Any

Unknown

All othercombinations

INS UNKNOWN OOS

Icon name

How State is determined

Unlocked

Busy

& &or

& &or

Any

Unknown

?

?

?

?

?

GPRS PCU?

SGSN

??

GSR6 (Horizon II) How administrative and operational state changes work

02 May 2003


68P02901W01-M 4�57

How administrative and operational state changes work

State changes

Administrative and operational state changes are only relevant for SITEs and links on themap. Figure 4-27 illustrates how the icons representing the SITEs or links are changed toreflect the change in state of the physical device.

Figure 4-27 State changes on the map

CommsLink

Network OMC-R MSC

BSS1 RXCDR BSS2BTS1MSI1 MMS1

GUI front panel

Mapnodes (BTS1)Maplinks

OOS

OOSUNKNOWN

Icon representing BTS1 onthe map changes to oos state

CM MIB

Map on operatorworkstation

Map

EM proxy

Active NSSsubscription lists

MAP_EVENTS

StateChangeEvent

(Operational state of BTS1 changes to disabled)

StateChangeEventSystemprocessor

OpState: Disabled Busy

AdminState: LockedShutting Down NotEquipped

GUIState: INS OOS Unknown

BTS1

Represents previous attribute setting

Represents new attribute setting

Enabled

INS

MapNode (BTS1)

GUIState

GUI processor

Unlocked

GSR6 (Horizon II)How alarms work

02 May 20034�58


68P02901W01-M

How alarms work

Alarm iconsIncoming alarms are reported by a flashing MapNode or MapLink icon, coloured torepresent different alarm severities. If an icon on a map is flashing, it denotes thepresence of unhandled alarms for the device or devices it represents. Alarms from linkscause both the MapLink and the MapNode containing the faulty MMS to flash andchange colour.

Figure 4-28 Alarms and how they change on the map

GUI front panel

Mapnodes (BTS1)Maplinks

Critical

MAP on operatorworkstation

EM proxy

Map

Alarm information

MapNode (BTS1)

GUIState

CMMIB

Not handled

Icon representing BTS1 onthe map changes colour to red and startsflashing.

Alarms icon on gui front panel startsflashing. alarms summary windowupdated.

Active NSSsubscriptionlists

Critical alarm event

MAP_ALARMSALM_ALARMS

BTS1

ALARM 001AlarmState: Being Handled | Not Being HandledAlarmSeverity: Critical | Major | Minor | Warning |Investigate | Clear[message fields]



Systemprocessor

GUI processor

(Alarm received fromBTS 1)

Represents the previous attribute setting

Represents new attribute setting

Colour Red Yellow

Blue Pink Turquoise Green

Flashing Yes No

Critical alarmevent

GSR6 (Horizon II) How alarms work

02 May 2003


68P02901W01-M 4�59

Colours

The colour of any displayed icon or link reflects the severity of alarms in the device orgroup 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 thedevices in the BSC and BTSs within the BSS) an alarm occurrence in any device withinthe group is shown at the displayed icon.

In the event of alarms of different severities existing for the same device, or group ofdevices the display colour reflects the most severe alarm condition.

The icon colour will automatically be reset to the Clear colour when the operator clearsthe alarm or an alarm clear message is received from the network.

GSR6 (Horizon II)How maps are configured

02 May 20034�60


68P02901W01-M

How maps are configured

Introduction to the CM MIB

The CM MIB stores a series of managed objects to which relevant configuration data isassigned. For example, both a BSS and a Map are considered to be managed objectsrequiring different data. All the GUI processors that run the Network Map communicatewith 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

OMC-R

NETWORK

SITE MSI MMS

MAPMAPNODE

MAPLINK

CommsLink

CONFIGURATIONOBJECTS

GRAPHICOBJECTS

BSS RXCDR MSC

RTF DRI CELL

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

S Configuration objects.

Hold all the data about the physical network. There is a containment relationshipbetween the different managed objects.

GSR6 (Horizon II) Graphic objects

02 May 2003


68P02901W01-M 4�61

Graphic objects

Graphic objects

There are three graphic objects in the CM MIB. Figure 4-30 shows the containmentrelationship 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 menuon selecting the Maps icon from the front panel. It defines the map name and thebackground map used with it.

MapNode

The MapNode graphic object specifies the type of NE or SITE to be represented on themap.

A MapNode can represent any of the following configuration objects:

S OMC-R.

S BSC.

S MSC.

S RXCDR.

S BSC�BTS.

S BTS.

MapLink

The MapLink graphic object represents one or more CommsLinks.

GSR6 (Horizon II)Configuration objects

02 May 20034�62


68P02901W01-M

Configuration objects

Configuration objects

The containment relationship between the different configuration objects is shown inFigure 4-31. The objects are grouped into four logical groups, namely, HardwareDevices, Software Functions, Logical Links, and Radio Frequency. This reflects thephysical configuration of the devices in the network, and determines the upwardpropagation of alarms. For example, an alarm from an MSI object will also be propagatedto its parent SITE, which in turn is propagated to its parent BSS.

Figure 4-31 The containment relationship for the configuration objects

Network

Cabinet CAGE EAS IASKSWpair GCLKProcessors LAN TDM MSI

SWInventory

SoftwareLoad

Map

MapNode MapLink

ProxyCell UserProfile

GPROC BSP CSFP

PCU

HardwareDevices

Cabinet CAGE Processors MSI GDS

DPROC PSP MMS

NSVCGSL GBL

NESoftware

LogicalLinks

SoftwareFunctions

BTF LCF OMF RSL PATH

* The handover control objects are: RelTimAdvHC, RxlevDlHC, RxlevUlHC, RxqualDlHC, RxqualUlHC, SurrndCellHC

** The power control objects are: RxlevDlPC, RxlevUlPC, RxqualDlPC, RxqualUlPC

RadioFrequency

CELL

FreqHopSys SMSCBmsg Neighbour TestNeighbour Handover/Power Control

TRX

DRIRTF

CM MIB

COMB

RTFGroup

DRIGroup

LogicalLinks

BSS RXCDR CommsLink MSC OMC-R

HardwareDevices

SITE

GSR6 (Horizon II) Configuration objects

02 May 2003


68P02901W01-M 4�63

Network

The Network configuration object represents the overall network being managed. Thereis only one Network configuration object in the MIB, and it is already configured ondelivery.

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 currentlystored in the OMC-R. A maximum of 2 147 483 647 SoftwareLoad objects can becontained within a SWInventory object.

MSC

The MSC configuration object represents the Mobile Switching Centre. The OMC-R doesnot directly manage the MSC, but manages the links between the BSSs, RXCDRs, andthe 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 thephysical network (maximum of 120) is represented by an object.

RXCDR

The RXCDR configuration object represents the Remote Transcoder. There are as manyof these objects as exist in the physical network (maximum of 120).

CommsLink

The CommsLink configuration object defines the two MMS ports in the different SITESthat 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 ofany 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 aBSC, a BTS. SITE 0 must always contain the BSC functionality, and is configured as aBSC or a BSC�BTS. The remaining SITEs may only be configured as BTSs. There areas many of these objects as exist in the physical network (maximum of 100 per BSS). ARXCDR can also have a SITE 0 associated with it.


02 May 20034�64


68P02901W01-M

Hardware devices

The Hardware Devices represent an abstract logical container class. It is used to groupthe 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 Systemdevice within the site.

Processors

The processors object represents a logical container class. It provides a grouping for theGPROC (Generic Processor Boards) BSP (Base Site Control) and CSFP (Code StorageFacility) processors within the site.

KSWpair

The KSWpair object is used to represent a pair of KSW (Kiloport Switch board) deviceswhich 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 suchas 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 whichcontrols two MMS ports. There is a maximum of 101 MSIs at SITE 0 and 51 at otherSITES.

COMB

The COMB is a general abbreviation used for a Combiner which combines two or moreRF transmissions, from a BTS transceiver control unit (TCU), for a simultaneousbroadcast to a single antenna.


02 May 2003


68P02901W01-M 4�65

Software functionsThe Software Functions represent an abstract logical container class. It is used to groupthe different software functions on the BSC.

BTF

The BTF object represents a Base Transceiver Function. There is a single instance ofthis class in BSC site 0.

LCF

The LCF object represents a Link Control Function. There is a single instance of thisclass in BSC site 0.

OMF

The OMF object represents a OMF GPROC Function. There is a single instance of thisclass in BSC site 0.

Logical linksThe logical links represent an abstract logical container class. It provides the grouping forthe various links present at the site.

CBL

A CBL link can be configured between the BSC or RXCDR and the Cell BroadcastCentre (CBC). This is used for downloading messages to broadcast along with othernecessary 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 BSCand the MSC. In the Motorola system, when local transcoding is used, this is a physicalconnection between the BSC and the MSC. When a Remote Transcoder is used, thelogical MTL is made up of two physical parts; the connection between the BSC and theRXCDR and the connection between the RXCDR and the MSC.

OML

This link is for control and communications between the BSS and OMC. The RXCDRprovides an OML for each BSC connected to it.

XBL

An XBL link may be configured between the BSC and the RXCDR for exchanginginternal Fault Management (FM) data between them.

RSL

The RSL represent a Radio Signalling Link. The RSL can only be contained within theremote 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. Therecan be a maximum of 10 PATH objects contained in a SITE object.


02 May 20034�66


68P02901W01-M

Radio frequencyThe Radio Frequency represent an abstract logical container class. This provides thegrouping for the various radio related objects.

RTFGroup

The RTFGroup object is used to represent a single RTF function grouping within a site. Amaximum 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 of25 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. Itcontains one or more DRIs which are connected to the same antenna and use the sameportion of the TDM highway. A maximum of 6 DRIGroup objects can be contained in aSITE object.

DRI

The DRI object is used to represent a single Digital Radio Interface (DRI) device within asite. It provides the interface between the DRCU and the digital portion of a BSS. Amaximum 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 objectscan be created under a SITE object. A maximum of 250 CELLs can be contained within aBSS.

FreqHopSys

The FreqHopSys object is used to represent a single frequency hopping system within acell.

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, thosecells to which it can handover calls. A maximum of 64 Neighbour objects can be createdunder 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 basedon certain criteria. For more details refer to the OMC-R Online Help.


02 May 2003


68P02901W01-M 4�67

Power control

Power Control objects are RxlevDlPC, RxlevUlPC, RxqualDlPC and RxqualUlPC. Theseobjects describe the power control algorithms based on certain criteria. For more detailsrefer to the OMC-R Online Help.

ProxyCell

The ProxyCell object represents CELLs outside the current PLMN. A maximum of 500ProxyCell objects can be contained in a SITE object.

UserProfile

The UserProfile object represents an OMC-R user who uses the OMC-R GUI. Amaximum 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 activeflag 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 typeBCCH 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 CELLit identifies exists. Otherwise, a Source object is automatically created when the CELLobject is created.


02 May 20034�68


68P02901W01-M

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

MapNode

A MapNode object is automatically created when a BSS, OMC-R, MSC, RXCDR or SITEobject 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.

GSR6 (Horizon II) Periodic Supervision of Accessibility (PSA)

02 May 2003


68P02901W01-M 4�69

Periodic Supervision of Accessibility (PSA)

Definition of PSA

Periodic Supervision of Accessibility (PSA) periodically sends messages to BSSsrequesting information on their current state. This verifies if the BSSs are operational ornot.

PSA failure

If a BSS fails to respond to a PSA request for its status, the OMC-R will generate analarm for that BSS. This alarm indicates that the BSS failed to respond to a messagerequesting its status, and may be indicative of a problem at the BSS. The OMC-Rcontinues to send messages periodically to the BSS requesting its status. On receipt ofa response message from the BSS, the OMC-R changes the alarm severity of themessage 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 changesthe alarm severity of the message to Clear.

GSR6 (Horizon II)Disk usage exceeded

02 May 20034�70


68P02901W01-M

Disk usage exceeded

System processor partition full

An alarm is raised when either of two (upper and lower) threshold values of disk usageare exceeded on the /,the /home, the /usr, and the /usr/gsm/ne_datapartitions of the System Processor.

The System removes any logfiles older than three days from the $OMC_TOP/logsdirectory using routine maintenance cron jobs, or if the upper disk usage threshold isexceeded. The threshold value should return to the default value of 90%.

The file $OMC_TOP/config/global/FM_audit.CNFG contains the values that areused for setting the timers for each audit and disk usage limits. These values are set atinstallation time and can only be changed by the system administrator.

Further information

For information on setting the related parameters, see Maintenance Information: AlarmHandling at the OMC-R, (68P02901W26).

GSR6 (Horizon II) DataGen

02 May 2003


68P02901W01-M 4�71

DataGen

Introduction to DataGen

DataGen is a GSM product used to create BSS databases off-line. DataGen can storepast, current, and future versions in an Informix database. These databases can betransferred to the OMC-R, then they are downloaded to the live BSSs. DataGen runs onits 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, upgradesto the BSS software, frequency replans, and network expansion. Figure 4-32 shows theDataGen configuration in a GSM environment.

Figure 4-32 DataGen in a GSM environment.

Data Gen NMC

OSI

OMC-R

SystemProcessor

OperatorWorkstations

Network ManagementCentre GatewayProcessor

Local Area Network

X.25BSC

BSC

BSCBSC

GSR6 (Horizon II)DataGen

02 May 20034�72


68P02901W01-M

DataGen configuration managementDataGen provides the user with the capability of performing off-line configuration ofMotorola GSM network entities (NEs). The Informix database contains two types ofinformation:

S A representation of the information required to create a Sysgen script for allsupported BSS releases.

Included in this are details relating to syntax, parameters, elements, and theirassociated ranges for the GUI commands in the Sysgen script.

S Configuration information for a specific BSS area.

These areas are identified by country or network, name, software release, andconfiguration number. The configuration number allows multiple BSSs to existwithin the DataGen database.

Figure 4-33 shows the DataGen main window.

Figure 4-33 DataGen main window

Off-line MIBFigure 4-34 shows the Off-line MIB, which is used to create new networks, visualise, andvalidate networks before deployment into a live network. It has a common user interfacewith the online OMC-R. BSS binary files are used to create the network which isdisplayed as a tree-like representation called the Navigation Tree. It is possible to updatemultiple BSS binary files simultaneously, for example, propagating neighbour changesfrom one BSS binary file to another.

The Navigation Tree allows:

S Graphical editing of configuration management.

S Neighbour propagation.

S An interface to radio refrequency planning tools.

Figure 4-34 Off-line MIB front panel

GSR 4.1 � 1.6.1.0

02 May 2003


68P02901W01-M 5�1

Chapter 5

BSS software release features

GSR6 (Horizon II)

02 May 20035�2


68P02901W01-M

GSR6 (Horizon II) Introduction to BSS software release features

02 May 2003


68P02901W01-M 5�3

Introduction to BSS software release features

In this chapter

This chapter summarizes the features of the Motorola BSS software releases. MotorolaGSM products are continually being updated. Releases of software before GSR2 wereidentified by four-digit release numbers, such as 1.2.1.1. After the 1.4.1.x release, thenumbering 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.











S BSS software release 1.3.0.x.






S BSS software release GSR2.



S BSS software release GSR4.1.


S BSS software release GSR5.1.


S BSS software release GSR6 (Horizon II).

GSR6 (Horizon II)BSS software release 1.1.1.0

02 May 20035�4


68P02901W01-M

BSS software release 1.1.1.0

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 Description

Teleservice 11 Compliant with GSM 02.03 for speech, data and signaltransmission from the PSTN/ISDN.

Connectionless callprocessing

Provides the functionality for dialogue between theMSC and MS.

MTP Part of the MSC-BSS A interface. Supports point topoint signalling, compliant with ITU-TSS SS7.

SCCP Part of the MSC-BSS A interface. Compliant withITU-TSS SS7 and ITU-TSS Q.711-Q.714 and GSM08.06 para 5.2 - para 5.5.

BSSAP Part of the MSC-BSS A interface. Comprises twodistinct 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 channelsfor full rate speech channels.

Layer 3 Specifies the procedures used at the radio interface forcall control, mobility management and radio resourcemanagement.

Modified Abis (Mobis) Reduces 2 Mbit/s link traffic by increasing BSSprocessing in the BTS.

MMI entry/response at localTTY

Compliant with GSM 12.01, 12.06 allows commandentry and printing of responses and alarm messagesfor the local network element.

System change controladministration

Provides services for the management andadministration of configuration or data changes.

Configuration Management Allows operating versions of hardware and softwarecomponents 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 50per BSC.

BSS capacities Set at 40 sites, 60 cells and 75 RCUs per BSS

Performance statistics Provides measurements to GSM recommendation12.04 and Motorola unique measurements.

GSR6 (Horizon II) BSS software release 1.1.1.0

02 May 2003


68P02901W01-M 5�5

Feature Description

Collect limited stats Provides a variety of statistics actions using MMIcommands.

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 throughexisting MMI commands and CM.

Classmark update Call processing feature that allows the MS to indicate aclassmark change to the rest of the network.

Dynamic timeslotreconfiguration

Call processing feature that allows timeslots to bereconfigured as requested.

Packaging page access grantmessages

Call processing feature that allows multiple informationtransfer in one message

Handover queuing Call processing feature allowing queuing of messagesduring and internal handover. Refer to GSMrecommendation 8.08.

Resource allocation Call processing feature allowing the BSS to notify theMSC of radio resources available on request. Refer toGSM recommendation 8.08.

Call queuing Allows call queuing until resources are available,subject to pre-set time constraints. Refer to GSMrecommendation 8.08.

Remove SCCP piggy backing Removes handover request from connection requeston SCCP.

Flexible ID format Allows variable length ID elements as defined in GSMrecommendation 8.08

Call tracing Initiates a call trace via an MMI command.

Fault recovery cleanup ofaffected 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 isadded.


02 May 20035�6


68P02901W01-M



Table 5-2 summarizes the features of 1.1.2.0.

Table 5-2 Software release 1.1.2.0 features

Feature Description

BSS-OMC agent statisticsreporting 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 areprovided.

Collect and provide access tolisted statistics

Provides additional functionality for statistics values viaMMI commands.

BSC-OMC agent: Softwarereporting

Reports software alarms to the OMC from the BSC.

BSC-OMC agent: Hardwarereporting

Reports hardware alarms to the OMC from the BSC.

Diversity option commands Turns On or Off the diversity option for a site using anMMI command.

Support antenna diversity(BTS4-D)

Modification to the BSS software to provide support forBTS4-D.

Fault management Provides enhanced fault detection and management.

Fault reporting to the OMC Collects alarms within the BSS and reports them locallyto the OMC.

Maximum systemconfiguration

Supports a database up to 6 Megabytes in size.

MMI commands MMI commands are added or enhanced to support thediversity option, XCDR maintenance and BSSdatabase control.

System commands System commands are added or enhanced to supportfault management and configuration management.

Device management of a site Supports a number of implementation commands for asite.

Device management of BSSdevices

Supports implementation commands for BSS devices.Provides minimal fault isolation and recovery.

Device managementoperations

Supports a number of management operations forimplementation of devices.


02 May 2003


68P02901W01-M 5�7





Function Description

Handover algorithm - D1 Supports algorithm as specified in FEIN specificationsfor Detecon (FS 05.08.1.1 (2.2), Chapter 3.3.1).

Force OMC download ofEEPROMs

Forces an OMC download of GPROC flash EEPROMmanually.

Device management of BSSdevice (EAS)

Supports implementation commands on the EASdevice PIX.

System commands Supports fault management and configurationmanagement.


02 May 20035�8


68P02901W01-M





Feature Description

BTS daisy chain with returnloop

The return loop feature, now known as a closed loop,adds a closed loop capability for open loop BTSconfigurations.

Signalling Point Inaccessible SPI implements the BSSMAP procedures for signallingpoint 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 forGPROCS.

EAS enhancements Includes optocoupler number and alarm text in EASoptocoupler alarms sent to the OMC.


02 May 2003


68P02901W01-M 5�9





Feature Description

Advanced RCU download Reduces BTS outage time during BTS initialisation byimproving overall DRI/RCU download and configurationtime. The time reduction increases as the number ofDRI/RCUs increase at a site.


02 May 20035�10


68P02901W01-M





Feature Description

Baseband hopping Switches information generated by the channelcoding/interleaving function on the DRI to theappropriate RCU.

Synthesizer hopping Re-tunes RCUs in real time from frequency tofrequency.

Data services full-rate trafficchannels

Supports data services on full-rate radio trafficchannels.

Support alternate speech anddata

Allows MSC/BSS coordinated switching betweenspeech and datausing in-call modification procedures.

GPROC device management Removes the need for BTS reinitialisation when RSLlinks to the BSC are interrupted.

Device management ofGPROCs

Ensure synchronization of BSC and BTS callprocessing after loss of all links or reinitialisation.

Cross load time improvement Reduces the time to cross load between GPROCs at asite.

Paging distributoroptimization

Ensures that only one message is sent to a BTS per Ainterface paging message.

Short message service, pointto point

The BSS supports Short Message Service (MSoriginated and MS terminated). Motorola will be phase1 compatible as the BSS responds to a SAPI �n� clearwith a SAPI �n� clear complete although the SAPI 3connection is not torn down.

Simple flow control Provides BSS overload managment by barring MSaccess classes as necessary when call informationblock usage reaches a predetermind threshold.

Intra-BTS synchronizedhandover

Allows handovers that do not require the BSS to senda physical information (timing advance) message to theMSC.

LAN device managment andswap over

Provides managment for the LAN hardware devicesand enables switching between the two LAN hardwareloops that interconnect all GPROCs at a BSC or BTSsite.

Remote BTS add and delete Provides an add and delete function allowing a BSC tosupport an open or closed loop of BTSs.

Remote transcoder to BSClink (XBL)

Notification of failed traffic circuits is sent from theRXCDR to the BSC, and the BSC disables thesecircuits by sending the appropriate blocking messagesto the MSC.


02 May 2003


68P02901W01-M 5�11

Feature Description

System audits processes The System Audits Processes (SAP) detects faulty ordegrading hardware and software (through the use ofaudit tests) and notifies the Alarms handling softwareof the condition. The SAP does not take any recoveryor further diagnostics action due to a fault. This is leftup to the Fault Translation Process (FTP) upon receiptof the alarm indication.

Audit control Provides SAP features using MMI commands at theOMC or local MMI terminal.

Audits of soft devices Verifies correct operation of the software proceeseswithin a GPROC.

Audits of boards Verifies correct operation of the hardware deviceswithin the BSS.

Audits of buses Verifies correct operation of the communication busseswithin a BSS site.

Database notification The database notification feature ensures that anyoperator-initiated change to data in the CM database isdistributed to all in-service GPROCs and that theappropriate devices are notified of the change.

Data catagories Handles changes to type 2 and 3 data within the CMdatabase.

BSS/OMC periodicsupervision of accessibilty

Enables periodic polling of the BSS from the OMC. Analarm is generated if the BSS does not respondcorrectly to the poll.

GCLK fault management This feature provides fault management of the GCLKdevice, together with more complete GCLK alarminformation than was previously available. Operatorcommands are also provided to control which of thetwo GCLKs is active.

Save alarm status upon OMLoutage

Allows the BSS to store alarms which may begenerated within the BSS while OMC is inaccessible.

Alarm clearig and throttling Alarms reported by the BSS can be categorized aseither intermittent or constant. The alarm clearing andthrottling feature clears constant alarms when theunderlying fault is no longer present and throttleintermittent alarms which repeat frequently.

Multiple CCCH This feature allows multiple CCCH timeslots to exist onsuccessive even timeslots on the BCCH carrier.

RF queuing priority withoutpre-emption

Positions information elements in priority order in thewaiting queue if the queuing indicator is set to Allow.The queue assignment requesrt is rejected if thequeueing indocator is set to Not Allowed.

KSW expansion Up to four KSWs can be connected together to supportup to 4096 TDM timeslots at a site. The BSScontinues to support redundant KSWs. Forredundancy a KSW is required for each KSW requiredfor capacity.


02 May 20035�12


68P02901W01-M



Table 5-7 summarizes the feature of 1.2.0.3.


Feature Description

Alarm and statussynchronization

The BSS supports future development of the OMCalarm and status synchronization feature within theOMC. Impacted areas are Fault Management (CA andFTP) and the OMC interface.The alarm and statesynchronization feature provides a mechanism forsynchronization of the OMC and BSS/RXCDR devicestatus. Status information is composed of both alarmand device state information.

Normally, the BSS/RXCDR sends alarms and devicestate change events to the OMC as they occur, so theOMC keeps up to date with changes to the networkelement device status. However, a mechanism fordevice status synchronization is required both at OMCinitialization time, and after a failure of the OMC,BSS/RXCDR or the links between them.

Synchronization can be initiated via operator requestOMC init, or it can be set up to occur automatically at aconfigurable interval.


02 May 2003


68P02901W01-M 5�13



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 remoteBTS fails, traffic is switched to a redundant 2 Mbit/s linkif one is available. The switchover improvementfeature reduces the time taken to switch links, thusminimising any break in voice or data transmission.

GCLK synchronization Ensures that air interface data timing and RFfrequencies remain within the GSM recommendationsand eliminates frame slips over the E1 interface.

Database level number The database level number feature keeps a databaselevel number for each site in the BSS. Database levelnumber increments are sent to a remote BTS only ifthe database changes for that site. This feature willhelp prevent unnecessary database downloads toremote BTSs and also reduce the message traffic inthe BSS.

BSC-BTS downloadcompression

This feature reduces the time taken by a BSC todownload the CM database to its BTSs. The BSCcompresses the information prior to downloading it,and the BTS decompresses it on receipt.Checksumming procedures prevent data loss orcorruption during compression and decompression.

Preventative cyclicretransmission

Preventive Cyclic Retransmission (PCR) involves theretention of a signal unit at the transmitting terminaluntil acknowledgement is received from the receivingterminal. During the period when there are no newsignal units to be transmitted, the transmitting terminalcyclically retransmits all the signal units that have notyet been acknowledged by the receiving terminal.

Multiple digital host processor The multiple DHP cage feature allows more than oneDHP per cage.

Timeslot reservation This feature allows ranges of timeslots on specified 2Mbit/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 afault. The feature also provides for any alarms detectedby the digital power supply modules (DPSMs) in a cageto be reported.


02 May 20035�14


68P02901W01-M





Feature Description

TopCell alarm enhancement The BSS software supports the additional alarms thatare 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 ExCellproduct.


02 May 2003


68P02901W01-M 5�15


Reason for this release

Release 1.2.2.3 addresses an internal problem that could pose a potential risk tocustomers with medium to large configurations. This release supersedes release 1.2.2.2and should be used instead of release 1.2.2.2.


02 May 20035�16


68P02901W01-M


Important information

GSM BSS 1.2.3.0 is released on a limited basis to support DCS1800 First OfficeApplication (FOA). The extent of functionality supported by this release is limited tobasic cellular phone service. The following feature functionality is excluded until sufficienttesting has been accomplished to release these features for use in the DCS1800environment:




Feature 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 broadcastsingle background message.Data services alternate speech; data servicesfull rate.Frequency hopping, baseband; frequencyhopping, synthesizer.

A BSS operating with BSGSM 1.2.3.0 in GSM900mode has not been qualified to operate with anotherBSS in DCS1800 mode, while both BSS are connectedto the same OMC. It is recommended that all BSSconnected to a single OMC remain homogenous withrespect to the radio spectrum they serve.

Fault isolation (enhanced) This feature provides enhancements to existing faultisolation capabilities for the DRI and GPROC devices.

Short message service, cellbroadcast (single backgroundmessage)

This feature is a means of unilaterally transmitting datato mobiles on a per cell basis, by use of a CellBroadcast Channel (CBCH). This feature provides asubset of the full GSM functionality. In particular, theBSC interface to the CBC is not supported. Instead, asingle operator defined message may be entered usingappropriate MMI command. The full functionality asdefined by GSM will be implemented in a later release.

Real time traffic monitoring This feature enhances the BSS and OMC to allow realtime traffic display of channels in use on both the Ainterface (terrestrial circuits) and air interface (radiochannels).

Display of hardware revisionlevel from MMI

Operators use this feature to obtain the hardwareversion number of certain boards, using an MMIcommand. Alarms are reported with the hardwareversion number of the board originating the alarm, ifthe alarm originates from either a GCLK, GPROC,DHP, BSP, BTP, KSW, MSI, XCDR or DRI.


02 May 2003


68P02901W01-M 5�17

Feature Description

RCU ID MMI feature Operators use this feature to display the serial numberof any RCU/DRCU, and the hardware version numberof its component boards. RCU/DRCU alarms arecorrelated to a specific RCU/DRCU, using theRCU/DRCU serial number.

BTS battery conservation atmain power failure

This feature enhances BTS battery backup operationby selectively stopping RCUs from transmitting, so thatpower is conserved. This extends the available BTSbattery time.

TopCell Alarm Enhancement The BSS software supports the additional alarms thatare 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 newRF hardware being developed to operate in the 1800MHz frequency band.

Update of LAN microcode Due to a change to the TMS380C26 LAN adapterdevice on the GPROC board, this release contains anupdate of the vendor provided microcode for thedevice.

Six carrier BTS shelf The BSS supports a 6 carrier BTS shelf for DRCU3.

ExCells The BSS supports a 6 carrier version of the ExCellproduct.

Preventative CyclicRetransmission on C7-MTPMSC-BSC A interface

The BSS supports Preventative Cyclic Retransmission(PCR) error correction for connecting to the MSC (theA interface) via a satellite link.

TopCell base The BSS software supports the new TopCell hardware,incorporating DCS1800 components. The TopCellproduct is a complete cell site (BTS)

TopCell requirements Defines the new requirements for a TopCell site.

GSR6 (Horizon II)BSS software release 1.3.0.x

02 May 20035�18


68P02901W01-M

BSS software release 1.3.0.x

Release 1.3.0.x features

Release 1.2.3.0 features integrated into 1.3.0.x are included for customers upgradingfrom 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 Description

Large BSS configurationcapacity

This feature introduces capacity support for a systemconsisting of 50 sites, 90 cells, and 90 active RCUs(TRXs).

Fault isolation (enhanced)DRI and GPROC

This feature provides enhancements to existing faultisolation capabilities for the DRI and GPROC devices.

KSW, TDM and TBUSmanagement

Provides control for configuration of the listed devicesand allows switching of between TDMs withoutre-booting the system.

Manage inactive GPROCS This feature enhances the operations and maintenanceof GPROC devices.

BSC LCF swaps Allows switching of logical links to the MPT layer 2physical links if an MTL GPROC fails duringtransmission.

BSC OMF The BSS provides the capability to independentlyhandle OMF function (OMF GPROC) failures withoutimpacting the remaining GPROCs at the BSS site.This capability does not prevent an interruption to callprocessing service.

BTS DHP swaps Shifts functionality of the RF carrier from a failed DHPto a healthy device, thus limiting the effect of the failedDHP recovery to a subset of the carriers at theBSS/BTS site. All carriers on the failed DHP aredisabled and re-enabled on other survivingDHPs/BTP/BTF within the same cage, if there isavailable capacity.

BSC BTF swaps Allows BTF swapping to ensure no loss of functionresources if a GPROC fails.

Code storage facilityprocessor

The Code Storage Facility Processor (CSFP) supportspropagation of new software instances with reducedsystem downtime. Optional CSFP falback is alsoprovided.

Encryption algorithm, A5/2 orNull

The BSS supports basic encryption operation using theA5/2 and Null encryption algorithms. Encryptionprovides security for user speech, data and signalinginformation at the physical layer. Encryption anddecryption must be deployed at both the BSS and MS.

Multiple versions of A5algorithm

The BSS supports the parallel operation of A5/1, A5/2and Null encryption algorithms. The operator is able toset the priority/order in which the algorithms shall bechosen by the BSS. This order can be set at sysgentime or via MMI command.

GSR6 (Horizon II) BSS software release 1.3.0.x

02 May 2003


68P02901W01-M 5�19

Feature Description

Restrict optional feature The BSS restricts use of optional features unlesspurchased by the customer.

Short message service, cellbroadcast (single backgroundmessage)

Defines the operator controlled, Short MessageService, Cell Broadcast (SMS CB) feature, which is ameans of unilaterally transmitting data to mobiles on aper 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/Ainterface

Delivers part of an operating system upgrade, oroverall application package, for BSS support of GSMphase 2 compliant messaging over the A and airinterfaces.

BSS signalling Provides BSS signalling compatibility with phase 2GSM, EGSM and DCS1800 systems. Also maintainsphase 1 GSM system compatibility.

Phase 2 compliant networkentities

Supports both phase 1 and 2 GSM mobiles over thenetwork.

Dynamic extended paging Allows dynamic extended paging to be enabled throughMMI commands. Also allows automatic dynamicextended paging in overload conditions.

Display of hardware revisionlevel

Allows display of version numbers or serial numbers ofhardware components.

BTS battery conservationafter main power failure

This feature enhances current BTS battery backupoperation by automatically stopping RCUs fromtransmitting, so that power is conserved. This extendsthe available BTS battery time. The non-BCCHcarriers are disabled before the BCCH carriers usingan algorithm in fault management the extent of which iscontrolled by MMI.

DCS1800 frequencies Supports the signalling required to operate in theDCS1800 frequency bands.

DCS1800 hardware Supports the RF hardware required to operate in theDCS1800 frequency bands.

MSI-2/T1 signalling supportfor PCS1900

This feature introduces support for PCS1900configurations. The BSS will have the functionalcapability to operate as both GSM900 and PCS1900configurations.

Preventative cyclicretransmission

The BSS supports Preventative Cyclic Retransmission(PCR) error correction for connecting to the MSC (theA interface) via a satellite link.

Network configurationmanagement

This feature provides the mechanism(s) to supportconfiguration management from the OMC using amanagement interface to the BSS. Also includessupport of alarm and status synchronization.

Dual OML download The redundant OML link supports load sharing fordownloading from the OMC providing BSS defaultrequirements are met.

GSR6 (Horizon II)BSS software release 1.3.0.x

02 May 20035�20


68P02901W01-M

Feature Description

Real time traffic channelmonitoring

This feature enhances the BSS and OMC, to allow realtime traffic display of channels in use on both theA interface (terrestrial circuits) and air interface (radiochannels).

Transcoder downloadlinkvolume control

This feature provides for an audio uplink and downlinkvolume control offset on a per BSS basis.


02 May 2003


68P02901W01-M 5�21





Feature Description

GCLK synchronization This is a standard 1.4.0.0 feature which enables anycurrent generation SITE to be configured so that it cansynchronize its GCLK to a known good clock sourcein an uplink SITE via an E1 or T1 link.


02 May 20035�22


68P02901W01-M




Table 5-13 Release1.4.0.1 features

Parameter Description

Preserve RCU/SITEcalibration

Enables all types/versions of a malfunctioning radiochannel unit to be replaced without the need to removethe Cell from service, in Cell configurations with two ormore radio channel units.

Indication of flow controlinvocation

Provides a new Cell level statistic,FLOW_CONTROL_BARRED, which measures theduration for which channel access to the cell isunavailable to any access class.

GSM short message service The Motorola BSS supports GSM Short MessageService - Cell Broadcast (SMS CB). MobileSubscribers with access to the short message serviceare able to receive alphanumeric information messagesat any time while their Mobile Station (MS) is in contactwith a BSS.

SMS - Cell broadcast:multiple backgroundmessages

Enables the BSS to directly support SMS Cellbroadcast for single or multiple (up to four)alphanumeric information messages to be sent to anysuitably configured MS.

SMS - Cell broadcast centresupport

Supports the use of a third party SMS Cell BroadcastCentre (CBC) on the Motorola GSM network. The BSSdatabase and MMI commands have been modified tosupport this feature.

Added nailed connections(optional)

Enables non-GSM connections used by third partyservices, such as, a paging network or analoguemobile phone network, to share the use of the E1 or T1links through a BSS without the need for externalmultiplexing equipment. The existing Timeslotreservation feature is modified to enable the reservingof timeslots on any E1 or T1 link. The RESERVEoperation is currently allowed for MMSs on a PATHonly.

Remote network devicelock/unlock

Enables BSS device administration to be performed byan OMC operator via the OMC GUI when carrying outFault Management (FM) and ConfigurationManagement (CM) procedures. A deviceoperational/administrative state report is possible froma new window, Contained Devices for Selected Node,which can be selected for any BSS, RXCDR, or SITEon either the network maps or the navigation tree atthe OMC GUI. Also reduces the need for a OMC -BSS remote login in order to perform either FMactivities or for Configuration Management activities


02 May 2003


68P02901W01-M 5�23





Function Description

Software support of M-Cell2/6GSM for 900 MHz

This feature introduces BSS software support of thecore M-Cell hardware, plus MCU, NIU and TCUsupport.

Software support of M-Cell2/6GSM for 1800 MHz

This feature introduces support of DCS1800 with boththe M-Cell2 and M-Cell6 BTS hardware platforms.

M-Cell EGSM This feature introduces an EGSM-capable TransceiverControl Unit (TCU) at 900 MHz. A TCU combines theRadio Subsystem, DRI and DRCU functions into asingle package.

TCU backwards compatibility Enables older generation BTSs to operate the currentTCU.

RSS functionality port tocarrier equipment (TCU)M-Cell

This feature provides for the porting of RSS and DRIfunctions 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-CellBTS SITEs only. A soft reset is defined as a resetwhere no equipment requires a code load and the resetswitch of no piece of equipment has been tripped. Noobject comparisons or checksums are done at a softreset. This fulfils the requirements of the Recoveryescalation (Roadmap ID 31240) feature.

M-Cell6 remote tunercombiner (900 MHz only)

This feature comprises BSS software support of aRemote Tuning Combiner (RTC) for an M-Cell6 at 900MHz only.

M-Cell6 receive matrix (900MHz only)

This feature introduces an Extended GSM(EGSM)-capable receiver RF matrix, which supportsup to six carriers in a single cabinet.

BSC CSFP redundancy This feature provides for BSS software support forequipping two Code Storage Facility Processors(CSFPs) at the BSC to provide redundancy.

M-Cell hardware impact onBSU-BTS

This requirement provides for BSC support of the newM-Cell hardware with no degradation in service at theBSC, except for outages necessary for interconnectionpurposes.


02 May 20035�24


68P02901W01-M





Feature Description

M-Cellmicro GSM900 Software support for the M-Cellmicro site for GSM900operation is provided in this release.

Low power DCS1800BTS-site M-Cellmicro

Software support for the M-Cellmicro site for DCS1800operation is provided in this release.

DCS1800 mast mountedpreamplifiers

An independently powered masthead preamplifier forDCS1800 only. The preamplifier is manually configuredon-site. Preamplifier power failure and device failureare reported through a single EAS alarm.

Optional filtering for front end This feature is a receive bandpass filter with a narrowspecification specifically designed for when ETACSfrequency spectrum is used in conjuncture with a GSMnetwork.


02 May 2003


68P02901W01-M 5�25





Feature Description

Transient alarm handling Enables the BSS software to perform more verificationand filtering of fault indications, to eliminate transientalarm messages from the Transcoder TRAU, the RSL,XBL and clock failures. The main impact of this featureis that it decreases the number of alarms reported bythe BSS. This results in less alarm handling requiredat the OMC.

Multiple trigger call traceevents

Enhances existing Call Trace functionality by providinga finer trigger scope for call trace. This feature allowstriggers to be set on a Cell level and multiple Cell level.All current triggering capability is supported on a perCell or per BSS level.

BSS level trace events - RFfailure (RF loss)

Enhances existing RF failure trace functionality byproviding the option to enable RF loss reporting on aper cell basis (previously it was BSS level). It alsoprovides the facility to forward the RF failure traceinformation via the event interface to the OMC

MSI-2 board with E1/T1 MSI-2 boards can be now ordered with either T1 or E1interconnections. The software support at the BSS andOMC is already available to support this.

Direct retry Redirects new traffic when a Cell is congested resultingin the new call being moved to the next most suitableCell.

Congestion relief: directedretry altenative

An alternative to Directed Retry for the case of acongested cell. This feature differs in that it choosesthe best candidates from all existing calls in the cell tobe moved to the alternate cell, thus freeing TCHs in thecongested cell.

Satallite A interface support(optional)

Provides the BSS software support transmission of theA interface via satellite.

Satallite Abis support(optional)

Provides the BSS software support transmission of theAbis interface via satellite.

Optional level 3 password Provides the facility for the BSS MMI security level 3password to be controlled by the OMC operator.

All channels at full power Sets all the call channels in the Cell to broadcast at aconstant power, the power level configured as themaximum transmit power allowed in the Cell. This canbe used for worst case interference monitoring fornetwork optimization.


02 May 20035�26


68P02901W01-M

Feature 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 quickerthan the standard ramp down time. When this featureis enabled a separate power control procedure powersthe MS down rapidly when the BSS detects that thesignal strength of the MS is above the specified triggerthreshold.

Concentric cells (optional) Used in GSM networks with constrained frequencyallocations, to increase network capacity by adding alayer of Cells (known as minicells) on top of theexisting network.

Cell level call trace events Enhances existing call trace functionality by providingthe option to forward call trace information to theOMC-R. This information takes the form of new eventmessages which the OMC-R then stores, as analternative to or in addition to sending it to the MMI.Once sent to the OMC-R, the call trace data is storedin a log file.

Link balance verificationstatistics

The Link balance verification statistics feature willidentify those carriers which have unbalanced uplinkand downlink signal strengths. This feature supportsoptimization activities.

Handover performacestatistics enhancements

Provides a package of enhanced handoverperformance statistics which reduce networkoptimization effort and time.

15,000 TCH support � 1475platform

Provides support for 15,000 traffic channels innetworks where the OMC-R is deployed with a TandemIntegrity 1475 System Processor. Existing OMC-Rsystems deployed with Tandem Integrity S300 SystemProcessors will continue to support 10,000 traffic

Enhanced GSM 12.04statistics compliance

Enhanced GSM 12.04 statistics compliance feature,ensures that the compliance of statistics to the GSM12.04 recommendations will be improved, withadditional OMC-R Key Statistics reports and a packageof additional BSS statistics.

NIU-T1 support for M-Cellsites

Provides the T1 NIU and T1 NIU-m boards toaccompany the E1 NIU and E1 NIU-m boards. M-CellBTSs can now support either T1 or E1interconnections.

M-Cell2/6 MCU redundancy(phase 1)

Provides the information required to install an M-Cellsite to optimize MCU redundancy.

Phase/frequency lock(phase 1)

Provides enhancements to the 1.4.0.x feature, GenericCLocK (GCLK) synchronization.

Synch boot Sync boot is a 1.4.1.1 feature which providesenhancements to the 1.4.0.x feature, M-Cell seriessoftware support.

GSR6 (Horizon II) BSS software release GSR2

02 May 2003


68P02901W01-M 5�27

BSS software release GSR2

GSR2 featuresTable 5-17 summarizes the features provided in the BSGSM-GSR2 release withOMC/BSS software support.

Table 5-17 Release GSR2 features

Feature Description

GPROC2 Supports the introduction of the GPROC2. Because ofthe increased reliability of the GPROC2 board, therewill be a decrease in the BSS unavailability due tounplanned outages. Increased reliability is provided bythe error correcting RAM on the GPROC2 board.

Cell level/carrier level tracing Enhances the existing Call Trace capabilities availablein the BSS.

Call trace via IMSI Allows a Mobile Station (MS) to be tracked as it movesacross the network.

DCS1800 RTC Supports the DCS1800 M-Cell CCB (Cavity CombiningBlock) at M-Cell sites. As a result, the BSS software isrequired to modify the management of remote tunedcombiners at an M-Cell site.

Transcoder On-lineExpansion

Allows the transcoder capacity of equipped transcodercards to be increased while on-line. The BSS remainsavailable while the equipped hardware is increased andconfigured. This eliminates any site outages during theexpansion.

Type 7 MicrocellularNeighbour 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 FrequencyHopping

enhances the operability of the existing hopping featureby introducing the following enhancements:

Hopping timeslots may be locked andunlocked.Carriers or timeslots may be specified ashopping or non-hopping when brought intoservice.When a carrier or timeslot is unlocked, it will bebrought back into service as hopping ornon-hopping based on the databaseconfiguration.Only the affected site will have to be reset forchanges to frequency hopping parameter to beeffective.

Configurable X.25 for BSS Allow the OML and CBL links to have configurableX.25 layer 3 packet sizes and window sizes. Thisfeature will provide MMI commands and OMC interfacesupport for modification and viewing of theseparameters.

Satellite XBL Interface(optional)

provides the BSS software support for transmission ofthe XBL link via satellite.

GSR6 (Horizon II)BSS software release GSR2

02 May 20035�28


68P02901W01-M

Feature Description

Satellite OML Interface(optional)

Provides the BSS software support for transmission ofthe OML link via satellite.

On-Line Add/Copy/DeleteCell BSS Command

Supports the on-line modification to the Cellconfiguration of the SITEs within a BSS, while Cellularservice is maintained to subscribers.

CM Service StatisticBreak-out

Provides call success statistics that more closelymatch MSC statistics. Call success criteria dependupon the service requested.

Upgraded Remote TuningCombiner at 900 MHz

Provides an adaption kit to enable the new M-CellRemote Tuning Combiner, known as CCB, to beretrofitted to BTS4 and BTS6 systems.


02 May 2003


68P02901W01-M 5�29


GSR3 features

Table 5-18 summarizes the features are provided in the BSGSM-GSR3 release withOMC/BSS software support.


Feature Description

Concentric Cells Allows the RF resource allocation for a cell to consistof two frequency channel groups with a single BCCHfrequency to operate in the same coverage area.

Support for Extended RangeCell

Allows the BTS to successfully handle the uplinktransmissions of a MS whose absolute timing advanceexceeds 63 bit periods.

16 kbit/s XBL Eliminates the requirement for a full E1/T1 timeslot foreach XBL.

Non-redundant RTF-PATHFault Containment

Allows a cell to be available for calls even when all ofthe paths on which a RTF is equipped fails, providedthere is another in-service RTF-PATH available for thecell. Traffic capacity can be increased by removing anyredundant RTF-PATHs and using this feature tomanage RTF-PATH failures. This will also result in acell not being barred provided that there is at least onein-service RTF-PATH available for the cell.

PCS1900 MHz Band(M-Cell2/6)

supports the PCS1900 GSM band 8 Watt (after firststage of combining) product on both the M-Cell2 andM-Cell6 BTS hardware platforms. No remote tuningcombining is supported. This feature is for M-Cell2/6only and supports all GSM900/DCS1800 featuresexcept multiband.

Infrastructure Sharing supports cells of different frequency bands in a singleBTS-site. This feature also supports the conversion ofsingle band BTS-BTUs and BCU-BTSs to multibandBTS-sites.

16 kbit/s RSL for PreservingTimeslots

Supports an interface between the BSC and theBTS-site using a 16 kbit/s LAPD and Motorolaproprietary signalling.

Circuit Error Rate Monitor Provides the means for identifying when discontinuity isdetected on a circuit path. The term circuit path refersto the network communication path from the transcoder(XCDR) to the BTS established during a call.

Adjustable Downlink AudioVolume Control

Provides the firmware support for adjustable downlinkaudio volume control in four steps of 2 dB each at thetranscoder.

GDP Support of Dual Rate,Full Rate, and Enhanced FullRate

supports the transcoding functions for full rate,enhanced full rate (EFR) and half rate. The GDPboard is one of the required components of the EFRfeature, which provides better overall speech qualitythan full rate.


02 May 20035�30


68P02901W01-M

Feature Description

Enhanced Full Rate Vocoder Implements the GSM defined Enhanced Full Rate(EFR) for speech. EFR provides a speech service thathas better voice quality than normal full rate speechservice.

Multi-Band Inter-CellHandover

the BSS supports inter-cell handover where cells areoperating in different frequency bands. In addition, thenetwork operator can deploy cells of differing frequencybands within the same BTS-Site(s). For example, asingle BTS-Site may support combination of theDCS1800, PCS1900 and GSM900 cells.

OMC & DataGen commonGUI

Provides BSS support for a common OMC andDataGen GUI.

GPROC2 removes CSFPrequirement

Provides the software support required to reallocateM-Cell specific objects from the BSC CSFP GPROCsto the BSPs which are GPROC2 boards. Thisremoves the requirement of having a CSFP GPROC atthe BSC to support M-Cell BTS sites.

Increased Capacity withGPROC2 as LCF

Allows a single GPROC2 serving as a LCF to support2 MTLs and 15 active BTS-sites. A new databaseparameter indicating the number of links supported ona GPROC2 is created.

MS handover power levelbased on path losscalculations

Sets the MS power level on an inter-cell intra-BSShandover to the target cell based on path losscalculations for promoting battery conservation.

SACCH on a Channel basis Provides BSS support for SACCH system informationon a channel basis.

RTF Subequipping Supports the unequipping of an RTF to reduce thenumber of E1/T1 timeslots required for a site. Aunequipped RTF utilizes a single 64 kbit/s timeslot onan E1/T1 link.

Prefer Different Carrier forIntra-cell handover

Permits a different carrier to be used for an intra-cellhandover when the uplink interference level is thesame.

Micro-micro quality handovers Calls which experience a quality condition in amicrocell will be handed over to another microcell whenpossible.

Timed offset upon RXQUALhandovers

Adds a new timer that may be set up provide anadditional margin to the handover margin to prevent ahandover to a cell with a lower power budget.

Time limitation for excessiveintra-cell handovers

The number of intra-cell channel changes due tointerference can be limited, by performing an intercellhandover when the threshold has been reached.

Remaining 12.04 Statistics(less 3)

Adds a number of raw statistics that are generated atthe BSS to more closely meet the 12.04 GSMSpecifications. In addition, a number of counter typestatistics have been changed to counter array statisticspermitting easier identification and analysis of eventson a cause or scenario basis.


02 May 2003


68P02901W01-M 5�31

Feature Description

DRIM/RCU FW AlarmTranslation Adjustments

Optimizes the handling of DRIM/RCU firmwaregenerated alarms. This prevents spurious alarmsbeing reported to the operator. The Hard Reset alarmwas previously used to indicate a reset of the DRI dueto a recurring fault in addition to an actual hard reset.Now a new DRI alarm (35) has been added to uniquelyidentify this reset reason. DRI 35 is Reset due torecurring fault.

Intra-cell Handover Ping PongProtection

Provides a configurable time interval to reduce pingpong effects. This permits increased handovermargins that may be applied to the original cell whichdiscourage handing a call back.

Enhanced full rate vocodertranscoder

Provides firmware support for the GSM Phase 2+enhanced full rate vocoder (codec) transcoding.

Concentric cells (interferencebased cell resourcepartitioning)

Provides an interference based algorithm which definesthe coverage area of the inner zone for concentric cellstructures.

Handover margin perhandover cause for candidateranking

Provides two new neighbour parameters to be used inthe handover decision process in the case where thehandover was due to RXQUAL or RXLEV. Theseparameters are used to order candidates based on acalculated value. This feature only applies tomicrocells.

Increase BSC capacity withintroduction of GPROC2

Provides BSS support for up to 40 BTS sites, 126cells, 255 carriers, and 1680 trunks.

High power DCS1800 withincreased sensitivity receivermatrix

The result of the receiver sensitivity increase isrestriction of the a single cell in a single cabinet.

Enable Hopping with no SiteReset

Allows frequency hopping parameters may be modifiedwithout resetting the site and normal synthesizer andbaseband hopping to be enabled at different cells in thesame site using synthesizer frequency hoppingenhancement. A site reset will not occur when an FHIis enabled or disabled.

Aggregate Abis Provides support for third-party switching equipmentbetween a BSC and BTSs. Additional flexibility in theallocation of E1/T1 timeslots at the BSC and BTSs isprovided to support the use of a switching network tocombine the timeslots from several low capacity BTSsonto a single E1/T1 link to the BSC.

New Millennium Provides Year 2000 compatibility for the BSS.

PCS1900 mast mountedpreamplifiers

Supports an independently powered mastheadpreamplifier supported for PCS1900

Accelerated Handover toInner Concentric Cell Zone

Provides a mechanism that accelerates handovers tothe inner concentric cell zone for cells using theinterference-based algorithm.


02 May 20035�32


68P02901W01-M


GSR4 featuresTable 5-19 summarizes the hardware/software features provided in the BSGSM-GSR4release with OMC/BSS software support.


Feature Description

Call trace expansion Provides enhanced operator features through the OMCGUI for call tracing.

Carrier prioritization forSDCCH

Provides the operator with the flexibility of prioritizingthe selection of Traffic Channels (TCHs) andStandalone Dedicated Control Channels (SDCCHs) inorder to minimize the overall interference level in aGSM network.

SMS alphabet extensions Adds three new alphabets to the list of defaultalphabets supported by the Short Message Servicefeature.

BTS concentration Provides the customer with an alternative mechanismfor allocating terrestrial backhaul for radio resourcesbetween the BSC and the BTS. This feature preservesthe existing mechanism, but allows the operator thechoice, on a per BTS site basis, of whether to use theexisting 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 whichsupports duplex high speed digital communication (atE1 rates) on one or more unshielded twisted pair lines.

Increased BSC capacity Expands the capacity of a BSC must be GPROC2s forall functions at a BSC.

Terrestrial circuit devicemanagement

Allows the customer to manage terrestrial circuits inmuch the same way as other devices.

Optimized power control Improves uplink and downlink power control. This isdone by adding flexibility in defined power steps,modifying the range of power steps, by allowing powerstep sizes to be changed dynamically, and byperforming downlink oscillation prevention.

Frequency hopping Enables each timeslot to use a set of frequenciesdefined in one of up to four frequency hoppingsystems.

New Millennium Addresses all aspects of the Motorola system; OMC-R,BSS, and the BTS and BSC hardware. It concernsitself with internal clock operation and the use of thedate in various parts of the product, for example withinEvent and Alarm reports.

Enhanced congestion relief Enhances the effectiveness of the congestion relieffeatures which are already in place, having beendelivered by the 1.4.1.0 implementation of theCongestion relief - directed retry alternative featureas well as enhancement PRs to GSR2 and GSR3.


02 May 2003


68P02901W01-M 5�33

Feature Description

GPROC2 required for all BSCprocessors

With the GSR4 software release, all GPROCs at theBSC must be GPROC2s.

BCCH frequency, SDCCH inEGSM

Allows the configuration of BCCH carriers and theplacement of SDCCH channels in the EGSM frequencyband based on an operator defined databaseparameter. It provides the capability for the operator toconfigure a stand alone EGSM cell and enables theoperator to implement a multiband/dual-band networkwith EGSM as one of the supported frequency bands,for example, DCS1800 and EGSM.

Flexible neighbour handling Enhances the existing handover decision process byadding more flexibility in the way neighbour cellprocessing is carried out for handovers.

Coincident multibandhandover

Enables operators to install new radios in a differentfrequency band. This installation will turn ancustomer�s 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 attemptfails.

The OMC provides the appropriate information to remind the operator that the BSC mustbe all GPROC2 boards, before a conventional or CSFP download of release GSR4.

GSR6 (Horizon II)BSS software release GSR4.1

02 May 20035�34


68P02901W01-M

BSS software release GSR4.1

GSR4.1 features

Table 5-20 summarizes the hardware features provided in the BSGSM-GSR4.1 releasewith OMC/BSS software support.

Table 5-20 Release GSR4.1 features

Feature Description

Point-to-point GPRS service. Supports implementation of one to eight timeslots on asingle carrier per cell for the transmission of GPRStraffic. This enables the Network Operator to optimallysize the network for efficient support of a mix of GPRSand voice traffic.

GPRS radio channelallocation.

Provides the flexibility for a cell supporting GPRS toallocate a given radio resource to handle circuitswitched voice/data or packet data as required. A radioresource can be configured as dedicated to circuitswitched traffic, packet data traffic, or switchablebetween the two.

Medium Access Controlmodes: fixed/dynamicallocation.

Includes the functions related to the management ofthe common transmission resources. These include thepacket data physical channels and the radio linkconnections on packet data physical channels.

Support of MS classes. Supports multislot MS classes 1-12, 19 and 20. Thisincludes support of both semi-duplex (classes 1-12)and half-duplex (classes 19 and 20). Semi-duplex MSscan support up to 4 TimeSlot (TS) downlink and 1 TSuplink, or 2 TS downlink and 2 TS uplink. Half-duplexMSs, can support 6 TS downlink or 2 TS uplink, or 1TS downlink and 4 TS uplink (fixed allocation MACmode).

GPRS codes schemes CS-1and CS-2.

Coding schemes CS-1 and CS-2, providing 9.05 kbit/sand 13.4 kbit/s respectively, are supported.

Dynamic adaption of codingschemes.

Enables the network to change the coding schemebetween MS transmissions based upon the radiocharacteristics of the link. Movement between CS-1and CS-2 is supported in the initial GPRS release.

Two phases packet access. Allows an exchange of information to take placebetween the MS and the network prior to assignmentof 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 basedupon the characteristics of the link. Power control issupported over the radio interface on both the uplinkand downlink. Power adjustments are directed by thenetwork based upon the measured characteristics ofthe radio link.

GSR6 (Horizon II) BSS software release GSR4.1

02 May 2003


68P02901W01-M 5�35

Feature Description

Gb interface. Provides connection between the BSS and the SGSN.

PCU load balancing andsharing (Gb and BTS).

Provides high reliability through efficient resourcemanagement. It also manages the movement ofresources from one part of a BSS to another to meetvarying peak capacity requirements in a networkdesigned primarily for coverage.


02 May 20035�36


68P02901W01-M


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

Optimized power control

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 reducingtraffic between the MSC and the BSS. This mechanism allows the MSC to notify the BSSthat it is becoming overloaded and the amount of information being sent to the MSC fromthe BSS should start to be reduced. The BSS receives the notification and starts toreduce the traffic loading on the MSC immediately. The BSS reduces the traffic load onthe MSC by barring mobile access classes within cells in the BSS. The unbarring of theaccess classes to increase the traffic to the MSC is controlled by a timer.


02 May 2003


68P02901W01-M 5�37

SMS CB upgrade The short message service (SMS) cell broadcast (CB) attracts subscribers to the networkby broadcasting information of interest to the general public, for example, roadconditions, traffic information, news flashes, weather reports, etc.

The SMS CB upgrade feature integrates changes made to the ETSI GSM standards andrecommendations since the initial development of the SMS CB features, and providessupport for large SMS CB messages.

The main system changes are:

S Multiple page message support. The initial implementation limited the number ofpages in a WRITE/REPLACE to 1.

S Different message categories. Message categories have been introduced. Thesecategories are defined as High Priority, Background or Normal. The introduction ofdifferent priority messages affects the scheduling of both the message itself andthe DRX scheduling messages. A new message is supported from the CBC whichreserves certain slots for potential High Priority messages.

S 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. Inaddition, the period of the DRX message may be set by the CBC.

S CBC-BSC interface upgrade. The definition of the Repetition-rate parameter haschanged.

S Support of extended SMS alphabets. ETSI 03.38 provides definitions of theextended alphabets which can be used for SMS cell broadcast messages.Extended SMS alphabets are supported for messages which are defined by theCBC. The extended SMS alphabet is not be supported for SMS cell broadcastmessages which are defined via the OMC/customer MMI.

S Backward compatibility. CBC vendors may be working to different versions of GSMspecifications 03.41 and 03.49. A mechanism has been introduced which allowsthe 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 radiodiagnostics to aid in fault detection in the field. Specifically, this feature provides:

S Reduced maintenance costs; through quick and accurate verification of radioserviceability, and prevention of unnecessary site visits.

S Enhanced system operability and reliability; through minimizing operatorprocedures for fault management, and enabling standby devices to be tested todetect latent faults.

S 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 byHorizonmacro.Transmitter output is looped back at the receive preamplifier input (after beingdown-converted to the receive frequency).

S Receive Antenna VSWR. This diagnostic is supported by Horizonmacro.Receive Antenna VSWR testing is first performed by gathering results from theReceive Preamplifier Input Loopback test. Next, the receive-frequency-translatedtransmitter output is directed to the receive antenna and the reflected signalstrength is measured. These two sets of results are used to compute a VSWRmeasurement.


02 May 20035�38


68P02901W01-M

Dynamic allocation of RXCDR-BSC circuits

The dynamic allocation of an RXCDR to BSC circuits feature introduces faultmanagement for call traffic on the BSC to RXCDR interface (referred to as the Aterinterface) by managing the individual 16 kbit/s channels (called Ater channels) on thisinterface. 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 callsare placed on the correct circuit between the BSC and the MSC. Without this feature inplace, no fault management of the Ater channels would be possible, and all Ater and CICinformation must be manually verified by the operator, resulting in a higher Operation andMaintenance (O&M) cost for the Motorola BSS.

The dynamic allocation and release of RXCDR to BSC circuits provides the followingbenefits:

S Simplified network provisioning; there is no need to manually map CICs to Aterchannels at both the BSC and RXCDR.

S Simplified network debugging; via automatic and manual audits of CIC and Aterchannel information between a BSC and RXCDR.

S Better fault tolerance for call traffic, since calls do not necessarily need to beterminated due to a single failure on the linkset between an RXCDR-BSC.

S Better utilization of network resources.

This feature will remain consistent with the Terrestrial Circuit Device Managementfeature, 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) featureimproves the robustness of communication between the BSC and the RXCDR. Thebasis of this feature is to provide a generic messaging system between the BSC and theRXCDR. This generic messaging system is used to suit both current operator needs andthe needs of future BSS features.

Operator-visible aspects of the EXBL feature are that runtime checks of databaseconsistency and connectivity are performed between the BSC and RXCDR to ensure thattraffic 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. Operatorsare notified of any failure of these connectivity checks so that they can take theappropriate action.

In the event of a verification failure, the BSS automatically disables the relevant CICdevices 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.


02 May 2003


68P02901W01-M 5�39

Horizonmicro2 / Horizoncompact2 generic BTS software The BSS software supports the 900/1800 Horizonmicro2/Horizoncompact2 feature as arestrictable feature (Master and Slave combination). The 900/1800Horizonmicro2/Horizoncompact2 feature is available on a per BSS basis. The operator isnot permitted to configure an Horizonmicro2 BTS site in the BSS database, if the900/1800 Horizonmicro2/Horizoncompact2 feature is restricted (specific to theHorizonmicro2/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/1800Horizonmicro2/Horizoncompact2 feature is implemented by modifying existing codeobjects.

Dynamic power control is also supported on the Horizonmicro2 and Horizoncompact2BTSs.

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 basedequipment due to code corruption. It also maintains backward compatibility with previoushardware and software loads.

Code corruption usually occurs during field code upgrades and a power outage disturbsthe programming process. In order to reduce the number of equipment returns,modifications have been made to both software and hardware.

HardwareFlash (non-volatile memory) is doubled in size. The flash is divided into two banks; thefirst bank stores a master copy of the operational code, whilst the second bank stores therecovery copy. A hardware switch is required to select either bank.

SoftwareThe software validates the operational code in both banks of flash. If there are noproblems, then the operation of the equipment is allowed to continue. If one of the bankshas corrupt operation code, then a copy of the valid bank is made to immediatelyoverwrite 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.

S Update TSCs for all timeslots on the BCCH carrier.

S Update TSCs for all timeslots on all carriers of the cell.

Single BCCH for dual band cells The Single BCCH for Dual Band Cells feature is an enhancement to the GSR3 multibandfeature, to allow more efficient network operation by enabling a single BCCH carrier toserve 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 customersneeding T1 support can purchase multiple serial interface 2 boards (MSI-2) as well as theT1 version of the generic DSP (GDP) boards.


02 May 20035�40


68P02901W01-M

Enhanced power outage recovery

The Enhanced Power Recovery feature improves system availability in the event of atotal power loss to the site, by providing a non-volatile storage mechanism for BSSSoftware. 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 MemoryCard (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 thesame BSS software objects as the master GPROC board. When powering up after apower 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 theuplink 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 functionimplemented at the MSC and is beyond the scope of this feature. The granularity of theload distribution is increased from 16 to 64, resulting in a more even distribution of trafficacross 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 MTPLayer 3 test message is added which allows the remote side to determine how the virtualcircuits are distributed over the active MTLs. A database element is added for setting theloadshare granularity to either 16 or 64.

BTS concentration resource optimization for handovers

The BTS Concentration Resource Optimization for Handovers (BCROH) featureoptimizes the terrestrial backhaul between a BSC and BTS during handovers, when theBTS concentration feature is applied. Previously when a handover occurred, a newcircuit for the destination radio channel was always allocated between the BSC and theBTS. The BCROH feature means that if the source and destination BTS in a handoverare the same, then a new circuit is not allocated and the existing circuit is re-used for theradio destination channel. It can only be used in conjunction with BTS equipment thatsupports BTS concentration.

The BCROH feature reduces the number of resources required when intra cell handoversor inter cell handovers (within the same site) occur and are controlled by the BSC. Inthese handover scenarios the switch connections for the voice traffic from the radiochannel to the MSC are no longer made at the BSC during the handover. The BTS toMSC path remains constant and the BTS must simply move the switch connection of theAbis circuit from the source radio channel to the destination radio channel.

Handover parameter

The Handover parameter reorganization/reduction (also referred to as RSS BinReduction) feature, removes a number of unused bins allocated to each of the radiosubsystem (RSS) handover and power control algorithms. It cleans up previously wasteddatabase 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 missingmeasurement report will be supported by CM/MMI commands.


02 May 2003


68P02901W01-M 5�41

Per neighbour area for adaptive handovers The adaptive handover methodology allows handovers to occur more rapidly whenconditions are deteriorating quickly and less rapidly when conditions are only marginallypoor.

This enhancement to adaptive handovers provides the operator with the option of settingthe cumulative area for adaptive power budget handovers on a per cell or per Neighbourbasis.

Optimized power control This enhancement to the existing optimized power control feature, allows the operator toenable 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 levelthreshold. If the algorithm is enabled, power level reduction step sizes can be changeddynamically, based on the current proximity to the upper power level threshold. This willallow the power to be brought down at a faster rate when it has strayed out of the powerbox. 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 chosenwithout 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 numberof 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 isan 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 CICsrepresents 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.

S Meaningful call quality metrics for hopping network benchmarking and healthreporting.

S 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-emergencycircuit switched calls are pre-empted by emergency calls.

This feature pre-empts circuit switched calls based on priority as well as age. The BSSattempts to pre-empt a non-emergency circuit switch call with the lowest priority first anda non-emergency circuit switch call with the highest priority last. If two calls exist with thesame priority level then the oldest is chosen first.


02 May 20035�42


68P02901W01-M

GPROC function pre-emption

This feature searches for a Busy-Unlocked generic processor board (GPROC) running alower priority function, when a GPROC hosting a higher priority function goes out ofservice, 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 priorityfunction. The operator is able to configure the pre-emption algorithm using a databaseelement.

The levels of pre-emption that can be configured are:

S No pre-emption.

S 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 thehighest function id will be pre-empted.

S Intra function level preemption: If a function of lower priority is running on aGPROC, that function will be pre-empted. If a GPROC running an LCF goes out ofservice and there is no lower priority function type (e.g. BTF) running on a poolGPROC, 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. Thisfeature brings the CAGEs at InCell BSCs and RXCDRs into service in parallel. Cages atan InCell BTS site will be brought into service in parallel when the master BTP is aGPROC2.

Cages at an InCell BTS site will continue to be brought into service serially when themaster BTP is a GPROC1.

Enhanced MMI link device warnings

MMI issues confirmation warnings when the operator uses the lock, ins_device, orreset_device commands on some link devices. Additionally, in some cases, MMI issuesconfirmation warnings when an MSI, MMS, or DPROC is locked and it has an associatedlink device.

The Enhanced MMI Link Device Warnings feature addresses a number of problems thatexisted with the MMI link device warnings. The previous link warnings have beenreplaced with a new, comprehensive set of warnings.

The affects of this feature are:

S MMI issues a warning message and prompt for confirmation whenever the lock,ins_device, or reset_device commands are used on a link device.

S 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 supportslink devices.

S MMI issues confirmation warnings for link devices regardless of their current state.

S The warnings that MMI issues for link devices define the link affected and theconsequences of locking the link device.

S The warning that MMI issues for a particular link device is the same for all of theMMI state change commands.


02 May 2003


68P02901W01-M 5�43

BSS software release GSR5.1

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 itto the Serving GPRS Support Node (SGSN) (GSM 08.18). This feature enables the BSSto communicate the suspend message to the SGSN.

Feature description

When a GPRS attached MS enters CS dedicated mode to answer a CS page, and MSlimitations make it unable to continue to communicate for GPRS, the MS will request tosuspend GPRS services. The BSS processes this message from the mobile to suspendits GPRS service and sends a suspend message to the SGSN via a Gb link (interfacebetween an SGSN and a BSC.

The SGSN, in turn, does not initiate any paging for this mobile while it�s in the suspendstate. 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 20035�44


68P02901W01-M


Feature overview

The GPRS Coding Scheme 3, Coding Scheme 4 (CS3/CS4) and 32 kbits/s TranscoderRate Adaption Unit (TRAU) feature implements an alternative channel coding algorithmover 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 CodingScheme 4 are software changes. There are no hardware modifications or additionsnecessary to support this feature.

32 kbps TRAU channels

The BSS supports 32 kbits/s TRAU channels that are comprised of two independentlysynchronized 16 kbbits/s TRAU channels. Both component 16 kbits/s TRAU channels ofany given 32 kbits/s TRAU channel reside on a single GDS to ensure that a single TRAUprocessing entity can handle the reassembly of the individual channels.

CM database parameters

Additionally, two new CM database parameters are necessary to control whether or notthe CS3, CS4 and 32 kbits/s TRAU is allowed in the BSS. If CS3, CS4 and 32 kbits/sTRAU is allowed in the BSS, then cs34_enabled must be enabled. To support thefeature on a per carrier basis, every timeslot dedicated to GPRS must have sufficientbackhaul present to support the 32 kbits/s TRAU. This is enabled by a per carrierparameter as part of the equip_rtf command called allow_32k_trau.

New statistic

A new statistic GPRS_32K_CHANNELS_SWITCHED is introduced to complement theCS1 and CS2 statistics that are currently implemented.

Dynamic allocation

The use of the dynamic allocation feature in conjunction with the CS3, CS4 and32 kbits/s TRAU feature is not supported at this time. In a network at sites usingdynamic 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/sTRAU, consequently no additional restrictions need be placed on the carriers or RTFequipage due to this feature.


02 May 2003


68P02901W01-M 5�45

GPROC fast reset

Feature overview

The Fast Reset (Soft Reset) feature enables a GPROC to come back into servicequicker, when recovering from a fatal Software Fault Management (SWFM). If theGPROC is functioning as the master BSP/BTP, then the fast reset feature has the effectof bringing the site into service sooner. This feature reduces the outage time for theinvolved 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 GPROCstransition software from RAM back to RAM during a reset, without going through theROM process. The differences between a RAM-RAM software transition verses aRAM-ROM software transition is that the RAM-RAM procedure does not execute thefunctionality in ROM, as it is passed over.

During a RAM-RAM software transition, the GPROC that incurred the fatal SWFM istaken off the LAN and all TDM connections for that GPROC are cleared. Then, insteadof performing a software transition to ROM, the GPROC comes back on the LAN in RAMand performs the RAM initialization procedure.

The theory behind the fast reset feature is that a process executing in RAM, whichencounters a bus fault or any other fatal SWFM event, does not need to go through theROM transition to restore the GPROC. By halting all processes on that GPROC andreinitializing it, the fault generating condition should no longer exist. If the fatal SWFMcondition still exists, an escalation mechanism eventually transitions (points) the GPROCsoftware into ROM.

Unequip of TCU/CTU cabinets

This feature enables the unequippage of extension cabinets of types TCU_2, TCU_6 andHorizonmacro_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 orEASs 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 usingfeatures already introduced in prior releases.

1900 MHz Horizonmacro

Provides software support for for a BSS to operate in the 1900 MHz frequency rangeusing features already introduced in prior releases.


02 May 20035�46


68P02901W01-M


The Single BCCH for Dual Band Cells feature is an enhancement to the GSR3 multibandfeature, to allow more efficient network operation by enabling a single BCCH carrier toserve 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 concentriccells configuration.

S The operator can define the coverage area of the secondary band by use of BSSdatabase parameters.

S Channel algorithms are supplied to incorporate selection of channels from differentfrequency bands, and ensure the allocation of a secondary band (inner zone)resource at TCH assignment when required criteria are met.

S Power level conversions are provided for intra-cell channel changes and incominginter-cell handovers between channels on different frequency bands.

Other optional features that must be unrestricted in order to configure dual band cellsare:

S Multiband handover - see Multiband intercell handover in the BSS softwarerelease GSR3 section.

S Concentric cells - see Concentric cells in the BSS software release GSR3section.

S Dual band cells - see BCCH frequency, SDCCH in EGSM in the BSS softwarerelease GSR4 section.

S The functions of these features on which the Single BCCH for dual band cells isdependent are described in this manual. A technical description of the SingleBCCH for dual band cells feature, and these features are contained in the manualTechnical Description: BSS Implementation (68P02901W36).

Homogeneous cabinet - see the equip CAB command in the manual TechnicalDescription: BSS Command Reference (68P02901W23).

Heterogeneous cabinet (for combined cabinet configurations) - see the equip CABcommand in the manual Technical Description: BSS Command Reference(68P02901W23).


02 May 2003


68P02901W01-M 5�47


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 20035�48


68P02901W01-M

Enhanced Circuit Error Rate Monitor

Feature overview

The original Circuit Error Rate Monitor (CERM) optional feature provides a means foridentifying when discontinuity is detected on a circuit. The customer can:

S Reduce cost of ownership

S Reduce downtime of devices

S Enhance system operability

S Enhance quality of service.

A circuit is considered to be the path along which a connection is made, from the entrypoint in the BSS (e.g. a radio at the BTS) to the exit point in the BSS (e.g. the MMStimeslot that connects to the MSC or PCU).

The CERM is used to monitor the continuity and sanity of hardware processing elementsin a circuit, on a per call basis. Whenever a discontinuity is detected for a circuit during acall, error counts are updated for the points monitored for the call. When the error countat a particular monitoring point reaches or exceed an operator specified threshold, analarm is generated. The alarm contains information identifying the monitored path inwhich the error is detected, thus allowing the operator to identify potentially faultydevices.

Feature description

The CERM feature is enhanced, enabling the monitoring at various points in a GSMnetwork circuit, thus improving the ability of a operator to narrow down where a faultydevice may be located. Although having these monitoring points in the circuit pathnarrows down the list of potentially faulty devices, it does not confirm that a device isfaulty. 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

S ATER Channel Identifier (ACI) groups on a link between the RXCDR and the BSC.

S GPRS Circuit Identifier (GCI) in the radio hardware.

S Radio Channel Identifier (RCI) in the radio hardware.

S 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, forexample, with a path leading from a BSC to two daisy chained BTSs, the PIC for thesecond BTS encompasses the path through the first BTS to the BSC.


02 May 2003


68P02901W01-M 5�49

Multiple GPRS carriers per Cell

Feature overview

Before GSR6 the Motorola GPRS product offered the capability to configure up to eightGPRS TimeSlots (TSs) on a single carrier in a cell. The increase in packet data trafficand availability of multiple timeslot GPRS MSs have increased the need for additionalGPRS capacity.

The Multiple GPRS carrier feature enables the network operator to configure multipleGPRS carriers per cell for increased GPRS traffic handling capability to meet thisincrease in packet data traffic and the expanding base of GPRS subscribers withincreased data throughput.

The operator is offered two options to configure GPRS TSs on multiple GPRS carriersper cell:

S Configure for performance,

S Operator specified.

Configuration performance

Configure for performance provides the network the capability to configure all thereserved 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 schedulingpacket data and the capability to service multiple TS GPRS mobiles.

Table 5-24 is an example of multiple GPRS carriers where the default option, configuredfor performance, is specified. The GPRS resources are configured contiguously onGPRS carriers in the cell to maximize performance. The cell has five GPRS carriers, tenreserved 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



02 May 20035�50


68P02901W01-M

Operator specified

The operator specified option provides customers with the flexibility to configure themaximum and minimum number of reserve and switchable GPRS timeslots on a percarrier basis in a cell. Table 5-25 is an example of GPRS timeslots distributed overcarriers in the cell. The cell has five GPRS carriers, ten reserved timeslots and elevenswitchable 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


When a carrier that has GPRS timeslots goes out of service, GPRS timeslots will bereconfigured on a different carrier that supports GPRS based on the radio resourcesavailable in the cell.


Feature overview

Enhanced GDP provisioning is an enabler for future features which require a reduction inboard channel capacity e.g. AMR.

A GDP is an Generic Digital Signal Processor (DSP) Processor board. It isinterchangeable 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 andphase 2 data services.

S Enhanced - Transcoding for future applications, particularly Adaptive Multirate(AMR) speech coding, in addition to existing GSM Full Rate speech, EnhancedFull Rate speech and phase 2 data services.


Enhanced GDP Provisioning:

S Supports GDPs that are capable of enhanced transcoding, particularly AMRspeech coding, in addition to supporting current transcoding services.

S Allows GDPs to provide additional enhanced transcoding resources only withoutmaking use of the E1 or T1 line interfaces.


02 May 2003


68P02901W01-M 5�51

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 providebasic transcoding, or be paired with a Secondary GDP to provide enhancedtranscoding. Primary GDP can provide Enhanced transcoding only.

S A Secondary GSD in a pair provides DSPs for transcoding for a set of CIC devicesrouted to the MSC via the E1 or T1 interface of a Primary GDP. Secondary GDPcan provide Enhanced transcoding only.

The Enhanced GDP provisoning feature performs the following functions:

S Supports provisioning for GDPs which are capable of enhanced transcodingfeatures, particularly AMR, in addition to supporting current services. Before thisfeature, transcoding was performed by 15 DSPs on a GDP processing 2 callseach. The processing requirement for future features demands that each of theDSPs processes a single call. A pair of GDPs are required for provisioning of 30transcoding circuits on an individual E1 link to the MSC, or 24 on a T1 link, whichare capable of the enhanced transcoding features.

S Supports provisioning for GDPs to provide additional enhanced transcodingresources 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, thefollowing 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 GDPor, if the MSC MMS is the GDP�s own MMS, it is equipped (automatically). A GDP canonly provide an MSC MMS for one secondary GDP.


02 May 20035�52


68P02901W01-M

Call downgrade on CIC capability mismatch

Feature overview

The call downgrade on CIC capability mismatch feature resolves erroneous call handlingthat could cause loss of speech due to the requested speech version not matching thecapabilities of the underlying transcoding equipment.

This feature also enchances the support of the Generic DSP Processing board, addingEnhance Full Rate capability as well as allowoing a staged migration to future advancedtranscoding technologies such as AMR.

Feature description

The Generic DSP Processor (GDP) board was introduced into the BSS and RXCDRs tosupport EFR speech as the previous transcoder, the XCDR was not re-programmableand 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 beGDPs. With local transcoding, this was easily enforced by not enabling EFR if XCDRboards were fitted at the BSC. However, for remote transcoding, because no specificsignalling in terms of capabilities exested between the BSC and RXCDR, EFR could beenabled at the BSC even though the RXCDR contained XCDRs.

Pooled transcoding at the MSC and the RXCDR was introduced to support thisco-existence of XCDRs and GDP within the BSS. EFR capable CICs terminating on GDPboards, FR capable CICs terminating on XCDR boards with data services beingsupported by both types of transcoder.

This configuration is satisfactory provided the pool of transcoders at the RXCDR matchthat of the MSC. However, if mismatches do occur, EFR calls could be routed to XCDRboards, resulting in calls with no speech.

Call downgrade on CIC capability mismatch resolves this problem by allowing theco-existence of differing capability platforms, which match the capabilities of theunderlying hardware with those for incoming call requests. These are:

S Calls specifying a preference for EFR, but also allowing the use of GSM FR, woulduse EFR when utilizing a CIC supported by a GDP board.

S Calls specifying a preference for EFR, but also allowing the use of GSM FR, woulduse GSM FR when utilizing a CIC supported by a XCDR board.

S Until the inclusion of AMR capable hardware is available, requests for AMR wouldbe targeted to match the capabilities of the associated CIC or supporting hardwareand use either GSM FR or EFR.

It also enhances the capability of the Generic DSP Processing board by adding EFR andallowing a staged migration to AMR.


02 May 2003


68P02901W01-M 5�53

This feature introduces the following:

S Mutli-platform support

Support of transcoding platforms with different capabilities within the BSS, that isto say, to allow the XCDR and GDP boards to co-exist within the same BSC (in thecase of local transcoding) or RXCDR (in the case of remote transcoding).

S Enhanced CIC management

Detection of CIC speech version capabilities by the BSS, based on the supportingtranscoding platform.

S Enhanced call management

Validation of MSC call setup, in-call modification and handover requests to ensurethat the given permitted speech version(s) included are supported by the specifiedCIC.

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 thepacket 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 andrebuilding of the resources in the data services.

A problem with the previous design was that once the PCU reset itself, it tookunnecessary time to re-establish the link between the BSC and PCU and then to bringback the PCU into service in order to process data calls again.

NOTE If no GSL connection is made within 30 minutes the PCU will gointo 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 andPCU from unstable GSLs.

This feature enhances the availability of the PCU by preventing the PCU from resettingupon the last GSL disconnection and quickly brings it up in service again upon the GSLreconnection. When the last GSL goes out of service, the system software in the PCUand BSC now manages and reconfigures the network resources promptly, smoothlydeallocating the resources for data calls and reallocating them for voice calls.

This feature also improves the problem analysis of the PCU because the processes onthe PCU stay up and continue to run during the last GSL failure allowing the operator tointerrogate the processes for problem analysis, locally.


02 May 20035�54


68P02901W01-M

Network Controlled (NC1 and NC2) cell reselection

Feature overview

In a GPRS network, cell reselection is equivalent of a GSM circuit switched handovertriggered by, for example:

S change in location of the mobile,

S change in RF conditions,

S cell congestion.

GPRS cell reselection offers mobility and performs network traffic management. Thedifferent modes of cell reselection in GPRS network are referred as NC0, NC1, NC2 andRESET. In the initial Motorola GPRS product offering, NC0 was provided. In cellreselection mode NC0, the mobile performs autonomous cell re-selection based upon onthe radio environment. This feature release provides the remaining two modes of cellreselection NC1 and NC2 to enhance the existing product offering. Table 5-26 shows thedifferent cell reselection modes, responsible network element and functionality.

Table 5-26 Cell reselection modes

Cellreselection

mode

Control element Functionality


Autonomous cell reselection.

Enhanced NC0 MS control Functionality in NC0 mode plus:

BSS sends cell reselection commands toGPRS MS to change cell reselection mode.


Autonomous cell reselection,

MS sends measurement reports to BSS.

Enhanced NC1 MS control Functionality in NC1 mode plus:

BSS sends cell reselection commands toGPRS MS to change cell reselection mode.

NC2 Network control MS sends measurement reports to BSS,

BSS sends cell reselection commands toGPRS MS,

BSS instructs MS to perform cellreselection.


02 May 2003


68P02901W01-M 5�55

Feature description

In the current Motorola GPRS network, the MS autonomously performs cell reselectionbased solely on the RF measurements of the serving and neighbouring cells. The GPRSMS is unable to reselect to a neighbour cell based on important factors: such ascongestion, availability of GPRS, ability to support mobiles and current grade of service.

The main objective of the network controlled cell reselection and congestion relief featureis to increase network capacity and to provide the network operator with a tool fornetwork planning and improved quality of service. The operator is able to specify GPRScell reselection mode on a per cell basis, within the network of cells with the same cellreselection command, thus providing the flexibility of virtual zones . A significant portionof this feature incorporates the addition or modification of statistics that reflect radioconditions at the MS and congestion in the GPRS network. Benefits of statisticscollection are as follows:

S Provide network information to change cell reselection mode on a per MS basis,

S Provide information to monitor network radio and congestion information todetermine and perform cell selection,

S Provide network planning information and configuration of NC2 mode parameter.In cell reselection mode, NC2 enables the BSS to take appropriate action toreduce congestion if the originating cell is congested.


02 May 20035�56


68P02901W01-M

Location services

BSS location services support

The Location Services (LCS) feature implements emergency services functionality inGSM systems (compliant with the Federal Communications Commission (FCC) 911requirements) in two phases:

Phase 1 To transmit the originating number of an emergency call (911in the United States) and the location of the serving site to thePublic Safety Answering Point (PSAP).

Phase 2 To transmit the emergency caller�s estimated position,expressed in latitude and longitude coordinates withinspecified limits of accuracy.

Applications that request location estimates from location services can be located in theMS, the network, or externally to the PLMN.

LCS positioning mechanisms

LCS currently specifies three positioning mechanisms in order to determine the locationof a Mobile Station. These positioning processes involve two main steps: signalmeasurement and position computation based on the measured signals. The standardSMG (Special Mobile Group) positioning mechanisms are:

S Network-based uplink Time of Arrival (TOA),

S Enhanced Observed Time Difference (E-OTD),

S Assisted GPS (A-GPS).

Conventional GSM Timing Advance (TA) measurements can also be used in conjunctionwith Cell ID determination to provide a coarser, lower quality location estimate.

Examples of applications to which LCS MS position determination can be applied are todeliver tailored content to MSs in a physical locality (location specific advertising), or todetermine the routing of voice traffic (location sensitive routing). Motorola supportsTiming 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 timingadvance measurements, the frequency of sending of which is specified by thetiming_advance_period parameter. The timing advance value is known for the servingBTS and when returned to the requesting LCS client, with the cell ID, provides theapproximate physical position of the MS.


02 May 2003


68P02901W01-M 5�57

Basic MPROC redundancy

Feature overview

The purpose of the complete Master Processor (MPROC) redundancy feature is tosupport a 2N redundancy scheme for the MPROC hardware within the Packet ControlUnit (PCU) platform.

NOTE 2N Redundancy is also called pair redundant. Essentially, itmeans that there is twice the amount of hardware than therewould be for a non-redundant system. One unit is active whilstthe 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 ControlUnit (PCU) with a second MPROC board waiting in standby mode. Should the activeboard fail or go out of service for some reason, the standby MPROC will automaticallytake over control of the cage and continue normal system operation.

NOTE MPROC failure will result in a PCU cage reset until the reserveMPROC assumes control.

In addition to supporting the redundant hardware, this feature focuses on providing a fastrecovery from failures of the active MPROC. In the worst case, the PCU should make acomplete recovery within three to five minutes of the failure.

Feature description

This particular feature supports two MPROC boards within the PCU cage and providesfor an automatic switchover to the redundant board, should the active board fail. Thefollowing 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 PCUwill remain out of service until field personnel are able to perform an on-sitereplacement of the faulty board. Once the board is replaced, the PCU will remainout 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 untilthe on-site replacement can be made.

S Detection of MPROC failures:

The redundant hardware will constantly monitor the other MPROC board. Whenthe redundant board detects the active board is no longer in charge of the PCUcage, the redundant will assume that the other board has failed and, therefore,take over ownership of the cage (and re-initialize the PCU accordingly). Althoughthe assumption made by the redundant board may be incorrect, the operation ofthe PCU will not be adversely affected, the only consequence is a longer recoverytime than would be necessary under ideal conditions.

S Improved recovery times:

While this feature is not introducing ideal recovery times, this feature will be able torecover from MPROC software faults faster than if redundant hardware were notpresent. This improvement is possible because the PCU may begin recovery assoon as the active board fails. Without this feature, the PCU would not be able tobegin recovery until the failed MPROC finished resetting.


02 May 20035�58


68P02901W01-M

Enhanced BSC capacity phase 2

Feature overview

This feature increases the number of carriers to 512 and the number of Circuit IdentityCodes (CICs) to 3200.

The feature supports the following configurations:

S The BSS supports the standard database configuration for 384 carriers if theenhanced BSC capacity feature is restricted.

S The BSS supports the standard database configuration for 2400 CICs if theenhanced BSC capacity feature is restricted.

S The BSS supports the enhanced database configuration for 512 carriers if theenhanced BSC capacity feature is not restricted.

S The BSS supports the enhanced database configuration for 3200 CICs if theenhanced BSC capacity feature is not restricted.

To increase the number of CICs to 3200, 27 BSC-RXCDR connectivities are required atthe user interface, as each connectivity is equivalent to a physical MMS port / 2.04Mbit/slink 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 increasedfrom 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 awatchdog timer. A low-level software process on the board resets the timer on a regularbasis 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 whichthen attempts to collect information about the current task, stores its registers/stack incompact Flash memory, and then immediately resets the board. Upon subsequentinitialization of the board, the software reads the compact flash memory and if anywatchdog reset information is stored, prints that information out to the internal ExecutiveMonitor (EMON) program.


02 May 2003


68P02901W01-M 5�59

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 UniversalMobile Telecommunication System (UMTS) or 2G GSM.

Feature description

Current evolving 3G UMTS networks soon will allow operators to provide UMTScoverage along with GSM/GPRS coverage in their networks.

This feature enables a multi-RAT Mobile Station (MS), a mobile station that can functionin multiple Radio Acess Networks (RAN) to hand over calls between a GSM RadioAccess Network (RAN) and a 3G UMTS Radio Access Network (UTRAN). To accomplishthis, support is needed from the MS, Core Network elements of the MSC andUMTS/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 idlemode.

S 2G (GSM) to 3G (UMTS) cell reselection in idle mode.

Being a completely new GSM function, a full description is available in the TechnicalDescription: BSS Implementation (68P02901W36) manual.


02 May 20035�60


68P02901W01-M

Clean install (E3x00)

Feature overview

The purpose of this feature is to install the OMC-R on an E3000/E3500 server. As Sunare making their current Solaris system obsolete, from 2001 only Solaris 8 is shipped.Therefore, the Operations and Maintenance Centre-Radio (OMC-R) has its operatingsystem 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 fromSolaris 2.51 to Solaris 8 is included in the OMC-R Upgrade.

A Solaris 8 licence is provided as part of the GSR6 package.


02 May 2003


68P02901W01-M 5�61

GPRS interleaving TBFs

Feature overview

This release is an extension to the software feature which introduced the General PacketRadio Service (GPRS).

The Interleaving Temporary Block Flow (TBF) feature allows the rapid multiplexing ofRadio Signalling Link (RLC) data blocks of many different MSs onto a common airresource. Multiple MSs are then able to share a common air resource although effectivethroughput 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 sharedresource 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 theremaining 30% of the timeslot. This is illustrated in Figure 5-1.

Figure 5-1 Example of Interleaving DL TBFs

MOBILE A

MOBILE B

= IDLE RLC BLOCK = RLC DATA BLOCK

RLC DATA BLOCKS

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, inwhich two or more MSs are multiplexed on a timeslot with the capability of switchingbetween 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 TBFsetup phase, TBF release phase, or data transfer phase of other TBFs belonging to otherMSs.


02 May 20035�62


68P02901W01-M

Delayed release of downlink TBF

NOTE Delayed release of downlink TBF is sometimes known asSupercoattail.

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. Bydelaying the downlink TBF release, there is no need to send a new Packet DownlinkAssignment (PDA), allowing data to be sent straight away in the next block period. It alsomeans that if the MS uplink needs to be established while being polled during theextended downlink TBF period, the CCCH and RACH do not have to be accessed, and achannel request in the DAK message is sent instead, reducing the UL TBF establishmenttime 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, interferenceto other MSs transferring data can be caused. To reduce this interference, the CS1 datablocks corresponding to the dummy LLCs are only sent on the Packet Associated ControlChannel (PACCH) timeslot when the MS needs to be polled.


02 May 2003


68P02901W01-M 5�63

Link utilization improvements

Feature overview

Previously, within the BSS software, the signalling messages exchanged between theRadio Sub System (RSS) and Packet Resource Manager (PRM) processes, over theRadio Signaling Link (RSL) and the GPRS Signalling Link (GSL), had a large headercompared with the data part of the message and consequently this produced atransmission delay. In addition, the BSS software sent one message per Link AccessProcedure for ISDN D-Channel (LAPD) frame on the RSL and GSL links; this did not fullyutilize the maximum size of the LAPD Unnumbered Information (UI) frame.

This feature improves the performance of the RSL/GSL links and alleviates the expectedpressure on the capacity and speed of the links from the expanded capacity and highspeed GPRS features. The link utilization improvements feature reduces the messagetransmission time between the BTS and PCU for the InCell, Horizonmacro andHorizonmicro/Horizoncompact by 35% to 40%, 20% to 35% and 15% to 30%respectively. The number of GPRS timeslots that the RSL can support should beincreased by 40% in most GPRS BTS configurations.

Feature description

The link utilization improvements feature addresses the above issues to speed upmessages exchanged between the RSS and PRM. The following enhancements havebeen made:

S Smaller header for delivering messages between the RSS and PRM

The new message header is eight bytes and contains minimum informationnecessary to deliver the messages between the two processes. The functionalityof the existing routeing functions will not change and a new set of routeingmethods and Application Programmer Interfaces (APIs) are created for theapplication processes to use.

S Message packing/unpacking mechanism at the RSL and GSL end-points

This improves both speed and utilization of the RSL/GSL links by packing morethan one signalling messages into the same LAPD frame thus reducing the LAPDheader overhead. Messages waiting in the RSL/GSL mailboxes are packed in oneLAPD frame before writing it to the link, and it is unpacked when it is read from thelink.

S Creating a high priority mailbox

The feature creates a high priority mailbox call LUI mailbox in the Executive Data LinkService Process (Exec DLSP) for certain high priority messages between the RSS andPRM. This mailbox is created at both the BTS and PCU. This enables processing ofmessages in the LUI mailbox at a higher priority than messages in all other RSL/GSLmailboxes.

The RSS and PRM uses the small header with high priority for only certain highpriority messages. The messages sent with this option are routed to the LUImailbox and all other messages between the RSS and PRM (using the smallheader/normal header) are sent to the RSL/GSL mailboxes. With this feature, theRSS 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 LUImailbox.

Normal priority messages with small headers, which go to the RSL/GSLmailbox


02 May 20035�64


68P02901W01-M

Advanced load management for EGSM carriers

The advanced load handover management function offers the operator the ability tospecify EGSM band handovers only to other EGSM bands. Otherwise EGSM handoverscan occur to neighbouring cells that may not have an EGSM band available. DCS1800bands may be used wastefully, particularly if the band_preference parameter is set, forexample, to DCS1800. A new parameter bss_egsm_alm_allowed enables the featureand EGSM handovers will occur to EGSM sites if available, whatever the setting ofband_preference.

When a handover is triggered with this feature set, the neighbour list of an EGSM MS onan EGSM resource is manipulated such that EGSM internal neighbour cells are givenpreference over non-EGSM neighbour cells.

Enhanced GPRS One Phase Access

Feature overview

This feature enables Enhanced General Packet Radio Service (GPRS) One PhaseAccess 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 toestablish an uplink TBF. The packet access can be done in either one phase or in twophases. In the current GPRS software architecture, the Base Station System (BSS) onlysupports the two phase access procedure. The intent of this feature is to introduce theone phase procedure, as well as improvements to both procedures.

Enhanced GPRS One phase uplink TBF access is an improvement over the two phaseuplink TBF access procedure. In a one phase uplink TBF access, the MS initiates anuplink TBF by sending a Random Access Channel (RACH) to the BSS. The RACH isreceived at the BTS, which is then forwarded to the PCU. The PCU responds to theRACH with a Immediate Assignment message containing an uplink assignment. The MSmoves to the assigned Packet Data (Traffic) Channel (PDTCH) and begins its uplink datatransfer. This procedure allows the MS to gain access to the network much quickerwhen comparing against the Two Phase establishment procedure.

Refer to Technical Description: BSS Implementation (68P02901W36) for a full descriptionof the differences between the two access methods.


02 May 2003


68P02901W01-M 5�65

Remove support for collocated BSC

Feature overview

Support for the collocated InCell/BSC will be disabled in GSR6 to enable compressedBTS objects to be stored at the BSC in order to free up memory for new GSM and GPRSfeatures.

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 inorder to free up memory for new GSM and GPRS features

Support for the collocated InCell/BSC will be disabled by blocking access to keycommands 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 beconverted to standalone InCell and BSC sites.

S All collocated BSCs should remain at pre-1650 release, while remainder of networkwill 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 atthe BSC and uncompressing them at the BTS. In addition it will speed up OMC to BSCand 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 buildand are stored in compressed form at the BSC to save memory.

The compressed objects are downloaded to the BTS and uncompressed as part of BTSinitialization.

GSR6 (Horizon II)BSS software release GSR6 (Horizon II)

02 May 20035�66


68P02901W01-M

BSS software release GSR6 (Horizon II)

GSR6 (Horizon II) features

Table 5-27 summarizes the BSS features provided at software release GSR6 (HorizonII).

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

The Horizon II feature comprises the following elements:

S Double density carrier CTU2 transceiver

S Support of up to six double density CTU2s in the Horizonmacro andHorizon II macro platforms.

S 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 ordual carrier mode. It is backwards compatible with the Horizonmacro platform, and maybe operated in single or dual carrier mode in both the Horizonmacro andHorizon II macro BTS cabinets.

Combinations of TCU-A, TCU-B, CTU and CTU2 in single carrier mode and dual carriermode 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 .

GSR6 (Horizon II) BSS software release GSR6 (Horizon II)

02 May 2003


68P02901W01-M 5�67

Table 5-28 CTU and CTU2 output power capabilities

Horizonmacro Horizon II macro

Transceivertype

Combining EGSM900 DCS1800 EGSM900 DCS1800

CTU None 40 32 N/A N/A

External 20 16 N/A N/A

CTU2Single carrier

None 40 32 63 50Single carrier

mode Internal 20 16 28 22

CTU2D al carrier

None 10 10 20 16Dual carrier

mode Internal andexternal

4.5 4.5 9 7

In single carrier mode the CTU2 capabilities are similar to those of the existing CTU, andthe CTU2 can be used as a replacement for the CTU providing GSR6 (or later) softwareis used.

In dual carrier mode, the CTU2 enables the Horizonmacro or Horizon II macro to supportup to twelve carriers. There are however certain restrictions when the CTU2 operates indual carrier mode:

S Baseband hopping is not supported when the controlling cabinets are eitherHorizonmacro or M-Cell, due to the switching capability of the MCU/MCUF.

S Maximum output power capacity is reduced due to internal combining within theCTU2.

S In Horizonmacro cabinets, maximun output power of a CTU2 in either singledensity or dual density modes, is also restricted by the Horizonmacro cabinetpower supply.

S Remote Tune Combining (RTC) is not supported if the CTU2 is operating as amaster or standby controller of an RTC, however RTC can be used if the CTU2 isnot the master/standby controller.

S Both carriers must be in the same cell because the CTU2 has one single RFoutput.

The Horizon II macro BTS can be either the controlling cabinet or extension cabinetconnected to a controlling Horizon II macro/Horizonmacro/M-Cell BTS cabinet.

NOTE BTS sites with Horizonmacro/M-Cell6 as the controlling cabinetmust have a PCMCIA card fitted for CTU2 to be supported.

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 intwo Horizonmacro/Horizon II macro cabinets.

S Horizon II macro Site Controller (H2SC) with integrated NIU and FMUX, E1support and enhanced E1 redundancy, and Increased removable flash media.

S SURF2 (Sectorized Unified Receiver Front end)

S XMUX

S Site I/O Panel

S Increased Radio Signalling Link (RSL) functionality

S Interoperability with the existing Horizonmacro/M-Cell BTS platform.

S Horizon II macro cabinets only support a single frequency band, 900 or 1800 MHz.Multiband cabinets are not available.


02 May 20035�68


68P02901W01-M

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), InterleavingTBFs (RDB4253), and Enhanced one phase access (RDB4386) features introduced inGSR6.

This feature improves MS GPRS performance by allocating multiple timeslots in theuplink direction.

Feature description

In GSR6, GPRS multi-slot class MSs which support multiple timeslot allocations in theuplink and downlink directions, were only allocated one uplink timeslot. The Enhanced2UL feature provides allocation of up to two uplink timeslots for the MSs that supportmultiple uplink timeslot allocation.

This feature improves the performance of MSs that support multiple uplink timeslotallocation and comprises two sub-features:

S Enhanced 2UL timeslot scheduling

S Advanced uplink/downlink bias detection

Enhanced 2UL Timeslot Scheduling

This enables operation of two uplink timeslots for MS multi-slot classes that support it. Allmulti-slot classes that support multiple uplink timeslots in dynamic mode are mapped tomulti-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

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

GSR6 (Horizon II) BSS software release GSR6 (Horizon II)

02 May 2003


68P02901W01-M 5�69

Advanced Uplink/Downlink Bias Detection

For some multi-slot class MSs the maximum number of uplink and downlink timeslots inthe MSs allocation is less than the sum of the maximum number of timeslots that can beallocated in an individual TBF direction. These MSs can be allocated more timeslots inone direction at the expense of fewer timeslots in the opposite direction. This type ofmulti-slot class is called a biasable multi-slot class. The Enhanced Two Uplink Timeslotsfeature supports biasable multi-slot classes 6 and 10.

Figure 5-2 shows the multi-slot class 6 MS uplink bias configuration of two timeslots inboth downlink and uplink directions, or downlink bias of three downlink timeslots and oneuplink timeslot.

Figure 5-2 Multi-slot class 6 uplink/downlink bias timeslot allocation

ÄÄÄÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

DL

UL

UL BiasClass 6

DL BiasClass 6

TS 5 6 75 6 7

Figure 5-3 shows multi-slot class 10 MS uplink bias configuration of two uplink timeslotsand three downlink timeslots, or downlink bias of four downlink timeslots and one uplinktimeslot.

Figure 5-3 Multi-slot class 10 uplink/downlink bias timeslot allocation

ÄÄÄÄÄÄÄÄÄ

ÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

ÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄÄÄ

ÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

DL

UL

UL BiasClass 10

DL BiasClass 10

ÄÄÄÄÄÄ

ÄÄÄÄÄÄÄÄÄ

TS 5 6 74 5 6 74

The bias change mechanism is based on the data transfer characteristics in the uplinkand downlink directions. During uplink data transfer for example, the uplink direction ishighly active compared to the downlink direction, the MS therefore receives an uplinkbiased timeslots allocation.

Although MS multi-slot classes 5 and 9 support multiple uplink timeslots, these MSs donot have the restrictions of biasable classes. Consequently, uplink/downlink biasing doesnot apply to MSs of class 5 or 9.


02 May 20035�70


68P02901W01-M

Removal of support for Horizonoffice

{4471}

Feature overview

Support for the Horizonoffice BTS is removed in GSR6 (Horizon II).

02 May 2003


68P02901W01-M 6�1

Chapter 6

OMC-R software release features

GSR6 (Horizon II)

02 May 20036�2


68P02901W01-M

GSR6 (Horizon II) Introduction to OMC-R software release features

02 May 2003


68P02901W01-M 6�3

Introduction to OMC-R software release features

In this chapter

The following chapter summarizes the configuration features of the Motorola OMC-Rsoftware releases. Motorola GSM products are continually being updated. Releases ofsoftware 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 hasbeen 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 BSSsoftware release 1.4.1.1.

S OMC-R software release GSR2.



S OMC-R software release GSR4.1


S OMC-R software release GSR5.1


S OMC-R software release GSR6 (Horizon II).

GSR6 (Horizon II)OMC-R software release 1.1.2.0

02 May 20036�4


68P02901W01-M

OMC-R software release 1.1.2.0

ConfigurationIn OMC-R release 1.1.2.0, the OMC-R configuration comprised the following:

S System Processor: Tandem A21.

� X.25 link.

S Man-Machine Interface (MMI) Processor.

Release 1.1.2.0 featuresThe following features were included in OMC-R release 1.1.2.0:

S Sounding of a bell whenever a new alarm is sent to MMI.

S A timeout variable for the X.25 connection establishment phase.

S A timeout variable for the data transfer phase.

S A timeout variable for the supervision of IPC response messages from both CMand LM (Uploader).

S Two versions of tabular key statistics reports, together with an interactive graphoption.

S On parsing a BSS statistics file, the parser moves it to:

� filename.parsed.

� filename.bad_header.

� filename.FATAL_ERROR.

S Fatal errors cause the Parser to terminate.(For example, unable to connect to db.)

S The parser no longer accepts statistics following a PROCEDURE tag.

S The parser expects a DURATION field in file headers. Durations of plus or minus5 seconds are accepted for parsing. No other files are parsed.

S The valid header year range changed from 1980 to 2079.

S An MMI printer command is provided, and the ability to change the font of text inSubscription List windows.

S Subscription by device class.

S Event log post-processing utilities (cel, fes, qfes, ces).

S Automatic backup of uploaded database.

S Automatic backup of load directory on selection of new software load.

S 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 clearalarm for each NE link brought into service, that is, for each link for which aconnect request is received. Subsequent link failures or recoveries areaccompanied 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 auditfile indicating the current time and the NE device ID associated with the link.

S Log files created for update and cutover procedures.

S OMCINIT logs information to OMC-R audit file.

S Uploads tagged in OMC-R audit file with process id.

GSR6 (Horizon II) OMC-R software release 1.1.2.1

02 May 2003


68P02901W01-M 6�5


Configuration

In OMC-R release 1.1.2.1, the OMC-R configuration comprised the following:


S MMI Processor.


The following features were included in OMC-R release 1.1.2.1:

S IPC logging is ENABLED by default in this release.

S OMC-R Database Schema upgraded to remove some indexes on the PM statstables.

S The OMC-R Watchman script (omc_watchman) provides facilities for monitoringthe OMC-R processes running on the System Processor. It also provides facilitiesfor informing OMC-R operators if any of the OMC-R processes terminate.

S Event Processing utilities.

S The rate at which MMI attempts to process events and what action MMI takeswhen flooded with events can be configured via environment variables.

S $DBMS_ROOT/bin/db_pm_maint modified to:

� Increase performance.

� Accept additional parameters when invoked.

S Manually, as well as automatically, cleared alarms change from red to black.

S Six new parameters added to the BSS Add Cell command. The Change, Add andDisplay Cell commands modified. The added parameters are:

� d1_ncell_proc (0�1).

� d1_missing_rpt (0�1).

� d1_ba_alloc_proc (0�1).

� full_pwr_rfloss (0�1).

� d1_sdcch_ho (0�1).

� d1_sdcch_timer_ho (0�31).


02 May 20036�6


68P02901W01-M


Configuration


S System Processor: Tandem A22

S MMI Processor


The following features were included in OMC-R release 1.1.2.2:

S Kernel parameter changes: MAXUMEM increased to 6 X 4096.

S Installation: size of logical logs increased, number of logical logs decreased, sizeof physical logs increased.

S db_pm_maint utility: approach to maintenance is changed from thelock-restrictions approach to a configuration row-set approach.

S IPC logging is ENABLED by default.

S Manual submission of stats files for parsing.

S MMI support for multiple printers.

S Manually handled and cleared alarms are written to the event log. The alarm iswritten to the log with the current time, new status field and user name of theoperator handling or clearing the alarm. Note that the original alarm appears with astatus field NOT APPL in the event log.

S Command partitioning: a new read-only OMC-R MMI, if required.

S Notification of incoming events/alarms in iconized event/alarm windows.

S Support for EAS in MMI.

S Subscription list sorting: events extracted from AET are displayed in chronologicalorder.

S Performance Management stats filtering:

� Filter RF_LOSSES_TCH.

� Filter CHAN_REQ_MS_FAIL.

� PM_SD_FILTER.

S Support for both 30 and 60 minute stats file collection.


02 May 2003


68P02901W01-M 6�7

S Front End updates for release 1.1.2.2. The OMC release 1.1.2.2 Front Endsupports both BSS version 1.1.2.1 and version 1.1.2.2. To change which BSSversion is supported, the BSS_VER environment variable can be set appropriately.A new menu option, Version, has been added to display the current value ofBSS_VER.

S Ability to view call trace output at the OMC-R.

S Support for Remote Tune Combiner device.

S Display of OMC-R software load version number (Tandem and MMI).

S Display of additional alarm Information at OMC-R.

S Channel number displayed in HEX at the OMC-R.

S KSW displayed correctly in events and alarms (not as TDM).

S Tab operation allowed in MMI dialogue boxes.

S Naming of event log changed to evYYMMDDHHMMSS.

S Input buffer size for X.25 data in the Event Interface application has beenincreased from 165 to 1024 bytes.

S Logging of messages added to the Event Router and List Manager processes.

S Date format for PM is now user configurable (PM_DATE_FORMAT).


02 May 20036�8


68P02901W01-M


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 NEdatabase, generated on a test BSS system, on to theOMC-R. The load_db script reads a NE databasefrom tape and installs it on the OMC-R. Theactivate_db script moves a NE database, installedvia load_db, from the installation directory to thecurrent database location of a specified NE.

Critical alram thresholdexceeded

Supports for MMS alarm Critical alarm thresholdexceeded to inform the operator when the critical MMSalarm 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. Throughoutthe MMI area for delete and modify commands andpotentially dangerous commands (for example, DisableLogging) the user is prompted with a confirmationdialogue box. The user can select OK to continue orCANCEL to cancel the operation.

Date/time on event logs A date/time stamp written at the start of every eventlog file when it is first opened. It is not visible to theOMC-R operator and is intended to be used only byevent post processing utilities.

Customizing database reports Consists of two simple methods of retrieving databasedata for display, namely, interactive ISQL, and a simpleINFORMIX report generator called ACE.

Alarms and eventshighlighted when selected

Alarms and events are highlighted when selected in anAlarm Display, Event Display or Event Log. Analarm/event remains highlighted until anotheralarm/event is selected.


02 May 2003


68P02901W01-M 6�9

Additional features

The following additional features were included in OMC-R release 1.1.2.3:

S Customizing PM Reports document.

S Support for new EAS alarm: the alarm Bad Daughter Board ID read � possible badEAS board replaced the Bad ID alarm to get output when an EAS board isunseated.

S MMI maintains its local list of selectable NEs. There is no need to log out MMIsessions after deletion of a node.

S Potentially separate Subscription Lists for Events and Alarms, configurable usingMIT file.

S BSP and DHP alarms added to MIT file.

S No Object field changed to Object No in Upload Status window.

S EM router no longer exits on an error return code from the IPC subsystem.

S More description error messages added to EM List Manager.

S Time Now option removed from PM reports.

S On the MPC, getlogin replaced by cuserid.

S Updated omc_db_ckspace script.

S Immediate printing of events and alarms.


02 May 20036�10


68P02901W01-M


Configuration



S MMI Processor.


Table 6-2 summarizes the features included in OMC-R release 1.1.2.4.


Feature Description

Enhancement foromc_watchman script

The omc_watchman script sends a mail message tothe users specified by the variable MAIL_ADDRESSwhen an OMC-R process terminates. The messagespecifies which process has terminated. In additionwatchman.log logs any processes� reports onomcinit, and logs any processes that have terminatedwhile watchman.live reports which processes arecurrently alive.

Disconnecting applications foron-line DB maintenance

The OMC-R database can be brought down to singleuser mode for certain types of maintenance. Theapplications connected to the database (EM and PM)can handle database disconnection and reconnection.This is to cater for db on-line maintenance.


02 May 2003


68P02901W01-M 6�11


ConfigurationIn OMC-R release 1.2.0.0 the OMC configuration comprised the following:


S MMI Processor (MPC).

S MMI Processor (SPARC 10).

In addition, the following is optional:

S NCD XRemote software.

S MMI Processor (SPARC IPX).

Release 1.2.0.0 featuresTable 6-3 summarizes the OMC-R release 1.2.0.0 features.


Feature Description

Display of loads on i-CMmodifiy window

As part of the X upgrade to X11R4 the horizontal scrollbar for the Load Names list (in the i-CM Node Modifywindow) is not included by default. This list isautomatically resized, if possible, and the horizontalscroll bar is only present when it is not possible toresize the list.

Graph of raw stats Default worksheets enable the graph option for allstatistics as soon as they become available.

Command constructor closingon X.25 connection break

Command Constructor closes following confirmation ofX.25 connection break error message and the Wingzlicense is freed.

Add alarm strings fortranscoder to BSC link (XBL)

XBL alarms which will be supported by BSS Release1.2.0.0 are supported at the OMC-R. These includetwelve hardware alarms and three PM alarms. The PMalarms are similar to those defined for RSL and OMLdevices.

Support XBL stats A parser, database and PM-UI are provided to supportXBL statistics.

Periodic supervision ofaccessibility

The OMC-R periodically polls the NEs with openconnections to the OMC-R for their status. If an NEinforms the OMC-R that is is not operating correctly, aCRITICAL processing Failure Event is generated forthat NE, with an error Id of BSS Error State [30006]. Ifan NE fails to respond to an OMC request for itsstatus, the OMC-R generates a CRITICAL processingFailure Event for that NE, with an error Id of BSS RespTimeout [30005].

Save alarm context If the BSS-OMC-R connection goes down, the BSSbuffers events/alarms until connection isre-established. If the buffer overflows (with more than100 events/alarms), an alarm is sent from BSS to theOMC-R indicating this. The OMC-R supports this BSSalarm (Id 4), alarm string Event Buffer Overflow.


02 May 20036�12


68P02901W01-M

Feature Description

BSS stats changes Supports changes made to BSS statistics.

Support new BSS alarms Introduces new BSS alarms.

Port of MPC applications toSPARC

All current MPC applications are ported to the SPARCplatform.

Incorporation of cron jobs New scripts support listing, removing, archiving androlling over log files produced by the OMC-R. Thesescripts have been written with a view to running themfrom cron.

Immediate sld program bufferflushing

The sld program flushes its buffer immediately tostandard output following a buffer write. Previously thiswas done only when the buffer was full. The changeenables immediate printing of alarms.

Remote x terminal supportover a dial up line

Users may access the OMC-R via a remote X terminalusing XRemote. When using XRemote the EventManager Subscription should not be displayed for longperiods, especially when high event rates are involved.

�M� and �O� defined on formsworksheets

The two worksheets EquipDRI.wkz andEquipRTF.wkz are updated with a description ofM/O/P (Mandatory/Optional/Predefined).

Error message if X.25connection lost

In the absence of an X.25 connection, the commandconstructor displays an error message. Onconfirmation of the error message the commandconstructor closes and the Wingz license is freed.

New directory BS GSM-1200to support BSS

A directory BSGSM-1.2.0.0 is created as part of theinstall/upgrade procedure on the MPC. Theinstall.M and update.M files are modified to createthe BSGSM-1.2.0.0 directory and its associatedsub-directories.

Management ofwatchman.log file

When the omc_watchman.log script is executed alog file is created. The script roll_watchman.logforces a roll-over of the log file when executed. Thescript moves the existing watchman.log file to thefilename watchman.log.yymmdd. It is recommendedthat this script be executed once a day from cron.

Reason strings changes The OMC-R reason strings are made consistent withthose used at BSS MMI and BSS FM and with those inthe Trouble shooting Guide. A new reason string is alsoadded for COMBINER CONTROLLER.

IAS device ID change The Id for BSS device IAS is changed fromSITE�CAGE�IAS to SITE�CAB�IAS.

Support new BSS PATHdevice

Supports a new device, PATH, in BSS release 1.2.0.0.The new path device Id is 42. The MMI name is PATHand the format of the BSS MMI device identifier isSITE,PATH. The SITE is the connected site on theother end of the PATH. The PATH is a unique identifier(0 � 9) within the reporting site.

Work in progress messagefor Wingz

The command constructor displays a work in progressmessage while being invoked. The performancemanagement reports generator also displays a work inprogress message while being invoked.


02 May 2003


68P02901W01-M 6�13

Feature Description

MIT file updates Two new tables are defined in the MIT File for EventState Definitions and Alarm Format Definitions. Theseare required for Event Log Processing utilities.

New 4GL reports Consists of four key statistics 4GL report modules,which provide key statistic data summary reportssummed over time for each cell and BSS. Thesereports can be invoked interactively from the UNIXcommand line, or automatically by using cron. Thesereport modules give an indication of the quality ofservice the GSM network is currently providing.

OMC-R forms for BSSmodifications

Updates to the OMC-R (forms) support changes madeto the BSS software.

New directoryBSGSM-1.1.2.3

A new directory for the forms software supportsBSGSM�1.1.2.3. The install and upgrade utilities aremodified to create this directory.

Using cron to produce keystat reports for yeaterday

The key_stat_reps script is invoked from the crontable early each morning. This produces reports in adirectory under the $PM_LOG directory, which mayalso be printed on request. These reports arekey_stat reports for the network for the day previousto which the script is called. The script removes allprevious reports from $PM_LOG prior to generatingthe new ones.

OMC-R key stats on MMIprocessor (MPC)

Key statistics are provided on the MMI processor.

OMC-R key stats on MMIprocessor (SPARC)

Supports The key statistics used by the 4GL PMcommand line reports.


02 May 20036�14


68P02901W01-M


ConfigurationIn OMC-R release 1.2.2.1. the revised/additional requirements are as follows:

S System Processor.

S MIB Processor (SPARC).

In addition, the following is optional:

NCD XRemote software.

S MMI Processor (SPARC IPX).

S MMI Processor (SPARC 5).

Release 1.2.2.1 featuresTable 6-4 summarizes the OMC-R release 1.2.2.1. features.


Feature Description

Network status summary Allows the operator to select a map of all, or part of thenetwork. The selected map can be configured todisplay the Network Elements (NEs), links in thenetwork and the sites and links contained within an NE.Maps can be topological or geographical.

Alarm and statesynchronization

Provides a mechanism for synchronization of theOMC-R and BSS/RXCDR device status at OMC-Rinitialization time, and after a failure of the OMC-R orBSS/RXCDR or the links between them. Statusinformation is composed of both alarm and device stateinformation. Synchronization occurs automatically at aconfigurable interval.

Audible alarm The OMC-R provides an output to drive an audiblealarm. The output is activated whenever alarms higherthan a programmable severity are detected. The alarmseverity level will be configurable on a system-widebasis only.

OMC-R application faultmanagement

Unrecoverable failures in OMC-R applications generateinternal alarms. For OMC-R release 1.2.2.1, faultnotification only is provided.

OMC-R systemadministration

Allows installation of the OMC-R software for the1.2.2.1 release.

OMC-R installation utilitiesand directory structure

Separates release dependent information from releaseindependent information so that the operator does notloose configuration information during an upgrade.

4GL/GX performancemanagement reporting

Performance Management (PM) reporting is nowbased on Informix 4GL/GX. Operators can accessperformance data via the MMI processor using the PMreporting module of the OMC-R MMI. There is also anenhancement to PM reporting whereby it gives a valuefor all the intervals present, but flags the fact that fullcoverage of the interval measured was not possible.


02 May 2003


68P02901W01-M 6�15

Feature Description

Total calls statistic This statistic is added to the existing 16 key statistics.

Zero filter and rollup The Parser is modified such thatCHAN_REQ_MS_FAIL statistics with zero values arenot inserted in the database. This saves insertion timeand database volume requirements as well aseliminating the restrictions on the use of the 1.1.2.2CHAN_REQ_MS_FAIL filter. A cell level value is alsoinserted for this statistic, representing the sum of theindividual channel values for the collection period inquestion.

Interim logging of change ofaccess rights

Provides information on which users are currentlyinstalled in the OMC-R and what their privileges are. Alog record is added to the log file each time a user isadded or deleted.

Compression of BSSsoftware objects at theOMC-R

Allows the OMC-R to store backup NE databases in acompressed format on the OMC-R. This reduces theamount of disk storage required to store databases atthe OMC-R and simplifies operator procedures.

OMC-R audit process Monitors the following: X.25 lines connected to thetandem system processor, tandem hardware unitintegrity, disk space usage on the Tandem /usrpartition. The feature produces alarms for these areasunder certain conditions.

Alarm filtering by device typeand alarm code

Provides the following event and alarm enhancements:subscription of alarms by Error Id, subscription of allevents by Device Type (Obj Class), display of alarmadditional information fields.

Event log search and printoption

Provides the operator with the following facilities: oneor more event logs may be selected forpost-processing, searches for events can be performedaccording to event log filtering criteria, a collection ofevents which meet the specified search criteria isformed, the collection of events is sent to standardoutput, search and input of selection criteria can beinvoked from MMI menus.

Load management commentand memo field

Provides enhanced user input capabilities from theOMC-R MMI terminals.

All but subscriptions(blocking)

The Add and Modify Subscription windows have beenmodified to allow blocking of subscriptions for a specificSubscription List. There is also an Equal/Not Equaltoggle button on the Error Id field.

Support of 1 Gbyteconfiguration

From the 1.2.2.1 release onwards support is given fora 1 Gbyte Tandem system disk. Support will continuefor the existing 650 Mbyte system disk. Note that the1 Gbyte disk allows for increase in database size.

Night concentration Allows an operator be able to handover managementof one network region to another OMC-R during thenight shift. This necessitates the provision of amechanism to allow a single workstation to accessmultiple System/MIB processor pairs.


02 May 20036�16


68P02901W01-M

Feature Description

Blacklist subscription list An alarm blacklist is introduced to provide system wideblocking of specific alarms, to prevent them reachingthe MMI; they are still logged.

Change cell command split The change cell command is split up into 11sub-sections.


02 May 2003


68P02901W01-M 6�17



Table 6-5 summarizes the OMC-R release 1.2.2.2 features to support the BTS6, ExCell6and TopCell cabinets.

Table 6-5 Release1.2.2.2 features

Feature Description

BSS support activities Provides support for the statistics and alarms definedby BSS release BSGSM 1.2.2.2.

Auto initiate alarm windows Allows alarm/event subscription windows to beautomatically opened on start up of an MMI session.

Total calls statistics The key statistic total calls replaces the existing pagingload in the call summary key statistic.

Forms updates A new parameter called TRU identifier is added to theEquipDRI worksheet after the Slot number.

Databse management A new script, delete_CELL is added for deleting cellsfrom the schema. This script provides similarfunctionality as the scripts for managing the deletion ofBSS and SITE information.


02 May 20036�18


68P02901W01-M


Configuration

In OMC-R release 1.2.3.0. the revised/additional requirements are as follows:

S System processor.

S MIB processor software (either SPARCstation 10 or 20).

S MMI processor software.


Table 6-6 summarizes the OMC-R release 1.2.3.0. features.


Feature Description

NMC-OMC-R securityapplication (optional)

Supports the optional security application on theinterface to the NMC. The purpose of this feature is toprovide secure access to the OMC-R via Remote Loginover an OSI Stack.

System administration Provides the necessary procedures and scripts toinstall the 1.2.3.0 OMC-R and to install the SACapplication on the OSI and RLP processors.

BSS support activities Provides support for the statistics and alarms definedby BSS release BSGSM 1.2.3.0.

Graphical key statistics �save selection

Enables the Operator to save the Date and Timeselection and the NE selection.

MMI audit trail - BSS MMIs Stores the commands carried out on the BSS, from theOMC-R, along with a time stamp.

Rlogin modifications Enables an Operator to remote login to a NE while adatabase upload is in progress. The Operator iswarned of the database upload.

Batch based time updates Provides a script which sets the time automatically atthe BSS, controlled by an OMC-R. The time is setusing BSS MMIs.


02 May 2003


68P02901W01-M 6�19



The OMC-R software is supplied on one CDROM which includes software for the SystemProcessor (Tandem), the MMI Processor (SPARC) and the MIB Processor (SPARC). Inaddition to the OMC software, the CDROM also contains third party product software forSolaris patches, Informix, Motif and X11R5.

In addition to the OMC-R CDROM, one additional CDROM is supplied which contains theWorldview version 2.0.1 software release, and one cartridge tape is supplied containingthe Wingz software release.

Table 6-7 summarizes the new OMC-R software release features for 1.3.0.0.


Feature Description

Network ConfigurationManagement (NCM)

Augments the BSS configuration data maintained atthe OMC-R, allows the manipulation of the data fromthe OMC-R and supports the synchronization of thisdata with the BSS. It centralizes the configuration dataat the OMC-R, supports the logging of changes andcreates the infrastructure to support the creation ofBSS binary from the OMC-R.

Code Storage FacilityProcessor (CSFP)

Allows the online download of a new BSS load, fromthe OMC-R to the BSS, to support the fast swapover toa new load, thus reducing BSS downtime. This featurealso includes support for electronic transfer of BSSdatabases from the Datagen platform to the OMC-R.

On�line help from GSMdocumentation

Provides the OMC-R user with a context sensitive helpfacility, covering all aspects of work at the OMC-R,including information on the BSS.

1.3.0.x systemsadministration

Provides the mechanisms for doing a clean installationof 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.0software release. Utilities for administrating theOMC-R databases and log files are also included.

Operability enhancements Provides a forms interface to support the followingOperations and Maintenance procedures:

Report all out of service devices.Add devices.Interface to the OMC-R batch facility.


02 May 20036�20


68P02901W01-M


Release 1.4.0.0 featuresMost of the new features and enhancements to the OMC-R software for 1.4.0.0 arebrought about by the introduction of a revised hardware platform.

New OMC-R systems will use the new OMC-R System Processor, the Tandem IntegrityS1475, while existing Tandems will be upgraded to UNIX SV.4. (B series OS).



Feature Description

Upgrade of Tandem operatingsystem software to UNIXSV.4 (B series) includingVeritas 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 applicationshave been ported to run on this operating system. TheB series Operating System on the System Processor isfully compatible with the existing Solaris configurationon the SPARCstations.

Port to Spider X.25. The OMC-R X.25 application has been ported fromTITN X.25 to Spider X.25 on the System Processor tofacilitate the new operating system. The main impact ofthis feature is that the X.25 trouble shootingprocedures change.

Dual 64 kbit/s file uploadcircuits.

Provides support for an additional upload circuit. Thisgives the OMC-R two 64 kbit/s X.25 circuits for fileuploads from the BSS to the OMC-R. The impact ofthis feature is that up to eight simultaneous uploads arenow supported (four uploads was the previous limit).The extra upload circuit increases redundancy.

Upgrade of databasesoftware to INFORMIXOn-line 5.0.

The port to the B operating system also necessitates amove to Informix 5.0 software as INFORMIX 4.1 is notsupported on the B series OS.

System AdministrationBackup menus.

The backup menu program handles on-line backups,file locking and data consistency as well as providingan easy to use front end for both backups and restoresacross the network.

Compatibility with existingsoftware

Tandem S300 or 1475 OMC-R systems, runningOMC-R software release 1.4.0.0 are compatible withthe BSS software releases BSGSM 1.4.0.x andBSGSM 1.3.0.x. Tandem S300s and 1475s can beused in the same cellular network. However, it isrecommended that a BSS software load compatiblewith the appropriate OMC-R software revision of bothOMC-Rs be run so that BSSs may be quicklytransferred between OMC-R systems if the needarises.

Installation andcommissioning impact

A menu driven install program is available which offersthe user a choice between upgrade and clean installoptions. Once the OMC-R GSM 1.4.0.0/1.4.0.xsoftware release has been installed, utilities areprovided which will configure the System Processor filesystem and X.25 software to meet the networkrequirements.


02 May 2003


68P02901W01-M 6�21

Feature Description

OMC-R upgrade/rollbackpaths

Full details of the procedures required forupgrade/rollback of the OMC-R will be provided byMotorola at a later date. The 1.3.x to 1.4.0.0 upgradepath will be supported. The 1.4.0.0 to 1.3.x rollbackpath will be supported.

OMC-R administration impact The port to B Series OS changes many of the OMC-Rsystem administration procedures.

Operations and maintenanceimpact

The port to Spider X.25 changes the X.25 maintenanceand trouble shooting procedures.


02 May 20036�22


68P02901W01-M



Most of the new features and enhancements to the OMC-R software for 1.4.0.1 arebrought about by the introduction of a revised hardware platform and are virtuallyidentical to the enhancements described in release 1.4.0.0, so a brief summary isincluded 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 Integrity1475, 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:

S Upgrade of Tandem operating system software to UNIX SV.4 (B series) includingVeritas file system manager.

S Port to Spider X.25.

S Dual 64 kbit/s file upload circuits.

S Upgrade of database software to INFORMIX On-line 5.0.

S System Administration Backup menus.

S On-line documentation.


02 May 2003


68P02901W01-M 6�23

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, tochange parameters in any Cell in the GSM networkand apply any of those changes to other Cells in thenetwork.

Neighbour propagation Automatically aligns the settings of some attributes ofthe Cell and RTF objects, with dependent attributes ofthe Neighbour object (and also DRI, RTF, and Sourceobjects).

MicoCellular MicroCellular is a concept in which RF coverage isstructured in more than one layer. It is generallyapplied as an extension to an existing MacroCellnetwork in order to significantly increase its capacityand provide better coverage in areas of high trafficdensity. MicroCellular supports a mixture of optionaland standard software features. They are identified asfollows:

Independent BCCH Allocations on BCCH/SACCH.Handover Flow Between Cells Statistics.Microcellular (combined micro/macrocell) support (optional).

Enhanced event log searchand print

Enables the OMC-R operator to filter event/alarmmessages in the Event Log windows via a filter whichcorresponds in functionality to the subscriptionselection dialogues used in the Event and AlarmDisplays windows.


02 May 20036�24


68P02901W01-M


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 releasesupported the following BSS features:

S M-Cell2 GSM900 MHz band.

S M-Cell2 DCS1800 MHz band.

S M-Cell6 GSM900 MHz band.

S M-Cell6 DCS1800 MHz band.

S M-Cell GSM900 MHz band with EGSM.

S RSS functionality port to carrier to carrier equipment (TCU) M-Cell.

S Recovery escalation.

S BSC CSFP redundancy.

S Dual rate and M-Cell impact on BSU�BTS.


02 May 2003


68P02901W01-M 6�25


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 supportedthe following BSS features:

S M-Cellmicro GSM900 MHz band.

S M-Cellmicro DCS1800 MHz band.


02 May 20036�26


68P02901W01-M



The OMC-R software release supports both BSS and OMC-R features. Although thereis no OMC-R 1.4.1.1 release, the OMC-R 1.4.1.0 software release supports the followingBSS 1.4.1.1 software release features:

S NIU-T1 support for M-Cell sites.

S M-Cell2/6 MCU redundancy.

S Phase/frequency lock.

S sync boot.

Table 6-10 summarizes the OMC-R features of release 1.4.1.0.


Feature Description

BSS device management viaOMC-R GUI

Enhances the functionality already provided by theOMC-R GUI for performing network level FaultManagement and Configuration Management activitiesfrom the OMC-R GUIs Navigation Tree.

Proxy cell Enables cells from external GSM Networks (managedby 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 isparticularly useful in microcellular networks employingequipment from more than one vendor.

Alarm context sensitive help Provides on-line context sensitive information on anyselected alarm when alarm handling.

Improved PM GUI Provides a new enhanced PM GUI, selectable from theOMC-R GUI front panel. The graphing capability hasbeen improved to support multiple traces.

PM activation from MAP Provides the facility to invoke the new PM GUI withdevices already preselected from other areas of theOMC-R GUI such as the network maps or theNavigation Tree.

Alarm handling improvements provides several enhancements to the EventManagement functionality provided by the OMC-R. Theenhancements are as follows:

Alarm blacklistingOIC alarm clearingMap event history

Command partitioning - GUIonly

Partitions OMC-R users into different security areas.Depending on which security area the user has accessto they will be allowed/disallowed options on theOMC-R GUI that could be used to alter OMC-R or BSSinformation.

Handover performancestatisitcs enhancementpackage

Provides a package of enhanced handoverperformance statistics which reduce networkoptimization effort and time.


02 May 2003


68P02901W01-M 6�27

Feature Description

15,000 TCH support Provides support for 15,000 traffic channels innetworks where the OMC-R is deployed with a TandemIntegrity 1475 System Processor. Existing OMC-Rsystems deployed with Tandem Integrity S300 SystemProcessors will continue to support 10,000 trafficchannels.

Alarm paging (optional) Can be used to automatically notify on-call personnelof certain alarms or state changes which have beenreported to the OMC-R.

DBMS upgrade Details the changes required for the OMC-R DBMS inthe OMC-R 1.4.1.0 system in order to support theother 1.4.1.0 features. The main impact of the featureis to the tables and columns of the PM database on theOMC-R System Processor.

GSR6 (Horizon II)OMC-R software release GSR2

02 May 20036�28


68P02901W01-M

OMC-R software release GSR2

GSR2 features

Table 6-11 summarizes the OMC-R features supported by the GSR2 (1.5.0.0) softwarerelease.


Feature Description

Expanded Call Trace With the introduction of the call trace expansion featurethe BSS will expand the data collected to be compliantwith GSM standards. This includes the collection ofRR and Abis messages.

MSC Initiated IMSI & IMEICall Trace

Allows an MS to be tracked as it moves across thenetwork.

On-line Transcoder expansion Allows the transcoder capacity, associated withequipped transcoder cards, to be increased on-linewhile cellular service is maintained to subscriberswithin the associated Base Station System (BSS).

On-line Add/Copy/Delete Cell Supports the on-line modification to the cellconfiguration of the SITEs within a BSS while cellularservice is maintained to subscribers.

Microcellular neighbourclass 7

Provides additional microCellular functionality to caterfor special handover situations in contiguousmicroCells in networks with limited frequencyspectrum, where it may be impossible to avoiddeploying adjacent cells on adjacent BCCHfrequencies.

Satellite BSC/�/XCDRinterface (optional)

Provides the BSS software support for transmission ofthe OML link via satellite. This gives the facility for theinterconnection, via satellite, of the BSC or RXCDRwith the OMC-R.

Satellite XBL support(optional)

Provides the BSS software support transmission of theXBL link via satellite. This gives the facility for theinterconnection of RXCDR to BSCs deployed in areaswhere land based and microwave links needed forinterconnection are unavailable or cost prohibitive.

Enhanced GSM 12.04Statistics Compliance

Provides a package of additional OMC�R key statisticsreports and additional BSS statistics which greatlyimprove the compliance of the Motorola statistics toGSM 12.04 recommendations.

Downlink RXQUAL Stat(OMC-R bin)

Provides an enhancement to existing OMC-R supportfor the downlink RxQual raw statistic reported from theBSS. The OMC-R now supports the full bin countsgathered by the BSS, improving on current support ofdistribution (min/mean/max values). This featureprovides improved system optimization support.

Link Balance VerificationStatistics

Provides a facility at the OMC-R to identify thosecarriers which have unbalanced uplink and downlinksignal strengths. This feature supports optimisationactivities.

GSR6 (Horizon II) OMC-R software release GSR2

02 May 2003


68P02901W01-M 6�29

Feature Description

CM Service StatisticsBreakout

Provides call success statistics that more closelymatch MSC statistics. Existing Motorola raw statisticshave been modified to improve the accuracy of callsuccess statistics.

Network Health Reports Enhances the OMC-R performance reportingcapabilities by providing additional PM reports thatmeasure network performance from the subscriberperspective.

Map filtered Event LogSearch & Print

Enables the OMC-R operator to select a node on themap and apply a user defined filter to eventsassociated with the node prior to display. Multiple logfiles can be then be processed by the invoked EventLog Search & Print window.

Generic RF data export Provides a facility at the OMC-R to easily extract RFdata. The objective of this feature is to reduce the timetaken to implement major network updates.

GPROC2 support Allows the use of either GPROC2 or GPROC1 inBSCs, BTSs and RXCDRs.

Q3 NMC interfaceConfiguration Management(optional)

Provides the support for NMC read/write access of theRF parameters stored in the OMC-R MIB via the Q3interface.

Automatic instance namingfor Q3 (optional)

Provides the OMC-R support for Automatic InstanceNaming in the CM MIB which has been part of theOMC-R Q3 Interface features since OMC�R release1.4.0.x.

Q3 NMC interface Call Tracetransfer

Provides the OMC-R support for the dynamic transferof Call Trace data, which is formatted according toGSM 12.08 recommendations, from the OMC-R to theNMC via the Q3 Interface.

SUN Scaleable OMC-R 0 �20 k TCH

Allows the network operator to install an OMC-Rplatform that can be cost effectively expanded as thecellular network grows.

Common Desktop Manager Provides an OMC-R desktop environment, which canbe customized on a per user basis, and which reduceswindow clutter and provides a graphical front end to theUNIX file system.

System Admin GUI Provides a GUI for routine OMC-R systemadministration tasks. It gives access from the frontpanel of the OMC-R desktop to the different SUNadministration tools which support Solaris 2.5.1.

Enhanced Informix DatabaseMaintenance

Reduces the amount of time and expertise required tomaintain the OMC-R Informix database. INFORMIXVersion 7 supports multiprocessor systems andincludes GUI tools for database performancemonitoring and administration.

Enhanced OMC-R SoftwareInstallation & Upgrade

This feature (known as Jumpstart) reduces the amountof time and expertise required to install or upgrade anOMC-R. Jumpstart allows multiple Sun workstations(such as Operator workstations) to be replicated fromanother similarly configured processor.


02 May 20036�30


68P02901W01-M

The following list summarizes the hardware features provided in the BSGSM-1.5.0.0release with OMC�R/BSS software support:

S GPROC2, enhanced processor board.

S M-Cell Remote Tune Combiner (1800 only).

S Retrofit M-Cell RTC (GSM900) for BTS4/BTS6.

S Remote VSWR monitor.


02 May 2003


68P02901W01-M 6�31


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 aclient machine connected to the OMC-R LAN. Thebrowser is supported on both Sun Solaris andWindows NT (Intel-based) platforms to access OMC-RPM data.

BSS Device Management viaOMC-R GUI

Enhances the BSS device and function managementcapabilities from the OMC-R GUI.

Metrica Statistics Introduces new statistics to support the BSS. Metricais a tool that gathers statistics from various types ofOMC-Rs and compares and consolidates thosestatistics.


02 May 20036�32


68P02901W01-M


GSR4 features

Table 6-13 summarizes the OMC-R features supported by software release GSR4.


Feature Description

Network geographical accesscontrol

NA

Transfer Motorola text detabformat to PlaNET

Converts Motorola text detab format files into a formatacceptable to PlaNET, which is necessary to transferdata to PlaNET.

Task-based RoutineOperations and Maintenance

Provides a new OMC-R user interface that integratesthe tools necessary for routine maintenance of theMotorola radio infrastructure equipment.

Operator specific regions NA

Network optimization: celloptimized GUI

NA

Scaleable OMC-R The System Processor and the MIB Processor havebeen consolidated into a single SUN E3500/E3000server. This provides further reductions in cost ofownership and improved system administration,performance, and reliability.

Process restartability Allows a subset of system processor processes(Restartable processes) to restart automatically, if theprocesses fail, without the need for a full OMC-Rstop/start. Other system processes (Non-restartablevital processes) will cause an automatic OMC-Rstop/start on failure.

New Millennium Addresses all aspects of the Motorola system; OMC-R,BSS, and the BTS and BSC hardware. It concernsitself with internal clock operation and the use of thedate in various parts of the product, for example withinEvent and Alarm reports.

GSR6 (Horizon II) OMC-R software release GSR4.1

02 May 2003


68P02901W01-M 6�33

OMC-R software release GSR4.1

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 existingOMC-R architecture. It consists of support for the PCUas part of the BSS.

OMC-R capacity increased to30k TCH and 120 NE

Increases the OMC-R capacity from the previous ratingof 20 kTCH and 64 network elements, to 30 kTCH and120 network elements without requiring hardwareupgrades to the E3000/E3500. Also increases thenetwork traffic and NE count of the OMC-R byextending the object model and increasing capacity ofthe OMC-R databases and data storage areas. Thismeans that the increased size network can bemanaged without altering the data storagearrangements.


02 May 20036�34


68P02901W01-M


GSR5 featuresTable 6-15 summarizes the OMC-R features supported by software release GSR5.


Description

BTS concentration

Optimized power control

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


02 May 2003


68P02901W01-M 6�35

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 allocatingterrestrial backhaul for radio resources between the BSC and the BTS. Previous to theintroduction of this feature, these resources were allocated when RTFs were equipped.This feature preserves the existing mechanism, but allows the operator the choice, on aper BTS site basis, of whether to use the existing mechanism, or the new dynamicallocation. This feature is optional.

Optimized power control This feature, previously called Dynamic Downlink Power Control Steps, providesoptimized uplink and downlink power control. This is achieved by:

S Adding flexibility in defining power steps.

S Modifying the range of power steps (by allowing power step sizes to be changeddynamically).

S Performing downlink oscillation prevention.

These power control modifications cause the mobile and BSS to respond more effectivelyto changing power level and quality conditions. This minimizes power output both for theMS and the BSS, as well as reducing interference.

Propagation after audit This feature will provide data consistency between different BSSs with the main focus ison synchronizing neighbour information across BSSs.

If the CELL attributes change as a result of an audit, a Neighbour Propagation is initiatedto 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 thecapability to set a default relay state for the PIX relays at either an InCell site, an M-Cellsite 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 existingcongestion relief procedures can benefit from the following advantages:

S Faster congestion relief (non-ideal targets will not be tried).

S Reduced signalling (fewer handover attempts).

S Less congestion and fewer congestion relief triggers (handovers that can lead tocongestion are not accepted).

S Efficient congestion control in the preferred band of a multiband network.

S Supported by OMC-R GUI.


02 May 20036�36


68P02901W01-M

Adaptive handover This feature will allow support of adaptive handovers and optimize type 3 and type 5power 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 inthe EGSM band. This impacts the operation of non-EGSM mobiles in that they may nothave service, since they are not able to access the BCCH frequency and SDCCHchannels in the EGSM band.

The support of the BCCH frequency and SDCCH channels in the EGSM band is basedon an operator defined database parameter.

The operator also has the capability to configure a standalone EGSM band cell byselecting EGSM band frequencies.

With this feature, the operator is allowed to implement a multi-band/dual-band networkwith EGSM as one of the supported frequency bands. It is possible for the operator toselect 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 thebands but not between the bands.

Coincident multiband boundaries This feature allows operators to install new radios in a different frequency band andeasily configure multiple frequencies. The installation of new radios allow an operator tohave Multiband capabilities. The major hurdle to this type of upgrade is that the operatorhas 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 majorstumbling block to many operators who want the capacity increase but are reluctant toconfigure and optimize two frequency bands.

To circumvent this multiple frequency band issue, the new secondary frequency bandcompliments the existing infrastructure. To do this, the software allows a cell with a newfrequency band to be configured with the same cell boundaries established by theoriginal frequency band. Also, it allows the new frequency band cells to use thehandover measurement reports based on the cells in the original frequency band.

This can be done by using mobile reported measurement reports from the primaryfrequency band while a call is established on the secondary frequency band. Thisenables the mobile to be handled as if it were on the primary frequency band, whilst nottaking any primary frequency band resources.

This feature is designed to compliment the Multiband Inter-Cell Handover feature and itsuse 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 statechanges 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 theResults of Alarm Recovery Action feature, enhances this hands free operation for theend user by including information describing the result of an alarm recovery action.


02 May 2003


68P02901W01-M 6�37

Flexible neighbour cell processing

This feature will modify the criteria for handover between neighbours. It has four mainelements that can be activated independent of each other.

Dynamic trace call flow control

The Dynamic Call Trace Flow Control feature significantly enhances the existing CallTrace capabilities available in the BSS and is now supported by the OMC-R. The mainuses 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 madeby a designated MS as it travels through the network. Call Trace can be used to locatestolen or defective GSM equipment. Network Operators can also use this feature todetermine why calls are being dropped due to RF Loss.

Depending on the amount of traffic between the BSS and OMC-R, the call trace flowcontrol techniques include:

S Modifications of active call trace criteria.

S Pre-emption of existing traces.

S Controlling the number of new trace activations.

The operator may also choose whether or not MSC initiated call traces are exempt to thecall trace flow control mechanism.

NOTE This feature consists of the operator enabled triggering of flowcontrol and the associated OMC-R GUI configuration support.

The intent of this feature is to address the outstanding issues surrounding the currentCall Trace functionality in the BSS, covering call trace usability.

Proxy cell autocreation

When the NeighbourGsmCellId is entered and the Neighbour has been initialized, if theNeighbourGsmCellId 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 parametersof the neighbour just created.

During a BSS-OMC-R audit, the NeighbourGsmCellIds are checked against thecomplete list of Cells and Proxy Cells existing in the MIB. If the NeighbourGsmCellIddoes not exist a Proxy Cell will be autocreated using the NeighbourGsmCellId.


02 May 20036�38


68P02901W01-M

Proxy cell import/export

The Proxy Cell Synchronisation feature ensures that Neighbour OMC-Rs are consistentacross all OMC-Rs managing a network by ensuring that the Proxy Cells in an OMC-Rare consistent with the original CELL that exists in another OMC.

The OMC�Rsupplies the user with a program pcellExport that exports Neighbourrelated parameters of all CELLs within the OMC�Rthat have Neighbour relationships withCELLs in other OMCs, into an ASCII file.

This ASCII file is then transferred by the user to all other OMCs and the pcellImport runon it.

The import program:

S Creates Proxy Cells if there are CELLs that contain Neighbours corresponding toentries in the file and no Proxy Cell exists. The parameters of the Proxy Cell arederived from the file.

S Updates the Proxy Cells if parameters have changed.

Create/Update of Proxy Cells, results in all related Neighbours getting updated. ThusCELL-Neighbour relationships across all OMCs are synchronized via the Proxy CellExport/Import mechanism.

The OMC�Ralso provides a single script pcellSync that synchronizes all OMCs in oneshot 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. Furtherinformation will be included in the next revision of this manual.

Completion of OMC�Rsupport 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 enablecontinued operation of Q3 in the field.

Motorola�s Q3 OMC-R Mediation device support for GSR5 includes the following:

S Interoperability testing of Q3 OMC-R interface functionality with GSR5 and BSS.

S Support GPRS (PCU) specific alarms and events (GSR5).

S Recognizing Motorola�s leadership in Q3, further functional enhancements for ourQ3 OMC-R implementation is driven and agreed by the key Q3 customers and anynew generic requirement to enhance our implementation.

DRI and combiner operability improvement

This enhancement improves the operability of the Digital Radio Interface (DRI) andCombiner 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 equipof the DRI.


02 May 2003


68P02901W01-M 6�39

NHA support maximum size GSM OMC-R

This feature will enable Expert Adviser (EA) Network Health Analyst (NHA) to support themaximum 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. TheOMC-R Event Manager (EM) is able to accept the messages and deal with them asstandard alarms and passes them to the GUI for viewing and handling in the standardmanner.

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

NOTE A site visit is required for accurate calibration of radios.

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.

S 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 neighbourparameters within the network.

The parameters that are exported or imported may be defined by the user. The cell filecontains a list of cells, their bsics, frequencies and other information. The neighbour filecontains a list of neighbours for each cell. The file format is published and is in ASCIIformat. RF planning tools, for example, NetPlan can import these files and use it to carryout a network frequency replan.

The output of the frequency replan can be imported into the OMC-R, and then used toupdate the relevant network elements, new base station id codes (bsics) and frequencieswill be propagated to neighbour relations.

RF Planning data import and export may be carried out from the Navigation form of theOMC-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 onthis upgrade can be fixed. Some of these PRs are customer commitments. Applix 4.41depends on having an Informix 7.2 engine.


02 May 20036�40


68P02901W01-M

System upgrade NOTE This feature maintains compatibility with BSS GSR4 and GSR4.1

releases. GSR4.1 was a limited release for GPRS customersonly; GSR5 contains all GSR4.1 features. It is not possible todirectly upgrade the OMC�Rfrom GSR3 release to GSR5release 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.

S BSS GSR5 release can be directly upgraded from GSR4 and GSR4.1 release.

S OMC GSR5 release is capable of managing a network of BSSs running GSR4,GSR4.1 and GSR5 releases simultaneously.

S OMC GSR5 release can be directly downgraded to GSR4 and GSR4.1 forroll-back.

S BSS GSR5 release can be directly downgraded to GSR4 and GSR4.1 forroll-back.

Enhanced SDCCH to TCH assignment An enhancement has been made to increase the success rate of assignment to apreferred band cell, that is, going from an SDCCH in a non-preferred band cell directly toa 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 theAXCDR and ABSS devices.

The Dynamic Allocation RXCDR to BSC Circuits (DARBC) feature expands upon thesenew devices. During initial configuration of these devices, it is possible that the operatorwill make a configuration mistake which, if not caught early, may cause the operator toenter upwards of a 100 commands in order to correct it. This feature enables an easymechanism to correct an early configuration mistake. Without this feature, the totalnumber of commands could be (21 + 10 + 10) x 2 = 82, to make a simple, deviceidentification number, change.

With this feature, an easy mechanism is provided to correct a mistake. The OMC-R isable to propagate the BSS or RXCDR identifier (network_entity_id) changes to itsassociated BSS or RXCDR devices and its contained devices (XBLs, CICs andConn_Links) by initiating a single operation from the GUI instead of <82> or more BSSMMI commands. The GUI provides a simple screen to rectify these configurationmistakes.

For example, the operator can select the AXCDR device whose network identifier needsto be changed and initiate the Change Assoc NE ID operation. The operator should notethat a single invocation of the Change Assoc NE ID operation changes the identifier foronly one AXCDR (or ABSS) in a BSS (or RXCDR) database. If the operator changes theidentifier of an NE, the identifier must be changed in the NEs database. The ChangeAssoc NE ID operation can be invoked to change the associated device id in eachdatabase which includes the NE as an associated device.

Consider a BSS-1 and BSS-2 which are connected to RXCDR-3. The AXCDR-3 isequipped in the databases of both BSS-1 and BSS-2. To change the NE id of theRXCDR from 3 to 5, the operator must change the id of the RXCDR in the RXCDRdatabase and can then invoke the Change Assoc NE ID operation on the AXCDR-3 atBSS-1 and BSS-2 to set the new AXCDR identifier to 5.


02 May 2003


68P02901W01-M 6�41

OMC-R GUI usability

OMC-R GUI usability has been enhanced; the new procedures can be contained withinthe following five categories:

S Handling AttributeValueChange Notifications from the BSS.

S Better Status Bar Management on GUI windows.

S AutoCreation/deletion of CommsLinks during Conn_Link creation/deletion.

S Support for Default BSS Naming on Detailed Views.

S Enhancements to the Contained Devices Form.

Datagen support

The purpose of this feature is to support all parameter changes introduced in thisrelease.

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 bestored 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 thepacket-mode transmission of data within a GSM network. Using GPRS, a MS can sendand receive data in an end-to-end packet transfer. This enables a more cost-effectiveand 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 oroff-line environment providing a batch capability to allow for the grouping of multipleexpansion 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 BSSconfiguration.

S Reparent a BTS within the same Intra- BSS or a different Inter-BSS.

S Delete a BTS with its associated hardware devices and software functions in asingle 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 mandatoryFault Management procedures. If deleting or reparenting a Site, then the SIte isgracefully shutdown, for example, DRIs are shutdown and RSLs are locked.


02 May 20036�42


68P02901W01-M

Performance management functions

For both platforms the Network Expansion application maintains PerformanceManagement data on devices. Specifically during a copy SITE operation, the applicationwill copy the Performance Management configuration (enables statistics and thresholdsetc.), from the original SITE to the new SITE. Similarly during a reparent SITE operationthe application will maintain the Performance Management configuration.

Maintenance of Performance Management is limited to those statistics configured withinthe containment of a BTS SITE. Statistics configured within a BTS SITE (CELL orCarrier level) for example, RF LOSSES TCH or CALL VOLUME DRI, will be manipulatedduring Network Expansion. Statistics outside the BTS SITE at the BSS level forexample, CPU_USAGE MAX will not be manipulated. These SITEs will inherit theconfigurations 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 receivetransmit 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 areincluded, 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 fromthe previous database limit of 1920 to a new limit of 2400. This is required to supportlarge capacity BSCs supporting up to 384 carriers using an aggressive Dense Urban callmodel (as used in China). It was determined that a minimum of 2300 trunks arerequired for the Dense Urban call model to support 384 carriers and the remaining trunkswould 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 supportingheavy call traffic, provided that other limitations specified in the Planning Guide have notalready been reached.

The main impacts to the subsystems in the Base Station System (BSS) for increasingthe BSC trunk limitation from 1920 to 2400 trunks are in ensuring data consistencythroughout the system. For example, increasing the number of CICs will requireincreasing 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 orOML which passes through the RXCDR without the RXCDRhaving any impact on that link, it is simply being used as amedium to get the control link to the destination. This medium iscalled a nail.

In order to achieve 384 carriers for the BSC on the Dense Urban Call model (the primarymotivation for this feature), the following assumptions regarding the BSC are made:

S Support of two Message Transfer Links (MTLs) per Link Control Function (LCF) at40% MTL link utilization.

S Support of: 25 LCFs.

S GPROC2 processing is approximately four times that of a GPROC.


02 May 2003


68P02901W01-M 6�43

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

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 TCHsystem. The 30 k TCH can be expanded to 45 k TCH system. In ascending order thereare four available TCH sizes:

S 5 k TCH (low end).

S 10 k TCH (mid end).

S 30 k TCH (mid end).

S 45 k TCH (high end).

Vanguard software upgrade support

Motorola�s Information Systems Group, Network Systems Division (NSD), in itscommitment to provide the highest value wide area multimedia access solutions, willprovide upgrade support for all routers. Software in the field will be upgraded to thelatest Vanguard router software.

Support for Vanguard 6455 router

Motorola�s Information Systems Group , Network Systems Division (NSD), in itscommitment to provide the highest value wide area multimedia access solutionsintroduces the Vanguard 6455 router (software and hardware) . The Vanguard 6400Series from Motorola provides multiservice edge networking solutions for multimedia, IPand 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 statusis also reflected through the LED indicators (when activated) on the PCU alarm panelboard.

GSR6 (Horizon II)OMC-R software release GSR5.1

02 May 20036�44


68P02901W01-M

OMC-R software release GSR5.1

GSR5.1 featuresTable 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 hasaccess to the network that a PCU resides on. Through the intranet, and the availabilityof the PCU cage and its ethernet capability, the BSS can be monitored and maintained.

NOTE The functionality that is offered consists only of the functionalitythat the Operations and Maintenance (O&M) Man MachineInterface (MMI) and the Executive Monitor (EMON) provide for asingle BSS, as opposed to the functionality that the OMC mightprovide as a whole.

CS3, CS4 and 32 kbits/s TRAU The OMC-R to BSS interface will be updated to include the new database parametersallow_32k_trau as well as the new and modified statistics.

The allow_32k_trau parameter is restricted by the GPRS restrictable feature and the 32kTRAU CS3/CS4 restrictable feature and can only be used if the GPRS and 32k TRAUCS3/CS4 features are unrestricted. Additionally, the dynamic allocation of terrestrialresources feature must be disabled for any sites using GPRS. This parameter willprevent GPRS usage on RTFs that are sub�equipped in the database. This parametercan only be enabled if max_gprs_pdch is set to a non�zero value. Additionally, ifallow_32k_trau parameter is enabled, the value of max_gprs_pdch can not be set to zerowithout first disabling allow_32k_trau. Verifications need to be performed to ensure thatthere are enough terrestrial resources available when max_gprs_pdch is increased andallow_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:

S PCU sites from Navig

S PCU sites from SITE

S PCU sites from Contaform.

S PCU sites from Map

GSR6 (Horizon II) OMC-R software release GSR5.1

02 May 2003


68P02901W01-M 6�45

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 tounequip the site. This action can be done provided that the cabinet is locked and thereare no DRIs or EASs equipped to the cabinet. All other cabinet types are not supportedby this feature.


02 May 20036�46


68P02901W01-M


GSR6 features

Table 6-17 summarizes the OMC-R features supported by software release GSR6.


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


02 May 2003


68P02901W01-M 6�47

Geographic command partitioning and region support

Feature overview

The feature enables operators to set up geographical regions, populate these regionswith 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 isincreased. The feature provides a method of reducing the amount of data visible to theoperator by allowing them to subscribe to a defined set of network elements. Thisprovides each Operations and Maintenance Centre-Radio (OMC-R) operator with asub-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 theregions are set up, the system administrator will have the ability to create, modify andremove access controls to particular regions for each operator.

All operator specific security related information will be stored in that operator�s securityfile. (This allows the OMC-R administrator to limit the access of each OMC-R operator tocertain 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.

S Delete an operations access control group.

S Modify an operations access control group�s properties.

S Copy a operations access control group�s properties.

S Add operations to an operations access control group.

S Delete operations from an operations access control group.

S Assign an operation to one or more operations access control groups.

S 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 whichspecific operators have control. The restricted user access provides a level of security toensure that only authorised users can access certain geographical areas. The ability tomanage multiple networks on one OMC-R reduces the cost of ownership of thenetworks.

Applications

This feature will find application in those networks where control of the network isexercised in geographic regions.

Compatibility/dependencies/network elements affected

Geographic command partitioning and region support is supported by the GSR6 versionof the OMC-R. No changes are required to the network elements.


02 May 20036�48


68P02901W01-M

Enhanced circuit error rate monitor

Feature overview

The original Circuit Error Rate Monitor (CERM) optional feature provides a means foridentifying when discontinuity is detected on a circuit. The customer can:

S Reduce cost of ownership.

S Reduce downtime of devices.

S Enhance system operability.

S Enhance quality of service.

A circuit is considered to be the path along which a connection is made, from the entrypoint in the BSS (for example, a radio at the BTS) to the exit point in the BSS (forexample, the MMS timeslot that connects to the MSC or PCU).

The CERM is used to monitor the continuity and sanity of hardware processing elementsin a circuit, on a per call basis. Whenever a discontinuity is detected for a circuit during acall, error counts are updated for the points monitored for the call. When the error countat a particular monitoring point reaches or exceeds an operator specified threshold, analarm is generated. The alarm contains information identifying the monitored path inwhich the error is detected, thus allowing the operator to identify potentially faultydevices.

Feature description

The CERM feature is enhanced enabling the monitoring at various points in a GSMnetwork circuit, thus improving the ability of an operator to narrow down where a faultydevice may be located. Although having these monitoring points in the circuit pathnarrows down the list of potentially faulty devices, it does not conform that a device isfaulty. 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.

S ATER Channel Identifier (ACI) groups on a link between the RXCDR and the BSC.

S GPRS Circuit Identifier (GCI) group on a link between the BSC and the PCU.

S Radio Channel Identifier (RCI) in the radio hardware.

S 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, forexample, with a path leading from a BSC to two daisy chained BTSs, the PIC for thesecond BTS encompasses the path through the first BTS to the BSC.


02 May 2003


68P02901W01-M 6�49

OMC-R GUI usability for large network support

Feature overview

This feature aims to provide an enhanced Graphical User Interface (GUI) and tools toenable the operator to help operate and maintain large networks with relative ease. Themain enhancements are described below:

S Neighbour Reciprocity: Previously, a significant number of CELLs in a networkexhibit 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 theOMC-R, add or drop reciprocal neighbours enable operators manage largenetworks with greater ease.

The source neighbour view is also now enhanced to provide the user withinformation about Neighbour reciprocity.

S Auto Reciprocation of Neighbours: Since most CELLs in a real network exhibitNeighbour reciprocity, the user now has the option of auto creating the reciprocalNeighbour when a neighbour is created.

S Enhanced Find: The find form option is enhanced to support search forparameters. The user is now able to locate the container of the given parametername.

Feature description

The OMC-R now supports the following enhancements to the GUI and ConfigurationManagement 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 tolet the operator view all sources (CELLs in which mobile phones are located) andneighbours 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 enablesthe user to add or remove neighbours and sources and thereby manage reciprocalrelations.

The OMC-R also enables fully automated creation of reciprocal neighbours by means ofan environment variable, since most of the neighbours in a practical network are two wayneighbours.

The ProxyCell synchronization processes are extended to synchronize sources alongwith neighbours between OMC-Rs so that the correct cross OMC-R reciprocal relationsare 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 toduring the equippage of the neighbours. The user is also be able to specify, on a perneighbour 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. Thefind form option also supports the task of find attributes (parameters) in addition to thefind devices option.


02 May 20036�50


68P02901W01-M

Enable cyclic neighbour statistics

Feature overview

The BSS and OMC-R were restricted in their ability to provide full neighbour statisticcoverage to the network operators. These limitations were based on hardware andprocessing limitations.

This feature introduces the ability to automatically traverse the OMC-R network on a perBSS basis and enable the neighbour statistics in rotation.

The feature also provides the operator with the ability to enable statistics based onanalysis carried out by the Network Health Analyst (NHA) and enables the operator toprovide 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 thenetwork expansion - phase 2 feature delivered in GSR5.

Feature description

The Online Network Expansion - Phase 3 feature provides the followingenhancements:

Daisy chain support

The Network Expansion Copy-SITE, Delete-SITE and Reparent-SITE operationsare 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 asthe Path Configure.

It is also be possible to invoke the Path Configure from the Navigation TreeConfiguration Management menu , for any given site that is not within aDYnamic NETwork (DYNET) device.

The Path Configure enables the operator to temporarily un-equip devices, todelete paths, to create new paths and to re-equip the devices with their originalsettings. Network Expansion invokes the Path Configure when it determines thatthe operation selected by the user involves a site within a daisy chain.


02 May 2003


68P02901W01-M 6�51

Scheduler functionality for CellChange

The network expansion scheduler is expanded to include the possibility ofscheduling a CellXChange operation and both a Cell-X-Import operation andCell-X-Export operation.

Benefits

The main benefit of this phase of network expansion is to improve the featureapplicability by introducing daisy chain support. It also extends the schedulerfunctionality by adding support for CellXChange.

Cell Xchange

Feature overview

This feature is an extension of the RF Planning Interface feature (RDB 3416) and of theCell Parameter Import Export Feature (RDB 3780). It now allows the user to export andimport SITE/RTF/DRI parameters for direct amendment, as previously for CELLparameters. The specific parameters to export/import are configurable by the user. Thename of the configuration file is :

� /usr/omc/config/global/RF.CNFG

This feature is available both on the OffLine Management Information Base (MIB) andalso on the Operations and Maintenance Centre-Radio (OMC-R) providing a mechanismto make large scale changes on-line.

GSR6 (Horizon II)OMC-R software release GSR6 (Horizon II)

02 May 20036�52


68P02901W01-M

OMC-R software release 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

GSR6 (Horizon II) OMC-R software release GSR6 (Horizon II)

02 May 2003


68P02901W01-M 6�53

Support for new UNIX server

{4475}

Feature overview

From GSR6 (Horizon II) Volume Deployment onwards, the existing OMC-R platform willbe replaced by a new OMC platform.

Two new server types are introduced:

S Netra 20

S SunFire 4800

The Netra 20 is intended for smaller configurations of up to 45000 TCH, whilst theSunFire 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 20server 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

SCSI controller + ethernet

SCSI controller + ethernet

HSI

HSI

2 x 900 MHz CPU2 Gb RAM

DVD & DAT

External disk array

NETRA SERVER

GSR6 (Horizon II)OMC-R software release GSR6 (Horizon II)

02 May 20036�54


68P02901W01-M

SunFire 4800 OMC-R platform

This platform comprises a SunFire 4800 server configured as a single domain. There arefour 900 MHz processors on two CPU boards, providing a total memory of 4 Gb. Thesystem also comprises dual differential SCSI interfaces, dual HSI cards and quad fastEthernet 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

SCSI controller

4 x 900 MHz CPU4 Gb RAM

DVD & DAT

External disk array

SunFire 4800 SERVER

SCSI controller

HSI HSI

QFE ethernet QFE ethernet

PCI cage PCI cage

OMC-R GUI server

The OMC-R GUI platform comprises a Sunblade 150 server with 650 MHz CPU, 1 GBRAM and two internal disks.

02 May 2003


68P02901W01-M 7�1

Chapter 7

Glossary of technical terms

GSR6 (Horizon II)

02 May 20037�2


68P02901W01-M

GSR6 (Horizon II) Glossary of technical terms

02 May 2003


68P02901W01-M 7�3

Glossary of technical terms

This Glossary of technical terms contains standard Motorola acronyms, abbreviationsand numbers used throughout the documentation set.

A Interface - AUTO

A Interface Interface between MSC and BSS. The interface is based onthe use of one or more E1/T1 digital links. The channels onthese links can be used for traffic or signalling.

A3 Authentication algorithm that produces SRES, using RANDand Ki.

A38 A single algorithm performing the function of A3 and A8.

A5 Stream cipher algorithm, residing on an MS, that producesciphertext out of plaintext, using Kc.

A8 Ciphering key generating algorithm that produces Kc usingRAND and Ki.

AB See Access Burst.

Abis interface Interface between a remote BSC and BTS. Motorola offers aGSM standard and a unique Motorola Abis interface. TheMotorola interface reduces the amount of message traffic andthus the number of 2 Mbit/s lines required between BSC andBTS.

ABR Answer Bid Ratio. The ABR is the ratio of successful calls tototal number of calls. As a measure of effective calls, itreflects the performance of the total network

ac-dc PSM AC-DC Power Supply module.

ac Alternating Current. In electricity, AC occurs when chargecarriers in a conductor or semiconductor periodically reversetheir direction of movement. Household utility current in mostcountries is AC with a frequency of either 50 or 60 hertz(complete cycles per second). The RF current in antennasand transmission lines is another example of AC. An ACwaveform can be sinusoidal, square, or sawtooth-shaped.Some AC waveforms are irregular or complicated. Square orsawtooth waves are produced by certain types of electronicoscillators, and by a low-end UPS when it is operating fromits battery.

AC Access Class (C0 to C15).

AC Application Context.

ACC Automatic Congestion Control. A method by which congestedswitches automatically communicate their congestion level toother switches.

Access Burst The Access Burst is used by the MS to access the BTS. Itcarries RACH uplink from the MS to the BTS to start a call.

ACCH Associated Control CHannel. Control information associatedwith TCH or DCCH.

ACK, Ack ACKnowledgement.

GSR6 (Horizon II)Glossary of technical terms

02 May 20037�4


68P02901W01-M

ACM Accumulated Call meter. The ACM is a function containedwithin the SIM. It accumulates the total units (in the homecurrency) for both the current call and all preceding calls. Forsecurity reasons, the SIM only allows the value of the ACM tobe incremented, not decremented. Resetting of the ACM isonly possible after entering PIN2.

ACM Address Complete Message.

ACPIM AC Power Interface Module. Used in M-Cell6 indoor ac BTSequipment.

AC PSM AC Power Supply Module. Used in M-Cell6 BTS equipment.

ACSE Association Control Service Element. The ACSE is one of thethree Application Service Elements (ASE) which reside in theapplication layer of the OSI protocol and act as an interface tothe lower layer protocols. It is used by applications to create atitle 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 signalthat is a function of a continuous variable into arepresentative number sequence carrying equivalentinformation.

ADCCP Advanced Data Communications Control Protocol. Abit-oriented data-link-layer (DL) protocol used to providepoint-to-point and point-to-multipoint transmission of dataframes that contain error-control information. Note: ADCCPclosely resembles high-level data link control (HDLC).

ADM ADMinistration processor.

ADMIN ADMINistration.

ADN Abbreviated Dialling Number. Abbreviated dialling is atelephone service feature that (a) permits the user to dialfewer digits to access a network than are required under thenominal numbering plan, and (b) is limited to asubscriber-selected set of frequently dialled numbers.

ADPCM Adaptive Differential Pulse Code Modulation. Differentialpulse-code modulation (DPCM) in which the predictionalgorithm is adjusted in accordance with specificcharacteristics of the input signal.

AE Application Entity. The system-independent applicationactivities that are made available as application services tothe application agent.

AEC Acoustic Echo Control. In a system, the reduction of thepower level of an echo or the elimination of an echo.

AEF Additional Elementary Functions.

AET Active Events Table. Alarms and events are sent to theEvents Log in the GUI. Different operators will have differentsubscription lists. All alarms and events are sent to the AETbefore they are re-routed to different subscription lists.


02 May 2003


68P02901W01-M 7�5

AFC Automatic Frequency Control. A device or circuit thatmaintains the frequency of an oscillator within the specifiedlimits with respect to a reference frequency.

AFN Absolute Frame Number.

AGC Automatic Gain Control. A process or means by which gain isautomatically adjusted in a specified manner as a function ofa specified parameter, such as received signal level.

AGCH Access Grant CHannel. A GSM common control channelused to assign MS to a SDCCH or a TCH.

Ai Action indicator.

AI Artificial Intelligence. A branch of computer science whosegoal is to develop electronic devices that can operate withsome of the characteristics of human intelligence. Amongthese properties are logical deduction and inference,creativity, the ability to make decisions based on pastexperience or insufficient or conflicting information, and theability 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 acarrier wave is varied in accordance with some characteristicof the modulating signal.

AMA Automatic Message Accounting (processor). A servicefeature that automatically records data regarding user-dialledcalls.

AM/MP Cell broadcast mobile terminated message. A messagebroadcast to all MSs in a cell.

ANSI American National Standards Institute. ANSI is the primaryorganisation for fostering the development of technologystandards in the United States. ANSI works with industrygroups and is the U.S. member of ISO and the IEC. Longestablished computer standards from ANSI include ASCII andSCSI.

Antenna A transmitter/receiver which converts electrical currents intoRF and vice versa. In GSM systems, transmits and receivesRF 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 sevenhierarchical layers. It interfaces directly to, and performscommon application services for, the application processes. Italso issues requests to the Presentation Layer. The commonapplication services provide semantic conversion betweenassociated application processes.


02 May 20037�6


68P02901W01-M

ARFCN Absolute Radio Frequency Channel Number. The GSMavailable frequency is divided in two bands. Each band isdivided into 200kHz slots called ARFCN. Each ARFCN isshared between 8 mobiles, each using it in turn. Each mobileuses the ARFCN for one TS (Timeslot) and then waits for itsturn to come around again. A mobile has use of the ARFCNonce per the TDMA frame. The combination of a TS numberand ARFCN is called a physical channel.

ARQ Automatic Repeat-reQuest. Error control for datatransmission in which the receiver detects transmission errorsin a message and automatically requests a retransmissionfrom the transmitter.

ARP Address Resolution Protocol. A Transmission ControlProtocol / Internet Protocol (TCP/IP) protocol that dynamicallybinds 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 whichprovides an AP with the means to establish and control anassociation with an AP in a remote NE. Maps directly ontothe Presentation layer (OMC).

ASCII American Standard Code for Information Interchange. ASCIIis a standard developed by ANSI to define how computerswrite and read characters. It is the most common format fortext files in computers and on the Internet. In an ASCII file,alphabetic, numeric, and special characters are representedwith a 7-binary digit binary number. 128 possible charactersare defined. UNIX and DOS-based operating systems (exceptfor Windows NT) use ASCII for text files. Windows NT uses anewer code, Unicode. IBM�s System 390 servers use aproprietary 8-bit code called extended binary-coded decimalinterchange code. Conversion programs allow differentoperating systems to change a file from one code to another.

ASE Application Service Element (OMC). A coherent set ofintegrated functions to help accomplish applicationcommunication, e.g., within an application entity (AE).

ASE Application Specific Entity (TCAP).

ASN.1 Abstract Syntax Notation One. A formal notation used fordescribing data transmitted by telecommunications protocols,regardless of language implementation and physicalrepresentation 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 arecompleted 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 andswitching method utilising fixed-length cells of 53 octets tosupport multiple types of traffic.

ATT (flag) ATTach.


02 May 2003


68P02901W01-M 7�7

ATTS Automatic Trunk Testing Subsystem. Ensures the quality oftelephone lines by means of a series of tests. ATTS can beinitiated by either an operator command or by a commandfile, which can be activated at a predetermined time.

AU Access Unit.

AUC Authentication Centre. A GSM network entity which providesthe functionality for verifying the identity of an MS whenrequested by the system. Often a part of the HLR.

AUT(H) AUThentication.

AUTO AUTOmatic mode.

B Interface - Byte

B Interface Interface between MSC and VLR.

BA BCCH Allocation. The radio frequency channels allocated in acell 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 orsignalling rate of a communication channel is measured. Onebaud is one symbol (state transition or level-transition) persecond. This coincides with bits per second only for two-levelmodulation with no framing or stop bits

BBBX Battery Backup Board.

BBH Base Band Hopping. Method of frequency hopping in whicheach transceiver at the base station is tuned to a differentfrequency, and the signal is switched to a different transceiverfor each burst.

BCC Base station Colour Code. The BCC and the NCC are part ofthe BSIC. The BCC comprises three bits in the range 000 to111. See also NCC and BSIC.

BCCH Broadcast Control CHannel. A GSM control channel used tobroadcast general information about a BTS site on a per cellor sector basis.

BCD Binary Coded Decimal. The representation of a decimal digitby a unique arrangement of no fewer than four binary digits.

BCF Base station Control Function. The GSM term for the digitalcontrol circuitry which controls the BTS. In Motorola cell sitesthis is a normally a BCU which includes DRI modules and islocated in the BTS cabinet.

B channel Bearer channel. Used in ISDN services to carry 64kbit/s ofdata, when used at full capacity.

BCIE Bearer Capability Information Element. Specific GSMparameters in the Setup message are mapped into a BCIEfor signalling to the network and within the PLMN. The BCIEis used to request a bearer service (BS) from the network.

BCU Base station Control Unit. A functional entity of the BSSwhich provides the base control function at a BTS site. Theterm no longer applies to a type of shelf (see BSC and BSU).

BCUP Base Controller Unit Power.


02 May 20037�8


68P02901W01-M

BER Bit Error Rate. The number of erroneous bits divided by thetotal number of bits transmitted, received, or processed oversome stipulated period. The BER is usually expressed as acoefficient and a power of 10; for example, 25 erroneous bitsout of 100,000 bits transmitted would be 25 out of 105 or 25 x10-5.

BES Business Exchange Services.

BFI Bad Frame Indication. An indication of unsuccessfullydecoded speech frames. See FER.

BH Busy Hour. In a communications system, the sliding60-minute period during which occurs the maximum totaltraffic load in a given 24-hour period.

BHCA Busy Hour Call Attempt. A statistic based on call attemptsthat 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 12balanced (6-pair) 120 ohm (37-pin D-type connector) lines for2 Mbit/s circuits. See also T43.

BIC-Roam Barring of all Incoming Calls when Roaming outside theHome PLMN Country supplementary service.

Bi-directional neighbour See Reciprocal neighbour..

BIM Balanced-line Interconnect Module.

Bin From BINary. An area in a data array used to storeinformation. Also, a name for a directory that contain filesstored in binary format.

BL BootLoad. Also known as download. For example, databasesand 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 twostates or digits (0 or 1) in the numeration system with a radixof 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 onesecond. For example, an eight-bit parallel transmission linkwhich transfers one character (eight bits) per second isoperating at 8 bps.

block A group of bits (binary digits) transmitted as a unit, over whicha 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 aparticular bit period within a timeslot.

BPF Bandpass Filter. A filter that ideally passes all frequenciesbetween two non-zero finite limits and bars all frequencies notwithin the limits.

BPSM mBCU Power Supply Module.


02 May 2003


68P02901W01-M 7�9

BRI Basic Rate Interface. An ISDN multipurpose user interfaceallowing simultaneous voice and data services provided overtwo clear 64 kb/s channels (B channels) and one clear 16kb/s channel (D channel). The interface is also referred to as2B+D.

BS Base Station. See BSS.

BS Basic Service (group).

BS Bearer Service. A type of telecommunication service thatprovides the capability for the transmission of signalsbetween user-network interfaces. The PLMN connection typeused to support a bearer service may be identical to that usedto support other types of telecommunication service.

BSC Base Station Controller. A network component in the GSMPLMN which has the digital control function of controlling allBTSs. The BSC can be located within a single BTS cabinet(forming a BSS) but is more often located remotely andcontrols several BTSs (see BCF, BCU, and BSU).

BSG Basic Service Group.

BSIC Base Transceiver Station Identity Code. Each cell has aBSIC. It is a local colour code that allows a mobile station todistinguish between different neighbouring base stations. TheBSIC is an octet, consisting of three bits for the NetworkColour Code (NCC) and three bits for the Base station ColourCode (BCC). The remaining two bits are unused. See alsoNCC 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) thatcontains the forward sequence number (FSN) of a correctlyreceived signal unit being acknowledged in the signal unit thatis 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 theMSC through a single interface as defined by the GSM 08series of recommendations, as being the entity responsiblefor communicating with MSs in a certain area. The radioequipment of a BSS may cover one or more cells. A BSSmay consist of one or more base stations. If an internalinterface is implemented according to the GSM 08.5x seriesof recommendations, then the BSS consists of one BSC andseveral BTSs.

BSSAP BSS Application Part (part of SS7) . Protocol for LAPD orLAPB signalling links on the A-interface. Comprises DTAPand BSSMAP messages. Supports message communicationbetween the MSC and BSS.

BSSC Base Station System Control cabinet. The cabinet whichhouses one or two BSU shelves at a BSC or one or two RXUshelves at a remote transcoder (RXCDR).

BSSMAP Base Station System Management Application Part (part ofSS7). Call processing protocol for A-interface messagesexchanged between the MSC and BSS. The BSS interpretsthese messages.


02 May 20037�10


68P02901W01-M

BSSOMAP BSS Operation and Maintenance Application Part (part ofSS7).

BSU Base Station Unit shelf. The shelf which houses the digitalcontrol 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 thebus, each bus segment has to be terminated at its physicalbeginning 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 basictask groups within the GPROC.

BTS Base Transceiver Station. A network component in the GSMPLMN 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. Thephysical 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 informationin a data store or memory.

C - CW

C Conditional.

C Interface Interface between MSC and HLR/AUC.

C7 See SS7.

CA Cell Allocation. The radio frequency channels allocated to aparticular cell.

CA Central Authority. Software process that controls the BSS.

CAB Cabinet.

CADM Country ADMinistration. The Motorola procedure used withinDataGen to create new country and network files in theDataGen database.

CAI Charge Advice Information.

CAT Cell Analysis Tool. The CAT is part of the Motorola CellOptimization product. It is intended for engineering staff andOMC administrators. CAT provides information about GSMnetwork cell performance.

CB Cell Balancer. The CB process balances the cells configuredfor GPRS across PRPs. In the event of a PRP outage, thisprocess sends message(s) indicating that GPRS service isunavailable to the appropriate CRM(s) for the cells that couldnot be moved to an INS (IN Service) PRP.

CB Cell Broadcast. See CBSMS.

CB Circuit Breaker.

CBA Cell Broadcast Agent.


02 May 2003


68P02901W01-M 7�11

CBC Cell Broadcast Centre. The call processing centre for CBSMSmessages.

CBCH Cell Broadcast CHannel. The channel which is used tobroadcast messages to all MSs in a specific cell.

CBF Combining Bandpass Filter.

CBL Cell Broadcast Link. A bi-directional data link which allowscommunications between the BSS and the CBC.

CBM Circuit Breaker Module.

CDMA Code-Division Multiple Access. CDMA is a digital cellulartechnology that uses spread-spectrum techniques. Unlikecompeting systems, such as GSM, that use TDM, CDMAdoes not assign a specific frequency to each user. Instead,every channel uses the full available spectrum. Individualconversations are encoded with a pseudo-random digitalsequence.

CBMI Cell Broadcast Message Identifier.

CBS Cell Broadcast Service. See CBSMS.

CBSMS Cell Broadcast Short Message Service. CBSMS allows anumber of unacknowledged general messages to bebroadcast to all MSs within a particular region. The contentmay include information such as local traffic conditions, theweather, the phone number of the local taxi company, etc.The messages are sent from a CBC via a BSC to a BTS andfrom there on a special cell broadcast channel to the MSs.The CBC is considered as a node outside the PLMN and canbe connected to several BSCs. However, a BSC is onlyconnected to one CBC.

CBUS Clock Bus.

CC Connection Confirm. Part of SCCP network connectivity.

CC Country Code. A one to three digit number which specificallyidentifies a country of the world that an international call isbeing routed to (e.g., 1 = North America, 44 = UnitedKingdom).

CC Call Control. CC functions, such as number translations androuteing, matrix path control, and allocation of outgoing trunksare performed by the MSC.

CCB Cavity Combining Block, a three way RF combiner. Thereare two types of CCB, CCB (Output) and CCB (Extension).These, with up to two CCB Control cards, may comprise theTATI. The second card may be used for redundancy.

CCBS Completion of Calls to Busy Subscriber supplementaryservice.

CCCH Common Control CHannels. A class of GSM controlchannels used to control paging and grant access. IncludesAGCH, 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 20037�12


68P02901W01-M

CCH Control CHannel. Control channels are channels which carrysystem management messages.

CCH Council for Communications Harmonization (referred to inGSM Recommendations).

CCITT Comité Consultatif International Télégraphique etTéléphonique. This term has been superseded. SeeITU-TSS.

CCM Current Call Meter.

CCP Capability/Configuration Parameter.

CCPE Control Channel Protocol Entity.

CCS Hundred call-seconds. A single call lasting one hundredseconds is one CCS. Also, a measure of traffic load obtainedby multiplying the number of calls per hour by the averageholding time per call expressed in seconds, and dividing by100. Often used in practice to mean hundred call seconds perhour with �per hour� implied; as such, it is a measure of trafficintensity. See also erlang.

CCU Channel Codec Unit. The CCU performs the followingfunctions:Channel coding functions, including FEC and interleaving,Radio channel measurement functions, including receivedquality level, received signal level, and information related totiming 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, whichincludes calling and called numbers, local and remote nodenames, data and timestamp, elapsed time, and call failureclass fields. This is the information needed to bill thecustomer 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.


02 May 2003


68P02901W01-M 7�13

CEIR Central Equipment Identity Register.

Cell By GSM definition, a cell is an RF coverage area. At anomni-site, cell is synonymous with site; at a sectored site, cellis synonymous with sector. This differs from analoguesystems where cell is taken to mean the same thing as site.(See below).

Omni Site1-Cell Site

(1 BTS)

6-Sector Siteor

6-Cell Site(6 BTSs)

1 Cell =1 Sector

CEND End of charge point. The time at which the calling, or called,party stops charging by the termination of the call or by anequivalent procedure invoked by the network or by failure ofthe radio path.

CEPT Conférence des administrations Européennes des Postes etTelecommunications.

CERM Circuit Error Rate Monitor. Identifies when discontinuity isdetected in a circuit. An alarm is generated and sent to theOMC-R when the error count exceeds an operator specifiedthreshold. The alarm identifies the RCI or CIC and the pathwhere the error is detected.

CF Conversion Facility.

CF Call Forwarding. A feature available to the mobile telephoneuser whereby, after initiation of the feature by an authorisedsubscriber, calls dialled to the mobile telephone of anauthorised subscriber will automatically be routed to thedesired number. See also CFC and CFU.

CF Control Function. CF performs the SGSN mobilitymanagement functions and OA&M functions for the GSNmodule.

CFB Call Forwarding on mobile subscriber Busy supplementaryservice. Service automatically redirects incoming calls forphone busy situations.

CFC Call Forwarding Conditional supplementary service. Serviceautomatically redirects incoming calls for busy, no reply, ornot reachable situations. See also CFB, CFNRc, and CFNRy.

CFNRc Call Forwarding on mobile subscriber Not Reachablesupplementary service. Service automatically redirectsincoming calls for not reachable situations.

CFNRy Call Forwarding on No Reply supplementary service. Serviceautomatically redirects incoming calls for no reply situations.

CFU Call Forwarding Unconditional supplementary service.Service automatically redirects all incoming calls.

CG Charging Gateway.


02 May 20037�14


68P02901W01-M

CGF Charging Gateway Function.

Channel A means of one-way transmission. A defined sequence ofperiods (for example, timeslots) in a TDMA system; a definedfrequency band in an FDMA system; a defined sequence ofperiods and frequency bands in a frequency hopped system.

CIM Coaxial Interconnect Module.

Channel Mode See Full Rate and Half Rate. These are the channel modesthat are currently used.

CHP CHarging Point.

CHV Card Holder Verification information.

CKSN Ciphering Key Sequence Number. The CKSN is a numberwhich is associated with the ciphering key, Kc. It is used toensure authentication consistency between the MS and theVLR.

CI Cell Identity. A block of code which identifies a cell within alocation area.

CI CUG Index.

CIC Circuit Identity Code. The unique identifier of the terrestrialportion of a circuit path. A CIC is either a 64 kbit/s or 16 kbit/sconnection depending on whether a site has local or remotetranscoding. A CIC with local transcoding occupies acomplete E1/T1 timeslot. A 16 kbit/s CIC, at a site withremote transcoding, occupies a sub-channel of an E1/T1timeslot.

CIR, C/I Carrier to Interference Ratio. Indicates the received signalpower 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 CLIPand CLIR.

CLIP Calling Line Identification Presentation supplementaryservice. Allows the called party to identify the caller. See alsoCLIR.

CLIR Calling Line Identification Restriction supplementary service.Allows the caller to withhold their identity from the calledparty. See also CLIP.

CLK Clock.

CLKX Clock Extender half size board. The fibre optic link thatdistributes GCLK to boards in system (part of the BSS, etc).

CLM ConnectionLess Manager. Coordinates global control over theBSS by handling of all connectionless messages (that is,messages that are not directly concerned with a connectedcall). This includes such messages as global resets, loadlimiting and circuit blocking.

CLR CLeaR.

CM Configuration Management. Configuration managementallows the operator to perform network configuration tasks,and to maintain all details of the network configuration at theOMC.


02 May 2003


68P02901W01-M 7�15

CM Connection Management. See CLM.

CM Connectionless Manager. See CLM.

CMD CoMmanD.

CMM Channel Mode Modify. Message sent to an MS to request achannel mode change. When it has received the CMMmessage, the MS changes the mode to the indicated channeland replies with a Channel Mode Modify Acknowledgemessage indicating the new channel mode.

CMIP Common Management Information Protocol. Protocol usedfor communication over the OML.

CMISE Common Management Information Service Element. An ASEwhich provides a means to transfer management informationvia CMIP messages with another NE over an associationestablished by ASCE using ROSE (OMC).

CMR Cellular Manual Revision. Documentation updates.

CNG CalliNg tone.

Codec Coder/Decoder. A speech coding unit that converts speechinto a digital format for radio broadcast, and vice versa.

CODEX Manufacturer�s name for a type of multiplexer and packetswitch commonly installed at the Motorola OMC-R.

Coincident Cell A cell whose cell boundary follows the boundary of aco-located neighbour cell. The coincident cell has a differentfrequency type, but the same BSIC, as that of the neighbourcell.

COLI COnnected Line Identity. Identity of the connected line. Seealso COLP and COLR.

Collocated Placed together; two or more items together in the sameplace.

Colour Code An 8-bit code assigned to a BTS to distinguish interferingsignals from another cell.

COLP COnnected Line Identification Presentation supplementaryservice. Allows the calling party to identify the line identity ofthe connected party. See also COLR.

COLR COnnected Line Identification Restriction supplementaryservice. Allows the connected party to withhold its line identityfrom the calling party. See also COLP.

COM Code Object Manager (software).

COM COMplete.

COMB Combiner. The purpose of a combiner in the BSS is tocombine transmitter outputs from the RCUs onto an antenna.

COMM, Comms COMMunications.

CommHub Communications Hub. Provides Ethernet switching and IProuteing for the GSN complex local networking and GSNcomplex 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 conferencecalls.


02 May 20037�16


68P02901W01-M

CONFIG CONFIGuration Control Program.

Congestion Situation occurring when an element cannot receive all theservice it is requesting.

CONNACK CONNect ACKnowledgement. Part of the synchronizationprocess. After a connection has been established, theCONNACK message indicates that traffic channels areavailable.

CP Call Processing. The CP process in the BTS controls the MSto BSS to MS signalling link, MS originated and terminatedcalls and inter-BSS and inter-BTS handovers.

cPCI Compact Peripheral Component Interconnect. A set ofstandards that define a common card cage, power supplies,and processor boards.

CPGM CCCH Paging Manager. The CPGM processes the pagingmessages sent from the SGSN to the BSC/BTS.

CPU Central Processing Unit. The portion of a computer thatcontrols the interpretation and execution of instructions.

Also, the portion of a digital communications switch thatexecutes programmed instructions, performs arithmetic andlogical operations on signals, and controls input/outputfunctions.

C/R Command/Response field bit.

CR Carriage Return (RETURN).

CR Connection Request (Part of SCCP network connectivity). AnSCCP Connection Request message is sent from the BSS tothe MSC to establish a connection. See also CREF.

CRC Cyclic Redundancy Check (3 bit). An error-detection schemethat (a) uses parity bits generated by polynomial encoding ofdigital signals, (b) appends those parity bits to the digitalsignal, and (c) uses decoding algorithms that detect errors inthe received digital signal.

CRE Call RE-establishment procedure. Procedure forre-establishing a call in the event of a radio link failure.

CREF Connection REFused (Part of SCCP network connectivity). Ina number of operating circumstances, a CREF message maybe sent from the MSC to the BSS in response to aConnection Request (CR).

CRM Cell Resource Manager. The CRM allocates and activatestimeslots and subchannels on the available carriers.

CRM Cell Resource Machine.

CRM-LS/HS Cellular Radio Modem-Low Speed/High Speed. Low speedmodem used to interwork 300 to 2400 bit/s data servicesunder V.22bis, V.23, or V.21 standards. High speed modemused to interwork 1200 to 9600 bit/s data services underV.22bis, V.32, or V.29/V.27ter/V.21 standards.

CRO Motorola Controlled Roll Out Group. A CRO consists of acustomer site implementation of a new product, softwarerelease, or combination of products/releases.

CRT Cathode Ray Tube (video display terminal).

CS-1 GPRS Coding Scheme-1 (9.05 kbit/s per TCH).


02 May 2003


68P02901W01-M 7�17




CSFP Code Storage Facility Processor (at BSC and BTS). AGPROC device which facilitates the propagating of newsoftware instances with reduced system down time. See alsoIP.

CSP Central Statistics Process. The statistics process in the BSC.

CSPDN Circuit Switched Public Data Network. A publicly availablecommunications network using circuit switched digital datacircuits.

CT Call Transfer supplementary service.

CT Channel Tester.

CT Channel Type.

CTP Call Trace Product (Tool). The CTP is designed to helpoperators of GSM900 and DCS1800 communication networkstune and optimize their systems. CTP allows Call Trace datato be analysed and decoded.

CTP Control Terminal Port.

CTR Common Technical Regulation.

CTS Clear to Send. A handshake signal used with communicationlinks, especially RS232 or CCITT Rec. V.24, to indicate (to atransmitter from a receiver) that transmission may proceed.Generated in response to a request to send signal. See alsoRTS.

CTU Compact Transceiver Unit (M-Cellhorizon radio).

CUG Closed User Group supplementary service. A CUG is used tocontrol who can receive and/or place calls, by creating aunique group. When a CUG is configured for an interface,only those subscribers that are members of the same CUGcan receive/place calls.

Cumulative value The total value for an entire statistical interval.

CW Call Waiting supplementary service. A subscriber featurewhich allows an individual mobile telephone user currentlyengaged in a call to be alerted that another caller is trying toreach him. The user has a predetermined period of time inwhich to terminate the existing conversation and respond tothe second call.


02 May 20037�18


68P02901W01-M

D Interface - DYNET

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 inputnumber sequence into a function of a continuous variable.

DACS Digital Access Cross-connect System. A data concentratorand 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 playbackmedium/format that maintains a signal quality equal to that ofthe CD-ROM medium/format.

DataGen Sysgen Builder System. A Motorola offline BSS binary objectconfiguration tool.

Data Link Layer See OSI RM. This layer responds to service requests fromthe Network Layer and issues service requests to thePhysical Layer. It provides the functional and proceduralmeans to transfer data between network entities and to detectand possibly correct errors that may occur in the PhysicalLayer.

dB Decibel. A unit stating the logarithmic ratio between twonumeric 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 ofelectric charge carriers, usually electrons. The intensity of thecurrent can vary with time, but the general direction ofmovement stays the same at all times. As an adjective, theterm DC is used in reference to voltage whose polarity neverreverses.

DCB Diversity Control Board (part of DRCU).

DCCH Dedicated Control CHannel. A class of GSM controlchannels used to set up calls and report measurements.Includes SDCCH, FACCH, and SACCH.

DCD Data Carrier Detect signal. Hardware signal defined by theRS-232-C specification that indicates that a device such as amodem is on-line and ready for transmission.


02 May 2003


68P02901W01-M 7�19

DCE Data Circuit terminating Equipment. The DCE performsfunctions such as signal conversion and coding, at thenetwork 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 astraight cable, but to other DCE equipment only with a nullmodem cable.

DCF Data Communications Function.

DCF Duplexed Combining bandpass Filter. (Used inHorizonmacro).

D channel Data channel. Used in ISDN to perform call signalling andconnection setup functions. In some circumstances, thechannel can also be used to carry user data.

DCN Data Communications Network. A DCN connects NetworkElements with internal mediation functions or mediationdevices to the Operations Systems.

DC PSM DC Power Supply Module.

DCS1800 Digital Cellular System at 1800 MHz. A cellular phonenetwork using digital techniques similar to those used in GSM900, but operating on frequencies of 1710 - 1785 MHz(receive) and 1805 - 1880 MHz (transmit).

DDF Dual-stage Duplexed combining Filter. (Used inHorizonmacro). The DDF is an integrated combiner, filter andduplexer.

DDS DataGen Data Store. Store area for DataGen input andoutput files.

DDS Data Drive Storage.

DDS Direct Digital Synthesis. A technology for generating highlyaccurate and frequency-agile (rapidly changeable frequencyover 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 datarelating to a specified problem and copies it to tape or file,together with a problem description. The file or tape is thensent to Motorola for analysis.

DHP Digital Host Processor. A hard GPROC based device locatedat Horizonmicro2 BTS sites. It represents the MCU of a slaveHorizonmicro2 FRU. The MCU that the DHP represents isresponsible 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 20037�20


68P02901W01-M

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 transmissionsystems, 13-bit field that defines the destination address of apacket. 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 intoRLC data blocks to be transmitted over the air interface.

DLSP Data Link Service Process. Handles messages for an OMPand 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; animmediate or deferred response is required (see also PMA).

DMA Direct Memory Access. Transfer of data from a peripheraldevice, such as a hard disk drive, into memory without thatdata passing through the microprocessor. DMA transfers datainto memory at high speeds with no processor overhead.

DMR Digital Mobile Radio.

DMX Distributed Electronic Mobile Exchange (Motorola�snetworked EMX family).

DN Directory Number.

DNIC Data Network Identifier Code. In the CCITT InternationalX.121 format, the first four digits indicate the internationaldata 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 logicaldomain 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 instrumentthat interrupts a steady current at a sequence and ratedetermined by the selected digit and the operatingcharacteristics of the instrument.

DPC Destination Point Code. A part of the label in a signallingmessage 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 issampled and the difference between the actual value of eachsample and its predicted value, derived from the previoussample or samples, is quantified and converted, by encoding,to a digital signal. Note: There are several variations ofdifferential pulse-code modulation.


02 May 2003


68P02901W01-M 7�21

DPNSS Digital Private Network Signalling System (BT standard forPABX 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 semiconductormemory in which the information is stored in capacitors on aintegrated circuit.

DRC Data Rate Converter board. Provides data and protocolconversion between PLMN and destination network for 8circuits. Part of IWF.

DRCU Diversity Radio Channel Unit. Contains transceiver, digitalcontrol circuits, and power supply. Part of the BSS.

DRI Digital Radio Interface. Provides encoding/decoding andencryption/decryption for radio channels. Part of BSS.

DRIM Digital Radio Interface extended Memory. A DRI with extramemory.

DRIX DRI Extender half size board. Fibre optic link from DRI toBCU. Part of the BSS.

DRX, DRx Discontinuous reception (mechanism). A means of savingbattery power (for example in hand-portable units) byperiodically and automatically switching the MS receiver onand off.

DS-1 Digital transmission System 1 (or Digital Signal level 1). Termused 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 thatrelies on the pauses between speech bursts to provideadditional compression. DSI enables users to gain anadditional 2:1 compression on the average on their line.

DSP Digital Signal Processor. A specialized, programmablecomputer processing unit that is able to perform high-speedmathematical processing.

DSS1 Digital Subscriber Signalling No 1. N-ISDN user networkinterface signalling.

DSSI Diversity Signal Strength Indication.

DTAP Direct Transfer Application Part (Part of SS7). Call processingprotocol for A-Interface messages exchanged directlybetween the MSC and the mobile unit without interpretationby the BSS.

DTE Data Terminal Equipment. An end instrument that convertsuser information into signals for transmission or reconvertsthe received signals into user information.

Also, the RS232 configuration designated for terminals. DTEequipment can be connected to DCE with a straight cable,but to other DTE equipment only with a null modem.


02 May 20037�22


68P02901W01-M

DTF Digital Trunk Frame. A frame or electronic rack of digital trunkinterface equipment.

DT1 DaTa form 1 (Part of SCCP network connectivity).

DTI Digital Trunk Interface.

DTMF Dual Tone Multi-Frequency. Multifrequency signalling in whichspecified combinations of two voice band frequencies, onefrom a group of four low frequencies and the other from agroup of four higher frequencies, are used. The sounds apush button tone telephone makes when it dials a number.

DTR Data Terminal Ready signal. Method of flow control (RS232Interface). A modem interface control signal sent from theDTE to the modem, usually to indicate to the modem that theDTE is ready to transmit data.

DTRX Dual Transceiver Module. (Radio used in Horizonmicro(M-Cellarena) and Horizonmacro (M-Cellarenamacro)).

DTX, DTx Discontinuous Transmission (mechanism). A means ofsaving battery power (for example in hand-portable units) andreducing interference by automatically switching thetransmitter off when no speech or data are to be sent.

Dummy burst A period of carrier less than one timeslot whose modulation isa defined sequence that carries no useful information. Adummy burst fills a timeslot with an RF signal when noinformation is to be delivered to a channel.

DYNET DYnamic NETwork. Used to specify BTSs sharing dynamicresources.

E - EXEC

E See Erlang.

E1 Also known as CEPT1. The 2.048 Mbit/s rate used byEuropean CEPT carrier to transmit 30 64 kbit/s digitalchannels for voice or data calls, plus a 64 kbit/s signallingchannel 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: Dooropen, High humidity, Low humidity, Fire, Intruder.

EAS External Alarm System. The EAS is responsible for themonitoring of all customer-defined environmental alarms at asite. The customer defines the alarm string and the severityof 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 perbit and No is the noise energy per hertz of noise bandwidth.

EBCG Elementary Basic Service Group.

EC Echo Canceller. Performs echo suppression for all voicecircuits. If cancellation does not take place, the PLMNsubscriber hears the voice signal as an echo, due to the totalround-trip delay introduced by the GSM system (typically 180ms).

ECB Provides echo cancelling for telephone trunks for 30 channels(EC).


02 May 2003


68P02901W01-M 7�23

ECID The Motorola European Cellular Infrastructure Division.

ECM Error Correction Mode. A facsimile mode, in which thesending machine will attempt to send a partial page up to fourtimes.

Ec/No Ratio of energy per modulating bit to the noise spectraldensity.

ECT Event Counting Tool. The ECT provides information about thenumber and type of events and alarms generated throughoutthe network. It extracts data from the event log files forspecified dates, allowing the user to generate reports onindividual network elements, groups of elements, or the wholenetwork.

ECT Explicit Call Transfer supplementary service. ECT enables auser to connect two other parties with which he is engaged ina telephone call and leave the connection himself.

EEL Electric Echo Loss.

EEPROM Electrically Erasable Programmable Read Only Memory. AnEEPROM is a special type of PROM that can be erased byexposing it to an electrical charge. Like other types of PROM,EEPROM retains its contents even when the power is turnedoff.

EGSM900 Extended GSM900. EGSM900 provides the BSS with afurther range of frequencies for MS and BSS transmit. EGSMMSs can use the extended frequency band as well as theprimary band, while non-EGSM MSs cannot use theextended frequency band. A GSM900 cell can contain bothGSM900 and EGSM900 carrier hardware. EGSM operateson the frequency range, 880 - 915 MHz (receive) and925 - 960 MHz (transmit).

EI Events Interface. Part of the OMC-R GUI.

EIR Equipment Identity Register. The EIR contains a centralizeddatabase for validating the IMEI. The register consists of listsof IMEIs organised as follows:White List - IMEIs which are known to have been assigned tovalid MS equipment.Black List - IMEIs which have been reported stolen or whichare to be denied service for some other reason.Grey List - IMEIs which have problems (for example, faultysoftware). These are not, however, sufficiently significant towarrant a black listing.

EIRP Effective Isotropically Radiated Power. The arithmetic productof 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 acentralised facility for reporting network-wide generatedevents and alarms, and for monitoring the status of theNetwork.


02 May 20037�24


68P02901W01-M

EMC ElectroMagnetic Compatibility. The ability of systems,equipment, and devices that utilize the electromagneticspectrum to operate in their intended operationalenvironments without suffering unacceptable degradation orcausing unintentional degradation because of electromagneticradiation or response.

EMF Electro Motive Force. The rate at which energy is drawn froma source that produces a flow of electricity in a circuit;expressed in volts.

EMI Electro Magnetic Interference. Any electromagneticdisturbance that interrupts, obstructs, or otherwise degradesor limits the effective performance of electronics/electricalequipment.

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 incombination with fast call set-up. Pre-emption involves theseizing of resources, which are in use by a call of a lowerprecedence, by a higher level precedence call in the absenceof idle resources. Pre-emption can also involve thedisconnection of an on-going call of lower precedence toaccept an incoming call of higher precedence.

EMMI Electrical Man Machine Interface.

EMU Exchange office Management Unit (part of Horizonoffice)

EMX Electronic Mobile Exchange (Motorola�s MSC family).

en bloc Fr. � all at once (a CCITT #7 Digital Transmission scheme);En bloc sending means that digits are sent from one systemto another ~ (that is, all the digits for a given call are sent atthe same time as a group). ~ sending is the opposite ofoverlap sending. A system using ~ sending will wait until ithas collected all the digits for a given call before it attempts tosend digits to the next system. All the digits are then sent asa group.

EOT End of Tape.

EPROM Erasable Programmable Read Only Memory. EPROM is atype of memory that retains its contents until it is exposed toultraviolet light. The ultraviolet light clears its contents,making it possible to re-program the memory.

EPSM Enhanced Power Supply Module. Used in +27 V positiveearth cabinets.

EQ50 Static model against which the performance of the equalizeris tested to extremes. See also TU3, TU50, HT100 andRA250.

EQB Equalizer Board. Control circuit for equalization for 8 timeslots 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 isrendered essentially constant over a band of frequencies,even though the transmission medium or the equipment haslosses that vary with frequency.


02 May 2003


68P02901W01-M 7�25

Equalizer An electrical network in which attenuation (or gain) and/orphase shift varies as a function of frequency. Used to provideequalization.

Erlang International (dimensionless) unit of traffic intensity defined asthe ratio of time a facility is occupied to the time it is availablefor occupancy. One erlang is equal to 36 CCS. In the USthis is also known as a traffic unit (TU).

ERP Ear Reference Point. Facility for assessing handset andheadset acoustic responses.

ERP Effective Radiated Power. The power supplied to an antennamultiplied by the antenna gain in a given direction.

ERR ERRor.

ESP Electro-static Point. Connection point on the equipment for ananti-static wrist strap.

ESQL Embedded SQL (Structured Query Language). An RDBMSprogramming interface language.

E-TACS Extended TACS (analogue cellular system, extended).

Ethernet A standard protocol (IEEE 802.3) for a 10 Mbit/s basebandlocal area network (LAN) bus using carrier-sense multipleaccess with collision detection (CSMA/CD) as the accessmethod, implemented at the Physical Layer in the OSI RM,establishing the physical characteristics of a CSMA/CDnetwork.

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 facsimileapparatus in order to be able to communicate over a GSMPLMN.

FA Full Allocation.

FA Functional Area.

FAC Final Assembly Code.

FACCH Fast Associated Control Channel. A GSM dedicated controlchannel which temporarily uses the TCH to perform highspeed transmissions, and carries control information after acall is set up. See also SDCCH.

FACCH/F Fast Associated Control Channel/Full rate. See also FullRate.

FACCH/H Fast Associated Control Channel/Half rate. See also HalfRate.

FB See Frequency correction burst.


02 May 20037�26


68P02901W01-M

FBM Flow control Buffer Management. FBM is a functional unitresiding on the PRP. It controls buffer capacity for each celland each mobile so that the incoming data from the SGSNmatches the air throughput.

FC-AL Fibre Channel Arbitrated Loop. A serial data transferarchitecture. FC-AL is designed for mass storage devices andother peripheral devices that require very high bandwidth.Using optical fibre to connect devices, FC-AL supportsfull-duplex data transfer rates of 100MBps.

FCCH Frequency Correction CHannel. A GSM broadcast controlchannel which carries information for frequency correction ofthe MS.

FCP Fault Collection Process. Part of the fault managementprocess in the BTS.

FCS Frame Check Sequence. The extra characters added to aframe for error detection and correction.

FDM Frequency Division Multiplex. A multiplexing technique thatuses different frequencies to combine multiple streams ofdata for transmission over a communications medium. FDMassigns a discrete carrier frequency to each data stream andthen combines many modulated carrier frequencies fortransmission.

FDMA Frequency Division Multiple Access. The use of frequencydivision to provide multiple and simultaneous transmissions toa single transponder.

FDN Fixed Dialling Number. The fixed dialling feature limits diallingfrom the MS to a pre-determined list maintained on the SIMcard. 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 errorsby transmitting additional information with the original bitstream. If an error is detected, the additional information isused to recreate the original information.

FEP Front End Processor. An OMC-R device. The FEP is a driverthat stores data in its own database about all of the sites inthe system. All bursts from the sites are directed to the FEP.It can also interrogate the sites and collect its data eithermanually or automatically at pre-defined times.

FER Frame Erasure Ratio. The ratio of successfully decoded goodspeech 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 togetherwith the forward sequence number and backward sequencenumber are used in the basic error control method to performthe signal unit sequence control and acknowledgementfunctions.

FIFO Memory logic device in which the information placed in thememory in a given order is retrieved in that order.


02 May 2003


68P02901W01-M 7�27

FIR Finite Impulse Response (filter type).

FK Foreign Key. A database column attribute; the foreign keyindicates an index into another table.

FM Fault Management (at OMC).

FM Frequency Modulation. Modulation in which the instantaneousfrequency of a sine wave carrier is caused to depart from thecentre frequency by an amount proportional to theinstantaneous value of the modulating signal.

FMIC Fault Management Initiated Clear. An alarm type. If an FMICalarm is received, the fault management software for thenetwork 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 TDMAframe within a hyperframe.

FOA First Office Application. A full functional verification of newproduct(s) on a commercial system using acceptedtechnology and approved test plans.

FOX Fibre Optic eXtender board.

FR See Full Rate.

FR Frame Relay. An interface protocol for statistically multiplexedpacket-switched data communications in which (a)variable-sized packets (frames) are used that completelyenclose the user packets they transport, and (b) transmissionrates are usually between 56 kb/s and 1.544 Mb/s (the T-1rate).

Frame A set of consecutive Pulse Code Modulation (PCM) time slotscontaining samples from all channels of a group, where theposition of each sample is identified by reference to a framealignment signal. Also, an information or signal structurewhich allows a receiver to identify uniquely an informationchannel.

Frame Alignment The state in which the frame of the receiving equipment issynchronized with respect to that of the received signal toaccomplish accurate data extraction.

FRU Field Replaceable Unit. A board, module, etc. which can beeasily replaced in the field with a few simple tools.

Frequency Correction Period of RF carrier less than one timeslot whose modulationbit stream allows frequency correction to be performed easilywithin an MS burst.

Frequency Hopping The repeated switching of frequencies during radiotransmission according to a specified algorithm. Frequencyhopping improves capacity and quality in a highly loadedGSM network. Multipath fading immunity can be increased byusing different frequencies and interference coming fromneighbour cells transmitting the same or adjacent frequenciescan be reduced.


02 May 20037�28


68P02901W01-M

FS Frequency Synchronization. All BSS frequencies and timingsignals are synchronized to a high stability referenceoscillator in the BSS. This oscillator can free run or besynchronized to the recovered clock signal from a selectedE1/T1 serial link. MSs lock to a reference contained in asynchronization burst transmitted from the BTS site.

FSL Free Space Loss. The decrease in the strength of a radiosignal as it travels between a transmitter and receiver. TheFSL is a function of the frequency of the radio signal and thedistance the radio signal has travelled from the point source.

FSN Forward Sequence Number. See FIB.

FTAM File Transfer, Access, and Management. An ASE whichprovides 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 auser on one computer to transfer files to and from anothercomputer over a TCP/IP network. Also the client program theuser executes to transfer files.

Full Rate Refers to the current capacity of a data channel on the GSMair interface, that is, 8 simultaneous calls per carrier. See alsoHR - Half Rate.

G Interface - GWY

G Interface Interface between VLR and VLR.

Gateway MSC An MSC that provides an entry point into the GSM PLMNfrom another network or service. A gateway MSC is also aninterrogating node for incoming PLMN calls.

GB, Gbyte Gigabyte. 230 bytes = 1,073,741,824 bytes = 1024megabytes.

GBIC Gigabit Interface Converter Converter for connection to theGigabit Ethernet.

GCLK Generic Clock board. System clock source, one per site (partof BSS, BTS, BSC, IWF, RXCDR).

GCR Group Call Register. The register which holds information aboutVGCS or VBS calls.

GDP Generic DSP Processor board. Interchangeable with the XCDRboard.

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 internetworking with external packet-switched networks.

GHz Giga-Hertz (109).

GID Group ID. A unique number used by the system to identify auser�s primary group.

GMB GSM Multiplexer Board (part of the BSC).

GMR General Manual Revision.


02 May 2003


68P02901W01-M 7�29

GMSC Gateway Mobile-services Switching Centre. See GatewayMSC.

GMSK Gaussian Minimum Shift Keying. The modulation techniqueused in GSM.

GND GrouND.

GOS Grade of Service. A traffic statistic defined as the percentageof calls which have a Probability of Busy or Queueing Delay.An alternative criterion is a maximum time for a percentage ofcalls to wait in the busy queue before they are assigned avoice channel.

GPA GSM PLMN Area.

GPC General Protocol Converter.

GPROC Generic Processor board. GSM generic processor board: a68030 with 4 to 16 Mb RAM (part of BSS, BTS, BSC, IWF,RXCDR).

GPROC2 Generic Processor board. GSM generic processor board: a68040 with 32 Mb RAM (part of BSS, BTS, BSC, IWF,RXCDR).

GPRS General Packet Radio Service. A GSM data transmissiontechnique that does not set up a continuous channel from aportable terminal for the transmission and reception of data,but transmits and receives data in packets. It makes veryefficient use of available radio spectrum, and users pay onlyfor the volume of data sent and received.

GPS Global Positioning by Satellite. A system for determiningposition on the Earth�s surface by comparing radio signalsfrom several satellites.

GSA GSM Service Area. The area in which an MS can be reachedby a fixed subscriber, without the subscriber�s knowledge ofthe location of the MS. A GSA may include the areas servedby several GSM PLMNs.

GSA GSM System Area. The group of GSM PLMN areasaccessible by GSM MSs.

GSM Groupe Spécial 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 bythe SGSN and GGSN.

GSN Complex A GSN Complex consists of an ISS Cluster, GGSN andSGSNs connected to a single CommHub.

GSR GSM Software Release.

GT Global Title. A logical or virtual address used for routing SS7messages using SCCP capabilities. To complete messagerouting, a GT must be translated to a SS7 point code andsubsystem number.


02 May 20037�30


68P02901W01-M

GTE Generic Table Editor. The Motorola procedure which allowsusers to display and edit MCDF input files.

Guard period Period at the beginning and end of timeslot during which MStransmission is attenuated.

GUI Graphical User Interface. A computer environment orprogram that displays, or facilitates the display of, on-screenoptions. These options are usually in the form of icons(pictorial symbols) or menus (lists of alphanumericcharacters) by means of which users may enter commands.

GUI client A computer used to display a GUI from an OMC-R GUIapplication which is being run on a GUI server.

GUI server A computer used to serve the OMC-R GUI applicationprocess 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

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 currentGSM air interface capacity to 16 simultaneous calls percarrier (see also FR - Full Rate).

HANDO, Handover HANDOver. The action of switching a call in progress fromone radio channel to another radio channel. Handover allowsestablished calls to continue by switching them to anotherradio resource, as when an MS moves from one BTS area toanother. Handovers may take place between the followingGSM entities: timeslot, RF carrier, cell, BTS, BSS and MSC.

HCU Hybrid Combining Unit. (Used in Horizonmacro). Part of theDDF, the HDU allows the outputs of three radios to becombined into a single antenna.

HDLC High level Data Link Control. A link-level protocol used tofacilitate reliable point-to-point transmission of a data packet.Note: A subset of HDLC, LAP-B, is the layer-two protocol forCCITT Recommendation X.25.

HDSL High bit-rate Digital Subscriber Line. HDSL is a datatransmission mechanism which supports duplex high speeddigital communication (at E1 rates) on one or moreunshielded twisted pair lines.

HLC High Layer Compatibility. The HLC can carry informationdefining the higher layer characteristics of a teleservice activeon the terminal.

HLR Home Location Register. The LR where the current locationand all subscriber parameters of an MS are permanentlystored.

HMS Heat Management System. The system that providesenvironmental control of the components inside the ExCell,TopCell and M-Cell cabinets.


02 May 2003


68P02901W01-M 7�31

HO HandOver. See HANDO.

HPU Hand Portable Unit. A handset.

HOLD Call hold supplementary service. Call hold allows thesubscriber to place a call on hold in order to make anothercall. When the second call is completed, the subscriber canreturn 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 thespecific hopping sequence (pattern) used in a given cell. Itranges from 0 to 63.

HT100 Hilly Terrain with the MS travelling at 100 kph. Dynamic modelagainst which the performance of a GSM receiver can bemeasured. See also TU3, TU50, RA250 and EQ50.

HU Home Units. The basic telecommunication unit as set by theHPLMN. This value is expressed in the currency of the homecountry.

HW Hardware.

Hybrid Combiner A combiner device which requires no software control and issufficiently broadband to be able to cover the GSMtransmitter frequency band. See also COMB.

Hybrid Transformer A circuit used in telephony to convert 2-wire operation to4-wire operation and vice versa. For example, every land-linetelephone contains a hybrid to separate earpiece andmouthpiece audio and couple both into a 2-wire circuit thatconnects the phone to the exchange.

Hyperframe 2048 superframes. The longest recurrent time period of theframe structure.

I - IWU

I Information frames. Part of RLP.

IA Incoming Access supplementary service. An arrangementwhich allows a member of a CUG to receive calls fromoutside the CUG.

IA5 International Alphanumeric 5 character set.

IADU Integrated Antenna Distribution Unit. The IADU is theequivalent of the Receive Matrix used on BTSs that pre-datethe M-Cell range.

IAM Initial Address Message. A message sent in the forwarddirection that contains (a) address information, (b) thesignaling information required to route and connect a call tothe called line, (c) service-class information, (d) informationrelating to user and network facilities, and (e) call-originatoridentity or call-receiver identity.


02 May 20037�32


68P02901W01-M

IAS Internal Alarm System. The IAS is responsible for monitoringall cabinet alarms at a BSS.

IC Integrated Circuit. An electronic circuit that consists of manyindividual circuit elements, such as transistors, diodes,resistors, capacitors, inductors, and other active and passivesemiconductor devices, formed on a single chip ofsemiconducting material and mounted on a single piece ofsubstrate material.

IC Interlock Code. A code which uniquely identifies a CUG withina network.

IC(pref) Interlock Code of the preferential CUG.

ICB Incoming Calls Barred. An access restriction that prevents aCUG member from receiving calls from other members ofthat 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 theInternet Protocol (IP) that allows for the generation of errormessages, test packets, and informational messages relatedto IP. The PING command, for example, uses ICMP to test anInternet connection.

ID, Id IDentification/IDentity/IDentifier.

IDN Integrated Digital Network. A network that uses both digitaltransmission and digital switching.

IDS Informix Dynamic Server. The OMC-R relational databasemanagement system.

IE Information Element. The part of a message that containsconfiguration or signalling information.

IEC International Electrotechnical Commission. An internationalstandards 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 carrierfrequency is shifted as an intermediate step in transmissionor reception.

IFAM Initial and Final Address Message.

IM InterModulation. The production, in a nonlinear element of asystem, of frequencies corresponding to the sum anddifference frequencies of the fundamentals and harmonicsthereof that are transmitted through the element.

IMACS Intelligent Monitor And Control System.

IMEI International Mobile station Equipment Identity. Electronicserial number that uniquely identifies the MS as a piece orassembly of equipment. The IMEI is sent by the MS alongwith request for service. See also IMEISV.


02 May 2003


68P02901W01-M 7�33

IMEISV International Mobile station Equipment Identity and SoftwareVersion number. The IMEISV is a 16 digit decimal numbercomposed 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 thenetwork 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 thenetwork to the MS to indicate that the MS must immediatelystart monitoring a specified channel.

IMSI International Mobile Subscriber Identity. Published mobilenumber (prior to ISDN) that uniquely identifies thesubscription. It can serve as a key to derive subscriberinformation such as directory number(s) from the HLR. Seealso MSISDN.

IN Intelligent Network. A network that allows functionality to bedistributed flexibly at a variety of nodes on and off thenetwork and allows the architecture to be modified to controlthe services.

IN Interrogating Node. A switching node that interrogates anHLR, to route a call for an MS to the visited MSC.

INS IN Service.

INS Intelligent Network Service. A service provided using thecapabilities of an intelligent network. See also IN.

InterAlg Interference Algorithm.

Intermittent Intermittent alarms are transient and not usually associatedwith a serious fault condition. After the intermittent alarms aredisplayed in the Alarm window, the operator must handle andclear the alarm. The system will report every occurrence of anintermittent alarm unless it is throttled. See also FMIC andOIC.

Interworking The general term used to describe the inter-operation ofnetworks, services, supplementary services and so on. Seealso 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 thenetwork quality. The IOS generates reports based onperformance data from the BTS and OMC-R.

IP Initialisation Process. The IP is primarily responsible forbringing up the site from a reset, including code loading thesite from a suitable code source. IP also provides the CSFPfunctionality, allowing two BSS code load version to beswapped very quickly, allowing the site to return to service assoon as possible.


02 May 20037�34


68P02901W01-M

IP Internet Protocol. A standard protocol designed for use ininterconnected systems of packet-switched computercommunication networks. IP provides for transmitting blocksof data called datagrams from sources to destinations, wheresources and destinations are hosts identified by fixed-lengthaddresses. The internet protocol also provides forfragmentation and reassembly of long datagrams, ifnecessary, for transmission through small-packet networks.See also TCP and TCP/IP.

IPC Inter-Process Communication. Exchange of data betweenone process and another, either within the same computer orover a network.

IP, INP INtermodulation Products. Distortion. A type of spuriousemission.

IPR Intellectual PRoperty.

IPSM Integrated Power Supply Module (-48 V).

IPX Internetwork Packet EXchange A networking protocol usedby the Novell NetWare operating systems. Like UDP/IP, IPXis a datagram protocol used for connectionlesscommunications. Higher-level protocols are used foradditional error recovery services.

Iridium A communications system comprising a constellation of 66low-earth-orbiting (LEO) satellites forming a mobile wirelesssystem allowing subscribers to place and receive calls fromany location in the world. The satellite constellation isconnected to existing terrestrial telephone systems through anumber of gateway ground-stations.

ISAM Indexed Sequential Access Method. A method for managingthe way a computer accesses records and files stored on ahard disk. While storing data sequentially, ISAM providesdirect access to specific records through an index. Thiscombination results in quick data access regardless ofwhether records are being accessed sequentially or randomly.

ISC International Switching Centre. The ISC routes calls to/fromother countries.

ISDN Integrated Services Digital Network. A digital network usingcommon switches and digital transmission paths to establishconnections for various services such as telephony, datatelex, and facsimile. See also B channel and D channel.

ISG Motorola Information Systems group (formerly CODEX).

ISO International Organisation for Standardization. ISO is aworld-wide federation of national standards bodies from some130 countries, one from each country.

ISQL An Interactive Structured Query Language client applicationfor the database server. See also IDS.

ISS Integrated Support Server. The ISS resides on a Sun Netrat 1125 and performs the CGF, DNS, NTP, and NFS functionsfor the GSN.

ISUP ISDN User Part. An upper-layer application supported bysignalling system No. 7 for connection set up and tear down.

IT Inactivity Test (Part of SCCP network connectivity).


02 May 2003


68P02901W01-M 7�35

ITC Information Transfer Capability. A GSM Bearer CapabilityElement which is provided on the Dm channel to supportTerminal adaptation function to Interworking controlprocedures.

ITU International Telecommunication Union. An intergovernmentalorganization through which public and private organizationsdevelop telecommunications. It is responsible for adoptinginternational treaties, regulations and standards governingtelecommunications.

ITU-T International Telecommunication Union - TelecommunicationsStandardization Sector. The standardization functions wereformerly performed by CCITT, a group within the ITU.

IWF InterWorking Function. A network functional entity whichprovides network interworking, service interworking,supplementary service interworking or signalling interworking.It may be a part of one or more logical or physical entities in aGSM PLMN.

IWMSC InterWorking MSC. MSC that is used to deliver data to/fromSGSN.

IWU InterWorking Unit. Unit where the digital to analogue (andvisa versa) conversion takes place within the digital GSMnetwork.

k - KW

k kilo (103).

k Windows size.

K Constraint length of the convolutional code.

KAIO Kernel Asynchronous Input/Output. Part of the OMC-Rrelational 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 theoperation of encipherment and decipherment.

kHz kilo-Hertz.

Ki Individual subscriber authentication Key. Part of theauthentication process of the AUC.

KIO A class of processor.

KSW Kiloport SWitch board. TDM timeslot interchanger to connectcalls. Part of the BSS.

KSWX KSW Expander half size board. Fibre optic distribution ofTDM bus. Part of the BSS.

kW kilo-Watt.

L1 - LV

L1 Layer 1 (of a communications protocol).



02 May 20037�36


68P02901W01-M

L2ML Layer 2 Management Link. L2ML is used for transferring layer2 management messages to TRX or BCF. One link per TRXand BCF.

L2R Layer 2 Relay function. A function of an MS and IWF thatadapts a user�s known layer 2 protocol LAPB onto RLP fortransmission between the MT and IWF.

L2R BOP L2R Bit Orientated Protocol.

L2R COP L2R Character Orientated Protocol.


LA Location Area. An area in which an MS may move freelywithout updating the location register. An LA may compriseone or several base station areas.

LAC Location Area Code. The LAC is part of the LAI. It is anoperator defined code identifying the location area.

LAI Location Area Identity. The information indicating the locationarea in which a cell is located. The LAI data on the SIM iscontinuously updated to reflect the current location of thesubscriber.

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 switchedtelecommunications network, but may be connected to one.

LANX LAN Extender half size board. Fibre optic distribution of LANto/from other cabinets. Part of BSS, etc.

LAPB Link Access Protocol Balanced. The balanced-mode,enhanced version of HDLC. Used in X.25 packet-switchingnetworks.

LAPD Link Access Protocol D-channel (Data). A protocol that operatesat the data link layer (layer 2) of the OSI architecture. LAPD isused to convey information between layer 3 entities across theframe relay network. The D-channel carries signallinginformation for circuit switching.

LAPDm Link Access Protocol on the Dm channel. A link accessprocedure (layer 2) on the CCH for the digital mobilecommunications 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 inand out of the BSC. Such links include MTL, XBL, OMF andRSL. See also LCP.


02 May 2003


68P02901W01-M 7�37

LCN Local Communications Network. A communication networkwithin 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 examplesinclude point-to-point connections and networks based onstar and bus topologies.

LCP Link Control Processor. An LCP is a GPROC or PCMCIAboard device which supplies the LCF. Once the LCF has beenequipped, 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 whencurrent passes through it. Depending on the material used thecolour can be visible or infrared.

LF Line Feed. A code that moves the cursor on a display screendown one line. In the ASCII character set, a line feed has adecimal value of 10. On printers, a line feed advances thepaper one line.

LI Length Indicator. Delimits LLC PDUs within the RLC datablock, when an LLC PDU boundary occurs in the block.

LI Line Identity. The LI is made up of a number of informationunits: the subscriber�s national ISDN/MSISDN number; thecountry code; optionally, subaddress information. In a fullISDN environment, the line identity includes all of the addressinformation 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 theconnected party.

LLC Lower Layer Compatibility. The LLC can carry informationdefining 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 aLAN has an LMP, which detects faults on the LAN. LANalarms are generated by the GPROC.

LMS Least Mean Squares. Parameters determined by minimizingthe sum of squares of the deviations.

LMSI Local Mobile Station Identity. A unique identity temporarilyallocated to visiting mobile subscribers in order to speed upthe search for subscriber data in the VLR, when the MSRNallocation is done on a per cell basis.

LMT Local Maintenance Terminal. Diagnostic tool, typically an IBMcompatible PC.

LNA Low Noise Amplifier. An amplifier with low noisecharacteristics.

LND Last Number Dialled.

Location area An area in which a mobile station may move freely withoutupdating the location register. A location area may compriseone or several base station areas.


02 May 20037�38


68P02901W01-M

LPC Linear Predictive Coding. A method of digitally encodinganalog signals. It uses a single-level or multi-level samplingsystem in which the value of the signal at each sample time ispredicted to be a linear function of the past values of thequantified signal.

LPLMN Local PLMN.

LR Location Register. The GSM functional unit where MSlocation information is stored. The HLR and VLR are locationregisters.

LSSU Link Stations Signalling Unit (Part of MTP transport system).

LSTR Listener Side Tone Rating. A rating, expressed in dB, basedon how a listener will perceive the background noise pickedup by the microphone.

LTA Long Term Average. The value required in a BTS�s GCLKfrequency 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 MSwhen it detects that it has entered a new location area.

LV Length and Value.

M - MUX

M Mandatory.

M Mega (106).

M-Cell Motorola Cell.

M&TS Maintenance and TroubleShooting. Functional area ofNetwork Management software which (1) collects anddisplays alarms, (2) collects and displays Software/Hardwareerrors, and (3) activates test diagnostics at the NEs (OMC).

MA Mobile Allocation. The radio frequency channels allocated toan MS for use in its frequency hopping sequence.

MAC Medium Access Control. MAC includes the functions relatedto the management of the common transmission resources.These include the packet data physical channels and theirradio link connections. Two Medium Access Control modesare supported in GSR5, dynamic allocation and fixedallocation.

MACN Mobile Allocation Channel Number. See also MA.

Macrocell A cell in which the base station antenna is generally mountedaway from buildings or above rooftop level.

MAF Mobile Additional Function.

MAH Mobile Access Hunting supplementary service. An automaticservice which searches for the first available mobile user outof a defined group.

MAI Mobile Allocation Index.


02 May 2003


68P02901W01-M 7�39

MAIDT Mean Accumulated Intrinsic Down Time.

MAINT MAINTenance.

MAIO Mobile Allocation Index Offset. The offset of the mobilehopping sequence from the reference hopping sequence ofthe cell.

MAP Mobile Application Part (part of SS7 standard). Theinter-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 theinter-GPROC communications channel in a BSC. Each cardcage in a BSC needs at least one GPROC designated as anMCAP Server.

MCC Mobile Country Code. The first three digits of the IMSI, usedto identify the country.

MCDF Motorola Customer Data Format used by DataGen for simpledata entry and retrieval.

MCI Malicious Call Identification supplementary service. Thisfeature is supported by a malicious call trace function byprinting the report at the terminating MSC when the mobilesubscriber initiates a malicious call trace request.

MCSC Motorola Customer Support Centre.

MCU Main Control Unit for M-Cell2/6. Also referred to as the MicroControl 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). Alsoreferred to as the Micro Control Unit in software.

MCUm The software subtype representation of the Field ReplaceableUnit (FRU) for the MCU-m.

MD Mediation Device. The MD (which handles the Q3 interface)allows the OSI Processor to communicate between theNetwork Management Centre (NMC) and OMC-R for networkconfiguration, 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 ofGSM PLMN and/or DCS telecommunication services, butwhich does not contain subscriber related information.Services may be accessed while the equipment, capable ofsurface movement within the GSM system area, is in motionor during halts at unspecified points.

MEF Maintenance Entity Function (GSM Rec. 12.00). A functionwhich possesses the capability to detect elementary anomaliesand convey them to the supervision process.

MF MultiFrame. In PCM systems, a set of consecutive frames inwhich the position of each frame can be identified byreference to a multiframe alignment signal.


02 May 20037�40


68P02901W01-M

MF Multi-Frequency (tone signalling type). See DTMF.

MF MultiFunction block.

MGMT, mgmt Management.

MGR Manager.

MHS Message Handling System. The family of services andprotocols that provides the functions for global electronic-mailtransfer among local mail systems.

MHS Mobile Handling Service.

MHz Mega-Hertz (106).

MI Maintenance Information.

MIB Management Information Base. A Motorola OMC-Rdatabase. There is a CM MIB and an EM MIB.

MIC Mobile Interface Controller.

Microcell A cell in which the base station antenna is generally mountedbelow rooftop level. Radio wave propagation is by diffractionand scattering around buildings, the main propagation iswithin street canyons.

min minute(s).

ms micro-second (10-6).

mBCU Micro Base Control Unit. The mBCU is the Macro/Microcellimplementation of a BTS site controller.

MIT Management Information Tree. A file on the MotorolaOMC-R. The MIT file effectively monitors data on everydevice and every parameter of each device that is in thecurrent versions of software on the OMC-R. The data isstored as a text file on the OMC-R. The MIT file also containsthe 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, IDconfidentiality, paging, handover, etc.

MME Mobile Management Entity.

MMF Middle Man Funnel process.

MMI Man Machine Interface. The method by which the userinterfaces with the software to request a function or changeparameters. The MMI may run on a terminal at the OMC, oran LMT. The MMI is used to display alarm reports, retrievedevice status, take modules out of service and put modulesinto service.

MMI client A machine configured to use the OMC-R software from anMMI server.

MMI processor MMI client/MMI server.

MMI server A computer which has its own local copy of the OMC-Rsoftware. It can run the OMC-R software for MMI clients tomount.

MML Man Machine Language. The tool of MMI.

MMS Multiple Serial Interface Link. (see also 2Mbit/s link)


02 May 2003


68P02901W01-M 7�41

MNC Mobile Network Code. The fourth, fifth and optionally sixthdigits of the IMSI, used to identify the network.

MNT MaiNTenance.

MO Mobile Originated.

MO/PP Mobile Originated Point-to-Point messages. Transmission of aSMS from a mobile to a message handling system. Themaximum length of the message is 160 characters. Themessage can be sent whether or not the MS is engaged in acall.

MOMAP Motorola OMAP.

MoU Memorandum of Understanding. Commercial term. An MoUusually sets out the broad parameters of an understanding aswell as the general responsibilities and obligations of eachparty in a proposed venture. It has little legal significanceexcept to indicate the parties� commitments and acts as anaid to interpreting the parties� intentions. There are varioustypes of MOUs: compliance MOUs help ensure that allMotorola units comply with applicable laws and regulations;intellectual property MOUs deal with copyright, trademark,and patent rights; and business arrangement MOUs relate tothe 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. MPTYprovides a mobile subscriber with the ability to have amulti-connection call, i.e. a simultaneous communication withmore than one party.

MPX MultiPleXed.

MRC Micro Radio Control Unit.

MRN Mobile Roaming Number.

MRP Mouth Reference Point. Facility for assessing handset andheadset acoustic responses.

MS Mobile Station. The GSM subscriber unit. A subscriberhandset, either mobile or portable, or other subscriberequipment, such as facsimile machines, etc.

MSC Mobile-services Switching Centre, Mobile Switching Centre.The MSC handles the call set up procedures and controls thelocation registration and handover procedures for all exceptinter-BTS, inter-cell and intra-cell handovers. MSC controlledinter-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 two2 Mbit/s digital links. See 2 Mbit/s link and DS-2. Part of BSS.

MSIN Mobile Station Identification Number. The part of the IMSIidentifying the mobile station within its home network.


02 May 20037�42


68P02901W01-M

MSISDN Mobile Station International ISDN Number. Published mobilenumber (see also IMSI). Uniquely defines the mobile stationas an ISDN terminal. It consists of three parts: the CountryCode (CC), the National Destination Code (NDC) and theSubscriber Number (SN).

MSRN Mobile Station Roaming Number. A number assigned by theMSC to service and track a visiting subscriber.

MSU Message Signal Unit (Part of MTP transport system). Asignal unit containing a service information octet and asignalling information field which is retransmitted by thesignalling link control, if it is received in error.

MT Mobile Terminated. Describes a call or short messagedestined for an MS.

MT (0, 1, 2) Mobile Termination. The part of the MS which terminates theradio transmission to and from the network and adaptsterminal equipment (TE) capabilities to those of the radiotransmission. MT0 is mobile termination with no support forterminal, MT1 is mobile termination with support for an S-typeinterface and MT2 is mobile termination with support for anR-type interface.

MTBF Mean Time Between Failures. An indicator of expectedsystem reliability calculated on a statistical basis from theknown 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 PCMtimeslot that is used to convey the SS7 signalling informationon the A interface between the MSC and the BSC.

MTM Mobile-To-Mobile (call).

MTP Message Transfer Part. The part of a common-channelsignaling system that transfers signal messages andperforms associated functions, such as error control andsignaling link security.

MT/PP Mobile Terminated Point-to-Point messages. Transmission ofa short message from a message handling system to amobile. The maximum length of the message is 160characters. The message can be received whether or not theMS is engaged in a call.

MTTR Mean Time To Repair. The total corrective maintenance timedivided by the total number of corrective maintenance actionsduring a given period of time.

Multiframe Two types of multiframe are defined in the system: a26-frame multiframe with a period of 120 ms and a 51-framemultiframe with a period of 3060/13 ms.

MU Mark Up.

MUMS Multi User Mobile Station.

MUX Multiplexer. A device that combines multiple inputs into anaggregate signal to be transported via a single transmissionchannel.


02 May 2003


68P02901W01-M 7�43

NACK - nW

NACK, Nack No Acknowledgement

N/W Network.

NB Normal Burst (see Normal burst).

NBIN A parameter in the frequency hopping sequence generationalgorithm.

NCC Network Colour Code. The NCC and the BCC are part of theBSIC. The NCC comprises three bits in the range 000 to 111.It is the same as the PLMN Colour Code. See also NCC andBSIC.

NCELL Neighbouring (of current serving) Cell.

NCH Notification CHannel. Part of the downlink element of theCCCH reserved for voice group and/or voice broad-cast callsand notification messages.

ND No Duplicates. A database column attribute meaning thecolumn contains unique values (used only with indexedcolumns).

NDC National Destination Code. Part of the MSISDN. An NDC isallocated to each GSM PLMN.

NDUB Network Determined User Busy. An NDUB condition occurswhen a call is about to be offered and the maximum numberof 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 oftelecommunications equipment that provides support orservices to the user.

NEF Network Element Function block. A functional block thatcommunicates with a TMN for the purpose of beingmonitored, or controlled, or both.

NET Norme Européennes de Telecommunications.

NetPlan An RF planning tool, NetPlan can import data from the OMCand use it to carry out a network frequency replan.

Network Layer See OSI RM. The Network Layer responds to servicerequests from the Transport Layer and issues servicerequests to the Data Link Layer. It provides the functionaland procedural means of transferring variable length datasequences from a source to a destination via one or morenetworks while maintaining the quality of service requested bythe Transport Layer. The Network Layer performs networkrouting, flow control, segmentation/desegmentation, and errorcontrol functions.

NF Network Function.

NFS Network File System. A file system that is distributed over acomputer network. Also, a file system, on a single computer,that contains the low-level networking files for an entirenetwork.


02 May 20037�44


68P02901W01-M

NHA Network Health Analyst. The NHA is an optional feature. Itdetects problems by monitoring network statistics and eventsvia the OMC-R. The NHA analyses the event history,statistics and network configuration data to try to determinethe cause of the detected problems.

NIC Network Interface Card. A network interface device in theform of a circuit card that provides network access.

NIC Network Independent Clocking.

NIS Network Information Service. It allows centralised control ofnetwork information for example hostnames, IP addressesand passwords.

N-ISDN Narrowband Integrated Services Digital Network: Servicesinclude basic rate interface (2B+D or BRI) and primary rateinterface (30B+D - Europe and 23B+D - North America orPRI). Supports narrowband speeds at/or below 1.5 Mbps.

NIU Network Interface Unit. A device that performs interfacefunctions, such as code conversion, protocol conversion, andbuffering, 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 whichcontrol, monitor and record the use and the performance ofresources of a telecommunications network in order toprovide telecommunication services to customers/users at acertain level of quality.

NMASE Network Management Application Service Element.

NMC Network Management Centre. The NMC node of the GSMTMN provides global and centralised GSM PLMN monitoringand control, by being at the top of the TMN hierarchy andlinked to subordinate OMC nodes.

NMSI National Mobile Station Identification number, or, NationalMobile Subscriber Identity. The NMSI consists of the MNCand the MSIN.

NMT Nordic Mobile Telephone system. NMT produced the world�sfirst automatic international mobile telephone system.

NN No Nulls. A database column attribute meaning the columnmust 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 byone significant condition and zeros are represented byanother, with no neutral or rest condition.

NSAP Network Service Access Point. An NSAP is a registrationmade by an application which specifies its desired listeningcriteria. The registration is limited to a particular CPU and portnumber. Criteria can include: DNICs, national numbers,subaddress ranges, protocol-ids, and extended addresses.


02 May 2003


68P02901W01-M 7�45

NSP Network Service Provider. A national or regional companythat owns or maintains a portion of the network and resellsconnectivity.

NSS Network Status Summary. A feature of the OMC-R MMI,which provides different network maps giving visual indicationof the network configuration and performance, and how thedifferent network management functions are implemented bythe OMC-R.

NST Network Service Test(er). A PCU process that periodicallytests all alive NS-VCs on a PICP board.

NS-VC Network Service - Virtual Circuit.

NT Network Termination. Network equipment that providesfunctions necessary for network operation of ISDN accessprotocols.

NT Non Transparent.

NTAAB NTRAC Type Approvals Advisory Board. Committee engagedin harmonisation type approval of telecom terminals inEurope.

NTP Network Time Protocol. A protocol built on top of TCP/IP thatassures accurate local timekeeping with reference to radio,atomic or other clocks located on the Internet. This protocol iscapable of synchronizing distributed clocks withinmilliseconds over long time periods.

Numbers # - The symbol used for number.

2 Mbit/s link - As used in this manual set, the term applies tothe European 4-wire 2.048 Mbit/s digital line or link which cancarry 30 A-law PCM channels or 120 16 kbit/s GSMchannels.

4GL - 4th Generation Language. Closer to human languagesthan typical high-level programming languages. most 4GLsare 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 accessmemory which is made into non-volatile storage either byhaving a battery permanently connected, or, by saving itscontents to EEPROM before turning the power off andreloading it when power is restored.

nW Nano-Watt (10-9).

O - Overlap

O Optional.

OA Outgoing Access supplementary service. An arrangementwhich allows a member of a CUG to place calls outside theCUG.

OA&M Operation, Administration, & Management.

OAMP Operation, Administration, Maintenance, and Provisioning.


02 May 20037�46


68P02901W01-M

O&M Operations and Maintenance.

OASCU Off-Air-Call-Set-Up. The procedure in which atelecommunication connection is being established whilst theRF 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 fromplacing calls to other members of that group.

OCXO Oven Controlled Crystal Oscillator. High stability clock sourceused 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 becleared by the OMC-R operator after the fault condition thatcaused the alarm is resolved. See also FMIC andIntermittent.

OLM Off_Line MIB. A Motorola DataGen database, used to modifyand carry out Radio Frequency planning on multiple BSSbinary files.

OLR Overall Loudness Rating.

OMAP Operations and Maintenance Application Part (part of SS7standard) (was OAMP).

OMC Operations and Maintenance Centre. The OMC node of theGSM TMN provides dynamic O&M monitoring and control ofthe PLMN nodes operating in the geographical areacontrolled 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 providescommunication between an OMC-R and a BSC or RXCDRfor 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 stateindicates the physical device is out of service. This state isreserved for physical communication links. Also, identifies atelephony state. The OOS state is used by the BTS devicesoftware to indicate that the BTS is completely out of service.

OPC Originating Point Code. A part of the label in a signallingmessage that uniquely identifies, in a signalling network, the(signalling) origination point of the message.

ORAC Olympus Radio Architecture Chipset.


02 May 2003


68P02901W01-M 7�47

OS Operating System. The fundamental program running on acomputer which controls all operations.

OSI Open Systems Interconnection. The logical structure forcommunications networks standardized by the ISO. Thestandard enables any OSI-compliant system to communicateand exchange information with any other OSI-compliantsystem.

OSI RM OSI Reference Model. An abstract description of the digitalcommunications between application processes running indistinct systems. The model employs a hierarchical structureof seven layers. Each layer performs value-added service atthe request of the adjacent higher layer and, in turn, requestsmore 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 usedfor the Motorola OMC-R MMI.

OSS Operator Services System.

Overlap Overlap sending means that digits are sent from one systemto another as soon as they are received by the sendingsystem. A system using ~ will not wait until it has received alldigits of a call before it starts to send the digits to the nextsystem. This is the opposite of en bloc sending where alldigits for a given call are sent at one time. See en bloc.

PA - PXPDN

PA Power Amplifier.

PAB Power Alarm Board. Part of the BSS.

PABX Private Automatic Branch eXchange. A private automatictelephone exchange that allows calls within the exchange andalso calls to and from the public telephone network.

Packet A sequence of binary digits, including data and controlsignals, that is transmitted and switched as a compositewhole.

Packet Switching The process of routing and transferring data by means ofaddressed packets so that a channel is occupied during thetransmission of the packet only, and upon completion of thetransmission the channel is made available for the transfer ofother traffic.

PAD Packet Assembler/Disassembler facility. A hardware devicethat allows a data terminal that is not set up for packetswitching to use a packet switching network. It assemblesdata into packets for transmission, and disassembles thepackets on arrival.


02 May 20037�48


68P02901W01-M

Paging The procedure by which a GSM PLMN fixed infrastructureattempts to reach an MS within its location area, before anyother 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 withonly a manual switchboard; a private automatic exchange(PAX) does not have a switchboard, a private automaticbranch exchange (PABX) may or may not have aswitchboard.

PC Personal Computer. A general-purpose single-usermicrocomputer designed to be operated by one person at atime.

pCA PCU Central Authority. One pCA software process is locatedat every PCU. The CA is in control of the PCU. It is residenton the master DPROC (MPROC) only, and maintains a list ofthe status of every device and every software process at thesite.

PCH Paging CHannel. A common access RF channel providingpoint-to-multipoint unidirectional signaling downlink. Providessimultaneous transmission to all MSs over a wide pagingarea.

PCHN Paging Channel Network.

PCHN Physical Channel. The physical channel is the medium overwhich the information is carried. In the case of GSM radiocommunications this would be the Air Interface. Each RFcarrier consists of eight physical channels (or timeslots) usedfor MS communications. In the case of a terrestrial interfacethe physical channel would be cable. See also PhysicalLayer.

PCI Packet Control Interface.

PCI Peripheral Component Interconnect. A standard forconnecting peripherals to a personal computer, PCI is a 64-bitbus, though it is usually implemented as a 32-bit bus.

PCM Pulse Code Modulation. Modulation in which a signal issampled, and the magnitude (with respect to a fixedreference) of each sample is quantized and converted bycoding to a digital signal. Provides undistorted transmission,even in the presence of noise. See also 2 Mbit/s link, which isthe physical bearer of PCM.

pCM PCU Configuration Management. pCM is a GWM process. Itdistributes all database changes performed at the BSC to thePCU boards.

PCN Personal Communications Network. Any network supportingPCS, but in particular DCS1800.

PCR Preventative Cyclic Retransmission. A form of errorcorrection suitable for use on links with long transmissiondelays, such as satellite links.


02 May 2003


68P02901W01-M 7�49

PCS The U.S. Federal Communications Commission (FCC) termused to describe a set of digital cellular technologies beingdeployed in the U.S. PCS works over GSM, CDMA (alsocalled IS-95), and North American TDMA (also called IS-136)air interfaces.

PCS System Personal Communications Services System. In PCS, acollection of facilities that provides some combination ofpersonal mobility, terminal mobility, and service profilemanagement. Note: As used here, �facilities� includeshardware, software, and network components such astransmission facilities, switching facilities, signalling facilities,and databases.

PCS1900 A cellular phone network using the higher frequency rangeallocated in countries such as the USA. It operates on thefrequency range, 1850 - 1910 MHz (receive) and1930 - 1990 MHz (transmit).

PCU Packet Control Unit. A BSS component that provides GPRSwith packet scheduling over the air interface with the MS, andpacket segmentization and packetization across the FrameRelay 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 packetheader 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 ofPBCCH and PDTCH logical channels.

PDF Power Distribution Frame (MSC/LR).

PDN Public Data Network. A network established and operated bya telecommunications administration, or a recognized privateoperating agency, for the specific purpose of providing datatransmission services for the public.

PDTCH Packet Data Traffic Channels

PDU Power Distribution Unit. The PDU consists consisting of theAlarm 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 ofdata, headers, and trailers at any layer in a network.

PEDC Pan-European Digital Cellular network. The GSM network inEurope.

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

Pegging Modifying a statistical value.

pFCP PCU Fault Collection Process. See pFTP.


02 May 20037�50


68P02901W01-M

pFTP PCU Fault Transaction Process. The pFTP resides on thePSP as part of the GWM Functional Unit process. All alarmsat the PCU are reported to pFTP. All DPROCs and theMPROC have a local pFCP to handle Software FaultManagement indications (SWFMs). The pFTP forwardsalarms to the Agent at the BSC and generates messages topCA for device transitions as needed, based on faultsreported.

PGSM Primary GSM. PGSM operates on the standard GSMfrequency range, 890 - 915 MHz (receive) and 935 - 960 MHz(transmit).

PH Packet Handler. A packet handler assembles anddisassembles packets.

PH PHysical (layer). See Physical Layer.

PHI Packet Handler Interface.

Physical Layer See OSI-RM. The Physical Layer is the lowest of sevenhierarchical layers. It performs services requested by theData Link Layer. The major functions and services of thelayer are: (a) establishment and termination of a connectionto a communications medium; (b) participation in the processof sharing communication resources among multiple users;and, (c) conversion between the representation of digital datain user equipment and the corresponding signals transmittedover a communications channel.

PI Presentation Indicator. The PI forms part of the calling nameinformation. Depending on database settings, the PI mayprevent the called party from seeing the identity of the callingparty.

Picocell A cell site where the base station antenna is mounted within abuilding.

PICP Packet Interface Control Processor. A PCU hardwarecomponent, the PICP is a DPROC board used for networkinterfacing functions such as SGSN and BSC.

PICS Protocol Implementation Conformance Statement. Astatement made by the supplier of an implementation orsystem claimed to conform to a given specification, statingwhich capabilities have been implemented.

PID Process IDentifier/Process ID.

PIM PCM Interface Module (MSC).

PIN Personal Identification Number. A password, typically fourdigits entered through a telephone keypad.

PIN Problem Identification Number.

PIX Parallel Interface Extender half size board. Customer alarminterface, part of the BSS. The PIX board provides a meansof wiring alarms external to the BSS, BSC, or BTS into thebase equipment.

PIXT or PIXIT Protocol Implementation eXtra information for Testing. Astatement made by a supplier or implementor of animplementation under test (IUT) which contains informationabout the IUT and its testing environment which will enable atest laboratory to run an appropriate test suite against theIUT.


02 May 2003


68P02901W01-M 7�51

PK Primary Key. A database column attribute, the primary key isa 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 theBTS). PLL is a mechanism whereby timing information istransferred within a data stream and the receiver derives thesignal element timing by locking its local clock source to thereceived timing information.

PLMN Public Land Mobile Network. The mobile communicationsnetwork.

PM Performance Management. An OMC application. PMenables the user to produce reports specific to theperformance of the network.

PMA Prompt Maintenance Alarm. An alarm report level; immediateaction 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 Présentation des Normes Européennes. Presentation rules ofEuropean Standards.

POI Point of Interconnection. A point at which the cellular networkis connected to the PSTN. A cellular system may havemultiple POIs.

POTS Plain Old Telephone Service. Basic telephone service withoutspecial 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 Bridgeboard. The PPB allows an MPROC to be linked to a separatebus. 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 foreach basic service group, is the nominated default CUG to beused when no explicit CUG index is received by the network.

Presentation Layer See OSI RM. The Presentation Layer responds to servicerequests from the Application Layer and issues servicerequests to the Session Layer. It relieves the ApplicationLayer of concern regarding syntactical differences in datarepresentation within the end-user systems.


02 May 20037�52


68P02901W01-M

Primary Cell A cell which is already optimized in the network and has aco-located neighbour whose cell boundary follows theboundary of the said cell. The primary cell has a preferredband equal to the frequency type of the coincident cell.

PRM Packet Resource Manager. The PRM is a PRP process. Itperforms all RLC/MAC functions and realises UL/DL powercontrol 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 packetresources at the PCU and is the processor where all of theradio related processing occurs. GPRS channels are routedto PRPs which perform the RLC/MAC processing, airinterface scheduling, and frame synchronization of thechannels.

Ps Location probability. Location probability is a quality criterionfor cell coverage. Due to shadowing and fading a cell edge isdefined by adding margins so that the minimum servicequality is fulfilled with a certain probability.

PSA Periodic Supervision of Accessibility. PSA is a faultmanagement function. It periodically sends messages toBSSs requesting information on their current state. Thisverifies whether the BSSs are operational or not. If a BSSfails to respond to a PSA request for its status, the OMC-Rwill generate an alarm for that BSS.

PSAP Presentation Services Access Point.

pSAP PCU System Audit Process. pSAP is a GWM process. Itperiodically monitors the soft devices to maintain the reliabilityof the system.

PSM Power Supply Module.

pSM

PCU Switch Manager. The pSM resides on the PSP as partof the GWM Functional Unit process. The pSM maintainsdata 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 Switchingand PDN.

PSTN Public Switched Telephone Network. The domestic land linetelecommunications network. It is usually accessed bytelephones, key telephone systems, private branch exchangetrunks, 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 theHome unit in a currency chosen by the subscriber. The PUCTis stored in the SIM. The value of the PUCT can be set by thesubscriber and may exceed the value published by theHPLMN. The PUCT value does not have any impact on thecharges raised by the HPLMN.


02 May 2003


68P02901W01-M 7�53

PVC Permanent Virtual Circuit. Also, in ATM terminology,Permanent Virtual Connection. A virtual circuit that ispermanently established, saving the time associated withcircuit establishment and tear-down. See also SVC.

PW Pass Word.

PWR Power.

PXPDN Private eXchange Public Data Network. See also PDN.

QA- Quiesent modeQA 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 toTDM switch highway. See MSI.

QIC Quarter Inch Cartridge (Data storage format).

QoS Quality Of Service. An alarm category which indicates that afailure is degrading service.

Queue Data structure in which data or messages are temporarilystored until they are retrieved by a software process. Also aseries of calls waiting for service. See also FIFO.

Quiescent mode IDS intermediate state before shutdown.

R - RXUR Value of reduction of the MS transmitted RF power relative to

the maximum allowed output power of the highest powerclass of MS (A).

RA RAndom mode request information field.

RA250 Rural Area with the MS travelling at 250 kph. Dynamic modelagainst which the performance of a GSM receiver can bemeasured. See also TU3, TU50, HT100 and EQ50.

RAB Random Access Burst. Data sent on the RACH.

RACCH Random Access Control CHannel. A GSM common controlchannel used to originate a call or respond to a page.

RACH Random Access CHannel. The RACH is used by the mobilestation to request access to the network. See also RAB.

Radio Frequency A term applied to the transmission of electromagneticallyradiated information from one point to another, usually usingair or vacuum as the transmission medium. Anelectromagnetic wave frequency intermediate between audiofrequencies and infrared frequencies used in radio andtelevision transmission.

RAM Random Access Memory. A read/write, nonsequential-accessmemory in which information can be stored, retrieved andmodified. This type of memory is generally volatile (i.e., itscontents are lost if power is removed).


02 May 20037�54


68P02901W01-M

RAND RANDom number (used for authentication). The RAND issent by the SGSN to the MS as part of the authenticationprocess.

RAT Radio Access Technology

RATI Receive Antenna Transceiver Interface.

RAx Rate Adaptation.

RBDS Remote BSS Diagnostic System (a discontinued Motoroladiagnostic facility).

RBER Residual Bit Error Ratio. RBER is a ratio of the number of bitsin error to the total number of bits received, within errordetected speech frames defined as good. The measurementperiod over which the calculation is made is 480 ms. Duringthis period, 24 speech frames are decoded and a ratiocalculated. By referring to a lookup table, the ratio is thenconverted to an RBER Quality number between 0 and 7.

RBTS Remote Base Transceiver Station. A BTS that is notco-located with the BSC that controls it.

RCB Radio Control Board. Part of the DRCU.

RCI Radio Channel Identifier. The unique identifier of the radiochannel portion of the circuit path.

RCI Radio Channel Interface. The RCI changes the MS addressused in the RSS (channel number) to the address used inLayer 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 isnow obsolete, see DRCU.

RCVR Receiver.

RDBMS Relational DataBase Management System (INFORMIX). Thedatabase management system for the OMC-R database.

RDI Restricted Digital Information.

RDIS Radio Digital Interface System.

RDM Reference Distribution Module. The RDM provides a stable3MHz reference signal to all transceivers. It is used for carrierand injection frequency synthesis.

RDN Relative Distinguished Name. A series of RDNs form aunique identifier, the distinguished name, for a particularnetwork element.

REC, Rec RECommendation.

Reciprocal neighbour Used to describe adjacent cells; each being designated as aneighbour of the other. Also known as bi�directional andtwo�way neighbour.

Registration The process of a MS registering its location with the MSC inorder to make or receive calls. This occurs whenever the MSfirst activates or moves into a new service area.

REJ REJect(ion).

REL RELease.


02 May 2003


68P02901W01-M 7�55

RELP Residual Excited Linear Predictive. A form of speech coding.RELP coders are usually used to give good quality speech atbit rates in the region of 9.6 kbit/s.

RELP-LTP RELP Long Term Prediction. A name for GSM full rate. SeeFull Rate.

Remotely TunedCombiner

A combiner device which houses two processors (forpaired-redundancy) and several tuneable cavities. See alsoCOMB

resync Resynchronize/resynchronization.

REQ REQuest.

Reuse Pattern The minimum number of cells required in a pattern beforechannel frequencies are reused, to prevent interference.Varies between cell configuration type and channel type. Thepattern shows assignments of adjacent channels to minimizeinterference between cells and sectors within the patternarea.

Revgen A Motorola DataGen utility for producing an MMI script from abinary object database.

RF See Radio Frequency.

RFC, RFCH Radio Frequency Channel. A partition of the system RFspectrum allocation with a defined bandwidth and centrefrequency.

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 commonlyto connect computers onto a local-area networks (LAN),especially Ethernets.

RISC Reduced Instruction Set Computer. A type of microprocessorthat recognizes a relatively limited number of instructiontypes, allowing it to operate at relatively higher speeds.

RL Remote login. RL is a means by which the operator performsconfiguration management, fault management, and someperformance management procedures at the NEs. The RLsoftware manages the X.25 connection for remote login. Thecircuit is made by the OMC-R calling the NE.

RLC Release Complete. An SCCP message type used with RLSDto release a connection.

RLC Radio Link Control. Air interface transmission layer. The RLCfunction processes the transfer of PDUs from the LLC layer.

RLP Radio Link Protocol. An ARQ protocol used to transfer userdata between an MT and IWF. See GSM 04.22.

RLR Receive Loudness Rating. See SLR.


02 May 20037�56


68P02901W01-M

RLSD ReLeaSeD. An SCCP message type used with RLC torelease a connection.

RMS Root Mean Square (value). The most common mathematicalmethod of defining the effective voltage or current of an ACwave. For a sine wave, the rms value is 0.707 times the peakvalue.

RMSU Remote Mobile Switching Unit. An RMSU is a lineconcentrator. It may be inserted between the MSC and someof the BSS sites served by the MSC to reduce the number ofterrestrial signalling and traffic circuits required.

RNTABLE Table of 128 integers in the hopping sequence.

Roaming Situation where mobile station operates in a cellular systemother than the one from which service is subscribed.

ROM Read Only Memory. Computer memory that allows fastaccess to permanently stored data but prevents addition to ormodification of the data. ROM is inherently non-volatilestorage - it retains its contents even when the power isswitched off.

ROSE Remote Operations Service Element. An ASE which carriesa message between devices over an association establishedby ASCE (a CCITT specification for O & M) (OMC).

Roundtrip Time period between transmit and receive instant of atimeslot in the BTS, propagation determined by the responsebehaviour 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 GSMdigital speech coding scheme. GSM uses a simplified RPEcodec, with long-term prediction, operating at 13 kbits/s toprovide toll quality speech.

RPOA Recognised Private Operating Agency. Privatetelecommunications operator recognised by the appropriatetelecommunications authority.

RPR Read Privilege Required. Part of the table structure of theOMC database schema. Access to the column is allowed onlyfor privileged accounts.

RR Radio Resource management. Part of the GSM managementlayer. The functions provided by RR include paging, ciphermode set, frequency redefinition, assignments, handover andmeasurement reports.

RR Receive Ready.

RRSM Radio Resource State Machine. Translates messagesthrough Call Processing (CP). Activates and deactivates radiochannels as controlled by the CRM.

RS232 Recommended Standard 232. The interface between aterminal (DTE) and a modem (DCE) for the transfer of serialdata. Standard serial interface.

RSE Radio System Entity.

RSL Radio Signalling Link. RSL is used for signalling between theBSC and BTSs. The interface uses a 64 kbit/s timeslot with aLAPD protocol.


02 May 2003


68P02901W01-M 7�57

RSLF Radio System Link Function.

RSLP Radio System Link Processor.

RSS Radio SubSystem (replaced by BSS).

RSSI Received Signal Strength Indicator. A parameter returnedfrom a transceiver that gives a measure of the RF signalstrength between the MS and BTS, either uplink or downlink.

RSZI Regional Subscription Zone Identity. The RSZI defines theregions in which roaming is allowed. The elements of theRSZI are:

The Country Code (CC) which identifies the country in whichthe GSM PLMN is located,

The National Destination Code (NDC) which identifies theGSM PLMN in that country,

The Zone Code (ZC) which identifies a regional subscriptionzone as a pattern of allowed and not allowed location areasuniquely within that PLMN.

RTC Remotely Tuneable Channel Combiner. RTCs are used tofine-tune the cavities to the right frequency. A poorly tunedcavity can cause power destined for the antenna to bereversed.

RTE Remote Terminal Emulator.

RTF Radio Transceiver Function. RTF is the function that supportsthe air interface channel and the DRI/Transceiver pair. Whenequipping a DRI at a remote BTS, one or more RTFs must beequipped.

RTF Receive Transmit Functions.

RTS Request to Send. A handshaking signal used withcommunication links, especially RS232 or CCITT Rec. V.24 toindicate (from a transmitter to a receiver) that data is readyfor transmission. See also CTS.

RU Rack Unit.

Run level System processor operating mode.

Rx Receive(r).

RXCDR Remote Transcoder. An RXCDR is used when thetranscoding is performed at a site away from the BSC. Thissite would be at or near the MSC. This enables 4:1multiplexing in which the transcoded data for four logicalchannels is combined onto one 64 kbit/s link, thus reducingthe 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 levelbased on the RSSI. RXLEV is one of the two criteria forevaluating the reception quality (the basis for handover andpower control). See also RXQUAL. The MS reports RXLEVvalues related to the apparent received RF signal strength. Itis necessary for these levels to attain sufficient accuracy forthe correct functioning of the system.

RXLEV-D Received signal level downlink.

RXLEV-U Received signal level uplink.


02 May 20037�58


68P02901W01-M

RXQUAL Received signal quality. An indication of the received signalquality based on the BER. RXQUAL is one of the two criteriafor evaluating the reception quality (the basis for handoverand power control). See also RXLEV. The MS measures thereceived signal quality, which is specified in terms of BERbefore channel decoding averaged over the reporting periodof 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 theremote transcoder modules in a BSSC cabinet at a remotetranscoder site.

S7- SYSGENS7 See SS7.

S/W SoftWare.

SABM Set Asynchronous Balanced Mode. A message whichestablishes the signalling link over the air interface.

SABME SABM Extended.

SACCH Slow Associated Control CHannel. A GSM control channelused by the MS for conveying power control and timingadvance information in the downlink direction, and RSSI andlink 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, SAPsof a layer are defined as gates through which services areoffered 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 detectsfaulty or degrading hardware and software (through the use ofaudit tests) and notifies the Alarms handling software of thecondition.

SAPI Service Access Point Indicator (identifier). The OSI term forthe component of a network address which identifies theindividual application on a host which is sending or receivinga packet.

SAW Surface Acoustic Wave. SAW devices basically consist of aninput transducer to convert electrical signals to tiny acousticwaves, which then travel through the solid propagationmedium to the output transducer where they are reconvertedto electrical signals. SAW band pass filters are used forsorting signals by frequency.

SB Synchronization Burst (see Synchronization burst).


02 May 2003


68P02901W01-M 7�59

SBUS Serial Bus. An SBUS is a logical device made up of thecommunication path between the GPROCs and LANX cardsin a cage.

SC Service Centre (used for Short Message Service).

SC Service Code.

SCCA System Change Control Administration. Software modulewhich 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 channelused to carry information for frame synchronization of MSsand identification of base stations.

SCI Status Control Interface. A slave to the Status ControlManager.

SCIP Serial Communication Interface Processor.

SCM Status Control Manager. Accepts messages from otherprocessors within the switch requesting status displays in theform of one or more lights on a hardware panel. The SCMmaps the status display requests into specific commands tothe status control interface processor to turn on and/or turnoff lights.

SCN Sub-Channel Number. One of the parameters defining aparticular physical channel in a BS.

SCP Service Control Point (an intelligent network entity).

SCSI Small Computer Systems Interface. A processor-independentstandard for system-level interfacing between a computer andintelligent devices including hard disks, floppy disks,CD-ROM, printers, scanners, and many more. SCSI-1 canconnect up to seven devices to a single SCSI adaptor (orhost adaptor) on the computer�s bus.

SCU Slim Channel Unit.

SCU900 Slim Channel Unit for GSM900.

SDCCH Stand-alone Dedicated Control CHannel. A GSM controlchannel where the majority of call setup occurs. Used forMS to BTS communications before MS assigned to TCH. ASDCCH is used by a single MS for call setup, authentication,location updating and SMS point to point.

SDL Specification Description Language. A method for visuallydepicting the functionality of call processing, operations andmaintenance software.

SDM Sub-rate Data Multiplexor

SDT SDL Development Tool. A software tool to model and validatereal-time, state-based product software designs.

SDU Service Data Unit. In layered systems, a set of data that issent by a user of the services of a given layer, and istransmitted to a peer service user semantically unchanged.


02 May 20037�60


68P02901W01-M

SDR Special Drawing Rights. The SDR is the InternationalMonetary Fund unit of account. It also serves as a basis forthe unit of account for a number of other internationalorganizations 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 aco-located neighbour whose cell boundary follows theboundary of the said cell. The secondary cell has a preferredband the same as that of its own frequency type.

SEF Support Entity Function. SEFs are functions not directlyinvolved in the telecommunication process. They include faultlocalisation, protection switching, etc. (GSM Rec.12.00).

Session Layer See OSI RM. The Session Layer responds to servicerequests from the Presentation Layer and issues servicerequests to the Transport Layer. It provides the mechanismfor managing the dialogue between end-user applicationprocesses. It provides for either duplex or half-duplexoperation and establishes checkpointing, adjournment,termination, and restart procedures.

SFH Synthesizer Frequency Hopping. The principle of SFH is thatevery mobile transmits its time slots according to a sequenceof frequencies that it derives from an algorithm. Thefrequency hopping occurs between time slots and, therefore,a mobile station transmits (or receives) on a fixed frequencyduring one time slot. It must then hop before the time slot onthe next TDMA frame. Due to the time needed for monitoringother base stations the time allowed for hopping isapproximately 1 ms, according to the receiverimplementation. The receive and transmit frequencies arealways duplex frequencies.

SGSN Serving GPRS Support Node. The SGSN provides thecontrol, transmission, OAMP, and charging functions. It keepstrack of the individual MS locations, and performs securityfunctions and access control. The SGSN is connected to theBSS via a Frame Relay network.

SI Screening Indicator. The supplementary service (SS)screening indicator is sent by the MS at the beginning of theradio connection to allow the network to assess thecapabilities of the MS and hence determine either whether aparticular network initiated SS operation may be invoked orwhich version of a network initiated SS operation should beinvoked. The SS screening indicator is only relevant tonetwork initiated SS operation and is valid for the duration ofa radio connection.

SI Service Interworking. Part of the IWF.

SI Supplementary Information.

SIA Supplementary Information A.


02 May 2003


68P02901W01-M 7�61

SID Silence Descriptor. The transmission of comfort noiseinformation to the RX side is achieved by means of a SIDframe. A SID frame is transmitted at the end of speech burstsand serves as an end of speech marker for the RX side. Inorder to update the comfort noise characteristics at the RXside, SID frames are transmitted at regular intervals alsoduring speech pauses. This also serves the purpose ofimproving the measurement of the radio link quality by theradio subsystem (RSS).

SIF Signal Information Field. The bits of a message signal unitthat carry information for a certain user transaction; the SIFalways contains a label.

Signalling System No.7 See SS7.

SIM Subscriber Identity Module. Removable module which isinserted into a mobile equipment; it is considered as part ofthe MS. It contains security related information (IMSI, Ki,PIN), other subscriber related information and the algorithmsA3 and A8.

SIMM Single Inline Memory module.

SIMM System Integrated Memory Module. A small plug-in circuitboard providing additional RAM for a computer.

SIO Service Information Octet. Eight bits contained in a messagesignal unit, comprising the service indicator and sub-servicefield. A value in the SIF of an SS7 signalling messagespecifying the User Part type.

SITE BSC, BTS or collocated BSC-BTS site.

SIX Serial Interface eXtender. Converts interface levels to TTLlevels. Used to extend 2 serial ports from GPROC to externaldevices (RS232, RS422, and fibre optics).

SK Secondary Key. A database column attribute, the secondarykey indicates an additional index and/or usage as acomposite key.

SL See Session Layer.

SL Signalling Link. The signalling links between the variousnetwork 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 SCIPand peripheral equipment. The information on the link is sentserially in a bit-synchronous format.

SLR Send Loudness Rating. The SLR, in the mobile to landdirection, and the Receive Loudness Rating (RLR) in the landto mobile direction, determine the audio signal levels for thecustomers speech. The loudness ratings are calculated fromthe send and receive sensitivity masks or frequencyresponses.

SLTA Signalling Link Test Acknowledge. Message sent from theMSC to the BSC in response to an SLTM.


02 May 20037�62


68P02901W01-M

SLTM Signalling Link Test Message. During the process of bringingan MTL link into service, the BSC sends an SLTM messageto the MSC. The MSC responds with an SLTA message.

SM Switch Manager. The function of the SM is to connect a MSterrestrial trunk from the MSC (designated by the MSC), tothe radio channel given to a MS by the cell resource managerin the BSS software.

SM Summing Manager.

SMAE System Management Application Entity (CCITT Q795, ISO9596). OSI terminology for a software ManagementInformation 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 receiveShort Messages. The SME may be located in a fixednetwork, an MS, or a SC. See also SMS.

SMG Special Mobile Group. To avoid confusion between the GSMsystem and the GSM committee with its wider responsibilities,the committee was renamed SMG in 1992.

SMP Motorola Software Maintenance Program. A Motorolaprogram designed to ensure the highest quality of softwarewith the highest level of support.

SMS Short Message Service. SMS is a globally accepted wirelessservice that enables the transmission of alphanumericmessages between mobile subscribers and external systemssuch as electronic mail, paging, and voice-mail systems. Ittransfers the short messages, up to 160 characters, betweenSmts and MSs via an SMS-SC. See also SMS-SC, SMS/PPand Smt.

SMSCB Short Message Service Cell Broadcast. SMSCB is a servicein which short messages may be broadcast from a PLMN toMSs. SMSCB messages come from different sources (e.g.traffic reports, weather reports). Messages are notacknowledged by the MS. Reception of SMSCB messages bythe MS is only possible in idle mode. The geographical areaover which each message is transmitted is selected by thePLMN operator, by agreement with the provider of theinformation.

SMS-SC Short Message Service - Service Centre. SMS-SC is aninterworking unit between stationary networks and the GSMNetwork. It acts as a store and forward centre for shortmessages. See also SMS, SMS/PP and Smt.

SMS/PP Short Message Service/Point-to-Point. Two differentpoint-to-point services have been defined: Mobile Originated(MO) and Mobile Terminated (MT). A short message alwaysoriginates or terminates in the GSM network. This means thatshort messages can never be sent between two users bothlocated in stationary networks. See also SMS, SMS-SC andSmt.


02 May 2003


68P02901W01-M 7�63

Smt Short message terminal. See also SMS, SMS-SC andSMS/PP. There are different types of Smt interfaces, onebeing the Computer Access Interface which provides servicesfor external computers communicating with SMS-SCs throughthe Computer Access Protocol.

SN Subscriber Number.

SND SeND.

SNDR SeNDeR.

SNR Serial NumbeR.

SOA Suppress Outgoing Access (CUG SS). An arrangementwhich prevents a member of a CUG placing calls outside theCUG.

Software Instance A complete set of software and firmware objects including thedatabase object.

SP Service Provider. The organisation through which thesubscriber obtains GSM telecommunications services. Thismay be a network operator or possibly a separate body.

SP Signalling Point. A signalling point is a node within a SS7network.

SP Special Product.

SP SPare.

SPARC Scalable Processor ArChitecture. a 32- and 64-bitmicroprocessor architecture from Sun Microsystems that isbased on the Reduced Instruction Set Computer (RISC).SPARC has become a widely-used architecture for hardwareused with UNIX-based operating systems.

SPC Signalling Point Code.

SPC Suppress Preferential CUG. Prohibits the use of thepreferential 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 forrelational database management systems as adopted by theAmerican National Standards Institute (ANSI X3.135-1989)and the International Standards Organization (ISO9075-1989).

SRD Service Request Distributor.

SRES Signed RESponse (authentication). The SRES is calculatedby the MS, using the RAND, and sent to the SGSN toauthenticate the MS.

SS Supplementary Service. A modification of, or a supplementto, a basic telecommunication service.

SS System Simulator.


02 May 20037�64


68P02901W01-M

SS7 ITU-TSS Common Channel Signalling System No. 7. Alsoknown as C7, S7 or SS#7. The standard defines theprocedures and protocol by which network elements in thePSTN exchange information over a digital signalling networkto effect wireless (cellular) and wireline call setup, routing andcontrol.

SSA SubSystem-Allowed. SSA is used for SCCP subsystemmanagement. An SSA message is sent to concerneddestinations to inform those destinations that a subsystemwhich was formerly prohibited is now allowed. (see ITU-TRecommendation Q.712 para 1.15).

SSAP Site System Audits Processor.

SSC Supplementary Service Control string. When a subscriberselects a supplementary service control from the menu in aGSM network, the mobile station invokes the SSC by sendingthe network the appropriate functional signalling message.

SSF Subservice Field. The level 3 field containing the networkindicator and two spare bits.

SSM Signalling State Machine.

SSN SubSystem Number. In SS7, each signalling point (SP) maycontain a number of subsystems. Each subsystem has aunique ID, the SSN (e.g. 149 for SGSN and 6 for HLR).

SSP Service Switching Point. Intelligent Network Term for theClass 4/5 Switch. The SSP has an open interface to the INfor switching signalling, control and handoff.

SSP Subsystem-prohibited. SSP is used for SCCP subsystemmanagement. An SSP message is sent to concerneddestinations to inform SCCP Management at thosedestinations of the failure of a subsystem.

SSS Switching SubSystem. The SSC comprises the MSC and theLRs.

STAN Statistical ANalysis (processor).

STAT STATistics.

stats Statistics.

STC System Timing Controller. The STC provides the timingfunctions for the GPROC.

STMR Side Tone Masking rating. A rating, expressed in dB, basedon 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 telephonenetwork that routes messages between exchanges andbetween exchanges and databases that hold subscriber androuting information.

SU Signal Unit. A group of bits forming a separately transferableentity used to convey information on a signalling link.

SunOS Sun Microsystems UNIX Operating System. SunOS wasrenamed Solaris.

Superframe 51 traffic/associated control multiframes or 26broadcast/common control multiframes (period 6.12s).


02 May 2003


68P02901W01-M 7�65

Super user User account that can access all files, regardless ofprotection settings, and control all user accounts.

SURF Sectorized Universal Receiver Front-end (Used inHorizonmacro).

SVC Switch Virtual Circuit. A temporary virtual circuit that is set upand used only as long as data is being transmitted. Once thecommunication between the two hosts is complete, the SVCdisappears. See also PVC.

SVM SerVice Manager. The SVM provides overall managementauthority for all in-service service circuits.

SVN Software Version Number. The SVN allows the MEmanufacturer to identify different software versions of a giventype approved mobile. See also IMEI and IMEISV.

SW Software.

SWFM SoftWare Fault Management. Software faults are handledthrough a SWFM facility which routes those events to theOMC independently through the FCP.

SYM SYstem information Manager. The SYM builds and sendsGPRS system information messages over the BCCH.

sync synchronize/synchronization.

Synchronization burst Period of RF carrier less than one timeslot whose modulationbit stream carries information for the MS to synchronize itsframe to that of the received signal.

Synthesizer hopping Synthesizer hopping is a method of frequency hopping inwhich the RCUs are re-tuned in real-time, from frequency tofrequency.

SYS SYStem.

SYSGEN SYStem GENeration. The Motorola procedure for loading aconfiguration database into a BTS.

T -TxBPF

T Timer.

T Transparent.

T Type only.

T1 Digital WAN carrier facility that transmits DS-1-formatted dataat 1544 kbp/s through the telephone-switching network.companies. T1 lines are widely used for private networks aswell as interconnections between an organization�s PBX orLAN and the telco.

T43 Type 43 Interconnect Board. Provides interface to 12unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for2 Mbit/s circuits (See BIB).

TA Terminal Adaptor. A physical entity in the MS providingterminal adaptation functions (see GSM 04.02).

TA See Timing Advance.

TAC Type Approval Code. Part of the IMEISV.

TACS Total Access Communication System. European analoguecellular system.


02 May 20037�66


68P02901W01-M

TAF Terminal Adaptation Function.

TATI Transmit Antenna Transceiver Interface. The TATI consistsof RF combining equipments, either Hybrid or CavityCombining. See CCB.

TAXI Transparent Asynchronous Transmitter/Receiver Interface(physical layer). A 100 Mbps ATM transmission standarddefined by the ATM Forum.

TBD To Be Determined.

TBF Temporary Block Flow. MAC modes support the provision ofTBFs allowing the point-to-point transfer of signalling anduser data between the network and an MS.

TBR Technical Basis for Regulation. An ETSI document containingtechnical requirements and procedures.

TBUS TDM Bus. A TBUS is a logical device made up of the TDMbackplane of a cage, the KSW devices managing the TDMhighway of the cage, and local and remote KSWX devices (ifthey exist).

TC Transaction Capabilities. TC refers to a protocol structureabove the network layer interface (i.e., the SCCP serviceinterface) up to the application layer including commonapplication service elements but not the specific applicationservice elements using them. TC is structured as aComponent sub-layer above a Transaction sub-layer.

TCAP Transaction Capabilities Application Part. The layer of theSS7 protocol that is used to obtain Routing data for certainservices.

TCB TATI Control Board.

TCH Traffic CHannel. GSM logical channels which carry eitherencoded 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 A full rate TCH at 4.8 kbit/s.

TCH/F9.6 A full rate TCH at 9.6 kbit/s.

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 mainprotocols in TCP/IP networks. Whereas the IP protocol dealsonly with packets, TCP enables two hosts to establish aconnection and exchange streams of data. TCP guaranteesdelivery of data and also guarantees that packets will bedelivered in the same order in which they were sent. See alsoIP and TCP/IP.


02 May 2003


68P02901W01-M 7�67

TCP/IP Transmission Control Protocol/Internet Protocol. Twointerrelated protocols that are part of the Internet protocolsuite. TCP operates on the OSI Transport Layer and IPoperates 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 thatcombines data streams by assigning each stream a differenttime slot in a set. TDM repeatedly transmits a fixed sequenceof time slots over a single transmission channel. WithinT-Carrier systems, such as T-1 and T-3, TDM combines PCMstreams created for each conversation or data stream.

TDMA Time Division Multiple Access. A technology for deliveringdigital wireless service using TDM. TDMA works by dividing aradio frequency into time slots and then allocating slots tomultiple calls. In this way, a single frequency can supportmultiple, simultaneous data channels.

TDU TopCell Digital Unit. Part of the TopCell BTS hardware. ATDU is capable of supporting 6 TRUs for supporting up to 6sectors.

TE Terminal Equipment. Equipment that provides the functionsnecessary for the operation of the access protocols by theuser.

Tei Terminal endpoint identifier. A number that identifies a specificconnection endpoint within a service access point.

TEI Terminal Equipment Identity.

TEMP TEMPorary.

TEST TEST control processor.

TF Transmission Function. The TF provides layered protocolsoftware for handling payload information transfer and forproviding signalling communications between the controlfunction and external systems.

TFA TransFer Allowed. An SPC route management message usedto notify adjacent signalling points of an accessible route.

TFP TransFer Prohibited. An SPC route management messageused to notify adjacent signalling points of an inaccessibleroute.

TFTP Trivial File Transfer Protocol. TFTP is a simple form of FTP.It uses UDP and provides no security features. It is oftenused by servers to boot diskless workstations, X-terminals,and routers.

TI Transaction Identifier.

Timeslot The multiplex subdivision in which voice and signalling bitsare sent over the air. Each RF carrier is divided into 8timeslots. See also ARFCN.

Timing advance A signal sent by the BTS to the MS. It enables the MS toadvance the timing of its transmission to the BTS so as tocompensate for propagation delay.

TL See Transport Layer.


02 May 20037�68


68P02901W01-M

TLV Type, Length and Value. An encoding element composed ofthree fields: a type identifier, a length indicator, and contentoctets.

TM Traffic Manager.

TMI TDM Modem Interface board. Provides analogue interfacefrom IWF to modems for 16 circuits. Part of IWF.

TMM Traffic Metering and Measuring. TMM provides system toolsto be used by traffic engineering and switch maintenancepersonnel 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 physicalentities required to implement the Network Managementfunctionality for the PLMN.

Also, TMN was originated formally in 1988 under the ITU-TSas a strategic goal to create or identify standard interfacesthat would allow a network to be managed consistently acrossall network element suppliers. The concept has led to a seriesof interrelated efforts at developing standard ways to defineand address network elements. TMN uses the OSIManagement Standards as its framework. TMN applies towireless communications and cable TV as well as to privateand public wired networks.

TMSI Temporary Mobile Subscriber Identity. A unique identitytemporarily allocated by the MSC to a visiting mobilesubscriber to process a call. May be changed between callsand even during a call, to preserve subscriber confidentiality.

TN Timeslot Number.

TON Type Of Number.

Traffic channels Channels which carry user�s speech or data. See also TCH.

Traffic unit Equivalent to an erlang.

Training sequence Sequence of modulating bits employed to facilitate timingrecovery and channel equalization in the receiver.

Transport Layer See OSI RM. The Transport Layer responds to servicerequests from the Session Layer and issues service requeststo the Network Layer. Its purpose is to provide transparenttransfer of data between end users, thus relieving the upperlayers from any concern with providing reliable andcost-effective data transfer.

TRS Timeslot Resource Shifter. The TRS determines whichtimeslots are active in a PRP board to perform a control ofthe GPRS traffic.

TRAU Transcoder Rate Adaption Unit. TRAU converts the encodedvoice and rate adapted data into 64 kbps data for the PSTN.

TRU TopCell Radio unit.

TRX Transceiver(s). A network component which can serve fullduplex communication on 8 full-rate traffic channels accordingto specification GSM 05.02. If Slow Frequency Hopping(SFH) is not used, then the TRX serves the communicationon one RF carrier.

TS Technical Specification.


02 May 2003


68P02901W01-M 7�69

TS TeleService. Any service provided by a telecommunicationprovider.

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 thecentre of a burst to help the receiver identify and synchronizeto the burst. The training sequence is a set sequence of bitswhich is known by both the transmitter and receiver. Thereare eight different TSCs numbered 0 to 7. Nearby cellsoperating with the same RF carrier frequency use differentTSCs to allow the receiver to identify the correct signal.

TSI TimeSlot Interchange. The interchange of timeslots within aTDM stream.

TSDI Transceiver Speech and Data Interface.

TSM Transceiver Station Manager.

TSW Timeslot SWitch.

TTCN Tree and Tabular Combined Notation. TTCN is aprogramming language endorsed by ISO that is used to writetest suites for telecommunications systems.

TTL Transistor to Transistor Logic. A common semiconductortechnology 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 modelagainst which the performance of a GSM receiver can bemeasured. See also TU50, HT100, RA250 and EQ50.

TU50 Typical Urban with the MS travelling at 50 kph. Dynamicmodel against which the performance of a GSM receiver canbe measured. See also TU3, HT100, RA250 and EQ50.

TUP Telephone User Part. TUP was an earlier implementation ofSS7 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 theMS_TXPWR_REQUEST and MS_TXPWR_CONFparameters.

TxBPF Transmit Bandpass Filter. See BPF.


02 May 20037�70


68P02901W01-M

U - UUS

UA Unnumbered Acknowledgment. A message sent from theMS to the BSS to acknowledge release of radio resourceswhen a call is being cleared.

UCS2 Universal Coded Character Set 2. A codeset containing all ofthe characters commonly used in computer applications.

UDI Unrestricted Digital Information.

UDP User Datagram Protocol. UDP is a connectionless protocolthat, like TCP, runs on top of IP networks. Unlike TCP/IP,UDP/IP provides very few error recovery services, offeringinstead a direct way to send and receive datagrams over anIP network. It is used primarily for broadcasting messagesover a network.

UDUB User Determined User Busy.

UHF Ultra High Frequency. The UHF range of the radio spectrumis the band extending from 300 MHz to 3 GHz.

UI Unnumbered Information (Frame).

UIC Union International des Chemins de Fer. The UIC is theworldwide organisation for cooperation among railwaycompanies. Its activities encompass all fields related to thedevelopment of rail transport.

UID User ID. Unique number used by the system to identify theuser.

UL Upload (of software or database from an NE to a BSS).

UL UpLink.

ULC UpLink Concatenator. The ULC concatenates RLC datablocks into LLC frames.

Um Air interface.

UMTS Universal Mobile Telecommunication System. The Europeanimplementation of the 3G wireless phone system. UMTS,which is part of IMT-2000, provides service in the 2GHz bandand offers global roaming and personalized features.Designed as an evolutionary system for GSM networkoperators, multimedia data rates up to 2 Mbps are expected.

UNIX A multiuser, multitasking operating system that is widely usedas the master control program in workstations and especiallyservers. UNIX was developed by AT&T and freely distributedto government and academic institutions, causing it to beported to a wider variety of machine families than any otheroperating system. As a result, UNIX became synonymouswith open systems.

UPCMI Uniform PCM Interface (13 bit). The UPCMI is introduced fordesign purposes in order to separate the speech transcoderimpairments 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).


02 May 2003


68P02901W01-M 7�71

UPS Uninterruptable Power Supply. A device that is insertedbetween a primary power source, such as a commercialutility, and the primary power input of equipment to beprotected, e.g., a computer system, for the purpose ofeliminating the effects of transient anomalies or temporaryoutages. Backup power is used when the electrical powerfails 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 fromthe full burst because of the bit shift of the I and Q parts ofthe GMSK signal.

USF Uplink State Flag.

USSD Unstructured Supplementary Service Data. The USSDmechanism allows the MS user and a PLMN operator definedapplication to communicate in a way which is transparent tothe MS and to intermediate network entities. The mechanismallows development of PLMN specific supplementaryservices.

UTRAN UMTS Radio Access Network

UUS User-to-User Signalling supplementary service. The UUSsupplementary service allows a mobile subscriber tosend/receive a limited amount of information to/from anotherPLMN or ISDN subscriber over the signalling channel inassociation with a call to the other subscriber.

V - VTX host

V Value only.

VA Viterbi Algorithm (used in channel equalizers). An algorithm tocompute the optimal (most likely) state sequence in a modelgiven a sequence of observed outputs.

VAD Voice Activity Detection. A process used to identify presenceor absence of speech data bits. VAD is used with DTX.

VAP Videotex Access Point.

VBS Voice Broadcast Service. VBS allows the distribution ofspeech (or other signals which can be transmitted via thespeech codec), generated by a service subscriber, into apredefined geographical area to all or a group of servicesubscribers located in this area.

VC See Virtual Circuit.

VCO Voltage Controlled Oscillator. An oscillator whose clockfrequency is determined by the magnitude of the voltagepresented at its input. The frequency changes when thevoltage changes.

VCXO Voltage Controlled Crystal Oscillator.

VDU Visual Display Unit. A device used for the real-time temporarydisplay of computer output data. Monitor.

VGCS Voice Group Call Service.


02 May 20037�72


68P02901W01-M

Videotex The Videotex service is an interactive service, that by meansof proper access points and standardized procedures,provides the access to data base information stored in hostcomputers external to the PLMN, via publictelecommunication networks.

Virtual Circuit A connection between two devices, that functions as though itis a direct connection, even though it may physically becircuitous. The term is used most frequently to describeconnections between two hosts in a packet-switchingnetwork.

VLR Visitor Location Register. A GSM network element whichprovides a temporary register for subscriber information for avisiting subscriber. Often a part of the MSC.

VLSI Very Large Scale Integration (in ICs). The process of placingbetween 100,000 and one million electronic components on asingle chip.

VMSC Visited MSC. (Recommendation not to be used).

vocoder Abbreviation for voice-coder. A device that usually consists ofa speech analyzer, which converts analog speech waveformsinto narrowband digital signals, and a speech synthesizer,which converts the digital signals into artificial speech sounds.

VOX Voice Operated Transmission. An acoustoelectric transducerand a keying relay connected so that the keying relay isactuated when sound, or voice energy above a certainthreshold is sensed by the transducer. A vox is used toeliminate the need for push-to-talk operation of a transmitterby 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 ratioof maximum to minimum voltage in a standing wave pattern.Note: The VSWR is a measure of impedance mismatchbetween the transmission line and its load. The higher theVSWR, the greater the mismatch. The minimum VSWR, i.e.,that which corresponds to a perfect impedance match, isunity.

VTX host The components dedicated to Videotex service.


02 May 2003


68P02901W01-M 7�73

W - WWW

WAN Wide Area Network. A physical or logical network thatprovides data communications to a larger number ofindependent users than are usually served by a LAN and isusually spread over a larger geographic area than that of aLAN. WANs may include physical networks, such as ISDNnetworks, X.25 networks, and T1 networks.

WPA Wrong Password Attempts (counter). Some supplementaryservices have the option of the subscriber using a password.If a password check is done with an incorrect password, theWPA 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 theservice provider.

WS Work Station. The remote device via which O&M personnelexecute input and output transactions for networkmanagement purposes.

WSF Work Station Function block.

WWW World Wide Web. An international, virtual-network-basedinformation service composed of Internet host computers thatprovide 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 hypertextbrowser.


02 May 20037�74


68P02901W01-M

X - X Window

X.25 X.25, adopted as a standard by the CCITT, is a commonlyused protocol for public packet-switched networks(PSPDNS). The X.25 protocol allows computers on differentpublic networks to communicate through an intermediarycomputer at the network layer level. The protocolcorresponds closely to the data-link and physical-layerprotocols defined in the OSI communication model.

X.25 link A communications link which conforms to X.25 specificationsand uses X.25 protocol (NE to OMC links).

XBL Transcoder to BSS Link. The carrier communications linkbetween the Transcoder (XCDR) and the BSS.

XCB Transceiver Control Board. Part of the Transceiver.

XCDR Full-rate Transcoder. The XCDR is the digital signalprocessing equipment required to perform GSM-definedspeech encoding and decoding. In terms of datatransmission, the speech transcoder interfaces the 64 kbit/sPCM in the land network to the 13 kbit/s vocoder format usedon the Air Interface. See also RXCDR.

XCDR board The circuit board required to perform speech transcoding atthe 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 XWindow System. A user can have many different invocationsof xterm running at once on the same display, each of whichprovides independent input and output for the processrunning in it (normally a shell).

X Window A specification for device-independent windowing operationson bitmap display devices.

ZC

ZC Zone Code. Part of the RSZI. The ZC identifies a regionalsubscription zone as a pattern of allowed and not allowedlocation areas uniquely within a PLMN.

02 May 2003


68P02901W01-M I�1

Index

GSR6 (Horizon II)

02 May 2003 I�2


68P02901W01-M

GSR6 (Horizon II)

02 May 2003


68P02901W01-M I�3

Numbers2 Mbit/s link, 2�53

2-site repeat pattern, 2�50

4 to 2-wire hybrid, 2�51

64 kbit/s link, 2�43

AAccess Grant CHannel (AGCH), 2�45

add and delete option, 2�43

Advanced load handover management, 2�82

Advanced load management for EGSM carriers, 5�64

air interface, 3�4control, 3�21radio channel, 2�56

air interface (BSS to MS), 2�44

alarm, reporting, 4�55

alarm state, 4�53

alarmscolours, 4�55, 4�59disk usage, 4�70

alarms icon, 4�58

alarms severity, icon colour, 4�59

allocating handover numbers, overview, 2�35

allocating TMSI numbers, overview, 2�36

architecturenetwork, hierarchical, 2�48PCU, 3�44

associated control channel ID, 2�49

associated control channels, 2�45FACCH, 2�45SACCH, 2�45

audio quality, 2�23

AUthentication Centre, AUC, 2�34

authentication key, 2�34

Bbackground maps, 4�55

Base Station System (BSS)configurations, 2�42overview, 2�42software functions, 2�43

BCCH, 4�20

Bill Of Materials, BOM, 4�31

billing centre, 2�46

BOM, bill of materials, 4�31

bridge, PCI to PCI, 3�44

broadcast control channelsFCCH, 2�45SCH, 2�45

Broadcast Control Channels (BCCH), 2�45

BSCinteraction with MSC, 3�6interfaces

to BTS, 3�19to MSC, 2�58, 3�19

purpose and functions, 3�6redundancy, 3�28site configuration, 3�12

BSC capacity, overview, 3�7

BSS, 3�5, 4�16capacity, 3�11fault management, 3�27handover, overview, 3�21links, overview, 3�4network elements, overview, 3�4network topology, 3�16

daisy chain with fork and return loop to chain,3�17

daisy chain with fork and return loop to BSC,3�17

drop and insert, 3�18open ended daisy chain, 3�16overview, 3�16star (spoke), 3�16

operation and maintenance, 4�7overview, 3�4purpose and functions, 3�4redundancy, 3�27site configurations

BSC, 3�12BTS, 3�12flexibility, 3�10introduction, 3�10

BSS definition, 4�4

BSS interfaces, 2�44A interface, 2�44Abis interface, 2�44Lb interface, 3�20

BSS mobile application part, 2�44

BSS object, 4�63

BSS software feature, Enhanced GDP provisioning,GSR6, 5�50

GSR6 (Horizon II)

02 May 2003 I�4


68P02901W01-M

BSS software features1900 MHz Horizonmacro, GSR5.1, 5�453646, GSR6, 5�484420, 5�664471, 5�66, 5�70850 MHz frequency range, GSR5.1, 5�45advanced load management for EGSM carriers,

GSR6, 5�64basic MPROC redundancy, GSR6, 5�57BSS overload protection, GSR5, 5�36BSS processing of suspend message, GSR5.1,

5�43BTS concentration call priority handling, GSR5,

5�41BTS concentration resource optimization for

handovers, GSR5, 5�40call downgrade on CIC mismatch, GSR6, 5�52Clean install (E3x00), GSR6, 5�60code corruption immune design, GSR5, 5�39CS3, CS4 and 32 kbits/s TRAU, GSR5.1, 5�44dynamic allocation of RXCDR-BSC circuits,

GSR5, 5�384443, 5�66, 5�68enhanced BSC capacity phase 2, GSR6, 5�58enhanced MMI link device warnings, GSR5, 5�42enhanced power outage recovery, GSR5, 5�40enhanced XBL, GSR5, 5�38GPROC fast reset, GSR5.1, 5�45GPROC function pre-emption, GSR5, 5�42GPRS PCU recovery on last GSL failure, GSR6,

5�53handover parameter, GSR5, 5�40Horizonmicro2/Horizoncompact2 generic BTS

software, GSR5, 5�39improved MPROC software failures detection and

recovery, GSR6, 5�58improved MTL load balancing, GSR5, 5�40Inter Radio Access Technology (RAT) 2�G to 3�G

handover, GSR6, 5�59Introduction, 5�3link utilization improvements, GSR6, 5�63Multiple GPRS carriers per Cell, GSR6, 5�49Network controlled (NC1 and NC2) cell

reselection, GSR6, 5�54optimized power control, GSR5, 5�41parallel cage enable, GSR5, 5�42per neighbour area for adaptive handovers,

GSR5, 5�41propogate TSC changes to all timeslots, GSR5,

5�39receive antenna VSWR and radio loopback test,

GSR5, 5�37Release 1.1.1.0, 5�4Release 1.1.2.0, 5�6Release 1.1.2.1, 5�7Release 1.1.2.2, 5�8Release 1.1.2.3, 5�9

Release 1.2.0.0, 5�10Release 1.2.0.3, 5�12Release 1.2.2.0, 5�13Release 1.2.2.2, 5�14Release 1.2.2.3, 5�15Release 1.2.3.0, 5�16Release 1.3.0.x, 5�18Release 1.4.0.0, 5�21Release 1.4.0.1, 5�22Release 1.4.0.6, 5�23Release 1.4.0.7, 5�24Release 1.4.1.1, 5�25Release GSR2, 5�27Release GSR3, 5�29Release GSR4, 5�32Release GSR5, 5�36Release GSR5.1, 5�43Release GSR6, 5�47single BCCH for dual band cells, GSR5, 5�39SMS CB upgrade, GSR5, 5�37support for E1/T1 conversion, GSR5, 5�39support for frame erasure rate statistic, GSR5,

5�41support for the MTL stat, GSR5, 5�41temporary block flow, GSR6, 5�61unequip of TCU/CTU cabinets, GSR5.1, 5�45

BSSAP, 2�44

BSSMAP, 2�44

BTSinterfaces

to BSC, 3�19to MS, 2�59, 3�20

purpose and functions, 3�8radio types, 3�8RCU, DRI, 4�19redundancy, 3�28site configuration, overview, 3�12

CC7, 2�30, 2�64

call control functions, overview, 2�30

call handling, overview, 2�37

call management, functional layering, 2�55

capacityBSS, 3�11GSM system, overview, 2�50

CBC, 2�46

CBL, 4�25

XCDR, 2�6

Cell Broadcast Centre (CBC), 2�46

GSR6 (Horizon II)

02 May 2003


68P02901W01-M I�5

Cell Broadcast CHannel (CBCH), 2�45

cell configuration, logical devices, 4�21

channelslogical, overview, 2�44logical types, overview, 2�44physical, overview, 2�44

chassis, PCU, 3�46

CM MIB, 4�50automatically created objects

MMS, 4�67NESoftware, 4�67source, 4�67SWInventory, 4�67TRX, 4�67

definition, 4�60

co-channel interference, 2�50

coding schemes, software features, 3�38

common control channels, 2�45AGCH, 2�45CBCH, 2�45PCH, 2�45RACH, 2�45

CommsLink object, 4�63

communication link, 3�4

Compress all BTS objects at the BSC, feature,GSR6, 5�65

confidentialitysignalling information, 2�24user data, 2�24

configuration mgt, 4�38

configuration objects, 4�62

configurations, BSS site, introduction, 3�10

containment, managed objects, 4�18

control, functions, 3�50

control channelsassociated control channels, 2�45broadcast control channels, 2�45common control channels, 2�45dedicated control channels, 2�45

controlling LAIs, overview, 2�35

controlling MSRNs, overview, 2�35

DD channel, 2�24

daisy chainopen ended, 3�16with fork and return loop to BSC, 3�17with fork and return loop to chain, 3�17

data channels, 2�45

data communication, overview, 2�24

database schemadefinition, 4�41size, 4�41

DBMS, 4�37

DCS1800, radio types, 3�8

DCS1800 frequencies and channelsDCS1800 channels, 2�86DCS1800 frequencies, 2�86

dedicated control channels, 2�45SDCCH, 2�45

definitionsE1 link, 2�53T1 link, 2�53

device mgt, 4�38

digital communication, 2�23, 2�49

digital networks, overview, 2�22

Digital Signal Processor (DSP), 2�23

digital switching matrix, overview, 3�6

Direct Transfer Application Part (DTAP), 2�44

discontinuous reception, 3�22

discontinuous transmission, 3�22

Distribution of Motorola manuals, 1�5Available formats, 1�5Ordering manuals, 1�5Updating manuals, 1�5

Documentation coding, 1�4

downlink, 4�21

DPROC, 3�45(PICP), 3�45(PRP), 3�45

DRI, 4�19, 4�20

dropped calls, 2�23

DTAP, 2�44

dynamic adaptation of coding schemes, softwarefeatures, 3�38

EE1, PMC, 3�46

E1 link, definition, 2�53

GSR6 (Horizon II)

02 May 2003 I�6


68P02901W01-M

EGSM to EGSM handovers, 2�82

EGSM900, radio types, 3�8

EIR, 2�5, 2�21

electrical interfaces, standardized, overview, 2�48

EM proxy process, 4�51

EM sub schema, 4�41

Emergency caller location, LCS, 2�52, 5�56

emergency calls, overview, 2�30

enhanced frequency hopping, 2�9

Enhanced GPRS One Phase Access, feature, GSR6,5�64

enhanced GPRS one phase access, softwarefeatures, 3�39

environment, PCU, 3�33

equipment identity, mobile, international, 2�21

equipment identity register, overview, 2�33

Equipment Identity Register (EIR), 2�21

ethernet, 4�32

ethernet support, 4�40

event interface, 4�38

event/alarm mgt, 4�38

expert front panel, 4�12

extrapolation algorithm, 2�23

FFast Associated Control CHannel (FACCH), 2�45

fault management, BSS, 3�27

fault toleranceMotorola GSM, 2�9PCU, 3�46

features, PCU, 3�34

features summary, PCU, 3�35

frequency reuse

2-site 6-sector, 3�253-site 3-sector, 3�253-site 6-sector, 3�254-site, 3�25introduction, 3�24

reuse, 9-site, 3�24synchronization, 3�23

Frequency Correction CHannel (FCCH), 2�45

frequency hopping of PDCH, software features, 3�40

frequency reuse, overview, 2�23

functional layering, 2�55

functionscontrol, 3�50MSC, overview, 2�28PCU system, 3�50PSP, 3�44radio, 3�50SGSN, 3�50

future system, Motorola GSM, 2�10

GGaussian Minimum Shift Keying (GMSK), 2�44, 2�47

Gbinterface, 3�49processes, 3�51

Gb interface, software features, 3�40

Global System for Mobile Communications (GSM),introduction, 2�3

Glossary of technical termsA Interface � AUTO, 7�3B Interface � Byte, 7�7C � CW, 7�10D Interface � DYNET, 7�18E � EXEC, 7�22F Interface � Full Rate, 7�25G Interface � GWY, 7�28H Interface � Hyperframe, 7�30I � IWU, 7�31k � KW, 7�35L1 � LV, 7�35M � MUX, 7�38N/W � nW, 7�43O � Overlap, 7�45PA � PXPDN, 7�47QA � Quiesent mode, 7�53R � RXU, 7�53S7 � SYSGEN, 7�58T � TxBPF, 7�65U � UUS, 7�70V � VTX host, 7�71W � WWW, 7�73X � X Window, 7�74ZC, 7�74

GMSK, 2�44, 2�47

GPROC2, 4�16

GPRSnetwork architecture, 3�31overview, 3�29

GPRS radio channel allocation, software features,3�36

GSR6 (Horizon II)

02 May 2003


68P02901W01-M I�7

graphic objects, maps, 4�61

GSMinterfaces, overview, 2�48network, 4�15network architecture, 3�31radio channel, 2�43radio interface, noise robustness, 2�51sub-systems, 2�46

GSM frequencies and channels, 2�66EGSM frequencies, 2�82ESGM channels, 2�83GSM850 channels, 2�67GSM850 frequencies, 2�66GSM900 channels, 2�75GSM900 frequencies, 2�74

GSM900, radio types, 3�8

GSNnetwork architecture, 3�31overview of complex, 3�30

GUIcommand line interface, 4�14configurations, 4�43GUI front panel, 4�12processors, 4�43

GUI client, SPARCstation 5, 4�48

GUI server, GUI client, 4�52

Hhandover, 2�49

overview, 3�21

handover control, 4�21

handportable, 2�24

hardware devices, 4�64

hierarchical network architecture, 2�48

hierarchy, network, 4�7

HLR, 2�5, 2�21

HLR data, 2�34

HLR master database, overview, 2�34

home location register, overview, 2�33

IIMEI, 2�21

IMSI, 2�21

In Service (INS) state, 4�53

increased capacity, overview, 2�22

information flow, OMC and NEs, 4�30

INFORMIX, 4�41

infrastructure, 2�50

inter-MSC handovers, 2�32

interfacesBSC to BTS, 3�19BTS to MS, 2�59, 3�20Gb, 3�49GSM, overview, 2�48GUI, command line, 4�11MSC to BSC, 2�58, 3�19PCU, 3�47, 3�48PCU-BSC, 3�48protocol layering, 3�19redundancy, 3�27standardized, 2�54standardized electrical, overview, 2�48summary, 2�57

interferenceco-channel, 2�50co-channel and adjacent channel, 2�23, 2�49

International Mobile station Equipment Identity (IMEI),2�21

International Mobile Subscriber Identity (IMSI), 2�21

introductionGPRS, 3�29GSN complex, 3�30PCU, 3�29

Introduction to Motorola GSM documentation, 1�3

introduction to the system processor, 4�35

ISDN, 2�10, 2�56

ISDN compatibility, overview, 2�48

LLAPD, 2�65

LCS, LoCation Services, 2�52, 5�56

link, types, 4�25

link quality, 2�23, 2�49

linksmaps, 4�55overview, 3�4physical/logical, 4�23

local registration and call handover, overview, 2�31

Location Services (LCS), 2�52, 5�56

logical channels, 2�43overview, 2�44types, overview, 2�44

GSR6 (Horizon II)

02 May 2003 I�8


68P02901W01-M

logical groups, 4�62hardware devices, 4�64logical links, 4�65radio frequency, 4�66software functions, 4�65

logical links, 4�65OML, MTL, RSL, XBL, CBL, 4�25

lost calls, 2�23, 2�49

low bit rates, non-voice data, overview, 2�50

Mmaintenance, Motorola GSM, 2�9

MAP, 2�30, 2�56

Map, automatically created objectsMap, 4�68MapLink, 4�68MapNode, 4�68

map, 4�50configuration, 4�54links, 4�55state changes, 4�55

Map display, map icons, 4�56

MapLink, 4�61

MapNode, 4�61

maps, 4�53background maps, 4�55configuration objects, 4�60graphic objects, 4�60

maps icon, 4�46

measured parameters, 2�49

medium access mode, software features, 3�36

Message Transfer Link (MTL), 2�30

MMS, MSI, 4�18

Mobile Application Part (MAP), 2�30, 2�56

mobile services switching centre, 2�28overview, 2�5, 2�28

mobile station, 2�24overview, 2�20

Mobile Subscriber ISDN (MSISDN) number, 2�21

mobility management, functional layering, 2�55

modem, 2�24, 2�46

module, information, subscriber, 2�21

Motorola manualsCD�ROM, 1�5Extranet, 1�5Hardcopy, 1�5

Motorola network specifications, introduction, 2�11

Motorola OMC, typical configuration, 4�31

MPROC, 3�44(PSP), 3�44

MSinterface to BTS, 2�59, 3�20power saving, overview, 2�50tracking, overview, 2�50

MS flow control, software features, 3�41

MS to MS callsMS to MS

different PLMN different country, 2�41different PLMN same country, 2�40same PLMN, 2�39

overview, 2�39

MS to PSTN subscriber, overview, 2�37

MSCinteraction with BSC, 3�6interface to BSC, 2�58, 3�19site configurations, overview, 3�12

MSC object, 4�63

MSI, MMS, 4�18, 4�29

MSI object, 4�64

MSISDN, 2�21

MTL, 4�25

MTP, 2�64

multiplexer, 4�27, 4�33

multiplexing, 2�43

NNC1, Nework Controlled cell reselectionLoCation

Services, 5�54

NC2, Network Controlled cell reselection, 5�54

NE definition, network element, 4�4

networkdevices, 4�29hierarchy, 4�7traffic capacity, 4�34

network architecture , GSM/GPRS/GSN, 3�31

network configuration, 4�53

Network Controlled cell reselection, NC1/NC2, 5�54

network elementslocation register, overview, 2�5overview, 3�4

GSR6 (Horizon II)

02 May 2003


68P02901W01-M I�9

Network File System (NFS), 4�43

Network Management Centre, (NMC), 4�7

network management centrefunctions, overview, 2�25overview, 2�5

network map, 4�50configuration, 4�54

network maps, 4�53

network object, 4�63

network status summary, 4�46

network topologyBSS, 3�16daisy chain with fork and return loop to BSC,

3�17daisy chain with fork and return loop to chain,

3�17drop and insert, 3�18open ended daisy chain, 3�16star (spoke), 3�16

NFS (Network File System), 4�43

night concentration configuration, 4�49

NMC, 4�7

noise robustness, radio interface, overview, 2�51

non-stop-UX A22 IPM02, 4�40

non-voice data, low bit rate use, overview, 2�50

NSS, features, 4�46

OObjects

Map, automatic creation of, 4�68MapLink, automatic creation of, 4�68MapNode, automatic creation of, 4�68MMS, automatic creation of, 4�67NESoftware, automatic creation of, 4�67SWInventory, automatic creation of, 4�67TRX, automatic creation of, 4�67

objects, source, automatic creation of, 4�67OMC software features, 4475, 6�52, 6�53OMC-R

basic configuration, 4�8command line interface, 4�14communication with GSM network, 4�4configuration summary, 4�10definition, 4�3GUI client, 4�48GUI front panel, 4�12network management architecture, 4�7Network management functions, 4�5PCU management, 3�42processes, 4�38SPARCstation 5, 4�48

OMC-R definition, 4�4OMC-R, NSS feature, 4�46OMC-R database, 4�41OMC-R functions, 4�16OMC-R object, 4�63OMC-R software features

adaptive handover, GSR5, 6�36Applix 4.41 upgrade, GSR5, 6�39Bay level cal default data, GSR5, 6�39BTS concentration, GSR5, 6�35cell parameter import/export, GSR5, 6�39cell Xchange, GSR6, 6�51changing NE ID of Assoc_BSSs or

Assoc_RXCDRs, GSR5, 6�40coincident multiband boundaries, GSR5, 6�36completion of OMC support for Horizonmacro,

GSR5, 6�38CS3, CS4 and 32 kbits/s TRAU, GSR5.1, 6�44datagen support, GSR5, 6�41DRI combiner operability improvement, GSR5,

6�38dynamic trace call flow control, GSR5, 6�37EAS relay MMI control for Incell, M-Cell and

Horizon, GSR5, 6�35enable cyclic neighbour statistics, GSR6, 6�50enhanced circuit error rate monitor, GSR6, 6�48enhanced SDCCH to TCH assignment, GSR5,

GSR6 (Horizon II)

02 May 2003 I�10


68P02901W01-M

6�40expansion/de-expansion, GSR5, 6�43flexible neighbour cell processing, GSR5, 6�37geographic command partitioning and region

support, GSR6, 6�47GPROC fast reset, GSR5.1, 6�44increased capacity OMC-R, GSR5, 6�42increased OMC-R neighbour stats, GSR5, 6�41increasing maximum number of trunks per BSC,

GSR5, 6�42intelligent congestion relief, GSR5, 6�35interrogation of NHA with GSM OMC-R EM,

GSR5, 6�39Introduction, 6�3network expansion batch capability, GSR5, 6�41NHA support maximum size GSM OMC-R,

GSR5, 6�39OMC-R GUI supportfor PCU device object,

GSR5, 6�41OMC-R GUI usability, GSR5, 6�41OMC-R GUI usability for large network support,

GSR6, 6�49online network expansion - phase 3, GSR6, 6�50optimized power control, GSR5, 6�35PCU alarms detected by HSC, GSR5, 6�43propogation after audit, GSR5, 6�35proxy cell autocreation, GSR5, 6�37proxy cell import/export, GSR5, 6�38Q3 support, GSR5, 6�38Release 1.1.2.0, 6�4Release 1.1.2.1, 6�5Release 1.1.2.2, 6�6Release 1.1.2.3, 6�8Release 1.1.2.4, 6�10Release 1.2.0.0, 6�11Release 1.2.2.1, 6�14Release 1.2.2.2, 6�17Release 1.2.3.0, 6�18Release 1.3.0.0, 6�19Release 1.4.0.0, 6�20Release 1.4.0.1, 6�22Release 1.4.0.6, 6�24Release 1.4.0.7, 6�25Release 1.4.1.0, 6�26Release GSR2, 6�28Release GSR3, 6�31Release GSR4, 6�32Release GSR4.1, 6�33Release GSR5, 6�34Release GSR5.1, 6�44Release GSR6, 6�46Release GSR6 (Horizon II), 6�52removal of clear stats command, GSR5, 6�43reporting the results of alarms recovery action,

GSR5, 6�36support for Vanguard 6455 router, GSR5, 6�43

support of BCCH and SDCCH for EGSM, GSR5,6�36

system upgrade, GSR5, 6�40unequip of TCU/CTU cabinets, GSR5.1, 6�45Vanguard software upgrade support, GSR5, 6�43web MMI, GSR5.1, 6�44

OMC-R system configurationhardware impact, 4�45single platform processor, 4�8

OML, 4�25

one phase access, software features, 3�39

operating system, non-stop-UX A22 IPM02, 4�40

operations and maintenance centre, overview, 2�5

OSI, 2�62

Other manuals, 1�16INFORMIX manuals, 1�16Printer manuals, 1�16SPARC E3000/E3500, 1�16SPARCstation manuals, 1�16X.25 manuals, 1�16

Out Of Service (OOS) state, 4�53

Overview of Motorola manuals, 1�6Manuals types, 1�6

P

packet switch, 4�27, 4�33

PADS, X.25, 2�46

Paging CHannel (PCH), 2�45

part, applicationBSS mobile, 2�44direct transfer, 2�44mobile, 2�30, 2�56

password protection, security management, 2�19

PATH, physical link, 4�24

PCI to PCI bridge, 3�44

PCS1900 frequencies and channels, 2�106PCS1900 channels, 2�106PCS1900 frequencies, 2�106

GSR6 (Horizon II)

02 May 2003


68P02901W01-M I�11

PCU, 3�32architecture, 3�44chassis, 3�46environment, 3�33fault tolerance, 3�46features summary, 3�35interfaces, 3�47, 3�48introduction of PCU, 4�63list of features, 3�34management, 3�42overview, 3�29, 3�32purpose, 3�42roadmap features, 3�34summary, 3�33system functions, 3�50

PCU architecture, PPB, 3�44

PCU load balancing & sharing, software features,3�41

PCU processes, PRP processes, Gb processes,3�51

PCU system, overview, 3�42

PCU-BSC, interface, 3�48

performance measurements, 4�30

performance mgt, 4�38

Periodic Supervision of Accessibility (PSA), 4�69

physical channels, overview, 2�44

physical layer, functional layering, 2�55

physical link, PATH, 4�24

PICP, 3�45

PM sub schema, 4�41

PMC, E1, 3�46

point-to-point GPRS service, software features, 3�35

power budget, 4�21

power control, 4�21overview, 3�22

power control: uplink/downlink, software features,3�40

power saving, MS, overview, 2�50

PPB, PCU architecture, 3�44

Private eXchange Packet Data Network, PXPDN,4�33

procedures, handover, 2�49

protocol stacks, TCP/IP, Ethernet, X11, X25, 4�32

protocols, network, 2�62

PRP, 3�45processes, 3�51

PSA, definition, 4�69

PSP, functions, 3�44

PSTN, 2�46

PSTN subscriber to MS, overview, 2�38

PXPDN, 4�33

QQ3 agent, 4�4

quality of reception, 2�49

Rradio, functions, 3�50

radio channel air interface, 2�56

radio channel bit rate, 2�44

radio frequency, 4�66

radio planning, 2�50

radio resource management, functional layering, 2�55

Random Access CHannel (RACH), 2�45

RCU, 4�19

RDBMS, 4�41

received level, 2�49

redundancyBSC, 3�28BSS, 3�27BTS, 3�28interfaces, 3�27RF carrier, 3�27RXCDR, 3�28

related commands and parameters, securitymanagement, 2�19

remote login, 4�38

Remove support for collocated BSC, feature, GSR6,5�65

resource management, 2�59, 3�20

RF carrier, redundancy, 3�27

RSL, 4�25

RTF, 4�20BCCH, 4�20non-BCCH, 4�20

GSR6 (Horizon II)

02 May 2003 I�12


68P02901W01-M

RXCDR, 2�6functions, 4�16operation and maintenance, 4�7purpose and functions, 3�9redundancy, 3�28

RXCDR object, 4�63

S

SCCP, 2�64

security management, password protection, 2�19

security procedures, overview, 2�31

services, ISDN-type, 2�24

SGSN, functions, 3�50

short message service, overview, 2�31

signaling performance, 2�23, 2�49

signalling link protocols, overview, 2�65

signalling links, summary, 2�57

signalling system 7, 2�30, 2�64C 7, 2�48

SIM, 2�21

single BCCH for dual band cells, featuredependencies, 5�46

single platform processor, 4�8

site configurationsBSC, overview, 3�12BTS, overview, 3�12CELL, 4�19introduction, 3�10MSC, overview, 3�12site definition, 4�17

site definition, 4�4

SITE object, 4�63

Slow Associated Control CHannel (SACCH), 2�45

smart card, 2�21

software elements, system processor, 4�38

software featurescoding schemes, 3�38dynamic adaptation of coding schemes, 3�38enhanced one phase access, 3�39frequency hopping of PDCH, 3�40Gb interface, 3�40GPRS radio channel allocation, 3�36medium access mode, 3�36one phase access, 3�39PCU load balancing & sharing, 3�41PCU MS flow control, 3�41point-to-point GPRS service, 3�35power control: uplink/downlink, 3�40support of mobile classes, 3�37two phase packet access, 3�39

software functions, 4�65

software load mgt, 4�38

SPARCstation, 4�8

SPARCstation 5/IPX, 4�48disk size, 4�48

specificationsOMC-R, 2�11receiver, 2�14transmitter, 2�17

speech transcoder, 2�6remote, 2�6

SQL, 4�41

Stand-alone Dedicated Control CHannel (SDCCH),2�45

standardized electrical interfaces, overview, 2�48

star (spoke), network topology, 3�16

state changesadmin and operational, 4�57on map display, 4�55

status summary window, 4�53

sub schema, EM, PM, 4�41

subscriber identity, mobileinternational, 2�21ISDN, 2�21temporary, 2�21

Subscriber Information Module (SIM), 2�21

Summary of Motorola manuals, 1�8Installation and configuration manuals, 1�14Maintenance information manuals, 1�14Operating information manuals, 1�13Service manuals-BSS, 1�8Service manuals-GPRS, 1�11Software release notes, 1�15System information manuals, 1�12Technical description manuals, 1�13

GSR6 (Horizon II)

02 May 2003


68P02901W01-M I�13

support of mobile classes, software features, 3�37

switching matrix, 2�43

synchronization, 2�51

Synchronization CHannel (SCH), 2�45

system impact, security management, 2�19

system planning, Motorola GSM, 2�9

system processor, 2�12, 4�35 software elements, 4�38configurations, 2�12

systems advantages, Motorola GSM, 2�9

TT1 link, definition, 2�53

TBF, 5�61

TCP/IP, 4�40

technological requirements, 2�47

teleservices, 2�49overview, 2�24

Temporary Mobile Subscriber Identity (TMSI), 2�21

terrestrial circuit device management, overview, 3�6

The CM MIB, 4�47

timing adjustment, 2�51

timing advance, overview, 3�23

TMSI, 2�21

topology, BSS network. See network topology

tracking, MS, overview, 2�50

traffic capacity, network, 4�34

speech channelsfull rate, 2�45half rate, 2�45

traffic channels, 2�45

transceiving, DRI/RTF groups, 4�20

transcoder, speech, 2�6

transcoding, 2�43location, 3�9

transmission, discontinuous, 3�22

transport layer, functional layering, 2�55

trunking, 2�50

trustworthiness, 2�49

two phase packet access, software features, 3�39

Uuplink, 4�21

Vvalidation exercise, 2�47

visited location register, overview, 2�35

VLR, 2�5, 2�21

WWAN, 4�32

wide area network, 4�32

XX.11, 4�32

X.21 address, 4�27

X.25, 2�27, 2�65, 4�32

X.25 PADS, 2�46

X25, 2�65

XBL, 4�25

GSR6 (Horizon II)

02 May 2003 I�14


68P02901W01-M

Documents

37852532 GSM Overview