68P02901W01 PDF

GSM Overview
System Information
GSR9
68P02901W01-S
2008 Motorola, Inc. All Rights Reserved.

Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no
liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in content
hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability
arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others. It is possible that this publication may contain references to, or
information about Motorola products (machines and programs), programming, or services that are not announced
in your country. Such references or information must not be construed to mean that Motorola intends to announce
such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include
or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right
to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,
any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the
Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a
product.
A list of 3rd Party supplied software copyrights are contained in the Supplemental information section of this
document.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials
Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT
designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments
requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication
Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Office.
Jul 2008
Table
of
Contents
Contents

System Information: GSM Overview

Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Resolution of Service Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Incorporation of Change Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
24hour support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Questions and comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Security advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Warnings, cautions, and notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
General safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Electromagnetic energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Caring for the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
In EU countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
In non-EU countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CMM labeling and disclosure table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Motorola document set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Ordering documents and CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Document banner definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 1: Introduction to Motorola GSM

Overview of the Motorola GSM system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
The Motorola GSM system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Network element overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Typical GSM system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Unique features of Motorola GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Introduction to the unique features of Motorola GSM . . . . . . . . . . . . . . . . . . . . 1-6
Systems advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
System planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Fault tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Motorola network specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
68P02901W01-S i
Jul 2008
Contents
Introduction to Motorola network elements . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

OMC-R specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Functions of the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
System processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Operator workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Optional processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
OMC configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Data communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Receiver specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Password levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Related commands and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
System impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Mobile station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Introduction to mobile stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Mobile station components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Subscriber Interface Module (SIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Hand portable viability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Equipment identity number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Subscriber identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
GSM network specifications and recommendations . . . . . . . . . . . . . . . . . . . . . . . 1-17
GSM advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Digital networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Increase capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Frequency reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Audio capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Link integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Subscriber services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Data communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Teleservices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Security features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
GSM network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Introduction to GSM network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Network management center functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Monitoring the equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Monitoring the routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Managing the traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Simulating the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Operation and Maintenance center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Introduction to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Mobile services switching center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Introduction to the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
MSC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Gateway MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Flexible design for MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
The A interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Location register interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Message transfer link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Call control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Emergency calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Short message service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Security procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Local registration and call handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Inter-MSC handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Equipment identity register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Home location register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
ii 68P02901W01-S
Jul 2008
System Information: GSM Overview Contents
HLR master database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

HLR data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
Authentication center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
Authentication key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Visitor location register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Controlling LAIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Controlling MSRNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Allocating handover numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Allocating TMSI numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Call handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
MS to PSTN subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
PSTN subscriber to MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
MS to MS calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Base station system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38
Introduction to the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38
BSS configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38
Software functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Motorola BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Connection of MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Speech transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41
BSS application parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41
BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41
Physical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
Logical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
Logical channel types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
Control channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
Traffic channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43
GSM subsystems (non-network elements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
Introduction to GSM non-network element subsystems . . . . . . . . . . . . . . . . . . . 1-44
Inter working function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
Echo canceler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
Billing center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
Cell broadcast center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-45
GSM system features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46
Introduction to GSM system features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46
Technological requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46
Standardized electrical interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47
GSM interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47
ISDN compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47
Signaling System 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47
Hierarchical network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47
Subscriber services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-48
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-48
Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-48
Link integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
Power saving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
Increased capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
Use of low bit rates for non-voice data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
Lower cost of infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50
Site size definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50
Timing adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50
Echo cancelers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50
Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50
Noise robustness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51
BSS Location Services support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51
LCS positioning mechanisms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51
Timing Advance positioning (TA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52
68P02901W01-S iii
Jul 2008
Contents
E1 links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
Link types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
E1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
BSC daisy chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
Standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54
Interface types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54
GSM functional layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55
BSSAP messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56
ISDN messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
MSC to MS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
Location register interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
OMC interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
NMC interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
Interface summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Signaling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
The A interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59
Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59
Air interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60
Lb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
Network protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64
Protocol types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64
OSI/protocol relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-65
ITU-TSS signaling system 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-67
X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68
LAPDm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68
Signaling link protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68
GSM frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-69
Introduction to frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . 1-69
GSM850 frequencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-69
GSM850 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-70
Primary GSM900 frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-77
Primary GSM900 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-78
EGSM frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-84
EGSM channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-85
DCS1800 frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-88
DCS1800 frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-88
DCS1800 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-89
PCS1900 frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-108
PCS1900 frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-108
PCS1900 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-109
Chapter 2: BSS General Description

Base station system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
BSS purpose and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
BSS network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Typical BSS layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
BSC description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
BSC purpose and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
BSC to MSC interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Digital switching matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Terrestrial circuit device management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
BSC capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
BTS description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
BTS purpose and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Frequency reuse plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
RF coverage areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
iv 68P02901W01-S
Jul 2008
Antenna systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Transcoder description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Transcoder purpose and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Remote transcoder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Transcoding location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
BSS site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Introduction to BSS site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
BSS configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Flexibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
BSS maximum capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
BTS cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
BSSC cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
BSS/MSC configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
BSS with more than one BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Flexible neighbor cell processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Basic configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Topology model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Star (spoke) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Open-ended daisy chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Daisy chain with fork and return loop to chain . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Daisy chain with fork and return loop to BSC . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Drop and insert BTS site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
BSS standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Introduction to BSS standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Protocol layering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
A interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Air interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Lb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Radio system and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Introduction to radio system and control functions . . . . . . . . . . . . . . . . . . . . . 2-23
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Dynamic power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Discontinuous transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Discontinuous reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Timing adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Frequency synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Intelligent Multi Layer Resource Management (IMRM) . . . . . . . . . . . . . . . . . . . 2-26
Cell system radio channel reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Introduction to cell system radio channel reuse . . . . . . . . . . . . . . . . . . . . . . . 2-27
9-site reuse pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
3-site 3-sector reuse pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
4-site reuse pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Cell pattern reuse comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
BSS redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Introduction to BSS redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
BSS fault management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Failed modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
RF carrier redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
Interface redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
BTS redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
BSC redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
RXCDR redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
General packet radio service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
68P02901W01-S v
Jul 2008
Contents
Introduction to GPRS and EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Packet control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
GSN complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
GSM/(E)GPRS network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Overview of VersaTRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Packet control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Introduction to the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
PCU information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
PCU overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
PCU summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
PCU environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
PCU features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
List of PCU features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Point-to-point (E)GPRS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
(E)GPRS radio channel allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Medium access control mode - dynamic allocation . . . . . . . . . . . . . . . . . . . . . . 2-44
Extended Dynamic Allocation Medium Access Mode (EDMAC) . . . . . . . . . . . . . . . 2-44
Support of MS classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Coding schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Dynamic adaptation of coding schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Two-phase packet access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
One phase access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Enhanced one phase access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Frequency hopping of PDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
Power control uplink/downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
PCU load balancing and sharing (Gb and BTS). . . . . . . . . . . . . . . . . . . . . . . . 2-49
MS flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
PCU description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
PCU purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
PCU management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
PCU devices and equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
PCU architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Introduction to PCU architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
MPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Bridge (PPB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
DPROC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
U-DPROC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
E1 PMC module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
Fault tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Introduction to (E)GPRS BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61
PCU system and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
System and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
PCU processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65
Chapter 3: OMC-R Overview

OMC-R network management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Event/alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
The OMC-R in GSM network management architecture . . . . . . . . . . . . . . . . . . . . . 3-5
Network hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
vi 68P02901W01-S
Jul 2008
Network levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

The OMC-R system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
OMC-R system configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
The OMC-R user interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
User interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
GUI interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
OMC-R front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
The command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
UNIX-based utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
The OMC-R in a GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
A typical GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
OMC-R functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
RXCDR functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
BSS and RXCDR configuration (SITES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
BSS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
RXCDR configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
NE device containment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Containment relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
CELL resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
BTS hardware relating to traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
BTS software relating to traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
DRI/RTF groups - transceiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Transceiving functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Types of RTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Redundancy (within a cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
CELL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Logical devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Handover control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Links in a GSM network: overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Information on links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
SITE link requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Link types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Physical links - PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Physical link requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
PATH devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Logical links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Introduction to links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Types of link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
OMC-R connection to the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Transferring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
X.21 connection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Operation and Maintenance of a BSS or RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Simplified network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Operation and Maintenance information flow between OMC-R and NEs . . . . . . . . . . . . . 3-34
Summary of information flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Information flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
OMC-R system configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Motorola OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Typical hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Communications handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Communications software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
68P02901W01-S vii
Jul 2008
Contents
Packet switch or multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Packet switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Operation and Maintenance network traffic capacity . . . . . . . . . . . . . . . . . . . . . . 3-39
Peak traffic capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
OMC-R system processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Introduction to the system processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
System processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
OMC-R GSM application software: overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
OMC-R processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
System processor software elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
UNIX: Solaris 10 operating system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Tools and applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
The OMC-R database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
RDBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Database schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Database size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Applications and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
The OMC-R GUI configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
Running the OMC-R GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
The network file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
LAN configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
Other configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
GUI processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Server client relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
The network status summary feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
The CM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Description of the CM MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Populating the CM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
GUI client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Software configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Hardware features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Night concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Network status summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Map process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
The EM proxy process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
GUI clients and servers: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Client or server system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
GUI servers and GUI clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Network maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Different maps available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60
Map modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60
Map configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60
The map display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Map backgrounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Map links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
State changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
viii 68P02901W01-S
Jul 2008
How administrative and operational state changes work. . . . . . . . . . . . . . . . . . . . . 3-64

State changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
How alarms work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Alarm icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
Map configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Introduction to the CM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Two object groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
MapNode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
MapLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Configuration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Configuration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Hardware devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Software functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Logical links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Radio frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
ProxyCell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
UserProfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Automatically created network objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Automatically created map display objects. . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
Periodic Supervision of Accessibility (PSA). . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
Definition of PSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
PSA failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
Disk usage exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
System processor partition full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
Introduction to DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
DataGen configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Off-line MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Feature Capacity Licensing and Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87
Chapter 4: BSS Software Release Features

BSS software release 1.1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Release 1.1.1.0 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Reason for this release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
68P02901W01-S ix
Jul 2008
Contents
Important information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

BSS software release 1.3.0.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Release 1.3.0.x features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
BSS software release GSR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
GSR2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
GSR3 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
GSR4 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
BSS software release GSR4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
GSR4.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
GSR5 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
BSS overload protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
SMS CB upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Receive antenna VSWR and radio loopback test . . . . . . . . . . . . . . . . . . . . . . . 4-46
Dynamic allocation of RXCDR-BSC circuits . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Enhanced XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Horizonmicro2/Horizoncompact2 generic BTS software . . . . . . . . . . . . . . . . . . . 4-47
Code corruption immune design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Propagate TSC changes to all timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Single BCCH for dual band cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Support for E1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Enhanced power outage recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Improved MTL load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
BTS concentration resource optimization for handovers . . . . . . . . . . . . . . . . . . . 4-49
Handover parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Per neighbor area for adaptive handovers . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Optimized power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Support for the MTL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Support for frame erasure rate statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
BTS concentration call priority handling . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
GPROC function preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Parallel cage enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Enhanced MMI link device warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
BSS software release GSR5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
GSR5.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
BSS processing of suspend message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
CS3, CS4, and 32 kbps TRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53
GPROC fast reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Unequip of TCU/CTU cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
850 MHz frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
1900 MHz Horizonmacro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Single BCCH for dual band cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
GSR6 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
Enhanced circuit error rate monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
x 68P02901W01-S
Jul 2008
Multiple GPRS carriers per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58

Enhanced GDP provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
Call downgrade on CIC capability mismatch . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
GPRS PCU recovery on last GSL failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Network Controlled (NC1 and NC2) cell reselection . . . . . . . . . . . . . . . . . . . . 4-62
Location services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
Basic MPROC redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65
Enhanced BSC capacity phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
Improved MPROC software failures detection and recovery . . . . . . . . . . . . . . . . . 4-67
Inter Radio Access Technology (RAT) 2G to 3G handover . . . . . . . . . . . . . . . . . . 4-67
Clean install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
GPRS interleaving TBFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Link utilization improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
Advanced load management for EGSM carriers . . . . . . . . . . . . . . . . . . . . . . . 4-71
Enhanced GPRS One Phase Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Remove support for collocated BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Compress all BTS objects at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
BSS software release GSR6 (Horizon II) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
GSR6 (Horizon II) features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Horizon II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Enhanced two uplink timeslots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
GSR7 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
PCU 3X capacity increase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
GPROC3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
Enhanced scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Performance enhancements under load . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Seamless cell reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
DSW/DSWX backward compatible with KSW/KSWX . . . . . . . . . . . . . . . . . . . . . 4-85
Adaptive Multi-Rate (AMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
Move PCU and BTS objects from BSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
GPRS PBCCH/PCCCH support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-91
Enhanced GPRS (EGPRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
BSS software release GSR7 (GSM Half Rate) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
GSR7 (GSM Half Rate) features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
Stop BTS transmission after the last RSL fails . . . . . . . . . . . . . . . . . . . . . . . . 4-96
GPRS resources (PDTCH) configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96
Out_inter_bss_ho statistical counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97
BSS support for full Cell ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98
BSC Reset Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98
Intelligent Multi Layer Resource Management (IMRM) . . . . . . . . . . . . . . . . . . . 4-100
GPRS Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-101
New GPRS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103
GPRS Statistics and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104
Network Assisted Cell Change (NACC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104
Enhanced 2G-3G handover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105
VersaTRAU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106
Support of QoS Release 4 (R4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-107
Support for Horizon II Mini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108
GPRS R4 Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109
Enhanced Multi Level Precedence and Preemption (eMLPP) service . . . . . . . . . . . . 4-109
Support for Half Rate on GDP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
Fast Call Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
RSL Congestion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111
Increased SDCCH capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111
Improved Timeslot Sharing (ITS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111
68P02901W01-S xi
Jul 2008
Contents

Enhanced BSC Capacity Using DSW2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114
Support for 96 Multiple Serial Interface (MSI) at BSC . . . . . . . . . . . . . . . . . . . . 4-114
RSL dimensioning statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-115
Increase the PCU database capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-115
BSC Overload Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-115
TDM Availability Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116
Software patching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-117
PCU Software Upgrade without BSC Outage . . . . . . . . . . . . . . . . . . . . . . . . 4-118
New drop call rate classes statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-118
Support for Horizon II Micro, Extended Range for Electronic IDs of Cabinet Power Supplies,
Software support for High power Horizon II Micro . . . . . . . . . . . . . . . . . . . . . 4-119
PCU high bandwidth interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-120
4-Branch receive diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-121
Quality of Service PhaseII Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-122
Support of RESUME at intra-BSC level . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123
Software support for High Bandwidth and/or existing E1 BSC/PCU interconnect . . . . . . 4-124
LCF Memory saving to prolong the life of existing GPROC2 . . . . . . . . . . . . . . . . . 4-125
Increase the throughput of PRP with the PCU . . . . . . . . . . . . . . . . . . . . . . . . 4-126
BSS LAN Packing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-126
HSP MTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-127
BSP CPU utilization reduction for higher call handling capacity . . . . . . . . . . . . . . . 4-127
Addition of new PCU hardware to increase GPRS capacity . . . . . . . . . . . . . . . . . 4-128
Increased Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-129
Support of Incell as an Optional Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-129
CTU2D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-130
TD-SCDMA and GSM interworking feature . . . . . . . . . . . . . . . . . . . . . . . . . 4-131
Support TFP and TFA in MTP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-131
Cell OOS Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-132
CTU2D Asymmetric EDGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-132
UL Retransmission Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-133
BSS software release GSR9 FP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
Support the display of GPRS resource allocation per PCU . . . . . . . . . . . . . . . . . . 4-134
Support the usage of idle TCH for packet burst traffic . . . . . . . . . . . . . . . . . . . . 4-135
Support a switch and additional stats for AGCH flow control . . . . . . . . . . . . . . . . 4-135
Add paging discard stats for RCC feature related link . . . . . . . . . . . . . . . . . . . . 4-136
Support for Release 6 based Extended Uplink TBF mode . . . . . . . . . . . . . . . . . . 4-136
Support for the Extended Dynamic MAC mode at the air interface (EDMAC) . . . . . . . . 4-137
Quality of Service Phase II Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-138
Chapter 5: OMC-R Software Release Features

OMC-R software release 1.1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Additional features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
xii 68P02901W01-S
Jul 2008

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Further features of OMC-R software release 1.4.0.1 . . . . . . . . . . . . . . . . . . . . . 5-23
Release 1.4.0.6 feature support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Release 1.4.0.7 feature support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
OMC-R software release GSR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
GSR2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
GSR3 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
GSR4 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
OMC-R software release GSR4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
GSR4.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
GSR5 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
BTS concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Optimized power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Propagation after audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
EAS relay MMI control for InCell, M-Cell, and Horizon . . . . . . . . . . . . . . . . . . . 5-37
Intelligent congestion relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Adaptive handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Support of BCCH and SDCCH for EGSM. . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Coincident multiband boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Reporting the results of alarms recovery action . . . . . . . . . . . . . . . . . . . . . . . 5-38
Flexible neighbor cell processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Dynamic trace call flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Proxy cell autocreation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Proxy cell import/export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Completion of OMC-R support for Horizonmacro . . . . . . . . . . . . . . . . . . . . . . 5-40
Q3 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
DRI and combiner operability improvement . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
NHA support maximum size GSM OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Integration of NHA with OMC-R EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Bay level cal default data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Cell parameter import or export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Applix 4.41 upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
System upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Enhanced SDCCH to TCH assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Changing NE ID of Assoc_BSSs or Assoc_RXCDRs . . . . . . . . . . . . . . . . . . . . . . 5-42
68P02901W01-S xiii
Jul 2008
Contents
OMC-R GUI usability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43

Datagen support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
Increased OMC-R neighbor statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
OMC-R GUI support for PCU device object . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
Network expansion batch capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
Increased capacity OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
Increasing maximum number of trunks per BSC . . . . . . . . . . . . . . . . . . . . . . . 5-45
Expansion or de-expansion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Vanguard software upgrade support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Support for Vanguard 6455 router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Removal of the clear stats command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
PCU alarms detected by HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
OMC-R software release GSR5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
GSR5.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
WebMMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
CS3, CS4, and 32 kbps TRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
GPROC fast reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
Unequip of TCU/CTU cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
GSR6 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
Geographic command partitioning and region support. . . . . . . . . . . . . . . . . . . . 5-50
Enhanced circuit error rate monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
OMC-R GUI usability for large network support . . . . . . . . . . . . . . . . . . . . . . . 5-53
Enable cyclic neighbor statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
Online network expansion - phase 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
Cell Xchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
OMC-R software release GSR6 (Horizon II) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
GSR6 (Horizon II) features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
Support for new UNIX server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
GSR7 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
Cell Xchange - BSS support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
Network Expansion - Phase 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
Performance Enhancements for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
Web Access Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
OMC-R software release GSR7 (GSM Half Rate) . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
GSR7 (GSM Half Rate) features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
User Barred Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
Intelligent Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
120K TCH OMC - Capacity Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
Upgrade OS to Solaris 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
Channel and Circuit Status (CACS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
Feature Capacity Licensing and Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
Implementation of Secure Services on Solaris based O and M products . . . . . . . . . . . 5-71
BSS User Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
3GPP Release 6 Performance Management IRP 2G . . . . . . . . . . . . . . . . . . . . . 5-73
Chapter 6: Glossary of Technical Terms

Glossary of technical terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
A Interface - AUTO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
B Interface - Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
C - CW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
D Interface - DYNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
E - EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
xiv 68P02901W01-S
Jul 2008
Contents
F Interface - Full Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

G Interface - GWY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
H Interface - Hyperframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32
I - IWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
k - KW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
L1 - LV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
M - MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41
NACK - nW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47
O - Overlap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
PA - PXPDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
QA- Quiesent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-58
R - RXU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59
S7- SYSGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-64
T -TxBPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-72
U - UUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77
V - VTX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-79
W - WWW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81
X - X Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81
ZC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82
68P02901W01-S xv
Jul 2008
Contents
xvi 68P02901W01-S
Jul 2008
List
of
Figures
List of Figures

Figure 1-1: GSM equipment architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Figure 1-2: Typical GSM system layout - Dual BSS system . . . . . . . . . . . . . . . . . . . 1-5
Figure 1-3: Four cell frequency reuse pattern . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Figure 1-4: A interface protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Figure 1-5: Handover control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Figure 1-6: Database list summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Figure 1-7: HLR configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Figure 1-8: Authentication center configuration . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
Figure 1-9: Visitor location register configuration . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Figure 1-10: MS to PSTN subscriber call . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
Figure 1-11: PSTN subscriber to MS call . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Figure 1-12: MS to MS call (same PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Figure 1-13: MS to MS call (different PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
Figure 1-14: MS to MS call (different PLMN/different country) . . . . . . . . . . . . . . . . . 1-37
Figure 1-15: BSS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
Figure 1-16: GSM functional layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56
Figure 1-17: OSI layers - main protocol relationships . . . . . . . . . . . . . . . . . . . . . . 1-65
Figure 1-18: Network protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-66
Figure 1-19: GSM850 frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-70
Figure 1-20: GSM900 frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-77
Figure 1-21: EGSM frequency range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-84
Figure 1-22: DCS1800 frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-88
Figure 1-23: PCS1900 frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-108
Figure 2-1: Dual BSS system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Figure 2-2: Multiple BTS sites per BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Figure 2-3: Topology model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Figure 2-4: Measurements made for handovers . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Figure 2-5: 9-site reuse pattern cellular system . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Figure 2-6: 3-site (sectored) cellular system . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Figure 2-7: The (E)GPRS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Figure 2-8: (E)GPRS network architecture showing the PCU and GSN complex . . . . . . . . . 2-36
Figure 2-9: PDTCHs to Backhaul Mapping on a 64K carrier . . . . . . . . . . . . . . . . . . . 2-38
Figure 2-10: PCU within the GSM/(E)GPRS network. . . . . . . . . . . . . . . . . . . . . . . 2-41
Figure 2-11: PCU managed from the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
Figure 2-12: Device and equipment hierarchy for the PCU device . . . . . . . . . . . . . . . . 2-53
Figure 2-13: Deployment Diagram 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Figure 2-14: Deployment diagram 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Figure 2-15: Deployment diagram 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Figure 2-16: BSS functional blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Figure 2-17: Data and signaling paths between the PCU and MS . . . . . . . . . . . . . . . . 2-61
Figure 2-18: PCU to BSC connection utilizing four E1 LINKS . . . . . . . . . . . . . . . . . . 2-62
Figure 2-19: Data and signaling paths between the PCU and SGSN . . . . . . . . . . . . . . . 2-63
Figure 3-1: GSM network management architecture . . . . . . . . . . . . . . . . . . . . . . 3-5
Figure 3-2: Typical hardware architecture of OMC-R SunFire/Netra system. . . . . . . . . . . 3-8
Figure 3-3: The OMC-R GUI front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
68P02901W01-S xvii
Jul 2008
List of Figures
Figure 3-4: The Expert OMC-R GUI front panel . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Figure 3-5: The OMC-R in a GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Figure 3-6: The naming convention and physical links of BSS . . . . . . . . . . . . . . . . . . 3-18
Figure 3-7: Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Figure 3-8: Example of path settings within a BSS. . . . . . . . . . . . . . . . . . . . . . . . 3-27
Figure 3-9: The different logical links in a GSM network . . . . . . . . . . . . . . . . . . . . 3-30
Figure 3-10: Communication between the OMC-R and other network elements . . . . . . . . . 3-32
Figure 3-11: Simplified GSM network showing devices and links at BSSs . . . . . . . . . . . . 3-33
Figure 3-12: Information flow between the OMC-R and BSSs . . . . . . . . . . . . . . . . . . 3-34
Figure 3-13: An example Motorola OMC-R system configuration . . . . . . . . . . . . . . . . 3-36
Figure 3-14: Example Packet switch or multiplexer connections . . . . . . . . . . . . . . . . . 3-38
Figure 3-15: Scalable OMC-R high-end system processor . . . . . . . . . . . . . . . . . . . . 3-40
Figure 3-16: System processor software configuration. . . . . . . . . . . . . . . . . . . . . . 3-42
Figure 3-17: OMC-R GSM (System processor) software components . . . . . . . . . . . . . . 3-43
Figure 3-18: OMC-R database - database schema breakdown . . . . . . . . . . . . . . . . . . 3-47
Figure 3-19: Maps icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Figure 3-20: The network status summary options on the GUI front panel. . . . . . . . . . . . 3-52
Figure 3-21: GUI client hardware and software configuration . . . . . . . . . . . . . . . . . . 3-54
Figure 3-22: Night concentration configuration . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Figure 3-23: Map processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Figure 3-24: Map icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
Figure 3-25: State changes on the map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
Figure 3-26: How alarms change on the map . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Figure 3-27: The CM MIB showing the different groups of managed objects . . . . . . . . . . 3-69
Figure 3-28: The containment relationship for the graphic objects . . . . . . . . . . . . . . . 3-71
Figure 3-29: The containment relationship for the configuration objects . . . . . . . . . . . . 3-74
Figure 3-30: DataGen in a GSM environment . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
Figure 3-31: DataGen main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Figure 3-32: Off-line MIB front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86
Figure 4-1: Example of Interleaving DL TBFs . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
Figure 4-2: Multi-slot class 6 uplink or downlink bias timeslot allocation . . . . . . . . . . . . 4-77
Figure 4-3: Multi-slot class 10 uplink/downlink bias timeslot allocation . . . . . . . . . . . . . 4-78
Figure 4-4: BSS configuration with 3 PCUs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
Figure 5-1: GSM OMC-R hardware configuration for up to 45 k TCH . . . . . . . . . . . . . . 5-57
Figure 5-2: GSM OMC-R hardware configuration for up to 60K TCH . . . . . . . . . . . . . . 5-58
xviii 68P02901W01-S
Jul 2008
List
of
Tables
List of Tables

Table 1-1: OMC-R functions and GSM and ITU-TSS references . . . . . . . . . . . . . . . . . 1-8
Table 1-2: OMC configurations (maximum values) . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Table 1-3: OMC-R/X.25 capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Table 1-4: Receiver specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Table 1-5: BSS software functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Table 1-6: GSM interface summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Table 1-7: Network element signaling links . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Table 1-8: GSM Frequency types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-69
Table 1-9: GSM850 channels 128 to 130 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-70
Table 1-10: GSM850 channels 131 to 140 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71
Table 1-22: PGSM channels 1 to 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-78
Table 1-31: PGSM channels 91 to 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-82
Table 1-32: PGSM channels 101 to 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-83
Table 1-35: EGSM channels 975 to 984 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-85
Table 1-38: EGSM channels 1005 to 1014 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-87
Table 1-39: EGSM channels 1015 to 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-87
Table 1-40: DCS1800 channels 512 to 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-89
68P02901W01-S xix
Jul 2008
List of Tables

Table 1-78: PCS 1900 channels 512 to 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-109
xx 68P02901W01-S
Jul 2008
System Information: GSM Overview List of Tables

Table 2-1: BSC maximum capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Table 2-2: BTS - BSC main and alternate paths (fork with return loop) . . . . . . . . . . . . . 2-17
Table 2-3: BTS - BSC main and alternate paths (chain with return loop) . . . . . . . . . . . . . 2-18
Table 2-4: Sector reuse pattern features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Table 2-5: Failed module situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Table 2-6: Cell reselection modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Table 2-7: MS multi-slot class mapping for all (E)GPRS multi-slot classes . . . . . . . . . . . . 2-45
Table 2-8: GPRS coding scheme characteristics . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Table 2-9: EGPRS Coding Schemes and Throughput . . . . . . . . . . . . . . . . . . . . . . . 2-46
Table 3-1: OMC-R specifications (maximum values) . . . . . . . . . . . . . . . . . . . . . . . 3-9
Table 3-2: Software requirements (Single Platform Processor) . . . . . . . . . . . . . . . . . 3-10
Table 3-3: Front panel icon description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Table 3-4: Scalable OMC-R configurations (maximum values) . . . . . . . . . . . . . . . . . . 3-41
Table 3-5: GUI processor hardware specifications . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Table 3-6: GUI processor software specifications . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Table 3-7: Alarm icon colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
Table 4-1: Release 1.1.1.0 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Table 4-2: Software release 1.1.2.0 features . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Table 4-11: Release 1.3.0.x features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Table 4-13: Release1.4.0.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Table 4-17: Release GSR2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Table 4-20: Release GSR4.1 features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Table 4-24: Multiple GPRS carriers configured for performance (Default) . . . . . . . . . . . . 4-58
Table 4-25: Operator specified options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
Table 4-26: Cell reselection modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63
Table 4-27: Release GSR6 (Horizon II) features . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Table 4-28: CTU and CTU2 output power capabilities . . . . . . . . . . . . . . . . . . . . . . 4-75
Table 4-29: MS multi-slot class mapping for all GPRS multi-slot classes . . . . . . . . . . . . . 4-77
Table 4-31: GPROC3 comparison with GPROC2 . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
Table 4-32: PBCCH/PCCCH packet logical channels . . . . . . . . . . . . . . . . . . . . . . . 4-92
Table 4-33: Release GSR7 (GSM Half Rate) features. . . . . . . . . . . . . . . . . . . . . . . 4-94
Table 4-35: Default Band Weightings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100
Table 4-37: PRP capacity in mode 1 and mode 2 . . . . . . . . . . . . . . . . . . . . . . . . . 4-126
Table 4-38: Release GSR9 FP1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
68P02901W01-S xxi
Jul 2008
List of Tables

Table 5-18: Release GSR6 (Horizon II) features . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
Table 5-20: Release GSR7 (GSM Half Rate) features. . . . . . . . . . . . . . . . . . . . . . . 5-63
Table 5-21: OMC-R features for GSR8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
Table 5-22: OMC-R features for GSR9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
xxii 68P02901W01-S
Jul 2008
About
This
Manual
System Information: GSM Overview

What is covered in 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+, Horizon II
micro, Horizoncompact2, M-Cellaccess, Horizoncompact, Horizonmicro, Horizonmacro, and
Horizon II macro. The manual is an overview of the Global System for Mobile Communications
(GSM) as implemented by Motorola, and includes:
Chapter 1, Introduction to Motorola GSM.
Chapter 2, BSS general description.
Chapter 3, OMC-R overview.
Chapter 4, BSS software release features.
Chapter 5, OMC-R software release features.
Chapter 6, Glossary of terms, acronyms, and abbreviations.
The information is intended for use by GSM Operation and Maintenance staff.
68P02901W01-S 1
Jul 2008
Revision history
Revision history

The following sections show the revision status of this document.
Version information
The following table lists the supported versions of this manual in order of issue:
Issue Date of issue Remarks

Q Sep 2004 Issue Q - GSM Software Release 7 Half Rate
R Nov 2006 Issue R - GSM Software Release 8 GMR02
S Apr 2008 Issue S - GSM Software Release 9
S Jul 2008 Issue S - GSM Software Release 9 FP1
Resolution of Service Requests
The following Service Requests are resolved in this document:
Service
CMBP Number Remarks
Request
NA NA NA
Incorporation of Change Notices
The following Change Notices (CN) are incorporated in this document:
CN Date CN Number Title

NA NA NA
2 68P02901W01-S
Jul 2008
General information
General information

Purpose
Motorola documents are intended to instruct and assist personnel in the operation, installation,
and maintenance of the Motorola equipment and ancillary devices. It is recommended that all
personnel engaged in such activities be properly trained by Motorola.
Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
NOTE
If this document was obtained when attending a Motorola training course, it is not
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then Motorola automatically supplies corrections and posts on the Motorola
customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.
68P02901W01-S 3
Jul 2008
Text conventions
Text conventions
The following conventions are used in the Motorola documents to represent keyboard input
text, screen output text, and special key sequences.
Input
Characters typed in at the keyboard are shown like this sentence.

Items of interest within a command appear like this sentence.
Output
Messages, prompts, file listings, directories, utilities, and environmental

variables that appear on the screen are shown like this sentence.
Items of interest within a screen display appear like this sentence.
Special key sequences
Special key sequences are represented as follows:
CTRL-c or CTRL+C Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or Press the Ctrl, Shift, and C keys at the same time.
CTRL+SHIFT+C
ALT-f or ALT+F Press the Alt and F keys at the same time.
ALT+SHIFT+F11 Press the Alt, Shift and F11 keys at the same time.
Press the pipe symbol key.
RETURN or ENTER Press the Return or Enter key.
4 68P02901W01-S
Jul 2008
Contacting Motorola
Contacting Motorola

Motorola appreciates feedback from the users of our documents.
24hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Office.
Questions and comments
Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
The document type
The document title, part number, and revision character
The page number with the error
A detailed description of the error and if possible the proposed solution
68P02901W01-S 5
Jul 2008
Security advice
Security advice

Motorola systems and equipment provide security parameters that the operator configures
based on their particular operating environment. Motorola recommends setting and using
these parameters following industry recognized security practices. Consider protecting the
confidentiality, integrity, and availability of information and assets. Assets include the ability
to communicate, information about the nature of the communications, and information about
the parties involved.
In certain instances, Motorola makes specific recommendations regarding security practices.

The implementation of these recommendations and final responsibility for the security of the
system lies with the operator of the system.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information, from the menu located to the left of the
Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local
Motorola Office.
6 68P02901W01-S
Jul 2008
Warnings, cautions, and notes
Warnings, cautions, and notes

The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
WARNING
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
CAUTION
Caution text and consequence for not following the instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or provides additional

information to help the reader understand a topic or concept. A note has the following format:
NOTE
Note text.
68P02901W01-S 7
Jul 2008
Safety
Safety

General safety
The following general safety guidelines apply to Motorola equipment:

The power jack and mating plug of the power cable must meet International
Electrotechnical Commission (IEC) safety standards.
NOTE
Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.
Power down or unplug the equipment before servicing.
Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

Use precautions to prevent damage.
Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
Council recommendation of 12 July 1999 on the limitation of exposure of the general

public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national
regulations.
Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on
the minimum health and safety requirements regarding the exposure of workers to the
risks arising from physical agents (electromagnetic fields) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
8 68P02901W01-S
Jul 2008
Caring for the environment
Caring for the environment

The following information describes national or regional requirements for the disposal of
Motorola supplied equipment and for the approved disposal of surplus packaging.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Office.
In EU countries
The following information is provided to enable regulatory compliance with the European
Union (EU) directives and any amendments to these directives when using Motorola equipment
in EU countries.
Disposal of Motorola equipment
European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction
with a recycling partner ensures that equipment is collected and recycled according to the
requirements of EU environmental law.
Disposal of surplus packaging
European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste
Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients
responsibility to ensure that packaging materials are collected and recycled according to the
requirements of EU environmental law.
In non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance
with national and regional regulations.
68P02901W01-S 9
Jul 2008
CMM labeling and disclosure table
CMM labeling and disclosure table

The Peoples Republic of China requires that our products comply with China Management
Methods (CMM) environmental regulations. (China Management Methods refers to the
regulation Management Methods for Controlling Pollution by Electronic Information Products.)
Two items are used to demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.

Logo 1 means the product contains no substances in excess of the maximum concentration
value for materials identified in the China Management Methods regulation.
Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identified in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years. The example shown
uses 50 years.
Logo 1 Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic
and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)
will not leak or mutate causing environmental pollution or bodily injury from the use of the
EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain
field-replaceable parts, such as battery modules, can have a different EFUP and are marked
separately.
The Disclosure table is intended only to communicate compliance with China requirements.
It is not intended to communicate compliance with EU RoHS or any other environmental
requirements.
10 68P02901W01-S
Jul 2008
Motorola document set
Motorola document set

The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
Ordering documents and CD-ROMs
With internet access available, to view, download, or order documents (original or revised), visit
the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or
contact your Motorola account representative.
Without internet access available, order hard-copy documents or CD-ROMs from your Motorola
Local Office or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.
Document banner definitions
A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY UNDER DEVELOPMENT.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
68P02901W01-S 11
Jul 2008
Data encryption
12 68P02901W01-S
Jul 2008
Chapter
Introduction to Motorola GSM

This chapter provides a high-level overview of the Global System for Mobile communications
(GSM) that includes GSM850, GSM900, Extended GSM (EGSM), Digital Communications System
1800 (DCS1800) and Personal Communications System 1900 (PCS1900) digital cellular systems.
The following topics are described in this chapter:

Overview of the Motorola GSM system on page 1-2.
Unique features of Motorola GSM on page 1-6.
Motorola network specifications on page 1-8.
Security management on page 1-13.
Mobile station on page 1-14.
GSM network specifications and recommendations on page 1-17.
GSM network elements on page 1-20.
Operation and Maintenance center on page 1-22.
Mobile services switching center on page 1-23.
Base station system on page 1-38.
GSM subsystems (non-network elements) on page 1-44.
GSM system features on page 1-46.
E1 links on page 1-53.
Standardized interfaces on page 1-54.
Network protocols on page 1-64.
GSM frequencies and channels on page 1-69.
GSM frequencies and channels on page 1-69.
PCS1900 frequencies and channels on page 1-108.
68P02901W01-S 1-1
Jul 2008
Overview of the Motorola GSM system Chapter 1: Introduction to Motorola GSM
Overview of the Motorola GSM system

The Motorola GSM system
The Motorola GSM cellular system provides radio coverage for communications with GSM
subscribers in a defined area. Its principle role is to support signaling and traffic channels for
Mobile Stations (MSs) across the Public Land Mobile Network (PLMN).
Network element overview
The GSM network incorporates a number of network elements to support mobile telephones and
other mobile equipment, known collectively as Mobile Stations, or MSs. These elements form
the major components of the GSM network.
Network Management Center
The Network Management Center (NMC) administers the entire cellular network to provide
Operation and Maintenance at the network level. Figure 1-1 shows the NMC relationship
with the other network elements.
Operation and Maintenance Center-Radio
The Operation and Maintenance Center-Radio (OMC-R) is a regional site, which controls and
monitors the daily operation of network elements within its region and the quality of service
provided by the network. Figure 1-1 shows the OMC-R relationship with the other network
elements.
Mobile services Switching Center
The Mobile services Switching Center (MSC) is a telephone switching office for handling calls
to and from the MSs within a defined geographical area. The MSC also provides the interface
between the cellular network and the ordinary land-based Public Switched Telephone Network
(PSTN). The MSC allows the GSM cellular system to function as an extension of the PSTN. It
also allows the GSM network to interface to other PLMNs. There can be a number of MSCs
within the region controlled by an OMC. Figure 1-1 shows the MSC relationship with the other
network elements.
1-2 68P02901W01-S
Jul 2008
System Information: GSM Overview Network element overview
Location registers
Three Location Registers (LR) are collocated with the MSC. These elements are
database-oriented processing nodes that manage subscriber data and keep track of the location
of the MS as it roams around the network. For detailed information regarding the LRs, see
Introduction to the MSC on page 1-23 in this chapter.
The following LRs are present in the GSM network:

Equipment Identity Register (EIR)
Home Location Register (HLR)
Visitor Location Register (VLR)
Base Station System
The Base Station System (BSS) is the fixed end of the radio interface that provides control
and radio coverage functions for one or more cells and their associated MSs. BSS is the link
between the MS and the MSC. The BSS comprises one or more Base Transceiver Stations
(BTSs). Each BTS contains radio components that communicate with MSs in a given area and a
Base Site Controller (BSC). The BSC supports call processing functions and the interfaces to
the MSC. Digital radio techniques are used for the radio communications link, known as the
Air Interface, between the BSS and the MS.
The BSS comprises:

Base Station Controller (BSC)
The BSC controls one or more Base Transceiver Stations (BTSs) and acts as a digital
processing interface between the BTS and the MSC. Detailed information regarding the
BSC can be found in BSC description on page 2-5 of this manual.
Base Transceiver Station (BTS)
The BTS contains the radio components that provide the interface to Mobile Stations for
one or more coverage areas or cells. Detailed information regarding the BTS can be found
in BTS description on page 2-7 of this manual.
Full-rate Transcoder (XCDR) and Remote Transcoder (RXCDR)
The Full-rate Transcoder (XCDR) is the digital signal processing equipment required to
perform GSM-defined speech encoding and decoding. In terms of data transmission, the
speech transcoder interfaces the 64 kbps PCM in the land network to the 13 kbps vocoder
format used on the Air Interface.
The Remote Transcoder (RXCDR) is used when the transcoding is performed at a site away
from the BSC, which is at or near the MSC. This enables 4:1 multiplexing with GSM or
8:1 with AMR half rate. The transcoded data for four logical channels is combined onto
one 64 kbps link. Thus, reducing the number of links required for interconnection to
the BSCs. Detailed information regarding the XCDR and RXCDR can be found in Base
station system on page 2-2 of this manual.
68P02901W01-S 1-3
Jul 2008
Network element overview Chapter 1: Introduction to Motorola GSM
Packet Control Unit (PCU)
The PCU is an interface adaptor handler unit that permits the Motorola GSM facility the
access to the packet network. As such, the PCU needs interfaces with the BSC on the
GSM side, and the SGSN on the packet network side. The PCU manages the packet radio
interface and also enables the interface from the BSS to the SGSN. The existing OMC-R
manages the PCU. Detailed information regarding the PCU can be found in General
packet radio service on page 2-33 of this manual.
The Motorola GSM equipment architecture is shown in Figure 1-1 with other associated
network elements. The BSS components are shown shaded. Also shown is the GPRS network
architecture.
Figure 1-1 GSM equipment architecture

GSM EQUIPMENT GSN EQUIPMENT
MSC HLR RADIUS SER VER PDN

(NON-TRANSP ARENT
MODE)
RXCDR OMC-G
(Including Shelf
Manager)
OMC-R
BSC PCU ISS SGSN GGSN
BSSn GSN
BTSs COMMHUB
BSS2 GSNn
BSS1 GSN1
OPERA TOR SER VER

COMPLEX
- RADIUS SER VER
BILLING (OPERA TOR IS ISP ,
SYSTEM TRANSP ARENT MODE)
- DHCP SER VER
- DNS SER VER
ti-GSM-GSM equipmentarchitecture-00020-ai-sw
1-4 68P02901W01-S
Jul 2008
System Information: GSM Overview Typical GSM system
Typical GSM system
Figure 1-2 shows a typical layout of a system with two BSSs. Each BSS contains several
components to make the link between the MS and the MSC. The BSS components are described
in more detail later in this manual.
Figure 1-2 Typical GSM system layout - Dual BSS system
EIR AUC HLR EIR
MOBILE n MOBILE n
VLR VLR
MSC MSC
XCDR XCDR
EC
IWF
OMC-S
1001 101 1001 101
EC
BSS
BSC
NMC
modems to
other networks
BSS
BTS BTS
BSC
OMC-R
BTS BTS BTS BTS BTS
PSTN
and
ISDN
MS MS
ti-GSM-GSM system layout-00021-ai-sw
68P02901W01-S 1-5
Jul 2008
Unique features of Motorola GSM Chapter 1: Introduction to Motorola GSM
Unique features of Motorola GSM

Introduction to the unique features of Motorola GSM
The section describes the aspects of the GSM equipment that are unique to Motorola. See
Chapter 2 BSS General Description of this manual for a general description of the Motorola BSS.
Systems advantages
Features of Motorola systems that can be used to maximize the GSM capacity include unique
reuse patterns, sector sharing, and equipment sharing. Many of these features are ideal for the
system operator who has a limited number of radio channels for initiating system operation.
Other features take maximum advantage of these unique capabilities. For example,
synchronization is provided to allow the rapid handover in Motorola systems. It also provides
enhanced frequency hopping and flexible traffic channel allocation when a limited number of
GSM channels are available. Enhanced algorithms and techniques improve handover decisions
and minimize handover traffic loading on the system.
System planning
A computer program (using artificial intelligence techniques) for system planning assists and
provides a degree of automation for frequency planning. A plan checker feature is also included.
The system includes facilities for user interaction and user friendly (graphical) presentation of
plan results and system statistics. Future interconnection with the OMC to provide a feedback
path for performance assessment and learning is also anticipated.
Fault tolerance
Motorola network equipment is designed with inherent fault tolerance. All network elements
except the BTS are designed to be fault tolerant to any single point failure. The BTS is designed
to provide redundancy economically, as required.
1-6 68P02901W01-S
Jul 2008
System Information: GSM Overview Maintenance
Maintenance
The cost of maintenance is an issue in the operation of a cellular network, especially where cell
sites are widely separated. The Motorola equipment is of high quality and incorporates highly
tolerant engineering design and manufacturing.
Extensive board-level self-diagnostics.
An extensive variety of alarms and indicators throughout the equipment.
Self-calibrating subsystems, including PA and Receiver (Rx) sensitivity.
Circuit designs that do not require tuning and are immune to drift. (For example, direct
digital synthesis for the modulation).
Remotely and software controllable parameters, including transmitter power and cavity
frequency.
High-performance circuit and system designs that meet the GSM recommendations. (For
example, a low noise figure receiver achieving GSM intermodulation rejection and spurious
response rejection specifications).
68P02901W01-S 1-7
Jul 2008
Motorola network specifications Chapter 1: Introduction to Motorola GSM
Motorola network specifications

Introduction to Motorola network elements
The following sections provide specifications for the Motorola Network Elements (NEs) in the
GSM system. Specifications described in this section are:
OMC-R
Receiver
Transmitter
OMC-R specifications
The Motorola Operation and Maintenance Center - Radio (OMC-R) is a UNIX-based system.
Specifications and performance data are provided in the following sections.
These specifications are for the Sun scalable OMC-R platforms.
Functions of the OMC-R
The functions of the OMC-R are specified in the GSM Recommendations series. These functions
are based on ITU-TSS recommendations such as, ITU-TSS Rec. M.30. Table 1-1 shows a list of
functions together with appropriate GSM and ITU-TSS references.
Table 1-1 OMC-R functions and GSM and ITU-TSS references
Function Reference
Event and Alarm Management GSM 12.07
Fault Management GSM 12.07
Performance Management GSM 12.04 and 12.07 (based on ITU-TSS
E.411, for example)
Configuration Management GSM 12.07
Security Management GSM 12.03
OMC-R Man Machine Interface (MMI) and ITU-TSS M.251 [44], and Z.301 to Z.337
MML [97 to 114]
Safety and protection aspects of OMC ITU-TSS E.410
operation
1-8 68P02901W01-S
Jul 2008
System Information: GSM Overview System processor
System processor
The Netra 20, Netra 440, Sunfire 4800 or Sunfire 4900 system processors are UNIX systems.
The OMC system processor runs the OMC application software which handles all Operation
and Maintenance communication with NEs. It processes all incoming events, alarms, uploads
and downloads, and performance statistics, and the setup of remote login sessions to different
NEs. The system processor contains a database based on an INFORMIX Database Management
System. This database is configured for storing performance statistics, subscription lists, and
network and map configuration data, enabling operators to monitor incoming events and alarms.
System processor configurations
Table 1-2 provides a comparison between the Low-end (10 k TCH), Mid-range (10 k and 30 k
TCH) and High-end (45 k TCH) OMC configurations.
Table 1-2 OMC configurations (maximum values)
Feature Low-end (10 k) Mid-range (10 k) Mid-range (30 k) High-end (45 k)

RTFs 714 1430 4285 6000
NEs 64 64 120 120
Total GUI sessions 10 10 10 30
Dial-up sessions per 1 1 1 1
GUI processor
Total remote dial-up 2 2 2 2
sessions
Remote login sessions 6 6 20 30
Simultaneous 6 6 12 12
downloads
Simultaneous uploads 4 4 16 32
Sustained event rate 8 alarms 8 alarms + 12 alarms + 12 alarms +
+ 2 state 2 state changes 3 state changes 3 state changes
changes
Event burst 20 events/s 60 events/s over 60 events/s over 60 events/s
over 20 mins 20 mins 20 mins over 20 mins
A packet switch or multiplexer is required with the HSI/S card.
The system processor operates on Solaris 10 Operating System (OS).
The OMC uses an optional laser printer.
68P02901W01-S 1-9
Jul 2008
Operator workstations Chapter 1: Introduction to Motorola GSM
Operator workstations
The rest of the OMC is made up of operator workstations, and is primarily concerned with
running the OMC operator interface, the OMC Graphical User Interface (GUI). Typically,
the OMC configuration contains a single application GUI server, and several Sunblade 150
workstations as GUI clients. Alternatively, newer workstations can be connected directly as GUI
servers. Each operator workstation is a complete UNIX system.
The operator workstations run the OMC GUI software for various operations.
Optional processors
Optional processors used for Mediation Device (OSI), Remote Login, and Offline BSS
Configuration can be included in the basic OMC configuration.
OMC configuration
The OMC, a system configuration based on SunFire 4900 System Processor hardware, is
supplied in Low-end (5 k TCH), Mid-range (10 k or 30 k TCH) and High-end (45 k TCH) versions.
The hardware requirements (hard disks, CPUs, and so on) vary depending on the version and the
processor in use, as does the disk partitioning. This section describes the hardware architecture
requirements for each processor and each version, and the common software requirements.
Data communication
OMC-R uses standard X.25 communication protocols on the interfaces with other entities in the
network.
For example, the NMC-OMC interface is defined in GSM 12.01 and corresponds to the Q3 type
of interface according to ITU-TSS M.30 [1]. The OMC-R X.25 capacities are shown in Table 1-3.
Table 1-3 OMC-R/X.25 capacities
Functional area Capacity

X.25 ports 8 V.35 ports @ 64 kbps (1 not used by the
Scalable OMC).
X.25 virtual circuits per X.25 port 376 virtual circuits per X.25.
X.25 virtual circuits (aggregate) 2256 total virtual circuits.
X.25 packets per second 100 packets per second (128-byte packets),
aggregate.
Speed 100 kbps, aggregate.
1-10 68P02901W01-S
Jul 2008
System Information: GSM Overview Receiver specifications
Receiver specifications
Table 1-4 lists the specifications for the receiver.
Table 1-4 Receiver specifications
Functionality Specification
Frequency range GSM850 824 MHz to 849 MHz.
GSM900 890 MHz to 915 MHz.
Extended GSM900 880 MHz to 915 MHz.
DCS1800 1710 MHz to 1785 MHz.
PCS1900 1850 MHz to 1910 MHz.
Channel spacing 200 kHz.
Frequency stability 0.05 ppm.
RF sensitivity The Receiver minimum sensitivity levels for GSM850,
(reference sensitivity) GSM900/EGSM900, DCS1800, and PCS1900 are as follows:
CTU, DRCU, SCU, TCU Each receiver input has a minimum sensitivity of - 104
dBm complying with GSM 05.05, section 6.2, as
measured according to the method of GSM 11.20/11.21.
TCU-B Same as above, but minimum sensitivity of - 108.5 dBm.

Diversity gain (DRCU models Both branches meet performance specifications stated above.
only) 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 dBm to 7 dBm depending on
the individual system and measurement conditions.
Rx inputs perfectly correlated; diversity gain

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

Gd = 5 dB. (4 dB to 6 dB is the approximate range).
Nominal error rates There are three additional Residual Bit Error Rates (RBER):
TCH/FS Class II RBER as a function of propagation condition.
The RBER values vary depending on the RBER type and
power level.
Static BER < 0.01% for input levels up to -40 dBm.
Static BER < 0.1% for input levels > -40 dBm.
EQ50 channel BER < 3%.

This performance is maintained for a mean signal input level
between -85 dBm and -40 dBm. The static performance is
maintained for signal level up to -15 dBm for GSM850/900
and -23 dBm for DCS1800 or PCS1900.
Continued
68P02901W01-S 1-11
Jul 2008
Receiver specifications Chapter 1: Introduction to Motorola GSM
Table 1-4 Receiver specifications (Continued)

Functionality Specification
Intermodulation rejection The intermodulation rejection power levels for GSM850/900
and DCS1800 or PCS1900 are as follows:
-43 dBm minimum level for GSM850/900.
-49 dBm minimum level for DCS1800/PCS1900.

Spurious response rejection The Spurious response rejection power levels for GSM850,
GSM900, DCS1800, and PCS1900 are as follows:
-57 dBm: 9 kHz to 1 GHz
-47 dBm: 1 GHz to 12.75 GHz

Blocking (GSM850) The In-Band Blocking Signal Frequency Range is 804 MHz to
869 MHz for GSM850. Minimum power levels are as follows:
600 kHz < | - 0| < 800 kHz: -26 dBm
800 kHz < | - 0|
1-12 68P02901W01-S
Jul 2008
System Information: GSM Overview Security management
Security management

Password levels
Passwords are required to access some commands in the BSS system. There are four levels of
security in the BSS system:
Level 1 - Permits only the display of certain system elements. This level is the entrance
level after booting up.
Level 2 - Permits access to all user-visible system commands, including changing

passwords for Levels 1 and 2.
Level 3 - Permits access as for level 2, and access to the executive monitor. Two passwords
are required at this level. Only users who have purchased the level 3 password option
have access at this level.
Level 4: The omcadmin user can create a username and assign a profile to the user. The
profile defines the BSS and EMON command sets that the user can access at the BSS. The
omcadmin user can set a NE access level for a NE user account. On login to the OMC, the
user is placed at that access level.
Related commands and parameters
The chg_password command can be used to change passwords by the level 4 user.
System impact
At the OMC-R GUI, the TTY (login) and CACS interfaces support the modified chg_password
MMI command.
A password is no longer required for Level 1 access to the BSS.
68P02901W01-S 1-13
Jul 2008
Mobile station Chapter 1: Introduction to Motorola GSM
Mobile station

Introduction to mobile stations
Subscribers use a Mobile Station (MS) to access the services provided by the PLMN. MSs can
be installed in vehicles or can be portable or hand held stations. An MS can include provisions
for data communication as well as voice communication.
Different types of MSs can provide different types of data interfaces. To provide a common
model for describing these different MS configurations, GSM defines reference configurations
for MSs similar to the configurations defined for ISDN land stations.
The Mobile Station (MS) together with the Subscriber Identity Module (SIM) is defined as
the radio equipment, and a subscriber needs Man Machine Interface (MMI) to access PLMN
services. Typically, it is a mobile telephone though it can also be a mobile data communications
unit.
Mobile station components
The Mobile Station consists of the Mobile Equipment (ME) and the Subscriber Identity Module
(SIM).
Mobile equipment
The Mobile Equipment is the hardware used by the subscriber to access the network. There
are three types:
Vehicle mounted, with the antenna physically mounted on the outside of the vehicle.
Portable mobile unit, which can be hand held, but the antenna is not on the handset.
Hand portable unit, which consists of a small handset with the antenna attached to the
handset.
Subscriber Interface Module (SIM)
The SIM is a removable card that plugs into the ME. It identifies the mobile subscriber and
provides information about the service that the subscriber receives.
1-14 68P02901W01-S
Jul 2008
System Information: GSM Overview Hand portable viability
Hand portable viability
The GSM specifications for hand portable MSs aim to minimize power consumption by design
features such as:
Discontinuous Transmission (DTx)
It ensures that the hand portable transmitter is energized only when there is speech or
data traffic to transmit.
Discontinuous Reception (DRx)
It is a group paging technique that allows the hand portable to cycle to a low drain standby
mode as much as 98% of the time.
Active power control
As the hand portable gets closer to the BTS, it uses less power to transmit. Thus it saves
on battery life.
GSM hand portables also incorporate digital signal processing.
Equipment identity number
International Mobile station Equipment Identity (IMEI)
Each MS is identified by an International Mobile station Equipment Identity (IMEI) number

which is permanently stored in the Mobile Equipment. On request, the MS sends this number
over the signaling channel to the MSC. The IMEI can be used to identify MSs that are reported
stolen or operating incorrectly.
Equipment Identity Register (EIR)
The PLMN maintains a list of the allowed IMEIs, in the Equipment Identity Register (EIR),
to validate the mobile equipment.
Subscriber identification
International Mobile Subscriber Identity (IMSI)
Just as the IMEI identifies the mobile equipment, other numbers are used to identify the mobile
subscriber. Different subscriber identities are used in different phases of call setup. The
International Mobile Subscriber Identity (IMSI) is the primary identity of the subscriber within
the mobile network and is permanently assigned to that subscriber.
68P02901W01-S 1-15
Jul 2008
Subscriber identification Chapter 1: Introduction to Motorola GSM
Temporary Mobile Subscriber Identity (TMSI)
The GSM system can also assign a Temporary Mobile Subscriber Identity (TMSI). After the
subscriber's IMSI has been initialized on the system, the TMSI can be sent across the network
to identify the subscriber. The system automatically changes the TMSI at regular intervals,
thus protecting the subscriber from being identified by someone attempting to monitor the
radio channels. The TMSI is a local number and is always transmitted with the Location Area
Identification (LAI) to avoid ambiguities.
Mobile Subscriber ISDN (MSISDN)
The Mobile Subscriber ISDN (MSISDN) number is the telephone number of the MS. It is the
number a calling party dials to reach the subscriber. The land network uses this number to
route calls toward the MSC.
Home Location Register (HLR) and Visitor Location Register (VLR)
The PLMN holds subscriber data in two registers: the Home Location Register (HLR) and
the Visitor Location Register (VLR).
Subscriber Information Module (SIM)
By making a distinction between the subscriber identity and the mobile equipment identity, a
GSM PLMN can route calls and perform billing tasks based on the identity of the subscriber
rather than the mobile equipment being used. It can be done using a removable Subscriber
Information Module (SIM). A smart card is one possible implementation of a SIM module.
The following information is stored in the SIM:

IMSI - IMSI is transmitted at initialization of the mobile equipment.
TMSI - The PLMN periodically updates the TMSI.
MSISDN - MSSISDN is made up of a country code, a national code, and a subscriber

number.
Local Area Identity (LAI) - LAI identifies the current location of the subscriber.
Subscriber Authentication Key (Ki) - Ki is used to authenticate the SIM.
When the SIM is inserted in the mobile equipment, a location update procedure registers the
subscriber's new location, allowing the correct routing of incoming calls.
1-16 68P02901W01-S
Jul 2008
System Information: GSM Overview GSM network specifications and recommendations
GSM network specifications and recommendations

GSM advantages
The advantages of GSM result from the following aspects:

Standardization of the GSM specifications.
Digital nature of the GSM network.
Increased capacity and low error rates compared with analog networks.
Digital networks
GSM networks are digital and can cater for high system capacities. They are consistent with
the worldwide digitization of the telephone network, and are an extension of the Integrated
Services Digital Network (ISDN), using a digital radio interface between the cellular network
and the mobile subscriber equipment.
Increase capacity
GSM allows 25 kHz per user, that is, eight conversations per 200 kHz channel pair (a pair
comprising one transmit channel and one receive channel). Use of digital channel coding
and the modulation makes the signal resistant to interference from cells where the same
frequencies are reused (co-channel interference); a Carrier to Interference Ratio (C/I) level of
9 dB is achieved, as opposed to the 18 dB, typical with analog cellular. This allows increased
geographic reuse by permitting a reduction in the number of cells in the reuse pattern. Since
this number is directly controlled by the amount of interference, the radio transmission design
can deliver acceptable performance.
Frequency reuse
Cellular networks were developed to circumvent the needs of increasingly powerful radio
equipment and having to use a greater number of individual frequencies. With a GSM cellular
network, the mobile equipment is not more than a few kilometers from the transceiver.
Therefore, pairs of frequencies (one for transmit, one for receive), called reuse groups, can
be reused in a geographic repeat pattern across the network. Figure 1-3 shows a four-cell
frequency reuse pattern.
68P02901W01-S 1-17
Jul 2008
Audio capacity Chapter 1: Introduction to Motorola GSM
Figure 1-3 Four cell frequency reuse pattern
FRE QUENCY FRE QUENCY

RE US E RE US E
GROUP 1 GROUP 2
FRE QUENCY FRE QUENCY

RE US E RE US E
GROUP 3 GROUP 4
FRE QUENCY
RE US E
GROUP 1
RE US ED
ti-GS M-Four ce ll fre que ncy re us e pa tte rn-00022-a i-s w
Audio capacity
Digital transmission of speech and high performance digital signal processors provide good
quality speech transmission. In regions of interference or noise-limited operation, the speech
quality is noticeably better than analog transmission. Where noise or interference obliterate
speech frames, error correction is used to put back some of the missing information. If too much
information is lost, a digital extrapolation algorithm is used to fill the gap. While the precise
implementation of the extrapolation algorithm is up to the manufacturer, GSM recommends
minimum and maximum permitted extrapolations.
Link integrity
GSM incorporates several features to achieve a high-integrity communication link and to ensure
high quality signaling performance. Call re-establishment procedures allow lost subscribers to
reconnect to an interrupted connection. These procedures reduce the number of dropped or
lost calls.
A unique feature of digital communication is the use of the error control coding to estimate the
bit error rate of the channel being used. Thus, the system evaluates link quality and can take
action on co-channel and adjacent channel interference, even when signal levels are relatively
high. If detrimental interference is sensed, a subscriber is handed over to a different cell
or channel.
1-18 68P02901W01-S
Jul 2008
System Information: GSM Overview Subscriber services
Subscriber services
Under GSM, subscriber services similar to the services provided by an ISDN land network can
be made available to portable mobile and hand portable Mobile Stations. The Mobile Station is
provided with control channels (like the D channel on ISDN) and a traffic channel for user data
or digitized voice (similar to the ISDN B channel).
Both data and voice are carried in digital form on the radio interface, allowing end-to-end digital
connections through land and GSM networks. The control channels also provide the mobile
subscriber with supplementary services similar to the services in the ISDN land network. For
example, calling number presentation, closed user groups, and in-call modifications.
Data communications
In addition to provisions for voice communication, GSM MSs can provide either an ISDN S
interface point, or an ITU-TSS X or V-series interface, to connect standard data terminal
equipment. A data inter working function allows inter working with other data networks such as
the ISDN land network. For interworking with an analog-oriented Public Switched Telephone
Network (PSTN), the function connects data from the mobile through a modem and converts the
modem audio to Pulse Code Modulation (PCM) format for connection to a PSTN digital trunk.
Other types of inter working, such as access to packet-switched and circuit-switched public data
networks can be provided. The call setup message from the MS includes information on the
MSs bearer capability to indicate which type of data call is being set up.
Teleservices
GSM provides several categories of teleservices, including basic speech, Short Message Service
(SMS) (for messages sent to a pager built into the MS), message handling service, facsimile,
videotext, and teletext. Data services are also available in both circuit and packet modes,
and with a diversity of inter working functions, to support interfaces between the PSTN and
the ISDN.
Traditional landline analog modems provides interfacing with the land network. Transparent
transmission can be used, which includes error correction. Data rates from 300 bits per second
to 12,000 bits per second are provided.
If improved error control is desired, data services using a non-transparent protocol can be
invoked. This error detection or retransmission scheme provides for much reduced net error
rates, though the throughput rate is dependent on the radio channel quality and is not affected
by the error control.
Security features
Security features of GSM protect both users and operators against eavesdropping and the
misuse of valuable resources. Specific provisions protect subscriber identity and authentication,
user data, and elements of the signaling information.
68P02901W01-S 1-19
Jul 2008
GSM network elements Chapter 1: Introduction to Motorola GSM
GSM network elements

Introduction to GSM network elements
The GSM network incorporates a number of network elements to support mobile telephones and
other mobile equipment (known collectively as Mobile Stations, or MSs). These elements form
the major components of the GSM network.
Network management center functions
The Network Management Center (NMC) is an element defined by the GSM recommendations
for managing an entire GSM cellular network to provide Operation and Maintenance at the
network level.
The NMC performs the following functions:

Monitors trunk routes between nodes on the network.
Monitors high-level alarms.
Monitors OMC-R regions and provides assistance to OMC-R staff.
Passes information from one OMC-R region to another to the improve problem solving
strategies.
Enables long-term planning for the entire network.
The NMC, being responsible for Operation and Maintenance at the network level and managing
traffic on the network, performs overall management of the PLMN. It is a single control point
in systems with multiple MSCs, with the ability to coordinate interconnects to networks such
as alternative PSTNs.
Monitoring the equipment
Both the OMC-S and OMC-R systems provide the NMC with information about the network
equipment. The NMC monitors this information for high-level alarms, such as a failed or
overloaded network node, and also monitors the status of automatic controls applied at
the network equipment in response to conditions such as overload. NMC operators monitor
the network status, and in the event of a problem, are able to give guidance to staff at the
appropriate OMC, according to the ability of other regions to handle increased traffic flow.
1-20 68P02901W01-S
Jul 2008
System Information: GSM Overview Monitoring the routes
Monitoring the routes
The NMC monitors the signaling and trunk routes between nodes to prevent an overload
condition propagating through the network. Routes between the PLMN and the PSTN are also
monitored to avoid propagation of overload conditions between networks. The NMC staff can
coordinate network management controls with the NMC facilities supporting the other networks.
Managing the traffic
The NMC also manages traffic on the BSS network equipment. In extreme circumstances,
NMC operators are able to invoke controls such as priority access, as described in GSM
recommendation 2.11. The control of traffic on the signaling and traffic routes between the
MSC and BSS can be used to isolate overloading problems within a region. The NMC provides
its operators with the ability to reconfigure cell parameters as needed and to force handovers.
Simulating the OMC-R
The NMC is able to take regional responsibility when an OMC-R is not manned, with the OMC-R
acting as a transit point between the NMC and the network equipment. In this instance, the
NMC can provide operators with functions equivalent to those available at the OMC-R. The
NMC also supports planned changes to, or expansion of, the network.
Interface
GSM defines the interface between the NMC and OMC-R to use Q3 protocol on a 64 kbps
digital link.
68P02901W01-S 1-21
Jul 2008
Operation and Maintenance center Chapter 1: Introduction to Motorola GSM
Operation and Maintenance center

Introduction to the OMC
The GSM recommendations identify an element that controls and monitors the other network
elements within a region. In the Motorola GSM network, the Operation and Maintenance Center
(OMC-R) performs this function. The OMC-R also monitors the quality of service provided by
the network. The OMC-R is connected to the other network elements through an X.25 packet
network, and sends and receives only the control and network information and, not speech
or data traffic.
1-22 68P02901W01-S
Jul 2008
System Information: GSM Overview Mobile services switching center
Mobile services switching center

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

Short Message Service).
Mobility management functions:

Interrogation of MS
Paging
Handover
Call re-establishment
Location updating: interrogation and updating of VLR and HLR
68P02901W01-S 1-23
Jul 2008
Gateway MSC Chapter 1: Introduction to Motorola GSM
Inter working between the signaling systems of fixed networks and the signaling system of
the BSS.
Resource handling:
Queuing
Off-air call setup
Mobile subscriber charging
Inter-administrative revenue accounting
Security functions
Simultaneous and alternate use of services
Inter working for dual tone multifrequency signals
User information language (For example, recorded announcements)
Gateway MSC
When the MSC provides an interface between the fixed and mobile networks, it is known as
the Gateway MSC (GMSC), since it gives the mobile network access to the landlines of the
PSTN, ISDN and data networks. It can also provide specific Inter Working Functions (IWFs) to
other networks.
Flexible design for MSC
The GSM recommendations define the functions of the MSC, but allow flexibility in its design.
The most common solution is to combine the functions of the MSC, VLR, HLR, AUC, and
EIR into one functional node. This has the advantage that the dynamic load, caused, for
example, by inter working through C7 signaling links, is kept to a minimum.
Another approach is to separate all functional elements into separate network nodes.
A third solution consists of combining functional elements in accordance with the

requirements of the operating company. For example, the MSC and VLR can be combined,
as can the HLR and AUC.
In practice, due to the transmission capacity of C7, the MSC must not be separated from the
VLR, nor the HLR from the AUC.
1-24 68P02901W01-S
Jul 2008
System Information: GSM Overview Interfaces
Interfaces
The MSC has interfaces to the following:

OMC-R
Other MSCs within the same PLMN
BSSs
Location registers: HLR, VLR, and EIR
Emergency Service Center
Service Center (SC) - Used for Short Message Service
Other networks, including the PSTN/ISDN, PDN and other PLMNs
The A interface
The interface between the MSC and the BSS is defined as the A Interface. The interface uses
one or more E1 digital links. The channels on these links can be used for traffic or signaling.
The A Interface provides facilities to the traffic channels and signaling links for the following
functions:
Terrestrial management - allocation and blocking of the terrestrial traffic channels.
Radio channel management - BSS management - radio channel allocations or control.
Mobility management - location update - transparency between the MS and MSC.
Call control - set up for mobile originating or terminating calls.
Supplementary services - transparency through the BSS.
Layered signaling
The signaling is layered, similar to the signaling in the OSI reference model. However, the
layers referred to are not identical but specified by ITU-TSS C7.
BSSMAP and DTAP
The A Interface carries messages between the BSC and the MSC and the BTS (MS). These
two data flows are referred to as BSSMAP and DTAP. In addition, the general BSC BSSMAP
messages must be distinguished from the DTAP messages specific to the mobile station
connection, with the DTAP messages identified between themselves. For the DTAP messages,
the virtual circuit approach is used with independent connections established and released.
68P02901W01-S 1-25
Jul 2008
Location register interfaces Chapter 1: Introduction to Motorola GSM
Protocols
Figure 1-4 shows how the signaling messages are transferred between the BSC (or different
mobile stations) and the MSC by using the C7 MTP-SCCP stack and protocols.
Figure 1-4 A interface protocols

BSSMAP DTAP
DISTRIBUTION LAYER
SCCP
MTP
PHYSICAL LAYER
ti-GSM-A interface protocols-00023-ai-sw
The SCCP defines several classes of services, of which only two are used in the GSM A Interface.
They are the connectionless mode and a connection orientated mode. These modes are referred
to as class 0 and class 2 SCCP services.
Location register interfaces
The lower level communication functions for the interfaces between the MSC, VLR, HLR, and
EIR follow the ITU-TSS recommendations for C7. At the application level, GSM specifies the
messages used on these interfaces as the Mobile Application Part, or MAP.
Message transfer link
The Message Transfer Link (MTL) is the Motorola name given to the signaling link between the
MSC and BSC. It takes up one timeslot on the E1 link.
Call control
The MSC performs call control functions such as number translations and routing, matrix
path control, and allocation of outgoing trunks. It maintains PLMN synchronization and
provides synchronization to its BSSs. The MSC also collects traffic statistics for performance
management.
Emergency calls
An international emergency number allows GSM subscribers to make emergency calls wherever
they are located. The MSC receives emergency call setup messages, and routes the calls to
the appropriate emergency center.
1-26 68P02901W01-S
Jul 2008
System Information: GSM Overview Short message service
Short message service
The Service Center (SC) sends point-to-point short messages destined for the MS to the GMSC.
The GMSC checks for errors, interrogates the HLR to determine the location of the MS
and transfers the message to the appropriate MSC (The GMSC and the MSC is the same
equipment). The MSC uses call setup parameters from the VLR to establish the call and
reports the outcome back to the GMSC, which in turn reports to the MSC.
If the message is unsuccessful, the GMSC requests the HLR to store the SC address as a
Message Waiting Data for the MSISDN. The HLR determines when the MS is next ready to
receive a message, and informs the MSC that has the inter working interface with the SC
(The inter working MSC and the MSC is the same equipment). The inter working MSC in
turn informs the SC so that a further attempt to send the message can be made.
MSCs also handle short messages sent from the MS. The MSC local to the MS checks
the message for errors and transfers it to the appropriate inter working MSC. The inter
working MSC transfers the message to the destination SC, receives the outcome and
reports it back to the MSC, which reports to the MS.
MSCs only handle point-to-point short messages. The OMC-R and the BSS handle short
messages broadcast to all MSs in a cell.
Security procedures
Other functions performed by the MSC are unique to the mobile environment. The MSC supports
the security procedures used to control access to the radio channels. These procedures include:
Passing the keys used to validate the identity of the mobile equipment and the subscriber
to the BSS.
Encrypting the data sent on the traffic channel and control channels.
Local registration and call handover
In addition to the call setup procedures, the MSC also controls location registration and some
handover procedures. Location registration and location update allow MSs to report changes in
their locations, enabling automatic completion of MS terminated calls. The handover procedure
preserves call connections as MSs moves from one radio coverage area to another during an
established call. A single and the same BSC controls handovers within cells. When handovers
are between cells controlled by different BSCs, the primary control is at the MSC. Figure 1-5
shows how the two types of handover are achieved.
68P02901W01-S 1-27
Jul 2008
Inter-MSC handovers Chapter 1: Introduction to Motorola GSM
Figure 1-5 Handover control
BSC
MS
EACH CELL CONTROLLED BY A
DIFFERENT BSC, SO MSC
CONTROLS HANDOVER
HANDOVER
BTS BTS
MSC
BSC BSC
BSC CONTROLS BOTH
CELLS, SO IT CONT ROLS
HANDOVER MS
HANDOVER
BTS BTS
ti-GSM-HO control-00024-ai-sw
Inter-MSC handovers
Handovers between MSCs can also be performed between BSSs connected to two different
MSCs. In these handovers, the MSC where the call originates functions as the primary MSC,
and retains ultimate control of the call through out its duration, even though the call processing
tasks are handed over to another MSC.
Equipment identity register
The Equipment Identity Register (EIR) option, is a centralized database for validating the
International Mobile station Equipment Identity (IMEI).
The database contains three lists:

The white list contains the IMEIs of valid MSs.
The gray list contains IMEIs of equipment to be monitored and observed for location
and correct functioning.
The black list contains IMEIs of MSs which have been reported stolen or are to be denied
service.
1-28 68P02901W01-S
Jul 2008
System Information: GSM Overview Home location register
The MSCs in the network can remotely access the EIR database. The MSC in a different PLMN
can also access the EIR. A given PLMN can contain more than one EIR, in which case each EIR
controls certain blocks of IMEI numbers. The MSC contains a translation facility, which, when
given an IMEI, returns the address of the proper EIR to access. Figure 1-6 summarizes the
three database lists.
Figure 1-6 Database list summary
Home location register
Figure 1-7 shows the Home Location Register (HLR), which is a database of subscriber
information used in setting up calls. Various identification numbers and addresses are stored as
well as authentication parameters, services subscribed for and special routing information are
stored in the HLR. The current status of the subscriber is maintained.
Figure 1-7 HLR configuration
MSC
MSISDN HLR
HOME LOCATION
REGISTER
MSISDN
or IMSI BASIC SER VICE LIST MSISDN
EXTERNAL VLR
PLMN SUPPL SER VICE LIST
CURRENT VLR
CALL FOR WARD
NUMBER and so on
IMSI
IMSI
VLR MSC
ti-GSM-HLR config-00026-ai-sw
68P02901W01-S 1-29
Jul 2008
HLR master database Chapter 1: Introduction to Motorola GSM
HLR master database
The HLR contains the master database of the subscribers to a PLMN. The MSCs and VLRs in the
network can remotely access this data. A PLMN can include more than one HLR, in which case
each HLR contains a portion of the total subscriber database. Either the IMSI or the mobile
subscriber ISDN number can access the subscriber data. The MSC or a VLR in a different PLMN
can also access the data, to allow inter-system and inter-country roaming.
HLR data
The data stored in the HLR indicates the basic and supplementary services a given subscriber
is allowed to use. This data is changed only when new subscribers are added or deleted, or
the specific services they subscribe to are changed. The HLR data also includes temporary
information related to supplementary services such as the current call forwarding number.
A subscriber's HLR entry also includes the address of the current VLR. This information, in
connection with the VLR data, allows completion of calls to the mobile subscriber.
Authentication center
The HLR function can also include the Authentication Center (AUC) as shown in Figure 1-8. The
AUC generates and stores the parameters necessary to authenticate a subscriber's identity to
guard against fraudulent system use.
Figure 1-8 Authentication center configuration
AUTHENTICATION CENTRE
AUTHENTICATION
KEY
ONE PER
REQUEST FOR SUBSCRIBER SIGNED
AUTHENTICATION RESPONSE
ALGORITHM
PROCESS To VLR
RANDOM
NUMBER RANDOM
GENERATOR NUMBER
To MS
ti-GSM-AUC config-00027-ai-sw
1-30 68P02901W01-S
Jul 2008
System Information: GSM Overview Authentication key
Authentication key
To support the authentication process, each subscriber is assigned an authentication key (Ki),
which is stored only in the SIM of the MS and at the authentication center. The AUC generates a
random number that is an input to the authentication algorithm along with the authentication
key. The algorithm produces a new number called the signed response. To authenticate a
subscriber, the random number is sent to the MS.
If the mobile is a valid one, it executes the same authentication algorithm as the AUC and using
its known Ki produces the same signed response that is sent back on the signaling channel.
Producing the same signed response from the same random number proves the authenticity
of the subscriber. This method provides increased security because anyone monitoring the
radio channel cannot acquire any fixed keys.
Visitor location register
Figure 1-9 shows the Visitor Location Register (VLR), which is a local subscriber database,
holding the details of those subscribers who enter the area of the network that it covers. The
details are held in the VLR until the subscriber moves into the area serviced by another VLR.
The data includes most of the information stored at the HLR, as well as more precise location
and status information. The VLR provides the system elements local to the subscriber, with
basic information on that subscriber, thus removing the need to access the HLR every time any
subscriber information is required.
Figure 1-9 Visitor location register configuration
VLR
VISITOR LOCATION
REGISTER
MSRN
(MOBILE STATION
VLR Database ROAMING MSRN
NUMBER)
GENERATOR
COPY OF SELECTED
IMSI DATA FROM HLR HANDOVER
INTERROGATION TMSI DATABASE FOR ALL HANDOVER NUMBER
ACCESS MODES SUBSCRIBERS NUMBER
MSRN CURRENTLY IN AREA GENERATOR
SER VICED BY THIS
VLR
TMSI
(TEMPORAR Y MOBILE NEW TMSI
SUBSCRIBER IDENTITY)
GENERATOR
ti-GS M-VLR config-00028-a i-sw
68P02901W01-S 1-31
Jul 2008
Controlling LAIs Chapter 1: Introduction to Motorola GSM
Controlling LAIs
Cells in the PLMN are grouped into geographic areas and each is assigned a Location Area
Identification (LAI). Each VLR controls a certain set of LAIs. When a mobile subscriber roams
from one LAI to another, the current location is updated in the VLR entry using the location
validate procedure.
If the old and new LAIs are under control of two different VLRs, the entry on the old VLR is
deleted and a new entry is created at the new VLR by copying the basic data from the HLR entry.
The subscriber's current VLR address, stored at the HLR, is also updated thus providing the
information necessary to complete calls to the mobile subscriber.
Controlling MSRNs
The VLR also controls the assignment of Mobile Station Roaming Numbers (MSRNs). When the
MS receives an incoming call, the HLR requests the correct VLR for an MSRN. The VLR selects
the MSRN from its pool of numbers and returns it to the MSC that initially handled the call. The
call is then forwarded using the MSRN as the called address. The MSRN causes the call to be
routed to the MSC which controls the base stations in the area where the MS is currently located.
Allocating handover numbers
The VLR also allocates handover numbers for use in inter-MSC handovers. These handovers
require the call to be rerouted from the source MSC to the target MSC. The handover number
functions similarly to the MSRN, as it allows the required trunk connection to be set up by
routing the call through the land network.
Allocating TMSI numbers
The VLR also controls allocation of new Temporary Mobile Subscriber Identity (TMSI) numbers.
A subscriber's TMSI can be periodically changed to secure the subscriber's identity. The system
configuration database controls when the TMSIs are changed. Options include changing the
TMSI during each location update procedure or changing it within each call setup procedure.
IMSI, TMSI, or MSRN can access the database in the VLR. Typically, there is one VLR per
MSC, but other configurations are possible.
Call handling
The following figures illustrate the functions of the MSC in handling mobile originated or
terminated traffic.
1-32 68P02901W01-S
Jul 2008
System Information: GSM Overview MS to PSTN subscriber
MS to PSTN subscriber
Figure 1-10 shows a call from the MS to a subscriber in the land network (that is, the PSTN).
The MSC acts as an outgoing exchange. If the call is directed to another country, the MSC
routes it to the International Switching Center. If the call is to a subscriber on the national
network, the call is routed to the PSTN, which sets up the connection to the PSTN subscriber.
The MSC performs the same function for a call directed to the ISDN.
Figure 1-10 MS to PSTN subscriber call
68P02901W01-S 1-33
Jul 2008
PSTN subscriber to MS Chapter 1: Introduction to Motorola GSM
PSTN subscriber to MS
Figure 1-11 shows a call from a subscriber in the land network (that is, the PSTN) to the MS.
The assumption is that the PSTN cannot interrogate the HLR, and so the call has to be directed
to the Gateway MSC, which performs the interrogation. The MSRN is then used to route the call
to MSC-B which pages MS-B and sets up the call to it. The connection between the Gateway
MSC and MSC-B is routed through one or more transit exchanges of the national ISDN or PSTN.
Figure 1-11 PSTN subscriber to MS call
PSTN or ISDN
PLMN
MSC-B GMSC
BSS
VLR HLR
MS-B
ti-GSM-PSTN MS call-00030-ai-sw
MS to MS calls
The scenarios covered include:

A call between MSs in the same PLMN.
A call between MSs in different PLMNs in the same country.
A call between MSs in different PLMNs in different countries.
1-34 68P02901W01-S
Jul 2008
System Information: GSM Overview MS to MS calls
MS to MS (same PLMN)
Figure 1-12 shows a call between a calling MS (MS-A) and a called MS (MS-B) in the same
PLMN. The MSC-A analyses the called number for MS-B, through the VLR. It interrogates the
HLR to retrieve the MSRN which it uses to route the call to MSC-B. The MSC-B acts as an
incoming exchange and establishes the call to MS-B. The connection between the two MSCs is
routed through one or more transit exchanges of the national ISDN or PSTN.
Figure 1-12 MS to MS call (same PLMN)
PLMN
HLR VLR
MSRN of MS-B
RETRIEVED
MSC-A
BSS
MS-A
VLR
PSTN/ISDN
MSC-B
BSS
MS-B
ti-GSM-MS MS same PLMN call-00031-ai-sw
68P02901W01-S 1-35
Jul 2008
MS to MS calls Chapter 1: Introduction to Motorola GSM
MS to MS (different PLMN/same country)
Figure 1-13 shows a call between a calling MS (MS-A) in one PLMN and a called MS (MS-B) in
another PLMN. MSC-A analyses the called number for MS-B. It interrogates the HLR of the
other PLMN to retrieve the MSRN which it uses to route the call to MSC-B. MSC-B acts as an
incoming exchange and establishes the call to MS-B.
Figure 1-13 MS to MS call (different PLMN)
PLMN
VLR
MSC-A
BSS
MS-A
PSTN or
ISDN
PLMN
HLR VLR
MSC-B
BSS
MS-B
ti-GSM-MS MS dif ferent PLMN call-00032-ai-sw
1-36 68P02901W01-S
Jul 2008
System Information: GSM Overview MS to MS calls
MS to MS (different PLMN/different country)
Figure 1-14 shows a call from the MS (MS-A) in one PLMN to the MS (MS-B) in a PLMN in
another country. The MSC-A determines from the international prefix that the call is directed
to another country but cannot determine the location of the called MS. The call is therefore
routed to the Gateway MSC in the other country, which interrogates the HLR to discover the
MSC area where MS-B is currently located. The HLR returns the MSRN and the call is routed to
MSC-B. MSC-B acts as an incoming exchange and establishes the call to MS-B. The connection
between the GMSC and whichever MSC area an MS-B roams to, is routed through one or
more exchanges of the national ISDN or PSTN.
Figure 1-14 MS to MS call (different PLMN/different country)
68P02901W01-S 1-37
Jul 2008
Base station system Chapter 1: Introduction to Motorola GSM
Base station system

Introduction to the BSS
The Base Station System (BSS) is the fixed end of the radio interface that provides control and
radio coverage functions for one or more cells and their associated MSs. It is the interface
between the MS and the MSC. The BSS comprises one or more Base Transceiver Stations (BTSs),
each containing the radio components that communicate with MSs in a given area, and a Base
Site Controller (BSC), which supports call processing functions and the interfaces to the MSC.
Digital radio techniques are used for the radio communications link, known as the Air Interface,
between the BSS and the MS.
The BSS and the Air Interface are described in detail in Base station system on page 2-2.
BSS configurations
Physically, a BTS is remote from its BSC. Where the BTSs are remote from the BSC, they are
linked in a variety of ways. Three possible configurations are shown in Figure 1-15.
BSS 1 is a simple configuration, with a direct link from the BSC to a single BTS.
BSS 2 shows a spoke configuration, where each of the BTSs has its own link to the BSC.
BSS 3 shows a closed loop configuration, with each BTS linked to the next, and a link
from the last BTS back to the BSC.
1-38 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS configurations
Figure 1-15 BSS configurations
BSS #2 BSS #3
MS
BTS
SITE
MS MS
BTS
SITE
BTS BTS
MS SITE
SITE
BSC
SITE
WITH BTS
XCDR SITE
MS
BTS
SITE
BSC
SITE
BTS
SITE
RXCDR
(NOTE 2)
A MSC
LEGEND
Air Interface
A A Interface PSTN/ISDN/PUBLIC DA TA NETWORK
NOTE:
(1) DASHED LINES ENCLOSE NETWORK COMPONENTS
OF A PARTICULAR BSS AND DO NOT SHOW THE BSS
SER VICE AREA.
(2) REMOTE TRANSCODING (RXCDR) IS LOCA TED AT
MSC SITE, BUT IS P ART OF BSS #2.
ti-GSM-BSS configs-00034-ai-sw
The configuration used at any particular site depends on a number of factors, and a mixture of
configurations can be used within a single BSS. The BTS configurations are described in greater
detail in the manual Service Manual: 68P02901W37.
68P02901W01-S 1-39
Jul 2008
Software functions Chapter 1: Introduction to Motorola GSM
Software functions
Table 1-5 summarizes the software functions of the BSS.
Table 1-5 BSS software functions
Executive/Operating Operation and

Radio Subsystem Call Processing
System Maintenance
TTY DLSP Terminal Fault Translation LAYER 2 INTERFACE CM Connectionless
Data Link Service Process Mobile Signaling Manager
Process Translation, LAPDm
protocol, and Short
Message Service
functions
TDM DLSP Time CM Configuration Abis INTERFACE: SCCP STATE
Division Multiplex Manager Interface between MACHINE Signaling
Data Link Service BSC and BTS Connection Control
Process Part
EXEC DLSP MMI Man-Machine Handover and Power RRSM Radio
Executive/Process Interface Control Resource State
Data Link Service Machine
Process
Initialization Process SM Switch Manager
Process Control
Motorola BSS
In Motorola systems, the BSS equipment can be used both as a concentrator hub and as a single
site. The Motorola add and delete option allows BTSs to be strung one to another in an open or
closed loop topology. This enhancement provides reduced line charges in low density coverage
regions, such as sparse rural areas or along highways.
The BSC controls the selection of signaling channels, and speech channels, and manages the
radio channels. It transfers signaling information to and from MSs through the BTS.
Connection of MSC
The relationship between the radio channels at the BSS and the terrestrial circuits, which
connect the BSS to the MSC is not fixed. A radio channel and terrestrial circuit must be
selected and assigned every time a call is set up. The BSC selects the radio channel, while the
MSC selects the terrestrial circuit. The BSC then uses a digital switching matrix to connect
the two together. The switching matrix also allows the BSS to perform inter-BSS handovers
without involving the MSC.
1-40 68P02901W01-S
Jul 2008
System Information: GSM Overview Speech transcoding
Speech transcoding
Speech transmitted on the GSM radio channel must be transcoded to reduce the bandwidth
requirement on the Air Interface. The speech transcoder (XCDR) performs this function.
Transcoding is performed at the BSC, or remotely at or near the MSC. When transcoding is
performed remotely, it can be combined with 4:1 multiplexing (with GSM or AMR half rate 8:1 is
possible in the optimum case) in which the data for four logical channels is combined onto one
64 kbps link, thus reducing the number of links required for interconnection of the BSCs.
BSS application parts
At the application levels of the C7 communications protocol, GSM defines a special set of
messages, unique to the mobile application, called the BSS Application Part (BSSAP).
The BSSAP comprises:

The BSS Mobile Application Part (BSSMAP), which is used on the BSS-MSC link.
The Direct Transfer Application Part (DTAP), which is used over the radio interface to
the MS.
BSS interfaces
The A interface
The interface between the MSC and the BSS is a standardized C7 interface and is fully defined
in the GSM recommendations. It enables the system operator to purchase switching equipment
(such as an MSC) from one supplier, and radio equipment (such as a BSS) from another supplier,
and still retain equipment compatibility.
The Abis interface
The interface between the BSC and a remote BTS is also a standard interface. However,
Motorola offers a unique Motorola Abis Interface, called Mobis, which reduces the amount of
message traffic and thus the number of E1 links required between a BSC and a BTS.
The Air interface
The radio communications link between the BSS and the MS is known as the Air Interface.
The GSM Air Interface is a noise-robust transmission medium. The speed of a radio channel used
in GSM is 270.833 kbps. The modulation is 0.3 BT Gaussian Minimum Shift Keying (GMSK).
68P02901W01-S 1-41
Jul 2008
Physical channels Chapter 1: Introduction to Motorola GSM
Physical channels
The Air Interface is capable of handling simultaneous calls; any call sent on an RF carrier
can share that carrier with up to seven other calls. GSM systems achieve this by virtue of
the high speed of digital radio communication, which allows each call to take its turn on the
carrier with no loss of transmission quality.
Logical channels
The different types of information sent over GSM physical channels are called logical channels.
The term channel is therefore used differently when applied to logical channels. The physical
channel is a pathway for the information; the logical channel is the type of information sent.
Logical channel types
There are two types of logical channel on the Air Interface: control (or signaling) channels
and traffic channels.
Control channels
The control channels are used to carry signaling information between the MS and BSS. The four
control channel groups are:
Broadcast control channels
Broadcast Control CHannel (BCCH) - Contains information about the cell.
Frequency Correction CHannel (FCCH) - Used by the MS to correct the frequency of its
internal time base.
Synchronization CHannel (SCH) - Used by the MS to synchronize to the TDMA frame

structure in the cell.
Common control channels
Random Access CHannel (RACH) - Transmitted by the MS to gain access to the system.
Paging CHannel (PCH) - Transmitted by the BTS to contact a specific MS.
Access Grant CHannel (AGCH) - Transmitted by the BTS to grant or refuse a specific
MS access to the system.
Cell Broadcast CHannel (CBCH) - Used to broadcast messages to all MSs in a specific cell.
1-42 68P02901W01-S
Jul 2008
System Information: GSM Overview Traffic channels
Dedicated control channels
Standalone Dedicated Control CHannel (SDCCH) - Used during call setup or to transmit short
messages.
Associated control channels
Slow Associated Control CHannel (SACCH) - Used by the BSS to transmit power and timing
information to the MS and to receive measurement reports from the MS.
Fast Associated Control CHannel (FACCH) - Used to transmit signaling information

between the MS and BSS. The FACCH is used when information must be passed quickly,
for example, during a handover.
Traffic channels
These channels are used to carry speech or data information between the MS and BSS, and
include:
Speech channels - These channels carry speech information over the Air Interface. There
are two types of speech channels:
Full rate
Half rate
Data channels - These channels carry data information over the Air Interface. There are
three types of data channels, each named according to the data rate it supports:
9.6 kbps
4.8 kbps
2.4 kbps
68P02901W01-S 1-43
Jul 2008
GSM subsystems (non-network elements) Chapter 1: Introduction to Motorola GSM
GSM subsystems (non-network elements)

Introduction to GSM non-network element subsystems
The GSM network also includes the following additional subsystems, which are not formally
recognized as network elements.
Inter working function
The Inter Working Function (IWF) performs the data rate adaptation between the PLMN and
networks such as the PSTN, the Integrated Services Digital Network (ISDN), and packet
networks. Other functions of the IWF include provisions for mobile subscribers to communicate
with a PSTN-based modem, or to connect directly to customer provided equipment, such as X.25
Packet Assembly/Disassembly facilities (PADs).
Echo canceler
The Echo Canceler (EC) eliminates echo from voice circuits. The voice signal from the PLMN
must be transformed from the 4-wire PLMN circuit to the 2-wire circuit on the land network. If
it is not canceled, the total round-trip delay introduced by the GSM system (typically 180 ms)
would become audible to the PLMN subscriber as an echo.
Billing center
The billing center is a system provided by the PLMN administration which collects the billing
data from the GSM network elements and applies the billing data to the accounts of the
subscribers. The GSM does not address the details of operation of the billing center, and the
billing center is not considered as a network element of the PLMN.
There are two types of billing data:

Call records
The MSC produces call records, and provides facilities for storing the completed call
records, as well as forwarding them to the billing center. The records are stored in a disk
file as they are being generated. In this case, the file has a fixed maximum size and when
the file becomes full, it is automatically closed and a new one is opened. The completed file
is then automatically transferred to the billing center using X.25 communication links and
the File Transfer Access and Management (FTAM) file transfer protocol. A backup of the
completed billing files can be manually copied to a magnetic tape. The same storage and
communication facilities can also be provided at HLRs and VLRs for handling event records.
Event records
The HLRs and VLRs produce event records. An event record contains the location updates
for the MS and the forwarding of MS terminated calls.
1-44 68P02901W01-S
Jul 2008
System Information: GSM Overview Cell broadcast center
Cell broadcast center
The Cell Broadcast Center (CBC) is the call processing center for Cell Broadcast Short Message
Service (CBSMS) messages, which are unacknowledged short messages (maximum of 128
bytes) that are broadcast to all MSs in a particular cell.
68P02901W01-S 1-45
Jul 2008
GSM system features Chapter 1: Introduction to Motorola GSM
GSM system features

Introduction to GSM system features
The following section describes GSM features and its technological requirements, and
summarizes the GSM specifications.
Technological requirements
Technological requirements for the GSM systems include the following:

A fast, highly reliable Automatic Gain Control (AGC) to facilitate capture of the short
random access burst.
Selection of proper filters to minimize spurious emissions without corrupting the desired
signal.
Stable quasi-linear RF PA to provide the rapid ramping for achieving GSM specified time
and spectral masks.
Adequate power supply decoupling and regulation to reduce transmitter pulsing transients.
Proper distribution of gain and AGC receiver stages to achieve the necessary 100 dB
of dynamic range.
Self calibrating techniques for generating and demodulating Gaussian Minimum Shift
Keying (GMSK) that do not require tuning and are immune to drift or ageing.
Adequate diagnostic capability, fault analysis tools, test equipment, and key servicing
test points.
Synthesizer technology that meets the high switching speeds required for frequency
hopping.
The GSM digital cellular system provides:

European standardization
Good audio quality and link Integrity
Features supplying:
Subscriber services
System-related features
Increased capacity
Lower cost infrastructure
Hand portable viability
1-46 68P02901W01-S
Jul 2008
System Information: GSM Overview Standardized electrical interfaces
Standardized electrical interfaces
GSM defines standardized electrical interfaces and communications protocols for both the
fixed and subscriber equipment. This guarantees compatibility and inter working between
systems designed by different manufacturers and also allows the user to choose equipment at
the subsystem level, as well as the overall system level.
GSM interfaces
The following GSM interfaces are standardized and specified:

MSC - PSTN/ISDN (of National concern)
MSC - MSC (of National concern)
MSC - BSC (of National concern)
BSC - BTS (not used by the Motorola)
BTS - MS
MSC - All LRs
LR - LR
Subscriber ISDN Interfaces
ISDN compatibility
GSM is compatible with the Integrated Services Digital Network (ISDN) which carries both
voice and data on standard telephone lines. Many countries are committed to implement this
telecommunication network.
Signaling System 7
As an extension of the landline telephone network, GSM clearly relies heavily on Signaling
System 7 (SS7/C7) to provide the bearer level communications protocol.
Hierarchical network architecture
The use of a hierarchical network architecture is another feature that can be exploited by
system designers and individual equipment providers to reduce the operating cost, particularly
inline charges. A hierarchical network architecture employs intermediate BSC controllers
between the MSC and the radio channel equipment.
68P02901W01-S 1-47
Jul 2008
Subscriber services Chapter 1: Introduction to Motorola GSM
Subscriber services
GSM systems can offer an enhanced range of services, such as teleservices, data and speech
services. These services can be augmented with a variety of supplementary subscriber services.
The following are some of the supplementary subscriber services:

Number identification services
Call forwarding services
Charging services
Call barring services
Emergency services
Mobile access hunting
Call forwarding
Call queuing
Conference calls
An international emergency call number
Point-to-point and broadcast Short Message Services
Separate personal and business numbers for a single subscriber
Videotext, teletext, and fax
Security
GSM security features include the authentication of the mobile equipment and the subscriber.
Control information is encrypted, and speech is digitally encoded. These features provide
confidentiality and prevent stolen equipment from being used.
Handovers
GSM handovers are more tightly controlled than analog handovers. MSs have built-in
intelligence to assist in the handovers, which ensures that the network is relieved of unnecessary
measurement reporting and associated overheads.
During the handover procedures, extensive measurements are made both by the MS and the
BSS of such parameters as uplink (MS-to-BSS) and downlink (BSS-to-MS) signal levels, downlink
signal levels of adjacent cells, BSS-to-MS distance, and so on.
Many of these measurements are crosschecked to ensure trustworthiness. For example, not
only is the received level of adjacent cells measured, but also the associated control channel ID
is also received, decoded, and reported together with the quality of reception (bit error rate).
Both the BTS and the MS measure signal quality and signal strength. The MS also monitors
signal strengths in up to 32 adjacent cells.
1-48 68P02901W01-S
Jul 2008
System Information: GSM Overview Link integrity
Link integrity
GSM incorporates several features to achieve a high-integrity communication link and to ensure
high quality signaling performance. Call re-establishment procedures allow lost subscribers to
reconnect to an interrupted connection. These procedures reduce the number of dropped or
lost calls.
A unique feature of digital communication is the use of the error control coding to estimate the
bit error rate of the channel being used. Thus, the system evaluates link quality and can take
action on co-channel and adjacent channel interference, even when signal levels are relatively
high. If detrimental interference is sensed, a subscriber is handed over to a different cell
or channel.
Tracking
GSM systems keep track of the MS by updating it location. When the MS moves to a new
location area, the VLR is updated. The system also knows whether an MS is switched off, and
so, does not waste resources trying to page the MS unsuccessfully.
Power saving
GSM uses methods that save on power usage and extend battery life in the MS:
MS and base station power control
DTx (Discontinuous Transmission)
DRx (Discontinuous Reception)
Increased capacity
GSM systems have more capacity than analog systems. Eight simultaneous calls can be active
on one RF carrier (as opposed to one call per carrier in analog). Less RF hardware is therefore
required to expand a GSM system. GSM uses a radio channel structure (TDMA) that leads to an
increased capacity of 16 simultaneous calls per carrier if half rate is used.
Use of low bit rates for non-voice data
For data communications, the GSM offers a better match, than analog, of provided radio
spectrum to data rate. GSM provides specialized data and message services, such as a
point-to-point Short Message Service (for messages sent to a pager built into the MS). The call
lengths of these data services average much less than the corresponding speech calls.
68P02901W01-S 1-49
Jul 2008
Lower cost of infrastructure Chapter 1: Introduction to Motorola GSM
Lower cost of infrastructure
GSM design is intended to minimize the cost of the service provided. For example, the
signaling rate, and Time Division Multiplexing Access (TDMA) structure of 8 was selected as
a compromise between equipment complexity, system issues and performance. The use of a
single radio carrier for multiple traffic channels reduces the cost per channel. Half rate speech
coding provides further cost reduction.
Site size definitions
The GSM digital cellular system uses a 9-site or a 3-site (3-sectored) pattern and 120 degree
sector arrangement, which provides a 12 dB Carrier to Interference Ratio (C/I) for 90% location
reliability.
In addition, a unique Motorola design proposes a 2-site (6-sectored) repeat pattern using 60
degree sectors. The capacity of this pattern is 40% greater than the 3-site repeat generic
pattern and provides nearly equivalent C/I performance.
A trunking efficiency factor influences this capacity improvement further because the reduced
cell reuse patterns allow a smaller number of frequency groups. The improved C/I, in conjunction
with the more accurate and sophisticated handover technique, allows microcells to be used.
Timing adjustment
The farther the MS is from the base station, the longer it takes for the bursts of transmission
to travel the distance between them. The short duration of the TDMA burst demands a high
degree of accuracy, and so, the problem of a varying time lag must be overcome by timing
corrections performed by the MS. The base station measures the distance between the MS and
the base station, and uses it to calculate a timing advance, which the MS is instructed to use
for all uplink transmissions. This timing advance information is sent to the MS twice a second
using the SACCH. The advance is superimposed on the 3-timeslot offset of the frame structure,
which the MS uses when transmitting.
Echo cancelers
Another problem is that of echo, which is made noticeable by hybrid transformers converting
the signal from 4-wire circuits in the PLMN to the traditional 2-wire circuits in the land
telephone network. High-performance echo cancelers are therefore provided for every speech
conversation in the interface between the MSC and the PSTN.
Synchronization
Synchronization is a key feature of the GSM. All frequencies and times are locked to a high
stability (0.05 ppm) reference, which can be referenced to a system-wide standard. MSs lock to
a reference transmitted from the base station.
Synchronizing clocks over a wide geographic area gives GSM system advantages such as rapid
and reduced interruption and handovers as specified in the GSM recommendations.
1-50 68P02901W01-S
Jul 2008
System Information: GSM Overview Noise robustness
Synchronization also allows the effective number of channels available for frequency hopping
to be increased and the capacity of a limited number of radio channels to be distributed
more evenly. Both these enhancements are useful where a limited spectrum is available for
implementing the GSM system.
Noise robustness
The GSM radio interface is noise robust because:

All the information to be transmitted is digitally encoded. Under the encoding scheme,
the information is spread out by being interleaved, and the decoding methods allow error
detection and correction.
Each burst carrying encoded information includes a training sequence. An equalizer in

the receiver uses this sequence to synchronize with the burst and then measures signal
distortion and calculates from that the most probable transmitted sequence of bits.
Frequency hopping, makes GSM systems more resistant to the effects of multipath fading,
apart from providing security.
The use of two antennas at the BTS, placed several wavelengths apart, creates diversity of
radio paths from the MS, leading to improved reception.
BSS Location Services support
The Location Services (LCS) feature implements emergency services functionality in GSM
systems (compliant with the Federal Communications Commission (FCC) 911 requirements)
in two phases:
Phase 1
To transmit the originating number of an emergency call (911 in the United States) and the
location of the serving site to the Public Safety Answering Point (PSAP).
Phase 2
To transmit the emergency caller's estimated position, expressed in latitude and longitude
coordinates within specified limits of accuracy.
Applications that request location estimates from location services can be located in the MS, the
network, or externally to the PLMN.
LCS positioning mechanisms
Locations services currently specify three positioning mechanisms to determine the location
of a Mobile Station. These positioning processes involve two main steps: signal measurement
and position computation based on the measured signals. The standard SMG (Special Mobile
Group) positioning mechanisms are:
Enhanced Observed Time Difference (E-OTD) - not implemented in this release.
Assisted GPS (A-GPS) - not implemented in this release.
68P02901W01-S 1-51
Jul 2008
Timing Advance positioning (TA) Chapter 1: Introduction to Motorola GSM
Conventional GSM Timing Advance (TA) measurements can also be used in conjunction with
Cell ID determination to provide a coarser, lower quality location estimate.
Examples of applications to which LCS MS position determination can be applied are to deliver
tailored content to MSs in a physical locality (location-specific advertising), or to determine the
routing of voice traffic (location sensitive routing). Motorola supports Timing Advance (TA),
Enhanced Observed Time Difference (E-OTD) and Assisted GPS (A-GPS) positioning mechanisms.
Timing Advance positioning (TA)
The Timing Advance positioning mechanism is based on the existing GSM timing advance
measurements and the frequency of sending specified by the timing_advance_period
parameter. The timing advance value is known for the serving BTS and when returned to the
requesting LCS client with the cell ID, provides the approximate physical position of the MS.
1-52 68P02901W01-S
Jul 2008
System Information: GSM Overview E1 links
E1 links

Link types
GSM uses E1 operating link, to provide the physical links on the network. Communication
between the PSTN, MSC, and BSS equipment is over E1 links. X.25 and C7 information is sent
using the physical protocols on these links.
NOTE
Throughout this manual, reference is made to E1 links. Read the information in the
context of the type of link used.
E1 link
The E1 link has a signaling rate of 2.048 Mbps and provides thirty-two 64 kbps timeslots,
of which 30 are available:
Timeslot 0 is always reserved for synchronization purposes.
Although the remaining 31 are available for PCM or data channels, one is normally
reserved for control.
NOTE
The E1 link is sometimes referred to as a 2 Mbps link or bearer.
BSC daisy chain
When using the High bit-rate Digital Subscriber Line (HDSL) feature, a modem converts E1
lines for less expensive transmission lines. The modem is daisy chain connected at the BSC or at
a point where the HDSL link is required to change to an E1 connection.
68P02901W01-S 1-53
Jul 2008
Standardized interfaces Chapter 1: Introduction to Motorola GSM
Standardized interfaces

Interface types
A major portion of GSM recommendations deals with standards for interfaces between network
elements. Communication between the PSTN, MSC, and BSS equipment is over the E1 physical
links.
These links support the following major interfaces defined by GSM:

Air Interface: MS-to-BTS (also referred to as the UM Interface)
Abis Interface: Remote BTS-to-BSC
A Interface: BSC-to-MSC
B Interface: MSC-to-VLR
C Interface: MSC-to-HLR/AUC
E Interface: MSC-to-MSC
F Interface: MSC-to-EIR
G Interface: VLR-to-VLR
H Interface: HLR-to-AUC
Lb Interface: BSS-to-BSS-based SMLC
The use of these standardized interfaces throughout the mobile network allows compatibility
between network elements from different manufacturers.
For example, ITU-TSS Signaling System 7 (SS7/C7) is extensively used as the communications
protocol from the BSS through the MSC to the PSTN.
NOTE
ITU-TSS was previously known as CCITT. Signaling System 7 (C7) is sometimes
referred to as SS7 or C7.
In general, the open systems interface recommendations of the International Standards

Organization (ISO) have been followed for the protocol layers of the Open Systems
Interconnection (OSI) seven layer model. The system can be changed from the ISO standard
C7 to the ANSI standard SS7 for PCS1900.
1-54 68P02901W01-S
Jul 2008
System Information: GSM Overview GSM functional layering
GSM functional layering
The layering of GSM functions is partially based on the seven layer model for open systems
interconnection suggested by the ISO. Each layer performs a specific set of functions that are
isolated and enhances the functions performed by the lower layers. This philosophy facilitates a
modular approach to implementation. The functions occurring at one layer have only limited
interaction with the functions at another. This fact provides a degree of flexibility for future
improvements without redesigning the entire system.
Layer 1 - Physical
Layer 1 comprises the physical channel layer and is concerned with transmitting and receiving
coded information symbols over the radio link. Layer 1 features include the TDMA frame
structure and frequency hopping.
Layer 2 - Transport
Layer 2 features include the multiplexing and demultiplexing of logical channels.
Layer 3 - Management
Layer 3 provides for the three major management functions:

Radio resource management (paging, cipher mode set, frequency redefinition,
assignments, handover, measurement reports, and so on).
Mobility management (authorization, location updating, IMSI attach/detach, periodic

registration, ID confidentiality, and so on).
Call management (control, supplementary services, Dual Tone Multi-Frequency (DTMF),

Short Message Service, and so on).
68P02901W01-S 1-55
Jul 2008
BSSAP messaging Chapter 1: Introduction to Motorola GSM
Figure 1-16 shows the GSM functional layering.
Figure 1-16 GSM functional layering
Management Layer
Radio Resource Management Mobility Management Call Management
For example: For example: For example:

Paging Authentication Control
Layer 3 Cipher mode set Location updating Supplementary services
Frequency redefinition IMSI attach DTMF
Assignments IMSI detach Short Message Service
Handover Periodic registration
Measurements ID confidentiality
Reports
Tra nsport Layer
Layer 2 Multiplexes and demultiplexes logical channels:

Tra ffic Signalling Synchronization
Control
Layer 1 Physical Channel Layer

Tra nsmits and receives coded information symbols over the radio link
ti-GSM-GSM functional layers-00035-ai-sw
BSSAP messaging
The A-interface and the Lb-interface carry C7 BSSAP messaging. The four types of BSSAP
messaging on these interfaces are:
BSSMAP (-LE) on the BSS-based SMLC-BSS link (Lb Interface, a two-way SMLC-BSS
protocol).
BSSMAP on the MSC-BSS link (A-interface, a two-way MSC-BSS protocol).
DTAP (-LE) on the BSS-based SMLC-LMU link (a two-way SMLC-LMU protocol). The BSS
transparently forwards DTAP-LE messages which the BSS-based SMLC and LMU use to
communicate with each other. There is, however, no direct link between BSS-based SMLC
and LMU.
DTAP on the BSS-MS link (Air Interface, a two-way MSC-MS protocol). The BSS
transparently forwards DTAP messages which the MSC and MS use to communicate with
each other. There is, however, no direct link between the MSC and MS.
1-56 68P02901W01-S
Jul 2008
System Information: GSM Overview ISDN messaging
ISDN messaging
Integrated Services Digital Network (ISDN) messaging is provided from the mobile subscribers
and extends throughout the terrestrial network, including other PLMNs.
MSC to MS
The BSS Application Part (BSSAP) of C7 specifies the MSC-MS interface. The two types of
BSSAP messaging on these interfaces are:
BSSMAP on the MSC-BSS link (A Interface).
DTAP on the BSS-MS link (Air Interface).
Location register interfaces
For the interfaces between the MSC, VLR, HLR, and EIR, the lower level communication
functions also follow the ITU-TSS recommendations for C7. At the application level, the GSM
specifies the messages used on these interfaces as the Mobile Application Part, or MAP.
OMC interfaces
For the interfaces between the OMC and the other network elements, X.25 and OSI upper layer
protocols are used as specified by ISO open standards.
NMC interface
GSM defines the interface between the NMC and OMC to use a Q3 protocol on a 64 kbps
digital link.
68P02901W01-S 1-57
Jul 2008
Interface summary Chapter 1: Introduction to Motorola GSM
Interface summary
Table 1-6 summarizes the GSM Interfaces.

Table 1-6 GSM interface summary
Interfacing network Main messaging

Interface name
elements protocols used
GSM Air interface BTS to MS DTAP/LAPDm
interfaces Abis interface BSC to remote BTS DTAP/LAPD
A interface BSC to MSC BSSMAP/SCCP
B interface MSC to VLR on C7 X 25
C interface MSC to HLR/AUC MAP/TCAP/SCCP on C7
D interface VLR to HLR MAP/TCAP/SCCP on C7
E interface MSC to MSC MAP/TCAP/SCCP on C7
F interface MSC to EIR MAP/TCAP/SCCP on C7
G interface VLR to VLR MAP/TCAP/SCCP on C7
H interface HLR to AUC MAP on C7
Lb interface BSS to BSS based No specified protocol
SMLC BSSLAP/BSSMAP/SCCP
on C7
External MSC to PSTN TUP on C7
interfaces MSC to ISDN ISUP on C7
OMC to all network OMAP on X 25
elements
Signaling links
The signaling links between the various network elements are listed in Table 1-7.
Table 1-7 Network element signaling links
Element Link
Remote BTS-to-BSC Radio Signaling Link (RSL)
BSC-to-BSS based SMLC Location Services Message Transfer Link (MTL)
OMC(R)-to-BSS Operation and Maintenance Link (OML)
Remote XCDR-to-BSC XCDR signaling Link (XBL)
CBC-to-BSC Cell Broadcast Link (CBL)
1-58 68P02901W01-S
Jul 2008
System Information: GSM Overview The A interface
The A interface
The interface between the MSC and the BSS is a standard interface, called the A Interface. The
A Interface is fully defined in the GSM recommendations.
The signaling portion of the interface between the MSC and the BSC uses the C7 protocol, for
which application parts are defined. For example, the Base Station System Application Part
(BSSAP).
The A Interface allows customers to purchase the switching equipment (for example, the MSC)
from one supplier, and the radio equipment (such as the BSS) from another supplier, and still
have equipment compatibility.
For support of location services, there are modifications to the A-interface: changes to various
protocols to support SMLC-BSS signaling through the MSC when the SMLC is NSS-based.
The new messages for the Motorola implementation of location services for the BSSMAP
protocol are:
BSSMAP Connection Oriented Information
BSSMAP Connectionless Information
A new protocol, BSSLAP, has also been added. This protocol is used for SMLC-BSS
communication as well as a carrier for SMLC-MS messages. The BSSLAP messages, which are
supported are:
BSSLAP TA Request
BSSLAP TA Response
BSSLAP MS Position Command
BSSLAP MS Position Response
BSSLAP Abort
BSSLAP Reset
BSSLAP Reject
Abis interface
The GSM defined interface between the BSC and the remotely located BTS equipment is called
the Abis interface. It uses Link Access Procedure D (LAPD).
At the application levels, GSM defines a special set of messages unique to the mobile application.
68P02901W01-S 1-59
Jul 2008
Air interface Chapter 1: Introduction to Motorola GSM
Mobis
The Motorola defined BSC-to-BTS interface is a modification of the Abis standard called Mobis.
It distributes functionality between the BSC and the remote BTS equipment, and offers several
advantages:
Reduced signaling link traffic which permits efficient use of E1 links. The BTS performs
handover data processing. This reduces the amount of data sent to the BSC over the
signaling link and significantly reduces the amount of processing required in the BSC.
Better synchronization of the BSC and BTS ensuring better handover from one traffic
channel to another.
Improved overload control and fault recovery algorithms.
Efficient use of the paging and access grant channels.
Control of more than one BTS (sectors) on a single control link.
For support of location services, the Mobis interface is modified to support new BSC-BTS
signaling for location services. The following messages are new for this interface:
Ta request
Ta response
Application information
Air interface
The GSM recommendations include detailed specifications for the radio channel (Air Interface)
between the MS and the BTS. The Air Interface uses a three layer protocol.
Layer 1 (physical channel)
Layer 1 is the physical channel layer. This layer transmits and receives coded information
symbols over the radio link. Layer 1 provides the basic time division multiplexing (TDM)
frame structure including timeslot, frame, multiframe, and so on. Layer 1 also provides for
multiplexing and demultiplexing (channel encoding or decoding) of the different types of logical
channels that the network requires, such as traffic channels, signaling or control channels and
synchronization channels.
Layer 2 (logical channel)
Layer 2 is a transport mechanism between layer 3 and layer 1. Layer 2 provides for error
free transport of layer 3 signaling.
1-60 68P02901W01-S
Jul 2008
System Information: GSM Overview Lb interface
Layer 3 (network control)
Layer 3 provides three major network management functions:

Radio resource management (paging, cipher mode setting, frequency redefinition, channel
assignments, handover, and measurement reports).
Mobility management (authentication, location updating, International Mobile Subscriber

Identity (IMSI) attach/detach, periodic registration, and ID confidentiality).
Call management (call setup, supplementary services, dual tone multifrequency (DTMF),
and short message service).
Support for location services
A new message has been added to the RR protocol for transport of SMLC-MS messages. The
new message is RR Application Information.
RR Application Information.
In addition, 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, but they are
restricted in the messages they can send or accept.
Lb interface
The Lb-interface is for the support of location services. It is located between the BSS and a
BSS-based SMLC. The interface uses a C7 protocol, and is modeled (from the BSS viewpoint)
from the A-Interface. The interface is not present when the SMLC is NSS-based.
At the physical level, the interface supports one or multiple 64 kbps signaling timeslots on E1
signaling link. By convention, these timeslots are typically placed only on timeslot 16 of a given
E1 signaling link. The Lb-interface, like the A-interface, may consist of one or multiple E1s
between the BSS and the BSS-based SMLC. Unlike the A-Interface, no traffic carriers (CICs) are
present on the E1 links (this could change in the future if LMUs on a TCH must be supported).
The Lb-interface fully supports all procedures in the MTPL2, MTPL3, and SCCP protocols.
BSSMAP messages supported
For BSSMAP, the following messages are supported:

BSSMAP Clear Command.
BSSMAP Clear Complete.
BSSMAP Clear Request.
68P02901W01-S 1-61
Jul 2008
Lb interface Chapter 1: Introduction to Motorola GSM
BSSMAP Complete Layer 3 Information.
BSSMAP Paging.
BSSMAP Confusion.
BSSMAP Classmark Update.
BSSMAP Handover Required.
BSSMAP Handover Required Reject.
BSSMAP Handover Performed.
BSS map enhancement
An enhancement to BSSMAP has been created for the Lb-interface called BSSMAP-LE. The
messages used for the BSSMAP-LE protocol are:
BSSMAP-LE Perform Location Request.
BSSMAP-LE Perform Location Response.
BSSMAP-LE Perform Location Abort.
BSSMAP-LE Connection Oriented Information.
BSSMAP-LE Connectionless Information.
BSSMAP-LE Reset.
BSSMAP-LE Reset Acknowledge.
DTAP messages supported
For DTAP, the following messages are supported:

RR Paging Response.
All MM messages.
DTAP enhancements
An enhancement to DTAP has been created for the Lb-interface called DTAP-LE. This is used for
SMLC-LMU communication. The messages used for DTAP-LE are:
DTAP-LE Register.
DTAP-LE Facility.
DTAP-LE Release Complete.
1-62 68P02901W01-S
Jul 2008
System Information: GSM Overview Lb interface
BSSLAP protocol
A new protocol, BSSLAP, has been created for direct SMLC-BSS communication, as well as a
carrier for SMLC-MS messages. The messages used for BSSLAP are:
BSSLAP TA Request.
BSSLAP TA Response.
BSSLAP MS Position Command.
BSSLAP MS Position Response.
BSSLAP Abort.
BSSLAP Reset.
BSSLAP Reject.
68P02901W01-S 1-63
Jul 2008
Network protocols Chapter 1: Introduction to Motorola GSM
Network protocols

Protocol types
The network protocols define the format of communication between two network entities.
The network protocols are:

E1 PCM
X.25
ITU-TSS Signaling System 7 (C7)
NOTE
ITU-TSS was previously known as CCITT. Signaling System 7 (C7) is sometimes
referred to as SS7.
Link Access Procedure D (LAPD)
Link Access Procedure Dm (LAPDm)
X.25 and C7 information is sent using the physical protocols on the E1 links.
1-64 68P02901W01-S
Jul 2008
System Information: GSM Overview OSI/protocol relationship
OSI/protocol relationship
Figure 1-17 shows the relationship between the OSI layers and the main protocols. Figure 1-18
shows the overall network protocols. The individual C7 protocols are shown, but not the
interfaces on which these protocols are used.
Figure 1-17 OSI layers - main protocol relationships
68P02901W01-S 1-65
Jul 2008
OSI/protocol relationship Chapter 1: Introduction to Motorola GSM
Figure 1-18 Network protocols
NMC CBE
PSTN
OMC-S OMC-R CBC

C7
X.25 LAPB X.25
RXCDR
EIR EC
LAPD
C7
BSC
MSC
IWF LAPD LAPD
HLR VLR
BTS BTS
AUC
Base Station System
LAPDm
Mobile Station (MS)

ME
SIM
ti-GSM-Networkprotocols-00037-ai-sw
1-66 68P02901W01-S
Jul 2008
System Information: GSM Overview ITU-TSS signaling system 7
ITU-TSS signaling system 7
The ITU-TSS signaling system 7 (C7) protocol is composed of several parts: the Message
Transfer Part (MTP), the Signaling Connection Control Part (SCCP), the X.25 link, the LAPDm
protocol, and various signaling link protocols.
Message Transfer Part (MTP)
MTP is part of the C7 protocol that is used throughout the network. MTP provides layers 1, 2
and 3 of the seven layer model. MTP is the transport system for reliable transfer of messages
between users.
The three functions involved in MTP are:

MTP1 - Signaling data link functions
Physical, electrical, and mechanical specifications for the interface.
MTP2 - Signaling link functions
Defines the functions and procedures for controlling the transfer of signaling messages
over a signaling link.
MTP3 - Signaling network functions
Defines the methods for message handling and routing on a signaling link.
MTP uses three types of Signaling Units (SU) to transmit information:

MSU - Message Signaling Unit.
LSSU - Link Status Signaling Unit.
FISU - Fill-In Signaling Unit.
Signaling Connection Control Part (SCCP)
The SCCP is a layer 3 protocol and provides network connectivity as required.
The SCCP forms part of the Signaling Information Field (SIF) in the MTP signaling unit.
The SCCP can operate in four modes. Two of these modes are used for GSM. Protocol class
numbers carried in the mandatory fixed field of the SCCP message indicate which mode is
being used. The two modes used for GSM are:
Connectionless. Protocol Class 0 - Single messages are sent to other SCCP users. The Unit
Data (UDT) is the only type of message sent in connectionless mode.
68P02901W01-S 1-67
Jul 2008
X.25 Chapter 1: Introduction to Motorola GSM
Connection-oriented. Protocol Class 2 - A signaling connection is established before

messages are sent. Pass the following SCCP message types to establish this connection:
CR - Connection Request
CC - Connection Confirm
CREF - Connection Refused
DT1 - Data form 1
IT - Inactivity Test
Once the communication is complete, the link must be released. The following SCCP
message types are used to release the connection:
RLSD - Released.
RLC - Release Complete.
X.25
The X.25 link uses LAPB and LAPD protocols for layer 2 messaging. Both LAPB and LAPD
protocols are variants of HDLC:
LAPB is used on the OML.
LAPD is used on Mobis, the XBL, and the RSL.
LAPDm
The LAPDm protocol is a variation of LAPD link protocol used exclusively on the Air Interface.
Signaling link protocols
The link protocols used on the signaling links are as follows:

RSL (Remote BTS-to-BSC) LAPD
MTL (BSC-to-MSC) C7 MTP-SCCP
OML (OMC(R)-to-BSS) X.25 LAPB
XBL (RXCDR-to-BSC) X.25 LAPD
CBL (CBC-to-BSC) X.25
1-68 68P02901W01-S
Jul 2008
System Information: GSM Overview GSM frequencies and channels
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 both decimal
and hexadecimal notation.
Table 1-8 lists and describes GSM, DCS, and PCS frequency types.
Table 1-8 GSM Frequency types
Frequency range Description

GSM850 The GSM 850 MHz frequency range.
PGSM900 The standard GSM 900 MHz frequency range.
EGSM The Extended GSM frequency range (additional 10 MHz of
bandwidth).
DCS1800 The standard DCS1800 MHz frequency range.
PCS1900 The higher frequency range allocated in countries such as
the USA.
GSM850 frequencies
GSM850 systems use radio frequencies between 824-849 MHz for receive and between 869-894
MHz for transmit, as shown in Figure 1-19. RF carriers are spaced every 200 kHz, allowing a
total of 124 carriers for use. Other frequencies between 851 MHz and 869 MHz are available
for use by other (non-GSM) cellular systems. A guard band of 2 MHz of unused frequencies
between 849 MHz and 851 MHz protects against interference between the transmit and receive
frequencies. Guard bands between GSM and non-GSM frequencies depend on the prevailing
standards in the country concerned and on agreements reached by network operators. Any
such guard bands are likely to be small, for example, the last carrier of the frequency range
is left unused.
Transmit and receive frequencies are separated by 45 MHz, and this fixed frequency gap
reduces the possibility of interference.
68P02901W01-S 1-69
Jul 2008
GSM850 channels Chapter 1: Introduction to Motorola GSM
Figure 1-19 GSM850 frequency range
GSM850 channels
Channels 128-130
Table 1-9 shows the frequencies for GSM850 channels 128 to 130.
Table 1-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
1-70 68P02901W01-S
Jul 2008
System Information: GSM Overview GSM850 channels
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
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
68P02901W01-S 1-71
Jul 2008
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
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
1-72 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-73
Jul 2008
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
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
1-74 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-75
Jul 2008
Channels 231-240
Table 1-20 shows the frequencies for GSM850 channels 231 to -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
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
1-76 68P02901W01-S
Jul 2008
System Information: GSM Overview Primary GSM900 frequencies
Primary GSM900 frequencies
This section lists all the frequencies used in Primary GSM (PGSM), with their channel numbers
in both decimal and hexadecimal notation.
GSM900 systems use radio frequencies between 890 MHz and 915 MHz for receive and
between 935 MHz and 960 MHz for transmit, as shown in Figure 1-20. RF carriers are spaced
every 200 kHz, allowing a total of 124 carriers for use. Other frequencies between 917 MHz and
935 MHz are available for use by other (non-GSM) cellular systems. A guard band of 2 MHz
of unused frequencies between 915 MHz and 917 MHz protects against interference between
the transmit and receive frequencies. Guard bands between GSM and non-GSM frequencies
depend on the prevailing standards in the country concerned and on agreements reached by
network operators. Any such guard bands are likely to be small; for example, the last carrier of
the frequency range is left unused.
Figure 1-20 GSM900 frequency range
68P02901W01-S 1-77
Jul 2008
Primary GSM900 channels Chapter 1: Introduction to Motorola GSM
Primary GSM900 channels
Channels 1-10
Table 1-22 shows the frequencies for Primary GSM (PGSM) channels 1 to 10.
Table 1-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 1-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
1-78 68P02901W01-S
Jul 2008
System Information: GSM Overview Primary GSM900 channels
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
68P02901W01-S 1-79
Jul 2008
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
1-80 68P02901W01-S
Jul 2008
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
68P02901W01-S 1-81
Jul 2008
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
1-82 68P02901W01-S
Jul 2008
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
68P02901W01-S 1-83
Jul 2008
EGSM frequencies Chapter 1: Introduction to Motorola GSM
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
EGSM frequencies
This section lists all the extra frequencies used in Extended GSM (EGSM), with their channel
numbers in both decimal and hexadecimal notation. EGSM also uses all frequencies listed in
PGSM frequencies and PGSM channels.
Figure 1-21 shows that further 10 MHz of bandwidth on both transmit and receive allocations
has now extended the GSM900 bandwidth.
Figure 1-21 EGSM frequency range
1-84 68P02901W01-S
Jul 2008
System Information: GSM Overview EGSM channels
BCCH frequency, SDCCH in EGSM
This feature supports the following configurations:

Stand alone extension band system.
Dual band system with EGSM and DCS1800.
Extension band system with origination across the entire 35 MHz (BCCH+SDCCH in
EGSM).
Ensuring handovers stay on EGSM band
The advanced load handover management function offers, the operator, the ability to specify
EGSM band handovers only to other EGSM bands. Otherwise EGSM handovers can occur to
neighboring cells that do not have an EGSM band available. DCS1800 band is used wastefully,
particularly if the band_preference parameter is set, for example, to DCS1800. A new
parameter bss_egsm_alm_allowed enables the feature and EGSM handovers occur only to
EGSM sites, whatever the setting of band_preference.
EGSM channels
Channels 975-984
Table 1-35 shows the frequencies for EGSM channels 975 to 984.
Table 1-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
68P02901W01-S 1-85
Jul 2008
EGSM channels Chapter 1: Introduction to Motorola GSM
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
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 930.60
1003 3EB 885.80 930.80
1004 3EC 886.00 931.00
1-86 68P02901W01-S
Jul 2008
System Information: GSM Overview EGSM channels
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
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
68P02901W01-S 1-87
Jul 2008
DCS1800 frequencies and channels Chapter 1: Introduction to Motorola GSM
DCS1800 frequencies and channels

DCS1800 frequencies
This section lists the frequencies used in Digital Cellular System (DCS) 1800, with their channel
numbers in both decimal and hexadecimal notation.
DCS1800 systems use radio frequencies between 1710-1785 MHz for receive and between
1805-1880 MHz for transmit, as shown in Figure 1-22. RF carriers are spaced every 200 kHz,
allowing a total of 373 carriers for use, with one used as a guard band. A guard band of 20 MHz
of unused frequencies between 1785 MHz and 1805 MHz protects against interference between
the transmit and receive frequencies. There is a 100 kHz guard band between 1710.0 MHz and
1710.1 MHz and between 1784.9 MHz and 1785.0 MHz for receive, and between 1805.0 MHz
and 1805.1 MHz and between 1879.9 MHz and 1880.0 MHz for transmit.
Figure 1-22 DCS1800 frequency range
1-88 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
DCS1800 channels
Channels 512-520
Table 1-40 shows the frequencies for DCS1800 channels 512 to 520.
Table 1-40 DCS1800 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
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
68P02901W01-S 1-89
Jul 2008
DCS1800 channels Chapter 1: Introduction to Motorola GSM
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
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
1-90 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-91
Jul 2008
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
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
1-92 68P02901W01-S
Jul 2008
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

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
68P02901W01-S 1-93
Jul 2008
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
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
1-94 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-95
Jul 2008
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
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
1-96 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-97
Jul 2008
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
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
1-98 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-99
Jul 2008
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
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
1-100 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-101
Jul 2008
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
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
1-102 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-103
Jul 2008
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
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
1-104 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-105
Jul 2008
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
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
1-106 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-107
Jul 2008
PCS1900 frequencies and channels Chapter 1: Introduction to Motorola GSM
PCS1900 frequencies and channels

PCS1900 frequencies
This section lists the frequencies used in PCS1900, with their channel numbers in both decimal
and hexadecimal notation.
PCS1900 systems use radio frequencies between 1850-1910 MHz for receive and between
1930-1990 MHz for transmit, as shown in Figure 1-23. RF carriers are spaced every 200 kHz,
allowing a total of 299 carriers for use. A guard band of 20 MHz of unused frequencies between
1910 MHz and 1930 MHz protects against interference between the transmit and receive
frequencies. There is a 100 kHz guard band between 1850.0 MHz and 1850.1 MHz and between
1909.9 MHz and 1910.0 MHz for receive, and between 1930.0 MHz and 1930.1 MHz and
between 1989.9 MHz and 1990.0 MHz for transmit.
Figure 1-23 PCS1900 frequency range
1-108 68P02901W01-S
Jul 2008
System Information: GSM Overview PCS1900 channels
PCS1900 channels
Channels 512-520
Table 1-78 shows the frequencies for PCS1900 channels 512 to 520.
Table 1-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
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
68P02901W01-S 1-109
Jul 2008
PCS1900 channels Chapter 1: Introduction to Motorola GSM
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
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
1-110 68P02901W01-S
Jul 2008
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

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
68P02901W01-S 1-111
Jul 2008
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
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
1-112 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-113
Jul 2008
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
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
1-114 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-115
Jul 2008
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
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
1-116 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-117
Jul 2008
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
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
1-118 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-119
Jul 2008
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
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
1-120 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-121
Jul 2008
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
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
1-122 68P02901W01-S
Jul 2008
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
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
68P02901W01-S 1-123
Jul 2008
1-124 68P02901W01-S
Jul 2008
Chapter
BSS General Description

This chapter provides a general description of the Motorola Base Station System (BSS), which
forms part of the GSM digital cellular system.
The GSM recommendations define the functions of the BSS, but allow flexibility in its design.
This chapter also describes some of the unique features of the Motorola BSS.

BSC description on page 2-5.
BTS description on page 2-7.
BSS site configuration on page 2-10.
Network topology on page 2-16.
BSS standardized interfaces on page 2-20.
BSS standardized interfaces on page 2-20.
Cell system radio channel reuse on page 2-27.
BSS redundancy on page 2-31.
General packet radio service on page 2-33.
PCU overview on page 2-40.
PCU features on page 2-42.
PCU description on page 2-51.
PCU architecture on page 2-54.
PCU interfaces on page 2-60.
PCU system and control functions on page 2-64.
68P02901W01-S 2-1
Jul 2008
Base station system Chapter 2: BSS General Description
Base station system

BSS purpose and functions
The BSS is the interface between the Mobile Station (MS) and the Mobile services Switching
Center (MSC) elements of the network.
The BSS performs a variety of functions. The following comprise the functions provided by the
BSS:
Radio coverage areas and control functions for one or more cells.
Radio coverage areas and control functions for the MSs in the cells.
Signaling data processing and routing of the traffic data exchanged between the MS
and the MSC.
Digital signal interfaces to the land circuits linking the BSS and the MSC.
Links
The BSS has links to the MSC and the MSs. The following comprise the links:
Interface links
Land circuits link the Base Station Controller (BSC) to the MSC. Each interface link contains a
multiplexed E1 serial data stream. The BSS places MS originated or MS terminated subscriber
(signaling or traffic) data in a timeslot (channel) on a serial data stream.
Air interface link
The communication link, or Air Interface, between the BSS and the MS uses digital radio
techniques.
BSS to MSC link
The BSS-to-MSC interface uses E1 links.
2-2 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS network elements
BSS network elements
The BSS consists of three basic Network Elements (NEs). The following comprise the network
elements:
Base Station Controller (BSC).
Base Transceiver Stations (BTSs) assigned to the BSC.
Speech transcoder (XCDR) or remote speech transcoder (RXCDR) assigned to the BSC.
Typical BSS layout
Figure 2-1 shows the layout of a typical system with two BSSs. Each BSS contains several
components to make the link between the MS and the MSC. The BSS components are described
in more detail in the following sections.
68P02901W01-S 2-3
Jul 2008
Typical BSS layout Chapter 2: BSS General Description
Figure 2-1 Dual BSS system
BSS #1 BSS #2
MS
BTS
SITE
MS MS
BTS
SITE
BTS BTS
MS SITE
SITE
BSC
SITE
WITH BTS
XCDR SITE
MS
BTS
SITE
BSC
SITE
BTS
SITE
RXCDR
(NOTE 2)
A MSC
LEGEND
Air Interface
A A Interface PSTN/ISDN/PUBLIC DA TA NETWORK
NOTE
(1) DASHED LINES ENCLOSE NETWORK COMPONENTS
OF A PARTICULAR BSS AND DO NOT SHOW THE BSS
SER VICE AREA.
(2) REMOTE TRANSCODING (RXCDR) IS LOCA TED AT
MSC SITE, BUT IS P ART OF BSS #2.
ti-GSM-Dual BSS-00043-ai-sw
2-4 68P02901W01-S
Jul 2008
System Information: GSM Overview BSC description
BSC description

BSC purpose and functions
The BSC network element provides the control for the BSS. It controls and manages the
associated BTSs, and interfaces with the Operation and Maintenance Center (OMC).
The purpose of the BSC is to perform a variety of functions. The following comprise the
functions provided by the BSC:
Controls the BTS components.
Performs Call Processing.
Performs Operation and Maintenance (O and M).
Provides the Operation and Maintenance link (OML) between the BSS and the OMC.
Provides the A Interface between the BSS and the MSC.
Manages the radio channels.
Transfers signaling 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 signaling and traffic data to BSCs. The BSCs provide
the opportunity for remote switching, distributed control, and traffic concentration.
Many types of call handling signal do not affect the BSC directly. In these cases, the BSC serves
as a relay point between an MS and the MSC.
Digital switching matrix
The BSC includes a digital switching matrix. There is no fixed correspondence between the
radio channels at the BSS and the terrestrial circuits (trunks), which connect the BSS to the
MSC. While the BSC selects the radio channel, the MSC selects the trunks.
The BSC connects the traffic channel (TCH) assigned to a particular MS with the trunk assigned
by the MSC.
The switching matrix also lets the BSS perform handovers within a single BSS without involving
the MSC.
68P02901W01-S 2-5
Jul 2008
Terrestrial circuit device management Chapter 2: BSS General Description
Terrestrial circuit device management
This feature enables CICs to be identified in three ways: By CIC number, on the MMS basis, on
the MMS basis providing timeslot and, if appropriate, group within a timeslot.
BSC capacity
Scalable BSC capacity is enabled through the further exploitation of the increased processing
performance and memory of the GPROC2/ GPROC3. As a result GPROC2s and/or GPROC3s are
required throughout the BSC. The BSC maximum capacity is increased as shown in Table 2-1.
{28398}
Table 2-1 BSC maximum capacities
Parameter GSR 7 GSR 8 GSR 9

Sites 100 100 100c
Cells 250 250 250
Carriers (RTFs) 384a 384a 384c
DRIs 512 512 512c
RSLs 250 250 250
PCUs 3 3 1
GSLs 180b 180b 60
MMSs 128 128 192
PATHs 250 250 250
DHPs 232 232 232
LCFs 25 25 25
Trunks 2400a 2400a 2400c
C7 links to MSC 16 16 16
C7 links to SMSC 16 16 16
E1 links 102 102 192
a Can be increased to 512 carriers and 3200 trunks if
the optional enhanced BSC capacity feature is enabled.
b 60 per PCU.
c Can be increased to 140 sites, 750 carriers, and 4800 trunks only if the optional
increased network capacity feature is enabled.
This increased capacity is achieved through the deployment of GPROC2s, GPROC3s for each
function at the BSC, including Base Station Processor (BSP) and Link Control Function (LCF).
BSCs for a given capacity are available, with hardware and software, according to the required
capacity.
2-6 68P02901W01-S
Jul 2008
System Information: GSM Overview BTS description
BTS description

BTS purpose and functions
The BTS network element consists of the hardware components, such as radios, interface
modules and antenna systems. The network elements provide the Air Interface between the
BSS and the MSs.
The BTS radio equipment used must be able to support the type of operation required, that is,
GSM900, EGSM900, DCS1800, or PCS1900. Refer to GSM frequencies and channels on
page 1-69 for an explanation of the characteristics of these systems.
The BTS provides radio channels (RF carriers) for a specific RF coverage area. The radio
channel is the communication link between the MSs within the RF coverage area and the
BSS. A single BTS site contains all the BTS network components that provide RF channels for
the same geographic area.
The BTS also has a limited amount of control functionality, which reduces the amount of traffic
between the BTS and BSC.
Frequency reuse plan
The frequency reuse plan for the cellular system defines:

The RF coverage area of each cell.
The number of RF channels in each cell.
The RF frequency of the channels that each BTS site in the network provides.
The reuse plan of RF frequencies across multiple cells.
RF coverage areas
The term, cell defines a single RF coverage area which is either a multidirectional and sectored
area, or an omnidirectional single area.
A BTS site can provide either of the following:

An omnidirectional RF coverage area, singular and undivided.
Multidirectional RF coverage area divided into sectors.
The antenna system at the BTS site determines the type of RF coverage area.
68P02901W01-S 2-7
Jul 2008
Antenna systems Chapter 2: BSS General Description
Antenna systems
BTS site equipment (RF hardware) can be configured for operation with the following types
of antenna systems for RF coverage areas:
One omnidirectional sector.
Two directional sectors (for use along highways).
Three directional sectors (120 or alternate 60).
Six directional sectors (60).
2-8 68P02901W01-S
Jul 2008
System Information: GSM Overview Transcoder description
Transcoder description

Transcoder purpose and functions
The speech transcoder (XCDR) is the digital signal processing equipment that performs GSM
defined speech encoding and decoding within the network.
The speech transcoder is the interface between the 64 kbps PCM channel in the land network
and the 13 kbps vocoder (22.8 kbps after channel coding) channel used on the Air Interface.
This reduces the amount of information carried on the Air Interface and hence, its bandwidth.
NOTE
13 kbps is the data rate of speech. This is mapped onto 16 kbps Transcoder
Rate Adaption Unit (TRAU) frames and then channel coded for protection, finally
comprising 22.8 kbps.
The transcoder can multiplex four traffic channels (with GSM or AMR half rate, eight traffic
channels are possible in the optimum case) into a single 64 kbps channel (timeslot). Therefore,
an E1 serial link can carry four times as many channels which can reduce the number of E1
leased lines required to connect remotely located equipment.
Remote transcoder
Speech transcoding can take place either at the BSC or between the MSC and BSC. When the
transcoder is between the MSC and the BSC it is called a remote transcoder (RXCDR).
Transcoding location
The location of the XCDR affects the overall cost of leased lines.
Transcoding at the BSC
If transcoding takes place at the BSC, then the number of leased lines required to connect the
BSC to the required BTSs is reduced.
Remote transcoding at the MSC
If transcoding takes place remotely at the MSC, then the number of leased lines from the MSC
(RXCDR) to the BSC is also reduced, thus providing greater savings.
68P02901W01-S 2-9
Jul 2008
BSS site configuration Chapter 2: BSS General Description
BSS site configuration

Introduction to BSS site configuration
The Motorola BSS uses a variety of BSC, BTS, and RXCDR site configurations to meet a wide
range of requirements.
The following items must be considered when meeting requirements for cell site configuration:
The number of RF carriers.
The distribution of the RF carriers at a site.
The type of transmit channel combining.
The number of RF carriers configured for frequency hopping.
The antenna configuration.
The number of E1 links for traffic/signaling channels.
The speech transcoder location.
The equipment redundancy provided for the sites.
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:
A BSC site.
Up to 100 BTS sites.
An RXCDR site is necessary if XCDR functionality is not integrated with the BSC. However,
note that the RXCDR is considered a separate site which is not part of the BSS.
Flexibility
Motorola BSS equipment uses a flexible architecture that expands easily. The BSC, BTS, and
RXCDR can start small and expand incrementally. The size of the Motorola BSC provides
significant switching capability to handle a variety of different BTS sites and network
configurations.
2-10 68P02901W01-S
Jul 2008
System Information: GSM Overview Definitions
Definitions
BSC
Provides the BSC function for controlling BTS sites. A Base Station System Control (BSSC)
cabinet can contain the necessary modules for the BSC-to-BTS line interface and for the
BSC-to-MSC line interface, acting as different BSCs. Alternatively, the equipment can be
connected to form a single BSC.
RXCDR
Provides the RXCDR function for speech transcoding. For example, the BSSC2 cabinet, contains
the necessary modules for the BSC-to-RXCDR line interface and speech transcoder modules
as part of the line interface to the MSC. Alternatively, the two shelves can be combined for
more capacity.
Combined BSC and XCDR
The BSSC2 cabinet is equipped to provide both the BSC function for controlling BTS sites and
the XCDR function for speech transcoding within one shelf. Alternatively, it could have the BSC
in one shelf and the XCDR in the other. This cabinet contains the modules needed for the
BSC-to-BTS, BSC-to-MSC, and XCDR functions.
BSS maximum capacity
The maximum capacity of a BSS is 2400 trunks from the MSC (3200 with the Enhanced Capacity
option). This maximum is independent of the number of BTS sites.
In order to achieve 384 carriers for the BSC on the Dense Urban Call model (the primary
motivation for this feature), the following assumptions regarding the BSC are made:
Support of two Message Transfer Links (MTLs) per Link Control Function (LCF) at 40%
MTL link utilization.
Support of 25 LCFs.
GPROC2 processing is approximately four times that of a GPROC.
GPROC3 processing is almost two times that of a GPROC2.
NOTE
Increasing the number of trunks limit does not provide value for Dense Urban
environments unless these assumptions hold true.
68P02901W01-S 2-11
Jul 2008
BTS cabinet Chapter 2: BSS General Description
BTS cabinet
A BTS cabinet contains the radio transceivers and associated Air Interface modules that make
up the BTS function. The BTS cabinet can contain equipment for up to six RF carriers and
support up to three different RF coverage areas or sectors.
A BTS cabinet can be configured to provide the BTS functions only. For this type of cabinet,
the following are the BTS functions provided:
The Air Interface to the MSs.
The line interface to a remote BSC.
BSSC cabinet
A single Base Station System Control (BSSC) cabinet can provide:

The BSC function
The RXCDR function
The combined BSC and RXCDR function
The equipment configuration in the cabinet determines the functions.
BSS/MSC configurations
The following BSS equipment can be installed at an MSC:

A BSSC2 cabinet with the BSC function.
A BSSC2 cabinet with the XCDR speech transcoding function.
If a BSSC2 cabinet with the XCDR is not implemented, speech transcoding can be integrated
into the BSSC2 cabinet with the BSC function.
BSS with more than one BTS
Figure 2-2 shows examples of two BSSs, designated BSS #1 and #2, with more than one BTS
site. The BTS sites in these BSSs contain BTS cabinets that perform the BTS function only; they
do not include the BSC function or transcoding.
A separate BSC site operates the BTS sites of BSS #1 remotely. The BSSC2 cabinet for this
BSS integrates transcoding for this BSS with the BSC function.
A separate BSC operates the BTS sites of BSS #2 remotely. Transcoding for this BSS is located
remotely in a BSSC2 cabinet at the MSC site.
2-12 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS with more than one BTS
Figure 2-2 Multiple BTS sites per BSS


(NON-TRANSP ARENT
MODE)
RXCDR OMC-G
(Including Shelf
Manager)
OMC-R
BSC PCU ISS SGSN GGSN
BSSn GSN
BTSs COMMHUB
BSS2 GSNn
BSS1 GSN1
OPERA TOR SER VER

COMPLEX
- RADIUS SER VER
- DHCP SER VER
- DNS SER VER
ti-GSM-GSM equipmentarchitecture-00020-ai-sw
For correct implementation of the multiple BTS feature, the BSS supports the following
functionality:
Non-imperative handover rejection
If an incoming non-imperative handover causes congestion relief procedures to be triggered,

the BSS rejects it. If the handover is for congestion relief and the handover itself leads to the
invocation of congestion relief, the BSS does not allow an incoming handover.
Congestion relief handover retry
The source cell does not attempt a congestion relief handover, to a target cell which had rejected
a previous handover attempt. The attempt is not made for a period of time, both imperative
and congestion relief. A new timer element is used to control this period of time. It does not,
however, affect any imperative handover retries. These handovers are allowed to take place
regardless of such timers, as they have to keep the call active.
68P02901W01-S 2-13
Jul 2008
Flexible neighbor cell processing Chapter 2: BSS General Description
Incoming handover requests
If a BSS target cell rejects an incoming handover, the target cell attempts to inform the source
cell of its future, intra-BSS only accessibility status. The rejection is because that handover
would trigger congestion relief procedures. If the target cell is configured to optionally invoke
congestion relief procedures after rejecting the handover request, then it is capable of handling
the necessary handovers.
If a BSS target cell accepts an incoming handover, the target cell does not trigger any handover
attempts back to the source cell. The acceptance occurs when the handover itself triggers
the target cell congestion relief procedures.
Handover retry
The source cell optionally retries an imperative, intra-BSS only handover to target cells, which
rejected the initial handover request and initiated a congestion relief procedure.
Multiband mobile station redirection
If the servicing of a handover causes the percentage to exceed, the BSS does not allow an
incoming band preference handover. If such a handover is serviced, the net result is simply the
movement of a Multiband congestion problem from one cell to another.
Flexible neighbor cell processing
This feature enhances the existing handover decision process by adding more flexibility in the
way neighbor cell processing is handled for handovers.
This process has four blocks:
Neighbor with lower RXLEV readings
Neighbor cells with lower RXLEV readings than the servicing cell are valid candidates for
handovers.
Neighbors with low disuse counts
Neighbor cells whose disuse count is less than or equal to the maximum disuse count are valid
candidates for handovers.
Disuse count is defined as the number of consecutive measurement reports of a previously

reported neighbor cell, not reported by the Mobile.
Modified RXQUAL and RXLEV handover parameters
Neighbor cells use RXQUAL or RXLEV handovers only when the Base or the Mobile is at full
power. This feature removes all candidates for interference handovers until the mobile or the
base reaches full power (Applicable only for decision algorithm 1).
2-14 68P02901W01-S
Jul 2008
System Information: GSM Overview Flexible neighbor cell processing
Warm-up period for neighbor cells
This parameter allows no warm-up period for neighbor cells. Averaging and power budget
calculations begin immediately.
This feature uses an RXLEV of zero if missing a measurement report.
68P02901W01-S 2-15
Jul 2008
Network topology Chapter 2: BSS General Description
Network topology

Basic configurations
There are three basic ways to configure BSS sites:

Star (spoke) configuration.
Daisy chain configuration.
Fork configuration (used in conjunction with a daisy chain configuration).
Combinations of these configurations can be used to connect the BSC-to-remote BTS sites.
Topology model
Network topology is specified in terms of the continuous traffic routes between the BSC and
a terminating remote BTS site, including any intermediate remote BTS sites. Physical site
interconnections are through E1 links.
Figure 2-3 shows a possible topology using combinations of the three basic configurations. Site
interconnections in the figure represent E1 links, not traffic routes. The actual connections
between network sites can consist of single or multiple E1 links.
Figure 2-3 Topology model
The subsections that follow describe typical traffic routes for each configuration.
2-16 68P02901W01-S
Jul 2008
System Information: GSM Overview Star (spoke)
Star (spoke)
The traffic route is from the BSC site to terminating site BTS 10.
Open-ended daisy chain
Open-ended daisy chain traffic routes comprise the following:

The BSC site to terminating site BTS 12.
The BSC site through intermediate site BTS 12 to terminating site BTS 13.
The BSC site through intermediate sites BTS 12 and BTS 13 to terminating site BTS 14.
Daisy chain with fork and return loop to chain
Table 2-2 shows the main paths to the BSC for each BTS and the alternate path for each BTS
in the looped part of the network.
Table 2-2 BTS - BSC main and alternate paths (fork with return loop)
BTS site Main path through... Alternate path through...

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
If there is a fault anywhere in the fork, the return loop provides an alternative communications
route between the BSC and BTS 9.
For example, a break in the E1 links between BTSs 6 and 9 causes BTSs 5, 6, 7, 8 and 9 to
function like an open-ended chain. The chain allows site BTS 9 to communicate with the BSC.
68P02901W01-S 2-17
Jul 2008
Daisy chain with fork and return loop to BSC Chapter 2: BSS General Description
Daisy chain with fork and return loop to BSC
Table 2-3 shows that for each BTS, one main path and at least one alternate path exist to the BSC.
Table 2-3 BTS - BSC main and alternate paths (chain with return loop)
BTS site Main path through... Alternate path through...

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
If there is a fault anywhere in the chain, alternate paths provide each BTS site on the chain or
fork with an alternate communication route to the BSC.
For example, assume there is a break in the E1 link(s) between BTSs 2 and 3. BTSs 11, 2,
and 1 function like an open-ended chain and communicate with the BSC through the traffic
routes on the operational part of the loop. BTSs 3 and 4 function like an open-ended chain and
communicate with the BSC through the traffic routes on the operational part of the loop.
Drop and insert BTS site configuration
The drop and insert option enhances the flexibility of Motorola BSS equipment configuration.
This option allows a single E1 circuit to connect several BTS sites in either a linear daisy chain
or a ring topology. The closing end of the ring of BTS sites connects to a BSC.
Fault tolerance
A closed-loop or closed-ring topology enhances the fault tolerance of the drop and insert
configuration. This topology prevents any single line fault from interrupting communication
to any site.
Leased line saving
The Motorola drop and insert option for BTS sites saves on leased line costs when addressing
sparse rural or special coverage requirements such as highways.
GSM compliance
A maximum of 10 BTS sites can be chained together in a closed loop and still comply with GSM
system timing and delay recommendations.
2-18 68P02901W01-S
Jul 2008
System Information: GSM Overview Drop and insert BTS site configuration
Maximum size
Each BTS site in the drop and insert configuration has one or more BTS cabinets. While
chaining the maximum number of BTS sites together, each BTS cabinet in the drop and insert
configuration contains one radio transceiver and associated air interface modules. The cabinet
also contains modules to provide the line interfaces to a BSSC or a BTS cabinet.
If a particular site requires additional transceivers, the maximum number of sites chained
together must be reduced proportionately.
68P02901W01-S 2-19
Jul 2008
BSS standardized interfaces Chapter 2: BSS General Description
BSS standardized interfaces

Introduction to BSS standardized interfaces
Many GSM recommendations deal with standards for interfaces between network elements.
Motorola employs internationally recognized standards for most of the network communications.
For example, Motorola uses ITU-TSS Signaling System 7 (C7) and X.25 protocols extensively
throughout the network.
Using Standardized interfaces throughout the GSM digital cellular system ensures compatibility
of network elements from different manufacturers.
Protocol layering
The functional layering of protocols is based in part on the seven layer model for open systems
interconnection suggested by the International Standards Organization (ISO). Each layer
performs a specific set of functions that are isolated from the other layers. However, the
functions of a particular layer enhance the functions performed by the lower layers.
The following subsections detail the BSS-related equipment-to-equipment interfaces that are
standardized and specified by GSM.
A interface
The interface between the MSC and the BSS is a standard interface, called the A Interface. The
A Interface is fully defined in the GSM recommendations.
The signaling portion of the interface between the MSC and the BSC uses the C7 protocol.
Application parts are defined for the C7 protocol. For example, the base station system
application part (BSSAP) is defined.
The A Interface allows customers to purchase the switching equipment from different suppliers.
For example, the MSC from one supplier, and the radio equipment (such as the BSS) from
another supplier, and still have equipment compatibility.
Abis interface
The GSM defined interface between the BSC and the remotely located BTS equipment is called
the Abis interface. It uses Link Access Procedure D (LAPD).
At the application levels, GSM defines a special set of messages unique to the mobile application.
2-20 68P02901W01-S
Jul 2008
System Information: GSM Overview Air interface
Mobis
The Motorola defined BSC-to-BTS interface is a modification of the Abis standard called Mobis.
It distributes functionality between the BSC and the remote BTS equipment, and offers several
advantages:
Reduced signaling link traffic, which permits efficient use of E1 links. The BTS performs
handover data processing which reduces the amount of data sent to the BSC over the
signaling link. This significantly reduces the amount of processing required in the BSC.
Better synchronization of the BSC and BTS ensures better handover from one traffic
channel to another.
Improved overload control and fault recovery algorithms.
Efficient use of the paging and access grant channels.
Control of more than one BTS (sectors) on a single control link.
Air interface
The GSM recommendations include detailed specifications for the radio channel (Air Interface)
between the MS and the BTS. The Air Interface uses a three layer protocol.
Layer 1 (physical channel)
Layer 1 is the physical channel layer. This layer transmits and receives coded information
symbols over the radio link. Layer 1 provides the basic time division multiplexing (TDM)
frame structure including timeslot, frame, multiframe, and so on. Layer 1 also provides for
multiplexing and demultiplexing (channel encoding/decoding) of the different types of logical
channels that the network requires, such as traffic channels, signaling or control channels and
synchronization channels.
Layer 2 (logical channel)
Layer 2 is a transport mechanism between layer 3 and layer 1. Layer 2 provides for error
free transport of layer 3 signaling.
Layer 3 (network control)
Layer 3 provides three major network management functions:

Radio resource management (paging, cipher mode setting, frequency redefinition, channel
assignments, handover, measurement reports).
Mobility management (authentication, location updating, International Mobile Subscriber

Identity (IMSI) attach/detach, periodic registration, ID confidentiality).
Call management (call setup, supplementary services, Dual Tone Multi-Frequency (DTMF),
short message service).
68P02901W01-S 2-21
Jul 2008
Lb interface Chapter 2: BSS General Description
Lb interface
The Lb-interface is for the support of location services. It is located between the BSS and a
BSS-based SMLC. The interface uses the C7 protocol, and is modeled (from the BSS viewpoint)
from the A-Interface. The interface is not present when the SMLC is NSS-based.
2-22 68P02901W01-S
Jul 2008
System Information: GSM Overview Radio system and control functions
Radio system and control functions

Introduction to radio system and control functions
The Air Interface provides an associated control channel. This allows communication of signaling
control channel data simultaneously with (and transparent to) user traffic channel (TCH) data.
The associated control channel is available for both the uplink and the downlink. It allows
continuous information reporting from the MS to the BSS, and continuous control of the MS
from the BSS.
Handover
The GSM handover process uses a mobile assisted technique for accurate and fast handovers, to:
Maintain the user connection link quality.
Minimize interference.
Manage traffic distribution.
3-timeslot offset
The TDMA frame structure for uplink transmission is offset by three timeslots from the downlink
frame structure; this interval allows the MS to have only one synthesizer to assess the signal
level of adjacent cells. SACCH and other signaling information, which is sent transparently with
user traffic, allows continuous reporting of information from the subscriber to the base and the
continuous control of the mobile from the base.
Because of this offset, the MS never has to transmit and receive simultaneously. The ability of
the MS to change frequency and monitor a neighbor channel while engaged in a speech or data
conversation is important for the high performance MS assisted handover scheme employed.
MS assisted technique
The MS assists the handover decision process by performing certain measurements. When the
MS is engaged in a speech (or data) conversation, a portion of the TDMA frame is idle while
the rest of the frame is used for uplink (BTS receive) and downlink (BTS transmit) timeslots.
During the idle time period of the frame, the MS changes radio channel frequency and monitors
and measures the signal level of the six best adjacent cells.
Handover decision process
Measurements, which feed the handover decision algorithm are made at both ends of the
radio link.
68P02901W01-S 2-23
Jul 2008
Dynamic power control Chapter 2: BSS General Description
MS end
At the MS end, measurements are continuously signaled, through the associated control
channel, to the BSS where the decision for handover is ultimately made.
MS measurements include:
Serving cell downlink quality (bit error rate (BER) estimate).
Serving cell downlink received signal level, and adjacent cells downlink received signal
level.
The MS also decodes the Base Station ID Code (BSIC) from the six best adjacent cells, and
reports the BSICs and the measurement information to the BTS.
BTS end
At the BTS site end, measurements involve only the uplink communication path, link quality,
received signal level, and MS to BTS site distance. The measurements are available to the
handover algorithm. The MS RF transmit output power budget is also considered in the
handover decision. If an adjacent cell serves the MS at a lower power, the handover is
recommended. From a system perspective, handover is considered due to loading or congestion
conditions. In this case, the MSC or BSC tries to balance channel usage among cells.
Handover measurement summary
Figure 2-4 shows the measurements made for handovers.
Figure 2-4 Measurements made for handovers

Downlink
Uplink (Received) Level
(Received) Level Downlink
Quality (BER)
BTS Uplink
MS
(Base Tra nsceiver Quality (BER) Handover Control Adjacent Channel
Station) (Mobile Station)
Downlink Level
Subscriber-to-Base
Distance Adjacent Channel
Cell ID
ti-GSM-HO measurements-00046-ai-sw
Dynamic power control
As the MS gets closer to the BTS, both use less power to transmit. Over a 30 dB range, power
is stepped up or down in 2 dB steps. Power control reduces interference with other calls and
extends the battery life of MSs, which is important in hand portables.
2-24 68P02901W01-S
Jul 2008
System Information: GSM Overview Discontinuous transmission
Discontinuous transmission
The speech transcoder is equipped with a Voice Activity Detector (VAD) that detects the
presence of speech data. Transmission is stopped in the intervals when speech is absent. This is
called Discontinuous Transmission (DTx) of speech. The system operator controls this feature
and enables it in either or both directions.
The benefits of DTx include the following:

In portable units, transmit battery power is consumed only when it is needed for speech or
data.
The potential for interference is reduced since transmitters are only energized when
needed. This has the side-effect of improving the system spectrum efficiency.
The algorithm used to calculate the DTx maximizes the amount of off-time, while avoiding
speech clipping or distortion. The VAD encodes the silences in the speech pattern at a rate
of 500 bps rather than the full 13 kbps. The encoding produces background noise called
comfort noise, which reduces noise contrast effects. The continuous transmission of signaling
information is unaffected by DTx.
Discontinuous reception
Once the MS is in synchronization with the BTS (it uses the FCCH and SCH channels to get into
synchronization), it monitors two control channels: the Broadcast Control CHannel (BCCH) and
the Paging Channel (PCH). If the MS is not in use, it can determine when control information is
next due, and switch off between signals. This is called Discontinuous Reception (DRx). The
potential for 2% power cycling in standby extends battery life in MSs.
Timing adjustment
The TDMA bursts transmitted by MSs over the same radio channel must be kept apart for proper
recovery of received data at the BTS site. The MSs are not stationary, therefore propagation
delay of MS transmissions can vary. Sometimes the delay becomes significantly long and a burst
overlaps into the next timeslot. This causes undesirable errors in the recovered data.
Timing correction is provided to maintain the guard time needed between bursts. A closed loop
mechanism provides timing correction for the MS. The BSS detects changes in timing through a
timing advance algorithm. If necessary, the BSS sends timing advance messages to the MS,
commanding it to transmit earlier or later, as required, to offset the modified propagation delay.
In addition, the timing advance algorithm provides an estimation of the distance between
the MS and the BTS site. This distance estimation can be a valuable parameter in handover
decision algorithms.
68P02901W01-S 2-25
Jul 2008
Frequency synchronization Chapter 2: BSS General Description
Frequency synchronization
All BSS frequencies and timing signals are synchronized to a high stability reference oscillator
in the BSS. This oscillator can free run or be synchronized to the recovered clock signal from a
selected E1 serial link. Either case provides better than 0.05 ppm stability. MSs lock to a
reference contained in a synchronization burst transmitted from the BTS site. This reference
has a stability of 0.1 ppm.
BTS cabinet synchronization sources
Equipping one cabinet with reference clock circuits and distributing the synchronized reference
signals to other cabinets saves cost considerably in sites with collocated cabinets. This
distribution is through fiber optic cables.
Intelligent Multi Layer Resource Management (IMRM)
A full description of this feature is provided in Intelligent Multi Layer Resource Management
(IMRM) on page 4-100.
2-26 68P02901W01-S
Jul 2008
System Information: GSM Overview Cell system radio channel reuse
Cell system radio channel reuse

Introduction to cell system radio channel reuse
Each MS is assigned to one of eight traffic channels (timeslots) carried on an RF channel

transmit/receive frequency pair 200 kHz wide. The combination of digital channel coding
and GMSK modulation provides robust radio channel transmissions and the ability to operate
with a carrier/interference (C/I) level of 9 dB. The RF frequency reuse distance between cells
(or sectors) is directly proportional to the C/I level. Reuse distance is the minimum distance
that can separate co-channel cells or sectors and still deliver acceptable performance with a
tolerable amount of radio transmission interference.
Because the C/I level is relatively small, RF frequencies used in a cell can be reused in other
cells that are relatively small distance apart. Thus, the frequency reuse patterns are smaller,
which permits more frequency reuse within a geographic area.
GSM digital cellular systems typically use a 9-site omni or 4-site/3-sector pattern. A 2-site
(sectored) pattern, which requires a unique Motorola design, is also available.
9-site reuse pattern
Figure 2-5 shows how GSM cellular systems using a 9-site reuse pattern, are configured with
sites providing omnidirectional RF coverage areas. These sites provide about a 15 dB C/I
for 90% location reliability.
68P02901W01-S 2-27
Jul 2008
3-site 3-sector reuse pattern Chapter 2: BSS General Description
In this arrangement, the allocated frequencies are divided into 9 reuse groups.
Figure 2-5 9-site reuse pattern cellular system
3-site 3-sector reuse pattern
Figure 2-6 shows a GSM cellular system using a 3-site (3-sectored), 120 degree sector
arrangement. This system provides about a 12 dB C/I for 90% location reliability.
2-28 68P02901W01-S
Jul 2008
System Information: GSM Overview 4-site reuse pattern
Figure 2-6 3-site (sectored) cellular system
4-site reuse pattern
Systems using sites with three 120 RF coverage sectors provide about a 13.6 dB C/I for 90%
location reliability. This arrangement requires dividing the allocated frequencies into nine
reuse groups.
Systems using sites with six 60 RF coverage sectors provide about a 13.5 dB C/I for 90%
location reliability. This arrangement requires dividing the allocated frequencies into 18 reuse
groups.
The Motorola unique 2-site reuse pattern is a 4-site repeat pattern that reuses each frequency
group twice. Therefore, this plan is an effective 2-site repeat pattern. Each site is sectored
into six 60 RF coverage areas. The capacity of this pattern is 40% greater than the generic
3-site reuse pattern using cells sectored into three 120 RF coverage areas, and provides an
equivalent C/I performance.
In this arrangement, the allocated frequencies are divided into 12 reuse groups.
68P02901W01-S 2-29
Jul 2008
Cell pattern reuse comparisons Chapter 2: BSS General Description
Cell pattern reuse comparisons
Table 2-4 compares the features of the various reuse patterns.
Table 2-4 Sector reuse pattern features
No. of sectors No. of frequency

Reuse pattern C/I ratio Comments
per site reuse groups
9-site 1 omnidirectional 15 dB for 90% 9
location reliability
4-site 3 of 120 13.8 dB for 90% 9
3-site 6 of 60 13.5 dB for 90% 18
2-site 6 of 60 Equivalent to the 3 12 40% greater
site/3 sector pattern capacity
than 3 site/3
sector
pattern
2-30 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS redundancy
BSS redundancy

Introduction to BSS redundancy
Redundancy can optionally be added to prevent single faults from producing a capacity loss.
Redundancy means adding more modules than necessary to support a given capacity. These
additional modules are in standby mode until the system requires them to replace a failed
module. Fault management of the redundant modules minimizes the number of additional
modules the system requires to provide full redundancy. This design is achieved by using
N+1 redundancy wherever possible.
BSS fault management
When failures occur, the BSS software fault diagnostics can usually isolate the failure down to a
replaceable module. Fault Management (FM) classifies failures as type A or B.
Type A failures cause an alarm at the Operation and Maintenance Center (OMC) and/or
local terminal (TTY), and result in the faulty module being taken Out Of Service (OOS).
Type B failures cause an alarm at the OMC and/or TTY, but the module is not taken OOS.
Failed modules
Table 2-5 contrasts situations when a module fails.
Table 2-5 Failed module situations
If... Then... And...

There is no redundant Nothing happens. Call capacity is lost.
module.
There is a redundant module. The BSS automatically No call capacity is
switches over to the lost; service continues
redundant module. uninterrupted.
68P02901W01-S 2-31
Jul 2008
RF carrier redundancy Chapter 2: BSS General Description
RF carrier redundancy
All RF carrier equipment can provide both signaling and traffic channels. Redundancy can be
provided by equipping the cell/sector with more carrier equipment than traffic requirements
dictate:
If additional radio channel frequencies for the cell/sector are available, the redundant
carrier can provide additional capacity until a carrier or associated equipment fails.
If additional radio channel frequencies for the cell/sector are not available, the redundant
carrier is only switched into service in response to a failure.
Interface redundancy
Each site connects to the BSC or MSC through E1 serial links as digital carriers. Therefore,
each site requires at least one line interface module (A interface or Abis interface). Each line
interface module provides an interface for two E1 serial links.
To provide redundancy at the interface, an additional E1 serial link and an additional interface
module are added.
BTS redundancy
To provide BTS redundancy, one set of RF carrier modules and associated digital modules for
each cell or sector RF coverage area within one or more BTS cabinets at a site are required.
BSC redundancy
To provide BSC redundancy, duplicate digital modules within the same BTS/BSSC cabinet are
required.
N+1 redundancy is available for the processing and power supply modules.
RXCDR redundancy
To provide RXCDR redundancy, duplicate digital modules within the same shelf of the same
BSSC cabinet are required.
N+1 redundancy is available for the processing and power supply modules.
2-32 68P02901W01-S
Jul 2008
System Information: GSM Overview General packet radio service
General packet radio service

Introduction to GPRS and EGPRS
General Packet Radio Service and Enhanced GPRS (E)GPRS are a packet radio system that
allows mobile subscriber (MS) units to access data services (such as World Wide Web (WWW) or
email). Access to WWW or email is through a modified GSM air interface protocol. The modified
air interface protocol allows multiple MS units to share a single timeslot, and also allows
different mobiles to utilize the uplink and downlink timeslots. This enables a more cost-effective
use of network resources for data transfer.
A cell can have all GPRS and EGPRS carriers, or a combination of the two.
Two units form the basis of the Motorola (E)GPRS hardware:

The Packet Control Unit (PCU) located at the BSS.
The GSN complex module (SGSN, GGSN, GSN CommHub, and ISS).
Figure 2-7 shows an overview of the GPRS network.
Figure 2-7 The (E)GPRS network
A interface
BSC MSC HLR
Gr
BSS-PCU Gs
interface Gc
Mobis
BTS PCU SGSN GGSN PDN

Gb Gn Gi
Gd
Um
Gp
SMC-GMSC
SMC-IWMSC
MS GGSN
Other PLMN
ti-GSM-EGPRS network-00049-ai-sw
68P02901W01-S 2-33
Jul 2008
Packet control unit Chapter 2: BSS General Description
Packet control unit
GPRS introduced a new device at the BSS, known as the Packet Control Unit (PCU). The PCU is
an interface adaptor handler unit that permits the Motorola GSM facility access to the packet
network. As such, the PCU needs interfaces with the BSC on the GSM side, and the SGSN on
the packet network side. The PCU manages the packet radio interface and also enables the
interface from the BSS to the SGSN. The existing OMC-R manages the PCU.
See General packet radio service on page 2-33 section for full details.
GSN complex
Network elements
GPRS introduced the following new network elements, as shown in Figure 2-8:
The Serving GPRS Support Node (SGSN)
The Gateway GPRS Support Node (GGSN)
The Shelf Manager (at the OMC-G)
The GSN Complex
The SGSN keeps track of the individual MS locations, and performs security functions and
access control. The SGSN is connected to the BSS through a Frame Relay network.
The GGSN provides inter working with external packet-switched networks and is connected
with SGSNs through an IP-based (E)GPRS backbone network. This backbone network includes
the CommHub and ISS (IP Support Server) nodes.
The Shelf Manager at the OMC-G allows an operator to monitor the hardware in a shelf. The
Shelf Manager is displayed in the Navigator under its parent Complex and at the same level as
SGSN, GGSN, and so on.
NOTE
A shelf is an entity housing 16 cPCI slots plus cooling fans and power supply units.
Four of the slots are taken up by system cards. Twelve slots are available for SGSNs.
Each SGSN is a two-card unit in release 1.6.1.3, one for the Control Function (CF)
and the other for the Transmission Function (TF) function.
2-34 68P02901W01-S
Jul 2008
System Information: GSM Overview GSN complex
GSN complex
A GSN complex comprises the following:

Communications cabinet - housing the CommHub and the Internet Support Services (ISS)
(consisting of Domain Name Server (DNS), Network Time Protocol (NTP), Charging
Gateway (CG), and Network File System (NFS)).
GGSN cabinet - housing one or more GGSNs.
GSN cabinet housing a cPCI shelf.
NOTE
The GSN complex is not described in this manual. For further information on the
GSN complex, see the Motorola GSN Service Manual.
Operation and Maintenance (O and M) applications
Operation and Maintenance applications are Load Management, Configuration Management,

Fault Management, Performance Management, and Security Management. These applications
are provided for the (E)GPRS network through an OMC-G. The OMC-G comprises NT and UNIX.
68P02901W01-S 2-35
Jul 2008
GSM/(E)GPRS network architecture Chapter 2: BSS General Description
GSM/(E)GPRS network architecture
The Motorola-specific implementation of (E)GPRS, as integrated with the existing GSM

infrastructure equipment, is shown in Figure 2-8.
The new GPRS equipment consists of a PCU attached to the BSC, as part of the BSS. The SGSN,
GGSN, GSN CommHub, and ISS are included as part of the GSN complex equipment.
Each BSC has a dedicated PCU, and multiple BSSs can be attached to one GSN complex.
Several GSN complexes can be networked together to serve one PLMN. One OMC-G can
manage several GSN complexes.
Figure 2-8 (E)GPRS network architecture showing the PCU and GSN complex

(NON-TRANSP ARENT
MODE)
RXCDR OMC-G
(Including Shelf
Manager)
OMC-R
BSC ISS SGSN GGSN

PCU
BSSn GSN
BTSs COMMHUB
BSS2 GSNn
BSS1 GSN1
OPERA TOR SER VER

COMPLEX
- RADIUS SER VER
- DHCP SER VER
- DNS SER VER
ti-GSM-EGPRS PCU GSN-00050-ai-sw
2-36 68P02901W01-S
Jul 2008
System Information: GSM Overview Overview of VersaTRAU
Overview of VersaTRAU
The VersaTRAU feature provides dynamic TRAU capability to EGPRS Carriers to optimize
backhaul usage and reduce costs to the customer. Without VersaTRAU, a GSM TDMA timeslot
(containing voice or GPRS data) is framed and sent on a 64 kbps backhaul timeslot between the
BSC and a remotely located BTS site. With VersaTRAU, both voice and GPRS/EGPRS frames
are combined into one large frame, which reduces backhaul wasted due to extra padding.
Additionally, when congestion occurs on the backhaul, GPRS/EGPRS data and control blocks are
scheduled accordingly at the PCU to fit the available backhaul. The combined VersaTRAU frame
can still be sent on a reduced backhaul link.
The VersaTRAU feature introduces five new per-carrier statistics namely:

UL_EGPRS_BACKHAUL_USED
UL_EGPRS_BACKHAUL_DEMAND
DL_ EGPRS_BACKHAUL_USED
DL_ EGPRS_BACKHAUL_DEMAND
EGPRS_64K_CHANNEL_WIDTH
Using the above statistics, the OMC provides a new utility. The utility presents the user an
analysis on the VersaTrau performance over a period of time specified by the user. The
summarized report details the total statistics interval data considered for analysis:
Maximum and mean bytes lost over all the statistics intervals.
Mean VersaTrau bandwidth demand.
Number of intervals where the demand was less than or equal to 80% backhaul.
Number of intervals where the demand was greater than 80% and less than or equal
to 100% backhaul.
Number of intervals where the demand was greater than 100% backhaul.
This information enables users to configure DS0s effectively.
The VersaTRAU feature updates two existing alarms: CERM and GDS OOS.
This feature introduces a new RTF element namely rtf_ds0_count. This element specifies the
number of RTF backhaul timeslots allocated for a 64K carrier.
The VersaTRAU feature extends the existing debug functionality in the PCU:
TSN TRAU/PTRAU log - An operator can capture and display all uplink and downlink
VersaTRAU frames on a VersaTRAU channel.
PRM Carrier log - An operator can capture and display all the uplink and downlink PTRAU
frames on a VersaTRAU channel. In addition, it is possible to:
Issue disp_rtf_channel on a 64K RTF to display the current VersaTRAU configuration.
68P02901W01-S 2-37
Jul 2008
Overview of VersaTRAU Chapter 2: BSS General Description
Use PRM per-carrier internal stats to monitor the uplink omission information.
Use the five new per-carrier stats to monitor the backhaul usage and demand on
a 64K carrier.
Use the extra information carried in UL/DL Sync frames to debug any problems
related to the Time Alignment procedure for each VT subchannel. See PCU-CCU
IDS[4] for the UL/DL Sync frame on a 64K carrier.
The VersaTRAU feature eliminates the static mapping between a PDCH and backhaul resources.
All the PDCHs on a 64K carrier share a group of DS0s defined by a VersaTRAU channel.
Figure 2-9 shows PDTCHs to Backhaul Mapping on a 64K carrier.
Figure 2-9 PDTCHs to Backhaul Mapping on a 64K carrier
The new TRAU frame formats on 64K carriers. In VersaTRAU, the backhaul available for a 64K
PDCH in the uplink direction for a block period depends on all the following factors:
The number of DS0s is currently allocated for the VersaTRAU channel.
The PDCHs are currently configured on the carrier.
The user data (CS1-4, MCS1-9) or signaling (CS1 or PRACH) traffic is scheduled on each
PDCH on the carrier for a block period.
The backhaul available for a PDCH on a 64K carrier may not be enough to carry the user data
or signaling received on the PDCH for a block period. In this case, the CCU omits the uplink
RLC/MAC radio block and send the omission frame to the PCU.
2-38 68P02901W01-S
Jul 2008
System Information: GSM Overview Packet control unit
Packet control unit

Introduction to the PCU
The following text provides a general description of the Motorola Packet Control Unit (PCU),
which links between the GPRS Support Node (GSN) and the Motorola BSS.
The GSM recommendations define the functions of the GPRS, but allow flexibility in its design.
The following text describes some of the unique features of the Motorola PCU.
PCU information
The following sections contain the following information about the PCU:
PCU overview on page 2-40.
PCU features on page 2-42.
PCU description on page 2-51.
PCU architecture on page 2-54.
PCU interfaces on page 2-60.
PCU system and control functions on page 2-64.
68P02901W01-S 2-39
Jul 2008
PCU overview Chapter 2: BSS General Description
PCU overview

PCU summary
The PCU is a collection of high-performance processors that are responsible for:

Packet scheduling on the air interface.
Ensuring that efficient use is made of the air interface.
Taking small uplink packets from the E1 links connected to the BSS that are carrying
user data from the MS units. The PCU then forms larger uplink packets to be sent over
the E1 links to the SGSN.
Packet segmentation and packetization on the frame relay link to the SGSN network entity.
Taking downlink packets from the SGSN and segmenting these packets into small packets
to be sent to the MS units.
There are two types of PCU cabinet:

A static frame cabinet, which can accommodate two PCUs.
A swing frame cabinet, which can accommodate three PCUs.
NOTE
{27955A} The BSC supports one PCU cage when the software is upgraded to GSR9.
For GPRS, each PCU requires one E1 Interface panels.
For EGPRS, each PCU requires one or two E1 Interface panels depending on the configuration.
For high capacity PCUs requiring more than 600 Air TS and 24 E1s, it is necessary to add a
second T43 patch panel to the PCU.
All connectivity (GDS) between BSC and PCU is through Ethernet. The Ethernet ports can
support either 100 Mbps or 1000 Mbps operation.
2-40 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU environment
PCU environment
Figure 2-10 shows the PCU positioned within the GSM/(E)GPRS network.
Figure 2-10 PCU within the GSM/(E)GPRS network
HLR
PDN TE
MAP-G Gr
Gs Gn Gi
MSC SGSN GGSN
Gb Gn
PCU
BSC GGSN
Um
Abis OTHER
MS BTS PLMN
SIGNALLING
SIGNALLING AND DATA TRANSFER
ti-GSM-PCU GSM EGPRSnetwork-00052-ai-sw
68P02901W01-S 2-41
Jul 2008
PCU features Chapter 2: BSS General Description
PCU features

List of PCU features
The PCU features are described in the following sections:

Point-to-point (E)GPRS service
(E)GPRS radio channel allocation
Medium Access Control mode - dynamic allocation
Support of MS classes
GPRS coding schemes
EGPRS coding schemes
Dynamic adaptation of coding schemes
Two-phase packet access
Enhanced GPRS one phase access
Frequency hopping of PDCH
Power control for uplink/downlink
Gb interface
PCU load balancing and sharing (Gb and BTS)
MS flow control
Point-to-point (E)GPRS service
(E)GPRS provides a new set of bearer services supporting packet mode transmission. This
supporting low-speed and high-speed signaling, a data transmission technique with improved
efficiency compared with circuit based techniques.
(E)GPRS enables the subscriber to send and receive data in an end-to-end packet transfer mode,
without utilizing circuit switched network resources. General characteristics where (E)GPRS
offers superior performance compared with circuit technology include applications where:
The transmission of small volumes of data is frequent.
The transmission of large volumes of data is infrequent.
The time between successive transmissions greatly exceeds the average transfer delay.
2-42 68P02901W01-S
Jul 2008
System Information: GSM Overview (E)GPRS radio channel allocation
The network operator can size the network optimally for efficient support of a mix of (E)GPRS
and voice traffic. To support this mix, each timeslot on a GPRS carrier can be configured as
dedicated to circuit traffic, or (E)GPRS traffic. The timeslot can also switch between the two
types of traffic In the case of switchable timeslots, (E)GPRS traffic has precedence over circuit
switched traffic on the last remaining timeslot.
The (E)GPRS network supports cell reselection modes as shown in Table 2-6.
The reselection modes allow the network to provide the Mobile Station (MS) with information
regarding the quality and signal strength of the link. The MS then uses this information to
determine whether to perform a cell reselection based upon signal strength of neighbor cells.
(E)GPRS carriers can also be configured to support the GSM discontinuous transmission feature,
defined for circuit switched traffic in an effort to conserve MS battery life. In network operation
mode 2, the network uses the CCCH paging channel for both CS and GPRS paging.
Table 2-6 Cell reselection modes
Cell reselection Control

Functionality
mode element
NC0 MS control Normal GPRS MS control: Autonomous cell reselection.
Enhanced NC0 MS control Functionality in NC0 mode plus: BSS sends cell reselection
commands to GPRS MS to change cell reselection mode.
NC1 MS control Normal GPRS MS control: Autonomous cell reselection, MS

sends measurement reports to BSS.
Enhanced NC1 MS control Functionality in NC1 mode plus: BSS sends cell reselection
commands to GPRS MS to change cell reselection mode.
NC2 Network MS sends measurement reports to BSS, BSS sends cell
control reselection commands to GPRS MS, BSS instructs MS to
perform cell reselection.
(E)GPRS radio channel allocation
Dynamic allocation of radio resources allows an operator to configure the radio resources of a
cell as dedicated circuit switched, dedicated (E)GPRS, or switchable between circuits switched
and (E)GPRS. This enables efficient use of air interface resources, and allows an operator to
tailor the cellular network to the packet data traffic requirements of the operator.
This feature provides the flexibility for a cell supporting (E)GPRS to allocate a given radio
resource to handle circuit switched voice/data or packet data, as required. A radio resource
can be configured as dedicated to circuit switched traffic, packet data traffic, or switchable
between the two. In the latter case, the traffic demands of the network determine the type
of traffic handled by the air interface timeslot. This provides the operator with a degree of
flexibility when configuring a (E)GPRS capable network, and also facilitates maximum utilization
of resources. In a (E)GPRS capable cell approaching congestion, (E)GPRS traffic can be given
preference over the last switchable radio resource, by setting a database parameter.
Originally the Motorola GPRS product offered the capability to configure up to eight GPRS
timeslots on a single carrier in a cell. The network operator can now configure multiple (E)GPRS
carriers per cell for increased (E)GPRS traffic handling capability to meet the increase in packet
data traffic and the expanding base of (E)GPRS subscribers with increased data throughput.
68P02901W01-S 2-43
Jul 2008
Medium access control mode - dynamic allocation Chapter 2: BSS General Description
Medium access control mode - dynamic allocation
Medium Access Control (MAC) includes the functions related to the management of the common
transmission resources. These include the packet data physical channels and the radio link
connections on packet data physical channels.
MAC supports the assignment of radio resources to MSs for transmission of (E)GPRS protocol
data units (PDUs). In all cases, the network determines the assignment and transmits this
information for a given radio resource to all MSs sharing that resource.
The MAC also supports the provision of Temporary Block Flows (TBFs) allowing the
point-to-point transfer of signaling and user data between the network and the MS. A temporary
block flow is a physical connection used by the two entities to support the transfer of (E)GPRS
protocol data units (PDUs) on packet data channels (PDCH). A TBF is temporary and is
maintained only for the duration of the data transfer.
Dynamic allocation mode
MAC operates in dynamic allocation mode. In this mode, three Uplink State Flag (USF) bits
are transmitted in every downlink block. Through these USF bits, the network instructs one of
the MSs sharing a timeslot to transmit data on the uplink. MSs monitor the channel for their
instruction to transmit. The advantage offered by dynamic allocation mode is flexibility in
the assignment of the air interface resource.
Extended Dynamic Allocation Medium Access Mode (EDMAC)
{23292}
The optional EDMAC feature supports class 11 and 12 mobiles with 3 and 4 UL timeslots
capability. When 3 or 4 uplink timeslot allocation is assigned, EDMAC is required for the
request uplink TBF. When a class 11 or 12 mobile requests an uplink TBF, the network assigns
the EDMAC for the uplink TBF if the mobile supports EDMAC and the TBF allocation requires
EDMAC mode. The network assigns the lowest numbered timeslot in the allocation as PACCH
timeslot.
Support of MS classes
The (E)GPRS network currently provides some form of support for all 29 multi-slot class MSs,
supporting multiple timeslot allocations in the UL and DL directions. An MS that supports
multiple UL timeslot allocation is always allocated a maximum of two UL timeslots, for multi-slot
classes mapped to (E)GPRS classes 5, 6, 9, or 10. All other mapped classes only allow allocation
of one UL timeslot. Table 2-7 shows the mobile multi-slot class mapping for all the (E)GPRS
multi-slot classes.
2-44 68P02901W01-S
Jul 2008
System Information: GSM Overview Coding schemes
Table 2-7 MS multi-slot class mapping for all (E)GPRS multi-slot classes
Multi-slot class Supported as multi-slot class

01 01
02, 03 02
04 04
05 05
06, 07 06
08 08
09, 13 09
10 - 12, 14 - 29 10
GSM voice MSs are semi-duplex. The direction of speech information transfer alternates
rapidly, about 210 times per second, between the uplink and the downlink directions. This rapid
switching emulates a full duplex speech connection.
The basic GPRS MSs are semi-duplex as well. These MSs spend a significant proportion of time
switching directions, which significantly limits their total throughput. For example, the most
capable semi-duplex MS can receive four timeslots while transmitting one timeslot, or receive
three timeslots while transmitting two timeslots.
Coding schemes
Four separate coding schemes, CS-1 to CS-1 are supported for GPRS and nine coding schemes,
MCS1 to MCS9, are supported for EGPRS. These schemes are described in the text that follows.
GPRS coding schemes
Four separate coding schemes, CS-1 to CS-1 are supported for GPRS; these schemes provide
differing throughput rates, as shown in Table 2-8.
Table 2-8 GPRS coding scheme characteristics
Effective approximate
Coding scheme Throughput/TimeSlot (kbps)
convolutional coding rate
CS-1 9.05 1/2
CS-2 13.4 2/3
CS-3* 15.6 3/4
CS-4* 21.4 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 the support of these four coding schemes, a
higher throughput is enabled for MSs operating in those areas of the network with excellent
68P02901W01-S 2-45
Jul 2008
Coding schemes Chapter 2: BSS General Description
RF coverage, based upon reduced requirement for error correction. In those areas of the
network where RF coverage suffers, error correction can be boosted, thereby maintaining a
quality transmission, at a reduced throughput.
In the BSS architecture, the link which the (E)GPRS data traverses from the channel coders in
the BTS to the PCU is currently implemented using 16 kbps TRAU-like links. These links are
carried over sub-rate switched E1 timeslots which have some signaling included to ensure that
the link is synchronized between the channel coders and the PCU.
As additional protection and identification bits are included in the transmitted frame, there
is not enough bandwidth available on a 16 kbps link to carry CS-3 and CS-4. Thus a new
mechanism for associating two 16 kbps TRAU channels together, giving a 32 kbps TRAU, must
be implemented to provide the bandwidth necessary to implement CS-3 and CS-4.
EGPRS coding schemes
Nine coding schemes, MCS1 to MCS9, are supported for EGPRS; these schemes provide
differing throughput rates, as shown in Table 2-9.
Table 2-9 EGPRS Coding Schemes and Throughput
Channel RLC data

Code rate Header Family Data rate
Coding Modulation unit size
[05.03] Code rate [04.60] kbps
Scheme [04.60]
MCS1 0.53 0.53 GMSK 22 C 8.8
MCS2 0.66 0.53 28 B 11.2
MCS3 0.80 0.53 37 A 14.8 13.6
(pad)
MCS4 1.0 0.53 44 C 17.6
MCS5 0.37 1/3 8PSK 56 B 22.4
MCS6 0.49 1/3 74 A 29.6 27.2
(pad)
MCS7 0.76 0.36 2x56 B 44.8
MCS8 0.92 0.36 2x68 A 54.4
MCS9 1.0 0.36 2x74 A 59.2
The BSS supports all EGPRS coding schemes (MCS1 to MCS9) for EGPRS TBFs on a 64 kbps
terrestrial channel. EGPRS coding schemes are only used to transmit data blocks.
When an MS is performing bidirectional packet transfer, the PCU allows independent coding
scheme selections for each direction. If the mobile does not support 8PSK modulation, the BSS
limits the uplink coding scheme usage to EGPRS-GMSK MCS1 to MCS9 for an EGPRS mode TBF.
For uplink data transfers, the BSS selects one of the EGPRS coding schemes on a per mobile
basis according to measurement information.
For downlink data transfers, the BSS selects one of the EGPRS coding schemes on a per mobile
basis. The selection is according to measurement information, unless interleaving with GPRS
requires GMSK only (CS1 to CS4 or MCS1 to MCS4) blocks to be sent.
The BSS transmits all EGPRS RLC/MAC control blocks using CS1 and uses MCS1 for all LLC
dummy blocks during delayed downlink TBF release mode.
2-46 68P02901W01-S
Jul 2008
System Information: GSM Overview Dynamic adaptation of coding schemes
Dynamic adaptation of coding schemes
This feature enables the network to change the coding scheme between MS transmissions
based upon the radio characteristics of the link.
During a (E)GPRS transmission, the network monitors the characteristics of the radio link.
Based upon these measured characteristics, the network is able to change the coding scheme in
use to maximize throughput of the link. As an example, an MS with a fairly high-quality radio
connection can maximize throughput, with no error correction, using CS-4. If the quality of
the link deteriorates, the number of retransmissions required would begin to increase due to
the lack of forward error correction. In this case, there would eventually be a point at which
the throughput enabled by CS-3 would exceed that of CS-4. It is based upon the fact that the
added error correction would reduce the number of retransmissions. Similarly, if the link quality
deteriorates still further, CS-2 would become the better option.
Two-phase packet access
GPRS supports two-phase packet access. This feature allows an exchange of information to take
place between the MS and the network before the assignment of resources.
The purpose of the packet access procedure is to establish an uplink transmission to support
the transfer of packet data units from the MS to the network. The packet access procedure
can take place in either one or two phases. Two-phase packet access avoids contention. In
this procedure, the MS requests a packet resource on the random access burst. The network
provides an immediate assignment of a single block. The MS responds to the single block with
its radio access capability (classmark) and MS ID, and the number of octets of user data. Based
upon this information, the network assigns a resource for the uplink transmission.
One phase access
GPRS one phase uplink TBF access is an improvement over the two-phase uplink TBF access
procedure.
In a GPRS one phase uplink TBF access, the MS initiates an uplink TBF by sending a Random
Access Channel (RACH) to the BSS. The RACH is received at the BTS, which is then forwarded
to the PCU. The PCU responds to the RACH with an Immediate Assignment message containing
an uplink assignment. The MS moves to the assigned Packet Data (Traffic) Channel (PDTCH)
and begins its uplink data transfer. This procedure allows the MS to gain access to the network
much quicker when comparing against the two-phase establishment procedure.
Enhanced one phase access
The enhanced GPRS one phase uplink TBF access procedure speeds up the one phase packet
access procedure even further.
The enhanced GPRS one phase access procedure improves PCU assignment of resources for a
one phase uplink TBF. The procedure involves enabling the BTS to react more quickly to a one
phase RACH without forwarding the RACH to the PCU. This obviates RSL delay and increasing
RSL load. Depending on the RSL load, the RACH to Immediate Assignment delay reduces
by approximately 60 ms or more.
68P02901W01-S 2-47
Jul 2008
Frequency hopping of PDCH Chapter 2: BSS General Description
There are two versions of enhanced GPRS one phase access:

If the PCU has pre-allocated resources at the BTS and the pre-allocated timeslot is not in
the USF active state, the timeslot broadcasts the corresponding Uplink Stage Flag (USF),
once the MS has moved to the pre-allocated timeslot.
If the TS pre-allocated by the PCU is in the USF active state, the timeslot broadcasts a valid
USF continuously. Once the MS moves to the pre-allocated timeslot (after the MS receives
the Immediate Assignment message), the MS receives the assigned USF immediately. This
is the earliest possible opportunity for the MS to transmit in the uplink. The only delay
between the Immediate Assignment message and the uplink data transmission is the
MS reaction time.
Refer to Technical Description: BSS Implementation (68P02901W36) for a full description of the
differences between the two access methods.
Frequency hopping of PDCH
The (E)GPRS network support frequency hopping of the packet data channel (PDCH).
Frequency hopping is one of the Motorola key techniques to improve capacity and quality in
a highly loaded GSM network. These same benefits are realized when frequency hopping is
implemented on (E)GPRS carriers. For (E)GPRS, all packet data channels assigned to a single
MS are included in the same frequency hopping system, which specifies the frequencies over
which the timeslots hop and the hopping sequence.
The principle of frequency hopping is as simple as changing the frequency used in transmission
at regular intervals. It has been included in GSM specifications mainly in order to deal with
two specific problems which can affect transmission quality:
Multipath fading
Multipath fading immunity can be increased by exploiting its frequency selectivity. By

using different frequencies, the probability of being continuously affected by fading is
reduced, and so, the transmission link quality is improved. This improvement is much more
noticeable for slow moving MSs.
Interference
Interference coming from neighbor cells transmitting the same or adjacent frequencies can
be reduced by using frequency hopping. This is because calls are moving through different
frequencies that are not equally affected by interfering signals.
If the master cabinet is a Horizon II cabinet, the only restriction is that EGPRS and non-EGPRS
RTFs cannot base band hop (BBH) together. They can BBH independently, EGPRS carriers
must be in their own BBH system.
If the master cabinet is not a Horizon II cabinet, only single density DRIs can BBH.
Power control uplink/downlink
The power control feature enables power adjustment over the radio link based upon the
characteristics of the link.
Power control is supported over the radio interface on both the uplink and downlink. The
network directs power adjustments based upon the measured characteristics of the radio link.
2-48 68P02901W01-S
Jul 2008
System Information: GSM Overview Gb interface
Gb interface
The PCU interface/Gb interface provides connection between the BSS and the SGSN.
The Gb interface connects the BSS/PCU to the SGSN, allowing the exchange of signaling
information and user data. The Gb interface allows many users to share the same physical
resource. To facilitate cost-effective transmission, the Motorola (E)GPRS offering also supports
infrastructure sharing, which allows the operator to carry A interface (CS) and Gb interface
(packet) traffic on a single E1 using the nailed connections capability. These two features
enable a cost-effective transmission solution in a (E)GPRS capable network. As (E)GPRS
traffic increases, it is appropriate to dedicate one or more E1 link lines to (E)GPRS traffic. To
accommodate this scenario, the network also supports a direct connection between the PCU
and the SGSN.
The Gb interface link layer is based on frame relay. Frame relay virtual circuits are established
between the SGSN and BSS, where PDUs from many users are multiplexed on these virtual
circuits. The virtual circuits are multi-hop, and traverse a network of frame relay switching
nodes. Frame relay is used for both signaling and data transmission.
PCU load balancing and sharing (Gb and BTS)
This feature provides high reliability through efficient resource management. It also manages
the movement of resources from one part of a BSS to another to meet varying peak capacity
requirements in a network designed primarily for coverage.
The primary objective of this feature is to support the use of multiple timeslots per cell
economically, with no delay penalty, in a BSS configured for coverage rather than capacity. A
coverage based (E)GPRS network provides coverage over a large number of cells, and assumes
a low average throughput per cell. This feature allows a network to move or enable resources
effectively as needed throughout a BSS, to handle traffic peaks. If there is a PCU failure (with
multiple PCUs), cells move from one PCU to another.
Another objective of this feature is to provide high reliability. During periods when the
designated resource is not required due to a failure, the spare resource can be used to manage
peak loads. This is accomplished with load sharing of E1 link lines and other key components
within the BSS. A BSS/PCU can be configured to support a maximum capacity of 270*3 (810)
active timeslots.
If the link line or equipment fails, the BSS provides load sharing of the following resources:
E1 link lines on the BTS-BSC link.
E1 links on the BSS-PCU link.
PRP (RLC/MAC) boards within the PCU.
E1 link lines on the Gb (PCU-SGSN) interface.
MS flow control
MS flow control is implemented to regulate the flow of data from the SGSN to the MS by
sending a message containing the MSs logical identifier (TLLI), the current maximum buffer
depth (MS_Bmax) and the current buffer leak rate (MS_R). The flow of data is then controlled
on a per MS basis.
68P02901W01-S 2-49
Jul 2008
MS flow control Chapter 2: BSS General Description
The BSS attempts a preset maximum number of times to send the message, in case the SGSN
does not acknowledge it within the maximum time allowed. Successive messages are sent a
pre-defined delay (C) apart, unless the messages are unacknowledged.
The MS flow control functionality complies with GSM 08.18.
2-50 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU description
PCU description

PCU purpose
The new BSS functionality for (E)GPRS mainly resides at the Packet Control Unit (PCU). The
functions of the PCU include the following:
Handling of frame relay.
Network Services (NS) signaling.
BSSGP signaling.
Routing of signaling messages.
Radio Link Control (RLC) and Medium Access Control (MAC) preload.
Transferring user data.
User data is routed to the PCU through the Channel Codec Unit (CCU) uplink from the BTS to
the BSC. Then over E1 to the PCU. At the PCU, the RLC blocks are reformulated in Logical Link
Control (LLC) frames and forwarded to the SGSN.
BSSGP signaling and NS signaling occur between the PCU and the SGSN using frame relay
protocol. There is also signaling between existing functional processes at the BSC such as the
signaling between the Base Station control Processor (BSP) at the BSC and the PCU through the
E1 interface, as well as between the PCU and channel coders.
The purpose of the PCU is to perform a variety of functions and is responsible for the following
(E)GPRS MAC and RLC layer functions:
LLC layer PDU segmentation into RLC blocks for downlink transmission.
LLC layer PDU reassembly from RLC blocks for uplink transmissions.
PDCH scheduling functions for the uplink and downlink data transfers.
PDCH uplink ARQ functions, including RLC block ack/nack.
PDCH downlink ARQ function, including buffering and retransmission of RLC blocks.
Channel access control functions, such as access requests and grants.
Radio channel management functions, such as power control, congestion control,

broadcast control information.
The functions inside the CCU are:

The channel coding functions, including Forward Error Correction (FEC) and interleaving.
Radio channel measurement functions, including received quality level, received signal
level, and information related to timing advance measurements.
68P02901W01-S 2-51
Jul 2008
PCU management Chapter 2: BSS General Description
The BSS is responsible for allocation and de-allocation of radio resources. A PCU frame can
be transferred between the PCU and the CCU every 20 ms.
PCU management
The PCU is managed, including software download and operations, by the OMC-R as an
extension to the BSS. The OMC information destined for the PCU is passed through the BSC.
The Common Management Information Protocol (CMIP) interface is modified on the BSC to
include the management of the PCU as a new device.
A summary of this process is shown in Figure 2-11.
Figure 2-11 PCU managed from the OMC-R
OML GSL
OMC-R BSC PCU
X.25 64 kbps
E1
ti-GSM-PCU managed from OMCR-00053-ai-sw
2-52 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU devices and equipage
PCU devices and equipage
Figure 2-12 shows the PCU devices and their equipage.
Figure 2-12 Device and equipment hierarchy for the PCU device
NOTE:
.
..
68P02901W01-S 2-53
Jul 2008
PCU architecture Chapter 2: BSS General Description
PCU architecture

Introduction to PCU architecture
The PCU hardware is off-the-shelf equipment that is based upon the compact PCI (cPCI)
standards. The cPCI is a set of standards that define a common chassis, power supplies, and
processor boards.
There are four cPCI board types:

The Master Processor (MPROC)
The Bridge (PPB)
The Data Processor (DPROC) consisting of:

The Packet Interface Control Processor (PICP)
The Packet Resource Processor (PRP)
If configured as a PICP, the DPROC provides one or two E1 interfaces. If configured as a

PRP, the DPROC provides up to two E1 interfaces. These are provided by PCI Mezzanine
Cards (PMC modules) which are managed as MSI devices.
{28351}A new board, U-DPROC2, replaces the DPROC board. The U-DPROC2 board is
configured with PXP function. PXP combines the functionality of PICP and PRP.
The PCU also supports load sharing (fault tolerance).
MPROC
The MPROC is the system slot processor that is responsible for bus arbitration and CPCI clock
generation. It contains interface and BSSGP protocol functions, and is called the PCU System
Processor (PSP). Two PSPs are automatically equipped for each PCU; one acts as the primary
and the second acts as the redundant, and so, MPROCs are redundant.
MPROC board (PSP)
The MPROC is the main control processor for the system, and works in conjunction with
the PPB. It acts as PCI system host, and in conjunction with the PPB supports hot removal
control for all board slots. It performs resource allocation, fault management, and gateway
management functions (such as control of allocation of cells to PRP boards). These functions
comprise the PSP, which resides on the MPROC.
The MPROC requires a high-performance processor system such as the 266 MHz MPC750 with
an 83 MHz bus for the memory subsystem. A minimum of 128 M bytes of DRAM is supported,
upgradeable to 256 MBs.
2-54 68P02901W01-S
Jul 2008
System Information: GSM Overview Bridge (PPB)
Bridge (PPB)
The bridge, also referred to as the PCI to PCI Bridge (PPB), allows the MPROC to be linked to a
separate bus. The PPB and MPROC are paired boards.
The PPB allows the redundant operation of the system host MPROC board, and gives the host
MPROC access to all boards in the system. It supports control of hot swap for all boards
and a communication link between bridge boards. This allows migration to a fully hot swap,
redundant, high-availability system, including hot standby/load sharing between MPROC boards
in the future, if necessary.
DPROC
The DPROC boards are non-system slot boards that have two PMC sockets and can host two
different functions. The DPROC can be configured as either a PICP or a PRP.
If configured as the PICP, the DPROC contains up to two PMC modules to provide the E1
interfaces. The E1 interface can support the LAPD GDS interface (GSL) and the Gb interface;
TRAU GDS devices are no longer supported.
If configured as a PRP, the DPROC performs air interface scheduling and the PMC sockets can
be used to support TRAU GDS devices. A single processor can support a pool of 120 radio
timeslots, of which 30 radio timeslots can be active at any one time.
DPROC (PICP)
The DPROC (PICP) is used for all network interfacing functions to the outside world, such
as the SGSN and BSC. The PICP has up to two interface modules installed and data to/from
these interfaces passes through the onboard processor. This processor has different functions
dependent on the interface type. It includes features such as packet routing on an incoming
SGSN link, and packet scheduling to an outgoing SGSN link.
DPROC (PRP)
The DPROC (PRP) is the processor where all of the radio-related processing takes place. Each of
the (E)GPRS channels is routed to a PRP. The PRP performs all of the RLC/MAC processing, air
interface scheduling, and frame synchronization on BTS facing channels.
The performance required from this board is such that it supports a minimum of 30 active air
interface timeslots, with the ability to monitor another 90 timeslots. A future tripling of this
capacity is envisaged. The PRP maintains synchronization to the air interface by the exchange
of the PCU-CCU frames (which is transmitted even on inactive timeslots).
U-DPROC2
{28351} A new hardware named Universal DPROC2 (U-DPROC2) replaces the legacy DPROC to
increase GPRS capacity in GSR9. The U-DPROC2 board is configured with PXP function. PXP
combines the functionality of PICP and PRP. The U-DPROC2 increases the GPRS capacity on the
current PCU and BSC hardware platform. The U-DPROC2 board can support Ethernet link and
hence, the process capability of TS for the board is improved highly.
68P02901W01-S 2-55
Jul 2008
U-DPROC2 Chapter 2: BSS General Description
A U-DPROC2 serving as PXP supports a 1000BASE-T or CAT 5e link from the PCU to the BSC
completing connection to the new PSI board.
With the introduction of new U-DPROC2, there are three PCU configurations. DD1 (Deployment
Diagram 1) is a legacy configuration utilizing DPROCs and/or U-DPROC2s configured as
PICPs and PRPs. In DD2, the PCU is configured with all U-DPROC2 boards configured as
PXP. All boards are connected with PSI board in BSC through Ethernet link. DD3 is a mixed
configuration mode in which the PCU has PRP/PICP and PXP in its cage.
Figure 2-13 Deployment Diagram 1
2-56 68P02901W01-S
Jul 2008
System Information: GSM Overview U-DPROC2
Figure 2-14 Deployment diagram 2
Figure 2-15 Deployment diagram 3
68P02901W01-S 2-57
Jul 2008
E1 PMC module Chapter 2: BSS General Description
U-DPROC2 PXP supports IPv4 and UDP protocols for Ethernet connection to PSI board at the
BSC. Therefore, both TRAU data and GSL signaling are transported over IP/UDP protocol
between U-DPROC2 and PSI when U-DPROC2 serves as a PXP.
E1 PMC module
A single PMC module residing on the U-DPROC2 provides the E1 interfaces to both the BSS
and the SGSN. The PMC board has a 8560 800 MHz PowerQUICC III processor and 512 MB
DDR266 ECC RAM.
This onboard processor is used for frame relay termination on the Gb link and contains a
small process to route the Gb interface signaling (control) information to the Gb manager on
the MPROC. E1 links are also used to interface the PCU to the BSC for transfer of signaling
information through LAPD protocol, as well as serial user data in the remaining timeslots.
The clock on the PMC module is free run and not synchronized to an external signal from E1
interface. The memory on the PMC module is used for the code object storage of the frame
relay protocol as well as the buffers which are necessary for both the transmit and receive
sides of the frame relay link.
The E1 interface can support the Gb interface or the TRAU (E)GPRS Data Stream (GDS)
interface, and LAPD GDS including the (E)GPRS signaling link. The GSL is a 64 kbps TCL and is
used to manage and control the PCU/BSC system. Multiple GSLs can be used to manage and
control the PCU/BSC system. Figure 2-18 shows a system where E1 PMCs are used to connect
the TDM data to the BSC. The MSIs used for these links can be equipped in any chassis of a
multi-chassis BSC system.
A PMC module can support only one of the following:

(LAPD) GDS
(TRAU) GDS
Gb interface
Chassis
The chassis houses a maximum of 16 cPCI boards, with the ability to support redundant
host processors. The power supply system is part of this OEM solution. The host processor,
redundant host processor, and their associated bridge boards occupy four of the slots, leaving
12 generic slots for the remaining boards. Hot removal of all boards is supported.
The PCU is an additional chassis that is collocated with any BSC that supports (E)GPRS
functionality and interfaces to the BSC, utilizing E1 PMC modules on a DPROC (PICP) board.
This requires corresponding Multiple Serial Interface boards (MSIs) to be present in the BSC.
The chassis is a 19-inch rack-mounting module supporting sixteen 6U PCI slots, four of these
slots are taken by the two MPROC/bridge pairs for redundant systems. Any combination of PICP,
and PRP boards with their associated PMC modules take up the remaining 12 generic slots.
It supports front access for all replaceable modules, redundant/load sharing PSU system, and
status LEDs. The interconnect cabling is routable from the rear, front, or bottom of the chassis.
2-58 68P02901W01-S
Jul 2008
System Information: GSM Overview Fault tolerance
Fault tolerance
The PCU supports load sharing across the PRP, PICP, and E1 PMC. The hardware can be N +
M redundant (and would generally be equipped as N + 1 when load sharing is active), but
software loads share across all installed boards, with any failures causing a loss in total capacity
capability. The operator determines whether the hardware is provisioned for greater capacity
than required, such that failures do not affect the system capabilities.
68P02901W01-S 2-59
Jul 2008
PCU interfaces Chapter 2: BSS General Description
PCU interfaces

Introduction to (E)GPRS BSS interfaces
The Motorola (E)GPRS BSS includes the:

Base Station Controller (BSC)
Base Transceiver Station (BTS)
Operations and Management Center-Radio (OMC-R)
Packet Control Unit (PCU)
Figure 2-16 shows these components and their interfaces.
Figure 2-16 BSS functional blocks
RXCDR SGSN
A Gb
X.25
OMC-R BSC PCU
Abis
BTS
Um
KEY:
MS optional
ti-GSM-BSS functional blocks-00055-ai-sw
The BSC supports the following interfaces as illustrated in Figure 2-16:

BSC-BTS (Abis)
ABSCONDER (X.25)
BSC-RXCDR (A)
BSC-PCU
PCU-SGSN (Gb)
2-60 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU interfaces
This section defines the interfaces the PCU has with other elements of the (E)GPRS.
PCU interfaces
PCU-BSC interface
The PCU-BSC interface carries user data and radio resource management information, called
Radio Link Control/Medium Access Control (RLC/MAC) packets, between the PCU and BTS. The
(E)GPRS Signaling Links (GSL) carry signaling information on 64 kbps E1 timeslots between the
PCU and BSC.
GDS connections carrying traffic and signaling are supported by E1 and Ethernet. ETH is an
Ethernet port on the PSI card at the BSC or on the PXP DPROC card at the PCU used for
GDS functionality.
An RSL carries the signaling information on 16 kbps or 64 kbps E1 timeslots between the
BSC and BTS.
Another 16 kbps E1 TS or channel carries the TRAU-like framed data between the BSC and BTS.
A BCCH or CCCH carries the signaling information between the BTS and MS.
Between the BTS and MS, the packet data is carried over CS1, CS2, CS3, or CS4 encoded
PDCHs (see Figure 2-17).
Figure 2-17 Data and signaling paths between the PCU and MS
68P02901W01-S 2-61
Jul 2008
PCU interfaces Chapter 2: BSS General Description
Figure 2-18 provides more detail of the E1 physical links.
Figure 2-18 PCU to BSC connection utilizing four E1 LINKS
E1 LINKS
BSC
E1PMC
DPROC
DPROC
(PICP)
(PICP)
MSI
MSI
E1PMC
The number of MSI links
needed is dependent on the
PCU capacity . All MSIs can
reside in a single BSC
chassis even in expanded PCU
systems.
E1 LINKS
ti-GSM-PCU BSC E1 connection-00057-ai-sw
2-62 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU interfaces
Gb interface
The Gb traffic, user data, and signaling, can take different paths between the PCU and SGSN
depending upon the needs of the voice and data networks. In all cases, the Gb traffic is always
carried over 64 kbps E1 channels. See Figure 2-19 for a summary of the three connection
methods. Option C, routing a connection through the transcoder, is a convenient way to bring
(E)GPRS traffic from multiple PCUs to a single SGSN.
Figure 2-19 Data and signaling paths between the PCU and SGSN
ALL INTERFACES ARE Gb n x 64 kbps E1 CHANNELS LAPF
PCU PCU PCU
BSC BSC
RXCDR
SGSN SGSN SGSN
OPTION A: DIRECT OPTION B: BSC OPTION C: BSC AND

PAS S-THROUGH RXCDR PAS S-THROUGH
ti-GSM-PCU SGSN data and sig paths-00058-ai-sw
68P02901W01-S 2-63
Jul 2008
PCU system and control functions Chapter 2: BSS General Description
PCU system and control functions

System and control functions
The Packet Control Unit (PCU) performs:

Radio functions.
(E)GPRS network functions.
The PCU has interfaces to:

OMC-R
BSC
SGSN
Radio functions
The PCU is responsible for the following (E)GPRS MAC and RLC layer functions, as defined
in GSM 03.64:
LLC layer PDU segmentation into RLC blocks for downlink transmission.
LLC layer PDU reassembly from RLC blocks for uplink transmissions.
PDCH scheduling functions for the uplink and downlink data transfers.
PDCH uplink ARQ functions, including RLC block ack/nack.
PDCH downlink ARQ function, including buffering and retransmissions of RLC blocks.
Channel access control functions, such as access requests and grants.
Radio channel management functions, such as power control, congestion control,

broadcast control information.
Interacting with existing BSS software for allocation/de-allocation of radio resources for
(E)GPRS.
Multiplexes data and signaling onto BSC facing E1 links.
SGSN functions
The PCU and the SGSN use frame relay and the Base Station System (E)GPRS Protocol (BSSGP)
protocols to exchange user data and signaling information. The frame relay network can be
point-to-point or an actual network. Signaling data, used for flow control and congestion
management, is exchanged between the PCU and SGSN.
2-64 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU processes
PCU processes
There are three PCU functional areas:

PRP processes
Gb processes
GWM processes
PRP processes
The PRP processes are:

The Packet Resource Manager (PRM):
Performs all RLC/MAC functions.
Releases UL/DL power control and timing advance.
The DownLink Segmentator (DLS) segments LLC frames into RLC data blocks to be
transmitted over the air interface.
The UpLink Concatenator (ULC) concatenates RLC data blocks into LLC frames.
The SYstem information Manager (SYM) builds and sends (E)GPRS system information
messages over the BCCH.
CCCH Paging Manager (CPGM) processes the paging messages coming from the SGSN
to the BSC or BTS.
Gb processes
The Gb processes are:

The Gb router (GR) routes incoming BSSGP PDUs from the SGSN to the relevant SW
process in the PCU.
The Flow control Buffer Manager (FBM) controls buffer capacity for each cell and each
mobile and so, that the incoming data from the SGSN matches the air throughput.
The Gb Manager (GBM) manages the state of all cell and signaling links between the
PCU and the SGSN.
The Gb Transmit Manager GTM) collects all UL frames from various ULCs and sends
them on the appropriate NS-VC.
The Network Service Tester (NST) periodically tests all alive Network Service-Virtual
Circuit (NS-VC) on a PICP board.
The Frame Relay (FR) performs the frame relay protocol functions.
68P02901W01-S 2-65
Jul 2008
PCU processes Chapter 2: BSS General Description
GWM processes
The GWM processes are:

The PCU Fault Transaction Process (pFTP) is the central collection point for all faults
generated in the PCU. The process translates faults and fault clears into out of service
and in-service requests for faulty devices.
The PCU Fault Collection Process (pFCP) resides on every DPROC and MPROC and collects
all software faults (SWFMs) and sends them to pFTP.
The PCU Central Authority (pCA) initializes devices, brings them in or out of service, tests
the devices, and performs fault recovery of the PCU (through out of service/in-service
request from pFTP).
The PCU System Audit Process (pSAP) periodically audits devices to maintain the reliability
of the system.
The PCU Configuration Management (pCM) distributes all database changes performed at
the BSC to the PCU boards.
The Cell Balancer (CB) handles the load balancing of cells across all PRPs.
2-66 68P02901W01-S
Jul 2008
Chapter
OMC-R Overview

This chapter provides an overview of the OMC-R hardware configurations for the SunFire 4900,
SunFire 4800, Netra 20 and Netra 440 based high-end and low-end systems. The OMC-R
hardware and software components for each system are identified.

OMC-R network management functions on page 3-3.
The OMC-R system on page 3-7.
The OMC-R user interfaces on page 3-12.
The command line interface on page 3-15.
The OMC-R in a GSM network on page 3-16.
BSS and RXCDR configuration (SITES) on page 3-18.
NE device containment on page 3-19.
Site configuration on page 3-20.
DRI/RTF groups - transceiving on page 3-22.
CELL configuration on page 3-23.
Links in a GSM network: overview on page 3-25.
Physical links - PATH on page 3-26.
Logical links on page 3-28.
OMC-R connection to the network on page 3-31.
Operation and Maintenance of a BSS or RXCDR on page 3-33.
Operation and Maintenance information flow between OMC-R and NEs on page 3-34.
OMC-R system configuration on page 3-36.
Communications handling on page 3-37.
Packet switch or multiplexer on page 3-38.
Operation and Maintenance network traffic capacity on page 3-39.
OMC-R system processor on page 3-40.
OMC-R GSM application software: overview on page 3-43.
68P02901W01-S 3-1
Jul 2008
PCU processes Chapter 3: OMC-R Overview
UNIX: Solaris 10 operating system on page 3-45.
The OMC-R database on page 3-47.
The OMC-R GUI configuration on page 3-49.
GUI processor on page 3-50.
The network status summary feature on page 3-51.
The CM MIB on page 3-53.
GUI client on page 3-54.
Network status summary on page 3-56.
GUI clients and servers: Overview on page 3-58.
Network maps on page 3-59.
The map display on page 3-61.
How administrative and operational state changes work on page 3-64.
How alarms work on page 3-66.
Map configuration on page 3-69.
Graphic objects on page 3-71.
Configuration objects on page 3-73.
Periodic Supervision of Accessibility (PSA) on page 3-82.
Disk usage exceeded on page 3-83.
DataGen on page 3-84.
Feature Capacity Licensing and Audit on page 3-87.
3-2 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R network management functions
OMC-R network management functions

Fault management
Fault management provides the facility to change the status of any device using fault handling
procedures. From the OMC-R, the GSM network operator can react to changes in the network.
The operator reconfigures the site by taking devices in or out of service as required, thus
maintaining continuity of service to mobile phone users. Fault management tasks can be
performed from the map, the alarm window, the Navigation Tree and through the contained
devices.
Event/alarm management
A primary function of an OMC-R is to maintain the quality of service to customers or users of the
GSM network by monitoring the state of Motorola equipment in the network. Event or alarm
messages containing information on the state of the network, devices, and links in the system
are sent through the X.25 network to the OMC-R. These messages notify the operators of any
potential problems occurring in the network. There is the optional alarm notification through
Paging feature, which automatically notifies key personnel of certain alarm or state changes.
Operators can filter and select the way in which alarms are displayed and handled. For example,
alarms, which have been handled, but not yet cleared, can be deferred. With the optional
Network Health Analyst (NHA), operators can move from being purely reactive to a more
proactive role by observing a combination of events, statistical information, and configuration
data that notifies them of network problems before any faults are raised.
Performance management
Performance management provides collection and reporting of network performance statistics.

The OMC-R collects, processes, and stores performance statistics on the different NEs in the
network. The OMC-R also provides reporting facilities for the presentation and printing of the
processed statistics. These statistics can then be used to analyze network performance and aid
long-term planning.
68P02901W01-S 3-3
Jul 2008
Configuration management Chapter 3: OMC-R Overview
Configuration management
The OMC-R provides the configuration management facilities for a scalable system that can
cater for an expanding GSM network. The system processor can be configured for a variety
of expandable traffic channel capacities on the same basic platform. The OMC-R system
allows customers to expand their network Operation and Maintenance support according to
their business growth. The system provides orderly migration for existing users and rapid
deployment for new users. Network Expansion and Cell Parameter Import/Export under the
control of the OMC-R enables rapid and widescale network expansion. The OMC-R also includes
the Call Trace function.
Configuration management also provides centralized software load management, database load
management, and the management of operating parameters. The OMC-R provides facilities
to initiate uploads and downloads of NE operating software, or to back up or download
configuration databases for the different NEs. The OMC-R also provides the facilities to
reconfigure the operating parameters of NEs using the remote login facility and facilities to
optimize through the GUI.
Network configuration from the OMC-R also includes the optional Packet Control Unit (PCU)
interface to the (E)GPRS system. The interface incorporates the packet switching logical
connections and devices.
Load management
Load management forms part of the Configuration Management. It provides the operator with a
central location to load all the NEs remotely with the latest compatible version of operating
software. New software loads are installed at the OMC-R and later downloaded to the NEs
under the control of the OMC-R.
3-4 68P02901W01-S
Jul 2008
System Information: GSM Overview The OMC-R in GSM network management architecture
The OMC-R in GSM network management architecture

Network hierarchy
The position of the OMC-R within the GSM network management hierarchy, is shown in
Figure 3-1.
Figure 3-1 GSM network management architecture
BUSINESS FIVE-LAYER TMN MODEL (DEFINED IN ITU M.3010)

MANAGEMENT
PHYSICAL IMPLEMENTATION
SER VICES OF THE LOWER THREE LAYERS
MANAGEMENT
NETWORK
NMC
MANAGEMENT
NETWORK
ELEMENT OMC-R OMC-R
MANAGEMENT
NETWORK ELEMENT
LEVEL NE NE NE NE NE NE
ti-GSM-GSM network mgmnt architecture-00059-ai-sw
Network levels
Operation and Maintenance management of the BSS and RXCDR can be performed at several
network levels:
Local level
Local level monitoring, where reconfiguration, and software loading can be performed by
connecting a personal computer to the BSC or RXCDR (Remote Transcoder).
68P02901W01-S 3-5
Jul 2008
Network levels Chapter 3: OMC-R Overview
Regional level
The OMC-R provides facilities for performing functions on NEs at a regional level. Built in
alarm and event management, configuration management, and fault handling facilities enable
operators at remote OMC-R sites to manage Operation and Maintenance in a consistent and
standardized manner. The OMC-R provides monitoring and control for a number of BSSs in
a specific geographical area. The prime function of the OMC-R is maintaining the quality
of service to customers or users by monitoring the performance of the radio equipment.
Procedures are provided which can dynamically reconfigure the radio resources, and rectify
faults from a single remote location. Additionally, the OMC-R provides databases for Operation
and Maintenance data and system performance statistics.
Top level
The Network Management Center (NMC) implements the top level of the network management.
The NMC could perform Operation and Maintenance functions at a network-wide level with
OMC-Rs as its subordinates.
3-6 68P02901W01-S
Jul 2008
System Information: GSM Overview The OMC-R system
The OMC-R system

OMC-R system configuration
Introduction to OMC-R system configuration
The OMC-R platform can be expanded in a cost-effective manner as the cellular network grows.
Based on the SUN computer product line, the OMC-R supports networks of different sizes:
Low-end
High-end
The hardware configuration of the system processor varies depending on whether a Low-end
or High-end OMC-R is chosen. For example, the number of CPU processors, memory, disk
capacity determines the configuration.
The RTF (Receive Transmit Function) and the number of Network elements (NEs) determine the
choice of Low-end or High-end OMC-R platform, the OMC-R is required to manage.
The OMC-R typically comprises of the following:

A system processor (also known as the Single Platform Processor, SunFire 4900, SunFire
4800, Netra 20 or Netra 440).
A Graphical User Interface (GUI) Server (for example, Sunblade 150).
Several GUI client processors which provide operator workstations (for example, Sunblade
150).
A laser printer, suitable for LAN connection.
Each processor is a complete UNIX system. An Ethernet Local Area Network (LAN) enables
interaction between all processors.
The OMC-R interfaces with the cellular network using of X.25 Packet Switched protocol.
68P02901W01-S 3-7
Jul 2008
OMC-R system configuration Chapter 3: OMC-R Overview
Typical hardware architecture of OMC-R system
Typical hardware architecture of an OMC-R SunFire/Netra system is illustrated in Figure 3-2.
Figure 3-2 Typical hardware architecture of OMC-R SunFire/Netra system
OMC-R specifications
The SunFire 4900, SunFire 4800, Netra 20 or Netra 440 is a UNIX system that acts as the
OMC-R system processor, running the OMC-R application software. The OMC-R handles all
Operation and Maintenance communication with the Network Elements (NEs). A Packet
Switch or Multiplexer and the system processor HSI/S or HSI/P hardware enable the OMC-R to
interface to the GSM Network. The OMC-R system processor processes all incoming events,
alarms, uploads, downloads, performance statistics, and the setting up of remote login sessions
to different NEs.
The OMC-R system processor contains two databases constructed on a Relational Database
Management System model (RDBMS), Informix. One database (PM) is configured for storing
performance statistics and subscription lists; the other (CM) is configured for network and map
configuration data. The PM and CM enable operators to monitor incoming events and alarms
using map displays.
The OMC-R system processor uses the Solaris 10 Operating System (OS) as the UNIX platform.
3-8 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R system configuration
In addition to the OMC-R system processor, Graphical User Interface (GUI) servers and clients
based on SUN ULTRASparc processors, can be used as operator workstations managing and
monitoring NEs.
The OMC-R can be configured to utilize an optional laser printer.
A comparison between Low-end and High-end OMC-R specifications is shown in Table 3-1.
Table 3-1 OMC-R specifications (maximum values)
Feature OMC-R Low-end OMC-R High-end

Total GUI sessions supported 12 12
Dial-up sessions per GUI 1 1
Processor
Total remote dial-up sessions 2 2
Remote login sessions 6 30
Simultaneous downloads 6 12
Simultaneous uploads 4 32
Sustained event rate 8 alarms + 2 state changes 12 alarms + 3 state changes
Maximum event burst 20 events/s over 20 mins 63 events/s over 20 mins
GUI sessions
A total of 12 GUI sessions are supported per GUI server.
Operator workstations
The OMC-R system comprises of a Single Platform system processor and a number of operator
workstations. Each operators workstation is a complete UNIX system and runs the OMC-R
Graphical User Interface (GUI).
The operator workstations consist of a possible combination of the following:

GUI server:
Netra 210 or Sunblade 150.
GUI client:
Sunblade 150.
Refer to the Software Release Notes: OMC-R System (68P02901W74) for configuration details.
68P02901W01-S 3-9
Jul 2008
Optional processors
Optional processors can be added to the basic OMC-R configuration:

OSI (Open Systems Interconnect) Processor
Based on the Netra 440 hardware platform.
Datagen
Based on the Netra 440 or Netra 20 hardware platform.
Network Health Analyst (NHA)
Based on the Netra 440 or Sunfire V440 hardware platform.
Web Access Server (WAS)
Software requirements
The software requirements for the OMC-R are contained on two GSR9 DVDs:
OMCR.1900xy.JS.ALL.ALL.DVD.0.00 and OMCR.1900xy.SW.ALL.ALL.DVD.0.00.
The JumpStart DVD contents are given in Table 3-2.
Table 3-2 Software requirements (Single Platform Processor)
No. of License key

Title Revision version Media
volumes required
OMCR.1900xy.JS.ALL. 1900.xy DVD 1
ALL.DVD.0.00
and
OMCR.1900xy.SW.ALL.
ALL.DVD.0.00.
Sun Solaris 10 6/06
Solaris Volume Management 1.0
Continued
3-10 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R system configuration
Table 3-2 Software requirements (Single Platform Processor) (Continued)

No. of License key
Title Revision version Media
volumes required
Sun SunLink X.25 9.2 Yes
Sun SunLink HSI/S or HSI/P 3.1
Sun CDE 1.6
TCL 11.10.0
TK 11.10.0
Expect 5.38
Perl 5.8.4
INFORMIX-IDS (UC6) 10.0
INFORMIX-Client SDK (UC5) 2.8.1
INFORMIX-ISQL (UC5) 7.3.2

OSP 5.3.1
Applix Spreadsheet 6.0
Applix Data 6.0
Mozilla 1.7
Python 2.2.3
Sun VTS 6.2
Solstice Backup Server 7.3 Yes
Solstice Backup Client 7.3
RTF license Yes
68P02901W01-S 3-11
Jul 2008
The OMC-R user interfaces Chapter 3: OMC-R Overview
The OMC-R user interfaces

User interfaces
The OMC-R has two user interfaces to operate the OMC-R system:
The Graphical User Interface (GUI)
Command line interface
The OMC-R GUI provides a Graphical User Interface (GUI), based on the Open Software
Foundation Motif (OSF-Motif).
GUI interface
The GUI presents the user with a front panel displaying icons that represent all the modules of
the OMC-R, shown in Figure 3-3. A smaller expert front panel, which does not have icon titles,
is also available for experienced personnel. The expert front panel prevents desktop clutter
and is shown in Figure 3-4.
The OMC-R GUI enables operators to interact with the OMC-R and to carry out network
management functions. All maintenance, network reconfiguration, troubleshooting, and
network administration, apart from equipment repair and replacement can be executed through
a single interface.
Command line interface
The UNIX-based system utilities are executed at the command line of an Xterm window, which is
opened from the GUI front panel.
OMC-R front panel
The GUI front panel contains icons that represent different modules of the OMC-R GUI. A
summary of the current alarms in the network is always displayed on the right-hand side of the
GUI front panel. Figure 3-3 shows the OMC-R front panel and Figure 3-4 shows the expert
OMC-R GUI front panel.
3-12 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R front panel
Figure 3-3 The OMC-R GUI front panel
1 2 3 4 5 6 7 8
16 15 14 13 12 11 10 9
ti-GSM-OMCR GUI frontpanel -00062-ai-sw
Figure 3-4 The Expert OMC-R GUI front panel
Table 3-3 describes the icons on the OMC-R GUI front panel (see Figure 3-3).
Table 3-3 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
Continued
68P02901W01-S 3-13
Jul 2008
OMC-R front panel Chapter 3: OMC-R Overview
Table 3-3 Front panel icon description (Continued)

Number Description
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
3-14 68P02901W01-S
Jul 2008
System Information: GSM Overview The command line interface
The command line interface

UNIX-based utilities
UNIX-based utilities are provided to give additional network management functionality to the
OMC-R GUI in the following functional areas:
Remote login
Synchronization of time with the OMC-BSS
Event management
Event log processing, searching, and filtering event logs
NE database management
System administration utilities
68P02901W01-S 3-15
Jul 2008
The OMC-R in a GSM network Chapter 3: OMC-R Overview
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 3-5. It
consists of an Operation and Maintenance Center Radio (OMC-R) and one or more Network
Elements (NE or nodes). The nodes are a Base Station System (BSS), a Remote Transcoder
(RXCDR), Mobile Switching Center (MSC) or Cell Broadcast Center (CBC) and so on.
Figure 3-5 The OMC-R in a GSM network
3-16 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R functions
OMC-R functions
The OMC-R performs the following functions:

Direct management of BSS and RXCDR and the links between them.
Management of the NE devices associated with the links (on the RXCDR side) between
the MSC, the BSSs, and RXCDRs. It is done using the Operation and Maintenance data
packets sent to or from the NE.
Provides a centralized facility for the network management of up to 120 NEs with up to
90,000 traffic channels for the scalable OMC-R.
Other functions include the following:

Monitoring of events and alarms.
Handling faults.
Reconfiguring NEs.
Uploading and downloading NE software.
Collecting performance data.
Reporting for all the NEs under its control.
RXCDR functions
The RXCDR routes the Operation and Maintenance data packets between the BSS and the
OMC-R, and traffic channels (voice) between the BSS and MSC. The Operation and Maintenance
data packets are routed between the OMC-R and the RXCDR using X.25 packet switching.
Each 2 Mbps link between the BSSs and the RXCDR typically consists of two 64 kbps Operation
and Maintenance links plus 120 ((30 kbps x 64 kbps) x (64 kbps)) traffic channels.
The primary feature of the RXCDR is that it converts the 64 kbps PCM output of the MSC to a
16 kbps rate required for transmission over the air interface (between the BSS and the MS).
The location of RXCDR between the MSC and the BSS, usually in the same area as the MSC
is the most efficient arrangement. Thus, four 16 kbps channels from the RXCDR can be fitted
on each 64 kbps terrestrial circuit. Thus, each 30 channel 2 Mbps PCM link can carry 120
GSM-specified channels with obvious cost savings.
Configurations
A BSS consists of a Base Site Controller (BSC) and one or more remote Base Transceiver
Stations (BTS). Every BTS must be physically connected to its controlling BSC using a 2 Mbps
link. A BTS can also be located in a BSC cabinet, thus creating a collocated BSC or BTS,
usually connected using a LAN. A BSS configuration can have all BTSs directly connected to
the controlling BSC (spoke connection) or the BSS is connected through another BTS (daisy
chaining). A BTS can also have more than one connection to its controlling BSC for redundancy.
The GPROC2 (second-generation processor) and GPROC3 (third-generation processor) boards
allow the BSC to support 100 sites.
68P02901W01-S 3-17
Jul 2008
BSS and RXCDR configuration (SITES) Chapter 3: OMC-R Overview
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 can also contain BTS equipment. Sites 1 to 100 contain
only BTS equipment, they cannot contain the BSC.
Thus there are two possible types of BSS site:

BSC site - This is a BSS with all the BTS functions at remote locations. This BSC also
provides the interface between the MSC and the remote BTS sites.
Remote BTS site - This site forms the remote part of a BSS controlled by the BSC site. The
BSC provides the interface with the MSC.
Example
An example configuration is shown in Figure 3-6.
Figure 3-6 The naming convention and physical links of BSS
RXCDR configuration
An XCDR placed at the MSC is known as a Remote Transcoder (RXCDR). It is regarded as a

separate NE or node. Sometimes, the transcoding functionality is located within a BSC. In
the example above, (Figure 3-6), the transcoding hardware is regarded as a subset of the
BSS SITE 0 configuration.
3-18 68P02901W01-S
Jul 2008
System Information: GSM Overview NE device containment
NE device containment

Containment relationship
There is a containment relationship between each entity in the GSM Network that is modeled
at the OMC-R. This hierarchical structure is known as the Containment Tree. Each entity is
contained within a container, which can consist of more than one entity known as containees.
For example, the MMS (the Multiple Serial interface link) is contained within the MSI (the
Multiple Serial Interface board), which is contained within a SITE. This containment relationship
is used for logical naming, configuration, and event management.
For more details on containment relationships, refer to manual Installation and Configuration:
GSM System Configuration (69P02901W17).
Ports
There are two MMS ports on the MSI board. There can be up to 96 MSI boards in a SITE and up
to 100 SITEs in a BSS. An instance of the MMS can be uniquely identified to the MSI/XCDR
as follows:
Example
MMS port 1 on MSI board 2 in SITE 0 would be named MMS 2 1 X. The first digit is the parent
MSI card, the second refers to the port number and the third is not required.
68P02901W01-S 3-19
Jul 2008
Site configuration Chapter 3: OMC-R Overview
Site configuration

CELL resources
In the Motorola implementation of GSM, a single BTS consists of one or more cabinets and
controls one or more CELLs. The Motorola term CELL is equivalent to the GSM term BTS, since
the Motorola BTS sites can contain more than one cell. GSM requirements specify one cell
per BTS.
The different related resources of a CELL configuration are shown in Figure 3-7.
Figure 3-7 Site Configuration
BTS hardware relating to traffic
A BTS cabinet would contain one or more radio units.
One or more carriers service each CELL, and a single radio unit services each carrier. Each
carrier has eight TDMA timeslots.
3-20 68P02901W01-S
Jul 2008
System Information: GSM Overview BTS software relating to traffic
BTS software relating to traffic
From a software perspective, a BTS contains the following software devices or functions:
Digital Radio Interface (DRI) Groups, which contains DRIs.
There is one DRI Group per cell on each site for redundancy purposes.
Receive Transmit Function (RTF) Groups, which contain a number of RTFs.
There is one RTF Group per cell on each site for redundancy purposes.
CELLs.
68P02901W01-S 3-21
Jul 2008
DRI/RTF groups - transceiving Chapter 3: OMC-R Overview
DRI/RTF groups - transceiving

Transceiving functionality
Motorola has implemented transceiving functionality using the DRIs and RTFs. This
functionality provides the radio carrier, which, in a GSM digital system, consists of eight TDMA
timeslots. These digital channels carry speech and various control data. One of the more
important of these control channels is the Broadcast Control CHannel (BCCH). Every CELL
must have at least one BCCH.
Types of RTF
RTFs are used to carry the traffic part of the call (speech or data). They are defined as functions
rather than devices as they are a logical representation of the traffic, rather than relating to
a physical piece of hardware. The RTF contains eight digital channels, one for each timeslot
on the air interface.
There are two types of RTF:

BCCH (one of the timeslots is used as a BCCH)
Non-BCCH
To provide redundancy of RTF traffic, it is possible to specify two routes or PATHs. The routes
are potentially able to carry the RTF traffic from the BTS to the BSC. These PATHs are called the
Primary and Secondary PATHs. If two PATHs are available, then the shorter is the connected
PATH and the longer is the redundant PATH. If the PATH availability changes and a shorter
PATH becomes available to the RTF, then a switchover occurs. Then the RTF starts to use this
new PATH. Refer to Physical links - PATH on page 3-26 for more details of PATHS.
Each RTF function, equipped to a remote SITE, uses two PCM (that is, 2 x 64 kbps, where 64
= 4 x 16 kbps) timeslots per PATH device.
Each OMC-R is limited to support a particular number of RTFs, called the RTF Limit. The
Motorola engineers set the RTF Limit during staging. Each OMC-R has a threshold RTF value,
which is 90% of the RTF Limit.
Redundancy (within a cell)
The DRI Group and RTF Group are used to support transceiving redundancy for CELLs.
Typically, for n RTFs, there is n+1 DRI devices equipped. When the RTF is equipped, it attaches
itself to an available In Service (INS) DRI. If the DRI goes Out Of Service (OOS), the RTF
attaches itself to another available DRI to maintain transceiving functionality to the CELL.
3-22 68P02901W01-S
Jul 2008
System Information: GSM Overview CELL configuration
CELL configuration

Logical devices
A CELL contains the following logical devices:

Neighbor
Handover control
Power control
Handover control
Handover means switching a call from a channel in a given CELL, to another channel in to
another channel in the same or another CELL. This handover is done keeping disturbance to a
minimum, ideally in a way not noticeable by the users.
The BSS allows adaptive power budget handovers (if enabled) on a per cell or neighbor
basis. The adaptive handover methodology allows handovers to be recognized based on a
cumulative area rather than a vote. At each measurement report, the cumulative area is
updated and compared to a cumulative trigger. If the power budget (pbgt) dips below the
handover margin temporarily, the cumulative area is decremented by the difference and not
reset. If this cumulative area is then greater than the cumulative pbgt trigger, a need for a
handover is recognized. The cumulative area is based on either a per cell or a per neighbor
basis as decided by the operator.
Handover control is the functionality required to detect and effect a handover, to maintain
acceptable service to the user.
Handover detection algorithm
There are a number of parameters used to detect when a handover occurs. A number of factors
are input to this algorithm. These factors are as follows:
Uplink and downlink receive signal strength.
Uplink and downlink receive signal quality.
Power budget.
When a power budget handover is enabled, the call is handedover to a neighboring cell.
The handover is at the point where a lower power budget can be achieved (both the MS
and the BTS can reduce their TX power).
68P02901W01-S 3-23
Jul 2008
Power control Chapter 3: OMC-R Overview
Interference.
Distance (between the BTS and the MS).
NOTE
Uplink is from the Mobile Station (MS) to the BTS, downlink is from the BTS to
the MS.
There are thresholds supported for each measurement and when a threshold is exceeded,
a handover occurs.
Power control
In order to reduce radio frequency interference in the network, and increase battery life on
MSs, it is desirable to run all the BTSs and MSs in the network at the minimum TX power. This
provides adequate rxqual (quality) and rxlev (level) for a call.
Power control is the functionality to detect and effect the modification of transmission power,
both for the MS and BTS, to maintain an acceptable service to the user.
A dynamic power reduction algorithm can be used in conjunction with the standard power
control algorithm. In the event that the power level exceeds the upper level threshold, the
algorithm allows the decrement step size to change dynamically based on the proximity to the
upper power threshold. The algorithm is used to reduce the power level to one under the
threshold level. The calculations are made for both uplink and downlink power control.
Power control detection algorithms
There are a number of parameters, which are used to detect when power control occurs.
A number of factors are input to the algorithms. These factors are:

Uplink and downlink receive signal strength.
Uplink and downlink receive signal quality.
There are thresholds supported for each measurement. When a threshold is exceeded,
transmission power modification can occur.
3-24 68P02901W01-S
Jul 2008
System Information: GSM Overview Links in a GSM network: overview
Links in a GSM network: overview

Information on links
Note the following BSS link definitions:

All links to and within BSSs and RXCDRs are in reality links to and between SITEs.
A link to a BSS, is a link to the SITE configured as a BSC within the BSS.
Similarly, links within a BSS, links between the BSC and BTSs and that between one BTS
and another, are all links between SITEs.
SITE link requirements
Every SITE must contain at least one Multiple Serial Interface (MSI) board (NIU for Horizon),
which is a communication controller containing two 2 Mbps (MMS) ports.
Link types
There are two types of links used in the GSM network:

Physical links
Logical links
68P02901W01-S 3-25
Jul 2008
Physical links - PATH Chapter 3: OMC-R Overview
Physical links - PATH

Connection
A physical link between two SITEs is made by connecting the MMS port of the MSI (NIU for
Horizon) card on one SITE, to that on another SITE.
Physical link requirements
The following are physical link requirements:

Every BSC must be physically connected to the OMC-R. A BSC is directly connected to the
OMC-R, or through the RXCDR or MSC.
Similarly, every BSC must be physically connected to its controlling MSC. A BSC is directly
connected to its controlling MSC or it is connected through the RXCDR.
Every BTS must be physically connected to its controlling BSC. A BTS is directly connected
to its controlling BSC or it is connected through another BTS (daisy chaining). A BTS can
have more than one signaling and traffic connection to its controlling BSC giving load
sharing and redundancy.
PATH devices
A PATH device defines the connectivity between a BSC site and BTS sites under its control.
It is a logical representation of a 2 Mbps route between the BSC and a destination BTS.
This connectivity specifies the physical route from the BSC, through intermediary BTSs to
the destination BTS. A PATH can contain a route through a maximum of 10 BTS sites. The
connection information between any two sites consists of the MSI (NIU for Horizon)/MMS
device at each end of the link.
3-26 68P02901W01-S
Jul 2008
System Information: GSM Overview PATH devices
Figure 3-8 shows two PATHs connecting BSC 0 with BTS 3, a PATH through BTS 1 and BTS 2,
(A-B-C), and one direct connection between BSC 0 and BTS 3 (D).
Figure 3-8 Example of path settings within a BSS

BSS
BSC 0
A BTS 1
D
B BTS 2
C BTS 3
PATH 1 = A-B-C
PATH 2 = D
ti-GS M-BS S pa th s e ttings e xa mple -00067-a i-s w
68P02901W01-S 3-27
Jul 2008
Logical links Chapter 3: OMC-R Overview
Logical links

Introduction to links
The 2 Mbps physical links in the GSM network, are configured to carry (as well as the voice
traffic channels) many logical links. The links contain signaling information or Operation and
Maintenance data. The OMC-R monitors these links.
Types of link
The types of logical links are shown in Figure 3-9. These links generate events, alarms, and
performance statistics, at the BSC (or RXCDR) site where they are equipped, and are reported
to the OMC-R.
The different logical links are as follows:
Operation and Maintenance Link (OML)
The purpose of the OML is to provide communication between an OMC-R and a BSC, or RXCDR
for transferring network management (Operation and Maintenance) data. Up to four OML links
can be configured between an OMC-R and BSC, or RXCDR. One OML is used at any given time.
The other three OMLs exist for redundancy purposes.
Message Transfer Link (MTL)
The purpose of the MTL is to provide a link for signaling information between the BSC and the
MSC. In the Motorola system, when local transcoding is used, MTL is a physical connection
between the BSC and the MSC. When a Remote Transcoder is used, the logical MTL is made
up of two physical parts. One connection is between the BSC and the RXCDR and the other is
between the RXCDR and the MSC.
When more than one MTL is configured between the BSC and MSC, both load sharing and
redundancy are present. Up to 16 MTLs can be configured between a BSC and MSC.
Radio System Link (RSL)
A signaling link between a BSC and a remote BTS is called a Radio System Link (RSL). The
purpose of an RSL is to provide signaling information between a BSC and a remote BTS. The
timeslots used, are chosen automatically by the Motorola software, thus ensuring that new
BTSs, added to the network, can be communicated with on default timeslots.
Each RSL link is associated with a PATH. It is possible to have multiple (up to eight) RSLs
between a BSC and a remote BTS. For example, in Figure 3-9, there are two RSLs between
BTS2 and the BSC. It is possible because of the daisy chain connection in the BSS. The two RSLs
provide both load sharing and redundancy functions for the signaling link.
3-28 68P02901W01-S
Jul 2008
System Information: GSM Overview Requirements
RXCDR to BSC Link (XBL)
An XBL link is configured between the BSC and the RXCDR for exchanging internal Fault
Management (FM) data between them. An Enhanced XBL (EXBL) will allow generic messaging
between the RXCDR and the BSC in support of current and future operator needs.
Cell Broadcast Link (CBL)
A CBL link can be configured between the BSC or RXCDR and the Cell Broadcast Center (CBC).
This link is used for downloading messages to broadcast along with other necessary information
such as repetition rate and number of broadcasts.
Requirements
Figure 3-9 shows the different logical links in a GSM network. Logical link requirements:
A BSC always contains at least one OML (with a maximum of four), one MTL or XBL/EXBL
(depending on how it is connected to the MSC) and at least one RSL for each remote
BTS under its control.
An RXCDR always contains at least one OML, and at least one XBL/EXBL.
A BTS always contains at least one RSL.
68P02901W01-S 3-29
Jul 2008
Requirements Chapter 3: OMC-R Overview
Figure 3-9 The different logical links in a GSM network

ffer l s:
-S I
(C I O T )
L O -BS I
)
XBL:RX CDR--BSC LINK

X.25
2 M bps lin
k
CB C
2 M bp slink
RS L11
)
BTS 1
)
BTS 2
3-30 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R connection to the network
OMC-R connection to the network

Transferring data
For every BSC in the network, one or two timeslots (64 kbps) on a 2 Mbps link is used to carry
the Operation and Maintenance data between the BSC and the RXCDR. All the timeslots from
the different BSC-RXCDR links are grouped onto one or more 2 Mbps links by the RXCDR or the
MSC. The RXCDR transfers the information to a packet switch/multiplexer.
The X.21 links are connected to the OMC-R through a public or private X.25 network/switch.
Figure 3-10 illustrates the method of transferring the Operation and Maintenance data between
the BSS and OMC-R network elements (NEs). Other NEs can also communicate with the
network.
X.21 connection configuration
The physical connection between the OMC-R processor and the packet switch/multiplexer
consists of two to seven X.21 connections. Each physical connection can support up to 256
virtual circuits. There are four types of virtual circuits that can be made on the OML:
Event Interface (EI) transfers data packets (events and alarms), plus the OMC-BSS
message from a NE (for example, a BSS) to the OMC-R. The circuit is made by the NE
calling the OMC-R.
Boot Load (BL), also called Download, transfers the BSS software and the BSS databases
to the NE. The NE calling the OMC-R makes the circuit.
Upload (UL) transfers the BSS database backups and raw statistics (performance data) to
the OMC-R. The OMC-R calling a NE makes the circuit.
Remote login (RL) provides sessions for transfer of BSS GUI commands or responses to a
NE. The OMC-R calling the NE makes the circuit.
The virtual circuits EI and BL can be accepted on any of the X.21 connections on the OMC-R.
Normally two connections are set up for EI and BL. If a given port is not working, then
the packet switch/multiplexer switches to a different port. The UL circuit 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 3-10 shows the communication between the OMC-R and other network elements.
68P02901W01-S 3-31
Jul 2008
X.21 connection configuration Chapter 3: OMC-R Overview
Figure 3-10 Communication between the OMC-R and other network elements
PROCESSOR
O and M
(two to seven
2 Mbps link
NAILED CONNECTIONS
(ONE PER O and M TIMESLOT)
64 kbps O and M
TIMESLOT
ti-GS M-OMCR ne twork e le me nts commu nica tion-00069-a i-s w
3-32 68P02901W01-S
Jul 2008
System Information: GSM Overview Operation and Maintenance of a BSS or RXCDR
Operation and Maintenance of a BSS or RXCDR

Simplified network
A simplified network showing some of the hardware devices in the different sites, and the links
between them, is shown in Figure 3-11. BSS1 from Figure 3-10 is used as the example BSS.
Figure 3-11 Simplified GSM network showing devices and links at BSSs
68P02901W01-S 3-33
Jul 2008
Operation and Maintenance information flow between OMC-R and NEs Chapter 3: OMC-R Overview
Operation and Maintenance information flow between

OMC-R and NEs

Summary of information flow
A summary of the information flow between the OMC-R and other NEs (for example, RXCDR
and BSS) is shown in Figure 3-12. The primary function of the OMC-R is to monitor the health
of the radio network.
Figure 3-12 Information flow between the OMC-R and BSSs
OMC-R TO NE OMC-R NE TO OMC-R
1. GUI COMMANDS 1. EVENTS & ALARMS

(through GUI OR REMOTE LOGIN) 2. NE RESPONSES TO
- FAULT HANDLING GUI COMMANDS
- SITE CONFIGURA TION 3. PERFORMANCE DA TA
- SITE RESETS (RA W STATISTICS)
2. SOFTW ARE and NE 4. NE DATABASE UPLOADS
DATABASE DOWNLOADS 5. CM DATA
3. NE DATABASE DOWNLOADS
NE NE NE NE NE
ti-GSM-OMCR BSS information flow-00071-ai-sw
Information flow
Events such as changes of state of a hardware device, link, or function and alarms which could
be service affecting are sent to the OMC-R, through the RXCDR and the X.25 packet switch. In
the OMC-R, they are processed into a standard format. The alarms can be configured to update
a network map, which gives the operator a visual warning by causing the appropriate BTS or
BSC to flash. The alarms or events can also be displayed on the operator terminals. They
are displayed within different windows, depending on how the network operator (or OMC-R
administrator) has configured them.
The RXCDR contains several of the same devices, links and functions as the BSS, and generates
events and alarms in the same way.
3-34 68P02901W01-S
Jul 2008
System Information: GSM Overview Information flow
Regardless of the number of BTSs, the BSS is regarded as a single NE, and runs only one
software load, for example, BSSGSM 1.6.0.x. When loading a BSS, the entire load is first sent to
the BSC, which then distributes the appropriate load objects to the configured BTSs. A copy of
the active BSS load is stored at the OMC-R as it is a copy of the previous version of the BSS
software. These software loads must be compatible with the load installed on the OMC-R. The
RXCDR receives the same software load as a BSS, it just implements a different part of it.
Each BSS and RXCDR contains an operational database. The database has the configuration
data for all the devices and links in the SITES within the NE is stored. A backup copy of the
active database is kept at the OMC-R.
Performance measurements for the different BSS and RXCDR are periodically routed every 30
minutes or 60 minutes to the OMC-R as raw statistics in a data file. This data is stored in a
database at the OMC-R, and processed into statistics which provide valuable information for
efficient network management and planning.
68P02901W01-S 3-35
Jul 2008
OMC-R system configuration

Motorola OMC-R
A typical hardware configuration of the Motorola OMC-R, is shown in Figure 3-13.
Figure 3-13 An example Motorola OMC-R system configuration
Typical hardware configuration
An OMC-R comprises a central system processor and several GUI processors. Each processor is
a complete UNIX system, which provides a GUI interface presented on a color monitor. The
system is connected through a LAN allowing all workstations access to a laser printer. The
GUI server is a server that allows the GUI processors to run on a fast machine while using
the slower machine for the display process.
NOTE
Some systems are configured differently; for specific information the OMC-R Bill
Of Materials (BOM) must be consulted.
3-36 68P02901W01-S
Jul 2008
System Information: GSM Overview Communications handling
Communications handling

Communications software
The OMC-R communications software provides control and support for the protocol stacks
which interface the OMC-R with the following:
Internal OMC-R communications:
TCP/IP
Ethernet
X.11
The NEs in the GSM network - X.25.
The X.25 software is loaded in the system processor, and the X.11 driver software is loaded in the
GUI Processors. The remaining communication software is shared between the two processors.
The operating processes are linked between machines by the Interprocess Communication
(IPC). The OMC-R network can be extended to include further GUI Processors, or secondary GUI
servers, connected either locally or through a Wide Area Network (WAN). Bridges and gateways
can also be used to connect to other computer systems such as an NMC, or other OMC-Rs.
68P02901W01-S 3-37
Jul 2008
Packet switch or multiplexer Chapter 3: OMC-R Overview
Packet switch or multiplexer

Connections
The OMC-R is connected to the GSM Network, to receive the Operation and Maintenance data
using a packet switch/multiplexer (as shown in Figure 3-14). The Packet Switch makes available
a maximum of 256 x X.25 virtual circuits for the exchange of Operation and Maintenance data
between the OMC-R and the NEs.
Figure 3-14 Example Packet switch or multiplexer connections

2 Mbps 2 Mbps
Links Links
Packet Switch or multiplexer
HSI Card HSI Connections
OMC-R
System processor system
processor
ti-GSM-Packet switch mux connections-00073-ai-sw
Packet switch
The connection between the system processor and the Packet Switch could be direct or
connected through a Private eXchange Public Data Network (PXPDN).
3-38 68P02901W01-S
Jul 2008
System Information: GSM Overview Operation and Maintenance network traffic capacity
Operation and Maintenance network traffic capacity

Peak traffic capacities
The system processor supports the following Operation and Maintenance peak network traffic
capacities:
100 x X.25 packets per second, with a packet length of 128 bytes, aggregate.
100 kbps aggregate.
The system processor can be configured to handle up to 90,000 traffic channels. The traffic
channels are associated with a maximum of 120 NEs through the 256 x X.25 virtual circuits.
68P02901W01-S 3-39
Jul 2008
OMC-R system processor Chapter 3: OMC-R Overview
OMC-R system processor

Introduction to the system processor
The hardware configuration of the system processor (for example, the number of CPU
processors, memory and disk capacity) can be varied depending on whether the low-capacity,
mid-capacity, or high-capacity TCH OMC-R is chosen. Thus, the scalable OMC-R provides easy
and cost effective expansion or reduction from low-capacity TCH through mid-capacity TCH
to high-capacity TCH configuration. The software requirements are the same for all capacity
Scalable OMC-R configurations.
System processor
System specifications
The system processor software is installed on internal and external disks depending on the
system processor in use. All system and data areas are mirrored for redundancy.
Figure 3-15 shows the Scalable OMC-R high-end system processor.
Figure 3-15 Scalable OMC-R high-end system processor
14
14
Connection to GSM network
The Scalable OMC-R uses Sunlink X.25 application software and connects to the network using
a HSI/S card. This allows the Scalable high-end OMC-R to be used where there is existing
packet switching and multiplexing equipment available, or to be connected to a public packet
switched network.
3-40 68P02901W01-S
Jul 2008
System Information: GSM Overview Feature description
OMC-R application software impact
Existing system processor OMC-R application software has been ported to work on the Solaris
10 OS.
Feature description
Table 3-4 gives a comparison between the four Scalable OMC-R configurations.
Table 3-4 Scalable OMC-R configurations (maximum values)
Scalable OMC-R Scalable OMC-R Scalable OMC-R Scalable OMC-R

Feature
low-end mid range mid range high-end
RTFs supported 714 1430 4285 6000
NEs supported 64 64 120 120
Total GUI 5 10 10 10
sessions
supported
Dial-up sessions 1 1 1 1
per GUI
processor
Total remote 2 2 2 2
dial-up sessions
Remote login 6 6 20 30
sessions
downloads
uploads
Sustained event 8 alarms + 8 alarms + 12 alarms + 12 alarms +
rate 2 state changes 2 state changes 3 state changes 3 state changes
Maximum event 20 events/s over 60 events/s over 60 events/s over 60 events/s over
burst 20 mins 20 mins 20 mins 20 mins
External interface (OMC-R to BSS)
The high-end Scalable OMC-R does not affect the OMC-R-BSS (rlogin) and the SMASE-NMASE
interface.
68P02901W01-S 3-41
Jul 2008
Configuration Chapter 3: OMC-R Overview
Configuration
The configuration of the system processor is shown in Figure 3-16. It uses a Solaris 10 UNIX
operating system and contains a DataBase Management System (DBMS) from Informix (which is
configured for storing the performance statistics). The Event Management Information Base
(EM MIB) containing the incoming events and alarms, updates the map displays. The map
displays present the operator with visual indication of alarms in the network. The System
processor also contains the CM MIB, which holds the configuration data required to run the
network maps.
Figure 3-16 System processor software configuration
10
3-42 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R GSM application software: overview
OMC-R GSM application software: overview

OMC-R processes
The functional software areas of the OMC-R are split between the OMC-R system processor
and the GUI processor. The processes of the OMC-R application software installed on the
OMC-R system processor are shown in Figure 3-17. The operator is provided with a front
end to all these processes at the OMC-R GUI. The command line utilities provide additional
front-end functionality.
Figure 3-17 OMC-R GSM (System processor) software components
OMC-R (System Processor)
Performance SW Load
Management Management
Configuration Event/Alarm
Management Management
Device Remote
Management Event Login
Interface
ti-GSM-System processor sw components-00076-ai-sw
System processor software elements
The software elements constituting the system processor software perform the following
functions:
Performs network element Operation and Maintenance management tasks.
Provides database storage facilities.
Provides the interface to the network elements through the X.25 network.
The OMC-R system processor software elements are as follows:
Configuration management
Configuration management allows the operator to perform the network configuration tasks, and
to maintain all details of the network configuration at the OMC-R.
68P02901W01-S 3-43
Jul 2008
System processor software elements Chapter 3: OMC-R Overview
Performance management controls the collection, administration, processing, and storage of

NE performance statistics.
Software load management
Load management provides a facility for uploading and downloading the NE software loads, and
NE operational databases. It also provides a means of managing multiple copies of software
loads for back up purposes.
Event/alarm management
Event/alarm management provides a mechanism at the OMC-R for alarm surveillance. It

manages events and alarms routed to the OMC-R from other NEs, or generated within the
OMC-R.
Remote login
The remote login software manages the X.25 connection for remote login to network elements
from the OMC-R. Remote login is a means by which the operator performs configuration
management, fault management, and some performance management procedures at the
network elements.
Event interface
The event interface handles the X.25 alarm connections to the network elements, then translates
and forwards incoming events and alarms to the event/alarm management functional software.
Device management
Device management allows the operator to perform fault management and configuration
management at the OMC-R. The OMC-R supports most hardware devices and software functions
located at the remote network elements.
3-44 68P02901W01-S
Jul 2008
System Information: GSM Overview UNIX: Solaris 10 operating system
UNIX: Solaris 10 operating system

Platform
The system processor operates under the Solaris 10 operating system. It provides the platform
for the OMC-R software applications and provides facilities for system administration.
Advantages
The main advantages of this operating system are that it is designed to provide:
An enhanced multi-architecture solution for systems to support Internet or Intranet
connectivity.
A system offering a Scalable, secure, and reliable operating environment.
Features
Included with this release is the Common Desktop Environment (CDE). It provides users with
a flexible open user environment that has a common look and feel across all major UNIX
desktops. This environment allows transparent access to the network resources; and allows
frequently used UNIX commands to be iconised. It is also possible to drag and drop between
files and commands.
Tools and applications
The Solaris 10 operating system includes the following tools and applications:
Solstice backup utilities
The Solstice backup software allows a Solaris operating system server to provide
automated, high performance backup, recovery and storage management services to
machines on the network.
Solstice backup provides simple centralized administration, through a single unified view
of the entire data management operation from any point on the network. Intuitive user
interfaces simplify administrative tasks such as configuring clients and servers, and setting
up backup schedules for file systems and databases.
68P02901W01-S 3-45
Jul 2008
Tools and applications Chapter 3: OMC-R Overview
Solstice AdminSuite
Solstice AdminSuite software provides an integrated collection of graphical user interfaces to

perform administrative tasks such as managing hosts, users, groups, administrative data, file
systems, disks, printers, and serial port devices.
The Solaris operating system allows the OMC-R to be administered as a typical UNIX system.
3-46 68P02901W01-S
Jul 2008
System Information: GSM Overview The OMC-R database
The OMC-R database

RDBMS
The OMC-R database, maintained at the system processor, uses an industry standard Relational
Database Management System (RDBMS) known as INFORMIX. The DBMS manages access to
its own stored data and provides its own data protection. It is made up of a PM sub-schema, a
CM sub-schema, and an EM sub-schema. The PM sub-schema is used for storing processed
performance statistics from the GSM network. The CM sub-schema holds the configuration
data needed for network maps used by the OMC-R GUI and for cell parameter optimization.
The EM sub-schema stores the subscription lists used to subscribe to incoming events and
alarms (see Figure 3-18).
Database schema
The OMC-R database is a centralized data store for data that has to be further manipulated,
either by system users or by other OMC-R application areas. A database schema is a data
model of a precise, complete definition of the data to be stored. It provides a formal notation
data model of tables, rows, columns, and keys. The database schema predefines the tables in
which the data is stored. The physical structure of the tables cannot be altered, only their
contents can be manipulated.
Figure 3-18 OMC-R database - database schema breakdown
68P02901W01-S 3-47
Jul 2008
Database size Chapter 3: OMC-R Overview
Database size
The database can be sized at installation to meet the requirements of the GSM Network. The
disk is hardware mirrored to provide a high level of protection against loss of data in case
of hardware failure.
Applications and utilities
The management of the OMC-R database is accomplished using Informix-OnLine utilities

and OMC-R applications built around them. The OMC-R database supports the following
applications:
Structured Query Language (SQL) and Applix access for custom reporting
SQL and Applix are industry standard languages, which can be used to write applications to
extract performance management data from the database. Read-only access to the data is
available.
Database backup and administration utilities
The OMC-R system administrator is provided with a facility for online back up of the OMC-R
database. This back up avoids halting the OMC-R during routine back up operations.
3-48 68P02901W01-S
Jul 2008
System Information: GSM Overview The OMC-R GUI configuration
The OMC-R GUI configuration

Running the OMC-R GUI
Typically the OMC-R configuration contains several processors; one Netra 210 or Sunblade 150
GUI server and Sunblade 150s as GUI clients. A second can be configured as a GUI server
or the system processor can fulfill this GUI server role. Two GUI servers are the preferred
arrangement and each supports half of the GUI clients. This arrangement allows system
operation to continue if one of the GUI servers fails.
Each machine is a complete UNIX system, which runs the same GUI version.
The network file system
The OMC-R GUI expects all the GUI clients to be configured as standalone NFS (Network File
System) machines. This configuration allows each machine some degree of independence
while still allowing resources to be shared.
LAN configurations
The Sunblade 150s execute the display process and function as operator workstations. The
OMC-R GUI software is made accessible over the LAN by configuring the machines in the
following way:
A Sunblade 150 is installed as a GUI Server to the Sunblade 150 GUI clients.
Other configurations
Other network configurations can also exist, such as a GUI processor configured to run the
OMC-R GUI from a remote site. In networks containing two OMC-Rs, a GUI processor in the
local OMC-R is configured to monitor a remote OMC-R during the night. The local OMC-R
is known as the night concentration center.
68P02901W01-S 3-49
Jul 2008
GUI processor Chapter 3: OMC-R Overview
GUI processor

Server client relationship
Up to 10 additional processors can be added to the system to support the GUI interface. One of
the machines must be configured as a GUI server. The additional machines mount the display
software from the GUI server. The total number of GUI sessions supported is 30 as on the
standard OMC-R. Each processor supports one GUI session.
An example of a GUI processor hardware configuration is shown in Table 3-5. The GUI processor
is configured with software as shown in Table 3-6.
Table 3-5 GUI processor hardware specifications
Hardware Applicable to both 0-10k TCH and 0-45k TCH

Model Sunblade 150
Processor (CPU) 1 x 650 MHz
Memory 512 MB
Disk Capacity 80 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
Table 3-6 GUI processor software specifications
Software Applicable to both 0-10k TCH and 0-45k TCH

SUN Solaris 10
Informix I-Connect 7.xx UC2
X11 X11 Release 5 Version 26
Desktop Motif 1.2.5G for SPARC 2.x single user license Sun Solaris
CDE 1.0.2
Interleaf (GUI Server only)
TCL (GUI Server only) TCL Version 11.10.0

Expect (GUI Server only) Expect Version 5.38
Applix (GUI Server only) Applix 6.0
3-50 68P02901W01-S
Jul 2008
System Information: GSM Overview The network status summary feature
The network status summary feature

Maps
Figure 3-19 shows the maps icon on the OMC-R GUI front panel.
Figure 3-19 Maps icon
ti-GSM-Maps icon-00078-ai-sw
The role of the OMC-R in a GSM network is to allow network operators to perform network
management functions to ensure that the network operates efficiently, and the service to the
customer is maintained. The OMC-R acts as a central collection point for measurement data
used in the analysis of current performance and future planning of the network.
Features
The NSS features are as follows (refer to Figure 3-20):

Network maps
Alarms icon
Alarm summary
68P02901W01-S 3-51
Jul 2008
Features Chapter 3: OMC-R Overview
Figure 3-20 The network status summary options on the GUI front panel
3-52 68P02901W01-S
Jul 2008
System Information: GSM Overview The CM MIB
The CM MIB

Description of the CM MIB
The system processor contains the CM Management Information Base (CM MIB) that holds all
the configuration data. The data is required for the network maps of the OMC-R GUI and for
cell parameter optimization. Information in the CM MIB includes lists of the various types of
nodes in the GSM network, with their attributes and interconnections. The CM MIB also lists
maps containing nodes and connections on each map. All the GUI processors which run the NSS
feature, communicate with the CM MIB using an internal process called cm_mib.
Populating the CM MIB
The CM MIB can be populated with NE data by selecting:

Audit
or
Detailed View Forms (for each object)
68P02901W01-S 3-53
Jul 2008
GUI client Chapter 3: OMC-R Overview
GUI client

Software configuration
Sun Micro systems Sunblade 150 (operator workstations) display the GUI data. This GUI
client is installed on either the system processor, or on one of the Sunblade 150 stations. In
all cases, the OMC-R GUI client software is executed on the local Sunblade 150s. A Netra
210 or Sunblade 150 machine is designated as a GUI server to half the GUI clients, providing
redundancy if one of the GUI servers fail.
Figure 3-21 shows the GUI client hardware and software configuration.
Figure 3-21 GUI client hardware and software configuration
Hardware features
The GUI client has the following hardware features:

Local Disk 1.2/4.2 Gb (minimum configuration)
20-inch color terminal
The GUI clients are configured as standalone NFS (Network File System) machines.
3-54 68P02901W01-S
Jul 2008
System Information: GSM Overview Night concentration
Night concentration
Figure 3-22 shows a night concentration center with one ULTRA5/Sunblade 150 configured as a
GUI Server for both region A and region B. That is, only one workstation is required during the
quiet night periods enabling a reduction in operating personnel.
Figure 3-22 Night concentration configuration
Printer
Printer
GUI Server LAN X.21

Bridge/ Router GUI Server
LAN
GUI Client Router (region A)
GUI Server
(region B)
GUI Client
System Processor Leased Line
Concentration centre
Regional OMC-R A (local)
Printer
LAN
GUI Server
Bridge/ Router X.21
GUI Server
GUI Client
System Processor
Regional OMC-R B (Remote)
ti-GSM-Night concentration config-00081-ai-sw
68P02901W01-S 3-55
Jul 2008
Network status summary Chapter 3: OMC-R Overview
Network status summary

Map process
When a network map, for example, Network 1600b: Device Mode (see Figure 3-23), is selected
using the Maps icon on the OMC-R front panel, a map process is invoked on the GUI processor.
Figure 3-23 Map processes
Active
NSS subscription List
3-56 68P02901W01-S
Jul 2008
System Information: GSM Overview Configuration data
Configuration data
All the configuration data required to run the network map are stored in the CM MIB, which is
maintained on the OMC-R system processor. The CM MIB stores a series of managed objects to
which relevant network configuration data and data required to configure maps are assigned.
For example, both a BSS and a Map are regarded as managed objects with different data. All
the GUI processors that run the network maps communicate with the CM MIB using an internal
process called cm_mib.
The EM proxy process
The EM Proxy process contains a list of all NEs, SITEs, cells, and links. The process examines
the incoming alarm messages and compares it to the list. It updates the list if a change has
occurred. Every two seconds, a changed list is forwarded to the GUI processor. The list contains
attributes, which reflect the severity of the alarm and its handling state. These attributes
in turn update the Alarm Summary on the GUI front panel, and the attributes of the links
and nodes on the active map, as configured in the CM MIB. The Contained Devices form and
alarm icons are also updated. Similarly, incoming State Changed Events from SITEs and MMSs
change the state of the attributes in the CM MIB. It reflects the administrative and operational
states of the different SITE and CommsLink configuration objects, representing the physical
devices in the network.
68P02901W01-S 3-57
Jul 2008
GUI clients and servers: Overview Chapter 3: OMC-R Overview
GUI clients and servers: Overview

Client or server system
The client or server concept is a common form of distributed system in which software processes
are split between server tasks and client tasks. A client sends requests to a server, according
to a standard protocol, asking for information or action. The server responds by sending the
requested information or by performing the required action.
This operation is analogous to a customer (the client) who sends an order (request) on an
order form to a supplier (the server). The supplier despatches the goods and sends an invoice
(response). The order form and invoice are part of the protocol used to communicate in this
analogy.
The connection between a GUI client and GUI server is through message passing, which is over
a network or even within a single machine. There is a single centralized server or several
distributed servers, depending on workloads. This model allows clients and servers to be placed
independently on nodes in a network, possibly on different hardware and operating systems.
GUI servers and GUI clients
The GUI servers and GUI clients have now replaced the older MMI servers and clients. However,
MMI servers and clients can both be re-deployed as GUI clients, but only the high-end MMI
servers have the power to run as a GUI server.
3-58 68P02901W01-S
Jul 2008
System Information: GSM Overview Network maps
Network maps

Functionality
Network maps show status information on the network and enable the following different types
of functionality to be invoked for a selected NE:
Current network configuration
Network maps present the current network topology. Network configurations can be updated
using the Detailed Views and an Audit, initiated to ensure consistency between the MIB and
the Network. A full network map, which displays all NEs and links in the network is available.
Each NE can be expanded to show the SITEs and links within the NE. Maps can be zoomed or
expanded when displayed (refer to Figure 3-23). If the system is configured, more detailed maps
of any part of the network can be displayed.
Alarm state
A color change in the NE and link icons on the map indicate the incoming alarms. The alarms
icon on the front panel also flashes, and wherever available, there is an audible warning.
MMS and SITE service states
The map display uses three different icon types to represent state changes in SITEs (represented
by SITE map nodes) and MMS devices (represented by map links). Refer to The map display
on page 3-61 in the Map Display section. The icon types represent in-service (INS),
out-of-service (OOS), and unknown states. The operational and administrative states of the
SITE or MMS determine the state changes.
An alarm display window for the NE or SITE on the map
Each map provides an alarm display window that subscribes only to incoming alarm messages
for selected NEs or SITEs. This window allows standard alarm handling to be performed.
Remote login through TTY window for the NE on the map
Remote login, through a TTY window for a selected NE, allows BSS GUI commands to be sent to
the NE. The responses to the commands can be monitored.
Provide resynchronization functions
The system checks the active alarm list for any unhandled alarms and retransmits any state
changes that have occurred since the previous Resync operation.
68P02901W01-S 3-59
Jul 2008
Different maps available Chapter 3: OMC-R Overview
Different maps available
The following maps are available for selection:

One map showing the full network configuration, containing all configured nodes and links.
One map for each BSS or RXCDR, containing all configured SITEs and links.
The administrator can configure all other maps.
Map modes
There are two map modes available from the View menu:
Device Mode displays severities according to the impact of faults on devices. For example,
a critical redundant device produces a critical severity.
Subscriber Mode displays severities according to the impact of faults on subscribers. For
example, service loss, capacity loss, or redundancy loss.
Map configuration
Different maps of the network can be displayed, depending on what type of information the
operator has to monitor. This is achieved by adding the new map configuration data to the CM
MIB through the Detailed View forms and Audit. The OMC-R GUI provides facilities for the
automated process, followed by operator input for longitude and latitude data.
When the MIB is initially populated with data from configuration files, default maps are created.
In the absence of any geographical map background files, the maps are displayed on a default
map background consisting of a single solid color. To use map backgrounds other than the
default, a background map, usually a geographical map, is assigned to the map object, which
configures the network map.
3-60 68P02901W01-S
Jul 2008
System Information: GSM Overview The map display
The map display

Map backgrounds
When maps are initially configured, they are displayed on a default map background of a single
solid color. A background, usually a geographical map background, is assigned to the network
map. Each map background is specified when defining the MapNode object. This map points to
a physical file describing the actual shape of the background map.
Map links
Each map link represents one or more 2 Mbps links between the NEs or SITEs in the network.
This is set when the map is configured. A cluster icon is used to represent a group of icons,
which are too close together to be displayed separately on the map.
Alarm reporting
If an icon on a map is flashing, it indicates that there are alarms which are not handled for
the device or devices it contains. Alarms from links cause both the link and the node, where
the faulty MSI/MMS is contained, to flash. The icon color is automatically reset to the color
representing Clear (defaulted to green) when the operator clears the alarm, or an alarm clear
message is received from the network.
State changes
The status of a SITE or MMS in the network determines whether it is in service (INS), or Out Of
Service (OOS. INS indicates it is supporting (or able to support) user traffic and OOS indicates
that it is unable to support user traffic. The administrative state (controlled by the operator)
and the operational state (controlled by the NE fault management application) determine the
device status.
The different combinations of operational and administrative states determine whether the node
or link is INS, OOS, or has an unknown state. For example, a SITE is INS if its operational state
is enabled or busy, and its administrative state is unlocked.
The normal state of a device is INS (busy or unlocked, or enabled/unlocked for a redundant
device). An operator or the NE fault management software can take a device OOS by issuing a
LOCK command or a SHUT-DOWN command. A LOCK is intrusive as it terminates all activity on
the device when the command is executed. The SHUTDOWN command permits the operator to
specify a time interval before the device changes from UNLOCKED to LOCKED state.
The map display uses different icon types to represent a change in state of devices.
Figure 3-24 shows the indications of the icons for an INS, unknown, and OOS device:
68P02901W01-S 3-61
Jul 2008
Additional information Chapter 3: OMC-R Overview
Additional information
Refer to the OMC-R Online Help facility for a complete description of the following:
Network map display.
The subscription lists that control alarm and state changes.
Icon colors.
Pending state
An asterisk *, on a node icon represents nodes in a pending state. Figure 3-24 shows the map
icons.
3-62 68P02901W01-S
Jul 2008
System Information: GSM Overview Additional information
Figure 3-24 Map icons
68P02901W01-S 3-63
Jul 2008
How administrative and operational state changes work Chapter 3: OMC-R Overview
How administrative and operational state changes work

State changes
Administrative and operational state changes are only relevant for SITEs and links on the map.
Figure 3-25 illustrates how the icons representing the SITEs or links are changed to reflect
the change in state of the physical device.
3-64 68P02901W01-S
Jul 2008
System Information: GSM Overview State changes
Figure 3-25 State changes on the map
68P02901W01-S 3-65
Jul 2008
How alarms work Chapter 3: OMC-R Overview
How alarms work

Alarm icons
Incoming alarms are reported by a flashing MapNode or MapLink icon, colored to represent
different alarm severities. If an icon on a map is flashing, it denotes the presence of unhandled
alarms for the device or devices it represents. Alarms from links cause both the MapLink and
the MapNode containing the faulty MMS to flash and change color.
3-66 68P02901W01-S
Jul 2008
System Information: GSM Overview Alarm icons
Figure 3-26 How alarms change on the map
68P02901W01-S 3-67
Jul 2008
Colors Chapter 3: OMC-R Overview
Colors
The color of any displayed icon or link reflects the severity of alarms in the device or group of
devices represented by the icon. The default colors are defined in Table 3-7.
Table 3-7 Alarm icon colors
Color 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 an alarm occurrence in any device within the
group is shown at the displayed icon.For example, a BSS represents all the devices in the BSC
and BTSs within the BSS.
If there are alarms of different severities existing for the same device, or group of devices the
display color reflects the most severe alarm condition.
The icon color is automatically reset to the Clear color when the operator clears the alarm or an
alarm clear message is received from the network.
3-68 68P02901W01-S
Jul 2008
System Information: GSM Overview Map configuration
Map configuration

Introduction to the CM MIB
The CM MIB stores a series of managed objects to which relevant configuration data is assigned.
For example, both a BSS and a Map are considered to be managed objects requiring different
data. All the GUI processors that run the Network Map communicate with the CM MIB using
an internal process called cm_mib.
Figure 3-27 shows the CM MIB showing the different groups of managed objects.
Figure 3-27 The CM MIB showing the different groups of managed objects
68P02901W01-S 3-69
Jul 2008
Two object groups Chapter 3: OMC-R Overview
Two object groups
There are two different groups of objects needed for maps:

Graphic objects
Used to build the different maps and which take their data from the configuration objects.
Configuration objects
Hold all the data about the physical network. There is a containment relationship between
the different managed objects.
3-70 68P02901W01-S
Jul 2008
System Information: GSM Overview Graphic objects
Graphic objects

Graphic objects
There are three graphic objects in the CM MIB. Figure 3-28 shows the containment relationship
between the graphic objects.
Figure 3-28 The containment relationship for the graphic objects
ti-GSM- Graphic objects containment-00087-ai-sw .eps
Map
The Map graphic object represents a map, which appears in the Map List Display menu on
selecting the Maps icon from the front panel. It defines the map name and the background
map used with it.
MapNode
The MapNode graphic object specifies the type of NE or SITE to be represented on the map.
A MapNode can represent any of the following configuration objects:

OMC-R
BSC
MSC
RXCDR
BSC-BTS
BTS
68P02901W01-S 3-71
Jul 2008
MapLink Chapter 3: OMC-R Overview
MapLink
The MapLink graphic object represents one or more CommsLinks.
3-72 68P02901W01-S
Jul 2008
System Information: GSM Overview Configuration objects

The containment relationship between the different configuration objects is shown in

Figure 3-29. The objects are grouped into four logical groups, namely, Hardware Devices,
Software Functions, Logical Links, and Radio Frequency. This reflects the physical configuration
of the devices in the network, and determines the upward propagation of the alarms. For
example, an alarm from the MSI object is also propagated to its parent SITE, which in turn is
propagated to its parent BSS.
68P02901W01-S 3-73
Jul 2008
Configuration objects Chapter 3: OMC-R Overview
Figure 3-29 The containment relationship for the configuration objects
3-74 68P02901W01-S
Jul 2008
System Information: GSM Overview Configuration objects
Network
The network configuration object represents the overall network being managed. There is only
one Network configuration object in the MIB, and it is already configured on delivery.
OMC-R
The OMC-R configuration object represents the Operation and Maintenance Center. There is
usually only one OMC-R object in the MIB.
SoftwareLoad
The SoftwareLoad object is used to point to a BSS or RXCDR software load currently stored
in the OMC-R. A maximum of 2147 483 647 SoftwareLoad objects can be contained within an
SW Inventory object.
MSC
The MSC configuration object represents the Mobile Switching Center. The OMC-R does not
directly manage the MSC, but manages the links between the BSSs, RXCDRs, and the MSC.
There are usually only two of these objects in the MIB.
BSS
The BSS configuration object represents the Base Station System. An object represents each
BSS in the physical network (maximum of 120).
RXCDR
The RXCDR configuration object represents the Remote Transcoder. There are as many of these
objects as exist in the physical network (maximum of 120).
CommsLink
The CommsLink configuration object defines the two MMS ports in the different SITES that
establish the 2 Mbps 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 (E)GPRS Support Node (SGSN).
SITE
The SITE configuration object represents a BSS SITE in the network. The functionality of any
given SITE depends on the devices it contains.
68P02901W01-S 3-75
Jul 2008
Hardware devices Chapter 3: OMC-R Overview
Hardware configuration
All the different hardware cages in a SITE are connected by a LAN, and configured as a BSC
or a BTS. SITE 0 must always contain the BSC functionality, and is configured as a BSC or a
BSC-BTS. The remaining SITEs can only be configured as BTSs. There are as many of these
objects as exist in the physical network (maximum of 100 per BSS). An RXCDR can also have a
SITE 0 associated with it.
Hardware devices
The hardware devices object represents an abstract logical container class. It is used to group
the different hardware devices on the BSS.
Cabinet
The cabinet object class describes a single cabinet within the site.
Cage
The cage object describes a single cage within a cabinet.
EAS
The EAS configuration object represents the detection of a single External Alarm System device
within the site.
Processors
The processors object represents a logical container class. It provides a grouping for the
GPROC (Generic Processor Boards), BSP (Base Site Control) and CSFP (Code Storage Facility)
processors within the site.
KSW pair
The KSW pair object is used to represent a pair of KSW (Kiloport Switch board) devices, which
manage a single TDM highway.
GCLK
The GCLK object represents a Generic clock board. There is one per site.
IAS
The IAS configuration object represents the detection of an Internal Alarm Systems such as
a power supply failure. There is one IAS device per cabinet.
3-76 68P02901W01-S
Jul 2008
System Information: GSM Overview Software functions
LAN
The LAN object represents a single Local Area Network within a site.
TDM
The TDM object represents a single Time Division Multiplex highway within a site.
MSI
The MSI configuration object represents a Multiple Serial Interface (MSI) board, which controls
two MMS ports. There is a maximum of 101 MSIs at SITE 0 and 51 at other SITEs.
COMB
The COMB is a general abbreviation used for a Combiner, which combines two or more RF
transmissions, from a BTS Transceiver Control Unit (TCU), for a simultaneous broadcast to a
single antenna.
Software functions
The software functions represent an abstract logical container class. It is used to group the
different software functions on the BSC.
BTF
The BTF object represents a Base Transceiver Function. There is a single instance of this
class in BSC site 0.
LCF
The LCF object represents a Link Control Function. There is a single instance of this class
in BSC site 0.
OMF
The OMF object represents an OMF GPROC Function. There is a single instance of this class
in BSC site 0.
Logical links
The logical links represent an abstract logical container class. It provides the grouping for
the various links present at the site.
68P02901W01-S 3-77
Jul 2008
Radio frequency Chapter 3: OMC-R Overview
CBL
A CBL link can be configured between the BSC or RXCDR and the Cell Broadcast Center (CBC).
This is used for downloading messages to broadcast along with other necessary information
such as repetition rate and number of broadcasts.
MTL
The purpose of the MTL is to provide a link for signaling information between the BSC and the
MSC. In the Motorola system, when local transcoding is used, this is a physical connection
between the BSC and the MSC. When a Remote Transcoder is used, the logical MTL is made
up of two physical parts; the connection between the BSC and the RXCDR and the connection
between the RXCDR and the MSC.
OML
This link is for control and communication between the BSS and the OMC. The RXCDR provides
an OML, for each BSC connected to it.
XBL
An XBL link is configured between the BSC and the RXCDR for exchanging internal Fault
Management (FM) data between them.
RSL
The RSL represent a Radio Signaling Link. The RSL can only be contained within the remote
BTS in which it terminates.
PATH
The PATH object specifies the path connection between a BSC and a specific BTS site. The path
connection is described as a series of MMS connections between sites. There can be a maximum
of 10 PATH objects contained in a SITE object.
Radio frequency
The radio frequency represents an abstract logical container class. This provides the grouping
for the various radio-related objects.
RTFGroup
The RTFGroup object is used to represent a single RTF function grouping within a site. A
maximum of six RTFGroup objects can be contained in a SITE object.
3-78 68P02901W01-S
Jul 2008
System Information: GSM Overview Radio frequency
RTF
The RTF object is used to represent a single RTF function within a site. A maximum of 25 RTF
objects can be contained in an RTFGroup object.
DRIGroup
The DRIGroup object is used to represent a single DRI device grouping within a site. It contains
one or more DRIs, which are connected to the same antenna and use the same portion of the
TDM highway. A maximum of six DRIGroup objects can be contained in a SITE object.
DRI
The DRI object is used to represent a single Digital Radio Interface (DRI) device within a site. It
provides the interface between the DRCU and the digital portion of a BSS. A maximum of 25
DRI objects can be contained in a DRIGroup object.
CELL
The CELL object is used to describe the cells within a BTS site. Up to six CELL objects can be
created under a SITE object. A maximum of 250 CELLs can be contained within a BSS.
FreqHopSys
The FreqHopSys object is used to represent a single frequency hopping system within a cell.
SMSCBmsg
The SMSCBmsg object is used to represent a single Short Message Cell Broadcast (SMS CB)
message within a cell.
Neighbor
The Neighbor object is used to identify a neighbor cell for a specific cell, that is, those cells
to which it can handover calls. A maximum of 64 Neighbor objects can be created under
a CELL object.
TestNeighbor
The TestNeighbour object is used to describe the test neighbor cells for a specific cell. One
instance of this class represents one test neighbor cell.
Handover control
Handover control objects are RelTimAdvHC, RxlevDlHC, RxlevUlHC, RxqualDlHC, RxqualUlHC,

and SurrndCellHC. These objects describe the handover algorithms based on certain criteria.
For more details, refer to the OMC-R Online Help.
68P02901W01-S 3-79
Jul 2008
ProxyCell Chapter 3: OMC-R Overview
Power control
Power Control objects are RxlevDlPC, RxlevUlPC, RxqualDlPC, and RxqualUlPC. These objects
describe the power control algorithms based on certain criteria. For more details, refer to
the OMC-R Online Help.
ProxyCell
The ProxyCell object represents CELLs outside the current PLMN. A maximum of 500 ProxyCell
objects can be contained in a SITE object.
UserProfile
The UserProfile object represents an OMC-R user who uses the OMC-R GUI. A maximum of
256 UserProfile objects can be contained in an OMC-R object.
Automatically created network objects
The network objects, which the CM MIB process creates automatically, are as follows:
NESoftware
The NESoftware object is automatically created when a BSS or RXCDR object is created.
SW Inventory
The SW Inventory object is automatically created when an OMC-R object, with the active flag
set to TRUE, is created.
MMS
An MMS object is automatically created when the MSI object is created.
TRX
A TRX object is automatically created in a CELL object when an RTF object of type BCCH is
created at a SITE with its carrier attribute assigned to the relevant CELL.
Source
A Source object is automatically created when a Neighbor object is created if the CELL it
identifies exists. Otherwise, a Source object is automatically created when the CELL object
is created.
3-80 68P02901W01-S
Jul 2008
System Information: GSM Overview Automatically created map display objects
Automatically created map display objects
The map display objects, which the CM MIB process creates automatically, are as follows:
Map
A Map object is automatically created when a Network, BSS, or RXCDR object is created.
MapNode
A MapNode object is automatically created when a BSS, OMC-R, MSC, RXCDR, or SITE object is
created. The map node must be associated with an object of the relevant type.
MapLink
A MapLink object is automatically created when a CommsLink object is created.
68P02901W01-S 3-81
Jul 2008
Periodic Supervision of Accessibility (PSA) Chapter 3: OMC-R Overview
Periodic Supervision of Accessibility (PSA)

Definition of PSA
Periodic Supervision of Accessibility (PSA) periodically sends messages to BSSs requesting

information on their current state. This verifies if the BSSs are operational or not.
PSA failure
If a BSS fails to respond to a PSA request for its status, the OMC-R generates an alarm for that
BSS. This alarm indicates that the BSS failed to respond to a message requesting its status, and
is indicative of a problem at the BSS. The OMC-R continues to send messages periodically to the
BSS requesting its status. On receipt of a response message from the BSS, the OMC-R changes
the alarm severity of the message to Clear.
An alarm is also generated when the BSS informs the OMC-R that it is not operational. The
OMC-R continues to send messages periodically to the BSS requesting its status. On being
informed that the BSS has returned to operating correctly, the OMC-R changes the alarm
severity of the message to Clear.
3-82 68P02901W01-S
Jul 2008
System Information: GSM Overview Disk usage exceeded
Disk usage exceeded

System processor partition full
An alarm is raised when either of the two (upper and lower) threshold values of disk usage are
exceeded on the /, the /home, the /usr, and the /usr/gsm/ne_data partitions of the system
processor.
The System removes any logfiles older than three days from the $OMC_TOP/logs directory
using routine maintenance cron jobs, or if the upper disk usage threshold is exceeded. The
threshold value must return to the default value of 90%.
The file $OMC_TOP/config/global/FM_audit.CNFG contains the values that are used for
setting the timers for each audit and disk usage limits. These values are set at the installation
time, and the system administrator can only change the values.
Further information
For information on setting the related parameters, see Maintenance Information: Alarm
Handling at the OMC-R, (68P02901W26).
68P02901W01-S 3-83
Jul 2008
DataGen Chapter 3: OMC-R Overview
DataGen

Introduction to DataGen
DataGen is a GSM product used to create BSS databases offline. DataGen can store past,
current, and future versions in an Informix database. These databases can be transferred to the
OMC-R, and then they are downloaded to the live BSSs. DataGen runs on its own processor and
can be integrated with the OMC-R if they are both on the same LAN.
DataGen is used to make major changes to a network, for example, upgrades to the BSS
software, frequency replans, and network expansion. Figure 3-30 shows the DataGen
configuration in a GSM environment.
Figure 3-30 DataGen in a GSM environment
3-84 68P02901W01-S
Jul 2008
System Information: GSM Overview DataGen configuration management
DataGen configuration management
DataGen provides the user with the capability of performing offline configuration of the
Motorola GSM network entities (NEs). The Informix database contains two types of information:
A representation of the information required to create a Sysgen script for all supported
BSS releases.
Details relating to syntax, parameters, elements, and their associated ranges for the GUI
commands in the Sysgen script are included.
Configuration information for a specific BSS area.
These areas are identified by country or network, name, software release, and
configuration number. The configuration number allows multiple BSSs to exist within the
DataGen database.
Figure 3-31 shows the DataGen main window.
Figure 3-31 DataGen main window
Off-line MIB
Figure 3-32 shows the off-line MIB, which is used to create new networks, visualize, and validate
networks before deployment into a live network. It has a common user interface with the
online OMC-R. BSS binary files are used to create the network which is displayed as a tree like
representation called the Navigation Tree. It is possible to update multiple BSS binary files
simultaneously, for example, propagating neighbor changes from one BSS binary file to another.
The Navigation Tree allows:

Graphical editing of configuration management.
Neighbor propagation.
An interface to radio refrequency planning tools.
68P02901W01-S 3-85
Jul 2008
Off-line MIB Chapter 3: OMC-R Overview
Figure 3-32 Off-line MIB front panel
3-86 68P02901W01-S
Jul 2008
System Information: GSM Overview Feature Capacity Licensing and Audit
Feature Capacity Licensing and Audit

The License Audit tool monitors the usage of carriers across the network on a per feature basis.
Information is gathered by running scheduled audits against the OMC-R CM database. The
audits produce a report indicating the number of RTFs equipped in the database to support
each feature.
The audit is triggered by a configurable interval parameter in the OMC software. If the interval
parameter is not set, or set outside the permissible range of 2 to 48 hours, the default value of
12 hours is used. The result of the audit (actual usage) is compared with the license file per
feature. An alarm is generated for each feature where the license usage is exceeded. If the
usage is within the limit, the License Audit Tool generates a corresponding event. The alarms
and events are displayed at one or all OMCs in the network as configured during the installation.
68P02901W01-S 3-87
Jul 2008
Feature Capacity Licensing and Audit Chapter 3: OMC-R Overview
3-88 68P02901W01-S
Jul 2008
Chapter
BSS Software Release Features

This chapter provides a summary of the features of Motorola BSS software releases. Releases of
software before GSR2 were identified by four-digit release numbers, such as 1.2.1.1. After the
1.4.1.x release, the numbering system was revised; release 1.5.0.x was renamed GSR2.
The following BSS software releases are described in this chapter:

BSS software release 1.1.1.0 on page 4-3.
BSS software release 1.3.0.x on page 4-22.
BSS software release GSR2 on page 4-34.
BSS software release GSR4.1 on page 4-42.
68P02901W01-S 4-1
Jul 2008
Feature Capacity Licensing and Audit Chapter 4: BSS Software Release Features
BSS software release GSR5.1 on page 4-52.
BSS software release GSR6 (Horizon II) on page 4-74.
BSS software release GSR9 FP1 on page 4-134
4-2 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release 1.1.1.0
BSS software release 1.1.1.0

Release 1.1.1.0 features
Table 4-1 summarizes the features of software release 1.1.1.0.
Table 4-1 Release 1.1.1.0 features
Feature Description
Teleservice 11 Compliant with GSM 02.03 for speech, data,
and signal transmission from the PSTN/ISDN.
Connectionless call processing Provides the functionality for dialogue
between the MSC and MS.
MTP Part of the MSC-BSS A interface. Supports
point-to-point signaling, compliant with
ITU-TSS SS7.
SCCP Part of the MSC-BSS A interface. Compliant
with ITU-TSS SS7 and ITU-TSS Q.711-Q.714
and GSM 08.06 para 5.2 - para 5.5.
BSSAP Part of the MSC-BSS A interface.
Comprises two distinct parts.
BSSMAP,
compliant with GSM 08.08 para 3.DTAP,
compliant with GSM 08.06.
RR status Sent by MS or network, can contain error
conditions (refer to GSM recommendation
4.08).
Multiplexing Compliant with GSM 05.02, supports logical
channels for full rate speech channels.
Layer 3 Specifies the procedures used at
the radio interface for call control,
mobility management, and radio resource
management.
Modified Abis (Mobis) Reduces 2 Mbps link traffic by increasing BSS
processing in the BTS.
MMI entry/response at local TTY Compliant with GSM 12.01, 12.06 allows
command entry and printing of responses
and alarm messages for the local network
element.
System change control administration Provides services for the management and
administration of configuration or data
changes.
Continued
68P02901W01-S 4-3
Jul 2008
Release 1.1.1.0 features Chapter 4: BSS Software Release Features
Table 4-1 Release 1.1.1.0 features (Continued)

Feature Description
Configuration management Allows operating versions of the hardware
and software components to be managed and
tracked.
Limited change control Provide in pre-op, compliant with GSM 12.06.
Local user validation Provides security management of user IDs.
Alarm and status reporting Reports alarms to the local TTY.
Cell capacities Set at 60 cells per BSS.
Database site capacities Can be BSC, BTS or BSC + BTS to a maximum
of 50 per BSC.
BSS capacities Set at 40 sites, 60 cells, and 75 RCUs per BSS.
Performance statistics Provides measurements to GSM
recommendation 12.04 and Motorola
unique measurements.
Collect limited stats Provides a variety of statistics actions using
MMI commands.
Minimal daisy chain Provides straight line open loop facility for
BTSs.
XCDR Allows configuration of remote XCDR.
16 k terrestrial circuits Supports terrestrial circuit for a remote XCDR
through existing MMI commands and CM.
Classmark update Call processing feature that allows the MS
to indicate a classmark change to the rest of
the network.
Dynamic timeslot reconfiguration Call processing feature that allows timeslots
to be reconfigured as requested.
Packaging page access grant messages Call processing feature that allows multiple
information transfer in one message.
Handover queuing Call processing feature allowing queuing
of messages during and internal handover.
Refer to GSM recommendation 8.08.
Resource allocation Call processing feature allowing the BSS to
notify the MSC of radio resources available on
request. Refer to GSM recommendation 8.08.
Call queuing Allows call queuing until resources are
available, subject to preset time constraints.
Refer to GSM recommendation 8.08.
Remove SCCP piggy backing Removes handover request from connection
request on SCCP.
Flexible ID format Allows variable length ID elements as defined
in the GSM recommendation 8.08.
Call tracing Initiates a call trace through a MMI command.
Continued
4-4 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.1.1.0 features

Feature Description
Fault recovery cleanup of affected calls Cleans up the BSC resources on restart of the
BTS, independent of the BSC.
Allocation of TDM resources Supports allocation of timeslots when a radio
carrier is added.
68P02901W01-S 4-5
Jul 2008
BSS software release 1.1.2.0 Chapter 4: BSS Software Release Features

This section describes about the BSS software release 1.1.2.0.
Table 4-2 summarizes the features of 1.1.2.0.
Table 4-2 Software release 1.1.2.0 features
Feature Description
BSS-OMC agent statistics reporting facility Statistics can be reported to the OMC based on
X.25 (without FTAM or CMISE).
Additional statistics provided A series of measurements as required by GSM
12.04, and some Motorola-unique measurements
are provided.
Collect and provide access to listed Provides additional functionality for statistics
statistics values through MMI commands.
BSC-OMC agent: Software reporting Reports software alarms to the OMC from the
BSC.
BSC-OMC agent: Hardware reporting Reports hardware alarms to the OMC from the
BSC.
Diversity option commands Turns On or Off the diversity option for a site
using a MMI command.
Support antenna diversity (BTS4-D) Modification to the BSS software to provide
support for BTS4-D.
Fault management Provides enhanced fault detection and
management.
Fault reporting to the OMC Collects alarms within the BSS and reports them
locally to the OMC.
Maximum system configuration Supports a database up to six MB in size.
MMI commands MMI commands are added or enhanced to
support the diversity option, XCDR maintenance
and BSS database control.
System commands System commands are added or enhanced to
support fault management and configuration
management.
Device management of a site Supports a number of implementation commands
for a site.
Continued
4-6 68P02901W01-S
Jul 2008
Table 4-2 Software release 1.1.2.0 features (Continued)

Feature Description
Device management of BSS devices Supports implementation commands for BSS
devices. Provides minimal fault isolation and
recovery.
Device management operations Supports a number of management operations
for implementation of devices.
68P02901W01-S 4-7
Jul 2008

Function Description
Handover algorithm - D1 Supports algorithm as specified in FEIN
specifications for Detecon (FS 05.08.1.1 (2.2),
Chapter 3.3.1).
Force OMC download of EEPROMs Forces an OMC download of GPROC flash
EEPROM manually.
Device management of BSS device (EAS) Supports implementation commands on the
EAS device PIX.
System commands Supports fault management and configuration
management.
4-8 68P02901W01-S
Jul 2008

Feature Description
BTS daisy chain with return loop The return loop feature, now known as a
closed loop, adds a closed loop capability for
open loop BTS configurations.
Signaling Point Inaccessible SPI implements the BSSMAP procedures for
signaling point inaccessible and user OOS.
Remote tuning combiner Allows combination of multiple RCUs.
Flash EEPROM Prevents accidental write to the flash
EEPROM. Provides a downloadable bootstrap
flash EEPROM for GPROCS.
EAS enhancements Includes optocoupler number and alarm text
in EAS optocoupler alarms sent to the OMC.
68P02901W01-S 4-9
Jul 2008

Feature Description
Advanced RCU download Reduces BTS outage time during BTS
initialization by improving overall DRI/RCU
download and configuration time. The
time reduction increases as the number of
DRI/RCUs increases at a site.
4-10 68P02901W01-S
Jul 2008

Feature Description
Baseband hopping Switches information generated by the channel
coding/interleaving function on the DRI to the
appropriate RCU.
Synthesizer hopping Re-tunes RCUs in real time from frequency to
frequency.
Data services full-rate traffic channels Supports data services on full-rate radio traffic
channels.
Support alternate speech and data Allows MSC/BSS co-ordinated switching between
speech and data using in-call modification
procedures.
GPROC device management Removes the need for BTS reinitialization when
RSL links to the BSC are interrupted.
Device management of GPROCs Ensure synchronization of the BSC and BTS call
processing after loss of all links or reinitialization.
Cross load time improvement Reduces the time to cross load between GPROCs
at a site.
Paging distributor optimization Ensures that only one message is sent to a BTS per
A interface paging message.
Short message service, point to point The BSS supports Short Message Service (MS
originated and MS terminated). Motorola is phase 1
compatible as the BSS responds to a SAPI n' clear
with a SAPI n' clear complete although the SAPI 3
connection is not torn down.
Simple flow control Provides BSS overload management by barring MS
access classes as necessary when call information
block usage reaches a predetermined threshold.
Intra-BTS synchronized handover Allows handovers that do not require the BSS
to send a physical information (timing advance)
message to the MSC.
LAN device management and swap over Provides management for the LAN hardware
devices and enables switching between the two
LAN hardware loops that interconnect all GPROCs
at a BSC or BTS site.
Continued
68P02901W01-S 4-11
Jul 2008

Feature Description
Remote BTS add and delete Provides an add and delete function allowing a BSC
to support an open or closed loop of BTSs.
Remote transcoder to BSC link (XBL) Notification of failed traffic circuits is sent from
the RXCDR to the BSC, and the BSC disables
these circuits by sending the appropriate blocking
messages to the MSC.
System audits processes The System Audits Processes (SAP) detects faulty
or degrading hardware and software (through the
use of audit tests) and notifies the alarms handling
software of the condition. The SAP does not take
any recovery or further diagnostics action due to a
fault. This is left up to the Fault Translation Process
(FTP) upon receipt of the alarm indication.
Audit control Provides SAP features using MMI commands at the
OMC or local MMI terminal.
Audits of soft devices Verifies correct operation of the software processes
within a GPROC.
Audits of boards Verifies correct operation of the hardware devices
within the BSS.
Audits of buses Verifies correct operation of the communication
buses within a BSS site.
Database notification The database notification feature ensures that
any operator-initiated change to data in the CM
database is distributed to all in-service GPROCs
and that the appropriate devices are notified of the
change.
Data categories Handles changes to type 2 and 3 data within the
CM database.
BSS/OMC periodic supervision of Enables periodic polling of the BSS from the OMC.
accessibility An alarm is generated if the BSS does not respond
correctly to the poll.
GCLK fault management This feature provides fault management of the
GCLK device, together with more complete GCLK
alarm information than was previously available.
Operator commands are also provided to control
which of the two GCLKs is active.
Save alarm status upon OML outage Allows the BSS to store alarms which is generated
within the BSS while OMC is inaccessible.
Alarm clearing and throttling Alarms reported by the BSS can be categorized as
either intermittent or constant. The alarm clearing
and throttling feature clears constant alarms
when the underlying fault is no longer present
and throttle intermittent alarms which repeat
frequently.
Continued
4-12 68P02901W01-S
Jul 2008

Feature Description
Multiple CCCH This feature allows multiple CCCH timeslots to exist
on successive even timeslots on the BCCH carrier.
RF queuing priority without preemption Positions information elements in priority order in
the waiting in queue if the queuing indicator is set
to Allow. The queue assignment request is rejected
if the queuing indicator is set to Not Allowed.
KSW expansion Up to four KSWs can be connected together to
support up to 4096 TDM timeslots at a site. The
BSS continues to support redundant KSWs. For
redundancy, a KSW is required for each KSW
required for capacity.
68P02901W01-S 4-13
Jul 2008

Table 4-7 summarizes the feature of 1.2.0.3.
Feature Description
Alarm and status synchronization The BSS supports future development of
the OMC alarm and status synchronization
feature within the OMC. Impacted
areas are Fault Management (CA
and FTP) and the OMC interface.
The alarm and state synchronization feature
provides a mechanism for synchronization
of the OMC and BSS/RXCDR device status.
Status information is composed of both alarm
and device state information. Normally, the
BSS/RXCDR sends alarms and device state
change events to the OMC as they occur, so
the OMC keeps up to date with changes to the
network element device status. However, a
mechanism for device status synchronization
is required both at OMC initialization time,
and after a failure of the OMC, BSS/RXCDR or
the links between them. Synchronization can
be initiated through operator request OMC
init, or it can be set up to occur automatically
at a configurable interval.
4-14 68P02901W01-S
Jul 2008

This section describes the features of software release 1.2.2.0.
Feature Description
Switchover improvement When a 2 Mbps link between a BSC and a remote BTS
fails, traffic is switched to a redundant 2 Mbps link if
one is available. The switchover improvement feature
reduces the time taken to switch links, thus minimizing
any break in voice or data transmission.
GCLK synchronization Ensures that air interface data timing and RF
frequencies remain within the GSM recommendations
and eliminates frame slips over the E1 interface.
Database level number The database level number feature keeps a database
level number for each site in the BSS. Database level
number increments are sent to a remote BTS only if
the database changes for that site. This feature helps
prevent unnecessary database downloads to remote
BTSs and also reduce the message traffic in the BSS.
BSC-BTS download compression This feature reduces the time taken by a BSC to
download the CM database to its BTSs. The BSC
compresses the information before downloading it,
and the BTS decompresses it on receipt. Checksum
procedures prevent data loss or corruption during
compression and decompression.
Preventative cyclic retransmission Preventive Cyclic Retransmission (PCR) involves the
retention of a signal unit at the transmitting terminal
until Acknowledgment is received from the receiving
terminal. During the period when there are no new
signal units to be transmitted, the transmitting terminal
cyclically retransmits all the signal units that have not
yet been acknowledged by the receiving terminal.
Multiple digital host processor The multiple DHP cage feature allows more than one
DHP per cage.
Timeslot reservation This feature allows ranges of timeslots on specified 2
Mbps links to be barred from use by a BSS (reserved)
using a MMI option or the OMC.
Continued
68P02901W01-S 4-15
Jul 2008

Feature Description
Internal alarm system Monitors the status of the Power Distribution Unit
(PDU) in a BTS and generates an alarm in the event
of a fault. The feature also provides for any alarms
detected by the Digital Power Supply Modules (DPSMs)
in a cage to be reported.
4-16 68P02901W01-S
Jul 2008

Feature Description
TopCell alarm enhancement The BSS software supports the additional
alarms that are generated for each TopCell
cabinet.
TopCell base The BSS software supports the new TopCell
hardware. The TopCell product is a complete
cell site (BTS).
TopCell requirements Defines the new requirements for a TopCell
site.
Six carrier BTS shelf The BSS supports a six carrier BTS shelf for
DRCU3.
ExCell 6 The BSS supports a six carrier version of the
ExCell product.
68P02901W01-S 4-17
Jul 2008

Reason for this release
Release 1.2.2.3 addresses an internal problem that could pose a potential risk to customers with
medium to large configurations. This release supersedes release 1.2.2.2 and should be used
instead of release 1.2.2.2.
4-18 68P02901W01-S
Jul 2008

Important information
GSM BSS 1.2.3.0 is released on a limited basis to support DCS1800 First Office Application
(FOA). The extent of functionality supported by this release is limited to basic cellular phone
service. The following feature functionality is excluded until sufficient testing has been
accomplished to release these features for use in the DCS1800 environment.
Feature Description
Excluded features The following features are excluded from
this release: 1800 MHz Remote Tuned
Combiner (RTC). DTX (Discontinuous
Transmission). Short Message Service
(SMS) point to point. Short Message Service
(SMS) cell broadcast single background
message. Data services alternate speech;
data services full rate. Frequency hopping,
baseband; frequency hopping, synthesizer.
A BSS operating with BSGSM 1.2.3.0 in
GSM900 mode has not been qualified to
operate with another BSS in DCS1800
mode, while both the BSSs are connected
to the same OMC. It is recommended that
all BSS connected to a single OMC remain
homogenous with respect to the radio
spectrum they serve.
Fault isolation (enhanced) This feature provides enhancements to
existing fault isolation capabilities for the DRI
and GPROC devices.
Continued
68P02901W01-S 4-19
Jul 2008

Feature Description
Short message service, cell broadcast (single This feature is a means of unilaterally
background message) transmitting data to mobiles on a per cell
basis, by use of a Cell Broadcast CHannel
(CBCH). This feature provides a subset of
the full GSM functionality. In particular, the
BSC interface to the CBC is not supported.
Instead, a single operator defined message
is entered using appropriate MMI command.
The full functionality as defined by GSM is
implemented in a later release.
Real time traffic monitoring This feature enhances the BSS and OMC to
allow real time traffic display of channels
in use on both the A interface (terrestrial
circuits) and the air interface (radio channels).
Display of hardware revision level from MMI Operators use this feature to obtain the
hardware version number of certain boards,
using a MMI command. Alarms are reported
with the hardware version number of the
board originating the alarm, if the alarm
originates from either a GCLK, GPROC, DHP,
BSP, BTP, KSW, MSI, XCDR or DRI.
RCU ID MMI feature Operators use this feature to display the
serial number of any RCU/DRCU, and the
hardware version number of its component
boards. RCU/DRCU alarms are correlated to
a specific RCU/DRCU, using the RCU/DRCU
serial number.
BTS battery conservation at main power This feature enhances BTS battery back up
failure operation by selectively stopping RCUs from
transmitting, so that power is conserved. This
extends the available BTS battery time.
TopCell Alarm Enhancement The BSS software supports the additional
alarms that are generated for each TopCell
cabinet as follows: Door open alarm, PSU
failure alarm, and Main power failure alarm.
DCS1800 frequencies This feature provides the software support
for the new RF hardware being developed to
operate in the 1800 MHz frequency band.
Update of LAN microcode Due to a change in the TMS380C26 LAN
adapter device on the GPROC board, this
release contains an update of the vendor
provided microcode for the device.
Six carrier BTS shelf The BSS supports a 6 carrier BTS shelf for
DRCU3.
ExCells The BSS supports a 6 carrier version of the
ExCell product.
Continued
4-20 68P02901W01-S
Jul 2008

Feature Description
Preventative Cyclic Retransmission on The BSS supports Preventative Cyclic
C7-MTP MSC-BSC A interface Retransmission (PCR) error correction for
connecting to the MSC (the A interface)
through a satellite link.
TopCell base The BSS software supports the new
TopCell hardware, incorporating DCS1800
components. The TopCell product is a
complete cell site (BTS).
TopCell requirements Defines the new requirements for a TopCell
site.
68P02901W01-S 4-21
Jul 2008
BSS software release 1.3.0.x Chapter 4: BSS Software Release Features
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 upgrading from
release 1.2.2.3.
Table 4-11 summarizes the features of software release 1.3.0.x.
Table 4-11 Release 1.3.0.x features
Feature Description
Large BSS configuration capacity This feature introduces capacity support for a
system consisting of 50 sites, 90 cells, and 90
active RCUs (TRXs).
Fault isolation (enhanced) DRI and GPROC This feature provides enhancements to
existing fault isolation capabilities for the DRI
and GPROC devices.
KSW, TDM, and TBUS management Provides control for configuration of the listed
devices and allows switching between TDMs
without re-booting the system.
Manage inactive GPROCS This feature enhances the Operation and
Maintenance of GPROC devices.
BSC LCF swaps Allows switching of logical links to the MPT
layer 2 physical links if an MTL GPROC fails
during transmission.
BSC OMF The BSS provides the capability to handle
the OMF function (OMF GPROC) failures
independently without impacting the
remaining GPROCs at the BSS site. This
capability does not prevent an interruption to
call processing service.
BTS DHP swaps Shifts functionality of the RF carrier from a
failed DHP to a healthy device, thus limiting
the effect of the failed DHP recovery to a
subset of the carriers at the BSS/BTS site. All
carriers on the failed DHP are disabled and
re-enabled on other surviving DHPs/BTP/BTF
within the same cage, if there is available
capacity.
BSC BTF swaps Allows BTF swapping to ensure no loss of
function resources if a GPROC fails.
Continued
4-22 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.3.0.x features
Table 4-11 Release 1.3.0.x features (Continued)

Feature Description
Code storage facility processor The Code Storage Facility Processor (CSFP)
supports propagation of new software
instances with reduced system downtime.
Optional CSFP fall back is also provided.
Encryption algorithm, A5/2 or Null The BSS supports basic encryption operation
using the A5/2 and Null encryption algorithms.
Encryption provides security for user speech,
data, and signaling information at the physical
layer. Encryption and decryption must be
deployed at both the BSS and MS.
Multiple versions of A5 algorithm The BSS supports the parallel operation of
A5/1, A5/2, and Null encryption algorithms.
The operator is able to set the priority/order
in which the BSS chooses the algorithms. This
order can be set at sysgen time or through
MMI command.
Restrict optional feature The BSS restricts use of optional features
unless purchased by the customer.
Short message service, cell broadcast (single Defines the operator controlled, Short
background message) Message Service, Cell Broadcast (SMS CB)
feature, which is a means of unilaterally
transmitting data to mobiles on a per cell
basis, by use of a Cell Broadcast CHannel
(CBCH).
Emergency call preemption Allows emergency calls to preempt all other
calls, even if system resources are utilized.
GSM phase 2 air interface/A interface Delivers part of an operating system upgrade,
or overall application package, for BSS
support of GSM phase 2 compliant messaging
over the A and air interfaces.
BSS signaling Provides BSS signaling compatibility
with phase 2 GSM, EGSM, and DCS1800
systems. Also maintains phase 1 GSM system
compatibility.
Phase 2 compliant network entities Supports both phase 1 and 2 GSM mobiles
over the network.
Dynamic extended paging Allows dynamic extended paging to be
enabled through MMI commands. Also
allows automatic dynamic extended paging in
overload conditions.
Display of hardware revision level Allows display of version numbers or serial
numbers of hardware components.
Continued
68P02901W01-S 4-23
Jul 2008
Release 1.3.0.x features Chapter 4: BSS Software Release Features
Table 4-11 Release 1.3.0.x features (Continued)

Feature Description
BTS battery conservation after main power This feature enhances current BTS battery
failure back up operation by automatically stopping
RCUs from transmitting, so that power is
conserved. This extends the available BTS
battery time. The non-BCCH carriers are
disabled before the BCCH carriers using an
algorithm in fault management the extent of
which is controlled by MMI.
DCS1800 frequencies Supports the signaling required to operate in
the DCS1800 frequency bands.
DCS1800 hardware Supports the RF hardware required to
operate in the DCS1800 frequency bands.
MSI-2/T1 signaling support for PCS1900 This feature introduces support for PCS1900
configurations. The BSS will have the
functional capability to operate as both
GSM900 and PCS1900 configurations.
Preventative cyclic retransmission The BSS supports Preventative Cyclic
Retransmission (PCR) error correction for
connecting to the MSC (the A interface)
through a satellite link.
Network configuration management This feature provides the mechanism(s) to
support configuration management from
the OMC using a management interface to
the BSS. Also includes support of alarm and
status synchronization.
Dual OML download The redundant OML link supports load
sharing for downloading from the OMC
provided the BSS default requirements are
met.
Real time traffic channel monitoring This feature enhances the BSS and OMC, to
allow real time traffic display of channels
in use on both the A interface (terrestrial
circuits) and air interface (radio channels).
Transcoder download link volume control This feature provides for an audio uplink and
downlink volume control offset on a per BSS
basis.
4-24 68P02901W01-S
Jul 2008

Feature Description
GCLK synchronization This is a standard 1.4.0.0 feature which
enables any current generation SITE to be
configured so that it can synchronize its GCLK
to a known good clock source in an uplink
SITE through an E1 link.
68P02901W01-S 4-25
Jul 2008

Table 4-13 Release1.4.0.1 features
Parameter Description
Preserve RCU/SITE calibration Enables all types or versions of a
malfunctioning radio channel unit to be
replaced without the need to remove the Cell
from service, in Cell configurations with two
or more radio channel units.
Indication of flow control invocation Provides a new Cell level statistic,
FLOW_CONTROL_BARRED, which measures
the duration for which channel access to the
cell is unavailable to any access class.
GSM short message service The Motorola BSS supports GSM Short
Message Service - Cell Broadcast (SMS CB).
Mobile subscribers with access to the
short message service are able to receive
alphanumeric information messages at any
time while their Mobile Station (MS) is in
contact with a BSS.
SMS - Cell broadcast: multiple background Enables the BSS to support the SMS Cell
messages broadcast directly for single or multiple (up
to four) alphanumeric information messages
to be sent to any suitably configured MS.
SMS - Cell broadcast center support Supports the use of a third-party SMS Cell
Broadcast Center (CBC) on the Motorola
GSM network. The BSS database and MMI
commands have been modified to support this
feature.
Added nailed connections (optional) Enables non-GSM connections used by
third-party services, such as, a paging
network or analog mobile phone network, to
share the use of the E1 link through a BSS
without the need for external multiplexing
equipment. The existing Timeslot reservation
feature is modified to enable the reserving of
timeslots on E1 link. The RESERVE operation
is currently allowed for MMSs on a PATH only.
Continued
4-26 68P02901W01-S
Jul 2008
Table 4-13 Release1.4.0.1 features (Continued)

Parameter Description
Remote network device lock/unlock Enables BSS device administration to
perform by an OMC operator through
the OMC GUI when carrying out Fault
Management (FM) and Configuration
Management (CM) procedures. A device
operational/administrative state report is
possible from a new window, Contained
Devices for selected node, which can be
selected for any BSS, RXCDR, or SITE on
either the network maps or the navigation
tree at the OMC GUI. Also reduces the need
for a OMC - BSS remote login to perform
either FM activities or for Configuration
Management activities.
68P02901W01-S 4-27
Jul 2008

This section describes the features of software release 1.4.0.6.
Software support of M-Cell2/6 GSM for 900 This feature introduces BSS software support
MHz of the core M-Cell hardware, plus MCU, NIU
and TCU support.
Software support of M-Cell2/6 GSM for 1800 This feature introduces support of DCS1800
MHz with both the M-Cell2 and M-Cell6 BTS
hardware platforms.
M-Cell EGSM This feature introduces an EGSM-capable
Transceiver Control Unit (TCU) at 900 MHz.
A TCU combines the Radio Subsystem, DRI,
and DRCU functions into a single package.
TCU backwards compatibility Enables older generation BTSs to operate the
current TCU.
RSS functionality port to carrier equipment This feature provides for the porting of RSS
(TCU) M-Cell and DRI functions to the Transceiver Station
Manager (TSM) board, which resides in the
TCU.
Recovery escalation (M-Cell) A new soft_reset command is available for
M-Cell BTS SITEs only. A soft reset is defined
as a reset where no equipment requires a
code load and the reset switch of no piece
of equipment has been tripped. No object
comparisons or checksums are done at a soft
reset. This fulfils the requirements of the
Recovery escalation (Roadmap ID 31240)
feature.
M-Cell6 remote tuner combiner (900 MHz This feature comprises BSS software support
only) of a Remote Tuning Combiner (RTC) for an
M-Cell6 at 900 MHz only.
M-Cell6 receive matrix (900 MHz only) This feature introduces an Extended GSM
(EGSM)-capable receiver RF matrix, which
supports up to six carriers in a single cabinet.
Continued
4-28 68P02901W01-S
Jul 2008

BSC CSFP redundancy This feature provides for BSS software
support for equipping two Code Storage
Facility Processors (CSFPs) at the BSC to
provide redundancy.
M-Cell hardware impact on BSU-BTS This requirement provides for BSC support of
the new M-Cell hardware with no degradation
in service at the BSC, except for outages
necessary for interconnection purposes.
68P02901W01-S 4-29
Jul 2008

Feature Description
M-Cellmicro GSM900 Software support for the M-Cellmicro site for
GSM900 operation is provided in this release.
Low power DCS1800 BTS-site M-Cellmicro Software support for the M-Cellmicro site for
DCS1800 operation is provided in this release.
DCS1800 mast mounted preamplifiers An independently powered mast mounted
preamplifier for DCS1800 only. The
preamplifier is manually configured on-site.
Preamplifier power failure and device failure
are reported through a single EAS alarm.
Optional filtering for front end This feature is a receive bandpass filter with
a narrow specification specifically designed
for when ETACS frequency spectrum is used
in conjuncture with a GSM network.
4-30 68P02901W01-S
Jul 2008

Feature Description
Transient alarm handling Enables the BSS software to perform more
verification and filtering of fault indications,
to eliminate transient alarm messages from
the Transcoder TRAU, the RSL, XBL and clock
failures. The main impact of this feature
is that it decreases the number of alarms
reported by the BSS. This results in less alarm
handling required at the OMC.
Multiple trigger call trace events Enhances existing Call Trace functionality by
providing a finer trigger scope for call trace.
This feature allows triggers to be set on a
Cell level and multiple Cell level. All current
triggering capability is supported on a per
Cell or per BSS level.
BSS level trace events - RF failure (RF loss) Enhances existing RF failure trace
functionality by providing the option to
enable RF loss reporting on a per cell basis
(previously it was BSS level). It also provides
the facility to forward the RF failure trace
information through the event interface to
the OMC.
MSI-2 board with E1 MSI-2 boards can be ordered with E1
interconnections. The software support at the
BSS and OMC is already available to support
this.
Direct retry Redirects new traffic when a Cell is congested
resulting in the new call being moved to the
next most suitable cell.
Congestion relief: directed retry alternative An alternative to Directed Retry for the case
of a congested cell. This feature differs in
that it chooses the best candidates from
all existing calls in the cell to be moved to
the alternate cell, thus freeing TCHs in the
congested cell.
Continued
68P02901W01-S 4-31
Jul 2008

Feature Description
Satellite A interface support (optional) Provides the BSS software support
transmission of the A interface through
satellite.
Satellite Abis support (optional) Provides the BSS software support
transmission of the Abis interface through
satellite.
Optional level 3 password Provides the facility for the BSS MMI security
level three password to be controlled by the
OMC operator.
All channels at full power Sets all the call channels in the Cell to
broadcast at a constant power, the power
level configured as the maximum transmit
power allowed in the Cell. This can be used
for worst case interference monitoring for
network optimization.
Fast initial MS power down (optional) Allows the initial power down of the Mobile
Station (MS) to be set so that the MS power
is reduced quicker than the standard ramp
down time. When this feature is enabled a
separate power control procedure powers the
MS down rapidly when the BSS detects that
the signal strength of the MS is above the
specified trigger threshold.
Concentric cells (optional) Used in GSM networks with constrained
frequency allocations, to increase network
capacity by adding a layer of Cells (known as
mini cells) on top of the existing network.
Cell level call trace events Enhances existing call trace functionality by
providing the option to forward call trace
information to the OMC-R. This information
takes the form of new event messages, which
the OMC-R then stores, as an alternative
to or in addition to sending it to the MMI.
Once sent to the OMC-R, the call trace data
is stored in a log file.
Link balance verification statistics The Link balance verification statistics
feature will identify those carriers which
have unbalanced uplink and downlink signal
strengths. This feature supports optimization
activities.
Handover performance statistics Provides a package of enhanced handover
enhancements performance statistics which reduce network
optimization effort and time.
Continued
4-32 68P02901W01-S
Jul 2008

Feature Description
15,000 TCH support - 1475 platform Provides support for 15,000 traffic channels in
networks where the OMC-R is deployed with
a Tandem Integrity 1475 system processor.
Existing OMC-R systems deployed with
Tandem Integrity S300 system processors will
continue to support 10,000 traffic.
Enhanced GSM 12.04 statistics compliance Enhanced GSM 12.04 statistics compliance
feature, ensures that the compliance of
statistics to the GSM 12.04 recommendations
are improved, with additional OMC-R Key
Statistics reports and a package of additional
BSS statistics.
M-Cell2/6 MCU redundancy (phase 1) Provides the information required to install
an M-Cell site to optimize MCU redundancy.
Phase/frequency lock (phase 1) Provides enhancements to the 1.4.0.x feature,
Generic CLocK (GCLK) synchronization.
Synch boot Sync boot is a 1.4.1.1 feature which provides
enhancements to the 1.4.0.x feature, M-Cell
series software support.
68P02901W01-S 4-33
Jul 2008
BSS software release GSR2 Chapter 4: BSS Software Release Features
BSS software release GSR2

GSR2 features
Table 4-17 summarizes the features provided in the BSGSM-GSR2 release with OMC/BSS
software support.
Table 4-17 Release GSR2 features
Feature Description
GPROC2 Supports the introduction of the GPROC2.
Because of the increased reliability of the
GPROC2 board, there is a decrease in the BSS
unavailability due to unplanned outages. The
error correcting RAM on the GPROC2 board
provides increased reliability.
Cell level/carrier level tracing Enhances the existing Call Trace capabilities
available in the BSS.
Call trace through IMSI Allows a Mobile Station (MS) to be tracked as
it moves across the network.
DCS1800 RTC Supports the DCS1800 M-Cell CCB (Cavity
Combining Block) at M-Cell sites. As a result,
the BSS software is required to modify the
management of remote tuned combiners at
an M-Cell site.
Transcoder Online Expansion Allows the transcoder capacity of equipped
transcoder cards to be increased while online.
The BSS remains available while the equipped
hardware is increased and configured.
This eliminates any site outages during the
expansion.
Type 7 Microcellular Neighbor Cell Adds a Type 7 Microcellular neighbor 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.
Continued
4-34 68P02901W01-S
Jul 2008
System Information: GSM Overview GSR2 features
Table 4-17 Release GSR2 features (Continued)

Feature Description
Enhanced Frequency Hopping Enhances the operability of the existing
hopping feature by introducing the following
enhancements:
Hopping timeslots is locked and

unlocked.
Carriers or timeslots is specified as

hopping or non-hopping when brought
into service.
When a carrier or timeslot is unlocked, it

is brought back into service as hopping
or non-hopping based on the database
configuration.
Only the affected site has to be reset

for changes to frequency hopping
parameter to be effective.
Configurable X.25 for BSS Allow the OML and CBL links to have
configurable X.25 layer 3 packet sizes and
window sizes. This feature provides MMI
commands and OMC interface support for
modification and viewing of these parameters.
Satellite XBL Interface (optional) Provides the BSS software support for
transmission of the XBL link through satellite.
Satellite OML Interface (optional) Provides the BSS software support for
transmission of the OML link through
satellite.
Online Add/Copy/Delete Cell BSS Command Supports the online modification to the Cell
configuration of the SITEs within a BSS, while
Cellular service is maintained to subscribers.
CM Service Statistic Break-out Provides call success statistics that more
closely match MSC statistics. Call success
criteria depend upon the service requested.
Upgraded Remote Tuning Combiner at 900 Provides an adaption kit to enable the new
MHz M-Cell Remote Tuning Combiner, known as
CCB, to be retrofitted to BTS4 and BTS6
systems.
68P02901W01-S 4-35
Jul 2008

GSR3 features
Table 4-18 summarizes the features are provided in the BSGSM-GSR3 release with OMC/BSS
software support.
Feature Description
Concentric Cells Allows the RF resource allocation for a cell to
consist of two frequency channel groups with
a single BCCH frequency to operate in the
same coverage area.
Support for Extended Range Cell Allows the BTS to handle successfully the
uplink transmissions of an MS whose absolute
timing advance exceeds 63-bit periods.
16 kbps XBL Eliminates the requirement for a full E1
timeslot for each XBL.
Non-redundant RTF-PATH Fault Containment Allows a cell to be available for calls even
when all of the paths on which an RTF is
equipped fails, provided there is another
in-service RTF-PATH available for the cell.
Traffic capacity can be increased by removing
any redundant RTF-PATHs and using this
feature to manage RTF-PATH failures. This
also results in a cell not being barred ifthere
is at least one in-service RTF-PATH available
for the cell.
PCS1900 MHz Band (M-Cell2/6) Supports the PCS1900 GSM band 8 Watt
(after first stage of combining) product on
both the M-Cell2 and M-Cell6 BTS hardware
platforms. No remote tuning combining is
supported. This feature is for M-Cell2/6 only
and supports all GSM900/DCS1800 features
except multiband.
Infrastructure Sharing Supports cells of different frequency bands in
a single BTS-site. This feature also supports
the conversion of single band BTS-BTUs and
BCU-BTSs to multiband BTS-sites.
16 kbps RSL for Preserving Timeslots Supports an interface between the BSC and
the BTS-site using a 16 kbps LAPD and the
Motorola proprietary signaling.
Continued
4-36 68P02901W01-S
Jul 2008

Feature Description
Circuit Error Rate Monitor Provides the means for identifying when
discontinuity is detected on a circuit path.
The term circuit path refers to the network
communication path from the transcoder
(XCDR) to the BTS established during a call.
Adjustable Downlink Audio Volume Control Provides the firmware support for adjustable
downlink audio volume control in four steps
of 2 dB each at the transcoder.
GDP Support of Dual Rate, Full Rate, and Supports the transcoding functions for full
Enhanced Full Rate rate, Enhanced Full Rate (EFR) and half
rate. The GDP board is one of the required
components of the EFR feature, which
provides better overall speech quality than
full rate.
Enhanced Full Rate Vocoder Implements the GSM defined Enhanced Full
Rate (EFR) for speech. EFR provides a speech
service that has better voice quality than
normal full rate speech service.
MultiBand Inter-Cell handover The BSS supports inter-cell handover where
cells are operating in different frequency
bands. In addition, the network operator
can deploy cells of differing frequency bands
within the same BTS-Site(s). For example, a
single BTS-Site can support combination of
the DCS1800, PCS1900 and GSM900 cells.
OMC and DataGen common GUI Provides BSS support for a common OMC and
DataGen GUI.
GPROC2 removes CSFP requirement Provides the software support required
to reallocate M-Cell specific objects from
the BSC CSFP GPROCs to the BSPs which
are GPROC2 boards. This removes the
requirement of having a CSFP GPROC at the
BSC to support M-Cell BTS sites.
Increased capacity with GPROC2 as LCF Allows a single GPROC2 serving as a LCF
to support 2 MTLs and 15 active BTS-sites.
A new database parameter indicating the
number of links supported on a GPROC2 is
created.
MS handover power level based on path loss Sets the MS power level on an inter-cell
calculations intra-BSS handover to the target cell based on
path loss calculations for promoting battery
conservation.
SACCH on a channel basis Provides BSS support for SACCH system
information on a channel basis.
Continued
68P02901W01-S 4-37
Jul 2008
GSR3 features Chapter 4: BSS Software Release Features

Feature Description
RTF Subequipping Supports the unequipping of the RTF to
reduce the number of E1 timeslots required
for a site. An unequipped RTF utilizes a single
64 kbps timeslot on an E1 link.
Prefer Different Carrier for Intra-cell Permits a different carrier to be used for
handover an intra-cell handover when the uplink
interference level is the same.
Micro-micro quality handovers Calls which experience a quality condition in a
microcell is handed over to another microcell
when possible.
Timed offset upon RXQUAL handovers Adds a new timer that is set up to provide
an additional margin to the handover margin
to prevent a handover to a cell with a lower
power budget.
Time limitation for excessive intra-cell The number of intra-cell channel changes due
handover to interference can be limited, by performing
an inter-cell handover when the threshold has
been reached.
Remaining 12.04 Statistics (less 3) Adds a number of raw statistics that are
generated at the BSS to more closely meet
the 12.04 GSM Specifications. In addition, a
number of counter type statistics have been
changed to counter array statistics permitting
easier identification and analysis of events on
a cause or scenario basis.
DRIM/RCU FW Alarm Translation Optimizes the handling of DRIM/RCU
Adjustments firmware generated alarms. This prevents
spurious alarms being reported to the
operator. The Hard Reset alarm was
previously used to indicate a reset of the DRI
due to a recurring fault in addition to an
actual hard reset. Now a new DRI alarm (35)
has been added to identify this reset reason
uniquely. DRI 35 is Reset due to recurring
fault.
Intra-cell Handover Ping Pong Protection Provides a configurable time interval to
reduce ping pong effects. This permits
increased handover margins that is applied to
the original cell which discourage handing a
call back.
Enhanced full rate vocoder transcoder Provides firmware support for the GSM
Phase 2+ enhanced full rate vocoder (codec)
transcoding.
Concentric cells (interference based cell Provides an interference based algorithm
resource partitioning) which defines the coverage area of the inner
zone for concentric cell structures.
Continued
4-38 68P02901W01-S
Jul 2008

Feature Description
Handover margin per handover cause for Provides two new neighbor parameters to be
candidate ranking used in the handover decision process in the
case where the handover was due to RXQUAL
or RXLEV. These parameters are used to
order candidates based on a calculated value.
This feature only applies to microcells.
Increase BSC capacity with introduction of Provides BSS support for up to 40 BTS sites,
GPROC2 126 cells, 255 carriers, and 1680 trunks.
High power DCS1800 with increased The result of the receiver sensitivity increase
sensitivity receiver matrix is restriction of a single cell in a single
cabinet.
Enable Hopping with no Site Reset Allows frequency hopping parameters is
modified without resetting the site and
normal synthesizer and baseband hopping
to be enabled at different cells in the same
site using synthesizer frequency hopping
enhancement. A site reset does not occur
when a FHI is enabled or disabled.
Aggregate Abis Provides support for third-party switching
equipment between a BSC and BTSs.
Additional flexibility in the allocation of E1
timeslots at the BSC and BTSs is provided
to support the use of a switching network
to combine the timeslots from several low
capacity BTSs onto a single E1 link to the
BSC.
New Millennium Provides Year 2000 compatibility for the BSS.
PCS1900 mast mounted preamplifiers Supports an independently powered masthead
preamplifier supported for PCS1900.
Accelerated Handover to Inner Concentric Provides a mechanism that accelerates
Cell Zone handovers to the inner concentric cell
zone for cells using the interference-based
algorithm.
68P02901W01-S 4-39
Jul 2008

GSR4 features
Table 4-19 summarizes the hardware/software features provided in the BSGSM-GSR4 release
with OMC/BSS software support.
Feature Description
Call trace expansion Provides enhanced operator features through
the OMC GUI for call tracing.
Carrier prioritization for SDCCH Provides the operator with the flexibility of
prioritizing the selection of Traffic Channels
(TCHs) and Standalone Dedicated Control
Channels (SDCCHs) in order to minimize the
overall interference level in a GSM network.
SMS alphabet extensions Adds three new alphabets to the list of default
alphabets supported by the Short Message
Service feature.
BTS concentration Provides the customer with an alternative
mechanism for allocating terrestrial backhaul
for radio resources between the BSC and
the BTS. This feature preserves the existing
mechanism, but allows the operator the
choice, on a per BTS site basis, of whether
to use the existing mechanism, or the new
dynamic allocation.
M-Cell HDSL interface Introduces a High bit-rate Digital Subscriber
Line (HDSL) interface into the Motorola BSS
product line. HDSL is a data transmission
mechanism which supports duplex high speed
digital communication (at E1 rates) on one or
more unshielded twisted pair lines.
Increased BSC capacity Expands the capacity of a BSC, must be
GPROC2s for all functions at a BSC.
Terrestrial circuit device management Allows the customer to manage terrestrial
circuits in much the same way as other
devices.
Optimized power control Improves uplink and downlink power control.
This is done by adding flexibility in defined
power steps, modifying the range of power
steps, by allowing power step sizes to be
changed dynamically, and by performing
downlink oscillation prevention.
Continued
4-40 68P02901W01-S
Jul 2008

Feature Description
Frequency hopping Enables each timeslot to use a set of
frequencies defined in one of up to four
frequency hopping systems.
New Millennium Addresses all aspects of the Motorola system;
OMC-R, BSS, and the BTS and BSC hardware.
It concerns itself with internal clock operation
and the use of the date in various parts of the
product, for example, within the Event and
Alarm reports.
Enhanced congestion relief Enhances the effectiveness of the congestion
relief features which are already in place,
having been delivered by the 1.4.1.0
implementation of the congestion relief -
directed retry alternative feature as well as
enhancement PRs to GSR2 and GSR3.
GPROC2 required for all BSC processors With the GSR4 software release, all GPROCs
at the BSC must be GPROC2s.
BCCH frequency, SDCCH in EGSM Allows the configuration of BCCH carriers
and the placement of SDCCH channels in the
EGSM frequency band based on an operator
defined database parameter. It provides
the capability for the operator to configure
a stand alone EGSM cell and enables the
operator to implement a multiband/dualband
network with EGSM as one of the supported
frequency bands, for example, DCS1800 and
EGSM.
Flexible neighbor handling Enhances the existing handover decision
process by adding more flexibility in the way
neighbor cell processing is carried out for
handovers.
Coincident multiband handover Enables operators to install new radios in a
different frequency band. This installation
turns a customer's network into a multiband
network.
Second assignment Allows a second attempt to assign a Traffic
Channel (TCH) to the MS if the first TCH
assignment attempt fails.
The OMC provides the appropriate information to remind the operator that the BSC must be all
GPROC2 boards, before a conventional or CSFP download of release GSR4.
68P02901W01-S 4-41
Jul 2008
BSS software release GSR4.1 Chapter 4: BSS Software Release Features
BSS software release GSR4.1

GSR4.1 features
Table 4-20 summarizes the hardware features provided in the BSGSM-GSR4.1 release with
OMC/BSS software support.
Table 4-20 Release GSR4.1 features
Feature Description
Point-to-point GPRS service. Supports implementation of one to eight
timeslots on a single carrier per cell for the
transmission of GPRS traffic. This enables
the Network Operator to optimally size the
network for efficient support of a mix of GPRS
and voice traffic.
GPRS radio channel allocation. Provides the flexibility for a cell supporting
GPRS to allocate a given radio resource to
handle circuit switched voice/data or packet
data as required. A radio resource can be
configured as dedicated to circuit switched
traffic, packet data traffic, or switchable
between the two.
Medium Access Control modes: fixed/dynamic Includes the functions related to the
allocation. management of the common transmission
resources. These include the packet
data physical channels and the radio link
connections on packet data physical channels.
Support of MS classes. Supports multislot MS classes 1-12, 19 and
20. This includes support of both semi-duplex
(classes 1-12) and half-duplex (classes 19 and
20). Semi-duplex MSs can support up to 4
TimeSlot (TS) downlink and 1 TS uplink, or
2 TS downlink and 2 TS uplink. Half-duplex
MSs, can support 6 TS downlink or 2 TS
uplink, or 1 TS downlink and 4 TS uplink
(fixed allocation MAC mode).
GPRS codes schemes CS-1 and CS-2. Coding schemes CS-1 and CS-2, providing
9.05 kbps, and 13.4 kbps respectively, are
supported.
Dynamic adaption of coding schemes. Enables the network to change the coding
scheme between MS transmissions based
upon the radio characteristics of the link.
Movement between CS-1 and CS-2 is
supported in the initial GPRS release.
Continued
4-42 68P02901W01-S
Jul 2008
System Information: GSM Overview GSR4.1 features
Table 4-20 Release GSR4.1 features (Continued)

Feature Description
Two phases packet access. Allows an exchange of information to take
place between the MS and the network before
assignment of resources.
Frequency hopping of PDCH. Supports frequency hopping of the packet
data channel (PDCH).
Power control: uplink/downlink. Enables power adjustment over the radio
link based upon the characteristics of the
link. Power control is supported over the
radio interface on both the uplink and
downlink. Power adjustments are directed
by the network based upon the measured
characteristics of the radio link.
Gb interface. Provides connection between the BSS and
the SGSN.
PCU load balancing and sharing (Gb and Provides high reliability through efficient
BTS). resource management. It also manages the
movement of resources from one part of a
BSS to another to meet varying peak capacity
requirements in a network designed primarily
for coverage.
68P02901W01-S 4-43
Jul 2008

GSR5 features
Table 4-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 immune design
Propagate TSC changes to all timeslots
Single BCCH for dual band cells
Support for E1 conversion
Enhanced Power Outage Recovery
Improved MTL load balancing
BTS concentration resource optimization for handovers
Handover parameter
Per neighbor 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 preemption
Parallel cage enable
Enhanced MMI Link Device Warnings
4-44 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS overload protection
BSS overload protection
The MSC Overload control feature introduces a mechanism for temporarily reducing traffic
between the MSC and the BSS. This mechanism allows the MSC to notify the BSS that it is
becoming overloaded and the amount of information being sent to the MSC from the BSS should
start to reduce. The BSS receives the notification and starts to reduce the traffic loading on
the MSC immediately. The BSS reduces the traffic load on the MSC by barring mobile access
classes within cells in the BSS. A timer controls the unbarring of the access classes to increase
the traffic to the MSC.
SMS CB upgrade
The short message service (SMS) cell broadcast (CB) attracts subscribers to the network by
broadcasting information of interest to the general public, for example, road conditions, traffic
information, news flashes, weather reports, and so on.
The SMS CB upgrade feature integrates changes made to the ETSI GSM standards and
recommendations since the initial development of the SMS CB features, and provides support
for large SMS CB messages.
The main system changes are:

Multiple page message support. The initial implementation limited the number of pages in
a WRITE/REPLACE to 1.
Different message categories. Message categories have been introduced. These categories
are defined as High Priority, Background, or Normal. The introduction of different priority
messages affects the scheduling of both the message itself and the DRX scheduling
messages. A new message is supported from the CBC which reserves certain slots for
potential High Priority messages.
CBC configurable DRX period. A configurable DRX message has been introduced. The
DRX message is turned on and off through messages from the CBC. In addition, the CBC
sets the period of the DRX message.
CBC-BSC interface upgrade. The definition of the Repetition-rate parameter has changed.
Support of extended SMS alphabets. ETSI 03.38 provides definitions of the extended
alphabets which can be used for SMS cell broadcast messages. Extended SMS alphabets
defined by the CBC are supported for messages. The extended SMS alphabet is not
supported for SMS cell broadcast messages which are defined through the OMC/customer
MMI.
Backward compatibility. CBC vendor is working to different versions of GSM specifications

03.41 and 03.49. A mechanism has been introduced which allows the BSC operator to
select which version of the specification to use.
68P02901W01-S 4-45
Jul 2008
Receive antenna VSWR and radio loopback test Chapter 4: BSS Software Release Features
Receive antenna VSWR and radio loopback test
The Receive Antenna VSWR and Radio Loopback Test feature provides added radio diagnostics
to aid in fault detection in the field. Specifically, this feature provides:
Reduced maintenance costs; through quick and accurate verification of radio serviceability,
and prevention of unnecessary site visits.
Enhanced system operability and reliability; through minimizing operator procedures for
fault management, and enabling standby devices to be tested to detect latent faults.
Enhanced quality of service; through enhanced system operability and reliability.
The diagnostics provided by this feature are:

Receive Preamplifier Input Loopback. Horizonmacro supports this diagnostic. Transmitter
output is looped back at the receive preamplifier input (after being down-converted to the
receive frequency).
Receive Antenna VSWR. Horizonmacro supports this diagnostic. Receive Antenna VSWR
testing is first performed by gathering results from the Receive Preamplifier Input
Loopback test. Next, the receive-frequency-translated transmitter output is directed to the
receive antenna and the reflected signal strength is measured. These two sets of results
are used to compute a VSWR measurement.
Dynamic allocation of RXCDR-BSC circuits
The dynamic allocation of an RXCDR to the BSC circuits feature introduces fault management
for call traffic on the BSC to RXCDR interface (referred to as the Ater interface) by managing
the individual 16 kbps channels (called Ater channels) on this interface. In addition, this feature
provides for validation of the Circuit Identity Code (CIC) and Ater channel provisioning between
the BSC and RXCDR to ensure that calls are placed on the correct circuit between the BSC and
the MSC. Without this feature in place, no fault management of the Ater channels would be
possible, and all Ater and CIC information must be manually verified by the operator, resulting
in a higher Operation and Maintenance cost for the Motorola BSS.
The dynamic allocation and release of RXCDR to BSC circuits provides the following benefits:
Simplified network provisioning; there is no need to manually map CICs to Ater channels
at both the BSC and RXCDR.
Simplified network debugging; through automatic and manual audits of CIC and Ater
channel information between a BSC and RXCDR.
Better fault tolerance for call traffic, since calls do not necessarily need to be terminated
due to a single failure on the link set between an RXCDR-BSC.
Better utilization of network resources.
This feature will remain consistent with the Terrestrial Circuit Device Management feature,
with respect to how the operator is permitted to manage the CIC devices.
4-46 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced XBL
Enhanced XBL
The term XBL, refers to a BSC-RXCDR link. The new Enhanced XBL (EXBL) feature improves the
robustness of communication between the BSC and the RXCDR. The basis of this feature is to
provide a generic messaging system between the BSC and the RXCDR. This generic messaging
system is used to suit both current operator needs and the needs of future BSS features.
Operator-visible aspects of the EXBL feature are that runtime checks of database consistency
and connectivity are performed between the BSC and RXCDR to ensure that traffic pathways are
properly configured, and that every E1 link to an RXCDR device, at the BSC has a corresponding
link configured at the appropriate RXCDR. Operators are notified of any failure of these
connectivity checks so that they can take the appropriate action.
In the event of a verification failure, the BSS automatically disables the relevant CIC devices
to ensure that they are not used.
In addition, indications regarding maintenance activity, or faults, occurring at the RXCDR, which
indirectly affect the BSC link devices, are forwarded to the BSC for processing.
Horizonmicro2/Horizoncompact2 generic BTS software
The BSS software supports the 900/1800 Horizonmicro2/Horizoncompact2 feature as a restricted

feature (Master and Slave combination). The 900/1800 Horizonmicro2/Horizoncompact2 feature
is available on a per BSS basis. The operator is not permitted to configure a Horizonmicro2 BTS
site in the BSS database, if the 900/1800 Horizonmicro2/Horizoncompact2 feature is restricted
(specific to the Horizonmicro2/Horizoncompact2).
There are no new code objects required exclusively for the master Horizonmicro2
BTS, they remain the same as existing Horizonmicro BTS platforms. The 900/1800
Horizonmicro2/Horizoncompact2 feature is implemented by modifying existing code objects.
Dynamic power control is also supported on the Horizonmicro2 and Horizoncompact2 BTSs.
Synthesizer frequency hopping is also available over multiple BTSs in the same cell.
Code corruption immune design
This feature aims to reduce the number of field returns of M-Cell, and Horizon based equipment
due to code corruption. It also maintains backward compatibility with previous hardware and
software loads.
Code corruption usually occurs during field code upgrades and a power outage disturbs the
programming process. In order to reduce the number of equipment returns, modifications have
been made to both software and hardware.
Hardware
Flash (non-volatile memory) is doubled in size. The flash is divided into two banks; the first bank
stores a master copy of the operational code, while the second bank stores the recovery copy.
A hardware switch is required to select either of the banks.
68P02901W01-S 4-47
Jul 2008
Propagate TSC changes to all timeslots Chapter 4: BSS Software Release Features
Software
The software validates the operational code in both banks of flash. If there are no problems,
then the operation of the equipment is allowed to continue. If one of the banks has corrupt
operation code, then a copy of the valid bank is made to immediately overwrite the corrupt bank.
Propagate TSC changes to all timeslots
This feature provides more flexibility for automatically updating Training Sequence Codes
(TSCs) of RTFs within a cell when a BSIC is changed. Three options are provided:
Current Implementation - only update TSCs of BCCH/CCCH timeslots.
Update TSCs for all timeslots on the BCCH carrier.
Update TSCs for all timeslots on all carriers of the cell.
The Single BCCH for Dual Band Cells feature is an enhancement to the GSR3 multiband feature,
to allow more efficient network operation by enabling a single BCCH carrier to serve GSM900
and DCS1800 cells in the same coverage area.
Support for E1 conversion
This feature removes the support for E1 conversion.
Enhanced power outage recovery
The Enhanced Power Recovery feature improves system availability in the event of a total
power loss to the site, by providing a non-volatile storage mechanism for BSS Software. This
feature works in conjunction with the present battery back up feature. The non-volatile memory
resides on a new piece of hardware, the Non-Volatile Memory Card (NVM card). This card is
located only at BSC and RXCDR sites.
A background task ensures that the NVM is loaded, and periodically updated, with the same
BSS software objects as the master GPROC board. When powering up after a power loss, the
site will retrieve code from the NVM board, if necessary.
Improved MTL load balancing
This feature improves the loadsharing of traffic on message transfer links (MTLs) in the
uplink direction from the Base Station System (BSS) to the Mobile Switching Center (MSC).
Loadsharing from the MSC to the BSC is based on the routing function implemented at the MSC
and is beyond the scope of this feature. The granularity of the load distribution is increased
from 16 to 64, resulting in a more even distribution of traffic across the MTLs.
4-48 68P02901W01-S
Jul 2008
System Information: GSM Overview BTS concentration resource optimization for handovers
The implementation of test traffic generation at the BSS for message transfer part (MTP)
Layer 3 testing is modified to support the new loadsharing mechanism. A new MTP Layer
3 test message is added which allows the remote side to determine how the virtual circuits
are distributed over the active MTLs. A database element is added for setting the loadshare
granularity to either 16 or 64.
BTS concentration resource optimization for handovers
The BTS Concentration Resource Optimization for Handovers (BCROH) feature optimizes the
terrestrial backhaul between a BSC and BTS during handovers, when the BTS concentration
feature is applied. Previously when a handover occurred, a new circuit for the destination radio
channel was always allocated between the BSC and the BTS. The BCROH feature means that if
the source and destination BTS in a handover are the same, then a new circuit is not allocated
and the existing circuit is reused for the radio destination channel. It can only be used in
conjunction with BTS equipment that supports BTS concentration.
The BCROH feature reduces the number of resources required when intra-cell handovers
or inter cell handovers (within the same site) occur and are controlled by the BSC. In these
handover scenarios the switch connections for the voice traffic from the radio channel to the
MSC are no longer made at the BSC during the handover. The BTS to MSC path remains
constant and the BTS must simply move the switch connection of the Abis circuit from the
source radio channel to the destination radio channel.
Handover parameter
The Handover parameter re-Organization/reduction (also referred to as RSS Bin Reduction)

feature, removes a number of unused bins allocated to each of the radio subsystem (RSS)
handover and power control algorithms. It cleans up previously wasted database space.
Additionally, this feature converts any test object functionality into MMI commands. Extended
range cell prioritization and the uplink quality value of 7 on a missing measurement report is
supported by CM/MMI commands.
Per neighbor area for adaptive handovers
The adaptive handover methodology allows handovers to occur more rapidly when conditions
are deteriorating quickly and less rapidly when conditions are only marginally poor.
This enhancement to adaptive handovers provides the operator with the option of setting the
cumulative area for adaptive power budget handovers on a per cell or per neighbor basis.
This enhancement to the existing optimized power control feature, allows the operator to enable
a power control algorithm that allows RXLEV based power reductions. Calculations are made
for both uplink and downlink power control.
68P02901W01-S 4-49
Jul 2008
Support for the MTL statistics Chapter 4: BSS Software Release Features
Dynamic power reduction is used in the event of the RXLEV exceeding the upper level threshold.
If the algorithm is enabled, power level reduction step sizes can be changed dynamically,
based on the current proximity to the upper power level threshold. This will allow the power
to be brought down at a faster rate when it has strayed out of the power box. The dynamic
power reduction feature is enabled in addition to the good quality, poor quality, and low-level
adjustments. These three adjustments may also be chosen without the high-level adjustment
provided by this feature.
Support for the MTL statistics
This feature implements the BUSY_CICS statistic at the BSS.
The weighted distribution statistics produce a mean value indicating the average number of
circuit identity codes (CICs) in use during a statistic interval.
The statistic is pegged each time an allocation or deallocation of a CIC is detected. It is an

indication of the amount of active calls under the mobile switching center (MSC). Since each
call is routed through the MSC (even intra-BSS and intra-cell), the number of CICs represents
the number of calls in progress under that MSC for the base station system (BSS).
Support for frame erasure rate statistic
This feature implements frame erasure rate (FER) and residual bit error rate (RBER) statistics
at the BSS.
These statistics provide the following benefits:

Ability to target optimization efforts on cells and radios.
Meaningful call quality metrics for hopping network benchmarking and health reporting.
Uplink FER offers an alternative to drive test for voice quality.
BTS concentration call priority handling
The BCCPH feature enables the BSS to prioritize the order in which non-emergency circuit
switched calls are preempted by emergency calls.
This feature preempts circuit switched calls based on priority as well as age. The BSS
attempts to preempt a non-emergency circuit switch call with the lowest priority first and a
non-emergency circuit switch call with the highest priority last. If two calls exist with the same
priority level then the oldest is chosen first.
GPROC function preemption
This feature searches for a Busy-Unlocked generic processor board (GPROC) running a lower
priority function, when a GPROC hosting a higher priority function goes out of service, and
there are no Enabled-Unlocked GPROCs to host the higher priority function. If such a GPROC is
found, the lower priority function is preempted by the higher priority function. The operator is
able to configure the preemption algorithm using a database element.
4-50 68P02901W01-S
Jul 2008
System Information: GSM Overview Parallel cage enable
The levels of preemption that can be configured are:

No preemption.
Function level preemption: If a function of lower priority is running on a GPROC, that

function is preempted. In the case of a preempted LCF, the LCF with the highest function
id is preempted.
Intra function level preemption: If a function of lower priority is running on a GPROC, that
function is preempted. If a GPROC running the LCF goes out of service and there is no
lower priority function type (for example, BTF) running on a pool GPROC, the function
tables are searched for a lower priority LCF to preempt.
Parallel cage enable
CAGEs at an InCell multi-cage site were previously brought into service serially. This feature
brings the CAGEs at InCell BSCs and RXCDRs into service in parallel. Cages at an InCell BTS
site is brought into service in parallel when the master BTP is a GPROC2.
Cages at an InCell BTS site will continue to be brought into service serially when the master
BTP is a GPROC1.
Enhanced MMI link device warnings
MMI issues confirmation warnings when the operator uses the lock, ins_device, or reset_device
commands on some link devices. Additionally, in some cases, MMI issues confirmation warnings
when the MSI, MMS, or DPROC is locked and it has an associated link device.
The Enhanced MMI Link Device Warnings feature addresses a number of problems that existed
with the MMI link device warnings. The previous link warnings have been replaced with a
new, comprehensive set of warnings.
The affects of this feature are:

MMI issues a warning message and prompt for confirmation whenever the lock, ins_device,
or reset_device commands are used on a link device.
MMI issues a warning message and prompt for confirmation whenever the lock, ins_device,
or reset_device commands are used on a parent device that supports link devices.
MMI issues confirmation warnings for link devices regardless of their current state.
The warnings that MMI issues for link devices define the link affected and the
consequences of locking the link device.
The warning that MMI issues for a particular link device is the same for all of the MMI
state change commands.
68P02901W01-S 4-51
Jul 2008
BSS software release GSR5.1 Chapter 4: BSS Software Release Features
BSS software release GSR5.1

GSR5.1 features
Table 4-22 summarizes the features provided at software release GSR5.1.
Description
BSS processing of suspend message
CS3, CS4, and 32 kbps TRAU
GPROC fast reset
Unequip TCU/CTU cabinet
850 MHz frequency range
1900 MHz Horizon
BSS processing of suspend message
Feature overview
Previously, the BSS did not process the suspend message received from the mobile. As stated
in GSM 04.08, the BSS needs to process this message and to communicate it to the Serving
GPRS Support Node (SGSN) (GSM 08.18). This feature enables the BSS to communicate the
suspend message to the SGSN.
Feature description
When a GPRS attached MS enters CS dedicated mode to answer a CS page, and MS limitations
make it unable to continue to communicate for GPRS, the MS will request to suspend GPRS
services. The BSS processes this message from the mobile to suspend its GPRS service and sends
a suspend message to the SGSN through a Gb link (interface between an SGSN and a BSC).
The SGSN, in turn, does not initiate any paging for this mobile while it's in the suspend state.
When the mobile switches from the CS dedicated mode back to the GPRS mode, it sends a
routing area update message asking the SGSN to resume the data transfers.
4-52 68P02901W01-S
Jul 2008
System Information: GSM Overview CS3, CS4, and 32 kbps TRAU
Feature overview
The GPRS Coding Scheme 3, Coding Scheme 4 (CS3/CS4) and 32 kbps Transcoder Rate
Adaption Unit (TRAU) feature implements an alternative channel coding algorithm over the air
which enables increased data rates to GPRS mobile stations.
Software changes
The BSS and PCU changes necessary to implement Coding Scheme 3 and Coding Scheme 4
are software changes. There are no hardware modifications or additions necessary to support
this feature.
32 kbps TRAU channels
The BSS supports 32 kbps TRAU channels that are comprised of two independently synchronized
16 kbps TRAU channels. Both component 16 kbps TRAU channels of any given 32 kbps TRAU
channel reside on a single GDS to ensure that a single TRAU processing entity can handle
the reassembly of the individual channels.
CM database parameters
Additionally, two new CM database parameters are necessary to control whether the CS3,
CS4, and 32 kbps TRAU is allowed in the BSS. If CS3, CS4, and 32 kbps TRAU is allowed in
the BSS, then cs34_enabled must be enabled. To support the feature on a per carrier basis,
every timeslot dedicated to GPRS must have sufficient backhaul present to support the 32
kbps TRAU. This is enabled by a per carrier parameter as part of the equip_rtf command
called allow_32k_trau.
New statistic
A new statistic GPRS_32K_CHANNELS_SWITCHED is introduced to complement the CS1 and

CS2 statistics that are currently implemented.
Dynamic allocation
The use of the dynamic allocation feature in conjunction with the CS3, CS4, and 32 kbps TRAU
feature is not supported at this time. In a network at sites using dynamic allocation, the CS3,
CS4, and 32 kbps TRAU feature is not allowed.
Restrictions
Every firmware platform that currently supports GPRS supports CS3, CS4, and 32 kbps TRAU,
consequently no additional restrictions need be placed on the carriers or RTF equipage due
to this feature.
68P02901W01-S 4-53
Jul 2008
GPROC fast reset Chapter 4: BSS Software Release Features
GPROC fast reset
Feature overview
The Fast Reset (Soft Reset) feature enables a GPROC to come back into service quicker, when
recovering from a fatal Software Fault Management (SWFM). If the GPROC is functioning as
the master BSP/BTP, then the fast reset feature has the effect of bringing the site into service
sooner. This feature reduces the outage time for the involved GPROC(s) and increases the
total availability of the site.
Feature description
The fast reset feature decreases the recovery time for a reset by having the GPROCs transition
software from RAM back to RAM during a reset, without going through the ROM process. The
differences between a RAM-RAM software transition and a RAM-ROM software transition is that
the RAM-RAM procedure does not execute the functionality in ROM, as it is passed over.
During a RAM-RAM software transition, the GPROC that incurred the fatal SWFM is taken off
the LAN and all TDM connections for that GPROC are cleared. Then, instead of performing
a software transition to ROM, the GPROC comes back on the LAN in RAM and performs the
RAM initialization procedure.
The theory behind the fast reset feature is that a process executing in RAM, which encounters
a bus fault or any other fatal SWFM event, does not need to go through the ROM transition
to restore the GPROC. By halting all processes on that GPROC and reinitializing it, the fault
generating condition should no longer exist. If the fatal SWFM condition still exists, an
escalation mechanism eventually transitions (points) the GPROC software into ROM.
Unequip of TCU/CTU cabinets
This feature enables the unequipage of extension cabinets of types TCU_2, TCU_6, and
Horizonmacro_ext at M-Cell, and Horizonmacro sites without having to unequip the site. This
action can be done, if the cabinet is locked and there are no DRIs or EASs equipped to the
cabinet. All other cabinet types are not supported by this feature.
850 MHz frequency range
Provides software support for a BSS to operate in the 850 MHz frequency range using features
already introduced in prior releases.
1900 MHz Horizonmacro
Provides software support for a BSS to operate in the 1900 MHz frequency range using features
already introduced in prior releases.
4-54 68P02901W01-S
Jul 2008
System Information: GSM Overview Single BCCH for dual band cells
The Single BCCH for Dual Band Cells feature is an enhancement to the GSR3 multiband feature,
to allow more efficient network operation by enabling a single BCCH carrier to serve GSM900
and DCS1800 carriers in the same coverage area.
The main impacts of the Single BCCH for dual band cells feature are as follows:
Support of two different frequency bands within a single cell, using a concentric cells
configuration.
The operator can define the coverage area of the secondary band by use of BSS database
parameters.
Channel algorithms are supplied to incorporate selection of channels from different

frequency bands, and ensure the allocation of a secondary band (inner zone) resource at
TCH assignment when required criteria are met.
Power level conversions are provided for intra-cell channel changes and incoming inter-cell
handover between channels on different frequency bands.
Other optional features that must be unrestricted in order to configure dual band cells are:
Multiband handover - Refer Multiband inter-cell handover in BSS software release
GSR3 on page 4-36.
Concentric cells - Refer Concentric cells in the BSS software release GSR3 on page
4-36 section.
Dual band cells - Refer BCCH frequency, SDCCH in EGSM in the BSS software release
GSR6 on page 4-56 section.
The functions of these features on which the Single BCCH for dual band cells is dependent
are described in this manual. A technical description of the Single BCCH for dual band
cells feature, and these features are contained in the manual Technical Description: BSS
Implementation (68P02901W36).
Homogeneous cabinet - Refer the equip CAB command in the manual Technical Description:
BSS Command Reference (68P02901W23).
Heterogeneous cabinet (for combined cabinet configurations) - Refer the equip CAB command
in the manual Technical Description: BSS Command Reference (68P02901W23).
68P02901W01-S 4-55
Jul 2008

GSR6 features
Table 4-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) 2G to 3G 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
4-56 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced circuit error rate monitor
Enhanced circuit error rate monitor
Feature overview
The original Circuit Error Rate Monitor (CERM) optional feature provides a means for
identifying when discontinuity is detected on a circuit. The customer can:
Reduce cost of ownership.
Reduce downtime of devices.
Enhance system operability.
Enhance quality of service.
A circuit is considered to be the path along which a connection is made, from the entry point in
the BSS (for example, a radio at the BTS) to the exit point in the BSS (for example, the MMS
timeslot that connects to the MSC or PCU).
The CERM is used to monitor the continuity and sanity of hardware processing elements in a
circuit, on a per call basis. Whenever a discontinuity is detected for a circuit during a call, error
counts are updated for the points monitored for the call. When the error count at a particular
monitoring point reaches or exceed an operator specified threshold, an alarm is generated. The
alarm contains information identifying the monitored path in which the error is detected, thus
allowing the operator to identify potentially faulty devices.
Feature description
The CERM feature is enhanced, enabling the monitoring at various points in a GSM network
circuit, thus improving the ability of an operator to narrow down where a faulty device is
located. Although having these monitoring points in the circuit path narrows down the list of
potentially faulty devices, it does not confirm that a device is faulty. It is still up to the operator
to determine which device is faulty.
The following points in a network can be monitored on a per timeslot basis:

Circuit identity Code (CIC) on a link between the RXCDR or BSC and the MSC.
ATER Channel Identifier (ACI) groups on a link between the RXCDR and the BSC.
GPRS Circuit Identifier (GCI) in the radio hardware.
Radio Channel Identifier (RCI) in the radio hardware.
Path Identity Code (PIC) on a link between the BSC and a BTS.
The PIC is a special case because it is measured on a from-BSC-to-site basis. So, for example,
with a path leading from a BSC to two daisy chained BTSs, the PIC for the second BTS
encompasses the path through the first BTS to the BSC.
68P02901W01-S 4-57
Jul 2008
Multiple GPRS carriers per Cell Chapter 4: BSS Software Release Features
Multiple GPRS carriers per Cell
Feature overview
Before GSR6, the Motorola GPRS product offered the capability to configure up to eight GPRS
TimeSlots (TSs) on a single carrier in a cell. The increase in packet data traffic and availability
of multiple timeslot GPRS MSs have increased the need for additional GPRS capacity.
The Multiple GPRS carrier feature enables the network operator to configure multiple GPRS
carriers per cell for increased GPRS traffic handling capability to meet this increase in packet
data traffic and the expanding base of GPRS subscribers with increased data throughput.
The operator is offered two options to configure GPRS TSs on multiple GPRS carriers per cell:
Configure for performance
Operator specified
Configuration performance
Configure for performance provides the network the capability to configure all the reserved
and switchable GPRS timeslots in a cell contiguously to maximize performance. The contiguous
GPRS TSs configured on a carrier in a cell provide ease in scheduling packet data and the
capability to service multiple TS GPRS mobiles.
Table 4-24 is an example of multiple GPRS carriers where the default option, configured for
performance, is specified. The GPRS resources are configured contiguously on GPRS carriers
in the cell to maximize performance. The cell has five GPRS carriers, ten reserved TSs, and
eleven Switchable TSs.
Table 4-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
Operator specified
The operator specified option provides customers with the flexibility to configure the maximum
and minimum number of reserve and switchable GPRS timeslots on a per carrier basis in a
cell. Table 4-25 is an example of GPRS timeslots distributed over carriers in the cell. The
cell has five GPRS carriers, ten reserved timeslots, and eleven switchable timeslots. The
max_gprs_ts_per_carrier element is set to 6.
4-58 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced GDP provisioning
Table 4-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 are reconfigured on
a different carrier that supports GPRS based on the radio resources available in the cell.
Feature overview
Enhanced GDP provisioning is an enabler for future features which require a reduction in
board channel capacity for example, AMR.
A GDP is a Generic Digital Signal Processor (DSP) Processor board. It is interchangeable

with the XCDR board.
A GDP can provide either Basic or Enhanced transcoding.
Types of transcoding
A user can select the type of transcoding used by a GDP. The transcoding types are:
Basic - Transcoding for GSM Full Rate speech, Enhanced Full Rate speech and phase 2
data services.
Enhanced - Transcoding for future applications, particularly Adaptive Multi Rate (AMR)
speech coding, in addition to existing GSM Full Rate speech, Enhanced Full Rate speech
and phase 2 data services.
Enhanced GDP Provisioning:

Supports GDPs that are capable of enhanced transcoding, particularly AMR speech coding,
in addition to supporting current transcoding services.
Allows GDPs to provide additional enhanced transcoding resources only without making
use of the E1 line interfaces.
68P02901W01-S 4-59
Jul 2008
Call downgrade on CIC capability mismatch Chapter 4: BSS Software Release Features
Feature description
A GDP can be either a Primary or Secondary GDP, as follows:

A Primary GDP provides an E1 interface to the MSC. The GDP may provide basic
transcoding, or be paired with a Secondary GDP to provide enhanced transcoding. Primary
GDP can provide Enhanced transcoding only.
A Secondary GSD in a pair provides DSPs for transcoding for a set of CIC devices routed
to the MSC through the E1 interface of a Primary GDP. Secondary GDP can provide
Enhanced transcoding only.
The Enhanced GDP provisioning feature performs the following functions:

Supports provisioning for GDPs which are capable of enhanced transcoding features,
particularly AMR, in addition to supporting current services. Before this feature,
transcoding was performed by 15 DSPs on a GDP processing 2 calls each. The processing
requirement for future features demands that each of the DSPs processes a single call. A
pair of GDPs is required for provisioning of 30 transcoding circuits on an individual E1 link
to the MSC, which are capable of the enhanced transcoding features.
Supports provisioning for GDPs to provide additional enhanced transcoding resources only,
without making use of their E1 link line interface.
Prerequisites for enhanced GDP provisioning
For Enhanced GDP Provisioning to be used for new transcoding applications, the following
feature must also be implemented:
Adaptive Multi-Rate (AMR) Speech Coding.
The related MMS must exist before specifying it as the MSC MMS for a secondary GDP or, if the
MSC MMS is the GDP's own MMS, it is equipped (automatically). A GDP can only provide the
MSC MMS for one secondary GDP.
Call downgrade on CIC capability mismatch
Feature overview
The call downgrade on CIC capability mismatch feature resolves erroneous call handling that
could cause loss of speech due to the requested speech version not matching the capabilities of
the underlying transcoding equipment.
This feature also enhances the support of the Generic DSP Processing board, adding Enhance
Full Rate capability as well as allowing a staged migration to future advanced transcoding
technologies such as AMR.
4-60 68P02901W01-S
Jul 2008
System Information: GSM Overview Call downgrade on CIC capability mismatch
Feature description
The Generic DSP Processor (GDP) board was introduced into the BSS and RXCDRs to support
EFR speech as the previous transcoder, the XCDR was not re-programmable and could only
support Full Rate (FR) speech and ETSI Phase 2 Data Services.
Previously, Motorola mandated that for EFR to be provided, all transcoders must be GDPs.
With local transcoding, this was easily enforced by not enabling EFR if XCDR boards were
fitted at the BSC. However, for remote transcoding, because no specific signaling in terms of
capabilities existed between the BSC and RXCDR, EFR could be enabled at the BSC even
though the RXCDR contained XCDRs.
Pooled transcoding at the MSC and the RXCDR was introduced to support this co-existence of
XCDRs and GDP within the BSS. EFR capable CICs terminating on GDP boards, FR capable CICs
terminating on XCDR boards with data services being supported by both types of transcoder.
This configuration is satisfactory provided the pool of transcoders at the RXCDR match that
of the MSC. However, if mismatches do occur, EFR calls could be routed to XCDR boards,
resulting in calls with no speech.
Call downgrade on CIC capability mismatch resolves this problem by allowing the co-existence
of differing capability platforms, which match the capabilities of the underlying hardware with
those for incoming call requests. These are:
Calls specifying a preference for EFR, but also allowing the use of GSM FR, would use EFR
when utilizing a CIC supported by a GDP board.
Calls specifying a preference for EFR, but also allowing the use of GSM FR, would use
GSM FR when utilizing a CIC supported by an XCDR board.
Until the inclusion of AMR capable hardware is available, requests for AMR would be
targeted to match the capabilities of the associated CIC or supporting hardware and use
either GSM FR or EFR.
It also enhances the capability of the Generic DSP Processing board by adding EFR and allowing
a staged migration to AMR.
This feature introduces the following:

Mutli-platform support
Support of transcoding platforms with different capabilities within the BSS, to allow the
XCDR and GDP boards to co-exist within the same BSC (in the case of local transcoding) or
RXCDR (in the case of remote transcoding).
Enhanced CIC management
Detection of CIC speech version capabilities by the BSS, based on the supporting
transcoding platform.
Enhanced call management
Validation of MSC call setup, in-call modification, and handover requests to ensure that the
given permitted speech version(s) included are supported by the specified CIC.
68P02901W01-S 4-61
Jul 2008
GPRS PCU recovery on last GSL failure Chapter 4: BSS Software Release Features
GPRS PCU recovery on last GSL failure
The GPRS Signaling Link (GSL) is a control link between the Base Station Controller (BSC) and
the Packet Control Unit (PCU). It is a required resource for providing the packet data services
as well as for operation and maintenance of the PCU. Previously, if all the GSL links went out
of service, the PCU reset itself to simplify the releasing and rebuilding of the resources in the
data services.
A problem with the previous design was that once the PCU reset itself, it took unnecessary
time to re-establish the link between the BSC and PCU and then to bring back the PCU into
service in order to process data calls again.
NOTE
If no GSL connection is made within 30 minutes the PCU will go into RAM mode reset.
At the first GSL restoration, the first GSL IN Service (INS) procedure will not be
started until the last GSL Out Of Service (OOS) procedures are completed. This
protects the BSC and PCU from unstable GSLs.
This feature enhances the availability of the PCU by preventing the PCU from resetting upon the
last GSL disconnection and quickly brings it up in service again upon the GSL reconnection.
When the last GSL goes out of service, the system software in the PCU and BSC now manages
and reconfigures the network resources promptly, smoothly deallocating the resources for data
calls and reallocating them for voice calls.
This feature also improves the problem analysis of the PCU because the processes on the PCU
stay up and continue to run during the last GSL failure allowing the operator to interrogate
the processes for problem analysis, locally.
Network Controlled (NC1 and NC2) cell reselection
Feature overview
In a GPRS network, cell reselection is equivalent of a GSM circuit switched handover triggered
by, for example:
change in location of the mobile.
change in RF conditions.
cell congestion.
GPRS cell reselection offers mobility and performs network traffic management. The different
modes of cell reselection in GPRS network are referred as NC0, NC1, NC2, and RESET. In the
initial Motorola GPRS product offering, NC0 was provided. In cell reselection mode NC0, the
mobile performs autonomous cell reselection based upon on the radio environment. This feature
release provides the remaining two modes of cell reselection NC1 and NC2 to enhance the
existing product offering. Table 4-26 shows the different cell reselection modes, responsible
network element, and functionality.
4-62 68P02901W01-S
Jul 2008
System Information: GSM Overview Network Controlled (NC1 and NC2) cell reselection
Table 4-26 Cell reselection modes
Cell reselection mode Control element Functionality

NC0 MS control Normal GPRS MS control: Autonomous cell
reselection.
Enhanced NC0 MS control Functionality in NC0 mode plus: BSS sends

cell reselection commands to GPRS MS to
change cell reselection mode.
NC1 MS control Normal GPRS MS control: Autonomous
cell reselection, MS sends measurement
reports to BSS.
Enhanced NC1 MS control Functionality in NC1 mode plus: BSS sends
cell reselection commands to GPRS MS to
change cell reselection mode.
NC2 Network control MS sends measurement reports to BSS,
BSS sends cell reselection commands to
GPRS MS, BSS instructs MS to perform cell
reselection.
Feature description
In the current Motorola GPRS network, the MS autonomously performs cell reselection based
solely on the RF measurements of the serving and neighboring cells. The GPRS MS is unable
to reselect to a neighbor cell based on important factors: such as congestion, availability of
GPRS, ability to support mobiles and current grade of service.
The main objective of the network controlled cell reselection and congestion relief feature is to
increase network capacity and to provide the network operator with a tool for network planning
and improved quality of service. The operator is able to specify GPRS cell reselection mode
on a per cell basis, within the network of cells with the same cell reselection command, thus
providing the flexibility of virtual zones. A significant portion of this feature incorporates the
addition or modification of statistics that reflect radio conditions at the MS and congestion in
the GPRS network. Benefits of statistics collection are as follows:
Provide network information to change cell reselection mode on a per MS basis.
Provide information to monitor network radio and congestion information to determine

and perform cell selection.
Provide network planning information and configuration of NC2 mode parameter. In cell
reselection mode, NC2 enables the BSS to take appropriate action to reduce congestion if
the originating cell is congested.
68P02901W01-S 4-63
Jul 2008
Location services Chapter 4: BSS Software Release Features
Location services
BSS location services support
The Location Services (LCS) feature implements emergency services functionality in GSM
systems (compliant with the Federal Communications Commission (FCC) 911 requirements)
in two phases:
Phase To transmit the originating number of an emergency call (911 in the United States)
1 and the location of the serving site to the Public Safety Answering Point (PSAP).
Phase To transmit the emergency caller's estimated position, expressed in latitude and
2 longitude co-ordinates within specified limits of accuracy.
Applications that request location estimates from location services can be located in the MS, the
network, or externally to the PLMN.
LCS positioning mechanisms
LCS currently specifies three positioning mechanisms in order to determine the location of a
Mobile Station. These positioning processes involve two main steps: signal measurement
and position computation based on the measured signals. The standard SMG (Special Mobile
Group) positioning mechanisms are:
Network-based uplink Time of Arrival (TOA)
Enhanced Observed Time Difference (E-OTD)
Assisted GPS (A-GPS)
Conventional GSM Timing Advance (TA) measurements can also be used in conjunction with
Cell ID determination to provide a coarser, lower quality location estimate.
Examples of applications to which LCS MS position determination can be applied are to deliver
tailored content to MSs in a physical locality (location-specific advertising), or to determine the
routing of voice traffic (location sensitive routing). Motorola supports Timing Advance (TA),
Enhanced Observed Time Difference (E-OTD) and Assisted GPS (A-GPS) positioning mechanisms.
Timing advance positioning
The Timing Advance (TA) positioning mechanism is based on the existing GSM timing advance
measurements, the frequency of sending of which is specified by the timing_advance_period
parameter. The timing advance value is known for the serving BTS and when returned to the
requesting LCS client, with the cell ID, provides the approximate physical position of the MS.
4-64 68P02901W01-S
Jul 2008
System Information: GSM Overview Basic MPROC redundancy
Basic MPROC redundancy
Feature overview
The purpose of the complete Master Processor (MPROC) redundancy feature is to support a 2N
redundancy scheme for the MPROC hardware within the Packet Control Unit (PCU) platform.
NOTE
2N Redundancy is also called pair redundant. Essentially, it means that there is
twice the amount of hardware than there would be for a non-redundant system. One
unit is active while the other is waiting in standby mode should the first unit fail.
In this scheme, one MPROC board serves as the active controller for the Packet Control Unit
(PCU) with a second MPROC board waiting in standby mode. Should the active board fail or
go out of service for some reason, the standby MPROC automatically takes over control of the
cage and continue normal system operation.
NOTE
MPROC failure results in a PCU cage reset until the reserve MPROC assumes control.
In addition to supporting the redundant hardware, this feature focuses on providing a fast
recovery from failures of the active MPROC. In the worst case, the PCU should make a complete
recovery within three to five minutes of the failure.
Feature description
This particular feature supports two MPROC boards within the PCU cage and provides for
an automatic switchover to the redundant board, should the active board fail. The following
benefits are provided by this feature:
Hardware-level failure of the MPROC board
Should such a failure occur, and a redundant MPROC is not available, the PCU remains out
of service until field personnel are able to perform an on-site replacement of the faulty
board. Once the board is replaced, the PCU will remain out of service until all code and
database objects are downloaded from the BSC. By having a redundant MPROC in place,
the PCU is able to remain in service until the on-site replacement can be made.
68P02901W01-S 4-65
Jul 2008
Enhanced BSC capacity phase 2 Chapter 4: BSS Software Release Features
Detection of MPROC failures
The redundant hardware constantly monitors the other MPROC board. When the
redundant board detects that the active board is no longer in charge of the PCU cage, the
redundant assumes that the other board has failed and, therefore, take over ownership of
the cage (and re-initialize the PCU accordingly). Although the assumption made by the
redundant board is incorrect, the operation of the PCU will not be adversely affected, the
only consequence is a longer recovery time than would be necessary under ideal conditions.
Improved recovery times
While this feature is not introducing ideal recovery times, this feature is able to recover
from MPROC software faults faster than if redundant hardware were not present. This
improvement is possible because the PCU is in recovery as soon as the active board fails.
Without this feature, the PCU would not be able to begin recovery until the failed MPROC
finished resetting.
Enhanced BSC capacity phase 2
Feature overview
This feature increases the number of carriers to 512 and the number of Circuit Identity Codes
(CICs) to 3200.
The feature supports the following configurations:

The BSS supports the standard database configuration for 384 carriers if the enhanced
BSC capacity feature is restricted.
The BSS supports the standard database configuration for 2400 CICs if the enhanced
BSC capacity feature is restricted.
The BSS supports the enhanced database configuration for 512 carriers if the enhanced
BSC capacity feature is not restricted.
The BSS supports the enhanced database configuration for 3200 CICs if the enhanced BSC
capacity feature is not restricted.
To increase the number of CICs to 3200, 27 BSC-RXCDR connectivities are required at the user
interface, as each connectivity is equivalent to a physical MMS port/2.04 Mbps link capable of
supporting 120 traffic channels, as follows:
20 x 120 = 2400.
27 x 120 = 3200.
Because of this, the BSC-RXCDR connectivity table at the BSS needs to be increased from
21 to 27 entries.
4-66 68P02901W01-S
Jul 2008
System Information: GSM Overview Improved MPROC software failures detection and recovery
Improved MPROC software failures detection and recovery
Feature overview
To improve recovery time for extreme software failures, the MPROC board implements a
watchdog timer. A low-level software process on the board resets the timer on a regular basis to
keep it from expiring. If this process is impeded for some reason (for example, the processing is
locked-up on some other task) the timer expires.
Should a watchdog timer expire, an interrupt is generated to low-level software which then
attempts to collect information about the current task, stores its registers or stack in compact
Flash memory, and then immediately resets the board. Upon subsequent initialization of the
board, the software reads the compact flash memory and if any watchdog reset information is
stored, prints that information out to the internal Executive Monitor (EMON) program.
Inter Radio Access Technology (RAT) 2G to 3G handover
Feature overview
This GSM feature supports handovers between different Radio Access Technology (RAT)
networks in the Circuit Switched (CS) domain. The RAT can be either 3G Universal Mobile
Telecommunication System (UMTS) or 2G GSM.
Feature description
Current evolving 3G UMTS networks soon will allow operators to provide UMTS coverage along
with GSM/GPRS coverage in their networks.
This feature enables a multi-RAT Mobile Station (MS), a mobile station that can function in
multiple Radio Access Networks (RAN) to hand over calls between a GSM Radio Access Network
(RAN) and a 3G UMTS Radio Access Network (UTRAN). To accomplish this, support is needed
from the MS, Core Network elements of the MSC and UMTS/GSM network elements.
The GSM BSS support for this feature includes:

3G (UMTS) to 2G (GSM) handover in active mode and cell reselection in idle mode.
2G (GSM) to 3G (UMTS) cell reselection in idle mode.
Being a completely new GSM function, a full description is available in the Technical Description:
BSS Implementation (68P02901W36) manual.
68P02901W01-S 4-67
Jul 2008
Clean install Chapter 4: BSS Software Release Features
Clean install
Feature overview
The purpose of this feature is to install the OMC-R on a SunFire 4800/4900 server. As Sun are
making their current Solaris system obsolete, from 2001 only Solaris 10 is shipped. Therefore,
the Operation and Maintenance Center-Radio (OMC-R) has its operating system upgraded.
Feature description
This feature installs the OMC-R on a SunFire 4800/4900 server. As part of the clean install,
OMC-R customers are using the Solaris 10 operating system.
For customers upgrading from a previous OMC-R release, a procedure to upgrade from Solaris
2.51 to Solaris 10 is included in the OMC-R Upgrade.
A Solaris 10 license is provided as part of the GSR9 package.
GPRS interleaving TBFs
Feature overview
This release is an extension to the software feature which introduced the General Packet Radio
Service (GPRS).
The Interleaving Temporary Block Flow (TBF) feature allows the rapid multiplexing of Radio
Signaling Link (RLC) data blocks of many different MSs onto a common air resource. Multiple
MSs are then able to share a common air resource although effective throughput of each MS on
that shared resource is decreased.
Feature description
Each MS sharing a common air resource is given a certain percentage of the shared resource
bandwidth. For example, if two MSs are interleaved on the same air timeslot, one MS is given
70% of the timeslot, while the second MS is given the remaining 30% of the timeslot. This
is illustrated in Figure 4-1.
4-68 68P02901W01-S
Jul 2008
System Information: GSM Overview GPRS interleaving TBFs
Figure 4-1 Example of Interleaving DL TBFs
RLC DATA BLOCKS
MOBILE A
MOBILE B
= IDLE RLC BLOCK = RLC DATA BLOCK
ti-GSM-Interleaving DL TBFs-00092-ai-sw
This interleaving increases the number of users that can be on a single timeslot, increasing the
overall capacity of a serving cell.
Interleaving TBFs in the uplink and downlink direction use block-by-block multiplexing, in which
two or more MSs are multiplexed on a timeslot with the capability of switching between MSs
every block period.
All of the MSs on a timeslot are all simultaneously active in TBFs. The TBF setup phase, TBF
release phase, or data transfer phase of one MS TBF may overlap with the TBF setup phase,
TBF release phase, or data transfer phase of other TBFs belonging to other MSs.
68P02901W01-S 4-69
Jul 2008
Link utilization improvements Chapter 4: BSS Software Release Features
Delayed release of downlink TBF
NOTE
Delayed release of downlink TBF is sometimes known as Supercoattail.
The delayed release of downlink TBF extends the downlink Temporary Block Flow (TBF) period
by 4.5 seconds by transmitting dummy Logical Link Control (LLC) frames. By delaying the
downlink TBF release, there is no need to send a new Packet Downlink Assignment (PDA),
allowing data to be sent straight away in the next block period. It also means that if the MS
uplink needs to be established while being polled during the extended downlink TBF period, the
CCCH and RACH do not have to be accessed, and a channel request in the DAK message is sent
instead, reducing the UL TBF establishment time by 500 ms.
Before the dummy LLC frames are sent, all previous LLCs are acknowledged by the MS. If no
meaningful data is sent by the MS on the PD channel for 4.5 seconds, interference to other MSs
transferring data can be caused. To reduce this interference, the CS1 data blocks corresponding
to the dummy LLCs are only sent on the Packet Associated Control Channel (PACCH) timeslot
when the MS needs to be polled.
Link utilization improvements
Feature overview
Previously, within the BSS software, the signaling messages exchanged between the Radio
subsystem (RSS) and Packet Resource Manager (PRM) processes, over the Radio Signaling Link
(RSL) and the GPRS Signaling Link (GSL), had a large header compared with the data part
of the message and consequently this produced a transmission delay. In addition, the BSS
software sent one message per Link Access Procedure for ISDN D-Channel (LAPD) frame on
the RSL and GSL links; this did not fully utilize the maximum size of the LAPD Unnumbered
Information (UI) frame.
This feature improves the performance of the RSL/GSL links and alleviates the expected
pressure on the capacity and speed of the links from the expanded capacity and high speed
GPRS features. The link utilization improvements feature reduces the message transmission
time between the BTS and PCU for the InCell, Horizonmacro and Horizonmicro/Horizoncompact
by 35% to 40%, 20% to 35% and 15% to 30% respectively. The number of GPRS timeslots that
the RSL can support should be increased by 40% in most GPRS BTS configurations.
4-70 68P02901W01-S
Jul 2008
System Information: GSM Overview Advanced load management for EGSM carriers
Feature description
The link utilization improvements feature addresses the above issues to speed up messages
exchanged between the RSS and PRM. The following enhancements have been made:
Smaller header for delivering messages between the RSS and PRM.
The new message header is eight bytes and contains minimum information necessary to
deliver the messages between the two processes. The functionality of the existing routing
functions will not change and a new set of routing methods and Application Programmer
Interfaces (APIs) are created for the application processes to use.
Message packing/unpacking mechanism at the RSL and GSL end-points.
This improves both speed and utilization of the RSL/GSL links by packing more than one
signaling messages into the same LAPD frame thus reducing the LAPD header overhead.
Messages waiting in the RSL/GSL mailboxes are packed in one LAPD frame before writing
it to the link, and it is unpacked when it is read from the link.
Creating a high priority mailbox.
The feature creates a high priority mailbox call LUI mailbox in the Executive Data Link
Service Process (Exec DLSP) for certain high priority messages between the RSS and PRM.
This mailbox is created at both the BTS and PCU. This enables processing of messages in
the LUI mailbox at a higher priority than messages in all other RSL/GSL mailboxes.
The RSS and PRM uses the small header with high priority for only certain high priority
messages. The messages sent with this option are routed to the LUI mailbox and all other
messages between the RSS and PRM (using the small header/normal header) are sent to the
RSL/GSL mailboxes. With this feature, the RSS and PRM can send and receive the following
messages:
Messages with normal headers, which go to RSL/GSL mailboxes.
High priority messages with small headers, which go to the high priority LUI mailbox.
Normal priority messages with small headers, which go to the RSL/GSL mailbox.
Advanced load management for EGSM carriers
The advanced load handover management function offers the operator the ability to specify
EGSM band handovers only to other EGSM bands. Otherwise EGSM handovers can occur
to neighboring cells that may not have an EGSM band available. DCS1800 bands is used
wastefully, particularly if the band_preference parameter is set, for example, to DCS1800. A
new parameter bss_egsm_alm_allowed enables the feature and EGSM handovers will occur to
EGSM sites if available, whatever the setting of band_preference.
When a handover is triggered with this feature set, the neighbor list of an EGSM MS on an
EGSM resource is manipulated such that EGSM internal neighbor cells are given preference
over non-EGSM neighbor cells.
68P02901W01-S 4-71
Jul 2008
Enhanced GPRS One Phase Access Chapter 4: BSS Software Release Features
Enhanced GPRS One Phase Access
Feature overview
This feature enables Enhanced General Packet Radio Service (GPRS) One Phase Access with the
Packet Control Unit (PCU) at the Base Station Controller (BSC) (Pre-load).
In a GPRS network, there are two packet access procedures that the mobile can use to establish
an uplink TBF. The packet access can be done in either one phase or in two phases. In the
current GPRS software architecture, the Base Station System (BSS) only supports the two-phase
access procedure. The intent of this feature is to introduce the one phase procedure, as well as
improvements to both procedures.
Enhanced GPRS One phase uplink TBF access is an improvement over the two-phase uplink TBF
access procedure. In a one phase uplink TBF access, the MS initiates an uplink TBF by sending
a Random Access Channel (RACH) to the BSS. The RACH is received at the BTS, which is then
forwarded to the PCU. The PCU responds to the RACH with an Immediate Assignment message
containing an uplink assignment. The MS moves to the assigned Packet Data (Traffic) Channel
(PDTCH) and begins its uplink data transfer. This procedure allows the MS to gain access to the
network much quicker when compared to the Two-Phase establishment procedure.
Refer to Technical Description: BSS Implementation (68P02901W36) for a full description of the
differences between the two access methods.
Remove support for collocated BSC
Feature overview
Support for the collocated InCell/BSC is disabled in GSR6 to enable compressed BTS objects to
be stored at the BSC in order to free up memory for new GSM and GPRS features.
See also feature Compress all BTS objects at the BSC.
A collocated InCell/BSC site will not be able to continue to operate in GSR6 release.
This feature enables all BTS objects to be stored in compressed form at the BSC in order to free
up memory for new GSM and GPRS features.
Support for the collocated InCell/BSC is disabled by blocking access to key commands to
prevent equipage of a collocated BSC.
Operators with collocated BSCs in their network have two choices:

Before upgrading from 1620 to 1650, all collocated InCell/BSC sites can be converted to
standalone InCell and BSC sites.
All collocated BSCs should remain at pre-1650 release, while remainder of network is
upgraded to 1650.
4-72 68P02901W01-S
Jul 2008
System Information: GSM Overview Compress all BTS objects at the BSC
Compress all BTS objects at the BSC
Feature overview
This feature is designed to save memory at the BSC by compressing all BTS objects at the
BSC and uncompressing them at the BTS. In addition, it speeds up OMC to BSC and BSC to
BTS download times.
See also feature Remove support for collocated BSC.
All non-BSC objects (Incell BTS, M-Cell, and so on) are compressed as part of the object build
and are stored in compressed form at the BSC to save memory.
The compressed objects are downloaded to the BTS and uncompressed as part of BTS
initialization.
68P02901W01-S 4-73
Jul 2008
BSS software release GSR6 (Horizon II) Chapter 4: BSS Software Release Features
BSS software release GSR6 (Horizon II)

GSR6 (Horizon II) features
Table 4-27 summarizes the BSS features provided at software release GSR6 (Horizon II).
Table 4-27 Release GSR6 (Horizon II) features
Description
Horizon II
Enhanced two uplink timeslots
Removal of support for Horizonoffice
Horizon II
Feature overview
The Horizon II feature provides support for the new Horizon II macro BTS and the CTU2
transceiver.
The Horizon II feature comprises the following elements:

Double density carrier CTU2 transceiver.
Support of up to six double density CTU2s in the Horizonmacro and Horizon II macro
platforms.
Backwards compatibility with the existing Horizonmacro platform.
The CTU2 transceiver provides the following functionality:
The CTU2 transceiver supports two logical carriers and can operate in either single or dual
carrier mode. It is backward compatible with the Horizonmacro platform, and is operated in
single or dual carrier mode in both the Horizonmacro and Horizon II macro BTS cabinets.
Combinations of TCU-A, TCU-B, CTU, and CTU2 in single carrier mode and dual carrier mode
are allowed within a cell providing RF power restrictions are obeyed.
Transmit power capability is different for single and dual carrier modes, see Table 4-28.
4-74 68P02901W01-S
Jul 2008
System Information: GSM Overview Horizon II
Table 4-28 CTU and CTU2 output power capabilities
Horizonmacro Horizon IImacro

Transceiver
Combining EGSM900 DCS1800 EGSM900 DCS1800
type
CTU None 40 32 N/A N/A
External 20 16 N/A N/A
CTU2 Single None 40 32 63 50
carrier mode
External 20 16 28 22
CTU2 Dual Internal 10 10 20 16
carrier mode
Internal and 4.5 4.5 9 7
external
In single carrier mode, the CTU2 capabilities are similar to those of the existing CTU, and the
CTU2 can be used as a replacement for the CTU providing GSR6 (or later) software is used.
In dual carrier mode, the CTU2 enables the Horizonmacro or Horizon II macro to support up
to twelve carriers. There are, however, certain restrictions when the CTU2 operates in dual
carrier mode:
Baseband hopping is not supported when the controlling cabinets are either Horizonmacro
or M-Cell, due to the switching capability of the MCU/MCUF.
Maximum output power capacity is reduced due to internal combination within the CTU2.
In Horizonmacro cabinets, maximum output power of a CTU2 in either single density or

dual density modes, is also restricted by the Horizonmacro cabinet power supply.
Remote Tune Combining (RTC) is not supported if the CTU2 is operating as a master
or standby controller of an RTC, however RTC is used if the CTU2 is not the master or
standby controller.
Both carriers must be in the same cell because the CTU2 has one single RF output.
The Horizon II macro BTS can be either the controlling cabinet or extension cabinet connected
to a controlling Horizon II macro/Horizonmacro/M-Cell BTS cabinet.
NOTE
BTS sites with Horizonmacro/M-Cell6 as the controlling cabinet must have a PCMCIA
card fitted for CTU2 to be supported.
The Horizon II macro BTS provides the following functionality:

Support up to six double density CTU2s, which provides up to 24 carriers in two
Horizonmacro/Horizon II macro cabinets.
Horizon II macro Site Controller (H2SC) with integrated NIU and FMUX, E1 support and
enhanced E1 redundancy, and increased removable flash media.
SURF2 (Sectored Unified Receiver Front end)
XMUX
68P02901W01-S 4-75
Jul 2008
Enhanced two uplink timeslots Chapter 4: BSS Software Release Features
Site I/O Panel
Increased Radio Signaling Link (RSL) functionality
Interoperability with the existing Horizonmacro/M-Cell BTS platform.
Horizon II macro cabinets only support a single frequency band, 900 MHz, or 1800 MHz.
Multiband cabinets are not available.
Enhanced two uplink timeslots
Feature overview
Enhanced two uplink timeslots (2UL) is an extension to the GPRS feature (RDB2773) introduced
in GSR4.1, and the Multiple GPRS carriers per cell (RDB3725), Interleaving TBFs (RDB4253),
and Enhanced one phase access (RDB4386) features introduced in GSR6.
This feature improves MS GPRS performance by allocating multiple timeslots in the uplink
direction.
Feature description
In GSR6, GPRS multi-slot class MSs which support multiple timeslot allocations in the uplink
and downlink directions, were only allocated one uplink timeslot. The Enhanced 2UL feature
provides allocation of up to two uplink timeslots for the MSs that support multiple uplink
timeslot allocation.
This feature improves the performance of MSs that support multiple uplink timeslot allocation
and comprises two sub-features:
Enhanced 2UL timeslot scheduling
Advanced uplink/downlink bias detection
Enhanced 2UL Timeslot Scheduling
This enables the operation of two uplink timeslots for MS multi-slot classes that support it.
All multi-slot classes that support multiple uplink timeslots in dynamic mode are mapped to
multi-slot class 5, 6, 9 or 10.
Table 4-29 shows the MS multi-slot class mapping for all GPRS multi-slot classes.
4-76 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced two uplink timeslots
Table 4-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
Advanced Uplink/Downlink Bias Detection
For some multi-slot class MSs the maximum number of uplink and downlink timeslots in the
MSs allocation is less than the sum of the maximum number of timeslots that can allocate in an
individual TBF direction. These MSs can be allocated more timeslots in one direction at the
expense of fewer timeslots in the opposite direction. This type of multi-slot class is called
a biasable multi-slot class. The Enhanced Two Uplink Timeslots feature supports biasable
multi-slot classes 6 and 10.
Figure 4-2 shows the multi-slot class 6 MS uplink bias configuration of two timeslots in both
downlink and uplink directions, or downlink bias of three downlink timeslots and one uplink
timeslot.
Figure 4-2 Multi-slot class 6 uplink or downlink bias timeslot allocation
Figure 4-3 shows multi-slot class 10 MS uplink bias configuration of two uplink timeslots and
three downlink timeslots, or downlink bias of four downlink timeslots and one uplink timeslot.
68P02901W01-S 4-77
Jul 2008
Enhanced two uplink timeslots Chapter 4: BSS Software Release Features
Figure 4-3 Multi-slot class 10 uplink/downlink bias timeslot allocation
The bias change mechanism is based on the data transfer characteristics in the uplink and
downlink directions. During uplink data transfer for example, the uplink direction is highly
active when compared to the downlink direction, the MS therefore receives an uplink biased
timeslots allocation.
Although MS multi-slot classes 5 and 9 support multiple uplink timeslots, these MSs do not have
the restrictions of biasable classes. Consequently, uplink/downlink biasing does not apply to
MSs of class 5 or 9.
4-78 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release GSR7

GSR7 features
Description
PCU 3X capacity increase
Enhanced Scheduling
Performance Enhancements Under Load
Seamless cell reselection
DSW/DSWX to be backwards compatible with KSW/KSWX
Adaptive Multi-Rate
Move PCU and BTS objects from BSP
GPRS PBCCH/PCCCH support
EGPRS
PCU 3X capacity increase
Feature overview
The primary purpose of the PCU 3X capacity increase feature is to allow an increase in PCU
capacity. The extra PCUs allow improved redundancy for PCUs.
The PCU 3X capacity increase feature allows the operator to enable redundancy for any or all
PCUs when more than one PCU is equipped. If three PCUs are equipped, a first and second
redundant PCU cell mapping can be set by the operator when redundancy is enabled.
The PCU 3X capacity increase feature allows the operator to add PCUs to a maximum of 3 per
BSC, which a single BSC must now manage. The other elements of the BSS (that is, BSC, BTS
PCUs) will not undergo any hardware or firmware changes for this feature, nor will the PCUs
have the capability to communicate directly with each other.
68P02901W01-S 4-79
Jul 2008
PCU 3X capacity increase Chapter 4: BSS Software Release Features
Figure 4-4 BSS configuration with 3 PCUs
Feature description
Figure 4-4 shows a general representation of a GSM BSS configuration with 3 PCUs equipped.
During certain fault conditions which render the Primary PCU inoperable, the cells are
moved from the Primary PCU to the first redundant PCU. If the Primary PCU return to the
IN-Service (INS) state, the cells are remapped back to the Primary PCU. If both the Primary
and first redundant PCU fail, the cells can be mapped to the second redundant PCU. If the first
redundant PCU returns to the INS state, the cells are mapped back to the first redundant
PCU. If at anytime the Primary PCU returns to the INS state, the cells are mapped back to
their respective Primary PCU.
NOTE
The BSC may interface with a range of 0 to 3 PCUs, where each PCU interfaces with
only that BSC. On the Gb interface, all PCUs which are attached to a single BSC
must interface with the same SGSN. All PCUs attached to a single BSC must also be
managed by the same OMC-R.
A PCU can terminate 60 single timeslot GSLs (30/E1 PMC) and support 4 GBLs. All combinations
of the various coding schemes (CS1 to CS4) are supported.
4-80 68P02901W01-S
Jul 2008
System Information: GSM Overview GPROC3
GPROC3
Feature overview
GPROC boards are used in the BSC, RXCDR, and InCell BTS network platforms to provide
the processing power required to operate the mobile network. However, as the capacity and
functionality of the GSM network product range has developed, system resources required to
power the network have increased and for GSR7 greater processing power is needed.
The original GPROC board was superseded by the GPROC2, which in turn is now being replaced
by the next generation of processor board, the GPROC3.
GPROC3 system performance is almost two times that of the GPROC2. This performance
increase is due to a culmination of several hardware factors, including:
Motorola 68060 processor
66 MHz bus clock frequency
Synchronous DRAM
Board layout modifications and MCAP timing changes
NOTE
The Battery Backup Extension (BBX) system does not support the GPROC3.
Table 4-31 provides a comparison between the GPROC3 and GPROC2 processor boards.
Table 4-31 GPROC3 comparison with GPROC2
Parameter GPROC2 GPROC3

Processor 68040 68060
Clock frequency 66 MHz 66 MHz
Memory 32 MB DRAM (scalable to 64 128 MB SDRAM
MB with SIMM module)
Flash memory 1 MB 16 MB
The GPROC3 is fully functionally backward compatible with the GPROC and GPROC2, and
can be used as a FRU at the following locations without impacting existing functionality or
external interfaces:
BSC
RXCDR
InCell BTS
68P02901W01-S 4-81
Jul 2008
Enhanced scheduling Chapter 4: BSS Software Release Features
Dual boot functionality
The GPROC3 has dual boot ROM functionality to provide additional protection in the event of
hardware, software, or flash failure.
Enhanced scheduling
Feature overview
Enhanced Scheduling is an extension to the GPRS feature introduced in GSR4.1, Multiple GPRS
Carriers Per Cell, Interleaving TBFs, and Enhanced One Phase Access features introduced in
GSR6, and the Two Uplink Timeslots feature introduced in GSR6.
Feature description
In GPRS One-Phase (EOP) access, when a Random Access CHannel (RACH) is received at a
BTS, the BTS uses an EOP assignment if available. When the EOP assignments are exhausted,
and the RACH throttle threshold has not been reached, the RACH is sent to the PCU. The
PCU then responds by sending a one-phase immediate assignment message back to BTS, for
transmission to the mobile station (MS).
Two-phase access is only used if the MS explicitly requests it. The two-phase RACH is processed
at the PCU and the required messaging is carried over RSL/GSL.
The number of messages exchanged between the PCU and BTS over the RSL by these different
TBF establishment methods may cause the RSL to overload at high RACH arrival rates. This
overloading may adversely affect circuit switched traffic and reduce GPRS traffic handling
capability.
The Enhanced Scheduling feature introduces mechanism that allow the BSS to dynamically
select the most appropriate access method, allowing fast access while reducing the load on the
signaling links. This feature comprises the following sub-features:
Dynamic allocation of reserved blocks for two-phase access.
Increased number of GPRS MSs that can be serviced by each PRP from the previous
number of 120.
Provides control for the percentage of RSL bandwidth reserved for circuit switched traffic.
These changes together increase scheduling efficiency leading to a greater amount of GPRS
traffic handling capacity in a given cell while reducing the impact of the data traffic on circuit
switched traffic.
4-82 68P02901W01-S
Jul 2008
System Information: GSM Overview Performance enhancements under load
Performance enhancements under load
Feature overview
The Performance Enhancements Under Load feature is an extension to the General Packet Radio
Service (GPRS) feature introduced in GSR4.1, and the Coding Scheme 3 or Coding Scheme 4
and Interleaving TBFs features introduced in GSR6.
It also provides support for the GSR7 features GPRS Seamless Cell Reselection, Enhanced
Scheduling, and PBCCH/PCCCH.
Feature description
Performance Enhancements Under Load is a combination of five sub-features:

Cell Partitioning
Delayed Downlink TBF Release Duration as a function of Cell Availability
Configurable Delayed Uplink TBF Release Duration
Configurable Initial Downlink and Uplink Coding Scheme
Scheduling algorithm Beta 0 and 2
Cell Partitioning
In GSR7, Packet Resource Processor (PRP) capacity and data traffic are increased in the
Enhanced Scheduling feature, and Seamless Cell Reselection between PRP boards introduces a
new data through the PCI backplane of the PCU.
Cell Partitioning is a software modification that reduces backplane traffic to prevent system
overload. It places the critical data for maintaining the synchronous radio link within a single
slot, and passes the larger more efficient Gb packets over the backplane.
The software processes that work with the TRAU data are repartitioned. The packetization
process is relocated to the PRP and is merged into the scheduling process to facilitate data
transfer with low overhead. The TRAU type GDS is equipped on a PRP board, and data path
latency is minimized. Processor overhead of the messages on the bus is reduced, and the
recovered CPU time is used for scheduling or increased capacity.
Delayed Downlink TBF Release (DDTR) duration as a function of Cell Availability
The GSR6 feature RDB4253 Interleaving TBFs introduced the parameter delay_dl_rel_dur to
set the downlink Temporary Block Flow (TBF) release duration.
As the number of simultaneous calls in a GPRS cell increases, a large percentage of mobiles
with assigned downlink resources are in delayed downlink TBF release mode with no actual
downlink traffic. The PCU scheduler assigns up to a maximum of four mobiles per PDCH,
and any additional mobiles requesting allocation are blocked until an existing TBF ends. The
longer the delayed downlink TBF release duration, the greater the possibility of new mobiles
requesting access in a cell being blocked. Mobiles in delayed downlink TBF release mode for an
extended period can be terminated, but this takes at least 500 msec (or T3193 period).
68P02901W01-S 4-83
Jul 2008
Seamless cell reselection Chapter 4: BSS Software Release Features
To reduce the possibility of mobiles being blocked, the scheduler in the PCU monitors the
availability of timeslot resources in the cell, and terminates downlink TBFs in delayed
downlink release mode before the cell is blocked. The maximum duration is determined by the
delay_dl_rel_dur parameter and ranges from 300 msecs to 10 seconds, with a typical value of
1 second.
Cell availability is calculated and monitored when timeslot resources that take a mobile from
idle to transfer state are assigned, and when release procedures are initiated that returns the
mobile to idle state. If the availability is less than the threshold, the scheduler selects one or
more downlink TBFs in delayed release mode to terminate. The criteria for termination of TBFs
comprise no uplink TBF in progress and a duration of at least 300 msecs in delayed release mode.
The downlink TBF establishment duration is minimized if a Packet Downlink Assignment is sent
on the PACCH while uplink TBF is in progress.
If no downlink TBF exists for a mobile while releasing the uplink TBF, the uplink TBF can be
extended by delaying the final PUAK by a configurable number of block periods.
Configurable Initial Coding Scheme
Before GSR7, all downlink and uplink TBFs used Coding Scheme 2 (CS-2). This feature enables
the initial downlink coding scheme to be set to improve throughput of cells in which all the
mobiles are capable of higher coding schemes.
The initial coding scheme is only set for TBFs with local Temporary Logical Link Identities
(TLLIs). Coding Scheme-2 is used for TBFs with non-local TLLIs, and when the carrier or PDCHs
assigned for the TBFs are not capable of the initial coding scheme CS-3 or CS-4.
The TLLI Block Coding Scheme in one-phase uplink TBFs is always set to CS-1 to ensure that
the contention is resolved quickly.
Scheduling Algorithm Beta 0 and 2
This parameter determines the extent of system efficiency against fairness among the users.
Share of throughput for each user is determined by using the current coding scheme (CS)
information, to allocate the available bandwidth among the active users with established TBFs.
The scheduling algorithm Beta gprs_sched_beta parameter introduced in the GSR6

Interleaving TBFs feature only supports the value 1, that is, each mobile is assigned to transfer
the same number of radio blocks as every other mobile. This feature adds the following values:
0 Each mobile throughput is the same. This allocates radio blocks so that each mobile
has the same throughput in bits per second (bps), thus providing maximum fairness to all
mobiles.
2 This favors mobiles with higher coding scheme, providing maximum overall throughput.
Seamless cell reselection
Feature overview
GPRS cell reselection offers mobility and performs network traffic management. The Seamless
cell reselection is performed with minimal data loss capability.
4-84 68P02901W01-S
Jul 2008
System Information: GSM Overview DSW/DSWX backward compatible with KSW/KSWX
Feature description
The term seamless cell reselection implies the completion of a cell change procedure at the
RLC/MAC layer in a controlled manner so that the higher layers do not notice the effect.
Seamless cell reselection is proposed to help Transmission Control Protocol (TCP) during cell
reselection. Cell reselection is performed with a minimal data loss capability, because no
segments need to be retransmitted and the TCP does not even notice that a cell reselection
is performed underneath.
DSW/DSWX backward compatible with KSW/KSWX
Feature overview
The DSW/DSWX are replacements to the KSW/KSWX and are backwards compatible with the
KSW/KSWX in the GSR7 loadline. The DSW/DSWX can therefore be deployed into an existing
site without any configuration changes.
68P02901W01-S 4-85
Jul 2008
DSW/DSWX backward compatible with KSW/KSWX Chapter 4: BSS Software Release Features
Feature description
The DSWX board is an enhanced version of the KSWX board that allows expansion and extension
to other cages. The operator is not required to specify the difference between the KSW and
the DSW device. The existing KSW device can be equipped and either KSW hardware or DSW
hardware can be deployed.
The DSW can be used as a replacement to the KSW and upgrades to the DSW hardware is
gradual so a mixture of KSW and DSW is likely to be required. A KSW board and DSW board can
co-exist within one cage, one acting as the slave and the other as primary switch. This will allow
the operator to change the slave KSWs that make up the redundant TDM highway to DSWs,
swap the primary and redundant highways to allow the DSW features and then replace the
KSWs that now make up the redundant TDM highway. Mixing KSWXs and DSWXs can occur in
the same cage as the DSWX acts as a KSWX and operates in single rate mode.
NOTE
Pairing a KSWX and DSWX together through fiber is not possible since the TDM fiber
data streams are incompatible.
Enhanced Capacity Mode (ECM)
ECM is configured on the new Double Kiloport Switch (DSW) and Double Kiloport Switch
(Extended) (DSWX). This allows timeslots for a double rate TDM bus (clocked at twice the rate
of a single-rate bus) to have the bit rate reduced so that the timing of the signals within the cage
is appropriate for existing boards; for example, MSI, XCDR, GDP, GPROC2 which do not support
the double-capacity mode. GDP2s can therefore occupy the same cages as these existing boards.
In order to use the GDP board as a 60-channel, two span line transcoder card and the following
changes to the system are required:
Use of 2048 timeslot mode (no KSW or KSWX used).
All RXU cages that are planned to house GDP2 boards are to be replaced with (Next
Generation) ngRXU cages.
All local transcoding BSC and RXCDR BSSC cabinets housing GDP2 boards are to be
replaced with (Next Generation) ngBSSC cabinets.
It is possible, however, for the GDP2 to operate as a 30-channel, one span line transcoder card
as a replacement to the GDP board and is capable of processing an AMR calls if the feature is
unrestricted. It can therefore be positioned in a regular RXU cage within a regular BSSC cabinet.
Double Kiloport Switch (DSW/DSWX)
The DSW/DSWX is an enhanced version of the KSW/KSWX to support double the number of
ports and extended sub-rate switching down to 8 kbps (single bit). To achieve double rate the
TDM bus bandwidth is increased to 128 Mbps divided into 2048 timeslots.
4-86 68P02901W01-S
Jul 2008
System Information: GSM Overview Adaptive Multi-Rate (AMR)
Adaptive Multi-Rate (AMR)
Feature overview
The AMR feature set provides improvements in system capacity and speech quality. The AMR
speech codec includes a set of fixed rate speech codec modes for full rate (FR) and half rate
(HR.) operations, with the ability to switch between the different channel coding modes as a
function of the propagation error conditions. An AMR HR for speech gives enhanced capacity
over the air interface and speech quality using codec mode adaptation. This requires selecting
the optimum channel (HR or FR) and codec mode (speech and channel bit rates) to deliver the
best combination of speech quality and system capacity.
An AMR HR call can occupy an 8 kbps timeslot (an Ater channel) on the terrestrial resource
from the BSC to the RXCDR, rather than the 16 kbps timeslot required for FR calls. If a
percentage of the active calls can be assumed to be HR, then efficiency can be gained by
reducing the number of terrestrial resources between the BSC and RXCDR. This is possible
only if the BSC can dynamically allocate a timeslot to a CIC. This allocation is performed across
the Ater interface and is considered to be an enhancement to the existing Auto Connect mode,
referred to as Enhanced Auto Connect or EAC mode.
NOTE
If the 7.95 kbps codec mode is included in the HR AMR Codec Set (ACS), a 16 kbps
timeslot is always required.
The initial AMR release supports the FR, HR, and link adaptation features on Horizonmacro
cabinets with CTU radio platforms. In this release, the AMR feature is available on the CTU,
TCU-A and TCU-B radio platforms.
68P02901W01-S 4-87
Jul 2008
Adaptive Multi-Rate (AMR) Chapter 4: BSS Software Release Features
Feature description
The AMR feature set can be divided into four component parts as follows:
Full-rate channel mode
Link adaptation (full-rate)
Half-rate channel mode
Link adaptation (half-rate)
AMR full-rate channel mode
The AMR full-rate channel is a full-rate channel that employs an AMR speech codec to provide
higher speech quality in areas of poor RF conditions. Full rate channels achieve improved
call speech quality at the expense of the increased cell capacity offered by half rate. Calls
designated as half rate is transferred to a full rate carrier if the speech quality of the call
is impaired by interference and the necessary resources are available. Conversely, if cell
congestion exceeds a preset threshold, full rate calls is reassigned to half rate to release extra
traffic channels, provided the cell RTFs are enabled as half rate capable.
Full-rate AMR link adaptation
Full-rate AMR link adaptation provides the mechanism for the BSS to adapt between
speech codec modes, in an AMR codec on the uplink and downlink of an AMR full-rate call.
This adaptation mechanism provides the most suitable level of error correction for the RF
environment. Uplink and downlink codec modes are monitored separately, and can be adapted
separately. With full-rate link adaptation, up to four codec modes can be placed in the per cell
Full-Rate Active Codec Set (FR ACS). Calls are adapted over this active codec set, according to
the quality of the link between the MS and the BSS.
The full-rate Adaptive Full-Speech (AFS) codec modes supported are as follows:
12.2 kbps
10.2 kbps
7.4 kbps
6.7 kbps
5.15 kbps
The higher the bit rate of the codec mode, the higher the speech rate and lower the error
correction rate. Up to 4 of these codec modes can be included in the FR ACS.
AMR half-rate channel mode
The AMR half-rate channel mode allows two AMR calls to be placed on a single air interface
timeslot. Use of the AMR half-rate channel mode increases cell capacity, without the need for
extra radio hardware. The cost of the increase in cell capacity with this release of the AMR
half-rate channel mode is the need for the provisioning of extra backhaul between the BSC and
BTS and the lower quality of service provided by AMR half-rate calls.
The BSS software allows the AMR half-rate channel mode to be enabled and disabled on a
per cell basis. Specific RTFs within a cell can be configured based on AMR half-rate channel
mode capability. Half-rate enabled RTFs are allocated an additional two E1 timeslots between
the BSC and BTS. Extra timeslot allocation is necessary if the BSC does not support 8 kbps
4-88 68P02901W01-S
Jul 2008
System Information: GSM Overview Adaptive Multi-Rate (AMR)
switching, so AMR half-rate call speech data must be carried in 16 kbps TRAU format between
the BSC and BTS. If DSW/DSWXs are used at the BSC 8 kbps switching is supported and 8
kbps backhaul can be used.
Given that, potentially, 16 AMR half-rate calls can be supported on an AMR half-rate carrier. An
AMR half-rate RTF must have four associated E1 timeslots provisioned between the BSC and
BTS. Due to reduced bandwidth, an AMR half-rate call has, in general, a lower perceived Quality
of Service (QoS) than a full-rate call. For this reason, a per cell database threshold is provided
to allow the operator to specify the level of congestion that must exceed in an AMR half-rate
capable cell before new calls can be assigned to half-rate traffic channels.
When the received Bit Error Rate (BER) rxqual indicates that a half-rate channel is suffering
interference and that the speech quality of the call is therefore impaired, an intra-cell handovers
back to full-rate (or to another half-rate channel) is supported to maintain quality of service.
Alternatively, a database parameter is set in order to override any MSC channel rate preference,
if given, and the cell's congestion threshold, causing AMR calls to be assigned directly to
half-rate channels. This allows temporary forcing (from the OMC) of half-rate usage during busy
periods. Intra-cell handovers for quality reasons from half-rate are still permitted when the
override flag is set, but the target resource for the intra-cell handover is forced to half-rate.
In addition to the ability to specify that new half-rate capable calls be assigned to half-rate traffic
channels when cell congestion exceeds the threshold, a second (or alternative) congestion
threshold can be specified. When this congestion threshold is exceeded in an AMR half-rate
channel mode cell, the BSS reassigns half-rate capable full-rate calls to half-rate traffic channels.
NOTE
Intra-cell handovers from full rate to half rate are not allowed.
Half-rate AMR link adaptation
Half-rate AMR link adaptation provides similar functionality to full-rate AMR link adaptation for
the half-rate AMR channel.
In half-rate AMR link adaptation there is a different half-rate ACS. This ACS can contain up to
four of the half-rate AMR codec modes that are supported. The half-rate Adaptive Half-rate
Speech (AHS) codec modes supported are:
7.95 kbps
7.4 kbps
6.7 kbps
5.9 kbps
5.15 kbps
There are different half-rate initial codec mode and associated uplink and downlink codec mode
adaptation thresholds and hysteresis values for half-rate AMR calls.
The existing GSM handover and power control algorithms are still used for the half-rate AMR
channel but, similar to full-rate link adaptation, a new set of handover and power control
thresholds are introduced. The new half-rate AMR handover and power control rxqual
thresholds are different to the full-rate AMR handover and power control thresholds because
the half-rate channel displays different characteristics to a full-rate AMR channel. For these
68P02901W01-S 4-89
Jul 2008
Move PCU and BTS objects from BSP Chapter 4: BSS Software Release Features
reasons handover and power control algorithms are configured in a different manner to cater
for the half-rate AMR channel. The MS Monitor introduced in full-rate AMR link adaptation
also applies to half-rate AMR calls.
Move PCU and BTS objects from BSP
Feature Overview
This feature reduces the code object sizes. It also enables smart management of the location of
code objects for the Base Site Processor (BSP).
Feature description
The BSP is near capacity and will exceed the physical memory available (32 MBs) with the
addition of the GSR6.1 and GSR7 GPRS features, H2, and AMR. To relieve the situation this
feature performs the following actions:
Removes the BTS and PCU objects from the BSP.
Optimizes PCU objects.
Optimizes compilers.
BTS and PCU objects removal from BSP
The BSC no longer stores the BTS and PCU objects on the BSP. These objects are stored on
other GPROCs within the BSC. Initialization Process (IP), Central Authority (CA) and the Code
Object Manager (COM) are modified to remove these objects at the initialization time of a BSP.
The BTS and PCU objects are loaded from other GPROCs, such as a Link Control Processor
(LCP) within the BSC.
NOTE
Type 0 BSC is no longer supported, therefore there must be at least a BSP and an
LCP at a BSC.
The network entity affected is the BSC only; all changes are confined to the BSC.
Predicted memory saving is 7.5 MBs on the BSP.
PCU objects optimizations
This sub-feature optimizes the way that PCU objects for the DPROC and MPROC are built
and initialized. Memory saving is gained by removing duplicated EXEC and PCM code from
the MPROC and DPROC objects and creating a single new object for each. A copy of each
object is then loaded on to both the MPROC and the DPROC after it is downloaded to the
PCU from the BSC.
The network entities affected are:
4-90 68P02901W01-S
Jul 2008
System Information: GSM Overview GPRS PBCCH/PCCCH support
PCU - These objects are loaded and initialized differently.
BSC - 2 new objects to store and download to the PCU, resulting in memory savings.
Predicted memory saving is 600 kbytes on the LCP boards storing the PCU objects.
Compiler optimizations
Compiler optimizations are updated to remove unused source level debugging information from
objects built for the BSC and BTS. Other compiler options to optimize for space utilization
versus performance are made for specific processes that do not require performance.
The network entities affected are the BSC or BTS, so that all objects are smaller and built using
compiler options that are appropriate for the function of the object or process.
Predicted memory saving is 1.5 MBs on all GPROC boards.
GPRS PBCCH/PCCCH support
Feature overview
The PBCCH/PCCCH feature (RDB 3723) is a software-only feature that introduces support for
the Packet Common Control Channels (PCCCH) and Packet Broadcast Control Channel (PBCCH)
to the Motorola BSS. The PCCCH consists of the following logical channels for common control
signaling used for GPRS:
PRACH (Packet Random Access CHannel)
PAGCH (Packet Access Grant CHannel)
PPCH (Packet Paging CHannel)
PNCH (Packet Notification CHannel)

PBCCH broadcasts packet data-specific System Information. If PBCCH is not allocated, the
packet data-specific system information is broadcast on BCCH (Broadcast Control Channel).
The MS uses PRACH to initiate uplink transfer for sending data or signaling information.
PAGCH is used in the packet transfer establishment phase to send resource assignment to the
MS before packet transfer. PPCH is used to page the MS before downlink packet transfer.
PPCH can be used for paging of both circuit switched and packet data services. The paging
for circuit switched services on PPCH is applicable for class A and B GPRS mobiles in NMO I
(paging co-ordination using the Gs interface).
PNCH is used to send a PTM-M (Point To Multipoint - Multicast) notification to a group of

MSs before a PTM-M packet transfer. PTM-M will not be supported, so the PNCH will not be
supported in this feature.
Previous to this feature, the Motorola BSS provided the functions of all these logical channels
using the CCCH. Therefore, GPRS-capable MSs served by a Motorola BSS would camp on
the CCCH. With this feature, GPRS-capable MSs served by a Motorola BSS will camp on the
PCCCH and use the PCCCH channels instead.
PBCCH/PCCCH are the packet data logical channels dedicated for GPRS signaling. With
PBCCH/PCCCH configured in a cell, MS reads system information on PBCCH and perform
packet access activities on PCCCH. Table 4-32 shows the functionality of each packet logical
channels on PBCCH/PCCCH.
68P02901W01-S 4-91
Jul 2008
Enhanced GPRS (EGPRS) Chapter 4: BSS Software Release Features
Table 4-32 PBCCH/PCCCH packet logical channels
Packet logical channels Packet Transfer Direction Functionality

PRACH (PCCCH) Uplink only Used by MS to initiate uplink
transfer for data or signaling
information.
PAGCH (PCCCH) Downlink only Used by BSS to send
resource assignment to the
MS before packet transfer.
PPCH (PCCCH) Downlink only Used by BSS to page a

mobile for PS and CS.
PBCCH Downlink only Used by BSS to broadcast
packet data-specific System
Information.
PNCH Not supported for the feature
Without PBCCH/PCCCH configured in a cell, GPRS-related information is broadcasted on BCCH

and GPRS accessing signaling is conducted on CCCH channels.
Enhanced GPRS (EGPRS)
Feature overview
The EGPRS feature is an extension to the software architecture introduced by the General
Packet Radio Service (GPRS) feature and the Coding Scheme 3 or Coding Scheme 4 feature. This
means that a network supporting EGPRS also provides support for GSM voice and GPRS data.
EGPRS employs a new set of GSM modulation and channel coding techniques that increase a
user's packet data throughput from a maximum of 21.4 kbps per air timeslot with GPRS to
a maximum of 59.2 kbps per air timeslot with EGPRS. The maximum data throughput for a
multi-slot mobile utilizing all eight air timeslots with EGPRS is 473.6 kbps compared to 171.2
kbps in GPRS.
Operational requirements
The BSS is compliant with the 3GPP R99 December 2002 version of the standards on the air and
Gb interfaces.
EDGE standards
EDGE standards define enhancements to both General Packet Radio Services (referred to as
EGPRS) and High Speed Circuit Switched Data (referred to as ECSD). Software release GSR7
only provides support for the EGPRS portion of EDGE; support for ECSD is not provided.
Throughout this manual and in the set of manuals accompanying this manual, reference is
therefore made only to EGPRS.
4-92 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced GPRS (EGPRS)
Feature description
The initial release of EGPRS provides support for a multi-slot mobile using four air timeslots.
Support for the mobile classes, which dictate the multi-slot capabilities of a mobile, are the same
for EGPRS as in GPRS (classes 1 - 12). Although a large portion of the EGPRS impact to the BSS
software is focused on the air interface, impacts also exist on the terrestrial interfaces to carry
the large volume of data traffic produced by these new data rates.
The 3GPP specification refers to two modes of operation for EGPRS, Classic and Compact. Only
the Classic mode of operation is supported for EGPRS. References to Compact mode are no
longer applicable in the standards and therefore they are not supported.
An EGPRS system encompasses changes to the existing GPRS BSS to support the higher data
rates that EGPRS provides.
68P02901W01-S 4-93
Jul 2008
BSS software release GSR7 (GSM Half Rate) Chapter 4: BSS Software Release Features
BSS software release GSR7 (GSM Half Rate)

GSR7 (GSM Half Rate) features
Table 4-33 summarizes the BSS features provided at software release GSR7 (GSM Half Rate).
Table 4-33 Release GSR7 (GSM Half Rate) features
Description
GSM Half Rate
GSM Half Rate
Feature overview
The GSM Half Rate (GSM-HR) feature provides enhanced capacity over the air interface. An air
timeslot is split into two sub-channels, each containing a GSM-HR channel.
A GSM-HR call can fit within an 8 kbps timeslot (an Ater channel) on the terrestrial resource
from the BSC to the RXCDR, rather than the 16 kbps timeslot required for FR calls. If a
percentage of the active calls is HR, then efficiency can be gained by reducing the number
of terrestrial resources between the BSC and RXCDR. This is possible only if the BSC can
dynamically allocate a timeslot to a CIC on an 8 kbps/16 kbps basis. This dynamic allocation is
performed across a trunked interface between the BSC and an RXCDR, the Ater interface. The
dynamic allocation is an enhancement to the existing Auto Connect mode feature, Enhanced
Auto Connect mode. Enhanced Auto Connect is part of the AMR feature and is mentioned here
only to point out that GSM-HR will enjoy the same benefit.
The backhaul between the BTS and BSC is 8 kbps or 16 kbps. 8 kbps requires that subrate
(8K) switching is present at the BSC.
GSM-HR interacts with EGPRS in the same manner as AMR-HR.
4-94 68P02901W01-S
Jul 2008

Description
Stop BTS transmission after the last RSL fails
GPRS resources (PDTCH) configured
Out_inter_bss_ho statistical counter
Support for CGI for Inter PLMN
BSC Reset Management
Intelligent multi-layer resource management for voice
GPRS Trace
New GPRS alarms
GPRS Statistics and enhancements
NACC Network Assisted Cell Change
Enhanced 2G-3G handover
VersaTRAU
Support of QoS Release 99 (was 22889)
Support for Horizon II Mini
GPRS R4 Compatibility
eMLPP
Support for Half Rate on GDP2
Fast Call Setup
RSL Congestion Control
Increased SDCCH capacity
Improved Timeslot Sharing (ITS)
68P02901W01-S 4-95
Jul 2008
Stop BTS transmission after the last RSL fails Chapter 4: BSS Software Release Features
Stop BTS transmission after the last RSL fails
Feature Description
This feature stops DRIs transmission when the CELL, they are in, goes out of service (OOS) for a
specified period of time. The DRIs start transmitting again when the CELL returns to service
(INS). This feature can be enabled or disabled per BSS in SYSGEN mode.
New CM attributes support this feature:

A BSS-wide switch to enable or disable functionality.
A cell timer, which provides flexibility on how long the DRIs continue transmitting after
the cell they are in has gone out of service. It can be used to prevent DRIs ceasing
transmission for short cell outages.
New reasons are included in state change events sent by the BSS to the OMC-R. The text for
each reason is coded by BSS in a rsn file that is loaded on the OMC-R. It activated when its
associated BSS load is activated at the BSS. No additional OMC-R functionality is required
to support these new state change reasons.
GPRS resources (PDTCH) configured
Feature Description
This feature displays the static configuration of PDTCHs on a PCU and cells mapping on a PRP
DPROC at the BSC using the disp_equipment command. OMC-R and MMI statistics monitor the
demand of PDTCHs and GCIs on a PRP DPROC.
The BSS issues a rejection message if more PDTCHs are required that can be handled by the
RTFs or PRPs on the PCU. A warning message is printed if insufficient PMC or GDS resources
are available.
The PDTCH demand statistics include:

PRP_PD_DEMAND: This statistic indicates the number of PDTCHs demanded on a PRP
DPROC.
GCI_FOR_64KPD_DEMAND, GCI_FOR_32KPD_DEMAND, GCI_FOR_16KPD_DEMAND,

TOTAL_GCI_FOR_PD_DEMAND: These statistics indicate the mean and maximum number
of GCIs demanded for 64k, 32k, 16k, or all PDTCHs on a PRP DPROC.
The statistics only count the PRP PDTCHs or GCIs demanded on cells that are dynamically
mapped on a PRP DPROC. If a cell is unmapped to a PRP DPROC or out of service, alarms are
generated to indicate the problem.
4-96 68P02901W01-S
Jul 2008
System Information: GSM Overview Out_inter_bss_ho statistical counter
Out_inter_bss_ho statistical counter
Feature Description
This feature improves the OUT_INTER_BSS_HO statistic pegging so that the global statistic
DROP_CALLS can be calculated accurately. The OUT_INTER_BSS_HO statistic has seven bins:
OUT_INTER_BSS_REQ_TO_MSC
OUT_INTER_BSS_HO_ATMPT
OUT_INTER_BSS_HO_SUC
OUT_INTER_BSS_HO_LOSTMS
OUT_INTER_BSS_HO_RETURN
OUT_INTER_BSS_EQUIP_FAIL
OUT_INTER_BSS_HO_CLEARED
NOTE
Some of these are included in DROP_CALLS formula and are pegged incorrectly, This
results in DROP_CALLS being calculated incorrectly. Pegging method for some bins
are improved in this enhancement feature.
68P02901W01-S 4-97
Jul 2008
BSS support for full Cell ID Chapter 4: BSS Software Release Features
BSS support for full Cell ID
Feature Description
This feature causes both the OMC and BSS to send the full GSM Cell ID (MCC, MNC, LAC, CI)
when transmitting the cell information over the OMC-BSS interface.
The GSM Cell ID is a unique identifier that identifies the cell within a network. GSM Cell ID
consists of four identifiers:
Mobile Country Code (MCC)
Mobile Network Code (MNC)
Location Area Code (LAC)
Cell Identity (CI)
GSM standard specifications requires that the GSM Cell ID is unique for all cells within the
world.
Because cells could exist in a BSS with the same LAC and CI, but having different MCC and/or
MNC, the LAC and CI is not sufficient to uniquely identify a Cell in a BSS to the OMC. The
GSM Cell ID feature overcomes this by sending the full GSM Cell ID (MCC, MNC, LAC, CI)
when transmitting cell information.
With the addition of UTRAN neighbors as a result of the Inter RAT handover feature (RDB4225)
it is possible for GSM cells to have 3G external neighbors. The BSS database allows the
provisioning of UTRAN cells to be specified as neighbors of existing GSM cells.
In the case of a UTRAN neighbor of a GSM cell, it is essential that the OMC-BSS interface
supports full UTRAN Cell IDs. Both OMC and BSS sends full Cell ID over the OMC-BSS interface.
BSC Reset Management
Feature Description
The BSC reset management feature introduces the capability to swap between active and
standby BSPs when the master BSP GPROC fails. The BSP recovers the most useful information
automatically (instead of users restoring it manually), and a greater amount of diagnostic
data is collected for analysis.
Deploying this feature:

Decreases the BSC outage time from about 10~20 minutes to about 2 minutes.
Provides more BSC diagnostic data (such as timing, time-outs, measurements of common
factors, system utilization) for great error handling control and understanding of fault
diagnostic.
Provides the capability of preserving device and function unit states before the BSP
switchover.
Provides the capability of preserving the alarm history before the BSP switchover.
4-98 68P02901W01-S
Jul 2008
System Information: GSM Overview BSC Reset Management
After switchover, the BSC initiates a global reset to ensure that the MSC/RXCDR/BSC or BTS
gets status synchronized. For the PCU, the BSC achieves this by disabling and re-enabling all
the GSLs in service. This leads to all the established calls (data and voice) being dropped.
NOTE
The third BSP reset, regardless of the reasons, within a 30 minute period will cause
the BSC to do a complete reset. Thus deploying this feature:
Drops the stable calls established before the BSP switchover.
Drops stable GPRS sessions established before the BSP switchover.
The statistics collected before the BSP switchover on the master BSP are lost. In addition,
if the BSC is type 1, the BSC fails to collect the statistics during BSP switchover.
If this feature is deployed, the impacts on the current BSS system are:
CBC The CBL is managed by an LCP (GPROC with LCF function), so it is kept INS during
BSP switchover. However, the BSC does not send any service request to the CBC during
the BSP switchover.
RXCDR (when the BSC is configured with remote transcoders) Includes two cases:
For type 1 BSC, the XBL links are managed by the BSP, and are OOS when the
master BSP fails. The RXCDR connected with this BSC experiences the loss of XBL
links to the BSC during the BSP switchover. After the BSC switchover, the XBL links
are recovered at the RXCDR, and a global reset is performed at the RXCDR along
with the BSC and BTSs.
For type 2 BSC, the XBL links are managed by OMP (GPROC with OMF) and they
are kept INS during switchover. After BSP switchover, the RXCDR performs a global
reset along with the BSC and BTSs.
OMC-R Includes two cases:

For type 1 BSC, the OML links are managed by the master BSP and are OOS when
the master BSP fails. The OMC-R connected with this BSC experiences the loss of
OML links to the BSC during the BSP switchover. After the BSC switchover, the
OML links are recovered at the OMC-R.
For type 2 BSC, the OML links are managed by OMP (GPROC with OMF) and are kept
INS during switchover. The OMC-R is not impacted.
MSC The MTLs are managed by an LCP (GPROC with LCF function) and are kept INS
during BSP switchover. After BSP switchover, the associated MSC is requested to perform
a global reset to release the affected calls and put the associated circuits into idle state.
BTS The RSLs are managed by an LCP and they are kept during BSP switchover. After
BSP switchover, all the associated BTSs are requested to perform a global reset to clear
calls and release the related resources.
GPRS - The BSC disables the GSLs in service and then re-enables those GSLs in order to
clear the data calls established before the BSP switchover, and release related resources.
68P02901W01-S 4-99
Jul 2008
Intelligent Multi Layer Resource Management (IMRM) Chapter 4: BSS Software Release Features
Intelligent Multi Layer Resource Management (IMRM)
IMRM allows users to better match overall traffic distribution to intrinsic network capacity and
MS penetration. By supporting, on a per cell basis, weightings for each of the available bands,
the system can effect a more dynamic distribution based on factors such as:
Local (cell) per band capacity
Neighbor (For example, micro underlay, macro overlay) per band capacity
Mobile Capability penetration for example, Multiband vs Single Band
Congestion Management that is, half rate management
Other System Considerations for example, GPRS capacity

The Layer Weightings supported are:
PGSM
EGSM
DCS1800
UMTS
The individual layer weightings are dynamically combined with a requesting MS capabilities to
define a set of probabilities for each of the supported layers; a random selection based on these
probabilities then effects the traffic distribution. The higher the layer weighting the higher the
probability and hence more likely selection. Setting any layer weighting to the maximum defined
value results in a fixed (to that layer) preference selection as per existing ALM procedures.
The default for all available layers is set to Unsupported. Where, IMRM is enabled in a cell with
all layers set to Unsupported, the system applies a set of fixed internal defaults for input into
the Preference Selection Algorithm. The system supports 2 sets of defaults with selection
based on local EGSM availability.
Table 4-35 Default Band Weightings
EGSM
PGSM EGSM DCS1800 PCS850 PCS1900 GSM450 UMTS
Support
Yes 45 10 45 N/A N/A N/A 0
No 50 0 50 N/A N/A N/A 0
4-100 68P02901W01-S
Jul 2008
System Information: GSM Overview GPRS Trace
The Preference Selection Algorithm is run for each initial network resource request
(Assignment and incoming External Handover) and is used in conjunction with the existing
band_preference_mode parameter to determine both initial resource targeting and also any
subsequent handover activity. The selected preference is then retained or utilized for the call
while it remains within the current BSS. There are situations whereby the Preference Selection
Algorithm can be re-run for existing calls, either due to system operation and/or operator
control as follows:
Intra-BSS hand-in from non-IMRM Source to IMRM Target.
Intra-BSS hand-in from IMRM Source with a locally unsupported Preference.
Intra-BSS hand-in to an IMRM Target with (configured) Forced Recalculation of Preference.

New statistics have been introduced to allow tracking of cell availability and utilization on a
per layer basis.
GPRS Trace
Feature Description
The GPRS Trace feature is an extension of the existing GSM Call Trace implementation. The
GPRS Trace feature enables the user to trace information on GPRS MSs. It provides similar
functionality to GSM Call Trace.
GPRS Trace differs from GSM Call Trace in the following respects:
GPRS signaling is more frequent due to the bursty packet nature of GPRS data transfers.
GPRS MSs may leave a cell without informing the BSS. Therefore, the continue beyond
scope option is not applicable in GPRS Trace. However, for ease of implementation, a
continue beyond scope value is always included in the trace Create action. This value is
ignored by the BSS, if the trace type is GPRS.
For GPRS Trace, the lifetime of an invoked trace will correspond to the lifetime of a GPRS
MS meeting the GPRS Trace criteria within a PCU. A number of GPRS data transfers
may occur within this period. Due to cell reselection, a GPRS MS may leave the scope of
the criteria and/or the PCU without prior warning. When the PCU detects that a GPRS
MS has left, the invoked trace ends. Since cell reselection can take up to 15 seconds,
the PCU waits 15 seconds for the MS to reappear before ending the invoked trace. This
differs from GSM Call Trace, where the lifetime of an invoked trace (and corresponding log
file) corresponds to a single call.
GPRS Trace is created and managed from the OMC and BSS MMI only.
NOTE
Unlike GSM Call Trace, creation of GPRS Trace criteria is not supported from
the MSC. Also, in this release, GPRS Trace Records will not be forwarded to
the NMC.
The GPRS trace create criteria includes:
68P02901W01-S 4-101
Jul 2008
GPRS Trace Chapter 4: BSS Software Release Features
Trace scope options for GPRS Trace: BSS, site, Cell, RTF (as for GSM).
Trace selector options for GPRS Trace: IMSI (International Mobile Subscriber Identity),
TLLI (Temporary Logical Link Identity), Nth GPRS MS.
Trace selector options for GPRS Trace: IMSI (International Mobile Subscriber Identity),
TLLI (Temporary Logical Link Identity), Nth GPRS MS.
GPRS Trace Record type: Basic or Radio. If Radio is selected, the user may select some or
all of the following:
LLC (Logical Link Control) information.
BSSGP (BSS GPRS protocol) messages.
RLC/MAC (Radio link control/Medium Access Control) messages:

GPRS Power Control and Coding Scheme, including UL/DL measurement data.
Packet Measurement Reports.
Every RLC/MAC PDAK.
Trace start/stop times.
Total number of GPRS MSs to be traced.
NOTE
This information is counted per-PRP. The trace criteria are complete at the BSS,
when the total numbers of MSs have been traced for at least one PRP. The
overall number of MSs traced during this period may exceed the total number
setting. This behavior is similar to the counting of Total number of calls at the
LCF level for Call Trace.
Measurement interval: This value applies for Packet Measurement Reports and UL/DL
Measurement data.
Maximum number of simultaneous MSs to be traced (applicable only if Trace selector

is set to Nth GPRS MS).
NOTE
This information is counted per-PRP. Therefore, the number of simultaneous
calls at any specific time may exceed the maximum number setting.
Users may request a combined trace of both GSM and GPRS information in the specific case
of an IMSI trace selector. In this case, the BSS forwards trace records relating to both GSM
calls and GPRS data transfers for that IMSI. GSM and GPRS trace information are written
to separate log files.
4-102 68P02901W01-S
Jul 2008
System Information: GSM Overview New GPRS alarms
New GPRS alarms
Feature Description
The following new alarms are introduced at the BSS:

GPRS Unavailable, EGPRS Unavailable
The BSS detects when GPRS (or EGPRS) becomes unavailable and there is no other GPRS
Unavailable alarm raised. On arrival of this alarm, an attempt to toggle GPRS/EGPRS is
made to correct the problem. The alarm is cleared if GPRS becomes available again. GPRS
toggling is not attempted for existing GPRS unavailable alarms.
All PDs OOS
The BSS detects when all PDs on a GDS go out of sync and there is no associated
MSI/MMS alarm.
68P02901W01-S 4-103
Jul 2008
GPRS Statistics and enhancements Chapter 4: BSS Software Release Features
NSVC Failure
The NSVC failure alarm is reported upon the first NSVC failure on a GBL. It indicates one
or more NSVCs have failed. The alarm is cleared when all NSVCs have come into service.
The 50% NSVC Failure alarm is deleted as it is no longer needed with the addition of
the NSVC failure alarm.
GPRS Statistics and enhancements
Feature Description
This feature introduces statistics to measure the performance of the GPRS/BSS system. The
new statistics provide accurate information about the use of system resources, the quality of
data transfer, the traffic at different GPRS protocol levels, and load distribution.
These statistics enable users to adjust the system configuration to enhance the performance
of the system.
The new GPRS statistics are split into the following six categories based on the different aspects
of the system performance to which the collected statistics data contribute.
Packet Congestion
BLER
Packet Loss (LLC Frame Loss)
LLC Traffic Reports
Paging Load
Miscellaneous
Network Assisted Cell Change (NACC)
Feature Description
The Network Assisted Cell Change feature improves GPRS performance by reducing delays in
the cell reselection process. It overcomes the potential problem of the MS selecting a congested
target cell, or that the cell may have GPRS/EGPRS disabled. Network Assisted Cell Change
consists of two independent procedures. The first procedure allows the MS to indicate to the
network the need for a cell change. In the second procedure, the network provides neighbor
cell data to the MS.
Network Assisted Cell Change consists of two independent procedures:

PCCN procedure - this assists a mobile station in packet transfer mode with neighbor cell
system information required for initial packet access after a cell change. The mobile
station notifies the network using a Packet Cell Change Notification (PCCN) message when
a cell reselection is needed and delays the cell reselection to let the network respond with
neighbor cell system information. This procedure allows the BSS to play a part in deciding
the best target cell to which the MS should move.
4-104 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced 2G-3G handover
Neighbor Cell Data procedure - After the target cell has been determined, the network
sends the mobile station a Packet Neighbor Cell Data (PNCD) message containing the
information needed for the mobile station to access the target cell. The neighbor cell
information is sent to the MS in the source cell before the MS performs cell reselection so
that the MS can perform packet access without reading all of the system information in
the target cell.
Enhanced 2G-3G handover
Feature Description
The Enhanced 2G-3G handover and Cell Reselection feature provides support in the BSS for:
Outgoing dedicated mode handover from 2G to 3G (basic measurement based and service
based handover triggers).
BSS control for measurement reporting by multi-RAT MS.
UTRAN Classmark Enquiry.
Blind search for idle mode cell reselection from 2G to 3G.
Inter-RAT related performance measurements.
This feature allows a multi-RAT MS to perform a handover while in dedicated mode from GSM
cell to a UTRAN FDD mode cell (2G to 3G). This feature allows the BSS to support handovers
from 2G to 3G based on radio measurements and the service capability of the MS.
68P02901W01-S 4-105
Jul 2008
VersaTRAU Chapter 4: BSS Software Release Features
VersaTRAU
Feature Description
Without the feature, a GSM TDMA timeslot, containing voice or GPRS data, is framed and sent on
a 64 kbps backhaul timeslot between the BSC and a remotely located BTS site. With VersaTRAU,
both voice and GPRS/EGPRS frames are combined into one large frame, which reduces
backhaul wasted due to extra padding. Additionally, when congestion occurs on the backhaul,
GPRS/EGPRS data and control blocks are scheduled accordingly at the PCU to fit the available
backhaul, so the combined VersaTRAU frame can still be sent on a reduced backhaul link.
The VersaTRAU feature provides dynamic TRAU capability to EGPRS Carriers to optimize
backhaul usage and reduce costs to the user.
The VersaTRAU feature introduces five new per-carrier stats namely:

UL_EGPRS_BACKHAUL_USED
UL_EGPRS_BACKHAUL_DEMAND
DL_ EGPRS_BACKHAUL_USED
DL_ EGPRS_BACKHAUL_DEMAND
EGPRS_64K_CHANNEL_WIDTH
Using the above statistics the OMC provides a new utility which presents the user an analysis on
the VersaTrau performance over a period of time specified by the user. The summarized report
details the total statistics interval data considered for analysis:
Maximum and mean bytes lost over all the statistics intervals.
Mean VersaTrau bandwidth demand.
Number of intervals where the demand was less than or equal to 80% backhaul.
Number of intervals where the demand was greater than 80% and less than or equal
to 100% backhaul.
Number of intervals where the demand was greater than 100% backhaul.
This information enables users to configure DS0s effectively.
Two existing alarms CERM and GDS OOS are updated.
This feature also introduces a new RTF element namely rtf_ds0_count. This element specifies
the number of RTF backhaul timeslots allocated for a 64K carrier.
4-106 68P02901W01-S
Jul 2008
System Information: GSM Overview Support of QoS Release 4 (R4)
Support of QoS Release 4 (R4)
Feature Description
This feature provides for aggregation of similar QoS profiles into a single Packet Flow Context
(PFC) and allows the BSS to negotiate and modify QoS parameters.
The Aggregate BSS QoS Profile (ABQP) field, contained in Packet Flow Management (PFM)
signals, describes the QoS characteristics for a single PFC, identified by a Packet Flow Identifier
(PFI). The ABQP field contains a full set of QoS parameters including:
Traffic class
Traffic Handling Priority (THP)
Maximum bit rates and guaranteed bit rates for uplink/downlink
Transfer delay
Other fields describing error rate/ratio characteristics are included in the ABQP to provide a
more specific differentiation of services to users. With the added parameters contained in the
ABQP field, and the ability to negotiate and modify these QoS parameters, the BSS now provides
differentiated services to users inline with the QoS requested by the mobile, and consistent to
those offered to the mobile by the other network entities, thus providing a more consistent end
to end QoS. QoS feature is a purchasable feature in GSR8. QoS feature is available only if the
GPRS feature is purchased and the NACC feature is enabled.
68P02901W01-S 4-107
Jul 2008
Support for Horizon II Mini Chapter 4: BSS Software Release Features
Support for Horizon II Mini
Feature Description
The Horizon II mini platform is a smaller version of Horizon II macro, supporting less capacity,
and hence lesser backhaul (RTF). The OMC-R software needs to identify the Horizon II Mini
from the cabinet ID and enable the option to provision lesser number of carriers for the Horizon
II Mini cabinet. When configured in a Horizon II Mini network, the maximum number of carriers
supported by the Horizon II Mini network is limited to 16.
The Horizon II mini fills the gap in the market left by Horizon Micro2. It should be noted
however that Horizon II mini is not a direct replacement for Horizon Micro2 - there is no
upgrade path in software from micro cabinet types to Horizon II mini.
Horizon II mini has these advantages over micro platforms:

Rx Diversity
16 - 63 W Output Power (depending on frequency and configuration)
Replaceable FRUs
Common FRUs with the macro unit
Better Rx sensitivity
Better expandability
Macro performance in a micro volume
The Horizon II mini behaves as if it were a Horizon II macro cabinet. Software distinguishes
Horizon II mini cabinets from macro varieties.
The Horizon II mini supports CTU2 radios. These are operated in double density mode, that
is, four carriers are possible at a Horizon II mini cabinet. Furthermore, CTU2 supports the
EDGE feature.
The software constraints on Horizon II mini cabinets are:

Only one BTP is equipped to a Horizon II mini master cabinet.
A maximum of two physical radios is equipped to a Horizon II mini cabinet.
4-108 68P02901W01-S
Jul 2008
System Information: GSM Overview GPRS R4 Compliance
GPRS R4 Compliance
Feature Description
The GPRS R4 Compliance feature makes the BSS compliant to all mandatory aspects of the
March 2003 release of the 3GPP GERAN Release 4 standards and offers the following benefits:
Supports the packet radio functionality of R4 mobiles.
Facilitates operation of optional R4 features such as Network Assisted Cell Change (NACC).
The GPRS R4 Compliance feature is unrestricted and compliance to the mandatory aspects of
the GERAN R4 specifications is unconditional.
The main functionalities supported by the feature are:

Enable Packet PSI Status procedure in PBCCH-enabled cells - Reduces data outage time
during acquisition of system information. For example, after cell (re)selection, when the
Packet PSI Status procedure is available in a PBCCH-enabled cell, the MS may enter
packet transfer mode after acquiring broadcasts of PSI1 and a consistent set of PSI2
messages. The Packet PSI Status procedure allows the MS to request additional system
information after entering packet transfer mode.
Enable Packet SI Status procedure in cells without PBCCH - Reduces data outage time
during acquisition of system information. For example, after cell (re)selection, when the
Packet SI Status procedure is available in a cell without PBCCH, the MS may enter packet
transfer mode after receiving broadcasts of SI3, SI13, and, if present, SI1 messages, the
Packet SI Status procedure allows the MS to request additional system information after
entering packet transfer mode.
Implement R4 GPRS/EGPRS message extensions.
Enhanced Multi Level Precedence and Preemption (eMLPP)

service
Feature Description
The eMLPP service allows calls to be allocated a precedence dependent on their function. For
example, a premium rate subscriber would have a higher precedence than a low tariff subscriber.
This is to allow users of high importance, for example, emergency services, or premium rate
subscribers to be given preferential treatment. The BSS uses this precedence to manage the
active calls in situations such as call setup and for call continuity in case of handover.
The priority, preemption capability, preemption vulnerability, and queuing ability criteria are
allocated by the MSC and is utilized by the BSS to provide the appropriate level of service.
The eMLPP feature enables Users to implement support for preemption within the network. The
eMLPP feature is enabled or disabled on a BSS basis.
The eMLPP feature includes the following optional User-controlled BSS functionality:
Priority protection of PDTCH
Priority level based selection of functionality
68P02901W01-S 4-109
Jul 2008
Support for Half Rate on GDP2 Chapter 4: BSS Software Release Features
Support for Half Rate on GDP2
Feature Description
The GSM Half-Rate feature increases capacity over the air and terrestrial interfaces. It enables
the network to carry up to twice as much traffic, allowing it to cope with increased congestion.
GSM Half-Rate introduced in GSR7, was limited to the GDP platform. Furthermore, the GDP
was unable to support both Half-Rate (HR) and Adaptive Multi-Rate (AMR).
The Support for Half Rate on GDP2 feature extends HR functionality by enabling HR support on
the GDP2 RXCDR platform. In addition, the GDP2 can support both HR and AMR. A combination
of up to 60 channels at SFR, EFR, HR, and AMR is available.
NOTE
AMR encompasses both AMR full-rate and AMR half rate.
Fast Call Setup
Feature Description
This feature reduces the time required for call setup by assigning the MS directly to the TCH
during the IMMEDIATE ASSIGNMENT message, while the available TCHs for the BCCH band
are below a user configured threshold. Once the TCH usage for the BCCH band has equaled or
exceeded this threshold, the BSS performs assignment through the SDCCH.
The benefits of this direct assignment are:

Re-tuning the MS from the SDCCH to the TCH is avoided.
Establishing the main signaling (LAPDm) is only done once.
The data throughout on the TCH is faster than that of the SDCCH.
The operator configured thresholds can help avoid cell congestion due to phantom RACHs.
4-110 68P02901W01-S
Jul 2008
System Information: GSM Overview RSL Congestion Control
RSL Congestion Control
Feature Description
The Radio Signaling Link Congestion Control feature is designed to protect downlink RSLs
from (GSM) paging surges.
When the RSL Congestion Control feature detects the onset of RSL congestion it rejects any
new service requirements and notifies the MSC with an Overload message until the congestion
abates.
During the congestion the BSS sends an alarm to the OMC and provides a statistic with the
amount of time a processor was in a congested state and number of OVERLOAD messages
sent to MSC.
Increased SDCCH capacity
Feature Description
This feature allows configuration of up to 128 SDCCH per cell. In a site with three cells with
24 carriers configured in an 8/8/8 fashion up to 128 SDCCH can be configured per cell. The
feature allows a configuration of up to 8 timeslots for SDCCH on a carrier, so up to 64 SDCCH
can be supported on a single carrier.
Improved Timeslot Sharing (ITS)
Feature Description
The Improved Timeslot Sharing (ITS) feature enables Double Density (DD) CTU2 support of
EGPRS. It does not double voice capacity per CTU2 compared with EGPRS on a Single Density
(SD) CTU2, but provides more channels available for voice users with the EGPRS service in
parallel.
Modifications to CTU2 hardware, BSS Software, or Horizon II Firmware are not required.
The timeslots on one carrier of a DD CTU2 is configured for EGPRS, while the corresponding
timeslots on the other carrier are set OOS.
ITS interacts with and affects other network features, such as VersaTRAU, EGPRS, Increased
SDCCH, and Switchable/Reserved PDTCH allocation.
The ITS feature requires EGPRS and VersaTRAU to be unrestricted.
Improve_ts_enabled specifies the enable or disable status of this feature in the BSS.
The EGPRS Unavailable - No EGPRS capable carriers available alarm is modified in this
feature.
68P02901W01-S 4-111
Jul 2008

Description
{22168} Enhanced BSC Capacity Using DSW2.
{22169} Support for 96 Multiple Serial Interface (MSI) at BSC.
{22266} RSL dimensioning statistics.
{22415} Increase the PCU database capacity.
{23306} BSC Overload Protection.
{25002} TDM Availability Enhancements.
{25423} Software patching.
{25424} PCU Upgrade without BSC Reset.
{25867} New drop call rate classes statistics.
{26481} Support for Horizon II Micro.
{29241} Extended Range for Electronic IDs of Cabinet Power
Supplies.
{30365} Software support for High power Horizon II Micro.
{26740} PCU high bandwidth interconnection.
{27236} 4 Branch Receive Diversity.
{27703A} Quality of Service PhaseII Feature.
{27717} Support of RESUME at intra-BSC level.
{27955A} Software support for High Bandwidth and/or existing E1
BSC/PCU interconnect.
{27962} LCF Memory saving to prolong the life of existing GPROC2.
{28000} Increase the Throughput of PRP with the PCU.
{28333} BSS LAN Packing.
{28337} HSP MTL.
{28340} BSP CPU utilization reduction for higher call handling
capacity.
{28351} Addition of new PCU hardware to increase GPRS capacity.
{28398} Increased Network Capacity.
{28938} Support of Incell as an Optional Feature.
{30828} CTU2D.
{31400} TD-SCDMA and GSM interworking feature.
Continued
4-112 68P02901W01-S
Jul 2008

Description
{32173} Support TFP and TFA in MTP Routing.
{32340} Cell OOS Enhancement.
{30830} CTU2D Asymmetric EDGE.
{33863} UL Retransmission Measurement.
68P02901W01-S 4-113
Jul 2008
Enhanced BSC Capacity Using DSW2 Chapter 4: BSS Software Release Features
Enhanced BSC Capacity Using DSW2
{22168}
Feature description
This is a default feature in GSR9, which is also unrestricted. This feature doubles the TDM
timeslots in BSC from 1024 to 2048 in one switch cage using bank 0/1 extension mode. When
this switch cage has one or more extension cages, the switch cage uses 1024 TSs (BANK0), and
the other extension cages share the rest 1024 TSs (BANK1). The maximum capacity is 8192 TSs
when up to 4 expansion cages are configured, making it possible to equip more devices (for
example, MSI, PSI, and so on) in multiple cages.
This feature is implemented automatically when BSC is up and without requiring changes to
any parameter when:
Primary and redundant TDM highways are fully equipped with DSW2/DSWX.
There is no hardware failure on equipped DSW2/DSWX.
The MMI command reset_device TDM x x brings the BSC from Single Rate Mode to Double
Rate mode when hardware configuration is changed from KSW/KSWX/DSW2/DSWX to ALL
DSW2/DSWX.
Support for 96 Multiple Serial Interface (MSI) at BSC
{22169}
Feature description
This feature provides support for expanding the number of Multiple serial interfaces (MSIs)
from 56 to 96 and additional E1s between the BSC and the BTSs, RXCDR(s), and PCU.
This allows for a greater fan-out on the links to the BTSs, allowing the BSC to support 12 MSIs
per cage on 8 cages. It also paves the way for additional call capacity if the BSC is modified to
support additional erlangs.
4-114 68P02901W01-S
Jul 2008
System Information: GSM Overview RSL dimensioning statistics
RSL dimensioning statistics
{22266}
Feature description
This feature provides new RSL dimensioning statistics generated by the BSS to monitor network
and system events.
RSL dimensioning statistics provide an indication of RSL link utilization. Two RSL raw statistics,
RSL_TX_OCTETS and RSL_RX_OCTETS provided by the BSS enable the operator to determine
the octets sent over the Abis interface. Both, 16k and 64k RSL links are supported. Another new
raw statistic, RSL_LINK_INS indicates the RSL link in-service duration.
Increase the PCU database capacity
{22415}
Feature description
The Increase the PCU database capacity feature allows an explicit request for more PDCH
for use by the PRP/PXP resources than are equipped in the database.
The PCU maps GPRS capable cells to PRPs activating and de-activating PDCH resources in
response to changes in the system (devices going INS, OOS, changes in cell demand, and so on)
with the objective of maximizing GPRS performance.
The PCU(CB) performs the cell balancing algorithm between cells mapped to a PRP instance at
a multiple of the rate at which it is performed between PRP instances. The rate at which cell
balancing is performed between PRP entities is maintained at the legacy duration of 20s.
BSC Overload Protection
{23306}
Feature description
This feature provides CPU utilization overload protection for the BSP. It monitors the BSP CPU
utilization in real time. When the BSP CPU utilization crosses the overload threshold with heavy
call load, the feature starts controlling the number of calls and handovers handled by the
system, so that the CPU utilization of BSP is maintained at a safe level. The feature ensures that
the BSP works reliably even at 90% CPU utilization when the system receives excessive number
of calls and handovers that exceed the maximum processing capability of the BSP.
The feature is triggered automatically when the BSP goes into CPU overload state. The operator
can enable or disable by changing the value of database element bsp_overload_protection.
68P02901W01-S 4-115
Jul 2008
TDM Availability Enhancements Chapter 4: BSS Software Release Features
TDM Availability Enhancements
{25002}
Feature description
This feature enhances the existing fault recovery and detection mechanism of the TDM buses
in the BSC and the RXCDR. This feature is supported only by configurations with expansion
TDM sites.
On detecting a fault in the active KSW/DSW2 expansion matrix, the system swaps to the
redundant TDM highway without waiting for the OMC to initiate the swap. The primary TDM
highway changes to EU state.
This feature also allows the automatic swap to the redundant TDM highway at a specified time
on a daily basis. If no fault is detected, the redundant TDM highway will be continued to be
used. When the redundant highway fails, the system swaps back to the primary highway.
NOTE
Avoid swapping to the redundant highway when audit on the current TDM and/or
KSW is scheduled to occur.
4-116 68P02901W01-S
Jul 2008
System Information: GSM Overview Software patching
Software patching
{25423}
Feature description
Software Patching allows processes running on any executive/exec API supported processors to
load a software patch without resetting or restarting the processor.
A software patch allows changes to be applied to a process in active status. This feature allows
small object changes to be downloaded and updated in real time without board or network
element outage. Certain software problems can be fixed on the system quickly, without causing
any system outage.
A patch level corresponds to a patch, which resolves a single problem or an SR. A patch object
contains one or more patch levels compiled together into an object. A patch object is identified
by a unique code object number, that is, object number 251.
Applying higher patch level also applies all lower patch levels on the BSS. For example,
installation of patch 4 installs patches 1 to 4 on the BSS.
A new version of patch object for the same point release is generated accumulatively from the
previous version of patch object. The new version of patch object contains all software patch
levels from the previous version of patch object. New patch levels are built on top of the patch
levels from the previous version of patch object.
In pre-GSR9 versions of the BSS, all network entities reset in order to upgrade to the new
load. In GSR9, the BSS determines the type of upgrade and communicates it to the OMC. The
type of upgrade is one of:
Full BSC reset (which may or may not include patch object update and/or patch level
update).
PCU upgrade only (which may or may not include patch object update and/or patch level
update).
Software Patch object with possible patch level update.
The BSC communicates the type of upgrade to the OMC. The OMC acknowledges with the
type of upgrade desired by the user.
The BSS continues to process voice calls and GPRS data sessions until the upgrade type is
received by the OMC. The entire BSC is reset only if Full BSC Reset is chosen. Otherwise, if
only a PCU upgrade is required, the BSC directs the PCU to reset and loads the new software,
and the BSC does not reset. Voice calls are not impacted during PCU upgrade.
When Patch Object Upgrade is acknowledged by the OMC, if a new patch object was loaded
with the CSFP download, the patch object is distributed to all network entities.
NOTE
If a patch level install fails at the BTS, then patch level will be reverted to level 0
on all other BTS.
68P02901W01-S 4-117
Jul 2008
PCU Software Upgrade without BSC Outage Chapter 4: BSS Software Release Features
PCU Software Upgrade without BSC Outage
{25424}
Feature description
Before GSR9, a new release of PCU software always caused a full BSC reset, even without any
change to the BSC software load. The PCU Software Upgrade without BSC Outage feature
allows the load of new software release on the PCU without impacting the BSC. Voice calls are
not affected and only GPRS calls drop while the PCU upgrade occurs. This enables to upgrade
the PCU service packs without impacting voice call revenue.
The system uses CSFP download and swap procedure to support this functionality. The BSC
recognizes that the BSC objects are not changed. Therefore, the BSC does not reset during
PCU software upgrade. The PCU downloads the software to CSFP in background mode and
swaps code objects after CFSP code download is complete.
New drop call rate classes statistics
{25867}
Feature description
This feature provides modified drop call statistics generated by the BSS to monitor network
and system events.
The new drop call rate classes statistics automatically give the cause for a dropped call on
both TCH and SDCCH. The existing statistics RF_LOSSES_TCH, RF_LOSSES_TCH_HR
and RF_LOSSES_SD are modified to give more details for the dropped call. When a call is
terminated because of RF problems on TCH or SDCCH, BTS implements an algorithm to
determine the cause for the dropped call. The drop call classification algorithm analyzes the
latest measurement report to ascertain the cause for the call being dropped.
4-118 68P02901W01-S
Jul 2008
System Information: GSM Overview Support for Horizon II Micro, Extended Range for Electronic
IDs of Cabinet Power Supplies, Software support for High power Horizon II Micro
Support for Horizon II Micro, Extended Range for Electronic

IDs of Cabinet Power Supplies, Software support for High
power Horizon II Micro
{26481}{29241} {30365}
Feature description
Horizon II Micro can be configured as a standalone cabinet. It also can be configured

as an expansion cabinet connected to a Horizonmacro/Horizonmacro2/Mcell
6/Horizon2mini/Horizon2micro site controller cabinet. When Horizon II Micro is configured as
the site controller cabinet, Horizonmacro/Horizonmacro2/Horizon2mini/Mcell 6/Horizon2micro
can be configured as its expansion cabinets. Up to three expansion cabinets is supported by a
Horizon II Micro master cabinet. Horizon II Micro has no redundancy since only one BTP is
supported.
FR26481 introduces a new platform constraint into GSR9, if the operator needs to explicitly
identify the cabinet type as Horizon II micro. Two new cabinet subtypes, HORIZON2MICRO,
and HORIZON2MICRO_EXT, are introduced for this purpose.
The software constraints on Horizon II micro cabinet are:

Only one BTP can be equipped to a Horizon II micro master cabinet.
Only one CTU2 radio can be equipped to a HORIZON2MICRO or a HORIZON2MICRO_EXT

cabinet.
The software allows the operator to equip only Opto alarms 1 to 6 to EAS at Horizon II
micro master and extension cabinets. If the operator attempts to enable an alarm in the PIX
range 7-16, software aborts the EAS equipage. A mismatch of PIX inputs and EAS database
information occurs if the operator modifies a cabinet subtype to or from Horizon II micro. The
software forces the EAS to be unequipped before a cabinets subtype is modified. The software
reads PIX inputs through the CTU2 and alarm card; hence both these FRUs must be in service
to determine cabinet type.
FR29241 adds software support to read the PSU vendor electronic ID in a Horizon II macro,
mini or micro cabinet. It supports the modified alarm to provide the manufacture ID of BCUP
for all Horizon II-derivative cabinets containing CTU2. The range of manufacture ID of BCUP
is extended from 7 to 15 for each BCUP type (AC, DC28v, DC48v). This feature provides an
easy way to manage the power supply unit.
FR30365 introduces a new version of Horizon II micro cabinet which can reach full power.
Hardware differences with the standard Horizon II micro cabinet include a dongle, which is
used to identify a Horizon II micro cabinet as a high-power version and also a more powerful fan
unit, as the standard cabinet cannot dissipate heat quickly enough to maintain full power. The
cabinet type is detected by the software through reading the PIX ports that are controlled by the
dongle. A new FRU type H2MICRO_HIGH_PWR is used for high-power Horizon II micro cabinet.
High-power Horizon II micro BTS supports all Horizon II micro functionality. The maximum
power output of CTU2 in a high-power Horizon II micro cabinet can reach 63 Watts for single
density and 2X20 watts for double density.
This feature provides a unique identifier to determine which cabinets are standard power
Horizon II micro and which are the high-power variant of Horizon II micro. The standard power
Horizon II micro supports 2 W per carrier in double density mode. The high-power variant
supports up to 20 W per carrier in double density mode or 63 W in single density mode.
68P02901W01-S 4-119
Jul 2008
PCU high bandwidth interconnection Chapter 4: BSS Software Release Features
PCU high bandwidth interconnection
{26740}
Feature description
This feature includes the support of the PSI into the current GSM BSC product. The PSI
interfaces are used to connect the GSM BSC to the PCU. The PSI occupies an MSI slot in the
current BSC cage, restricted to slots 13, 12, 7 and 6. Instead of using two MSIs to allow up to
120 timeslots of EDGE data, one slot is occupied by a PSI to allow up to 320 timeslots of EDGE
data. A PSI can process 480 timeslots of EDGE data itself, and the constraint lies in TDM
highway timeslot allocation. The freed MSI slot can be used for 2 downstream or upstream span
lines. The PSI provides an Ethernet link from the BSC to the PCU.
PSI has an MPC8260 controller with 17 56311 DSPs. The MPC8260 controller (MCU) has the
following functions:
Code-loading for all DSPs.
Setting up the TDM highway maps.
DSP resource management for TRAU connection.
TDM timeslot management for TRAU connection.
Terminating all 64k HDLC links for GSLs.
Collecting statistics and alarms.
The MCU also has access to the TDM bus through its communication processor HDLC ports.
The feature supports the GSL over Ethernet. To establish a GSL, the software sets up TDM
connection between LCF HDLC channel and MCU HDLC channel through the KSW. As each
GSL can be identified by (IP+UDP port) on the Ethernet, the MCU sets up an internal router
between the HDLC channel and the UDP port.
The feature introduces an ALIVE protocol between the PSI and PXP. The ALIVE protocol uses
UDP frame and the default UDP port 0xE300. The ALIVE protocol is used by both PSI and PXP
to detect alive status of peer side. When the BSC and PCU detect the Ethernet connection on
one PSI/PXP board, they will automatically try to establish the ALIVE protocol for the board. The
connection status of ALIVE protocol also represents the state of GDS equipped on the board.
The ALIVE protocol can also provide ability to detect exceptional reset of remote board and GDS
locking operation from remote. It can also provide BSC the ROM-RAM status of PCU.
Two new device types are introduced by this feature. One is PSI and another is ETH. The PSI
is a child device of CAGE, and ETH is a child device of PSI.
4-120 68P02901W01-S
Jul 2008
System Information: GSM Overview 4-Branch receive diversity
4-Branch receive diversity
{27236}
Feature Description
The 4-branch receive diversity feature provides the BSS an ability to support configuration of 4
branch receive diversity for each DRI (Digital Radio Interface).
The BSC supports the configuration of 4 branch receive diversity through the DRI diversity_flag
database parameter.
The BSC allows the configuration of a single cabinet with 4 branch receive diversity. The BSC
also allows the configuration of a dual band cell with 4 branch receive diversity capability
with the restriction that the cell contains multiple single band cabinets, one or more of each
frequency band type. For example, a dual band cell could consist of one or more 900 and one or
more 1800 Horizon II Macro cabinets, each of which contains DRIs configured for 4 branch
receive diversity.
The BSC allows the co-existence of dual band cabinets, single band cabinets with 4 branch
receive diversity configured DRIs, single band cabinets without 4 branch receive diversity
configured DRIs in the same site.
NOTE
Dual band and 4 branch receive diversity configurations are mutually exclusive
on a per cabinet basis because both require different SURF and cable harness
modules.
The non-4 branch receive diversity configured cabinets can be any Horizon II
or legacy cabinet type.
Dependencies
The BSC allows 4 branch receive diversity configuration on DRIs only within a single
band Horizon II Macro cabinet.
The BSC allows 4 branch receive diversity configuration only on a CTU2 transceiver
operating in single density mode.
The cabinet_type parameter should be set to HorizonIImacro or a HorizonIImacro_exten-

sion cabinet and the cabinet frequency_type parameter should be set to single band.
68P02901W01-S 4-121
Jul 2008
Quality of Service PhaseII Feature Chapter 4: BSS Software Release Features
Quality of Service PhaseII Feature
{27703A}
Feature description
This feature is an enhancement of the GSR8 QoS feature. This feature includes the following
components:
Support for Streaming Traffic Class: Support for Streaming Traffic Class allows the
operator to specify a service that requires constraints on delay and jitter as well as
minimum bit rate. Support for PFCs requesting streaming traffic class can be enabled or
disabled using the streaming_enabled BSS parameter. If support for streaming traffic
class is disabled, BSS will still try to admit the streaming traffic classes as one of the
matching interactive traffic classes, determined based on the MTBR settings.
Support for Maximum Bit Rate enforcement: Maximum Bit Rate enforcement allows
the BSS to throttle the throughput of user to the maximum bit - rate stated in the QoS
parameters (ABQP) even if there is capacity to provide the user a higher throughput.
Controlling triggering of PFM messaging to SGSN when a non-real time PFC is downgraded
or upgraded due to admission control or retention.
Configuration parameters determine whether bit rate negotiation below MTBR/GBR is

permitted or not for non real time or real-time traffic classes.
Capacity is based on a less conservative budget to start (using operator configurable

initial coding scheme).
The DELETE-BSS-PFC.REQ PDU and the associated procedures defined in the 3GPP R6
specifications is also supported. BSS sends this PDU when it deletes or preempts a PFC.
This feature is a restricted feature and requires the GPRS QoS feature to be unrestricted.
The BSS is enhanced to include changes based on R6 standards. The key modification is the
ability of the SGSN to communicate the Allocation and Retention Priority (ARP) using the ARP
Information Element (IE) as a part of the BSS Create PFC procedures. If this information
element is received, the BSS considers the priority level of the requested PFC when deciding
on the resource allocation. If the ARP IE is not provided in the Create PFC PDU by the
SGSN, parameters are provided to configure the ARP based on precedence class for all traffic
classes/PFCs for which the BSS does not receive the ARP IE from the SGSN.
4-122 68P02901W01-S
Jul 2008
System Information: GSM Overview Support of RESUME at intra-BSC level
Support of RESUME at intra-BSC level
{27717}
Feature Description
The Support of RESUME at intra-BSC level feature provides BSS system, the flexibility to
suspend or resume GPRS services. The MS requests the network for suspension of GPRS
services by sending Suspend message to the network when:
A GPRS-attached MS enters dedicated mode and the support of Class A mode of operation
is not possible.
An MS in class A mode of operation is handed over to a cell where the support of Class A
mode of operation is not possible.
The BSC tracks the MS status as Suspended when it receives Suspend Ack message from
the SGSN. If the BSS detects that the conditions for the GPRS suspension have disappeared
for an MS in suspended state and there is no RA change, the BSS sends a Resume message
to the SGSN to resume GPRS services. If a Resume Ack is received from the SGSN, the BSS
sends a Channel Release message with a GPRS Resumption bit to the MS, to notify the MS
to resume GPRS service.
The MS resumes GPRS services by sending a Routing Area Update Request message to
the SGSN in the following cases:
If the BSS fails to request the SGSN to resume GPRS services.
If the RR Channel Release message was not received before the MS left the dedicated
mode.
If the MS locally determines that the conditions for the GPRS suspension have disappeared.
The bssgp_t4_timer starts when the BSS sends either Suspend or Resume request to the
SGSN. After the timer expires, the BSS restarts the timer and resends the message. The BSS
aborts Suspend or Resume requests after three attempts.
When the lower level calls are preempted, BSS initiated resume procedure is not initiated
due to the performance of eMLPP.
68P02901W01-S 4-123
Jul 2008
Software support for High Bandwidth and/or existing E1 BSC/PCU interconnect Chapter 4: BSS Software Release Features
Software support for High Bandwidth and/or existing E1

BSC/PCU interconnect
{27955A}
Feature Description
This feature provides backward compatibility for GSR9 software. It allows network operators
to reuse existing DPROC hardware in the PCU. The GSR9 software treats the U-DPROC2 as
legacy DPROC. It also has a mixed mode operation (old DPROCs working with new U-DPROC2
boards). This feature disables the 3xPCU feature.
The PRP capacity is 280 PDCH of capacity/70 PDCH of throughput.
This feature supports two deployment modes when U-DPROC2 and legacy DPROC are used at
the same time in the PCU.
In the first mode of deployment, the U-DPROC2 serves as a PRP or PICP just as legacy DPROC.
The PRP capacity/throughput is 280/70 in this mode (with rolling blackout mechanism). The
PRP capacity/throughput is 140/140 with the rolling blackout mechanism disabled. Therefore,
capacity is reduced for increased throughput. All connectivity between the BSC and PCU
is through E1 links.
In the second mode of deployment, the PCU allows DPROC/U-DPROC2 (PICP),

DPROC/U-DPROC2 (PRP) to coexist in the same PCU cage. Up to 11 PXPs with one PRP or
PICP can be configured in PCU. PXP has more than double PRP capacity. It increases PRP
capacity/throughput (280/70) in the second mode (without rolling blackout mechanism).
GSR 9 supports one PCU equipped at a BSS to provide the necessary functionality for
GPRS/EGPRS. When a PCU is equipped, a corresponding cabinet and cage device are
automatically equipped.
The PCU has the following features:

It supports the new U-DPROC2 hardware board.
It allows both legacy DPROCs and U-DPROC2s to coexist and operate within the same
PCU shelf.
It supports and provides for hardware upgrade from legacy DPROC to U-DPROC2 board.
PCU redundancy is not available.
The BSC supports the same alarms, device states, statistics generated on legacy MSI board for
E1 BSC-PCU connectivity.
4-124 68P02901W01-S
Jul 2008
System Information: GSM Overview LCF Memory saving to prolong the life of existing GPROC2
Dependencies
This feature is dependent on the FR28351 (ePCU) set.
The dependencies for enabling this feature are as follows:

High bandwidth interconnect between BSC and PCU (PSI)
Increased PCU database capacity
Packet or coaxial interface module
Increased PRP throughput
LCF Memory saving to prolong the life of existing GPROC2
{27962}
Feature Description
The increase in the capacity of the BSC in terms of carriers, sites, CICs, and so on requires
additional memory for the database object and the normal increase in object sizes due to
addition of functionality in feature releases. With this feature, the system will not load PSI or
PCU objects, onto a GPROC2 during initialization of board or BSC. This prevents the failure of
GPROC cross load due to the GPROC2 being out of memory. This feature also removes some
of the BTS objects from each of the GPROC2-LCFs in order to save memory, so processes
can be run on these LCFs.
As the GPROC2 no longer stores PSI or PCU objects, the source must be a GPROC3 when
GPROC cross load is done using LAN broadcasting mode since it contains all the BSS objects.
While cross loading from GPROC2 to GPROC3, GPROC3 has highest priority. But when GPROC2
is chosen, the BSC uses two GPROCs as the source. One GPROC2 is used as the load controller
and the other, which must be GPROC3, is used as a second source.
NOTE
A GPROC can be assigned as the second source multiple times but can be the
controlling source for only one download session at a time.
68P02901W01-S 4-125
Jul 2008
Increase the throughput of PRP with the PCU Chapter 4: BSS Software Release Features
Increase the throughput of PRP with the PCU
{28000}
Feature description
The current PRP processor has a fanout/throughput of 120/30 PDCHs. A rolling blackout
mechanism determines which 30 of the 120 PDCHs is serviced in any 20 ms block period.
This feature provides an option to disable the rolling blackout mechanism on the PCU so that
the throughput of the PRP processor is the same as the fanout of the PRP.
A new database parameter, prp_fanout_mode is introduced in this feature to support two types
of PRP fanout mode. In mode 1, with rolling blackout mechanism enabled, a maximum of the
total In Service timeslots in a PRP are allowed to perform data transfers in each direction for
every block period. Refer to Table 4-37. In mode 2 with rolling blackout mechanism disabled, a
maximum of total In Service timeslots in a PRP can transmit data in each direction for every
block period. Table 4-37 depicts the detailed processing capacity in mode 1 and 2. As a new
hardware U-DPROC2 is introduced in GSR9, PXP configured by this new board has much higher
capacity and throughput.
Table 4-37 PRP capacity in mode 1 and mode 2
Base Processor Fanout/

Total Fanout/ Throughput/ PMC Fanout/ Throughput
Processor Throughput / # of
# of Mobiles /# of Mobiles
Mobiles
Mode 1 Mode 2 Mode 1 Mode 2 Mode 1 Mode 2
DPROC/PRP or 120/30/120 48/48/72 N/A N/A N/A N/A
U-DPROC2/PRP
U-DPROC2/PXP 280/70/280 140/140/280 196/49/196 98/98/196 84/21/84 42/42/84
BSS LAN Packing
{28333}
Feature description
This feature increases the efficiency of the LAN by reducing the number of messages sent. It
allows the BSC to support 180kBHCA under the GSR9 call model.
4-126 68P02901W01-S
Jul 2008
System Information: GSM Overview HSP MTL
HSP MTL
{28337}
Feature description
The restricted HSP MTL (High Speed MTP Transport Layer Link) feature offers enhanced
capacity and flexibility of MTL. The BSC implements this feature. It increases the capacity of
MTL from 64k to 2M to support huge BSC configurations and the BSC supports High Speed
MTL (HSP MTL) link utilization maximally at 13%.
This feature introduces one new timer, ss7_hsp_l2_t1. The ss7_hsp_l2_t1 timer is used for
signaling link alignment procedure called Timer alignment ready in ITU Q703.
A new statistic, MTP_SL_ERROR_RATE_HSP analyses MTP C7 performance and locates fault

on Signaling Link (SL). The statistic tracks the number of times an SL is lost when the Error
internal monitoring threshold (TE) is reached during the monitoring period.
NOTE
FR28337 is only supported when GPROC3-2 is available at BSC for hosting HSP LCF.
This feature is depended on FR28398 Increased Network Capacity.
BSP CPU utilization reduction for higher call handling capacity
{28340}
Feature description
The BSP CPU Utilisation Improvement feature supports a call load of 180K BHCA (96s call
duration). This is to improve the CPU utilization at the BSP by improving the efficiency of the
Ater allocation algorithm.
With the memory restriction removed, the CPU efficiency can be improved at the cost of higher
memory usage. A list-based Ater search algorithm allocates resources when a new call (mobile
originated, mobile terminated, external handover from MSC), CIC remap or Ater switchover is
initiated and also for an existing call with rate change. The Aters are allocated from the top
of the available lists to minimize the search. This enables the BSC to assure that the mean
BSP CPU utilization does not exceed 70%. The new Ater search algorithm is provided with a
mean computation complexity of O(1). The list searching enhancement also applies to internal
handover where the backhaul rate changes when the Allocation Manager process is called
for a CPU intensive task.
68P02901W01-S 4-127
Jul 2008
Addition of new PCU hardware to increase GPRS capacity Chapter 4: BSS Software Release Features
Addition of new PCU hardware to increase GPRS capacity
{28351}
Feature description
This feature increases the GPRS capacity on the current PCU and BSC hardware platform by
introducing a new board, Universal DPROC-2, (U-DPROC2). Accordingly, it also introduces a
new rear transition module U-DPROC2 RTM as a new replacement board for the PCU.
Each U-DPROC2 is mated with a U-DPROC2 RTM. Pairing a U-DPROC2 board with a legacy RTM
module or pairing a legacy DPROC board with a U-DPROC2 RTM module is not supported. The
U-DPROC2 replaces existing DPROC and creates new functionality called PXP which combines
PRP and PICP functionality on the same board.
U-DPROC2 hardware supports the following features:

PICMG 2.9 systems management.
Full hot-swap capability.
A U-DPROC2 serving as PXP supports a 1000BASE-T or CAT-5e link from the PCU to the BSC
completing connection to the new PSI board.
Also, the U-DPROC2 can coexist with legacy DPROC which serves as PRP or PICP. U-DPROC2
can function as PRP or PICP.
U-DPROC2 PXP supports IPv4 and UDP protocols for Ethernet connection to PSI board at the
BSC. Therefore, both TRAU data and GSL signaling are transported over IP/UDP protocol
between U-DPROC2 and PSI when U-DPROC2 serves as a PXP.
The U-DPROC2 uses more power than the original DPROC. To ensure that the U-DPROC2 can
be used in the same functionality of the DPROC card without any additional power and cooling
considerations, the core frequency of the U-DPROC2 processor is scaled back to reduce power.
This mode is used while operating in PICP and PRP mode of operation.
While operating the U-DPROC2 in PXP mode, the card is operated in full 1GHz mode. Additional
baffling is added to the cabinet supporting the PCUs to increase the cooling capacity.
4-128 68P02901W01-S
Jul 2008
System Information: GSM Overview Increased Network Capacity
Increased Network Capacity
{28398}
Feature description
The optional feature, Increased network capacity enhances the network capacity and
supports database capacity up to 8 MB.
The network capacity will be as follows:

The Maximum number of carriers that a BSC supports increases from 512 to 750.
The Maximum number of sites that a BSC supports increases from 100 to 140.
The Maximum number of circuits that a BSC supports increases from 3200 to 4800.
The maximum number of BSC-XCDR connectivity that a BSC supports increases from
27 to 42.
This feature has an impact on the collection and dispatch of the additional statistics due to the
increased number of managed objects. The upload and collection of statistics to the OMC takes
place at 30 or 60 minute intervals, and completes in 20 minutes.
Support of Incell as an Optional Feature
{28938}
Feature description
This feature is to provide the option to restrict the use of Incell BTS sites within a network if
required. During the database upgrade (that is, upgrading GSR8 database to GSR9) the system
does not allow any Incell site to be equipped in the database unless the customer has purchased
this feature. This feature would also restrict the adding of Incell hardware if the option has
not been purchased.
The IncellOpt parameter indicates whether the Incell Support feature functionality is
unrestricted in the BSS software.
68P02901W01-S 4-129
Jul 2008
CTU2D Chapter 4: BSS Software Release Features
CTU2D
{30828}
Feature Description
This feature introduces CTU2D radios that can support both SD (Single Density) and DD
(Double Density)) EDGE architectures. This is an optional feature. The CTU2D radio supports
the following EDGE modes:
CTU2D SD: This mode is identical in operation to the existing CTU2 SD.
CTU2D PWR: This mode is also known as ITS mode as the operation is identical to that of
CTU2 in ITS mode.
CTU2D CAP: In this mode, carrier A is fully EDGE capable and carrier B supports
GPRS/TCH. No timeslot blanking is required.
The CTU2D in Capacity mode enables the BTS to support BBH for GMSK carriers assigned to
carrier B irrespective of the EDGE capabilities and PD support for carrier A.
The Capacity mode is only applicable to the new CTU2D radio platform. As it is not possible to
detect the radio platform in all scenarios, radio configuration mismatch handling is enhanced to
support the new mode as follows:
When a non-CTU2 radio is configured in Capacity mode, it remains OOS.
When a CTU2 is configured in Capacity mode, it assumes double density behavior but
with EDGE restriction.
CTU2D feature implements the following features:

Improves Receiver Sensitivity.
Supports Double Density EDGE.
Only one Carrier is EDGE capable.
This feature introduces a new parameter, ctu2dcapopt. The ctu2dcapopt parameter indicates
whether the CTU2D Capacity feature is restricted or unrestricted in the BSS. The range of
the dri_density parameter is extended to 3.
Dependencies
This feature requires the EGPRS feature to be unrestricted.
4-130 68P02901W01-S
Jul 2008
System Information: GSM Overview TD-SCDMA and GSM interworking feature
TD-SCDMA and GSM interworking feature
{31400}
Feature description
This feature provides GSM/TD-SCDMA inter-working support. It is an optional feature and

supports the following functions:
GSM/GPRS to TD-SCDMA cell reselection in circuit-switched idle mode and packet idle
mode by broadcasting TD-SCDMA neighbor list and corresponding 3G measurement
parameters in SI2ter, SI2Quater.
GSM/GPRS to TD-SCDMA cell reselection in packet transfer mode.
MS reselect to GSM/GPRS from TD-SCDMA.
Supports TD-SCDMA to GSM handover in circuit-switched dedicated mode.
NOTE
When TD-SCDMA and GSM interworking is disabled if the feature is restricted, all
functions described above will not be available.
When TD-SCDMA and GSM interworking is enabled, the user can add/change/delete/display
TD-SCDMA neighbor list from BSS MMI or from OMC-R.
Support TFP and TFA in MTP Routing
{32173}
Feature description
This feature is an enhancement of FR 30340 (MTP routing). FR30340 introduced the

functionality of MTP Routing to enable the BSS to be connected to MSC through an STP node,
usually MGW. However, BSS does not process the Transfer Prohibited (TFP) and Transfer
Allowed (TFA) messages. TFP is sent from STP to BSS when the link between STP and MSC is
broken to indicate the MSC signaling point is unavailable. TFA is sent from STP to BSS when
the link between STP and MSC is restored. This feature adds the support of TFP and TFA in
Motorola BSS.
68P02901W01-S 4-131
Jul 2008
Cell OOS Enhancement Chapter 4: BSS Software Release Features
Cell OOS Enhancement
{32340}
Feature description
This feature introduces an operator configurable delay to postpone system information update
message for System Information types 1, 2, 2bis, 3 and 4 to the MS when a BSC is undergoing
reset during master BSP failover. This delays cell reselection procedure by the MS during
a global reset.
This feature is designed to extend the time the MS remains on the network undergoing a reset
procedure and enables the operator to maintain roaming subscribers.
Call processing at the BSS is responsible for the delay of system information update message to
the MS when the BSS is undergoing reset. OMC is responsible for providing the mechanism to
configure value of the delay.
A new database parameter cell_barred_delay specifies the delay of cell bar information to the
MS. The BSS parameter specifies the time the BSS delays sending SystemInformationUpdate
message to the MS during global reset procedure.
CTU2D Asymmetric EDGE
{30830}
Feature description
This is an optional feature which enables EDGE capability on both DRIs of the CTU2D. This
feature can be supported only on Horizon II macro, Horizon II micro and Horizon II mini sites.
In the asymmetric mode, carrier A is fully EDGE capable and carrier B supports EDGE on the
downlink and GMSK on the uplink. Same timeslots on both the carriers cannot support 8PSK
simultaneously. The asymmetric feature requires the remapping of the internal TDM allocations
to provide two EDGE carriers. Hence, BBH support for EDGE is removed for the entire site.
The CTU2D can process only GMSK coding schemes in uplink on timeslots of Carrier B when
the corresponding timeslot on Carrier A has an uplink 8PSK capable TBF. Hence, an EGPRS
MS cannot use MCS 5-9.
Call processing at the BSS is responsible for the delay of system information update message to
the MS when the BSS is undergoing reset. OMC is responsible for providing the mechanism to
configure value of the delay.
This feature introduces two new parameters, ctu2dasymopt and asym_edge_enabled. The
ctu2dasymopt parameter indicates whether the CTU2D asymmetric feature is restricted or
unrestricted. The asym_edge_enabled parameter enables or disables asymmetric EGPRS for
CTU2D on per SITE basis. The CTU2D asymmetric feature must be unrestricted to enable
this. The site cabinets have to be Horizon II macro, Horizon II micro, Horizon II mini.
Dependencies
The asymmetric EDGE feature requires the EGPRS feature and the CTU2D Capacity feature to
be unrestricted.
4-132 68P02901W01-S
Jul 2008
System Information: GSM Overview UL Retransmission Measurement
UL Retransmission Measurement
{33863}
Feature description
This feature provides an accurate method to calculate the UL RLC abnormal retransmission
rate on a cell basis. This feature introduces two statistics UL_RLC_NACK_BLKS and
UL_RLC_STALLED_BLKS, which are used to calculate the UL RLC retransmission rate.
In addition, these statistics are used to distinguish the reason for the retransmissions, and
obtain the overall and specific retransmission ratios.
68P02901W01-S 4-133
Jul 2008
BSS software release GSR9 FP1 Chapter 4: BSS Software Release Features
BSS software release GSR9 FP1

Table 4-38 summarizes the features provided at software release GSR9 FP1.
Table 4-38 Release GSR9 FP1 features
Description
{34145} Support the display of GPRS resource allocation per PCU.
{34144} Support the usage of idle TCH for packet burst traffic.
{31565} Support a switch and additional stats for AGCH flow control.
{33397} Add paging discard stats for RCC feature related link.
{26881} Support for Release 6 based Extended Uplink TBF mode.
{23292} Support for the extended dynamic MAC mode at the air
interface.
{27703A} Quality of Service Phase II Feature.
Support the display of GPRS resource allocation per PCU
{34145}
Feature description
The main function of this feature is to display the actual PDTCH and backhaul configuration for
each cell per PCU and per PRP/ PXP DPROC and PPROC level. This feature provides information
on the GPRS configuration per PCU side to facilitate the GPRS configuration and deployment.
The MMI command disp_equipment displays the actual cell GPRS configuration information
per PCU and PRP/PXP level along with the existing equipment information. When full option
is set on disp_equipment command, it displays the actual PDTCHs configuration and the
information of whether all requirements are satisfied at cell level for all the cells belonging to
this PCU or PRP/PXP DPROC or PPROC board.
NOTE
To display the actual PDTCH and backhaul configuration, update the message from
PRP to PCU CB for the cell PD configuration status and use the message from MMI to
PCU CB.
4-134 68P02901W01-S
Jul 2008
System Information: GSM Overview Support the usage of idle TCH for packet burst traffic
Support the usage of idle TCH for packet burst traffic
{34144}
Feature description
Reserved PDTCH channels and Switchable PDTCH channels are used for GPRS traffic. Without
this feature, TCH channels are used only for voice call traffic and cannot be used for GPRS traffic.
This feature introduces a mechanism which allocates the idle TCH channels as additional
switchable PDTCH resource when there is GPRS traffic congestion in a cell. It returns these
PDTCH resources back to the TCH resources when the GPRS traffic congestion is relieved. The
additional switchable PDTCH resources are defaulted as TCH resources which have no impact
on normal voice call.
This feature is available only for EDGE enabled cell (at least one 64k PDTCH available in the
cell). The number of additional switchable PDTCHs are calculated based on the EDGE carrier
configuration.
Support a switch and additional stats for AGCH flow control
{31565}
Feature description
This feature allows the user to manually enable or disable Access Grant Channel (AGCH) flow
control. The users can enable AGCH flow control on the required cells and disable the AGCH
flow control on other cells based on different network situations.
This feature provides the users with the option to avoid frequent triggering of AGCH overload
due to the trigger of Immediate Assign Reject (IAR). It also adds additional counter array stats
to monitor the number of Immediate Assign (IA) or IAR messages sent over CCCH or discarded
when AGCH overload respectively.
The BSS supports a per cell element _cell_data, 20 which indicates whether the functionality of
the AGCH flow control is enabled or disabled. It also specifies the triggers associated with IA
or IAR that can trigger the AGCH overload.
When the functionality of AGCH flow control is disabled, the overall flow control works by
appropriately configuring other parameters that affect RACH/TCH/SSM flow control.
NOTE
To make the overall functionality of flow control efficiently on system level, it is
recommended that at least one flow control must be enabled and work well.
68P02901W01-S 4-135
Jul 2008
Add paging discard stats for RCC feature related link Chapter 4: BSS Software Release Features
Add paging discard stats for RCC feature related link
{33397}
Feature description
This feature provides a mechanism to count the number of paging messages discarded from a
specific point between the A interface and Air interface, for Network Operation Mode II (NOM2)
and Network Operation Mode III (NOM3).
In 33397 feature, CS_PAGING_MSGS_FROM_MSC (as well as the legacy stats

PAGE_REQ_FROM_MSC) tracks the number of paging requests received from the MSC.
Support for Release 6 based Extended Uplink TBF mode
{26881}
Feature description
This feature enhances uplink/downlink data performance by minimizing the interruptions of

uplink data flow in GPRS/EGPRS networks due to the frequent release and establishment of
uplink TBF. The uplink TBF is maintained during temporary inactive periods, where the mobile
station has no RLC information to send. The network determines the release of the uplink TBF.
The network continues to allocate USFs (Uplink State Flags) for the mobile station during the
inactivity period. The mobile sends Uplink Dummy Control Blocks, if indicated or RLC data
blocks, when new RLC data blocks become available.
The feature introduces two new parameters, ext_ul_dur and ext_utbf_nodata. The ext_ul_dur
parameter determines if the feature is enabled or disabled and the duration of the Extended
Uplink TBF. The feature is disabled when ext_ul_dur is set as 0 and is enabled when it is set
within a range of 24 to 250. The maximum duration of Extended Uplink TBF is 5 seconds (250
data blocks). The uplink TBF is released when ext_ul_dur expires.
The ext_utbf_nodata parameter determines whether R6 mobile sends UL Dummy Control Block
or not during Extended Uplink TBF mode when USFs are assigned for the mobile. When the
ext_utbf_nodata is set as 0, R6 mobile sends UL Dummy Control Block during Extended Uplink
TBF period. When the ext_utbf_nodata is set as 1, R6 mobile does not send UL Dummy Control
Block during Extended Uplink TBF period.
4-136 68P02901W01-S
Jul 2008
System Information: GSM Overview Support for the Extended Dynamic MAC mode at the air interface (EDMAC)
Support for the Extended Dynamic MAC mode at the air

interface (EDMAC)
{23292}
Feature description
The EDMAC feature is introduced to support class 11 and 12 mobiles with 3 and 4 UL (uplink)
timeslots capability. When 3 or 4 uplink timeslot allocation is assigned, EDMAC is required
for the request uplink TBF.
This is an optional feature for the network. When a class 11 or 12 mobile requests an uplink
TBF, the network assigns the EDMAC for the uplink TBF if the mobile supports EDMAC and the
TBF allocation requires EDMAC mode. The network assigns the lowest numbered timeslot in
the allocation as PACCH timeslot.
The PCU attempts to assign three timeslots to the EDA capable class 11 and class 12 mobile if
gprs_ul_dl_bias is set to UL bias. During the uplink TBF in EDMAC, the network schedules
USFs in the lowest or the second timeslot in the allocation, the mobile station transmits a
single RLC/MAC block on the same PDCH and all higher numbered assigned PDCHs. The PCU
schedules periodic PUAKs for 3 or 4 UL TBFs frequently enough to prevent stalling dependent
on number of uplink timeslot (3 or 4) used and GPRS or EGPRS TBF mode.
The EDMAC feature increases the users throughput in UL (for example, video and email
uploads) with ability to support 3 and 4 UL timeslots.
Dependencies
The Extended Dynamic Allocation feature requires the GPRS feature to be unrestricted.
Parameters and statistics
The gprs_mac_mode parameter enables the support of Extended Dynamic Allocation (EDA)
when set to 2.
The edaOpt parameter indicates whether or not the Extended Dynamic Allocation feature
functionality is unrestricted in the BSS software.
The following statistics are introduced by this feature:

UL_RADIO_BLKS_8PSK_3_TS
UL_RADIO_BLKS_GMSK_4_TS
UL_RADIO_BLKS_8PSK_4_TS
UL_RADIO_BLKS_GMSK_3_TS
UL_TBF_TIME_GMSK_3_TS
UL_TBF_TIME_GMSK_4_TS
UL_TBF_TIME_8PSK_3_TS
UL_TBF_TIME_8PSK_4_TS
68P02901W01-S 4-137
Jul 2008
Quality of Service Phase II Feature Chapter 4: BSS Software Release Features
Quality of Service Phase II Feature
{27703A}
Feature description
This feature is an enhancement of the GSR9 QoS feature. This feature includes the following
components:
Support for Streaming Traffic Class: Support for Streaming Traffic Class allows the
operator to specify a service that requires constraints on delay and jitter as well as
minimum bit rate. Support for PFCs requesting streaming traffic class can be enabled or
disabled using the streaming_enabled BSS parameter. If support for streaming traffic
class is disabled, BSS will still try to admit the streaming traffic classes as one of the
matching interactive traffic classes, determined based on the MTBR settings.
Support for Maximum Bit Rate enforcement: Maximum Bit Rate enforcement allows
the BSS to throttle the throughput of user to the maximum bit-rate stated in the QoS
parameters (ABQP) even if there is capacity to provide the user a higher throughput.
Controlling triggering of PFM messaging to SGSN when a non-real time PFC is downgraded
or upgraded due to admission control or retention.
Configuration parameters determine whether bit rate negotiation below MTBR/GBR is

permitted or not for non real-time or real-time traffic classes.
Capacity is based on a less conservative budget to start (using operator configurable

initial coding scheme).
The DELETE-BSS-PFC.REQ PDU and the associated procedures defined in the 3GPP R6
specifications is also supported. BSS sends this PDU when it deletes or pre-empts a PFC.
This feature is a restricted feature and requires the GPRS QoS feature to be unrestricted.
The BSS is enhanced to include changes based on R6 standards. The key modification is the
ability of the SGSN to communicate the Allocation and Retention Priority (ARP) using the ARP
Information Element (IE) as a part of the BSS Create PFC procedures. If this information
element is received, the BSS considers the priority level of the requested PFC when deciding
on the resource allocation. If the ARP IE is not provided in the Create PFC PDU by the
SGSN, parameters are provided to configure the ARP based on precedence class for all traffic
classes/PFCs for which the BSS does not receive the ARP IE from the SGSN.
4-138 68P02901W01-S
Jul 2008
Chapter
OMC-R Software Release Features

This chapter provides a summary of the features of Motorola OMC-R software releases. Releases
of software before GSR2 were identified by four-digit release numbers, such as 1.2.1.1. After
the 1.4.1.x release, the numbering system was revised; release 1.5.0.x was renamed GSR2.
The following OMC-R software releases are described in this chapter:
OMC-R software release 1.1.2.0 on page 5-3.
OMC-R software release GSR2 on page 5-29.
OMC-R software release GSR4.1 on page 5-34.
OMC-R software release GSR5.1 on page 5-48.
68P02901W01-S 5-1
Jul 2008
Quality of Service Phase II Feature Chapter 5: OMC-R Software Release Features
OMC-R software release GSR6 (Horizon II) on page 5-56.
OMC-R software release GSR7 (GSM Half Rate) on page 5-63.
5-2 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release 1.1.2.0
OMC-R software release 1.1.2.0

Configuration
In OMC-R release 1.1.2.0, the OMC-R configuration comprised the following:

System processor: Tandem A21. X.25 link
Man-Machine Interface (MMI) Processor
The following features were included in OMC-R release 1.1.2.0:

Sounding of a bell whenever a new alarm is sent to MMI.
A timeout variable for the X.25 connection establishment phase.
A timeout variable for the data transfer phase.
A timeout variable for the supervision of IPC response messages from both CM and LM
(Uploader).
Two versions of tabular key statistics reports, together with an interactive graph option.
On parsing a BSS statistics file, the parser moves it to:

Filename.parsed.
Filename.bad_header.
Filename.FATAL_ERROR.
Fatal errors cause the Parser to terminate (For example, unable to connect to db).
The parser no longer accepts statistics following a PROCEDURE tag.
The parser expects a DURATION field in file headers. Durations of plus or minus 5 seconds
are accepted for parsing. No other files are parsed.
The valid header year range changed from 1980 to 2079.
An MMI printer command is provided, and the ability to change the font of text in
Subscription List windows.
Subscription by device class.
Event log post-processing utilities (cel, fes, qfes, ces).
Automatic back up of uploaded database.
68P02901W01-S 5-3
Jul 2008
Release 1.1.2.0 features Chapter 5: OMC-R Software Release Features
Automatic back up of load directory on selection of new software load.
The Event Interface subsystem generates a critical alarm for all Network Elements (NEs)
in the network as reported by CM on system start up. It generates a clear alarm for each
NE link brought into service, that is, for each link for which a connect request is received.
Subsequent link failures or recoveries are accompanied by corresponding alarms and
clears. In addition, whenever a link goes down or comes up, a message is written to the
OMC-R audit file indicating the current time and the NE device ID associated with the link.
Log files created for update and cut over procedures.
OMCINIT logs information to OMC-R audit file.
Uploads tagged in OMC-R audit file with process id.
5-4 68P02901W01-S
Jul 2008

Configuration

System processor: Tandem A21
MMI Processor

IPC logging is ENABLED, by default in this release.
OMC-R Database Schema upgraded to remove some indexes on the PM stats tables.
The OMC-R Watchman script (omc_watchman) provides facilities for monitoring the
OMC-R processes running on the system processor. If any of the OMC-R processes
terminate, it provides facilities for informing OMC-R operators.
Event Processing utilities.
The rate at which MMI attempts to process events and what action MMI takes when
flooded with events can be configured through environment variables.
$DBMS_ROOT/bin/db_pm_maint modified to:

Increase performance.
Accept additional parameters when invoked.
Manually, as well as automatically, cleared alarms change from red to black.
Six new parameters added to the BSS Add Cell command. The Change, Add, and Display
Cell commands modified. The added parameters are:
d1_ncell_proc (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)
68P02901W01-S 5-5
Jul 2008
OMC-R software release 1.1.2.2 Chapter 5: OMC-R Software Release Features

Configuration

MMI Processor

Kernel parameter changes: MAXIMUM to 6 X 4096.
Installation: size of logical logs increased, number of logical logs decreased, size of
physical logs increased.
db_pm_maint utility: approach to maintenance is changed from the lock-restrictions

approach to a configuration row-set approach.
IPC logging is ENABLED, by default.
Manual submission of stats files for parsing.
MMI support for multiple printers.
Manually handled and cleared alarms are written to the event log. The alarm is written to
the log with the current time, new status field, and user name of the operator handling or
clearing the alarm.
NOTE
The original alarm appears with a status field NOT APPL in the event log.
Command partitioning: a new read-only OMC-R MMI, if necessary.
Notification of incoming events/alarms in iconized event/alarm windows.
Support for EAS in MMI.
Subscription list sorting: events extracted from AET are displayed in chronological order.
5-6 68P02901W01-S
Jul 2008
Performance Management stats filtering:

Filter RF_LOSSES_TCH
Filter CHAN_REQ_MS_FAIL
PM_SD_FILTER
Support for both 30 minute and 60 minute stats file collection.
Front End updates for release 1.1.2.2. The OMC release 1.1.2.2 Front End supports both
BSS version 1.1.2.1 and version 1.1.2.2. To change which BSS version is supported, the
BSS_VER environment variable can be set appropriately. A new menu option, Version, has
been added to display the current value of BSS_VER.
Ability to view call trace output at the OMC-R.
Support for Remote Tune Combiner device.
Display of OMC-R software load version number (Tandem and MMI).
Display of additional alarm Information at OMC-R.
Channel number displayed in HEX at the OMC-R.
KSW displayed correctly in events and alarms (not as TDM).
Tab operation allowed in MMI dialogue boxes.
Naming of event log changed to evYYMMDDHHMMSS.
Input buffer size for X.25 data in the Event Interface application has been increased from
165 bytes to 1024 bytes.
Logging of messages added to the Event Router and List Manager processes.
Date format for PM is now user configurable (PM_DATE_FORMAT).
68P02901W01-S 5-7
Jul 2008

Configuration

MMI processor: OSF/MOTIF 1.1.1
Table 5-1 summarizes the OMC-R release 1.1.2.3 main features.
Feature Description
load_db and activate_db Two scripts allow the installation from tape
of a NE database, generated on a test BSS
system, on to the OMC-R. The load_db script
reads a NE database from tape and installs it
on the OMC-R. The activate_db script moves
a NE database, installed through load_db,
from the installation directory to the current
database location of a specified NE.
Critical alarm threshold exceeded Supports for MMS alarm. Critical alarm
threshold exceeded to inform the operator
when the critical MMS alarm threshold is
exceeded and the MMS is disabled. The alarm
string is included in MMI MIT data file.
Confirmation dialogues Relates to confirmation of user commands.
Throughout the MMI area for delete and
modify commands and potentially dangerous
commands (for example, Disable Logging)
the operator is prompted with a confirmation
dialogue box. The operator can select OK to
continue or CANCEL to cancel the operation.
Date/time on event logs A date/time stamp written at the start of every
event log file when it is first opened. It is not
visible to the OMC-R operator and is intended
to be used only by event post processing
utilities.
Continued
5-8 68P02901W01-S
Jul 2008
System Information: GSM Overview Additional features

Feature Description
Customizing database reports Consists of two simple methods of retrieving
database data for display, namely, interactive
ISQL, and a simple Informix report generator
called ACE.
Alarms and events highlighted when selected Alarms and events are highlighted when
selected in an Alarm Display, Event Display
or Event Log. An alarm/event remains
highlighted until another alarm/event is
selected.
Additional features
The following additional features were included in OMC-R release 1.1.2.3:

Customising PM Reports document.
Support for new EAS alarm: the alarm Bad Daughter Board ID read - possible bad EAS
board replaced the Bad ID alarm to get output when an EAS board is unseated.
MMI maintains its local list of selectable NEs. There is no need to log out MMI sessions
after deletion of a node.
Potentially separate Subscription Lists for Events and Alarms, configurable using MIT file.
BSP and DHP alarms added to MIT file.
No Object field changed to Object No in Upload Status window.
EM router no longer exits on an error return code from the IPC subsystem.
More description error messages added to EM List Manager.
Time Now option removed from PM reports.
On the MPC, get login replaced by cuserid.
Updated omc_db_ckspace script.
Immediate printing of events and alarms.
68P02901W01-S 5-9
Jul 2008

Configuration

MMI processor
Table 5-2 summarizes the features included in OMC-R release 1.1.2.4.
Feature Description
Enhancement for omc_watchman script The omc_watchman script sends a mail
message to the users specified by the
variable MAIL_ADDRESS when an OMC-R
process terminates. The message specifies
which process has terminated. In addition,
watchman.log logs any processes reports on
omcinit, and logs any processes that have
terminated while watchman.live reports
which processes are currently alive.
Disconnecting applications for online DB The OMC-R database can be brought down
maintenance to single user mode for certain types of
maintenance. The applications connected
to the database (EM and PM) can handle
database disconnection and reconnection.
This is to cater for db online maintenance.
5-10 68P02901W01-S
Jul 2008

Configuration
In OMC-R release 1.2.0.0 the OMC configuration comprised the following:

System Processor: Tandem A22
MMI Processor (MPC)
MMI Processor (SPARC 10)
In addition, the following is optional:

NCD XRemote software
MMI Processor (SPARC IPX)
Table 5-3 summarizes the OMC-R release 1.2.0.0 features.
Feature Description
Display of loads on i-CM modify window As part of the X upgrade to X11R4 the
horizontal scroll bar for the Load Names list
(in the i-CM Node Modify window) is not
included by default. This list is automatically
resized, if possible, and the horizontal scroll
bar is only present when it is not possible to
resize the list.
Graph of raw stats Default worksheets enable the graph option
for all statistics as soon as they become
available.
Command Constructor closing on X.25 Command Constructor closes following
connection break confirmation of X.25 connection break error
message and the Wingz license is freed.
Add alarm strings for transcoder to BSC link BSS Release 1.2.0.0 and the OMC-R support
(XBL) the XBL alarms. The XBL alarms include
twelve hardware alarms and three PM alarms.
The PM alarms are similar to those defined
for RSL and OML devices.
Support XBL stats A parser, database, and PM-UI are provided
to support XBL statistics.
Continued
68P02901W01-S 5-11
Jul 2008

Feature Description
Periodic supervision of accessibility The OMC-R periodically polls the NEs with
open connections to the OMC-R for their
status. If the NE informs the OMC-R that
is not operating correctly, a CRITICAL
processing Failure Event is generated for
that NE, with an error Id of BSS Error State
[30006]. If the NE fails to respond to an OMC
request for its status, the OMC-R generates
a CRITICAL processing Failure Event for that
NE, with an error Id of BSS Resp Timeout
[30005].
Save alarm context If the BSS-OMC-R connection goes down, the
BSS buffers events or alarms until connection
is re-established. If the buffer overflows (with
more than 100 events or alarms), an alarm is
sent from BSS to the OMC-R indicating this.
The OMC-R supports this BSS alarm (Id 4),
alarm string Event Buffer Overflow.
BSS stats changes Supports changes made to BSS statistics.
Support new BSS alarms Introduces new BSS alarms.
Port of MPC applications to SPARC All current MPC applications are ported to
the SPARC platform.
Incorporation of cron jobs New scripts support listing, removing,
archiving, and rolling over log files produced
by the OMC-R. These scripts have been
written with a view to running them from
cron.
Immediate sld program buffer flushing The sld program flushes its buffer immediately
to standard output following a buffer write.
Previously, this was done only when the buffer
was full. The change enables immediate
printing of alarms.
Remote x terminal support over a dial-up line Users can access the OMC-R through a remote
X terminal using XRemote. When using
XRemote the Event Manager Subscription
must not be displayed for long periods,
especially when high event rates are involved.
M' and O' defined on forms worksheets The two worksheets EquipDRI.wkz and
EquipRTF.wkz are updated with a description
of M/O/P (Mandatory/Optional/Predefined).
Error message if X.25 connection lost In the absence of an X.25 connection, the
Command Constructor displays an error
message. On confirmation of the error
message, the command constructor closes
and the Wingz license is freed.
Continued
5-12 68P02901W01-S
Jul 2008

Feature Description
New directory BS GSM-1200 to support BSS A directory BSGSM-1.2.0.0 is created as
part of the install or upgrade procedure
on the MPC. Install M files and update.
M files are modified to create the
BSGSM-1.2.0.0 directory and its associated
sub directories.
Management of watchman.log file When the omc_watchman.log script is
executed a log file is created. The script
roll_watchman.log forces a roll-over of the
log file when executed. The script moves the
existing watchman.log file to the filename
watchman.log.yymmdd. It is recommended to
execute this script once a day from cron.
Reason strings changes The OMC-R reason strings are made
consistent with those used at BSS MMI and
BSS FM and with those in the Troubleshooting
Guide. A new reason string is also added for
COMBINER CONTROLLER.
IAS device ID change The Id for BSS device IAS is changed from
SITE-CAGE-IAS to SITE-CAB-IAS.
Support new BSS PATH device Supports a new device, PATH, in BSS release
1.2.0.0. The new path device Id is 42. The
MMI name is PATH and the format of the
BSS MMI device identifier is SITE, PATH. The
SITE is the connected site on the other end of
the PATH. The PATH is a unique identifier (0
- 9) within the reporting site.
Work in progress message for Wingz The command constructor displays a work in
progress message while being invoked. The
performance management reports generator
also displays a work in progress message
while being invoked.
MIT file updates Two new tables are defined in the MIT File
for Event State Definitions and Alarm Format
Definitions. These are required for Event Log
Processing utilities.
New 4GL reports Consists of four key statistics 4GL report
modules, which provide key statistic data
summary reports summed over time for each
cell and BSS. These reports can be invoked
interactively from the UNIX command line,
or automatically by using cron. These report
modules give an indication of the quality
of service the GSM network is currently
providing.
OMC-R forms for BSS modifications Updates to the OMC-R (forms) support
changes made to the BSS software.
Continued
68P02901W01-S 5-13
Jul 2008

Feature Description
New directory BSGSM-1.1.2.3 A new directory for the forms software
supports BSGSM-1.1.2.3. The install and
upgrade utilities are modified to create this
directory.
Using cron to produce key stat reports for The key_stat_reps script is invoked from
yesterday the cron table early each morning. Running
the script produces reports in a directory
under the $PM_LOG directory, which can
also be printed on request. These reports
are key_stat reports for the network for the
day previous to which the script is called.
The script removes all previous reports from
$PM_LOG before generating the new ones.
OMC-R key stats on MMI processor (MPC) Key statistics are provided on the MMI
processor.
OMC-R key stats on MMI processor (SPARC) Supports the key statistics used by the 4GL
PM command line reports.
5-14 68P02901W01-S
Jul 2008

Configuration
In OMC-R release 1.2.2.1. the revised/additional requirements are as follows:

System processor
MIB processor (SPARC)
In addition, the following is optional:
NCD XRemote software

MMI Processor (SPARC IPX)
MMI Processor (SPARC 5)
Table 5-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 the network. The selected map can be
configured to display the Network Elements
(NEs), links in the network and the sites and
links contained within the NE. Maps can be
topological or geographical.
Alarm and state synchronization Provides a mechanism for synchronization
of the OMC-R and BSS/RXCDR device status
at OMC-R initialization time, and after a
failure of the OMC-R or BSS/RXCDR or the
links between them. Status information
is composed of both alarm and device
state information. Synchronization occurs
automatically at a configurable interval.
Audible alarm The OMC-R provides an output to drive
an audible alarm. The output is activated
whenever alarms higher than a programmable
severity are detected. The alarm severity
level is configurable on a system-wide basis
only.
Continued
68P02901W01-S 5-15
Jul 2008

Feature Description
OMC-R application fault management Unrecoverable failures in OMC-R applications
generate internal alarms. For OMC-R release
1.2.2.1, fault notification only is provided.
OMC-R system administration Allows installation of the OMC-R software for
the 1.2.2.1 release.
OMC-R installation utilities and directory Separates release dependent information
structure from release independent information so that
the operator does not loose configuration
information during an upgrade.
4GL/GX performance management reporting Performance Management (PM) reporting
is based on Informix 4GL/GX. Operators
can access performance data through the
MMI processor using the PM reporting
module of the OMC-R MMI. There is also an
enhancement to PM reporting whereby it
gives a value for all the intervals present, but
flags the fact that full coverage of the interval
measured was not possible.
Total calls statistic This statistic is added to the existing 16 key
statistics.
Zero filter and rollup The Parser is modified such that
CHAN_REQ_MS_FAIL statistics with
zero values are not inserted in the database.
This saves insertion time and database
volume requirements as well as eliminating
the restrictions on the use of the 1.1.2.2
CHAN_REQ_MS_FAIL filter. A cell level value
is also inserted for this statistic, representing
the sum of the individual channel values for
the collection period in question.
Interim logging of change of access rights Provides information on which users are
currently installed in the OMC-R and what
their privileges are. A log record is added
to the log file each time a user is added or
deleted.
Compression of BSS software objects at the Allows the OMC-R to store backup NE
OMC-R databases in a compressed format on the
OMC-R. This reduces the amount of disk
storage required to store databases at the
OMC-R and simplifies operator procedures.
OMC-R audit process Monitors the following: X.25 lines connected
to the tandem system processor, tandem
hardware unit integrity and disk space usage
on the Tandem/usr partition. The feature
produces alarms for these areas under certain
conditions.
Continued
5-16 68P02901W01-S
Jul 2008

Feature Description
Alarm filtering by device type and alarm code Provides the following event and alarm
enhancements: subscription of alarms by
Error Id, subscription of all events by Device
Type (Obj Class), display of alarm additional
information fields.
Event log search and print option Provides the operator with the following
facilities such as one or more event logs is
selected for post-processing, searches for
events can be performed according to event
log filtering criteria, a collection of events
which meet the specified search criteria is
formed, the collection of events is sent to
standard output, search and input of selection
criteria can be invoked from MMI menus.
Load management comment and memo field Provides enhanced user input capabilities
from the OMC-R MMI terminals.
All but subscriptions (blocking) The Add and Modify Subscription windows
have been modified to allow blocking of
subscriptions for a specific Subscription List.
There is also an Equal/Not Equal toggle
button on the Error Id field.
Support of 1 Gbyte configuration From the 1.2.2.1 release onwards support
is given for a 1 Gbyte Tandem system disk.
Support continues for the existing 650 MB
system disk. Note that the 1 Gbyte disk allows
for increase in database size.
Night concentration Allows an operator be able to handover
management of one network region to
another OMC-R during the night shift. This
necessitates the provision of a mechanism to
allow a single workstation to access multiple
System/MIB processor pairs.
Blacklist subscription list An alarm blacklist is introduced to provide
system wide blocking of specific alarms, to
prevent them reaching the MMI; they are still
logged.
Change cell command split The change cell command is split up into 11
sub sections.
68P02901W01-S 5-17
Jul 2008

Table 5-5 summarizes the OMC-R release 1.2.2.2 features to support the BTS6, ExCell6, and
TopCell cabinets.
Feature Description
BSS support activities Provides support for the statistics and alarms
defined by BSS release BSGSM 1.2.2.2.
Auto initiate alarm windows Allows alarm/event subscription windows to
be automatically opened on start up of a MMI
session.
Total calls statistics The key statistic total calls replaces the
existing paging load in the call summary key
statistic.
Forms updates A new parameter called TRU identifier is
added to the EquipDRI worksheet after the
Slot number.
Database management A new script, delete_CELL is added for
deleting cells from the schema. This script
provides similar functionality as the scripts
for managing the deletion of BSS and SITE
information.
5-18 68P02901W01-S
Jul 2008

Configuration
In OMC-R release 1.2.3.0. the revised/additional requirements are as follows:

System processor
MIB processor software (either SPARCstation 10 or 20)
MMI processor software
Table 5-6 summarizes the OMC-R release 1.2.3.0. features.
Feature Description
NMC-OMC-R security application (optional) Supports the optional security application
on the interface to the NMC. The purpose of
this feature is to provide secure access to the
OMC-R through Remote Login over an OSI
Stack.
System administration Provides the necessary procedures and
scripts to install the 1.2.3.0 OMC-R and to
install the SAC application on the OSI and
RLP processors.
BSS support activities Provides support for the statistics and alarms
defined by BSS release BSGSM 1.2.3.0.
Graphical key statistics - save selection Enables the Operator to save the Date and
Time selection and the NE selection.
MMI audit trail - BSS MMIs Stores the commands carried out on the BSS,
from the OMC-R, along with a time stamp.
Rlogin modifications Enables an Operator to remote login to a NE
while a database upload is in progress. The
Operator is warned of the database upload.
Batch based time updates Provides a script which sets the time
automatically at the BSS, controlled by an
OMC-R. The time is set using BSS MMIs.
68P02901W01-S 5-19
Jul 2008

The OMC-R software is supplied on one CDROM which includes software for the System
Processor (Tandem), the MMI Processor (SPARC) and the MIB Processor (SPARC). In addition to
the OMC software, the CDROM also contains third-party product software for Solaris patches,
Informix, Motif, and X11R5.
In addition to the OMC-R CDROM, one additional CDROM is supplied with it. The CDROM
contains the Worldview version 2.0.1 software release, and one cartridge tape is supplied
containing the Wingz software release.
Table 5-7 summarizes the new OMC-R software release features for 1.3.0.0.
Feature Description
Network Configuration Augments the BSS configuration data maintained at the
Management (NCM) OMC-R, allows the manipulation of the data from the OMC-R
and supports the synchronization of this data with the BSS. It
centralizes the configuration data at the OMC-R, supports the
logging of changes and creates the infrastructure to support
the creation of BSS binary from the OMC-R.
Code Storage Facility Allows the online download of a new BSS load, from the
Processor (CSFP) OMC-R to the BSS, to support the fast swap over to a new
load, thus reducing BSS downtime. This feature also includes
support for electronic transfer of BSS databases from the
Datagen platform to the OMC-R.
Online help from GSM Provides the OMC-R user with a context sensitive help
documentation facility, covering all aspects of work at the OMC-R, including
information on the BSS.
1.3.0.x systems Provides the mechanisms for doing a clean installation of
administration the GSM OMC-R system or for upgrading a current (1.2.2.
X/1.2.3.0) OMC-R system to the 1.3.0.0 software release.
Utilities for administrating the OMC-R databases and log files
are also included.
Operability enhancements Provides a forms interface to support the following Operation
and Maintenance procedures: Report all out of service
devices. Add devices. Interface to the OMC-R batch facility.
5-20 68P02901W01-S
Jul 2008

Most of the new features and enhancements to the OMC-R software for 1.4.0.0 are brought
about by the introduction of a revised hardware platform.
New OMC-R systems use the new OMC-R System Processor, the Tandem Integrity S1475, while
existing Tandems are upgraded to UNIX SV.4. (B series OS).
Feature Description
Upgrade of Tandem operating system The OMC-R System Processor Operating
software to UNIX SV.4 (B series) including System (OS) has been upgraded to UNIX SV.4
Veritas file system manager. (B series OS). The OMC-R System Processor
software applications have been ported to
run on this operating system. The B series
Operating System on the System Processor
is fully compatible with the existing Solaris
configuration on the SPARC stations.
Port to Spider X.25. The OMC-R X.25 application has been ported
from TITN X.25 to Spider X.25 on the System
Processor to facilitate the new operating
system. The main impact of this feature is that
the X.25 troubleshooting procedures change.
Dual 64 kbps file upload circuits. Provides support for an additional upload
circuit. This gives the OMC-R two 64 kbps
X.25 circuits for file uploads from the BSS to
the OMC-R. The impact of this feature is that
up to eight simultaneous uploads are now
supported (four uploads was the previous
limit). The extra upload circuit increases
redundancy.
Upgrade of database software to INFORMIX The port to the B operating system also
online 5.0. necessitates a move to Informix 5.0 software
as INFORMIX 4.1 is not supported on the B
series OS.
System Administration Backup menus. The backup menu program handles online
backups, file locking and data consistency as
well as providing an easy to use front end
for both backups and restores across the
network.
Continued
68P02901W01-S 5-21
Jul 2008

Feature Description
Compatibility with existing software Tandem S300 or 1475s systems, running
OMC-R software release 1.4.0.0 are
compatible with the BSS software releases
BSGSM 1.4.0.x and BSGSM 1.3.0.x. Tandem
S300s and 1475s can be used in the same
cellular network. However, it is recommended
to run a BSS software load that is compatible
with the appropriate OMC-R software revision
of both OMC-Rs so that BSSs are quickly
transferred between OMC-R systems if the
need arises.
Installation and commissioning impact A menu driven install program is available
which offers the user a choice between
upgrade and clean install options. Once the
OMC-R GSM 1.4.0.0/1.4.0.x software release
has been installed, utilities are provided
which will configure the System Processor
file system and X.25 software to meet the
network requirements.
OMC-R upgrade/rollback paths Motorola provides full details of the
procedures required for upgrade/rollback of
the OMC-R at a later date. The 1.3.x to 1.4.0.0
upgrade path is supported. The 1.4.0.0 to
1.3.x rollback path is supported.
OMC-R administration impact The port to B Series OS changes many of the
OMC-R system administration procedures.
Operation and Maintenance impact The port to Spider X.25 changes the X.25
maintenance and troubleshooting procedures.
5-22 68P02901W01-S
Jul 2008

Most of the new features and enhancements to the OMC-R software for 1.4.0.1 are brought
about by the introduction of a revised hardware platform and are identical to the enhancements
described in release 1.4.0.0, so a brief summary is included here followed by the specific
enhancements unique to 1.4.0.1.
New OMC-R systems use the new OMC-R System Processor, the Tandem Integrity 1475, while
existing Tandems are 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:
Upgrade of Tandem operating system software to UNIX SV.4 (B series) including Veritas
file system manager.
Port to Spider X.25.
Dual 64 kbps file upload circuits.
Upgrade of database software to INFORMIX online 5.0.
System Administration Backup menus.
Online documentation.
Further features of OMC-R software release 1.4.0.1
Table 5-9 summarizes the features that are only available from release 1.4.0.1.
Feature Description
Cell parameter propagation Allows the operator, through the CM MIB at
the OMC-R, to change parameters in any Cell
in the GSM network and apply any of those
changes to other Cells in the network.
Neighbor propagation Automatically aligns the settings of some
attributes of the Cell and RTF objects, with
dependent attributes of the Neighbor object
(and also DRI, RTF, and Source objects).
Continued
68P02901W01-S 5-23
Jul 2008
Further features of OMC-R software release 1.4.0.1 Chapter 5: OMC-R Software Release Features

Feature Description
MicroCellular MicroCellular is a concept in which RF
coverage is structured in more than one
layer. It is generally applied as an extension
to an existing MacroCell network in order to
increase its capacity significantly and provide
better coverage in areas of high traffic
density. MicroCellular supports a mixture
of optional and standard software features.
They are identified as follows: Independent
BCCH Allocations on BCCH/SACCH.
Handover Flow Between Cells Statistics.
Microcellular (combined micro/macrocell)
support (optional).
Enhanced event log search and print Enables the OMC-R operator to filter
event/alarm messages in the Event Log
windows through a filter which corresponds
in functionality to the subscription selection
dialogues used in the Event and Alarm
Displays windows.
5-24 68P02901W01-S
Jul 2008

Release 1.4.0.6 feature support
There were no OMC-R specific features for 1.4.0.6. The OMC-R 1.4.0.6 release supported
the following BSS features:
M-Cell2 GSM900 MHz band
M-Cell2 DCS1800 MHz band
M-Cell6 GSM900 MHz band
M-Cell6 DCS1800 MHz band
M-Cell GSM900 MHz band with EGSM
RSS functionality port to carrier to carrier equipment (TCU) M-Cell
Recovery escalation
BSC CSFP redundancy
Dual rate and M-Cell impact on BSU-BTS
68P02901W01-S 5-25
Jul 2008

Release 1.4.0.7 feature support
There were no OMC-R specific features for 1.4.0.7. The OMC 1.4.0.7 release supported the
following BSS features:
M-Cellmicro GSM900 MHz band
M-Cellmicro DCS1800 MHz band
5-26 68P02901W01-S
Jul 2008

The OMC-R software release supports both BSS and OMC-R features. Although there is no
OMC-R 1.4.1.1 release, the OMC-R 1.4.1.0 software release supports the following BSS 1.4.1.1
software release features:
M-Cell2/6 MCU redundancy
Phase/frequency lock
Sync boot
Table 5-10 summarizes the OMC-R features of release 1.4.1.0.
Feature Description
BSS device management through OMC-R GUI Enhances the functionality already provided
by the OMC-R GUI for performing network
level Fault Management and Configuration
Management activities from the OMC-R GUIs
Navigation Tree.
Proxy cell Enables cells from external GSM Networks
(managed by another Motorola OMC-R or
that of another vendor) to be modeled at the
OMC-R so that when changed, they can be
updated through neighbor propagation. It is
particularly useful in microcellular networks
employing equipment from more than one
vendor.
Alarm context sensitive help Provides online context sensitive information
on any selected alarm when alarm handling.
Improved PM GUI Provides a new enhanced PM GUI, which can
be selected from the OMC-R GUI front panel.
The graphing capability has been improved to
support multiple traces.
PM activation from MAP Provides the facility to invoke the new PM
GUI with devices already preselected from
other areas of the OMC-R GUI such as the
network maps or the Navigation Tree.
Continued
68P02901W01-S 5-27
Jul 2008

Feature Description
Alarm handling improvements Provides several enhancements to the Event
Management functionality provided by the
OMC-R. The enhancements are as follows:
Alarm blacklisting, OIC alarm clearing and
Map event history.
Command partitioning - GUI only Partitions OMC-R users into different security
areas. Depending on which security area
the user has access to, they are allowed
or disallowed options on the OMC-R GUI
that could be used to alter OMC-R or BSS
information.
Handover performance statistics Provides a package of enhanced handover
enhancement package performance statistics which reduce network
optimization effort and time.
15,000 TCH support Provides support for 15,000 traffic channels in
networks where the OMC-R is deployed with
a Tandem Integrity 1475 System Processor.
Existing OMC-R systems deployed with
Tandem Integrity S300 System Processors
will continue to support 10,000 traffic
channels.
Alarm paging (optional) Can be used automatically to notify on-call
personnel of certain alarms or state changes
which have been reported to the OMC-R.
DBMS upgrade Details the changes required for the OMC-R
DBMS in the OMC-R 1.4.1.0 system to support
the other 1.4.1.0 features. The main impact of
the feature is to the tables and columns of the
PM database on the OMC-R System Processor.
5-28 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release GSR2
OMC-R software release GSR2

GSR2 features
Table 5-11 summarizes the OMC-R features supported by the GSR2 (1.5.0.0) software release.
Feature Description
Expanded Call Trace With the introduction of the call trace
expansion feature, the BSS will expand the
data collected to be compliant with GSM
standards. This includes the collection of RR
and Abis messages.
MSC Initiated IMSI and IMEI Call Trace Allows the MS to be tracked as it moves across
the network.
Online Transcoder expansion Allows the transcoder capacity, associated with
equipped transcoder cards, to be increased
online while cellular service is maintained to
subscribers within the associated Base Station
System (BSS).
Online Add/Copy/Delete Cell Supports the online modification to the cell
configuration of the SITEs within a BSS while
cellular service is maintained to subscribers.
Microcellular neighbor class 7 Provides additional microcellular functionality
to cater for special handover situations in
contiguous microcells in networks with limited
frequency spectrum, where it is impossible
to avoid deploying adjacent cells on adjacent
BCCH frequencies.
Satellite BSC/XCDR interface (optional) Provides the BSS software support for
transmission of the OML link through satellite.
This gives the facility for the interconnection,
through satellite, of the BSC or RXCDR with
the OMC-R.
Satellite XBL support (optional) Provides the BSS software support
transmission of the XBL link through satellite.
This gives the facility for the interconnection
of RXCDR to BSCs deployed in areas where
land based and microwave links needed
for interconnection are unavailable or cost
prohibitive.
Continued
68P02901W01-S 5-29
Jul 2008
GSR2 features Chapter 5: OMC-R Software Release Features

Feature Description
Enhanced GSM 12.04 Statistics Compliance Provides a package of additional OMC-R key
statistics reports and additional BSS statistics
which greatly improve the compliance
of the Motorola statistics to GSM 12.04
recommendations.
Downlink RXQUAL Stat (OMC-R bin) Provides an enhancement to existing OMC-R
support for the downlink RxQual raw statistic
reported from the BSS. The OMC-R now
supports the full bin counts gathered by
the BSS, improving on current support of
distribution (min/mean/max values). This
feature provides improved system optimization
support.
Link Balance Verification Statistics Provides a facility at the OMC-R to identify
those carriers which have unbalanced uplink
and downlink signal strengths. This feature
supports optimization activities.
CM Service Statistics Breakout Provides call success statistics that more
closely match MSC statistics. Existing
Motorola raw statistics have been modified to
improve the accuracy of call success statistics.
Network Health Reports Enhances the OMC-R performance reporting
capabilities by providing additional PM reports
that measure network performance from the
subscriber perspective.
Map filtered Event Log Search and Print Enables the OMC-R operator to select a node
on the map and apply a user defined filter to
events associated with the node before display.
The invoked Event Log Search and Print
window can then process the multiple log files.
Generic RF data export Provides a facility at the OMC-R to extract RF
data easily. The objective of this feature is
to reduce the time taken to implement major
network updates.
GPROC2 support Allows the use of either GPROC2 or GPROC1
in BSCs, BTSs, and RXCDRs.
Q3 NMC interface Configuration Provides the support for NMC read/write
Management (optional) access of the RF parameters stored in the
OMC-R MIB through the Q3 interface.
Automatic instance naming for Q3 (optional) Provides the OMC-R support for Automatic
instance naming in the CM MIB which has
been part of the OMC-R Q3 Interface features
since OMC-R release 1.4.0.x.
Continued
5-30 68P02901W01-S
Jul 2008

Feature Description
Q3 NMC interface Call Trace transfer Provides the OMC-R support for the dynamic
transfer of Call Trace data, which is formatted
according to GSM 12.08 recommendations,
from the OMC-R to the NMC through the Q3
Interface.
SUN Scalable OMC-R 0 - 20 k TCH Allows the network operator to install an
OMC-R platform that can be cost effectively
expanded as the cellular network grows.
Common Desktop Manager Provides an OMC-R desktop environment,
which can be customized on a per user
basis, and which reduces window clutter and
provides a graphical front end to the UNIX file
system.
System Admin GUI Provides a GUI for routine OMC-R system
administration tasks. It gives access from
the front panel of the OMC-R desktop to the
different SUN administration tools which
support Solaris 2.5.1.
Enhanced Informix Database Maintenance Reduces the amount of time and expertise
required to maintain the OMC-R Informix
database. INFORMIX Version 7 supports
multiprocessor systems and includes GUI tools
for database performance monitoring and
administration.
Enhanced OMC-R Software Installation and This feature (known as Jumpstart) reduces
Upgrade the amount of time and expertise required to
install or upgrade an OMC-R. Jumpstart allows
multiple Sun workstations (such as Operator
workstations) to be replicated from another
similarly configured processor.
The following list summarizes the hardware features provided in the BSGSM-1.5.0.0 release
with OMC-R/BSS software support:
GPROC2, enhanced processor board
M-Cell Remote Tune Combiner (1800 only)
Retrofit M-Cell RTC (GSM900) for BTS4/BTS6
Remote VSWR monitor
68P02901W01-S 5-31
Jul 2008
OMC-R software release GSR3 Chapter 5: OMC-R Software Release Features

GSR3 features
Table 5-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 through a standard web browser (Netscape)
on a client machine connected to the OMC-R LAN. The
browser is supported on both Sun Solaris and Windows
NT (Intel-based) platforms to access OMC-R PM data.
BSS Device Management through Enhances the BSS device and function management
OMC-R GUI capabilities from the OMC-R GUI.
Metrica Statistics Introduces new statistics to support the BSS. Metrica is a
tool that gathers statistics from various types of OMC-Rs
and compares and consolidates those statistics.
5-32 68P02901W01-S
Jul 2008

GSR4 features
Table 5-13 summarizes the OMC-R features supported by software release GSR4.
Feature Description
Network geographical access control N/A
Transfer Motorola text detab format to Converts Motorola text detab format files
PlaNET into a format acceptable to PlaNET, which is
necessary to transfer data to PlaNET.
Task-based Routine Operation and Provides a new OMC-R user interface
Maintenance that integrates the tools necessary for
routine maintenance of the Motorola radio
infrastructure equipment.
Operator-specific regions N/A
Network optimization: cell optimized GUI N/A
Scalable OMC-R The System Processor and the MIB Processor
have been consolidated into a single SunFire
4800/4900 server. This provides further
reductions in cost of ownership and improved
system administration, performance, and
reliability.
Process restartability Allows a subset of system processor
processes (Restartable processes) to restart
automatically, if the processes fail, without
the need for a full OMC-R stop/start. Other
system processes (Non-restartable vital
processes) cause an automatic OMC-R
stop/start on failure.
New Millennium Addresses all aspects of the Motorola system;
OMC-R, BSS, and the BTS and BSC hardware.
It concerns itself with internal clock operation
and the use of the date in various parts of the
product, for example, within the Event and
Alarm reports.
68P02901W01-S 5-33
Jul 2008
OMC-R software release GSR4.1 Chapter 5: OMC-R Software Release Features
OMC-R software release GSR4.1

GSR4.1 features
Table 5-14 summarizes the OMC-R features supported by software release GSR4.1.
Feature Description
GPRS OMC-R (PCU) Provides a fully integrated solution within the existing
OMC-R architecture. It consists of support for the PCU as
part of the BSS.
OMC-R capacity increased to Increases the OMC-R capacity from the previous rating of
30k TCH and 120 NE 20 kTCH and 64 network elements, to 30k TCH and 120
network elements without requiring hardware upgrades
to the E3500. Also increases the network traffic and
NE count of the OMC-R by extending the object model
and increasing capacity of the OMC-R databases and
data storage areas. This means that the increased size
network can be managed without altering the data storage
arrangements.
5-34 68P02901W01-S
Jul 2008

GSR5 features
Description
BTS concentration
Propagation after audit
EAS relay MMI output control for InCell, M-Cell, and Horizon
Intelligent congestion relief
Adaptive handovers
Support of BCCH and SDCCH for EGSM
Coincident multiband boundaries
Reporting the results of alarms recovery action
Flexible neighbor 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
Continued
68P02901W01-S 5-35
Jul 2008
BTS concentration Chapter 5: OMC-R Software Release Features

Description
Increased OMC-R neighbor stats
OMC-R GUI support for PCU device object
Network expansion batch capability
Increased capacity OMC-R
Increasing maximum number of trunks per BSC
Expansion/de-expansion
Vanguard software upgrade support
Support for Vanguard 6455 router
Removal of the clear stats command
PCU alarms detected by HSC
BTS concentration
The BTS concentration feature provides an alternative mechanism for allocating terrestrial
backhaul for radio resources between the BSC and the BTS. Previous to the introduction of this
feature, these resources were allocated when RTFs were equipped. This feature preserves the
existing mechanism, but allows the operator the choice, on a per BTS site basis, of whether to
use the existing mechanism, or the new dynamic allocation. This feature is optional.
This feature, previously called Dynamic Downlink Power Control Steps, provides optimized
uplink and downlink power control. This is achieved by:
Adding flexibility in defining power steps.
Modifying the range of power steps (by allowing power step sizes to be changed
dynamically).
Performing downlink oscillation prevention.
These power control modifications cause the mobile and BSS to respond more effectively to
changing power level and quality conditions. This minimizes power output both for the MS and
the BSS, as well as reducing interference.
Propagation after audit
This feature provides data consistency between different BSSs with the main focus is on
synchronizing neighbor information across BSSs.
If the CELL attributes change as a result of an audit, a Neighbor Propagation is initiated to

synchronize the neighbor information across BSSs.
5-36 68P02901W01-S
Jul 2008
System Information: GSM Overview EAS relay MMI control for InCell, M-Cell, and Horizon
EAS relay MMI control for InCell, M-Cell, and Horizon
This external alarm system (EAS) relay configuration feature gives the operator the capability to
set a default relay state for the PIX relays at an InCell site, an M-Cell site or a Horizon site and
display the relay states from the OMC-R GUI.
Intelligent congestion relief
With the implementation of the Intelligent Congestion Relief feature, the existing congestion
relief procedures can benefit from the following advantages:
Faster congestion relief (non-ideal targets will not be tried).
Reduced signaling (fewer handover attempts).
Less congestion and fewer congestion relief triggers (handovers that can lead to congestion
are not accepted).
Efficient congestion control in the preferred band of a multiband network.
Supported by OMC-R GUI.
Adaptive handover
This feature allows support of adaptive handovers and optimizes type 3 and type 5 power
budget handovers from the OMC-R.
Support of BCCH and SDCCH for EGSM
This feature allows the configuration of BCCH carriers and the placement of SDCCH in the
EGSM band. This impacts the operation of non-EGSM mobiles in that they may not have service,
since they are not able to access the BCCH frequency and SDCCH channels in the EGSM band.
The support of the BCCH frequency and SDCCH channels in the EGSM band is based on an
operator defined database parameter.
The operator also has the capability to configure a standalone EGSM band cell by selecting
EGSM band frequencies.
With this feature, the operator is allowed to implement a multiband/dualband network with
EGSM as one of the supported frequency bands. It is possible for the operator to select the
EGSM band as the preferred band over the DCS1800 or GSM900 band.
In addition, this feature allows hopping systems to support the EGSM frequency band.
In a dual band system (EGSM and DCS1800), hopping is only supported within the bands
but not between the bands.
68P02901W01-S 5-37
Jul 2008
Coincident multiband boundaries Chapter 5: OMC-R Software Release Features
Coincident multiband boundaries
This feature allows operators to install new radios in a different frequency band and easily
configure multiple frequencies. The installation of new radios allows an operator to have
Multiband capabilities. The major hurdle to this type of upgrade is that the operator has already
spent significant time and money optimizing the existing infrastructure.
With the addition of a second frequency band, with different propagation characteristics, the
operator has to increase efforts to optimize the infrastructure. This is a major stumbling block
to many operators who want the capacity increase but are reluctant to configure and optimize
two frequency bands.
To circumvent this multiple frequency band issue, the new secondary frequency band
compliments the existing infrastructure. To do this, the software allows a cell with a new
frequency band to be configured with the same cell boundaries established by the original
frequency band. Also, it allows the new frequency band cells to use the handover measurement
reports based on the cells in the original frequency band.
This can be done by using mobile reported measurement reports from the primary frequency
band while a call is established on the secondary frequency band. This enables the mobile to be
handled as if it were on the primary frequency band, while not taking any primary frequency
band resources.
This feature is designed to compliment the Multiband Inter-Cell Handover feature and its use is
dependent upon Multiband being enabled.
Reporting the results of alarms recovery action
The Alarms Consolidation feature provides the operator the ability to view all state changes and
secondary alarms associated with a primary alarm in a hands free manner, that is, without the
need to search through alarm and event logs. The Reporting the Results of Alarm Recovery
Action feature, enhances this hands free operation for the end user by including information
describing the result of an alarm recovery action.
Flexible neighbor cell processing
This feature modifies the criteria for handover between neighbors. It has four main elements
that can be activated independent of each other.
Dynamic trace call flow control
The Dynamic Call Trace Flow Control feature significantly enhances the existing Call Trace
capabilities available in the BSS and is now supported by the OMC-R. The main uses for Call
Trace in GSM are fault management, optimization, and security.
A network can be optimized by analyzing call trace data that is collected from a call made by a
designated MS as it travels through the network. Call Trace can be used to locate stolen or
defective GSM equipment. Network Operators can also use this feature to determine why calls
are being dropped due to RF Loss.
5-38 68P02901W01-S
Jul 2008
System Information: GSM Overview Proxy cell autocreation
Depending on the amount of traffic between the BSS and OMC-R, the call trace flow control
techniques include:
Modifications of active call trace criteria.
Preemption of existing traces.
Controlling the number of new trace activations.
The operator can also choose whether MSC initiated call traces are exempt to the call trace flow
control mechanism.
NOTE
This feature consists of the operator enabled triggering of flow control and the
associated OMC-R GUI configuration support.
The intent of this feature is to address the outstanding issues surrounding the current Call
Trace functionality in the BSS, covering call trace usability.
Proxy cell autocreation
When the NeighbourGsmCellId is entered and the Neighbor has been initialized, if the
NeighbourGsmCellId does not exist either as a Cell or a Proxy Cell in the OMC-R MIB, the
feature informs the user that the Proxy Cell has been created using the parameters of the
neighbor created.
During a BSS-OMC-R audit, the NeighbourGsmCellIds are checked against the complete list of
Cells and Proxy Cells existing in the MIB. If the NeighbourGsmCellId does not exist a Proxy Cell
is autocreated using the NeighbourGsmCellId.
Proxy cell import/export
The Proxy Cell Synchronization feature ensures that Neighbor OMC-Rs are consistent across all
OMC-Rs managing a network by ensuring that the Proxy Cells in an OMC-R are consistent with
the original cell that exists in another OMC.
The OMC-R supplies the user with a program pcellExport that exports Neighbor-related
parameters of all cells within the OMC-R that have Neighbor relationships with cells in other
OMCs, into an ASCII file.
The user then transfers this ASCII file to all other OMCs and the pcellImport run on it.
The import programs are:

Creates Proxy Cells if there are CELLs that contain Neighbors corresponding to entries in
the file and no Proxy Cell exists. The parameters of the Proxy Cell are derived from the file.
Updates the Proxy Cells if parameters have changed.
Create/Update of Proxy Cells, results in all related Neighbors getting updated. Thus
CELL-Neighbor relationships across all OMCs are synchronized through the Proxy Cell
Export/Import mechanism.
68P02901W01-S 5-39
Jul 2008
Completion of OMC-R support for Horizonmacro Chapter 5: OMC-R Software Release Features
The OMC-R also provides a single script pcellSync that synchronizes all OMCs in one shot
without any manual intervention.
This program in turn runs export and import on all OMCs connected in the network.
Detailed feature information was not available at the time of publication. Further information is
included in the next revision of this manual.
Completion of OMC-R support for Horizonmacro
This feature provides the completion of OMC-R support for the Horizonmacro.
Q3 support
The purpose of this feature is to port the GSR4 mediation device to GSR5 to enable continued
operation of Q3 in the field.
Motorola's Q3 OMC-R Mediation device support for GSR5 includes the following:
Inter-operability testing of Q3 OMC-R interface functionality with GSR5 and BSS.
Support GPRS (PCU) specific alarms and events (GSR5).
Recognizing Motorola's leadership in Q3, further functional enhancements for our Q3

OMC-R implementation is driven and agreed by the key Q3 customers and any new generic
requirement to enhance our implementation.
DRI and combiner operability improvement
This enhancement improves the operability of the Digital Radio Interface (DRI) and Combiner
devices by increasing the flexibility with which these devices can be equipped, and unequipped.
This feature is achieved by specifying the DRIs role in system combining during the equip
of the DRI.
NHA support maximum size GSM OMC-R
This feature enables Expert Adviser (EA) Network Health Analyst (NHA) to support the
maximum size GSM OMC-R (that is, 45 k TCH).
Integration of NHA with OMC-R EM
This feature allows the OMC-R operators to view Network Health Analyst (NHA) problems
through the standard OMC-R alarm windows.
The NHA sends the problems in the correct format to the OMC-R as alarms. The OMC-R Event
Manager (EM) is able to accept the messages and deal with them as standard alarms and passes
them to the GUI for viewing and handling in the standard manner.
5-40 68P02901W01-S
Jul 2008
System Information: GSM Overview Bay level cal default data
There is a new event type on the OMC-R for the NHA to facilitate easy filtering.
Detailed feature information was not available at the time of publication. Further information is
included in the next revision of this manual.
Bay level cal default data
This feature permits operators to insert default radio values remotely.
NOTE
A site visit is required for accurate calibration of radios.
Cell parameter import or export
Cell parameter import or export enables the following:

Export of RF data from the OMC-R network into an RF planning environment.
Import of RF data from an RF planning environment into the OMC-R network.
NOTE
Current RF Planning data can be exported from the live OMC-R.
The export function generates two ASCII tab delimited files for cell and neighbor parameters
within the network.
User defines the parameters that are exported or imported. The cell file contains a list of cells,
their basics, frequencies and other information. The neighbor file contains a list of neighbors for
each cell. The file format is published and is in ASCII format. RF planning tools, for example,
NetPlan can import these files and use it to carry out a network frequency replan.
The output of the frequency replan can be imported into the OMC-R, and then used to
update the relevant network elements, new base station id codes (bsics) and frequencies are
propagated to neighbor relations.
RF Planning data import and export is carried out from the Navigation form of the OMC-R
or from the command line.
Applix 4.41 upgrade
This feature provides an upgrade of Applix from 4.3 to 4.41, so that PRs dependent on this
upgrade can be fixed. Some of these PRs are customer commitments. Applix 4.41 depends
on having an Informix 7.2 engine.
68P02901W01-S 5-41
Jul 2008
System upgrade Chapter 5: OMC-R Software Release Features
System upgrade
NOTE
This feature maintains compatibility with BSS GSR4 and GSR4.1 releases. GSR4.1
was a limited release for GPRS customers only; GSR5 contains all GSR4.1 features. It
is not possible to upgrade the OMC-R directly from GSR3 release to GSR5 release due
to the Y2K compliant release being GSR4.
The capability implies the following high-level requirements:

OMC GSR5 release can be directly upgraded from GSR4 and GSR4.1 releases.
BSS GSR5 release can be directly upgraded from GSR4 and GSR4.1 release.
OMC GSR5 release is capable of managing a network of BSSs running GSR4, GSR4.1
and GSR5 releases simultaneously.
OMC GSR5 release can be directly downgraded to GSR4 and GSR4.1 for roll-back.
BSS GSR5 release can be directly downgraded to GSR4 and GSR4.1 for roll-back.
Enhanced SDCCH to TCH assignment
An enhancement has been made to increase the success rate of assignment to a preferred
band cell, that is, going from an SDCCH in a non-preferred band cell directly to a TCH in a
preferred band cell.
Changing NE ID of Assoc_BSSs or Assoc_RXCDRs
This feature enables a recovery mechanism for Associated Transcoder/Associated BSS

(AXCDR)/(ABSS) configuration mistakes.
With the new GSR5 software release, the Enhanced XBL (EXBL) feature introduces the AXCDR
and ABSS devices.
The Dynamic Allocation RXCDR to BSC Circuits (DARBC) feature expands upon these new
devices. During initial configuration of these devices, it is possible that the operator makes a
configuration mistake which, if not caught early, can cause the operator to enter upwards of
a 100 commands to correct it. This feature enables an easy mechanism to correct an early
configuration mistake. Without this feature, the total number of commands could be (21 + 10 +
10) x 2 = 82, to make a simple, device identification number, change.
With this feature, an easy mechanism is provided to correct a mistake. The OMC-R is able to
propagate the BSS or RXCDR identifier (network_entity_id) changes to its associated BSS or
RXCDR devices and its contained devices (XBLs, CICs, and Conn_Links) by initiating a single
operation from the GUI instead of <82> or more BSS MMI commands. The GUI provides a
simple screen to rectify these configuration mistakes.
5-42 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R GUI usability
For example, the operator can select the AXCDR device whose network identifier has to be
changed and initiate the Change Assoc NE ID operation. The operator must note that a
single invocation of the Change Assoc NE ID operation changes the identifier for only one
AXCDR (or ABSS) in a BSS (or RXCDR) database. If the operator changes the identifier of the
NE, the identifier must be changed in the NEs database. The Change Assoc NE ID operation
can be invoked to change the associated device id in each database which includes the NE as
an associated device.
Consider a BSS-1 and BSS-2 which are connected to RXCDR-3. The AXCDR-3 is equipped in the
databases of both BSS-1 and BSS-2. To change the NE id of the RXCDR from 3 to 5, the operator
must change the id of the RXCDR in the RXCDR database and can then invoke the Change Assoc
NE ID operation on the AXCDR-3 at BSS-1 and BSS-2 to set the new AXCDR identifier to 5.
OMC-R GUI usability
OMC-R GUI usability has been enhanced; the new procedures can be contained within the
following five categories:
Handling Attribute Value Change Notifications from the BSS.
Better Status Bar Management on GUI windows.
Autocreation or deletion of CommsLinks during Conn_Link creation or deletion.
Support for Default BSS Naming on Detailed Views.
Enhancements to the Contained Devices Form.
Datagen support
The purpose of this feature is to support all parameter changes introduced in this release.
This is a standard activity for Datagen in each release.
68P02901W01-S 5-43
Jul 2008
Increased OMC-R neighbor statistics Chapter 5: OMC-R Software Release Features
Increased OMC-R neighbor statistics
This feature provides an increase in the volume of neighbor statistics data that can be stored at
the OMC-R, that is, the number of cells with neighbor statistics enabled.
OMC-R GUI support for PCU device object
GPRS is a service supported under GSR4.1 and GSR5 which allows for the packet-mode
transmission of data within a GSM network. Using GPRS, an MS can send and receive data in
an end-to-end packet transfer. This enables a more cost-effective and efficient use of network
resources for data transfer.
Network expansion batch capability
The purpose of this feature is to support large scale network expansion in an online or offline
environment providing a batch capability to allow for the grouping of multiple expansion
activities.
This is achieved from the Navigation Form by being able to:

Create a new BTS SITE by copying and pasting an existing BTS into a BSS configuration.
Re-parent a BTS within the same Intra-BSS or a different Inter-BSS.
Delete a BTS with its associated hardware devices and software functions in a single
operation.
Network Expansion can be performed either on the off-line MIB or OMC-R platform.
Fault management functions
In the case of online operations, the network expansion application performs mandatory
Fault Management procedures. If deleting or re-parenting a Site, then the Site is gracefully
shutdown, for example, DRIs are shutdown and RSLs are locked.
Performance management functions
For both platforms the Network Expansion application maintains Performance Management data
on devices. Specifically during a copy SITE operation, the application copies the Performance
Management configuration (enables statistics and thresholds, and so on), from the original
SITE to the new SITE. Similarly, during a re parent SITE operation the application maintains
the Performance Management configuration.
Maintenance of Performance Management is limited to those statistics configured within the

containment of a BTS SITE. Statistics configured within a BTS SITE (cell or carrier level) for
example, RF LOSSES TCH or CALL VOLUME DRI, is manipulated during Network Expansion.
Statistics outside the BTS SITE at the BSS level for example, CPU_USAGE MAX will not be
manipulated. These SITEs inherit the configurations from the parent BSS for inter-BSS
operations.
5-44 68P02901W01-S
Jul 2008
System Information: GSM Overview Increased capacity OMC-R
Increased capacity OMC-R
This feature expands the capacity of the OMC-R to cater for a higher number of receive transmit
functions (RTFs) on a single platform. The capacity is 6000 RTF (45 k TCH).
To cater for the handling of a larger network, a number of usability enhancements are included,
mostly notably the alarm deferral and split-screen alarm window option.
Increasing maximum number of trunks per BSC
This feature increases the maximum number of trunks (CICs) supported at the BSC from the
previous database limit of 1920 to a new limit of 2400. This is required to support large capacity
BSCs supporting up to 384 carriers using an aggressive Dense Urban call model (as used in
China). It was determined that a minimum of 2300 trunks are required for the Dense Urban call
model to support 384 carriers and the remaining trunks would be used for redundancy.
NOTE
These new CICs must also be known to the MSC.
This feature allows the operator to provision larger capacity BSCs in networks supporting
heavy call traffic, provided that other limitations specified in the Planning Guide have not
already been reached.
The main impacts to the subsystems in the Base Station System (BSS) for increasing the BSC
trunk limitation from 1920 to 2400 trunks are in ensuring data consistency throughout the
system. For example, increasing the number of CICs requires increasing the number of nails, so
connections can be nailed through at the RXCDR.
NOTE
A nailed control link is a fixed 64 kbps link such as an MTL or OML which passes
through the RXCDR without the RXCDR having any impact on that link, it is simply
being used as a medium to get the control link to the destination. This medium is
called a nail.
In order to achieve 384 carriers for the BSC on the Dense Urban Call model (the primary
motivation for this feature), the following assumptions regarding the BSC are made:
Support of two Message Transfer Links (MTLs) per Link Control Function (LCF) at 40%
MTL link utilization.
Support of 25 LCFs.
GPROC2 processing is approximately four times that of a GPROC.
NOTE
Increasing the number of trunks limit does not provide value for Dense Urban
environments unless these assumptions hold true.
68P02901W01-S 5-45
Jul 2008
Expansion or de-expansion Chapter 5: OMC-R Software Release Features
Expansion or de-expansion
This feature enables the capacity of the OMC-R to cater for a higher number of TCHs.
The lowest level is a 5 k TCH system which can be expanded to a 10 k or 30 k TCH system. The
30 k TCH can be expanded to 45 k TCH system. In ascending order there are four available
TCH sizes:
5 k TCH (low-end)
10 k TCH (mid end)
30 k TCH (mid end)
45 k TCH (high-end)
Vanguard software upgrade support
Motorola's Information Systems Group, Network Systems Division (NSD), in its commitment to
provide the highest value wide area multimedia access solutions, provides upgrade support for
all routers. Software in the field is upgraded to the latest Vanguard router software.
Support for Vanguard 6455 router
Motorola's Information Systems Group, Network Systems Division (NSD), in its commitment
to provide the highest value wide area multimedia access solutions introduces the Vanguard
6455 router (software and hardware). The Vanguard 6400 Series from Motorola provides
multi service EDGE networking solutions for multimedia, IP, and serial traffic simultaneously
over the WAN.
5-46 68P02901W01-S
Jul 2008
System Information: GSM Overview Removal of the clear stats command
Removal of the clear stats command
The clear_stats command is no longer supported in GSR5.
PCU alarms detected by HSC
Provides software functionality to enable detection of PSU failures on a PCU cage. When a
failure is detected, an alarm is raised, and the operator notified. The alarm status is also
reflected through the LED indicators (when activated) on the PCU alarm panel board.
68P02901W01-S 5-47
Jul 2008
OMC-R software release GSR5.1 Chapter 5: OMC-R Software Release Features
OMC-R software release GSR5.1

GSR5.1 features
Table 5-16 summarizes the OMC-R features supported by software release GSR5.1.
Description
Web MMI
GPROC fast reset
Unequip TCU/CTU Cabinet
WebMMI
The Web MMI is a new feature which provides a remote service to any user who has access to
the network that a PCU resides on. Through the Intranet, and the availability of the PCU cage
and its Ethernet capability, the BSS can be monitored and maintained.
NOTE
The functionality that is offered consists only of the functionality that the Operation
and Maintenance Man Machine Interface (MMI) and the Executive Monitor (EMON)
provide for a single BSS, as opposed to the functionality that the OMC might provide
as a whole.
The OMC-R to BSS interface is updated to include the new database parameters allow_32k_trau
as well as the new and modified statistics.
The allow_32k_trau parameter is restricted by the GPRS restrictable feature and the 32k
TRAU CS3/CS4 restrictable feature and can only be used if the GPRS and 32k TRAU CS3/CS4
features are unrestricted. Additionally, the dynamic allocation of terrestrial resources feature
must be disabled for any sites using GPRS. This parameter prevents GPRS usage on RTFs that
are sub equipped in the database. This parameter can only be enabled if max_gprs_pdch
is set to a non-zero value. Additionally, if allow_32k_trau parameter is enabled, the value
of max_gprs_pdch cannot be set to zero without first disabling allow_32k_trau. Perform
the verifications to ensure that there are enough terrestrial resources available when
max_gprs_pdch is increased and allow_32k_trau is enabled.
5-48 68P02901W01-S
Jul 2008
System Information: GSM Overview GPROC fast reset
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:
PCU sites from Navig
PCU sites from SITE
PCU sites from Contaform
PCU sites from Map
Unequip of TCU/CTU cabinets
This feature enables support for the unequipage of extension cabinets of types TCU_2, TCU_6
and Horizonmacro_ext at M-Cell, and Horizonmacro sites without having to unequip the site.
This action can be done provided that the cabinet is locked and there are no DRIs or EASs
equipped to the cabinet. This feature does not support all other cabinet types.
68P02901W01-S 5-49
Jul 2008

GSR6 features
Description
Geographic command partitioning and region support.
Enhanced circuit error rate monitor.
OMC-R GUI usability for large network support.
Enable cyclic neighbor statistics.
Online network expansion - phase 3.
Cell Xchange.
Geographic command partitioning and region support
Feature overview
The feature enables operators to set up geographical regions, populate these regions with
network elements (Base Station System (BSS) and Remote Transcoder (RXCDR)) and assign
read and/or write access for these regions to individual users.
Feature description
As the networks grow in size, the amount of information available to the operator is increased.
The feature provides a method of reducing the amount of data visible to the operator by allowing
them to subscribe to a defined set of network elements. This provides each Operation and
Maintenance Center-Radio (OMC-R) operator with a sub network for them to manage.
The feature provides a mechanism for defining geographic regions. Network elements (BSS and
RXCDR) can be added to these regions to represent sub networks. Once the regions are set
up, the system administrator has the ability to create, modify and remove access controls to
particular regions for each operator.
5-50 68P02901W01-S
Jul 2008
System Information: GSM Overview Geographic command partitioning and region support
All operator-specific security-related information is stored in that operator's security file.

(This allows the OMC-R administrator to limit the access of each OMC-R operator to certain
geographical areas based upon the NEs to which the operator is given access).
The security administrator is able to:

Create an operations access control group.
Delete an operations access control group.
Modify an operations access control group's properties.
Copy an operations access control group's properties.
Add operations to an operations access control group.
Delete operations from an operations access control group.
Assign an operation to one or more operations access control groups.
Copy a user profile data record.
Help is provided for the command partitioning feature.
Benefits
This feature permits network operators to create geographical domains over which specific
operators have control. The restricted user access provides a level of security to ensure that
only authorized users can access certain geographical areas. The ability to manage multiple
networks on one OMC-R reduces the cost of ownership of the networks.
Applications
This feature finds application in those networks where control of the network is exercised in
geographic regions.
Compatibility/dependencies/network elements affected
The GSR6 version of the OMC-R supports the Geographic command partitioning and region
support. No changes are required to the network elements.
68P02901W01-S 5-51
Jul 2008
Enhanced circuit error rate monitor Chapter 5: OMC-R Software Release Features
Enhanced circuit error rate monitor
Feature overview
The original Circuit Error Rate Monitor (CERM) optional feature provides a means for
identifying when discontinuity is detected on a circuit. The customer can:
Reduce cost of ownership.
Reduce downtime of devices.
Enhance system operability.
Enhance quality of service.
A circuit is considered to be the path along which a connection is made, from the entry point in
the BSS (for example, a radio at the BTS) to the exit point in the BSS (for example, the MMS
timeslot that connects to the MSC or PCU).
The CERM is used to monitor the continuity and sanity of hardware processing elements in a
circuit, on a per call basis. Whenever a discontinuity is detected for a circuit during a call, error
counts are updated for the points monitored for the call. When the error count at a particular
monitoring point reaches or exceeds an operator specified threshold, an alarm is generated.
The alarm contains information identifying the monitored path in which the error is detected,
thus allowing the operator to identify potentially faulty devices.
Feature description
The CERM feature is enhanced enabling the monitoring at various points in a GSM network
circuit, thus improving the ability of an operator to narrow down where a faulty device is
located. Although having these monitoring points in the circuit path narrows down the list of
potentially faulty devices, it does not conform that a device is faulty. It is still up to the operator
to determine which device is faulty.
The following points in a network can be monitored on a per timeslot basis:

Circuit Identity Code (CIC) on a link between the RXCDR or BSC and the MSC.
ATER Channel Identifier (ACI) groups on a link between the RXCDR and the BSC.
GPRS Circuit Identifier (GCI) group on a link between the BSC and the PCU.
Radio Channel Identifier (RCI) in the radio hardware.
Path Identity Code (PIC) on a link between the BSC and a BTS.
The PIC is a special case because it is measured on a from-BSC-to-site basis. For example, with
a path leading from a BSC to two daisy chained BTSs, the PIC for the second BTS encompasses
the path through the first BTS to the BSC.
5-52 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R GUI usability for large network support
OMC-R GUI usability for large network support
Feature overview
This feature aims to provide an enhanced Graphical User Interface (GUI) and tools. The GUI
and tools enable the operator to help operate and maintain large networks with relative ease.
The main enhancements are described below:
Neighbor Reciprocity: Previously, a significant number of cells in a network exhibit
neighbor reciprocity. This means that if cell A is a neighbor of cell B, then cell B must be a
neighbor of cell A (two-way relationships).
Enhancements to the OMC-R to view reciprocal relations between cells in the OMC-R, add
or drop reciprocal neighbors enable operators manage large networks with greater ease.
The source neighbor view is also now enhanced to provide the user with information
about neighbor reciprocity.
Auto Reciprocation of Neighbors: Since most cells in a real network exhibit Neighbor
reciprocity, the user now has the option of auto creating the reciprocal Neighbor when a
neighbor is created.
Enhanced Find: The find form option is enhanced to support search for parameters. The
user is able to locate the container of the given parameter name.
Feature description
The OMC-R now supports the following enhancements to the GUI and Configuration
Management Information Base (CM MIB):
Neighbor reciprocity and enhancement source neighbor view
The OMC-R GUI is enhanced to provide a menu option on the navigation tree. The menu option
lets the operator view all sources (cells in which mobile phones are located) and neighbors for
cells in the network being managed by the OMC-R.
The new GUI screen is an enhanced version of the source neighbor view. The new view enables
the user to add or remove neighbors and sources and hence manage reciprocal relations.
The OMC-R also enables fully automated creation of reciprocal neighbors with an environment
variable, since most of the neighbors in a practical network are two-way neighbors.
The ProxyCell synchronization processes are extended to synchronize sources along with
neighbors between OMC-Rs so that the correct cross OMC-R reciprocal relations are presented
to the user.
Autocreation of reciprocal neighbor during neighbor creation
The OMC-R now provides the user the ability to reciprocate neighbors if they wish to during
the equipage of the neighbors. The user is also able to specify, on a per neighbor basis, if it
can be reciprocated or not.
68P02901W01-S 5-53
Jul 2008
Enable cyclic neighbor statistics Chapter 5: OMC-R Software Release Features
Enhanced find
The OMC-R GUI is enhanced to let user find the container of the given parameter. The find form
option also supports the task of find attributes (parameters) in addition to the find devices option.
Enable cyclic neighbor statistics
Feature overview
The BSS and OMC-R were restricted in their ability to provide full neighbor statistic coverage to
the network operators. These limitations were based on hardware and processing limitations.
This feature introduces the ability to traverse the OMC-R network automatically on a per BSS
basis and enable the neighbor statistics in rotation.
The feature also provides the operator with the ability to enable statistics based on analysis
carried out by the Network Health Analyst (NHA) and create a list of their own favorite cells for
enabling.
Online network expansion - phase 3
Feature overview
The network expansion phase 3 feature extends the functional capabilities of the network
expansion phase 2 feature delivered in GSR5.
Feature description
The Online Network Expansion - Phase 3 feature provides the following enhancements:
Daisy chain support
The Network Expansion Copy-SITE, Delete-SITE and Re-parent-SITE operations are enhanced
to facilitate the insertion or deletion of a Base Transceiver Station (BTS) within a static daisy
chain Base Station System (BSS) configuration.
A stand-alone functionality, referred to as the Path Configure handles the path dependencies.
It is also possible to invoke the Path Configure from the Navigation Tree Configuration
Management menu, for any given site that is not within a DYnamic NETwork (DYNET) device.
The Path Configure enables the operator to un-equip the devices temporarily, to delete paths,
to create new paths and to re-equip the devices with their original settings. Network Expansion
invokes the Path Configure when it determines that the operation selected by the user involves
a site within a daisy chain.
5-54 68P02901W01-S
Jul 2008
System Information: GSM Overview Cell Xchange
Scheduler functionality for CellChange
The network expansion scheduler is expanded to include the possibility of scheduling a

CellXChange operation and both a Cell-X-Import operation and Cell-X-Export operation.
Benefits
The main benefit of this phase of network expansion is to improve the feature applicability by
introducing daisy chain support. It also extends the scheduler functionality by adding support
for CellXChange.
Cell Xchange
Feature overview
This feature is an extension of the RF Planning Interface feature (RDB 3416) and of the Cell
Parameter Import Export Feature (RDB 3780). It now allows the user to export and import
SITE/RTF/DRI parameters for direct amendment, as previously for CELL parameters. The
specific parameters to export/import are configurable by the user. The name of the configuration
file is:
/usr/omc/config/global/RF.CNFG
This feature is available both on the Offline Management Information Base (MIB) and on the
Operation and Maintenance Center-Radio (OMC-R) providing a mechanism to make large
scale changes online.
68P02901W01-S 5-55
Jul 2008
OMC-R software release GSR6 (Horizon II) Chapter 5: OMC-R Software Release Features
OMC-R software release GSR6 (Horizon II)

GSR6 (Horizon II) features
Table 5-18 summarizes the OMC-R features supported by software release GSR6 (Horizon II).
Table 5-18 Release GSR6 (Horizon II) features
Description
Support for new UNIX server
Support for new UNIX server
Feature overview
From GSR6 (Horizon II) Volume Deployment onwards, a new OMC platform replaces the
existing OMC-R platform.
Two new server types are introduced:

Netra 20
SunFire 4800
The Netra 20 is intended for smaller configurations of up to 45000 TCH, while the SunFire 4800
platform is for larger configurations of up to 60000 TCH.
5-56 68P02901W01-S
Jul 2008
System Information: GSM Overview Support for new UNIX server
Netra 20 OMC-R platform
Netra20 is used in configurations of up to 45000 TCH. The platform comprises a Netra 20 server
with two 900 MHz CPUs, 2 Gb memory, two I/O controllers and two HSI/P cards. An external
disk array of twelve 36 Gb disks is attached.
Figure 5-1 GSM OMC-R hardware configuration for up to 45 k TCH
68P02901W01-S 5-57
Jul 2008
Support for new UNIX server Chapter 5: OMC-R Software Release Features
SunFire 4800 OMC-R platform
This platform comprises a SunFire 4800 server configured as a single domain. There are four
900 MHz processors on two CPU boards, providing a total memory of 4 Gb. The system also
comprises dual differential SCSI interfaces, dual HSI cards, and quad fast Ethernet cards for
I/O. An external disk array of twelve 36 Gb disks is attached.
Figure 5-2 GSM OMC-R hardware configuration for up to 60K TCH
OMC-R GUI server
The OMC-R GUI platform comprises a Sunblade 150 server with 650 MHz CPU, 1 GB RAM,
and two internal disks.
5-58 68P02901W01-S
Jul 2008

GSR7 features
Description
Cell Xchange - BSS Support.
Network Expansion - Phase 4.
Performance Enhancements for GPRS.
Web Access Server.
Cell Xchange - BSS support
Feature overview
The Cell Xchange - BSS support feature is an extension of RDB4301 Cell XChange introduced
in GSR6.
This feature enables user-configurable BSS parameters to be imported and exported, and is
available on both the Off-line MIB and the OMC-R.
Network Expansion - Phase 4
Feature overview
The Network Expansion - Phase 4 feature extends the functionality of Network Expansion -
Phase 3 introduced in GSR6.
This feature contains the enhancement Support for timeslot switch in PATH configure.
Where a Radio Transceiver Function (RTF) or Radio Signaling Link (RSL) are equipped against
a PATH containing a Timeslot Switch (TS) or adjacent Timeslot Switches, this enhancement
enables the RTFs and RSLs to be equipped on timeslots on Multiple Serial Interface Links
(MMSs) connected directly to the TS.
68P02901W01-S 5-59
Jul 2008
Performance Enhancements for GPRS Chapter 5: OMC-R Software Release Features
Performance Enhancements for GPRS
Feature overview
The Performance Enhancements for GPRS feature is an extension to the General Packet Radio
Service (GPRS) feature introduced in GSR4.1 and the Coding Scheme 3/Coding Scheme and
Interleaving TBFs features introduced in GSR6.
It also provides support for the GSR7 features GPRS Seamless Cell Reselection, Enhanced
Scheduling and PBCCH/PCCCH. Performance Enhancements for GPRS is a combination of
four sub features:
Cell Partitioning
Delayed Downlink TBF Release Duration as a function of Cell Availability
Configurable Initial Downlink and Uplink Coding Scheme
Scheduling algorithm Beta 0 and 2
Feature description
Cell Partitioning
Packet Resource Processor (PRP) capacity and data traffic are increased in the Enhanced
Scheduling feature, and Seamless Cell Reselection between PRP boards introduces new data
through PCI backplane of the PCU.
Cell Partitioning is a software modification that reduces backplane traffic to prevent system
overload. It places the critical data for maintaining the synchronous radio link within a single
slot, and passes the larger more efficient Gb packets over the backplane.
The software processes that work with the TRAU data are repartitioned. The packetization
process is relocated to the PRP and is merged into the scheduling process to facilitate data
transfer with low overhead. The TRAU type GDS is equipped on PRP board, and data path
latency is minimized. Processor overhead of the messages on the bus is reduced, and the
recovered CPU time is used for scheduling or increased capacity.
Delayed Downlink TBF Release (DDTR) duration as a function of Cell Availability
The feature Interleaving TBFs introduced the parameter delay_dl_rel_dur to set the downlink
Temporary Block Flow (TBF) release duration.
As the number of simultaneous calls in a GPRS cell increases, a large percentage of mobiles
with assigned downlink resources are in delayed downlink TBF release mode with no actual
downlink traffic. The PCU scheduler assigns up to a maximum of four mobiles per PDCH,
and any additional mobiles requesting allocation are blocked until an existing TBF ends. The
longer the delayed downlink TBF release duration, the greater the possibility of new mobiles
requesting access in a cell being blocked. Mobiles in delayed downlink TBF release mode for an
extended period can be terminated, but this takes at least 500 msec (or T3193 period).
To reduce the possibility of mobiles being blocked, the scheduler in the PCU monitors the
availability of timeslot resources in the cell, and terminates downlink TBFs in delayed downlink
release mode before the cell is blocked. The delay_dl_rel_dur parameter determines the
maximum duration and ranges from 300 msecs to 10 seconds, with a typical value of 1 second.
5-60 68P02901W01-S
Jul 2008
System Information: GSM Overview Performance Enhancements for GPRS
Cell availability is calculated and monitored when timeslot resources that take a mobile from
idle to transfer state are assigned, and when release procedures are initiated that return the
mobile to idle state. If the availability is less than the threshold, the scheduler selects one or
more downlink TBFs in delayed release mode to terminate. The criteria for termination of
TBFs comprises no uplink TBF in progress and a duration of at least 300 msecs in delayed
release mode.
The downlink TBF establishment duration is minimized if a Packet Downlink Assignment is sent
on the PACCH while uplink TBF is in progress.
If no downlink TBF exists for a mobile while releasing the uplink TBF, the uplink TBF can be
extended by delaying the final PUAK by a configurable number of block periods.
Configurable Initial Coding Scheme
Before GSR7, all downlink and uplink TBFs used Coding Scheme 2 (CS-2). This feature enables
the initial downlink coding scheme to be set to improve throughput of cells in which all the
mobiles are capable of higher coding schemes.
The initial coding scheme is only set for TBFs with local Temporary Logical Link Identities
(TLLIs). Coding Scheme-2 is used for TBFs with non-local TLLIs, and when the carrier or PDCHs
assigned for the TBFs are not capable of the initial coding scheme CS-3 or CS-4.
The TLLI Block Coding Scheme in one-phase uplink TBFs is always set to CS-1 to ensure the
contention resolved quickly.
Scheduling Algorithm Beta 0 and 2
This parameter determines the extent of system efficiency against fairness among the users.
Share of throughput for each user is determined by using the current coding scheme (CS)
information to allocate the available bandwidth among the active users with established TBFs.
The scheduling algorithm Beta gprs_sched_beta parameter introduced in the GSR6

Interleaving TBFs feature only supports the value 1, that is, each mobile is assigned to transfer
the same number of radio blocks as every other mobile. This feature adds the following values:
0 Each mobile throughput is the same. This allocates radio blocks so that each mobile
has the same throughput in bits per second (bps), thus providing maximum fairness to all
mobiles.
2 This favors mobiles with higher coding scheme, providing maximum overall throughput.
68P02901W01-S 5-61
Jul 2008
Web Access Server Chapter 5: OMC-R Software Release Features
Web Access Server
Feature overview
The Web Access Server feature provides OMC functionality remote from the management
center. It enables consolidation of OMC operation to a single location without the need for a
full Network Management Center (NMC), or alternatively allows OMC operators to manage
multiple OMCs remotely.
Operators are not restricted to dedicated OMC terminals, and can carry out multiple tasks
from a single workstation.
The use of web browser access allows operators to achieve flexibility in their operator terminal
architecture. The web access interface exactly replicates the standard OMC screen, preserving
full OMC functionality.
Netra 20 Web Access platform
The Web Access Server platform is a Netra 20 or similar with the following specification:
2 x 900 MHz CPU
8 GB RAM
2 x 73 Gb disk (internal)
The Web Access Server software connects to GUI servers running GSR6 onwards. The
supported browsers are
Netscape Navigator 4.61, 4.7x, and 6.x
Internet Explorer 4.01, 5.0, 5.01, 5.5, and 6.0
5-62 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release GSR7 (GSM Half Rate)
OMC-R software release GSR7 (GSM Half Rate)

GSR7 (GSM Half Rate) features
Table 5-20 summarizes the OMC-R features provided at software release GSR7 (GSM Half Rate).
Table 5-20 Release GSR7 (GSM Half Rate) features
Description
GSM Half Rate
GSM Half Rate
Feature overview
The GSM Half Rate (GSM-HR) feature provides enhanced capacity over the air interface,
corresponding to the proportion of mobiles that supports HR within a coverage area. An air
timeslot is split into two sub channels, each containing an HR channel.
The GSM OMC-R supports GSM-HR as a restricted optional feature on the BSS and RXCDR.
In addition the GSM OMC-R allows the operator to enable or disable GSM-HR on a per BSS
and per CELL basis.
The GSM-HR feature builds on the AMR-HR feature. It introduces new attributes and associated
groups to configure GSM-HR and modifies a number of existing AMR-HR attributes making
them generic. The Detailed Views affected are the BSS, Cell, and RTF. It also introduces and
modifies a number of statistics to enable the Performance Management Reporting of the
GSM-HR. The feature also supports an additional Alarm to inform the Operator of problems
enabling both GSM and AMR Half Rate at the NE.
68P02901W01-S 5-63
Jul 2008

summarizes the OMC-R features supported by software release GSR8.
Table 5-21 OMC-R features for GSR8
Description
User Barred Cell
Intelligent Audit
120K TCH OMC - Capacity Expansion
Upgrade OS to Solaris 2.9
Channel and Circuit Status (CACS)
User Barred Cell
Feature description
The User Barred Cell feature enables the user to see the list of cells that are currently barred.
The scope can be set to Network/Region/NE/Site. This list is presented to the user in a new
GUI Screen.
The list is dynamically updated. If the barring status is updated while the list is open, the same
changes will be reflected in the list.
Single or multiple cells can be selected from this list and can be unbarred as a single menu
operation. Double clicking on any cell in the list opens the detail view of the User Barred cell.
5-64 68P02901W01-S
Jul 2008
System Information: GSM Overview Intelligent Audit
Intelligent Audit
Feature description
This feature enhances the existing Audit functionality. The major enhancement is to facilitate
the user to intervene on pending and blocked-pending scheduled audits.
This feature also provides information on the time of the last audit gather and audit apply
operations performed on a Network, Region, BSS, SITE, RXCDR, and PCU.
Users can also traverse the Navigation Tree opening Detailed Views for devices in read mode
during the audit/apply phases. The intelligent audit feature has also had some of the menu
options that were only available in the audit inconsistency list brought forward to the audit logs
window. This allows users to apply audit inconsistencies without the need to open the audit
inconsistency window. The options that are now also available on the Audit Log window are
Apply to OMC under the Options menu, and an additional menu named Display has also been
added. Five options are available under it, namely: All, Success, Others, Error, and Failure.
120K TCH OMC - Capacity Expansion
Feature description
The 120K TCH OMC-R feature expands the capacity of the GSM OMC-R to support a maximum
of 120K Traffic Channels and/or a maximum of 254 Network Entities. This feature does not
affect the BSS.
The 120K Traffic Channel feature comprises five sections:

Characterization
Usability
Resync
MIB Locking
Multi NE Audit
The supported platforms for 120K are a SunFire4800 System Processor, SunFire4900 System
Processor, and a SunBlade150 GUI Server.
68P02901W01-S 5-65
Jul 2008
120K TCH OMC - Capacity Expansion Chapter 5: OMC-R Software Release Features
Characterization
Allows the OMC-R to support up to 120,000 Traffic Channels and 254 NEs. Increases the
limitations on specific system parameters:
Increase in the number of simultaneous downloads to 36 per X25 link.
Increase in the number of remote login sessions supported to 90 (default 60).
Increase in the number of simultaneous gui sessions to 60.
Increased event logs supported to 15 on 120K platforms.
Increase in the number of alarms stored in the active event table (AET) to 12,000 alarms.
Increase in the number of invoked call traces to 40000.
NOTE
Increases in system parameters are only available on 120K platforms.
Alarm and state initialization now occur within the initialization progress dialog.
Usability
Allows enhanced Region and Find support to manage the increase in the TCH and Network
Elements supported. For example:
Audit can be performed on a region.
The events window can be opened on a region.
Enhanced Region support.

The following operations can now be performed on a region.
Audit
Resync
Cell Propagation
Cell-X
The following windows can now be opened for a region.

Alarms
Events
OOS devices
Events with history
5-66 68P02901W01-S
Jul 2008
System Information: GSM Overview 120K TCH OMC - Capacity Expansion
Resync
Allows Network and Region Resync operations to occur in parallel.
MIB Locking
Allows Configuration Management operations to occur in parallel, therefore no longer locking

the network when a Configuration Management operation is in progress.
Two types of locking are now available Intelligent and Global (backward compatible) locking.
Allows operations that affect devices not contained by a Network Element to progress without a
lock. For example, Organize Nodes for the Map will no longer produce a lock.
Two new system parameters are added:

MAX_CM_OPS defines the max number of locked NEs, above which no new configuration
management operations that require a lock on an NE can be started.
MAX_CMUTIL_OPS defines the maximum number of Cmutil operations allowed in parallel.
Two new scripts are added as part of the MIB Locking feature:
LockUtility allows a user to monitor the locks on the system. When executed the script
lists all locks on the system. When executed as omcadmin the LockUtility allows users to
remove locks.
CheckValidLockPID script is set up to run every 15 minutes, it checks to see if there are
any dead locks on the system and removes them.
MIB Locking is available on all supported platforms not just 120K platforms.
NOTE
For more information on the MIB Locking feature refer to the manual Operating
Information: OMC-R System Administration (68P02901W19).
68P02901W01-S 5-67
Jul 2008
Upgrade OS to Solaris 10 Chapter 5: OMC-R Software Release Features
Multi NE Audit
The Multi NE Audit feature allows users to select two or more BSSs/RXCDRs and initiate
an audit on those selected Network Elements, which decreases the time taken for an
Audit Gather to complete.
The Audit Gather phase for each NE of a network audit now runs in parallel.
Users can schedule audits for multiple BSSs/RXCDRs and multiple SITEs.
A new menu item, Audit Progress, is added to the Edit menu of the Audit Log window. This
displays the Element Name, the Status, the Actual Start Time and the Actual End Time.
A new menu item, NE List, is added to the Edit menu of the Audit Scheduler window. This
displays the name of network elements that the scheduled audit is running on.
Multi NE Audit is available on all supported platforms not just 120K platforms.
NOTE
For more information on the Multi NE Audit feature, refer to the manual Operating
Information: OMC-R System Administration (68P02901W19).
Upgrade OS to Solaris 10
Feature description
Upgrade of OMC platform from SUN Solaris 9 to Solaris 10.
The OS upgrade applies to the core OMC platform plus ALL related platforms such as NHA,
Datagen, Corba server, Web Server, GUI Servers, and so on.
Additional security hardening is implemented on the OMC platform to take advantage of

security features delivered in Solaris 9. All relevant third-party products are upgraded in line
with the operating system upgrade.
5-68 68P02901W01-S
Jul 2008
System Information: GSM Overview Channel and Circuit Status (CACS)
Channel and Circuit Status (CACS)
Feature description
The new GSR8 CACS feature replaces the Wingz feature familiar to users with previous OMC-R
releases.
The Circuit Status dialog enables users to monitor timeslot usage on an MMS link, and also to
view the status of all eight timeslots on an RTF carrier. These dialogs are refreshed on a periodic
interval which is set by the user. Each refresh operation results in an invocation of a BSS
command to a network element and the parsing of information returned by the network element
via the Remote Login process. OMC-R users can use both dialogs for diagnostic purposes.
The Circuit Status dialog provides a GUI front end to the BSS MMI commands
disp_mms_ts_usage and disp_rft_channel.
The disp_mms_ts_usage command is issued to the BSS when the Circuit dialog is launched
from an MMS or when this dialog is refreshed periodically or on demand.
The disp_rft_channel command is issued to the BSS when the Channel dialog is launched
from an RTF or when this dialog is refreshed periodically or on demand.
The parameters required for these commands are gathered from the selected node. The
corresponding generated MMI commands are sent to the Remote Login process. The Remote
Login process then executes the command at minimum intervals of 15 seconds, this interval is
configurable by the user. The results are sent back to the front-end, parsed, and displayed on
the front-end GUI dialogs.
68P02901W01-S 5-69
Jul 2008
Feature Capacity Licensing and Audit Chapter 5: OMC-R Software Release Features
Feature description
The License Audit tool introduces a mechanism to monitor the usage of the carriers across the
customer network on a per feature basis. Information is gathered by running scheduled audits
against the OMC-R Configuration Management database to produce a report indicating how
many RTF(s) are equipped in the database to support each feature. This feature extends the
License Audit only functionality to provide license file comparison and customer notification
of license overruns.
Each software release has a list of features that are monitored for carrier capacity usage. The
OMC software triggers the License Audit tool at pre-defined intervals, which can be configured
by the customer.
The License Audit tool will be extended on each release to incorporate new features in the audit
functions. For each customer a license file is issued which contains the information on current
licensed capacity for every licensable feature. A single license key is provided to control this
information per network.
The License Audit Tool is distributed with the OMC software and installed and configured by
the user. The audit is triggered by a configurable interval parameter in the OMC software. If
the interval parameter is not set, or set outside the permissible range [2 hours, 48 hours],
the default value of 12 hours is used. The result of the audit (actual usage) is compared with
the license file per feature. An alarm is generated when the carrier usage for one or more
features exceeds the carriers purchased for those features. If the usage is within the limit, the
License Audit Tool generates an event which indicates that the carrier usage is within the
license purchased. The alarms and events are displayed at one or all OMC(s) in the network as
previously configured during installation and configuration.
The License Audit Tool produces a report which is stored in a predefined location containing the
result of the latest audit and license file comparison. Users and Motorola have access to this
report by physically accessing the location where the file is stored.
5-70 68P02901W01-S
Jul 2008

Table 5-22 OMC-R features for GSR9
Feature Description
{25663} Implementation of Secure Services on Solaris based O and M
products.
{27508} BSS User Security Management.
{27751} 3GPP Release 6 Performance Management IRP 2G.
{27752} 3GPP Upgrade to Release 6 for 2G element manager FM and
CM functionality.
Implementation of Secure Services on Solaris based O and M

products
{25663}
Feature description
This feature replaces the older insecure Solaris services such as rsh with more secure ssh
versions. All UNIX based platforms are updated: OMC-R, GUI server, GUI client, NHA, Corba
server, and Web access server.
OMC-R and NHA sysadmin disable all insecure services such as, telnet, rsh, rlogin, rcp, and ftp
and replace them with more secure services such as ssh, scp, and sftp.
The OMC-R currently has a facility for users to rlogin directly to the BSC. This is not related to
the standard UNIX rlogin., Hence, disabling the UNIX rlogin command does not impact this
facility. Therefore, there is no impact on BSC or BTS.
BSS User Security Management
{27508}
Feature description
The BSS User Security Management feature provides enhanced user security functionality to a
customer network, by providing the operator with the ability to define individual usernames
and passwords for BSS access from the OMC-R, and also locally at the BSS TTY. This provides
information about the users logged into the network through their username and ID. The
usernames and passwords have standard password control features such as complexity
checking, ageing and storage in encrypted format, and are managed from the OMC-R.
68P02901W01-S 5-71
Jul 2008
BSS User Security Management Chapter 5: OMC-R Software Release Features
A user profile is associated with each username, which provides controlled access to a
partitioned command set at the BSS. Both standard BSS commands and EMON commands are
partitioned. The OMC-R administrator can create a username and assign a profile to each user
which defines the BSS and EMON command sets that the user can access at the BSS.
A user is authenticated at the OMC-R whenever logging in using a UNIX account setup by
OMCADMIN. The UNIX login details are compared to an NE user list held at the OMC-R, to
determine which NEs the user has access rights to if it is needed to access the remote network
while logged on to the OMC-R.
There are two types of user accounts maintained as part of the feature implementation:
NE User Account: This is the normal user account which has to be maintained and
managed at the managing OMC-R, and is identified with the OMC-R user having a UNIX
login ID and password ( unixid / unixpasswd ) on the splat server. The OMC-R administrator
is able to create a username and assign a profile to the user which defines the BSS and
EMON command sets that the user can access at the BSS. The omcadmin user can set a
NE access level for a NE user account and when the user login to OMC they will be placed
at that access level. The default NE access level for the omcadmin and non omcadmin
user is 4. The NE user account passwords expire after a certain age set at the UNIX
and can also be blocked.
NE Field Engineer Account : This account is used only when a field engineer physically
visits a Site. The fieldeng2, fieldeng3, fieldeng4 accounts are meant only for qcomm or
local login purposes. The fieldengX accounts are meant only for qcomm purpose. These
account passwords never expire. Also blocking is not supported for these passwords. They
can also be used when the OML is up or down and is configurable from NE.
Three field engineering accounts will be maintained at BSS as follows :

fieldeng2 mmi access_level = 2 , emon access_level = 0
fieldeng3 mmi access_level = 3 , emon access_level = 1
fieldeng4 mmi access_level = 4, emon access_level = 2
NOTE
emon_access_level 0 means no access to the EMON commands.
MMI alarm window displays a new alarm - FieldengPassChangeAlarm generated by the

OMC-R, when the field engineer account passwords have not been changed for a specified
number of days.
5-72 68P02901W01-S
Jul 2008
System Information: GSM Overview 3GPP Release 6 Performance Management IRP 2G
3GPP Release 6 Performance Management IRP 2G
{27751}{27752}
Feature Description
This feature upgrades 3GPP functionality to Release 6 compliance.
Fault Management IRP (Integration Reference Point), Bulk Configuration management IRP and
State management IRP features are all upgraded to be Release 6 compliant. In addition, the
Performance Management file is also upgraded to be Release 6 compliant.
The following IRPs are required for GSR9:

Entry Point IRP (Release 6)
Performance Management IRP (Release 6)
Communications Surveillance IRP (Release 6)
Kernel Configuration Management IRP (Release 5 and Release 6)
Bulk Configuration Management IRP (Release 5 and Release 6)
File Transfer IRP (Release 6)
NBI Fault Management (Release 5 and Release 6)

In addition to the above IRPs, the GSR9 Network Resource Models (NRM) adheres to the
following NRM standards:
GeranNRM (Release 6)
GenericNRM (Release 6)
StnNrm (Release 6)
UtranNRM (Release 6)
NOTE
The upgrade to the latest NBI Core partner release of GSR9 requires a clean install.
68P02901W01-S 5-73
Jul 2008
3GPP Release 6 Performance Management IRP 2G Chapter 5: OMC-R Software Release Features
5-74 68P02901W01-S
Jul 2008
Chapter
Glossary of Technical Terms

This chapter provides a glossary of technical terms, standard Motorola acronyms, and
abbreviations used throughout the documentation set.
68P02901W01-S 6-1
Jul 2008
Glossary of technical terms Chapter 6: Glossary of Technical Terms
Glossary of technical terms

A Interface - AUTO
A Interface Interface between MSC and BSS. The interface is based on

the use of one or more E1 digital links. The channels on
these links can be used for traffic or signaling.
A3 Authentication algorithm that produces SRES, using RAND
and Ki.
A38 A single algorithm performing the function of A3 and A8.
A5 Stream cipher algorithm, residing on the MS, that produces
ciphertext out of plaintext, using Kc.
A8 Ciphering key generating algorithm that produces Kc using
RAND and Ki.
AB See Access Burst.
Abis interface Interface between a remote BSC and BTS. Motorola offers
a GSM standard and a unique Motorola Abis interface. The
Motorola interface reduces the amount of message traffic
and thus the number of 2 Mbps lines required between BSC
and BTS.
ABR Answer Bid Ratio. The ABR is the ratio of successful calls
to total number of calls. As a measure of effective calls, it
reflects the performance of the total network.
ac-dc PSM AC-DC Power Supply module.
ac Alternating Current. In electricity, ac occurs when charge
carriers in a conductor or semiconductor periodically reverse
their direction of movement. Household utility current in
most countries is ac with a frequency of either 50 hertz or
60 hertz (complete cycles per second). The RF current in
antennas and transmission lines is another example of ac. An
ac waveform can be sinusoidal, square, or sawtooth-shaped.
Some ac waveforms are irregular or complicated. Certain
types of electronic oscillators and low-end UPSs produce
Square or sawtooth waves, when operating from battery.
AC Access Class (C0 to C15).
AC Application Context.
ACC Automatic Congestion Control. A method by which congested
switches automatically communicate their congestion level
to other switches.
Access Burst The MS uses the Access Burst to access the BTS. It carries
RACH uplink from the MS to the BTS to start a call.
Continued
6-2 68P02901W01-S
Jul 2008
System Information: GSM Overview A Interface - AUTO
ACCH Associated Control CHannel. Control information associated

with TCH or DCCH.
ACK, Ack Acknowledgment.
ACM Accumulated Call meter. The ACM is a function contained

within the SIM. It accumulates the total units (in the home
currency) for both the current call and all preceding calls.
For security reasons, the SIM only allows the value of the
ACM to be incremented, not decremented. Resetting of the
ACM is only possible after entering PIN2.
ACM Address Complete Message.
ACPIM AC Power Interface Module. Used in M-Cell6 indoor ac BTS
equipment.
AC PSM AC Power Supply Module. Used in M-Cell6 BTS equipment.
ACSE Association Control Service Element. The ACSE is one of the
three Application Service Elements (ASE) which reside in the
application layer of the OSI protocol and act as an interface
to the lower layer protocols. Applications use ACSE to create
a title for identification. See also ASI and ROSE.
ACU Antenna Combining Unit.
A/D Analog to Digital (converter). See ADC.
ADC ADministration Center.
ADC Analog to Digital Converter. A device that converts a
signal that is a function of a continuous variable into
a representative number sequence carrying equivalent
information.
ADCCP Advanced Data Communications Control Protocol. A
bit-oriented data-link-layer (DL) protocol used to provide
point-to-point and point-to-multipoint transmission of data
frames that contain error-control information. Note: ADCCP
closely resembles high-level data link control (HDLC).
ADM ADMinistration processor.
ADMIN ADMINistration.
ADN Abbreviated Dialling Number. Abbreviated dialling is a
telephone service feature that (a) permits the user to
dial fewer digits to access a network than are required
under the nominal numbering plan, and (b) is limited to a
subscriber-selected set of frequently dialled numbers.
ADPCM Adaptive Differential Pulse Code Modulation. Differential
Pulse-Code Modulation (DPCM) in which the prediction
algorithm is adjusted in accordance with specific
characteristics of the input signal.
AE Application Entity. The system-independent application
activities that are made available as application services to
the application agent.
AEC Acoustic Echo Control. In a system, the reduction of the
power level of an echo or the elimination of an echo.
Continued
68P02901W01-S 6-3
Jul 2008
A Interface - AUTO Chapter 6: Glossary of Technical Terms
AEF Additional Elementary Functions.

AET Active Events Table. Alarms and events are sent to the
Events Log in the GUI. Different operators have different
subscription lists. All alarms and events are sent to the AET
before they are re-routed to different subscription lists.
AFC Automatic Frequency Control. A device or circuit that
maintains the frequency of an oscillator within the specified
limits with respect to a reference frequency.
AFN Absolute Frame Number.
AGC Automatic Gain Control. A process or means by which gain
is automatically adjusted in a specified manner as a function
of a specified parameter, such as received signal level.
AGCH Access Grant CHannel. A GSM common control channel
used to assign MS to a SDCCH or a TCH.
Ai Action indicator.
AI Artificial Intelligence. A branch of computer science whose
goal is to develop electronic devices that can operate with
some of the characteristics of human intelligence. Among
these properties are logical deduction and inference,
creativity, the ability to make decisions based on past
experience or insufficient or conflicting information, and the
ability to understand natural language.
AIB Alarm Interface Board.
AIO A class of processor.
Air interface The radio link between the BTS and the MS.
AL See Application Layer.
AM Amplitude Modulation. Modulation in which the amplitude
of a carrier wave is varied in accordance with some
characteristic of the modulating signal.
AMA Automatic Message Accounting (processor). A service
feature that automatically records data regarding
user-dialled calls.
AMR Adaptive Multi-Rate. The capability of operating at gross
bit-rates of 11.4 kbps (half-rate) and 22.8 kbps (full-rate)
over the air interface.
AM/MP Cell broadcast mobile terminated message. A message
broadcast to all MSs in a cell.
ANSI American National Standards Institute. ANSI is the primary
organization for fostering the development of technology
standards in the United States. ANSI works with industry
groups and is the U.S. member of ISO and the IEC. Long
established computer standards from ANSI include ASCII
and SCSI.
Antenna A transmitter/receiver which converts electrical currents
into RF and vice versa. In GSM systems, transmits and
receives RF signals between the BTS and MS.
Continued
6-4 68P02901W01-S
Jul 2008
System Information: GSM Overview A Interface - AUTO
AoC Advice of Charge.

AoCC Advice of Charge Charging supplementary service.
AoCI Advice of Charge Information supplementary service.
AOC Automatic Output Control.
AP Application Process.
Application Layer See OSI RM. The Application Layer is the highest of seven
hierarchical layers. It interfaces directly to, and performs
common application services for, the application processes.
It also issues requests to the Presentation Layer. The
common application services provide semantic conversion
between associated application processes.
ARFCN Absolute Radio Frequency Channel Number. The GSM
available frequency is divided in two bands. Each band is
divided into 200 kHz slots called ARFCN. Each ARFCN is
shared between eight mobiles, each using it in turn. Each
mobile uses the ARFCN for one TS (Timeslot) and then waits
for its turn to come around again. A mobile has use of the
ARFCN once per the TDMA frame. The combination of a TS
number and ARFCN is called a physical channel.
ARQ Automatic Repeat-reQuest. Error control for data
transmission in which the receiver detects transmission
errors in a message and automatically requests a
retransmission from the transmitter.
ARP Address Resolution Protocol. A Transmission Control
Protocol/Internet Protocol (TCP/IP) protocol that dynamically
binds a Network Layer (NL) IP address to a Data Link Layer
(DL) physical hardware address, for example, Ethernet
address.
ASCE Association Control Service Element. An ASE which
provides an AP with the means to establish and control an
association with an AP in a remote NE. Maps directly onto
the Presentation layer (OMC).
ASCII American Standard Code for Information Interchange. ASCII
is a standard developed by ANSI to define how computers
write and read characters. It is the most common format for
text files in computers and on the Internet. In an ASCII file,
alphabetic, numeric, and special characters are represented
with a 7-binary digit binary number. 128 possible characters
are defined. UNIX and DOS-based operating systems (except
for Windows NT) use ASCII for text files. Windows NT uses
a newer code, Unicode. IBM's System 390 servers use a
proprietary 8-bit code called extended binary-coded decimal
interchange code. Conversion programs allow different
operating systems to change a file from one code to another.
ASE Application Service Element (OMC). A coherent set
of integrated functions to help accomplish application
communication, for example, within an application entity
(AE).
ASE Application Specific Entity (TCAP).
Continued
68P02901W01-S 6-5
Jul 2008
B Interface - Byte Chapter 6: Glossary of Technical Terms
ASN.1 Abstract Syntax Notation One. A formal notation used

for describing data transmitted by telecommunications
protocols, regardless of language implementation and
physical representation of these data, whatever the
application, whether complex or simple.
ASP Alarm and Status Panel.
ASR Answer Seizure Ratio. The percentage of calls that are
completed successfully.
ATB All Trunks Busy. An equipment condition in which all trunks
(paths) in a given trunk group are busy.
Ater The interface between XCDR and BSC.
ATI Antenna Transceiver Interface.
ATM Asynchronous Transfer Mode. A high-speed multiplexing
and switching method utilizing fixed-length cells of 53 octets
to support multiple types of traffic.
ATT (flag) ATTach.
ATTS Automatic Trunk Testing Subsystem. Ensures the quality of
telephone lines with a series of tests. An operator command
or a command file can initiate the ATTS can be initiated,
which can be activated at a predetermined time.
AU Access Unit.
AUC Authentication Center. A GSM network entity which provides
the functionality for verifying the identity of the MS when
requested 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
a cell for BCCH transmission.
BAIC Barring of All Incoming Calls supplementary service.
BAOC Barring of All Outgoing Calls supplementary service.
Baud The unit in which the information carrying capacity or
signaling rate of a communication channel is measured. One
baud is one symbol (state transition or level-transition) per
second. This coincides with bits per second only for two-level
modulation with no framing or stop bits.
BBBX Battery Backup Board.
Continued
6-6 68P02901W01-S
Jul 2008
System Information: GSM Overview B Interface - Byte
BBH Base Band Hopping. Method of frequency hopping in

which each transceiver at the base station is tuned to a
different frequency, and the signal is switched to a different
transceiver for each burst.
BCC Base station Color Code. The BCC and the NCC are part of
the BSIC. The BCC comprises three bits in the range 000 to
111. See also NCC and BSIC.
BCCH Broadcast Control CHannel. A GSM control channel used
to broadcast general information about a BTS site on a per
cell or sector basis.
BCD Binary Coded Decimal. The representation of a decimal digit
by a unique arrangement of no fewer than four binary digits.
BCF Base station Control Function. The GSM term for the digital
control circuitry which controls the BTS. In Motorola cell
sites, this is a normally a BCU which includes DRI modules
and is located in the BTS cabinet.
B channel Bearer channel. Used in ISDN services to carry 64 kbps of
data, when used at full capacity.
BCIE Bearer Capability Information Element. Specific GSM
parameters in the Setup message are mapped into a BCIE
for signaling to the network and within the PLMN. The BCIE
is used to request a bearer service (BS) from the network.
BCU Base station Control Unit. A functional entity of the BSS
which provides the base control function at a BTS site. The
term no longer applies to a type of shelf (see BSC and BSU).
BCUP Base Controller Unit Power.
BEP Bit Error Probability.
BER Bit Error Rate. The number of erroneous bits divided by the
total number of bits transmitted, received, or processed over
some stipulated period. The BER is usually expressed as a
coefficient and a power of 10; for example, 25 erroneous
bits out of 100,000 bits transmitted would be 25 out of 105
or 25 x 10-5.
BES Business Exchange Services.
BFI Bad Frame Indication. An indication of unsuccessfully
decoded speech frames. See FER.
BH Busy Hour. In a communications system, the sliding
60-minute period during which occurs the maximum total
traffic load in a given 24-hour period.
BHCA Busy Hour Call Attempt. A statistic based on call attempts
that a switch processes during a BH. See also BH.
BI Barring of all Incoming call supplementary service.
BIB Balanced-line Interconnect Board. Provides interface to 12
balanced (6-pair) 120 ohm (37-pin D-type connector) lines
for 2 Mbps circuits. See also T43.
Continued
68P02901W01-S 6-7
Jul 2008
B Interface - Byte Chapter 6: Glossary of Technical Terms
BIC-Roam Barring of all Incoming Calls when Roaming outside the

Home PLMN Country supplementary service.
bidirectional neighbor See Reciprocal neighbor.
BIM Balanced-line Interconnect Module.
BIN From BINary. An area in a data array used to store
information. Also, a name for a directory that contain files
stored in binary format.
BL BootLoad. Also known as download. For example, databases
and software can be downloaded to the NEs from the BSS.
BLER Block Error Rate.
BLLNG BiLLiNG.
bit Binary digit. A character used to represent one of the two
states or digits (0 or 1) in the numeration system with a radix
of two. Also, a unit of storage capacity.
bit/s Bits per second (bps). A measure of data transmission speed.
The number of binary characters (1s or 0s) transmitted in
one second. For example, an eight-bit parallel transmission
link which transfers one character (eight bits) per second
is operating at 8 bps.
block A group of bits (binary digits) transmitted as a unit, over
which a parity check procedure is applied for error control
purposes.
Bm Full rate traffic channel. See also Full Rate.
BN Bit Number. Number which identifies the position of a
particular bit period within a timeslot.
BPF Bandpass Filter. A filter that ideally passes all frequencies
between two non-zero finite limits and bars all frequencies
not within the limits.
BPSM BCU Power Supply Module.
BRI Basic Rate Interface. An ISDN multipurpose user interface
allowing simultaneous voice and data services provided over
two clear 64 kbps channels (B channels) and one clear 16
kbps channel (D channel). The interface is also referred to
as 2B + D.
BS Base Station. See BSS.
BS Basic Service (group).
BS Bearer Service. A type of telecommunication service that
provides the capability for the transmission of signals
between user-network interfaces. The PLMN connection
type used to support a bearer service is identical to that used
to support other types of telecommunication service.
BSC Base Station Controller. A network component in the GSM
PLMN which has the digital control function of controlling
all BTSs. The BSC can be located within a single BTS cabinet
(forming a BSS) but is more often located remotely and
controls several BTSs (Refer BCF, BCU, and BSU).
Continued
6-8 68P02901W01-S
Jul 2008
System Information: GSM Overview B Interface - Byte
BSG Basic Service Group.

BSIC Base Transceiver Station Identity Code. Each cell has a
BSIC. It is a local color code that allows a mobile station to
distinguish between different neighboring base stations. The
BSIC is an octet, consisting of three bits for the Network
Color Code (NCC) and three bits for the Base station Color
Code (BCC). The remaining two bits are unused. See also
NCC and BCC.
BSIC-NCELL BSIC of an adjacent cell.
BSP Base Site control Processor (at BSC).
BSN Backward Sequence Number. A field in a signal unit (SU)
that contains the forward sequence number (FSN) of a
correctly received signal unit being acknowledged in the
signal unit that is being returned to the sender. See also
FSN and SU.
BSS Base Station System. The system of base station equipment
(Transceivers, controllers, and so on) which is viewed by the
MSC through a single interface as defined by the GSM 08
series of recommendations, as being the entity responsible
for communicating with MSs in a certain area. The radio
equipment of a BSS may cover one or more cells. A BSS
can consist of one or more base stations. If an internal
interface is implemented according to the GSM 08.5x series
of recommendations, then the BSS consists of one BSC and
several BTSs.
BSSAP BSS Application Part (part of SS7). Protocol for LAPD or
LAPB signaling links on the A-interface. Comprises DTAP
and BSSMAP messages. Supports message communication
between the MSC and BSS.
BSSC Base Station System Control cabinet. The cabinet which
houses one or two BSU shelves at a BSC or one or two RXU
shelves at a remote transcoder (RXCDR).
BSSMAP Base Station System Management Application Part (part of
SS7). Call processing protocol for A-interface messages
exchanged between the MSC and BSS. The BSS interprets
these messages.
BSSOMAP BSS Operation and Maintenance Application Part (part of
SS7).
BSU Base Station Unit shelf. The shelf which houses the digital
control modules for the BTS (part of BTS cabinet) or BSC
(part of BSSC cabinet).
BT British Telecom.
BT Bus Terminator. To avoid signal reflections on the bus, each
bus segment has to be terminated at its physical beginning
and at its end with the characteristic impedance.
BTC Bus Terminator Card.
BTF Base Transceiver Function.
Continued
68P02901W01-S 6-9
Jul 2008
C - CW Chapter 6: Glossary of Technical Terms
BTP Base Transceiver Processor (at BTS). One of the six basic
task groups within the GPROC.
BTS Base Transceiver Station. BSC controls the network
component in the GSM PLMN which serves one cell. The
BTS contains one or more Transceivers (TRXs).
Burst A period of modulated carrier less than one timeslot. The
physical content of a timeslot.
Byte A sequence of adjacent binary digits operated upon as a unit.
Generally consists of eight bits, usually presented in parallel.
A byte is usually the smallest addressable unit of information
in a data store or memory.
C - CW
C Conditional.
C Interface Interface between MSC and HLR/AUC.
C7 See SS7.
CA Cell Allocation. The radio frequency channels allocated to
a particular cell.
CA Central Authority. Software process that controls the BSS.
CAB Cabinet.
CADM Country ADMinistration. The Motorola procedure used
within DataGen to create new country and network files in
the DataGen database.
CAI Charge Advice Information.
CAT Cell Analysis Tool. The CAT is part of the Motorola Cell
optimization product. It is intended for engineering staff
and OMC administrators. CAT provides information about
GSM network cell performance.
CB Cell Balancer. The CB process balances the cells configured
for GPRS across PRPs. If there is a PRP outage, this process
sends message(s). The message indicates that GPRS service
is unavailable to the appropriate CRM(s) for the cells that
could not be moved to an INS (IN Service) PRP.
CB Cell Broadcast. See CBSMS.
CB Circuit Breaker.
CBA Cell Broadcast Agent.
CBC Cell Broadcast Center. The call processing center for CBSMS
messages.
CBCH Cell Broadcast CHannel. The channel which is used to
broadcast messages to all MSs in a specific cell.
CBF Combining Bandpass Filter.
Continued
6-10 68P02901W01-S
Jul 2008
System Information: GSM Overview C - CW
CBL Cell Broadcast Link. A bidirectional data link which allows

communications between the BSS and the CBC.
CBM Circuit Breaker Module.
CDMA Code-Division Multiple Access. CDMA is a digital cellular
technology that uses spread-spectrum techniques. Unlike
competing systems, such as GSM, that use TDM, CDMA
does not assign a specific frequency to each user. Instead,
every channel uses the full available spectrum. Individual
conversations are encoded with a pseudo-random digital
sequence.
CBMI Cell Broadcast Message Identifier.
CBS Cell Broadcast Service. See CBSMS.
CBSMS Cell Broadcast Short Message Service. CBSMS allows
a number of unacknowledged general messages to be
broadcast to all MSs within a particular region. The content
can include information such as local traffic conditions, the
weather, the phone number of the local taxi company, and so
on. The messages are sent from a CBC through a BSC to a
BTS and from there on a special cell broadcast channel to
the MSs. The CBC is considered as a node outside the PLMN
and can be connected to several BSCs. However, a BSC is
only connected to one CBC.
CBUS Clock Bus.
CC Connection Confirm. Part of SCCP network connectivity.
CC Country Code. A one to three digit number which specifically
identifies a country of the world that an international call
is being routed to (for example, 1 = North America, 44 =
United Kingdom).
CC The MSC performs the Call Control. CC functions, such as
number translations and routing, matrix path control, and
allocation of outgoing trunks.
CCB Cavity Combining Block, a three way RF combiner. There
are two types of CCB, CCB (Output) and CCB (Extension).
These, with up to two CCB Control cards, can comprise the
TATI. The second card is used for redundancy.
CCBS Completion of Calls to Busy Subscriber supplementary
service.
CCCH Common Control CHannels. A class of GSM control channels
used to control paging and grant access. Includes AGCH,
PCH, and RACH.
CCCH_GROUP Group of MSs in idle mode.
CCD Common Channel Distributor.
CCDSP Channel Coding Digital Signal Processor.
CCF Conditional Call Forwarding. See CFC.
CCH Control CHannel. Control channels are channels which carry
system management messages.
Continued
68P02901W01-S 6-11
Jul 2008
CCH Council for Communications Harmonization (referred to in

GSM Recommendations).
CCITT Comit Consultatif International Tlgraphique et
Tlphonique. This term has been superseded. See ITU-TSS.
CCM Current Call Meter.
CCP Capability/Configuration Parameter.
CCPE Control Channel Protocol Entity.
CCS Hundred call-seconds. A single call lasting 100 secs is one
CCS. Also, a measure of traffic load obtained by multiplying
the number of calls per hour by the average holding time
per call expressed in seconds, and dividing by 100. Often
used in practice to mean 100 call seconds per hour with per
hour implied; as such, it is a measure of traffic density. See
also erlang.
CCU Channel Codec Unit. The CCU performs the following
functions: Channel coding functions, including FEC and
interleaving, Radio channel measurement functions,
including received quality level, received signal level, and
information related to timing advance measurements.
Cct Circuit.
CDB Control Driver Board.
CDE Common Desktop Environment. Part of the SUN software
(crontab - cron job file).
CDR Call Detail Record. A record of voice or data SVCs, including
calling and called numbers, local and remote node names,
data and time-stamp, elapsed time, and call failure class
fields. This is the information needed to bill the customer for
calls and facility usage data for calls.
CD-ROM Compact Disk-Read Only Memory.
CDUR Chargeable DURation.
CEB Control Equalizer Board (BTS).
CED Called station identifier.
CEIR Central Equipment Identity Register.
Cell By GSM definition, a cell is an RF coverage area.
At an omni-site, cell is synonymous with site; at a
sectored site, cell is synonymous with sector. This
differs from analog systems where cell is taken
to mean the same thing as site. (See below).
6-12 68P02901W01-S
Jul 2008
1 C e ll =
1 S e c to r
O m n i S ite 6 -S e c to r S ite
1 -C e ll S ite or
(1 B T S ) 6 -C e ll S ite
(6 B T S s )
CEND End of charge point. The time at which the calling, or called
party stops charging by the termination of the call or by an
equivalent procedure invoked by the network or by failure
of the radio path.
CEPT Confrence des administrations Europennes des Postes et
Telecommunications.
CERM Circuit Error Rate Monitor. Identifies when discontinuity is
detected in a circuit. An alarm is generated and sent to the
OMC-R when the error count exceeds an operator specified
threshold. The alarm identifies the RCI or CIC and the path
where the error is detected.
CF Conversion Facility.
CF Call Forwarding. A feature whereby, after initiation of
the feature by an authorised subscriber, calls dialled to
the mobile telephone of an authorised subscriber will
automatically be routed to the desired number. See also
CFC and CFU.
CF Control Function. CF performs the SGSN mobility
management functions and OA and M functions for the GSN
module.
CFB Call Forwarding on mobile subscriber Busy supplementary
service. Service automatically redirects incoming calls for
phone busy situations.
CFC Call Forwarding Conditional supplementary service. Service
automatically redirects incoming calls for busy, no reply,
or not reachable situations. See also CFB, CFNRc, and
CFNRy.
CFM Configuration Fault Management RSS process.
CFNRc Call Forwarding on mobile subscriber Not Reachable
supplementary service. Service automatically redirects
incoming calls for not reachable situations.
CFNRy Call Forwarding on No Reply supplementary service. Service
automatically redirects incoming calls for no reply situations.
CFU Call Forwarding Unconditional supplementary service.
Service automatically redirects all incoming calls.
CG Charging Gateway.
Continued
68P02901W01-S 6-13
Jul 2008
CGF Charging Gateway Function.

Channel A means of one-way transmission. A defined sequence of
periods (for example, timeslots) in a TDMA system; a defined
frequency band in a FDMA system; a defined sequence of
periods and frequency bands in a frequency hopped system.
CIM Coaxial Interconnect Module.
Channel Mode See Full Rate and Half Rate. These are the channel modes
that are currently used.
CHP CHarging Point.
CHV Card Holder Verification information.
CKSN Ciphering Key Sequence Number. The CKSN is a number
which is associated with the ciphering key, Kc. It is used
to ensure authentication consistency between the MS and
the VLR.
CI Cell Identity. A block of code which identifies a cell within a
location area.
CI CUG Index.
C/I Carrier to Interference ratio.
CIC Circuit Identity Code. The unique identifier of the terrestrial
portion of a circuit path. A CIC is either a 64 kbps or 16
kbps connection depending on whether a site has local or
remote transcoding. A CIC with local transcoding occupies a
complete E1 timeslot. A 16 kbps CIC, at a site with remote
transcoding, occupies a sub-channel of an E1 timeslot.
CIR, C/I Carrier to Interference Ratio. Indicates the received signal
power level relative to the interference power level.
Ciphertext Unintelligible data produced through the use of
encipherment.
CKSN Ciphering Key Sequence Number.
CLI Calling Line Identity. The identity of the caller. See also
CLIP and CLIR.
CLIP Calling Line Identification Presentation supplementary
service. Allows the called party to identify the caller. See
also CLIR.
CLIR Calling Line Identification Restriction supplementary
service. Allows the caller to withhold their identity from the
called party. See also CLIP.
CLK Clock.
CLKX Clock Extender half size board. The fiber optic link that
distributes GCLK to boards in system (part of the BSS, and
so on).
Continued
6-14 68P02901W01-S
Jul 2008
CLM ConnectionLess Manager. co-ordinates global control over

the BSS by handling of all connectionless messages (that is,
messages that are not directly concerned with a connected
call). This includes such messages as global resets, load
limiting, and circuit blocking.
CLR CLeaR.
CM Configuration Management. Configuration management
allows the operator to perform network configuration tasks,
and to maintain all details of the network configuration at
the OMC.
CM Connection Management. See CLM.
CM Connectionless Manager. See CLM.
CMD CoMmanD.
CMM Channel Mode Modify. Message sent to the MS to request
a channel mode change. When it has received the CMM
message, the MS changes the mode to the indicated
channel. The MS then replies with a Channel Mode Modify
Acknowledge message indicating the new channel mode.
CMIP Common Management Information Protocol. Protocol used
for communication over the OML.
CMISE Common Management Information Service Element. An ASE
which provides a means to transfer management information
through CMIP messages with another NE over an association
established by ASCE using ROSE (OMC).
CMR Cellular Manual Revision. Documentation updates.
CNG CalliNg tone.
Codec Coder/Decoder. A speech coding unit that converts speech
into a digital format for radio broadcast, and vice versa.
CODEX Manufacturer's name for a type of multiplexer and packet
switch commonly installed at the Motorola OMC-R.
Coincident Cell A cell whose cell boundary follows the boundary of a
co-located neighbor cell. The coincident cell has a different
frequency type, but the same BSIC, as that of the neighbor
cell.
COLI COnnected Line Identity. Identity of the connected line. See
also COLP and COLR.
Collocated Placed together; two or more items together in the same
place.
Color Code An 8-bit code assigned to a BTS to distinguish interfering
signals from another cell.
COLP COnnected Line Identification Presentation supplementary
service. Allows the calling party to identify the line identity
of the connected party. See also COLR.
COLR COnnected Line Identification Restriction supplementary
service. Allows the connected party to withhold its line
identity from the calling party. See also COLP.
Continued
68P02901W01-S 6-15
Jul 2008
COM Code Object Manager (software).

COM COMplete.
COMB Combiner. The purpose of a combiner in the BSS is to
combine transmitter outputs from the RCUs onto an antenna.
COMM, Comms COMMunications.
CommHub Communications Hub. Provides Ethernet switching and IP
routing for the GSN complex local networking and GSN
complex E1 interfaces to the public data network.
CommsLink Communications Link. See also 2 Mbps link.
Compact PCI See cPCI.
CONF CONFerence circuit. Circuit used for multi-party conference
calls.
CONFIG CONFIGuration Control Program.
Congestion Situation occurring when an element cannot receive all the
service it is requesting.
CONNACK CONNect ACKnowledgment. Part of the synchronization
process. After a connection has been established, the
CONNACK message indicates that traffic channels are
available.
CP Call Processing. The CP process in the BTS controls the MS
to BSS to MS signaling link, MS originated and terminated
calls and inter-BSS and inter-BTS handovers.
cPCI Compact Peripheral Component Interconnect. A set of
standards that define a common card cage, power supplies,
and processor boards.
CPGM CCCH Paging Manager. The CPGM processes the paging
messages sent from the SGSN to the BSC or BTS.
CPS Code and Puncturing Scheme.
CPU Central Processing Unit. The portion of a computer that
controls the interpretation and execution of instructions.
Also, the portion of a digital communications switch that
executes programmed instructions, performs arithmetic
and logical operations on signals, and controls input/output
functions.
C/R Command/Response field bit.
CR Carriage Return (RETURN).
CR Connection Request (Part of SCCP network connectivity). A
SCCP Connection Request message is sent from the BSS to
the MSC to establish a connection. See also CREF.
CRC Cyclic Redundancy Check (3 bit). An error-detection scheme
that (a) uses parity bits generated by polynomial encoding
of digital signals, (b) appends those parity bits to the digital
signal, and (c) uses decoding algorithms that detect errors in
the received digital signal.
Continued
6-16 68P02901W01-S
Jul 2008
CRE Call RE-establishment procedure. Procedure for

re-establishing a call in the event of a radio link failure.
CREF Connection REFused (Part of SCCP network connectivity).
In a number of operating circumstances, a CREF message is
sent from the MSC to the BSS in response to a Connection
Request (CR).
CRM Cell Resource Manager. The CRM allocates and activates
timeslots and subchannels on the available carriers.
CRM Cell Resource Machine.
CRM-LS/HS Cellular Radio Modem-Low Speed/High Speed. Low speed
modem used to interwork 300 to 2400 bps data services
under V.22bis, V.23, or V.21 standards. High speed modem
used to interwork 1200 to 9600 bps data services under
V.22bis, V.32, or V.29/V.27ter/V.21 standards.
CRO Motorola Controlled Roll Out Group. A CRO consists of a
customer site implementation of a new product, software
release, or combination of products/releases.
CRT Cathode Ray Tube (video display terminal).
CS Circuit Switched.
CS-1 GPRS Coding Scheme-1 (9.05 kbps per TCH).
CSFP Code Storage Facility Processor (at BSC and BTS). A GPROC
device which facilitates the propagating of new software
instances with reduced system down time. See also IP.
CSP Central Statistics Process. The statistics process in the BSC.
CSPDN Circuit Switched Public Data Network. A publically available
communications network using circuit switched digital data
circuits.
CT Call Transfer supplementary service.
CT Channel Tester.
CT Channel Type.
CTP Call Trace Product (Tool). The CTP is designed to help
operators of GSM900 and DCS1800 communication
networks tune and optimize their systems. CTP allows Call
Trace data to be analyzed and decoded.
CTP Control Terminal Port.
CTR Common Technical Regulation.
CTS Clear to Send. A handshake signal used with communication
links, especially RS232 or CCITT Rec. V.24, to indicate (to a
transmitter from a receiver) that transmission can proceed.
Generated in response to a request to send signal. See also
RTS.
Continued
68P02901W01-S 6-17
Jul 2008
D Interface - DYNET Chapter 6: Glossary of Technical Terms
CTU Compact Transceiver Unit (M-Cellhorizon radio).

CUG Closed User Group supplementary service. A CUG is used
to control who can receive and/or place calls, by creating a
unique group. When a CUG is configured for an interface,
only those subscribers that are members of the same CUG
can receive/place calls.
Cumulative value The total value for an entire statistical interval.
CW Call Waiting supplementary service. A subscriber feature
which allows an individual mobile telephone user currently
engaged in a call to be alerted that another caller is trying to
reach him. The user has a predetermined period of time in
which to terminate the existing conversation and respond to
the second call.
D Interface - DYNET
D Interface Interface between VLR and HLR.

D/A Digital to Analog (converter). See DAC.
DAB Distribution Alarm Board (in BTS6 cabinet).
DAC Digital to Analog Converter. A device that converts an input
number sequence into a function of a continuous variable.
DACS Digital Access Cross-connect System. A data concentrator
and organizer for Tl/El based systems.
DAK Downlink Acknowledgment.
DAN Digital ANnouncer (for recorded announcements on MSC).
DAS Data Acquisition System.
DAT Digital Audio Tape. Audio-recording and playback
medium/format that maintains a signal quality equal to that
of the CD-ROM medium or format.
DataGen Sysgen Builder System. A Motorola offline BSS binary object
configuration tool.
Data Link Layer See OSI RM. This layer responds to service requests from
the Network Layer and issues service requests to the
Physical Layer. It provides the functional and procedural
means to transfer data between network entities and to
detect and possibly correct errors that can occur in the
Physical Layer.
dB Decibel. A unit stating the logarithmic ratio between two
numeric quantities. See also dBm.
DB DataBase.
DB Dummy Burst (see Dummy burst).
DBA DataBase Administration or Database Administrator.
dBm A dB referenced to 1 milliwatt; 0 dBm equals one milliwatt.
Continued
6-18 68P02901W01-S
Jul 2008
System Information: GSM Overview D Interface - DYNET
DBMS DataBase Management System.

dc Direct Current. DC is the unidirectional flow or movement
of electric charge carriers, usually electrons. The intensity
of the current can vary with time, but the general direction
of movement stays the same at all times. As an adjective,
the term DC is used in reference to voltage whose polarity
never reverses.
DCB Diversity Control Board (part of DRCU).
DCCH Dedicated Control CHannel. A class of GSM control channels
used to set up calls and report measurements. Includes
SDCCH, FACCH, and SACCH.
DCD Data Carrier Detect signal. Hardware signal defined by the
RS-232-C specification that indicates that a device such as a
modem is online and ready for transmission.
DCE Data Circuit terminating Equipment. The DCE performs
functions such as signal conversion and coding, at the
network end of the line between the DTE and the line.
Also, The RS232 configuration designated for computers.
DCE equipment can be connected to DTE equipment with a
straight cable, but to other DCE equipment only with a null
modem cable.
DCF Data Communications Function.
DCF Duplexed Combining bandpass Filter. (Used in
Horizonmacro).
D channel Data channel. Used in ISDN to perform call-signaling and
connection setup functions. In some circumstances, the
channel can also be used to carry user data.
DCN Data Communications Network. A DCN connects Network
Elements with internal mediation functions or mediation
devices to the Operations Systems.
DC PSM DC Power Supply Module.
DCS1800 Digital Cellular System at 1800 MHz. A cellular phone
network using digital techniques similar to those used in
GSM900, but operating on frequencies of 1710 - 1785 MHz
(receive) and 1805 - 1880 MHz (transmit).
DDF Dual-stage Duplexed combining Filter. (Used in
Horizonmacro). The DDF is an integrated combiner, filter,
and duplexer.
DDS DataGen Data Store. Store area for DataGen input and
output files.
DDS Data Drive Storage.
DDS Direct Digital Synthesis. A technology for generating highly
accurate and frequency-agile (rapidly changeable frequency
over a wide range), low-distortion output waveforms.
DEQB Diversity Equalizer Board.
DET DETach.
Continued
68P02901W01-S 6-19
Jul 2008
DFE Decision Feedback Equalizer. A receiver component/function.

The DFE results in a very sharp Bit Error Rate (BER)
threshold by using error feedback.
DGT Data Gathering Tool. The DGT collects all the relevant data
relating to a specified problem and copies it to tape or file,
together with a problem description. The file or tape is then
sent to Motorola for analysis.
DHP Digital Host Processor. A hard GPROC based device located
at Horizonmicro2 BTS sites. It represents the MCU of a slave
Horizonmicro2 FRU. The MCU that the DHP represents is
responsible for providing DRI and carrier support.
DIA Drum Intercept Announcer.
DINO E1/HDSL Line termination module (part of Horizonmicro).
DINO T1 Line termination module (part of Horizonmicro).
DISC DISConnect.
Discon Discontinuous.
DIQ Diversity In phase and Quadrature phase.
DIR Device Interface Routine. Software routine used in the BSS.
DL Data Link (layer). See Data Link Layer.
DL See Downlink.
DLCI Data Link Connection Identifier. In frame-relay transmission
systems, 13-bit field that defines the destination address of a
packet. The address is local on a link-by-link basis.
DLD Data Link Discriminator.
DLNB Diversity Low Noise Block.
DLS DownLink Segmentator. The DLS segments LLC frames into
RLC data blocks to be transmitted over the air interface.
DLSP Data Link Service Process. Handles messages for an OMP
and a shelf GPROC.
DLSP Digital Link Signaling Processor.
Dm Control channel (ISDN terminology applied to mobile
service).
DMA Deferred Maintenance Alarm. An alarm report level; an
immediate or deferred response is required (Refer PMA).
DMA Direct Memory Access. Transfer of data from a peripheral
device, such as a hard disk drive, into memory without that
data passing through the microprocessor. DMA transfers
data into memory at high speeds with no processor overhead.
DMR Digital Mobile Radio.
DMX Distributed Electronic Mobile Exchange (Motorola's
networked EMX family).
DN Directory Number.
Continued
6-20 68P02901W01-S
Jul 2008
System Information: GSM Overview D Interface - DYNET
DNIC Data Network Identifier Code. In the CCITT International

X.121 format, the first four digits indicate the international
data number, the next three digits are the data country code,
and the final digit is the network code.
DNS Domain Name Service. A service that translates from logical
domain or equipment names to IP addresses.
Downlink Physical link from the BTS towards the MS (BTS transmits,
MS receives).
DP Dial/Dialled Pulse. A dc pulse produced by an end
instrument that interrupts a steady current at a sequence
and rate determined by the selected digit and the operating
characteristics of the instrument.
DPC Destination Point Code. A part of the label in a signaling
message that uniquely identifies, in a signaling network, the
(signaling) destination point of the message.
DPC Digital Processing and Control board.
DPCM Pulse-code modulation (PCM) in which an analog signal is
sampled and the difference between the actual value of each
sample and its predicted value, derived from the previous
sample or samples, is quantified and converted, by encoding,
to a digital signal.
NOTE
There are several variations of differential
pulse-code modulation.
DPNSS Digital Private Network Signaling System (BT standard for
PABX interface).
DPP Dual Path Preselector. BTS module.
DPR, DPRAM Dual Port Random Access Memory.
DPROC Data PROCessor.
DPSM Digital Power Supply Module.
DRAM Dynamic Random Access Memory. A type of semiconductor
memory in which the information is stored in capacitors on
an integrated circuit.
DRC Data Rate Converter board. Provides data and protocol
conversion between PLMN and destination network for eight
circuits. Part of IWF.
DRCU Diversity Radio Channel Unit. Contains transceiver, digital
control circuits, and power supply. Part of the BSS.
DRI Digital Radio Interface. Provides encoding/decoding and
encryption/decryption for radio channels. Part of BSS.
DRIM Digital Radio Interface extended Memory. A DRI with extra
memory.
DRIX DRI Extender half size board. Fiber optic link from DRI to
BCU. Part of the BSS.
Continued
68P02901W01-S 6-21
Jul 2008
DRX, DRx Discontinuous reception (mechanism). A means of saving

battery power (for example, in hand-portable units) by
periodically and automatically switching the MS receiver
on and off.
DS-1 Digital transmission System 1 (or Digital Signal level 1).
Term used to refer to the 1.44 Mbps (U.S.) or 2.108 Mbps
(Europe) digital signal carried on a T1 facility.
DS-2 German term for 2 Mbps line (PCM interface).
DSE Data Switching Exchange.
DSI Digital Speech Interpolation. A compression technique
that relies on the pauses between speech bursts to provide
additional compression. DSI enables users to gain an
additional 2:1 compression on the average on their line.
DSO 64 kbps timeslot on an E1.
DSP Digital Signal Processor. A specialized, programmable
computer processing unit that is able to perform high-speed
mathematical processing.
DSS1 Digital Subscriber Signaling No 1. N-ISDN user network
interface signaling.
DSSI Diversity Signal Strength Indication.
DTAP Direct Transfer Application Part (Part of SS7). Call
processing protocol for A-Interface messages exchanged
directly between the MSC and the mobile unit without
interpretation by the BSS.
DTE Data Terminal Equipment. An end instrument that
converts user information into signals for transmission
or reconverts the received signals into user information.
Also, the RS232 configuration designated for terminals. DTE
equipment can be connected to DCE with a straight cable,
but to other DTE equipment only with a null modem.
DTF Digital Trunk Frame. A frame or electronic rack of digital
trunk interface equipment.
DT1 DaTa form 1 (Part of SCCP network connectivity).
DTI Digital Trunk Interface.
DTM Dual Transfer Mode.
DTMF Dual Tone Multi-Frequency. Multifrequency signaling in
which specified combinations of two voice band frequencies,
one from a group of four low frequencies and the other from
a group of four higher frequencies, are used. The sounds a
push button tone telephone makes when it dials a number.
DTR Data Terminal Ready signal. Method of flow control (RS232
Interface). A modem interface control signal sent from the
DTE to the modem, usually to indicate to the modem that the
DTE is ready to transmit data.
DTRX Dual Transceiver Module. (Radio used in Horizonmicro
(M-Cellarena) and Horizonmacro (M-Cellarenamacro).
Continued
6-22 68P02901W01-S
Jul 2008
System Information: GSM Overview E - EXEC
DTX, DTx Discontinuous Transmission (mechanism). A means of

saving battery power (for example, in hand-portable units)
and reducing interference by automatically switching the
transmitter off when no speech or data are to be sent.
Dummy burst A period of carrier less than one timeslot whose modulation
is a defined sequence that carries no useful information.
A dummy burst fills a timeslot with an RF signal when no
information is to be delivered to a channel.
DYNET DYnamic NETwork. Used to specify BTSs sharing dynamic
resources.
E - EXEC
E See Erlang.
E1 Also known as CEPT1. The 2.048 Mbps rate used by
European CEPT carrier to transmit 30 64 kbps digital
channels for voice or data calls, plus a 64 kbps signaling
channel and a 64 kbps channel for framing and maintenance.
E Interface Interface between MSC and MSC.
EA External Alarm. Refer EAS. Typical external alarms are Door
open, High humidity, Low humidity, Fire, Intruder.
EAS External Alarm System. The EAS is responsible for the
monitoring of all customer-defined environmental alarms at a
site. The customer defines the alarm string and the severity
of the alarms based on the individual requirements of the site.
Indications are provided when the alarms are set or cleared.
Eb/No Energy per Bit/Noise floor, where Eb is the signal energy per
bit and No is the noise energy per hertz of noise bandwidth.
EBCG Elementary Basic Service Group.
EC Echo Canceler. Performs echo suppression for all voice
circuits. If cancelation does not take place, the PLMN
subscriber hears the voice signal as an echo, due to the total
round-trip delay introduced by the GSM system (typically
180 ms).
ECB Provides echo canceling for telephone trunks for 30 channels
(EC).
ECID The Motorola European Cellular Infrastructure Division.
ECM Error Correction Mode. A facsimile mode, in which the
sending machine attempts to send a partial page up to four
times.
Ec/No Ratio of energy per modulating bit to the noise spectral
density.
Continued
68P02901W01-S 6-23
Jul 2008
E - EXEC Chapter 6: Glossary of Technical Terms
ECT Event Counting Tool. The ECT provides information about the
number and type of events and alarms generated throughout
the network. It extracts data from the event log files for
specified dates, allowing the user to generate reports on
individual network elements, groups of elements, or the
whole network.
ECT Explicit Call Transfer supplementary service. ECT enables
a user to connect two other parties with which the user is
engaged in a telephone call and leave the connection himself.
EDGE Enhanced Data-rates for Global Evolution.
EEL Electric Echo Loss.
EEPROM Electrically Erasable Programmable Read Only Memory.
An EEPROM is a special type of PROM that can be erased
by exposing it to an electrical charge. Like other types of
PROM, EEPROM retains its contents even when the power
is turned off.
EGPRS Enhanced GPRS.
EGSM900 Extended GSM900. EGSM900 provides the BSS with a
further range of frequencies for MS and BSS transmit. EGSM
MSs can use the extended frequency band as well as the
primary band, while non-EGSM MSs cannot use the extended
frequency band. A GSM900 cell can contain both GSM900
and EGSM900 carrier hardware. EGSM operates on the
frequency range, 880 MHz to 915 MHz (receive) and 925
MHz to 960 MHz (transmit).
EI Events Interface. Part of the OMC-R GUI.
EIA Electronic Industries Alliance.
EIR Equipment Identity Register. The EIR contains a centralized
database for validating the IMEI. The register consists of
lists of IMEIs organized as follows: White List - IMEIs which
are known to have been assigned to valid MS equipment.
Black List - IMEIs which have been reported stolen or which
are to be denied service for some other reason. Grey List -
IMEIs which have problems (for example, faulty software).
These are not, however, sufficiently significant to warrant a
black listing.
EIRP Effective Isotropically Radiated Power. The arithmetic
product of the power supplied to an antenna and its gain.
EIRP Equipment Identity Register Procedure.
EL Echo Loss.
EM Event Management. An OMC-R application. It provides a
centralized facility for reporting network-wide generated
events and alarms, and for monitoring the status of the
Network.
Continued
6-24 68P02901W01-S
Jul 2008
System Information: GSM Overview E - EXEC
EMC Electro Magnetic Compatibility. The ability of systems,

equipment, and devices that utilize the electromagnetic
spectrum to operate in their intended operational
environments without suffering unacceptable degradation
or causing unintentional degradation because of
electromagnetic radiation or response.
EMF Electro Motive Force. The rate at which energy is drawn
from a source that produces a flow of electricity in a circuit;
expressed in volts.
EMI Electro Magnetic Interference. Any electromagnetic
disturbance that interrupts, obstructs, or otherwise degrades
or limits the effective performance of electronics/electrical
equipment.
eMLPP enhanced Multi-Level Precedence and Preemption service.
This service has two parts: precedence and preemption.
Precedence involves assigning a priority level to a call
in combination with fast call setup. Preemption involves
the seizing of resources, which are in use by a call of a
lower precedence, by a higher level precedence call in the
absence of idle resources. Preemption can also involve the
disconnection of an on-going call of lower precedence to
accept an incoming call of higher precedence.
EMMI Electrical Man Machine Interface.
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 system
to another (that is, all the digits for a given call are sent at
the same time as a group). Sending is the opposite of overlap
sending. A system using sending waits until it has collected
all the digits for a given call before it attempts to send digits
to the next system. All the digits are then sent as a group.
EOP Enhanced One-Phase.
EOT End of Tape.
EPCR EGPRS Packet Channel Request.
EPROM Erasable Programmable Read Only Memory. EPROM is a
type of memory that retains its contents until it is exposed
to ultraviolet light. The ultraviolet light clears its contents,
making it possible to re-program the memory.
EPSM Enhanced Power Supply Module. Used in +27 V positive
earth cabinets.
EQ50 Static model against which the performance of the equalizer
is tested to extremes. See also TU3, TU50, HT100 and
RA250.
EQB Equalizer Board. Control circuit for equalization for eight
time slots each with equalizing circuitry and a DSP.
EQCP Equalizer Control Processor.
EQDSP Equalizer Digitizer Signal Processor.
Continued
68P02901W01-S 6-25
Jul 2008
F Interface - Full Rate Chapter 6: Glossary of Technical Terms
Equalization The process by which attenuation and/or phase shift is

rendered constant over a band of frequencies, even though
the transmission medium or the equipment has losses that
vary with frequency.
Equalizer An electrical network in which attenuation (or gain) and/or
phase shift varies as a function of frequency. Used to provide
equalization.
Erlang International (dimensionless) unit of traffic intensity defined
as the ratio of time a facility is occupied to the time it is
available for occupancy. One erlang is equal to 36 CCS. In
the US, this is also known as a traffic unit (TU).
ERP Ear Reference Point. Facility for assessing handset and
headset acoustic responses.
ERP Effective Radiated Power. The power supplied to an antenna
multiplied by the antenna gain in a given direction.
ERR ERRor.
ESP Electro-static Point. Connection point on the equipment for
an anti-static wrist strap.
ESQL Embedded SQL (Structured Query Language). The RDBMS
programming interface language.
E-TACS Extended TACS (analog cellular system, extended).
Ethernet A standard protocol (IEEE 802.3) for a 10 Mbps baseband
local area network (LAN) bus using carrier-sense multiple
access with collision detection (CSMA/CD) as the access
method, implemented at the Physical Layer in the OSI RM,
establishing the physical characteristics of a CSMA/CD
network.
ETR ETSI Technical Report.
ETS European Telecommunication Standard.
ETSI European Telecommunications Standards Institute.
ETX End of Transmission.
EXEC Executive Process.
F Interface - Full Rate
F Interface Interface between MSC and EIR.

FA Fax Adaptor. Device which complements Group 3 facsimile
apparatus to be able to communicate over a GSM PLMN.
FA Full Allocation.
FA Functional Area.
FAC Final Assembly Code.
Continued
6-26 68P02901W01-S
Jul 2008
System Information: GSM Overview F Interface - Full Rate
FACCH Fast Associated Control Channel. A GSM dedicated control

channel which temporarily uses the TCH to perform high
speed transmissions, and carries control information after
a call is set up. See also SDCCH.
FACCH/F Fast Associated Control Channel/Full rate. See also Full
Rate.
FACCH/H Fast Associated Control Channel/Half rate. See also Half
Rate.
FB See Frequency correction burst.
FBM Flow control Buffer Management. FBM is a functional unit
residing on the PRP. It controls buffer capacity for each
cell and each mobile so that the incoming data from the
SGSN matches the air throughput.
FC-AL Fiber Channel Arbitrated Loop. A serial data transfer
architecture. FC-AL is designed for mass storage devices
and other peripheral devices that require very high
bandwidth. Using optical fiber to connect devices, FC-AL
supports full-duplex data transfer rates of 100 Mbps.
FCCH Frequency Correction CHannel. A GSM broadcast control
channel which carries information for frequency correction
of the MS.
FCP Fault Collection Process. Part of the fault management
process in the BTS.
FCS Frame Check Sequence. The extra characters added to a
frame for error detection and correction.
FDM Frequency Division Multiplex. A multiplexing technique
that uses different frequencies to combine multiple
streams of data for transmission over a communications
medium. FDM assigns a discrete carrier frequency to each
data stream and then combines many modulated carrier
frequencies for transmission.
FDMA Frequency Division Multiple Access. The use of
frequency division to provide multiple and simultaneous
transmissions to a single transponder.
FDN Fixed Dialling Number. The fixed dialling feature limits
dialling from the MS to a predetermined list maintained
on the SIM card. It can be used to limit calling to certain
areas, exchanges, or full phone numbers.
FDP Fault Diagnostic Procedure.
FEC Forward Error Correction. Correction of transmission
errors by transmitting additional information with the
original bit stream. If an error is detected, the additional
information is used to recreate the original information.
FEP Front End Processor. An OMC-R device. The FEP is a
driver that stores data in its own database about all of the
sites in the system. All bursts from the sites are directed
to the FEP. It can also interrogate the sites and collect its
data either manually or automatically at predefined times.
Continued
68P02901W01-S 6-27
Jul 2008
F Interface - Full Rate Chapter 6: Glossary of Technical Terms
FER Frame Erasure Ratio. The ratio of successfully decoded

good speech frames against unsuccessfully decoded bad
frames.
FFS, FS For Further Study.
FH See Frequency Hopping.
FHI Frequency Hopping Indicator.
FIB Forward Indicator Bit. Used in SS7 - Message Transfer
Part. The forward indicator bit and backward indicator bit
together with the forward sequence number and backward
sequence number are used in the basic error control
method to perform the signal unit sequence control and
acknowledgment functions.
FIFO Memory logic device in which the information placed in
the memory in a given order is retrieved in that order.
FIR Finite Impulse Response (filter type).
FK Foreign Key. A database column attribute; the foreign key
indicates an index into another table.
FM Fault Management (at OMC).
FM Frequency Modulation. Modulation in which the
instantaneous frequency of a sine wave carrier is caused
to depart from the center frequency by an amount
proportional to the instantaneous value of the modulating
signal.
FMIC Fault Management Initiated Clear. An alarm type. If a
FMIC alarm is received, the fault management software
for the network item clears the alarm when the problem is
solved. See also Intermittent and OIC.
FMON Feature Capacity Licensing and Audit.
FMUX Fiber optic MUltipleXer module.
FN Frame Number. Identifies the position of a particular

TDMA frame within a hyperframe.
FOA First Office Application. A full functional verification of
new product(s) on a commercial system using accepted
technology and approved test plans.
FOX Fiber Optic eXtender board.
FR See Full Rate.
FR Frame Relay. An interface protocol for statistically
multiplexed packet-switched data communications in
which (a) variable-sized packets (frames) are used that
completely enclose the user packets they transport, and
(b) transmission rates are usually between 56 kbps and
1.544 Mbps (the T-1 rate).
Continued
6-28 68P02901W01-S
Jul 2008
System Information: GSM Overview F Interface - Full Rate
Frame A set of consecutive Pulse Code Modulation (PCM) time

slots containing samples from all channels of a group,
where the position of each sample is identified by reference
to a frame alignment signal. Also, an information or signal
structure which allows a receiver to identify uniquely an
information channel.
Frame Alignment The state in which the frame of the receiving equipment is
synchronized with respect to that of the received signal to
accomplish accurate data extraction.
FRU Field Replaceable Unit. A board, module, and so on. which
can be easily replaced in the field with a few simple tools.
Frequency Correction Period of RF carrier less than one timeslot whose
modulation bit stream allows frequency correction to be
performed easily within the MS burst.
Frequency Hopping The repeated switching of frequencies during radio
transmission according to a specified algorithm. Frequency
hopping improves capacity and quality in a highly loaded
GSM network. Multipath fading immunity can be increased
by using different frequencies and interference coming
from neighbor cells transmitting the same or adjacent
frequencies can be reduced.
FS Frequency synchronization. All BSS frequencies and
timing signals are synchronized to a high stability
reference oscillator in the BSS. This oscillator can free run
or be synchronized to the recovered clock signal from a
selected E1 serial link. MSs lock to a reference contained
in a synchronization burst transmitted from the BTS site.
FSL Free Space Loss. The decrease in the strength of a radio
signal as it travels between a transmitter and receiver.
The FSL is a function of the frequency of the radio signal
and the distance the radio signal has travelled from the
point source.
FSN Forward Sequence Number. Refer FIB.
FTAM File Transfer Access and Management. An ASE which
provides a means to transfer information from file to file.
(OMC).
ftn forwarded-to number.
FTP Fault Translation Process (in BTS).
FTP File Transfer Protocol. A client-server protocol which
allows a user on one computer to transfer files to and from
another computer over a TCP/IP network. Also the client
program the user executes to transfer files.
Full Rate Refers to the current capacity of a data channel on the
GSM air interface, that is, eight simultaneous calls per
carrier. See also HR - Half Rate.
68P02901W01-S 6-29
Jul 2008
G Interface - GWY Chapter 6: Glossary of Technical Terms
G Interface - GWY
G Interface Interface between VLR and VLR.

Gateway MSC The MSC that provides an entry point into the GSM PLMN
from another network or service. A gateway MSC is also
an interrogating node for incoming PLMN calls.
Gb, Gbyte Gigabyte. 230 bytes = 1,073,741,824 bytes = 1024
megabytes.
GBIC Gigabit Interface Converter for connection to the Gigabit
Ethernet.
GBL Gb Link.
GBM Gb Manager.
GCLK Generic Clock board. System clock source, one per site
(part of BSS, BTS, BSC, IWF, RXCDR).
GCR Group Call Register. The register which holds information
about VBS calls.
GDP Generic DSP Processor board. Interchangeable with the
XCDR board.
GDP E1 GDP board configured for E1 link usage.
GDS GPRS Data Stream.
GGSN Gateway GPRS Support Node. The GGSN provides Internet
working with external packet-switched networks.
GHz Giga-Hertz (109).
GID Group ID. A unique number used by the system to identify
a user's primary group.
GIP GPRS Initialization Process.
GMB GSM Multiplexer Board (part of the BSC).
GMM GPRS Mobility Management.
GMR General Manual Revision.
GMSC Gateway Mobile-services Switching Center. See Gateway
MSC.
GMSK Gaussian Minimum Shift Keying. The modulation
technique used in GSM.
GND GrouND.
GOS Grade of Service. A traffic statistic defined as the
percentage of calls which have a Probability of Busy or
Queueing Delay. An alternative criterion is a maximum
time for a percentage of calls to wait in the busy queue
before they are assigned a voice channel.
GPA GSM PLMN Area.
GPC General Protocol Converter.
Continued
6-30 68P02901W01-S
Jul 2008
System Information: GSM Overview G Interface - GWY
GPROC Generic Processor board. GSM generic processor board: a

68030 with 4 Mb to 16 Mb RAM (part of BSS, BTS, BSC,
IWF, RXCDR).
GPROC2 Generic Processor board. GSM generic processor board:
a 68040 with 32 Mb RAM (part of BSS, BTS, BSC, IWF,
RXCDR).
GPROC3 Generic Processor board. GSM generic processor board:
a 68060 with 128 Mb RAM (part of BSS, BTS, BSC, IWF,
RXCDR).
GPRS General Packet Radio Service. A GSM data transmission
technique that does not set up a continuous channel from
a portable terminal for the transmission and reception of
data, but transmits and receives data in packets. It makes
efficient use of available radio spectrum, and users pay
only for the volume of data sent and received.
GPS Global Positioning by Satellite. A system for determining
position on the Earth's surface by comparing radio signals
from several satellites.
GR Gb Router.
GSA GSM Service Area. The area in which the MS can be
reached by a fixed subscriber, without the subscriber's
knowledge of the location of the MS. A GSA can include
the areas served by several GSM PLMNs.
GSA GSM System Area. The group of GSM PLMN areas
accessible by GSM MSs.
GSD GSM Systems Division.
GSL GPRS Signaling Link.
GSM Groupe Spcial Mobile (the committee).
GSM Global System for Mobile communications (the system).
GSM900 See PGSM.
GSM HR GSM Half Rate.
GSM MS GSM Mobile Station.
GSM PLMN GSM Public Land Mobile Network.
GSM RF GSM Radio Frequency.
GSN GPRS Support Node. The combined functions provided by
the SGSN and GGSN.
GSN Complex A GSN Complex consists of an ISS Cluster, GGSN, and
SGSNs connected to a single CommHub.
GSR GSM Software Release.
GT Global Title. A logical or virtual address used for routing
SS7 messages using SCCP capabilities. To complete
message routing, a GT must be translated to a SS7-point
code and subsystem number.
GTM Gb Transmit Manager.
Continued
68P02901W01-S 6-31
Jul 2008
H Interface - Hyperframe Chapter 6: Glossary of Technical Terms
GTE Generic Table Editor. The Motorola procedure which

allows users to display and edit MCDF input files.
GTS GBRS TBF Scheduler.
Guard period Period at the beginning and end of timeslot during which
MS transmission is attenuated.
GUI Graphical User Interface. A computer environment
or program that displays, or facilitates the display of,
on-screen options. These options are usually in the form of
icons (pictorial symbols) or menus (lists of alphanumeric
characters) with which users can enter commands.
GUI client A computer used to display a GUI from an OMC-R GUI
application which is being run on a GUI server.
GUI server A computer used to serve the OMC-R GUI application
process running locally (on its processor) to other
computers (GUI clients or other MMI processors).
GWM GateWay Manager.
GWY GateWaY (MSC/LR) interface to PSTN.
H Interface - Hyperframe
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 doubles the current
GSM air interface capacity to 16 simultaneous calls per
carrier (Refer also FR - Full Rate).
HANDO, Handover HANDOver. The action of switching a call in progress from
one radio channel to another radio channel. Handover
allows established calls to continue by switching them to
another radio resource, as when the MS moves from one
BTS area to another. Handovers can take place between
the following GSM entities: timeslot, RF carrier, cell, BTS,
BSS, and MSC.
HCU Hybrid Combining Unit. (Used in Horizonmacro). Part of
the DDF, the HDU allows the outputs of three radios to be
combined into a single antenna.
HDLC High-level Data Link Control. A link-level protocol used
to facilitate reliable point-to-point transmission of a data
packet. Note: A subset of HDLC, LAP-B, is the layer-two
protocol for CCITT Recommendation X.25.
HDSL High bit-rate Digital Subscriber Line. HDSL is a data
transmission mechanism which supports duplex high
speed digital communication (at E1 rates) on one or more
unshielded twisted pair lines.
Continued
6-32 68P02901W01-S
Jul 2008
System Information: GSM Overview H Interface - Hyperframe
HLC High Layer Compatibility. The HLC can carry information

defining the higher layer characteristics of a teleservice
active on the terminal.
HLR Home Location Register. The LR where the current
location and all subscriber parameters of the MS are
permanently stored.
HMS Heat Management System. The system that provides
environmental control of the components inside the ExCell,
TopCell, and M-Cell cabinets.
HO HandOver. See HANDO.
HPU Hand Portable Unit. A handset.
HOLD Call hold supplementary service. Call hold allows the
subscriber to place a call on hold in order to make another
call. When the second call is completed, the subscriber
can return to the first call.
HPLMN Home PLMN.
HR See Half Rate.
HS HandSet.
HSI/S High Speed Interface card.
HSM HLR Subscriber Management.
HSN Hopping Sequence Number. HSN is an index indicating
the specific hopping sequence (pattern) used in a given
cell. It ranges from 0 to 63.
HT100 Hilly Terrain with the MS travelling at 100 kph. Dynamic
model against which the performance of a GSM receiver
can be measured. See also TU3, TU50, RA250 and EQ50.
HU Home Units. The basic telecommunication unit as set by
the HPLMN. This value is expressed in the currency of the
home country.
HW Hardware.
Hybrid Combiner A combiner device which requires no software control
and is sufficiently broadband to be able to cover the GSM
transmitter frequency band. See also COMB.
Hybrid Transformer A circuit used in telephony to convert 2-wire operation
to 4-wire operation and vice versa. For example, every
landline telephone contains a hybrid to separate earpiece
and mouthpiece audio and couple both into a 2-wire circuit
that connects the phone to the exchange.
Hyperframe 2048 superframes. The longest recurrent time period of
the frame structure.
68P02901W01-S 6-33
Jul 2008
I - IWU Chapter 6: Glossary of Technical Terms
I - IWU
I Information frames. Part of RLP.

IA Incoming Access supplementary service. An arrangement
which allows a member of a CUG to receive calls from
outside the CUG.
IA5 International Alphanumeric 5-character set.
IADU Integrated Antenna Distribution Unit. The IADU is the
equivalent of the Receive Matrix used on BTSs that
pre-date the M-Cell range.
IAM Initial Address Message. A message sent in the forward
direction that contains (a) address information, (b) the
signaling information required to route and connect
a call to the called line, (c) service-class information,
(d) information relating to user and network facilities, and
(e) call-originator identity or call-receiver identity.
IAS Internal Alarm System. The IAS is responsible for
monitoring all cabinet alarms at a BSS.
IC Integrated Circuit. An electronic circuit that consists of
many individual circuit elements, such as transistors,
diodes, resistors, capacitors, inductors, and other active
and passive semiconductor devices, formed on a single
chip of semiconducting material and mounted on a single
piece of substrate material.
IC Interlock Code. A code which uniquely identifies a CUG
within a network.
IC(pref) Interlock Code of the preferential CUG.
ICB Incoming Calls Barred. An access restriction that prevents
a CUG member from receiving calls from other members
of that group.
ICC Integrated Circuit(s) Card.
ICM In-Call Modification. Function which allows the service
mode (speech, facsimile, data) to be changed during a call.
ICMP Internet Control Message Protocol. An extension to the
Internet Protocol (IP) that allows for the generation of
error messages, test packets, and informational messages
related to IP. The PING command, for example, uses ICMP
to test an Internet connection.
ID, Id IDentification/IDentity/IDentifier.
IDN Integrated Digital Network. A network that uses both
digital transmission and digital switching.
IDS Interface Design Specification.
IDS Informix Dynamic Server. The OMC-R relational database
management system.
Continued
6-34 68P02901W01-S
Jul 2008
System Information: GSM Overview I - IWU
IE Information Element. The part of a message that contains

configuration or signaling information.
IEC International Electrotechnical Commission. An
international standards and conformity assessment body
for electrical, electronic, and related technologies.
IEEE Institute of Electrical and Electronic Engineers. A
non-profit, technical professional association.
IEI Information Element Identifier. The identifier field of the
IE.
I-ETS Interim European Telecommunication Standard.
IF Intermediate Frequency. A frequency to which a carrier
frequency is shifted as an intermediate step in transmission
or reception.
IFAM Initial and Final Address Message.
IM InterModulation. The production, in a nonlinear element
of a system, of frequencies corresponding to the sum and
difference frequencies of the fundamentals and harmonics
thereof that are transmitted through the element.
IMACS Intelligent Monitor And Control System.
IMEI International Mobile station Equipment Identity. Electronic
serial number that uniquely identifies the MS as a piece or
assembly of equipment. The MS sends the IMEI along with
request for service. See also IMEISV.
IMEISV International Mobile station Equipment Identity and
Software Version number. The IMEISV is a 16 digit decimal
number composed of four elements:- a 6 digit Type Approval
Code; - a 2 digit Final Assembly Code; - a 6 digit Serial
Number; and - a 2 digit Software Version Number (SVN).
The first three elements comprise the IMEI. When the
network requests the IMEI from the MS, the SVN (if
present) is also sent towards the network. See also IMEI
and SVN.
IMM IMMediate assignment message. IMMs are sent from
the network to the MS to indicate that the MS must
immediately start monitoring a specified channel.
IMSI International Mobile Subscriber Identity. Published
mobile number (pre- ISDN) that uniquely identifies the
subscription. It can serve as a key to derive subscriber
information such as directory number(s) from the HLR.
See also MSISDN.
IN Intelligent Network. A network that allows functionality
to be distributed flexibly at a variety of nodes on and off
the network and allows the architecture to be modified to
control the services.
IN Interrogating Node. A switching node that interrogates a
HLR, to route a call for the MS to the visited MSC.
Continued
68P02901W01-S 6-35
Jul 2008
I - IWU Chapter 6: Glossary of Technical Terms
INS IN Service.
INS Intelligent Network Service. A service provided using the
capabilities of an intelligent network. See also IN.
InterAlg Interference Algorithm.
Intermittent Intermittent alarms are transient and not usually
associated with a serious fault condition. After the
intermittent alarms are displayed in the Alarm window,
the operator must handle and clear the alarm. The system
reports every occurrence of an intermittent alarm unless it
is throttled. See also FMIC and OIC.
inter working The general term used to describe the inter-operation of
networks, services, supplementary services, and so on.
See also IWF.
Interval A recording period of time in which a statistic is pegged.
Interval expiry The end of an interval.
I/O Input/Output.
IOS Intelligent Optimization Service. Tool for improving the
network quality. The IOS generates reports based on
performance data from the BTS and OMC-R.
IP Initialization Process. The IP is primarily responsible for
bringing up the site from a reset, including code loading
the site from a suitable code source. IP also provides the
CSFP functionality, allowing two BSS code load version to
be swapped quickly, allowing the site to return to service
as soon as possible.
IP Internet Protocol. A standard protocol designed for
use in interconnected systems of packet-switched
computer communication networks. IP provides for
transmitting blocks of data called datagrams from sources
to destinations, where sources and destinations are
hosts identified by fixed-length addresses. The internet
protocol also provides for fragmentation and reassembly
of long datagrams, if necessary, for transmission through
small-packet networks. See also TCP and TCP/IP.
IPC Inter-Process Communication. Exchange of data between
one process and another, either within the same computer
or over a network.
IP, INP INtermodulation Products. Distortion. A type of spurious
emission.
IPR Intellectual PRoperty.
IPSM Integrated Power Supply Module (-48 V).
IPX Internet work Packet EXchange A networking protocol
used by the Novell NetWare operating systems. Like
UDP/IP, IPX is a datagram protocol used for connectionless
communications. Higher-level protocols are used for
additional error recovery services.
IR Incremental Redundancy (Hybrid Type II ARQ).
Continued
6-36 68P02901W01-S
Jul 2008
System Information: GSM Overview I - IWU
Iridium A communications system comprising a constellation of

66 low-earth-orbiting (LEO) satellites forming a mobile
wireless system allowing subscribers to place and
receive calls from any location in the world. The satellite
constellation is connected to existing terrestrial telephone
systems through a number of gateway ground-stations.
ISAM Indexed Sequential Access Method. A method for
managing the way a computer accesses records and files
stored on a hard disk. While storing data sequentially,
ISAM provides direct access to specific records through
an index. This combination results in quick data access
regardless of whether records are being accessed
sequentially or randomly.
ISC International Switching Center. The ISC routes calls
to/from other countries.
ISDN Integrated Services Digital Network. A digital network
using common switches and digital transmission paths
to establish connections for various services such as
telephony, data telex, and facsimile. See also B channel
and D channel.
ISG Motorola Information Systems group (formerly CODEX).
ISO International Organization for Standardization. ISO is a

worldwide federation of national standards bodies from
some 130 countries, one from each country.
ISQL An Interactive Structured Query Language client
application for the database server. See also IDS.
ISS Integrated Support Server. The ISS resides on a Sun
Netra t 1125 and performs the CGF, DNS, NTP, and NFS
functions for the GSN.
IST Integrated System Test.
ISUP ISDN User Part. An upper-layer application supported by
signaling system No. 7 for connection set up and tear
down.
IT Inactivity Test (Part of SCCP network connectivity).
ITC Information Transfer Capability. A GSM Bearer Capability
Element which is provided on the Dm channel to support
Terminal adaptation function to inter working control
procedures.
ITU International Telecommunication Union. An
intergovernmental organization through which public and
private Organizations develop telecommunications. It is
responsible for adopting international treaties, regulations,
and standards governing telecommunications.
ITU-T International Telecommunication Union -
Telecommunications Standardization Sector. The
CCITT, a group within the ITU, performed standardization
functions previously, .
Continued
68P02901W01-S 6-37
Jul 2008
k - KW Chapter 6: Glossary of Technical Terms
IWF inter working Function. A network functional entity which

provides network inter working, service inter working,
supplementary service inter working or signaling inter
working. It is a part of one or more logical or physical
entities in a GSM PLMN.
IWMSC inter working MSC. MSC that is used to deliver data to or
from SGSN.
IWU inter working Unit. Unit where the digital to analog (and
visa versa) conversion takes place within the digital GSM
network.
k - KW
k kilo (103).
k Windows size.
K Constraint length of the convolutional code.
KAIO Kernel Asynchronous Input/Output. Part of the OMC-R
relational database management system.
kb, kbit kilo-bit.
kbps kilo-bits per second.

kbyte kilobyte. 210 bytes = 1024 bytes.
Kc Ciphering key. A sequence of symbols that controls the
operation of encipherment and decipherment.
kHz kilo-Hertz.
Ki Individual subscriber authentication Key. Part of the
authentication process of the AUC.
KIO A class of processor.
KPI Key Performance Indicator.
KSW Kiloport SWitch board. TDM timeslot interchanger to
connect calls. Part of the BSS.
KSWX KSW Expander half size board. Fiber optic distribution of
TDM bus. Part of the BSS.
kW kilo-Watt.
L1 - LV
L1 Layer 1 (of a communications protocol).

Continued
6-38 68P02901W01-S
Jul 2008
System Information: GSM Overview L1 - LV
L2ML Layer 2 Management Link. L2ML is used for transferring

layer 2 management messages to TRX or BCF. One link
per TRX and BCF.
L2R Layer 2 Relay function. A function of the MS and IWF that
adapts a user's known layer 2 protocol LAPB onto RLP for
transmission between the MT and IWF.
L2R BOP L2R Bit Orientated Protocol.
L2R COP L2R Character Orientated Protocol.
LA Link Adaptation.
LA Location Area. An area in which the MS can move freely
without updating the location register. The LA can
comprise one or several base station areas.
LAC Location Area Code. The LAC is part of the LAI. It is an
operator defined code identifying the location area.
LAI Location Area Identity. The information indicating the
location area in which a cell is located. The LAI data on
the SIM is continuously updated to reflect the current
location of the subscriber.
LAN Local Area Network. A data communications system that
(a) lies within a limited spatial area, (b) has a specific user
group, (c) has a specific topology, and (d) is not a public
switched telecommunications network, but is connected
to one.
LANX LAN Extender half size board. Fiber optic distribution of
LAN to or from other cabinets. Part of BSS, and so on.
LAPB Link Access Protocol Balanced. The balanced-mode,
enhanced version of HDLC. Used in X.25 packet-switching
networks.
LAPD Link Access Protocol D-channel (Data). A protocol
that operates at the data link layer (layer 2) of the
OSI architecture. LAPD is used to convey information
between layer 3 entities across the frame relay network.
The D-channel carries signaling information for circuit
switching.
LAPDm Link Access Protocol on the Dm channel. A link access
procedure (layer 2) on the CCH for the digital mobile
communications system.
Layer 1 See OSI-RM and Physical Layer.
Layer 2 See OSI-RM and Data Link Layer.
Layer 3 See OSI-RM and Network Layer.
Layer 4 See OSI-RM and Transport Layer.
Layer 5 See OSI-RM and Session Layer.
Layer 6 See OSI-RM and Presentation Layer.
Layer 7 See OSI-RM and Application Layer.
Continued
68P02901W01-S 6-39
Jul 2008
L1 - LV Chapter 6: Glossary of Technical Terms
LC Inductor Capacitor. A type of filter.

LCF Link Control Function. LCF GPROC controls various links
in and out of the BSC. Such links include MTL, XBL, OMF,
and RSL. See also LCP.
LCN Local Communications Network. A communication
network within a TMN that supports data communication
functions (DCFs) normally at specified reference points q1
and q2. LCNs range from the simple to the complex. LCN
examples include point-to-point connections and networks
based on star and bus topologies.
LCP Link Control Processor. The LCP is a GPROC or PCMCIA
board device which supplies the LCF. Once the LCF has
been equipped, and assuming that GPROCs have been
equipped, processors are allocated by the software.
LCS Location Services.
LE Local Exchange.
LED Light Emitting Diode. A type of diode that emits light when
current passes through it. Depending on the material used
the color can be visible or infrared.
LF Line Feed. A code that moves the cursor on a display
screen down one line. In the ASCII character set, a line
feed has a decimal value of 10. On printers, a line feed
advances the paper one line.
LI Length Indicator. Delimits LLC PDUs within the RLC data
block, when a LLC PDU boundary occurs in the block.
LI Line Identity. The LI is made up of a number of information
units: the subscriber's national ISDN or MSISDN number;
the country code; optionally, sub address information. In
a full ISDN environment, the line identity includes all of
the address information necessary to identify a subscriber
unambiguously. The calling line identity is the line identity
of the calling party. The connected line identity is the line
identity of the connected party.
LLC Logical Link Control.
LLC Lower Layer Compatibility. The LLC can carry information
defining the lower layer characteristics of the terminal.
Lm Traffic channel with capacity lower than a Bm.
LMP LAN Monitor Process. Each GPROC which is connected to
a LAN has a LMP, which detects faults on the LAN. The
GPROC generate LAN alarms.
LMS Least Mean Squares. Parameters determined by
minimizing the sum of squares of the deviations.
LMSI Local Mobile Station Identity. A unique identity temporarily
allocated to visiting mobile subscribers to speed up the
search for subscriber data in the VLR, when the MSRN
allocation is done on a per cell basis.
Continued
6-40 68P02901W01-S
Jul 2008
System Information: GSM Overview M - MUX
LMT Local Maintenance Terminal. Diagnostic tool, typically an

IBM compatible PC.
LNA Low Noise Amplifier. An amplifier with low noise
characteristics.
LND Last Number Dialled.
Location area An area in which a mobile station can move freely without
updating the location register. A location area can
comprise one or several base station areas.
LPC Linear Predictive Coding. A method of digitally encoding
analog signals. It uses a single-level or multi-level sampling
system in which the value of the signal at each sample time
is predicted to be a linear function of the past values of
the quantified signal.
LPLMN Local PLMN.
LQC Link Quality Control.
LR Location Register. The GSM functional unit where MS
location information is stored. The HLR and VLR are
location registers.
LSSU Link Stations Signaling Unit (Part of MTP transport
system).
LSTR Listener Side Tone Rating. A rating, expressed in dB,
based on how a listener perceives the background noise
picked up by the microphone.
LTA Long Term Average. The value required in a BTS's GCLK
frequency register to produce a 16.384 MHz clock.
LTE Local Terminal Emulator.
LTP Long Term Predictive.
LTU Line Terminating Unit.
LU Local Units.
LU Location Update. The MS initiates a location update when
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.
Continued
68P02901W01-S 6-41
Jul 2008
M - MUX Chapter 6: Glossary of Technical Terms
M and TS Maintenance and TroubleShooting. Functional area of

Network Management software which (1) collects and
displays alarms, (2) collects and displays Software or
Hardware errors, and (3) activates test diagnostics at the
NEs (OMC).
MA Mobile Allocation. The radio frequency channels allocated
to the MS for use in its frequency hopping sequence.
MAC Medium Access Control. MAC includes the functions
related to the management of the common transmission
resources. These include the packet data physical channels
and their radio link connections. Two Medium Access
Control modes are supported in GSR5, dynamic allocation,
and fixed allocation.
MACN Mobile Allocation Channel Number. See also MA.
Macrocell A cell in which the base station antenna is generally
mounted away from buildings or above roof top level.
MAF Mobile Additional Function.
MAH Mobile Access Hunting supplementary service. An

automatic service which searches for the first available
mobile user out of a defined group.
MAI Mobile Allocation Index.
MAIDT Mean Accumulated Intrinsic Down Time.
MAINT MAINTenance.
MAIO Mobile Allocation Index Offset. The offset of the mobile
hopping sequence from the reference hopping sequence
of the cell.
MAP Mobile Application Part (part of SS7 standard). The
inter-networking signaling between MSCs and LRs and
EIRs.
MAPP Mobile Application Part Processor.
MB, MB Megabyte. 220 bytes = 1,048,576 bytes = 1024 kilobytes.
Mbps Mega bits per second.
MCAP Motorola Cellular Advanced Processor. The MCAP Bus is
the inter-GPROC communications channel in a BSC. Each
card cage in a BSC needs at least one GPROC designated
as a MCAP Server.
MCC Mobile Country Code. The first three digits of the IMSI,
used to identify the country.
MCDF Motorola Customer Data Format used by DataGen for
simple data entry and retrieval.
MCI Malicious Call Identification supplementary service. This
feature is supported by a malicious call trace function
by printing the report at the terminating MSC when the
mobile subscriber initiates a malicious call trace request.
MCS Modulation and Coding Scheme.
Continued
6-42 68P02901W01-S
Jul 2008
MCSC Motorola Customer Support Center.

MCU Main Control Unit for M-Cell2/6. Also referred to as the
Micro Control Unit in software.
MCUF Main Control Unit, with dual FMUX. (Used in
M-Cellhorizon).
MCU-m Main Control Unit for M-Cellmicro sites (M-Cellm). Also
referred to as the Micro Control Unit in software.
MCUm The software subtype representation of the Field
Replaceable Unit (FRU) for the MCU-m.
MD Mediation Device. The MD (which handles the Q3
interface) allows the OSI Processor to communicate
between the Network Management Center (NMC) and
OMC-R for network configuration, events, and alarms.
MDL mobile Management entity - Data Link layer.
ME Maintenance Entity (GSM Rec. 12.00).
ME Mobile Equipment. Equipment intended to access a set of
GSM PLMN and/or DCS telecommunication services, but
which does not contain subscriber related information.
Services is accessed while the equipment, capable of
surface movement within the GSM system area, is in
motion or during halts at unspecified points.
MEF Maintenance Entity Function (GSM Rec. 12.00). A function
which possesses the capability to detect elementary
anomalies and convey them to the supervision process.
MF MultiFrame. In PCM systems, a set of consecutive frames
in which the position of each frame can be identified by
reference to a multiframe alignment signal.
MF Multi-Frequency (tone signaling type). See DTMF.
MF MultiFunction block.
MGMT, mgmt Management.
MGR Manager.
MHS Message Handling System. The family of services
and protocols that provides the functions for global
electronic-mail transfer among local mail systems.
MHS Mobile Handling Service.
MHz Mega Hertz (106).
MI Maintenance Information.
MIB Management Information Base. A Motorola OMC-R
database. There is a CM MIB and an EM MIB.
MIC Mobile Interface Controller.
Microcell A cell in which the base station antenna is generally
mounted below roof top level. Radio wave propagation is
by diffraction and scattering around buildings, the main
propagation is within street canyons.
Continued
68P02901W01-S 6-43
Jul 2008
min minute(s).
s micro second (10-6).
BCU Micro Base Control Unit. The BCU is the Macro or
Microcell implementation of a BTS site controller.
MIT Management Information Tree. A file on the Motorola
OMC-R. The MIT file effectively monitors data on every
device and every parameter of each device that is in
the current versions of software on the OMC-R. The
data is stored as a text file on the OMC-R. The MIT file
also contains the hierarchical relationships between the
network devices.
MM Man Machine. Refer MMI.
MM Mobility Management. MM functions include
authorization, location updating, IMSI attach or detach,
periodic registration, ID confidentiality, paging, handover,
and so on.
MME Mobile Management Entity.
MMF Middle Man Funnel process.
MMI Man Machine Interface. The method by which the user
interfaces with the software to request a function or
change parameters. The MMI can run on a terminal at
the OMC, or the LMT. The MMI is used to display alarm
reports, retrieve device status, take modules out of service
and put modules into service.
MMI client A machine configured to use the OMC-R software from
the MMI server.
MMI processor MMI client or MMI server.
MMI server A computer which has its own local copy of the OMC-R
software. It can run the OMC-R software for MMI clients
to mount.
MML Man Machine Language. The tool of MMI.
MMS Multiple Serial Interface Link. (Refer also 2 Mbps link).
MNC Mobile Network Code. The fourth, fifth and optionally
sixth digits of the IMSI, used to identify the network.
MNT MaiNTenance.
Mobis Motorola Signaling Link between the BSC and BTS.
MO Mobile Originated.
MO/PP Mobile Originated Point-to-Point messages. Transmission
of a SMS from a mobile to a message handling system.
The maximum length of the message is 160 characters.
The message can be sent whether the MS is engaged in
a call or not.
MOMAP Motorola OMAP.
Continued
6-44 68P02901W01-S
Jul 2008
MoU Memorandum of Understanding. Commercial term. A MoU

usually sets out the broad parameters of an understanding
as well as the general responsibilities and obligations
of each party in a proposed venture. It has little legal
significance except to indicate the parties' commitments
and acts as an aid to interpreting the parties' intentions.
There are various types of MOUs: compliance MOUs help
ensure that all Motorola units comply with applicable laws
and regulations; intellectual property MOUs deal with
copyright, trademark, and patent rights; and business
arrangement MOUs relate to the terms and conditions of a
product or service transfer.
MPC Multi Personal Computer (was part of the OMC).
MPH (mobile) Management (entity) - PHysical (layer) [primitive].
MPROC Master Processor.
MPTY MultiParTY (Multi ParTY) supplementary service.
MPTY provides a mobile subscriber with the ability to
have a multi-connection call, that is, a simultaneous
communication with more than one party.
MPX MultiPleXed.
MRC Micro Radio Control Unit.
MRN Mobile Roaming Number.
MRP Mouth Reference Point. Facility for assessing handset and
headset acoustic responses.
MS Mobile Station. The GSM subscriber unit. A subscriber
handset, either mobile or portable, or other subscriber
equipment, such as facsimile machines, and so on.
MSC Mobile-services Switching Center, Mobile Switching
Center. The MSC handles the call setup procedures and
controls the location registration and handover procedures
for all except inter-BTS, inter-cell, and intra-cell handovers.
MSC controlled inter-BTS handovers can be set as an
option at the switch.
MSCM Mobile Station Class Mark.
MSCU Mobile Station Control Unit.
msec millisecond (.001 second).
MSI Multiple Serial Interface board. Intelligent interface to
two 2 Mbps digital links. See 2 Mbps link and DS-2.
Part of BSS.
MSIN Mobile Station Identification Number. The part of the IMSI
identifying the mobile station within its home network.
MSISDN Mobile Station International ISDN Number. Published
mobile number (see also IMSI). Uniquely defines the
mobile station as an ISDN terminal. It consists of three
parts: the Country Code (CC), the National Destination
Code (NDC) and the Subscriber Number (SN).
Continued
68P02901W01-S 6-45
Jul 2008
MSRN Mobile Station Roaming Number. A number assigned by

the MSC to service and track a visiting subscriber.
MSU Message Signal Unit (Part of MTP transport system). A
signal unit containing a service information octet and a
signaling information field which is retransmitted by the
signaling link control, if it is received in error.
MT Mobile Terminated. Describes a call or short message
destined for the MS.
MT (0, 1, 2) Mobile Termination. The part of the MS which terminates
the radio transmission to and from the network and adapts
terminal equipment (TE) capabilities to those of the radio
transmission. MT0 is mobile termination with no support
for terminal, MT1 is mobile termination with support for
a S-type interface and MT2 is mobile termination with
support for a R-type interface.
MTBE Mean Time Between Exceptions.
MTBF Mean Time Between Failures. An indicator of expected
system reliability calculated on a statistical basis from the
known failure rates of various components of the system.
MTBF is usually expressed in hours.
MTL Message Transfer Link. The MTL is the 64 kbps PCM
timeslot that is used to convey the SS7 signaling
information on the A interface between the MSC and the
BSC.
MTM Mobile-To-Mobile (call).
MTP Message Transfer Part. The part of a common-channel
signaling system that transfers signal messages and
performs associated functions, such as error control and
signaling link security.
MT/PP Mobile Terminated Point-to-Point messages. Transmission
of a short message from a message handling system to
a mobile. The maximum length of the message is 160
characters. The message can be received whether the MS
is engaged in a call or not.
MTTR Mean Time To Repair. The total corrective maintenance
time divided by the total number of corrective maintenance
actions during a given period of time.
Multiframe Two types of multiframe are defined in the system: a
26-frame multiframe with a period of 120 ms and a
51-frame multiframe with a period of 3060/13 ms.
MU Mark Up.
MUMS Multi User Mobile Station.
MUX Multiplexer. A device that combines multiple inputs into
an aggregate signal to be transported through a single
transmission channel.
6-46 68P02901W01-S
Jul 2008
System Information: GSM Overview NACK - nW
NACK - nW
NACK, Nack No Acknowledgment.

NACC Network Assisted Cell Change.
N/W Network.
NB Normal Burst (see Normal burst).
NBIN A parameter in the frequency hopping sequence generation
algorithm.
NCC Network Color Code. The NCC and the BCC are part of
the BSIC. The NCC comprises three bits in the range 000
to 111. It is the same as the PLMN Color Code. See also
NCC and BSIC.
NCELL Neighboring (of current serving) Cell.
NCH Notification CHannel. Part of the downlink element of the
CCCH reserved for voice group and/or voice broad-cast
calls and notification messages.
NCRM Network Cell Reselection Manager.
ND No Duplicates. A database column attribute meaning that
the column contains unique values (used only with indexed
columns).
NDC National Destination Code. Part of the MSISDN. A NDC is
allocated to each GSM PLMN.
NDUB Network Determined User Busy. A NDUB condition occurs
when a call is about to be offered and the maximum
number of total calls for the channel has been reached. In
practice, the total number of calls could be three: one for
the basic call, one for a held call and one for call waiting.
NE Network Element (Network Entity). A piece of
telecommunications equipment that provides support or
services to the user.
NEF Network Element Function block. A functional block
that communicates with a TMN for the purpose of being
monitored, or controlled, or both.
NET Norme Europennes de Telecommunications.
NetPlan An RF planning tool, NetPlan can import data from the
OMC and use it to carry out a network frequency re-plan.
Network Layer Refer OSI RM. The Network Layer responds to service
requests from the Transport Layer and issues service
requests to the Data Link Layer. It provides the functional
and procedural means of transferring variable length data
sequences from a source to a destination. The transfer is
through one or more networks while still maintaining the
quality of service requested by the Transport Layer. The
Network Layer performs network routing, flow control,
segmentation or desegmentation, and error control
functions.
Continued
68P02901W01-S 6-47
Jul 2008
NACK - nW Chapter 6: Glossary of Technical Terms
NF Network Function.
NFS Network File System. A file system that is distributed
over a computer network. Also, a file system, on a single
computer, that contains the low-level networking files for
an entire network.
NHA Network Health Analyst. The NHA is an optional feature.
It detects problems by monitoring network statistics and
events through the OMC-R. The NHA analyses the event
history, statistics, and network configuration data to try to
determine the cause of the detected problems.
NIB Network Interface Board.
NIC Network Interface Card. A network interface device in the
form of a circuit card that provides network access.
NIC Network Independent Clocking.
NIS Network Information Service. It allows centralized control
of network information for example, hostnames, IP
addresses, and passwords.
N-ISDN Narrowband Integrated Services Digital Network: Services
include basic rate interface (2B + D or BRI) and primary
rate interface (30B + D - Europe and 23B + D - North
America or PRI). Supports narrowband speeds at/or below
1.5 Mbps.
NIU Network Interface Unit. A device that performs interface
functions, such as code conversion, protocol conversion,
and buffering, required for communications to and from a
network.
NIU-m Network Interface Unit, micro. M-Cellmicro MSI.
NL See Network Layer.
NLK Network LinK processor(s).
Nm Newton metres.
NM Network Management (manager). NM is all activities
which control, monitor, and record the use and the
performance of resources of a telecommunications
network in order to provide telecommunication services to
customers or users at a certain level of quality.
NMASE Network Management Application Service Element.
NMC Network Management Center. The NMC node of the
GSM TMN provides global and centralized GSM PLMN
monitoring and control, by being at the top of the TMN
hierarchy and linked to subordinate OMC nodes.
NMSI National Mobile Station Identification number, or, National
Mobile Subscriber Identity. The NMSI consists of the MNC
and the MSIN.
NMT Nordic Mobile Telephone system. NMT produced the
world's first automatic international mobile telephone
system.
Continued
6-48 68P02901W01-S
Jul 2008
System Information: GSM Overview NACK - nW
NN No Nulls. A database column attribute meaning the

column must contain a value in all rows.
Normal burst A period of modulated carrier less than a timeslot.
NPI Number Plan Identifier.
NRZ Non Return to Zero. A code in which ones are represented
by one significant condition and zeros are represented by
another, with no neutral or rest condition.
NSAP Network Service Access Point. A NSAP is a registration
made by an application which specifies its desired listening
criteria. The registration is limited to a particular CPU
and port number. Criteria can include: DNICs, national
numbers, sub address ranges, protocol-ids, and extended
addresses.
NSP Network Service Provider. A national or regional company
that owns or maintains a portion of the network and resells
connectivity.
NSS Network Status Summary. A feature of the OMC-R MMI,
which provides different network maps giving visual
indication of the network configuration and performance,
and how the different network management functions are
implemented by the OMC-R.
NST Network Service Test(er). A PCU process that periodically
tests all alive NS-VCs on a PICP board.
NS-VC Network Service - Virtual Circuit.
NT Network Termination. Network equipment that provides
functions necessary for network operation of ISDN access
protocols.
NT Non Transparent.
NTAAB NTRAC Type Approvals Advisory Board. Committee
engaged in harmonization type approval of telecom
terminals in Europe.
NTP Network Time Protocol. A protocol built on top of TCP/IP
that assures accurate local timekeeping with reference to
radio, atomic or other clocks located on the Internet. This
protocol is capable of synchronizing distributed clocks
within milliseconds over long time periods.
Numbers # - The symbol used for number. 2 Mbps link - As used in
this manual set, the term applies to the European 4-wire
2.048 Mbps digital line or link which can carry 30 A-law
PCM channels or 120 16 kbps GSM channels. 4GL - 4th
Generation Language. Closer to human languages than
typical high-level programming languages. most 4GLs are
used to access databases.
NUA Network User Access.
NUI Network User Identification.
NUP National User Part. (part of SS7).
Continued
68P02901W01-S 6-49
Jul 2008
O - Overlap Chapter 6: Glossary of Technical Terms
NV Non-Volatile.
NVRAM Non-Volatile Random Access Memory. Static random
access memory which is made into non-volatile storage
either by having a battery permanently connected, or, by
saving its contents to EEPROM before turning the power
off and reloading it when power is restored.
nW Nano-Watt (10-9).
O - Overlap
O Optional.
OA Outgoing Access supplementary service. An arrangement
which allows a member of a CUG to place calls outside
the CUG.
OA and M Operation, Administration, and Management.
OAMP Operation, Administration, Maintenance, and Provisioning.
O and M Operation and Maintenance.
OASCU Off-Air-Call-SetUp. The procedure in which a
telecommunication connection is being established while
the RF link between the MS and the BTS is not occupied.
OCB Outgoing Calls Barred within the CUG supplementary
service. An access restriction that prevents a CUG member
from placing calls to other members of that group.
OCXO Oven Controlled Crystal Oscillator. High stability clock
source used for frequency synchronization.
OD Optional for operators to implement for their aim.
OFL % OverFlow.
Offline IDS shutdown state.
Online IDS normal operating state.
OIC Operator Initiated Clear. An alarm type. The OMC-R
operator must clear the OIC alarms after the fault
condition that caused the alarm is resolved. See also FMIC
and Intermittent.
OLM Off_Line MIB. A Motorola DataGen database, used to
modify and carry out radio frequency planning on multiple
BSS binary files.
OLR Overall Loudness Rating.
OMAP Operation and Maintenance Application Part (part of SS7
standard) (was OAMP).
OMC Operation and Maintenance Center. The OMC node of the
GSM TMN provides dynamic Operation and Maintenance
monitoring and control of the PLMN nodes operating in
the geographical area controlled by the specific OMC.
Continued
6-50 68P02901W01-S
Jul 2008
System Information: GSM Overview O - Overlap
OMC-G Operation and Maintenance Center - Gateway Part.

(Iridium).
OMC-G Operation and Maintenance Center - GPRS Part.
OMC-R Operation and Maintenance Center - Radio Part.
OMC-S Operation and Maintenance Center - Switch Part.
OMF Operation and Maintenance Function (at BSC).
OML Operation and Maintenance Link. The OML provides
communication between an OMC-R and a BSC or RXCDR
for transferring network management (Operation and
Maintenance) data.
OMP Operation and Maintenance Processor. Part of the BSC.
OMS Operation and Maintenance System (BSC-OMC).
OMSS Operation and Maintenance SubSystem.
OOS Out Of Service. Identifies a physical state. The OOS state
indicates the physical device is out of service. This state is
reserved for physical communication links. Also, identifies
a telephony state. The BTS device software uses the OOS
state to indicate that the BTS is out of service.
OPC Originating Point Code. A part of the label in a signaling
message that uniquely identifies, in a signaling network,
the (signaling) origination point of the message.
ORAC Olympus Radio Architecture Chipset.
OS Operating System. The fundamental program running on a
computer which controls all operations.
OSI Open Systems Interconnection. The logical structure
for communications networks standardized by the ISO.
The standard enables any OSI-compliant system to
communicate and exchange information with any other
OSI-compliant system.
OSI RM OSI Reference Model. An abstract description of the digital
communications between application processes running
in distinct systems. The model employs a hierarchical
structure of seven layers. Each layer performs value-added
service at the request of the adjacent higher layer and,
in turn, requests more basic services from the adjacent
lower layer: Layer 1 - Physical Layer, Layer 2 - Data Link
Layer, Layer 3 - Network Layer, Layer 4 - Transport
Layer, Layer 5 - Session Layer, Layer 6 - Presentation
Layer, Layer 7 - Application Layer.
OSF Operation Systems Function block.
OSF/MOTIF Open Software Foundation Motif. The basis of the GUI
used for the Motorola OMC-R MMI.
OSS Operator Services System.
Continued
68P02901W01-S 6-51
Jul 2008
PA - PXPDN Chapter 6: Glossary of Technical Terms
Overlap Overlap sending means that digits are sent from one
system to another as soon as they are received by the
sending system. A system using ~ will not wait until it
has received all digits of a call before it starts to send the
digits to the next system. This is the opposite of en bloc
sending where all digits for a given call are sent at one
time. Refer en bloc.
PA - PXPDN
P1, P2, P3 Puncturing Schemes 1, 2, and 3.

PA Power Amplifier.
PAB Power Alarm Board. Part of the BSS.
PABX Private Automatic Branch eXchange. A private automatic
telephone exchange that allows calls within the exchange
and also calls to and from the public telephone network.
PACCH Packet Associated Control Channel.
Packet A sequence of binary digits, including data and control
signals, that is transmitted and switched as a composite
whole.
Packet Switching The process of routing and transferring data through
addressed packets so that a channel is occupied during
the transmission of the packet only, and upon completion
of the transmission the channel is made available for the
transfer of other traffic.
PAD Packet Assembler or Disassembler facility. A hardware
device that allows a data terminal that is not set up for
packet switching to use a packet switching network.
It assembles data into packets for transmission, and
disassembles the packets on arrival.
Paging The procedure by which a GSM PLMN fixed infrastructure
attempts to reach the MS within its location area, before
any other network-initiated procedure can take place.
PATH CEPT 2 Mbps route through the BSS network.
PBCCH Packet Braodcast Control channel.
PBUS Processor Bus.
PBX Private Branch eXchange. In the general use of the term,
PBX is a synonym for PABX. However, a PBX operates
with only a manual switchboard; a private automatic
exchange (PAX) does not have a switchboard, a private
automatic branch exchange (PABX) may or may not have a
switchboard.
PC Personal Computer. A general-purpose single-user
microcomputer designed to be operated by one person
at a time.
Continued
6-52 68P02901W01-S
Jul 2008
System Information: GSM Overview PA - PXPDN
pCA PCU Central Authority. One pCA software process is

located at every PCU. The CA is in control of the PCU.
It is resident on the master DPROC (MPROC) only, and
maintains a list of the status of every device and every
software process at the site.
PCCCH Packet Common Control Channel.
PCH Paging CHannel. A common access RF channel providing
point-to-multipoint unidirectional signaling downlink.
Provides simultaneous transmission to all MSs over a wide
paging area.
PCHN Paging Channel Network.
PCHN Physical Channel. The physical channel is the medium
over which the information is carried. For GSM radio
communications, this would be the Air Interface. Each RF
carrier consists of eight physical channels (or timeslots)
used for MS communications. For a terrestrial interface
the physical channel would be cable. See also Physical
Layer.
PCI Packet Control Interface.
PCI Peripheral Component Interconnect. A standard for
connecting peripherals to a personal computer, PCI is a
64-bit bus, though it is usually implemented as a 32-bit bus.
PCM Pulse Code Modulation. Modulation in which a signal
is sampled, and the magnitude (with respect to a fixed
reference) of each sample is quantized and converted
by coding to a digital signal. Provides undistorted
transmission, even in the presence of noise. See also 2
Mbps link, which is the physical bearer of PCM.
pCM PCU Configuration Management. pCM is a GWM process.
It distributes all database changes performed at the BSC
to the PCU boards.
PCN Personal Communications Network. Any network
supporting PCS, but in particular DCS1800.
PCR Preventative Cyclic Retransmission. A form of error
correction suitable for use on links with long transmission
delays, such as satellite links.
PCS The U.S. Federal Communications Commission (FCC)
term used to describe a set of digital cellular technologies
being deployed in the U.S. PCS works over GSM, CDMA
(also called IS-95), and North American TDMA (also called
IS-136) air interfaces.
Continued
68P02901W01-S 6-53
Jul 2008
PCS System Personal Communications Services System. In PCS, a

collection of facilities that provides some combination of
personal mobility, terminal mobility, and service profile
management.
NOTE
As used here, facilities includes hardware,
software, and network components such as
transmission facilities, switching facilities,
signaling facilities, and databases.
PCS1900 A cellular phone network using the higher frequency
range allocated in countries such as the USA. It operates
on the frequency range, 1850 - 1910 MHz (receive) and
1930 - 1990 MHz (transmit).
PCU Packet Control Unit. A BSS component that provides GPRS
with packet scheduling over the air interface with the MS,
and packet segmentization and packetization across the
Frame Relay link with the SGSN.
PCU Picocell Control unit. Part of M-Cellaccess.
pd Potential difference. Voltage.
PD Protocol Discriminator field. The first octet of the packet
header that identifies the protocol used to transport the
frame.
PD Public Data. Refer PDN.
PDB Power Distribution Board.
PDCH Packet Data Channel. PDCH carries a combination of
PBCCH and PDTCH logical channels.
PDF Power Distribution Frame (MSC/LR).
PDN Public Data Network. A network established and operated
by a telecommunications administration, or a recognized
private operating agency, for the specific purpose of
providing data transmission services for the public.
PDP Packet Data Protocol.
PDTCH Packet Data Traffic Channels.
PDU Power Distribution Unit. The PDU consists consisting of
the Alarm Interface Board (AIB) and the Power Distribution
Board (PDB).
PDU Protected Data Unit.
PDU Protocol Data Unit. A term used in TCP/IP to refer to a unit
of data, headers, and trailers at any layer in a network.
PEDC Pan-European Digital Cellular network. The GSM network
in Europe.
Continued
6-54 68P02901W01-S
Jul 2008
Peg A single incremental action modifying the value of a

statistic. Also, A number indicating the use of a device or
resource. Each time the device or resource is used the
peg count is incremented.
Pegging Modifying a statistical value.
pFCP PCU Fault Collection Process. See pFTP.
pFTP PCU Fault Transaction Process. The pFTP resides on the
PSP as part of the GWM Functional Unit process. All
alarms at the PCU are reported to pFTP. All DPROCs and
the MPROC have a local pFCP to handle Software Fault
Management indications (SWFMs). The pFTP forwards
alarms to the Agent at the BSC and generates messages
to pCA for device transitions as needed, based on faults
reported.
PGSM Primary GSM. PGSM operates on the standard
GSM frequency range, 890 - 915 MHz (receive) and
935 - 960 MHz (transmit).
PH Packet Handler. A packet handler assembles and
disassembles packets.
PH PHysical (layer). See Physical Layer.
PHI Packet Handler Interface.
Physical Layer Refer OSI-RM. The Physical Layer is the lowest of seven
hierarchical layers. It performs services requested by
the Data Link Layer. The major functions and services
of the layer are: (a) establishment and termination of a
connection to a communications medium; (b) participation
in the process of sharing communication resources
among multiple users; and, (c) conversion between the
representation of digital data in user equipment and the
corresponding signals transmitted over a communications
channel.
PI Presentation Indicator. The PI forms part of the calling
name information. Depending on database settings, the PI
can prevent the called party from seeing the identity of
the calling party.
PIA Packet Immediate Assignment.
Picocell A cell site where the base station antenna is mounted
within a building.
PICP Packet Interface Control Processor. A PCU hardware
component, the PICP is a DPROC board used for network
interfacing functions such as SGSN and BSC.
PICS Protocol Implementation Conformance Statement. A
statement made by the supplier of an implementation or
system claimed to conform to a given specification, stating
which capabilities have been implemented.
PID Process IDentifier or Process ID.
PIM PCM Interface Module (MSC).
Continued
68P02901W01-S 6-55
Jul 2008
PIN Personal Identification Number. A password, typically four

digits entered through a telephone keypad.
PIN Problem Identification Number.
PIX Parallel Interface Extender half size board. Customer
alarm interface, part of the BSS. The PIX board provides a
means of wiring alarms external to the BSS, BSC, or BTS
into the base equipment.
PIXT or PIXIT Protocol Implementation eXtra information for Testing.
A statement made by a supplier or implementor of
an implementation under test (IUT) which contains
information about the IUT and its testing environment
which enables a test laboratory to run an appropriate test
suite against the IUT.
PK Primary Key. A database column attribute, the primary key
is a not-null, non-duplicate index.
PL See Presentation Layer.
Plaintext Unciphered data.
PlaNET Frequency planning tool.
PLL Phase Lock Loop (refers to phase locking the GCLK in the
BTS). PLL is a mechanism whereby timing information is
transferred within a data stream and the receiver derives
the signal element timing by locking its local clock source
to the received timing information.
PLMN Public Land Mobile Network. The mobile communications
network.
PM Performance Management. An OMC application. PM
enables the user to produce reports specific to the
performance of the network.
PMA Prompt Maintenance Alarm. An alarm report level;
immediate action is necessary. See also DMA.
PMC PCI Mezzanine Card.
PMR Packet Management Report.
PMS Pseudo MMS.
PM-UI Performance Management User Interface.
PMUX PCM MUltipleXer.
PN Permanent Nucleus group of the GSM committee.
PNE Prsentation des Normes Europennes. Presentation rules
of European Standards.
POI Point of Interconnection. A point at which the cellular
network is connected to the PSTN. A cellular system may
have multiple POIs.
POTS Plain Old Telephone Service. Basic telephone service
without special features such as call waiting, call
forwarding, and so on.
Continued
6-56 68P02901W01-S
Jul 2008
pp, p-p Peak-to-peak.

PP Point-to-Point.
ppb Parts per billion.
PPB PCI (Peripheral Component Interconnect) to PCI Bridge
board. The PPB allows an IMPORT to be linked to a
separate bus. The PUB and IMPORT are paired boards.
PPE Primitive Procedure Entity.
ppm Parts per million (x 10-6).
Pref CUG Preferential CUG. A Pref CUG, which can be specified for
each basic service group, is the nominated default CUG to
be used when the network receives no explicit CUG index.
Presentation Layer See OSI RM. The Presentation Layer responds to service
requests from the Application Layer and issues service
requests to the Session Layer. It relieves the Application
Layer of concern regarding syntactical differences in data
representation within the end-user systems.
Primary Cell A cell which is already optimized in the network and has
a co-located neighbor whose cell boundary follows the
boundary of the said cell. The primary cell has a preferred
band equal to the frequency type of the coincident cell.
PRM Packet Resource Manager. The PRM is a PRP process. It
performs all RLC/MAC functions and realizes UL/DL power
control and timing advance.
PROM Programmable Read Only Memory. A storage device that,
after being written to once, becomes a read-only memory.
PRP Packet Resource Process(or). A PCU hardware component,
the PRP is a DPROC board which manages the packet
resources at the PCU and is the processor where all of
the radio-related processing occurs. GPRS channels are
routed to PRPs which perform the RLC/MAC processing,
air interface scheduling, and frame synchronization of the
channels.
Ps Location probability. Location probability is a quality
criterion for cell coverage. Due to shadowing and fading, a
cell edge is defined by adding margins so that the minimum
service quality is fulfilled with a certain probability.
PS Puncturing Scheme.
PSA Periodic Supervision of Accessibility. PSA is a fault
management function. It periodically sends messages to
BSSs requesting information on their current state. This
verifies whether the BSSs are operational or not. If a BSS
fails to respond to a PSA request for its status, the OMC-R
generates an alarm for that BSS.
PSI Packet System Information.
PSAP Presentation Services Access Point.
Continued
68P02901W01-S 6-57
Jul 2008
QA- Quiesent mode Chapter 6: Glossary of Technical Terms
pSAP PCU System Audit Process. pSAP is a GWM process. It

periodically monitors the soft devices to maintain the
reliability of the system.
PSM Power Supply Module.
pSM PCU Switch Manager. The pSM resides on the PSP as part
of the GWM Functional Unit process. The pSM maintains
data paths within the PCU and communicates with the
BSC.
PSP PCU System Processor board. Part of GPRS.
PSPDN Packet Switched Public Data Network. See Packet
Switching and PDN.
PSTN Public Switched Telephone Network. The domestic
landline telecommunications network. It is usually
accessed by telephones, key telephone systems, private
branch exchange trunks, and data arrangements.
PSU Power Supply Unit.
PSW Pure Sine Wave.
PTACH Packet Timing Advance Control Channel.
PTO Public Telecommunications Operator.
PTR Packet Timeslot Reconfiguration.
PUA Packet Uplink Assignment.
PUCT Price per Unit Currency Table. The PUCT is the value of
the Home unit in a currency chosen by the subscriber. The
PUCT is stored in the SIM. The value of the PUCT can be
set by the subscriber and can exceed the value published
by the HPLMN. The PUCT value does not have any impact
on the charges raised by the HPLMN.
PVC Permanent Virtual Circuit. Also, in ATM terminology,
Permanent Virtual Connection. A virtual circuit that is
permanently established, saving the time associated with
circuit establishment and tear-down. See also SVC.
PW Pass Word.
PWR Power.
PXPDN Private eXchange Public Data Network. See also PDN.
QA- Quiesent mode
QA Q (Interface) - Adapter. TMN interface adapter used

to communicate with non-TMN compatible devices and
objects. Used to connect MEs and SEs to TMN (GSM Rec.
12.00).
Q3 Interface between NMC and GSM network.
Q-adapter See QA.
Continued
6-58 68P02901W01-S
Jul 2008
System Information: GSM Overview R - RXU
QAF Q-Adapter Function.

QEI Quad European Interface. Interfaces four 2 Mbps circuits
to TDM switch highway. Refer MSI.
QIC Quarter Inch Cartridge (Data storage format).
QoS Quality Of Service. An alarm category which indicates that
a failure is degrading service.
Queue Data structure in which data or messages are temporarily
stored until a software process retrieves them. Also a
series of calls waiting for service. See also FIFO.
Quiescent mode IDS intermediate state before shutdown.
R - RXU
R Value of reduction of the MS transmitted RF power relative

to the maximum allowed output power of the highest
power class of MS (A).
RA RAndom mode request information field.
RA Radio Access.
RA Routing Area.
RA250 Rural Area with the MS travelling at 250 kph. Dynamic
can be measured. See also TU3, TU50, HT100 and EQ50.
RAB Random Access Burst. Data sent on the RACH.
RACCH Random Access Control CHannel. A GSM common control
channel used to originate a call or respond to a page.
RACH Random Access CHannel. The MS uses the RACH to
request access to the network. See also RAB.
Radio Frequency A term applied to the transmission of electromagnetically
radiated information from one point to another, usually
using air or vacuum as the transmission medium. An
electromagnetic wave frequency intermediate between
audio frequencies and infrared frequencies used in radio
and television transmission.
RAM Random Access Memory. A read/write,
non-sequential-access memory in which information can
be stored, retrieved and modified. This type of memory is
generally volatile (that is, its contents are lost if power
is removed).
RAND RANDom number (used for authentication). The SGSN
sends the RAND to the MS as part of the authentication
process.
RAT Radio Access Technology.
RATI Receive Antenna Transceiver Interface.
Continued
68P02901W01-S 6-59
Jul 2008
R - RXU Chapter 6: Glossary of Technical Terms
RAx Rate Adaptation.

RBDS Remote BSS Diagnostic System (a discontinued Motorola
diagnostic facility).
RBER Residual Bit Error Ratio. RBER is a ratio of the number
of bits in error to the total number of bits received,
within error detected speech frames defined as good. The
measurement period over which the calculation is made is
480 ms. During this period, 24 speech frames are decoded
and a ratio calculated. By referring to a lookup table, the
ratio is then converted to a RBER Quality number between
0 and 7.
RBTS Remote Base Transceiver Station. A BTS that is not
co-located with the BSC that controls it.
RCB Radio Control Board. Part of the DRCU.
RCI Radio Channel Identifier. The unique identifier of the radio
channel portion of the circuit path.
RCI Radio Channel Interface. The RCI changes the MS address
used in the RSS (channel number) to the address used in
Layer 3 in the BSC CP.
RCP Radio Control Processor.
RCU Radio Channel Unit. Part of the BSS. Contains transceiver,
digital control circuits, and power supply. Note: The RCU
is now obsolete, see DRCU.
RCVR Receiver.
RDB Requirements Database.
RDBMS Relational DataBase Management System (INFORMIX).
The database management system for the OMC-R
database.
RDI Restricted Digital Information.
RDIS Radio Digital Interface System.
RDM Reference Distribution Module. The RDM provides a stable
3 MHz reference signal to all transceivers. It is used for
carrier and injection frequency synthesis.
RDN Relative Distinguished Name. A series of RDNs form a
unique identifier, the distinguished name, for a particular
network element.
REC, Rec RECommendation.
Reciprocal neighbor Used to describe adjacent cells; each being designated as
a neighbor of the other. Also known as bidirectional and
two-way neighbor.
Registration The process of an MS registering its location with the MSC
in order to make or receive calls. This occurs whenever
the MS first activates or moves into a new service area.
REJ REJect(ion).
REL RELease.
Continued
6-60 68P02901W01-S
Jul 2008
RELP Residual Excited Linear Predictive. A form of speech

coding. RELP coders are usually used to give good quality
speech at bit rates in the region of 9.6 kbps.
RELP-LTP RELP Long Term Prediction. A name for GSM full rate.
Refer Full Rate.
Remotely Tuned Combiner A combiner device which houses two processors (for
paired-redundancy) and several tuneable cavities. See
also COMB.
resync Resynchronize or resynchronization.
REQ REQuest.
Reuse Pattern The minimum number of cells required in a pattern before
channel frequencies are reused, to prevent interference.
Varies between cell configuration type and channel type.
The pattern shows assignments of adjacent channels to
minimize interference between cells and sectors within
the pattern area.
Revgen A Motorola DataGen utility for producing a MMI script
from a binary object database.
RF See Radio Frequency.
RFC, RFCH Radio Frequency Channel. A partition of the system RF
spectrum allocation with a defined bandwidth and center
frequency.
RFE Radio Front End (module).
RFE Receiver Front End (shelf).
RFEB Receiver Front End Board. Part of DRCU II.

RFI Radio Frequency Interference.
RFM Radio Frequency Module.
RFN Reduced TDMA Frame Number.
RFU Reserved for Future Use.
RJ45 Registered Jack 45. An eight-wire connector used
commonly to connect computers onto a local-area networks
(LAN), especially Ethernet.
RISC Reduced Instruction Set Computer. A type of
microprocessor that recognizes a relatively limited number
of instruction types, allowing it to operate at relatively
higher speeds.
RL Remote login. RL is a means by which the operator
performs configuration management, fault management,
and some performance management procedures at the
NEs. The RL software manages the X.25 connection for
remote login. The circuit is made by the OMC-R calling
the NE.
RLC Release Complete. A SCCP message type used with RLSD
to release a connection.
Continued
68P02901W01-S 6-61
Jul 2008
R - RXU Chapter 6: Glossary of Technical Terms
RLC Radio Link Control. Air interface transmission layer. The

RLC function processes the transfer of PDUs from the LLC
layer.
RLM RF Link Manager.
RLP Radio Link Protocol. An ARQ protocol used to transfer user
data between the MT and IWF. See GSM 04.22.
RLR Receive Loudness Rating. Refer SLR.
RLSD ReLeaSeD. A SCCP message type used with RLC to release
a connection.
RMS Root Mean Square (value). The most common
mathematical method of defining the effective voltage or
current of an ac wave. For a sine wave, the rms value is
0.707 times the peak value.
RMSU Remote Mobile Switching Unit. A RMSU is a line
concentrator. It is inserted between the MSC and some of
the BSS sites served by the MSC to reduce the number of
terrestrial signaling and traffic circuits required.
RNTABLE Table of 128 integers in the hopping sequence.
ROAM Reliability, Operability, Availability, Maintainability.
Roaming Situation where mobile station operates in a cellular system
other than the one from which service is subscribed.
ROM Read Only Memory. Computer memory that allows fast
access to permanently stored data but prevents addition to
or modification of the data. ROM is inherently non-volatile
storage - it retains its contents even when the power is
switched off.
ROSE Remote Operations Service Element. An ASE which
carries a message between devices over an association
established by ASCE (a CCITT specification for operation
and maintenance (OMC)).
Roundtrip Time period between transmit and receive instant of
a timeslot in the BTS, propagation determined by the
response behavior of the MS and the MS to BTS delay
distance.
RPE Regular Pulse Excited (codec). Refer RPE-LTP.
RPE-LTP Regular Pulse Excitation - Long Term Prediction. The GSM
digital speech coding scheme. GSM uses a simplified RPE
codec, with long-term prediction, operating at 13 kbps to
provide toll quality speech.
RPOA Recognized Private Operating Agency. Private
telecommunications operator recognized by the
appropriate telecommunications authority.
RPR Read Privilege Required. Part of the table structure of the
OMC database schema. Access to the column is allowed
only for privileged accounts.
Continued
6-62 68P02901W01-S
Jul 2008
RR Radio Resource management. Part of the GSM

management layer. The functions provided by RR
include paging, cipher mode set, frequency redefinition,
assignments, handover and measurement reports.
RR Receive Ready.
RRSM Radio Resource State Machine. Translates messages
through Call Processing (CP). Activates and deactivates
radio channels as controlled by the CRM.
RRSM Radio Resource Switch Manager.
RS232 Recommended Standard 232. The interface between a
terminal (DTE) and a modem (DCE) for the transfer of
serial data. Standard serial interface.
RSE Radio System Entity.
RSL Radio Signaling Link. RSL is used for signaling between
the BSC and BTSs. The interface uses a 64 kbps timeslot
with a LAPD protocol.
RSLF Radio System Link Function.
RSLP Radio System Link Processor.
RSS Radio subsystem (replaced by BSS).
RSSI Received Signal Strength Indicator. A parameter returned
from a transceiver that gives a measure of the RF signal
strength between the MS and BTS, either uplink or
downlink.
RSZI Regional Subscription Zone Identity. The RSZI defines the
regions in which roaming is allowed. The elements of the
RSZI are: The Country Code (CC) which identifies the
country in which the GSM PLMN is located. The National
Destination Code (NDC) which identifies the GSM PLMN
in that country. The Zone Code (ZC) which identifies a
regional subscription zone as a pattern of allowed and not
allowed location areas uniquely within that PLMN.
RTC Remotely Tuneable Channel Combiner. RTCs are used
to fine-tune the cavities to the right frequency. A poorly
tuned cavity can cause power destined for the antenna
to be reversed.
RTE Remote Terminal Emulator.
RTF Radio Transceiver Function. RTF is the function that
supports the air interface channel and the DRI/Transceiver
pair. When equipping a DRI at a remote BTS, one or more
RTFs must be equipped.
RTF Receive Transmit Functions.
RTS Request to Send. A handshaking signal used with
communication links, especially RS232 or CCITT Rec. V.24
to indicate (from a transmitter to a receiver) that data is
ready for transmission. See also CTS.
RU Rack Unit.
Continued
68P02901W01-S 6-63
Jul 2008
S7- SYSGEN Chapter 6: Glossary of Technical Terms
Run level System processor operating mode.

Rx Receive(r).
RX Receive window buffer.
RXCDR Remote Transcoder. An RXCDR is used when the
transcoding is performed at a site away from the BSC.
This site would be at or near the MSC. This enables 4:1
multiplexing in which the transcoded data for four logical
channels is combined onto one 64 kbps link, thus reducing
the number of links required for interconnection to the
BSCs. See also XCDR.
RXF Receive Function (of the RTF).
RXLEV Received signal level. An indication of received signal
level based on the RSSI. RXLEV is one of the two criteria
for evaluating the reception quality (the basis for handover
and power control). See also RXQUAL. The MS reports
RXLEV values related to the apparent received RF signal
strength. It is necessary for these levels to attain sufficient
accuracy for the correct functioning of the system.
RXLEV-D Received signal level downlink.
RXLEV-U Received signal level uplink.
RXQUAL Received signal quality. An indication of the received
signal quality based on the BER. RXQUAL is one of the two
criteria for evaluating the reception quality (the basis for
handover and power control). See also RXLEV. The MS
measures the received signal quality, which is specified in
terms of BER before channel decoding averaged over the
reporting period of length of one SACCH multiframe.
RXQUAL-D Received signal quality downlink.
RXQUAL-U Received signal quality uplink.
RXU Remote Transcoder Unit. The shelf which houses the
remote transcoder modules in a BSSC cabinet at a remote
transcoder site.
S7- SYSGEN
S7 See SS7.
S/W SoftWare.
SABM Set Asynchronous Balanced Mode. A message which
establishes the signaling link over the air interface.
SABME SABM Extended.
SACCH Slow Associated Control CHannel. A GSM control channel
used by the MS for conveying power control and timing
advance information in the downlink direction, and RSSI
and link quality reports in the uplink direction.
Continued
6-64 68P02901W01-S
Jul 2008
System Information: GSM Overview S7- SYSGEN
SACCH/C4 Slow Associated Control CHannel/SDCCH/4.

SACCH/C8 Slow Associated Control CHannel/SDCCH/8.
SACCH/T Slow Associated Control CHannel/Traffic channel.
SACCH/TF Slow Associated Control CHannel/Traffic channel Full rate.
SACCH/TH Slow Associated Control CHannel/Traffic channel Half rate.
SAGE A brand of trunk test equipment.
SAP Service Access Point. In the reference model for OSI, SAPs
of a layer are defined as gates through which services are
offered to an adjacent higher layer.
SAP System Audits Process. SAP is on each GPROC in the BSS.
It monitors the status of the BSS on a periodic (scheduled)
and on-demand basis during normal mode. SAP detects
faulty or degrading hardware and software (through
the use of audit tests) and notifies the Alarms handling
software of the condition.
SAPI Service Access Point Indicator (identifier). The OSI term
for the component of a network address which identifies
the individual application on a host which is sending or
receiving a packet.
SAW Surface Acoustic Wave. SAW devices basically consist
of an input transducer to convert electrical signals to
tiny acoustic waves, which then travel through the solid
propagation medium to the output transducer where they
are reconverted to electrical signals. SAW band pass filters
are used for sorting signals by frequency.
SB Synchronization Burst (Refer synchronization burst).
SBUS Serial Bus. A SBUS is a logical device made up of the
communication path between the GPROCs and LANX
cards in a cage.
SC Service Center (used for Short Message Service).
SC Service Code.
SCCA System Change Control Administration. Software module
which allows full or partial software download to the NE
(OMC).
SCCP Signaling Connection Control Part (part of SS7).
SCEG Speech Coding Experts Group (of GSM).
SCH Synchronization CHannel. A GSM broadcast
control channel used to carry information for frame
synchronization of MSs and identification of base stations.
SCI Status Control Interface. A slave to the Status Control
Manager.
SCIP Serial Communication Interface Processor.
Continued
68P02901W01-S 6-65
Jul 2008
SCM Status Control Manager. Accepts messages from other

processors within the switch requesting status displays
in the form of one or more lights on a hardware panel.
The SCM maps the status display requests into specific
commands to the status control interface processor to turn
on and/or turn off lights.
SCN Sub-Channel Number. One of the parameters defining a
particular physical channel in a BS.
SCP Service Control Point (an intelligent network entity).
SCSI Small Computer Systems Interface. A
processor-independent standard for system-level
interfacing between a computer and intelligent devices
including hard disks, floppy disks, CD-ROM, printers,
scanners, and many more. SCSI-1 can connect up to seven
devices to a single SCSI adaptor (or host adaptor) on the
computer's bus.
SCU Slim Channel Unit.
SCU900 Slim Channel Unit for GSM900.
SDCCH Standalone Dedicated Control CHannel. A GSM control
channel where the majority of call setup occurs. Used for
MS to BTS communications before MS assigned to TCH.
A single MS uses a SDCCH for call setup, authentication,
location updating, and SMS point to point.
SDL Specification Description Language. A method for visually
depicting the functionality of call processing, operation
and maintenance software.
SDM Sub-rate Data Multiplexer.
SDT SDL Development Tool. A software tool to model and
validate real time, state-based product software designs.
SDU Service Data Unit. In layered systems, a user of the
services of a given layer sends a set of data, and is
transmitted to a peer service user semantically unchanged.
SE Support Entity. Refer SEF.
Secondary Cell A cell which is not optimized in the network and has
a co-located neighbor whose cell boundary follows the
boundary of the said cell. The secondary cell has a
preferred band the same as that of its own frequency type.
SEF Support Entity Function. SEFs are functions not directly
involved in the telecommunication process. They include
fault localization, protection switching, and so on. (GSM
Rec.12.00).
Session Layer Refer OSI RM. The Session Layer responds to service
requests from the Presentation Layer and issues service
requests to the Transport Layer. It provides the mechanism
for managing the dialogue between end-user application
processes. It provides for either duplex or half-duplex
operation and establishes checkpointing, adjournment,
termination, and restart procedures.
Continued
6-66 68P02901W01-S
Jul 2008
SFH Synthesizer Frequency Hopping. The principle of SFH is

that every mobile transmits its time slots according to a
sequence of frequencies that it derives from an algorithm.
The frequency hopping occurs between time slots and,
therefore, a mobile station transmits (or receives) on a
fixed frequency during one time slot. It must then hop
before the time slot on the next TDMA frame. Due to the
time needed for monitoring other base stations the time
allowed for hopping is approximately 1 ms, according to
the receiver implementation. The receive and transmit
frequencies are always duplex frequencies.
SGSN Serving GPRS Support Node. The SGSN provides the
control, transmission, OAMP, and charging functions. It
keeps track of the individual MS locations, and performs
security functions and access control. The SGSN is
connected to the BSS through a Frame Relay network.
SI Screening Indicator. The supplementary service (SS)
screening indicator is sent by the MS at the beginning of
the radio connection to allow the network to assess the
capabilities of the MS and hence determine either whether
a particular network initiated SS operation is invoked or
which version of a network initiated SS operation should
be invoked. The SS screening indicator is only relevant to
network initiated SS operation and is valid for the duration
of a radio connection.
SI Service inter working. Part of the IWF.
SI Supplementary Information.
SI System Information.
SIA Supplementary Information A.
SID Silence Descriptor. The transmission of comfort noise
information to the RX side is achieved with a SID frame.
A SID frame is transmitted at the end of speech bursts
and serves as an end of speech marker for the RX side. In
order to update the comfort noise characteristics at the
RX side, SID frames are transmitted at regular intervals
also during speech pauses. This also serves the purpose
of improving the measurement of the radio link quality by
the radio subsystem (RSS).
SIF Signal Information Field. The bits of a message signal unit
that carry information for a certain user transaction; the
SIF always contains a label.
Signaling System No.7 See SS7.
SIM Subscriber Identity Module. Removable module which
is inserted into a mobile equipment; it is considered as
part of the MS. It contains security-related information
(IMSI, Ki, PIN), other subscriber related information and
the algorithms A3 and A8.
SIMM Single Inline Memory module.
Continued
68P02901W01-S 6-67
Jul 2008
SIMM System Integrated Memory Module. A small plug-in circuit

board providing additional RAM for a computer.
SIO Service Information Octet. Eight bits contained in a
message signal unit, comprising the service indicator and
sub-service field. A value in the SIF of the SS7 signaling
message specifying the User Part type.
SITE BSC, BTS or collocated BSC-BTS site.
SIX Serial Interface eXtender. Converts interface levels to
TTL levels. Used to extend 2-serial ports from GPROC to
external devices (RS232, RS422, and fiber optics).
SK Secondary Key. A database column attribute, the
secondary key indicates an additional index and/or usage
as a composite key.
SL See Session Layer.
SL Signaling Link. The signaling links between the various
network elements are: Remote BTS to BSC - Radio
Signaling Link (RSL), BSC to MSC - Message Transfer Link
(MTL), OMC (R) to BSS - Operation and Maintenance Link
(OML), Remote XCDR to BSC - XCDR signaling Link (XBL),
CBC to BSC - Cell Broadcast Link (CBL).
SLNK Serial Link. One of four communications paths between
SCIP and peripheral equipment. The information on the
link is sent serially in a bit-synchronous format.
SLR Send Loudness Rating. The SLR, in the mobile to land
direction, and the Receive Loudness Rating (RLR) in
the land to mobile direction, determine the audio signal
levels for the customers speech. The loudness ratings are
calculated from the send and receive sensitivity masks or
frequency responses.
SLTA Signaling Link Test Acknowledge. Message sent from the
MSC to the BSC in response to an SLTM.
SLTM Signaling Link Test Message. During the process of
bringing an MTL link into service, the BSC sends an SLTM
message to the MSC. The MSC responds with an SLTA
message.
SM Switch Manager. The function of the SM is to connect an
MS terrestrial trunk from the MSC (designated by the
MSC), to the radio channel given to an MS by the cell
resource manager in the BSS software.
SM Summing Manager.
SMAE System Management Application Entity (CCITT Q795,
ISO 9596). OSI terminology for a software Management
Information Server that manages a network.
SMASE System Management Application Service Element.
SMCB Short Message Cell Broadcast.
Continued
6-68 68P02901W01-S
Jul 2008
SME Short Message Entity. An entity that can send or receive

Short Messages. The SME is located in a fixed network,
the MS, or a SC. See also SMS.
SMG Special Mobile Group. To avoid confusion between the
GSM system and the GSM committee with its wider
responsibilities, the committee was renamed SMG in 1992.
SMP Motorola Software Maintenance Program. A Motorola
program designed to ensure the highest quality of software
with the highest level of support.
SMS Short Message Service. SMS is a globally accepted
wireless service that enables the transmission of
alphanumeric messages between mobile subscribers and
external systems such as electronic mail, paging, and
voice-mail systems. It transfers the short messages, up to
160 characters, between Smts and MSs through a SMS-SC.
See also SMS-SC, SMS/PP and Smt.
SMSCB Short Message Service Cell Broadcast. SMSCB is a service
in which short messages is broadcast from a PLMN to
MSs. SMSCB messages come from different sources (for
example, traffic reports, weather reports). The MS does
not acknowledge the messages. Reception of SMSCB
messages by the MS is only possible in idle mode. The
PLMN operator, in agreement with the provider of the
information selects the geographical area over which each
message is transmitted.
SMS-SC Short Message Service - Service Center. SMS-SC is an
inter working unit between stationary networks and the
GSM Network. It acts as a store and forward center for
short messages. See also SMS, SMS/PP and Smt.
SMS/PP Short Message Service/Point-to-Point. Two different
point-to-point services have been defined: Mobile
Originated (MO) and Mobile Terminated (MT). A short
message always originates or terminates in the GSM
network. This means that short messages can never
be sent between two users both located in stationary
networks. See also SMS, SMS-SC and, Smt.
Smt Short message terminal. See also SMS, SMS-SC
and,SMS/PP. There are different types of Smt interfaces,
one being the Computer Access Interface which provides
services for external computers communicating with
SMS-SCs through the Computer Access Protocol.
SN Subscriber Number.
SND SeND.
SNDR SeNDeR.
SNR Serial NumbeR.
SOA Suppress Outgoing Access (CUG SS). An arrangement
which prevents a member of a CUG placing calls outside
the CUG.
Continued
68P02901W01-S 6-69
Jul 2008
Software Instance A complete set of software and firmware objects including

the database object.
SP Service Provider. The organization through which the
subscriber obtains GSM telecommunications services. This
is a network operator or possibly a separate body.
SP Signaling Point. A signaling point is a node within a SS7
network.
SP Special Product.
SP SPare.
SPARC Scalable Processor ArChitecture. A32-bit and 64-bit
microprocessor architecture from Sun Microsystems
that is based on the Reduced Instruction Set Computer
(RISC). SPARC has become a widely-used architecture for
hardware used with UNIX-based operating systems.
SPC Signaling Point Code.
SPC Suppress Preferential CUG. Prohibits the use of the
preferential CUG, on a per call basis.
SPI Signaling Point Inaccessible.
SPP Single Path Preselector.
SQE Signal Quality Error.
SQL Structured Query Language. The standard language for
relational database management systems as adopted by the
American National Standards Institute (ANSI X3.135-1989)
and the International Standards Organization (ISO
9075-1989).
SRD Service Request Distributor.
SRES Signed RESponse (authentication). The MS calculates the
SRES, by using the RAND, and sends it to the SGSN to
authenticate the MS.
SS Supplementary Service. A modification of, or a supplement
to, a basic telecommunication service.
SS System Simulator.
SS7 ITU-TSS Common Channel Signaling System No. 7. Also
known as C7, S7 or SS#7. The standard defines the
procedures and protocol by which network elements in
the PSTN exchange information over a digital signaling
network to effect wireless (cellular) and wireline call
setup, routing, and control.
SSA SubSystem-Allowed. SSA is used for SCCP subsystem
management. A SSA message is sent to concerned
destinations to inform those destinations that a subsystem
which was formerly prohibited is now allowed. (see ITU-T
Recommendation Q.712 para 1.15).
SSAP Site System Audits Processor.
Continued
6-70 68P02901W01-S
Jul 2008
SSC Supplementary Service Control string. When a subscriber

selects a supplementary service control from the menu in
a GSM network, the mobile station invokes the SSC by
sending the network the appropriate functional signaling
message.
SSF Subservice Field. The level 3 field containing the network
indicator and two spare bits.
SSM SCCP Switch Manager.
SSM Signaling State Machine.
SSN SubSystem Number. In SS7, each signaling point (SP) can
contain a number of subsystems. Each subsystem has a
unique ID, the SSN (for example, 149 for SGSN and 6 for
HLR).
SSP Service Switching Point. Intelligent Network Term for the
Class 4/5 Switch. The SSP has an open interface to the IN
for switching signaling, control, and handoff.
SSP Subsystem-prohibited. SSP is used for SCCP subsystem
management. A SSP message is sent to concerned
destinations to inform SCCP Management at those
destinations of the failure of a subsystem.
SSS Switching SubSystem. The SSC comprises the MSC and
the LRs.
STAN Statistical ANalysis (processor).
STAT STATistics.
stats Statistics.
STC System Timing Controller. The STC provides the timing
functions for the GPROC.
STMR Side Tone Masking rating. A rating, expressed in dB, based
on how a speaker perceives his own voice when speaking.
SUERM Signal Unit Error Rate Monitor. A link error rate monitor.
STP Signaling Transfer Point. A node in the SS7 telephone
network that routes messages between exchanges and
between exchanges and databases that hold subscriber
and routing information.
SU Signal Unit. A group of bits forming a separately
transferable entity used to convey information on a
signaling link.
SunOS Sun Microsystems UNIX Operating System. SunOS was
renamed Solaris.
Superframe 51 traffic/associated control multiframes or 26
broadcast/common control multiframes (period 6.12s).
Super user User account that can access all files, regardless of
protection settings, and control all user accounts.
SURF Sectored Universal Receiver Front-end (Used in
Horizonmacro).
Continued
68P02901W01-S 6-71
Jul 2008
T -TxBPF Chapter 6: Glossary of Technical Terms
SVC Switch Virtual Circuit. A temporary virtual circuit that is

set up and used only as long as data is being transmitted.
Once the communication between the two hosts is
complete, the SVC disappears. See also PVC.
SVM SerVice Manager. The SVM provides overall management
authority for all in-service service circuits.
SVN Software Version Number. The SVN allows the ME
manufacturer to identify different software versions of a
given type approved mobile. See also IMEI and IMEISV.
SW Software.
SWFM SoftWare Fault Management. Software faults are handled
through a SWFM facility which routes those events to the
OMC independently through the FCP.
SYM SYstem information Manager. The SYM builds and sends
GPRS system information messages over the BCCH.
sync synchronize/synchronization.
synchronization burst Period of RF carrier less than one timeslot whose
modulation bit stream carries information for the MS to
synchronize its frame to that of the received signal.
Synthesizer hopping Synthesizer hopping is a method of frequency hopping in
which the RCUs are re-tuned in real time, from frequency
to frequency.
SYS SYStem.
SYSGEN SYStem GENeration. The Motorola procedure for loading
a configuration database into a BTS.
T -TxBPF
T Timer.
T Transparent.
T Type only.
T1 Digital WAN carrier facility that transmits DS-1-formatted
data at 1544 kbps through the telephone-switching
network companies. T1 lines are widely used for
private networks as well as interconnections between an
Organization's PBX or LAN and the telco.
T43 Type 43 Interconnect Board. Provides interface to 12
unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for
2 Mbps circuits (Refer BIB).
TA Terminal Adaptor. A physical entity in the MS providing
terminal adaptation functions (see GSM 04.02).
TA See Timing Advance.
TAC Type Approval Code. Part of the IMEISV.
Continued
6-72 68P02901W01-S
Jul 2008
System Information: GSM Overview T -TxBPF
TACS Total Access Communication System. European analog

cellular system.
TAF Terminal Adaptation Function.
TATI Transmit Antenna Transceiver Interface. The TATI consists
of RF combining equipment, either Hybrid or Cavity
Combining. Refer CCB.
TAXI Transparent Asynchronous Transmitter/Receiver Interface
(physical layer). A 100 Mbps ATM transmission standard
defined by the ATM Forum.
TBD To Be Determined.
TBF Temporary Block Flow. MAC modes support the provision
of TBFs allowing the point-to-point transfer of signaling
and user data between the network and the MS.
TBR Technical Basis for Regulation. An ETSI document
containing technical requirements and procedures.
TBUS TDM Bus. A TBUS is a logical device made up of the TDM
backplane of a cage, the KSW devices managing the TDM
highway of the cage, and local and remote KSWX devices
(if they exist).
TC Transaction Capabilities. TC refers to a protocol structure
above the network layer interface (that is, the SCCP
service interface) up to the application layer including
common application service elements but not the specific
application service elements using them. TC is structured
as a Component sub-layer above a Transaction sub-layer.
TCAP Transaction Capabilities Application Part. The layer of the
SS7 protocol that is used to obtain Routing data for certain
services.
TCB TATI Control Board.
TCH Traffic CHannel. GSM logical channels which carry either
encoded speech or user data.
TCH/AFS Traffic CHannel. AMR Full rate Speech.
TCH/AHS Traffic CHannel. AMR Half rate Speech.
TCH/F A full rate TCH. See also Full Rate.
TCH/F2.4 A full rate TCH at 2.4 kbps.
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 kbps.
TCH/H4.8 A half rate TCH at 4.8 kbps.
TCH/HS A half rate Speech TCH.
TCI Transceiver Control Interface.
Continued
68P02901W01-S 6-73
Jul 2008
TCP Transmission Control Protocol. TCP is one of the main

protocols in TCP/IP networks. Whereas the IP protocol
deals only with packets, TCP enables two hosts to
establish a connection and exchange streams of data.
TCP guarantees delivery of data and also guarantees that
packets are delivered in the same order in which they were
sent. See also IP and TCP/IP.
TCP/IP Transmission Control Protocol/Internet Protocol. Two
interrelated protocols that are part of the Internet protocol
suite. TCP operates on the OSI Transport Layer and IP
operates on the OSI Network Layer. See also IP and TCP.
TC-TR Technical Committee Technical Report.
TCU Transceiver Control Unit.
TDF Twin Duplexed Filter. Used in M-Cellhorizon.
TDM Time Division Multiplexing. A type of multiplexing that
combines data streams by assigning each stream a
different time slot in a set. TDM repeatedly transmits a
fixed sequence of time slots over a single transmission
channel. Within T-Carrier systems, such as T-1 and T-3,
TDM combines PCM streams created for each conversation
or data stream.
TDMA Time Division Multiple Access. A technology for delivering
digital wireless service using TDM. TDMA works by
dividing a radio frequency into time slots and then
allocating slots to multiple calls. Thus, a single frequency
can support multiple, simultaneous data channels.
TDU TopCell Digital Unit. Part of the TopCell BTS hardware. A
TDU is capable of supporting six TRUs for supporting up
to six sectors.
TE Terminal Equipment. Equipment that provides the
functions necessary for the operation of the access
protocols by the user.
Tei Terminal endpoint identifier. A number that identifies a
specific connection endpoint within a service access point.
TEI Terminal Equipment Identity.
TEMP TEMPorary.
TEST TEST control processor.
TF Transmission Function. The TF provides layered protocol
software for handling payload information transfer and for
providing signaling communications between the control
function and external systems.
TFA TransFer Allowed. A SPC route management message used
to notify adjacent signaling points of an accessible route.
TFP TransFer Prohibited. A SPC route management message
used to notify adjacent signaling points of an inaccessible
route.
Continued
6-74 68P02901W01-S
Jul 2008
System Information: GSM Overview T -TxBPF
TFTP Trivial File Transfer Protocol. TFTP is a simple form of FTP.

It uses UDP and provides no security features. The servers
often use it to boot diskless workstations, X-terminals,
and routers.
TI Transaction Identifier.
Timeslot The multiplex subdivision in which voice and signaling bits
are sent over the air. Each RF carrier is divided into eight
timeslots. See also ARFCN.
Timing advance A signal sent by the BTS to the MS. It enables the MS
to advance the timing of its transmission to the BTS to
compensate for propagation delay.
TL See Transport Layer.
TLLI Temporary Logical Link Identifier.
TLV Type, Length and Value. An encoding element composed
of three fields: a type identifier, a length indicator, and
content octets.
TM Traffic Manager.
TMI TDM Modem Interface board. Provides analog interface
from IWF to modems for 16 circuits. Part of IWF.
TMM Traffic Metering and Measuring. TMM provides system
tools to be used by traffic engineering and switch
maintenance personnel to determine if the system is
operating correctly. TMM reports are provided for trunk
circuits, trunk groups, service circuits, call routing and
miscellaneous system data.
TMN Telecommunications Management Network. The
physical entities required to implement the
Network Management functionality for the PLMN.
Also, TMN was originated formally in 1988 under the
ITU-TS as a strategic goal to create or identify standard
interfaces that would allow a network to be managed
consistently across all network element suppliers. The
concept has led to a series of interrelated efforts at
developing standard ways to define and address network
elements. TMN uses the OSI Management Standards as its
framework. TMN applies to wireless communications and
cable TV as well as to private and public wired networks.
TMSI Temporary Mobile Subscriber Identity. A unique identity
temporarily allocated by the MSC to a visiting mobile
subscriber to process a call. is changed between calls and
even during a call, to preserve subscriber confidentiality.
TN Timeslot Number.
TOM Tunneling of Messages.
TON Type Of Number.
Traffic channels Channels which carry user's speech or data. See also TCH.
Traffic unit Equivalent to an erlang.
Continued
68P02901W01-S 6-75
Jul 2008
Training sequence Sequence of modulating bits employed to facilitate timing

recovery and channel equalization in the receiver.
Transport Layer See OSI RM. The Transport Layer responds to service
requests from the Session Layer and issues service
requests to the Network Layer. Its purpose is to provide
transparent transfer of data between end users, thus
relieving the upper layers from any concern with providing
reliable and cost-effective data transfer.
TRS Timeslot Resource Shifter. The TRS determines which
timeslots are active in a PRP board to perform a control of
the GPRS traffic.
TRAU Transcoder Rate Adaption Unit. TRAU converts the
encoded voice and rate adapted data into 64 kbps data
for the PSTN.
TRM Terrestrial Resource Management.
TRU TopCell Radio unit.
TRX Transceiver(s). A network component which can serve full
duplex communication on eight full-rate traffic channels
according to specification GSM 05.02. If Slow Frequency
Hopping (SFH) is not used, then the TRX serves the
communication on one RF carrier.
TS Technical Specification.
TS TeleService. Any service provided by a telecommunication
provider.
TS TimeSlot (see Timeslot).
TS1 Training Sequence 1.
TS2 Training Sequence 2.
TSA TimeSlot Acquisition.
TSA TimeSlot Assignment.
TSDA Transceiver Speech and Data Interface.
TSC Training Sequence Code. A training sequence is sent at
the center of a burst to help the receiver identify and
synchronize to the burst. The training sequence is a set
sequence of bits which is known by both the transmitter
and receiver. There are eight different TSCs numbered
0 to 7. Nearby cells operating with the same RF carrier
frequency use different TSCs to allow the receiver to
identify the correct signal.
TSI TimeSlot Interchange. The interchange of timeslots within
a TDM stream.
TSDI Transceiver Speech and Data Interface.
TSM Transceiver Station Manager.
TSN TRAU SyNc.
TSW Timeslot SWitch.
Continued
6-76 68P02901W01-S
Jul 2008
System Information: GSM Overview U - UUS
TTCN Tree and Tabular Combined Notation. TTCN is a

programming language endorsed by ISO that is used to
write test suites for telecommunications systems.
TTL Transistor to Transistor Logic. A common semiconductor
technology for building discrete digital logic integrated
circuits.
TTY TeleTYpe (refers to any terminal).
TU Traffic Unit.
TU3 Typical Urban with the MS travelling at 3 kph. Dynamic
can be measured. See also TU50, HT100, RA250
and,EQ50.
TU50 Typical Urban with the MS travelling at 50 kph. Dynamic
can be measured. See also TU3, HT100, RA250 and,
EQ50.
TUP Telephone User Part. TUP was an earlier implementation
of SS7 and generally does not allow for data type
applications.
TV Type and Value.
Two-way neighbor See Reciprocal neighbor.
Tx Transmit(ter).
TX Transmit window buffer.
TXF Transmit Function. Refer RTF.
TXPWR Transmit PoWeR. Tx power level in the
MS_TXPWR_REQUEST and MS_TXPWR_CONF
parameters.
TxBPF Transmit Bandpass Filter. Refer BPF.
U - UUS
UA Unnumbered Acknowledgment. A message sent from the

MS to the BSS to acknowledge release of radio resources
when a call is being cleared.
UCS2 Universal Coded Character Set 2. A code set containing all
of the characters commonly used in computer applications.
UDI Unrestricted Digital Information.
UDP User Datagram Protocol. UDP is a connectionless protocol
that, like TCP, runs on top of IP networks. Unlike TCP/IP,
UDP/IP provides very few error recovery services, offering
instead a direct way to send and receive datagrams over an
IP network. It is used primarily for broadcasting messages
over a network.
Continued
68P02901W01-S 6-77
Jul 2008
U - UUS Chapter 6: Glossary of Technical Terms
UDUB User Determined User Busy.

UFE Uplink Frame Error.
UHF Ultra High Frequency. The UHF range of the radio
spectrum is the band extending from 300 MHz to 3 GHz.
UI Unnumbered Information (Frame).
UIC Union International des Chemins de Fer. The UIC is the
worldwide organization for cooperation among railway
companies. Its activities encompass all fields related to the
development of rail transport.
UID User ID. Unique number used by the system to identify
the user.
UL Upload (of software or database from the NE to a BSS).
UL UpLink.
ULC UpLink Concatenator. The ULC concatenates RLC data
blocks into LLC frames.
Um Air interface.
UMTS Universal Mobile Telecommunication System. The
European implementation of the 3G wireless phone system.
UMTS, which is part of IMT-2000, provides service in the
2GHz band and offers global roaming and personalized
features. Designed as an evolutionary system for GSM
network operators, multimedia data rates up to 2 Mbps
are expected.
UNIX A multiuser, multitasking operating system that is widely
used as the master control program in workstations and
especially servers. AT developed UNIX and it was freely
distributed to government and academic institutions,
causing it to be ported to a wider variety of machine
families than any other operating system. As a result,
UNIX became synonymous with open systems.
UPCMI Uniform PCM Interface (13 bit). The UPCMI is introduced
for design purposes to separate the speech transcoder
impairments from the basic audio impairments of the MS.
UPD Up to Date.
Uplink Physical link from the MS towards the BTS (MS transmits,
BTS receives).
UPS Uninterruptable Power Supply. A device that is inserted
between a primary power source, such as a commercial
utility, and the primary power input of equipment to
be protected, for example, a computer system, for the
purpose of eliminating the effects of transient anomalies
or temporary outages. Backup power is used when the
electrical power fails or drops to an unacceptable voltage
level.
UPU User Part Unavailable.
Continued
6-78 68P02901W01-S
Jul 2008
System Information: GSM Overview V - VTX host
Useful part of burst That part of the burst used by the demodulator; differs
from the full burst because of the bit shift of the I and Q
parts of the GMSK signal.
USF Uplink State Flag.
USSD Unstructured Supplementary Service Data. The USSD
mechanism allows the MS user and a PLMN operator
defined application to communicate in a way which is
transparent to the MS and to intermediate network
entities. The mechanism allows development of PLMN
specific supplementary services.
UTRAN UMTS Radio Access Network.
UUS User-to-User Signaling supplementary service. The UUS
supplementary service allows a mobile subscriber to
send/receive a limited amount of information to/from
another PLMN or ISDN subscriber over the signaling
channel in association with a call to the other subscriber.
V - VTX host
V Value only.
VA Viterbi Algorithm (used in channel equalizers). An
algorithm to compute the optimal (most likely) state
sequence in a model given a sequence of observed outputs.
VAD Voice Activity Detection. A process used to identify
presence or absence of speech data bits. VAD is used with
DTX.
VAP Videotext Access Point.
VBS Voice Broadcast Service. VBS allows the distribution of
speech (or other signals which can be transmitted through
the speech codec), generated by a service subscriber, into
a predefined geographical area to all or a group of service
subscribers located in this area.
VC See Virtual Circuit.
VCO Voltage Controlled Oscillator. An oscillator whose clock
frequency is determined by the magnitude of the voltage
presented at its input. The frequency changes when the
voltage changes.
VCXO Voltage Controlled Crystal Oscillator.
VDU Visual Display Unit. A device used for the real time
temporary display of computer output data. Monitor.
VersaTRAU Allows both voice and GPRS/EGPRS frames to be combined
into one large frame to reduces backhaul. See TRAU
(Transcoder Rate Adaption Unit).
Continued
68P02901W01-S 6-79
Jul 2008
V - VTX host Chapter 6: Glossary of Technical Terms
Videotext The Videotext service is an interactive service, that

with proper access points and standardized procedures,
provides the access to data base information stored in
host computers external to the PLMN, through public
telecommunication networks.
Virtual Circuit A connection between two devices, that functions as though
it is a direct connection, even though it can physically be
circuitous. The term is used most frequently to describe
connections between two hosts in a packet-switching
network.
VLR Visitor Location Register. A GSM network element which
provides a temporary register for subscriber information
for a visiting subscriber. Often a part of the MSC.
VLSI Very Large Scale Integration (in ICs). The process
of placing between 100,000 and 1,000,000 electronic
components on a single chip.
VMSC Visited MSC. (Recommendation not to be used).
vocoder Abbreviation for voice-coder. A device that usually consists
of a speech analyzer, which converts analog speech
waveforms into narrow band digital signals, and a speech
synthesizer, which converts the digital signals into artificial
speech sounds.
VOX Voice Operated Transmission. An acoustoelectric

transducer and a keying relay connected so that the keying
relay is actuated when sound, or voice energy above
a certain threshold is sensed by the transducer. A vox
is used to eliminate the need for push-to-talk operation
of a transmitter by using voice energy to turn on the
transmitter.
VPLMN Visited PLMN.
VSC Videotext Service Center.
V(SD) Send state variable.
VSP Vehicular Speaker Phone.
VSWR Voltage Standing Wave Ratio. In a transmission line, the
ratio of maximum to minimum voltage in a standing wave
pattern. Note: The VSWR is a measure of impedance
mismatch between the transmission line and its load.
The higher the VSWR, the greater the mismatch. The
minimum VSWR, that is, that which corresponds to a
perfect impedance match, is unity.
VTX host The components dedicated to videotext service.
6-80 68P02901W01-S
Jul 2008
System Information: GSM Overview W - WWW
W - WWW
WAN Wide Area Network. A physical or logical network that

provides data communications to a larger number of
independent users than are usually served by a LAN and is
usually spread over a larger geographic area than that of a
LAN. WANs may include physical networks, such as ISDN
networks and X.25 networks.
WPA Wrong Password Attempts (counter). Some supplementary
services have the option of the subscriber using a
password. If a password check is done with an incorrect
password, the WPA is incremented by one. If a password
check is passed, the WPA is set to zero. If the WPA exceeds
the value three, the subscriber has to register a new
password with the service provider.
WS WorkStation. The remote device through which Operation
and Maintenance personnel execute input and output
transactions for network management purposes.
WSF WorkStation Function block.
WWW World Wide Web. An international, virtual-network-based
information service composed of Internet host computers
that provide online information in a specific hypertext
format. WWW servers provide hypertext mark-up language
(HTML) formatted documents using the hypertext transfer
protocol, HTTP. Information on the WWW is accessed with
a hypertext browser.
X - X Window
X.25 X.25, adopted as a standard by the CCITT, is a commonly

used protocol for public packet-switched networks
(PSPDNS). The X.25 protocol allows computers on different
public networks to communicate through an intermediary
computer at the network layer level. The protocol
corresponds closely to the data-link and physical-layer
protocols defined in the OSI communication model.
X.25 link A communications link which conforms to X.25
specifications and uses X.25 protocol (NE to OMC links).
XBL Transcoder to BSS Link. The carrier communications link
between the Transcoder (XCDR) and the BSS.
XCB Transceiver Control Board. Part of the Transceiver.
XCDR Full-rate Transcoder. The XCDR is the digital signal
processing equipment required to perform GSM-defined
speech encoding and decoding. In terms of data
transmission, the speech transcoder interfaces the 64 kbps
PCM in the land network to the 13 kbps vocoder format
used on the Air Interface. See also RXCDR.
Continued
68P02901W01-S 6-81
Jul 2008
ZC Chapter 6: Glossary of Technical Terms
XCDR board The circuit board required to perform speech transcoding

at the BSS or (R)XCDR). Also known as the MSI (XCDR)
board. Interchangeable with the GDP board.
XFER Transfer.
XID eXchange IDentifier.
xterm X terminal window. A terminal emulator program for
the X Window System. A user can have many different
invocations of xterm running at once on the same display,
each of which provides independent input and output for
the process running in it (normally a shell).
X Window A specification for device-independent windowing
operations on bitmap display devices.
ZC
ZC Zone Code. Part of the RSZI. The ZC identifies a regional

subscription zone as a pattern of allowed and not allowed
location areas uniquely within a PLMN.
6-82 68P02901W01-S
Jul 2008
Index
Index

120K TCH OMC Capacity Expansion . . 5-65 28398 . . . . . . . . . . . . . . . . . . . 4-129

2 Mbips link. . . . . . . . . . . . . . . . 1-53 3GPP Release 6 Performance Management IRP
2-site repeat pattern . . . . . . . . . . . 1-50 2G. . . . . . . . . . . . . . . . . . . . . 5-73
25663 . . . . . . . . . . . . . . . . . . . 5-71 4 to 2-wire hybrid . . . . . . . . . . . . . 1-50
27508 . . . . . . . . . . . . . . . . . . . 5-71 64 kbps link . . . . . . . . . . . . . . . . 1-41
27751/27752 . . . . . . . . . . . . . . . 5-73
Access Grant CHannel (AGCH) . . . . . . 1-42 alarms icon . . . . . . . . . . . . . . . . 3-66

Adaptive Multi-Rate . . . . . . . . . . . . 4-87 alarms severity
add and delete option . . . . . . . . . . . 1-40 icon colour . . . . . . . . . . . . . . . 3-68
Addition of new PCU hardware to increase GPRS allocating handover numbers
capacity . . . . . . . . . . . . . . . . . . 4-128 overview . . . . . . . . . . . . . . . . 1-32
Advanced load handover management . . 1-85 allocating TMSI numbers
Advanced load management for EGSM carriers overview . . . . . . . . . . . . . . . . 1-32
Advanced load handover management. . 4-71 architecture
air interface . . . . . . . . . . . . . . . . . 2-2 network
control . . . . . . . . . . . . . . . . . 2-23 hierarchical . . . . . . . . . . . . . . 1-47
radio channel . . . . . . . . . . . . . . 1-57 PCU . . . . . . . . . . . . . . . . . . . 2-54
air interface (BSS to MS) . . . . . . . . . 1-41 associated control channel ID . . . . . . . 1-48
alarm associated control channels
reporting . . . . . . . . . . . . . . . . 3-61 Associated Control Channels . . . . . . 1-43
alarm state . . . . . . . . . . . . . . . . 3-59 audio quality . . . . . . . . . . . . . . . 1-18
alarms AUthentication Centre
colours . . . . . . . . . . . . . . . 3-61, 3-68 Authentication centre . . . . . . . . . . 1-30
disk usage. . . . . . . . . . . . . . . . 3-83 authentication key . . . . . . . . . . . . 1-31
background maps . . . . . . . . . . . . . 3-61 broadcast control channels (contd.)

Base Station System (BSS) FCCH . . . . . . . . . . . . . . . . . . 1-42
configurations. . . . . . . . . . . . . . 1-38 SCH . . . . . . . . . . . . . . . . . . . 1-42
overview . . . . . . . . . . . . . . . . 1-38 Broadcast Control Channels (BCCH) . . . 1-42
software functions . . . . . . . . . . . 1-40 BSC
BCCH . . . . . . . . . . . . . . . . . . . 3-22 interaction with MSC . . . . . . . . . . . 2-5
Bill Of Materials interfaces . . . . . . . . . . . . . . . . 1-59
BOM . . . . . . . . . . . . . . . . . . 3-36 to BTS . . . . . . . . . . . . . . . . 2-20
billing centre . . . . . . . . . . . . . . . 1-44 to MSC . . . . . . . . . . . . . . . . 2-20
BOM purpose and functions . . . . . . . . . . 2-5
bill of materials . . . . . . . . . . . . . 3-36 redundancy . . . . . . . . . . . . . . . 2-32
bridge site configuration . . . . . . . . . . . . 2-12
PCI to PCI. . . . . . . . . . . . . . . . 2-55 BSC capacity
broadcast control channels overview . . . . . . . . . . . . . . . . . 2-6
68P02901W01-S IX-83
Jul 2008
Index
BSC Overload Protection . . . . . . . . . 4-115 BSS software features (contd.)

BSC Reset Management . . . . . . . . . 4-98 code corruption immune design. . . . . 4-47
BSP CPU utilization reduction for higher call CS3, CS4 and 32 kbits/s TRAU . . . . . 4-53
handling capacity . . . . . . . . . . . . . 4-127 dynamic allocation of RXCDR-BSC
BSS . . . . . . . . . . . . . . . . . . 2-3, 3-17 circuits . . . . . . . . . . . . . . . . . 4-46
capacity . . . . . . . . . . . . . . . . . 2-11 Enhanced 2G-3G handover . . . . . . . 4-105
fault management. . . . . . . . . . . . 2-31 enhanced BSC capacity phase 2 . . . . 4-66
handover enhanced MMI link device warnings . . 4-51
overview . . . . . . . . . . . . . . . 2-23 Enhanced Multi Level Precedence and
links Preemption . . . . . . . . . . . . . . . 4-109
overview . . . . . . . . . . . . . . . . 2-2 enhanced power outage recovery . . . . 4-48
network elements enhanced XBL. . . . . . . . . . . . . . 4-47
overview . . . . . . . . . . . . . . . . 2-3 Fast Call Setup . . . . . . . . . . . . . 4-110
network topology . . . . . . . . . . . . 2-16 GPROC fast reset . . . . . . . . . . . . 4-54
daisy chain with fork and return loop to GPROC function pre-emption . . . . . . 4-50
BSC . . . . . . . . . . . . . . . . . . 2-18 GPRS PCU recovery on last GSL fail-
daisy chain with fork and return loop to ure . . . . . . . . . . . . . . . . . . . 4-62
chain . . . . . . . . . . . . . . . . . 2-17 GPRS R4 Compliance . . . . . . . . . . 4-109
drop and insert . . . . . . . . . . . . 2-18 GPRS resources (PDTCH) configured . . 4-96
open ended daisy chain . . . . . . . . 2-17 GPRS Statistics and enhancements . . . 4-104
overview . . . . . . . . . . . . . . . 2-16 GSM half rate . . . . . . . . . . . . . . 4-94
star (spoke) . . . . . . . . . . . . . . 2-17 handover parameter . . . . . . . . . . 4-49
operation and maintenance . . . . . . . . 3-5 Horizonmicro2/Horizoncompact2 generic BTS
overview . . . . . . . . . . . . . . . . . 2-2 software . . . . . . . . . . . . . . . . 4-47
purpose and functions . . . . . . . . . . 2-2 improved MPROC software failures detection
redundancy . . . . . . . . . . . . . . . 2-31 and recovery . . . . . . . . . . . . . . 4-67
site configurations improved MTL load balancing. . . . . . 4-48
BSC . . . . . . . . . . . . . . . . . . 2-12 Increased SDCCH . . . . . . . . . . . . 4-111
BTS . . . . . . . . . . . . . . . . . . 2-12 Intelligent Multi Layer Resource Manage-
flexibility . . . . . . . . . . . . . . . 2-10 ment . . . . . . . . . . . . . . . . . . 4-100
introduction . . . . . . . . . . . . . . 2-10 Inter Radio Access Technology (RAT) 2-G to 3-G
BSS interfaces . . . . . . . . . . . . . . 1-41 handover . . . . . . . . . . . . . . . . 4-67
A interface . . . . . . . . . . . . . . . 1-41 link utilization improvements . . . . . . 4-70
Abis interface . . . . . . . . . . . . . . 1-41 Multiple GPRS carriers per Cell. . . . . 4-58
Lb interface . . . . . . . . . . . . . . . 2-22 Network Assisted Cell Change . . . . . 4-104
BSS LAN Packing . . . . . . . . . . . . . 4-126 Network controlled (NC1 and NC2) cell
BSS mobile application part. . . . . . . . 1-41 reselection . . . . . . . . . . . . . . . 4-62
BSS object . . . . . . . . . . . . . . . . 3-75 New GPRS alarms. . . . . . . . . . . . 4-103
BSS software feature optimized power control . . . . . . . . 4-49
Enhanced GDP provisioning. . . . . . . 4-59 Out_inter_bss_ho statistical counter . . 4-97
BSS software features . . . . . . . . . . . 2-6, parallel cage enable. . . . . . . . . . . 4-51
2-11, 3-17, 4-76, 4-82 per neighbour area for adaptive han-
1900 MHz Horizonmacro . . . . . . . . 4-54 dovers. . . . . . . . . . . . . . . . . . 4-49
3646 . . . . . . . . . . . . . . . . . . 4-57 propogate TSC changes to all times-
850 MHz frequency range . . . . . . . 4-54 lots . . . . . . . . . . . . . . . . . . . 4-48
advanced load management for EGSM receive antenna VSWR and radio loopback
carriers . . . . . . . . . . . . . . . . . 4-71 test . . . . . . . . . . . . . . . . . . . 4-46
basic MPROC redundancy . . . . . . . 4-65 Release 1.1.1.0 . . . . . . . . . . . . . . 4-3
BSC Reset Management . . . . . . . . 4-98 Release 1.1.2.0 . . . . . . . . . . . . . . 4-6
BSS overload protection . . . . . . . . 4-45 Release 1.1.2.1 . . . . . . . . . . . . . . 4-8
BSS processing of suspend message . . 4-52 Release 1.1.2.2 . . . . . . . . . . . . . . 4-9
BSS support for full Cell ID . . . . . . . 4-98 Release 1.1.2.3 . . . . . . . . . . . . . 4-10
BTS concentration call priority han- Release 1.2.0.0 . . . . . . . . . . . . . 4-11
dling . . . . . . . . . . . . . . . . . . 4-50 Release 1.2.0.3 . . . . . . . . . . . . . 4-14
BTS concentration resource optimization for Release 1.2.2.0 . . . . . . . . . . . . . 4-15
handovers . . . . . . . . . . . . . . . . 4-49 Release 1.2.2.2 . . . . . . . . . . . . . 4-17
call downgrade on CIC mismatch . . . . 4-60 Release 1.2.2.3 . . . . . . . . . . . . . 4-18
Clean install (E3x00) . . . . . . . . . . 4-68 Release 1.2.3.0 . . . . . . . . . . . . . 4-19
IX-84 68P02901W01-S
Jul 2008
Index
BSS software features (contd.) BSS software features (contd.)

Release 1.3.0.x . . . . . . . . . . . . . 4-22 Support for GPRS Trace . . . . . . . . 4-101
Release 1.4.0.0 . . . . . . . . . . . . . 4-25 Support for Half Rate on GDP2 . . . . . 4-110
Release 1.4.0.1 . . . . . . . . . . . . . 4-26 Support for Horizon II Mini . . . . . . . 4-108
Release 1.4.0.6 . . . . . . . . . . . . . 4-28 support for the MTL stat . . . . . . . . 4-50
Release 1.4.0.7 . . . . . . . . . . . . . 4-30 Support of QoS Release 4 . . . . . . . . 4-107
Release 1.4.1.1 . . . . . . . . . . . . . 4-31 temporary block flow . . . . . . . . . . 4-68
Release GSR2 . . . . . . . . . . . . . . 4-34 unequip of TCU/CTU cabinets. . . . . . 4-54
Release GSR3 . . . . . . . . . . . . . . 4-36 VersaTRAU . . . . . . . . . . . . . . . 4-106
Release GSR4 . . . . . . . . . . . . . . 4-40 BSS support for full Cell ID . . . . . . . . 4-98
Release GSR5 . . . . . . . . . . . . . . 4-44 BSS User Security Management . . . . . 5-71
Release GSR5.1 . . . . . . . . . . . . . 4-52 BSSAP . . . . . . . . . . . . . . . . . . 1-41
Release GSR6 . . . . . . . . . . . . . . 4-56 BSSMAP . . . . . . . . . . . . . . . . . 1-41
Release GSR6 (HII) . . . . . . . . . . . 4-74 BTS
Release GSR7 . . . . . . . . . . . . . . 4-87 interfaces . . . . . . . . . . . . . . . . 1-60
Release GSR8 . . . . . . . . . . . . . . 4-79 to BSC . . . . . . . . . . . . . . . . 2-20
RSL Congestion Control. . . . . . . . . 4-111 to MS . . . . . . . . . . . . . . . . . 2-21
single BCCH for dual band cells . . . . 4-48 purpose and functions . . . . . . . . . . 2-7
SMS CB upgrade . . . . . . . . . . . . 4-45 radio types . . . . . . . . . . . . . . . . 2-7
Stop BTS transmission after the last RSL RCU. . . . . . . . . . . . . . . . . . . 3-20
fails . . . . . . . . . . . . . . . . . . . 4-96 redundancy . . . . . . . . . . . . . . . 2-32
support for E1 conversion. . . . . . . . 4-48 site configuration
support for frame erasure rate statis- overview . . . . . . . . . . . . . . . 2-12
tic . . . . . . . . . . . . . . . . . . . . 4-50
C7. . . . . . . . . . . . . . . . . . . 1-25, 1-67 CM MIB (contd.)

call control functions automatically created objects (contd.)
overview . . . . . . . . . . . . . . . . 1-26 NESoftware . . . . . . . . . . . . . . 3-80
call handling source. . . . . . . . . . . . . . . . . 3-80
overview . . . . . . . . . . . . . . . . 1-32 SWInventory . . . . . . . . . . . . . 3-80
call management TRX . . . . . . . . . . . . . . . . . . 3-80
functional layering . . . . . . . . . . . 1-55 definition . . . . . . . . . . . . . . . . 3-69
capacity co-channel interference . . . . . . . . . . 1-50
BSS . . . . . . . . . . . . . . . . . . . 2-11 coding schemes
GSM system software features . . . . . . . . . . . . 2-45
overview . . . . . . . . . . . . . . . 1-49 common control channels . . . . . . . . . 1-42
CBC . . . . . . . . . . . . . . . . . . . . 1-45 AGCH . . . . . . . . . . . . . . . . . . 1-42
CBL . . . . . . . . . . . . . . . . . . . . 3-28 CBCH . . . . . . . . . . . . . . . . . . 1-42
Cell Broadcast Centre (CBC) . . . . . . . 1-45 PCH . . . . . . . . . . . . . . . . . . . 1-42
Cell Broadcast CHannel (CBCH) . . . . . 1-42 RACH . . . . . . . . . . . . . . . . . . 1-42
cell configuration CommsLink object . . . . . . . . . . . . 3-75
logical devices . . . . . . . . . . . . . 3-23 communication link . . . . . . . . . . . . . 2-2
channels Compress all BTS objects at the BSC
logical feature . . . . . . . . . . . . . . . . . 4-73
overview . . . . . . . . . . . . . . . 1-42 confidentiality
logical types signalling information. . . . . . . . . . 1-19
overview . . . . . . . . . . . . . . . 1-42 user data . . . . . . . . . . . . . . . . 1-19
physical configuration mgt . . . . . . . . . . . . . 3-43
overview . . . . . . . . . . . . . . . 1-42 configuration objects . . . . . . . . . . . 3-73
chassis configurations
PCU . . . . . . . . . . . . . . . . . . . 2-58 BSS site
CM MIB . . . . . . . . . . . . . . . . . . 3-57 introduction . . . . . . . . . . . . . . 2-10
automatically created objects containment
MMS . . . . . . . . . . . . . . . . . 3-80 managed objects . . . . . . . . . . . . 3-19
68P02901W01-S IX-85
Jul 2008
Index
control controlling LAIs

functions . . . . . . . . . . . . . . . . 2-64 overview . . . . . . . . . . . . . . . . 1-32
control channels controlling MSRNs
associated control channels . . . . . . . 1-42 overview . . . . . . . . . . . . . . . . 1-32
broadcast control channels . . . . . . . 1-42 CTU2-D . . . . . . . . . . . . . . . . . . 4-130
common control channels . . . . . . . . 1-42
dedicated control channels . . . . . . . 1-42
D channel . . . . . . . . . . . . . . . . . 1-19 device mgt . . . . . . . . . . . . . . . . 3-43

daisy chain digital communication . . . . . . . . 1-18, 1-49
open ended . . . . . . . . . . . . . . . 2-17 digital networks
with fork and return loop to BSC . . . . 2-18 overview . . . . . . . . . . . . . . . . 1-17
with fork and return loop to chain . . . 2-17 Digital Signal Processor (DSP) . . . . . . 1-18
data channels . . . . . . . . . . . . . . . 1-43 digital switching matrix
data communication overview . . . . . . . . . . . . . . . . . 2-5
overview . . . . . . . . . . . . . . . . 1-19 Direct Transfer Application Part (DTAP). . 1-41
database schema discontinuous reception . . . . . . . . . . 2-25
definition . . . . . . . . . . . . . . . . 3-47 discontinuous transmission . . . . . . . . 2-25
size . . . . . . . . . . . . . . . . . . . 3-47 Doc = TOC-INDEX-LINK
DBMS . . . . . . . . . . . . . . . . . . . 3-42 Glossary of technical terms . . . . . . . . 6-2
DCS1800 downlink . . . . . . . . . . . . . . . . . 3-23
radio types . . . . . . . . . . . . . . . . 2-7 DPROC . . . . . . . . . . . . . . . . . . 2-55
DCS1800 frequencies and channels (PICP) . . . . . . . . . . . . . . . . . . 2-55
DCS1800 channels . . . . . . . . . . . 1-89 (PRP) . . . . . . . . . . . . . . . . . . 2-55
DCS1800 frequencies . . . . . . . . . . 1-88 DRI . . . . . . . . . . . . . . . . . . 3-20, 3-22
dedicated control channels dropped calls . . . . . . . . . . . . . . . 1-18
SDCCH . . . . . . . . . . . . . . . . . 1-43 DTAP . . . . . . . . . . . . . . . . . . . 1-41
definitions dynamic adaptation of coding schemes
E1 link . . . . . . . . . . . . . . . . . 1-53 software features . . . . . . . . . . . . 2-47
E1 enhanced GPRS one phase access

PMC . . . . . . . . . . . . . . . . . . 2-58 software features . . . . . . . . . . . . 2-47
E1 link Enhanced GPRS One Phase Access
definition . . . . . . . . . . . . . . . . 1-53 feature . . . . . . . . . . . . . . . . . 4-72
EGPRS . . . . . . . . . . . . . . . . . . 4-92 Enhanced Multi Level Precedence and
EGSM to EGSM handovers . . . . . . . . 1-85 Preemption . . . . . . . . . . . . . . . . 4-109
EGSM900 environment
radio types . . . . . . . . . . . . . . . . 2-7 PCU . . . . . . . . . . . . . . . . . . . 2-41
EIR . . . . . . . . . . . . . . . . . . 1-3, 1-15 equipment identity
electrical interfaces mobile
standardized international . . . . . . . . . . . . . 1-15
overview . . . . . . . . . . . . . . . 1-47 equipment identity register
EM proxy process . . . . . . . . . . . . . 3-57 overview . . . . . . . . . . . . . . . . 1-28
EM sub schema . . . . . . . . . . . . . . 3-47 Equipment Identity Register (EIR) . . . . 1-15
Emergency caller location ethernet. . . . . . . . . . . . . . . . . . 3-37
LCS . . . . . . . . . . . . . . . . . 1-51, 4-64 ethernet support . . . . . . . . . . . . . 3-45
emergency calls event interface . . . . . . . . . . . . . . 3-43
overview . . . . . . . . . . . . . . . . 1-26 event/alarm mgt . . . . . . . . . . . . . 3-43
Enhanced 2G-3G handover . . . . . . . . 4-105 expert front panel . . . . . . . . . . . . . 3-12
enhanced frequency hopping . . . . . . . . 1-6 extrapolation algorithm . . . . . . . . . . 1-18
IX-86 68P02901W01-S
Jul 2008
Index
Fast Associated Control CHannel feature (contd.)

(FACCH) . . . . . . . . . . . . . . . . . 1-43 30830 . . . . . . . . . . . . . . . . . . 4-113
Fast Call Setup . . . . . . . . . . . . . . 4-110 31400 . . . . . . . . . . . . . . . . . . 4-112
fault management 31565 . . . . . . . . . . . . . . . . . . 4-134
BSS . . . . . . . . . . . . . . . . . . . 2-31 32173 . . . . . . . . . . . . . . . . . . 4-113
fault tolerance 32340 . . . . . . . . . . . . . . . . . . 4-113
Motorola GSM . . . . . . . . . . . . . . 1-6 33397 . . . . . . . . . . . . . . . . . . 4-134
PCU . . . . . . . . . . . . . . . . . . . 2-59 34144 . . . . . . . . . . . . . . . . . . 4-134
feature . . . . . . . . . . . . . . . . . . 4-113 34145 . . . . . . . . . . . . . . . . . . 4-134
22168 . . . . . . . . . . . . . . . . . . 4-112 Feature
22169 . . . . . . . . . . . . . . . . . . 4-112 22280
22266 . . . . . . . . . . . . . . 4-112, 4-115 Barred Cell . . . . . . . . . . . . . . 5-64
22415 . . . . . . . . . . . . . . 4-112, 4-115 Feature Capacity Licensing and Audit. . . 3-87,
22904 . . . . . . . . . . . . . . . . . . 5-64 5-70
23292 . . . . . . . . . . . . . . . . . . 4-134 features
23306 . . . . . . . . . . . . . . 4-112, 4-115 PCU . . . . . . . . . . . . . . . . . . . 2-42
23370 . . . . . . . . . . . . . . . . . . 5-64 features summary
23376 . . . . . . . . . . . . . . . . . . 5-64 PCU . . . . . . . . . . . . . . . . . . . 2-42
24452 . . . . . . . . . . . . . . . . . . 5-64 frequency
25002 . . . . . . . . . . . . . . . . . . 4-112 reuse
25423 . . . . . . . . . . . . . . 4-112, 4-117 2-site 6-sector . . . . . . . . . . . . . 2-29
25424 . . . . . . . . . . . . . . 4-112, 4-118 3-site 3-sector . . . . . . . . . . . . . 2-28
25867 . . . . . . . . . . . . . . 4-112, 4-118 3-site 6-sector . . . . . . . . . . . . . 2-29
26481 . . . . . . . . . . . . . . 4-112, 4-119 4-site . . . . . . . . . . . . . . . . . 2-29
26740 . . . . . . . . . . . . . . 4-112, 4-120 9-site . . . . . . . . . . . . . . . . . 2-27
26881 . . . . . . . . . . . . . . . . . . 4-134 introduction . . . . . . . . . . . . . . 2-27
27236 . . . . . . . . . . . . . . . . . . 4-112 synchronization . . . . . . . . . . . . . 2-26
27703A . . . . . . . . . . 4-112, 4-122, 4-134 Frequency Correction CHannel (FCCH). . 1-42
27717 . . . . . . . . . . . . . . 4-112, 4-123 frequency hopping of PDCH
27955A . . . . . . . . . . . . . . . . . 4-112 software features . . . . . . . . . . . . 2-48
2795A . . . . . . . . . . . . . . . 2-40, 4-124 frequency reuse
27962 . . . . . . . . . . . . . . 4-112, 4-125 overview . . . . . . . . . . . . . . . . 1-17
28000 . . . . . . . . . . . . . . 4-112, 4-126 functional layering . . . . . . . . . . . . 1-55
28333 . . . . . . . . . . . . . . 4-112, 4-126 functions
28337 . . . . . . . . . . . . . . 4-112, 4-127 control . . . . . . . . . . . . . . . . . 2-64
28340 . . . . . . . . . . . . . . 4-112, 4-127 MSC
28351 . . . . . . . 2-54 to 2-55, 4-112, 4-128 overview . . . . . . . . . . . . . . . 1-23
28398 . . . . . . . . . . . . . . . . . . 4-112 PCU system . . . . . . . . . . . . . . . 2-64
28938 . . . . . . . . . . . . . . 4-112, 4-129 PSP . . . . . . . . . . . . . . . . . . . 2-54
29241 . . . . . . . . . . . . . . 4-112, 4-119 radio . . . . . . . . . . . . . . . . . . 2-64
30365 . . . . . . . . . . . . . . 4-112, 4-119 SGSN . . . . . . . . . . . . . . . . . . 2-64
30828 . . . . . . . . . . . . . . 4-112, 4-130
Gaussian Minimum Shift Keying Glossary of technical terms (contd.)

(GMSK) . . . . . . . . . . . . . . . . 1-41, 1-46 A Interface - AUTO . . . . . . . . . . . . 6-2
Gb B Interface - Byte . . . . . . . . . . . . . 6-6
interface . . . . . . . . . . . . . . . . 2-63 C - CW . . . . . . . . . . . . . . . . . 6-10
processes . . . . . . . . . . . . . . . . 2-65 D Interface - DYNET . . . . . . . . . . 6-18
Gb interface E - EXEC . . . . . . . . . . . . . . . . 6-23
software features . . . . . . . . . . . . 2-49 F Interface - Full Rate. . . . . . . . . . 6-26
Glossary of technical terms G Interface - GWY . . . . . . . . . . . . 6-30
68P02901W01-S IX-87
Jul 2008
Index
Glossary of technical terms (contd.) GSM (contd.)

H Interface - Hyperframe . . . . . . . . 6-32 interfaces
I - IWU . . . . . . . . . . . . . . . . . 6-34 overview . . . . . . . . . . . . . . . 1-47
k - KW . . . . . . . . . . . . . . . . . . 6-38 network . . . . . . . . . . . . . . . . . 3-16
L1 - LV . . . . . . . . . . . . . . . . . 6-38 network architecture . . . . . . . . . . 2-36
M - MUX . . . . . . . . . . . . . . . . 6-41 radio channel . . . . . . . . . . . . . . 1-41
N/W - nW . . . . . . . . . . . . . . . . 6-47 radio interface
O - Overlap . . . . . . . . . . . . . . . 6-50 noise robustness . . . . . . . . . . . 1-51
PA - PXPDN . . . . . . . . . . . . . . . 6-52 sub-systems . . . . . . . . . . . . . . . 1-44
QA - Quiesent mode . . . . . . . . . . . 6-58 GSM frequencies and channels . . . . . . 1-69
R - RXU . . . . . . . . . . . . . . . . . 6-59 EGSM frequencies . . . . . . . . . . . 1-84
S7 - SYSGEN . . . . . . . . . . . . . . 6-64 ESGM channels . . . . . . . . . . . . . 1-85
T - TxBPF . . . . . . . . . . . . . . . . 6-72 GSM850 channels. . . . . . . . . . . . 1-70
U - UUS . . . . . . . . . . . . . . . . . 6-77 GSM850 frequencies . . . . . . . . . . 1-69
V - VTX host . . . . . . . . . . . . . . . 6-79 GSM900 channels. . . . . . . . . . . . 1-78
W - WWW . . . . . . . . . . . . . . . . 6-81 GSM900 frequencies . . . . . . . . . . 1-77
X - X Window . . . . . . . . . . . . . . 6-81 GSM half rate . . . . . . . . . . . . . 4-94, 5-63
ZC . . . . . . . . . . . . . . . . . . . 6-82 GSM900
GMSK . . . . . . . . . . . . . . . . . 1-41, 1-46 radio types . . . . . . . . . . . . . . . . 2-7
GPROC2 . . . . . . . . . . . . . . . . . 3-17 GSN
GPRS network architecture . . . . . . . . . . 2-36
network architecture . . . . . . . . . . 2-36 overview of complex . . . . . . . . . . 2-34
overview . . . . . . . . . . . . . . . . 2-33 GUI
GPRS PBCCH/PCCCH support . . . . . . 4-91 command line interface . . . . . . . . . 3-15
GPRS R4 Compliance . . . . . . . . . . . 4-109 configurations. . . . . . . . . . . . . . 3-49
GPRS radio channel allocation GUI front panel . . . . . . . . . . . . . 3-12
software features . . . . . . . . . . . . 2-43 processors . . . . . . . . . . . . . . . 3-49
GPRS resources (PDTCH) configured . . . 4-96 GUI client . . . . . . . . . . . . . . . . . 3-54
GPRS Statistics and enhancements . . . . 4-104 GUI server
graphic objects GUI client . . . . . . . . . . . . . . . . 3-58
maps . . . . . . . . . . . . . . . . . . 3-71 GUI workstation
GSM disk size. . . . . . . . . . . . . . . . . 3-54
handover . . . . . . . . . . . . . . . . . 1-48 HLR . . . . . . . . . . . . . . . . . . 1-3, 1-16

overview . . . . . . . . . . . . . . . . 2-23 HLR data . . . . . . . . . . . . . . . . . 1-30
handover control . . . . . . . . . . . . . 3-23 HLR master database
handportable . . . . . . . . . . . . . . . 1-19 overview . . . . . . . . . . . . . . . . 1-30
hardware devices . . . . . . . . . . . . . 3-76 home location register
hierarchical network architecture. . . . . 1-47 overview . . . . . . . . . . . . . . . . 1-29
hierarchy HSP MTL . . . . . . . . . . . . . . . . . 4-127
network . . . . . . . . . . . . . . . . . . 3-5
IMEI . . . . . . . . . . . . . . . . . . . 1-15 increased capacity

Implementation of Secure Services on Solaris overview . . . . . . . . . . . . . . . . 1-17
based O&M products . . . . . . . . . . . 5-71 Increased Network Capacity . . . . . . . 4-129
IMSI . . . . . . . . . . . . . . . . . . . 1-15 Increased SDCCH . . . . . . . . . . . . . 4-111
In Service (INS) state . . . . . . . . . . . 3-59 information flow
Increase the PCU database capacity . . . 4-115 OMC and NEs . . . . . . . . . . . . . . 3-34
Increase the Throughput of PRP with the INFORMIX . . . . . . . . . . . . . . . . 3-48
PCU . . . . . . . . . . . . . . . . . . . . 4-126 infrastructure . . . . . . . . . . . . . . . 1-50
IX-88 68P02901W01-S
Jul 2008
Index
Intelligent Audit. . . . . . . . . . . 5-64 to 5-65 interfaces (contd.)

Intelligent Multi Layer Resource Manage- summary . . . . . . . . . . . . . . . . 1-58
ment . . . . . . . . . . . . . . . . . . . 4-100 interference
inter-MSC handovers . . . . . . . . . . . 1-28 co-channel . . . . . . . . . . . . . . . 1-50
interfaces co-channel and adjacent channel . . . . 1-18,
BSC to BTS . . . . . . . . . . . . . . . 2-20 1-49
BTS to MS . . . . . . . . . . . . . 1-60, 2-21 International Mobile station Equipment Identity
Gb. . . . . . . . . . . . . . . . . . . . 2-63 (IMEI) . . . . . . . . . . . . . . . . . . . 1-15
GSM International Mobile Subscriber Identity
overview . . . . . . . . . . . . . . . 1-47 (IMSI) . . . . . . . . . . . . . . . . . . . 1-15
GUI . . . . . . . . . . . . . . . . . . . 3-12 introduction
MSC to BSC. . . . . . . . . . . . . 1-59, 2-20 GPRS . . . . . . . . . . . . . . . . . . 2-33
PCU . . . . . . . . . . . . . . . . 2-60 to 2-61 GSN complex . . . . . . . . . . . . . . 2-34
PCU-BSC . . . . . . . . . . . . . . . . 2-61 PCU . . . . . . . . . . . . . . . . . . . 2-34
protocol layering . . . . . . . . . . . . 2-20 introduction to the system processor . . . 3-40
redundancy . . . . . . . . . . . . . . . 2-32 ISDN . . . . . . . . . . . . . . . . . . . 1-57
standardized . . . . . . . . . . . . . . 1-54 ISDN compatibility
standardized electrical overview . . . . . . . . . . . . . . . . 1-47
overview . . . . . . . . . . . . . . . 1-47
LAPD . . . . . . . . . . . . . . . . . . . 1-68 logical channels . . . . . . . . . . . . . . 1-41

LCF Memory saving to prolong the life of existing overview . . . . . . . . . . . . . . . . 1-42
GPROC2 . . . . . . . . . . . . . . . . . 4-125 types
LCS overview . . . . . . . . . . . . . . . 1-42
LoCation Services . . . . . . . . . . 1-51, 4-64 logical groups . . . . . . . . . . . . . . . 3-73
link hardware devices . . . . . . . . . . . . 3-76
types . . . . . . . . . . . . . . . . . . 3-28 logical links . . . . . . . . . . . . . . . 3-77
link quality . . . . . . . . . . . . . . 1-18, 1-49 radio frequency . . . . . . . . . . . . . 3-78
links software functions . . . . . . . . . . . 3-77
maps . . . . . . . . . . . . . . . . . . 3-61 logical links . . . . . . . . . . . . . . . . 3-77
overview . . . . . . . . . . . . . . . . . 2-2 OML, MTL, RSL, XBL, CBL . . . . . . . 3-28
physical/logical . . . . . . . . . . . . . 3-25 lost calls . . . . . . . . . . . . . . . 1-18, 1-49
local registration and call handover low bit rates
overview . . . . . . . . . . . . . . . . 1-27 non-voice data
Location Services (LCS). . . . . . . . 1-51, 4-64 overview . . . . . . . . . . . . . . . 1-49
maintenance MapNode . . . . . . . . . . . . . . . . . 3-71

Motorola GSM . . . . . . . . . . . . . . 1-7 maps . . . . . . . . . . . . . . . . . . . 3-59
map . . . . . . . . . . . . . . . . . . . . 3-56 background maps . . . . . . . . . . . . 3-61
configuration . . . . . . . . . . . . . . 3-60 configuration objects . . . . . . . . . . 3-69
links. . . . . . . . . . . . . . . . . . . 3-61 graphic objects . . . . . . . . . . . . . 3-69
state changes . . . . . . . . . . . . . . 3-61 maps icon . . . . . . . . . . . . . . . . . 3-51
Map measured parameters . . . . . . . . . . . 1-49
automatically created objects . . . . . . 3-81 medium access mode
MapLink . . . . . . . . . . . . . . . 3-81 software features . . . . . . . . . . . . 2-44
MapNode . . . . . . . . . . . . . . . 3-81 Message Transfer Link (MTL) . . . . . . . 1-26
MAP. . . . . . . . . . . . . . . . . . 1-26, 1-57 MMS
Map display MSI . . . . . . . . . . . . . . . . . . . 3-19
map icons . . . . . . . . . . . . . . . . 3-63 Mobile Application Part (MAP) . . . . 1-26, 1-57
MapLink . . . . . . . . . . . . . . . . . 3-72 mobile services switching centre . . . . . 1-23
68P02901W01-S IX-89
Jul 2008
Index
mobile services switching centre (contd.) MS flow control (contd.)

overview . . . . . . . . . . . . . . 1-2, 1-23 software features . . . . . . . . . . . . 2-49
mobile station . . . . . . . . . . . . . . . 1-19 MS to MS calls
overview . . . . . . . . . . . . . . . . 1-14 MS to MS
Mobile Subscriber ISDN (MSISDN) different PLMN different country . . . 1-37
number . . . . . . . . . . . . . . . . . . 1-16 different PLMN same country. . . . . 1-36
mobility management same PLMN . . . . . . . . . . . . . . 1-35
functional layering . . . . . . . . . . . 1-55 overview . . . . . . . . . . . . . . . . 1-34
modem . . . . . . . . . . . . . . . . 1-19, 1-44 MS to PSTN subscriber
module overview . . . . . . . . . . . . . . . . 1-33
information . . . . . . . . . . . . . . . 1-16 MSC
Motorola network specifications interaction with BSC . . . . . . . . . . . 2-5
introduction . . . . . . . . . . . . . . . . 1-8 interface to BSC . . . . . . . . . . 1-59, 2-20
Motorola OMC site configurations
typical configuration . . . . . . . . . . 3-36 overview . . . . . . . . . . . . . . . 2-12
MPROC . . . . . . . . . . . . . . . . . . 2-54 MSC object . . . . . . . . . . . . . . . . 3-75
(PSP) . . . . . . . . . . . . . . . . . . 2-54 MSI
MS MMS . . . . . . . . . . . . . . . . 3-19, 3-33
interface to BTS. . . . . . . . . . . 1-60, 2-21 MSI object . . . . . . . . . . . . . . . . 3-77
power saving MSISDN . . . . . . . . . . . . . . . . . 1-16
overview . . . . . . . . . . . . . . . 1-49 MTL. . . . . . . . . . . . . . . . . . . . 3-28
tracking MTP. . . . . . . . . . . . . . . . . . . . 1-67
overview . . . . . . . . . . . . . . . 1-49 multiplexer . . . . . . . . . . . . . . 3-31, 3-38
MS flow control multiplexing. . . . . . . . . . . . . . . . 1-41
NC1 network maps . . . . . . . . . . . . . . . 3-59

Nework Controlled cell reselectionLoCation network object . . . . . . . . . . . . . . 3-75
Services . . . . . . . . . . . . . . . . . 4-62 network status summary . . . . . . . . . 3-51
NC2 network topology
Network Controlled cell reselection. . . 4-62 BSS . . . . . . . . . . . . . . . . . . . 2-16
network daisy chain with fork and return loop to
devices . . . . . . . . . . . . . . . . . 3-33 BSC . . . . . . . . . . . . . . . . . . . 2-18
hierarchy . . . . . . . . . . . . . . . . . 3-5 daisy chain with fork and return loop to
traffic capacity . . . . . . . . . . . . . 3-39 chain . . . . . . . . . . . . . . . . . . 2-17
network architecture . . . . . . . . . . . 2-36 drop and insert . . . . . . . . . . . . . 2-18
Network Assisted Cell Change . . . . . . 4-104 open ended daisy chain . . . . . . . . . 2-17
network configuration. . . . . . . . . . . 3-59 star (spoke) . . . . . . . . . . . . . . . 2-17
Network Controlled cell reselection New drop call rate classes statistics . . . 4-118
NC1/NC2 . . . . . . . . . . . . . . . . 4-62 New GPRS alarms. . . . . . . . . . . . . 4-103
network elements NFS (Network File System) . . . . . . . . 3-49
location register . . . . . . . . . . . . . 1-3 night concentration configuration. . . . . 3-55
overview . . . . . . . . . . . . . . . . . 2-3 NMC . . . . . . . . . . . . . . . . . . . . 3-5
Network File System (NFS) . . . . . . . . 3-49 noise robustness
network management centre radio interface
functions overview . . . . . . . . . . . . . . . 1-51
overview . . . . . . . . . . . . . . . 1-20 non-voice data
overview . . . . . . . . . . . . . . . . . 1-2 low bit rate use
Network Management Centre overview . . . . . . . . . . . . . . . 1-49
(NMC) . . . . . . . . . . . . . . . . . . 3-5 NSS
network map . . . . . . . . . . . . . . . 3-56 features . . . . . . . . . . . . . . . . . 3-51
configuration . . . . . . . . . . . . . . 3-60
IX-90 68P02901W01-S
Jul 2008
Index
objects OMC-R software features (contd.)

source coincident multiband boundaries (contd.)
automatic creation of . . . . . . . . . 3-80 GSR5 . . . . . . . . . . . . . . . . . 5-38
Objects completion of OMC support for Horizonmacro
Map GSR5 . . . . . . . . . . . . . . . . . 5-40
automatic creation of . . . . . . . . . 3-81 CS3, CS4 and 32 kbits/s TRAU
MapLink GSR5.1 . . . . . . . . . . . . . . . . 5-48
automatic creation of . . . . . . . . . 3-81 datagen support
MapNode GSR5 . . . . . . . . . . . . . . . . . 5-43
automatic creation of . . . . . . . . . 3-81 DRI combiner operability improvement
MMS GSR5 . . . . . . . . . . . . . . . . . 5-40
automatic creation of . . . . . . . . . 3-80 dynamic trace call flow control
NESoftware GSR5 . . . . . . . . . . . . . . . . . 5-38
automatic creation of . . . . . . . . . 3-80 EAS relay MMI control for Incell, M-Cell and
SWInventory Horizon
TRX enable cyclic neighbour statistics
OMC enhanced circuit error rate monitor
SUN ULTRA ENTERPRISE 3500 . . . . . 3-7 GSR6 . . . . . . . . . . . . . . . . . 5-52
OMC software features . . . . . . . . . . 5-56 enhanced SDCCH to TCH assignment
OMC-R GSR5 . . . . . . . . . . . . . . . . . 5-42
command line interface . . . . . . . . . 3-15 expansion/de-expansion
configurations. . . . . . . . . . . . . . . 3-7 GSR5 . . . . . . . . . . . . . . . . . 5-46
GUI client . . . . . . . . . . . . . . . . 3-54 Feature Capacity Licensing and Audit. . 5-70
GUI front panel . . . . . . . . . . . . . 3-12 flexible neighbour cell processing
network management architecture . . . . 3-5 GSR5 . . . . . . . . . . . . . . . . . 5-38
Network management functions . . . . . 3-3 geographic command partitioning and region
NSS feature . . . . . . . . . . . . . . . 3-51 support
OMC . . . . . . . . . . . . . . . . . . . 3-7 geographic command partitioning . . 5-50
PCU management . . . . . . . . . . . . 2-52 GPROC fast reset
processes . . . . . . . . . . . . . . . . 3-43 GSR5.1 . . . . . . . . . . . . . . . . 5-49
software requirements . . . . . . . . . 3-10 GSM half rate . . . . . . . . . . . . . . 5-63
OMC-R database . . . . . . . . . . . . . 3-47 GSM Half Rate . . . . . . . . . . . . . 5-63
OMC-R functions . . . . . . . . . . . . . 3-17 increased capacity OMC-R
OMC-R object . . . . . . . . . . . . . . . 3-75 GSR5 . . . . . . . . . . . . . . . . . 5-45
OMC-R software features increased OMC-R neighbour stats
120K TCH OMC Capacity Expansion. . 5-65 GSR5 . . . . . . . . . . . . . . . . . 5-44
adaptive handover increasing maximum number of trunks per BSC
GSR5 . . . . . . . . . . . . . . . . . 5-37 GSR5 . . . . . . . . . . . . . . . . . 5-45
Applix 4.41 upgrade Intelligent Audit. . . . . . . . . . . . . 5-64
GSR5 . . . . . . . . . . . . . . . . . 5-41 intelligent congestion relief
Bay level cal default data GSR5 . . . . . . . . . . . . . . . . . 5-37
GSR5 . . . . . . . . . . . . . . . . . 5-41 interrogation of NHA with GSM OMC-R EM
BTS concentration GSR5 . . . . . . . . . . . . . . . . . 5-40
GSR5 . . . . . . . . . . . . . . . . . 5-36 Network Expansion - Phase 4 . . . . . . 5-59
cell parameter import/export network expansion batch capability
GSR5 . . . . . . . . . . . . . . . . . 5-41 GSR5 . . . . . . . . . . . . . . . . . 5-44
cell Xchange NHA support maximum size GSM OMC-R
GSR6 . . . . . . . . . . . . . . . . . 5-55 GSR5 . . . . . . . . . . . . . . . . . 5-40
Cell Xchange - BSS support . . . . . . . 5-59 OMC-R GUI supportfor PCU device object
changing NE ID of Assoc_BSSs or GSR5 . . . . . . . . . . . . . . . . . 5-44
Assoc_RXCDRs OMC-R GUI usability
GSR5 . . . . . . . . . . . . . . . . . 5-42 GSR5 . . . . . . . . . . . . . . . . . 5-43
coincident multiband boundaries OMC-R GUI usability for large network support
68P02901W01-S IX-91
Jul 2008
Index
OMC-R software features (contd.) OMC-R software features (contd.)

OMC-R GUI usability for large network support Release GSR6 . . . . . . . . . . . . . . 5-50
(contd.) Release GSR6 (Horizon II) . . . . . . . 5-56
GSR6 . . . . . . . . . . . . . . . . . 5-53 Release GSR7 . . . . . . . . . . . . . . 5-59
online network expansion - phase 3 Release GSR8 . . . . . . . . . . . . . . 5-64
GSR6 . . . . . . . . . . . . . . . . . 5-54 removal of clear stats command
optimized power control GSR5 . . . . . . . . . . . . . . . . . 5-47
GSR5 . . . . . . . . . . . . . . . . . 5-36 reporting the results of alarms recovery action
PCU alarms detected by HSC GSR5 . . . . . . . . . . . . . . . . . 5-38
GSR5 . . . . . . . . . . . . . . . . . 5-47 support for Vanguard 6455 router
Performance Enhancements for GPRS. . 5-60 GSR5 . . . . . . . . . . . . . . . . . 5-46
propogation after audit support of BCCH and SDCCH for EGSM
GSR5 . . . . . . . . . . . . . . . . . 5-36 GSR5 . . . . . . . . . . . . . . . . . 5-37
proxy cell autocreation system upgrade
GSR5 . . . . . . . . . . . . . . . . . 5-39 GSR5 . . . . . . . . . . . . . . . . . 5-42
proxy cell import/export unequip of TCU/CTU cabinets
GSR5 . . . . . . . . . . . . . . . . . 5-39 GSR5.1 . . . . . . . . . . . . . . . . 5-49
Q3 support Upgrade OS to Solaris 2.9 . . . . . . . 5-68
GSR5 . . . . . . . . . . . . . . . . . 5-40 Vanguard software upgrade support
Release 1.1.2.0 . . . . . . . . . . . . . . 5-3 GSR5 . . . . . . . . . . . . . . . . . 5-46
Release 1.1.2.1 . . . . . . . . . . . . . . 5-5 Web Access Server . . . . . . . . . . . 5-62
Release 1.1.2.2 . . . . . . . . . . . . . . 5-6 web MMI
Release 1.1.2.3 . . . . . . . . . . . . . . 5-8 GSR5.1 . . . . . . . . . . . . . . . . 5-48
Release 1.1.2.4 . . . . . . . . . . . . . 5-10 OMC-R system configuration
Release 1.2.0.0 . . . . . . . . . . . . . 5-11 hardware impact . . . . . . . . . . . . 3-50
Release 1.2.2.1 . . . . . . . . . . . . . 5-15 OML . . . . . . . . . . . . . . . . . . . 3-28
Release 1.2.2.2 . . . . . . . . . . . . . 5-18 one phase access
Release 1.2.3.0 . . . . . . . . . . . . . 5-19 software features . . . . . . . . . . . . 2-47
Release 1.3.0.0 . . . . . . . . . . . . . 5-20 operating system
Release 1.4.0.0 . . . . . . . . . . . . . 5-21 non-stop-UX A22 IPM02. . . . . . . . . 3-45
Release 1.4.0.1 . . . . . . . . . . . . . 5-23 operations and maintenance centre
Release 1.4.0.6 . . . . . . . . . . . . . 5-25 overview . . . . . . . . . . . . . . . . . 1-2
Release 1.4.0.7 . . . . . . . . . . . . . 5-26 Operator workstations . . . . . . . . . . . 3-9
Release 1.4.1.0 . . . . . . . . . . . . . 5-27 Optional processors . . . . . . . . . . . . 3-10
Release GSR2 . . . . . . . . . . . . . . 5-29 OSI . . . . . . . . . . . . . . . . . . . . 1-65
Release GSR3 . . . . . . . . . . . . . . 5-32 Out Of Service (OOS) state . . . . . . . . 3-59
Release GSR4 . . . . . . . . . . . . . . 5-33 Out_inter_bss_ho statistical counter . . . 4-97
Release GSR4.1 . . . . . . . . . . . . . 5-34 Overview
Release GSR5 . . . . . . . . . . . . . . 5-35 VersaTRAU . . . . . . . . . . . . . . . 2-37
Release GSR5.1 . . . . . . . . . . . . . 5-48
packet switch . . . . . . . . . . . . . 3-31, 3-38 PCI to PCI bridge . . . . . . . . . . . . . 2-55

PADS PCS1900 frequencies and channels . . . . 1-108
X.25 . . . . . . . . . . . . . . . . . . . 1-44 PCS1900 channels . . . . . . . . . . . 1-109
Paging CHannel (PCH) . . . . . . . . . . 1-42 PCS1900 frequencies . . . . . . . . . . 1-108
part PCU . . . . . . . . . . . . . . . . . . . . 2-39
application . . . . . . . . . . . . . . . 1-57 architecture . . . . . . . . . . . . . . . 2-54
BSS mobile . . . . . . . . . . . . . . 1-41 chassis . . . . . . . . . . . . . . . . . 2-58
direct transfer . . . . . . . . . . . . 1-41 environment . . . . . . . . . . . . . . 2-41
mobile . . . . . . . . . . . . . . . . 1-26 fault tolerance . . . . . . . . . . . . . 2-59
password protection features summary . . . . . . . . . . . . 2-42
security management . . . . . . . . . . 1-13 interfaces . . . . . . . . . . . . . 2-60 to 2-61
PATH introduction of PCU . . . . . . . . . . . 3-75
physical link. . . . . . . . . . . . . . . 3-26 list of features. . . . . . . . . . . . . . 2-42
IX-92 68P02901W01-S
Jul 2008
Index
PCU (contd.) PMC

management . . . . . . . . . . . . . . 2-52 E1. . . . . . . . . . . . . . . . . . . . 2-58
overview . . . . . . . . . . . . . . 2-34, 2-39 point-to-point GPRS service
purpose . . . . . . . . . . . . . . . . . 2-51 software features . . . . . . . . . . . . 2-42
roadmap features . . . . . . . . . . . . 2-42 power budget . . . . . . . . . . . . . . . 3-23
summary . . . . . . . . . . . . . . . . 2-40 power control . . . . . . . . . . . . . . . 3-23
system functions . . . . . . . . . . . . 2-64 overview . . . . . . . . . . . . . . . . 2-24
PCU architecture power control: uplink/downlink
PPB . . . . . . . . . . . . . . . . . . . 2-55 software features . . . . . . . . . . . . 2-48
PCU High bandwidth interconnection. . . 4-120 power saving
PCU load balancing & sharing MS
software features . . . . . . . . . . . . 2-49 overview . . . . . . . . . . . . . . . 1-49
PCU processes PPB
PRP processes . . . . . . . . . . . . . 2-65 PCU architecture . . . . . . . . . . . . 2-55
PCU Software Upgrade without BSC Private eXchange Packet Data Network
Outage . . . . . . . . . . . . . . . . . . 4-118 PXPDN . . . . . . . . . . . . . . . . . 3-38
PCU system procedures
overview . . . . . . . . . . . . . . . . 2-51 handover . . . . . . . . . . . . . . . . 1-48
PCU-BSC protocol stacks
interface . . . . . . . . . . . . . . . . 2-61 TCP/IP, Ethernet, X11, X25 . . . . . . . 3-37
performance measurements . . . . . . . 3-34 protocols
performance mgt . . . . . . . . . . . . . 3-43 network . . . . . . . . . . . . . . . . . 1-64
Periodic Supervision of Accessibility PRP . . . . . . . . . . . . . . . . . . . . 2-55
(PSA) . . . . . . . . . . . . . . . . . . . 3-82 processes . . . . . . . . . . . . . . . . 2-65
physical channels PSA
overview . . . . . . . . . . . . . . . . 1-42 definition . . . . . . . . . . . . . . . . 3-82
physical layer PSP
functional layering . . . . . . . . . . . 1-55 functions . . . . . . . . . . . . . . . . 2-54
physical link PSTN . . . . . . . . . . . . . . . . . . . 1-44
PATH . . . . . . . . . . . . . . . . . . 3-26 PSTN subscriber to MS
PICP . . . . . . . . . . . . . . . . . . . 2-55 overview . . . . . . . . . . . . . . . . 1-34
PM sub schema . . . . . . . . . . . . . . 3-47 PXPDN . . . . . . . . . . . . . . . . . . 3-38
quality of reception . . . . . . . . . . . . 1-48 Quality of Service PhaseII Feature . . . . 4-122
radio redundancy (contd.)

functions . . . . . . . . . . . . . . . . 2-64 BTS . . . . . . . . . . . . . . . . . . . 2-32
radio channel air interface . . . . . . . . 1-57 interfaces . . . . . . . . . . . . . . . . 2-32
radio channel bit rate . . . . . . . . . . . 1-41 RF carrier . . . . . . . . . . . . . . . . 2-32
radio frequency . . . . . . . . . . . . . . 3-78 RXCDR . . . . . . . . . . . . . . . . . 2-32
radio planning . . . . . . . . . . . . . . 1-50 related commands and parameters
radio resource management security management . . . . . . . . . . 1-13
functional layering . . . . . . . . . . . 1-55 remote login . . . . . . . . . . . . . . . 3-43
Random Access CHannel (RACH) . . . . . 1-42 Remove support for collocated BSC
RCU. . . . . . . . . . . . . . . . . . . . 3-20 feature . . . . . . . . . . . . . . . . . 4-72
RDBMS . . . . . . . . . . . . . . . . . . 3-47 resource management . . . . . . . . 1-61, 2-21
received level . . . . . . . . . . . . . . . 1-48 RF carrier
redundancy redundancy . . . . . . . . . . . . . . . 2-32
BSC . . . . . . . . . . . . . . . . . . . 2-32 RSL . . . . . . . . . . . . . . . . . . . . 3-28
BSS . . . . . . . . . . . . . . . . . . . 2-31 RSL Congestion Control. . . . . . . . . . 4-111
68P02901W01-S IX-93
Jul 2008
Index
RSL dimensioning statistics . . . . . . . . 4-115 RXCDR (contd.)

RTF . . . . . . . . . . . . . . . . . . . . 3-22 operation and maintenance . . . . . . . . 3-5
BCCH . . . . . . . . . . . . . . . . . . 3-22 purpose and functions . . . . . . . . . . 2-9
non-BCCH. . . . . . . . . . . . . . . . 3-22 redundancy . . . . . . . . . . . . . . . 2-32
RXCDR . . . . . . . . . . . . . . . . . . . 1-3 RXCDR object . . . . . . . . . . . . . . . 3-75
functions . . . . . . . . . . . . . . . . 3-17
SCCP . . . . . . . . . . . . . . . . . . . 1-67 software features (contd.)

security management medium access mode . . . . . . . . . . 2-44
password protection . . . . . . . . . . 1-13 one phase access . . . . . . . . . . . . 2-47
security procedures PCU load balancing & sharing . . . . . 2-49
overview . . . . . . . . . . . . . . . . 1-27 PCU MS flow control . . . . . . . . . . 2-49
services point-to-point GPRS service . . . . . . . 2-42
ISDN-type. . . . . . . . . . . . . . . . 1-19 power control: uplink/downlink . . . . . 2-48
SGSN support of mobile classes . . . . . . . . 2-44
functions . . . . . . . . . . . . . . . . 2-64 two phase packet access . . . . . . . . 2-47
short message service software functions . . . . . . . . . . . . 3-77
overview . . . . . . . . . . . . . . . . 1-27 software load mgt . . . . . . . . . . . . . 3-43
signaling performance . . . . . . . . 1-18, 1-49 Software patching. . . . . . . . . . . . . 4-117
signalling link protocols Software support for High Bandwidth and/or
overview . . . . . . . . . . . . . . . . 1-68 existing E1 BSC/PCU interconnect . . . . 4-124
signalling links Software support for High power Horizon II
summary . . . . . . . . . . . . . . . . 1-58 Micro . . . . . . . . . . . . . . . . . . . 4-119
signalling system 7 . . . . . . . . . . 1-25, 1-67 specifications
C7 . . . . . . . . . . . . . . . . . . . 1-47 OMC-R . . . . . . . . . . . . . . . . . . 1-8
SIM . . . . . . . . . . . . . . . . . . . . 1-16 receiver . . . . . . . . . . . . . . . . . 1-11
single BCCH for dual band cells speech channels
feature dependencies . . . . . . . . . . 4-55 traffic channels . . . . . . . . . . . . . 1-43
site configurations speech transcoder . . . . . . . . . . . . . 1-3
BSC remote . . . . . . . . . . . . . . . . . . 1-3
overview . . . . . . . . . . . . . . . 2-12 SQL . . . . . . . . . . . . . . . . . . . . 3-48
BTS Stand-alone Dedicated Control CHannel
overview . . . . . . . . . . . . . . . 2-12 SDCCH . . . . . . . . . . . . . . . . . 1-43
CELL . . . . . . . . . . . . . . . . . . 3-20 standardized electrical interfaces
introduction . . . . . . . . . . . . . . . 2-10 overview . . . . . . . . . . . . . . . . 1-47
MSC star (spoke)
overview . . . . . . . . . . . . . . . 2-12 network topology . . . . . . . . . . . . 2-17
site definition . . . . . . . . . . . . . . 3-18 state changes
SITE object . . . . . . . . . . . . . . . . 3-75 admin and operational . . . . . . . . . 3-64
Slow Associated Control CHannel on map display . . . . . . . . . . . . . 3-61
(SACCH) . . . . . . . . . . . . . . . . . 1-43 status summary window . . . . . . . . . 3-59
smart card . . . . . . . . . . . . . . . . 1-16 Stop BTS transmission after the last RSL
software elements fails . . . . . . . . . . . . . . . . . . . . 4-96
system processor . . . . . . . . . . . . 3-43 sub schema
software features EM, PM . . . . . . . . . . . . . . . . . 3-47
coding schemes . . . . . . . . . . . . . 2-45 subscriber identity
dynamic adaptation of coding mobile. . . . . . . . . . . . . . . . . . 1-15
schemes. . . . . . . . . . . . . . . . . 2-47 ISDN . . . . . . . . . . . . . . . . . 1-16
enhanced one phase access . . . . . . . 2-47 temporary. . . . . . . . . . . . . . . 1-16
Extended Dynamic Allocation Medium Access Subscriber Information Module (SIM) . . 1-16
Mode (EDMAC) . . . . . . . . . . . . . 2-44 Support for . . . . . . . . . . . . . . . . 4-119
frequency hopping of PDCH. . . . . . . 2-48 Support for GPRS Trace. . . . . . . . . . 4-101
Gb interface. . . . . . . . . . . . . . . 2-49 Support for Half Rate on GDP2 . . . . . . 4-110
GPRS radio channel allocation . . . . . 2-43 Support for Horizon II Mini . . . . . . . . 4-108
IX-94 68P02901W01-S
Jul 2008
Index
Support of Incell as an Optional Fea- system planning

ture . . . . . . . . . . . . . . . . . . . . 4-129 Motorola GSM . . . . . . . . . . . . . . 1-6
support of mobile classes system processor . . . . . . . . . . . 1-9, 3-40
software features . . . . . . . . . . . . 2-44 configurations. . . . . . . . . . . . . . . 1-9
Support of QoS Release 4 (R4) . . . . . . 4-107 software elements. . . . . . . . . . . . 3-43
Support of RESUME at intra-BSC level . . 4-123 System Processor . . . . . . . . . . . . . . 3-8
switching matrix . . . . . . . . . . . . . 1-40 OMC-R specifications
synchronization . . . . . . . . . . . . . . 1-50 SUN ULTRA ENTERPRISE 3000 . . . . 3-8
Synchronization CHannel (SCH) . . . . . 1-42 systems advantages
system impact Motorola GSM . . . . . . . . . . . . . . 1-6
security management . . . . . . . . . . 1-13
TBF . . . . . . . . . . . . . . . . . . . . 4-68 traffic capacity

TCP/IP . . . . . . . . . . . . . . . . . . 3-45 network . . . . . . . . . . . . . . . . . 3-39
technological requirements . . . . . . . . 1-46 traffic channels . . . . . . . . . . . . . . 1-43
teleservices . . . . . . . . . . . . . . . . 1-48 transceiving
overview . . . . . . . . . . . . . . . . 1-19 DRI/RTF groups . . . . . . . . . . . . . 3-22
Temporary Mobile Subscriber Identity transcoder
(TMSI) . . . . . . . . . . . . . . . . . . 1-16 speech . . . . . . . . . . . . . . . . . . 1-3
terrestrial circuit device management transcoding . . . . . . . . . . . . . . . . 1-41
overview . . . . . . . . . . . . . . . . . 2-6 location . . . . . . . . . . . . . . . . . . 2-9
The CM MIB . . . . . . . . . . . . . . . 3-53 transmission
timing adjustment. . . . . . . . . . . . . 1-50 discontinuous . . . . . . . . . . . . . . 2-25
timing advance transport layer
overview . . . . . . . . . . . . . . . . 2-25 functional layering . . . . . . . . . . . 1-55
TMSI . . . . . . . . . . . . . . . . . . . 1-16 trunking. . . . . . . . . . . . . . . . . . 1-50
topology trustworthiness . . . . . . . . . . . . . . 1-48
BSS network two phase packet access
network topology . . . . . . . . . . . 2-16 software features . . . . . . . . . . . . 2-47
tracking Typical hardware for OMC-R system . . . . 3-8
MS
overview . . . . . . . . . . . . . . . 1-49
Upgrade OS to Solaris 2.9 . . . . . . . . 5-68 uplink . . . . . . . . . . . . . . . . . . . 3-23
validation exercise . . . . . . . . . . . . 1-46 visited location register (contd.)

VersaTRAU . . . . . . . . . . . . . . . . 4-106 overview . . . . . . . . . . . . . . . . 1-31
visited location register VLR . . . . . . . . . . . . . . . . . . 1-3, 1-16
WAN . . . . . . . . . . . . . . . . . . . 3-37 wide area network . . . . . . . . . . . . 3-37
68P02901W01-S IX-95
Jul 2008
Index
X.11 . . . . . . . . . . . . . . . . . . . . 3-37 XBL . . . . . . . . . . . . . . . . . . . . 3-28

X.21 address . . . . . . . . . . . . . . . 3-31 XCDR
X.25 . . . . . . . . . . . . . . . 1-22, 1-68, 3-37 cell broadcast centre . . . . . . . . . . . 1-3
X.25 PADS . . . . . . . . . . . . . . . . 1-44
IX-96 68P02901W01-S
Jul 2008

68P02901W01 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

68P02901W01 PDF

Uploaded by

Copyright:

Available Formats

GSM Overview

2008 Motorola, Inc. All Rights Reserved.

System Information: GSM Overview

Chapter 1: Introduction to Motorola GSM

Introduction to Motorola network elements . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

HLR master database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

Chapter 2: BSS General Description

Antenna systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Introduction to GPRS and EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Chapter 3: OMC-R Overview

Network levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Packet switch or multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

How administrative and operational state changes work. . . . . . . . . . . . . . . . . . . . . 3-64

Chapter 4: BSS Software Release Features

Important information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Multiple GPRS carriers per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58

BSS software release GSR9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-112

Chapter 5: OMC-R Software Release Features

OMC-R software release 1.2.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

OMC-R GUI usability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43

Chapter 6: Glossary of Technical Terms

F Interface - Full Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

Figure 1-1: GSM equipment architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Figure 3-4: The Expert OMC-R GUI front panel . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Table 1-46: DCS1800 channels 571 to 580 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-92

Table 1-104: PCS 1900 channels 771 to 780 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-122

Table 5-1: Release 1.1.2.3 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

System Information: GSM Overview

What is covered in this manual?

Chapter 2, BSS general description.

Chapter 3, OMC-R overview.

Chapter 4, BSS software release features.

Chapter 5, OMC-R software release features.

Chapter 6, Glossary of terms, acronyms, and abbreviations.

The following sections show the revision status of this document.

Issue Date of issue Remarks

Resolution of Service Requests

The following Service Requests are resolved in this document:

Incorporation of Change Notices

The following Change Notices (CN) are incorporated in this document:

CN Date CN Number Title

Characters typed in at the keyboard are shown like this sentence.

Messages, prompts, file listings, directories, utilities, and environmental

Special key sequences

Special key sequences are represented as follows:

Motorola appreciates feedback from the users of our documents.

Questions and comments

The document title, part number, and revision character

The page number with the error

A detailed description of the error and if possible the proposed solution

In certain instances, Motorola makes specific recommendations regarding security practices.

Warnings, cautions, and notes

A note means that there is a possibility of an undesirable situation or provides additional

The following general safety guidelines apply to Motorola equipment:

Power down or unplug the equipment before servicing.

Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

Council recommendation of 12 July 1999 on the limitation of exposure of the general

Caring for the environment

Disposal of Motorola equipment

Disposal of surplus packaging

CMM labeling and disclosure table

The label is placed in a customer visible position on the product.

Motorola document set