Sys02 GSR9

SYS02: Introduction to BSS Database GSR9

FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED
2006 Motorola, Inc.
June 2007
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories
or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs,
including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer
programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express
written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication,
estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the rights that arise by operation
of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or
disclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized
copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system,
or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting fromany inaccuracies
or omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products
described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to
time in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume any liability arising out of the
application or use of any product or circuit described herein; neither does it convey license under its patent rights of others.
Trademarks
Motorola and the Motorola logo are registered trademarks of Motorola Inc.
M-Cell, Tasknder and Intelligence Everywhere are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
CE Compliance
The CE mark conrms Motorola Ltds 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 the CNRC help desk, contact details below:
Email: csc.emea@motorola.com
Tel: +44 (0) 1793 565 444
2006 Motorola, Inc.
June 2007
Contents


General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
ETSI standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Structure of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Electromagnetic energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Reporting Safety Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Failure to comply with warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Specic warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Protective Equipment Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Caution labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Specic cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Devices sensitive to electrostatic discharge (ESD) . . . . . . . . . . . . . . . . . . . . . . . . 10
Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 1: Network Conguration Review
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Network Conguration Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Base Station System (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Network Switching System (NSS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Hardware Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Base Station Unit (BSU) Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Remote Transcoder Unit (RXU3) Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1st Generation BTS - InCell Cabinet ( BTS 4/5/6) . . . . . . . . . . . . . . . . . . . . . . . 1-10
2nd Generation BTS - MCell Cabinet ( MCell2/6) . . . . . . . . . . . . . . . . . . . . . . . 1-12
3rd Generation BTS - Horizonmacro Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Horizon II Macro Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Horizon II Mini Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Horizon II Micro Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Software Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
BSC Initialisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Initialisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
BSS Reset Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Global Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Conguration Management (CM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
CM Database Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38
CM Database and Central Authority Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
To Change Site Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
CM Database and CA Interaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
To Change Remote BTS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
Database Level Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
Software Patching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46
Patch Object Download and Patch Level Application . . . . . . . . . . . . . . . . . . . . . 1-48
BSS Radio Sub System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50
2006 Motorola, Inc.
i
June 2007
Contents SYS02: Introduction to BSS Database GSR9
BSS Conguration and Fault Management Interface . . . . . . . . . . . . . . . . . . . . . . . 1-52
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52
Layer 1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52
Layer 2 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52
RSS A-bis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52
Handover Detection and Power Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54
Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56
MTP L3/SCCP Preprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56
Connectionless Manager (CLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56
SCCP State Machine (SSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56
Switch Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56
Cell Resource Manager (CRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Radio Resource State Machine (RRSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Radio Channel Interface (RCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Comparison GSM and Motorola Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60
User Security Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64
NE User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64
NE Field Engineer Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64
OMC-R Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-66
BSC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-66
QCOM LOgin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-66
Password Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68
Chapter 2: Network Element Conguration
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
BSS Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
The Base Station System (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
The Base Station Controller (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
The Base Transceiver Station (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
The Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Command/Database Parameters Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Type A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
RXCDR/BSS/SITE/CAB/CAGE Numbering Scheme . . . . . . . . . . . . . . . . . . . . . . . 2-10
RXCDR/BSS/SITE/CAB/CAGE NUMBERING CHART . . . . . . . . . . . . . . . . . . . . 2-10
Site Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Equipping the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Equipping the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
equip <0 or bsc> AXCDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Equipping a SITE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Site Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Operating Modes and Denitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Ater Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Increased Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
CPU Utilisation Feature Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
BSC LAN Packing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Benets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
LAN Packing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Cabinet Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
1st prompt (identier): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Cage Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
1st prompt (identier) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Site Conguration Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Site Conguration Exercise 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Site Conguration Exercise 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Kilo-Port Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
KSW Extension/Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
DSW2 Extension/Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
DSW2 Operational Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
DSW2 Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
KSW Conguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Common Device/Function Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
Generic Clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
GCLK Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
ii SYS02: Introduction to BSS Database GSR9
2006 Motorola, Inc.
June 2007
SYS02: Introduction to BSS Database GSR9 Contents
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Free Run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Hold Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Set Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Closed Loop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
Base Site Processor (BSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
Code Storage Facility Processor (CSFP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68
Multiport Serial Interface (MSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
In-cell MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72
In-Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72
BSC PSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74
PSI MCU Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78
Additional Database Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-80
BSC Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82
BTS Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-84
BSC/ BTS Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86
GPROC Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88
Generic Processor Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-90
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-90
GPROC Function Pre-emption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92
Function Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-94
LCF Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-96
Radio Signalling Link (RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
Optional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
Message Transfer Link (MTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-104
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-104
Operations and Maintenance Link (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-106
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-106
Cell Broadcast Link (CBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-108
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-108
Location Message Transfer Link (LMTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-110
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-110
XBL Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-112
Equipping the XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-114
Enter the ABSS or AXCDR id for the XBL. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-114
XBL Connectivity: add_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-116
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-116
XBL Connectivity Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-118
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-118
Enhanced XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
CIC Blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
Link Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
Number of XBLs Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
BSS/RXCDR Verication and Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
XBL Connectivity Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122
Adding a Control Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-124
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-124
Unequip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-126
Un-equip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-126
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-126
Sysgen On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-126
Sysgen On/OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-126
Synchronisation Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-128
Remote Loss Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-130
Site Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-132
Slip Loss Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-134
BER Loss Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-136
BER Monitoring Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-138
Site Synchronisation Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-140
Site Synchroniation Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-140
2006 Motorola, Inc.
iii
June 2007
N Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142
Statistics Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-144
Chapter 3: Transcoder Conguration
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Remote Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Recent Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
RXCDR Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
RXCDR - 1.9.0.0 Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Equipping the RXCDR and ABSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
ABSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Equipping CICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Which BSS/RXCDR is managing the CICs. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
MMS id to BSC/RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Starting timeslot and Subgroup (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
MMS id to MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Starting timeslot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Terrestrial Circuits: Circuit Identity Codes (CICs) . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Circuit Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Enhanced BSS Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
AMR Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Circuit/Channel Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Relationship Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Call Downgrade on CIC Capability Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Call Downgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Adaptive Multi-Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
AMR Full-Rate Channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
AMR Full-Rate Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
AMR Half-Rate Channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
AMR Half-Rate Link Adaptation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Active Codec Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
AMR/GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
AMR Half Rate/GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Enabling AMR/GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Enhanced GDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Enhanced GDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Enhanced GDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Equipping a GDP Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Equipping a GDP 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
On Line Reconguration of GDP Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
On Line Reconguration of GDP cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Transcoder On-Line Expansion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
MSC Quietone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Downlink DTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Chapter 4: BSS Conguration
BSS Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Device and Function Dependency - In-Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
BSS - 1.9.0.0 Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Script Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
BSS - 1.9.0.0 Script Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Link Control Function (LCF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Operations and Maintenance Function (OMF) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
External Alarm System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
EAS Alarm Text String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
EAS Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
iv SYS02: Introduction to BSS Database GSR9
2006 Motorola, Inc.
June 2007
BTS Script (site 32). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
BTS Script (site 33). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
BSC Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
MTP Level 3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Signalling Point Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Enhanced Multi-level Precedence and Pre-emption Service . . . . . . . . . . . . . . . . . . . 4-24
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Assignment request / Handover Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
TCH Pre-emption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Emergency Call Pre-emption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
ATER Pre-emption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Precedence Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
BSS Feature Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Multiple Encryption Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Circuit Error Rate Monitor (CERM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
Enhanced Circuit Error Rate Monitor (ECERM) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
ECERM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Timers at the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Increments at the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Alarm Generation at the BSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Alarm Clearing at the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
GPRS Monitoring Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
AMR/GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Short Message Service Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Cell Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Multiple Background Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Point to Point SMS Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Trafc Channel SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
AGCH ow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
The Flow Control Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
Access Class Barring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
max_retran and tx_integer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
RSS Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
RACH Non-Overload (Uplink). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
RACH Overload (downlink) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
AGCH Non-Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
AGCH Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
RACH Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
RACH Load Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Load_Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Base_Slot_Count. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
RACH_Slot_ Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Correct Access Percentage (Standard) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
Standard RACH load Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Alternative RACH Load Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
RACH_Incorrect_Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
No_Rach_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
RACH_Busy_ Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
Busy Access Percentage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Alternative RACH Load Indication Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
Site Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
CRM Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
SSM Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
MSC Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86
RSL Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88
2006 Motorola, Inc.
v
June 2007
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88
Enabling the RSL Overload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
Detecting RSL Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
RSL Congestion Control Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
Control of RSL Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
BSC Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96
Possible BSC Overload Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96
Assumptions and Transition States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100
BSS Location Services (LCS) - System Overview. . . . . . . . . . . . . . . . . . . . . . . . . 4-104
TA Positioning Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104
E-OTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104
A-GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104
BSS Location Services (LCS) - Network Architecture . . . . . . . . . . . . . . . . . . . . . . . 4-106
GMLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106
SMLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106
LMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108
Type A LMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108
Type B LMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108
LMU Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108
LCS Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
LCS Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
LCS Perform Location Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-112
LCS Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-112
Segmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-112
Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114
Path Equipage Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116
Chapter 5: BTS Conguration
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Device and Function Dependency - M-Cell/Horizon. . . . . . . . . . . . . . . . . . . . . . . . 5-4
BTS Script Building. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Script Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
BTS - 1.9.0.0 Script Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Battery Conservation, Mains Power Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Base Transceiver Processor (BTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Digital Host Processor (DHP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Digital Radio Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Digital Radio Interface - In-Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Digital Radio Interface - M-Cell/Horizon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Remote Tuneable Combiner (RTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
M-Cell/Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
MSI Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Stop BTS transmitting when cell OOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Chapter 6: Database Building Exercise
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Practical Database Building Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Remote Transcoder Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
LAPD Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
DSP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Trafc Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
GCLK Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
GPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
AMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
GPRS/EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
BSS Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
vi SYS02: Introduction to BSS Database GSR9
2006 Motorola, Inc.
June 2007
External Alarm Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
LAPD Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Trafc Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
GPROCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
BTS Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
BTS Site 1 Specic (Horizon II Macro) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Equipment Shelves. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
BTS Site 2 Specic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
External Alarm System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
BTS Site 3 Specic (micro-cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
M-Cellarena . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Chapter 7: Answers
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
XBL Connectivity Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Site Synchronisation Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
EAS Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Path Equipage Exercise Answers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
# Script for RXCDR Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
# BSS No. 1 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
# BTS Number 1 Answer Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
# BTS Number 2 Answer Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
# BTS Number 3 (M_Cellarena) Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Chapter 8: Glossary
Glossary of technical terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
A Interface - AUTO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
B Interface - Byte. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
C - CW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
D Interface - DYNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
E - EXEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
F Interface - Full Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
G Interface - GWY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
H Interface - Hyperframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
I - IWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
k - KW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
L1 - LV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
M - MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
NACK - nW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42
O - Overlap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-45
PA - PXPDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46
QA- Quiesent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-52
R - RXU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-52
S7- SYSGEN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-57
T -TxBPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-64
U - UUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68
V - VTX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-70
W - WWW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-71
X - X Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-72
ZC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-73
2006 Motorola, Inc.
vii
June 2007
This page intentionally left blank.
viii SYS02: Introduction to BSS Database GSR9
2006 Motorola, Inc.
June 2007
About This Manual Version 1 Rev 3

2006 Motorola, Inc.

1
June 2007
Version 1 Rev 3 General information
General information
NOTE
Motorola disclaims all liability whatsoever, implied or express, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or any one acting on the customers behalf, to abide by the instructions, system parameters or
recommendations made in Motorola Customer Product Documentation.
If this manual was obtained when attending a Motorola training course, it will not be updated or
amended by Motorola. It is intended for TRAINING PURPOSES ONLY.
Purpose
Motorola Technical Training manuals are intended to support the delivery of Technical Training only and
are not intended to replace the use of Motorola Customer Product Documentation.
WARNING
Failure to comply with Motorola's operation, installation and maintenance instructions may, in
exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by Motorola,
although they can be used to supplement and enhance the knowledge gained through such training.
ETSI standards
The standards in the table below are protected by copyright and are the property of the European
Telecommunications Standards Institute (ETSI).
ETSI specication number
GSM 02.60 GSM 04.10 GSM 08.08
GSM 03.60 GSM 04.11 GSM 08.16
GSM 03.64 GSM 04.12 GSM 08.18
GSM 04.01 GSM 04.13 GSM 08.51
GSM 04.02 GSM 04.60 GSM 08.52
GSM 04.03 GSM 04.64 GSM 08.54
GSM 04.04 GSM 04.65 GSM 08.56
GSM 04.05 GSM 08.01 GSM 08.58
GSM 04.06 GSM 08.02 GSM 09.18
GSM 04.07 GSM 08.04 GSM 09.60
GSM 04.08 GSM 08.06
Figures from the above cited technical specications standards are used, in this training manual, with
the permission of ETSI. Further use, modication, or redistribution is strictly prohibited. ETSI standards
are available from http://pda.etsi.org/pda/ and http://etsi.org/eds/
Structure of this manual
This manual is divided into uniquely identied and numbered chapters that, in turn, are divided into
sections. Sections are not numbered, but are individually named at the top of each page, and are listed
in the table of contents.
2 SYS02: Introduction to BSS Database GSR9
2006 Motorola, Inc.
June 2007
General information Version 1 Rev 3
General information
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to represent keyboard
input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, pr ompt s, f i l e l i st i ngs, di r ect or i es, ut i l i t i es, and envi r onment al var i abl es
t hat appear on t he scr een ar e shown l i ke t hi s.
Special key sequences
Special key sequences are represented as follows:
CTRL-c Press the Control and c keys at the same time.
ALT-f Press the Alt and f keys at the same time.
Press the pipe symbol key.
CR or RETURN Press the Return key.
2006 Motorola, Inc.
3
June 2007
Version 1 Rev 3 Safety
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 elds (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 elds) (18th individual Directive within the meaning of
Article 16(1) of Directive 89/391/EEC).
Reporting Safety Issues
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all site
personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
Procedure 1 Safety issue reporting
1 Make the equipment concerned safe, for example by removing power.
2 Make no further attempt to adjust or rectify the equipment.
3 Report the problem directly to the Customer Network Resolution Centre,
Swindon +44 (0)1793 565444 or China +86 10 88417733 (telephone) and
follow up with a written report by fax, Swindon +44 (0)1793 430987 or China
+86 10 68423633 (fax).
4 Collect evidence from the equipment under the guidance of the Customer
Network Resolution Centre.
2006 Motorola, Inc.
June 2007
Warnings and cautions Version 1 Rev 3
Warnings and cautions
The following describes how warnings and cautions are used in this manual and in all manuals of this
Motorola manual set.
Warnings
A denition and example follow below:
Denition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or
ill health. This includes hazards introduced during maintenance, for example, the use of adhesives and
solvents, as well as those inherent in the equipment.
Example and format
WARNING
Do not look directly into bre optic cables or data in/out connectors. Laser radiation can come
from either the data in/out connectors or unterminated bre optic cables connected to data in/out
connectors.
Failure to comply with warnings
Observe all warnings during all phases of operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these warnings, or with specic
warnings elsewhere in the Motorola manuals, or on the equipment itself, violates safety
standards of design, manufacture and intended use of the equipment. Motorola assumes no
liability for the customer's failure to comply with these requirements.
Cautions
A denition and example follow below:
Denition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of
equipment within a system. However, this presents no danger to personnel.
Example and format
CAUTION
Do not use test equipment that is beyond its due calibration date; arrange for calibration to be carried
out.
2006 Motorola, Inc.
5
June 2007
Version 1 Rev 3 General warnings
General warnings
Observe the following specic warnings during all phases of operation, installation and maintenance of
the equipment described in the Motorola manuals:
Potentially hazardous voltage.
Electric shock.
RF radiation.
Laser radiation.
Heavy equipment.
Parts substitution.
Battery supplies.
Lithium batteries,
Protective Equipment Recommendations
Failure to comply with these warnings, or with specic warnings elsewhere in the Motorola manuals,
violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes
no liability for the customer's failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working
with or operating Motorola equipment must comply with any warning labels tted to the equipment.
Warning labels must not be removed, painted over or obscured in any way.
Specic warnings
Specic warnings used throughout the Technical Training manual set are shown below, and will be
incorporated into procedures as applicable.
These must be observed by all personnel at all times when working with the equipment, as must any
other warnings given in text, in the illustrations and on the equipment. Potentially hazardous voltage
Potentially hazardous voltage
WARNING
This equipment operates using a potentially hazardous voltage of 230 V ac single phase or 415 V ac
three phase supply. To achieve isolation of the equipment from the ac supply, the ac input isolator
must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at Work Regulations
1989 (UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
NOTE
Motorola equipment does not utilise high voltages.
Electric shock
WARNING
Do not touch the victim with your bare hands until the electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry insulating material and pull or push the
victim clear of the conductor.
ALWAYS send for trained rst aid or medical assistance IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries and even death,
may result. Direct electrical contact can stun a casualty causing breathing, and even the heart, to stop.
It can also cause skin burns at the points of entry and exit of the current.
In the event of an electric shock it may be necessary to carry out articial respiration. ALWAYS send for
trained rst aid or medical assistance IMMEDIATELY.
2006 Motorola, Inc.
June 2007
General warnings Version 1 Rev 3
General warnings
If the casualty is also suffering from burns, treat the affected area with cold water to cool the burn until
trained rst aid or medical assistance arrives.
RF radiation
WARNING
High RF potentials and electromagnetic elds are present in this equipment when in operation.
Ensure that all transmitters are switched off when any antenna connections have to be changed.
Do not key transmitters connected to unterminated cavities or feeders.
Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to
Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz
CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10 kHz
to 300 GHz).
Laser radiation
WARNING
Do not look directly into bre optic cables or optical data in/out connectors. Laser radiation can come
from either the data in/out connectors or unterminated bre optic cables connected to data in/out
connectors.
Lifting equipment
WARNING
When dismantling heavy assemblies, or removing or replacing equipment, a competent responsible
person must ensure that adequate lifting facilities are available. Where provided, lifting frames must
be used for these operations.
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible
person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be
used for these operations. When equipments have to be manhandled, reference must be made to the
Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation
for the country in which the equipment is used.
Parts substitution
WARNING
Do not install substitute parts or performany unauthorized modication of equipment, because of the
danger of introducing additional hazards. Contact Motorola if in doubt to ensure that safety features
are maintained.
Battery supplies
WARNING
Do not wear earth straps when working with standby battery supplies.
2006 Motorola, Inc.
7
June 2007
Version 1 Rev 3 General warnings
General warnings
Lithium batteries
WARNING
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithium batteries must
not be removed or replaced. Any boards containing defective lithium batteries must be returned to
Motorola for repair.
Contact your local Motorola ofce for how to return defective lithium batteries.
Protective Equipment Recommendations
Feet and Legs
In environments that may include electrostatic build-up, wet slippery surfaces, chemical splashes or
abrasives, it is recommended that safety shoes or boots with protective toe caps and penetration-resistant
mid-soles are worn.
Hands and Arms
In environments that may endure temperature extremes, risks of cuts and punctures to the skin, disease
or contamination from chemical substances, electrical shocks or skin infections, it is recommended that
suitable gloves, gauntlets, mitts, wristcuffs or armlets are worn.
Breathing
In environments that may exude dust, vapour, gas or be an oxygen-decient atmosphere, it is
recommended that suitable apparatus is worn (disposable ltering facepiece or respirator, half-or
full-face respirator, air-fed helmets or breathing apparatus).
Head Protection
In environments where there is risk from falling or ying objects, hair entanglement or head bumping, it
is recommended that a safety helmet is worn and long hair kept in some form of restraint.
Eyes
In environments where the eyes are at risk of metal splash, dust, projectiles, gas and vapour radiation,
it is recommended that safety spectacles, goggles, visors, or faceshields are worn.
Body
In environments that are at risk from chemical or metal splash, spray from pressure leaks or spray
guns, impact or penetration, contaminated dust, excessive wear or entanglement of own clothing, it
is recommended that conventional or disposable overalls or other specialist protective clothing is worn.
2006 Motorola, Inc.
June 2007
General cautions Version 1 Rev 3
General cautions
Observe the following cautions during operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these cautions or with specic cautions
elsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes no
liability for the customer's failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels tted to
the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specic cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These
must be observed by all personnel at all times when working with the equipment, as must any other
cautions given in text, on the illustrations and on the equipment.
Fibre optics
CAUTION
Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
CAUTION
Motorola equipment contains CMOS devices. These metal oxide semiconductor (MOS) devices are
susceptible to damage from electrostatic charge. See the section Devices sensitive to static in the
preface of this manual for further information.
2006 Motorola, Inc.
9
June 2007
Version 1 Rev 3 Devices sensitive to electrostatic discharge (ESD)
Devices sensitive to electrostatic discharge (ESD)
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation that
is susceptible to damage from electrostatic discharge. Such a charge applied to the leads of the device
could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulation
packing material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads shorted together, for
example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam.
Provided the leads are shorted it is safe to handle the device.
Special handling techniques
In the event of one of these devices having to be replaced, observe the following precautions when
handling the replacement:
Always wear an earth strap which must be connected to the electrostatic point (ESP) on the
equipment.
Leave the short circuit on the leads until the last moment. It may be necessary to replace the
conductive foam by a piece of wire to enable the device to be tted.
Do not wear outer clothing made of nylon or similar man made material. A cotton overall is
preferable.
If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic work surfaces
with an anti-static cloth before starting the operation.
All metal tools should be used and when not in use they should be placed on an earthed surface.
Take care when removing components connected to electrostatic sensitive devices. These
components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to
electrostatic damage. However PCBs should be handled with care, preferably by their edges and not
by their tracks and pins, they should be transferred directly from their packing to the equipment (or the
other way around) and never left exposed on the workbench.
2006 Motorola, Inc.
June 2007
Network Conguration Review Version 1 Rev 3
Chapter 1
Network Conguration Review
2006 Motorola, Inc.
1-1
June 2007
Version 1 Rev 3 Network Conguration Review
1-2 SYS02: Introduction to BSS Database GSR9
2006 Motorola, Inc.
June 2007
Objectives Version 1 Rev 3
Objectives
On completion of this chapter the student will be able to:
Network conguration review
1. Describe the various components that make up the GSM network
Hardware review
1. Describe the component parts of the BSU
2. Describe the component parts of the RXCDR
3. Describe the component parts of an In-Cell BTS
4. Describe the component parts of a M-Cell BTS
5. Describe the component parts of Horizon BTSs
Software review
1. Describe the software architecture of the BSS
2. Describe the download and initialisation process of the BSS
3. Describe how the BSS database is stored, amended and controlled throughout the BSS
4. Describe the role of the processes that make up the Radio Subsystem software (RSS)
User Security Management
1. Describe the Login and Authentication sequence at the BSS
2006 Motorola, Inc.
1-3
June 2007
Version 1 Rev 3 Network Conguration Review
The following is a listing with a brief explanation of the major system components of the GSM System.
Mobile Station (MS)
The radio equipment and man-machine interface that a subscriber needs to access PLMN services.
Base Station System (BSS)
The xed end of the radio interface that provides control and radio coverage functions for one or more
sites and their associated mobile stations. The BSS includes:
Base Transceiver Station (BTS) - The BTS cabinet is capable of operating as a self contained BTS with
the option of supporting up to 24 carriers over a number of hardware platforms that will be described in
later sections.
Base Station Controller (BSC) - The BSC cabinet is only used at BSC sites and provides the required
expansion capabilities to interface to the maximum number of remote BTS's allowed by the Motorola
GSM BSS offering. The BSC can be a cabinet to itself or as a function at other cabinets. The BSC is
discussed in greater detail later in this course.
Transcoder Function (XCDR) - Converts the signal from 64kbs A-law to 13kbit/s GSM speech.
Network Switching System (NSS)
Mobile Switching Centre (MSC) - The telephone switching exchange for mobile originated or terminated
subscriber trafc.
Authentication Centre (AUC) - Generates and stores authentication parameters for subscriber
identication.
Equipment Identity Register (EIR) - The data base oriented processing network entity that contains
centralized data base information for validating mobile stations based on their international mobile
equipment identity.
Visitor Location Register (VLR) - The database oriented processing network entity that temporarily
contains information for subscribers roaming in a given location area.
Home Location Register (HLR) - The database oriented processing network entity that contains the
master data base of the subscribers to a PLMN.
Echo Canceller (EC) - Performs echo suppression for all voice circuits.
Interworking Function (IWF) - Performs data rate adaptation between Public Land Mobile Network
(PLMN) and other existing land networks.
Operations and Maintenance Centre (OMC) - A central network entity that controls and monitors other
network entities, including the quality of service provided by the network. Two OMCs are used, OMC-R
for the BSS monitoring and OMC-S for MSC monitoring.
Network Management Centre (NMC) - Performs hierarchical regionalized network management of the
complete GSM system.
2006 Motorola, Inc.
June 2007
Network Conguration Review Version 1 Rev 3
PSTN
AUC HLR IWF EIR EC
MSC
VLR
OMC-S
NMC
OMC-R
MSC
VLR
XCDR
BSC
BSS
BTS
BTS
XCDR
BSC
BTS BTS
BSS
NSS
NMS
XCDR
BSC
BSS
BTS
BTS
2006 Motorola, Inc.
1-5
June 2007
Version 1 Rev 3 Hardware Review
Hardware Review
Base Station Unit (BSU) Shelf
Base Station Unit Shelf Assembly
A Base Station Unit (BSU) shelf assembly consists of:
A backplane.
Two vertical-slot module shelves containing the required digital modules:
The upper shelf holds half size digital modules.
The lower shelf holds full size digital modules.
A three-compartment shelf for the power supply modules.
Every cabinet must be tted with the following digital cards:
Two Bus Termination Cards (BTC).
One Local Area Network Extender (LANX) module.
Base Station Unit (BSU)
Max number of full size boards - contained within in BSU.
2 x Kiloport Switch (KSW) or 2x Double Kiloport Switch (DSW2)
12 x Multiport Serial Interface (MSI)
2 x Generic Clock (GCLK)
8 x Generic Processor (GPROC2/3)
6 x Generic DSP Processor (GDP2)
2 x Bus Terminator Card (BTC)
Max number of half size boards - contained within in BSU.
18 x Kiloport Switch Extender (KSWX) or 18x Double Kiloport Switch Extender (DSWX)
6 x Clock Extender (CLKX)
2 x Local Area Network Extender (LANX)
2 x Parallel Interface Extender (PIX)
BSU shelf diagrams
This diagram shows the BSU shelf slot assignment and backplane connectors:
BSU backplane connectors
AI0 and AI1 are 10-pin headers.
AI2 is a 4-pin power connector to the backup supply (BBBX). NOT used
KS0 and KS1 are 20-pin headers and provide TTY access to serial ports for KSW/TSW boards.
DR0 to DR5 are 20-pin headers and provide TTY access to serial ports for DRI/MSI boards NOT
used.
GK0 is a 9-pin D-type and provides a GCLK synchronization input.
MS0 to MS3 are 37-pin D-types for connecting E1/T1 circuits.
2006 Motorola, Inc.
June 2007
Hardware Review Version 1 Rev 3
Hardware Review
B
T
C

0
B
T
C

1
G
P
R
O
C

6
G
P
R
O
C

7
K
S
W
/
D
S
W
2
A
G
C
L
K

B
G
C
L
K

A
P
I
X

0
K
S
W
/
D
S
W
2

B
G
P
R
O
C

5
G
D
P
/
G
D
P
2

1
R
M
T
K
S
W
X

A
4
R
M
T
K
S
W
X

A
3
R
M
T
K
S
W
X

A
2
R
M
T
K
S
W
X

A
1
R
M
T
K
S
W
X

A
0
K
S
W
X

A
2
K
S
W
X

A
1
K
S
W
X

A
0
E
X
P
E
X
P
E
X
P
L
A
N
X

A
L
A
N
X

B
K
S
W
X

B
0
K
S
W
X

B
1
E
X
P
E
X
P
K
S
W
X

B
2
E
X
P
R
M
T
K
S
W
X

B
0
R
M
T
K
S
W
X

B
1
R
M
T
K
S
W
X

B
2
N
V
W
G
P
R
O
C

3
G
P
R
O
C

4
G
P
R
O
C

2
G
P
R
O
C

1
G
P
R
O
C

0
M
S
I

0
M
S
I

1
M
S
I

2
M
S
I

3
M
S
I

4
M
S
I

5
M
S
I

6
M
S
I

7
M
S
I

8
M
S
I

9
M
S
I

1
0
M
S
I

1
1
C
L
K
X

B
0
C
L
K
X

B
1
C
L
K
X

A
0
C
L
K
X

A
1
C
L
K
X

A
2
C
L
K
X

B
2
R
M
T
K
S
W
X

B
3
R
M
T
K
S
W
X

B
4
K
S
W
X

A
K
S
W
X

B
L
C
L
L
C
L
U0 U1 U2 U3 U4 U5 U6 U7 U8 U9 U10 U11 U12 U13 U14 U15 U16 U17 U18 U19 U20 U21 U22 U23 U24 U25 U26 U27 U28
L0 L1 L3 L5 L6 L7 L8 L9 L10 L11 L12 L13 L14 L15 L16 L17 L18 L19 L20 L21 L22 L23 L24 L25 L26 L27 L28
KS0 KS1 AI0
AI1
AI2
MS0
GK0
DR5 DR4 DR3 DR2 DR1 DR0
MS1 MS2 MS3
P
I
X

1
S
P
A
R
E
S
P
A
R
E
G
D
P
/
G
D
P
2

5
G
D
P
/
G
D
P
2

4
G
D
P
/
G
D
P
2

3
G
D
P
/
G
D
P
2

2
G
D
P
/
G
D
P
2

9
G
D
P
/
G
D
P
2

8
G
D
P
/
G
D
P
2

7
G
D
P
/
G
D
P
2

6
G
D
P
/
G
D
P
2

1
2
G
D
P
/
G
D
P
2

1
1
G
D
P
/
G
D
P
2

1
0
2006 Motorola, Inc.
1-7
June 2007
Hardware Review
Remote Transcoder Unit (RXU3) Shelf
Remote Transcoder Unit Shelf Assembly
A Remote Transcoder Unit (RXU3) shelf assembly consists of:
A backplane.
Two vertical-slot module shelves containing the required digital modules:
The upper shelf holds half size digital modules.
The lower shelf holds full size digital modules.
A three-compartment shelf for the power supply modules.
Every cabinet must be tted with:
Two Bus Termination Cards (BTC).
One Local Area Network eXtender (LANX) module.
Remote Transcoder Unit (RXU3)
Max number of full-size boards - contained within the RXU3.
2 x Kiloport Switch (KSW) or 2x Double Kiloport Switch (DSW2)
5 x Multiport Serial Interface (MSI)
2 x Generic Clock (GCLK)
2 x Generic Processor (GPROC2/3)
19 x Generic DSP Processor (GDP2)
2 x Bus Terminator Card (BTC)
Max number of half-size boards - contained within the RXU3.
18 x Kiloport Switch Extender (KSWX) or 18x Double Kiloport Switch Extender (DWSX)
6 x Clock Extender (CLKX)
2 x Local Area Network Extender (LANX)
2 x Parallel Interface Extender (PIX)
Backplane Conections
AI0 and AI1 are 10-pin headers.
AI2 is a 4-pin power connector to the backup supply (BBBX). (No longer supported)
KS0 and KS1 provide TTY access to serial ports for KSWs/DSW2s.
MS0 to MS6 are 37-pin D-types for connecting E1/T1 lines.
2006 Motorola, Inc.
June 2007
Hardware Review
B
T
C

0
B
T
C

1
K
S
W

A

/

D
S
W
2
A
G
C
L
K

B
G
C
L
K

A
P
I
X

0
K
S
W

B

/

D
S
W
2

B
G
D
P
/
G
D
P
2

0
R
M
T
K
S
W
X

A
4
R
M
T
K
S
W
X

A
3
R
M
T
K
S
W
X

A
2
R
M
T
K
S
W
X

A
1
R
M
T
K
S
W
X

A
0
K
S
W
X

A
2
K
S
W
X

A
1
K
S
W
X

A
0
E
X
P
E
X
P
E
X
P
L
A
N
X

A
L
A
N
X

B
K
S
W
X

B
0
K
S
W
X

B
1
E
X
P
E
X
P
K
S
W
X

B
2
E
X
P
R
M
T
K
S
W
X

B
0
R
M
T
K
S
W
X

B
1
R
M
T
K
S
W
X

B
2
G
P
R
O
C

1
G
P
R
O
C

0
M
S
I

0
M
S
I

1
M
S
I

2
M
S
I

3
M
S
I

4
C
L
K
X

B
0
C
L
K
X

B
1
C
L
K
X

A
0
C
L
K
X

A
1
C
L
K
X

A
2
C
L
K
X

B
2
R
M
T
K
S
W
X

B
3
R
M
T
K
S
W
X

B
4
K
S
W
X

A
K
S
W
X

B
L
C
L
L
C
L
U0 U1 U2 U3 U4 U5 U6 U7 U8 U9 U10 U11 U12 U13 U14 U15 U16 U17 U18 U19 U20 U21 U22 U23 U24 U25 U26 U27 U28
KS0 AI0
AI1
MS0 MS1 MS2 MS3
P
I
X

1
AI2
S
P
A
R
E
KS1
S
P
A
R
E
MS4 MS5 MS6
G
D
P
/
G
D
P
2

1
G
D
P
/
G
D
P
2

5
G
D
P
/
G
D
P
2

4
G
D
P
/
G
D
P
2

3
G
D
P
/
G
D
P
2

2
G
D
P
/
G
D
P
2

1
2
G
D
P
/
G
D
P
2

1
1
G
D
P
/
G
D
P
2

1
0
G
D
P
/
G
D
P
2

9
G
D
P
/
G
D
P
2

8
G
D
P
/
G
D
P
2

7
G
D
P
/
G
D
P
2

6
G
D
P
/
G
D
P
2

1
8
G
D
P
/
G
D
P
2

1
7
G
D
P
/
G
D
P
2

1
6
G
D
P
/
G
D
P
2

1
5
G
D
P
/
G
D
P
2

1
4
G
D
P
/
G
D
P
2

1
3
2006 Motorola, Inc.
1-9
June 2007
Hardware Review
1st Generation BTS - InCell Cabinet ( BTS 4/5/6)
Overview
The Base Transceiver Station (BTS) provides the gateway between the mobile stations and the cellular
network. There are three versions of the InCell BTS, the BTS4, BTS5 and BTS6, the main difference
between the versions are the number of transceivers, which is denoted by the number.
External features
The cabinet door is hinged on the left side of the cabinet, and has four air vents with grilles:
Intake vents have air lters.
Exhaust vents have exhaust fans tted behind the vents.
All connections to a cabinet are at the interconnect panel, which is on top of the cabinet. This panel also
has feed-through tubes for routeing bre optic inter-cabinet cables in and out of the cabinet. All cabinets
are RF/EMI shielded.
The cabinet has the following dimensions:
Height 2100 mm excluding lifting eyelets
Width 711 mm excluding isolation strips
Depth 416 mm excluding isolation strips
Internal units
As shown, the BTS contains a base station unit (BSU) in a card cage in the lower half of the cabinet.
The BSU is equipped with digital modules according to the required function, and is described in more
detail in Base station unit shelf assembly in this manual.
The upper portion of the cabinet houses RF hardware:
Transceiver shelf.
Transmitter combiners and bandpass lters.
Receiver Front End (RFE).
Transceiver shelf
The transceiver shelf assembly consists of a tray that can mount transceivers. The number of
transceivers that can be tted to a cabinet depends on the cabinet type and the type of transceiver,
generally the number of the cabinet denotes the maximum number of transceivers that can be tted.
For example a BTS6 cabinet can accommodate six transceivers.
Transmit combiner shelf
The transmit combiner shelf is directly above the upper bank of fans. The shelf holds transmit combiners
and bandpass lters. Transmit combiners are discrete hybrid combiners. Transmit RF signals to be
combined inside a BTS cabinet can either come from transceivers within the cabinet or from an external
source, usually a second BTS cabinet.
Receiver front end shelf
The Receiver Front End (RFE) shelf is directly above the transmit combiner shelf. The RFE shelf
contains:
Receiver preselector and eight-way splitter modules.
Dual Path Preselectors (DPPs).
There must be one preselector module for each antenna input.
A shelf can contain up to three DPPs. A DPP module consists of a bandpass lter, a preamplier, and
two eight-way splitters. This module allows two antennas to feed up to ve transceivers.
2006 Motorola, Inc.
June 2007
Hardware Review
Power Distribution Unit (PDU)
The cabinet PDU is in the top shelf and contains circuit breakers and fuses and distributes power in the
cabinet.
Fan cooling system
The lower bank of fans draws air downward fromthe upper intake, through the RFE shelf and the transmit
combiner shelf, then through a channel behind the transceiver shelf, and down through the BSU shelf.
Blanking panels are installed in the front of empty slots to maintain the correct airow.
The upper bank of fans draws air from below the transceiver shelf through openings in the tray, the
transceiver and the deectors. Blanking plates are installed to close the openings in the tray when the
transceiver slot is empty, to prevent air from owing through empty slots.
INTERCONNECT PANEL
CIRCUIT BREAKER PANEL
BSU SHELF
BLANKING PLATE
POWER AND ALARM BOARD
RECEIVE FRONT END SHELF
POWER
SUPPLY
MODULE
TRANSCEIVER
TRANSMIT
COMBINER
SHELF
TRANSCEIVER SHELF
FANS
FANS
POWER AND DISTRIBUTION
UNIT
2006 Motorola, Inc.
1-11
June 2007
Hardware Review
2nd Generation BTS - MCell Cabinet ( MCell2/6)
Overview
The cabinet has two variants:
Outdoor.
Indoor.
A BTS consists of:
Radio equipment in the radio system, which provides the air interface.
Digital equipment to control the radio system.
Equipment
The M-Cell6 cabinet is equipped with:
Up to two micro base control units (BCUs), located in the lower portion of the cabinet.
In the indoor ac version, an 88 to 264 V AC Power Interface Module (ACPIM) and an AC Power
Supply Module (ACPM).
A PDU located between the BCUs in the lower portion of the cabinet.
Up to six transceiver control units (TCUs), located above the BCUs and PDU in the cabinet.
An alarm board (AB6), located above the TCU cage in the cabinet.
The top panel contains the RF coupling equipment.
There is also provision for:
Mounting a Global Positioning Satellite (GPS) module.
M-Cell6 cabinets operating from either an isolated positive earth (-48 V/-60 V dc), negative earth (+27 V
dc), nominal 230 V ac single phase or 415 V ac three phase supply are described in this chapter.
External cabinets are equipped with a Heat Management System (HMS), which may use either a heat
exchanger or air conditioner.
2006 Motorola, Inc.
June 2007
Hardware Review
TOP PANEL
POWER DISTRIBUTION UNIT
(PDU)
BCU 0 CAGE
BLANKING
PLATE or
REDUNDANT
POWER SUPPLY
ALARM BOARD
(AB 6)
TCU 2
TCU 3
DC POWER INPUT TERMINALS
TRANSCEIVER CONTROL UNIT
(TCU) 0 (not visible)
TCU 1
TCU 4
TCU 5
REDUNDANT
BCU 1 CAGE
COOLING FANS
POSITIVE OR NEGATIVE
POWER SUPPLY MODULE
(P/NPSM) 1
P/NPSM 0
RECEIVE/TRANSMIT EQUIPMENT
BLANKING PLATE OR
IADU
2006 Motorola, Inc.
1-13
June 2007
Hardware Review
3rd Generation BTS - Horizonmacro Cabinet
Horizonmacro Indoor Cabinet
The BTS cabinet consists of a main cage and a top panel.
The main cage contains the following equipment:
A micro Base Control Unit (BCU), located in the lower right portion of the cabinet. This contains
master and optional redundant digital modules:
Fibre Optic Multiplexer (FMUX).
Main Control Unit with dual FMUX (MCUF).
Network Interface Units (NIUs), four in total.
An alarm board (no redundancy option).
One or two (for redundancy) BCU Power Supply Modules (BPSMs).
Up to three Power Supply Modules (PSMs) and one circuit breaker module (CBM) in the upper
right portion of the cabinet. The PSMs are load sharing, with the third PSM providing optional
redundancy.
Up to six Compact Transceiver Units (CTUs), located in the left portion of the cabinet.
Fan modules placed in the bottom of the cabinet, two 2-Fan modulesand one 4-Fan module.
The top panel contains the following equipment:
RF modules, comprising transmit (Tx) blocks, and a receive (Rx) module, the Sectorized Universal
Receiver Front-end (SURF).
Interface panel for customer power and communications connectors.
2006 Motorola, Inc.
June 2007
Hardware Review
CIRCUIT
BREAKER
MODULE (CBM)
RF MODULES
POWER SUPPLY AND
CIRCUIT BREAKER
TEMPERATURE
CONTROL SYSTEM
DIGITAL
MODULES
T43/BIB
MCUF
ALARM BOARD
FMUX/NIU/BPSM
TWO 2-FANS.
ONE 4-FAN.
SIX TRANSCEIVERS
(CTUs)
THREE Tx BLOCKS
(DCFs SHOWN AS
EXAMPLE)
ONE SURF
(Rx)
THREE PSMs
DC POWER IN
AC POWER IN
INTERFACE
PANEL
CONNECTORS
CABINET STRUCTURE
2006 Motorola, Inc.
1-15
June 2007
Hardware Review
Horizon II Macro Cabinet
Cabinet Equipment
The macro cabinet consists of the cabinet frame structure (including door), a main cage with integrated
backplane and a top panel. It contains the following equipment.
Plinth. This secures the cabinet rmly to the oor (or to the stacking bracket in a stacked
conguration).
Fan module (x3). These provide cooling for the cabinet, and especially for the CTU2 transceivers
and digital modules mounted directly above.
Power Supply Unit (PSU). The PSUs are load sharing. In a fully equipped cabinet, a fourth PSU
provides 3 + 1 redundancy. An optional hold-up battery module (under development) may be tted
to ac supply BTS variants instead of the fourth PSU. The PSUs contain integral cooling fans.
Circuit Breaker Card (CBC). The CBCprovides circuit protection and the facility to manually isolate
individual modules within the macro cabinet.
Alarm module. This handles all cabinet alarm I/O signals and provides current sensing for external
site alarms (via the PIX connectors).
Power Distribution Assembly (PDA). Mounted on the left side of the top panel assembly.
Provides the connectors for ac or dc power input. Also contains the interface panel for customer
communications connectors.
Site Controller Card (HIISC). Provides the site processing functions for the BTS. This includes an
integrated XMUX and NIU. Provision is made for an additional HIISC to be tted, if redundancy is
required.
EXpansion MUltipleXer module (XMUX). An optional module that replaces the site controller
unit in an expansion (slave) cabinet to provide multiplexer connections to the master cabinet. An
additional XMUX can be installed if redundancy is required.
Site expansion board (I/O). An optional module that is mounted in the right side of the top panel
assembly. Provides bre optic connections to expansion cabinets. An additional site expansion
board can be installed if redundancy is required.
Compact Transceiver Unit (CTU2). Provides amplication and signal conditioning for outgoing
(Tx) signals and receives Rx signals from the SURF2. The CTU2 provides 2 x GSM/ GPRS and
1 x EDGE capability. It is backwards compatible with the Horizonmacro CTU (with BBH limitations
in double density form). Up to six CTU2s may be tted in the cabinet to provide 12 GSM/GPRS
carriers (double density).
Sectorized Universal Receiver Front End (SURF2) module. Mounted at the rear of the top panel
assembly. Provides amplication and signal conditioning functions for incoming (Rx) signals. One
or two SURF2s may be tted to provide 2 or 4 branch receive diversity.
Tx blocks. Up to six Tx blocks can be tted in the basket in the top panel. There are three types of
Tx block available for the macro: DUPlexer (DUP), Hybrid Combiner Unit (HCU) and Dual Hybrid
combiner Unit (DHU).
2006 Motorola, Inc.
June 2007
Hardware Review
CIRCUIT BREAKER
CARD (CBC)
TWO HIISCs
(REPLACED BY XMUXs IN
EXPANSION CABINET)
ALARM
MODULE
THREE
2-FAN UNITS
SIX CTU2s
SIX Tx
BLOCKS
TWO SURF2s
OPTIONAL HOLD-UP
BATTERY MODULE *
REPLACES 4th PSU
(AC CABINETS ONLY)
TWO SITE
EXPANSION
BOARDS
(OPTIONAL)
3 x HEAT
SENSORS
LOCATED ON
BACKPLANE
UP TO FOUR
PSUs
PLINTH
POWER SUPPLY
CONNECTORS
INTERFACE PANEL
CONNECTORS
BIM/BIB OR
CIM/T43
2006 Motorola, Inc.
1-17
June 2007
Hardware Review
Horizon II Mini Enclosure
The Horizon II mini indoor enclosure consists of the cabinet frame structure (including door), a main cage
integrated midplane and a back panel. It contains the following equipment:
Power supply unit (PSU). The PSU provides a regulated bus voltage converted from the primary
power applied. The PSU contains an integral cooling fan.
Mini circuit breaker module (MCBM). The MCBM provides circuit protection and the facility to
manually isolate individual modules within the Horizon II mini enclosure.
Fan modules. These provide cooling for the enclosure, especially for the CTU2 transceivers and
digital modules mounted directly above.
Compact transceiver unit (CTU2). Provides amplication and signal conditioning for downlink (Tx)
signals and receives uplink signals from the Mini-SURF. Up to two CTU2s may be tted in the
Horizon II mini enclosure to provide four GSM/GPRS carriers (double density).
Alarm module. This handles all enclosure alarm I/O signals and provides current sensing for
external site alarms (via the PIX connectors).
Site controller unit (HIISC). Provides the site processing functions for the BTS (equivalent to the
MCUF in Horizonmacro). Includes an integrated XMUX and NIU. Provision is made for an additional
HIISC to be tted, if redundancy is required.
Expansion multiplexer module (XMUX). An optional module that replaces the site controller unit in
an expansion (slave) enclosure to provide multiplexer connections to the master enclosure. An
additional XMUX can be installed if redundancy is required.
Line interface unit. (T43 or BIB type.) This provides the interface for external network backhaul
connections, along with line isolation and impedance matching.
Miniature sectorized universal receiver front end (Mini-SURF) module. Mounted at the mid left rear
of the assembly. Provides amplication, switching and signal conditioning functions for incoming
(Rx) signals.
Optional battery backup unit. Mounted at the mid centre rear of the assembly. Provides short term
battery backup in the event of power supply failure.
Back panel connectors. Located at the rear right of the assembly. Provides connectors for:
External power supplies, a.c. and d.c Although terminals are provided for a.c. and d.c. external
power supplies, a cabinet will be equipped with power supply units for a.c. power input or with
power supply units for d.c. power input. An enclosure congured for one type of power input cannot
be used with the other.
External alarms, used by outdoor enclosure. For indoor use the external alarms connector is tted
with a shorting plug. If this is removed in an indoor site, the BTS will become non-operational.
Fitting the Horizon II mini indoor with the optional battery module requires the replacement of the
external alarms shorting plug for the one supplied with the battery module.
2006 Motorola, Inc.
June 2007
Hardware Review
2006 Motorola, Inc.
1-19
June 2007
Hardware Review
PIX connector for customer-specic alarms and/or equipment.
Tx blocks: There are two types of Tx block available for the Horizon II mini: duplexer (DUP) and
hybrid combiner (CMB), (used in bow tie conguration only).
Up to two DUPs can be tted in the shelf in the back panel. The DUP allows Rx and Tx signals to
share an antenna and also provides ltering and VSWR monitoring.
A single CMB can be attached to the front of the Horizon II mini using a bracket secured by one M4
captive fastener. The CMB allows two CTU2 Tx signals shared use of antennas.
Site expansion board. An optional module mounted in the right side at the top rear of the indoor
cabinet. Provides bre optic connections to expansion cabinets. An additional site expansion board
can be installed if redundancy is required.
Auxiliary power supply module (AuxPSM). This optional module provides 48 V d.c. to power
customer equipment.
2006 Motorola, Inc.
June 2007
Hardware Review
2006 Motorola, Inc.
1-21
June 2007
Hardware Review
Horizon II Micro Enclosure
The equipped enclosure is shown. The enclosure is designed for minimum maintenance and maximum
ease of module replacement, and has access only from the front.
The Horizon II micro structure components are:
Horizon II micro internal structure and harnesses
Interface panel and cable entry box
Enclosure temperature control
Fan units (internal and external)
Enclosure doors
Mounting Options
The Horizon II micro internal structure provides a platform for module installation and power and digital
signal interconnection to enclosure modules. The internal structural components comprise:
The main cage providing compartments for internal fans, the CTU2, digital modules, the climate
control unit circuit board and the PSU.
The secondary cage providing compartments for: the mini-SURF, the DUPs, the site expansion
board and the optional backup battery.
The midplane and internal harnesses - routes power and signals to all modules and power to the
Mini-SURF.
The cable entry box - contains the line interface unit, either T43 or BIB and allows the connection
of other communications connectors, (PIX alarms and site expansion bre optics).
The Interface panel - houses power and earth connectors and communications cable glands.
2006 Motorola, Inc.
June 2007
Hardware Review
2006 Motorola, Inc.
1-23
June 2007
Hardware Review
Midplane Function
The midplane and internal harnesses are permanently xed to the external enclosure body at the factory
and cannot be removed in the course of normal maintenance or FRU replacement procedures.
All possible RF and digital module combinations are served by the same midplane. The only
module-to-module cabling required is the Tx cabling from the CTU2 to the Tx block and the Mini-SURF
to the TX block. Any external attachments will require separate cabling.
The midplane is a multi layered printed circuit board with attached connectors on front and back;
this construction maintains controlled impedance and screening for high speed signal lines. The
midplane uses partial planes for power circuits to meet conductor separation requirements and minimize
electromagnetic interference (EMI).
Routes power and digital signals throughout the enclosure.
Provides connectors for hot swap capable plug in modules, including Horizon II mini battery module.
Provides power to the Mini-SURF harness.
Provides connectors for the heat sensors in the enclosure above the CTU2.
RF connections are not made through the midplane, but are separately cabled. All FRUs connected to
the midplane, are hot swap capable. The midplane is not user replaceable and is supplied as part of the
enclosure assembly.
Internal harness function
The harnesses provides cables to link connectors on the midplane with internal equipment. The internal
harnesses are tted to the enclosure at the factory and are not intended to be removed in the course of
normal maintenance or FRU replacement procedures.
Mini-SURF harness
The Mini-SURF harness connects between the Mini-SURF chassis and the CTU2 connector tted on the
midplane of the enclosure. The Mini-SURF chassis supports the Mini-SURF modules. The Mini-SURF
harness provides, one connector to the Mini-SURF for RF and power. one RF connector to the CTU2,
consisting of two inputs, one each for Rx A and Rx B.
2006 Motorola, Inc.
June 2007
Hardware Review
2006 Motorola, Inc.
1-25
June 2007
Version 1 Rev 3 Software Review
Software Review
The BSS software is made up of a number of different les called code objects.
These les are downloaded into a site by various means.
All the processors resident in a cabinet receive all the downloaded code object les, which are stored in
the RAM memory.
Each code object le has the capability of becoming a system application process, but with certain
exceptions - the rst being the database, the second is the executive, and the third being the object
list.
The applications created on individual processors is decided by the fault management software during
the initialisation of the site.
2006 Motorola, Inc.
June 2007
Software Review Version 1 Rev 3
Software Review
SYS02_Ch1_11
Code object files
Code object files
can become a
system process
All processors at the same site are downloaded
with all code object files
2006 Motorola, Inc.
1-27
June 2007
Version 1 Rev 3 BSC Initialisation Process
BSC Initialisation Process
The BSC executive process is responsible for starting the initialisation of the GPROC, using the
initialisation process (IP), which is stored on Flash eprom.
1. The GPROC starts off in the ROM exec monitor mode. In this mode the IP has no database to work
with. Therefore it works with default values written into the IP. At this stage the master GPROC may
or may not have code, this will be determined by checking the object list if available.
2. The IP rst initialises the LAN, so that any GPROCs may talk to one another. On LAN initialisation,
the GPROC audits the LAN to ascertain how many GPROCs there are on the LAN.
3. The IP then decides which GPROC is to become the master. (The master GPROC is normally a
GPROC in the slot dened in the IP)
4. The IP then tests KSWs/DSW2s, MSI, and XCDR/GDP/GDP2 boards which are dened in the IP.
5. Then the IP must determine whether any code exists on the ANY GPROC. A number of scenarios
may now take place.
If no code exists on the Master GPROC, or any of the other GPROCs then the system will
check to see if an NVRAM card has been tted. If it has, and it has code available this code will
be down loaded to the master GPROCs provided it is the same as the code held at he OMC-R.
This is determined once the object list that is received from the OMC-R is compared against
the stored object list.
If code exists on a GPROC which is not the master, the Master GPROC will arrange to load all
other GPROCs from that code source, provided the code is the same as the code held at the
OMC-R. This is determined once the object list that is received from the OMC-R is compared
against the stored object list.
If no code exist at all, the system must wait for connection to the OMC-R, which could take up
to 6 minutes. Once connection has been established the code will then be down loaded as
normal, and the initialisation will continue.
6. When the Master GPROC has received all the required code, the IP on the Master GPROC will
cross-load all the other GPROCs on the LAN.
7. Once the Master GPROC has received conrmation from the other GPROCs that the cross-load
has been successful, a message is broadcast to all GPROCs to go to RAM exec monitor.
2006 Motorola, Inc.
June 2007
BSC Initialisation Process Version 1 Rev 3
BSC Initialisation Process
Reboot
Establish LAN
Bring GPROCs
On to LAN
Select Master
Has any
GPROC any
Code objects?
Check NVM
Board for code
X-load code
Check
if there is
enough
equipment for
a download
of code
Connect
to OMC
within
6 mins
Is there
Any Valid
Code
Available?
Is a
Download
Required?
Broadcast to
all GPROCs
Broadcast to
all GPROCs
Complete
Download
Jump
to
RAM
Initialization Process in ROM
Fail
No
Yes
Yes
No
No
Yes
No
Yes
Yes
No
Reboot
Establish LAN
Bring GPROCs
On to LAN
Select Master
Has any
GPROC any
Code objects?
Check NVM
Board for code
X-load code
Check
if there is
enough
equipment for
a download
of code
Connect
to OMC
within
6 mins
Is there
Any Valid
Code
Available?
Is a
Download
Required?
Broadcast to
all GPROCs
Broadcast to
all GPROCs
Complete
Download
Jump
to
RAM
Initialization Process in ROM
Fail
No
Yes
Yes
No
No
Yes
No
Yes
Yes
No
2006 Motorola, Inc.
1-29
June 2007
Version 1 Rev 3 Initialisation Process
Initialisation Process
Once in RAM the rst check that is made is for a valid database, this is carried out by calculating a
checksum based on the stored database and comparing this against the stored checksum. Although
apparently correct, there may be level number differences which will cause the download of a new
database.
Now in RAM the IP once again initialises the LAN, because when moving from ROM EMON to RAM
EMON the LAN deactivates.
If no database exists, then the IP waits 45 seconds before rebooting' the site and starting the initialisation
process again.
A system operator has this time period to enter the MMI Command Sysgen on. This tells the IP software
that a database is going to be provided. The IP will re-initialise the site and go through the IP from the
start, but will stop at this point. The system operator can then provide a database. Once the database
has been provided, the operator uses another MMI command, Sysgen off, and the master GPROC will
then cross-load this new database to each GPROC on the LAN.
On completion of database cross loading to all GPROCs, the IP initiates the Central Authority (CA)
process. When this happens it is the CA process that now looks after the initialisation of the site. The IP
performs one more task if the site is a BSC - it helps the Central Authority to bring up' the remote BTS.
The CA informs each BTS site its site number then each BTS is downloaded by the BSC. The database
contains information relating to the entire BSS and is downloaded in its entirety.
Each BTS site will follow a similar IP, however these will differ between In-Cell and M-Cell/Horizon. The
major exception being that unlike the BSC, a BTS has to set up its signalling link to the BSC and not the
OMC-R. This link is called the Radio Signalling Link (RSL) and used for the download process.
Once the BTS has been downloaded from the BSC including the BSS database it will activate that part
of database relevant to it.
2006 Motorola, Inc.
June 2007
Initialisation Process Version 1 Rev 3
Initialisation Process
RAM
Re-establish LAN
Does
A valid
Database
Exist?
Do all
GPROCs in
DB have
A copy?
BSP/Redundant
Purge all
New Gen
BTS objects
Inform User a
Sysgen required
Has
Sysgen Mode
been started
within
45 seconds
Reset Site
To create CM
Reboot
Load to all
GPROCs in DB
Sysgen
Mode
Is
Database
Valid?
Initialize CA
Continue
Boot-up
No
Yes
Yes
No
No
Yes
Yes
No
2006 Motorola, Inc.
1-31
June 2007
Version 1 Rev 3 BSS Reset Management
BSS Reset Management
Introduction
Up to and including GRS7 a failure in the master BSP will cause the whole BSC has to go through a
reset. This mechanism has following shortcomings from customer viewpoint:
If the master BSP fails, depending on the conguration of the BSS, the reset for the whole BSC will
take an outage somewhere between 10 to 20 minutes.
There is little diagnostic information to assist in the analyzing the root cause of the BSP failure.
The BSC can not preserve the states of all devices and function units. Thus, network operators
have to individually relock all the devices that were locked prior to the reset.
All alarm history prior to the reset is lost.
All stable calls prior to the reset are lost.
The GSR8 BSS reset management feature introduces the capability of swapping between the active
and standby BSP when the master BSP GPROC fails. In addition, the BSP will recover the most useful
information automatically, such as alarms and statistics (type 2 bss only) instead of manual restoration
by network operators. Finally, more diagnostic data will be collected for analysis by development and
customer support teams.
After switchover, the BSS will initiate a global reset to ensure that the MSC/RXCDR/BSC/BTS network
elements become status synchronized. With respect to GPRS service, the BSS will obtain status
synchronization with the PCU by disabling and re-enabling all the GSLs in service. In all cases, this will
lead to all the established calls (data and voice) dropping off.
Global Reset
Global Reset is a procedure which can be initiated by MSC or BSC, that initializes the MSC and BSC
after a failure that results in the loss of normal call information. The procedure causes the MSC to
release the affected calls and erase all the affected references, and to put all associated circuits into idle
state. Meanwhile the procedure causes the BSS to clear all call information and call references. Within
the BSS, the BSC and the associated RXCDRs and BTSs will be involved in the procedure to release
resource allocated to calls at BSC, RXCDRs and BTSs respectively.
When a global reset is performed at BSS, it does not mean that all the hardware components in the BSS
are reset. As a result, this action will only clear the affected calls and release the associated resources.
2006 Motorola, Inc.
June 2007
BSS Reset Management Version 1 Rev 3
Disadvantages of current BSC reset procedure
Prolonged outage time of up to 20 minutes
Loss of device and function states
Loss of alarm history
Loss of statistic
Loss of stable calls
Loss of GPRS sessions
Disadvantages of current BSC reset procedure
Prolonged outage time of up to 20 minutes
Loss of device and function states
Loss of alarm history
Loss of statistic
Loss of stable calls
Loss of GPRS sessions
Advantages
Reduce outage time
Preservation of device and function states
Preservation of alarm history
Preservation of statistic (type 2 BSS only)
ages
Reduce outage time
Preservation of device and function states
Preservation of alarm history
Preservation of statistic (type 2 BSS only)
2006 Motorola, Inc.
1-33
June 2007
Version 1 Rev 3 BSS Reset Management
Impacts
BSS
The stable calls, both voice and data that were established prior to the BSP switchover will be dropped.
The statistics that were collected prior to the BSP switchover by the master BSP will be lost. If the BSS is
a type 1, the BSS will fail to collect statistics during BSP switchover process. In addition it will also provide
the capability of reserving device, function unit states and alarm history prior to the BSP switchover. If
the switch over occurs in ROM, the master BSP will toggle between the card in slot 20 and slot 24, for
every switchover that occurs and not continually choose the card in slot 20 as master. This aspect has
been introduced as a solution to PR159011, which was raised as a result of having to pull out the BSP
(Slot 20) to stop the BSC from rolling in the event of a BSP failure, as slot 20 would always be chosen
as the master. For the feature to function correctly the BSP cards must be of GPROC3 type.
RXCDR (when the BSS is congured with remote transcoders) it includes 2 cases
For a type 1 BSS, the XBL links are managed by the BSP, and thus they will be OOS when the
master BSP fails. The RXCDR connected with this BSS will experience the loss of XBL links to the
BSS during the BSP switchover. After the BSP switchover, the XBL links will be recovered at the
RXCDR, and a global reset will be performed at the RXCDR along with the BSS and BTSs.
For a type 2 BSS, the XBL links are managed by an OMF and they will be maintained during
switchover. After the BSP switchover, the RXCDR will perform a global reset along with the BSS
and BTSs.
BTS
The RSLs are managed by a LCF and they will be maintained during the BSP switchover. After the BSP
switchover, all the associated BTSs will be requested to perform a global reset to clear calls and release
the related resources.
MSC
The MTLs are managed by a LCF and they will be maintained during the BSP switchover. After the BSP
switchover, the associated MSC will be requested to perform a global reset to release the affected calls
and put the associated circuits into idle state.
OMC-R it includes 2 cases
For a type 1 BSS, were the OMLs are managed by the master BSP, they will be OOS when the
master BSP fails. The OMC-R connected to this BSS will experience the loss of these OMLs to
the BSS during the BSP switchover. After the BSC switchover, the OMLs will be recovered at the
OMC-R.
For a type 2 BSS, the OMLs are managed by an OMF and they will be maintained during the BSP
switchover. The OMC-R will therefore not be impacted.
CBC
The CBL is managed by a LCF, so it will be maintained during BSP switchover. However, the BSS will
not send any service request to the CBC during the BSP switchover.
2006 Motorola, Inc.
June 2007
BSS Reset Management Version 1 Rev 3
Impacts
BSS
RXCDR
BTS
MSC
OMC - R
CBC
ts
BSS
RXCDR
BTS
MSC
OMC - R -
CBC
2006 Motorola, Inc.
1-35
June 2007
Version 1 Rev 3 Conguration Management (CM)
Conguration Management (CM)
Overview
The Conguration Management (CM) software is responsible for managing and updating the main
conguration database at either a BSC or a BTS. This is the database that is downloaded as an object
le in the download code. In this database is held all the site parameters such as carrier frequencies,
site conguration, surrounding site information and handover parameters. Also stored in this database
is device functionality and distribution as well as all timing information for the site.
All application processes have access to this database but their access is read only. If the CM database
is required to be changed, the CM process performs this task. This process has both read/write access
to the CM Database.
2006 Motorola, Inc.
June 2007
Conguration Management (CM) Version 1 Rev 3
Conguration Management (CM)
All Other Processes
CM Process
CM
DATABASE
2006 Motorola, Inc.
1-37
June 2007
Version 1 Rev 3 CM Database Distribution
CM Database Distribution
The CM database is distributed across all active GPROCs on any particular LAN. On the LAN, one
GPROC is designated to have the master CM database and hence the CM application process is also
present on this GPROC.
If there are to be any changes to the CM database, the new information is written into the master CM
database via the CM application process. Once the CM database has checked with other system
processes, and is happy that the changes are usable, the master CM database then broadcasts these
changes to all CM databases of all GPROCs on its particular LAN. If the CM process is at the BSC, this
process will also broadcast any changes to each BTS site.
2006 Motorola, Inc.
June 2007
CM Database Distribution Version 1 Rev 3
CM Database Distribution
GPROC
Process A
Process B
Database
Copy
GPROC
CM
Master
Database
GPROC
Database
Copy
Process C
GPROC
Database
Copy
Process Y
Process Z
2006 Motorola, Inc.
1-39
June 2007
Version 1 Rev 3 CM Database and Central Authority Interaction
CM Database and Central Authority Interaction
To Change Site Database
When outside of Sysgen mode any changes that are to be made to the CM database have rst to be
checked and approved by the CA. This is done to ensure that the desired changes are possible given
the state of the devices in the system.
1. Changes to database downloaded to MMI process from the OMC-R.
2. The changes are downloaded to the CM process from the MMI process.
3. The CM process writes the changes into the CM database.
4. The CM process transfers the proposed changes to the CA.
5. The CA replies as to whether the desired changes are possible. (Yes or No).
6. If the CA answers yes', the CM process then broadcasts the changes to all the CM databases of
GPROCs on its site. If the answer is no', the CM process instructs the CM database to erase the
changes.
7. The CM process uploads the outcome of the operation to the MMI process, i.e. changes possible
or not possible.
8. Operation outcome uploaded to the OMC-R.
From the release of GSR3 (1.5.1.0), all database change commands will only be allowed at the BSC. At
times it is necessary to update the database while visiting a site. This can be done using rlogin to set
up a remote login to a GPROC at the BSC from the BTS. This then allows MMI commands to be entered
from the BTS as though from the BSC.
2006 Motorola, Inc.
June 2007
CM Database and Central Authority Interaction Version 1 Rev 3
CM Database and Central Authority Interaction
GPROC
CM
Database
GPROC
CM
Database
GPROC
CM
Database
LAN
MMI
PROCESS
CM
PROCESS
CENTRAL
AUTHORITY
CM
DATABASE
MASTER
FROM
OMC/R
2 1
4
5
3
6
7
8
6
No
Yes/No
Yes
2006 Motorola, Inc.
1-41
June 2007
Version 1 Rev 3 CM Database and CA Interaction
CM Database and CA Interaction
To Change Remote BTS Database
The process for changing elements of the database outside of Sysgen at a remote BTS is basically
similar to the process of changing a single site database.
1. The OMC-R downloads the proposed changes to the BSC MMI process.
2. The BSC MMI downloads the changes to the BSC CM process.
3. The BSC CM process then writes the proposed changes into the BSC master CM database. The BSC
CM process also sends the proposed changes to the BTS CM process.
4. The BTS CM process then writes the changes into the BTS master CM database.
5. The BTS CM process sends the proposed changes to the CA for the BTS site.
6. The CA replies yes or no to changes.
7. The BTS CM process tells the BSC CM Process yes or no as to whether changes possible.
8. If answer from CA is yes, both CM processes now broadcast database changes to all CM databases
on their respective LANs.
9. BSC CM process then tells BSC MMI the outcome of the operation, i.e. whether changes have been
completed or not.
10. BSC MMI uploads the operation outcome up to the OMC-R.
2006 Motorola, Inc.
June 2007
CM Database and CA Interaction Version 1 Rev 3
CM Database and CA Interaction
MMI
PROCESS
CM
PROCESS
BTS
CENTRAL
AUTHORITY
CM
DATABASE
MASTER
FROM
OMC/R
2 1
4
5
3
6
9
8
GPROC
CM
Database
GPROC
CM
Database
GPROC
CM
Database
LAN
BTS
CM
PROCESS
BTS CM
DATABASE
MASTER
GPROC
CM
Database
GPROC
CM
Database
GPROC
CM
Database
LAN
10
7
Abis Link
3
Yes/No
Yes/No
8
2006 Motorola, Inc.
1-43
June 2007
Version 1 Rev 3 Database Level Numbers
Database Level Numbers
Subsequent changes to a database during call processing can be made from the OMC using a number
of input mechanisms, these are TTY, Forms, Batch and Detailed view. In any case the update is sent to
the required entities using the procedure outline in the previous pages.
The whole database for a BSS is stored in every entity of the BSS, the BSC for example will initially have
the same database as each BTS. Subsequent changes during call processing will cause a disparity
between databases held in different entities. If, for example four consecutive changes are made to the
database of BTS 3 using forms at the OMC-R. The level number for BTS 3 at the BSC will be incremented
by four, likewise the level number at BTS 3 will also be incremented by four. Even though the database at
BTS 3 has changed the alterations are not passed on to BTS 1 or 2, they will still have the old database
for BTS 3 in store. Certain changes to a BTS database may be copied to other BTS's, these changes
will be necessary for the correct operation of the handover procedure.
In the example shown opposite, four changes have been made to the database of BTS 3 and one change
has been made to the database of BTS 2. For each change made to an individual site the database level
number is incremented on a site basis, for each change made to a BSS database the level number of
the BSC is incremented.
If these changes are made using TTY, Batch, Forms or Detailed View at the OMC-R the changes are
made in the BSS as discussed but are not copied to the master database held by the OMCR. Hence any
changes made to the BSS database should be followed at some stage with a database upload to renew
the database in the OMC-R. If this procedure is not carried out, upon a BSC reset, the OMC-R could
potentially download an old database not current with any recent changes that have been made. As the
OMC-R is deemed the master entity, the BSC would abandon any database it held and implement the
one being held and subsequently downloaded by the OMC-R.
2006 Motorola, Inc.
June 2007
Database Level Numbers Version 1 Rev 3
Database Level Numbers
TTY
BATCH
FORMS
DETAILED VIEW
LEVEL = 5
BTS 1 = 0
BTS 2 = 1
BTS 3 = 4
LEVEL = 0
BSC
BTS 2
BTS 3
BTS 1
LEVEL = 1
BSC
BTS 1
BTS 3
BTS 2
LEVEL = 4
BSC
BTS 1
BTS 2
BTS 3
OMC-R
BSC
BTS 1 BTS 2 BTS 3
2006 Motorola, Inc.
1-45
June 2007
Version 1 Rev 3 Software Patching
Software Patching
Software Patch - refers to a software change made within a process and applied to each instance of
this process during suspension of that process. It typically replaces an existing function in a process,
in order to resolve a problem or error in the software. Certain software problems can be xed on the
system quickly, without causing any system outage.
Patch level - Corresponds to a patch or group of patches which addresses a single problem or SR.
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.
Patch object - One or more patch levels compiled together into an object. A patch object is identied by
a unique code object number, (i.e. object number 251). As multiple patch objects may be released within
a specic software point release, each patch object therefore must have its respective version number.
A new version of patch object for the same point release is generated accumulatively from the previous
version of the 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.T he 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.
The new element nePatchObjectVer species the version of the patch object which is distributed
throughout the BSC/XCDR. It can be displayed at the OMC-R.
The new element nePatchObjectLev species the patch object level which is distributed throughout
the BSC/XCDR. The actual maximum patch level to be installed is according to the number of patch
levels as specied in the patch object. It can also be displayed at the OMC-R.
2006 Motorola, Inc.
June 2007
Software Patching Version 1 Rev 3
Software Patching
MMI Commands
nePatchObjectVer 0 to 255 Version of 0 indicates that
(Default 0) there is no patch object
included in this point release
nePatchObjectLev 0 to 255 Version of 0 indicates that
there is no patch level
2006 Motorola, Inc.
1-47
June 2007
Version 1 Rev 3 Software Patching
Software Patching
Patch Object Download and Patch Level Application
There maybe cases that only a different version of patch object needs to be downloaded to the BSS and
XCDR, the rest of the code objects of this software point release remain the same. This feature allows
the patch to be downloaded and updated in real-time without a board or network element outage, aiming
towards a timely resolution of the system problem. In a patch object download scenario, there will be no
reset or reboot of the processor. After patch object is downloaded to the system, patches will be applied
to processes that got affected. Processes that are affected by the patch application will be suspended
in order for patch to be applied.
Patches should be independent, i.e. not have interactions within the process or between processes; i.e.
the patch should not rely on changed data structure, message format, interface, etc.
Interfaces that are affected: RSL, MTL, etc Processes/entities that are affected: BTP, LCF, U-DPROC2,
etc Patches cannot be applied to rmware les such as MSI, KSW, PCU NIB companion processors in
RSS modules, NIUs, PSI/MCU,GPROC3-2 PQII.
Patching can be applied to limited code object set:
BSC GPROC: BSC GPROC process objects (68000 based)
PCU: PCU MPROC/DPROC/UDPROC processes (incl. PICP, PRP, PXP, PPROC)
MCELL 2/6: MCU TSM Board (68040 based) on TCU-A (provides RSS) RSS processor (68040
with 68360 in companion mode) on TCU-B
M-Cellaccess, M-Cellmicro, M-Cellcity MCU-m (68LC060) ORAC RSS processor (68LC040)
Horizon Macro/Micro CTU/CTUII MCUF processors
To support download of patches and applying patches to affected processes, the current code download
mechanism will be impacted. Conventional download is used by the operator to download a complete
software load and/or database, the BSS in this case will boot up in ROM. When the software load includes
a patch object, which is identied by a unique code object number just like the rest of the code objects,
the patch object will be downloaded to the BSS and XCDR in the same way as existing code objects.
For CSFP download, code is loaded to a CSFP board. BSC will then codeload the CSFP software load
and then start to propagate respective code objects to BTSs in the system. Only objects that are different
from CSFP load will be downloaded.
The patch level can be changed via a PatchLevelSet action from the OMC. This action will cause the
BSS to broadcast to all network entities, the new patch level. Once each BTS has installed the new patch
level, it will send back to the BSC, the patch level installed, and a status. If installing any of the individual
patch levels up to and including the designated patch level has failed, then the status will indicate failure
and the BSS will back out all patch levels and return to a patch level of 0 (on all BTSs) and will not reinstall
a patch level until a new patch object is downloaded.
Patch levels can be de-installed by the Code Object Manager (COM) from boards which they reside.
The top gure opposite shows the procedure to install only a new patch object and to apply patch levels
to various subsystems. The bottom gure opposite shows alterations needed to current code swap
procedure to support the features. The scenario showed is when OMC acknowledges with a Full BSS
Reset.
2006 Motorola, Inc.
June 2007
Software Patching Version 1 Rev 3
Software Patching
Patch Object Install and Allocation of Patch Level
OMC BSS
PatchLevelSet(CodeVersion, nePatchLevel,nePatchObjectVersion)
Patch Install
BTS
Patch_install_ack
Patch_install_complete
(PatchLevel,Patchstatus)
BSS Present
.
Code Object Download
Complete
Patch Install
IP directs COM to COM
dialog to distribute the
patch object to all network entities
PatchLevelSetResp(Status)
PatchLevelStatusNotification(CodeVersion,nePatchObjectVersion,
nePatchLevel,Patchlevel Status)
2006 Motorola, Inc.
1-49
June 2007
Version 1 Rev 3 BSS Radio Sub System
BSS Radio Sub System
Overview
The Radio Sub System (RSS) is a collection of application processes whose purpose is to manage the
BSS RF hardware and the radio link to the MS. The RSS functions include the Layer 2 interface to the
MS LAPDm and radio link control including the handover detection and power control process.
The RSS portion of the BSS implements the interconnection between the application layer (Layer 3) and
the physical channel hardware (layer 1). Currently one instance of RSS has the messaging capability
to handle six carriers, although an instance of RSS would normally handle Layer 2 control for only
2 or 3 DRIMs, depending on the trafc model in use. In In-cell equipment, RSS runs on single or
multiple GPROCs which must be physically located in the same cage as the DRI board it controls. In
M-Cell/Horizon equipment the RSS is located on the TCU/CTU/CTU2.
The RSS is comprised of ve components:
1. RSS Conguration and Fault Management (CFM)
2. Layer 1 Interface
3. Layer 2 Protocol
4. RSS A-bis interface
5. Handover Detection and Power Control (HDPC)
2006 Motorola, Inc.
June 2007
BSS Radio Sub System Version 1 Rev 3
BSS Radio Sub System
Software interface procedures between BSS RF hardware and MS
One subsystem has the capability to control 6 DRCUs - Incell.
Incell - RSS runs on DHP (GPROC)
M-Cell/Horizon - RSS runs on TCU/CTU/CTU2
2006 Motorola, Inc.
1-51
June 2007
Version 1 Rev 3 BSS Conguration and Fault Management Interface
BSS Conguration and Fault Management Interface
Overview
The CFM process controls the conguration of the related DRCU/TCU/CTU/CTU2, and is the interface
to the BTS fault management system. With regard to conguration, this process is responsible for
informing the hardware as to its conguration, and instructing the particular radio type as to the usage
of each timeslot (e.g. BCCH, SDCCH 8 channel or TCH/FS). The process also has the responsibility of
downloading information to the DRIM board (In-Cell) during the initialisation of the base site, as well as
the loading and conguration of the radio type before call processing is achieved.
The collection of alarm and error messages is also the responsibility of this process. The alarm and error
indications are then forwarded to the Fault Collection Process (FCP) of the GPROC or radio on which
the RSS functionality exists.
Layer 1 Interface
The Layer 1 process translates the message protocol used in the GPROC into the message protocol
used by the DRIM. Also, the addressing used by the higher system layers must be translated into the
actual memory location addressing used by the DRIM. These only apply to In-cell
In addition this process stacks paging messages and access granted messages until the relevant timeslot
appears on the control channels.
Layer 2 Protocol
This process is responsible for translating any signalling information for the MS received from the MSC
into GSM signalling used on the air interface on a per timeslot basis. This process handles all LAPDm
protocol messaging for the MS.
The Layer 2 is responsible for setting up the link to the MS, over the air interface, to support the SMS
data transfer, irrespective of whether the SMS is MS originated or MS terminated.
RSS A-bis Interface
This process is responsible for the translating of all messages generated inside the RSS into A-bis format
messages for transmission to any Layer 3 application processes. Any messages received by this process
are veried to make sure they are complete.
If the system becomes overloaded by trafc, the RSS A-bis Interface intercepts any random access
messages and automatically gives a no access' message back to the MS. This action is undertaken
in response to commands from the call processing software. When trafc becomes lower, RSS A-bis
Interface allows random access messages to proceed to call processing software.
2006 Motorola, Inc.
June 2007
BSS Conguration and Fault Management Interface Version 1 Rev 3
BSS Conguration and Fault Management Interface
To call processing
To fault management
To the radio hardware
RSS
A-bis
CFM
HDPC
Layer 1
Layer 2
2006 Motorola, Inc.
1-53
June 2007
Version 1 Rev 3 Handover Detection and Power Control
Handover Detection and Power Control
This process has by far the most functions to full inside the RSS. It controls the transmission power
of the MS (uplink) and also the transmission power of its related TCU/CTU/CTU2 (downlink) on a per
timeslot basis. The object is to keep both the MS and the radio on the lowest possible transmission power
to help reduce interference between system users. This process is also responsible for calculating the
MS's timing advance to keep the mobile inside its allocated timeslot.
The handover detection and power control process takes responsibility for initiating the handover process
for a MS. It decides when the handover is necessary, i.e. the MS is on maximum power but the received
level at the BSS is still too low or the MS is on maximum timing advance. It follows the handover
procedure as suggested in GSM Recommendation 5.08 but a number of special Motorola algorithms
can be implemented.
When TCHs are idle, this process monitors the ambient noise in the receive slot period. After processing,
the average noise level per TCH is passed to call processing.
Once a call to a MS has been established, if a MS leaves the system without terminating the call, the
system will waste its resources if the MS channel remains in operation. To reduce this, the handover
detection and power control process monitors the SACCH messages from all MS on its busy TCHs. If a
number of consecutive SACCH messages from a particular MS fail to appear, the process informs call
processing software to close down the resources allocated to that MS.
All messaging to and from the handover detection and power control process are in the A-bis format.
Therefore the location of this process is in theory interchangeable, depending upon which A-bis format
is chosen.
2006 Motorola, Inc.
June 2007
Handover Detection and Power Control Version 1 Rev 3
Handover Detection and Power Control
Functions
Controls transmission power of MS
Controls the timing advance of MS
Controls the transmission power of the BSS
Determines the need for handover
Monitors the interference level on idle channels
Detects loss of SACCH messages (conserving resources)
2006 Motorola, Inc.
1-55
June 2007
Version 1 Rev 3 Call Processing
Call Processing
MTP L3/SCCP Preprocessor
This process handles the protocol adaptation of messages when transmitting or receiving messages on
the A interface. It also determines which process each message is destined for, by interrogating the
message header, and then addresses the message accordingly.
Connectionless Manager (CLM)
The CLM deals with the global control of a BSS. This process deals with the non-connection orientated
portion of the C7 signalling.
SCCP State Machine (SSM)
The Signalling Control Connection Part State Machine (SSM) is responsible for handling all the
connection orientated portion of the C7 Signalling.
The SCCP State Machine is responsible for co-ordinating all intra-BSS and intra-cell handovers. It
makes sure that the target cell is informed of the handover request and ensures that a radio channel
is allocated to the mobile station. This process generates all the required messaging/signalling to
co-ordinate a handover, it will also inform the MSC when this procedure has been completed . The
SCCP State Machine informs the source cell of a successful handover in order that radio resources can
be de-allocated.
Switch Manager (SM)
The function of the SM is to connect a MS's terrestrial trunk from the MSC (designated by the MSC), to
the radio channel given to a MS by the cell resource manager in the BSS software.
2006 Motorola, Inc.
June 2007
Call Processing Version 1 Rev 3
Call Processing
Collection of Layer 3 Procedures
FUNCTIONS:
Call Set-Up
Air Interface encryption
Control of Handovers
Signalling (MSC to BSS)
(BSS to MS)
Connectionless
Manager
(CLM)
SCCP
State Machine
(SSM)
Switch
Manager
(SM)
Radio
Sub-system
(RSS)
Cell Resource
Manager
(CRM)
MTP L3
SCCP
Preprocessor
Radio Resource
Stste Machine
(RRSM)
Radio Channel
Interface (RCI)
2006 Motorola, Inc.
1-57
June 2007
Version 1 Rev 3 Call Processing
Call Processing
Cell Resource Manager (CRM)
The CRM is responsible for the allocation of radio channels in response to either a MS accessing the
system or the MSC paging a MS. The CRM keeps a dynamic database concerning the state of each of
its channels, and uses the interference information provided by the RSS to allocate the best available
resource.
When the trafc loading on a BTS site or cell becomes too heavy, the CRM can instigate ow control.
The CRM tells the A-bis Interface in the RSS software to block any further Random Access requests
from MS on that cell or site. When trafc load reduces, this ow control will be removed.
Radio Resource State Machine (RRSM)
The Radio Resource State Machine (RRSM) is the call processing software entity responsible for the
initiation and maintenance of physical connections.
This process is responsible for the activation of the radio channels requested from the CRM. When a MS
no longer requires a radio channel, the RRSM is responsible for closing the channel down.
Radio Channel Interface (RCI)
The RCI process changes the address of a MS used in the RSS into the address used by the Layer 3
call processing processes.
The RSS addresses MS by using its channel number, whilst the Layer 3 Call Processing processes
address messages for a MS using the SCCP reference number.
These processes can be located dependant on which form of A-bis is chosen. Under Motorola systems
these reside at the BTS cabinet.
2006 Motorola, Inc.
June 2007
Call Processing Version 1 Rev 3
Call Processing
SYS02_Ch1_24
BSC MTL
LCF BSP
CLM
SM
MTPL2
MTPL3
SCCP PRE PRO
SSM
HO
EVAL
LCF
MTPL2
MTPL3
SCCP PRE PRO
SSM
HO
EVAL
LCF
MTPL2
MTPL3
SCCP PRE PRO
SSM
HO
EVAL
In-Cell
BTS
M-Cell
BTS
BTP
RSS
DHP
RSS
DHP
CRM
RCI
RRSM
MCU
RSS
TCU
CRM
RCI
RRSM
MCUF
RSS
CTU
CRM
RCI
RRSM
Horizonmacro
BTS
HorizonIImacro
BTS
HIISC
RSS
CTU2
CRM
RCI
RRSM
2006 Motorola, Inc.
1-59
June 2007
Version 1 Rev 3 Comparison GSM and Motorola Systems
Comparison GSM and Motorola Systems
Under the GSM dened system, most of the intelligence' of the BSS is kept at the BSC. All handover
decisions, allocation of TCHs and monitoring of active radio channels is done at the BSC itself. This
means that a great deal of control messaging/signalling must pass between the BTS and the BSC along
the A-bis interface, the greatest overhead being MS uplink measurement reports.
Due to the large amount of signalling/message transfer, there is a large requirement for Radio Signalling
Link (RSL) timeslots between the BSC and BTS.
These RSL timeslots utilise the Link Access Protocol Data Layer 2 protocol to carry the signalling and
BTS control messages. Each LAPD signalling link will occupy a complete 64 Kbit/second timeslot on the
A-bis Interface.
2006 Motorola, Inc.
June 2007
Comparison GSM and Motorola Systems Version 1 Rev 3
MSC
MTP L3/SCCP
PREPROCESSOR
Switch
Manager
SCCP
State
Machine
Connectionless
Manager
Cell
Resource
Manager
Radio
Resource
State
Machine
Radio
Channel
Interface
Radio
Subsystem
Radio
Subsystem
BSC
BTS
A-bis LINK
2006 Motorola, Inc.
1-61
June 2007
Version 1 Rev 3 Comparison GSM and Motorola Systems
Using the Motorola system, the control of the radio and terrestrial circuits is divided between the BSC
and the BTS. The BSC retains the processes which control the Terrestrial links up to the MSC and the
nal decision process concerning handovers. Meantime, the BTS has all the processes to monitor and
control the radio channels. The Motorola application generally needs 1 RSL per BTS site.
This reduction in dedicated A-bis links is achieved because far fewer control/signalling messages
are required between the BSC and the essentially more intelligent BTS. Using less 2Mb timeslots for
signalling allows more TCH channels and hence more economic use of the BSC-BTS link.
From GSR 5, automatic allocation of trafc channels is also carried out on the Ater Interface between the
RXCDR and the BSC. Using the dynamic switching capability of the transcoder, the Ater trafc channels
are held in a 'pool' and are allocated to calls as and when they are needed, rather than being statically
mapped between the RXCDR and BSC. This process requires the operation of 2 logical devices; the
Associate Remote Transcoder (AXCDR) at the BSC and the Associate Base Station System (ABSS) at
the transcoder. The 2 devices act to allocate channels dynamically using the Allocation Manager process
responding to control messages sent on the Transcoder Base Site Link (XBL) control channel, which has
been enhanced in importance to full this capability.
2006 Motorola, Inc.
June 2007
Comparison GSM and Motorola Systems Version 1 Rev 3
MSC
Switch
Manager
Allocation
Manager
ABSS
RXCDR
A ter interface XBL
BSC
AXCDR
MTP L3/SCCP Preprocessor
Switch
Manager
Allocation
Manager
SCCP
State
Machine
Connectionless
Manager
A bis
interface
Cell
Resource
Manager
Radio
Resource
State
Machine
Radio
Channel
Interface
Radio
Subsystem
Radio
Subsystem
BTS
2006 Motorola, Inc.
1-63
June 2007
Version 1 Rev 3 User Security Management
This feature provides enhanced user security functionality by providing a new username and password
management system for the BSS/RXCDR replacing the existing system of shared password access. It
is not backward compatible with previous releases.
The main benet of this feature is to improve the security and access control on the customers network.
It provides the operator the ability to set up individual usernames for BSS/BTS access from the OMC-R
and also locally at the BSS TTY. It provides for standard password management system which includes
complexity checking, password ageing and encryption of password information both in password storage
and password transfer across systems. It also provides logging of user sessions therefore providing full
traceability and accountability of network changes.
There are two types of user accounts maintained as part of this feature implementation:
NE User Account
NE Field Engineer Account
NE User Account
This is the normal user account which needs to be maintained and managed at the managing OMC-R.
The OMC-R administrator will be able to create a new username and assign a prole to the user which
denes what BSS and EMON command sets that the user may access at the BSS.The omcadmin user
can set NE access level for a NE user on OMC-R and when the user login to OMC-R, they will be placed
at that access level. The default NE access level for the omcadmin user is 4, and for all other users the
default is 1. The NE user account passwords expire after a certain age set at the UNIX and can also be
blocked.
NE Field Engineer Account
These accounts are meant to be used by a eld engineer only when physically visiting a site. Three xed
eld engineer user accounts, eldeng2, eldeng3, and eldeng4 are used only for qcomm application
or local login purposes. The eldengX accounts are meant only for qcomm purposes. hese account
passwords never expire and blocking is not supported. Three eld engineer accounts will be maintained
at the BSS as follows:
eldeng2 NE access_level=2, MMI access_level=2, EMON access_level=0
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 eld engineer account passwords have not been changed for a specied number of days and
has therefore expired.
The default passwords for the three eld engineering accounts associated with access level 2/3/4
are listed as following:
Level2 eld engineer account user name/password is: eldeng2/2galvins.
Level3 eld engineer account user name/password is: eldeng3/3stooges.
Level4 eld engineer account user name/password is: eldeng4/4beatles.
OMC-R provides interface to manage eld engineering account passwords and actively
synchronizes with BSS when these passwords are changed. It is not able to change the eld
engineering account passwords at BSS side.
2006 Motorola, Inc.
June 2007
User Security Management Version 1 Rev 3
Functionality
Authentication
Access control
Activity logging
Data confidentiality
Communication Security
2006 Motorola, Inc.
1-65
June 2007
Usernames and passwords are managed at the OMC-R and usernames set-up on the OMC-R are
dened across the entire system or on a geographic region basis. A mechanism will be provided at
the OMC-R to manage BSS/BTS accounts and an interface from the OMC-R to the NEs will be provided
for validation of the account information on user login attempts at individual NEs. A user will have a
single username and only one password associated with the username which will be valid across all the
NEs to which that user has access.
The account will be associated with a BSS command partition(level 1,2,3 or 4) which denes the
commands accessible on the NEs by that account. The same command partition will apply across all
NEs accessible by the user. NE granularity for access is BSC, that means access will be provided to
a BSC and all elements under that BSC.
Engineering accounts will be maintained at the BSS. The purpose of these accounts is to let an on-site
eld engineer open a local session at the BSS when the OML link is either not congured or is not
functional. The authentication of the users of these eld engineering accounts is under the control of the
BSS.
OMC-R Overview
The OMC-R will contain the account management application, the password verication application and
generate appropriate actions to communicate valid logins to the BSS, the log le maintenance and
log le interface application. All applications will be appropriately interfaced with geographic command
partitioning.
BSC Overview
The BSS will change the login interface to request valid username and password for each login and
display banner information. BSS will log user sessions and transfer log les to the OMC-R on session
end. BSS will log failed login attempts and transfer this information to the OMC-R. BSS will request new
root passwords for newly installed equipment. BSS will store root password information locally.
QCOM LOgin
When a user logs in with qcomm:
MMI wont automatically prompt user to input username and password
The user has level 1 access by default, as legacy
If a user want to execute level 2/3/4 commands, user need to input a new MMI command: Login
at the command prompt
A new MMI command Logout will be introduced
Login/Logout command will be ignored during login/batch session
Note: The old MMI commands chg_level and chg_password are removed from GSR9, although
chg_level is still used in the OMC-R scripts as a dummy command to allow correct functionality at
levels 3 and 4 only. Existing automated scripts can be used but the user must login before they can be
executed. Scripts that only change access to level 2 may fail, (i.e. only passing in one password).By
default, all OMC-R account users have level 4 access.
There is a new BSS parameter: eldeng_always_enabled. This parameter determines whether a eld
engineering account can always be used to login, or if it can only be used when the OML is out of service
(OOS).
2006 Motorola, Inc.
June 2007
User login from qcomm
User input MMI command:
login
OMC connected
(use omc unix account)
Account:
Password:
Account:
Password:
No OMC connection
(use fieldengX)
d )
MMI
prompt:
Login Authentication - Qcomm
Scenario: user run command login and
OMC is connected.
BSS prompt user to input user name
and password
BSS collects the user name and
password input by user.
BSS then sends the user name and
password to OMC
Password verification is done at
the OMC.
OMC send back the result to BSS.
2006 Motorola, Inc.
1-67
June 2007
Password Management
Local Passwords Management
BSS will not be able to change the local passwords
OMC is able to reset the local passwords
The local passwords are saved in database and NVRAM in encrypted format.
Command Access Control
BSS provide access control for MMI and emon commands
Each rlogin session has an attribute for user access level
A command can be executed by a user only when:
MMI: User access level >= MMI command level
EMON: User access level >= EMON cmd level + 2
User Activity Log
Only those activities after user login will be logged
BSS will record the original text printed by MMI and EMON
Log le is only kept on the rst board user login
When a user execute emon command rlogin to login another board/site, the new board create
logs for the user activities on the local board, and then send to the original board.
The rst-login board is responsible for transferring the log le to the OMC
Triggers for Transferring Log
BSS transfers logles to the OMC when
The session is over
The session expires
Log le size reaches the buffer limitation
At the end of a day
Storage of Log File on BSS
Log les are stored by memory blocks
When a block is full, the log le will be transferred to OMC, so that the block can be used for saving
log le again
When all the blocks are used up, the log will overow.
2006 Motorola, Inc.
June 2007
Local login message sequence:
1. Under the control of the OMC OML in-service
The sequence begins with the user requesting access to Level 1, by
use of the LOGIN command at the MMI.
The LOGIN command will then be used to determine the state of
the requisite links (depending on the platform being accessed) by
the corresponding MMI sending a message to the BSC CA.
The BSS CA will respond with a message containing the link
status.
If the requisite link is in-service, the user is given a UNIX user
interface, into which their UNIX user id and password should be
entered.
Once this information has been submitted, a LOGIN REQUEST
message will be sent to the OMC-R over the ALARMS/EVENTS SVC.
Embedded within this message is the USER_ID and ENCRYPTED
PASSWORD.
The Event reporting Main Function then attempts to send the data
across the EVENTS virtual circuit to the OMC-R.
The OMC-R will use a look-up table to authenticate the user and
respond with a message back to the BSS Event reporting Main
Function.
The Event reporting Main Function will then send a LOGIN
RESPONSE message to the BSS MMI.
2. Under the control of the BSS OML out-of-service
The sequence begins with the user requesting access to Level 1, by
use of the LOGIN command at the MMI.
The LOGIN command will then be used to determine the state of
the requisite links (depending on the platform being accessed) by
the corresponding MMI sending a message to the BSC CA
Because the OML is out-of-service, CA responds to the MMI with a
message, and the user is now offered a RAM field engineering
account dialogue box where they are prompted for ACCESS LEVEL,
USER ID and PASSWORD.
The BSS MMI will resolve this information and if accepted, allow
access to the command level entered by the user.
2006 Motorola, Inc.
1-69
June 2007
2006 Motorola, Inc.
June 2007
Network Element Conguration Version 1 Rev 3
Chapter 2
Network Element Conguration
2006 Motorola, Inc.
2-1
June 2007
Version 1 Rev 3 Network Element Conguration
2006 Motorola, Inc.
June 2007
Objectives
Describe the device/function interdependency used within database structures
Describe the Site congurations of a BSS and their associated commands
Describe the operating modes within the Network
Describe the process of Ater Allocation and BSC LAN Packing
Describe the Cabinet/Cage structure equipage
Describe the use of KSW/DSW2 extension/expansion cages
Describe the equipage/functions of common cards and processors within the BSS
Describe the equipage of links within the BSS
Describe the use of the Unequip command parameter
Describe how a network element is synchronised to other elements and the commands used to
report alarms
Explain the statistics interval time period
Complete a written exercise to partly equip a BSS database
2006 Motorola, Inc.
2-3
June 2007
Version 1 Rev 3 BSS Conguration
BSS Conguration
The owchart on the facing page details the sequence of building a database script, the order and content
of which will change depending on its function, whether supporting RXCDR, BSS, BTS or Path.
Appendix B shows a more detailed ow chart for each script type.
2006 Motorola, Inc.
June 2007
BSS Conguration Version 1 Rev 3
BSS Conguration
EQUIP CAGE
EQUIP CABINET
EQUIP FUNCTIONS
EQUIP LINKS
DSP OPTIONS
ADD CELL (BTS ONLY)
EQUIP DEVICES (DIGITAL BOARDS)
SITE CONFIGURATION
(CHANGE ELEMENTS)
EQUIP AXCDR or ABSS
EQUIP BSS, RXCDR or SITE
2006 Motorola, Inc.
2-5
June 2007
Version 1 Rev 3 The Base Station System (BSS)
The Base Station System (BSS)
A BSS can be divided into three functions, the BSC, the BTS and the RXCDR.
The Base Station Controller (BSC)
The BSC is the digital control function which performs the following:
1. Controls all associated Base Transceiver Stations (BTS).
2. Performs call processing
3. Supports operations and maintenance
4. Supports the interface between the BSS and Mobile Switching Centre (MSC).
5. Supports the interface between the BSC and BTS.
The Base Transceiver Station (BTS)
The BTS provides the Radio Frequency (RF) equipment that supports the radio path to the mobile station
(MS) and the digital control functions to support it.
The Transcoder
The transcoder (RXCDR) is the digital signal processing equipment that performs GSM dened speech
encoding and decoding. The transcoding function can be performed within the BSS or remotely, normally
at the MSC location.
Up to 9 transcoders may support a single BSS, and a single BSS may be connected to up to 9
transcoders.
2006 Motorola, Inc.
June 2007
The Base Station System (BSS) Version 1 Rev 3
The Base Station System (BSS)
BTS
BTS
MSC
OMC
Site 1
Site 2
Site 0
BSC
WITH
XCDR
Operations and Maintenance
Link (OML)
MSC
BSS with
Transcoding
BTS
BSC
RXCDR
OMC
BTS BTS BTS
BSC
RXCDR
OMLs
(BSC &
XCDR)
TCHs
MTLs
TCHs
MTLs
XBLs
OMLs
TCHs
RSLs
A bis
Interface
A ter
Interface
2006 Motorola, Inc.
2-7
June 2007
Version 1 Rev 3 Command/Database Parameters Types
Command/Database Parameters Types
MMI commands and database parameters are classied on the basis of whether or not a user action is
required to enter the command or change the value of the database parameter.
Type A
No special user action is required to enter a Type A command or change a Type A database parameter.
Type B
Special conditions must exist in the system when entering a Type B command or changing a Type B
database parameter. The special conditions are included in the Operator Actions listing of each command
and database parameter description.
2006 Motorola, Inc.
June 2007
Command/Database Parameters Types Version 1 Rev 3
Command/Database Parameters Types
Type A
No operator actions
Type B
Special conditions exist
(refer to W23 BSS command reference manual)
Sys02_Ch2_17
2006 Motorola, Inc.
2-9
June 2007
Version 1 Rev 3 RXCDR/BSS/SITE/CAB/CAGE Numbering Scheme
RXCDR/BSS/SITE/CAB/CAGE Numbering Scheme
Motorola have developed a conventional numbering scheme that must be adhered to in the equipage
of a RXCDR, BSS, SITE, Cabinet and Cage. Cage references are for In-Cell stations, cages are not
explicitly equipped at M-Cell/Horizon sites because the cabinets do not have a cage structure.
The term SITE is used for BTS sites.
RXCDR, and BSCs (both with local transcoding and with remote transcoding) are equipped separately
as RXCDR and BSS; both BSS and RXCDR will be created as site '0' within the initial 'equip' command,
but also require a unique network identity (id) number between 1 and 254. A BSC and RXCDR are
thereafter known as 'BSS xxx' or 'RXCDR xxx' within a network, where 'xxx' is the (id).
For example a network will henceforth have a BSS 1, possibly a RXCDR 1 (some networks may decide
to use the range of 1 - 254 to differentiate between BSS and RXCDRs).
Within a BSS system, BTS SITES will have site numbers as now from 1 to 140. The BSS system will
focus on the BSS itself and its dependant BTS sites, although a BSS may be served by more than 1
RXCDR (up to 9). Likewise, a RXCDR may serve up to 9 BSS systems.
RXCDR/BSS/SITE/CAB/CAGE NUMBERING CHART
SITE TYPE SITE CAB CAGE NETWORK
IDENTITY
NUMBER
RXCDR 0 0 - 13 0 - 13 1 - 254
BSS(remote
transcoding)
0 0 - 13 0 - 13 1 - 254
BSS (local
transcoding)
0 0 - 13 0 - 13 1 - 254
BTS 1 - 140 0 - 13 15 - 2
Shown opposite are some typical examples of this scheme.
Notes:
1. A BSS, whether with local or remote transcoding, will be of a stand alone type.
2. The site type is equipped in the equip bsc BSS, RXCDR or SITE command. Within the prompts
which follow equip bsc BSS and equip bsc RXCDR, the command prompts will automatically
set the fm_site_type element to the correct value. If the local site number is greater than zero,
fm_site_type is always set to BTS. If the local site number is zero, fm_site_type will be either
RXCDR, BSC. The operator may use the command disp_bss to distinguish which.
2006 Motorola, Inc.
June 2007
RXCDR/BSS/SITE/CAB/CAGE Numbering Scheme Version 1 Rev 3
RXCDR/BSS/SITE/CAB/CAGE Numbering Scheme
MSC
RXCDR 1 - 254
RXCDR
CAB
CAGE
CAGE
0
0
0
1
BSS
CAB
CAGE
CAGE
0
0
0
1
BSS 1 - 254 BSS 1 - 254
BSS
CAB
CAGE
0
0
0
BTS (Horizonmacro)
SITE
CAB
1
0
BTS (In-Cell)
SITE
CAB
CAB
CAGE
CAGE
1
0
1
15
14
SITE
CAB
2
0
RXCDR 1 - 254
RXCDR
CAB
CAGE
CAGE
0
0
0
1
BTS (HorizonIImacro) BTS (M-Cell)
SITE
CAB
3
0
2006 Motorola, Inc.
2-11
June 2007
Version 1 Rev 3 Site Conguration
Site Conguration
RXCDR, BSS, and BTS sites are equipped individually, dening the site as a RXCDR, BSS or SITE
where the device being equipped is a BTS.
All types of site are equipped under SYSGEN ON mode, using the equip 0 xxx command where
xxx is either BSS, RXCDR or SITE. The 3 types of site equipage command strings are shown below and
on the following page.
For each of the RXCDR and BSS sites, an additional logical device is also now equipped: for the
RXCDR an Associate BSS (ABSS) and for the BSS an Associate XCDR (AXCDR). The equipage of
these devices follows immediately after the main device which each supports. These Associate devices
are logical representations of their parent sites, created within the opposing site to allow the provisioning
of resources (trafc circuits from the MSC and Ater circuits between the RXCDR and BSS) so that the
system can operate in Auto Connect (dynamic) mode.
Since each RXCDR may be connected to up to 9 BSSs, and each BSC may be served by up to 9
RXCDRs, there may be up to 9 ABSS equipped in each RXCDR, and up to 9 AXCDR equipped in each
BSS.
Equipping the RXCDR
The rst line in a database script will equip the RXCDR. After the rst line, additional prompts will appear.
equip < 0 or bsc > RXCDR
1st prompt (identier)
This prompt species the transcoder network number between 1 and 254.
Following the RXCDR equipage, an associate BSS must be equipped for each BSS to which the RXCDR
is connected.
equip < 0 or bsc >ABSS
This prompt species the network identity between 1 and 254 for the BSS to which the RXCDR is
connected. Note that there may be up to 9 ABSS devices equipped in a RXCDR.
2006 Motorola, Inc.
June 2007
Site Conguration Version 1 Rev 3
Site Conguration
equip <0 or bsc> RXCDR
Enter the rxcdr id:
(range 1 - 254)
equip <0 or bsc> ABSS
Enter the abss device id:
(range 1 - 254)
Sys02_Ch2_18
2006 Motorola, Inc.
2-13
June 2007
Site Conguration
Equipping the BSS
The rst line in a database script will equip the BSS. After the rst line, additional prompts will appear.
Again, following the equipage of the BSS, it will be necessary to equip an AXCDR for each RXCDR to
which the BSS is connected.
equip <0 or bsc> BSS
This prompt species the local BSS number between 1 and 254.
2nd prompt (whether local transcoding is performed)
This prompt species whether the site is a BSS with local transcoding.
equip <0 or bsc> AXCDR
This value corresponds to the network identity of the RXCDR represented by this AXCDR.
2nd prompt (CIC Validation Mode)
This prompt denes whether the Ater (BSS - RXCDR) is operating in a dynamic (Auto-Connect) mode,
i.e. that Ater circuits will be allocated to CIC's automatically on system initialisation.
3rd prompt (EAC Mode)
This prompt denes whether the Ater (BSS - RXCDR) is capable of operating at a switching rate of
8kbps. For this to be valid the system must also be operating in a dynamic (Auto-Connect) mode, i.e.
that Ater circuits will be allocated to CIC's automatically on system initialisation, and the AMR/GSM half
rate features must be unrestricted. In addition this will only be allowed if the system detects that only
DSW2 boards are tted.
4th prompt (CIC blocking threshold)
This prompt sets the threshold to block ater channels according to availability of IDLE aters. It will only
be prompted when eac_mode is enabled and must be less that the value of cic_unblock_thres.
5th prompt (CIC unblocking threshold)
This prompt sets the threshold to unblock ater channels according to availability of IDLE aters. It will only
be prompted when eac_mode is enabled and must be greater that the value of cic_block_thres.
2006 Motorola, Inc.
June 2007
Site Conguration
equip <0 or bsc> BSS
Enter the bss id:
(range 1 - 254)
Is local transcoding performed at the
BSC?
Yes/No
equip <0 or bsc> AXCDR
Enter the AXCDR device id:
Range 1 to 254
Enter CIC validation mode:
Yes/No
Enable Enhanced Auto-Connect Mode:
No = disabled
Yes = enabled
Enter the cic blocking threshold:
0 - 245
Enter the cic unblock threshold:
0
- 225
Sys02_Ch2_19
2006 Motorola, Inc.
2-15
June 2007
Site Conguration
Equipping a SITE
The rst line will equip the Site. After the rst prompt, additional prompts will appear as shown.
equip <0 or bsc> SITE
This prompt will be a number between 1 and 140, which will identify the BTS within the Base Station
System.
2nd prompt (LCF)
This prompt denotes that an LCF is supporting the RSLs for the site. As a BSC type 0 is no longer
supported, LCF is the only valid response
3rd prompt (BSP/LCF)
This prompt denotes the unique identier of the LCF supporting the RSLs.
4th prompt (RSL rate)
This prompt species the RSL rate to be implemented. The prompt is displayed only if the site is remote
and the 16k RSL option is enabled.
5th prompt (Dynamic allocation)
This prompt only appears if:
1. The dynamic allocation feature is unrestricted.
2. The site being equipped is a stand alone BTS.
3. The site in use, is not using the 32K trau feature of GPRS.
The prompt refers to dynamic allocation of Abis trafc channels where a DYNET device is used (this will
only occur if the BTS is In-Cell).
2006 Motorola, Inc.
June 2007
Site Conguration
Enter the site identifier
1 to 140
LCF
Enter the RSL type
16 or 64
Yes/No
equip < 0 or bsc > SITE
Enter the type of BSP or LCF
Enter the function identifier for the BSP or LCF
LCF 0 to 24
Does the SITE use dynamic allocation
of terrestrial backing resources
2006 Motorola, Inc.
2-17
June 2007
Version 1 Rev 3 Site Type
Site Type
The BSS is very exible and can have many congurations consisting of three elements;
1. Base Station Controller (BSC)
2. Base Transceiver Station (BTS)
3. Transcoding
The main processing within the BSC and In-Cell BTS's, is performed by modules called Generic
Processors (GPROCs). The GPROCs within a BSS have to be able to communicate with one another
for BSS control, signalling and software down loading.
As the BSC and BTS are in separate locations then communication must be via the LAPD signalling link
on the 2.048 Mbit/s links.
The site type parameter also determines other site related features. If the site type is 1 i.e. a BSS, then
timeslots on the TDM highway of that site will not be allocated to digital radio interface boards as they
will only be found at a BTS.
The parameter fm_site_type is set to the correct value automatically when the site type is equipped.
2006 Motorola, Inc.
June 2007
Site Type Version 1 Rev 3
Site Type
MSC
BSC
BSC
RXCDR
SITE TYPE 3
SITE TYPE 1
SITE TYPE 1
LOCAL TRANSCODING
BTS
SITE TYPE 2
BTS
SITE TYPE 2
BTS
SITE TYPE 2
2006 Motorola, Inc.
2-19
June 2007
Version 1 Rev 3 Operating Modes and Denitions
Operating Modes and Denitions
The upgrade to GSR 5 introduced Auto-Connect Mode to GSM, which is now the standard mode of
operation, while a Backwards Compatibility mode has also been retained. In addition the release of
GSR 7 has seen the introduction of Enhanced Auto-connect Mode in relation to AMR. The 3 modes are
dened as follows:
Auto-Connect Mode: Auto-connect mode is an operator - selectable mode in which Ater trafc channels
are allocated and released dynamically by a BSS as resources are provisioned, unprovisioned, or during
the handling of a fault condition. Auto-connect mode provides improved fault tolerance of a dynamic
mode but also the call processing efciency of backwards compatibility mode. Auto-Connect mode is
controlled by the BSC.
Enhanced Auto-Connect Mode: An optional mode dened for the RXCDR-BSC interface whereby the
specic timeslots used for calls are selected by the system during call set-up. This method is used with
AMR and GSM half rate, in order to allow the sharing of E1 link timeslots used for 16Kbps (for AMR
full-rate) and 8Kbps (for half-rate) trafc subchannels and GSM for half rate, thereby allowing an overall
saving in the E1 requirement.
Backwards Compatibility Mode: This operator - selectable mode is equivalent to the situation under
GSR 4 (and previous releases) and denes a BSC/RXCDR mode in which Ater channels and CICs are
statically switch connected. This mode does not provide any fault tolerance or CIC validations, and is
intended only to provide an upgrade path from GSR 4 to GSR 5.
Denitions: The denitions of interfaces and Circuit Identity Codes have been revised as follows:
A-Interface: The A-Interface carries the E1/T1 network connection between the MSC and a TRAU
resource (i.e. GDP, GDP2 or XCDR card) as well as signalling between the MSC and the BSC. If
the TRAU resource is remotely located at an RXCDR, the A-interface does not include the linkset
between the BSC and RXCDR. The A, Abis and
m
interfaces continue unchanged.
Ater Channel: An Ater channel is a 16Kbps channel (or an 8Kbps channel under AMR/GSM half
rate operation) on the Ater interface between the BSC and RXCDR. At the BSC, an Ater channel
is switch-connected to the appropriate RCI/NCI for the given call, while at the RXCDR, an Ater is
switch-connected to the appropriate CIC for the given call.
CIC (Circuit): A CIC is a number used on the A-interface to represent a single 64Kbps circuit
between a TRAU resource and the MSC, and denes the xed position of the circuit on the
A-interface. For remote transcoding, CICs must rst be switch-connected to an Ater channel at
the RXCDR, which is then switch-connected to an RCI/NCI at the BSC.
2006 Motorola, Inc.
June 2007
Operating Modes and Denitions Version 1 Rev 3
Operating Modes and Denitions
RXCDR
RXCDR
MSC
RXCDR (Static)
BSC BSC Dynamic
RXCDR Dynamic
MSC
Ater
A
CICs
Auto-connect
mode
Backwards
compatibility
mode
CICs
CICs defined
to match A interface
CICs may be < Aters

2006 Motorola, Inc.
2-21
June 2007
Version 1 Rev 3 Ater Allocation
Ater Allocation
A new feature has been introduced at GSR9, along with others, to increase Network Capacity,which will
improve the efciency of the Ater allocation algorithm. This in turn will improve the CPU utilisation at
the BSP which will support an increase in call handling capacity with a call load of 180K Busy Hour Call
Attempts (BHCA 96s call duration), under an appropriate conguration. The BSS will have the ability
to support an increased number of calls in a mixed FR and HR call load. The BSC shall assure the mean
BSP CPU utilization will not exceed 70%.This feature is restricted by the option incNetCapacityOpt.
The number of Aters has increased with GSR9 features from 6696 to 10416.
The current Ater algorithm was introduced at GSR7 with AMR phase 2. The GSR7 memory restrictions
resulted in a 3 tier search algorithm designed to reduce the search time but without a high memory
impact. However the resulting algorithm is not scalable and so as the load increases the search time
and effort increases. In GSR9 CPU efciency is the main focus and memory is less of an issue so the
Ater search algorithm can be redesigned to be more efcient and more scaleable at the cost of higher
memory usage. The new algorithm is a list based algorithm where Aters are allocated from the top of
the available lists to minimise the search.
Another feature, BSC LAN packing, (explained in the next section) will support 250k BHCA, using the
GSR9 trafc call model as shown. The expected maximum effective message rates (unpacked) that
can be supported using the LAN packing mechanism are dependent on deployment but an indication is
provided in the table below, together with the associated deployments:
Table 2-1 Maximum unpacked-equivalent message loads that can be supported using LAN packing
Deployments Congurations Exec Message Loads
180k BHCA Greeneld
(GSR9 call model with
96s call duration)
4 GPROC3-2 MTL-LCF
8 GPROC3-2 RSL-LCF
1 GPROC3 BSP
4DSW2
RSL-LCF: 860 messages/s
MTL-LCF: 970 messages/s
BSP: 1420 messages/s
180k BHCA Legacy
96s call duration)
4 GPROC3-2 MTL-LCF
16 GPROC2 RSL-LCF
1 GPROC3 BSP
4DSW2
250k BHCA Greeneld
60s call duration)
6 GPROC3-2 MTL-LCF
8 GPROC3-2 RSL-LCF
1 GPROC3 BSP
4DSW2
Note that the actual number of messages sent (packed) do not exceed 600 msgs/s.
2006 Motorola, Inc.
June 2007
Ater Allocation Version 1 Rev 3
Ater Allocation
overload
overload
76%
Current
360k BHCA
250k BHCA
180k BHCA
34% 34% 68060
33% PQ II
24% 24% 68060
overload PQ II
48% 49% 68060
65% PQ II
AM / SM split AM optimisation GPROC 3-2
proocessor
overload
overload
76%
Current
360k BHCA
250k BHCA
180k BHCA
34% 34% 68060
33% PQ II
24% 24% 68060
overload PQ II
48% 49% 68060
65% PQ II
AM / SM split AM optimisation GPROC 3-2
proocessor
GSR9 Reference Service Mix Loadings on BSP
(Behavioural Model data GSR9 reference service mix)
GSR9 Call Model
180k BHCA (96s Call Duration)
250k BHCA (60s Call Duration)
Implications on the LAN:
Number of cages
typically 6
4 expansion + 2 extension cages
Number of GPROCs
dependent on GPROC2, GPROC3 or
GPROC3-2 usage)
Number of DSW2s
4 with 2 in B0/B1 operation
Number of switch connection requests
Worst case 2 per call setup, tear down and 2
per handover on average
Typically 1 per call setup, tear down and 2
per handover on average
2 handovers per call
2006 Motorola, Inc.
2-23
June 2007
Ater Allocation
Increased Network Capacity
There are other purchasable features that have been introduced with GSR9 that will increase Network
Capacity. They are all restricted by the option incNetCapacityOpt. (0 = restricted, 1 = unrestricted).
The benets of these features, of which will be explained in detail throughout this course, include:
Increased capacity
Increased operability
Increased performance
Reduced CAPEX (CAPital EXpense)
The increase in network capacity in GSR9 has implications on:
The conguration of the BSC:
There will be an increase in the number of boards required actual numbers are dependent on
which GPROC boards (GPROC2 GPROC3, GPROC3-2) are hosting the software functionality.
The number of boards affect the number of messages sent on the LAN and sent/received from the
boards.
The boards that will be used:
Another GSR9 feature will allow the use of an E1 MTL that services up to the equivalent of 16 DSO
MTLs, which is terminated by a GPROC3-2. There will be increased messages sent from the E1
MTL terminating GPROC3-2. Prior to this feature, a GPROC2 terminates only two DSO MTLs.
Of course, there are limitations as follows:
BSC LAN limitation
OMP CPU limitation
OMP Memory limitation
OML Bandwidth limitation
RSL Bandwidth limitation
It is recommended therefore that the GSR9 BSC maximum capacities are as follows:
Table 2-2 GSR9 Increased Network Capacity
Item GSR9
BTS Sites 140
BTS Cells (sectors) 250
Active RF carriers 750
Trunks (CICs) 4800
E1/T1 Links 112
Maximum BHCA rating 180,000 (call duration 96s)
288,000 (call duration 60s)
2006 Motorola, Inc.
June 2007
Ater Allocation
Recommended GSR9 BSC maximum capacities:
Item GSR9
BTS Sites 140
BTS Cells (sectors) 250
Active RF carriers- 750
Trunks (CICs) 4800
T1/E1 links 112
Maximum BHCA rating 180,000 (call duration 96s)
288,000 (call duration 60s)
2006 Motorola, Inc.
2-25
June 2007
Ater Allocation
The critical parameter dening the BSCsize is not the BHCA, which is very dependent on the call duration,
but the Erlangs it can support. It is a common tactic for vendors to claim a high BHCA which on closer
inspection is achieved by assuming very short call durations in the call model. The Erlangs per BSC is
the parameter that denes how many simultaneous calls the BSC supports. This in turn is determined
directly by the Trunks / CICs. There are of course other factors as illustrated opposite.
The rst bottleneck is the number of TRX supported. 750 TRX is more than enough to support 4800
CICs, bearing in mind site conguration dependencies and HR.
The second bottleneck is E1s. Abis, Ater and A interface E1s should be considered. In GSR9, the PSI
card will remove GDS and GSL from impacting the BSC E1s supported by the MSIs this frees up more
E1s for Abis, Ater and A interfaces. With the PSI cards, the E1s required to support 4800 CICs are just
sufcient provided careful E1 planning is employed
The third bottleneck is CICs or Trunks. It is crucial that the number of CICs supported in the BSC be
increased to 4800 at least, for reasons discussed earlier in this section. As the Figure opposite shows, a
GSR9 BSC with 3200 CICs will not support many calls in addition to the GSR8 BSC. The GSR8 RXCDR
already supports 4800 CICs.
The fourth bottleneck is processing power and the LAN. An estimate indicates that the increase
in processing speed provided by the GPROC3-2 cards should be sufcient to support up to 5000
CICs, or 360,000 BHCA at 50s call duration. The same model also indicates that provided BSC
LAN Unacknowledged Mode of Operation and BSP CPU utilization reduction for higher call handling
capacity are supported, together with planning considerations to reduce paging load at the BSC and
the implementation of a more efcient Ater search algorithm, then the BSC LAN and the BSP should
be able to cope with 4800 CICs.
The fth bottleneck is the TDM highway. The new GPROC3-2 boards with their increased processing
power reduce the total GPROCs required, while an efcient E1 planning strategy which is necessary to
minimise E1 links will also minimise MSI impact on the TDM highway. With these, the TDM highway in a
7-BSU shelf BSC should be sufcient for 4800 CICs in GSR9, should further TDM timeslots be required,
for example in a high data deployment, then up to 8 BSU shelves could be deployed. One BSU shelf
supports 1016 TDM timeslots, one GPROC3-2 board needs 32 TDM timeslots, one MSI needs 64 TDM
timeslots. Any CICs or TRX increases will require further increase in the TDM highway or an alternative
architecture.
2006 Motorola, Inc.
June 2007
Ater Allocation
BSC Call Bottlenecks GSR6 GSR9
384
TRX
750
TRX
750
TRX
512
TRX
3200
CICs
GPROC2
3200
CICs
3200
CICs
4800
CICs
GPROC2
TDM
GPROC3 -2
GPROC3 -2
TDM
A-int E1s
TDM
TDM A-int E1s
A-int E1s
A-int E1s
GSR6
GSR7/8
GSR9 4800
CICs
GSR9 3200
CICs
Abis E1s
Abis E1s
+ Abis
E1s (PSI)
+ Abis
E1s (PSI)
2006 Motorola, Inc.
2-27
June 2007
Ater Allocation
CPU Utilisation Feature Basics
AM Optimisation:
New search algorithm to efciently manage FR and HR Aters
Maintain separate link list for each type of Ater source
Increased speed at cost of higher memory usage
Constant Time Search and Release of FR and HR Aters
Negligible load on BSP even in high capacity system
Utilises same GPROC 3 card
This feature has interactions with the features of AMR Phase 2, GSM Half-Rate, Dynamic Allocation of
switch (RXCDR-BSC) Circuits, eMLPP and Emergency Call Pre-emption.It is also dependent on other
features to do with increased network capacity.
The main change of this feature will focus on Ater allocation. Compared with AMR Phase 2, when a new
call (mobile origination, mobile termination, external handover fromMSC), CIC remap, or Ater switchover
is initiated and also for an existing call with rate change, BSC shall allocate resources by following the
different allocation rules per the table opposite. (The steps with bold font are the newones for this feature)
2006 Motorola, Inc.
June 2007
Ater Allocation
CIC connected to a
16k Ater resource
(Call setup, external
ho, cic remap)
CIC connected to an 8k
Ater resource(Call
setup, external ho, cic
remap)
CIC Has no connection(Ater
Switchover, call setup,
external ho, cic remap)
16k
Ater
required
Use existing resource. Allocate 16k resource.
1st choice: Allocate an
existing 16k Ater after
releasing current 8k
Ater.
1) 16k Float Ater
2) 16k Idle Ater
associated to a HR
capable CIC
3) 16k Idle Ater
associated to a nonHR
capable CIC
2nd choice: Attempt to
join 8k Ater to its
partner.
3rd choice: Release
current 8k Ater and
allocate a 8k Ater pair.
1) 8k Float/Float Ater
pair
2) 8k Float/Idle Ater
pair
3) 8k Idle/Idle Ater pair
For CIC remap only,
1st choice is to reuse
existing Ater and
remap it to new CIC if
it is 16k, followed by
choices 1, 2, and 3
above.
Allocate 16k resource.
1st choice: allocate an existing
16k Ater.
1) 16k Float Ater
2) 16k Idle Ater associated to a
HR capable CIC
3) 16k Idle Ater associated to a
nonHR capable CIC
2nd choice: obtain a pair of
unused 8k Aters that can be
recombined to a 16k Ater.
1) 8k Float/Float Ater pair
2) 8k Float/Idle Ater pair
For CIC remap only, 1st choice
is to reuse existing Ater and
remap it to new CIC if it is 16k,
followed by choices 1, and 2
above.
8k Ater
required
1st choice: Release
16k resource and
allocate an 8k Ater.
1) 8k Float/(Inuse)
Ater
2) 8k Float/(Idle) Ater
3) 8k Float/(Float)
Ater
4) 8k Idle/(Inuse) Ater
5) 8k Idle/(Idle) Ater
6) 8k Idle/(Float) Ater
2nd choice: Use 8k of
currently associated
16k Ater.
For CIC remap only,
1st choice is to reuse
existing Ater and
remap it to new CIC if
it is 8k, followed by
choices 1 and 2 above.
Use existing resource Allocate 8k resource.
1st choice: Attempt to obtain an
existing 8k Ater
1) 8k Float/(Inuse) Ater
3) 8k Float/(Float) Ater
2nd choice, Obtain a 16k Ater
that can be split into 8k Aters for
allocation.
1) Half of 16k Float Ater
2) Half of 16k Idle Ater
associated to a HR capable CIC
3) Half of 16k Idle Ater
associated to a nonHR capable
CIC
For CIC remap only, 1st choice
is to reuse existing Ater and
remap it to new CIC if it is 16k,
followed by choices 1 and 2
above.
2006 Motorola, Inc.
2-29
June 2007
Ater Allocation
For an existing call rate change, BSC shall allocate Ater resources by following the different allocation
rules per the table opposite. (The steps with bold font are the new ones for this feature)
AM functionality
MMS 1 0
MMS 1 0
E1
MMS 0 0
GDP 1 0
BSC
RXCDR
E1 to BTS
E1 to MSC
32 timeslots
Ater (8k/16k)
SM
AM SM
AM
MMS 1 0
MMS 1 0
E1
MMS 0 0
GDP 1 0
BSC
RXCDR
E1 to BTS
E1 to MSC
32 timeslots
Ater (8k/16k)
SM
AM SM
AM
0 1 2 3 4 5 6 7
TS0
0 1 2 3 4 5 6 7
TS1
0 1 2 3 4 5 6 7
TS30
0 1 2 3 4 5 6 7
TS31
MMS 0
GRP 0 GRP 1 GRP 2 GRP 3
0 1 2 3 4 5 6 7
TS0
0 1 2 3 4 5 6 7
TS1
0 1 2 3 4 5 6 7
TS30
0 1 2 3 4 5 6 7
TS31
MMS 0
GRP 0 GRP 1 GRP 2 GRP 3
2006 Motorola, Inc.
June 2007
Ater Allocation
CIC connected to a 16k Ater
resource, 16k in use
CIC connected to an 8k Ater resource
16k
Ater
required
N/A Allocate 16k resource.
1st choice: allocate an existing 16k Ater
after releasing current 8k Ater.
1) 16k Float Ater
2) 16k Idle Ater associated to a HR
capable CIC
3) 16k Idle Ater associated to a nonHR
capable CIC
2nd choice: attempt to join 8k Ater to its
partner.
3rd choice: Release current 8k Ater and
allocate a 8k Ater pair.
1) 8k Float/Float Ater pair
2) 8k Float/Idle Ater pair
8k Ater
required
1st choice, release 16k resource and
allocate an 8k Ater.
1) 8k Float/(Inuse) Ater
3) 8k Float/(Float) Ater
2nd choice, use 8k of currently
associated 16k Ater.
N/A
2006 Motorola, Inc.
2-31
June 2007
Ater Allocation
The following diagrams show the existing Ater Algorithm search method, the underlying problem and the
solution to the problem.
2006 Motorola, Inc.
June 2007
Ater Allocation
Feature Basics Existing Method
Three levels of linear search for Ater resource
Search by Ater allocation rules (AMR 2 FRAS)
Search per MMS (num_MMS)
Search per ts_sub_group (32 * 8)
Worse case scenario:
Num_Rule * num_MMS * 32 * 8
Current Algorithm performs a linear
search across All Aters to find a
suitable free one
2006 Motorola, Inc.
2-33
June 2007
Ater Allocation
Underlying Problem maintaining interacting Free Resource lists
Pointer to Free Ater
Assign an HR Ater as half of
this FR Ater in order to meet
demand
Problem: Free List pointer is no
longer valid because the FR
Ater is now 2 HR Aters.
Simple solution is
to maintain a list
of Free FR Aters
that we can assign
from, without
searching the
entire Ater set.
Current Algorithm performs a linear
search across All Aters to find a
suitable free one
Solution : Double Linking
FR Ater Free List
FR_ptr
FR_ptr *
HR_ptr *
HR Ater Free List
HR_ptr
HR_ptr
HR_ptr *
FR Ater
structure
HR Ater
structure
2006 Motorola, Inc.
June 2007
2006 Motorola, Inc.
2-35
June 2007
Version 1 Rev 3 BSC LAN Packing
BSC LAN Packing
The support of message packing on the LAN is an unrestricted feature. LAN packing refers to an
algorithm whereby when a message is scheduled to be sent over the LAN to a particular destination, the
GPROC transmit buffers are checked for other messages with the same destination. If such messages
are found, they are then collated (by EXEC) with the original message to produce a larger message,
which is then sent across the LAN. On arrival, this concatenated message is then split out again, i.e.
(each time a GPROC receives an I-frame it will unpack the messages and route them to their respective
destination software processes within the GPROC). This will increase the efciency of the LAN and
reduces LAN congestion by reducing the number of messages sent. LAN congestion mechanisms
include, token ring speed but more likely to be the LAN processor (TMS380) limitation.
The LAN I/O message rate should not exceed 600 msgs/s in Acknowledged Mode (limited due to LAN
I/O coprocessor on each GPROC) and 1600 msgs/s in Unacknowledged Mode. (In LAN Unack Mode,
removes I-frame retransmissions if ACK frame not received within a certain time).
The packing algorithm takes advantage of the existing delays that accrue as transmit queues get longer
with increasing trafc so packing efciency increases as trafc load increases.
The LAN Packing mechanism shall be implemented on the BSC, InCell BTS and the RXCDR and shall
be implemented on GPROC2, GPROC3, GPROC3-2 and above. A GPROC that has just been brought
into service sends a notication message to inform all other GPROCs that it supports the message
packing/unpacking mechanism. It will only pack messages to other GPROCs that can support the
unpacking mechanism. Other GPROCs then respond with a special MDL message notifying of LAN
packing support.
Paging messages are broadcast from the MTL-LCF to all/several different GPROCs (RSL-LCFs)
simultaneously rather than on a point-to-point basis.
Benets
Packs messages going to the same destination together
More efcient under heavy trafc conditions
LANcongestion more likely to occur for increased number of messages, regardless of the messages
size
Therefore benecial to send less messages but with larger sizes
Interrupts per second from the LAN are decreased
LAN Packing Process
Most recent Q_BLOCK queued to LANhardware is examined. If newmsg to write will t in this Q_BLOCK
and Q_BLOCK has not been enqueued to actual hardware, memcpy new msg to end of Q_BLOCK and
increase Q_BLOCK length eld by msg length.
Modication of receive side to unpack incoming messages : use MSG_HDR->length to know when one
msg ends in a packet and another begins.
Additional checks to ensure packed messages only sent to destination GPROC that supports receiving
packed LAN msgs
LAN packing in ACK Mode will be implemented in GSR9 but not in UnAck Mode.
2006 Motorola, Inc.
June 2007
BSC LAN Packing Version 1 Rev 3
BSC LAN Packing
LAN Congestion Mechanisms
Token ring
LAN rate is 16 Mbps
Token is 3 octets
The BSP needs to transmit far
more messages than other
GPROCs
TMS380 processor
Limits the number of msgs/s
transmitted per GPROC
Ack: 600 msgs/sec/GPROC
UnAck: 1400 msgs/sec/GPROC
LANX
GPROC
0
GPROC
1
GPROC
2
GPROC
3
GPROC
4
GPROC
5
GPROC
6
GPROC
7
TX RX
TOKEN
TMS380 Bottleneck: UnAck & Packing Solutions
600
msgs/s
600
msgs/s
Bigger
msgs
1400
msgs/s
GPROC
- 1 message - 1 message - 1 message
GPROC GPROC
Current
LAN packing UnAck Mode
2006 Motorola, Inc.
2-37
June 2007
Version 1 Rev 3 Cabinet Conguration
Cabinet Conguration
The second device to be equipped in any RXCDR, BSS or BTS database will be the cabinet.
equip <site number> CAB
1st prompt (identier):
This prompt species the unique identier of the cabinet.
2nd prompt (cabinet type)
An integer code or equivalent test string is used to specify the cabinet type being equipped, this is
necessary for the IAS to process and accurately report alarms.
Note: Although M-Cellarena is now known as HorizonMicro and M-Cellarena Macro is known as
HorizonCompact, the old name should be used if using a text string.
The use of InCell becomes a purchaseable option in GSR9. In order to restrict the use of InCell BTS,
before equipping any cabinet type that belongs to GPROC group (cabinet_type ranged 0 to 9), the InCell
support option must be unrestricted. (i.e. the IncellOpt parameter must be set to a value of 1)
BSC (CM) shall check InCell support feature is unrestricted before allowing any equipage of InCell BTS
sites. (InCell BSC cabinet can be equipped whether this feature is restricted or not).
Cabinet types 18 and 19 can also now be used with PCS 1900.
3rd prompt (frequency type):
An integer code, or unique text string is used to specify the frequency ranges used within the specied
cabinet.
Note: If the frequency type entered contains GSM850 as a selection, the cabinet type must be 18 or 19.
In the case of entering 15 or M-Cellcity, 16 or "M_Cellarena" and 20 or "M_Cellarena_Macro the following
prompts will appear:
Is an internal HDSL modem present: Yes/No
Is an internal integrated antenna present: Yes/No
These two prompts are only relevant to the M-Cellcity product. In the case of remote M-Cell cabinets
(those having no MCU) integers 12 and 13 should be specied depending on cabinet type.
In the case of entering 24 to 29, which are Horizon IIproducts, the frequency type must be one of PGSM,
EGSM or DCS1800. If the HorizonII macro dual band feature is to be used then the cabinet will support
EGSM and DCS1800 in the same cabinet. Only a maximum of 3 carriers per frequency may be equipped
when using this conguration. In addition it should be noted that the Horizon IImini cannot be used as
the master cabinet, with M-Cell6/Horizon/Horzion IIproducts acting as extension cabinets.
The HorizonIImicro will not support Dual band within a single cabinet. An extension HorizonIImicro
cabinet must be equipped. When selected, the conguration management software will audit requested
site equipage and ensure that the correct number and type of devices are equipped, i.e. only one CTU2
and one BTP per cabinet.
2006 Motorola, Inc.
June 2007
Cabinet Conguration Version 1 Rev 3
Cabinet Conguration
equip <site number> CAB
enter the CABINET identifiers: 0 15
0 bts4d_48V
1 bts4d_27V
2 bssc_48V
3 bssc_27V
4 bts_dab
5 bssc_dab
6 excell_4
7 excell_6
8 topcell
9 bts_5
10 m_cell_2
11 m_cell_6
12 tcu_2
13 tcu_6
14 m_cell_micro
15 m_cellcity
16 m_cellarena
17 horizonoffice
18 horizonmacro
19 horizonmacro_ext
20 M-Cellarena_macro
22 Horizonmicro2
23 Horizoncompact2
24 - HorizonII macro
25 HorizonII macro _Ext
26 HorizonII mini
27 HorizonII mini _Ext
28 HorizonIImicro
29 HorizonIImicro_Ext
enter the cabinet type: 0 29
enter the frequency type: 1 - 31
1. PGSM
2. EGSM
3. PGSM, EGSM
4. DCS1800
5. PGSM, DCS1800
6. EGSM, DCS1800
7. PGSM, EGSM, DCS1800
8. PCS1900
9. PGSM, PCS1900
10. EGSM, PCS1900
11. PGSM, EGSM, PCS1900
12. DCS1800, PCS1900
13. PGSM, DCS1800,PCS1900
14. EGSM, DCS1800, PCS1900
15. PGSM, EGSM, DCS1800,
PCS1900
16 GSM850
17 PGSM, GSM850
18 EGSM, GSM850
19 PGSM, EGSM, GSM850
20 DCS1800, GSM850
21 PGSM, DCS1800, GSM850
22 EGSM, DCS1800, GSM850
23 PGSM, EGSM, DCS1800, GSM850
24 PCS1900, GSM850
25 PGSM, PCS1900, GSM850
26 EGSM, PCS1900, GSM850
27 PGSM, EGSM, PCS1900, GSM850
28 DCS1800, PCS1900, GSM850
29 PGSM,DCS1800,PCS1900,GSM850
30 EGSM,DCS1800, PCS1900,GSM850
31 PGSM, EGSM, DCS1800,PCS1900,
GSM850
2006 Motorola, Inc.
2-39
June 2007
Version 1 Rev 3 Cage Equipage
Cage Equipage
Equipage of cages at a site is not as straightforward as that for cabinets and sites. There are ve
parameters that need to be entered when equipping a cage. This device is only equipped at In-cell sites.
equip <site number> CAGE
Up to 16 cages can be equipped at any one site being numbered from 0-15. Valid identiers for a BSC
cage are 0-13, the rst two BSC cages being number 0 and another ID number respectively. If there is
only one BSC cage it must be numbered 0 or 1.
Valid BTS identiers for cages are 2-15. The rst BTS at a site must be numbered either 15 or 14,
conventionally 15.
The cage ID allocated must be equal to the switch setting on the LANX board in that cage.
The next set of prompts concern the KSW, TSW and DSW2 which control switching on the TDM highway
with an RXCDR, BSS or BTS. All three types use the commands prompts relating to KSW. Although the
command is for KSW is used at a BTS, it actually relates to a TSW. At a BSC or RXCDR, the KSW card
may be replaced by DSW2, or indeed a mixture may be used. In all cases the command for KSW would
be followed.
2nd prompt (KSW pair - Expansion)
Up to four pairs of KSW/DSW2/TSW (0-3) can be equipped at a site. This parameter identies which
pair manages that particular cage and therefore, which TDM highway the cage is being served by.
This eld must equal the rst i.d. of the KSW/DSW2/TSW equipage, ie, the Highway supported by
the KSW/DSW2/TSW. If expansion is not being used this will always be 0.
3rd/4th prompts (KSW Extension)
It is possible to extend a TDM highway driven by a particular KSW/DSW2/TSW to a number of
extension cages. If redundancy has been implemented then each TDM highway has associated with
it a KSW/TSW/DSW2 pair. The next two parameters identify which KSWX(R)/DSW2(R) (slot position)
in the parent cage, connects the cage to the source active and redundant KSW/TSW/DSW2. These
two parameters are optional and are only required if the cage being equipped is an extension (child)
cage. The 0-4 code being used signies the A0-A4 or B0-B4 KSWX(R)/DSW2(R) slots being used in
the parent shelf.
Note: If DSW2 is being used in an RXCDR it is only possible to extend to 1 cage.
5th prompt (cabinet)
This parameter denes the cabinet in which the cage belongs.
6th prompt (ias)
This is an optional parameter and is necessary to specify whether the cage has a connection to the
Internal Alarm System (IAS) equipment (PAB, DAB etc ...). In most cases the answer will be "yes", the
exception to this being a BSSC cabinet where 2 cages can be tted, only one of which having the IAS
connection.
Note:
This device is not explicitly equipped at M-Cell/Horizon sites. It is automatically equipped when the rst
Base Transceiver Process (BTP) at a site is entered.
2006 Motorola, Inc.
June 2007
Cage Equipage Version 1 Rev 3
Cage Equipage
equip <site number> CAGE
Enter the identifier for the cage:
0 - 13 BSS
0 -13 RXCDR
15 - 2 BTS
Enter the KSW pair that manages the cage: 0 - 3
Enter the KSWX connecting cage to KSW for TDM 0: 0 - 4
Enter the KSWX connecting cage to KSW for TDM 1: 0 - 4
Enter the cabinet to which the cage belongs: 0 - 15
Is an IAS connected? Yes/No
Sys02_Ch2_23
2006 Motorola, Inc.
2-41
June 2007
Version 1 Rev 3 Site Conguration Exercises
Site Conguration Exercises
Site Conguration Exercise 1
The following exercise will give the student the opportunity to practice the theory presented in this section.
The page opposite gives a diagrammatic representation of a typical BSC site running GSR 8 1.8.0.0,
showing only the equipment necessary to allow the student to build this rst part of the database. The
BSS id is 1, with transcoding performed remotely. The AXCDR id is 4, and uses CIC validation mode,
together with Enhanced Auto Connection. CIC Blocking and unblocking thresholds are set to 10 & 15
respectively. The OMS for the BSS is located on its own GPROC. The IAS is tted to cage 0.
The BSS site consists of one BSSC dab cabinet utilising both cages and an extended TDMA highway
with a DSW2 card tted. There are multiple working GPROC 2s at this site all having a maximum number
of TDM highway slots.
The network uses PGSM/EGSM and DCS1800 bands.
2006 Motorola, Inc.
June 2007
Site Conguration Exercises Version 1 Rev 3
SYS02_Ch2_16a
# BSC SITE (1 - 128)
# LOAD 1.8.0.0 (GSR8)
equip ____ bss
>
>
equip ___ axcdr
>
>
freq_types_allowed 7
equip ___ cab
>
>
>
equip ___ cage
>
>
>
>
>
>
equip ___ cage
>
>
>
>
>
>
chg_element bsc_type
chg_element gproc_slots
>
>
>
Fibre Connectors
DSWX DSWX
D
S
W
2
Cabinet 0 Cage 0 Cabinet 0 Cage 1
U24 U1
2006 Motorola, Inc.
2-43
June 2007
Version 1 Rev 3 Site Conguration Exercises
Site Conguration Exercise 2
Site 18 consists of a 2 cabinet, 12 carrier M-Cell6 site using the EGSM in the rst cabinet and 1800DCS
RF equipment in the second cabinet. The Radio Signalling Link for site 18 which is set at 64 kbps is
processed by LCF number 2 at the BSC. The 16 kbps RSL option is unrestricted
2006 Motorola, Inc.
June 2007
Site Conguration Exercises Version 1 Rev 3
#
BTS SITE 18
equip ___ SITE
>
>
>
>
>
equip ___ CAB
>
>
>
equip ___ CAB
>
>
>
# Load 1.8.0.0 (GSR8)
2006 Motorola, Inc.
2-45
June 2007
Version 1 Rev 3 Kilo-Port Switch
Kilo-Port Switch
The switching of the TDM timeslots are carried out by a KSW or DSW2 at an RXCDR or BSC, while this
function is carried out by a TSW at a BTS. The command used for each one related to KSW.
To equip a KSW/TSW/DSW2 the following command must be entered:
equip <site number> KSW
The site number identies the site in which the KSW/TSW/DSW2 is to be equipped. Valid entries are 0
(or BSC) to 140. This device cannot be equipped at an M-Cell/Horizon site. After the initial command a
series of identiers must be added.
Prompts
1st prompt (highway)
This prompt species which highway is being managed by this KSW/TSW/DSW2. Highway number 0 is
conventionally used rst.
2nd prompt (identier)
This gure species the unique rst identier of this KSW/TSW/DSW2. If set to 0 the board must be tted
in card slot L27, if set to 1 the board should be tted in card slot L1.
3rd prompt (cage)
This gure species the cage where the KSW/TSW/DSW2 has been tted.
4th prompt (DRIMS)
This prompt species if DRIMS are used on the TDM Highway. Yes may only be entered at an in-cell
BTS
2006 Motorola, Inc.
June 2007
Kilo-Port Switch Version 1 Rev 3
Kilo-Port Switch
equip < site number > KSW
enter portion of TDM highway managed: 0
3
enter the TDM identifier: 0 or 1
enter the cage number: BSS 013
RXCDR 0 -13
BTS 152

-
SYS02_Ch4_01
Are DRIMS allowed on the highway: Yes / No

2006 Motorola, Inc.
2-47
June 2007
Version 1 Rev 3 KSW Extension/Expansion
KSW Extension/Expansion
As the TDMhighway function uses timeslot allocation, depending on the size of the site one TDMhighway
may not be sufcient to support the digital boards or may be sufcient to support a number of cages.
A single KSW (1 TDM highway) can be extended to ve digital cages although extension does not
increase the TDM Highway capacity. It is simply the sharing of the available timeslots over a number of
digital cages.
In a large site, 1 TDM highway may not be sufcient to meet the timeslot allocation requirement of the
digital boards. To overcome this the TDM highway can be expanded by interconnecting up to four KSWs.
This would increase the number of timeslots from 1024 to up to 4096 which is the maximum expansion
conguration. When expanded each KSW has access to any of the input ports of interconnected KSW
but can only output to its own 1024 ports.
Extension and expansion is achieved by the use of Kiloport Switch Extender boards. An additional KSW
can be equipped for redundancy, giving 4 KSW pairs when maximum expansion is implemented.
2006 Motorola, Inc.
June 2007
KSW Extension/Expansion Version 1 Rev 3
KSW Extension/Expansion
SYS02_Ch4_04
CLKX R R R R E L
K
S
W CLKX
L L L L
L L L L
R R R R E L
K
S
W
R = Remote KSWX-R
L = Local KSWX-L
E = Expansion KSWX-E
Switch cabinet 0
Extension cabinets 3-4
Extension cabinets 1-2
Cage 0
Cage 1
Switch cabinet 0
Cage
6
Cage
7
Cage
8
Cage
9
Cage
2
Cage
3
Cage
4
Cage
5
2006 Motorola, Inc.
2-49
June 2007
Version 1 Rev 3 DSW2 Extension/Expansion
DSW2 Extension/Expansion
The DSW2 card performs a similar function to the KSW card. However, it doubles the number of ports
from 1024 to 2048 on the TDM highway and has the ability to reduce the subrate switching capacity
down to 8kbps. It may be used at the BSS and RXCDR as a replacement for the KSW (this is required
if Enhanced Allocation Mode is to be used and if AMR Half - Rate is to be supported), or may be used in
conjunction with a KSW if only normal switching is required. The 2048 timeslots of the DSW2 are divided
as follows: Bank 0, 0-1023, Bank 1, 1024 - 2047
The DSW2 in conjunction with the DSWX (and KSW/KSWX) will function in different modes depending
upon what features are required and the location of the switching being carried out. While DSW2 and
KSW may be mixed, DSWX & KSWX may only be mixed in the same cage, as data streams over
connecting bres are incompatible.
DSW2 Operational Modes
Single Rate Mode
In this mode of working, the DSWX will provide standard rate extension to another cage. Only the
timeslots of bank 0 are available, as this is the backwards compatible mode of using a KSW
Bank 1 Extension
In this mode of operation, the timeslots of bank 0 are available to the parent cage only, while the timeslots
of bank 1 are available to the child cage only. The DSWX ensures the correct timeslots are ltered to
the correct cage.
Using DSW2s and DSWXs along with other GSR9 features increases network capacity as follows:
512 carriers to 750 carriers
!00 sites to 140 sites
3200 CICs to 4800 CICs
120K BHCA to 180K BHCA
BSC-XCDR connectivity from 27 to 42
2006 Motorola, Inc.
June 2007
DSW2 Extension/Expansion Version 1 Rev 3
3 1 3 8191 7168
3 0 3 7167 6144
2 1 2 6143 5120
2 0 2 5119 4096
1 1 1 4095 3072
1 0 1 3071 2048
0 1 0 2047 1024
0 0 0 1023 0
HIGHWAY NO BANK SWITCH CAGE TDM timeslot range
Cage & bank allocations expanded RXCDR
SYS02_Ch4_26
2006 Motorola, Inc.
2-51
June 2007
DSW2 Locations
DSW2 - RXCDR / BSS
If the backward compatible mode is being employed at the RXCDR, it will operate in single rate mode,
with only the timeslots in bank 0 available. If Enhanced capacity mode is being used, all 2048 timeslots
will be available, with bank 1 being used in the extension mode, ie 1024 timeslots in the parent cage and
1024 timeslots in the child cage. The BSS will support DSW2 in double rate mode from GSR9.
DSW2 Extension
When the DSW2 is used exclusively throughout an RXCDR site, there will be 2048 timeslots available
to the TDM highway. When extending to a child cage, bank 1 extension results in the highway being
extended to one child cage only from the parent cage. A mirror TDM highway may be equipped for
redundancy. Extension at a BSS site will be as for a KSW with only 1024 timeslots (bank 0) being
available, unless the BSS in working with DSW2 cards in double rate mode.
DSW2 Expansion
In the RXCDR expansion mode of operation, up to 4 pairs of DSW2 may be used in parallel to expand
the highway across 4 cages, (master + 3 expansion). This would allow a total 4 x 2048 = 8192 timeslots.
In a large RXCDR site, each switch cage could be extended to one child cage, giving 8 cages in total.
A mirror TDM highway may be equipped for redundancy. Expansion at a BSS site will be as for a KSW
with only 1024 timeslots (bank 0) being available unless double raet switching is enabled.
Large Site RXCDR/BSC Hardware Conguration
Bank 0 (1024 timeslots) is available to the master, or expansion cage.
Bank 1 (1024 timeslots) is available to all extension cages off that master or expansion cage.
There are up to 4 master/expansion cages, thus supporting 2048 x 4 TS. Actual availability is slightly
less due to some reserved timeslots and fragmentation during assignment. (A minimum of 6 cages is
required for supporting 4800 CICs).
2006 Motorola, Inc.
June 2007
Extension
(up to 2 more)
Expansion
D
S
W
Bank 1
Master
switch
cage
Parent
switch
cage
Parent
switch
cage
Parent
switch
cage
Child non-
switch cage
Child non-
switch cage
Child non-
switch cage
Child non-
switch cage
D
S
W
D
S
W
D
S
W
Maximum Expansion/Extension using DSW
Bank 0
7 N/A 8191 7168
6 0 3 7167 6144
5 N/A 6143 5120
4 0 2 5119 4096
3 N/A 4095 3072
2 0 1 3071 2048
1 N/A 2047 1024
0 0 1023 0
HIGHWAY
NO
BANK SWITCH
CAGE
TDM timeslot range
Cage & bank allocations expanded BSS
0
1
2
3
0
1
2
3
SYS02_Ch4_27
2006 Motorola, Inc.
2-53
June 2007
The double clocking of the TDM highway will allow for maximum (2048 X 4) 8192 TDM timeslots, with
limits of 2048 per DSW2, 1024 per cage. This will allow for additional equipment to be supported, such
as MSIs or PSIs in multiple cages. Although the TDM bus is operating at double rate, the bit rate is
reduced to single rate within individual cages, thus compatible with existing cards. Any device may use
the extra timeslots (GPROCS, GDP, GDP2, EGDP,MSI, PSI XCDR, etc.).
The implementation of double rate TDM along with the DSWs ability to store timeslots in two separate
banks (bank 0 and bank 1), allows the transcoder subsystem to handle twice as much TDM trafc as the
standard rate TDM conguration, thus allowing for double capacity.
The BSC shall detect the switching board types (KSW/KSWX/DSW2/DSWX) at site initialisation; if and
only if both primary and secondary TDM highways fully constitute DSW2/DSWX, the BSC shall enable
enhanced capacity mode. Otherwise the BSC will run in single rate mode.
Note: The BSC initializes in Single Rate Mode (Primary Highway) to perform verication procedures.
Only on completion of these activities and activating all devices will the BSC perform the switching
hardware checks, and if OK will congure the Secondary TDM Highway in Double Rate Mode and swap
to the Secondary TDM Highway to enable Bank0/1 for Enhanced Capacity support with minimal delay.
If the BSS SW at the BSC determines during site initialization that enhanced capacity mode is not
available, the BSS SW at the BSC shall generate an alarm for OOS MMSs disabled due to Enhanced
Capacity Mode unavailable with the reason DSW/DSWX Required. The alarm will be cleared once
all KSW and KSWX switching hardware is replaced by DSW and DSWX switching hardware and the
operator has enabled enhanced capacity mode.
The BSS SW at a BSS shall enable enhanced capacity mode (i.e. from Single Rate Mode to Double
Rate Mode via the reset_device TDM command if the detected hardware contains the master and
redundant DSW2/DSWX. The command will be rejected if the detected hardware contains a KSW/KSWX.
As in the RXCDR, rules will be applied when assigning timeslots to banks 0 and 1 in order to minimize
impact when a BSC is forced out of enhanced capacity mode (e.g. a DSW2 is replaced with a KSW). In
some cases such a transition may cause some conicting devices using TDM timeslots which overlap
others (as per the bank 0/bank1 operation) to be removed from service (as is the case today in the
RXCDR). Note that the RXCDR currently supports this (Enhanced capacity) mode of operation and most
of the above behaviour is already accounted for in the software.
2006 Motorola, Inc.
June 2007
Bank 0/1 Extension
reset_device 0 TDM
reset_device <location><device_name><device_id1>
< device_id2>< device_id3>
location: 0 or BSC BSC
1 to 140 BTS
pcu or pcu_0 PCU
2006 Motorola, Inc.
2-55
June 2007
Version 1 Rev 3 KSW Conguration
KSW Conguration
Overview
When maximum expansion is implemented at a site, four KSW pairs are required with full redundancy.
Each active KSW has to be able to interface to each of the other three active KSWs via KSWX EXP
cards, as well as placing data onto its local highway. Shown opposite is a schematic diagram showing
full expansion, the cards shown as A0, A1, and A2 are expansion slot positions 21, 22, 23 of the upper
shelf and are lled with KSWX cards. The interconnection between these cards is provided by optical
bre. Each of the four highways is provided by a single KSW, redundancy is not shown.
This system is exactly the same for DSW2 cards used in the expansion mode
The chg_ksw_config eld is used to determine the Switch managers viewpoint of the KSW
conguration, specically the mapping of the TDM highway numbers for a particular KSW pair and is
used to equip the Switch Managers database.
Each KSW pair must be informed which highway is being received on which KSWX (A0, A1 or A2) in the
upper shelf. The following table is essential:
I/P KSWX
0 ITSELF
1 A0
2 A1
3 A2
SYS02_Ch4_29
Shown opposite is an example. Take KSW pair 2, physically in cage 2 of the site. H/W 0 is received on
KSWX A0, using the table, gives a value of 1. H/W 1 is received on KSWX A1, using the table gives a
value of 2. H/W 2 is not received by a KSWX card, the KSW in cage 2 is providing this highway, using
the table gives a value of 0 H/W 3 is received on KSWX A2, using the table gives a value of 3.
These prompts will also apply if DSW2 cards are being used in expansion mode.
2006 Motorola, Inc.
June 2007
KSW Conguration Version 1 Rev 3
KSW Conguration
A
2
A
1
A
0
Cage 0
K
S
W
Slot 27
A
2
A
1
A
0
Cage 1
K
S
W
Slot 27
A
2
A
1
A
0
Cage 2
K
S
W
Slot 27
A
2
A
1
A
0
Cage 3
K
S
W
Slot 27
HW 0
HW 1
HW 2
HW 3
Site 0
(Pair 0)
(Pair 1) (Pair 2) (Pair 3)
chg_ksw_config <SITE No><KSW Pair>
<kswx_connected_to_hwy_0><kswx_connected_to_hwy_1>
<kswx_connected_to_hwy_2><kswx_connected_to_hwy_3>
EXAMPLE
SITE KSW P
air
H/W 0 H/W 1 H/W 2 H/W 3
chg_ksw_config 0 0 0 1 2 3
SYS02_Ch4_28
2006 Motorola, Inc.
2-57
June 2007
Version 1 Rev 3 Common Device/Function Equipage
Common Device/Function Equipage
Generic Clock (GCLK)
GCLKs are equipped on a site basis and its functionality can be extended to other cages via clock
extender boards. One GCLK must be equipped per site and two if redundancy is to be implemented.
This device may not be explicitly equipped at M-Cell/Horizon sites, it is automatically equipped with the
rst BTP. The command to equip an In-Cell GCLK is as follows:
equip <site number> GCLK
Device ID
This eld species the unique identier for the GCLK, the card identied as 0 must be tted in card slot
5 and the card identier 1 must be tted in card slot 3
Cage number
The parameter identies the cage in which the GCLK is tted.
CLKX prompts (In-cell sites only)
The three CLKX prompts are used to indicate whether GCLK extension is used at this site, and if so which
CLKXs support it. This is important, as slots U5, U6 and U7 can support either CLKX or KSWX/DSWX
cards, and if the same slot is specied for two cards then the CM must reject the equipage.
2006 Motorola, Inc.
June 2007
Common Device/Function Equipage Version 1 Rev 3
Common Device/Function Equipage
equip < site number > GCLK
enter the device identification for the GCLK: 0/1
enter the cage number: 015
Is CLKX 0 (slot U7) present? Yes No
SYS02_Ch4_30
2006 Motorola, Inc.
2-59
June 2007
Version 1 Rev 3 GCLK Synchronisation
GCLK Synchronisation
Overview
This feature will provide frequency synchronisation of the GCLK output signals based on the standard
provided by an incoming 2 Mbit/s link. The aim of GCLK synchronisation is to provide RF carrier
frequencies to within +/- 0.05 ppm. Synchronisation to an E1 or T1 link will also minimise frame slips
and reduce the frequency of on site calibrations.
The network clock should be maintained at +/- 0.01 ppm of 2.048 MHz (E1) or 1.544 MHz (T1). To
maintain synchronisation the clock data should have no breaks greater that 80 micro seconds. The
synchronisation circuit resides on the GCLK card tted at every site. This feature will operate with BTSs
connected in star, daisy chain and loop topologies.
In order to phase lock, a GCLK must have a span assigned as a reference source. Parameters in the
database can be used to specify priorities applicable to each span at a site. These priorities will be used
to determine the order of selection of spans as a reference source
There are four modes that the GCLK board can operate in, these are: Free Run, Hold Frequency, Set
frequency and Closed loop.
Free Run
When a GCLK is inserted into the digital cage (or on power up) a 30 minute warm up period is required
for the ovenised crystal oscillator (OXCO) to reach the correct operating temperature, during this time
the GCLK is in free run mode and the input to the DAC is set to 80(hex). The value 80(hex) cannot be
changed. The OXCO in free run mode will produce a clock output of 16.384 MHz accurate to 0.05ppm,
assuming the GCLK is in calibration.
Note:The 30 minute warm up period is set by Motorola but may be changed by us eof the database
parameter gclk_qwarm_flag, providing the feature is unrestricted and the GCLK Is version 9 or later.
Hold Frequency
Phase lock mode means the GCLK is synchronized to a clock froman uplink site. Hold frequency is when
a GCLK has previously had frequency lock and the reference clock suddenly disappears. This mode
uses the last 8 bit word output from the ADC to set the DAC. The hold frequency mode is a transitional
mode (typically 10 secs) until the set frequency mode is activated by the software.
Set Frequency
The Set Frequency mode allows the software to use the LTA to set the DAC to control the output of the
OXCO during loss of the 2.048 MHz reference signal (this is after the transitional Hold Frequency mode).
2006 Motorola, Inc.
June 2007
GCLK Synchronisation Version 1 Rev 3
f
in
Input signal
2.048 MHZ
OSC.IN
LOCK DET
LPF
ADC DAC OXCO
16.384 MHZ
Vref
GPROC (MCAP data bus)
Control
Reference Fail Detect
V
in
Divide by
8
EN
256 KHz
Conv.CS
80(Hex)
Buffer
OE
Read Freq
Latch
OE
16.384 MHZ
Set Freq
Latch
OE
Calibration
Adjust
Feedback
output
signal
Phase
Detector
2006 Motorola, Inc.
2-61
June 2007
Closed Loop Mode
Within the closed loop mode there are two sub modes or states:
Acquiring Frequency Lock State
Frequency Lock State
The acquiring frequency lock state is the operating condition where the GCLK PLL output is converging
towards the long term frequency of the E1/T1 line. The time spent in this state is dependant on the
hardware revision level of the GCLK board, current build boards will be in this state a maximum of 2
minutes, typically much less. Once this state is reached (i.e. the output is within GSM specications) the
second sub state, frequency lock state is activated.
This mode is again dependant on the GCLK hardware revision level (either 2 or 10 minutes), and is used
to conrm that the GCLK output is stable within the GSM specication for the set period (2/10 minutes).
The following command is used to enable or disable phase locking at a site:
chg_element phase_lock_gclk <*> <location>
Should the chosen span subsequently go oos a GCLK reference fail alarm will be initiated. The following
timer controls the time the system will wait before selecting another span for extraction. If the current
span returns to ins before the timer expires then it will remain the clock extraction source.
chg_element wait_for_reselection <*><location>
To enable the GCLK to synchronise to an E1 or T1 a suitable source must exist. The priority for source
selection is:
1. MMS in service.
2. Priority of MMS (database parameter)
3. Number of times the MMS has gone oos in a given period
4. If priority and MMS oos are equal the order of selection of sources shall be on a rotation basis.
The priority of each MMS can be individually set by the command:
modify_value <site> mms_priority <*> mms <mms_id 1> <mms_id 2> <mms_id 3>
2006 Motorola, Inc.
June 2007
chg_element phase_lock_gclk <*> <site>
* 0 Disable phase locking
* 1 Enable phase locking
0 Default
chg_element wait_for_reselection <*> <site>
* 0 86400 (seconds)
Default = 10
modify_value <site> mms_priority <*> mms <mms_id 1> <mms_id 2> <mms_id 3>
* 0 255 0 MMS will not be selected
1 Lowest priority
255 Highest priority
2006 Motorola, Inc.
2-63
June 2007
A count of the number of times the MMS goes oos is kept to enable the prioritizing algorithm to function.
A reset period is used to delimit the time for which an oos count is held. It is set using the database
command shown below. At the end of each reset period the oos count is reset to zero and the count
begins again.
chg_element clk_src_fail_reset_period <*><location>
After initialisation of the site the GCLK will attempt to synchronise to the chosen MMS, the time duration
taken for this synchronisation will vary depending on the hardware revision level of the card. If the
synchronisation has been maintained for phase_lock_duration the CA will declare the GCLK phase
locked. The default value for this variable is 0 which indicates that there is no change from the minimum
period dened for the revision level of the GCLK. The variable may be set on an mms basis to account
for different transmission media.
modify_value<location>phase_lock_duration <*> mms <mms_id 1> <mms_id 2>
<mms_id 3>
The GCLK is polled once every 30 minutes to establish the current 8 bit DAC value. A rolling average
mechanism of the previous 48 DAC values (24 hours in time) produces a Long Term Average (LTA).
This average is used as the DAC setting in the case of 'Set Frequency Mode'. Every polling period the
previous 48 averages are checked against the current LTA. If 25% of the values vary by a specied range
an alarm is then raised. The range is specied as follows:
chg_element lta_alarm_range <*> <location>
2006 Motorola, Inc.
June 2007
chg_element clk_src_fail_reset_period <*> <site>
* 1 255 Hours
Default = 24
modify_value <site> phase_lock_duration <*> mms <mms_id 1> <mms_id 2> <mms_id 3>
* 0 Default, GCLK revision level dependant, any mms details ignored
1 3600 seconds, mms details used
chg_element lta_alarm_range <*> <site>
* 1 - 255
Default = 7
2006 Motorola, Inc.
2-65
June 2007
Version 1 Rev 3 Base Site Processor (BSP)
Base Site Processor (BSP)
The BSP is the master processor type at a BSC and also at a RXCDR. Its functionality is dependant
upon the BSC type, at the smallest BSC it will carry out the majority of any processing required, then as
the BSS grows in functionality certain software entities migrate away from BSP and use other processor
types which must be created. To equip a BSP the following command must be used:
equip <site number> BSP
Prompts
This prompt gives the BSP its unique identier, a maximum of two BSPs can be equipped at any one
site, the second being redundant
2nd prompt (cage)
This identies the cage in which the BSP is to be equipped.
3rd prompt (slot)
Valid card slots are 20/24 for a BSU cage and 25/26 for an RXU cage.
2006 Motorola, Inc.
June 2007
Base Site Processor (BSP) Version 1 Rev 3
Base Site Processor (BSP)
equip <0 or
bsc> BSP
enter the BSP identifier:
0/1
enter the cage number:

0/1
enter the slot number:

20/24(BSS)
25/26 (RXCDR)
SYS02_Ch4_31
2006 Motorola, Inc.
2-67
June 2007
Version 1 Rev 3 Code Storage Facility Processor (CSFP)
Code Storage Facility Processor (CSFP)
The Code Storage Facility Processor (CSFP) is a GPROCdevice which facilitates the propagating of new
software instances with reduced system downtime. A software instance is a complete set of software
and rmware objects including the database object.
New software loads can be down loaded from the OMC-R to the BSS and consequently from the BSS
to BTS. Without a CSFP this down load will result in system downtime whilst the BSS or BTS is in ROM
utilising the IP. This system downtime is dependent on link throughput (number of OMLs) and system
topology (number and connection of BTSs). If used, the CSFP will reduce this system down time as the
down load can take place to the BSS or BTS whilst the system is on-line and call processing.
After the software has been down loaded to all entities in the BSS, a special BSS reset is performed
for the activation of the new software instance. Since the new software instance exists locally, network
outage time is drastically reduced.
The CSFP feature also provides optional CSFP fall back. As previously described a new software
instance is distributed to all CSFPs in a BSS. After the reset, all non-CSFP GPROCs begin executing
the new software load, while the fallback CSFP retains the old software load.
At M-Cell / Horizon sites, this device cannot be explicitly equipped. It is automatically equipped with the
rst BTP.
To equip a CSFP the following command must be used:
equip <site number> CSFP
Prompts
1st prompt (identication)
This parameter identies the CSFP within site 0 only. At sites 1-140 the prompt will not appear.
2nd prompt (cage)
This eld identies the cage in which the GPROC acting as the CSFP has been tted.
3rd prompt (slot)
This eld identies the cage slot position in which the GPROC acting as the CSFP has been tted.
2006 Motorola, Inc.
June 2007
Code Storage Facility Processor (CSFP) Version 1 Rev 3
Code Storage Facility Processor (CSFP)
equip <site number> CSFP
enter the CSFP identifier
(only prompted at site 0)
0/1
Enter the cage number:
BSS 013
RXCDR 0 13
BTS 152
Enter the slot number

1825 (BSU)
2526 (RXU)
SYS02_Ch4_32
2006 Motorola, Inc.
2-69
June 2007
Version 1 Rev 3 Multiport Serial Interface (MSI)
Multiport Serial Interface (MSI)
The equip command associated with an MSI can equip a number of 2Mb termination modules namely
the MSI, XCDR, GDP, GDP2 and the NIU. The MSI, NIU & GDP2 modules are capable of terminating
2 x 2Mb links, where as a XCDR and GDP board can only terminate one E1 2Mb link. chg_element
land_layer1_mode is the database command which will enable either a T1 or E1 network to function,
and it is written on a BSS basis, ie all termination modules within the network will terminate in the same
L1 mode.
The prompts associated with the equip MSI command are dependant upon the type of site, M-Cell /
Horizon or In-Cell.
2006 Motorola, Inc.
June 2007
Multiport Serial Interface (MSI) Version 1 Rev 3
Multiport Serial Interface (MSI)
MSI
MSI_EXT_HDSL
XCDR
GDP
GDP2
NIU / NIU2
NIU_HDSL
NIU_EXT_HDSL
Incell
M-cell / Horizon / Horizon2 -
SYS02_Ch4_24
2006 Motorola, Inc.
2-71
June 2007
Version 1 Rev 3 In-cell MSI
In-cell MSI
In-Cell
equip <site number> MSI
Identier
The eld species a unique identier on site type
Cage
This prompt species the cage in which the termination card is tted.
Slot
The eld species the slot in which the module is tted, restrictions exist depending upon default positions
and cage type (BSU and RXU). Conventionally, in the rst cage, slot 17 is always allocated to MSI 0.
Type
The eld species the module type tted, MSI, XCDR, GDP or GDP2.
Protocol type MMS 0, MMS 1
These prompts only appear if the integrated MSI HDSL feature is enabled and the msi_type is
niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.
Timeslots supported on MMS 0, MMS 1
niu_hdsl, niu_ext_hdsl or msi_ext_hdsl and the protocol type is HDSL.
Modem setting on MMS 0, MMS 1
niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.
MSC MSI
This prompt only occurs if the selected MSI type is GDP or GDP2. If the value is the same as the
MSI identier of the GDP/GDP2 being equipped, it is classed as a primary GDP card. If not, it will be
considered a secondary GDP (only applies when 2 GDPs equipped as a pair).
Transcoding Capability
This prompt determines if the GDP supports basic transcoding, enhanced transcoding or enhanced
transcoding while providing 2 E1 links.
2006 Motorola, Inc.
June 2007
In-cell MSI Version 1 Rev 3
In-cell MSI
In-Cell
equip (site number) MSI
enter the MSI identifier: 055 (BSS)
09 (BTS)
0123 (RXCDR)

enter the cage number: 013 (BSS)

0 13 (RXCDR)
15 2 (BTS)
enter the slot number: BSS, BTSs: 617

RXCDR: MSI type 0: 6 10
MSI type 1: 624

enter the MSI type:

0 MSI
1 XCDR
2 GDP
5 msi_ext_hdsl
20 GDP2
SYS02_Ch4_25
enter MMS 0 protocol type E1 or HDSL
enter number of timeslots supported on MMS 0: 16 or 32
enter MMS 1 protocol type: E1 or HDSL
enter modem setting of MMS 0: Master or slave
enter modem setting of MMS 1: Master or slave
enter the GDP MSI id to the MSC 0-55 (BSS)
0-123 (RXCDR)
0
enter the Transcoding capability
0 = basic
1 = enhanced
2 = GDP_2E1
SYS02_Ch4_39
2006 Motorola, Inc.
2-73
June 2007
Version 1 Rev 3 BSC PSI
BSC PSI
GSR9 has introduced a Packet Switch Interface (PSI) board into the BSC to provide a high bandwidth
GbE interconnect between the GSM BSC and the PCU cage. This feature was requested to reduce
the number of cables needed between BSC and PCU; therefore higher capacity congurations could be
handled by the BSC. Target customer is heavy EDGE users, where the number of E1s required to the
PCU results in lower site capacity on the BSC. Instead of using 2 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. The BSC shall
allocate 32 TDM timeslots per block for the PSI. A PSI can process 480 timeslots onf EDGE data itself
and the constraint lies in the TDM highway timeslot allocation. The freed MSI slot can be used for 2
downstream or upstream span lines.
The PSI is a Packet Subrate Interface card. There will be a max of 12 PSI per BSC and the BSC will
support a maximum of 4 PSIs per cage (if other MSI slots are empty). A Maximum of 3 PSIs per cage
recommended due to power supply limitations. The PSI device will occupy an MSI slot in the current
BSC cage, restricted to slots 6, 7, 12 and 13 due to top of cabinet interconnect. The PSI cards primary
function is to terminate GPRS TRAU and transfer the TRAU payload to the PCU (PXP) over Ethernet.
Other card functions include MCU access to packet data and up to 128 channels of HDLC data via the
backplane.
The physical interface from the PSI card is a 1000BASE-T over 4 pairs of copper wire. This same
connection can be operated in 100BASE-TX mode of operation as well, utilizing 2 pairs of copper wire.
(The dual 100 Mbps links, available as an alternative to the 1000BASE-T, are disabled at all times.) The
standard backplane connections can be used, with a PBIB-ES or PT43-ES board replacing the BIB or
T43 board, respectively, at the top of the cabinet. The path has to be a direct connection with CAT5E
cable, less than or equal to 100m in length.
On the PBIB-ES, the rst two ports allow for balanced span line connections. The 3rd port connects a
single Gigabit Ethernet from the PSI card into a RJ45 connector. This link is referred to generically as
the Ethernet Link unless it is required to specify 100BASE-TX or 1000BASE-T modes of operation.
On the PT43-ES, the rst two ports are used for unbalanced coaxial cable connections and the 3rd
port is used for the Gigabit Ethernet (using a RJ45 connector). The same electrical characteristics and
protection for the unbalanced coaxial cable connections provided by the T43 board shall be provided for
the PT43-ES. A new cover is also be provided with the PT43-ES.
Each PSI is connected point-to-point to a DPROC2 card in the PCU. The maximum number of PCUI
cages supported in GSR9 is 1 and there are at most 12 DPROC2s in the PCU cage; therefore there is
a maximum of 12 PSIs per BSC. Power and TDM timeslot constraints are such that each BSC cage will
support 0, 1 or 2 PSIs.
The PSI shall be equipped as a new child device of the cage. Its child shall be the ETH device
representing the physical link between PSI and DPROC2. The BSC will support codeloading for all
DSPs and initialization of the PCU through the PSI card. TDM timeslot usage of the PSI card shall be
determined during initialization. The PSI itself can support up to a full 1024 TDM timeslots (unrealistic).
Hardware specic information will be presented when disp_equipment with the full option is used. The
PSI device will be equipped/unequipped/modied inside or outside of SYSGEN mode. The ETH is
automatically equipped/unequipped when the parent PSI is equipped/unequipped.
2006 Motorola, Inc.
June 2007
BSC PSI Version 1 Rev 3
BSC PSI
Functionality: GDS/GSL Hierarchy Diagram
Cage
GDS (LAPD)
MMS
MSI
GDS (TRAU)
MMS
MSI
GSL
PSI
GDS (LAPD_TRAU)
ETH
GSL
BSC Equipment Hierarchy Mixed config
ETH*
BSS
BSC SITE
CAB
CAGE
LCF
GPROC
OMF
PSI
Glossary:
ETH : Ethernet Port
GSL : Signalling Link to ePCU
GDS : Path between PSI ETH and
U-DPROC2 ETH
GDS** (LAPD_TRAU)
GSL
GSL***
GDS-TRAU
GDS (LAPD)
GSL
MSI
MMS MMS
TDM highway
* Auto-equipped
** Supports TRAU and LAPD
*** Assigned to an LCF by FM
: New device
2006 Motorola, Inc.
2-75
June 2007
BSC PSI
PSI MCU Software
One PSI has a MCU (MPC8260 controller ) and 17 DSPs. (16 working, 1 testing).
The MCP8260 controller performs the following functions:
Responsible for code-load for all DSPs
Responsible for setting up the TDM highway maps
DSP resource management for TRAU connection
TDM timeslot management for TRAU connection
Terminates all 64k HDLC links for GSLs. Data is routed through the on-board ethernet switch to
the GbE port
MCU will collect stats and alarms
DSP functions
Each DSP can support 35 carriers and can support 30x32K PDCH, or 30x64K PDCH, or 60x16K PDCH
Essentially does the same functions as the NIB code for TRAU-GDS.
Performs TRAU header hunting
Performs dibit extraction
Responsible for ensuring each timeslot of the TDM has data every block period
Inserts idle frames if data for a timeslot isnt received from PCU in time
Bundles data from the same carrier into a single UDP packet
PSI and PXP are in pairs, If either of the pair fails, both are taken OOS. Up to 12 PSI/PXP pairs can be
equipped. Signalling and trafc load is shared amongst in-service PSI/PXP pairs. If one pair fails, the
load is redistributed amongst remaining in-service PSI/PXP pairs.
2006 Motorola, Inc.
June 2007
BSC PSI
The (GbE) Ethernet connection between
BSC and ePCU
2006 Motorola, Inc.
2-77
June 2007
BSC PSI
MMI Commands
equip BSC PSII
Enter the PSI identier:
Enter the slot number:
Enter the number of TDM timeslot blocks:
Enter the maximum number of GSLs on this PSI:
Enter the PCU base GDS IP Address:
Enter the PCU GDS Subnet Mask:
Enter the PCU GDS Router IP Address:
Enter the WebMMI IP address:
Enter the WebMMI subnet mask:
Enter the WebMMI router IP address:
Enter the NSEI value:
Enter the PRP Fanout Mode:
Notes : PRP Fanout Mode element will be skipped and set to the default value during the PCU equipage
when Increase the Throughput of PRP is restricted. The BSC will default the gds_subnet_mask ,
gds_router_ip_address and prp_fanout_mode during the PCU equipage if no value is entered.
tdm_ts_blocks (No. of TDM 32-timeslot blocks reserved for this PSI)
Range 2 to 10 (Default=2)
max_gsls (max no. of GSLs supported by this PSI)
Range 0 to 30 (Default=0)
The BSS will support a maximum of 180 GSL links per PCU.
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. This is auto equipped.
parent_device (identies the parent device of ETHernet) Value 1 or PSI Value 2 or DPROC
device_id 1st identier: PSI unique identier 2nd identier: identier Ethernet port
Note: The BSC supports the modify_value command for the PSI parameters tdm_ts_blocks and
max_gsls and for the base_ip_address parameter.
2006 Motorola, Inc.
June 2007
BSC PSI
MMI Command Equip BSC PSI
Parameter Min Max Default Type Access Description
device_id 0 11 N/A 1 RC First device ID. Second and third IDs are optional
and shall be set to 0.
cage 0 15 N/A 1 RC Cage number
slot 6 13 N/A 1 RC Slot number
tdm_ts_blocks 2 10 2 3b RW Number of TDM 32-timeslot blocks reserved for PSI
max_gsls 0 30 0 3b RW A maximum number of GSLs that will be supported
on this PSI.
base_ip_address 0.0.0.1 255.255.255.
237
N/A 3b RW The base IP address to be used for the MCU. There
must be 17 contiguous addresses available
after the base address for the DSPs. The IP
address shall be entered in dotted quad
notation.
subnet_mask 255.0.0.
0
255.255.255.
224
255.255.255.
0
3b RW Subnet mask
router_ip_address 0.0.0.0 255.255.255.
254
0.0.0.0 3b RW The IP address of the router. The value of 0.0.0.0
means no router is in use.
Enter the PSI identifier:
Enter the slot number:
Enter the number of TDM timeslot blocks:
Enter the maximum number of GSLs on this PSI:
Enter the PCU base GDS IP Address:
Enter the PCU GDS Subnet Mask:
Enter the PCU GDS Router IP Address:
Enter the WebMMI IP address:
Enter the WebMMI subnet mask:
Enter the WebMMI router IP address:
Enter the NSEI value:
Enter the PRP Fanout Mode:
2006 Motorola, Inc.
2-79
June 2007
BSC PSI
Additional Database Elements
New database elements have been introduced to support this feature:
eth_tx_errors_threshold - The new per BSS element species the maximum allowable percentage of
Ethernet transmit errors of all frames transmitted:
Range 0-100%: 0 = turn off. There is no alarm generated. The percentage parameter will be on a per
BSS basis. The default will be 10%.
dsp_error_inc - Value 0-255
Default: This parameter will be defaulted to 1 when the ECERM features is unrestricted and 0 (feature
turned off) if ECERM feature is restricted.
Dependencies: The dsp_error_inc parameter is restricted by the Enhanced Circuit Error Rate Monitor
restrictable feature. When the dsp_error_inc parameter is set to 0 outside of sysgen mode, the operator
is warned that this will prevent any more DSP alarms from being generated.
dsp_error_gen_thresh - This is a new database parameter which identies the value which the error
count must be equal to or greater than for an alarm to be generated for a DSP - Value 2-255
Default: This parameter will be defaulted to 6.
Dependencies: The dsp_error_gen_thresh parameter is restricted by the Enhanced Circuit Error
Rate Monitor restrictable feature. The parameter is restricted so that at least two GPRS Alarm
Increment/Decrement Time Periods must pass without a sync loss error occuring on a resource before
an alarm can be cleared. It is necessary to look for sufcient successes to avoid clearing the alarm on
one or more successful GPRS Alarm Increment/Decrement Time Period that had too short a duration
for the CCU to time out and send an error indication.
dsp_error_clr_thresh - This is a new database parameter which identies the value for which the error
count must be equal or less than for an alarm to be cleared for a DSP - Value 0-253
Default: This parameter will be defaulted to 0.
Dependencies: The dsp_error_clr_thresh parameter is restricted by the Enhanced Circuit Error Rate
Monitor restrictable feature. The parameter is restricted so that at least two GPRS Alarm Increment Time
Periods must pass without a sync loss error occurring on a resource before an alarm can be cleared.
It is necessary to look for sufcient successes to avoid clearing the alarm on one or more successful
GPRS Alarm Increment Time Period that had too short a duration for the CCU to time out and send an
error indication.
psi_trau_ll_frames_threshold: The new per BSS element species the maximum allowable
percentage of all TRAU frames transmitted that can be ll frames
Value 0-100: 0 = turn off. There is no alarm generated. The percentage parameter will be on a per BSS
basis. The default will be 10%.
eth_rx_errors_threshold: The new per BSS element species the maximum allowable percentage of
Ethernet frames received in error of all frames received
Value 0-100: 0 = turn off. There is no alarm generated. The percentage parameter will be on a per BSS
basis. The default will be 10%.
2006 Motorola, Inc.
June 2007
BSC PSI
New Database Elements
psi_trau_fill_frames_threshold Range 1-100% (Default=10)
eth_rx_errors_ threshold Range 1-100% (Default=10)
eth_tx_errors _threshold Range 1-100% (Default=10)
dsp_error_inc Value 0-255 (Default=1)
dsp_error_gen_thresh Value 2-255 (Default=6)
dsp_error_clr_thresh Value 0-253 (Default=0)
2006 Motorola, Inc.
2-81
June 2007
Version 1 Rev 3 BSC Types
BSC Types
GPROCs are software machines. Their functionality is dependant upon the size or type of site.
That GPROC becomes a certain processor type depending on whether it is at a BSS or BTS.
As the site increases in size the software processes necessary to support the site become too large
to reside on one GPROC so some of those processes are moved onto another GPROC creating other
processor types. The site will then become another BSC/BTS type.
With the increased loading required by the BSS, more processing will be required to support the signalling
coming into and going out of the BSC. The software processes that support this is the Message Transfer
Part (MTP) and the Signalling Connection Control Part State Machine (SSM). These two processes
reside on a device type called a Link Control Function (LCF). This is a BSC Type 1.
The largest type of BSC is a type 2. As the amount of signalling is increased this can be catered for
by adding additional LCFs. The bottle neck will now probably be the BSP. To reduce the load on the
BSP the Operations and Maintenance System is placed on its own processor type, the Operations and
Maintenance Processor (OMP).
A number of features introduced for GSR9 increases the capacity of the BSC to 750 carriers / 4800
circuits. For this to occur all GPROCs tted must be of the type GPROC2, GPROC 3 or GPROC32..
The AMR features introduced already increased the number of circuits at a RXCDR to 4800..
2006 Motorola, Inc.
June 2007
BSC Types Version 1 Rev 3
BSC Types
BSC Type 1
BSP LCF LCF
CLM
SM
OMS
MTP
SSM
MTP
SSM
BSP OMF LCF LCF
CLM
SM OMS
MTP
SSM
MTP
SSM
BSC Type 2
2006 Motorola, Inc.
2-83
June 2007
Version 1 Rev 3 BTS Types
BTS Types
There are two types of BTS, types 0 and 1. The smallest is a type 0 where all of the software processes
required to support the BTS are resident on one GPROC called the Base Transceiver Processor (BTP).
As the BTS grows the RF equipment will require the most processing so the relevant software process,
the Radio Sub System (RSS), is moved from the BTP and placed on a new processor type, the Digital
Radio Host Processor (DHP). This is a BTS type 1.
If the feature "BIG BSC" is unrestricted, then the GPROC which hosts the BTP software must be a
GPROC 2, GPROC 3 or GPROC32.
This parameter is not necessary at M-Cell or Horizon sites.
2006 Motorola, Inc.
June 2007
BTS Types Version 1 Rev 3
BTS Types
BTP
RRSM
CRM
RSS
BTP
RRSM
CRM
DHP
RSS
DHP
RSS
BTS Type 0
Type 1
2006 Motorola, Inc.
2-85
June 2007
Version 1 Rev 3 BSC/ BTS Types
BSC/ BTS Types
If the incorrect site type is entered in the database problems will arise during the initialisation process.
The site will be down loaded as normal, but on conguration, discrepancies will arise in the database.
If for example a BTS site was congured as a type 1 instead of 0 on conguration it will expect to nd
GPROCs to become Digital Host Processors (DHP) which may not physically be either there or equipped
in the database. Therefore, conguration of the site will not take place.
2006 Motorola, Inc.
June 2007
BSC/ BTS Types Version 1 Rev 3
BSC/ BTS Types
chg_element bsc_type <*><SITE No>
chg_element bts_type <*> <SITE No>
(not required at M-cell or Horizon sites)
* 0 = BTS type 0
1 = BSC/BTS type 1
2 = BSC type 2
Sys02_Ch2_26
2006 Motorola, Inc.
2-87
June 2007
Version 1 Rev 3 GPROC Slots
GPROC Slots
Data, which is primarily trafc, will be coming into and going out of the BSS on the 2.048 Mbit/s links.
All downlink trafc data going into the transcoder function will be serial PCM at 64 kbps and after the
transcoding function will be at 16 kbps. On entering the BSS equipment it is converted from serial to
parallel and routed within the equipment via the TDM highway.
The TDM highway is interfaced by all full sized boards with the exception of the Generic Clocks. All
boards are allocated timeslots during which to take the data off and for putting the data on. The Kiloport
Switch (KSW) provides the timeslot interchange function.
The Generic Processor (GPROC) boards need to interface to the TDM highway for transmitting
information between the BSC and MSC (SS#7), all control and management information from the
OMC-R including software down loads (X.25) and all signalling between BSS GPROCs and BTS
GPROCs (LAPD) must go over the 2.048 Mbit/s links. The only way that the GPROCs can interface to
this signalling data is via the TDM highway. The GPROC is able to support up to thirty two 64 kbps serial
channels, however GPROC 1 will only support 16. GPROC 2, GPROC 3 and GPROC 32 will support
16 and 32 timeslots and if tted at a BSS, 24 will be a valid entry (if the EGPRS feature is unrestricted).
If a value of greater than 16 is entered, the operator will be warned that GPROC 2 or GPROC 3 boards
are required.
GPROC 3s are required to run GSR8 software.
2006 Motorola, Inc.
June 2007
GPROC Slots Version 1 Rev 3
GPROC Slots
chg_element gproc_slots < * > SITE No.
* 16 (default)
24 BSC only
Sys02_Ch2_27
32 GPROC2, GPROC3 or GPROC3 - 2
2006 Motorola, Inc.
2-89
June 2007
Version 1 Rev 3 Generic Processor Equipage
Generic Processor Equipage
Depending on the site type, certain software processes and functions will have to be created to support
the site functionality. When a function such as an LCF, or OMF is to be equipped then a GPROC platform
must be equipped in advance to support it. In the case of a processor such as a BSP or BTP the GPROC
platform does not have to be previously equipped, see the dependency table at the beginning of this
section. This device cannot be equipped at an M-Cell / Horizon site.
There are 4 types of GPROC available, GPROC 1, 2, 3 & 32. While they all perform similar functions,
each type sees an increase in performance over its predecessor. In addition the number of TDM slots
they can deal with are different. A GPROC 1 may not be tted at a BSC, and a GPROC 3 must be used
if the software is GSR8.
To equip a GPROC of any type the following command must be entered:
equip <site number> GPROC
Prompts
This prompt species the unique identier of the GPROC.
2nd prompt (cage)
This gure species the cage where the GPROC has been tted.
3rd prompt (slot)
This gure denotes the card slot location of the GPROC being equipped.
2006 Motorola, Inc.
June 2007
Generic Processor Equipage Version 1 Rev 3
Generic Processor Equipage
enter the GPROC identifier: 1111
enter the cage number
BSS 013
RXCDR 0 -13
152
enter the slot number

BSS 1825
RXCDR 2526
BTS 1825
SYS02_Ch4_35
equip <site number > GPROC
BTS
2006 Motorola, Inc.
2-91
June 2007
Version 1 Rev 3 GPROC Function Pre-emption
GPROC Function Pre-emption
In the event of a GPROC which is hosting a high priority function going out of service, but where there
is no alternative pool GPROC in an Enabled-Unlocked condition available to host the function, the new
feature GPROC Function Pre-emption searches for a Busy-Unlocked GPROC running a lower priority
function. If such a GPROC is found, the lower priority function is pre-empted by the higher priority
function.
For example at a Type 2 BSC, the ATER channel allocation is hosted by the OMF (rather than the BSP) to
reduce the load on the BSP. IF the OMF goes out of service, calls cannot be processed because the XBL
also terminates on the OMF, and if the XBL is disabled, the circuits are blocked. Thus the OMF becomes
the highest priority function and critical to the operation of the BSS. For call processing to continue it
must be re-hosted by an alternative GPROC. Pre-emption is reasonable to allow this to occur, and the
function would move to a B-U GPROC hosting a lower-priority function.
The pre-emption function is enabled by the parameter.
chg_element pool_gproc_preemption whose settings are:
0 No pre-emption
1 Function level pre-emption
2 Intra Function pre-emption
Function level pre-emption operates by pre-empting a function of a lower priority than that which has lost
its host. If no lower priority functions are available on any GPROC, the feature stops.
Intra-Function pre-emption rst seeks a function of a lower priority, but if it does not nd one, then seeks
a lower priority function within the function type which has lost its host GPROC.
GPROC function pre-emption searches for a Busy-Unlocked (B-U) GPROC running a lower priority
function when a GPROC hosting a higher priority function goes out of service, and there are no
Enabled-Unlocked (E-U) GPROCs to host the higher priority function. If such a GPROC is found,
the lower priority function will be pre-empted by the higher priority function. The operator is able to
determine the pre-emption algorithm to be used by use of a database element.
2006 Motorola, Inc.
June 2007
GPROC Function Pre-emption Version 1 Rev 3
SYS02_Ch4_36
GPROC
BSP
GPROC
OMF
OMF Process
GPROC
LCF
OMF Process
GPROC
Pool
Failed
pool_gproc_pre-emption <*>
* 0 = No pre-emption
1 = Inter-function pre-emption
2 = Inter-function and intra-function pre-emption
change_element
2006 Motorola, Inc.
2-93
June 2007
Version 1 Rev 3 GPROC Function Pre-emption
Function Priority
The BSS software uses the function type and function ID to determine the order in which functions are
brought into service. The ordering of function type is OMF rst, then LCF second. Functions with lower
IDs are brought into service before functions with higher IDs. This priority scheme allows the operator
to arrange functions in order of importance. When a pool GPROC comes into service, it selects the
Enabled-Equipped (E-E) function with the highest priority.
For example, there are ve functions dened for a particular site: OMF 0, LCF 0, LCF 1, LCF 2, and LCF
3. OMF is a highest priority function than the LCFs. However LCF 1 has higher priority than LCF 2 and
LCF 3, but has lower priority than LCF 0.
OMF
0
LCF
0
LCF
1
LCF
2
LCF
3
Lower Priority
Lower Priority
Function
ID
Function
ID
SYS02_Ch4_37
2006 Motorola, Inc.
June 2007
GPROC Function Pre-emption Version 1 Rev 3
GPROC goes out of
service
Pool GPROC
free?
Lower priority
B-E function?
Yes
Search functions
pre-empt lower
priority function by
resetting its
GPROC
Do nothing
Free GPROC
takes function
No
Yes
No
SYS02_Ch4_38
2006 Motorola, Inc.
2-95
June 2007
Version 1 Rev 3 LCF Memory
LCF Memory
GSR9 introduces a higher capacity BSC in terms of carriers, sites, CICs, etc. and as such requires
additional memory for the database object as well as the normal increase in object size due to adding
functionality in typical features in a release (such as DTM and QoS.) The GSR9 load will exceed the
GPROC2 maximum available memory. This GSR9 software feature will save some LCF memory (about
3.5M) to prolong the life of existing GPROC2.
It will not load GPROC2 with PSI object, GPROC3-2 PQ2 object and PCU related objects in
the initialization of a GPROC2 or BSC. It also removes half of the BTS objects from each of the
GPROC2-LCFs in order to save memory
During a BTS site initialisation, the pool GPROC2 and GPROC3 have higher priority to be selected as
source to download the BTS. If there is no available pool GPROC2 or GPROC3 for code loading, the
BSC uses two GPROC2 LCFs as source to download the BTS. Each GPROC2 will have a different half
of the BTS objects.
In the two source GPROC2-LCFs, only one is assigned as the controller, the other one just function as a
2nd source. A GPROC can be assigned as the 2nd source for multiple download controllers at a time. As
a controller GPROC only supports one BTS download at a time, the number of parallel BTS downloading
is determined by the number of total available GPROCs in the BSC. In GSR9, this number will be same
with pre-GSR9 releases.
A pool GPROC2 contains all the BTS objects. When a pool GPROC2 is assigned as LCF or OMF, the
BSC will determine which group of objects this board will store, and then BSC commands the board to
delete BTS objects which are not in the selected group. After half of the BTS objects are removed, the
GPROC2 will have enough memory for starting the LCF or OMF function. The controlling IP use the
objects on the local board and 2nd board to download the BTS.
When a single GPROC2 jumping into RAM needs to be assigned as a LCF, the same scenario happens
to the GPROC for stripping half of BTS objects. After a GPROC2 is assigned as a LCF, BSC CA will
determine which group of BTS objects this LCF will store and will label the LCF with a group ID, the range
of ID is 0 or 1. The CA will save the BTS objects grouping information internally.
After a BSC jumps into RAM state, the BSC will divide the BTS objects except for those used by both
BSC and INCELL BTS into 2 groups (0 and 1). The size of objects in the 2 groups should be closely
even.
Note: The recommended value for the difference is less than 100Kb.
The BSC will delete a BTS object from a LCF if the object has a different object group id as the LCF
group id.
Before the CA starts the LCF function on a GPROC2, the CA will send a message to GPROC2-LCF
COM to purge the BTS objects unneeded for this board, by using the existing COM interface.
A GPROC can be assigned as the second source multiple times but can only be the controlling source for
one download session at a time. This is determined by the design of the IP process. When a GPROC2
is selected as controlling source to cross load a GPROC3, the second source must be a GPROC3.
In selecting source for code loading a BTS or GPROC2, the pool GPROC2 and GPROC3 shall have
higher priority than GPROC2-LCF or GPROC2-OMF, and Pool GPROC2 shall have higher priority than
GPROC3.
Note: Pool GPROC means a GPROC which is in Enabled-Unlocked state. A Pool GPROC is in RAM
state
When GPROC2-LCF or GPROC2-OMF is selected as controlling source to load BTS or GPROC2, BSC
shall use another GPROC as the second source. When two GPROC2-LCFs are selected to load a BTS
or GPROC, each GPROC2-LCF shall have a different half of the BTS objects.
When the GPROC2-OMF is selected as controlling source for code loading a BTS, the 2nd source must
be a Pool GPROC or GPROC3. Note: All BTS objects are removed from GPROC2-OMF. This was
introduced by GDBP feature
2006 Motorola, Inc.
June 2007
LCF Memory Version 1 Rev 3
LCF Memory
2006 Motorola, Inc.
2-97
June 2007
LCF Memory
The CSFP must be a GPROC3 in GSR9 otherwise the GPROC cross load may fail due to the GPROC2
out of memory. The BSC will select GPROC3 as source in GPROC LAN broadcasting cross loading.
When an LCF is assigned to a pool GPROC2 which was selected as the source GPROC for a on going
xload and BTS download session, the on-going xload and download session shall be killed and select a
new source to continue xloading/downloading. During the source reselecting procedure, the xload target
GPROC and the download target BTS shall not reset and continue xload/download code from the new
source.
BTS Downloading
During BTS site initialisation, the BSC can select one GPROC2 as controller to download the BTS. This
is same with pre-GSR9, however the difference is BSC will select another GPROC as 2nd source and
send the ID of 2nd GPROC to the controller GPROC. The controlling IP use the objects on the local
board and 2nd board to download the BTS.
A GPROC can be assigned as the 2nd source multiple times at a time. But the controller GPROC only
works one BTS downloading at a time. This is mainly because the IP design only supports one download
session.
BSC shall support a GPROC assigned as 2nd source for a maximum of 10 code loading sessions at a
time.
Note: With this function, in GSR9, if BSC has N GPROCs in service, the BSC can support downloading
a maximum number of N BTSs in parallel. This number is the same as pre-GSR9 release.
The COM process is already able to support multiple code load dialogs. The IP process on the controller
GPROC communicate with COM on the 2nd source GPROC directly.
2006 Motorola, Inc.
June 2007
LCF Memory Version 1 Rev 3
LCF Memory
INCELL Download
2006 Motorola, Inc.
2-99
June 2007
LCF Memory
MCELL Download
COM Multiple Downloads
2006 Motorola, Inc.
June 2007
2006 Motorola, Inc.
2-101
June 2007
Version 1 Rev 3 Radio Signalling Link (RSL)
Radio Signalling Link (RSL)
The RSL is the LAPD 64 kbps timeslot between the BTS and BSC to support BSC-BTS signalling. The
RSL may only be equipped at the BSC. It should be noted that with M-Cell and HorizonMacro equipment,
you may have up to 2 RSL's per E1 link. up to a maximum of 6 RSLs per site. With Horizon IImacro
and Horizon IImini equipment, the number of RSLs per site remains at a maximum 6 per site, but the
maximum number per E1 link is increased to 4.
equip <0 or bsc> RSL
Prompts
First device ID
This identies the site number associated with the RSL.
Second device ID
This identies a particular RSL associated with the site.
Path ID
Identies the unique path ID.
Optional Parameters
LAPD T200 timer
This is the maximumtime the LAPD (Layer 2) transmitter will wait for an acknowledgement before making
a retransmission.
LAPD N200
This is the maximum number of retransmissions a transmitter will make.
LAPD K
This is the maximum number of unacknowledged Information frames a transmitter will allow before
holding up transmission.
2006 Motorola, Inc.
June 2007
Radio Signalling Link (RSL) Version 1 Rev 3
Radio Signalling Link (RSL)
Enter the 1st device ID for the RSL: 1 - 140 (Site)
Enter the 2nd device ID for the RSL: 0 - 7 IN-CELL
0 - 5 M-CELL
2 Horizonmacro
6 Horizon II
Enter the unique path ID: 0 - 9
(ms, values in multiples of 50) Default = 2500
Enter the LAPD N200 value for this device: 1 - 5 Default = 3
Enter the LAPD K value for this device: 1 - 10 Default = 7
SYS02_Ch4_51
equip < 0 or bsc > RSL:
Optional Parameters
Enter the LAPD T200 timer value for this device: 1400 - 5000
2006 Motorola, Inc.
2-103
June 2007
Version 1 Rev 3 Message Transfer Link (MTL)
Message Transfer Link (MTL)
In GSR9, a number of features have been implemented to increase Network Capacity. This feature,
along with others is restricted by the option incNetCapacityOpt. It will support larger BSCs, provide
more exibility of conguration for MTL support and it increases capacity for MTL (MSC Transmission
Link) support.
Each BSC is connected to each MSC with a Signalling Link Set (SLS). Each Signalling link Set can
accommodate up to 16 distinct Signalling Links (SL). At present the BSCsupports each signalling link with
a 64kbit/s DS0. However, as the BSC is developed over successive releases its capacity is increasing
to a point where we now need more according capacity for the MTLs..
There are several ways to effect SLS enhancement:
Increase the size of the Signalling Link to the next PDH quanta [ie. 1xE1(2Mbit/s) as opposed to
1xTDM channel (DS0/64kbit/s)
Allow a mix of DS0/E1(recommended utilization 15%/40%) Signalling links (depends on both
options being supported, ie. existing plus 1)). The MSC must support this feature.
The E1 2MB MTL is terminated on a single GPROC3 with a PQ2 processor. This feature will allow the
equipage of 16 MTLs (as it is now) with the ability to bring all equipped links into service. Full MTP
change over and change back functionality would be supported. (Existing proposal only allows one 2MB
link to come into service. If more than one 2MB MTL is provisioned, the remaining MTLs remain in a hot
standby state. Swapping over to the standby would result in the signalling going out of service and then
coming back into service). MTLs can be a mix of 2MB (E1 MTL) and 64K (single DS0) links. Based on
current CPU utilization of a GPROC2 with 2 x 64K MTLs, it is estimated that a GPROC3 could terminate
6 x 64K MTLs or 20% of a 2MB MTL. You cannot have a mixture of HSP MTLs and 64Kbps MTLs on
one BSC MSC can support 64K MTLs on one BSC at the same time as HSP MTLs on another HSP MTL
will be required when more than 16 x 64Kbps MTLs are required according to Network Planning Guide
68P02900W21.
This feature does not support the sub_equipped MTL functionality. Sub_equipped MTL allows number
of MTL timeslots in MTL equipage to be any value between 1 and 31 inclusive.
The modied command equip <0 or bsc> MTL should be used to equip the MTL. which adds
devices and functions to the Fault Management portion of the CM database. It denes the number of
DS0 that the MTL use.
Prompts
Identies a specic MTL associated with a site.
2nd prompt (bit rate)
Identies the rate of the MTL.
3rd prompt (MSI/XCDR/GDP/GDP2)
Species the rst identiers of the MSI/XCDR/GDP/GDP2 to which the MTL is associated.
4th prompt (PORT)
Species the second identier of MMS to which the MTL is associated, ie the MSI/XCDR/GDP/GDP2
port.
5th prompt (timeslot)
Species which of the thirty two 64 kbps timeslots is to be assigned to the MTL, conventionally timeslot
16 is always used.
2006 Motorola, Inc.
June 2007
Message Transfer Link (MTL) Version 1 Rev 3
Message Transfer Link (MTL)
equip <0 or bsc> MTL
Enter the device identification for this MTL:
0 15
Enter the rate of this MTL: *
1: 64kbps MTL (default)
31: HSP MTL
Other values reserved
Enter the first MMS description for this device:
0 123
Enter the second MMS description for this device:
0 1
Enter start timeslot on MMS where this device
appears: **
1 31 (E1)
Note:
*: Only when Increased Network Capacity feature
is unrestricted, this value can be set to 31.
If user attempts to equip a mixture of MTLs, the equip
command shall be rejected.
**: If MTL rate is 31, this value must be 1.
Configuration
BSC 1 RXCDR MSC
BSC 2
MTLs
& CICs
CICs HSP MTL
CICs & MTL
CICs
No Point in MTL going via RXCDR any more
2006 Motorola, Inc.
2-105
June 2007
Version 1 Rev 3 Operations and Maintenance Link (OML)
Operations and Maintenance Link (OML)
The OML is the X.25 64 kbps timeslot between the BSC and OMC-R to support the remote Operation
and Maintenance function of the OMC-R. It cannot be equipped on an HDSL Link.
equip <0 or bsc> OML
Prompts
Identies a particular OML.
2nd prompt (MSI/XCDR/GDP/GDP2)
Identies the MSI/XCDR/GDP/GDP2 board supporting the OML. For initialisation purposes the OML is
defaulted to timeslot 1 of a port associated with an MSI in slot 16 or 14 of cage 0 or 16 in cage 1.
3rd prompt (port)
Identies a particular port on a MSI/XCDR/GDP/GDP2 board.
Identies the 64 kbps timeslot to which the OML has been allocated.
2006 Motorola, Inc.
June 2007
Operations and Maintenance Link (OML) Version 1 Rev 3
Operations and Maintenance Link (OML)
equip < 0 or bsc > OML
Enter the first MMS description for this OML: 0 - 55 (BSC)
0 - 123 (RXCDR)
Enter the second MMS description for this OML: 0 - 1
Enter timeslot on MMS where this device appears: 1 - 31
SYS02_Ch4_53
Enter the device ID for the OML: 0 - 3
2006 Motorola, Inc.
2-107
June 2007
Version 1 Rev 3 Cell Broadcast Link (CBL)
Cell Broadcast Link (CBL)
The CBL is a bi-directional data link that will allow communications between the BSS and the Cell
Broadcast Centre (CBC). The link will activate an underlying connection with an X.25 network and
establish a switch virtual circuit with the CBC. The CBC is responsible for down loading cell broadcast
messages to the BSS, together with an indication of the repetition rate and the number of broadcasts per
message. The BSS will in turn interpret these messages and transmit each request to the appropriate
BTSs.
The CBL feature is purchasable and will only support a single 64 kbs, non-redundant link using LAPB as
the Layer 2 protocol. DTE addresses need to be congured via MMI in order for the X.121 connection to
be made. In addition to the X.121 address, operator names must also be specied. These are included
in the N-connect message used to establish the SVC and must be consistent at both ends. The device
will reside upon the LCF for both type 1 and type 2 BSS sites.
The CBL can be connected directly from the X.25 network into the BSS via a 2MB link Alternatively it
may be connected via a 64kbs cross connect in the RXCDR.
The database command and prompts necessary to congure a CBL are as follows:
equip <0 or bsc> CBL
Prompts
Identies the CBL, ID 0 or 1.
Identies the MSI/XCDR/GDP/GDP2 board supporting the CBL.
3rd prompt (port)
Identies the MSI/XCDR/GDP/GDP2 port.
Identies the 64kbs timeslot the CBL has been allocated to.
5th prompt (BSS operator)
This eld species the BSS operator's name. This eld must be entered between double quotes.
6th prompt (CBC operator)
This eld species the CBC operator's name. This eld must be entered between double quotes.
2006 Motorola, Inc.
June 2007
Cell Broadcast Link (CBL) Version 1 Rev 3
Cell Broadcast Link (CBL)
Cell Broadcast Link (CBL) Equipage
enter the device id for the CBL:
0/1
enter the first MMS id for this device:
055
enter the second MMS id for this device:
0/1
equip < 0 or bsc > CBL
enter timeslot on MMS where this device appears:
131
enter the BSS operator = 20 characters:
enter the CBC operator = 20 characters:
2006 Motorola, Inc.
2-109
June 2007
Version 1 Rev 3 Location Message Transfer Link (LMTL)
Location Message Transfer Link (LMTL)
The Location Message Transfer Link (LMTL) is a 64 kbps timeslot between the BSS and the SMLC to
support ss7 signalling messages between these two network elements. These timeslots, of which up to
16 can be congured, are located on an interface known as the Lb interface.
Like all these types of link, it must be controlled by an LCF. It may not be equipped at an RXCDR.
equip <0 or bsc> LMTL
Identies the LMTL device.
Identies the MSI/XCDR/GDP/GDP2 board supporting the LMTL.
3rd prompt (port)
Identies the MSI/XCDR/GDP/GDP2 port.
Identies the 64kbs timeslot the LMTL has been allocated to.
2006 Motorola, Inc.
June 2007
Location Message Transfer Link (LMTL) Version 1 Rev 3
Location Message Transfer Link (LMTL)
SYS02_Ch4_54
Enter the device ID for the LMTL: 0 - 15
Enter the first MMS description for this LMTL: 0 - 55 (BSS)
Enter the second MMS description for this LMTL: 0 - 1
Enter the timeslot on MMS where this device appears: 1 - 31
equip < 0 or bsc > LMTL
2006 Motorola, Inc.
2-111
June 2007
Version 1 Rev 3 XBL Equipage
XBL Equipage
XBLs must be equipped at both the RXCDR and BSS as these are separate GSM entities.
At any BSS there can be a maximum of 10 XBLs, distributed between a maximum of 9 XBL link sets
provided the number of GPROC TDM timeslots available for use is set to 16 or 32. One link set is
assumed for each interface to a RXCDR. Therefore, a BSS supports XBL interfaces to up to nine different
RXCDRs. There may be as few as 1 XBL device and as many as 10 XBL devices per XBL link set. The
MMS specied in the equip XBL command must be in the connectivity table. The connectivity table
AXCDR or ABSS device ID entry for the MMS specied must also match the AXCDR or ABSS device
specied in the equip XBL command.
ARXCDRcan support a maximumof 10 XBLs distributed between a maximumof 9 XBL link sets provided
the number of GPROC TDM timeslots available for use is set to 16 or 32. One link set is assumed for
each interface to a BSC. Therefore, a RXCDR supports an XBL interface to up to nine different BSSs.
There may be as few as 1 XBL device and as many as 10 XBL devices per XBL link set.
Each XBL device has 2 identiers; the rst identier being the ABSS/AXCDR device identier to which
the XBL is communicating, and the second the XBL device number.
The RXCDR will support backwards compatibility in accordance with how the OMC-R currently supports
backwards compatibility. Since the RXCDR and BSS are assumed to be managed by the same OMC-R,
the RXCDR need only support the same range of loads which a single OMC-R may manage. An example
is that if a RXCDR is running software release 1.7.6.0.X, this RXCDR will be able to communicate
with BSSs running 1.7.6.0.X, 1.7.4.0.X, or 1.7.0.0.X. The BSS will also support the same backwards
compatibility.
2006 Motorola, Inc.
June 2007
XBL Equipage Version 1 Rev 3
XBL Equipage
RXCDR 1
RXCDR 2
RXCDR 3
RXCDR 4
RXCDR 5
BSS 3
MSC
BSS 5
BSS 4
BSS 2
BSS 1
XBL Linksets
Up to 9 BSSs per RXCDR
2006 Motorola, Inc.
2-113
June 2007
Version 1 Rev 3 Equipping the XBL
Equipping the XBL
Enter the ABSS or AXCDR id for the XBL
This value species the ABSS or AXCDR identity that the XBL will be communicating to.
Enter the second identity for the XBL
This is the value for the XBL device
Data Rate
The XBL can be 16 kbit/s or 64 kbit/s, i.e. occupying a quarter of a timeslot or a whole timeslot.
First MMS Description
This number identies the MSI card within the transcoder.
Second MMS Description
This number identies the port on the MSI card.
Timeslot
This is the timeslot on the MMS.
Group
Only appears if the data rate is 16 kbit/s. Identies which quarter of the timeslot is used for the XBL
maximum 2 XBLs per timeslot.
LAPD T200 Timer
This is the maximumtime the LAPD (Layer 2) transmitter will wait for an acknowledgement before making
a retransmission.
LAPD N200
This is the maximum number of retransmissions a transmitter will make.
LAPD K Value
This is the maximum number of Unacknowledged Information frames a transmitter will allow before
holding up transmission.
2006 Motorola, Inc.
June 2007
Equipping the XBL Version 1 Rev 3
Equipping the XBL
equip 0 XBL
Enter the ABSS device identifer for the XBL: 1 to 254
Second identifer for the XBL: 0 to 9
Data rate for the XBL (kbps): 64K or 16K
First MMS identifer for this device: 0 to 71 (RXCDR)
0 to 55 (BSS)
Second MMS identifer for this device: 0 or 1
T imeslot on MMS where this device appears: 1 - 31
Enter the group of the timeslot where this device appears: 0 - 3
LAPD T200 timer value for this device: 200 - 5000
(default 2500)
LAPD N200 value for this device: 1 - 5
(default 3)
LAPD K value for this device is: 1 - 127
(default 7)
Note: The XBL is also equipped at the BSC, the main diference is the id for the AXCDR
instead of the ABSS. It should have the same XBL id and must have the same timeslot
at the BSS as at the RXCDR. Also the LAPD parameters must be the same at both
ends.
2006 Motorola, Inc.
2-115
June 2007
Version 1 Rev 3 XBL Connectivity: add_conn
XBL Connectivity: add_conn
Overview
In order to ensure correct XBL operation, network connectivity information must be entered at the RXCDR
or the BSS. Using the add_conn command, every RXCDR to BSS (or BSS to RXCDR) link must be
specied separately. This parameter can be entered at either the RXCDR or the BSS. The add_conn
command is used to add MMS connectivity between the RXCDR and the BSS. It updates the BSS
database to reect a particular connection between a MMS at the BSS and an MMS at the RXCDR.
add_conn
local_mms_id_1: mms id 1: 1st link identier at either the RXCDR or BSS, depending where this
command is being entered.
local_mms_id_2: 2nd link identier at the RXCDR or BSS.
network_entity_id : AXCDR or ABSS identier representing the actual network entity (RXCDR or
BSC) with which this BSC or RXCDR MMS is communicating. The range of values is 1 to 128.
remote_mms_id_1: 1st link identier at the distant BSS or RXCDR.
remote_mms_id_2: 2nd link identier at the distant BSS or RXCDR.
This connectivity information will enable circuit or board failure information at a RXCDR to be transmitted
to the corresponding BSSs.
2006 Motorola, Inc.
June 2007
XBL Connectivity: add_conn Version 1 Rev 3
XBL Connectivity: add_conn
add_conn <local mms id1> <local mms id2>
<network_entity_id> <remote mms id1>
<remote mms id 2>
2006 Motorola, Inc.
2-117
June 2007
Version 1 Rev 3 XBL Connectivity Tables
XBL Connectivity Tables
Overview
In the event of either XCDR equipment or link failure affecting the RXCDRs 2Mb inputs from the MSC,
the BSS whose circuits have been affected can be informed via message sequences on the XBL. These
messages will inform the fault management of the BSS of the incoming link id, slot and group number of
each circuit affected. This information is then used by the BSS to re-allocate an un-allocated Ater circuit
to the call under fault management, or if no Ater circuits are available, to format the appropriate blocking
messages' to be sent to the MSC.
To enable the RXCDR's FM to specify these circuit details to the BSS, XBL connectivity tables are
produced by the RXCDR's FM from the database parameters:
equip 0 cic: At the RXCDR, which species BSS managing the CIC, the MMS incoming from the
BSS including start timeslot and group number, and MMS outgoing to MSC including start timeslot.
equip 0 cic: At the BSS, which species the RXCDR providing the TRAU resource, the MMS
outgoing to the RXCDR, and the starting timeslot and group.
add_conn: Will specify every link connection from Remote Transcoder to BSC, or from BSC to RXCDR,
depending on where it is entered. Each span is dened by the local MMS id, the Associate BSS or
RXCDR to which it is routed, and the remote MMS id.
equip xbl: Will specify the link id holding the XBL. This link id will be one of the link within the group
of links attributed to one BSS.
The table below can then be constructed by the RXCDR's FM. If a fault occurs to a particular XCDR
card, then equip 0 cic will point to outgoing links (to BSSs), timeslots and group numbers which are
affected by the incoming failure. These outgoing links have been identied by the add_conn parameter
as belonging to a group of links notionally attributed to a specied BSS. The failure messages can then
be sent via an XBL having a link id consistent with one of the links within the notional group.
Incoming Outgoing XBL ID & BSS MMS ID
Timeslot MMS id Timeslot Group Number MMS id
2006 Motorola, Inc.
June 2007
XBL Connectivity Tables Version 1 Rev 3
XBL Connectivity Tables
equip 0 xbl
1
0
64
10
0
2
2500
3
7
GDP 15 GDP 17
equip 0 cic
ABSS 1
MSI 10
0 1
equip 0 xbl
1
0
64
8
0
2
2500
3
7
GDP 22 GDP 23
equip 0 cic
ABSS 1
MSI 8
0 1
ABSS 2
MSI 9
0 1
equip 0 xbl
2
0
64
9
0
2
2500
3
7
MSC
AXCDR 102
MSI 1
0 1
AXCDR 103
MSI
equip 0 cic
equip 0 xbl
102
0
64
1
0
2
2500
3
7
equip 0 xbl
103
0
64
1
1
12
2500
3
7
AXCDR 103
MSI 3
0 1
MSI
equip 0 xbl
103
0
64
3
0
2
2500
3
7
equip 0 cic
At RXCDR 102:
add conn 10 0 1 1 0
At RXCDR 103:
add conn 8 0 1 1 1
At BSC 2:
add conn 3 0 103 9 0
BSC 1 BSC2
RXCDR 102
RXCDR 103
RXCDR 103
2006 Motorola, Inc.
2-119
June 2007
Version 1 Rev 3 Enhanced XBL
Enhanced XBL
Overview
Between a RXCDR and a BSS there must now exist one or more XBLs, to provide bi-directional
communications between the BSP in the BSS and the BSP in the RXCDR. The purpose of the XBL is
to ensure database consistency and connectivity between the BSS and RXCDR to ensure that trafc
pathways are properly established, and to ensure that maintenance activity or faults occurring at the
RXCDR which indirectly affect BSS link devices are forwarded to the BSS for processing.
The XBL provides a signalling link and generic messaging system between the base site controller (BSS)
and the remote transcoder (RXCDR). It carries the control messages which allow the BSS to nominate
an Ater circuit to carry a CIC allocated by the MSC to a call, The consistency and connectivity checks
between BSS and RXCDR are to ensure that trafc pathways are properly established and to conrm
that conguration of both RXCDR and BSS databases is correct.
CIC Blocking
To ensure that the BSS software is always using valid trafc CICs to carry calls, the BSS software blocks
any CIC at the BSS which cannot be veried to be in good working order. Blocking a CIC informs the
MSC not to select that CIC for phone calls.
Link Control
Control links (OML, MTL and CBL) which route through the RXCDR and terminate at the BSS will be
removed from service if the E1/T1 devices which carry them are locked at the RXCDR. The links will
reect the states of the RXCDR MMS devices through which they are nailed.
Number of XBLs Required
The number of XBLs required depends upon the number of CICs and/or the number of Ater interface
channels. A BSS can be connected to a maximum of 9 RXCDRs, and vice versa. A maximum of 10
XBLs (64 kbit/s or 16 kbit/s) can be congured for each BSC/RXCDR pair'. Within the auto-connect
mode, one XBL must be equipped for every 1200 trunks from MSC to the BSS. If XBLs are equipped at
16 kbit/s, then a proportionally greater number (x 4) than 64 kbit/s devices are required.
BSS/RXCDR Verication and Validation
The connectivity between a BSS and RXCDR is stored in the BSS and RXCDR databases. When the
rst XBL at a BSS to an RXCDR comes in-service, the BSC validates E1/T1 connectivity information. If
the RXCDR fails to respond to three attempts by the BSC to participate in the CIC validation procedure,
the BSC sends an alarm to the OMC-R "BSC Detecting CIC Validation Failure" and blocks all CICs
associated with the RXCDR. A similar alarm is generated by the RXCDR.
In order to increase connectivity capacity without causing the validation procedure to fail, connectivity
entries should be added to the RXCDR rst and then at the BSS. Conversely, to decrease connectivity
without causing the validation process to fail, connectivity entries should be deleted at the BSS rst and
then at the RXCDR. AXCDR devices must exist in the BSS database, and ABSS devices must exist in
the RXCDR database before connectivity is equipped between the BSS and RXCDR.
2006 Motorola, Inc.
June 2007
Enhanced XBL Version 1 Rev 3
Enhanced XBL
RXCDR
Ater chans EXBL
BSS
ABSS
AXCDR
2006 Motorola, Inc.
2-121
June 2007
Version 1 Rev 3 XBL Connectivity Exercise
XBL Connectivity Exercise
Complete the database parameters for the connectivity shown opposite as viewed from the RXCDR
add_conn _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
add_conn _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
add_conn _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
add_conn _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
add_conn _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
add_conn _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
add_conn _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
add_conn _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
add_conn _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
2006 Motorola, Inc.
June 2007
XBL Connectivity Exercise Version 1 Rev 3
XBL Connectivity Exercise
MSI
1
MSI
2
MSI
3
MSI
4
MSI
5
RXCDR 101
MSI
1
MSI
2
BSS 1
MSI
1
MSI
2
BSS 2
MSI
1
MSI
2
BSS 3
MSC
0
1
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
XBL
XBL
XBL
2006 Motorola, Inc.
2-123
June 2007
Version 1 Rev 3 Adding a Control Link
Adding a Control Link
Overview
In order to route control circuits (links) to a BSS, the command chg_ts_usage is employed, which
describes a nailed 64 kbit/s circuit cross connected through the RXCDR.
The command chg_ts_usagehas several operations associated with it, but in cross-connecting a
control link, only the nail operation is employed.
chg_ts_usage
<operation>
<site>
<mms1 id 1> <mms1 id 2>
<mms 1 ts>
<mms2 id 1> < mms2 id 2>
<mms 2 ts>
<range>
This command string will nail a 64 kbit/s circuit in site 0 (the RXCDR being equipped) from the nominated
timeslot on MMS1 to the nominated timeslot on MMS2.
Inbound (from MSC, OMC or CBC)
Incoming span id 1 MMS 1 id 1
Incoming span id 2 MMS 1 id 2
Incoming timeslot MMS 1 ts
Outbound (to BSS)
Outbound span id 1 MMS 2 id 1
Outbound span id 2 MMS 2 id 2
Outbound timeslot MMS 2 ts
chg_ts_usage <operations>
reserve
free
free_path
nail
nail_path
2006 Motorola, Inc.
June 2007
Adding a Control Link Version 1 Rev 3
Adding a Control Link
0
0
1
0 MSI 10
0
1
BSS
MTL
TS 16
OMC
MSC
1
KSW
GDP 14
MSI 8
MTL
TS 16
OML
TS 1
OML TS 2
chg_ts_usage
nail
0
14 0
16
8 0
16
1
chg_ts_usage
nail
0
10 0
2
8 0
1
1
chg_ts_usage
<operation>
<location>
<incoming MMS id 1> <incoming MMS id 2>
<incoming timeslot>
<outgoing MMS id 1> <outgoing MMS id 2>
<outgoing timeslot>
<range>
2006 Motorola, Inc.
2-125
June 2007
Version 1 Rev 3 Unequip
Unequip
Un-equip
As well as carrying out the equipage of various devices and functions, the operator is also provided with
the facility to un-equip these devices and functions. Like the various equip commands already covered,
there are a number of prerequisites that have to be met before the unequip command is accepted.
Prerequisites
The following prerequisites are applied to the unequip command:
1. The device or function being un-equipped must be in the locked state.
2. When un-equipping the device or function, the location must be specied.
3. No child dependencies must be specied for the device or function being un-equipped.
Sysgen On
The following devices and functions can only be un-equipped during the sysgen on mode, at a BSS
location:
cbl, mtl, omf, oml, lmtl
Sysgen On/OFF
The following devices and functions can be un-equipped when sysgen is either on or off:
bsp, dri, omf, oml, btp, eas, path, cab, gclk, rsl, cbl, gproc, rtf
cic, ksw, site, comb, lcf, xbl, csfp, msi, dhp, mtl, lmtl
It should be noted that various conditions apply to each device or function which must be considered
before the unequip command is carried out.
Example:
One of the devices that can be un-equipped, is a cabinet, using the unequip cab command. Before
GSR5.1, it was only possible to un-equip a cabinet from a site by rst un-equipping the site. The
unequip cab command allows you to un-equip cabinets without rst un-equipping the site. However,
the only cabinets allowed with this command are TCU_2, TCU_6 and Horizonmacro. It should also be
remembered that the cabinet has to be locked, with no DRIs and EASs equipped to it.
2006 Motorola, Inc.
June 2007
Unequip Version 1 Rev 3
Unequip
unequip <location> <*>
* = device/function
bsp
dri
omf
oml
btp eas path
cab gclk rsl
cbl gproc rtf
cic ksw site
comb lcf xbl
csfp msi dhp
mtl lmtl
SYS02_Ch4_55
2006 Motorola, Inc.
2-127
June 2007
Version 1 Rev 3 Synchronisation Loss
Synchronisation Loss
For site synchronisation each site will have two Generic Clock (GCLK) modules.
All terrestrial circuits interfacing to a site will do so on standard 2.048 Mbit/s PCM links and the GCLK is
able to derive its reference from these links or alternatively free run in case of reference failure.
The GCLK enables the site to synchronise to the 2.048 Mbit/s links so that frame and multiframe
alignment can be achieved.
Synchronisation loss thresholds can be set on both an hourly and daily basis so that when these
thresholds are reached an alarm message can be generated by the MSI/XCDR/GDP card to the FM.
Both of these periods are chronological, i.e. if an alarm condition has been reached in the rst 10 minutes
of an hour, that alarm is then locked out until the next chronological hour begins.
The parameter sync_loss_oos provides an upper limit of sync loss alarms, upon reading this threshold
the GDP/XCDR/MSI will notify the FMwhich in turn will take the MMS out of service. This threshold works
on a daily basis.
If an MMS has been taken out of service as a result of the sync_loss_oos threshold being reached,
the FM will not put it back in service until the sync_loss_restore time has expired. For this timer to
activate no sync loss alarms must occur, a single sync alarm will reset it.
2006 Motorola, Inc.
June 2007
Synchronisation Loss Version 1 Rev 3
Synchronisation Loss
SYS02_Ch2_10
HOURS
Alarm threshold
reached
Alarm locked out
0 1 2
chg_element sync_loss_daily <*> <SITE No> Default 16
chg_element sync_loss_hourly <*> <SITE No> Default 20
chg_element sync_loss_oos <*> <SITE No> Default 511
chg_element sync_loss_restore <*> <SITE No> Default 600
* Number of alarm conditions Range 0 to 65535 * Number of alarm conditions Range 0 to 65535
* integer (100ms periods) Range 0 to 65535 * integer (100ms periods) Range 0 to 65535
2006 Motorola, Inc.
2-129
June 2007
Version 1 Rev 3 Remote Loss Alarms
Remote Loss Alarms
As previously mentioned the MSI/XCDR/GDP/GDP2 can track sync alarms from its own transmit by
receipt of the remote ag from the distant end.
This ag allows the monitoring of restore sync losses in much the same way as the sync loss parameters
on the previous page.
2006 Motorola, Inc.
June 2007
Remote Loss Alarms Version 1 Rev 3
Remote Loss Alarms
chg_element remote_loss_daily <*><SITE No> Default 16
chg_element remote_loss_hourly <*><SITE No> Default 20
chg_element remote_loss_oos <*><SITE No> Default 511
* Number of alarms Range 0 to 65535
chg_element remote_loss_restore <*><SITE No> Default 600
* integer (100ms periods) Range 0 to 65535
Sys02_Ch2_28
2006 Motorola, Inc.
2-131
June 2007
Version 1 Rev 3 Site Synchronization
Site Synchronization
The four parameters shown opposite are interrelated. The sync_time_oos eld indicates the permitted
time that the receive leg of the 2Mb link can have a prolonged synchronization alarm. When this time
is exceeded the MSI/XCDR/GDP card will inform the FM. The FM will initiate the MMS into a state of
unlocked/disabled.
The sync_time_restore eld indicates the length of time that the receive leg of a 2Mb link must
maintain synchronization before the MSI/XCDR/GDP card will inform the FM. The FM will activate the
MMS to a state of unlocked/enabled.
Immediately a synchronization alarmoccurs on the receive leg of a 2Mb the MSI/XCDR/GDP card will set
the remote alarmag (timeslot 0) on the transmit leg. At the distant end, on receipt of this alarmcondition,
the remote timer starts, if no clear indication is received before the remote_time_oos expires then the
MSI/XCDR/GDP will inform the Fault Management (FM). The FM will initiate a state of unlocked/disabled
for the MMS. The remote_time_restore eld sets the time that a remote alarm ag must be in a
clear condition before the MSI/XCDR/GDP noties the FM. The FM will activate the MMS to a state of
unlock/enabled.
2006 Motorola, Inc.
June 2007
Site Synchronization Version 1 Rev 3
Site Synchronization
remote_time_oos
remote_time_restore
sync_time_oos
sync_time_restore
sync_time_oos
sync_time_restore
remote_time_oos
remote_time_restore
Rx
Rx
Tx
Rx
Rx
Tx
Tx
Tx
Remote flag
Direction of Traffic
Remote flag
Direction of Traffic

chg_element remote_time_restore <*><SITE No> DEFAULT = 600
chg_element remote_time_oos <*><SITE No> DEFAULT = 25
chg_element sync_time_restore <*><SITE No> DEFAULT = 600
chg_element sync_time_oos <*><SITE No> DEFAULT = 25
2006 Motorola, Inc.
2-133
June 2007
Version 1 Rev 3 Slip Loss Alarms
Slip Loss Alarms
The MSI/XCDR/GDP contains an elastic 2 frame buffer to account for slip loss. If this loss exceeds the
size of the buffer a TDM frame will be lost as the buffer resets, each time the buffer resets, a slip loss
alarm is generated. Each slip loss alarm is counted and subject to similar thresholds mentioned.
2006 Motorola, Inc.
June 2007
Slip Loss Alarms Version 1 Rev 3
Slip Loss Alarms
chg_element slip_loss_daily <*><SITE No> Default 4
chg_element slip_loss_hourly <*><SITE No> Default 10
chg_element slip_loss_oos <*><SITE No>Default 255
* Number of slip loss alarms Range 0 to 65535
chg_element slip_loss_restore <*><SITE No> Default 600
* integer (100ms periods) Range 0 to 65535
Sys02_Ch2_30
2006 Motorola, Inc.
2-135
June 2007
Version 1 Rev 3 BER Loss Alarms
BER Loss Alarms
Bit Error Rates (BER) are constantly being checked by an MSI/XCDR/GDP card, the period over which
they are assessed for out of service purposes is controlled by ber_oos_mon_period.
An alarm will be generated when the daily and hourly thresholds for BER are exceeded.
2006 Motorola, Inc.
June 2007
BER Loss Alarms Version 1 Rev 3
BER Loss Alarms
chg_element ber_loss_daily <*><SITE No> DEFAULT = 6
chg_element ber_loss_hourly <*><SITE No>DEFAULT = 4
* ber rate
e.g. 4= 10e
- 4
Range 3 to 6
Sys02_Ch2_31
2006 Motorola, Inc.
2-137
June 2007
Version 1 Rev 3 BER Monitoring Periods
BER Monitoring Periods
The MSI/XCDR/GDP card monitors the Bit error rate of the incoming 2Mb, the BER can be determined
using the xed bits of the Frame Alignment Word and Frame Data Word. The xed Bits do not alter and
therefore are ideal to calculate BER.
The ber_oos_mon_period is the period that an in-service MMS must exceed the set BER rate before
it is taken out of service. The BER rate is set in rmware at 10e
-3
.
The ber_restore_mon_period is the amount of time an out of service MMS must exceed the set BER
rate before it can be put back in service. The location for both of these periods can be set individually
for each site but more usually is set to all' to include every site in the BSS.
2006 Motorola, Inc.
June 2007
BER Monitoring Periods Version 1 Rev 3
BER Monitoring Periods
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
0 0 1 1 1 1 0
CRC
Check
EVEN
FRAMES
(FAW)
ODD
FRAMES
(FDW)
I.U
REMOTE
ALARM
N BIT I.U SPARE SPARE SPARE 1
TIMESLOT 0 STRUCTURE
FIXED BITS
FIXED BIT
SYNC TOGGLE
I.U = International usage
modify_value<location>ber_oos_mon_period <*>
MMS
* 1 - 60 seconds
Default 1
modify_value<location>ber_restore_mon_period<*> MMS
* integer (100ms periods)
* 1 18000
Default 6000
Sys02_Ch2_32
2006 Motorola, Inc.
2-139
June 2007
Version 1 Rev 3 Site Synchronisation Exercise
Site Synchronisation Exercise
Site Synchroniation Exercise
The following exercise will give the student the opportunity to practice the theory presented in this section.
If a prolonged synchronisation alarm of 10 seconds is suffered by any 2Mb terminated at site 0 then FM
should remove the link from service. If synchronization is established for more than 5 seconds the 2Mb
should be restored to service. The remote values should be consistent with the receive synchronization
parameters.
If any 2Mb at site 0 should lose sync more than 20 times in a 24 hour period the FM should remove the
link from service. If no synchronization alarms occur for a period of 5 seconds then the 2Mb should be
restored to service. The alarms associated with synchronization losses should be triggered at 15 alarms
hourly and 5 alarms daily. The remote values should be consistent with the receive synchronization loss
parameters.
Only 20 slip loses should be allowed within any 24 hour period before FM removes the affected 2Mb
from service. Before FM restores the 2Mb to trafc there should be no slip losses for at least 1 minute.
Slip loss conditions should generate alarms when they exceed the following period thresholds, 12 per
hour and 5 per day.
Bit error rate alarms should be generated at 10e
-4
on an hourly basis and 10e
-6
on a daily basis.
2006 Motorola, Inc.
June 2007
Site Synchronisation Exercise Version 1 Rev 3
# BTS SITE 18
# LOAD 1.8.0.0 (GSR8 )

chg_element sync_time_oos
chg_element sync_time_restore
chg_element remote_time_oos
chg_element remote_time_restore
chg_element sync_loss_oos
chg_element sync_loss_restore
chg_element sync_loss_daily
chg_element sync_loss_hourly
chg_element remote_loss_oos
chg_element remote_loss_restore
chg_element remote_loss_daily
chg_element remote_loss_hourly
chg_element slip_loss_oos
chg_element slip_loss_restore
chg_element slip_loss_daily
chg_element slip_loss_hourly
chg_element ber_loss_daily
chg_element ber_loss_hourly
SYS02_Ch2_16b
2006 Motorola, Inc.
2-141
June 2007
Version 1 Rev 3 N Bit
N Bit
It is possible to set an extra remote alarm bit, the n bit. The bit which is used for this purpose is bit 4 of
the frame data word. The actual use of this bit is specied by the customer but the bit must be enabled
using the modify_value command. Again this bit can be enabled for all sites using the all' location
index, although any in-service MMSs will not use it until they are reset.
2006 Motorola, Inc.
June 2007
N Bit Version 1 Rev 3
N Bit
SYS02_Ch2_13
1 2 3 4 5 6 7 8
FDW I.U
REMOTE
ALARM
N BIT I.U SPARE SPARE SPARE
TIMESLOT 0 STRUCTURE
SYNC
TOGGLE
modify_value<location>nbit<*>MMS
* 0 disabled
1 enabled
2006 Motorola, Inc.
2-143
June 2007
Version 1 Rev 3 Statistics Interval
Statistics Interval
Statistics are, as of GSR9 implementation, gathered in parallel from BSCs/RXCDRS DSFs, sorted and
compressed (4Mb to 1Mb) before being uploaded to the OMC-R at regular intervals.The interval can be
set to either 30 or 60 minutes using the chg_element stat_interval command. This parameter
is only entered at the BSS and RXCDR (i.e. all site 0s) and must be set to the same value as all the
other BSSs connected to the same OMC-R. The interval, 30 or 60, is determined by the OMC-R system
administrator who will enter the same interval at the OMC-R.
The upload rate is about 5Kbps and is expected to take about 27 minutes.
2006 Motorola, Inc.
June 2007
Statistics Interval Version 1 Rev 3
Statistics Interval
chg_element stat_interval <*> <Site>
<*> interval in minutes (30 - 60 only)
Default - = 30
chg_element stat_interval 30 0
chg_element stat_interval 30 0 chg_element stat_interval 30 0
OML
OML
OML
BSS 3 BSS 2
BSS 1
RXCDR
OML
OMC
2006 Motorola, Inc.
2-145
June 2007
Version 1 Rev 3 Statistics Interval
2006 Motorola, Inc.
June 2007
Transcoder Conguration Version 1 Rev 3
Chapter 3
Transcoder Conguration
2006 Motorola, Inc.
3-1
June 2007
Version 1 Rev 3 Transcoder Conguration
2006 Motorola, Inc.
June 2007
Objectives
Describe the device/function interdependency used within the Transcoder database structure
Describe the device/function equipage of cards and CICs for the Transcoder
Describe the various types of Transcoder and the use of Call Downgrade
Explain the different methods of working with EFR/AMR/GSM Half Rate
Explain the Enhanced GDP feature
Explain MSC Quietone and Downlink DTX
Complete a written exercise to equip a Transcoder database
2006 Motorola, Inc.
3-3
June 2007
Version 1 Rev 3 Remote Transcoder
Remote Transcoder
Recent Changes
Major changes during recent software changes, have been made to the structure of the GSM BSS
and RXCDR entities and their network conguration. Trafc channels between the RXCDR and BSC
(on the Ater interface) can be auto-connected to the CICs between the BSC and the MSC. To support
the auto-connect mode of allocating trafc channels between the RXCDR and the BSC the following
commands/parameters are used:
The commands equip 0 bss and equip 0 rxcdr together with the supporting logical devices
axcdr (at a BSC) and abss (at an RXCDR) .
The equip 0 site command has been retained from GSR 5 onwards for BTS sites only, or to
BSC/RXCDR/BTS sites equipped under pre GSR5 databases.
The commands add_channel and add_link have been deleted, and replaced by extensions of
the equip 0 cic and change_ts_usage commands respectively.
The commandadd_conn is now used to describe mms connectivity between RXCDR and BSC,
and may be added at either location.
Within the equip 0 bss / rxcdr command for the initial BSS device, the fm_site_type is
automatically set. If the local site number is greater than zero, fm_site_type is always set to
BTS.
The theoretical network on which the examples script in this manual is based, is as shown opposite:
MSC
OMC
RXCDR 101 RXCDR 102 RXCDR 103
BSS 1 BSS 2
CIC 1 to 9
Link 0
CICs 97 to 100
CICs 129 to 132
Links 3 and 4
CIC 33 to 44
CIC 65 to 76
Links 1, 2
9 Ater
circuits
12 Ater
circuits
12 Ater
circuits
8 Ater
circuits
OML
OML
OML
MSI 1
MSI 5
MSI 9
0 1
0 1
0 1 0 1
0 1 0 1 0 1
0 1 0 1
GDP GDP GDP
GDP GDP
MSI MSI
MSI 2 MSI 1
MSI 6 MSI 8
MSI 10
(17) (15)
(23) (22)
MSI 8
M
S
I
M
S
I
0
1
MSI 10
2006 Motorola, Inc.
June 2007
Remote Transcoder Version 1 Rev 3
Remote Transcoder
RXCDR Script Building
The script building chart shown opposite species the groups of parameters necessary to populate a
Remote Transcoder database. The actual parameters can be examined more closely by following the
example script overleaf.
The structure of the database equipage for BSCand BTS sites contains newparameters and is contained
in subsequent chapters.
Equip RXCDR
Device/Function Equipage
Equip ABSS
Equip CAB
Equip CAGE
Site Configuration
MMS Thresholds
Equip Links
Equip CICs
2006 Motorola, Inc.
3-5
June 2007
Version 1 Rev 3 RXCDR - 1.9.0.0 Script Files
RXCDR - 1.9.0.0 Script Files
# EXAMPLE RXCDR DATABASE
# GSR9 (1.9.0.0)
# Equipage of RXCDR 102 (connected to BSS 1 and BSS 2, 12 x ater each)
# AMR not enabled
equip 0 rxcdr
102 # rxcdr id
equip 0 abss
1 # abss device id
equip 0 abss
2
equip 0 cab
0 # cab id
5 # cab type
equip 0 cage
0 # cage id
0 # highway num
# no kswx
# no red kswx
0 # cab id
yes # IAS present
chg_element gproc_slots 32 0 # Default 16 - Only valid if gproc 2 or 3 boards present
equip 0 ksw
0 # TDM highway managed
0 # TDM id
0 # cage id
no # drims managed
equip 0 bsp
0 # bsp id
0 # cage id
25 # slot number
equip 0 bsp
1
0
26
equip 0 gclk
0 # gclk id
0 # cage id
no # clkx 0
no # clkx1
no # clkx 2
equip 0 msi # to bss 01
6 # mms id1
0 # cage no
6 # slot no
0 # msi type
equip 0 msi
8
0
8
0
equip 0 msi
10
0
10
0
equip 0 msi
15
0
9
2006 Motorola, Inc.
June 2007
RXCDR - 1.9.0.0 Script Files Version 1 Rev 3
2
0
equip 0 msi
17
0
7
2
0
add_conn 6 0 1 1 1 # local mms1, local mms2, abss, # remote mms1, remote mms2
add_conn 8 0 2 2 1
equip 0 oml # rxcdr oml
0 # oml number
10 # mms 1
0 # mms 2
1 # ts
equip 0 xbl
1 # abss device id for xbl 1-128
0 # second identier for xbl
64 # xbl capacity
6 # mms id 1
0 # mms id 2
25 # timeslot for xbl
2500 # t200 timer value
3 # n200 value
7 # lapd k value
equip 0 xbl
2
0
64
8
0
25
2500
3
7
chg_ts_usage # nails the bss mtl via the rxcdr
nail # action
0 # site
15 0 # mms
16 # ts
6 0 # mms to bss 1
16 # ts
1 # how many
chg_ts_usage
nail # mtl to bss 2
0
17 0
16
8 0
16
1
chg_ts_usage
nail # oml through to bss 1
0
10 0
2
6 0
1
1
2006 Motorola, Inc.
3-7
June 2007
chg_ts_usage
nail # oml to bss 2
0
10 0
3
8 0
1
1
equip 0 cic
33 to 44 # cic numbers (12 cic's)
1 # which bss
6 0 # mms to bss
2 # starting timeslot
0 # starting subgroup
15 0 # mms to msc
1 # starting timeslot
****Remark: this quantity can be set to include a complete E1 link, even if the number of ATERs is less
than this. This will allow a rxcdr to be equipped to match its total E1 availability to MSC. The BSC can
be equipped according to actual need.
equip 0 cic
65 to 76
2
8 0
2
0
17 0
1
# E1 link parameters left at defaults
modify_value 0 mms_priority 0 MMS 6 0 0 # mms not selected
modify_value 0 mms_priority 254 MMS 15 0 0 # mms 15 0 chosen second
modify_value 0 mms_priority 255 MMS 17 0 0 # mms 17 0 chosen rst
chg_element phase_lock_gclk 1 0 # phase locking enabled
chg_element wait_for_reselection 240 0 # wait 240s for reselection
chg_element lta_alarm_range 10 0 # LTA alarm range set to 10
2006 Motorola, Inc.
June 2007
2006 Motorola, Inc.
3-9
June 2007
Version 1 Rev 3 Equipping the RXCDR and ABSS
Equipping the RXCDR and ABSS
Both BSS and RXCDR devices must be individually equipped under DARBC. Each BSS is numbered
(although its creation will be as site 0) from 1 to 254 and each transcoder also from 1 to 254. The
commands inform the system whether the BSS uses local or remote transcoding, and whether dynamic
allocation is in use. Up to 9 RXCDRs may connect to a BSC, and up to 9 BSCs may be served by
an RXCDR. Equipping the BSC is described at Section 2. The equip command for a RXCDR must be
followed by an equip command for the ABSS matching each BSS to which the RXCDR is connected.
RXCDR
The RXCDR device is the rst device equipped in the SYSGEN ON mode at an RXCDR site.
The additional prompt which is displayed is the required RXCDR network number, which has a range
from 1 to 254.
ABSS
The ABSS is equipped after its associate RXCDR. An ABSS is equipped for each BSS served by the
RXCDR. ABSS are logical software-created process models which match existing BSC devices, and are
equipped at RXCDRs to enable the provisioning of Ater circuit resources.
The rst prompt determines the BSS network number of the opposing BSS, whose range is from 1 to
254.
If a GDP/GDP2 is being used as the transcoder, the operator is able to exercise volume control over the
trafc channels passing through it. The volume control can be disabled/enabled by using
chg_element volume_control_type<*><location>[<bss id>]
Uplink and downlink audio level can be changed by
chg_element ul_audio_lev_offset <*> bss_id = <bss_id>
chg_element dl_audio_lev_offset <*> bss_id = <bss_id>
2006 Motorola, Inc.
June 2007
Equipping the RXCDR and ABSS Version 1 Rev 3
Equipping the RXCDR and ABSS
equip 0 rxcdr
enter the rxcdr id 1 to 254
equip 0 abss
enter the abss device id 1 to 254
chg_element volume_control_type<*><location>[<bss_id>]
<*> 0 = Disable GDP volume control
1 = Enable GDP volume control
chg_element ul_audio_lev_offset < *> bss_id = < bss_id>
chg_element dl_audio_lev_offset < *> bss_id = < bss id>
<*> 15 to +15 dB in integer steps (1 Step = 1 dB)
2006 Motorola, Inc.
3-11
June 2007
Version 1 Rev 3 Equipping CICs
Equipping CICs
At both a BSS and a RXCDR a single CIC device, or a range of unique CIC devices has to be equipped.
At the RXCDR, the same CIC number may be used for multiple BSS's.
Which BSS/RXCDR is managing the CICs.
This prompt nominates which BSS is managing the CICs in the case of an RXCDR and which RXCDR
is providing the TRAU resource in the case of an BSS.
MMS id to BSC/RXCDR
This is an optional prompt for use when the operator needs to state which MMS is to be used
for the CICs. The operator may enter a carriage return for the case when auto_connect /
enhanced_auto_connect mode is being used. This has the effect of skipping the starting timeslot
and subgroup prompts and the software automatically equips CICs on the links between the RXCDR
and BSC starting from the rst available timeslot on the rst link.
Starting timeslot and Subgroup (optional)
These prompts only appear if an MMS ID is specied, and where transcoding is carried out remotely.
They identify either the specic timeslot on the E1/T1 link at the BSC on which to add the circuit or the
rst timeslot if a range of circuits is to be equipped. The rst CIC in the range will be equipped on the
timeslot specied. Subsequent CICs follow sequentially through the entire range. 4 x 16 kb/s timeslot
channels are tted into 1 x 64 kb/s timeslot and are numbered 0 - 3. A particular CIC cannot be equipped
more than once per BSS, but at the remote RXCDR, the same CIC number may be used for multiple
BSSs.
MMS id to MSC
This prompt appears only for the RXCDR and for local transcoding BSSs. It nominates the MMS id 1
and id 2 which carry the CICs being equipped to the MSC.
Starting timeslot
This prompt appears only for RXCDR and local transcoding. It identies the starting timeslot on the link
to the MSC.
2006 Motorola, Inc.
June 2007
Equipping CICs Version 1 Rev 3
Equipping CICs
equip 0 cic
enter cics
which BSS is managing the CIC(s)
or which RXCDR provides the T RAU
enter the MMS I D to the BSS
or MMS I D to the RXDCR
enter starting timeslot (static mode)
enter starting subgroup (static mode)
enter the MMS I D to MSC
enter starting timeslot (to MSC)
<cic> [to < cic>]
0 to 65535
1 to 254
<card id> < port id>
0 - 71 0 - 1 (RXCDR)
0 - 55 0 - 1 (BSS)
1 - 31
0 - 3
0 to 71 (MSI)
0 (Port)
1 - 31
2006 Motorola, Inc.
3-13
June 2007
Version 1 Rev 3 Terrestrial Circuits: Circuit Identity Codes (CICs)
Terrestrial Circuits: Circuit Identity Codes (CICs)
Circuit Number
The individual CIC number is constructed by combining the link number and the timeslot number of the
particular trafc channel between the MSC and the Transcoder.
The 5 least signicant bits (LSB) denote the timeslot number of the trafc channel, whilst the remaining
11 bits represent the link number.
Once the timeslot and link number have been entered the entire 16 bit number is read as a whole to
determine the circuit number.
Circuit number 0 or any multiple of 16 are not allowed.
Circuit number 0, 32, 64, etc will refer to the synchronization timeslot and therefore cannot be designated
to carry trafc.
Circuit number 16, 48, etc are reserved for carrying Message Transfer Links (MTL) from the MSC to the
BSC and cannot be processed by an RXCDR card. These also cannot be designated to carry trafc.
Enhanced BSS Capacity
The total number of circuits that can be equipped per BSS can be increased by having the enhanced
BSS capacity feature unrestricted (enabled) from GSR 5.1 onwards.
Feature restricted
2400 Circuits
384 Carriers
Feature unrestricted
3200 Circuits
600 Carriers
For this feature to operate correctly the following GPROC dependencies have to be adhered to:
RXCDR site - GPROC 2 or 3 with 32 MB RAM
BSC site - All GPROCs have to be GPROC 2 or 3 with 64 MB RAM
BTS site (Incell) - BTP Processor has to be a GPROC 2 or 3 with 32 MB RAM
AMR Phase 2
Adaptive Multi Rate (AMR) - phase 1 & 2 introduced at GSR 7, will allow different coding schemes to be
used in an effort to improve the quality of a call to a subscriber and will also see support for AMR halfrate.
This will also allow switching of 8kbps on the backhaul to support AMR half rate (providing GDP2 cards
are equipped) and will increase the number of circuits.
Feature restricted
2400 Circuits 384 Carriers ( 3200 Circuits, 600 Carriers when enhanced BSC is unrestricted)
Feature unrestricted
4800 Circuits
Number of carrier will depend upon the Enhanced BSC and Increased Network Capacity features (up to
750 carriers per BSS)
2006 Motorola, Inc.
June 2007
Terrestrial Circuits: Circuit Identity Codes (CICs) Version 1 Rev 3
Terrestrial Circuits: Circuit Identity Codes (CICs)
1
0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1
32 64
Link 3 Timeslot 1
CIC No = 64 + 32 + 1 = 97
Enhanced BSS Capacity

Restricted 2400 Circuits, 384 Carriers
Unrestricted 3200 Circuits, 600 Carriers

AMR

Restricted 3200 Circuits, 600 Carriers
if Enhanced BSS capacity is not restricted
Unrestricted 4800 Circuits

Number of carriers will carriers depend
upon Enhanced BSS and increased network capacity features
(up to 750 per BSS)
2006 Motorola, Inc.
3-15
June 2007
Version 1 Rev 3 Circuit/Channel Relationship
Circuit/Channel Relationship
Overview
Certain circuit numbering conventions are used by the MSC. In auto-connect/enhanced auto connect
mode, the CICs emanating from the MSC are equipped in the RXCDR which will throughput them; and
the MMS serving the A interface to the MSC through which the CICs pass is nominated by MMS number
and timeslot. The BSC which will manage the CICs is also declared; note that CICs may be declared to
more than one BSC. At each BSC the CICs which it will manage are again equipped, together with the
nominated RXCDR.
In auto-connect/enhanced auto connect Mode when the MSCallocates a CICto a call, the BSCAllocation
Manager, working via the XBL with the Switch manager at the RXCDR, places the call in the next vacant
trafc channel on the Ater interface to the BSC.
In Backwards Compatibility Mode, the CICs are mapped at the RXCDR both to the MSC via a nominated
MMS and timeslot, but also to the BSC via an MMS and TS/Group. At the BSC they are again mapped
to an MMS and timeslot/group connecting to the RXCDR.
The E1/T1 link connecting the Ater interface is nominated via add_conn . The CIC numbering scheme
that the switch follows is reasonably simple:
CCT ID 0 is never used
CCT ID 16 and multiples of 16 are never used.
1st link CCT IDS 1-31 TS 1-31 (TS16 being omitted)
2nd link CCT IDS 33-63 TS 1-31 (TS16 being omitted)
etc...
The idea of this from the switch perspective is that CCT IDs match timeslot numbers in a set pattern.
Relationship Example
equip 0 cic
69
102
1 1
5
3
BSC 1
RXCDR 102
17/0
KSW
ABSS 1 6/0
cic = 69 (16 KBS)
Group = 3
TS = 5
link 2
TS 5
cic no = 69
equip 0 cic
69
1
6 0
5
3
17 0
5
1/1
2006 Motorola, Inc.
June 2007
Circuit/Channel Relationship Version 1 Rev 3
Circuit/Channel Relationship
MSC
equip 0 cic
97 to 111
2
8 0*
3*
0*
22 0
1
equip 0 cic
113 to 127
2
8 0*
6*
3*
22 0
1
equip 0 cic
129 to 143
2
8 0*
10*
2*
23 0
1
equip 0 cic
145 to 152
2
8 0*
14*
1*
23 0
1
23 0
15 0
17 0
equip 0 cic
33 to 47
1
15 0
1
equip 0 cic
49 to 63
1
15 0
17
equip 0 cic
65 to 79
1
17 0
1
equip 0 cic
81 to 95
1
17 0
17
6 1 6 0 8 0 8 1
equip 0 cic
129 to 143
103
1 0*
10*
2*
equip 0 cic
145 to 152
103
1 0*
14*
1*
equip 0 cic
97 to 111
103
1 0*
3*
0*
equip 0 cic
113 to 127
103
1 0*
6*
3*
1 0 1 1
equip 0 cic
33 to 47
102
equip 0 cic
65 to 79
102
1 1
B
S
C
1
B
S
C
2
bss
mms
ts
gp
mms
ts
22 0
R
X
C
D
R
1
0
3
R
X
C
D
R
1
0
2
RXCDR 102 and BSS 1 in
auto_connect mode
CIC = 0, 16 and multiples of 16 are not used.
TS 16 is used for MTL. Other links are also reserved (not listed as CICs).
* = Mandatory for Backwards Compatibility Mode optional for autoconnect
Link 1 Link 2
Link 3
Link 4
equip 0 cic
153 to 159
2
8 0
17*
0*
23 0
1
equip 0 cic
153 to 159
103
1 0*
17*
0*
equip 0 cic
49 to 63
102
equip 0 cic
81 to 95
102
2006 Motorola, Inc.
3-17
June 2007
Version 1 Rev 3 Call Downgrade on CIC Capability Mismatch
Call Downgrade on CIC Capability Mismatch
The purpose of the Call Downgrade on CIC Capability Mismatch feature, which was introduced form
GSR6 software releases onwards is:
Multi-Platform Support
Initially it was assumed that operators wishing to provide EFR (ETSI dened speech version 2) would
swop all there existing XCDR capacity for GDPs. Subsequently due to the cycle time to get EFR
capable mobiles into the market place, a number of operators have chosen to introduce EFR into their
infrastructure in a staged manner. This feature allows XCDR and GDP platforms to co-exist.
Enhanced CIC Management
The co-existence of the XCDR and GDP leads to the concept of pooled transcoding resources within the
BSS, in this instance those CICs terminating on XCDR boards being FR capable and those on the GDP
board being both FR and EFR capable, with both types supporting existing GSM data services. Without
support by the MSC there is no cross verication between MSC and BSS and hence the situation could
occur whereby EFR calls are routed onto XCDR cards resulting in no speech. Call Downgrade on CIC
Capability Mismatch feature addresses this situation by detecting the CIC speech version capabilities of
the BSS based on the supporting transcoding platform i.e. XCDR or GDP.
Enhanced Call Management
This feature also deals with MSC call/handover requests for particular speech versions with the
corresponding CIC capabilities. With the introduction of AMR, and AMR/GSM half rate, which impacts
the current GDP provisioning rules by introducing a new type of transcoding resource, this enhancement
is of heightened importance. Because it is envisaged that these features will be used in the MS well
in advance of feature availability in the BSS. This feature will downgrade the speech version (if other
speech versions are available) or reject it. This includes:
Call set-up request handling - Assignment request for initial call set-up which includes the channel type
IE detailing the CIC and required speech version.
CIC remap request handling - Upon receipt of an assignment request message remapping the CIC for
an existing speech call, where the speech version differs from that already in use, the BSS shall instigate
the channel mode modify procedures.
Handover request handling - Upon receipt of the handover request message fromthe MSCfor a speech
call, the BSS veries the CIC capability information (dictated by the received CIC) with the received
channel type IE speech version(s).
2006 Motorola, Inc.
June 2007
Call Downgrade on CIC Capability Mismatch Version 1 Rev 3
Call Downgrade on CIC Capability Mismatch
Multi-Platform Support
Enhanced CIC Management
Enhanced Call Management
2006 Motorola, Inc.
3-19
June 2007
Version 1 Rev 3 Call Downgrade
Call Downgrade
From GSR7 there are three types of Transcoder which Motorola support, XCDR, GDP and GDP2. Unlike
the XCDR card, the GDP and GDP2 cards are capable of handling Full Rate speech, GSM Half rate
spech, Enhance Full Rate speech, Adaptive Multi Rate speech and Adaptive Multi Rate half rate speech
for Phase 2 + Mobiles (in the case of AMR full and half rate and GSM half rate, GDP cards must be
equipped ). The GDP2 card will in addition will be able to terminate 2E1 links, much like a standard MSI
card.
Because the BSS can support multi transcoder platforms it is possible for EFR/AMR/Half Rate calls
to be routed to non EFR/AMR/Half Rate compatible XCDR cards, resulting in the loss of speech. To
overcome this problem, the Allocation Manager at the remote transcoder or the BSS if local transcoding
is being performed; will maintain information on the capabilities of the CICs that connect to the transcoder
platforms.
It will be the responsibility of the BSS to check if the type of codec requested within the assignment
request or handover request is supported by the allocated CIC. Depending upon the result of this check,
there are 3 possibilities.
1. The capability of the CIC and the codec match and the calls proceeds as normal.
2. The capability of the CIC and the codec are different, but the request includes a list of alternative
codecs. If one of these alternative types matches the CIC capability the BSS will downgrade the call.
3. If the capability of the CIC and the codec is different, and no alternatives are specied in the request,
the BSS will reject the request.
2006 Motorola, Inc.
June 2007
Call Downgrade Version 1 Rev 3
Call Downgrade
BSC/BTS BSC/BTS
GDP
XCDR
MSC PSTN
EFR/AMR
Half Rate Capable
CIC CIC
Sys02_Ch2_24
1. CIC / codec match = call proceeds
2. CIC / codec do not match, alternative
codec specified & supported = call downgraded
3. CIC / codec do not match, no alternative codec
specified or supported = call blocked
Non EFR / AMR / Half Rate capable
2006 Motorola, Inc.
3-21
June 2007
Version 1 Rev 3 Adaptive Multi-Rate
Adaptive Multi-Rate
GSR7 saw the introduction of Adaptive Multi-Rate (AMR) for transcoding. There are two methods of
working which may be employed, AMR Full rate channel mode and AMR Half rate channel mode. Both
these methods can be employed when local or remote transcoding is used. They can only be used
with M-cell, Horizonmacro, Horizon IImacro and Horizon II mini equipment. If 8Kbps switching is to be
employed on the backhaul, then the KSW cards must be replaced by DSW2 cards
AMR Full-Rate Channel Mode
This mode of working provides higher speech quality in poor RF conditions.
AMR Full-Rate Link Adaptation
This mode of working is compatible with the rest of the AMR feature set, such as AMR, Call downgrade
on CIC capability mismatch and Enhanced GDP provisioning. It provides for improved speech quality
by adapting the speech rates and levels of error corrections for individual calls. There are 4 AMR codec
sets which the system may utilised for any given call in both uplink and downlink.
AMR Half-Rate Channel Mode
This mode of working allows two AMR call to be placed onto one air interface channel, thereby
increasing capacity without the need for any further hardware. In general terms the Q of S of an AMR
Half-Rate channel will be lower when compared to a full rate channel. To this end the operator may
specify congestion levels and thresholds when the quality is so poor, that the call may be handed over
to a full rate channel.
AMR Half-Rate Link Adaptation
This mode of working is compatible with the rest of the AMRfeature set, such as AMR, Call downgrade on
CIC capability mismatch and Enhanced GDP provisioning and works in a similar way to AMR Full-Rate
Link Adaptation. The differences are the bit rates of the HR codec set that are supported, the different
initial HR codec mode and different uplink/downlink codec mode adaptation thresholds and hysteresis
values.
Active Codec Sets
The codec values available with AMR are as follows.
0 = 12.20kbps
1 = 10.20kbps
2 = 7.95kbps
3 = 7.40kbps
4 = 6.70kbps
5 = 5.90kbps
6 = 5.15kbps
7 = 4.75kbps
12.2, 10.2, 7.4, 6.7 & 5.15 are for AMR Full rate
7.95, 7.4, 6.7, 5.9 & 5.15 are for AMR Half rate
2006 Motorola, Inc.
June 2007
Adaptive Multi-Rate Version 1 Rev 3
Adaptive Multi-Rate
AMR Full - Rate Channel Mode
AMR Full Rate Link Adaptation
AMR Half - Rate Channel Mode
AMR Half Rate Link Adaptation
Codecs
0 = 12.20kbps
1 = 10.20kbps
2 = 7.95kbps
3 = 7.40kbps
4 = 6.70kbps
5 = 5.90kbps
6 = 5.15kbps
7 = 4.75kbps
12.20kbps, 10.20kbps, 7.40kbps, 6.70kbps & 5.15kbps used for AMR Full - Rate
7.95kbps, 7.40kbps, 6.70kbps, 5.9kbps & 5.15kbps used for AMR Half - Rate
Sys102_Ch2_25
2006 Motorola, Inc.
3-23
June 2007
Version 1 Rev 3 AMR/GSM Half Rate
AMR/GSM Half Rate
AMR/ GSM Half Rate speech can be employed when local or remote transcoding is used, but only if the
transcoding card is a GDP/GDP2. In addition the feature may not be used with Incell BTS products. If
8Kbps switching is to be employed on the backhaul, then the KSW cards must be replaced by DSW2
cards which applies to both AMR Half Rate and GSM Half Rate.
AMR Half Rate/GSM Half Rate
It is possible to mix AMR half rate calls and GSM half rate calls on the same physical timeslot within a
carrier.
Enabling AMR/GSM Half Rate
When enabling the AMR/GSM Half Rate feature, the operator has the ability to carry out this function at
BSS, Cell and RTF level. These are carried out by the following database commands:
gsm_bss_half_rate_enabledused for the BSS
amr_bss_half_rate_enabledused for the BSS
gsm_half_rate_enabledused or the Cell
amr_half_rate_enabledused for the BSS
half_rate_enabled used for the RTF (note: this command applies to both GSM and AMR half
rate)
2006 Motorola, Inc.
June 2007
AMR/GSM Half Rate Version 1 Rev 3
AMR/GSM Half Rate
gsm_bss_half_rate_enabled <*>
* 0 - disabled
1 - enabled
gsm_half_rate_enabled <*>
* 0 - disabled
1 - enabled
half_rate_enabled <*>
* 0 - disabled
1 - enabled
SYS02_Ch2_37
amr_bss_half_rate_enabled <*>
* 0 - disabled
1 - enabled
amr_half_rate_enabled <*>
* 0 - disabled
1 - enabled
2006 Motorola, Inc.
3-25
June 2007
Version 1 Rev 3 Enhanced GDP
Enhanced GDP
Enhanced GDP
Enhanced GDP provisioning has been introduced to provide support for GDP's capable of enhanced
transcoding features, particularly AMR and ETSI dened TFO (Tandem Free Operation), in addition to
supporting current services. When equipping an MSI type, one of the options is GDP, a board which
provides the transcoding functions of the BSS. One GDP card has the ability to process a maximum
of 30 full rate or 30 half rate calls on the 15 available DSPs, ie 2 calls per DSP. As new transcoding
techniques are introduced, such as AMR, the processors will only be able to process a single call on one
DSP. Because the link to and from the MSC can carry 30 calls on the E1 link, GDP cards will have to be
congured in pairs to support this type of transcoding.
GDP Pairs
When the GDP boards are equipped, the Primary GDP connects to the MSC and will process 15 calls,
while the Secondary GDP which will process the other 15 calls can connect to a BSC/BTS, or to an MSI
card. These two congurations are shown on the facing page. A Primary GDP can never be paired with
a XCDR card.
Transcoding Capability
The Primary GDP can be initialized to handle enhanced transcoding. In addition, an enhanced capable
transcoder may be recongured to basic transcoding by use of themodify_value command. However,
the GDP must rst be locked, and will only be allowed if it is not paired with a secondary GDP. (If this
was allowed, the secondary GDP would have no connection to the MSC to send and receive calls)
GDP2
If the option of GDP2 was selected when using the equip_msi command, the selected card will be able
to handle the required number of circuits for use with AMR and will therefore not be equipped as a pair.
The number of calls that a GDP2 can handle will depend upon the cabinet conguration and whether
local or remote transcoding is in use (this is shown in the table below). If a GDP 2 is being used in basic
transcoding mode it will only be able to handle 30 GSM half rate calls.
LOCAL TRANSCODING
- GDP2
REMOTE TRANSCODING -
GDP2
RXUx/BSSCx BSUx/BSSCx
MSI/RXCDR
RXU3
/BSSC3
RXUx
/BSSCx
BSUx/BSSCx
MSI/RXCDR
RXU3/BSSC3
30 calls 60 calls 60 calls 30 calls 60 calls 60 calls
2006 Motorola, Inc.
June 2007
Enhanced GDP Version 1 Rev 3
Enhanced GDP
GDP
PRIMARY
GDP
SECONDARY
15 DSPs
15 DSPs
MSI
TDM
BUS
E1 LINK
TO/FROM
MSC
GDP PAIRINGS
GDP
PRIMARY
GDP
SECONDARY
15 DSPs
15 DSPs
MSI
TDM
BUS
E1
TO/FROM
MSC
GDP
PRIMARY
GDP
SECONDARY
15 DSPs
MSI
TDM
BUS
SYS02_Ch4_40
15 DSPs
E! LINK
To/From
BSC/BTS
GDP
PRIMARY
15 DSPs
GDP
SECONDARY
15 DSPs
TDM
BUS
E1 LINK
TO/FROM
MSC
E1 LINK
TO/FROM
BSC/BTS
GDP REPLACING MSI BOARD
GDP
PRIMARY
15 DSPs
GDP
SECONDARY
15 DSPs
TDM
BUS
GDP
PRIMARY
15 DSPs
GDP
SECONDARY
TDM
BUS
15 DSPs
2006 Motorola, Inc.
3-27
June 2007
Version 1 Rev 3 Enhanced GDP
Enhanced GDP
The equipcommand parameters for equipping a GDP pair and for equipping a GDP2 are shown opposite.
2006 Motorola, Inc.
June 2007
Enhanced GDP Version 1 Rev 3
Enhanced GDP
Equipping a GDP Pair
Equip a primary GDP.
equip 0 msi
Enter the MSI identier: 1 (RXCDR 0 to 123)
Enter the cage number: 0 (0 to 15)
Enter the slot number: 14 (MSI type 0 - 6 to 10, MSI type 1, 2 or 20 - 6 to 24 )
Enter the MSI type: gdp (msi, xcdr, or gdp applicable)
Enter the MSI ID to the MSC: 1 0 (If msi type is gdp, then MSC MMS id is always 0)
Enter the transcoding capability: enhanced
( Only prompts if msi_id is same as MMS ID to the MSC 0 = basic, 1 = enhanced)
Equip a secondary (enhanced) GDP
equip 0 msi
Enter the MSI identier: 2
Enter the cage number: 0
Enter the slot number: 15
Enter the MSI type: gdp
Enter the MMS ID to the MSC: 1 0 (Identies as secondary gdp)
Equipping a GDP 2
Equip GDP 2.
equip 0 msi
Enter the MSI identier: 1 (RXCDR 0 to 123)
Enter the cage number: 1 (0 to 15)
Enter the slot number: 14 (MSI type 0 - 6 to 10, MSI type 1, 2 0r 20 - 6 to 24 )
Enter the MSI type: 20 (msi, xcdr, gdp or gdp 2 applicable)
Enter the MSI ID to the MSC: 1 0 (If msi type is gdp, then MSC MMS id is always 0)
Enter the transcoding capability: enhanced (Only prompted if msi_id is same as MMSID to the MSC 0 =
basic, 1 = enhanced, 2 = GDP2_E1)
2006 Motorola, Inc.
3-29
June 2007
Version 1 Rev 3 On Line Reconguration of GDP Cards
On Line Reconguration of GDP Cards
On Line Reconguration of GDP cards
On line reconguration, shown opposite allow changes to the board conguration within a RXCDR
or BSC cage, for example to increase the proportion of enhanced transcoding circuits available. The
replacement of MSIs and XCDRs with GDP cards and the upgrading of Basic GDP boards to provide
enhanced transcoding, can be performed with minimal modication of the channel/circuit usage, or
external connectivity specication of the E1 links.
XCDR or MSI to GDP
To change an XCDR or an MSI to a GDP, having rst locked the board and then physically replaced it,
the modify msi_type command would be used to change its type to a GDP.
If the newly equipped GDP card was to support enhanced transcoding, this would be enabled by use of
the modify transcoding_type command. As enhanced transcoding must be enabled at the Primary
GDP, the msc_mms will automatically be set to the GDPs own mms.
Modication from an MSI to an Enhanced Secondary GDP involves the operator being prompted for the
msc_mms ID before the change in the msi_type attribute is accepted.
2006 Motorola, Inc.
June 2007
On Line Reconguration of GDP Cards Version 1 Rev 3
On Line Reconguration of GDP Cards
Basic GDP
XCDR
Enhanced GDP
(Primary)
Enhanced GDP
(Secondary)
MSI
modify msi_type
modify transcoding_type
msc_mms defaults to
GDPs own MMS
modify msc_mms _id
GDPs MMS id = Primary GDP MMS id
modify msi_type
set msc_mms_id
2006 Motorola, Inc.
3-31
June 2007
Version 1 Rev 3 Transcoder On-Line Expansion
Transcoder On-Line Expansion
Overview
The transcoding capacity (and therefore the trafc circuit capacity) of a network can be increased on-line,
i.e. without interruption to service. This is possible because the associated commands are allowed
outside SYSGEN mode. Trafc circuits can be added or deleted at the BSS and RXCDR, control links
can be mapped through the RXCDR and XBLs equipped all on-line.
The full list of commands possible outside SYSGEN mode is shown opposite.
Before unequipping a control link it must be locked as is the case before unequipping any other device.
2006 Motorola, Inc.
June 2007
Transcoder On-Line Expansion Version 1 Rev 3
Transcoder On-Line Expansion
XCDR on-line expansion
equip
unequip
chg_ts_usage nail
add_conn
del_conn
mod_conn
2006 Motorola, Inc.
3-33
June 2007
Version 1 Rev 3 MSC Quietone
MSC Quietone
Overview
During call set-up or handover the MSC-RXCDR circuit will be idle, the bit pattern that the MSC transmits
and expects to receive for this condition is called MSC Quietone. Different switch manufacturers may
require a different quietone and therefore this pattern can be set.
This parameter is only valid at a site that is equipped with a transcoder or GDP/GDP2 card, the range is
0-255 (one byte).
2006 Motorola, Inc.
June 2007
MSC Quietone Version 1 Rev 3
MSC Quietone
MSC
RXCDR
BTS
IDLE CONDITION
(MSC QUIETONE)
IDLE FRAME
chg_element msc_qt <*> <site>
* 0-255
2006 Motorola, Inc.
3-35
June 2007
Version 1 Rev 3 Downlink DTX
Downlink DTX
Overview
Within the XCDR/GDP/GDP2 card is a Voice Activity Detector (VAD), together with its rmware routine
this device can detect, if enabled, the difference between speech and noise being received on each PCM
channel. The 320 bit (260 Bits GSM dened speech plus 60 bits TRAU) block will either be identied
as speech or a silence descriptor frame (block), by the TRAU overhead. DTX may be in use for this air
interface channel, if so, the channel coder will transmit appropriate SID frames on the air interface. If
downlink DTX is not being used for this call then the channel coder will process each SID frame as if it
were trafc.
This parameter is applicable only in locations where the XCDR/GDP/GDP2 is present and if disabled will
not allow DTX to take place regardless of other DTX parameters.
The downlink DTX option needs to be enabled in the MSCswitch. When an assignment request message
is sent from the MSC to the BSS a ag called a downlink DTX is set.
The parameter dl_dtx_voice_data further species the enablement for speech and for
non-transparent data, on a per cell basis.
0 = dtx enabled for speech - disabled for non-transparent data.
1 = dtx disabled for speech - disabled for non-transparent data.
2 = dtx disabled for speech - enabled for non-transparent data.
3 = dtx enabled for speech - enabled for non-transparent data.
Default = 0.
2006 Motorola, Inc.
June 2007
Downlink DTX Version 1 Rev 3
Downlink DTX
DTX specified
from RXCDR
SPEECH
chg_element dnlk_vad_dtx <*> <site no>
* 0 = Downlink DTX Enabled
1 = Downlink DTX Disabled
XCDR
VAD
DRIM
CC
MS
VAD
AND/OR
MANDATORY
SID
BLOCKS
dnlk_vad_dtx
SPEECH
NOISE
PCM
DATA,
NOISE
OR
SPEECH
dl_dtx_voice_data
2006 Motorola, Inc.
3-37
June 2007
Version 1 Rev 3 Downlink DTX
2006 Motorola, Inc.
June 2007
Chapter 4
BSS Conguration
2006 Motorola, Inc.
4-1
June 2007
Version 1 Rev 3 BSS Conguration
2006 Motorola, Inc.
June 2007
BSS Conguration
Objectives
Describe the principle of device/function equipage
Describe the equipage of functions within the BSS
Describe the External Alarm System
Describe the MTP Level 3 parameters
Describe the process of EMPPS
Describe the Multiple Encryption Algorithms
Explain CERM/ECERM
Describe the SMS Options and Multiple Background Messages
Describe the Flow Control procedures and RACH Load calculations
Describe the Overload Mechanisms
Describe Location Based Services
Complete a written exercise to partly equip a BSS database
2006 Motorola, Inc.
4-3
June 2007
Version 1 Rev 3 Device and Function Dependency - In-Cell
Device and Function Dependency - In-Cell
Some devices/functions are dependent upon other devices having already been equipped to support
them. For example, before a Receive Transmit Function (RTF) can be equipped a Digital Radio Interface
Extended Memory (DRIM) must be equipped to support it. The chart opposite shows the device and
equipment hierarchy for In-Cell systems
The use of InCell is an optional feature in GSR9.
2006 Motorola, Inc.
June 2007
Device and Function Dependency - In-Cell Version 1 Rev 3
Device and Function Dependency - In-Cell
SYS02_Ch4_02
COMB KSW GCLK GPROC EAS MSI
BSS SITE (BSC)
CAB
CELL CAGE
LCF OMF RSLF
64 kbit/s RSL
RTF
XBL PAT H
BSP BTP DHP CSFP
DRI
OML
16 kbit/s RSL
Associated RTF
CIC
MMS *
RF_Unit
NOTE: * indicates an automatically equipped device
BTS SITE PCU
CBL
MTL
(See Note
below)
GSL
AXCDR
PSI
ETH**
GDS**
** supports TRAUand LAPD
GSL
2006 Motorola, Inc.
4-5
June 2007
Version 1 Rev 3 BSS - 1.9.0.0 Script Building
BSS - 1.9.0.0 Script Building
Script Chart
The script chart shown opposite species the groups of parameters necessary to populate a BSS
database. From GSR9, the BSS Database will be between 6MB and 8MB. The actual parameters can
be examined more closely by following the example script on the following pages..
MSC
OMC
RXCDR 101 RXCDR 102 RXCDR 103
BSS 1 BSS 2
CIC 1 to 9
Link 0
CICs 97 to 100
CICs 129 to 132
Links 3 and 4
CIC 33 to 44
CIC 65 to 76
Links 1, 2
9 Ater
circuits
12 Ater
circuits
12 Ater
circuits
8 Ater
circuits
OML
OML
OML
MSI 1
MSI 5
MSI 9
0 1
0 1
0 1 0 1
0 1 0 1 0 1
0 1 0 1
GDP GDP GDP
GDP GDP
MSI MSI
MSI 2 MSI 1
MSI 6 MSI 8
MSI 10
(17) (15)
(23) (22)
MSI 8
M
S
I
M
S
I
0
1
MSI 10
2006 Motorola, Inc.
June 2007
BSS - 1.9.0.0 Script Building Version 1 Rev 3
Script Chart
Equip BSS
Device/Function Equipage
Equip AXCDR
Equip CAB
Equip CAGE
Site Configuration
MMS Thresholds
Equip Links
Equip Ater Circuits
Miscellaneous
2006 Motorola, Inc.
4-7
June 2007
Version 1 Rev 3 BSS - 1.9.0.0 Script Files
BSS - 1.9.0.0 Script Files
# EXAMPLE BSS DATABASE
# 1.9.0.0.GSR9
# Equipage of BSS 1 (connected to RXCDRs 101 and 102)
# BSS Name : BSS01
# Software Release : 1.9.0.0
equip 0 bss
1 # bsc number
no # is local transcoding performed at the BSC?
equip 0 axcdr
101 # axcdr id
yes # auto-connect enabled
no # eac_mode enabled
freq_types_allowed 5 #pgsm and 1800 in this BSS
equip 0 cab
0 # cab id
5 # cab type
5 # frequencies allowed
equip 0 cage
0 # cage id
0 # ksw pair
# no kswx
# no kswx red
0 # cab id
yes # IAS connected
equip 0 axcdr
102
yes
no
chg_element gproc_slots 32 0 # 32 timeslots required on TDM highway - gproc 2 or 3 only
chg_element bsc_type 1 0 # bsc type 1 - bsp with lcf's
# E1 link parameters left at default values
equip 0 ksw
0 # TDM highway
0 # TDM id
0 # Cage number
no # drims not allowed
equip 0 bsp
0 # Identier
0 # Cage
20 # Slot
equip 0 gproc
1 # Identier
0 # Cage number
23 # Slot number
equip 0 lcf
1 # Identier
1 # No of MTLs LCF can manage
0 # No of CBLs LCF can manage
equip bsc GPROC
2
0
21
equip bsc LCF
2
0
0
2006 Motorola, Inc.
June 2007
BSS - 1.9.0.0 Script Files Version 1 Rev 3
equip bsc GPROC
3
0
22
equip bsc LCF
3
0
0
equip bsc GPROC
4
0
24
equip bsc LCF
4
0
0
# DEFAULT ALARM MESSAGES
chg_eas_alarm 0 0 "Burglar"
chg_eas_alarm 1 0 "Door Open"
chg_eas_alarm 2 0 "Fire"
chg_eas_alarm 3 0 "High Temperature"
chg_eas_alarm 4 0 "Low Temperature"
chg_eas_alarm 5 0 "High Humidity"
chg_eas_alarm 6 0 "Low Humidity"
chg_eas_alarm 7 0 "Tower Beacon Outage"
chg_eas_alarm 8 0 "Surge Arrestor Failure"
chg_eas_alarm 9 0 "Microwave Trans. Failure"
chg_eas_alarm 10 0 "AC Power Failure"
chg_eas_alarm 11 0 "Generator Running"
chg_eas_alarm 12 0 "Generator Failed"
chg_eas_alarm 13 0 "PSU Rectier"
chg_eas_alarm 14 0 "PSU Battery"
chg_eas_alarm 15 0 "PSU Fuse"
chg_eas_alarm 16 0 "Personnel on Site"
chg_eas_alarm 17 0 "General Alarm 1"
chg_eas_alarm 20 0 "PCU Over Temperature"
chg_eas_alarm 21 0 "PCU Customer Dened 1"
chg_eas_alarm 22 0 "PCU Door Open"
chg_eas_alarm 23 0 "PCU DC Fail"
chg_eas_alarm 24 0 "PCU Circuit Breaker"
chg_eas_alarm 25 0 "PCU AC Fail"
chg_eas_alarm 26 0 "PCU Comms Equipment"
chg_eas_alarm 27 0 "TDU Over Temperature"
chg_eas_alarm 28 0 "TDU Door Open"
chg_eas_alarm 29 0 "TDU Circuit Breaker"
chg_eas_alarm 30 0 "TDU Battery"
chg_eas_alarm 31 0 "TDU Customer Dened 1"
equip 0 gclk
0 # gclk id
0 # cage num
no # clkx 0
no # clkx 1
no # clkx 2
equip 0 msi # to rxcdr 102
1 # mms id 1
0 # cage no
16 # slot no.
0 # msi type
2006 Motorola, Inc.
4-9
June 2007
Version 1 Rev 3 BSS - 1.9.0.0 Script Files
equip 0 msi
9
0
8
0
equip 0 msi
5
0
12
0
add_conn 1 0 101 10 0 # local mms (1) and (2) AXCDR distant # mms (1 ) and (2)
add_conn 1 1 102 6 0
equip 0 cic
5 to 9 # cic's 5 to 9
101 # rxcdr to which connected
equip 0 cic
18 to 21
101
equip 0 cic
33 to 34
102
equip 0 cic
65 to 76
102
equip 0 mtl
0 # device id
1 # msi id
0 # port id
16 # timeslot
equip 0 oml
0 # device id
1 # msi id
0 # port id
1 # timeslot
equip 0 xbl
101 # axcdr device id
0 # second id for xbl
64 # data rate for xbl
1 # mms id
0 # port id
15 # timeslot
2500 # T200
3 # N200
7 # K value
equip 0 xbl
102
0
64
1
0
2
2500
3
7
chg_element opc 109 0 # OPC for this bsc 109
chg_element dpc 10 0 # DPC for MSC connect to this bsc 10
chg_element ni 2 0 # SS 7 link set to national network
chg_element stat_interval 60 0 # statistical interval set to every 60m
2006 Motorola, Inc.
June 2007
BSS - 1.9.0.0 Script Files Version 1 Rev 3
chg_element option_alg_a5_1 1 0 # encryption alg 1 enabled
chg_element option_alg_a5_2 1 0 # encryption alg 2 enabled
chg_a5_alg_pr 1 2 0 # encryption priority set to alg 1 and then alg 2
chg_element handover_required_sp_ver_used 1 0 # set to enabled
chg_element efr_enabled 1 0 # efr enabled
chg_element option_peempt 3 0 # ECP & eMLPP both enabled
modify_value 0 mms_priority 255 mms 1 0 0 # mms 1 port 0 set to highest priority
modify_value 0 mms_priority 254 mms 1 1 0 # mms 1 port 1 set to 2nd highest priority
modify_value 0 mms_priority 0 mms 9 0 0 # mms will not be selected
modify_value 0 mms_priority 0 mms 9 1 0
chg_element phase_lock_gclk 1 0 # phase locking enabled
chg_element rsl_lcf_congestion_thi 90 bsc #level to register rsl congestion
chg_element rsl_lcf_congestion_tlow 30 bsc # level to remove rsl congestion
chg_element msc_bss_overload_allowed 1 bsc # send overload message to msc
chg_element bss_overload_control 60000 bsc # rate to send overload message to msc
chg_element rsl_congestion_alarm_timer 3000 bsc # rate to send rsl congestion alarms to OMC-R
chg_element max_pagenum_per_sec 200 bsc # max number of paging message to BTS
2006 Motorola, Inc.
4-11
June 2007
Version 1 Rev 3 Link Control Function (LCF)
Link Control Function (LCF)
The BSC has to interface signalling information to and from the MSC, SLMC, CBC and BTS sites. LCFs
can only be equipped at BSS site.
GPROCs are assigned the LCF which is equipped in the database and it is not necessary to specify a
particular GPROC to be assigned the LCF. A GPROC has to be equipped at the site and functionality is
distributed on initialisation. To equip an LCF the following command must be used:
equip <0 or bsc> LCF
Prompts
prompt 1 (identier)
This eld species the LCF identication (0-24)
prompt 2 (MTLs)
This prompt species the maximum number of MTLs that the LCF can manage. This attribute can be
set to 31only if the Increased Network Capacity optional feature is unrestricted.
prompt 3 (LMTLs)
This prompt species the maximum number of LMTLs that the LCF can manage.
prompt 4 (CBLs)
This eld species the maximum number of Cell Broadcast Links (CBLs) that the LCF can manage.
Increasing the value may reduce the link capacity of the LCF. The max_cbls can be changed when
max_mtls does not equal 31.
prompt 5 (GSLs)
This prompt species the maximum number of GSLs that the LCF can manage. This parameter can be
used only if the GPRS feature is unrestricted. The sum of all max_gsls specied by the equipped LCFs
must be greater than or equal to the total number of GSLs equipped. The value for max_gsls must not
exceed the available LCF HDLC channel capacity. The max_gsls can be changed to non-zero value
when max_mtls does not equal to 31.
The BSC will support the modied MMI command modify_value to modify any of the above
parameters. This command can only be entered at the BSC.
Modify_value<location><value_name><new_value><dev_func><dev_func_id1><dev_func_id2><dev_func_i
2006 Motorola, Inc.
June 2007
Link Control Function (LCF) Version 1 Rev 3
Link Control Function (LCF)
Link Control Function (LCF) Parameters
equip < 0 or bsc > LCF
enter the function identifier for the LCF:
024
enter the number of LMTLs the LCF can manage:
02 **
enter the number of DS0 channels the LCF
can manage as MTLs:
0,1,2,31*
enter the number of Cell Broadcast Links (CBLs)
the LCF can manage:
0/1 **
enter the number of GSLs the LCF can manage:
012 **
Note:
*: To processing 64k MTL, valid value is 0,1 or 2 for all types of GPROC.
For HSP MTL, the valid value is 31. In GSR9, value between 3-30 are invalid.
**: these prompts only pop up when MTL DS0 channels handled by
the LCF is set to 0,1 or 2.
2006 Motorola, Inc.
4-13
June 2007
Version 1 Rev 3 Operations and Maintenance Function (OMF)
Operations and Maintenance Function (OMF)
This GPROC device can only be equipped at a BSC type 2. When a BSC type 2 is specied it causes
the software controlling both the XBL and OML to migrate to the available OMF GPROC. To equip an
OMF the following command must be used:
equip <0 or bsc> OMF
(there are no prompts.)
2006 Motorola, Inc.
June 2007
Operations and Maintenance Function (OMF) Version 1 Rev 3
Operations and Maintenance Function (OMF)
equip < 0 or bsc > OMF
No prompts
SYS02_Ch4_15
2006 Motorola, Inc.
4-15
June 2007
Version 1 Rev 3 External Alarm System
External Alarm System
Overview
Required customer site alarms can be connected through the parallel Interface extension cards, tted in
the digital cage of In-Cell, upper slots 15 & 16 or the digital frame in M-Cell. These PIX cards each have
eight opto inputs and four dry contact relay outputs. In the database up to 8 cards can be specied per
BTS for In-Cell; although each PIX card must be congured separately for M-Cell only one card can be
congured per cabinet to a maximum of 4 per site. The functionality resides on an AB6 at an M-Cell site.
First ID
The EAS Identity within the site for In-cell sites is that of the PIX card, for M-Cell sites it is the cabinet id.
Cage ID
The cage identity where the PIX is tted. (Not prompted at M-Cell sites)
Backplane slot position
Although this eld has a valid range of 0-31 slots, the PIX card can only be tted into slots 15 & 16 in an
RXU and slots 15-18 in a BSU, depending on its age. (Not prompted at M-Cell sites)
Initial output relay settings
Each output relay will be initially set to the open (1) or closed (0) position by customer wiring. Where
the customer has wired between the Common and the Normally Open (N/O) contact, the de-energised
setting will be Open (1) and where the wiring is between the Common and the Normally Closed (N/C)
contact the setting will be closed (0). Four outputs must be set, regardless of whether they are being
used or not.
Input Opto's no alarm condition
The no alarm condition' has to be specied for each of 8 or 16 opto alarm inputs, open (1) and closed
(0). Eight conditions must be set, regardless if they are being used or not.
Reported Opto state changes
The master GPROC will only report on a change of state of an opto input if specied in this list.
Alarm index
A text string which will appear in a resulting alarm condition can be specied for each of the 8 or 16 opto
inputs. Eight alarm indexes must be specied regardless if they are being used or not.
The text string "mpf" is used in place of one of the integers to indicate which opto input is used for the
EAS mains power failure alarm.
2006 Motorola, Inc.
June 2007
External Alarm System Version 1 Rev 3
Equip (site Number) EAS:
Enter the first ID for the EAS:
0-15 M-Cell (This is the cabinet ID for M-Cell)
0-7 In-Cell (This is the EAS ID for In-Cell)
Enter the cage where the PIX is connected: 0-15
(Not prompted for M-Cell sites)
Enter the daughter slot where the PIX is located: 15-18
(Not prompted for M-Cell sites)
Enter the relay wiring of the 4 relays: 0/1 0/1 0/1 0/1
(Only 3 relays for HorizonIImicro)
Enter the input of the optos for no alarm condition: (0 or 1)
Enter 1 to 8 for In-Cell
1 to 16 for M-Cell sites
1 to 6 for HorizonIImicro
Enter each opto whose state changes are to be reported:
Enter 1 to 8 for In-Cell
1 to 16 for M-Cell sites
1 to 6 for HorizonIImicro
Enter the user defined alarm index for the 8 or 16 optos:
External Alarm System (EAS) Parameters
list 0-33, mpf
2006 Motorola, Inc.
4-17
June 2007
Version 1 Rev 3 EAS Alarm Text String
EAS Alarm Text String
As mentioned on the previous page, a text string, which will appear in any resulting alarm condition, can
be specied for each of the eight opto inputs. Thirty-four text string messages may be entered per BSS
(0-33) each with a unique id.
chg_eas_alarm <1><2><3>
Alarm_table_index
Values are in the range 0-33, thirty-four text strings can be specied for each BSS. This value corresponds
to the number entered as the last parameter in the equip_device EAS.
Severity
The severity level of an alarm can be nominated out of ve categories:
0 investigate
1 critical
2 major
3 minor
4 warning
Text string
The maximum length of the alarm text string is 24 characters and must be entered between quotation
marks, i.e. "TEXT".
2006 Motorola, Inc.
June 2007
EAS Alarm Text String Version 1 Rev 3
EAS Alarm Text String
chg_eas_alarm <1> <2> <3>
1. Alarm table index (0 33)
2. Severity (0
4)
3. Text string (up to 24 characters) and must be
entered between quotation marks, i.e. TEXT
Note: If an EAS is equipped at an RXCDR this command must
also be entered as the RXCDR has its own OML.
2006 Motorola, Inc.
4-19
June 2007
Version 1 Rev 3 EAS Exercise
EAS Exercise
Using the details specied opposite complete the following database parameters:
BTS Script (site 32)
equip _ _ _ _ EAS
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_
_
_
_
_
_
_
_
equip _ _ _ _ EAS
_ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
_
_
BSC Script
chg_eas_alarm _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
chg_eas_alarm _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
chg_eas_alarm _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
chg_eas_alarm _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
chg_eas_alarm _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
2006 Motorola, Inc.
June 2007
EAS Exercise Version 1 Rev 3
EAS Exercise
SITE 32, ONLY 1 CAGE
ONLY 1 PIX CARD, SLOT 16 OF BSU
Outputs include:
O/P 1: Burglar alarm reset (rest condition is closed)
O/P 2: Smoke alarm reset (rest condition is open)
Inputs include:
I/P 1: Burglar alarm (alarm condition is open)
I/P 2: Smoke alarm (alarm condition is open)
I/P 3: Door intruder (alarm condition is open)
I/P 4: High temperature (alarm condition is closed)
I/P 5: Low temperature (alarm condition is open)
SITE 33 (M-Cell6 site)
An AB6 with no extension is fitted.
No outputs
Inputs Include:
I/P 1: High temperature (alarm condition is closed)
I/P 2: Low temperature (alarm condition is open)

All inputs connected to the card are to be reported (i.e. optos used)

Use appropriate text strings, numbered from 0-4 as per alarm inputs to site 32

Alarm severity for all alarms is "major".
2006 Motorola, Inc.
4-21
June 2007
Version 1 Rev 3 MTP Level 3 Parameters
MTP Level 3 Parameters
Signalling Point Codes
The signalling protocol used on the A interface is ITU-7 signalling system SS7. The rst three layers of
this protocol are constructed using Message Transfer Part' level 1, 2 and 3. Level 3, in a true SSN
o
7
network, would be responsible for routing messages to particular signalling points, to enable this each
signalling point is allocated a Signalling Point Code (SPC). This SPC can then be included, within MTP
level 3, in any message directed at that signalling point.
This wider use of signalling point codes may implemented on the A interface if the MTP is routed via
an intermediate node. In this case, the parameter chg_element stp_pc_enbaled is set to 1 and a
point code must be entered for this node by use of the paramterchg_element stp_pc. In any event
signalling point codes still have to be entered but only for each end of the A interface.
A network indicator (NI) also has to be specied for each message, again this has a much wider use in a
true SS7 network. As far as the MTP layer 3 on the A interface is concerned each message will terminate
at the MSC and therefore the value used for this parameter should equal 2, for a National Network.
With the introduction of Location Based Services, the BSS may now have another DPC.
2006 Motorola, Inc.
June 2007
MTP Level 3 Parameters Version 1 Rev 3
MTP Level 3 Parameters
BSS MSC
A Interface
SPC= 15 SPC= 33
Originating Point Code= 15
Destination Point Code= 33
Originating Point Code= 33
Destination Point Code= 15
chg_element opc < value><site>
chg_element dpc<value><site>
chg_element ni < *><site>
* value in range 0-3
0 - international network
1 - spare
2 - national network
3 - reserved for national use
chg_element stp_pc < *> 0
* 0 - 16383
chg_element stp_pc_enabled < *> 0
* 0 = disabled
1 = enabled
2006 Motorola, Inc.
4-23
June 2007
Version 1 Rev 3 Enhanced Multi-level Precedence and Pre-emption Service
Enhanced Multi-level Precedence and Pre-emption Service
Overview
Up until GSR8, precedence and pre-emption was only allowed for emergency calls, as all other calls were
classed as low priority. From GSR8, eMLPP functionality allows all calls to be allocated a precedence
dependant 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, emergency services or premium
rate subscribers to be given preferential treatment. The BSS shall use this precedence to manage the
active calls in certain scenarios. The key scenarios where the precedence of a call will be utilized as
follows;
Pre-emption
Queuing
BSS Feature Interaction
The Pre-emption mechanismof eMLPPwill work in tandemwith the existing Emergency Call Pre-emption
feature by allowing a call of higher priority or precedence to gain access to a BSS, by releasing an
established vulnerable call of lower priority where there are no idle resources available that can be used
by a high priority call.
Pre-emption covers a number of areas which are as follows:
TCH pre-emption (which includes Emergency Call Pre-emption)
Ater pre-emption
There are two other areas of optional functionality that may be controlled by the operator. these are:
Priority protection of PDTCH
Priority level based upon selection of functionality
2006 Motorola, Inc.
June 2007
Enhanced Multi-level Precedence and Pre-emption Service Version 1 Rev 3
TCH pre-emption (including Emergency Call Pre-emption)
Ater pre-emption
TCH pre- -emption)
Ater pre-emption

Pre -emption
Queuing
-
The use of Precedence
Types of Pre-emption
2006 Motorola, Inc.
4-25
June 2007
Assignment request / Handover Request
The MSC will allocate eMLPP priority, pre-emption capability, pre-emption vulnerability and queuing
ability to the call, which is mapped (by the MSC) onto the priority format and transmitted to the BSS
within the ASSIGNMENT REQUEST or HANDOVER REQUEST. The BSS will then use this information
to manage the call. This information contained within the Priority IE is comprised of;
Priority Level Range from 1(highest priority) 14(lowest priority).
Pre-emption Capability Indicator (PCI) Indicates if call can trigger pre-emption of vulnerable lower
priority calls. Range 0(not capable)-1(capable)
Pre-emption vulnerability Indicator (PVI) Indicates whether the call is vulnerable to pre-emption.
Range 0(not vulnerable)-1(vulnerable)
Queuing Allowed (QA) Indicates if the call may be queued or not. Range 0(not allowed)-1(allowed)
The database parameter option_peempt is used to enable or disable eMLPP and / or ECP within the
BSS, but it is the MSC that actually controls pre-emption.
2006 Motorola, Inc.
June 2007
octet 3 Priority
octet 2 Length
octet 1 Element identifier
1 2 3 4 5 6 7 8
octet 3 Priority
octet 2 Length
octet 1 Element identifier
1 2 3 4 5 6 7 8
octet 3 pvi qa priority level pci spare
1 2 3 4 5 6 7 8
octet 3 pvi qa priority level pci spare
1 2 3 4 5 6 7 8
Priority Level - Range from 1(highest priority) 14 (lowest priority)
Pre-emption Capability Indicator (PCI) - Range 0 (not capable) -1 (capable)
Pre-emption Vulnerability Indicator (PVI) - Range 0 (not vulnerable) 1
(vulnerable)
Queuing Allowed (QA) - Range 0 (not allowed) 1 (allowed)
Enabling ECP & eMLPP
option_preempt = <*> (default 0)
* 0 -3
0 = ECP & eMLPP are both disabled
1 = ECP enabled
2 = eMLPP enabled
3 = ECP & eMLPP are both enabled
2006 Motorola, Inc.
4-27
June 2007
TCH Pre-emption
Overview
When using eMLPP, emergency calls may possibly be is identied as no longer having the highest priority
within the BSS. in this situation it is possible that an emergency call could be pre-empted by a higher
priority call, requesting a high priority service. For example, in an emergency situation it may be difcult
for emergency services to communicate with each other because of congestion caused by emergency
calls. To guarantee access for these higher priority groups the eMLPP features will track resources within
the BSC using the MSC dened priority and using the pre-emption capability and vulnerability dened
by the MSC.
There are a number of situations when pre-emption may occur for a MS on a TCH as shown below.
TCH Pre-emption during Initial Establishment
TCHPre-emption during Initial Establishment (prior to receiving the ASSIGNMENT REQUEST) is applied
to avoid the queuing of the emergency call while the pre-empted resource is released.
When performing TCH Pre-emption during Initial Establishment, the BSS must make assumptions
about the priority level, pre-emption capabilities and vulnerabilities of the incoming emergency call. The
BSS assumes that the emergency call has the highest priority (lowest priority level), the PCI allows
pre-emption and the PVI does not allow the emergency call to be pre-empted.
If the eMLPP feature is enabled, the emergency call pre-emption must be enhanced to take into
account the pre-emption vulnerability of such calls when searching for a call to pre-empt. However the
assumptions made concerning priority level, PCI and PVI will continue to be applied.
TCH Pre-emption during other phases
TCH pre-emption may also be triggered during other phases of a call. These are listed below
ASSIGNMENT REQUEST
HANDOVER REQUEST
IMPERATIVE INTRA-BSS INTER-CELL HANDOVER
The BSS shall perform pre-emption based upon the data dened in the ASSIGNMENT REQUEST, or
HANDOVER REQUEST from the MSC. The pre-emption mechanism is triggered when no resource can
be found to satisfy the requirements of the incoming call and the incoming call has pre-emption capability.
The TCH pre-emption mechanism can be triggered with and without queuing. If pre-emption is triggered
with queuing the pre-empted resource is allocated to the highest priority call in the queue when it
becomes idle. This may or may not be the call which originally pre-empted the resource being released.
If pre-emption is triggered without queuing, the pre-empted resource when becomes idle it is allocated
to the call which triggered pre-emption. If there are any higher priority calls within the queue then they
will not be allocated to the pre-empted resource, while the pre-empting call still exists.
2006 Motorola, Inc.
June 2007
TCH Pre- emption during Initial Establishment
Assignment request
Handover request
Imperati ve intra-BSS inter-cell handover
2006 Motorola, Inc.
4-29
June 2007
Emergency Call Pre-emption
Overview
The emergency call pre-emption feature, if enabled, will allow a BSS to provide access for an emergency
call on a particular cell regardless of other calls in progress. The emergency call is identied in the
Channel Request with a specied cause value of 101, and upon receipt of this cause value the BSS will
make an attempts to assign a channel. If no idle channels are available when the emergency request is
received at the BSS, then the BSS will dislodge a currently active call on the cell in order to make room
for the emergency request.
When deciding which call to dislodge, the system will assume the following with reference to the
emergency call:
The priority of the emergency call is the highest
The pre-emption capability of the call is allowed (PCI)
The pre-emption vulnerability is disabled. (PVI)
In addition the pre-emption vulnerability of calls will also be considered when looking for a call to pre-empt,
however this action will only take place in the case that eMLPP is enabled.
For the purposes of half rate call pre-emption, a dual occupancy half-rate trafc timeslot will be regarded
as having the highest priority. Therefore a single occupancy trafc channel would be pe-empted rst,
followed by a full rate trafc channel and then a dual-occupancy half-rate trafc channel. This condition
will apply for both AMR/GSM half rate and in addition there is no priority between AMR half rate and
GSM half rate calls. Emergency calls in progress will not be pre-empted by other emergency requests.
The emergency call pre-emption feature is enabled and disabled by the setting of option_peempt.
Immediate assignment of an emergency channel request to a TCH shall occur in all cases so long as
there are TCHs available and the threshold of TCH assignment has not been met.
The following are example scenarios to clarify the processing of an emergency channel request in respect
to resource allocation and must take into account the threshold set by tch_usage_threshold:
Example 1 TCH Available for immediate assignment
Request is assigned TCH, call set-up signalling completed, emergency call in progress.
Example 2 No TCH Available, SDCCH Available
SDCCH allocated for call set-up, BSS initiates the release of a low priority call. When the BSS
receives the assignment request for the emergency call the BSS queues the request and waits for the
released channel to become available. Emergency call queuing is independent of normal call queuing
(queue_management_information) and MSC decision, providing that eMLPP is not enabled. The
position in the emergency queue is then dependent upon age and not priority. If eMLPP is enabled then
emergency calls are queued in the same way as non emergency calls, ie priority and age.
Example 3 No TCH Available, No SDCCH Available
The emergency channel request is answered by an immediate assignment reject message. A low priority
call is dislodged to free resources for when the MS retries.
The channel freed by this dislodging is not available to ordinary queued calls. The channel is placed in
a reserved list for emergency calls for a period of time emerg_reserved (crm_timer_value, 8). After
this timer expires the channel will be made available to ordinary assignment requests.
2006 Motorola, Inc.
June 2007
RACH
Immediate Assignment
Assignment Command
RACH
Immediate Assignment
Assignment Command
RACH
Immediate Assignment Reject
RACH
RRSM
Example 3
Example 2
Example 1
MS is allocated direct
to a TCH so the
Emergency call can
proceed
During this time
another dedicated MS
is dropped from a
TCH so the
Emergency call can
proceed
During this time
another dedicated MS
is dropped from a
TCH so the
Emergency call can
proceed
Wait
indication
period
MS
2006 Motorola, Inc.
4-31
June 2007
ATER Pre-emption
Overview
When the BSS is operating in EAC mode, the number of Ater resources available per RXCDR to the BSS
may be less than the maximum number of CICs that are supported by that RXCDR-BSS combination.
In a congestion scenario, it is possible that Ater resources for a RXCDR will be exhausted. This could
be due to incorrect provisioning of Ater resources, or a change in the network penetration of MS with
restricted capabilities (i.e. FR only), or a failure of an E1 link between the RXCDR and BSC. Pre-emption
of ater resources may occur during the following phases to guarantee allocation of an Ater resource to a
high priority call when in such an Ater congestion scenario:
Ater pre-emption on initial connection
Ater pre-emption on Intra-BSS Inter-Cell Handover
Ater Pre-emption upon Ater Switchover
Ater Pre-emption if EAC idle CIC blocking threshold reached
If the BSS is being operated in AC mode, there is a one-to-one relationship between the CIC and Ater
resources. Therefore such a congestion scenario can only occur when there is a reduction in the number
of Ater resources for a RXCDR due to E1 failure. During E1 failure, pre-emption can be triggered to
guarantee allocation of an Ater resource to a high priority call in an Ater switchover scenario.
This type of pre-emption will be enabled when the eMLPP feature is enabled (irrespective of whether ECP
is enabled). When the eMLPP feature is disabled this type of pre-emption will emulate the pre-GSR8
behaviour (i.e. only when ECP is enabled only for emergency calls).
Ater pre-emption on Intra-BSS Inter-Cell Handover
This type of pre-emption will be enabled when the eMLPP feature is enabled.
Ater Pre-emption upon Ater Switchover
When an E1 link between a RXCDR and BSS fails it may be supporting Ater resources containing active
calls. To maintain voice continuity of the active calls the BSS shall perform Ater switchover procedures.
The Ater switchover procedure involves allocating alternative Ater resources for the active calls upon the
failing 2.048 Mbps link. This procedure is time critical, the calling and called parties of the active calls will
be experiencing loss of voice during the switchover. Any large delays will produce a larger audio hole and
perhaps lead to dropped calls due to the calling or called parties of the active calls terminating the call due
to perceiving the audio hole. The number of resources to be allocated upon Ater switchover can be large
(maximum 248 HR calls on 8kbps Aters). If there are not enough idle Ater resources available the BSS
can initiate pre-emption for calls that qualify. Prior to GSR7, pre-emption is only triggered for emergency
calls when the ECP feature is enabled. When the eMLPP feature is disabled and ECP enabled, the Ater
pre-emption mechanism shall operate as it did previously in GSR7. When the eMLPP feature is enabled
(irrespective of the enable status of the ECP feature), the pre-emption mechanism can be triggered by
any call with pre-emption capability dened by the MSC. As the volume of calls to trigger pre-emption
in this failure scenario could be a maximum of 248 in worst case scenario, although limits will be placed
within the BSS to provide a balance between call integrity and performance.
Ater Pre-emption if EAC idle CIC blocking threshold reached
This type of pre-emption will occur if the threshold to block idle Aters, cic_block_thresh is breached
2006 Motorola, Inc.
June 2007
Ater pre-emption on Intra-BSS Inter-Cell handover
Ater
pre-emption upon Ater switchover
Ater pre-emption if EAC idle CIC blocking
threshold reached
2006 Motorola, Inc.
4-33
June 2007
Precedence Queuing
The BSS allows an incoming call to be queued if no resources are available for it immediately and the
call indicates that queuing is allowed (qa=1) and queuing is enabled within the BSS. The calls are stored
within the queues ranked according to priority and within each priority level the queued requests are
ordered by age.
When the eMLPP feature is enabled, resources will be queued according to the priority dened by the
MSC. Therefore an emergency call is allocated a priority level by the MSC, this priority level may not
be of the highest priority. It is thus possible that a call of a higher priority than an emergency call could
reside in the queue and be assigned to a resource becoming idle.
When the eMLPP feature is disabled the BSS will emulate pre-GSR8 behaviour in that the BSS considers
emergency calls to have the highest priority and therefore will allocate an emergency call to a TCH
resource becoming idle prior to allocating the TCH becoming idle to a non-emergency call. Emergency
calls are considered to all have the same priority, and so the queue is not ordered by priority, but on age,
oldest emergency call at the top of the list. .
There are two queues available within the BSS, an external queue and an internal queue. While the
external queue is only available if allowed by the MSC and BSS, the internal queue is always available.
If a call is queued in the external queue due to no resources being available and pre-emption is allowed,
both queues will be taken into account when looking for a call to pre-empt.
2006 Motorola, Inc.
June 2007
mail
Master
Return
call
Smail
eMLPP enabled
mail
Master
Return
call
Smail
mail
Master
Return
call
Smail
eMLPP not enabled
Priority 1
12:00:01
Priority 7
12:00:08
Priority 7
12:00:07
Priority 4
12:00:02
Priority 3
12:00:03
Priority 1
12:00:08
Priority 1
12:00:12
Priority 1
12:00:09
CS CS CS CS CS CS CS
mail
Master
Return
call
Smail
mail
Master
Return
call
Smail
Priority 1
12:00:01
Priority 4
12:00:02
2006 Motorola, Inc.
4-35
June 2007
There are two other areas of optional functionality that may be controlled by the operator. these are:
Normally a, PDTCH can be stolen by any Circuit Switched call of any priority. However, when the eMLPP
feature is enabled, the BSS will allow the customer to assign a priority level to the switchable PDTCH (via
per BSS database element sw_pdtch_priority). This will prevent Circuit Switched calls with equal
or lower priority to the PDTCH from stealing the PDTCH resource. This functionality can be disabled by
the customer.
Within the BSSthere are a number of mechanisms which exempt emergency calls frombeing considered,
e.g. Congestion mechanisms, Multi-band Handover etc. If the eMLPP feature is enabled the customer
will be able to specify a priority level threshold. Any call with an equal or higher priority than this operator
dened priority level threshold will be exempted from certain BSS mechanisms. The operator may dene
this threshold by the parameter emergency_group_priorityThis allows the BSS to provide a better
QoS for these high priority calls by not performing any non-essential mechanisms. Examples of these
mechanisms are shown below;
Standard Congestion Handovers
FR-HR Congestion Handovers
Multi-band Handover upon assignment
Direct assignment to the secondary band of a Dual Band Cell
2006 Motorola, Inc.
June 2007
sw_pdtch_priority <*>
* 1 14
Default = 14
emergency_group_priority <*>
* 0 14
Default = 0
0 = no calls exempt
14 = all calls considered
2006 Motorola, Inc.
4-37
June 2007
Version 1 Rev 3 Multiple Encryption Algorithms
Multiple Encryption Algorithms
Overview
Multiple encryption algorithms can be loaded into the BSS via the software download. During
conguration of the BSC the CA informs the SSM of the encryption algorithms supported by the BSS
software. Purchasable algorithms include A5/0 (Null encryption), A5/1 (Full encryption) and A5/2
(Prime). When the MSC sends the "Cipher mode command" or "Handover Request", the message may
include just one or a number of permitted algorithms. The SSM will then, if given a number of permitted
algorithms, decide which algorithms are to be used upon the following criteria:
Capability of the MS as indicated by the classmark.
Permitted algorithms supplied by the MSC.
Algorithms purchased by the operator (stored in the GSM database).
Algorithms supported by the DRIM Firmware.
Operator prioritized list of algorithms (stored in the CM database).
If no algorithms meet the above criteria the SSM sends the appropriate failure message, if the BSS
selects the encryption algorithm from the set of more than one supplied by the MSC the SSM includes
the chosen algorithm in the "Cipher mode complete" or "Handover Request Acknowledge" message to
the MSC.
The individual algorithms (1-7) can be used independently from the multiple encryption option. i.e. a
customer may purchase just A5-1, therefore, the requirement for multiple encryption priority is removed.
Multiple A5 Encryption algorithm versions can be purchased by the operator, but cannot be used unless
they have been enabled by the change element option_alg_a5 command and prioritized by the
chg_a5_alg_pr database command. The order in which they are entered prioritizes their use. The
encryption algorithms are prioritized on a per BSS basis and only those prioritized can be used, if no
algorithms are prioritized then "no encryption" is the default.
2006 Motorola, Inc.
June 2007
Multiple Encryption Algorithms Version 1 Rev 3
Multiple Encryption Algorithms
Ho Resource Allocation
Cipher mode control
MS BSS MSC MS BSS MSC
Ho request
Ho request Ack
Ho complete
Ho complete
Cipher mode cmd
Cipher mode cmd
Cipher mode complete
Cipher mode complete
chg_element option_alg_a5_* <**><0 or bsc>
* 1-7
** 0-disabled
1-enabled
chg_a5_alg_pr <1st ALG>[<2nd ALG>....<8th ALG>]
(If multiple encryption algorithm is purchased and the
operator is using more than one algorithm)
Parameter Description Values
1st ALG Algorithm with highest
priority
0= no encryption
1= A5/1 2= A5/2
3= A5/3 4= A5/4
5= A5/5 6= A5/6
7= A5/7 Default =0
2nd ALG through
8th ALG
Algorithms with
successively less priority
Same as above
2006 Motorola, Inc.
4-39
June 2007
Version 1 Rev 3 Circuit Error Rate Monitor (CERM)
Circuit Error Rate Monitor (CERM)
Overview
The CERM feature provides the ability to identify a discontinuity in a trafc circuit path through the GSM
network from RXCDR to BTS. The path can be divided into two parts, namely the CIC (RXCDR to BSS)
and the radio channel identier (RCI, BSS to BTS). The link between these is the Switch Manager (SM).
The channel coders at the DRI and the XCDR/GDP monitor TRAU frames, i.e. the 3 kbit/s added on
to the 13 kbit/s of speech after transcoding and can detect when a valid TRAU frame is not detected.
When this happens, an error is reported to the SM (via FCP and FTP), which maintains a count of all
such errors associated with the CIC and RCI involved with the call. If this counter reaches a pre-set level
an alarm is raised.
TRAU frame error can be detected in 3 ways:
Initial TRAU errors, where the channel coder is activated and expects to receive the rst TRAU
frame within a certain period (initial_sync_timer). If a TRAU frame is not received within this
period, an error indication is sent to FCP.
Downlink TRAUerrors where, after receiving the rst TRAUframe, the DRIs channel coder monitors
TRAU frame synchronisation. If it loses synchronisation for more than downlink_sync_timer,
an error indication is sent to FCP.
Uplink TRAU errors, which are detected by the XCDR/GDPs channel when an uplink TRAU is not
detected. An alarm pattern is sent in the downlink TRAU, to be detected by the radios channel
coder. If this pattern exists for the period of uplink_sync_timer the radios channel coder sends
an error indication to FCP.
CERM errors for AMR and GSM half rate using 8Kbps switching, will count as one 16Kbps error even
thought the channel is made up of 2 x 8Kbps sub timeslots.
2006 Motorola, Inc.
June 2007
Circuit Error Rate Monitor (CERM) Version 1 Rev 3
FCP
CC
SM FTP
CC
initial_sync_timer
downlink_sync_timer
uplink_sync_timer
FCP
CC
SM FTP
CC
Initial or Downlink Problem Uplink Problem
"Missed
Trau"
"Missed
Trau"
RXCDR
BTS
BSS
2006 Motorola, Inc.
4-41
June 2007
Version 1 Rev 3 Circuit Error Rate Monitor (CERM)
When a TRAU error is detected in a call, the error counters for both the CIC and the RCI involved
are incremented by cic_error_increment and rci_error_increment respectively, at the SM,
because it is the SMs job to join the CIC and the RCI together. If the counters reach or exceed
cic_error_gen_threshold or rci_gen_threshold respectively and alarm is generated.
Whenever a call is made, maintained and completed on a CIC/RCI combination with no TRAU
frame errors detected, the counters are decremented by predened steps. If the counters fall below
cic_error_clr_threshold or rci_error_clr_threshold respectively the alarms previously
raised are cleared.
It is important to understand that the BSS software cannot distinguish between a CIC problem and an
RCI problem in one particular call; when a TRAU error is detected both counters are incremented as
above. However, probability says that the same CIC/RCI combination will not be used for subsequent
calls, so the CIC and RCI counters will be incremented and decremented independently over a period of
time. Also, due to handovers, it is possible that a single call could use several different RCIs and more
than one CIC during its course; the denition of call completion used to decrement the counters is that
the CIC or RCI is no longer required, which could be due to termination or handover.
2006 Motorola, Inc.
June 2007
Circuit Error Rate Monitor (CERM) Version 1 Rev 3
Timers at the BTS only
initial_sync timer 1500 - 7000 ms
downlink_sync_timer
uplink_sync_timer
Increment/decrement at the BSS
cic_error_increment 0 - 255
rci_error_increment (0 disables CERM)
Alarm generation at the BSS
cic_error_gen_threshold
rci_error_gen_threshold
Alarm clearing at the BSS
cic_error_clr_threshold
rci_error_clr_threshold
All set by chg_element <parameter><*><site>
1000 - 3000 ms
2 - 255
0 - 253
2006 Motorola, Inc.
4-43
June 2007
Version 1 Rev 3 Enhanced Circuit Error Rate Monitor (ECERM)
Enhanced Circuit Error Rate Monitor (ECERM)
Restricted feature
The enhancement to the CERM feature allows more points along the circuit path to be monitored. 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 points along the circuit path that are monitored are the CIC, ACI, PIC, RCI and
GCI.
CIC (Circuit Identity Code) - A timeslot on the link between the RXCDR or BSS and MSC.
ACI (Ater Identity Code) - A timeslot on the link between the RXCDR and the BSS.
GCI (GPRS Circuit Identier) - A timeslot on the link between BSS and PCU.
RCI (Radio Channel Identier) - Radio hardware dene by timeslot and frequency. This will also include
radios which have been congured for half-rate use.
PIC (Path Identity Code) - A timeslot on the link between BSS and BTS. The PIC is a special case
because it is measured from BSS to site basis. So for instance a path leading from a BSS to two daisy
chained BTS's, the later BTS's PIC will encompass the path through the rst BTS to the BSS. This will
also include radios which have been congured for half-rate use.
Operation
The ECERM monitors the continuity of circuits for both circuit switched and GPRS circuits.
Circuit Switched - Done on a per call basis, whenever a discontinuity is detected ("Error Indication -
Sync loss" received during a call) for a circuit during a circuit switched call, error counts are updated for
the RCI, PIC, ACI and CIC involved in that connection. If the error count threshold has been exceeded,
the error count will be reset to the error count threshold value. If the call completes without any TRAU
frame sync errors occurring during the call, the error counts for the resources involved in the call will
be decremented. In the case of handover to a new resource the old resource will be decremented if no
TRAUframe sync errors had occurred while the old resource was in use. Error counts never decremented
below zero.
GPRS Circuits - Monitoring occurs over a designated period of time. When a discontinuity is detected
("Error Indication - Sync loss" received during a call) on a GPRS circuit, error counts are updated for
the RCI, PIC(s) and GCI(s) involved in the connection. If the specied period of time passes without a
TRAU frame sync error occurring, the GPRS resources being used in the circuit will be decremented. If
a GPRS circuit is transferred to a circuit switched call, the resources that were used in the GPRS circuit
will be decremented if no errors occur in the specied time.
When an error count on a particular resource reaches or exceeds an operator specied threshold and
there is not already an alarm on that resource, an alarm is generated. The alarm contains information
pertaining to the resource, thus allowing the operator to identify potentially faulty devices. For both
circuit-switched and GPRS calls, if the error count decreases below a specied threshold and there is
an alarm for the resource, a clear alarm for the resource will be sent to the MMI and OMC-R.
The resources monitored by ECERM feature varies depending on the conguration of the BSS. When
local transcoding is being used, the ACI resource is not monitored and additional timeslot information is
displayed with the CIC resource. If BC mode is used ACI and CIC alarms are generated in pairs.
Error count will only be decremented for applicable CIC and ACI for a circuit only call transfer; it will only
be decremented for the RCI and PIC for a radio channel only call transfer; it will be decremented for CIC,
ACI, PIC and RCI for a circuit and radio channel call transfer.
2006 Motorola, Inc.
June 2007
Enhanced Circuit Error Rate Monitor (ECERM) Version 1 Rev 3
Enhanced Circuit Error Rate Monitor (ECERM)
GDP GDP GDP

MSC
MSI MSI
KSW
MSI MSI
MSI MSI
KSW
MSI MSI
CCU CCU
KSW
MS1 MS2
CICs
ACI
PIC
RCI RCI
PMC
PMC
PICP
Gb Interface
PMC PMC
PMC
PICP
PRP
KSW
KSW
MS1 MS2
GCI
PIC
RCI RCI
MSI MSI
MSI MSI
MSI
MSI
CCU CCU
SGSN
GDP
MSC
CICs
OMCR
NMC
RXCDR
BSS
BTS
PCU
BSS
BTS
2006 Motorola, Inc.
4-45
June 2007
Version 1 Rev 3 ECERM Parameters
ECERM Parameters
Timers at the BTS
These parameters are available to the operator depending on whether the ECERMfeature is unrestricted
or in some cases when the GPRS feature is unrestricted. In the rst instance the operation of the feature
is under the control of four timers and is the period of time that the BTS expects to see a TRAU frame.
initial_sync_timer
downlink_sync_timer
uplink_sync_timer
static_sync_timer(GPRS restricted timer)
The initial_sync_timer is set to a higher value than the rest due to the rst TRAU frame is always
uplink and this timer is allowing for the rst downlink TRAU. Once this has happened uplink and downlink
TRAU frames are monitored in the same way as the standard CERM feature. In the case of GPRS, the
static_sync_timer is used to detect TRAU frames.
In addition to the standard CERM feature parameters for error increments, alarm generation and alarm
clearance for ACI and PIC, with GCI and alarm time for GPRS.
Increments at the BSS
aci_error_inc
This identies the value by which the error count is incremented if an error indication is received for a
ACI during a call.
pic_error_inc
PIC during a call.
gci_error_inc
GCI during a GPRS alarm increment time period.
Alarm Generation at the BSS
aci_error_gen_thresh
This identies the value which the error count must be equal to or greater than for an alarm to be
generated for an ACI.
pic_error_gen_thresh
generated for a PIC.
gci_error_gen_thresh
generated for a GCI.
2006 Motorola, Inc.
June 2007
ECERM Parameters Version 1 Rev 3
ECERM Parameters
Timers at BTS
initial_sync_timer 1500 - 7000ms
downlink_sync_timer 1000 - 3000ms
uplink_sync_timer
static_sync_timer
Increment at the BSS
aci_error_inc 0 255
pic_error_inc
gci_error_inc
Alarm generation at the BSS
aci_error_gen_thresh 0 253
pic_error_gen_thresh
gci_error_gen_thresh
1000 - 3000ms
1000 - 3000ms
0 255
0 255
0 253
0 253
2006 Motorola, Inc.
4-47
June 2007
Version 1 Rev 3 ECERM Parameters
ECERM Parameters
Alarm Clearing at the BSS
aci_error_clr_thresh
This identies the value for which the error count must be equal or less than for an alarm to be cleared
for an ACI.
pic_error_clr_thresh
for a PIC.
gci_error_clr_thresh
for a GCI.
Note: At least two calls are required on a resource before an alarm can be cleared. This is to ensure
a valid alarm clearance. Modifying the value below the current count will not cause an alarm but will
happen on the next error.
GPRS Monitoring Period
gprs_alarm_time
This identies the time period in which error counts are incremented if an error indication is received for
a GCI or decremented if no error indication is received.
AMR/GSM Half Rate
ECERM errors for AMR and GSM half rate using 8Kbps switching, will count as one 16Kbps error even
thought the channel is made up of 2 x 8Kbps sub timeslots. This will apply to all errors generated by the
CIC, AIC, PCI and RCI.
2006 Motorola, Inc.
June 2007
ECERM Parameters Version 1 Rev 3
ECERM Parameters
Alarm clearing at the BSS
aci_error_clr_thresh 0 253
pic_error_clr_thresh
gci_error_clr_thresh
GPRS monitoring period
gprs_alarm_time 0, 5 - 240s
0
253
0 253
2006 Motorola, Inc.
4-49
June 2007
Version 1 Rev 3 Short Message Service Options
Short Message Service Options
Overview
The Short Message Service is specied by GSM and can be divided into two functions: Cell Broadcast
and Point-to-Point. There are a number of database parameters which control the use of Short Message
Service.
Cell Broadcast
The GSM-dened Cell Broadcast feature is a means of unilaterally transmitting data to mobiles on a
per-cell basis, by use of the Cell Broadcast channel. A BSS can be connected to a Cell Broadcast
Centre (CBC), which is responsible for downloading cell broadcast messages to the BSS, together with
dening repetition rate, and the number of broadcasts required per message. The CBC will also dene
whether messages are to be single or multiple page, and the length of the DRX period. The CBC will also
dene the category of messages: Normal, Background or High Priority. The BSS is then responsible for
transmitting these updates to the BTS's affected, which will ensure that the message is transmitted as
requested.
If this option is purchased and enabled, frequency, slot, and subslot information present within BCCH
system information will cause suitably equipped mobiles to monitor the Cell Broadcast Channel (CBCH).
This channel, when enabled, ts into the 102 frame multiframe in place of SDCCH subslot 2 on an
SDCCH/4, and on the SDCCH subslot number pointed to by bs_ag_blks_res for an SDCCH/8. It can
appear on BCCH or Non-BCCH carriers on timeslots 0-3 inclusive. Only one CBCH will exist within a cell
and an algorithm specied in GSM 05.02 will control its whereabouts. A cell broadcast block is made up
of 23 bytes (184 bits) which is encoded to produce the familiar 456 bit block, this is then transmitted over
four successive air interface bursts. In a period of 8 multiframes the CBCH will only be transmitted on 4
of them. In the case where the the CBCH resides on a BCCH carrier dummy bursts will be transmitted
in the other 4 multiframes.
The SMS Cell Broadcast service is designed to minimise the battery usage requirements for an MS. If the
SMSCBDRX GSMrequirement is supported, every 1 minute the cell will broadcast a scheduled message
on the cell broadcast channel. The MS will use this information to restrict reception of those messages
the customer is not interested in receiving, perhaps because of language or information choice. The MS
user may choose the information he requires through the channel number selection which is a feature on
certain MS mobiles. SMSCB scheduled messages are detailed in GSM 04.12. SMSCB is a purchasable
feature which is enabled on a cell basis using the following database command:
chg_element cbch_enabled <*> <location> cell_number=<cell_id>
* 0 disabled
1 enabled
At BTS only.
2006 Motorola, Inc.
June 2007
Short Message Service Options Version 1 Rev 3
Short Message Service Options
0
10
20
30
40
50
DOWNLINK
A3
A2
A1
A0
D7
D6
D5
D4
D0
D1
CBCH
D3
A7
A6
A5
A4
D7
D6
D5
D4
D0
D1
CBCH
D3
0
10
20
30
40
50
DOWNLINK
A1
A0
D3
D1
D0
C
B
C
C
A3
A2
D3
D1
D0
C
B
C
C
Combined Multiframe DCCH Multiframe
CBCHCBCH
0 1 2 3 4 5 6 7 0 1 5 4 3 2
. . . . . . .
7 6
51 frame multiframes
4 Successive
Bursts
CBCH 23 Bytes 23 Bytes 23 Bytes 23 Bytes
Dummy Bursts (BCCH ONL Y)
2006 Motorola, Inc.
4-51
June 2007
Version 1 Rev 3 Multiple Background Messages
Multiple Background Messages
Overview
Cell Broadcast background messages can be a maximumof 93 characters and will be sent on the SMSCB
channel in the absence of messages originating from the Cell Broadcast Center (CBC). A maximum of
four background messages can be specied using the following database commands:
chg_smscb_msg <msg_num> <msg_id> <gs> <msg_code> <update_number>
<language>cell_number= <cell id>
msg_num (0-3)
This number is not sent to the MS, but is used as a message identier within the Motorola BSS software.
msg_id (0-65535)
Identies the logical channel used within the physical CBSMS slot. This corresponds to the "channel
number" entered in the MMI of the MS.
gs (0-3)
This eld indicates to the MS the geographical area over which the message code is unique. It also
indicates the display mode to the mobile.
0 - Immediate, Cell Wide
1 - Normal, PLMN Wide
2 - Normal, Location Area (LAC) Wide
3 - Normal, Cell Wide
msg_code (0-1023)
This eld is used by the MS to differentiate between different messages being broadcast using the same
msg_id.
update_number
(0-15) indicates that an existing message has been updated. The MS usually does not read the same
message twice, but if an update has occurred this eld causes the MS to decode the message.
language (0-255)
This eld species the alphabet/coding scheme being used in the message. Values specied in W23.
(English= 1)
cell_desc
This prompt species the cell identity for the cell being modied
2006 Motorola, Inc.
June 2007
Multiple Background Messages Version 1 Rev 3
Multiple Background Messages
chg_smscb_msg <msg_number><msg_id><gs><msg_code>
<update_number><language>cell_number = <cell_id>
Enter text string here
2006 Motorola, Inc.
4-53
June 2007
Version 1 Rev 3 Point to Point SMS Options
Point to Point SMS Options
Overview
Point to Point SMS provides a means of sending messages of limited size (255 message bytes) to and
from GSM mobiles. The ability to provide SMS requires a Service Centre which acts as a store and
forward for short messages. To allow for SMS transfer, the mobile station and BSS must set up the
appropriate air interface protocol (LAPD). The logical channel used for this data transfer will depend on
the status of the mobile:
Mobile idle - SDCCH used
Mobile on SDCCH - SDCCH used
Mobile busy - SACCH or FACCH used (applies to all types of trafc channels)
The ability to enable/disable mobile originated/terminated SMS is also available.
change_element sms_dl_allowed
change_element sms_ul_allowed
2006 Motorola, Inc.
June 2007
Point to Point SMS Options Version 1 Rev 3
Point to Point SMS Options
change_element sms_dl_allowed<*><site number>
change_element sms_ul_allowed<*><site number>
* 0 disable
1 enable
2006 Motorola, Inc.
4-55
June 2007
Version 1 Rev 3 Trafc Channel SMS
Trafc Channel SMS
Overview
Whilst engaged on a trafc channel of any type, the mobile can still receive SMS via FACCH or the
SACCH. If the FACCH is chosen as the means of delivery then an SMS block (23 octets of information)
can be transmitted in 8 successive TDMA frames. Due to the timing constraints of the SACCH, an SMS
block can be delivered in 104 frames if this method of delivery is used. The disadvantage of FACCH is
that trafc frames are stolen, with injurious effect on the audio quality, this frame stealing would become
more noticeable as the size of the short message increase.
2006 Motorola, Inc.
June 2007
Trafc Channel SMS Version 1 Rev 3
Trafc Channel SMS
chg_element sms_tch_chan<*><site number>
* 0 = via BSS decision
1 = FACCH always used
2 = SACCH always used
2006 Motorola, Inc.
4-57
June 2007
Version 1 Rev 3 AGCH ow control
AGCH ow control
Description
The _cell_data,20 parameter indicates whether the functionality of the AGCH ow control is enabled.
The parameter also indicates the triggers associated with IA or IAR that can trigger AGCH overload.
This parameter may be changed inside and outside of SYSGEN mode without warning.
Table 4-1
BSS parameter name Description Values
_cell_data,19 Enables or disables AGCH
ow control.
0 AGCH ow control function
is disabled.
is enabled, any one of the
triggers associated with IA
and IAR can trigger AGCH
overload.
is enabled, while only the
trigger associated with IA can
trigger AGCH overload.
Default value 1
2006 Motorola, Inc.
June 2007
AGCH ow control Version 1 Rev 3
AGCH ow control
Flow Control Procedure
Values
Value type Integer
Valid range 0 to 2
0 AGCH fow control function is disabled.
1 AGCH fow control function is enabled, any one
of the triggers associated with IA and IAR can
trigger AGCH overload.
2 AGCH fow control function is enabled, while only
the trigger associated with IA can trigger AGCH
overload.
Default value 1
_cell_data, 20
2006 Motorola, Inc.
4-59
June 2007
Version 1 Rev 3 The Flow Control Procedure
The Flow Control Procedure
The ow control procedure can follow four different scenarios
Overload at the RSS due to RACH/AGCH
Normal and critical overload at the CRM
Normal and critical overload at the SSM
Overload at the MSC
These four scenarios can occur simultaneously. However they all use barring and unbarring of access
classes and modication of database parameters max_retran and tx_integer as a means of
reducing trafc and hence reducing the load within the system. These procedures are initiated within
the BTS, so the CRM uses timers T1 (flow_control_t1) and T2 (flow_control_t2) to control
barring and unbarring of access classes (dened in TS GSM 8.58). In the case of MSC overload T1
and T2 timers are used again to replace timers T17 and T18 (dened in TS GSM 8.08).
Access Class Barring
Flow control is initiated by receipt of an overload message to the CRM. The types of overload message
are:
rss_overload (overload at the RSS due to RACH/AGCH)
overload_onset (CRM, SSM and MSC overload conditions)
When an overload message is received both timers T1 and T2 are started; the rst access class is barred
and the cell alarm is raised. The decision of which access class is to be barred rst is decided at random
by CP and further access classes are barred on a cyclic basis, low to high. If another overload message
arrives at the CRM before T1 expires it is ignored, with the exception of an overload_onset message
with the cause value critical_overload. In this case the cause is saved. If an overload message
arrives at the CRM after T1 expires, but before T2 expires, another access class is barred and both
timers are restarted. The overload_onset message with critical_overload cause value is given
higher precedence to bar two access classes.
If timer T2 expires without additional overload indications, the CRM is instructed to bring one access
class back into service and timer T2 is restarted. This continues until all the active access classes are
in service. When all the active access classes of a cell in the CRM are back in service, the ow control
procedure for that cell is ended. The access classes barred by the operator are not considered for
barring/unbarring of ow control procedure. The alarm generated due to ow control procedure would
be cleared when conditions that triggered it are removed.
2006 Motorola, Inc.
June 2007
The Flow Control Procedure Version 1 Rev 3
Overload at the RSS due to RACH/AGCH
Normal and critical overload at the CRM
Normal and critical overload at the SSM
Overload at the MSC
2006 Motorola, Inc.
4-61
June 2007
Version 1 Rev 3 The Flow Control Procedure
max_retran and tx_integer
max_retran indicates the number of RACHs that a mobile station sends for any one-call set up
attempt. In a congested system it is advantageous to have the MS sending as few RACHs as
possible. tx_integer affects the spread of RACHs over a number of frames. The larger the value of
tx_integer the greater the number of frames over which the RACHs are spread. The ow control
procedure modies the value of tx_integer towards the maximum value of 15, which gives a possible
spread of 50 slots, and max_retran towards its maximum value of 3, which gives a retransmission
number of 7.
Timers T1 and T2 once again govern the gradual manipulation of parameters tx_integer and
max_retran. If an rss_overload message is received from the RRSM timers T1 and T2 are
started, max_retran is decremented by one and tx_integer is incremented by one and the system
information messages are modied. If another rss_overload message is received whilst T1 is
running, then no modication of tx_integer or max_retran occurs. If a rss_overload message is
received after T1 has expired but before T2 has expired, the ow control procedure checks the value of
tx_int_max_ret_ind in the CRM and takes the following actions:
If tx_int_max_ret_ind is set to 0 then add 1 to the value of tx_integer. The value
of tx_int_max_ret_ind is then set to 1, indicating that the next time round the value of
max_retran is modied.
If the value of tx_int_max_ret_ind is set to 1 then 1 is subtracted from the value of
max_retran. The value of tx_int_max_ret_ind is then set to 0.
If timer T2 expires without additional overload indications, the CRM gradually reverts the
values of tx_integer and max_retran to those stored in the CM database. The value of
tx_int_max_ret_ind is checked, to see if tx_integer or max_retran needs to be adjusted. The
value of tx_int_max_ret_ind is then set to allow the value of the other parameter to be adjusted. If
the values of both parameters are not those stored in the CM database, T2 is restarted until they are.
2006 Motorola, Inc.
June 2007
The Flow Control Procedure Version 1 Rev 3
t1
t2
Access
Class
Barred
Overload
indication
ignored
Access
Class
Barred
Access Class
Un
-
Barred
Access Class
Un-Barred
Overload
messages
Overload
message
t1
t2
t2
When an access class is barred or unbarred
tx_integer and max_retran are modified
chg_element flow_control_t1 <value> <location> cell=cell_ desc
chg_element flow_control_t2 <value> <location> cell=cell_ desc
Def = 20000
Def = 30000
Value = 0 - 100000
2006 Motorola, Inc.
4-63
June 2007
Version 1 Rev 3 RSS Flow Control
RSS Flow Control
A site may be congured for one to four CCCH timeslots (indicated by ccch_conf). The CCCH load is
determined on a per timeslot basis.
Uplink: The RSS_CCCH_Load_Indication is sent after the determination that the uplink CCCH
(RACH) load is in an overload situation.
Downlink: The RSS_Overload message is sent after the determination that the downlink CCCH
(AGCH) load is in an overload situation.
These messages are sent from the Layer1 process to the Abis process, which in turn forwards them onto
the Call Processing RRSM process, which controls ow control.
RACH Non-Overload (Uplink)
When a CCCH timeslot is congured, the RACH_CHECKLOAD_TIMER (calculated from
rach_load_period) is started. At each RACH measurement period completion
(RACH_CHECKLOAD_TIMER expiry), the RACH load is calculated. Layer 1 reads the maximum load
value for a RACH from the RSS database. It then compares the load value stored by the RACH Load
in the Layer 1 database to see if a load situation exists. If there is no overload situation, the RACH
access count and busy count are reset and a new RACH measurement period is started. If an overload
situation does exist, the RACH is considered to be in Overload.
RACH Overload (downlink)
When a RACH overload situation is detected, a RSS_CCCH_LOAD_INDICATION message is sent to the
Abis process with the CCCH Overload cause value. A timer RACH_OVERLOAD_TIMER (calculated from
ccch_load_period) is then set which sends a timeout message back to Layer 1. The CCCH Load
Period allows the Layer 3 processes to handle the RACH overload situation and make adjustments to
reduce the current CCCH Load. At the end of this time, if the RACH overload situation still exists, then
another RSS_CCCH_LOAD_INDICATION message is sent to the Abis process and the timer is restarted.
This is repeated until the RACH load is brought below the RACH overload threshold by the Layer 3
process. If no overload exists, the RACH load changes to the Non-Overload situation and the RACH
measurement period timer is started.
AGCH Non-Overload
Each time an Immediate Assign or Immediate Assign Reject is received by Layer 1, a calculation of the
size of the associated buffer is performed. When a threshold of 4 less than the maximum size of an
AGCH buffer is reached, the AGCH is in overload. The Immediate Assign buffer can store up to 56
immediate assign messages per CCCH timeslot at a particular DRI. The Immediate Assign Reject buffer
can store up to 112 immediate assign reject messages per CCCH timeslot at a particular DRI. If the
AGCH Immediate Assign buffer is full, any additional immediate assign messages received will cause a
delete indication message to be sent. The delete indication will result in an unsuccessful assignment
scenario for the call.
2006 Motorola, Inc.
June 2007
RSS Flow Control Version 1 Rev 3
RSS Flow Control
RSS checks for RACH overload in TDMA blocks.
The number of blocks is set by two database parameters
Non- overload condition
rach_load_period = 1 to 1020 default = 16
Overload condition
ccch_load_period = 1 to 1020 default = 40
1 step = 1 X TDMA multiframe (51 TDMA frames)
2006 Motorola, Inc.
4-65
June 2007
Version 1 Rev 3 RSS Flow Control
RSS Flow Control
AGCH Overload
When a AGCH overload situation is detected, a RSS_CCCH_LOAD_INDICATION message is sent to
the Abis process with the CCCH Overload cause value. A timer RACH_OVERLOAD_TIMER (calculated
fromccch_load_period) is then set which sends a timeout message back to Layer 1. The CCCHLoad
Period allows the Layer 3 processes to handle the AGCH overload situation and make adjustments to
reduce the current CCCH Load. The length of the timer is acquired from the RSS database. At the end
of this time, if the AGCH overload situation still exists, then another RSS_CCCH_LOAD_INDICATION
message is sent to the Abis process and the timer is restarted.
This is repeated until the AGCH load is brought below the RACH overload threshold by the Layer 3
process. If no overload exists, the RACH load changes to the Non-Overload situation and the RACH
measurement period timer is started.
2006 Motorola, Inc.
June 2007
RSS Flow Control Version 1 Rev 3
RSS Flow Control
1 TDMA Multiframe
0.2354s
Example rach_load_period = 4 and ccch_load_period = 6
After 4 TDMA frames L1
calculates if in overload
Overload exists
After 6 TDMA frames L1
calculates if still in
overload
rach_load_period
ccch_load_period
2006 Motorola, Inc.
4-67
June 2007
Version 1 Rev 3 RACH Loading
RACH Loading
There are two different algorithms currently dened for RACH ow control. The RACH load is calculated
as the percentage of RACH accesses that are incorrect. The rst algorithm is a standard, GSM-dened
method of RACHowcontrol is a trafc control approach. The RACHload is calculated as the percentage
of RACH opportunities that successful RACH accesses have been received on. The second algorithm,
is an overload control approach. which will detect sudden high bursts of trafc on the RACH while the
trafc control' approach attempts to limit the RACH load based on the cell conguration and prevent
"overload" from ever occurring. The database parameter, which sets the RACH load algorithm, is:
rach_load_type <value> <location>
value = 0 (standard algorithm)
1 (overload control algorithm)
RACH Load Calculation
The RACH load is calculated when the RACH Measurement Period timer for a RACH timeslot has
been received (RACH_CHECKLOAD_TIMER expires) or the CCCH Load Period timer for a RACH
timeslot has been received (RACH_OVERLOAD_TIMER expires). For customers using the standard
method of RACH ow control, the Correct Access Percentage is calculated and compared to the
rach_load_threshold to determine if the RACH is overloaded.
rach_load_threshold <value> <location>cell=<cell_desc>
value = 0 to 1000 (default = 1000 - disables ow control)
Load_Period
When a RACH overload condition does not exist, the Load_Period is equal to the rach_load_period
(non overload) or ccch_load_period (overload) obtained from the database. The
rach_load_period and ccch_load_period values specify the number of 51 frame TDMA
multiframes between successive calculations of the rach load.
Layer 1 uses the Load_Period to calculate the actual time period over which the measurements will
be taken. The minimum time period over which the RACH load measurement is calculated is 0.2354
seconds for a load period value of 1. The RACH load timeout value is calculated by multiplying the
Load_Period by 0.2354 seconds.
Base_Slot_Count
The Base_Slot_Count for pure RACH (non-combined) is 51 (51 RACH opportunities per multiframe).
The Base_Slot_Count for combined RACH is 27 (27 RACH opportunities per multiframe).
RACH_Slot_ Count
The RACH Slot Count is dened as the total number of RACH timeslots over which a measurement
is performed. The RACH_Slot_Count is calculated as the Load_Period multiplied by the
Base_Slot_Count. If a RACH overload occurs, the RACH_Slot_Count is sent to Call Processing in
the CCCH Load Indication message.
2006 Motorola, Inc.
June 2007
RACH Loading Version 1 Rev 3
RACH Loading
rach_load_type = 0 (Standard) or 1 (Alternative)
rach_load_threshold = 0 to 1000 (def = 1000 which disables flow control)
Base_Slot_Count
51 non-combined
rach_load_period rach_load_period
ccch_load_period ccch_load_period
27 - combined
Meas period = 6x0.2354 =1.4124s Meas period = 4x0.2354 =0.9416s
RACH_Slot_Count = load_period x Base_Slot_Count
From previous example
2006 Motorola, Inc.
4-69
June 2007
Version 1 Rev 3 RACH Loading
RACH Loading
Correct Access Percentage (Standard)
The RACH_Access_Count is divided by the maximum number of RACH accesses possible during the
calculation period. This proportion is multiplied by 1000 to get the load percentage. This percentage can
range from 0 to 1000 since each unit corresponds to one-tenth of one percent. The maximum number
of RACH accesses is equal to the RACH_Slot_Count. The equation is shown below:
2006 Motorola, Inc.
June 2007
RACH Loading Version 1 Rev 3
RACH Loading
Threshold Load Rach
Count Slot RACH
Access RACH
_ _
_ _
1000 * _
>
Number of
RACH
accesses in a
measurement
period
Multiply by 1000 to get
the load %. Each unit
corresponds to one-
tenth of one percent.
Load period
(rach_load_period or
ccch_load_period)
multiplied by
Base_Slot_Count
(either 51 or 27)
Set in database, the valid
range is between 0 and
1000, once access % goes
above this level overload
situation exists
2006 Motorola, Inc.
4-71
June 2007
Version 1 Rev 3 Standard RACH load Calculation
Standard RACH load Calculation
The RACH load is calculated when the RACH Measurement Period timer for a RACH timeslot has been
received (RACH_CHECKLOAD_TIMER expires) or the CCCH Load Period timer for a RACH timeslot
has been received, (RACH_OVERLOAD_TIMER expires). When using the standard method of RACH
ow control, the Correct Access Percentage is calculated and compared to the rach_load_threshold
to determine if the RACH is overloaded.
Example
Site A
Carriers 3
SDCCH 16
TCH 21
ccch_conf = 0 (non-combined 51 multiframe, ccch on timeslot 0 only)
rach_load_period = 16
ccch_load_period = 40
rach_load_type = 0
The total loading for this cell can be worked out by calculating the maximum load on the site, dividing it
by total number of RACH slots that are available for that measurement period.
In this case it would be:
rach_load_threshold = 181 (18.1% overload threshold - set in 1/10th of 1%)
Which means when in overload, the threshold has been set so all resources are being used in the cell if
the ow control is to bar another class i.e. max threshold setting.
At the end of the measurement period (Meas_Period = 16 * 235.5ms = 3.766 sec) the RACH_Access is
calculated and used to see if the RACH is overloaded.
2006 Motorola, Inc.
June 2007
Standard RACH load Calculation Version 1 Rev 3
Site Configuration: 3 carriers, 2 SDCCH timeslots 21 TCH and 16 SDCCH
rach_load_type = 0
ccch_conf = 0
Non-overload condition
51x16
Rach_Slot_Count
Total site resources * 1000 = 37*1000 = 45.34 %
Rach_Slot_Count 51x16
51x40
Rach_Slot_Count
Total site resources * 1000 = 37*1000 = 18.1 %
Rach_Slot_Count 51x40
Overload condition
Meas_Period =3.766s
Meas_Period =9.42s
rach_load_threshold = 181
2006 Motorola, Inc.
4-73
June 2007
Version 1 Rev 3 Standard RACH load Calculation
For example
RACH_Access = 34
When in overload the load_period is calculated from ccch_load_period, which therefore changes
RACH_Slot_Count. Also because an access class has been barred the RACH_Access count will
probably reduced by around 10%.
Meas_Period = 40 * 235.5ms = 9.42 secs
2006 Motorola, Inc.
June 2007
Standard RACH load Calculation Version 1 Rev 3
RACH accesses = 34 RACH accesses = 34
34*1000
= 41.67 > 18Overload
51x16
30*1000 = 14.71 < 18Non-overload
51x40
RACH accesses = 30 RACH accesses = 30
0
rach_load_period
3.766s
00
rach_load_period
3.766s
ccch_load_period
13.186s
ccch_load_period
13.186s
rach_load_period
16.952s
rach_load_period
16.952s
2006 Motorola, Inc.
4-75
June 2007
Version 1 Rev 3 Alternative RACH Load Calculation
Alternative RACH Load Calculation
The RACH load is calculated when the RACH Measurement Period timer for a RACH timeslot has
been received (RACH_CHECKLOAD_TIMER expires) or the CCCH Load Period timer for a RACH
timeslot has been received (RACH_OVERLOAD_TIMER expires). When using the alternate (overload
control) method of RACH ow control, the Busy Access Percentage is calculated and compared
to therach_load_threshold to determine if the RACH is overloaded. Before the Busy Access
percentage can be calculated, further terms have to be investigated
RACH_Incorrect_Access
Number of RACH's that can't be decoded by the CCDSP (since the last correct RACH access). These
have exceeded a given RXLEV threshold but have been unable to be decoded due to collisions or
interference.
No_Rach_Count
If a correct RACH access is not received during a RACH load period, this must be taken into account
when calculating the load. Layer 1 should maintain a count of RACH load periods where a successful
RACH is not received (No_Rach_Count). The value No_Rach_Count is incremented by one when a
RACH load period goes by without a correct RACH access. No_Rach_Count is cleared when a correct
RACH access is nally received.
RACH_Busy_ Count
When the load period timer expires and at least one correct RACH access occurred during the time
period, the RACH_Busy_Count is calculated by averaging the RACH_Incorrect_Access count over
the number of RACH load periods where a RACH was not received and adding the number of correct
RACH_Accesses, as follows:
If the load period timer expires and no correct RACH access occurred during the time period, the
RACH_Busy_Count will equal 0.
2006 Motorola, Inc.
June 2007
Alternative RACH Load Calculation Version 1 Rev 3
s RACH_Acces
1 unt No_Rach_Co
s rect_Acces RACH_Incor
Count RACH_Busy_ +
+
=
Number of
RACHs that
cannot be
decoded
Number of load
periods where a
correct access not
received
Number of
correct RACH
accesses
The formula in the
brackets calculates the
average incorrect
RACH over the number
of load periods
2006 Motorola, Inc.
4-77
June 2007
Version 1 Rev 3 Alternative RACH Load Calculation
Busy Access Percentage
The average number of RACH_Incorrect_Accesses per load period since the last successful RACH
[i.e., RACH_Incorrect_Access / (No_Rach_Count + 1)] is divided by RACH_Busy_Count to get the
current load proportion. This proportion is multiplied by 1000 to get the load percentage since each unit
is equivalent to one-tenth of one percent. If this number is greater than a set threshold read from the
common database, then an overload situation exists. The value of the RACH_Overload_Threshold
should range from 0 to 1000, with a default value of 950. The equation is shown below:
2006 Motorola, Inc.
June 2007
Alternative RACH Load Calculation Version 1 Rev 3
Threshold RACH_Load_
_ _
1000 * cess correct_Ac RACH_In
>
Count Busy RACH

Calculated from
the number of
incorrect
accesses divided
by the total
number of RACH
load periods
Total number of correct
RACH accesses, plus the
total average number of
incorrect RACH accesses
Set in database, the
valid range is
between 0 and
1000, once busy
access % goes
above this level
overload situation
exists
2006 Motorola, Inc.
4-79
June 2007
Version 1 Rev 3 Alternative RACH Load Indication Example
Alternative RACH Load Indication Example
Site Details
Site B
Carriers 1
SDCCH 4
TCH 7
ccch_conf = 1 (non-combined 51 multiframe, ccch on timeslot 0 only)
rach_load_type = 1
rach_load_threshold = 900
Measurement period = 16*235.5ms = 3.766 sec (no overload)
Measurement period = 40*235.5ms = 9.42 sec (overload)
Description
Using this type of ow control the site conguration is not relevant, as the busy_access_percentage
is based upon a ratio of the total RACH accesses (RACH_Busy_Count) and the average of incorrect
RACH accesses
(RACH_Incorrect_Access)
The rst time the RACH measurement timer expires there have been no RACH accesses or RACH
incorrect accesses. This means:
no_rach_count = 1 (i.e. counts one measurement periods for averaging)
second time the RACH measurement timer expires, again there have been no RACH accesses or RACH
incorrect accesses. This means:
no_rach_count = 2 (i.e. count two measurement periods for averaging)
The third time the RACH measurement timer expires, there have been 2 RACH accesses and 7 incorrect
RACH accesses.
no_rach_count = 0 (but the previous no_rach_count value of 2 is used in the RACH_Busy_Count
calculation).
2006 Motorola, Inc.
June 2007
Alternative RACH Load Indication Example Version 1 Rev 3
Alternative RACH Load Indication Example
Site Configuration: 1 carrier, 4 SDCCH, 7 TCH
rach_load_type = 1
ccch_conf = 1
Site Configuration: 1 carrier, 4 SDCCH, 7 TCH
rach_load_type = 1
ccch_conf = 1
no_rach_count =1 no_rach_count =1
no_rach_count = 2 no_rach_count = 2
no_rach_count = 0 no_rach_count = 0
RACH Accesses = 0
Incorrect RACH Acc = 0
Rach_Slot_Count
RACH Accesses = 0
RACH Accesses = 0
Rach_Slot_Count
0
Rach_Slot_Count
RACH Accesses = 0
Rach_Slot_Count
RACH Accesses = 0
Rach_Slot_Count
RACH Accesses = 0
RACH Accesses = 0
Rach_Slot_Count
RACH Accesses = 2
Rach_Slot_Count
RACH Accesses = 2
RACH Accesses = 2
Threshold RACH_Load_
_ _
1000 * cess correct_Ac RACH_In
>
Count Busy RACH

1 unt No_Rach_Co
rect_Acces RACH_Incor
Count RACH_Busy_
+
=
((7/(2+1)*1000/4) > 900
500 < 900 no overload
Rounding down Rounding down
RACH_Access
s
+
= (7/(2+1)) + 2 = 4
2006 Motorola, Inc.
4-81
June 2007
Version 1 Rev 3 CRM Overload
CRM Overload
If the ag tch_flow_control is enabled the CRM can trigger ow control due to TCH congestion.
Every time the CRM allocates a TCH, the percentage of busy TCH is calculated. An extended range
channel is counted as one resource for TCH usage calculations. This calculated value is compared to
two thresholds:
The percentage of busy TCH is equal to or exceeds the value indicated by the database parameter
tch_busy_norm_threshold. If this happens an overload_onset message with the cause value
"normal overload" is generated.
The percentage of busy TCH is equal to or exceeds the value indicated by the database parameter
tch_busy_critical_threshold. If this happens an overload_onset message with the cause
value "critical overload" is generated.
Both of these threshold will also be triggered for AMR/GSM half-rate TCHs.
On receipt of the overload_onset message ow control commences (see ow control procedures).
2006 Motorola, Inc.
June 2007
CRM Overload Version 1 Rev 3
CRM Overload
chg_element tch_flow_control <value> <location>cell=<cell_desc>
value = 0 (disabled)
1 (enabled)
chg_element tch_busy_normal_threshold <value> <location>
default = 100
value = 0 to 100
chg_element tch_busy_critical_threshold <value> <location>
default = 100
value = 81 to 100
2006 Motorola, Inc.
4-83
June 2007
Version 1 Rev 3 SSM Flow Control
SSM Flow Control
SSM monitors the percentage of call information blocks used after allocation of each call information
block. Each SSM can handle up to 400 calls, after this number has been reached no more mobile
originated calls can be made. The remaining SSM resources are used to accommodate handover
of existing calls The number of call information blocks used will be increased by one each time a
call information block is allocated. Similarly, the count will be decreased when a call information
block is freed. Using the count of call info blocks used, the percentage of call info blocks used
will be calculated after each call info block allocation. Such a percentage will be compared with
the ssm_normal_overload_threshold in the SSM part of CM database. If the current level of
usage exceeds the ssm_normal_overload_threshold value, the SSM sends an overload_onset
message to the corresponding CRM. The process of sending overload_onset message to the
corresponding CRM will continue each time the call info block usage exceeds threshold value. The
overload cause value for this message to CRM will be normal overload.
The process of allocating the call info blocks will be continued until the call info block usage reaches
the ssm_critical_overload_threshold in the SSM part of CM database. When the call info block
usage reaches this second threshold, the SSM veries the new call info block allocation is for a call
origination. Any non-emergency call origination made after reaching the second overload threshold will
be torn down. Then the SSM sends a blast message to the corresponding the RRSM to tear down this
call. At the same time, SSM sends an overload_onset message to the corresponding CRM to reduce
mobile originations. The overload cause for this message to CRM will be critical_overload. If the SSM
is in critical overload and no call information blocks are available to satisfy an emergency call without the
extra emergency reserved blocks being used, the following steps are taken:
If the CM database parameter option_emerg_preempt indicates that emergency call
pre-emption is in operation, the SSM calculates the total number of available call information block
using the extra blocks reserved for emergency purposes only. It allocates a call information block
if one is available. If a block is allocated the SSM then attempts to initiate the release of a currently
active low priority call to obtain a call information block to replace the one that was allocated.
If the emergency call pre-emption feature is not in operation the SSM rejects the emergency call in
the usual manner.
2006 Motorola, Inc.
June 2007
SSM Flow Control Version 1 Rev 3
SSM Flow Control
chg_element ssm_critical_overload_threshold <value> 0
default = 80
chg_element ssm_normal_overload_threshold <value> 0
default = 70
value = 0 to 100
2006 Motorola, Inc.
4-85
June 2007
Version 1 Rev 3 MSC Overload
MSC Overload
In addition to the BSS initiated ow control situations the MSC may send an OVERLOAD message
to the BSS. This overload message triggers the existing ow control mechanisms on a per cell basis.
MSC overload is enabled by the database parameter bss_msc_overload_allowed. On receipt of the
OVERLOAD message from the MSC the MTPL3 process forwards the message to the CLM. The CLM
sends the message to each CRM in the BSS. Then for each cell CRM ow control is invoked following
the same timer constraints as exist for the BSS initiated ow control.
2006 Motorola, Inc.
June 2007
MSC Overload Version 1 Rev 3
MSC Overload
MSC
RXCDR
BSC
BTS
MSC
RXCDR
BSS
BTS
MSC Overl oaded
Overload
message
sent from
MSC to BSS
BSS reduces
traffic by barring
access classes
within cells
Access
class barred
Mobile class information is
carried to MS in SYSTEM
INFORMATION message
Timers t1 and t2 are used
to prevent multiple
overload messages from
the MSC and the
procedure for unbarring
access classes
chg_element bss_msc.overload_allowed<value>
Value = 0 (disabled)
Value = 1 (enabled)
BTS BTS
Access
class barred
BTS BTS
Access
class barred
2006 Motorola, Inc.
4-87
June 2007
Version 1 Rev 3 RSL Overload
RSL Overload
Introduction
When a MS in idle mode is to be contacted during a call, the mechanismused is paging. A single PAGING
message will be sent across the MSC to BSS interface and will contain information on the cells in which
the page shall be broadcasted. The page sent from the MSC will arrive at a single MTL-LCF, whereby
this card will re-construct the page and forward it to all RSL-LCFs. A RSL-LCF will, upon receiving the
page, duplicate it and send one paging message to each BTS controlled by the LCF. This way, a single
page message will be sent to all BTSs.
In certain conditions, surges of paging trafc may occur which could lead to buffer overow on one or
more RSLs. Due to the increased number of messages which have to be processed by the LCF, the
heartbeat response of the LCF to BSP could thus be delayed. This would cause the CA to assume that
the LCF is dead, leading to a GPROC reset. The purpose of the RSL Congestion Control is therefore:
To detect the onset of RSL congestion
Reject GSM paging trafc when overload condition is detected
Restart GSM paging trafc when overload condition abates.
2006 Motorola, Inc.
June 2007
RSL Overload Version 1 Rev 3
RSL Overload
Purpose:
To detect the onset of RSL congestion
Reject GSM paging traffic when overload condition is detected
Reject GSM paging traffic when overload condition abates
2006 Motorola, Inc.
4-89
June 2007
RSL Overload
Enabling the RSL Overload
This feature is enabled and unrestricted in the software.
Detecting RSL Overload
The detection of RSL overload or congestion is carried out in a number of ways and will concern individual
RSLs, individual LCFs and the GPROC lan.
Individual RSL Congestion
The LCF will look at the number of queued messages for the individual RSLs it controls and if the number
of messages exceeds a preset software threshold, the RSL is then considered to be congested. In this
instance the LCF will stop sending messages to that individual RSL
When the number of queued message falls below a preset software threshold for the individual RSL, the
LCF will recommence the sending of paging message to that RSL.
Individual LCF Congestion
The RSL-LCF will look at the individual RSLs that it controls to see how many are in the congested
state. If this number is greater than the percentage gure set by the database parameter
rsl_lcf_congestion_thi then the LCF will broadcast periodically the XOFF message to the LCFs
controlling the MTLs. This message will cause the MTL-LCF to stop sending paging message to the
RSL-LCF.
When the percentage of congested RSLs falls to a level below that set by the database parameter
rsl_lcf_congestion_tlow the RSL-LCF will cease the broadcast of the XOFF message and
commence periodic broadcast of the XON message to all MTL-LCFs. This will allow the MTL-LCFs to
recommence the sending of paging messages to the RSL-LCF
rsl_lcf_congestion_thi must be set to a higher value than rsl_lcf_congestion_tlow. It
should also be noted that only RSLs which are B-U will be considered by the detection system.
GPROC Lan congestion
If the Lan buffer for the MTL-LCF to RSL-LCF becomes full, the system will automatically stop sending
paging messages to the RLS-LCF concerned. When the buffer space becomes available, the system
will recommence the sending of the paging messages.
2006 Motorola, Inc.
June 2007
RSL Overload
MSC
MTL - LCF
RSL - LTF
XOFF/XON
OVERLOAD
BTS
rsl_lcf_congestion_thi <*> bsc
* 1 100 %
Default = 60 %
rsl_lcf_congestion_tlow <*> bsc
* 0 99 %
Default = 25 %
Paging
messages
Paging
messages
2006 Motorola, Inc.
4-91
June 2007
RSL Overload
RSL Congestion Control Mechanisms
The control hierarchy of this feature is as below, if one stage of control fails to alleviate congestion then
the next stage will be activated.
1. Maximum pages per second to the BTS, sets a throttle at the BSC and indicates when pages
are being discarded by pegging the statistic MSGS_DISCARD_ON_GPROC.
2. RSL Mailbox Congestion, LCF (RSL) discards paging when it detects an RSL is congested. This
is not congurable by the operator but pegs the statistic MSGS_DISCARD_ON RSL to indicate
pages were discarded.
3. RSLs per LCF Congestion threshold exceeded. A threshold set by an operator in the database
rsl_lcf_congestion_thi, throttles paging from LCF (MTL) whilst LCF (RSL) is transmitting
XOFF message.
4. If enabled by the database parameter msc_bss_overload_allowed the LCF (MTL) will send
overload messages to the MSC to indicate the BSS is in congestion, enabling throttling at the MSC.
5. When the LAN becomes congested, the paging will be discarded in the LAN mailbox rst. The
number of messages discarded is put into the statistic MSGS_DISCARD_ON_GPROC. However,
this Statistic contains another situation: when RSL is congested on a RSL-LCF, other GPROCs
will stop sending paging to this RSL-LCF and update the statistic MSGS_DISCARD_ON_GPROC
with the number. Therefore this Statistic does not always indicate LAN congestion. If
the LAN congestion still occur when GPROC discard paging and the depth of the LAN
mailbox reach maximum, any message to this mailbox will be discarded and a nonfatal swfm
"analyse_full_mailbox" will be generated.
2006 Motorola, Inc.
June 2007
RSL Overload
RSL Congestion Control Hierarchy
1. Discarding pages to the BTS from the BSC
2. Discard pages to an individual RSL
3. Discard pages to an Individual LCF
4. Throttle pages form the MSC
5. Discard pages across the LAN
2006 Motorola, Inc.
4-93
June 2007
RSL Overload
Control of RSL Overload
Timers
When the MTL-LCF receives the XOFF message fromthe RSL-LCF, it will stop sending paging messages
to the card, and start a Status timer (this is an internal timer and cannot be set by the operator). Continued
reception of the periodic XOFF message will stop this timer from expiring and therefore halt the sending
of paging messages. If the timer expires or is halted by an XON message it will recommence the sending
of the paging messages.
The periodic sending of the XOFF message is controlled by an internal RSL-LCF timer which cannot be
set by the operator
Overload Message
When the MTL-LCF detects the receipt of the XOFF message i.e. RSL overload has occurred, it will
in addition to stopping paging messages being sent to the RSL-LCF, notify the MSC with a overload
message whose cause value is processor overload. This message will only be sent if the database
parameter msc_bss_overload_allowed is set correctly and will cause the system to carry out ow
control as previously described. The time between sending these message will depend upon the setting
of the database parameter bss_overload_control.
RSL Overload Alarms
In the event of RSL overload being detected by the RSL-LCF, the GPROC will forward to the OMC-R,
an RSL Congestion Alarm. The minimum time between sending this alarm may be set by the database
parameter rsl_congestion_alarm_timer.
Maximum Number of Pages
The operator also has the ability to set the maximum number of pages that will occur form the BSS to
the BTS in one second. This is carried out by the database parameter max_pagenum_per_sec.
2006 Motorola, Inc.
June 2007
RSL Overload
msc_bss_overload_allowed <*> bsc
* 0 = do not send overload message
1 = send overload message
Default = 1
bss_overload_control <*> bsc
* 1000 1000000ms
Default = 12500ms
rsl_congestion_alarm_timer <*> bsc
* 1000 600000ms
Default = 6000ms
max_pagenum_per_sec <*> bsc
* 70 - 65535
Default = 65535
2006 Motorola, Inc.
4-95
June 2007
Version 1 Rev 3 BSC Overload
BSC Overload
This GSR9 feature, along with others has been implemented to increase Network Capacity. All features
are restricted by the option incNetCapacityOpt.
The BSS system only has one active BSP equipped. The availability of the BSP is critical for the system
as it is responsible for BSS site management (FM, ALARM, STATS etc.) As the BSP also take the
responsibility for the function of switch management(SM) and circuit management (AM), these functions
will cause BSPCPUto have high utilization when the systemis working under high load of call processing.
This feature provides CPU utilization overload protection for the BSP. The feature monitors the BSP CPU
utilization in real-time. When the BSP CPU utilization jumps over the overload threshold, the feature
starts controlling the amount of assignment requests and non-imperative handovers to be handled by
the system, by dropping them at random, so that the CPU utilization of the BSP can be kept under a safe
level.
The target of the feature is to make the BSP able to work reliably around 90% CPU utilization when
the system receives excessive requests for calls and handovers which exceed the maximum processing
capability of the BSP. As the feature makes the system more stable under high load of service requests,
the operator may plan the BSP to work in a higher CPU utilization in normal time.
The operator can enable/disable this feature by changing the value of the new database element
bsp_overload_protection. When the feature is enabled, the feature will be triggered automatically
when the BSP jumps into CPU overload state. This element can be displayed and changed at the OMC.
It can be changed inside and outside of SYSGEN mode. It is optional in the creation of a BSS.
Possible BSC Overload Causes
1. While the BSC is processing a huge number of requests for handover and call setup/release,
the BSP exhausts the available CPU resources.
2. A great number of alarms are generated in the BSS.
3. A software fault in some BSP process causes high CPU utilization.
4. Hardware fault.
The BSP calculates the CPU utilization and broadcasts to all LCF boards periodically (every 5 secs).
When the CPU utilization goes over 85%, the BSC generates an alarm BSP safe overload. When
the CPU utilization goes over 95%, the BSC generates an alarm BSP critical overload. The control
mechanism attempts to prevent the BSP moving from safe overload into critical overload state.
If the database element MSC_BSS_OVERLOAD_ALLOWED is enabled, the BSC will send overload
message periodically to the MSC when the BSP is under overload state. (Cause Value: processor
overload)
The LCF keep two types of tokens separately for assignment request message from MSC and
non-imperative handover recognized received message from BTS. A handover recognized received
message can be identied as non-imperative according some eld in the message. In a BSP
broadcasting cycle, the LCF is not permitted to process each type of message more than the number
of corresponding tokens. This is because these two messages will cause the LCF to send a message
to the BSP.
The LCF tracks the numbers for assignment request and non-imperative handover recognized
received messages handled by the SSM in the last BSP broadcasting cycle. When the LCF receives
the BSP CPU utilization message from the BSP, it calculates the new number for the tokens. The new
tokens are used to control the number of message permitted to process in the coming cycle.
The feature has interaction with GSR8 feature RSL Congestion Control on the function of sending
overload message to MSC. The overload message can be triggered by RSL congestion as well. Only
when both RSL congestion and BSP overload abate, the BSC will stop sending overload message.
The value for safe_overload guard timer is one minute.
This feature doesnt introduce any new impact to performance and capacity of the system. It makes the
system more robust. This feature adds reliability and availability to the system under high load.
2006 Motorola, Inc.
June 2007
BSC Overload Version 1 Rev 3
BSC Overload
bsp_overload_protection 0: Disabled
1: Enabled
2006 Motorola, Inc.
4-97
June 2007
BSC Overload
Assumptions and Transition States
BSP safe-overload threshold: The threshold of CPU utilization for the BSP transiting from
non-overload state into safe-overload state.
BSP critical-overload threshold: The threshold of CPU utilization for the BSP transiting from
safe-overload state into critical-overload state.
BSP safe-overload state: When the BSP CPU utilization is in the range of safe-overload threshold
to critical-overload threshold, the overload control mechanism starts the control. The BSP has a high
CPU utilization but still works reliably.
BSP safe-overload target point: This term is used when the CPU utilization is at mid-point between
safe-overload and critical-overload thresholds. The control mechanism will attempt to move the
utilization toward the mid-point when BSP is in safe-overload state, therefore it takes different action
when the BSP CPU utilization is above and below the mid-point.
The safe-overload and critical-overload threshold are hard coded.
Token bucket shaping algorithm is applied in this feature to control the load. Whenever the transmitter
(LCF) sends a packet to the receiver (BSP), it removes a token from its bucket (that is, decrements the
counter). If the bucket becomes empty (that is, the counters value is zero), the transmitter will no longer
send packets to the receiver; instead, it will drop them. The receiver (BSP) periodically sends CPU
utilization information to the transmitter, so that the bucket can be recalculated for the number of tokens
(that is, the counter is updated with the re-calculated number of tokens).There are two token buckets
dened for token bucket algorithm at SSM. One is for the assignment request messages from MSC,
another one is for the non-imperative handover recognize received message.
2006 Motorola, Inc.
June 2007
BSC Overload
BSP Overload State Transition
No Overload
Safe Overload
Critical Overload
util > 95
Get BSP out of
this state
85 ~ 95
Keep BSP in this
state
util < 85
Do nothing except for
keeping monitor
B S P s afe-overload thres hold
B S P critical-overload thres hold
B S P s afe-overload s tate
B S P s afe-overload target point
2006 Motorola, Inc.
4-99
June 2007
BSC Overload
Procedure
The BSP goes into safe-overload from non-overload state when the BSC come into in service state,
It will then begin calculating the CPU utilization of BSP board periodically. When the BSP CPU utilization
reaches the BSP safe-overload threshold, if the BSP safe overload alarm is not active, the BSC will
send an alarm BSP Safe Overload. If the database element MSC_BSS_OVERLOAD_ALLOWED is
enabled, the BSC will start periodically sending the Overload message to the MSC with clause Process
overload.The BSC will start dropping non-imperative handover recognized messages from the BTS and
rejecting assignment request message from the MSC. Upon rejection of an assignment request, the BSC
shall send an Assignment Failure message with cause O&M intervention to the MSC as response.
The BSC shall control the rate at which non-imperative handovers are dropped and assignment requests
rejected to keep the BSP working in safe-overload state. When the BSP CPU utilization falls below
BSP safe-overload threshold. the BSC shall stop sending Overload to the MSC If BSP CPU utilization
does not reach the BSP safe-overload threshold in a guard period since it fell below the threshold, the
BSC shall clear the alarm BSP safe overload
When the BSP CPU utilization reaches the BSP critical-overload threshold. the BSC shall send an
alarm BSP Critical Overload. The BSC shall control the rate at which non-imperative handovers are
dropped and assignment requests rejected to move the BSP from critical-overload into safe -overload
state. when BSP CPU utilization falls below BSP critical -overload threshold.the BSC shall clear the
alarm BSP critical overload.
Note: Probability of being in overload state for too long is low:
The probability of BSP going too far over critical overload stste from safe-overload state is small
(messages may be dropped in safe overload state. This implies it is not necessary to reduce the
threshold to a minimum value immediately.
The control cycle is sufciently fast (5 seconds) to reduce the BSP CPU utilisation from the sudden
change to critical overload state.
2006 Motorola, Inc.
June 2007
BSC Overload
BSP
utilization
(U)
MTL-LCF Actions RSL-LCF Actions BSP Actions
1) ALL Monitor BSP Utilization
message and respond as
described below.
Load tracking (as
described in white paper)
Monitor BSP Utilization
message and respond as
described below.
Load tracking (as
described in white
paper)
BSP periodically computes
moving average of its
utilization and multicasts
moving average to MTL-
LCFs & RSL-LCFs.
2)
Initialization
Computed refresh value
(value used to reset token
bucket) set to minimum
(value used to reset
token bucket) set to
minimum
utilization;
Multicasts to MTL-LCFs &
RSL-LCFs.
3) U 80% Rapid increase of
computed refresh value
Rapid increase of
utilization, and multicasts to
MTL-LCFs & RSL-LCFs.
4) 80% < U
90%
Slow increase of
Slow increase of
If BSP utilization is > 88%,
rebalance LCFs every 5
minutes (as described in
paper) by overriding locally
computed refresh values.
5) 88% U <
93%
Transmits computed
refresh values to BSP on
demand.
Resets computed refresh
value to value specified
by BSP (if rebalancing is
being done).
Transmits computed
refresh values to BSP on
demand;
Resets computed refresh
value to value specified
by BSP (if rebalancing
is being done).
Rebalance LCFs every 5
minutes by overriding
locally computed refresh
values.
6) 90% U <
93%
Page admission/dropping
(as descibed per white
paper).
CM SERVICE
REQUEST accept/reject
(as described per white
paper).
Minor overload
alarms/events logs
/notifications to OMC-R
(refer to RSL-LCF
Congestion Control SFRAS
in GSR8 for similar
alarming situation)
7) 93% U <
95%
50% reduction in
computed refresh value,
not below the minimum
value.
50% reduction in
computed refresh value.
Reject all non-
imperative HO requests;
Reject inbound Inter-
BSS HO requests;
Send OVERLOAD
ONSET message to
BTSs.
Major overload alarms/
events logs /notifications to
OMC-R;
Transmit OVERLOAD to
MSC with cause value =
PROCESSOR
OVERLOAD in
accordance with GSM 48.08
specifications.
8) U 95% Computed refresh value
set to minimum.
set to minimum.
Reject all HO requests;
Send OVERLOAD
ONSET message to
BTSs.
Critical overload alarms/
events logs / notifications to
OMC-R;
Transmit OVERLOAD to
MSC with cause value =
PROCESSOR
OVERLOAD in
accordance with GSM 48.08
specifications.
2006 Motorola, Inc.
4-101
June 2007
BSC Overload
Overload Control Algorithm 1
Overload Control (5 seconds cycle):
CPU utilisation thresholds:
70%: Load-control threshold; 85%: Safe-overload threshold
90%: Target Utilisation; 95%: Critical overload threshold
The following actions will take place in the LCFs:
CPU utilisation <70%
Calculate the token value but not used to drop calls
70% <CPU utilisation <85%
Rapidly increase token value by 10%
CPU utilisation <90%
Slowly increase token value by 5%
90% <CPU utilisation <95%
Slowly decrease token value by 5%
CPU utilisation >95%
Rapidly decrease token value by 10%
Overload Control Algorithm 2
The following actions will take place in the LCFs once the token value is reached and the BSP CPU
utilisation is above 70%:
Drop non-imperative handovers (RSL-LCF)
Drop incoming inter_BSS handover requests (RSL-LCF)
Send OVERLOAD message to MSC periodically (MTL-LCF)
2006 Motorola, Inc.
June 2007
BSC Overload
Token Value Adjustments
80 82 84 86 88 90 92 94 96 98 4 7 6 7 8 7
CPU utilization %
Token
Adjustment
No Overload
Safe Overload
Critical
Overload
Slowly increase token;
Slowly decrease token
Rapidly decrease
token
82 84 86 88
No Overload
Rapidly increase token;
Drop call may occur
Overload Load Control
1s 2s 3s 4s 5s 6s 7s 8s 9s 10s time
BSP load
mean
1s 2s 3s 4s
time
BSP load
5s 6s 7s 8s 9s 10s 11s 12s
mean
Token Increase:
no drop period drop period
no drop period
drop period
Token Decrease:
2006 Motorola, Inc.
4-103
June 2007
Version 1 Rev 3 BSS Location Services (LCS) - System Overview
BSS Location Services (LCS) - System Overview
From GSR6 the BSS is providing support for Location Services. Location Services uses one or more
positioning mechanisms in order to determine the location of the MS. The positioning process involves
two main steps: signal measurements and location estimate computation based on the measured
signals. LCS has been seen by operators, service providers and Motorola as a key application enabler.
This will allow calculation of the position of the MS directly, location specic advertising and to determine
the routing of voice trafc. This can be achieved in three ways:
TA Positioning Mechanism
The Timing Advance positioning mechanism is based on the existing Timing Advance (TA) parameter.
The TA value is known for the serving BTS. The TA value, the cell ID and the measurement reports are
return to the requesting LCS client.
E-OTD
Enhanced Observed Time Difference (E-OTD) Positioning Mechanism uses the MS and a number of
BTS's to calculate a position for the MS based on time delays (Real Time Differences - RTDs) to the MS
from the BTS and geometry. This depends on whether it is a synchronised network or unsynchronised
network. If synchronised the MS measures the relative time of arrival of the signal fromseveral BTSs. For
unsynchronised the signals are received by a xed measuring point known as a Location Measurement
Unit (LMU). The calculations can be made in the MS if all information present (MS-based) or if not
MS-assisted. To obtain accurate triangulation RTDs are required from at least three geographically
distinct BTSs.
A-GPS
Global Positioning System (GPS) provides a means to determine position, velocity and time around the
globe. It uses satellites emitting radio signals to the receivers to determine position of the receiver.
The GPS constellation consists of 24 satellites orbiting at an altitude of 20,183.62km above Earths
surface. Based on Time of Arrival (TOA) principle, when four or more satellites are in Line of Sight
(LOS) from the receiver, the latitude, longitude and altitude of the receiver are determined. Standard
Positioning Service (SPS) is a grade of GPS service available for commercial applications including
mobile phone location determination. SPS is deliberately degraded by selective availability (SA), but
provides horizontal position accuracy within a circle of 100m radius 95% of the time. Differential-GPS
(D-GPS) can reduce the error to under 5m, while SA and other factors are in effect. It uses a reference
receiver at a surveyed position to send correcting information to the mobile over the communication link.
For Assisted-GPS (A-GPS), a GPS reference network (or a Wide area D-GPS network) is established.
The GPS reference network manages receivers with clear views of the sky and can operate continuously.
This reference network is connected with the GSM network. At the request of the GSM network,
assistance data from the reference network is transmitted to the MS to increase performance of the
GPS sensor. The Assisted-GPS method should be able to:
Reduce the sensor start-up time;
Increase the sensor sensitivity; and
Consume less handset power than conventional GPS does.
Additional assisted data, such as differential GPS corrections, approximate handset location or cell base
station location, and others can be transmitted to improve the location accuracy and decrease acquisition
time.
2006 Motorola, Inc.
June 2007
BSS Location Services (LCS) - System Overview Version 1 Rev 3
BSS Location Services (LCS) - System Overview
Timing Advance Positioning Mechanism
Enhanced Observed Time Difference Positioning Mechanism
Assisted Global Position System Positioning Mechanism
2006 Motorola, Inc.
4-105
June 2007
Version 1 Rev 3 BSS Location Services (LCS) - Network Architecture
BSS Location Services (LCS) - Network Architecture
Several new network elements are added to the general GSM architecture to support Location Services.
A brief illustration of the new network topology is shown in the diagram opposite. Note that a number of
new interfaces were created for the new network entities. The central interface impacting the BSS is the
Lb interface.
GMLC
The Gateway Mobile Location Center (GMLC) is a new network element being added to the GSM PLMN
in support of Location Services. The GMLC is the rst node an external LCS Client accesses in a GSM
PLMN. The GMLC may request routing information from the HLR via the Lh interface. After performing
registration authorization, it sends positioning requests to and receives nal location estimates from the
VMSC via the Lg interface. The GMLC is responsible for the following functions:
Managing external interface to LCS
Authorising LCS Clients requesting LCS information
Collecting charging and billing data related to LCS for both clients and subscribers
Transforming location estimates into local geographic system understood by the client.
SMLC
The Serving Mobile Location Center (SMLC) is a new network element being added to the GSM PLMN in
support of Location Services. The SMLC manages the overall co-ordination and scheduling of resources
required for MS positioning. It also calculates the nal location estimate and accuracy. As seen in the
diagram opposite, two new signal interfaces, Ls and Lb, have been dened to transport messages to
and from the SMLC. The Ls interface associates the SMLC with the VMSC. Hence, the VMSC will be
needed to route signals to the SMLC via the Ls interface in this conguration. Similarly, the Lb interface
associates the SMLC with the BSC. The BSS will need to support message routing to the SMLC via the
Lb interface in this conguration.
The SMLC is responsible for the following functions:
Registering and maintaining operational status of LMUs
Providing broadcast capability for E-OTD and A-GPS
Managing the positioning of a MS through the co-ordination and scheduling of resources
Calculating the positioning of the MS
The phrase "BSS based SMLC" refers to an SMLC communicating with the BSS via the Lb interface.
The phrase "NSS based SMLC" refers to an SMLC communicating with the MSC via the Ls interface.
For this feature BSS will be communicating with the MSC only.
2006 Motorola, Inc.
June 2007
BSS Location Services (LCS) - Network Architecture Version 1 Rev 3
BTS
BSS
MSC/VLR
Gateway
MLC
HLR
External
LCS
Client
SMLC
CBC
Lb
Ls
CBC-BSC
CBC-SMLC
ABIS
A
Lg
Lh
SMLC Lp
Lg
Gateway
MLC
Other
PLMN
LMU
Type A
LMU
Type B
uM
Le
2006 Motorola, Inc.
4-107
June 2007
Version 1 Rev 3 BSS Location Services (LCS) - Network Architecture
LMU
A Location Measurement Unit (LMU) makes radio measurements to support one or more positioning
methods. These measurements fall into one of two categories:
Location measurements specic to one MS used to compute the location of this MS
Assistance measurements specic to all MSs in a certain geographic area
All location and assistance measurements obtained by an LMU are supplied to a particular SMLC
associated with the LMU. Instructions concerning the timing, the nature and any periodicity of these
measurements are either provided by the SMLC or are pre-administered in the LMU.
Type A LMU
A type A LMU is accessed exclusively over the GSM air interface (Um interface): there is no wired
connection to any other network element. A type A LMU has a serving BTS and BSC that provide
signalling access to a controlling SMLC. With an NSS based SMLC, a type A LMU also has a serving
MSC and VLR and a subscription prole in an HLR. A type A LMU always has a unique IMSI and supports
all radio resource and mobility management functions of the GSM air interface that are necessary to
support signalling using an SDCCH to the SMLC. A type A LMU supports those connection management
functions necessary to support LCS signalling transactions with the SMLC and may support certain call
control functions to support signalling to an SMLC using a circuit switched data connection.
Type B LMU
A Type B LMU is accessed over the Abis interface from a BSC. The LMU may be either a standalone
network element addressed using some pseudo cell ID or connected to or integrated in a BTS. Signalling
to a Type B LMU is by means of messages routed through the controlling BSC for a BSS based SMLC
or messages routed through a controlling BSC and MSC for an NSS based SMLC.
The term "LMU" indicates a Type A LMU. The BSS does not support Type B LMUs. Also the term
"SMLC", when not prefaced by either "NSS based" or "BSS based" shall be inferred to be indicating a
BSS based SMLC.
LMU Procedures
For the most part, LMUs will be handled like regular mobiles, except that all signalling goes to the SMLC
and not the MSC when the SMLC is BSS based. The LMUs are allowed to get an SDCCH and even
perform handovers. However, the LMUs cannot get a TCH.
2006 Motorola, Inc.
June 2007
BSS Location Services (LCS) - Network Architecture Version 1 Rev 3
BTS
BSS
MSC/VLR
Gateway
MLC
HLR
External
LCS
Client
SMLC
CBC
Lb
Ls
CBC-BSC
CBC-SMLC
ABIS
A
Lg
Lh
SMLC Lp
Lg
Gateway
MLC
Other
PLMN
LMU
Type A
LMU
Type B
uM
Le
2006 Motorola, Inc.
4-109
June 2007
Version 1 Rev 3 LCS Database Parameters
LCS Database Parameters
LCS is a restricted feature and must be purchased.
There are a number of database parameters associated with the LCS feature. The important ones
are included and described in this manual to aid clarity of feature understanding, whilst timer database
parameters associated with the Lb interface are not included as they are normally defaulted the same
as the SSNo7 timers applicable to the A-Interface link.
LCS Mode
The database parameter LCS mode sets the mode of operation for LCS if it is enabled at a BSS site. It
has a number of dependencies associated with it.
chg_element lcs_mode <*><location>
<*> 0 - LCS disabled, SMLC not supported
1 - LCS enabled, BSS supports a NSS based SMLC
2 - LCS enabled, BSS supports a BSS based SMLC
Default = 0
Dependencies
The database parameter early classmark sending must be set to supported across both the air and A
interface.
chg_element early_classmark_sending <*><location>
<*> 0 - Disabled
1 - Enabled on A int, disabled on air int
2 - Disabled on A int, enabled on air int
3 - Enabled on A int, enabled on air int
Default = 0
The database parameter phase 2 classmark allowed must be set to allow mutliband.
chg_element phase2_classmark_allowed <*><location>
<*> 0 - Formatted for phase 1
1 - Formatted for phase 2
2 - Formatted for phase 2 with multiband
Default = 0
2006 Motorola, Inc.
June 2007
LCS Database Parameters Version 1 Rev 3
BTS
BSS
MSC/VLR
Lb
ABIS
LMU
Type A
LMU
Type B
SMLC
A
chg_element lcs_mode 2 0
chg_element early_classmark_sending 3 0
chg_element phase2_classmark_allowed 2 0
2006 Motorola, Inc.
4-111
June 2007
Version 1 Rev 3 LCS Database Parameters
LCS Perform Location Response
A perform location response message may come from the MSC to a BSS-based SMLC via the BSS. In
this case the BSS must initiate a SCCP connection to the BSS based SMLC. This includes classmark 3
information, timing advance and measurement report information. Hence the BSS must have performed
the timing advance positioning procedure. The LCSPerformLocation timer guards against there being no
response fromthe BSS-based SMLCin the formof a BSSMAP-LEPerformLocation Response message.
If the timer is allowed to expire it sends a BSSMAP Perform Location Response message with the cause
value "Location Request Aborted" and send a SCCP Released message to the SMLC to release the Lb
connection.
chg_element lcs_perf_location <*><location>
* 0 to 1,000,000(ms) Default = 300,000(ms)
LCS Supervision
There are three positioning procedures. The BSS does not support the Time of Arrival positioning
procedure, but does support the Timing Advance and E-OTD/A-GPS positioning procedures. In the
case of Timing Advance positioning procedure if either the MSC or BSS-based SMLC sends a BSSLAP
TA Request the LCS Supervision Timer is started, it is stopped when the BSS sends a BSSLAP TA
response message to either the MSC or BSS Based SMLC. If it expires a BSSLAP Abort message is
sent to the MSC or BSS-based SMLC with the cause value "Supervision Timer Expired". In the case
of E-OTD/A-GPS positioning procedure the LCS Supervision Timer is started on receipt of a BSSLAP
MS Position Command from either the MSC or BSS-based SMLC. The timer is stopped in both cases
by the receipt of a RR Application Information with the APDU ag C/R bit set to "Not Command or Final
response" message from the MS. If the timer expires before receipt of the RR Application Information
message then a BSSLAP Abort message with the cause value "Supervision Timer Expired" is sent to
either the MSC or the BSS-based SMLC.
chg_element lcs_supervision <*><location>
* 0 to 1,000,000(ms) Default = 30,000(ms)
Segmentation
Segmentation is used for messages that are longer than the maximum size message allowed for a
given protocol. The protocols where segmentation is allowed are BSSMAP-LE, BSSMAP RR Application
messages. The LCS Supervision timer guards against the last segment not arriving in time. If the timer
is allowed to expire then all segmentation messages are discarded
chg_element lcs_segmentation <*><location>
* 0 to 1,000,000(ms) Default = 10,000(ms)
2006 Motorola, Inc.
June 2007
LCS Database Parameters Version 1 Rev 3
BSSMAP Perform Location Request
MSC BSS BSS Based SMLC
0
LCS Perform
Location Timer
BSSMAP-LE Perform Location Request
-LE Perform Location Response
BSSMAP Perform Location Response
0
LCS Perform
Location Timer
BSSMAP Perform Location Response
Cause Value
Location req aborted"
SCCP RLSD
BSSMAP
2006 Motorola, Inc.
4-113
June 2007
Version 1 Rev 3 Path
Path
The specic transmission route which trafc and signalling will take from a BTS, perhaps via intermediate
BTSs, to the BSS is largely determined by the software. To enable this to occur "Paths" have to be built
using the available MSI cards and port numbers through each BTS, starting from the BSS. The path
command is very simple and is as follows:
equip <0 or bsc> PATH
Prompts
Prompt 1 (Terminating site ID)
This is the ID of the BTS site terminating the path.
Prompt 2 (Unique Path ID)
Each BTS site can have up to 10 unique paths, conventionally, numbering of paths start at 0.
Prompt 3 (BSC MSI ID)
This is the ID of the terminating MSI card and MMS port at the BSS.
Prompt 4 (Site ID)
This is the identity of the next BTS site in the chain.
If the aggregate A-bis feature is enabled the system will accept ts_switch as the site Id. If is
ts_switch is used, the system will not prompt for upstream MSI, upstream MMS, downstream MSI
and downstream MMS identiers.
Prompt 5 (Upstream MSI ID)
This is the identity of the MSI card and MMS port at the rst BTS in the chain, facing upstream towards
the BSS.
Prompt 6 (Downstream MSI ID)
This is the identity of the MSI card and MMS port at the rst BTS in the chain, facing downstream towards
the terminating site.
A path can proceed through a number of BTS sites before reaching its terminating BTS. To that end, the
last three parameters are repeated for each intermediate site.
2006 Motorola, Inc.
June 2007
Path Version 1 Rev 3
Path
equip <0 or
bsc> Path
enter the terminating SITE id: 1
120
enter the unique PATH id: 09
enter the BSC MSI id: 055 , 0 or 1
enter the SITE id: 1100 or ts_switch

enter the upstream MSI id: BTS
09, 0 or 1 (non M- Cell)
03, 0 or 1 (M-Cell6 Horizonmacro)
01, 0 or 1 (M-Cell2)
0, 0 or 1 (M-Cellmicro)
0, 0-5 (
HorizonII
macro
-
- macro)
- )
- )
- )
enter the downstream MSI id:
Repeat
SYS02_Ch4_44
BTS
09, 0 or 1 (non M- Cell)
03, 0 or 1 (M-Cell6 Horizonmacro)
01, 0 or 1 (M-Cell2)
0, 0 or 1 (M-Cellmicro)
0, 0-5 (
HorizonII
macro
-
- macro)
- )
- )
-
& HorizonIImini
)
& HorizonIImini
2006 Motorola, Inc.
4-115
June 2007
Version 1 Rev 3 Path Equipage Exercise
Path Equipage Exercise
The diagram opposite contains the information necessary to equip 2 paths to BTS site 16. Use the
working area below to equip both paths, path 0 should be made the shortest.
equip < > PATH equip < > PATH
terminating site id
path id
BSC MSI id
Site id
upstream MSI id
downstream MSI id
Site id
upstream MSI id
downstream MSI id
Site id
upstream MSI id
SYS02_Ch4_08
2006 Motorola, Inc.
June 2007
Path Equipage Exercise Version 1 Rev 3
Path Equipage Exercise
SYS04_Ch4_09
MSI 3
BSS
MSI 1
MSI 1
M
S
I
3
BTS 14
NIU 0
N
I
U
1
BTS 15
MSI 3
M
S
I
1
BTS 16
Port 0
Port 0
Port 0
Port 0
Port 0
Port 1
Port 0
Port 0
2006 Motorola, Inc.
4-117
June 2007
Version 1 Rev 3 Path Equipage Exercise
2006 Motorola, Inc.
June 2007
BTS Conguration Version 1 Rev 3
Chapter 5
BTS Conguration
2006 Motorola, Inc.
5-1
June 2007
Version 1 Rev 3 BTS Conguration
2006 Motorola, Inc.
June 2007
Objectives
On completion of this chapter the student will be able to
Describe the device / function interdependency used within BTS database structure
Explain battery conservation and mains power failure procedures
Describe the equipage of cards and processors within the BTS
Describe the equipage of DRIs/TCUs and combiners within the BSS
Complete a written exercise to equip a BTS database
2006 Motorola, Inc.
5-3
June 2007
Version 1 Rev 3 Device and Function Dependency - M-Cell/Horizon
Device and Function Dependency - M-Cell/Horizon
As with In-Cell sites a logical order exists with respect to equipping devices and functions in the CM for
M-Cell/Horizon sites. It is logical for example that an NIU be equipped before a path statement, as the
path statement will nominate certain NIUs for its trafc route. The chart opposite shows the dependency
chart in respect of M-Cell/Horizon systems.
It should be remembered that the BTP could actually be an MCU, MCUF or an HIISC card depending
on the type of equipment in use at he site
2006 Motorola, Inc.
June 2007
Device and Function Dependency - M-Cell/Horizon Version 1 Rev 3
Device and Function Dependency - M-Cell/Horizon
SYS02_Ch4_03
BSS
Site
Cell Cab
COMB MCU (BTP)
GCLK CSFP
TCU (DRI)
Path
RTF
16 kbit/s RSL 64 kbit/s RSL
Associated RTF
NIU (MSI/PSI)
2006 Motorola, Inc.
5-5
June 2007
Version 1 Rev 3 BTS Script Building
BTS Script Building
Script Chart
The script building chart shown opposite species the groups of parameters necessary to populate a
BTS database. The actual parameters can be examined more closely by following the example script
overleaf.
2006 Motorola, Inc.
June 2007
BTS Script Building Version 1 Rev 3
BTS Script Building
EQUIP SITE
EQUIP CAB
EQUIP CAGE
SITE CONFIGURATION
MMSTHRESHOLDS
ADD CELL
DEVICE EQUIPAGE
MISCELLANEOUS
2006 Motorola, Inc.
5-7
June 2007
Version 1 Rev 3 BTS - 1.9.0.0 Script Files
BTS - 1.9.0.0 Script Files
# EXAMPLE MCELL6 BTS DATABASE
# GSR9 (1.9.0.0 )
# 3 CARRIER OMNI WITH CCB
equip 0 site
4 # Site id
LCF # LCF at BSC supporting this site
0 # Function id for LCF
64 # RSL data rate
equip 4 cab
0 # Cab id
11 # Cab type
1 # pgsm frequency
# E1 link parameters defaulted
add_cell 2 3 4 0 1 678 4 4 "Swindon East"
frequency_type = 1
bsic = 8h
wait_indication_parameters = 20
ccch_conf = 0
bs_ag_blks_res = 1
bs_pa_mfrms = 1
extended_paging_active = 1
number_sdcchs_preferred = 8
en_incom_ho = 1
intra_cell_handover_allowed = 1
inter_cell_handover_allowed = 1
number_of_preferred_cells = 6
ho_margin_def = 8
handover_recognized_period = 12
ul_rxqual_ho_allowed = 1
dl_rxqual_ho_allowed = 1
ul_rxlev_ho_allowed = 1
dl_rxlev_ho_allowed = 1
sdcch_ho = 0
sdcch_timer_ho = 1
interfer_ho_allowed = 1
pwr_handover_allowed = 1
ms_distance_allowed = 0
mspwr_alg = 0
handover_power_level = 6
pwrc = 1
intave = 8
timing_advance_period = 4
ms_p_con_interval = 2
ms_p_con_ack = 2
ms_power_control_allowed = 1
bts_p_con_interval = 4
bts_p_con_ack = 2
bts_power_control_allowed = 0
pow_inc_step_size_ul = 6
pow_inc_step_size_dl = 6
pow_red_step_size_ul = 4
pow_red_step_size_dl = 4
dyn_step_adj= 0
dyn_step_adj_fmpr = 10
max_tx_bts = 0
max_tx_ms = 31
rxlev_min_def = 0
ms_txpwr_max_def = 31
decision_alg_type = 0
decision_1_dl_rxlev_av_h = 1
decision_1_dl_rxlev_av_ih = 0
decision_1_dl_rxlev_av_p = 0
2006 Motorola, Inc.
June 2007
BTS - 1.9.0.0 Script Files Version 1 Rev 3
decision_1_dl_rxqual_av_h = 0
decision_1_dl_rxqual_av_p = 0
decision_1_n1 = 2
decision_1_n2 = 2
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 2
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_ncell_rxlev_av_h_calc = 0
decision_1_p1 = 2
decision_1_p2 = 2
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 2
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
decision_1_p_bgt_rxlev_av_h = 0
decision_1_tim_adv_av_alg = 0
decision_1_ul_rxlev_av_h = 0
decision_1_ul_rxlev_av_ih = 0
decision_1_ul_rxlev_av_p = 0
decision_1_ul_rxqual_av_h = 0
decision_1_ul_rxqual_av_p = 0
alt_qual_proc = 0
l_rxqual_ul_p = 226
l_rxqual_dl_p = 226
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 400
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 2
link_about_to_fail = 1
full_pwr_ross = 1
cell_bar_access_switch = 0
cell_bar_access_class = 0
emergency_class_switch = 0
report_resource_tch_f_high_water_mark = 1
report_resource_tch_f_low_water_mark = 5
rxlev_access_min = 0
dtx_required = 0
attach_detach = 0
ncc_of_plmn_allowed = 2h
max_retran = 3
ms_txpwr_max_cch = 6
tx_integer = 12
radio_link_timeout = 2
reestablish_allowed = 1
cell_reselect_hysteresis = 2
cell_reselect_param_ind = 0
2006 Motorola, Inc.
5-9
June 2007
Version 1 Rev 3 BTS - 1.9.0.0 Script Files
cell_bar_qualify = 0
cell_reselect_offset = 0
temporary_offset = 0
penalty_time = 0
rapid_pwr_down = 0
rpd_trigger = 40
rpd_offset = 8
rpd_period = 2
chg_element cbch_enabled 1 4 cell_number = 2 3 4 0 1 678 4
chg_cell_element surround_cell, 0 0 2 3 4 0 1 678 4
4
1
chg_cell_element rel_tim_adv, 0 0 2 3 4 0 1 678 4
4
2
chg_cell_element rxlev_dl_ho, 0 0 2 3 4 0 1 678 4
4
2
chg_cell_element rxlev_dl_ho, 1 0 2 3 4 0 1 678 4
4
1
chg_cell_element rxlev_dl_pc, 0 0 2 3 4 0 1 678 4
4
2
chg_cell_element rxlev_ul_ho, 0 0 2 3 4 0 1 678 4
4
2
chg_cell_element rxlev_ul_pc, 0 0 2 3 4 0 1 678 4
4
2
chg_cell_element rxqual_dl_ho, 0 0 2 3 4 0 1 678 4
2
2
chg_cell_element rxqual_dl_pc, 0 0 2 3 4 0 1 678 4
2
2
chg_cell_element rxqual_ul_ho, 0 0 2 3 4 0 1 678 4
2
2
chg_cell_element rxqual_ul_pc, 0 0 2 3 4 0 1 678 4
2
2
chg_element max_number_of_sdcchs 32 4 cell_number = 2 3 4 0 1 678 4
chg_element interfer_bands,0 0 4 cell_number = 2 3 4 0 1 678 4
equip 4 btp
0 # BTP id
equip 4 msi
0 # MSI id
0 # MCU card frame where NIU exists
0 # NIU slot number
3 # NIU
equip 4 comb
0 # Comb id
0 # Comb address
2006 Motorola, Inc.
June 2007
BTS - 1.9.0.0 Script Files Version 1 Rev 3
equip 4 eas
0 # EAS id
0 0 0 0 # o/p relay initial settings
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 # i/p opto no alarm condition
1 2 3 4 5 6 7 8 # Reported opto state changes
0 # user dened alarm index
1
2
3
4
5
6
7
equip 4 dri
0 0 # 1st and 2nd DRI id
0 # Cab id
fox # Connection to BTP made by fox
0 # Port to which TCU connected
# 1st and 2nd rtf id (optional for equipment sharing only)
2 3 4 0 1 678 4 # Cell id
1 # Antenna select number
yes # Tunable combining used
2 # DRI controlling the combiner
0 # Comb id
0 # Cavity used by this TCU
1 # Diversity enabled
4 # Full diversity
equip 4 dri
0 1
0
fox
1
2 3 4 0 1 678 4
1
yes
0
1
1
4
equip 4 dri
0 2
0
fox
2
2 3 4 0 1 678 4
1
yes
1
0
2
1
4
chg_element rf_res_ind_period 20 4 # Int meas trans to CRM every 10s
chg_element tch_busy_norm_threshold 85 4 # CRM normal ow control set 85%
chg_element tch_busy_critical_threshold 95 4 # CRM critical ow control set 95%
Note:
The MMS priority and gclk_sync enable are not shown. These commands can be part of the PATH
statement.
2006 Motorola, Inc.
5-11
June 2007
Version 1 Rev 3 Battery Conservation, Mains Power Failure
Battery Conservation, Mains Power Failure
Overview
If an external battery back-up supply is available in the case of mains failure, this feature will extend
that battery supplies life by deactivating a specied number of carriers. Mains failure will be detected
by one of the input sensors on the PIX card. The input to be used can be specied in the database
command equip <location> eas. The text string associated with such an alarm cannot be specied
by the customer and is preset as EAS has detected main Power Failure'. Two chg_element commands
further control this feature:
carrier_disable_time
When a mains power failure has occurred the EAS will inform the CA which will wait this period before
disabling the rst carrier. The CA will also wait this period in between disabling subsequent carriers.
carriers_ins_pwr_fail
This number of carriers will always remain in service despite a mains power failure.
Note:
This feature is of no use at an M-Cellmicro, M-Cellarena and Horizonmicro site.
2006 Motorola, Inc.
June 2007
Battery Conservation, Mains Power Failure Version 1 Rev 3
Battery Conservation, Mains Power Failure
BATTERY
MAINS
FAILURE
SENSOR
MAINS
PIX
BTS 6
+27v
chg_element carrier_disable_time <*> <SITE NUMBER>
* 120 - 65535 seconds (default = 120)
chg_element carriers_ins_pwr_fail <*> <SITE NUMBER>
* 0 - 30 carriers (default = 0)
2006 Motorola, Inc.
5-13
June 2007
Version 1 Rev 3 Base Transceiver Processor (BTP)
Base Transceiver Processor (BTP)
The BTP is the master processor at a BTS. Its load and functionality is dependant upon the BTS type, at
the smallest BTS it will carry out all the processing required. As more processing power is required at a
site software entities will appear in multiple instances on other designated processors. To equip a BTP
the following command must be used:
equip <site number> BTP
Prompts
1st prompt (identier/card frame)
This prompt gives the BTP its unique identier, a maximum of two BTPs can be equipped at any one
site, the second being redundant. In M-Cell /Horizon products this prompt identies the card frame in
which the MCU is being equipped. In the case of M-Cell this prompt must be answered 0 rst in the CM.
0 is the valid entry for M-Cellmicro. If the BTP is being equipped in an Horizon IImacro cabinet, it points
to the Horizon2 Site Controller (H2SC) acting as the BTP
2nd prompt (cage)
This identies the cage in which the BTP is to be equipped. Not prompted for M-Cell / Horizon products.
3rd prompt (slot)
Valid slot ranges are 20/24 for cage 15 and 20 for cage 14. Not prompted for M-Cell / Horizon products.
4th prompt (DRIMs)
This prompt species the maximum number of DRIMs that the CA will allow the BTP to support. Not
prompted for M-Cell / Horizon products. At an In-cell BTS a value of 0 is only allowed if the BTS is a type
1
2006 Motorola, Inc.
June 2007
Base Transceiver Processor (BTP) Version 1 Rev 3
equip <site number> BTP
enter the BTP identifier: 0/1 (In-Cell)
0/1 (card frame, M-Cell/Horizon)
0/1 (H2SC HorizonIImacro)
0 (H2SC HorizonIImini/HorizonIImicro)
enter the cage number: 15/14
20/24 (cage 15)
20 (cage 14)
enter the maximum DRIMs
supported by this BTP:
06
2006 Motorola, Inc.
5-15
June 2007
Version 1 Rev 3 Digital Host Processor (DHP)
Digital Host Processor (DHP)
Prompts
The DHP will be required to support one instance of the RSS function at a BTS type 1. This device
cannot be equipped at an M-Cell / Horizon site.
equip <site number> DHP
1st prompt (cage)
This prompt acts as the 1st identier for the DHP and denes the cage where the DHP is tted.
2nd prompt (identier)
This prompt gives the DHP its unique identier in the specied cage.
3rd prompt (slot)
Valid slot ranges are 18-25.
4th prompt (DRIMs)
This prompt species the maximum number of DRIMs that the CA will allow the DHP to support.
2006 Motorola, Inc.
June 2007
Digital Host Processor (DHP) Version 1 Rev 3
Digital Host Processor (DHP)
equip <site number> DHP
enter the cage number for this DHP:
015
enter the unique DHP number in the cage:

07

1825
enter the maximum number of DRIMs

supported by this DHP:
16
SYS02_Ch4_34
2006 Motorola, Inc.
5-17
June 2007
Version 1 Rev 3 Digital Radio Interface
Digital Radio Interface
In-Cell, M-Cell and Horizon systems hardware differs at the Digital Radio Interface. In-Cell systems
utilises the DRIM, DRIX and DRCU/SCU combination, M-Cell utilises the Transceiver Control Unit (TCU)
and possibly the FOX and FMUX, Horizon uses the CTU and possibly the FOX and FMUX , were as
Horizon IImacro and Horizon IImini and Horizon IImicro will use the CTU2 with H2SC (integrated FMUX)
combination and maybe an XMUX. This difference is reected in the equip (site) dri command.
It should also be remembered that backward compatibility will allow equipment to be mixed from different
platforms, although there are limitations.
The DRIM provides the interface between the digital and RF domains. It performs the following function:
1. Logical to physical channel mapping.
2. Interleaving/deinterleaving
3. Channel coding/decoding
4. Base band hopping
5. Encryption function
6. Supports control/signalling between processor and DRCU
2006 Motorola, Inc.
June 2007
Digital Radio Interface Version 1 Rev 3
Digital Radio Interface
Logical to physical channel mapping
Interleaving/ de-interleaving
Channel coding/decoding
Base band hopping
Encryption
Interfaces control/signalling
SYS02_Ch4_16
2006 Motorola, Inc.
5-19
June 2007
Version 1 Rev 3 Digital Radio Interface - In-Cell
Digital Radio Interface - In-Cell
Prompts
Redundancy Group
Current software provides RTF\DRIM redundancy. In order for this feature to function correctly DRIMs
belonging to the same cell (connected to the same antenna) are grouped together using this rst
identier called the redundancy group. If an RTF is functioning on a DRIM\DRCU that goes faulty, it
will automatically move to a DRIM\DRCU that is redundant (if present), this move will only take place
if the rst identier (redundancy group) of the faulty DRIM\DRCU is the same as the spare\redundant
DRIM\DRCU. This rst identier is also matched by that of the RTF. If it is the BCCH RTF that is
functioning on a DRIM\DRCU that goes faulty, this RTF will move to a DRIM\DRCU in the same
redundancy group (unless the cell has only one carrier) replacing a non-BCCH RTF if necessary. The
second identier uniquely identies the DRIM within its redundancy group.
cabinet id
This eld identies the cabinet in which the DRIM is tted. Range 0-15.
DRIM type
This eld identies the DRIM type in use. For an In-Cell system the only allowable response is 0 or the
text string drim'.
Cage
This identies the cage in which the DRIM is tted. This prompt is only presented if the DRI board type
is DRIM.
Slot
This eld identies the card slot number in which the DRIM is tted. This prompt is only presented if the
DRI board type is DRIM.
TRU id
This parameter is only necessary when equipping a DRIM in a Topcell Data Unit (TDU). It is optional and
can be replaced by a carriage return or alternatively a zero, for non TDU cages. The range available is
0-6, to identify up to 6 TRU's. This prompt will only be presented if the DRI board type is DRIM.
2006 Motorola, Inc.
June 2007
Digital Radio Interface - In-Cell Version 1 Rev 3
SYS02_Ch4_17
D
R
C
U
D
R
C
U
D
R
C
U
D
R
C
U
D
R
C
U
D
R
C
U
0 2 0 1 0 0
1 1
1 0
2 0
equip <site number > DRI
enter the first and second DRI id: (0
5) (0
11)
enter the cabinet identifier 015
enter the DRI board type: DRIM (or integer code 0)
enter the cage number: BTS 152
enter the slot number (7, 9, 11, 13, 15, 17)
enter the TRU identifier: (06)
2006 Motorola, Inc.
5-21
June 2007
Version 1 Rev 3 Digital Radio Interface - In-Cell
RTF Identier
An RTF contains the frequency information for a particular cell and is equipped as a function after the
DRIM. This rst part of the identier determines which group of RTFs that the DRIM must use to obtain
its frequency information. A DRIM belonging to a particular redundancy group will automatically use an
RTF from the same group, and therefore, this eld is optional. The second part of the eld completes
the RTF identication and identies a particular RTF within a group of RTFs. RTFs are identied in an
identical way to the DRIMs.
This prompt is optional and a value should only be added if equipment sharing (future feature) is
implemented.
Cell id
This prompt requires the cell identity or the cell name that the DRIM is serving.
Antenna id
This parameter is used to engage the correct bay level offset tables calibrated by the eld engineer when
the radio was commissioned. These calibrations are usually stored in the 1st antenna memory area and
hence this eld is normally set to 1.
Diversity ag
This eld species the use of diversity within the radio.A value of 2 cannot be used with InCell
Tuneable Combining
This prompt determines whether the DRI utilises a combining device (RTCor CCB) or not. The responses
are yes or no.
Combiner Type
If the previous prompt declared that the DRI uses a tunable combining device, this prompt appears. It
denes whether no combining is used, or whether the combining is in controlled or non-controlled mode.
0 = none (This is used as a modify command to change the controlling DRI without unequipping it.)
1 = non-controlling
2 = controlling
Combiner id
This optional parameter nominates the Combiner (e.g. RTC) being used by the DRIM. The response
consists of a single combiner device number between 0 and 13. The combiner may be controlled by two
DRIs.
Cavity Number
If the 'Combiner id' above has been entered the MMI will prompt for the cavity number. Each RTC has 5
cavities (0 - 4) clearly labelled in hardware. The cavity in use by this DRIM/DRCU should be entered in
this eld.
fm_cell_type
The eld will nominate which receive coaxial connectors are in use in the diversity summation. This
feature is not supported at present.
Only certain combinations of the above two ags may be congured, they can be seen in the table
opposite.
When a DRCU is not in diversity mode the bottom connector (branch 1) should be used as the coaxial
input, fm_cell_type can be set to a 0, 1 or 2; in all cases the input to this connector will be processed.
2006 Motorola, Inc.
June 2007
Digital Radio Interface - In-Cell Version 1 Rev 3
16
0 diversity disabled
1 diversity enabled

0 non-diversity mode
4
non-
RCU
DRCU
DRCU
0
0
1
0
0 (non diversity)
4 (full diversity)
fm_cell_type
RCU
DRCU
DRCU
0
0
1
0
0 (non diversity)
4 (full diversity)
fm_cell_type
Yes/No
0, 1 or 2
0 13
0 5
(05) (011)
enter the first and second RTF ID:
enter the GSM cell ID where the DRI appears:
enter antenna select number for this cell:
does the DRI use tunable combining:
enter the tunable combining type:
enter the COMB identifier:
enter the cavity number for this COMB:
enter diversity flag for this DRI:
enter the fm_cell_type:
full diversity
GSM cell ID / name
Diversity flag
2006 Motorola, Inc.
5-23
June 2007
Version 1 Rev 3 Digital Radio Interface - M-Cell/Horizon
Digital Radio Interface - M-Cell/Horizon
Prompts
Within an M-Cell/Horizon macro set up, the DRMis actually a TCU/CTU. Within Horizon IImacro, Horizon
IImini, and Horizon II micro, the DRIM is known as a CTU2 which can operate in single density or double
density mode. The CTU2 may also be tted into Horizonmacroequipment and operate in single/double
density mode or it may tted to an M-Cell 6 or M-Cell 2 cabinet if using the M-Cell CTU2 adaptor. Again
it may operate in single/double density mode
Redundancy Group
Current software provides RTF/TCU/CTU/CTU2 redundancy. In order for this feature to function
correctly DRIs belonging to the same cell (connected to the same antenna) are grouped together using
this rst identier called the redundancy group. If an RTF is functioning on a DRI that goes faulty, it
will automatically move to a radio that is redundant (if present), this move will only take place if the
rst identier (redundancy group) of the faulty DRI is the same as the spare/redundant DRI. This rst
identier is also matched by that of the RTF. If it is the BCCH RTF that is functioning on a DRI that goes
faulty, this RTF will move to a DRI in the same redundancy group (unless the cell has only one carrier)
replacing a non-BCCH RTF if necessary. The second identier uniquely identies the DRI within its
redundancy group.
Dri Density
This eld is only prompted for Horizon II macro/Ext, mini, Ext or Horizon macro/Ext or M-Cell 6/2 and
species whether the DRI will operate in Single or Double Density mode. If Double is selected, the
associated DRI prompt will appear.
A new selection has been added to enable EGPRS on both carriers A and B of a CTUIID. It is called
Capacity and is selected by entering the number 3 when prompted for the DRI Density
Associated DRI
This prompt will only appear if the DRI density is chosen as double. It species the DRI id that is
associated with the DRI being equipped, ie, the DRI that is psychically located with the carrier.
Auto equipping of the associated DRI
When a DRI is equipped as a double density DRI, the associated DRI will automatically be equipped. It
will inherit it characteristics from the main DRI apart from an RTF identier.
Cabinet id
This eld identies the cabinet in which the radio is tted. This entry will directly match that entered in
the equip cabinet command. If the cabinet id points to Horizonmacro/ext and the frequency is one
of DCS1800/PCS1900/GSM850 (tx_power_cap) must be set for a high power cell.
2006 Motorola, Inc.
June 2007
Digital Radio Interface - M-Cell/Horizon Version 1 Rev 3
enter the rst and second DRI id:
(05) (0 11)
enter the cabinet identi er:

015
Note: If using DCS1800/PC1900/GSM850 with HorizonMacro /Ext ensure
015
tx_power_cap =1
enter the density of the DRI:
1 or single
2 or double
enter the 2
nd
DRI id of the associated DRI:
(011)
equip < site number > DRI

SYS02_Ch4_19
3 or Capacity
2006 Motorola, Inc.
5-25
June 2007
BTP connection
The response to this and the next prompt will specify the method of connection to the BTP. A number
of alternatives exist for this eld dependent on the type of equipment. The rst, fox indicates that the
DRI is connected via one of the ports in the master card frame (the one supporting the MCU). Three
further alternatives exist to describe the fmux to fmux connection in the case of a remote cage. The
fmux specied being the one in the master cage, this directly correlates to the shelf map numbering. The
last alternative is direct, this indicates that the DRI is connected to one of the ports on the BTP front
panel and should only be used in the event of the equipment being Mcell 2. If the equipment is of any
of the Horizon Types then direct should also be entered. Text strings or integer codes can be entered in
response to this prompt. In the case of an M-Cellmicro, M-Cellcity, and M-Cellarena this prompt should
be answered with direct' or 4.
The response to this and the next prompt will specify the method of connection to the MCU. A number of
alternatives exist for this eld. The rst, fox' indicates that the TCU is connected via one of the fox ports
in the master card frame (the one supporting the MCU). Three further alternatives exist to describe the
fmux to fmux connection in the case of a remote cage. The fmux specied being the one in the master
cage, this directly correlates to the shelf map numbering. The last alternative is direct', this indicates
that the TCU/TCU is connected to one of the ports on the MCU front panel. Text strings or integer codes
can be entered in response to this prompt. In the case of an
XMUX
To use extension cabinets with an Horizon IImacro or Horizon II mini cabinet, the connections are made
by the XMUX. This card provides the multiplexing functions and ts into the cabinet Mico Cage. It should
be noted that it cannot be placed in any other cabinets, nor can an FMUX be placed within an Horizon
IImacro or an mini cabinet.
TCU/CTU/CTU2 Port
The MCU card has 6 optical interfaces, each one being physically numbered on the front panel. The
TCU being equipped may be connected to one of these ports, the number of the port is entered in this
eld. Again there is a direct correlation between the database entry and the front panel labelling. In an
M-Cell 6 cabinet the TCU would normally be connected to the FOX.
The port number entered here could also be referring to one of the 2 ports (0 and 1) on the front panel
of the MCU. For this to be the case the previous prompt must be entered as direct'.For an M-cell micro
TRX0 is referred to as port 0 and TRX1 is referred to as port 1.
When the Horizon IImacro dual band feature is used, a check will also be made to ensure that the cabinet
and supported frequencies for the cell are correct
The operator can modify the tcu_port parameter to a value no greater than 0 where the DRI is equipped
to a HorizonIImicro cabinet.
2006 Motorola, Inc.
June 2007
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
FOX
MCU
FMUX0
FMUX1
FMUX2
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
FOX
FMUX
Master Card Frame
1 KM
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
FOX
FMUX
enter the type of the connection to the TCU/CTU 0 or fox
1 or fmux0
2 or fmux1
3 or fmux2
4 or direct
enter the port to which the TCU is connected: 05

2006 Motorola, Inc.
5-27
June 2007
RTF Identier
An RTF contains the frequency information for a particular cell and is equipped as a function after the
DRI. This rst part of the identier determines which group of RTFs that the DRI must use to obtain its
frequency information. A DRI belonging to a particular redundancy group will automatically use an RTF
from the same group, and therefore, this eld is optional. The second part of the eld completes the RTF
identication and identies a particular RTF within a group of RTFs. RTFs are identied in an identical
way to the DRI.
This prompt is optional and a value should only be entered if equipment sharing (future feature) is
implemented.
Cell ID
This prompt requires the cell identity or the cell name that the DRI is serving
Antenna Identity M-Cell
This enables two different mechanisms to correctly operate within the receiver RF sub-system. Firstly,
this parameter points to the bay level offset antenna memory area to be engaged by the DRI. These
offsets will have been calibrated when the DRI hardware was initially commissioned.
The second use for this entry is only meaningful when an Integrated Antenna Distribution Unit (IADU) is
in use (M-cell6). This entry points to the DLNB connection point on the IADU which is to be connected
through to the TCU. The TCU will communicate this parameter to the IADU for the correct switch to be
enabled.
Shown opposite is a typical example of a 4/4/4 conguration. Given the antenna settings at the bottom
of the diagram, the internal switching of the IADU is shown. The third Diversity Low Noise Block (DLNB)
port on the IADU can be used to extend the receive signal to an IADU in a different cabinet, the internal
IADU connections to make the extension port effective are enabled by dip switch settings on the IADU
itself. Diversity connections can be seen as ghosted lines in the diagram.
Antenna Identity Horizon
For the Horizonmacro equipment, this number congures the 1800 Sectorized Universal Receive Filter
(SURF). If the receive antenna is connected to the Rx ANT 0A/0B in the cabinet supporting the CTU, set
the antenna_select number to 1. If the receive antenna is connected to the Rx ANT 1A/1B in the cabinet
supporting the CTU, set the antenna_select number to 2 If the receive antenna is connected to the Rx
ANT 2A/2B in the cabinet supporting the CTU, set the antenna_select number to 3.
If the receive antenna is connected to the Rx ANT 900 0A/0B in the cabinet supporting the CTU, the
antenna_select number must be set to 2.
A DRI can be equipped to a Horizon II micro where the antenna_select parameter is 1 or 2 only.
2006 Motorola, Inc.
June 2007
SYS02_Ch4_07
3
2
1 3
2
1
I
A
D
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
3 3 3 3 3 3 1 1 1 1 1 1
Antenna Select Number
D
L
N
B
2 1 0 2 1
0
0
Ant Sel No DLNB
1
2
3
0
1
2
Ant Sel No DLNB
1
2
3
0
1
2
enter the first and second RTF id: (05) (011)
enter the GSM cell id where the DRI appears: Cell id/cell name
enter the antenna select number of this cell: 13
2006 Motorola, Inc.
5-29
June 2007
Use of Tuneable Combiner/CTU
This parameter informs the system whether the DRI is using a tuneable combiner or not. This prompt will
not appear if DRI double density is specied, or the cabinet type is specied as Horizon IImacro Horizon
IImini.
Combiner Type
This optional parameter describes which type of combiner is in use. This species whether no combining
is used by this DRI (enter 0); or if combining is used whether this DRI is controlling the combiner (enter 1)
or not (enter 2). Up to two DRIs may exercise control over it, and up to 6 DRI in total may be connected.
0 = none (This is used as a modify command to change the controlling TCU/CTU without un-equipping
it.)
1 = non-controlling
2 = controlling
Combiner Identity
This parameter informs the system of the combiner number. The prompt is mandatory if a combiner has
been declared.
Cavity Number
Only if the combiner id (above) has been entered will the MMI prompt for the cavity number. Each CCB
has 3 cavities, each being physically numbered from right to left (0 - 5), this eld points to the cavity in
use by this DRI.
Diversity Flag
This eld species the use of diversity within the DRI. GSR8 allows for 4 branch diversity mode with
HorizonII Macro cabinets but only when the DRI density is set to single density mode and the cabinet
frequency_type is set to a single band
fm cell type
This eld will nominate which receive coaxial connectors are in use in the diversity summation. This
feature is not supported at present.
Only certain combinations of the above two ags may be congured, they can be seen in the table
opposite.
When a DRI is not in diversity mode the bottom connector (branch 1) should be used as the coaxial input,
fm_cell_type can be set to a 0, 1 or 2 in all cases the input to this connector will be processed.
2006 Motorola, Inc.
June 2007
RCU
TCU/CTU
TCU/CTU
0
0
1
0
0 (non diversity)
4 (full diversity)
Diversity flag fm_cell_type
RCU
TCU/CTU2
TCU/CTU2
0
1
2
0
4 (full diversity)
4 (full diversity)
Diversity flag fm_cell_type
Enter the fm_cell_type: (0 4) 0 non-diversity mode
4 full diversity
Yes / No
Enter the tuneable combining type: (0, 1 or 2)
(0 13)
0 = non-diversity mode
11 = 2 branch diversity mode
(0 5)
2 = 4 branch diversity mode
Does the DRI use tunable combining:
Enter the COMB identifier:
Enter the cavity number for this COMB:
Enter the diversity flag for this DRI:
2006 Motorola, Inc.
5-31
June 2007
Version 1 Rev 3 Remote Tuneable Combiner (RTC)
Remote Tuneable Combiner (RTC)
The equipage of the combiner creates a single device which may be controlled by 2 DRI devices, a rst
and second controlling DRI.
The combiner parameters, Combiner address, DRI combining type and cavity may also be modied after
equipage by the use of the modify_value command.
Note that a combiner may be connected to up to 6 /TCU/CTU devices, but only a maximum 2 of them
can be in a controlling mode.
An RTC may not be equipped to an Horizon IImacro/ext or an Horizon IImini/ext cabinet, regardless
of whether Single or Double Density DRIs are being used. If a CTU2 is tted to an HorizonMacro or
HorizonMacro_Ext cabinet, and the DRI is being used in Single Density mode, then the RTC may be
equipped. If the DRI is to be used in Double Density mode, an RTC may not be used. The same rule
will apply to M-cell 6 / 2 if the CTU2 adaptor is being used. This can be seen in the chart opposite
The Combiner is equipped by the following commands:
equip<site number>COMB
prompt 1 (identier)
This rst prompt uniquely identies the TCB within the site. Range is 0 - 13.
prompt 2 (address)
This eld provides the TCB address, which must be equal to the hardware address straps on the TCB
itself. Essentially all TCBs at the same site could have the same address, the only use for this address
is when one TCU is controlling two TCBs, this may be the case in equipment sharing (a future feature).
2006 Motorola, Inc.
June 2007
Remote Tuneable Combiner (RTC) Version 1 Rev 3
Remote Tuneable Combiner (RTC)
No Yes Yes HorizonMacro&
HorizonMacro_Ext
No Yes N/A M-Cell 6 & M-Cell 2
(with CTU2 adaptor)
N/A N/A N/A HorionIImacro &
HorizonIImacro_Ext
HorionIImini &
HorizonIImini_Ext
CTU2 Double
Density
CTU2 Single Density CTU
No Yes Yes HorizonMacro&
HorizonMacro_Ext
No Yes N/A M-Cell 6 & M-Cell 2
(with CTU2 adaptor)
N/A N/A N/A HorionIImacro &
HorizonIImacro_Ext
HorionIImini &
HorizonIImini_Ext
CTU2 Double
Density
CTU2 Single Density CTU
RTC - Horizon equipment / DRI allowed combinations
SYS02_Ch4_22
Combiner
ID
DRI 0 0 DRI 0 1
Controlling
DRI
Standby
DRI
equip <site number> COMB
enter first combiner identifier: 0-13
enter combiner address:
0-255
2006 Motorola, Inc.
5-33
June 2007
Version 1 Rev 3 M-Cell/Horizon
M-Cell/Horizon
MSI Equipage
Identier
Valid identiers are dependent on the equipment at the site. Only identier 0 is valid at an
M-Cellmicro/M-Cellcity.
Card frame
Two card frames exist in an M-Cell and Horizon equipment and hence the identies are 0 and 1. However
only identier 0 is valid at an M-Cellmicro/M-Cellcity.
Slot
This eld identies the card slot in which the NIU is tted. 0 is the only possible value for M-Cell2 and
M-Cellmicro/M-Cellcity.
Type
This optional eld states what type of module is used, NIU, NIU with integrated HDSL modem, NIU with
external HDSL modem.
Protocol type MMS 0
This eld only appears if the integrated MSI HDSL feature is enabled and the msi_type is niu_hdsl,
niu_ext_hdsl or msi_ext_hdsl.
Timeslots supported on MMS 0
This prompt only appears if the integrated MSI HDSL feature is enabled and the msi_type is niu_hdsl,
Modem setting on MMS 0
This prompt only appears if the integrated MSI HDSL feature is enabled and the msi_type is niu_hdsl.
Protocol type MMS 1
This eld only appears if the integrated MSI HDSL feature is enabled and the msi_type is niu_hdsl,
Timeslots supported on MMS 1
This prompt only appears if the integrated MSI HDSL feature is enabled and the msi_type is niu_hdsl,
Modem setting on MMS 1
This prompt only appears if the integrated MSI HDSL feature is enabled and the msi_type is niu_hdsl.
Horizon II macro
It is not possible to equip an MSI with Horizon IImacro or Horizon IImini. One MSI is automatically
equipped when the BTP is equipped, as are the 3 MMSs associated with it.
2006 Motorola, Inc.
June 2007
M-Cell/Horizon Version 1 Rev 3
M-Cell/Horizon
M-Cell/Horizon
equip < site number > MSI
enter the MSI identifier 01 M-Cell2
03 M-Cell6/Horizonmacro
0 M-Cellmicro/M-Cellcity
-
-
- -
enter the MCU card frame in which the NIU exists: 01
enter the slot number: 01
enter the MSI type: NIU (default)
9 = niu_ext_hdsl
3 = niu
8 = niu_hdsl
9 = niu_ext_hdsl
M-Cell2
M-Cell6
M-Cellcity
Horizonmicro
3 = niu
9 =
- 2
-
-
-
-
enter the MMS 0 protocol type: E1 or HDSL
enter the MMS 0 modem setting: Master or slave
enter MMS 1 modem setting: Master or slave
1 MSI & 3 MMSs are auto equipped at HorizonIImacro &
HorizonIImini sites when the BTP is equipped
SYS02_Ch4_43
2006 Motorola, Inc.
5-35
June 2007
Version 1 Rev 3 Stop BTS transmitting when cell OOS
Stop BTS transmitting when cell OOS
Overview
This feature will allow the operator to dene a time period, after which the BTS will stop transmitting when
the cell transits to OOS. In addition the BTS will start to retransmit when the cell returns to in-service.
By stopping the cell transmitting when it has gone OOS, it will help reduce the amount of interference in
the network.
Enabling the feature
The feature may be enabled or disabled on a BSS basis by use of the database parameter
stop_dri_tx_enablebut can only be changed when in Sysgen mode. The operator, once the feature
is enabled can then specify the time between the cell transiting to OOS and the BTS ceasing to transmit.
This is carried out by use of the database parameter stop_dri_tx_time and may be performed on
a cell basis
2006 Motorola, Inc.
June 2007
Stop BTS transmitting when cell OOS Version 1 Rev 3
Stop BTS transmitting when cell OOS
stop_dri_tx_enable <*> site number
* 0 1
0 = Stop Tx when cell OSS feature disabled (default)
1 = Stop Tx when cell OSS feature enabled
stop_dri_tx_time <*> site number
* 0 1800 seconds
Default = 0
2006 Motorola, Inc.
5-37
June 2007
Version 1 Rev 3 Stop BTS transmitting when cell OOS
2006 Motorola, Inc.
June 2007
Database Building Exercise Version 1 Rev 3
Chapter 6
Database Building Exercise
2006 Motorola, Inc.
6-1
June 2007
Version 1 Rev 3 Database Building Exercise
2006 Motorola, Inc.
June 2007
Objectives
On completion of this chapter the student should be able to:
Write a database for a complete BSS including three BTS sites in a closed loop.
2006 Motorola, Inc.
6-3
June 2007
Version 1 Rev 3 Practical Database Building Exercise
Practical Database Building Exercise
This exercise will test the students knowledge and understanding of the rst and present database
courses. The exercise itself centres around the GSM entities of a mini training network.
To complete the exercise use a PC and write the scripts using Notepad or similar. You will be supplied
with a disc containing les where each script is to be built. These les will have the extension .STU and
within each le are timer values and MMS thresholds to help quicken the script writing process.
An answer script for each GSM entity is available from your instructor, it is advisable to check your
answers before moving onto the next script.
2006 Motorola, Inc.
June 2007
Practical Database Building Exercise Version 1 Rev 3
Practical Database Building Exercise
Network Connectivity
MSC
RXCDR
BSS 1
BTS
SITE3
BTS
SITE1
BTS
SITE2
BTS
SITE4
BSS2
MORE
BTSs
BTS
SITE6
BTS
SITE5
M Cell arena
2006 Motorola, Inc.
6-5
June 2007
Version 1 Rev 3 Remote Transcoder Script
Remote Transcoder Script
The rst task in this database building exercise is to produce a transcoder script for this mini network.
The necessary terrestrial connectivity needed to complete this part of the exercise is shown over the next
few pages. The Remote Transcoder is connected to an MSC and 2 BSSs, numbered 1 & 2.
Only one cage is present at the RXCDR, it is tted into a BSSC cabinet (DAB), its layout is specied in the
diagrams that follow, use this when equipping the necessary devices. All devices have to be equipped,
numbering should follow the normal Motorola convention using the shelf map.
2006 Motorola, Inc.
June 2007
Remote Transcoder Script Version 1 Rev 3
Remote Transcoder Connectivity
MSC
GDP GDP GDP
RXCDR 101
MSI MSI
MSI MSI
BSS 1
BSS 2
2006 Motorola, Inc.
6-7
June 2007
BSS 1 Terrestrial Connectivity
MSI 8
MSI 1
R
X
C
D
R
BSS1
Port 0
Port 1
18 TFC CCTS
1 MTL (TS16)
OML (TS1)
XBL (TS25)
1 CBL (TS8)
18 TFC CCTS
1 MTL/BSC 1 (TS16)
GDP 23
M
S
I

10
MSC
OMC
X.25
OML/RXCDR (TS1)
OML/BSC1 (TS2)
OML/BSC2 (TS3)
Port 0
1
1
2006 Motorola, Inc.
June 2007
BSS 2 Terrestrial Connectivity
Port 0
MSC
GDP 22
MSI 10
MSI 1
R
X
C
D
R
BSS2
Port 1
GDP 21
MSI 8
5 TFC CCTS
8 TFC CCTS
1 MTL/BSC 2 (TS 16)
Port 0
Port 0 Port 1
1 XBL (TS15)
5 TFC CCTS
8 TFC CCTS
1 OML (TS1)
1 MTL (TS16)
1 CBL (TS8)
CBC
X.25
CBL/BSC1 (TS1)
CBL/BSC2 (TS2)
M
S
I
6
2006 Motorola, Inc.
6-9
June 2007
LAPD Timers
Use the following LAPD timers for the XBLs.
T200 Timer: 2500 ms
N200: 3
K: 7
DSP Options
Downlink DTX may be in use by each BSS connected to this RXCDR. The MSC will employ a quietone
of 84.
Trafc Circuits
auto-connect mode should be used to connect trafc circuits
Enable GCLK synchronisation to the MSC. MMS 23 0 should be set to the highest priority, MMS 22 0
and MMS 21 0 should be equal but lower than MMS 23 0. The system should wait up to 4 minutes on a
span that has gone OOS before re-selecting to another synchronisation source. The delimiting time for
the OOS counter should be set to 24 hours. The lta alarm range should be set to 10.
GPROC
A gproc3 board is tted and requires 32 timeslots on the TDM highway.
AMR
AMR, AMR half rate and GSM half rate will not be used with this system.
GPRS/EGPRS
GPRS and EGPRS will not be used with this system.
2006 Motorola, Inc.
June 2007
RXU SHELF LAYOUT
G
P
R
O
C

0
G
D
P

3
G
D
P

2
G
D
P

1
X
C
D
R

1
6
X
C
D
R

1
4
X
C
D
R

1
8
M
S
I

6
M
S
I

8
M
S
I

1
0
M
S
I

2
1
M
S
I

2
2
M
S
I

2
3
2006 Motorola, Inc.
6-11
June 2007
Version 1 Rev 3 BSS Script
BSS Script
The second task in this exercise is to produce a BSS script, for BSS 1 only. The terrestrial connectivity
necessary to complete this exercise is shown opposite. The BSS is connected to two BTS chains, one
is a closed loop the other is open.
BSS1 comprises one digital shelf tted into a BSSC_DAB cabinet, its layout is included overleaf, all
boards need equipping using conventional numbering. One BSP and one CSFP need to be equipped,
the remainder of the GRPOCs being LCFs.
Trafc circuits should be equipped using the convention discussed in Section 1. The statistics interval
should be set to 60 minutes.
2006 Motorola, Inc.
June 2007
BSS Script Version 1 Rev 3
BSS Script
External Alarm Service
Six possible alarm strings are required for this BSS, the index number, severity and appropriate text
string are entered below.
Index Severity Text String
0 Major High Temperature
1 Major Low Temperature
2 Major Door Intruder Alarm
3 Major Burglar Alarm
4 Major Window Intruder Alarm
5 Critcal Mains failure Alarm
LAPD Timers
Similar LAPD timers should be used to those specied in the RXCDR script.
Encryption
All three available encryption algorithms have been loaded, their priority for use should be A5/1, A5/2
then A5/0.
Call Pre-emption
Both ECP and eMLPP should be enabled. Any call with a priority level of less than 10 will be exempt
form congestion mechanisms etc.
Enhanced Full Rate
EFR to be enabled, handover_required_sp_ver_used must be enabled.
Point to Point SMS
Point to Point SMS should be enabled for this BSS.
GCLK synchronisation should be enabled. As far as necessary, parameters should be set to the same
values as the RXCDR.
RSL overload
The RSL-LCF will be considered congested when 80%of its RSLs are congested. The level of congested
RSLs must fall to 20% before the RSL-LCF is not congested.
Overload messages will be sent to the msc at a rate of 1 per minute and alarms will be sent to the OMC-R
every 3 seconds
The number of pages that can be sent to the BTS from the BSS is to be 200 per second
Cell Broadcast Link
The operator names for the CBL should be:
BSS Operator : Sys03test
CBC Operator : CBCtest
The CBL should be processed by LCF 2 O O.
2006 Motorola, Inc.
6-13
June 2007
BSS Script
BSS Terrestrial Connectivity
MSI 1
MSI 2 MSI 3
M
S
I
4
GDP 23
MSI 8
BTS
SITE 4
BTS
SITE 5
BTS
SITE 6
BTS
SITE 3
BTS
SITE 1
RXCDR
MSC
spc= 33 (dec)
BSC 1
spc= 15 (dec)
PORT 0
PORT 0
CHAIN 2
CHAIN 1
PORT 0 PORT 0
BTS
SITE 2
PORT 1
2006 Motorola, Inc.
June 2007
BSS Script
LAPD Timers
Use the following LAPD timers for the XBLs.
T200 Timer: 2500 ms
N200: 3
K: 7
Trafc Circuits
auto-connect mode should be used to connect trafc circuits
GPROCs
In all cases gproc3 boards are tted and require 32 timeslots on the TDM highway.
2006 Motorola, Inc.
6-15
June 2007
BSS Script
BSU Shelf Layout - BSS 1
B
T
C

0
B
T
C

1
K
S
W
/
T
S
W

A
G
C
L
K

B
G
C
L
K

A
P
I
X

0
K
S
W
/
T
S
W

B
R
M
T
K
S
W
X

A
4
R
M
T
K
S
W
X

A
3
R
M
T
K
S
W
X

A
2
R
M
T
K
S
W
X

A
1
R
M
T
K
S
W
X

A
0
K
S
W
X

A
2
K
S
W
X

A
1
K
S
W
X

A
0
E
X
P
E
X
P
E
X
P
L
A
N
X

BK
S
W
X

B
0
K
S
W
X

B
1
E
X
P
E
X
P
K
S
W
X

B
2
E
X
P
R
M
T
K
S
W
X

B
0
R
M
T
K
S
W
X

B
1
R
M
T
K
S
W
X

B
2
s
p
a
r
e
G
P
R
O
C

7
M
S
I

0
M
S
I

1
M
S
I

2
M
S
I

3
M
S
I

4
G
D
P

0
G
D
P

1
G
D
P

2
G
D
P

3
G
D
P

4
C
L
K
X

B
0
C
L
K
X

B
1
C
L
K
X

A
0
C
L
K
X

A
1
C
L
K
X

A
2
C
L
K
X

B
2
R
M
T
K
S
W
X

B
3
R
M
T
K
S
W
X

B
4
K
S
W
X

A
K
S
W
X

B
L
C
L
L
C
L
U0
U1 U2 U3 U4 U5 U6 U7 U8 U9 U10 U11 U12 U13 U14 U15 U16 U17 U18 U19 U20 U21 U22 U23 U24 U25 U26 U27 U28
D
R
I
X
5
B
B
B
X

P
I
X
1
G
D
P

5
G
D
P

6
G
D
P

7
B
B
B
X

P
I
X
2
G
P
R
O
C

7
G
P
R
O
C

6
G
P
R
O
C

5
G
P
R
O
C

4
G
P
R
O
C

3
G
P
R
O
C

2
G
P
R
O
C

1
G
P
R
O
C

0
G
D
P

9
G
D
P

8
G
D
P

1
0
G
D
P

1
1
M
S
I

5
M
S
I

6
M
S
I

7
M
S
I

8
M
S
I

9
M
S
I

1
0
M
S
I

1
1
CARD FITTED
D
R
I
X

4
D
R
I
X

3
D
R
I
X

2
D
R
I
X

1
D
R
I
X

0
D
R
I
(
M
)

2
D
R
I
(
M
)

1
D
R
I
(
M
)

0
D
R
I
(
M
)

3
D
R
I
(
M
)

4
L
A
N
X

A
CARD NOT FITTED
D
R
I
(
M
)

5
2006 Motorola, Inc.
June 2007
BSS Script
RSL/MTL & Processor Distribution
L
C
F
B
S
P
L
C
F
1 0 0
MTL
CBL
RSL
BTS3
RSL
BTS2
RSL
BTS1
L20
RSL
BTS4
L
C
F
2
RSL
BTS5
RSL
BTS6
C
S
F
P
0
2006 Motorola, Inc.
6-17
June 2007
Version 1 Rev 3 BTS Scripts
BTS Scripts
The third task in this exercise is to produce a number of BTS scripts - one each for site's 1, 2 and 3.
The scripts for BTS sites 4, 5 and 6 do not have to be written. General information concerning all sites
is shown in the next couple of pages. Site specic information follows. The terrestrial connectivity for
these sites is shown opposite. To be consistent with the earlier sections of this exercise all tted cards
& equipment should be equipped.
2006 Motorola, Inc.
June 2007
BTS Scripts Version 1 Rev 3
BTS Scripts
BTS Terrestrial Connectivity Chain 1
MSI 2 MSI 3
RHINO 0
RHINO 0
MSI 0
MSI 0
BTS
SITE1
BTS
SITE 3
BSS 1
PORT 0 PORT 0
PORT 0
PORT 1
PORT 1
PORT 0
PORT 1
PORT 0
BTS
SITE2
N
I
U
0
N
I
U
0
2006 Motorola, Inc.
6-19
June 2007
Version 1 Rev 3 BTS Site 1 Specic (Horizon II Macro)
BTS Site 1 Specic (Horizon II Macro)
Equipment Shelves
The BTS cabinet being used is an Horizon II Macro with 2 x CTU2 working in double density within
GSM 900 frequencies. The cabinet layout diagram should provide enough information to equip all the
necessary devices.
2006 Motorola, Inc.
June 2007
BTS Site 1 Specic (Horizon II Macro) Version 1 Rev 3
BTS Site 1 Specic (Horizon II Macro)
Card Not Fitted Card Fitted
H
I
I
S
C
H
I
I
S
C
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
2006 Motorola, Inc.
6-21
June 2007
Version 1 Rev 3 BTS Site 2 Specic
BTS Site 2 Specic
M-Cell6
This site is using a GSM900 M-Cell6 cabinet.
It can be noted from the shelf layout a AB-6 card has been tted, the physically equipped sensors and
their inputs are shown below.
Sensor Usage Alarm Condition
1 High Temperature 1
2 Low Temperature 1
3 Burglar Alarm 0
All alarms must be reported, there are no relay outputs at this site.
2006 Motorola, Inc.
June 2007
BTS Site 2 Specic Version 1 Rev 3
BTS Site 2 Specic
BTS2 M-Cell6 Frame 0
M
C
U
F
O
X
N
I
U
0
N
I
U
1
F
M
U
X
0
F
M
U
X
1
B
P
S
M
F
M
U
X
2
Card Fitted
Card Not fitted
2006 Motorola, Inc.
6-23
June 2007
BTS Site 2 Specic
RF Shelf Layout - BTS 2
IADU
FOX
0 1 2 3
T
C
U
T
C
U
T
C
U
T
C
U
Cell 38
RxAnt 1 RxAnt 1
Cell 37
RxAnt 2
Cell 36
RxAnt 3
FREQ -
C85
C80 C75 C70
IADU - Internal Antenna Distribution Unit
FOX - Fibre Optic extender
Note: The Tx path of Cell 38 is using a hybrid combiners.
(Redundancy
Group 2)
(Redundancy
Group 1)
(Redundancy
Group 0)
2006 Motorola, Inc.
June 2007
2006 Motorola, Inc.
6-25
June 2007
Version 1 Rev 3 BTS Site 3 Specic (micro-cell)
BTS Site 3 Specic (micro-cell)
M-Cellarena
This site is using a DCS1800 M-Cellarena.
2006 Motorola, Inc.
June 2007
BTS Site 3 Specic (micro-cell) Version 1 Rev 3
BTS Site 3 Specic (micro-cell)
BTS 3 M-Cellarena
Note: This is a two carrier M Cell arena that does not support
space diversity but does support synthesizer frequency
hopping (NOT to be enabled in this exercise)
DTRX MODULE
(INCORPORATING THE DUPLEXER AND
COMBINER/ISOLATOR MODULE)
AC DC POWER
SUPPLY MODULE
RDIS MODULE
ANTENNA
CONNECTOR
2006 Motorola, Inc.
6-27
June 2007
Version 1 Rev 3 BTS Site 3 Specic (micro-cell)
2006 Motorola, Inc.
June 2007
Answers Version 1 Rev 3
Chapter 7
Answers
2006 Motorola, Inc.
7-1
June 2007
Version 1 Rev 3 Answers
2006 Motorola, Inc.
June 2007
Answers
# BSC SITE (1 - 128)
# LOAD 1.8.0.0 (GSR8)
equip bsc bss
> 1
> no
equip bsc axcdr
> yes
> 4
freq_types_allowed 7
equip bsc cab
> 7
> 5
> 0
equip 0 cage
> 0
> 0
> cr
> cr
> 0
> yes
equip 0 cage
> 1
> 0
> cr
> 0
> 0
> no
chg_element bsc_type 2 0
chg_element gproc_slots 32 0
Fibre Connectors
DSWX DSWX
D
S
W
Cabinet 0 Cage 0 Cabinet 0 Cage 1
U24 U1
> 15
> 10
> yes
2
SYS02_ANS_01
2006 Motorola, Inc.
7-3
June 2007
Answers
#
BTS SITE 18
equip 0 SITE
>
> LCF
> 2
> 64
> no
equip 18 CAB
> 0
> 11
> 2
equip 18 CAB
> 1
> 13
> 4
# Load 1.8.0.0 (GSR8)
Sys02_ANS_05
18
2006 Motorola, Inc.
June 2007
Answers
XBL Connectivity Exercise Answers
add_conn 1 0 1 1 0
add_conn 1 1 11 1
add_conn 2 0 1 2 0
add_conn 2 1 1 2 1
add_conn 3 0 2 1 0
add_conn 3 1 2 1 1
add_conn 4 0 2 2 1
add_conn 5 0 3 1 1
add_conn 5 1 3 2 0
2006 Motorola, Inc.
7-5
June 2007
Answers
# BTS SITE 18
# LOAD 1.8.0.0 (GSR8 )

chg_element sync_time_oos100 18
chg_element sync_time_restore 50 18
chg_element remote_time_oos 100 18
chg_element remote_time_restore 50 18
chg_element sync_loss_oos 20 18
chg_element sync_loss_restore 50 18
chg_element sync_loss_daily 5 18
chg_element sync_loss_hourly 15 18
chg_element remote_loss_oos 20 18
chg_element remote_loss_restore 50 18
chg_element remote_loss_daily 5 18
chg_element remote_loss_hourly 15 18
chg_element slip_loss_oos 20 18
chg_element slip_loss_restore 600 18
chg_element slip_loss_daily 5 18
chg_element slip_loss_hourly 12 18
chg_element ber_loss_daily 6 18
chg_element ber_loss_hourly 4 18
SYS02_ANS_02
2006 Motorola, Inc.
June 2007
Answers
EAS Exercise
equip 32 EAS
0
15
16
0 1 0 0
0 0 0 1 0 0 0 0
1 2 3 4 5
0
1
2
3
4
0
0
0
0
equip 33 EAS
0
0 0 0 0
1 0 0 0 0 0 0 0 0 0 0 0 0
1 2
3
4
BSC Script
chg_eas_alarm 0 2 " Burglar Alarm"
chg_eas_alarm 1 2 " Smoke Alarm"
chg_eas_alarm 2 2 " Door Intruder"
chg_eas_alarm 3 2 " High Temperature"
chg_eas_alarm 4 2 " Low Temperature"
2006 Motorola, Inc.
7-7
June 2007
Answers
Path Equipage Exercise Answers
equip< 0 >PATH equip< 0 >P ATH
terminating site id 16 16
path id 1
BSC MSI id 3 0 3 0
Site id 14 14
upstream MSI id 1 0 1 0
downstream MSI id 1 1 3 0
Site id 15 16
upstream MSI id 0 0 3 0
downstream MSI id 1 0
Site id 16
upstream MSI id 1 0
0
SYS02_ANS_04
2006 Motorola, Inc.
June 2007
Answers
# Script for RXCDR Answers
# 1.9.0.0 (GSR 9)
equip 0 rxcdr
101
equip 0 abss
1
equip 0 abss
2
equip 0 CAB
0
5
equip 0 CAGE
0
0
0
yes
equip 0 KSW
0
0
0
no
equip 0 BSP
0
0
25
equip 0 GCLK
0
0
no
no
no
equip 0 MSI
6
0
6
0
equip 0 MSI
8
0
8
0
equip 0 MSI
10
0
10
0
equip 0 MSI
21
0
21
2
0
2006 Motorola, Inc.
7-9
June 2007
Answers
equip 0 MSI
22
0
22
2
0
equip 0 MSI
23
0
23
2
0
add_conn 8 1 1 1 0
add_conn 8 0 2 1 1
add_conn 10 1 2 1 0
equip 0 OML
0
10
0
1
# XBL to BSC 1
equip 0 XBL
1
0
64
8
1
25
2500
3
7
# XBL to BSC 2
equip 0 XBL
2
0
64
8
0
15
2500
3
7
# MTL/OML/CBL Descriptions
chg_ts_usage # MTL BSC 1
nail
0
23 0
16
8 1
16
1
chg_ts_usage # MTL BSC 2
nail
0
22 0
16
10 1
16
1
2006 Motorola, Inc.
June 2007
Answers
chg_ts_usage # OML BSC 1
nail
0
10 0
2
8 1
1
1
chg_ts_usage # OML BSC 2
nail
0
10 0
3
10 1
1
1
chg_ts_usage # CBL BSC 1
nail
0
6 0
1
8 1
8
1
chg_ts_usage # CBL BSC 2
nail
0
6 0
2
10 1
8
1
equip 0 CIC
1 to 15
1
8 1
2
0
23 0
1
equip 0 CIC
17 to 19
1
23 0
17
equip 0 CIC
33 to 40
2
22 0
1
equip 0 CIC
65 to 69
2
21 0
1
2006 Motorola, Inc.
7-11
June 2007
Answers
chg_element sync_time_oos 90 0
chg_element clk_src_fail_reset_period 24 0
chg_element wait_for_reselection 240 0
chg_element lta_alarm_range 10 0
chg_element phase_lock_gclk 1 0
chg_element dnlk_vad_dtx 1 0
chg_element msc_qt 84 0
# BSS No. 1 Answers
# 1.9.0.0 (GSR 9 )
equip 0 bss
1
no
equip 0 axcdr
101
yes
freq_type_allowed 5
equip bsc CAB
0
5
5
equip bsc CAGE
0
0
0
yes
chg_element bsc_type 1 0
2006 Motorola, Inc.
June 2007
Answers
chg_element sync_time_oos 90 0
equip bsc KSW
0
0
0
no
equip bsc KSW
0
1
0
no
equip bsc BSP
0
0
20
equip bsc CSFP
0
0
18
equip bsc GPROC
1
0
19
equip bsc GPROC
3
0
21
equip bsc GPROC
4
0
22
equip bsc LCF
0
0
0
equip bsc LCF
1
0
0
equip bsc LCF
2
1
1
chg_eas_alarm 0 2 "High Temperature"
chg_eas_alarm 1 2 "Low Temperature"
chg_eas_alarm 2 2 "Door Intruder Alarm"
chg_eas_alarm 3 2 "Burglar Alarm"
chg_eas_alarm 4 2 "Window Intruder Alarm"
equip bsc GCLK
0
0
2006 Motorola, Inc.
7-13
June 2007
Answers
no
no
no
equip bsc GCLK
1
0
no
no
no
equip bsc MSI
1
0
16
0
equip bsc MSI
2
0
15
0
equip bsc MSI
3
0
14
0
equip bsc MSI
4
0
13
0
add_conn 1 0 101 8 1
equip bsc CIC
1 to 15
101
equip bsc CIC
17 to 19
101
equip bsc MTL
0
1
1
0
16
equip bsc OML
0
1
0
1
equip bsc XBL
101
0
64
1
0
25
2500
3
7
2006 Motorola, Inc.
June 2007
Answers
equip bsc CBL
0
1
0
8
"sys03test"
"cbctest"
chg_element dpc 33 0
chg_element opc 15 0
chg_element ni 2 0
chg_element option_alg_a5_1 1 0
chg_element option_alg_a5_2 1 0
chg_a5_alg_pr 1 2 0
chg_element option_emergency_preempt 1 0
chg_element handover_required_sp_ver_used 1 0
chg_element efr_enabled 1 0
chg_element phase_lock_gclk 1 0
chg_element rsl_lcf_congestion_thi 80 bsc
chg_element rsl_lcf_congestion_tlow 20 bsc
chg_element msc_bss_overload_allowed 1 bsc
chg_element bss_overload_control 60000 bsc
chg_element rsl_congestion_alarm_timer 3000 bsc
chg_element max_pagenum_per_sec 200 bsc
# BTS Number 1 Answer Script
# 1.9.0.0 (GSR 9)
# Horizon II Macro BTS DATABASE BTS Site 1
# 2 CARRIER OMNI
equip 0 site
1
lcf
0
64
no
equip 1 cab
0
24
1
# MMS Thresholds defaulted
# Enter SMS options
2006 Motorola, Inc.
7-15
June 2007
Answers
chg_element sms_dl_allowed 1 1
chg_element sms_ul_allowed 1 1
chg_element sms_tch_chan 2 1
# sms_tch_channel defaults to 2
#Add cell parameter
add_cell 2 3 4 1 1 368 39 1
frequency_type = 1
bsic = 24
ccch_conf = 2
bs_ag_blks_res = 1
bs_pa_mfrms = 1
en_incom_ho = 1
ho_margin_def = 8
sdcch_ho = 0
sdcch_timer_ho = 1
mspwr_alg = 1
pwrc = 1
intave = 10
ms_p_con_ack = 2
bts_p_con_ack = 2
dyn_step_adj= 0
max_tx_bts = 0
max_tx_ms = 31
rxlev_min_def = 6
1
decision_1_n1 = 2
decision_1_n2 = 2
decision_1_n3 = 2
2006 Motorola, Inc.
June 2007
Answers
decision_1_n4 = 2
decision_1_n5 = 2
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_p1 = 1
decision_1_p2 = 1
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 1
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
alt_qual_proc = 0
l_rxqual_ul_p = 226
l_rxqual_dl_p = 226
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 400
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 2
full_pwr_ross = 1
dtx_required = 0
attach_detach = 0
ncc_of_plmn_allowed = 12
max_retran = 3
tx_integer = 12
penalty_time = 0
rapid_pwr_down = 1
2006 Motorola, Inc.
7-17
June 2007
Answers
rpd_trigger = 45
rpd_offset = 12
rpd_period = 2
equip 1 btp
0
equip 1 btp
0
# Equip the radios
equip 1 dri
0 0
2
1
0
0
0
2 3 4 1 1 368 39
1
1
4
equip 1 dri
0 2
2
3
0
0
1
2 3 4 1 1 368 39
1
1
4
# BTS Number 2 Answer Script
# This is an M_Cell6 Site
# 1.9.0.0 (GSR 9)
equip 0 SITE
2
LCF
1
64
no
equip 2 CAB
0
11
1
# MMS THRESHOLDS DEFAULTED
# SMS OPTIONS
2006 Motorola, Inc.
June 2007
Answers
add_cell 2 3 4 1 1 368 36 2
frequency_type = pgsm
bsic = 31
ccch_conf = 1
bs_ag_blks_res = 1
bs_pa_mfrms = 0
en_incom_ho = 1
ho_margin_def = 8
sdcch_ho = 0
sdcch_timer_ho = 1
mspwr_alg = 0
pwrc = 1
intave = 3
ms_p_con_ack = 2
bts_p_con_ack = 2
dyn_step_adj = 0
max_tx_bts = 6
max_tx_ms = 31
rxlev_min_def = 0
1
decision_1_n1 = 2
decision_1_n2 = 2
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 2
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
2006 Motorola, Inc.
7-19
June 2007
Answers
decision_1_p1 = 1
decision_1_p2 = 1
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 1
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
alt_qual_proc = 0
l_rxqual_ul_p = 1800
l_rxqual_dl_p = 1800
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 5
full_pwr_ross = 1
dtx_required = 2
attach_detach = 0
max_retran = 3
tx_integer = 12
penalty_time = 0
rapid_pwr_down = 0
rpd_trigger = 45
rpd_offset = 8
rpd_period = 2
add_cell 2 3 4 1 1 368 37 2
2006 Motorola, Inc.
June 2007
Answers
bsic = 29
ccch_conf = 1
bs_ag_blks_res = 1
bs_pa_mfrms = 0
en_incom_ho = 1
ho_margin_def = 8
sdcch_ho = 0
sdcch_timer_ho = 1
mspwr_alg = 0
pwrc = 1
intave = 3
ms_p_con_ack = 2
bts_p_con_ack = 2
dyn_step_adj = 0
max_tx_bts = 6
max_tx_ms = 31
rxlev_min_def = 0
1
decision_1_n1 = 2
decision_1_n2 = 2
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 2
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_p1 = 1
decision_1_p2 = 1
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 1
2006 Motorola, Inc.
7-21
June 2007
Answers
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
alt_qual_proc = 0
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 5
full_pwr_ross = 1
dtx_required = 2
attach_detach = 0
max_retran = 3
tx_integer = 12
penalty_time = 0
rapid_pwr_down = 0
rpd_trigger = 45
rpd_offset = 8
rpd_period = 2
add_cell 2 3 4 1 1 368 38 2
bsic = 26
ccch_conf = 1
bs_ag_blks_res = 1
2006 Motorola, Inc.
June 2007
Answers
bs_pa_mfrms = 0
en_incom_ho = 1
ho_margin_def = 8
sdcch_ho = 0
sdcch_timer_ho = 1
mspwr_alg = 0
pwrc = 1
intave = 3
ms_p_con_ack = 2
bts_p_con_ack = 2
dyn_step_adj = 0
max_tx_bts = 6
max_tx_ms = 31
rxlev_min_def = 0
1
decision_1_n1 = 2
decision_1_n2 = 2
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 2
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_p1 = 1
decision_1_p2 = 1
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 1
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
2006 Motorola, Inc.
7-23
June 2007
Answers
alt_qual_proc = 0
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 2
full_pwr_ross = 1
dtx_required = 2
attach_detach = 0
max_retran = 3
tx_integer = 12
penalty_time = 0
rapid_pwr_down = 0
rpd_trigger = 45
rpd_offset = 8
rpd_period = 2
# DEVICE\FUNCTION EQUIPAGE
equip 2 BTP
0
equip 2 MSI
0
0
0
equip 2 EAS
2006 Motorola, Inc.
June 2007
Answers
0
1 1 1 1
0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
1 2 3
1
2
4
equip 2 DRI
0 0
1
0
fox
0
2 3 4 1 1 368 36
3
1
4
equip 2 DRI
1 0
1
0
fox
1
2 3 4 1 1 368 37
2
1
4
equip 2 DRI
2 0
1
0
fox
2
2 3 4 1 1 368 38
1
1
4
equip 2 DRI
2 1
1
0
fox
3
2006 Motorola, Inc.
7-25
June 2007
Answers
2 3 4 1 1 368 38
1
1
4
# TIMERS DEFAULTED
chg_element tch_busy_norm_threshold 85 2
chg_element tch_busy_critical_threshold 95 2
chg_element rf_res_ind_period 20 2
# BTS Number 3 (M_Cellarena) Answer
# 1.9.0.0 (GSR 9)
equip 0 SITE
3
LCF
0
64
no
equip 3 CAB
0
16
4
# MMS THRESHOLDS DEFAULTED
# SMS OPTIONS
add_cell 2 3 4 1 1 368 40 3
frequency_type = 4
bsic = 22
ccch_conf = 1
bs_ag_blks_res = 1
bs_pa_mfrms = 0
en_incom_ho = 1
ho_margin_def = 8
sdcch_ho = 0
sdcch_timer_ho = 1
mspwr_alg = 0
2006 Motorola, Inc.
June 2007
Answers
pwrc = 1
intave = 3
ms_p_con_ack = 2
bts_p_con_ack = 2
dyn_step_adj = 0
max_tx_bts = 6
max_tx_ms = 30
rxlev_min_def = 0
1
decision_1_n1 = 2
decision_1_n2 = 2
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 2
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_p1 = 1
decision_1_p2 = 1
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 1
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
alt_qual_proc = 0
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
2006 Motorola, Inc.
7-27
June 2007
Answers
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 2
full_pwr_ross = 1
dtx_required = 2
attach_detach = 0
max_retran = 3
tx_integer = 12
penalty_time = 0
rapid_pwr_down = 1
rpd_trigger = 45
rpd_offset = 8
rpd_period = 2
# DEVICE\FUNCTION EQUIPAGE
equip 3 BTP
equip 3 MSI
0
0
0
equip 3 DRI
0 0
0
4
0
2 3 4 1 1 368 40
0
0
equip 3 DRI
0 1
0
4
1
2 3 4 1 1 368 40
0
0
# TIMERS DEFAULTED
2006 Motorola, Inc.
June 2007
Answers
chg_element tch_busy_norm_threshold 85 3
chg_element tch_busy_critical_threshold 95 3
chg_element rf_res_ind_period 20 3
2006 Motorola, Inc.
7-29
June 2007
2006 Motorola, Inc.
June 2007
Glossary Version 1 Rev 3
Chapter 8
Glossary
2006 Motorola, Inc.
8-1
June 2007
Version 1 Rev 3 Glossary
2006 Motorola, Inc.
June 2007
Glossary of technical terms Version 1 Rev 3
Glossary of technical terms
This Glossary of technical terms contains standard Motorola acronyms, abbreviations and numbers used
throughout the documentation set.
A Interface - AUTO
A Interface Interface between MSC and BSS. The interface is based on the
use of one or more E1/T1 digital links. The channels on these
links can be used for trafc or signalling.
A3 Authentication algorithm that produces SRES, using RAND and
Ki.
A38 A single algorithm performing the function of A3 and A8.
A5 Stream cipher algorithm, residing on an MS, that produces
ciphertext out of plaintext, using Kc.
A8 Ciphering key generating algorithm that produces Kc using
RAND and Ki.
AB See Access Burst.
Abis interface Interface between a remote BSC and BTS. Motorola offers
a GSM standard and a unique Motorola Abis interface. The
Motorola interface reduces the amount of message trafc and
thus the number of 2 Mbit/s lines required between BSC and BTS.
ABR Answer Bid Ratio. The ABR is the ratio of successful calls to total
number of calls. As a measure of effective calls, it reects the
performance of the total network
ac-dc PSM AC-DC Power Supply module.
ac
Alternating Current. In electricity, AC occurs when charge
carriers in a conductor or semiconductor periodically reverse their
direction of movement. Household utility current in most countries
is AC with a frequency of either 50 or 60 hertz (complete cycles
per second). The RF current in antennas and transmission lines
is another example of AC. An AC waveform can be sinusoidal,
square, or sawtooth-shaped. Some AC waveforms are irregular
or complicated. Square or sawtooth waves are produced by
certain types of electronic oscillators, and by a low-end UPS
when it is operating from its battery.
AC Access Class (C0 to C15).
AC Application Context.
ACC Automatic Congestion Control. A method by which congested
switches automatically communicate their congestion level to
other switches.
Access Burst The Access Burst is used by the MS to access the BTS. It carries
RACH uplink from the MS to the BTS to start a call.
ACCH Associated Control CHannel. Control information associated with
TCH or DCCH.
ACK, Ack ACKnowledgement.
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.
2006 Motorola, Inc.
8-3
June 2007
Version 1 Rev 3 Glossary of technical terms
ACPIM AC Power Interface Module. Used in M-Cell6 indoor ac BTS
equipment.
AC PSM AC Power Supply Module. Used in M-Cell6 BTS equipment.
ACSE Association Control Service Element. The ACSE is one of the
three Application Service Elements (ASE) which reside in the
application layer of the OSI protocol and act as an interface to
the lower layer protocols. It is used by applications to create a
title for identication. See also ASI and ROSE.
ACU Antenna Combining Unit.
A/D Analogue to Digital (converter). See ADC.
ADC ADministration Centre.
ADC Analogue to Digital Converter. A device that converts a signal
that is a function of a continuous variable into a representative
number sequence carrying equivalent information.
ADCCP Advanced Data Communications Control Protocol. A bit-oriented
data-link-layer (DL) protocol used to provide point-to-point and
point-to-multipoint transmission of data frames that contain
error-control information. Note: ADCCP closely resembles
high-level data link control (HDLC).
ADM ADMinistration processor.
ADMIN ADMINistration.
ADN Abbreviated Dialling Number. Abbreviated dialling is a telephone
service feature that (a) permits the user to dial fewer digits to
access a network than are required under the nominal numbering
plan, and (b) is limited to a subscriber-selected set of frequently
dialled numbers.
ADPCM Adaptive Differential Pulse Code Modulation. Differential
pulse-code modulation (DPCM) in which the prediction algorithm
is adjusted in accordance with specic characteristics of the input
signal.
AE Application Entity. The system-independent application activities
that are made available as application services to the application
agent.
AEC Acoustic Echo Control. In a system, the reduction of the power
level of an echo or the elimination of an echo.
AEF Additional Elementary Functions.
AET Active Events Table. Alarms and events are sent to the Events
Log in the GUI. Different operators will have different subscription
lists. All alarms and events are sent to the AET before they are
re-routed to different subscription lists.
AFC Automatic Frequency Control. A device or circuit that maintains
the frequency of an oscillator within the specied 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 specied manner as a function of a
specied 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.
2006 Motorola, Inc.
June 2007
AI Articial 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 insufcient or conicting
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 kbit/s (half-rate) and 22.8 kbit/s (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
organisation for fostering the development of technology
standards in the United States. ANSI works with industry groups
and is the U.S. member of ISO and the IEC. Long established
computer standards from ANSI include ASCII and SCSI.
Antenna A transmitter/receiver which converts electrical currents into RF
and vice versa. In GSM systems, transmits and receives RF
signals between the BTS and MS.
AoC Advice of Charge.
AoCC Advice of Charge Charging supplementary service.
AoCI Advice of Charge Information supplementary service.
AOC Automatic Output Control.
AP Application Process.
Application Layer See OSI RM. The Application Layer is the highest of seven
hierarchical layers. It interfaces directly to, and performs common
application services for, the application processes. It also issues
requests to the Presentation Layer. The common application
services provide semantic conversion between associated
application processes.
ARFCN Absolute Radio Frequency Channel Number. The GSM available
frequency is divided in two bands. Each band is divided into
200kHz slots called ARFCN. Each ARFCN is shared between 8
mobiles, each using it in turn. Each mobile uses the ARFCN
for one TS (Timeslot) and then waits for its turn to come around
again. A mobile has use of the ARFCN once per the TDMA
frame. The combination of a TS number and ARFCN is called a
physical channel.
ARQ Automatic Repeat-reQuest. Error control for data transmission in
which the receiver detects transmission errors in a message and
automatically requests a retransmission from the transmitter.
2006 Motorola, Inc.
8-5
June 2007
ARP Address Resolution Protocol. A Transmission Control Protocol
/ Internet Protocol (TCP/IP) protocol that dynamically binds a
Network Layer (NL) IP address to a Data Link Layer (DL) physical
hardware address, e.g., Ethernet address.
ASCE Association Control Service Element. An ASE which provides
an AP with the means to establish and control an association
with an AP in a remote NE. Maps directly onto the Presentation
layer (OMC).
ASCII American Standard Code for Information Interchange. ASCII is
a standard developed by ANSI to dene how computers write
and read characters. It is the most common format for text les
in computers and on the Internet. In an ASCII le, alphabetic,
numeric, and special characters are represented with a 7-binary
digit binary number. 128 possible characters are dened. UNIX
and DOS-based operating systems (except for Windows NT) use
ASCII for text les. 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 le from
one code to another.
ASE Application Service Element (OMC). A coherent set of integrated
functions to help accomplish application communication, e.g.,
within an application entity (AE).
ASE Application Specic Entity (TCAP).
ASN.1 Abstract Syntax Notation One. A formal notation used
for describing data transmitted by telecommunications
protocols, regardless of language implementation and physical
representation of these data, whatever the application, whether
complex or very simple.
ASP Alarm and Status Panel.
ASR Answer Seizure Ratio. The percentage of calls that are
completed successfully.
ATB All Trunks Busy. An equipment condition in which all trunks
(paths) in a given trunk group are busy.
Ater The interface between XCDR and BSC.
ATI Antenna Transceiver Interface.
ATM Asynchronous Transfer Mode. A high-speed multiplexing and
switching method utilising xed-length cells of 53 octets to
support multiple types of trafc.
ATT (ag) ATTach.
ATTS Automatic Trunk Testing Subsystem. Ensures the quality of
telephone lines by means of a series of tests. ATTS can be
initiated by either an operator command or by a command le,
which can be activated at a predetermined time.
AU Access Unit.
AUC Authentication Centre. A GSM network entity which provides the
functionality for verifying the identity of an MS when requested by
the system. Often a part of the HLR.
AUT(H) AUThentication.
AUTO AUTOmatic mode.
2006 Motorola, Inc.
June 2007
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 signalling
rate of a communication channel is measured. One baud is one
symbol (state transition or level-transition) per second. This
coincides with bits per second only for two-level modulation with
no framing or stop bits
BBBX Battery Backup Board.
BBH Base Band Hopping. Method of frequency hopping in which each
transceiver at the base station is tuned to a different frequency,
and the signal is switched to a different transceiver for each burst.
BCC Base station Colour Code. The BCC and the NCC are part of the
BSIC. The BCC comprises three bits in the range 000 to 111.
See also NCC and BSIC.
BCCH Broadcast Control CHannel. A GSM control channel used to
broadcast general information about a BTS site on a per cell or
sector basis.
BCD Binary Coded Decimal. The representation of a decimal digit by a
unique arrangement of no fewer than four binary digits.
BCF Base station Control Function. The GSM term for the digital
control circuitry which controls the BTS. In Motorola cell sites this
is a normally a BCU which includes DRI modules and is located
in the BTS cabinet.
B channel Bearer channel. Used in ISDN services to carry 64kbit/s of data,
when used at full capacity.
BCIE Bearer Capability Information Element. Specic GSM parameters
in the Setup message are mapped into a BCIE for signalling to
the network and within the PLMN. The BCIE is used to request a
bearer service (BS) from the network.
BCU Base station Control Unit. A functional entity of the BSS which
provides the base control function at a BTS site. The term no
longer applies to a type of shelf (see BSC and BSU).
BCUP Base Controller Unit Power.
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 coefcient
and a power of 10; for example, 25 erroneous bits out of 100,000
bits transmitted would be 25 out of 10
5
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 trafc load in a
given 24-hour period.
2006 Motorola, Inc.
8-7
June 2007
BHCA Busy Hour Call Attempt. A statistic based on call attempts that a
switch processes during a BH. See also BH.
BI Barring of all Incoming call supplementary service.
BIB Balanced-line Interconnect Board. Provides interface to 12
balanced (6-pair) 120 ohm (37-pin D-type connector) lines for 2
Mbit/s circuits. See also T43.
BIC-Roam Barring of all Incoming Calls when Roaming outside the Home
PLMN Country supplementary service.
Bi-directional neighbour See Reciprocal neighbour..
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 les 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 trafc channel. See also Full Rate.
BN Bit Number. Number which identies the position of a particular
bit period within a timeslot.
BPF Bandpass Filter. A lter that ideally passes all frequencies
between two non-zero nite 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 kb/s channels (B channels) and one clear 16 kb/s
channel (D channel). The interface is also referred to as 2B+D.
BS Base Station. See BSS.
BS Basic Service (group).
BS Bearer Service. A type of telecommunication service that
provides the capability for the transmission of signals between
user-network interfaces. The PLMN connection type used to
support a bearer service may be identical to that used to support
other types of telecommunication service.
BSC Base Station Controller. A network component in the GSM PLMN
which has the digital control function of controlling all BTSs. The
BSC can be located within a single BTS cabinet (forming a BSS)
but is more often located remotely and controls several BTSs
(see BCF, BCU, and BSU).
2006 Motorola, Inc.
June 2007
BSG Basic Service Group.
BSIC Base Transceiver Station Identity Code. Each cell has a BSIC. It
is a local colour code that allows a mobile station to distinguish
between different neighbouring base stations. The BSIC is an
octet, consisting of three bits for the Network Colour Code (NCC)
and three bits for the Base station Colour Code (BCC). The
remaining two bits are unused. See also NCC and BCC.
BSIC-NCELL BSIC of an adjacent cell.
BSP Base Site control Processor (at BSC).
BSN Backward Sequence Number. A eld 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 dened by the GSM 08
series of recommendations, as being the entity responsible for
communicating with MSs in a certain area. The radio equipment
of a BSS may cover one or more cells. A BSS may consist of one
or more base stations. If an internal interface is implemented
according to the GSM 08.5x series of recommendations, then the
BSS consists of one BSC and several BTSs.
BSSAP BSS Application Part (part of SS7) . Protocol for LAPD or
LAPB signalling links on the A-interface. Comprises DTAP
and BSSMAP messages. Supports message communication
between the MSC and BSS.
BSSC Base Station System Control cabinet. The cabinet which houses
one or two BSU shelves at a BSC or one or two RXU shelves at
a remote transcoder (RXCDR).
BSSMAP Base Station System Management Application Part (part of SS7).
Call processing protocol for A-interface messages exchanged
between the MSC and BSS. The BSS interprets these messages.
BSSOMAP BSS Operation and Maintenance Application Part (part of SS7).
BSU Base Station Unit shelf. The shelf which houses the digital
control modules for the BTS (part of BTS cabinet) or BSC (part
of BSSC cabinet).
BT British Telecom.
BT Bus Terminator. In order to avoid signal reections on the bus,
each bus segment has to be terminated at its physical beginning
and at its end with the characteristic impedance.
BTC Bus Terminator Card.
BTF Base Transceiver Function.
BTP Base Transceiver Processor (at BTS). One of the six basic task
groups within the GPROC.
2006 Motorola, Inc.
8-9
June 2007
BTS Base Transceiver Station. A network component in the GSM
PLMN which serves one cell, and is controlled by a BSC. The
BTS contains one or more Transceivers (TRXs).
Burst A period of modulated carrier less than one timeslot. The physical
content of a timeslot.
Byte A sequence of adjacent binary digits operated upon as a unit.
Generally consists of eight bits, usually presented in parallel. A
byte is usually the smallest addressable unit of information in a
data store or memory.
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 les 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 congured for
GPRS across PRPs. In the event of a PRP outage, this process
sends message(s) indicating that GPRS service is unavailable to
the appropriate CRM(s) for the cells that could not be moved to
an INS (IN Service) PRP.
CB Cell Broadcast. See CBSMS.
CB Circuit Breaker.
CBA Cell Broadcast Agent.
CBC Cell Broadcast Centre. The call processing centre for CBSMS
messages.
CBCH Cell Broadcast CHannel. The channel which is used to broadcast
messages to all MSs in a specic cell.
CBF Combining Bandpass Filter.
CBL Cell Broadcast Link. A bi-directional data link which allows
communications between the BSS and the CBC.
CBM Circuit Breaker Module.
CDMA Code-Division Multiple Access. CDMA is a digital cellular
technology that uses spread-spectrum techniques. Unlike
competing systems, such as GSM, that use TDM, CDMA does
not assign a specic frequency to each user. Instead, every
channel uses the full available spectrum. Individual conversations
are encoded with a pseudo-random digital sequence.
2006 Motorola, Inc.
June 2007
CBMI Cell Broadcast Message Identier.
CBS Cell Broadcast Service. See CBSMS.
CBSMS Cell Broadcast Short Message Service. CBSMS allows a number
of unacknowledged general messages to be broadcast to all MSs
within a particular region. The content may include information
such as local trafc conditions, the weather, the phone number of
the local taxi company, etc. The messages are sent from a CBC
via a BSC to a BTS and from there on a special cell broadcast
channel to the MSs. The CBC is considered as a node outside
the PLMN and can be connected to several BSCs. However, a
BSC is only connected to one CBC.
CBUS Clock Bus.
CC Connection Conrm. Part of SCCP network connectivity.
CC Country Code. A one to three digit number which specically
identies a country of the world that an international call is being
routed to (e.g., 1 = North America, 44 = United Kingdom).
CC Call Control. CC functions, such as number translations and
routeing, matrix path control, and allocation of outgoing trunks
are performed by the MSC.
CCB Cavity Combining Block, a three way RF combiner. There are
two types of CCB, CCB (Output) and CCB (Extension). These,
with up to two CCB Control cards, may comprise the TATI. The
second card may be used for redundancy.
CCBS Completion of Calls to Busy Subscriber supplementary service.
CCCH Common Control CHannels. A class of GSM control channels
used to control paging and grant access. Includes AGCH, PCH,
and RACH.
CCCH_GROUP Group of MSs in idle mode.
CCD Common Channel Distributor.
CCDSP Channel Coding Digital Signal Processor.
CCF Conditional Call Forwarding. See CFC.
CCH Control CHannel. Control channels are channels which carry
system management messages.
CCH Council for Communications Harmonization (referred to in GSM
Recommendations).
CCITT Comit Consultatif International Tlgraphique et Tlphonique.
This term has been superseded. See ITU-TSS.
CCM Current Call Meter.
CCP Capability/Conguration Parameter.
CCPE Control Channel Protocol Entity.
CCS Hundred call-seconds. A single call lasting one hundred seconds
is one CCS. Also, a measure of trafc load obtained by multiplying
the number of calls per hour by the average holding time per call
expressed in seconds, and dividing by 100. Often used in practice
to mean hundred call seconds per hour with per hour" implied;
as such, it is a measure of trafc intensity. See also erlang.
CCU Channel Codec Unit. The CCU performs the following functions:
Channel coding functions, including FEC and interleaving, Radio
channel measurement functions, including received quality level,
received signal level, and information related to timing advance
measurements.
2006 Motorola, Inc.
8-11
June 2007
Cct Circuit.
CDB Control Driver Board.
CDE Common Desktop Environment. Part of the SUN software
(crontab - cron job le).
CDR Call Detail Record. A record of voice or data SVCs, which
includes calling and called numbers, local and remote node
names, data and timestamp, elapsed time, and call failure class
elds. 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 identier.
CEIR Central Equipment Identity Register.
Cell By GSM denition, a cell is an RF coverage area. At an
omni-site, cell is synonymous with site; at a sectored site, cell is
synonymous with sector. This differs from analogue systems
where cell is taken to mean the same thing as site. (See below)
2006 Motorola, Inc.
June 2007
GSM Core Network
(MSC/GSN)
BSS
BSC
GSM/GPRS UTRAN
UMTS Core Network
(3G MSC/SGSN)
PCU
BTS BTS
Abis
Multi-RAT MS
Iub
Node B
RNS RNS
RNC
RNC
Node B
Iur
Iub
E-Interface
Gn-Interface
Um
Gb-Interface A-Interface Iu-Cs-Interface
Iu-Ps--Interface
Uu
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. Identies when discontinuity is
detected in a circuit. An alarm is generated and sent to the
OMC-R when the error count exceeds an operator specied
threshold. The alarm identies the RCI or CIC and the path
where the error is detected.
CF Conversion Facility.
CF Call Forwarding. A feature available to the mobile telephone
user whereby, after initiation of the feature by an authorised
subscriber, calls dialled to the mobile telephone of an authorised
subscriber will automatically be routed to the desired number.
See also CFC and CFU.
CF Control Function. CF performs the SGSN mobility management
functions and OA&M functions for the GSN module.
CFB Call Forwarding on mobile subscriber Busy supplementary
service. Service automatically redirects incoming calls for phone
busy situations.
CFC Call Forwarding Conditional supplementary service. Service
automatically redirects incoming calls for busy, no reply, or not
reachable situations. See also CFB, CFNRc, and CFNRy.
CFM Conguration Fault Management RSS process.
2006 Motorola, Inc.
8-13
June 2007
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.
CGF Charging Gateway Function.
Channel A means of one-way transmission. A dened sequence of
periods (for example, timeslots) in a TDMA system; a dened
frequency band in an FDMA system; a dened 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 Verication 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 identies a cell within a
location area.
CI CUG Index.
C/I Carrier to Interference ratio.
CIC Circuit Identity Code. The unique identier of the terrestrial
portion of a circuit path. A CIC is either a 64 kbit/s or 16 kbit/s
connection depending on whether a site has local or remote
transcoding. A CIC with local transcoding occupies a complete
E1/T1 timeslot. A 16 kbit/s CIC, at a site with remote transcoding,
occupies a sub-channel of an E1/T1 timeslot.
CIR, C/I Carrier to Interference Ratio. Indicates the received signal power
level relative to the interference power level.
Ciphertext Unintelligible data produced through the use of encipherment.
CKSN Ciphering Key Sequence Number.
CLI Calling Line Identity. The identity of the caller. See also CLIP
and CLIR.
CLIP Calling Line Identication Presentation supplementary service.
Allows the called party to identify the caller. See also CLIR.
CLIR Calling Line Identication 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 bre optic link that distributes
GCLK to boards in system (part of the BSS, etc).
2006 Motorola, Inc.
June 2007
CLM ConnectionLess Manager. Coordinates global control over
the BSS by handling of all connectionless messages (that is,
messages that are not directly concerned with a connected call).
This includes such messages as global resets, load limiting and
circuit blocking.
CLR CLeaR.
CM Conguration Management. Conguration management allows
the operator to perform network conguration tasks, and to
maintain all details of the network conguration at the OMC.
CM Connection Management. See CLM.
CM Connectionless Manager. See CLM.
CMD CoMmanD.
CMM Channel Mode Modify. Message sent to an MS to request a
channel mode change. When it has received the CMM message,
the MS changes the mode to the indicated channel and replies
with a Channel Mode Modify Acknowledge message indicating
the new channel mode.
CMIP Common Management Information Protocol. Protocol used for
communication over the OML.
CMISE Common Management Information Service Element. An ASE
which provides a means to transfer management information via
CMIP messages with another NE over an association established
by ASCE using ROSE (OMC).
CMR Cellular Manual Revision. Documentation updates.
CNG CalliNg tone.
Codec Coder/Decoder. A speech coding unit that converts speech into a
digital format for radio broadcast, and vice versa.
CODEX 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
neighbour cell. The coincident cell has a different frequency type,
but the same BSIC, as that of the neighbour cell.
COLI COnnected Line Identity. Identity of the connected line. See also
COLP and COLR.
Collocated Placed together; two or more items together in the same place.
Colour Code An 8-bit code assigned to a BTS to distinguish interfering signals
from another cell.
COLP COnnected Line Identication Presentation supplementary
service. Allows the calling party to identify the line identity of the
connected party. See also COLR.
COLR COnnected Line Identication Restriction supplementary service.
Allows the connected party to withhold its line identity from the
calling party. See also COLP.
COM Code Object Manager (software).
COM COMplete.
COMB Combiner. The purpose of a combiner in the BSS is to combine
transmitter outputs from the RCUs onto an antenna.
COMM, Comms COMMunications.
2006 Motorola, Inc.
8-15
June 2007
CommHub Communications Hub. Provides Ethernet switching and IP
routeing for the GSN complex local networking and GSN complex
E1 interfaces to the public data network.
CommsLink Communications Link. See also 2 Mbit/s link.
Compact PCI See cPCI.
CONF CONFerence circuit. Circuit used for multi-party conference calls.
CONFIG CONFIGuration Control Program.
Congestion Situation occurring when an element cannot receive all the
service it is requesting.
CONNACK CONNect ACKnowledgement. Part of the synchronization
process. After a connection has been established, the CONNACK
message indicates that trafc channels are available.
CP Call Processing. The CP process in the BTS controls the MS to
BSS to MS signalling link, MS originated and terminated calls
and inter-BSS and inter-BTS handovers.
cPCI Compact Peripheral Component Interconnect. A set of standards
that dene a common card cage, power supplies, and processor
boards.
CPGM CCCH Paging Manager. The CPGM processes the paging
messages sent from the SGSN to the BSC/BTS.
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 eld bit.
CR Carriage Return (RETURN).
CR Connection Request (Part of SCCP network connectivity). An
SCCP Connection Request message is sent from the BSS to the
MSC to establish a connection. See also CREF.
CRC Cyclic Redundancy Check (3 bit). An error-detection scheme that
(a) uses parity bits generated by polynomial encoding of digital
signals, (b) appends those parity bits to the digital signal, and
(c) uses decoding algorithms that detect errors in the received
digital signal.
CRE Call RE-establishment procedure. Procedure for re-establishing
a call in the event of a radio link failure.
CREF Connection REFused (Part of SCCP network connectivity). In
a number of operating circumstances, a CREF message may
be sent from the MSC to the BSS in response to a Connection
Request (CR).
CRM Cell Resource Manager. The CRM allocates and activates
timeslots and subchannels on the available carriers.
CRM Cell Resource Machine.
CRM-LS/HS Cellular Radio Modem-Low Speed/High Speed. Low speed
modem used to interwork 300 to 2400 bit/s data services under
V.22bis, V.23, or V.21 standards. High speed modem used to
interwork 1200 to 9600 bit/s data services under V.22bis, V.32,
or V.29/V.27ter/V.21 standards.
2006 Motorola, Inc.
June 2007
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 kbit/s 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 publicly available
communications network using circuit switched digital data
circuits.
CT Call Transfer supplementary service.
CT Channel Tester.
CT Channel Type.
CTP Call Trace Product (Tool). The CTP is designed to help operators
of GSM900 and DCS1800 communication networks tune and
optimize their systems. CTP allows Call Trace data to be
analysed and decoded.
CTP Control Terminal Port.
CTR Common Technical Regulation.
CTS Clear to Send. A handshake signal used with communication
links, especially RS232 or CCITT Rec. V.24, to indicate (to a
transmitter from a receiver) that transmission may proceed.
Generated in response to a request to send signal. See also RTS.
CTU Compact Transceiver Unit (M-Cellhorizon radio).
CUG Closed User Group supplementary service. A CUG is used
to control who can receive and/or place calls, by creating a
unique group. When a CUG is congured 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 Analogue (converter). See DAC.
DAB Distribution Alarm Board (in BTS6 cabinet).
2006 Motorola, Inc.
8-17
June 2007
DAC Digital to Analogue Converter. A device that converts an input
number sequence into a function of a continuous variable.
DACS Digital Access Cross-connect System. A data concentrator and
organizer for Tl / El based systems.
DAK Downlink Acknowledgement
DAN Digital ANnouncer (for recorded announcements on MSC).
DAS Data Acquisition System.
DAT Digital Audio Tape. Audio-recording and playback medium/format
that maintains a signal quality equal to that of the CD-ROM
medium/format.
DataGen Sysgen Builder System. A Motorola ofine BSS binary object
conguration tool.
Data Link Layer See OSI RM. This layer responds to service requests from the
Network Layer and issues service requests to the Physical Layer.
It provides the functional and procedural means to transfer data
between network entities and to detect and possibly correct
errors that may occur in the Physical Layer.
dB Decibel. A unit stating the logarithmic ratio between two numeric
quantities. See also dBm.
DB DataBase.
DB Dummy Burst (see Dummy burst).
DBA DataBase Administration/Database Administrator.
dBm A dB referenced to 1 milliwatt; 0 dBm equals one milliwatt.
DBMS DataBase Management System.
dc Direct Current. DC is the unidirectional ow 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 dened by the
RS-232-C specication that indicates that a device such as a
modem is on-line 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 conguration designated for computers. DCE
equipment can be connected to DTE equipment with a straight
cable, but to other DCE equipment only with a null modem cable.
DCF Data Communications Function.
DCF Duplexed Combining bandpass Filter. (Used in Horizonmacro).
D channel Data channel. Used in ISDN to perform call signalling and
connection setup functions. In some circumstances, the channel
can also be used to carry user data.
DCN Data Communications Network. A DCN connects Network
Elements with internal mediation functions or mediation devices
to the Operations Systems.
2006 Motorola, Inc.
June 2007
DC PSM DC Power Supply Module.
DCS1800 Digital Cellular System at 1800 MHz. A cellular phone network
using digital techniques similar to those used in GSM 900, but
operating on frequencies of 1710 - 1785 MHz (receive) and
1805 - 1880 MHz (transmit).
DDF Dual-stage Duplexed combining Filter. (Used in Horizonmacro).
The DDF is an integrated combiner, lter and duplexer.
DDS DataGen Data Store. Store area for DataGen input and output
les.
DDS Data Drive Storage.
DDS Direct Digital Synthesis. A technology for generating highly
accurate and frequency-agile (rapidly changeable frequency over
a wide range), low-distortion output waveforms.
DEQB Diversity Equalizer Board.
DET DETach.
DFE Decision Feedback Equalizer. A receiver component/function.
The DFE results in a very sharp Bit Error Rate (BER) threshold
by using error feedback.
DGT Data Gathering Tool. The DGT collects all the relevant data
relating to a specied problem and copies it to tape or le,
together with a problem description. The le 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 Identier. In frame-relay transmission
systems, 13-bit eld that denes the destination address of a
packet. The address is local on a link-by-link basis.
DLD Data Link Discriminator.
DLNB Diversity Low Noise Block.
DLS DownLink Segmentator. The DLS segments LLC frames into
RLC data blocks to be transmitted over the air interface.
DLSP Data Link Service Process. Handles messages for an OMP and
a shelf GPROC.
DLSP Digital Link Signalling Processor.
Dm Control channel (ISDN terminology applied to mobile service).
2006 Motorola, Inc.
8-19
June 2007
DMA Deferred Maintenance Alarm. An alarm report level; an
immediate or deferred response is required (see also PMA).
DMA Direct Memory Access. Transfer of data from a peripheral device,
such as a hard disk drive, into memory without that data passing
through the microprocessor. DMA transfers data into memory at
high speeds with no processor overhead.
DMR Digital Mobile Radio.
DMX Distributed Electronic Mobile Exchange (Motorola's networked
EMX family).
DN Directory Number.
DNIC Data Network Identier Code. In the CCITT International X.121
format, the rst four digits indicate the international data number,
the next three digits are the data country code, and the nal digit
is the network code.
DNS Domain Name Service. A service that translates from logical
domain or equipment names to IP addresses.
Downlink Physical link from the BTS towards the MS (BTS transmits, MS
receives).
DP Dial/Dialled Pulse. A dc pulse produced by an end instrument that
interrupts a steady current at a sequence and rate determined
by the selected digit and the operating characteristics of the
instrument.
DPC Destination Point Code. A part of the label in a signalling
message that uniquely identies, in a signalling network, the
(signalling) destination point of the message.
DPC Digital Processing and Control board.
DPCM Pulse-code modulation (PCM) in which an analog signal is
sampled and the difference between the actual value of each
sample and its predicted value, derived from the previous sample
or samples, is quantied and converted, by encoding, to a
digital signal. Note: There are several variations of differential
pulse-code modulation.
DPNSS Digital Private Network Signalling 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 a
integrated circuit.
DRC Data Rate Converter board. Provides data and protocol
conversion between PLMN and destination network for 8 circuits.
Part of IWF.
DRCU Diversity Radio Channel Unit. Contains transceiver, digital control
circuits, and power supply. Part of the BSS.
DRI Digital Radio Interface. Provides encoding/decoding and
encryption/decryption for radio channels. Part of BSS.
DRIM Digital Radio Interface extended Memory. A DRI with extra
memory.
2006 Motorola, Inc.
June 2007
DRIX DRI Extender half size board. Fibre optic link from DRI to BCU.
Part of the BSS.
DRX, DRx Discontinuous reception (mechanism). A means of saving battery
power (for example in hand-portable units) by periodically and
automatically switching the MS receiver on and off.
DS-1 Digital transmission System 1 (or Digital Signal level 1). Term
used to refer to the 1.44 Mbit/s (U.S.) or 2.108 Mbit/s (Europe)
digital signal carried on a T1 facility.
DS-2 German term for 2 Mbit/s line (PCM interface).
DSE Data Switching Exchange.
DSI Digital Speech Interpolation. A compression technique that relies
on the pauses between speech bursts to provide additional
compression. DSI enables users to gain an additional 2:1
compression on the average on their line.
DSO 64 kbit/s timeslot on an E1/T1.
DSP Digital Signal Processor. A specialized, programmable computer
processing unit that is able to perform high-speed mathematical
processing.
DSS1 Digital Subscriber Signalling No 1. N-ISDN user network interface
signalling.
DSSI Diversity Signal Strength Indication.
DTAP Direct Transfer Application Part (Part of SS7). Call processing
protocol for A-Interface messages exchanged directly between
the MSC and the mobile unit without interpretation by the BSS.
DTE Data Terminal Equipment. An end instrument that
converts user information into signals for transmission
or reconverts the received signals into user information.
Also, the RS232 conguration 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 Transer Mode.
DTMF Dual Tone Multi-Frequency. Multifrequency signalling in which
specied 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 ow control (RS232
Interface). A modem interface control signal sent from the DTE
to the modem, usually to indicate to the modem that the DTE is
ready to transmit data.
DTRX Dual Transceiver Module. (Radio used in Horizonmicro
(M-Cellarena) and Horizonmacro (M-Cellarena
macro
)).
2006 Motorola, Inc.
8-21
June 2007
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
dened sequence that carries no useful information. A dummy
burst lls 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 Mbit/s rate used by European
CEPT carrier to transmit 30 64 kbit/s digital channels for voice
or data calls, plus a 64 kbit/s signalling channel and a 64 kbit/s
channel for framing and maintenance.
E Interface Interface between MSC and MSC.
EA External Alarm. See EAS. Typical external alarms are: Door
open, High humidity, Low humidity, Fire, Intruder.
EAS External Alarm System. The EAS is responsible for the monitoring
of all customer-dened environmental alarms at a site. The
customer denes 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 oor, where Eb is the signal energy per bit
and No is the noise energy per hertz of noise bandwidth.
EBCG Elementary Basic Service Group.
EC Echo Canceller. Performs echo suppression for all voice circuits.
If cancellation does not take place, the PLMN subscriber hears
the voice signal as an echo, due to the total round-trip delay
introduced by the GSM system (typically 180 ms).
ECB Provides echo cancelling for telephone trunks for 30 channels
(EC).
ECID The Motorola European Cellular Infrastructure Division.
ECM Error Correction Mode. A facsimile mode, in which the sending
machine will attempt to send a partial page up to four times.
Ec/No Ratio of energy per modulating bit to the noise spectral density.
ECT Event Counting Tool. The ECT provides information about the
number and type of events and alarms generated throughout the
network. It extracts data from the event log les for specied
dates, allowing the user to generate reports on individual network
elements, groups of elements, or the whole network.
ECT Explicit Call Transfer supplementary service. ECT enables a
user to connect two other parties with which he is engaged in a
telephone call and leave the connection himself.
EDGE Enhanced Data-rates for Global Evolution.
EEL Electric Echo Loss.
2006 Motorola, Inc.
June 2007
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 - 915
MHz (receive) and 925 - 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 organised as follows: White List - IMEIs which are known
to have been assigned to valid MS equipment. Black List - IMEIs
which have been reported stolen or which are to be denied service
for some other reason. Grey List - IMEIs which have problems
(for example, faulty software). These are not, however, sufciently
signicant to warrant a black listing.
EIRP Effective Isotropically Radiated Power. The arithmetic product of
the power supplied to an antenna and its gain.
EIRP Equipment Identity Register Procedure.
EL Echo Loss.
EM Event Management. An OMC-R application. It provides a
centralised facility for reporting network-wide generated events
and alarms, and for monitoring the status of the Network.
EMC ElectroMagnetic Compatibility. The ability of systems, equipment,
and devices that utilize the electromagnetic spectrum to operate
in their intended operational environments without suffering
unacceptable degradation or causing unintentional degradation
because of electromagnetic radiation or response.
EMF Electro Motive Force. The rate at which energy is drawn from a
source that produces a ow of electricity in a circuit; expressed
in volts.
EMI Electro Magnetic Interference. Any electromagnetic disturbance
that interrupts, obstructs, or otherwise degrades or limits the
effective performance of electronics/electrical equipment.
eMLPP enhanced Multi-Level Precedence and Pre-emption service. This
service has two parts: precedence and pre-emption. Precedence
involves assigning a priority level to a call in combination with
fast call set-up. Pre-emption involves the seizing of resources,
which are in use by a call of a lower precedence, by a higher level
precedence call in the absence of idle resources. Pre-emption
can also involve the disconnection of an on-going call of lower
precedence to accept an incoming call of higher precedence.
EMMI Electrical Man Machine Interface.
EMX Electronic Mobile Exchange (Motorola's MSC family).
2006 Motorola, Inc.
8-23
June 2007
en bloc Fr. - all at once (a CCITT #7 Digital Transmission scheme);
En bloc sending means that digits are sent from one system to
another ~ (that is, all the digits for a given call are sent at the same
time as a group). ~ sending is the opposite of overlap sending.
A system using ~ sending will wait until it has collected all the
digits for a given call before it attempts to send digits to the next
system. All the digits are then sent as a group.
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 8 time slots
each with equalizing circuitry and a DSP.
EQCP Equalizer Control Processor.
EQDSP Equalizer Digitizer Signal Processor.
Equalization The process by which attenuation and/or phase shift is rendered
essentially constant over a band of frequencies, even though the
transmission medium or the equipment has losses that vary with
frequency.
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 trafc intensity dened 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 trafc unit (TU).
ERP Ear Reference Point. Facility for assessing handset and headset
acoustic responses.
ERP Effective Radiated Power. The power supplied to an antenna
multiplied by the antenna gain in a given direction.
ERR ERRor.
ESP Electro-static Point. Connection point on the equipment for an
anti-static wrist strap.
ESQL Embedded SQL (Structured Query Language). An RDBMS
programming interface language.
E-TACS Extended TACS (analogue cellular system, extended).
Ethernet A standard protocol (IEEE 802.3) for a 10 Mbit/s baseband local
area network (LAN) bus using carrier-sense multiple access
with collision detection (CSMA/CD) as the access method,
implemented at the Physical Layer in the OSI RM, establishing
the physical characteristics of a CSMA/CD network.
ETR ETSI Technical Report.
ETS European Telecommunication Standard.
2006 Motorola, Inc.
June 2007
ETSI European Telecommunications Standards Institute.
ETX End of Transmission.
EXEC Executive Process.
F Interface - Full Rate
F Interface Interface between MSC and EIR.
FA Fax Adaptor. Device which complements Group 3 facsimile
apparatus in order to be able to communicate over a GSM
PLMN.
FA Full Allocation.
FA Functional Area.
FAC Final Assembly Code.
FACCH Fast Associated Control Channel. A GSM dedicated control
channel which temporarily uses the TCH to perform high speed
transmissions, and carries control information after a call is set
up. See also SDCCH.
FACCH/F Fast Associated Control Channel/Full rate. See also Full Rate.
FACCH/H Fast Associated Control Channel/Half rate. See also Half Rate.
FB See Frequency correction burst.
FBM Flow control Buffer Management. FBM is a functional unit
residing on the PRP. It controls buffer capacity for each cell
and each mobile so that the incoming data from the SGSN
matches the air throughput.
FC-AL Fibre Channel Arbitrated Loop. A serial data transfer
architecture. FC-AL is designed for mass storage devices and
other peripheral devices that require very high bandwidth.
Using optical bre to connect devices, FC-AL supports
full-duplex data transfer rates of 100MBps.
FCCH Frequency Correction CHannel. A GSM broadcast control
channel which carries information for frequency correction of
the MS.
FCP Fault Collection Process. Part of the fault management process
in the BTS.
FCS Frame Check Sequence. The extra characters added to a
frame for error detection and correction.
FDM Frequency Division Multiplex. A multiplexing technique that
uses different frequencies to combine multiple streams of data
for transmission over a communications medium. FDM assigns
a discrete carrier frequency to each data stream and then
combines many modulated carrier frequencies for transmission.
FDMA Frequency Division Multiple Access. The use of frequency
division to provide multiple and simultaneous transmissions
to a single transponder.
FDN Fixed Dialling Number. The xed dialling feature limits dialling
from the MS to a pre-determined list maintained on the SIM
card. It can be used to limit calling to certain areas, exchanges
or full phone numbers.
FDP Fault Diagnostic Procedure.
2006 Motorola, Inc.
8-25
June 2007
FEC Forward Error Correction. Correction of transmission errors by
transmitting additional information with the original bit stream.
If an error is detected, the additional information is used to
recreate the original information.
FEP Front End Processor. An OMC-R device. The FEP is a driver
that stores data in its own database about all of the sites in the
system. All bursts from the sites are directed to the FEP. It can
also interrogate the sites and collect its data either manually or
automatically at pre-dened times.
FER Frame Erasure Ratio. The ratio of successfully decoded good
speech frames against unsuccessfully decoded bad frames.
FFS, FS For Further Study.
FH See Frequency Hopping.
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 acknowledgement
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 (lter type).
FK Foreign Key. A database column attribute; the foreign key
indicates an index into another table.
FM Fault Management (at OMC).
FM Frequency Modulation. Modulation in which the instantaneous
frequency of a sine wave carrier is caused to depart from
the centre frequency by an amount proportional to the
instantaneous value of the modulating signal.
FMIC Fault Management Initiated Clear. An alarm type. If an FMIC
alarm is received, the fault management software for the
network item clears the alarm when the problem is solved. See
also Intermittent and OIC.
FMUX Fibre optic MUltipleXer module.
FN Frame Number. Identies the position of a particular TDMA
frame within a hyperframe.
FOA First Ofce Application. A full functional verication of new
product(s) on a commercial system using accepted technology
and approved test plans.
FOX Fibre Optic eXtender board.
FR See Full Rate.
FR Frame Relay. An interface protocol for statistically
multiplexed packet-switched data communications in which
(a) variable-sized packets (frames) are used that completely
enclose the user packets they transport, and (b) transmission
rates are usually between 56 kb/s and 1.544 Mb/s (the T-1 rate).
Frame A set of consecutive Pulse Code Modulation (PCM) time slots
containing samples from all channels of a group, where the
position of each sample is identied by reference to a frame
alignment signal. Also, an information or signal structure which
allows a receiver to identify uniquely an information channel.
2006 Motorola, Inc.
June 2007
Frame Alignment The state in which the frame of the receiving equipment is
synchronized with respect to that of the received signal to
accomplish accurate data extraction.
FRU Field Replaceable Unit. A board, module, etc. which can be
easily replaced in the eld with a few simple tools.
Frequency Correction Period of RF carrier less than one timeslot whose modulation
bit stream allows frequency correction to be performed easily
within an MS burst.
Frequency Hopping The repeated switching of frequencies during radio transmission
according to a specied algorithm. Frequency hopping
improves capacity and quality in a highly loaded GSM network.
Multipath fading immunity can be increased by using different
frequencies and interference coming from neighbour cells
transmitting the same or adjacent frequencies can be reduced.
FS Frequency Synchronization. All BSS frequencies and timing
signals are synchronized to a high stability reference oscillator
in the BSS. This oscillator can free run or be synchronized to
the recovered clock signal from a selected E1/T1 serial link.
MSs lock to a reference contained in a synchronization burst
transmitted from the BTS site.
FSL Free Space Loss. The decrease in the strength of a radio
signal as it travels between a transmitter and receiver. The
FSL is a function of the frequency of the radio signal and the
distance the radio signal has travelled from the point source.
FSN Forward Sequence Number. See FIB.
FTAM File Transfer, Access, and Management. An ASE which
provides a means to transfer information from le to le. (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 les to and from another
computer over a TCP/IP network. Also the client program the
user executes to transfer les.
Full Rate Refers to the current capacity of a data channel on the GSM
air interface, that is, 8 simultaneous calls per carrier. See also
HR - Half Rate.
G Interface - GWY
G Interface Interface between VLR and VLR.
Gateway MSC An MSC that provides an entry point into the GSM PLMN
from another network or service. A gateway MSC is also an
interrogating node for incoming PLMN calls.
GB, Gbyte Gigabyte. 2
30
bytes = 1,073,741,824 bytes = 1024 megabytes.
GBIC Gigabit Interface Converter 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).
2006 Motorola, Inc.
8-27
June 2007
GCR Group Call Register. The register which holds information
about VGCS or VBS calls.
GDP Generic DSP Processor board. Interchangeable with the
XCDR board.
GDP E1 GDP board congured for E1 link usage.
GDP T1 GDP board congured for T1 link usage.
GDS GPRS Data Stream.
GGSN Gateway GPRS Support Node. The GGSN provides internet
working with external packet-switched networks.
GHz Giga-Hertz (10
9
).
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 Centre. See Gateway
MSC.
GMSK Gaussian Minimum Shift Keying. The modulation technique
used in GSM.
GND GrouND.
GOS Grade of Service. A trafc statistic dened as the percentage
of calls which have a Probability of Busy or Queueing Delay.
An alternative criterion is a maximum time for a percentage
of calls to wait in the busy queue before they are assigned a
voice channel.
GPA GSM PLMN Area.
GPC General Protocol Converter.
GPROC Generic Processor board. GSM generic processor board: a
68030 with 4 to 16 Mb RAM (part of BSS, BTS, BSC, IWF,
RXCDR).
GPROC2 Generic Processor board. GSM generic processor board: a
68040 with 32 Mb RAM (part of BSS, BTS, BSC, IWF, RXCDR).
{4354} 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 very efcient
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.
2006 Motorola, Inc.
June 2007
GSA GSM Service Area. The area in which an MS can be reached
by a xed subscriber, without the subscriber's knowledge of the
location of the MS. A GSA may include the areas served by
several GSM PLMNs.
GSA GSM System Area. The group of GSM PLMN areas accessible
by GSM MSs.
GSD GSM Systems Division.
GSL GPRS Signalling Link.
GSM Groupe Spcial Mobile (the committee).
GSM Global System for Mobile communications (the system).
GSM900 See PGSM.
GSM MS GSM Mobile Station.
GSM PLMN GSM Public Land Mobile Network.
GSM RF GSM Radio Frequency.
GSN GPRS Support Node. The combined functions provided by
the SGSN and GGSN.
GSN Complex A GSN Complex consists of an ISS Cluster, GGSN and SGSNs
connected to a single CommHub.
GSR GSM Software Release.
GT Global Title. A logical or virtual address used for routing SS7
messages using SCCP capabilities. To complete message
routing, a GT must be translated to a SS7 point code and
subsystem number.
GTM Gb Transmit Manager.
GTE Generic Table Editor. The Motorola procedure which allows
users to display and edit MCDF input les.
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) by means
of which users may enter commands.
GUI client A computer used to display a GUI from an OMC-R GUI
application which is being run on a GUI server.
GUI server A computer used to serve the OMC-R GUI application process
running locally (on its processor) to other computers (GUI
clients or other MMI processors).
GWM GateWay Manager.
GWY GateWaY (MSC/LR) interface to PSTN.
2006 Motorola, Inc.
8-29
June 2007
H Interface - Hyperframe
H Interface Interface between HLR and AUC.
H-M Human-Machine Terminals.
HAD, HAP HLR Authentication Distributor.
Half Rate Refers to a type of data channel that will double the current
GSM air interface capacity to 16 simultaneous calls per carrier
(see also FR - Full Rate).
HANDO, Handover HANDOver. The action of switching a call in progress from
one radio channel to another radio channel. Handover allows
established calls to continue by switching them to another
radio resource, as when an MS moves from one BTS area to
another. Handovers may take place between the following
GSM entities: timeslot, RF carrier, cell, BTS, BSS and MSC.
HCU Hybrid Combining Unit. (Used in Horizonmacro). Part of
the DDF, the HDU allows the outputs of three radios to be
combined into a single antenna.
HDLC High level Data Link Control. A link-level protocol used to
facilitate reliable point-to-point transmission of a data packet.
Note: A subset of HDLC, LAP-B, is the layer-two protocol for
CCITT Recommendation X.25.
HDSL High bit-rate Digital Subscriber Line. HDSL is a data
transmission mechanism which supports duplex high speed
digital communication (at E1 rates) on one or more unshielded
twisted pair lines.
HLC High Layer Compatibility. The HLC can carry information
dening the higher layer characteristics of a teleservice active
on the terminal.
HLR Home Location Register. The LR where the current location
and all subscriber parameters of an MS are permanently stored.
HMS Heat Management System. The system that provides
environmental control of the components inside the ExCell,
TopCell and M-Cell cabinets.
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 rst call.
HPLMN Home PLMN.
HR See Half Rate.
HS HandSet.
HSI/S High Speed Interface card.
HSM HLR Subscriber Management.
HSN Hopping Sequence Number. HSN is a index indicating the
specic 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.
2006 Motorola, Inc.
June 2007
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
sufciently broadband to be able to cover the GSM transmitter
frequency band. See also COMB.
Hybrid Transformer A circuit used in telephony to convert 2-wire operation
to 4-wire operation and vice versa. For example, every
land-line telephone contains a hybrid to separate earpiece and
mouthpiece audio and couple both into a 2-wire circuit that
connects the phone to the exchange.
Hyperframe 2048 superframes. The longest recurrent time period of the
frame structure.
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 identies 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 Modication. Function which allows the service mode
(speech, facsimile, data) to be changed during a call.
2006 Motorola, Inc.
8-31
June 2007
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 IDentication/IDentity/IDentier.
IDN Integrated Digital Network. A network that uses both digital
transmission and digital switching.
IDS Interface Design Specication.
IDS Informix Dynamic Server. The OMC-R relational database
management system.
IE Information Element. The part of a message that contains
conguration or signalling information.
IEC International Electrotechnical Commission. An international
standards and conformity assessment body for electrical,
electronic and related technologies.
IEEE Institute of Electrical and Electronic Engineers. A non-prot,
technical professional association.
IEI Information Element Identier. The identier eld 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 identies the MS as a piece or
assembly of equipment. The IMEI is sent by the MS 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 rst 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 specied channel.
IMSI International Mobile Subscriber Identity. Published mobile
number (prior to ISDN) that uniquely identies 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 exibly at a variety of nodes on and off the
network and allows the architecture to be modied to control
the services.
2006 Motorola, Inc.
June 2007
IN Interrogating Node. A switching node that interrogates an HLR,
to route a call for an MS to the visited MSC.
INS IN Service.
INS Intelligent Network Service. A service provided using the
capabilities of an intelligent network. See also IN.
InterAlg Interference Algorithm.
Intermittent Intermittent alarms are transient and not usually associated
with a serious fault condition. After the intermittent alarms are
displayed in the Alarm window, the operator must handle and
clear the alarm. The system will report every occurrence of an
intermittent alarm unless it is throttled. See also FMIC and OIC.
Interworking The general term used to describe the inter-operation of
networks, services, supplementary services and so on. See
also IWF.
Interval A recording period of time in which a statistic is pegged.
Interval expiry The end of an interval.
I/O Input/Output.
IOS Intelligent Optimization Service. Tool for improving the network
quality. The IOS generates reports based on performance data
from the BTS and OMC-R.
IP Initialisation Process. The IP is primarily responsible for
bringing up the site from a reset, including code loading
the site from a suitable code source. IP also provides the
CSFP functionality, allowing two BSS code load version to be
swapped very quickly, allowing the site to return to service as
soon as possible.
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 identied by
xed-length addresses. The internet protocol also provides for
fragmentation and reassembly of long datagrams, if necessary,
for transmission through small-packet networks. See also TCP
and TCP/IP.
IPC Inter-Process Communication. Exchange of data between one
process and another, either within the same computer or over
a network.
IP, INP INtermodulation Products. Distortion. A type of spurious
emission.
IPR Intellectual PRoperty.
IPSM Integrated Power Supply Module (-48 V).
IPX Internetwork Packet EXchange A networking protocol used by
the Novell NetWare operating systems. Like UDP/IP, IPX is a
datagram protocol used for connectionless communications.
Higher-level protocols are used for additional error recovery
services.
IR Incremental Redundancy (Hybrid Type II ARQ)
2006 Motorola, Inc.
8-33
June 2007
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 les stored on a
hard disk. While storing data sequentially, ISAM provides direct
access to specic records through an index. This combination
results in quick data access regardless of whether records are
being accessed sequentially or randomly.
ISC International Switching Centre. The ISC routes calls to/from
other countries.
ISDN Integrated Services Digital Network. A digital network using
common switches and digital transmission paths to establish
connections for various services such as telephony, data telex,
and facsimile. See also B channel and D channel.
ISG Motorola Information Systems group (formerly CODEX).
ISO International Organisation for Standardization. ISO is a
world-wide federation of national standards bodies from some
130 countries, one from each country.
ISQL An Interactive Structured Query Language client application for
the database server. See also IDS.
ISS Integrated Support Server. The ISS resides on a Sun Netra
t 1125 and performs the CGF, DNS, NTP, and NFS functions
for the GSN.
IST Integrated System Test.
ISUP ISDN User Part. An upper-layer application supported by
signalling system No. 7 for connection set up and tear down.
IT Inactivity Test (Part of SCCP network connectivity).
ITC Information Transfer Capability. A GSM Bearer Capability
Element which is provided on the Dm channel to support
Terminal adaptation function to Interworking control procedures.
ITU International Telecommunication Union. An intergovernmental
organization through which public and private organizations
develop telecommunications. It is responsible for adopting
international treaties, regulations and standards governing
telecommunications.
ITU-T International Telecommunication Union - Telecommunications
Standardization Sector. The standardization functions were
formerly performed by CCITT, a group within the ITU.
IWF InterWorking Function. A network functional entity which
provides network interworking, service interworking,
supplementary service interworking or signalling interworking.
It may be a part of one or more logical or physical entities in a
GSM PLMN.
IWMSC InterWorking MSC. MSC that is used to deliver data to/from
SGSN.
IWU InterWorking Unit. Unit where the digital to analogue (and visa
versa) conversion takes place within the digital GSM network.
2006 Motorola, Inc.
June 2007
k - KW
k kilo (10
3
).
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.
kbit/s, kbps kilo-bits per second.
kbyte kilobyte. 2
10
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. Fibre optic distribution of TDM
bus. Part of the BSS.
kW kilo-Watt.
L1 - LV
L1 Layer 1 (of a communications protocol).
L2ML Layer 2 Management Link. L2ML is used for transferring layer
2 management messages to TRX or BCF. One link per TRX
and BCF.
L2R Layer 2 Relay function. A function of an MS and IWF that
adapts a 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 an MS may move freely
without updating the location register. An LA may comprise one
or several base station areas.
LAC Location Area Code. The LAC is part of the LAI. It is an
operator dened code identifying the location area.
2006 Motorola, Inc.
8-35
June 2007
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 reect 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 specic user group,
(c) has a specic topology, and (d) is not a public switched
telecommunications network, but may be connected to one.
LANX LAN Extender half size board. Fibre optic distribution of LAN
to/from other cabinets. Part of BSS, etc.
LAPB Link Access Protocol Balanced. The balanced-mode,
enhanced version of HDLC. Used in X.25 packet-switching
networks.
LAPD Link Access Protocol D-channel (Data). A protocol that
operates at the data link layer (layer 2) of the OSI architecture.
LAPD is used to convey information between layer 3 entities
across the frame relay network. The D-channel carries
signalling information for circuit switching.
LAPDm Link Access Protocol on the Dm channel. A link access
procedure (layer 2) on the CCH for the digital mobile
communications system.
Layer 1 See OSI-RM and Physical Layer.
Layer 2 See OSI-RM and Data Link Layer.
Layer 3 See OSI-RM and Network Layer.
Layer 4 See OSI-RM and Transport Layer.
Layer 5 See OSI-RM and Session Layer.
Layer 6 See OSI-RM and Presentation Layer.
Layer 7 See OSI-RM and Application Layer.
LC Inductor Capacitor. A type of lter.
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 specied reference points q1 and q2. LCNs
range from the simple to the complex. LCN examples include
point-to-point connections and networks based on star and
bus topologies.
LCP Link Control Processor. An LCP is a GPROC or PCMCIA
board device which supplies the LCF. Once the LCF has been
equipped, and assuming GPROCs have been equipped,
processors are allocated by the software.
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
colour can be visible or infrared.
LF Line Feed. A code that moves the cursor on a display screen
down one line. In the ASCII character set, a line feed has
a decimal value of 10. On printers, a line feed advances the
paper one line.
2006 Motorola, Inc.
June 2007
LI Length Indicator. Delimits LLC PDUs within the RLC data
block, when an LLC PDU boundary occurs in the block.
LI Line Identity. The LI is made up of a number of information
units: the subscriber's national ISDN/MSISDN number; the
country code; optionally, subaddress information. In a full
ISDN environment, the line identity includes all of the address
information necessary to unambiguously identify a subscriber.
The calling line identity is the line identity of the calling party.
The connected line identity is the line identity of the connected
party.
LLC Logical Link Control.
LLC Lower Layer Compatibility. The LLC can carry information
dening the lower layer characteristics of the terminal.
Lm Trafc channel with capacity lower than a Bm.
LMP LAN Monitor Process. Each GPROC which is connected to a
LAN has an LMP, which detects faults on the LAN. LAN alarms
are generated by the GPROC.
LMS Least Mean Squares. Parameters determined by minimizing
the sum of squares of the deviations.
LMSI Local Mobile Station Identity. A unique identity temporarily
allocated to visiting mobile subscribers in order to speed up
the search for subscriber data in the VLR, when the MSRN
allocation is done on a per cell basis.
LMT Local Maintenance Terminal. Diagnostic tool, typically an IBM
compatible PC.
LNA Low Noise Amplier. An amplier with low noise characteristics.
LND Last Number Dialled.
Location area An area in which a mobile station may move freely without
updating the location register. A location area may comprise
one or several base station areas.
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 quantied 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 Signalling Unit (Part of MTP transport system).
LSTR Listener Side Tone Rating. A rating, expressed in dB, based
on how a listener will perceive the background noise picked
up by the microphone.
LTA Long Term Average. The value required in a BTS's GCLK
frequency register to produce a 16.384 MHz clock.
LTE Local Terminal Emulator.
LTP Long Term Predictive.
LTU Line Terminating Unit.
2006 Motorola, Inc.
8-37
June 2007
LU Local Units.
LU Location Update. A location update is initiated by the MS when
it detects that it has entered a new location area.
LV Length and Value.
M - MUX
M Mandatory.
M Mega (10
6
).
M-Cell Motorola Cell.
M&TS Maintenance and TroubleShooting. Functional area of Network
Management software which (1) collects and displays alarms,
(2) collects and displays Software/Hardware errors, and (3)
activates test diagnostics at the NEs (OMC).
MA Mobile Allocation. The radio frequency channels allocated to
an MS for use in its frequency hopping sequence.
MAC Medium Access Control. MAC includes the functions related
to the management of the common transmission resources.
These include the packet data physical channels and their
radio link connections. Two Medium Access Control modes are
supported in GSR5, dynamic allocation and xed allocation.
MACN Mobile Allocation Channel Number. See also MA.
Macrocell A cell in which the base station antenna is generally mounted
away from buildings or above rooftop level.
MAF Mobile Additional Function.
MAH Mobile Access Hunting supplementary service. An automatic
service which searches for the rst available mobile user out of
a dened 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 signalling between MSCs and LRs and EIRs.
MAPP Mobile Application Part Processor.
MB, Mbyte Megabyte. 2
20
bytes = 1,048,576 bytes = 1024 kilobytes.
Mbit/s Megabits per second.
MCAP Motorola Cellular Advanced Processor. The MCAP Bus is the
inter-GPROC communications channel in a BSC. Each card
cage in a BSC needs at least one GPROC designated as an
MCAP Server.
MCC Mobile Country Code. The rst three digits of the IMSI, used
to identify the country.
MCDF Motorola Customer Data Format used by DataGen for simple
data entry and retrieval.
2006 Motorola, Inc.
June 2007
MCI Malicious Call Identication 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.
MCSC Motorola Customer Support Centre.
MCU Main Control Unit for M-Cell2/6. Also referred to as the Micro
Control Unit in software.
MCUF Main Control Unit, with dual FMUX. (Used in M-Cellhorizon).
MCU-m Main Control Unit for M-Cellmicro sites (M-Cellm). Also referred
to as the Micro Control Unit in software.
MCUm The software subtype representation of the Field Replaceable
Unit (FRU) for the MCU-m.
MD Mediation Device. The MD (which handles the Q3 interface)
allows the OSI Processor to communicate between the
Network Management Centre (NMC) and OMC-R for network
conguration, events and alarms.
MDL mobile Management entity - Data Link layer.
ME Maintenance Entity (GSM Rec. 12.00).
ME Mobile Equipment. Equipment intended to access a set of GSM
PLMN and/or DCS telecommunication services, but which does
not contain subscriber related information. Services may be
accessed while the equipment, capable of surface movement
within the GSM system area, is in motion or during halts at
unspecied 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 identied by reference
to a multiframe alignment signal.
MF Multi-Frequency (tone signalling type). See DTMF.
MF MultiFunction block.
MGMT, mgmt Management.
MGR Manager.
MHS Message Handling System. The family of services and
protocols that provides the functions for global electronic-mail
transfer among local mail systems.
MHS Mobile Handling Service.
MHz Mega-Hertz (10
6
).
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 rooftop level. Radio wave propagation is by diffraction
and scattering around buildings, the main propagation is within
street canyons.
min minute(s).
2006 Motorola, Inc.
8-39
June 2007
s
micro-second (10
-6
).
BCU Micro Base Control Unit. The BCU is the Macro/Microcell
implementation of a BTS site controller.
MIT Management Information Tree. A le on the Motorola OMC-R.
The MIT le 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 le
on the OMC-R. The MIT le also contains the hierarchical
relationships between the network devices.
MM Man Machine. See MMI.
MM Mobility Management. MM functions include authorization,
location updating, IMSI attach/detach, periodic registration, ID
condentiality, paging, handover, etc.
MME Mobile Management Entity.
MMF Middle Man Funnel process.
MMI Man Machine Interface. The method by which the user
interfaces with the software to request a function or change
parameters. The MMI may run on a terminal at the OMC, or
an LMT. The MMI is used to display alarm reports, retrieve
device status, take modules out of service and put modules
into service.
MMI client A machine congured to use the OMC-R software from an MMI
server.
MMI processor MMI client/MMI server.
MMI server A computer which has its own local copy of the OMC-R
software. It can run the OMC-R software for MMI clients to
mount.
MML Man Machine Language. The tool of MMI.
MMS Multiple Serial Interface Link. (see also 2Mbit/s link)
MNC Mobile Network Code. The fourth, fth and optionally sixth
digits of the IMSI, used to identify the network.
MNT MaiNTenance.
Mobis Motorola Signalling 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 or not the MS is engaged in
a call.
MOMAP Motorola OMAP.
MoU Memorandum of Understanding. Commercial term. An MoU
usually sets out the broad parameters of an understanding as
well as the general responsibilities and obligations of each
party in a proposed venture. It has little legal signicance
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.
2006 Motorola, Inc.
June 2007
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, i.e. a simultaneous communication with
more than one party.
MPX MultiPleXed.
MRC Micro Radio Control Unit.
MRN Mobile Roaming Number.
MRP Mouth Reference Point. Facility for assessing handset and
headset acoustic responses.
MS Mobile Station. The GSM subscriber unit. A subscriber
handset, either mobile or portable, or other subscriber
equipment, such as facsimile machines, etc.
MSC Mobile-services Switching Centre, Mobile Switching Centre.
The MSC handles the call set up procedures and controls the
location registration and handover procedures for all except
inter-BTS, inter-cell and intra-cell handovers. MSC controlled
inter-BTS handovers can be set as an option at the switch.
MSCM Mobile Station Class Mark.
MSCU Mobile Station Control Unit.
msec
millisecond (.001 second).
MSI Multiple Serial Interface board. Intelligent interface to two 2
Mbit/s digital links. See 2 Mbit/s link and DS-2. Part of BSS.
MSIN Mobile Station Identication 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 denes the mobile station as
an ISDN terminal. It consists of three parts: the Country Code
(CC), the National Destination Code (NDC) and the Subscriber
Number (SN).
MSRN Mobile Station Roaming Number. A number assigned by the
MSC to service and track a visiting subscriber.
MSU Message Signal Unit (Part of MTP transport system). A signal
unit containing a service information octet and a signalling
information eld which is retransmitted by the signalling link
control, if it is received in error.
MT Mobile Terminated. Describes a call or short message destined
for an MS.
MT (0, 1, 2) Mobile Termination. The part of the MS which terminates the
radio transmission to and from the network and adapts terminal
equipment (TE) capabilities to those of the radio transmission.
MT0 is mobile termination with no support for terminal, MT1 is
mobile termination with support for an S-type interface and
MT2 is mobile termination with support for an R-type interface.
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.
2006 Motorola, Inc.
8-41
June 2007
MTL Message Transfer Link. The MTL is the 64 kbit/s PCM timeslot
that is used to convey the SS7 signalling information on the A
interface between the MSC and the BSC.
MTM Mobile-To-Mobile (call).
MTP Message Transfer Part. The part of a common-channel
signaling system that transfers signal messages and performs
associated functions, such as error control and signaling link
security.
MT/PP Mobile Terminated Point-to-Point messages. Transmission of a
short message from a message handling system to a mobile.
The maximum length of the message is 160 characters. The
message can be received whether or not the MS is engaged in
a call.
MTTR Mean Time To Repair. The total corrective maintenance time
divided by the total number of corrective maintenance actions
during a given period of time.
Multiframe Two types of multiframe are dened in the system: a 26-frame
multiframe with a period of 120 ms and a 51-frame multiframe
with a period of 3060/13 ms.
MU Mark Up.
MUMS Multi User Mobile Station.
MUX Multiplexer. A device that combines multiple inputs into an
aggregate signal to be transported via a single transmission
channel.
NACK - nW
NACK, Nack No Acknowledgement
N/W Network.
NB Normal Burst (see Normal burst).
NBIN A parameter in the frequency hopping sequence generation
algorithm.
NCC Network Colour Code. The NCC and the BCC are part of the
BSIC. The NCC comprises three bits in the range 000 to 111.
It is the same as the PLMN Colour Code. See also NCC and
BSIC.
NCELL Neighbouring (of current serving) Cell.
NCH Notication CHannel. Part of the downlink element of the
CCCH reserved for voice group and/or voice broad-cast calls
and notication messages.
NCRM Network Cell Reselection Manager.
ND No Duplicates. A database column attribute meaning the
column contains unique values (used only with indexed
columns).
NDC National Destination Code. Part of the MSISDN. An NDC is
allocated to each GSM PLMN.
2006 Motorola, Inc.
June 2007
NDUB Network Determined User Busy. An NDUB condition occurs
when a call is about to be offered and the maximum number of
total calls for the channel has been reached. In practice, the
total number of calls could be three: one for the basic call, one
for a held call and one for call waiting.
NE Network Element (Network Entity). A piece of
telecommunications equipment that provides support or
services to the user.
NEF Network Element Function block. A functional block that
communicates with a TMN for the purpose of being monitored,
or controlled, or both.
NET Norme Europennes de Telecommunications.
NetPlan An RF planning tool, NetPlan can import data from the OMC
and use it to carry out a network frequency replan.
Network Layer See OSI RM. The Network Layer responds to service requests
from the Transport Layer and issues service requests to the
Data Link Layer. It provides the functional and procedural
means of transferring variable length data sequences from
a source to a destination via one or more networks while
maintaining the quality of service requested by the Transport
Layer. The Network Layer performs network routing, ow
control, segmentation/desegmentation, and error control
functions.
NF Network Function.
NFS Network File System. A le system that is distributed over a
computer network. Also, a le system, on a single computer,
that contains the low-level networking les for an entire network.
NHA Network Health Analyst. The NHA is an optional feature. It
detects problems by monitoring network statistics and events
via the OMC-R. The NHA analyses the event history, statistics
and network conguration 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 centralised control of
network information for example hostnames, IP addresses and
passwords.
N-ISDN Narrowband Integrated Services Digital Network: Services
include basic rate interface (2B+D or BRI) and primary rate
interface (30B+D - Europe and 23B+D - North America or PRI).
Supports narrowband speeds at/or below 1.5 Mbps.
NIU Network Interface Unit. A device that performs interface
functions, such as code conversion, protocol conversion, and
buffering, required for communications to and from a network.
NIU-m Network Interface Unit, micro. M-Cellmicro MSI.
NL See Network Layer.
NLK Network LinK processor(s).
Nm Newton metres.
2006 Motorola, Inc.
8-43
June 2007
NM Network Management (manager). NM is all activities which
control, monitor and record the use and the performance of
resources of a telecommunications network in order to provide
telecommunication services to customers/users at a certain
level of quality.
NMASE Network Management Application Service Element.
NMC Network Management Centre. The NMC node of the GSM
TMN provides global and centralised GSM PLMN monitoring
and control, by being at the top of the TMN hierarchy and linked
to subordinate OMC nodes.
NMSI National Mobile Station Identication 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
rst automatic international mobile telephone system.
NN No Nulls. A database column attribute meaning the column
must contain a value in all rows.
Normal burst A period of modulated carrier less than a timeslot.
NPI Number Plan Identier.
NRZ Non Return to Zero. A code in which ones are represented by
one signicant condition and zeros are represented by another,
with no neutral or rest condition.
NSAP Network Service Access Point. An NSAP is a registration made
by an application which species its desired listening criteria.
The registration is limited to a particular CPU and port number.
Criteria can include: DNICs, national numbers, subaddress
ranges, protocol-ids, and extended addresses.
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 conguration and performance, and how the
different network management functions are implemented by
the OMC-R.
NST Network Service Test(er). A PCU process that periodically tests
all alive NS-VCs on a PICP board.
NS-VC Network Service - Virtual Circuit.
NT Network Termination. Network equipment that provides
functions necessary for network operation of ISDN access
protocols.
NT Non Transparent.
NTAAB NTRAC Type Approvals Advisory Board. Committee engaged
in harmonisation type approval of telecom terminals in Europe.
NTP Network Time Protocol. A protocol built on top of TCP/IP that
assures accurate local timekeeping with reference to radio,
atomic or other clocks located on the Internet. This protocol is
capable of synchronizing distributed clocks within milliseconds
over long time periods.
2006 Motorola, Inc.
June 2007
Numbers # - The symbol used for number.2 Mbit/s link - As used in
this manual set, the term applies to the European 4-wire
2.048 Mbit/s digital line or link which can carry 30 A-law PCM
channels or 120 16 kbit/s GSM channels.4GL - 4
th
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 Identication.
NUP National User Part. (part of SS7).
NV NonVolatile.
NVRAM Non-Volatile Random Access Memory. Static random access
memory which is made into non-volatile storage either by
having a battery permanently connected, or, by saving its
contents to EEPROM before turning the power off and
reloading it when power is restored.
nW Nano-Watt (10
-9
).
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&M Operation, Administration, & Management.
OAMP Operation, Administration, Maintenance, and Provisioning.
O&M Operations and Maintenance.
OASCU Off-Air-Call-Set-Up. The procedure in which a
telecommunication connection is being established whilst the
RF link between the MS and the BTS is not occupied.
OCB Outgoing Calls Barred within the CUG supplementary service.
An access restriction that prevents a CUG member from
placing calls to other members of that group.
OCXO Oven Controlled Crystal Oscillator. High stability clock source
used for frequency synchronization.
OD Optional for operators to implement for their aim.
OFL % OverFlow.
ofine IDS shutdown state.
online IDS normal operating state.
OIC Operator Initiated Clear. An alarm type. OIC alarms must be
cleared by the OMC-R operator after the fault condition that
caused the alarm is resolved. See also FMIC and Intermittent.
OLM Off_Line MIB. A Motorola DataGen database, used to modify
and carry out Radio Frequency planning on multiple BSS
binary les.
OLR Overall Loudness Rating.
OMAP Operations and Maintenance Application Part (part of SS7
standard) (was OAMP).
2006 Motorola, Inc.
8-45
June 2007
OMC Operations and Maintenance Centre. The OMC node of the
GSM TMN provides dynamic O&M monitoring and control of
the PLMN nodes operating in the geographical area controlled
by the specic OMC.
OMC-G Operations and Maintenance Centre - Gateway Part. (Iridium)
OMC-G Operations and Maintenance Centre - GPRS Part.
OMC-R Operations and Maintenance Centre - Radio Part.
OMC-S Operations and Maintenance Centre - Switch Part.
OMF Operations and Maintenance Function (at BSC).
OML Operations and Maintenance Link. The OML provides
communication between an OMC-R and a BSC or RXCDR for
transferring network management (O&M) data.
OMP Operation and Maintenance Processor. Part of the BSC.
OMS Operation and Maintenance System (BSC-OMC).
OMSS Operation and Maintenance SubSystem.
OOS Out Of Service. Identies a physical state. The OOS state
indicates the physical device is out of service. This state is
reserved for physical communication links. Also, identies a
telephony state. The OOS state is used by the BTS device
software to indicate that the BTS is completely out of service.
OPC Originating Point Code. A part of the label in a signalling
message that uniquely identies, in a signalling network, the
(signalling) 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.
Overlap Overlap sending means that digits are sent from one system to
another as soon as they are received by the sending system. A
system using ~ will not wait until it has received all digits of a
call before it starts to send the digits to the next system. This
is the opposite of en bloc sending where all digits for a given
call are sent at one time. See en bloc.
2006 Motorola, Inc.
June 2007
PA - PXPDN
P1, P2, P3 Puncturing Schemes 1, 2, and 3.
PA Power Amplier.
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 by means of
addressed packets so that a channel is occupied during the
transmission of the packet only, and upon completion of the
transmission the channel is made available for the transfer of
other trafc.
PAD Packet Assembler/Disassembler facility. A hardware device
that allows a data terminal that is not set up for packet switching
to use a packet switching network. It assembles data into
packets for transmission, and disassembles the packets on
arrival.
Paging The procedure by which a GSM PLMN xed infrastructure
attempts to reach an MS within its location area, before any
other network-initiated procedure can take place.
PATH CEPT 2 Mbit/s route through the BSS network.
Patch Level Corresponds to a patch or group of patches which address a
single problem or SR.
Patch Object One or more patch levels compiled together into an object.
A patch object is identied by a unique code object number.
As multiple patch objects may be released within a specic
software point release, each patch object therefore must have
its respective version number.
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.
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.
2006 Motorola, Inc.
8-47
June 2007
PCHN Physical Channel. The physical channel is the medium over
which the information is carried. In the case of GSM radio
communications this would be the Air Interface. Each RF
carrier consists of eight physical channels (or timeslots) used
for MS communications. In the case of a terrestrial interface the
physical channel would be cable. See also Physical Layer.
PCI Packet Control Interface.
PCI Peripheral Component Interconnect. A standard for connecting
peripherals to a personal computer, PCI is a 64-bit bus, though
it is usually implemented as a 32-bit bus.
PCM Pulse Code Modulation. Modulation in which a signal is
sampled, and the magnitude (with respect to a xed reference)
of each sample is quantized and converted by coding to a
digital signal. Provides undistorted transmission, even in the
presence of noise. See also 2 Mbit/s link, which is the physical
bearer of PCM.
pCM PCU Conguration 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.
PCS System Personal Communications Services System. In PCS, a
collection of facilities that provides some combination of
personal mobility, terminal mobility, and service prole
management. Note: As used here, "facilities" includes
hardware, software, and network components such as
transmission facilities, switching facilities, signalling facilities,
and databases.
PCS1900 A cellular phone network using the higher frequency range
allocated in countries such as the USA. It operates on
the frequency range, 1850 - 1910 MHz (receive) and
1930 - 1990 MHz (transmit).
PCU Packet Control Unit. A BSS component that provides GPRS
with packet scheduling over the air interface with the MS, and
packet segmentization and packetization across the Frame
Relay link with the SGSN.
PCU Picocell Control unit. Part of M-Cellaccess.
pd Potential difference. Voltage.
PD Protocol Discriminator eld. The rst octet of the packet header
that identies the protocol used to transport the frame.
PD Public Data. See PDN.
PDB Power Distribution Board.
PDCH Packet Data Channel. PDCH carries a combination of PBCCH
and PDTCH logical channels.
PDF Power Distribution Frame (MSC/LR).
2006 Motorola, Inc.
June 2007
PDN Public Data Network. A network established and operated by
a telecommunications administration, or a recognized private
operating agency, for the specic purpose of providing data
transmission services for the public.
PDP Packet Data Protocol.
PDTCH Packet Data Trafc Channels
PDU Power Distribution Unit. The PDU consists consisting of the
Alarm Interface Board (AIB) and the Power Distribution Board
(PDB).
PDU Protected Data Unit.
PDU Protocol Data Unit. A term used in TCP/IP to refer to a unit of
data, headers, and trailers at any layer in a network.
PEDC Pan-European Digital Cellular network. The GSM network in
Europe.
Peg A single incremental action modifying the value of a statistic.
Also, A number indicating the use of a device or resource.
Each time the device or resource is used the peg count is
incremented.
Pegging Modifying a statistical value.
pFCP PCU Fault Collection Process. See pFTP.
pFTP PCU Fault Transaction Process. The pFTP resides on the PSP
as part of the GWM Functional Unit process. All alarms at the
PCU are reported to pFTP. All DPROCs and the MPROC have
a local pFCP to handle Software Fault Management indications
(SWFMs). The pFTP forwards alarms to the Agent at the BSC
and generates messages to pCA for device transitions as
needed, based on faults reported.
PGSM Primary GSM. PGSM operates on the standard GSM frequency
range, 890 - 915 MHz (receive) and 935 - 960 MHz (transmit).
PH Packet Handler. A packet handler assembles and disassembles
packets.
PH PHysical (layer). See Physical Layer.
PHI Packet Handler Interface.
Physical Layer See OSI-RM. The Physical Layer is the lowest of seven
hierarchical layers. It performs services requested by the Data
Link Layer. The major functions and services of the layer
are: (a) establishment and termination of a connection to a
communications medium; (b) participation in the process of
sharing communication resources among multiple users; and,
(c) conversion between the representation of digital data in
user equipment and the corresponding signals transmitted over
a communications channel.
PI Presentation Indicator. The PI forms part of the calling name
information. Depending on database settings, the PI may
prevent the called party from seeing the identity of the calling
party.
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.
2006 Motorola, Inc.
8-49
June 2007
PICS Protocol Implementation Conformance Statement. A statement
made by the supplier of an implementation or system claimed
to conform to a given specication, stating which capabilities
have been implemented.
PID Process IDentier/Process ID.
PIM PCM Interface Module (MSC).
PIN Personal Identication Number. A password, typically four
digits entered through a telephone keypad.
PIN Problem Identication Number.
PIX Parallel Interface Extender half size board. Customer alarm
interface, part of the BSS. The PIX board provides a means of
wiring alarms external to the BSS, BSC, or BTS into the base
equipment.
PIXT or PIXIT Protocol Implementation eXtra information for Testing.
A statement made by a supplier or implementor of an
implementation under test (IUT) which contains information
about the IUT and its testing environment which will enable a
test laboratory to run an appropriate test suite against the IUT.
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 specic 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, etc.
pp, p-p
Peak-to-peak.
2006 Motorola, Inc.
June 2007
PP Point-to-Point.
ppb Parts per billion.
PPB PCI (Peripheral Component Interconnect) to PCI Bridge board.
The PPB allows an MPROC to be linked to a separate bus.
The PPB and MPROC are paired boards.
PPE Primitive Procedure Entity.
ppm
Parts per million (x 10
-6
).
Pref CUG Preferential CUG. A Pref CUG, which can be specied for each
basic service group, is the nominated default CUG to be used
when no explicit CUG index is received by the network.
Presentation Layer See OSI RM. The Presentation Layer responds to service
requests from the Application Layer and issues service
requests to the Session Layer. It relieves the Application
Layer of concern regarding syntactical differences in data
representation within the end-user systems.
Primary Cell A cell which is already optimized in the network and has a
co-located neighbour whose cell boundary follows the boundary
of the said cell. The primary cell has a preferred band equal to
the frequency type of the coincident cell.
PRM Packet Resource Manager. The PRM is a PRP process. It
performs all RLC/MAC functions and realises UL/DL power
control and timing advance.
PROM Programmable Read Only Memory. A storage device that, after
being written to once, becomes a read-only memory.
PRP Packet Resource Process(or). A PCU hardware component,
the PRP is a DPROC board which manages the packet
resources at the PCU and is the processor where all of the
radio related processing occurs. GPRS channels are routed to
PRPs which perform the RLC/MAC processing, air interface
scheduling, and frame synchronization of the channels.
Ps Location probability. Location probability is a quality criterion
for cell coverage. Due to shadowing and fading a cell edge is
dened by adding margins so that the minimum service quality
is fullled 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
veries whether the BSSs are operational or not. If a BSS fails
to respond to a PSA request for its status, the OMC-R will
generate an alarm for that BSS.
PSI Packet System Information.
PSAP Presentation Services Access Point.
pSAP PCU System Audit Process. pSAP is a GWM process. It
periodically monitors the soft devices to maintain the reliability
of the system.
PSM Power Supply Module.
pSM PCU Switch Manager. The pSM resides on the PSP as part of
the GWM Functional Unit process. The pSM maintains data
paths within the PCU and communicates with the BSC.
PSP PCU System Processor board. Part of GPRS.
2006 Motorola, Inc.
8-51
June 2007
PSPDN Packet Switched Public Data Network. See Packet Switching
and PDN.
PSTN Public Switched Telephone Network. The domestic land
line telecommunications network. It is usually accessed by
telephones, key telephone systems, private branch exchange
trunks, and data arrangements.
PSU Power Supply Unit.
PSW Pure Sine Wave.
PTACH Packet Timing Advance Control Channel
PTO Public Telecommunications Operator.
PTR Packet Timeslot Reconguration.
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 may 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.
QAF Q-Adapter Function.
QEI Quad European Interface. Interfaces four 2 Mbit/s circuits to
TDM switch highway. See MSI.
QIC Quarter Inch Cartridge (Data storage format).
QoS Quality Of Service. An alarm category which indicates that a
failure is degrading service.
Queue Data structure in which data or messages are temporarily
stored until they are retrieved by a software process. Also a
series of calls waiting for service. See also FIFO.
Quiescent mode IDS intermediate state before shutdown.
2006 Motorola, Inc.
June 2007
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 eld.
RA Radio Access.
RA Routing Area.
RA250 Rural Area with the MS travelling at 250 kph. Dynamic model
measured. See also TU3, TU50, HT100 and EQ50.
RAB Random Access Burst. Data sent on the RACH.
RACCH Random Access Control CHannel. A GSM common control
channel used to originate a call or respond to a page.
RACH Random Access CHannel. The RACH is used by the mobile
station to request access to the network. See also RAB.
Radio Frequency A term applied to the transmission of electromagnetically
radiated information from one point to another, usually using air
or vacuum as the transmission medium. An electromagnetic
wave frequency intermediate between audio frequencies and
infrared frequencies used in radio and television transmission.
RAM Random Access Memory. A read/write, nonsequential-access
memory in which information can be stored, retrieved and
modied. This type of memory is generally volatile (i.e., its
contents are lost if power is removed).
RAND RANDom number (used for authentication). The RAND is sent
by the SGSN to the MS as part of the authentication process.
RAT Radio Access Technology
RATI Receive Antenna Transceiver Interface.
RAx Rate Adaptation.
RBDS Remote BSS Diagnostic System (a discontinued Motorola
diagnostic facility).
RBER Residual Bit Error Ratio. RBER is a ratio of the number of
bits in error to the total number of bits received, within error
detected speech frames dened as good. The measurement
period over which the calculation is made is 480 ms. During this
period, 24 speech frames are decoded and a ratio calculated.
By referring to a lookup table, the ratio is then converted to an
RBER Quality number between 0 and 7.
RBTS Remote Base Transceiver Station. A BTS that is not co-located
with the BSC that controls it.
RCB Radio Control Board. Part of the DRCU.
RCI Radio Channel Identier. The unique identier 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.
2006 Motorola, Inc.
8-53
June 2007
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
3MHz reference signal to all transceivers. It is used for carrier
and injection frequency synthesis.
RDN Relative Distinguished Name. A series of RDNs form a unique
identier, the distinguished name, for a particular network
element.
REC, Rec RECommendation.
Reciprocal neighbour Used to describe adjacent cells; each being designated as
a neighbour of the other. Also known as bi-directional and
two-way neighbour.
Registration The process of a MS registering its location with the MSC in
order to make or receive calls. This occurs whenever the MS
rst activates or moves into a new service area.
REJ REJect(ion).
REL RELease.
RELP Residual Excited Linear Predictive. A form of speech coding.
RELP coders are usually used to give good quality speech at
bit rates in the region of 9.6 kbit/s.
RELP-LTP RELP Long Term Prediction. A name for GSM full rate. See
Full Rate.
Remotely Tuned Combiner A combiner device which houses two processors (for
paired-redundancy) and several tuneable cavities. See also
COMB
resync
Resynchronize/resynchronization.
REQ REQuest.
Reuse Pattern The minimum number of cells required in a pattern before
channel frequencies are reused, to prevent interference.
Varies between cell conguration type and channel type. The
pattern shows assignments of adjacent channels to minimize
interference between cells and sectors within the pattern area.
Revgen A Motorola DataGen utility for producing an MMI script from a
binary object database.
RF See Radio Frequency.
RFC, RFCH Radio Frequency Channel. A partition of the system RF
spectrum allocation with a dened bandwidth and centre
frequency.
RFE Radio Front End (module).
RFE Receiver Front End (shelf).
RFEB Receiver Front End Board. Part of DRCU II.
RFI Radio Frequency Interference.
RFM Radio Frequency Module.
RFN Reduced TDMA Frame Number.
2006 Motorola, Inc.
June 2007
RFU Reserved for Future Use.
RJ45 Registered Jack 45. An eight-wire connector used commonly
to connect computers onto a local-area networks (LAN),
especially Ethernets.
RISC Reduced Instruction Set Computer. A type of microprocessor
that recognizes a relatively limited number of instruction types,
allowing it to operate at relatively higher speeds.
RL Remote login. RL is a means by which the operator performs
conguration management, fault management, and some
performance management procedures at the NEs. The RL
software manages the X.25 connection for remote login. The
circuit is made by the OMC-R calling the NE.
RLC Release Complete. An SCCP message type used with RLSD
to release a connection.
RLC Radio Link Control. Air interface transmission layer. The RLC
function processes the transfer of PDUs from the LLC layer.
RLM RF Link Manager.
RLP Radio Link Protocol. An ARQ protocol used to transfer user
data between an MT and IWF. See GSM 04.22.
RLR Receive Loudness Rating. See SLR.
RLSD ReLeaSeD. An SCCP message type used with RLC to release
a connection.
RMS Root Mean Square (value). The most common mathematical
method of dening the effective voltage or current of an AC
wave. For a sine wave, the rms value is 0.707 times the peak
value.
RMSU Remote Mobile Switching Unit. An RMSU is a line concentrator.
It may be inserted between the MSC and some of the BSS
sites served by the MSC to reduce the number of terrestrial
signalling and trafc 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
modication 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 specication for O & M) (OMC).
Roundtrip Time period between transmit and receive instant of a timeslot
in the BTS, propagation determined by the response behaviour
of the MS and the MS to BTS delay distance.
RPE Regular Pulse Excited (codec). See RPE-LTP.
RPE-LTP Regular Pulse Excitation - Long Term Prediction. The GSM
digital speech coding scheme. GSM uses a simplied RPE
codec, with long-term prediction, operating at 13 kbits/s to
provide toll quality speech.
2006 Motorola, Inc.
8-55
June 2007
RPOA Recognised Private Operating Agency. Private
telecommunications operator recognised by the appropriate
telecommunications authority.
RPR Read Privilege Required. Part of the table structure of the
OMC database schema. Access to the column is allowed only
for privileged accounts.
RR Radio Resource management. Part of the GSM management
layer. The functions provided by RR include paging, cipher
mode set, frequency redenition, 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 Signalling Link. RSL is used for signalling between the
BSC and BTSs. The interface uses a 64 kbit/s 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 denes the
regions in which roaming is allowed. The elements of the RSZI
are:The Country Code (CC) which identies the country in
which the GSM PLMN is located,The National Destination Code
(NDC) which identies the GSM PLMN in that country,The
Zone Code (ZC) which identies 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
ne-tune the cavities to the right frequency. A poorly tuned
cavity can cause power destined for the antenna to be reversed.
RTE Remote Terminal Emulator.
RTF Radio Transceiver Function. RTF is the function that supports
the air interface channel and the DRI/Transceiver pair. When
equipping a DRI at a remote BTS, one or more RTFs must
be equipped.
RTF Receive Transmit Functions.
RTS Request to Send. A handshaking signal used with
communication links, especially RS232 or CCITT Rec. V.24 to
indicate (from a transmitter to a receiver) that data is ready for
transmission. See also CTS.
RU Rack Unit.
Run level System processor operating mode.
2006 Motorola, Inc.
June 2007
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 kbit/s link, thus reducing the number of links required for
interconnection to the BSCs. See also XCDR.
RXF Receive Function (of the RTF).
RXLEV Received signal level. An indication of received signal level
based on the RSSI. RXLEV is one of the two criteria for
evaluating the reception quality (the basis for handover and
power control). See also RXQUAL. The MS reports RXLEV
values related to the apparent received RF signal strength. It is
necessary for these levels to attain sufcient 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 specied 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 signalling link over the air interface.
SABME SABM Extended.
SACCH Slow Associated Control CHannel. A GSM control channel
used by the MS for conveying power control and timing
advance information in the downlink direction, and RSSI and
link quality reports in the uplink direction.
SACCH/C4 Slow Associated Control CHannel/SDCCH/4.
SACCH/C8 Slow Associated Control CHannel/SDCCH/8.
SACCH/T Slow Associated Control CHannel/Trafc channel.
SACCH/TF Slow Associated Control CHannel/Trafc channel Full rate.
SACCH/TH Slow Associated Control CHannel/Trafc channel Half rate.
SAGE A brand of trunk test equipment.
2006 Motorola, Inc.
8-57
June 2007
SAP Service Access Point. In the reference model for OSI, SAPs of
a layer are dened 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 noties the Alarms handling software of the condition.
SAPI Service Access Point Indicator (identier). The OSI term for the
component of a network address which identies 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 lters are used for sorting
signals by frequency.
SB Synchronization Burst (see Synchronization burst).
SBUS Serial Bus. An SBUS is a logical device made up of the
communication path between the GPROCs and LANX cards
in a cage.
SC Service Centre (used for Short Message Service).
SC Service Code.
SCCA System Change Control Administration. Software module
which allows full or partial software download to the NE (OMC).
SCCP Signalling Connection Control Part (part of SS7).
SCEG Speech Coding Experts Group (of GSM).
SCH Synchronization CHannel. A GSM broadcast control channel
used to carry information for frame synchronization of MSs and
identication of base stations.
SCI Status Control Interface. A slave to the Status Control Manager.
SCIP Serial Communication Interface Processor.
SCM Status Control Manager. Accepts messages from other
processors within the switch requesting status displays in the
form of one or more lights on a hardware panel. The SCM maps
the status display requests into specic commands to the status
control interface processor to turn on and/or turn off lights.
SCN Sub-Channel Number. One of the parameters dening 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, oppy 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.
2006 Motorola, Inc.
June 2007
SDCCH Stand-alone Dedicated Control CHannel. A GSM control
channel where the majority of call setup occurs. Used for MS to
BTS communications before MS assigned to TCH. A SDCCH
is used by a single MS for call setup, authentication, location
updating and SMS point to point.
SDL Specication Description Language. A method for visually
depicting the functionality of call processing, operations and
maintenance software.
SDM Sub-rate Data Multiplexor
SDT SDL Development Tool. A software tool to model and validate
real-time, state-based product software designs.
SDU Service Data Unit. In layered systems, a set of data that is sent
by a user of the services of a given layer, and is transmitted to
a peer service user semantically unchanged.
SDR Special Drawing Rights. The SDR is the International Monetary
Fund unit of account. It also serves as a basis for the unit of
account for a number of other international organizations and
as a basis for private nancial instruments. The SDR is based
on the values of the euro, U.S. dollar, Japanese yen and pound
sterling.
SE Support Entity. See SEF.
Secondary Cell A cell which is not optimized in the network and has a
co-located neighbour whose cell boundary follows the boundary
of the said cell. The secondary cell has a preferred band the
same as that of its own frequency type.
SEF Support Entity Function. SEFs are functions not directly
involved in the telecommunication process. They include fault
localisation, protection switching, etc. (GSM Rec.12.00).
Session Layer See OSI RM. The Session Layer responds to service requests
from the Presentation Layer and issues service requests to
the Transport Layer. It provides the mechanism for managing
the dialogue between end-user application processes. It
provides for either duplex or half-duplex operation and
establishes checkpointing, adjournment, termination, and
restart procedures.
SFH Synthesizer Frequency Hopping. The principle of SFH is that
every mobile transmits its time slots according to a sequence of
frequencies that it derives from an algorithm. The frequency
hopping occurs between time slots and, therefore, a mobile
station transmits (or receives) on a xed frequency during one
time slot. It must then hop before the time slot on the next
TDMA frame. Due to the time needed for monitoring other
base stations the time allowed for hopping is approximately 1
ms, according to the receiver implementation. The receive and
transmit frequencies are always duplex frequencies.
SGSN Serving GPRS Support Node. The SGSN provides the control,
transmission, OAMP, and charging functions. It keeps track of
the individual MS locations, and performs security functions
and access control. The SGSN is connected to the BSS via a
Frame Relay network.
2006 Motorola, Inc.
8-59
June 2007
SI Screening Indicator. The supplementary service (SS) screening
indicator is sent by the MS at the beginning of the radio
connection to allow the network to assess the capabilities of the
MS and hence determine either whether a particular network
initiated SS operation may be invoked or which version of a
network initiated SS operation should be invoked. The SS
screening indicator is only relevant to network initiated SS
operation and is valid for the duration of a radio connection.
SI Service Interworking. Part of the IWF.
SI Supplementary Information.
SI System Information.
SIA Supplementary Information A.
SID Silence Descriptor. The transmission of comfort noise
information to the RX side is achieved by means of a SID
frame. A SID frame is transmitted at the end of speech bursts
and serves as an end of speech marker for the RX side. In
order to update the comfort noise characteristics at the RX
side, SID frames are transmitted at regular intervals also during
speech pauses. This also serves the purpose of improving the
measurement of the radio link quality by the radio subsystem
(RSS).
SIF Signal Information Field. The bits of a message signal unit that
carry information for a certain user transaction; the SIF always
contains a label.
Signalling System No.7 See SS7.
SIM Subscriber Identity Module. Removable module which is
inserted into a mobile equipment; it is considered as part of
the MS. It contains security related information (IMSI, Ki, PIN),
other subscriber related information and the algorithms A3 and
A8.
SIMM Single Inline Memory module.
SIMM System Integrated Memory Module. A small plug-in circuit
board providing additional RAM for a computer.
SIO Service Information Octet. Eight bits contained in a message
signal unit, comprising the service indicator and sub-service
eld. A value in the SIF of an SS7 signalling message
specifying the User Part type.
SITE BSC, BTS or collocated BSC-BTS site.
SIX Serial Interface eXtender. Converts interface levels to TTL
levels. Used to extend 2 serial ports from GPROC to external
devices (RS232, RS422, and bre optics).
SK Secondary Key. A database column attribute, the secondary
key indicates an additional index and/or usage as a composite
key.
SL See Session Layer.
SL Signalling Link. The signalling links between the various
network elements are: Remote BTS to BSC - Radio Signalling
Link (RSL), BSC to MSC - Message Transfer Link (MTL),
OMC(R) to BSS - Operations and Maintenance Link (OML),
Remote XCDR to BSC - XCDR signalling Link (XBL), CBC to
BSC - Cell Broadcast Link (CBL).
2006 Motorola, Inc.
June 2007
SLNK Serial Link. One of four communications paths between SCIP
and peripheral equipment. The information on the link is sent
serially in a bit-synchronous format.
SLR Send Loudness Rating. The SLR, in the mobile to land
direction, and the Receive Loudness Rating (RLR) in the land
to mobile direction, determine the audio signal levels for the
customers speech. The loudness ratings are calculated from
the send and receive sensitivity masks or frequency responses.
SLTA Signalling Link Test Acknowledge. Message sent from the
MSC to the BSC in response to an SLTM.
SLTM Signalling Link Test Message. During the process of bringing
an MTL link into service, the BSC sends an SLTM message to
the MSC. The MSC responds with an SLTA message.
Software Patch A software change made within a process and applied to each
instance of this process during suspension of that process. It
replaces an existing function in a process, in order to resolve a
problem or error in the software.
SM Switch Manager. The function of the SM is to connect a MS
terrestrial trunk from the MSC (designated by the MSC), to the
radio channel given to a MS by the cell resource manager in
the BSS software.
SM Summing Manager.
SMAE System Management Application Entity (CCITT Q795, ISO
9596). OSI terminology for a software Management Information
Server that manages a network.
SMASE System Management Application Service Element.
SMCB Short Message Cell Broadcast.
SME Short Message Entity. An entity that may send or receive Short
Messages. The SME may be located in a xed network, an
MS, or a SC. See also SMS.
SMG Special Mobile Group. To avoid confusion between the GSM
system and the GSM committee with its wider responsibilities,
the committee was renamed SMG in 1992.
SMP Motorola Software Maintenance Program. A Motorola program
designed to ensure the highest quality of software with the
highest level of support.
SMS Short Message Service. SMS is a globally accepted wireless
service that enables the transmission of alphanumeric
messages between mobile subscribers and external systems
such as electronic mail, paging, and voice-mail systems. It
transfers the short messages, up to 160 characters, between
Smts and MSs via an SMS-SC. See also SMS-SC, SMS/PP
and Smt.
SMSCB Short Message Service Cell Broadcast. SMSCB is a service in
which short messages may be broadcast from a PLMN to MSs.
SMSCB messages come from different sources (e.g. trafc
reports, weather reports). Messages are not acknowledged by
the MS. Reception of SMSCB messages by the MS is only
possible in idle mode. The geographical area over which each
message is transmitted is selected by the PLMN operator, by
agreement with the provider of the information.
2006 Motorola, Inc.
8-61
June 2007
SMS-SC Short Message Service - Service Centre. SMS-SC is an
interworking unit between stationary networks and the GSM
Network. It acts as a store and forward centre for short
messages. See also SMS, SMS/PP and Smt.
SMS/PP Short Message Service/Point-to-Point. Two different
point-to-point services have been dened: 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.
Software Instance A complete set of software and rmware objects including the
database object.
SP Service Provider. The organisation through which the
subscriber obtains GSM telecommunications services. This
may be a network operator or possibly a separate body.
SP Signalling Point. A signalling point is a node within a SS7
network.
SP Special Product.
SP SPare.
SPARC Scalable Processor ArChitecture. a 32- and 64-bit
microprocessor architecture from Sun Microsystems that is
based on the Reduced Instruction Set Computer (RISC).
SPARC has become a widely-used architecture for hardware
used with UNIX-based operating systems.
SPC Signalling Point Code.
SPC Suppress Preferential CUG. Prohibits the use of the preferential
CUG, on a per call basis.
SPI Signalling Point Inaccessible.
SPP Single Path Preselector.
SQE Signal Quality Error.
SQL Structured Query Language. The standard language for
relational database management systems as adopted by the
American National Standards Institute (ANSI X3.135-1989) and
the International Standards Organization (ISO 9075-1989).
SRD Service Request Distributor.
SRES Signed RESponse (authentication). The SRES is calculated by
the MS, using the RAND, and sent to the SGSN to authenticate
the MS.
2006 Motorola, Inc.
June 2007
SS Supplementary Service. A modication of, or a supplement to,
a basic telecommunication service.
SS System Simulator.
SS7 ITU-TSS Common Channel Signalling System No. 7. Also
known as C7, S7 or SS#7. The standard denes the procedures
and protocol by which network elements in the PSTN exchange
information over a digital signalling network to effect wireless
(cellular) and wireline call setup, routing and control.
SSA SubSystem-Allowed. SSA is used for SCCP subsystem
management. An SSA message is sent to concerned
destinations to inform those destinations that a subsystem
which was formerly prohibited is now allowed. (see ITU-T
Recommendation Q.712 para 1.15).
SSAP Site System Audits Processor.
SSC Supplementary Service Control string. When a subscriber
selects a supplementary service control from the menu in a
GSM network, the mobile station invokes the SSC by sending
the network the appropriate functional signalling message.
SSF Subservice Field. The level 3 eld containing the network
indicator and two spare bits.
SSM SCCP Switch Manager.
SSM Signalling State Machine.
SSN SubSystem Number. In SS7, each signalling point (SP) may
contain a number of subsystems. Each subsystem has a
unique ID, the SSN (e.g. 149 for SGSN and 6 for HLR).
SSP Service Switching Point. Intelligent Network Term for the Class
4/5 Switch. The SSP has an open interface to the IN for
switching signalling, control and handoff.
SSP Subsystem-prohibited. SSP is used for SCCP subsystem
management. An SSP message is sent to concerned
destinations to inform SCCP Management at those destinations
of the failure of a subsystem.
SSS Switching SubSystem. The SSC comprises the MSC and the
LRs.
STAN Statistical ANalysis (processor).
STAT STATistics.
stats Statistics.
STC System Timing Controller. The STC provides the timing
functions for the GPROC.
STMR Side Tone Masking rating. A rating, expressed in dB, based on
how a speaker will perceive his own voice when speaking.
SUERM Signal Unit Error Rate Monitor. A link error rate monitor.
STP Signalling Transfer Point. A node in the SS7 telephone network
that routes messages between exchanges and between
exchanges and databases that hold subscriber and routing
information.
SU Signal Unit. A group of bits forming a separately transferable
entity used to convey information on a signalling link.
SunOS Sun Microsystems UNIX Operating System. SunOS was
renamed Solaris.
2006 Motorola, Inc.
8-63
June 2007
Superframe 51 trafc/associated control multiframes or 26
broadcast/common control multiframes (period 6.12s).
Super user User account that can access all les, regardless of protection
settings, and control all user accounts.
SURF Sectorized Universal Receiver Front-end (Used in
Horizonmacro).
SVC Switch Virtual Circuit. A temporary virtual circuit that is set up
and used only as long as data is being transmitted. Once the
communication between the two hosts is complete, the SVC
disappears. See also PVC.
SVM SerVice Manager. The SVM provides overall management
authority for all in-service service circuits.
SVN Software Version Number. The SVN allows the ME
manufacturer to identify different software versions of a given
type approved mobile. See also IMEI and IMEISV.
SW Software.
SWFM SoftWare Fault Management. Software faults are handled
through a SWFM facility which routes those events to the OMC
independently through the FCP.
SYM SYstem information Manager. The SYM builds and sends
GPRS system information messages over the BCCH.
sync
synchronize/synchronization.
Synchronization burst Period of RF carrier less than one timeslot whose modulation
bit stream carries information for the MS to synchronize its
frame to that of the received signal.
Synthesizer hopping Synthesizer hopping is a method of frequency hopping in
which the RCUs are re-tuned in real-time, from frequency to
frequency.
SYS SYStem.
SYSGEN SYStem GENeration. The Motorola procedure for loading a
conguration 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 kbp/s 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
Mbit/s circuits (See BIB).
TA Terminal Adaptor. A physical entity in the MS providing terminal
adaptation functions (see GSM 04.02).
TA See Timing Advance.
TAC Type Approval Code. Part of the IMEISV.
2006 Motorola, Inc.
June 2007
TACS Total Access Communication System. European analogue
cellular system.
TAF Terminal Adaptation Function.
TATI Transmit Antenna Transceiver Interface. The TATI consists of
RF combining equipments, either Hybrid or Cavity Combining.
See CCB.
TAXI Transparent Asynchronous Transmitter/Receiver Interface
(physical layer). A 100 Mbps ATM transmission standard
dened by the ATM Forum.
TBD To Be Determined.
TBF Temporary Block Flow. MAC modes support the provision of
TBFs allowing the point-to-point transfer of signalling and user
data between the network and an MS.
TBR Technical Basis for Regulation. An ETSI document containing
technical requirements and procedures.
TBUS TDM Bus. A TBUS is a logical device made up of the TDM
backplane of a cage, the KSW devices managing the TDM
highway of the cage, and local and remote KSWX devices (if
they exist).
TC Transaction Capabilities. TC refers to a protocol structure
above the network layer interface (i.e., the SCCP service
interface) up to the application layer including common
application service elements but not the specic 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 Trafc CHannel. GSM logical channels which carry either
encoded speech or user data.
TCH/F A full rate TCH. See also Full Rate.
TCH/F2.4 A full rate TCH at ? 2.4 kbit/s.
TCH/F4.8 A full rate TCH at 4.8 kbit/s.
TCH/F9.6 A full rate TCH at 9.6 kbit/s.
TCH/FS A full rate Speech TCH.
TCH/H A half rate TCH. See also Half Rate.
TCH/H2.4 A half rate TCH at ? 2.4 kbit/s.
TCH/H4.8 A half rate TCH at 4.8 kbit/s.
TCH/HS A half rate Speech TCH.
TCI Transceiver Control Interface.
TCP Transmission Control Protocol. TCP is one of the main
protocols in TCP/IP networks. Whereas the IP protocol deals
only with packets, TCP enables two hosts to establish a
connection and exchange streams of data. TCP guarantees
delivery of data and also guarantees that packets will be
delivered in the same order in which they were sent. See also
IP and TCP/IP.
2006 Motorola, Inc.
8-65
June 2007
TCP/IP Transmission Control Protocol/Internet Protocol. Two
interrelated protocols that are part of the Internet protocol suite.
TCP operates on the OSI Transport Layer and IP operates on
the OSI Network Layer. See also IP and TCP.
TC-TR Technical Commitee Technical Report.
TCU Transceiver Control Unit.
TDF Twin Duplexed Filter. Used in M-Cellhorizon.
TDM Time Division Multiplexing. A type of multiplexing that combines
data streams by assigning each stream a different time slot in a
set. TDM repeatedly transmits a xed sequence of time slots
over a single transmission channel. Within T-Carrier systems,
such as T-1 and T-3, TDM combines PCM streams created for
each conversation or data stream.
TDMA Time Division Multiple Access. A technology for delivering
digital wireless service using TDM. TDMA works by dividing
a radio frequency into time slots and then allocating slots to
multiple calls. In this way, a single frequency can support
multiple, simultaneous data channels.
TDU TopCell Digital Unit. Part of the TopCell BTS hardware. A TDU
is capable of supporting 6 TRUs for supporting up to 6 sectors.
TE Terminal Equipment. Equipment that provides the functions
necessary for the operation of the access protocols by the user.
Tei Terminal endpoint identier. A number that identies a specic
connection endpoint within a service access point.
TEI Terminal Equipment Identity.
TEMP TEMPorary.
TEST TEST control processor.
TF Transmission Function. The TF provides layered protocol
software for handling payload information transfer and for
providing signalling communications between the control
function and external systems.
TFA TransFer Allowed. An SPC route management message used
to notify adjacent signalling points of an accessible route.
TFP TransFer Prohibited. An SPC route management message
used to notify adjacent signalling points of an inaccessible
route.
TFTP Trivial File Transfer Protocol. TFTP is a simple form of FTP. It
uses UDP and provides no security features. It is often used by
servers to boot diskless workstations, X-terminals, and routers.
TI Transaction Identier.
Timeslot The multiplex subdivision in which voice and signalling bits are
sent over the air. Each RF carrier is divided into 8 timeslots.
See also ARFCN.
Timing advance A signal sent by the BTS to the MS. It enables the MS to
advance the timing of its transmission to the BTS so as to
compensate for propagation delay.
TL See Transport Layer.
TLLI Temporary Logical Link Identier.
TLV Type, Length and Value. An encoding element composed of
three elds: a type identier, a length indicator, and content
octets.
2006 Motorola, Inc.
June 2007
TM Trafc Manager.
TMI TDM Modem Interface board. Provides analogue interface
from IWF to modems for 16 circuits. Part of IWF.
TMM Trafc Metering and Measuring. TMM provides system tools
to be used by trafc 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
dene and address network elements. TMN uses the OSI
Management Standards as its framework. TMN applies to
wireless communications and cable TV as well as to private
and public wired networks.
TMSI Temporary Mobile Subscriber Identity. A unique identity
temporarily allocated by the MSC to a visiting mobile subscriber
to process a call. May be changed between calls and even
during a call, to preserve subscriber condentiality.
TN Timeslot Number.
TOM Tunneling of Messages.
TON Type Of Number.
Trafc channels Channels which carry user's speech or data. See also TCH.
Trafc unit Equivalent to an erlang.
Training sequence Sequence of modulating bits employed to facilitate timing
recovery and channel equalization in the receiver.
Transport Layer See OSI RM. The Transport Layer responds to service requests
from the Session Layer and issues service requests to the
Network Layer. Its purpose is to provide transparent transfer
of data between end users, thus relieving the upper layers
from any concern with providing reliable and cost-effective
data transfer.
TRS Timeslot Resource Shifter. The TRS determines which
timeslots are active in a PRP board to perform a control of the
GPRS trafc.
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 8 full-rate trafc channels according
to specication GSM 05.02. If Slow Frequency Hopping (SFH)
is not used, then the TRX serves the communication on one
RF carrier.
TS Technical Specication.
TS TeleService. Any service provided by a telecommunication
provider.
2006 Motorola, Inc.
8-67
June 2007
TS TimeSlot (see Timeslot).
TS1 Training Sequence 1.
TS2 Training Sequence 2.
TSA TimeSlot Acquisition.
TSA TimeSlot Assignment.
TSDA Transceiver Speech & Data Interface.
TSC Training Sequence Code. A training sequence is sent at the
centre of a burst to help the receiver identify and synchronize
to the burst. The training sequence is a set sequence of bits
which is known by both the transmitter and receiver. There are
eight different TSCs numbered 0 to 7. Nearby cells operating
with the same RF carrier frequency use different TSCs to allow
the receiver to identify the correct signal.
TSI TimeSlot Interchange. The interchange of timeslots within a
TDM stream.
TSDI Transceiver Speech and Data Interface.
TSM Transceiver Station Manager.
TSN TRAU SyNc.
TSW Timeslot SWitch.
TTCN Tree and Tabular Combined Notation. TTCN is a programming
language endorsed by ISO that is used to write test suites for
telecommunications systems.
TTL Transistor to Transistor Logic. A common semiconductor
technology for building discrete digital logic integrated circuits.
TTY TeleTYpe (refers to any terminal).
TU Trafc Unit.
TU3 Typical Urban with the MS travelling at 3 kph. Dynamic model
measured. See also TU50, HT100, RA250 and EQ50.
TU50 Typical Urban with the MS travelling at 50 kph. Dynamic model
measured. See also TU3, HT100, RA250 and EQ50.
TUP Telephone User Part. TUP was an earlier implementation of
SS7 and generally does not allow for data type applications.
TV Type and Value.
Two-way neighbour See Reciprocal neighbour.
Tx Transmit(ter).
TX Transmit window buffer.
TXF Transmit Function. See RTF.
TXPWR Transmit PoWeR. Tx power level in the
MS_TXPWR_REQUEST and MS_TXPWR_CONF
parameters.
TxBPF Transmit Bandpass Filter. See BPF.
2006 Motorola, Inc.
June 2007
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 codeset containing all of
the characters commonly used in computer applications.
UDI Unrestricted Digital Information.
UDP User Datagram Protocol. UDP is a connectionless protocol that,
like TCP, runs on top of IP networks. Unlike TCP/IP, UDP/IP
provides very few error recovery services, offering instead a
direct way to send and receive datagrams over an IP network.
It is used primarily for broadcasting messages over a network.
UDUB User Determined User Busy.
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 organisation for cooperation among railway
companies. Its activities encompass all elds related to the
development of rail transport.
UID User ID. Unique number used by the system to identify the user.
UL Upload (of software or database from an NE to a BSS).
UL UpLink.
ULC UpLink Concatenator. The ULC concatenates RLC data blocks
into LLC frames.
Um Air interface.
UMTS Universal Mobile Telecommunication System. The European
implementation of the 3G wireless phone system. UMTS, which
is part of IMT-2000, provides service in the 2GHz band and
offers global roaming and personalized features. Designed as
an evolutionary system for GSM network operators, multimedia
data rates up to 2 Mbps are expected.
UNIX A multiuser, multitasking operating system that is widely used
as the master control program in workstations and especially
servers. UNIX was developed by AT&T and freely distributed to
government and academic institutions, causing it to be ported
to a wider variety of machine families than any other operating
system. As a result, UNIX became synonymous with open
systems.
UPCMI Uniform PCM Interface (13 bit). The UPCMI is introduced for
design purposes in order to separate the speech transcoder
impairments from the basic audio impairments of the MS.
UPD Up to Date.
Uplink Physical link from the MS towards the BTS (MS transmits, BTS
receives).
2006 Motorola, Inc.
8-69
June 2007
UPS Uninterruptable Power Supply. A device that is inserted
between a primary power source, such as a commercial utility,
and the primary power input of equipment to be protected,
e.g., a computer system, for the purpose of eliminating the
effects of transient anomalies or temporary outages. Backup
power is used when the electrical power fails or drops to an
unacceptable voltage level.
UPU User Part Unavailable.
Useful part of burst That part of the burst used by the demodulator; differs from
the full burst because of the bit shift of the I and Q parts of the
GMSK signal.
USF Uplink State Flag.
USSD Unstructured Supplementary Service Data. The USSD
mechanism allows the MS user and a PLMN operator dened
application to communicate in a way which is transparent to
the MS and to intermediate network entities. The mechanism
allows development of PLMN specic supplementary services.
UTRAN UMTS Radio Access Network
UUS User-to-User Signalling supplementary service. The UUS
supplementary service allows a mobile subscriber to
send/receive a limited amount of information to/from another
PLMN or ISDN subscriber over the signalling channel in
association with a call to the other subscriber.
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 Videotex Access Point.
VBS Voice Broadcast Service. VBS allows the distribution of speech
(or other signals which can be transmitted via the speech
codec), generated by a service subscriber, into a predened
geographical area to all or a group of service subscribers
located in this area.
VC See Virtual Circuit.
VCO Voltage Controlled Oscillator. An oscillator whose clock
frequency is determined by the magnitude of the voltage
presented at its input. The frequency changes when the
voltage changes.
VCXO Voltage Controlled Crystal Oscillator.
VDU Visual Display Unit. A device used for the real-time temporary
display of computer output data. Monitor.
VGCS Voice Group Call Service.
Videotex The Videotex service is an interactive service, that by means of
proper access points and standardized procedures, provides
the access to data base information stored in host computers
external to the PLMN, via public telecommunication networks.
2006 Motorola, Inc.
June 2007
Virtual Circuit A connection between two devices, that functions as though
it is a direct connection, even though it may physically be
circuitous. The term is used most frequently to describe
connections between two hosts in a packet-switching network.
VLR Visitor Location Register. A GSM network element which
provides a temporary register for subscriber information for a
visiting subscriber. Often a part of the MSC.
VLSI Very Large Scale Integration (in ICs). The process of placing
between 100,000 and one million electronic components on
a single chip.
VMSC Visited MSC. (Recommendation not to be used).
vocoder Abbreviation for voice-coder. A device that usually consists of
a speech analyzer, which converts analog speech waveforms
into narrowband digital signals, and a speech synthesizer,
which converts the digital signals into articial speech sounds.
VOX Voice Operated Transmission. An acoustoelectric transducer
and a keying relay connected so that the keying relay is
actuated when sound, or voice energy above a certain
threshold is sensed by the transducer. A vox is used to
eliminate the need for push-to-talk operation of a transmitter by
using voice energy to turn on the transmitter
VPLMN Visited PLMN.
VSC Videotex Service Centre.
V(SD) Send state variable.
VSP Vehicular Speaker Phone.
VSWR Voltage Standing Wave Ratio. In a transmission line, the ratio
of maximum to minimum voltage in a standing wave pattern.
Note: The VSWR is a measure of impedance mismatch
between the transmission line and its load. The higher the
VSWR, the greater the mismatch. The minimum VSWR, i.e.,
that which corresponds to a perfect impedance match, is unity.
VTX host The components dedicated to Videotex service.
W - WWW
WAN Wide Area Network. A physical or logical network that provides
data communications to a larger number of independent users
than are usually served by a LAN and is usually spread over a
larger geographic area than that of a LAN. WANs may include
physical networks, such as ISDN networks, X.25 networks,
and T1 networks.
WPA Wrong Password Attempts (counter). Some supplementary
services have the option of the subscriber using a password.
If a password check is done with an incorrect password, the
WPA is incremented by one. If a password check is passed,
2006 Motorola, Inc.
8-71
June 2007
the WPA is set to zero. If the WPA exceeds the value three,
the subscriber will have to register a new password with the
service provider.
WS Work Station. The remote device via which O&M personnel
execute input and output transactions for network management
purposes.
WSF Work Station Function block.
WWW World Wide Web. An international, virtual-network-based
information service composed of Internet host computers that
provide on-line information in a specic hypertext format. WWW
servers provide hypertext metalanguage (HTML) formatted
documents using the hypertext transfer protocol, HTTP.
Information on the WWW is accessed with a hypertext browser.
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 dened in the OSI communication
model.
X.25 link A communications link which conforms to X.25 specications
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-dened speech encoding
and decoding. In terms of data transmission, the speech
transcoder interfaces the 64 kbit/s PCM in the land network to
the 13 kbit/s vocoder format used on the Air Interface. See
also RXCDR.
XCDR board The circuit board required to perform speech transcoding at
the BSS or (R)XCDR). Also known as the MSI (XCDR) board.
Interchangeable with the GDP board.
XFER Transfer.
XID eXchange IDentier.
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 specication for device-independent windowing operations
on bitmap display devices.
2006 Motorola, Inc.
June 2007
ZC
ZC Zone Code. Part of the RSZI. The ZC identies a regional
subscription zone as a pattern of allowed and not allowed
location areas uniquely within a PLMN.
2006 Motorola, Inc.
8-73
June 2007

Sys02 GSR9

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

Sys02 GSR9

Uploaded by

Copyright:

Available Formats

SYS02: Introduction to BSS Database GSR9

SYS02: Introduction to BSS Database GSR9

SYS02: Introduction to BSS Database GSR9

2006 Motorola, Inc.

enter portion of TDM highway managed: 0

Are DRIMS allowed on the highway: Yes / No

enter the cage number:

enter the slot number:

Enter the slot number

enter the cage number: 013 (BSS)

enter the slot number: BSS, BTSs: 617

enter the MSI type:

enter the slot number

Unrestricted 3200 Circuits, 600 Carriers

Unrestricted 4800 Circuits

GDP GDP GDP

Count Busy RACH

Count Busy RACH

enter the SITE id: 1100 or ts_switch

enter the unique DHP number in the cage:

enter the slot number:

enter the maximum number of DRIMs

enter the cabinet identi er:

equip < site number > DRI

enter the port to which the TCU is connected: 05

You might also like