GSM System Configuration

Installation and Configuration

GSR10
68P02901W17-T

2009 Motorola, Inc. All Rights Reserved.

Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no
liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in content
hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability
arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others. It is possible that this publication may contain references to, or
information about Motorola products (machines and programs), programming, or services that are not announced
in your country. Such references or information must not be construed to mean that Motorola intends to announce
such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include
or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right
to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,
any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the
Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a
product.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials
Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT
designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments
requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication
Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks

Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.

The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Office.

Jan 2010

Table
of
Contents

Contents

Installation and Configuration: GSM System Configuration

Revision history . . . . . . . . . . . .
Version information . . . . . . . .
Release information . . . . . . . .
Resolution of Service Requests . .
General information . . . . . . . . . .
Purpose . . . . . . . . . . . . . .
Cross references . . . . . . . . . .
Document banner definitions . . .
Text conventions . . . . . . . . . .
Contacting Motorola . . . . . . . . . .
24hour support . . . . . . . . . .
Ordering documents and CD-ROMs
Questions and comments . . . . .
Errors . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

4
4
4
4
5
5
5
5
6
7
7
7
7
7

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

1-2
1-2
1-2
1-3
1-4
1-4
1-5
1-7
1-9
1-10
1-11
1-11
1-11
1-11
1-12
1-13
1-14
1-23
1-23
1-23
1-23
1-24
1-24
1-24
1-24

Chapter 1: Configuration Management General Information

Recommendations for Configuration Management . . . .
Introduction to Configuration Management . . . . .
Recommended weekly procedures . . . . . . . . . .
Off-line and online network change recommendation
Working practice recommendation. . . . . . . . . .
Preventing remote login . . . . . . . . . . . . . . .
Command partitioning using the GUI . . . . . . . .
Tracking logged CM changes . . . . . . . . . . . .
Online Configuration Management setup . . . . . .
Interrogating the network using the COP GLU tool .
Management Information Base (MIB) . . . . . . . . . .
Definition of the MIB. . . . . . . . . . . . . . . . .
Initializing the MIB . . . . . . . . . . . . . . . . .
Backing up MIB configuration data . . . . . . . . .
Containment . . . . . . . . . . . . . . . . . . . . .
Containment rules . . . . . . . . . . . . . . . . . .
MIB locking . . . . . . . . . . . . . . . . . . . . .
Definition of a Network Element (NE) . . . . . . . . . .
Types of Network Element . . . . . . . . . . . . . .
Base Station System (BSS) . . . . . . . . . . . . . .
RXCDR . . . . . . . . . . . . . . . . . . . . . . . .
Uploading an NE database to the OMC-R . . . . . . . .
BSS and RXCDR databases . . . . . . . . . . . . .
When to upload an NE database . . . . . . . . . . .
Uploading the NE database to the OMC-R . . . . . .
68P02901W17-T
Jan 2010

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

Contents

Configuring network objects using the OMC-R GUI . . . . . . . . . . . .

Introduction to creating, editing, and deleting network objects . . . .
Activities available in Navigation Tree . . . . . . . . . . . . . . . . .
Selecting regions using the Navigation Tree . . . . . . . . . . . . . .
User access to OMC-R GUI functions . . . . . . . . . . . . . . . . .
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Navigating to a network object class or instance. . . . . . . . . . . . . .
Network object class and network object instance buttons . . . . . .
Introduction to using the Navigation Tree . . . . . . . . . . . . . . .
Navigating to the network object . . . . . . . . . . . . . . . . . . .
Representation of a navigation route to a network object . . . . . . .
Closing the Navigation Tree . . . . . . . . . . . . . . . . . . . . . .
Using the FIND option to locate a network object . . . . . . . . . . .
Using Detailed Views . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of Detailed Views . . . . . . . . . . . . . . . . . . . . .
Displaying Detailed Views with BSS or OMC-R names . . . . . . . . .
Creating a network object using the OMC-R GUI . . . . . . . . . . . . .
Overview of creating a network object using the Navigation Tree . . .
Creating the Detailed View for the network object . . . . . . . . . . .
Defining the parameter fields for the network object . . . . . . . . .
Saving information and closing the Detailed View . . . . . . . . . . .
Modifying a network object using the OMC-R GUI . . . . . . . . . . . . .
Introduction to modifying a network object using the Navigation Tree
Non-editable fields in Detailed Views . . . . . . . . . . . . . . . . .
Displaying and modifying a Detailed View . . . . . . . . . . . . . . .
Deleting a network object using the OMC-R GUI. . . . . . . . . . . . . .
Methods of deleting a network object . . . . . . . . . . . . . . . . .
Prerequisites for deleting network objects . . . . . . . . . . . . . . .
Deleting a network object from the Navigation Tree . . . . . . . . . .
Deleting a network object from a Detailed View . . . . . . . . . . . .
Remotely logging in to a BSS site from the OMC-R . . . . . . . . . . . .
Introduction to remote login to a BSS . . . . . . . . . . . . . . . . .
Maximum number of remote login sessions . . . . . . . . . . . . . .
Logging in remotely to a BSS . . . . . . . . . . . . . . . . . . . . .
Changing security level (for TTY interface commands). . . . . . . . . . .
Introduction to changing security levels . . . . . . . . . . . . . . . .
Using the TTY interface to change to security level 2 . . . . . . . . .
Remotely logging in to a BSS using WebMMI . . . . . . . . . . . . . . .
Introduction to WebMMI . . . . . . . . . . . . . . . . . . . . . . . .
WebMMI GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for WebMMI . . . . . . . . . . . . . . . . . . . . . . .
Setting up and using WebMMI . . . . . . . . . . . . . . . . . . . . .
Making wide area modifications . . . . . . . . . . . . . . . . . . . . . .
Introduction to wide area modifications . . . . . . . . . . . . . . . .
Wide area modifications using the TTY interface. . . . . . . . . . . .
Propagating cell parameters using the OMC-R GUI . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

1-26
1-26
1-26
1-26
1-27
1-27
1-28
1-28
1-28
1-28
1-29
1-29
1-29
1-30
1-30
1-30
1-32
1-32
1-32
1-33
1-33
1-34
1-34
1-34
1-34
1-37
1-37
1-37
1-37
1-38
1-39
1-39
1-39
1-39
1-43
1-43
1-43
1-45
1-45
1-45
1-46
1-46
1-49
1-49
1-49
1-50

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

2-4
2-4
2-4
2-4
2-5
2-5
2-6
2-8
2-9

Chapter 2: Configuring BSS Features

Frequency hopping . . . . . . . . . . . . . . . . . . . . . .
Overview of frequency hopping . . . . . . . . . . . . . .
Methods of configuring frequency hopping . . . . . . . .
Planning constraints of frequency hopping . . . . . . . .
Types of frequency hopping . . . . . . . . . . . . . . . .
Synthesizer frequency hopping (SFH) . . . . . . . . . . .
SFH guidelines (BCCH frequency excluded) with example.
SFH guidelines (BCCH frequency included) with example .
Baseband frequency hopping (BBH) . . . . . . . . . . . .

ii

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BBH guidelines with typical example . . . . . . . . . . . . . . . . .

Enhanced XBL (EXBL) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of Enhanced XBL . . . . . . . . . . . . . . . . . . . . . .
Assoc_BSS and Assoc_RXCDR devices . . . . . . . . . . . . . . . . .
CIC blocking and validation . . . . . . . . . . . . . . . . . . . . . .
Enabling CIC validation . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic Allocation of RXCDR-BSC Circuits (DARBC) . . . . . . . . . . .
Overview of dynamic allocation of RXCDR-BSC Circuits . . . . . . . .
BSC and RXCDR responsibilities . . . . . . . . . . . . . . . . . . . .
Auto-connect mode or backwards compatibility (static) mode . . . . .
Determining the number of XBLs required. . . . . . . . . . . . . . .
RXCDR-BSC dynamic allocation parameters . . . . . . . . . . . . . .
Methods of configuring dynamic allocation of RXCDR-BSC circuits . .
Configuring RXCDR-BSC dynamic allocation using the TTY interface .
Dynamic allocation of BSC-BTS Backing Resources (DYNET) . . . . . . .
Overview of BSC-BTS dynamic allocation (DYNET) . . . . . . . . . .
RSL TCHs used for backhaul. . . . . . . . . . . . . . . . . . . . . .
Prerequisites to enabling BSC-BTS dynamic allocation at a BTS . . . .
BSC-BTS dynamic allocation parameters . . . . . . . . . . . . . . .
Displaying if BSC-BTS dynamic allocation is unrestricted at a BSS . .
Enabling BSC-BTS dynamic allocation at a BTS . . . . . . . . . . . .
Displaying details of an equipped BTS using the TTY interface . . . .
Other dynamic allocation features . . . . . . . . . . . . . . . . . . .
MSC to BSS overload control . . . . . . . . . . . . . . . . . . . . . . .
Overview of MSC to BSS overload Control . . . . . . . . . . . . . . .
Enabling MSC to BSS overload control . . . . . . . . . . . . . . . .
Related overload control statistic . . . . . . . . . . . . . . . . . . .
Timer parameters for mobile access class barring and unbarring . . .
Methods of configuring MSC to BSS overload control . . . . . . . . .
Configuring MSC to BSS overload control using the TTY interface . .
Encryption algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to encryption algorithms . . . . . . . . . . . . . . . . .
Prerequisites for configuring encryption algorithms . . . . . . . . . .
Encryption algorithm procedures . . . . . . . . . . . . . . . . . . .
Activating the encryption algorithms . . . . . . . . . . . . . . . . .
Prioritizing the encryption algorithms . . . . . . . . . . . . . . . . .
Displaying the prioritized list . . . . . . . . . . . . . . . . . . . . .
Dual band cells option . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the single BCCH for a dual band cells feature . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . .
Prerequisites and restrictions for enabling the Dual Band Option . . .
Dual band cells option parameters . . . . . . . . . . . . . . . . . . .
Overview of configuring single BCCH for dual band cells feature . . .
Methods of configuring the dual band cells option . . . . . . . . . .
Configuring the dual band cells option using the TTY interface . . . .
GPRS and EGPRS coding schemes . . . . . . . . . . . . . . . . . . . . .
Introduction to GPRS CS3/CS4 . . . . . . . . . . . . . . . . . . . .
Introduction to EGPRS MCS . . . . . . . . . . . . . . . . . . . . . .
GPRS and EGPRS coding scheme parameters . . . . . . . . . . . . .
Methods for configuring GPRS and EGPRS coding schemes . . . . . .
Configuring GPRS and EGPRS coding schemes using the TTY interface
Short Message Service - Cell Broadcast . . . . . . . . . . . . . . . . . .
Overview of SMS-CB . . . . . . . . . . . . . . . . . . . . . . . . . .
Message details for SMS-CB . . . . . . . . . . . . . . . . . . . . . .
SMS-CB parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
Methods of configuring SMS-CB . . . . . . . . . . . . . . . . . . . .
Configuring SMS-CB using the TTY interface . . . . . . . . . . . . .
Short Message Service - Point-To-Point . . . . . . . . . . . . . . . . . .

68P02901W17-T
Jan 2010

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2-10
2-11
2-11
2-11
2-12
2-12
2-13
2-13
2-13
2-14
2-15
2-16
2-17
2-17
2-19
2-19
2-19
2-20
2-20
2-21
2-21
2-21
2-22
2-23
2-23
2-23
2-23
2-23
2-24
2-25
2-26
2-26
2-26
2-26
2-26
2-27
2-27
2-28
2-28
2-30
2-30
2-31
2-35
2-36
2-37
2-39
2-39
2-39
2-40
2-43
2-44
2-45
2-45
2-45
2-46
2-48
2-48
2-53

iii

Contents

Introduction to setting up SMS-PTP . . . . . . . . . . . . . . . .

SMS-PTP procedures . . . . . . . . . . . . . . . . . . . . . . .
SMS-PTP prerequisites . . . . . . . . . . . . . . . . . . . . . .
Enabling and disabling MS originated Point to Point SMS at a site
Displaying the state of MS originated Point to Point SMS at a site .
Enabling and disabling MS terminated SMS-PTP at a site . . . . .
Displaying the state of MS terminated SMS-PTP at a site . . . . .
Specifying the downlink logical channel . . . . . . . . . . . . . .
Displaying the DOWNLINK LOGICAL CHANNEL . . . . . . . . .
Preventive Cyclic Retransmission (PCR) . . . . . . . . . . . . . . . .
Introduction to PCR . . . . . . . . . . . . . . . . . . . . . . . .
Range and default values for Timers . . . . . . . . . . . . . . . .
Range and default values for N-value parameters . . . . . . . . .
Methods of configuring PCR . . . . . . . . . . . . . . . . . . . .
Configuring PCR using the TTY interface . . . . . . . . . . . . .
MSC initiated IMSI and IMEI call trace . . . . . . . . . . . . . . . .
Introduction to MSC initiated call trace . . . . . . . . . . . . . .
Controlling an MSC initiated call trace . . . . . . . . . . . . . .
Naming of call trace log files. . . . . . . . . . . . . . . . . . . .
Call trace flow control . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of call trace flow control . . . . . . . . . . . . . . . . .
Call trace flow control parameters . . . . . . . . . . . . . . . . .
Methods of configuring call trace flow control . . . . . . . . . . .
Configuring call trace flow control using the TTY interface . . . .
GPRS Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Feature Description . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced Circuit Error Rate Monitor (ECERM) . . . . . . . . . . . .
Overview of ECERM . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to configuring ECERM. . . . . . . . . . . . . . . .
Determining whether ECERM has been enabled . . . . . . . . . .
ECERM parameters . . . . . . . . . . . . . . . . . . . . . . . .
Methods for configuring ECERM. . . . . . . . . . . . . . . . . .
Configuring ECERM using the TTY interface . . . . . . . . . . .
Advanced Load Management for EGSM . . . . . . . . . . . . . . . .
Introduction to Advanced Load Management for EGSM . . . . . .
Restrictions and dependencies to ALM for EGSM . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . .
ALM for EGSM parameters . . . . . . . . . . . . . . . . . . . .
Methods of configuring ALM for EGSM . . . . . . . . . . . . . .
Configuring ALM for EGSM using the TTY interface . . . . . . . .
Network Controlled Cell Reselection. . . . . . . . . . . . . . . . . .
Description of Network Controlled Cell Reselection (NCCR) . . . .
Determining whether Network Controlled Cell Reselection (NCCR)
Network Controlled Cell Reselection parameters . . . . . . . . .
NCCR changes to Detailed Views . . . . . . . . . . . . . . . . .
Methods for configuring NCCR . . . . . . . . . . . . . . . . . .
Configuring NCCR using the TTY interface . . . . . . . . . . . .
GPRS Interleaving TBFs . . . . . . . . . . . . . . . . . . . . . . . .
Description of TBF . . . . . . . . . . . . . . . . . . . . . . . . .
Description of GPRS interleaving TBFs . . . . . . . . . . . . . .
Delayed Downlink TBF Release . . . . . . . . . . . . . . . . . .
Delayed Downlink TBF Release Control . . . . . . . . . . . . . .
Delayed Uplink TBF Release . . . . . . . . . . . . . . . . . . . .
GPRS interleaving TBFs capacity . . . . . . . . . . . . . . . . .
GPRS interleaving TBFs parameters . . . . . . . . . . . . . . . .
Impact of GPRS interleaving TBFs on a BSS . . . . . . . . . . . .
Methods for configuring GPRS interleaving TBFs . . . . . . . . .
Configuring GPRS interleaving TBFs using the TTY interface . . .

iv

. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
is enabled
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2-53
2-53
2-53
2-54
2-54
2-54
2-55
2-55
2-55
2-56
2-56
2-56
2-57
2-57
2-57
2-60
2-60
2-60
2-61
2-63
2-63
2-63
2-65
2-65
2-68
2-68
2-70
2-70
2-70
2-71
2-71
2-76
2-77
2-78
2-78
2-78
2-78
2-79
2-79
2-79
2-81
2-81
2-82
2-82
2-85
2-85
2-86
2-89
2-89
2-89
2-89
2-90
2-90
2-90
2-90
2-92
2-92
2-93

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Enhanced BSC Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to the Enhanced BSC Capacity feature . . . . . . . . . . . . .
Determining whether Enhanced BSC Capacity is enabled . . . . . . . . . .
Inter-Radio Access Technology (Inter-RAT) Handover . . . . . . . . . . . . . .
Overview of Inter-RAT Handover. . . . . . . . . . . . . . . . . . . . . . .
Inter-RAT Handover dependencies . . . . . . . . . . . . . . . . . . . . . .
Enhanced Inter-RAT Handover feature. . . . . . . . . . . . . . . . . . . .
Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . .
Inter-RAT Handover and Enhanced Inter-RAT Handover parameters . . . .
Methods of configuring Inter-RAT Handover . . . . . . . . . . . . . . . . .
Configuring Inter-RAT Handover using the TTY interface . . . . . . . . . .
GSM location services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of Location Services . . . . . . . . . . . . . . . . . . . . . . .
Location services and the LMTL device . . . . . . . . . . . . . . . . . . .
Determining whether location services is unrestricted. . . . . . . . . . . .
Location services parameters . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions for Location Services parameters . . . . . . . . . . . . . . . .
Methods for configuring Location Services . . . . . . . . . . . . . . . . .
Configuring GSM Location Services using the TTY interface. . . . . . . . .
Enhanced GPRS One Phase Access . . . . . . . . . . . . . . . . . . . . . . .
Overview of Enhanced GPRS One Phase Access . . . . . . . . . . . . . . .
Enhanced GPRS One Phase Access dependencies . . . . . . . . . . . . . .
Enhanced GPRS One Phase Access parameters . . . . . . . . . . . . . . .
Methods of configuring Enhanced GPRS one phase access . . . . . . . . .
Configuring Enhanced GPRS one phase access using the TTY interface . . .
PBCCH/PCCCH feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of PBCCH/PCCCH feature . . . . . . . . . . . . . . . . . . . . .
Prerequisites to configuring PBCCH/PCCCH. . . . . . . . . . . . . . . . .
Determining whether PBCCH/PCCCH is unrestricted at the BSS . . . . . .
PBCCH/PCCCH parameters . . . . . . . . . . . . . . . . . . . . . . . . .
Methods for configuring PBCCH/PCCCH . . . . . . . . . . . . . . . . . .
Configuring PBCCH/PCCCH using TTY interface . . . . . . . . . . . . . .
Adaptive Multi-Rate (AMR) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the AMR feature . . . . . . . . . . . . . . . . . . . . . . . .
Link Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AMR Full Rate - MS Monitor function . . . . . . . . . . . . . . . . . . . .
AMR Enhanced GDP feature . . . . . . . . . . . . . . . . . . . . . . . . .
AMR Enhanced Capacity feature. . . . . . . . . . . . . . . . . . . . . . .
Technical description of AMR . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for enabling AMR . . . . . . . . . . . . . . . . . . . . . . .
Configuring AMR at a cell . . . . . . . . . . . . . . . . . . . . . . . . . .
Determining whether the AMR features are unrestricted . . . . . . . . . .
AMR parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Methods of configuring AMR. . . . . . . . . . . . . . . . . . . . . . . . .
Configuring AMR using the TTY interface . . . . . . . . . . . . . . . . . .
GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for enabling GSM HR . . . . . . . . . . . . . . . . . . . . .
Configuring GSM HR . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . .
Determining whether the GSM HR feature is unrestricted . . . . . . . . . .
GSM HR parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPRS Seamless Cell Reselection . . . . . . . . . . . . . . . . . . . . . . . . .
Description of GPRS Seamless Cell Reselection (SCR) . . . . . . . . . . . .
Determining whether GPRS Seamless Cell Reselection (SCR) is unrestricted
GPRS Seamless Cell Reselection parameters . . . . . . . . . . . . . . . .
Methods for configuring SCR . . . . . . . . . . . . . . . . . . . . . . . .
Configuring SCR using TTY interface . . . . . . . . . . . . . . . . . . . .

68P02901W17-T
Jan 2010

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2-94
2-94
2-94
2-95
2-95
2-95
2-96
2-96
2-96
2-96
2-102
2-102
2-104
2-104
2-104
2-104
2-105
2-111
2-111
2-111
2-113
2-113
2-113
2-113
2-115
2-115
2-117
2-117
2-118
2-119
2-119
2-127
2-128
2-129
2-129
2-130
2-131
2-131
2-131
2-131
2-132
2-132
2-132
2-133
2-137
2-137
2-140
2-140
2-140
2-140
2-140
2-141
2-142
2-142
2-142
2-143
2-143
2-144

Contents

Current Bucket Level (CBL) feature . . . . . . . . . . . . . . . . . . . . . . .

Overview of the Current Bucket Level feature . . . . . . . . . . . . . . . .
Prerequisite for Current Bucket Level feature . . . . . . . . . . . . . . . .
Current Bucket Level parameters . . . . . . . . . . . . . . . . . . . . . .
Enhanced Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced Scheduling sub-features . . . . . . . . . . . . . . . . . . . . .
Enhanced Scheduling dependencies . . . . . . . . . . . . . . . . . . . . .
Enhanced Scheduling parameters . . . . . . . . . . . . . . . . . . . . . .
Methods of configuring enhanced scheduling . . . . . . . . . . . . . . . .
Configuring enhanced scheduling using the TTY interface . . . . . . . . . .
Intelligent Multi Layer Resource Management (IMRM) . . . . . . . . . . . . .
Prerequisites to configuring Intelligent Multi Layer Resource Management .
Intelligent Multi Layer Resource Management parameters . . . . . . . . .
Quality of Service (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to configuring QoS. . . . . . . . . . . . . . . . . . . . . . .
Quality of Service parameters . . . . . . . . . . . . . . . . . . . . . . . .
Network Assisted Cell Change (NACC) . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interaction with QoS (Quality of Service) . . . . . . . . . . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . .
Network Assisted Cell Change (NACC) parameters . . . . . . . . . . . . .
Enhanced Multi-level Precedence and Pre-emption (eMLPP) . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . .
eMLPP parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fast Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . .
Fast Call Setup parameters . . . . . . . . . . . . . . . . . . . . . . . . .
RSL Congestion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSL congestion control parameters . . . . . . . . . . . . . . . . . . . . .
VersaTRAU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Permissible values for RTF backhaul timeslots . . . . . . . . . . . . . . . .
VersaTRAU parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .
Feature Capacity Licensing and Audit . . . . . . . . . . . . . . . . . . . . . .
Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration and operation . . . . . . . . . . . . . . . . . . . . . . . . .
Improved Timeslot Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . .
ITS parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPRS - Suspend/Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of GPRS Suspend/Resume . . . . . . . . . . . . . . . . . . . .
Description of GPRS Suspend/Resume . . . . . . . . . . . . . . . . . . .
Measuring Suspend/Resume statistic . . . . . . . . . . . . . . . . . . . .
GPRS - Suspend/Resume dependencies . . . . . . . . . . . . . . . . . . .
GPRS - Suspend/Resume parameters . . . . . . . . . . . . . . . . . . . .
Configuring GPRS - Suspend/Resume parameter using the TTY interface . .
Increased Network Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . .

vi

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2-145
2-145
2-145
2-145
2-146
2-146
2-146
2-146
2-146
2-148
2-148
2-150
2-151
2-151
2-154
2-154
2-154
2-154
2-162
2-162
2-162
2-163
2-163
2-163
2-165
2-165
2-165
2-165
2-166
2-168
2-168
2-168
2-168
2-168
2-170
2-170
2-170
2-170
2-172
2-172
2-172
2-173
2-174
2-175
2-175
2-175
2-176
2-176
2-176
2-176
2-178
2-178
2-178
2-178
2-179
2-179
2-180
2-181

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Overview of Increased Network Capacity . . . . . . . . . . . . . . . . . . . . . . .

Determining whether Increased Network Capacity is enabled . . . . . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSC High Load Protection Mechanism Phase 2 . . . . . . . . . . . . . . . . . . . . . .
Overview of BSC High Load Protection Mechanism Phase 2 . . . . . . . . . . . . . .
BSC High Load Protection Mechanism Phase 2 parameters . . . . . . . . . . . . . .
Configuring BSC High Load Protection Mechanism Phase 2 . . . . . . . . . . . . . .
HSP MTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSP MTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to configuring HSP MTL . . . . . . . . . . . . . . . . . . . . . . . . .
HSP MTL parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software patching and PCU Software Upgrade with no BSC Outage. . . . . . . . . . . .
Overview of Software patching and PCU Software Upgrade with no BSC Outage . . .
Software patching and PCU Software Upgrade with no BSC Outage parameters . . .
PCU hardware to increase GPRS capacity . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU hardware to increase GPRS capacity parameters . . . . . . . . . . . . . . . . .
Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High Bandwidth interconnection between BSC and PCU (PSI). . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High Bandwidth interconnection between BSC and PCU parameters . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Increase the Throughput of PRP with the PCU . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Increase the Throughput of PRP with the PCU parameters . . . . . . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support of Incell as an optional feature . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support of Incell as an optional feature parameters . . . . . . . . . . . . . . . . . .
BSP CPU utilization reduction for higher call handling capacity . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS User Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS User Security Management parameters. . . . . . . . . . . . . . . . . . . . . .
Logging in to the BSS through a local maintenance terminal using the login command
verify_field_pass and .field_pass utilities . . . . . . . . . . . . . . . . . . . . . . . .
Setting fieldeng_always_enabled parameter . . . . . . . . . . . . . . . . . . . . . .
Password management and banner text management . . . . . . . . . . . . . . . . .
Quality of Service Phase II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quality of Service Phase II parameters . . . . . . . . . . . . . . . . . . . . . . . .
CTU2-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CTU2-D dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CTU2-D parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell OOS Timer Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell OOS Timer Enhancement parameters . . . . . . . . . . . . . . . . . . . . . . .
TDM Availability Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TDM Availability Enhancements parameters . . . . . . . . . . . . . . . . . . . . . .
TD-SCDMA and GSM interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TD-SCDMA and GSM interworking dependencies . . . . . . . . . . . . . . . . . . .
TD-SCDMA and GSM interworking parameters . . . . . . . . . . . . . . . . . . . .
Extended Uplink TBF (Temporary Block Flow) . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

68P02901W17-T
Jan 2010

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2-181
2-181
2-182
2-183
2-183
2-183
2-183
2-185
2-185
2-185
2-185
2-188
2-188
2-188
2-190
2-190
2-190
2-193
2-194
2-194
2-194
2-196
2-197
2-197
2-197
2-198
2-199
2-199
2-199
2-200
2-200
2-201
2-201
2-202
2-204
2-205
2-206
2-207
2-212
2-212
2-213
2-225
2-225
2-226
2-227
2-228
2-229
2-229
2-229
2-230
2-230
2-230
2-231
2-231
2-231
2-231
2-234
2-234

vii

Contents

Extended Uplink TBF (Temporary Block Flow) parameters . . . . . . . . . . . . .

Interaction with other features . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extended Dynamic Allocation Medium Access Mode (EDMAC) . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extended Dynamic Allocation Medium Access Mode (EDMAC) parameters . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adjustable FER Bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adjustable FER Bins parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .
Critical Statistics Reporting in 5 minutes . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Critical Statistics Reporting in 5 minutes parameters . . . . . . . . . . . . . . . .
SW enabler for PA bias switch on/off on CTU2D . . . . . . . . . . . . . . . . . . . . .
Overview of SW enabler for PA bias switch on/off on CTU2D . . . . . . . . . . . .
Enabling and disabling the SW enabler for PA bias switch on/off on CTU2D feature .
SW enabler for PA bias switch on/off on CTU2D parameters . . . . . . . . . . . . .
Dual Abis aware BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dual Abis aware BTS parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
Extended Range Cell (ERC) for Data . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of Cage Management . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling and disabling the Cage Management feature . . . . . . . . . . . . . . .
Cage Management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operability impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A5/1 Security Hardening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dummy Byte Randomization . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Immediate SDCCH Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Periodic Traffic Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gb over IP feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Increase RSL-LCF capacity on GPROC3/GPROC3-2 . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CTU4 and RCTU4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of CTU4 and RCTU4 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CTU4 and RCTU4 parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2-234
2-235
2-236
2-236
2-236
2-237
2-238
2-238
2-238
2-239
2-239
2-239
2-241
2-241
2-241
2-241
2-243
2-243
2-243
2-244
2-244
2-246
2-246
2-246
2-246
2-247
2-248
2-248
2-248
2-249
2-251
2-253
2-253
2-253
2-253
2-256
2-256
2-256
2-257
2-257
2-257
2-258
2-263

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

3-2
3-2
3-2
3-3
3-6
3-7
3-7
3-7
3-7
3-9

Chapter 3: Configuring Network, OMC-R, and MSC Instances

Configuring a network instance . . . . . . . . . . . . . .
Introduction to configuring a network instance . . . .
Creating a Network instance using the OMC-R GUI . .
Network Detailed View fields . . . . . . . . . . . . .
Deleting a Network instance . . . . . . . . . . . . . .
Configuring an OMC-R or MSC instance . . . . . . . . . .
Introduction to configuring an OMC-R or MSC instance
Creating an OMC-R or MSC instance . . . . . . . . .
OMC and MSC Detailed View fields . . . . . . . . . .
Deleting an OMC-R or MSC . . . . . . . . . . . . . .

viii

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Contents

Chapter 4: Configuring a BSS/RXCDR

Overview of adding a BSS or RXCDR . . . . . . . . . . . . . . .
Introduction to adding a BSS/RXCDR . . . . . . . . . . . . .
Prerequisites for adding BSS/RXCDR . . . . . . . . . . . . .
Overview procedure for adding BSS/RXCDR to the network . .
Creating a BSS using the OMC-R GUI . . . . . . . . . . . . . . .
Introduction to creating a BSS using OMC-R GUI . . . . . . .
Prerequisites to creating a BSS . . . . . . . . . . . . . . . .
Creating a BSS using the OMC-R GUI . . . . . . . . . . . . .
BSS Detailed View fields . . . . . . . . . . . . . . . . . . . .
Modifying BSS details using the OMC-R GUI . . . . . . . . .
Creating an RXCDR using the OMC-R GUI . . . . . . . . . . . . .
Prerequisites to creating an RXCDR . . . . . . . . . . . . . .
Creating an RXCDR using the OMC-R GUI . . . . . . . . . . .
Modifying RXCDR details using the OMC-R GUI . . . . . . . .
Creating a BSS/RXCDR database . . . . . . . . . . . . . . . . .
Definition of BSS/RXCDR database . . . . . . . . . . . . . .
BSS/RXCDR database types . . . . . . . . . . . . . . . . . .
Configuration Management database object . . . . . . . . . .
Database script file . . . . . . . . . . . . . . . . . . . . . .
NE database checks . . . . . . . . . . . . . . . . . . . . . .
Typical database directory structure. . . . . . . . . . . . . .
Deleting a BSS/RXCDR. . . . . . . . . . . . . . . . . . . . . . .
Introduction to deleting a BSS/RXCDR. . . . . . . . . . . . .
Impact of deleting a BSS on an Assoc_BSS. . . . . . . . . . .
Impact of deleting an RXCDR on an Assoc_RXCDR . . . . . .
Prerequisites before deleting a BSS/RXCDR . . . . . . . . . .
Removing a BSS/RXCDR from the network . . . . . . . . . .
Deleting a BSS/RXCDR from the OMC-R . . . . . . . . . . . .
Deleting a BSS/RXCDR at the packet switch/MUX . . . . . . . . .
Introduction to Deleting the BSS/RXCDR at the packet switch.
Configuration changes at the packet switch . . . . . . . . . .
Deleting the routing table entry . . . . . . . . . . . . . . . .
Removing the cabling between packet switch and MUX . . . .
Configuration changes at the MUX . . . . . . . . . . . . . .
Dependencies on NE removal from the MUX . . . . . . . . .
Removing the NE from the MUX . . . . . . . . . . . . . . . .
Removing the NE link to the MUX . . . . . . . . . . . . . . .
Equipping cabinets and cages at a BSS site . . . . . . . . . . . .
Overview of equipping cabinets and cages at a BSS . . . . . .
Horizonmicro2 and Horizoncompact2 BTS cabinets . . . . . .
Horizon II macro and Horizon II macro extension cabinets . .
Horizon II mini and Horizon II macro cabinets . . . . . . . . .
Configuring a cabinet . . . . . . . . . . . . . . . . . . . . . . .
Creating a cabinet for a site using the OMC-R GUI . . . . . .
Cabinet Detailed View fields . . . . . . . . . . . . . . . . . .
Equipping a cabinet using the TTY interface . . . . . . . . . .
Configuring a cage . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a cage using the OMC-R GUI . . . . . . . . . . . . .
Cage Detailed View fields . . . . . . . . . . . . . . . . . . .
Equipping a cage from the TTY interface . . . . . . . . . . .
Configuring an RXCDR cabinet . . . . . . . . . . . . . . . . . .
Overview of configuring an RXCDR cabinet . . . . . . . . . .
Creating an RXCDR cabinet using the OMC-R GUI . . . . . .
Equipping an RXCDR cabinet using the TTY interface . . . . .
Configuring an RXCDR cage . . . . . . . . . . . . . . . . . . . .
Overview of configuring an RXCDR cage. . . . . . . . . . . .

68P02901W17-T
Jan 2010

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

4-2
4-2
4-2
4-3
4-6
4-6
4-6
4-7
4-8
4-38
4-39
4-39
4-39
4-40
4-41
4-41
4-41
4-41
4-41
4-42
4-43
4-44
4-44
4-44
4-44
4-44
4-45
4-45
4-48
4-48
4-48
4-48
4-48
4-49
4-49
4-49
4-50
4-51
4-51
4-51
4-51
4-52
4-54
4-54
4-54
4-58
4-59
4-59
4-59
4-61
4-62
4-62
4-62
4-63
4-64
4-64

ix

Contents

RXCDR cage numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating an RXCDR cage using the OMC-R GUI . . . . . . . . . . . . . . . .
Example of equipping an RXCDR cabinet and cage using the TTY interface . . . .
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overall procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipping the RXCDR cabinet using the TTY interface . . . . . . . . . . . .
Equipping the RXCDR cage using the TTY interface . . . . . . . . . . . . . .
Configuring an Assoc_BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of an Assoc_BSS . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to creating an Assoc_BSS . . . . . . . . . . . . . . . . . . . .
Creating an Assoc_BSS using the OMC-R GUI . . . . . . . . . . . . . . . . .
Assoc_BSS Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . .
Deleting an Assoc_BSS using the OMC-R GUI . . . . . . . . . . . . . . . . .
Creating an Assoc_BSS using the TTY interface . . . . . . . . . . . . . . . .
Displaying Assoc_BSS details using the TTY interface . . . . . . . . . . . . .
Setting Assoc_BSS parameters using the TTY interface . . . . . . . . . . . .
Deleting an Assoc_BSS using the TTY interface . . . . . . . . . . . . . . . .
Configuring an Assoc_RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of an Assoc_RXCDR . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to creating an Assoc_RXCDR . . . . . . . . . . . . . . . . . .
Creating an Assoc_RXCDR using the OMC-R GUI . . . . . . . . . . . . . . .
Assoc_RXCDR Detailed View fields. . . . . . . . . . . . . . . . . . . . . . .
Creating an Assoc_RXCDR using the TTY interface . . . . . . . . . . . . . .
Displaying Assoc_RXCDR details using the TTY interface . . . . . . . . . . .
Enabling/Disabling CIC Validation at an Assoc_RXCDR using the TTY interface
Changing eac_mode and cic_block_thresh . . . . . . . . . . . . . . . . . . .
Changing AMR Half Rate mode using the TTY interface . . . . . . . . . . . .
Changing GSM Half Rate mode using the TTY interface . . . . . . . . . . . .
Deleting an Assoc_RXCDR using the OMC-R GUI . . . . . . . . . . . . . . .
Deleting an Assoc_RXCDR using the TTY interface . . . . . . . . . . . . . .
Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR . . . . . . . . . . . . . .
Introduction to changing the NE ID of an AXCDR or ABSS . . . . . . . . . .
Phases in the change assoc NE ID process. . . . . . . . . . . . . . . . . . .
Change assoc NE ID process log files . . . . . . . . . . . . . . . . . . . . .
Prerequisites to changing an associated NE ID . . . . . . . . . . . . . . . .
Restrictions to changing an NE ID . . . . . . . . . . . . . . . . . . . . . . .
Changing the NE ID of an ABSS or AXCDR using the OMC-R GUI . . . . . . .
Viewing other log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resuming a suspended change assoc NE ID process. . . . . . . . . . . . . .
Configuring DYNETs and DYNETGroups . . . . . . . . . . . . . . . . . . . . . .
DYNET device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DYNETGroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DYNETGroup and DYNET topics . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a DYNETGroup . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to creating a DYNETGroup . . . . . . . . . . . . . . . . . . .
Creating a DYNETGroup using the OMC-R GUI . . . . . . . . . . . . . . . .
DYNETGroup Detailed View fields . . . . . . . . . . . . . . . . . . . . . . .
Equipping a DYNETGroup using the TTY interface . . . . . . . . . . . . . .
Deleting a DYNETGroup using the OMC-R GUI . . . . . . . . . . . . . . . .
Configuring a DYNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Path devices for a DYNET . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to creating a DYNET. . . . . . . . . . . . . . . . . . . . . . .
Creating a DYNET using the OMC-R GUI . . . . . . . . . . . . . . . . . . .
DYNET Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying and deleting a DYNET using the OMC-R GUI . . . . . . . . . . . .
Configuring a DYNET using the TTY interface . . . . . . . . . . . . . . . . .
Reparenting a BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

4-64
4-64
4-65
4-65
4-65
4-66
4-66
4-67
4-68
4-68
4-68
4-68
4-69
4-70
4-70
4-71
4-71
4-71
4-72
4-72
4-72
4-72
4-73
4-76
4-76
4-76
4-77
4-78
4-78
4-79
4-79
4-80
4-80
4-80
4-81
4-81
4-82
4-82
4-85
4-88
4-90
4-90
4-91
4-91
4-92
4-92
4-92
4-92
4-93
4-93
4-94
4-94
4-94
4-94
4-95
4-97
4-97
4-100

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Contents

Overview of reparenting a BSS . . . . . . . . . . . . . . . . . .

Preserving SITE names . . . . . . . . . . . . . . . . . . . . . .
Reparenting a BSS to a different OMC-R. . . . . . . . . . . . . . . .
Prerequisites to reparenting a BSS to a different OMC-R . . . . .
Reparenting a BSS to a different OMC-R. . . . . . . . . . . . . .
Reparenting a BSS to a different RXCDR (same OMC-R). . . . . . . .
Prerequisites for assigning a BSS to a different RXCDR . . . . . .
Reparenting a BSS to a different RXCDR . . . . . . . . . . . . .
Reparenting an RXCDR to a different MSC . . . . . . . . . . . . . .
Introduction to reparenting an RXCDR to a different MSC. . . . .
Reparenting RXCDR commslinks . . . . . . . . . . . . . . . . .
Checking the software version for a BSS/RXCDR/OMC-R . . . . . . .
Software version number format. . . . . . . . . . . . . . . . . .
Checking a single NE using the OMC-R GUI . . . . . . . . . . . .
Checking multiple NEs using the OMC-R GUI . . . . . . . . . . .
Checking a single NE and multiple NEs using cmutil . . . . . . .
Checking OMC-R software load version . . . . . . . . . . . . . .
Checking NE software load versions using disp_version command

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

4-100
4-100
4-101
4-101
4-101
4-104
4-104
4-104
4-106
4-106
4-106
4-108
4-108
4-108
4-109
4-109
4-109
4-109

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

5-2
5-2
5-2
5-2
5-3
5-3
5-3
5-5
5-5
5-5
5-7
5-7
5-8
5-8
5-10
5-10
5-10
5-10
5-12
5-13
5-14
5-15
5-15
5-15
5-15
5-17
5-17
5-17
5-17
5-18
5-19
5-19
5-19
5-19
5-19
5-20
5-22

Chapter 5: Configuring Connectivity

Checking BSS to MSC (Through RXCDR) connectivity . . .
BSS to MSC connectivity. . . . . . . . . . . . . . . .
Connection report . . . . . . . . . . . . . . . . . . .
Checking BSS connections . . . . . . . . . . . . . . .
Checking RXCDR connections . . . . . . . . . . . . .
Creating and extracting CommsLink details . . . . . .
Checking BSS to RXCDR connectivity . . . . . . . . .
Configuring a Conn_Link . . . . . . . . . . . . . . . . . .
Creating a Conn_Link using the OMC-R GUI . . . . . .
Conn_Link Detailed View fields . . . . . . . . . . . .
Deleting a Conn_Link using the OMC-R GUI . . . . . .
Adding a Conn_Link using the TTY interface . . . . . .
Displaying connectivity using the TTY interface . . . .
Deleting a Conn_Link using the TTY interface . . . . .
Configuring a CommsLink using the OMC-R GUI . . . . .
Introduction to configuring a CommsLink . . . . . . .
Autocreation and deletion of CommsLinks . . . . . .
Creating a CommsLink using the OMC-R GUI . . . . .
CommsLink Detailed View fields . . . . . . . . . . . .
Filtering the CommsLink list window . . . . . . . . .
Deleting a CommsLink using the OMC-R GUI . . . . .
Checking RXCDR/BSS to OMC-R (OML) connectivity . . .
Overview to OML connectivity . . . . . . . . . . . . .
Checking OMLs for a single NE using the OMC-R GUI.
Checking OMLs for multiple NEs using SQL . . . . . .
DTE X.121 addresses at the OMC-R . . . . . . . . . . . .
Introduction to DTE X.121 addresses . . . . . . . . .
x25_config file location. . . . . . . . . . . . . . . . .
x25_config file fields . . . . . . . . . . . . . . . . . .
x25_config file entries . . . . . . . . . . . . . . . . .
Assigning DTE X.121 addresses at the NE . . . . . . . . .
Introduction to assigning DTE X.121 addresses . . . .
Setting X.121 addresses . . . . . . . . . . . . . . . .
Slot: port settings for OMLs . . . . . . . . . . . . . .
Setting OML addresses using the TTY interface . . . .
OMC-R addresses - general rules . . . . . . . . . . .
Modifying configurations on A, M, and Mobis interfaces . .

68P02901W17-T
Jan 2010

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

xi

Contents

Introduction to A, M, Mobis interfaces . . . . . . . . . . . . . . . . . .

Methods for modifying configurations on A, M, and Mobis interfaces . .
Prerequisites to modifying A, M, and Mobis interfaces. . . . . . . . . .
Displaying interface status . . . . . . . . . . . . . . . . . . . . . . . .
Equipping and unequipping A and M interfaces using the TTY interface.
Modifying the Mobis interface using the TTY interface . . . . . . . . .

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

5-22
5-22
5-22
5-23
5-23
5-23

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

6-2
6-2
6-2
6-2
6-3
6-5
6-5
6-6
6-6
6-6
6-7
6-8
6-8
6-8
6-8
6-9
6-14
6-15
6-16
6-16
6-16
6-17
6-17
6-17
6-18
6-18
6-18
6-18
6-19
6-20
6-21
6-22
6-22
6-22
6-22
6-24
6-24
6-24
6-24
6-25
6-26
6-26
6-27
6-27
6-27
6-28
6-29
6-29
6-30

Chapter 6: Configuring a PCU for GPRS

Introduction to the PCU and its devices . . . . . . . . . . . . . .
Overview of GPRS . . . . . . . . . . . . . . . . . . . . . . .
Introduction to PCU . . . . . . . . . . . . . . . . . . . . . .
List of PCU contained devices . . . . . . . . . . . . . . . . .
PCU equipage hierarchy chart . . . . . . . . . . . . . . . . .
PCU contained devices in the Navigation Tree . . . . . . . .
PCU contained devices to be equipped. . . . . . . . . . . . .
Overview of configuring a PCU and its devices . . . . . . . . . .
Recommended method for configuring a PCU . . . . . . . . .
Other PCU configuration methods . . . . . . . . . . . . . . .
Recommended list of PCU configuration procedures. . . . . .
Configuring a PCU using the OMC-R GUI . . . . . . . . . . . . .
Introduction to configuring a PCU using the OMC-R GUI . . .
Prerequisites for configuring a PCU using the OMC-R GUI . .
Creating a PCU using the OMC-R GUI . . . . . . . . . . . . .
PCU Detailed View fields. . . . . . . . . . . . . . . . . . . .
Modifying PCU details from the OMC-R GUI . . . . . . . . . .
Deleting a PCU using the OMC-R GUI . . . . . . . . . . . . .
Displaying and modifying PCU cabinet details . . . . . . . . . . .
Introduction to displaying and modifying PCU cabinet details .
Displaying and modifying a PCU cabinet Detailed View . . . .
Displaying and modifying PCU cage details . . . . . . . . . . . .
Introduction to displaying and modifying PCU cage details . .
Displaying and modifying a PCU cage Detailed View . . . . .
Configuring a DPROC using the OMC-R GUI . . . . . . . . . . . .
Introduction to DPROCs . . . . . . . . . . . . . . . . . . . .
Prerequisites to creating a DPROC . . . . . . . . . . . . . .
Creating a DPROC using the OMC-R GUI . . . . . . . . . . .
DPROC Detailed View fields . . . . . . . . . . . . . . . . . .
Modifying DPROC details from the OMC-R GUI . . . . . . . .
Deleting a DPROC using the OMC-R GUI . . . . . . . . . . .
Displaying and modifying PSP details . . . . . . . . . . . . . . .
Introduction to PSP . . . . . . . . . . . . . . . . . . . . . .
Displaying and modifying PSP details from the OMC-R GUI . .
PSP Detailed View fields . . . . . . . . . . . . . . . . . . . .
Configuring a PCU MSI using the OMC-R GUI . . . . . . . . . . .
Introduction to configuring a PCU MSI using the OMC-R GUI .
Prerequisites to creating a PCU MSI. . . . . . . . . . . . . .
Creating a PCU MSI using the OMC-R GUI . . . . . . . . . .
PCU MSI Detailed View fields . . . . . . . . . . . . . . . . .
Modifying PCU MSI details from the OMC-R GUI . . . . . . .
Deleting a PCU MSI using the OMC-R GUI . . . . . . . . . .
Displaying and modifying PCU MMS details . . . . . . . . . . . .
Introduction to displaying and modifying PCU MMS details . .
Prerequisites to viewing and modifying a PCU MMS. . . . . .
Displaying and modifying an MMS Detailed View . . . . . . .
Configuring a GDS using the OMC-R GUI . . . . . . . . . . . . .
Introduction to configuring a GDS using the OMC-R GUI . . .
Fault Management of a GDS . . . . . . . . . . . . . . . . . .

xii

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Prerequisites to creating a GDS . . . . . . . . . . . . . .

Creating a GDS using the OMC-R GUI . . . . . . . . . . .
GDS Detailed View fields. . . . . . . . . . . . . . . . . .
Modifying GDS details from the OMC-R GUI . . . . . . . .
Deleting a GDS using the OMC-R GUI . . . . . . . . . . .
Configuring a GSL using the OMC-R GUI . . . . . . . . . . .
Introduction to configuring a GSL using the OMC-R GUI .
Defining the GSL equipage mode . . . . . . . . . . . . .
Prerequisites to creating a GSL . . . . . . . . . . . . . .
Creating a GSL using the OMC-R GUI . . . . . . . . . . .
GSL Detailed View parameter fields . . . . . . . . . . . .
Deleting a GSL using the OMC-R GUI . . . . . . . . . . .
Configuring a GBL using the OMC-R GUI . . . . . . . . . . .
Introduction to configuring a GBL using the OMC-R GUI .
Prerequisites to creating a GBL . . . . . . . . . . . . . .
Creating a GBL using the OMC-R GUI . . . . . . . . . . .
GBL Detailed View fields . . . . . . . . . . . . . . . . . .
Deleting a GBL using the OMC-R GUI . . . . . . . . . . .
Configuring an NSVC using the OMC-R GUI . . . . . . . . . .
Introduction to configuring an NSVC using the OMC-R GUI
Prerequisites to creating an NSVC . . . . . . . . . . . . .
Creating an NSVC using the OMC-R GUI . . . . . . . . .
NSVC Detailed View parameter fields . . . . . . . . . . .
Modifying NSVC details from the OMC-R GUI . . . . . . .
Deleting an NSVC using the OMC-R GUI . . . . . . . . .
Configuring an SGSN (GPRS) using the OMC-R GUI . . . . . .
SGSN configuration . . . . . . . . . . . . . . . . . . . .
GPRS SGSN network topology . . . . . . . . . . . . . . .
Multiple SGSNs . . . . . . . . . . . . . . . . . . . . . .
Creating an SGSN using the Navigation Tree . . . . . . .
SGSN Detailed View fields . . . . . . . . . . . . . . . . .
Displaying and modifying an SGSN . . . . . . . . . . . .
Deleting an SGSN . . . . . . . . . . . . . . . . . . . . .
Configuring the PCU and its devices from the TTY interface . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
Examples of the equip command . . . . . . . . . . . . . .
BSS commands supporting a PCU and its devices . . . . .

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

6-30
6-30
6-31
6-32
6-33
6-34
6-34
6-34
6-35
6-35
6-35
6-36
6-38
6-38
6-38
6-38
6-39
6-41
6-43
6-43
6-43
6-43
6-44
6-46
6-48
6-49
6-49
6-49
6-49
6-49
6-50
6-51
6-51
6-52
6-52
6-52
6-53

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

7-2
7-2
7-2
7-3
7-3
7-5
7-6
7-7
7-7
7-8
7-11
7-12
7-12
7-12
7-12
7-13
7-14
7-14

Chapter 7: Configuring a Site

Introduction to BSC and BTS sites . . . . . . . . . . . . . . .
Overview of a BSS and its connections. . . . . . . . . . .
BSS links and control functions . . . . . . . . . . . . . .
BSS topology and path limitations . . . . . . . . . . . . .
Path devices . . . . . . . . . . . . . . . . . . . . . . . .
MSI and RSL restrictions . . . . . . . . . . . . . . . . .
RTF considerations . . . . . . . . . . . . . . . . . . . .
RSL/TCH and BSC-BTS dynamic allocation considerations
900/1800 Horizonmicro2 and Horizoncompact2 BTS . . .
Horizon II BTS . . . . . . . . . . . . . . . . . . . . . . .
Horizon II mini . . . . . . . . . . . . . . . . . . . . . . .
Overview of adding a BTS . . . . . . . . . . . . . . . . . . .
Recommended way to add a BTS . . . . . . . . . . . . .
Who provides the BTS information . . . . . . . . . . . . .
Prerequisites to adding a BTS . . . . . . . . . . . . . . .
Procedures for adding a BTS. . . . . . . . . . . . . . . .
Adding a BTS using a batch rlogin script. . . . . . . . . . . .
Adding a BTS online using batch rlogin script . . . . . . .

68P02901W17-T
Jan 2010

xiii

Contents

Using batch templates . . . . . . . . . . . . . . . . . . . .

Assumptions . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure list . . . . . . . . . . . . . . . . . . . . . . . .
Beginning a batch session . . . . . . . . . . . . . . . . . .
Running script file . . . . . . . . . . . . . . . . . . . . . .
Checks to perform after adding a BTS . . . . . . . . . . . .
Adding a BTS using the TTY interface (example 1) . . . . . . . .
Introduction to adding a BTS using the TTY interface . . . .
Procedure list for adding a BTS using the TTY interface . . .
Equipping BTS devices and functions . . . . . . . . . . . .
Creation order for devices and functions . . . . . . . . . .
General procedure for adding a SITE . . . . . . . . . . . .
Adding path devices . . . . . . . . . . . . . . . . . . . . .
Adding RSL devices . . . . . . . . . . . . . . . . . . . . .
Adding RTF functions . . . . . . . . . . . . . . . . . . . .
Adding a BTS using the TTY interface (example 2) . . . . . . . .
Equipping a SITE and MSIs using the equip command. . . .
Equipping path devices using the TTY interface . . . . . . .
Adding RSL devices using equip command . . . . . . . . .
Adding RTF functions . . . . . . . . . . . . . . . . . . . .
Unequipping a SITE using the TTY interface. . . . . . . . .
Creating a SITE using the OMC-R GUI . . . . . . . . . . . . . .
Introduction to adding a SITE using the OMC-GUI. . . . . .
Creating a SITE using the OMC-R GUI. . . . . . . . . . . .
SITE Detailed View fields . . . . . . . . . . . . . . . . . .
Modifying SITE parameters . . . . . . . . . . . . . . . . . . .
Methods for modifying SITE parameters . . . . . . . . . . .
Using the chg_element command . . . . . . . . . . . . . .
Using the modify_value command . . . . . . . . . . . . . .
Equipping cabinets and cages at a remote BTS . . . . . . . . .
Overview of equipping cabinets and cages at a remote BTS .
Cabinet and cage numbers. . . . . . . . . . . . . . . . . .
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS equipment . . . . . . . . . . . . . . . . . . . . . . .
Additional equipment . . . . . . . . . . . . . . . . . . . .
Overall procedure list . . . . . . . . . . . . . . . . . . . .
Equipping a remote BTS cabinet using the TTY interface . .
Equipping a BTS cage using the TTY interface. . . . . . . .
Deleting and unequipping TCU/CTU cabinets . . . . . . . . . .
Introduction to deleting and unequipping TCU/CTU cabinets
Prerequisites for deleting TCU/CTU cabinet types . . . . . .
Deleting TCU/CTU cabinet types using the OMC-R GUI . . .
Unequipping TCU/CTU cabinet types using the TTY interface
Extending an existing path to a new site using the TTY interface
Introduction to path extension . . . . . . . . . . . . . . . .
Prerequisites to extending a path to new BTS . . . . . . . .
Extending a path to new site using copy_path . . . . . . . .
Example of equipping path device using copy_path command
GCLK synchronization . . . . . . . . . . . . . . . . . . . . . .
Introduction to GCLK synchronization . . . . . . . . . . . .
Description of GCLK synchronization . . . . . . . . . . . .
Effect of the number of GCLKs per site . . . . . . . . . . .
Configuration restrictions . . . . . . . . . . . . . . . . . .
Commands used for GCLK synchronization . . . . . . . . .
Database parameters used for GCLK synchronization . . . .
GCLK modes of operation . . . . . . . . . . . . . . . . . .
Controlling GCLK synchronization using the TTY interface .
Examples of GCLK commands . . . . . . . . . . . . . . . .

xiv

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

7-14
7-14
7-14
7-15
7-15
7-16
7-17
7-17
7-17
7-18
7-18
7-19
7-19
7-19
7-20
7-21
7-21
7-22
7-24
7-25
7-25
7-26
7-26
7-26
7-27
7-34
7-34
7-34
7-34
7-36
7-36
7-36
7-36
7-37
7-37
7-37
7-37
7-38
7-39
7-39
7-39
7-39
7-39
7-40
7-40
7-40
7-40
7-41
7-43
7-43
7-43
7-43
7-44
7-44
7-45
7-46
7-47
7-47

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

7-52
7-52
7-52
7-52
7-52
7-55
7-55
7-55
7-56
7-56
7-56
7-56
7-56
7-57
7-57
7-58
7-59
7-59
7-59
7-59
7-59

. . . .
. . . .
. . . .
a cell .
. . . .
site . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

8-4
8-4
8-4
8-4
8-5
8-5
8-6
8-6
8-6
8-8
8-8
8-8
8-8
8-9
8-10
8-10
8-10
8-11
8-11
8-11
8-13
8-13
8-14
8-14
8-14
8-48
8-48
8-48
8-63
8-63
8-63
8-70
8-70
8-70

Checking GCLK synchronization for a site . . . . . . . . . . . . .

Introduction to GCLK synchronization . . . . . . . . . . . . .
Checking GCLK at a single SITE using the TTY interface . . .
Checking GCLK at a single site using the OMC-R GUI . . . . .
Multiple GCLK SITE checks using scripting and TTY interface
Barring calls at a site using the TTY interface . . . . . . . . . . .
Barring calls at a site using the TTY interface . . . . . . . . .
Additional information . . . . . . . . . . . . . . . . . . . . .
Checking the hardware deployed at each site . . . . . . . . . . .
Overview to site hardware checking . . . . . . . . . . . . . .
Checking a single site using the TTY interface . . . . . . . . .
Checking a single site using the OMC-R GUI. . . . . . . . . .
Checking multiple sites using scripting and TTY interface . . .
Checking a single site, PCU, or NE using cmutil . . . . . . . .
Further analysis of extracted MIB data . . . . . . . . . . . .
Checking a device type in the network using cmutil . . . . . .
Checking key site parameters . . . . . . . . . . . . . . . . . . .
Overview of key site parameter checking . . . . . . . . . . .
tru_id (TopCell SITE). . . . . . . . . . . . . . . . . . . . . .
max_dris per GPROC. . . . . . . . . . . . . . . . . . . . . .
antenna_select number . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

Chapter 8: Configuring cells

General information for configuring cells . . . . . . . . . . . .
Recommendation for small scale RF changes . . . . . . . .
Recommendation for large scale RF changes . . . . . . . .
Viewing the sources, neighbors, and reciprocal neighbors for
Methods of adding a cell . . . . . . . . . . . . . . . . . . .
Creating cells at a Horizonmicro2 and Horizoncompact2 BTS
Adding a cell (recommended procedure) . . . . . . . . . . . . .
Recommended method of adding a cell . . . . . . . . . . .
Recommended procedure for adding a cell . . . . . . . . .
Adding a cell using the copy/change method . . . . . . . . . . .
Description of copy/change method . . . . . . . . . . . . .
Restrictions for copy_cell . . . . . . . . . . . . . . . . . .
Creating a cell by copying then changing details . . . . . .
Example of a copy_cell command . . . . . . . . . . . . . .
Adding a cell using the TTY interface . . . . . . . . . . . . . .
Introduction to adding a cell using the TTY interface . . . .
Adding a cell using the add_cell command . . . . . . . . . .
Adding a cell using the OMC-R GUI . . . . . . . . . . . . . . .
Introduction to adding a cell using the OMC-R GUI . . . . .
Using the CELL Detailed View to create a cell . . . . . . . .
Autocreation of cell algorithms . . . . . . . . . . . . . . .
Modifying a cell using the OMC-R GUI. . . . . . . . . . . .
General cell parameter section. . . . . . . . . . . . . . . . . .
Displaying General cell parameter section . . . . . . . . . .
General cell parameter section groupings . . . . . . . . . .
Handover cell parameter section. . . . . . . . . . . . . . . . .
Displaying the handover cell parameter section . . . . . . .
Handover cell parameter section groupings . . . . . . . . .
Power control cell parameter section . . . . . . . . . . . . . .
Displaying the power control cell parameter section. . . . .
Power control cell parameter section groupings . . . . . . .
GPRS cell parameter section . . . . . . . . . . . . . . . . . . .
Displaying the GPRS cell parameter section . . . . . . . . .
Prerequisites for defining GPRS parameters . . . . . . . . .

68P02901W17-T
Jan 2010

xv

Contents

GPRS cell parameter section grouping. . . . . . . . . . . . . . . . . . . .

Propagating cell parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to propagating cell parameters . . . . . . . . . . . . . . . . .
Cell parameter propagation options . . . . . . . . . . . . . . . . . . . . .
Cell propagation parameters. . . . . . . . . . . . . . . . . . . . . . . . .
Propagating cell parameters using the OMC-R GUI . . . . . . . . . . . . .
Deleting a cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a cell: overall procedure . . . . . . . . . . . . . . . . . . . . . .
Deleting a cell using the OMC-R GUI . . . . . . . . . . . . . . . . . . . .
Defining algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to algorithms . . . . . . . . . . . . . . . . . . . . . . . . . .
Methods for defining algorithms . . . . . . . . . . . . . . . . . . . . . . .
Modifying default algorithms using the OMC-R GUI . . . . . . . . . . . . . . .
Overview of algorithm definition . . . . . . . . . . . . . . . . . . . . . . .
Modifying an algorithm using the OMC-R GUI . . . . . . . . . . . . . . . .
Algorithm Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . .
Modifying default algorithms using the TTY interface . . . . . . . . . . . . . .
Using the chg_cell_element command and parameters . . . . . . . . . . .
Using chg_cell_element to change algorithms . . . . . . . . . . . . . . . .
Defining hreqave, hreqt, and qual_weight . . . . . . . . . . . . . . . . . .
Examples of chg_cell_element commands . . . . . . . . . . . . . . . . . .
Description of rel_tim_adv and surround_cell parameters . . . . . . . . . .
Example of modifying rel_tim_adv and surround_cell parameters . . . . . .
Description of rxlev_dl_ho and rxlev_ul_ho parameters . . . . . . . . . . .
Example of modifying uplink and downlink parameters . . . . . . . . . . .
Neighbors, Sources and Reciprocal Neighbors. . . . . . . . . . . . . . . . . .
Definition: Neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition: source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition: Reciprocal Neighbors . . . . . . . . . . . . . . . . . . . . . .
Automatic creation of Reciprocal Neighbors . . . . . . . . . . . . . . . . .
Viewing Sources, Neighbors and Reciprocals . . . . . . . . . . . . . . . . . .
Introduction to viewing Sources, Neighbors and Reciprocal Neighbors . . .
Procedure to view Sources, Neighbors and Reciprocal Neighbors . . . . . .
Creating and deleting Sources, Neighbors and Reciprocals . . . . . . . . . . .
Introduction to creating and deleting Sources, Neighbors and Reciprocals .
Creating missing Sources and Neighbors for all Cells . . . . . . . . . . . .
Creating missing Sources and Neighbors for selected Cells . . . . . . . . .
Creating a neighbor for a selected cell. . . . . . . . . . . . . . . . . . . .
Creating a Source for a selected cell. . . . . . . . . . . . . . . . . . . . .
Deleting a neighbor for a cell . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a reciprocal neighbor for a cell . . . . . . . . . . . . . . . . . . .
Creating neighbors using Neighbor Detailed View . . . . . . . . . . . . . . . .
Introduction to creating neighbors using the Detailed View . . . . . . . . .
Neighbor Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . .
Creating a single Neighbor using the Neighbor Detailed View . . . . . . . .
Adding a neighbor both ways . . . . . . . . . . . . . . . . . . . . . . . .
Adding multiple neighbors using add_nei . . . . . . . . . . . . . . . . . .
Modifying a neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recommendation for modifying neighbors . . . . . . . . . . . . . . . . . .
Modifying a neighbor using the OMC-R GUI . . . . . . . . . . . . . . . . .
Modifying multiple neighbors of same cell . . . . . . . . . . . . . . . . . .
Modifying multiple neighbors of same site or NE using cmutil . . . . . . . .
Deleting neighbors using the Navigation Tree Delete option. . . . . . . . . . .
Introduction to deleting Neighbors using Navigation Tree . . . . . . . . . .
Deleting a single neighbor using the Navigation Tree Delete option . . . . .
Deleting a neighbor both ways . . . . . . . . . . . . . . . . . . . . . . . .
Deleting multiple neighbors using del_neighbor command or del_nei utility .
Neighbor templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xvi

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

8-70
8-79
8-79
8-79
8-79
8-89
8-92
8-92
8-93
8-94
8-94
8-94
8-95
8-95
8-95
8-96
8-98
8-98
8-98
8-99
8-99
8-99
8-100
8-101
8-102
8-106
8-106
8-106
8-107
8-107
8-109
8-109
8-109
8-115
8-115
8-115
8-117
8-118
8-118
8-119
8-119
8-121
8-121
8-121
8-127
8-128
8-129
8-130
8-130
8-130
8-130
8-130
8-131
8-131
8-131
8-132
8-132
8-133

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Introduction to neighbor templates . . . . . . . . . . . . . .

Displaying a list of neighbor templates . . . . . . . . . . . .
Creating a neighbor template . . . . . . . . . . . . . . . . .
Editing a neighbor template . . . . . . . . . . . . . . . . . .
Deleting a neighbor template . . . . . . . . . . . . . . . . .
Configuring a UTRAN neighbor . . . . . . . . . . . . . . . . . .
Definition of a UTRAN neighbor . . . . . . . . . . . . . . . .
Prerequisites to configuring a UTRAN neighbor . . . . . . . .
UTRAN neighbor parameters . . . . . . . . . . . . . . . . .
Creating a UTRAN neighbor using the OMC-R GUI . . . . . .
Configuring a UTRAN neighbor using the TTY interface . . . .
UTRAN blind search neighbor . . . . . . . . . . . . . . . . . . .
Introduction to a UTRAN blind search neighbor . . . . . . . .
UTRAN Blind Search Neighbor Detailed View fields . . . . . .
Creating a UTRAN blind search neighbor . . . . . . . . . . .
Deleting a UTRAN blind search neighbor . . . . . . . . . . .
Proxy cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to proxy cells . . . . . . . . . . . . . . . . . . .
Environmental variables relating to proxy cells . . . . . . . .
TD-SCDMA UTRAN Proxy Cells . . . . . . . . . . . . . . . .
BCCH and SDCCH in the EGSM band for Proxy cells . . . . .
Proxy cell information . . . . . . . . . . . . . . . . . . . . .
Configuring a single proxy cell . . . . . . . . . . . . . . . . . . .
Creating a proxy cell using the OMC-R GUI . . . . . . . . . .
ProxyCELL Detailed View fields . . . . . . . . . . . . . . . .
Modifying a proxy cell using the OMC-R GUI . . . . . . . . .
Deleting a proxy cell using the OMC-R GUI . . . . . . . . . .
Configuring a single UTRAN ProxyCELL . . . . . . . . . . . . . .
Creating a UTRAN ProxyCELL using the OMC-R GUI . . . . .
UTRAN ProxyCELL Detailed View fields . . . . . . . . . . . .
Modifying a UTRAN ProxyCELL using the OMC-R GUI . . . .
Deleting a UTRAN ProxyCELL using the OMC-R GUI . . . . .
Autocreation of a ProxyCELL . . . . . . . . . . . . . . . . . . .
Introduction to autocreation of a ProxyCELL . . . . . . . . .
Proxy cell autocreation parameters . . . . . . . . . . . . . .
Propagation of autocreated proxy cell information . . . . . . .
Autocreated proxy cell restrictions. . . . . . . . . . . . . . .
Enabling autocreation of proxy cells . . . . . . . . . . . . . .
Autocreating a proxy cell using the OMC-R GUI . . . . . . . .
Configuring multiple proxy cells using cmutil . . . . . . . . . . .
Creating multiple proxy cells . . . . . . . . . . . . . . . . .
Modifying and deleting multiple proxy cells . . . . . . . . . .
Exporting and importing proxy cell information between OMC-Rs .
Introduction to importing and exporting proxy cells . . . . . .
Contents of proxy cell export file. . . . . . . . . . . . . . . .
Enabling proxy cell export . . . . . . . . . . . . . . . . . . .
Prerequisites for exporting and importing . . . . . . . . . . .
Exporting proxy cell information using the TTY interface . . .
Importing proxy cell information. . . . . . . . . . . . . . . .
Use of neighbor information in the import file . . . . . . . . .
Synchronizing all OMC-R proxy cells within a network . . . . . .
Synchronizing all OMC-R proxy cells. . . . . . . . . . . . . .
Changing LAC-CI of proxy cell . . . . . . . . . . . . . . . . .
Dynamic propagation of proxy cell data to OMC-Rs . . . . . . . .
Overview of dynamic propagation . . . . . . . . . . . . . . .
Prerequisites for dynamic propagation. . . . . . . . . . . . .
Rules for dynamic propagation. . . . . . . . . . . . . . . . .
Expanding the capacity of a cell . . . . . . . . . . . . . . . . . .

68P02901W17-T
Jan 2010

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

8-133
8-133
8-133
8-134
8-134
8-135
8-135
8-135
8-135
8-136
8-137
8-140
8-140
8-140
8-140
8-140
8-141
8-141
8-141
8-141
8-142
8-142
8-143
8-143
8-143
8-145
8-145
8-146
8-146
8-146
8-148
8-149
8-150
8-150
8-150
8-151
8-151
8-151
8-152
8-154
8-154
8-154
8-155
8-155
8-155
8-157
8-157
8-157
8-158
8-159
8-160
8-160
8-160
8-162
8-162
8-162
8-162
8-163

xvii

Contents

Recommendation for expanding cell capacity . . . . . . . . . . . . . . . .

Prerequisites for expanding cell capacity . . . . . . . . . . . . . . . . . .
Expanding cell capacity . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . .
Frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Methods for configuring frequency hopping . . . . . . . . . . . . . . . . .
Frequency hopping parameters . . . . . . . . . . . . . . . . . . . . . . .
Configuring frequency hopping using the OMC-R GUI . . . . . . . . . . . . . .
Overview of configuring frequency hopping using the OMC-R GUI . . . . .
Description of configuring frequency hopping using the OMC-R GUI . . . .
Mobile allocation at a DCS1800 or PCS1900 site . . . . . . . . . . . . . .
Impact of BCCH and SDCCH in the EGSM band . . . . . . . . . . . . . . .
Configuring frequency hopping for a cell using the OMC-R GUI . . . . . . .
FreqHopSys Detailed View fields . . . . . . . . . . . . . . . . . . . . . .
Viewing frequency hopping details for a cell . . . . . . . . . . . . . . . . .
Configuring frequency hopping using the TTY interface . . . . . . . . . . . . .
Introduction to configuring frequency hopping using the TTY interface . . .
Methods for configuring frequency hopping using the TTY interface . . . .
Setting frequency hopping parameters using the TTY interface . . . . . . .
Assigning a hopping system to each RTF timeslot . . . . . . . . . . . . . .
Checking frequency hopping configuration for cells . . . . . . . . . . . . . . .
Overview to checking cell frequency hopping . . . . . . . . . . . . . . . .
Checking a single hopping object using the OMC-R GUI . . . . . . . . . . .
Checking multiple hopping objects using cmutil . . . . . . . . . . . . . . .
Multiple hopping checks of OMC-R using cmutil . . . . . . . . . . . . . . .
Configuring a cell with BCCH and SDCCH in the EGSM band . . . . . . . . . .
Introduction to BCCH and SDCCH in the EGSM band . . . . . . . . . . . .
Methods of configuring BCCH and SDCCH in the EGSM band. . . . . . . .
Prerequisites for disabling BCCH and SDCCH in the EGSM band . . . . . .
Configuring a cell with BCCH and SDCCH on EGSM using the TTY interface
Configuring a cell for coincident multiband handovers. . . . . . . . . . . . . .
Overview of coincident multiband handovers . . . . . . . . . . . . . . . .
Interaction with other features . . . . . . . . . . . . . . . . . . . . . . .
Coincident multiband handover parameters . . . . . . . . . . . . . . . . .
Prerequisites to configuring a coincident multiband cell . . . . . . . . . . .
Methods of configuring a cell for coincident multiband handover . . . . . .
Configuring a coincident multiband handover cell using the TTY interface .
Configuring a cell for adaptive handovers . . . . . . . . . . . . . . . . . . . .
Overview of adaptive handovers . . . . . . . . . . . . . . . . . . . . . . .
Adaptive handover parameters . . . . . . . . . . . . . . . . . . . . . . .
Methods of configuring a cell for adaptive handovers . . . . . . . . . . . .
Configuring a cell for adaptive handovers using the TTY interface. . . . . .
Configuring a neighbor cell for adaptive handovers . . . . . . . . . . . . . . .
Overview of configuring a neighbor cell for adaptive handovers . . . . . . .
Configuring a neighbor cell for adaptive handovers using the OMC-R GUI .
Configuring a neighbor cell for handovers using the TTY interface . . . . .
Limiting Ping-Pong handovers between cell zones . . . . . . . . . . . . . . . .
Ping-Pong handover limitation parameters. . . . . . . . . . . . . . . . . .
Configuring Ping-Pong handover parameters using the OMC-R GUI . . . . .
Configuring Ping-Pong handover parameters using the TTY interface . . . .
Configuring a cell for flexible neighbor cell processing . . . . . . . . . . . . .
Introduction to flexible neighbor cell processing . . . . . . . . . . . . . .
Flexible neighbor cell processing parameters . . . . . . . . . . . . . . . .
Methods of configuring a cell for flexible neighbor processing . . . . . . .
Configuring a cell for flexible neighbor processing using the TTY interface .
Configuring enhanced SDCCH to TCH band assignment . . . . . . . . . . . . .
Introduction to enhanced SDCCH to TCH band assignment . . . . . . . . .
Methods of configuring enhanced SDCCH to TCH band assignment . . . . .

xviii

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

8-163
8-163
8-163
8-165
8-165
8-165
8-165
8-167
8-167
8-167
8-168
8-169
8-169
8-171
8-173
8-175
8-175
8-175
8-175
8-176
8-178
8-178
8-178
8-178
8-178
8-179
8-179
8-179
8-180
8-180
8-181
8-181
8-181
8-181
8-182
8-183
8-183
8-185
8-185
8-185
8-188
8-188
8-190
8-190
8-190
8-191
8-193
8-193
8-194
8-194
8-195
8-195
8-195
8-197
8-197
8-198
8-198
8-198

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Prerequisites for configuring enhanced SDCCH to TCH band assignment . . . .

Enhanced SDCCH to TCH band assignment parameter . . . . . . . . . . . . .
Setting enhanced SDCCH to TCH band assignment using the TTY interface. . .
Displaying enhanced SDCCH to TCH band assignment using the TTY interface .
Configuring a cell for extended cell range prioritization . . . . . . . . . . . . . . .
Introduction to extended cell range prioritization . . . . . . . . . . . . . . . .
Extended cell range prioritization parameter . . . . . . . . . . . . . . . . . .
Methods of configuring a cell for extended cell range prioritization . . . . . . .
Configuring a cell for extended range cell prioritization using the TTY interface
Configuring a cell for power control optimization . . . . . . . . . . . . . . . . . .
Introduction to cell power control optimization . . . . . . . . . . . . . . . . .
Cell power control optimization parameters . . . . . . . . . . . . . . . . . . .
Dynamic BTS Power control for Horizonmicro2 . . . . . . . . . . . . . . . . .
Methods for configuring power control optimization . . . . . . . . . . . . . . .
Configuring cell power control optimization using the TTY interface . . . . . .
Configuring a cell for multiple GPRS carriers . . . . . . . . . . . . . . . . . . . .
Introduction to multiple GPRS carriers per cell . . . . . . . . . . . . . . . . .
Prerequisites for configuring multiple GPRS carriers per cell . . . . . . . . . .
Multiple GPRS carriers per cell parameters . . . . . . . . . . . . . . . . . . .
Methods for configuring multiple GPRS carriers per cell . . . . . . . . . . . .
Configuring a cell for multiple GPRS carriers using the TTY interface . . . . . .
Changing a BCCH carrier frequency . . . . . . . . . . . . . . . . . . . . . . . . .
Changing BCCH carrier frequency using the OMC-R GUI . . . . . . . . . . . .
Checking the status of a site . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing a non-BCCH carrier frequency . . . . . . . . . . . . . . . . . . . . . .
Methods of changing non-BCCH carrier frequency for a cell. . . . . . . . . . .
Changing non-BCCH carrier frequency for a cell using the OMC-R GUI . . . . .
Changing non-BCCH carrier frequency using the TTY interface . . . . . . . . .
Changing a BSIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recommendation and overview to BSIC change . . . . . . . . . . . . . . . . .
Changing a BSIC with no hopping using the OMC-R GUI . . . . . . . . . . . .
Changing a BSIC with hopping. . . . . . . . . . . . . . . . . . . . . . . . . .
Changing a TSC for a BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview to TSC change . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing a TSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Propagating TSC updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of TSC update propagation . . . . . . . . . . . . . . . . . . . . . .
Methods of specifying the propagation of TSC updates . . . . . . . . . . . . .
Prerequisites for changing TSC propagation . . . . . . . . . . . . . . . . . . .
Modifying the TSC update propagation method using the TTY interface . . . . .
Displaying the TSC update propagation method using the TTY . . . . . . . . .
Assigning a quality of 7 to missing measurement reports . . . . . . . . . . . . . .
Introduction to quality 7 for missing reports . . . . . . . . . . . . . . . . . . .
Quality of 7 for missing measurement reports parameter . . . . . . . . . . . .
Methods of assigning a quality of 7 to missing measurement reports . . . . . .
Recording missing measurement reports as quality 7 using the TTY interface . .
Changing the number of allocated SDCCHs . . . . . . . . . . . . . . . . . . . . .
Introduction to determining the number of SDCCHs . . . . . . . . . . . . . . .
Changing the number of SDCCHs: associated parameters . . . . . . . . . . . .
Methods of reconfiguring the number of SDCCHs . . . . . . . . . . . . . . . .
Reconfiguring the number of SDCCHs using the TTY interface . . . . . . . . .
Checking SDCCH configuration for multiple cells using SQL . . . . . . . . . .
Establishing a cell boundary by changing transmit power . . . . . . . . . . . . . .
Introduction to establishing a cell boundary by changing transmit power . . . .
Methods of changing the maximum output of a cell . . . . . . . . . . . . . . .
Setting all channels at full power . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to setting channel power level . . . . . . . . . . . . . . . . . . .
Description of set_full_power process . . . . . . . . . . . . . . . . . . . . . .

68P02901W17-T
Jan 2010

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

8-198
8-199
8-199
8-200
8-201
8-201
8-201
8-201
8-202
8-203
8-203
8-203
8-204
8-204
8-205
8-207
8-207
8-208
8-208
8-211
8-211
8-213
8-213
8-214
8-216
8-216
8-216
8-217
8-219
8-219
8-219
8-220
8-221
8-221
8-221
8-222
8-222
8-222
8-222
8-222
8-223
8-224
8-224
8-224
8-224
8-225
8-226
8-226
8-226
8-230
8-230
8-233
8-234
8-234
8-236
8-237
8-237
8-237

xix

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

8-237
8-238
8-238
8-239
8-239
8-239
8-240
8-240
8-241
8-242
8-242
8-242
8-242
8-243
8-244
8-244
8-244

Methods of configuring individual devices and functions. . . . . . . .

Introduction to configuring individual devices and functions. . . .
Creating/equipping individual devices and functions. . . . . . . .
Modifying individual devices and functions . . . . . . . . . . . .
Displaying individual device and function details . . . . . . . . .
Deleting/unequipping individual devices and functions . . . . . .
Methods of configuring multiple devices and functions . . . . . . . .
Introduction to configuring multiple devices and function . . . . .
Creating multiple devices or functions using a batch_rlogin script.
Methods of modifying multiple devices and functions . . . . . . .
Modifying multiple devices or functions using batch_rlogin . . . .
Deleting multiple devices or functions using a script . . . . . . .
Checking the hardware version/serial number/FRU . . . . . . . . . .
Overview to tracking devices . . . . . . . . . . . . . . . . . . .
Checking a single device using the OMC-R GUI . . . . . . . . . .
Checking a single SITE using the TTY interface . . . . . . . . . .
Checking multiple devices using SQL . . . . . . . . . . . . . . .
Making multiple checks using scripting and TTY interface. . . . .
Reassigning SITE, MTL, and CBL devices between GPROCs . . . . . .
Device redistribution. . . . . . . . . . . . . . . . . . . . . . . .
Reassignment controlling factors . . . . . . . . . . . . . . . . .
Reassignment capacity issues . . . . . . . . . . . . . . . . . . .
Reassigning devices using the OMC-R GUI . . . . . . . . . . . .
Reassigning devices using the TTY interface. . . . . . . . . . . .
Displaying current devices assigned to LCF . . . . . . . . . . . .
Displaying HDLC layout . . . . . . . . . . . . . . . . . . . . . .
Modifying max_mtls and max_cbls supported by LCF . . . . . . .
Reassigning child devices using reassign command . . . . . . . .
Displaying Channel and Circuit Status . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Circuit Status form. . . . . . . . . . . . . . . . . . . . . . . . .
Channel Status form . . . . . . . . . . . . . . . . . . . . . . . .
Hierarchy of devices and functions . . . . . . . . . . . . . . . . . .
Introduction to the hierarchy of devices and functions. . . . . . .
BSS/RXCDR containment . . . . . . . . . . . . . . . . . . . . .
SITE containment . . . . . . . . . . . . . . . . . . . . . . . . .
Motorola product equipage hierarchy . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

9-3
9-3
9-3
9-4
9-5
9-6
9-8
9-8
9-8
9-8
9-8
9-9
9-10
9-10
9-11
9-11
9-11
9-12
9-14
9-14
9-14
9-15
9-15
9-15
9-16
9-16
9-17
9-18
9-20
9-20
9-20
9-20
9-24
9-29
9-29
9-29
9-30
9-34

Displaying the status of full power mode using the TTY interface
Enabling full power on all channels using the TTY interface . .
Disabling full power on all channels using the TTY interface. . .
Barring calls at a cell . . . . . . . . . . . . . . . . . . . . . . . .
Overview of barring options . . . . . . . . . . . . . . . . . . .
Displaying cells where calls are barred . . . . . . . . . . . . .
Barring of incoming handovers . . . . . . . . . . . . . . . . .
Changing neighbor BA lists . . . . . . . . . . . . . . . . . . .
Barring calls at a site . . . . . . . . . . . . . . . . . . . . . .
Changing LAC and/or CI . . . . . . . . . . . . . . . . . . . . . . .
GSM Cell identifier . . . . . . . . . . . . . . . . . . . . . . .
Recommendation for changing LAC and/or CI . . . . . . . . . .
Changing a single LAC and/or CI using the OMC-R GUI . . . . .
Changing multiple LACs and/or CIs using cmutil . . . . . . . .
Viewing and editing the SMS-CB message using the OMC-R GUI . .
Using the SMS CB Detailed View . . . . . . . . . . . . . . . .
SMSCBmsg Detailed View fields . . . . . . . . . . . . . . . . .

Chapter 9: Configuring Devices and Functions

xx

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a BSP device . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition of a BSP . . . . . . . . . . . . . . . . . . . . . . . .
BSP cage and slot restrictions . . . . . . . . . . . . . . . . . .
Creating a BSP using the OMC-R GUI . . . . . . . . . . . . . .
BSP Detailed View fields . . . . . . . . . . . . . . . . . . . . .
Equipping a BSP using the TTY interface . . . . . . . . . . . .
Configuring a BTP device . . . . . . . . . . . . . . . . . . . . . .
Definition of a BTP . . . . . . . . . . . . . . . . . . . . . . . .
Creating and deleting a BTP in a Horizon II macro cabinet . . .
BTP in Horizon II mini cabinet . . . . . . . . . . . . . . . . . .
BTP cage and slot restrictions . . . . . . . . . . . . . . . . . .
Creating a BTP from the OMC-R GUI . . . . . . . . . . . . . .
BTP Detailed View fields . . . . . . . . . . . . . . . . . . . . .
Equipping a BTP using the TTY interface . . . . . . . . . . . .
Configuring a CBL . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition of a CBL . . . . . . . . . . . . . . . . . . . . . . . .
Creating a CBL using the OMC-R GUI . . . . . . . . . . . . . .
CBL Detailed View fields . . . . . . . . . . . . . . . . . . . . .
Equipping a CBL using the TTY interface . . . . . . . . . . . .
Configuring a CIC . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to configuring CICs . . . . . . . . . . . . . . . . .
Impact of Enhanced GDP Provisioning on a CIC . . . . . . . . .
Equipping CICs using the TTY interface . . . . . . . . . . . . .
Displaying CIC information using the TTY interface . . . . . . .
Configuring a COMB device . . . . . . . . . . . . . . . . . . . . .
Definition of COMB . . . . . . . . . . . . . . . . . . . . . . .
Configuration of RTC . . . . . . . . . . . . . . . . . . . . . .
RTC hardware addresses . . . . . . . . . . . . . . . . . . . .
DRI and Combiner configuration . . . . . . . . . . . . . . . . .
Creating a COMB device using the OMC-R GUI . . . . . . . . .
COMB Detailed View fields . . . . . . . . . . . . . . . . . . .
Equipping a COMB using the TTY interface . . . . . . . . . . .
Displaying COMB details using the TTY interface . . . . . . . .
Configuring a CSFP device. . . . . . . . . . . . . . . . . . . . . .
Definition of a CSFP . . . . . . . . . . . . . . . . . . . . . . .
Methods of creating a CSFP . . . . . . . . . . . . . . . . . . .
GPROC cage and slot restrictions . . . . . . . . . . . . . . . .
CSFP Detailed View fields . . . . . . . . . . . . . . . . . . . .
Creating a CSFP device using the OMC-R GUI. . . . . . . . . .
Unconfiguring CSFP devices using the OMC-R GUI . . . . . . .
Equipping a CSFP device using the TTY interface . . . . . . . .
Using other settings of stealing algorithm . . . . . . . . . . . .
Configuring a DHP device . . . . . . . . . . . . . . . . . . . . . .
Definition of a DHP . . . . . . . . . . . . . . . . . . . . . . .
DHP cage and slot restrictions . . . . . . . . . . . . . . . . . .
Horizonmicro2 and Horizoncompact2 DHPs . . . . . . . . . . .
Configuring a DHP at a Horizonmicro2 or Horizoncompact2 BTS
Creating a DHP using the OMC-R GUI . . . . . . . . . . . . . .
DHP Detailed View fields . . . . . . . . . . . . . . . . . . . .
Equipping a DHP using the TTY interface . . . . . . . . . . . .
Equipping multiple DHP devices . . . . . . . . . . . . . . . . .
Configuring a DRI . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition of a DRI . . . . . . . . . . . . . . . . . . . . . . . .
DRIGroup . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for configuring a DRI . . . . . . . . . . . . . . .
Impact of Dual Band Cells feature on DRI/RTFs . . . . . . . . .
Horizonmicro2 and Horizoncompact2 DRIs . . . . . . . . . . .

68P02901W17-T
Jan 2010

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

9-35
9-35
9-35
9-35
9-35
9-36
9-38
9-39
9-39
9-39
9-39
9-39
9-40
9-40
9-42
9-43
9-43
9-43
9-43
9-44
9-46
9-46
9-46
9-46
9-47
9-49
9-49
9-49
9-50
9-51
9-51
9-52
9-53
9-53
9-54
9-54
9-54
9-54
9-55
9-56
9-57
9-57
9-58
9-59
9-59
9-59
9-59
9-60
9-60
9-60
9-62
9-62
9-63
9-63
9-63
9-64
9-64
9-64

xxi

Contents

DRI and Combiner configuration . . . . . . . . . . . . . . . . . . . . .

Double Density DRIs in a Horizon II mini . . . . . . . . . . . . . . . .
Configuring Double density DRIs . . . . . . . . . . . . . . . . . . . .
Creating a DRI using the OMC-R GUI . . . . . . . . . . . . . . . . . .
DRI Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . . .
Other DRI configuration tasks . . . . . . . . . . . . . . . . . . . . . .
Reassigning a DRI device . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to reassigning . . . . . . . . . . . . . . . . . . . . . . .
Reassigning a Horizonmicro2 or Horizoncompact2 BTS . . . . . . . . .
Reassigning a DRI using the OMC-R GUI . . . . . . . . . . . . . . . .
Reassigning a DRI using the TTY interface. . . . . . . . . . . . . . . .
Remotely calibrating DRIs . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to the Remote Bay Level Calibration facility . . . . . . . .
Enabling the Preserve Transceiver Calibration feature at the OMC-R . .
Standard configurations used for a calibration. . . . . . . . . . . . . .
Calibration restrictions . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R calibration checks . . . . . . . . . . . . . . . . . . . . . . . .
Enabling the bay level calibration facility . . . . . . . . . . . . . . . .
Bay level calibration parameters . . . . . . . . . . . . . . . . . . . . .
Enabling a site to be remotely calibrated . . . . . . . . . . . . . . . .
Remote DRI calibration procedures . . . . . . . . . . . . . . . . . . .
Creating a standard configuration for DRI calibration . . . . . . . . . . . .
Introduction to DRI calibration . . . . . . . . . . . . . . . . . . . . .
Prerequisites to DRI calibrations . . . . . . . . . . . . . . . . . . . .
Creating a standard configuration . . . . . . . . . . . . . . . . . . . .
Rx A and Rx B receive path options . . . . . . . . . . . . . . . . . . .
Remotely calibrating DRIs from the OMC-R . . . . . . . . . . . . . . . . .
Prerequisites for remotely calibrating DRIs . . . . . . . . . . . . . . .
Calibrating DRIs from the OMC-R . . . . . . . . . . . . . . . . . . . .
Managing existing standard configurations . . . . . . . . . . . . . . . . .
Viewing and editing an existing standard configuration . . . . . . . . .
Deleting a standard configuration . . . . . . . . . . . . . . . . . . . .
Configuring an EAS device . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition of EAS device . . . . . . . . . . . . . . . . . . . . . . . . .
EAS configuration procedures: overview . . . . . . . . . . . . . . . .
User-definable EAS BSC/BSS and BTS alarm strings. . . . . . . . . . . . .
Introduction to user-definable alarm strings . . . . . . . . . . . . . . .
Rules for defining EAS alarms . . . . . . . . . . . . . . . . . . . . . .
Alarm severity levels . . . . . . . . . . . . . . . . . . . . . . . . . . .
EAS alarm strings . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining EAS alarms in the alarm table using the TTY interface . . . . . . .
Using chg_eas_alarm command . . . . . . . . . . . . . . . . . . . . .
Defining EAS alarms using the TTY interface . . . . . . . . . . . . . .
Changing EAS alarms in the alarms table using the TTY interface . . . . . .
Using the chg_eas_alarm command . . . . . . . . . . . . . . . . . . .
Displaying parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing EAS alarm strings and security levels using the TTY interface
Creating an EAS device using the OMC-R GUI . . . . . . . . . . . . . . . .
Introduction to creating an EAS using the OMC-R GUI . . . . . . . . .
Creating an EAS using the Navigation Tree . . . . . . . . . . . . . . .
EAS Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring an EAS using the TTY interface . . . . . . . . . . . . . . . . .
Equipping an EAS using the equip command . . . . . . . . . . . . . .
Modifying EAS details using the TTY interface. . . . . . . . . . . . . .
Displaying EAS details using the TTY interface . . . . . . . . . . . . .
Configuring the EAS physical relay states using the TTY interface. . . . . .
Displaying the physical relay states for an EAS . . . . . . . . . . . . .
Setting the physical relay states for an EAS . . . . . . . . . . . . . . .

xxii

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

9-65
9-66
9-66
9-68
9-68
9-76
9-77
9-77
9-77
9-77
9-78
9-79
9-79
9-79
9-80
9-80
9-80
9-81
9-82
9-82
9-83
9-84
9-84
9-84
9-84
9-88
9-93
9-93
9-93
9-99
9-99
9-100
9-101
9-101
9-101
9-102
9-102
9-102
9-102
9-102
9-103
9-103
9-103
9-104
9-104
9-104
9-104
9-106
9-106
9-106
9-108
9-111
9-111
9-111
9-111
9-112
9-112
9-112

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a GCLK device . . . . . . . . . . . . . . . . . . . . . . .

Definition of a GCLK . . . . . . . . . . . . . . . . . . . . . . . . .
Rules for configuring a GCLK . . . . . . . . . . . . . . . . . . . .
GCLK slot restrictions . . . . . . . . . . . . . . . . . . . . . . . .
Creating a GCLK device using the OMC-R GUI . . . . . . . . . . .
GCLK Detailed View fields . . . . . . . . . . . . . . . . . . . . . .
Equipping a GCLK device using the TTY interface . . . . . . . . . .
Configuring a GPROC device. . . . . . . . . . . . . . . . . . . . . . .
Definition of a GPROC . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for configuring a GPROC . . . . . . . . . . . . . . .
GPROC slot restrictions . . . . . . . . . . . . . . . . . . . . . . .
Creating a GPROC device using the OMC-R GUI. . . . . . . . . . .
GPROC Detailed View fields . . . . . . . . . . . . . . . . . . . . .
Equipping a GPROC device using the TTY interface . . . . . . . . .
Equipping a GPROC at a BSC or BSS site . . . . . . . . . . . . . .
Configuring a KSWpair device . . . . . . . . . . . . . . . . . . . . . .
Definition of a KSWpair . . . . . . . . . . . . . . . . . . . . . . .
KSWpair Detailed View fields . . . . . . . . . . . . . . . . . . . .
Configuring a KSW (or DSW) device . . . . . . . . . . . . . . . . . . .
Definition of a KSW and KSWX. . . . . . . . . . . . . . . . . . . .
Rules for configuring a KSW . . . . . . . . . . . . . . . . . . . . .
Slot restrictions for KSW. . . . . . . . . . . . . . . . . . . . . . .
Definition of a DSW and DSWX . . . . . . . . . . . . . . . . . . .
Creating a KSW or DSW device using the OMC-R GUI . . . . . . . .
KSW Detailed View fields . . . . . . . . . . . . . . . . . . . . . .
Equipping a KSW device using the TTY interface . . . . . . . . . .
Displaying DSW or KSW details using the TTY interface . . . . . . .
Configuring an LCF function . . . . . . . . . . . . . . . . . . . . . . .
Introduction to configuring an LCF . . . . . . . . . . . . . . . . .
Prerequisites to configuring an LCF . . . . . . . . . . . . . . . . .
Creating an LCF function using the OMC-R GUI . . . . . . . . . . .
LCF Detailed View fields . . . . . . . . . . . . . . . . . . . . . . .
Equipping an LCF function using the TTY interface . . . . . . . . .
Displaying LCF settings using the TTY interface . . . . . . . . . .
Modifying LCF settings using the TTY interface . . . . . . . . . . .
Configuring an LMTL device . . . . . . . . . . . . . . . . . . . . . . .
Definition of an LMTL . . . . . . . . . . . . . . . . . . . . . . . .
LMTL restrictions . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for creating an LMTL . . . . . . . . . . . . . . . . .
LMTL parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating an LMTL device using the OMC-R GUI . . . . . . . . . . .
Commands used to configure an LMTL using the TTY interface . . .
Creating an LMTL using the TTY interface. . . . . . . . . . . . . .
Modifying LMTL loadsharing granularity . . . . . . . . . . . . . . . .
Overview of LMTL loadsharing granularity . . . . . . . . . . . . .
Detailed description of BSS routing function. . . . . . . . . . . . .
Methods of modifying LMTL loadsharing granularity . . . . . . . .
LMTL Loadshare Granularity field . . . . . . . . . . . . . . . . .
Modifying LMTL loadsharing granularity using the OMC-R GUI . . .
Modifying LMTL loadsharing granularity using the TTY interface . .
Displaying LMTL loadsharing granularity using the TTY interface . .
Configuring an MSI device . . . . . . . . . . . . . . . . . . . . . . . .
Definition of MSI. . . . . . . . . . . . . . . . . . . . . . . . . . .
MSI hierarchy requirements . . . . . . . . . . . . . . . . . . . . .
Additional database changes required . . . . . . . . . . . . . . . .
Autocreation and deletion of MSI 0 and MMSs at a Horizon II macro
Creating an MSI using the OMC-R GUI . . . . . . . . . . . . . . .
MSI Detailed View fields . . . . . . . . . . . . . . . . . . . . . . .

68P02901W17-T
Jan 2010

Contents

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
BTS .
. . .
. . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

9-113
9-113
9-113
9-113
9-113
9-114
9-115
9-116
9-116
9-116
9-116
9-117
9-117
9-119
9-119
9-120
9-120
9-120
9-123
9-123
9-123
9-123
9-123
9-124
9-124
9-126
9-126
9-127
9-127
9-127
9-127
9-128
9-129
9-130
9-130
9-131
9-131
9-131
9-131
9-131
9-132
9-132
9-133
9-134
9-134
9-134
9-135
9-135
9-135
9-135
9-136
9-137
9-137
9-137
9-137
9-138
9-138
9-139

xxiii

Contents

Equipping an MSI using the TTY interface . . . . . . . . . . . . . . . . . . .

Equipping an MSI at a BSC or BSS site . . . . . . . . . . . . . . . . . . . .
Displaying CICs using transcoding resources . . . . . . . . . . . . . . . . .
Other MSI configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Enhanced GDP provisioning. . . . . . . . . . . . . . . . . . . . . .
Definition of a GDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced GDP provisioning . . . . . . . . . . . . . . . . . . . . . . . . . .
Primary and secondary GDPs . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for enhanced GDP provisioning . . . . . . . . . . . . . . . . .
Enhanced GDP provisioning parameters . . . . . . . . . . . . . . . . . . . .
Restrictions: changing MSI type and enhanced GDP provisioning parameters.
Configuring an MTL device . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MTL hierarchy requirements . . . . . . . . . . . . . . . . . . . . . . . . .
Creating an MTL using the OMC-R GUI . . . . . . . . . . . . . . . . . . . .
MTL Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipping an MTL using the TTY interface . . . . . . . . . . . . . . . . . .
Modifying MTL loadsharing granularity . . . . . . . . . . . . . . . . . . . . . .
Overview of MTL loadsharing granularity . . . . . . . . . . . . . . . . . . .
Detailed description of BSS routing function. . . . . . . . . . . . . . . . . .
Methods of modifying MTL loadsharing granularity . . . . . . . . . . . . . .
MTL Loadshare Granularity field . . . . . . . . . . . . . . . . . . . . . . .
Modifying MTL loadsharing granularity using the OMC-R GUI . . . . . . . .
Modifying MTL loadsharing granularity using the TTY interface. . . . . . . .
Displaying MTL loadsharing granularity using the TTY interface . . . . . . .
Configuring an OMF function . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to the configuring of an OMF function . . . . . . . . . . . . . .
Creating an OMF device instance using the OMC-R GUI. . . . . . . . . . . .
OMF Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipping an OMF function using the TTY interface . . . . . . . . . . . . . .
Configuring an OML device . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OML hierarchy requirements . . . . . . . . . . . . . . . . . . . . . . . . .
Creating an OML using the OMC-R GUI . . . . . . . . . . . . . . . . . . . .
OML Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipping an OML device using the TTY interface . . . . . . . . . . . . . . .
Configuring a path device . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition of a path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
path devices for a DYNET . . . . . . . . . . . . . . . . . . . . . . . . . . .
path configuration topics . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Methods of creating a path . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for creating a path. . . . . . . . . . . . . . . . . . . . . . . .
Creating a path using the TTY interface (recommended method) . . . . . . .
Creating a path device using the OMC-R GUI . . . . . . . . . . . . . . . . .
PATH Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Methods of deleting a path. . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to deleting a path . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a path online using the TTY interface (recommended method) . . . .
Extending and reparenting a path . . . . . . . . . . . . . . . . . . . . . . . . .
Extending an existing path to a new site . . . . . . . . . . . . . . . . . . . .
Reparenting a path online (recommended method) . . . . . . . . . . . . . .
Checking path connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview to path connectivity . . . . . . . . . . . . . . . . . . . . . . . . .
Checking a single path using the OMC-R GUI . . . . . . . . . . . . . . . . .
Checking multiple paths using cmutil . . . . . . . . . . . . . . . . . . . . .
Checking single site or NE path using cmutil . . . . . . . . . . . . . . . . .

xxiv

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

9-142
9-144
9-144
9-144
9-146
9-146
9-146
9-146
9-146
9-147
9-147
9-148
9-152
9-152
9-152
9-152
9-153
9-155
9-155
9-155
9-156
9-156
9-156
9-156
9-157
9-158
9-158
9-158
9-158
9-159
9-160
9-160
9-160
9-160
9-161
9-162
9-162
9-163
9-163
9-163
9-164
9-164
9-164
9-164
9-167
9-167
9-170
9-170
9-170
9-170
9-172
9-172
9-172
9-174
9-174
9-174
9-174
9-175

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Contents

Checking multiple paths in the OMC-R using cmutil . . . . . . . . . . . . .

Configuring an RSL device . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition of an RSL device . . . . . . . . . . . . . . . . . . . . . . . . .
RSL congestion control . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSL timeslot restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . .
Impact of BSC-BTS dynamic allocation on RTFs/RSLs . . . . . . . . . . . .
RSLs at a Horizon II macro BTS . . . . . . . . . . . . . . . . . . . . . . .
Methods of configuring an RSL . . . . . . . . . . . . . . . . . . . . . . .
Creating an RSL using the OMC-R GUI . . . . . . . . . . . . . . . . . . .
RSL Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipping an RSL using the TTY interface . . . . . . . . . . . . . . . . . .
Unequipping an RSL using the TTY interface . . . . . . . . . . . . . . . .
Other RSL configuration tasks . . . . . . . . . . . . . . . . . . . . . . . .
Configuring an RTF function . . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition of an RTF function . . . . . . . . . . . . . . . . . . . . . . . .
TRX creation and deletion . . . . . . . . . . . . . . . . . . . . . . . . . .
Impact of Dual Band Cells feature on RTFs and DRIs . . . . . . . . . . . .
Impact of VersaTRAU feature on an RTF . . . . . . . . . . . . . . . . . . .
Impact of BSC-BTS dynamic allocation on an RTF . . . . . . . . . . . . . .
Impact of BCCH and SDCCH in the EGSM band on an RTF . . . . . . . . .
Timeslots and frequency hopping . . . . . . . . . . . . . . . . . . . . . .
Methods of configuring an RTF . . . . . . . . . . . . . . . . . . . . . . .
Additional information for RTFs . . . . . . . . . . . . . . . . . . . . . . .
Creating an RTF function . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to creating an RTF. . . . . . . . . . . . . . . . . . . . . . .
Creating an RTF using the OMC-R GUI . . . . . . . . . . . . . . . . . . .
RTF Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipping an RTF function using the TTY interface . . . . . . . . . . . . .
Deleting an RTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions when deleting an RTF. . . . . . . . . . . . . . . . . . . . . .
Methods of deleting an RTF . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting an RTF using the TTY interface. . . . . . . . . . . . . . . . . . .
Exporting incoming neighbors on deletion of BCCH RTFs . . . . . . . . . .
Other RTF configuration tasks . . . . . . . . . . . . . . . . . . . . . . . .
Configuring an XBL device . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Definition of an XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for creating an XBL . . . . . . . . . . . . . . . . . . . . . .
SYSGEN rules for XBLs . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating an XBL for an Assoc_RXCDR using the OMC-R GUI . . . . . . . .
XBL Detailed View fields . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating an XBL for an Assoc_BSS using the OMC-R GUI . . . . . . . . . .
Deleting an XBL from a Assoc_RXCDR or Assoc_BSS using the OMC-R GUI .
Equipping an XBL device at a BSC using the TTY interface . . . . . . . . .
Equipping an XBL device at an RXCDR using the TTY interface . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

9-175
9-176
9-176
9-176
9-176
9-176
9-176
9-177
9-177
9-177
9-179
9-180
9-181
9-182
9-182
9-182
9-182
9-183
9-183
9-184
9-184
9-184
9-184
9-185
9-185
9-185
9-185
9-192
9-193
9-193
9-193
9-193
9-195
9-195
9-197
9-197
9-197
9-197
9-198
9-198
9-200
9-200
9-200
9-201

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

10-2
10-2
10-3
10-4
10-5
10-5
10-5
10-5
10-5
10-6
10-8

Chapter 10: Auditing

Introduction to auditing . . . . . . . .
Overview of auditing . . . . . . . .
Intelligent audit . . . . . . . . . .
Multiple BSS/RXCDR Audit . . . .
Audit logs and temporary files . . .
Audit restrictions . . . . . . . . .
Scheduled audits queuing support .
Initiating an audit . . . . . . . . .
Configuring the Audit Gather phase
Per Site Audit feature . . . . . . .
Auditing recommendations. . . . . . .

68P02901W17-T
Jan 2010

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

xxv

Contents

Recommended use of audit . . . . . . . . . . . . . . . . . . . . . . . .

Auditing scenarios and NE basis . . . . . . . . . . . . . . . . . . . . . .
Audit logs and expired logs . . . . . . . . . . . . . . . . . . . . . . . .
Auditing problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Proper use of Audit, Proxy Cell sync, Network Expansion, and propagation
Auditing the network using the OMC-R GUI . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auditing the network using the Navigation Tree . . . . . . . . . . . . . .
Auditing a BSS/RXCDR using the OMC-R GUI . . . . . . . . . . . . . . . . .
Auditing a BSS or RXCDR using the Navigation Tree . . . . . . . . . . .
Resolving auditing NE Id inconsistencies . . . . . . . . . . . . . . . . .
Multiple site audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting multiple site audits . . . . . . . . . . . . . . . . . . . . . . .
Multiple BSS/RXCDR audits . . . . . . . . . . . . . . . . . . . . . . . . . .
Auditing multiple BSS/RXCDRs . . . . . . . . . . . . . . . . . . . . . .
Selecting multiple BSS/RXCDRs for auditing. . . . . . . . . . . . . . . .
Viewing the status of Multiple BSS Audits . . . . . . . . . . . . . . . . .
Scheduling an audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of scheduling procedures . . . . . . . . . . . . . . . . . . . . . . .
Creating a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . .
Deferring a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . .
Displaying the network elements in a scheduled audit . . . . . . . . . . .
Displaying the status of a Multiple BSS Audit . . . . . . . . . . . . . . .
Printing a list of scheduled audits . . . . . . . . . . . . . . . . . . . . .
Deleting a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting all scheduled audits . . . . . . . . . . . . . . . . . . . . . . .
Managing audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing an audit log list . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing an audit log list . . . . . . . . . . . . . . . . . . . . . . . . . .
Aborting an audit in progress . . . . . . . . . . . . . . . . . . . . . . .
Viewing an audit inconsistency report . . . . . . . . . . . . . . . . . . .
Printing an inconsistency report . . . . . . . . . . . . . . . . . . . . . .
Updating the database with inconsistencies . . . . . . . . . . . . . . . .
Deleting audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Propagating cell changes to neighbor cells after an audit . . . . . . . . . . .
Propagation of cell changes after audit . . . . . . . . . . . . . . . . . .
Cell details propagated after an audit . . . . . . . . . . . . . . . . . . .
Enabling the propagation after audit facility . . . . . . . . . . . . . . . .
Reasons for disabling propagation after audit facility . . . . . . . . . . .
Disabling the propagation after audit facility . . . . . . . . . . . . . . .
Time of the last audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Looking up the time of the last audit . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

10-8
10-9
10-10
10-10
10-11
10-12
10-12
10-12
10-14
10-14
10-16
10-17
10-17
10-18
10-18
10-18
10-18
10-19
10-19
10-19
10-24
10-25
10-26
10-26
10-27
10-27
10-28
10-29
10-29
10-29
10-29
10-30
10-31
10-32
10-33
10-35
10-35
10-35
10-36
10-37
10-37
10-38
10-38

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

11-2
11-2
11-3
11-3
11-4
11-5
11-6
11-6
11-6
11-6
11-7
11-8

Chapter 11: Network Expansion

Introduction to network expansion . . . . . . . . . . .
Overview of network expansion . . . . . . . . . .
Prerequisites for using network expansion. . . . .
Network expansion restrictions . . . . . . . . . .
Path error messages recorded in omcaudit log file .
Defining network expansion environment variables
Copying and pasting a BTS . . . . . . . . . . . . . .
Introduction to copying and pasting a BTS. . . . .
Copying and pasting a Horizon II macro BTS . . .
Restrictions to copy and pasting a BTS . . . . . .
Procedure for copying a BTS. . . . . . . . . . . .
Entering hardware devices . . . . . . . . . . . .

xxvi

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Entering logical links . . . . . . . . . . . . . . . . . . . . . . . . . .

Entering radio frequency device information . . . . . . . . . . . . . .
Errors when copying neighbor relations . . . . . . . . . . . . . . . . .
Completing or terminating the operation . . . . . . . . . . . . . . . .
Aborting the copy operation . . . . . . . . . . . . . . . . . . . . . . .
Printing a Progress Dialog window . . . . . . . . . . . . . . . . . . .
Filtering criteria - Progress Dialog window . . . . . . . . . . . . . . .
Reparenting a BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to reparenting a BTS . . . . . . . . . . . . . . . . . . . .
Prerequisites for swapping site LAC and CI operations . . . . . . . . .
Reparenting a BTS by copying and swapping LACs (online only) . . . .
Reparenting a BTS within the same BSS or to another BSS (offline only)
BTS rollback to original BSS . . . . . . . . . . . . . . . . . . . . . . .
Deleting a BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions to deleting a BTS . . . . . . . . . . . . . . . . . . . . . .
Procedure for deleting a BTS . . . . . . . . . . . . . . . . . . . . . .
Aborting a delete operation . . . . . . . . . . . . . . . . . . . . . . .
Network expansion in a daisy chain configuration . . . . . . . . . . . . . .
Introduction to network expansion in a daisy chain . . . . . . . . . . .
Restrictions on network expansion operations . . . . . . . . . . . . . .
Deleting a Site in a daisy chain configuration . . . . . . . . . . . . . . . .
Introduction to deleting a Site in a daisy chain . . . . . . . . . . . . .
Prerequisites to deleting a Site in a daisy chain configuration . . . . . .
Selecting the Site to be deleted . . . . . . . . . . . . . . . . . . . . .
Reconfiguring MMSs for a deleted Site . . . . . . . . . . . . . . . . .
Rolling back a delete operation . . . . . . . . . . . . . . . . . . . . .
Copying a site and inserting it in a daisy chain configuration . . . . . . . .
Introduction to copying a site in a daisy chain . . . . . . . . . . . . . .
Prerequisites to copying and inserting a site in a daisy chain . . . . . .
Copying and inserting a site in a daisy chain. . . . . . . . . . . . . . .
Reconfiguring MMSs for a copied site . . . . . . . . . . . . . . . . . .
Troubleshooting Network expansion . . . . . . . . . . . . . . . . . . . . .
Introduction to troubleshooting . . . . . . . . . . . . . . . . . . . . .
Reporting problems . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore binary object file . . . . . . . . . . . . . . . . . . . . . . . .
Scheduling network expansion . . . . . . . . . . . . . . . . . . . . . . . .
Overview of scheduling . . . . . . . . . . . . . . . . . . . . . . . . .
List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduling a network expansion . . . . . . . . . . . . . . . . . . . . .
Scheduling a new operation . . . . . . . . . . . . . . . . . . . . . . .
Changing default settings . . . . . . . . . . . . . . . . . . . . . . . .
Viewing a batch log . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a scheduled network expansion . . . . . . . . . . . . . . . .
Deleting all scheduled network expansions . . . . . . . . . . . . . . .
Aborting a scheduled batch operation . . . . . . . . . . . . . . . . . .
Network expansion logs . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedures for network expansion logs . . . . . . . . . . . . . . . . .
Viewing a network expansion log . . . . . . . . . . . . . . . . . . . .
Deleting network expansion logs. . . . . . . . . . . . . . . . . . . . .
Aborting/Rollback network expansion . . . . . . . . . . . . . . . . . .
Retrying network expansion . . . . . . . . . . . . . . . . . . . . . . .
Abandoning a single network expansion operation. . . . . . . . . . . .
Managing network expansion logs . . . . . . . . . . . . . . . . . . . . . .
Overview of log management . . . . . . . . . . . . . . . . . . . . . .
Setting the delete period. . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a path using Path Configure menu option . . . . . . . . . . . .
Introduction to configuring a path using Path Configure menu option . .
Definition of terms used in this section . . . . . . . . . . . . . . . . .

68P02901W17-T
Jan 2010

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

11-12
11-15
11-18
11-19
11-19
11-20
11-20
11-22
11-22
11-23
11-24
11-27
11-32
11-34
11-34
11-34
11-36
11-37
11-37
11-37
11-38
11-38
11-38
11-38
11-40
11-43
11-45
11-45
11-45
11-46
11-49
11-52
11-52
11-52
11-53
11-54
11-54
11-54
11-54
11-59
11-62
11-64
11-65
11-66
11-66
11-67
11-67
11-67
11-69
11-70
11-70
11-71
11-72
11-72
11-72
11-73
11-73
11-73

xxvii

Contents

Prerequisites for using configure path facility . . . . . . . . . . . . . . . .

Benefits of using the configure path facility . . . . . . . . . . . . . . . . .
Restrictions to configuring a path . . . . . . . . . . . . . . . . . . . . . .
Initiating a path configure . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying the Path Configure form . . . . . . . . . . . . . . . . . . . . .
Description of the Path Configure form . . . . . . . . . . . . . . . . . . .
Displaying Detailed Views from the Path Configure form . . . . . . . . . .
Tasks available in the Path Configure form. . . . . . . . . . . . . . . . . .
Creating a path using the Path Configure menu option . . . . . . . . . . . . .
Prerequisites to creating a path using the Path Configure menu option . . .
Creating a path using Path Configure menu option . . . . . . . . . . . . .
Deleting a path using the Path Configure menu option. . . . . . . . . . . . . .
Introduction to deleting a path using the Path Configure menu option . . . .
Prerequisites to deleting a path using the Path Configure menu option . . .
Deleting a path using Path Configure menu option. . . . . . . . . . . . . .
Unassigning a device on a path using Path Configure menu option . . . . . . .
Prerequisites to unassigning a device on a path . . . . . . . . . . . . . . .
Unassigning a device on a path using Path Configure menu option . . . . .
Reassigning a device on the primary path using Path Configure menu option . .
Prerequisites to reassigning a device on a primary path . . . . . . . . . . .
Reassigning a device on a primary path using Path Configure menu option .
Reassigning an RTF on the secondary path . . . . . . . . . . . . . . . . . . .
Prerequisites to reassigning an RTF on a secondary path . . . . . . . . . .
Reassigning an RTF on a secondary path using Path Configure menu option
Deleting a device from a site using Path Configure menu option . . . . . . . . .
Prerequisites to deleting a device from a site . . . . . . . . . . . . . . . .
Deleting a device from a site using Path Configure menu option . . . . . . .
Creating an RTF at a site using the Path Configure menu option. . . . . . . . .
Prerequisites to creating an RTF at a site . . . . . . . . . . . . . . . . . .
Creating an RTF at a site using Path Configure menu option . . . . . . . .
Creating an RSL at a site using the Path Configure menu option. . . . . . . . .
Prerequisites to creating an RSL at a site . . . . . . . . . . . . . . . . . .
Creating an RSL at a Site using Path Configure menu option . . . . . . . .
Using flat files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unassigning and reassigning RSLs using flat files . . . . . . . . . . . . . .
Unassigning and reassigning RTFs using flat files . . . . . . . . . . . . . .
Unassigning and reassigning BCCH RTFs using flat files . . . . . . . . . .
Checking if RSL/RTF details are written to a flat file. . . . . . . . . . . . .
Checking if a flat file is present . . . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

11-74
11-74
11-74
11-76
11-76
11-77
11-78
11-79
11-80
11-80
11-80
11-81
11-81
11-81
11-81
11-85
11-85
11-85
11-87
11-87
11-87
11-89
11-89
11-89
11-91
11-91
11-91
11-92
11-92
11-92
11-93
11-93
11-93
11-94
11-94
11-95
11-95
11-96
11-96

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

12-2
12-2
12-2
12-3
12-5
12-5
12-5
12-6
12-7
12-7
12-8
12-9
12-9
12-9
12-10
12-14

Chapter 12: CellXchange

Guidelines for implementing a new frequency plan
Overview to frequency replanning . . . . . . .
Off-Line MIB (OLM) . . . . . . . . . . . . . .
CellXchange . . . . . . . . . . . . . . . . . .
Introduction to CellXchange . . . . . . . . . . . .
Overview of CellXchange . . . . . . . . . . .
Export and import files. . . . . . . . . . . . .
Configuration file (RF.CNFG) . . . . . . . . .
Import/Export progress information . . . . . .
CellXchange log files. . . . . . . . . . . . . .
Setting up automatic deletion of backup files .
Cell-X-Export. . . . . . . . . . . . . . . . . . . .
Cell-X-Export procedure list . . . . . . . . . .
Selecting the network or a specific BSS . . . .
Selecting configuration files . . . . . . . . . .
Selecting export options . . . . . . . . . . . .

xxviii

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

12-16
12-17
12-17
12-17
12-18
12-19
12-22
12-25
12-26
12-27
12-28
12-28
12-28
12-34
12-35
12-35
12-35
12-35
12-36
12-37
12-38
12-38
12-39
12-40
12-40
12-41
12-43
12-43
12-43
12-45
12-47
12-47
12-50
12-52
12-52
12-52
12-53
12-53
12-53
12-67
12-70
12-73

Adding and deleting a user-defined regional map . . . . . . . . . .

Procedures for adding and deleting user-defined regional maps .
Adding a map using the OMC-R GUI . . . . . . . . . . . . . . .
Adding a map using cmutil . . . . . . . . . . . . . . . . . . . .
Deleting a map using the OMC-R GUI . . . . . . . . . . . . . .
Deleting a map using cmutil . . . . . . . . . . . . . . . . . . .
Storing updated map data using cmutil . . . . . . . . . . . . .
Adding and changing a background to a map . . . . . . . . . . . .
Overview of adding or changing a map background . . . . . . .
Obtaining a geographical map background . . . . . . . . . . .
Installing a map background file . . . . . . . . . . . . . . . . .
Selecting and displaying the geographical map background . . .
Adding and deleting a map node . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.

13-2
13-2
13-2
13-2
13-3
13-3
13-3
13-4
13-4
13-4
13-4
13-5
13-6

Starting and monitoring a Cell-X-Export . . . . . . . . . .

Cell-X-Import. . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites to Cell-X-Import . . . . . . . . . . . . . . .
List of procedures . . . . . . . . . . . . . . . . . . . . .
Selecting a network or a specific BSS . . . . . . . . . . .
Selecting configuration files . . . . . . . . . . . . . . . .
Selecting import options . . . . . . . . . . . . . . . . . .
Starting and monitoring a Cell-X-Import . . . . . . . . . .
Aborting a Cell-X-Import . . . . . . . . . . . . . . . . .
Displaying the RF log file . . . . . . . . . . . . . . . . .
Defining CellXchange parameters from the GUI . . . . . . . .
Overview of defining CellXchange parameters . . . . . . .
Defining CellXchange parameters . . . . . . . . . . . . .
Creating an RF configuration file . . . . . . . . . . . . .
CellXchange using the command line . . . . . . . . . . . . .
Overview of command line utilities . . . . . . . . . . . .
Task list . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining environment variables (offline only) . . . . . . .
Configuration file overview . . . . . . . . . . . . . . . .
Description of flags section . . . . . . . . . . . . . . . .
Description of cell parameter section . . . . . . . . . . .
Description of neighbor parameter section . . . . . . . .
Description of handover and power control objects section
Description of site parameter section . . . . . . . . . . .
Description of DRI/RTF parameter section . . . . . . . . .
Description of UTRAN neighbor parameter section . . . .
CellXchange command line utilities . . . . . . . . . . . . . .
Overview of command line utilities . . . . . . . . . . . .
rf_export . . . . . . . . . . . . . . . . . . . . . . . . . .
rf_import . . . . . . . . . . . . . . . . . . . . . . . . . .
rfNcheck . . . . . . . . . . . . . . . . . . . . . . . . . .
correct_rtfs . . . . . . . . . . . . . . . . . . . . . . . .
chg_lac_ci . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Cell-X-Import . . . . . . . . . . . . . . . . .
Overview of Cell-X-Import file . . . . . . . . . . . . . . .
Setting up a dummy ARFCN . . . . . . . . . . . . . . . .
CellXchange import and export tables . . . . . . . . . . . . .
Introduction to exporting/importing parameters . . . . . .
Cell parameters . . . . . . . . . . . . . . . . . . . . . .
Neighbor parameters . . . . . . . . . . . . . . . . . . .
Site parameters . . . . . . . . . . . . . . . . . . . . . .
DRI/RTF parameters . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

Chapter 13: Manipulating Maps

68P02901W17-T
Jan 2010

xxix

Contents

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

13-6
13-7
13-8
13-9
13-11
13-11
13-11
13-12
13-12
13-13

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

14-2
14-2
14-2
14-4
14-4
14-4
14-4
14-5
14-5
14-5
14-6
14-6
14-7
14-7
14-8
14-8
14-8
14-9
14-9
14-9
14-10
14-10
14-10
14-10
14-11
14-11
14-11
14-11
14-12
14-12
14-12
14-12
14-13
14-13
14-14
14-14
14-14
14-15
14-15

Introduction to cmutil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose of cmutil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring new networks using cmutil . . . . . . . . . . . . . . . . . . . . . . . . . . .

15-2
15-2
15-2

Adding a map node . . . . . . . . . . . .

Adding NEs and links to a map . . . . . .
Deleting a map node . . . . . . . . . . . .
Removing NEs and links from a map. . . .
Adding and deleting a map link . . . . . . . .
Introduction to adding a CommsLink . . .
Adding a map link using the OMC-R GUI .
Adding map links using cmutil . . . . . . .
Deleting a map link using the OMC-R GUI .
Deleting map links using cmutil . . . . . .

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

Chapter 14: Optimizing the Network

Overview of optimization. . . . . . . . . . . . . . . . . . .
Overview of the optimization process . . . . . . . . . .
Stages in an optimization exercise . . . . . . . . . . . .
Preparing for optimization . . . . . . . . . . . . . . . . . .
Collecting information . . . . . . . . . . . . . . . . . .
Learning from past experiences . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . .
Checking and changing the current network status . . . . .
Checking and changing network status . . . . . . . . .
Enabling, disabling, and setting key features . . . . . .
Performing sanity checks . . . . . . . . . . . . . . . .
Configuring GPROCs. . . . . . . . . . . . . . . . . . .
Setting network-related parameters . . . . . . . . . . .
Setting network-related timers . . . . . . . . . . . . .
Collecting information about the current network . . . . . .
Collecting statistics . . . . . . . . . . . . . . . . . . .
Collecting customer complaints and issues . . . . . . .
Checking for and rectifying Out Of Service (OOS) devices . .
Auditing sites . . . . . . . . . . . . . . . . . . . . . .
Changing devices to INS . . . . . . . . . . . . . . . . .
Checking for and rectifying hardware defects . . . . . . . .
Introduction to checking and rectifying hardware defects
Hardware defect checks . . . . . . . . . . . . . . . . .
Rectifying hardware defects . . . . . . . . . . . . . . .
Checking for and rectifying database errors . . . . . . . . .
Introduction to checking for database errors . . . . . .
Further information for BSS parameters and commands.
Handover failure checks . . . . . . . . . . . . . . . . .
Dropped call checks . . . . . . . . . . . . . . . . . . .
Call setup failure checks . . . . . . . . . . . . . . . . .
Poor quality checks . . . . . . . . . . . . . . . . . . .
SDCCH blocking checks . . . . . . . . . . . . . . . . .
TCH Blocking checks . . . . . . . . . . . . . . . . . .
Other miscellaneous checks . . . . . . . . . . . . . . .
Using call trace to detect problems . . . . . . . . . . . . .
Using call trace at the OMC-R . . . . . . . . . . . . . .
Using the Call Trace tool (CTP NT) . . . . . . . . . . .
Monitoring network changes. . . . . . . . . . . . . . . . .
Collecting new statistics . . . . . . . . . . . . . . . . .

Chapter 15: cmutil

xxx

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

When to use cmutil . . . . . . . . . . . . . . . . . . . . .

Maximum number of parallel cmutil operations . . . . . . .
Definition of cmutil terms: container and containee . . . . .
Prerequisites for using cmutil . . . . . . . . . . . . . . . .
Logging in for cmutil. . . . . . . . . . . . . . . . . . . . .
cmutil command syntax . . . . . . . . . . . . . . . . . . . . .
Introduction to cmutil command syntax . . . . . . . . . . .
General syntax . . . . . . . . . . . . . . . . . . . . . . . .
primarg (primary argument) . . . . . . . . . . . . . . . . .
secarg (secondary argument) . . . . . . . . . . . . . . . .
secparam (secondary parameter) . . . . . . . . . . . . . .
ASCII file content used with cmutil . . . . . . . . . . . . . . .
Introduction to ASCII file content . . . . . . . . . . . . . .
ASCII file content when adding objects using cmutil . . . . .
ASCII file content when deleting objects using cmutil . . . .
ASCII file content when modifying objects using cmutil . . .
ASCII file content when extracting objects using cmutil . . .
MIB object identification . . . . . . . . . . . . . . . . . . .
ASCII file rules used with cmutil . . . . . . . . . . . . . . . . .
Introduction to ASCII file rules . . . . . . . . . . . . . . .
ASCII file syntax . . . . . . . . . . . . . . . . . . . . . . .
ASCII file content . . . . . . . . . . . . . . . . . . . . . .
Object definition in cmutil ASCII files . . . . . . . . . . . . . .
Introduction to object definition . . . . . . . . . . . . . . .
Description of object definition . . . . . . . . . . . . . . .
Attribute definitions . . . . . . . . . . . . . . . . . . . . .
Integer value. . . . . . . . . . . . . . . . . . . . . . . . .
Enumeration value . . . . . . . . . . . . . . . . . . . . . .
String value . . . . . . . . . . . . . . . . . . . . . . . . .
Object reference . . . . . . . . . . . . . . . . . . . . . . .
Attribute names . . . . . . . . . . . . . . . . . . . . . . .
cmutil status messages . . . . . . . . . . . . . . . . . . . . .
Introduction to cmutil status messages . . . . . . . . . . .
Definition of cmutil status messages . . . . . . . . . . . . .
cmutil warning messages . . . . . . . . . . . . . . . . . .
cmutil error messages . . . . . . . . . . . . . . . . . . . .
cmutil script files . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to cmutil script files . . . . . . . . . . . . . .
MoveCommsLinks . . . . . . . . . . . . . . . . . . . . . .
HierDelete . . . . . . . . . . . . . . . . . . . . . . . . . .
Using cmutil to add, delete, and modify CM MIB data . . . . . .
Introduction to using cmutil . . . . . . . . . . . . . . . . .
Checking input file syntax . . . . . . . . . . . . . . . . . .
Adding objects using cmutil . . . . . . . . . . . . . . . . .
Deleting objects using cmutil . . . . . . . . . . . . . . . .
Updating objects using cmutil . . . . . . . . . . . . . . . .
Modifying multiple devices or functions using cmutil . . . .
Ways of extracting data from the CM MIB . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . .
Extracting data from the CM MIB using cmutil . . . . . . . . .
Overview of extracting data from the CM MIB using cmutil .
Examples of input files and extraction commands . . . . . .
cmutil data extraction examples . . . . . . . . . . . . . . .
Extracting objects using cmutil . . . . . . . . . . . . . . .
Extracting objects and hierarchy of children using cmutil . .
Extracting objects and hierarchy of children of specific type.
Extracting objects with no children of specific type . . . . .
Extracting CommsLinks and associated devices . . . . . . .

68P02901W17-T
Jan 2010

Contents

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

15-2
15-3
15-3
15-3
15-3
15-5
15-5
15-5
15-5
15-6
15-6
15-7
15-7
15-7
15-8
15-8
15-8
15-8
15-10
15-10
15-10
15-11
15-12
15-12
15-12
15-12
15-13
15-13
15-13
15-13
15-15
15-16
15-16
15-16
15-16
15-16
15-17
15-17
15-17
15-17
15-18
15-18
15-18
15-18
15-20
15-21
15-22
15-24
15-24
15-25
15-25
15-25
15-26
15-26
15-27
15-27
15-27
15-28

xxxi

Contents

Extracting information using a macro script . . . . . . . . . .

Extracting data from the CM MIB using SQL . . . . . . . . . . .
Overview of extracting data using SQL . . . . . . . . . . . .
When not to use SQL to extract data . . . . . . . . . . . . . .
Extracting data using SQL queries . . . . . . . . . . . . . . .
SQL script rules . . . . . . . . . . . . . . . . . . . . . . . .
Tips on using SQL queries for MIB. . . . . . . . . . . . . . .
Configuring CommsLinks using cmutil . . . . . . . . . . . . . . .
Introduction to configuring CommsLinks using cmutil . . . . .
Changing CommsLinks using cmutil . . . . . . . . . . . . . .
Adding CommsLinks to existing sites using cmutil . . . . . . .
Deleting CommsLinks from existing sites using cmutil. . . . .
Configuring multiple proxy cells using cmutil . . . . . . . . . . .
Creating multiple proxy cells . . . . . . . . . . . . . . . . .
Modifying multiple proxy cells . . . . . . . . . . . . . . . . .
Deleting multiple proxy cells . . . . . . . . . . . . . . . . . .
Checking paths using cmutil . . . . . . . . . . . . . . . . . . . .
Checking multiple paths using cmutil . . . . . . . . . . . . .
Checking a path for a single site or NE using cmutil . . . . . .
Checking multiple paths in the OMC-R using cmutil . . . . . .
Comparison of cmutil path output with TTY rlogin output . . .
Managing maps using cmutil. . . . . . . . . . . . . . . . . . . .
Creating new maps . . . . . . . . . . . . . . . . . . . . . .
Adding a map using cmutil . . . . . . . . . . . . . . . . . . .
Example map input file . . . . . . . . . . . . . . . . . . . .
Deleting a map using cmutil . . . . . . . . . . . . . . . . . .
Storing updated map data . . . . . . . . . . . . . . . . . . .
Changing a map background using cmutil . . . . . . . . . . .
Adding map links using cmutil . . . . . . . . . . . . . . . . .
Deleting map links using cmutil . . . . . . . . . . . . . . . .
Using cmutil to perform other specific tasks . . . . . . . . . . . .
Introduction to other specific tasks . . . . . . . . . . . . . .
Populating a new MIB database using cmutil . . . . . . . . .
Dumping the entire CM MIB to a file using cmutil . . . . . . .
Managing regions using cmutil . . . . . . . . . . . . . . . .
Changing multiple LACs and/or CIs using cmutil . . . . . . .
Modifying multiple neighbors of same site or NE using cmutil .
Checking multiple hopping objects using cmutil . . . . . . . .

xxxii

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

15-28
15-30
15-30
15-30
15-30
15-31
15-35
15-36
15-36
15-36
15-36
15-37
15-38
15-38
15-38
15-39
15-40
15-40
15-40
15-40
15-41
15-44
15-44
15-44
15-45
15-47
15-47
15-48
15-49
15-50
15-51
15-51
15-51
15-52
15-52
15-53
15-54
15-54

68P02901W17-T
Jan 2010

List
of
Figures

List of Figures

Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure

1-1:
1-2:
1-3:
1-4:
1-5:
2-1:
2-2:
2-3:
2-4:
2-5:
2-6:
2-7:
2-8:
2-9:
4-1:
4-2:
4-3:
4-4:
4-5:
4-6:
4-7:
5-1:
5-2:
6-1:
6-2:
7-1:
7-2:
7-3:
7-4:
7-5:
7-6:
7-7:
7-8:
8-1:
8-2:
8-3:
8-4:
8-5:
8-6:
8-7:
8-8:
8-9:
9-1:
9-2:
9-3:

CM Navigation Tree showing containment relationship . . . . . .

Example of a Detailed View in Edit mode . . . . . . . . . . . . .
OMC-R front panel. . . . . . . . . . . . . . . . . . . . . . . . .
RLogin window . . . . . . . . . . . . . . . . . . . . . . . . . .
Batch File Selection window for a BSS . . . . . . . . . . . . . .
Typical SFH mobile allocations with BCCH frequency excluded . .
Typical SFH mobile allocations with BCCH frequency included . .
Typical example of BBH mobile allocations . . . . . . . . . . . .
BSS Detailed View . . . . . . . . . . . . . . . . . . . . . . . . .
Admin options window. . . . . . . . . . . . . . . . . . . . . . .
NE Field Engineer Password Management status dialog . . . . .
CTU2D PWR mode. . . . . . . . . . . . . . . . . . . . . . . . .
CTU2D CAP mode . . . . . . . . . . . . . . . . . . . . . . . . .
CTU2D ASYM mode . . . . . . . . . . . . . . . . . . . . . . . .
Initial BSS Detailed View in Create mode . . . . . . . . . . . . .
Example of a script file . . . . . . . . . . . . . . . . . . . . . .
Typical BSS database directory structure . . . . . . . . . . . . .
Change Assoc NE ID form (for an Assoc_RXCDR instance) . . . .
.progress log file . . . . . . . . . . . . . . . . . . . . . . . . . .
Log File Selection window . . . . . . . . . . . . . . . . . . . . .
.active log file . . . . . . . . . . . . . . . . . . . . . . . . . . .
CommsLink List showing GPRS links . . . . . . . . . . . . . . .
Typical x25_config file . . . . . . . . . . . . . . . . . . . . . . .
Device and equipment hierarchy for a PCU . . . . . . . . . . . .
Example of PCU containment in the Navigation Tree . . . . . . .
Simplified MSC (SMLC) - BSC-BTS links. . . . . . . . . . . . . .
Hypothetical BSS site . . . . . . . . . . . . . . . . . . . . . . .
Example of adding BTS 2 . . . . . . . . . . . . . . . . . . . . .
Path assignment example . . . . . . . . . . . . . . . . . . . . .
Example of equipping a SITE and MSIs . . . . . . . . . . . . . .
Example of equipping paths . . . . . . . . . . . . . . . . . . . .
Navigation Tree showing SITE hierarchy . . . . . . . . . . . . .
Example of path connections . . . . . . . . . . . . . . . . . . .
CELL Detailed View showing parameter section buttons . . . . .
Cell Parameter Propagation form . . . . . . . . . . . . . . . . .
Navigation Tree showing navigation to the cell algorithm instance
Sources and Neighbors View window in Monitor mode . . . . . .
Power budget algorithm prompt . . . . . . . . . . . . . . . . . .
Neighbor Detailed View Reciprocate form . . . . . . . . . . . . .
Mobile Allocation Selector window - for a GSM 900 cell . . . . . .
Frequency Hopping View . . . . . . . . . . . . . . . . . . . . .
MIB Propagation Dialog Form . . . . . . . . . . . . . . . . . . .
Circuit Status form . . . . . . . . . . . . . . . . . . . . . . . .
Channel Status form . . . . . . . . . . . . . . . . . . . . . . . .
Hierarchy for BSS or RXCDR devices and functions . . . . . . . .

68P02901W17-T
Jan 2010

. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
buttons
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

1-12
1-36
1-40
1-41
1-42
2-7
2-9
2-10
2-206
2-208
2-210
2-225
2-226
2-226
4-8
4-42
4-43
4-83
4-85
4-86
4-87
5-12
5-18
6-4
6-5
7-2
7-3
7-17
7-20
7-21
7-23
7-26
7-41
8-13
8-91
8-96
8-112
8-116
8-117
8-171
8-173
8-214
9-23
9-27
9-29
xxxiii

List of Figures

Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure

xxxiv

9-4: Hierarchy for SITE devices and functions . . . . . . . . . . . . .

9-5: Hierarchy for Hardware Devices . . . . . . . . . . . . . . . . .
9-6: Hierarchy for Software Functions at BSC only. . . . . . . . . . .
9-7: Hierarchy for Logical Links containment . . . . . . . . . . . . .
9-8: Hierarchy for Radio Frequency containment . . . . . . . . . . .
9-9: Hierarchy for Cell containment . . . . . . . . . . . . . . . . . .
9-10: Hierarchy for Handover/Power Control containment . . . . . . .
9-11: Configuration of RTC (InCell). . . . . . . . . . . . . . . . . . .
9-12: RTC hardware addresses . . . . . . . . . . . . . . . . . . . . .
9-13: DRI-Combiner configuration . . . . . . . . . . . . . . . . . . .
9-14: DRI Reassign box. . . . . . . . . . . . . . . . . . . . . . . . .
9-15: Calibrate Site form . . . . . . . . . . . . . . . . . . . . . . . .
9-16: New Standard Configuration form . . . . . . . . . . . . . . . .
9-17: Select DRI(s) form . . . . . . . . . . . . . . . . . . . . . . . .
9-18: Calibration data set at BSS form . . . . . . . . . . . . . . . . .
9-19: EAS Alarms Dialog . . . . . . . . . . . . . . . . . . . . . . . .
9-20: Network showing paths and terminating site . . . . . . . . . . .
11-1: Copy SITE form . . . . . . . . . . . . . . . . . . . . . . . . .
11-2: SITE <Create> form . . . . . . . . . . . . . . . . . . . . . . .
11-3: Path Details form . . . . . . . . . . . . . . . . . . . . . . . . .
11-4: Cell Details Form . . . . . . . . . . . . . . . . . . . . . . . . .
11-5: Copy SITE Progress Dialog window - applying filters . . . . . . .
11-6: Swap site LACs Form . . . . . . . . . . . . . . . . . . . . . . .
11-7: Reparent SITE controlling form . . . . . . . . . . . . . . . . .
11-8: Confirmation window after selecting rollback . . . . . . . . . .
11-9: Delete SITE Progress Dialog window. . . . . . . . . . . . . . .
11-10: Delete SITE daisy chain operation confirmation form . . . . . .
11-11: MMS Reconfiguration form . . . . . . . . . . . . . . . . . . .
11-12: Delete SITE <name> Progress Dialog form . . . . . . . . . . .
11-13: Copy SITE daisy chain operation confirmation form. . . . . . .
11-14: MMS Reconfiguration form . . . . . . . . . . . . . . . . . . .
11-15: Network Expansion Scheduler Detailed View window. . . . . .
11-16: Copy SITE Operation Default Behavior window . . . . . . . . .
11-17: Network Expansion Log window (part 1) . . . . . . . . . . . .
11-18: Network Expansion Log window (part 2) . . . . . . . . . . . .
11-19: Path Configure form. . . . . . . . . . . . . . . . . . . . . . .
11-20: Delete Path Confirmation window . . . . . . . . . . . . . . . .
11-21: Flat file information dialog box . . . . . . . . . . . . . . . . .
12-1: Cell X Export Watcher window . . . . . . . . . . . . . . . . . .
12-2: File Selection window . . . . . . . . . . . . . . . . . . . . . .
12-3: Cell X Import Watcher window . . . . . . . . . . . . . . . . . .
12-4: File Selection window . . . . . . . . . . . . . . . . . . . . . .
12-5: Radio Frequency Import/Export configuration form (partial) . . .
12-6: Cell RF Config Detail View form . . . . . . . . . . . . . . . . .
15-1: Two sites cmutil output example . . . . . . . . . . . . . . . . .
15-2: One site cmutil example with columns and specific labels marked

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

9-30
9-31
9-31
9-32
9-33
9-34
9-34
9-50
9-51
9-65
9-78
9-87
9-88
9-95
9-97
9-107
9-162
11-8
11-11
11-14
11-18
11-21
11-27
11-28
11-33
11-35
11-39
11-40
11-43
11-47
11-48
11-57
11-64
11-68
11-69
11-77
11-83
11-97
12-10
12-12
12-18
12-20
12-29
12-33
15-41
15-43

68P02901W17-T
Jan 2010

List
of
Tables

List of Tables

Table 1-1: Access levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 1-2: Recommended CM command partitioning configuration . . . . . . . . . .
Table 1-3: Same day omcaudit log file naming convention . . . . . . . . . . . . . . .
Table 1-4: MAX_CM_OPS Minimum, maximum, and default Values . . . . . . . . . .
Table 1-5: MAX_CMUTIL_OPS minimum, maximum, and default values . . . . . . . .
Table 2-1: Number of BSC to RXCDR signaling links. . . . . . . . . . . . . . . . . .
Table 2-2: RXCDR-BSCdynamic allocation parameters . . . . . . . . . . . . . . . . .
Table 2-3: BSC-BTS dynamic allocation parameters . . . . . . . . . . . . . . . . . .
Table 2-4: Timer parameters for mobile access class barring . . . . . . . . . . . . .
Table 2-5: Single BCCH parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-6: GPRS and EGPRS coding schemes parameters . . . . . . . . . . . . . . .
Table 2-7: SMS-CB parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-8: 7 MTP level 2 timer parameters. . . . . . . . . . . . . . . . . . . . . . .
Table 2-9: 3 N-value parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-10: Call trace flow control parameters. . . . . . . . . . . . . . . . . . . . .
Table 2-11: ECERM parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-12: Advanced Load Management for EGSM parameters . . . . . . . . . . . .
Table 2-13: GPRS cell reselection modes. . . . . . . . . . . . . . . . . . . . . . . .
Table 2-14: Network Controlled Cell Reselection parameters . . . . . . . . . . . . .
Table 2-15: add_neighbor NCCR-related prompts . . . . . . . . . . . . . . . . . . .
Table 2-16: GPRS interleaving BSS and cell parameters . . . . . . . . . . . . . . .
Table 2-17: Inter-RAT Handover and Enhanced Inter-RAT handover parameters . . .
Table 2-18: Location Services parameters . . . . . . . . . . . . . . . . . . . . . . .
Table 2-19: chg_element and disp_element accepted locations . . . . . . . . . . . .
Table 2-20: Enhanced GPRS One Phase Access parameters . . . . . . . . . . . . . .
Table 2-21: PBCCH/PCCCH parameters . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-22: PBCCH/PCCCH parameters . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-23: Active Codec set modes . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-24: AMR parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-25: GSM HR-specific parameters . . . . . . . . . . . . . . . . . . . . . . .
Table 2-26: Seamless Cell Reselection parameters. . . . . . . . . . . . . . . . . . .
Table 2-27: Current Bucket Level parameters . . . . . . . . . . . . . . . . . . . . .
Table 2-28: Enhanced Scheduling parameters . . . . . . . . . . . . . . . . . . . . .
Table 2-29: Default Band Weightings . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-30: Intelligent Multi Layer Resource Management parameters . . . . . . . .
Table 2-31: Quality of Service parameters . . . . . . . . . . . . . . . . . . . . . . .
Table 2-32: Network Assisted Cell Change (NACC) parameters . . . . . . . . . . . .
Table 2-33: Enhanced Multi-level Precedence and Pre-emption (eMLPP) parameters .
Table 2-34: Fast Call Setup parameters . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-35: RSL congestion control parameters . . . . . . . . . . . . . . . . . . . .
Table 2-36: Possible values for RFT field: Number of Backhaul Timeslots on Carrier
(rtf_ds0_count) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-37: VersaTRAU parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-38: ITS parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-39: GPRS - Suspend/Resume parameters . . . . . . . . . . . . . . . . . . .
68P02901W17-T
Jan 2010

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

1-6
1-7
1-8
1-20
1-21
2-16
2-16
2-20
2-24
2-31
2-40
2-47
2-56
2-57
2-64
2-71
2-79
2-81
2-83
2-87
2-91
2-97
2-105
2-111
2-114
2-117
2-119
2-129
2-133
2-141
2-143
2-145
2-147
2-150
2-151
2-155
2-163
2-166
2-169
2-170

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

2-173
2-174
2-176
2-179
xxxv

List of Tables

Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table

xxxvi

2-40: BSC High Load Protection Mechanism Phase 2 parameters . . . . . . . . . . .

2-41: HSP MTL parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-42: Software patching and PCU Software Upgrade with no BSC Outage parameters
2-43: PCU hardware to increase GPRS capacity parameters. . . . . . . . . . . . . .
2-44: High Bandwidth interconnection between BSC and PCU parameters . . . . . .
2-45: PRP capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-46: Increase the Throughput of PRP with the PCU parameters . . . . . . . . . . .
2-47: Support of Incell as an optional feature parameters . . . . . . . . . . . . . . .
2-48: Field engineering accounts . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-49: BSS User Security Management parameters . . . . . . . . . . . . . . . . . .
2-50: Quality of Service Phase II parameters . . . . . . . . . . . . . . . . . . . . .
2-51: CTU2-D parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-52: Cell OOS Timer Enhancement parameters. . . . . . . . . . . . . . . . . . . .
2-53: TDM Availability Enhancements parameters. . . . . . . . . . . . . . . . . . .
2-54: TD-SCDMA and GSM interworking parameters . . . . . . . . . . . . . . . . .
2-55: Extended Uplink TBF (Temporary Block Flow) parameters . . . . . . . . . . .
2-56: Extended Dynamic Allocation Medium Access Mode (EDMAC) parameters . . .
2-57: Adjustable FER Bins parameters . . . . . . . . . . . . . . . . . . . . . . . .
2-58: Critical Statistics Reporting in 5 minutes parameters . . . . . . . . . . . . . .
2-59: SW enabler for PA bias switch on/off on CTU2D parameters. . . . . . . . . . .
2-60: Dual Abis aware BTS parameters . . . . . . . . . . . . . . . . . . . . . . . .
2-61: Extended Range Cell (ERC) for Data parameters . . . . . . . . . . . . . . . .
2-62: Cage Management parameters . . . . . . . . . . . . . . . . . . . . . . . . .
2-63: Dummy Byte Randomization parameters . . . . . . . . . . . . . . . . . . . .
2-64: Immediate SDCCH Handover parameters . . . . . . . . . . . . . . . . . . . .
2-65: Periodic Traffic Handover parameters . . . . . . . . . . . . . . . . . . . . . .
2-66: Gb over IP feature BSS parameters . . . . . . . . . . . . . . . . . . . . . . .
2-67: Gb over IP feature GBL attributes . . . . . . . . . . . . . . . . . . . . . . . .
2-68: Gb over IP feature NSVC attributes . . . . . . . . . . . . . . . . . . . . . . .
2-69: Increase RSL-LCF capacity on GPROC3/GPROC3-2 parameters . . . . . . . . .
2-70: (R)CTU4 feature set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-71: CTU4 and RCTU4 BSS parameters . . . . . . . . . . . . . . . . . . . . . . .
2-72: CTU4 and RCTU4 BTP and BBU parameters . . . . . . . . . . . . . . . . . .
2-73: CTU4 and RCTU4 DRI parameters. . . . . . . . . . . . . . . . . . . . . . . .
2-74: Modified DRI parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1: Network Detailed View fields - Identification grouping . . . . . . . . . . . . . .
3-2: Network Detailed View fields - State grouping . . . . . . . . . . . . . . . . . .
3-3: Network Detailed View fields - Map Information grouping . . . . . . . . . . . .
3-4: OMC and MSC Detailed View fields - Identification grouping . . . . . . . . . . .
4-1: BSS Detailed View fields - Identification grouping . . . . . . . . . . . . . . . .
4-2: BSS Detailed View fields - State grouping. . . . . . . . . . . . . . . . . . . . .
4-3: BSS Detailed View fields - Network Addresses grouping . . . . . . . . . . . . .
4-4: BSS Detailed View fields - Optional Features grouping . . . . . . . . . . . . . .
4-5: BSS Detailed View fields - Signaling Information grouping . . . . . . . . . . . .
4-6: BSS Detailed View fields - A5 Algorithms grouping . . . . . . . . . . . . . . . .
4-7: BSS Detailed View fields - General grouping . . . . . . . . . . . . . . . . . . .
4-8: BSS Detailed View fields - PCS 1900 Frequency grouping . . . . . . . . . . . .
4-9: BSS Detailed View fields - Flash Information grouping . . . . . . . . . . . . . .
4-10: BSS Detailed View fields - Trunk Information grouping . . . . . . . . . . . . .
4-11: BSS Detailed View fields - Directed Retry grouping . . . . . . . . . . . . . . .
4-12: BSS Detailed View fields - Multiband grouping . . . . . . . . . . . . . . . . .
4-13: BSS Detailed View fields - Enhanced Full Rate grouping . . . . . . . . . . . .
4-14: BSS Detailed View fields - GPRS grouping . . . . . . . . . . . . . . . . . . . .
4-15: BSS Detailed View fields - Map Information grouping . . . . . . . . . . . . . .
4-16: BSS Detailed View fields - Traffic Parameters grouping . . . . . . . . . . . . .
4-17: BSS Detailed View fields - Network Assisted Cell Change grouping . . . . . . .
4-18: BSS Detailed View fields - GPRS Seamless Cell Reselection grouping . . . . . .
4-19: Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2-183
2-186
2-189
2-191
2-194
2-197
2-198
2-199
2-202
2-202
2-213
2-227
2-229
2-230
2-232
2-234
2-236
2-238
2-239
2-242
2-243
2-244
2-247
2-249
2-251
2-252
2-253
2-254
2-255
2-256
2-257
2-258
2-258
2-259
2-262
3-4
3-6
3-6
3-8
4-9
4-10
4-11
4-12
4-17
4-19
4-19
4-27
4-27
4-28
4-29
4-29
4-30
4-30
4-33
4-34
4-34
4-35
4-35

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table

4-20: Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping
4-21: Extension cabinets for Horizon II macro . . . . . . . . . . . . . . . . . . . .
4-22: Cabinet types allowing Horizon II macro_ext as an extension type . . . . . .
4-23: Extension cabinet types allowed for Horizon II mini . . . . . . . . . . . . . .
4-24: Master cabinet types allowed for Horizon II mini extension . . . . . . . . . .
4-25: Cabinet Detailed View fields - Identification grouping . . . . . . . . . . . . .
4-26: Permitted cabinet_type modifications and restrictions . . . . . . . . . . . . .
4-27: Cabinet Detailed View fields - General grouping . . . . . . . . . . . . . . . .
4-28: Cage Detailed View fields - Identification grouping . . . . . . . . . . . . . .
4-29: Assoc_BSS Detailed View fields - Identification grouping . . . . . . . . . . .
4-30: Assoc_BSS Detailed View fields - General grouping . . . . . . . . . . . . . .
4-31: Assoc_RXCDR Detailed View fields - Identification grouping. . . . . . . . . .
4-32: Assoc_RXCDR Detailed View fields - Local Routing Information grouping . . .
4-33: Assoc_RXCDR Detailed View fields - General grouping . . . . . . . . . . . .
4-34: Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping
4-35: DYNETGroup Detailed View fields - Identification grouping . . . . . . . . . .
4-36: DYNET Detailed View fields - Identification grouping . . . . . . . . . . . . .
4-37: DYNET Detailed View fields - Local Routing Information grouping . . . . . .
4-38: DYNET Detailed View fields - path Information grouping . . . . . . . . . . .
5-1: Example Connection report for BSS1015 . . . . . . . . . . . . . . . . . . . .
5-2: Conn_Link Detailed View fields - Identification grouping . . . . . . . . . . . .
5-3: Conn_Link Detailed View fields - Connectivity Information grouping . . . . . .
5-4: CommsLink Detailed View fields - Identification grouping . . . . . . . . . . .
5-5: CommsLink Detailed View fields - Map Information grouping. . . . . . . . . .
5-6: Slot: port settings for OML link . . . . . . . . . . . . . . . . . . . . . . . . .
6-1: PCU contained devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2: PCU Detailed View fields - Identification grouping . . . . . . . . . . . . . . .
6-3: PCU Detailed View fields - Alarm Information grouping. . . . . . . . . . . . .
6-4: PCU Detailed View fields - BSSGP Information grouping . . . . . . . . . . . .
6-5: PCU Detailed View fields - Gb Mapping Information grouping . . . . . . . . .
6-6: PCU Detailed View fields - Gb Statistics Configuration grouping . . . . . . . .
6-7: PCU Detailed View fields - NS Information grouping . . . . . . . . . . . . . .
6-8: PCU Detailed View fields - Address Information grouping . . . . . . . . . . .
6-9: PCU Detailed View fields - General grouping . . . . . . . . . . . . . . . . . .
6-10: DPROC Detailed View fields - Identification grouping . . . . . . . . . . . . .
6-11: PSP Detailed View fields - Identification grouping . . . . . . . . . . . . . . .
6-12: PSP Detailed View fields - Cage and Slot Information grouping . . . . . . . .
6-13: PCU MSI Detailed View fields - Identification grouping . . . . . . . . . . . .
6-14: PCU MSI Detailed View fields - Cage and Slot Information grouping . . . . .
6-15: GDS Detailed View fields - Identification grouping. . . . . . . . . . . . . . .
6-16: GDS Detailed View fields - Connectivity Information grouping. . . . . . . . .
6-17: gsl_lcf_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-18: GSL Detailed View fields - Identification grouping . . . . . . . . . . . . . . .
6-19: GBL Detailed View fields - Identification grouping . . . . . . . . . . . . . . .
6-20: GBL Detailed View fields - Connectivity Information grouping . . . . . . . . .
6-21: GBL Detailed View fields - Frame Relay Information grouping. . . . . . . . .
6-22: NSVC Detailed View fields - Identification grouping . . . . . . . . . . . . . .
6-23: NSVC Detailed View fields - NS Information grouping . . . . . . . . . . . . .
6-24: SGSN Detailed View fields - Identification grouping . . . . . . . . . . . . . .
7-1: Default RSLs - Timeslots and Cages. . . . . . . . . . . . . . . . . . . . . . .
7-2: Default RSLs - Timeslots and Card frame for Horizon II macro Site. . . . . . .
7-3: Default RSLs - Timeslots and Card frame for non Horizon II macro Site . . . .
7-4: SITE Detailed View fields - Identification grouping . . . . . . . . . . . . . . .
7-5: SITE Detailed View fields - General grouping . . . . . . . . . . . . . . . . . .
7-6: SITE Detailed View fields - SMS Information grouping . . . . . . . . . . . . .
7-7: SITE Detailed View fields - GPRS grouping . . . . . . . . . . . . . . . . . . .
7-8: BSS commands for GCLK synchronization . . . . . . . . . . . . . . . . . . .
7-9: BSS parameters for GCLK synchronization . . . . . . . . . . . . . . . . . . .

68P02901W17-T
Jan 2010

List of Tables

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

4-37
4-52
4-52
4-52
4-53
4-55
4-56
4-57
4-60
4-69
4-70
4-73
4-74
4-74
4-75
4-93
4-95
4-96
4-96
5-2
5-6
5-6
5-13
5-13
5-19
6-5
6-9
6-10
6-11
6-11
6-12
6-13
6-14
6-14
6-19
6-23
6-23
6-25
6-25
6-31
6-32
6-34
6-36
6-39
6-40
6-40
6-44
6-45
6-50
7-5
7-6
7-6
7-27
7-28
7-31
7-32
7-44
7-45

xxxvii

List of Tables

Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table

xxxviii

8-1: CELL Detailed View, General - Identification grouping . . . . . . . . . . . . .

8-2: CELL Detailed View fields, General - General grouping . . . . . . . . . . . . .
8-3: CELL Detailed View fields, General - System Access grouping . . . . . . . . .
8-4: CELL Detailed View fields, General - Cell Selection/Reselection grouping . . .
8-5: CELL Detailed View fields, General - Radio Channel Config grouping. . . . . .
8-6: CELL Detailed View fields, General - Queuing grouping . . . . . . . . . . . .
8-7: CELL Detailed View fields, General - Flow Control grouping . . . . . . . . . .
8-8: CELL Detailed View fields, general - channel allocation-deallocation grouping .
8-9: CELL Detailed View fields, general - radio link control grouping . . . . . . . .
8-10: CELL Detailed View fields, general - congestion relief grouping . . . . . . . .
8-11: CELL Detailed View fields, general - directed retry grouping . . . . . . . . .
8-12: CELL Detailed View fields, general - multiband handover grouping . . . . . .
8-13: Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping
8-14: CELL Detailed View fields, General - AMR full rate grouping . . . . . . . . .
8-15: CELL Detailed View fields, General - AMR/GSM Half Rate grouping . . . . .
8-16: CELL Detailed View fields, General - AMR/GSM Half Rate grouping . . . . .
8-17: CELL Detailed View fields, General - Intelligent Selective Paging . . . . . . .
8-18: CELL Detailed View, Handover - Handover - General grouping . . . . . . . .
8-19: CELL Detailed View, Handover - Handover Thresholds grouping . . . . . . .
8-20: CELL Detailed View, Handover - Handover types allowed grouping . . . . . .
8-21: CELL Detailed View, Handover - Handover Timer grouping . . . . . . . . . .
8-22: CELL Detailed View, Handover - Uplink RxQual Handover grouping . . . . .
8-23: CELL Detailed View, Handover - Downlink RxQual handover grouping . . . .
8-24: CELL Detailed View, Handover - Uplink RxLev Handover grouping . . . . . .
8-25: CELL Detailed View, Handover - Downlink RxLev Handover grouping . . . . .
8-26: CELL Detailed View, Handover - Uplink Interference Handover grouping . . .
8-27: CELL Detailed View, Handover - Downlink Interference Handover grouping .
8-28: CELL Detailed View, Handover - Distance Handover grouping . . . . . . . .
8-29: CELL Detailed View, Handover - Power Budget Handover grouping . . . . . .
8-30: CELL Detailed View, Handover - SDCCH Handover grouping . . . . . . . . .
8-31: CELL Detailed View, Handover - Handover - AMR Full Rate grouping . . . . .
8-32: CELL Detailed View, Handover - Handover - AMR/GSM Half Rate grouping . .
8-33: CELL Detailed View, Power Control - Power Control - General grouping. . . .
8-34: CELL Detailed View, Power Control - Rapid MS Power Down grouping . . . .
8-35: CELL Detailed View, Power Control - Uplink Power Control grouping . . . . .
8-36: CELL Detailed View, Power Control - Downlink Power Control grouping . . .
8-37: CELL Detailed View, Pwr Ctrl - Pwr Ctrl - AMR Full Rate grouping . . . . . .
8-38: CELL Detailed View, Pwr Ctrl - Pwr Ctrl - AMR/GSM Half Rate grouping . . .
8-39: CELL Detailed View, GPRS grouping . . . . . . . . . . . . . . . . . . . . .
8-40: CELL Detailed View fields, GPRS - Ntwk Ctrld Cell Reselection grouping . . .
8-41: GSM cell propagation parameters . . . . . . . . . . . . . . . . . . . . . .
8-42: GSM cell propagation parameters with GSM Half Rate unrestricted . . . . .
8-43: Algorithm Detailed View - Identification grouping . . . . . . . . . . . . . . .
8-44: Algorithm Detailed View - General grouping. . . . . . . . . . . . . . . . . .
8-45: chg_cell_element rel_tim_adv and chg_cell_element surround_cell . . . . . .
8-46: chg_cell_element rxlev_dl_ho and chg_cell_element rxlev_ul_ho . . . . . . . .
8-47: Neighbor Detailed View fields - Identification grouping . . . . . . . . . . . .
8-48: Neighbor Detailed View fields - General grouping . . . . . . . . . . . . . . .
8-49: Neighbor Detailed View fields - Power Budget Algorithm grouping . . . . . .
8-50: Neighbor Detailed View fields - Directed Retry grouping . . . . . . . . . . .
8-51: Neighbor Detailed View fields - Concentric Cells grouping . . . . . . . . . .
8-52: UTRAN neighbor parameters and values . . . . . . . . . . . . . . . . . . .
8-53: UTRAN Blind Search Neighbor Detailed View Fields General grouping. . .
8-54: ProxyCELL Detailed View fields - Identification grouping . . . . . . . . . . .
8-55: ProxyCELL Detailed View fields - Proxy Cell Data grouping . . . . . . . . . .
8-56: ProxyCELL Detailed View fields - Identification grouping . . . . . . . . . . .
8-57: ProxyCELL Detailed View fields - ProxyCELL Data grouping . . . . . . . . .
8-58: Command line options for pcellImport . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

8-14
8-16
8-19
8-21
8-22
8-23
8-24
8-25
8-26
8-26
8-28
8-29
8-33
8-33
8-39
8-46
8-47
8-48
8-50
8-51
8-52
8-52
8-54
8-55
8-56
8-56
8-57
8-58
8-58
8-59
8-60
8-61
8-63
8-64
8-64
8-66
8-67
8-68
8-71
8-77
8-79
8-89
8-97
8-97
8-100
8-101
8-121
8-123
8-125
8-126
8-126
8-135
8-140
8-144
8-144
8-147
8-147
8-158

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table

8-59: Frequency hopping cell parameters . . . . . . . . . . . . . . . .

8-60: Frequency hopping maximum frequency number . . . . . . . . .
8-61: FreqHopSys Detailed View fields - Identification grouping . . . .
8-62: FreqHopSys Detailed View fields - General grouping . . . . . . .
8-63: Coincident multiband handover parameters . . . . . . . . . . . .
8-64: Adaptive handover parameters . . . . . . . . . . . . . . . . . .
8-65: Ping Pong limitation parameters. . . . . . . . . . . . . . . . . .
8-66: Flexible neighbor processing parameters . . . . . . . . . . . . .
8-67: erc_ta_priority parameter . . . . . . . . . . . . . . . . . . . .
8-68: Optimizing cell power control parameters . . . . . . . . . . . . .
8-69: Timeslots on multiple GPRS carriers configured for performance .
8-70: Timeslots on multiple GPRS carriers configured using OSA . . . .
8-71: Multiple GPRS carriers per cell parameters . . . . . . . . . . . .
8-72: rpt_bad_qual_no_mr parameter . . . . . . . . . . . . . . . . . .
8-73: SDCCH parameters . . . . . . . . . . . . . . . . . . . . . . . .
8-74: SDCCH parameters with combined channel configurations . . . .
8-75: SDCCH parameters with NON-combined channel configurations .
8-76: Value ranges for max_tx_bts . . . . . . . . . . . . . . . . . . . .
8-77: (R)CTU4 output values without any stage of combining . . . . . .
8-78: SMSCBmsg Detailed View fields - Identification grouping . . . . .
8-79: SMSCBmsg Detailed View fields - SMS Information grouping . . .
9-1: VersaTRAU (VT) channel information in Channel Status form. . . .
9-2: BSP cage and slot restrictions . . . . . . . . . . . . . . . . . . .
9-3: BSP Detailed View fields - Identification grouping . . . . . . . . .
9-4: BSP Detailed View fields - Cage and Slot Information grouping . . .
9-5: BTP cage and slot restrictions . . . . . . . . . . . . . . . . . . .
9-6: BTP Detailed View fields - Identification grouping . . . . . . . . .
9-7: BTP Detailed View fields - Cage and Slot Information grouping . . .
9-8: BTP Detailed View fields - State Information grouping . . . . . . .
9-9: CBL Detailed View fields - Identification grouping . . . . . . . . .
9-10: COMB Detailed View fields - Identification grouping . . . . . . .
9-11: GPROC cage and slot restrictions . . . . . . . . . . . . . . . . .
9-12: CSFP Detailed View fields - Identification grouping . . . . . . . .
9-13: DHP cage and slot restrictions. . . . . . . . . . . . . . . . . . .
9-14: DHP Detailed View fields - Identification grouping . . . . . . . .
9-15: DHP Detailed View fields - Cage and Slot Information grouping . .
9-16: DHP Detailed View fields - State Information grouping . . . . . .
9-17: DRI Detailed View fields - Identification grouping . . . . . . . . .
9-18: DRI Detailed View fields - Cage and Slot Information grouping . .
9-19: DRI Detailed View fields - Additional State Information grouping .
9-20: DRI Detailed View fields - Preferred RTF grouping . . . . . . . .
9-21: DRI Detailed View fields - DRI RCU grouping . . . . . . . . . . .
9-22: DRI Detailed View fields - Combiner 1 grouping . . . . . . . . . .
9-23: DRI Detailed View fields - Shared Cells grouping . . . . . . . . .
9-24: DRI Detailed View fields - Port Connections grouping . . . . . . .
9-25: DRI Detailed View fields - Power Distribution Board grouping . . .
9-26: Bay level calibration parameters. . . . . . . . . . . . . . . . . .
9-27: Rx A and Rx B receive path options . . . . . . . . . . . . . . . .
9-28: Severity level definitions. . . . . . . . . . . . . . . . . . . . . .
9-29: EAS Detailed View fields - Identification grouping . . . . . . . . .
9-30: EAS Detailed View fields - Cage and Slot Information grouping . .
9-31: EAS Detailed View fields - OptoCoupler groupings . . . . . . . .
9-32: EAS Detailed View fields - Relay Information grouping . . . . . .
9-33: GCLK Detailed View fields - Identification grouping . . . . . . . .
9-34: GCLK Detailed View fields - Cage and Slot Information grouping .
9-35: GPROC cage and slot numbers . . . . . . . . . . . . . . . . . .
9-36: GPROC Detailed View fields - Identification grouping . . . . . . .
9-37: GPROC Detailed View fields - Cage and Slot Information grouping

68P02901W17-T
Jan 2010

List of Tables

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

8-165
8-169
8-172
8-172
8-181
8-186
8-193
8-195
8-201
8-203
8-207
8-208
8-209
8-224
8-227
8-229
8-229
8-234
8-236
8-245
8-245
9-26
9-35
9-36
9-37
9-39
9-40
9-41
9-42
9-44
9-52
9-55
9-55
9-59
9-61
9-61
9-62
9-69
9-73
9-73
9-73
9-74
9-74
9-75
9-75
9-76
9-82
9-89
9-102
9-108
9-109
9-110
9-110
9-114
9-115
9-116
9-117
9-118

xxxix

List of Tables

Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table

xl

9-38: GPROC Detailed View fields - State Information grouping . . . . . . . . .

9-39: KSWpair Detailed View fields - Identification grouping . . . . . . . . . .
9-40: KSW Detailed View fields - Identification grouping . . . . . . . . . . . .
9-41: KSW Detailed View fields - Cage and Slot Information grouping. . . . . .
9-42: LCF Detailed View fields - Identification grouping . . . . . . . . . . . . .
9-43: LMTL parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-44: LMTL Loadshare Granularity parameter. . . . . . . . . . . . . . . . . .
9-45: MSI Detailed View fields - Identification grouping . . . . . . . . . . . . .
9-46: MSI Detailed View fields - Cage and Slot Information grouping . . . . . .
9-47: MSI Detailed View fields - MMS HDSL Information grouping . . . . . . .
9-48: Enhanced GDP Provisioning parameters. . . . . . . . . . . . . . . . . .
9-49: MTL Detailed View fields - Identification grouping . . . . . . . . . . . .
9-50: MTL Loadshare Granularity parameter . . . . . . . . . . . . . . . . . .
9-51: OMF Detailed View fields - Identification grouping . . . . . . . . . . . .
9-52: OML Detailed View fields - Identification grouping . . . . . . . . . . . .
9-53: Abis link cage timeslots . . . . . . . . . . . . . . . . . . . . . . . . . .
9-54: Default RSLs - Timeslots and Card frame for Horizon II macro Site . . . .
9-55: Default RSLs - Timeslots and Card frame for non Horizon II macro Site . .
9-56: PATH Detailed View fields - Identification grouping . . . . . . . . . . . .
9-57: PATH Detailed View fields - Path information grouping . . . . . . . . . .
9-58: RSL Detailed View fields - Identification grouping . . . . . . . . . . . . .
9-59: RSL Detailed View fields - LapD Information grouping . . . . . . . . . .
9-60: RSL Detailed View fields - MMS Timeslots grouping. . . . . . . . . . . .
9-61: RTF Detailed View fields - Identification grouping . . . . . . . . . . . . .
9-62: RTF Detailed View fields - Carrier 1 Information grouping . . . . . . . .
9-63: RTF Detailed View fields - Concentric cells grouping . . . . . . . . . . .
9-64: RTF Detailed View fields - GPRS grouping . . . . . . . . . . . . . . . . .
9-65: RTF Detailed View fields - MMS Timeslot grouping . . . . . . . . . . . .
9-66: RTF Detailed View fields - General grouping. . . . . . . . . . . . . . . .
9-67: RTF Detailed View fields - AMR/GSM Half Rate grouping . . . . . . . . .
9-68: XBL Detailed View fields - Identification grouping . . . . . . . . . . . . .
9-69: XBL Detailed View fields - LapD Information grouping . . . . . . . . . .
10-1: Values propagated after an audit . . . . . . . . . . . . . . . . . . . . .
11-1: Example of a successful swap site LAC operation . . . . . . . . . . . . .
11-2: Example of an unsuccessful swap site LAC operation . . . . . . . . . . .
11-3: Example of an unsuccessful swap site LAC operation . . . . . . . . . . .
11-4: Reparent site - Examples of OMC Device Transition States . . . . . . . .
11-5: Delete SITE - Examples of OMC-R Device Transition States . . . . . . . .
11-6: Default Actions when copying, deleting, reparenting a site . . . . . . . .
12-1: RF General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12-2: Configuration file parameters . . . . . . . . . . . . . . . . . . . . . . .
12-3: Command line options (rf_export) . . . . . . . . . . . . . . . . . . . . .
12-4: Command line options (rf_import) . . . . . . . . . . . . . . . . . . . . .
12-5: Command line options (rfNcheck) . . . . . . . . . . . . . . . . . . . . .
12-6: Command line options (correct_rtfs) . . . . . . . . . . . . . . . . . . . .
12-7: RTF attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12-8: RFPlanCell default parameters . . . . . . . . . . . . . . . . . . . . . .
12-9: User selectable cell parameters . . . . . . . . . . . . . . . . . . . . . .
12-10: User selectable cell parameters with GSM Half Rate unrestricted . . . .
12-11: RFPlanNeighbor default parameters . . . . . . . . . . . . . . . . . . .
12-12: User selectable Neighbor parameters . . . . . . . . . . . . . . . . . .
12-13: Site parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12-14: DRI parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12-15: RTF parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15-1: FreqHopSys attribute details . . . . . . . . . . . . . . . . . . . . . . .
15-2: Path attributes link(1 ... 10) (stored outside pathtable2, in intlisttable2) .
15-3: Path attribute commsLinkList (stored outside pathtable2 in oidlisttable2).
15-4: Mangled object classes with resulting table names . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

9-118
9-120
9-124
9-125
9-128
9-131
9-135
9-139
9-140
9-141
9-147
9-153
9-156
9-159
9-161
9-166
9-166
9-166
9-168
9-168
9-178
9-178
9-179
9-186
9-187
9-189
9-189
9-190
9-190
9-191
9-199
9-200
10-35
11-23
11-23
11-24
11-31
11-36
11-62
12-30
12-37
12-44
12-45
12-47
12-48
12-49
12-54
12-55
12-67
12-68
12-69
12-70
12-74
12-76
15-33
15-33
15-33
15-34

68P02901W17-T
Jan 2010

List of Tables

Table 15-5: Example of OIDs mangled in OSP 4 . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-6: cmutil output use of columns . . . . . . . . . . . . . . . . . . . . . . . . . . . .

68P02901W17-T
Jan 2010

15-34
15-41

xli

List of Tables

xlii

68P02901W17-T
Jan 2010

About
This
Manual

Installation and Configuration: GSM System

Configuration

What is covered in this manual?

This manual provides information and procedures to enable an experienced and qualified user
at the OMC-R to configure Motorola GSM Network Elements and objects, and to populate the
Configuration Management database. This manual should be used with the OMC-R operating on
one of the following series platforms:

SunFire 4800 and SunFire 4900

Netra20

SunBlade 150

Netra 440 platform

Chapter 1 Configuration Management general information: This chapter provides useful

information to assist in the configuration of a GSM system. For example, this chapter includes:

Recommended working practices.

Description of the CM Management Information Base (MIB).

Uploading an NE database to the OMC-R.

Using the Navigation Tree and Detailed Views to create, modify and delete network objects.

Remotely logging in to a BSS from the OMC-R GUI and changing security levels.

Chapter 2 Configuring BSS features: This chapter provides an overview of BSS features
and how to configure them from the OMC-R.
Chapter 3 Configuring Network, OMC-R and MSC instances: This chapter describes the
procedures to be followed to add a Network, OMC-R or MSC object to the OMC-R Navigation
Tree.

68P02901W17-T
Jan 2010

Chapter 4 Configuring a BSS/RXCDR: This chapter describes how to configure a BSS or

RXCDR. It covers topics such as:

Adding a BSS/RXCDR to a network.

Creating a BSS/RXCDR database.

Equipping cabinets and cages.

Configuring an Assoc_BSS and Assoc_RXCDR.

Changing the NE ID of an Assoc_BSS/Assoc_RXCDR.

Reparenting a BSS/RXCDR.

Creating Dynets and DynetGroups.

Chapter 5 Configuring connectivity: This chapter describes how to create and check
connectivity between the following:

Network Elements and OMC-R

BSS and MSC (through an RXCDR)

BSS/RXCDR and OMC-R

Chapter 6 Configuring a PCU for GPRS: This chapter describes configuring a Packet Control
Unit (PCU). It covers General Packet Radio Service (GPRS) PCU topology, equipping PCU
contained devices, and configuring a Serving GPRS Support Node (SGSN).
Chapter 7 Configuring a site: This chapter describes configuring BTS and BSC sites. It
covers topics such as:

Description of sites.

Adding, deleting, and modifying sites.

Equipping cabinets and cages at a remote BTS.

Extending paths.

Generic clock synchronization.

Barring calls at a site.

Chapter 8 Configuring cells: This chapter describes how to configure cells, neighbors, and
proxy cells from the OMC-R GUI using Detailed Views or TTY interface commands. In addition,
this chapter includes procedures to manipulate specific cell parameters, and bar calls at a cell.
Chapter 9 Configuring devices and functions: This chapter describes equipping devices
and functions using the OMC-R GUI Navigation Tree or TTY interface. These procedures are
referenced throughout the manual but are collected together in this chapter for convenience.
Chapter 10 Auditing: This chapter describes the purpose of an audit, and how to run and
schedule an audit.
Chapter 11 Network Expansion: This chapter describes how to expand the network,
including copying and reparenting a BTS.

68P02901W17-T
Jan 2010

Chapter 12 CellXchange: This chapter describes how to use the OMC-R GUI CellXchange
facility to import and export cell parameters. This may be necessary in order to replan network
frequencies.
Chapter 13 Manipulating maps: This chapter describes the facilities available to manipulate
background geographical maps. The procedures described use both the OMC-R GUI Navigation
Tree and the cmutil utility. The following procedures are described, for example:

Adding and deleting a user-defined regional map.

Adding and changing a map background.

Adding and deleting a map node.

Adding and deleting a map link.

Chapter 14 Optimizing the network: This chapter gives advice, guidelines and
recommendations about how to perform an optimization of the network from the OMC-R.
Chapter 15 cmutil: This chapter describes the cmutil utility, and the configuration
management operations it can perform.

68P02901W17-T
Jan 2010

Revision history

Revision history

The following sections show the revision status of this document.

Version information
The following table describes the changes made to this document:
Version

Date of issue

Description

Dec 2008

GSM Software Release 9 FP1

Jan 2010

GSM Software Release GSR10

Release information
This section describes the changes in this document between release GSR9 and GSR10.

Gb over IP

Reduced number of LCFs

CTU4

PA bias in mixed radio Horizon II sites

Changing scratchpad parameters into CM parameters

E-EDGE (Dual Downlink Carrier)

CTU4 and RCTU4 8 carrier support.

Resolution of Service Requests

The following Service Requests are resolved in this document:

Service
Request

CMBP Number

NA

NA

Description
Initial release

68P02901W17-T
Jan 2010

General information

General information

Purpose
Motorola documents provide the information to operate, install, and maintain Motorola
equipment. It is recommended that all personnel engaged in such activities be properly trained
by Motorola.
Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.

NOTE
If this document was obtained when attending a Motorola training course, it is not
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then Motorola automatically supplies corrections and posts on the Motorola
customer website.

Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.

Document banner definitions

A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY UNDER DEVELOPMENT

68P02901W17-T
Jan 2010

Text conventions

Text conventions
The following conventions are used in Motorola documents to represent keyboard input text,
screen output text, and special key sequences.

Input
Characters typed in at the keyboard are shown like this sentence.
Items of interest within a command appear like this sentence.

Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this sentence.
Items of interest within a screen display appear like this sentence.

Special key sequences

Special key sequences are represented as follows:

CTRL-c or CTRL+C

Press the Ctrl and C keys at the same time.

CTRL-SHIFT-c or
CTRL+SHIFT+C

Press the Ctrl, Shift, and C keys at the same time.

ALT-f or ALT+F

Press the Alt and F keys at the same time.

ALT+SHIFT+F11

Press the Alt, Shift and F11 keys at the same time.

Press the pipe symbol key.

RETURN or ENTER

Press the Return or Enter key.

68P02901W17-T
Jan 2010

Contacting Motorola

Contacting Motorola

Motorola appreciates feedback from the users of our documents.

24hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Office.

Ordering documents and CD-ROMs

With internet access available, to view, download, or order documents (original or revised), visit
the Motorola customer web page at https://mynetworksupport.motorola.com, or contact your
Motorola account representative.
Without internet access available, order hard-copy documents or CD-ROMs from your Motorola
Local Office or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.

Questions and comments

Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.

Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):

The document type

The document title, part number, and revision character

The page number with the error

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

68P02901W17-T
Jan 2010

Errors

68P02901W17-T
Jan 2010

Chapter

1
Configuration Management General
Information

General information relating to the configuration of a GSM network from the OMC-R is provided
here. The following topics are described:

Recommendations for Configuration Management on page 1-2.

Management Information Base (MIB) on page 1-11.

Definition of a Network Element (NE) on page 1-23.

Uploading an NE database to the OMC-R on page 1-24.

Configuring network objects using the OMC-R GUI on page 1-26.

Navigating to a network object class or instance on page 1-28.

Using Detailed Views on page 1-30.

Creating a network object using the OMC-R GUI on page 1-32.

Modifying a network object using the OMC-R GUI on page 1-34.

Deleting a network object using the OMC-R GUI on page 1-37.

Remotely logging in to a BSS site from the OMC-R on page 1-39.

Changing security level (for TTY interface commands) on page 1-43.

Remotely logging in to a BSS using WebMMI on page 1-45.

Making wide area modifications on page 1-49.

68P02901W17-T
Jan 2010

1-1

Recommendations for Configuration Management

Chapter 1: Configuration Management General Information

Recommendations for Configuration Management

Introduction to Configuration Management

This section gives recommendations on the following subjects:

Weekly procedures.

Offline and online network changes.

Working practices.

Preventing rlogin.

Command partitioning.

Tracking logged Configuration Management (CM) changes.

online CM setup.

Interrogating the network using the COP GLU tool.

Upgrade information.

Recommended weekly procedures

The following weekly procedures are recommended:

Check Audit schedules and the resulting update of OMC-R CM database.

Carry out NE database checks.

Hold a weekly meeting.

Schedule a weekly meeting between all concerned parties to discuss the following:
Any outstanding service affecting faults from the previous week.
Review configuration changes and planned maintenance work from the previous week.

1-2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Off-line and online network change recommendation

Planned work for the week ahead.

Any issues relating to the future planning or expansion of the network.
Prepare a summary weekly report before the meeting. Circulate the actions agreed
upon at the meeting.

NOTE
Further information about recommended weekly procedures can be found
in OMC-R Online Help, Network Operations.

Off-line and online network change recommendation

Network Configuration Management takes two forms, off-line configuration and online
configuration.

Off-line Configuration Management

Off-line Configuration Management is used for large scale network changes, such as frequency
replanning, and rapid network expansion which involves rolling out new CM database.
The DataGen tool is the recommended method of producing new database. The DataGen tool
features RevGen Upgrader, Compiler, and MCDF tables. The DataGen tool also has an off-line
MIB feature which allows the online MIB to be recreated off-line. See System Information:
DataGen (68P02900W22) for further details.

Online Configuration Management

Online Configuration Management is used for small scale network changes. It is performed
by a dedicated online CM team working on live BSSs, based on job orders from other groups,
such as the optimization or BSS roll out team.
The OMC-R GUI is the preferred tool for online expansion. The recommended method is using
Detailed Views accessed using the OMC-R GUI Navigation Tree. The other method is to use
Remote Login (Rlogin) and type TTY interface commands directly into the BSS.
The export and import of RF planning data to/from a third-party planning tool can also take
place online using the OMC-R GUI.
When using the Remote Login method, if the OML to the network element is in service and
there is no MIB lock on the corresponding object, any database changes are propagated to the
MIB. These changes are logged using attributeStateChangeEvents, objectCreateEvents, or
objectDeleteEvents in the event logs.

68P02901W17-T

1-3
Jan 2010

Working practice recommendation

Chapter 1: Configuration Management General Information

Working practice recommendation

The following work practices are recommended:

Always consult with the CM supervisor before carrying out work on any site which involves
changes to the CM Database setup.

Always inform the FM supervisor before resetting any live devices.

If possible, restrict the number of users working on a BSS to one at a time.

Only one user can carry out work on a site at a time.

Disable download to the BSS for the duration of the CM work.

Always upload the database upon completion of a job order.

The recommended method of making changes to devices is using the Navigation Tree and
Detailed Views in Edit mode. This method ensures that the device being worked on is
locked in the MIB database, preventing other users from making changes on that object.
See Configuring network objects using the OMC-R GUI on page 1-26 for details.

Preventing remote login

Rlogin functionality is still frequently used, and is the preferred method of configuration for
some users who are familiar with TTY commands and database parameters. Others prefer to
use the OMC-R GUI with its user-friendly interface.
Rlogin functionality is designed independently of MIB, and changes can be made using the
rlogin method regardless of whether the object is locked or not. There are advantages and
disadvantages to this method:

1-4

Main advantage is that changes can be made to the BSS CM database regardless of the
state of the CM MIB. The BSS CM database is the live (revenue generating) database.
The CM MIB is a model of this data used centrally to manage the network. Therefore
any change can be applied retrospectively to the MIB (using Audit) with no effect on
the revenue stream.

Main disadvantage is that if strict work practices are not implemented to restrict CM staff
changing BSS parameters, then the network manager can lose control of the network
configuration. As result revenue opportunities may be missed. For example, if uncontrolled
changes are made to the frequency plan, they could introduce excess interference into the
network and reduce the available capacity.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Command partitioning using the GUI

Local maintenance parameter

Rlogin users and local maintenance terminal users can be prevented from accessing a BSS.
This ensures that changes are only made using the OMC-R GUI. Set the local maintenance
(BSS parameter name: Local_maintenance) parameter field to Yes in the BSS Detailed View.
This method is secure, because the rlogin user cannot reset this parameter without going to
SYSGEN mode. The procedure can therefore be:
1.

Before starting a job order, set local maintenance parameter to No.

2.

After completing a job order, set local maintenance parameter to Yes.

3.

After completing a job order, exit Edit mode of Detailed View.

Applying the local maintenance parameter for a single BSS

Use the following procedure to apply the local maintenance parameter for a single BSS:

Procedure 1-1 Apply local maintenance parameter for a single BSS

1

Edit the BSS Detailed View in the Navigation Tree.

Set the Local Maintenance parameter field in the Identification

grouping to No (0).

Save the changes by selecting File Save from the menu bar.

Exit the Detailed View.

Applying the local maintenance parameter for whole OMC-R

The local maintenance parameter can be set to Yes or No for a whole OMC-R. Create a simple
shell script that reads NE.MAP to get the different BSSs and runs a cmutil update script for
each of the BSSs found.

Command partitioning using the GUI

The command partitioning facility provides a means of partitioning OMC-R users into different
security areas. Depending on which security area a user has access to, options that could be
used to alter OMC-R/BSS information are allowed/disallowed on the OMC-R GUI. Command
partitioning also improves OMC-R usability by giving users a smaller, easier, and more applicable
selection of menu options from which to choose. Only the GUI is command partitioned, OMC-R
UNIX scripts still need existing permissions to run. Setting up command partitioning is detailed
in: OMC-R Online Help, Network Operations.
This feature provides the operator with the ability to determine which commands can be
assigned to a specific level through the use of a new MMI command as part of command
partitioning control.

68P02901W17-T

1-5
Jan 2010

Command partitioning using the GUI

Chapter 1: Configuration Management General Information

A user is authenticated at the OMC-R whenever they first login using a UNIX account setup
by OMCADMIN. When a user uses remote login to access a NE from the OMC-R, the user is
automatically authenticated using their UNIX login. If regions are enabled, the username is
compared to a list of NEs held at the OMC-R to determine if the user has access to the NE.
Each OMC-R user has an access level of 1 to 4 defined in a user profile table. This determines
what level of MMI and/or EMON command access they have, once logged in. If they have
access rights to a particular NE while logged into the OMC-R, their user ID and user profile
are compared to determine the level of command access. Command partitioning is assigned as
follows: Levels 1 to 4 for MMI commands and levels 1 to 2 for EMON commands.

Table 1-1 Access levels

Access levels

MMI Access Level

EMON Access Level

By default, all OMC-R account users have access level 4, which allows all the commands to be
executed.
Follow Procedure 1-2 to change the access levels for a user.

Procedure 1-2 Changing the access levels for a user

1-6

Start the OMC-R GUI as omcadmin.

Open the Admin menu from the OMC-R GUI front panel and select the Access
Control option.

Double click the user ID to access the user profile detailed view.

Select Edit Edit to enter edit mode. Go to the NE Access section of the
form and change to the appropriate value.

Select File Save.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Tracking logged CM changes

Table 1-2 shows the recommended CM command partitioning configuration.

Table 1-2

Recommended CM command partitioning configuration

Subject

Person usually
responsible

Load Management (LM)

Supervisor

All action options under load management

in the GUI.

BSS rlogin (RLog)

Supervisor/Operator

TTY and batch rlogin.

Subscription
Management (Subs)

Supervisor

Changes to the subscriptions and

subscription lists.

Alarm handling (Alarms)

Alarm handler (Not

required for CM)

Handle alarms option in alarm window.

Fault Management
commands (FM)

Supervisor/Operator

Device administration of BSS devices

after creation.

Statistics Management
(Stat)

Supervisor/Operator

Enabling/disabling statistics on BSS

through GUI.

Map Management
(Map)

Supervisor/Operator

Create, save, and delete options under

network icon.

Configuration
Management (CM)

Supervisor/Operator

Create/delete/edit of all detailed

views/commslinks.

Audit

Supervisor

Audit scheduler and logs. All audit and

PM resync options using GUI.

Resync

Supervisor

Resync scheduler and logs options listed.

Cell Propagation
(CellProp)

Supervisor/Operator

Cell parameter propagation.

Access Control (Access)

OMC-R Administrator
or Access Controller
(Not required for CM)

Changing command partitioning options

for all users.

OMC-R Administration
(Admin)

OMC-R Administrator
(Not required for CM)

Modifying blacklist and pager

subscriptions.

Functions enabled

Tracking logged CM changes

There are several ways of monitoring changes to the network. These are explained in this
section.

Event logs - logging of all CM changes

The recommended method of tracking logged CM changes to the network is using the
attributeStateChangeEvents and objectCreateEvents stored in the event logs. Any
database changes to existing devices/functions made using the Navigation Tree, Audit, or
rlogin are logged using attributeStateChangeEvents (AVCs) in the event logs. Any new
devices created/deleted are also logged using objectCreateEvents / objectDeleteEvents in
the event logs.

68P02901W17-T

1-7
Jan 2010

Tracking logged CM changes

Chapter 1: Configuration Management General Information

omcaudit log file - logs all CM changes

The omcaudit log file is a general-purpose log file, which records OMC-R system activity. The
file can be found in:
/usr/omc/logs/
A new omcaudit log file is created each day. The date of creation is included in the omcaudit log
file name in the following format:
omcaudit<yyyymmdd>
For example, the omcaudit log file for 14th December 2004, would be named: omcaudit20041214.
When an omcaudit log file becomes full, the OMC-R automatically creates a file. To distinguish
between omcaudit log files for a specific day, the dated log files are also sequentially numbered
using the convention shown in Table 1-3. Table 1-3 shows three omcaudit log files created for
the same day, that is, 14th December 2004.

Table 1-3 Same day omcaudit log file naming convention

Description

omcaudit log file

omcaudit20041214_1

The first full omcaudit log file of the day.

omcaudit20041214_2

The second full omcaudit log file of the day.

omcaudit20041214

The third omcaudit log file of the day. On the 14th

December 2004, this file would have been the log file
to which the OMC-R was currently writing. If this
file had become full, it would have been renamed
omcaudit20041214_3, and so on.

An omcaudit log file can be viewed using the commands: cat or more. For example:
cat omcaudit20041214_1
or
more omcaudit20041214_1
Use the following command to track CM only changes:
grep cm :

/usr/omc/logs/omcaudit* >/tmp/omcaudit_stripped

usraudit log file

Messages from the GUI are logged in the usraudit log file. The file can be found in:
/usr/omc/logs/usrauditlogs

1-8

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Online Configuration Management setup

BSS log files - logging of rlogin changes (TTY and batch rlogin changes)
Two environment variables (in Common.csh) determine where these logs are kept, and if they
are enabled. Log files are stored on a per BSS/per session basis.

RL_BSSLOGDIR identifies the directory used for storing all files detailing BSS command
activity.
Use: setenv RL_BSSLOGDIR $OMC_TOP/logs/bss

RL_LOGCMDS controls the logging facility for BSS commands.

See Operating Information: OMC-R System Administration (68P02901W19) for further details
of these environment variables, how to use them, and how to manage log files.

Online Configuration Management setup

This section describes how to set up online CM for one or more OMC-Rs.

For a single OMC-R

Use the following procedure when there is one OMC-R:

Procedure 1-3 Online CM set up for single OMC-R

1

Each user should have access to an OMC-R GUI. Command partitioning

should have been set up for each user.

Edit the file /usr/omc/config/global/AUTOINIT.CNFG and ensure it

contains all the windows that are required at GUI start-up.

Placing an AUTOINIT.CNFG in the home account allows the

users to customize what appears at start-up. Refer to OMC-R
Online Help, Network Operations for further details on configuring
AUTOINIT.CNFG.

Set up periodic audits and turn on CM logging.

NOTE
If the GUI is not available (for example on a remote site
where the overhead is not economic), rlogin to the SITE
using the command:
RLstart <NE_name>

68P02901W17-T

1-9
Jan 2010

Interrogating the network using the COP GLU tool

Chapter 1: Configuration Management General Information

Multiple OMC-R
Use the following procedure when there are multiple OMC-Rs:

Procedure 1-4 Online CM set up for multiple OMC-Rs

1

Configure each operator workstation with a CDE window per OMC-R,

and name appropriately.

Set up the CDE pull-across windows to start GUIs for the different
OMC-Rs.

Set up the CDE pull-across windows to allow access to the database

utilities of each OMC-R.

Install the utilities available on CD ROM aid some CM operations (such

as Adding Neighbors across MIBs) in a multi-OMC-R environment.
Refer to the Software Release Notes supplied with the software for
further details.

Interrogating the network using the COP GLU tool

Motorola recommends using the COP Generic Lookup Utility (GLU) tool to interrogate an
existing network. GLU is an optional tool, available from Motorola, capable of extracting
configuration information on hardware version/serial number/FRU. For full details about COP
and GLU, see System Information: Cell Optimization (COP) (68P02900W90). Other methods for
interrogating the network, include using Detailed Views and cmutil.

1-10

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Management Information Base (MIB)

Management Information Base (MIB)

Definition of the MIB

The Management Information Base (MIB) is the set of network and map configuration data
stored in a database. It contains all the necessary network configuration information required
to check the devices contained in the network, how they are configured, and the settings of
the parameters.

Initializing the MIB

The MIB database is initialized as follows:

Procedure 1-5

Initializing the MIB database

Populate the OMC-R MIB database with enough information to allow it

to communicate with each Network Element. In practice, this means
that the Network, OMC-R, BSS, RXCDR, and MSC objects must be
created in the MIB database.

The OMC-R reads in information from the BSS about its associated
BTS sites, links, cells, and cell parameter data. This information is
retrieved using the audit process. The audit can be configured so
that any differences detected between the OMC-R and the BSS are
automatically applied to the MIB database.

Backing up MIB configuration data

Regularly back up the MIB database. See Operating Information: OMC-R System Administration
(68P02901W19) for further details.

68P02901W17-T

1-11
Jan 2010

Containment

Chapter 1: Configuration Management General Information

Containment
The data stored in the MIB database has a hierarchical structure; the relationship of which is
reflected in the Configuration Management Navigation Tree (see Figure 1-1). The relationship
between two objects is known as a parent-child, or a containment relationship.

Figure 1-1 CM Navigation Tree showing containment relationship

Map

Network
MapNode

MapLink

BSS

RXCDR CommsLink

MSC

OMC-R

SGSN

SWInventory
DYNETGroup

Assoc_RXCDRs/
Assoc_BSSs

NESoftware

PCU
(BSS only)

SITE

SoftwareLoad

Dynet
XBL

Conn_link

Software
Functions

Hardware
Devices

LCF

Logical
Links

OMF

CBL

MTL

OML

LMTL

Radio
Frequency

PATH

RSL

RTFGroup

RTF

Cabinet

Cage

Processors

EAS

COMB

KSWpair

DHP

GPROC

FreqHopSys

GCLK

IAS

LAN

KSW

BSP/
BTP

TDM

DRIGroup

CELL

DRI

MSI

MMS

CSFP

SMSCBmsg

UtranNbr

Neighbour

BlindSrchNbr

TestNeighbour

Handover*/
Power
Control**

TRX

* The Handover Control Objects are:

RelTimAdvHC, RxlevDlHC, RxlevUlHC, RxqualDlHC, RxqualUlHC, SurrndCellHC
** The Power Control Objects are :
RxlevDlPC, RxlevUlPC, RxqualDlPC, RxqualUlPC
ti-GSM-CM Navigation Tree showing containment relationship-00772-ai-sw

See Hierarchy of devices and functions on page 9-29 for further details.

1-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Containment rules

Containment rules
Some of the rules that apply to the containment of objects are as follows:

Network object

There can be only one network instance.

OMC-R objects

The maximum number of OMC-Rs is 51 (0 to 50).

Each active OMC-R contains one SWInventory and each SWInventory can contain n
Software Loads.

In the network, only one active OMC-R is allowed.

GUI sessions

The maximum number of simultaneous GUI sessions supported per OMC-R is 60 (provided
the appropriate number and size of GUI servers are available). This includes 60 MMI
processes, one started by each GUI.

Only five GUI sessions can start in parallel across all connected GUI server platforms. If
more than five sessions are started at the same time, then the additional sessions wait for
the other sessions to complete initialization before commencing their own initialization.

The maximum number of GUI Clients that can be started on the SunBlade 150 server is 12.
If more than 12 are started an error message is displayed.

The maximum number of MSCs allowed is 101 (0 to 100).

MSCs

BSS/RXCDR

On a SunFire 4800, SunFire 4900 and SunBlade 150, the OMC-R supports a maximum
of 254 RXCDRs, or 254 BSSs. (On a SunFire 4800, SunFire 4900 and SunBlade 150, the
OMC-R supports a maximum of 254 combined BSSs and RXCDRs).

A BSS node can contain up to 100 sites.

An RXCDR node contains one site (SITE 0).

A BSS can support up to three PCUs (for GPRS).

A BSS can support up to three NSEIs, one per PCU. The NSEIs must be unique.

Each BSS and RXCDR contains one NESoftware object, which identifies software loads.

68P02901W17-T

1-13
Jan 2010

MIB locking

Chapter 1: Configuration Management General Information

BSC and BTSs

A BSC can support up to 96 MSI to MSI connections.

A BSC can support up to 96 MSI to XCDR connections.

A BSC SITE can contain up to 175 (0 to 174) MSIs and XCDRs.

Up to ten RXCDRs can be connected to each BSC, and ten BSCs can be connected to
each RXCDR.

A BTS SITE can contain up to 10 (0 to 9) MSIs and XCDRs.

A BTS can contain up to 24 cells.

A site can contain one CSFP.

An MSI can contain up to six MMSs depending on the cabinet type.

Each XCDR contains one MMS.

A cell can contain up to 64 GSM Neighbor cells.

A cell can contain up to 16 UTRAN Neighbor cells.

A cell can contain up to 31 GSM Neighbor cells when the cell contains one or more
UTRAN Neighbors.

A cell can contain up to four Handover Control objects, four Power Control objects and
one InterferAlg.

MSI

XCDR

Cells

MIB locking

MIB locking is an intelligent locking scheme which allows applications to run simultaneously if
they meet certain criteria.

NOTE
Regardless of the introduction of MIB Locking, only one network expansion operation
can be run at a time (except for Path Configure). See Chapter 11 Network Expansion
for further details.

1-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

MIB locking

Types of locking
Instead of locking the entire MIB, it is possible to specify that only specific network elements
(BSS/RXCDR) are locked. In this way, multiple operations can run in parallel if they do not use
the same BSS(s)/RXCDR(s) and contained devices. The following is an overview of the types of
locks which are configurable per application type:

Intelligent Locking - allows the OMC-R to identify and lock only the BSS(s)/RXCDR(s)
that are affected by a particular operation for the duration of the operation. However, in
the case of an Audit Gather for a Network or multiple NEs, a lock is released when the
application has finished with an NE rather than waiting until the entire operation has
finished. If there is a Resync operation, intelligent locking takes the form of no locking.
This is because Resync only affects state and MO locks can be broken to update the state
without affecting an audit or other CM operation.

Global Locking puts a lock on the entire network for the duration of the operation. This is
supported purely for backward compatibility.

mib_locks.cfg file
The lock configuration for each application can be defined and stored in the
/usr/omc/config/global/mib_locks.cfg file.
The /usr/omc/config/global/mib_locks.cfg file is copied over from one OMC release to the
next to maintain the customer lock configuration.

Recommended settings for the mib_locks.cfg file

The following default configurations are recommended for the /usr/omc/config/global/
mib_locks.cfg file:

Audit Gather = Intelligent.

Audit Apply = Intelligent.

Cell Prop = Intelligent.

Resync = Intelligent.

NetEx = Intelligent.

CellEx = Intelligent.

Bay Level Cal = Intelligent.

Cmutil = Intelligent.

OLM = Intelligent.

Proxy Cell = Intelligent.

CleanMib always uses global locking.

68P02901W17-T

1-15
Jan 2010

MIB locking

Chapter 1: Configuration Management General Information

Lock files
Lock files are created for the Audit, Resync, CMutil, NetEx, CellEx, Cell Propagation, Bay Level
Calibration, OLM and Proxy Cell Import/Export applications, and are stored in the directory:
/usr/omc/config/global/locks.
The OMC-R removes all lock files from /usr/omc/config/global/locks on startup of the OMC.
The name of a lock file depends on the type of locking specified:

A lock file with a name in the format <BSS/RXCDR OID> is created when Intelligent
Locking has been specified. Where BSS/RXCDR OID is a unique numerical identifier for
each device instance. An Audit Gather lock file name has the format <BSS/RXCDR OID
AUDIT_TAG>, where AUDIT_TAG is AG to indicate an Audit Gather lock file. For example,
28034-131072-1120583512-AG.

A file called ALL-GLOBAL is created for Global Locking.

A file called ALL-INTELLIGENT-NETWORK is created when Intelligent Locking is

configured for an application and where the operation affects the entire network. For
example, Cell-X-export for a network, Cell-X-import for a network, CMutil network
operation, CMutil type extraction, Proxy Cell Export, and Network Realignment on the
OLM. It is also applicable when the Verify NE and Save NE Database options are initiated
through the OLM Operations menu option when the Network icon on the Navigation
Tree has been selected.

The OMC-R does not lock the MIB for an operator-initiated neighbor propagation procedure
from a Cell or RTF Detailed View.

LOCK_LOGGING option
The LOCK_LOGGING option determines the type of logging that occurs for the MIB Locking
feature. If set to 0 (Off), limited locking data is logged to the omcauditlog files, that is, the
logged information just indicates the creation and deletion of a lock for an NE. If set to 1 (On),
then extra locking information is logged in the omcauditlog files. It consists of the location of
the lock file, the name of the lock file and the lock file contents, for example:
2004-04-16 16:29:02 gui: Lock File : /usr/omc/config/global/locks/28034
-131089- 1080813742
2004-04-16 16:29:02 gui : Populating File with the following info 2004-04-16 16:29:02 gui : Ne Name : BSS1011
2004-04-16 16:29:02 gui : Process Name : Path Configure
2004-04-16 16:29:02 gui : Process ID : 11041
2004-04-16 16:29:02 gui : User Name : alynch010
2004-04-16 16:29:02 gui : IP Address : 10.131.2.192
2004-04-16 16:29:02 gui : Host Name : liath192
The default is 0 (Off). The LOCK_LOGGING option is contained in the /usr/omc/config/global/mib_locks.cfg configuration file.

1-16

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

MIB locking

Examples of the MIB locking strategy in operation

Example 1: Intelligent Locking set
The following procedure illustrates how the MIB locking strategy is used for the Audit Gather
operation on a BSS/RXCDR when Intelligent Locking (recommended setting) is set:

Procedure 1-6 Example 1: Audit Gather operation when Intelligent Locking is set

68P02901W17-T

The operator selects the BSS(s)/RXCDR(s) to Audit from either the

Navigation Tree, BSS/RXCDR Detailed View, Map, or LM applications.

The operator selects the Audit option from the Config Mgt Menu.

The OMC-R checks the /usr/omc/config/global/mib_locks.cfg file

where Intelligent Locking has been set for Audit Gather operations.

For each BSS/RXCDR to be audited, the OMC-R creates a lock

file. The lock file name has the format: <BSS/RXCDR OID AG>
where AG signifies the Audit Gather operation, and can be found in
/usr/omc/config/global/locks. Each file contains the NE name, the
process name, the PID, user ID of the person initiating the operation,
and the IP address of the machine on which the operation is running.

For each BSS/RXCDR locked in Step 4, the system logs the following
information to the omcauditlogs:
YYYY-MM-DD HH:MM:SS au : Audit Gather locking <BSS/RXCDR
Name> : <UserId> (PID)
For each BSS/RXCDR locked by the Audit Gather, steps 6 to 8 and
then performed.

The system determines a list of audit inconsistencies for the

BSS/RXCDR.

The system removes the lock file created in Step 4 for that BSS/RXCDR.

The system logs the following information in the omcauditlogs for the
released lock:
YYYY-MM-DD HH:MM:SS au : Audit Gather releasing <BSS/RXCDR
Name> : <UserId> (PID)

The system verifies that all BSS(s)/RXCDR(s) selected in Step 1 have

been audited.

1-17
Jan 2010

MIB locking

Chapter 1: Configuration Management General Information

Example 2: Global Locking set

The following procedure illustrates how the MIB locking strategy is used for the Audit Gather
operation on a BSS/RXCDR when Global Locking is set:

Procedure 1-7 Example 2: Audit Gather operation when Global Locking is set
1

The operator selects the BSS(s)/RXCDR(s) to Audit from either the

Navigation Tree, BSS/RXCDR Detailed View, Map, or LM applications.

The operator selects the Audit option from the Config Mgt menu.

The OMC-R checks the /usr/omc/config/global/mib_locks.cfg file

where Global Locking has been set for Audit Gather operations.

The system creates a lock file called ALL-GLOBAL in

/usr/omc/config/global/locks which contains the process name, the
PID, user ID of the person initiating the operation, and the IP address
of the machine on which the operation is running.

The system logs the following information to the omcauditlogs:

YYYY-MM-DD HH:MM:SS au : Audit Gather locking ALL-GLOBAL:
<user id> (PID)

The system determines a list of audit inconsistencies for the selected

BSS(s)/RXCDR(s).

The system removes the lock file created in Step 4.

The system logs the following information to the omcauditlogs:

YYYY-MM-DD HH:MM:SS au : Audit Gather releasing ALL-GLOBAL:
<user id>(PID)

Lock error messages

If the OMC-R is unable to lock a network object, the OMC-R logs the information to the
omcauditlogs. For example, if the OMC-R could not lock an NE during an Audit Gather
operation, the following message is logged to the omcauditlogs:
YYYY-MM-DD HH:MM:SS au : Audit Gather unable to lock <NE Name> due to the
existence of one or more locks. Run utility /usr/omc/current/sbin/LockUtility
to list the NE(s) on which a lock exists.

LockUtility
To view the locks that currently exist, run the LockUtility found in: /usr/omc/current/sbin/.
LockUtility displays the following information for each lock found in /usr/omc/config/global/locks:

1-18

Id.

BSS/RXCDR Name.

Application Type.

PID.
68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Lock Type.

Time.

User.

MIB locking

The omcadmin can either Remove Lock, Remove All Locks, or Exit. If a lock is removed, the
following information is logged to the omcauditlogs:
YYYY-MM-DD HH:MM:SS: Lock Utility releasing <BSS/RXCDR Name> :

<UserId> (PID)

checkValidLockPID utility
To ensure that locks do not exist for processes that have died, the checkValidLockPID utility can
be deployed. Set up a cronjob on every GUI server and the SPLAT to run the checkValidLockPID
utility every 15 minutes.
The checkValidLockPID utility checks for lock files in /usr/omc/config/global/locks containing
the same IP address as the machine on which it is running. For each lock file with the same IP
address, checkValidLockPID verifies that the PID associated with the lock file is still alive and
running. If it is not alive and running, checkValidLockPID removes the associated lock file.

Limiting the number of parallel CM operations

The MAX_CM_OPS and MAX_CMUTIL_OPS system parameters are defined in the
/usr/omc/config/global/mib_locks.cfg file on the system processor. It is not necessary
to perform an OMC Stop/Start when these parameters are modified. The parameters are
maintained on a point release cutover.

MAX_CM_OPS
The MAX_CM_OPS parameter defines the maximum number of locked NEs, above which no
new configuration management operations that require a lock on an NE can be started.

NOTE
Audit Gathers are not included in the MAX_CM_OPS count.

68P02901W17-T

1-19
Jan 2010

MIB locking

Chapter 1: Configuration Management General Information

Minimum, Maximum, and Default Values

The MAX_CM_OPS minimum, maximum, and default values are listed in Table 1-4:

Table 1-4 MAX_CM_OPS Minimum, maximum, and default Values

MAX_CM_OPS
MINIMUM

MAX_CM_OPS
MAXIMUM

MAX_CM_OPS
DEFAULT

120 k TCH

17

12

All other platforms

Off Line MIB on any

DataGen supported system
specifications

System TCH Capacity

NOTE
The MAX_CM_OPS system parameter cannot be set to values outside the ranges
specified in Table 1-4 for the different TCH capacity systems.

Starting a new configuration management operation

Before starting a new configuration management operation, the system performs the following:

Counts the number of NE lock files on the system (not including Audit Gathers).

Compares the number of configuration management operations currently running to the

system parameter (MAX_CM_OPS).

If the number of NE lock files is less than MAX_CM_OPS, the new configuration management
operation starts.
Example 1:
If the value of MAX_CM_OPS is set to 5 and the following configuration management operations
(that is, five NE lock files) are currently running:
Path configure.
Delete site with no neighbors.
CellEx Export with no neighbors.
CellEx Import with no neighbors.
CMutil extract BSS.
Another new configuration management operation would not be allowed to start.

1-20

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

MIB locking

Example 2:
If the value of MAX_CM_OPS is set to 5 and the following configuration management operations
are currently running:
Path configure.
Delete site with no neighbors.
CellEx Export with no neighbors.
Audit Gather.
Audit Gather.
Audit Gather.
CMutil extract BSS.
Because there are four configuration management operations running (four NE lock files), a
new configuration management operation would be allowed to start as Audit Gathers are not
included.

MAX_CMUTIL_OPS
The MAX_CMUTIL_OPS parameter defines the maximum number of Cmutil operations allowed
in parallel.

Minimum, Maximum, and Default Values

The MAX_CMUTIL_OPS minimum, maximum, and default values are listed in Table 1-5.

Table 1-5 MAX_CMUTIL_OPS minimum, maximum, and default values

MAX_CMUTIL_OPS
minimum

MAX_CMUTIL_OPS
maximum

MAX_CMUTIL_OPS
default

120 K TCH

All other platforms

Off Line MIB on any

DataGen supported system
specifications

System TCH

NOTE

68P02901W17-T

The MAX_CMUTIL_OPS system parameters cannot be set to values outside the

ranges specified in Table 1-5 for the different TCH capacity systems.

Cmutil operations are counted as part of the MAX_CM_OPS total.

A HierDelete operation is classified as ONE cmutil operation. This Cmutil

operation is part of the MAX_CMUTIL_OPS total.

1-21
Jan 2010

MIB locking

Chapter 1: Configuration Management General Information

Starting a new Cmutil operation

Example 1:
If the number of Cmutil operations currently running is less than MAX_CMUTIL_OPS, and the
total number of NEs locked is less than MAX_CM_OPS, the new Cmutil operation is started.
If the value of MAX_CM_OPS is set to 5, MAX_CMUTIL_OPS is set to 2 and the following
configuration management operations are currently running:
Path configure
Delete site with no neighbors
CellEx Export with no neighbors
HierDelete BSS
CMutil extract BSS
Because there are four configuration management operations running (four NE lock files), and
one CMutil operation (one NE lock file), another new Cmutil operation would not be allowed to
start.
Example 2:
If the value of MAX_CM_OPS is set to 5, MAX_CMUTIL_OPS is set to 2 and the following
configuration management operations are currently running:
Path configure.
Delete site with no neighbors.
CellEx Export with no neighbors.
Audit Gather.
Audit Gather.
Audit Gather.
CMutil extract BSS.
Because there are three configuration management operations running (three NE lock files),
and one CMutil operation running (one lock file), a new CMutil operation would be allowed
to start as Audit Gathers are not included.

1-22

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Definition of a Network Element (NE)

Definition of a Network Element (NE)

Types of Network Element

There are two types of Network Element (NE):

Base Station System (BSS).

Remote Transcoder (RXCDR).

Base Station System (BSS)

A Base Station System (BSS) is the system between the Mobile Switching Centre (MSC) and
the Mobile Stations (MSs).
This system requires Base Station Controller (BSC) and Base Transceiver Station (BTS)
functions and can include a local transcoding function. The BSS consists of one or more of
the following sites:

BSC site.
This is a BSS with all BTS functions at remote locations. This BSC provides the interface
between the MSC and the remote BTS sites.

Remote BTS site.

These sites provide the interface between the BSC and the MSC or MSs, performing
the base transceiver functions.

BSS site with local transcoding.

Local transcoding can be included at any type of site except BTS.

NOTE
Transcoding can be included at any type of site except a BTS.

RXCDR
Transcoding is the digital signal processing required to interface between the MSC 64 kbit/s
circuits and the MS air interface 13 kbit/s circuits. Transcoding is a BSS function that can be
performed at a BSC and/or remote BTS sites. A Remote Transcoder (RXCDR), typically located
at the MSC, provides transcoding for multiple BSSs.

68P02901W17-T

1-23
Jan 2010

Uploading an NE database to the OMC-R

Chapter 1: Configuration Management General Information

Uploading an NE database to the OMC-R

BSS and RXCDR databases

The Base Station Controller (BSC) holds the master copy of the database for the BSS, known
as the BSS database. The BSS database can be downloaded to a BTS when required. The
master copy of the BSS database can be manually uploaded to the OMC-R when necessary. For
example, it may be necessary to upload the BSS database to the OMC-R to preserve the most
recent changes in the event of a power loss or similar event at the BSS/RXCDR node. Likewise,
the RXCDR holds an RXCDR database, which can be uploaded to the OMC-R database, when
required.

When to upload an NE database

Upload the NE database after any of the following events has occurred:

A new database has been downloaded to the site since the last upload.

One or more MMI commands have been performed on the site either locally or from the
OMC-R.

A week has elapsed since the last upload from the BSC.

NOTE
If any changes are made to the BSS database, using BSS commands or Detailed
Views, upload the BSS database to the OMC-R.

Uploading the NE database to the OMC-R

Use the following procedure to upload the NE database to the OMC-R:

Procedure 1-8

Upload NE database to the OMC-R

From the Front Panel, select the Config Mgt icon to display the
Navigation Tree.

For each affected BSS NE, open the Detailed View by either double
clicking the required NE, or by selecting Edit Detailed View from
the menu bar.

Select Options NESoftware to open the NESoftware window.

Continued

1-24

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Procedure 1-8

Uploading the NE database to the OMC-R

Upload NE database to the OMC-R (Continued)

Select Load Mgt Upload Object to open the Upload box.

Select Database in the Object Type field.

Click OK to initiate an upload of the NE database so that the database

has the recent cell id and neighbor updates.
An information box is displayed with the following message:
Upload Operation Started...

Click OK. The information box closes.

In the NESoftware window, select File Close from the menu bar.

Use the following procedure to monitor the upload status during the upload process:

Procedure 1-9

68P02901W17-T

Monitor upload process

Select the Load Mgt icon from the Front Panel. the Load Mgt Options
window is displayed.

Select the Upload Status option on the Upload window to display the
Upload Status window.

Monitor the status of the upload in the Upload Status window.

When the upload is complete, close the Upload Status window.

Repeat Procedure 1-8 and Procedure 1-9 for all affected BSS NEs.

1-25
Jan 2010

Configuring network objects using the OMC-R GUI

Chapter 1: Configuration Management General Information

Configuring network objects using the OMC-R GUI

Introduction to creating, editing, and deleting network objects

Network objects can be created using any of the following methods:

OMC-R GUI Navigation Tree.

Remote login and the TTY interface, see Remotely logging in to a BSS site from the OMC-R
on page 1-39.

cmutil, see Chapter 15 cmutil.

This section provides a general procedure for creating, modifying, and deleting network objects
using the OMC-R GUI Navigation Tree and Detailed View forms.

Activities available in Navigation Tree

The OMC-R GUI Navigation Tree can be used to:

Create network objects.

Display details of network objects.

Modify network objects.

Delete network objects.

Other activities initiated from the Navigation Tree are detailed in OMC-R Online Help, Network
Operations.
Network objects are created and modified using Detailed View forms.

Selecting regions using the Navigation Tree

If the geographic command partitioning and region support feature is in operation, it may
also be necessary for a user to select the appropriate region before creating or managing a
network object.
Select the required region name from the list displayed above the panner window in the
Navigation Tree. The selected region and its network elements are then displayed in the
Navigation Tree. See OMC-R Online Help, Network Operations for further details of geographic
command partitioning and region support feature.

1-26

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

User access to OMC-R GUI functions

User access to OMC-R GUI functions

A user can only create/modify/delete network objects if the system administrator has allocated
the user to specific command partitioning areas. If a user does not have access to certain
functions, the menu options are grayed-out and cannot be selected. OMC-R Online Help,
Network Operations describes how command partitioning and user access privileges are set up.

Related topics
The following sections describe related topics:

Navigating to a network object class or instance on page 1-28.

Using Detailed Views on page 1-30.

Creating a network object using the OMC-R GUI on page 1-32.

Modifying a network object using the OMC-R GUI on page 1-34.

Deleting a network object using the OMC-R GUI on page 1-37.

68P02901W17-T

1-27
Jan 2010

Navigating to a network object class or instance

Chapter 1: Configuration Management General Information

Navigating to a network object class or instance

Network object class and network object instance buttons

Network objects are divided into classes in the Navigation Tree, for example, BSS, SITE,
Processors, Logical Links, Cage, and so on. A button in the Navigation Tree represents each
class.
Network object instances are actual network objects and have their own Detailed View.
To display a network object instance, click the folder button next to the network object class
button. If network object instances have been created, they are displayed in the Navigation Tree.

Introduction to using the Navigation Tree

To create a network object instance using the OMC-R GUI, the network object class must be
visible in the Navigation Tree. To modify, display or delete a network object instance the network
object instance must be visible in the Navigation Tree. Open the branches of the Navigation
Tree to make these objects visible. This action is referred to as navigating to a network object.

Navigating to the network object

Use the following procedure to navigate to a network object:

Procedure 1-10 Navigate to network object

1-28

From the Front Panel, click the Config Mgt icon to display the
Navigation Tree.

Click the folder icon buttons next to the network object class and
network object instance buttons to open the Navigation Tree levels
until the network class button required in visible. See Figure 1-1
for information about network object containment. If necessary, see
OMC-R Online Help, Network Operations for further details of how to
use the Navigation Tree.

Click the folder icon button next to network object class button. If any
network object instances have been created, the OMC-R displays them.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Representation of a navigation route to a network object

Representation of a navigation route to a network object

In this manual, the navigation route to a network object is represented in parentheses and
shows the type and instance buttons which have to be selected to display the destination
network object button or network object type button. For example, the following shows the
navigation route to a BTP instance:
(Network - BSS - BSS instance -Site - Site instance (BTS only) - Hardware Devices - Processors BTP - BTP instance).
Double clicking a BTP instance button would display the BTP Detailed View.

Closing the Navigation Tree

Close the Navigation Tree window by selecting File Close from the Navigation Tree menu bar.

Using the FIND option to locate a network object

To find a network object (such as a BSS, site, PCU or cell) quickly, use the Find icon on the Front
Panel, or select Find from the Navigation Tree. The Find function displays a Navigation Tree
starting at the network object defined in the Find criteria. See OMC-R Online Help, Network
Operations for further details.

68P02901W17-T

1-29
Jan 2010

Using Detailed Views

Chapter 1: Configuration Management General Information

Using Detailed Views

Description of Detailed Views

A Detailed View form contains fields representing specific parameters for a network object.
Detailed View forms can be displayed for most network objects, for example, for all NEs, sites,
cells, and most devices, functions and links.
Detailed Views provide a user-friendly method of defining network object parameters.
Alternatively, network object parameters can be defined and modified by remotely logging in to
a BSS, and then using the TTY interface and MMI BSS commands. Refer to Remotely logging in
to a BSS site from the OMC-R on page 1-39.
The appropriate sections of this manual list and provide a brief description of the fields in
each Detailed View. For each Detailed View description, the following information is provided,
where possible:

OMC-R GUI field name. Where pertinent, the BSS database parameter name is also shown.
If the OMC-R database parameter name is different from the BSS database parameter
name, then the OMC-R database parameter name is also shown. The BSS parameter
names are always used in TTY interface commands.

Brief description of the field.

Valid values that can be entered for the field.

If the field is Mandatory or Optional, which indicates whether the field requires a value
when creating an instance of the class.

Displaying Detailed Views with BSS or OMC-R names

Fields in the OMC-R GUI Detailed View forms can be displayed as:

A plain English description - known as the OMC-R Naming. When space is limited, field
names are shown in an abbreviated form.

BSS and OMC-R database parameter name - known as the BSS Naming.

For example, the BTS Power Control Acknowledgment field in the CELL Detailed View form can
be displayed as bts_p_con_ack, which is the name of the parameter in the BSS and OMC-R
database. (An OMC-R attribute is also referred to as a parameter.)

NOTE
Some parameters can have slightly different names in the OMC-R and BSS databases.

1-30

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying Detailed Views with BSS or OMC-R names

Changing naming for all Detailed Views

If necessary, BSS parameter names can always be displayed in Detailed Views by setting the
environment variable: BSS_NAMING. By default, BSS_NAMING is not set (meaning that
OMC-R parameter names are displayed by default in Detailed Views). Set BSS_NAMING
before starting the GUI, otherwise the GUI needs to be stopped and then restarted in order for
the variable to take effect.
To set BSS_NAMING, type the following line in the file mmiProcConfig.csh, which can be
found in /usr/omc/config/global/env:
setenv BSS_NAMING
To unset BSS_NAMING, comment-out, or delete the variable in the mmiProcConfig.csh file.
Environment variables are detailed in Operating Information: OMC-R System Administration
(68P02901W19).

Changing naming for a single Detailed View

To switch between the OMC-R and BSS naming conventions in a Detailed View, select View
OMC Naming, or View BSS Naming from the Detailed View menu bar.

68P02901W17-T

1-31
Jan 2010

Creating a network object using the OMC-R GUI

Chapter 1: Configuration Management General Information

Creating a network object using the OMC-R GUI

Overview of creating a network object using the Navigation

Tree
Creating a network object using the Navigation Tree involves:
1.

Creating a Detailed View for the required network object.

2.

Defining the Detailed View parameter fields for the network object.

3.

Saving the information and closing the Detailed View.

4.

Unlock the device to bring it into service. (This step is not required when creating a
Network instance.)

Creating the Detailed View for the network object

Use the following procedure to create a Detailed View for the network object:

Procedure 1-11 Create Detailed View for network object

1-32

Navigate to and select the network object class button in the

Navigation Tree. If necessary, see Navigating to a network object class
or instance on page 1-28 for further details. The network object class
button changes color.

Select Edit Create from the Navigation Tree menu bar. The OMC-R
displays the Detailed View for the network object in Create mode.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Defining the parameter fields for the network object

Defining the parameter fields for the network object

Use the following procedure to define the required parameter settings for the network object:

Procedure 1-12 Define parameter fields for network object

1

Create the Detailed View for the network object.

Complete the mandatory and optional fields in the Detailed View, as

required. All the mandatory fields must be completed before a network
object can be created. See the appropriate sections in this manual for
details of specific Detailed View fields.

Use the scroll bar on the right-hand side of the window to scroll all the
way to the top and bottom of the window to ensure that all the fields
in the Detailed View have been completed. The proportion of window
which is invisible depends on the physical size of the window displayed.

Saving information and closing the Detailed View

When all the fields have been completed as required in the Detailed View, use the following
procedure to create the network object and close the Detailed View:

Procedure 1-13 Saving and closing Detailed View

68P02901W17-T

Select File Create from the menu bar.

The create process is documented in the status bar. Any errors
occurring are also displayed in this area.
If the create is not successful, use this information to help remove
possible errors from the Detailed View.
If successful, the network object is created and is visible in the
Navigation Tree.

Select File Close from the menu bar to close the Detailed View
window.
If you chose not to create or save the information in the Detailed
View, the OMC-R displays a confirmation window, asking whether the
changes are to be discarded or saved. Reply as required.

1-33
Jan 2010

Modifying a network object using the OMC-R GUI

Chapter 1: Configuration Management General Information

Modifying a network object using the OMC-R GUI

Introduction to modifying a network object using the

Navigation Tree
The parameters for a network object may have to be modified from time to time, perhaps as
a result of reconfiguring the network. To modify a network object, edit the Detailed View for
the object.
When editing a Detailed View, the modified parameters are propagated to the BSS and, if
acceptable, are sent back for storage in the MIB database.

Non-editable fields in Detailed Views

A user cannot change some fields in a Detailed View (read-only) for the following reasons:

The OMC-R generates the information in the field, for example, the current status of a
network object.

The information in the field can only be entered when the object is created, that is, when
the Detailed View is in Create mode. When the Detailed View is in Monitor or Edit mode
some fields can no longer be modified.

Displaying and modifying a Detailed View

Before a Detailed View form can be modified, it must have been created and saved as part of
the current network.
To display and edit a Detailed View, use the following procedure:

Procedure 1-14 Display and edit a Detailed View

1

Navigate to and select the network object instance button in the

Navigation Tree. If necessary, see Navigating to a network object
class or instance on page 1-28 for further details. The network object
instance button changes color.
Alternatively, use the Find icon on the Front Panel to locate a network
object, see OMC-R Online Help, Network Operations for further details.

Select Edit Detailed View from the menu bar. The OMC-R displays
the Detailed View in Monitor mode. Alternatively, double-click the
network object instance button to display the Detailed View form.
Continued

1-34

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying and modifying a Detailed View

Procedure 1-14 Display and edit a Detailed View (Continued)

3

To modify fields, select Edit Edit from the menu bar.

The Detailed View changes from Monitor to Edit mode. It is only
possible to change fields in the Detailed View when it is in Edit mode.
Figure 1-2 shows an example of a Detailed View in Edit mode.

Move to the field to be changed using the mouse, arrow keys, or TAB
key.
The scroll bar at the right of the window can also be used when the
Detailed View has many fields extending over several pages. Details of
individual Detailed View fields are described in the relevant sections
of this manual.

Click the required field.

The field information can be changed using the arrow and Backspace
keys.
Where an entry with a list of options is to be changed:
1.

Open the option list by pointing at the current selection and

holding down the left mouse button.

2.

Keeping the button depressed, use the mouse to scroll up or down

through the available options.

3.

When the required option has been highlighted, release the

mouse button. The new selection replaces the previous selection.

Saving the information

Use the following procedure to save the information:

Procedure 1-15 Save information in Detailed View

1

Select File Save from the menu bar to save the changes.
Alternatively, to return all changed fields to the state they were in
before editing took place, select File Revert.

NOTE
It is impossible to revert to a previous version after an edited
version has been saved.
2

68P02901W17-T

Close the Detailed View by selecting File Close from the menu bar.

1-35
Jan 2010

Displaying and modifying a Detailed View

Chapter 1: Configuration Management General Information

Figure 1-2 Example of a Detailed View in Edit mode

ti-GSM-ExampleofaDetailedViewinEditmode-00773-ai-sw

1-36

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a network object using the OMC-R GUI

Deleting a network object using the OMC-R GUI

Methods of deleting a network object

A network object can be deleted from either the:

Navigation Tree.

Detailed View.

Prerequisites for deleting network objects

Before a network object can be deleted, child objects should be deleted and the network object
should be locked.

Deleting a network object from the Navigation Tree

Use the following procedure to delete a network object using the Navigation Tree:

Procedure 1-16 Delete network object using Navigation Tree

1

Navigate to and select the network object instance button in the

Navigation Tree. If necessary, see Navigating to a network object class
or instance on page 1-28 for further details.
The network object class button changes color.

Select Edit Detailed View Delete from the menu bar.

The OMC-R displays a deletion confirmation window.

To cancel the deletion, click Cancel.

The confirmation window closes and the OMC-R displays the
Navigation Tree.

To confirm the deletion, click OK.

The deletion process is documented in the status bar. When completed,
the message: Delete Complete is displayed. After a few seconds, the
OMC-R deletes the network object from the Navigation Tree.

Select File Close from the menu bar to close the Navigation Tree
window.

NOTE
In the instance of deleting a BCCH RTF, the deletion confirmation window displays
a further option to allow the incoming neighbors to be exported. This is further
described in Exporting incoming neighbors on deletion of BCCH RTFs on page 9-195.

68P02901W17-T

1-37
Jan 2010

Deleting a network object from a Detailed View

Chapter 1: Configuration Management General Information

Deleting a network object from a Detailed View

Use the following procedure to delete a network object using the Detailed Views:

Procedure 1-17 Delete network object from Detailed View

1

Display the Detailed View for the network object to be deleted.

Select Edit Edit from the menu bar to enter Edit mode.

Select File Delete from the menu bar.

The OMC-R displays a deletion confirmation window.

Either click OK to confirm the deletion, or click Cancel to cancel the

deletion.
The confirmation window closes and the OMC-R displays the
Navigation Tree.
The deletion process is documented in the status bar. When completed,
the message:
Delete Complete
is displayed. After a few seconds, the OMC-R deletes the network
object from the Navigation Tree.

Select File Close from the menu bar to close the Detailed View.

Select File Close from the menu bar to close the Navigation Tree
window.

NOTE
In the instance of deleting a BCCH RTF, the deletion confirmation window displays
a further option to allow the incoming neighbors to be exported. This is further
described in Exporting incoming neighbors on deletion of BCCH RTFs on page 9-195.

1-38

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Remotely logging in to a BSS site from the OMC-R

Remotely logging in to a BSS site from the OMC-R

Introduction to remote login to a BSS

Once a BSS or RXCDR has been created, it is possible to log in to it from the OMC-R. A user
can then set up and manage the BSS using BSS MMI commands and parameters through the
TTY interface. This is referred to as Remote Login or Rlogin.
Remote login involves:
1.

Logging in to a BSS.

2.

Changing security level, as necessary, according to the commands to be used, see

Changing security level (for TTY interface commands) on page 1-43.

Maximum number of remote login sessions

The maximum number of concurrent remote logins supported by the OMC-R is 90. The default
number of concurrent remote logins supported is 60.
The maximum simultaneous remote login sessions to a single node are defined by the number
of GPROCs available at that node to receive the rlogin requests. For example, two GPROCs
support a maximum of two simultaneous rlogins.

Logging in remotely to a BSS

Use the following procedure to log in remotely to a BSS from the OMC-R:

Procedure 1-18 Remote log in to a BSS

1

Select the Remote Login icon from the Front Panel as shown in
Figure 1-3. The OMC-R displays the RLogin window (see Figure 1-4)
which lists all the current network elements in alphabetical order.

Select the network element required.

Continued

68P02901W17-T

1-39
Jan 2010

Logging in remotely to a BSS

Chapter 1: Configuration Management General Information

Procedure 1-18 Remote log in to a BSS (Continued)

3

Click the TTY button to start a TTY interface session. The OMC-R
displays a window for the site and an MMI prompt.
The BATCH button displays the Batch File Selection window (see
Figure 1-5), which lists the available batch files in the default batch
directory. Use this window to:

Select, view, edit, and run the batch files.

Search for, and manipulate, files in other directories.

Change to security level 2 once logged in, see Changing security level
(for TTY interface commands) on page 1-43.

Use any of the BSS commands mentioned in this manual or detailed in

the Technical Description: BSS Command Reference (68P02901W23).

Figure 1-3 OMC-R front panel

ti-GSM-OMC-Rfrontpanel-00774-ai-sw

1-40

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Logging in remotely to a BSS

Figure 1-4 RLogin window

ti-GSM-Rloginwindow-00775-ai-sw

68P02901W17-T

1-41
Jan 2010

Logging in remotely to a BSS

Chapter 1: Configuration Management General Information

Figure 1-5 Batch File Selection window for a BSS

ti-GSM-BatchFileSelectionwindowforaBSS-00776-ai-sw

1-42

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Changing security level (for TTY interface commands)

Changing security level (for TTY interface commands)

Introduction to changing security levels

System configuration and administration commands, such as those used in equipping devices
and functions, may only be performed in security level 2. Some activities require the user to
log in at security level 3. Technical Description: BSS Command Reference (68P02901W23)
specifies the security level for each command.

Using the TTY interface to change to security level 2

Use the following procedure to change to security level 2 using the TTY interface:

Procedure 1-19 Change security level at TTY interface

1

From the RLogin window (see Figure 1-4), click the TTY button. The
OMC-R displays a window for the site and an MMI prompt.

Type chg_level and press Return.

Enter the password for security level 2 and press Return.

NOTE
step 1 and step 2 can only be done if the password is the
Return character. If the password has been changed, it is
necessary to enter the changed password.

For example, the system displays:

OMC> Login completed successfully
-> chg_level
Enter password for security level you wish to access:...
Current security level is 2
The chg_level command no longer fulfills any function in GSR10. It is supported in GSR10 only
as a dummy command to ensure OMC-R scripts which require this command function correctly.
It does not change the access level for a user as each user has a fixed access level which can
only be changed by an omcadmin user. This command prompts for two passwords and the
output is always:
Current security level is 3.

68P02901W17-T

1-43
Jan 2010

Using the TTY interface to change to security level 2

Chapter 1: Configuration Management General Information

An example of an rlogin script using level two security is provided as follows:

chg_level
<level 2 password>
trace_call cell_number=<gsmcellid>
all
all
no
nth=10
2
200
no
omc
When executed on a GSR10 BSS, this script fails because the chg_level command expects
two passwords to be entered. The solution is to modify the script so that it contains both the
level three passwords instead of the level two password. This ensures that the script executes
correctly on both GSR10 and pre-GSR10 BSS. The same script modified to use level three
passwords is provided as follows:
chg_level
<1st level 3 password>
<2nd level 3 password>
trace_call cell_number=<gsmcellid>
all
all
no
nth=10
2
200
no
omc

1-44

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Remotely logging in to a BSS using WebMMI

Remotely logging in to a BSS using WebMMI

Introduction to WebMMI
WebMMI allows a user to access a BSS from any part of the world through a PC and the network
operator's intranet, providing the PCU is attached to the Ethernet.
For a full technical description of the WebMMI feature, see Technical Description: BSS
Implementation (68P02901W36).
When the connection to the PCU is established a WebMMI GUI is displayed through which a
user can manage the BSS using BSS MMI commands.

WebMMI GUI
The WebMMI GUI acts like a telnet session, where any commands allowed by the MMI or
Executive Monitor (EMON) can be entered (as determined by the current security level).
A user can also perform the following activities using the WebMMI GUI, as required:

Logging - allows the user to store the data entered and displayed in the WebMMI GUI to
a file on the hard drive. The MMI Shell and the EMON Shell can be logged to different
files at the same time.

Script catting - allows the user to load a file from their hard drive and run the contents
at either the MMI Shell or EMON Shell.

Repetitive commands - allows the user to run a single command at the MMI Shell or the
EMON Shell any number of times, at any time required.

Aliasing - provides a GUI interface to the MMI and EMON command alias.

Quick-key aliasing - allows the user to assign commands to keystrokes.

BSS element descriptions - allows the user to display a short description of an element by
typing the element name at the prompt. Element names can also be entered as part of a
command, such as disp_element <element name>. This facility can be switched on/off
from the Preferences menu in the WebMMI GUI.

Pop-up historical commands - allows the user to display a pop-up box listing the commands
previously entered. This facility can be switched on/off from the Preferences menu in
the WebMMI GUI.

68P02901W17-T

1-45
Jan 2010

Prerequisites for WebMMI

Chapter 1: Configuration Management General Information

Prerequisites for WebMMI

At the BSS
Before using WebMMI, ensure that the following requirements are met at the BSS:

PCU is connected to the BSS.

Ethernet cable connects the PCU MPROC to either:

the network operator's intranet,
or a local dial-in server located next to the PCU.
If MPROC redundancy is in use, the Ethernet cable must also be connected to the
redundant MPROC.

At the PC
Before using WebMMI, ensure that the following requirements are met at the PC:

Windows or UNIX operating system is installed suitable for running a web browser.

A web browser, such as Microsoft Internet Explorer Version 4+ or Netscape[Symbol_registersans] Navigator Version 4+ is available on the PC.

Java Runtime Environment version 1.3 (minimum) is available on the PC. If this is not
already installed on the PC, the web browser displays prompts to load it before WebMMI
can run.

Setting up and using WebMMI

To set up WebMMI, complete the following procedures:

1-46

1.

Identify the Internet address details of the PCU to be connected to. If the details have
not been set, enter the appropriate details.

2.

Load the WebMMI applet from the PCU to the PC. Once the applet is loaded at the PC,
the WebMMI GUI appears.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Setting up and using WebMMI

These procedures are detailed as follows.

Identifying the PCU address details

Use the following procedure to identify the PCU Internet address details (perform the steps
only once for a PCU):

Procedure 1-20 Identify PCU Internet address

1

Look up the IP address, Router IP address, and Subnet Mask of the

PCU in the Address Information grouping in the PCU Detailed View,
see Configuring a PCU using the OMC-R GUI on page 6-8.

NOTE
If a dial-in server is used, all the PCUs could have the same
IP address since each PCU would be on its own network with
its dial-in server installed on a PC next to it. Otherwise, if
the PCUs are connected directly to hubs which connect into
the network, each PCU should have its own IP address.
2

If the IP address, Router IP address and Subnet Mask fields have not
been completed, and assuming the PCU device on the BSC is in a
Busy-Unlocked State, enter the appropriate values.
Alternatively, enter the following commands from either a terminal
connected to the BSP TTY port at the BSC, or through a rlogin session
at the OMC-R:
modify_value pcu ip_address <ip address> psp 0
modify_value pcu router_ip_address <router ip address> psp 0
modify_value pcu subnet_mask <subnet mask> psp 0
If the system uses MPROC redundancy, type the following commands:
modify_value 0 ip_address <ip address> pcu 0
modify_value 0 router_ip_address <router ip address> pcu 0
modify_value 0 subnet_mask <subnet mask> pcu 0

At a PC, which has access to the network on which the PCU resides,
enter the following command from a DOS or UNIX prompt to test the
web server: ping <PCU ip address>
The system replies that the site is alive. If the site is not alive, check
the network connections.
If the PCU is connected to a dial-in server, dial-in to the server, log in
to the network remotely, and then proceed.

Loading the WebMMI applet to the PC

Before a PC can use WebMMI, an applet must be uploaded from the PCU to the PC. Perform the
following procedure at the PC (which has access to the network on which the PCU resides).

68P02901W17-T

1-47
Jan 2010

Setting up and using WebMMI

Chapter 1: Configuration Management General Information

Procedure 1-21 Load WebMMI applet to PC

1

Start a web browsing tool (such as, Microsoft Internet Explorer 4+ or

Netscape Navigator 4+).

Go to the following website:

http://<PCU ip address>/index.html
The web page appears and an applet downloads to the PC.
If the PC does not have Java Runtime Environment 1.3+, the web
browser displays prompts to install it. Follow the instructions given by
the web browser. After installing the Java Runtime Environment 1.3+,
exit, and restart the web browser.

Once the applet is downloaded, Java Runtime Environment 1.3+ runs

the applet.
If the .java.policy file does not contain the necessary permissions
(for example, when the PC accesses a new PCU), a window appears
containing the required text. Copy and paste this text into the
.java.policy file. The .java.policy file is located in your home directory
(for example, in Microsoft Windows inprofiles/<username>
directory). If the .java.policy is updated, exit, and restart the web
browser.
Once the permissions are sufficient, the WebMMI GUI appears allowing
the MMI Shell window to be opened. If security level 3 has been
accessed, the EMON Shell window can also be opened.

Using the WebMMI GUI at the PC

Use the following procedure to use the WebMMI GUI at a PC:

Procedure 1-22 Use WebMMI GUI at PC

1

Click the MMI Shell checkbox in the WebMMI GUI window. The
MMIShell window opens. (If security level 3 has been accessed, the
EMON Shell checkbox is also displayed.)

Enter the appropriate BSS MMI commands and parameters to manage

the BSS, as required.

Exiting the WebMMI GUI

To exit the WebMMI GUI at a PC, close the web browser, or go to a different web page (not
WebMMI), or click the EXIT button in the WebMMI GUI window. (To exit a rlogin session in the
EMON Shell, type exit.)

1-48

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Making wide area modifications

Making wide area modifications

Introduction to wide area modifications

Wide area modifications involve making amendments to database elements that are applicable
to all sites, all BTSs, or all cells at a site.

Wide area modifications using the TTY interface

Some BSS commands exist which permit wide area modifications. Some of the commonly
used commands are listed and examples are given of using the commands with the all
parameter. However, it is not sufficient just to issue the command; in some cases, an audit
must be performed to update the OMC-R. The Local Maintenance flag must also be set so
that TTY commands can be issued from the OMC-R (see Recommendations for Configuration
Management on page 1-2 in this chapter for further details).
Full details relating to the prerequisites, limitations of use, and the full syntax for all the
commands detailed in this section are included in: Technical Description: BSS Command
Reference (68P02901W23).

chg_element
When used with the all input parameter, this command changes the database element to the
specified value for all cells at the specified location. For example, to change the database
element max_tx_bts to value 10 for all cells at site 1, issue the following command at the TTY
command line interface: chg_element max_tx_bts 10 1 all

chg_A5_alg_pr
Specifies A5 encryption algorithms in the order in which they are used by the BSS. For example,
to prioritize the algorithms in the following order: A5/1, A5/2 for a BSS, issue the following
command at the TTY command line: chg_a5_alg_pr 1 2

del_neighbor
When used with the all input parameter, this command deletes all neighbor cells from a cell
neighbor list. For example, to delete all cells from the neighbor list of cell 5 4 3 2 1 61986
34944, issue the following command at the TTY command line interface: del_neighbor 5
4 3 2 1 61986 34944 all

68P02901W17-T

1-49
Jan 2010

Propagating cell parameters using the OMC-R GUI

Chapter 1: Configuration Management General Information

modify_value
When used with the all input parameter, this command modifies values for MMS, RSL or XBL
devices. For example, to modify lapd_t200_timer to 2500 ms for every equipped RSL, issue
the following command at the TTY command line interface:
In SYSGEN mode: modify_value all lapd_t200_timer 2500 rsl

reset_site
Used selectively to reboot available sites without remotely logging in. Typical scenarios could
be: all sites including BSC, all sites excluding BSC, multiple sites and single site. For example to
reboot all sites, issue the following command from the BSC: reset_site all_sites

Propagating cell parameters using the OMC-R GUI

While chg_element is a useful command, it lacks the functionality provided by cell/neighbor
parameter propagation features available from the OMC-R GUI.
Cell parameters can be modified using the OMC-R GUI CELL Detailed View. The modified
parameters are updated at the BSS and, if accepted, are then updated at the MIB.
The user can propagate the settings to the appropriate cells under control of the OMC-R. A user
can propagate cell modifications to:

All cells within the site associated with the selected cell.

All cells within the BSS associated with the selected cell.

All cells controlled by the OMC-R in BSCs running the same version of BSC software.

All cells within the user's Region(s).

See Propagating cell parameters on page 8-79 for further details.

1-50

68P02901W17-T
Jan 2010

Chapter

2
Configuring BSS Features

The information provided here shows how BSS features can be configured to align to the
requirements of the service provider. The following topics are described:

Frequency hopping on page 2-4.

Enhanced XBL (EXBL) on page 2-11.

Dynamic Allocation of RXCDR-BSC Circuits (DARBC) on page 2-13.

Dynamic allocation of BSC-BTS Backing Resources (DYNET) on page 2-19.

MSC to BSS overload control on page 2-23.

Encryption algorithms on page 2-26.

Dual band cells option on page 2-28.

GPRS and EGPRS coding schemes on page 2-39.

Short Message Service - Cell Broadcast on page 2-45.

Short Message Service - Point-To-Point on page 2-53.

Preventive Cyclic Retransmission (PCR) on page 2-56.

MSC initiated IMSI and IMEI call trace on page 2-60.

Call trace flow control on page 2-63.

GPRS Trace on page 2-68

Enhanced Circuit Error Rate Monitor (ECERM) on page 2-70.

Advanced Load Management for EGSM on page 2-78.

Network Controlled Cell Reselection on page 2-81.

GPRS Interleaving TBFs on page 2-89.

GSM location services on page 2-104.

Enhanced GPRS One Phase Access on page 2-113.

PBCCH/PCCCH feature on page 2-117.

Quality of Service (QoS) on page 2-154.

Network Assisted Cell Change (NACC) on page 2-162.

68P02901W17-T
Jan 2010

2-1

Propagating cell parameters using the OMC-R GUI

2-2

Chapter 2: Configuring BSS Features

Enhanced Multi-level Precedence and Pre-emption (eMLPP) on page 2-165.

Fast Call Setup on page 2-168.

RSL Congestion Control on page 2-170.

VersaTRAU on page 2-172.

Feature Capacity Licensing and Audit on page 2-175.

Improved Timeslot Sharing on page 2-176.

GPRS - Suspend/Resume on page 2-178.

Increased Network Capacity on page 2-181.

BSC High Load Protection Mechanism Phase 2 on page 2-183.

HSP MTL on page 2-185.

Software patching and PCU Software Upgrade with no BSC Outage on page 2-188.

High Bandwidth interconnection between BSC and PCU (PSI) on page 2-194.

PCU hardware to increase GPRS capacity on page 2-190.

Increase the Throughput of PRP with the PCU on page 2-197.

Support of Incell as an optional feature on page 2-199.

BSP CPU utilization reduction for higher call handling capacity on page 2-200.

BSS User Security Management on page 2-201.

Quality of Service Phase II on page 2-212.

CTU2-D on page 2-225.

Cell OOS Timer Enhancement on page 2-229.

TDM Availability Enhancements on page 2-230.

TD-SCDMA and GSM interworking on page 2-231.

Extended Uplink TBF (Temporary Block Flow) on page 2-234.

Extended Dynamic Allocation Medium Access Mode (EDMAC) on page 2-236.

Adjustable FER Bins on page 2-238.

Critical Statistics Reporting in 5 minutes on page 2-239.

SW enabler for PA bias switch on/off on CTU2D on page 2-241.

Dual Abis aware BTS on page 2-243

Extended Range Cell (ERC) for Data on page 2-244

Cage Management on page 2-246.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Propagating cell parameters using the OMC-R GUI

A5/1 Security Hardening on page 2-248.

{26638} Gb over IP feature on page 2-253.

{34282} Increase RSL-LCF capacity on GPROC3/GPROC3-2 on page 2-256.

{34371G} CTU4 and RCTU4 on page 2-257

68P02901W17-T

2-3
Jan 2010

Frequency hopping

Chapter 2: Configuring BSS Features

Frequency hopping

Overview of frequency hopping

All subscriber units are capable of frequency hopping under control of the BTS. Implementation
of frequency hopping provides higher quality communications. When hopping is not
implemented, the communications quality between different channels can vary greatly from
causes that include interference and signal fading. Since frequency hopping assigns a different
RF channel to each signaling/traffic channel timeslot every frame, any RF channel interference
is averaged with interference free channels.
Restated, frequency hopping provides higher-quality communications when compared to the
following:

Frequency diversity.

Interference diversity.

Frequency hopping is described in detail in Technical Description: BSS Implementation

(68P02901W36).
Also see Configuring frequency hopping on page 8-165 for details of how to configure frequency
hopping for a cell.

Methods of configuring frequency hopping

To configure frequency hopping, use one of the following methods:

OMC-R GUI CELL Detailed View, see Configuring frequency hopping using the OMC-R
GUI on page 8-167.

TTY interface, see Configuring frequency hopping using the TTY interface on page 8-175.

Planning constraints of frequency hopping

Since the BCCH RF carrier must be transmitted continuously and the BCCH timeslot (timeslot
0 of the BCCH carrier) must always be available in the cell RF coverage area, constraints
associated with frequency hopping include:

2-4

The BCCH timeslot of the BCCH RF channel does not hop.

The non-BCCH timeslots of the BCCH RF channel may hop.

The RF power level of the BCCH RF TX carrier is maintained at the level specified for the
cell. This means that non-BCCH timeslots that hop through the BCCH frequency are
transmitted at the specified BCCH level and are not decreased/increased in incremental
steps.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Types of frequency hopping

Types of frequency hopping

Either of two types of frequency hopping can be implemented at a BTS:

Synthesizer frequency hopping.

Baseband frequency hopping.

If hopping is to be used then Receive Transmit Functions (RTF) must be equipped to assign
frequency hopping indicators (fhi) to each of the eight carrier timeslots. This indicator identifies
a particular frequency hopping system for a cell, or no hopping. Four different systems can
be defined.

NOTE
For EGPRS, baseband hopping is supported, but there are some restrictions due to
the Horizon II macro controller:

If the master cabinet is anything other than a Horizon II macro, baseband

hopping cannot be supported.

EGPRS RTFs must be in a different hopping system from GPRS RTFs. There is
no such restriction for synthesizer hopping.
Firstly, Second,

Synthesizer frequency hopping (SFH)

NOTE
Synthesizer frequency hopping cannot be implemented when RTCs (Remotely
Tunable Combiners) are used.
With synthesizer frequency hopping (SFH), both the transmit and receive RF carrier frequencies
are changed each timeslot. This is accomplished by retuning the Radio Channel Unit (RCU).
A cell equipped with a minimum of two DRI/RCU (RF carriers) can support hopping over a
maximum of 64 frequencies. One DRI/RCU is dedicated for the BCCH (broadcast control
channel) carrier.
Cells with a small number of RF carriers are suited for SFH. Such cells are easily implemented
with hybrid combiners, a requirement for SFH.

68P02901W17-T

2-5
Jan 2010

SFH guidelines (BCCH frequency excluded) with example

Chapter 2: Configuring BSS Features

SFH guidelines (BCCH frequency excluded) with example

Refer to the following guidelines to use SFH with BCCH frequency excluded:

2-6

With SFH, the number of transceivers required in the cell is determined by the number of
traffic channels to be supported. It is not determined by the cell RF channel allocation.

The mobile allocations for these hopping systems must exclude the BCCH carrier channel.

The non-BCCH timeslots of the BCCH carrier must not hop when using SFH so that
mobiles can locate the BCCH carrier. This is a principle of GSM.

Excluding the BCCH carrier, the mobile allocation for these systems can include part of
or all the cell allocation.

The mobile allocation must equal or exceed the number of DRIs in the cell that are to
use the hopping system.

Select different HSNs in distant cells that share the same mobile allocation, avoiding
HSN 0.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

SFH guidelines (BCCH frequency excluded) with example

Example of SFH with BCCH frequency excluded

A typical cell allocation could include a BCCH RF channel and ten non-BCCH channels.
Assuming that the cell is equipped with one DRI dedicated to the BCCH carrier and four DRIs
dedicated to non-BCCH carriers, each SFH system would have to include at least four RF
channels.
The typical mobile allocations shown in Figure 2-1 split the non-BCCH cell allocation in half
for two frequency hopping systems.

Figure 2-1 Typical SFH mobile allocations with BCCH frequency excluded

CELL ALLOCATION

MOBILE ALLOCATIONS

1
9

FREQUENCY

FREQUENCY

HOPPING SYSTEM 0

HOPPING SYSTEM 1

12
16

22

16

12

29

29

22

32

46

46
BCCH

88

32
69

52

RF CHANNEL

69
88
ti-GSM-SC01W17-000041-eps-sw

68P02901W17-T

2-7
Jan 2010

SFH guidelines (BCCH frequency included) with example

Chapter 2: Configuring BSS Features

SFH guidelines (BCCH frequency included) with example

Refer to the following guidelines to use SFH with BCCH frequency included:

With SFH, the number of transceivers required in the cell is determined by the number of
traffic channels to be supported; not by the cell RF channel allocation.

One of the mobile allocations for these hopping systems must exclude the BCCH carrier
channel for assignment to the BCCH timeslot of the non-BCCH carriers.

Excluding the BCCH carrier, the mobile allocation for these hopping systems can include
part of or all the cell allocation.

The mobile allocation must equal or exceed the number of DRIs in the cell that are to
use the hopping system.

Select different HSNs in distant cells that share the same mobile allocation, avoiding
HSN 0.

If using the BCCH frequency on non-BCCH carriers, then the non-BCCH timeslots cannot
be used for traffic channels (hopping through the BCCH).

If not using the BCCH frequency on non-BCCH carriers, then the non-BCCH timeslots can
be used for traffic channels. These channels are broadcasted at the maximum cell power.

Example of SFH with BCCH included

A typical cell allocation could include a BCCH RF channel and ten non-BCCH channels.
Assuming that hopping is to be assigned to all DRIs and that the cell is equipped with one DRI
dedicated to the BCCH carrier and four DRIs dedicated to non-BCCH carriers:

2-8

A system that hops through the BCCH channel would have to include at least five RF
channels.

A system that does not hop through the BCCH channel would have to include at least
four RF channels.

The typical mobile allocations shown in Figure 2-2 split the cell allocation into:

A 5-frequency allocation that does not include the BCCH frequency.

A 6-frequency allocation that includes the BCCH frequency.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Baseband frequency hopping (BBH)

Figure 2-2 Typical SFH mobile allocations with BCCH frequency included

CELL ALLOCATION

MOBILE ALLOCATIONS

FREQUENCY

FREQUENCY

HOPPING SYSTEM 0

HOPPING SYSTEM 1

12

BCCH

16

22

16

12

29

29

22

32

46

32

46

88

69

52

RF CHANNEL

69
88
ti-GSM-SC01W17-000041-eps-sw

Baseband frequency hopping (BBH)

With baseband frequency hopping (BBH), only the receive RF carrier frequencies are changed
each timeslot; the transmit RF carrier is obtained from a different, fixed tuned Radio Channel
Unit (RCU) each timeslot.
A cell equipped with up to 25 DRI/RCU (RF carriers) can support hopping over a maximum of
25 frequencies.
Cells with a large number of RF carriers are well suited for BBH. Such cells are usually
implemented with Remotely Tuneable Combiners (RTCs) and therefore restrict the selection to
BBH at the site.

NOTE
Timeslot 0 of the BCCH cannot baseband hop.

68P02901W17-T

2-9
Jan 2010

BBH guidelines with typical example

Chapter 2: Configuring BSS Features

BBH guidelines with typical example

Refer to the following guidelines to use baseband frequency hopping:

With BBH, the number of transceivers required in the cell is determined by the number of
RF channels in the mobile allocation; not by the number of traffic channels to be supported.

The mobile allocation in a system to be assigned to the BCCH timeslot of non-BCCH

carriers must exclude the BCCH carrier channel.

Select different HSNs in distant cells that share the same mobile allocation, avoiding
HSN 0.

A typical cell allocation would include a BCCH RF channel and four non-BCCH channels
in a cell equipped with one DRI dedicated to the BCCH carrier and four DRIs dedicated to
non-BCCH carriers.
The typical mobile allocations shown in Figure 2-3 split the cell allocation into:

A 4-frequency allocation that does not include the BCCH frequency.

A 5-frequency allocation that includes the BCCH frequency.

Figure 2-3

Typical example of BBH mobile allocations

CELL ALLOCATION

MOBILE ALLOCATIONS

FREQUENCY
HOPPING SYSTEM 0

FREQUENCY
HOPPING SYSTEM 1

32
32
46

32
46

BCCH

46
52

RF CHANNEL

52
69
69

69

88
88

88

ti-GSM-SC01W17-000043-eps-sw

2-10

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Enhanced XBL (EXBL)

Enhanced XBL (EXBL)

Overview of Enhanced XBL

Enhanced XBL (EXBL) provides communication between the BSC and the RXCDR. To maintain
this communication, the RXCDR and BSC have information stored in their databases which
details all the other RXCDRs and BSCs with which with they can communicate.
To ensure that traffic pathways are properly established, the EXBL feature performs runtime
checks of database consistency and connectivity between the BSC and RXCDR. These checks
ensure that the user has configured both the RXCDR and BSS databases correctly.

The connectivity checks verify that for each E1 device, which the BSS database has
indicated is connected to an RXCDR, there exists a corresponding E1 device in the RXCDR
connected to the BSS.

The consistency checks verify that for each CIC (Circuit Identity Code) device equipped
to a particular E1 device at the BSC, there exists a corresponding RXCDR channel in
the RXCDR database.

If any of these consistency or connectivity checks fail, the user is notified so that they can
take the appropriate action. The BSS also automatically disables the relevant CIC devices to
ensure they are not used.
Another user visible aspect is that indications regarding maintenance activity or faults occurring
at the RXCDR which indirectly affect BSC link devices are forwarded to the BSC for processing.
For example, if the MMS at the RXCDR which is carrying the OML link from the BSC is locked,
the RXCDR forwards this information to the BSC. The BSC then disables the OML.
Support of the signaling link between the RXCDR and BSC is not new, however, EXBL
significantly changes the RXCDR and BSC interface. For example, CIC validation is enabled and
provisioning of at least one XBL per RXCDR-BSC pair is mandatory to ensure that the traffic
carrying capability of the interface is available.
EXBL supports RXCDRs which use either existing nailed connect information or CIC information
available from the DARBC feature.
XBLs are contained by the Assoc_RXCDR or Assoc_BSS.
For further technical details, see Technical Description: BSS Implementation (68P02901W36).

Assoc_BSS and Assoc_RXCDR devices

Enhanced XBL uses two devices:

Assoc_RXCDR (AXCDR)

Assoc_BSS (ABSS)

Chapter 4 Configuring a BSS/RXCDR explains how to create and manage these devices.

68P02901W17-T

2-11
Jan 2010

CIC blocking and validation

Chapter 2: Configuring BSS Features

CIC blocking and validation

NOTE
This section applies when XBLs are in use and CIC validation is enabled at the BSC
for a given XBL.
To ensure that the BSS is always using valid traffic circuit identity codes (CIC) to carry calls, the
BSS blocks any CIC at the BSC which cannot be verified to be in good working order. Blocking a
CIC informs the MSC that the CIC should not be used for calls.
When using remote transcoding, the only way to determine if a CIC is in good working order is
to communicate with the RXCDR. If nothing is wrong at the RXCDR that would affect the CIC,
the BSC allows the CIC to remain in operation provided no other blocking condition exists. If
the RXCDR indicates that something is wrong, the BSC blocks the CIC from use.
If the BSC cannot communicate with the RXCDR, the BSC has no way to determine the validity
of any CIC connected through that RXCDR. In this case, the BSC blocks all the CICs connected
to the RXCDR to ensure no calls use the potentially corrupt CICs.
The user must enable the CIC validation option before CICs can be blocked due to RXCDR/BSC
communication failure, see Configuring an Assoc_RXCDR on page 4-72.

Enabling CIC validation

To specify whether the BSC performs CIC validation when the XBL linkset to the RXCDR
comes in-service, or when the XBL linkset is already in service, use the field: CIC Validation
(BSS naming convention: cic_validation) in the Local Routing Information grouping of the
Assoc_RXCDR Detailed View. This parameter can be set to Disabled (No) or Enabled (Yes).
When cic_validation is Disabled (No), the RXCDR can be referred to as in Backwards
Compatibility mode or Static mode. This refers to a BSC or RXCDR in which the Ater channels
and CICs are statically switch connected. This mode does not provide any fault tolerance or
CIC validation, and is intended only to provide an upgrade path. When the BSC and RXCDR
are upgraded, the use of Auto-connect mode is recommended.
When cic_validation is Enabled (Yes), the RXCDR enters Auto-connect mode. In Auto-connect
mode, Ater channels are allocated and released dynamically as resources are provisioned,
un-provisioned, or during handling of fault condition. Auto-connect mode provides fault
tolerance along with the call processing efficiency of Backwards compatibility mode. This is the
recommended mode of operation for the BSC.

NOTE
If CIC Validation is enabled, XBLs must be equipped on the RXCDR and BSC. If no
XBLs are equipped and the AXCDR is operating in Auto-connect mode, all CICs at the
BSC associated with the AXCDR are blocked and no call traffic goes to the AXCDR.

2-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Dynamic Allocation of RXCDR-BSC Circuits (DARBC)

Dynamic Allocation of RXCDR-BSC Circuits (DARBC)

Overview of dynamic allocation of RXCDR-BSC Circuits

The dynamic allocation of Remote Transcoder (RXCDR) to BSC Circuits (DARBC) feature
provides fault management for call traffic on the BSC to RXCDR interface (referred to as the
Ater interface) by managing the individual 16 kbit/s channels (called Ater channels) on this
interface. In addition, this feature provides for validation of the Circuit Identity Code (CIC).
It also provides Ater channel provisioning between the BSC and RXCDR to ensure that calls
are placed on the correct circuit between the BSC and the MSC. Without this feature in place,
fault management of the Ater channels is not possible. In addition, all Ater and CIC information
would have to be manually verified by the user.
This feature is consistent with the Terrestrial Circuit Device Management (TCDM) feature with
respect to how the operator is permitted to manage the CIC devices.
DARBC is an unrestricted feature.
For further technical details, see Technical Description: BSS Implementation (68P02901W36).

BSC and RXCDR responsibilities

The DARBC feature redefines the roles for both the BSC and RXCDR within the BSS network.
However, these changes are transparent to other GSM network entities, such as BTSs and
MSCs. In redefining the responsibilities, a client/server approach is used where the BSC is the
client to the RXCDR server. For example, the RXCDR has the resources (CICs) that the BSC
wants to access, yet the BSC has the intelligence to know which CIC to use.
The BSC responsibilities are as follows:

Track CIC utilization.

Track Ater channel utilization.

Allocate/deallocate Ater channels, as necessary.

Instruct the RXCDR to make switch connections between the Ater channel and transcoder
and rate adaptor unit (TRAU).

Initiate and execute audits of the CIC and Ater information.

68P02901W17-T

2-13
Jan 2010

Auto-connect mode or backwards compatibility (static) mode

Chapter 2: Configuring BSS Features

The RXCDR responsibilities are as follows:

Inform the BSC when activity (due to faults or operator actions) at the RXCDR affects
the usability of Ater channels and/or CICs.

Make switch connections between the Ater channels and TRAU resource when instructed
by the BSC.

Ensure that Ater channels and CICs are switch-connected to the proper idle tone at the
proper times.

Provide the BSC with the necessary CIC and Ater information for auditing.

Handle the error case where the BSC does not initiate the audit procedure.

Auto-connect mode or backwards compatibility (static) mode

Auto-connect mode
This is a user-selectable mode which refers to a BSC in which Ater channels are allocated
and released dynamically as resources are provisioned, un-provisioned, or during handling of
a fault condition (as opposed to a per-cell basis). Auto-connect mode provides fault tolerance
along with the call processing efficiency of backwards compatibility mode. BSC controls the
Auto-connect mode.

NOTE
Before the introduction of this feature, all Ater channels were statically assigned
and the use of XBL links was not mandatory. If an operator decides to use the
Auto-connect mode, it becomes imperative to equip XBL links on the RXCDR and
BSC. If no XBLs are equipped, and the AXCDR is operating in the Auto-connect
mode, all CICs at the BSC associated with the AXCDR become blocked and call
traffic does not go to the AXCDR.
Auto-connect mode is the recommended mode of operation for the BSC. Auto-connect mode
is set using the AXCDR parameter cic_validation, see Enhanced XBL (EXBL) on page 2-11
for further details. For example, if there are six RXCDRs connected to the BSC, enable
cic_validation for the six corresponding AXCDRs.

Backwards compatibility mode (or static mode)

This is a user-selectable mode which refers to a BSC and/or RXCDR in which the Ater channels
and CICs are statically switch connected. (Before DARBC, all Ater channels were statically
assigned) This mode does not provide any fault tolerance or CIC validations.
When upgrading the network (especially when upgrading the BSC before the RXCDR),
Backward compatibility mode should be used for the corresponding AXCDR, otherwise all the
associated CICs become blocked.
Once both BSC and RXCDR are upgraded, the use of Auto-connect mode is recommended.
Backwards compatibility mode is set using the parameter cic_validation, see Enhanced XBL
(EXBL) on page 2-11 for further details.
2-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Determining the number of XBLs required

Network provisioning issues for dynamic allocation

Moving from a static allocation system to a dynamic allocation system (Auto-connect mode)
presents some issues that should be considered when planning and provisioning the BSC/RXCDR
network.
For example, when in Auto-connect mode, a CIC no longer has a fixed position on the Ater
interface. Instead, a CIC may be seen as belonging to a pool of CICs where a separate pool is
maintained for each RXCDR connected to the BSC. When a call is assigned to a CIC, the BSC
allocates an Ater channel that goes to the same RXCDR as the assigned CIC. One implication
of such a pooling is that the number of CICs equipped that go through the RXCDR may not
be the same as the number of Ater channels from the BSC to the RXCDR, as compared to
the static allocation system.

NOTE
The allocation information used by DARBC relies on what is entered when equipping
CICs, both at the BSC and RXCDR plus how a particular MMS is provisioned (that is,
using chg_ts_usage or equip of a link). Therefore, the use of equip and disp_equip
of CICs, disp_mms_ts_usage and disp_connectivity commands are essential for
the user to properly manage and maintain the system.

Determining the number of XBLs required

XBLs carry the signaling traffic between BSC and RXCDR. The number of XBL links required
depends upon the number of CICs and/or the number of Ater interface channels.

Planning considerations
The following factors are considered when planning the number of XBL links from BSC to
RXCDR:

Determine the traffic requirements of the BSC and/or the number of trunks (CICs) used
between the BSC and AXCDR.

Determine the mode (Backward Compatibility or Auto-connect) in which the BSC and
RXCDR operate.

A maximum of 20 XBLs (64 kbit/s or 16 kbit/s) can be configured for a BSC/RXCDR.

A BSC can connect to a maximum of ten RXCDRs.

68P02901W17-T

2-15
Jan 2010

RXCDR-BSC dynamic allocation parameters

Chapter 2: Configuring BSS Features

Provisioning
The number of XBL links depends on the number of trunks on the BSC-RXCDR interface and
whether the Auto-connect mode is enabled at the RXCDR/BSC. Table 2-1 details the minimum
number of XBLs required to support the given number of trunks between the BSC and RXCDR,
with Auto-connect mode.

Table 2-1 Number of BSC to RXCDR signaling links

N = number of MSC
to BSC trunks

No redundancy

With redundancy

Number of 64
kbit/s XBLs

Number of 16
kbit/s XBLs

Number of 64
kbit/s XBLs

Number of 16
kbit/s XBLs

N < 1200

1200 < N < 2400

16

NOTE
The figures mentioned in Table 2-1 , only apply to Auto-connect mode. The
redundancy values are two times the non-redundancy values.
When using Backwards Compatibility mode (cic_validation is off for the corresponding AXCDR
device), technically there is no requirement to equip any XBLs, but it is good practice to equip
at least two 16 kbit XBLs for each AXCDR.
In Backwards Compatibility mode, the only traffic on the XBL is CIC block/unblock information,
which is very minimal; although one XBL link is sufficient, built in redundancy should also
be considered.

RXCDR-BSC dynamic allocation parameters

Table 2-2 details the parameters associated with RXCDR-BSC dynamic allocation. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name.
For further details of commands and parameters, see Technical Description: BSS Command
Reference (68P02901W23).

Table 2-2 RXCDR-BSCdynamic allocation parameters

OMC-R GUI field name/BSS
parameter name
Network Entity Id
network_entity_id

Description
Located in the Identification grouping
of the BSS Detailed View. Indicates
the unique identification of the network
element. When the BSS is created from
the BSS, the user must assign a unique
value to this parameter in the range 1 254. When a user creates a BSS from the
OMC-R, the default identifier is the next
free number in the range.

Values
1 - 254

Continued

2-16

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Methods of configuring dynamic allocation of RXCDR-BSC circuits

Table 2-2 RXCDR-BSCdynamic allocation parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

Transcoding
local_transcoding

Displayed in the Identification grouping of

the BSS Detailed View. Indicates whether
transcoding is performed locally at the
BSS or remotely at an RXCDR.
Once set (at BSS creation), it cannot
be changed. Instead the BSS must be
deleted/unequipped and recreated.

Local (1)
Remote (0)
Default: Remote
(0).

fm_site_type

Indicates the configuration of the site. Not

visible to a user (it is derived internally
from other parameters).

BSC (1)
BTS (2)
RXCDR (3)

Also see parameter cic_validation in Enhanced XBL (EXBL) on page 2-11.

Methods of configuring dynamic allocation of RXCDR-BSC

circuits
RXCDR-BSC dynamic allocation parameters can be configured using:

OMC-R GUI BSS Detailed View and the fields detailed in Table 2-2.

TTY interface, see Configuring RXCDR-BSC dynamic allocation using the TTY
interface.

Configuring RXCDR-BSC dynamic allocation using the TTY

interface
Displaying information for a BSS
To display information for a BSS, use the disp_equipment or disp_bss commands. For example,
the following command displays information for the local transcoding BSS 16:
disp_equip 0 BSS 16

Changing the network entity id of a BSS

To change the network entity identity of a BSS, use the modify_value command and the
network_entity_id parameter. For example, the following command changes the local
transcoding BSS id 17 from 17 to 16:
modify_value 0 network_entity_id 16 BSS 17
If an attempt is made to change the network_entity_id of a remote transcoding BSS, the
following message is displayed:
Changing the BSS id will cause all AXCDRs to be cycled which will result in the

68P02901W17-T

2-17
Jan 2010

Configuring RXCDR-BSC dynamic allocation using the TTY interface

Chapter 2: Configuring BSS Features

loss of all call traffic.

Are you sure (yes/no)?

Displaying the RXCDR-BSC dynamic allocation settings

To display the current local_transcoding setting, use the disp_equipment or disp_bss
commands. For example:
disp_equip 0 BSS 22
The system responds by displaying the following information, for example:
BSS Identifier: 22
Is transcoding performed at the BSC? No

Equipping CICs
See Configuring a CIC on page 9-46 for details of how to configure CICs.

2-18

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Dynamic allocation of BSC-BTS Backing Resources (DYNET)

Dynamic allocation of BSC-BTS Backing Resources

(DYNET)

Overview of BSC-BTS dynamic allocation (DYNET)

NOTE
BSC-BTS dynamic allocation is not supported for M-Cell and Horizon products. It is
only available for InCell and in-building systems.
BSC-BTS dynamic allocation is an alternative mechanism for allocating radio resources between
a BSC and a BTS. BSC-BTS Dynamic allocation is also referred to as BTS concentration or
Dynamic Network of BTSs (DYNET).
Before BSC-BTS Dynamic allocation was available, terrestrial backing resources between the
BSC and BTS were allocated when RTFs were equipped. This mechanism can still be used, but
BSC-BTS dynamic allocation allows the operator to enable dynamic allocation of terrestrial
backing resources for each BTS.
When BSC-BTS dynamic allocation is enabled, when a call is placed on a TCH the terrestrial
backing resource is allocated. When the call leaves a TCH, the terrestrial backing resource is
freed.
The terrestrial backing resource is a 16 kbit/s portion of a timeslot on a span and is allocated by
the BSC from a pool of available resources. This pool is shared by every BTS the user specifies,
and which are within the same network configuration.
BSC-BTS dynamic allocation can be used for spoke, daisy chain and closed loop daisy chain
network configurations.
Two network objects are required for BSC-BTS dynamic allocation; a Dynet, and a DynetGroup.
For a full technical description of BSC-BTS dynamic allocation, see Technical Description: BSS
Implementation (68P02901W36).

RSL TCHs used for backhaul

If the RSL at the BTS containing the cell is set to use 16 kbit/s (parameter: rsl_rate) and
ts_sharing is enabled at the BTS, the remaining three 16 kbit/s TCHs on the RSL 64 kbit/s
timeslot are used for backhaul for that BTS only. This means there are three additional TCHs
that can be used by any cell at that BTS only. In addition, the three additional TCHs are reserved
only for cells at the site with 16 kbit/s RSL. Other BTSs in the Dynet may not use the additional
three TCHs. For example, if there are 10 timeslots in the Dynet, 40 TCHs are available to all
cells in the Dynet. If BTS1 has a 16 kbit/s RSL and BTS2 has 64 kbit/s RSL, then cells at BTS1
have 43 TCHs available to share with the other cells at BTS1. In this example, the maximum
number of TCHs allocated to all cells in the Dynet cannot exceed 43. If all RSLs are 64 kbit/s in
the Dynet, the maximum TCHs allocated cannot exceed 40.

68P02901W17-T

2-19
Jan 2010

Prerequisites to enabling BSC-BTS dynamic allocation at a BTS

Chapter 2: Configuring BSS Features

Prerequisites to enabling BSC-BTS dynamic allocation at a BTS

BSC-BTS dynamic allocation at a BTS can only be enabled if:

BSC-BTS dynamic allocation is unrestricted (enabled) at the containing BSS.

BTS is a remote BTS.

BSC-BTS dynamic allocation parameters

Table 2-3 lists the parameters associated with BSC-BTS dynamic allocation. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name.
For further details of commands and parameters, see Technical Description: BSS Command
Reference (68P02901W23). Also see Configuring DYNETs and DYNETGroups on page 4-90 for
details of associated BSC-BTS dynamic allocation Dynet parameters.

Table 2-3 BSC-BTS dynamic allocation parameters

OMC-R GUI field
name/BSS parameter
name

Description

BSC-BTS dynamic
allocation Feature
(OMC-R parameter
name:
BSCBTSDynAllocOpt)

Displayed in the BSS Detailed View Optional

Features grouping.
Displays whether BSC-BTS dynamic allocation for
the BSS is enabled or disabled. A user cannot
change it.

Enabled (1)
Disabled (0)

Timeslot Sharing
ts_sharing

Displayed in the SITE Detailed View, Local

Routing Information grouping. This parameter
field is grayed out for SITE0 (BSC). Enables or
disables BSC-BTS dynamic allocation for the BTS
at the time of creation only. Once a BTS has been
created, it cannot be reset.
Only accessible when BSC-BTS dynamic allocation
is Enabled (1).

Enabled (1)
Disabled (0)
Default:
Disabled (0)

Dynet Retry Time

dynet_retry_time

Displayed in the BTS SITE Detailed View, Local

Routing grouping. This parameter field is grayed
out for SITE0 (BSC).

150 - 3000 ms
Default: 1000

Values

The retry time used by the BTS when requesting

a terrestrial backing resource from the BSC. The
BTS tries three times to get terrestrial backing
resources before deciding a TCH cannot be
allocated due to lack of resources.
Only accessible when BSC-BTS dynamic allocation
and Timeslot Sharing are Enabled (1).
Continued

2-20

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Displaying if BSC-BTS dynamic allocation is unrestricted at a BSS

Table 2-3 BSC-BTS dynamic allocation parameters (Continued)

OMC-R GUI field
name/BSS parameter
name
Total TCHs Reserved
dynet_tchs_reserved
(OMC-R parameter
name:
dynet_tchs_rsvd)

Description
Displayed in the CELL Detailed View, General
section, Local Routing Information grouping.
The amount of terrestrial backing resources
(TCHs) reserved for a cell.
Only available when BSC-BTS dynamic allocation
is enabled for the BTS containing this cell (that
is, ts_sharing is enabled). Otherwise the field is
grayed-out in the CELL Detailed View and is set to
0.
If the user attempts to set a value so that the
total reserved cell capacity exceeds the terrestrial
backing resources for the BTS network, the BSS
rejects the request.

Values
0 - 32 traffic
channels
Default: 0

Displaying if BSC-BTS dynamic allocation is unrestricted at a

BSS
To display if the optional BSC-BTS dynamic allocation feature is unrestricted (enabled) at a BSS
using the OMC-R GUI, look in the Optional Features grouping of the BSS Detailed View. If the
feature is unrestricted, Enabled (1) is displayed in the BSC-BTS dynamic allocation Feature
field (BSS parameter name: BSCBTSDynAllocOpt). If the feature is restricted, Disabled
(0) is displayed.

Enabling BSC-BTS dynamic allocation at a BTS

To enable BSC-BTS dynamic allocation at a BTS using the OMC-R GUI, use the SITE Detailed
View and the Local Routing grouping parameters as detailed in Table 2-3.
To enable BSC-BTS dynamic allocation at a BTS using the TTY interface, use the equip
command. For full details of the equip command, see Technical Description: BSS Command
Reference (68P02901W23).

Displaying details of an equipped BTS using the TTY interface

To display details for an equipped BTS, including whether BSC-BTS dynamic allocation is
enabled, use the disp_equip command. For example, to display the details for BTS 1, enter the
following command: disp_equip 0 site 1
The system responds by displaying all the BTS details. For full details of the disp_equip
command, see Technical Description: BSS Command Reference (68P02901W23).

68P02901W17-T

2-21
Jan 2010

Other dynamic allocation features

Chapter 2: Configuring BSS Features

Other dynamic allocation features

Dynamic allocation of RXCDR-BSC circuits (DARBC) enables E1 connection between the RXCDR
and BSC channels between the RXCDR and BSC to be assigned to calls as needed, rather than
statistically assigning such channels to CIC.
See Dynamic Allocation of RXCDR-BSC Circuits (DARBC) on page 2-13 for further details.

2-22

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

MSC to BSS overload control

MSC to BSS overload control

Overview of MSC to BSS overload Control

MSC to BSS Overload Control temporarily reduces the traffic between the MSC and the BSS on
the A interface when an overload occurs. By default, MSC Overload Control is disabled.
When MSC Overload Control is enabled at a BSS and the MSC becomes overloaded, the MSC
sends an overload message to the BSS to indicate that it is becoming overloaded. The BSS
reacts to the overload message by reducing the traffic sent to the MSC by barring specific
mobile access classes within cells in the BSS. When a mobile class is barred, a group of MSs are
no longer allowed to make calls on the network. Hence the traffic to the MSC is reduced. The
mobile access class information for the classes to be barred is carried to the mobile subscriber
in the SYSTEM INFORMATION message specified in GSM recommendations.
See Technical Description: BSS Implementation (68P02901W36) for a full explanation of this
feature.

Enabling MSC to BSS overload control

The parameter bss_msc_overload_allowed controls whether MSC to BSS Overload Control
is enabled or disabled, that is, whether the BSS acts on the OVERLOAD message sent from
the MSC.
To enable MSC to BSS Overload Control for an existing BSS using the OMC-R GUI, set the MSC
Overload Control field (BSS name: bss_msc_overload_allowed) to Enabled (1) in the General
grouping of the BSS Detailed View.

Related overload control statistic

The database statistic msc_ovld_msgs_rx records the number of OVERLOAD messages received
from the MSC. See Maintenance Information: GSM Statistics Application (68P02901W56) for
full statistics details.

Timer parameters for mobile access class barring and unbarring

Table 2-4 details the timer parameters used for mobile access class barring. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For
further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).
The BSS reuses the T1 and T2 timers to implement the T17 and T18 timers at the cell level. The
T17 and T18 times are the same duration as the T1 and T2 timers. The duration of the T17 and
T18 timers are therefore defined by the cell parameters flow_control_t1 and flow_control_t2.

68P02901W17-T

2-23
Jan 2010

Methods of configuring MSC to BSS overload control

Chapter 2: Configuring BSS Features

Table 2-4 Timer parameters for mobile access class barring

OMC-R GUI field
name/BSS parameter
name

Description

Flow Control T1 Timer

flow_control_t1

Displayed in the CELL Detailed View, Flow Control parameter

grouping.
Indicates the time that must elapse before new overload messages
are considered by the Flow Control mechanism.
Multiple OVERLOAD messages may be sent from the MSC to the
BSS. There is a danger that the access classes will be barred far too
rapidly, resulting in all access classes being restricted throughout
the BSS. To guard against this a timer is started on reception
of an OVERLOAD message. This timer is called T17. The BSS
ignores all subsequent OVERLOAD messages received after the
first instance until T17 expires. When T17 has expired the next
OVERLOAD message received by the BSS results in the next access
class being barred and T17 is restarted. Timer T17 duration is set
by flow_control_t1.
Valid values are: 0 - 1000000 (ms).
Default is 20000.

Flow Control T2 Timer

flow_control_t2

Displayed in the CELL Detailed View, Flow Control parameter

grouping.
Indicates the time that must elapse before a previously flow control
barred access class is brought back in service.
There is no message sent from the MSC to the BSS notifying the
BSS that the MSC processor overload condition has cleared. The
unbarring of the access classes to increase the traffic to the MSC
is controlled by a timer. This timer is called T18. This timer is
also started when the first OVERLOAD message is received. If no
subsequent OVERLOAD message has been received when the T18
timer expires then the BSS will unbar an access class. The T18 timer
is then restarted, unless all of the access classes are now unbarred.
Timer T18 duration is set by the flow_control_t2 parameter. The
reception of an OVERLOAD message after the expiry of T17, but
before the expiry of T18, results in the barring of a mobile access
class and both timers T17 and T18 are restarted.
Valid values are 0 - 1000000 (ms).
Default is 3000.

Methods of configuring MSC to BSS overload control

A user can configure MSC to BSS Overload Control, using either of the following methods:

2-24

OMC-R GUI BSS and CELL Detailed Views, and the parameter fields already detailed
in this section.

TTY interface, see Configuring MSC to BSS Overload Control using the TTY interface.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Configuring MSC to BSS overload control using the TTY interface

Configuring MSC to BSS overload control using the TTY interface

Enabling and disabling MSC overload control using the TTY interface
To set MSC overload control using the TTY, use the chg_element command. For example, the
following command enables (1) MSC overload control at site 0:
chg_element bss_msc_overload_allowed 1 0
See Technical Description: BSS Command Reference (68P02901W23) for full command and
parameter details.

Displaying the status of MSC overload control using the TTY interface
To display whether MSC overload control is enabled or disabled, use the disp_element
command. For example:
disp_element bss_msc_overload_allowed 0
If the MSC overload control is enabled the OMC-R displays:
bss_msc_overload_allowed = 1

Controlling mobile access class barring using the TTY interface

Use the parameters detailed in Table 2-4 to control mobile access class barring. For example, to
set a value of 1500 ms for flow_control_t1, use the chg_element command as follows:
chg_element flow_control_t1 1500 <location> <celldescription>

68P02901W17-T

2-25
Jan 2010

Encryption algorithms

Chapter 2: Configuring BSS Features

Encryption algorithms

Introduction to encryption algorithms

Encryption/decryption provides security for user speech, data, and signaling information. The
encryption feature is optional and for effective use must be deployed at the MSC, BSS, and
the MS.
Parallel operation of the A5/1, A5/2 and Null encryption algorithms are supported at BSS level.

Prerequisites for configuring encryption algorithms

To configure encryption algorithms, the encryption feature (multiEncryptOpt) must be
unrestricted (Enabled).

Encryption algorithm procedures

These procedures are described in the following sub-sections:

Activating the specific encryption algorithm using the chg_element command.

Prioritizing the order in which the encryption algorithms are to be used by the BSS using
the chg_a5_alg_pr command.

Displaying the prioritized list of encryption algorithms used at the BSS using the
disp_a5_alg_pr command.

Activating the encryption algorithms

To activate the encryption algorithms, use the chg_element command and either the
option_alg_a5_1 (A5/1) or option_alg_a5_2 (A5/2) parameter (detailed in Table 4-6).
For complete details of the commands used, refer to: Technical Description: BSS Command
Reference (68P02901W23).

2-26

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Prioritizing the encryption algorithms

Prioritizing the encryption algorithms

Before prioritizing the encryption algorithms into a list for use by the BSS, the specific
encryption algorithm database parameters must be enabled.
To prioritize the A5 encryption algorithms into a list for use by the BSS, use the following
command:
chg_a5_alg_pr <first_alg> [<second_alg>] [<third_alg>] [<fourth_alg>]
[<fifth_alg>] [<sixth_alg>] [<seventh_alg>] [<eighth_alg>]
For example, to prioritize the encryption algorithms in the following order: A5/2, A5/1, the
command is:
chg_a5_alg_pr 2 1
To set no encryption, the command is:
chg_a5_alg_pr 0
The BSS provides the capability to send a Cipher Mode Reject message to the MSC (if the
MSC supports this message). This message is sent when a problem is encountered during the
signaling encryption process when the MS and the system are attempting to perform encryption.
To enable this capability, the command is:
chg_element ciph_mode_rej_allowed 1 <location>
For full details of the commands used refer to: Technical Description: BSS Command Reference
(68P02901W23).

Displaying the prioritized list

To display the current priority list of encryption algorithms used by the BSS, enter the following
command:
disp_a5_alg_pr
The current priority order of encryption algorithms used by the BSS is displayed.
For example, the system response where two encrypting algorithms are used in the order:
A5/2, A5/1, is:
Ciphering Algorithms are prioritized as follows:

2 1

When no ciphering algorithms are used, the system response is:

Ciphering Algorithms are prioritized as follows:

For full details of the commands used refer to: Technical Description: BSS Command Reference
(68P02901W23).

68P02901W17-T

2-27
Jan 2010

Dual band cells option

Chapter 2: Configuring BSS Features

Dual band cells option

Overview of the single BCCH for a dual band cells feature

The Dual Band Cells feature (also referred to as the Single BCCH for Dual Band Cells feature)
enables a single BCCH carrier to serve GSM900 and DSC1800 frequencies in the same
coverage area. The frequency band used in a dual band cell for the BCCH carrier and any
optional non-BCCH carrier of the same band, is considered the primary band for the cell. The
frequency band used in a dual band cell for the remaining non-BCCH carriers is considered
the secondary band.
The Single BCCH for Dual Band Cells feature provides the capability to configure and manage
cells with carriers from different frequency bands by using a concentric cells configuration.
Specifically, primary band carriers can be configured in the outer zone (providing total cell
coverage) and secondary band carriers can be configured in the inner zone. Configure all
SDCCHs in the cell on the primary band/outer zone. (This is consistent with the Concentric Cells
feature, which requires the BCCH and SDCCHs to be configured in the outer zone carriers.)
An example of a system which could utilize the Single BCCH for Dual Band Cells feature is
an established PGSM network with access to DCS1800 frequencies, and a subscriber base
populated with a sufficient number of multiband capable mobiles. In this situation, the DCS1800
frequencies can be allocated as non-BCCH carriers added to existing PGSM cells. The PGSM is
the primary band and the DCS1800 is the secondary band for the dual band cell.
Single BCCH for Dual Band Cells feature permits configuration of carriers with only two
different frequency types at the cell level for the following frequency bands:

PGSM/EGSM.

DCS1800.

Either of these bands can be assigned as the primary band for the cell.
When the Dual Band Cells feature is enabled for a cell, the frequency type is managed on
a per zone basis. Primary band carriers are configured in the outer zone (providing total cell
coverage), and secondary band carriers are configured for the inner zone.
GPRS is not supported on the secondary band within a Dual Band cell.
See Technical Description: BSS Implementation (68P02901W36) for a full description of this
feature.

2-28

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Overview of the single BCCH for a dual band cells feature

Benefits
Single BCCH for Dual Band Cells feature provides a:

Convenient way of expanding system capacity by utilizing frequencies from the secondary
band (provided sufficient multiband subscriber population exists). This enables system
capacity to be increased without modifying either the frequency plan of the primary
frequency or the associated neighbor list.

Reduction in the number of cells required in the database.

Reduction in the management of neighbor lists.

Areas impacted
The areas primarily impacted by the Single BCCH for Dual Band Cells feature include
configuration, inner zone use algorithms, channel selection algorithms, and handover and
power control. Also, the BSS:

Supports two different frequency bands within a single cell using a concentric cells
configuration.

Allows the network operator to define the coverage area of the primary and secondary
bands independently using BSS parameters.

Enhances the channel allocation algorithms to incorporate selection of channels from

different frequency bands and ensure that the allocation of the secondary band inner zone)
resource at TCH assignment when qualifications are met.

Provides power level conversions for intra-cell channel changes and incoming inter-cell
handovers between channels on different frequency bands.

Impact on RTFs and DRIs

Normally, there is an RTFGroup for each cell, and one of these RTFs is a BCCH RTF. The Dual
Band Cells Option uses two RTFGroups for one cell. The RTFGroup containing the BCCH RTF
must be for the primary band. All RTFs in this group are in the outer cell zone and have ARFCN
frequencies in the primary band. The other RTFGroup containing RTFs for the same cell:

Are non-BCCH.

Are in the inner cell zone.

Have ARFCN frequencies in the secondary band.

68P02901W17-T

2-29
Jan 2010

Interaction with other features

Chapter 2: Configuring BSS Features

Influence of concentric cells, multiband, and congestion relief features

The single BCCH for dual band cells feature requires inter-zone traffic management to control
the two frequency bands within the single cell. This is provided by the concentric cells feature
(concentricCellOpt). The concentric cells feature inter-zone traffic management is handled
by the power based use algorithm which manages traffic between zones using algorithms
based on uplink and downlink receive levels, as well as network operator preferences defined
by the outer_zone_usage_level parameter.
Traffic is managed between frequency bands of different cells using the MultiBand Inter-Cell
H/O feature (mbInterCellHoOpt) by using algorithms based on frequency types of the serving
cell neighbor cells, as well as network operator preferences defined by the band_preference
and band_preference_mode parameters. To achieve a satisfactory algorithm for inter-zone
traffic management with the dual band cells feature, the concentric cells feature power-based
use algorithm has been enhanced with the MultiBand Inter-Cell H/O feature inter-band traffic
management shifted from an inter-cell level to an intra-cell level. The resulting inner zone use
algorithm for dual band cells feature verifies that the MS supports the frequency band of the
inner zone before evaluation of the receive levels.
If unrestricted and enabled, the alternative congestion relief Feature (congestReliefOpt) (that
is, Directed Retry alternatives) is applied to dual band cells. This can also include enabling
Enhanced Congestion Relief (ECR) (enhanced_relief). See BSS and CELL Detailed Views for
the related parameter fields.

Interaction with other features

This feature interacts with the IMRM feature, see for further details.

Prerequisites and restrictions for enabling the Dual Band

Option
The following features must also be unrestricted (enabled) for the dual band cells feature to
function:

The homogenous cabinet feature.

The multiband inter-cell H/O feature.

The heterogeneous cabinet feature (only required for combined cabinet configurations).

Concentric cells feature.

The status of all these features can be viewed in the BSS Detailed View (Optional Features
grouping).
The Coincident Multiband feature and the Dual Band Cells feature are mutually exclusive, and
cannot be enabled at the same time.

2-30

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Dual band cells option parameters

Dual band cells option parameters

Table 2-5 shows the parameters associated with the Dual Band Cells feature. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. A full
description of BSS database parameters is provided in Technical Description: BSS Command
Reference (68P02901W23).

Table 2-5 Single BCCH parameters

OMC-R GUI field
name/BSS parameter
name
Dual Band Cells Option
(OMC-R parameter
name:
dualBandCellOpt)

Inner Zone Algorithm

inner_zone_alg

Description
Displayed in the BSS Detailed View Optional Features grouping.
Displays whether the Dual Band Cells feature has been enabled for
this BSS. Valid values are:

Enabled (1)

Disabled (0)

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping.
Displays the algorithm used to hand into the inner zone. Valid values
are:

Disabled (0).

Power Based Use Algorithm (1).

Interference based Use Algorithm (2).

Dual Band Cell Use Algorithm (3).

The Interference based Use algorithm (2) determines that an

intra-cell handover should occur based on interference levels from
neighbor cells which use an interfering frequency. The Power
based Use Algorithm (1) determines that an intra-cell handover
should occur based on power control algorithms. The Dual Band
Cell Use Algorithm (3) can only be used when the Dual Band Cell
option is enabled. This algorithm provides the capability to manage
cells with carriers from two different frequency bands. When the
Dual Band Cells feature and MultiBand (mb_preference) are
enabled for a BSS, no RTFs are equipped for the inner zone, and
coincident_mb is disabled, this parameter can be set to Dual Band
Cell Use Algorithm (3). This indicates the cell is a dual band cell.
If the primary frequency_type is PCS1900, this parameter cannot
be set to 3. When set to 3, prompts for the following are displayed:
BTS Max Transmit Pwr for Inner Zone (bts_txpwr_max_inner),
Secondary Frequency Type (secondary_freq_type), Max MS
Transmit Power When HO to Inner zone (ms_txpwr_max_inner),
Inner Zone Handover Hysteresis (zone_ho_hyst), Inner Zone DL
Receive Level Threshold (rxlev_dl_zone), Inner Zone UL Receive
Level Threshold (rxlev_ul_zone) and HO Power level for Inner Zone
(ho_pwr_level_inner).
Continued

68P02901W17-T

2-31
Jan 2010

Dual band cells option parameters

Chapter 2: Configuring BSS Features

Table 2-5 Single BCCH parameters (Continued)

OMC-R GUI field
name/BSS parameter
name

Description

Dual Band Offset

dual_band_offset
(OMC-R parameter
name:
dualBand_offset)

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping.
Specifies the offset used when calculating the power budget using
measurement information from a secondary band channel. Valid
value range is: -63 to +63. The default is 0.

Power Budget Mode

pbgt_mode

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping.
Specifies for the preferred method of compensating for a mismatch
in frequency types between the serving channel and the neighbor
cell BCCH when calculating power budget. Valid values are:

Second Frequency
Type
secondary_freq_type
(OMC-R parameter
name:
second_freq_type)

0 - the MS uses the serving channel measurements for the

secondary band with the addition of the dual_band_offset to
calculate the power budget.

1 - the MS uses the reported serving cell signal strength for the
primary band (Through modified SACCH System Information
messages) to calculate the power budget. The BCCH frequency
of the serving cell is added to the BA SACCH neighbor cell
list of the serving cell.

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping.
When a cell is configured as dual band, this parameter specifies the
frequency type of the inner zone, secondary band of the cell. Valid
values are:

PGSM (1).

EGSM (2).

DCS1800 (4).

BTS Max Transmit Pwr

For Inner Zone
bts_txpwr_max_inner
(OMC-R parameter
name:
btsTxPwrMax_inner)

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping.
When inner_zone_alg is set to 3, indicating the cell is a dual band
cell, this parameter specifies the BTS maximum transmit power
for the secondary band/inner zone. Valid values depend on the
equipment type and are detailed in Technical Description: BSS
Command Reference (68P02901W23). For example, for PGSM,
EGSM and DCS1800 cells, and M-Cell6, Horizonmacro or Horizon II
macro controlling BTS cabinets, the range is -1 to 21.

HO Power level for

Inner Zone
ho_pwr_level_inner
(OMC-R parameter
name:
hoPwrLevel_inner)

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping.
When the cell is configured as a dual band cell, this parameter
specifies the handover power level for the inner zone. Valid range
is: 0 - 19 and 29 - 31 (that is, the same as for handover_power_level
except based on the secondary_freq_type, not the primary
frequency_type). The default value is 2.
Can only be modified when Dual Band Cell Option is enabled.
Continued

2-32

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Dual band cells option parameters

Table 2-5 Single BCCH parameters (Continued)

OMC-R GUI field
name/BSS parameter
name

Description

Coincident MB HO
Status
coincident_mb

Displayed in the CELL Detailed View, General section, Coincident

Multiband HO grouping. Determines whether the Coincident
Multiband HO feature is enabled or disabled at the cell.
Can only be modified if the MultiBand feature is unrestricted.
Cannot be enabled if the cell is configured as a dual band cell (that
is, inner_zone_alg is set to 3)
Valid values are 0 - 3:
0 - Coincident MultiBand is disabled at this cell.
1 - Coincident cell handovers are enabled
2 - Coincident cell handovers and coincident cell redirections are
enabled
3 - Intra BSC handovers behave the same as coincident_mb = 2. But
for inter BSC handovers, the call is targeted at the primary cell.

MultiBand Enabled
mb_preference

Displayed in the BSS Detailed View, Multiband grouping. Determines

whether the MultiBand feature is enabled or disabled for the BSS.
Can only be modified if the MultiBand Inter-Cell Handover feature is
unrestricted (Enabled).
Cannot be disabled if there are cells at this BSS that are configured
as a dual band cell (that is, inner_zone_alg is set to 3).

Cell Transmit Power

tx_power_cap

Displayed in the CELL Detailed View, General section, General

grouping. Determines whether the cell transmits at high or low
power.
Only valid for cells that are configured as dual band cells (that is,
inner_zone_alg is set to 3), regardless of the frequency type of
the cell.

Max MS Transmit Pwr

When HO to Inner Zone
ms_txpwr_max_inner

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping.
Determines the maximum transmit power of the mobile station when
handing over from the outer zone to the inner zone.
Only valid for cells that are configured as dual band cells (that is,
inner_zone_alg is set to 3). The valid range is then dependent
on the secondary band frequency type. Otherwise, the range is
dependent on the primary frequency type.

Inner Zone Handover

Hysteresis
zone_ho_hyst

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping.
Determines the hysteresis added to the threshold to determine if an
outer zone to inner zone handover should take place.
Only valid for cells that are configured as dual band cells (that is,
inner_zone_alg is set to 3). The valid range is then -63 to 63.
Otherwise the range is 0 - 30.

Frequency Type
frequency_type

Displayed in the CELL Detailed View, General section, General

grouping.
Specifies the single frequency band capability of the cell.
When the cell is a dual band cells (that is, inner_zone_alg is set to
3), and secondary_freq_type is EGSM or PGSM, frequency_type can
only be set to DCS1800. When the cell is a dual band cells (that is,
inner_zone_alg is set to 3), and secondary_freq_type is DCS1800,
frequency_type can only be set to PGSM or EGSM.
Continued

68P02901W17-T

2-33
Jan 2010

Dual band cells option parameters

Chapter 2: Configuring BSS Features

Table 2-5 Single BCCH parameters (Continued)

OMC-R GUI field
name/BSS parameter
name

Description

Inner Zone DL Receive

Level Threshold
rxlev_dl_zone

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping.
The downlink receive threshold that must be crossed for a handover
to take place from the outer zone to the inner zone in a concentric
cell or dual band cell. Only used if the CELL inner_zone_alg type is
set to the Power Based or the Dual Band Cell Use Algorithms. Valid
values are 0 - 63, where:
0 = -110 dBm.
1 = -109 dBm.
2 = 108 dBm.
..
63 = -47 dBm.

Inner Zone DL Receive

Level Threshold
rxlev_ul_zone

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping.
The uplink receive threshold that must be crossed for a handover to
take place from the outer zone to the inner zone in a Concentric cell
or Dual Band cell. Only used if the Cell inner_zone_alg type is set to
the Power Based or the Dual Band Cell Use Algorithms.
Valid values are 0 - 63, where:
0 = -110 dBm.
1 = -109 dBm.
63 = -47 dBm.

Concentric Cell Zone

cell_zone

Displayed in the RTF Detailed View, Concentric cells Grouping.

Determines in which zone the RTF is located. Only used for
non-BCCH carriers. Valid values are: Outer zone (0), Inner zone (1).
Default is Outer zone (0).

Outer Zone Usage

Level
outer_zone_usage_
level

Displayed in the CELL Detailed View, General section, Concentric,

and Dual-Band Cells grouping. Defines the usage level required
before inner zone resources are allocated for traffic and phone
calls are handed into the inner zone. Valid values are: 0 - 100
(percentage).

Band Preference
band_preference

Displayed in the CELL Detailed View, General section, Multiband

Handover grouping. Determines the destination frequency band
preferred for an Inter-Cell handover. The value of this element
indicates to which band this cell prefers to assign or hand over. Valid
values are: 1 = PGSM, 2 = EGSM, 4 = DCS1800, 8 = PCS1900. 16
= DYNAMIC.
Cannot be modified unless the MultiBand Inter-Cell Handover
feature is enabled (unrestricted). Not used if Cell band_pref_mode
has a value of 0. Default value is the frequency_type of the Cell.
A value of 16 (Dynamic) indicates that the Intelligent Multilayer
(IMRM) feature is enabled (unrestricted) for the cell. Can only be set
to 16 (Dynamic) if the Intelligent Multilayer Resource Management
feature (imrmOpt) is enabled (unrestricted) for the BSS (See for
details). If set to 16 (Dynamic) and all weightings are set to 0, the
following message is displayed: WARNING: IMRM weights set to
unsupported. The BSS applies internal defaults.
Continued

2-34

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Overview of configuring single BCCH for dual band cells feature

Table 2-5 Single BCCH parameters (Continued)

OMC-R GUI field
name/BSS parameter
name
Band Preference Mode
band_preference_
mode

Description
Displayed in the CELL Detailed View, General section, Multiband
Handover grouping. Determines the method that is used to have a
MultiBand MS use the band of preference for a given cell in the BSS.
Can only be modified if the MultiBand Inter-Cell Handover feature
is unrestricted (enabled). (See for details)

Mobile Station HO
Displayed in the CELL Detailed View, Handover section, General
Power Level
grouping. Indicates the maximum Dedicated Control Channel (CCH)
handover_power_level power level allowed for a Mobile Station (MS) after a handover to
this cell. Valid range depends on the setting of Cell frequency_type.
Maximum Transmit
Power for BTS
max_tx_bts

Displayed in the CELL Detailed View, Power Control section,

Downlink Power Control grouping. Indicates the maximum output
power for the base station transmitter. Can be used to establish
a cell boundary. Valid range depends on the setting of Cell
frequency_type. For example, for PGSM, EGSM and DCS1800
cells, and M-Cell6, Horizonmacro or Horizon II macro controlling
BTS cabinets, the range is -1 to 21.

Maximum Mobile
Station Transmit Power
max_tx_ms

Displayed in the CELL Detailed View, Power Control section, Uplink

Power Control grouping. Indicates the maximum MS output power
which can be used in this cell. Regardless of the power class of the
mobile, the mobile is not told to use a higher output power. The
values should be chosen to balance the up and down links in a cell.
Valid range depends on the setting of Cell frequency_type.

Maximum Control
Channel Transmit
Power
ms_txpwr_max_cch

Displayed in the CELL Detailed View, General section, System

Access grouping. Defines maximum random access power available
for a mobile station, on a control channel (CCCH) in a cell. Valid
range depends on the setting of Cell frequency_type.

Maximum Default
Transmit Power
ms_txpwr_max_def

Displayed in the CELL Detailed View, Power Control section, General

grouping. Contains the default value to be used for a neighbor
cell when the Neighbor ms_txpwr_max_cell is not defined in an
underlying Neighbor instance. Valid range depends on the setting of
Cell frequency_type.

Intra-Cell Handover
Allowed
intra_cell_handover
_allowed

Displayed in the CELL Detailed View, Handover section, Handover

Types Allowed grouping.
Disables or enables intra-cell handovers. Valid values are 0 - 2.
Default is BSC Controlled Handover (1).

Overview of configuring single BCCH for dual band cells feature

A network operator with an existing single band network and the necessary restricted features
enabled, can change cells from a single band configuration to a dual band configuration without
interruption of service on the primary band.
The procedure is:

68P02901W17-T

2-35
Jan 2010

Methods of configuring the dual band cells option

Chapter 2: Configuring BSS Features

Procedure 2-1 Change cells from single band to dual band configuration
1

Modify the inner_zone_alg parameter for the cell to Dual Band

Cell (3).

Specify settings for the following parameters:

Frequency Type of the secondary band.

BTS Maximum Transmit Power level.

MS maximum Transmit Power Level.

Handover Power Level.

Handover Hysteresis.

Downlink Receive Level Threshold.

Uplink Receive Level Threshold.

Dual Band Offset.

Power Budget Mode.

Once the inner_zone_alg parameter and above parameters are set to

enable dual band cells, the DRIs and RTFs for the secondary band
must be equipped. It is necessary to allow two DRI/RTFGroups per cell
because the frequency of the RTF must match the radio equipment tied
to the DRI. There must be different DRI/RTFGroups associated with the
primary band and the secondary band of the dual band cell. Secondary
band carriers must be equipped as inner zone carriers.

Define the percentage in the Outer Zone Usage Level field

(outer_zone_usage_level) (that is, outer zone TCHs) that need to be
in use before the assignment of secondary band channels.

The dual band cell is fully operational when the secondary band DRIs are brought in to service.

Methods of configuring the dual band cells option

The Dual Band Cells Option can be configured using either of the following methods:

2-36

OMC-R GUI BSS and CELL Detailed Views, and the fields described in Table 2-5.

TTY interface, see Configuring the Dual Band Cells Option using the TTY interface.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring the dual band cells option using the TTY interface

Configuring the dual band cells option using the TTY interface
The TTY interface can be used to configure a cell, including specifying the dual band operation
requirements. The following sections indicate the BSS commands and parameters that can
be used to create, display, and modify dual band operation parameters. For further details
of these commands and parameters, see Technical Description: BSS Command Reference
(68P02901W23). Also see Table 2-5 in this section for details of the parameters.
Security Level 2 is required to enter these TTY commands.

Creating a dual band operation cell

To create a cell and specify all the cell parameters, including the dual band operation
parameters, use the add_cell command. In response to this command, the BSS prompts for
each of the cell parameters.

Displaying if dual band cells feature is enabled

To display whether dual band cells feature is restricted or unrestricted for the BSS, use the
command:
disp_options all
If the dual band operation feature is unrestricted the system displays the following in the
unrestricted features list:
40 Dual Band Cells
Ensure that the following features are also unrestricted:

Infrastructure Sharing Homogenous Cabinet

MultiBand Inter-Cell Handover

Infrastructure Sharing Heterogeneous Cabinet

Concentric Cells

The Infrastructure Sharing Heterogeneous Cabinet feature is only required for combined
cabinet configurations.

Setting the dual band offset

To display the current dual band offset, use either the disp_cell or disp_element commands,
and the dual_band_offset parameter. For example, the following command displays the offset
value at BSC (site 0) for cell 001 01 17:
disp_element dual_band_offset 0 cell 0 0 1 0 1 1 7
To set the dual band offset value, use either chg_element or chg_cell_element and the
dual_band_offset parameter. For example, the following command sets the dual band offset to
28 at the BSC (site 0) at the cell 0010111:
chg_cell_element dual_band_offset 28 0 cell 0 0 1 0 1 1 1

68P02901W17-T

2-37
Jan 2010

Configuring the dual band cells option using the TTY interface

Chapter 2: Configuring BSS Features

Setting the power budget mode

To display the current power budget mode, use either the disp_cell or disp_element
commands, and the pbgt_mode parameter. For example, the following command displays the
power budget mode at BSC (site 0) for cell 001 01 17:
disp_element pbgt_mode 0 cell 0 0 1 0 1 1 7
To change the power budget mode, use either chg_element or chg_cell_element and the
pbgt_mode parameter. For example, the following command sets the power budget mode
to 1 at the BSC (site 0) at the cell 0010111:
chg_cell_element pbgt_mode 1 0 cell 0 0 1 0 1 1 1

Setting the frequency type of the inner zone

To display the current frequency type of the inner zone, use either the disp_cell or
disp_element commands, and the secondary_freq_type parameter. For example, the following
command displays the secondary frequency type at BSC (site 0) for cell 001 01 17:
disp_element secondary_freq_type 0 cell 0 0 1 0 1 1 7
To change the secondary frequency type, use chg_element and the secondary_freq_type
parameter. For example, the following command sets the secondary frequency type to 2 (EGSM)
at the BSC (site 0) at the cell 0010111:
chg_element secondary_freq_type 2 0 cell 0 0 1 0 1 1 1

Setting the transmit power for the inner zone

To display the maximum BTS transmit power for the secondary/inner zone, use either the
disp_cell or disp_element commands, and the bts_txpwr_max_inner parameter. For
example, the following command displays the inner zone maximum transmit power at BSC
(site 0) for cell 001 01 17:
disp_element bts_txpwr_max_inner 0 cell 0 0 1 0 1 1 7
To change the inner zone maximum transmit power, use chg_element and the
bts_txpwr_max_inner parameter. For example, the following command sets the inner zone
maximum transmit power to 11 at the BSC (site 0) at the cell 0010111:
chg_element bts_txpwr_max_inner 11 0 cell 0 0 1 0 1 1 1

Setting the handover power level for the inner zone

To display the handover power level for the secondary/inner zone, use either the disp_cell or
disp_element commands, and the ho_pwr_level_inner parameter. For example, the following
command displays the inner zone handover power at BSC (site 0) for cell 001 01 17:
disp_element ho_pwr_level_inner 0 cell 0 0 1 0 1 1 7
To change the inner zone handover power level, use chg_element and the ho_pwr_level_inner
parameter. For example, the following command sets the inner zone handover power level to
16 at the BSC (site 0) at the cell 0010111:
chg_element ho_pwr_level_inner 16 0 cell 0 0 1 0 1 1 1

2-38

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GPRS and EGPRS coding schemes

GPRS and EGPRS coding schemes

Introduction to GPRS CS3/CS4

The GPRS Coding Schemes 3 and 4 feature (CS3/CS4) implements an alternative channel coding
algorithm over the air interface, which enables increased data rates to the GPRS mobile stations.
For further information of GPRS Coding Schemes 3 and 4, see Technical Description: BSS

Implementation (68P02901W36).

Introduction to EGPRS MCS

The EGPRS Coding Schemes 1 to 9 feature provides higher data rates to the EGPRS mobile
station. Coding Schemes MCS-1 through MCS-4 use GMSK (as per standard GPRS), whilst
MCS-5 through MCS-9 use 8PSK.
For further information of EGPRS Coding Schemes 1 to 9, see Technical Description: BSS

Implementation (68P02901W36).

68P02901W17-T

2-39
Jan 2010

GPRS and EGPRS coding scheme parameters

Chapter 2: Configuring BSS Features

GPRS and EGPRS coding scheme parameters

Table 2-6 details the parameters associated with configuring GPRS and EGPRS coding schemes.

Table 2-6 GPRS and EGPRS coding schemes parameters

OMC-R GUI field name/BSS
parameter name

Description

BSS Parameters:
GPRS Coding Schemes 3
and 4 (CS3/CS4) feature
(OMC-R parameter
name:
cs34Opt)

Displayed in the Optional Features grouping in the BSS Detailed

View form.
Displays whether the GPRS Coding Schemes 3 and 4 (CS3/CS4)
feature is unrestricted (Enabled) or restricted (disabled) for the
BSS.
Valid values: Disabled (0) or Enabled (1). Default is 0. Cannot be
modified by a user.
Grayed-out if the GPRS feature (gprsOpt) is restricted at the BSS.

EGPRS Feature
egprsOpt

Displayed in the Optional Features grouping in the BSS Detailed

View form.
Displays whether the EGPRS feature is unrestricted (enabled) or
restricted (disabled) for the BSS.
Valid values: Disabled (0) or Enabled (1). Cannot be modified by
a user.

Cell Parameters:
Initial Downlink Coding
Scheme
init_dl_cs

Displayed in the GPRS grouping in the CELL Detailed View.

The init_dl_cs parameter is used to specify the initial downlink
Coding Scheme (CS) configuration information for a cell. This
parameter is also used for QoS capacity determination. The value
of this parameter cannot be changed when gprs_enabled equals
1.
Valid values: 0 - 3, where:
0 - CS-1
1 - CS-2
2 - CS-3
3 - CS-4
The OMC-R disregards any RTF parameters when determining
valid values for init_dl_cs. (pkt_radio_type will not be prompted
during the equipage of an RTF and the option to select CS-3 or
CS-4 is disabled).
Grayed-out if the GPRS feature (gprsOpt) is restricted at the BSS.
Continued

2-40

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GPRS and EGPRS coding scheme parameters

Table 2-6 GPRS and EGPRS coding schemes parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Initial Uplink Coding

Scheme
init_ul_cs

Displayed in the GPRS grouping in the CELL Detailed View.

The init_ul_cs attribute is used to specify the initial uplink Coding
Scheme (CS) configuration information for a cell. This parameter
is also used for QoS capacity determination. The value of this
parameter cannot be changed when gprs_enabled equals 1.
Valid values: 0 - 3, where:
0 - CS-1
1 - CS-2
2 - CS-3
3 - CS-4
The OMC-R disregards any RTF attributes when determining legal
values for init_ul_cs CELL DV attribute. (pkt_radio_type will
not be prompted during the equipage of an RTF and the option to
select CS-3 or CS-4 is disabled).
Grayed-out if the GPRS feature (gprsOpt) is restricted at the BSS.

EGPRS Initial Downlink

Coding Scheme
egprs_init_dl_cs

Displayed in the GPRS grouping in the CELL Detailed View.

The egprs_init_dl_cs attribute specifies the initial downlink coding
scheme to be used for an EGPRS TBF in a cell. This parameter is
also used for QoS capacity determination. The EGPRS feature
must be unrestricted. The value of this parameter cannot be
changed when gprs_enabled equals 1. Grayed-out if the EGPRS
feature (egprsOpt) is restricted at the BSS.

EGPRS Initial Uplink

Coding Scheme
egprs_init_ul_cs

Displayed in the GPRS grouping in the CELL Detailed View.

The egprs_init_ul_cs attribute specifies the initial uplink coding
scheme to be used for an EGPRS TBF in the cell. This parameter
is also used for QoS capacity determination. The EGPRS feature
must be unrestricted. The value of this parameter cannot be
changed when gprs_enabled equals 1.
Grayed-out if the EGPRS feature (egprsOpt) is restricted at the
BSS.
Continued

68P02901W17-T

2-41
Jan 2010

GPRS and EGPRS coding scheme parameters

Chapter 2: Configuring BSS Features

Table 2-6 GPRS and EGPRS coding schemes parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

RTF Parameter:
Packet Radio Type
pkt_radio_type

Displayed in the RTF Detailed View in the GPRS group.

This parameter replaces allow_32k_trau, and indicates whether
the RTF can carry GPRS or EGPRS data. SDCCH allocation favors
carriers with low values.
Valid values are: 0 - 3, where:
0 - None
1 - 16 k
2 - 32 k
3 - 64 k
Grayed out if the parent BSS has the GPRS feature (gprsOpt)
restricted.
The 32 k option is not displayed if the Coding Schemes 3 and 4
feature (cs34Opt) is restricted (Disabled) in the associated BSS.
The 64 k option is not displayed if the EGPRS feature (egprsOpt)
is restricted (Disabled) for the associated BSS.
The 32 k and 64 k options are not displayed if the RTF cell_zone
parameter is set to inner zone (1).
RTF cell_zone is restricted to outer zone (0) if pkt_radio_type
value is 32 k or 64 k.
The 32 k and 64 k options are not displayed if the associated
SITE ts_sharing value is set to BSC-BTSdynamic allocation
supported (1).
The 32 k and 64 k options are not displayed if the RTFrtf_capacity
value is RTF_SUB (1) (sub-equipped).
The RTFrtf_capacity value of RTF_SUB (1) (sub-equipped) is not
displayed if the pkt_radio_type value is 32 k or 64 k.
The 64 k option is not displayed if the RTF ext_timeslots value is
non-zero.
RTF ext_timeslots value is restricted to 0 if the RTF
pkt_radio_type value is 64 k.
The 64 k option is displayed if the associated SITE contains at
least one of the following cabinets: Horizon macro, Horizon macro
extension, Horizon II macro, Horizon II macro extension, Horizon
II mini or Horizon II mini extension.
If a user changes pkt_radio_type in edit mode, the OMC-R issues
a warning message that the configuration change results in a
temporary outage of the RT and requests operator confirmation
before proceeding.

PCU Parameters:
Continued

2-42

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Methods for configuring GPRS and EGPRS coding schemes

Table 2-6 GPRS and EGPRS coding schemes parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

SCORE MCS THRES A

score_mcs_thres_a

Displayed in the PCU Detailed View in the General group.

The parameter score_mcs_thres_a allows customer setting Score
MCS Threshold A in Coding Scheme Selection.
Modification of this element will not be allowed when the EGPRS
feature is restricted.
The value of element score_mcs_thres_a for Score MCS Threshold
A must be less than or equal to the value of score_mcs_thres_b for
score MCS threshold B.
Valid values are in the range of 0 - 100, with step size of 1 and
default value 20.

SCORE MCS THRES B

score_mcs_thres_b

Displayed in the PCU Detailed View in the General group.

The parameter score_mcs_thres_b allows customer setting Score
MCS Threshold B in Coding Scheme Selection.
Modification of this element will not be allowed when the EGPRS
feature is restricted.
The value of element score_mcs_thres_b for Score MCS Threshold
B must be greater than or equal to the value of score_mcs_thres_a
for Score MCS Threshold A.
Valid values are in the range of 0 - 100, with step size of 1 and
default value 48.

NOTE
If DRIM-based carriers are used, and if any of the timeslots are used for GPRS, then
all timeslots must have backing for 32 kbit/s TRAU due to the processing limitations
within the DRIM hardware.

Methods for configuring GPRS and EGPRS coding schemes

The GPRS and EGPRS coding schemes can be configured using:

OMC-R GUI, using the BSS Detailed View (Optional Features grouping), and RTF Detailed
View (GPRS grouping), and the fields detailed in Table 2-6.

TTY interface, see Configuring GPRS and EGPRS Coding Schemes using the TTY
interface.

68P02901W17-T

2-43
Jan 2010

Configuring GPRS and EGPRS coding schemes using the TTY interface

Chapter 2: Configuring BSS Features

Configuring GPRS and EGPRS coding schemes using the TTY

interface
Displaying if the GPRS CS3/CS4 feature is unrestricted
To display whether the GPRS Coding Schemes 3 and 4 (CS3/CS4) feature is unrestricted
(Enabled) or restricted (Disabled) for the BSS, use the command: disp_options all
If the GPRS Coding Schemes 3 and 4 (CS3/CS4) feature is unrestricted it is listed in the
unrestricted features list.

Setting 32 k TRAU Allowed for an RTF

To enable or disable 32k TRAU for an RTF, use the modify_value command. For example, the
following command enables 32 kbit/s TRAU timeslots for RTF 0 1.
modify_value 1 pkt_radio_type 2 rtf 0 1

2-44

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Short Message Service - Cell Broadcast

Short Message Service - Cell Broadcast

Overview of SMS-CB
The Short Message Service - Cell Broadcast (SMS-CB) is an optional feature that provides a
means of unilaterally transmitting background messages to MSs on a per cell basis, using
the Cell Broadcast Channel (CBCH).
Each BSC is connected to a single Cell Broadcast Centre (CBC), which is responsible for
downloading cell broadcast messages to the BSC together with indications of the repetition rate
and the number of broadcasts required per message. The BSC is responsible for transmitting
these updates to the BTSs affected, which then ensures that the message is transmitted as
requested.

Message details for SMS-CB

Message handling
The maximum number of concatenated messages (pages) forming one macromessage is 15 for a
maximum of 128 cells. The length of this message cannot be more than 2.5 kbytes, otherwise
the CBL resets, and an alarm is raised.
Each page in a micromessage has the same message identifier, indicating the source of the
message, and the same serial number.
The maximum storage capacity at the BTS is 650 pages.
The BSS divides into segments messages larger than 576 bytes received from the CBC.

Message categories
The CBC categorizes messages as:

High.

Normal.

Background.

High priority messages are scheduled into Reserved slots allocated by the CBC in the current
schedule period. Thereafter, they are treated as normal messages.
Background priority messages are accepted from the CBC and scheduled into slots remaining
from those occupied by High and Normal priority messages.

68P02901W17-T

2-45
Jan 2010

SMS-CB parameters

Chapter 2: Configuring BSS Features

CBC configurable DRX period

A DRX message can be configured, which can be switched on or off by messages from the CBC.
The period of the DRX can also be set through the CBC.

Alphabets supported by the SMS

Various default alphabets are supported by the Short Message Service feature. The default
alphabets enable background messages to be broadcast in the following languages:

Czech.

Danish.

Dutch.

English.

Finnish.

French.

German.

Greek.

Hungarian.

Italian.

Norwegian.

Polish.

Portuguese.

Spanish.

Swedish.

Turkish.

SMS-CB parameters
Table 2-7 details the SMS-CB parameters. Unless stated otherwise, the OMC-R parameter name
is usually the same as the BSS parameter name. Refer to: Technical Description: BSS Command
Reference (68P02901W23) for full details of the commands and parameters used.

2-46

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 2-7

SMS-CB parameters

SMS-CB parameters

OMC-R GUI field name/BSS

parameter name

Description

Values

CBC to BSC Interface

Version
cbc_intface_vers

Displayed in the BSS Detailed View SMS

Information grouping. Used to select the BSS
to CBC interface. Select (on a per BTS site
basis) either the existing interface, or the
enhanced interface with the new interpretation
of the repetition rate and CBCH loading fields.
This selects the protocol used across the SMS
CB interface. The new maximum broadcast
repetition rate is one 8 x 51 multiframe
sequence which corresponds to a frequency
period of 1.883 seconds. The current interface
selected can also be displayed.

Existing (0).
Existing with new
interpretation of
repetition rate
(1).
The default is
Existing (0).

CBC VBIND Counter

cbc_vbind_cntr

Displayed in the BSS Detailed View SMS

Information grouping. Used to set (on a per
BTS site basis) the number of successful
Version Binds (VBINDS) that must be sent by
the BSS to the CBC before a negotiation takes
place within the next VBIND sent. The VBIND
includes a version parameter which indicates
what version of the specifications is supported
by the CBC/BSS sending the VBIND, and the
version of the interface the system wants to
use on the established SVC. The number of
successful VBINDS sent to the CBC before
negotiation takes place can also be displayed.
This value is the number of successful Version
Binds (VBINDS) that must be sent by the BSS
to the CBC before a negotiation takes place.

A value in the
range 0 - 255.
The default is 0.

SMS Fast Select

sms_fast_select

Displayed in the BSS Detailed View SMS

Information grouping. Indicates what type
of X.25 network is being used. Enabled
(1) indicates the BSS and CBC attempts to
exchange user data in the network connection
and network connection release phases of
X.25. Disabled (0) means the BSS and CBC
will not exchange user data in the network
connection and network connection release
phases of X.25. If a user changes this field the
system displays a message to warn that the
CBL will be recycled.

Enabled (1) or
Disabled (0).

CBC to CBS Outage

Counter
cbs_outage_cntr

Displayed in the SITE Detailed View SMS

Information grouping. Specifies (on a per
BTS site basis) how many broadcast slots
the CBS should wait before considering the
CBC sourced messages invalid in the case of
an outage. This introduces a delay between
the outage occurring and the CBS halting
transmission of CBC originated messages. The
current delay, on a per BTS basis, can also be
displayed.

0 - 255.

68P02901W17-T

2-47
Jan 2010

Methods of configuring SMS-CB

Chapter 2: Configuring BSS Features

Methods of configuring SMS-CB

The SMS-CB can be configured using the following methods:

OMC-R GUI, BSS and SITE Detailed Views, and the parameters detailed in Table 2-7.

TTY interface, see Configuring SMS-CB using the TTY interface.

An SMS-CB message can be edited and viewed using the OMC-R GUI, see Viewing and editing
the SMS-CB message using the OMC-R GUI on page 8-244.

Configuring SMS-CB using the TTY interface

For further details of the commands and parameters detailed in the following sections, refer to:
Technical Description: BSS Command Reference (68P02901W23).

Determining status of CBCH using the TTY interface

To determine the status of the CBCH, use the disp_cbch_state command. For example, the
following command displays the status of message number 3 at cell 543 21 61986 3494:
disp_cbch_state 3 543 21 61986 3494
The system response depends on the state of the CBCH.

Displaying state of CBCH using the TTY interface

To display the state of the CBCH, use the command disp_element and the cbch_enabled
parameter. For example:
disp_element cbch_enabled 0 cell_number = 5 4 3 2 1 61986 34944
The response is one of the following:
cbch_enabled = 0 (CBCH disabled).
cbch_enabled = 1 (CBCH enabled).

Displaying counter statistic state using the TTY interface

To display the state of the counter statistic, use the command disp_stats. For example:
disp_stats sms_no_bcast_msg cell 5 4 3 2 1 62259 784
The response is one of the following:

2-48

No stats data available.

Valid stats info from specified interval.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring SMS-CB using the TTY interface

Selecting the interface version between the BSS and CBC using the TTY
interface
To select the interface version between the BSS and CBC, use the chg_element command and
the cbc_intface_vers parameter. For example, to select the existing interface with a new
interpretation of the repetition rate and CBCH loading fields at BSC, use the following command:
chg_element cbc_intface_vers 1 0
The command is rejected in the following instances:

If a BTS location is entered in the command, the following error message is displayed:
COMMAND REJECTED: Element requires a location parameter of 0

If a BSC location with a bsc type 0 is entered in the command, the following error message
is displayed: COMMAND REJECTED: bsc_type not compatible with specified element

If an RXCDR location is entered in the command, the following error message is displayed:
COMMAND REJECTED: Element specified not allowed at an RXCDR site.

Setting number of successful VBINDs using the TTY interface

To set number of successful VBINDs sent between a BSS and CBC in a BSC site before a
negotiate is needed, use the chg_element command and the cbc_vbind_cntr parameter. For
example, to set the number of successful VBINDs to 3 before a negotiate becomes necessary,
use the following command:
chg_element cbc_vbind_cntr 3 bsc
The command is rejected in the following instances:

If a BTS location is entered in the command, the following error message is displayed:
COMMAND REJECTED: Element requires a location parameter of 0

If a BSC location with a bsc type 0 is entered in the command, the following error message
is displayed:COMMAND REJECTED: bsc_type not compatible with specified element

If an RXCDR location is entered in the command, the following error message is

displayed:COMMAND REJECTED: Element specified not allowed at an RXCDR site.

Setting delay between outage and halting transmission using the TTY
interface
To set a delay between an outage occurring and the CBS halting transmission of CBC messages,
use the chg_element command and the cbs_outage_cntr parameter. For example, to set the
delay to 20 for site 1 use the following command: chg_element cbs_outage_cntr 20 1
The command is rejected in the following instances:

If a stand alone BSC location is entered in the command, the following error message is
displayed: COMMAND REJECTED: Element specified not allowed at a stand alone
BSC

If an RXCDR location is entered in the command, the following error message is displayed:
COMMAND REJECTED: Element specified not allowed at an RXCDR site.

68P02901W17-T

2-49
Jan 2010

Configuring SMS-CB using the TTY interface

Chapter 2: Configuring BSS Features

Displaying CBC to BSS interface information using the TTY interface

To display the CBC to BSS interface version being used by BSC sites, use the following
disp_element command and the cbc_intface_vers parameter. For example:
disp_element cbc_intface_vers 0
If the command is accepted, the system responds: cbc_intface_vers = 0
The command is rejected in the following instances:

If a BTS location is entered in the command, the following error message is displayed:
COMMAND REJECTED: Element requires a location parameter of 0

If a BSC location with a bsc type 0 is entered in the command, the following error message
is displayed: COMMAND REJECTED: bsc_type not compatible with specified element

If an RXCDR location is entered in the command, the following error message is displayed:
COMMAND REJECTED: Element specified not allowed at an RXCDR site.

Displaying number of successful VBINDs using the TTY interface

To display the number of successful VBINDs sent between a BSS and CBC in a BSC site before a
negotiation is needed, use the disp_element command and the cbc_vbind_cntr parameter. For
example:
disp_element cbc_vbind_cntr 0
If the command is accepted, the system responds: cbc_vbind_cntr = 0
The command is rejected in the following instances:

If a BTS location is entered in the command, the following error message is displayed:
COMMAND REJECTED: Element requires a location parameter of 0

If a BSC location with a bsc type 0 is entered in the command, the following error message
is displayed: COMMAND REJECTED: bsc_type not compatible with specified element

If an RXCDR location is entered in the command, the following error message is displayed:
COMMAND REJECTED: Element specified not allowed at an RXCDR site.

Displaying delay between an outage and halting transmission using the

TTY interface
To display the delay between an outage occurring and the CBS halting transmission of CBC
messages at a BTS site, use the disp_element command and the cbs_outage_cntr parameter.
For example, use the following command to display the value of the cbs_outage_cntr at site 2:
disp_element cbs_outage_cntr 2
If the command is accepted, the system responds: cbc_vbind_cntr = 0
The command is rejected in the following instances:

2-50

If a standalone BSC location is entered in the command, the following error message is
displayed: COMMAND REJECTED: Element specified not allowed at a stand alone
BSC

If an RXCDR location is entered in the command, the following error message is displayed:
COMMAND REJECTED: Element specified not allowed at an RXCDR site.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring SMS-CB using the TTY interface

Enabling and disabling CBCH using the TTY Interface

To enable the CBCH use the chg_element command and cbch_enabled parameter. For example:
chg_element cbch_enabled 1 0 cell = 5 4 3 2 1 61986 34944
To disable the CBCH use the chg_element command and cbch_enabled parameter. For
example:
chg_element cbch_enabled 0 0 cell = 5 4 3 2 1 61986 34944

Enabling and disabling counter statistic using the TTY interface

To enable the counter statistic use the stat_mode command and sms_no_bcast_msg parameter.
For example:
stat_mode sms_no_bcast_msg ON cell = 5 4 3 2 1 61986 34944

Disabling counter statistic

To disable the counter statistic use the stat_mode command and sms_no_bcast_msg
parameter. For example:
stat_mode sms_no_bcast_msg OFF cell = 5 4 3 2 1 61 986 34944

Creating and transmitting background messages using the TTY interface

To create and transmit background messages, use the chg_smscb_msg command. For example,
to send a background message to cell number = 5 4 3 2 1 61986 34944 with a message number
of 0, a message id of 1234, scope of immediate, cell wide, a code of 0, the language set to
English and an update number of 0, follow these steps:

Procedure 2-2 Create and transmit background messages at the TTY interface
1

Enter the following command:

chg_smscb_msg 0 1234 0 0 0 1 5 4 3 2 1 61986 34944
The following is displayed:
Enter the Message:

At this prompt, enter the CBCH background message, which can be

up to 93 alphanumeric characters in length. To continue a message,
use the escape character (\) at the end of each line of the message, for
example:
Enter the Message:
This is the first line of the message.\
This is the last line of the message.

Press the Return key to terminate the message and transmit it to the
cell.

Technical Description: BSS Command Reference (68P02901W23) contains further examples of

this command.

68P02901W17-T

2-51
Jan 2010

Configuring SMS-CB using the TTY interface

Chapter 2: Configuring BSS Features

Deleting background messages using the TTY interface

One or more background messages may be deleted using the del_smscb_msg command. The
following can be deleted:

A single message at a single cell.

A single message at all cells in the BSC.

All messages at a single cell.

All messages at all cells in the BSC.

For example, to delete a single message at a single cell (message number 0 at cell number 5 4 3
2 1 61986 34944) use the following command:
del_smscb_msg 0 5 4 3 2 1 61986 34944

Technical Description: BSS Command Reference (68P02901W23) contains further examples of

this command.

2-52

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Short Message Service - Point-To-Point

Short Message Service - Point-To-Point

Introduction to setting up SMS-PTP

The Short Message Service - Point-to-Point (SMS-PTP) is an option that provides a means of
two-way transmission between the network and the MS.
The parameters associated with this feature permit selective MS originated or MS terminated
Point-to-Point SMS. The downlink logical channel may also be specified for MS terminated
point-to-point sms. The timing constraints on the SACCH allow a block to be transferred every
104 frames, while the FACCH allows a block to be delivered every 8 frames. The disadvantage
of the FACCH is that frames are stolen, with adverse effects on the audio quality or data
transmission. Stealing frames on the FACCH would be more noticeable as the size of the short
message increases, but using the SACCH for larger messages means longer delivery times.
If the logical channel is selected by the BSS, the selection depends on the status of the MS.
If.....

Then.....

the MS is idle

SDCCH is used.

the MS is on SDCCH

SDCCH is used.

the MS is busy

SACCH or FACCH is used.

Refer to: Technical Description: BSS Command Reference (68P02901W23) for full details of
the commands used.

SMS-PTP procedures
The following SMS-PTP procedures are described in the following sections:

Enabling the MS originated point-to-point SMS.

Displaying the MS originated point-to-point SMS.

Enabling the MS terminated point-to-point SMS.

Displaying the MS terminated point-to-point SMS.

Specifying the downlink logical channel.

SMS-PTP prerequisites
This feature is automatically enabled when the system is purchased. It is disabled when either
the MS originated SMS-PTP feature or the MS terminated SMS-PTP feature are themselves
disabled. It requires a Service Centre which stores and forwards the messages. The transfer of
short messages between the Service Centre and the MS needs the support of the GSM PLMN.

68P02901W17-T

2-53
Jan 2010

Enabling and disabling MS originated Point to Point SMS at a site

Chapter 2: Configuring BSS Features

Enabling and disabling MS originated Point to Point SMS at a

site
For further details of the commands and parameters detailed in the following sections, refer to
Technical Description: BSS Command Reference (68P02901W23).

Enabling MS originated SMS-PTP

To enable MS originated SMS-PTP on an individual site basis, use the following command:
chg_element sms_ul_allowed 1 <location>
For example to enable the MS originated SMS-PTP at site 1, use:
chg_element sms_ul_allowed 1 1

Disabling MS originated SMS-PTP

To disable MS originated SMS-PTP on an individual site basis, use the following command:
chg_element sms_ul_allowed 0 <location>
For example to disable the MS originated SMS-PTP at site 1, use:
chg_element sms_ul_allowed 0 1

Displaying the state of MS originated Point to Point SMS at a

site
To display the status of MS originated SMS-PTP on an individual site basis, use the following
command:
disp_element sms_ul_allowed <location>
For example, to display the status of the MS originated SMS-PTP at site 1, use:
disp_element sms_ul_allowed 1
The system responds, for example:
sms_ul_allowed = 1

Enabling and disabling MS terminated SMS-PTP at a site

Enabling MS terminated SMS-PTP
The MS terminated SMS-PTP may be enabled on an individual site basis by using the following
command:
chg_element sms_dl_allowed 1 <location>
For example to enable MS terminated SMS-PTP at site 0, use:
chg_element sms_dl_allowed 1 0

2-54

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying the state of MS terminated SMS-PTP at a site

Disabling MS terminated SMS-PTP

The MS terminated SMS-PTP may be disabled on an individual site basis by using the following
command:
chg_element sms_dl_allowed 0 <location>
For example, to disable MS terminated SMS-PTP at site 0, use:
chg_element sms_dl_allowed 0 0

Displaying the state of MS terminated SMS-PTP at a site

The status of MS terminated SMS-PTP may be displayed on an individual site basis by using the
following command:
disp_element sms_dl_allowed <location>
For example, to display the status of MS terminated SMS-PTP at site 1, use:
disp_element sms_dl_allowed 1
The system responds, for example:
sms_dl_allowed = 1

Specifying the downlink logical channel

The downlink logical channel may be specified on an individual site basis by using the following
command:
chg_element sms_tch_chan <element_value> <location>
For example, to specify the downlink logical channel at site 1 use:
chg_element sms_tch_chan 1 1

Displaying the DOWNLINK LOGICAL CHANNEL

The downlink logical channel may be displayed on an individual site basis by using the following
command:
disp_element sms_tch_chan <location>
For example to display the downlink logical channel at site 1, use:
disp_element sms_tch_chan 1
The system responds, for example:
sms_tch_chan = 1

68P02901W17-T

2-55
Jan 2010

Preventive Cyclic Retransmission (PCR)

Chapter 2: Configuring BSS Features

Preventive Cyclic Retransmission (PCR)

Introduction to PCR
The Preventive Cyclic Retransmission (PCR) method of error correction is supported by the
Multiple Serial Interface, and is advantageous where large transmission delays are experienced,
as in satellite links. At initialization, the database is checked by the Layer 2 code to ensure that
PCR error correction has been enabled for use. If PCR error correction is not enabled for use,
the default is Basic error correction. When using PCR, a Message Signaling Unit (MSU) which
has been transmitted is retained at the transmitting signaling link terminal until a positive
acknowledgment for that MSU has been received. During a period when there are no new
MSUs to be transmitted, or when the maximum number of unacknowledged messages has been
reached, all of the MSUs which have not been positively acknowledged are transmitted cyclically.
PCR is clearly defined in CCITT Q.703 section 6 (reference #2).

Range and default values for Timers

The range and default values of the 7 MTP level 2 timer parameters are listed in Table 2-8.

Table 2-8

7 MTP level 2 timer parameters

Timer

Range (ms)

Default

Index Value

T1 (alignment ready)

40000 - 50000

50000

T2 (not aligned)

5000 - 150000

25000

1000 - 1500

1400

T4 (emergency)

400 - 600

600

T5 (sending SIB)

80 - 120

100

3000 - 6000

5000

800 - 2000

1000

T3 (aligned)

T6 (remote
congestion)
T7 (excessive delay of
acknowledgment)

These timers are displayed and can be configured in the BSS Detailed View MTP Timers
parameter grouping or using the TTY interface.

2-56

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Range and default values for N-value parameters

Range and default values for N-value parameters

The default values of the two N-value parameters are listed in Table 2-9.

Table 2-9 3 N-value parameters

N-value

Parameter

Range

Default

N1 (threshold)

pcr_n1

32-127 MSUs

127 MSUs.

N2 (threshold)

pcr_n2

950-3750 (octets)

3750 octets.

The third N-value parameter, pcr_enable, is the flag required to change the error correction
from basic error mode to PCR error correction mode. When this element is set to 1, PCR error
correction is in the enabled state, and when it is set to 0, the PCR error correction is disabled,
and the basic error correction mode is enabled.

Methods of configuring PCR

PCR can be configured using the following methods:

OMC-R GUI, BSS Detailed View, and the parameters detailed in the Signaling Information
grouping (see Table 4-5).

TTY interface, see Configuring PCR using the TTY interface below.

Configuring PCR using the TTY interface

The following PCR TTY interface procedures are described in this section:

Enabling and disabling PCR.

Displaying the status of PCR.

Setting up message signaling units.

Setting up message unit octets.

Displaying the current value of a PCR parameter.

Setting up timer values.

Refer to Technical Description: BSS Command Reference (68P02901W23) for full details of the
commands used in the subsequent sections.

68P02901W17-T

2-57
Jan 2010

Configuring PCR using the TTY interface

Chapter 2: Configuring BSS Features

Enabling and disabling PCR using the TTY interface

To display the status of the PCR error correction feature at the BSC, use the following command:
disp_element pcr_enable 0
The system responds with a message stating whether PCR error correction is Enabled or
Disabled.
To enable the PCR error correction mode at the BSC, use the following command:
chg_element pcr_enable 1 0
To disable the PCR error correction mode at the BSC, use the following command:
chg_element pcr_enable 0 0
To set up the number of Message Signaling Units use the following command:
chg_element pcr_n1 <element_value> <location>
For example, to set the number of MSUs to 33 at the BSC, enter the command:
chg_element pcr_n1 33 0

Setting up message unit octets using the TTY interface

To set up the number of message unit octets, use the following command:
chg_element pcr_n2 <element_value>
For example, to set the number of message unit octets to 1000, enter the command:
chg_element pcr_n2 1000

Displaying the current value using the TTY interface

To display the current value of the new PCR N parameters, use the following command:
disp_element pcr_n1
disp_element pcr_n2
If the command is executed correctly, the displayed responses might be:
pcr_n1 = 64
pcr_n2 = 1850

Setting up timer values using the TTY interface

To update the appropriate MTP level 2 timer value, use the following command:
chg_element ss7_l2_t* <element_value> <location>

2-58

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Where:

Configuring PCR using the TTY interface

is:
t*

T1 to T7 (inclusive)

<element value>

the value within the range for the

particular timer shown in the table
below.

<location>

the location identifier, either 0 or bsc.

Refer to Table 2-8 for the range and default values of the MTP level 2 timers.

68P02901W17-T

2-59
Jan 2010

MSC initiated IMSI and IMEI call trace

Chapter 2: Configuring BSS Features

MSC initiated IMSI and IMEI call trace

Introduction to MSC initiated call trace

The MSC initiated IMSI and IMEI call trace allows an MS to be tracked as it moves across the
network. The MSC invokes call tracing at the BSS, which collects call trace data for either the
International Mobile Subscriber Identity (IMSI) or the International Mobile Equipment Identity
(IMEI), based upon the invoking message. This call trace data is then forwarded to the OMC-R.
A call trace started by an MSC request, has the call trace data sent to the OMC-R for storage
in a call trace logfile. This call trace data can also be forwarded to the Network Management
Centre (NMC) if necessary.
The percentage of BSS resources to be reserved for MSC initiated traces can be specified
through the call_trace_options parameter. The maximum number of call traces allowed at any
one time is 16 for each BSS. The maximum number of traces the OMC-R can support is 40,000.

OMC-R Online Help, Network Operations describes how to initiate and manage a standard call
trace using the OMC-R GUI and TTY interface.

Controlling an MSC initiated call trace

The call_trace_options parameter enables or disables MSC initiated call traces for the entire
BSS. The value of the call_trace_options parameter indicates the percentage of traces to be
reserved exclusively for use by MSC initiated traces on a per-LCF basis.
Entering a value between 0 and 100 indicates the percentage of traces reserved for MSC
initiated traces on a per LCF basis. Entering a value of 255 indicates that MSC traces are
blocked (barred). The default value is 0.

Example 1
To enable the MSC call trace feature and set the percentage of traces reserved for MSC initiated
traces to 1 percent, enter the command:
chg_element call_trace_options 1 0
If the command is executed successfully, the following is displayed:
COMMAND ACCEPTED

Example 2
To bar the MSC call trace feature, enter the command:
chg_element call_trace_options 255 0
If the command is executed successfully, the following is displayed:
COMMAND ACCEPTED

2-60

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Naming of call trace log files

Example 3
To display the current setting of the call_trace_options parameter, enter the command:
disp_element call_trace_options 0
If the command is executed successfully, the following is displayed:
call_trace_options = 1

Naming of call trace log files

Each logfile name includes a timestamp consisting of the day of the month, the hour, the minute
and the second at which the logfile was created. This is to cater to situations where a call
which is being traced goes outside the scope of that trace (moves from one cell to another)
and re-enters the original scope.

GSM Trace Log file

The naming convention for the GSM Call Trace Log file is modified. The file name is in the
following format:
ct_<SourceID>_<BSSID>_<BSSVersion>_<TraceReference>_<SCCPNumber>.<timestamp>
A few examples of file naming conventions are as follows:
ct_MSC_0000000023_1900_00257_0933472.28175502
ct_MMI_0000000005_1800_00508_1132800.23181320
ct_OMC_0000000222_1760_00009_0531712.14155138

NOTE

68P02901W17-T

A timestamp consists of the following fields: <date><hour><min><sec>,

where each field consists of 2 digits. The <date> field indicates a number
between 1 and 31.

If the OMC-R fails to get the version of a BSS, it inserts 0000 in place of the
BSSVersion.

2-61
Jan 2010

Naming of call trace log files

Chapter 2: Configuring BSS Features

GPRS Trace Log file

The naming convention for the GPRS Trace Log file is modified. The file name is in the following
format:
gt_<SourceID>_<BSSID>_<BSSVersion>_<TraceReference>_<PcuId>_<TLLI>.<timestamp>
A few examples of file naming conventions are as follows:
gt_MMI_0000000003_1900_00004_0_e8003d7d.16165815
gt_OMC_0000000002_1800_00010_0_c0f0a94d.17114120

NOTE

2-62

A timestamp consists of the following fields: <date><hour><min><sec>,

where each field consists of 2 digits. The <date> field indicates a number
between 1 and 31.

If the OMC-R fails to get the version of a BSS, it inserts 0000 in place of the
BSSVersion.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Call trace flow control

Call trace flow control

Overview of call trace flow control

Call traces can generate large and excessive amounts of trace data, which can load other parts
of the system. OMC-R Online Help, Network Operations describes how to initiate and manage a
standard call trace using the OMC-R GUI and TTY interface.
Call trace flow control is a mechanism that reduces the number of call traces that can be
initiated. The BSS enables or disables call trace flow control by monitoring the OML buffer
availability. When the Operations and Maintenance Link (OML) buffer reaches a predefined user
level, the BSS enables or disables call trace flow control. When enabled the BSS temporarily
suspends the triggering and the dynamic adjustment of the call trace criteria by the BSS.
The BSS displays the current call trace flow control setting in the BSS Detailed View window.
When call trace flow control is disabled (default), a user can initiate call traces from a BSS,
SITE, CELL, or RTF. When call trace flow control is enabled, a user cannot initiate a call trace
from a BSS, SITE, CELL, or RTF. If a user attempts this procedure, the OMC-R displays an error
message in the status bar.

NOTE
When a BSS is reset, call trace flow control is set to Disabled (0).
MSC traces are generally considered to be of greater importance than other types of traces, and
are less likely to collect excessive trace data than, for example, nth call traces. MSC traces only
exist for the life of the call upon which they were invoked. For this reason, call traces initiated
from an MSC can be enabled or disabled, when the call trace flow control is enabled.

Call trace flow control parameters

Table 2-10 shows the parameters associated with Call Trace Flow Control. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For
further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).

68P02901W17-T

2-63
Jan 2010

Call trace flow control parameters

Chapter 2: Configuring BSS Features

Table 2-10 Call trace flow control parameters

OMC-R GUI field name/BSS
parameter name

Description

Valid Input

Flow Control by BSS

ct_flow_control_bss_
enabled
(OMC-R parameter name:
ct_fc_bss_enabled)

Displayed in the GSM/GPRS Trace

Information grouping of the BSS Detailed
View.
Automatically set by the BSS when the
ct_fc_hi_level or ct_fc_lo_level is reached
(see below).
Displays whether a user can initiate a call
trace from a BSS, SITE, CELL or RTF. This
parameter is set to 0 (zero) when the BSS
is reset.
This field cannot be modified by a user.

0 to 2.
Disabled (0):
meaning a user
can initiate a call
trace from a BSS,
site, cell or RTF.
Enabled (1):
meaning a user
cannot initiate a
call trace from a
BSS, site, cell or
RTF.
Halted (2).
Default is
Disabled (0).

Flow Control High Threshold

ct_flow_control_hi_level
(OMC-R parameter name:
ct_fc_hi_level)

Displayed in the GSM/GPRS Trace

Information grouping of the BSS Detailed
View.
Specifies the percentage of the call
trace OML buffer space that has to be
used before flow control is automatically
enabled. When this limit is reached,
ct_fc_bss_enabled is automatically set
to Enabled (1). This parameter must be
greater than or equal to ct_fc_lo_level plus
20.
Setting this parameter to 100% effectively
disables call trace flow control.

20 to 100.
Default is 60%.

Flow Control Low Threshold

ct_flow_control_lo_level
(OMC-R parameter name:
ct_fc_lo_level)

Displayed in the GSM/GPRS grouping of

the BSS Detailed View.
Specifies the percentage of the call
trace OML buffer space that has to be
used before flow control is automatically
disabled. When this limit is reached,
ct_fc_bss_enabled is automatically set to
Disabled (0). This parameter must be less
than or equal to ct_fc_hi_level minus 20.
For example, if ct_fc_hi_level is set to 75%
and ct_fc_lo_level is set to 25%, call trace
flow control is automatically enabled when
the OML buffer capacity reaches 75%,
and call trace flow control is automatically
disabled when the OML buffer capacity
reaches 25%.

0 to 80.
Default is 20%.

Continued

2-64

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 2-10

Methods of configuring call trace flow control

Call trace flow control parameters (Continued)

OMC-R GUI field name/BSS

parameter name
Apply Flow Control to MSC
Trace
ct_flow_control_msc_
enabled
(OMC-R parameter name:
ct_fc_msc_trace)

Description
Displayed in the GSM/GPRS Trace
Information grouping of the BSS Detailed
View.
Enables or disables the initiation of call
traces from an MSC, when call trace flow
control is enabled. For example, when
BSS, SITE, CELL, and RTF call traces are
prevented using ct_fc_bss_enabled = 1,
MSC initiated call traces can be initiated
when ct_fc_msc_trace is set to Disabled (0).
This parameter can only operate when
call trace flow control is enabled, that is,
ct_fc_bss_enabled is set to 1, and MSC
traces have not been barred using the
call_trace_options parameter.

Valid Input
Disabled (0):
meaning that
MSC traces are
allowed while
flow control is
enabled.
Enabled (1):
meaning that
MSC traces are
not allowed
while flow
control is
enabled.
Default is
Disabled (0).

Methods of configuring call trace flow control

Call trace flow control can be configured using either of the following methods:

OMC-R GUI BSS Detailed View and the fields detailed in Table 2-10.

TTY interface, see Configuring Call Trace Flow Control using the TTY interface.

Configuring call trace flow control using the TTY interface

Configuring call trace flow control using chg_element
To configure the call trace flow control, use the chg_element command and the appropriate call
trace flow control parameter as shown in Table 2-10.
See Technical Description: BSS Command Reference (68P02901W23) for further details of BSS
commands and parameters.

Setting the high level of the OML buffer

To set the level of the OML buffer at which the BSS enables call trace flow control, use the
chg_element command and the ct_fc_hi_level parameter. For example, the following
command sets the OML at 85%:
chg_element ct_fc_hi_level 85

68P02901W17-T

2-65
Jan 2010

Configuring call trace flow control using the TTY interface

Chapter 2: Configuring BSS Features

Setting the low level of the OML buffer

To set the level of the OML buffer at which the BSS disables call trace flow control, use the
chg_element command and the ct_fc_lo_level parameter. For example, the following
command sets the OML at 60%:
chg_element ct_fc_lo_level 60

Disabling MSC call trace flow control

To allow call traces to be initiated from an MSC only, when call trace flow control is enabled, use
the chg_element command and the ct_fc_msc_trace parameter. For example, to enable MSC
call traces, disable MSC Call Trace Flow Control using in the following command:
chg_element ct_fc_msc_trace 0

Enabling MSC call trace flow control

To prevent call traces being initiated at an MSC, when call trace flow control is enabled, use the
chg_element command and the ct_fc_msc_trace parameter. For example, to prevent MSC call
traces, enable MSC call trace flow control use the following command:
chg_element ct_fc_msc_trace 1

Displaying call trace flow control using the TTY interface

To display the call trace flow control settings, use the disp_element command and the
appropriate call trace flow control parameter as shown in Table 2-10.
To display the level of the OML buffer at which the BSS enables call trace flow control, for
example, enter the following command:
disp_element ct_fc_hi_level
The system responds:
ct_flow_control_hi_level = 85%
To display the level of the OML buffer at which the BSS disables call trace flow control, use the
following command:
disp_element ct_fc_ho_level
The system responds, for example:
ct_flow_control_hi_level = 60%
To display whether MSC call trace flow control is enabled, use the following command:
disp_element ct_fc_msc_trace
The system responds, for example:
ct_flow_control_msc_trace = 0

2-66

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring call trace flow control using the TTY interface

Displaying whether call trace flow control is enabled, disabled, or halted

To display whether call trace flow control is enabled or disabled, use the following command:
disp_element ct_fc_bss_enabled
The system responds, for example: ct_flow_control_bss_enabled = 0

68P02901W17-T

2-67
Jan 2010

GPRS Trace

Chapter 2: Configuring BSS Features

GPRS Trace

Feature Description
The GPRS Trace feature is an extension of the existing GSM Call Trace implementation. The
GPRS Trace feature enables users to trace information on GPRS MSs. It provides similar
functionality to GSM Call Trace.
GPRS Trace differs from GSM Call Trace in the following respects:

GPRS signaling is more frequent due to the bursty packet nature of GPRS data transfers.

GPRS MSs may leave a cell without informing the BSS. Therefore, the continue beyond
scope option is not applicable in GPRS Trace. However, for ease of implementation, a
continue beyond scope value is always included in the trace Create action. This value is
ignored by the BSS, if the trace type is GPRS.

For GPRS Trace, the lifetime of an invoked trace corresponds to the lifetime of a GPRS
MS meeting the GPRS Trace criteria within a PCU. A number of GPRS data transfers
may occur within this period. Due to cell reselection, a GPRS MS may leave the scope of
the criteria and/or the PCU without prior warning. When the PCU detects that a GPRS
MS has left, the invoked trace ends. Since cell reselection can take up to 15 seconds,
the PCU waits 15 seconds for the MS to reappear before ending the invoked trace. This
differs from GSM Call Trace, where the lifetime of an invoked trace and corresponding log
file corresponds to a single call.

GPRS Trace is created and managed from the OMC and BSS MMI only.

NOTE
Unlike GSM Call Trace, creation of GPRS Trace criteria is not supported from the
MSC. GPRS Trace Records are forwarded to the NMC.
The GPRS trace create criteria includes:

2-68

Trace scope options for GPRS Trace: BSS, site, Cell, RTF (as for GSM).

Trace selector options for GPRS Trace: IMSI (International Mobile Subscriber Identity).

TLLI (Temporary Logical Link Identity), Nth GPRS MS.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Feature Description

GPRS Trace Record type: Basic or Radio. If Radio is selected, the user may select some or
all of the following:
LLC (Logical Link Control) information.
BSSGP (BSS GPRS protocol) messages.

RLC/MAC (Radio link control / Medium Access Control) messages.

GPRS Power Control and Coding Scheme, including UL/DL measurement data.
Packet Measurement Reports.
Every RLC/MAC PDAK.

Trace start/stop times.

Total number of GPRS MSs to be traced.

NOTE
This information is counted per-PRP. The trace criteria are complete at the
BSS, when the total number of MSs have been traced for at least one PRP. The
overall number of MSs traced during this period may exceed the total number
setting. This behavior is like the counting of total number of calls at the LCF
level for Call Trace.

Measurement interval: This value applies for Packet Measurement Reports and UL/DL
Measurement data.

Maximum number of simultaneous MSs to be traced (applicable only if Trace selector

is set to Nth GPRS MS).

NOTE
This information is counted per-PRP. Therefore, the number of simultaneous calls at
any specific time may exceed the maximum number setting.
The user may request a combined trace of both GSM and GPRS information in the specific
case of an IMSI trace selector. In this case, the BSS forwards trace records relating to both
GSM calls and GPRS data transfers for that IMSI. GSM and GPRS trace information is written
to separate log files.

68P02901W17-T

2-69
Jan 2010

Enhanced Circuit Error Rate Monitor (ECERM)

Chapter 2: Configuring BSS Features

Enhanced Circuit Error Rate Monitor (ECERM)

Overview of ECERM
Enhanced Circuit Error Rate Monitor (ECERM) monitors the continuity of circuits. A circuit
is a path along which the connection is made from the entry point in the BSS to the exit point
in the BSS.
Enhanced Circuit Error Rate Monitor (ECERM) is an enhancement to the existing Circuit Error
Rate Monitor feature (see OMC-R Online Help, Network Operations for details). ECERM
increases the number of monitor points along the circuit path to narrow down the identification
of potentially faulty devices. ECERM does not confirm that a device is faulty; the user must
determine this.
The circuit path points monitored by CERM are:

CIC (Circuit Identity Code) - a timeslot on the link between the RXCDR or BSC and the MSC.

RCI (Radio Channel Identifier) - the radio hardware.

In addition to these points, ECERM also monitors the following new points:

ACI (Ater Channel Identifier) - the timeslot group on the link between the RXCDR and
the BSC.

PIC (Path Identity Code) - the timeslot in the link between the BSC and the BTS.

GCI (GPRS Circuit Identifier) - a timeslot on the link between the BSC and the PCU.

These points are monitored on a per-timeslot basis.

For a full description of ECERM, see Technical Description: BSS Implementation
(68P02901W36). For details of the alarms generated by CERM and the ECERM feature, see
Maintenance Information: Alarm Handling at the OMC-R (68P02901W26).

Prerequisites to configuring ECERM

Before configuring ECERM, ensure that the following features have been enabled:

ECERM (ecermOpt parameter).

GPRS (gprsOpt parameter).

Table 2-11 indicates which ECERM parameters require these parameters to be enabled. For
example, existing CERM parameters cannot be restricted.

2-70

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Determining whether ECERM has been enabled

Determining whether ECERM has been enabled

ECERM is an optional feature, which must be enabled before it can be used.

Using the OMC-R GUI

To check if ECERM has been enabled using the OMC-R GUI, display the setting of the Enhanced
CERM Feature field in the Optional Features grouping in the BSS Detailed View. The values
for ecermOpt are:

Disabled (0).

Enabled (1).

The default is Disabled (0).

Using the TTY interface

To check if ECERM has been enabled using the TTY interface, enter the following command:
disp_options all
If the ECERM optional feature has been enabled, and is therefore unrestricted, the system
displays the following in the unrestricted list: <43> Enhanced Circuit Error Rate Monitor

ECERM parameters
Table 2-11 details the ECERM parameters. Unless stated otherwise, the OMC-R parameter
name is usually the same as the BSS parameter name. For further details of these and other
parameters, see Technical Description: BSS Command Reference (68P02901W23).

Table 2-11 ECERM parameters

OMC-R GUI field name/BSS
parameter name

Description

BSS parameters:
ECERM Feature (OMC-R
parameter name:
ecermOpt)

Displayed in the Optional Features grouping in the BSS

Detailed View.
Indicates whether the ECERM feature is enabled. Valid
values are 0 or 1, where:

0 - Disabled.

1 - Enabled.
Continued

68P02901W17-T

2-71
Jan 2010

ECERM parameters

Chapter 2: Configuring BSS Features

Table 2-11 ECERM parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

CIC Error Gen Threshold

cic_error_gen_thresh

Displayed in the Circuit Error Rate Monitor grouping in

the BSS Detailed View.
Specifies the CIC error count threshold at the BSC.
Once this threshold is reached, further CIC errors do
not increase the CIC error count. When this threshold is
reached or exceeded a CIC alarm is generated.
Valid range: 2 - 255.
Default value: 6.
If a user changes the threshold value, an alarm is not
immediately generated. The new threshold only takes
effect when the CIC error count changes.
This parameter must be two greater than
cic_error_clr_thresh.

CIC Error Clear Threshold

cic_error_clr_thresh

Displayed in the Circuit Error Rate Monitor grouping in

the BSS Detailed View.
Specifies the CIC error count clearing threshold at the
BSC. When the error count reaches or falls below this
threshold the alarm clears.
Valid range: 0 - 253.
Default value: 0.
Must be two less than cic_error_gen_thresh.

CIC Error Increment

cic_error_inc

Displayed in the Circuit Error Rate Monitor grouping in

the BSS Detailed View.
Specifies the CIC error increment value. The system
updates the CIC error count by this value whenever an
error is detected.
Valid range: 0 (Disabled) - 255.
Default value: 1.
If a user sets the value to 0, an error message is displayed
indicating that no more CIC alarms will be generated.

ACI Error Gen Threshold

aci_error_gen_
thresh
(OMC-R parameter name:
aciErrGenThresh).

Displayed in the Enhanced Circuit Error Rate Monitor

grouping in the BSS Detailed View.
Specifies the ACI error count threshold at the BSC.
Once this threshold is reached, further ACI errors do
not increase the ACI error count. When this threshold is
reached or exceeded, an ACI alarm is generated.
Valid values: 2 - 255.
Default value: 6.
If a user changes the threshold value, an alarm is not
immediately generated. The new threshold only takes
effect when the ACI error count changes.
Grayed-out if the ECERM Feature (ecermOpt) is disabled.
Exists only at a BSC.
Continued

2-72

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

ECERM parameters

Table 2-11 ECERM parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

ACI Error Clear Threshold

aci_error_clr_
thresh
(OMC-R parameter name:
aciErrClrThresh).

Displayed in the Enhanced Circuit Error Rate Monitor

grouping in the BSS Detailed View.
Specifies the value which the error count must be equal
to or less than for an ACI alarm to be cleared.
Valid values: 0 - 253.
Default value: 0.
If a user changes the threshold value, an alarm is not
immediately cleared. The new threshold only takes effect
when the ACI error count changes.
Grayed-out if the ECERM Feature (ecermOpt) is disabled.
Exists only at a BSC.

ACI Error Increment

aci_error_inc
(OMC-R parameter name:
aciErrorInc)

Displayed in the Enhanced Circuit Error Rate Monitor

grouping in the BSS Detailed View.
Specifies the ACI error increment value. The system
updates the ACI error count by this value whenever an
error is detected.
Valid range: 0 (Disabled) - 255.
Default value: 1.
If a user sets the value to 0, an error message is displayed
indicating that no more ACI alarms will be generated.
Set to 0, if the ECERM feature is disabled.
Grayed-out if the ECERM Feature (ecermOpt) is disabled.
Exists only at a BSC.

GCI Error Gen Threshold

gci_error_gen_thresh
(OMC-R parameter name:
gciErrGenThresh)

Displayed in the Enhanced Circuit Error Rate Monitor

grouping in the BSS Detailed View.
Specifies the GCI error count threshold at the BSC.
Once this threshold is reached, further GCI errors do
not increase the GCI error count. When this threshold is
reached or exceeded a GCI alarm is generated.
Valid values: 2 - 255. Default value: 6.
If a user changes the threshold value, an alarm is not
immediately generated. The new threshold only takes
effect when the GCI error count changes.
Grayed-out if the GPRS Feature (gprsOpt) or ECERM
Feature (ecermOpt) is disabled. Exists only at a BSC.

GCI Error Clear Threshold

gci_error_clr_thresh
(OMC-R parameter name:
gciErrClrThresh)

Displayed in the Enhanced Circuit Error Rate Monitor

grouping in the BSS Detailed View.
Specifies the value which the error count must be equal
to or less than for a GCI alarm to be cleared.
Valid values: 0 - 253.
Default value: 0.
If a user changes the threshold value, an alarm is not
immediately cleared. The new threshold only takes effect
when the GCI error count changes.
Grayed-out if the GPRS Feature (gprsOpt) or ECERM
Feature (ecermOpt) is disabled.
Exists only at a BSC.
Continued

68P02901W17-T

2-73
Jan 2010

ECERM parameters

Chapter 2: Configuring BSS Features

Table 2-11 ECERM parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

GCI Error Increment

gci_error_inc
(OMC-R parameter name:
gciErrorInc)

Displayed in the Enhanced Circuit Error Rate Monitor

grouping in the BSS Detailed View.
Specifies the GCI error increment value. The system
updates the GCI error count by this value whenever an
error is detected.
Valid range: 0 (Disabled) - 255.
Default value: 1.
If a user set the value to 0, an error message is displayed
indicating that no more GCI alarms will be generated.
Set to 0, if either the GPRS or ECERM feature is disabled.
Grayed-out if the GPRS Feature (gprsOpt) or ECERM
Feature (ecermOpt) is disabled.
Exists only at a BSC.

GPRS Alarm Time

gprs_alarm_time
(OMC-R parameter name:
gprsAlarmTime)

Displayed in the Enhanced Circuit Error Rate Monitor

grouping in the BSS Detailed View.
Specifies the time period in which the error counters are
incremented if an error indication is received for a GCI,
or decremented if no error indication is received.
Valid values: 0 (Disabled), 5 - 240 seconds.
Default values:

60, when GPRS and ECERM are enabled.

0, if either GPRS or ECERM is disabled.

Grayed-out if the GPRS Feature (gprsOpt) or ECERM

Feature (ecermOpt) is disabled. Exists only at a BSC.
PIC Error Gen Threshold
pic_error_gen_thresh
(OMC-R parameter name:
picErrGenThresh)

Displayed in the Enhanced Circuit Error Rate Monitor

grouping in the BSS Detailed View.
Specifies the PIC error count threshold at the BSC. Once
this threshold is reached, further PIC errors do not
increase the PIC error count. When this threshold is
reached or exceeded a PIC alarm is generated.
Valid values: 2 - 255.
Default value: 6.
If a user changes the threshold value, an alarm is not
immediately generated. The new threshold only takes
effect when the PIC error count changes.
Grayed-out if the ECERM Feature (ecermOpt) is disabled.
Exists only at a BSC.
Continued

2-74

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

ECERM parameters

Table 2-11 ECERM parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

PIC Error Clear Threshold

pic_error_clr_thresh
(OMC-R parameter name:
picErrClrThresh)

Displayed in the Enhanced Circuit Error Rate Monitor

grouping in the BSS Detailed View.
Specifies the value which the error count must be equal
to or less than for a PIC alarm to be cleared.
Valid values: 0 - 253.
Default value: 0.
If a user changes the threshold value, an alarm is not
immediately cleared. The new threshold only takes effect
when the PIC error count changes.
Grayed-out if the ECERM Feature (ecermOpt) is disabled.
Exists only at a BSC.

PIC Error Increment

pic_error_inc
(OMC-R parameter name:
picErrorInc)

Displayed in the Enhanced Circuit Error Rate Monitor

grouping in the BSS Detailed View.
Specifies the PIC error increment value. The system
updates the PIC error count by this value whenever an
error is detected.
Valid range: 0 (Disabled) - 255.
Default value: 1.
If a user set the value to 0, an error message is displayed
indicating that no more PIC alarms will be generated.
Set to 0, if the ECERM feature is disabled.
Grayed-out if the ECERM Feature (ecermOpt) is disabled.
Exists only at a BSC.

RCI Error Gen Threshold

rci_error_gen_thresh

Displayed in the Circuit Error Rate Monitor grouping in

the BSS Detailed View.
Specifies the RCI error count threshold at the BSC.
Once this threshold is reached, further RCI errors do
not increase the RCI error count. When this threshold is
reached or exceeded, an RCI alarm is generated.
Valid range: 2 - 255.
Default value: 6.
If a user changes the threshold value, an alarm is not
immediately generated. The new threshold only takes
effect when the RCI error count changes.
Must be two greater than rci_error_clr_thresh.

RCI Error Clear Threshold

rci_error_clr_thresh

Displayed in the Circuit Error Rate Monitor grouping in

the BSS Detailed View form.
Specifies the Radio Channel Identifier (RCI) error count
clearing threshold at the BSC. When the error count
reaches or falls below this threshold the alarm clears.
Valid range: 0 - 253.
Default value: 0.
Must be two less than rci_error_gen_thresh.
Continued

68P02901W17-T

2-75
Jan 2010

Methods for configuring ECERM

Chapter 2: Configuring BSS Features

Table 2-11 ECERM parameters (Continued)

OMC-R GUI field name/BSS
parameter name
RCI Error Increment
rci_error_inc

Description
Displayed in the Circuit Error Rate Monitor grouping in
the BSS Detailed View.
Specifies the Radio Channel Identifier (RCI) error
increment value. The system updates the RCI error count
by this value whenever an error is detected.
Valid range: 0 (Disabled) - 255.
Default value: 1.
If a user set the value to 0, an error message is displayed
indicating that no more RCI alarms will be generated.

SITE parameters:
Initial Sync Timer (msec)
initial_sync_timer
(OMC-R parameter name:
initSyncTimer)

Displayed in the Circuit Error Rate Monitor grouping in

the SITE Detailed View.
This parameter is supported at BTS sites.
If a user changes this parameter, a warning message is
displayed indicating that a site reset occurs when the
value is saved.

Uplink Sync Timer (msec)

uplink_sync_timer
(OMC-R parameter name:
ulSyncTimer)

Displayed in the Circuit Error Rate Monitor grouping in

the SITE Detailed View.
This parameter is supported at BTS sites.
If a user changes this parameter, a warning message is
displayed indicating that a site reset occurs when the
value is saved.

Downlink Sync Timer (msec)

downlink_sync_timer
(OMC-R parameter name:
dlSyncTimer)

Displayed in the Circuit Error Rate Monitor grouping in

the SITE Detailed View form.
This parameter is supported at BTS sites.
If a user changes this parameter, a warning message is
displayed indicating that a site reset occurs when the
value is saved.

Static Sync Timer

static_sync_timer

Displayed in the GPRS grouping in the SITE Detailed

View.
This parameter is supported at BTS sites.
If a user changes this parameter, a warning message is
displayed indicating that a site reset occurs when the
value is saved.
Valid values: 1 - 65535, when the GPRS Feature is
enabled. Default value: 0, when the GPRS feature is
disabled.
Grayed-out in the SITE 0 Detailed View if the GPRS
Feature (gprsOpt) is disabled.

Methods for configuring ECERM

The ECERM feature can be configured using:

2-76

OMC-R GUI, using the BSS Detailed View (Circuit Error Rate Monitor grouping), and SITE
Detailed View (Circuit Error Rate Monitor grouping), and the fields detailed in Table 2-11.

TTY interface, see Configuring ECERM using the TTY interface.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring ECERM using the TTY interface

Configuring ECERM using the TTY interface

Using chg_ and disp_element commands
The chg_element and disp_element commands can be used to configure and change the
ECERM parameters shown in Table 2-11. Some examples are also given in the following
sections. See Technical Description: BSS Command Reference (68P02901W23) for full details of
BSS commands, prompts, and parameters.

Displaying the current GPRS alarm increment/decrement period

Use the disp_element command to display the current GPRS Alarm Increment/Decrement
Period parameter of the BSC. For example, the following command displays the current setting
at the BSC:
disp_element gprs_alarm_time 0
The system replies, for example: gprs_alarm_time = 30

Setting the GPRS alarm increment/decrement period

Use the chg_element command to change the GPRS Alarm Increment/Decrement Period
parameter. For example, the following command changes the GPRS Alarm Increment/Decrement
Period parameter to 40 at the BSC:
chg_element gprs_alarm_time 40 0
COMMAND ACCEPTED

Changing the initial sync timer parameter

Use the chg_element command to change the Initial Sync Timer parameter. For example, the
following command changes the Initial Sync Timer to 2000 at the BSC:
chg_element initial_sync_timer 2000 0
The system responds with the following prompts for further information (bold text shows typical
user responses):
Enter value for downlink sync timer: 1000
Enter value for uplink sync timer: 1000
Enter value for static sync timer: 1000
WARNING: Changing initial_sync_timer will cycle device SITE.
Are you sure (y = yes, n = no)? y
COMMAND ACCEPTED

68P02901W17-T

2-77
Jan 2010

Advanced Load Management for EGSM

Chapter 2: Configuring BSS Features

Advanced Load Management for EGSM

Introduction to Advanced Load Management for EGSM

The Advanced Load Management (ALM) for EGSM feature is an optional feature. It enables an
EGSM mobile to handover to an EGSM resource on a neighboring cell rather than allowing it to
be handed over to a neighboring cell which may not contain EGSM carriers.
Before the introduction of the Advanced Load Management for EGSM feature, EGSM carriers in
a PGSM/EGSM and DCS1800 multiband network were under utilized because of the interaction
with the multiband handover feature. A typical example of this is when an EGSM mobile is
established on a PGSM cell (which has EGSM capabilities) and the neighbor cell uses the
Multiband Handover feature with the band preference set to DCS1800, and the band preference
mode set to 4. If there is idle EGSM TCH capacity, the mobile is assigned to the EGSM TCH
resource and when a handover is triggered, the mobile is targeted to the DCS 1800 band. The
result is EGSM resources are under utilized.
To allow EGSM resources to be fully utilized, the Advanced Load Management for EGSM feature
uses an EGSM targeting algorithm which the operator can enable in the BSS software. The
EGSM targeting algorithm selects an internal EGSM capable neighbor cell, rather than a
non-EGSM cell, when a handover is triggered.
For a full description of Advanced Load Management for EGSM, see Technical Description: BSS
Implementation (68P02901W36).

Restrictions and dependencies to ALM for EGSM

Before Advanced Load Management for EGSM can be enabled, there must not be any:

Coincident multiband cells.

EGSM BCCH frequencies.

Hopping through EGSM frequencies within a PGSM/EGSM cell.

Also external handovers assume that a cell with PGSM BCCH is a PGSM only cell.

Interaction with other features

This feature interacts with the IMRM feature, see for further details.

2-78

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

ALM for EGSM parameters

ALM for EGSM parameters

Table 2-12 details the parameters associated with configuring Advanced Load Management for
EGSM. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS
parameter name. For further details of these and other parameters, see Technical Description:
BSS Command Reference (68P02901W23).

Table 2-12 Advanced Load Management for EGSM parameters

OMC-R GUI field name/BSS
parameter name
ALM Enhancement for EGSM
Carriers (OMC-R parameter
name:
AlmEgsmOpt)

BSS EGSM ALM ALLOWED

bss_egsm_alm_allowed
(OMC-R parameter name:
egsm_alm_allowed)

Description
Displayed in the Optional Features grouping of the
BSS Detailed View. Indicates whether Advanced Load
Management for EGSM feature is unrestricted at the BSS.
Valid values: 0 or 1, where:

0 - Disabled (restricted).

1 - Enabled (unrestricted).

Displayed in the General grouping of the BSS Detailed View.

Indicates whether Advanced Load Management for EGSM is
enabled or disabled at the BSS. Valid values: 0 or 1, where:

0 - Disabled.

1 - Enabled.

This field is grayed-out if the field: ALM Enhancement for

EGSM Carriers (parameter name:AlmEgsmOpt) has been
set to Disabled (0).

Methods of configuring ALM for EGSM

ALM for EGSM can be configured using:

OMC-R GUI BSS Detailed View and the fields shown in Table 2-12.

TTY interface, see Configuring ALM for EGSM using the TTY interface.

Configuring ALM for EGSM using the TTY interface

Displaying current setting of ALM for EGSM using the TTY interface
To display the current setting for Advanced Load Management for EGSM feature (that
is, whether it is restricted or unrestricted at the BSS) using the TTY interface, use the
disp_element command. For example:
disp_element bss_egsm_alm_allowed bsc
If Advanced Load Management for EGSM is unrestricted (enabled), the system displays:
bss_egsm_alm_allowed = 1
68P02901W17-T

2-79
Jan 2010

Configuring ALM for EGSM using the TTY interface

Chapter 2: Configuring BSS Features

If Advanced Load Management for EGSM is restricted (disabled), the system displays:
bss_egsm_alm_allowed = 0

Enabling and disabling ALM for EGSM using the TTY interface
To modify the current setting for Advanced Load Management for EGSM (that is, to enable or
disable the feature at the BSS) using the TTY interface, use the chg_element command and the
bss_egsm_alm_allowed parameter. The feature can only be enabled at the BSC. For example,
the following command enables Advanced Load Management for EGSM at a BSC:
chg_element bss_egsm_alm_allowed 1 bsc

2-80

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Network Controlled Cell Reselection

Network Controlled Cell Reselection

Description of Network Controlled Cell Reselection (NCCR)

In a GPRS network, cell reselection is the equivalent of a GSM circuit switched handover.
In general, as the location of a mobile or RF conditions change, or cells get congested, cell
reselection offers mobility and performs network traffic management. The different modes of
cell reselection in GPRS network are referred to as:

NC0.

NC1.

NC2.

RESET.

The main objective of Network Controlled Cell Reselection (NCCR) and congestion relief is to
increase network capacity and provide a tool for network planning and improved quality of
service. The operator can specify GPRS cell reselection mode on a per cell basis providing the
flexibility of virtual zones within the network of cells with same cell reselection order.
Table 2-13 details the cell reselection modes offered by Motorola.

Table 2-13 GPRS cell reselection modes

Cell Reselection
Mode

Responsible
Network Element

Functionality

NC0

MS control

Normal GPRS mobile control. The mobile performs

autonomous cell reselection based on the radio
environment.

Enhanced NC0

MS control

Includes all functionality provided by NC0 mode.

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

NC1

MS control

GPRS mobile control with measurement reports to

the BSS. MS performs autonomous cell reselection.

Enhanced NC1

MS control

All functionality in NC1 mode. BSS sends cell

reselection command to GPRS mobile to change cell
reselection mode.

NC2

Network control

Network control. GPRS MS sends measurement

reports to the BSS. BSS sends cell reselection
commands and instructs mobile to perform cell
reselection.

For a full description of NCCR, see Technical Description: BSS Implementation (68P02901W36).

68P02901W17-T

2-81
Jan 2010

Determining whether Network Controlled Cell Reselection (NCCR) is enabled

Chapter 2: Configuring BSS Features

Determining whether Network Controlled Cell Reselection

(NCCR) is enabled
NCCR is an optional feature, which must be unrestricted for a BSS in order for it to be used.
If NCCR is enabled, the GPRS option must also be enabled.

Using the OMC-R GUI

To check if NCCR is restricted or unrestricted, using the OMC-R GUI, display the setting of the
Network Controlled Cell Reselection Feature field in the Optional Features grouping in the BSS
Detailed View. The values for nccrOpt are:

Disabled (0).

Enabled (1).

Default is Disabled (0).

This field cannot be changed by a user.

Using the TTY interface

To check if NCCR is unrestricted using the TTY interface, enter the following command:
disp_options all
If the NCCR optional feature is unrestricted, the system displays the following in the
unrestricted list:
43 Network Controlled Cell Reselection

Network Controlled Cell Reselection parameters

Table 2-14 details the Network Controlled Cell Reselection parameters. Unless stated otherwise,
the OMC-R parameter name is usually the same as the BSS parameter name. For further
details of these and other parameters, see Technical Description: BSS Command Reference

(68P02901W23).

2-82

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 2-14

Network Controlled Cell Reselection parameters

Network Controlled Cell Reselection parameters

OMC-R GUI field name/BSS

parameter name

Description

NCCR Enabled
nccr_enabled

Displayed in the Network Controlled Cell Reselection grouping

in the BSS Detailed View form.
Indicates whether the Network Controlled Cell Reselection
feature is Enabled (1) or Disabled (0). The default is Disabled
(0).
This field can be modified by a user.
This field is grayed-out if the BSS Detailed View field: Network
Controlled Cell Reselection Feature (parameter name:
nccrOpt) is set to Disabled (0).

NC Reporting Period Idle

nc_reporting_period_i

Displayed in the Network Controlled Cell Reselection grouping

in the BSS Detailed View form.
Indicates the time interval between successive measurement
reports from a GPRS MS to the BSS when the MS is idle.
Valid values are: 4 - 6, where:
4 - 15.36 seconds
5 - 30.72 seconds
6 - 61.44 seconds
The default is 6, that is, 61.44 seconds.
This field is grayed-out if the BSS Detailed View field: Network
Controlled Cell Reselection Feature (parameter name:
nccrOpt) is set to Disabled (0).

NC Non Drx Period

nc_non_drx_period

Displayed in the Network Controlled Cell Reselection grouping

in the BSS Detailed View form.
Indicates the time interval the BSS expects the MS to read the
paging channel (CCCH) for a control message (PCCO).
Valid values are: 0 - 7, where:
0 - No non_drx_period after a measurement report has been
sent.
1 - 0.24 seconds
2 - 0.48 seconds
3 - 0.72 seconds
4 - 0.96 seconds
5 - 1.20 seconds
6 - 1.44 seconds
7 - 1.92 seconds
The default is 2, that is, 0.48 seconds.
This field is grayed-out if the BSS Detailed View field: Network
Controlled Cell Reselection Feature (parameter name:
nccrOpt) is set to Disabled (0).
Continued

68P02901W17-T

2-83
Jan 2010

Network Controlled Cell Reselection parameters

Chapter 2: Configuring BSS Features

Table 2-14 Network Controlled Cell Reselection parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

NC Reporting Period
Transfer
nc_reporting_period_t

Displayed in the Network Controlled Cell Reselection grouping

in the BSS Detailed View form.
Indicates the time interval between successive measurement
reports from a GPRS MS to the BSS when the MS is transferring
packet data.
Valid values are: 0 - 6, where:
0 - 0.96 seconds
1 - 1.92 seconds
2 - 3.84 seconds
3 - 7.68 seconds
4 - 15.36 seconds
5 - 30.72 seconds
6 - 61.44 seconds
The default is 2, that is, 3.84 seconds.
This field is grayed-out if the BSS Detailed View field: Network
Controlled Cell Reselection Feature (parameter name:
nccrOpt) is set to Disabled (0).

Network Control Order

network_control_order
(OMC-R parameter name:
netwk_ctrl_order)

Displayed in the General - Cell Selection-Reselection grouping

in the CELL Detailed View form.
Indicates the network entity responsible for cell reselection.
Valid values are: 0 - 4, where:
0 - NC0
1 - NC1
2 - NC2
3 - Enhanced NC0
4 - Enhanced NC1
The default is 0.
This parameter can be modified regardless of whether the cell
is GPRS enabled/disabled.
This field is grayed-out if the BSS Detailed View field: Network
Controlled Cell Reselection Feature (parameter name:
nccrOpt) is set to Disabled (0). Cannot be set to 1, 2, 3 or 4,
if inter_rat_enabled is set to 1 (Idle) and the PBCCH/PCCCH
feature (pccchOpt) is unrestricted.

Bad PMRs
gprs_num_pmrs

Displayed in the GPRS - Network Controlled Cell Reselection

grouping of the CELL Detailed View.
Indicates the number of bad Packet Resource Reports
(PMR) that are received before the PCU initiates network
controlled cell reselection. (A bad PMR is one in which the
difference between the serving cell's rxlev and the serving
cell's configured value of rxlev_access_min is less than
gprs_cr_margin.) Grayed-out if the Network Controlled Cell
Reselection Feature (nccrOpt) is Disabled (0) for the BSS.
Valid values: 1 - 10. The default is 3.
Continued

2-84

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

NCCR changes to Detailed Views

Table 2-14 Network Controlled Cell Reselection parameters (Continued)

OMC-R GUI field name/BSS
parameter name
PMR Threshold
gprs_cr_margin

Description
Displayed in the GPRS - Network Controlled Cell Reselection
grouping of the CELL Detailed View.
Indicates the threshold at which the network determines the
Packet Resource Report (PMR) received from the MS is a bad
PMR.
Grayed-out if the Network Controlled Cell Reselection Feature
(nccrOpt) is Disabled (0) for the BSS.
Valid values: 5 - 40. The default is 30.

NCCR changes to Detailed Views

The NCCR feature adds a GPRS checkbox to the BA Type field (parameter ba_type) in the
following OMC-R GUI Detailed Views:

Neighbor Detailed View*

TestNeighbor Detailed View*

Neighbor Template Detailed View*

Multiple TestNeighbor Create Form*

Neighbor Template View Form

Source/Neighbor View Form

An asterisk (*) in the list above indicates that the GPRS checkbox is grayed-out if the Network
Controlled Cell Reselection Feature (parameter name: nccrOpt) field is set to Disabled (0) in
the Optional Features grouping of the BSS Detailed View. Also, at least one of the checkboxes in
the BA Type field must be checked before the Detailed View can be saved.
It is possible to select the following combinations in the BA Type field:

SACCH or BCCH or GPRS

SACCH or BCCH

SACCH and GPRS

BCCH and GPRS

SACCH and BCCH and GPRS

Methods for configuring NCCR

The NCCR feature can be configured using:

OMC-R GUI BSS and CELL Detailed Views and the fields shown in Table 2-14.

TTY interface, see Configuring NCCR using the TTY interface.

68P02901W17-T

2-85
Jan 2010

Configuring NCCR using the TTY interface

Chapter 2: Configuring BSS Features

Configuring NCCR using the TTY interface

Using chg_element and disp_element commands to change NCCR
parameters
The chg_element and disp_element commands can be used to configure and change the NCCR
parameters shown in Table 2-14. Some examples are also given in the following sections.
See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS
commands, prompts, and parameters.

Displaying the current NCCR parameter values

Use the disp_element command to display the current values of NCCR parameters shown in
Table 2-14.
For example, the following command displays the value of nc_reporting_period_i at site 5:
disp_element nc_reporting_period_i 5
The system replies, for example:
nc_reporting_period_i = 6
The following command displays the value of the network_control_order parameter at site 5,
cell id 0010116:
disp_element network_control_order 5 cell 0 0 1 0 1 1 6

Changing the NCCR parameter values

To change the NCCR parameter values, use chg_element. For example, the following command
changes the value of nc_reporting_period_i to 4 at site 5:
chg_element nc_reporting_period_i 4 5

Changing the network_control_order parameter

To change the network_control_order parameter, use the chg_cell_element command. for
example, the following command changes the value of network_control_order to 2 (for NC2)
at site 3, cell 0010116:
chg_cell_element 3 network_control_order 2 cell 0 0 1 0 1 1 6

NCCR changes to neighbor commands

The NCCR feature modifies the add_neighbor, modify_neighbor, and disp_neighbor
commands.

New add_neighbor prompts:

Table 2-15 details the additional system prompts for NCCR information when the
add_neighbor is used.

2-86

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring NCCR using the TTY interface

Table 2-15 add_neighbor NCCR-related prompts

Prompt

Values

Default

Add neighbor to the BA BCCH list

(yes/no)?

yes or no

yes

Add neighbor to the BA SACCH list

(yes/no)?

yes or no

yes

Add neighbor to the BA GPRS list

(yes/no)?
(Only displayed if NCCR is restricted for
the BSS.)

yes or no

yes

0 - 63

None

Enter base station identity code (bsic):

(Prompted for all external neighbors.)

If an attempt is made to create a neighbor, which is not present in any of the BCCH,
SACCH or GPRS lists, the command is rejected and an error message is displayed.

modify_neighbor NCCR changes:

The modify_neighbor command can be used to specify if a previously added frequency
should be added or removed from the ba_gprs list.
For example, the following command attempts to delete the neighbor 0010112 of cell
0010111 from the GPRS list, when the neighbor is not present in both the SACCH and
BCCH lists:
modify_neighbor 0 0 1 0 1 1 1 0 0 1 0 1 1 2 ba_gprs delete
COMMAND REJECTED: Neighbor not present in SACCH list:
remove from BCCH/GPRS list.

must be deleted to

The following command adds the neighbor 0010112 of cell 0010111 on the GPRS list, when
NCCR is unrestricted in the BSS:
modify_neighbor 0 0 1 0 1 1 1 0 0 1 0 1 1 2 ba_gprs add
COMMAND ACCEPTED
If a user attempts to include a neighbor's frequency on the GPRS list when the NCCR
feature is restricted at the BSS, the command is rejected and an error message is displayed.

disp_neighbor NCCR changes:

The disp_neighbor command can be used to display whether the frequencies of the
neighboring cells are part of the ba_gprs list. For example, the following command
displays all neighbor cells of cell 0010111, when NCCR is unrestricted at the BSS:
disp_neighbor 0 0 1 0 1 1 1 all
The system responds by displaying a report including a GPRS column.

68P02901W17-T

2-87
Jan 2010

Configuring NCCR using the TTY interface

Chapter 2: Configuring BSS Features

The following command displays all neighbor information for neighbor cell 0010114 of cell
0010111, when NCCR is unrestricted at the BSS:
disp_neighbor 0 0 1 0 1 1 4 0 0 1 0 1 1 1
The system responds by displaying a report including Frequency in the ba_type list
information.
See Technical Description: BSS Command Reference (68P02901W23) for full details of the
reports displayed.

del_neighbor NCCR changes:

The del_neighbor command can be used to delete the frequencies of the neighboring cells
from the ba_type list. For example, the following command deletes the cell 0010114 from
the neighbor list of cell 0010111:
del_neighbor 0 0 1 0 1 1 1 0 0 1 0 1 1 4

2-88

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GPRS Interleaving TBFs

GPRS Interleaving TBFs

Description of TBF
A Temporary Block Flow (TBF) is a logical connection used by the two GPRS RR entities to
support unidirectional transfer of LLC PDUs on packet data physical channels. The TBF is
allocated a radio resource on one or more PDCHs and comprises a number of RLC/MAC blocks
carrying one or more LLC PDUs. A TBF is temporary and is maintained only for the duration
of a data transfer; that is, until there are no more RLC/MAC blocks to be transmitted and,
in RLC acknowledged mode, all of the transmitted RLC/MAC blocks have been successfully
acknowledged by the receiving entity.

Description of GPRS interleaving TBFs

Interleaving TBFs allow the rapid multiplexing of RLC data blocks of many different mobiles on
to a common air resource. Many mobiles can then share a common air resource (although the
effective throughput of each mobile on the shared resource may be decreased).
Each mobile sharing a common air resource is given a percentage of the bandwidth of the
shared resource. For example, if two mobiles are interleaved on the same air timeslot, one
mobile can be given 70% of the timeslot, and the second mobile is given the remaining 30%.
Interleaving increases the number of users on a single timeslot, therefore increasing the overall
capacity (in terms of number of users) of a serving cell.
Interleaving TBFs in the uplink and downlink use Block-by-Block multiplexing, which involves
multiplexing two or more mobiles on a timeslot with the capability of switching between mobiles
every block period.
All mobiles on a timeslot are simultaneously active in TBFs. The TBF setup, release, and data
transfer phases of the TBF for one mobile can overlap the TBF setup, release, and data transfer
phases of other TBFs belonging to other mobiles.
For a full description of this feature, see Technical Description: BSS Implementation

(68P02901W36).

Delayed Downlink TBF Release

When in Delayed Downlink TBF Release mode, the BSS sends dummy data blocks at least every
24 block periods to the MS if no new data is available. If new downlink data does not arrive
within a predetermined number of block periods, downlink TBF is released. If new data arrives
for an MS in Delayed Downlink TBF Release mode, then the BSS exits Delayed Downlink TBF
Release mode and continues in data transfer mode. The BSS parameter delay_dl_rel_dur
determines the number of block periods in which the network delays the release of a downlink
TBF. See Table 2-16 for details.

68P02901W17-T

2-89
Jan 2010

Delayed Downlink TBF Release Control

Chapter 2: Configuring BSS Features

Delayed Downlink TBF Release Control

When Delayed Downlink TBF Release Control is enabled, the BSS monitors and calculates the
availability of timeslot resources in the cell as cell availability, and terminates one or more
downlink TBFs in Delayed Downlink Release mode if the cell is under congestion. The downlink
TBFs terminated due to cell availability will be in Delayed Downlink TBF Release mode for less
than the number of blocks determined by delay_dl_rel_dur. Delayed Downlink TBF Release
Duration as a function of cell availability is enabled and disabled using the BSS parameter
ddtr_ctrl_enabled. See Table 2-16 for details.

Delayed Uplink TBF Release

When a downlink TBF does not exist for the MS, the BSS extends the uplink TBF of the MS by
delaying the release of the uplink TBF. If a new downlink TBF is not established for the MS
within the predetermined number of block periods, uplink TBF is released. If a new downlink
TBF is established for the MS, the BSS releases the uplink TBF immediately. The BSS parameter
delay_ul_rel_dur determines the number of block periods in which the network delays the
release of an uplink TBF. See Table 2-16 for details.

GPRS interleaving TBFs capacity

The BSS can support:

Up to four unique mobiles in both the Uplink and Downlink directions on a timeslot.

Up to 120 active downlink TBFs per PRP board.

Up to 120 active uplink TBFs per PRP board.

Up to 120 active mobiles per PRP board.

GPRS interleaving TBFs parameters

Table 2-16 details the GPRS interleaving parameters for a BSS and cell. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For
further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).

2-90

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GPRS interleaving TBFs parameters

Table 2-16 GPRS interleaving BSS and cell parameters

OMC-R GUI field name/BSS
parameter name

Description

BSS Parameters:
Delayed Downlink TBF
Release Duration
delay_dl_rel_dur

Displayed in the GPRS grouping in the BSS Detailed View form.

The number of block periods in which the network delays the
release of a downlink TBF. One block period is 20 ms. Valid
values: 15 - 600 blocks. Default is 50 blocks.
Can only be modified if the GPRS Feature (gprsOpt) is
unrestricted (Enabled) in the BSS Detailed View. Otherwise,
the field is grayed-out in the Detailed View form.

Delayed Uplink TBF Release

Duration
delay_ul_rel_dur

Displayed in the GPRS grouping in the BSS Detailed View form.

The number of block periods in which the network delays the
release of an uplink TBF.
Valid values: 10 - 50 blocks. Default is 18 blocks.
Grayed-out if the GPRS feature (gprsOpt) is restricted at the
BSS.

Delayed Downlink TBF

Release Control
ddtr_ctrl_enabled

Displayed in the GPRS grouping in the BSS Detailed View form.

Whether the BSS supports the feature for Delayed Downlink
TBF Release Duration as a function of cell availability.
Valid values: Disabled (0) or Enabled (1). Default is 0.
Grayed-out if either the GPRS feature (gprsOpt) or Increased
PRP Capacity feature is restricted at the BSS.
The ddtr_ctrl_enabled parameter enables or disables the
functionality related to delayed downlink TBF release duration
and extended uplink TBF duration of cell availability. Valid
values: 0 or 1
0 - Disable the functionality related to delayed downlink TBF
release duration and extended uplink TBF duration of cell
availability.
1 - Enable the functionality related to delayed downlink TBF
release duration and extended uplink TBF duration of cell
availability.
This element requires the GPRS feature and Increased PRP
Capacity feature to be unrestricted.

Auto Downlink Duration

auto_dl_dur

Displayed in the GPRS grouping in the BSS Detailed View form.

The number of block periods in which the network keeps a new
downlink TBF, which was created through the auto downlink
mechanism, alive while waiting for new downlink data to
arrive. One block period is 20 ms. Valid values: 15 - 250 blocks.
Default is 50 blocks.
Can only be modified if the GPRS Feature (gprsOpt) is
unrestricted (Enabled) in the BSS Detailed View. Otherwise,
the field is grayed-out in the Detailed View form.
Continued

68P02901W17-T

2-91
Jan 2010

Impact of GPRS interleaving TBFs on a BSS

Chapter 2: Configuring BSS Features

Table 2-16 GPRS interleaving BSS and cell parameters (Continued)

OMC-R GUI field name/BSS
parameter name
GPRS Scheduling Beta
Algorithm
gprs_sched_beta

Description
Displayed in the GPRS grouping in the BSS Detailed View form.
The scheduling beta algorithm at the BSS.
Valid values: 0 - 2, where:

0 - Each MS throughput in bps is the same.

1 - Each MS transfers the same number of blocks as every

other mobile.

2 - MS with the higher coding scheme is preferred.

Can only be modified, if the GPRS Feature (gprsOpt) is

unrestricted (Enabled) in the BSS Detailed View. Otherwise,
the field is grayed-out.
If gprs_sched_beta is modified and saved while the QoS feature
(see Quality of Service (QoS) on page 2-154) is enabled, the
following message is displayed: WARNING: Changes to
gprs_sched_beta are overridden while QoS is enabled.
Cell Parameter:
Max Number of TS In
Pre-load USF Active State
ts_in_usf_active

Displayed in the GPRS grouping in the CELL Detailed View

form.
The maximum number of non-BCCH timeslots allowed to be in
preload USF (Uplink State Flag) active state in the cell at the
same time. (That is, the number of non-BCCH timeslots that
are broadcast continuously at full power even when no mobile
is active on the timeslot.) Valid values are 0 - 3.
If not set by a user at cell creation time, defaults to 1 timeslot.
Can only be modified, if the GPRS Feature (gprsOpt) and
Enhanced GPRS One Phase feature are unrestricted (Enabled)
in the BSS Detailed View. Otherwise, the field is grayed-out in
the CELL Detailed View form.

Impact of GPRS interleaving TBFs on a BSS

The introduction of GPRS interleaving TBFs modifies the BSS parameter gprs_mac_mode,
which determines the medium access mode to be used by the BSS. gprs_mac_mode now
only supports dynamic access mode (1), which is also the default. For example, the following
command changes gprs_mac_mode to dynamic access mode:
chg_element gprs_mac_mode 1 bsc

Methods for configuring GPRS interleaving TBFs

The GPRS interleaving TBFs feature can be configured using:

2-92

OMC-R GUI BSS and CELL Detailed Views and the fields shown in Table 2-16.

TTY interface, see Configuring GPRS interleaving TBFs using the TTY interface.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring GPRS interleaving TBFs using the TTY interface

Configuring GPRS interleaving TBFs using the TTY interface

Displaying the current GPRS interleaving TBF BSS parameter values
Use the disp_element command to display the current value of a BSS GPRS interleaving TBFs
parameter detailed in Table 2-16. For example, the following command displays the current
value of auto_dl_dur:
disp_element auto_dl_dur 0
The system replies, for example: auto_dl_dur = 20

Modifying GPRS interleaving TBF BSS parameter values

Use the chg_element command to change the value of a BSS GPRS interleaving TBFs parameter
detailed in Table 2-16. For example, the following command changes auto_dl_dur to 20:
chg_element auto_dl_dur 20 0

Displaying the current value of ts_in_usf_active

Use the disp_element command to display the current value of the GPRS interleaving TBFs
cell parameter ts_in_usf_active detailed in Table 2-16. For example, the following command
displays the current value of ts_in_usf_active at the BSC, cell 0010111:
disp_element ts_in_usf_active 0 cell 0 0 1 0 1 1 1
The system replies, for example:
ts_in_usf_active = 1

Modifying the current value of ts_in_usf_active

Use the chg_element or chg_cell_element command to display the current value of the GPRS
interleaving TBFs cell parameter ts_in_usf_active detailed in Table 2-16. For example, the
following commands change ts_in_usf_active to 1 at cell 0010111:
chg_cell_element ts_in_usf_active 1 0 0 1 0 1 1 1
chg_element ts_in_usf_active 1 0 cell 0 0 1 0 1 1 1

68P02901W17-T

2-93
Jan 2010

Enhanced BSC Capacity

Chapter 2: Configuring BSS Features

Enhanced BSC Capacity

Introduction to the Enhanced BSC Capacity feature

The Enhanced BSC Capacity feature is an optional feature, which increases the capacity of the
BSC from 384 carriers and 2400 circuits (CICs) to 512 carriers and 3200 circuits (CICs).

NOTE
If either GSM HR and/or AMR has been purchased and enabled, a maximum of 4800
CICs can be equipped at an RXCDR site.
The Enhanced BSC Capacity feature also increases the number of entries in the BSC-RXCDR
connectivity table to 27.

Determining whether Enhanced BSC Capacity is enabled

Using the OMC-R GUI
To check if the Enhanced BSC Capacity feature has been enabled using the OMC-R GUI, display
the setting of the Enhanced BSC Capacity Feature (ebscOpt) field in the Optional Features
grouping in the BSS Detailed View. The values for Enhanced BSC Capacity Feature field are:

Disabled (0).

Enabled (1).

Default is Disabled (0).

Using the TTY interface

To check if Enhanced BSC Capacity has been enabled using the TTY interface, enter the
following command:
disp_options all
If the Enhanced BSC Capacity is unrestricted (enabled) the system displays the following in
the unrestricted list:
49 Enhanced BSC Capacity

2-94

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Inter-Radio Access Technology (Inter-RAT) Handover

Inter-Radio Access Technology (Inter-RAT) Handover

Overview of Inter-RAT Handover

Initially, when network operators provide a UMTS service, there may only be small pockets of
UMTS coverage in a predominantly GSM coverage network. In this situation, when a UMTS
subscriber leaves a UMTS coverage area, the call may be dropped. UMTS subscribers may also
face problems establishing a UMTS call when the traffic in the UMTS coverage area is high. To
avoid these problems, the Inter-RAT Handover feature can be enabled.
The Inter-RAT Handover feature allows a multi-RAT mobile station (MS) to perform 2G to 3G
cell selection/reselection in idle mode, and 3G to 2G handovers in circuit-switched dedicated
mode. When the Inter-RAT Handover feature is enabled at a BSS, the BSS broadcasts new
system information messages to allow a multi-RAT MS to perform measurements on UMTS
FDD (UTRAN) neighbor cells for handover and cell selection/reselection purposes. When in
dedicated mode, Inter-RAT Handover provides 3G measurement control parameters to the MS.
When the Inter-RAT Handover feature is enabled at a BSS, it can then be enabled or disabled
for individual cells.

Inter-RAT Handover dependencies

The Inter-RAT Handover feature requires:

Multi-RAT mobile stations, which are capable of accessing the Core Network (CN) from a
UMTS coverage area and a GSM coverage area. The MS must be capable of operating in
either GSM or UMTS cells including execution of procedures such as PLMN selection, cell
reselection, measurements in idle mode and dedicated mode, and so on.

A UMTS network including 2G/3G compatible MSC.

Existing 2G CN nodes must be able to interact with the 3G CN nodes through MAP
procedures defined on the E-interface between a 3G CN node and 2G CN node.

68P02901W17-T

2-95
Jan 2010

Enhanced Inter-RAT Handover feature

Chapter 2: Configuring BSS Features

Enhanced Inter-RAT Handover feature

The Enhanced 2G/3G Handover and Cell Reselection feature (also referred to as the Enhanced
Inter-RAT Handover feature) provides support in the BSS for:

Outgoing dedicated mode handover from 2G to 3G (basic measurement-based and

service-based handover triggers).

BSS control for measurement reporting by multi-RAT MS, UTRAN early classmark sending
blind search for cell reselection from 2G to 3G.

Inter-RAT related performance measurements.

The Enhanced Inter-RAT feature also uses a new device called a Blind Search Neighbor, which is
supported under a cell, and represents the blind search neighbors of a cell. See UTRAN blind
search neighbor on page 8-140 for further details.

Additional information
For further details of the Inter-RAT Handover feature and the Enhanced Inter-RAT Handover
feature, see Technical Description: BSS Implementation (68P02901W36).

Interaction with other features

This feature interacts with the IMRM feature, see for further details.

Inter-RAT Handover and Enhanced Inter-RAT Handover

parameters
Table 2-17 lists the parameters associated with the Inter-RAT Handover and Enhanced Inter-RAT
Handover features. Unless stated otherwise, the OMC-R parameter name is usually the same
as the BSS parameter name. For further details of these and other parameters, see Technical
Description: BSS Command Reference (68P02901W23).

2-96

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Handover and Enhanced Inter-RAT Handover parameters

Inter-RAT

Table 2-17 Inter-RAT Handover and Enhanced Inter-RAT handover parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

BSS parameters:
Inter-RAT Handover Feature
InterRatOpt

Displayed in the Optional Features

grouping of the BSS Detailed View form.
Indicates whether the Inter-RAT
Handover Feature is restricted (disabled)
or unrestricted (enabled) in the BSS
software.
This parameter cannot be modified by
a user. When the Enhanced Inter-RAT
Handover Feature (EnhncdInterRatOpt)
is set to 1 (Enabled), InterRatOpt is
automatically set to 1 (Enabled).

0 or 1, where:
Disabled (0).
Enabled (1).
Default is
Disabled (0).

Enhanced Inter-RAT
Handover Feature
EnhancedInterRatOpt
(OMC parameter name:
EnhncdInterRatOpt)

Displayed in the Optional Features

grouping of the BSS Detailed View form.
Indicates whether the Enhanced
Inter-RAT Handover Feature is restricted
(disabled) or unrestricted (enabled)
for the BSS. This parameter cannot
be modified by a user. When the
Enhanced Inter-RAT Handover Feature
(EnhncdInterRatOpt) is set to 1 (Enabled),
InterRatOpt is automatically set to 1
(Enabled).

0 or 1, where:
Disabled (0).
Enabled (1).
Default is
Disabled (0).

MSC Release
msc_release

Displayed in the General grouping of the

BSS Detailed View form.
Indicates the release of the MSC to which
this BSS is connected.

0 or 1, where:
Release 1998 or
older (0).
Release 1999 or
newer (1).
Default is 0.
Continued

68P02901W17-T

2-97
Jan 2010

Inter-RAT Handover and Enhanced Inter-RAT Handover parameters

Chapter 2: Configuring BSS Features

Table 2-17 Inter-RAT Handover and Enhanced Inter-RAT handover parameters

(Continued)
OMC-R GUI field name/BSS
parameter name

Description

Values

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View form.
Indicates whether idle mode, dedicated
mode, or idle mode and dedicated mode
functionality of the Inter-RAT Handover
feature are enabled for this cell.
This field is grayed-out if the Inter-RAT
Handover Feature (InterRatOpt)
is restricted (disabled) for the
BSS. Can only be set to 1 (Idle) if
network_control_order is set to 0
(NC0).
This field cannot be set to 4, 5, 6 or 7 if the
container BSS has EnhancedInterRatOpt
set to Disabled (0).
If modified to either of 4, 5, 6 or 7 and the
container BSS has earlyClassmarkSndset
to 0 or 1, the following warning is
displayed: Enhanced 2G/3G requires
early_classmark_sending to be enabled
across both the A and Air Interfaces.
If modified to either of 4, 5, 6 or 7 and
the container BSS has phase2ClssmkAld
not set to 2, the following warning is
displayed: Enhanced 2G/3G requires
phase2_classmark_allowed to be
configured to support multiband.

0 - 7, where:
0 - OFF.
1 - 2 3G Idle.
2 - 3 2G
Dedicated.
3 - 2 3G Idle and
3-2G Dedicated.
4- 2G-3G
Dedicated.
5- 2G-3G Idle and
2G-3G Dedicated.
6- 3G-2G
Dedicated and
2G-3G Dedicated.
7- Idle and
bi-directional
Dedicated.
Default is 0.

CELL parameters:
Inter-RAT Handovers Enabled
inter_rat_enabled

Continued

2-98

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Handover and Enhanced Inter-RAT Handover parameters

Inter-RAT

Table 2-17 Inter-RAT Handover and Enhanced Inter-RAT handover parameters

(Continued)
OMC-R GUI field name/BSS
parameter name

Description

Values

BCCH RF Signal Level

Threshold
qsearch_i

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View form.
Used by the MS to determine when to
start measuring a UTRAN neighbor cell.
When the received RF signal level of
the BCCH carrier in the serving GSM
cell is below or above the qsearch_i
value, the MS starts measurement of
the UTRAN neighbor cells. This field is
grayed-out if Inter-RAT Handover Feature
(InterRatOpt) and TD-SCDMA Feature
(tdOpt) are restricted (disabled) for the
BSS.
This parameter is modified to be capable
of access when either tdOpt / InterRATOpt
/ EnhancedInterRATOpt is unrestricted.

0 - 15, where:
0 = -98 dBm.
1 = -94 dBm.
2 = -90 dBm.
....
4 = -82 dBm.
5 = Below -78
dBm.
6 = Below -74
dBm.
7 = (Always
search).
8 = Above -78
dBm.
9 = Above -74
dBm.
10 = -70 dBm.
....
14 = -54 dBm.
15 = (Never
search).
Default is 15.

Use BCCH RF Signal Level

Threshold
qsearch_c_initial

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View form.
The value of this parameter is broadcast
on the BCCH using the SYSTEM
INFORMATION TYPE 2quater message,
and determines if qsearch_I is used
by the MS in dedicated mode after
certain instances of MEASUREMENT
INFORMATION messages are received,
OR if the MS should always search.
Modifying this parameter causes
the SI2ter_MP_CHANGE_MARK and
SI2quater MP_CHANGE_MARK to be
toggled.
This field is grayed-out if Inter-RAT
Handover Feature (InterRatOpt)
and TD-SCDMA Feature (tdOpt) are
restricted (disabled) for the BSS.
This parameter is modified to be capable
of access when either tdOpt / InterRATOpt
/ EnhancedInterRATOpt is unrestricted.

0 or 1, where:
0 = Use Q
Search_I
1 = Infinity
(always)
Default is 0.

Continued

68P02901W17-T

2-99
Jan 2010

Inter-RAT Handover and Enhanced Inter-RAT Handover parameters

Chapter 2: Configuring BSS Features

Table 2-17 Inter-RAT Handover and Enhanced Inter-RAT handover parameters

(Continued)
OMC-R GUI field name/BSS
parameter name

Description

Values

Receive Signal Code Power

(RSCP) Threshold
fdd_qoffset

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View form.
Used by the MS in the cell reselection
algorithm.
This field is grayed-out if Inter-RAT
Handover Feature (InterRatOpt) is
restricted (disabled) for the BSS.

0 - 15, where:
0 = always
select a cell, if
acceptable.
1 = -28 dB.
2 = -24 dB.
3 = -20 dB.
....
15 = 28 dB.
Default is 8 (0
dB).

Minimum Ec/No Threshold

fdd_qmin

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View form.
Used by the MS in the cell reselection
algorithm.
This field is grayed-out if Inter-RAT
Handover Feature (InterRatOpt) is
restricted (disabled) for the BSS.

0 - 7, where:
0 = -20 dB.
1 = -6 dB.
2 = -18 dB.
3 = -8 dB.
4 = -16 dB.
5 = -10 dB.
6 = -14 dB.
7 = -12 dB.
Default is 0 (-20
dB).

SACCH RF Signal Level

Threshold
qsearch_c

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View
form. Used by the MS in dedicated mode
to decide when to start measurement
of a UTRAN neighbor cell. This field
is grayed-out if EnhncdInterRatOpt is
Disabled (0).

0 - 15, where:
0 = -98 dBm.
1 = -94 dBm.
4 = -82 dBm.
5 = Below -78
dBm.
6 = Below -74
dBm.
7 = Always
search.
8 = Above -78
dBm. 9 = Above
-74 dBm.
10 = -70 dBm.
14 = -54 dBm.
15 = Never
search.
Default is 15
(Never search).

UTRAN Reporting Quantity

fdd_rep_quant

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View form.
Indicates the measurement quantity to be
reported for a UTRAN FDD cell. Grayed
out if EnhncdInterRatOpt is Disabled (0).

0 or 1, where:
0 = RSCP.
1 = Ec/No.
Default is 1
(Ec/No).
Continued

2-100

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Handover and Enhanced Inter-RAT Handover parameters

Inter-RAT

Table 2-17 Inter-RAT Handover and Enhanced Inter-RAT handover parameters

(Continued)
OMC-R GUI field name/BSS
parameter name

Description

Values

Number of Serving Band cells

to report
serving_band_reporting

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View
form. Indicates the number of cells to
be reported from the frequency band
to which the serving GSM cell belongs.
Grayed out if EnhncdInterRatOpt is
Disabled (0).

Values: 0 - 3.
Default is 3.

Number of UTRAN FDD cells

to report
fdd_multirat_reporting

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View form.
Indicates the number of UTRAN FDD
cells to be reported in the list of strongest
cells in the measurement report. Grayed
out if EnhncdInterRatOpt is Disabled (0).

0 - 3.
Default is 1.

Blind Search Preference

blind_search_preference

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View
form. Indicates the preference for blind
search in idle mode and/or dedicated
mode. Grayed out if EnhncdInterRatOpt
is Disabled (0). If modified from 0 to 1,
and there are no UTRAN blind search
neighbors equipped to that cell, the
following warning message is displayed:
There are no Blind Search neighbors
equipped for this cell.

0 or 1, where:
0 = No blind
search in idle
mode.
1 = Blind search
in idle mode.
Default is 0 (No
blind search in
idle mode).

UMTS Band Preferred

umts_band_preferred

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View
form. Indicates whether handover to
UMTS band is preferred. Grayed out if
EnhncdInterRatOpt is Disabled (0)

0 or 1, where:
0 = No.
1 = Yes.
Default is 0 (No).

Threshold when
FDD_REP_QUANT is Ec/No
umts_cpich_ec_no_min

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View
form. It is a threshold parameter
used by the handover algorithm when
fdd_rep_quant is Ec/No(1). Grayed out if
EnhncdInterRatOpt is Disabled (0).

-20 dBm to 0
dBm.
Default is -15
dBm.

Threshold when
FDD_REP_QUANT is RSCP
umts_cpich_rscp_min

Displayed in the Inter-RAT Handover

grouping of the CELL Detailed View
form. It is a threshold parameter
used by the handover algorithm when
fdd_rep_quant is RSCP (0). Grayed out if
EnhncdInterRatOpt is Disabled (0).

-53 dBm to -115

dBm.
Default is -90
dBm.

Continued

68P02901W17-T

2-101
Jan 2010

Methods of configuring Inter-RAT Handover

Chapter 2: Configuring BSS Features

Table 2-17 Inter-RAT Handover and Enhanced Inter-RAT handover parameters

(Continued)
OMC-R GUI field name/BSS
parameter name

Description

Values

UTRAN parameters:
UMTS Measurement Margin
umts_meas_margin

Displayed in the Identification parameter

grouping in the UTRAN Detailed View
form.
It is a measurement parameter used by
the handover algorithm. Grayed out if
EnhncdInterRatOpt is Disabled (0).

0 dB to 20 dB.
Default is 3 dB.

Averaging Period
umtsNcellAvgPrd

Displayed in the General parameter

grouping in the UTRAN Detailed View
form. Indicates UTRAN neighbor cell
measurement averaging period. Grayed
out if EnhncdInterRatOpt is Disabled (0).

0 - 12.
Default is 6.

UMTS BA Type
umts_ba_type

Displayed in the General parameter

grouping in the UTRAN Detailed View
form. Specifies the neighbor lists: BCCH,
SACCH, or BCCH and SACCH. Grayed
out if EnhncdInterRatOpt is Disabled (0).

1 - 3, where:
1 = BCCH.
2 = SACCH.
3 = BCCH.
and SACCH.
Default is 3 (both
buttons checked).
If the SACCH
option is selected,
it cannot be
modified after
creation (whether
selected or not).

Blind Search Neighbor

parameters

See UTRAN blind search neighbor on

page 8-140 for details.

Methods of configuring Inter-RAT Handover

Inter-RAT Handover can be configured using:

OMC-R GUI BSS and CELL Detail Views and the fields shown in Table 2-17.

TTY interface, see Configuring Inter-RAT Handover using the TTY interface.

Configuring Inter-RAT Handover using the TTY interface

Checking if Inter-RAT Handover is unrestricted
To check if the Inter-RAT Handover feature is unrestricted (enabled) using the TTY interface,
enter the following command:
disp_options

2-102

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring Inter-RAT Handover using the TTY interface

If Inter-RAT Handover is unrestricted, the following is displayed:

36 InterRat Handover 2G>3G Cell Reselection, 3G>2G Dedicated Mode.

Displaying and modifying Inter-RAT Handover parameters

The disp_element, disp_cell, chg_element and chg_cell_element commands can be used
to display and configure the Inter-RAT Handover cell parameters shown in Table 2-17. Some
examples are also given in the following sections.
See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS
commands, prompts, and parameters.

Displaying whether Inter-RAT handover is enabled at a cell

Use the disp_element command to display whether Inter-RAT Handover is enabled for a cell.
For example, the following command displays the current setting at cell 0010114, site 0:
disp_element inter_rat_enabled 0 cell_number = 0 0 1 0 1 1 4
The system replies, for example:
inter_rat_enabled = 0

Setting cell parameters for Inter-RAT Handover

Use the chg_cell_element command to change an Inter-RAT Handover cell parameter. For
example, the following command changes qsearch_i to 10 for cell 0010114:
chg_cell_element qsearch_i 10 0 0 1 0 1 1 4

68P02901W17-T

2-103
Jan 2010

GSM location services

Chapter 2: Configuring BSS Features

GSM location services

Description of Location Services

Location services (LCS) is an optional feature, which identifies the physical location of a Mobile
Station (MS) by using one or more positioning mechanisms.
The location services feature provides support for a Motorola or third-party mobile positioning
application.
The positioning process involves two main steps:
1.

Signal measurement.

2.

Location estimate computation based on the measured signal.

Location services have been identified by operators, service providers and Motorola as being a
key application enabler. For example, through applications tailored to use the position of the
mobile device directly (Where am I?), to deliver tailored content (Location Specific Advertising)
or to determine the routing of voice traffic (Location Sensitive Routing).
Location services support is through:

NSS-based Servicing Mobile Location Centre (SMLC), which is an SMLC communicating

with an MSC through the Ls interface.

BSS-based SMLC, which is an SMLC communicating with the BSS through the Lb interface.

For a full description of location services, see Technical Description: BSS Implementation
(68P02901W36).

Location services and the LMTL device

The Location Services Message Transfer Link (LMTL) device is present in a BSS-based
implementation of the LCS feature. The LMTL device refers to both the physical and logical
interface between the BSC and the BSS-based SMLC.
See Configuring an LMTL device on page 9-131 for details of how to configure an LMTL device.

Determining whether location services is unrestricted

Location services is an optional feature.

Using the OMC-R GUI

To check if location services is unrestricted (enabled) using the OMC-R GUI, display the setting
of the Location Services field in the Optional Features grouping in the BSS Detailed View.

2-104

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Location services parameters

Using the TTY interface

To check if location services feature is unrestricted using the TTY interface, enter the following
command:
disp_options all
If the location services optional feature is unrestricted the system displays the following in
the unrestricted list:
43 Location Services

Location services parameters

Location services configurable parameters are divided into the following categories:

General Location Services Timers.

General Location Services Database Elements.

Lb Interface MTP Layer 2 Timers.

Lb Interface MTP Layer 3 Timers.

Lb Interface MTP Layer 3 Elements.

Lb Interface Call Processing (CP) Timers.

Lb Interface Call Processing (CP) Elements.

Table 2-18 details these Location Services parameters. Unless stated otherwise, the OMC-R
parameter name is usually the same as the BSS parameter name. For further details of these
and other parameters, see Technical Description: BSS Command Reference (68P02901W23).

Table 2-18 Location Services parameters

OMC-R GUI field name/BSS
parameter name

Description

General Location Services Timers:

LCS Perform Location
Timer (ms)
lcs_perf_location

Displayed in the LCS grouping in the BSS Detailed View form.

Guards the receipt of a BSSMAP-LE perform Location Response
from a BSS-based SMLC. Valid values: 0 - 1,000,000 ms. Default
is 300,000 ms.

LCS Supervision Timer

(ms)
lcs_supervision

Displayed in the LCS grouping in the BSS Detailed View form.

Supervises the overall operation of a location request. Valid
values: 0 - 1,000,000 ms. Default is 30,000 ms. The value of
this parameter should be less than the value of the LCS Perform
Location timer.

LCS Segmentation Timer

(ms)
lcs_segmentation

Displayed in the LCS grouping in the BSS Detailed View form.

Supervises an LCS segmentation operation. Valid values: 0 1,000,000 ms. Default is 10,000 ms. The value of this parameter
should be less than the value of the LCS Supervision timer.
Continued

68P02901W17-T

2-105
Jan 2010

Location services parameters

Chapter 2: Configuring BSS Features

Table 2-18 Location Services parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

General Location Services Database Elements:

LCS Mode
lcs_mode

Displayed in the LCS grouping of the BSS Detailed View.

Specifies the LCS mode of the BSS. Valid values: 0 - LCS disabled,
SMLC not supported. 1 - LCS enabled, BSC supports a NSS-based
SMLC.2 - LCS enabled, BSC supports a BSS-based SMLC.
Can only be modified in SYSGEN mode.
If LCS is enabled and early_classmark_sending is not enabled
across the A-interface and the Air-interface, an error message is
displayed. If LCS is enabled and phase2_classmark_allowed
is not configured to support multiband, an error message is
displayed.
If LCS is disabled and one or more LMTL devices are equipped,
an error message is displayed.

Lb Interface MTP Layer 2 Timers:

Lb Interface MTP Layer 2
T1 timer (ms)
lb_int_ss7_l2_t1

Displayed in the LCS grouping in the BSS Detailed View form.

The alignment ready timer (ITU Q.703) associated with the Lb
interface.
The valid values are dependent on the value of the ss7_mode
parameter.
If ss7_mode is 0, values are 40,000 - 50,000 ms. Default is
50,000 ms.
If ss7_mode is 1, values are 13,000 - 30,000 ms. Default is
13,000 ms.
This parameter is automatically changed to the appropriate
default value if the value of ss7_mode is changed.

Lb Interface MTP Layer 2

T2 timer (ms)
lb_int_ss7_l2_t2

Displayed in the LCS grouping in the BSS Detailed View form.

The not aligned timer (ITU Q.703) associated with the Lb
interface. The valid values are dependent on the value of the
ss7_mode parameter.
If ss7_mode is 0, values are 5,000 - 150,000 ms. Default is
25,000 ms.
If ss7_mode is 1, values are 5,000 - 30,000 ms. Default is 23,000
ms.
This parameter is automatically changed to the appropriate
default value if the value of ss7_mode is changed.

Lb Interface MTP Layer 2

T3 timer (ms)
lb_int_ss7_l2_t3

Displayed in the LCS grouping in the BSS Detailed View form.

The aligned timer (ITU Q.703) associated with the Lb interface.
The valid values are dependent on the value of the ss7_mode
parameter.
If ss7_mode is 0, values are 1,000 - 1,500 ms. Default is 1,400
ms.
If ss7_mode is 1, values are 5,000 - 14,000 ms. Default is 11,500
ms.
This parameter is automatically changed to the appropriate
default value if the value of ss7_mode is changed.
Continued

2-106

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Location services parameters

Table 2-18 Location Services parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Lb Interface MTP Layer 2

T4 timer (ms)
lb_int_ss7_l2_t4

Displayed in the LCS grouping in the BSS Detailed View form.

The emergency proving period timer (ITU Q.703) associated
with the Lb interface. Valid values: 400 - 600 ms. Default is 600
ms.

Lb Interface MTP Layer 2

T5 timer (ms)
lb_int_ss7_l2_t5

Displayed in the LCS grouping in the BSS Detailed View form.

The sending SIB timer (ITU Q.703) associated with the Lb
interface. Valid values: 80 - 120 ms. Default is 100 ms.

Lb Interface MTP Layer 2

T6 timer (ms)
lb_int_ss7_l2_t6

Displayed in the LCS grouping in the BSS Detailed View form.

The remote congestion timer (ITU Q.703) associated with the
Lb interface. The valid values are dependent on the value of the
ss7_mode parameter.
If ss7_mode is 0, values are 3,000 - 6,000 ms. Default is 5000 ms.
If ss7_mode is 1, values are 1,000 - 6,000 ms. Default is 5,000
ms.
This parameter is automatically changed to the appropriate
default value if the value of ss7_mode is changed.

Lb Interface MTP Layer 2

T7 timer (ms)
lb_int_ss7_l2_t7

Displayed in the LCS grouping in the BSS Detailed View form.

The excessive delay of acknowledgment timer (ITU Q.703)
associated with the Lb interface. Valid values: 500 - 2,000 ms.
Default is 1,000 ms.

Lb Interface MTP Layer

3 Timers:

Displayed in the LCS grouping in the BSS Detailed View form.

The delay to avoid mis-sequencing on changeover timer (ITU
Q.704) associated with the Lb interface. Valid values: 500 - 1,200
ms. Default is 850 ms.

Interface MTP Layer 3 T1

timer (ms)
lb_int_ss7_l3_t1
Lb Interface MTP Layer 3
T2 timer (ms)
lb_int_ss7_l3_t2

Displayed in the LCS grouping in the BSS Detailed View form.

The waiting for changeover acknowledgment timer (ITU
Q.704) associated with the Lb interface. Valid values: 700 - 2,000
ms. Default is 1,400 ms.

Lb Interface MTP Layer 3

T4 timer (ms)
lb_int_ss7_l3_t4

Displayed in the LCS grouping in the BSS Detailed View form.

The waiting for changeback acknowledgment (first attempt)
timer (ITU Q.704) associated with the Lb interface. Valid values:
500 - 1,20 ms. Default is 850 ms.

Lb Interface MTP Layer 3

T5 timer (ms)
lb_int_ss7_l3_t5

Displayed in the LCS grouping in the BSS Detailed View form.

The waiting for changeback acknowledgment (second
attempt) timer (ITU Q.704) associated with the Lb interface.
Valid values: 500 - 1,200 ms. Default is 850 ms.

Lb Interface MTP Layer 3

T12 timer (ms)
lb_int_ss7_l3_t12

Displayed in the LCS grouping in the BSS Detailed View form.

The waiting for uninhibit acknowledgment timer (ITU Q.704)
associated with the Lb interface. Valid values: 800 - 1,500 ms.
Default is 1,150 ms.

Lb Interface MTP Layer 3

T13 timer (ms)
lb_int_ss7_l3_t13

Displayed in the LCS grouping in the BSS Detailed View form.

The waiting for force uninhibit timer (ITU Q.704) associated
with the Lb interface. Valid values: 800 - 1,500 ms. Default is
1,150 ms.
Continued

68P02901W17-T

2-107
Jan 2010

Location services parameters

Chapter 2: Configuring BSS Features

Table 2-18 Location Services parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Lb Interface MTP Layer 3

T14 timer (ms)
lb_int_ss7_l3_t14

Displayed in the LCS grouping in the BSS Detailed View form.

The waiting for inhibition acknowledgment timer (ITU Q.704)
associated with the Lb interface. Valid values: 2,000 - 3,000 ms.
Default is 2,500 ms.

Lb Interface MTP Layer 3

T17 timer (ms)
lb_int_ss7_l3_t17

Displayed in the LCS grouping in the BSS Detailed View form.

The delay to avoid oscillation of initial alignment failure
and link restart timer (ITU Q.704) associated with the Lb
interface. Valid values: 800 - 1,500 ms. Default is 1,150 ms.

Lb Interface MTP Layer 3

T22 timer (ms)
lb_int_ss7_l3_t22

Displayed in the LCS grouping in the BSS Detailed View form.

The local inhibit test timer (ITU Q.704) associated with the Lb
interface. The valid values are dependent on the value of the
ss7_mode parameter.
If ss7_mode is 0, values are 180,000 - 360,000 ms. Default is
270,000 ms.
If ss7_mode is 1, values are 90,000 - 120,000 ms. Default is
90,000 ms.
This parameter is automatically changed to the appropriate
default value if the value of ss7_mode is changed.

Lb Interface MTP Layer 3

T23 timer (ms)
lb_int_ss7_l3_t23

Displayed in the LCS grouping in the BSS Detailed View form.

The remote inhibit test timer (ITU Q.704) associated with the
Lb interface. The valid values are dependent on the value of the
ss7_mode parameter.
If ss7_mode is 0, values are 180,000 - 360,000 ms. Default is
270000 ms.
If ss7_mode is 1, values are 90,000 - 120,000 ms. Default is
90,000 ms.
This parameter is automatically changed to the appropriate
default value if the value of ss7_mode is changed.

Lb Interface SS7 Link Test

T1 timer (ms)
lb_int_ss7_slt_t1

Displayed in the LCS grouping in the BSS Detailed View form.

The supervision timer for signaling link test
acknowledgment message timer (ITU Q.707) associated with
the Lb interface.
Valid values: 4,000 - 12,000 ms. Default is 8,000 ms.

Lb Interface MTP Layer 3 Elements:

Lb Interface CR Calling
lb_int_cr_calling

Displayed in the LCS grouping in the BSS Detailed View form.

Specifies if the calling party address is to be included in the
SCCP message Connect Request messages that travel over the Lb
interface.
Valid values: 0 or 1.
Default is 0.
0 - not included.
1 - included.

Lb Interface Destination
Point Code (DPC)
lb_int_dpc

Displayed in the LCS grouping in the BSS Detailed View form.

The point code of a BSS-based SMLC. The valid values are
dependent on the value of the ss7_mode parameter.
If ss7_mode is 0, values are 0 - 16383 ms. No default.
If ss7_mode is 1, values are 0 - 16,777,215. No default.
For a live system, lb_int_dpc should not be the same as the opc.
Continued

2-108

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Location services parameters

Table 2-18 Location Services parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Lb Int PC Included Called

Party Flag
lb_int_called_pci

Displayed in the LCS grouping in the BSS Detailed View form.

Specifies if the point code is included in the called party address
in the SCCP messages that travel over the Lb interface.
Valid values: 0 or 1.
The default is None.
0 - point code not included.
1 - point code is included.

Lb Int PC Included Calling

Party Flag
lb_int_calling_pci
(OMC-R parameter name:
lb_calling_pci)

Displayed in the LCS grouping in the BSS Detailed View form.

Specifies if the point code is included in the calling party address
in the SCCP messages that travel over the Lb interface.
Valid values: 0 or 1.
The default is None.
0 - point code not included.
1 - point code is included.

LMTL Load Share

Granularity
lmtl_loadshare_
granularity(OMC-R
parameter name:
lmtl_loadshare)

Displayed in the LCS grouping in the BSS Detailed View form.

Indicates the level of granularity for LMTL load sharing. Valid
values are 0 or 1. Default is 0.0 - corresponds to a granularity of
16.1 - corresponds to a granularity of 64.
If this parameter is modified outside SYSGEN mode, all LMTLs
must be locked for the modification to take effect. This parameter
cannot be modified or displayed at an RXCDR site.

Lb Interface CP Timers:
Lb Interface BSSMAP T4
Timer (ms)
lb_int_bssmap_t4

Displayed in the LCS grouping in the BSS Detailed View form.

Guards the time allowed for the BSS-based SMLC to respond to a
RESET message with a RESET ACKNOWLEDGE message. Valid
values are 0 - 1,000,000 ms. The default is 50,000 ms.

Lb Interface BSSMAP T13

Timer (ms)
lb_int_bssmap_t13

Displayed in the LCS grouping in the BSS Detailed View form.

The reset guard timer (GSM 8.08-3.2.3: BSSMAP timers).
The system starts this timer when the RESET message from
the BSS-based SMLC is received at the BSS. Valid values: 0 1,000,000 ms. Default is 40,000 ms.

Lb Interface Clear
Command Timer (ms)
lb_clear_command

Displayed in the LCS grouping in the BSS Detailed View form.

The wait from clear command from the BSS-based SMLC
timer. Valid values are 0 - 1,000,000 ms. Default is 30,000 ms.

Lb Interface SCCP Conn

Conf Timer (ms)
lb_int_sccp_tconn_est
(OMC-R parameter name:
lb_sccp_tconn_est)

Displayed in the LCS grouping in the BSS Detailed View form.

Specifies the amount of time to wait for the SCCP connection
confirmation from the BSS-based SMLC. Valid values: 0 1,000,000 ms. Default is 30,000 ms.

Continued

68P02901W17-T

2-109
Jan 2010

Location services parameters

Chapter 2: Configuring BSS Features

Table 2-18 Location Services parameters (Continued)

OMC-R GUI field name/BSS
parameter name
Lb Interface SCCP TIAR
Timer (ms)
lb_int_sccp_tiar

Description
Displayed in the LCS grouping in the BSS Detailed View form.
The receive inactivity control timer (GSM 8.08-3.23: all
BSSMAP timers, TIAR) for the Lb interface. Valid values: 0 1,000,000 ms. Default is 30,000 ms. The value of this parameter
should be:

Greater than the lb_int_sccp_tias parameter.

Greater than the value of sccp_tiar at the SMLC.

Lb Interface SCCP Rel

Complete Timer (ms)
lb_int_sccp_trel

Displayed in the LCS grouping in the BSS Detailed View form.

The wait for SCCP release complete timer for the LB interface.
Valid values: 4000 - 15,000 ms. Default is 10,000 ms.

Lb Interface SCCP Rel

Timer (ms)
lb_int_sccp_released
(OMC-R parameter name:
lb_sccp_released)

Displayed in the LCS grouping in the BSS Detailed View form.

The wait for SCCP released message from BSS-based SMLC
timer. Valid values: 0 - 1,000,000 ms. Default is 30,000 ms.

Lb Interface SCCP TIAS

Timer (ms)
lb_int_sccp_tias

Displayed in the LCS grouping in the BSS Detailed View form.

The send activity control timer (GSM 8.08-3.23: all BSSMAP
timers, TIAS) for the Lb interface. Valid values: 0 - 1,000,000 ms.
Default is 30,000 ms. The value of this parameter should be less
than the lb_int_sccp_tiar parameter.

Lb Interface SPI Timer

(ms)
lb_int_spi

Displayed in the LCS grouping in the BSS Detailed View form.

Specifies the amount of time the BSS shall wait before initiating
an internal reset after either Subsystem Prohibited (SSP) or
SPI has occurred over the Lb interface. Valid values: 10,000 1,000,000 ms. Default is 60,000 ms.

Lb Subsystem Status Test

Timer (ms)
lb_int_t_stat_info
(OMC-R parameter name:
lb_t_stat_info)

Displayed in the LCS grouping in the BSS Detailed View form.

Specifies the amount of time between sending Subsystem Status
Test (SST) messages to the BSS-based SMLC. Valid values: 0 1,000,000 ms. Default is 90,000 ms.

Lb Interface CP Elements:
Lb Interface Global Reset
Repetitions
lb_int_global_reset_
repetitions(OMC-R
parameter name:
lb_globresetReps)

2-110

Displayed in the LCS grouping in the BSS Detailed View form.

Specifies the number of times the global reset procedure on the
Lb interface is allowed to repeat before an alarm is generated.
Valid values: 0 - 255. Default is 0.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Restrictions for Location Services parameters

Restrictions for Location Services parameters

If Location Services mode (LSC_mode) is enabled and a user attempts to change the
early_classmark_sending parameter to a value which does not support early classmark
sending on both the A-interface and the Air-interface, the command shall be rejected
and an error message shall be displayed.

If Location Services mode is enabled and a user attempts to change the

phase2_classmark_allowed parameter to a value which does not support multiband, the
command is rejected and an error message is displayed.

If a user changes the opc parameter to the same value as the Lb Interface DPC, a warning
message is displayed indicating the effects of the modification.

If a user attempts to change the ss7_mode parameter to a value which would cause the
Lb Interface DPC to be out of range, the command is rejected and an error message is
displayed.

Methods for configuring Location Services

The Location Services feature can be configured using:

OMC-R GUI, using the LCS grouping parameters in the BSS Detailed View and the fields
detailed in Table 2-18.

TTY interface, see Configuring Location Services using the TTY interface.

Configuring GSM Location Services using the TTY interface

Using chg_ and disp_element to change Location Services parameters
and timers
The chg_element and disp_element commands can be used to configure and change the
Location Services-related parameters shown in Table 2-18. Some examples are also given
in the following sections.
The chg_element and disp_element commands are only accepted at certain locations.
Table 2-19 shows the accepted locations.

Table 2-19 chg_element and disp_element accepted locations

Command

BTS

BSC

RXCDR

chg_element
disp_element
See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS
commands, prompts, and parameters.

68P02901W17-T

2-111
Jan 2010

Configuring GSM Location Services using the TTY interface

Chapter 2: Configuring BSS Features

Displaying the current BSS Location Services mode

Use the disp_element command to display the Location Services mode of the BSS. For example,
the following command displays the current Location Services mode.
disp_element lcs_mode bsc
The system replies, for example:
lcs_mode = 1

Setting the BSS Location Services mode

In SYSGEN mode, use the chg_element command to change the Location Services mode of the
BSS. For example, the following command changes the Location Services mode to 1 (Location
Services enabled, BSC supports a NSS-based SMLC):
chg_element lcs_mode 1 bsc

Displaying and changing lcs_perf_location timer

To display and change the Location Services perform location timer, use the disp_element and
chg_element, respectively.
For example, the following command displays the current setting:
disp_element lcs_perf_location bsc
The system replies, for example:
lcs_perform_location = 50000
The following command changes the value of lcs_perf_location to 60,000 ms:
chg_element lcs_perf_location 60000 bsc

2-112

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Enhanced GPRS One Phase Access

Enhanced GPRS One Phase Access

Overview of Enhanced GPRS One Phase Access

In a GPRS network there are two packet access procedures a mobile station (MS) can use to
establish an uplink Temporary Block Flow (TBF). The packet access can be done in either one
phase or two phases. Until now the GPRS architecture only supported the two-phase access
process. The Enhanced GPRS One Phase Access feature provides the one phase access, and also
provides improvements to both procedures.
To summarize, the Enhanced GPRS One Phase Access feature provides:

The one phase uplink TBF access procedure, also see GPRS Interleaving TBFs on page 2-89.

A performance enhancement to the phase uplink TBF access procedure (optional feature).

Modifications to the current two-phase uplink TBF access procedure.

Modifications to polling of downlink assignment messages.

Introduce uplink congestion management functionality.

For further details of the Enhanced GPRS One Phase Access feature, see Technical Description:
BSS Implementation (68P02901W36).

Enhanced GPRS One Phase Access dependencies

The Enhanced GPRS One Phase Access requires the GPRS feature (gprsOpt) to be unrestricted
(enabled).

Enhanced GPRS One Phase Access parameters

Table 2-20 lists the parameters associated with the Enhanced GPRS One Phase Access feature.
Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter
name. For further details of these and other parameters, see Technical Description: BSS
Command Reference (68P02901W23).

68P02901W17-T

2-113
Jan 2010

Enhanced GPRS One Phase Access parameters

Chapter 2: Configuring BSS Features

Table 2-20 Enhanced GPRS One Phase Access parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

BSS parameters:
Enhanced One Phase
Access Feature
(OMC-R parameter name:
eopOpt)

Displayed in the Optional Features grouping

of the BSS Detailed View form.
Indicates whether the Enhanced GPRS One
Phase Access feature is restricted (disabled)
or unrestricted (enabled) in the BSS software.
This parameter cannot be modified by a user.
The field is grayed-out in the OMC-R GUI if
the GPRS feature is restricted (disabled).

0 or 1, where:
Disabled (0).
Enabled (1).
Default is
Disabled (0).

Enhanced One Phase

Access
eop_enabled

Displayed in the GPRS grouping of the BSS

Detailed View form. Indicates whether
Enhanced GPRS One Phase Access feature is
enabled or disabled for the BSS.
This parameter can be modified by a user.
The field is grayed-out in the OMC-R GUI
if the Enhanced GPRS One Phase Access
Feature (eopOpt) and GPRS feature are
restricted (disabled). The QoS feature (see
Quality of Service (QoS) on page 2-154)
modifies the behavior of this parameter.
If bssgp_pfc_bit is set to On (1), any
modification to eop_enabled is overridden. If
eop_enabled is modified and saved while QoS
is enabled and bssgp_pfc_bit is set to on (1),
the following message is displayed: WARNING:
Changes to eop_enabled are overridden
while QoS is enabled.

0 or 1, where:
Disabled (0).
Enabled (1).
Default is
Disabled (0).

Displayed in the GPRS grouping of the CELL

Detailed View form.
The maximum number of non-BCCH timeslots
allowed to be in preload USF (Uplink State
Flag) active state in the cell at the same
time. (That is, the number of non-BCCH
timeslots that are broadcast continuously at
full power even when no mobile is active on
the timeslot.)
Can only be modified, if the GPRS Feature
(gprsOpt) and Enhanced GPRS One Phase
feature are unrestricted (Enabled) in the
BSS Detailed View and GPRS Enabled
(gprs_enabled) is Yes (1) in the CELL
Detailed View. Otherwise, the field is
grayed-out in the CELL Detailed View form.

0 - 3.
If not set by a user
at cell creation
time, defaults to 1
timeslot.

CELL parameters:
Number of TS In Pre-load
USF Active State
ts_in_usf_active

2-114

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Methods of configuring Enhanced GPRS one phase access

Methods of configuring Enhanced GPRS one phase access

Enhanced GPRS one phase access can be configured using:

OMC-R GUI BSS and CELL Detail Views and the fields shown in Table 2-20.

TTY interface, see Configuring Enhanced GPRS one phase access using the TTY
interface.

Configuring Enhanced GPRS one phase access using the TTY

interface
Checking if Enhanced GPRS one phase access is unrestricted
To check if the Enhanced GPRS one phase access feature is unrestricted (enabled) using the
TTY interface, enter the following command:
disp_options
If Enhanced GPRS one phase access is unrestricted, the following is displayed:
44 Enhanced One Phase Access

Displaying and modifying Enhanced GPRS one phase access parameters

The disp_element, disp_cell, chg_element and chg_cell_element commands can be used to
display and configure the Enhanced GPRS one phase access BSS and cell parameters shown in
Table 2-20. Some examples are also given in the following sections.
See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS
commands, prompts, and parameters.

Displaying whether Enhanced GPRS One Phase Access is enabled at a BSS

Use the disp_element command to display whether Enhanced GPRS One Phase Access
is enabled for a BSS. For example, the following command displays the current setting of
eop_enabled:
disp_element eop_enabled 0
The system replies, for example:
eop_enabled = 1

68P02901W17-T

2-115
Jan 2010

Configuring Enhanced GPRS one phase access using the TTY interface

Chapter 2: Configuring BSS Features

Displaying the current setting of ts_in_usf_active

Use the disp_element command to display the value of ts_in_usf_active. For example, the
following command displays the current value of ts_in_usf_active at site 1:
disp_element ts_in_usf_active 1 cell_number = 0010111
The system replies, for example:
ts_in_usf_active = 1

Setting BSS and cell parameters for Enhanced GPRS One Phase Access
Use the chg_element command to change Enhanced GPRS One Phase Access BSS parameters
and chg_cell_element command to change Enhanced GPRS One Phase Access cell parameter.
For example, the following command changes eop_enabled to 1:
chg_element eop_enabled 1 0
The following command changes ts_in_usf_active to 2 at cell 0010111:
chg_cell_element ts_in_usf_active 2 0 0 1 0 1 1 1

2-116

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH feature

PBCCH/PCCCH feature

Overview of PBCCH/PCCCH feature

Packet Broadcast Control Channel/Packet Common Control Channel (PBCCH/PCCCH) is the
packet data logical channels dedicated to GPRS signaling. When the PBCCH/PCCCH feature
is configured for a cell, the MS reads system information on PBCCH and performs packet
access activities on PCCCH.
Table 2-21 shows the functionality of each packet logical channel on PBCCH/PCCCH.

Table 2-21 PBCCH/PCCCH parameters

Packet Transfer Direction

Functionality

Uplink only

Used by MS to initiate uplink

transfer for data or signaling
information.

Packet Access Grant Channel

(PAGCH) (on PCCCH)

Downlink only

Used by BSS to send resource

assignment to an MS before
packet transfer.

Packet Paging Channel

(PPCH) (on PCCCH)

Downlink only

Used by BSS to page an MS

for Packet Switched (PS) or
Circuit Switched (CS).

Packet Broadcast Control

Channel (PBCCH)

Downlink only

Used by BSS to broadcast

packet data-specific System
Information.

Packet Notification Channel

(PNCH)

Downlink only

Not supported.

Packet Logical Channels

Packet Random Access
Channel (PRACH) (on
PCCCH)

If the PBCCH/PCCCH feature is not configured for a cell, GPRS-related information is broadcast
on the Broadcast Control Channel (BCCH) and GPRS-accessing signaling is conducted on the
Common Control Channel (CCCH) channels.
In a lightly loaded GSM/GPRS network, BCCH/CCCH has sufficient signaling capacity for both
GSM and GPRS. In a highly loaded GSM/GPRS network, PBCCH/PCCCH provides more signaling
capabilities for both the GSM voice and GPRS service. In addition, if PBCCH/PCCCH is enabled,
there is reduced internal traffic over the GPRS Signaling Link (GSL) and Radio Signaling Link
(RSL) because there are fewer requests, assignments, or paging messages over GSL and RSL.
The PBCCH/PCCCH feature also facilitates both MS controlled (C31/C32) and network
controlled cell reselection (PSI 3, PSI 3bis and PSI 5) by broadcasting cell reselection
parameters to the MS.

68P02901W17-T

2-117
Jan 2010

Prerequisites to configuring PBCCH/PCCCH

Chapter 2: Configuring BSS Features

When the PBCCH/PCCCH feature is enabled, a BSS supports the following messages:

PSI1.

PSI2.

PSI3.

PSI3bis.

PSI3quater.

PSI5.

PSI8.

PSI3ter, PSI4, PSI6, and PSI7 messages are not supported. PSI13 is supported on PACCH.
For a full description of the PBCCH/PCCCH feature, see Technical Description: BSS
Implementation (68P02901W36).

Prerequisites to configuring PBCCH/PCCCH

Before configuring the PBCCH/PCCCH feature, ensure that the following have been enabled
at the BSS:

PBCCH/PCCCH Feature (pccchOpt).

GPRS Feature (gprsOpt).

PBCCH/PCCCH can only be enabled for a cell, if the cell:

Operates in the normal range. That is, ext_range_cell must set to 0 meaning Extended
Range Cell is disabled.

BCCH carrier is non-hopping.

If the cell parameter GPRS enabled (gprs_enabled) is set to 1 (Enabled), the cell parameter:
PBCCH/PCCCH enabled (pccch_enabled) cannot be modified.
To change PBCCH/PCCCH for a GPRS cell, use the following procedure:

Procedure 2-3 Change PBCCH/PCCCH for a cell

2-118

Set gprs_enabled to 0 (Disabled).

Set pccch_enabled to 1 (Enabled).

Set gprs_enabled to 1 (Enabled).

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Determining whether PBCCH/PCCCH is unrestricted at the BSS

Determining whether PBCCH/PCCCH is unrestricted at the BSS

PBCCH/PCCCH is an optional feature, which must be unrestricted at the BSS before it can be
used.

Using the OMC-R GUI

To check if PBCCH/PCCCH feature is unrestricted at the BSS using the OMC-R GUI, display the
setting of the PBCCH/PCCCH Feature field (pccchOpt) in the Optional Features grouping in the
BSS Detailed View. The values are:

Disabled (0).

Enabled (1).

The default is Disabled (0).

Using the TTY interface

To check if PBCCH/PCCCH is unrestricted using the TTY interface, enter the following command:
disp_options all
If the PBCCH/PCCCH optional feature is unrestricted, and is therefore enabled at the BSS, the
system displays the following in the unrestricted list:
<51> PBCCH/PCCCH

PBCCH/PCCCH parameters
Table 2-22 details the PBCCH/PCCCH parameters. For further details of these and other
parameters, see Technical Description: BSS Command Reference (68P02901W23).

Table 2-22 PBCCH/PCCCH parameters

OMC-R GUI field name/BSS
parameter name

Description

BSS parameters:
PBCCH/PCCCH Feature
pccchOpt

Displayed in the Optional Features grouping in the BSS

Detailed View.
Indicates whether the PBCCH/PCCCH feature is enabled for
the BSS. Valid values are 0 or 1, where:

0 - Disabled.

1 - Enabled.
Continued

68P02901W17-T

2-119
Jan 2010

PBCCH/PCCCH parameters

Chapter 2: Configuring BSS Features

Table 2-22 PBCCH/PCCCH parameters (Continued)

OMC-R GUI field name/BSS
parameter name
SGSN Release
sgsn_release

Description
Displayed in the GPRS grouping in the BSS Detailed View.
Specifies the SGSN release version.
Valid values are 0 - 2
Default is 0
0 - SGSN is compliant with 3GPP release 1998 or older.
1 - SGSN is compliant with 3GPP release 1999 to any version
before Release 6.
2 - SGSN is compliant with 3GPP release 6 to newer.

CELL parameters:
PBCCH/PCCCH enabled
pccch_enabled

Displayed in the GPRS grouping in the CELL Detailed View.

Indicates whether the PBCCH/PCCCH feature is enabled for
the cell. Valid values are 0 or 1, where:

0 - False.

1 - True.

when:
PBCCH/PCCCH feature is unrestricted.
gprs_enabled is 0.
BSS has configured the BCCH carrier of a cell as a
non-hopping carrier.
Cell is a normal range cell.
ts_sharing is set to 0 (Disabled) on the same cell site.
Number of PCCCH Timeslots
bs_pcc_chans

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the number of PCCCH timeslots. Indicates the
number of physical channels carrying PCCCHs including the
physical channel carrying the PBCCH.
Valid value is 1. Default: 1.

Number of Blocks Allocated

to PBCCH
bs_pbcch_blks

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the number of PBCCH blocks per
52-frame-multiframe.
Valid values are 1 - 4. Default: 2.

Number of PAGCH Blocks per

Multiframe
bs_pag_blks_res

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the number of PAGCH blocks per
52-frame-multiframe. Can only be set to a value of
(bs_pbcch_blks + bs_pag_blks_res) within range of 1 - 11.
Valid values are 0 - 10. Default: 3.

Number of PRACH Blocks

per Multiframe
bs_prach_blks

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the number of PRACH blocks per
52-frame-multiframe.
Valid values are 1 - 12. Default: 4.
When psi1_repeat_period is set to 1, bs_pbcch_blks cannot
be set to 1 or 2.
Continued

2-120

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH parameters

Table 2-22 PBCCH/PCCCH parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Time Interval for Scheduling

PSI Messages
psi1_repeat_period
(OMC-R parameter name:
psi1_repeat_prd)

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the time interval between consecutive PSI 1
messages in 52-multiframes.
Valid values are 0 - 16. Default: 5.
If in range 1 - 16, the BSS uses the value of psi1_repeat_period
to scheduling PSI messages. If psi1_repeat_period is
0, the BSS algorithmically determines the value of
psi1_repeat_period based upon the value of bs_pbcch_blks
and the number of PSI instances in low repetition rate group.
When psi1_repeat_period is set to 1, bs_pbcch_blks cannot
be set to 1 or 2.

Non-DRX Mode Transfer

Period Duration
pccch_drx_timer_max
(OMC-R parameter name:
pccch_drx_max_t)

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the duration of the transfer non-DRX mode period
on PCCCH. This field is the binary representation of the
parameter DRX_TIMER_MAX.
Valid values are 0 - 7, where:

0 = 0 seconds.

1 = 1 second.

2 = 2 seconds.

3 = 4 seconds.

4 = 8 seconds.

5 = 16 seconds.

6 = 32 seconds.

7 = 64 seconds.
Continued

68P02901W17-T

2-121
Jan 2010

PBCCH/PCCCH parameters

Chapter 2: Configuring BSS Features

Table 2-22 PBCCH/PCCCH parameters (Continued)

OMC-R GUI field name/BSS
parameter name
Slots Between Channel
Request
prach_s

Persistence Level 1 to 4
persistence_lvl_0
persistence_lvl_1
persistence_lvl_2
persistence_lvl_3

Description
Displayed in the GPRS grouping in the CELL Detailed View.
Specifies the minimum number of frames between two
successive Packet Channel Request messages.
Valid values are 0 - 9, where:

0 - S = 12.

1 - S = 15.

2 - S = 20.

3 - S = 30.

4- S = 41.

5 - S = 55.

6 - S = 76.

7 - S = 109.

8 - S = 163.

9 - S = 217.

Displayed in the GPRS grouping in the CELL Detailed View.

Specify the values of the access persistence level P(i) for each
priority i (i = 1 to 4), where radio priority 1 represents the
highest radio priority.
Valid values are 0 - 15, where:

0 - persistence level 0.

1 - persistence level 1.

2 - persistence level 2.

...

14 - persistence level 14.

15 - persistence level 16.

Continued

2-122

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH parameters

Table 2-22 PBCCH/PCCCH parameters (Continued)

OMC-R GUI field name/BSS
parameter name
Retransmissions Allowed for
Radio Priority 1 to 4
prach_mx_retran_0
prach_mx_retran_1
prach_mx_retran_2
prach_mx_retran_3

Slots to Spread Random

Access Transmission
prach_tx_int

GPRS Minimum Receive

Level
gprs_rxlev_access_min
(OMC-R parameter name:
gprs_rxlev_ac_min)

Description
Displayed in the GPRS grouping in the CELL Detailed View.
Specifies the maximum number of retransmissions allowed for
each radio priority i, where radio priority 1 represents the
highest radio priority.
Valid values are 0 - 3, where:

0 - 1 retransmission allowed.

1 - 2 retransmissions allowed.

2 - 4 retransmissions allowed.

3 - 7 retransmissions allowed.

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the number of frames to spread transmission of the
random access.
Valid values are 0 - 15, where:

0 - two slots used to spread transmission.

1 - three slots used to spread transmission.

2 - four slots used to spread transmission.

...

8 - 10 slots used to spread transmission.

9 -12 slots used to spread transmission.

10 - 14 slots used to spread transmission.

11 - 16 slots used to spread transmission.

12 - 20 slots used to spread transmission.

13 - 25 slots used to spread transmission.

14 - 32 slots used to spread transmission.

15 - 50 slots used to spread transmission.

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the minimum received signal level at the MS
required to access the system.
Valid values are 0 - 63 (representing -110 dB to -47 dB).
Default: 0.
Continued

68P02901W17-T

2-123
Jan 2010

PBCCH/PCCCH parameters

Chapter 2: Configuring BSS Features

Table 2-22 PBCCH/PCCCH parameters (Continued)

OMC-R GUI field name/BSS
parameter name
GPRS MS Max Transmit
Power
gprs_ms_txpwr_max_cch
(OMC-R parameter name:
gprs_mx_txpwr_cch)

Description
Displayed in the GPRS grouping in the CELL Detailed View.
Specifies the maximum power level an MS may use when
accessing the system.
Valid values are 0 - 31.
The valid range depends on the value of frequency_type,
that is, whether a cell is PGSM and EGSM, DCS1800, or PCS
1900. Defaults:

22 for PGSM and EGSM.

0 for DCS1800.

30 for PCS1900.

HCS Priority Class

priority_class

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the Hierarchical Cell Structures (HCS) priority class.
Valid values are 0 - 7. Default: 0 (Lowest Priority).

HCS Signal Strength

hcs_thr

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the HCS signal strength threshold. Each step is + 2
dBm.
Valid values are 0 - 31, where:

0 means -110 dBm.

1 means -108 dBm.

...

31 means -48 dBm.

GPRS Cell Reselect

Displayed in the GPRS grouping in the CELL Detailed View.
Hysteresis
Specifies the additional hysteresis that applies in ready state
gprs_cell_reselect_hysteresis for cells in the same Routing Area (RA).
(OMC-R parameter name:
Valid values are 0 - 7, where:
gprs_reselect_hys)

0 = 0 dB.

C32 Exception Rule

c32_qual

1 = 2 dB.

2 = 4 dB.

...

7 = 14 dB.

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the exception rule for gprs_reselect_offset.
Valid values are 0 or 1, where:

0 - Exception not allowed.

1 - Exception allowed.
Continued

2-124

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH parameters

Table 2-22 PBCCH/PCCCH parameters (Continued)

OMC-R GUI field name/BSS
parameter name
C31 Hysteresis
c31_hyst

Routing Area Reselect

Hysteresis
ra_reselect_hysteresis
(OMC-R parameter name:
ra_reselect_hyst)

GPRS Negative C32 Offset

gprs_temporary_offset
(OMC-R parameter name:
gprs_temp_offset)

GPRS Penalty Time

gprs_penalty_time

Description
Displayed in the GPRS grouping in the CELL Detailed View.
Specifies if hysteresis is applied to C31.
Valid values are 0 or 1, where:

0 - Hysteresis is not applied to C31.

1 - Hysteresis is applied to C31.

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the additional hysteresis that applies when selecting
a cell in a new routing area.
Valid values are 0 - 7, where:

0 = 0 dB.

1 = 2 dB.

2 = 4 dB.

...

7 = 14 dB.

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the negative offset to C32 that the MS uses for
duration of gprs_penalty_time. Valid values are 0 - 7, where:

0 = 0 dB.

1 = 10 dB.

2 = 20 dB.

3 = 30 dB.

...

6 = 60 dB.

7 = infinity.

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the length of time for which gprs_temporary_offset
is active. One step equals 10 seconds. Valid values are 0 31, where:

0 = 10 seconds.

1 = 20 seconds.

...

31 = 320 seconds.
Continued

68P02901W17-T

2-125
Jan 2010

PBCCH/PCCCH parameters

Chapter 2: Configuring BSS Features

Table 2-22 PBCCH/PCCCH parameters (Continued)

OMC-R GUI field name/BSS
parameter name
GPRS Cell Reselect Offset
gprs_reselect_offset
(OMC-R parameter name:
gprsReselectOffs)

3G Cell Threshold for

Multi-RAT MS
qsearch_p

Description
Displayed in the GPRS grouping in the CELL Detailed View.
Specifies the negative or positive offset and a hysteresis to the
GPRS cell reselection criteria.
Valid values are 0 - 31, where:

0 = -52 dB.

1 = -48 dB.

...

10 = -12 dB.

11 = -10 dB.

...

22 = +12 dB.

23 = +16 dB.

...

31 = +48 dB.

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the threshold for a multi-RAT MS to search for 3G
cells.
Valid values are 0 - 15, where:

Search for 3G cells if the signal level is below a threshold

of:
0 : -98 dBm.
1 : -94 dBm.
2 : -90 dBm.
3 : -86 dBm.
4 : -82 dBm.
5 : -78 dBm.
6 : -74 dBm.
7 : Infinity, always search for 3G cells.

Search for 3G cells if the signal level is above a threshold

of:
8 : -78 dBm.
9 : -74 dBm.
10 : -70 dBm.
11 : -66 dBm.
12 : -62 dBm.
13 : -58 dBm.
14 : -54 dBm
15 : Infinity, never search for 3G cells.
Continued

2-126

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Methods for configuring PBCCH/PCCCH

Table 2-22 PBCCH/PCCCH parameters (Continued)

OMC-R GUI field name/BSS
parameter name
Allow Search for 3G Cells
search_prio_3g

FDD Cell Reselection Offset

fdd_gprs_qoffset

Description
Displayed in the GPRS grouping in the CELL Detailed View.
Indicates whether 3G cells are searched when BSIC decoding
is required.
Valid values are 0 or 1, where:

0 - False (not searched).

1 - True (searched).

Displayed in the GPRS grouping in the CELL Detailed View.

Specifies the offset to RLA_P for cell reselection to access
technology/mode FDD.
Valid values are 0 - 15, where:

0 = - infinity (always select a cell if acceptable).

1 = -28 dB.

2 = -24 dB.

3 = -20 dB.

...

8 = 0 dB.

9 = 4 dB.

...

15 = 28 dB.

Methods for configuring PBCCH/PCCCH

The PBCCH/PCCCH feature can be configured using:

OMC-R GUI, using the BSS Detailed View (Optional Features and GPRS groupings), and
CELL Detailed View (GPRS grouping), and the fields detailed in Table 2-22.

TTY interface, see Configuring PBCCH/PCCCH using TTY interface.

68P02901W17-T

2-127
Jan 2010

Configuring PBCCH/PCCCH using TTY interface

Chapter 2: Configuring BSS Features

Configuring PBCCH/PCCCH using TTY interface

Using chg_ and disp_element commands
The chg_element and disp_element commands can be used to configure and change the
PBCCH/PCCCH parameters shown in Table 2-22. Some examples are also given in the following
sections. See Technical Description: BSS Command Reference (68P02901W23) for full details of
BSS commands, prompts, and parameters.
For example, use the following disp_element command to display the current setting of the
parameter: GPRS Network Operation Mode (gprs_network_operation_mode):
disp_element gprs_network_operation_mode 0
The system replies, for example:
gprs_network_operation_mode = 3
To change the setting of gprs_network_operation_mode to 1, use the following command:
chg_element gprs_network_operation_mode 1 0

Enabling PBCCH/PCCCH at a cell

Use the chg_element command to change the cell parameter: PBCCH/PCCCH enabled. For
example, the following command enables the PBCCH/PCCCH feature at cell 0010111:
chg_element pccch_enabled 1 1 cell_number = 0 0 1 0 1 1 1
The following example illustrates the system response if an attempt is made to modify
pccch_enabled when gprs_enabled is 1 (enabled):
chg_element pccch_enabled 1 1 cell_number = 0 0 1 0 1 1 1
ERROR: gprs_enabled must be disabled before pccch can be enabled.
COMMAND REJECTED

Changing the time interval for scheduling PSI messages

Use the chg_element command to change the Time Interval for Scheduling PSI Messages
(psi1_repeat_period) parameter. For example, the following command changes the time
interval for scheduling PSI messages to 1 at the cell 0010111 when bs_pbcch_blks is set
to 3 or 4:
chg_element psi1_repeat_period 1 1 cell_number = 0 0 1 0 1 1 1
COMMAND ACCEPTED.

2-128

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adaptive Multi-Rate (AMR)

Adaptive Multi-Rate (AMR)

Overview of the AMR feature

AMR Full Rate (FR) channel mode
The AMR feature improves overall speech quality. Unlike existing GSM speech Codec (FR and
EFR), which operate at a fixed rate and constant error protection level, the AMR speech Codec
includes a set of fixed rate speech Codec modes for full rate operation with the possibility to
switch between the different channel coding modes as a function of the propagation error
conditions. Each Codec mode provides a different level of error protection through a dedicated
distribution of the available gross bit rate between source coding and channel coding. The
actual speech rate used for each speech frame depends on the existing radio channel and traffic
conditions. Table 2-23 shows the Full Rate and Half Rate Codec modes. In Table 2-23, a high the
bit rate mode means high speech rate but low error correction rate.

Table 2-23 Active Codec set modes

Codec mode value

Meaning (kbit/s)

Available at Full
Rate (FR)

Available at Half
Rate (HR)

12.20

YES

NO

10.20

YES

NO

7.95

NO

YES

7.4

YES

YES

6.7

YES

YES

5.9

NO

YES

5.15

YES

YES

4.75

NO

NO

AMR Half Rate (HR) channel mode

AMR Half Rate (HR) for speech feature provides enhanced capacity over the air interface and
speech quality by means of Codec mode adaptation. AMR selects the optimum channel (HR
or FR) and Codec to deliver the best combination of speech quality and system capacity. AMR
Half Rate offers capacity increase over the air interface relative to FR or EFR by pairing half
rate channels together within one air timeslot.
AMR Half Rate (HR) channel mode allows two AMR calls to be placed on a single air interface
timeslot. This increases cell capacity without the need for extra radio hardware. When AMR
Half Rate is enabled, the BCCH and SDCCH channels in any cell operate identically for Full
Rate and Half Rate, however, the requirement for SDCCHs may increase. The dual rate channel
allocation algorithm pairs a half rate speech with another half rate channel. This algorithm can
be manually controlled or automatically controlled by a predefined traffic threshold.

68P02901W17-T

2-129
Jan 2010

Link Adaptation

Chapter 2: Configuring BSS Features

AMR Half Rate and GSM Half Rate

The GSM Half Rate feature builds on the AMR Half Rate feature. It uses new attributes and
associated groups to configure GSM Half Rate and modifies a number of existing AMR Half
Rate attributes, making them generic. Full details about GSM Half Rate feature can be found
in GSM Half Rate on page 2-140.

AMR hardware and software utilization

The AMR feature is only available on the following radio platforms:

CTU.

CTU2.

TCU-A.

TCU-B.

The BSC and RXCDR software supports 8 kbit/s switching so that half-rate enabled RTFs are
provisioned on only two E1 timeslots between the BSC and BTS, that is, 8 kbit/s backhaul is
utilized. However, 7.95 capable RTFs are provisioned on an additional two E1 timeslots between
the BSC and BTS, because 7.95 kbit/s mode only fits in 16 kbit/s TRAU frame format between
the BSC and BTS. The GPD2 boards are used to double the transcoding capability. Each GDP2
board can handle up to 60 channels. The backhaul saving is achieved by replacing KSWs with
DSWs in the BSC and RXCDR.

Link Adaptation
Full Rate Link Adaptation
When Full Rate Link Adaptation is used in conjunction with AMR, speech quality in poor RF
environments is improved by adapting the speech rates and level of error correction on a call.
For example, in a poor RF environment speech quality is reduced by reducing the speech rate
and increasing the level of error correction.
Full Rate AMR Link Adaptation enables the BSS to adapt the speech Codec modes in an AMR
codec set on the uplink and downlink of an AMR FR call to provide the most suitable level of
error correction for the RF environment. Uplink and Downlink Codec modes are considered
separately and can be adapted separately. With Full Rate Link Adaptation up to four Codec
modes can be included in the Full Rate Active Codec Set for a cell. A call is then adapted over
this Active Codec Set according to the quality of the link between the mobile and the BSS.
The Full Rate Codec modes supported are shown in Table 2-23.

2-130

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

AMR Full Rate - MS Monitor function

Half Rate Link Adaptation

Half Rate AMR Link Adaptation provides similar functionality to the Full Rate AMR Link
Adaptation, but for the Half Rate AMR channel.
In Half Rate AMR Link Adaptation there is a different Half Rate Active Codec Set, which can
contain up to four of the Half Rate Codec modes supported in the Hardware Capable Codec Set
for the CTU/TCU-B/TCU-A platforms. The Half Rate Codec modes supported in the Hardware
Capable Codec Set for the CTU/TCU-B/TCU-A radios are shown in Table 2-23. There is also a
different Half Rate Initial Codec Mode and different uplink and downlink Codec mode thresholds
and hysteresis values for Half Rate AMR calls. GSM Handover and Power Control algorithms
are used for the Half Rate AMR channel, but additional Handover and Power control thresholds
are used.

AMR Full Rate - MS Monitor function

MS Monitor compensates for the inability of some mobiles to accurately estimate the current
conditions of the channel it is using. MS Monitor adjusts the downlink Codec mode adaptation
thresholds during a call so that the MS is able to correctly adapt across the Active Code Set
(ACS) as needed. MS Monitor monitors a mobile during a call and detects conditions that
indicate the downlink Codec mode adaptation thresholds need adjusting. MS Monitor then
decreases the thresholds at the MS if they are too high, and increases the thresholds if they
are too low.

AMR Enhanced GDP feature

AMR Enhanced GDP feature is the AMR feature with enhanced transcoding configuration of
GDPs (GDP pairing).
Enhanced GDP refers to the firmware configuration of the GDP board, where each of the 15
DSPs on the GDP board is only capable of supporting the transcoding function for a single
channel of GSM speech (AMR, FR and EFR) and Phase 2 data services. To offer 30 channels of
enhanced transcoding using the same E1 span line to the MSC, enhanced GDPs are equipped as
pairs, each providing half of the transcoding resources.

AMR Enhanced Capacity feature

AMR Enhanced Capacity feature is configured on the DSW and DSWX, where timeslots for a
double rate TDM bus (twice the rate of a single-rate bus) can have the bit rate reduced so that
the timing of the signals within the cage is appropriate for existing boards (for example, MSI,
XCDR, GDP, GPROC2), which do not support the double-capacity mode. GDP2s can therefore
occupy the same cages as these existing boards.

Technical description of AMR

A full technical description of AMR can be found in Technical Description: BSS Implementation
(68P02901W36).

68P02901W17-T

2-131
Jan 2010

Prerequisites for enabling AMR

Chapter 2: Configuring BSS Features

Prerequisites for enabling AMR

AMR can only be enabled for a BSS, if its Assoc_RXCDR has CIC Validation (cic_validation)
enabled.
If a site contains Horizonmacro and/or M-Cell2/6 type cabinets, including Horizonmacro
Extension cabinets, the site is AMR capable. The AMR associated Cell and RTF parameters
can only be modified if the container site is AMR capable, and the AMR feature (amrOpt) is
unrestricted (Enabled) for the NE.

Configuring AMR at a cell

AMR is an optional feature for a BSS. If the AMR feature is unrestricted (Enabled) at the BSS,
then AMR Full Rate and AMR Half Rate can be enabled or disabled on a BSS and Cell basis.
When a cell is created, the following can be defined:

A set of Active Codec Modes for calls on the carriers of the cell (separate Active Codec
Sets can be defined for Full and Half Rate).

Initial Codec modes for both Half Rate and Full Rate.

Uplink and downlink thresholds for mode adaptation between Codec modes in the Active
Codec Set.

These settings can also be modified to fine tune performance as required.

Within the Cell, RTFs can then be configured to be Half Rate channel mode capable.

Determining whether the AMR features are unrestricted

AMR, AMR Enhanced GDP, AMR Enhanced Capacity, AMR TCU-A, and AMR TCU-B are optional
features, which must be unrestricted before they can be used.

Using the OMC-R GUI

To check if AMR, AMR Enhanced GDP, AMR Enhanced Capacity, AMR TCU-A, and AMR TCU-B
features are unrestricted using the OMC-R GUI, display the settings of the following fields in the
Optional Features grouping in the BSS Detailed View:

2-132

AMR Feature (amrOpt).

AMR Enhanced GDP Feature (amrEGDPProOpt).

AMR Enhanced Capacity Feature (amrEnhancedCapOpt).

AMR TCU-A Feature (amrTCUAOpt).

AMR TCU-B Feature (amrTCUBOpt).

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

AMR parameters

The values for these fields are:

Disabled (0) - meaning the feature is restricted.

Enabled (1) - meaning the feature is unrestricted.

The default for these fields is Disabled (0), and cannot be changed by a user.

Using the TTY interface

To check if AMR features are unrestricted using the TTY interface, enter the following command:
disp_options all
If an AMR feature is unrestricted, the system displays it in the Unrestricted list. For example, if
all the AMR features are unrestricted, the following would be included in the unrestricted list:
<feature no.> AMR
<feature no.> AMR Using Enhanced GDP
<feature no.> AMR Enhanced Capacity
<feature no.> TCU-A support for AMR
<feature no.> TCU-B support for AMR

AMR parameters
Table 2-24 lists the parameters associated with configuring AMR.

Table 2-24

AMR parameters

BSS parameter name

Details

AMR BSS parameters:

amrOpt

Displayed in the Optional Features grouping of the

BSS Detailed View. Indicates whether the Adaptive
Multi-Rate (AMR) feature is restricted (Disabled) or
unrestricted (Enabled) for the BSS.

amrEGDPProOpt

Displayed in the Optional Features grouping of the

BSS Detailed View. Indicates whether the Adaptive
Multi-Rate (AMR) using Enhanced GDP feature is
restricted (Disabled) or unrestricted (Enabled) for
the BSS.

amrEnhancedCapOpt

Displayed in the Optional Features grouping of the

BSS and RXCDR Detailed View. Indicates whether
the Adaptive Multi-Rate (AMR) Enhanced Capacity
feature is restricted (Disabled) or unrestricted
(Enabled) for the BSS or RXCDR. If this feature
is enabled, the RXCDR supports 4800 CICs and 8
kbit/s switching.
Continued

68P02901W17-T

2-133
Jan 2010

AMR parameters

Chapter 2: Configuring BSS Features

Table 2-24

AMR parameters (Continued)

Details

BSS parameter name

amrTCUAOpt

Displayed in the Optional Features grouping of the

BSS Detailed View. Indicates whether the Adaptive
Multi-Rate (AMR) TCU-A feature is restricted
(Disabled) or unrestricted (Enabled) for the BSS. If
this feature is enabled, TCU-A support for AMR is
provided.

amrTCUBOpt

Displayed in the Optional Features grouping of the

BSS Detailed View. Indicates whether the Adaptive
Multi-Rate (AMR) TCU-B feature is restricted
(Disabled) or unrestricted (Enabled) for the BSS. If
this feature is enabled, TCU-B support for AMR is
provided.

Half Rate AMR BSS parameters:

amr_bss_half_rate_enabled
force_hr_usage

See BSS Detailed View fields - ( Channel Mode

Usage (AMR Full Rate and Half Rate/GSM Half
Rate) grouping on page 4-35) for details of these
parameters.

Full Rate AMR BSS parameters:

amr_bss_full_rate

See BSS Detailed View fields - ( Channel Mode

Usage (AMR Full Rate and Half Rate/GSM Half
Rate) grouping on page 4-35) for details of these
parameters.

Link Adaptation BSS parameters:

amr_dl_thresh_adjust
amr_dl_la_mode_chg_min

See BSS Detailed View fields - ( Channel Mode

Usage (AMR Full Rate and Half Rate/GSM Half
Rate) grouping on page 4-35) for details of these
parameters.

Downlink Adaptation MS Monitor BSS parameters:

amr_ms_monitor_period
amr_ms_high_cmr
amr_ms_low_cmr
amr_ms_high_rxqual
amr_ms_low_rxqual

See BSS Detailed View fields - ( Channel Mode

Usage (AMR Full Rate and Half Rate/GSM Half
Rate) grouping on page 4-35) for details of these
parameters.

General AMR Cell parameters:

hr_fr_hop_count

See CELL Detailed View fields, General - ( Channel

Mode Usage (AMR Full Rate and Half Rate/GSM
Half Rate) grouping on page 8-32) for further details.

Full Rate AMR Cell parameters:

amr_full_rate

See CELL Detailed View fields, General - ( AMR Full

Rate grouping on page 8-33) for details.
Continued

2-134

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 2-24

AMR parameters

AMR parameters (Continued)

Details

BSS parameter name

Half Rate AMR Cell parameters:
amr_half_rate_enabled
hr_res_ts
hr_intracell_ho_allowed
inner_hr_usage_thres
new_calls_hr
reconfig_fr_to_hr

See CELL Detailed View fields, General - grouping

( AMR/GSM Half Rate grouping on page 8-39) for
details of these parameters.

Full Rate Active Codec Set (ACS) Cell parameters:

amr_fr_acs
See CELL Detailed View fields, General - ( AMR Full
amr_fr_icm
Rate grouping on page 8-33) for details.
amr_fr_uplink_threshold1
amr_fr_uplink_threshold2
amr_fr_uplink_threshold3
amr_fr_uplink_hysteresis1
amr_fr_uplink_hysteresis2
amr_fr_uplink_hysteresis3
amr_fr_downlink_threshold1
amr_fr_downlink_threshold2
amr_fr_downlink_threshold3
amr_fr_downlink_hysteresis1
amr_fr_downlink_hysteresis2
amr_fr_downlink_hysteresis3
amr_fr_uplink_threshold1_hopping
amr_fr_uplink_threshold2_hopping
amr_fr_uplink_threshold3_hopping
amr_fr_uplink_hysteresis1_hopping
amr_fr_uplink_hysteresis2_hopping
amr_fr_uplink_hysteresis3_hopping
amr_fr_downlink_threshold1_hopping
amr_fr_downlink_threshold2_hopping
amr_fr_downlink_threshold3_hopping
amr_fr_downlink_hysteresis1_hopping
amr_fr_downlink_hysteresis2_hopping
amr_fr_downlink_hysteresis3_hopping
Continued

68P02901W17-T

2-135
Jan 2010

AMR parameters

Chapter 2: Configuring BSS Features

Table 2-24

AMR parameters (Continued)

Details

BSS parameter name

Half Rate Active Codec Set (ACS)
Cell parameters:

See CELL Detailed View fields, General - ( AMR/GSM

Half Rate grouping on page 8-39) for details.

amr_hr_acs
amr_hr_icm
amr_hr_uplink_threshold1
amr_hr_uplink_threshold2
amr_hr_uplink_threshold3
amr_hr_uplink_hysteresis1
amr_hr_uplink_hysteresis2
amr_hr_uplink_hysteresis3
amr_hr_downlink_threshold1
amr_hr_downlink_threshold2
amr_hr_downlink_threshold3
amr_hr_downlink_hysteresis1
amr_hr_downlink_hysteresis2
amr_hr_downlink_hysteresis3
amr_hr_uplink_threshold1_hopping
amr_hr_uplink_threshold2_hopping
amr_hr_uplink_threshold3_hopping
amr_hr_uplink_hysteresis1_hopping
amr_hr_uplink_hysteresis2_hopping
amr_hr_uplink_hysteresis3_hopping
amr_hr_downlink_threshold1_hopping
amr_hr_downlink_threshold2_hopping
amr_hr_downlink_threshold3_hopping
amr_hr_downlink_hysteresis1_hopping
amr_hr_downlink_hysteresis2_hopping
amr_hr_downlink_hysteresis3_hopping
Full Rate AMR Cell Handover parameters:
l_rxqual_ul_h_amr_fr
l_rxqual_ul_h_hopping_amr_fr
l_rxqual_dl_h_amr_fr
l_rxqual_dl_h_hopping_amr_fr

See CELL Detailed View fields, General - ( AMR Full

Rate grouping on page 8-33) for details.

Full Rate AMR Cell Power Control parameters:

l_rxqual_ul_p_amr_fr
l_rxqual_ul_p_hopping_amr_fr
l_rxqual_dl_p_amr_fr
l_rxqual_dl_p_hopping_amr_fr

See CELL Detailed View fields ( Power control AMR Full Rate on page 8-67) for details of these
parameters.

Half Rate AMR Cell Handover parameters:

l_rxqual_ul_h_hr
l_rxqual_ul_h_hopping_hr
l_rxqual_dl_h_hr
l_rxqual_dl_h_hopping_hr

See CELL Detailed View fields, ( Handover AMR/GSM Half Rate grouping on page 8-60) for
details of these parameters.

Continued

2-136

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 2-24

Methods of configuring AMR

AMR parameters (Continued)

Details

BSS parameter name

Half Rate AMR Cell Power Control
parameters:

See CELL Detailed View fields, ( Power control AMR/GSM Half Rate on page 8-68) for details of
these parameters.

l_rxqual_ul_p_hr
u_rxqual_ul_p_hr
l_rxqual_ul_p_hopping_hr
l_rxqual_dl_p_hr
u_rxqual_dl_p_hr
l_rxqual_dl_p_hopping_hr
Half Rate Link Adaptation Cell parameters:
amr_hr_ul_la_enabled
amr_hr_dl_la_enabled

See CELL Detailed View fields, General - AMR Half

Rate grouping (Table 8-15) for details of these
parameters.

Full Rate Link Adaptation Cell parameters:

amr_fr_dl_la_enabled
amr_fr_ul_la_enabled

CELL Detailed View fields, General - AMR Full

Rate grouping (Table 8-14) for details of these
parameters.

Half Rate RTF parameters:

half_rate_enabled
allow_8k_trau

See RTF Detailed View fields, Channel Mode Usage

(AMR Full Rate and Half Rate/GSM Half Rate)
grouping (Table 9-67) for details.

Assoc_RXCDR parameters:
eac_mode
cic_block_thresh
cic_unblock_thresh

See Assoc_RXCDR Detailed View fields, Channel

Mode Usage (AMR Full Rate and Half Rate/GSM
Half Rate) grouping () for details.

Methods of configuring AMR

AMR can be configured using:

OMC-R GUI BSS, Cell and RTF Detailed View and the parameters shown in Table 2-24.

TTY interface, see Configuring AMR using the TTY interface.

Configuring AMR using the TTY interface

The following sections give examples of using the TTY interface to configure AMR. For further
details of the commands and parameters shown in these examples, see Technical Description:
BSS Command Reference (68P02901W23).

68P02901W17-T

2-137
Jan 2010

Configuring AMR using the TTY interface

Chapter 2: Configuring BSS Features

Displaying AMR cell parameters using the TTY interface

To display the current value of an AMR cell parameter use either of the commands
disp_element, or disp_cell with the full option. For example, the following command displays
the current value of amr_fr_ul_la_enabled for cell 4960114 at site 0:
disp_element amr_fr_ul_la_enabled 0 cell 4 9 6 0 1 1 4
amr_fr_ul_la_enabled = 1

Modifying AMR cell parameters using the TTY interface

To modify the current value of an AMR cell parameter use the chg_element or chg_cell_element
command. For example, the following command enables AMR uplink codec mode adaptation
for cell 4960114 at site 1:
chg_element amr_fr_ul_la_enabled 1 1 cell 4 9 6 0 1 1 4
The chg_cell_element command prompts for dependant cell parameters when necessary. For
example, the AMR RXqual Handover and Power Control parameters are prompted for when
changing the value of alt_qual_proc and hopping related parameters are prompted for when
changing hop_qual_enabled to 1, for example:
chg_cell_ele alt_qual_proc 0 cell 0 0 1 0 1 98 75
chg_cell_ele hop_qual_enabled 1 cell 0 0 1 0 1 98 75

Displaying AMR BSS parameters using the TTY interface

To display the current value of an AMR BSS parameter, use the disp_element command. For
example, the following command displays the current value of amr_ms_monitor_period for the
BSS:
disp_element amr_ms_monitor_period 0
amr_ms_monitor_period = 25

Modifying AMR BSS parameters using the TTY interface

To modify the current value of an AMR BSS parameter use the chg_element command. For
example, the following command changes the MS monitor period to 25 at the BSS:
chg_element amr_ms_monitor_period 25 0

Displaying the Active Codec Set

To display the Active Codec Set for an AMR cell, use the disp_acs command, and security level
3. For example the following command displays the active codec set for cell 4960111:
disp_acs 4 9 6 0 1 1 1
The system then displays the Active Codec Set modes, associated threshold and hysteresis
values for the cell.

2-138

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring AMR using the TTY interface

Specifying the Active Codec Set

To specify the Active Codec Set for an AMR cell, use the chg_acs_params command, and security
level 3. For example the following command sets four Full Rate codec modes in the active codec
set for cell 4960111, where previously only one mode was configured:
chg_acs_params 0 4 9 6 0 1 1 1
The system then prompts for the Active Codec Set modes, associated threshold and hysteresis
values for the cell.

68P02901W17-T

2-139
Jan 2010

GSM Half Rate

Chapter 2: Configuring BSS Features

GSM Half Rate

The GSM Half Rate feature offers enhanced capability over the air interface, corresponding
to the proportion of mobiles within a coverage area that support Half Rate. An air timeslot is
split into two sub-channels, each containing a half rate channel. Although speech quality is
considered inferior to other speech codecs, the penetration level is high making it a viable
option for high density areas.
A full technical description of GSM HR can be found in Technical Description: BSS

Implementation (68P02901W36).

Prerequisites for enabling GSM HR

GSM HR can only be enabled for a BSS if the GSM HR feature (gsmHalfRateOpt) is
unrestricted (Enabled) for the NE.

Configuring GSM HR
GSM HR is an optional feature for a BSS. If the GSM HR feature is unrestricted (Enabled) at the
BSS, then GSM HR can be enabled or disabled on a BSS, Cell or RTF basis.

Interaction with other features

This feature interacts with the IMRM feature, see for further details.

Determining whether the GSM HR feature is unrestricted

GSM HR is an optional feature, which must be unrestricted before it can be used.

Using the OMC-R GUI

To check if GSM HR is unrestricted (enabled) using the OMC-R GUI, display the setting of the
GSM HR feature (gsmHalfRateOpt) in the Optional Features grouping in the BSS Detailed View.

2-140

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GSM HR parameters

Using the TTY interface

To check if the GSM HR feature is unrestricted using the TTY interface, enter the following
command:
disp_options 22064
If the GSM HR feature is unrestricted, the system displays it in the Unrestricted list as follows:
<22064> GSM Half Rate

GSM HR parameters
Table 2-25 lists the additional parameters specific to configuring GSM HR.

Table 2-25 GSM HR-specific parameters

Details

BSS parameter name

GSM HR BSS parameters:
gsmHalfRateOpt

Displayed in the Optional Features grouping

of the BSS Detailed View. Indicates whether
the GSM Half Rate (HR) feature is restricted
(Disabled) or unrestricted (Enabled) for the
BSS.

GSM Half Rate Channel Mode Usage BSS parameters:

gsm_bss_half_rate_enabled

See BSS Detailed View fields - Channel Mode

Usage (AMR Full Rate and Half Rate/GSM
Half Rate ( Channel Mode Usage (AMR Full
Rate and Half Rate/GSM Half Rate) grouping
with GSM Half Rate on page 4-37) for details
of these parameters.

AMR/GSM Half Rate Cell parameters:

gsm_half_rate_enabled

68P02901W17-T

See CELL Detailed View fields, General AMR/GSM Half Rate grouping ( AMR/GSM
Half Rate grouping with GSM Half Rate on
page 8-46) for details of these parameters.

2-141
Jan 2010

GPRS Seamless Cell Reselection

Chapter 2: Configuring BSS Features

GPRS Seamless Cell Reselection

Description of GPRS Seamless Cell Reselection (SCR)

The GPRS receiver performs cell selection based on the receive level (RxLev) from the
neighboring cells due to cell reselection. During cell reselection, when buffered data is still
being transferred from the original cell to the target cell, the MS may select yet another cell
and the buffered data can be lost.
The GPRS Seamless Cell Reselection feature transfers data from the source cell to the target
cell to avoid data loss and to minimize the retransmissions at the TCP layer, thus boosting
performance. GPRS Seamless Cell Reselection feature ensures completion of the cell change
procedure at the RLC/MAC layers in a controlled manner so that the higher layers (specifically
TCP) do not notice the effect.
For further details of the GPRS Seamless Cell Reselection feature, see Technical Description:
BSS Implementation (68P02901W36).

Determining whether GPRS Seamless Cell Reselection (SCR)

is unrestricted
SCR is an optional feature, which must be unrestricted for a BSS in order for it to be used. The
GPRS feature (gprsOpt) must also be unrestricted at the BSS in order for SCR to function.

Using the OMC-R GUI

To check if SCR is restricted or unrestricted, using the OMC-R GUI, display the setting of the
GPRS Seamless Cell Reselection Feature field (scrOpt) in the Optional Features grouping in the
BSS Detailed View. The values for scrOpt are:

Disabled (0) - data from the source cell to the target cell is discarded.

Enabled (1) - data is forwarded from the source cell to the target cell.

Default is Disabled (0).

This field cannot be changed by a user.

2-142

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GPRS Seamless Cell Reselection parameters

Using the TTY interface

To check if SCR is restricted or unrestricted using the TTY interface, enter the following
command:
disp_options all
If the SCR optional feature is unrestricted, the system displays the following in the unrestricted
list:
54 Seamless Cell Reselection

GPRS Seamless Cell Reselection parameters

Table 2-26 details the GPRS Seamless Cell Reselection parameters.

Table 2-26 Seamless Cell Reselection parameters

OMC-R GUI
field name/
parameter name
GPRS Seamless
Cell Reselection
Enabled
scr_enabled

Description

Attributes

Displayed in the GPRS Seamless

Cell Reselection grouping in the BSS
Detailed View form.
Indicates whether the GPRS Seamless
Cell Reselection feature is Enabled (1)
or Disabled (0). The default is Disabled
(0). Can be modified by a user.
Grayed-out if the BSS Detailed View
field: GPRS Seamless Cell Reselection
Feature (parameter name: scrOpt) is
set to Disabled (0).

gprs_cr_margin
This attribute specifies
the threshold at which the
network considers the PMR
received from the MS as a
bad PMR.
gprs_num_pmrs
This attribute specifies the
number of bad PMRs the
network receives before
initiating a network controlled
cell reselection.

Methods for configuring SCR

The SCR feature can be configured using:

OMC-R GUI BSS and CELL Detailed Views and the fields shown in Table 2-26.

TTY interface, see Configuring SCR using TTY interface.

68P02901W17-T

2-143
Jan 2010

Configuring SCR using TTY interface

Chapter 2: Configuring BSS Features

Configuring SCR using TTY interface

See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS
commands, prompts, and parameters.

Displaying whether SCR is enabled for a BSS

Use the disp_element command to display whether SCR is enabled for a BSS. For example, the
following command displays the value of scr_enabled:
disp_element scr_enabled bsc
The system replies, for example:
scr_enabled = 1

Enabling and disabling SCR for a BSS

Use the chg_element command to enable or disabled SCR at a BSS. For example, the following
command sets scr_enabled to 1 (enabled) at a BSS:
chg_element scr_enabled 1 bsc

2-144

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Current Bucket Level (CBL) feature

Current Bucket Level (CBL) feature

Overview of the Current Bucket Level feature

The Current Bucket Level (CBL) feature is essential for the correct working of BSSGP flow
control. When the Current Bucket Level (CBL) feature is enabled, a current bucket level (buffer
full percentage) is included with every flow control message, to correct the estimation error in
the SGSN.
The Current Bucket Level feature can be enabled or disabled for each BSS using the Current
Bucket Level Feature field (bssgp_cbl_bit) in the BSS Detailed View.
For further details of the Current Bucket Level feature, see Technical Description: BSS
Implementation (68P02901W36).

Prerequisite for Current Bucket Level feature

The GPRS feature (gprsOpt) must be unrestricted at the BSS, before CBL can be enabled.

Current Bucket Level parameters

Table 2-27 details the Current Bucket Level parameters.

Table 2-27 Current Bucket Level parameters

OMC-R GUI
field name/BSS
parameter name
Current Bucket
Level Feature
bssgp_cbl_bit

68P02901W17-T

Description
Displayed in the GPRS grouping in the BSS Detailed View form.
Indicates whether the Current Bucket Level (CBL) feature is used
at the PCU. Values are Disabled (0) or Enabled (1). The default is
0.
Grayed-out if the GPRS Feature (gprsOpt) is Disabled (0) at the
BSS.
The OMC-R displays the following message if the value is
changed: WARNING: Changing this element may trigger a
negotiation with the SGSN, resulting in the reset of
signaling BVCI. CBL feature shall be enabled/disabled
subject to this negotiation. Ongoing data transfers
will be affected due to signaling reset. Do you wish
to continue?

2-145
Jan 2010

Enhanced Scheduling

Chapter 2: Configuring BSS Features

Enhanced Scheduling

Overview
The Enhanced Scheduling feature provides mechanisms that allow the BSS to dynamically
select the most appropriate access method, allowing fast access whilst reducing the load on
the signaling links.

Enhanced Scheduling sub-features

The Enhanced Scheduling feature comprises the following sub-features:

Increased PRP Capacity - Increased number of GPRS MSs that can be serviced by each
Packet Resource Processor (PRP) (that is, more than 120 MSs) (using the BSS parameters
prp_capacity_opt and inc_prp_cap_ena).

Dynamic allocation of reserved Packet Resource Request (PRR) blocks for two-phase
access (using cell parameter gprs_min_prr_blks and BSS parameter prr_aggr_factor).

Provides control for the percentage of RSL bandwidth reserved for circuit switched (CS)
traffic (using the cell parameter percent_traf_cs).

Advanced UL/DL bias detection to optimize MS throughput (using the BSS parameter
gprs_ul_dl_bias and gprs_com_ms_class).

These changes together increase scheduling efficiency leading to a greater amount of GPRS
traffic handling capacity in a given cell whilst reducing the impact of the data traffic on circuit
switched traffic.
For further details of the Enhanced Scheduling, see Technical Description: BSS Implementation
(68P02901W36).

Enhanced Scheduling dependencies

The Enhanced Scheduling feature requires the GPRS feature (gprsOpt) to be unrestricted
(enabled).

Enhanced Scheduling parameters

Table 2-28 lists the parameters associated with the Enhanced Scheduling feature. Unless
stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name.
For further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).

2-146

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Enhanced Scheduling parameters

Table 2-28 Enhanced Scheduling parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

BSS parameters:
Increased PRP Capacity
Feature Supported
prp_capacity_opt

Displayed in the Optional Features

grouping of the BSS Detailed View form.
Indicates whether the increased PRP
capacity feature is restricted (disabled)
or unrestricted (enabled) in the BSS
software.
This parameter cannot be modified by a
user.
The field is grayed-out in the OMC-R
GUI if the GPRS feature is restricted
(disabled).

0 or 1, where:
Disabled (0).
Enabled (1).
Default is
Disabled (0).

Increased PRP Capacity

Feature Enabled
inc_prp_cap_ena

Displayed in the GPRS grouping of the

BSS Detailed View form.
Indicates whether increased PRP capacity
is enabled (1) or disabled (0). If disabled
(0), the concept of short and long GPRS
sessions do not apply.
This field cannot be set to True (1), if
the Increased PRP Capacity Feature
(prp_capacity_opt) is Disabled (0).

True (1) or False

(0).
Default is False
(0).

Most Common Multislot of

GPRS Mobiles
gprs_com_ms_class

Displayed in the GPRS grouping of the

BSS Detailed View form.
Determines the maximum number of DL
timeslots allocated to a mobile for EOP
and one-phase access.

1, 2, 4 or 8, where:
1 - multislot
class1.
2 - multislot class
2, 3, 5.4 - multislot
class 4, 6, 7.
8 - multislot class
8 to 29.
Default is 8.

PRR Blocks Reservation

Aggressiveness Factor
prr_aggr_factor

Displayed in the GPRS grouping of the

BSS Detailed View form.
Represents a coefficient for a
linear function to dynamically
allocate/deallocate reserved PRR
blocks. An aggressiveness factor of 0
means that each cell in the BSS has PRR
blocks allocated according to the value of
the gprs_min_prr_blks cell parameter.
This field has no effect on cells that have
pccch_enabled set to 1 (Enabled).

0 - 4.
Default is 3.

GPRS Uplink or Downlink

bias
gprs_ul_dl_bias

Displayed in the GPRS grouping of the

BSS Detailed View form.
This parameter is applied if the operator
wants more UL timeslots to be allocated
to mobiles initially with multislot class
6, 10, 11 and 12 as well as any multislot
class that maps to class 6, 10, 11 and 12.

UL (0) or DL (1).
Default is DL (1).

Continued

68P02901W17-T

2-147
Jan 2010

Methods of configuring enhanced scheduling

Chapter 2: Configuring BSS Features

Table 2-28 Enhanced Scheduling parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

CELL parameters:
Minimal number of dynamic
PRR blocks
gprs_min_prr_blks

Displayed in the GPRS grouping of the

CELL Detailed View form.
Indicates the minimum number of
reserved PRR blocks created per cell,
when measured over four multiframes.
This field has no effect on cells that have
pccch_enabled set to 1 (Enabled).

0 - 24.
Default is 0.

Displayed in the GPRS grouping of the

BTS SITE Detailed View form.
Indicates the percentage of RSL traffic
reserved for circuit switch (CS) traffic
per site.
This field can only be modified if GPRS
is enabled.

0 - 90.
Default is 55.

BTS site parameters:

Percentage of RSL Reserved
for CS
percent_traf_cs

Methods of configuring enhanced scheduling

Enhanced scheduling can be configured using:

OMC-R GUI BSS, site and CELL Detail Views and the fields shown in Table 2-28.

TTY interface, see Configuring enhanced scheduling using the TTY interface on page 2-148.

Configuring enhanced scheduling using the TTY interface

Checking if Increased PRP capacity is unrestricted
To check if Increased PRP capacity is unrestricted (enabled) using the TTY interface, enter the
following command:
disp_options
If Increased PRP capacity is unrestricted, the following is displayed:
58 PRP Capacity

Displaying and modifying enhanced scheduling parameters

The disp_element, disp_cell, chg_element and chg_cell_element commands can be used
to display and configure the Enhanced Scheduling BSS, site and cell parameters shown in
Table 2-28. Some examples are also given in the following sections.
See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS
commands, prompts, and parameters.
2-148

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring enhanced scheduling using the TTY interface

Displaying whether Increased PRP Capacity is enabled at a BSS

Use the disp_element command to display whether Increased PRP Capacity is enabled for a
BSS. For example, the following command displays the current setting of inc_prp_cap_ena:
disp_element inc_prp_cap_ena 0
The system replies, for example:
inc_prp_cap_ena = 1

Displaying the current setting of Enhanced Scheduling parameters

Use the disp_element command to display the value of percent_traf_cs or gprs_min_prr_blks.
For example, the following command displays the current value of percent_traf_cs at site 1:
disp_element percent_traf_cs 1
The system replies, for example:
percent_traf_cs = 55%
For example, the following command displays the current value of gprs_min_prr_blks at cell
0010111:
disp_element gprs_min_prr_blks 0 cell_number = 0 0 1 0 1 1 1
The system replies, for example:
gprs_min_prr_blks = 4

Setting BSS, site, and Cell parameters for Enhanced Scheduling

Use the chg_element command to change Enhanced Scheduling BSS and site parameters, and
chg_cell_element command to change the Enhanced Scheduling cell parameter.
For example, the following command changes the site parameter percent_traf_cs to 50%
at site 1:
chg_element percent_traf_cs 50 1
The following command changes the cell parameter gprs_min_prr_blks to 5 at cell 0010111:
chg_cell_element gprs_min_blks 5 0 0 1 0 1 1 1

68P02901W17-T

2-149
Jan 2010

Intelligent Multi Layer Resource Management (IMRM)

Chapter 2: Configuring BSS Features

Intelligent Multi Layer Resource Management (IMRM)

IMRM allows users to better match overall traffic distribution to intrinsic network capacity and
MS penetration. By supporting, on a per cell basis, weightings for each of the available bands,
the system can effect a more dynamic distribution based on factors such as:

Local (cell) per band capacity

Neighbor (For example, micro underlay, macro overlay) per band capacity

Mobile Capability penetration for example, Multiband vs Single Band

Congestion Management that is, half rate management

Other System Considerations for example, GPRS capacity

The Layer Weightings supported are:

PGSM

EGSM

DCS1800

UMTS

The individual layer weightings are dynamically combined with a requesting MS capabilities to
define a set of probabilities for each of the supported layers; a random selection based on these
probabilities then effects the traffic distribution. The higher the layer weighting the higher the
probability and hence more likely selection. Setting any layer weighting to the maximum defined
value results in a fixed (to that layer) preference selection as per existing ALM procedures.
The default for all available layers is set to Unsupported. Where, IMRM is enabled in a cell with
all layers set to Unsupported, the system applies a set of fixed internal defaults for input into
the Preference Selection Algorithm. The system supports 2 sets of defaults with selection
based on local EGSM availability.

Table 2-29

2-150

Default Band Weightings

EGSM
Support

PGSM

EGSM

DCS1800

PCS850

PCS1900

GSM450

UMTS

Yes

45

10

45

N/A

N/A

N/A

No

50

50

N/A

N/A

N/A

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

configuring Intelligent Multi Layer Resource Management

Prerequisites to

The Preference Selection Algorithm is run for each initial network resource request
(Assignment and incoming External Handover) and is used in conjunction with the existing
band_preference_mode parameter to determine both initial resource targeting and also any
subsequent handover activity. The selected preference is then retained or utilized for the call
while it remains within the current BSS. There are situations whereby the Preference Selection
Algorithm can be re-run for existing calls, either due to system operation and/or operator
control as follows:

Intra-BSS hand-in from non-IMRM Source to IMRM Target.

Intra-BSS hand-in from IMRM Source with a locally unsupported Preference.

Intra-BSS hand-in to an IMRM Target with (configured) Forced Recalculation of Preference.

Statistics have been used to allow tracking of cell availability and utilization on a per layer basis.

Prerequisites to configuring Intelligent Multi Layer Resource

Management
Before configuring IMRM, ensure that the Multiband Inter-Cell Handover (mbInterCellHoOpt
parameter) has been enabled: See Table 4-4, Configuring enhanced SDCCH to TCH band
assignment on page 8-198 and Configuring a cell for coincident multiband handovers on page
8-181 for details

Intelligent Multi Layer Resource Management parameters

Table 2-30 details the parameters associated with the Intelligent Multi Layer Resource
Management feature. Unless stated otherwise, the OMC-R parameter name is usually the same
as the BSS parameter name. For further details of these and other parameters, see Technical
Description: BSS Command Reference (68P02901W23).

Table 2-30 Intelligent Multi Layer Resource Management parameters

OMC-R GUI field
name/BSS parameter
name

Description

Values

BSS parameters:
Intelligent Multi Layer
Feature imrmOpt

Displayed in the Optional Features

grouping of the BSS Detailed View.
Indicates whether IMRM feature is
unrestricted (enabled) or restricted
(disabled).

0 or 1, where:
Disabled (0).
Enabled (1).

CELL parameters:
Continued

68P02901W17-T

2-151
Jan 2010

Intelligent Multi Layer Resource Management parameters

Chapter 2: Configuring BSS Features

Table 2-30 Intelligent Multi Layer Resource Management parameters (Continued)

OMC-R GUI field
name/BSS parameter
name

Description

Values

Band Preference
band_preference

Displayed in the CELL Detailed View,

General section, Multiband handover
grouping.
Allows the preferred band to be set
for a cell. To enable IMRM on a per
cell basis, set to 16 (DYNAMIC)
The value 16 (DYNAMIC) can only
be selected if Intelligent Multi Layer
Feature (imrmOpt) is unrestricted
(enabled).
When IMRM is enabled for a cell,
Advanced Load Management (ALM)
feature is automatically switched off.
When IMRM is switched off, ALM is
automatically switched on.
Also used by the ALM feature, see
Advanced Load Management for
EGSM on page 2-78.

1, 2, 4, 8, or 16.

IMRM Force Recalculation

imrm_force_recalc

Displayed in the CELL Detailed View,

General section, Multiband handover
grouping.
When the IMRM feature (imrmOpt)
is enabled, displays whether a
recalculation on the preferred band
to handover to is executed on the
cell. See for further details of how to
set this parameter.

0 or 1, where:
0 = Disabled.
1 = Enabled.
Default is 0.

PGSM Weighting (0100)

imrm_pgsm_weight

Displayed in the CELL Detailed View,

General section, Multiband handover
grouping. When the IMRM feature
(imrmOpt) is enabled, displays the
weighting for the PGSM frequency.
Only one weighting can be set to
100, otherwise the following error
message is displayed: Cannot set
more than one IMRM band weight to
the max value.
See for further details of how to set
this parameter.

0 - 100.
Default is 0.

Continued

2-152

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Intelligent Multi Layer Resource Management parameters

Table 2-30 Intelligent Multi Layer Resource Management parameters (Continued)

OMC-R GUI field
name/BSS parameter
name

Description

Values

IMRM EGSM Weighting

(0-100)
imrm_egsm_weight

Displayed in the CELL Detailed View,

General section, Multiband handover
grouping. When the IMRM feature
(imrmOpt) is enabled, displays the
weighting for the EGSM frequency.
Only one weighting can be set to
100, otherwise the following error
message is displayed: Cannot set
more than one IMRM band weight to
the max value.
See for further details of how to set
this parameter.

0 - 100.
Default is 0.

IMRM DCS1800
Weighting (0-100)
imrm_dcs1800_weight
(Field name in OMC-R
database table:
mrm_dcs18_weight)

Displayed in the CELL Detailed View,

General section, Multiband handover
grouping. When the IMRM feature
(imrmOpt) is enabled, displays
the weighting for the DCS1800
frequency. Only one weighting
can be set to 100, otherwise the
following error message is displayed:
Cannot set more than one IMRM
band weight to the max value.
See for further details of how to set
this parameter.

0 - 100.
Default is 0.

IMRM UMTS Weighting

(0-100)
imrm_umts_weight

Displayed in the CELL Detailed View,

General section, Multiband handover
grouping. When the IMRM feature
(imrmOpt) is enabled, displays the
weighting for the UMTS frequency.
Only one weighting can be set to
100, otherwise the following error
message is displayed: Cannot set
more than one IMRM band weight to
the max value.
Grayed-out if either the IMRM or
2G3G feature is restricted.
See for further details of how to set
this parameter.

0 - 100.
Default is 0.

Band Preference Mode

band_preference_mode

Displayed in the CELL Detailed

View, General section, Multiband
Handover grouping. Determines the
method used to have a MultiBand
MS use the band of preference for
a given cell in the BSS. Can only be
modified if the MultiBand Inter-Cell
Handover feature is unrestricted
(enabled). See for recommended
settings when used in conjunction
with IMRM.

0 - 6.
Default is 0.

68P02901W17-T

2-153
Jan 2010

Quality of Service (QoS)

Chapter 2: Configuring BSS Features

Quality of Service (QoS)

Overview of QoS
In R99 of the 3GPP specifications, Packet Flow Management (PFM) procedures were added to
the BSSGP protocol. These procedures provide for aggregation of similar QoS profiles into a
single Packet Flow Context and allow the BSS to negotiate and modify QoS parameters.
The Aggregate BSS QoS Profile (ABQP) field, contained in PFM signals, describes the QoS
characteristics for a single PFC, identified by a Packet Flow Identifier (PFI). The ABQP field
contains a full set of QoS parameters: traffic class, Traffic Handling Priority (THP), maximum bit
rates and guaranteed bit rates for uplink/downlink, transfer delay, and other fields describing
error rate/ratio characteristics are parameters included in the ABQP to provide a more specific
differentiation of services to users. With the added parameters contained in the ABQP field, and
the ability to negotiate and modify these QoS parameters, the BSS can now provide differentiated
services to users in line with the QoS requested by the mobile and consistent to those offered to
the mobile by the other network entities, thus providing a more consistent QoS E2E.
For a full description of QoS, see Technical Description: BSS Implementation (68P02901W36).

Prerequisites to configuring QoS

Before configuring QoS, ensure that the following features have been enabled:

Network Assisted Cell Change (NACC) (naccOpt parameter). See Network Assisted Cell
Change (NACC) on page 2-162 for further details.

GPRS (gprsOpt parameter).

Quality of Service parameters

Table 2-31 details the QoS parameters. Unless stated otherwise, the OMC-R parameter name is
usually the same as the BSS parameter name. For further details of these and other parameters,
see Technical Description: BSS Command Reference (68P02901W23).

2-154

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Quality of Service parameters

Table 2-31 Quality of Service parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

Quality Of Service Feature

qosOpt

Displayed in the Optional Features

grouping of the BSS Detailed View.
Indicates whether QoS feature is enabled
or disabled.

0 or 1, where:
Disabled (0).
Enabled (1).
If the feature has
been purchased
the default
is Enabled
(1), otherwise
the default is
Disabled (0).

BSS support of PFM on

BSSGP (for QoS)
bssgp_pfc_bit

Displayed in the Quality of Service

grouping in the BSS Detailed View.
Specifies whether PFM procedures are
enabled.
Grayed out if QoS feature is not purchased
and NACC feature is not enabled in the
BSS.
If modified the following warning message
is displayed: WARNING: Changing
this element may trigger a negotiation
with the SGSN, resulting in the reset
of signaling BVCI. QoS feature shall
be enabled/disabled subject to this
negotiation. Ongoing data transfers will
be affected due to signaling reset. Do you
wish to modify?

0 or 1, where:
Off (0).
On (1).
Default is Off (0).

ARP Signaling Selection

arp_signal_sele

Displayed in the Quality of Service

grouping in the BSS Detailed View.
Indicates which ARP signaling selection
option is used for R99/R4 mobiles.
Grayed out if QoS Feature is not
purchased.
If bssgp_pfc_bit set to On (1) and
arp_signal_sele is modified the following
message is displayed: WARNING:
Changing arp_signal_sele when QoS is
enabled will only affect new PFCs.

0, 1, or 2, where:
Fixed ARP Value
of 3 (0).
Map precedence
class values to
ARP(1, 2, 3) (1),
Map Traffic
Handling Priority
to ARP (2)
Default is Map
precedence class
values to ARP(1,
2, 3) (1).

BSS parameters:

Continued

68P02901W17-T

2-155
Jan 2010

Quality of Service parameters

Chapter 2: Configuring BSS Features

Table 2-31 Quality of Service parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

THP Weight of Interactive 2

Class
thp_i2_weight

Displayed in the Quality of Service

grouping in the BSS Detailed View.
Specifies the THP weight of interactive 2
class. Traffic Handling Priority controls
relative throughput of PFCs by assigning a
weighting factor for interactive 2 class.
Grayed out if QoS Feature is not
purchased.
Field becomes read only if bssgp_pfc_bit
is set to On (1).
If thp_i2_weight is modified and then
bssgp_pfc_bit is set from 0 to 1, the BSS
Detailed View reverts back to previously
saved value for thp_i2_weight.

10 - 40
Default is 40.

THP Weight of Interactive 3

Class
thp_i3_weight

Displayed in the Quality of Service

grouping in the BSS Detailed View.
Specifies the THP weight of interactive 3
class. Traffic Handling Priority controls
relative throughput of PFCs by assigning a
weighting factor for interactive 3 class.
Grayed out if QoS Feature is not
purchased.
Field becomes read only if bssgp_pfc_bit
is set to On (1).
If thp_i3_weight is modified and then
bssgp_pfc_bit is set from 0 to 1, the BSS
Detailed View reverts back to previously
saved value for thp_i3_weight.
thp_i3_weight must be less than or equal
to the value of thp_i2_weight.

10 - 40
Default is 40.

THP Weight of Background

Class
thp_bg_weight

Displayed in the Quality of Service

grouping in the BSS Detailed View.
Specifies the THP weight of background
class. Traffic Handling Priority controls
relative throughput of PFCs by assigning
a weighting factor for background class.
Grayed-out if QoS Feature is not
purchased.
Field becomes read only if bssgp_pfc_bit
is set to On (1).
If thp_bg_weight is modified and then
bssgp_pfc_bit is set from 0 to 1, the BSS
Detailed View reverts back to previously
saved value for thp_bg_weight.
thp_bg_weight must be less than or equal
to the value of thp_i3_weight.

10 - 40
Default is 40.

Continued

2-156

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Quality of Service parameters

Table 2-31 Quality of Service parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

THP Weight of Best Effort

Class
thp_be_weight

Displayed in the Quality of Service

grouping in the BSS Detailed View.
Specifies the THP weight of best effort
class. Traffic Handling Priority controls
relative throughput of PFCs by assigning
a weighting factor for best effort class.
Grayed-out if QoS Feature is not
purchased.
Field becomes read only if bssgp_pfc_bit
is set to On (1).
If thp_be_weight is modified and then
bssgp_pfc_bit is set from 0 to 1, the BSS
Detailed View reverts back to previously
saved value for thp_be_weight.
thp_be_weight must be less than or equal
to the value of thp_i3_weight.

0 - 40
Default is 40.

ARP Parameter for Best Effort

Class PFCs
pfc_be_arp

Displayed in the Quality of Service

grouping in the BSS Detailed View.
Specifies choices for ARP parameter for
PFCs belonging to best effort traffic class.
Grayed-out if QoS Feature is not
purchased.
If arp_signal_sele is set to Disable
ARP across BSS (0), any attempt to
modify pfc_be_arp displays the following
message: WARNING: Any changes to
pfc_be_arp do not change system behavior
when arp_signal_sele is equal to 0.

0, 1, 2, or 3,
where:
ARP mapped
from precedence
class (0), ARP 1
(1), ARP 2 (2),
ARP 3 (3).
Default is ARP
mapped from
precedence class
(0).

GPRS Scheduling Beta

Algorithm
gprs_sched_beta

Displayed in the GPRS grouping in the

BSS Detailed View.
QoS modifies the behavior of this
parameter. If gprs_sched_beta is
modified and saved while QoS is enabled,
the following message is displayed:
WARNING: Changes to gprs_sched_beta
are overridden while QoS is enabled.

Enhanced One Phase Access

eop_enabled

Displayed in the GPRS grouping in the

BSS Detailed View.
QoS modifies the behavior of this
parameter. If bssgp_pfc_bit is set to On
(1), any modification to eop_enabled is
overridden. If eop_enabled is modified
and saved while QoS is enabled and
bssgp_pfc_bit is set to on(1), the following
message is displayed: WARNING:
Changes to eop_enabled are overridden
while QoS is enabled.
Continued

68P02901W17-T

2-157
Jan 2010

Quality of Service parameters

Chapter 2: Configuring BSS Features

Table 2-31 Quality of Service parameters (Continued)

OMC-R GUI field name/BSS
parameter name
CELL parameters:

Description

Values

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the downlink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2 - 24 for Interactive
traffic class, traffic handling priority 1.
Grayed-out if QoS Feature is not
purchased.
read only if bssgp_pfc_bit is set to On (1).

2 - 24.
Default 2.

Uplink MTBR for Interactive

THP 1
qos_mtbr_i1_ul

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the uplink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2 - 6 for Interactive
traffic class, traffic handling priority 1.
Grayed-out if QoS Feature is not
purchased.
read only if bssgp_pfc_bit is set to On (1).

2 - 6.
Default is 2.

Uplink MTBR for Interactive

THP
qos_mtbr_i1_ul

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the uplink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2-6 for Interactive
traffic class, traffic handling priority 1.
Grayed-out if QoS Feature is not
purchased.
Read only if bssgp_pfc_bit is set to On (1).

2 - 6.
Default is 2.

Downlink MTBR for

Interactive THP 2
qos_mtbr_i2_dl

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the downlink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2-24 for Interactive
traffic class, traffic handling priority 2.
Must be less than or equal to the value of
qos_mtbr_i1_dl.
Grayed-out if QoS Feature is not
purchased.
Read only if bssgb_pfc_bit is set to On (1).

2 - 24.
Default is 2.

MTBR for Interactive THP 1

qos_mtbr_i1_dl

Continued

2-158

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Quality of Service parameters

Table 2-31 Quality of Service parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

Uplink MTBR for Interactive

THP 2
qos_mtbr_i2_ul

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the uplink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2-6 for Interactive
traffic class, traffic handling priority 2.
Grayed-out if QoS Feature is not
purchased.
Must be less than or equal to the value of
qos_mtbr_i1_ul.
Grayed-out if QoS Feature is not
purchased.
Read only if bssgp_pfc_bit is set to On (1).

2 - 6.
Default is 2.

Downlink MTBR for

Interactive THP 3
qos_mtbr_i3_dl

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the downlink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2-6 for Interactive
traffic class, traffic handling priority 3.
Grayed-out if QoS Feature is not
purchased.
Must be less than or equal to the value of
qos_mtbr_i2_dl.
read only if bssgp_pfc_bit is set to On (1).

2 - 6.
Default is 2.

Uplink MTBR for Interactive

THP 3
qos_mtbr_i3_ul

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the uplink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2-6 for Interactive
traffic class, traffic handling priority 3.
Grayed-out if QoS Feature is not
purchased.
Must be less than or equal to the value of
qos_mtbr_i2_ul.
Read only if bssgp_pfc_bit is set to On (1).

2 - 6.
Default is 2.

Downlink MTBR for Best

Effort Traffic Class
qos_mtbr_be_dl

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the downlink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2-6 for Best Effort
traffic class.
Grayed-out if QoS Feature is not
purchased.
Read only if bssgp_pfc_bit is set to On (1).

2 - 6.
Default is 2.

Continued

68P02901W17-T

2-159
Jan 2010

Quality of Service parameters

Chapter 2: Configuring BSS Features

Table 2-31 Quality of Service parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

Uplink MTBR for Best Effort

Traffic Class
qos_mtbr_be_ul

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the uplink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2-6 for Best Effort
traffic class.
Grayed-out if QoS Feature is not
purchased.
Read only if bssgp_pfc_bit is set to On (1).

2 - 6.
Default is 2.

Downlink MTBR for

Background Traffic Class
qos_mtbr_bg_dl

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the downlink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2-6 for Background
traffic class.
Grayed-out if QoS Feature is not
purchased.
Read only if bssgp_pfc_bit is set to On (1).

2 - 6.
Default is 2.

Uplink MTBR for Background

Traffic Class
qos_mtbr_bg_ul

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies the uplink Minimum
Throughput Budget Requirement (in
kbit/s) ranges from 2-6 for Background
traffic class.
Grayed-out if QoS Feature is not
purchased.
Read only if bssgp_pfc_bit is set to On (1).

2 - 6.
Default is 2.

PAR Waiting Time

gprs_par_wait_ind

Displayed in the Quality of Service

grouping in the CELL Detailed View, GPRS
section. Specifies how long the mobile
needs to wait before Re-Raching into the
cell.
Grayed-out if GPRS Feature is not
purchased.

100 - 750.
Default is 150.
The unit is Block
Periods; one
Block Period is
20 ms.

Continued

2-160

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Quality of Service parameters

Table 2-31 Quality of Service parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

PCU parameters:
DOWNLOAD-BSS-PFC
Procedure Guard Timer
bssgp_t6_timer

Displayed in the Quality of Service

grouping in the PCU Detailed View.
Guards the DOWNLOAD-BSS-PFC
procedure. Grayed out if the QoS feature
(qosOpt) is restricted. Set to read only if
bssgp_pfc_bit is set to 1 (On).

100 - 10000.
Default is 3000.

MODIFY-BSS-PFC Procedure
Guard Timer
bssgp_t8_timer

Displayed in the Quality of Service

grouping in the PCU Detailed View.
Guards the MODIFY-BSS-PFC procedure.
Grayed out if the QoS feature (qosOpt) is
restricted. Set to read only if bssgp_pfc_bit
is set to 1 (On).

100 - 10000.
Default is 3000.

RA-CAPABILITY-UPDATE
Procedure Guard Timer
bssgp_t5_timer

Displayed in the Quality of Service

grouping in the PCU Detailed View.
Guards the RA-CAPABILITY-UPDATE
procedure. Grayed out if the GPRS feature
(gprsOpt) is restricted.

1000 - 30000.
Default is 3000.

Maximum Number of Retries

for PFC Download
bssgp_dwnld_retry

Displayed in the Quality of Service

grouping in the PCU Detailed View.
Indicates the maximum number of retries
for PFC Download. Grayed out if the QoS
feature (qosOpt) is restricted.

1 - 3.
Default is 3
(tries).

Negotiated value of CBL Bit

cbl_bit_negotiate

Displayed in the Quality of Service

grouping in the PCU Detailed View.
Indicates the negotiated value of CBL Bit.

0 or 1.
0 = CBL feature
at PCU disabled.
1 = CBL feature
at PCU enabled.
No default.
Read only.

Negotiated Value of PFC Bit

pfc_bit_negotiate

Displayed in the Quality of Service

grouping in the PCU Detailed View.
Indicates the negotiated value of PFC Bit.

0 or 1.
0 = QoS feature
at PCU disabled.
1 = QoS feature
at PCU enabled.
No default.
Read only.

68P02901W17-T

2-161
Jan 2010

Network Assisted Cell Change (NACC)

Chapter 2: Configuring BSS Features

Network Assisted Cell Change (NACC)

Overview
The Network Assisted Cell Change (NACC) feature reduces the overhead associated with cell
selection.

Description
The Network Assisted Cell Change feature consists of two independent procedures. The first
procedure allows the MS to indicate to the network the need for a cell change. In the second
procedure, the network provides neighbor cell data to the MS.
For a full description of NACC, see Technical Description: BSS Implementation (68P02901W36).

Procedure 1: PCCN procedure

The MS notifies the network using a Packet Cell Change Notification (PCCN) message when
a cell reselection is needed and delays the cell reselection to let the network respond with
neighbor cell system information. This procedure allows the BSS to play a part in deciding the
best target cell to which the MS should move. The BSS considers the following to make a
decision:

If the neighbor cell is internal or external to the BSS

RxLev measurements of the serving and the neighbor cell as reported by the MS

QoS capabilities of the serving and neighbor cells and the QoS profile of the mobile station

EGPRS/GPRS availability on the target cells

Whether the target cells are in the same routing area

Whether the target cells are on the same PRP board

Whether the proposed target cell/neighbor cell is a macro or a micro cell

If the neighbor cell is within the same PCU

Procedure 2: Neighbor cell data

After the target cell has been determined, the network sends the MS a Packet Neighbor Cell
Data (PNCD) message containing the information needed for the MS to access the target cell.
The neighbor cell information is sent to the MS in the source cell before the MS performs
cell reselection so that the MS can perform packet access without reading all of the system
information in the target cell. This procedure could also be an extension of Procedure 1 if the
network has information about the target cell.

2-162

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Interaction with QoS (Quality of Service)

Interaction with QoS (Quality of Service)

The areas where QoS and NACC/NCCR interact are detailed in the following sections.

Congestion Relief
When performing congestion relief, QoS has to be considered so as to not move high priority
users for the sake of reducing congestion. QoS signals if a cell is congested and also sends a
candidate list of mobiles preferable for cell reselection. Cell congestion and PRP congestion
are indicated separately by QoS. In both cases the candidate list of mobiles are the only list of
mobiles considered for cell reselection due to congestion relief. However, when PRP congestion
is indicated, only the mobiles that can be reselected to cells that are not on the congested PRP
are considered for cell reselection.

Idle Mode Cell Reselection

When MSs are in idle mode, the QoS congestion level is used to determine how to logically size
the cell for the idle mobiles in the cell. Idle mode congestion relief would help in QoS admission
control as it would reduce the number of mobiles waiting for resources in the cell.

Interaction with other features

This feature interacts with the IMRM feature, see for further details.

Network Assisted Cell Change (NACC) parameters

Table 2-32 details the parameters associated with the Network Assisted Cell Change (NACC)
feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS
parameter name. For further details of these and other parameters, see Technical Description:
BSS Command Reference (68P02901W23).

Table 2-32

Network Assisted Cell Change (NACC) parameters

OMC-R GUI field

name/BSS parameter
name

Description

Values

BSS parameters:
Network Assisted Cell
Change Feature
naccOpt

Displayed in the Optional Features

grouping of the BSS Detailed View.
Displays whether the Network
Assisted Cell Change Feature is
Unrestricted or Restricted for the
BSS.

0 or 1, where:
Restricted (0).
Unrestricted (1).
It cannot be
modified by a
user.

Cell Change Notification

Enabled
nacc_enabled

Displayed in the Network Assisted

Cell Change grouping of the BSS
Detailed View. Indicates whether
Cell Change Notification (CCN) is

0 or 1, where:
Disabled (0).
Enabled (1).
Continued

68P02901W17-T

2-163
Jan 2010

Network Assisted Cell Change (NACC) parameters

Table 2-32

Chapter 2: Configuring BSS Features

Network Assisted Cell Change (NACC) parameters (Continued)

OMC-R GUI field

name/BSS parameter
name

Description

Values

enabled or disabled for the BSS. Can

only be modified by a user if Network
Assisted Cell Change (NACC) feature
(naccOpt) is unrestricted for the BSS.
Cannot be set to 0 if the QoS feature
is enabled.

2-164

NC2 mode of Network

Assisted Cell Change
Enabled
nacc_nc2_enabled

The per-BSS element

nacc_nc2_enabled allows the
customer to enable or disable the
NC2 mode of Network Assisted Cell
Change (NACC).

0 or 1, where:
0 = NC2 mode of
NACC is off.
1 = NC2 mode of
NACC is on.

GPRS Type 5 Algorithm

Enabled
gprs_type5_alg

Displayed in the GPRS grouping

of the BSS Detailed View. Allows
enabling and disabling of the GPRS
type-5 microcellular algorithm for
the BSS. Enabling the GPRS type 5
algorithm is only allowed when the
NACC feature, microcellular feature
and NCCR feature are enabled for
the BSS.

0 or 1, where:
0 = GPRS type-5
algorithm is
disabled.
1 = GPRS type-5
algorithm is
enabled.

Congestion Threshold
gprs_cell_cgt_thr

Removed by introduction of the

QoS feature.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Enhanced Multi-level Precedence and Pre-emption (eMLPP)

Enhanced Multi-level Precedence and Pre-emption

(eMLPP)

Overview
Enhanced Multi-Level Precedence and Pre-emption (eMLPP) feature enhances the control of
call traffic by adding multi level precedence and pre-emption to the existing functionality of
prioritizing the calls and call queuing.

Background
Previous software allowed only two levels of priority; high priority and low priority. Emergency
calls were classified as high priority calls and non-emergency calls were classified as low priority
calls. Hence, only pre-emption of non-emergency calls by emergency calls was supported by
the system. The pre-emption was implemented within the BSS. The BSS ignored the PCI and
PVI information in the assignment request message from MSC. Pre-emption was performed
in the following:

TCH pre-emption emergency calls (high priority) calls are allowed to pre-empt the
non-emergency calls (low priority). TCH pre-emption during initial establishment is
supported for the emergency calls only when the ECP feature is enabled.

Ater pre-emption supported for the emergency calls (including Ater switchover) as an
option only when the ECP feature is enabled.

Mobis channel pre-emption supported for emergency calls by BTS concentration only
when the ECP feature is enabled.

Description of eMLPP
The eMLPP feature adds multi level priority (precedence), to which an originating and incoming
external handover call can be assigned.
The BSS conforms to 3GPP 48.008 standards in supporting the full set of priority and
pre-emption procedures.
Three kinds of resource pre-emption are supported: TCH, Ater channel, and queue block.
Pre-emption is supported for:

New call set up

External handover that comes into the BSS

Internal imperative handover (not queue block)

Call switchover by which calls do not necessarily need to be terminated due to a single
failure on the link set (not queue block).

68P02901W17-T

2-165
Jan 2010

eMLPP parameters

Chapter 2: Configuring BSS Features

When eMLPP is enabled:

In EAC mode (irrespective of whether ECP functionality is enabled), Ater pre-emption

based on priority is supported for call setup, external handover and internal imperative
handover requests.

In EAC/AC mode, Ater pre-emption is supported for call switchover.

It is responsibility of MSC to ensure that the priority, pci/pvi, and QA are set consistently for
emergency calls and non-emergency calls. It is responsibility of MSC to protect a TS12 call from
pre-emption by setting pvi = 0 to this kind of call. The BSS follows the pci/pvi and priority
settings as per MSC assigned values without any modification or validation. For example, if
the MSC mistakenly set pvi = 1 to an emergency call, this call is not protected and can be
pre-empted in BSS.
For a full description of NACC, see Technical Description: BSS Implementation (68P02901W36).

eMLPP parameters
Table 2-33 details the parameters associated with the Enhanced Multi-level Precedence and
Pre-emption (eMLPP) feature. Unless stated otherwise, the OMC-R parameter name is usually
the same as the BSS parameter name. For further details of these and other parameters, see
Technical Description: BSS Command Reference (68P02901W23).

Table 2-33 Enhanced Multi-level Precedence and Pre-emption (eMLPP) parameters

OMC-R GUI field
name/BSS parameter
name
EMLPP Feature
enhancedMLPPOpt

Description
Displayed in the Optional
Features grouping of the BSS
Detailed View. Displays
whether the Enhanced
Multi-Level Precedence and
Preemption (eMLPP) feature is
unrestricted or restricted.

Values
0 or 1, where:
Restricted (0).
Unrestricted (1).

Continued

2-166

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 2-33
(Continued)

eMLPP parameters

Enhanced Multi-level Precedence and Pre-emption (eMLPP) parameters

OMC-R GUI field

name/BSS parameter
name

Description

Values

Preemption Options
option_preempt
(previously called
option_emergency_
preempt)

Displayed in the Pre-emption

grouping in the BSS Detailed
View.
Displays the selected
pre-emption option.

0 - 3, or, 0 or 1.
If enhancedMLPPOpt
is enabled, the range is
0 - 3, where:
ECP and eMLPP
Disabled (0)
ECP Enabled eMLPP
Disabled (1)
ECP Disabled eMLPP
Enabled (2)
ECP and eMLPP
Enabled (3).
If enhancedMLPPOpt
is disabled, the range
is 0 - 1, where:
ECP Disabled (0)
ECP Enabled (1).
Default is 0.

Emergency Group Priority

emergency_
group_priority

Displayed in the Pre-emption

grouping in the BSS Detailed
View.
Defines a priority level
threshold for calls. Any call
(including handovers) with
higher or equal priority than
emergency_group_priority is
exempt from certain congestion
mechanisms. Grayed out if
enhancedMLPPOpt is disabled.

0 - 14.
Default is 0 meaning
no calls are exempt
(disabled) from
certain congestion
mechanisms.

PDTCH Priority
sw_pdtch_priority

Displayed in the Pre-emption

grouping in the BSS Detailed
View.
Indicates the priority level for
switchable PDTCH resources.
This ensures that the equal
or lower priority calls to the
PDTCH do not steal the PDTCH
resources. Grayed out if
enhancedMLPPOpt is disabled.

1 - 14.
Default is 14, meaning
priority protection
is disabled allowing
all calls to allocate
switchable PDTCH
resources.

68P02901W17-T

2-167
Jan 2010

Fast Call Setup

Chapter 2: Configuring BSS Features

Fast Call Setup

Overview
The Fast Call Setup feature speeds up the time taken to set up a standard voice call.

Description
The Fast Call Setup feature assigns the MS directly to the TCH during the IMMEDIATE
ASSIGNMENT message, when the available TCHs for the BCCH band are below the
operator-configured threshold. Once the TCH usage for the outer zone has equaled or exceeded
this threshold, the BSS performs assignment through the SDCCH. The benefits of this direct
assignment are:

Returning the MS from the SDCCH to the TCH is avoided.

Establishing the main signaling (LAPDm) is only done once.

The data throughput on the TCH is faster than that of the SDCCH.

The operatorconfigured thresholds can help avoid cell congestion due to phantom
RACHs.

Interaction with other features

This feature interacts with the IMRM feature, see for further details.

Fast Call Setup parameters

Table 2-34 details the parameters associated with the Fast Call Setup feature. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For
further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).

2-168

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Fast Call Setup parameters

Table 2-34 Fast Call Setup parameters

OMC-R GUI field
name/BSS parameter
name

Description

Values

BSS parameters:
Fast Call Service Feature
FastCallOpt

Displayed in the Optional Features

grouping of the BSS Detailed View.
Displays whether the Fast Call Service
feature is restricted (Disabled (0)) or
unrestricted (Enabled (1)). Cannot be
modified by a user.

0 or 1, where:
Disabled (0),
Enabled (1).

TCH Usage Threshold

tch_usage_
threshold
(OMC-R parameter name:
tch_usage_thrsld)

Displayed in the General Radio

Channel Configuration grouping of
the CELL Detailed View.
Indicates percentage of TCH usage,
at or above which the Fast Call
Service feature (FastCallOpt) is
disabled. This field is grayed-out
if the Fast Call Service feature
(FastCallOpt) is restricted (Disabled
(0)).

0 - 100.
Default is 0.

Immediate Assign Mode

immediate_assign_mode
(OMC-R parameter name:
immediateAssMode)

Deleted by the Fast Call Setup

feature.

CELL parameters:

68P02901W17-T

2-169
Jan 2010

RSL Congestion Control

Chapter 2: Configuring BSS Features

RSL Congestion Control

Overview
The Radio Signaling Link (RSL) Congestion Control feature protects downlink RSLs from GSM
paging surges, which can occur during events such as Formula 1 car crashes, football goal
scoring and so on. The controls are scalable, fault tolerant of message losses in the BSC's
LAN, and interact with the MSC.

Description
The purpose of RSL Congestion Control is to detect the onset of RSL congestion. When RSL
congestion is detected, any new service requirements are rejected and the MSC is notified with
an OVERLOAD message until the congestion abates. During the congestion, the BSS alarms the
OMC-R and provides a statistic with the amount of time a processor was in a congested state
and the number of OVERLOAD messages that were sent to the MSC.

RSL congestion control parameters

Table 2-35 details the parameters associated with RSL Congestion Control. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For
further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).

Table 2-35

RSL congestion control parameters

OMC-R GUI field

name/BSS parameter
name
RSL Congestion Upper
Threshold (%)
rsl_lcf_congestion_thi

Description

Values

Displayed in the RSL Congestion

grouping of the BSS Detailed View.
The high threshold to detect RSL
congestion on an RSLLCF. If the
RSLLCF board detects the number
of congested RSL links are more than
this percentage of the total number
of RSLs it services, then the RSLLCF
board is in congestion status.

1 - 100.
Default is 60%.
If set to 0%, the
BSS does not
send out XOFF
information on
RSLLCF.

Continued

2-170

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 2-35

RSL congestion control parameters

RSL congestion control parameters (Continued)

OMC-R GUI field

name/BSS parameter
name

Description

Values

RSL Congestion Lower

Threshold (%)
rsl_lcf_congestion_tlow

Displayed in the RSL Congestion

grouping of the BSS Detailed View.
The low threshold to detect RSLLCF
not in a congested state. If the
RSLLCF board detects the number
of congested RSL links are less than
this percentage of the total number
of RSLs it services, then the RSLLCF
board is out of congestion status.

0 - 99.
Default is 25%.

Overload Messages Timer

Interval (ms)
bss_overload_control

Displayed in the RSL Congestion

grouping of the BSS Detailed View.
Defines the OVERLOAD message
interval. This avoids reducing the
A-interface traffic too rapidly.

1000 - 1000000
(ms).
Default is 12500
(ms).

RSL Congestion Alarm

Clear Time (ms)
rsl_congestion_alarm
_timer

Displayed in the RSL Congestion

grouping of the BSS Detailed View.
Defines the minimum interval
between reporting and clearing RSL
congestion alarms to the OMC-R on a
per RSLLCF basis.

1000 - 600000
(ms)
Default is 60000
(ms).

Send Overload Messages

to MSC
msc_bss_overload
_allowed
(OMC-R parameter name:
msc_bss_ovld_alw)

Displayed in the RSL Congestion

grouping of the BSS Detailed View.
Enables or disables the BSC to send
an OVERLOAD message to the MSC
when there is RSL congestion.

0 or 1, where:
Disabled (0),
Enabled (1).
Default is
Disabled (0).

Max Number of Page

Messages per Second
max_pagenum_per_sec

Displayed in the RSL Congestion

grouping of the BSS Detailed View.
Defines the maximum number of
PAGE messages that can be sent from
the BSC to a BTS in a second.

70 - 65535.
Default is
65535.

68P02901W17-T

2-171
Jan 2010

VersaTRAU

Chapter 2: Configuring BSS Features

VersaTRAU

Overview
The VersaTRAU feature is an extension to the General Packet Radio Service (GPRS) and the
Enhanced GPRS (EGPRS) feature. Currently each timeslot in an EGPRS carrier is allocated 64 k
TRAU regardless of whether the timeslot is being used for EGPRS coding schemes, GPRS
coding schemes, or voice. The VersaTRAU feature provides dynamic TRAU capability to EGPRS
Carriers to optimize backhaul usage and reduce costs.
This feature is only available if the EGPRS (egprsOpt) feature is unrestricted (enabled).
VersaTRAU channel information is displayed in the Channel Status form, see Displaying Channel
and Circuit Status on page 9-20.

NOTE
A 16 k TRAU Half Rate call is not supported on a 64 k carrier, regardless of whether
VersaTRAU is restricted or unrestricted.
A VersaTRAU Backhaul Summary report can be displayed from the Navigation Tree by
right-clicking the site instance and then selecting VersaTrau Backhaul Summary option from the
drop-down list, see OMC-R Online Help, Network Operations for further details.

Description
The VersaTRAU feature reduces backhaul costs by taking advantage of statistical multiplexing
that can be achieved when packing variable size radio blocks, to be sent over PDCHs on a
carrier, into one large TRAU frame associated with the carrier. This feature creates a pool
of DS0s connections between the BTS and PCU for an EDGE carrier. The size of the pool is
allocated by the operator depending on anticipated data traffic for the site. EDGE data packets
are routed onto this pool as required.
The VersaTRAU feature eliminates the static mapping between a PDCH and backhaul resources.
All the PDCHs on a 64 k carrier shares a group of DS0s defined by a VersaTRAU channel.
The feature eliminates the need for one-to-one mapping of air TSs and TRAU slots and instead
allows configuration of a versatile TRAU backhaul that will carry the data load for a carrier.
The impacts to backhaul synchronization are minimal; expanding and contracting the number of
air timeslots and/or TRAU timeslots is done seamlessly as long as at least one air timeslot on
the VersaTRAU carrier is in synchronization

2-172

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Permissible values for RTF backhaul timeslots

Permissible values for RTF backhaul timeslots

Table 2-36 shows the possible range, default values and accessibility for the RTF Detailed View
field: Number of Backhaul Timeslots on Carrier (rtf_ds0_count) (also see Table 2-37). The
fields Packet Radio Type (pkt_radio_type), Half Rate (half_rate_enabled), 8 k TRAU Allowed
(allow_8k_trau) are all displayed in the RTF Detailed View (see RTF Detailed View fields on
page 9-185).

Table 2-36 Possible values for RFT field: Number of Backhaul Timeslots on Carrier
(rtf_ds0_count)
Packet
Radio
Type
field

EGPRS
enabled

VersaTRAU
enabled

64 k (3)

YES

64 k (3)

BCCH

Half
Rate
field

8k
TRAU
Allowed
field

Valid
range

Default

Sensitivity?

YES

YES

Disabled

N/A

3 to 7

Sensitive

YES

YES

YES

Enabled

YES

3 to 7

Sensitive

64 k (3)

YES

YES

NO

Disabled

N/A

3 to 8

Sensitive

64 k (3)

YES

YES

NO

Enabled

YES

3 to 8

Sensitive

64 k (3)

YES

NO

YES

N/A

N/A

Value of
7 sent
from
BSS.

Insensitive

64 k (3)

YES

NO

NO

N/A

N/A

Value of
8 sent
from
BSS.

Insensitive

None

N/A

N/A

N/A

N/A

N/A

1 to 8

Value
sent
from
BSS.

Grayedout

16 k (1)

N/A

N/A

N/A

N/A

N/A

1 to 8

Value
sent
from
BSS.

Grayedout

32 k (2)

N/A

N/A

N/A

N/A

N/A

1 to 8

Value
sent
from
BSS.

Grayedout

68P02901W17-T

2-173
Jan 2010

VersaTRAU parameters

Chapter 2: Configuring BSS Features

VersaTRAU parameters
Table 2-37 details the parameters associated with VersaTRAU. Unless stated otherwise,
the OMC-R parameter name is usually the same as the BSS parameter name. For further
details of these and other parameters, see Technical Description: BSS Command Reference
(68P02901W23).

Table 2-37 VersaTRAU parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

BSS parameters:
VersaTRAU Feature
versaTrauOpt

Displayed in the Optional Features

grouping of the BSS Detailed View.
Indicates whether versaTRAU feature
is unrestricted (enabled) or restricted
(disabled).
Cannot be modified by a user.
This feature is only available if
the EGPRS feature (egprsOpt) is
unrestricted (enabled).

0 or 1, where:
Disabled (0).
Enabled (1).

Displayed in the GPRS grouping of the

RTF Detailed View. If the VersaTRAU
feature is enabled, defines the
number of DS0s for RTF backhaul,
when equipping an EGPRS capable
RTF (64 k RTF).
Modifying this field displays the
following message:
WARNING: This operation may
cause a carrier to be taken out
of service and calls affected
by this carrier may be lost.
Loss of calls depends on the
availability of other carriers.
Do you wish to modify?

1 - 8.
See Table 2-36
for details of
possible values
and defaults.

RTF parameters:
Number of Backhaul
Timeslots on Carrier
rtf_ds0_count

2-174

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Feature Capacity Licensing and Audit

Feature Capacity Licensing and Audit

Feature description
The License Audit tool monitors the usage of the carriers across the customer network on a
per feature basis. Information is gathered by running scheduled audits against the OMC-R
Configuration Management database to produce a report indicating how many RTF(s) are
equipped in the database to support each feature. This feature extends the License Audit only
functionality to provide license file comparison and customer notification of license overruns.
Each software release has a list of features that are monitored for carrier capacity usage. The
OMC software triggers the License Audit tool at pre-defined intervals, which can be configured
by the customer.
The License Audit tool is extended on each release to incorporate new features in the audit
functions. For each customer, a license file is issued which contains the information on current
licensed capacity for every licensable feature. A single license key is provided to control this
information per network.
The License Audit Tool is distributed with the OMC software, and installed and configured by
the user. The audit is triggered by a configurable interval parameter in the OMC software. If
the interval parameter is not set, or set outside the permissible range [2 hours, 48 hours],
the default value of 12 hours is used. The result of the audit (actual usage) is compared with
the license file per feature. An alarm is generated when the carrier usage for one or more
features exceeds the carriers purchased for those features. If the usage is within the limit, the
License Audit Tool generates an event which indicates that the carrier usage is within the
license purchase. The alarms and events are displayed at one or all OMC(s) in the network as
previously configured during installation and configuration.
The License Audit Tool produces a report which is stored in a predefined location containing the
result of the latest audit and license file comparison. Users and Motorola have access to this
report by physically accessing the location where the file is stored.

Configuration and operation

Details regarding the configuration and operation of the License Audit tool are described in the
manual System Information: License Audit (68P02901W59).

68P02901W17-T

2-175
Jan 2010

Improved Timeslot Sharing

Chapter 2: Configuring BSS Features

Improved Timeslot Sharing

Overview
Improved Timeslot Sharing (ITS) feature is an optional feature, which supports Enhanced GPRS
(EGPRS) on a Double Density (DD) CTU2. It requires no hardware changes to the CTU2, BSS
software and Horizon II firmware. In that way the EGPRS PDTCH (Packet Data Traffic Channel)
can only be configured on Carrier A of a DD CTU2 while the corresponding timeslots on the
paired Carrier B must be blanked out.
Improved Timeslot Sharing (ITS) feature is only available if the EGPRS (egprsOpt) and
VersaTRAU (versaTrauOpt) are unrestricted (enabled).
ITS provides more channels to service voice users with EGPRS service in parallel and when
implemented in the EGPRS network it further improves the network capacity.

Interaction with other features

ITS interacts with the following features:

VersaTRAU

Enhanced Multi-level Precedence and Pre-emption (eMLPP)

NOTE
The ITS feature requires the EGPRS and VersaTRAU features to be unrestricted.

ITS parameters
Table 2-38 details the parameters associated with Improved Timeslot Sharing. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name.

Table 2-38

ITS parameters

OMC-R GUI field name/BSS

parameter name
Improved Timeslot
Sharing Feature
itsOpt

Description

Values

Displayed in the Optional

Features grouping of
the BSS Detailed View.
Indicates whether ITS is
unrestricted (enabled) or
restricted (disabled).

0 or 1, where: Disabled
(0). Enabled (1).

Continued
2-176

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 2-38

ITS parameters (Continued)

OMC-R GUI field name/BSS

parameter name
Improved Timeslot
Sharing Enabled
improve_ts_enabled
(OMC-R parameter name:
its_enabled)

68P02901W17-T

ITS parameters

Description

Values

Displayed in the Improved

Timeslot Sharing group of
the BSS Detailed View.

0 or 1, where: Disabled
(0). Enabled (1).

2-177
Jan 2010

GPRS - Suspend/Resume

Chapter 2: Configuring BSS Features

GPRS - Suspend/Resume

Overview of GPRS Suspend/Resume

The GPRS Suspend and Resume feature provides the BSS system the ability to suspend and
resume GPRS services.

Description of GPRS Suspend/Resume

The MS requests the network for a suspension of GPRS services by sending a Suspend message
to the network if the following conditions exist:

A GPRS attached MS enters dedicated mode and the support of Class A mode of operation
is not possible.

An MS in Class A mode of operation is handed over to cell and the Class A mode of
operation is not possible.

The BSC tracks the MS status as Suspended after receiving a Suspend Ack message from
the SGSN.
Once the conditions for the suspension of GPRS services no longer exist the BSS sends a
Resume message to the SGSN. If a Resume Ack message is received from the SGSN, the BSS
sends a GPRS Resumption message to the MS to notify the MS that it can resume GPRS service.
The MS resumes GPRS services by sending a Routing Area Update Request to the SGSN if one
of the following conditions exist:

If the BSS fails to request the SGSN to resume GPRS services.

If the RR Channel Release message was not received before the MS left dedicated mode.

If the MS locally determines that the conditions for GPRS suspension have disappeared.

NOTE
The GPRS Resume functionality is supported at the intraBSC level only.

Measuring Suspend/Resume statistic

The database statistic NUM_SUSP_RESU_RCVD measures per BSS the number of:

Responses received for Suspend and Resume.

No responses received for Suspend and Resume.

Resume not triggered due to different reasons.

See Maintenance Information: GSM Statistics Application (68P02901W56) for full statistics
details.
2-178

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GPRS - Suspend/Resume dependencies

GPRS - Suspend/Resume dependencies

The GPRS - Suspend/Resume requires the GPRS feature (gprsOpt) to be unrestricted (enabled).

GPRS - Suspend/Resume parameters

Table 2-37 details the parameters associated with GPRS - Suspend/Resume feature. Unless
stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name.
For further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).

Table 2-39

GPRS - Suspend/Resume parameters

OMC-R GUI field name/BSS

parameter name

Description

Values

BSS parameters:
GPRS - Suspend/Resume
Feature
bssgp_t4_timer

68P02901W17-T

Displayed in the SSM

Timers grouping of the
BSS Detailed View.
Indicates the timer used to
guard the GPRS Suspend
/Resume procedures.
The PCU starts this timer
once RESUME PDU or
SUSPEND PDU is sent out
to an SGSN.
The timer stops when
the PCU receives a
RESUME ACK/NACK PDU
or SUSPEND ACK/NACK
PDU from the SGSN.

100 - 10000 ms
Default: 800.

2-179
Jan 2010

Configuring GPRS - Suspend/Resume parameter using the TTY interface

Chapter 2: Configuring BSS Features

Configuring GPRS - Suspend/Resume parameter using the

TTY interface
The disp_element and chg_element commands can be used to display and configure the GPRS
- Suspend/Resume parameter bssgp_t4_timer.
Use the disp_element command to display the value of the bssgp_t4_timer. For example, the
following command displays the current value of the bssgp_t4_timer at BSS location 0:
disp_element bssgp_t4_timer 0
The system replies, for example:
bssgp_t4_timer = 800
Use the chg_element command to modify the value of the bssgp_t4_timer. For example,
the following command modifies the current value of the bssgp_t4_timer at BSS location 0,
to 300 ms.
chg_element bssgp_t4_timer 300 0
The system replies:
COMMAND ACCEPTED

2-180

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Increased Network Capacity

Increased Network Capacity

Overview of Increased Network Capacity

The Increased Network Capacity feature is an optional feature. This feature increases the
system capacity limits as follows:

Maximum Carriers per BSC from 512 to 750

Maximum Sites per BSC from 100 to 140

Maximum Circuits per BSC from 3200 to 4800

Maximum number of BSC-XCDR connections a BSC can support increases from 27 to 42

Determining whether Increased Network Capacity is enabled

It is possible to use the OMC-R GUI or the TTY interface to determine if Increased Network
Capacity is enabled.

Using the OMC-R GUI

To check if the Increased Network feature has been enabled using the OMC-R GUI, display
the setting of Increased Network Capacity Feature (incNetCapacityOpt) field. This field is
located in the Optional Features grouping in the BSS Detailed View. The values for Increased
Network Feature field are:

Disabled (0)

Enabled (1)

Using the TTY interface

To check if Increased Network feature has been enabled using the TTY interface, enter the
following command: disp_options all
If the Increased Network Capacity is unrestricted (enabled) the system displays the following in
the unrestricted list:
81 Increased Network Capacity

68P02901W17-T

2-181
Jan 2010

Interaction with other features

Chapter 2: Configuring BSS Features

Interaction with other features

The Increased network Capacity feature interacts with the following features:

2-182

Enhanced BSC capacity using DSW

BSC High Load Protection Mechanism Phase 2

LAN Packing

HSP MTL

BSP CPU utilization reduction for higher Call handling Capacity

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSC High Load Protection Mechanism Phase 2

BSC High Load Protection Mechanism Phase 2

Overview of BSC High Load Protection Mechanism Phase 2

The BSC High Load Protection Mechanism feature allows the BSC to operate reliably during
periods of high utilization and to deal efficiently when traffic surges occur. It provides this
reliability by monitoring the Base Site control Processor (BSP) CPU utilization inreal-time.
When the BSP CPU utilization reaches the overload threshold, this feature starts controlling
the amount of calls and handovers to be handled by the system, so that the CPU utilization of
the BSP can be kept under a safe level. This mechanism allows the BSP to operate reliably at
90% utilization.

BSC High Load Protection Mechanism Phase 2 parameters

Table 2-40 details the parameters associated with the BSC High Load Protection Mechanism
feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS
parameter name. For further details of these and other parameters, see Technical Description:

BSS Command Reference (68P02901W23)

Table 2-40

BSC High Load Protection Mechanism Phase 2 parameters

OMC-R GUI field name/BSS

parameter name

Description

Values

BSS parameters:
BSC High Load Protection
Mechanism Phase 2
Feature
bsp_overload_protection
(OMC-R parameter name:
bsp_ovld_protect)

Displayed in the BSP

Overload Protection group
of the BSS Detailed View.
Enables or disables the
monitoring of the BSP
CPU utilization.

0 or 1, where:
Disabled (0)
Enabled (1)
Default is Disabled (0)

Configuring BSC High Load Protection Mechanism Phase 2

It is possible to use the OMC-R GUI or the TTY interface to enable or disable BSC High Load
Protection Mechanism Phase 2 feature.

Using the OMC-R GUI

To check if the BSC High Load Protection Mechanism Phase 2 feature has been enabled using
the OMC-R GUI, display the setting of BSP CPU Overload Protection (bsp_overload_protection)
field. This field is located in the BSP Overload Protection grouping in the BSS Detailed View.
The values are detailed in Table 2-40.

68P02901W17-T

2-183
Jan 2010

Configuring BSC High Load Protection Mechanism Phase 2

Chapter 2: Configuring BSS Features

Using the TTY interface

The disp_element and chg_element commands can be used to display and enable or disable
the BSP CPU Overload Protection parameter bsp_overload_protection.
To check if the BSC High Load Protection Mechanism Phase 2 feature has been enabled using
the TTY interface, enter the following command: disp_element bsp_overload_protection
<location>. For example, the following command displays the current value of the
bsp_overload_protection at BSS location bsc:
disp_element bsp_overload_protection bsc
The system replies, for example:
bsp_overload_protection = 1
Use the chg_element command, chg_element bsp_overload_protection <value>
<location>to enable or disable the value of the bsp_overload_protection. For example, the
following command disables the bsp_overload_protection at location bsc.
chg_element bsp_overload_protection 0 bsc
The system replies:
COMMAND ACCEPTED

2-184

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

HSP MTL

HSP MTL

HSP MTL
The HSP MTL feature increases the capacity and the flexibility of the Signaling Links Set
between the BSC and each MSC. Each BSC is connected to each MSC with a Signaling Link Set
(SLS). Each Signaling Link Set can accommodate up to 16 distinct Signaling Links (SL).
At present the BSC supports each Signaling Link with a 64kbit/s DS0. As a result of the BSC
capacity increasing it is now necessary to increase the capacity of the MTLs (MTP Transport
Layer Link (A-Interface)). The High Speed MTL feature increases the maximum number of
message transfer links to 31.
For a full description of HSP MTL, see Technical Description: BSS Implementation
(68P02901W36).

Prerequisites to configuring HSP MTL

Before configuring HSP MTL ensure that the Increased Network feature incNetCapacityOpt
has been enabled. See Increased Network Capacity on page 2-181 for further details.

HSP MTL parameters

Table 2-41 details the parameters associated with the HSP MTL feature. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For
further details of these and other parameters, see Technical Description: BSS Command

Reference (68P02901W23).

68P02901W17-T

2-185
Jan 2010

HSP MTL parameters

Chapter 2: Configuring BSS Features

Table 2-41 HSP MTL parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

mtl_rate

Displayed in the
Identification grouping
of the MTL Detailed View.
Defines the type of MTL to
create.

If the Increased
Network feature is
enabled valid values are
1 or 31.
1= 64k MTL
31 = HSP MTL
Default is 1.

ss7_hsp_l2_t1

Displayed in the MTP

Timers grouping of the
BSS Detailed View. Can
only be modified, if
incNetCapacityOpt is
unrestricted (enabled).
Otherwise, the field is
grayed out in the BSS
Detailed View form.

Valid values: 25000 350,000 ms. Default is

300,000 ms.

max_mtls

Displayed in the
Identification grouping
of the BSP Detailed View.
The number of message
transfer links that the BSP
can handle. The values 0
to 2 are for 64k MTL and
31 for HSP MTL.

0, 1, 2 or 31.
31 is valid only if the
Increased Network
feature is enabled.

Displayed in the
Identification grouping
of the LCF Detailed View.
The number of message
transfer links that the LCF
can handle. The values 0
to 2 are for 64k MTL and
31 for HSP MTL.

0, 1, 2 or 31.
31 is valid only if the
Increased Network
feature is enabled.

BSS parameters:

Continued

2-186

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

HSP MTL parameters

Table 2-41 HSP MTL parameters (Continued)

OMC-R GUI field name/BSS
parameter name
max_gsls

max_cbls

68P02901W17-T

Description
Displayed in the
Identification grouping
of the LCF Detailed View.
The maximum number of
GSLs the LCF can manage.
Only displayed if:

GPRS feature is
unrestricted.

Sum of max_gsls is
greater than or equal
to the total number
of GSLs equipped.

Value of max_gsls
must not exceed the
available LCF HDLC
channel capacity.

max_gsls can be
changed to non zero
value only when
max_mtls is not equal
to 31.

Displayed in the
Identification grouping
of the LCF Detailed View.
The maximum number of
CBLs the LCF can manage.

Values
0 - 12.

0 or 1
1 is valid only if
max_mtls is not equal
to 31.

2-187
Jan 2010

Software patching and PCU Software Upgrade with no BSC Outage

Chapter 2: Configuring BSS Features

Software patching and PCU Software Upgrade with no

BSC Outage

Overview of Software patching and PCU Software Upgrade with

no BSC Outage
The software patching section of this feature allows the NE software to be dynamically modified
without requiring an NE Element restart. The software patch (Patch Object) contains NE
Software changes which after downloading modifies all existing objects. A Patch Object is
made up of one or more patch levels compiled together into a Patch Object. The Patch Level
corresponds to a patch (fix) or group of patches which address a single problem.
The PCU Software Upgrade section of this feature allows new PCU objects to be downloaded and
installed at the PCU without requiring a BSS outage. The new PCU objects can be downloaded
to the BSC using CSFP download, and from there downloaded to the PCU. After download is
completed a swap code object is carried out.

Software patching and PCU Software Upgrade with no BSC

Outage parameters
Table 2-42 details the parameters associated with the Software patching and PCU Software
Upgrade with no BSC Outage feature. Unless stated otherwise, the OMC-R parameter name is
usually the same as the BSS parameter name. For further details of these and other parameters,
see Technical Description: BSS Command Reference (68P02901W23).

2-188

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

patching and PCU Software Upgrade with no BSC Outage parameters

Software

Table 2-42 Software patching and PCU Software Upgrade with no BSC Outage
parameters
OMC-R GUI field name/BSS
parameter name

Description

Values

BSS and RXCDR

parameters:
NE Patch Object Version
nePatchObjectVer

Displayed in the
Identification grouping
of the BSS or RXCDR
Detailed View form.
Displays the version of
the Patch Object. The
value 0 indicates that no
Patch Object is installed.
This parameter cannot be
modified by a user and is
not displayed for a BSS or
RXCDR with Pre-GSR10
software loads.

0 - 255
Default is 0

NE Patch Object Level

nePatchObjectLev

Displayed in the
Identification grouping
of the BSS or RXCDR
Detailed View form.
Displays the Patch Object
Level number set for the
NE. The range is the
maximum Patch Level of
that Patch Object. The
value 0 indicates that no
Patch Level is installed.
This parameter cannot be
modified by a user and is
not displayed for a BSS or
RXCDR with Pre-GSR10
software loads.

0255
Default is 0

Displayed in the General

grouping of the PCU
Detailed View form.
Displays the CSFP flow
control value that controls
the amount of GSL link
utilization that a CSFP
download from BSC to
PCU uses.
This parameter is also
applicable for BTS
CSFP. For BTS CSFP,
this parameter controls
the RSL utilization for
CSFP download.

10 100
Select in increments of
10. Default is 10.

PCU parameters:
CSFP Flow Value
csfp_flow

68P02901W17-T

2-189
Jan 2010

PCU hardware to increase GPRS capacity

Chapter 2: Configuring BSS Features

PCU hardware to increase GPRS capacity

Overview
The new Universal DPROC2 (U-DPROC2) replaces all existing DPROCs and increase GPRS
capacity. The U-DPROC2 creates a functionality called PXP, which combines PRP and PICP
functionality on the same board. The boards are connected with the PSI board in BSC through a
Gigabit Ethernet link (GbE).
E1 GDS connectivity is supported on PRP/PICP, but not on the PXP. The PRP part of PXP
functionality is lost if the Ethernet link goes OOS.
U-DPROC2 can be configured as a PRP and PICP. U-DPROC2 can coexist with a DPROC, which
serves as PRP or PICP. It can function as PRP or PICP. Each U-DPROC2 must be paired with a
U-DPROC2 RTM (Rear Transition Module). Pairing a U-DPROC2 board with a RTM module or
pairing a DPROC board with a U-DPROC2 RTM module is not supported.
The PCU supports hot swap capability and provides thermal monitoring for U-DPROC2 boards.
The PCU is controlled by a single BSC.
This feature reduces the PCU maintenance requirements and configuration complexity.

PCU hardware to increase GPRS capacity parameters

Table 2-43 details the parameters associated with the U-DPROC2. Unless stated otherwise, the
OMC-R parameter name is usually the same as the BSS parameter name. For further details
of these and other parameters, refer to Technical Description: BSS Command Reference

(68P02901W23).

2-190

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PCU hardware to increase GPRS capacity parameters

Table 2-43 PCU hardware to increase GPRS capacity parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

eth_rx_errors_threshold

It specifies the maximum

allowable percentage of error
among the Ethernet frames
received. The percentage
parameter is on a per BSS
basis. 0 indicates that there
is no alarm generated. This
parameter changes inside and
outside of SYSGEN mode.

0 - 100
Default is 10

eth_tx_errors_threshold

It specifies the maximum

allowable percentage of
Ethernet transmit errors of
all frames transmitted. The
percentage parameter is on a
per BSS basis. 0 indicates that
there is no alarm generated.
This parameter changes
inside and outside of SYSGEN
mode.

0 - 100
Default is 10

psi_trau_fill_frames_
threshold

It specifies the maximum

allowable percentage of all
TRAU frames transmitted
that can be fill frames. The
percentage parameter is on a
per BSS basis. 0 indicates that
there is no alarm generated.
This parameter changes
inside and outside of SYSGEN
mode.

0 - 100
Default is 10

prpThptOpt

This parameter indicates

whether the Increase PRP
Throughput with PCU feature
is unrestricted in the BSS
software. If the prpThptOpt
flag indicates that Increase
the Throughput of PRP with
PCU is restricted, attempts to
change this feature-specific
database parameters are
rejected.

0 - restricted
1 unrestricted

Continued

68P02901W17-T

2-191
Jan 2010

PCU hardware to increase GPRS capacity parameters

Chapter 2: Configuring BSS Features

Table 2-43 PCU hardware to increase GPRS capacity parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

dsp_error_inc

This database parameter

identifies the value by
which the error count is
incremented if an error
indication is received for a
DSP during a GPRS Alarm
Increment Time Period. This
parameter defaults to 1
when the ECERM feature is
unrestricted and it defaults to
0 when the ECERM feature is
restricted. It exists only at a
BSC and it is modified inside
or outside of SYSGEN mode.

0 - 255
Default is 1

dsp_error_gen_thresh

This database parameter

identifies the value that the
error count must be equal to
or greater than for an alarm
to be generated for a DSP.
This parameter is restricted
by the ECERM restrictable
feature and is modified inside
or outside of SYSGEN mode.
It exists only at a BSC. If
the value of this parameter
is reduced, no alarms are
generated for those DSPs
whose current error counts
are equal to or exceed the
new value.

2 - 255
Default is 6

dsp_error_clr_thresh

This database parameter

identifies the value that the
error count must be equal
or less than for an alarm to
be cleared for a DSP. This
parameter is restricted by the
ECERM restrictable feature.
It is modified inside or outside
of SYSGEN mode and exists
only at a BSC. If the value of
this parameter is increased,
no alarms are cleared for
those DSPs whose current
error counts are now equal
to or below the new value
until another GPRS Alarm
Increment Time Period passes
without error for the DSP.

0 - 253
Default is 0

Continued

2-192

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Dependencies

Table 2-43 PCU hardware to increase GPRS capacity parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

gds_connectivity

This parameter indicates GDS

connectivity.

Minimum value
is 0 or E1.
Maximum value is
1 or Ethernet.

bsc_eth

This parameter describes the

Ethernet connectivity.
psi_id indicates a unique PSI
ID.
bsc_eth_port indicates the
BSC Ethernet port.

Minimum value:
psi_id - 0
bsc_eth_port - 0

pcu_eth

This parameter describes the

Ethernet connectivity.
dproc_id indicates a unique
DPROC ID.
pcu_eth_port indicates the
PCU Ethernet port.

Maximum value:
psi_id - 11
bsc_eth_port - 0
Minimum value:
dproc_id - 1
pcu_eth_port - 0
Maximum value:
dproc_id - 16
pcu_eth_port - 0

Dependencies
This feature depends on the following:

High Bandwidth interconnection between BSC and PCU (PSI)

Increase the PCU database capacity

Packet/Coaxial Interface Module

Air Flow Improvements for the PCU Cabinet

68P02901W17-T

2-193
Jan 2010

High Bandwidth interconnection between BSC and PCU (PSI)

Chapter 2: Configuring BSS Features

High Bandwidth interconnection between BSC and PCU

(PSI)

Overview
This feature uses a PSI (Packet Subrate Interface) to reduce the number of cables between the
BSC and the PCU. This enables the BSC to handle higher capacity configurations. The PSI
provides an Ethernet link from the BSC to the PCU.
Instead of using two MSIs to allow up to 120 timeslots of EDGE data, one slot is occupied
by a PSI to allow configurable timeslots from 64 - 320. The freed MSI slot can be used for 2
downstream or upstream span lines.

High Bandwidth interconnection between BSC and PCU

parameters
Table 2-44 details the parameters associated with the feature High Bandwidth interconnection
between BSC and PCU. Unless stated otherwise, the OMC-R parameter name is usually the
same as the BSS parameter name. For further details of these and other parameters, refer to

Technical Description: BSS Command Reference (68P02901W23).

Table 2-44 High Bandwidth interconnection between BSC and PCU parameters
OMC-R GUI field name/BSS
parameter name

Description

Value

eth_rx_errors_threshold

It specifies the maximum

allowable percentage of error
among the Ethernet frames
received. The percentage
parameter is on a per BSS basis.
0 indicates that there is no alarm
generated. This parameter
changes inside and outside of
SYSGEN mode.

0 100
Default is 10

eth_tx_errors_threshold

It specifies the maximum

allowable percentage of
Ethernet transmit errors of
all frames transmitted. The
percentage parameter is on a
per BSS basis. 0 indicates that
there is no alarm generated.
This parameter changes inside
and outside of SYSGEN mode.

0 100
Default is 10

Continued

2-194

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Bandwidth interconnection between BSC and PCU parameters

Table 2-44
(Continued)

High

High Bandwidth interconnection between BSC and PCU parameters

OMC-R GUI field name/BSS

parameter name

Description

Value
0 100
Default is 10

psi_trau_fill_frames_
threshold

It specifies the maximum

allowable percentage of all
TRAU frames transmitted
that can be fill frames. The
percentage parameter is on a
per BSS basis. 0 indicates that
there is no alarm generated.
This parameter changes inside
and outside of SYSGEN mode.

dsp_error_in

This database parameter which

identifies the value by which the
error count is incremented if
an error indication is received
for a DSP during a GPRS Alarm
Increment Time Period. This
parameter defaults to 1 when the
ECERM feature is unrestricted
and it defaults to 0 when the
ECERM feature is restricted.
It exists only at a BSC and is
modified inside or outside of
SYSGEN mode.

0 255
Default is 1

dsp_error_gen_thresh

This database parameter

identifies the value that the
error count must be equal to
or greater than for an alarm to
be generated for a DSP. This
parameter is restricted by the
ECERM restrictable feature. It
is modified inside or outside of
SYSGEN mode and exists only
at a BSC. If the value of this
parameter is reduced, no alarms
are generated for those DSPs
whose current error counts
are equal to or exceed the new
value.

2 255
Default is 6

Continued

68P02901W17-T

2-195
Jan 2010

Interaction with other features

Table 2-44
(Continued)

Chapter 2: Configuring BSS Features

High Bandwidth interconnection between BSC and PCU parameters

OMC-R GUI field name/BSS

parameter name
dsp_error_clr_thresh

Description

Value

This database parameter

identifies the value that the
error count must be equal
or less than for an alarm to
be cleared for a DSP. This
parameter is restricted by the
ECERM restrictable feature.
It is modified inside or outside
of SYSGEN mode and exists
only at a BSC. If the value of
this parameter is increased, no
alarms are cleared for those
DSPs whose current error counts
are now equal to or below the
new value until another GPRS
Alarm Increment Time Period
passes without error for the DSP.

0 253
Default is 0

Interaction with other features

This feature interacts with the following:

2-196

PCU hardware to increase GPRS capacity

Increase the PCU database capacity

Packet/Coaxial Interface Module

Increase throughput of PRP

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Increase the Throughput of PRP with the PCU

Increase the Throughput of PRP with the PCU

Overview
The current PRP processor has a fanout of 120 PDCHs but only has a throughput of 30 PDCHs.
A rolling blackout mechanism is used to choose which 30 of the 120 PDCHs are serviced in a 20
ms block period. Increase the throughput of PRP with the PCU is an optional feature that
provides an option to disable the rolling blackout mechanism on the PCU so that the throughput
of the PRP processor is the same as the fanout of the PRP. It provides two options, mode 1 and
mode 2. Refer to Table 2-45 for the processing capacity in mode 1 and mode 2. This feature
resides on the BSC and PCU.
When the rolling blackout mechanism is enabled, a maximum of X timeslots in a PRP are allowed
to perform data transfers in each direction (uplink and downlink) during every block period.
Without rolling blackout mechanism, all timeslots configured in a PRP are allowed to perform
data transfers in both uplink and downlink directions.
A PXP configured by the UDPROC-2 board has higher capacity and throughput. The increased
throughput of the PRP offers improved support for high throughput services such as HTTP,
PoC, and video streaming.

Table 2-45 PRP capacity

DPROC configuration

Total Fanout/Throughput/Number of mobiles

Mode 1

Mode 2

DPROC/PRP or U-DPROC2/PRP

120/30/120

60/60/60

U-DPROC2/PXP

280/70/280

140/140/280

Increase the Throughput of PRP with the PCU parameters

Table 2-46 details the parameters associated with Increase the Throughput of PRP with the
PCU feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the
BSS parameter name. For further details of these and other parameters, refer to Technical
Description: BSS Command Reference (68P02901W23).

68P02901W17-T

2-197
Jan 2010

Interaction with other features

Chapter 2: Configuring BSS Features

Table 2-46 Increase the Throughput of PRP with the PCU parameters
OMC-R GUI field name/BSS
parameter name

Description

Values

prpThptOpt

The prpThptOpt parameter

indicates whether the
Increase PRP Throughput
with PCU feature is
unrestricted in the BSS
software.
If the prpThptOpt flag
indicates that Increase the
Throughput of PRP with PCU
is restricted, attempts to
change this feature-specific
database parameter are
rejected.

0 - 1
0 - restricted
1 - unrestricted

prp_fanout_mode

The prp_fanout_mode
parameter indicates the
PDCHs fanout mode of the
PRP in the PCU. The fanout
mode of the PRP provides
the preference of more
PDCH capacity or higher
throughput of the PRP.
When prp_fanout_mode is
in mode 1, more PDCHs
can be configured in a PRP,
and RLC data blocks can be
only scheduled on a number
of PDCHs. The rest of the
PDCHs in the PRP can be
used for RLC control blocks.
When prp_fanout_mode
is in mode 2, this allows
higher throughput of the
PRP with fewer PDCHs
configured. RLC data blocks
are scheduled on all the
PDCHs in the PRP.
This parameter can only be
modified if the optional
feature Increase the
Throughput of PRP with
PCU is unrestricted.

1 - 2
Default is 1
1 - the rolling
blackout mechanism
is enabled at the PCU
2 - the rolling blackout
mechanism is disabled
at the PCU

Interaction with other features

This feature interacts with the following:

2-198

PCU hardware to increase GPRS capacity

Software on old platform without new hardware

QoS Streaming

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Support of Incell as an optional feature

Support of Incell as an optional feature

Overview
This feature provides the option to restrict the use of Incell BTS sites within a network if
required. During the database upgrade (upgrading GSR9 database to GSR10) the system does
not allow any Incell site to be equipped in the database unless the customer has purchased
this feature. This feature also restricts the adding of Incell hardware if the option has not
been purchased.

Support of Incell as an optional feature parameters

Table 2-47 details the parameters associated with Support of Incell as an optional feature.
Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter
name. For further details of these and other parameters, refer to Technical Description: BSS
Command Reference (68P02901W23).

Table 2-47 Support of Incell as an optional feature parameters

OMC-R GUI field name/BSS
parameter name
IncellOpt

68P02901W17-T

Description

Values

This parameter indicates

whether the Incell Support
feature functionality is
unrestricted in the BSS
software.
If the IncellOpt flag indicates
that Incell Support is
restricted, attempts to
change Incell Support
specific database parameters
are rejected.

0 - 1
0 - restricted
1 - unrestricted

2-199
Jan 2010

BSP CPU utilization reduction for higher call handling capacity

Chapter 2: Configuring BSS Features

BSP CPU utilization reduction for higher call handling

capacity

Overview
With the memory restriction removed, the CPU efficiency can be improved at the cost of higher
memory usage. A list-based Ater search algorithm is used to allocate resources when a new
call (mobile originated, mobile terminated, external handover from MSC), CIC remap, or Ater
switchover is initiated or for calls with rate change. The Aters are allocated from the top of
the available lists to minimize the search. This ensures that the mean BSP CPU utilization
does not exceed 70%.

2-200

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS User Security Management

BSS User Security Management

Overview
The BSS User Security Management feature provides enhanced user security functionality to a
customer network, by providing the operator with the ability to define individual user names
and passwords for BSS access from the OMC-R, and also locally at the BSS TTY. This provides
information about the users logged into the network through their user name and ID. The user
names and passwords have standard password control features such as complexity checking,
ageing and storage in encrypted format, and are managed from the OMC-R.
A user profile is associated with each user name, which provides controlled access to a
partitioned command set at the BSS. Both standard BSS commands and EMON commands are
partitioned. The OMC-R administrator can create user name and assign a profile to each user
which defines the BSS and EMON command sets that the user can access at the BSS.
Authentication is carried out at the OMC-R when the user first logs in, using a UNIX account
setup by OMCADMIN. When a user uses remote login to access a NE from the OMC-R, the user
is automatically authenticated using their UNIX login. If regions are enabled, the username is
compared to a list of NEs held at the OMC-R to determine if the user has access to the NE.
The OMC authenticates the user account and password for qcomm which are sent from BSS.
Passwords need be to be encrypted in BSS and decrypted in OMC. When the OML link is not in
service, only the field engineer can qcomm on BSS. Users that qcomm from BSS are logged. The
user name, time stamp, commands name and board id are also logged.
This feature supports two types of login:

OMC-R accounts: These are the same UNIX accounts used to login to the OMC-R and
are maintained at the OMC-R. Each account has an access level which defines the set of
commands that can be accessed by the user. There are 4 access levels (numbered 1 to 4),
where level 1 provides read only commands and level 4 allows access to all commands.
Passwords for these accounts are managed through the existing OMC-R administration
procedures. Authentication is performed at the OMC-R. These accounts cannot be used
when the OML is out of service.

Field engineering accounts: These are for use by field engineers when executing
MMI/emon commands locally on the NE equipment. There are 3 instances of these
accounts, each of which has a fixed access level that cannot be changed. These accounts
cannot be used for remote login from the OMC-R. They are intended to be used when the
OML is out of service, or by engineers who do not have OMC-R user accounts. When the
OML is out of service, these are the only accounts that can be used to access the NE. The
passwords for these accounts are managed at the OMC-R, which propagates them to the
network elements. Authentication is performed locally at the NE. When initially deployed,
the BSS has default passwords which are used until it is connected to the OMC-R. The
OMC-R then updates the BSS database with the current passwords and these passwords
are used for all subsequent authentication.

68P02901W17-T

2-201
Jan 2010

BSS User Security Management parameters

Chapter 2: Configuring BSS Features

Table 2-48 Field engineering accounts

Account

Access Level

fieldeng2

level 2

fieldeng3

level 3

fieldeng4

level 4

BSS User Security Management parameters

Table 2-49 details the parameters associated with the feature BSS User Security Management.
The following parameters are OMC only attributes and the BSS name is not applicable. For
further details of these and other parameters, refer to Technical Description: BSS Command
Reference (68P02901W23).

Table 2-49 BSS User Security Management parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

fieldeng_always_enabled

The fieldeng_always_enabled
parameter specifies whether
the field engineering
accounts at the BSS/RXCDR
are used only when the OML
link is down or irrespective
of whether the OML link is
up or down.

0 - 1
Default is 1.
0 - fieldengX accounts
can be used only when
the OML link is down.
1 - fieldengX accounts can
be used whether the OML
link is up or down.

ExpLoginCount

This parameter is a counter

used by CM MIB to keep
track of the number of login
attempts by a normal NE
user after the password
expires.

Minimum - 0
Maximum - 5
Default is 5.

fieldeng2_pass

This parameter is a
computed field, hence
the default value cannot
be stated. This has to be
taken care of by the cutover
or clean install script
while doing the MIB upgrade
which invokes the encryption
algorithm to compute the
value. The maximum value
of 8 characters is to store
the encrypted password in
the MIB.

Minimum - 6 characters
Maximum - 8 characters

Continued

2-202

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS User Security Management parameters

Table 2-49 BSS User Security Management parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

fieldeng3_pass

This parameter is a
computed field, hence
the default value cannot
be stated. This has to be
taken care of by the cutover
or clean install script
while doing the MIB upgrade
which invokes the encryption
algorithm to compute the
value. The maximum value
of 8 characters is to store
the encrypted password in
the MIB.

Minimum - 6 characters
Maximum - 8 characters

fieldeng4_pass

This parameter is a
computed field, hence
the default value cannot
be stated. This has to be
taken care of by the cutover
or clean install script
while doing the MIB upgrade
which invokes the encryption
algorithm to compute the
value. The maximum value
of 8 characters is to store
the encrypted password in
the MIB.

Minimum - 6 characters
Maximum - 8 characters

ne_banner

This parameter specifies the

NE usage policy for users
and is provided by the NE to
the user at the time of lmt
login with both fieldengX
account and normal user
account. The default
message is as follows:
This network element is
protected by the Motorola
BSS security feature.
Access by unauthorized
persons is prohibited and
all users are verified.
For further information,
contact the OMC-R systems
administrator.

Minimum - 1 character
Maximum - 255 characters

Continued

68P02901W17-T

2-203
Jan 2010

Logging in to the BSS through a local maintenance terminal using the login command Chapter 2: Configuring BSS Features

Table 2-49 BSS User Security Management parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

FieldEng2Chg

This parameter is used to

specify the date when the
fieldeng2 password was
changed. The range and
default values of this field
cannot be specified as this is
inserted by the OMC-R when
the fieldeng2 passwords
are changed. Also, this
parameter is not visible on
the GUI.

FieldEng3Chg

This parameter is used to

specify the date when the
fieldeng3 password was
changed. The range and
default values of this field
cannot be specified as this is
inserted by the OMC-R when
the fieldeng3 passwords
are changed. Also, this
parameter is not visible on
the GUI.

FieldEng4Chg

This parameter is used to

specify the date when the
fieldeng4 password was
changed. The range and
default values of this field
cannot be specified as this is
inserted by the OMC-R when
the fieldeng4 passwords
are changed. Also, this
parameter is not visible on
the GUI.

NEAccessLevel

This parameter specifies the

NE command access level
for the user.

Values

Minimum - 1
Maximum - 4
Default is 4 (For omcadmin
user and non omcadmin
users)

Logging in to the BSS through a local maintenance terminal

using the login command
The login command is used when logging in to a BSS through a local maintenance terminal
(for example: a laptop connected to the master GPROC). It is used to authenticate the user and
assign the user the appropriate command access level.

2-204

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

verify_field_pass and .field_pass utilities

This command requires the user to login using either a UNIX account (the same account used to
login to the OMC-R) or a field engineer account (fieldeng2, fieldeng3 or fieldeng4). The login
requested depends on the status of the OML and the setting of the fieldeng_always_enabled
parameter. By default it is possible to login using either account.

Example
MMI-RAM 0115 -> login
[BANNER TEXT]
Please input your UNIX account or Field Engineer account information
Login:

user1

Password:

********

COMMAND ACCEPTED
A user is provided three opportunities to enter the correct username and password. If the user
enters incorrect information thrice in succession, the user is blocked from logging in for 10
minutes. This block applies only to the board to which the user is currently connected.

verify_field_pass and .field_pass utilities

The BSS user security feature uses two OMC-R scripts to check field engineer accounts.

The utility verify_field_pass authenticates the field engineer account passwords. This utility
accepts the field engineer user name and password, and compares this with the encrypted
field engineer user stored in MIB. This utility has execute permission for all users.

The utility .field_pass displays all the field engineering passwords in plain text. It has
execute permission only for the omcadmin user and is stored as a hidden file.

Both these utilities are located in the /usr/omc/current/bin directory on the OMC-R.

68P02901W17-T

2-205
Jan 2010

Setting fieldeng_always_enabled parameter

Chapter 2: Configuring BSS Features

Setting fieldeng_always_enabled parameter

Figure 2-4 BSS Detailed View

The BSS Detailed View and RXCDR Detailed View display the BSS parameter
fieldeng_always_enabled.
The CMMIB supports the fieldeng_always_enabled parameter for both BSS and RXCDR class
which is used to specify whether the fieldengX accounts at the NE (BSS / RXCDR) are used
only when the OML link is down or under all the scenarios, that is, irrespective of whether
the OML link is up or down
The fielding_always_enabled parameter is displayed on OMC-R BSS/RXCDR DV with the name
Field Engineer Always Enabled

2-206

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Password management and banner text management

Procedure 2-4 Setting fieldeng_always_enabled parameter

Set the parameter fieldeng_always_enabled to 0 (FALSE) to enable the field

engineer user accounts to be used only when the OML link is down.

Set the parameter fieldeng_always_enabled to 1 (TRUE) to enable the field

engineer user accounts to be used when the OML link is up or down.

Password management and banner text management

NOTE
The Admin Options window is updated with two new options NE Field Engineer
Password Management and NE Banner Text Management. Figure 2-5 displays
the Admin Options window.

68P02901W17-T

2-207
Jan 2010

Password management and banner text management

Figure 2-5

Chapter 2: Configuring BSS Features

Admin options window

Setting the field engineering password

The NE Field Engineer Password Management window is used to change the Field Engineer
password for all the NEs connected to the OMC-R.

NOTE
The omcadmin user and users with omcadmin privileges can invoke the NE Field
Engineer Password Management window.

Procedure 2-5 Setting the field engineering password

Login to the OMC-R GUI server as omcadmin user.

Click the Admin Option on the main OMC-R GUI front panel. The Admin
Options window is displayed, as shown in Figure 2-5.
Continued

2-208

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Password management and banner text management

Procedure 2-5 Setting the field engineering password (Continued)

3

Click the option NE Field Engineering Password Management to display

the NE Field Engineering Password Management window.

Select Edit Edit from the menu.

Click the Checkboxes and enter the values for the following parameters:
Fieldeng2 Password, Fieldeng2 Password Confirm
Fieldeng3 Password, Fieldeng3 Password Confirm
Fieldeng4 Password, Fieldeng4 Password Confirm.

Select File Propagate to propagate all fieldengX passwords across the

network.

NOTE
This option is grayed out when the NE Field Engineer Password
Management window is in the Monitor mode.

Select Propagate to Failed to propagate the field engineering passwords to

all those NEs to which the password propagation has failed in the previous
attempt. This option can be enabled only when the NE Field Engineer
Password Management window is in the Monitor mode.
Run Propagate to Failed in the Monitor mode if any of the previous
propagation attempts have failed.
7

Select File Close to close the NE Field Engineer Password Management

window without propagating the changes to fieldengX passwords across the
network. This option is enabled both in the Monitor and Edit state of the
window. The following warning dialog is displayed if the user tries to close
the window after editing but without propagating the changes: There have
been changes since you last saved. Exit without saving changes?

Select OK and close the NE Field Engineer Password Management window.

Select Xterm from the OMC-R GUI to launch an Xterm.

10

At the Xterm command prompt, enter the following command:

/usr/omc/current/bin/verify_field_pass fieldeng2
Enter Password: ***********

11

Enter the password for the Fieldeng2 user which was entered in step 5.

12

Verify that the authentication is successful, confirming that the password

was updated successfully in the MIB.

13

Repeat step 10 to step 12 for each field engineering account.

14

At the Xterm command prompt, enter the following command:

/usr/omc/current/bin/.field_pass

15

Enter the omcadmin password when prompted. The tool display the field
engineering passwords stored at the MIB. Verify that they match the
passwords entered in step 5.

NOTE
Performing step 10 to step 15 ensures that the passwords are updated at the NE.

68P02901W17-T

2-209
Jan 2010

Password management and banner text management

Chapter 2: Configuring BSS Features

Figure 2-6 NE Field Engineer Password Management status dialog

NE Banner Text Management Window

When the user logs into NE, NE provides a banner text containing a brief outline of the NE
usage policy and legal matters that are relevant to NE usage. The NE banner text can be
customized at the OMC-R.
The NE Banner Text Management GUI is used to update the Banner Text, and to synchronize
with all the NEs connected to the OMC-R.

NOTE
The omcadmin user and users with omcadmin privileges can invoke the NE Banner
Text Management window.

Procedure 2-6 NE Banner Text Management

Login into the OMC-R system processor as omcadmin user on the GUI server.

Click the Admin Option on the main OMC-R GUI front panel.
Continued

2-210

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Password management and banner text management

Procedure 2-6 NE Banner Text Management (Continued)

3

In the Admin Options window, click the option NE Banner Text Management
and verify that the following text is displayed in the NE Banner Text
Management Window: This Network Element is protected by the Motorola
BSS Security Feature. Access by unauthorized persons is prohibited and all
users will be verified. For further information contact the OMC-R Systems
Administrator.

Select Edit Edit and enter the text for the NE_banner parameter.

Select File Propagate to propagate the banner text across the network
and to store the banner text in the MIB.

NOTE
This option is grayed out when the NE Banner Text Management
window is in the Monitor mode and it is enabled in the Edit mode.

Select Propagate to Failed to propagate the currently set banner text to all
those NEs to which the Banner Text propagation has failed in the previous
attempt. This option is enabled only when the NE Banner Text Management
window is in the Monitor mode.
Run Propagate to Failed in the Monitor mode if any of the previous
propagation attempts have failed.

68P02901W17-T

Select File Close. A warning dialog is displayed if the user tries to close
the window after editing but without propagating the changes: There have
been changes since you last saved. Exit without saving changes?

Select OK and close the NE banner text management window.

Login to the BSS/XCDR locally from a laptop or through the qcomm

application from the qcomm server as a normal user or field engineer and
verify that the displayed text is the same text as in step 3.

2-211
Jan 2010

Quality of Service Phase II

Chapter 2: Configuring BSS Features

Quality of Service Phase II

Overview
Quality of Service (QoS) architecture aims at providing a framework for differentiation of
services and users for GPRS/EGPRS and UMTS. The key components of phase 2 of QoS
implementation are as follows:

Add support for Streaming Traffic class

Max bit-rate enforcement as per the QoS Profile

Capacity is based on a less conservative budget

Support for Streaming Traffic Class allows the operator to specify a service requiring constraints
on delay and jitter as well as minimum bit rate. Support for PFCs requesting streaming traffic
class can be enabled/disabled using the streaming_enabled BSS parameter. If support for
streaming traffic class is disabled, BSS tries to admit the streaming traffic classes as one of the
matching interactive traffic classes (determined based on the MTBR settings).
Guaranteed Bit Rate as per the 3GPP specification is defined as the guaranteed number of bits
delivered at a SAP within a period of time (provided that there is data to deliver), divided by the
duration of the period. For the GPRS RAN, the guaranteed bit rate is defined as the bit rate
at the LLC layer. The Guaranteed Bit Rate for each PFC is an extension of MTBR (minimum
throughput budget requirement) associated with each PFC. The MTBR is measured as the
raw air throughput at the RLC/MAC layer whereas the GBR measurements exclude any RLC
retransmissions.
Transfer Delay (definition as per 23.107) indicates maximum delay for 95th percentile of the
distribution of delay for all delivered SDUs during the lifetime of a bearer service, where delay
for an SDU is defined as the time from a request to transfer an SDU at one SAP to its delivery
at the other SAP. Transfer delay of an arbitrary SDU is not meaningful for a bursty source
(applicable only to real-time traffic classes streaming/conversational). In addition, the transfer
delay for Radio Access Bearer may be smaller than the overall requested transfer delay, as
transport through the core network uses a part of the acceptable delay. Transfer delay as all
other attributes in the Aggregate BSS QoS Profile is negotiable.
Maximum Bit Rate enforcement allows the BSS to throttle the throughput of user to the max bit rate stated in the QoS parameters (ABQP) even if there is a capacity to provide the user a higher
throughput. The key requirement here is to modify the scheduling algorithms to enforce Max-bit
rate as per the negotiated QoS profile. The main purpose of maximum bit rate enforcement from
an operators perspective is to limit the delivered bit rate to applications or external networks
and to allow maximum required/permitted bit rate to be defined for applications able to operate
with different rates. The Maximum bit rate applies to all traffic classes.

2-212

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Quality of Service Phase II parameters

Quality of Service Phase II parameters

Table 2-50 details the Quality of Service Phase II parameters. Unless stated otherwise,
the OMC-R parameter name is usually the same as the BSS parameter name. For further
details of these and other parameters, see Technical Description: BSS Command Reference
(68P02901W23).

Table 2-50 Quality of Service Phase II parameters

OMC-R GUI field name/BSS
parameter name
streaming_enabled

Description

Values

The parameter streaming_enabled

provides streaming support per BSS
when enabled and if the operator
disables the parameter, then
the support for all streaming
traffic classes, all existing
streaming/conversational PFCs
are deleted by the BSS.
Future streaming/conversational
users are downgraded and mapped
to an appropriate interactive traffic
class using rules described in QoS.

0 - 1
Default is 0
0 - Disabled
1 - Enabled

NOTE
This attribute can only be
modified if Qos Phase II
is enabled/unrestricted at
the OMC.
Continued

68P02901W17-T

2-213
Jan 2010

Quality of Service Phase II parameters

Chapter 2: Configuring BSS Features

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
qos_mbr_enabled

Description

Values

The parameter qos_mbr_enabled

enables or disables support of
Max Bit Rate or Peak Bit Rate
enforcement on a per BSS basis.
When this parameter is enabled, the
throughput of all the subscribers in
this BSS is limited by the Maximum
Bit Rate defined in HLR.

0 - 1
Default is 0
0 - Disabled
1 - Enabled

NOTE
This attribute can only be
modified if Qos Phase II
is enabled/unrestricted at
the OMC.
stream_downgrade_
enabled

The parameter
stream_downgrade_enabled enables
or disables the downgrading of
GBR and Transfer Delay of an
admitted PFC during future retention
procedures to a lower value than
was initially committed. Any
changes to this parameter only affect
future retention procedures. This
parameter controls the negotiation
of GBR, TD, MaxSDUsize, besides
RT-nRT downgrade.

0 - 1
Default is 1
0 - Not allowed to
set the GBR to a lower
value than committed
1 - Allowed to set the
GBR to a lower value
than committed

NOTE
This attribute can only be
modified if Qos Phase II
is enabled/unrestricted at
the OMC.
thp_stream_weight

The parameter thp_stream_weight

specifies the THP weight of the
streaming traffic class.
The thp_stream_weight is restricted
by the QoS Phase 2 feature. When
streaming_enabled parameter is
equal to 1, this attribute cannot be
changed.

10 - 40
Default is 40
All values in the range
of 10 - 40 are valid,
the higher the value,
the more precedence
it is given.

Continued

2-214

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Quality of Service Phase II parameters

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
mtbr_downgrade_enabled

Description

Values

The parameter
mtbr_downgrade_enabled enables
or disables downgrading the MTBR
of an admitted PFC during future
retention procedures to a lower value
than was initially committed.

0 - 1
Default is 1
0 - Not allowed to set
the MTBR to a lower
value than committed
1 - Allowed to set the
MTBR to a lower value
than committed.

NOTE
This attribute can only
be modified if Qos is
enabled/unrestricted at
the OMC.
pfm_sig_enabled

The parameter pfm_sig_enabled

enables or disables support of PFC
modification signaling to SGSN when
there is downgrade or upgrade for
non-real time PFC on a per BSS basis.

NOTE
This attribute can only
be modified if Qos is
enabled/unrestricted at
the OMC.

0 - 1
Default is 1
0 - No PFC modification
message sent to SGSN
when there is an
upgrade or downgrade
for non real-time PFC.
1 - PFC modification
message is sent to
SGSN when there is an
upgrade or downgrade
for non real-time PFC.
Continued

68P02901W17-T

2-215
Jan 2010

Quality of Service Phase II parameters

Chapter 2: Configuring BSS Features

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
arp_streaming_1

Description

Values

The parameter arp_streaming_1

specifies the Allocation and Retention
Priority (ARP) value of streaming
traffic class, precedence class 1. The
OMC-R interprets the decimal value
into decimal value of four parts: qa,
priority level/arp value, pci, and pvi
according to ARP IE structure. This
ARP information is used during the
admission control and retention of
PFC when they cannot be derived
from SGSN.
The value of this attribute is
converted to binary and the bits are
interpreted as follows to obtain the
pci, pvi and the priority level/arp
value:
8 - spare
7 - pci
6,5,4,3 - priority level
2 - qa
1 - pvi
The value of qa bit is not used in
GSR10.

4 - 123
Default is 68 (pci - 1,
priority level - 1, pvi - 0)
All values in the range
of 4 - 123 except 60,
61, 62, 63, 64, 65, 66
and 67 are valid.

NOTE
This item can only be
modified if the QoS Phase
2 feature is unrestricted.
The priority level value of
arp_streaming_1 must be less than
or equal to those of arp_streaming_2
and arp_streaming_3.
The OMC-R supports a message
string in the status bar of the BSS DV
when attribute arp_streaming_1, is
modified.
The message displays the pci, pvi
and priority level based on the value
entered in the BSS DV.
Continued

2-216

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Quality of Service Phase II parameters

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
arp_streaming_2

Description

Values

The parameter arp_streaming_2

specifies the allocation and retention
Priority (ARP) value of streaming
traffic class, precedence class 2.
The OMC-R interprets the decimal
value into a decimal value of four
parts: qa, priority level/arp value,
pci, and pvi according to ARP IE
structure. This ARP information is
used during the admission control
and retention of PFC when they
cannot be derived from SGSN. The
value of qa bit is not used in GSR10.

4 - 123
Default is 73 (pci - 1,
priority level - 7, pvi - 0)
All values in the range
of 4 - 123 except 60,
61, 62, 63, 64, 65, 66
and 67 are valid.

NOTE
This item can only be
modified if the QoS Phase
2 feature is unrestricted.

The priority level value of

arp_streaming_2 must be less than
or equal to that of arp_streaming_3
and greater than or equal to that of
arp_streaming_1.
The OMC-R supports a message
string in the status bar of the BSS DV
when attribute arp_streaming_2, is
modified.
The message displays the pci, pvi,
and priority level based on the value
entered in the BSS DV.
Continued

68P02901W17-T

2-217
Jan 2010

Quality of Service Phase II parameters

Chapter 2: Configuring BSS Features

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
arp_streaming_3

Description

Values

The parameter arp_streaming_3

specifies the allocation and retention
Priority (ARP) value of streaming
traffic class, precedence class 3.
The OMC-R interprets the decimal
value into decimal value of four parts:
qa, priority level/arp value, pci and
pvi according to ARP IE structure.
This ARP information is used during
the admission control and retention
of PFC when they cannot be derived
from SGSN.

4 - 123
Default is 77 (pci
- 0, priority level
- 14, pvi - 1)
All values in the range
of 4 - 123 except 60,
61, 62, 63, 64, 65, 66
and 67 are valid.

NOTE
This item can only be
modified if the QoS Phase
2 feature is unrestricted.
The priority level value of
arp_streaming_3 must be
greater than or equal to
those of arp_streaming_1 and
arp_streaming_2.
The OMC-R supports a message
string in the status bar of the BSS DV
when the attribute arp_streaming_3,
is modified.
The message displays the pci, pvi
and priority level based on the value
entered in the BSS DV.
Continued

2-218

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Quality of Service Phase II parameters

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
arp_i_be_1

Description

Values

The parameter arp_i_be_1 specifies

the Allocation and Retention Priority
(ARP) value of Interactive or Best
Effort traffic class, precedence class
1.
The OMC-R interprets the decimal
value into a decimal value of four
parts: qa, priority level/arp value,
pci, and pvi according to ARP IE
structure. This ARP information is
used during the admission control
and retention of PFC when they
cannot be derived from SGSN.

4 - 123
Default is 93 (pci - 1,
priority level - 1, pvi - 0)
All values in the range
of 4 - 123 except 60,
61, 62, 63, 64, 65, 66
and 67 are valid.

NOTE
This item can only be
modified if the QoS feature
is unrestricted.
The priority level value of arp_i_be_1
must be less than or equal to those of
arp_i_be_2 and arp_i_be_3.
The OMC-R supports a message
string in the status bar of the BSS
DV when the attribute arp_i_be_1, is
modified.
The message displays the pci, pvi,
and priority level based on the value
entered in the BSS DV.
Continued

68P02901W17-T

2-219
Jan 2010

Quality of Service Phase II parameters

Chapter 2: Configuring BSS Features

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
arp_i_be_2

Description

Values

The parameter arp_i_be_2 specifies

the Allocation and Retention Priority
(ARP) value of Interactive or Best
Effort traffic class, precedence class
2.
The OMC-R interprets the decimal
value into a decimal value of four
parts: qa, priority level/arp value,
pci and pvi according to ARP IE
structure. This ARP information is
used during the admission control
and retention of PFC when they
cannot be derived from SGSN.

4 - 123
Default is 97 (pci - 1,
priority level - 7, pvi - 1)
All values in the range
of 4 - 123 except 60,
61, 62, 63, 64, 65, 66
and 67 are valid.

NOTE
This item can only be
modified if the QoS feature
is unrestricted.
The priority level value of arp_i_be_2
must be less than or equal to that of
arp_i_be_3 and greater than or equal
to that of arp_i_be_1.
The OMC-R supports a message
string in the status bar of the BSS
DV when attribute arp_i_be_2, is
modified.
The message displays the pci, pvi
and priority level based on the value
entered in the BSS DV.
Continued

2-220

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Quality of Service Phase II parameters

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
arp_i_be_3

Description

Values

The parameter arp_i_be_3 specifies

the Allocation and Retention Priority
(ARP) value of Interactive or Best
Effort traffic class, precedence class
3.
The OMC-R interprets the decimal
value into a decimal value of four
parts: qa, priority level/arp value,
pci and pvi according to ARP IE
structure. This ARP information is
used during the admission control
and retention of PFC when they
cannot be derived from SGSN.

4 - 123
Default is 101
(pci - 0, priority
level - 14, pvi - 1)
All values in the range
of 4 - 123 except 60,
61, 62, 63, 64, 65, 66
and 67 are valid.

NOTE
This item can only be
modified if the QoS feature
is unrestricted.
The priority level value of arp_i_be_3
must be greater than or equal to
those of arp_i_be_1 and arp_i_be_2.
The OMC-R supports a message
string in the status bar of the BSS
DV when attribute arp_i_be_3, is
modified.
The message displays the pci, pvi
and priority level based on the value
entered in the BSS DV.
Continued

68P02901W17-T

2-221
Jan 2010

Quality of Service Phase II parameters

Chapter 2: Configuring BSS Features

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
arp_bg_1

Description

Values

The parameter arp_bg_1 specifies

the Allocation and Retention Priority
(ARP) value of Background traffic
class, precedence class 1.
The OMC-R interprets the decimal
value into decimal value of four parts:
qa, priority level/arp value, pci and
pvi according to ARP IE structure.
This ARP information is used during
the admission control and retention
of PFC when they cannot be derived
from SGSN.

4 - 123
Default is 49 (pci - 1,
priority level - 1, pvi - 0)
All values in the range
of 4 - 123 except 60,
61, 62, 63, 64, 65, 66
and 67 are valid.

NOTE
This item can only be
modified if the QoS feature
is unrestricted.
The priority level value of arp_bg_1
must be less than or equal to those of
arp_bg_2 and arp_bg_3.
The OMC-R supports a message
string in the status bar of the BSS DV
when attribute arp_bg_1, is modified.
The message displays the pci, pvi
and priority level based on the value
entered in the BSS DV.
Continued

2-222

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Quality of Service Phase II parameters

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
arp_bg_2

Description

Values

The parameter arp_bg_2 specifies

the Allocation and Retention Priority
(ARP) value of Background class,
precedence class 2.
The OMC-R interprets the decimal
value into a decimal value of four
parts: qa, priority level/arp value,
pci and pvi according to ARP IE
structure. This ARP information is
used during the admission control
and retention of PFC when they
cannot be derived from SGSN.

4 - 123
Default is 53 (pci - 1,
priority level - 7, pvi - 1)
All values in the range
of 4 - 123 except 60,
61, 62, 63, 64, 65, 66
and 67 are valid.

NOTE
This item can only be
modified if the QoS feature
is unrestricted.
The priority level value of arp_bg_2
must be less than or equal to that of
arp_bg_3 and greater than or equal
to that of arp_bg_1.
The OMC-R supports a message
string in the status bar of the BSS DV
when attribute arp_bg_2, is modified.
The message displays the pci, pvi
and priority level based on the value
entered in the BSS DV.
Continued

68P02901W17-T

2-223
Jan 2010

Quality of Service Phase II parameters

Chapter 2: Configuring BSS Features

Table 2-50 Quality of Service Phase II parameters (Continued)

OMC-R GUI field name/BSS
parameter name
arp_bg_3

Description

Values

The parameter arp_bg_3 specifies

the Allocation and Retention Priority
(ARP) value of Background traffic
class, precedence class 3.
The OMC-R interprets the decimal
value into decimal value of four parts:
qa, priority level/arp value, pci and
pvi according to ARP IE structure.
This ARP information is used during
the admission control and retention
of PFC when they cannot be derived
from SGSN.

4 - 123
Default is 57 (pci
- 0, priority level
- 14, pvi - 1)
All values in the range
of 4 - 123 except 60,
61, 62, 63, 64, 65, 66
and 67 are valid.

NOTE
This item can only be
modified if the QoS feature
is unrestricted.
The priority level value of arp_bg_3
must be greater than or equal to
those of arp_bg_1 and arp_bg_2.
The OMC-R supports a message
string in the status bar of the BSS DV
when attribute arp_bg_3, is modified.
The message displays the pci, pvi
and priority level based on the value
entered in the BSS DV.

2-224

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

CTU2-D

CTU2-D

Description
CTU2-D radios can support both SD and DD EDGE architectures, in addition to the various
modes supported by CTU2 radios. According to the CTU2, Carrier A/B definitions and
nomenclature also apply to CTU2-D. The following are the different Edge modes that the
CTU2-D radio supports:

CTU2D SD
This mode is identical in operation to the existing CTU2 SD and is only included for
reference.

CTU2D PWR
This mode is also known as ITS Mode whereby the CTU2 and CTU2D operations are
identical. Of the two carriers, if the TS on carrier A is supporting an EDGE TS, then the
corresponding TS on carrier B is blanked, that is, it does not support anything. Carrier B
TS is capable of supporting only TCH or GPRS PDs while the corresponding TS on carrier A
does not have an EDGE TS. The maximum output power of both carriers whether in GMSK
or 8PSK mode is 20 W* as shown in Figure 2-7.

Figure 2-7

CTU2D PWR mode

CTU2D CAP
Of the two carriers, carrier A is fully EDGE-capable, while carrier B supports GPRS/TCH.
TS blanking is not required. The maximum output power of carrier A in 8PSK mode is
10 W* and GMSK mode is 20 W*. The maximum output power carrier B (GMSK only)
is always 20 W* as shown in Figure 2-8.

68P02901W17-T

2-225
Jan 2010

CTU2-D dependencies

Chapter 2: Configuring BSS Features

Figure 2-8 CTU2D CAP mode

CTU2D ASYM
Of the two carriers, carrier A is fully EDGE-capable, while carrier B supports EDGE on
the DL and GMSK (EDGE) on the UL. The maximum output power of carrier A in 8PSK
mode is 10 W* and GMSK mode is 20 W*. The maximum output power of carrier B in
GMSK mode is 20 W*, as shown in Figure 2-9.

Figure 2-9

CTU2D ASYM mode

NOTE
* The output powers listed are for 900 MHz frequency. For all other frequencies, the
output power may vary.
The capacity of the overall BSS remains unchanged. However, due to the elimination of timeslot
blanking in DD mode, the capacity of the radio in DD CAP and ASYM mode increases.

CTU2-D dependencies

2-226

CTU2-D is supported on Horizon II macro, Horizon II mini, and Horizon II micro sites
only. When the master cabinets are Horizon II macro and Horizon II mini, the extension
Horizon II cabinets support CTU2-D, M-Cell and Horizon extension cabinets do not support
CTU2-D and remain OOS.

The CTU2-D capacity feature requires EGPRS to be unrestricted.

The CTU2-D asymmetric operation requires both EGPRS and capacity feature to be
unrestricted.

For the asymmetric mode to be operational, asym_edge_enabled should be enabled and

dri_density should be set to Capacity mode.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

CTU2-D parameters

CTU2-D parameters
Table 2-51 details the parameters associated with the CTU2-D feature. Unless stated otherwise,
the OMC-R parameter name is usually the same as the BSS parameter name. For further details
of these and other parameters, refer to Technical Description: BSS Command Reference
(68P02901W23).

Table 2-51 CTU2-D parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

ctu2dcapOpt

The ctu2dcapOpt parameter

indicates whether the CTU2-D
Capacity feature is restricted
or unrestricted in the BSS.
The CTU2-D capacity feature
requires the EGPRS feature to
be unrestricted.

0 - 1
0 - Disabled
1 - Enabled

ctu2dasymOpt

The ctu2dasymOpt parameter

indicates whether the CTU2-D
Asymmetric EDGE feature
is restricted/unrestricted in
the BSS. The Asymmetric
EDGE feature requires the
EGPRS feature and the
CTU2-D Capacity feature to
be unrestricted.

0 - 1
0 - Disabled
1 - Enabled

The asym_edge_enabled
parameter enables or disables
the Asymmetric EDGE feature
available on the CTU2-D
hardware on a per-SITE basis.
Changing this parameter
requires the site to be reset
manually for the change to
take effect. This is a type
1 parameter. The OMC-R
displays a message to the
operator to reset the SITE.
This attribute can only be
enabled at sites where the
master SITE cabinet is a
member of the Horizon II
family (Horizon II macro,
Horizon II mini and Horizon II
micro).

0 to 1
Default is 0.
0 - Asymmetric
EDGE is disabled.
1 - Asymmetric EDGE
is enabled.

SITE parameter
asym_edge_enabled

68P02901W17-T

2-227
Jan 2010

Interaction with other features

Chapter 2: Configuring BSS Features

Interaction with other features

This feature interacts with the following:

2-228

Quality of Service Phase II

CTU2 Debug and Diagnostics

Improved Timeslot Sharing

VersaTRAU

Four branch Diversity

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell OOS Timer Enhancement

Cell OOS Timer Enhancement

Description
This feature provides an operator configurable delay to postpone the system information update
message for SIs 1, 2, 2bis, 3 and 4 to the MS when the BSC is undergoing reset during master
BSP failover (BRM feature). This delays the MS cell reselection procedure during global reset.
This feature is designed to extend the amount of time that the mobile remains on the network
which is undergoing a reset procedure. This enables operators to maintain roaming subscribers
and reduce revenue loss.
Call processing at the BSS is responsible for the delay of system information update message to
the mobile while the BSS is undergoing reset. OM is responsible for providing the mechanism
to configure the value of the delay.

Cell OOS Timer Enhancement parameters

Table 2-52 details the parameters associated with Cell OOS Timer Enhancement. Unless stated
otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For
further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).

Table 2-52 Cell OOS Timer Enhancement parameters

OMC-R GUI field
name/BSS parameter
name
cell_barred_delay

68P02901W17-T

Description

Values

The BSS parameter

cell_barred_delay specifies
how long the BSS delays sending
SystemInformationUpdate
message to the MS during the
global reset procedure.
This element can be updated
both in or out of sysgen mode.

0 - 180 seconds.
Default is 0.

2-229
Jan 2010

TDM Availability Enhancements

Chapter 2: Configuring BSS Features

TDM Availability Enhancements

Overview
This feature increases the availability of the system by enhancing the existing fault recovery
and detection mechanism of the TDM buses in the BSC. These enhancements also apply to
the RXCDR.
Previously, operator intervention was required to initiate certain types of TDM swap which
resulted in a long service outage. Modification to the hardware fault management (HWFM) of
the KSW/DSW2 Expansion matrix was carried out to ensure that the TDM highways are handled
properly. Currently, upon detecting a fault in the active Expansion Matrix with a Redundant
Expansion Matrix equipped, the fault manager maintains call processing but does not initiate
a TDM swap. The system waits for the OMC to command a swap to the redundant TDM bus
and associated expansion matrix.
There are two parts to the modified behavior. The first part causes the system to automatically
swap to the redundant TDM highway upon detection of a fault. The second allows for an
automatic daily swap to the redundant highway.

TDM Availability Enhancements parameters

Table 2-53 details the parameters associated with TDM Availability Enhancements. Unless
stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name.
For further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).

Table 2-53 TDM Availability Enhancements parameters

OMC-R GUI field name/BSS
parameter name
tdm_switch

2-230

Description

Values

A switch is added to the OMC in

order to control the TDM Availability
Enhancements feature. When
the switch is open, the feature
is activated. When the switch is
closed, the feature is disabled. The
switch is denoted by the parameter
tdm_switch. The definition of the
values is based on the states of the
switch.

0 - Close
1 - Open
Default is 0.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

TD-SCDMA and GSM interworking

TD-SCDMA and GSM interworking

Overview
This feature supports intersystem cell reselection between TD-SCDMA and GSM/GPRS in order
that:

Subscribers do not lose service when they reach the edge of TD-SCDMA coverage.

Subscribers gain the benefits of the more advanced TD-SCDMA system when they enter
its coverage area.

This feature performs the following functions:

Supports GSM/GPRS to TD-SCDMA cell reselection in circuit-switched idle mode and

packet idle mode by broadcasting TD-SCDMA neighbor list and the corresponding 3G
measurement parameters in SI2ter, SI2Quater.

Supports GSM/GPRS to TD-SCDMA cell reselection in packet transfer mode.

Supports TD-SCDMA to GSM/GPRS cell reselection.

Supports TD-SCDMA to GSM handover in circuit-switched dedicated mode.

TD-SCDMA and GSM interworking dependencies

This feature is supported on M-Cell, Horizon, and Horizon II platforms. Incell is not supported.
The TD-SCDMA and GSM interworking feature requires:

Multi-RAT mobile stations, which are capable of accessing the Core Network (CN) from
a UMTS TD-SCDMA coverage area and a GSM coverage area. The MS must be capable
of operating in either GSM or UMTS TD-SCDMA cells, including execution of procedures
such as PLMN selection, cell reselection, measurements in idle mode and dedicated mode,
and so on.

A UMTS network including 2G/3G compatible MSC.

Existing 2G CN nodes must be able to interact with the 3G CN nodes through MAP
procedures defined on the E-interface between a 3G CN node and 2G CN node.

TD-SCDMA and GSM interworking parameters

Table 2-54 details the parameters associated with TD-SCDMA and GSM interworking. Unless
stated otherwise, the OMC-R parameter name is usually same as the BSS parameter name.
For further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).

68P02901W17-T

2-231
Jan 2010

TD-SCDMA and GSM interworking parameters

Chapter 2: Configuring BSS Features

Table 2-54 TD-SCDMA and GSM interworking parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

TD-SCDMA Inter-working
Feature
tdOpt

Displayed in the Optional Features

grouping of the BSS Detailed View
Form.
This parameter indicates whether
the TD-SCDMA interworking feature
is restricted or unrestricted in the
BSS. When tdOpt is restricted,
attempts to add TD-SCDMA neighbor
cell and modify/display TD-SCDMA
measurement parameters are
rejected.

0 - 1
0 - Restricted
1 - Unrestricted

TD-SCDMA Inter-working
Enabled
td_enabled

Displayed in the General grouping of

the BSS Detailed View Form.
This parameter allows the user to
enable or disable the TD-SCDMA
inter-working feature at the BSS
level. When the TD-SCDMA
inter-working feature (tdOpt) is
restricted, this parameter cannot
be modified. When InterRATOpt
or EnhancedInterRatOpt feature is
unrestricted, this parameter cannot
be modified from 0 to 1. If tdOpt is
unrestricted, this parameter is sent
across the OMC-BSS interface.
When the parameter is not 1, the user
cannot add TD-SCDMA Neighbor.

0 - 1
0 - Off
1 - On
Default is 0.

The offset for cell

reselection to TD-SCDMA
tdd_qoffset

Displayed in the General grouping of

the CELL Detailed View Form.
This parameter is used in the cell
reselection algorithm followed by
the MS for the UMTS TDD neighbor
cell. When tdOpt is restricted, this
parameter cannot be modified. If
tdOpt is unrestricted, this parameter
is sent across the OMC_BSS interface.
This parameter applies an offset to
RLA_C for cell reselection to access
the TD-SCDMA mode. This is a
configurable parameter.

0 - 15 where
0 = -
1 = - 28 dB
2 = - 24 dB
......
15 = 28 dB
Default is 8.

TD-SCDMA ARFCN
tdd_arfcn

This parameter indicates the

TD-SCDMA frequency. This is a
Read-Write parameter of the UTRAN
Neighbor Cell.
When tdOpt is restricted, this
parameter cannot be modified.

10054 - 10121

Continued

2-232

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

TD-SCDMA and GSM interworking parameters

Table 2-54 TD-SCDMA and GSM interworking parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Values

TD-SCDMA Cell
Parameter
tdd_cell_param

This parameter indicates the

TD-SCDMA cell parameter. This is a
Read-Write parameter of the UTRAN
Neighbor Cell.
When tdOpt is restricted, this
parameter cannot be modified.

0 to 127

TD-SCDMA Time
Switched Transmit
Diversity Mode
tdd_tstd_mode

This parameter indicates the

TD-SCDMA Time Switched Transmit
Diversity mode. This is a Read-Write
parameter of the UTRAN Neighbor
Cell.
When tdOpt is restricted, this
parameter cannot be modified.

0 to 1
0 - Disabled
1 - Enabled
Default is 0.

TD-SCDMA Space Code

Transmit Diversity Mode
tdd_sctd_mode

This parameter indicates the

TD-SCDMA cell diversity capability
(Space Code Transmit Diversity).
This is a Read-Write parameter of the
UTRAN Neighbor Cell. When tdOpt
is restricted, this parameter cannot
be modified.

0 to 1
0 - Disabled
1 - Enabled
Default is 0.

BCCH RF Signal Level

Threshold
qsearch_i

Refer to Inter-RAT Handover and

Enhanced Inter-RAT Handover
parameters on page 2-96 for further
details.

Use BCCH RF Signal

Level Threshold
qsearch_c_initial

Refer to Inter-RAT Handover and

Enhanced Inter-RAT Handover
parameters on page 2-96 for further
details.

68P02901W17-T

2-233
Jan 2010

Extended Uplink TBF (Temporary Block Flow)

Chapter 2: Configuring BSS Features

Extended Uplink TBF (Temporary Block Flow)

Overview
The Extended Uplink TBF feature enhances uplink/downlink data performance by minimizing
the interruptions of uplink data flow in GPRS/EGPRS networks due to frequent release and
establishment of uplink TBF. The uplink TBF is maintained during temporary inactive periods,
when the mobile station has no RLC information to send. The network determines the release of
the uplink TBF. The network continues to allocate USFs for the mobile station during the period
of inactivity. The mobile station sends Uplink Dummy Control Blocks if indicated or RLC data
blocks when new RLC data blocks become available.
This feature requires the GPRS Feature to be unrestricted.

Extended Uplink TBF (Temporary Block Flow) parameters

Table 2-55 details the parameters associated with the Extended Uplink TBF (Temporary Block
Flow) feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the
BSS parameter name. For further details of these and other parameters, refer to Technical
Description: BSS Command Reference (68P02901W23).

Table 2-55 Extended Uplink TBF (Temporary Block Flow) parameters

OMC-R GUI field name/BSS
parameter name
extuplinkOpt

Description

Values

The extuplinkOpt parameter

indicates whether or not
the Extended Uplink TBF
feature functionality is
unrestricted in the BSS
software. If the extuplinkOpt
flag indicates that extended
uplink TBF feature is
restricted, attempts to
change extended uplink
TBF specific database
parameters are rejected.

0 to 1
0 - restricted
1 - unrestricted

Continued

2-234

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 2-55

Interaction with other features

Extended Uplink TBF (Temporary Block Flow) parameters (Continued)

OMC-R GUI field name/BSS

parameter name
ext_ul_dur

Description

Values

The ext_ul_dur parameter

indicates the maximum
duration in block periods
(1 bp = 20 ms) for which
uplink TBF operates in
extended mode without
receiving any new real
RLC data block. When the
extended uplink feature is
unrestricted 0 indicates that
the extended uplink feature
is disabled. By default the
extended uplink feature is
disabled. When the feature is
unrestricted, the range 24 to
250 represents the possible
values for ext_ul_duration
and selecting any value
in this range enables the
feature. This parameter
changes inside and outside
of SYSGEN mode.

0, 24 to 250
Default is 0.

The ext_utbf_nodata
parameter indicates to
the mobile station during
extended uplink TBF mode
whether or not to send
any PACKET UPLINK
DUMMY CONTROL BLOCK
message when there is
no other RLC/MAC block
ready to send for this TBF.
It is broadcasted to the
MS in (PACKET) SYSTEM
INFORMATION message.
This element cannot be
modified if the Extended
Uplink TBF feature is
restricted. This element
is modified in or out of
SYSGEN mode.

0 to 1
Default is 0.
0 - The mobile station sends
a PACKET UPLINK DUMMY
CONTROL BLOCK during
extended uplink mode.
1 - The mobile station
refrains from sending a
PACKET UPLINK DUMMY
CONTROL BLOCK during
extended uplink mode.

Cell parameters
ext_utbf_nodata

Interaction with other features

Extended Dynamic Allocation Medium Access Mode (EDMAC) on Block Scheduling algorithm
during extended uplink TBF mode for EDMAC mobiles.

68P02901W17-T

2-235
Jan 2010

Extended Dynamic Allocation Medium Access Mode (EDMAC)

Chapter 2: Configuring BSS Features

Extended Dynamic Allocation Medium Access Mode

(EDMAC)

Overview
This is an optional feature for the network. It is an enhancement of the Dynamic Allocation
Medium Access Mode (DA). In EDMAC mode, the mobile station monitors its assigned PDCHs
starting with the lowest numbered PDCH, then the next lowest numbered PDCH, and so on.
Whenever the mobile station detects an assigned Uplink Status Flag (USF) value on an assigned
PDCH, the mobile station transmits a single RLC/MAC block on the same PDCH and all higher
numbered assigned PDCHs.
When a class 11 or 12 mobile requests an uplink TBF, the network assigns the EDMAC for the
uplink TBF if the mobile supports EDMAC and the TBF allocation requires EDMAC mode. The
network assigns the lowest numbered timeslot in the allocation as PACCH timeslot.
The PCU attempts to assign the maximum possible number of UL timeslots (3 for class 11 and 4
for class 12) to the mobile if gprs_ul_dl_bias is set to UL bias. During the uplink TBF in EDMAC,
the network schedules USFs in the lowest timeslot in the allocation, and the mobile station
transmits a single RLC/MAC block on the same PDCH and all higher numbered assigned PDCHs.
The PCU schedules periodic PUAKs for 3 or 4 UL TBFs frequent enough to prevent stalling
dependent on the number of uplink timeslots (3 or 4) used and GPRS or EGPRS TBF mode.
This feature requires the GPRS feature to be unrestricted.

Extended Dynamic Allocation Medium Access Mode (EDMAC)

parameters
Table 2-56 details the parameters associated with the Extended Dynamic Allocation Medium
Access Mode (EDMAC) feature. Unless stated otherwise, the OMC-R parameter name is usually
the same as the BSS parameter name. For further details of these and other parameters, refer
to Technical Description: BSS Command Reference (68P02901W23).

Table 2-56 Extended Dynamic Allocation Medium Access Mode (EDMAC) parameters
OMC-R GUI field name/BSS
parameter name
edaOpt

2-236

Description

Values

This parameter indicates

whether or not the Extended
Dynamic Allocation feature
functionality is unrestricted
in BSS software.

0 to 1
Default is 0
0 - restricted
1 - unrestricted

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Interaction with other features

Interaction with other features

This feature interacts with the following:

68P02901W17-T

Extended Uplink TBF

2-237
Jan 2010

Adjustable FER Bins

Chapter 2: Configuring BSS Features

Adjustable FER Bins

Overview
This feature modifies the Frame Erasure Rate (FER) bins and the measurement period
calculation.
It provides adjustable bins for all the FER counters so that all the thresholds are shared, and
can be configured by the user. It also calculates the measurement period of the FER by tracing
the number of SACCH multiframes.

Adjustable FER Bins parameters

Table 2-57details the parameters associated with Adjustable FER Bins. Unless stated otherwise,
the OMC-R parameter name is same as the BSS parameter name. For further details of these
and other parameters, see Technical Description: BSS Command Reference (68P02901W23).

Table 2-57 Adjustable FER Bins parameters

OMC-R GUI field name/BSS
parameter name
fer_meas_period

2-238

Description

Values

The parameter
fer_meas_period is displayed
in the BSS Detailed View.
This parameter allows the
customer to configure the
FER measuring period. The
value indicates the multiple
of 24 speech frames that is
used as the measuring period
of FER family statistics.

0 - Disabled
Use 24 speech frames
as the measuring period
of FER family statistics.
1 to 255 - The multiple of 24
speech frames that is used
as the measuring period of
FER family statistics.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Critical Statistics Reporting in 5 minutes

Critical Statistics Reporting in 5 minutes

Overview
While carrying out system performance optimization, the user can tune system parameters
in 5 minutes, once the parameter takes effect. Earlier, the user had to wait for at least one
statistics interval to obtain system performance measurements to make an adjustment in the
next interval. After the second interval, they could observe the adjustment results. With this
feature, the interval can be reduced to 5 minutes.
The user can check the status of the following top 6 customer prioritized statistics:
1.

Number of discarded CS paging messages per cell.

2.

Number of paging received from MSC per cell.

3.

Number of unsuccessful full rate and half rate allocations of a TCH within a cell for both
call origination and hand-in.

4.

The number of times that an attempt at SDCCH seizure was rejected because of SDCCH
congestion.

5.

Number of Short Message Service (SMS) transactions that occurred on a cell.

6.

Total number of calls originated for each cell on the BSS.

When the system performance is stable and optimization is complete, this feature can be
disabled.

Critical Statistics Reporting in 5 minutes parameters

Table 2-58details the parameters associated with Critical Statistics Reporting in 5 minutes.
For further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).

Table 2-58

Critical Statistics Reporting in 5 minutes parameters

OMC-R GUI field name/BSS

parameter name
_bss_data,1

Description
This parameter enables
or disables the function of
statistics uploading in a 5
minute interval.
This parameter can be
accessed/updated both in
and out of sysgen mode.

Values
0 to 1.
Default is 0.
0 - Disable the function
of statistics uploading
in a 5 minute interval.
1 - Enable the function of
statistics uploading in a
5 minute interval.
Continued

68P02901W17-T

2-239
Jan 2010

Critical Statistics Reporting in 5 minutes parameters

Chapter 2: Configuring BSS Features

Table 2-58 Critical Statistics Reporting in 5 minutes parameters (Continued)

OMC-R GUI field name/BSS
parameter name
_cell_data,21

2-240

Description

Values

This parameter enables

or disables the function of
statistics uploading in a 5
minute interval for each cell.
If it has a different value
from _bss_data,1, the BSS
level parameter has higher
priority.
This parameter can only
be accessed/updated out of
sysgen mode.

0 to 1.
Default is 0.
0 - Disable the function of
statistics uploading in a 5
minute interval for the cell.
1 - Enable the function of
statistics uploading in a 5
minute interval for the cell.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

SW enabler for PA bias switch on/off on CTU2D

SW enabler for PA bias switch on/off on CTU2D

Overview of SW enabler for PA bias switch on/off on CTU2D

Power-saving variants of the CTU2D radio have the capability to turn off the bias to the Power
Amplifier (PA) for individual idle Timeslots (TS). This feature provides software capability to
control (enable/disable) the PA bias on/off.
This optional feature can be enabled or disabled at the OMC-R via the parameters
Pw_Save_SwitchOpt and power_save_enable.
The OMC-R functionality is limited to sending enable/disable messages to the BSS and is not
involved in sending the messages to the BTS hardware.

Using PA bias feature in mixed radio Horizon II sites

{34416} In Horizon II sites with a mixed configuration of power-saving and non-power-saving
radios, this feature allocates the traffic to the non-power-saving radios first, so that the
power-saving radios can stay in power-saving mode for as long as possible. When there are
no TS or BCCH available on the non-power-saving radios, traffic is then allocated to the
power-saving radios.
Power saving is maximized when the least preferred RF channels are assigned to the
power-saving radios. At least one RTF has to be assigned to the power-saving radios if there are
more DRIs than the RTFs in the site.

Enabling and disabling the SW enabler for PA bias switch

on/off on CTU2D feature
The OMC-R GUI provides the interface to enable or disable the feature and in the CM, will
support sending of these messages to BSS. In the GUI, this feature can be enabled or disabled
only if the Pw_Save_SwitchOpt is unrestricted. Also the CMMib ensures that the enable/disable
information is sent to the BSS only if Pw_Save_SwitchOpt is unrestricted.

SW enabler for PA bias switch on/off on CTU2D parameters

Table 2-59 details the parameters associated with SW enabler for PA bias switch on/off on
CTU2D feature. For further details of these and other parameters, see Technical Description:
BSS Command Reference (68P02901W23).

68P02901W17-T

2-241
Jan 2010

SW enabler for PA bias switch on/off on CTU2D parameters

Chapter 2: Configuring BSS Features

Table 2-59 SW enabler for PA bias switch on/off on CTU2D parameters

OMC-R GUI field
name/BSS parameter
name

Description

Values

SW enabler
PA bias switch
on/off on CTU2D
Pw_Save_SwitchOpt

This attribute describes whether both

SW enabler for PA bias switch on/off on
CTU2D and Using PA bias feature in
mixed radio Horizon II sites features are
restricted or unrestricted at the BSS.
It is displayed on the BSS Detailed View
on the GUI.

0 to 1
0 - disabled
1 - enabled

{34416}power
save enable
power_save_enable

The site-level parameter

power_save_enable enables or
disables the feature SW enabler for PA
bias switch on/off on CTU2D and the
feature Using PA bias feature in mixed
radio Horizon II sites {FR34416} on the
BSS.
Enabling/disabling this parameter is
acknowledged by a message at the OMC
event management window. The OMC-R
displays a message to the Operator if
it receives an out of range value in a
Create/Set operation.

0 to 2
0 - Both SW enabler
for PA bias switch
on/off on CTU2D and
Using PA bias feature
in mixed radio Horizon
II sites are disabled
1 -SW enabler for PA
bias switch on/off on
CTU2D is enabled and
Using PA bias feature
in mixed radio Horizon
II sites is disabled
2 - Both SW enabler for
PA bias switch on/off on
CTU2D and Using PA
bias feature in mixed
radio Horizon II sites
are enabled

NOTE

2-242

The value of this

parameter can be
set to 0, 1, or 2 if
Pw_Save_SwitchOpt is
unrestricted at the BSS.

The features can only be

enabled or disabled on
Horizon II sites.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Dual Abis aware BTS

Dual Abis aware BTS

Overview
The Dual Abis aware BTS feature supports the BSC6 (RSR) program.

NOTE
BSC6 and Abis functionality is beyond the scope of GSR10 documentation and is
described in the RSR documentation.
This feature enables Horizon and Horizon II base stations to detect the Standard Abis interface
used by the BSC6, in addition to the existing Mobis interface used by the BSC2. It allows
migration (or large scale migration) from BSC2 to BSC6 to be implemented with minimum
downtime.
The following BTSs can be migrated to a BSC6:

Horizon I macro

Horizon II macro

Horizon II micro

Horizon II mini

This feature requires the dual boot functionality delivered in the BSC6 program to enable the
BTS to establish the Abis-OML connection, and to download the full Abis load from the BSC6
and then work under that BSC6.
The disp_option command displays this feature option at the BSS.

Dual Abis aware BTS parameters

Table 2-60 details the parameters associated with the Dual Abis aware BTS feature. For
further details of these and other parameters, refer to Technical Description: BSS Command
Reference (68P02901W23).

Table 2-60 Dual Abis aware BTS parameters

68P02901W17-T

BSS parameter name

Description

_site_data, 5

This element enables or

disables the Horizon I or
Horizon II BTS to connect to
the Abis interface. For other
BTS types, this element is
always set to 0.

Values
0 to 2.
Default is 0.
0 = Abis_Disable
1 = Abis_Enable_Conv
2 = Abis_Enable_CSFP

2-243
Jan 2010

Extended Range Cell (ERC) for Data

Chapter 2: Configuring BSS Features

Extended Range Cell (ERC) for Data

Overview
This feature allows a much larger diameter of cell sites in areas where there is not much traffic,
thereby reducing equipment needs in sparsely populated areas. A normal GSM/ GPRS cell has a
coverage of 35 km radius. An extended range GSM cell can cover up to 121 km radius.
In the normal range, the maximum timing advance value of a mobile can only go up to 63 bits.
To accommodate the additional propagation delay in the extended range, an extended range
timeslot needs to support a timing advance value of up to 219 bits. An extended range timeslot
is created by coupling two regular TDMA timeslots to support the extended timing advance.
Only the even numbered timeslot in an extended range pair is operational over the air.
GPRS/EGPRS channel type (PDCH) can also be supported on an extended timeslot. A mobile in
extended range can only be allocated on an extended PDCH, while a mobile in normal range can
be allocated on normal PDCH and/or extended PDCH.
In this feature, the extended timeslot can also be configured as GPRS/EGPRS channel type (that
is, 16K/32K/64K PDCH) for ERC data. In order to support EGPRS service for mobile in extended
range, extended timeslot can be supported on 64K RTF. Both extended PDCH and extended
TCH can be configured on the extended timeslot of 64K RTF.
This feature is configured on a per cell basis, and can be configured with extended PDCH
only on one RTF per cell.
If this feature is enabled, the BSC supports only synthesizer hopping in the cell. Baseband
hopping is not supported. The BSC supports Extended Range Cell for Data only when the
PCCCH feature and ASYM feature are disabled, and erc_range_cell is enabled.
The BTS supports extended range PDCHs only on CTU-2 radios and CTU2D radios.
This is an optional feature in GSR9.
Table 2-61 details the parameters associated with the Extended Range Cell (ERC) for Data
feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the
BSS parameter name. For further details of these and other parameters, refer to Technical
Description: BSS Command Reference (68P02901W23).

Table 2-61 Extended Range Cell (ERC) for Data parameters

OMC-R GUI field name/BSS
parameter name
ext_pdchs

Description
This element indicates the
number of extended range
PDCH supported by the RTF,
and also indicates whether
Extended Range Cell for
Data feature is enabled or
disabled. This parameter is

Values
0 to 4.
Default is 0.
0 indicates an extended
PDCH on this RTF is
disabled, and extended
PDCH number = 0.
At the same time, 0
Continued

2-244

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Overview

Table 2-61 Extended Range Cell (ERC) for Data parameters (Continued)
OMC-R GUI field name/BSS
parameter name

ercgprsOpt

68P02901W17-T

Description

Values

valid only if ercgprsOpt is set

to non-restricted.

indicates ERC for Data

feature is disabled.
1 indicates an extended
PDCH on this RTF is
enabled, and extended
PDCH number = 1.
2 indicates an extended
PDCH on this RTF is
enabled, and extended
PDCH number = 2.
3 indicates an extended
PDCH on this RTF is
enabled, and extended
PDCH number = 3.
4 indicates an extended
PDCH on this RTF is
enabled, and extended
PDCH number = 4.
A value of 1,2,3, or 4
indicates that ERC for Data
feature is enabled.

This parameter indicates

whether the Extended Range
Cell (ERC) for Data feature is
restricted or unrestricted.

0 to 1.
0 - Restricted.
1 - Unrestricted.

2-245
Jan 2010

Cage Management

Chapter 2: Configuring BSS Features

Cage Management

Overview of Cage Management

The Cage Management feature is a reliability and availability enhancement based on the
existing GSR10 BSC/XCDR hardware and software platform. This enhancement allows isolation
of non-master cages without causing a site reset and increases the availability by reducing
service outage to partial outage.
The RAN supports the BSC/XCDR cage management in taking a non-master cage and the
possible child extension cage out of service manually or automatically by fatal fault detection.
It keeps the remaining BSC/XCDR cages operational, and resumes the service of the OOS
cages after maintenance operations.

NOTE
The BSC/XCDR performs a BSC/XCDR reset when the master cage fails, or when
both the active and the standby LAN fail.
The OSS supports the Cage Management as a baseline feature.

Enabling and disabling the Cage Management feature

The Cage Management feature can be enabled or disabled by the MMI command line
configuration, or Sysgen configuration script. The configuration is effective immediately after
the operation and persistent throughout the lifecycle of the database. The BSC/XCDR disables
the Cage Management feature by default for better control of the feature during deployment.

Cage Management parameters

Table 2-62 details the parameters associated with Cage Management feature. For further
details of these and other parameters, see Technical Description: BSS Command Reference

(68P02901W23).

2-246

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Operability impacts

Table 2-62 Cage Management parameters

OMC-R GUI field name/BSS
parameter name
_bss_data,10

Description

Values

The per-BSS element _bss_data,10 allows

the customer to enable or disable the
functionality of the Cage Management
feature.
This element can be accessed and updated
both in and out of sysgen mode.
In case of GSR9 to GSR10 upgrade, the
element _bss_data,10 is reused from
GSR9, therefore an upgrade warning to set
to GSR10 default value is prompted.

0 to 1
Default is 0

Operability impacts
The following are the limitations of this feature:

Fatal failure of a master cage causes a BSC/XCDR reset.

When both the active and redundant LAN fail, it causes a BSC/XCDR reset.

If any cage is powered off, it causes a BSC/XCDR reset.

68P02901W17-T

2-247
Jan 2010

A5/1 Security Hardening

Chapter 2: Configuring BSS Features

A5/1 Security Hardening

Overview
The features A5/1 Security Hardening - Dummy Byte Randomization, A5/1 Security
Hardening - Immediate SDCCH Handover and A5/1 Security Hardening - Periodic
Traffic Handover, together strengthens the A5/1 stream cipher that provides over-the-air
communication in the GSM and reduces the possibility of reproducing the public decoding
in A5/1 Encryption.

Dummy Byte Randomization

Description
The length of each LAPDm frame, used to transport information between the mobile and
the network across a radio interface, is fixed. If the traffic information is not sufficient to
fill the frame, dummy bits are used to fill the LAPDm frame. These dummy bits are highly
predictable, and hence to increase security the dummy bits are randomly generated to fill up
the frame. This reduces the amount of predictable information in downlink messaging. The
PN9+PN18 algorithm is used for this purpose. The randomly generated dummy bits are less
predictable when sent over the air, and increases the security level in GSM networks without
any degradation in the quality of voice, and without any modification in the hardware.
The value of these dummy fill bits is insignificant and hence, setting the fill bits to a random
value does not have any impact on the compatibility of mobile station and air interface.

Dependencies
The dependencies for this feature are as follows:

A5/1 encryption support feature is unrestricted.

This feature is enabled on the CTU, CTU2 and CTU2D radios equipped in the Horizon

macro, Horizon II macro, Horizon II mini and Horizon II micro cabinets.

2-248

Signaling phase messages are transmitted on downlink SDCCH, SACCH associated with
SDCCH, FACCH when the associated TCH is in signaling only mode, and SACCH associated
with TCH when the associated TCH is in signaling only mode.

Traffic phase messages are transmitted on downlink FACCH when the associated TCH is
NOT in signaling only mode, and SACCH associated with TCH when the associated TCH is
not in signaling only mode.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Immediate SDCCH Handover

Dummy Byte Randomization parameters

Table 2-63 details the parameters associated with the Dummy Byte Randomization feature.
These parameters are available only at the BSS level. For further details of these parameters,
see Technical Description: BSS Command Reference (68P02901W23).

Table 2-63

Dummy Byte Randomization parameters

Description

BSS parameter name

Values

a51hardenOpt

The BSS parameter a51hardenOpt indicates

whether the A5/1 Security Hardening feature
bundle functionality is unrestricted or not in
the BSS software.

Default is N/A.
0 is restricted.
1 is unrestricted.

lapdm_fb_rand_s

The BSS parameter lapdm_fb_rand_s

indicates whether the A5/1 Security
Hardening - Dummy Byte Randomization
feature is enabled or not, for signaling phase
messages.

Default is 0.
0 is disabled.
1 is enabled.

NOTE
This parameter can be configured
only if a51hardenOpt is
unrestricted. This element
can be configured both in and out
of SYSGEN mode.
lapdm_fb_rand_t

The BSS parameter lapdm_fb_rand_t

indicates whether the A5/1 Security
Hardening - Dummy Byte Randomization
feature is enabled or not, for traffic phase
messages.

Default is 0.
0 is disabled.
1 is enabled.

NOTE
This parameter can be configured
only if a51hardenOpt is
unrestricted. This element
can be configured both in and out
of SYSGEN mode.

Immediate SDCCH Handover

Description
The Immediate SDCCH Handover feature performs handover of the encrypted call as soon as
possible after encryption has begun. This handover is done to prevent unauthorized monitoring
of the SDCCH channels and to prevent decoding of the encrypted data. The feature also stops
the downlink SACCH system information messages and downlink encrypted fill frames until
the handover is complete

68P02901W17-T

2-249
Jan 2010

Immediate SDCCH Handover

Chapter 2: Configuring BSS Features

Intra-cell handover When the BSC receives the Cipher Mode command from the MSC,
it buffers the message and initiates the intra-cell handover process by activating the A5/1
Encryption algorithm. When the BTS receives a message for intra-cell handover, it buffers the
message, allocates target resource for this handover and initiates the Assignment command.
When the target resource is activated successfully, the BSC sends a Ciphering Request message
to the BTS. The BTS stops all downlink SDCCH information and downlink fill frames until
the handover procedure is completed. The BTS sends the Assignment command to the MS
immediately after it receives the Ciphering Mode Completed message from the MS.

Inter-cell handover When the BSC receives the Cipher Mode command from the MSC,
it buffers the message and initiates the inter-cell handover process by activating the A5/1
Encryption algorithm and selects the target cell from the SACCH neighbor cell list.
When the source BTS receives a message for inter-cell handover for a special A5/1 immediate
SDCCH procedure, it buffers the message and initiates the Handover command.
The BSC sends the Ciphering Request message to the BTS after initiating the inter-cell handover
procedure to the source BTS. The source BTS stops all downlink SACCH system information
and downlink fill frames until the handover procedure is completed. The source BTS sends
the Handover command to the MS immediately after the Ciphering Mode Complete message
is received from the MS.

Dependencies
The dependencies for this feature are as follows:

A5/1 encryption support feature is unrestricted.

This feature is enabled on the CTU, CTU2 and CTU2D radios equipped in the Horizon
macro, Horizon II macro, Horizon II mini and Horizon II micro cabinets.

This feature does not support preemption of SDCCH channel.

This feature does not support communications on signaling TCH.

NOTE
The existing handover statistics are pegged for the additional SDCCH handovers,
additional handover failures, and call drops in the cell caused by immediate SDCCH
handovers. As a result, the value of these statistics and some KPIs may be affected
after enabling this feature.

2-250

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Periodic Traffic Handover

Immediate SDCCH Handover parameters

Table 2-64 details the parameters associated with the Immediate SDCCH Handover feature.
These parameters are available only at the BSS level. For further details of these parameters,
see Technical Description: BSS Command Reference (68P02901W23).

Table 2-64
BSS parameter
name

Immediate SDCCH Handover parameters

Values

Description

_cell_data,25

Default is 0.
Minimum is 0.
Maximum is 1.

0 - The immediate SDCCH intra-cell handover is

not active.
1 - The immediate SDCCH intra-cell handover
is active.

_cell_data,26

Default is 0.
Minimum is 0.
Maximum is 1.

0 - The immediate SDCCH inter-cell handover is

not active.
1 - The immediate SDCCH inter-cell handover
is active.

_cell_data,27

Default is 0.
Minimum is 0.
Maximum is 1.

0 - The immediate SDCCH intra-cell handover

has a higher priority.
1 - The immediate SDCCH inter-cell handover
has a higher priority.

_cell_data,28

Default is 0.
Minimum is 0.
Maximum is 3.

0 Do not perform the handover.

1 - Wait until an SDCCH channel is available, and
not to perform the handover if the timer defined
by _cell_data,29 timeout.
2 - Wait until an SDCCH channel is available, and
drop the call if the timer defined by _cell_data,29
timeout.
3 - Drop the current call.

_cell_data,29

Default is 6.
Minimum is 1.
Maximum is 30.

The maximum value of the timer is 1.5 sec, the

minimum value of the timer is 50ms,
The timer values are divided into 30 steps of
50ms
1 50ms
2 100ms

30 1.5 sec

Periodic Traffic Handover

Description
This feature performs inter-cell periodic traffic handover, which can occur randomly or at fixed
intervals until the call ends. The period at which the handover occurs is decided by comparing
the minimum and maximum values set by two parameters. These minimum and maximum
values are user-defined timer durations between 5 seconds and 300 seconds. If the value of the
maximum timer is equal to the minimum timer, the handover occurs at a fixed time, otherwise a
value is generated randomly using a Linear Congruential algorithm.

68P02901W17-T

2-251
Jan 2010

Periodic Traffic Handover

Chapter 2: Configuring BSS Features

This forced handover is differentiated from other intra-cell handovers by a new intra-cell
handover reason (periodic). Also, the periodic traffic handover searches for the channel type
rather than the interference band levels for selecting the target resource.

Dependencies
The dependencies for this feature are as follows:

A5/1 encryption support feature is unrestricted.

This feature is enabled on the CTU, CTU2 and CTU2D radios equipped in the Horizon

macro, Horizon II macro, Horizon II mini and Horizon II micro cabinets.

All existing Intra-cell handover statistics are pegged.

NOTE
The existing handover statistics are pegged for the intra-cell handovers caused by
periodic TCH handovers. As a result, the value of these statistics and some KPIs
may increase after enabling this feature.

Periodic Traffic Handover parameters

Table 2-65 details the parameters associated with the Periodic Traffic Handover feature. These
parameters are available only at the BSS level. For further details of these parameters, see
Technical Description: BSS Command Reference (68P02901W23).

Table 2-65

Periodic Traffic Handover parameters

BSS parameter
name

Values

Description

_cell_data,03

Range is 0 to 1.
Default is 0.

0 = periodic traffic handover is disabled.

1 = periodic traffic handover is enabled.

_cell_data,04

Range is 5 to 300.
Default is 40.

Maximum configurable timer value.

NOTE
The unit is measured
in seconds.
_cell_data,06

Range is 5 to 300.
Default is 40.

Minimum configurable timer value.

NOTE
The unit is measured
in seconds.

2-252

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Gb over IP feature

Gb over IP feature

{26638}

Overview
The Gb interface connects the BSS and the SGSN, allowing the exchange of signaling
information and user data. The Gb over IP feature is implemented on the Gb Interface and
provides an alternate backhaul option to the existing E1 link that uses frame relay for data
transmission. An option is provided to select either the frame relay or the Internet Protocol as
the network service for the Gb Interface for the PCU.
A UDPROC2 configured as a PXP can carry both Gb over IP and GDS/GSL over IP traffic
simultaneously. The front panel Ethernet port is used to transport Gb traffic and the rear
Ethernet port is used to transport GDS/GSL traffic. The PPROC mounted on these PXPs
processes both Gb and GDS(LAPD) traffic, while the baseboard of the PXP processes the GDS
(TRAU) traffic.
The weighted load sharing algorithm distributes the UL GB data or signaling traffic over the
available NSVCs, and the new resource distribution function allows the PCU to change the IP
endpoint for the MS in response to a request from the SGSN. This enhances the flexibility in
distributing the traffic on the GB interface.

Dependencies
The U-DPROC2 PXP configuration is supported for the Gb over IP feature, as only U-DPROC2
has an Ethernet interface that supports the Internet Protocol.
The remote end of the Gb Over IP link works in auto-negotiation mode as a mandatory setting.

Parameters
Table 2-66 details the parameters associated with the Gb over IP feature. These parameters
are available only at the BSS level. For further details of these parameters, see Technical
Description: BSS Command Reference (68P02901W23).

Table 2-66 Gb over IP feature BSS parameters

OMC-R GUI field
Name/BSS parameter
name
Gb Over IP Feature
GboIPOpt

Description
The GboIPOpt parameter
indicates whether the Gb over
IP feature is restricted or
unrestricted at the BSS.

Values
Range is 0 to 1.
0 - Restricted
1 - Unrestricted

Continued

68P02901W17-T

2-253
Jan 2010

Parameters

Chapter 2: Configuring BSS Features

Table 2-66 Gb over IP feature BSS parameters (Continued)

OMC-R GUI field
Name/BSS parameter
name
Gb Mode
gb_mode

Description

Values

The gb_mode parameter

indicates whether the Gb over IP
feature functionality is enabled or
disabled at the BSS.

Range is 0 to 1.
0 Frame Relay.
1 Static IP.
Default is 0.

Table 2-67 details the GBL attributes:

Table 2-67

Gb over IP feature GBL attributes

OMC-R GUI
field Name/GBL
attribute name

Description

Values

DPROC ID
dproc_id

The attribute dproc_id identifies a

unique id for the PXP DPROC that
is connected to the Ethernet GBL.

Range is 1 to 6 and 11 to
16.

Gateway
gateway

The attribute gateway identifies

the default gateway for the PCU
Ethernet GBL.

Range is 0.0.0.0 to
223.255.255.255.
Exception is 127.x.x.x.

NOTE

IP Address
ip_address

The address
0.0.0.0 means no
default gateway is
in use.

The gateway and

the ip_address
should be in the
same subnet,
(defined by the
subnet_mask).

The gateway
address should
not be the same as
the ip_address.

The attribute ip_address identifies

the valid class A/B/C network IP
Address for the PCU Ethernet
GBL.

Range is 0.0.0.0 to
223.255.255.255.
Exception is 127.x.x.x.

Continued

2-254

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Parameters

Table 2-67 Gb over IP feature GBL attributes (Continued)

OMC-R GUI
field Name/GBL
attribute name
Subnet Mask
subnet_mask

Description
The attribute subnet_mask
identifies the PCU Ethernet GBL
subnet mask.

Values
Range is 128.0.0.0 to
255.255.255.255.

NOTE

UDP Port
udp_port

The attribute udp_port identifies

the valid numeric UDP port for the
PCU Ethernet GBL.

Most
significant
bit is 1.

Least
significant
bit is 0.

Range is 1024 to 65535.

Minimum is 1024.
Maximum is 65535.

Table 2-68 details the NSVC attributes:

Table 2-68 Gb over IP feature NSVC attributes

OMC-R GUI field
Name/NSVC
attribute name

Description

Values

Data weight
dat_weight

The attribute dat_weight is an

IP based NSVC attribute and
it identifies the data weight
associated with the remote IP end
point. NSVC is recycled when
dat_weight is changed

Range is 0 to 255.
Minimum is 0.
Maximum is 255.

Remote IP
remote_ip

The attribute remote_ip is an IP

based NSVC attribute and identifies
the valid value of the remote ip.

Range is 0.0.0.0 to
223.255.255.255.
Exception is 127.x.x.x.

Signaling weight
sig_weight

The attribute sig_weight is an IP

based NSVC attribute and identifies
the signaling weight associated
with the remote IP end point.

Range is 0 to 255.
Minimum is 0.
Maximum is 255.

UDP Port
udp_port

The attribute udp_port is an IP

based NSVC attribute and identifies
the UDP port of the remote IP end
point.

Range is 0 to 65535.
Minimum is 0.
Maximum is 65535.

68P02901W17-T

2-255
Jan 2010

Increase RSL-LCF capacity on GPROC3/GPROC3-2

Chapter 2: Configuring BSS Features

Increase RSL-LCF capacity on GPROC3/GPROC3-2

{34282}

Overview
This feature increases the RSL-LCF capacity on GPROC3 and GPROC3-2 by utilizing their
capability to the maximum.
A new threshold on the LCF is set and the maximum number of call information blocks for the
GPROC3 and GPROC3-2 is increased and processing is streamlined to improve the call load
support.
The feature supports a new GPROC alarm to report the over-utilization of CPU on a GPROC. The
alarm is based on the value of CPU_USAGE statistics. The threshold value can be configured
through MMI. The GPROC allocation algorithm is modified to improve the allocation of
GPROC3-2s to RSL-LCFs when the Increased Network Capacity feature is unrestricted.

Parameters
Table 2-69 details the parameters associated with the Increase RSL-LCF capacity on
GPROC3/GPROC3-2 feature. These parameters are available only at the BSS level. For
further details of these parameters, see Technical Description: BSS Command Reference
(68P02901W23).

Table 2-69 Increase RSL-LCF capacity on GPROC3/GPROC3-2 parameters

OMC-R GUI field
Name/BSS parameter
name
CPU Threshold
cpu_threshold

2-256

Description
The parameter cpu_threshold
identifies the High CPU utilisation
threshold used for the GPROC
high CPU alarm.
The threshold is customer
configurable and the
cpu_threshold parameter
defines the High CPU utilisation
threshold used for the GPROC
high CPU utilisation alarm.

Values
Range is 0 to 100.
Minimum is 0.
Maximum is 100.
Default is 100.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

CTU4 and RCTU4

CTU4 and RCTU4

{34371G}

Feature description
This set of features supports the CTU4 radio and the RCTU4 remote radio head. The CTU4 and
RCTU4 are available in 900 and 1800 MHz versions for use in Horizon II macro, Horizon II
mini, and Horizon II micro BTSs.
The {34371G} feature forms the base and the other features are the enhancements.
Table 2-70 shows the (R)CTU4 feature set and their functions.

Table 2-70

(R)CTU4 feature set

Feature

Functionality

{34371G}

This feature supports the CTU4 and the RCTU4 900 MHz
variant in the Horizon II macro and Horizon II mini sites.

{34372G}

This feature supports the CTU4 and the RCTU4 1800 MHz
variant in the Horizon II macro and Horizon II mini sites.

{34373G}

This feature increases the Horizon II BTS capacity to support

additional carriers and the BBU (R)CTU4 in the Horizon II
micro site.

{34374G}

This feature supports the BBU on the Site Controller 2.

{35200G}

CTU4 and RCTU4 8 carrier support.

Overview of CTU4 and RCTU4

The Horizon II BBU (R)CTU4 radio platform separates the combined baseband and the radio
frequency functions between a dedicated baseband unit (BBU) processing board and an internal
(CTU4) unit and an external (RCTU4) unit.
The BBU is a baseband processing card mounted on the Site Controller 2 in the Horizon II site.
The BBU provides most of the digital baseband processing for multiple radio units and the
Radio Sub-System (RSS).
The RF functions are handled by the CTU4 and the RCTU4 units. The remote radio head RCTU4
is connected to the BBU by a fiber-optic cable. Every RF unit supports up to 6 GSM carriers.
Multi-carrier power amplifiers (MCPA) and wideband receiver ports in the CTU4 / RCTU4
facilitate future wideband technology such as Long Term Evolution (LTE). The radio units are
configurable up to 20MHz bandwidth and supports up to 24 carriers per cabinet.
Advantages provided by these features:

68P02901W17-T

2-257
Jan 2010

CTU4 and RCTU4 parameters

Chapter 2: Configuring BSS Features

Improved receiver sensitivity.

Radio hardware capability for Long Term Evolution (LTE).

Improved power efficiency.

Improved network coverage.

CTU4 and RCTU4 parameters

Table 2-71 details the parameters associated with CTU4 and RCTU4 feature. For further
details of this and other parameters, see Technical Description: BSS Command Reference
(68P02901W23).

Table 2-71 CTU4 and RCTU4 BSS parameters

OMC-R GUI field name/BSS
parameter name

Description

Values

(R)CTU4 to support 3 carriers per

Tx port
MCBTSR8Opt

This parameter indicates

if the (R)CTU4 Radio can
support the operation of 3
carriers per Tx port in one
(R)CTU4 Radio in the BSS
software.

0 - Does not support

(R)CTU4 in 3 carriers per
Tx port.
1 - Supports (R)CTU4 in 3
carriers per Tx port.

{35200G} (R)CTU4 to support 4

carriers per Tx port
CTU8Opt

This parameter indicates

if the (R)CTU4 Radio can
support the operation of 4
DRIs per Tx lineup port in
one (R)CTU4 Radio in the
BSS software.

0 - Does not support

(R)CTU4 in 4 carriers per
Tx port.
1 - Supports (R)CTU4 in 4
carriers per Tx port.

Table 2-72 shows the BTP and BBU parameters.

Table 2-72

CTU4 and RCTU4 BTP and BBU parameters

OMC-R GUI field name/BTP

parameter name

Description

Values

BBU Attached
bbu_attached

This is a BTP parameter and

indicates whether a BBU is
attached to the BTP.

0 is No.
1 is Yes.

BBU Identifier
bbu_id

This is a BBU parameter and

indicates the identifier of the
bbu and inherited from the
related BTP. For Example, BTP 0
0 with BBU 0 0.

Range is 0-1.

Inter BBU Port

inter_bbu_port

This is a BBU parameter and

indicates the BBU port reserved
for D4+link between two BBUs.

Range is 0-2.

Table 2-73 shows the DRI parameters.

2-258

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 2-73

CTU4 and RCTU4 parameters

CTU4 and RCTU4 DRI parameters

OMC-R GUI field name/DRI

parameter name
Slot Number
slot_num

Description
This parameter indicates the
slot where the CTU4 resides.
For CTU2 radio units, the
attribute tcu_port indicates the
slot where the radio resides.
For CTU4 radio unit, the slot
is indicated by the attribute
slot_num. Any two radios
including CTU2 and CTU4
cannot reside on the same slot
in the same cabinet.

Values
0-5 for Horizon II

macro.
0-1 for Horizon II
mini.
0 for Horizon II
micro.

NOTE
RCTU4 does
not support this
parameter.
First Component
first_dev_type

This parameter indicates the

type of the first device attached
to.

39 for BBU.
5 for CTU4.

First Component Device Id1

first_dev_id

This indicates the first device ID

of the BBU or the (R)CTU4 DRI.

0-1 for BBU.

0-5 for DRI.

First Component Device Id2

first_dev_dri_id

The second device ID of

(R)CTU4 DRI. The BBU does not
have second device ID.

Range is 0-11

First Component Port

first_dev_port

This parameter indicates the

port on the BBU/(R)CTU4 at
which the (R)CTU4 is attached.

0-2 for BBU.

0-1 for CTU4.

First Ingress SFP Port

ingress_1_port

This parameter indicates the

first ingress port of (R)CTU4.

Range is 0-1.

Second Component
second_dev_type

This parameter indicates the

second device attached to.

39 for BBU.

NOTE
Invalid value
indicates that there
is no second device
attached.
Continued

68P02901W17-T

2-259
Jan 2010

CTU4 and RCTU4 parameters

Chapter 2: Configuring BSS Features

Table 2-73 CTU4 and RCTU4 DRI parameters (Continued)

OMC-R GUI field name/DRI
parameter name
Second Component Device Id1
second_dev_id

Description
This indicates the first device ID
of the BBU.

Values
Range is 0-1 for
BBU.

NOTE
This attribute is
valid only when
second_device_type
has a valid value.
Second Component Port
second_dev_port

This parameter indicates the

port on the BBU at which the
(R)CTU4 is attached.

Range is 0-2.

NOTE
This attribute is
valid only when
second_device_type
has a valid value.
Second Ingress SFP Port
ingress_2_port

This parameter indicates the

second ingress port of (R)CTU4.

Range is 0-1.

NOTE
This attribute is
valid only when
second_device_type
has a valid value.
Lowest ARFCN
lowest_arfcn

This parameter specifies the

ARFCN of the lowest frequency
set for (R)CTU4.

NOTE

PGSM: 1-124.
EGSM: 0, 1-124,
975-1023.
DCS1800:
512-885.

PCS1900 is not
supported at the
Horizon II site.
DRI density on Tx Port 0
tx_0_dri_density

This parameter specifies the

carrier number on Tx port
0 in one (R)CTU4 Radio. It
supports 2 density per Tx port,
which means 2 carriers per Tx
port in one (R)CTU4 Radio. If
MCBTSR8Opt is unrestricted,
3 density per Tx port can
be supported. {35200G} If
CTU8Opt is unrestricted, up to
4 density per Tx port can be
supported.

{35200G} Range
is 0-4.

Continued
2-260

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

CTU4 and RCTU4 parameters

Table 2-73 CTU4 and RCTU4 DRI parameters (Continued)

OMC-R GUI field name/DRI
parameter name

Description

Values

DRI density on Tx Port 1

tx_l_dri_density

This parameter specifies the

carrier number on Tx port 1
in one (R)CTU4 Radio. This
parameter supports 2 density
per Tx port. If MCBTSR8Opt
is unrestricted, 3 density per
Tx port can be supported.
{35200G} If CTU8Opt is
unrestricted, up to 4 density per
Tx port can be supported.

{35200G} Range
is 0-4.

Tx Port
tx_port

This parameter specifies which

RF transmission port the DRI is
using. Each Tx port can support
up to 2 carriers (3 carriers per
Tx port can be supported if
MCBTSR8Opt is unrestricted).

0 for Tx port 0,
l for Tx port l.

DRI id of the first DRI of Tx Port 0

assoc_dri_id1_tx0

This parameter specifies the

first associated DRI on Tx port
0.

Range is 0-11.

DRI id of the second DRI of Tx Port 0

assoc_dri_id2_tx0

This parameter specifies the

second associated DRI on Tx
port 0.

Range is 0-11.

DRI id of the third DRI of Tx Port 0

assoc_dri_id3_tx0

This parameter specifies the

third associated DRI on Tx port
0.

Range is 0-11.

{35200G}DRI id of the fourth DRI of

Tx Port 0
assoc_dri_id4_tx0

This parameter specifies the

fourth associated DRI on Tx
port 0.

Range is 0-11.

DRI id of the first DRI of Tx Port 1

assoc_dri_id1_tx1

This parameter specifies the

first associated DRI on Tx port
1.

Range is 0-11.

DRI id of the second DRI of Tx Port 1

assoc_dri_id2_tx1

This parameter specifies the

second associated DRI on Tx
port 1.

Range is 0-11.

DRI id of the third DRI of Tx Port 1

assoc_dri_id3_tx1

This parameter specifies the

third associated DRI on Tx port
1.

Range is 0-11.

{35200G} DRI id of the fourth DRI of

Tx Port 1
assoc_dri_id4_tx1

This parameter specifies the

fourth associated DRI on Tx
port 1.

Range is 0-11.

Table 2-74 shows the modified DRI parameters.

68P02901W17-T

2-261
Jan 2010

CTU4 and RCTU4 parameters

Chapter 2: Configuring BSS Features

Table 2-74

Modified DRI parameters

OMC-R GUI field Name/DRI

parameter name

Description

Values

DRI Type
DRI board_type

DRIM: Old DRI for non-M-Cell

site.
TCU: Old DRI for M-Cell site.
RH: Radio Head, new generation
DRI should work with BBU on
Horizon II cabinet.

DRIM is 0,
TCU is 2,
RH is 24.

Cabinet Identifier
cabinet_id

RCTU4 does not use this

parameter since it does not
reside in any cabinet. When
board_type is RH and cabinet_id
is an invalid value, then it
suggests an RCTU4 instead of
CTU4.

Range is 0-15.

Cell 1 Antenna Select

antenna_select

Antenna selected for Cell1.

Range is 1-3.

Diversity Flag
diversity_flag

(R)CTU4 does not support

4branch Rx diversity.

CTU4: Range is 0-1

Others: Range is
0-2

Cell Type
fm_cell_type

This parameter indicates the

type of the cell.

Range is 0-4.

Cell-X-Import changes to double-density or single-density DRIs

Cell-X-Import automatically locks and unlocks a DRI when changing it from double density to
single density.
If the DRI/RTF Planning input file contains the dri_density attribute with a change in value from
single density (1) to double density (2), then the Cell-X-Import operation locks the DRI, makes
the change to dri_density, and then unlocks the DRI (the associated DRI is auto created). The
Associated DRI is also be unlocked. The user can specify the value of assoc_dri_id (the rdn of
the associated DRI) when changing the DRI attribute dri_density from 1 to 2 or 3 (assuming
that the user has configured the parameter).
If the DRI/RTF Planning input file contains the dri_density attribute with a change in value from
double density (2) to single density (1), then Cell-X-Import automatically locks the DRI and
the associated DRI, makes the change, and then unlocks the DRI (the associated DRI is auto
deleted). The DRI locking and unlocking is recorded in the RF log file.
The user cannot modify the attribute assoc_dri_id directly (in one step). To modify the attribute
assoc_dri_id, carry out the following procedure:

Procedure 2-7 Modifying the attribute assoc_dri_id

2-262

Change the dri_density to 1 using an import (CellX automatically locks both

DRIs and unlocks the original DRI).

Perform an export.

Change dri_density to 2 or 3 and specify the new assoc_dri_id value in a second

import.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Interaction with other features

Interaction with other features

This feature interacts with the following features:

Software patching.

Support for high-power variant of Horizon II micro.

4way receive diversity.

CTU2D.

68P02901W17-T
Jan 2010

2-263

Interaction with other features

2-264

Chapter 2: Configuring BSS Features

68P02901W17-T
Jan 2010

Chapter

3
Configuring Network, OMC-R, and MSC
Instances

The information here describes how to create Network, OMC-R, and MSC instances in the
OMC-R GUI. The following topics are described:

Configuring a network instance on page 3-2.

Configuring an OMC-R or MSC instance on page 3-7.

68P02901W17-T
Jan 2010

3-1

Configuring a network instance

Chapter 3: Configuring Network, OMC-R, and MSC Instances

Configuring a network instance

Introduction to configuring a network instance

A network instance must be the first network object to be created in the OMC-R GUI Navigation
Tree. It must be configured before a BSS can be configured.
Only one Network instance should be configured for a GSM system.
This section describes how to:

Create a Network instance.

Delete a Network instance.

To modify a Network instance, see Modifying a network object using the OMC-R GUI on page
1-34.

Creating a Network instance using the OMC-R GUI

To create a Network instance to the OMC-R Navigation Tree, use the following procedure:

Procedure 3-1 Create Network instance using OMC-R GUI

1

From the Front Panel, click the Config Mgt icon to display the
Navigation Tree.

Select Edit Create Network from the menu bar to open a new
Network Detailed View.

NOTE
If a Network instance has already been created, the Create
Network menu option is not displayed.
3

Complete the fields as required. See Network Detailed View fields on

page 3-3 for details.
Continued

3-2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Network Detailed View fields

Procedure 3-1 Create Network instance using OMC-R GUI (Continued)

4

Complete the Map Information section using the name selected for the
network as it is required to appear on the relevant map.
For the Name field, enter the name of the map where the network is to
be placed. This will probably be a new map name, since a new network
is being created. The Map label name is created by default to coincide
with the name of the new network. Only input a name where there is a
special requirement to do so.
When a special background to a map is required, for example a
geographical display, type the name of the file (without the .map
extension) under which the background is stored.

NOTE
A background display to a map is only possible where the
relevant file has been defined and placed in the directory:
/usr/omc/config/global/maps.

Where the map background is to be blank, or where no geographical

backgrounds are available, allow the field to default to Empty.
5

Select File Save from the menu bar to save the new configuration.

Select File Close to close the Map Network Detailed View window.

Select File Create from the menu bar.

Select File Close from the menu bar to close the Network Detailed
View.

Network Detailed View fields

The following sections list and briefly describe the parameter fields in the Network Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

68P02901W17-T

3-3
Jan 2010

Network Detailed View fields

Chapter 3: Configuring Network, OMC-R, and MSC Instances

Identification grouping
Table 3-1 details the fields in the Identification grouping of the Network Detailed View.

Table 3-1

Network Detailed View fields - Identification grouping

Field name
Name

Brief description
Unique Network name.

Mandatory
or
Optional?

Values
Up to 31
characters
plus the
NULL
character.

Mandatory.

Mobile
Country Code

The MCC for the network.

3 digits.

Mandatory.

Mobile
Network Code

The MNC for the network.

2 or 3 digits.

Mandatory.

Resync on
Startup

Whether the OMC-R initiates a Resync of the

Network on system start-up.

Yes (1) or
No (0).
Default is 1.

Optional.

RDN Class

The object class identifier.

Default is
Network.

Optional.

Continued

3-4

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Network Detailed View fields

Table 3-1 Network Detailed View fields - Identification grouping (Continued)

Field name

Brief description

Values

Mandatory
or
Optional?

RDN Instance

The instance identifier of the object. Together

with the rdnClass, it makes up the Relative
Distinguished Name (RDN) of an object.
When the Environment Variable
AUTO_GEN_RDN is set to On (default)
(see Operating Information: OMC-R System
Administration (68P02901W19) for further
details), the RDN Instance field is automatically
populated by the OMC-R with the next available
RDN instance id when the following objects are
created: BSS, RXCDR, AssocRXCDR, AssocBSC,
SITE, Region, CELL, Neighbor, UtranNbr, RTF
Group, RTF, DRI Group, DRI, SMSCBmsg, RSL,
Cabinet, Cage, DHP, EAS, COMB, KSW, GCLK,
MSI, Conn Link, PATH, XBL, PCU, PSP, GDS,
GBL, GSL, OML, OMF, LCF, CBL, MTL, CSFP,
TestNeighbour, DYNETGroup, DYNET, GPROC,
BSP and BTP.
The RDN Instance is not automatically
populated for the following auto-created
objects: IAS, KSWpair, LAN, TDM, TRX,
FreqHopSys, Handover/Power Control
algorithms. Neither is it auto-populated for a
DPROC because the valid set for the DPROC
RDN Instance is 1 to 6 or 11 to 16. There is no
RDN Instance field for object NSVC.
The RDN Instance field is auto-populated in
sequential order.
Although the RDN instance is created
automatically by the OMC-R, a user can still
type in a different valid RDN instance when
creating the object, if required.

Default is 0.

Mandatory.

NMC Value

The OMC-R supports an interface to a Network

Management Centre (NMC). This is the instance
identifier of the object on the NMC interface.

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this Network. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

68P02901W17-T

3-5
Jan 2010

Deleting a Network instance

Chapter 3: Configuring Network, OMC-R, and MSC Instances

State grouping
Table 3-2 Network Detailed View fields - State grouping
Mandatory or
Optional?

Field name

Brief description

Values

Time of Last Audit

Gather Complete
timeOfLastAuGather
Complete

Shows the last time the

Gather phase of a network
Audit was completed.

Date and
Time
(ddmmyy
hhmm).

Read-only.

Time of Last Audit

Apply Complete
timeOfLastAuApply
Complete

Shows the last time the

Apply phase of a network
Audit was completed.

Date and
Time
(ddmmyy
hhmm).

Read-only.

Map Information grouping

Table 3-3 details the fields in the Map Information grouping of the Network Detailed View.

Table 3-3 Network Detailed View fields - Map Information grouping

Field name

Brief description

Default Map

When a Network is created, the

OMC-R creates a default Network
map. This is the object identifier
of the default map. As each node
(BSS, RXCDR, SITE, OMC, MSC) is
created, appropriate map nodes are
created on the Network's default
map.
In edit mode, click the button to
display the Map Network Detailed
View, which shows the Map
Background setting.

Values

Mandatory or
Optional?
Optional.

Deleting a Network instance

A Network instance can only be deleted if all its child instances have also been deleted. That is,
BSSs, RXCDRs, OMC-Rs, MSCs and Commslinks must also have been deleted. Any attempt to
delete a network containing any network elements is refused.
To delete a Network instance, see Deleting a network object using the OMC-R GUI on page 1-37.

3-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring an OMC-R or MSC instance

Configuring an OMC-R or MSC instance

Introduction to configuring an OMC-R or MSC instance

An OMC instance must be configured before a BSS can be configured.
This section describes how to:

Create an OMC or MSC instance.

Delete an OMC or MSC instance.

To modify an OMC or MSC instance, see Modifying a network object using the OMC-R
GUI on page 1-34.

Creating an OMC-R or MSC instance

An OMC-R or MSC can only be created if a Network instance (that is, the parent) has already
been created.
To create an OMC-R or MSC instance, use the following procedure:

Procedure 3-2

Create an OMC-R or MSC instance

Navigate to and select the OMC-R or MSC class button. If necessary,

see Navigating to a network object class or instance on page 1-28 for
further details. The network object class button changes color.

From the menu bar, select Edit Create. The OMC-R or MSC Detailed
View window in Create mode is displayed.

Complete the fields, as required. See OMC and MSC Detailed View
fields on page 3-7 for further details.

Save and close the Detailed View as detailed in Creating a network

object using the OMC-R GUI on page 1-32.

OMC and MSC Detailed View fields

The following sections list and briefly describe the parameter fields in the OMC and MSC
Detailed Views according to their parameter grouping.

68P02901W17-T

3-7
Jan 2010

OMC and MSC Detailed View fields

Chapter 3: Configuring Network, OMC-R, and MSC Instances

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

NOTE
Without write permission on the fields, it is not possible to change any values in the
Active fields. In this case, delete the OMC-R and recreate it in Edit mode.

Identification grouping
Table 3-4 details the fields in the Identification grouping of the OMC and MSC Detailed Views.

Table 3-4

OMC and MSC Detailed View fields - Identification grouping

Field name
Name

Active (OMC only)

Brief description

Mandatory
or
Optional?

Values

Unique OMC or MSC name.

Up to 31
characters
plus the
NULL
character.

Mandatory.

Multiple OMCs can be created in the MIB, but

only one represents the actual in-situ OMC.
This is the active OMC where, for example,
the SoftwareLoads will be installed.
Select Yes if this is the first OMC-R.
It is essential that the first OMC-R in a
network is created with Active flag set at
True, or software download is impossible.
Subsequent OMC-Rs have to be created
with Active flag set at False, as there can
only be one active OMC-R in a network.

No (0) and
Yes (1).
Default is
No (0)

Optional.

Continued

3-8

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting an OMC-R or MSC

Table 3-4 OMC and MSC Detailed View fields - Identification grouping (Continued)
Field name

Brief description

Values

Mandatory
or
Optional?

Host name (OMC

only)

Name of the UNIX host machine. Mainly

used to support the ProxyCell synchronization
feature for inter-OMC ProxyCell updates.

0 - 24

Mandatory.

RDN Class

See description in Table 3-1.

Default is
OMC or
MSC

Optional.

RDN Instance

See description in Table 3-1.

OMC is
0 - 50.
MSC is
0 - 100.
Default is 0.

Optional.

NMC RDN Value

See description in Table 3-1.

Optional.

Displays the name of the parent. Click to

display the parent Network Detailed View.

Not
applicable.

Parent Detail View

Additional Information
Use the Additional Information window to input any notes relating to this OMC or MSC. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Map Information grouping

Standard map information fields, see Table 4-15 for details.

Deleting an OMC-R or MSC

An OMC-R or MSC must only be deleted after authorization has been obtained in advance from
the OMC-R System Administrator.
All software loads associated with the active OMC-R must be deleted before an OMC-R can
be deleted.
To delete an OMC-R or MSC, see Deleting a network object using the OMC-R GUI on
page 1-37.

68P02901W17-T
Jan 2010

3-9

Deleting an OMC-R or MSC

3-10

Chapter 3: Configuring Network, OMC-R, and MSC Instances

68P02901W17-T
Jan 2010

Chapter

4
Configuring a BSS/RXCDR

The procedures to be followed to configure a BSS and/or RXCDR are provided here. The
following topics are described:

Overview of adding a BSS or RXCDR on page 4-2.

Creating a BSS using the OMC-R GUI on page 4-6.

Creating an RXCDR using the OMC-R GUI on page 4-39.

MSC to BSS overload control on page 2-23.

Deleting a BSS/RXCDR on page 4-44.

Reparenting a BSS on page 4-100.

Equipping cabinets and cages at a BSS site on page 4-51.

Configuring an RXCDR cabinet on page 4-62.

Configuring an Assoc_BSS on page 4-68.

Configuring an Assoc_RXCDR on page 4-72.

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR on page 4-80.

Configuring DYNETs and DYNETGroups on page 4-90.

Configuring a DYNETGroup on page 4-92.

Configuring a DYNET on page 4-94.

Reparenting a BSS on page 4-100.

Reparenting an RXCDR to a different MSC on page 4-106.

68P02901W17-T
Jan 2010

4-1

Overview of adding a BSS or RXCDR

Chapter 4: Configuring a BSS/RXCDR

Overview of adding a BSS or RXCDR

Introduction to adding a BSS/RXCDR

This section provides a high-level overview of all the procedures required to add a BSS or
RXCDR to a network. The information should be used as an initial explanation, and later as a
quick reference guide.

Prerequisites for adding BSS/RXCDR

Prerequisites at BSS
Before adding a BSS, check that:

The BSC hardware has been installed and commissioned.

Physical links exist between BSC and ING 6525 packet switch, 6250 MUX, or 6560
MPRouter.

Physical links exist between OMC-R and ING 6525 packet switch, 6250 MUX, or 6560
MPRouter.

The BSS has valid DTE addresses (BSS address is set and OMC-R DTE addresses point to
the appropriate OMC-R). Refer to Assigning DTE X.121 addresses at the NE on page 5-19.

The BSC has had its software load and NE database object LAN loaded. This is confirmed
if the database object has been uploaded to the OMC-R, immediately after the BSS has
been created at the OMC-R.

Prerequisites at the OMC-R

Before adding a BSS, check the following at the OMC-R:

4-2

The network, OMC-R, and MSC objects are already added to the Navigation Tree. Refer to
Chapter 3 Configuring Network, OMC-R, and MSC Instances for details.

Ensure that the software load for running the BSS has been installed on the OMC-R. Refer
to OMC-R Online Help, Network Operations.

If the BSS is not already operational (software load and NE database object not LAN loaded)
and requires a code download, ensure that the NE database object is available to be loaded
and activated once the BSS has been created. Ensure that the database version matches
the required software load version. Refer to OMC-R Online Help, Network Operations.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Overview procedure for adding BSS/RXCDR to the network

Overview procedure for adding BSS/RXCDR to the network

To add a BSS/RXCDR to the network, follow this overall procedure:

Procedure 4-1

68P02901W17-T

Add BSS/RXCDR to the network

Create the BSS or RXCDR. Refer to Creating a BSS using the OMC-R
GUI on page 4-6 and Creating an RXCDR using the OMC-R GUI on
page 4-39.
If the BSS already contains a load and database, and has its X.25
connections and OML properly configured, the BSS will be able to
connect to the OMC-R once the BSS object has been created in the MIB.

Open a Event with History window. Select the BSS on the Navigation
Tree, and use the Display - Events - With History menu option. Select
Wide format. Check for a red X.25 link failure alarm, which means
the OMC-R cannot connect to the BSS. Refer to OMC-R Online Help,
Network Operations for further details.

If the alarm exists, cycle the X.25 port on the packet switch/MUX and
check if the OML comes into service. If this works, the alarm clears
and the BSS begins sending events and statistics files to the OMC-R.

If the alarm has not cleared, configure the packet switch/MUX. Refer
to . The red X.25 link failure alarm clears, when the OML connects
to the OMC-R.

If the BSS is not already operational (software load and NE database

object are missing), load and activate the appropriate NE database
object for the BSS. Use the Database Management - Load Database
menu option of Load Management available from the GUI front panel.
Reset the BSS to begin downloading the BSS software and database
from the OMC-R. Refer to OMC-R Online Help, Network Operations.

If the BSS is already operational (software load and NE database

object are LAN loaded), upload the NE database object. Use the Load
Mgt - Upload object menu option in the Navigation Tree. Monitor the
upload status. Refer to OMC-R Online Help, Network Operations for
further details.

Rlogin to the BSS, see Remotely logging in to a BSS site from the
OMC-R on page 1-39. If the BSS name appears, and the rlogin is
successful, then NE.MAP has been configured properly.

4-3
Jan 2010

Overview procedure for adding BSS/RXCDR to the network

Chapter 4: Configuring a BSS/RXCDR

Performing an audit
Now an audit should be performed for the BSS/RXCDR. To perform the audit follow these steps:

Procedure 4-2 Perform an audit for the BSS/RXCDR

1

Initiate an audit of the BSS/RXCDR, using Audit Scheduler from the

Admin icon on the GUI front panel. Create a new Audit for the new
BSS, using One-shot/Apply to OMC-R. See Introduction to auditing
on page 10-2 for further details.

Once the audit is completed, verify that the destination point code and
originating point code are set correctly. Otherwise the BSS is unable
to communicate properly with the MSC. Use the BSS Detailed View
Signaling Information grouping to check.

Verify all SITEs and cells have been audited properly.

Verifying information
Verify the BSS/RXCDR settings using the following procedure:

Procedure 4-3 Verify RSS.RXCDR settings

1

Verify that the Statistics collection interval matches that set for the
OMC-R, using the BSS Detailed View General grouping to check BSS
setting.

NOTE
At the OMC-R, if PM_HOURLY_STATS environment variable
is not set for the system processor, then the default collection
interval is 30 minutes. Access is by:
cd/usr/omc/config/global
grep PM_HOURLY_STATS *
2

If necessary, change the SITE names. Refer to Reparenting a BSS on

page 4-100.

Verify that all SITEs under the BSC have come into service, using the
TTY command: state 0 site * *

NOTE
Some sites may be dummy sites, and may be D-U or D-L.

4-4

Verify that the raw statistics files are being uploaded for the BSS, using
the Event window to monitor for filetransferCompletedEvents. Refer to
OMC-R Online Help, Network Operations for further details.

Verify that the PM reports are available for the BSS. Refer to OMC-R
Online Help, Network Operations for further details.

If necessary, edit the appropriate subscription lists to add the new

BSS to them. Refer to OMC-R Online Help, Network Operations for
further details.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Overview procedure for adding BSS/RXCDR to the network

Configuring connectivity
The next stage is to configure connectivity. Configure BSS to RXCDR connectivity. From
Network Operator System Engineering Drawings, identify the RXCDRs connecting to the BSS.
Create the RXCDR - Associated BSS objects, filling in the appropriate 2 Mbit/s link information.

Checking the maps

Use the following procedure to check the maps:

Procedure 4-4 Check maps

1

If using the Map feature, when a new BSS/RXCDR is added, a new

default map is created for the BSS/RXCDR. The NEs are incorrectly
positioned on this new default map. Before storing the updated MIB
data in backup files, select the new BSS from the map list and then
select Organize Nodes menu option to reposition the BTSs. Then move
the nodes to required positions on the map background. Refer to
OMC-R Online Help, Network Operations for a description of how to
move the NEs on a map.

If using the Map feature, the network map now has a new node added
that corresponds to the new BSS/RXCDR. Open the network map
from the GUI and move the new node to the required position on the
map background. When the NEs are in the required position, save
the network map and the new default map. Select File Save from
the menu bar to save a map. Refer to OMC-R Online Help, Network
Operations for a description of how to move the NEs on a map.

If using the Map feature, add Commslinks from the BSS to devices such
as RXCDRs, OMC-R and MSC, so that they are displayed on the map.
Refer to Adding and deleting a map link on page 13-11 in Chapter 13.

If using the Map feature, add the BSS to any customized regional maps.

Making backups
The final stage is to make backups. Store the following updated MIB data in backup files:

BSS object.

NE Software object.

SITE names.

All Map data.

Updated RXCDR connectivity information.

68P02901W17-T

4-5
Jan 2010

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Creating a BSS using the OMC-R GUI

Introduction to creating a BSS using OMC-R GUI

The BSS object class in the OMC-R GUI is used to hold BSS-wide information within the BSS.
This section describes how to create and modify a BSS using the OMC-R GUI.

Prerequisites to creating a BSS

A BSS should be created in the OMC-R GUI before physically connecting it to the OMC-R. It can
only be created if a Network (that is, the parent) has been defined in advance.
Before creating a BSS, Commslinks from it to devices such as RXCDRs, OMC-R and MSC should
have been created.

NOTE
A BSS that supports the GPRS feature can only be created if the gprsOpt parameter
is unrestricted.

4-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Creating a BSS using the OMC-R GUI

To create a BSS using the OMC-R GUI, use the following procedure:

Procedure 4-5 Create BSS using OMC-R GUI

Navigate to and select the BSS class button in the Navigation Tree. If
necessary, see Navigating to a network object class or instance on page
1-28 for further details. The BSS class button changes color.

From the menu bar, select Edit Create. The OMC-R displays the
initial BSS Detailed View in Create mode, see Figure 4-1.

Click the Initial Software Load button to display a Software Inventory

Dialog window.

Double-click one of the software loads displayed to select it and enter

it in the initial BSS Detailed View.

Click the Initial Patch Level button to display the Initial Patch Level
Details Dialog window.

NOTE
The initial patch level is set to the default patch level if there
is a patch object contained in the software load selected.
Otherwise 0 is displayed.
6

Double-click one of the patch levels displayed to select it and enter it

in the initial BSS Detailed View.

NOTE
The initial patch level can only be selected if there is a patch
object contained in the software load.

68P02901W17-T

Select Options Initialize Form from the BSS Detailed View menu bar.
The OMC-R displays the complete BSS Detailed View window.

Complete the fields in the Detailed View as required. See BSS

Detailed View fields for details.

Select File Create from the menu bar.

10

Select File Close from the menu bar to close the Detailed View.

4-7
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Figure 4-1

Initial BSS Detailed View in Create mode

ti-GSM-InitialBSSDetailedViewinCreatemode-00780-ai-sw

BSS Detailed View fields

The following sections list and briefly describe the parameter fields in the BSS Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

4-8

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Identification grouping
Table 4-1 describes the fields in the Identification grouping of the BSS Detailed View.

Table 4-1 BSS Detailed View fields - Identification grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Name

Unique BSS name.

Up to 31
characters
plus the NULL
character.

Mandatory.

RDN Class

The object class identifier.

Default is BSS.

Optional.

Network Entity Id

Automatically set to the next

available network element
identifier. See Dynamic Allocation
of RXCDR-BSC Circuits (DARBC)
on page 2-13 for details.

1 - 254

Mandatory.

NMC RDN Value

The OMC-R supports an interface

to a Network Management Centre
(NMC). This is the instance
identifier of the object on the
NMC interface.

4 - 11 digits.

Optional.

Parent Detailed View

Click to display the parent

Network Detailed View.

OMC/NE Load
Version

Version number of the software

load active in the Network
Element.

OMC/NE Load
Version Create Time

Date and time at which the

current NE load was created.

Mandatory.

Initial Software Load

Initial Software Load installed

when NE was created.

Mandatory.

Local Maintenance
local_maintenance

Can be set to Yes to warn

operators that the BSS is out of
service. See Recommendations
for Configuration Management on
page 1-2 for further information
on how to set this parameter.

Yes (1) or No
(0). Default
is Yes (1).

Mandatory.

BSC Configuration
Type
bsc_type

The BSC configuration type. This

attribute has no function at an
RXCDR.

0-3.
0 = Non
Abis, Type 0.
1 = Non-Abis,
Type 1.
2 = Non-Abis,
Type 2
3 = Abis,
Type 0.
Default is
Non-Abis,
Type 0 (0)

Mandatory.

Not applicable.
4 - 11 digits.

Mandatory.

Continued

68P02901W17-T

4-9
Jan 2010

BSS Detailed View fields

Table 4-1

Chapter 4: Configuring a BSS/RXCDR

BSS Detailed View fields - Identification grouping (Continued)

Field name/BSS
parameter name
Transcoding
local_transcoding

Brief description

Values

Whether transcoding is performed

locally at the BSC, or remotely at
one or more RXCDR. See Dynamic
Allocation of RXCDR-BSC Circuits
(DARBC) on page 2-13 for details.

Local (1) or
Remote (0).
Default is 0.

Mandatory or
Optional?
Mandatory.

Additional information
Use the Additional Information window to input any notes relating to this BSS. Where additional
notes are not required, close this field by clicking the toggle button next to the Additional
Information header.

State grouping
The OMC-R updates the state parameter fields and shows the current status of the object. A
user cannot update any of the fields in this section. When an object is being created, these
fields are not up-to-date. Only when an object has been created, does the OMC-R keep these
fields up-to-date.
Table 4-2 describes the fields in the State grouping of the BSS Detailed View.

Table 4-2 BSS Detailed View fields - State grouping

Field name
Operational State

Brief description

Values

The operational state of the NE.

0 - 3.
UNDEFINED
(0),
DISABLED (1),
ENABLED (2),

Mandatory or
Optional?
Optional.

BUSY (3).
Administration State

The administration state of the

NE.

Reason Code

The reason code why the state

changed.

Time of Last Transition

The time of the last state

transition.

0 - 5.
UNDEFINED
(0),
NOT
EQUIPPED (1),
EQUIPPED (2),
LOCKED (3),
UNLOCKED (4),
SHUTTING-DOWN
(5).
0 - 65535.

Optional.

Optional.
Mandatory.

Continued

4-10

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Table 4-2 BSS Detailed View fields - State grouping (Continued)

Field name

Brief description

Values

Mandatory or
Optional?

Time of Last Audit

Gather Complete
timeOfLastAuGather
Complete

The date and time when the

Audit (Gather phase) of the
device was last performed.

Date and time

- in the format
ddmmyy hh:mm.

Read-only.

Time of Last Audit Apply

Complete
timeOfLastAuApply
Complete

The date and time when the

audit (apply phase) of the
device was last performed.

Date and Time

- in the format
ddmmyy hh:mm

Read-only.

Other State grouping

fields:
Last OMC Administrator
(not shown in BSS
Detailed View)

The username of the last OMC

administrator to modify the
state of the object through a
Device Management action
such as Lock, UnLock.

Related Device (not

shown in BSS Detailed
View)

The identifiers of any related

devices.

Mandatory.

Optional.

Network Addresses grouping

Table 4-3 describes the fields in the Network Addresses grouping of the BSS Detailed View.

Table 4-3 BSS Detailed View fields - Network Addresses grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Network Element X.121

Address

Must be unique. The other

X121 addresses in the Network
Address grouping are read from
the DTE X.121 addresses at the
OMC-R on page 5-17 file.

1 - 14
characters

Mandatory.

OMC X.121 Event

Address 1 OMC X.121
Event Address 2

The OMC-R's first and second

Event Virtual Circuit X.121
address stored in the Network
Element's Non Volatile RAM.
Only necessary to complete the
first OMC-R X.121 Event Address
1 (always nnnnnnnn03) to create
the NE. The rest of the DTE
addresses are set through Audit.

1 - 14
characters

Mandatory.

OMC X.121 Download

Address 1 OMC X.121
Download Address 2

The OMC-R's first and second

Download Virtual Circuit X.121
address stored in the Network
Element's Non Volatile RAM.

0 - 14
characters

Mandatory.

Continued

68P02901W17-T

4-11
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Table 4-3 BSS Detailed View fields - Network Addresses grouping (Continued)
Field name/BSS
parameter name

Mandatory or
Optional?

Brief description

Values

OMC X.121 Remote

Login Address

The OMC-R's Remote Login

Virtual Circuit X.121 address
stored in the Network Element's
Non Volatile RAM.

0 - 14
characters

Mandatory.

OMC X.121 Upload

Address

The OMC's Upload Virtual Circuit

X.121 address stored in the
Network Element's Non Volatile
RAM.

0 - 14
characters

Mandatory.

OMC X.121 Spare

Address (two fields)

The OMC-R's Spare Virtual

Circuit X.121 address stored
in the Network Element's Non
Volatile RAM.

0 - 14
characters

Mandatory.

CBC X.121 Address

Cell Broadcast Center (CBC)

X.121 address.

0 - 14
characters

Mandatory.

BSC CBC X.121 Address

bsc_cbc

X.121 address at the BSC used

to communicate with the Cell
Broadcast Center (CBC).

0 - 14
characters

Mandatory.

Optional Features grouping

Table 4-4 shows the fields in the Optional Features grouping. These fields show whether an
optional BSS feature is unrestricted (Enabled (1)) or restricted (Disabled (0)). All fields are
Read Only (RO) and cannot be modified by a user.

Table 4-4 BSS Detailed View fields - Optional Features grouping

Field name/OMC-R parameter
name

Brief description

Frequency Hopping Baseband

Feature
basebandHopOpt

See Frequency hopping on page 2-4 for details.

Concentric Cells Feature

concentricCellOpt

Affects the ability of the system to process a request to

configure Concentric Cells.

Preventative Cyclic
Retransmission Feature
cycRetranPrevOpt

See Preventive Cyclic Retransmission (PCR) on page 2-56

for details. If disabled, the BSS parameters pcr_enable,
pcr_n1, pcr_n2 cannot be used.

Daisy Chaining Feature

daisyChainOpt

If this feature is restricted, the creation of non-spoke PATH

instance is not allowed.

Receiver Spatial Diversity

Feature
diversityOpt

If this feature is unrestricted (enabled), the DRI

diversity_flag can be used (see Table 9-17).

Extended GSM 900 Feature

egsmOpt

If this feature is unrestricted (enabled), the CELL parameter

egsm_ho_thresh can be used (see Table 8-19).
Continued

4-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 4-4

BSS Detailed View fields

BSS Detailed View fields - Optional Features grouping (Continued)

Field name/OMC-R parameter

name

Brief description

Extended Range Cell Feature

ercOpt

If this feature is unrestricted (enabled), the CELL parameter

ext_range_cell can be used (see Table 8-2).

A and Um Interface - GSM

Phase 2 Feature
gsmPhase2Opt

Whether the A and Um Interface feature is restricted. See

System Information: GSM Overview (68P02901W01) for a
description of this feature. Also see Table 4-7 for related
BSS parameters.

GSM Half Rate

gsmHalfRateOpt

See GSM Half Rate on page 2-140 for details.

Heterogeneous Cabinet
Feature
heteroCabFreqOpt

Whether the Heterogeneous Cabinet Feature is restricted.

Cannot be enabled without homoCabFreqType also being
enabled.

Homogeneous Cabinet Feature

homoCabFreqOpt

Whether the Homogeneous Cabinet Frequency Type is

restricted.

MultiBand Inter-Cell H/O

Feature
mbInterCellHoOpt

See Configuring enhanced SDCCH to TCH band assignment

on page 8-198 and Configuring a cell for coincident
multiband handovers on page 8-181 for details. Also see
Table 8-10 CELL Detailed View Congestion Relief parameter
grouping.

MicroCell Feature
microcellOpt

Whether the Microcell feature is restricted. See Table 8-29,

Table 8-48 and Table 8-49 for associated parameters.

Multiple Encryption Feature

multiEncryptOpt

Whether the Multiple Encryption feature is restricted. See

Table 4-6 for related parameters. Also see Encryption
algorithms on page 2-26 and Technical Description: BSS
Implementation (68P02901W36) for details of this feature.

Add Nail Connections Feature

nailConnectsOpt

Whether the Add Nail Connections feature is restricted. See

Technical Description: BSS Implementation (68P02901W36)

for details of this feature.

Reserved Timeslot Feature

resTimeslotOpt

Whether the Reserved Timeslot feature is restricted. See

Technical Description: BSS Implementation (68P02901W36)

for details of this feature.

Sub-equipped RTF Feature

rtf_capacityOpt

Whether the Sub-equipped RTF feature is restricted. See

Technical Description: BSS Implementation (68P02901W36)

for details of this feature.

RTF PATH Fault Containment

Feature
RTFPathEnableOpt

Whether the RTF PATH Fault Containment feature is

restricted. See Technical Description: BSS Implementation
(68P02901W36) for details of this feature.

16 kbit/s LAPD RSL Feature

rsl_rateOpt

Whether the 16 kbit/s LAPD RSL RTF feature is

restricted. See Technical Description: BSS Implementation
(68P02901W36) for details of this feature.

Alternative Congestion Relief

Feature
congestReliefOpt

Whether the Alternative Congestion Relief feature is

restricted. See Table 8-10 and Table 8-50 for details of the
Cell and Neighbor Detailed View fields associated with
this feature. Also see System Information: GSM Overview
(68P02901W01) for a description of this feature.
Continued

68P02901W17-T

4-13
Jan 2010

BSS Detailed View fields

Table 4-4

Chapter 4: Configuring a BSS/RXCDR

BSS Detailed View fields - Optional Features grouping (Continued)

Field name/OMC-R parameter

name

Brief description

Directed Retry Feature

directedRetryOpt

Whether the Directed Retry feature is restricted. See

Table 4-11, Table 8-11 and Table 8-50 for details of the BSS,
cell, and neighbor parameters associated with this feature.
Also see Technical Description: BSS Implementation
(68P02901W36) for details of this feature.

SMS Cell Broadcast Feature

smsCellBroadOpt

See Short Message Service - Cell Broadcast on page 2-45

for details.

SMS Point to Point Feature

smsPntToPntOpt

See Short Message Service - Point-To-Point on page 2-53

for details.

Frequency Hopping
Synthesizer Feature
synthHoppingOpt

See Frequency hopping on page 2-4 for details.

SMS Service Centre Feature

smsServCenterOpt

Whether the SMS Service Centre feature is restricted.

Affects the ability of the system to process a request to
equip/create a CBL.

Aggregate Abis Feature

aggAbisOpt

Whether the Aggregate Abis feature is restricted. If this

attribute is enabled, the link attributes in the Path Managed
Object between a BSC and a BTS can have a TS-Switching
site. See Technical Description: BSS Implementation
(68P02901W36) for details of this feature.

Integrated M-Cell HDSL

Feature
hdslOpt

Whether Integrated M-Cell HDSL feature is restricted.

See site Detailed View HDSL Information grouping,
and Table 9-47 for detailed of the site and MSI fields
associated with this feature. See Technical Description: BSS
Implementation (68P02901W36) for details of this feature.

GPRS Feature
gprsOpt

Whether GPRS feature is restricted. See the GPRS

parameter groupings of the BSS, Cell, and site Detailed
Views for detailed of the associated parameters. Also see
System Information: GSM Overview (68P02901W01) for a
description of this feature.

EGPRS Feature
egprsOpt

Whether EGPRS feature is restricted. See GPRS and

EGPRS coding schemes on page 2-39 for details of
configuring EGPRS Coding Schemes. See the GPRS
parameter groupings of the BSS, Cell and site Detailed
Views for detailed of the associated parameters. Also see
System Information: GSM Overview (68P02901W01) for a
description of this feature.

Dual Band Cells Option

dualBandCellOpt

See Dual band cells option on page 2-28 for details.

HorizonMicro/HorizonCompact
Feature
HorizonMicCom2Opt

Whether the HorizonMicro/HorizonCompact feature is

restricted.

ECERM Feature
ecermOpt

See Enhanced Circuit Error Rate Monitor (ECERM) on page

2-70 for details.
Continued

4-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 4-4

BSS Detailed View fields

BSS Detailed View fields - Optional Features grouping (Continued)

Field name/OMC-R parameter

name

Brief description

ALM Enhancement for EGSM

Carriers
AlmEgsmOpt

See Advanced Load Management for EGSM on page 2-78

for details.

Network Controlled Cell

Reselection Feature
nccrOpt

See Network Controlled Cell Reselection on page 2-81 for

details.

Coding Scheme 3 and 4

cs34Opt

See GPRS and EGPRS coding schemes on page 2-39 for

details.

Enhanced BSC Feature

ebscOpt

See Enhanced BSC Capacity on page 2-94 for details.

Enhanced One Phase Access

Feature
eopOpt

See Enhanced GPRS One Phase Access on page 2-113 for

details.

Inter-RAT Handover Feature

InterRatOpt

See Inter-Radio Access Technology (Inter-RAT) Handover on

page 2-95 for details. Whenever EnhncdInterRatOpt is set
to 1, InterRatOpt is also set to 1.

XBL 16 kbit/s LAPD Feature

xbl_rateOpt

Whether the XBL 16 kbit/s LAPD feature is restricted. See

Table 9-68 for details of the XBL parameters associated with
this feature.

PBCCH/PCCCH Feature

See PBCCH/PCCCH feature on page 2-117 for details.

Enhanced Full Rate Feature

EFROpt

Whether the Enhanced Full Rate feature is restricted. See

Table 4-13 for the associated parameters. Also see Technical
Description: BSS Implementation (68P02901W36) for
details of this feature.

GDP Volume Control Feature

gdpVolContOpt

Whether the GDP Volume Control feature is restricted.

Determines whether the BSS and Assoc_BSS parameter
volume_control_type can be used (see Table 4-7
and Table 4-30). Also see Technical Description: BSS
Implementation (68P02901W36) for details of this feature.

Fast GCLK Warm Up Feature

FastWarmGclkOpt

Whether the Fast GCLK Warm Up feature is restricted.

Determines whether the site parameter gclk_qwarm_flag
can be used (see Table 7-5).

Location Services Feature

lcsOpt

See GSM location services on page 2-104 for details.

GPRS Trace Feature

gprsTraceOpt

Whether the GPRS Trace feature is enabled or disabled.

See OMC-R Online Help, Network Operations for details of
this feature.

AMR Feature
amrOpt

See Adaptive Multi-Rate (AMR) on page 2-129 for details.

AMR Enhanced GDP Feature

amrEGDPProOpt

See Adaptive Multi-Rate (AMR) on page 2-129 for details.

Grayed-out if the AMR Feature (amrOpt) is restricted
(Disabled).
Continued

68P02901W17-T

4-15
Jan 2010

BSS Detailed View fields

Table 4-4

Chapter 4: Configuring a BSS/RXCDR

BSS Detailed View fields - Optional Features grouping (Continued)

Field name/OMC-R parameter

name

Brief description

AMR Enhanced Capacity

Feature
amrEnhancedCapOpt

See Adaptive Multi-Rate (AMR) on page 2-129 for details.

AMR TCU-A Feature

amrTCUAOpt

See Adaptive Multi-Rate (AMR) on page 2-129 for details.

AMR TCU-B Feature

amrTCUBOpt

See Configuring a network instance on page 3-2 for details.

GPRS Seamless Cell

Reselection Feature
scrOpt

See GPRS Seamless Cell Reselection on page 2-142 for

details.

Increased PRP Capacity

Feature Supported
prp_capacity_opt

See Enhanced Scheduling on page 2-146 for details. This

feature can only be enabled if GPRS is enabled.

Intelligent Multilayer Feature

imrmOpt

Whether the Intelligent Multilayer Resource Management

feature is restricted. See for further details.

Fast Call Service Feature

FastCallOpt

Whether the Fast Call Service feature is restricted or

unrestricted. See Fast Call Setup on page 2-168 for further
details.

Enhanced Inter RAT Handover

Feature
EnhancedInterRatOpt

Where the Enhanced Inter RAT Handover feature has

been restricted. Whenever EnhncdInterRatOpt is set to
1, InterRatOpt is also set to 1. See Enhanced Inter-RAT
Handover feature on page 2-96 for further details.

Network Assisted Cell Change

Feature
naccOpt

Whether the Network Assisted Cell Change feature is

restricted (disabled) or unrestricted (enabled). See Network
Assisted Cell Change (NACC) on page 2-162 for further
details.

EMLPP Feature
enhancedMLPPOpt

Whether the Enhanced Multi-Level Precedence and

Preemption (eMLPP) is restricted or unrestricted for the
BSS. See Enhanced Multi-level Precedence and Pre-emption
(eMLPP) on page 2-165 for further details.

Quality of Service
qosOpt

Whether Quality of Service feature is restricted or

unrestricted. See Quality of Service (QoS) on page 2-154
for further details.

VersaTRAU Feature
versaTrauOpt

Displays whether the VersaTRAU feature is restricted

(Disabled (0)) or unrestricted (Enabled (1)). See VersaTRAU
on page 2-172 for further details.

Signaling Information grouping

Table 4-5 describes the fields in the Signaling Information grouping of the BSS Detailed View.

4-16

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Table 4-5 BSS Detailed View fields - Signaling Information grouping

Field name/BSS
parameter name

Mandatory
or
Optional?

Brief description

Values

Establishes a method of
differentiation between international
and national messages.

0 - 3.
International
Network (0),
Spare (for
international
use only) (1),
National
Network (2),
Reserved for
national use (3).
Default is 2.

Mandatory.

Originating Point
Code

0 - 16777215.
0 - 16777215,
if ss7_mode
is ANSI SS7.
0 - 16383, if
ss7_mode is not
ANSI SS7.

Mandatory.

Destination Point
Code

0 - 16777215.
0 - 16777215,
if ss7_mode
is ANSI SS7.
0 - 16383, if
ss7_mode is not
ANSI SS7.

Mandatory.

Network Indicator
Code

Called Point Code

Included

Whether point code is included

(enabled) in called party (call
receiver) address in the SCCP
messages.

Disabled (0) or
Enabled (1).

Mandatory.

Calling PCI

Whether point code is included in

calling party (call originator) address
in the SCCP messages.

Disabled (0) or
Enabled (1).

Mandatory.

Connection
Request Calling

Whether calling party address is

included in the SCCP message
Connection Request.

Disabled (0) or
Enabled (1).
Default is 0.

Mandatory.

Preventative
Cyclic
Retransmission
Enable
pcr_enable

Whether Preventative Cyclic

Retransmission (PCR) is enabled
or disabled as an error correction
scheme for the MSC-BSC A-interface.
See Preventive Cyclic Retransmission
(PCR) on page 2-56 for further
details.

Disabled (0) or
Enabled (1).
Default is 0.

Mandatory.

Continued

68P02901W17-T

4-17
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Table 4-5 BSS Detailed View fields - Signaling Information grouping (Continued)
Field name/BSS
parameter name

4-18

Brief description

Mandatory
or
Optional?

Values

Preventative
Cyclic
Retransmission
N1
pcr_n1

See Preventive Cyclic Retransmission

(PCR) on page 2-56 for further
details.

Mandatory.

Preventative
Cyclic
Retransmission
N2
pcr_n2

See Preventive Cyclic Retransmission

(PCR) on page 2-56 for further
details.

Mandatory.

SCCP BSSAP
Management Flag

When enabled, detects Signaling

Point Inaccessible, and loss of
BSSAP subsystem, and handles
the following messages: User Part
Unavailable (UPU), Subsystem
prohibited (SSP), Subsystem Allowed
(SSA), and Subsystem Test (SST).
When disabled, the BSS responds to
an SST with an SSA message.

SS7 Mode
ss7_mode

Indicates which SS7 definition is

supported.

BSSAP Subsystem
Number

Disabled (0) or
Enabled (1).
Default is 0.

Mandatory.

SS7 defined by
CCITT (0) or SS7
defined by ANSI (1).
Default is 0.

Mandatory.

The BSS AP subsystem number.

0 - 255.
Defaults to 254.

Mandatory.

STP PC
stp_pc_enabled

Used for enabling the stp_pc.

Disabled (0) or
Enabled (1).
Default is 0.

Mandatory.

STP Point Code

stp_pc

The STP (signaling transfer point)

point code. This point code should
be used by MTPL3 and not by SCCP.
Only used when stp_pc_enabled is
1.

0 - 16777215.
0 - 16777215 if
ss7_mode is ANSI
SS7.0 to 16383 if
ss7_mode is not
ANSI SS7.

Mandatory.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

A5 Algorithms grouping
Table 4-6 describes the fields in the A5 Algorithms grouping of the BSS Detailed View.

Table 4-6 BSS Detailed View fields - A5 Algorithms grouping

Field name/BSS parameter
name

Mandatory or
Optional?

Brief description

Values

A5 Algorithm Priority 1

The A5 encryption algorithm

with priority 1 (highest) to
be used by the BSS.

0 - 7.
Default is 0 (No
Encryption).

Mandatory.

A5 Algorithm Priority 2 - 7

As above but for Priority 2 to

7.

0 - 7.
Default is null.

Optional.

A5 Algorithm Priority 8

No encryption algorithm
associated.

0 or null.
Default is null.

Optional.

Encryption Algorithm A5/1

to 7 Allowed
option_alg_a5_1 to 7

These fields enable or disable

encryption algorithm A5/1 to
7.
multiEncryptOpt must be
enabled.

Disabled (0) or
Enabled (1).
Default is
Disabled (0).

Mandatory.

General grouping
Table 4-7 describes the fields in the General grouping of the BSS Detailed View.

Table 4-7 BSS Detailed View fields - General grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory
or Optional?

Land Layer 1 Mode

The layer 1 mode of the land network

TELCO connection type.

CEPT
(E1) (0).
Default is 0.

Mandatory.

MMS Critical Alarm

Threshold Enable

Turns the MMS critical alarm threshold

(cat) on or off. When enabled, takes the
MMS out of service if it goes in and out
of service ten times within a ten-minute
period.
If disabled, keeps the MMS in service
even if it goes in and out of service ten
times in a ten minute period.

Disabled
(0) or
Enable (1).
Default is 0.

Mandatory.

XCDR Downlink
VAD/DTX Enable

Whether downlink Voice Activity

Detection/Discontinuous Transmission
(VAD/DTX) is enabled.

Disabled (1)
or VAD/DTX
Enable (0).
Default is 0.

Optional.

XCDR MSC Quiet

Tone

Identifies a generated tone which is

transmitted over a traffic channel when
a voice is not being transmitted.

0 - 255
(Number
identifying
the tone).
Default is 0

Mandatory.

Continued

68P02901W17-T

4-19
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Table 4-7 BSS Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

Brief description

Statistics Interval

The time in minutes in which the

statistics file should be reported.

OML X.25 Layer 3

Packet Size

Mandatory
or Optional?

Values
5 - 60 (in
minutes).
Default is 30

Mandatory.

Used to negotiate the Packet Size in the

X.25 Call Request Packet.

128, 256
or 512.
Default is
128

Mandatory.

OML X.25 Layer 3

Window Size

Used to negotiate the Window Size in

the X.25 Call Request Packet.

2 - 7.
Default 2.

Mandatory.

Illegal Circuit ID

An identifier to describe a circuit that

is never used. It is used as an internal
placeholder in call processing to show
that no circuit has been assigned to a
call.

0 - 65535.
Default is 0.

Mandatory.

Cipher Mode Reject

Message Allowed
ciph_mode_rej
_allowed(OMC-R
parameter name:
ciphModeRejAllwd)

Whether the Cipher Mode Reject

message is sent to the MSC. Generated
when the Cipher Mode Command
message from the MSC specifies
ciphering that the BSS or MS is unable
to perform. Only used if the BSS optional
feature gsmPhase2Opt is unrestricted.

Cipher
Mode Reject
message is
not sent (0)
or Cipher
Mode Reject
message is
sent (1)

Mandatory.

Confusion Message
Allowed
confusion_msg
_allowed(OMC-R
parameter name:
confusionMsgAllwd)

Whether the BSS sends Confusion

messages over the A-interface when an
erroneous message is received from
the MSC. If disabled, an alarm is sent
instead to the MSC. Only used if the
BSS optional feature gsmPhase2Opt is
unrestricted.

Disabled
(0) or
Enable (1).
Default is 0.

Mandatory.

Reset Circuit
Message Flag

Whether the Reset Circuit message is

sent to the MSC.

Message not
sent (0), or
Message
sent (1).
Default is 0.

Mandatory.

Radio Resource
Status Flag

Whether a RR status message is sent to

the mobile. The RR status message is
sent to report certain error conditions in
the messages received from the mobile.

Disabled
(0) or
Enabled (1).
Default is 0.

Mandatory.

Downlink Audio Level

Offset
dl_audio_lev_offset
(OMC-R parameter
name:
dlAudioLevOff)

The audio downlink volume control.

Affects background and comfort noise,
not data.

-15 to 15
(in dB)
Default is 0.

Mandatory.

Continued

4-20

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Table 4-7 BSS Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

Mandatory
or Optional?

Brief description

Values

Uplink Audio Level

Offset
ul_audio_lev_offset
(OMC-R parameter
name:
ulAudioLevOff)

The audio uplink volume control. Affects

background and comfort noise, not data.

-15 to 15
(in dB)
Default is 0.

Mandatory.

Global Reset
Repetitions
global_reset
_repetitions(OMC-R
parameter name:
globalResetReps)

Allows the reset procedure to continue

indefinitely, or stops the procedure
after a fixed number of repetitions. The
global reset procedure is only repeated
if the MSC fails to acknowledge the BSS.
Only used if the BSS optional feature
gsmPhase2Opt is unrestricted.

0 - 255
(number of
repetitions)
Default is 0.

Mandatory.

Group Block Unblock

Allowed
group_block
_unblock_allowed
(OMC-R parameter
name:
grpBlkUnblkAllwd)

Allows the A-interface to be more

efficient by enabling support of the
group blocking/unblocking procedure
if MSC supports circuit group block
and circuit group unblock messages.
Only used if the BSS optional feature
gsmPhase2Opt is unrestricted.

Disabled
(0) or
Enable (1).
Default is 0.

Mandatory.

GSM Cell ID Format

gsm_cell_id_format

The format of the GSM cell id sent by

the BSS to the MSC.

0 - 2.
Whole
CGI (0),
(LAC) and
CI (1),
or CI (2).
Default is 1.

Max Reset Circuit

Timer Expirations

Number of times the reset

circuit message is repeated if an
acknowledgment is not received from
the MSC.

0 - 100
(number of
repeats).
Default is 1.

Mandatory.

Phase 2 Classmark
Allowed

The format of the classmark parameter

sent to the MSC based on GSM phases.

Formatted
for Phase
1 (0),
Formatted
for Phase
2 (1),
Formatted
for Phase
2 with
MultiBand
(2)
Default is 0.

Mandatory.

(OMC-R parameter
name:
gsm_cell_id_fmt)

Mandatory.

Continued

68P02901W17-T

4-21
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Table 4-7 BSS Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

Brief description

Mandatory
or Optional?

Values

Phase Resource
Indication
phase2_resource
_ind_allowed(OMC-R
parameter name:
phase2ResIndAllwd)

The format used to send Resource

Indication messages to the MSC.
Only used if the BSS optional feature
gsmPhase2Opt is unrestricted.

GSM Phase 1
format (0) or
GSM Phase
2 format (1).
Default is 0.

Mandatory.

SSM Critical
Overload Threshold

The usage of call information blocks, as

expressed by the ratio of the number of
active calls to the maximum number of
calls the SSM can handle (250).

0 - 100
(Percentage
of Call
Information
Blocks
in Use).
Default is 80.

Mandatory.

SSM Normal
Overload Threshold

The usage of call information blocks, as

expressed by the ratio of the number of
active calls to the maximum number of
calls the SSM can handle (250). Every
time the usage equals or exceeds this
threshold, one access class is barred.

0 - 100.
Default is 70.

Mandatory.

Site Statistics Process

Burst Delay

The delay between bursts of messages

sent from the Site Statistics Process
(SSP) to the Central Statistics Process
(CSP).

0 - 2500
(in ms).
Default is
200.

Mandatory.

Site Statistics Process

Burst Limit

Number of messages Site Statistics

Process (SSP) can forward to Central
Statistics Process (CSP) in one burst.

1 - 65535
(number of
messages).
Default is 10.

Mandatory.

Unequipped Circuit
Allowed
unequipped_circuit
_allowed(OMC-R
parameter name:
uneqCctAlld)

Determines if, when a message arrives

from the MSC specifying a terrestrial
circuit that is not equipped, an
unequipped circuit message is sent
to the MSC. Alternatively, an alarm is
generated. Only used if the BSS optional
feature gsmPhase2Opt is unrestricted.

0 - 2.
Send alarm
to OMC (0),
Send
message to
MSC (1),
Send alarm
to OMC and
message to
MSC (2).
Default is 0.

Mandatory.

Continued

4-22

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Table 4-7 BSS Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

Brief description

Values

Mandatory
or Optional?

Call Traces Options

Reserved space for MSC-initiated

Call Traces in the BSS, or to block
MSC-initiated Call Traces. The values
are specified as a percentage of traces
reserved per LCF.

0 - No space Mandatory.
reserved for
MSC-initiated
Call Traces.
1 to 100 Percentage
of space
reserved for
MSC-initiated
Call Traces.
255 MSC-initiated
Call Traces
blocked.
Default is 0.

Override Intra Bss

Pre Transfer

Whether SSM should send a pre-transfer

request to SM when the handover
allocation message is received during an
inter-cell handover.

Send (0)
or Do not
send (1).
Default is 0.

Mandatory.

Current Channel in
HO Required Msg

Determines if the optional element

current channel is included in the
Handover Required message to the
MSC.

Disabled
(0) or
Enabled (1).
Default is 0.

Mandatory.

CBL X.25 Layer 3

Packet Size

Used to negotiate the Packet Size in the

X.25 Call Request Packet.

128, 256
or 512.
Default is
128.

Mandatory.

CBL X.25 Layer 3

Window Size

Used to negotiate the Window Size in

the X.25 Call Request Packet.

2 - 7.
Default is 2

Mandatory.

RTF PATH Fault

Containment Status

Whether the functionality for the RTF

PATH Fault Containment Feature is
enabled or disabled.

Disabled
(0) or
Enabled (1).
Default is 0.

Optional.

Handover Reject
Message Required

Disables or enables the delivery of a

handover required reject message from
the MSC to the source BSS, in the event
that a target cannot be found for a
requested handover.

Reject
message not
required (0),
Reject
message
required (1)
Default is 1.

Mandatory.

Frequency Types
Allowed

Determines the values that can be used

for the Cabinet frequency_type and the
CELL frequency_type.

1 - 15.
Default is
PGSM900
(1).

Mandatory.

Continued

68P02901W17-T

4-23
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Table 4-7 BSS Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

Brief description

Mandatory
or Optional?

Values
CCDSP
Volume
Control (0),
GDP Volume
Control (1).
Default is 0.

Uplink and Downlink

Volume Control Type
volume_control
_type(OMC-R
parameter name:
volContType)

Cannot be changed if the GDP Volume

Control feature (gdpVolContOpt) is
restricted (disabled).

BSS EGSM ALM

Allowed
egsm_alm_allowed

See Advanced Load Management for

EGSM on page 2-78 for details.

MMI Cell ID Format

Format of the cell id accepted on the

MMI command line.

0 or 1.
7-Parameter
Cell Id
Format
Used On
Command
Line (0)
4-Parameter
Cell Id
Format
Used On
Command
Line.
Default is 0.

Mandatory.

Call Trace Msgs

Before Handover

The number of messages of each type of

handover data (RSS, Abis, and MS Power
Control) collected immediately before a
handover attempt has been completed,
when handover data is requested by the
operator.

0 - 8.
Default is 5.

Mandatory.

Call Trace Msgs After

Handover

The number of messages of each type of

handover data (RSS, Abis, and MS Power
Control) collected immediately after a
handover attempt has been completed,
when handover data is requested by the
operator.

0 - 8.
Default is 5.

Mandatory.

Second Assignment
Procedure

Whether Second Assignment Procedure

has been enabled at the BSS.

Enabled
(1) or
Disabled (0).
Default is
Disabled (0).

Optional.

MSC Overload
Control
bss_msc_overload
_allowed

See MSC to BSS overload control on

page 2-23 for further details.

Enabled
(1) or
Disabled (0).
Default is
Disabled (0).

Optional.

Update TSCs
tsc_update_method

See Propagating TSC updates on page

8-222 for further details.

Default is 0.

Optional.

Mandatory.

Optional.

Continued

4-24

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Table 4-7 BSS Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

Brief description

Values

Mandatory
or Optional?

Pool GPROC
Preemption

The preemption level for the pool

GPROC functions.

0 - 2.
No
replacement
(0),
Based on
Function
Priority (1),
Based on
Function and
Intra-function
priorities (2).
Default is 1.

Optional.

MTPL3 Signaling
Link Test

Whether the MTPL3 signaling link test is

enabled when the MTL comes in service.

Allowed
(1) or
Disallowed
(0).
Default is
Allowed (1).

Mandatory.

SCCP Inactivity
Control

Enables or disables the SCCP Inactivity

Control.

Enabled
(1) or
Disabled (0).
Default is
Enabled (1).

Mandatory.

MTL Loadshare
Granularity
mtl_loadshare
_granularity

See Modifying MTL loadsharing

granularity on page 9-155 for details.

Terminate RF when
Cell goes OOS
stop_dri_tx_enable

It takes time to stop RF transmission

in a cell after it has been OOS. To
avoid adding additional time to a
short cell outage (for example caused
by the momentary interruption of a
non-redundant RSL), this field allows
a user to specify the amount of time a
DRI should continue RF transmission
after the cell in which it is contained
goes OOS. If set to Yes (1), the DRIs
continue transmitting for the length of
time specified in stop_dri_tx_time before
transitioning to the D-U: CELL OOS
state. If set to No (0) (default), the DRIs
do not stop transmitting when the cell
goes OOS.

Optional.

0 or 1
where:
0 = No
1 = Yes.
Default is
No (0).

Mandatory.

Continued

68P02901W17-T

4-25
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Table 4-7 BSS Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

Brief description

Mandatory
or Optional?

Values

LMTL Loadshare
Granularity
lmtl_loadshare
_granularity

See Modifying LMTL loadsharing

granularity on page 9-134 for details.

MSC Release

The version of the MSC to which the

BSS is connected.

0 or 1,
where:
0 - Indicates
the MSC is
a release
'98 or older.
1 - Indicates
the MSC is
a release '99
or newer.

Optional.

Interzone PingPong
Allowed Count
zone_pingpong
_count

Indicates how many times zone

ping-pong handover is allowed during the
time in which the frequency of interzone
ping-pong handovers are measured (as
set by zone_pingpong_enable_win).

0 - 255.
Default is 3.

Optional.

Interzone PingPong
Enabled Timer
zone_pingpong
_enable_win

Indicates the length of time in which

the frequency of interzone ping-pong
handovers are measured (seconds).

0 - 255.
Default is 30.

Optional.

Interzone PingPong
Disabled Timer
zone_pingpong
_disable_win

Indicates the length of time during

which zone ping-pong handovers are
not allowed during the time in which
the frequency of interzone ping-pong
handovers are measured (as set by
zone_pingpong_enable_win) after
ping-pong handover has happened
zone_pingpong_count times.

0 - 255.
Default is 30.

Optional.

Preferred PingPong
Target Zone
zone_pingpong
_preferred_zone

Indicates which zone is preferred as the

hop target zone.

0 (outer zone
preferred),
1 (inner zone
preferred) or
255 (current
zone).
Default is
255.

Optional.

{34452} CStats BSS

Enabled
cstats_bss
_enabled

Used to enable or disable the function

of critical statistics uploading in
five-minute interval.

0 to 1.
Default is 0.

Optional.

{34452} Cage
Management Enabled
cage_manage
_enabled

Used to enable or disable the cage

management feature.

Range is
0 to 1.
Default is 1.

Optional.

Optional.

Continued

4-26

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Table 4-7 BSS Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name
{34452} AMR Home
Filter Enabled
amr_home_filter
_enabled

Mandatory
or Optional?

Brief description

Values

Specifies whether the AMR homing filter

is enabled or not.

Range is
0 to 1.
0disabled.
1enabled.
Default is 0.

Optional.

PCS 1900 Frequency grouping

Table 4-8 describes the fields in the PCS 1900 Frequency grouping of the BSS Detailed View.

Table 4-8 BSS Detailed View fields - PCS 1900 Frequency grouping
Mandatory or
Optional?

Field name

Brief description

Values

Address Indicator
bit 8

Specifies whether bit 8 of the

address indicator in a PCS
1900 is set or unset.

0 or 1.
Default is Unset
(0).

Mandatory.

PCS 1900 Frequency

Blocks

The PCS 1900 Frequency

Blocks which determine the
Absolute Radio Frequency
Channels (ARFCNs) that the
BSS is allowed to use for the
PCS 1900 frequency type.

Click buttons A
to F.

Mandatory.

Flash Information grouping

Table 4-9 describes the fields in the Flash Information grouping of the BSS Detailed View.

Table 4-9 BSS Detailed View fields - Flash Information grouping

Brief description

Values

Mandatory or
Optional?

Flash Information

Version information of the

current Flash EEPROM load.

4 - 11 digits.

Mandatory.

Flash Time

Date and time when current

Flash EEPROM load was
created.

Flash Checksum

Checksum value of the

current Flash EEPROM load.

-2147483648 2147483647.

Mandatory.

Flash Size

The size of the current Flash

EEPROM load.

-2147483648 2147483647.
Size in Bytes

Mandatory.

Field name

68P02901W17-T

Mandatory.

4-27
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Trunk Information grouping

Table 4-10 describes the fields in the Trunk Information grouping of the BSS Detailed View.

Table 4-10 BSS Detailed View fields - Trunk Information grouping

Field name

Values

Brief description

Mandatory or
Optional?

Trunk Critical
Threshold

Used to determine the severity

assignment of alarms and
maintenance actions affecting
trunks.

0 - 100
(Represents a
percent of the
capacity lost).
Default is 50.

Mandatory.

Trunk Major
Threshold

Used to determine the severity

assignment of alarms and
maintenance actions affecting
trunks.

0 - 99 (Represents
a percent of the
capacity lost).
Default is 10.

Mandatory.

CLM Timers grouping

This grouping contains all the CLM timers, such as BSSMAP_T20 (CLM_T20). See Maintenance
Information: BSS Timers (68P02901W58) for further details.

MTP Timers grouping

This grouping contains all the MTP timers, such as SS7_L2_T1 (Alignment Ready). See

Maintenance Information: BSS Timers (68P02901W58) and Preventive Cyclic Retransmission

(PCR) on page 2-56for details.

SSM Timers grouping

This grouping contains all the SSM timers, such as SCCP_TCONN_EST. See Maintenance

Information: BSS Timers (68P02901W58) for further details.

4-28

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Directed Retry grouping

Table 4-11 describes the fields in the Directed Retry grouping of the BSS Detailed View. Only
used when the Directed Retry BSS feature (directedRetryOpt) is unrestricted.

Table 4-11 BSS Detailed View fields - Directed Retry grouping

Field name/BSS
parameter name

Brief description

Mandatory
or
Optional?

Values

Directed Retry
Preference
dr_preference

Whether the MSC can

be involved when a
directed retry procedure
is necessary.

Enabled (1) or Disabled (0).

Default is 0.

Optional.

Directed Retry
Channel Mode
Modify
dr_chan_mode
_modify(OMC-R
parameter name:
dr_chan_mode_mod)

Whether a channel mode

modify procedure follows
a successful handover in
which the channel mode
changed.

Enabled (1) or Disabled

(0) (perform channel mode
modify procedure after a
handover for a Phase 1 MS
in which the channel mode
changed to full rate speech).
Default is 0.

Optional.

Multiband grouping
Table 4-12 describes the fields in the Multiband grouping of the BSS Detailed View.

Table 4-12 BSS Detailed View fields - Multiband grouping

Field name/BSS
parameter name

Mandatory or
Optional?

Brief description

Values

MultiBand Enabled
mb_preference

Can only be modified if

the MultiBand Inter-Cell
Handover feature is
unrestricted (enabled).

Enabled (1) or Disabled (0).

Default is 0.

Mandatory.

Early Classmark
Sending
early_classmark
_send(OMC-R
parameter name:
earlyClassmarkSnd)

Determines if the BSS

suppresses the early
sending of the Classmark
Update message to the
MSC.

0 - 3.
Disabled on A-Interface and
Air-Interface (0),
Enabled on A-Interface,
disable on Air-Interface (1),
Disabled on A-Interface, and
enabled on Air-Interface (2),
Enabled on A-Interface and
Air-Interface (3).
Default is 0.

Mandatory.

Early Classmark
Delay

The duration the BSS

delays before sending
the Classmark Update
message to the MSC in
the case of controlled
early classmark sending.

0 - 100000 ms.
Default is 0.

Mandatory.

68P02901W17-T

4-29
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Enhanced Full Rate grouping

Table 4-13 describes the fields in the Directed Retry grouping of the BSS Detailed View.

Table 4-13 BSS Detailed View fields - Enhanced Full Rate grouping
Field name/BSS
parameter name

Mandatory
or Optional?

Brief description

Values

Enhanced Full Rate

Enabled
efr_enabled

Whether Enhanced Full Rate (EFR)

has been enabled at the BSS. Only
valid when the Enhanced Full Rate
feature EFROpt is unrestricted.

Disabled (0),
Enabled (1).
Default is 0.

Optional.

HO Req Speech
Version Used
handover_required
_sp_ver_used
(OMC-R parameter
name:
ho_req_spver_used)

Whether the speech version used

can be built into the Handover
Required message.
Cannot be disabled:

Disabled (0),
Enabled (1).
Default is 0.

Mandatory.

Unless efr_enabled is
disabled.

If either AMR Full Rate

Enabled (amr_fr_enabled)
or AMR Half Rate Enabled
(amr_hr_enabled) is enabled
at the BSS.

Circuit Error Rate Monitor grouping

See Enhanced Circuit Error Rate Monitor (ECERM) on page 2-70 for further details.

Enhanced Circuit Error Rate Monitor grouping

See Enhanced Circuit Error Rate Monitor (ECERM) on page 2-70 for further details.

GPRS grouping
Table 4-14 describes the fields in the GPRS grouping of the BSS Detailed View. These fields are
grayed-out, if the GPRS feature (gprsOpt) is restricted at the BSS.

Table 4-14

BSS Detailed View fields - GPRS grouping

Field name/BSS parameter

name

Brief description

Values

SMG Gb Protocol Version

smg_gb_vers

The SMG version adopted

by the BSS over the Gb
interface.

24 - 31 (SMG
Gb version).
Default is 31.

Related SGSN

Serving GPRS support

node object identifier
associated with this BSS.

Mandatory or
Optional?
Optional.

Optional.

Continued

4-30

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Table 4-14 BSS Detailed View fields - GPRS grouping (Continued)

Field name/BSS parameter
name

Brief description

Values

Mandatory or
Optional?

Delayed Downlink TBF

Release Duration

See GPRS Interleaving

TBFs on page 2-89 for
further details.

Optional.

Delayed Uplink TBF Release

Duration

See GPRS Interleaving

TBFs on page 2-89 for
further details.

Optional.

Delayed Downlink TBF

Release Control

See GPRS Interleaving

TBFs on page 2-89 for
further details.

Optional.

Auto Downlink Duration

See GPRS Interleaving

TBFs on page 2-89 for
further details.

Optional.

GPRS Scheduling Beta

Algorithm

See GPRS Interleaving

TBFs on page 2-89 for
further details.

Optional.

Enhanced One Phase

Access
eop_enabled

See Enhanced GPRS One

Phase Access on page
2-113 for details.

PCU Redundancy Status

pcu_redundancy

Indicates whether the BSC

allows PCU redundancy.
Restricted to Disabled.

Disabled.

Mandatory.

1st Redundant for PCU 0

pcu_red_map_01

Identifier of the first

redundant PCU for PCU 0.

-1.

Optional.

2nd Redundant for

PCU 0
pcu_red_map_02

Identifier of the second

redundant PCU for PCU 0.

-1.

Optional.

1st Redundant for

PCU 1
pcu_red_map_11

Identifier of the first

redundant PCU for PCU 1.

-1.

Optional.

2nd Redundant for

PCU 1
pcu_red_map_12

Identifier of the second

redundant PCU for PCU 1.

-1.

Optional.

1st Redundant for

PCU 2
pcu_red_map_21

Identifier of the first

redundant PCU for PCU 2.

-1.

Optional.

2nd Redundant for

PCU 2
pcu_red_map_22

Identifier of the second

redundant PCU for PCU 2.

-1.

Optional.

Mandatory.

Continued

68P02901W17-T

4-31
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Table 4-14 BSS Detailed View fields - GPRS grouping (Continued)

Field name/BSS parameter
name

Mandatory or
Optional?

Brief description

Values

Medium Access Control

Mode
gprs_mac_mode

The Medium Access mode

that should be used by the
PCUs.
This element is restricted
by the GPRS optional
feature. It can be set to the
value 2 only if the Extended
Dynamic Allocation feature
is unrestricted.

Fixed access
mode (0)
Dynamic access
mode (1)
Default is 1.

Mandatory.

Network Operation Mode

gprs_network_
operation_mode

Whether a GPRS is present

between the MSC and the
SGSN.

1 to 3.
Default is 3.

Mandatory.

GPRS Dual Power Mode

gprs_dl_pwr_mode

The downlink power

control mode the PCUs
uses to broadcast data
blocks to the mobile.

No power mode
(0), Mode A
(1), Mode B (2).
Default is Mode
A (1).

Optional.

SGSN Release
sgsn_release

See PBCCH/PCCCH
feature on page 2-117
for details.

Current Bucket Level

Feature
bssgp_cbl_bit

See Current Bucket Level

(CBL) feature on page
2-145 for details.

Mandatory.

Increased PRP Capacity

Feature Enabled

See Enhanced Scheduling

on page 2-146 for details.

Mandatory.

Max Number of UL
timeslots per mobile
PRR Blocks Reservation
Aggressiveness Factor
GPRS Uplink or Downlink
bias
Most Common Multislot of
GPRS Mobiles

See Enhanced Scheduling

on page 2-146 for details.

Optional.

Maximum Sum Timeslots

max_sum_timeslot

Indicates whether in the

BSS software, allocations
with a total of 6 GPRS
timeslots on a single
carrier is supported.

Min (5)
Max (6)
Default (5)

Optional.

Redundant PSP Audit Timer

red_psp_audit_tmr

Audit mechanism used to

determine the health of
the secondary MPROC.
Grayed-out if the GPRS
feature is restricted at the
BSS.

0 to 24.
Default 24.

Optional.

GPRS Type 5 Algorithm

Enabled
gprs_type5_alg

See Network Assisted Cell

Change (NACC) on page
2-162 for further details.

Optional.

Continued
4-32

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Table 4-14 BSS Detailed View fields - GPRS grouping (Continued)

Field name/BSS parameter
name

Mandatory or
Optional?

Brief description

Values

{34452} MS Flow Control

Enabled
ms_flow_control
_enabled

Used to enable or disable

the function of mobile flow
control for PS call.

0 to 1.
Default 1.

Optional.

{34452} GMSK Capability

Mode
gmsk_capability
_mode

Used for configuration of

the PRM detect mode for
GMSK block.

0 to 2.
Default is 0.

Optional.

{34452} PUAK Compress

Mode
puak_compress
_mode

Specifies the PUAK

working modes, and
includes the following
modes:

0 to 2.
Default is 0.

Optional.

0- Flexible PUAK
mode

1- Forced compressed
PUAK mode

2- Forced
uncompressed PUAK
mode

Map Information grouping

Table 4-15 describes the fields in the Map Information grouping of the BSS Detailed View.

Table 4-15 BSS Detailed View fields - Map Information grouping

Field name

Brief description

Longitude

Longitude position of the

displayable node.

Latitude

Latitude position of the

displayable node.

Service State

The state of a node or link on

a map.

Default Map

See description in Table 3-3.

68P02901W17-T

Values

Mandatory or
Optional?

-18000 to 18000.

Optional.

-9000 to 9000.

Optional.

INS, OOS
or Unknown.
Currently, INS
is defined as
Enabled-Unlocked
or Busy-Unlocked,
and OOS is
Disabled-Locked or
Disabled-Unlocked.

Optional.

4-33
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

GSM/GPRS Trace Information grouping

See Call trace flow control on page 2-63 for details of these parameters.

SMS Information grouping

See Short Message Service - Cell Broadcast on page 2-45 for details of these fields.

Traffic Parameters grouping

Table 4-16 describes the fields in the Traffic Parameters grouping of the BSS Detailed View. All
fields in this grouping are OMC only attributes, and are used in traffic model formulae.

Table 4-16 BSS Detailed View fields - Traffic Parameters grouping

Field name

Values

Brief description

Mandatory or
Optional?

Ratio of SMSs to
calls

Number of SMS messages compared to

calls, expressed as a ratio. OMC only
attribute.

0.0 - 1.0.
Default is 0.

Optional.

Number of
handovers per
call

Average number of handovers per call.

OMC only attribute.

0.0 - 15.0.
Default is 0.

Optional.

Ratio of Intra-BSC
handovers to all
handovers

The ratio of intra-BSC handovers to all

handovers. OMC only attribute.

0.0 - 1.0.
Default is 0.

Optional.

Location Update
factor

A function of the ratio of location updates

to calls, the ratio of IMSI detaches to calls
and whether the short message sequence
or long message sequence is used for IMSI
detach.

0.0 - 30.0.
Default is 0.

Optional.

Call Duration seconds

The average call duration during the

busiest period of the day.

0 - 1200.
Default is 0.

Optional.

0 - 20.
Default is 0.

Optional.

Paging rate in
pages per second

Network Assisted Cell Change (NACC) grouping

Table 4-17 describes the fields in the Network Assisted Cell Change grouping of the BSS
Detailed View.

Table 4-17 BSS Detailed View fields - Network Assisted Cell Change grouping
Field name
Cell Change
Notification Enabled
nacc_enabled

4-34

Brief description

Values

Mandatory or
Optional?

See Network Assisted Cell

Change (NACC) on page
2-162 for further details.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Quality of Service (QoS) grouping

See Quality of Service (QoS) on page 2-154 for details of these fields.

LCS grouping
See GSM location services on page 2-104 for details of these fields.

Network Controlled Cell Reselection grouping

See Network Controlled Cell Reselection on page 2-81 for further details of these fields.

GPRS Seamless Cell Reselection

Table 4-18 describes the fields in the GPRS Seamless Cell Reselection grouping of the BSS
Detailed View. These fields are grayed-out if the GPRS Seamless Cell Reselection Feature
(scrOpt) in the Optional Features grouping of the BSS Detailed View is unrestricted (Disabled
(0)).

Table 4-18 BSS Detailed View fields - GPRS Seamless Cell Reselection grouping
Field name/
parameter name
GPRS Seamless Cell
Reselection Feature
scr_enabled

Brief description

Values

See GPRS Seamless Cell

Reselection on page 2-142 for
details.

Mandatory or
Optional?
Mandatory.

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)
grouping
Table 4-19 describes the fields in the Channel Mode Usage (AMR Full Rate and Half Rate/GSM
Half Rate) grouping of the BSS Detailed View. Unless stated otherwise, the OMC-R database
parameter names are the same as the BSS database parameter names. Fields in this grouping
can be accessed if the AMR Feature (amrOpt) or the GSM HR Feature (gsmHalfRateOpt) are
unrestricted (Enabled) at the BSS, see Adaptive Multi-Rate (AMR) on page 2-129 for details.

Table 4-19
grouping

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)

Field name/BSS
parameter name
AMR Full Rate
Enabled
amr_bss_full
_rate_enabled
(OMC-R parameter

Brief description

Values

Enables and disables AMR

Full Rate (FR) for the
BSS. Cannot be enabled
if HO Req Speech Version
Used (ho_req_spver_used)
is disabled at the BSS,
or if CIC Validation

0 or 1.
Enabled (1),
Disabled (0).
Default is 0.

Mandatory or
Optional?
Optional.

Continued

68P02901W17-T

4-35
Jan 2010

BSS Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Table 4-19 Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)
grouping (Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

name:
amr_fr_enabled)

(cic_validation) is disabled
at the Assoc_RXCDR.

AMR Half Rate

Enabled
amr_bss_half_rate
_enabled(OMC-R
parameter name:
amr_hr_enabled)

Enables and disables AMR

Half Rate (HR) for the
BSS. Cannot be enabled
if ho_req_spver_used
is disabled at the BSS,
or if CIC Validation
(cic_validation) is disabled
at the Assoc_RXCDR.

0 or 1.
Enabled (1),
Disabled (0).
Default is 0.

Optional.

AMR MS Monitor
Period
amr_ms_monitor
_period(OMC-R
parameter name:
AmrMsMonPeriod)

Used to detect MSs

continually requesting
the highest or lowest modes.

0, or 10 - 120
SACCH periods.
0 disables the MS
Monitor function.
Default is 40.

Optional.

AMR MS Low CMR

amr_ms_low_cmr

The percentage of the

monitor period for which an
individual MS can request
the lowest Codec mode.

50 - 100%. Default
is 95%.

Optional.

AMR MS Low
If the MS is consistently
RXQUAL
requesting lowest rate
amr_ms_low_rxqual Codec mode but reports
RXQUAL values less than
defined, the BSS uses this
value to decrease the Down
Link adaptation Thresholds.

0 - 7 Qband units.
Default is 2
Qbands or 0.5%
BER.

Optional.

AMR MS High CMR

amr_ms_high_cmr

The percentage of the

monitor period for which an
individual MS can request
the highest Codec mode.

50 - 100%
Default is 99%.

Optional.

AMR MS High
RXQUAL
amr_ms_high_rxqual
(OMC-R parameter
name:
AmrMsHighRxqual)

If the MS is consistently
requesting the highest rate
Codec mode but reports
RXQUAL values less than
defined, the BSS uses this
value to increase the Down
Link adaptation Thresholds.

0 - 7 Qband units.
Default is 4
Qbands, or 2.5%
BER.

Optional.

AMR Downlink
Threshold
Adjustment
amr_dl_thresh
_adjust(OMC-R
parameter name:
AmrDlThreshAdj)

Used to increase or decrease

C/I adaptation thresholds
according to the values for
AmrMsHighRxqual and
amr_ms_low_rxqual.

1 - 7 dB.
Default is 3.

Optional.

Continued

4-36

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS Detailed View fields

Table 4-19 Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)
grouping (Continued)
Field name/BSS
parameter name

Mandatory or
Optional?

Brief description

Values

AMR Force Half Rate

Usage
force_hr_usage
(OMC-R parameter
name:
force_hr_use)

Overrides MSC provided

preference, and forces Half
Rate usage for all AMR/GSM
Half Rate capable calls
within the BSS.
Does not apply when the
MSC has specified that
rate changes are not
allowed. For example, if
hr_intracell_ho_allowed is
set such that full-rate only is
allowed, force_hr_usage is
ignored.

0 or 1.
Disabled (0)
Enabled (1).
Default is Disabled
(0).

Optional.

AMR Downlink LA
Mode Change Min
amr_dl_la_mode
_chg_min(OMC-R
parameter name:
AmrDlLaMode
ChgMin)

Used for the downlink

adaptation procedure to set
the minimum time period
between initiating changes
in the downlink Codec mode.
The delay is only added, if
set to less than the inherent
delay in the adaptation
(including zero).

0 - 255 ms.
Default is 100.

Optional.

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)
grouping with GSM Half Rate
Table 4-20 describes the fields in the Channel Mode Usage (AMR Full Rate and Half Rate/GSM
Half Rate) grouping of the BSS Detailed View when the Half Rate feature is unrestricted. All
other fields remain the same. Unless stated otherwise, the OMC-R database parameter names
are the same as the BSS database parameter names. Fields in this grouping can be accessed
if the GSM HR Feature (gsmHalfRateOpt) is unrestricted (Enabled) at the BSS, see GSM
Half Rate on page 2-140 for details.

Table 4-20
grouping

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)

Field name/BSS
parameter name
GSM BSS Half Rate
Enabled
gsm_bss_half_rate
_enabled(OMC-R
parameter name:
gsm_bss_half_rate
_enabled)

68P02901W17-T

Brief description

Values

Enables and disables GSM

Half Rate (HR) for the
BSS. Cannot be enabled
(grayed-out) if GSM Half
Rate Feature is restricted,
or if CIC Validation
(cic_validation) is disabled
at the Assoc_RXCDR.

0 or 1. Enabled
(1), Disabled
(0).Default is 0.

Mandatory or
Optional?
Optional.

4-37
Jan 2010

Modifying BSS details using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Pre-empt grouping
See Enhanced Multi-level Precedence and Pre-emption (eMLPP) on page 2-165 for details
of these parameters.

RSL Congestion grouping

See RSL Congestion Control on page 2-170 for details of these parameters.

Modifying BSS details using the OMC-R GUI

To change BSS details, see Modifying a network object using the OMC-R GUI on page 1-34. For
information about changing specific fields in the BSS Detailed View, see the following section.

Changing the Network Entity Id field after BSS creation

Modifying the Network Entity Id field in the Identification grouping after the BSS has been
created to a value that is already in use, causes the OMC-R to reject the value and display the
following warning message:
The Network Entity Identifier must be unique within the network
When the Transcoding field is set to Remote (0), and an attempt is made to modify the value in
the Network Entity Id field, the OMC-R displays the following warning message:
Warning: Changing Network Entity Id will result in cycling all Associated RXCDR
devices which are BUSY_UNLOCKED. Cycling these devices will result in loss of all
call traffic from this BSS to those RXCDRs. This loss of call traffic may be
avoided if cic_validation is disabled at the BSS. The connected remote Associated
BSS entities may need to the updated at the following RXCDRs:
RXCDR_<name>
RXCDR_<name> ...
Do you wish to continue?
Click OK to continue or Cancel to cancel the cycling.
However, these messages are not displayed if the Transcoding field in the BSS Detailed View is
set to Local (1).

4-38

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating an RXCDR using the OMC-R GUI

Creating an RXCDR using the OMC-R GUI

Prerequisites to creating an RXCDR

An RXCDR should be created in the OMC-R GUI before physically connecting to the OMC-R. It
can only be added if a network (that is, the parent) has been defined in advance.

Creating an RXCDR using the OMC-R GUI

To create an RXCDR using the OMC-R GUI, use the following procedure:

Procedure 4-6 Create an RXCDR using the OMC-R GUI

1

Navigate to and select the RXCDR class button in the Navigation Tree.
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details. The RXCDR class button changes color.

From the menu bar, select Edit Create. The OMC-R displays the
RXCDR Detailed View in Create mode

Click the Initial Software Load button to display a Software Inventory

Dialog window.

Double-click one of the software loads to select it and enter it in the

RXCDR Detailed View.

From the menu bar of the RXCDR Detailed View window, select Options
Initialize Form. The OMC-R displays the RXCDR Detailed View
window.

Complete the fields in the RXCDR Detailed View as required. See

Table 4-1 to Table 4-16 for guidance.

NOTE
To obtain the relevant information for a parameter, select
Help - On Context from the menu and drag the ? prompt to
the appropriate field and click that field. A context-sensitive
help page is displayed.

68P02901W17-T

Once all the required information has been entered in the RXCDR
Detailed View, select File Create from the menu bar.

Select File Close from the menu bar to close the Detailed View.

4-39
Jan 2010

Modifying RXCDR details using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Modifying RXCDR details using the OMC-R GUI

To change RXCDR details, see Modifying a network object using the OMC-R GUI on page
1-34. For information about changing specific fields in the RXCDR Detailed View, refer to
the following section.

Changing the Network Entity Id field after RXCDR creation

Any attempt to modify the Network Entity Id parameter field in the Identification grouping after
the RXCDR has been created to a value that is already in use, results in the OMC-R rejecting the
value and displaying the following warning message:
The Network Entity Identifier must be unique within the network
Any attempt to modify this field after the RXCDR has been created, results in the OMC-R
displaying the following warning message:
Warning: Changing Network Entity Id will result in cycling all Associated BSS
devices which are BUSY_UNLOCKED. Cycling these devices will result in loss of all
call traffic from those BSSs to this RXCDR. This loss of call traffic may be
avoided if cic_validation is disabled at the BSS for this RXCDR. The connected
remote Associated RXCDR entities may need to be updated at the following BSSs:
BSS_<name>
BSS_<name> ...
Do you wish to continue?
Click OK to continue or Cancel to cancel the cycling.
If the Network Entity Id field is changed, later when the RXCDR Detailed View window is saved,
the OMC-R displays the following warning message:
Warning: Changing the Network Entity Identifier will cause all the associated
BSSs to be cycled which may result in the loss of all active calls.
Do you wish to continue?
Click OK to continue or Cancel to cancel the cycling.

4-40

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating a BSS/RXCDR database

Creating a BSS/RXCDR database

Definition of BSS/RXCDR database

A BSS/RXCDR database contains many parameters which describe the configuration of the
hardware and software of the BSS. Each BSS requires a software load and a database of the
same version to be operational.

BSS/RXCDR database types

A BSS/RXCDR database can exist in two types:

Configuration Management database object.

Database script file.

Configuration Management database object

Motorola recommends the use of the DataGen tool to produce the BSS/RXCDR database objects.
A Configuration Management (CM) database object is the compiled database script file. This
compiled file cannot be read or edited.
The CM database object is produced by using the DataGen tool. This object file is then in a form
used for downloading to the live network when required.
The database can be downloaded along with, or separate from, the software load. The database
is always object number 02 of the load.
For further information about DataGen, see System Information: DataGen (68P02900W22).

Database script file

A database script file is an ASCII file which may be read from or written to. The script can
be produced manually by entering text into an ASCII file or it can be produced from an 02
object using the DataGen tool (RevGen utility) as shown in Figure 4-2. The advantages of using
DataGen are that it is faster and more accurate.
The content of a database script file is commands such as equip, chg_element and
modify_value. Refer to Technical Description: BSS Command Reference (68P02901W23) for
detailed information of all these commands and parameters.

68P02901W17-T

4-41
Jan 2010

NE database checks

Chapter 4: Configuring a BSS/RXCDR

This script can be LAN loaded onto the BSC to create the database object during the installation
and commissioning of a BSC.

Figure 4-2 Example of a script file

ti-GSM-Exampleofascriptfile-00781-ai-sw

NE database checks
Network Element (NE) database checks are required for the following reasons:

4-42

To ensure that the NE has the same database as the OMC-R.

To clear out old databases. Only the last three databases are kept.

To check if an upload has been made after NE database changes. When changes are made,
they must be logged using any method selected by the customer.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Typical database directory structure

When configuration changes at an NE database are made, the MIB is updated by performing an
audit. The OMC-R must also be updated, by uploading the NE database.
There should be a maximum of three databases on the system for any BSS or RXCDR at any
one time.
For more information on the database checking procedure see Operating Information: OMC-R
System Administration, (68P02901W19).

Typical database directory structure

Typically, the database is stored in the following directory: usr/omc/ne_data/dbroot.
A typical BSS database directory structure is shown in Figure 4-3. There is a similar directory
structure for an RXCDR.

Figure 4-3 Typical BSS database directory structure

00.00.03.fd.02
YORK

current database
database.list

$DBROOT/
BSSspecific/
BSS<name>

dbComment
download.list
00.00.03.fd.02.Z
db950228122300

database.list

fallback
database for
current load

dbComment
00.00.03.fd.02
database.list

CSFP
database

CSFP directory
dbComment
download.list
OTHER BSSs
ti-GSM-SC01W17-000049-eps-sw

68P02901W17-T

4-43
Jan 2010

Deleting a BSS/RXCDR

Chapter 4: Configuring a BSS/RXCDR

Deleting a BSS/RXCDR

Introduction to deleting a BSS/RXCDR

This section describes the procedure to delete a BSS/RXCDR from the OMC-R, and the two
additional procedures required to delete the BSS/RXCDR from the X.25 network.

CAUTION
Removing a BSS or RXCDR prevents the OMC-R from communicating with the
BSS/RXCDR.
Failure to physically disconnect the BSS/RXCDR from the OMC-R may result in
unnecessary traffic across the GSM network.

Impact of deleting a BSS on an Assoc_BSS

If a BSS, which has been specified as an Associated BSS, is deleted from the network, the
Associated BSS field in the Assoc_BSS Detailed View is set to NULL. This indicates that the
Assoc_BSS does not correspond to any BSS device.

Impact of deleting an RXCDR on an Assoc_RXCDR

If an RXCDR, which has been specified as an Associated RXCDR is deleted from the network,
the Associated RXCDR field in the Assoc_RXCDR Detailed View is set to NULL. This indicates
that the Assoc_RXCDR does not correspond to any RXCDR device.

Prerequisites before deleting a BSS/RXCDR

A BSS/RXCDR should be deleted only after authorization has been obtained in advance from
the Network planning team.
This procedure only applies to a BSS to be decommissioned. If the BSS is being moved to a
different OMC-R or RXCDR, refer to the Reparenting a BSS on page 4-100 or Reparenting an
RXCDR to a different MSC on page 4-106 procedures.

4-44

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Removing a BSS/RXCDR from the network

Removing a BSS/RXCDR from the network

Perform the following tasks to remove a BSS or RXCDR from the network:

Procedure 4-7 Remove a BSS or RXCDR from the network

1

Carry out Deleting a BSS/RXCDR from the OMC-Rin this section.

Remove the BSS/RXCDR from the X.25 network by deleting a

BSS/RXCDR at the packet switch, see Reparenting a BSS on page
4-100.

Deleting a BSS/RXCDR from the OMC-R

To delete a NE from the OMC-R carry out the following procedure:

Preparing to delete
The following preparation is required before deleting a BSS/RXCDR:

Procedure 4-8 Prepare to delete BSS/DXCDR

1

Lock the OML(s) between the OMC-R and this BSS/RXCDR using the
command:
lock_device 0 OML x y 0
Where:
x is an OML identifier.
y is an OML identifier.

NOTE
This can be done locally at the BSC or remotely using rlogin.
2

68P02901W17-T

Physically disconnect the cable between the OMC-R and BSS/RXCDR.

4-45
Jan 2010

Deleting a BSS/RXCDR from the OMC-R

Chapter 4: Configuring a BSS/RXCDR

Deleting the BSS/RXCDR

Follow Procedure 4-9 to delete the BSS/RXCDR:

Procedure 4-9 Delete BSS/RXCDR

1

Using the Navigation Tree, display the BSS/RXCDR to be deleted.

NOTE
Configuration information can be extracted if the BSS is to
be added at a later date. Refer to Extracting data from the
CM MIB using cmutil on page 15-25 for further details.
2

As omcadmin, delete the BSS from the MIB using the following
command:

NOTE
This step requires authorization in advance from the OMC-R
System Administrator.
HierDelete BSS <name>

The following confirmation message is displayed:

Do you really want to delete the BSS <name>?
The gui might core if any of the forms for the objects are
open for edit
Please ensure this is not the case and will not be at any
time while this script is running
(Warning: this operation cannot be aborted once started.
Type Y to proceed, anything else will abort operation now).
3

Press Y to proceed.
The deletion is complete when the BSS/RXCDR has been removed from
the Navigation Tree. No further deletes should be performed until this
occurs.

NOTE

4-46

The BSS software directory is renamed in a similar

manner to after the activation of a new BSS software
load.

The relevant entries in the PM database are renamed

to <old_name>~xx where xx is a two digit number.

The relevant entries in the NE.MAP and SITE.MAP

are commented out. The old names must not be
re-used until the PM statistics have cleared (after
approximately five days) and the entries deleted using
delete_BSS, delete_SITE or delete_CELL commands.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a BSS/RXCDR from the OMC-R

Follow up activities after deletion of the BSS/RXCDR

When the BSS/RXCDR has been deleted, perform the following procedure:

Procedure 4-10 Follow up after deleting BSS/RXCDR

1

If the cells of the BSS are being decommissioned, or reused under

different BSSs, external neighbors which point to these cells may
require removal. The HierDelete utility does not remove these
external neighbors from other BSSs. The neighbors should be removed
from other BSS databases during the next frequency replan.

Verify NE.MAP has been cleaned up correctly, by checking NE.MAP

for entries relating to the BSS. Also use Remote Login icon on the GUI
front panel; if the BSS name still appears, then NE.MAP has not been
cleaned up correctly.

Remove the BSS directory from the following location:

/usr/omc/ne_data/dbroot/BSS/BSSspecific

Edit any appropriate subscription lists to remove the BSS from

them. See OMC-R Online Help, Network Operations for details of
subscription lists.

NOTE
Once the BSS has been deleted, the following are also
removed:
Event and Alarm windows for the BSS and the BSS SITES,
if subscriptions are exclusive to them.

68P02901W17-T

Remove the appropriate RXCDR - Associated BSS objects from the

RXCDRs which are connected to the BSS.

Remove any entries for the NE from the packet switch/MUX, see
Reparenting a BSS on page 4-100.

Delete the default network map and any user-defined map files
containing the deleted BSS information.

If using the Map feature, remove Commslinks from the BSS to devices
such as RXCDRs, OMC-R, and MSC so that they are no longer displayed
on the map. Also remove the BSS from any customized regional maps.

If using the Map feature, open the network map from the GUI and
check the impact of the BSS/RXCDR removal on the remaining NEs.
Move the remaining nodes to any desired new positions on the map
background. When the NEs are in the desired position, save the
network map and the new default map, by selecting File Save from
the menu bar. Refer to: OMC-R Online Help, Network Operations for a
description of how to move the NEs on a map.

4-47
Jan 2010

Deleting a BSS/RXCDR at the packet switch/MUX

Chapter 4: Configuring a BSS/RXCDR

Deleting a BSS/RXCDR at the packet switch/MUX

Introduction to Deleting the BSS/RXCDR at the packet switch

This section describes the procedure to delete a BSS/RXCDR at the packet switch, and at the
MUX. Refer to Operating Information: OMC-R System Administration (68P02901W19) for
further details about the packet switch/MUX.

Configuration changes at the packet switch

The following configuration changes must be made to the packet switch when removing a
BSS/RXCDR from the network:

Procedure 4-11 Change packet switch configuration before deleting BSS/RXCDR

1

At the packet switch delete the routing table entry, if necessary.

Remove the cabling between the packet switch and MUX.

Deleting the routing table entry

The removal of an NE from the network may not require any actions to be carried out at the
packet switch. There is no path through the MUX to the packet switch and the NE should have
been removed from the OMC-R NE nodes file so that data is not routed to it. However, the
OMC-R System Administrator may wish to modify the routing table entry for the NE by deleting
the address field as a precautionary procedure.

Removing the cabling between packet switch and MUX

If a complete 2 Mbit/s link is to be removed:

Procedure 4-12 Remove complete 2 Mbit/s link before deleting BSS/RXCDR

4-48

Disconnect the cable from the access link port and the cable between
ports used between the MUX and packet switch.

Use the configuration table to determine to which ports these cables

are connected.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuration changes at the MUX

Configuration changes at the MUX

The following configuration changes must be made to the MUX when removing a BSS/RXCDR
from the network:

Procedure 4-13 Change MUX configuration before deleting BSS/RXCDR

1

Delete the link, endpoints, and circuit entries from the MUX
configuration.

Remove the cabling between the packet switch and MUX.

Dependencies on NE removal from the MUX

Actions at the MUX are dependent on whether the NE being removed is:

On its own 2 Mbit/s link.

On a single timeslot on a shared link.

If the NE is on its own 2 Mbit/s link, an additional action is required as detailed in the following
section Removing the NE from the MUX.

Removing the NE from the MUX

Removing configuration information
If the NE is on its own 2 Mbit/s link, remove the access link entry from the MUX configuration,
before removing the configuration information:

Procedure 4-14 Remove configuration information

68P02901W17-T

Use the MUX configuration table to determine the linkname, endpoints

and circuit name, that have to be removed from the MUX configuration.

Continue with the next procedure, Removing the NE link to the

MUX, to remove the links to the MUX.

4-49
Jan 2010

Removing the NE link to the MUX

Chapter 4: Configuring a BSS/RXCDR

Removing the NE link to the MUX

To remove an NE link to the MUX:

Procedure 4-15 Remove NE link to the MUX

4-50

Log in to the MUX.

Remove the access link entry if a 2 Mbit/s link is being disconnected

using the following command:
d l -r <linkname>

Remove circuit entries using the following command:

d c -r <circuitname>

Remove endpoint entries using the following command:

d e -r <endpoint1>
d e -r <endpoint2>

Log out of the MUX by pressing Ctrl-L.

Remove the cabling.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping cabinets and cages at a BSS site

Equipping cabinets and cages at a BSS site

Overview of equipping cabinets and cages at a BSS

Cabinets and cages can be created using either the:

OMC-R GUI Navigation Tree.

equip BSS command from a TTY session.

Equipping cabinets and cages can be carried out either in SYSGEN mode or outside of SYSGEN
mode with the site locked.
See Configuring a cabinet on page 4-54 and Configuring a cage on page 4-59 in the following
sections.

Horizonmicro2 and Horizoncompact2 BTS cabinets

A maximum of three Cabinets can exist at a Horizonmicro2 and Horizoncompact2 BTS. Each
Cabinet can be seen as a BTS.
The first Cabinet equipped (Cabinet:0) represents the master BTS. Further Cabinets (Cabinet:1
and Cabinet: 2) represent slave BTSs. The slave Cabinets are attached to the master Cabinet
through fiber ports 1 and 2, respectively. The master Cabinet must be equipped before the
slave Cabinets.
When a slave Cabinet is equipped, the BTS Configuration Type field (BSS parameter name:
bts_type) in the BTS Detailed View of the parent BTS is set to 1, meaning Non-Abis, Type 1.
If Cabinet devices 1 and 2 exists, the BSS autoequips the related DHP(s) devices with the
ids 1 and 2.
See Introduction to BSC and BTS sites on page 7-2 for further details of Horizonmicro2.

Horizon II macro and Horizon II macro extension cabinets

If a cabinet is created with the cabinet type Horizon II macro or Horizon II macro_ext (indicating
a cabinet extension), the cabinet type cannot be changed to any other type. Likewise, a cabinet's
type cannot be modified from any other type to Horizon II macro. However, a cabinet with
cabinet type Horizonmacro_ext, TCU 6, or TCU 2 can be modified to Horizon II macro_ext.
A Horizon II macro or Horizon II macro_ext cabinet type can support only one of the following
frequencies at a time:

PGSM900.

EGSM900.

DCS1800.

68P02901W17-T

4-51
Jan 2010

Horizon II mini and Horizon II macro cabinets

Chapter 4: Configuring a BSS/RXCDR

A maximum of three extension cabinets can be connected to a Horizon II macro cabinet type, as
shown in Table 4-21.

Table 4-21 Extension cabinets for Horizon II macro

Master cabinet

Extension

Horizon II macro

TCU_6.
Horizonmacro_ext.
Horizon II macro_ext.

A Horizon II macro_ext cabinet type can be equipped to the cabinet types shown in Table 4-22.

Table 4-22 Cabinet types allowing Horizon II macro_ext as an extension type

Extension

Master cabinet

Horizon II macro_ext

M-Cell6.
Horizonmacro.
Horizon II macro.

Horizon II mini and Horizon II macro cabinets

Horizon II macro functionality can be applied to a Horizon II mini, that is, whatever a Horizon II
macro cabinet with two CTU2s and a single BTP can do, a Horizon II mini can also do, except
where otherwise stated.
Modification of cabinet type from Horizon II mini to Horizon II macro is permitted as long as
there are no DRI or EAS devices equipped.
Modification from Horizon II macro to Horizon II mini is permitted as long as the site has one or
fewer BTPs, no EASs, and no DRIs equipped to it. All other changes involving Horizon II mini
and Horizon II macro master cabinet are disallowed. The frequency type of the source and
destination cabinet remain the same.
A Horizon II mini or Horizon II mini extension cabinet can support only one type of frequency
at any one time. A Horizon II mini cannot support dual band. It can support PGSM, EGSM,
and DCS1800 but only one band per cabinet.
A Horizon II mini can be the master of, or slave to, a Horizon II macro cabinet.
Table 4-23 shows extension cabinets to which a Horizon II mini can be master.

Table 4-23

Extension cabinet types allowed for Horizon II mini

Master cabinet
Horizon II mini

Extension cabinet
Horizon II mini extension.
Horizon II macro
extension.
Horizon macro extension.
TCU6.

4-52

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Horizon II mini and Horizon II macro cabinets

Table 4-24 shows the master cabinets to which a Horizon II mini extension can be equipped.

Table 4-24 Master cabinet types allowed for Horizon II mini extension
Extension cabinet

Master cabinet

Horizon II mini extension

Horizon II mini.
Horizon II macro.
Horizon macro.
M-Cell6.

68P02901W17-T

4-53
Jan 2010

Configuring a cabinet

Chapter 4: Configuring a BSS/RXCDR

Configuring a cabinet

Creating a cabinet for a site using the OMC-R GUI

To create an instance of a Cabinet, proceed as follows:

Procedure 4-16 Create Cabinet instance using the OMC-R GUI

1

Navigate to and select the Cabinet class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Hardware Devices
Cabinet). If necessary, see Navigating to a network object class or
instance on page 1-28 for further details. The network object class
button changes color.

Select Edit Create from the Navigation Tree menu bar.

Complete the fields, as required. See Cabinet Detailed View fields

for further details.

Select File Create from the menu bar to create a Cabinet instance.

Select File Close from the menu bar to close the Detailed View form.

Cabinet Detailed View fields

The following sections list and briefly describe the parameter fields in the Cabinet Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

4-54

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cabinet Detailed View fields

Identification grouping
Table 4-25 describes the fields in the Identification grouping of the Cabinet Detailed View.

Table 4-25 Cabinet Detailed View fields - Identification grouping

Brief description

Values

Mandatory
or
Optional?

Cabinet Type
cabinet_type

This parameter represents a physical

cabinet within a BSC/RXCDR/BTS site.
28 or HORIZON2MICRO indicates that the
cabinet is a Horizon II micro.
29 or HORIZON2MICRO_EXT indicates
that the cabinet is a Horizon II micro
extension.

0 - 29.

Mandatory.

RDN Class

See description in Table 4-1.

Default is
Cabinet.

RDN Instance

See description in Table 3-1.

0 - 15.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent site. Click

to display the parent site Detailed View.

Kit Number

Not displayed for a Horizonmacro or

Horizon II macro BTS. Grayed-out if site
is not a Horizonmicro or Horizoncompact.
For a Horizonmicro or Horizoncompact,
this field is inherited from the Hardware
Version Number (HVN), and cannot be
changed.

Field Replaceable
Unit (FRU)

See Maintenance Information: BSS Field

Troubleshooting (68P02901W51) for

Field name

0 - 15
characters

Optional.

Optional.

details of all the possible values that can

be displayed.
Displayed when cabinet_type is: Horizon
II mini, Horizon II macro, Horizon macro,
M-Cell6 or M-Cell2.
For a Horizonmicro or Horizoncompact,
this field is inherited from the Hardware
Version Number (HVN), and cannot be
changed. For a BSSC3 cabinet at the BSC
site, this field is set to BSSC3 and cannot
be changed.
Serial Number

68P02901W17-T

Not displayed for a Horizonmacro or

Horizon II macro BTS. Grayed-out if site
is not a Horizonmicro or Horizoncompact.
For a Horizonmicro or Horizoncompact,
this field is inherited from the Hardware
Version Number (HVN), and cannot be
changed.

0 - 15
characters

Optional.

4-55
Jan 2010

Cabinet Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Permitted cabinet_type modifications and restrictions

The BSS allows the operator to modify the value of cabinet_type as shown in Table 4-26.

Table 4-26 Permitted cabinet_type modifications and restrictions

Source cab type

Target cab type

Restrictions on source cab

HORIZONMACRO2

HORIZON2MINI or
HORIZON2MICRO

Fewer than 2 BTPs equipped;

DRI and EAS not equipped;
single frequency type.

HORIZON2MINI or
HORIZON2MICRO

HORIZON2MACRO or
HORIZON2MINI or
HORIZON2MICRO

DRI and EAS not equipped.

TCU_2 or TCU_6 or
HORIZONMACRO_EXT
or HORIZONMACRO2_EXT
or HORIZON2MINI_EXT

HORIZON2MICRO_EXT

DRI and EAS not equipped;

single frequency type
excluding PCS1900.

HORIZON2MICRO_EXT

HORIZONMACRO2_EXT or
HORIZON2MINI_EXT

DRI and EAS not equipped.

Additional Information
Use the Additional Information window to input any notes relating to this Cabinet. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

4-56

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cabinet Detailed View fields

General grouping
Table 4-27 describes the fields in the General grouping of the Cabinet Detailed View.

Table 4-27 Cabinet Detailed View fields - General grouping

Brief description

Values

Mandatory
or Optional?

Frequency Type
frequency_type
(OMC-R
parameter name:
freq_type)

The frequency band capability of the Cabinet.

If the Infrastructure Sharing Homogeneous
Cabinet feature is restricted, then only
required for the first Cabinet created at
a site. Thereafter, the frequency type of
future Cabinets should be forced to the
freq_type of the first Cabinet. If cabinet_type
is M-Cellmicro, then only one frequency
type is allowed regardless of whether
the Infrastructure Sharing Homogenous
or Heterogenous features are restricted
(disabled) or not.
Horizon II and Horizon II mini sites can
support one of the following frequencies:
PGSM, EGSM, or DCS1800.

1 - 15.

Optional.

Power Supply
Unit 1 to 4
psu_fru_1 to
psu_fru_4

The type of the first, second, third, and fourth

power supply units (PSUs) out of four PSUs
installed in the cabinet, if any. PSUs 1 to 3 are
valid for Horizonmacro, Horizonmacro_ext,
Horizon II macro and Horizon II macro_ext
cabinet types. PSU 4 is only valid for Horizon
II macro and Horizon II macro_ext cabinet
types.
When cabinet-type is a Horizon II mini
psu_fru_1 and psu_fru_2 are displayed.
psu_fru_1 displays hardware information
for the Power Supply Unit at the Horizon II
mini cabinet. psu_fru_2 indicates whether a
battery hold-up unit is present in the Horizon
II mini cabinet.
These fields are not visible for any other
cabinet types. Cannot be modified by a user
(read only).

Internal HDSL
Modem
(OMC-R
parameter name:
int_hdsl_modem)

Indicates whether an internal HDSL modem

is present in the cabinet. When cabinet type
is Horizonmacro, or Horizonmacro_ext this
field is grayed-out. For a Horizon II mini,
Horizon II mini extension, Horizon II macro,
and Horizon II macro extension, this field
does not appear.

Field name/BSS
parameter name

Optional.

0 or 1.
Internal
HDSL
modem
is not
present (0).
Internal
HDSL
modem is
present (1).

Optional.

Continued

68P02901W17-T

4-57
Jan 2010

Equipping a cabinet using the TTY interface

Chapter 4: Configuring a BSS/RXCDR

Table 4-27 Cabinet Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name
Internal
Integrated
Antennae
int_integrated
_ant

Brief description
Indicates whether an internal integrated
antenna is present in the cabinet.
When cabinet type is Horizonmacro or
Horizonmacro_ext this field is grayed-out.
For a Horizon II mini, Horizon II mini
extension, Horizon II macro, and Horizon II
macro extension, this field does not appear.

Mandatory
or Optional?

Values
0 or 1.
Internal
integrated
antenna
is not
present (0).
Internal
integrated
antenna is
present (1).

Optional.

Equipping a cabinet using the TTY interface

To equip a cabinet at a previously equipped BSC site, follow these steps:

Procedure 4-17 Equip a Cabinet at the TTY interface

1

Enter the following command:

equip <location> CAB
The system prompts for further configuration information, for example:
Enter the CABINET:
Enter the cabinet type:
Enter the frequency type:

At the prompts, enter the required configuration information.

Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on BSS commands, parameters, and prompts.

4-58

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a cage

Configuring a cage

Creating a cage using the OMC-R GUI

To create an instance of a Cage device using the OMC-R GUI, proceed as follows:

Procedure 4-18 Create a Cage instance using the OMC-R GUI

1

Navigate to and select the Cage class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Hardware Devices
Cage). If necessary, see Navigating to a network object class or
instance on page 1-28 for further details. The network object class
button changes color.

Select Edit Create from the Navigation Tree menu bar. The Cage
Detailed View form is displayed.

Enter all required information in this form. See Cage Detailed View
fields for further details.

Select File Create from the menu bar to create the cage instance.

Select File Close from the menu bar to close the Detailed View.

Cage Detailed View fields

The following sections list and briefly describe the parameter fields in the Cage Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

68P02901W17-T

4-59
Jan 2010

Cage Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Identification grouping
Table 4-28 describes the fields in the Identification grouping of the Cage Detailed View.

Table 4-28 Cage Detailed View fields - Identification grouping

Field name

Values

Brief description

Mandatory or
Optional?

RDN Class

See Table 4-1 description.

Default is Cage.

RDN Instance

See Table 3-1 description.

For a BSC or
RXCDR, cage
range is 0 - 13.
For a BTS, cage
range is 2-15.

NMC RDN Value

See Table 4-1 description.

Parent Detailed View

Displays the name of the

parent site (BSC or BTS).
Click to display the parent site
Detailed View.

Cabinet Identifier

The identifier of the cabinet in

which this cage resides.

IAS Connected

Whether an IAS is connected

to this cage. Not used if
cabinet_type is PCU.

IAS not connected,

or IAS is
connected.

Mandatory.

KSWX Number 0

The KSWX device which is

connecting the cage to a KSW
for TDM0 in another cage.
Not used if TDM0 or the KSW
resides in this cage. Not used
if cabinet_type is PCU.

0 - 4

Optional.

KSWX Number 1

The KSWX device which is

connecting the cage to a KSW
for TDM1 in another cage.
Not used if TDM1 or the KSW
resides in this cage. Not used
if cabinet_type is PCU.

0 - 4

Optional.

KSW Pair

The KSW pair managing

this cage. Not used if
cabinet_type is PCU.

0 - 3

Optional.

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this Cage. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

4-60

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping a cage from the TTY interface

Equipping a cage from the TTY interface

To equip a cage using the TTY interface, follow these steps:

Procedure 4-19 Equip a Cage at the TTY interface

1

Enter the following command:

equip <location> CAGE
The system responds with the prompts for further information.

At the displayed prompts, enter the appropriate configuration

information.

Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on BSS commands and parameters.

68P02901W17-T

4-61
Jan 2010

Configuring an RXCDR cabinet

Chapter 4: Configuring a BSS/RXCDR

Configuring an RXCDR cabinet

Overview of configuring an RXCDR cabinet

Equipping a cabinet can be carried out using either the:

OMC-R GUI.

equip command from a TTY session.

RXCDR cabinet numbers

When equipping cabinets at an RXCDR, the numbers 0 to 15 may be assigned for reference
purposes.

Creating an RXCDR cabinet using the OMC-R GUI

To create an RXCDR cabinet Navigation Tree, proceed as follows:

Procedure 4-20 Create an RXCDR cabinet using the OMC-R GUI

1

Navigate to and select the Cabinet class button in the Navigation Tree
(RXCDR RXCDR instance SITE SITE instance Hardware
Devices Cabinet). If necessary, see Navigating to a network object
class or instance on page 1-28 for further details. The network object
class button changes color.

Select Edit Create from the Navigation Tree menu bar. A Cabinet
Detailed View form is displayed.

Enter all required information in this form. See Configuring a cabinet

on page 4-54 for details of the Cabinet Detailed View fields.

NOTE
To obtain the relevant information for a parameter, click
Help at the top right of the window, select On Context and
drag the ? prompt to the appropriate field and click that
field. A context-sensitive help page is displayed.

4-62

Select File Create from the menu bar to create an RXCDR cabinet.

Select File Close to close the Detailed View form.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping an RXCDR cabinet using the TTY interface

Equipping an RXCDR cabinet using the TTY interface

See Example of equipping an RXCDR cabinet and cage using the TTY interface on page 4-65.

68P02901W17-T

4-63
Jan 2010

Configuring an RXCDR cage

Chapter 4: Configuring a BSS/RXCDR

Configuring an RXCDR cage

Overview of configuring an RXCDR cage

Configuring a cage can be carried out using either the:

OMC-R GUI.

equip command from a TTY session.

RXCDR cage numbers

When equipping cages at an RXCDR, the numbers 0 to 13 may be assigned with the first
equipped cage assigned number 0, the second cage assigned number 1, and so on.

Creating an RXCDR cage using the OMC-R GUI

To create an instance of a Cage device using the OMC-R GUI, proceed as follows:

Procedure 4-21 Create an RXCDR Cage instance using the OMC-R GUI
1

Navigate to and select the Cage class button in the Navigation Tree
(RXCDR RXCDR instance SITE SITE instance Hardware
Devices Cage). If necessary, see Navigating to a network object
class or instance on page 1-28 for further details. The network object
class button changes color.

Select Edit Create from the Navigation Tree menu bar. A CAGE
Detailed View form is displayed.

Enter all required information in this form. See Configuring a cage on

page 4-59 for details of the Cage Detailed View fields.

NOTE
To obtain the relevant information for a parameter, click
Help at the top right of the window, select On Context and
drag the ? prompt to the appropriate field and click that
field. A context-sensitive help page is displayed.

4-64

Select File Create from the menu bar to create an RXCDR cage.

Select File Close from the menu bar to close the Detailed View form.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

equipping an RXCDR cabinet and cage using the TTY interface

Example of

Example of equipping an RXCDR cabinet and cage using

the TTY interface

Scenario
In this example, an RXCDR cabinet is equipped at MSC_XCDR. The following information is
available:

The RXCDR cabinet is number 0.

The cabinet is equipped with one cage, numbered 0.

NOTE
The RXCDR examples shown in this section are for demonstration purposes only.
Parameters are system specific and will vary.

Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the BSS commands, parameters, and prompts.

Equipment
Cage 0 is equipped with the following required and optional devices:

EAS (half size PIX module).

MSI.

XCDR.

KSW A and KSW B.

GCLK A and GCLK B.

GPROC.

68P02901W17-T

4-65
Jan 2010

Overall procedure list

Chapter 4: Configuring a BSS/RXCDR

Additional equipment
Although there is no equip procedure for the following devices, they must be physically inserted
when more than one cage is equipped:

CLKX (half size modules, cage 0 only).

KSWX (half size modules).

NOTE
The Bus Terminator Card (BTC) is always provided in a BSC (or BTS or RXCDR)
cage.

Overall procedure list

The following steps are required when equipping cabinets and cages at an RXCDR site using the
TTY interface:

Procedure 4-22 Equip RXCDR cabinet and cages using TTY interface
1

Select the RXCDR site and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Equip the cabinet using the equip command, see the following sections.

Equip a cage using the equip command, see the following sections.

Equipping the RXCDR cabinet using the TTY interface

The following provides example input and output for equipping RXCDR cabinets.
-> equip 0 CAB
Enter the CABINET identifier: 0
Enter the cabinet type: 3
COMMAND ACCEPTED
->

4-66

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping the RXCDR cage using the TTY interface

Equipping the RXCDR cage using the TTY interface

At an RXCDR site, cage numbers are unique. The numbers can range from 0 - 13; the first
equipped cage assigned number 0 and the second assigned number 1. The following provides
example input and output for equipping the BSUs using the example data.
-> equip 0 CAGE
Enter the identifier for the CAGE: 0
Enter the KSW pair that manages the CAGE: 1
Enter the KSWX connecting cage to KSW for TDM 0:
Enter the KSWX connecting cage to KSW for TDM 1:
Enter cabinet to which the cage belongs:
0
Is an IAS connected?:

no

COMMAND ACCEPTED
->

68P02901W17-T

4-67
Jan 2010

Configuring an Assoc_BSS

Chapter 4: Configuring a BSS/RXCDR

Configuring an Assoc_BSS

Description of an Assoc_BSS
An Assoc_BSS (ABSS) specifies the actual BSS connected to the RXCDR. An Assoc_BSS is
said to be contained by an RXCDR.
A maximum of ten Assoc_BSSs can be supported by each RXCDR.
There is one Assoc_BSS device for each BSS connected to the RXCDR.
Performing an action on a Assoc_BSS in effect performs the action on the XBLs contained
within the Assoc_BSSs.
If the actual BSS is deleted from the network, the BSS identifier in the Assoc_BSS Detailed View
is set to NULL. This indicates that the Assoc_BSS does not correspond to any BSS device.
When an Assoc_BSS is created, a CommsLink is automatically created. Likewise, when an
Assoc_BSS is deleted, the CommsLink is automatically deleted.

Prerequisites to creating an Assoc_BSS

An Assoc_BSS can only be created if:

The BSS exists.

The parent device has been defined in advance, that is, an RXCDR.

Creating an Assoc_BSS using the OMC-R GUI

To create an Assoc_BSS to the network using the OMC-R GUI, follow these steps:

Procedure 4-23

Create an Assoc_BSS to the network using OMC-R GUI

Navigate to and select the Assoc_BSS class button in the Navigation

Tree (RXCDR RXCDR instance Assoc_BSS). If necessary, see
Navigating to a network object class or instance on page 1-28 for
further details.
The Assoc_BSS class button changes color.

Select Edit Create from the Navigation Tree menu bar.

The OMC-R displays the Assoc_BSS Detailed View in Create mode.

Click the Associated BSS button.

The OMC-R displays a popup window which lists all the BSSs currently
in the network.
Continued

4-68

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Procedure 4-23

Assoc_BSS Detailed View fields

Create an Assoc_BSS to the network using OMC-R GUI (Continued)

Select the BSS to be associated with this RXCDR.

This highlights the BSS.

Click OK. The OMC-R displays the name of the selected BSS in the
Associated BSS field.

Complete the remaining fields as required.

See Assoc_BSS Detailed View fields for details of these fields.

NOTE
To obtain the relevant information for a parameter, select
Help - On Context from the menu and drag the ? prompt to
the appropriate field and click that field. A context-sensitive
help page is displayed.
7

From the menu bar, select File Create to create the Assoc_BSS
details.

From the menu bar, select File Close to close the Detailed View.

Assoc_BSS Detailed View fields

The following sections list and briefly describe the parameter fields in the Assoc_BSS Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 4-29 describes the fields in the Identification grouping of the Assoc_BSS Detailed View.

Table 4-29 Assoc_BSS Detailed View fields - Identification grouping

Field name

Brief description

Values

RDN Class

See Table 4-1 description.

Default is
Assoc_BSS.

RDN Instance

See Table 3-1 description.

1 - 128.

NMC RDN Value

See Table 4-1 description.

Mandatory or
Optional?

Continued

68P02901W17-T

4-69
Jan 2010

Deleting an Assoc_BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-29 Assoc_BSS Detailed View fields - Identification grouping (Continued)

Field name

Brief description

Parent Detailed View

Displays the name of the

parent object. Click to display
the parent RXCDR Detailed
View.

Associated BSS

Displays the identifier of the

associated BSS.

Values

Mandatory or
Optional?
Not applicable.

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this Assoc_BSS. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard object status information fields, see Table 4-2 for details.

General grouping
Table 4-30 describes the fields in the General grouping of the Assoc_BSS Detailed View.

Table 4-30 Assoc_BSS Detailed View fields - General grouping

Field name

Brief description

UL and DL Volume
Control Type

See description in Table 4-7.

Downlink Audio Level

Offset

See description in Table 4-7.

Uplink Audio Level

Offset

See description in Table 4-7.

Values

Mandatory or
Optional?

Deleting an Assoc_BSS using the OMC-R GUI

To delete an existing instance of an Assoc_BSS using the OMC-R GUI, refer to the general
procedure in Deleting a network object using the OMC-R GUI.

Creating an Assoc_BSS using the TTY interface

To add an Assoc_BSS to the network using the TTY interface, use the equip command. For
example: equip 0 ABSS

4-70

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying Assoc_BSS details using the TTY interface

The system responds by displaying the prompts for the ABSS parameters. Technical Description:
BSS Command Reference (68P02901W23) gives details of all commands, command prompts,
and parameters.

Displaying Assoc_BSS details using the TTY interface

To display information for an Assoc_BSS using the TTY interface, use the disp_equipment
command. For example: disp_equipment 0 ABSS 1
The system responds by displaying details of the Assoc_BSS. See Technical Description: BSS
Command Reference (68P02901W23) for further details.

Setting Assoc_BSS parameters using the TTY interface

To set other parameters at an Assoc_BSS, use the modify_value command, and the appropriate
volume_control_type, dl_audio_lev_offset or ul_audio_lev_offset parameter. For example, to
change the Uplink and Downlink Volume Control Type to CCDSP (0), use:
modify_value 0 volume_control_type 0 ABSS 1

Deleting an Assoc_BSS using the TTY interface

To delete an Assoc_BSS using the TTY interface, use the unequip command. For example, to
delete ABSS 5, use the following command:
unequip 0 ABSS 5

68P02901W17-T

4-71
Jan 2010

Configuring an Assoc_RXCDR

Chapter 4: Configuring a BSS/RXCDR

Configuring an Assoc_RXCDR

Description of an Assoc_RXCDR
An Assoc_RXCDR (AXCDR) specifies the actual RXCDR connected to the BSS. An Assoc_RXCDR
is said to be contained by a BSS.
There is one Assoc_RXCDR for each RXCDR connected to the BSC.
A maximum of ten Assoc_RXCDRs can be supported by each BSS.
Performing an action on a Assoc_RXCDR in effect performs the action on the XBLs contained
within the Assoc_RXCDR.
The Conn_Link object class is a child of an Assoc_RXCDR.
Assoc_RXCDRs only exist if remote transcoding is specified at the BSS.
When an Assoc_RXDCR is created, a CommsLink is automatically created. Likewise, when an
Assoc_RXCDR is deleted, the CommsLink is automatically deleted.

Prerequisites to creating an Assoc_RXCDR

An Assoc_RXCDR can only be created if:

Remote transcoding has been specified at the BSS.

The RXCDR exists in the network.

A BSS exists in the network.

Creating an Assoc_RXCDR using the OMC-R GUI

To create an Assoc_RXCDR using the OMC-R GUI, follow these steps:

Procedure 4-24 Create an Assoc_RXCDR using the OMC-R GUI

Navigate to and select the Assoc_RXCDR class button in the Navigation

Tree (RXCDR RXCDR instance Assoc_RXCDR). If necessary, see
Navigating to a network object class or instance on page 1-28 for
further details. The Assoc_RXCDR class button changes color.

Select Edit Create from the Navigation Tree menu bar. The OMC-R
displays the Assoc_RXCDR Detailed View in Create mode.
Continued

4-72

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Assoc_RXCDR Detailed View fields

Procedure 4-24 Create an Assoc_RXCDR using the OMC-R GUI (Continued)

3

Click the Associated RXCDR button. The OMC-R displays a popup

window which lists all the RXCDRs currently in the network.

Select the RXCDR to be associated with this BSS. This highlights the
RXCDR.

Click OK. The OMC-R displays the name of the selected RXCDR in the
Associated RXCDR field.

Complete the remaining fields, as required. See Assoc_RXCDR

Detailed View fields for further details.

From the menu bar, select File Create to create the Assoc_RXCDR.

From the menu bar, select File Close to close the Detailed View.

Assoc_RXCDR Detailed View fields

The following sections list and briefly describe the parameter fields in the Assoc_RXCDR
Detailed View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 4-31 describes the fields in the Identification grouping of the Assoc_RXCDR Detailed View.

Table 4-31

Assoc_RXCDR Detailed View fields - Identification grouping

Field name

Brief description

Values

RDN Class

See Table 4-1 description.

Default is
Assoc_RXCDR.

RDN Instance

See Table 3-1 description.

1 - 128.

NMC RDN Value

See Table 4-1 description.

Parent Detailed View

Displays the parent BSS

Detailed View.

Associated RXCDR

Displays the name of the

associated RXCDR.

68P02901W17-T

Mandatory or
Optional?

Mandatory.

4-73
Jan 2010

Assoc_RXCDR Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Additional Information
Use the Additional Information window to input any notes relating to this Assoc_RXCDR.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard object status information fields, see Table 4-2 for details.

Local Routing Information grouping

Table 4-32 describes the fields in the Local Routing Information grouping of the Assoc_RXCDR
Detailed View.

Table 4-32 Assoc_RXCDR Detailed View fields - Local Routing Information grouping
Field name/BSS
parameter name

Brief description

CIC Validation
cic_validation

See Enhanced XBL (EXBL) on

page 2-11 for further details.

Mandatory or
Optional?

Values

Mandatory.

General grouping
Table 4-33 describes the fields in the Local Routing Information grouping of the Assoc_RXCDR
Detailed View.

Table 4-33 Assoc_RXCDR Detailed View fields - General grouping

Field name

4-74

Brief description

Values

Mandatory or
Optional?

{34452} AMR Home

Filter Enabled
amr_home_filter
_enabled

Specifies whether the

AMR homing filter is
enabled or not.

Range is 0 to 1.
0 disabled.
1 enabled.
Default is 0.

Optional.

{34452} Cage
Management Enabled
cage_manage_enabled

Used to enable or disable

the cage management
feature.

Range is 0 to 1.
0 disabled.
1 is enabled.
Default is 1.

Optional

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Assoc_RXCDR Detailed View fields

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)
grouping
Table 4-34 describes the fields in the Channel Mode Usage (AMR Full Rate and Half Rate/GSM
Half Rate) grouping of the Assoc_RXCDR Detailed View. The fields in this grouping are
grayed-out if both amrEnhancedCapOpt and gsmHalfRateOpt are restricted. (see Adaptive
Multi-Rate (AMR) on page 2-129 and GSM Half Rate on page 2-140 for additional information).

Table 4-34
grouping

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)

Field name/BSS
parameter name

Mandatory or
Optional?

Brief description

Values

Enhanced
Auto Connect
Modeeac_mode

Whether the BSC-RXCDR

interface is using the
available resources for
half rate calls with 8
kbit/s Ater allocations.
If cic_validation (see
Table 4-32) is disabled, this
field is grayed-out and set to
Disabled (0).

0 or 1. Disabled
(0) or Enabled (1).
Default is 0.

Optional.

CIC Blocking
Thresho ld
cic_block_thresh

Threshold used to block

CICs according to the
availability of IDLE Aters.
Only sensitive if eac_mode
is set to Enabled (1) and
if AMR and/or GSM HR
features are unrestricted.

0 - 245.
Default is 0.

Optional.

CIC Unblocking
Threshold
cic_unblock_thresh
(OMC-R parameter
name:
CicUnblockThresh)

Threshold used to unblock

CICs according to the
availability of IDLE Aters.
Only sensitive if eac_mode
is set to Enabled (1) and
the AMR and/or GSM HR
features are unrestricted.
cic_unblock_thresh
must be greater than
cic_block_thresh by a
value of 10 or more.

0, 11 - 255.
Default is 0.

Optional.

NOTE
The CIC blocking mechanism can be formally disable by setting cic_block_thresh
and cic_unblock_thresh to 245 and 255 respectively. It should be noted however,
that if no 16 kbit/s ATERs are available, then full rate calls are prevented from being
set up and only half rate calls are accepted.

68P02901W17-T

4-75
Jan 2010

Creating an Assoc_RXCDR using the TTY interface

Chapter 4: Configuring a BSS/RXCDR

Creating an Assoc_RXCDR using the TTY interface

To create an Assoc_RXCDR using the TTY interface, use the equip command. For example:
equip 0 AXCDR
The system responds by displaying the following prompts (bold text shows example user
responses):
Enter the AXCDR device id:
Perform CIC validation:

YES

Enable Enhanced Auto-Connect Mode:

yes

Enter the CIC blocking threshold:

<CR>

Enter the CIC unblocking threshold:

<CR>

COMMAND ACCEPTED

Displaying Assoc_RXCDR details using the TTY interface

To display information for an Assoc_RXCDR using the TTY interface, use the disp_equipment
command. For example:
disp_equipment 0 AXCDR 1
The system responds by displaying details of the Assoc_RXCDR. See Technical Description: BSS
Command Reference (68P02901W23) for further details.

Enabling/Disabling CIC Validation at an Assoc_RXCDR using

the TTY interface
To enable CIC Validation at an RXCDR using the TTY interface, use the modify_value command.
For example:
modify_value 0 cic_validation YES AXCDR 1
The system responds:
WARNING: Any CIC equipage inconsistencies between BSC and RXCDR may result
in dropped calls.
Do you want to continue (Y/N) : Y
COMMAND ACCEPTED
To disable CIC Validation at an Assoc_RXCDR, use the modify_value command. For example,
the following command disables cic_validation (sysgen on) whether AMR Half Rate, GSM Half
Rate, and eac_mode are enabled:
modify_value 0 cic_validation NO AXCDR 1

4-76

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Changing eac_mode and cic_block_thresh

The system responds:

WARNING: The AXCDR will not support AMR/GSM HR when CIC Validation is disabled.
A confirmation dialogue box is also displayed:
WARNING: Disabling CIC Validation will cause this AXCDR to be cycled, resulting
in the loss of all call traffic to this RXCDR.

Changing eac_mode and cic_block_thresh

To enable eac_mode (with SYSGEN on or off) with cic_validation, amr_bss_half_rate_enabled
and gsm_bss_half_rate_enabled enabled, use the modify_value command. For example, the
following command modifies eac_mode to Yes at Assoc_RXCDR 128:
modify_value 0 eac_mode yes AXCDR 128
The following command enables eac_mode (with SYSGEN on or off) with cic_validation
enabled, amr_bss_half_rate_enabled disabled and gsm_bss_half_rate_enabled disabled:
modify_value 0 eac_mode yes AXCDR 128
The system responds:
COMMAND ACCEPTED WARNING: AMR and GSM Half Rate is currently disabled at this
BSC.
To disable eac_mode when AMR and GSM Half Rate features are unrestricted, (with SYSGEN
on or off), cic_validation, amr_bss_half_rate_enabled and gsm_bss_half_rate_enabled
enabled, use the modify_value command. For example, the following command modifies
eac_mode to No at Assoc_RXCDR 128:
modify_value 1 eac_mode no AXCDR 128
The system responds:
WARNING: Disabling enhanced auto connect mode will terminate all active calls
through this Associated RXCDR from this BSC, and reconfigure the CIC Ater
assignments as for Auto Connect Mode.
The following command modifies cic_unblock_thresh to 100 at Assoc_RXCDR 128:
modify_value 0 cic_unblock_thresh 100 AXCDR 128
The following command attempts to modify cic_unblock_thresh to 10 at Assoc_RXCDR 128:
modify_value 0 cic_unblock_thresh 10 AXCDR 128
The system responds:
COMMAND REJECTED: The valid range is 0 to disable cic_unblock_thresh or 11-255
to enable it.
The following command attempts to modify cic_unblock_thresh to 29 when
cic_unblock_thresh is currently 40 and cic_block_thresh is 20:
modify_value 0 cic_unblock_thresh 29 AXCDR 128
The system responds:

68P02901W17-T

4-77
Jan 2010

Changing AMR Half Rate mode using the TTY interface

Chapter 4: Configuring a BSS/RXCDR

COMMAND REJECTED: CIC unblocking threshold must be greater than the CIC blocking
threshold by a value of 10.
The following command attempts to modify cic_unblock_thresh to 20 at Assoc_RXCDR 128
when eac_mode is disabled:
modify_value 0 cic_unblock_thresh 20 AXCDR 128
The system responds:
COMMAND REJECTED: Cannot modify CIC blocking or unblocking thresholds if Enhanced
Auto-Connect Mode is disabled

Changing AMR Half Rate mode using the TTY interface

The following command disables amr_bss_half_rate_enabled (with SYSGEN on or off) with
either cic_validation and/or eac_mode enabled:
chg_element amr_bss_half_rate_enabled no 0
The system responds:
WARNING: AXCDR CIC validation and/or enhanced auto connect mode are currently enabled
COMMAND ACCEPTED

Changing GSM Half Rate mode using the TTY interface

The following command disables gsm_bss_half_rate_enabled (with SYSGEN on or off) with
either cic_validation and/or eac_mode enabled:
chg_element gsm_bss_half_rate_enabled 1 0
The system responds:
WARNING: This may cause a short delay in a new call setup during reconfiguration.
COMMAND ACCEPTED

NOTE

If an AXCDR with cic_validation enabled does not exist, the system also
responds:

If the parameter handover_required_sp_ver_used is disabled in the BSS

Detailed View, the system responds:

WARNING: AXCDR CIC validation must be enabled for AMR or GSM HR.

Unable to enable EFR/AMR or GSM HR when handover_required_sp_ver_used is set to disabled

The following command enables gsm_bss_half_rate_enabled (with SYSGEN on or off) with
either cic_validation and/or eac_mode enabled:
4-78

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting an Assoc_RXCDR using the OMC-R GUI

chg_element gsm_bss_half_rate_enabled 0 1
The system responds:
WARNING: This may cause a short delay in a new call setup during reconfiguration.
COMMAND ACCEPTED

Deleting an Assoc_RXCDR using the OMC-R GUI

To delete an existing instance of an Assoc_RXCDR using the OMC-R GUI, refer to the general
procedure in Deleting a network object using the OMC-R GUI.

Deleting an Assoc_RXCDR using the TTY interface

To delete an Assoc_RXCDR using the TTY interface, use the unequip command. For example, to
delete AXCDR 10, use the following command:
unequip 0 AXCDR 10

68P02901W17-T

4-79
Jan 2010

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

Chapter 4: Configuring a BSS/RXCDR

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

Introduction to changing the NE ID of an AXCDR or ABSS

After configuring either an Assoc_RXCDR (AXCDR) or Assoc_BSS (ABSS), the user may realize
they have given the ABSS or AXCDR the wrong Network Entity (NE) id. The user can change
the NE ID of the AXCDR or ABSS using the OMC-R GUI, which then propagates the new NE
ID to all the related connections.
For example, a user connected an RXCDR to a BSC and labeled the NEs: RXCDR-5, BSC-10,
and AXCDR-5. The user then performed up to 21 add_conn commands (which all referenced
AXCDR-5), equipped 20 XBLs, and up to 2400 CICs. The user then discovers that the RXCDR
connected to BSC-10 has an NE id of 7 instead of 5. To correct this problem, the user would
have to unequip all CICs, XBLs, and connectivity entries referencing AXCDR-5 and then re-equip
these devices to the new AXCDR-7. Instead, the user can initiate a single request at the OMC-R
GUI to propagate changes to all the affected devices and connectivity entries. This is done using
the Change Assoc NE ID menu option. The same situation could occur for a ABSS device in
an RXCDR database.
The change assoc NE ID operation only changes the identifier of an AXCDR (or ABSS) in a BSS
(or RXCDR) database. If the user changes the identifier of an NE, the user must also change the
identifier in the NE database and, if necessary, use the change assoc NE ID operation to change
the associated device id in each database which includes the NE as an associated device. For
example, BSS-1 and BSS-2 are connected to RXCDR-3, and AXCDR-3 is equipped in BSS-1
and BSS-2 databases. To change the NE id for RXCDR from 3 to 5, the user must change the
id of the RXCDR in the RXCDR database, and then start the change assoc NE ID operation on
AXCDR-3 at BSS-1 and BSS-2 to set the new AXCDR id to 5.

NOTE
Once the change assoc NE ID process has started, if the GUI is closed for some
reason the change assoc NE ID process continues.

Phases in the change assoc NE ID process

The change assoc NE ID operation has three phases:

Extract.

Unequip.

Re-equip

The progress of the change assoc NE ID operation is displayed in the status bar and also in the
change assoc NE ID process log file, which is displayed in an Xterm window when the change
assoc NE ID process is initiated.

4-80

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Change assoc NE ID process log files

Change assoc NE ID process log files

The change assoc NE ID process generates log files to show the progress of the change
operation.
The OMC-R creates the log files in the following directory:
/usr/omc/ne_data/assocneid_changer_logs.
The log file names have the following format:
<NEname>_<old_ne_id>_<new_ne_id>.<status>
Where:
<NEname> is the name of the BSS or RXCDR to which the ABSS/AXCDR being changed is
associated.
<old_ne_id> is the current (old) network entity id of the network element to be changed.
<new_ne_id> is the new network entity id of the network element.
<status> is the status of log file, which can be:

active - indicates an active log file, that is, one that is currently being written to by the
change process.

progress - a log file showing a summary of the progress of the change process. The
progress file is automatically displayed when the change process is initiated.

resume - indicates a halted change assoc NE ID process log file. Such a file is created
if the system suspends a change assoc NE ID process for some reason (for example, if
there is a GUI stop or start). The system can suspend a change process in any phase of
the process. This log file is used if the change assoc NE ID process is resumed. When
resumed, the log file has the extension .active.

complete - a log file of a completed change assoc NE ID process. This file name is suffixed
with a time stamp.

For example, changing RXCDR1 NE id 5 to NE id 6 on BSS1018, creates an active log file

named: BSS1018_5_6.active. If the change assoc NE ID process continues successfully a
log file called BSS1018_5_6.progress is also created. Finally, when the change process is
complete a log file called BSS1018_5_6.complete is created.
The user can view any type of log file.

Prerequisites to changing an associated NE ID

To change the name of a Assoc_BSS or Assoc_RXCDR, CM access control must be enabled in the
user profile of the user. See OMC-R Online Help, Network Operations for further information
about user profiles.

68P02901W17-T

4-81
Jan 2010

Restrictions to changing an NE ID

Chapter 4: Configuring a BSS/RXCDR

Restrictions to changing an NE ID
Do not modify the database of the NE being changed until the change assoc NE ID process is
complete.
Do not start a change assoc NE ID operation for an associated device, if:

An Audit, Resync, Network Expansion, CellXchange, Bay Level Calibration, or cell

parameter propagation operation is in progress for the container NE.

cmutil updates are in progress in the container NE database.

Likewise, if a change assoc NE ID operation is in progress:

An Audit, Resync, Network Expansion, CellXchange, Bay Level Calibration, or cell

parameter propagation should not be started for the container NE.

A cmutil operation cannot be invoked for an NE or its containers.

Changing the NE ID of an ABSS or AXCDR using the OMC-R GUI

To change the NE ID of an Assoc_BSS or Assoc_RXCDR using the OMC-R GUI, follow these steps:

Procedure 4-25 Change NE ID of Assoc_BSS or Assoc_RXCDR using the OMC-R GUI

4-82

Navigate to and select the Assoc_BSS or Assoc_RXCDR instance button

in the Navigation Tree (for an Assoc_BSS, select: RXCDR - RXCDR
instance - Assoc_BSS - Assoc_BSS instance.
For an Assoc_RXCDR, select: BSS - BSS instance - Assoc_RXCDR Assoc_RXCDR instance.
The instance button changes color.

Select Options - Change Assoc NE ID from the menu bar. The Change
Assoc NE ID form is displayed, see Figure 4-4 for an example.
If a window is already open for the associated NE, the Change Assoc
NE ID form cannot be opened, and the active window is brought to the
foreground.
More than one Change Assoc NE ID form can be open at a time. If
necessary, the user can open other GUI forms while the Change Assoc
NE ID form is displayed.
The name of the selected instance is displayed in the title bar of the form.
The OMC-R displays the current network entity id of the ABSS or AXCDR
in the Current Assoc NE ID field. This field cannot be changed by a user.

Enter the new network entity id for the Assoc_BSS or Assoc_RXCDR in

the New Assoc NE ID field. Enter a unique value in the range 1 - 128.
If the new network entity id number is not unique, the OMC-R displays
a message in the status bar and rejects the new number. Enter a new
unique network entity number.
If the new network entity id is not known, go to Viewing network
entity ids step 1. Otherwise, go to Starting the change assoc NE
ID process - step 1.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Changing the NE ID of an ABSS or AXCDR using the OMC-R GUI

Figure 4-4 Change Assoc NE ID form (for an Assoc_RXCDR instance)

ti-GSM-ChangeAssocNEIDform_foranAssoc_RXCDRinstance_-00783-ai-sw

Viewing network entity ids

To display a list of all the network entities managed by the OMC-R, follow these steps:

Procedure 4-26 Display network entities

1

Click the View NE IDs button.

The BSSs or RXCDRs list form is displayed.
For example, if the selected element is a ABSS, a list of all BSSs is
shown. The BSSs/RXCDRs list form displays the following information
for each BSS or RXCDR managed by the OMC-R:

NE ID - the network entity id.

Version - the version number of the software load active in the

Network Element (BSS database parameter neLoadVersion).

Network Element - the name of the network element.

If required, click the Print button to print the list of NEs to the printer
specified in the PRINTER environmental variable.
2

Click the required network element in the list. The OMC-R highlights
the selection. To exit the list and return to the Change Assoc NE ID
form, click Cancel.
Continued

68P02901W17-T

4-83
Jan 2010

Changing the NE ID of an ABSS or AXCDR using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Procedure 4-26 Display network entities (Continued)

3

Click OK. The network entity id of the selected NE is copied into

the New Network Entity Id field in the Change Assoc NE ID form.
Double-clicking the network element in the NE List form has the same
result.

Now go to Starting the change assoc NE ID process - step 1.

Starting the change assoc NE ID process

To start the change assoc NE ID process, follow these steps:

Procedure 4-27 Start the change assoc NE ID process

1

Click OK.
When changing the NE ID of an Assoc_RXCDR, the OMC-R displays the
following message. An equivalent message is displayed when changing
an Assoc_BSS NE id. Use the scroll bars to display all of the message.
WARNING: Changing the Network Entity Id will result in loss
of all calls and communication between this RXCDR and the
BSS. The operation will first delete all the XBLs, CICs,
Conn_Links and Assoc_RXCDRs between this RXCDR and the BSS
in the BSS database. Then it will re-equip all the XBLs,
CICs, Conn_Links and Assoc_RXCDRs as it was originally in
the BSS database but with the new Network Entity Id. The
operation may take a long time to complete.
Do you wish to continue?

Click OK to continue with the change assoc NE ID process. To close

the confirmation box and return to the Change Assoc NE ID form, click
Cancel.

The OMC-R displays the status of the NE id change process in the

status bar, and the .process log file in an Xterm window. By default, the
status bar is one line deep.
To expand the status bar, click the [Symbol_triangledown] button to
the right of the status bar.
To shrink the status bar back to its original size, click the
[Symbol_triangleup] button.

To view the active log file for the change assoc NE ID process, go to
Viewing other log files below.

Figure 4-5 shows an example of the .progress log file with the Extracting phase complete, and
the Unequipping phase in progress.

4-84

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Figure 4-5

Viewing other log files

.progress log file

ti-GSM-progresslogfile-00784-ai-sw

Viewing other log files

To view other change assoc NE ID process log files, select Options - View Log from the menu bar
of the Change Assoc NE ID form. The OMC-R opens a Log File Selection window. An example is
shown in Figure 4-6.

68P02901W17-T

4-85
Jan 2010

Viewing other log files

Chapter 4: Configuring a BSS/RXCDR

Figure 4-6 Log File Selection window

ti-GSM-LogFileSelectionwindow-00785-ai-sw

Selecting an .active log file

To select an .active log file, follow these steps:

Procedure 4-28 View an active log file

4-86

Select the .active log file in the Files pane of the Log File Selection
window.

Click the View Active Log button to view the .active log file.
The text editor displays the contents of the .active log file in an Xterm
window (see Figure 4-7, for example). If necessary, use the Return key
to scroll through the log file.
If an active log file does not exist, the View Active Log button is
grayed-out and cannot be selected.

Now go to Closing the log file window step 1.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Viewing other log files

Figure 4-7 .active log file

ti-GSM-activelogfile-00786-ai-sw

68P02901W17-T

4-87
Jan 2010

Resuming a suspended change assoc NE ID process

Chapter 4: Configuring a BSS/RXCDR

Viewing an inactive log file

To view an inactive log file (such as, .complete log file) follow these steps:

Procedure 4-29

View an inactive log file

Navigate to another directory using the Filter line and button, and
select a log file.
Or, if necessary:
Click Cancel to close the window and return to the Change Assoc NE
ID window.

Click the View Log button to view the contents of an inactive log file.
The text editor displays the contents of the log file in an Xterm window.
Use the Return key to scroll through the log file.

Closing the log file window

To close the log file window, follow these steps:

Procedure 4-30

Close the log file window

Left-click the button in the top left corner of the window.

Select Close from the dropdown menu.

Resuming a suspended change assoc NE ID process

Prerequisites and restrictions
A change assoc NE ID operation can only be resumed if:

The change assoc NE ID process was suspended by the system (for example, if there is
was a GUI stop or start during the change process). The system may suspend the change
process during any phase in the process.

The change operation is resumed with the same old and new network entity id values.

The associated log file (<filename>.resume) exists for the suspended change NE ID
process.

NOTE
Before resuming a change assoc NE ID operation, ensure that no changes were
made to the database since the suspension and before the resume. Otherwise,
the change assoc NE ID reconfigurations may not be successful.

4-88

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Resuming a suspended change assoc NE ID process

Procedure
To restart a suspended change assoc NE ID process, select Options - Resume from the menu
bar of the Change Assoc NE ID form. The OMC-R resumes the change assoc NE ID process
from the point at which it was halted.

68P02901W17-T

4-89
Jan 2010

Configuring DYNETs and DYNETGroups

Chapter 4: Configuring a BSS/RXCDR

Configuring DYNETs and DYNETGroups

DYNET device
A DYNET device specifies the BTSs sharing dynamic terrestrial backing resources and how
they are interconnected. See Dynamic allocation of BSC-BTS Backing Resources (DYNET) on
page 2-19 for further details.
A DYNET is contained in a DYNETGroup. When the user creates the first DYNET using the TTY
interface, a DYNETGroup is automatically created. When the last DYNET in a DYNETGroup is
deleted, the DYNETGroup is automatically deleted.

Equipping path devices

When a DYNET is equipped, the path devices for the BTSs that supported the dynamic allocation
are also equipped.

Equipping RSLs
RSLs for BTS sites that support dynamic allocation must be equipped to the automatically
equipped paths associated with the DYNET.

DYNET restrictions
Restrictions and exceptions for a DYNET are as follows:

4-90

A DYNET can be equipped and unequipped, but cannot be locked, unlocked, or shutdown.

A DYNET can include BTSs with the SITE Detailed View field: Timeslot Sharing (parameter
name ts_sharing) disabled.

A DYNET can include BTSs with timeslot (TS) marker sites (switching sites).

All DYNETs that share the same first identifier must have the same BTSs, or marker sites
(switching sites), in the same order.

DYNETs must have different E1 links for the BTSs that have the SITE Detailed View field:
Timeslot Sharing (parameter name ts_sharing) enabled.

Equipping the DYNET also equips path devices for the BTSs supporting dynamic allocation
(that is, BTSs with Timeslot Sharing field (parameter name ts_sharing) enabled). For any
non-DYNET BTSs, paths have to be manually created.

DYNETs must include at least one BTS that has the Timeslot Sharing field (parameter
name ts_sharing) enabled.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

A DYNET device can only be equipped to a BSC.

There can be only three DYNETs per DYNETGroup.

More than one E1 link can exist between BTSs for dynamic sharing purposes.

DYNETGroup

DYNETGroup
A DYNETGroup represents a grouping of DYNETs.
When the user creates the first DYNET using the TTY interface, a DYNETGroup is automatically
created.
A DYNETGroup is contained by a BSS.

DYNETGroup restrictions
Restrictions and exceptions for a DYNETGroup are:

A maximum of 20 DYNETGroup objects can be supported per BSS.

A DYNETGroup is only visible on the Navigation Tree when BSC-BTSdynamic allocation is

enabled at the BSS (that is, the BSCBTSDynAllocOptparameter is set to Enabled (1)).

The DYNETGroup can include BTSs with the SITE Detailed View field: Timeslot Sharing
(parameter name ts_sharing) disabled.

A maximum of three DYNETs can be supported per DYNETGroup.

Fault management activities are not supported for a DYNETGroup object.

DYNETGroup and DYNET topics

The following sections contain further information about DYNETGroups and DYNETs:

Configuring a DYNETGroup on page 4-92, including creating and deleting using GUI or
TTY interface.

Configuring a DYNET on page 4-94, including creating, viewing, editing and deleting
using GUI or TTY interface.

68P02901W17-T

4-91
Jan 2010

Configuring a DYNETGroup

Chapter 4: Configuring a BSS/RXCDR

Configuring a DYNETGroup

Prerequisites to creating a DYNETGroup

A DYNETGroup cannot be created unless BSC-BTSdynamic allocation has been enabled at
the associated BSS, see Dynamic allocation of BSC-BTS Backing Resources (DYNET) on page
2-19 for further details.

Creating a DYNETGroup using the OMC-R GUI

To create a DYNETGroup using the OMC-R GUI, follow these steps:

Procedure 4-31 Create a DYNETGroup using the OMC-R GUI

1

Navigate to and select the DYNETGroup class button in the Navigation

Tree (BSS BSS instance DYNETGroup). If necessary, see
Navigating to a network object class or instance on page 1-28 for
further details. The class button changes color.

Select Edit Create from the menu bar. The OMC-R displays the
DYNETGroup Detailed View form in Create mode.

Complete the fields as required. See DYNETGroup Detailed View

fields for further information.

Select File Create from the menu bar to create the DYNETGroup.

Select File Close from the menu bar to close the DYNETGroup
Detailed View.

DYNETGroup Detailed View fields

The following sections list and briefly describe the parameter fields in the DYNETGroup Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

4-92

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping a DYNETGroup using the TTY interface

Identification grouping
Table 4-35 describes the fields in the Identification grouping of the DYNETGroup Detailed View.

Table 4-35

DYNETGroup Detailed View fields - Identification grouping

Field name

Brief description

Values

RDN Class

See Table 4-1 description.

Default is DYNET
Group.

RDN Instance

See Table 3-1 description.

0 - 19.

NMC RDN Value

See Table 4-1 description.

Parent Detailed View

Click to display the parent

BSS Detailed View.

Mandatory or
Optional?

Additional Information
Use the Additional Information window to input any notes relating to this DYNETGroup. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

Equipping a DYNETGroup using the TTY interface

When creating the first DYNET using the TTY interface, the OMC-R automatically creates a
DYNETGroup.
A DYNETGroup cannot be equipped using the TTY interface.

Deleting a DYNETGroup using the OMC-R GUI

A DYNETGroup cannot be deleted until all the DYNETs it contains have been deleted. When the
last DYNET is deleted, the OMC-R automatically deletes the DYNETGroup.

68P02901W17-T

4-93
Jan 2010

Configuring a DYNET

Chapter 4: Configuring a BSS/RXCDR

Configuring a DYNET

Path devices for a DYNET

When a DYNET is equipped for BSC-BTSdynamic allocation, the OMC-R automatically creates
the path devices and assigns path identifiers in the range 0 - 5. These values indicate that
the path has been automatically equipped.
When dynamic allocation is enabled at the corresponding site, valid path identifiers are available
in the range 6 - 9. When dynamic allocation is disabled at the corresponding site, valid path
identifiers are available in the range 0 - 9.
See Dynamic allocation of BSC-BTS Backing Resources (DYNET) on page 2-19 for further details.

Prerequisites to creating a DYNET

A DYNET cannot be created unless BSC-BTSdynamic allocation has been enabled at the
associated BSS and BTSs, see Dynamic allocation of BSC-BTS Backing Resources (DYNET) on
page 2-19.

Creating a DYNET using the OMC-R GUI

Prerequisite
Before creating a DYNET using the OMC-R GUI, a DYNETGroup must have been created.

Procedure
To create a DYNET, follow these steps:

Procedure 4-32 Create a DYNET using the OMC-R GUI

1

Navigate to and select the DYNET class button in the Navigation Tree
(BSS BSS instance DYNETGroup DYNETGroup instance
DYNET). If necessary, see Navigating to a network object class or
instance on page 1-28 for further details. The class button changes
color.

Select Edit Create from the Navigation Tree menu bar. The OMC-R
displays the DYNET Detailed View form in Create mode.
Continued

4-94

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DYNET Detailed View fields

Procedure 4-32 Create a DYNET using the OMC-R GUI (Continued)

3

Complete the fields as required. See DYNET Detailed View fields

for further details.

Select File Create from the menu bar to create the DYNET.

Select File Close from the menu bar to close the DYNET Detailed
View.

DYNET Detailed View fields

The following sections list and briefly describe the parameter fields in the DYNET Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 4-36 describes the fields in the Identification grouping of the DYNET Detailed View.

Table 4-36 DYNET Detailed View fields - Identification grouping

Field name

Brief description

Values

RDN Class

See Table 4-1 description.

Default is BSS.

RDN Instance

See Table 3-1 description.

0 - 2.

NMC RDN Value

See Table 4-1 description.

Parent Detailed View

Click to display the parent

DYNET Group Detailed View.

Mandatory or
Optional?

Additional Information
Use the Additional Information window to input any notes relating to this DYNET. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

68P02901W17-T

4-95
Jan 2010

DYNET Detailed View fields

Chapter 4: Configuring a BSS/RXCDR

Local Routing Information grouping

Table 4-37 describes the fields in the Local Routing Information grouping of the DYNET Detailed
View.

Table 4-37 DYNET Detailed View fields - Local Routing Information grouping
Field name/BSS
parameter name
Shared Timeslots
shared_timeslots

Brief description

Values

The number of timeslots

reserved at a DYNET for
BSC-BTSdynamic allocation.

0 - 31.
Default: 0.

Mandatory or
Optional?
Mandatory.

Path information grouping

Table 4-38 describes the fields in the path Information grouping of the DYNET Detailed View.

Table 4-38

DYNET Detailed View fields - path Information grouping

Values

Mandatory or
Optional?

Number of links in the

sequence for the DYNET. A
DYNET can have up to 11
links.

1 - 11.

Mandatory.

BSC MSI Id
msi_id

The MSI id at the BSC where

the MMS resides.

0 - 95.

Mandatory.

BSC MMS Id
mms_id

The MMS id for the BSC

network definition.

0 or 1.

Mandatory.

Field name/BSS
parameter name
No of Links
numInSequence

Brief description

Site Id
Site_id

The BTS site identifier, that

is, the terminating site.

1 to 100.

Mandatory.

Link 1 to Link 6
DYNET_link1
to
DYNET_link6

The first to sixth link in the

DYNET path.

Site Id
(0..100, 254).
Upstream MSI
(0..55, 254).
Upstream MMS
(0..1, 254).
Downstream
MSI (0..55, 254).
Downstream MMS
(0..1, 254).

Link 1 is
mandatory,
Link 2 to 6 are
optional.

Continued

4-96

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Modifying and deleting a DYNET using the OMC-R GUI

Table 4-38 DYNET Detailed View fields - path Information grouping (Continued)
Field name/BSS
parameter name

Mandatory or
Optional?

Brief description

Values

Link 7, 8, 9, 10
(DYNET_link7)

The seventh, eight, ninth and

tenth links in the DYNET
path.

Site Id
(0..100, 254).
Upstream MSI
(0..55, 254).
Upstream MMS
(0..1, 254).
Downstream
MSI (0..55, 254).
Downstream MMS
(0..1, 254).

Optional.

Link 11
(DYNET_link11)

The eleventh link in the

DYNET path. It can only
be used to make the final
loop-closing link back to the
BSC.

Site Id (0)
Upstream
MSI (0..55)
Upstream
MMS (0..1)
Downstream
MSI (0..55)
Downstream MMS
(0..1).

Optional.

TS Switch
(GUI only)

Determines whether the site

is a timeslot switching site.

Button on or off.

Modifying and deleting a DYNET using the OMC-R GUI

To modify DYNET parameters, see the general procedure in Modifying a network object using
the OMC-R GUI on page 1-34.
To delete a DYNET, see the general procedure in Deleting a network object using the OMC-R
GUI on page 1-37.

Configuring a DYNET using the TTY interface

For full details of command and parameters mentioned in the following sections, see Technical
Description: BSS Command Reference (68P02901W23).

Creating a DYNET using the TTY interface

When creating the first DYNET using the TTY interface, the OMC-R automatically creates a
DYNETGroup.
To equip a DYNET, use the equip command.
Example 1: To equip a BTS network that contains a single BTS that does not loop back to the
BSC, enter the following command:
equip 0 DYNET

68P02901W17-T

4-97
Jan 2010

Configuring a DYNET using the TTY interface

Chapter 4: Configuring a BSS/RXCDR

The system responds with prompts for further information. Bold text shows examples of user
responses:
Enter 1st and 2nd DYNET identifiers:
Enter BSC MMS identifiers:
Enter SITE identifier:

1 0

0 0

Enter upstream MMS identifiers:

0 0

Enter downstream MMS identifiers:

COMMAND ACCEPTED
Example 2: To equip a second set of E1 links for the BTS network defined in Example 1, enter
the following command:
equip 0 DYNET
The system responds with the following prompts. Bold text shows examples of user responses:
Enter 1st and 2nd DYNET identifiers:
Enter BSC MMS identifier:
Enter SITE identifier:

1 1

1 0

Enter upstream MMS identifiers:

1 1

Enter downstream MMS identifiers:

COMMAND ACCEPTED

Displaying DYNET parameters using the TTY interface

To display DYNET settings using the TTY interface, use the disp_equipment command. For
example, the following command displays settings for DYNET 1 0:
disp_equipment 0 DYNET 1 0
The systems responds by displaying all details for this DYNET.

Modifying DYNET parameters using the TTY interface

To edit DYNET parameters using the TTY interface, use the modify_value command and one
of the DYNET parameters. For example, the following command sets the number of timeslots
reserved for a BTS network to 10 at DYNET 1 0:
modify_value 0 shared_timeslots 10 DYNET 1 0

Displaying BSC-BTSdynamic allocation resources using the TTY interface

To display the timeslots which have been reserved for BSC-BTSdynamic allocation purposes,
use the disp_mms_ts_usage BSS command. When requested for a BSC MMS, this command
also displays the associated RTF and air timeslot. For example, the following command displays
resources for a BSC MMS:
disp_mms_ts_usage 0 0 0

4-98

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a DYNET using the TTY interface

Deleting a DYNET using the TTY interface

When the last DYNET is deleted, the OMC-R automatically deletes the DYNETGroup.
To delete a DYNET using the TTY interface, use the unequip command. For example, to unequip
a BTS network, enter the following command:
unequip 0 DYNET 1 0
The system responds:
WARNING: Calls on this DYNET may be dropped. Are you sure (Y = Yes, N = No)?
COMMAND ACCEPTED

68P02901W17-T

4-99
Jan 2010

Reparenting a BSS

Chapter 4: Configuring a BSS/RXCDR

Reparenting a BSS

Overview of reparenting a BSS

The procedure for reparenting a BSS depends on where the BSS is being moved to. The BSS
can be moved in either of the following ways:

From one OMC-R to another OMC-R.

From one RXCDR to another RXCDR (within the same OMC-R).

In addition, the RXCDR might itself be reparented from one MSC to another MSC.
The following sections detail reparenting procedures:

Reparenting a BSS to a different OMC-R on page 4-101.

Reparenting a BSS to a different RXCDR (same OMC-R) on page 4-104.

Reparenting an RXCDR to a different MSC on page 4-106.

Some reparenting procedures detailed in the following sections use cmutil. For further
information about cmutil, see Chapter 15 cmutil.

Preserving SITE names

The script preserve_site_names can be used to preserve site names during a reparent or drop
or recreate of MIB or MIB migration. This script is available in the /usr/omc/current/sbin
directory as part of the OMC-R product.
To use the preserve_site_names script, follow these steps:

Procedure 4-33 Use preserve_site_names script

1

As omcadmin, run the script in extract mode. This extracts the site
names for the BSS to be reparented.
For example:
preserve_site_names BSS BSS1019
The script creates a file in /usr/omc/ne_data/ called
<bss_name>.upd. This file should be stored in a new folder in
/usr/omc/ne_data/.

4-100

Once the BSS has been created (using the same BSS name as originally
used in the old OMC-R) and audited, the script can be run in update
mode. This updates the site names for the BSS which has been
reparented.
For example:
preserve_site_names update BSS1019

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reparenting a BSS to a different OMC-R

Reparenting a BSS to a different OMC-R

Prerequisites to reparenting a BSS to a different OMC-R

To assign a BSS to a different OMC-R (reparent a BSS), the BSS must be removed from its
original parent OMC-R and then added to the new parent OMC-R. In some cases, the BSS
might be reparented solely due to capacity problems in the old OMC-R and retains its RXCDR
connectivity. In other cases, the reparenting can involve connecting to different RXCDRs (and
MSCs).
The following prerequisites apply:

Change the OMC-R DTE addresses of the BSS to those of the new OMC-R. Use the BSS
Detailed view or the chg_dte command. Use OML to get the changes to take effect. The
old OMC-R then loses the connection to the BSS.

Ensure that the OML links between the BSS and old OMC-R have been disconnected.

Ensure that the OML links between the BSS and the new OMC-R have been properly
configured, by joining with the BSS field engineer.

If required, reconfigure the entries for the NE from the packet switch/MUX.

Reparenting a BSS to a different OMC-R

To assign a BSS (reparent a BSS) to a different OMC-R, the BSS must be removed from its
original (old) OMC-R and then added to the new OMC-R. This requires reparenting procedures
at the:

Old OMC-R.

New OMC-R.

Old OMC-R
At the old OMC-R, proceed as follows:

Procedure 4-34 At the old OMC-R, reparent a BSS to a different OMC-R

1

Extract all the MIB data for the selected BSS by using the following
command:
cmutil -x -h -i bss_name.ip -o <bss_name>.op
This file is required to create proxy cells, and also for keeping the
site names.
Continued

68P02901W17-T

4-101
Jan 2010

Reparenting a BSS to a different OMC-R

Chapter 4: Configuring a BSS/RXCDR

Procedure 4-34 At the old OMC-R, reparent a BSS to a different OMC-R (Continued)
2

Locate which cells of the BSS still have external neighbors in the old
OMC-R. These cells are added as proxy cells to the old OMC-R, once
the BSS has been HierDeleted.

Create a proxy cell input file from the extracted cells in the
bss_name.op file.
Name the file proxycell.ip

If using custom SITE names, obtain the script preserve_site_names,

as detailed in Preserving SITE names.
As omcadmin, run the preserve_site_names script in extract mode
as follows: preserve_site_names BSS <bss_name>
This extracts the site names for the BSS to be reparented.
For example:
preserve_site_names BSS BSS1019
The script creates the file /usr/omc/ne_data/<bss_name>.upd.

Store the file in /usr/omc/ne_data/ at the new OMC-R, and once the
BSS has been created (using the same BSS name as originally used in
the old OMC-R) and audited, the script can be run in update mode
as follows:
preserve_site_names update <BSS_name>
This updates the site names for the BSS which has been reparented.
For example:
preserve_site_names update BSS1019

At the old OMC-R, delete the BSS/RXCDR.

Refer to Deleting a BSS/RXCDR on page 4-44.

Add the proxy cells to the old OMC-R using the proxycell.ip file as
follows:
cmutil -a -i proxycell.ip

New OMC-R
At the new OMC-R, proceed as follows:

Procedure 4-35 At the new OMC-R reparent the BSS

1

Create the BSS. Refer to Overview of adding a BSS or RXCDR on page

4-2. Ensure that the BSS name given when creating the new BSS on the
Navigation Tree matches the name originally used in the old OMC-R.

Audit in the new BSS.

Continued

4-102

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reparenting a BSS to a different OMC-R

Procedure 4-35 At the new OMC-R reparent the BSS (Continued)

3

If using custom SITE names, after the audit, copy the file
/usr/omc/ne_data/ <bss_name>.upd from the original OMC-R. The
preserve_site_names script should also be stored in the new OMC-R.
The script can be run in update mode as follows:
preserve_site_names update <BSS_name>

This updates the site names for the BSS which has been reparented.
For example:
preserve_site_names update BSS1019

68P02901W17-T

4-103
Jan 2010

Reparenting a BSS to a different RXCDR (same OMC-R)

Chapter 4: Configuring a BSS/RXCDR

Reparenting a BSS to a different RXCDR (same OMC-R)

Prerequisites for assigning a BSS to a different RXCDR

To assign a BSS to a different RXCDR (reparent a BSS), the BSS must be removed from its
original parent RXCDR and then added to the new parent RXCDR.
The following prerequisites apply:

Ensure that the links between the BSS and original RXCDR have been disconnected,
with the help of BSS field engineer.

If required, reconfigure the entries for the NE from the packet switch/MUX (see ).

Ensure that the links between the BSS and the new RXCDR have been connected, and
are in service.

Verify that the destination point code and originating point code are set correctly, to ensure
full communication between the BSS and the MSC. Verify by using the BSS Detailed View
Signaling Information grouping.

Verify that calls are going to the MSC.

Reparenting a BSS to a different RXCDR

To reparent a BSS to a different RXCDR, follow these steps at the System Processor:

Procedure 4-36 Reparent a BSS to a different RXCDR

1

Clean up BSS - RXCDR connectivity.

Remove the appropriate RXCDR - Associated BSS objects from the old
RXCDRs which are connected to the BSS.

From the engineering diagram, identify the new RXCDRs connecting to

the BSS.
Create the RXCDR - Associated BSS objects completing the appropriate
link information.

If using the Map feature, proceed to Reparenting a BSS to a different

RXCDR on page 4-104.
If not, the procedure is finished.
Continued

4-104

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reparenting a BSS to a different RXCDR

Procedure 4-36 Reparent a BSS to a different RXCDR (Continued)

To reparent a BSS to a different RXCDR when using the Map feature, follow these steps at
the System Processor:

Procedure 4-37 Reparent a BSS to a different RXCDR when using the Map feature
1

If using the Map feature, first complete all steps in Procedure 4-36.

Log in to the system processor as omcadmin.

Open a shell and change to the temporary work directory:

cd $OMC_TOP/config/local/cm_mib_db/temp_files

Extract the link information between the BSS to be reparented and

its RXCDR:
mib_env
cmutil -x -h -t CommsLink -n BSS:<name> -o current_links
cp current_links current_links_del

Remove the links between the BSS and its current parent RXCDR
using the following command:
cmutil -d -i current_links_del

Use an editor to edit current_links and replace all instances of the

old RXCDR and RXCDR_SITE names with that of the new RXCDR and
RXCDR_SITE.
Change the MMS ids for the associated devices to those used by the
new RXCDR.

Use the following command to check the file syntax:

cmutil -s -i current_links
If the file syntax check reveals errors, self-explanatory error messages
are displayed.

68P02901W17-T

Use the following command to add the links between the BSS and its
new parent RXCDR:
cmutil -a -i current_links

When the BSS has been reparented, it is necessary to extract the

BSS configuration from the MIB database as it now contains link
information for the newly parented RXCDR. This is done using the
procedure described in step 4 .

10

As a result of reparenting, links may have been deleted from the

user-defined maps. Refer to: Adding and deleting a map link on page
13-11 for the procedure on adding links between the BSS and the new
RXCDR for relevant user-defined maps.

11

The default network map is modified. The map nodes are not deleted
and re-added, so the node positioning is correct. Only the map links
have changed. Follow the procedure described in step 4 , to extract
the new information for the network map.

12

Log out from the system processor by typing:

logout

4-105
Jan 2010

Reparenting an RXCDR to a different MSC

Chapter 4: Configuring a BSS/RXCDR

Reparenting an RXCDR to a different MSC

Introduction to reparenting an RXCDR to a different MSC

To move an RXCDR to a different MSC, the RXCDR must be removed from its original parent
MSC and then added to the new MSC.
The following prerequisites apply:

Ensure that the links between the RXCDR and original MSC have been disconnected,
with the help of BSS field engineer.

Ensure that the links between the RXCDR and the new MSC have been connected, and
are in service.

Verify that the destination point code and originating point code are set correctly to ensure
full communication between the BSSs under the RXCDR and the MSC. Verify by using the
BSS Detailed View Signaling Information grouping.

Verify that calls are going to the MSC.

Reparenting RXCDR commslinks

Carry out the following procedure to move an RXCDR:

Procedure 4-38 Reparent an RXCDR commslink

1

At the System Processor, log in as omcadmin.

Open a shell and change to the temporary work directory:

cd $OMC_TOP/config/local/cm_mib_db/temp_files

Extract the link information between the RXCDR and RXCDR SITE
and the MSC:
cmutil -x -h -t CommsLink -n RXCDR:<name> current_links

Remove the links between the RXCDR and its MSC:

cmutil -d -i current_links

Use an editor to edit current_links and replace all instances of the old
MSC_name with the new MSC_name.

Use the following command to check the file syntax of the file
current_links.
cmutil -s -i current_links
If the file syntax check reveals errors, self-explanatory error messages
are displayed.
Continued

4-106

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reparenting RXCDR commslinks

Procedure 4-38 Reparent an RXCDR commslink (Continued)

68P02901W17-T

Use the following command to add the links between the RXCDR and
its new MSC:
cmutil -a -i current_links

When the RXCDR has been moved to a new MSC, it is necessary to

extract the RXCDR configuration from the MIB as it now contains new
link information for the RXCDR.

Log out from the system processor:

logout

4-107
Jan 2010

Checking the software version for a BSS/RXCDR/OMC-R

Chapter 4: Configuring a BSS/RXCDR

Checking the software version for a BSS/RXCDR/OMC-R

Software version number format

NOTE
An f in the fifth character position of the number shown in Version column indicates a
Fix Object load. For example, 06.00.f3.c4 is a Fix Object load, whereas 06.00.03.c4
is a standard load.
However, the Fix Object number does not indicate the point release to which it
applies, and the result returned by the disp_ver command does not show the point
release information.
If this information is needed, contact CNRC or the SDLC group for assistance.

Checking a single NE using the OMC-R GUI

To check the software version of a single NE using the OMC-R GUI, proceed as follows:

Procedure 4-39 Check software version of single NE

4-108

Open a BSS/RXCDR Detailed View from the Navigation Tree.

Check the setting of OMC-R/NE load version field (in the Identification
parameter group) to obtain current software load version number.

Select Options - NE Software from the BSS/RXCDR Detailed View menu

bar, to check all other load versions associated with the selected NE.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking multiple NEs using the OMC-R GUI

Checking multiple NEs using the OMC-R GUI

To check the software version of multiple NEs, follow these steps:

Procedure 4-40 Check software version of multiple NEs

1

Click the Load Management icon on the front panel. This displays
the Software Load Management window. The software load setting
is displayed in the Current Software Load column. If required, use
options File Save As to save this information to a text file.

Select Load Mgt - Software Inventory from the menu bar to display the
Software Inventory window, which lists all the software loads currently
installed at the OMC-R. The software version number for each Software
Load Name is displayed in the Version column.

Checking a single NE and multiple NEs using cmutil

Use cmutil to extract the BSS object data for a specific BSS, or to extract information for more
than one NE. See Chapter 15 cmutil for details.

Checking OMC-R software load version

To check the OMC-R software load version, enter the following UNIX command:
ls -l /usr/omc | grep current | awk '{print $11}'

Checking NE software load versions using disp_version

command
Remotely logging in to an NE and using the disp_version command can be used to display
the software version number. Refer to: Technical Description: BSS Command Reference
(68P02901W23) for full details of this command.

68P02901W17-T
Jan 2010

4-109

Checking NE software load versions using disp_version command

4-110

Chapter 4: Configuring a BSS/RXCDR

68P02901W17-T
Jan 2010

Chapter

5
Configuring Connectivity

The information here shows how to check and create connectivity between a BSS and MSC
(Through RXCDR), and a BSS/RXCDR and OMC-R. The following topics are described:

Checking BSS to MSC (Through RXCDR) connectivity on page 5-2.

Configuring a Conn_Link on page 5-5.

Configuring a CommsLink using the OMC-R GUI on page 5-10.

Checking RXCDR/BSS to OMC-R (OML) connectivity on page 5-15.

DTE X.121 addresses at the OMC-R on page 5-17 - contains details of the x25_config
file, which contains the DTE X.121 addresses necessary for the OMC-R to communicate
with Network Elements.

Assigning DTE X.121 addresses at the NE on page 5-19.

Modifying configurations on A, M, and Mobis interfaces on page 5-22.

68P02901W17-T
Jan 2010

5-1

Checking BSS to MSC (Through RXCDR) connectivity

Chapter 5: Configuring Connectivity

Checking BSS to MSC (Through RXCDR) connectivity

BSS to MSC connectivity

BSC to RXCDR connections are tracked by engineering diagrams. They are not modeled
automatically by the OMC-R MIB. However, Commslinks or Associated_BSSs can be created
between the BSSs and RXCDRs to track the MMS connections. The timeslot usage, and circuit
groupings can only be checked using the TTY commands.

NOTE
Motorola recommends using the Generic Lookup Utility (GLU). GLU is an optional
tool, available from Motorola, capable of extracting configuration information on
connectivity.

Connection report
Description
A Connection report can be displayed for any NE, that is, any BSS or RXCDR. A Connection
report displays the following information:

Table 5-1 Example Connection report for BSS1015

Connection
name

NE

Device

Connected NE

Device

Conn 3:0

BSS1015

MMS 1 0

RXCDR-1

MMS 22 0

Conn 3:1

BSS1015

MMS 1 0

RXCDR-1

MMS 22 1

Conn 3:2

BSS1015

MMS 1 1

RXCDR-1

MMS 22 1

Displaying a Connection report

To display a Connection report from the Navigation Tree, click the BSS or RXCDR for which the
report is required, and select Connection Report from the Options menu.

Checking BSS connections

Links and timeslots to the RXCDR are configured using the add_circuit and del_circuit
commands. The timeslot usage of a link is not modeled at the OMC-R. To see how timeslots are
configured, use the disp_mms_ts_usage command.

5-2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking RXCDR connections

Checking RXCDR connections

Conn_Links
A Conn_Link describes the connections (links) between a BSS (BSC) and RXCDR.
At the RXCDR side, the add_conn and del_conn commands configure the E1 links (Conn_Links)
connected between the RXCDR and each BSS. disp_conn command lists the links connected
between the RXCDR and each BSS. Each BSS has its own BSS_id. Use the BSS rdn instance
(from MIB or NE.MAP file) as the BSS_id entry.
Conn_Links can also be created using the OMC-GUI, see Configuring a Conn_Link on page 5-5.
If the Enhanced BSC Capacity on page 2-94 is enabled, up to 27 Conn_Links can exist per
BSS-RXCDR connection. If the Enhanced BSC Capacity feature is disabled, up to 21 Conn_Links
can exist per BSS-RXCDR connection.

Timeslots
The disp_mms_ts_usage command lists the incoming (from BSS) and outgoing timeslots (to
MSC) through the RXCDR and gives its associated group. disp_links also lists the nailed
connections through the RXCDR for features such as SMS.

Creating and extracting CommsLink details

Creating CommsLinks
CommsLinks can be created between the BSSs and RXCDRs to track the connections. These are
OMC-R only objects and must be manually updated if a configuration changes. See Configuring
a CommsLink using the OMC-R GUI on page 5-10 for details.
The advantage of using CommsLinks is that all path connectivity is automatically tracked by
CommsLinks. By manually configuring the BSS to RXCDR links all link information can be
extracted for a particular BSS from one MIB object.

Extracting CommsLinks
To extract CommsLinks details on a per object basis, or to extract all CommsLinks details,
see Chapter 15 cmutil.

Checking BSS to RXCDR connectivity

The BSS to RXCDR MMS data can be kept in the MIB by manually updating from the Assoc_BSS
object of the RXCDR. This MIB data consists of OMC-R only objects and must be manually
updated if a configuration changes.

68P02901W17-T

5-3
Jan 2010

Checking BSS to RXCDR connectivity

Chapter 5: Configuring Connectivity

To check BSS to RXCDR connectivity, proceed as follows:

Procedure 5-1 Check BSS to RXCDR connectivity

5-4

Create a job order to associate each BSS with RXCDR.

Using the Navigation Tree, create an Assoc_BSS object for each connection (see
Configuring an Assoc_BSS on page 4-68).
Each connection can be identified from disp_bss_conn output.

Extract the information created in step 2 from the MIB by creating the following sql
script, get_rxcdr_bsc_links.sql:
unload to /tmp/tmp_links1.op
delimiter '#'
select
rxcdrtable2.name,
bsstable2.name,
conn_linktable2.rxcdr_mms,
conn_linktable2.bsc_mms
from
bsstable2,
rxcdrtable2,
conn_linktable2,
assoc_bscstable2
where
(assoc_bscstable2.containerinstrite = rxcdrtable2.oidinstrite
and assoc_bscstable2.containerinstleft = rxcdrtable2.oidinstleft
and assoc_bscstable2.containertomid = rxcdrtable2.oidtomid
and assoc_bscstable2.containerclass = rxcdrtable2.oidclass)
and
(conn_linktable2.containerinstrite = assoc_bscstable2.oidinstrite
and conn_linktable2.containerinstleft = assoc_bscstable2.oidinstleft
and conn_linktable2.containertomid = assoc_bscstable2.oidtomid
and
conn_linktable2.containerclass = assoc_bscstable2.oidclass)
and (assoc_bscstable2.bss_idinstrite = bsstable2.oidinstrite
and assoc_bscstable2.bss_idinstleft = bsstable2.oidinstleft
and assoc_bscstable2.bss_idtomid = bsstable2.oidtomid)
order by
rxcdrtable2.name

Create the following script, get_rxcdr_bsc_links, which formats the output of the
sql extract:
#!/bin/csh
rm -f rxcdr_links.asc
echo rxcdr name#bss name#rxcdr mms_id#bss mms_id# >rxcdr_links.asc
mib_env
isql mib_16xx <get_rxcdr_bsc_links.sql
sed 's/31\/1,30\/0,9\///g' /tmp/tmp_links1.op >/tmp/tmp_links2.op
sed 's/10\///g' /tmp/tmp_links2.op >/tmp/tmp_links3.op
sed 's/60\/1,30\/0,9\///g' /tmp/tmp_links3.op >>rxcdr_links.asc
rm -f /tmp/tmp_links1.op /tmp/tmp_links2.op /tmp/tmp_links3.op

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a Conn_Link

Configuring a Conn_Link

Creating a Conn_Link using the OMC-R GUI

Prerequisites
Before a Conn_Link can be created, the corresponding Assoc_RXCDR (AXCDR) or Assoc_BSS
(ABSS) must exist.

Procedure
If no Conn_Link exists for the MMS on the BSC, create a Conn_Link using the OMC-R GUI. Use
the following procedure to create a Conn_Link:

Procedure 5-2 Create Conn_Link using the OMC-R GUI

1

Navigate to and select the Conn_Link class button in the Navigation

Tree (BSS BSS instance Assoc_RXCDR Assoc_RXCDR instance
Conn_Link).
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details.
The network object class button changes color.

Select Edit Create from the Navigation Tree menu bar.

The OMC-R displays the Conn_Link Detailed View in Create mode.

Complete the required fields.

See Conn_Link Detailed View fields for details.

Select File Create from the menu bar to create the Conn_Link.

Select File Close from the menu bar to close the Detailed View.

Conn_Link Detailed View fields

The following sections list and briefly describe the parameter fields in the Conn_Link Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

68P02901W17-T

5-5
Jan 2010

Conn_Link Detailed View fields

Chapter 5: Configuring Connectivity

Identification grouping
Table 5-2 describes the fields in the Identification grouping of the Conn_Link Detailed View.

Table 5-2 Conn_Link Detailed View fields - Identification grouping

Field name

Mandatory or
Optional?

Values

Brief description

RDN Class

See Table 4-1 description.

Default is
Conn_Link.

RDN Instance

See Table 3-1 description.

0 - 26.

NMC RDN Value

See Table 4-1 description.

Parent Detailed View

The id of the Associated

RXCDR. Click to display
the parent Assoc_RXCDR
Detailed View.

Additional Information
Use the Additional Information window to input any notes relating to this Conn_Link. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

Connectivity Information grouping

Table 5-3 describes the fields in the Connectivity Information grouping of the Conn_Link
Detailed View.

Table 5-3 Conn_Link Detailed View fields - Connectivity Information grouping

Field name

5-6

Brief description

Values

Mandatory
or Optional?

RXCDR

Identifier of the container RXCDR.

Mandatory.

BSS

Identifier of the BSS connected to the RXCDR

through this Conn_Link.

Mandatory.

Local MMS

The local MMS id for the XBL connectivity,

that is, the MMS id at the site (BSS or
RXCDR) at which the Conn_Link is being
created.

Mandatory.

Remote MMS

The remote MMS id for the XBL connectivity,

that is, the MMS id of the site between which
the Conn_link is being created.

Mandatory

Connected
Associated RXCDR

Id of the connected Associated RXCDR.

Mandatory.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a Conn_Link using the OMC-R GUI

Deleting a Conn_Link using the OMC-R GUI

Prerequisites
The connectivity for an MMS pair cannot be deleted when the Transcoding field (BSS naming
convention: local_transcoding) located in the Identification section of the BSS Detailed View
form, is set to Remote (0).

Other deletions required to delete a Conn_Link

To delete a Conn_Link from the OMC-R GUI, it is also necessary to delete the following:

The contained XBLs.

All the CICs equipped on the MMS used by the Conn_Link connectivity.

Procedure
To delete a Conn_Link using the OMC-R GUI, see the general procedure in Deleting a network
object using the OMC-R GUI on page 1-37.

Adding a Conn_Link using the TTY interface

Prerequisites
Before arbitrarily numbering the BSCs connected to the RXCDR, the XBL must have been
equipped at the BSC and the RXCDR. This is so that different BSCs can be distinguished from
the RXCDR.

68P02901W17-T

5-7
Jan 2010

Displaying connectivity using the TTY interface

Chapter 5: Configuring Connectivity

Adding connectivity - add_conn command

For correct XBL operation, network connectivity information must be supplied in the database
SYSGEN using the add_conn command. The add_conn command adds MMS connectivity
between the RXCDR and the BSS. Connectivity may be added for a maximum of 21 MMSs at a
BSC or RXCDR regardless of how many RXCDRs or BSSs are connected. If the Enhanced BSC
Capacity feature is enabled, connectivity can be added for up to 27 MMSs.

NOTE
The add_conn command can also be used outside of SYSGEN.
This command allows the operator to specify the E1 connectivity information identifying which
RXCDR is associated with the E1 link and the device identity within the RXCDR to which the E1
link is connected. This connectivity information must be specified for each E1 link connecting
to an RXCDR.
Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the add_conn command.

Displaying connectivity using the TTY interface

To display the contents of the XBL connectivity, at the RXCDR site, use the disp_conn command.

Deleting a Conn_Link using the TTY interface

del_conn command
To delete a particular connection between an MMS at the BSC and an MMS at the RXCDR,
use the DEL_CONN command.
Connectivity may not be removed for an MMS pair if the BSC is operating in static mode and
CICs are statically assigned to that MMS pair. This only applies to remote transcoding BSC
and RXCDR sites.
Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the del_conn command.

Example of deleting a Conn_Link

The following example deletes connectivity information for MMS 4 0 at the BSC:
del_conn 4 0
The following example deletes connectivity information for MMS 3 0 at the RXCDR:
del_conn 3 0

5-8

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a Conn_Link using the TTY interface

Other deletions required to delete a Conn_Link

To delete a Conn_Link, it is also necessary to delete the following:

The contained XBLs.

All the CICs equipped on the MMS used by the Conn_Link connectivity.

68P02901W17-T

5-9
Jan 2010

Configuring a CommsLink using the OMC-R GUI

Chapter 5: Configuring Connectivity

Configuring a CommsLink using the OMC-R GUI

Introduction to configuring a CommsLink

This section describes how to configure a CommsLink using the OMC-R GUI.
To add and delete links to existing sites using cmutil, see Chapter 15 cmutil.

Autocreation and deletion of CommsLinks

If a CommsLink does not exist, when a Conn_Link is created between a BSC and an RXCDR,
the CommsLink is automatically created in the CM MIB to represent the point-to-point links
between BSSs and RXCDRs, and the Conn_Link added to it.

NOTE
The CommsLink is created only after validating the end nodes, the container
BSC/RXCDR and the associated RXCDR/BSC.
Auto-created CommsLinks can only be auto-deleted. Manually created CommsLinks can only
be manually deleted. Manually deleted CommsLinks do not delete corresponding Conn_Links
or paths.

Creating a CommsLink using the OMC-R GUI

Prerequisites for creating a CommsLink
A CommsLink can only be created if the two nodes it connects have been defined in advance.

Procedure
To create a CommsLink using the OMC-R GUI, use the following procedure:

5-10

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating a CommsLink using the OMC-R GUI

Procedure 5-3 Create a CommsLink using the OMC-R GUI

68P02901W17-T

Navigate to and select the CommsLink class button in the Navigation

Tree.
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details.
The network object class button changes color.

Click the folder icon next to the CommsLink class button.

The OMC-R displays the CommsLink List window as shown in
Figure 5-1 for GPRS networks.

Select Edit Create from the Navigation Tree menu bar.

A CommsLink Detailed View window is displayed.

Complete the Name field, preferably choosing a name relating to the

two nodes the link connects, separated by a hyphen (-).

To input a node name, click the Node A button.

A Navigation Tree is displayed.
Navigate through the Navigation Tree in the usual way, and when the
required network element is reached, double-click the left mouse
button. This NE is recorded as node A in the Node A field.

Repeat step 5 for Node B at the other end of the CommsLink.

Select File Create from the menu bar.

Close the Detailed View window by selecting File Close from the
menu bar, and by selecting OK from the subsequent Confirmation
window.

5-11
Jan 2010

CommsLink Detailed View fields

Chapter 5: Configuring Connectivity

Figure 5-1 CommsLink List showing GPRS links

ti-GSM-CommsLinkListshowingGPRSlinks-00787-ai-sw

CommsLink Detailed View fields

The following sections list and briefly describe the parameter fields in the CommsLink Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

5-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Filtering the CommsLink list window

Identification grouping
Table 5-4 describes the fields in the Identification grouping of the CommsLink Detailed View.

Table 5-4 CommsLink Detailed View fields - Identification grouping

Field name

Brief description

Values

Mandatory or
Optional?

Name

The name of the CommsLink.

Mandatory.

Node A

A CommsLink has two end

points, A and B. This is the
object at point A. Click to
display the Detailed View of
Node A.

Mandatory.

Node B

A CommsLink has two end

points, A and B. This is the
object at point B. Click to
display the Detailed View of
Node B.

Mandatory.

Parent Detailed View

Displays the name of the

parent. Click to display the
Detailed View of the parent. A
CommsLink can only have the
network as a parent.

Map Information grouping

Table 5-5 describes the fields in the Identification grouping of the CommsLink Detailed View.

Table 5-5 CommsLink Detailed View fields - Map Information grouping

Field name
Service State

Brief description

Values

The state of a node or link on

a map.

INS, OOS or
Unknown.

Mandatory or
Optional?
Optional.

CommsLink Related Devices grouping

Displays the devices related to this CommsLink. The Name, Operational State, and
Administration state of each device is displayed.

Filtering the CommsLink list window

For anything other than a very small network, the number of links in the CommsLink list
window grows to a large number. This makes it difficult to find a particular link when sites
are being modified and the CommsLink Detailed View is to be edited. The filtering feature
can be used to help.

68P02901W17-T

5-13
Jan 2010

Deleting a CommsLink using the OMC-R GUI

Chapter 5: Configuring Connectivity

To filter for links between two nodes, proceed as follows:

Procedure 5-4 Apply filter for links between two nodes

1

From the Navigation Tree, click the folder icon next to the CommsLink
type button.
The CommsLink list is displayed.

Click the Node A button. The Navigation Tree is displayed.

Double-click one of the nodes that is attached to one end of the link
to be accessed.

Click the Node B button.

The Navigation Tree is redisplayed.

Double-click the node that is attached to the other end of the link to
be accessed.

Click the Apply Filter button.

Only the links that are configured between the two selected nodes are now displayed in the
CommsLink list.

Deleting a CommsLink using the OMC-R GUI

To delete a Commslink using the OMC-R GUI, use the following procedure:

Procedure 5-5 Delete a Commslink using the OMC-R GUI

5-14

Navigate to and select the CommsLink class button in the Navigation

Tree. If necessary, see Navigating to a network object class or instance
on page 1-28 for further details.
The network object class button changes color.

Click the folder icon next to the Commslink class button, to display the
Commslink List window.

Select the Commslink to be deleted.

The selection is highlighted.

Select Edit Delete from the menu bar.

A confirmation window is displayed.

To delete the Commslink, select OK in the confirmation window.

The confirmation window closes and the process is documented on the
status bar at the bottom of the Commslink List window.
When the deletion has been completed, the chosen Commslink node
disappears from the Commslink List, and the message Element Deleted
is displayed in the status bar.

Close the Commslink List window by selecting File Close from the
menu bar.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking RXCDR/BSS to OMC-R (OML) connectivity

Checking RXCDR/BSS to OMC-R (OML) connectivity

Overview to OML connectivity

Checking RXCDR/SS to OMC-R (OML) connectivity can be carried out using one of two methods:

Checking OMLs for a single NE using the OMC-R GUI.

Checking OMLs for multiple NEs using SQL.

To create an OML see Configuring an OML device on page 9-160.

Checking OMLs for a single NE using the OMC-R GUI

To check OMLs for a single NE using the GUI, proceed as follows:

Procedure 5-6 Check OMLs for a single NE using the GUI

1

Open a Navigation Tree to show OMLs (BSS - SITE - <Site:0> - Logical

links - OML).

Check number of configured OMLs. There are usually two OMLs

configured (one active and one standby).

Open the Detailed Views and check the associated MMS id and
timeslot.
The MMSs of the active and standby OMLs are usually equipped in
slots 16 and 14 of the BSC cage. This allows utilization of the dual
OML feature which speeds up software downloads.

Checking OMLs for multiple NEs using SQL

Use SQL to get the information for all OMLs in the MIB. Use the following example SQL query
procedure to extract the state (whether it is active or standby or OOS), and MMS configuration
information for all OMLs in the OMC-R:

68P02901W17-T

5-15
Jan 2010

Checking OMLs for multiple NEs using SQL

Chapter 5: Configuring Connectivity

Procedure 5-7 Check OMLs for multiple NEs using SQL

1

Create the following script:

select
bsstable2.name BSC,
sitetable2.name SITE,
omltable2.rdninstance RDN,
omltable2.opstate opstate,
omltable2.adminsate adminstate,
omltable2.msi_id MSI,
omltable2.mms_id MMS,
omltable2.timeslot TIMESLOT
from
omltable2,
sitetable2,
bsstable2
where
omltable2.containerinstrite = sitetable2.oidinstrite
and omltable2.containerinstleft = sitetable2.oidinstleft
and sitetable2.containerinstrite = bsstable2.oidinstrite
and sitetable2.containerinstleft = bsstable2.oidinstleft
order by
BSC, SITE, RDN

Create a file called oml.sql with this query.

As an omcadmin user, enter:

mib_env
isql mib_16xx <oml.sql> oml.op
Where mib_16xx is the name of the database.
The file called oml.op contains all the data for analysis or further
parsing.

5-16

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DTE X.121 addresses at the OMC-R

DTE X.121 addresses at the OMC-R

Introduction to DTE X.121 addresses

For the OMC-R to communicate with the various network elements, certain addresses must be
set at the OMC-R in the x25_config file. Initial addresses are assigned during staging and need
not be altered. When new network elements are added, the new addresses of the network
elements are added to the x25_config.

x25_config file location

The OMC-R X.121 addresses are stored in the x25_config file, located at /usr/omc/config/global
on the system processor.

x25_config file fields

Each line in this file contains eleven fields, each separated by a space. The fields are:
<record no.>

Record number within the file.

<x25 chan.

X.25 channel number (specified as x25_chan<channel number>).

no.>

<link number>

Sunlink X.25 link number. For the HSI configuration, the link
numbers in the x25_config file must correspond to the Sunlink
X.25 link numbers.

<x121 app.

Local X.121 address for an application (maximum 14 digits).

Digits one to four relate to the country of location. Digits five
to ten/twelve are the dial code. The last two digits relate to the
subnet address of the X.25 process.

addr.>

<internal instance>

Interface identifier. It is H for Sunlink HSI.

<proc.

Process call characteristic field. A value of -' indicates that the

process makes calls. Any other value in this field indicates that the
process listens for incoming calls.

<app.

call char>

process>

Type of X.25 application process which may be any of the following:

OMC_BL Bootload.
OMC_EI Event Interface.
OMC_RL Remote Login.
OMC_PU Upload.

<protocol>

Protocol being used by a process. The only valid value in this field
is X.25.

<packet size>

Packet size.

<window size>

Window size.

<timeout parameter>

Timeout value.

68P02901W17-T

5-17
Jan 2010

x25_config file entries

Chapter 5: Configuring Connectivity

x25_config file entries

Each entry associates an X.121 DTE address with a sync controller port on the system processor.
The contents of a typical file are shown in Figure 5-2.

Sun
For the HSI configuration, the link numbers in the x25_config file must correspond to the
Sunlink X.25 link numbers. A typical x25_config file for the Sun HS/IS is shown in Figure 5-2.

Figure 5-2 Typical x25_config file

1
2
3
4
5
6
7

x25_chan1
x25_chan2
x25_chan3
x25_chan4
x25_chan5
x25_chan6
x25_chan7

Internal Instance
Identifier

X25
X25
X25
X25
X25
X25
X25

Application
Process

128
128
128
128
128
128
128
Packet
Size

Protocol

2
2
2
2
2
2
2

50
50
500
500
500
50
50

Process
Calchar

OMC_BL
OMC_BL
OMC_EI
OMC_EI
OMC_RL
OMC_PU
OMC_PU

Link
Number

g_bootload
g_bootload
g_ei
g_ei
-

Record
Number

x121 Application
address

H
H
H
H
H
H
H

Number

26800623010061
26800623011062
26800623010141
26800623011142
26800623010200
26800623011299
26800623011299

x25 Channel

2
3
0
1
0
2
3

Time out
Parameter

Window
Size

ti-GSM-SC01W17-000052-eps-sw

5-18

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Assigning DTE X.121 addresses at the NE

Assigning DTE X.121 addresses at the NE

Introduction to assigning DTE X.121 addresses

The X.121 address of the NE and the X.121 addresses of the OMC-R must be assigned at the
NE. The purpose of the address is to verify the calling address on the inbound X.25 packet. The
NE rejects any connections where the address does not match.
For further details of DTE X.121 addresses, see DTE X.121 addresses at the OMC-R on page 5-17.

Setting X.121 addresses

To set all X.121 addresses at the NE, arrange for the changes to be entered at the NE using a PC.

Slot: port settings for OMLs

In RAM, only address 0 is used. In ROM, however, the addresses are link dependent. Table 5-6
shows the slot: port settings for the 2 Mbit/s link carrying the OMLs. In ROM mode, the site
uses link number 0 by default, if this is not available then it uses link number 1, if this link does
not work it uses link number 2 and, finally, link number 3.
Table 5-6 should be used in conjunction with the subsequent procedures.

Table 5-6 Slot: port settings for OML link

link_num

RXCDR (slot: port)

BSS (slot: port)

10:0

16:0

10:1

16:1

8:0

14:0

*10:0
(*denotes cage 2)

*16:0
(*denotes cage 2)

Setting OML addresses using the TTY interface

Set the OML(s) DTE addresses (0 to 3) with reference to Table 5-6.

68P02901W17-T

5-19
Jan 2010

OMC-R addresses - general rules

Chapter 5: Configuring Connectivity

Procedure 5-8 Set OML(s) DTE addresses

1

Set the DTE addresses using the command:

chg_dte bsc <link_num> <address_length> <address_byte> ....
<address_byte>
For example, the following command sets link 0, address length of 14,
address 26245911023431:
chg_dte bsc 0 14 2 6 2 4 5 9 1 1 0 2 3 4 3 1

Verify the value set using the disp_dte command.

NOTE
The address in bsc 0 must always be set, even if the primary
OMC-R connection is not used. The bsc 0 address is used by
the BSC or RXCDR in RAM. The slot number refers to the
MSI board which carries the OML in the BSC cabinet and
the port number refers to the MMS.

For full details of BSS commands, refer to Technical Description: BSS

Command Reference (68P02901W23).

OMC-R addresses - general rules

The general rules for the OMC-R addresses can be summarized as follows:

Always 14 digits for the address length.

Address byte(s):
1, 2 and 3 are the country code.
4 and 5 are the network code.
6 and 7 indicate the location and are set at staging.
8 is equipment type (BSS = 1, RXCDR = 2, OMC-R = 3).
9 and 10 are the number of the OMC-R, that is, 01 is the first, 02 the second, and so on.
11 is the sync controller board at the OMC-R and can be 0 or 1.
12 is the port on the sync controller board and can be 0, 1, 2 or 3 representing
ports a, b, c or d.

5-20

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

OMC-R addresses - general rules

13 and 14 identify the address usage, and are allocated as follows:

41 Event/alarm Interface
42 Event/alarm interface
61 Download/Bootload
62 Download/Bootload
99 Upload
00 Rlogin

68P02901W17-T

5-21
Jan 2010

Modifying configurations on A, M, and Mobis interfaces

Chapter 5: Configuring Connectivity

Modifying configurations on A, M, and Mobis interfaces

Introduction to A, M, Mobis interfaces

The A interface signaling link is the link between the MSC and the RXCDR.
The M interface signaling link is the link between the RXCDR and the BSC.
The Mobis interface signaling link is the link between the BSC and the BTS.
The devices available on the A and M interfaces are the Message Transfer Link (MTL) and the
Transcoder-Base Station Link (XBL). The devices/functions available on the Mobis interface are
Radio Signaling Link (RSL) and Receive Transmit Function (RTF).

Methods for modifying configurations on A, M, and Mobis

interfaces
Generally, modifying configurations on the A, M and Mobis interfaces must be performed using
the TTY interface, although the Equip Function RTF option is available from the Configuration
menu of the BSS MML Command Constructor window.

Prerequisites to modifying A, M, and Mobis interfaces

NOTE
The following have to be noted when modifying interfaces:

Before any modification of an interface, display the current status of that

interface using either the display features of the BSS MML Command
Constructor window, or the TTY interface commands such as disp_traffic
or disp_mms_ts_usage

Implement the required configuration changes from the TTY interface using
the equip, add_conn and chg_ts_usage commands, although there is some
functionality available from the OMC-R GUI.

Refer to: OMC-R Online Help, Network Operations for information on displaying the status
using the BSS MML Command Constructor window.
Full details of the syntax for these TTY commands can be found in: Technical Description:
BSS Command Reference (68P02901W23).

5-22

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying interface status

Displaying interface status

The interface status can be displayed using the BSS MML Command Constructor window,
or the TTY interface, using MMI commands.
Commands available to display the status of the interfaces are:

disp_traffic to display all traffic equipped to a particular path device, that is, all RSL
devices and RTF devices (Mobis interface).

disp_mms_ts_usage to display the utilization of all timeslots for a specified 2 Mbit/s link.
This gives the status of each timeslot in the form unallocated/allocated to RSL, allocated to
RTF and reserved, and Dynet timeslot or shared timeslot.

Equipping and unequipping A and M interfaces using the TTY

interface
To alter the configuration of the devices/functions on the A and M interfaces, use the following
commands:
unequip <location> MTL
equip <location> MTL
For the M interface only, use:
unequip <location> XBL
equip <location> XBL

Modifying the Mobis interface using the TTY interface

Equipping/unequipping devices/functions
To alter the configuration of the devices/functions on the Mobis interface, use the following
commands:
unequip <location> RSL
equip <location> RSL
or
unequip <location> RTF
equip <location> RTF

68P02901W17-T

5-23
Jan 2010

Modifying the Mobis interface using the TTY interface

Chapter 5: Configuring Connectivity

Reserving a timeslot
Timeslots on specified E1 links can be barred from use by a BSS, that is reserved for other
uses. To reserve timeslots the chg_ts_usage reserve command is used (refer to: Technical
Description: BSS Command Reference (68P02901W23) for full details of the syntax). To
illustrate the steps required to use the command refer to the following example:
For example, to reserve the range of timeslots between 6 and 9 at BTS 12 for MMS 1 0, follow
these steps:

Procedure 5-9 Reserve a timeslot

1

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Enter the following command:chg_ts_usage reserve 12 1 0 6 9

Freeing a timeslot - at the same site

To free timeslots that have been reserved or nailed at the same site, use the chg_ts_usage free
command (refer to: Technical Description: BSS Command Reference (68P02901W23) for full
details). For example, to free the range of timeslots between 6 and 9 at BTS 12 for MMS 1
0, follow these steps:

Procedure 5-10 Free a timeslot at the same site

1

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Enter the following command:chg_ts_usage free 12 1 0 6 9

Freeing a timeslot - between different sites

To free timeslots of a nailed connection between different sites the chg_ts_usage free_path
command is used (refer to: Technical Description: BSS Command Reference (68P02901W23)
for full details of the syntax).
For example, to free the path (with path identity of 3) nailed to timeslot 5 of MMS 1 0 at SITE 0
to timeslot 7 of MMS 0 1 at SITE 3.

Procedure 5-11 Free a timeslot between different sites

5-24

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Enter the following command:

chg_ts_usage free_path 3 0 0 1 0 5 3 0 1 7 1

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Modifying the Mobis interface using the TTY interface

Adding a nailed connection

Nailed connections can be added to enable third party non-GSM calls to be connected through
GSM nodes. A nailed connection can be established between two timeslots at the same site or
different sites.
To nail connections between two timeslots at the same site the chg_ts_usage nail command is
used.
To nail connections between two timeslots at different sites the chg_ts_usage nail_path
command is used.

NOTE
Full syntax details of the chg_ts_usage command are in the Technical Description:
BSS Command Reference (68P02901W23) manual.
To illustrate the steps required to use the command, refer to the following examples.
Example 1: To nail timeslots 5 to 8 of MMS 1 0 to timeslots 7 to 10 of MMS 0 1 at the same site.

Procedure 5-12 Nail a timeslot

1

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Enter the following command:

chg_ts_usage nail 0 1 0 5 0 1 7 4

Example 2: To nail a path (with path identity of 3) from timeslot 5 of MMS 1 0 at SITE 0 to
timeslot 7 of MMS 0 1 at SITE 3.

Procedure 5-13 Nail a path

68P02901W17-T
Jan 2010

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Enter the following command: chg_ts_usage nail_path 3 0 0 1

0 5 3 0 1 7 1

5-25

Modifying the Mobis interface using the TTY interface

5-26

Chapter 5: Configuring Connectivity

68P02901W17-T
Jan 2010

Chapter

6
Configuring a PCU for GPRS

The procedures here show how to configure a PCU (for GPRS) and its devices. The following
topics are described:

Introduction to the PCU and its devices on page 6-2.

Overview of configuring a PCU and its devices on page 6-6.

Configuring a PCU using the OMC-R GUI on page 6-8.

Displaying and modifying PCU cabinet details on page 6-16.

Displaying and modifying PCU cage details on page 6-17.

Configuring a DPROC using the OMC-R GUI on page 6-18.

Displaying and modifying PSP details on page 6-22.

Configuring a PCU MSI using the OMC-R GUI on page 6-24.

Displaying and modifying PCU MMS details on page 6-27.

Configuring a GDS using the OMC-R GUI on page 6-29.

Configuring a GSL using the OMC-R GUI on page 6-34.

Configuring a GBL using the OMC-R GUI on page 6-38.

Configuring a GSL using the OMC-R GUI on page 6-34.

Configuring an SGSN (GPRS) using the OMC-R GUI on page 6-49.

Configuring the PCU and its devices from the TTY interface on page 6-52.

68P02901W17-T
Jan 2010

6-1

Introduction to the PCU and its devices

Chapter 6: Configuring a PCU for GPRS

Introduction to the PCU and its devices

Overview of GPRS
GPRS is a service which allows for the packet-mode transmission of data within a GSM network.
Using GPRS, an MS can send and receive data in an end-to-end packet transfer mode. GPRS
enables a more cost effective and efficient use of network resources for data transfer.

Introduction to PCU
GSM Packet Radio Service (GPRS) functionality needs a Packet Control Unit (PCU) to manage
the packet radio interface and link the Serving GPRS Support Node (SGSN) into each GSM BSC.
The SGSN is connected to the PCU by the Gb link (GBL).
PCUs are located at the BSS, and up to three PCU can be equipped, with identifiers in the
range 0 - 2.
PCUs and SGSN are visible in the OMC-R GUI once they have been configured.

List of PCU contained devices

A PCU has the following contained devices:

Hardware devices:
Cabinet.
Cage.
Processors:

DPROC (types: PICP and PRP).

PSP.

MSI:

MMS.

Logical Links:
GDS (types: TRAU and LAPD)
GSL
GBL
NSVC

6-2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PCU equipage hierarchy chart

PCU equipage hierarchy chart

Figure 6-1 shows the device and equipment hierarchy for a PCU. It shows that a Cabinet and a
Cage are created (also referred to as equipped) automatically when a PCU is created using the
TTY or OMC-R GUI interface. An MMS is automatically created when an MSI is created using
the TTY or GUI interface.

68P02901W17-T

6-3
Jan 2010

PCU equipage hierarchy chart

Chapter 6: Configuring a PCU for GPRS

Figure 6-1 Device and equipment hierarchy for a PCU

BSC

PCU

PCU

PCU

CAB1

CAGE1

PSP1

DPROC (PICP)

MSI

MMS2

DPROC (PRP)

MSI

MMS2

GDS (TRAU)

GBL

GDS (TRAU)

GDS (LAPD)

GSL

LEGEND 1 indicates automatically equipped device, when a PCU is equipped.

2 Indicates automatically equipped device, when an MSI is equipped.
ti-GSM-DeviceandequipmenthierarchyforaPCU-00789-ai-sw

6-4

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PCU contained devices in the Navigation Tree

PCU contained devices in the Navigation Tree

Figure 6-2 shows an example of PCU containment as shown in the Navigation Tree.

Figure 6-2 Example of PCU containment in the Navigation Tree

ti-GSM-ExampleofPCUcontainmentintheNavigationTree-00790-ai-sw

PCU contained devices to be equipped

When a PCU device is equipped, the contained devices shown in Table 6-1 must also be
equipped/created.

Table 6-1

68P02901W17-T

PCU contained devices

Contained device

Device acronym

Data Processor

DPROC.

PCU System Processor

PSP.

GPRS Data Stream

GDS.

GPRS Signaling Link

GSL.

Multiple Serial Interface board

MSI.

Gb Link

GBL.

Network Service Virtual Connection

NSVC.

6-5
Jan 2010

Overview of configuring a PCU and its devices

Chapter 6: Configuring a PCU for GPRS

Overview of configuring a PCU and its devices

Recommended method for configuring a PCU

The recommended method for configuring a PCU is to:
1.

Install the PCU equipment.

2.

Create a batch_rlogin script file containing equip commands for each of the required PCU
devices and functions. See Configuring the PCU and its devices from the TTY interface on
page 6-52 for guidance.

3.

Load the batch_rlogin script file into the BSS database.

4.

Run an audit at the OMC-R. The PCU and its devices then appear in the OMC-R GUI
Navigation Tree.

Creating a batch_rlogin script file is also recommended for creating a BTS.

Other PCU configuration methods

A PCU and its contained devices can be configured using any of the following methods:

OMC-R GUI, specifically the Navigation Tree, see Configuring a PCU using the OMC-R
GUI on page 6-8.

From the OMC-R, log in to a BSC remotely (rlogin) and then use the TTY interface, see
Configuring the PCU and its devices from the TTY interface on page 6-52.

Using the MMI interface and TTY interface locally at the BSC, see Configuring the PCU
and its devices from the TTY interface on page 6-52.

Locking, unlocking, and other event and fault management activities are described in: OMC-R
Online Help, Network Operations.

6-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Recommended list of PCU configuration procedures

Recommended list of PCU configuration procedures

When creating a PCU and its contained devices, perform the procedures in the following order:
1.

Create a PCU using the Navigation Tree (seeConfiguring a PCU using the OMC-R GUI on
page 6-8) or the equip command (see Configuring the PCU and its devices from the TTY
interface on page 6-52).

2.

Create an SGSN using the Navigation Tree (see Configuring an SGSN (GPRS) using the
OMC-R GUI on page 6-49).

3.

If necessary, modify any PCU Cabinet details, see Displaying and modifying PCU cabinet
details on page 6-16.

4.

If necessary, modify any PCU Cage details, see Displaying and modifying PCU cage details
on page 6-17.

5.

Create a DPROC, see Configuring a DPROC using the OMC-R GUI on page 6-18 or
Configuring the PCU and its devices from the TTY interface on page 6-52.

6.

Modify a PSP, see Displaying and modifying PSP details on page 6-22 or Configuring the
PCU and its devices from the TTY interface on page 6-52.

7.

Create an MSI, see Configuring a PCU MSI using the OMC-R GUI on page 6-24 or
Configuring the PCU and its devices from the TTY interface on page 6-52.

8.

Create an MMS, see Displaying and modifying PCU MMS details on page 6-27 or
Configuring the PCU and its devices from the TTY interface on page 6-52.

9.

Create a GDS, see Configuring a GDS using the OMC-R GUI on page 6-29 or Configuring
the PCU and its devices from the TTY interface on page 6-52.

10. Create a GSL, see Configuring a GSL using the OMC-R GUI on page 6-34 or Configuring
the PCU and its devices from the TTY interface on page 6-52.
11. Create a GBL, see Configuring a GBL using the OMC-R GUI on page 6-38 or Configuring
the PCU and its devices from the TTY interface on page 6-52.
12. Create an NSVC, see Configuring an NSVC using the OMC-R GUI on page 6-43 or
Configuring the PCU and its devices from the TTY interface on page 6-52.

68P02901W17-T

6-7
Jan 2010

Configuring a PCU using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Configuring a PCU using the OMC-R GUI

Introduction to configuring a PCU using the OMC-R GUI

A PCU can be added to the network using the OMC-R GUI Navigation Tree.
Up to three PCUs can exist at a BSS.
A PCU can be locked, unlocked, INS, and reset from the OMC-R GUI. See OMC-R Online Help,

Network Operations for further details.

When a PCU is created, the OMC-R automatically creates a:

Cage, see Displaying and modifying PCU cage details on page 6-17.

Cabinet, see Displaying and modifying PCU cabinet details on page 6-16.

PSP 0 and PSP 1, see Displaying and modifying PSP details on page 6-22.

SYSGEN mode cannot be exited if a PCU has been created but a PSP has not been created for it.

Prerequisites for configuring a PCU using the OMC-R GUI

Before configuring a PCU, ensure that the:

GPRS Feature field (BSS parameter name: gprsOpt) in the associated BSS Detailed View
form is set to Enabled (1). If this is not enabled, the PCU is not displayed in the Navigation
Tree.

Land Layer 1 Mode field (BSS parameter name: ManagedNENode::landLayer1Mode) in

the associated BSS Detailed View form is set to CEPT (E1) (0), which is the default. This
parameter can only be changed in SYSGEN mode.

Creating a PCU using the OMC-R GUI

To add a PCU to the network using the OMC-R GUI, follow these steps:

Procedure 6-1 Add a PCU to the network using the OMC-R GUI
1

Navigate to and select the PCU class button in the Navigation Tree
(BSS BSS instance PCU). If necessary, see Navigating to a
network object class or instance on page 1-28 for further details. The
PCU class button changes color.

Select Edit Create from the menu bar. The OMC-R displays the PCU
Detailed View in Create mode.
Continued

6-8

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PCU Detailed View fields

Procedure 6-1 Add a PCU to the network using the OMC-R GUI (Continued)
3

Complete the fields, as required. See PCU Detailed View fields for
details.

Select File Create from the menu bar.

Close the PCU Detailed View window by selecting File Close from
the menu bar.

PCU Detailed View fields

The following sections list and briefly describe the parameter fields in the PCU Detailed View
according to their parameter grouping.

NOTE

To obtain further detailed information for a parameter, select Help - On Context

from the menu and drag the ? prompt to the appropriate field and click that
field. A context-sensitive help page is displayed.

The PCU Detailed View shows all cells that are currently mapped to the PCU.

Identification grouping
Table 6-2 describes the fields in the Identification grouping of the PCU Detailed View.

Table 6-2 PCU Detailed View fields - Identification grouping

Field name

Brief description

Name

The unique PCU name.

This name must be unique
to the OMC-R. If a PCU is
created during an audit,
the OMC-R auto-generates
a name for the PCU.

RDN Class

See description in
Table 4-1.

Default is PCU.

RDN Instance

See description in
Table 3-1.

0.

NMC RDN Value

See description in
Table 4-1.

Parent Detailed
View

Click to display the parent

BSS Detailed View.

68P02901W17-T

Values
Up to 31 characters.
Format of an
auto-generated
PCU name is:
<BSSname>:PCU-0.

Mandatory or
Optional?
Mandatory.

6-9
Jan 2010

PCU Detailed View fields

Chapter 6: Configuring a PCU for GPRS

Additional Information
Use the Additional Information window to input any notes relating to this PCU. Where additional
notes are not required, close this field by clicking the toggle button next to the Additional
Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Alarm Information grouping

Table 6-3 describes the fields in the Alarm Information grouping of the PCU Detailed View. The
alarm information is used for all MSIs within this container.

Table 6-3 PCU Detailed View fields - Alarm Information grouping

Field name

6-10

Mandatory or
Optional?

Brief description

Values

MSI Remote Loss

Daily Alarm Level

The number of alarms in this

level.

0 - 65535.
Default is 16.

Mandatory.

MSI Remote Loss

Hourly Alarm Level

The number of alarms in this

level.

0 - 65535.
Default is 20.

Mandatory.

MSI Remote Loss

OOS Alarm Level

The number of alarms in this

level.

0 - 65535.
Default is 511.

Mandatory.

MSI Remote Time

OOS Alarm Level

The number of alarms in this

level.

0 - 65535.
Default is 25.

Mandatory.

MSI Remote Time

Restoral Time

Each step is 100 ms.

0 - 65535.
Default is 600.

Mandatory.

MSI Sync Loss Daily

Alarm Level

The number of alarms in this

level.

0 - 65535.
Default is 16.

Mandatory.

MSI Sync Loss Hourly

Alarm Level

The number of alarms in this

level.

0 - 65535.
Default is 20.

Mandatory.

MSI Sync Loss OOS

Alarm Level

The number of alarms in this

level.

0 - 65535.
Default is 511.

Mandatory.

MSI Sync Loss Time

OOS Alarm Level

The number of alarms in this

level.

0 - 65535.
Default is 25.

Mandatory.

MSI Sync Loss

Restoral Time (time)

Each step is 100 ms.

0 - 65535.
Default is 600.

Mandatory.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PCU Detailed View fields

BSSGP Information grouping

Table 6-4 describes the fields in the BSSGP Information grouping of the PCU Detailed View.

Table 6-4 PCU Detailed View fields - BSSGP Information grouping

Field name

Mandatory or
Optional?

Brief description

Values

T1 (Un)Blocking
Guard Timer

The guard timer used for

cell blocking and unblocking
procedures with the SGSN.

1 - 120 Seconds.
Default is 3.

Mandatory.

T2 Reset Guard Timer

The guard timer used during

Reset procedures with the
SGSN (BSSGP T2).

1 - 120 Seconds.
Default is 60.

Mandatory.

Cell Block Retry

Messages

Number of retries for a cell

block message to the SGSN.

1 - 3.
Default is 3.

Mandatory.

Cell Unblock Retry

Messages

Number of retries for a cell

unblock message to the
SGSN.

1 - 3.
Default is 3.

Mandatory.

Cell Reset Retry

Messages

Number of retries for a cell

reset message to the SGSN.

1 - 3.
Default is 3.

Mandatory.

Flow Control Period

Configures flow control

frequency from the PCU to
the SGSN.

1 - 1000 tenths
of seconds.
Default is 10.

Mandatory.

RA Capability Update
Retries

Number of retries the

BSS generates for
RA-Capability-Update
messages to the SGSN.

1 - 3.
Default is 3.

Mandatory.

Gb Mapping Information and Air Interface grouping

Table 6-5 describes the fields in the Gb Mapping Information grouping of the PCU Detailed View.

Table 6-5 PCU Detailed View fields - Gb Mapping Information grouping

Field name/
parameter name
Signaling BVCI

Brief description

Values

Mandatory or
Optional?

The signaling BSSGP

Virtual Connection
Identifier (BVCI) for the
BSS. Cannot be modified
if gprs_enabled is
Enabled (1) for any cells
in the BSS.

0 - 65535.

Mandatory.

Continued

68P02901W17-T

6-11
Jan 2010

PCU Detailed View fields

Chapter 6: Configuring a PCU for GPRS

Table 6-5 PCU Detailed View fields - Gb Mapping Information grouping (Continued)
Field name/
parameter name

Brief description

Network Operation Mode

Whether a GS is present
(OMC-R parameter name:
between the MSC and
gprs_net_op_mode
the SGSN.
BSS parameter name:
gprs_network_operation_mode)

Values
1 or 3.1 - the
network sends
a CS paging
message for a
GPRS attached
mobile on the
GPRS paging
channel, which is
the PCH or the
PPCH depending
on whether there
is a PCCCH in
the cell, or on a
GPRS PDTCH.3
- if allocate, the
network sends
CS pages for a
GPRS attached
mobile on the
CCCH and PS
pages on the
PCCC., Default is
3. Cannot be set
to a value of 2.

Mandatory or
Optional?
Mandatory.

Gb Statistics Configuration grouping

Table 6-6 describes the fields in the Gb Statistics Configuration grouping of the PCU Detailed
View.

Table 6-6 PCU Detailed View fields - Gb Statistics Configuration grouping

Field name/
parameter name

Mandatory or
Optional?

Brief description

Values

GBL Throughput
Period

The time period used to

compute GBL_UL_DATA_
THRPUT and GBL_DL_DATA_
THRPUT statistics.

1 - 255 (10ths
of a second).
Default is 50.

Mandatory.

GBL Uplink
Throughput Samples

Number of samples used to

compute the GBL_UL_DATA_
THRPUT statistics.

1 - 10.
Default is 10.

Mandatory.

GBL Downlink
Throughput Samples

Number of samples used to

compute the GBL_DL_DATA_
THRPUT statistics.

1 - 10.
Default is 10.

Mandatory.

Continued

6-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 6-6

PCU Detailed View fields

PCU Detailed View fields - Gb Statistics Configuration grouping (Continued)

Field name/
parameter name
PCU MMS
Configuration Type

Values

Brief description
The type of connection
wanted for the TELCO
connection.

0 or 1.
For CEPT(E1):
Timeslot 0
multiframe (CRC is
on) (0), No timeslot
0 multiframe (CRC
is off).

Mandatory or
Optional?
Mandatory.

NS Information grouping
Table 6-7 describes the fields in the NS Information grouping of the PCU Detailed View.

Table 6-7 PCU Detailed View fields - NS Information grouping

Field name

Values

Brief description

Mandatory or
Optional?

NSVC (Un)Block
Guard Timer

Guards the NS-VC blocking

and unblocking.

1 - 30 (Seconds).
Default is 3.

Mandatory.

NSVC Reset Guard

Timer

Guards the NS-VC reset

procedure.

1 - 120 (Seconds).
Default is 40.

Mandatory.

NSVC Test Period

The period of NS-VC test

procedure.

1 - 60 (Seconds).
Default is 30.

Mandatory.

NSVC Test Guard

Timer

Guards the NS-VC test

procedure.

1 - 30 (Seconds).
Default is 3.

Mandatory.

NSVC Block Retry

Messages

The number of retries when

attempting to block an
NS-VC.

1 - 3.
Default is 3.

Mandatory.

NSVC Unblock Retry

Messages

The number of retries when

attempting to unblock an
NS-VC.

1 - 3.
Default is 3.

Mandatory.

NSVC Alive Retry

Messages

The number of retries

generated when establishing
whether an NS-VC is alive.

1 - 10.
Default is 3.

Mandatory.

NSVC Reset Period

The period during which the

PCU attempts to reset an
NS-VC.

1 - 250 (Seconds).
Default is 125.

Mandatory.

Network Service
Entity Identifier
nsei

The NSEI used by the PCU

over the Gb Interface.

0 to 65535.

Mandatory.

Map Information grouping

Standard map information fields, see Table 4-15 for details.

68P02901W17-T

6-13
Jan 2010

Modifying PCU details from the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Address Information grouping

Table 6-8 describes the fields in the Address Information grouping of the PCU Detailed View.

Table 6-8 PCU Detailed View fields - Address Information grouping

Field name/
parameter name

Mandatory or
Optional?

Brief description

Values

IP Address
ip_address

The Internet Protocol (IP)

address of the PCU. Used
by the WebMMI facility, see
Remotely logging in to a BSS
using WebMMI on page 1-45.

0.0.0.0 to
223.255.255.255.
Default: 127.0.0.1.

Optional.

Subnet Mask
subnet_mask

The subnet mask to use with

Internet Protocol (IP). Used
by the WebMMI facility, see
Remotely logging in to a BSS
using WebMMI on page 1-45.

0.0.0.0 to
255.255.255.255.
Default:
255.255.255.255.

Optional.

Router IP Address
router_ip_address

The IP address of the default

router when sending IP data.
Used by the WebMMI facility,
see Remotely logging in to a
BSS using WebMMI on page
1-45.

0.0.0.0 to
223.255.255.255.
Default: 127.0.0.1.

Optional.

General grouping
Table 6-9 describes the fields in the general grouping of the PCU Detailed View.

Table 6-9 PCU Detailed View fields - General grouping

Field name/
parameter name
{34452} Congest PD
Expand Enabled
congest_pd_expand
_enabled

Brief description
Specifies whether
the functionality of
use idle TCH for
burst packet traffic is
enabled or not.

Values
Range is 0 to
1.
0 disabled.
1 enabled.
Default is 0.

Mandatory or
Optional?
Optional.

Quality of Service (QoS) grouping

See Quality of Service (QoS) on page 2-154 for further details of the PCU parameters in this
grouping.

Modifying PCU details from the OMC-R GUI

To modify PCU details from the Navigation Tree, see the general procedure described in
Modifying a network object using the OMC-R GUI on page 1-34.

6-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a PCU using the OMC-R GUI

Fields causing PCU cycling

If a user changes the Medium Access Control Mode field (BSS parameter name:
gprs_mac_mode), the OMC-R displays the following message:
WARNING: Changing the value of gprs_mac_mode may cause TBFs to be dropped,
Are you sure you want to change ? (Y/N)
When saving the changes in the Detailed View form, the OMC-R displays the following message
if parameters have been changed which cause the PCU to be cycled:
WARNING: You have modified attribute(s) that cause the PCU to be cycled when
you select OK. Do you wish to modify? If you do not wish to proceed, select
Cancel, which shall undo all your changes.

Deleting a PCU using the OMC-R GUI

Deleting a PCU also deletes all PCU contained devices. To delete a PCU from the Navigation
Tree, see the general procedure in Deleting a network object using the OMC-R GUI on page 1-37.

Prerequisites to deleting a PCU

Before deleting a PCU, ensure that:

GPRS Enabled field (BSS parameter name: gprs_enabled) in all the associated CELL
Detailed View forms is set to False (0). Use the cell propagation facility options in the CELL
Detailed View menu bar to propagate changes to other cells.

Land Layer 1 Mode field (BSS parameter name: ManagedNENode::landLayer1Mode) in

the associated BSS Detailed View form is set to (CEPT (E1) (0)), which is the default. This
parameter can only be changed in SYSGEN mode.

All GDSs and GSLs have been deleted.

68P02901W17-T

6-15
Jan 2010

Displaying and modifying PCU cabinet details

Chapter 6: Configuring a PCU for GPRS

Displaying and modifying PCU cabinet details

Introduction to displaying and modifying PCU cabinet details

When a PCU is created, the OMC-R automatically creates a PCU cabinet. Likewise when a PCU
is deleted, the OMC-R automatically deletes the PCU cabinet.
A cabinet is a child of a PCU (and can also be a child of a site).
A PCU cabinet cannot be created from the OMC-R Navigation Tree. However, details of the PCU
cabinet can be displayed and modified using Cabinet Detailed View form (see Configuring a
cabinet on page 4-54 for details).
When the cabinet type (cabinet_type) of a cabinet is PCU, the Cabinet Detailed View form
displays only the following information:

cabinet type.

rdnClass.

RdnInstance.

nmcRDNInstance.

Parent.

additionalInfo.

opState.

adminState.

reasonCode

timeOfLastTrans

OMC-RUser

Displaying and modifying a PCU cabinet Detailed View

To display and modify details for a PCU cabinet using the Navigation Tree, see the general
procedure in Modifying a network object using the OMC-R GUI on page 1-34. The Cabinet
Detailed View fields are described in Configuring a cabinet on page 4-54.
Some PCU cabinet fields cannot be modified and are set by the OMC-R, for example:

Type: PCU
RdnInstance

6-16

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying and modifying PCU cage details

Displaying and modifying PCU cage details

Introduction to displaying and modifying PCU cage details

When a PCU is created, the OMC-R automatically creates a PCU cage. Likewise when a PCU
is deleted, the OMC-R automatically deletes the PCU cage.
A cage is a child of a PCU (and can also be a child of a site). A PCU can only have one cage.
No child objects for a PCU cage are displayed in the Navigation Tree (for example, DHP class).
A PCU cage cannot be created by a user from the OMC-R Navigation Tree. However, the user
can display and modify details of the PCU Cage using Cage Detailed View (see Configuring a
cage on page 4-59 for details).
When displayed for a PCU Cage, the Cage Detailed View form displays only the following
information:

rdnClass.

RdnInstance.

nmcRDNInstance.

Parent.

cabinet.

additionalInfo.

opState.

adminState.

reasonCode.

timeOfLastTrans.

OMC-RUser.

Displaying and modifying a PCU cage Detailed View

To display and modify details for a PCU cage using the Navigation Tree, see the general
procedure in Modifying a network object using the OMC-R GUI on page 1-34. The Cage Detailed
View fields are described in Configuring a cage on page 4-59.

68P02901W17-T

6-17
Jan 2010

Configuring a DPROC using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Configuring a DPROC using the OMC-R GUI

Introduction to DPROCs
A DPROC is a child of a PCU.
There are two types of DPROC:

Packet Interface Control Processor (PICP).

A maximum of six DPROCs with the type PICP can be created.

Packet Resource Processor (PRP).

A maximum of ten DPROCs with the type PRP can be created.

The total number of PICP DPROCs and PRP DPROCs cannot exceed 12.
When U-DPROC2 replaces DPROC boards, the GPRS capacity is increased by combining PRP
and PICP into PXP functionality. Refer to the section PCU hardware to increase GPRS capacity
on page 2-190 for further details.
The links to a PCU are normally controlled by PICPs. If, in special circumstances, a direct link is
made to a PRP, the relatedDev parameters of the GDS contain the information needed by the
PICP for link control. See Technical Description: BSS Command Reference (68P02901W23)
for the GDS parameters.
A DPROC PICP must be created in either slot 1 or slot 2 of the PCU Cage.

Prerequisites to creating a DPROC

Before creating a DPROC, a PCU must exist.

Creating a DPROC using the OMC-R GUI

To add a DPROC to the network using the OMC-R GUI, use the following procedure:

Procedure 6-2 Add a DPROC to the network using the OMC-R GUI
1

Navigate to and select the DPROC class button in the Navigation Tree
(BSS BSS instance PCU PCU instance Hardware Devices
Processors DPROC). If necessary, see Navigating to a network object
class or instance on page 1-28 for further details. The DPROC class
button changes color.
Continued

6-18

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DPROC Detailed View fields

Procedure 6-2 Add a DPROC to the network using the OMC-R GUI (Continued)
2

Select Edit Create from the menu bar.

The OMC-R displays the DPROC Detailed View in Create mode.

Complete the fields, as required.

See DPROC Detailed View fields for details.

Select File Create from the menu bar.

Select File Close from the menu bar.

DPROC Detailed View fields

The following sections list and briefly describe the parameter fields in the DPROC Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 6-10 describes the fields in the Identification grouping of the DPROC Detailed View.

Table 6-10

DPROC Detailed View fields - Identification grouping

Field name

Brief description

DPROC Type

The functionality to be
performed by the DPROC.

RDN Class

See the description in

Table 4-1.

RDN Instance

See the description in

Table 3-1. When creating the
first device or function for
the PCU, the default value
is unique and need not be
changed.

NMC RDN Value

See the description in

Table 4-1.

Values
PRP (1) or
PICP (2) or PXP (3).
Default is 1.

Mandatory or
Optional?
Mandatory.

Default is DPROC.
1 - 6 or 11 - 16.
Default is 0.

Continued

68P02901W17-T

6-19
Jan 2010

Modifying DPROC details from the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Table 6-10 DPROC Detailed View fields - Identification grouping (Continued)

Field name

Brief description

Values

Mandatory or
Optional?

Parent Detailed View

Displays the name of the

parent site (PCU). Click
to display the parent PCU
Detailed View.

PCI Vendor ID

Identifier unique to the PCI

Device Vendor.

Optional.

PCI Device ID

Identifier unique to the PCI

Device.

Optional.

PCI Device Revision

The revision number of the

PCI device.

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this device. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Modifying DPROC details from the OMC-R GUI

To display and modify details for DPROC details using the Navigation Tree, see the general
procedure in Modifying a network object using the OMC-R GUI on page 1-34.
The following fields cannot be modified:

6-20

DPROC Type.

RDN class.

RdnInstance.

PCI Vendor ID.

PCI Device ID.

PCI Device Revision.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a DPROC using the OMC-R GUI

Deleting a DPROC using the OMC-R GUI

Deleting a DPROC
When a DPROC is deleted, the delete instruction is sent to the BSS, where the DPROC
information is deleted from the BSS database. The BSS then sends the delete instruction
information to the OMC-R database, where the DPROC information is deleted from the OMC-R
database.

Prerequisites to deleting a DPROC

Only delete a DPROC when:

The DPROC is locked.

The associated child MSIs have been deleted.

For a PRP DPROC only, a user can only delete it when the remaining total PRP timeslots
resources available at the PCU is sufficient to support the GPRS timeslot resources for cells
where the field: GPRS Enabled (BSS parameter name: gprs_enabled) is True.

Procedure to delete a DPROC

To delete a DPROC using the Navigation Tree, see the general procedure in Deleting a network
object using the OMC-R GUI on page 1-37.

68P02901W17-T

6-21
Jan 2010

Displaying and modifying PSP details

Chapter 6: Configuring a PCU for GPRS

Displaying and modifying PSP details

Introduction to PSP
A PCU System Processor (PSP) is a child of a PCU. Up to two PSP can exist per PCU.
A PSP is used as the master processor at the PCU, and is necessary for GPRS functionality.
Because the PSP is the main system processor and without it the PCU cannot function, a PSP
cannot be deleted.
When a PCU is created, PSP 0 and PSP 1 are automatically created (auto-equipped). When a
PCU is deleted, the PSPs are also deleted automatically. A user cannot create or delete a PSP.
All commands used by PSP 0 are also supported for PSP 1.
A PSP must be in slot 7 or slot 9 of the PCU cage. PSP 0 is auto-equipped as the PSP device in
slot 7. PSP 1 is auto-equipped in slot 9. A user cannot change these values.
Device management of the MPROC boards is available through the PCU PSP device. A PSP
cannot be locked.

Displaying and modifying PSP details from the OMC-R GUI

To display and modify PSP details from the Navigation Tree, follow these steps:

Procedure 6-3

Display and modify PSP details from the Navigation Tree

Navigate to and select the PSP instance button in the Navigation

Tree (BSS - BSS instance - PCU - PCU instance - Hardware Devices Processors - PSP - PSP instance). If necessary, see Navigating to a
network object class or instance on page 1-28 for further details. The
PSP instance button changes color.

See the general procedure in Modifying a network object using the

OMC-R GUI on page 1-34.
The OMC-R displays the PSP Detailed View in Monitor mode. See PSP
Detailed View fields for details.

PSP Detailed View fields

The following sections list and briefly describe the parameter fields in the PSP Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

6-22

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PSP Detailed View fields

Identification grouping
Table 6-11 describes the fields in the Identification grouping of the PSP Detailed View.

Table 6-11 PSP Detailed View fields - Identification grouping

Field name

Mandatory or
Optional?

Brief description

Values

RDN Class

See description in Table 4-1.

Default is PSP.

RDN Instance

The PSP Identifier field. Also

see description in Table 3-1.

0 or 1.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed View

Displays the parent PCU

name. Click to display the
parent PCU Detailed View.

PCI Vendor ID

See description in Table 6-10.

Optional.

PCI Device ID

See description in Table 6-10.

Optional.

PCI Device Revision

See description in Table 6-10.

Optional.

Cage and Slot Information grouping

Table 6-12 describes the fields in the Cage and Slot Information grouping of the PSP Detailed
View.

Table 6-12 PSP Detailed View fields - Cage and Slot Information grouping
Field name

Brief description

PCU Slot

The slot in the PCU cage

where the PSP is located.

Values
7 or 9.
Default for
PSP 0 is 7.
Default for PSP
1 is 9.

Mandatory or
Optional?
Optional.

Additional Information
Use the Additional Information window to input any notes relating to this PSP. Where additional
notes are not required, close this field by clicking the toggle button next to the Additional
Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

68P02901W17-T

6-23
Jan 2010

Configuring a PCU MSI using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Configuring a PCU MSI using the OMC-R GUI

Introduction to configuring a PCU MSI using the OMC-R GUI

An MSI is a child of a PCU (and a SITE). No more than 24 MSI objects can be created.
A PCU MSI has the MSI type: MSI-E1_PMC (14).
Two MMS object instances are contained under an MSI.
For code download to the PCU, there must be a DPROC in either slot 1 or slot 2 of the PCU with
the MSI on socket 1 of that DPROC.

Prerequisites to creating a PCU MSI

Before creating a PCU MSI, the following must exist:

PCU.

DPROC.

Creating a PCU MSI using the OMC-R GUI

To add an MSI to a PCU using the OMC-R GUI, follow these steps:

Procedure 6-4 Add an MSI to a PCU using the OMC-R GUI

6-24

Navigate to and select the MSI class button in the Navigation Tree
(BSS BSS instance PCU PCU instance Hardware Devices
MSI). If necessary, see Navigating to a network object class or instance
on page 1-28 for further details. The MSI class button changes color.

Select Edit Create from the menu bar.

The OMC-R displays the MSI Detailed View in Create mode.

Complete the fields, as required.

See PCU MSI Detailed View fields for details.

Select File Create from the menu bar.

Select File Close from the menu bar.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PCU MSI Detailed View fields

PCU MSI Detailed View fields

The following sections list and briefly describe the parameter fields in the PCU MSI Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 6-13 describes the fields in the Identification grouping of the PCU MSI Detailed View.

Table 6-13 PCU MSI Detailed View fields - Identification grouping

Field name/
parameter name

Brief description

Values

MSI Type
msi_type

The MSI device type.

RDN Class

See description in Table 4-1.

Default is MSI.

RDN Instance

See description in Table 3-1.

0 or 1.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed View

Displays the parent PCU

name. Click to display the
parent PCU Detailed View.

Default is
MSI-E1_PMC (14).
Only available if
BSS gprsOpt is
enabled (1).

Mandatory or
Optional?
Mandatory.

Cage and Slot Information grouping

Table 6-14 describes the fields in the Cage and Slot Information grouping of the PCU MSI
Detailed View.

Table 6-14 PCU MSI Detailed View fields - Cage and Slot Information grouping
Field name

Brief description

Data Processor

The unique id of the DPROC

where the MSI resides.
Only valid if msi_type is
MSI-E1_PMC.

Data Processor
Socket

The socket on the DPROC

on which the MSI resides.
Only valid if msi_type is
MSI-E1_PMC.

68P02901W17-T

Values

Mandatory or
Optional?

The default is null.

Optional.

Socket 1 or Socket 2.
Default is Socket 1.

Optional.

6-25
Jan 2010

Modifying PCU MSI details from the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Additional Information
Use the Additional Information window to input any notes relating to this device. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Modifying PCU MSI details from the OMC-R GUI

To modify PCU MSI details from the Navigation Tree, see the general procedure in Modifying a
network object using the OMC-R GUI on page 1-34.
The following MSI fields cannot be changed:

Data Processor.

Data Processor Socket.

Deleting a PCU MSI using the OMC-R GUI

Introduction to deleting an MSI
When a PCU MSI is deleted, the OMC-R automatically deletes the MMS objects beneath it.
MMS objects are connected to a GDS and a GBL. If a user attempts to delete a PCU MSI when a
GDS or GBL object exists and the PCU MMS fields in the GDS or GBL Detailed View contain an
MMS object identifier contained within the MSI, the delete operation is rejected by the BSS.

Prerequisites to deleting an MSI

A PCU MSI can only be deleted if:

The MSI has been locked.

The GDS and/or GBL related to the MMS of the MMI have been deleted.

Procedure to delete an MSI

To delete a PCU MSI using the Navigation Tree, see the general procedure in Deleting a network
object using the OMC-R GUI on page 1-37.

6-26

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying and modifying PCU MMS details

Displaying and modifying PCU MMS details

Introduction to displaying and modifying PCU MMS details

When a PCU MSI is created, the OMC-R automatically creates a PCU MMS. Likewise when a
PCU MSI is deleted, the OMC-R automatically deletes the PCU MMS.
A PCU MMS is a child of an MSI under a PCU (and can also be a child of an MSI under a site). A
user cannot create or delete a PCU MSI from the OMC-R Navigation Tree. However, the user
can display and modify details of the PCU MSI using the MSI Detailed View form.
When displayed for a PCU MMS, the MMS Detailed View form displays only the following
information:

rdnClass.

RdnInstance.

nmcRDNInstance.

Parent.

additionalInfo.

opState.

adminState.

adminState.

reasonCode.

timeOfLastTrans.

omcUser.

Prerequisites to viewing and modifying a PCU MMS

Before a PCU MMS details can be viewed or modified:

A PCU must exist.

An MSI must exist.

68P02901W17-T

6-27
Jan 2010

Displaying and modifying an MMS Detailed View

Chapter 6: Configuring a PCU for GPRS

Displaying and modifying an MMS Detailed View

To display and modify details for a PCU MMS using the Navigation Tree, follow these steps:

Procedure 6-5

Display and modify details for a PCU MMS using the Navigation Tree

Navigate to and select the MMS instance button in the Navigation

Tree (BSS - BSS instance - PCU - PCU instance - Hardware Devices MSI - MSI instance). If necessary, see Navigating to a network object
class or instance on page 1-28 for further details. The MSI instance
button changes color.

See the general procedure in Modifying a network object using the

OMC-R GUI on page 1-34.

Monitoring timeslot usage on MMS link

To monitor timeslot usage on an MMS link, see Displaying Channel and Circuit Status on page
9-20.

6-28

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a GDS using the OMC-R GUI

Configuring a GDS using the OMC-R GUI

Introduction to configuring a GDS using the OMC-R GUI

A GPRS Data Stream (GDS) is a child of a PCU.
The GDS provides the link between the BSC and the PCU. It is used to load code into the PCU.
There are three types of GDS:

Transcoder Rate Adaption Unit (TRAU).

TRAU carries the GPRS traffic and is the default type.

Link Access Protocol Data (LAPD)

LAPD carries the GPRS signaling link (GSL).

LAPD_TRAU
When there is Ethernet connectivity between the BSC and the PCU, the GDS type is
LAPD_TRAU. LAPD_TRAU GDSs can carry both GSL and TRAU traffic. Up to 30 GSLs
can be equipped on a GDS and each GSL requires one TDM 64 kbit/s timeslot for LAPD
signaling. All the remaining TDM 64 kbit/s timeslots on the GDS are unused. The PSI
provides the Ethernet link.

TRAU type GDS is equipped only in PRP

LAPD type GDS is equipped only in PICP

LAPD_TRAU type GDS is equipped only in PXP

NOTE
A TRAU type GDS creation fails, if it is terminated on an MSI equipped on a PICP
DPROC and an appropriate message is displayed.
The GDS can be configured over the Ethernet as a child device of ETH. For this new GDS
configuration, the BSC GDS is introduced in pair with the PXP GDS. The GDS configuration
(over E1) changes when the PCU E1 GDS is equipped. BSC side also has a BSC GDS. The BSC
GDS is automatically equipped when the PCU GDS is equipped on the PXP.
A GDS cannot be configured to an MMS on a PICP MSI when the PICP of the other MMS
is supporting a GBL.
The PCU can support a maximum of 36 TRAU GDSs and 2 LAPD GDSs.
A GDS and a GBL cannot be equipped to the same MSI at the PCU.

68P02901W17-T

6-29
Jan 2010

Fault Management of a GDS

Chapter 6: Configuring a PCU for GPRS

Fault Management of a GDS

If an attempt is made to lock, INS, or reset a GDS device, the following warning message is
displayed:
Warning: The GDS carries GPRS data traffic between the BSC and the PCU. Loss of
a GDS device will reduce GPRS traffic capacity between the BSC and the PCU. A
PXP or PRP DPROC with no GDSs in service will not be able to schedule any GPRS
traffic.
Do you wish to <FM activity> device: <object instance>?
Click either OK or Cancel to continue the FM activity, or cancel to abandon the FM activity.

NOTE
In GSR10, the GDS is a BSC side as well as a PCU side device, and has two different
connections, E1 and Ethernet. There are two lock GDS situations:
1.

Lock PCU GDS, E1, or ETH.

2.
Lock BSC GDS, E1, or ETH.
In both cases, connectivity has slight differences. For example, remote GDS is E-U for
ETH and D-U for E1 connections.

Prerequisites to creating a GDS

Before creating a GDS, the following must exist:

PCU

DPROC

MSI and a child MMS, or PSI and an ETH

Creating a GDS using the OMC-R GUI

To add a GDS to the network using the OMC-R GUI, use the following procedure:

Procedure 6-6 Add a GDS to the network using the OMC-R GUI
1

Navigate to and select the GDS class button in the Navigation Tree
(BSS BSS instance PCU PCU instance Logical Links GDS).
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details.
The GDS class button changes color.

Select Edit Create from the menu bar.

The OMC-R displays the GDS Detailed View in Create mode.
Continued

6-30

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Procedure 6-6

GDS Detailed View fields

Add a GDS to the network using the OMC-R GUI (Continued)

Complete the fields, as required. See GDS Detailed View fields for
details.

Select File Create from the menu bar.

Close the GDS Detailed View window by selecting File Close from
the menu bar.

GDS Detailed View fields

The following sections list and briefly describe the parameter fields in the GDS Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 6-15 describes the fields in the Identification grouping of the GDS Detailed View.

Table 6-15 GDS Detailed View fields - Identification grouping

Field name

Brief description

Values

GDS Type

The function type of the GDS.

TRAU (0) or
LAPD (1) or
LAPD_TRAU (2)
Default is 0.

RDN Class

See description in Table 4-1.

Default is GDS.

RDN Instance

See description in Table 3-1.

0 - 19.

NMC RDN Value

See description in Table 4-1.

Parent Detailed View

Displays the parent PCU

name. Click to display the
parent PCU Detailed View.

Mandatory or
Optional?
Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this device. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

68P02901W17-T

6-31
Jan 2010

Modifying GDS details from the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

State grouping
Standard network object state fields, see Table 4-2 for details.

Connectivity Information grouping

Table 6-16 describes the fields in the Connectivity Information grouping of the GDS Detailed
View.

Table 6-16 GDS Detailed View fields - Connectivity Information grouping

Brief description

BSC MMS

The identifier of the MMS at

the BSS (SITE 0) end of the
GDS link.

Mandatory.

PCU MMS

The identifier of the MMS at

the PCU end of the GDS link.

Mandatory.

ETH

Ethernet port on the PSI

card at the BSC or on the
PXP DPROC card at the PCU
used for GDS functionality.
There is only one ETH on PSI
and one on PXP DPROC.

Mandatory.

gds_connectivity

This parameter indicates

GDS connectivity.

Minimum value
is 0 or E1.
Maximum value
is 1 or Ethernet.

bsc_eth

This parameter describes the

Ethernet connectivity.
psi_id indicates a unique PSI
ID.
bsc_eth_port indicates the
BSC Ethernet port.

Minimum value:
psi_id - 0
bsc_eth_port - 0

pcu_eth

This parameter describes the

Ethernet connectivity.
dproc_id indicates a unique
DPROC ID.
pcu_eth_port indicates the
PCU Ethernet port.

Values

Mandatory or
Optional?

Field name

Maximum value:
psi_id - 11
bsc_eth_port - 0
Minimum value:
dproc_id - 1
pcu_eth_port - 0
Maximum value:
dproc_id - 16
pcu_eth_port - 0

Modifying GDS details from the OMC-R GUI

To modify GDS details from the Navigation Tree, see the general procedure in Modifying a
network object using the OMC-R GUI on page 1-34.

6-32

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a GDS using the OMC-R GUI

The following GDS fields cannot be modified:

GDS Type.

RdnInstance.

BSC MMS.

PCU MMS.

Deleting a GDS using the OMC-R GUI

Prerequisites
A GDS can only be deleted if all the GSLs on the GDS have been deleted.

Procedure
To delete a GDS using the Navigation Tree, see the general procedure in Deleting a network
object using the OMC-R GUI on page 1-37.

68P02901W17-T

6-33
Jan 2010

Configuring a GSL using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Configuring a GSL using the OMC-R GUI

Introduction to configuring a GSL using the OMC-R GUI

A GPRS Signaling Link (GSL) is a child of a PCU. The GSL is used for signaling, communications
to and from the BSC, and for loading code on to the PCU. A GSL can only be created on a
LAPD or a LAPD_TRAU type GDS. A maximum of 30 GSLs can be created for a single GDS of
type LAPD (that is, 30 GSLs can be equipped on a LAPD type GDS or 2 LAPD GDSs can be
equipped on a PICP or PXP DPROC). The PCU supports a maximum of 60 GSLs. The PCU can be
codeloaded either over GSL or over GbE link, depending on boards configured in slots 1, 2, or
11. When a GSL is created the BSS ensures that there are sufficient LCF resources to manage it.
In the SYSGEN mode, a GSL must be equipped in the default location before SYSGEN mode
can be exited.

Defining the GSL equipage mode

Use the TTY interface and the BSS parameter gsl_lcf_mapping to determine the mode of
GSL equipage. This parameter can only be modified in SYSGEN mode. Table 6-17 gives
gsl_lcf_mapping details.

Table 6-17 gsl_lcf_mapping

Parameter name

Brief description

gsl_lcf_mapping

Determines the way in which

the GSL is equipped. If
Manual mode is selected,
the user is prompted to
enter the LCF during the
equipage of a GSL. If Auto
mode is selected, the system
automatically distributes the
equipped GSL to a useable
LCF. During SYSGEN mode,
gsl_lcf_mapping cannot
be changed if any GSLs are
equipped.

Values
Manual (0) or Auto
(1). In SYSGEN
mode, the default is
Auto (1). Outside
SYSGEN mode, the
default is Manual
(0).

Mandatory or
Optional?
Optional.

For example, the following command changes the value of gsl_lcf_mapping before any GSLs
are equipped while in SYSGEN mode:
chg_element gsl_lcf_mapping 0 1

6-34

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Prerequisites to creating a GSL

Prerequisites to creating a GSL

Before creating a GSL, the following must exist:

PCU.

Associate GDS.

LCF.

A GSL cannot be created if the total number of max_gsls for all LCFs would be less than the
total number of equipped GSLs.

Creating a GSL using the OMC-R GUI

To add a GSL to the network using the OMC-R GUI, follow these steps:

Procedure 6-7 Add a GSL to the network using the OMC-R GUI
1

Navigate to and select the GSL class button in the Navigation Tree
(BSS BSS instance PCU PCU instance Logical Links GSL).
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details.
The GSL class button changes color.

Select Edit Create from the menu bar.

The OMC-R displays the GSL Detailed View in Create mode.

Complete the fields, as required.

See GSL Detailed View fields for details.

Select File Create from the menu bar.

Close the GSL Detailed View window by selecting File Close from
the menu bar.

GSL Detailed View parameter fields

The following sections list and briefly describe the parameter fields in the GSL Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

68P02901W17-T

6-35
Jan 2010

Deleting a GSL using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Identification grouping
Table 6-18 describes the fields in the Identification grouping of the GSL Detailed View.

Table 6-18 GSL Detailed View fields - Identification grouping

Values

Mandatory or
Optional?

Field name

Brief description

RDN Class

See description in Table 4-1.

Default is GSL.

RDN Instance

See description in Table 3-1.

0 - 59.

NMC RDN Value

See description in Table 4-1.

Parent Detailed View

Displays the parent PCU

name. Click to display the
parent PCU Detailed View.

GDS Identifier

Identifier of the GDS on

which this GSL resides.
Cannot be modified.

0 to 37.

Mandatory.

LCF managing this

GSL

Determines the LCF to

which the GSL is equipped.
Only displayed when
gsl_lcf_mapping is set
to Manual, see Table 6-17 for
details.

0 to 24.

Mandatory.

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this device. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard network object state fields, see Table 6-23 for details.

Deleting a GSL using the OMC-R GUI

Prerequisites for deleting a GSL
A GSL must be locked before it can be deleted. See OMC-R Online Help, Network Operations
for details of how to lock a device.

NOTE
When the last GSL is locked, the PCU becomes OOS.

6-36

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a GSL using the OMC-R GUI

Procedure for deleting a GSL

To delete a GSL using the Navigation Tree, see the general procedure in Deleting a network
object using the OMC-R GUI on page 1-37.

68P02901W17-T

6-37
Jan 2010

Configuring a GBL using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Configuring a GBL using the OMC-R GUI

Introduction to configuring a GBL using the OMC-R GUI

A Gb Link (GBL) is a child of a PCU. A GBL device describes a group of timeslots on a link which
is configured as a frame relay link for communication between a BSS and the SGSN. Only one
GBL can reside on a single E1 link. The maximum number of GBLs per PCU is 12. A GBL must
not be configured to an MMS on the last PICP MSI. A GBL cannot be configured to an MMS on a
PICP MMI when the other MMS is supporting a GDS. A GBL and a GDS cannot be created for
the same MSI at the PCU. A GBL cannot be created for an MMS on a PICP MSI when the other
MMS is supporting a GDS. The loss of a GBL causes all NSVCs on the GBL to become blocked.

Prerequisites to creating a GBL

Before creating a GBL the following must exist:

PCU.

MMS.

Creating a GBL using the OMC-R GUI

To add a GBL to the network using the OMC-R GUI, follow these steps:

Procedure 6-8

6-38

Add a GBL to the network using the OMC-R GUI

Navigate to and select the GBL class button in the Navigation Tree
(BSS BSS instance PCU PCU instance Logical Links GBL).
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details.
The GBL class button changes color.

Select Edit Create from the menu bar. The OMC-R displays the GBL
Detailed View in Create mode.

Complete the fields as required. See GBL Detailed View fields for
details.

Select File Create from the menu bar.

Select File Close from the menu bar.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GBL Detailed View fields

GBL Detailed View fields

The following sections list and briefly describe the parameter fields in the GBL Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 6-19 describes the fields in the Identification grouping of the GBL Detailed View.

Table 6-19 GBL Detailed View fields - Identification grouping

Field name/BSS
parameter name

Mandatory or
Optional?

Brief description

Values

First GBL Timeslot

start_ts.

The first timeslot for the

GBL. When creating a GBL,
the First GBL Timeslot field
(parameter name: start_ts)
must be less than or equal to
the Last GBL Timeslot field
(parameter name: end_ts).

1 - 31 (the timeslot
number on the
span).

Mandatory.

Last GBL Timeslot

end_ts.

The last timeslot for the

GBL on the span. Also see
start_ts.

1 - 31 (the timeslot
number on the
span).

Mandatory.

RDN Class.

See description in Table 4-1.

Default is GBL.

RDN Instance.

See description in Table 3-1.

0 - 3.
The default is 0.

NMC RDN Value.

See description in Table 4-1.

Parent Detailed View.

Displays the parent PCU

name. Click to display the
parent PCU Detailed View.

Connectivity Information grouping

Table 6-20 describes the fields in the Connectivity Information grouping of the GBL Detailed
View.

68P02901W17-T

6-39
Jan 2010

GBL Detailed View fields

Chapter 6: Configuring a PCU for GPRS

Table 6-20 GBL Detailed View fields - Connectivity Information grouping

Mandatory or
Optional?

Field name

Brief description

Values

PCU MMS

The identifier of the MMS

at the PCU end of the GBL.
Cannot be modified.

The default is 0.

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this device. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Frame Relay Information grouping

Table 6-21 describes the fields in the Frame Relay Information grouping of the GBL Detailed
View.

Table 6-21 GBL Detailed View fields - Frame Relay Information grouping
Field name

6-40

Brief description

Values

Mandatory or
Optional?

Link Integrity Timer

T391

The value of the Frame

Relay default link Integrity
Verification Polling Timer in
seconds.

5 - 30.
Default is 10.

Mandatory.

Polling Verification
Timer T392

The value of the Frame Relay

default polling Verification
Timer in seconds.

5 - 30.
Default is 15.

Mandatory.

Full Status Polling

Counter N391

The Frame Relay default

Full Status Polling Counter,
specified as a number of
polling cycles.

1 - 255.
Default is 6.

Mandatory.

Error Threshold
Counter N392

The Frame Relay default

value for Error Threshold
Counter, specified as a
number of errors.

1 - 10.
Default is 3.

Mandatory.

Monitored Events
Counter N393

The Frame Relay default

value for Monitored Events
Counter, specified as a
number of events.

1- 10.
Default is 4.

Mandatory.

NS Access Rate

The Frame Relay Access rate

specified in kbit/s. Cannot be
modified.

64 - 1984 (kbit/s
in steps of 64).
Default is 64.

Mandatory.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a GBL using the OMC-R GUI

Fields causing GBL cycling

If the following fields are changed, the OMC-R displays a warning message that the GBL will
be cycled:

Link Integrity Timer T391 (BSS parameter name: t391).

Polling Verification Timer T392 (BSS parameter name: t392).

Full Status Polling Counter N391 (BSS parameter name: n391).

Error Threshold Counter N392 (BSS parameter name: n393).

Monitored Events Counter N393 (BSS parameter name: n393).

First GBL Timeslot (BSS parameter name: start_ts).

Last GBL Timeslot (BSS parameter name: end_ts).

When one of these parameters is changed the following message is displayed:

WARNING: Modifying this attribute will cause the GBL to be cycled.
to Modify?

Do you wish

When a second parameter is modified the OMC-R displays the following message:
WARNING: The attribute you have just modified will cause the GBL to be cycled
when the Detailed View is saved. You have already modified attributes that cause
the GBL to be cycled on Saving. If you do not wish to proceed, select File Revert to undo your changes.
When saving the changes, the OMC-R displays the following message if parameters have been
changed which cause the GBL to be cycled:
WARNING: You have modified attribute(s) that cause the GBL which is specified by
the GBL Identifier to be cycled when you select OK. Do you wish to modify? If
you do not wish to proceed, select Cancel, which shall undo all your changes.

Deleting a GBL using the OMC-R GUI

Introduction to deleting a GBL
When a GBL is deleted, all associated NSVCs are automatically deleted.

Prerequisites to deleting a GBL

A GBL can only be deleted if:

The GPRS Enabled field (BSS parameter name: gprs_enabled) in the associated CELL
Detailed View forms is set to False (0). (To propagate cell parameters to other cells, use
the cell propagation facility options in the menu bar of the CELL Detailed View form.)

It does not contain the last NSVC at the PCU. Otherwise the GPRS Enabled field (BSS
parameter name: gprs_enabled) in the associated CELL Detailed View set forms to False
(0) before deleting the GBL.

68P02901W17-T

6-41
Jan 2010

Deleting a GBL using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Procedure for deleting a GBL

To delete a GBL using the Navigation Tree, see the general procedure in Deleting a network
object using the OMC-R GUI on page 1-37.

6-42

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring an NSVC using the OMC-R GUI

Configuring an NSVC using the OMC-R GUI

Introduction to configuring an NSVC using the OMC-R GUI

A Network Service Virtual Connection (NSVC) is a child of a PCU. An NSVC describes the
mapping of an NSVCI to a GBL and Data Link Connection Identifier (DLCI) with associated
control parameters.
Network Service Virtual Connection Identifier (NSVCI) are not displayed in the Navigation Tree.

NOTE
The NSVC state of a PCU is only displayed after an Audit.

Prerequisites to creating an NSVC

Before creating an NSVC the following must exist:

PCU.

GBL.

Creating an NSVC using the OMC-R GUI

To add an NSVC to the network using the OMC-R GUI, follow these steps:

Procedure 6-9 Add an NSVC to the network using the OMC-R GUI
1

Navigate to and select the NSVC class button in the Navigation Tree
(BSS BSS instance PCU PCU instance Logical Links
NSVC). If necessary, see Navigating to a network object class or
instance on page 1-28 for further details.
The NSVC class button changes color.
Continued

68P02901W17-T

6-43
Jan 2010

NSVC Detailed View parameter fields

Procedure 6-9

Chapter 6: Configuring a PCU for GPRS

Add an NSVC to the network using the OMC-R GUI (Continued)

Select Edit Create from the menu bar.

The OMC-R displays the NSVC Detailed View in Create mode.

NOTE
An NSVC can also be created from the NSVC List by using
File Create, which also displays the NSVC Detailed View
in Create mode.
3

Complete the fields as required.

See NSVC Detailed View fields for details.

Select File Create from the menu bar.

Select File Close from the menu bar to close the NSVC Detailed View.

NSVC Detailed View parameter fields

The following sections list and briefly describe the parameter fields in the NSVC Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 6-22 describes the fields in the Identification grouping of the NSVC Detailed View.

Table 6-22 NSVC Detailed View fields - Identification grouping

Field name

Brief description

Values

Mandatory or
Optional?

Data Link Connection

Identifier

The Data Link Connection

Identifier on the GBL.

16 - 991.

Mandatory.

GBL Identifier

The object identifier of the

GBL.

0 - 11.

Mandatory.

RDN Class

See description in Table 4-1.

Default is NSVC.
Continued

6-44

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

NSVC Detailed View parameter fields

Table 6-22 NSVC Detailed View fields - Identification grouping (Continued)

Field name

Brief description

Values

NSVCI

A unique NSVC identifier.

When creating the first NSVC
for the PCU the default value
(0) is unique and does not
have to be changed.

0 - 65535. The
default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed View

Displays the parent PCU

name.
Click to display the parent
PCU Detailed View.

Mandatory or
Optional?

Additional Information
Use the Additional Information window to input any notes relating to this device. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

NS Information grouping
Table 6-23 describes the fields in the NS Information grouping of the NSVC Detailed View.

Table 6-23 NSVC Detailed View fields - NS Information grouping

Field name

Brief description

Values

Mandatory or
Optional?

NS Committed
Information Rate

The committed information

rate in kbit/s for NSVC. If
either the NS Committed
Information Rate or the NS
Burst Size field is set to 0,
then both fields must be set
to 0.

0 - 1984.
There is no default
value.

Mandatory.

NS Burst Size

Specifies burst rate in kbit/s

for this NSVC. If either the
NS Committed Information
Rate or the NS Burst Size
field is set to 0, then both
fields must be set to 0.
The fields BS Burst Size and
NS Burst Excess must not
both have a value of 0.

0 - 1984.
There is no default
value.

Mandatory.

NS Burst Excess

Specifies burst rate in kbit/s

for this NSVC. The fields
BS Burst Size and NS Burst
Excess must not both have a
value of 0.

0 - 1984.
There is no default
value.

Mandatory.

68P02901W17-T

6-45
Jan 2010

Modifying NSVC details from the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Modifying NSVC details from the OMC-R GUI

Introduction to modifying NSVC details
The BSS ensures that the last NSVC in the BSS cannot be modified until all the GBLs have
been locked.

NOTE
The NSVC state of a PCU is only displayed after an Audit.

Prerequisites to modifying NSVC details

Before NSVC details can be modified, set the GPRS Enabled field to FALSE (0) in the CELL
Detailed View form for all associated cells.

Procedure to modify NSVC details

To modify NSVC details from the Navigation Tree, follow these steps:

Procedure 6-10

Modify NSVC details from the Navigation Tree

Navigate to the NSVC class button in the Navigation Tree (BSS

BSS instance PCU PCU instance Logical Links NSVC). If
necessary, see Navigating to a network object class or instance on
page 1-28 for further details.

Click the folder icon next to the NSVC type button.

The OMC-R displays the NSVC List.
The NSVC List displays a list of all NSVCs associated with the PCU. For
each NSVC, values are shown for the following:

NSVC identifier (NSVCI).

Data Link Connection Identifier (DLCI)

GBL identifier.

NS Committed Rate.

NS Burst Size.

NS Burst Excess.

Click the NSVC to be modified. The OMC-R highlights the entry.

From the menu bar, select Edit Detailed View. The OMC-R displays
the NSVC Detailed View in Monitor mode. (An NSVC can also be
created from the NSVC List using File - Create.)
Continued

6-46

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Modifying NSVC details from the OMC-R GUI

Procedure 6-10 Modify NSVC details from the Navigation Tree (Continued)
5

Select Edit Edit from the menu bar of the NSVC Detailed View form.

Modify the required fields. See NSVC Detailed View fields for details.
The following fields cannot be modified:

Data Link Connection Identifier.

GBL Identifier.

NSVCI.

If the following fields are modified, the OMC-R displays a series of

warning message that the specified GBL is cycled:

NS Committed Information Rate (BSS parameter name:

ns_com_rate)

NS Burst Size (BSS parameter name: ns_burst_size)

NS Burst Excess (BSS parameter name: ns burst_excess)

When one of these parameters is changed the following message is

displayed:
WARNING: Modifying this attribute will cause the GBL which
is specified by the GBL Identifier to be cycled. Do you
wish to Modify?
When a second parameter is modified the OMC-R displays the following
message:
WARNING: The attribute you have just modified will cause the
GBL which is specified in the GBL Identifier to be cycled
when the Detailed View is saved. You have already modified
attributes that cause the GBL to be cycled on Saving. If
you do not wish to proceed, select File Revert to undo
your changes.

68P02901W17-T

Select File Save from the menu bar to save any changes.
The OMC-R displays the following message if parameters have been
changed which cause the GBL to be cycled:
WARNING: You have modified attribute(s) that cause the GBL
which is specified by the GBL Identifier to be cycled when
you select OK. Do you wish to modify? If you do not
wish to proceed, select Cancel, which shall undo all your
changes.
Click OK or Cancel as required.

Select File Close from the menu bar to close the NSVC Detailed View.

6-47
Jan 2010

Deleting an NSVC using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Deleting an NSVC using the OMC-R GUI

To delete an NSVC using the Navigation Tree, follow these steps:

Procedure 6-11

6-48

Delete an NSVC using the Navigation Tree

Navigate to the NSVC class button in the Navigation Tree (BSS

BSS instance PCU PCU instance Logical Links NSVC). If
necessary, see Navigating to a network object class or instance on
page 1-28 for further details.

Click the folder icon next to the NSVC type button. The OMC-R
displays the NSVC List.
The NSVC List displays a list of all NSVCs associated with the PCU.

Click the NSVC to be deleted.

The OMC-R highlights the entry.

Select Edit Delete from the menu bar.

The OMC-R displays a deletion confirmation message.

Click OK to confirm the deletion.

After a few seconds, the OMC-R deletes the NSVC from the NSVC List.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring an SGSN (GPRS) using the OMC-R GUI

Configuring an SGSN (GPRS) using the OMC-R GUI

SGSN configuration
The SGSN can only be created using the OMC-R GUI. It cannot be created using the equip
command.

GPRS SGSN network topology

GPRS functionality requires a PCU to link the Serving GPRS Support Node (SGSN) into each
GSM BSC. The SGSN is connected to the PCU by the Gb link (GBL).

Multiple SGSNs
When a GBL is created, it is associated with a Commslink (that is, it is added as a Related Device
to the Commslink object). By default, a GBL is associated with the Commslink between the PCU
and SGSN-0. This default can be modified to a specified SGSN for all the GBLs at a particular
BSS, by setting the Related SGSN attribute of the BSS to the required SGSN. This associates
the GBLs to the Commslink between the PCU and the specified SGSN.

Creating an SGSN using the Navigation Tree

To create an SGSN follow these steps:

Procedure 6-12

68P02901W17-T

Create an SGSN using the Navigation Tree

Navigate to and select the SGSN class button in the Navigation Tree
(Network SGSN).
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details. The SGSN class button changes color.

Select Edit Create from the menu bar.

The OMC-R displays the SGSN Detailed View.

Complete the fields, as required.

See SGSN Detailed View fields for further details.

Create and close the Detailed View form.

6-49
Jan 2010

SGSN Detailed View fields

Chapter 6: Configuring a PCU for GPRS

SGSN Detailed View fields

The following sections list and briefly describe the parameter fields in the SGSN Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 6-24 describes the fields in the Identification grouping of the SGSN Detailed View.

Table 6-24

SGSN Detailed View fields - Identification grouping

Field name

Values

Brief description

Name

Unique SGSN name.

RDN Class

See description in Table 4-1.

Default is SGSN.

RDN Instance

See description in Table 3-1.

Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed View

Click to display the parent

Network Detailed View.

Up to 31 characters
plus the NULL
character.

Mandatory or
Optional?
Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this SGSN. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Map Information grouping

Standard map information fields, see Table 4-15 for details.

6-50

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying and modifying an SGSN

Displaying and modifying an SGSN

To modify an SGSN, refer to the general procedure in Modifying a network object using the
OMC-R GUI on page 1-34.

Deleting an SGSN
To delete an SGSN, refer to the general procedure in Deleting a network object using the
OMC-R GUI on page 1-37.

68P02901W17-T

6-51
Jan 2010

Configuring the PCU and its devices from the TTY interface

Chapter 6: Configuring a PCU for GPRS

Configuring the PCU and its devices from the TTY

interface

Introduction
To configure a PCU or any of its contained devices using the TTY interface, use the equip
command. This is referred to as equipping a device.
Use the equip command to create the PCU and its contained devices, and the unequip
command to delete a PCU and its contained devices. These commands are described in detail in
the manual: Technical Description: BSS Command Reference (68P02901W23).
The BSS supports PCU equipage and unequipage inside and outside SYSGEN mode.
If the Local Maintenance field (BSS parameter name: local_maintenance) in the BSS Detailed
View form has been set to False (0), the TTY interface cannot be used to configure a PCU either
remotely through Remote Login (Rlogin) or locally at the BSS.

Examples of the equip command

Equipping a PCU
The general form of the equip command for a PCU is:
equip <site_id> PCU
For example, to equip a PCU at the BSC, enter the following command:
equip 0 PCU
The system then prompts for further information (text shown in bold indicates an example user
response to each prompt):
Enter the PCU Identifier (default 0):
Enter the IP address:

192.168.53.17

Enter the IP subnet mask:

255.255.255.0

Enter the IP address of the default router:

Enter the NSEI value:

192.168.53.254

COMMAND ACCEPTED

6-52

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS commands supporting a PCU and its devices

Equipping a PCU device

The general form of the equip command for PCU devices is:
equip PCU<_id> <device_id>
Where _id is the PCU identifier (in the range 0 - 2) and device_id is replaced by any device
acronym shown in Table 6-1.
To equip a DPROC at PCU_1, enter the following command:
equip PCU_1 DPROC
Depending on the device type, the system then prompts the user for further information.
The equip and unequip command cannot be used to equip the following devices, instead these
devices are auto-equipped when the PCU is created:

PSP.

Cage.

Cabinet.

BSS commands supporting a PCU and its devices

The following BSS commands support a PCU and its devices:

assess to assess the condition of the equipment or device.

device_audit to audit a specific device (For use on a PSP, only supported for the active
PSP).

disp_equip to display equipment and device details.

disp_processor to display processor details.

chg_audit_sched to schedule an audit execution.

ins_device to INS a device.

lock and unlock to lock or unlock a device.

modify_value to change database values. For example, to modify PCU parameters, such
as ip_address, subnet_mask, and so on.

reset_site and reset_device to reset a device or site.

state to display the status of a device.

status_mode to disable/enable status notification.

site_audit to audit devices at a site.

These commands are described in detail in the manual: Technical Description: BSS Command
Reference (68P02901W23).

68P02901W17-T
Jan 2010

6-53

BSS commands supporting a PCU and its devices

6-54

Chapter 6: Configuring a PCU for GPRS

68P02901W17-T
Jan 2010

Chapter

7
Configuring a Site

The procedures here show how to configure BSC and BTS sites. The following topics are
described:

Introduction to BSC and BTS sites on page 7-2.

Overview of adding a BTS on page 7-12.

Adding a BTS using a batch rlogin script on page 7-14.

Adding a BTS using the TTY interface (example 1) on page 7-17.

Adding a BTS using the TTY interface (example 2) on page 7-21.

Creating a SITE using the OMC-R GUI on page 7-26.

Modifying SITE parameters on page 7-34.

Equipping cabinets and cages at a remote BTS on page 7-36.

Deleting and unequipping TCU/CTU cabinets on page 7-39.

Extending an existing path to a new site using the TTY interface on page 7-40.

GCLK synchronization on page 7-43.

Barring calls at a site using the TTY interface on page 7-55.

NOTE
For full details on the design considerations of a BTS site, refer to System Information:
BSS Equipment Planning (68P02900W21).

68P02901W17-T
Jan 2010

7-1

Introduction to BSC and BTS sites

Chapter 7: Configuring a Site

Introduction to BSC and BTS sites

Overview of a BSS and its connections

The BSC maintains a database which it uses to manage physical connections throughout the
BSS. Physical connections are made using E1 links (MMSs on MSI devices). The path device
provides a logical representation of a particular route between the BSC, and a destination BTS.
Equipping RSL devices and RTF functions for a remote BTS requires defining the path between
the BSC and the remote BTS. Each RTF function can be provided with a redundant path.

BSS links and control functions

The links and control functions for the BSS network are managed at the BSC (see Figure 7-1).
For Type 1 or 2 BSCs, management is shifted to particular LCF functions.
The LCF functions at larger BSCs are used to control the MTLs between the MSC and the BSC,
and the RSLs between the BSC and remote BTSs. Assignment of a remote BTS to a particular
LCF is made when the remote BTS site device is equipped.
Each RSL for a remote BTS is assigned a path when the RSL devices are equipped. Equip
at least one default RSL.
The RTFs at remote BTSs are assigned to a primary and, optionally, a secondary path when the
RTF function is equipped.

Figure 7-1 Simplified MSC (SMLC) - BSC-BTS links

MTL
(LMTL)

MSC
(SMLC)

RSL RTF

BSC

BTS

TRAFFIC

TYPE 1 or 2 - LCF 0 to 16
ti-GSM-SimplifiedMSC_SMLC_-BSC-BTSlinks-00791-ai-sw

7-2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BSS topology and path limitations

BSS topology and path limitations

This discussion of BSS topology and path device limitations uses the hypothetical BSS site
drawing shown in Figure 7-2.

Figure 7-2
27

Hypothetical BSS site

21

17

13

10

A and B indicate
parallel E1 links
28

22

18
A

29

14
B

23
BSC

30

24

31

25

19

15

11

32

26

20

16

12

Net02_4_14

ti-GSM-HypotheticalBSSsite-00792-ai-sw

Path devices
Usage
One of the more important concepts of using path devices for multiple routes between the BSC
and a destination BTS, is that topological terms such as spoke, fork, or loop are not considered all paths reduce to a straight line. Consider the loop formed by BSC-10-4-3-9-BSC. Available
paths to BTS 3 are BSC-10-4-3 and BSC-9-3.

68P02901W17-T

7-3
Jan 2010

Path devices

Chapter 7: Configuring a Site

NOTE
The BTS code loads on the MMS on which the RSL is equipped. The RSL is equipped
on a PATH which can have a primary path and a secondary path. If the primary path
on which the RSL is equipped is in service (BU) then the BTS code loads through
PATH1s MSSs.

Maximum number of BTSs

A path can include a maximum of ten BTSs. For this reason, a path to BTS 31 or 32 that includes
a 2.048 Mbit/s link between BTSs 5 and 6 cannot be made since total BTSs would exceed the
maximum (15-11-5-6-12-16-20-19-25-26-32). Valid paths for BTS 32 are 15-11-5-20-19-25-26-32
and 19-25-26-32.

Maximum number of paths

A maximum of ten paths can be equipped for a BTS. Consider equipping the following nine
paths for BTS 22:

BSC-22.

BSC-18A-27-22.

BSC-18A-22.

BSC-18B-27-22.

BSC-18B-22.

BSC-18A-27-28-22.

BSC-18A-17-22.

BSC-18B-27-28-22.

BSC-18B-17-22.

Only one additional path from all the paths that are still available can be equipped.

7-4

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

MSI and RSL restrictions

MSI and RSL restrictions

MSI devices at a remote BTS have the following restrictions:

A maximum of ten MSIs (numbered 0 - 9) can be equipped, which provides 20 MMS

circuits. A site can have up to ten paths, the remaining MMS circuits are available for
paths that terminate at other BTSs.

NOTE
The maximum number of MSIs at a remote BTS is dependent on the BTS type,
number of radios equipped, and the number of associated DRIMs. DRIMs take
up the slots used by MSIs, and therefore reduce the number of MSIs that can
be equipped.

A recommendation is that RSL 0 is assigned to the first default RSL and RSL 1 to the
second.

Default RSLs use specific timeslots of the Abis link. Table 7-1 identifies these timeslots
and cages.

Table 7-1 Default RSLs - Timeslots and Cages

Cage

MSI Slot Number

MMS Group

Abis Timeslot Used

15

16

16

14

16

14

NOTE
This table only applies to InCell BTS sites only.

68P02901W17-T

The path intended for the first default RSL must terminate at MMS 0 of the MSI equipped
in cage 15, slot 16.

7-5
Jan 2010

RTF considerations

Chapter 7: Configuring a Site

The path intended for the second default RSL must terminate as:
MMS 1 of the MSI equipped in cage 15, slot 16 for a BTS with a single MSI.
MMS 0 of the MSI equipped in cage 15, slot 14 for a BTS with a single cage.
MMS 0 of the MSI equipped in cage 14, slot 16 for a BTS with two or more cages.

The RSL connections differ depending upon if the site is a Horizon II macro or non Horizon
II macro site.
Table 7-2 identifies the default RSLs for Horizon II macro site.
Table 7-3 identifies the default for non Horizon II macro site.

Table 7-2

Default RSLs - Timeslots and Card frame for Horizon II macro Site

Card frame

NIU2 Number

Span

Timeslot Used

Table 7-3 Default RSLs - Timeslots and Card frame for non Horizon II macro Site
Card frame

NIU Number

Span

Timeslot Used

RTF considerations
When RTF functions are equipped, a primary path must be specified. Once equipped, this path
cannot be changed without first unequipping the RTF. For this reason, consider the future
network changes before equipping RTFs.
The optional secondary path can be specified when the RTF is first equipped. The secondary
path can be added or changed at a later time.

NOTE
An important concept relating to RTF paths is that whenever there are two paths
equipped, the shortest path (fewer intervening BTS sites) are used. For example,
if the secondary path is shorter after being added or changed, it is chosen as the
primary path. When paths are equal in length, the primary path is selected.
When the selected path is not available, the RTF is switched over to the alternate path. The RTF
switches back to the shortest path when availability is restored.

7-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

RSL/TCH and BSC-BTS dynamic allocation considerations

RSL/TCH and BSC-BTS dynamic allocation considerations

If the RSL at a BTS is set to use 16 kbit/s (SITE parameter: rsl_rate) and ts_sharing is enabled
at the BTS, the remaining three 16 kbit/s TCHs on the 64 kbit/s timeslot are used for backhaul
for that BTS only. This means there are three additional TCHs that can be used by any cell at
that BTS only. In addition, the three additional TCHs are reserved only for cells at the site with
16 kbit/s RSL. Other BTSs in the Dynet cannot use the additional three TCHs.
For example, if there are 10 timeslots in the Dynet, 40 TCHs are available to all cells in the
Dynet. If BTS1 has a 16 kbit/s RSL and BTS2 has 64 kbit/s RSL, then Cell1 at BTS1 has 43
TCHs available to share with the other cells at BTS1. However, at BTS2 only 40 TCHs are
available for the cells to share, because the RSL at BTS2 is 64 kbit/s and BTS2 cannot use the
three TCHs from the 16 kbit/s RSL at BTS1.

900/1800 Horizonmicro2 and Horizoncompact2 BTS

Overview
The BTS equipment models available are:

Horizonmicro2.

Horizoncompact2.

These BTS models can only be created and configured if the HorizonMicro/HorizonCompact
field (BSS parameter name: HorizonMicCom2Opt) in the BSS Detailed View is set to Enabled
(1), see Figure 4-4. This setting can also be displayed using the disp_options TTY command,
see Technical Description: BSS Command Reference (68P02901W23) for further details.

68P02901W17-T

7-7
Jan 2010

Horizon II BTS

Chapter 7: Configuring a Site

Horizonmicro2 and Horizoncompact2 configuration

This BTS consists of a master BTS device, and one or two slave BTS devices.
At a Horizonmicro2 and Horizoncompact2 BTS, each device determines whether it is
configured as a master Horizonmicro2 and Horizoncompact2 or a slave Horizonmicro2 and
Horizoncompact2. Only the master is connected to the BSC (possibly through intermediate BTS
sites). The E1 lines terminate at the master Horizonmicro2 and Horizoncompact2, so a device
determines whether it is a master or a slave according to whether it has a E1 connection.
The BSS software also determines whether it is running on a slave or master Horizonmicro2
and Horizoncompact2 BTS.
When configuring a BTS and its devices,

NOTE

Up to three Cabinet devices can be equipped at a Horizonmicro2 and

Horizoncompact2 BTS site. Each cabinet represents a BTS. The first Cabinet
equipped is the master, the second (and third, if necessary) the slave. See
Equipping cabinets and cages at a BSS site on page 4-51 for further details.

The slave is represented by a DHP device. Two DHPs can be supported. A

Horizonmicro2 DHP is different from an InCell BTS DHP, see Configuring a DHP
device on page 9-59 for further details.

DRI devices are statically assigned to a Cabinet device. A parent-child

relationship exists between the DHP of the Cabinet, and the DRI devices assigned
to it. Up to six carriers can be supported; two at the master unit and two at each
slave. The DHP at the slave unit must be in-service before a DRI device can
come in-service. See Configuring a DRI on page 9-63 for further details.

For further details of this feature, see manual: Technical Description: BSS Implementation

(68P02901W36).

Horizon II BTS
Horizon II can be divided into two main areas:

7-8

CTU2 radio

Horizon II macro BTS cabinet hardware

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Horizon II BTS

CTU2 radio
The CTU2 provides the following functionality:

Double density carrier support

The CTU2 transceiver has the ability to support two logical carriers within a single
transceiver unit. The number of carriers to be supported can be defined by a user using
the DRI parameter dri_density. See Configuring a DRI on page 9-63 for further details.
The CTU2 can operate in single or double density mode in a Horizonmacro or Horizon II
macro cabinet.

Backwards compatibility
The CTU2 can be placed within the Horizonmacro platform. The Horizonmacro
cabinet can be a controlling cabinet or an extension cabinet connected to a Horizon II
macro/Horizonmacro/M-Cell controlling cabinet.

68P02901W17-T

900 MHz or 1800 MHz.

7-9
Jan 2010

Horizon II BTS

Chapter 7: Configuring a Site

Horizon II macro cabinet

The Horizon II macro BTS hardware provides the following functionality:

Support for up to six double density CTU2s/CTU2-Ds.

Each CTU2/CTU2-D FRU can support two independent carriers simultaneously, therefore
up to 12 carriers can be supported in a Horizon II macro cabinet.

900 MHz and 1800 MHz cabinets.

Support of MCUF functionality with the Horizon II Site Controller (HIISC).

NOTE
The HIISC is not backward compatible with MCU/MCUF and cannot be used as
a direct replacement for a MCU(F) in a Horizon/M-Cell cabinet.
The Horizon II macro Site Controller (HIISC) acts as the main processor card with the
Horizon II macro cabinet. It performs the same functions when located in a Horizonmacro
cabinet.

Multiplexing functionality
To allow the Horizon II macro cabinet to be used as an extension cabinet, an XMUX card
provides multiplexing of data to and from the controlling cabinet. The XMUX card slots
into the HIISC slot in the digital card cage.

Site I/O panel

In the Horizon II macro cabinet, the fiber connectors are consolidated on to the Site I/O
panel.

Increased RSL functionality

The integrated NIU on the HIISC supports up to six E1 span connections, with up to
four RSL devices per span. The RSL devices can be provisioned with either 16 kbit/s or
64 kbit/s channels.

Interoperability
The Horizon II macro BTS platform can be used as controlling or extension cabinets within
sites with a mixture of M-Cell and Horizonmacro equipment.

Compact Digital Module.

The presence of the HIISC in the Horizon II macro cabinet allows the size of the Digital
Module to be reduced, due the removal of slots required for multiple FRUs (NUI/FMUX).

SURF2 (Sectorized Unified Receiver Front-end).

The SURF2 module in the Horizon II macro cabinet provides the same functionality as the
SURF in the Horizonmacro cabinet. It also supports additional functionality such as four
branch receive diversity.

For further technical details, see the Horizon II product documentation.

7-10

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Horizon II mini

Horizon II mini
The Horizon II mini platform is a smaller version of Horizon II macro, supporting less capacity,
and hence less backhaul (RTF). The OMC-R software identifies the Horizon II mini from the
cabinet id and provisions a lesser number of carriers for the cabinet.
When configured in a Horizon II mini network (that is, a network of four Horizon II mini
cabinets), the maximum number of carriers supported is limited to 16. This does not apply, if
there is an M-Cell, Horizonmacro, or Horizon II macro cabinet in the network.
The Horizon II mini BSS software recognizes the four PIX alarms at the CTU2 caused by Horizon
II mini hardware and suppresses the four PIX (EAS) alarms. The FRU type is sent to the OMC-R
and can be viewed in the Detailed View of the Horizon II mini BTS cabinet.
The Horizon II mini BTS, unlike the Horizon II macro BTS, has no redundant site controller
(BTP device).
A maximum of two physical radios can be equipped to a Horizon II mini cabinet.
The Horizon II mini BSS software supports the EGPRS (egprsOpt) feature.
For further technical details, see the Horizon II mini product documentation.

68P02901W17-T

7-11
Jan 2010

Overview of adding a BTS

Chapter 7: Configuring a Site

Overview of adding a BTS

Recommended way to add a BTS

The recommended way to add a BTS to an existing BSS is by copying and pasting an existing
BTS as detailed in Copying and pasting a BTS on page 11-6 in Chapter 11 Network Expansion.

NOTE
Refer to Introduction to BSC and BTS sites on page 7-2 for further considerations and
restrictions of the different SITE devices and functions.

Who provides the BTS information

Typically, the system engineer provides the appropriate site parameter inputs necessary to
create or customize a BTS SITE.

Prerequisites to adding a BTS

Before any of the following procedures, the new BTS must have been:

Installed and commissioned.

Connected to the BSS network through E1 links.

In addition, there must be sufficient MSIs equipped at the BSC and intermediate BTSs for the
addition of connections toward the new BTS. This includes sufficient provision for paths, RSLs,
and RTFs between the BSC and the new BTS.

7-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Procedures for adding a BTS

Procedures for adding a BTS

The possible methods for adding a BTS are:

Copying and pasting a BTS on page 11-6 (recommended procedure) detailed in Chapter 11
Network Expansion.

Adding a BTS using a batch rlogin script on page 7-14.

Adding a BTS using the TTY interface - two examples are provided in the following
sections: Adding a BTS using the TTY interface (example 1) on page 7-17 and Adding a
BTS using the TTY interface (example 2) on page 7-21.

Creating a SITE using the OMC-R GUI on page 7-26.

NOTE
When a BTS is to be moved from one BSC to another, the BTS must be powered-down
before disconnection. It can then be connected to the new BSC and powered-up
again. Failure to do so could cause a conflict between the BTS previous site number
(held in RAM) and the same site number in the new BSC database.
These procedures are described in detail in the following sections.
In addition, new paths may be required to be connected to a new SITE; refer to Extending an
existing path to a new site using the TTY interface on page 7-40.

68P02901W17-T

7-13
Jan 2010

Adding a BTS using a batch rlogin script

Chapter 7: Configuring a Site

Adding a BTS using a batch rlogin script

Adding a BTS online using batch rlogin script

The fastest way to add a SITE is using a batch rlogin script.

Using batch templates

To facilitate the addition of sites, some operators may choose to maintain a set of batch templates
which cater for adding different types of site. These templates are scripts that contain all the
necessary commands and parameters (a series of equip, add, change_element and stat_mode
commands) to create a site database. For example, template scripts can be kept for the different
BTS configurations, such as: 1 sector BTS6, 3 sector BTS6, and 1 sector Horizonmicro).
However, the scripts have to be upgraded after each BSS software release load change.
Adding a BTS using the TTY interface (example 1) on page 7-17 provides information on the
commands to be included in the batch script or template.

Assumptions
For brevity, this procedure assumes that:

Sufficient MSIs are equipped at the BSC and intermediate BTSs for connections toward
the BTS being added.

The remote BTS is physically installed and connected to the BSS network through 2.048
Mbit/s links.

Procedure list
The following steps are required to add a remote BTS to a BSS:

Procedure 7-1 Add remote BTS to a BSS

1

Create the script file or template, see Adding a BTS using the TTY
interface (example 1) on page 7-17 for details of the TTY commands
to be included in the script file.

Select the BSS to which the BTS is to be added, see Remotely logging
in to a BSS site from the OMC-R on page 1-39 for further details.
Continued

7-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Beginning a batch session

Procedure 7-1 Add remote BTS to a BSS (Continued)

3

Begin a batch session.

Run the amended file under the batch session to add the site to the
relevant database.

Audit the site and apply any inconsistencies to the OMC-R.

Each of these steps is described in detail in the following subsections.

Beginning a batch session

To begin the batch session:

Procedure 7-2 Begin a batch session

1

From the Rlogin window, click the Batch button.

If templates are used, a chg_level command should be included at the
start followed by the password.

Identify the appropriate and previously written or uploaded

script file for adding a BTS which is available in the
$SYS_CONFIG_BATCH/templates_1500 directory.

Copy this file to the $SYS_CONFIG_BATCH/input directory and modify

its contents accordingly.

Running script file

To run the BTS script file:

Procedure 7-3 Run the BTS script file

68P02901W17-T

Click the Run button to execute the selected BTS script file.

On successful completion, close the Batch window and return to the

Front Panel.

7-15
Jan 2010

Checks to perform after adding a BTS

Chapter 7: Configuring a Site

Checks to perform after adding a BTS

Perform the following checks, after adding a BTS:

Procedure 7-4 Checks after adding a BTS

7-16

If necessary, update the SITE names on the SITE Detailed View.

Verify that the new SITE under the BSC has come into service using,
through rlogin, the TTY command:
state 0 site **

If necessary, unlock the SITE and associated RSLs.

Verify that the raw statistics files are enabled for the BTS.

Wait one statistic interval before verifying that the PM reports are
available for the BTS.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adding a BTS using the TTY interface (example 1)

Adding a BTS using the TTY interface (example 1)

Introduction to adding a BTS using the TTY interface

The network drawing shown in Figure 7-3 are used as the basis for the 2.048 Mbit/s link-related
command parameters in this procedure.

Figure 7-3 Example of adding BTS 2

MSI 16
MMS 0

MSI 0
MMS 0

MSI 17
MMS 0

MSI 1
MMS 0

MSI 0
MMS 1

MSI 0
MMS 0

BTS 1

BSC

MSI 18
MMS 1

MSI 1
MMS 1

BTS 2

MSI 2
MMS 1

MSI 1
MMS 0

ti-GSM-ExampleofaddingBTS2-00793-ai-sw

Procedure list for adding a BTS using the TTY interface

The basic steps for adding a BTS using the TTY interface are:

Procedure 7-5 Add BTS using TTY interface

68P02901W17-T

Select the BSS and change security level, see Remotely logging in to a
BSS site from the OMC-R on page 1-39 for further details.

Equip the new BTS site and all required devices and functions in the
database.

Perform checks to verify that the site is in service, see Checks to

perform after adding a BTS in Adding a BTS using a batch rlogin script
on page 7-14.

7-17
Jan 2010

Equipping BTS devices and functions

Chapter 7: Configuring a Site

Equipping BTS devices and functions

To fully equip a BTS site, equip/create devices and functions such as the following:

The devices: DRI, GPROC, and so on.

Two MSIs.

path.

RSL.

RTF.

Creation order for devices and functions

The order in which devices/functions should be created/equipped is as follows.

Hardware:
SITE.
CAB.
CAGE.
KSW (cage 15 only).
Now use chg_csfp to change CSFP algorithm or flow control values.
GPROC.
BTP.
GCLK (cage 15 only).
MSI (MMS).

Links:
DYNET.
path.
RSL.
Reserving timeslots.

Radio:
Cells (including Short Message Service, Hopping, Surround Cell, Power Budgets,
Enabling Statistics, and so on).
Neighbors.
RTF.
DRI.

7-18

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General procedure for adding a SITE

General procedure for adding a SITE

To equip the new site, its cabinets, cages, devices, and functions, follow these steps:

Procedure 7-6 Equip the new site, devices and functions

1

Add BTS 2 (see Figure 7-3) using the following command:

equip <location> SITE
The system responds by prompting for further information about the
site.

Equip required devices and functions.

Add the two MSIs to BTS 2 using the following command:

equip <location> MSI
The system responds by prompting for further information about the
MSI.

See Technical Description: BSS Command Reference (68P02901W23) for further command,
parameter, and system prompt information.

Adding path devices

To add paths for BTS 2, use the following command:
equip <location> PATH
Refer to: Technical Description: BSS Command Reference (68P02901W23) for comprehensive
command, parameter, and system prompt information.

Adding RSL devices

To add RSL devices:

Procedure 7-7 Add RSL devices

1

Add RSL devices to BTS 2 using the equip command. The path
specified for RSL 0 terminates at the default MSI and MMS. Since
PATH 1 and PATH 2 both terminate at the secondary default position,
either could be entered for RSL 1. Refer to: Technical Description: BSS
Command Reference (68P02901W23) for comprehensive parameter
information.

Repeat Step 1 to add additional RSL devices.

NOTE
RSL devices 0 and 1 must be assigned to the
primary/secondary default slots.

68P02901W17-T

7-19
Jan 2010

Adding RTF functions

Chapter 7: Configuring a Site

Adding RTF functions

To add RTF functions follow these steps:

Procedure 7-8 Add RTF functions

1

Add RTF functions to BTS 2 using the Navigation Tree, or the TTY
interface equip command. Only certain RTF parameters are shown in
the example.
Refer to: Technical Description: BSS Command Reference
(68P02901W23) for comprehensive parameter information.

Repeat Step 1 to add additional RTF functions.

The primary path assignment cannot be changed or deleted.
The secondary path can be omitted, added at a later time (using
add_rtf_path), and deleted (using del_rtf_path).
If a secondary path is later added that is shorter than the primary
path (for example, over a new 2.048 Mbit/s link directly between the
BSC and BTS 2), the secondary path is used for the RTF. The example
shown in Figure 7-4 deletes the PATH 1 assignment and adds a PATH
3 assignment.

Figure 7-4 Path assignment example

BSC

PATH 0

BTS 1
PATH 0

MSI 0
MMS 0

BTS 2
Slot 16 Cage 15

MSI 1
PATH 1

PATH 1

PATH 2

MSI 1
PATH 2 MMS 0 Slot 16 Cage 14

Slot 16 Cage 14

Slot 14 Cage 15

PATH 3
ti-GSM-Pathassignmentexample-00794-ai-sw

7-20

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adding a BTS using the TTY interface (example 2)

Adding a BTS using the TTY interface (example 2)

Equipping a SITE and MSIs using the equip command

The network drawing shown in Figure 7-5 is used as the basis for the E1 link-related command
parameters in this procedure. To equip a SITE and MSIs using the equip command:

Procedure 7-9 Equip a SITE and MSIs

1

Add BTS 3 using the equip command. The example is appropriate for
a Type 1 or Type 2 BSC.

Equip required devices and functions.

Add three MSIs to BTS 3 using the equip command. The physical
locations specified in the command for MSIs 0 and 2 are required for
the default RSL ports.

Figure 7-5 Example of equipping a SITE and MSIs

BSC

MSI 16
MMS 0

MSI 0
MMS 0

MSI 0
MMS 1

MSI 0
MMS 0

MSI 0
MMS 1

MSI 0
MMS 0

MSI 17
MMS 0

MSI 1
MMS 0

MSI 1
MMS 1

MSI 1
MMS 0

MSI 1
MMS 1

MSI 1
MMS 0

MSI 18
MMS 1

MSI 2
MMS 0

MSI 2
MMS 1

MSI 2
MMS 0

MSI 2
MMS 1

MSI 1
MMS 1

MSI 19
MMS 0

MSI 3
MMS 0

BTS 1

MSI 3
MMS 1

BTS 2

BTS 3

MSI 2
MMS 0

ti-GSM-ExampleofequippingaSITEandMSIs-00795-ai-sw

The following is an example input and output for equipping a SITE and MSI devices:
-> equip bsc SITE
Enter the SITE identifier:

Enter the type of BSP or LCF: LCF

Enter the function ID for the LCF: 2
Enter the function ID of the LCF: 3
Enter the RSL rate:

68P02901W17-T

16

7-21
Jan 2010

Equipping path devices using the TTY interface

Chapter 7: Configuring a Site

Does the site use dynamic allocation of terrestrial backing resources:

COMMAND ACCEPTED
-> equip 2 MSI
Enter the device identification for the MSI: 0
Enter the cage number:

15

Enter the slot number:

16

Enter the MSI type:

Enter MMS0 protocol type:

E1

Enter the number of timeslots supported on MMS0:

Enter MMS0 modem setting:

master

Enter MMS1 protocol type:

E1

Enter the number of timeslots supported on MMS1:

Enter MMS1 modem setting:

16

16

master

COMMAND ACCEPTED
-> equip 3 MSI
Enter the device identification for the MSI: 0
Enter the cage number:

15

Enter the slot number:

14

Enter the MSI type:

Enter MMS0 protocol type:

E1

Enter the number of timeslots supported on MMS0:

Enter MMS0 modem setting:

master

Enter MMS1 protocol type:

E1

Enter the number of timeslots supported on MMS1:

Enter MMS1 modem setting:

16

16

master

COMMAND ACCEPTED

Equipping path devices using the TTY interface

The network drawing shown in Figure 7-6 is used as the basis for the path-related command
parameters in this procedure.

7-22

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping path devices using the TTY interface

Figure 7-6 Example of equipping paths

BSC
PATH 0

BTS 1

PATH 0

PATH 0

BTS 3
Slot 16 Cage 15

MSI 1
MMS 0

PATH 1

PATH 1

MSI 0
MMS 0

BTS 2

PATH 1

PATH 2

PATH 2

Slot 14 Cage 15

MSI 1
MMS 1
Slot 14 Cage 15

MSI 2
MMS 0
Slot 16 Cage 14

PATH 3
ti-GSM-Exampleofequippingpaths-00796-ai-sw

To add path devices proceed as follows:

Procedure 7-10 Add path devices

1

Identify paths to be copied using the disp_link_usage command.

Add PATH 0 and PATH 1 for BTS 3 using the copy_path command.
PATH 0 MSI at the terminating BTS is the one equipped for the default
primary RSL position.

Add PATH 2 for BTS 3 using the copy_path command.

Add PATH 3 for BTS 3 using the copy_path command. PATH 3 MSI at
the terminating BTS is the one equipped for the default secondary
RSL position.

NOTE
For the copy_path command, selection of the path to be
copied is arbitrary. For example, any of the BTS 1 paths
could be specified in step 4.

68P02901W17-T

7-23
Jan 2010

Adding RSL devices using equip command

Chapter 7: Configuring a Site

Adding RSL devices using equip command

To add RSL devices proceed as follows:

Procedure 7-11 Add RSL devices

1

Add RSL devices to BTS 3 using the equip command, see below. The
path specified for RSL 0 (primary) terminates at the default MSI
and MMS and that for RSL 1 (secondary) terminates at the standby
default MSI and MMS. Refer to Technical Description: BSS Command
Reference (68P02901W23) for comprehensive parameter information.

Repeat Step 1 to add additional RSL devices.

The following is an example input and output for equipping RSL devices:
-> equip 0 RSL
Enter the 1st device ID for the RSL: 3
Enter the 2nd device ID for the RSL: 0
Enter the unique PATH identifier:

Enter LAPD T200 timer value for this device:

2500

Enter LAPD N200 timer value for this device:

Enter LAPD K value for this device:

COMMAND ACCEPTED
-> equip 0 RSL

Enter the 1st device ID for the RSL: 3

Enter the 2nd device ID for the RSL:
Enter the unique PATH identifier:

COMMAND ACCEPTED

7-24

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adding RTF functions

Adding RTF functions

To add RTF functions proceed as follows:

Procedure 7-12
1

Add RTF functions

Add frequencies to the system by adding RTF functions to BTS 3 using

the navigation tree or the TTY interface equip command as shown
earlier.
Only certain RTF parameters are shown in the example; refer to:
Technical Description: BSS Command Reference (68P02901W23) for
comprehensive parameter information.

NOTE
The primary path assignment cannot be changed or deleted.
The secondary path can be omitted, added at a later time
(add_rtf_path) and deleted (del_rtf_path). If a secondary
path is later added that is shorter than the primary path, the
secondary path is used for the RTF.
2

Repeat Step 1 to add additionally required RTF functions.

Example input and output for equipping an RTF

The following is an example input and output for equipping RTF functions:
-> equip 3 RTF
Enter type of carrier:

BCCH

Enter the 1st and 2nd RTF id:

Enter the 1st and 2nd RTF id:
Enter the primary unique PATH id:

Enter the optional secondary unique PATH id:

Enter the GSM cell assigned to ...

.
.
COMMAND ACCEPTED

Unequipping a SITE using the TTY interface

To unequip a site, use the unequip command, for example:
unequip bsc SITE <location> 0 0

68P02901W17-T

7-25
Jan 2010

Creating a SITE using the OMC-R GUI

Chapter 7: Configuring a Site

Creating a SITE using the OMC-R GUI

Introduction to adding a SITE using the OMC-GUI

SITEs are shown in, and can be created from, the OMC-R GUI Navigation Tree (see Figure 7-7).
SITE Detailed Views allow SITE parameters to be viewed and configured.

Figure 7-7

Navigation Tree showing SITE hierarchy

ti-GSM-NavigationTreeshowingSITEhierarchy-00797-ai-sw

Creating a SITE using the OMC-R GUI

BSC and BTS creation
When creating the first site for a BSS, the OMC-R GUI displays a SITE Detailed View for a BSC
(SITE 0). When creating subsequent sites, the OMC-R GUI displays a SITE Detailed View
for a BTS.

7-26

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

SITE Detailed View fields

Procedure
To create a site using the OMC-R GUI, follow these steps:

Procedure 7-13 Create a site using the OMC-R GUI

1

Navigate to and select the SITE class button in the Navigation Tree
(BSS BSS instance SITE).
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details. The SITE class button changes color.

From the menu bar select Edit Create.

The OMC-R displays the SITE Detailed View form.

Enter all the required information, see SITE Detailed View fields
for details.

Select File Create to create the site.

Select File Close to close the SITE Detailed View form.

SITE Detailed View fields

The following sections list and briefly describe the parameter fields in the SITE Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 7-4 describes the fields in the Identification grouping of the SITE Detailed View.

Table 7-4 SITE Detailed View fields - Identification grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Name

Unique SITE name.

Up to 31
characters
plus the NULL
character.

Mandatory.

BTS Configuration
Type
bts_type

Displayed for a BTS site only.

0 or 1.
Non-Abis,
Type 0 (0).
Non-Abis,
Type 1 (1).
Default is null.

Optional.

Continued

68P02901W17-T

7-27
Jan 2010

SITE Detailed View fields

Chapter 7: Configuring a Site

Table 7-4 SITE Detailed View fields - Identification grouping (Continued)

Brief description

Values

Mandatory or
Optional?

RDN Class

The class identifier used to format the

DN in the OMC. It is also used in the
Alarm Interface between the OMC
and BSS.

Default is SITE.

Optional.

RDN Instance

The instance identifier of the object.

Together with the rdnClass, it
makes up the Relative Distinguished
Name (RDN) of an object. Also see
description inTable 3-1.

Default is 0.

Optional.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the parent BSS name. Click

to display the parent BSS Detailed
View.

Site Generation

The type of hardware contained

by this SITE. Set to M-Cell for a
Horizonmacro or Horizonmacro_ext
site.

0 - 2.
InCell (0), M-Cell
(1), M-Cell-Micro
(2).

Mandatory.

Field name/BSS
parameter name

Additional Information
Use the Additional Information window to input any notes relating to this SITE. Where additional
notes are not required, close this field by clicking the toggle button next to the Additional
Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Reconfiguration Information grouping

Not currently used.

General grouping
Table 7-5 describes the fields in the General grouping of the SITE Detailed View.

Table 7-5

SITE Detailed View fields - General grouping

Field name/BSS
parameter name
LCF managing
this site

Brief description
Only valid for a remote BTS.

Values
0 - 24.
Default is null.

Mandatory or
Optional?
Optional.

Continued

7-28

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 7-5

SITE Detailed View fields

SITE Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

BSP/LCF Flag

Whether a BSP or LCF manages this

site. Only valid for a remote BTS.

BSP (0) or
LCF (1).

Optional.

Carrier Disable
Time

The time to wait in seconds before a

carrier is disabled while the site is in
power-saving mode.

120 - 65535
(seconds).
Default is 120.

Optional.

Carriers Ins Power

Fail

The number of carriers to remain in

service in the event of a main power
failure. Not displayed for SITE 0 (BSC).

0 - 30 (number
of RCUs).
Default is 30.

Optional.

CSFP Algorithm

ANY - Select using Pool Algorithm then

STDBY algorithm (1), POOL - Select
a redundant BSP or BTP (2), POOL Select a pooled GPROC (3), NONE - Do
not configure a CSFP device at this site
(4).

1 - 4. Default
is ANY (1).

Mandatory.

CSFP Flow Value

Controls the amount of BSC-BTS link

bandwidth which the CSFP download
consumes. Only valid in a BTS.

10 - 100 (step
size of 10).
Default is 10.

Optional.

Phase Lock GCLK

Enables phase locking for the GCLK

board. Phase locking means the GCLK
board is synchronized to a clock at an
uplink site.

Enabled (1)
or Disabled
(0). Default is
Disabled (0).

Mandatory.

1 - 255
(in hours).
Default is 24.

Mandatory.

Clock Source Fail

Reset Period
GPROC Timeslots

The number of timeslots to be allocated

to all GPROCs for the TDM highway.

16 or 32.
Default is 16.

Mandatory.

LTA Alarm Range

The alarm range on the allowed

long-term average (LTA) variation.

1 - 255 (no
units). Default
is 7.

Optional.

Number Of Audit
Retries

The number of times CP processes audit

each other with regard to a particular
connection.

0 - 5. Default
is 1.

Mandatory.

Poor Initial
Assignment

Enables or disables the flag which

checks the timing advance on a Random
Access Channel (RACH). Not displayed
for SITE 0 (BSC).

Enabled (1)
or Disabled
(0). Default is
Disabled (0).

Mandatory.

RACH Load Type

The RACH loading calculation method

to be used. Not displayed for SITE 0
(BSC).

0 or 1.
Default is
0 (Motorola
method).

Mandatory.

RF Resource
Indication Period

The handover RF response to indicate

the period of the idle channel
categories. Not displayed for SITE 0
(BSC).

1 - 127
(in SACCH
Multiframes).
Default is 10.

Mandatory.

Continued

68P02901W17-T

7-29
Jan 2010

SITE Detailed View fields

Table 7-5

Chapter 7: Configuring a Site

SITE Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

Mandatory or
Optional?

Brief description

Values

RSL Rate
rsl_rate

Specifies the signaling and control

information rate of the RSL. Only valid
at a BTS.
If the BSS feature 16 kbit/s LAPD RSL
(rsl_rateOpt) is restricted, can only be
set to RATE_64 kbit/s.

Default is
RATE_64 kbit/s
(0).

Optional.

TCH Busy Critical

Threshold

The usage of TCHs, as expressed by

the ratio of the number of active calls
to the maximum number of calls the
SSM can handle (250). Every time the
usage equals or exceeds this threshold,
two access classes are barred. Not
displayed for SITE 0 (BSC).

81 - 100.
Default is 100.

Mandatory.

TCH Busy Norm

Threshold

The usage of TCHs, as expressed by the

ratio of the number of active calls to
the maximum number of calls the SSM
can handle (250). Every time the usage
equals or exceeds this threshold, one
access class are barred. Not displayed
for SITE 0 (BSC).

0 - 100.
Default is 100.

Mandatory.

Wait For
Reselection

The time that the site waits before

selecting a new MMS for clock extract
after an MMS has a reference failure
alarm.

0 - 86400
(in seconds).
Default is 10.

Mandatory.

MMS
Configuration
Type

The type of connection wanted for the

TELCO connection. Not displayed for
SITE 0 (BSC).

0 or 1.
Default is 0.

Mandatory

Timeslot
Allocation Flag

The cept timeslot mapping algorithm

at sites adjacent to a TS_SWITCH.
Grayed-out for SITE 0 (BSC).

0 or 1.
Default is
Existing
timeslot
algorithm (0).

Optional.

Fast GCLK Warm

Up Flag
gclk_qwarm_flag

Whether the GCLK is active after the

normal 30 minute warm up period or
after a 15 minute warm up period.
Grayed-out for SITE 0 (BSC). Only valid
if the Fast GCLK Warm Up feature
(FastWarmGclkOpt) is unrestricted
(Enabled).

Default is
GCLK to warm
up in 30
minutes (0).

Optional.

Phase Lock Retry

Interval

Specifies the time in minutes which

would be used by the FM Sync process
to retry phase locking automatically
after it fails. Grayed-out for SITE 0
(BSC).

0 - 255
(minutes).
Default is 255.

Optional.

Continued

7-30

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 7-5

SITE Detailed View fields

SITE Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

Brief description

Values

Calibrate Enabled
calibrate_flag

Whether the SITE can be calibrated.

Only displayed if the bay level
calibration facility has been enabled.
See Remotely calibrating DRIs on page
9-79 for further details.

Disabled (0) or
Enabled (1).

Configuration
used on last
calibrate

Configuration type used the last time

the SITE was calibrated. Only displayed
if the bay level calibration facility has
been enabled. See Remotely calibrating
DRIs on page 9-79 for further details.

Mandatory or
Optional?
Mandatory.

Optional.

Alarm Information grouping

This grouping contains all the alarm information for the MSI, such as MSI Remote Loss Daily
Alarm Level. See Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for
further details.

SMS Information grouping

This grouping is not displayed for SITE 0 (BSC). Table 7-6 describes the fields in the SMS
Information grouping of the SITE Detailed View.

Table 7-6

SITE Detailed View fields - SMS Information grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

SMS Downlink
Allowed

Enables or disables downlink (mobile

terminated) point to point short
message service.

Disabled (0)
or Enabled
(1). Default
is Disabled (0).

Mandatory.

SMS TCH Channel

The logical radio channel used for the

short message service (SMS) transfer
in the event of a call being present on a
traffic channel.

0 - 2. Default is
SACCH always
used (2).

Mandatory.

SMS Uplink
Allowed

Enables or disables uplink (mobile

originated) point to point short message
service.

Disabled (0)
or Enabled
(1). Default
is Disabled (0).

Mandatory.

CBC to CBS
Outage Counter
cbs_outage_cntr

Determines the delay between an

outage occurring and the CBS halting
transmission of the CBC originated
messages.

0 - 255.
Default is 0.

Optional.

68P02901W17-T

7-31
Jan 2010

SITE Detailed View fields

Chapter 7: Configuring a Site

CRM Timers grouping

This grouping is not displayed for SITE 0 (BSC). This grouping contains all the CRM timers, such
as Carrier Free Immediately Timer. See Maintenance Information: BSS Timers (68P02901W58)
for further details.

RRSM Timers grouping

This grouping is not displayed for SITE 0 (BSC). This grouping contains all the RRSM timers,
such as Cifer Mode Complete from an MS Timer. See Maintenance Information: BSS Timers
(68P02901W58) for further details.

RSS Timers grouping

This grouping is not displayed for SITE 0 (BSC). This grouping contains all the RSS timers, such
as TM BCCH Information Timer. See Maintenance Information: BSS Timers (68P02901W58) for
further details.

Circuit Error Rate Monitor grouping

This grouping is not displayed for SITE 0 (BSC). This grouping contains all the CERM timers,
such as Initial Sync Timer (msec). See Maintenance Information: BSS Timers (68P02901W58)
for further details. Also see Enhanced Circuit Error Rate Monitor (ECERM) on page 2-70.

HDSL Information grouping

This grouping contains all the HDSL alarm information, such as MSI SNR Hourly Alarm Level
(in 0.5 dB units). See Maintenance Information: Alarm Handling at the OMC-R (68P02901W26)
for further details. Some of these fields are only used if the Integrated M-Cell HDSL Feature (
hdslOpt) is unrestricted at the BSS.

GPRS grouping
This grouping is not displayed for SITE 0 (BSC). Table 7-7 describes the fields in the GPRS
grouping of the SITE Detailed View.

Table 7-7 SITE Detailed View fields - GPRS grouping

7-32

Field name

Brief description

Values

Static Sync Timer

Specifies the maximum amount of time

the channel coder has to transition
from initial time alignment to static
time alignment.

1 - 65535 (ms).
Default is 1200.

Percentage of RSL
Reserved for CS

See Enhanced Scheduling on page

2-146 for details.

Mandatory or
Optional?
Optional.

Optional.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

SITE Detailed View fields

Map Information grouping

Standard map information fields, see Table 4-15 for details.

68P02901W17-T

7-33
Jan 2010

Modifying SITE parameters

Chapter 7: Configuring a Site

Modifying SITE parameters

Methods for modifying SITE parameters

The following methods can be used to modify SITE parameters:

Using the OMC-R GUI SITE Detailed View, see Modifying a network object using the
OMC-R GUI on page 1-34 for further details.

chg_element command.

modify_value command.

Using the chg_element command

If only one or two parameter changes are to be made, follow these steps:

Procedure 7-14

Change element parameters

Remotely log in to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Use the chg_element command and the appropriate parameter.

Parameter values should be obtained from a system engineer.
The following example activates the BTS type to type 1:
chg_element bts_type 1 3
The following example assigns 16 TDM timeslots to GPROC:
chg_element gproc_slots 16 3

A complete description of the chg_element command and the device/function parameters

affected by it can be found in: Technical Description: BSS Command Reference (68P02901W23).

Using the modify_value command

Some device/function parameters for a site can only be changed using the modify_value
command from the TTY interface (or the Modify Value option from the Configuration menu of
the MML Command Constructor window of the FORMs interface).

7-34

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Using the modify_value command

To use the modify_value command, follow these steps:

Procedure 7-15 Use modify_value command

1

Remotely log in to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Enter the modify_value command with the parameter to be defined.

For example:
To change the maximum number of DRIs on DHP 4 2 0 at site 7 to
5, use the following:
modify_value 7 max_dris 5 dhp 4 2 0
To change the time period to wait for acknowledgment of a transmitted
frame for the RSL device at site 1 to 2500 ms, use the following:
modify_value 1 lapd_t200_timer 2500 rsl 1 0

A complete description of the modify_value command and the device/function parameters

affected by it can be found in: Technical Description: BSS Command Reference (68P02901W23).

68P02901W17-T

7-35
Jan 2010

Equipping cabinets and cages at a remote BTS

Chapter 7: Configuring a Site

Equipping cabinets and cages at a remote BTS

Overview of equipping cabinets and cages at a remote BTS

This section provides an example of how to equip a cabinet and cage at a remote BTS site
(InCell). Equipping cabinets and cages can be carried out either in SYSGEN mode or outside
of SYSGEN mode with the site locked. It requires the use of the equip command in the TTY
interface.

NOTE
The BTS examples shown in this section are for demonstration purposes only.
Parameters are system specific and will vary.
Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the BSS commands.

Cabinet and cage numbers

When equipping cabinets the numbers 0 to 15 may be assigned. When equipping cages at a
BTS, the numbers 2 to 15 may be assigned with the first equipped cage assigned number 15, the
second cage assigned number 14 and so on.

Scenario
In this example, two remote BTS cabinets are equipped. The following information is available:

The remote BTS cabinets (0, 1) are equipped at SITE 2 BSS SWest BSIC 26.

The BTS cabinet numbers are 0 and 1.

Each cabinet is equipped with a cage:

Cabinet 0 - cage 15.
Cabinet 1 - cage 14.

7-36

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BTS equipment

BTS equipment
Cages 15 and 14 are equipped with the following required and optional devices:

EAS (half size PIX module).

KSW A and KSW B (cage 15 only).

MSI.

GCLK A and GCLK B (cage 15 only).

DRI.

GPROC.

Additional equipment
Although there is no equip procedure for the following devices, they must be physically inserted
when more than one cage is equipped:

CLKX (half size modules, cage 15 only).

KSWX (half size modules).

The Bus Terminator Card (BTC) is always provided in a BTS cage.

Furthermore, although there is no equip procedure for the DRIX half size modules, they must
be physically inserted to provide the interface between the DRI and RCU.

Overall procedure list

The following steps are required when equipping cabinets and cages at a remote BTS:

Procedure 7-16 Equipping cabinets and cages

1

Select BSS site and change to security level 2.

Equip the remote BTS cabinets. Refer to Equipping a remote BTS

cabinet using the TTY interface on page 7-37 for further details.

Equip the BTS cages. Refer to Equipping a BTS cage using the TTY
interface on page 7-38 for further details.

Add any new cells.

Equipping a remote BTS cabinet using the TTY interface

The following provides example input and output for equipping remote BTS cabinets:
-> equip 1 CAB

68P02901W17-T

7-37
Jan 2010

Equipping a BTS cage using the TTY interface

Enter the CABINET identifier:

Chapter 7: Configuring a Site

0
1

Enter the cabinet type number:

COMMAND ACCEPTED
-> equip 1 CAB
Enter the CABINET identifier:
Enter the cabinet type number:

1
1

COMMAND ACCEPTED

Equipping a BTS cage using the TTY interface

At a BTS site, cage numbers are unique, and can range from 2 - 15. The first equipped cage
is assigned number 15, and the second number 14. The following provides an example for
equipping the BTSs using the example data:
-> equip 1 CAGE
Enter the identifier for the cage:

15
0

Enter the KSW pair that manages the cage:

Enter the KSWX connecting cage to KSW for TDM 0:

Enter the KSWX connecting cage to KSW for TDM 1:

Enter cabinet to which the cage belongs:

Is an IAS connected?:

no

COMMAND ACCEPTED
-> equip 1 CAGE
Enter the identifier for the cage:

14
0

Enter the KSW pair that manages the cage:

Enter the KSWX connecting cage to KSW for TDM 0:

Enter the KSWX connecting cage to KSW for TDM 1:

Enter cabinet to which the cage belongs:

Is an IAS connected?:

no

COMMAND ACCEPTED

7-38

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting and unequipping TCU/CTU cabinets

Deleting and unequipping TCU/CTU cabinets

Introduction to deleting and unequipping TCU/CTU cabinets

Extension cabinets of types: TCU_2, TCU_6, and Horizonmacro extension at M-Cell and
Horizonmacro sites can be unequipped without having to unequip the site first.

Prerequisites for deleting TCU/CTU cabinet types

To unequip cabinet types TCU_2, TCU_6, and Horizonmacro extension at an M-Cell or
Horizonmacro site, ensure:

The cabinet is locked.

DRIs and EASs are not equipped to the cabinet.

Deleting TCU/CTU cabinet types using the OMC-R GUI

To delete cabinet types: TCU_2, TCU_6, and Horizonmacro extension at an M-Cell or
Horizonmacro sites using the OMC-R GUI, see Deleting a network object using the OMC-R
GUI on page 1-37.

Unequipping TCU/CTU cabinet types using the TTY interface

To unequip cabinet types TCU_2, TCU_6, and Horizonmacro extension at M-Cell and
Horizonmacro sites using the TTY interface, use the unequip command. For example:
unequip 50 cab 1 0 0
See Technical Description: BSS Command Reference (68P02901W23) for complete information
on the BSS commands.

68P02901W17-T

7-39
Jan 2010

Extending an existing path to a new site using the TTY interface

Chapter 7: Configuring a Site

Extending an existing path to a new site using the TTY

interface

Introduction to path extension

To extend an existing path to a new site, use:

Configuring a path using Path Configure menu option on page 11-73 in Chapter 11
Network Expansion.

copy_path command, as detailed in this section.

Prerequisites to extending a path to new BTS

Before extending an existing path to a new site, ensure that:

Sufficient MSIs are available at the BSC and intermediate BTSs for connections toward
the BTS being added.

The remote BTS is physically installed and connected to the BSS network through 2 Mbit/s
links.

Extending a path to new site using copy_path

The copy and extend a path, proceed as follows:

Procedure 7-17 Extend a path to a new SITE

1

Remotely log in, select the BSS site and change to security level 2, see
Remotely logging in to a BSS site from the OMC-R on page 1-39.

Enter the command:

copy_path
The SITE responds with prompts for further information.
See Technical Description: BSS Command Reference (68P02901W23)
for further details.

At the prompts, enter the appropriate configuration information, after

which a copied path exists.
Continued

7-40

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Example of equipping path device using copy_path command

Procedure 7-17 Extend a path to a new SITE (Continued)

4

The new path can now be extended one site further down the branch if
necessary.

A new branch can be started (a fork) by recopying the same path and
extending to a different BTS, as shown in Figure 7-8 below.

NOTE
Install the physical sites and 2 Mbit/s links first. Enter them
in the CM database, to allow the procedure to be successful.

Figure 7-8 Example of path connections

Upstream
MSI & MMS

[10]
BSC

[20]

[1 1 ]

BTS 1
[30]

BTS 2
[11]

BTS 3
[20]

BSC
MSI & MMS

[10]

Downstream
MSI & MMS
BTS 4

Downstream
MSI & MMS

[30]
Upstream
MSI & MMS
ti-GSM-Exampleofpathconnections-00798-ai-sw

Example of equipping path device using copy_path command

The following is an example of equipping a path device using the copy_path command (bold
text shows typical user responses):
--> copy_path
Enter terminating site id to be copied:
Enter unique PATH id to be copied:
Enter NEW terminating site id:

Enter downstream MSI id:

Enter downstream MMS id:

68P02901W17-T

Enter NEW unique PATH id:

Enter upstream MSI id:

7-41
Jan 2010

Example of equipping path device using copy_path command

Enter upstream MMS id:

Chapter 7: Configuring a Site

COMMAND ACCEPTED
--> copy_path
Enter terminating site id to be copied:
Enter unique PATH id to be copied:
Enter NEW terminating site id:

Enter downstream MSI id:

Enter downstream MMS id:

0
3

Enter upstream MMS id:

Enter NEW unique PATH id:

Enter upstream MSI id:

COMMAND ACCEPTED
Refer to Technical Description: BSS Command Reference (68P02901W23) for complete
information on the copy_path command.

7-42

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GCLK synchronization

GCLK synchronization

Introduction to GCLK synchronization

Generic CLocK (GCLK) synchronization enables any site to be configured so that it can
synchronize its GCLK to a known good clock source in an uplink site. This feature minimizes
frame slips and prevents the output frequency drifting at the ageing rate of the GCLK oscillator.
This reduces the on-site calibrations of GCLKs.

NOTE
Throughout this section the term GCLK refers either to the GCLK board in InCell sites
or the GCLK part of the MCU for M-Cell sites and MCUF for Horizonmacro. Any
specific differences are detailed where appropriate.
To create a GCLK, see Configuring a GCLK device on page 9-113.

Description of GCLK synchronization

A known good clock (for example, the MSC clock) is defined as the master clock source. This
clock requires a frequency accuracy of at least 0.01 ppm, when wander and jitter have been
removed, and having no breaks greater than 80s.
It is possible to synchronize the RXCDR to the MSC, synchronize the BSCs to the RXCDR,
synchronize the BTSs to the BSC, and so on, until the network is synchronized to the one known
good clock source. The site GCLK can also run at a set frequency (unsynchronized). In this case,
the output frequency is held at a predefined value.
The feature works in networks consisting of sites in star, daisy chain, and loop topologies and
containing all builds of GCLK hardware. Sites within an NE are configured independently of
each other. It is possible, for example, to have some sites using, and some not using, GCLK
synchronization within the same NE. The GCLK synchronization feature does not affect the
configuration limits of the sites or the NEs.

Effect of the number of GCLKs per site

Single GCLK site
For a single GCLK site, it is not possible for the operator to perform the device management
lock operation on the GCLK board, as this takes the site out of service.

68P02901W17-T

7-43
Jan 2010

Configuration restrictions

Chapter 7: Configuring a Site

Two GCLK site

In a two GCLK system, one GCLK operates as a master and generates the reference clock for the
site. The second GCLK operates as a slave and takes the clocks from the master and distributes
them to the internal redundant bus. Upon failure of the master, a swap occurs.
If there is a hardware failure of the master GCLK, then the slave GCLK takes over as the
master regardless of its mode of operation at the time. If the master is phase locking when it
fails, then a site reset can occur.
The feature is supported in a multi-cage site where clock extension is used. The clock is
distributed through equal length fibers to all cages to ensure that clock timing is identical
on all the BSU backplanes.

Configuration restrictions
The following restrictions apply:

An RXCDR or BSC is not allowed to synchronize to an MMS which is connected to a lower

order site. This restriction does not apply to a BTS.

A GCLK in a BTS cannot synchronize to an MMS if the synchronization path does not lead
directly or indirectly (through the path configuration) to a BSC.

An MMS of non-zero priority (mms_priority database parameter greater than zero) must
be specified as the MMS source.

Only one site can synchronize to a single MMS.

Commands used for GCLK synchronization

Table 7-8 shows the BSS commands used in support of GCLK synchronization. See Table 7-9
for parameter descriptions.

Table 7-8 BSS commands for GCLK synchronization

Command

Description

chg_element

Used to modify the settings of the following parameters:

phase_lock_gclk, wait_for_reselection, clk_src_fail_reset_period,
lta_alarm_range.

disp_element

Used to display the settings of the following

parameters:phase_lock_gclk, wait_for_reselection,
clk_src_fail_reset_period, lta_alarm_range.

modify_value

Used to modify the settings of the following

parameters:mms_priority, phase_lock_duration.

disp_equipment

Used to display the time necessary to achieve priority rating and phase
lock for an MMS. Used with the following parameters:mms_priority,
phase_lock_duration.
Continued

7-44

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Database parameters used for GCLK synchronization

Table 7-8 BSS commands for GCLK synchronization (Continued)

Description

Command
clear_gclk_avgs

Clears the stored LTA values held for a specified GCLK. Must be
performed when the GCLK interface is changed or recalibrated, if the
uplink site does not provide a stable source.

reattempt_pl

Causes the GCLK to reattempt phase lock. It is only valid if the GCLK
has previously failed to phase lock.

disp_gclk_cal

Checks, reads, and displays the contents of the site clock frequency
register when the GCLK is in phase lock mode. If the clock is not
in phase lock mode or there is an error on reading the register, a
message is displayed stating that the GCLK is not phased locked. Can
be used to display the clock frequency value at any time. It can also
be used as a diagnostic tool if there is a problem with the LTA or clock
frequency at a site. This command is only supported for InCell sites.

state

Displays the status of the indicated device. It is updated to display

which MMS is currently selected for synchronization.

gclk_cal_mode

Informs the sync function and MCU software that a clock calibration
is to be performed. May only be executed at the M-Cell and Horizon
BTSs where the calibration is being carried out. The MCU is
suspended until the calibration is completed. Only supported for
M-Cell and Horizon sites.

disp_gclk_avgs

Displays the stored LTA values and other associated values held for a
specific GCLK. These values provide a view of the aging of the GCLK.
Only supported for InCell sites.

Database parameters used for GCLK synchronization

Table 7-9 shows the BSS database parameters used in support of GCLK synchronization.

Table 7-9

BSS parameters for GCLK synchronization

BSS parameter

Description

chg_element

Enables or disables phase locking at a site. If this flag is set to 0 then

the site does not attempt phase lock at any time. If set to 1, the site
attempts to phase lock. If the flag is set to 1 and the user updates it to
zero, then the GCLK sets frequency mode. The default setting is 0.

lta_alarm_range

Updates the alarm range on the allowed LTA variation. During every
LTA polling period, the stored LTA values are checked by comparing
the stored LTA values with the newly calculated LTA. If 25% of the
stored LTA values vary (either positively or negatively) from the newly
calculated LTA by more than the allowed LTA variation, an alarm is
raised to alert the operator to potential problems/ alterations in the
system. For example, the GCLK is phase locked to a different clock
source; the uplink site is unstable. It can be set to a value of 1 to 255.
The default value is 7 to allow for day to day temperature variations.
This parameter is invalid for M-CELL sites.
Continued

68P02901W17-T

7-45
Jan 2010

GCLK modes of operation

Chapter 7: Configuring a Site

Table 7-9 BSS parameters for GCLK synchronization (Continued)

Description

BSS parameter
wait_for_
reselection

Controls the time that the system waits before selecting an MMS
for clock extraction, after a GCLK has had a GCLK reference failure
alarm. If the MMS providing the clock extraction is INS after the time
period has expired, it is left as the clock extraction source. A default
value of 10 seconds is used. This value is available on equipage of the
site, but is overwritten by an entry the user makes. The timer can
be set to a value of 0 - 255 seconds, where 0 indicates that there is
no wait period.

clk_src_fail_
reset_period

Changes the value of the clk_src_fail_reset_period. The reset period

is used to delimit the time for which an OOS count is held. At the end
of each reset period, the OOS count is reset to zero and the count
begins again. It can be set to a value between 1 to 255 hours. The
default value is 24 hours.

mms_priority

Changes the priority rating for an MMS. The priority rating

determines its possible use as a reference source to which the GCLK
will phase lock. The MMS with the highest rating is initially used as
the source for the incoming reference clock. The parameter can be
set to a value in the range 0 - 255. The default setting is 0.

phase_lock_
duration

Updates the value of the phase_lock_duration. The GCLK/MCU

(GCLK/MCUF in Horizon sites) achieves the locked state when
its frequency equals the long-term frequency of the E1 line for a
specified period of time and is stable to within $0.05 ppm. For M-Cell
and Horizon sites this time can be configured using this parameter.
For InCell sites, the value of this parameter is added onto the time
duration determined by the GCLK revision level. The parameter can
be set to a value between 0 and 3600 seconds. The default value is
0 seconds for InCell sites and 1500 seconds for M-Cell and Horizon
sites.
For InCell sites, it is recommended that the value of this parameter
is set to 0.

GCLK modes of operation

A GCLK can be used in the following modes:

7-46

Free Run.

Set Frequency.

Closed Loop.

Hold Frequency.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Controlling GCLK synchronization using the TTY interface

GCLKs are used in either Closed Loop or Set Frequency mode. There are short periods of time
when the GCLK hardware puts the GCLK into Hold Frequency and Free Run. The Closed
Loop mode is the mode which achieves GCLK synchronization. Within this mode, there are
two sub-modes:

Acquiring phase locked state.

Phase locked state.

Controlling GCLK synchronization using the TTY interface

To control GCLK synchronization, proceed as follows:

Procedure 7-18 Synchronize the GCLK using TTY interface

1

Remotely log in to a BSS and change to security level 2, see Remotely

logging in to a BSS site from the OMC-R on page 1-39.

For each required location, there are some commands available to

display the current setting and to perform GCLK synchronization
procedures. Examples are described in the following sub section.

NOTE
If an attempt is made to enable the GCLK synchronization
feature before an MMS priority has been assigned, a warning
alarm is displayed. This has no effect on the operation of
the feature as it is enabled once an MMS priority is set and
the alarm clears.

Examples of GCLK commands

The following are examples of displaying current settings and performing GCLK synchronization
procedures.
Refer to Technical Description: BSS Command Reference (68P02901W23) for complete
information on the commands and parameters described in this section.

To prioritize the order in which the MMSs of a site are configured as

reference clock sources
For example, the following command sets a priority rating for an MMS to value 2:
modify_value bsc mms_priority 2 mms 0 0
The following example sets the priority to zero and MMS is providing clock extraction:
modify_value bsc mms_priority 0 mms 0 0
MMS [0,0,0] is currently providing clock extraction.
You will deselect MMS {0,0,0] for clock extraction.
Are you sure? (y = yes, n = no).

68P02901W17-T

7-47
Jan 2010

Examples of GCLK commands

Chapter 7: Configuring a Site

To update the value of the phase_lock_duration

For example:
modify_value bsc phase_lock_duration 0 mms 0 0

To enable/disable the GCLK synchronization feature

For example, the following command disables the feature:
chg_element phase_lock_gclk 0 0

To display the phase_lock_gclk value at a site

For example:
disp_element phase_lock_gclk bsc

To change the value of the wait_for_reselection period

For example, to change to 50 seconds at BSC:
chg_element wait_for_reselection 50 0

To display the wait_for_reselection period

For example:
disp_element wait_for_reselection bsc

To change the value of the clk_src_fail_reset_period

For example, to change to 24 hours at BSC:
chg_element clk_src_fail_reset_period 24 0

To display the value of the clk_src_fail_reset_period

For example:
disp_element clk_src_fail_reset_period bsc

To update the alarm range on the allowed LTA variation

For example, to update range to 10 at BTS 1:
chg_element lta_alarm_range 10 1

To display the alarm range on the allowed LTA variation

For example:
disp_element lta_alarm_range 0

7-48

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Examples of GCLK commands

To display the status of each MMS and its priority rating

For example:
disp_equipment bsc mms 0 0
MSI identifier: 0
First MMS identifier for this device: 0
The N-bit value for this device id[nbit]: 1
The BER OOS monitor period for this device is[ber_oos_mon_period]: 1
The BER restoral monitor period for this device is{ber_restoral_mon_period]: 6000
The Priority rating is [mms_priority]: 0
The Lock Duration for this device (in seconds) is [phase_lock_duration]: 3

To reset LTA to default LTA

For example, to Clear the LTA values for GCLK1 at the BSC for a site:
clear_gclk_avgs 0

To re-attempt phase lock if the phase lock has previously failed

Example 1: Command executed when GCLK 0 is in the FAILED_PHASE_LOCK state:
reattempt_pl bsc 0
Example 2: Command executed when GCLK 0 is in the FAILED_PHASE_LOCK state, but
synchronization is turned off, or an MMS is not providing clock source:
reattempt_pl bsc 0
COMMAND ACCEPTED : GCLK reason reset but system config blocks phase lock
Example 3: Command executed when GCLK 0 is not in the FAILED_PHASE_LOCK state:
reattempt_pl bsc 0
COMMAND REJECTED - GCLK reason does not equal FAILED_PHASE_LOCK

To display the current clock frequency value

Example 1: Request the clock frequency register value when GCLK 0 is not phase locked:
disp_gclk_cal 0 0
SITE 0, GCLK 0 0 0 not in phase lock.
Example 2: Request the clock frequency register value when GCLK 0 is phase locked:
disp_gclk_cal 0 0
SITE 0, GCLK 0 0 0 Clock frequency register value = XX.

68P02901W17-T

7-49
Jan 2010

Examples of GCLK commands

Chapter 7: Configuring a Site

To display the LTA history

Example 1: Display the LTA values for GCLK 1 at site 0:
disp_gclk_avgs 0 1
The GCLK 1 0 0 Frequency Reg values for site 0 are:
80 80 80 80 81 80
Long term average = 80
Example 2: If the GCLK has never been phase locked, then the default LTA is displayed:
disp_gclk_avgs 0 1
The GCLK 1 0 0 Frequency Reg values for site 0 are:
80
Long term average = 80

To display the status of the GCLK device

For example, to display status of GCLK 1 at BSC:
state 0 gclk 1
STATUS INFORMATION:
DEVICE: GCLK 0 0 0
Administration state: unlocked
Operational state: busy
Reason code: NO REASON
Time of last transition:
Related Device/Function: None
Assigned to:
Config Tag (hex)
Tag Site
END OF STATUS REPORT.

7-50

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Examples of GCLK commands

To begin GCLK calibration mode at the local site

NOTE
This command is not allowed from remote login, and is ONLY allowed at M-Cell and
Horizon sites.
Use the command:
gclk_cal_mode
The system responds with the following:
Site <local site number> starting GCLK CALIBRATION MODE. If this is a single MCU
site, the site will be down until calibration is complete. If this is a two MCU
site, the site will be down until the redundant takes over.
(Are you sure (y = yes, n = no)?
If replying with anything other than y, the command is aborted. If replying y, the GCLK begins
the calibration mode. No call processing can occur which involves this GCLK during calibration
mode. The GCLK is reset when calibration is complete.

68P02901W17-T

7-51
Jan 2010

Checking GCLK synchronization for a site

Chapter 7: Configuring a Site

Checking GCLK synchronization for a site

Introduction to GCLK synchronization

The purpose of checking GCLK synchronization is to:

Check that GCLK synchronization has been deployed.

Check performance, in keeping a site in synchronization with the network.

Checking GCLK at a single SITE using the TTY interface

Use the following commands to check the GCLK deployment at a SITE:
disp_eq <site num> gclk * * full
state <site num> gclk * *

Checking GCLK at a single site using the OMC-R GUI

Use the Contained Devices form in the OMC-R GUI to check the GCLK synchronization. OMC-R
Online Help, Network Operations describes the Contained Devices form.

Multiple GCLK SITE checks using scripting and TTY interface

UNIX shell scripting can be combined with TTY commands to check multiple SITEs for GCLK
synchronization. The output can be logged to a file for further analysis or parsing.
An example script is shown, which checks the GCLK synchronization configuration and status
for all BSCs/RXCDRs and sites under the OMC-R. The script operates on the basis that BSS
loads are correctly named (for example, BSGSM) during load install.
Example script: GCLK sync configuration and status for all NEs and sites:
#!/bin/ksh
# Script to check the GCLK version on all BSCs/RXCDRs and sites under this OMC
# Written by Motorola Field Engineer on 19/11/98
# Loop through all BSCs first
bscs = grep BSGSME /usr/omc/config/global/NE.MAP| awk '{print $2}'
for i in echo $bscs
do

7-52

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Multiple GCLK SITE checks using scripting and TTY interface

bsc_num = grep $i /usr/omc/config/global/NE.MAP|awk '{print $4}'

site_nums = grep SITE 31 $bsc_num /usr/omc/config/global/SITE.MAP
|awk ' { print $5}' |cut -c9-10
# setup batch_rlogin command file for all sites
for j in echo $site_nums
do
echo disp_eq $j gclk * * full >>bsc_cmd.file
echo state $j gclk * * >>bsc_cmd.file
done
echo BSCname $i >>bsc_sync.log
batch_rlogin $i <bsc_cmd.file >>bsc_sync.log
sleep 15
rm bsc_cmd.file
done
# Loop through all RXCDRs second
xcdrs = grep XRGSME /usr/omc/config/global/NE.MAP| awk '{print $2}'
for i in echo $xcdrs
do
echo disp_eq 0 gclk * * full >>bsc_cmd.file
echo state $j gclk * * >>bsc_cmd.file
echo RXCDRname $i >>bsc_sync.log
batch_rlogin $i <bsc_cmd.file >>bsc_sync.log
sleep 15
rm bsc_cmd.file
done
phase_locked_gclks = grep -i phase locked bsc_sync.log|wc -l
echo Count of phase locked GCLKs = $phase_locked_gclks >>bsc_sync.log
failed_locked_gclks = grep -i failed phase lock bsc_sync.log|wc -l
echo Count of failed phase locked GCLKs = $failed_locked_gclks \ >>bsc_sync.log
set_freq_gclks = grep -i Set Freq. Mode bsc_sync.log|wc -l
echo Count of set frequency mode GCLKs = $set_freq_gclks >>bsc_sync.log
fine_tune_gclks = grep -i Fine Tune Mode bsc_sync.log|wc -l
echo Count of fine tune mode GCLKs = $fine_tune_gclks >>bsc_sync.log
locking_gclks = grep -i phase locking bsc_sync.log|wc -l
echo Count of phase locking GCLKs = $locking_gclks >>bsc_sync.log
fast_tune_gclks = grep -i Fine Tune Mode bsc_sync.log|wc -l
echo Count of fast tune mode GCLKs = $fast_tune_gclks >>bsc_sync.log
hvn_gclks = grep -i hvn = bsc_sync.log|wc -l
echo Count of Incell GCLKs = $hvn_gclks >>bsc_sync.log
mcell_gclks = grep -i MCU bsc_sync.log|wc -l
echo Count of M-Cell GCLKs = $mcell_gclks >>bsc_sync.log
mcell_micro_gclks = grep -i MCUm bsc_sync.log|wc -l

68P02901W17-T

7-53
Jan 2010

Multiple GCLK SITE checks using scripting and TTY interface

Chapter 7: Configuring a Site

echo Count of M-Cell Micro GCLKs = $mcell_micro_gclks >>bsc_sync.log

mcell_arena_gclks = grep -i Arena (MCU) bsc_sync.log|wc -l
echo Count of M-Cell Arena GCLKs = $mcell_arena_gclks
>>bsc_sync.log
echo Log file is in $PWD/bsc_sync.log

7-54

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Barring calls at a site using the TTY interface

Barring calls at a site using the TTY interface

Barring calls at a site using the TTY interface

To bar calls and divert all traffic from cells at the site by shutting down all DRIs and locking
the site, follow these steps:

Procedure 7-19 Bar calls at a site using TTY interface

1

Remotely log in to a BSS and change to security level 2, see Remotely

logging in to a BSS site from the OMC-R on page 1-39.

Determine the DRI equipage at the BTS by entering:

disp_equipment <location>

Shut down the DRI by entering:

shutdown_device <location> DRI <1st DRI identifier>
<2nd DRI identifier> <3rd DRI identifier> <seconds>

NOTE
Entering 60 in the seconds field puts the DRI in the locked
state after one minute.
4

Repeat Step 2 to shut down all DRIs at the BTS.

Lock the site by entering:

lock_device 0 SITE <1st device id>

Additional information
Refer to Technical Description: BSS Command Reference (68P02901W23) for complete
information on the commands and parameters described in this section.
To bar calls to a cell, see Barring calls at a cell on page 8-239.

68P02901W17-T

7-55
Jan 2010

Checking the hardware deployed at each site

Chapter 7: Configuring a Site

Checking the hardware deployed at each site

Overview to site hardware checking

The following SITE checking procedures are detailed in this section:

Checking a single site using the TTY interface.

Checking a single site using the OMC-R GUI.

Checking multiple sites using scripting and TTY interface.

Checking a single site or NE using cmutil.

Checking a Device Type in the network using cmutil.

Checking a single site using the TTY interface

Use disp_equipment command to display all of the equipment at a site. The output is a table
which includes kit and serial numbers.

Checking a single site using the OMC-R GUI

Use the Contained Devices form in the OMC-R GUI to check the status of hardware in the
network. OMC-R Online Help, Network Operations describes the Contained Devices form.

Checking multiple sites using scripting and TTY interface

UNIX shell scripting can be combined with TTY commands to check multiple sites. The output
can be logged to a file for further analysis or parsing.
The script in this example checks the equipment on all sites under the OMC-R and logs it to a file.

7-56

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking a single site, PCU, or NE using cmutil

NOTE
The script operates on the basis that BSS loads are correctly named (for example,
BSGSM) during load install.
#!/bin/ksh
# Script to check the equipment on all sites under this OMC
# Written by Motorola Field Engineer on 17/11/98
bscs = grep BSGSM /usr/omc/config/global/NE.MAP| awk '{print $2}'
for i in echo $bscs
do
bsc_num = grep $i /usr/omc/config/global/NE.MAP|awk '{print $4}'
site_nums =grep SITE 31 $bsc_num /usr/omc/config/global/SITE.MAP|awk
' { print $5}' |cut -c9-10 |grep -v 00
for j in echo $site_nums
do
echo disp_eq $j full >>bsc_cmd.file
done
echo bscname $i >>hardware_check.log
batch_rlogin $i <bsc_cmd.file >>hardware_check.log
sleep 10
rm bsc_cmd.file
done
echo Log file is in $PWD/hardware_check.log.

Checking a single site, PCU, or NE using cmutil

To check a single site, PCU or NE using cmutil, see Chapter 15 cmutil.

Further analysis of extracted MIB data

The file extracted through cmutil contains all the MIB data for the BSS/SITE. This data can
then be analyzed or further parsed.

68P02901W17-T

7-57
Jan 2010

Checking a device type in the network using cmutil

Chapter 7: Configuring a Site

Examples of analysis or parsing of MIB data

The following shows how to extract DRI only objects:
awk '/DRI /, /}/' bss.op > /tmp/bss_dri_strip
The following shows how to count the number of DRI only objects:
grep rdnInstance /tmp/bss_dri_strip |wc -l
The following shows how to extract SITE only objects from the BSS op file:
awk '/SITE /, /}/' bss.op > /tmp/bss_site_tst
The following shows how to count the number of SITE only objects:
grep rdnInstance /tmp/bss_site_tst | wc -l

Checking a device type in the network using cmutil

To extract all objects of specific type from the MIB using cmutil, see Chapter 15 cmutil.
The file extracted through cmutil contains all the MIB data for the device. This data can then
be analyzed or further parsed.

Examples of analysis or parsing of device type data

The following shows how to count the number of DRI only objects:
grep rdnInstance dri_all.op | wc -l

7-58

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking key site parameters

Checking key site parameters

Overview of key site parameter checking

After a BSS download, or after adding cell capacity online, DRIs/RTFs in a site should come into
service. If the DRIs/RTFs do not come into service, verify the following parameters to check
that they are appropriate to the site configuration required:

tru_id setting.

max_dris setting per GPROC.

antenna_select number.

These parameters are explained in the following sections. Refer to: Technical Description: BSS
Command Reference (68P02901W23) for full details of commands and parameters.

tru_id (TopCell SITE)

Verify that the DRI tru_id parameter setting in the database matches the settings of the site.
The tru_id is used to identify up to six TRUs (TopCell Radio Units) in a TopCell site. This
attribute is valid only if dri_type is DRIM or ACM.
A value of 0 for the tru_id parameter indicates that the site is not TopCell.

max_dris per GPROC

Verify that the max_dris parameter setting in the database for the DHPs and/or the configured
BTPs for the SITE has the capacity for the extra DRI.

antenna_select number
The antenna_select number DRI attribute contains the receiver antenna select number for the
first shared cell. Verify that the coupling at the site matches the setting in the database.

68P02901W17-T
Jan 2010

7-59

antenna_select number

7-60

Chapter 7: Configuring a Site

68P02901W17-T
Jan 2010

Chapter

8
Configuring cells

The procedures here show how to configure cells and cell neighbors using the Navigation Tree,
Detailed Views, and TTY interface. Also shown are procedures to manipulate cell parameters,
for example, how to change a BCCH carrier frequency. The following topics are described:

General information for configuring cells on page 8-4.

Adding a cell (recommended procedure) on page 8-6.

Adding a cell using the copy/change method on page 8-8.

Adding a cell using the TTY interface on page 8-10.

Adding a cell using the OMC-R GUI on page 8-11.

General cell parameter section on page 8-14.

Handover cell parameter section on page 8-48.

Power control cell parameter section on page 8-63.

GPRS cell parameter section on page 8-70.

Propagating cell parameters on page 8-79.

Deleting a cell on page 8-92.

Defining algorithms on page 8-94.

Modifying default algorithms using the OMC-R GUI on page 8-95.

Modifying default algorithms using the TTY interface on page 8-98.

Neighbors, Sources and Reciprocal Neighbors on page 8-106.

Viewing Sources, Neighbors and Reciprocals on page 8-109.

Creating and deleting Sources, Neighbors and Reciprocals on page 8-115.

Creating neighbors using Neighbor Detailed View on page 8-121.

Modifying a neighbor on page 8-130.

Deleting neighbors using the Navigation Tree Delete option on page 8-131.

Neighbor templates on page 8-133.

Configuring a UTRAN neighbor on page 8-135.

Proxy cells on page 8-141.

68P02901W17-T
Jan 2010

8-1

antenna_select number

8-2

Chapter 8: Configuring cells

Configuring a single proxy cell on page 8-143.

Autocreation of a ProxyCELL on page 8-150.

Configuring multiple proxy cells using cmutil on page 8-154.

Exporting and importing proxy cell information between OMC-Rs on page 8-155.

Synchronizing all OMC-R proxy cells within a network on page 8-160.

Dynamic propagation of proxy cell data to OMC-Rs on page 8-162.

Expanding the capacity of a cell on page 8-163.

Configuring frequency hopping on page 8-165.

Configuring frequency hopping using the OMC-R GUI on page 8-167.

Configuring frequency hopping using the TTY interface on page 8-175.

Checking frequency hopping configuration for cells on page 8-178.

Configuring a cell with BCCH and SDCCH in the EGSM band on page 8-179.

Configuring a cell for coincident multiband handovers on page 8-181.

Configuring a cell for adaptive handovers on page 8-185.

Configuring a neighbor cell for adaptive handovers on page 8-190.

Configuring a cell for flexible neighbor cell processing on page 8-195.

Configuring enhanced SDCCH to TCH band assignment on page 8-198.

Configuring enhanced SDCCH to TCH band assignment on page 8-198.

Configuring a cell for power control optimization on page 8-203.

Configuring a cell for multiple GPRS carriers on page 8-207.

Changing a BCCH carrier frequency on page 8-213.

Changing a non-BCCH carrier frequency on page 8-216.

Changing a BSIC on page 8-219.

Changing a TSC for a BCCH on page 8-221.

Propagating TSC updates on page 8-222.

Assigning a quality of 7 to missing measurement reports on page 8-224.

Changing the number of allocated SDCCHs on page 8-226.

Establishing a cell boundary by changing transmit power on page 8-234.

Setting all channels at full power on page 8-237.

Barring calls at a cell on page 8-239.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

antenna_select number

Changing LAC and/or CI on page 8-242.

Viewing and editing the SMS-CB message using the OMC-R GUI on page 8-244.

68P02901W17-T

8-3
Jan 2010

General information for configuring cells

Chapter 8: Configuring cells

General information for configuring cells

Recommendation for small scale RF changes

It is recommended that small scale RF parameter changes to RTFs, cells, and neighbors are
made by editing Detailed Views. This method makes use of the neighbor and cell parameter
propagation features through the OMC-R MIB.
Neighbor propagation is a standard OMC-R feature which automatically sets specific neighbor
parameters at the BSS and OMC-R when source cells and RTFs are changed. Neighbor
propagation:

Removes the necessity for manually editing the neighbor, RTF and DRI Detailed Views, if
dependent cell and RTF parameters are changed.

Removes the necessity to perform an audit to detect parameter changes at the BSS.

Provides a facility to monitor the success of the internal/automatic propagation.

Cell parameters can be modified and propagated using the CELL Detailed View. See Propagating
cell parameters on page 8-79 for further details.

Recommendation for large scale RF changes

Large scale network RF parameter changes can be performed by exporting RF data from the
OMC-R to a replanning tool, such as Netplan. The data generated by the replanning tool can
then be imported back into the OMC-R. See Introduction to CellXchange on page 12-5 in
Chapter 12 for full details.

Viewing the sources, neighbors, and reciprocal neighbors for a

cell
Before adding new cells, it may be useful to view sources, neighbors, and reciprocal neighbors
for existing cells. See Neighbors, Sources and Reciprocal Neighbors on page 8-106 for further
details.

8-4

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Methods of adding a cell

Methods of adding a cell

A cell can be added using any of the following methods:

Copy/change method using the copy_cell command (recommended method), see Adding a
cell (recommended procedure) on page 8-6.

Using TTY interface and the add_cell command, see Adding a cell using the TTY interface
on page 8-10.

Using OMC-R GUI CELL Detailed View, see Adding a cell using the OMC-R GUI on page
8-11.

Creating cells at a Horizonmicro2 and Horizoncompact2 BTS

site
Up to three cells can be created at a Horizonmicro2 Horizoncompact2 BTS site. For more details
of Horizonmicro2 and Horizoncompact2, see Introduction to BSC and BTS sites on page 7-2.

68P02901W17-T

8-5
Jan 2010

Adding a cell (recommended procedure)

Chapter 8: Configuring cells

Adding a cell (recommended procedure)

Recommended method of adding a cell

The recommended Motorola method to add a cell is using the copy_cell command. This method
is quicker than adding a cell using the CELL Detailed View method. The main time saving is if
raw statistics are enabled in the cell being copied, default sets of raw statistics can be used.
The SITE does not have to be out of service to create a cell.
Ensure that the LAC-CI used are unique for the network.

Recommended procedure for adding a cell

To add and configure a cell, the recommended procedure is:

Procedure 8-1 Add a cell (recommended procedure)

1

Use the copy/change method to create a cell. See Adding a cell using
the copy/change method on page 8-8 for further details. Once the cell
is created, it appears on the Navigation Tree.

Enable any remaining required raw statistics. Use the

disp_enable_stat command to check which ones are enabled, and use
a batch rlogin script with the appropriate stat_mode commands.

Configure the handover and power control algorithm data for the cell,
see Defining algorithms on page 8-94 for further details.

Configure the frequency hopping objects for the cell, as required. See
Configuring frequency hopping on page 8-165.

Configure each associated RTF and DRI, enabling the RF hardware to

bring air interface timeslots into operation. Configure the RTF for
frequency hopping. See Configuring an RTF function on page 9-182
and Configuring a DRI on page 9-63 for further details.

NOTE
The DRIs and RTFs must have the same group number
(that is, DRI 0 0 matches RTF 0 0 or RTF 0 1.DRI 0 0 does
not bring RTF 1 0 or RTF 1 1 into service).
6

Add the required sources/neighbors for the cell. See Neighbors,

Sources and Reciprocal Neighbors on page 8-106.

Ensure each DRI and RTF configured for the cell is in service. See
OMC-R Online Help, Network Operations for further details about
locking and unlocking devices.
Continued

8-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Recommended procedure for adding a cell

Procedure 8-1 Add a cell (recommended procedure) (Continued)

68P02901W17-T

Verify that the cell is processing calls, using the disp_rtf_chan and
disp_cell_status commands. Refer to Technical Description: BSS
Command Reference (68P02901W23) for further details of these
commands.

If cells within the SITE are not processing calls, refer to Checking
key site parameters on page 7-59, which describes how to check the
settings of tru_id, max_dris per GPROC and antenna_select number.

10

Verify successful handovers take place into, and out of, the cell.

11

If necessary, configure SMS cell broadcast messages.

For example, to broadcast the name of the region the cell covers. See
Short Message Service - Cell Broadcast on page 2-45 for further details.

12

Verify the Performance Management reports are available for the

cell. See OMC-R Online Help, Network Operations for further details
of reports.

8-7
Jan 2010

Adding a cell using the copy/change method

Chapter 8: Configuring cells

Adding a cell using the copy/change method

Description of copy/change method

A cell can be created by selecting a similar existing cell and then using the copy_cell command
to copy it. The new cell details can be changed using the CELL Detailed View form. This cell
creation technique is referred to as the Copy/Change method.

NOTE
The site does not have to be out of service to create a cell.

Restrictions for copy_cell

When the PBCCH/PCCCH feature (pccchOpt) is unrestricted, the copy_cell command copies
all parameters at a cell to another new cell, except for the parameter PBCCH/PCCCH enabled
(pccch_enabled).

Creating a cell by copying then changing details

To copy a cell, then change the new cell details, follow these steps:

Procedure 8-2 Add a cell by copying and changing details

8-8

Find a cell that has parameters which match the cell to be created.

Remotely log in to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39 for further
details.

Use the copy_cell command to create a cell with the same parameters
as an existing cell. Refer to Technical Description: BSS Command
Reference (68P02901W23) for further details of copy_cell. The
created cell appears on the Navigation Tree.
The new cell has the same parameters as the copied cell but with a
new BSIC.

If required, change the cell parameters in the CELL Detailed View.

In particular, verify that cell_bar_access_switch (capability to set up
MS calls in cell) and en_incom_ho (the capability to receive incoming
handovers) are set to required values.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Example of a copy_cell command

Example of a copy_cell command

The following is an example of the input and output for the copy_cell command:
-> copy_cell 3 6 4 1 7 1C3 1D7 3 6 4 1 7 1C3 1D8 1 27
COMMAND ACCEPTED

68P02901W17-T

8-9
Jan 2010

Adding a cell using the TTY interface

Chapter 8: Configuring cells

Adding a cell using the TTY interface

Introduction to adding a cell using the TTY interface

This section describes the procedure for adding a cell to a site using the TTY interface.

NOTE
The recommended Motorola method to add a cell is using the copy_cell command.
See Adding a cell (recommended procedure) on page 8-6 for further details.
The cell can be added through the Batch Rlogin process using a script that contains the
add_cell command and its parameters, the algorithm and neighbor data.

Adding a cell using the add_cell command

To add a cell using the TTY interface, proceed as follows:

Procedure 8-3 Add cell using TTY interface

8-10

Remotely log in to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39 for further
details.

Enter the add_cell command and reply to the prompts with the
required data. See Technical Description: BSS Command Reference
(68P02901W23) for full details.

Define algorithm data for cell parameters using either the Navigation
Tree, or the chg_cell_element command from the TTY interface.

Define neighbor lists using the Navigation Tree.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adding a cell using the OMC-R GUI

Adding a cell using the OMC-R GUI

Introduction to adding a cell using the OMC-R GUI

NOTE
The recommended Motorola method to add a cell is using the copy_cell command.
See Adding a cell (recommended procedure) on page 8-6 for further details.
The OMC-R GUI CELL Detailed View can also be used to create a cell. If the CELL Detailed
View method is used to create a cell, also refer to Adding a cell (recommended procedure) on
page 8-6 for an overview of the complete cell configuration procedure.

Using the CELL Detailed View to create a cell

To display the CELL Detailed View, follow these steps:

Procedure 8-4 Add cell using OMC-R GUI

1

Navigate to and select the CELL class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Radio Frequency
CELL). If necessary, see Navigating to a network object class or
instance on page 1-28 for further details. The CELL class button
changes color.

Select Edit Create from the menu bar. The OMC-R displays the CELL
Detailed View form in Create mode. At the top of the CELL Detailed
View, there are four section buttons as shown in Figure 8-1.

Click one of the following buttons to display more cell parameter fields
grouped by function:

General, see General cell parameter section on page 8-14 for

details of these parameters. By default, the form shows the
General cell parameter fields.

Handover, see Handover cell parameter section on page 8-48 for

details of these parameters.
Continued

68P02901W17-T

8-11
Jan 2010

Using the CELL Detailed View to create a cell

Chapter 8: Configuring cells

Procedure 8-4 Add cell using OMC-R GUI (Continued)

Power Control, see Power control cell parameter section on page

8-63 for details of these parameters.

GPRS, see GPRS cell parameter section on page 8-70 for details
of these parameters.

If necessary, click the grouping button to display the individual cell

parameter fields.
Use the scroll bar to display all the parameters in each grouping, if
necessary.

Complete the required parameter fields in each grouping as required.

Press TAB after entering each value.

NOTE
To obtain the relevant information for a parameter, select
Help - On Context from the menu bar and drag the ?
prompt to the appropriate field and click that field. A
context-sensitive help page is displayed.

8-12

Select File Create from the menu bar to create the cell.

Select File Close from the menu bar to close the CELL Detailed
View form.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Autocreation of cell algorithms

Figure 8-1 CELL Detailed View showing parameter section buttons

ti-GSM-CELLDetailedViewshowingparametersectionbuttons-00799-ai-sw

Autocreation of cell algorithms

Cell algorithms are automatically created when a cell is created (and autodeleted when a cell is
deleted).
When the cell creation is complete, the OMC-R displays an information message stating that
handover and power control algorithm field: Algorithm Number (parameter name: alg_num)
must be changed from Unused (255) to another setting before creating RTFs or DRIs.

Modifying a cell using the OMC-R GUI

To display and modify the parameters of a cell, see the general procedure in Modifying a
network object using the OMC-R GUI on page 1-34. Use the cell parameter grouping buttons at
the top of the window to select the type of cell parameters to be modified.

68P02901W17-T

8-13
Jan 2010

General cell parameter section

Chapter 8: Configuring cells

General cell parameter section

Displaying General cell parameter section

To display General cell parameter section, click the General button at the top of the CELL
Detailed View.

General cell parameter section groupings

The following sections list and briefly describe the parameter groupings and fields in the CELL
Detailed View General section. Unless stated otherwise, the OMC-R database parameter
name is the same as the BSS database parameter name. BSS parameters are described in detail
in Technical Description: BSS Command Reference (68P02901W23).

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 8-1 describes the fields in the General - Identification grouping of the CELL Detailed View.

Table 8-1 CELL Detailed View, General - Identification grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Name

Unique Cell name.

Up to 31
characters
plus the NULL
character.

GSM Cell ID

The unique GSM Cell identifier (also

known as Cell Global Identification
(CGI)). Made up of the following
sub-fields: Mobile Country Code
(MCC), Mobile Network Code (MNC),
Location Area Code (LAC), Cell
Identity (CI).
The MCC and MNC subfields can be
edited in Create and Edit mode.

There are two

Mandatory.
types of GSM cell
ID input format;
seven elements
or four elements.
The format used is
set with the GSM
Cell ID Format
(mmi_cell_id_format)
parameter.

Optional.

Continued

8-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-1 CELL Detailed View, General - Identification grouping (Continued)

Field name/BSS
parameter name

Brief description

Values

(By default, the MCC and MNC

sub-fields are entered when the
network was created.) The MCC and
MNC sub-fields cannot be edited for
n-1 or n-2 BSS.
A two digit MNC is supported for
all frequency types, except when
frequency_type is 8 (PCS1900), in
which case a three digit MNC is
supported.

See Technical
Description:
BSS Command
Reference
(68P02901W23)

Base Station
Identity Code
(BSIC)

A local color code that allows an

MS to distinguish between different
neighboring base stations. BSIC
is encoded on the Synchronization
Channel.

Default is 0.

Layer Number
layer_number

Indicates on which layer the cell

exists. Not relevant if Microcellular
is restricted.

0 - 2. Macro (0),
Micro (1), Pico (2).

RDN Class

See description in Table 4-1.

Default is CELL.

RDN Instance

See description in Table 3-1.

Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

site. Click to display the parent SITE
Detailed View.

Mandatory or
Optional?

for further details

of GSM Cell Id
formats.

Mandatory.

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this CELL. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for further details.

General grouping
Table 8-2 describes the fields in the General - General grouping of the CELL Detailed View.

68P02901W17-T

8-15
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-2 CELL Detailed View fields, General - General grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Discontinuous
Transmission Mode
dtx_required

The Mobile Station (MS)

capability to use discontinuous
transmission. Enabling helps to
reduce interference and prolong
battery life.

Frequency Type

See Configuring a cell with BCCH

and SDCCH in the EGSM band on
page 8-179 for further details of this
field.

Minimum Receive
Level Default
rxlev_min_def

The default value to be used for

the Neighbor rxlev_min_cell by
contained Neighbors.

0 - 63.
Default is 15.

Mandatory.

Decision Algorithm
Type
decision_alg_type

The decision algorithm is currently

being used.

0 or 1. Default
is 0 (handover
decision
algorithm
number 1).

Mandatory.

NCC of PLMN
Allowed
ncc_of_plmn
_allowed(OMC-R
parameter name:
nccOfPlmn
Allowed)

Which foreign Network Color Codes

(NCCs) are allowed on specific
broadcast control channels (BCCH
carriers).

0 - 255
(Bitmapped
value of network
country codes).
Default is 255.

Mandatory.

Maximum Number
of Preferred Cells
number_of
_preferred_cells
(OMC-R parameter
name:
numOfPrefCells)

The maximum number of target cells

to be included in the HANDOVER_
REQUIRED message.

1 - 16.
Default is 16.

Mandatory.

Power Excluding
Broadcast Ctrl
Channels
pwrc

Whether the Broadcast Control

Channels (BCCH) measurement is
included in the averaged value of
hopping frequencies.

0 or 1. Default
is Measurement
Not Included (1).

Mandatory.

Cell Broadcast
Channel (CBCH)
cbch_enabled

Whether the Cell Broadcast Channel

is enabled.

0 or 1. Default is
Disabled (0).

Mandatory.

Hopping Support
hopping_support

The type of hopping supported in

this cell.
If any DRI servicing the cell is
Double density, and the container
site is anything other than a Horizon
II macro, this field cannot be
modified to 2.

0 - 2. No Hopping
(0), Synthesizer
Hopping (1),
Baseband
Hopping (2).
Default is 0.

Optional.

0 - 2. Permitted
(0), Required
(1), Disallowed
(2). Default is
Disallowed (2).

Mandatory.

Mandatory.

Continued

8-16

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 8-2

General cell parameter section groupings

CELL Detailed View fields, General - General grouping (Continued)

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Automatic RF Loss
Trace Reporting
auto_rf_loss_trace
(OMC-R parameter
name:
auto_rf_loss)

Enables and disables RF Loss

reporting for a cell.

0 - 2. Disabled
(0), or Enabled,
sends reports to
OMC and MMI
(1), or Enabled,
sends reports to
OMC (2). Default
is Disabled (0).

Mandatory.

Extended Range
Cell
ext_range_cell

Whether the Extended Range Cell

option is enabled or disabled for the
cell.
Can only be modified if:

0 - 2.
Default is 0.
Extended range
is disabled for the
cell (0), Extended
range is enabled
as a Boundary
cell (1), Extended
range is enabled
as an Isolated cell
(rural area) (2).

Mandatory.

all related DRIs in the cell have

been locked.

the Extended Range

Cell feature (ercOpt) is
unrestricted for the BSS.

pccch_enabled is set, any attempt

to change this value is rejected.
Prioritize Microcell
prioritize
_microcell(OMC-R
parameter name:
prior_micro)

If the level of the serving cell

impacts sorting of the HO candidate
list. Only valid if the Microcellular
option is not restricted.

Default is
Enabled (1) (will
impact sorting of
candidate list).

Optional.

Cell Transmit
Power
tx_power_cap

Whether the cell is high or low

transmit power. Only valid for
cells with DCS1800 and PCS1900
frequency types or cells that are
configured as Dual Band cells. Not
valid for micro type sites.
Set to High Power (1) for a Horizon
II macro site, which cannot be
changed by a user.

0 or 1. Low
power (0), High
power (1).
Default is 0.

Optional.

EGSM Carrier
Configuration
Information

See Configuring a cell with BCCH

and SDCCH in the EGSM band on
page 8-179 for further details.

Optional.

Ext Range
Neighbor Priority

See Configuring a cell for extended

cell range prioritization on page
8-201 for further details.

Optional.

Rpt Bad Quality on

a Missing Rpt

See Assigning a quality of 7 to

missing measurement reports on
page 8-224 for further details.

Optional.

Continued

68P02901W17-T

8-17
Jan 2010

General cell parameter section groupings

Table 8-2

Chapter 8: Configuring cells

CELL Detailed View fields, General - General grouping (Continued)

Field name/BSS
parameter name
Downlink DTX for
Voice/Data
dl_dtx_voice_data

Brief description
Allows downlink discontinuous
transmission (DTX) to be enabled
independently for speech and
Non-Transparent (NT) data calls.

Values
0 - 3.
Enabled for
speech and
disabled for NT
data (0).
Disabled for
speech and
disabled for NT
data (1).
Disabled for
speech and
enabled for NT
data (2).
Enabled for
speech and
enabled for NT
data (3).
Default is 0.

Mandatory or
Optional?
Mandatory.

{34452} PCH
Used to set the PCH queue length
Queue Length Ctr
to 648 or 2*648.
pch_queue_length
_ctr

Range is 1 to 2
1 Sets the PCH
queue length to
648
2 Sets the PCH
queue length to
2*648
Default is 2

Optional.

{34452} AGCH
Flow Control Mode
agch_flow_control
_mode

Range is 0 to 2.
0 Disabled.
1 The
functionality
of AGCH flow
control is
enabled, and
any one of
the triggers
associated with
IA and IAR can
trigger AGCH
overload.
2 The
functionality
of AGCH flow
control is
enabled, while
only the trigger
associated with
IA can trigger
AGCH overload.
Default is 1.

Optional.

Used to indicate whether the

functionality of AGCH flow control
is enabled or not, and also indicates
the triggers that are associated with
IA and IAR that can trigger AGCH
overload.

Continued

8-18

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 8-2

General cell parameter section groupings

CELL Detailed View fields, General - General grouping (Continued)

Field name/BSS
parameter name

Values

Brief description

{34452} CStats
Used to indicate whether the
Cell Enabled
functionality statistics uploading in
cstats_cell_enabled five-minute interval for the cell is
enabled or not.

Range is 0 to 1.
0 is Disabled.
1 is Enabled.
Default is 0.

Mandatory or
Optional?
Optional.

System Access grouping

Table 8-3 describes the fields in the General - System Access grouping of the CELL Detailed View.

Table 8-3 CELL Detailed View fields, General - System Access grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Call
Re-Establishment
reestablish
_allowed(OMC-R
parameter name:
reestablishAllwd)

Enables or disables call reestablishment

after a radio link failure.

0 or 1.
Default is
Enabled (0).

Mandatory.

Cell Barred Access

Class
cell_bar_access
_class
(OMC-R
parameter name:
cellBarAccClass)

Defines access classes that are barred

(or not barred) access to the PLMN. A
channel request is only initiated when
the access class of a mobile is not
barred.

0 - 65535.
Default is 0.

Mandatory.

Subscriber Access
to Cell

See Barring calls at a cell on page 8-239

for details.

IMSI
Attach/Detach
attach_detach

A flag to the Mobile Station (MS) to

either enable, or disable the mandatory
International Mobile Subscriber
Identity (IMSI) attach/detach.

Default is
Disabled (0).

Mandatory.

Emergency Class
Switch
emergency
_class_switch
(OMC-R
parameter
name:
emergencyClass)

Enables or disables emergency calls by

access class.

0 or 1.
Enabled in
cell for access
classes 11 - 15
only (1).
Enabled for All
Classes (0).
Default is 0.

Mandatory.

Maximum
Retransmissions
max_retran

The maximum channel request

retransmission value for Mobile
Stations (MSs).

0 - 3.
Default is 1
Retransmission
(0).

Mandatory.

Mandatory.

Continued

68P02901W17-T

8-19
Jan 2010

General cell parameter section groupings

Table 8-3

Chapter 8: Configuring cells

CELL Detailed View fields, General - System Access grouping (Continued)

Field name/BSS
parameter name

Brief description

Mandatory or
Optional?

Values

Maximum Control
Channel Transmit
Power
ms_txpwr_max
_cch

Maximum random access power

available for a mobile station, on a
control channel (CCCH) in a cell.

0 or 19.
Default is 2.

Mandatory.

Mobile Station
Power Offset
ms_power_offset

Read by the mobile from the BCCH

system information. It is used in
addition to cell ms_txpwr_max_cch
to determine the new power for
cell selection by the mobile before
accessing the cell on the RACH.

0 - 3.
Default is 0 dBm
(0).

Mandatory.

Number of RACH
Slots Between
Access Retries
tx_integer

The number of Random Access Channel

(RACH) slots between the access retry
transmission on the RACH.

0 - 15.
Default is 4.

Mandatory.

Wait Indication
The T3122 timer value (in seconds) that
Parameters
the MS uses.
wait_indication
_parameters
(OMC-R
parameter name:
waitIndicParams)

0 - 255.
Default is 5.

Mandatory.

RR_T3212 Timer
rr_t3212

Governs the mobile's periodic location

update procedure.

0 - 255 (1
range step =
1 decihour).
Default is 10.

Mandatory.

RR_T3101 Timer
rr_t3101

The time the BSS waits for the MS to

establish on an SDCCH after sending
an immediate assignment message.

0 - 1000000
(ms).
Default is 5000.

Mandatory.

Cell selection - reselection grouping

Table 8-4 describes the fields in the General - Cell Selection-Reselection grouping of the CELL
Detailed View.

8-20

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-4 CELL Detailed View fields, General - Cell Selection/Reselection grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Min Received
Signal Level For
Access
rxlev_access_min

The minimum received signal level

(dBm) required for an MS to access the
system.

0 - 63.
Default is 0
(-110 dBm).

Mandatory.

Cell Reselect
Hysteresis Level
cell_reselect
_hysteresis

The hysteresis level for cell reselection

into a different location area.

0 (0 dB) to 7
(14 dB).

Mandatory.

(OMC-R
parameter
name:
cellReselectHys)

Default is 0 dB
(0).

Cell Reselection
Whether C2 cell reselection parameters
Parameters
being broadcast is system information
cell_reselect
of this cell.
_param_ind(OMC-R
parameter
name:
cellResel
ParamInd)

0 or 1.
Default is C2
Parameters
Not Present
(0).

Mandatory.

Low Cell Selection

Priority
cell_bar_qualify

The priority of the cell. Used for

computing the C2 cell reselection
criterion.

0 or 1.
Default is
Priority is Not
Low (0).

Mandatory.

Cell Reselect
Offset
cell_reselect
_offset(OMC-R
parameter name:
cellReselectOffs)

The positive or negative offset for

computing the C2 cell reselection
criterion.

0 - 63 (dB
where each
range step
equals 2 dB).
Default is 0.

Mandatory.

Temporary Offset
temporary_offset

The negative offset for computing

the C2 cell reselection criterion for
the duration specified by the CELL
penalty_time.

0 - 7.
Default is 0.

Mandatory.

Penalty Time
penalty_time

The duration for which the

value specified by the CELL
temporary_offset is valid.

0 - 31.
Default is 0.

Mandatory.

Network Control
Order

See Network Controlled Cell

Reselection on page 2-81 for details.

Mandatory.

Radio Channel Configuration grouping

Table 8-5 describes the fields in the General - Radio Channel Configuration grouping of the
CELL Detailed View.

68P02901W17-T

8-21
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-5 CELL Detailed View fields, General - Radio Channel Config grouping
Field name/BSS
parameter name

Brief description

Mandatory or
Optional?

Values

CCCH
configuration

See Changing the number of allocated

SDCCHs on page 8-226 for further
details.

Mandatory.

Number of
Reserved Access
Grant Blocks
bs_ag_blks_res

See Changing the number of allocated

SDCCHs on page 8-226 for further
details.

Mandatory.

Period Between
Mobile Paging
Messages
bs_pa_mfrms

The number of 51 frame multiframes

between transmissions of paging
messages to MSs of the same paging
group.

Default is 2
Multiframes (0).

Mandatory.

Activate Extended
Paging
extended_paging
_active(OMC-R
parameter name:
extended
PagingAct)

Activates or deactivates extended

paging. The MS receives and analyzes
the paging messages on the paging
subchannel, that corresponds to the
paging subgroup.

Default is
Normal Paging
(0).

Mandatory.

Channel
Reconfiguration
Preferred Number
of SDCCH
Maximum
Number of
SDCCH
SDCCH Need
High Water Mark
SDCCH Need Low
Water Mark

See Changing the number of allocated

SDCCHs on page 8-226 for further
details of these fields.

Report Resource
TCH Full High
Water Mark
report_resource
_tch_f_high
_water_mark
(OMC-R
parameter name:
repResTchF
HighWm)

The upper limit threshold of a full-rate

traffic channel (TCH).

0 - 254 (number
of TCHs).
Default is 2.

Mandatory.

Report Resource
The lower limit threshold of a full-rate
TCH Full Low
traffic channel (TCH).
Water Mark
report_resource
_tch_f_low
_water_mark(OMC-R
parameter name:
repResTchFLowWm)

1 - 255 (number
of TCHs).
Default is 12.

Mandatory.

Continued

8-22

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-5 CELL Detailed View fields, General - Radio Channel Config grouping
(Continued)
Field name/BSS
parameter name

Brief description

TCH Full Need

Low Water Mark

See Changing the number of allocated

SDCCHs on page 8-226 for further
details.

Time From
Cell-Outage to
RF Termination
(secs.)
stop_dri_tx_time

It takes time to stop RF transmission

in a cell after it has been OOS. To
avoid adding additional time to a
short cell outage (for example caused
by the momentary interruption of a
non-redundant RSL), this field provides
the ability to maintain RF transmission
for a number of seconds (0 to 1800)
into the cell outage. This allows
the termination and restart of RF
transmission to be avoided for a short
cell outage.
Only takes effect if stop_dri_tx_enable
is Yes(1).

TCH Usage
Threshold
tch_usage
_threshold

See Fast Call Setup on page 2-168 for

further details.

Values

0 - 1800
seconds
Default: 300
seconds.

Mandatory or
Optional?

Optional.

Queuing grouping
Table 8-6 describes the fields in the General - Queuing grouping of the CELL Detailed View.

Table 8-6 CELL Detailed View fields, General - Queuing grouping

Field name/BSS
parameter name
Queue Length
Management
Information
queue
_management
_information
(OMC-R parameter
name:
queueMgtInfo)

Brief description
The number of subscribers that
can wait in the queue for channel
assignment.

Max Queue Length The maximum number of MSs that can

Channel
wait in queue for a channel assignment
max_q_length
(applied to both full rate and half rate).
_channel
(OMC-R parameter
name:
maxQLengthChan)

Values

Mandatory or
Optional?

0 - 50.
Default is 50.
(0 disables
queuing).

Mandatory.

0 - 50.
Default is 0.

Mandatory.

Continued

68P02901W17-T

8-23
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-6 CELL Detailed View fields, General - Queuing grouping (Continued)
Field name/BSS
parameter name
Max Queue Length
SDCCH
max_q_length
_sdcch
(OMC-R parameter
name:
maxQLgtSdcchs)

Brief description
The maximum length of the queue
for Stand-alone Dedicated Control
Channel (SDCCH) requests.

Values
0 - 50.
Default is 0.

Mandatory or
Optional?
Mandatory.

Flow Control grouping

Table 8-7 describes the fields in the General - Flow Control grouping of the CELL Detailed View.

Table 8-7 CELL Detailed View fields, General - Flow Control grouping
Field name/BSS
parameter name
Random Access
Channel Load
Period
rach_load_period

8-24

Brief description
How often to check for the RACH
overload condition when the cell is
not in RACH overload.

Values

Mandatory or
Optional?

1 - 1020 (ms
/941.5).
Default is 16.

Mandatory.

Random Access
The threshold level for RACH loading.
Channel Load
Threshold
rach_load
_threshold
(OMC-R parameter
name:
rach_load_thresh)

0 - 1000.
Default is 1000.

Mandatory.

CCCH Load Period

ccch_load_period

How often to check for RACH and/or

AGCH overload, once the cell under
consideration is already overloaded.

1 - 1020 (in
235 millisecond
units).
Default is 40.

Mandatory.

TCH Flow Control

tch_flow_control

Enables or disables the flow control

of the TCH Congestion flow control.

Enabled (1) or
Disabled (0).
Default is 0.

Mandatory.

Flow Control T1
Timer

See MSC to BSS overload control on

page 2-23.

Mandatory.

Flow Control T2
Timer

See MSC to BSS overload control on

page 2-23.

Mandatory.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Channel allocation-deallocation grouping

Table 8-8 describes the fields in the General - channel allocation-deallocation grouping of the
CELL Detailed View.

Table 8-8 CELL Detailed View fields, general - channel allocation-deallocation

grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Interference
Average
intave

The averaging period in terms of

number of SACCH multiframes.

1 - 31.
Default is 8.

Mandatory.

Interference Band
0 to 4
interfer_band0-4

Contain the limit for the interference

categories (bands) 0 to 4.

0 - 63.
Default is 63.

Mandatory.

RR_T3109 Timer
rr_t3109

The time allowed before a channel is

released after a communications loss.

0 - 1000000 ms.
Default is
14400.

Mandatory.

RR_T3111_TCH
Timer
rr_t3111_tch

The time allowed to delay the

deactivation of a channel after the
disconnection of the main signaling
link.

0 - 1000000 ms.
Default is 1500.

Mandatory.

RR_T3111_SD
Timer
rr_t3111_sd

The time allowed to delay the

deactivation of a channel after the
disconnection of the main signaling
link.

0 - 1000000 ms.
Default is 1500.

Mandatory.

Deallocate Inactive
Timer
dealloc_inact

The timer that governs the deallocation

of a channel for which a fatal error
indication has been received from the
BSS.

0 - 1000000 ms.
Default is 5000.

Mandatory.

RF Channel
Release
Acknowledgment
Timer
rf_chan_rel_ack

The amount of time that the system

waits for an RF channel release
(acknowledgment) message from the
Radio SubSystem (RSS).

0 - 1000000 ms.
Default is 5000.

Mandatory.

Threshold
threshold

The number of times the Cell Resource

Manager (CRM) attempts to assign
a Signaling Connection Control Part
(SCCP) number before rejecting the
request.

0 - 255.
Default is 7.

Mandatory.

68P02901W17-T

8-25
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Radio Link Control grouping

Table 8-9 describes the fields in the General - Radio Link Control grouping of the CELL Detailed
View.

Table 8-9 CELL Detailed View fields, general - radio link control grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

The threshold (limit) for the radio

downlink failure on the Slow
Associated Control Channel (SACCH).

0 - 15.
Default is 20
SACCH blocks
(4).

Mandatory.

Link Fail
Threshold
link_fail

The amount of non-received SACCH

frames before a loss of SACCH is
reported to Abis.

0 - 15.
Default is 20
SACCH blocks
(4).

Mandatory.

Full Power Radio

Frequency Before
Loss
full_pwr_rfloss

Enables or disables the ability of the

BTS to switch the BSS and MS power
levels to full before allowing radio link
timeout in an attempt to restore the
link.

Default is
Disabled (0).

Mandatory.

0 - 15.
Default is 8
SACCH blocks
(2).

Mandatory.

Radio Link
Timeout
radio_link
_timeout
(OMC-R
parameter name:
radioLink
Timeout)

Link About to Fail

The amount of non-received SACCH
Threshold
frames before the MS and BS is
link_about_to_fail switched to full power.
(OMC-R
parameter name:
linkAboutToFail)

Congestion relief grouping

Table 8-10 describes the fields in the General - Congestion Relief grouping of the CELL Detailed
View.

Table 8-10 CELL Detailed View fields, general - congestion relief grouping
Field name/BSS
parameter name
Retry Candidate
Period Timer
rtry_can_prd
(OMC-R parameter
name:
retry_cand_period)

Brief description
Time between successive attempts
to handover to target cells which
had previously rejected a handover
attempt. Only valid when BSS
congestReliefOpt is Enabled (1).

Values
1 - 1000000
(ms).
Default is 4000.

Mandatory or
Optional?
Optional.

Continued

8-26

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-10 CELL Detailed View fields, general - congestion relief grouping (Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Congestion at
Target Cell
congest_at_target

How the cell behaves if it rejects a

handover request. When enabled
(1), after rejecting a handover a
cell shall invoke congestion relief
procedure. When disabled (0), after
rejecting a handover, the cell takes
no action. Only valid when BSS
congestReliefOpt is Enabled (1).

Default is
Disabled (0).

Optional.

Congestion at
Source Cell
congest_at_source

How a cell behaves if it is unable

to service a given congestion relief
handover. When enabled (1) the cell
is allowed to retry handovers to those
cells which had previously rejected
the request for a handover. When
disabled (0) no action is taken if a
handover is rejected. Only valid when
BSS congestReliefOpt is Enabled
(1).

Default is
Disabled (0).

Optional.

MB TCH
The percentage at which MultiBand
Congestion
mobiles start to be re-directed to
Threshold
the preferred band. Only valid when
mb_tch_congest
BSS congestReliefOpt and BSS
_thres
mbInterCellHoOpt are Enabled (1).
(OMC-R parameter
name:
mb_tch_cong_thres)

1 - 101.
Default is 100.

Optional.

External Retry
Period Timer
ext_rtry_cand_prd
(OMC-R parameter
name:
exRtryCandPrd)

The time between successive

attempts to handover to external
non-coincident target cells which
have previously rejected a handover
attempt.

1 - 1000000
(ms).
Default is 4000.

Optional.

Valid Candidate
Period Timer
valid_candidate
_period
(OMC-R parameter
name:
validCandPeriod)

The duration that candidates for

handovers due to congestion are valid
before querying for new ones.

1 - 1000000 ms.
Default is 4000.

Mandatory.

Handover existing
calls
ho_exist_congest

Whether attempts to handover

existing calls on a TCH are initiated
in the case of an MS needing a
TCH when there are none available
in that cell. Only valid when BSS
congestReliefOpt is Enabled (1).

0 - 2.
Default is 0
(Disabled).

Optional.

Continued

68P02901W17-T

8-27
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-10 CELL Detailed View fields, general - congestion relief grouping (Continued)
Field name/BSS
parameter name

Brief description

Mandatory or
Optional?

Values

TCH Congest
Prevent Threshold
tch_congest
_prevent_
thres
(OMC-R parameter
name:
tch_congprev_thr)

The TCH congest prevention

threshold. If the TCH allocation
causes the percent busy TCH to be
greater than tch_congprev_thr, then
the Congestion Relief Procedure is
initiated. Only used the BSS feature
congestReliefOpt is unrestricted.

1 - 101 %.
Default is 100.

Optional.

Enhanced
Congestion Relief
enhanced_relief

Whether the Enhanced Congestion

Relief (ECR) feature is Enabled (1) or
Disabled (0) for this cell. Only valid
when Alternative Congestion Relief
congestReliefOpt is unrestricted
(Enabled (1)) for the BSS.

Default is
Disabled (0).

Optional.

Directed retry grouping

Table 8-11 describes the fields in the General - Directed Retry grouping of the CELL Detailed
View. These parameters are only used when the Directed Retry Feature BSS feature
(directedRetryOpt) is unrestricted.

Table 8-11 CELL Detailed View fields, general - directed retry grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Directed Retry Std

Congestion Allowed
dr_std_congest

If directed retry is allowed at the

external neighbor.

Default is No
(0).

Optional.

MSC Preference
msc_preference

The message sequence and contents

across the A-interface during directed
retry procedures that require
an external handover during the
assignment procedure.

0 - 7.
Default is 0
(directed retry
supported
within the BSS
(not across the
A-interface)).

Optional.

Directed Retry HO
during Assign
dr_ho_during
_assign
(OMC-R parameter
name:
dr_ho_dur
_assign)

If a handover can be processed during

an assignment procedure.

Default is
Ignore need of
handover (0).

Optional.

Concentric and dual-band cells grouping

See Dual band cells option on page 2-28 for details of how to configure dual band cells.

8-28

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Multiband handover grouping

Table 8-12 describes the fields in the general - multiband handover grouping of the CELL
Detailed View.

Table 8-12 CELL Detailed View fields, general - multiband handover grouping
Field name/BSS
parameter name
Interband
Handover
Allowed
interband_ho
_allowed

Brief description

Values

The destination frequency

band for handover. Cannot
be modified if the MultiBand
Inter-Cell Handover feature
(mbInterCellHoOpt)
is disabled. If the
mbInterCellHoOpt is disabled
(restricted), the default is the
frequency_type of the cell. If
mbInterCellHoOpt is enabled
(unrestricted), when a cell
is created, if a value is not
specified, the default value
is 3 for PGSM and EGSM
cells. This assumes that
freqTypesAllowed allows both
PGSM and EGSM frequency
types at the BSS. If either
PGSM or EGSM is not allowed
at the BSS, the default is the
CELL frequency_type. For
example, if adding a PGSM
cell when PGSM is allowed
at the BSS but EGSM is not
allowed, the default value
is 1 (PGSM). Defaults to
the CELL frequency_type
for DCS1800 and PCS1900
cells. Must always, at a
minimum, contain the value
representing the CELL
frequency_type of the Cell.
For example, if the cell
associated with this attribute
has a CELL frequency_type
of PGSM (1), the Interband
Handover Allowed must
always contain PGSM as a
possible value (that is, one of
values 1,3,5,7,9, or 11).

1 - 11, where:
1 = PGSM
2 = EGSM.
3 = PGSM and EGSM.
4 = DCS1800.
5 = PGSM and DCS1800.
6 = EGSM and DCS1800.
7 = PGSM, EGSM, and
DCS1800.
8 = PCS1900.
9 = PGSM and PCS1900.
10 = EGSM and PCS1900.
11 = PGSM, EGSM, and
PCS1900.

Mandatory or
Optional?
Optional.

Continued

68P02901W17-T

8-29
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-12 CELL Detailed View fields, general - multiband handover grouping
(Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Band
Preference
band
_preference

See Dual band cells option

on page 2-28, Advanced
Load Management for EGSM
on page 2-78, Configuring
enhanced SDCCH to TCH
band assignment on page
8-198 and for details.

Optional.

IMRM Force
Recalculation
imrm_force
_recalc

See for details.

Optional.

IMRM PGSM
Weighting
(0100)
imrm_pgsm
_weight

See for details.

Optional.

IMRM EGSM
Weighting
(0-100)
imrm_egsm
_weight

See for details.

Optional.

IMRM DCS1800
Weighting
(0-100)
imrm_dcs1800
_weight

See for details.

Optional.

IMRM UMTS
Weighting
(0-100)
imrm_umts
_weight

See for details.

Optional.

Band
Preference
Mode
band
_preference
_mode

See Dual band cells option

on page 2-28, Advanced
Load Management for EGSM
on page 2-78, Configuring
enhanced SDCCH to TCH
band assignment on page
8-198 and for details.

Optional.

Continued

8-30

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-12 CELL Detailed View fields, general - multiband handover grouping
(Continued)
Field name/BSS
parameter name
Multiband
Reporting
multiband
_reporting

Brief description

Values

The number of Cells in each

supported band to be included
in the Measurement Report
message by an MS. Cannot
be accessed if the MultiBand
Inter-Cell Handover
(mbInterCellHoOpt) feature
is disabled (restricted).

0 - 3, where:
0 = Normal reporting of
the six strongest neighbor
cells with known and
allowed NCC part of
BSIC, irrespective of the
band used.
1 = Report the strongest
neighbor cell, with known
and allowed NCC part
of BSIC, in each of
the frequency bands in
the neighbor cell list,
excluding the frequency
band of the serving cell.
The remaining positions in
the measurement report
are used for reporting
Cells in the band of
the serving Cell. Any
still remaining positions
are used to report the
next strongest identified
neighbors in other bands
irrespective of the band
used.
2 = Report the two
strongest cells, with
known and allowed NCC
part of BSIC, in each of
the frequency bands in
the neighbor cell list,
excluding the frequency
band of the serving cell.
The remaining positions in
the measurement report
are used for reporting
Cells in the band of
the serving Cell. Any
positions that remain
are used to report the
next strongest identified
neighbors in other bands
irrespective of the band
used. (continued...)

Mandatory or
Optional?
Optional.

Continued

68P02901W17-T

8-31
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-12 CELL Detailed View fields, general - multiband handover grouping
(Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

3 = Report the three

strongest cells, with
known and allowed NCC
part of BSIC, in each of
the frequency bands in
the neighbor cell list,
excluding the frequency
band of the serving cell.
The remaining positions in
the measurement report
are used for reporting
Cells in the band of
the serving Cell. Any
still remaining positions
are used to report the
next strongest identified
neighbors in other bands
irrespective of the band
used.
Default is 0.
SDCCH to TCH
Band Reassign
Delay

See Configuring enhanced

SDCCH to TCH band
assignment on page 8-198 for
further details.

Coincident Multiband HO grouping

For details of how to configure coincident multiband handover cells, see Configuring a cell for
coincident multiband handovers on page 8-181.

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)
grouping
Table 8-13 describes the fields in the General - Channel Mode Usage (AMR Full Rate and
Half Rate/GSM Half Rate) grouping of the CELL Detailed View. Unless stated otherwise, the
OMC-R database parameter names are the same as the BSS database parameter names.
Fields in this grouping can be accessed if the AMR Feature (amrOpt) or the GSM HR Feature
(gsmHalfRateOpt) are unrestricted (Enabled) at the BSS. Fields in this grouping cannot be
accessed if the site is not AMR or GSM HR capable, see Adaptive Multi-Rate (AMR) on page
2-129 for details.

8-32

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 8-13
grouping

General cell parameter section groupings

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)

Field name/BSS
parameter name
AMR Hop Count
fr_hr_hop_count

Brief description
Controls the number of intracell
handovers from Half Rate channels to
Full Rate channels for a call.
Must not exceed the value of
hop_count (see Table 8-18).

Values
0 - 255.
Default is 1.

Mandatory or
Optional?
Optional.

AMR Full Rate grouping

Table 8-14 describes the fields in the General - AMR Full Rate grouping of the CELL Detailed
View. Unless stated otherwise, the OMC-R database parameter names are the same as the
BSS database parameter names. Fields in this grouping can be accessed if the AMR Feature
(amrOpt) is unrestricted (Enabled) at the BSS, or if the site is not AMR capable, see Adaptive
Multi-Rate (AMR) on page 2-129 for details.

Table 8-14 CELL Detailed View fields, General - AMR full rate grouping
Field name/BSS
parameter name
AMR Full Rate
Enabled
amr_full_rate
_enabled
(OMC-R parameter
name:
amr_fr_enabled)

Brief description
Enables and disables AMR Full Rate
(FR) for the cell.
Grayed-out if the BSS has both the
amrTCUAopt and amrTCUBOpt
Features restricted, and the site
contains only M-CELL2 and/or
M-CELL6 cabinets. However, if
the site has Horizonmacro and/or
Horizonmacro_ext cabinets and the
amrTCUAopt and amrTCUBOpt
Features are restricted at the BSS,
this field is not grayed-out.

AMR FR Uplink
Enables and disables Link Adaptation
Link Adaptation
for AMR FR on the uplink.
Enabled
amr_fr_ul_la
_enabled
(OMC-R parameter
name:
AmrFrUlLaEnabled)

Values

Mandatory or
Optional?

0 or 1.

Optional.

0 or 1.
Enabled (1),
Disabled (0).
Default is 1.

Optional.

Continued

68P02901W17-T

8-33
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-14 CELL Detailed View fields, General - AMR full rate grouping (Continued)
Field name/BSS
parameter name

Brief description

Mandatory or
Optional?

Values

AMR FR Downlink
Enables and disables Link Adaptation
Link Adaptation
for AMR FR on the downlink.
Enabled
amr_fr_dl_la
_enabled
(OMC-R parameter
name:
AmrFrDlLaEnabled)

0 or 1.
Enabled (1),
Disabled (0).
Default is 1.

Optional.

AMR Full Rate

Active Codec Set
amr_fr_acs

Allows selection of the Active Codec

Set for AMR Full Rate.
Click to display the Cell<id>AMR
Full Rate Codec Modes window. Click
the required modes to select and
deselect. Click Apply when selection
is complete.
At least one, and up to four modes
can be selected.

0, 1, 3, 4, 6.
Where: 0 = 12.2
kbit/s.
1 = 10.2 kbit/s.
3 = 7.4 kbit/s.
4 = 6.7 kbit/s.
6 = 5.15 kbit/s.
Default is 0, 1, 3,
6.

Optional.

AMR Full Rate

Uplink Threshold 1
amr_fr_uplink_
threshold1
(OMC-R parameter
name:
amr_fr_ul_thr1)

The lower uplink decision threshold

for switching from one codec mode to
another.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 9.

Optional.

AMR Full Rate

Uplink Threshold 2
amr_fr_uplink_
threshold2
(OMC-R parameter
name:
amr_fr_ul_thr2)

The lower uplink decision threshold

for switching from one codec mode to
another.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 14.

Optional.

AMR Full Rate

Uplink Threshold 3
amr_fr_uplink_
threshold3
(OMC-R parameter
name:
amr_fr_ul_thr3)

The lower uplink decision threshold

for switching from one codec mode to
another.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 20.

Optional.

AMR Full
Rate Downlink
Threshold 1
amr_fr_downlink
_threshold1
(OMC-R parameter
name:
amr_fr_dl_thr1)

The lower downlink decision

threshold for switching from one
Codec mode to another.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 19.

Optional.

Continued

8-34

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-14 CELL Detailed View fields, General - AMR full rate grouping (Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

AMR Full
Rate Downlink
Threshold 2
amr_fr_downlink
_threshold2
(OMC-R parameter
name:
amr_fr_dl_thr2)

The lower downlink decision

threshold for switching from one
Codec mode to another.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 24.

Optional.

AMR Full
Rate Downlink
Threshold 3
amr_fr_downlink
_threshold3
(OMC-R parameter
name:
amr_fr_dl_thr3)

The lower downlink decision

threshold for switching from one
Codec mode to another.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 30.

Optional.

AMR Full Rate

Uplink Hysteresis
1
amr_fr_uplink
_hystersis1
(OMC-R parameter
name:
amr_fr_ul_hys1)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Full Rate

Uplink Hysteresis
2
amr_fr_uplink
_hystersis2
(OMC-R parameter
name:
amr_fr_ul_hys2)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Full Rate

Uplink Hysteresis
3
(amr_fr_uplink
_hystersis3
amr_fr_ul_hys3)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Full
Rate Downlink
Hysteresis 1
amr_fr_down
link_hystersis1
(OMC-R parameter
name:
amr_fr_dl_hys1)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

Continued

68P02901W17-T

8-35
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-14 CELL Detailed View fields, General - AMR full rate grouping (Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

AMR Full
Rate Downlink
Hysteresis 2
amr_fr_downlink
_hystersis2
(OMC-R parameter
name:
amr_fr_dl_hys2)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Full
Rate Downlink
Hysteresis 3
amr_fr_downlink
_hystersis3
(OMC-R parameter
name:
amr_fr_dl_hys3)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_fr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Full Rate

The uplink switching threshold
Uplink Threshold 1 applied to frequency hopping
Hopping
channels.
amr_fr_uplink
If only one codec mode has been
_threshold1
selected for amr_fr_acs, this field is
_hopping
set to NULL and is grayed-out.
(OMC-R parameter
name:
amr_fr_ul_thr1Hop)

0 - 63.
Default is 4.

Optional.

AMR Full Rate

The uplink switching threshold
Uplink Threshold 2 applied to frequency hopping
Hopping
channels.
amr_fr_uplink
If only one codec mode has been
_threshold2
selected for amr_fr_acs, this field is
_hopping
set to NULL and is grayed-out.
(OMC-R parameter
name:
amr_fr_ul_thr2Hop)

0 - 63.
Default is 11.

Optional.

AMR Full Rate

The uplink switching threshold
Uplink Threshold 3 applied to frequency hopping
Hopping
channels.
amr_fr_uplink
If only one codec mode has been
_threshold3
selected for amr_fr_acs, this field is
_hopping
set to NULL and is grayed-out.
(OMC-R parameter
name:
amr_fr_ul_thr3Hop)

0 - 63.
Default is 16.

Optional.

Continued

8-36

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-14 CELL Detailed View fields, General - AMR full rate grouping (Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

AMR Full
The downlink switching thresholds
Rate Downlink
applied to frequency hopping
Threshold 1
channels.
Hopping
If only one codec mode has been
amr_fr_downlink
selected for amr_fr_acs, this field is
_threshold1
set to NULL and is grayed-out.
_hopping
(OMC-R parameter
name:
amr_fr_dl_thr1Hop)

0 - 63.
Default is 14.

Optional.

AMR Full
The downlink switching thresholds
Rate Downlink
applied to frequency hopping
Threshold 2
channels.
Hopping
If only one codec mode has been
amr_fr_downlink
selected for amr_fr_acs, this field is
_threshold2
set to NULL and is grayed-out.
_hopping
(OMC-R parameter
name:
amr_fr_dl_thr2Hop)

0 - 63.
Default is 21.

Optional.

AMR Full
The downlink switching thresholds
Rate Downlink
applied to frequency hopping
Threshold 3
channels.
Hopping
If only one codec mode has been
amr_fr_downlink
selected for amr_fr_acs, this field is
_threshold3
set to NULL and is grayed-out.
_hopping
(OMC-R parameter
name:
amr_fr_dl_thr3Hop)

0 - 63.
Default is 26.

Optional.

AMR Full Rate

The Uplink hysteresis applied to
Uplink Hysteresis
frequency hopping channels.
1 Hopping
If only one codec mode has been
amr_fr_uplink
selected for amr_fr_acs, this field is
_hysteresis1
set to NULL and is grayed-out.
_hopping
(OMC-R parameter
name:
amr_fr_ul_hys1Hop)

0 - 15.
Default is 1.

Optional.

AMR Full Rate

The Uplink hysteresis applied to
Uplink Hysteresis
frequency hopping channels.
2 Hopping
If only one codec mode has been
amr_fr_uplink
selected for amr_fr_acs, this field is
_hysteresis2
set to NULL and is grayed-out.
_hopping
(OMC-R parameter
name:
amr_fr_ul_hys2Hop)

0 - 15.
Default is 1.

Optional.

Continued

68P02901W17-T

8-37
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-14 CELL Detailed View fields, General - AMR full rate grouping (Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

AMR Full Rate

The Uplink hysteresis applied to
Uplink Hysteresis
frequency hopping channels.
3 Hopping
If only one codec mode has been
amr_fr_uplink
selected for amr_fr_acs, this field is
_hysteresis3
set to NULL and is grayed-out.
_hopping
(OMC-R parameter
name:
amr_fr_ul_hys3Hop)

0 - 15.
Default is 1.

Optional.

AMR Full
The Downlink hysteresis applied to
Rate Downlink
frequency hopping channels.
Hysteresis 1
If only one codec mode has been
Hopping
selected for amr_fr_acs, this field is
amr_fr_downlink
set to NULL and is grayed-out.
_hysteresis1
_hopping
(OMC-R parameter
name:
amr_fr_dl_hys1Hop)

0 - 15.
Default is 1.

Optional.

AMR Full
The Downlink hysteresis applied to
Rate Downlink
frequency hopping channels.
Hysteresis 2
If only one codec mode has been
Hopping
selected for amr_fr_acs, this field is
amr_fr_downlink
set to NULL and is grayed-out.
_hysteresis2
_hopping
(OMC-R parameter
name:
amr_fr_dl_hys2Hop)

0 - 15.
Default is 1.

Optional.

AMR Full
The Downlink hysteresis applied to
Rate Downlink
frequency hopping channels.
Hysteresis 3
If only one codec mode has been
Hopping
selected for amr_fr_acs, this field is
amr_fr_downlink
set to NULL and is grayed-out.
_hysteresis3
_hopping
(OMC-R parameter
name:
amr_fr_dl_hys3Hop)

0 - 15.
Default is 1.

Optional.

Continued

8-38

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-14 CELL Detailed View fields, General - AMR full rate grouping (Continued)
Field name/BSS
parameter name
AMR Full Rate
Initial Codec Mode
amr_fr_icm
(OMC-R parameter
name:
amr_fr_icm)

Values

Brief description
The initial codec mode (used at the
beginning of a call).
Click to display a list of the modes
selected in the AMR Full Rate Active
Codec Set field (amr_fr_acs). Click
the mode to be the initial codec
mode. If AMR Full Rate Active Codec
Set field (amr_fr_acs) is changed at
a later date and the mode set does
not include the mode selected for
amr_fr_icm, then amr_fr_icm is
set to the highest mode in the new
amr_fr_acs mode set.

0, 1, 3, 4, or 6.
Default is 1.

Mandatory or
Optional?
Optional.

AMR/GSM Half Rate grouping

Table 8-15 describes the fields in the General - AMR/GSM Half Rate grouping of the CELL
Detailed View. Unless otherwise stated, the OMC-R database parameter names are the same as
the BSS database parameter names. Fields in this grouping can be accessed if the AMR Feature
(amrOpt) or the GSM HR Feature (gsmHalfRateOpt is unrestricted (Enabled)) at the BSS.
Fields in this grouping cannot be accessed if the site is not AMR or GSM HR capable, see
Adaptive Multi-Rate (AMR) on page 2-129 for details.

Table 8-15 CELL Detailed View fields, General - AMR/GSM Half Rate grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory
or Optional?

AMR Half Rate

Enabled
amr_half_rate
(OMC-R parameter
name:
amr_hr)

Enables and disables AMR Half Rate

(HR) for the cell. Grayed-out if the
BSS has both the amrTCUAopt and
amrTCUBOpt Features restricted,
and the site contains only M-CELL2
and/or M-CELL6 cabinets. However,
if the site has Horizonmacro and/or
Horizonmacro_ext cabinets and the
amrTCUAopt and amrTCUBOpt
Features are restricted at the BSS, this
field is not grayed-out.

0 or 1.
Enabled (1)
Disabled (0).
Default is 0.

Optional.

AMR HR Uplink Link

Adaptation Enabled
amr_hr_ul_la
_enabled
(OMC-R parameter
name:
AmrHrUlLa
Enabled)

Enables and disables Link Adaptation

for AMR HR on the uplink.

0 or 1.
Enabled (1),
Disabled (0).
Default is 1.

Optional.

Continued

68P02901W17-T

8-39
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-15 CELL Detailed View fields, General - AMR/GSM Half Rate grouping
(Continued)
Field name/BSS
parameter name

Brief description

Mandatory
or Optional?

Values

AMR HR Downlink
Link Adaptation
Enabled
amr_hr_dl_la
_enabled
(OMC-R parameter
name:
AmrHrDlLa
Enabled)

Enables and disables Link Adaptation

for AMR HR on the downlink.

0 or 1.
Enabled (1),
Disabled (0).
Default is 1.

Optional.

AMR Half Rate

Active Codec Set
amr_hr_acs

Allows selection of the Active Codec

Set for AMR Half Rate.
Click to display the Cell<id>AMR Half
Rate Codec Modes window. Click the
required modes to select and deselect.
Click Apply when selection is complete.
At least one, and up to four modes
can be selected. If any RTF serving a
cell has allow_8k_trau set to Yes (1),
the option 7.95 kbit/s (2) cannot be
included in the amr_hr_acs set.

2, 3, 4, 5, 6.
Where:
2 = 7.95 kbit/s.
3 = 7.4 kbit/s.
4 = 6.7 kbit/s.
5 = 5.9 kbit/s.
6 = 5.15 kbit/s.
Default is 4, 5,
6.

Optional.

AMR Half Rate

Uplink Threshold 1
amr_hr_uplink
_threshold1
(OMC-R parameter
name:
amr_hr_ul_thr1)

The lower uplink decision threshold

for switching from one Codec mode to
another.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 22.

Optional.

AMR Half Rate

Uplink Threshold 2
amr_hr_uplink
_threshold2
(OMC-R parameter
name:
amr_hr_ul_thr2)

The lower uplink decision threshold

for switching from one Codec mode to
another.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 28.

Optional.

AMR Half Rate

Uplink Threshold 3
amr_hr_uplink
_threshold3
(OMC-R parameter
name:
amr_hr_ul_thr3)

The lower uplink decision threshold

for switching from one Codec mode to
another.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
No default.

Optional.

Continued

8-40

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-15 CELL Detailed View fields, General - AMR/GSM Half Rate grouping
(Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory
or Optional?

AMR Half Rate

Downlink Threshold
1
amr_hr_downlink
_threshold1
(OMC-R parameter
name:
amr_hr_dl_thr1)

The lower downlink decision threshold

for switching from one Codec mode to
another.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 24.

Optional.

AMR Half Rate

Downlink Threshold
2
amr_hr_downlink
_threshold2
(OMC-R parameter
name:
amr_hr_dl_thr2)

The lower downlink decision threshold

for switching from one Codec mode to
another.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 30.

Optional.

AMR Half Rate

Downlink Threshold
3
amr_hr_downlink
_threshold3
(OMC-R parameter
name:
amr_hr_dl_thr3)

The lower downlink decision threshold

for switching from one Codec mode to
another.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
No default.

Optional.

AMR Half Rate

Uplink Hysteresis 1
amr_hr_uplink
_hysteresis1
(OMC-R parameter
name:
amr_hr_ul_hys1)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Half Rate

Uplink Hysteresis 2
amr_hr_uplink
_hysteresis2
(OMC-R parameter
name:
amr_hr_ul_hys2)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Half Rate

Uplink Hysteresis 3
amr_hr_uplink
_hysteresis3
(OMC-R parameter
name:
amr_hr_ul_hys3)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
No default.

Optional.

Continued

68P02901W17-T

8-41
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-15 CELL Detailed View fields, General - AMR/GSM Half Rate grouping
(Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory
or Optional?

AMR Half Rate

Downlink Hysteresis
1
amr_hr_downlink
_hysteresis1
(OMC-R parameter
name:
amr_hr_dl_hys1)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Half Rate

Downlink Hysteresis
2
amr_hr_downlink
_hysteresis2
(OMC-R parameter
name:
amr_hr_dl_hys2)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Half Rate

Downlink Hysteresis
3
amr_hr_downlink
_hysteresis3
(OMC-R parameter
name:
amr_hr_dl_hys3)

The sum of the associated threshold

and hysteresis is used as the upper
decision threshold for switching the
Codec mode.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
No default.

Optional.

AMR Half Rate

Uplink Threshold 1
Hopping
amr_hr_uplink
_threshold1
_hopping
(OMC-R parameter
name:
amr_hr_ul_thr1
Hop)

The Uplink switching threshold applied

to frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 21.

Optional.

AMR Half Rate

Uplink Threshold 2
Hopping
amr_hr_uplink
_threshold2
_hopping
(OMC-R parameter
name:
amr_hr_ul_thr2
Hop)

The Uplink switching threshold applied

to frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 28.

Optional.

Continued

8-42

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-15 CELL Detailed View fields, General - AMR/GSM Half Rate grouping
(Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory
or Optional?

AMR Half Rate

Uplink Threshold 3
Hopping
amr_hr_uplink
_threshold3
_hopping
(OMC-R parameter
name:
amr_hr_ul_thr3
Hop)

The Uplink switching threshold applied

to frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
No default.

Optional.

AMR Half Rate

Downlink Threshold
1 Hopping
amr_hr_downlink
_threshold1
_hopping
(OMC-R parameter
name:
amr_hr_dl_
thr1Hop)

The Downlink switching threshold

applied to frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 23.

Optional.

AMR Half Rate

Downlink Threshold
2 Hopping
amr_hr_downlink
_threshold
2_hopping
(OMC-R parameter
name:
amr_hr_dl
_thr2Hop)

The Downlink switching threshold

applied to frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
Default is 30.

Optional.

AMR Half Rate

Downlink Threshold
3 Hopping
amr_hr_downlink
_threshold3
_hopping
(OMC-R parameter
name:
amr_hr_dl
_thr3Hop

The Downlink switching threshold

applied to frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 63.
No default.

Optional.

Continued

68P02901W17-T

8-43
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-15 CELL Detailed View fields, General - AMR/GSM Half Rate grouping
(Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory
or Optional?

AMR Half Rate

Uplink Hysteresis 1
Hopping
amr_hr_uplink
_hysteresis1
_hopping
(OMC-R parameter
name:
amr_hr_ul
_hys1Hop)

The Uplink hysteresis applied to

frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Half Rate

Uplink Hysteresis 2
Hopping
amr_hr_uplink
_hysteresis2
_hopping
(OMC-R parameter
name:
amr_hr_ul
_hys2Hop)

The Uplink hysteresis applied to

frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Half Rate

Uplink Hysteresis 3
Hopping
amr_hr_uplink
_hysteresis3
_hopping
(OMC-R parameter
name:
amr_hr_ul
_hys3Hop)

The Uplink hysteresis applied to

frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
No default.

Optional.

AMR Half Rate

Downlink Hysteresis
1 Hopping
amr_hr_downlink
_hysteresis1
_hopping
(OMC-R parameter
name:
amr_hr_dl
_hys1Hop)

The Downlink hysteresis applied to

frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

Continued

8-44

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Table 8-15 CELL Detailed View fields, General - AMR/GSM Half Rate grouping
(Continued)
Field name/BSS
parameter name

Brief description

Values

Mandatory
or Optional?

AMR Half Rate

Downlink Hysteresis
2 Hopping
amr_hr_downlink
_hysteresis2
_hopping
(OMC-R parameter
name:
amr_hr_dl
_hys2Hop)

The Downlink hysteresis applied to

frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
Default is 1.

Optional.

AMR Half Rate

Downlink Hysteresis
3 Hopping
amr_hr_downlink
_hysteresis3
_hopping
(OMC-R parameter
name:
amr_hr_dl
_hys3Hop)

The Downlink hysteresis applied to

frequency hopping channels.
If only one codec mode has been
selected for amr_hr_acs, this field is
set to NULL and is grayed-out.

0 - 15.
No default.

Optional.

AMR Half Rate

Initial Codec Mode
amr_hr_icm
(OMC-R parameter
name:
amr_hr_icm)

The initial codec mode (used at the

beginning of a call).
Click to display a list of the modes
selected in the AMR Half Rate Active
Codec Set field (amr_hr_acs). Click
the mode to be the initial codec mode.
If AMR Half Rate Active Codec Set field
(amr_hr_acs) is changed at a later
date and the mode set does not include
the mode selected for amr_hr_icm,
then amr_hr_icm is set to the highest
mode in the new amr_hr_acs mode
set.

2, 3, 4, 5, or 6.
Default is 4.

Optional.

Half Rate Reserved

Timeslot
hr_res_ts

The maximum number of half rate

capable timeslots to be reserved within
each zone of the cell.

0 - 255
timeslots.
Default is 255.

Optional.

Inner Half Rate

Usage Threshold
inner_hr
_usage_thres
(OMC-R parameter
name:
InnHrUseThres)

The congestion level at which the BSS

allows:

0 - 101%.
Default is 101.

Optional.

Reconfiguration of Half Rate

capable' Full Rate calls to Half
Rate calls in the inner zone.

Assignment of new calls on Half

Rate channels establishing in the
inner zone.
Continued

68P02901W17-T

8-45
Jan 2010

General cell parameter section groupings

Chapter 8: Configuring cells

Table 8-15 CELL Detailed View fields, General - AMR/GSM Half Rate grouping
(Continued)
Field name/BSS
parameter name

Mandatory
or Optional?

Brief description

Values

Reconfigure Full
Rate to Half Rate
reconfig_fr_to_hr
(OMC-R parameter
name:
ReconfigFrToHr)

If the congestion level at the target cell

exceeds this threshold, any existing
Half Rate capable' Full Rate calls
are reassigned to Half Rate traffic
channels. Setting the value to 101
disables reconfiguration.

0 - 101%.
Default is 101.
Setting the
value to 101
effectively
disables
reconfiguration.

Optional.

New Calls Half Rate

new_calls_hr

If the congestion level in the target cell

exceeds this threshold, all new calls
are allocated to Half Rate channels, if
channels are available.
Setting the value to 101 disables
reconfiguration.
Does not apply when the MSC
has specified that rate changes
are not allowed. For example, if
hr_intracell_ho_allowed is set
such that full-rate only is allowed,
new_calls_hr is ignored.

0 - 101%.
Default is 101.
Setting the
value to 101
effectively
disables
reconfiguration.

Optional.

Half Rate Intracell

Handover Allowed
hr_intracell_ho
_allowed
(OMC-R parameter
name:
HrIntHoAllwd)

Enables and disables Intracell

handovers for Half Rate channels
within a cell.

0 - 3.
Default is 0.

Optional.

AMR/GSM Half Rate grouping with GSM Half Rate

Table 8-16 describes the new fields in the General - AMR/GSM Half Rate grouping of the CELL
Detailed View. Unless stated otherwise, the OMC-R database parameter names are the same as
the BSS database parameter names. Fields in this grouping can be accessed if the GSM Half
Rate Feature (gsmHalfRateOpt) is unrestricted (Enabled) at the BSS. If the site is not GSM
Half Rate capable, see GSM Half Rate on page 2-140 for details.

Table 8-16 CELL Detailed View fields, General - AMR/GSM Half Rate grouping
Field name/BSS
parameter name
GSM Half Rate
gsm_half_rate
_enabled
(OMC-R parameter
name:
gsm_hr)

8-46

Brief description
Enables and disables GSM Half Rate
(HR) for the Cell. It is not displayed if
GSM Half Rate Feature is restricted,
or if CIC Validation (cic_validation)
is disabled at the Assoc_RXCDR. It is
grayed-out if the container site is not
AMR or GSM Half Rate capable.

Values
0 or 1.
Enabled (1),
Disabled (0).
Default is 0.

Mandatory or
Optional?
Optional.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

General cell parameter section groupings

Intelligent Selective Paging

Table 8-17 describes the new fields in the General - AMR/GSM Half Rate grouping of the CELL
Detailed View. Unless stated otherwise, the OMC-R database parameter names are the same as
the BSS database parameter names.

Table 8-17 CELL Detailed View fields, General - Intelligent Selective Paging
Field name/BSS
parameter name
{34452} ISP
Enabled
isp_enabled

68P02901W17-T

Brief description
Used to indicate whether the
functionality of Intelligent Selective
Paging is enabled or not.

Values
0 to 1.
Default is 0.

Mandatory or
Optional?
Optional.

8-47
Jan 2010

Handover cell parameter section

Chapter 8: Configuring cells

Handover cell parameter section

Displaying the handover cell parameter section

To display handover cell parameter section, click the Handover button at the top of the CELL
Detailed View.

Handover cell parameter section groupings

The following sections list and briefly describe the parameter groupings and fields in the CELL
Detailed View Handover section. Unless stated otherwise, the OMC-R database parameter
name is the same as the BSS database parameter name. BSS parameters are described in detail
in Technical Description: BSS Command Reference (68P02901W23).

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Handover - General grouping

Table 8-18 describes the fields in the Handover - Handover - General grouping of the CELL
Detailed View.

Table 8-18

CELL Detailed View, Handover - Handover - General grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

BA
Re-Initialization
ba_alloc_proc

Enables or disables the re-initialization

of the active block following a change
in the broadcast control allocation
(BA), and to suspend subsequent
measurements until the new BA is
reported.

Default is
Disabled (0).

Mandatory.

Bounce Protect
HO Margin
bounce_protect
_margin
(OMC-R
parameter name:
bnce_prt_mgn)

Used to prevent continuous handover

bouncing between cells due to RXQUAL
and RXLEV reasons.

0 - 127 Decibels.
Default is 0.

Mandatory.

Continued

8-48

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Handover cell parameter section groupings

Table 8-18 CELL Detailed View, Handover - Handover - General grouping (Continued)
Field name/BSS
parameter name

Mandatory or
Optional?

Brief description

Values

Bounce Protect
Quality Ho Timer
bounce_protect
_qual_tmr
(OMC-R
parameter name:
bnce_prt
_qual_tmr)

Used to prevent continuous handover

bouncing between cells due to RXQUAL
reasons.

0 - 255 (Number
of SACCH
periods).
Default is 0.

Mandatory.

Bounce Protect
Congestion HO
Timer
bounce_protect
_cong_tmr
(OMC-R
parameter name:
bnce_prt_cong
_tmr)

Used to prevent continuous handover

bouncing between cells due to
congestion reasons.

0 - 255 (Number
of SACCH
periods). Default
is 0.

Mandatory.

Mobile Station
HO Power Level
handover_power
_level
(OMC-R
parameter name:
handoverPwr
Level)

The maximum Dedicated Control

Channel (CCH) power level allowed
for an MS after a handover to this
cell. Value range depends on the CELL
frequency_type.

0 - 19, 29 - 31.
Default is 2.

Mandatory.

Minimum
Handover
Recognized
Period
handover
_recognized
_period
(OMC-R
parameter name:
handoverRec
Period)

The threshold for handover interval

when the MSC needs to queue a
handover request.

2 - 64.
Default is 2.

Mandatory.

Handover Margin
Default
ho_margin_def

Used for a neighbor whenever

ho_margin_cell is not defined in the
neighbor object.

-63 to 63 (dB).
Default is 8.

Mandatory.

Generic H/O
margin formula
(0) or Specialized
HO margin
formula (1).
Default is 0.

Mandatory.

Handover Margin The sorting algorithm used to sort the

Usage Flag
neighbor list.
ho_margin
_usage_flag
(OMC-R
parameter name:
ho_mgn_use_flag)
Enable Incoming
Handovers

See Barring calls at a cell on page

8-239 for details.

Mandatory.

Continued

68P02901W17-T

8-49
Jan 2010

Handover cell parameter section groupings

Chapter 8: Configuring cells

Table 8-18 CELL Detailed View, Handover - Handover - General grouping (Continued)
Field name/BSS
parameter name
Hop Count
hop_count

Brief description

Mandatory or
Optional?

Values
0 - 255.
Default is 255.

Mandatory.

Hop Count Timer The number of SACCH periods before

hop_count_timer the CELL hop_count value is reset.

Default is 0.

Mandatory.

Missing
Measurement
Report
missing_rpt

Default is
Disable (0).

Mandatory.

Timing Advance
The interval between timing advance
Period
changes.
timing_advance
_period
(OMC-R
parameter name:
timingAdvPeriod)

0 - 31 (SACCH
multi-frames).
Default is 4.

Mandatory.

Max Disuse Count

based on Hreqave
HO UL/DL with
MS/BSS at Full
Pwr
Nbr Journaling

Default is No (0).

Mandatory.

The number of interference

handovers allowed within a CELL
hop_count_timer period.

Enables or disables the

no_measurement_report flag in
the call block, and to suspend all
measurement processing (store,
averaging, power control, handover) in
the event of a missing measurement
report.

See Configuring a cell for flexible

neighbor cell processing on page 8-195
for further details of these fields.

Handover thresholds grouping

Table 8-19 describes the fields in the Handover - Handover - Thresholds grouping of the CELL
Detailed View.

Table 8-19 CELL Detailed View, Handover - Handover Thresholds grouping

Field name/BSS
parameter name
EGSM Handover
Threshold
egsm_handover
_threshold
(OMC-R
parameter name:
egsm_ho_thresh)

8-50

Brief description
Indicates the range of interference
bands allowed for handing over an
extended mobile using a primary
resource which is needed by a
primary mobile. Only valid if
egsmOpt is unrestricted.

Values
0 - 5.
Default is
Forced HO Not
Allowed (0).

Mandatory or
Optional?
Optional.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Handover cell parameter section groupings

Handover types allowed grouping

Table 8-20 describes the fields in the Handover - Handover - Handover types allowed grouping
of the CELL Detailed View.

Table 8-20 CELL Detailed View, Handover - Handover types allowed grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Downlink Receive
Enables or disables a
Quality Handover
handover due to downlink
dl_rxqual_ho
receive quality (rxqual).
_allowed
(OMC-R parameter
name:
dlRxqualHoAllowed)

Default is Enabled
(1).

Mandatory.

Inter-Cell Handover
inter_cell_handover
_allowed
(OMC-R parameter
name:
interCellHoAllowd)

Disables or enables inter-cell

handovers.

0 - 3.
Default is BSC
Controlled
Handover (1).

Mandatory.

Intra-Cell Handover
intra_cell_handover
_allowed
(OMC-R parameter
name:
intraCellHoAllowd)

Disables or enables intra-cell

handovers.

0 - 2.
Default is BSC
Controlled
Handover (1).

Mandatory.

Default is Enabled
(1).

Mandatory.

Uplink Receive
Enables or disables a
Quality Handover
handover due to uplink
ul_rxqual_ho
receive quality (rxqual).
_allowed
(OMC-R parameter
name:
ulRxqualHoAllowed)

Adaptive handovers grouping

See Configuring a cell for adaptive handovers on page 8-185 for further details of these fields.

Handover Timer grouping

Table 8-21 describes the fields in the Handover - Handover - Handover Timer grouping of the
CELL Detailed View.

68P02901W17-T

8-51
Jan 2010

Handover cell parameter section groupings

Table 8-21

Chapter 8: Configuring cells

CELL Detailed View, Handover - Handover Timer grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

RR_T3105 Timer
rr_t3105

The timer that causes the repetition of

the PHYSICAL INFORMATION message
during the handover procedure.

0 - 200 ms.
Default is 60.

Mandatory.

RR_NY1_REP
Timer
rr_ny1_rep

The threshold for the maximum number

of repetitions for the PHYSICAL
INFORMATION message during a
handover.

0 - 200.
Default is 20.

Mandatory.

RR_T3103 Timer
rr_t3103

The time that the BSS waits for an

internal handover to complete.

0 - 1000000
ms.
Default is
30000.

Mandatory.

Handover
Acknowledgment
Timer
ho_ack

The time that the system waits for

confirmation that the mobile has
accessed the handover' channel.

0 - 1000000
ms.
Default is
5000.

Mandatory.

Uplink RxQual Handover grouping

Table 8-22 describes the fields in the Handover - Uplink RxQual Handover grouping of the
CELL Detailed View.

Table 8-22

CELL Detailed View, Handover - Uplink RxQual Handover grouping

Field name/BSS parameter

name

Brief description

Values

Mandatory or
Optional?

Uplink Receive Quality

HO Bin
decision_1_ul_
rxqual_av_h
(OMC-R parameter name:
dec1UlRxqualAv_h)

The measurement averaging bin

used to generate handover for
uplink receive quality.

0 or 1.
Default is 0.

Mandatory.

Lower Uplink Receive

Quality (HO)
l_rxqual_ul_h

The lower uplink receive quality

handover threshold.

0 - 1810.
Default is 453.

Mandatory.

Decision Algorithm
Parameter N6
decision_1_n6

The parameter n6 in the decision

algorithm in the BSS. N6 is
the number of samples in the
threshold comparison process
used in handover decisions based
on receive signal quality.

1 - 31 (1 range
step = 1 peg).
Default is 1.

Mandatory.

Continued

8-52

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Handover cell parameter section groupings

Table 8-22 CELL Detailed View, Handover - Uplink RxQual Handover grouping
(Continued)
Field name/BSS parameter
name

Mandatory or
Optional?

Brief description

Values

Decision Algorithm
Parameter P6
decision_1_p6

The parameter p6 in the decision

algorithm in the BSS. P6 is the
number of averages that must
exceed a threshold in order for
the handover decisions based on
receive signal quality to be taken.

1 - 31 (1 range
step = 1 peg).
Default is 1.

Mandatory.

Alt Hopping Quality

Thresholds
hop_qual_enabled

Whether the receive quality

parameters for hopping are
enabled.

0 or 1.
Default is
Disabled (0).

Mandatory.

Lower Uplink Rcv Qual

(HO) Hopping
l_rxqual_ul_h_
hopping
(OMC-R parameter name:
lRxqualUlHHopping)

The lower uplink receive quality

handover threshold for hopping.

0 - 1810.
Default is 0.

Optional.

Lower Uplink Rcv Qual

(Pwr) Hopping
l_rxqual_ul_p_hopping
(OMC-R parameter name:
lRxqualUlPHopping)

The lower uplink signal quality

threshold for power control for
hopping in the serving cell.

0 - 1810.
Default is 0.

Optional.

Alt Data Quality

Thresholds
data_qual_flag
(OMC-R parameter name:
data_qual_enabled)

Whether the receive quality

parameters for data will be
enabled.

0 or 1.
Default is
Disabled (0).

Mandatory.

Lower Uplink Rcv Qual

(HO) Data
l_rxqual_ul_h_data
(OMC-R parameter name:
lRxqualUlHData)

The lower uplink receive quality

handover threshold for data
services.

0 - 1810.
Default is 0.

Mandatory.

Lower Uplink Rcv Qual

(Pwr) Data
l_rxqual_ul_p_data
(OMC-R parameter name:
lRxqualUlPData)

The lower uplink signal quality

threshold for power control for
data services in the serving cell.

0 - 1810.
Default is 0.

Mandatory.

68P02901W17-T

8-53
Jan 2010

Handover cell parameter section groupings

Chapter 8: Configuring cells

Downlink RxQual handover grouping

Table 8-23 describes the fields in the Handover - Downlink RxQual handover grouping of the
CELL Detailed View.

Table 8-23 CELL Detailed View, Handover - Downlink RxQual handover grouping
Field name/BSS parameter
name

8-54

Brief description

Values

Mandatory or
Optional?

Downlink Receive
Quality HO Bin
decision_1_dl_rxlev_
av_h
(OMC-R parameter
name:
dec1DlRxlevAv_h)

The measurement averaging bin

used to generate handover for
downlink receive quality.

0 or 1.
Default is 0.

Mandatory.

Lower Downlink Receive

Quality (HO)(OMC-R
parameter name:
l_rxqual_dl_h)

The lower downlink receive

quality handover threshold.

0 - 1810.
Default is 453.

Mandatory.

Lower Downlink Rcv

Qual (Ho) Hopping
l_rxqual_dl_h_hopping
(OMC-R parameter
name:
lRxqualDlHHopping)

The lower downlink receive

quality handover threshold for
hopping.

0 - 1810.
Default is 0.

Optional.

Lower Downlink Rcv

Qual (Pwr) Hopping
l_rxqual_dl_p_
hopping
(OMC-R parameter
name:
lRxqualDlPHopping)

The lower downlink signal

quality threshold for power
control for hopping in the
serving cell.

0 - 1810.
Default is 0.

Optional.

Lower Downlink Rcv

Qual (HO) Data
l_rxqual_dl_h_data
(OMC-R parameter
name:
lRxqualDlHData)

The lower downlink receive

quality handover threshold for
data services.

0 - 1810.
Default is 0.

Mandatory.

Lower Downlink Rcv

Qual (Pwr) Data
l_rxqual_dl_p_data
(OMC-R parameter
name:
lRxqualDlPData)

The lower downlink signal

quality threshold for power
control for data services in the
serving cell.

0 - 1810.
Default is 0.

Mandatory.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Handover cell parameter section groupings

Uplink RxLev handover grouping

Table 8-24 describes the fields in the Handover - Uplink RxLev Handover grouping of the CELL
Detailed View.

Table 8-24

CELL Detailed View, Handover - Uplink RxLev Handover grouping

Field name/
BSS parameter name

Brief description

Values

Mandatory or
Optional?

Uplink Receive Level

Handover
ul_rxlev_ho_allowed
(OMC-R parameter name:
ulRxlevHoAllowed)

Enables or disables a handover

due to uplink receive level
(rxlev).

0 or 1.
Default is
Enabled (1).

Mandatory.

Uplink Signal Strength

HO Bin
decision_1_ul_rxlev_
av_h
(OMC-R parameter name:
dec1UlRxlevAv_h)

The measurement averaging

bin used to generate handover
for uplink signal strength.

0 or 1.
Default is 0.

Mandatory.

Lower Uplink Receive

Level (HO)
l_rxlev_ul_h

The lower uplink receive level

handover threshold.

0 - 63.
Default is 10.

Mandatory.

Decision Algorithm
Parameter N5
decision_1_n5

The parameter n5 in the

decision algorithm in the BSS.
N5 is the number of samples
in the threshold comparison
process used in handover
decisions based on receive
signal level.

1 - 31 (1 range
step = 1 peg).
Default is 1.

Mandatory.

Decision Algorithm
Parameter P5
decision_1_p5

The parameter p5 in the

decision algorithm in the BSS.
P5 is the number of averages
that must exceed a threshold
in order for the handover
decisions based on receive
signal level to be taken.

1 - 31 (1 range
step = 1 peg).
Default is 1.

Mandatory.

68P02901W17-T

8-55
Jan 2010

Handover cell parameter section groupings

Chapter 8: Configuring cells

Downlink RxLev Handover grouping

Table 8-25 describes the fields in the Handover - Downlink RxLev Handover grouping of the
CELL Detailed View.

Table 8-25 CELL Detailed View, Handover - Downlink RxLev Handover grouping
Field name/
BSS parameter name

Brief description

Values

Mandatory or
Optional?

Downlink Receive Level

Handover
dl_rxlev_ho_allowed
(OMC-R parameter name:
dlRxlevHoAllowed)

Enables or disables a handover

due to downlink receive level
(rxlev).

0 or 1.
Default is
Enabled (1).

Mandatory.

Downlink Signal Strength

HO Bin
decision_1_dl_
rxlev_av_h
(OMC-R parameter name:
dec1DlRxlevAv_h)

The measurement averaging bin

used to generate handover for
downlink signal strength.

0 or 1.
Default is 0.

Mandatory.

Lower Downlink Receive

Level (HO)
l_rxlev_dl_h

The lower downlink receive level

handover threshold.

0 - 63.
Default is 10.

Mandatory.

HO to Nbr with Lower

RxLev

See Configuring a cell for flexible

neighbor cell processing on page
8-195 for further details.

Uplink Interference Handover grouping

Table 8-26 describes the fields in the Handover - Uplink Interference Handover grouping of the
CELL Detailed View.

Table 8-26 CELL Detailed View, Handover - Uplink Interference Handover grouping
Field name/BSS parameter
name

Brief description

Values

Mandatory or
Optional?

Interference Handover
interfer_ho_allowed
(OMC-R parameter name:
interferHoAllowed)

Enables or disables handover

due to interference.

0 or 1.
Default is
Enabled (1).

Mandatory.

Uplink Signal
Interference HO Bin
decision_1_ul_
rxlev_av_ih
(OMC-R parameter name:
dec1UlRxlevAv_ih)

The identifier for one of the

RxLevUl_HC instances contained
within the BTS-CELL object
instance.

0 or 1.
Default is 0.

Mandatory.

Continued

8-56

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Handover cell parameter section groupings

Table 8-26 CELL Detailed View, Handover - Uplink Interference Handover grouping
(Continued)
Field name/BSS parameter
name

Mandatory or
Optional?

Brief description

Values

Decision Algorithm
Parameter N7
decision_1_n7

The parameter n7 in the decision

algorithm in the BSS. N7 is
the number of samples in the
threshold comparison process
used in handover decisions based
on interference.

1 - 31 (1 range
step = 1 peg).
Default is 1.

Mandatory.

Decision Algorithm
Parameter P7
decision_1_p7

The parameter p7 in the decision

algorithm in the BSS. P7 is the
number of averages that must
exceed a threshold in order for
the handover decisions based on
interference to be taken.

1 - 31 (1 range
step = 1 peg).
Default is 1.

Mandatory.

Upper Uplink Receive

Interfer Level (HO)
u_rxlev_ul_ih

The upper uplink interference

receive level handover threshold.

0 - 63.
Default is 45.

Mandatory.

Downlink interference handover grouping

Table 8-27 describes the fields in the Handover - Downlink interference handover grouping
of the CELL Detailed View.

Table 8-27 CELL Detailed View, Handover - Downlink Interference Handover grouping
Field name/BSS parameter
name

Brief description

Values

Mandatory or
Optional?

Downlink Signal
Interference HO Bin
decision_1_dl_
rxlev_av_ih
(OMC-R parameter
name:
dec1DlRxlevAv_ih)

The identifier of one of the

RxLevDl_HC instances contained
within the CELL.

0 or 1.
Default is 0.

Mandatory.

Upper DL Receive
Interfere Level (HO)
u_rxlev_dl_ih

The upper downlink interference

receive level handover threshold.

0 - 63.
Default is 45.

Mandatory.

Distance handover grouping

Table 8-28 describes the fields in the Handover - Distance Handover grouping of the CELL
Detailed View.

68P02901W17-T

8-57
Jan 2010

Handover cell parameter section groupings

Chapter 8: Configuring cells

Table 8-28 CELL Detailed View, Handover - Distance Handover grouping

Field name/BSS parameter
name

Brief description

Values

Mandatory or
Optional?

Mobile Station Distance

Handover
ms_distance_allowed
(OMC-R parameter
name:
msDistanceAllowed)

Disables or enables the use

of the distance comparison
process in the handover
decision process.

0 - 1.
Default is
Disabled (0).

Mandatory.

Mobile Station Distance

HO Bin
decision_1_tim_
adv_av_alg
(OMC-R parameter
name:
dec1TimAdvAv_alg)

The measurement averaging

bin used to determine whether
a handover is necessary due to
MS distance.

0 - 1.
Default is 0.

Mandatory.

Mobile Station Maximum

Timing Advance
ms_max_range

The maximum timing advance

between the BTS and the MS.
Set in terms of timing advance
bits.

0 - 219.
Default is 0.

Optional.

Decision Algorithm
Parameter N8
decision_1_n8

The parameter n8 in the decision

algorithm in the BSS. N8 is the
number of samples in the
threshold comparison process
used in handover decisions
based on MS distance.

1 - 31 (1 range
step = 1 peg).
Default is 1.

Mandatory.

Decision Algorithm
Parameter P8
decision_1_p8

The parameter p8 in the decision

algorithm in the BSS. P8 is the
number of averages that must
exceed a threshold in order for
the handover decisions based on
MS distance to be taken.

1 - 31.
Default is 1.

Mandatory.

Power budget handover grouping

Table 8-29 describes the fields in the Handover - Power budget handover grouping of the CELL
Detailed View.

Table 8-29 CELL Detailed View, Handover - Power Budget Handover grouping
Field name/BSS parameter
name
Power Budget Handover
pwr_handover_
allowed
(OMC-R parameter name:
pwrHoAllowed)

Brief description
Disables or enables the use of
the power budget handover.

Values
0 or 1.
Default is
Enabled (1).

Mandatory or
Optional?
Mandatory.

Continued

8-58

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Handover cell parameter section groupings

Table 8-29 CELL Detailed View, Handover - Power Budget Handover grouping
(Continued)
Field name/BSS parameter
name

Brief description

Values

Mandatory or
Optional?

Power Budget HO Bin

decision_1_p_bgt_
rxlev_av_h
(OMC-R parameter name:
dec1PBgtRxlevAv_h)

The measurement averaging

bin used to determine whether
a handover is necessary due to
power budget.

0 or 1.
Default is 0.

Mandatory.

Neighbor Cell Signal

Strength HO Bin
decision_1_ncell_
rxlev_av_h_calc
)(OMC-R parameter
name:
dec1NcellRxlevAvH)

The measurement averaging

bin used to determine whether
a handover is necessary due to
neighbor cell signal strength.

0 or 1.
Default is 0.

Mandatory.

Use Neighbor Power

Budget Hreqave
use_neighbor_
pbgt_hreqave
(OMC-R parameter name:
useNeiPbgtHreqave)

Tells the handover process

whether to use the unique
hreqave value for each neighbor
of a given cell.
Only used if the BSS optional
feature microcellOpt is
unrestricted.

0 or 1.
Default is No
(0).

Optional.

SDCCH handover grouping

Table 8-30 describes the fields in the Handover - SDCCH Handover grouping of the CELL
Detailed View.

Table 8-30 CELL Detailed View, Handover - SDCCH Handover grouping

Field name/
BSS parameter name

Brief description

Values

Mandatory or
Optional?

SDCCH Handover
Allowed
sdcch_ho

Enables or disables handover

on the SDCCH following
the expiration of the RSS
SDCCH handover timer:
sdcch_timer_ho.

0 or 1.
Default is
Enabled (1).

Mandatory.

SDCCH Timer Handover

sdcch_timer_ho

The number of SACCH

multi-frames before handover
on the SDCCH occurs.

1 - 31.
Default is 1.

Mandatory.

Inter-RAT handover grouping

See Inter-Radio Access Technology (Inter-RAT) Handover on page 2-95 for further details of
these fields.

68P02901W17-T

8-59
Jan 2010

Handover cell parameter section groupings

Chapter 8: Configuring cells

Handover - AMR Full Rate grouping

Table 8-31 describes the fields in the Handover - Handover - AMR Full Rate grouping of the
CELL Detailed View. Fields in this grouping can be accessed if the AMR Feature (amrOpt) is
unrestricted (Enabled) at the BSS, or if the site is not AMR capable, see Adaptive Multi-Rate
(AMR) on page 2-129 for details.

Table 8-31 CELL Detailed View, Handover - Handover - AMR Full Rate grouping
Field name/
BSS parameter name

Mandatory or
Optional?

Brief description

Values

AMR FR Lower Uplink

Receive Quality (HO)
l_rxqual_ul_h_
amr_fr
(OMC-R parameter name:
lRxqualUlHAmrFr)

The handover control threshold

for the lower receive quality
uplink. This threshold is
checked to determine if a
handover condition exists.

0 - 1810 BER
or 0 - 7 Qband
units.
Default is 453
BER, or 5
Qband units.

Optional.

AMR FR Lower Uplink

Rcv Qual (HO) Hopping
l_rxqual_ul_h_
hopping_amr_fr
(OMC-R parameter name:
lRxqUlHHopAmrFr)

The handover control threshold

for the lower receive quality
on the uplink for hopping
calls only. This threshold is
checked to determine if a
handover condition exists. This
threshold is enabled using the
Alt Hopping Quality Thresholds
field (hop_qual_enabled).

0 - 1810 BER
or 0 - 7 Qband
units.
Default is 0.

Optional.

AMR FR Lower Downlink

Receive Quality (HO)
l_rxqual_dl_h_amr_fr
(OMC-R parameter name:
lRxqualDlHAmrFr)

The handover control threshold

for the lower received quality
downlink. This threshold is
checked to determine if a
handover condition exists.

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 226
BER or 4 Qband
units.

Optional.

AMR FR Lower Downlink

Rcv Qual (HO) Hopping
l_rxqual_dl_h_
hopping_amr_fr
(OMC-R parameter name:
lRxqDlHHopAmrFr)

The handover control threshold

for the lower receive quality
downlink for hopping calls
only. This threshold is checked
to determine if a handover
condition exists. This threshold
is enabled using the Alt
Hopping Quality Thresholds field
(hop_qual_enabled).

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 0.

Optional.

Handover - AMR/GSM Half Rate grouping

Table 8-32 describes the fields in the Handover - Handover - AMR/GSM Half Rate grouping of
the CELL Detailed View. Fields in this grouping can be accessed if the AMR Feature (amrOpt)
or GSM HR Feature (gsmHalfRateOpt) are unrestricted, see Adaptive Multi-Rate (AMR) on
page 2-129 for details.

8-60

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Handover cell parameter section groupings

Table 8-32 CELL Detailed View, Handover - Handover - AMR/GSM Half Rate grouping
Mandatory or
Optional?

Field name/BSS parameter

name

Brief description

Values

HR Lower Uplink Receive

Qual (HO)
l_rxqual_ul_h_hr
(OMC-R parameter name:
lRxqualUlHHr)

The handover control threshold

for the receive quality uplink.
This threshold is checked
to determine if a handover
condition exists.

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 226
BER or 4 Qband
units.

Optional.

HR Lower Uplink Rcv

Qual (HO) Hopping
l_rxqual_ul_h_
hopping_hr
(OMC-R parameter name:
lRxqUlHHopHr)

The handover control threshold

for the lower receive quality
downlink for hopping calls
only. This threshold is checked
to determine if a handover
condition exists. This threshold
is enabled using the Alt
Hopping Quality Thresholds
field (hop_qual_enabled).

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 226
BER or 4 Qband
units.

Optional.

HR Lower Downlink Rcv

Qual (HO)
l_rxqual_dl_h_hr
(OMC-R parameter name:
lRxqualDlHHr)

The handover control threshold

for the lower receive quality
downlink. This threshold if
checked to determine if a
handover condition exists.

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 226
BER or 4 Qband
units.

Optional.

HR Lower Downlink Rcv

Qual (HO) Hopping
l_rxqual_dl_h_
hopping_hr
(OMC-R parameter name:
lRxqDlHHopHr)

The handover control threshold

for the lower receive quality
downlink for hopping calls
only. This threshold is checked
to determine if a handover
condition exists. This threshold
is enabled using the Alt
Hopping Quality Thresholds
field (hop_qual_enabled).

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 226
BER or 4 Qband
units.

Optional.

{34452} New Calls AMR

HR
new_calls_amr_hr

Used to define the congestion

threshold to indicate at which
congestion level, the new
half-rate capable calls with AMR
HR as the first permitted HR
speech version are assigned as
AMR half-rate calls.

Range is 0 to
101.
Default is 101.

Optional.

{34452} Reconfig FR To
AMR HR
reconfig_fr_to_amr
_hr

Used to indicate that if the

congestion levels in target cell
exceeds the threshold, then
any existing Half Rate Capable
Full-Rate calls with AMR as
the first permitted HR speech
version are reassigned to Half
Rate traffic channels.

Range is 0 to
101.
Default is 101.

Optional.

Continued

68P02901W17-T

8-61
Jan 2010

Handover cell parameter section groupings

Table 8-32
(Continued)

Chapter 8: Configuring cells

CELL Detailed View, Handover - Handover - AMR/GSM Half Rate grouping

Field name/BSS parameter

name
{34452} Inner AMR HR
Usage Threshold
inner_amr_hr_usage
_thres

8-62

Brief description
Used to define the congestion
threshold to indicate at what
congestion level the BSS
software allows the following:

Reconfiguration of
half-rate capable full
rate calls with AMR HR
as the first permitted HR
speech version to AMR
half-rate calls in the inner
zone.

The assignment of new

half rate capable calls
with AMR HR as the first
permitted HR speech
version on half-rate
channels establishing
in the inner zone.

Values
Range is 0 to
101.
Default is 101.

Mandatory or
Optional?
Optional.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Power control cell parameter section

Power control cell parameter section

Displaying the power control cell parameter section

To display the Power Control cell parameter section, click the Power Control button at the top
of the CELL Detailed View.

Power control cell parameter section groupings

The following sections list and briefly describe the parameter groupings and fields in the
CELL Detailed View Power Control section. Unless stated otherwise, the OMC-R database
parameter name is the same as the BSS database parameter name. BSS parameters are
described in detail in Technical Description: BSS Command Reference (68P02901W23).

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Power Control - General

Table 8-33 describes the fields in the Power Control - Power Control - General grouping of the
CELL Detailed View.

Table 8-33 CELL Detailed View, Power Control - Power Control - General grouping
Field name/BSS
parameter name
Maximum Default
Transmit Power
ms_txpwr
_max_def

68P02901W17-T

Brief description
The default value used for a
neighbor cell when the Neighbor
ms_txpwr_max_cell is not defined
in an underlying Neighbor instance.
Values depend on the value of the CELL
frequency_type. (Sets the equation
for evaluating the need for a handover
due to the power budget expression
ms_txpwr_max_cell).

Values
0 - 39.
Default is 0.

Mandatory or
Optional?
Mandatory.

8-63
Jan 2010

Power control cell parameter section groupings

Chapter 8: Configuring cells

Rapid MS Power Down

Table 8-34 describes the fields in the Power Control - Rapid MS Power Down grouping of the
CELL Detailed View.

Table 8-34

CELL Detailed View, Power Control - Rapid MS Power Down grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Rapid Power Down

Procedure
rapid_pwr_down

Enables or disables the rapid MS

power down procedure.

0 or 1.
Default is
Disabled (0).

Mandatory.

Rapid Power Down

Offset
rpd_offset

Specifies the rxlev steps below

the CELL rpd_trigger value.

0 - 63 (number
of dBm below
the trigger
threshold).
Default is 8.

Mandatory.

Rapid Power Down

Period
rpd_period

The number of reports that are

averaged before checking for a
rapid power down situation.

1 - 32.
Default is 2.

Mandatory.

Rapid Power Down

Trigger
rpd_trigger

The minimum power threshold

beyond which the MS is
immediately ordered to a
calculated power level.

0 - 63.
Default is 45.

Mandatory.

Uplink Power Control

Table 8-35 describes the fields in the Power Control - Uplink Power Control grouping of the
CELL Detailed View.

Table 8-35 CELL Detailed View, Power Control - Uplink Power Control grouping
Field name/
BSS parameter name

Brief description

Values

Mandatory or
Optional?

Maximum Mobile Station

Transmit Power
max_tx_ms

The maximum MS output power

which can be used in this cell.

0 and 39.
The default
is the highest
allowed value.

Mandatory.

MS Power Control
ms_power_control_
allowed
(OMC-R parameter name:
msPowerCntlAllowd)

Whether MS power control is

allowed.

0 or 1.
Default is
Enabled (1).

Mandatory.

UL Signal Strength Power

Change Bin
decision_1_ul_
rxlev_av_p
(OMC-R Parameter name:
dec1UlRxlevAv_p)

The measurement averaging

bin number used to generate
power change based on uplink
signal strength.

0 - 1.
Default is 0.

Mandatory.

Continued

8-64

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Power control cell parameter section groupings

Table 8-35 CELL Detailed View, Power Control - Uplink Power Control grouping
(Continued)
Field name/
BSS parameter name

Brief description

Values

Mandatory or
Optional?

UL Receive Quality Power

Change Bin
decision_1_ul_
rxqual_av_p
(OMC-R parameter name:
dec1UlRxqualAv_p)

The measurement averaging

bin number used to generate
power change based on uplink
receive quality.

0 - 1.
Default is 0.

Mandatory.

Lower Uplink Receive

Level (Pwr)
l_rxlev_ul_p

The lower uplink signal strength

threshold for power control in
the serving cell.

0 - 63.
Default is 30.

Mandatory.

Lower Uplink Signal

Quality (Pwr)
l_rxqual_ul_p

The lower uplink signal quality

threshold for power control in
the serving cell.

0 - 1810.
Default is 226.

Mandatory.

Upper Uplink Signal Level

(Pwr)
u_rxlev_ul_p

The upper uplink signal level

threshold for power control of
the serving cell.

0 - 63.
Default is 40.

Mandatory.

Upper Uplink Signal

Quality (Pwr)
u_rxqual_ul_p

The upper uplink signal quality

threshold for power control of
the serving cell.

0 - 1810.
Default is 28.

Mandatory.

Power Increase Step Size

UL
Power Reduction Step
Size UL

See Configuring a cell for power

control optimization on page
8-203 for details of these fields.

MS Power Control
Message Acknowledge
ms_p_con_ack

The minimum time in which an

ordered MS power change must
be confirmed.

0 - 31.
Default is 4
Multiframes (2).

Mandatory.

Mobile Station Power

Control Interval
ms_p_con_interval

The minimum time interval

between successive RF power
change orders to the mobile.

0 - 31.
Default is 4
Multiframes (2).

Mandatory.

MS Power Control
Processing
mspwr_alg

The algorithm used for MS

power control processing.

0 or 1.
Do not use
enhanced
algorithm (0).
Use enhanced
algorithm (1).
Default is 0.

Mandatory.

Mandatory.

Downlink power Control

Table 8-36 describes the fields in the Power Control - Downlink Power Control grouping of
the CELL Detailed View. For further details of optimizing the power control of a cell, see
Configuring a cell for power control optimization on page 8-203.

68P02901W17-T

8-65
Jan 2010

Power control cell parameter section groupings

Chapter 8: Configuring cells

Table 8-36 CELL Detailed View, Power Control - Downlink Power Control grouping
Field name/BSS parameter
name

Brief description

Values

Mandatory or
Optional?

Maximum Transmit
Power for BTS
max_tx_bts

See Establishing a cell boundary

by changing transmit power on
page 8-234 for details.

BTS Power Control

bts_power_control_
allowed
(OMC-R Parameter name:
btsPwrCntlAllowed)

Whether the downlink RF power

control for the BTS-CELL is
allowed.

0 or 1.
Default is
Disabled (0).

Mandatory.

Alt Quality Procedure

alt_qual_proc

Whether the radio link quality

processing is based on Bit Error
Rate (BER) (0) or quality band
(Qband) (1). When changed, the
AltQualProcForm is displayed.

0 or 1.
Default is BER
based (0).

Mandatory.

DL Signal Strength Power

Change Bin
decision_1_dl_
rxlev_av_p
(OMC-R Parameter name:
dec1DlRxlevAv_p)

The measurement averaging bin

number used to generate power
change based on downlink
signal strength.

0 or 1.
Default is 0.

Mandatory.

DL Receive Quality Power

Change Bin
decision_1_dl_
rxqual_av_p
(OMC-R parameter name:
dec1DlRxqualAv_p)

The measurement averaging bin

number used to generate power
change based on downlink
receive quality.

0 or 1.
Default is 0.

Mandatory.

Lower Downlink Receive

Level (Pwr)
l_rxlev_dl_p

The lower downlink signal

strength threshold for power
control in the serving cell.

0 - 63.
Default is 30.

Mandatory.

Lower Downlink Receive

Quality (Pwr)
l_rxqual_dl_p

The lower downlink signal

quality threshold for power
control in the serving cell.

0 - 1810.
Default is 226.

Mandatory.

Upper Downlink Receive

Level (Pwr)
u_rxlev_dl_p

The upper downlink receive

level threshold for power control
of the serving cell.

0 - 63.
Default is 40.

Mandatory.

Upper Downlink Signal

Quality (Pwr)
u_rxqual_dl_p

The upper downlink signal

quality threshold for power
control of the serving cell.

0 - 1810.
Default is 28.

Mandatory.

Decision Algorithm N1 to
N4
decision_1_n1 to 4

Parameters n1 to n4 in the
decision algorithm in the BSS.

1 - 31 (1 range
step = 1 peg).
Default is 1.

Mandatory.

Decision Algorithm P1 to
P4
decision_1_p1 to 4

Parameter p1 to p4 in the
decision algorithm in the BSS.

1 - 31 (1 range
step = 1 peg).
Default is 1.

Mandatory.

Mandatory.

Continued

8-66

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 8-36
(Continued)

Power control cell parameter section groupings

CELL Detailed View, Power Control - Downlink Power Control grouping

Field name/BSS parameter

name

Brief description

Values

Mandatory or
Optional?

Power Increase Step Size

DL
Power Reduction Step
Size DL
Dynamic Step Adjustment
Alg
Factor of Max Pwr
Reduction

See Configuring a cell for power

control optimization on page
8-203 for details of these fields.

BTS Power Control

Acknowledgment
bts_p_con_ack

The minimum time in which

an ordered BTS power change
must be confirmed.

0 - 31.
Default is 2
Multiframes (1).

Optional.

BTS Power Level Changes

Min Interval
bts_p_con_intervl

The minimum amount of time

between successive downlink
power level changes.

0 - 31.
Default is 4
Multiframes (2).

Mandatory.

Mandatory.

Power control - AMR Full Rate

Table 8-37 describes the fields in the Power Control - Power Control - AMR Full Rate grouping of
the CELL Detailed View. Fields in this grouping can be accessed if the AMR Feature (amrOpt)
is unrestricted (Enabled) at the BSS, or if the site is not AMR capable, see Adaptive Multi-Rate
(AMR) on page 2-129 for details.

Table 8-37 CELL Detailed View, Pwr Ctrl - Pwr Ctrl - AMR Full Rate grouping
Field name/BSS parameter
name

Mandatory or
Optional?

Brief description

Values

AMR FR Lower Uplink

Signal Quality (Pwr)
l_rxqual_ul_p_
amr_fr
(OMC-R parameter
name:
lRxqualUlPAmrFr)

The lower uplink limit of

the signal quality of the MS.
This threshold is checked to
determine if the MS power needs
to be increased.

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 226
BER or 4 Qband
units.

Optional.

AMR FR Lower Uplink

Rcv Qual (Pwr) Hopping
l_rxqual_ul_p_
hopping_amr_fr
(OMC-R parameter
name:
lRxqUlPHopAmrFr)

The lower uplink limit of the

signal quality of the serving
cell for hopping calls only.
This threshold is checked to
determine if the BTS power
needs to be increased. This
threshold is enabled using the
Alt Hopping Quality Thresholds
field (hop_qual_enabled).

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 0.

Optional.

Continued

68P02901W17-T

8-67
Jan 2010

Power control cell parameter section groupings

Table 8-37
(Continued)

Chapter 8: Configuring cells

CELL Detailed View, Pwr Ctrl - Pwr Ctrl - AMR Full Rate grouping

Field name/BSS parameter

name

Brief description

Mandatory or
Optional?

Values

AMR FR Lower Downlink

Receive Quality (Pwr)
l_rxqual_dl_p_
amr_fr
(OMC-R parameter
name:
lRxqualDlPAmrFr)

The lower downlink limit of the

signal quality of the serving
cell. This threshold is checked
to determine if the BTS power
needs to be increased.

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 113
BER or 3 Qband
units.

Optional.

AMR FR Lower Downlink

Rcv Qual (Pwr) Hopping
l_rxqual_dl_p_
hopping_amr_fr
(OMC-R parameter
name:
lRxqDlPHopAmrFr)

The lower downlink limit for

the signal quality of the serving
cell for hopping calls only.
This threshold is checked to
determine if the BTS power
needs to be increased. This
threshold is enabled using the
Alt Hopping Quality Thresholds
field (hop_qual_enabled).

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 0.

Optional.

Power control - AMR/GSM Half Rate

Table 8-38 describes the fields in the Power Control - Power Control - AMR/GSM Half Rate
grouping of the CELL Detailed View. Fields in this grouping can be accessed if the AMR Feature
(amrOpt) or GSM HR Feature (gsmHalfRateOpt) is unrestricted, see Adaptive Multi-Rate (AMR)
on page 2-129 for details.

Table 8-38 CELL Detailed View, Pwr Ctrl - Pwr Ctrl - AMR/GSM Half Rate grouping
Field name/BSS parameter
name

Mandatory or
Optional?

Brief description

Values

HR Lower Uplink Signal

Quality (Pwr)
l_rxqual_ul_p_hr
(OMC-R parameter
name:
lRxqualUlPHr)

The lower uplink limit of

the signal quality of the MS.
This threshold is checked to
determine if the MS power needs
to be increased.

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 113
BER or 3 Qband
units.

Optional.

HR Upper Uplink Signal

Quality (Pwr)
u_rxqual_ul_p_hr
(OMC-R parameter
name:
uRxqualUlPHr)

The power control threshold for

the best allowed uplink receive
quality.

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 28
BER or 1 Qband
units.

Optional.

Continued

8-68

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 8-38
(Continued)

Power control cell parameter section groupings

CELL Detailed View, Pwr Ctrl - Pwr Ctrl - AMR/GSM Half Rate grouping

Field name/BSS parameter

name

Brief description

Values

Mandatory or
Optional?

HR Lower Uplink Rcv

Qual (Pwr) Hopping
l_rxqual_ul_p_
hopping_hr
(OMC-R parameter
name:
lRxqUlPHopHr)

The lower uplink limit of the

signal quality of the serving
cell for hopping calls only.
This threshold is checked to
determine if the BTS power
needs to be increased. This
threshold is enabled using the
Alt Hopping Quality Thresholds
field (hop_qual_enabled).

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 113
BER or 3 Qband
units.

Optional.

HR Lower Downlink Rcv

Qual (Pwr)
l_rxqual_dl_p_hr
(OMC-R parameter
name:
lRxqualDlPHr)

The lower downlink limit of the

signal quality of the serving
cell. This threshold is checked
to determine if the BTS power
needs to be increased.

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 113
BER or 3 Qband
units.

Optional.

HR Upper Downlink
Signal Qual (Pwr)
u_rxqual_dl_p_hr
(OMC-R parameter
name:
uRxqualUlHr)

The power control threshold

for the best allowed downlink
receive quality. Values depend
on the type of unit selected.

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 28
BER or 1 Qband
units.

Optional.

HR Lower Downlink Rcv

Qual (Pwr) Hopping
l_rxqual_dl_p_
hopping_hr
(OMC-R parameter
name:
lRxqDlPHopHr)

The lower downlink limit for

the signal quality of the serving
cell for hopping calls only.
This threshold is checked to
determine if the BTS power
needs to be increased. This
threshold is enabled using the
Alt Hopping Quality Thresholds
field (hop_qual_enabled).

0 - 1810 BER,
or 0 - 7 Qband
units.
Default is 113
BER or 3 Qband
units.

Optional.

68P02901W17-T

8-69
Jan 2010

GPRS cell parameter section

Chapter 8: Configuring cells

GPRS cell parameter section

Displaying the GPRS cell parameter section

To display the GPRS cell parameter section, click the GPRS button at the top of the CELL
Detailed View.

Prerequisites for defining GPRS parameters

Before GPRS cell parameters can be defined, the GPRS Feature field (BSS parameter name:
gprsOpt) in the associated BSS Detailed View must be set to Enabled (1). If not, the GPRS
parameters in the CELL Detailed View are grayed-out.

GPRS cell parameter section grouping

Table 8-39 briefly describes the parameter grouping and fields in the CELL Detailed View
GPRS section. These parameters are grayed-out if BSS gprsOpt is restricted (disabled).
Unless stated otherwise, the OMC-R database parameter name is the same as the BSS database
parameter name. BSS parameters are described in detail in Technical Description: BSS
Command Reference (68P02901W23).

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

NOTE
An asterisk (*) next to the field name indicates a propagatable cell parameter (see
Propagating cell parameters on page 8-79 for details). ** indicates parameters that
are only available for propagation if the Network Controlled Cell Reselection Feature
(nccrOpt) is Enabled (1) for the BSS.

8-70

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GPRS cell parameter section grouping

Table 8-39 CELL Detailed View, GPRS grouping

Field name/BSS parameter
name

Brief description

Values

Mandatory
or Optional?

GPRS Enabled
gprs_enabled

Whether a cell supports

GPRS.
Cannot be set to 1, if there is
no reserved PDCH timeslot
in the same cell.

0 or 1.
Default is Disabled
(0).

Optional.

Routing Area Code *

rac

The RAC (Routing Area

Code) which is part of the
GPRS cell identifier.

0 - 255.
Default is null.

Optional.

Routing Area Color *

ra_colour

Specifies that GPRS is

supported in a cell in System
Information messages.

0 - 7.
Default is null.

Optional.

GPRS Intra-Cell HO
Allowed *
gprs_intraho_allwd
(OMC-R parameter name:
gprs_intraho_allw)

Whether intra-cell
handovers can be performed
to free up GPRS PDTCHs
which have been switched to
TCHs.

0 or 1.
Default is Enabled
(1).

Optional.

GPRS Protect Last Time

Slot *
protect_last_ts

Whether the last timeslot

should be protected or not.

0 or 1.
Default is Disabled
(0).

Optional.

Power Offset
Multiplier *
gprs_pc_alpha

Broadcast on the BCCH and

is used as a multiplier of
the power offset in power
control calculations.

0 - 10.
(multiplicative
factor).
Default is 0.

Optional.

C Averaging in Wait State

*
t_avg_w

The number of multiframes

for C averaging in the Wait
state.

0 - 25.
Default is 10.

Optional.

C Averaging in Transfer
Mode *
t_avg_t

The number of multiframes

for C averaging in the
transfer mode.

0 - 25.
Default is 10.

Optional.

Signal Strength
Measurements *
n_avg_i

The number of signal

strength measurements
that must be made for each
filtered interference signal
strength sample.

0 - 15 (number of
radio blocks).
Default is 2.

Optional.

Max MS Count Down

Value *
gprs_bs_cv_max

The maximum count down

value a mobile can use for
uplink RLC data transfer.

0 - 1.
Default is 6.

Optional.

gprs_cr_margin**

The threshold at which the

network shall consider the
PMR received from the MS
as poor.

5 - 40.
Default is 30.

Optional.

MS Counter N3102
Decrement *
gprs_ms_pan_dec

The amount by which to

decrement N3102.

0 - 7.
Default is 1.

Optional.

Continued

68P02901W17-T

8-71
Jan 2010

GPRS cell parameter section grouping

Chapter 8: Configuring cells

Table 8-39 CELL Detailed View, GPRS grouping (Continued)

Field name/BSS parameter
name

Brief description

Mandatory
or Optional?

Values

MS Counter N3102
Increment *
gprs_ms_pan_inc

The amount by which to

increment N3102.

0 - 7.
Default is 1.

Optional.

Max MS Counter N3102*

gprs_ms_pan_max

The maximum value for

N3102.

0 - 7.
Default is 3.

Optional.

gprs_num_pmrs**

Specifies the number of

poor PMRs the network
shall receive before
initiating network controlled
reselection.

1 - 10.
Default is 3.

Optional.

Downlink Power
Measurement
Chan *
gprs_pc_meas_chan
(OMC-R parameter name:
pc_meas_chan)

Whether the MS measures

the received power level
on the downlink for the
purposes of uplink power
control on the BCCH or
PDCH.

0 or 1.
Default is BCCH (0).

Optional.

Max MS Downlink Buffer

*
max_ms_dl_buffer

The maximum size of the

downlink buffer for each
mobile in the cell.

1600 - 20000 octets.

Default is 12000.

Optional.

Max MS Downlink Rate*

max_ms_dl_rate

The maximum rate the SGSN

can transmit data to mobiles
in the cell.

1 - 900.
Default is 900.

Optional.

Reconfig Idle TCH

Threshold *
gprs_reconfig_
thresh_idle_tch
(OMC-R parameter name:
gprs_rec_idle_tch)

The number of idle circuit

switched resources that
must be exceeded before
a switchable timeslot is
reconfigured as a PDTCH.

0 - 5.
Default is 1.

Optional.

BVCI
bvci

A unique ID that identifies a

cell to the SGSN.

2 - 65535.
Default is null.

Optional.

BCCH Blocks Power

Reduction *
gprs_pb

Specifies the power

reduction used by the
BTS on BCCH blocks.

0 - 16.
Default is 1.

Optional.

Max MS Non-DRX Mode

Request Time *
gprs_drx_timer_max
(OMC-R parameter name:
gprs_drx_time_max)

The maximum time allowed

for the MS to request for
Non-DRX mode after packet
transfer mode.

0 - 3 (Seconds).
Default is 0.

Optional.

T3168 *
gprs_t3168

Specifies the two mobile

timers used by the BTS on
BCCH blocks.

500, 1000, 2000, or

4000.
Default is 4000
msecs.

Optional.

Continued

8-72

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GPRS cell parameter section grouping

Table 8-39 CELL Detailed View, GPRS grouping (Continued)

Field name/BSS parameter
name

Brief description

Values

Mandatory
or Optional?

T3192 (SMG24-SMG30) *
gprs_smg30_t3192

Specifies the mobile timers

used by the BTS on BCCH
blocks. Only valid if BSS
smg_gb_vers <= 30.

0, 80, 120, 160, 200,

500, 1000, or 1500.
Default is 500 msecs.

Optional.

T3192 (SMG31) *
gprs_t3192

Specifies the mobile timers

used by the BTS on BCCH
blocks.

0, 80, 120, 160, 200,

500, 1000, or 1500.
Default is 500 msecs.

Optional.

Reserved GPRS Data

Timeslots Switchable
GPRS Data Timeslots*
Switchable PDCHs When
One Carrier Goes OOS
Reserved PDCHs When
One Carrier Goes OOS
Use BCCH Carrier for
GPRS
GPRS Timeslot
Configuration Algorithm*
Maximum GPRS Data
Timeslots per Carrier *
Minimum GPRS Data
Timeslots per Carrier *

See Configuring a cell for

multiple GPRS carriers on
page 8-207 for details of
these fields.

Optional.

Max Number of TS In
Pre-load USF Active
State

See GPRS Interleaving TBFs

on page 2-89 and Enhanced
GPRS One Phase Access
on page 2-113 for further
details of this parameter.

Optional.

PBCCH/PCCCH enabled
pccch_enabled

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Number of PCCCH
Timeslots
bs_pcc_chans

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Number of Blocks
Allocated to PBCCH
bs_pbcch_blks

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Number of PAGCH Blocks

per Multiframe
bs_pag_blks_res

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Number of PRACH Blocks

per Multiframe
bs_prach_blks

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Time Interval for

Scheduling PSI Messages
psi1_repeat_period
(OMC-R parameter name:
psi1_repeat_prd)

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Continued

68P02901W17-T

8-73
Jan 2010

GPRS cell parameter section grouping

Chapter 8: Configuring cells

Table 8-39 CELL Detailed View, GPRS grouping (Continued)

Field name/BSS parameter
name

Brief description

Values

Mandatory
or Optional?

Non-DRX Mode Transfer

Period Duration
pccch_drx_timer_max
(OMC-R parameter name:
pccch_drx_max_t)

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Slots Between Channel

Request
prach_s

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Perstistence Level 1 to 4
persistence_lvl_0
persistence_lvl_1
persistence_lvl_2
persistence_lvl_3

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Retransmissions Allowed
for Radio Priority 1 to 4
prach_mx_retran_0
prach_mx_retran_1
prach_mx_retran_2
prach_mx_retran_3

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Slots to Spread Random

Access Transmission
prach_tx_int

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional

GPRS Minimum Receive

Level
gprs_rxlev_access_min
(OMC-R parameter name:
gprs_rxlev_ac_min)

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

GPRS MS Max Transmit

See PBCCH/PCCCH feature
Power
on page 2-117 for details.
gprs_ms_txpwr_max_cch
(OMC-R parameter
name:
gprs_mx_txpwr_cch)

Optional.

HCS Priority Class

priority_class

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

HCS Signal Strength

hcs_thr

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

GPRS Cell Reselect

Hysteresis
gprs_cell_reselect_
hysteresis
(OMC-R parameter name:
gprs_reselect_hys)

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

C32 Exception Rule

c32_qual

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Continued

8-74

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GPRS cell parameter section grouping

Table 8-39 CELL Detailed View, GPRS grouping (Continued)

Field name/BSS parameter
name

Brief description

Values

Mandatory
or Optional?

C31 Hysteresis
c31_hyst

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Routing Area Reselect

Hysteresis
ra_reselect_hysteresis
(OMC-R parameter name:
ra_reselect_hyst)

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

GPRS Negative C32

Offset
gprs_temporary_offset
(OMC-R parameter name:
gprs_temp_offset)

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

GPRS Penalty Time

gprs_penalty_time

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

GPRS Cell Reselect Offset

gprs_reselect_offset
(OMC-R parameter name:
gprsReselectOffs)

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

3G Cell Threshold for

Multi-RAT MS
qsearch_p

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Allow Search for 3G Cells

search_prio_3g

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

FDD Cell Reselection

Offset
fdd_gprs_qoffset

See PBCCH/PCCCH feature

on page 2-117 for details.

Optional.

Primary PCU
primary_pcu

Identifier of the primary

PCU for this cell.

-1 or 0.
Default is -1
(meaning no primary
PCU site or GPRS
has never been
enabled).

Mandatory.

Current PCU
current_pcu(OMC-R
only parameter)

Displays the identifier of

the current PCU to which
this cell mapped. Cannot be
updated by a user.

-1 to 2.
Default is -1.

Mandatory.

Initial Downlink Coding

Scheme
init_dl_cs

See GPRS and EGPRS

coding schemes on page
2-39 for details.

Optional.

Initial Uplink Coding

Scheme
init_ul_cs

See GPRS and EGPRS

coding schemes on page
2-39 for details.

Optional.

EGPRS Initial Downlink

Coding Scheme
egprs_init_dl_cs

See GPRS and EGPRS

coding schemes on page
2-39 for details.

Optional.

Continued

68P02901W17-T

8-75
Jan 2010

GPRS cell parameter section grouping

Chapter 8: Configuring cells

Table 8-39 CELL Detailed View, GPRS grouping (Continued)

Field name/BSS parameter
name

Brief description

Mandatory
or Optional?

Values

EGPRS Initial Uplink

Coding Scheme
egprs_init_ul_cs

See GPRS and EGPRS

coding schemes on page
2-39 for details.

Optional.

Minimal number of
dynamic PRR blocks

See GPRS and EGPRS

coding schemes on page
2-39 for details.

Optional.

Bit Error Probability

Period
bep_period

BEP filter averaging period

used at the MS for channel
quality measurements.

0 - 10 where:
0 = 1 radio block.
1 = 2 radio blocks.
2 = 3 radio blocks.
3 = 4 radio blocks.
4 = 5 radio blocks.
5 = 7 radio blocks.
6 = 10 radio blocks.
7 = 12 radio blocks.
8 = 15 radio blocks.
9 = 20 radio blocks.
10 = 25 radio blocks.
Default = 0.

Optional.

Bit Error Probability

Period 2
bep_period2

BEP filter averaging period

used at the MS for channel
quality measurements.

0 - 15 where:
0 = 1 radio block.
1 = 2 radio blocks.
2 = 3 radio blocks.
3 = 4 radio blocks.
4 = 5 radio blocks.
5 = 7 radio blocks.
6 = 10 radio blocks.
7 = 12 radio blocks.
8 = 15 radio blocks.
9 = 20 radio blocks.
10 = 25 radio blocks.
10 = 25 radio blocks.
11 = 40 radio blocks.
12 = 55 radio blocks.
13 = 70 radio blocks.
14 = 90 radio blocks.
15 = normal
filtering.
Default = 15.

Optional.

Continued

8-76

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

GPRS cell parameter section grouping

Table 8-39 CELL Detailed View, GPRS grouping (Continued)

Field name/BSS parameter
name

Values

Brief description

TLLI_BLOCK
Indicates whether an RLC
_CHANNE
data block containing the
L_CODINGtlli_blk_coding contention resolution TLLI
field in the RLC data block
header is to be encoded
using:

CS-1 (in GPRS mode)

or MCS-1 in EGPRS
mode

the commanded
modulation and
channel coding
scheme.

Mandatory
or Optional?

0 or 1.
0 = CS-1 for GPRS or
MCS-1 for EGPRS.
1 = commanded
coding scheme.
Default = 0.

Optional.

{34452} GPRS EDGE

Mismatch Sigma
gprs_edge_mismatch
_sigma

Used to set the weight

factor which indicates the
possibility of the EDGE
mobile to be allocated on the
GPRS carrier, or the GPRS
mobile to be allocated on the
EDGE carrier.

0 to 100.
Default is 60.

Optional.

{34452} GPRS ASYM

Mismatch Delta
gprs_asym_mismatch
_delta

Used set the weight factor

between the GPRS only
mobile and the GMSK UL
restricted carrier.

0 to 100.
Default is 10.

Optional.

{34452} EDGE
ASYM Mismatch Cita
edge_asym_mismatch
_cita

Used to set the weight factor

between the EDGE capable
mobiles and UL GMSK
restricted carriers.

0 to 100.
Default is 30.

Optional.

Network Controlled Cell Reselection grouping

Table 8-40 describes the fields in the GPRS - Network Controlled Cell Reselection grouping
of the CELL Detailed View.

Table 8-40

CELL Detailed View fields, GPRS - Ntwk Ctrld Cell Reselection grouping
Mandatory or
Optional?

Field name/
parameter name

Brief description

Bad PMRs
gprs_num_pmrs

See Network Controlled Cell

Reselection on page 2-81 for details.

Optional.

PMR Threshold
gprs_cr_margin

See Network Controlled Cell

Reselection on page 2-81 for details.

Optional.

68P02901W17-T

Values

8-77
Jan 2010

GPRS cell parameter section grouping

Chapter 8: Configuring cells

Quality of Service grouping

See Quality of Service (QoS) on page 2-154 for details of the CELL parameters/fields contained
in this grouping.

8-78

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Propagating cell parameters

Propagating cell parameters

Introduction to propagating cell parameters

Cell parameters can be modified and propagated using the CELL Detailed View. The modified
parameters are first updated at the BSS and, if accepted at the BSS, are then updated in the
MIB. When the modified parameters have been accepted in the MIB, the settings are propagated
to all relevant cells under control of the OMC-R.

Cell parameter propagation options

Modifications to the parameters of the cell can be propagated to:

All cells within the site associated with the selected cell.

All cells within the BSS associated with the selected cell.

All cells within the selected Region.

All cells within the scope of control of the OMC-R whose parent BSCs are running the same
version of BSC software.

Cell propagation parameters

GSM and GPRS cell parameters can be propagated.

GPRS cell propagation parameters

An asterisk (*) next to the field name in GPRS cell parameter section on page 8-70 indicates a
GPRS cell parameter which is propagated.

GSM cell propagation parameters

Table 8-41 shows the GSM cell propagation parameters.

Table 8-41 GSM cell propagation parameters

BSS database parameter name
adap_trigger_rxlev_dl
adap_trigger_rxlev_ul
adap_trigger_rxqual_dl
Continued

68P02901W17-T

8-79
Jan 2010

Cell propagation parameters

Chapter 8: Configuring cells

Table 8-41 GSM cell propagation parameters (Continued)

BSS database parameter name
adap_trigger_rxqual_ul
adap_trigger_hop_rxqual_dl
adap_trigger_hop_rxqual_ul
amr_fr_acs
amr_fr_dl_la_enabled
amr_fr_downlink_threshold1
amr_fr_downlink_threshold1_hopping
amr_fr_downlink_threshold2
amr_fr_downlink_threshold2_hopping
amr_fr_downlink_threshold3
amr_fr_downlink_threshold3_hopping
amr_fr_downlink_hysteresis1
amr_fr_downlink_hysteresis1_hopping
amr_fr_downlink_hysteresis2
amr_fr_downlink_hysteresis2_hopping
amr_fr_downlink_hysteresis3
amr_fr_downlink_hysteresis3_hopping
amr_fr_icm
amr_fr_ul_la_enabled
amr_fr_uplink_hysteresis1
amr_fr_uplink_hysteresis1_hopping
amr_fr_uplink_hysteresis2
amr_fr_downlink_hysteresis2_hopping
amr_fr_downlink_hysteresis3
amr_fr_downlink_hysteresis3_hopping
amr_fr_uplink_threshold1
amr_fr_uplink_threshold1_hopping
amr_fr_uplink_threshold2
amr_fr_uplink_threshold2_hopping
amr_fr_uplink_threshold3
amr_fr_uplink_threshold3_hopping
amr_full_rate_enabled
amr_hr_acs
amr_hr_dl_la_enabled
Continued

8-80

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell propagation parameters

Table 8-41 GSM cell propagation parameters (Continued)

BSS database parameter name
amr_hr_downlink_hysteresis1
amr_hr_downlink_hysteresis1_hopping
amr_hr_downlink_hysteresis2
amr_hr_downlink_hysteresis2_hopping
amr_hr_downlink_hysteresis3
amr_hr_downlink_hysteresis3_hopping
amr_hr_downlink_threshold1
amr_hr_downlink_threshold1_hopping
amr_hr_downlink_threshold2
amr_hr_downlink_threshold2_hopping
amr_hr_downlink_threshold3
amr_hr_downlink_threshold3_hopping
amr_hr_icm
amr_hr_ul_la_enabled
amr_hr_uplink_threshold1
amr_hr_uplink_threshold1_hopping
amr_hr_uplink_threshold2
amr_hr_uplink_threshold2_hopping
amr_hr_uplink_threshold3
amr_hr_uplink_threshold3_hopping
amr_hr_uplink_hysteresis1
amr_hr_uplink_hysteresis1_hopping
amr_hr_uplink_hysteresis2
amr_hr_uplink_hysteresis2_hopping
amr_hr_uplink_hysteresis3
amr_hr_uplink_hysteresis3_hopping
attach_detach
ba_alloc_proc
band_preference
band_preference_mode
blind_search_preference
bounce_protect_cong_tmr
bounce_protect_margin
bounce_protect_qual_tmr
Continued

68P02901W17-T

8-81
Jan 2010

Cell propagation parameters

Chapter 8: Configuring cells

Table 8-41 GSM cell propagation parameters (Continued)

BSS database parameter name
bs_ag_blks_res
bs_pa_mfrms
bs_pag_blks_res
bs_pbcch_blks
bs_pcc_chans
bs_prach_blks
bts_p_con_ack
bts_p_con_interval
c31_hyst
c32_qual
cbch_enabled
ccch_config
ccch_load_period
cell_bar_access_class
cell_bar_access_switch
cell_bar_quality
cell_reselect_hysteresis
cell_reselect_offset
cell_reselect_param_ind
channel_reconfiguration_switch
coincident_mb
coincident_offset
data_qual_enabled
dealloc_inact
decision_1_dl_rxlev_av_h
decision_1_dl_rxlev_av_ih
decision_1_dl_rxlev_av_p
decision_1_dl_rxqual_av_h
decision_1_dl_rxqual_av_p
decision_1_n1-8
decision_1_p1-8
decision_1_tim_adv_av_alg
decision_1_ul_rxlev_av_ih
decision_1_ul_rxqual_av_h
Continued

8-82

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell propagation parameters

Table 8-41 GSM cell propagation parameters (Continued)

BSS database parameter name
decision_1_ncell_rxlev_av_h_calc
decision_1_p_bgt_rxlev_av_h
decision_1_ul_rxlev_av_h
decision_1_ul_rxlev_av_p
decision_1_ul_rxqual_av_p
decision_alg_type
direct_inner_zone_threshold
dl_rxlev_ho_allowed
dl_rxqual_ho_allowed
dr_ho_during_assign
dr_standard_congest
dtx_required
dyn_step_adj_fmpr
emergency_class_switch
en_incom_ho
erc_ta_priority
ex_range_cell
ext_rtry_cand_prd
extended_paging_active
fdd_gprs_qoffset
fdd_qmin
fdd_qoffset
fdd_multirat_reporting
fdd_rep_quant
flow_control_t1
flow_control_t2
full_pwr_rfloss
gprs_par_wait_ind
half_rate_enabled
handover_power_level
handover_recognized_period
hcs_thr
ho_ack
ho_exist_congest
Continued

68P02901W17-T

8-83
Jan 2010

Cell propagation parameters

Chapter 8: Configuring cells

Table 8-41 GSM cell propagation parameters (Continued)

BSS database parameter name
ho_margin_def
ho_margin_usage_flag
hop_count
hop_count_timer
hop_qual_enabled
hopping_support
hr_fr_hop_count
hr_intracell_ho_allowed
hr_res_ts
imrm_dcs1800_weight
imrm_egsm_weight
imrm_force_recalc
imrm_pgsm_weight
imrm_umts_weight
inner_hr_usage_thres
inner_zone_alg
intave
inter_band_ho_allowed
inter_cell_handover_allowed
inter_rat_enabled
interfer_band0-4
interfer_ho_allowed
intracell_handover_allowed
l_rxlev_dl_h
l_rxlev_dl_p
l_rxlev_ul_h
l_rxlev_ul_p
l_rxqual_dl_h
l_rxqual_dl_h_amr_fr
l_rxqual_dl_h_data
l_rxqual_dl_h_hopping
l_rxqual_dl_h_hopping_amr_fr
l_rxqual_dl_h_hopping_hr
l_rxqual_dl_h_hr
Continued

8-84

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell propagation parameters

Table 8-41 GSM cell propagation parameters (Continued)

BSS database parameter name
l_rxqual_dl_p
l_rxqual_dl_p_amr_fr
l_rxqual_dl_p_data
l_rxqual_dl_p_hopping
l_rxqual_dl_p_hopping_amr_fr
l_rxqual_dl_p_hopping_hr
l_rxqual_dl_p_hr
l_rxqual_ul_h
l_rxqual_ul_h_amr_fr
l_rxqual_ul_h_data
l_rxqual_ul_h_hopping
l_rxqual_ul_h_hopping_amr_fr
l_rxqual_ul_h_hopping_hr
l_rxqual_ul_h_hr
l_rxqual_ul_p
l_rxqual_ul_p_amr_fr
l_rxqual_ul_p_data
l_rxqual_ul_p_hopping
l_rxqual_ul_p_hopping_amr_fr
l_rxqual_ul_p_hopping_hr
l_rxqual_ul_p_hr
link_about_to_fail
link_fail
low_sig_thresh
max_number_of_sdcchs
max_q_length_channel
max_q_length_full_rate_channel
max_q_length_sdcch
max_retran
max_tx_bts
max_tx_ms
mb_tch_congest_thresh
min_gprs_ts_per_carrier
missing_rpt
Continued

68P02901W17-T

8-85
Jan 2010

Cell propagation parameters

Chapter 8: Configuring cells

Table 8-41 GSM cell propagation parameters (Continued)

BSS database parameter name
ms_distance_allowed
ms_max_range
ms_p_con_ack
ms_p_con_interval
ms_power_control_allowed
ms_power_offset
ms_txpwr_max_cch
ms_txpwr_max_def
msc_preference
mspwr_alg
multiband_reporting
ncc_of_plmn_allowed
nch_position
neighbor_report_timer
network_control_order
new_calls_hr
number_of_preferred_cells
number_sdcchs_preferred
outer_zone_usage_level
pbgt_mode
pcch_drx_max_t
pcch_enabled
penalty_time
persistence_lvl_1 to 4
pow_inc_step_size_dl
pow_inc_step_size_ul
pow_red_step_size_dl
pow_red_step_size_ul
prach_mx_retran_1 to 4
prach_s
prach_tx_int
priority_class
priortize_microcell
psi1_repeat_prd
Continued

8-86

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell propagation parameters

Table 8-41 GSM cell propagation parameters (Continued)

BSS database parameter name
pwr_handover_allowed
qos_mtbr_i1_dl
qos_mtbr_i1_ul
qos_mtbr_i2_dl
qos_mtbr_i12_ul
qos_mtbr_i13_dl
qos_mtbr_i13_ul
qos_mtbr_be_dl
qos_mtbr_be_ul
qos_mtbr_bg_dl
qos_mtbr_bg_ul
qsearch_c
qsearch_c_initial
qsearch_I
qsearch_p
queue_management_information
ra_reselect_hyst
rach_load_period
rach_load_threshold
radio_link_timeout
rapid_pwr_down
reconfig_fr_to_hr
reestablish_allowed
report_resource_tch_f_high_water_mark
report_resource_tch_f_low_water_mark
res_gprs_pdchs
res_ts_less_one_carrier
retry_cand_period
rf_chan_rel_ack
rpd_offset
rpd_period
rpd_trigger
rpt_bad_qual_mr
rr_ny1_rep
Continued

68P02901W17-T

8-87
Jan 2010

Cell propagation parameters

Chapter 8: Configuring cells

Table 8-41 GSM cell propagation parameters (Continued)

BSS database parameter name
rr_t3101
rr_t3103
rr_t3105
rr_t3109
rr_t3111_sd
rr_t3111_tch
rr_t3212
rxlev_access_min
rxlev_min_def
sdcch_ho
sdcch_need_high_water_mark
sdcch_need_low_water_mark
sdcch_timer_ho
search_prio_3g
serving_band_reporting
stop_dri_tx_time
sw_ts_less_one_carrier
tch_congest_prevent_thres
tch_flow_control
tch_full_need_low_water_mark
tch_usage_threshold
temporary_offset
threshold
timing_advance_period
ts_in_usf_active
tx_integer
u_rxlev_dl_ih
u_rxlev_dl_p
u_rxlev_ul_ih
u_rxlev_ul_p
u_rxqual_dl_h
u_rxqual_dl_p
u_rxqual_dl_p_hr
u_rxqual_ul_h
Continued

8-88

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Propagating cell parameters using the OMC-R GUI

Table 8-41 GSM cell propagation parameters (Continued)

BSS database parameter name
u_rxqual_ul_p
u_rxqual_ul_p_hr
ul_rxlev_ho_allowed
ul_rxqual_ho_allowed
umts_band_preferred
umts_cpich_ec_no_min
umts_cpich_rscp_min
use_bcch_for_gprs
use_derived_ho_power
use_neighbor_pbgt_hreqave
valid_candidate_period
wait_indication_parameters

GSM cell propagation parameters with GSM Half Rate unrestricted

Table 8-42 shows the cell propagation parameters if the Half Rate feature is unrestricted.

Table 8-42 GSM cell propagation parameters with GSM Half Rate unrestricted
BSS database parameter name
gsm_half_rate_enabled

Propagating cell parameters using the OMC-R GUI

To propagate cell parameters to other cells follow these steps:

Procedure 8-5 Propagate cell parameters using the OMC-R

Navigate to the CELL instance button in the Navigation Tree (BSS

BSS instance SITE SITE instance Radio Frequency CELL
CELL instance). If necessary, see Navigating to a network object class
or instance on page 1-28 for further details.

Double-click the required cell instance.

Result: The OMC-R displays the CELL Detailed View form in Monitor
mode.

From the menu bar, select Edit Edit.

Result: This changes the form to Edit mode.
Continued

68P02901W17-T

8-89
Jan 2010

Propagating cell parameters using the OMC-R GUI

Procedure 8-5
4

Chapter 8: Configuring cells

Propagate cell parameters using the OMC-R (Continued)

Modify the parameters that can be propagated. Refer to Propagating

cell parameters on page 8-79 and Table 8-41 for lists of propagatable
parameters.

NOTE
To obtain the relevant information for a parameter, select
Help - On Context from the menu and drag the ? prompt to
the appropriate field and click that field.
A context-sensitive help page is displayed.
5

Select File Save from the menu bar.

Select Options Propagate Cell Parameters from the menu bar and
select the desired scope of propagation (that is, one of the following):

Propagate to site.

Propagate to BSS.

Propagate to Network.

Propagate to Region.

Result: The Cell Parameter Propagation form is displayed as shown in

Figure 8-2.
7

Select the modified parameters from the Do Not Propagate Parameters

list and add them to the Propagate Parameters list using the Add or
Add All buttons.

Select the cells to which the parameters are to be propagated.

NOTE
The Cell Parameter Propagation form has a filter mechanism
to allow display of cells based on Cell Id or Cell name. For
large networks, this is a useful tool for selecting large
groups of cells.
9

Once the parameter and cell lists has been built up and reviewed, click
the Propagate button to commence the propagation.

NOTE
Parameters and/or cells can be cancelled or removed from
the lists by selecting the appropriate buttons.
Result: The progress of the propagation is monitored on the Cell
Parameter Propagation monitor form. This form additionally indicates
whether the cell is a standard cell (Cell) or a Proxy Cell (Proxy).
10

8-90

Click Cancel, to close the monitor form.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Propagating cell parameters using the OMC-R GUI

Figure 8-2 Cell Parameter Propagation form

ti-GSM-CellParameterPropagationform-00800-ai-sw

68P02901W17-T

8-91
Jan 2010

Deleting a cell

Chapter 8: Configuring cells

Deleting a cell

Deleting a cell: overall procedure

Deleting a cell involves many stages, which are detailed in the following overall procedure:

Procedure 8-6 Delete a cell

8-92

Use shutdown_device menu option in the Navigation Tree to stop calls

on the cells by gracefully shutting down the DRIs.
Shut down the non-BCCH DRIs first to prevent the BCCH hopping to
another in service RTF.
Allow 60 seconds to terminate all existing calls.

Delete the required sources/neighbors for the cell.

Using the Navigation Tree, open the Sources/Neighbors form for the
cell to be deleted. Make a note of all the cells which have this cell
as a neighbor.

Remotely log in to the BSS. See Remotely logging in to a BSS site from
the OMC-R on page 1-39 for further details.

Use the del_nei command to remove the cell sources and neighbors.
See Deleting neighbors using the Navigation Tree Delete option on
page 8-131 for further details.

Unconfigure the frequency hopping objects, using the FreqHopSys

Detailed View under the cell using the Navigation Tree.

Use the del_rtf_path command to delete the RTFs from the paths
configured for the site.

If not retaining the cell statistics, for the time taken by the database
management tool to clean out the cell statistics, use the del_CELL
command on the OMC-R (/usr/omc/current/sbin) to delete the entries
in the PM DBMS.
This should be done immediately if unloading statistics to a third party
DBMS, to avoid duplicate LAC-CIs occurring in the third-party reports.

Unconfigure RTFs and DRIs.

This enables the RF hardware to be released.

Delete the cell in the OMC-R GUI. See Deleting a cell using the
OMC-R GUI in this section.

10

Verify that Performance Management reports can no longer be selected

for the cell.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a cell using the OMC-R GUI

Deleting a cell using the OMC-R GUI

Prerequisites
Before deleting a cell, ensure that the cell has been removed from the neighbor lists.

Procedure
To delete the cell using the OMC-R GUI, see the general deletion procedure in Deleting a
network object using the OMC-R GUI on page 1-37.

Deletion of cell algorithms

When a cell is deleted, the associated algorithms are automatically deleted.

68P02901W17-T

8-93
Jan 2010

Defining algorithms

Chapter 8: Configuring cells

Defining algorithms

Introduction to algorithms
When a cell is created, power control and handover algorithms are automatically created under
the CELL object.
If the cell is created using the OMC-R GUI, add_cell, or cmutil, the Algorithm Number field
(BSS parameter name: alg_num) in the algorithm Detailed View form is set to Unused (255),
and may have to be changed. For example, before an RTF or DRI can be created, the Algorithm
Number field (BSS parameter name: alg_num) must be changed from Unused (255) to another
setting.
If the cell was created using the copy/change method, the algorithms have the same settings
as the original cell.
When a cell is deleted, the algorithms are automatically deleted.

Methods for defining algorithms

Algorithm data for cell parameters is defined using:

OMC GUI, see Modifying default algorithms using the OMC-R GUI on page 8-95.

TTY interface, see Modifying default algorithms using the TTY interface on page 8-98.

NOTE
The algorithm data examples shown in these sections are for demonstration
purposes only. Actual values required vary with the number of carriers on
the cell and specific system conditions. For this reason, only use values
recommended by a system engineer.

8-94

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Modifying default algorithms using the OMC-R GUI

Modifying default algorithms using the OMC-R GUI

Overview of algorithm definition

The following algorithms are created with default values when a cell is created:

RelTimAdvHC - provides handover algorithm data for distance.

SurrndCellHC - provides algorithm data for surround cell handovers.

RxlevDlHC - provides handover algorithm data for downlink receive level.

RxlevUlHC - provides handover algorithm data for uplink receive level.

RxlevDlPC - provides power control algorithm data for downlink receive level.

RxlevUlPC - provides power control algorithm data for uplink receive level.

RxqualDlHC - provides handover algorithm data for downlink receive quality.

RxqualUlHC - provides handover algorithm data for uplink receive quality.

RxqualDlPC - provides power control algorithm data for downlink receive quality.

RXqualUlPC - provides power control algorithm data for uplink receive quality.

The default values for these algorithms may have to be modified.

Modifying an algorithm using the OMC-R GUI

To modify an algorithm using the OMC-R GUI, follow these steps:

Procedure 8-7 Modifying an algorithm

1

Navigate to and select an algorithm instance button in the Navigation

Tree as shown in Figure 8-3 (BSS BSS instance SITE
SITE instance Radio Frequency CELL CELL instance
Handover/Power Control algorithm class algorithm instance). If
necessary, see Navigating to a network object class or instance on page
1-28 for further details.
The algorithm instance button changes color.

Select Edit Detailed View from the menu bar. The OMC-R displays
the algorithm Detailed View in Monitor mode.

Select Edit Edit from the menu bar. The Detailed View changes
from Monitor mode to Edit mode.
Continued

68P02901W17-T

8-95
Jan 2010

Algorithm Detailed View fields

Chapter 8: Configuring cells

Procedure 8-7

Modifying an algorithm (Continued)

Modify the information as required. See Algorithm Detailed View

fields for details.

Select File Save from the menu bar to save the new details.

Select File Close from the menu bar to close the Detailed View.

Figure 8-3

Navigation Tree showing navigation to the cell algorithm instance buttons

ti-GSM-NavigationTreeshowingnavigationtothecellalgorithminstancebuttons-00801-ai-sw

Algorithm Detailed View fields

The following sections list and briefly describe the parameter groupings and fields in the cell
algorithm Detailed Views.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

8-96

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Algorithm Detailed View fields

Identification grouping
Table 8-43 describes the fields in the Identification grouping of the Algorithm Detailed View.

Table 8-43 Algorithm Detailed View - Identification grouping

Field name

Brief description

Values

RDN Class

See description in Table 4-1.

Default is the
class, such as
RxqualDlHC.

RDN Instance

See description in Table 3-1.

Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent CELL.

Click to display the parent CELL
Detailed View.

Mandatory or
Optional?

Additional Information
Use the Additional Information window to input any notes relating to this algorithm. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

General grouping
Table 8-44 describes the fields in the General grouping of the Algorithm Detailed View.

Table 8-44 Algorithm Detailed View - General grouping

Mandatory or
Optional?

Field name/BSS
parameter name

Brief description

Algorithm Number
alg_num

The measurement averaging algorithm

number used.

0, 1 or 255.
Unweighted
(0),
Weighted (1),
Unused (255).

Mandatory.

Distance
Averaging Periods
(HREQAVE)
hreqave

The averaging period in terms of

number of SACCH multiframes.

1 - 31.
Default is 4.

Mandatory.

Averaged Results
hreqt

The number of averages to be

performed before making a handover
or power control decision.

1 - 31.
Default is 1.

Mandatory.

Weighting
qual_weight
(OMC-R database
name:
w_qual)

The weight applied to the receive

quality (RX_QUAL) when Discontinuous
Transmission is being used (DTX).

0 - 255.
Default is 1.

Mandatory.

68P02901W17-T

Values

8-97
Jan 2010

Modifying default algorithms using the TTY interface

Chapter 8: Configuring cells

Modifying default algorithms using the TTY interface

Using the chg_cell_element command and parameters

To modify algorithms using the TTY interface, use the chg_cell_element command and the
following database parameters:

rel_tim_adv - provides handover algorithm data for distance.

surround_cell - provides algorithm data for surround cell handovers.

rxlev_dl_ho - provides handover algorithm data for downlink receive level.

rxlev_ul_ho - provides handover algorithm data for uplink receive level.

rxlev_dl_pc - provides power control algorithm data for downlink receive level.

rxlev_ul_pc - provides power control algorithm data for uplink receive level.

rxqual_dl_ho - provides handover algorithm data for downlink receive quality.

rxqual_ul_ho - provides handover algorithm data for uplink receive quality.

rxqual_dl_pc - provides power control algorithm data for downlink receive quality.

rxqual_ul_pc - provides power control algorithm data for uplink receive quality.

Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the chg_cell_element command, parameters, and prompts.

Using chg_cell_element to change algorithms

The format of chg_cell_element when used to change algorithms is as follows:
chg_cell_element <alg_name>, <bin_num> <alg_num> cell <cell_descrip>
For example, the following command sets surround_cell, bin number 0, algorithm number 0,
for cell 0010114, hreqave to four SACCH multiframes, and does not change the value of hreqt:
chg_cell_element surround_cell, 0 0 cell 0 0 1 0 1 1 4
hreqave: 4
hreqt:
COMMAND ACCEPTED

8-98

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Defining hreqave, hreqt, and qual_weight

Defining hreqave, hreqt, and qual_weight

After entering a chg_cell_element command, the system prompts for values for the following
parameters:

hreqave - to define measurement periods.

hreqt - to define the number of measurement results that can be sent in a handover
required message or follow measurements made for a power control decision.

In addition, the four rxqual algorithms permit the definition of qual_weight to set an rxqual
weighting factor for discontinuous transmission (DTx).

NOTE
If the value of <alg_num> is 255 for any of the algorithms, the system does not
prompt for any parameters.

Examples of chg_cell_element commands

In the following example, hreqave is set to 8, meaning eight SACCH multiframes, and hreqt is
left unchanged:
chg_cell_element rxlev_dl_ho, 0 0 cell 3 6 4 1 7 1C3h 1D7h
hreqave: 8
hreqt:
COMMAND ACCEPTED
In the following example, hreqt is set to 4, meaning to four measurements, and hreqave and
qual_weight are left unchanged:
chg_cell_element rxqual_ul_ho, 0 0 cell 3 6 4 1 7 1C3h 1D7h
hreqave:
hreqt:

qual_weight:
COMMAND ACCEPTED
In the following example alg_num is 255, so the system does not prompt for parameters:
chg_cell_element rxlev_dl_ho, 0 255 cell 3 6 4 1 7 1C3h 1D7h
COMMAND ACCEPTED

Description of rel_tim_adv and surround_cell parameters

Table 8-45 describes the chg_cell_element rel_tim_adv and the chg_cell_element
surround_cell commands and their parameters.

68P02901W17-T

8-99
Jan 2010

Example of modifying rel_tim_adv and surround_cell parameters

Chapter 8: Configuring cells

Table 8-45 chg_cell_element rel_tim_adv and chg_cell_element surround_cell

Parameter

Description

Value

chg_cell_element rel_tim_adv:
hreqave

Sets the tim_adv measurement period.

NOTE

1 to 31 = 1
to 31 SACCH
multiframes.

hreqave x hreqt cannot be greater than 32.

hreqt

1 to 31.

Sets the number of tim_adv measurement results

that can be sent in a handover required message.
This should not be set to less than the value for RSS
decision alg 1 n8.

chg_cell_element surround_cell:
hreqave

Sets the surround_cell measurement period.

NOTE

1 to 31 = 1
to 31 SACCH
multiframes.

hreqave x hreqt cannot be greater than 32.

hreqt

1 to 31.

Sets the number of surround_cell measurement

results that can be sent in a handover required
message. This should not be set to less than the value
for RSS decision alg 1 n8.

Example of modifying rel_tim_adv and surround_cell

parameters
Scenario
For the purposes of the following example, assume cell parameters of:

MCC = 364

MNC = 17

LAC = 1C3

CI = 1D7

The GSM cell id input parameter is then: 3 6 4 1 7 1C3h 1D7h (h for hexadecimal).

8-100

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Description of rxlev_dl_ho and rxlev_ul_ho parameters

Procedure
To modify rel_tim_adv and surround_cell parameters, proceed as follows:

Procedure 8-8 Modify rel_tim_adv and surround_cell parameters

1

Remotely log in to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39 for further
details.

Define the handover for distance hreqave and hreqt using the
command:
chg_cell_element rel_tim_adv, 1 0 cell 3 6 4 1 7 1C3h 1D7h
The system then prompts (bold text shows typical user response):
hreqave: 4
hreqt: 2
COMMAND ACCEPTED
Where 4 sets hreqave to four SACCH multiframes, and 2 sets hreqt to
two measurements.

Define the surround cell handover hreqave and hreqt using the
command:
chg_cell_element surround_cell, 1 0 cell 3 6 4 1 7 1C3h 1D7h
The system then prompts (bold text shows typical user response):
hreqave: 8
hreqt: 4
COMMAND ACCEPTED

Description of rxlev_dl_ho and rxlev_ul_ho parameters

Table 8-46 describes the chg_cell_element rxlev_dl_ho and the chg_cell_element
rxlev_ul_ho commands and their parameters.

Table 8-46 chg_cell_element rxlev_dl_ho and chg_cell_element rxlev_ul_ho

Parameter

Description

Value

chg_cell_element rxlev_dl_ho:
hreqave

Sets the rxlev measurement period.

NOTE

1 to 31 = 1
to 31 SACCH
multiframes.

hreqave x hreqt cannot be greater than

32.
Continued

68P02901W17-T

8-101
Jan 2010

Example of modifying uplink and downlink parameters

Chapter 8: Configuring cells

Table 8-46 chg_cell_element rxlev_dl_ho and chg_cell_element rxlev_ul_ho

(Continued)
Parameter

Description

hreqt

Sets the number of rxlev measurement results that

can be sent in a handover required message. This
should not be set to less than the value for RSS
decision alg 1 n8.

Value
1 to 31.

chg_cell_element rxlev_ul_ho:
hreqave

Sets the rxlev measurement period.

NOTE

1 to 31 = 1
to 31 SACCH
multiframes.

hreqave x hreqt cannot be greater than

32.
hreqt

1 to 31.

Sets the number of rxlev measurement results that

can be sent in a handover required message. This
should not be set to less than the value for RSS
decision alg 1 n8.

Example of modifying uplink and downlink parameters

Scenario
For the purposes of the following example, assume cell parameters of:

MCC = 364

MNC = 17

LAC = 1C3

CI = 1D7

The GSM cell id input parameter is then: 3 6 4 1 7 1C3h 1D7h (h for hexadecimal).

8-102

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Example of modifying uplink and downlink parameters

Procedure
To modify uplink and downlink parameters, proceed as follows:

Procedure 8-9 Modify uplink and downlink parameters

1

Remotely log in to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39 for further
details.

Define the downlink receive level for handover hreqave and

hreqtparameters using the command:
chg_cell_element rxlev_dl_ho, 0 0 cell 3 6 4 1 7 1C3h 1D7h
hreqave: 8
hreqt: 4
COMMAND ACCEPTED
Where 8 sets hreqave to eight SACCH multiframes, and 4 sets hreqt
to four measurements.

Repeat step 2 for the two uplink parameters using the

chg_cell_element rxlev_ul_ho command.

Define downlink receive level for power control hreqave and hreqt
parameters using the commands:
chg_cell_element rxlev_dl_pc, 0 0 cell 3 6 4 1 7 1C3h 1D7h
hreqave: 8
hreqt: 4
COMMAND ACCEPTED
Where 8 sets hreqave to eight SACCH multiframes, and 4 sets hreqt
to four measurements.

Repeat step 4 for the two uplink parameters, using the

chg_cell_element rxlev_ul_pc command, but assigning two
multiframes and two measurements. For example:
chg_cell_element rxlev_ul_pc, 0 0 cell 3 6 4 1 7 1C3h 1D7h
hreqave: 2
hreqt: 2
COMMAND ACCEPTED

Define the downlink receive quality for handover hreqave, hreqt, and
(optionally) qual_weight parameters using the commands:
chg_cell_element rxqual_dl_ho, 0 0 cell 3 6 4 1 7 1C3h 1D7h
hreqave: 8
hreqt: 4
qual_weight: 1
COMMAND ACCEPTED
Where 8 sets hreqave to eight SACCH multiframes, 4 sets hreqt to
four measurements, and 1 sets qual_weight to a weighting factor of 1.

Repeat step 6 for the three uplink parameters using the

chg_cell_element rxqual_ul_ho command.
Continued

68P02901W17-T

8-103
Jan 2010

Example of modifying uplink and downlink parameters

Chapter 8: Configuring cells

Procedure 8-9 Modify uplink and downlink parameters (Continued)

8

Define downlink receive quality for power control hreqave, hreqt, and
(optionally) qual_weight parameters using the commands:
chg_cell_element rxqual_dl_pc, 0 0 cell 3 6 4 1 7 1C3h 1D7h
hreqave: 8
hreqt: 4
qual_weight: 1
COMMAND ACCEPTED
Where 8 sets hreqave to eight SACCH multiframes, 4 sets hreqt to
four measurements, and 1 sets qual_weight to a weighting factor of 1.

Repeat step 8 for the three uplink parameters using the

chg_cell_element rxqual_ul_pc command.

Summary
A summary of the input and output for this procedure is as follows:
chg_cell_element rxlev_dl_ho, 0 0 cell 3 6 4 1 7 1C3h 1D7h
8

hreqave:
hreqt:

COMMAND ACCEPTED
chg_cell_element rxlev_ul_ho, 0 0 cell 3 6 4 1 7 1C3h 1D7h
8

hreqave:
hreqt:

COMMAND ACCEPTED
chg_cell_element rxlev_dl_pc, 0 0 cell 3 6 4 1 7 1C3h 1D7h
8

hreqave:
hreqt:

COMMAND ACCEPTED
chg_cell_element rxlev_ul_pc, 0 0 cell 3 6 4 1 7 1C3h 1D7h
2

hreqave:
hreqt:

COMMAND ACCEPTED
chg_cell_element rxqual_dl_ho, 0 0 cell 3 6 4 1 7 1C3h 1D7h
8

hreqave:
hreqt:

qual_weight:

COMMAND ACCEPTED
chg_cell_element rxqual_ul_ho, 0 0 cell 3 6 4 1 7 1C3h 1D7h

8-104

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

hreqave:
hreqt:

Example of modifying uplink and downlink parameters

qual_weight:

COMMAND ACCEPTED
chg_cell_element rxqual_dl_pc, 0 0 cell 3 6 4 1 7 1C3h 1D7h
8

hreqave:
hreqt:

qual_weight:

COMMAND ACCEPTED
chg_cell_element rxqual_ul_pc, 0 0 cell 3 6 4 1 7 1C3h 1D7h
8

hreqave:
hreqt:

qual_weight:

COMMAND ACCEPTED
!logout

68P02901W17-T

8-105
Jan 2010

Neighbors, Sources and Reciprocal Neighbors

Chapter 8: Configuring cells

Neighbors, Sources and Reciprocal Neighbors

Definition: Neighbor
A Neighbor is a cell to which another cell can hand over calls. Information about the cells
which are Neighbors to a cell are held in a cell's Neighbor objects in the OMC-R, and can be
displayed in the cell's Neighbor Detailed Views. For example, CELLB is a Neighbor of CELL A,
so CELL A has a Neighbor object for CELL B.

Definition: source
A Source is an OMC-R only object, which cannot be displayed as a Detailed View. A Source
object contains information about the cell to which a cell is a Neighbor. For example, if CELL
A has CELL B as its Neighbor, then CELL B contains information about CELL A in its Source
object. The Source object of CELLB is then referred to as Source A.

Contents of a Source object

A Source object contains information, such as:

omc_name - the name of the OMC-R where the Source cell resides. The omc_name is set
correctly when a proxy cell synchronization (see Synchronizing all OMC-R proxy cells
within a network on page 8-160 is performed at the OMC-Rs.

name - the name of the CELL pointing to this Source. If the name of the CELL is empty
then the name of the Source is the same as the sourceGsmCellId.

Creation of a source object

After creating a Neighbor, if the neighborGsmCellId exist in the CM MIB as a proxy cell with
a valid omc_name, the CM MIB creates a Source object under the CELL pointed to by the
neighborGsmCellId at the appropriate OMC-R. (The omc_name of the Source is the name of the
OMC-R where the original Neighbor cell was created.)
For example, if CELL A was created at OMC1 and a user creates CELL A as a Neighbor of
CELL B on OMC2, the CM MIB creates the Source object for CELLA at OMC1 containing the
omc_name: OMC2, which is the omc_name where CELL B resides.
If the creation of the Source object fails, an error message is written to the omcaudit log file.

8-106

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Definition: Reciprocal Neighbors

Deletion of a source object

If a Neighbor cell is deleted, whose neighborGsmCellId points to a proxy cell, the CM MIB
deletes the Source object under the CELL pointed to by the neighborGsmCellId at the remote
OMC-R.
For example, if CELL C was created at OMC2 and a CELL C is created as a Neighbor of CELLB
on OMC2 (referred to as Neighbor C), when a user deletes Neighbor C the CM MIB deletes the
Source object for CELLC.
If the deletion of the Source object fails, an error message is written to the omcaudit log file.

Definition: Reciprocal Neighbors

A significant number of cells in a network are Reciprocal Neighbors. This means that if CELL A
is a Neighbor of CELL B, then CELL B is also a Neighbor of CELL A. This means that CELL A
can hand over calls to CELL B and CELL B can hand over calls to CELL A. This is also referred
to as bi-directional.
Reciprocal relationships between cells in an OMC-R can be viewed using the OMC-R GUI
Sources and Neighbors View window.

One-Way Neighbors
If two CELLs are Neighbors of each other, they are said to exhibit neighbor reciprocity.
If cells are not Reciprocal Neighbors, for example if CELL A can hand over to CELL B, but CELL
B cannot hand over to CELL A, this is referred to as One-Way.

Automatic creation of Reciprocal Neighbors

Because most cells in a network are Reciprocal Neighbors, when a user creates a Neighbor, by
default, the OMC-R automatically creates the Reciprocal Neighbor. For example, when CELL B
is defined as the Neighbor of CELL A, the OMC-R assumes that CELL A is also the Neighbor of
CELL B and so create the Reciprocal Neighbor relationship between CELL A and CELL B.
Automatic creation of the Reciprocal Neighbor can be switched off (and on) using the
environment variable: RECIPROCATE_NBR. The default is on (TRUE).
The Reciprocate Neighbor field (OMC-R parameter name: noReciprocal) in the Neighbor
Detailed View form can be set to On or Off and determines whether the OMC-R should
automatically create a Reciprocal Neighbor for this Neighbor. If switched Off, the OMC-R does
not create a Reciprocal Neighbor for this Neighbor, that is, the Neighbor is One-Way only. If
switched On, a Reciprocal Neighbor is always created for this Neighbor.
If the value of RECIPROCATE_NBR is changed, the OMC-R must be stopped and restarted
before the new value takes effect.

68P02901W17-T

8-107
Jan 2010

Automatic creation of Reciprocal Neighbors

Chapter 8: Configuring cells

Example of autocreation of a Reciprocal Neighbor

When a Neighbor (Neighbor B) is created for a cell (CELLA), if RECIPROCATE_NBR is TRUE
and Reciprocate Neighbor field in the Neighbor Detailed View is Yes (1), and a Source object
does not exist under the CELL (CELLB) with the neighborGsmCellId, the OMC-R automatically
creates the Reciprocal Neighbor (Neighbor A) under the CELL (CELLB) pointed to by the
Neighbor, provided the location of the Neighbor CELL is known. The parameters of the
Reciprocal Neighbor (Neighbor A) shall be derived from the starting CELL (CELLA) under which
the original Neighbor was created.
The non-existence of the Source (Source A) indicates that the Neighbor is not already
reciprocated. If Neighbor B is being added to CELL A, and Source B does not exist below CELL
A and Neighbor B exists as a CELL, or exists as a Proxy Cell in the OMC-R with a non-NULL
omc_name, the location of the Neighbor CELL is known. The parameters of the Reciprocal
Neighbor to be created under CELL B shall be derived from CELL A.

8-108

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Viewing Sources, Neighbors and Reciprocals

Viewing Sources, Neighbors and Reciprocals

Introduction to viewing Sources, Neighbors and Reciprocal

Neighbors
Sources, Neighbors, and Reciprocal Neighbors can be displayed for one or more cells using the
Sources and Neighbors View window.
Information displayed in the Sources and Neighbors View window can be:

Displayed by Cell Id (in hexadecimal or decimal) or by Cell Name.

Filtered by MCC, MNC, LAC, or CI for CELL Id or Neighbor CELL id. Also information can
be displayed for non-Reciprocal Neighbors only.

Printed in ASCII format.

Saved to an ASCII file.

The Sources and Neighbors View window can also be used to:

Display Cell, Neighbor or reciprocal Neighbor Detailed View forms for selected entries.

Add a Neighbor, Source or Reciprocal.

Delete a Neighbor, Source or Reciprocal.

Procedure to view Sources, Neighbors and Reciprocal

Neighbors
To view Sources, Neighbors, and Reciprocal Neighbors for one or more cells, follow these steps:

Procedure 8-10 View Sources, Neighbors, and Reciprocal Neighbors for one or more
cells
1

Click the Config Mgt icon on the Front Panel. The OMC-R displays the
Navigation Tree.

Select either the Network, a BSS, SITE or CELL instance in the

Navigation Tree. Alternatively, use the Find option (see OMC-R Online
Help, Network Operations for further information).
Continued

68P02901W17-T

8-109
Jan 2010

Procedure to view Sources, Neighbors and Reciprocal Neighbors

Chapter 8: Configuring cells

Procedure 8-10 View Sources, Neighbors, and Reciprocal Neighbors for one or
more cells (Continued)
3

From the Navigation Tree menu bar, select Config Mgt - Sources and
Neighbors option.
The OMC-R displays the Sources and Neighbors View window in monitor
mode as shown in Figure 8-4. The full title of the window depends on
the scope selected in step 2. For example, if Network is selected the
name of the network is also displayed in the window title. The scrollable
pane on the left-hand side of the window displays a list of cells within
the scope selected at step 2.
For example, if a specific BSS is selected, all cells at each SITE within
the BSS are displayed. The right-hand side of the screen shows
Neighbor parameters.
Use the close/open icon to expand or contract the information displayed
for each BSS or site.
For each CELL, the pane shows the following columns:

CELL - the id of the CELL (gsmCellId).

Neighbor - the cell id of the Neighbor (neighborGsmCellId)

Reciprocal - the Reciprocal cell id (sourceGsmCellId). The

Reciprocal cell id is the Source cell id.
If a Neighbor does not exist for a cell, None is displayed in the
Neighbor column. If a cell has multiple Neighbors/Sources,
multiple entries are displayed in the list for the same CELL
gsmCellId. If a Source object does not exist for a cell, and the
Neighbors Reciprocate Neighbor field is set to Yes (1), None is
displayed in the Reciprocal column. If an entry has both a Source
and Neighbor present, but the Neighbors Reciprocate Neighbor
field is set to No (0), the OMC-R sets the value of the Reciprocate
Neighbor field to Yes (1). If a Source object does not exist for a cell,
and Neighbors Reciprocate Neighbor field is set to No (0), One Way
is displayed in the Reciprocal column. For example, the following
entry indicates that CELL 001-01-1-1 has CELL 001-01-1-4 as a
Neighbor, but CELL 001-01-1-4 does not have 001-01-1-1 as its
Neighbor:
CELL

Neighbor

Reciprocal

001-01-1-1

None

001-01-1-4

If the cell or Neighbor does not exist, the appropriate error message is
displayed in the status bar.

8-110

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Procedure to view Sources, Neighbors and Reciprocal Neighbors

Displaying cell names instead of cell ids

By default, cell ids are displayed in the Sources and Neighbors View window. To display cell
names: select View CELL name from the menu bar.
The OMC-R displays the names of the cells and Neighbors in the form.

Displaying cell ids in hexadecimal

By default, cell ids are displayed in decimal format. To display cell ids as hexadecimal values in
the Sources and Neighbors View window, follow these steps:

Procedure 8-11 Display cell ids as hexadecimal values

68P02901W17-T

Select View CELL Id from the menu bar.

Select HEX to display cell ids in hexadecimal format.

Select a CELL id displayed in the left-hand pane to display the Cell

Name, GSM Cell Id, BSIC and BCCH in the fields across the top of the
window.
The OMC-R also displays information for the Neighbor of the selected
cell in the right-hand side of the screen, such as, Ho Margin, Cell
Condition, BSIC, BCCH Frequency number, Ba type.
If an entry is not selected, or if multiple entries are selected, or if an
entry without any Neighbors is selected, default values are displayed
for all Neighbor parameters.

8-111
Jan 2010

Procedure to view Sources, Neighbors and Reciprocal Neighbors

Figure 8-4

Chapter 8: Configuring cells

Sources and Neighbors View window in Monitor mode

ti-GSM-SourcesandNeighboursViewwindowinMonitormode-00802-ai-sw

Filtering the displayed information

To filter the information displayed in the form, follow these steps:

Procedure 8-12 Filtering the displayed information

1

Enter a value in one or more of the fields: MCC, MNC, LAC or CI at the
bottom of the screen. These fields are grayed-out if the form displays
a single CELL instance only, or if cells are displayed using the cell
name format.

Select Filter - by CELL Id to display only the entries where the CELL
gsmCellId conforms to the information entered at step 1. This option is
grayed-out if the form displays a single CELL instance only, or if cells
are displayed using the cell name format.

Select Filter - by Neighbor CELL Id to display only the entries where

the Neighbor gsmCellId conforms to the information entered at step 1.
This option is grayed-out if the form displays a single CELL instance
only, or if cells are displayed using the cell name format.
Continued

8-112

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Procedure to view Sources, Neighbors and Reciprocal Neighbors

Procedure 8-12

Filtering the displayed information (Continued)

Select Filter - Display Non Reciprocal neighbors to display only the

entries where Neighbor relationship is not reciprocated.

Select Filter - All to undo all filters and return to the default display,
which is to display a complete list of CELLS, Neighbors and Reciprocals
for the scope selected in step 2.

Opening a related Detailed View window

To from the Sources and Neighbors View window, follow these steps:

Procedure 8-13 Open a CELL, Neighbor or Reciprocal Detailed View window

1

Highlight a cell in the cell information pane.

Select either Edit Open CELL Detailed View, Edit Open Neighbor
Detailed View, or Edit Open Reciprocal Detailed View from the menu
bar. The OMC-R displays the appropriate Cell, Neighbor or Reciprocal
Neighbor Detailed View window for the selected cell.
For example, in the following situation if Edit Open Reciprocal
Detailed View is selected, a Neighbor Detailed View opens under
CELLB with the Neighbor ID field set as A.
CELL

Neighbor

Reciprocal

If the cell or Neighbor does not exist, the appropriate error message is
displayed in the status bar.
3

Close the Detailed View.

Printing specific information in the window

To print, in ASCII format, specific information displayed in, follow these steps:

Procedure 8-14 Print specific information in Sources and Neighbors View window
1

Highlight the information to be printed in the Sources and Neighbors

View.

Select File Print Selected from the menu bar.

Printing all information in the window

To print, in ASCII format, all the information displayed in the Sources and Neighbors View
window, select File Print All from the menu bar.

68P02901W17-T

8-113
Jan 2010

Procedure to view Sources, Neighbors and Reciprocal Neighbors

Chapter 8: Configuring cells

Saving specific information in the window to an ASCII file

To save specific information in the Sources and Neighbors View window to an ASCII file, follow
these steps:

Procedure 8-15 Save specific information in Sources and Neighbors View window
1

Highlight the required information.

Select File Save Selected from the menu bar. The File Selection
window is displayed.

Enter the name of the file and the directory to which the selected
information is to be saved.

Saving all information in the window to an ASCII file

To save all the information in the Sources and Neighbors View window to an ASCII file, follow
these steps:

Procedure 8-16

Save all information in Sources and Neighbors View window

Select File Save All from the menu bar. The File Selection window
is displayed.

Enter the name of the file and the directory to which the selected
information is to be saved.

Closing the window

To close the Sources and Neighbors View window, select File Close from the menu bar.

8-114

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating and deleting Sources, Neighbors and Reciprocals

Creating and deleting Sources, Neighbors and

Reciprocals

Introduction to creating and deleting Sources, Neighbors and

Reciprocals
Use the Sources and Neighbors View window to perform the following activities:

Create missing Sources and Neighbors for all CELLs in the Sources and Neighbors View.
Missing Sources are only created for cells with an entry of None in the Reciprocal column.
If One Way is displayed in the Reciprocal column, missing Sources are not created.

Create missing Sources and Neighbors for CELLs selected in the Sources and Neighbors
View.

Create a Neighbor for a selected CELL, which has a Source but does not have a Neighbor.

Create a Source for a selected CELL.

Delete a Neighbor for a selected CELL.

Delete a Reciprocal Neighbor (and Source) for a selected CELL.

A new Source cannot be created for a CELL unless a Neighbor exists for the cell. When adding
Sources and Neighbors manually, the Neighbor has to be created first.

Creating missing Sources and Neighbors for all Cells

To create Sources and Neighbors for all cells using the Sources and Neighbors View, follow
these steps:

Procedure 8-17 Create Sources and Neighbors for all cells

1

Display the Sources and Neighbors View window for the required
scope.

If necessary, use the filter fields and options to display the required
cells.
Continued

68P02901W17-T

8-115
Jan 2010

Creating missing Sources and Neighbors for all Cells

Chapter 8: Configuring cells

Procedure 8-17 Create Sources and Neighbors for all cells (Continued)
3

Select Config Mgt - Reciprocate All from the menu bar.

Result: The OMC-R displays the progress of the Reciprocate All
process in the status bar and a prompt to select the power budget
algorithm is displayed (as shown in Figure 8-5).

NOTE
The power budget algorithm grouping is shown in Power
Budget Algorithm grouping on page 8-125.
4

To select the power budget algorithm, click Yes.

Result: The Neighbor Detailed View Reciprocate form is displayed as
shown in Figure 8-6 - go to step 5.
To select the default power budget algorithm, click No and go to step 7.

NOTE
By selecting No, the power budget algorithm is set to 1
(Conventional GSM PBGT).
5

Enter the power budget algorithm type in the Power budget

Algorithm Type field.
Result: The other fields in the form are populated according to the
type of power budget algorithm selected.

Select Create Reciprocal Neighbour(s) from the File pull-down

menu.
Result: The power budget algorithm as set in the Neighbor Detailed
View Reciprocate form shall be used.

Close the window.

Figure 8-5

Power budget algorithm prompt

ti-GSM-Powerbudgetalgorithmprompt-00803-ai-sw

8-116

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Figure 8-6

Creating missing Sources and Neighbors for selected Cells

Neighbor Detailed View Reciprocate form

ti-GSM-NeighbourDetailedViewReciprocateform-00804-ai-sw

Creating missing Sources and Neighbors for selected Cells

To create Sources and Neighbors for specific cells only, using the Sources and Neighbors View,
follow these steps:

Procedure 8-18 Create Sources and Neighbors for specific cells only
1

Display the Sources and Neighbors View window for the required
scope.

If necessary, use the filter fields and options to display the required
cells.

Select the cell or cells for which Sources are to be created.

Continued

68P02901W17-T

8-117
Jan 2010

Creating a neighbor for a selected cell

Chapter 8: Configuring cells

Procedure 8-18 Create Sources and Neighbors for specific cells only (Continued)
4

Select Config Mgt - Reciprocate from the menu bar.

Result: The OMC-R displays the progress of the Reciprocate process
in the status bar and a prompt to select the power budget algorithm is
displayed (as shown in Figure 8-5).

Follow step 4 through step 7 in Creating missing Sources and

Neighbors for all Cells on page 8-115.

Creating a neighbor for a selected cell

To create a Neighbor for specific cells only, using the Sources and Neighbors View, follow
these steps:

Procedure 8-19 Create a Neighbor for specific cells only

1

Display the Sources and Neighbors View window for the required
scope.

If necessary, use the filter fields and options to display the required
cells.

Select the cell for which a neighbor is to be created.

Select Config Mgt - Add Neighbor from the menu bar. The OMC-R
displays a Neighbor Detailed View form in Create mode. If the
selected CELL has a source but does not have a Neighbor, the
neighborGsmCellId is initialized from the cell id of the source.

If the selected cell does not have a reciprocal inconsistency or if it had

a missing source, enter the neighborGsmCellId. A new entry is added
to the cell's neighbor List.
The OMC-R updates the Sources and Neighbors View window
accordingly.

Close the window.

Creating a Source for a selected cell

To create a Source for specific cells only, using the Sources and Neighbors View, follow these
steps:

Procedure 8-20

Create a Source for specific cells only

Display the Sources and Neighbors View window for the required
scope.

Select the cell for which a source is to be created.

Continued

8-118

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a neighbor for a cell

Procedure 8-20 Create a Source for specific cells only (Continued)

3

Select Config Mgt - Add Reciprocal from the menu bar. If the selected
cell does not have a source and if the neighbor cell exists in the
same OMC-R, the OMC-R displays a Neighbor Detailed View form in
Create mode with the Neighbor cell as the parent, and its parameters
initialized from the starting cell. For example, if CELL A has Neighbor
B but no source, and CELL B exists in the OMC-R, the Neighbor
Detailed View displays its parent as CELL B and the neighborGsmCellId
and all other parameters are derived from Cell A.
If the selected entry displays a valid Cell Id, name, or On Way in the
Reciprocal column, an error message is displayed in the status bar.
The OMC-R updates the Sources and Neighbors View window
accordingly.

Close the window.

Deleting a neighbor for a cell

To delete a neighbor for specific cells only, using the Sources and Neighbors View, follow these
steps:

Procedure 8-21 Delete a Neighbor for specific cells only

1

Display the Sources and Neighbors View window for the required
scope.

Select the cell or cells for which neighbors are to be removed.

Select Config Mgt - Remove Neighbor from the menu bar. The OMC-R
deletes the Neighbors for the highlighted cells and updates the Sources
and Neighbors View window accordingly.

Close the window.

Deleting a reciprocal neighbor for a cell

To delete a Reciprocal Neighbor, using the Sources and Neighbors View, follow these steps:

Procedure 8-22 Delete a reciprocalneighbour for specific cells only

1

Display the Sources and Neighbors View window for the required
scope.

Select the cell or cells for which reciprocal neighbors are to be

removed.
Continued

68P02901W17-T

8-119
Jan 2010

Deleting a reciprocal neighbor for a cell

Chapter 8: Configuring cells

Procedure 8-22 Delete a reciprocalneighbour for specific cells only (Continued)

8-120

Select Config Mgt - Remove Source from the menu bar. The
OMC-R deletes the selected reciprocal neighbors (and therefore the
corresponding sources) for the highlighted cells and updates the
Sources and Neighbors View window accordingly.

Close the window.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating neighbors using Neighbor Detailed View

Creating neighbors using Neighbor Detailed View

Introduction to creating neighbors using the Detailed View

A neighbor can be created using:

Sources and Neighbors View, see Creating and deleting Sources, Neighbors and
Reciprocals on page 8-115 for further details.

Neighbor Detailed View. The neighbor propagation feature allows the operator to specify
the gsmCellId and initialize the Neighbor Detailed View. The Neighbor Detailed View then
inherits Neighbor parameters from the cell, or proxy cell, if they exist in the same OMC-R.

This section describes how to create a Neighbor for a cell using the Neighbor Detailed View.

Neighbor Detailed View fields

The following sections list and briefly describe the parameter fields in the Neighbor Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

Identification grouping
Table 8-47 describes the fields in the Identification grouping of the Neighbor Detailed View.

Table 8-47 Neighbor Detailed View fields - Identification grouping

Field name/OMC-R
parameter name
Name

Brief description
The textual name of the
neighbor.

Values
Up to 31 characters plus the
NULL character.

Mandatory or
Optional?
Optional.

Continued

68P02901W17-T

8-121
Jan 2010

Neighbor Detailed View fields

Chapter 8: Configuring cells

Table 8-47 Neighbor Detailed View fields - Identification grouping (Continued)

Field name/OMC-R
parameter name
Neighbor GSM
Cell Identifier
NeighborGsm
CellId

Brief description

Values

The GSM cell id of the

neighboring cell. The
subfields MCC and MNC
can be edited in create
mode. The MCC and MNC
fields cannot be edited for
n-1 or n-2 BSS.

There are two types of

GSM cell ID input format;
seven elements or four
elements. The format used
is set with the GSM Cell ID
Format (mmi_cell_id_format)
parameter. See Technical

Mandatory or
Optional?
Mandatory.

Description: BSS Command

Reference (68P02901W23)
for further details of GSM
Cell Id formats.
Neighbor
Template

Name of the Neighbor

template used when
creating the neighbor.

RDN Class

See description in
Table 3-1.

RDN Instance

See description in
Table 3-1.

NMC RDN Value

See description in
Table 4-1.

Cell Condition

The condition of the

CELL pointed to by
NeighborGsmCellId.

Mandatory.

0 - 3.
Cell Does Not Exist (0), Cell
Exists Under Same site (1),
Cell Exists Under Different
site (2), Proxy Cell 3).

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this Neighbor. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

8-122

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Neighbor Detailed View fields

General grouping
Table 8-48 describes the fields in the General grouping of the Neighbor Detailed View.

Table 8-48

Neighbor Detailed View fields - General grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Base Station
Identity Code
(BSIC)

The Base Station Identity Code (BSIC)

of the neighbor cell.

0 - 63.

Mandatory.

BCCH Frequency
(ARFCN)

The Absolute Radio Frequency Channel

Number of the neighbor cell's BCCH.

0 - 124,
512 - 885,
975 - 1023.

Mandatory.

BA Type

The Neighbors ba_type. Determines

whether the neighbor is included in
the bcch allocation table for System
Information messages sent on the
BCCH, SACCH, and/or GPRS.

BCCH, SACCH,
and/or GPRS.

Mandatory.

Frequency Type

The single frequency band capability

of a Neighbor.

PGSM900 (1),
EGSM900 (2),
DCS1800 (4),
PCS1900 (8).

Mandatory.

Handover Margin
Cell

The amount by which the received

signal strength from the neighboring
cell must exceed that from the source
cell to request handover.

-63 to 63 dB.

Optional.

Rxqual Handover
This margin is applied to the power
Margin
budget (PBGT) calculation when the
ho_margin_rxqual handover cause is RXQUAL.

-63 to 63 dB.

Optional.

Rxlev Handover
Margin
ho_margin_rxlev

This margin is applied to the power

budget (PBGT) calculation when the
handover cause is RXLEV.

-63 to 63 dB.

Optional.

Mobile Station
Maximum
Transmit Power

The maximum power level an MS can

use in the neighbor cell. Used for the
power budget equation.

0 - 39.

Optional.

Placement

Whether the neighbor cell is within the

same BSS as the originating cell.

Internal (0) or
External (1).

Minimum Call
Receive Level

The minimum rxlev of the neighbor

required for an MS to handover to the
neighbor cell.

0 - 63.

Optional.

Synchronized

Whether the neighbor cell is

synchronized with the present cell.

No (0) or Yes
(1).

Optional.

Mandatory.

Continued

68P02901W17-T

8-123
Jan 2010

Neighbor Detailed View fields

Table 8-48

Chapter 8: Configuring cells

Neighbor Detailed View fields - General grouping (Continued)

Field name/BSS
parameter name

8-124

Mandatory or
Optional?

Brief description

Values

Adjacent Channel
Interference Test
adj_chn_intf_test
(OMC-R
parameter name:
adj_chn_intf_tst)

Whether the Adjacent Channel

Interference Test is enabled. If a call
is handed over from a serving cell to
a neighbor cell which has a type 7
neighbor, it is possible that the call can
be dropped due to high interference
from the adjacent channel. To avoid
this, the adjacent channel interference
avoidance test can be performed before
handing over a call to a neighbor.
Only used if the BSS Optional Feature
microcellOpt is unrestricted.

Disabled (0) or
Enabled (1).
Default is 0.

Optional.

Adjacent Channel
Receive Level
Difference
adj_chan_rxlev_dif
(OMC-R
parameter name:
adj_chn_rxlev_dif)

The Receive Level Difference for the

Adjacent Channel Interference Test.
Only valid when adj_chn_intf_test is
enabled. Only used if the BSS Optional
Feature microcellOpt is unrestricted.

-63 to 63.

Optional.

Neighboring
Range

If the neighbor is an extended range

neighbor.

Normal range
area (0),
Extended range
area (1).

Optional.

Neighbor Adapt
Pbgt HO Trigger

Used as a threshold when using the

adaptive power budget handover
algorithm on a per neighbor basis.

0 - 255.

Optional.

Reciprocate
Neighbor

Whether a reciprocal neighbor is

created while creating the neighbor.
If set to Enabled (1) and environment
variable RECIPROCATE_NBR is set to
TRUE, then a reciprocal neighbor is
created.

0 or 1.
Enabled (1).
Disabled (0).
Default is 1.

Mandatory.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Neighbor Detailed View fields

Power Budget Algorithm grouping

Table 8-49 describes the fields in the Power Budget Algorithm grouping of the Neighbor
Detailed View.

Table 8-49 Neighbor Detailed View fields - Power Budget Algorithm grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Power Budget
Surround Cell
Hreqave
pbgt_surround_
cell_hreqave
(OMC-R parameter
name:
pbgtSrcell
Hreqave)

Represents the unique hreqave used for

the averaging rxlev measurements for
this neighbor cell. Only used if the cell
parameter: Use Neighbor Power Budget
Hreqave (useNeiPbgtHreqave) is set to 1.
Only used if the BSS Optional Feature
microcellOpt is unrestricted.

1 - 31.

Optional.

Power Budget
Algorithm Type
pbgt_alg_type

The power budget algorithm to be used per

neighbor cell. This allows per neighbor
control over the triggering of power budget
handover. The algorithm should be selected
based on the relationship between the
serving cell and the given neighbor, that
is around the corner neighbors or line
of sight neighbors. Affects the ranges
of pbgt_alg_data0, pbgt_alg_data1,
and pbgt_alg_data2. Only used if the
BSS Optional Feature microcellOpt is
unrestricted.

1 - 7.

Optional.

Power Budget
Algorithm Data
0
pbgt_alg_data0

Allows the operator to modify one of three

data values used in the per neighbor
surround cell power budget algorithm.
Only used if the BSS Optional Feature
microcellOpt is unrestricted.

Power Budget
Algorithm Data
1
pbgt_alg_data1

See pbgt_alg_data0.

Power Budget
Algorithm Data
2
pbgt_alg_data2

See pbgt_alg_data0.

Type 5 HO Margin
ho_margin_type5

See Configuring a neighbor cell for adaptive

handovers on page 8-190 for details.

68P02901W17-T

Optional.

Optional.

8-125
Jan 2010

Neighbor Detailed View fields

Chapter 8: Configuring cells

Directed Retry grouping

Table 8-50 describes the fields in the Directed Retry grouping of the Neighbor Detailed View.

Table 8-50 Neighbor Detailed View fields - Directed Retry grouping

Field name/BSS
parameter name

Mandatory or
Optional?

Brief description

Values

Directed Retry
Allowed
dr_allowed

Whether directed retry is allowed at

the external neighbor. Only used when
directedRetryOpt is unrestricted, and
it is only valid for SACCH neighbors.

Directed Retry
not allowed (0)
or Directed
Retry allowed
(1).

Optional.

Congestion
Handover Margin
congest_ho
_margin

The congestion handover margin, used

in the case of a congestion handover.
Only valid if the Directed Retry feature
(directedRetryOpt) or the Congestion
Relief (Directed Retry Alternatives)
feature (congestReliefOpt) is enabled
at the BSS.

-63 to 63 dB.

Optional.

Concentric Cells grouping

Table 8-51 describes the fields in the Concentric Cells grouping of the Neighbor Detailed View.

Table 8-51 Neighbor Detailed View fields - Concentric Cells grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Interfering
Neighbor
interfering_nei

Whether a neighbor that has a carrier

which uses a frequency that could
interfere with the carrier used in the
inner zone of the source cell. Only used
if the CELL inner_zone_alg type is
set to interference algorithm and the
neighbor is being added to the SACCH
list.

0 or 1.
No interfering
frequency (0),
Interfering
frequency (1).
Default is 0.

Optional.

Inner Zone
Threshold
inner_zone
_thresh

The signal strength difference between

the serving cell and the interfering
neighbor which is required for the MS
to qualify for a channel in the inner
zone. Only used if concentricCellOpt
is unrestricted (enabled) at the
BSS, CELL inner_zone_alg is set to
interference based algorithm, Neighbor
interfering_nei is set to TRUE, and the
neighbor is being added to the SACCH
list.

0 - 63 (db).
Default is 0.

Optional.

Continued

8-126

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 8-51

Creating a single Neighbor using the Neighbor Detailed View

Neighbor Detailed View fields - Concentric Cells grouping (Continued)

Field name/BSS
parameter name
Inner Zone
Margin
inner_zone
_margin

Brief description
An additional signal strength level
above the defined threshold necessary
for an MS to handover into the inner
zone. Only used if concentricCellOpt
is unrestricted (enabled) at the
BSS, CELL inner_zone_alg is set to
interference based algorithm, Neighbor
interfering_nei is set to TRUE, and the
neighbor is being added to the SACCH
list.

Mandatory or
Optional?

Values
0 - 63 (db).
Default is 0.

Optional.

Creating a single Neighbor using the Neighbor Detailed View

To create a Neighbor for a cell, perform these activities:

Find the source cell, see Finding the source cell on page 8-127.

Create the neighbor information, see Creating the Neighbor information on page 8-127.

Finding the source cell

To find the source cell quickly, follow these steps:

Procedure 8-23 Find the source cell

1

From the Front Panel, click the Find icon.

Complete the Cell Name and/or GSM Cell Id fields of the Source cell.

Click Find Cell(s) button. If found, the cell is listed in the Find Results
pane.

Highlight the required cell and click the Navigation Tree button. A
Navigation Tree is displayed, starting at the selected cell.

Creating the Neighbor information

To create the neighbor information using the Neighbor Detailed View form, follow these steps:

Procedure 8-24 Create neighbor information using Neighbor Detailed View form
1

Click the NEIGHBOR type button.

Select Edit Create from the Configuration Management menu bar.

The Neighbor Detailed View window is displayed.
Continued

68P02901W17-T

8-127
Jan 2010

Adding a neighbor both ways

Chapter 8: Configuring cells

Procedure 8-24 Create neighbor information using Neighbor Detailed View form
(Continued)
3

Enter a valid cell id in the Neighbor GSM Cell Identifier field.

Select Options - Initialize FORM from the menu bar.

This initializes the parameters on the form with the values of the
parameters in the cell pointed to in the Neighbor GSM Cell Identifier
field and, for microcellular, the parameters already identified in the
template.

NOTE
Specifying a gsmCellid that does not exist as a cell or a proxy
cell in the OMC-R MIB, the OMC-R automatically creates a
proxy cell. See Autocreation of a ProxyCELL on page 8-150
for more information.
5

If the microcellular option is enabled, select the appropriate template

from the menu.

Once initialized, all default values derived from the cell identified by
the gsmCellid are displayed in the Detailed View.
For example, the bcchFrequencyNum attribute derives its value from
the carrier1_arfcn attribute of the identified cell RTF_BCCH carrier.
These values can be modified as required. See Neighbor Detailed
View fields for details.

Select Disabled (0) in the Reciprocate Neighbor field in the General

parameter grouping, if a Reciprocal Neighbor for this Neighbor should
not be automatically created.
For example, when the Neighbor being created is to be one-way.
By default, this field is set to Enabled (1), so Reciprocal Neighbors are
automatically created if the RECIPROCATE_NBR environment variable
is switched on (set to TRUE). If a Reciprocal Neighbor already exists,
a new Reciprocal Neighbor is not created. If a Reciprocal Neighbor
already exists, and the Reciprocate Neighbor field is set to Disabled
(0), the OMC-R automatically switches the field to Enabled (1).

To create a neighbor, select File Create from the menu bar.

Close the Detailed View window by selecting File Close from the
menu bar.

Adding a neighbor both ways

A neighbor is required to be added both ways. Create the source after the neighbor. The Find
option, available from the GUI front panel, enables efficient location of source and neighbor cell
objects on the Navigation Tree. Follow the procedure described in Creating a single Neighbor
using the Neighbor Detailed View on page 8-127 to create both neighbors.

8-128

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adding multiple neighbors using add_nei

Adding multiple neighbors using add_nei

Greater efficiency in adding multiple neighbors can be achieving by using the Motorola utility
add_nei, which uses Batch_Rlogin. add_nei allows neighbors to be added both ways, including
neighbors across multiple OMC-Rs. For further details on add_nei, consult Software Release
Notes: OMC-R System (68P02901W74).

NOTE
The Motorola utility add_nei is part of an optional set of Operation and Maintenance
utilities available on the OMC-R GSM software CD-ROM.

68P02901W17-T

8-129
Jan 2010

Modifying a neighbor

Chapter 8: Configuring cells

Modifying a neighbor

Recommendation for modifying neighbors

The recommended method of modifying neighbors is using the GUI (Neighbor Detailed View
form). The modified parameters are propagated first to the BSS and, if acceptable, are then
updated in the MIB.

Modifying a neighbor using the OMC-R GUI

To edit a neighbor Detailed View, see the general procedure in Modifying a network object
using the OMC-R GUI on page 1-34.
Also see Configuring a neighbor cell for adaptive handovers on page 8-190, which describes how
to set the Optimized Type 5 Handover algorithm and margin for a neighbor cell.

Modifying multiple neighbors of same cell

To modify multiple neighbors of the same cell, use the cell Source Neighbor window. This
window enables selection of each neighbor in turn to edit the parameters.
Proceed as follows:

Procedure 8-25 Modify multiple neighbors of the same cell

1

Use the Navigation Tree or the Find option to locate the required cell
on the Navigation Tree.

From the Navigation Tree menu bar, select Config Mgt - Sources and
Neighbors option. A Source Neighbor window is displayed.

Highlight each item in the cell neighbor list and select Edit option to
modify the parameters. To move to the next neighbor on the list, first
return to Monitor mode.

Modifying multiple neighbors of same site or NE using cmutil

To modify multiple neighbors of the same SITE or NE using cmutil, see Chapter 15 cmutil.

8-130

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting neighbors using the Navigation Tree Delete option

Deleting neighbors using the Navigation Tree Delete

option

Introduction to deleting Neighbors using Navigation Tree

Before a cell can be deleted, the Neighbors must be deleted.
A Neighbor can be deleted using:

Sources and Neighbors View, see Creating and deleting Sources, Neighbors and
Reciprocals on page 8-115 for further details.

Navigation Tree.

This section describes how to delete a Neighbor for a cell using the Navigation Tree.

Deleting a single neighbor using the Navigation Tree Delete

option
To delete a single Neighbor from a cell using the Navigation Tree, proceed as follows:

Procedure 8-26 Delete a single Neighbor from a cell using the Navigation Tree

68P02901W17-T

Navigate to the required Neighbor.

Use the Find icon if required.

Click the Neighbor instance button to be deleted.

The button changes color.

From the menu bar select Edit Delete.

A confirmation window is displayed requesting confirmation of
intention to delete.

Click OK to delete.
The confirmation window closes and the process is documented on the
status bar.
When the deletion has been completed, the chosen neighbor instance
button disappears from the Navigation Tree, and the message Delete
Complete is displayed in the status bar.

8-131
Jan 2010

Deleting a neighbor both ways

Chapter 8: Configuring cells

Deleting a neighbor both ways

A neighbor is required to be deleted both ways. The source must be deleted after the neighbor.
The Find option, available from the GUI front panel, enables efficient location of source and
neighbor cell objects on the Navigation Tree. Follow the procedure described in Deleting a
single Neighbor using the Navigation Tree Delete option in this section, to delete both
neighbors.

Deleting multiple neighbors using del_neighbor command or

del_nei utility
To remove multiple Neighbors, or Sources/Neighbors, of a cell using the TTY interface, use
the del_neighbor command. Refer to Technical Description: BSS Command Reference
(68P02901W23) for full details of this command.
Greater efficiency in deleting multiple neighbors can be achieving by using the Motorola utility
del_nei, which uses Batch_Rlogin. del_nei enables to neighbors to be deleted both ways,
including neighbors across multiple OMC-Rs. For further details on del_nei, consult Software
Release Notes: OMC-R System (68P02901W74).

NOTE
The Motorola utility del_nei is part of an optional set of Operation and Maintenance
utilities available on the OMC-R GSM software CD-ROM.

8-132

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Neighbor templates

Neighbor templates

Introduction to neighbor templates

Neighbor templates can be used to create neighbor cells in a network without the need for
re-entering similar information.

Displaying a list of neighbor templates

To display a list of neighbor templates, follow these steps:

Procedure 8-27 Display a list of neighbor templates

1

Open the Navigation Tree.

Select the Config Mgt - Neighbor Templates from the menu bar.

A list of existing templates is displayed.

Creating a neighbor template

To create a neighbor template, follow these steps:

Procedure 8-28 Create a neighbor template

68P02901W17-T

When the list of templates is shown, select Edit Create.

Enter the required parameters to the Detailed View.

Select File Create to create a template.

8-133
Jan 2010

Editing a neighbor template

Chapter 8: Configuring cells

Editing a neighbor template

To edit a neighbor template, follow these steps:

Procedure 8-29 Edit a neighbor template

1

When the list of templates is shown, select the required template.

Select Edit Detailed View from the neighbor template.

Select Edit Edit.

Change the required parameters in the Detailed View.

Select File Save to save the changes to the template.

Deleting a neighbor template

To delete a template, follow these steps:

Procedure 8-30 Delete a template

8-134

When the list of templates is shown, select the required template to

be deleted.

Select Edit Delete.

Confirm the deletion by clicking on OK in the confirmation box.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a UTRAN neighbor

Configuring a UTRAN neighbor

Definition of a UTRAN neighbor

A UMTS Terrestrial Radio Access Network (UTRAN) neighbor is a 3G neighbor object. Up to 16
UTRAN neighbors can be supported per cell. A UTRAN neighbor can only be created when the
cell has no more than 31 GSM neighbors. A cell with a UTRAN neighbor can be added to the
BCCH list, but cannot be added to a SACCH list.
A cell can have up to 32 exclusive UTRAN BCCH neighbors where the UMTS BA Type field
(umts_ba_type) in the UTRAN Detailed View (see Table 8-52) is set to BCCH(1). An error
message is displayed if this condition is not satisfied.
A cell can have up to 32 UTRAN BCCH neighbors per FDD ARFCN (fdd_arfcn). An error
message is displayed and the operation fails, if this condition is not satisfied.
A cell can have up to 32 UTRAN SACCH neighbors when the UMTS BA Type field (umts_ba_type)
in the UTRAN Detailed View is set to SACCH(2) or BCCH and SACCH (3). An error is displayed
and the operation fails, if this condition is not satisfied.
A cell can have up to 32 UTRAN SACCH neighbors per FDD ARFCN (fdd_arfcn). An error
message is displayed and the operation fails, if this condition is not satisfied.
A cell can only support three FDD ARFCN (fdd_arfcn) for its UTRAN neighbors. An error
message is displayed and the operation fails, if this condition is not satisfied.

Prerequisites to configuring a UTRAN neighbor

The Inter-RAT handover feature (see Inter-Radio Access Technology (Inter-RAT) Handover on
page 2-95) must be unrestricted before a UTRAN neighbor can be created.

UTRAN neighbor parameters

Table 8-52 lists the parameter associated with a UTRAN neighbor and its valid values.

Table 8-52 UTRAN neighbor parameters and values

OMC-R GUI
field name/BSS
parameter name
Utran Neighbor
Cell Identifier
utran_cell_id

Description

Values

Displayed in the Identification parameter grouping in

the UTRAN Detailed View form.
The unique UTRAN Cell identifier for this UTRAN
neighbor.
This parameter can only be completed in Create mode,
Continued

68P02901W17-T

8-135
Jan 2010

Creating a UTRAN neighbor using the OMC-R GUI

Chapter 8: Configuring cells

Table 8-52 UTRAN neighbor parameters and values (Continued)

OMC-R GUI
field name/BSS
parameter name

Description

Values

and cannot be modified in Monitor or Edit mode.

Name
name

An OMC-R only parameter.

Displayed in the Identification parameter grouping in
the UTRAN Detailed View form.
Automatically created when the UTRAN is created
using the UTRAN cell id.

Up to 31
characters
plus the NULL
character.

FDD ARFCN
fdd_arfcn

Displayed in the General parameter grouping in the

UTRAN Detailed View form.
Indicates the frequency of the cell.

0 - 16383

Scrambling Code
scr_code

Displayed in the General parameter grouping in the

UTRAN Detailed View form.
Indicates the primary scrambling code.

0 - 511.

UMTS
Measurement
Margin
umts_meas
_margin

See Inter-Radio Access Technology (Inter-RAT)

Handover on page 2-95 for further details.

Averaging Period
umtsNcellAvg
Prd

See Inter-Radio Access Technology (Inter-RAT)

Handover on page 2-95 for further details.

UMTS BA Type
umts_ba_type

See Inter-Radio Access Technology (Inter-RAT)

Handover on page 2-95 for further details.

TD-SCDMA
ARFCN
tdd_arfcn

Refer to TD-SCDMA and GSM interworking on page

2-231 for further details.

TD-SCDMA Cell
Parameter
tdd_cell_param

Refer to TD-SCDMA and GSM interworking on page

2-231 for further details.

TD-SCDMA
Time Switched
Transmit
Diversity Mode
tdd_tstd_mode

Refer to TD-SCDMA and GSM interworking on page

2-231 for further details.

TD-SCDMA Space
Code Transmit
Diversity Mode
tdd_sctd_mode

Refer to TD-SCDMA and GSM interworking on page

2-231 for further details.

Creating a UTRAN neighbor using the OMC-R GUI

To create a UTRAN neighbor using the OMC-R GUI, follow Procedure 8-31.

8-136

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a UTRAN neighbor using the TTY interface

Procedure 8-31 Create a UTRAN neighbor using the OMC-R GUI

1

Navigate to and select the UTRAN class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Radio Frequency
CELL CELL instance UTRAN).
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details.
The UTRAN class button changes color.

Select Edit Create from the menu bar.

The OMC-R displays the UTRAN Detailed View.

Enter all required information in this form, see Table 8-52 for field
details.

NOTE
To obtain the relevant information for a parameter, select
Help - On Context from the menu bar and drag the ?
prompt to the appropriate field and click that field. A
context-sensitive help page is displayed.
4

Create and close the Detailed View.

Configuring a UTRAN neighbor using the TTY interface

To configure a UTRAN neighbor using the TTY interface, use the following commands:

add_neighbor.

disp_neighbor.

modify_neighbor.

del_neighbor.

If TD-SCDMA inter-working feature is unrestricted, the BSC supports the addition, modification,
display, and deletion of TD-SCDMA neighbor. The MMI neighbor commands are updated
to support the TD-SCDMA neighbor cell in the BSS database and to support the TD-SCDMA
inter-working feature. These commands allow the BSS to add, delete, modify, and display
TD-SCDMA cells in the database. These commands also continue to support the existing GSM
cell format.
The following sections provide some examples of using these commands with the parameters
detailed in Table 2-17. For further details of these commands, parameters, and command
prompts, see the Technical Description: BSS Command Reference (68P02901W23) manual.

68P02901W17-T

8-137
Jan 2010

Configuring a UTRAN neighbor using the TTY interface

Chapter 8: Configuring cells

Creating a UTRAN neighbor

For example, the following command creates the UTRAN cell 496231111 as the neighbor of
GSM cell 0010114:
add_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_fdd
Enter the UMTS Absolute Radio Freq Chan Number: 10762
Enter the Scrambling Code:

200

Enter the Diversity Enabled Flag:

COMMAND ACCEPTED
Where umts_fdd is the add_neighbor command placement parameter, which specifies the new
neighbor as a UTRAN cell. The BSS automatically adds the UTRAN neighbor to the BCCH list.
For example, the following command creates the TD-SCDMA cell 4 9 6 2 3 1 1 1 1 as a
neighbor of GSM cell 0 0 1 0 1 1 4 with all values entered for all parameters when TD-SCDMA
inter-working is enabled:
add_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_tdd
Enter the UTRAN Absolute Radio Freq Chan Number: 10110
Enter the TD-SCDMA cell parameter: 100
Enter the Time Switched Transmit Diversity Flag: 1
Enter the Space Code Transmit Diversity Flag:

11

COMMAND ACCEPTED

Deleting a UTRAN neighbor

For example, the following command deletes the UTRAN cell 496231111 as the neighbor of
GSM cell 0010114:
del_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1
COMMAND ACCEPTED
For example, the following command deletes the TD-SCDMA neighbor cell 4 9 6 2 3 1 1 1
1 as a neighbor of GSM cell 0 0 1 0 1 1 4:
del_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1
COMMAND ACCEPTED

Modifying a UTRAN neighbor

For example, the following command modifies the UTRAN parameter scr_code to 5 for UTRAN
cell 496231111 as the neighbor of GSM cell 0010114:
modify_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 scr_code 5
COMMAND ACCEPTED
For example, the following command modifies the tdd_cell_parameter attribute to a value of 100
for TD-SCDMA cell 4 9 6 2 3 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4:
modify_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 tdd_cell_parameter 100
COMMAND ACCEPTED

8-138

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a UTRAN neighbor using the TTY interface

Displaying details of a UTRAN neighbor

For example, the following command displays details for the UTRAN cell 496231111 as the
neighbor of GSM cell 0010114:
disp_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1
UTRAN cell id: 496 231 1(0001h) 1(0001h)
FDD ARFCN: 10683
Scrambling code: 511
Diversity enabled: 1 (yes)
For example, the following command displays all the neighbor cells of GSM cell 0 0 1 0 1 1 4
which includes 1 GSM neighbor, 1 TD-SCDMA neighbor:
disp_neighbor 0 0 1 0 1 1 4 all
Start of neighbor report:
Neighbor cell id: 001 01 1 (0001h) 4 (0004h)
Neighbor cell name: N/A
Neighbor cell frequency type: PGSM
Placement: External
Synchronization enabled: N/A
BCCH frequency number: 60
Base station identity code: 16
MS transmit power maximum: 37
Neighbor receive level minimum: 15
Neighbor handover margin: 8
Power budget surrounding cell hreqave: 8
Receive quality handover margin: 63
Receive level handover margin: -63
Neighbor type 5 handover margin: 63
Adjacent channel interference test enabled: 0 (no)
Power budget algorithm type: 1
Neighbor congestion handover margin: 8
Range of the neighbor cell: Normal
UTRAN cell id: 496 231 1 (0001h) 1 (0001h) 1 (0001h)
TDD-ARFCN: 10110
TD-SCDMA cell parameter: 100
Time Switched Transmit Diversity: 0 (no)
Space Code Transmit Diversity: 0 (no)
End of report

68P02901W17-T

8-139
Jan 2010

UTRAN blind search neighbor

Chapter 8: Configuring cells

UTRAN blind search neighbor

Introduction to a UTRAN blind search neighbor

A blind search neighbor is contained within a cell. A cell can have up to eight UTRAN blind
search neighbors. A blind search neighbor defines the parameters for performing a cell
reselection search from 2G to 3G.

UTRAN Blind Search Neighbor Detailed View fields

Identification grouping parameters
See Table 8-1 for field descriptions.

General grouping
Table 8-53 UTRAN Blind Search Neighbor Detailed View Fields General grouping
OMC-R GUI
field name/BSS
parameter name
Blind Search
FDD ARFCN
bs_fdd_arfcn

Description
The FDD ARCN of the Blind Search neighbor.
A blind search neighbor cannot share
bs_fdd_arfcn with a UTRAN neighbor or
another blind search neighbor.

Values
0 - 16383

Creating a UTRAN blind search neighbor

To create a UTRAN blind search neighbor (BlindSrchNbr), the Enhanced Inter-RAT Handover
feature (EnhncdInterRatOpt) must be Enabled(1), see Table 4-4.

Deleting a UTRAN blind search neighbor

When the last UTRAN blind search neighbor equipped to the container cell is deleted, if
blindSearchPref is set to 1 the following warning message is displayed in the status bar:

WARNING: There are no Blind Search neighbors equipped for this cell.

8-140

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Proxy cells

Proxy cells

Introduction to proxy cells

A proxy cell represents any cell under the control of a neighboring OMC-R and is geographically
adjacent to (that is, is a neighbor of) any cell within the current OMC-R.
The proxy cell is, in effect, a placeholder for the actual cell and contains a limited subset of the
cell parameters. These parameters are those on which neighbor cells have a dependency,
such as BSIC and BCCH frequency.
Proxy cell updates use the Neighbor Propagation feature of the MIB, so that cell changes for
LAC-CI, BSIC, max transmit power, or carrier1 ARFCN of the BCCH RTF, automatically update
associated sources/neighbors.
The proxy cell is also a placeholder for the network topology under control of the OMC-R.
This ensures cells cannot be created if they exist in another part of the network, because the
proxy cell is flagged as a duplicate.
The proxy cell feature enables Motorola's microcellular networks to operate under the umbrella
of other manufacturer's macrocellular infrastructure.

Environmental variables relating to proxy cells

The following environmental variables relate to proxy cells:

PROXYCELL_AUTOCREATE - controls the autocreation of proxy cells during neighbor

creation.

PROXYCELL_UPDATE - controls if the dynamic propagation of proxy cells information

occurs between OMC-Rs or not.

PROXYCELL_UPDATE_PERIOD - controls the amount of time between each execution of

proxy cell update. The value is set in seconds. The default is 28800 seconds (8 hours).

EXPORT_ALL_CELLS - if set to ON, information on all the Cells in the network will be
exported. The default is OFF.

{31400} TDD_PROXY_ENABLED - used to control the creation, display, and modification

of TD-SCDMA UTRAN Proxy Cells. This is a new environment variable supported by the
OMC-R.

TD-SCDMA UTRAN Proxy Cells

When the environmental variable TDD_PROXY_ENABLED is set to 0 (the default value), only
FDD specific attributes are displayed on UtranProxyCellForm and UtranProxyCellListForm.
When TDD_PROXY_ENABLED is set to 1, only TDD specific attributes are displayed on
UtranProxyCellForm and UtranProxyCellListForm.

68P02901W17-T

8-141
Jan 2010

BCCH and SDCCH in the EGSM band for Proxy cells

Chapter 8: Configuring cells

NOTE
TDD_PROXY_ENABLED should correspond with tdOpt at BSS level, that is, when
TDD_PROXY_ENABLED is 0, tdOpt should not be purchased at BSS level, and when
TDD_PROXY_ENABLED is 1 ,tdOpt should be purchased.

BCCH and SDCCH in the EGSM band for Proxy cells

The frequency range for proxy cells can be set to EGSM band frequencies. See Configuring a
cell with BCCH and SDCCH in the EGSM band on page 8-179 for further details.

Proxy cell information

The following proxy cell information is provided in the following sections:

8-142

Configuring a single proxy cell on page 8-143.

Configuring a single UTRAN ProxyCELL on page 8-146

Autocreation of a ProxyCELL on page 8-150.

Configuring multiple proxy cells using cmutil on page 8-154.

Exporting and importing proxy cell information between OMC-Rs on page 8-155.

Synchronizing all OMC-R proxy cells within a network on page 8-160.

Dynamic propagation of proxy cell data to OMC-Rs on page 8-162.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a single proxy cell

Configuring a single proxy cell

Creating a proxy cell using the OMC-R GUI

To create a Proxy Cell using the OMC-R GUI, follow these steps:

Procedure 8-32 Create a Proxy Cell using the OMC-R GUI

1

From the Navigation Tree, select Config Mgt Proxy Cells Proxy
Cells from the menu bar. The Proxy Cell List form is displayed, which
contains a scrollable list of the currently configured Proxy Cells and
their parameters.

Select the Edit Create option. The ProxyCELL Detailed View form
is displayed in Create mode. The Proxy CELL Detailed View is used
primarily for creation and modification of Proxy Cells. All values except
ARFCN map directly to normal attribute values from the corresponding
cell under an external OMC-R.

Complete the fields, as required. See ProxyCELL Detailed View

fields for details.

Select File Create from the menu bar to create the proxy cell.

Select File Close from the menu bar to close the ProxyCELL Detailed
View.

ProxyCELL Detailed View fields

The following sections list and briefly describe the parameter fields in the ProxyCELL Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

68P02901W17-T

8-143
Jan 2010

ProxyCELL Detailed View fields

Chapter 8: Configuring cells

Identification grouping
Table 8-54 describes the fields in the Identification grouping of the ProxyCELL Detailed View.

Table 8-54

ProxyCELL Detailed View fields - Identification grouping

Field name

Values

Brief description

GSM Cell ID

The Cell Global Identification (CGI) of the

proxy cell.
The MCC and MNC subfields can be edited
in Create and Edit mode.

Cell Name

The textual name of the cell.

Mandatory or
Optional?
Mandatory.

Optional.

Proxy Cell Data grouping

Table 8-55 describes the fields in the Proxy Cell Data grouping of the ProxyCELL Detailed View.

Table 8-55

ProxyCELL Detailed View fields - Proxy Cell Data grouping

Field name

Brief description

Values

Mandatory or
Optional?

OMC Name

The name of the OMC where the CELL

represented by this ProxyCell resides.
Set to NULL for an autocreated proxy
cell. See Autocreation of a ProxyCELL
on page 8-150 for further details.

Layer Number

Indicates on which layer the cell exists.

Specific to cells when Microcellular is
unrestricted (enabled).

0 - 2.
Macro (0),
Micro (1),
Pico (2).

Optional.

Carrier 1 ARFCN

The absolute radio frequency channel

for carrier 1. The ARFCN field
corresponds to the BCCH frequency
associated with that cell. In the
Motorola configuration, this is the
ARFCN of the RTF type BCCH whose
carrier 1GsmCellId attribute points to
this cell.

0 - 124,
512 - 885,
975 - 1023.

Mandatory.

BSIC

The Base Station Identity Code (BSIC).

The BSIC is a local color code that
allows an MS to distinguish between
different neighboring base stations.
BSIC is encoded on the Synchronization
Channel.

0 - 63.

Mandatory

Maximum MS
Transmit Power

The maximum MS output power which

can be used in this cell.

0 - 39

Mandatory

Optional.

Continued

8-144

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Modifying a proxy cell using the OMC-R GUI

Table 8-55 ProxyCELL Detailed View fields - Proxy Cell Data grouping (Continued)
Field name

Brief description

Values

Mandatory or
Optional?

Handover Margin
Default

The default value used for a neighbor

whenever ho_margin_cell is not
defined in the Neighbor object.

-63 to 63 dB

Mandatory

Min Receive Level

Default

The default value to be used for

Neighbor xlev_min_cell by contained
Neighbor class instances.

0 - 63

Mandatory

Modifying a proxy cell using the OMC-R GUI

To modify a proxy cell, proceed as follows:

Procedure 8-33 Modify a proxy cell

1

Select the required proxy cell instance.

Select the Edit Detailed View option.

Select Edit Edit from the menu bar to change the form to Edit mode.

Modify the fields, as required. See ProxyCELL Detailed View fields

for details.

Select File Save from the menu bar to save your modifications.

Select File Close from the menu bar to close the ProxyCELL Detailed
View.

Deleting a proxy cell using the OMC-R GUI

CAUTION
Always consult the CM supervisor before deleting a proxy cell. Deleting a proxy cell
also sets the cellCondition to Does not Exist for any neighbors in the MIB with the
same gsmCellid. This condition will be set for both proxy cells and real cells, though
real cells are not deleted.
To delete a proxy cell, proceed as follows:

Procedure 8-34 Delete a proxy cell

68P02901W17-T

From the Navigation Tree, select Config Mgt Proxy Cells Proxy
Cells from the menu bar.

Select the required proxy cell instance.

Select the Edit Delete option. The selected proxy cell instance is
deleted. All associated sources/neighbors are updated.

8-145
Jan 2010

Configuring a single UTRAN ProxyCELL

Chapter 8: Configuring cells

Configuring a single UTRAN ProxyCELL

Creating a UTRAN ProxyCELL using the OMC-R GUI

To create a UTRAN ProxyCELL using the OMC-R GUI, follow these steps:

Procedure 8-35 Creating a UTRAN ProxyCELL using the OMC-R GUI

1

From the Navigation Tree, select Config Mgt ProxyCELL

Utran ProxyCELLs. The UTRAN ProxyCELL List form is displayed,
which contains a dropdown list of the currently configured UTRAN
ProxyCELLs and their parameters.

Select the Edit Create option. The UTRAN ProxyCELL Detailed

View form is displayed in Create mode. The UTRAN ProxyCELL
Detailed View is used primarily for creation and modification of
UTRAN ProxyCELLs. All values except ARFCN, map directly to normal
attribute values from the corresponding cell under an external OMC-R.

Complete the fields, as required. See UTRAN ProxyCELL Detailed

View fields for details.

Select File Create from the menu bar to create the UTRAN
ProxyCELL.

Select File Close from the menu bar to close the UTRAN ProxyCELL
Detailed View.

NOTE
5000 UTRAN_Proxy_CELLS can be created from the UTRAN ProxyCELL window.

UTRAN ProxyCELL Detailed View fields

The following sections list and briefly describe the parameter fields in the UTRAN ProxyCELL
Detailed View according to their parameter grouping.

NOTE
To obtain further information about a parameter, select Help On Context from
the menu and drag the ? prompt to the appropriate field and click that field. A
context-sensitive help page is displayed.

8-146

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

UTRAN ProxyCELL Detailed View fields

Identification grouping
Table 8-56 describes the fields in the Identification grouping of the UTRAN ProxyCELL Detailed
View.

Table 8-56

ProxyCELL Detailed View fields - Identification grouping

Field name

Brief description

Values

Utran ProxyCELL Id

The Utran ProxyCELL Id

consists of the following:
Mobile Country Code (MCC),
Mobile Network Code (MNC),
Location Area Code (LAC),
Radio Network Controller
Identity (RNC Id), and Cell Id.

10
MCC (3 digits): 0 9
MNC (3 digits): 0 9
LAC: 0 - 65535
RNC Id: 0 - 4095
Cell Id: 0 - 65535

Name

Textual name of the UTRAN

Neighbor.

Mandatory or
Optional?
Mandatory

Optional

UTRAN ProxyCELL Data grouping

Table 8-57 describes the fields in the UTRAN ProxyCELL Data grouping of the UTRAN
ProxyCELL Detailed View.

Table 8-57 ProxyCELL Detailed View fields - ProxyCELL Data grouping

Field name

Values

Brief description

Mandatory or
Optional?

FDD ARFCN

The Absolute Radio

Frequency Channel Number
(ARFCN) of the UtranNbr
cell.

10562 - 10838

Mandatory

Scrambling Code

The primary scrambling code

of the UtranNbr cell.

0 - 511

Mandatory

Diversity Enabled

Indicates whether diversity is

enabled for this cell.

0 and 1
Disabled (0)
Enabled (1)

Mandatory

UMTS Measurement
Margin

Measurement parameter used

by the handover algorithm.

0 - 20

Optional
Continued

68P02901W17-T

8-147
Jan 2010

Modifying a UTRAN ProxyCELL using the OMC-R GUI

Table 8-57

Chapter 8: Configuring cells

ProxyCELL Detailed View fields - ProxyCELL Data grouping (Continued)

Field name

Values

Brief description

Mandatory or
Optional?

Averaging Period

Utran neighbor cell averaging

period measured in SACCH
multiframes (480mS).

1 - 12

UMTS BA Type

The neighbor lists, UTRAN

BCCH, UTRAN SACCH,
UTRAN BCCH and SACCH.

1-3
Optional
1 UMTS_BA_BCCH
2 UMTS_BA_SACCH
3 UMTS_BA_BCCH_SACCH

Optional

Modifying a UTRAN ProxyCELL using the OMC-R GUI

To modify a UTRAN ProxyCELL, proceed as follows:

Procedure 8-36

8-148

Modifying a ProxyCELL

Select the required UTRAN ProxyCELL instance.

Select Edit Detailed View option.

Select Edit Edit from the menu bar to change the form to Edit mode.

Modify the fields, as required. See UTRAN ProxyCELL Detailed

View fields for details.

Select File Save from the menu bar to save the modifications.

Select File Close from the menu bar to close the UTRAN ProxyCELL
Detailed View.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a UTRAN ProxyCELL using the OMC-R GUI

Deleting a UTRAN ProxyCELL using the OMC-R GUI

CAUTION
Always consult the CM supervisor before deleting a UTRAN ProxyCELL. Deleting a
proxy cell also sets the cellCondition to Does not Exist for any neighbors in the MIB
with the same utran_cell_id.
To delete a UTRAN ProxyCELL, proceed as follows:

Procedure 8-37 Deleting a UTRAN ProxyCELL

68P02901W17-T

From the Navigation Tree, select Config Mgt ProxyCELLs

UTRAN ProxyCELLs from the menu bar.

Select the required UTRAN ProxyCELL instance.

Select Edit Delete option. The selected UTRAN ProxyCELL

instance is deleted.

8-149
Jan 2010

Autocreation of a ProxyCELL

Chapter 8: Configuring cells

Autocreation of a ProxyCELL

Introduction to autocreation of a ProxyCELL

When creating a neighbor cell with a GSM cell identifier, which does not exist as either
a cell or a ProxyCELL in the MIB, the OMC-R creates a ProxyCELL instead. This is
referred to as autocreation of proxy cells, and occurs whenever the environment variable
PROXYCELL_AUTOCREATE is set.
Autocreation of proxy cells also occurs when an unrecognized neighbor is created by an:

Audit.

cmutil.

Object creation event from the BSS.

Proxy cell autocreation parameters

The following autocreated proxy cell parameter fields are derived from the neighbor cell. The
OMC-R GUI parameter field names are listed first and the BSS parameter names are shown
in parentheses.

Neighbor GSM Cell Identifier (neighbourGsmCellId)

BSIC (bsic)

Handover Margin Cell (ho_margin_cell)

Mobile Station Maximum Transmit Power (ms_txpwr_max_cell)

Minimum Call Receive Level (rxlev_min_cell)

BCCH Frequency (bcchFrequencyNum)

The operator has to enter all values for a proxy cell created manually.
The following autocreated proxy cell parameters are set to a temporary value, until the correct
source cell information is determined by a proxy cell import:

8-150

Cell Name field (name) of the proxy cell is set to the same value as specified in the Neighbor
GSM Cell Identifier field.

layer_number of the proxy cell is initialized to MACROCELL.

omc_name of the proxy cell is initialized to NULL.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Propagation of autocreated proxy cell information

Propagation of autocreated proxy cell information

After the proxy cell is created (or updated), the OMC-R:

Propagates the following proxy cell parameters to all neighbors pointing to it:
gsmCellID
carrier1_afcn
bsic
max_tx_ms
When changes to a proxy cell parameter trigger a neighbor propagation, messages
are logged in the omcaudit log file indicating the result of each propagation.

Sets the Cell Condition field (cellCondition) of all neighbors pointing to the proxy cell to
Neighbor Exists Proxy Cell.

Autocreated proxy cell restrictions

If a cell is created in the OMC-R network with the same gsmCellId as an existing proxy cell, the
OMC-R deletes the proxy cell from the MIB before creating the cell. However, if the proxy cell
has neighbors, the cell create request is rejected by the BSS and the proxy cell is kept.
If the one remaining Neighbor pointing to a proxy cell is deleted, and proxy cell autocreation
is enabled, the OMC-R deletes the proxy cell automatically.
When a proxy cell is deleted, the OMC-R sets the Cell Condition field of the Neighbors pointing
to the deleted proxy cell to Neighbor Does Not Exist.

Enabling autocreation of proxy cells

Autocreation of proxy cells is only enabled when the environmental variable
PROXYCELL_AUTOCREATE is set to 1. By default, this variable is disabled, that is, set to 0.
PROXYCELL_AUTOCREATE can be found in /usr/omc/current/config/proxy_cell.cfg.
An OMC stop/start is not required to enable the variable and the value is picked up automatically
by the Mib Processes from the proxy_cell.cfg file.
Enabling automatic updates of proxy cells:
Automatic updates to proxy cells are only enabled when the variable PROXYCELL_UPDATE
is set to 1.
By default, this variable disabled, that is, set to 0.
PROXYCELL_UPDATE is found in /usr/omc/current/config/proxy_cell.cfg.
An OMC stop/start is not required to enable the variable and the value is picked up automatically
by the Mib Processes from the proxycell.cfg file.

68P02901W17-T

8-151
Jan 2010

Autocreating a proxy cell using the OMC-R GUI

Chapter 8: Configuring cells

Autocreating a proxy cell using the OMC-R GUI

To autocreate a proxy cell using the OMC-R GUI, follow these steps:

Procedure 8-38 Autocreate a proxy cell using the OMC-R GUI

1

Execute the following command as omcadmin to ensure that the

autocreate function is set:ECHO $PROXYCELL_AUTOCREATE
If PROXYCELL_AUTOCREATE is not set, use text editor or set
command, and restart the OMC-R to make the change take effect.

Select the required CELL instance and click the folder icon next to this
element to display the NEIGHBOR type button.

Click the NEIGHBOR type button and select Edit Create. The
OMC-R displays the Neighbor Detailed View window in Create mode.

Specifying parameter values for the proxy cell

To enter parameter values for the proxy cell, follow these steps:

Procedure 8-39 Enter parameter values for the proxy cell

8-152

Enter a unique cell identification number in the Neighbor GSM Cell

Identifier fields. To autocreate a proxy cell this cell identification
number should not already exist as a cell or a proxy cell.

Select Options - Initialize Form from the menu bar.

If the GSM cell identifier does not exist as either a cell or a proxy cell
in the OMC-R MIB, the OMC-R displays the following message:
<cell id> does not exist in the System Database as a CELL or
a Proxy Cell.
A Proxy Cell shall be automatically created when this
Neighbor is created.
The Proxy Cell's parameters shall be derived from this
Neighbor.

Click OK. The OMC-R displays the Neighbor Detailed View in Create
mode.

Modify any default field settings as required, and as permitted. See

Table 8-54 and Table 8-55 for details.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Autocreating a proxy cell using the OMC-R GUI

Saving and Closing

To create and store parameter values for the autocreated proxy cell, follow these steps:

Procedure 8-40 Create and store parameter values for the autocreated proxy cell

68P02901W17-T

Select File Create from the menu bar to create the proxy cell.
If the create fails, the OMC-R displays a message in the status bar at
the bottom of the window. Otherwise, a Create Complete message is
displayed, and the Cell Condition field displays Proxy Cell.
On successful creation, the proxy cell is displayed in the Navigation
Tree as a neighbor with the cell id the same as the proxy cell name.

Select File Close from the menu bar to close and exit the Detailed
View window.

8-153
Jan 2010

Configuring multiple proxy cells using cmutil

Chapter 8: Configuring cells

Configuring multiple proxy cells using cmutil

Creating multiple proxy cells

The usual requirement is for multiple proxy cells to be configured at a given time. The
recommended way to create the proxy cells is to use the pcellImport utility. See Exporting and
importing proxy cell information between OMC-Rs on page 8-155 in this section.
Alternatively, to create multiple proxy cells using cmutil, see Chapter 15 cmutil.

Modifying and deleting multiple proxy cells

To modify and delete multiple proxy cells using cmutil, see Chapter 15 cmutil.

8-154

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Exporting and importing proxy cell information between OMC-Rs

Exporting and importing proxy cell information

between OMC-Rs

Introduction to importing and exporting proxy cells

Motorola recommends that proxy cell information is exported from the OMC-R to a file whenever
new cells are created, deleted, or reparented.
The information in the export file can then be imported into the neighboring OMC-Rs so that all
proxy cell information is synchronized between OMC-Rs. This indirectly synchronizes all cells
and neighbors across OMC-Rs, which helps the smooth handover of calls.

Contents of proxy cell export file

The proxy cell export file is an ASCII file containing information on the proxy cells. The first line
of the file is the header, which labels the parameters to be exported. Each subsequent line in the
file represents cell values, one line per cell. Each parameter is separated by a | (pipe) symbol.
The parameters exported for each proxy cell are:

OMC_Name.

GSMCellId.

Cell_Name.

Layer_Number.

Carrier1_ARFCN.

BSIC.

Max_MS_Tx_Pwr.

HO_Margin.

Min_Rxlev.

List_Of_Nbr (consisting of a neighbor count, followed by a list of the neighborCellids).

68P02901W17-T

8-155
Jan 2010

Contents of proxy cell export file

Chapter 8: Configuring cells

NOTE
Help on the export feature is available from the following location:
/usr/omc/current/sbin/pcellExport -help

The proxy cell export process retrieves the name parameter of the active OMC-R in the MIB
and uses this name to complete the OMC_Name field in the proxy cell export file. The active
OMC-R is the OMC-R controlling the MIB; inactive OMC-Rs are the OMC-Rs managing other
parts of the network.

Neighbor information in the export file

The proxy cell export file for each CELL contains a count of Neighbors, followed by the
neighborGsmCellId of all neighbors that reside below the CELL, and have their cellCondition set
to NEIGHBOR_DOES_NOT_EXIST or NEIGHBOR_EXISTS_PROXYCELL. Therefore, for each
cell, the cell ids of neighbors that do not exist as CELLs in the OMC-R are exported.

Example of a proxy export file cell entry

An entry for a CELL with two neighbors would have the following format in the proxy cell
export file, for example:
omcA|123-45-25-0|cork| 2 | 3 | 0 | 4| 0 | 0 | 2 |145-26-25-0|156-36-34-0
Where:

is:
omcA

8-156

OMC_Name.

123-45-25-0

GsmCellId.

cork

Cell_Name.

Layer_Number.

Carrier1_ARFCN.

BSIC.

Max_MS_Tx_Pwr.

HO_Margin.

Min_Rxlev.

List_Of_Nbr - neighbor count, followed by...

145-26-25-0

gsmcellid of first neighbor.

156-36-34-0

gsmcellids of second neighbor.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Enabling proxy cell export

Enabling proxy cell export

If the environmental variable EXPORT_ALL_CELLS is set, ProxyCellExport exports the data
of all the cells. By default, EXPORT_ALL_CELLS is unset.
If there are one way neighbors at an OMC-R, set EXPORT_ALL_CELLS.

Prerequisites for exporting and importing

To carry out an export or import:

User access privileges must be set to read and write.

Configuration Management access must be enabled in the user's user profile.

Exporting proxy cell information using the TTY interface

To export all proxy cell information from an OMC-R to a tab delimited file, carry out the
following procedure:

Procedure 8-41 Export all proxy cell information from an OMC-R

1

Log in as omcadmin.

From the Front Panel, select Xterm to open an Xterm window.

Execute the following command:

/usr/omc/current/sbin/pcellExport

NOTE
To specify the export file name execute the following
command:
/usr/omc/current/sbin/pcellExport [-o <filename>]

An error message is displayed if RF import or export is taking place.

On successful completion the following message is displayed in the
command line:
ProxyCellExport completed successful
The outcome of the export, and the path where the file may be located
are recorded in the usr audit log file.
Continued

68P02901W17-T

8-157
Jan 2010

Importing proxy cell information

Chapter 8: Configuring cells

Procedure 8-41
4

Export all proxy cell information from an OMC-R (Continued)

To locate the export file, use the following command:

cd /usr/omc/ne_data/proxycell_data
ls <filename>
Where:
<filename> is PROXYCELL_EXPORT.OUT (by default), specified
filename.

NOTE
If a proxycell_export file already exists, the file is backed
up and given the extension .BAK.
All files in the directory proxycell_data that have not been
accessed within seven days are removed.

Importing proxy cell information

To import proxy cell information into the OMC-R, carry out the following procedure:

Procedure 8-42 Import proxy cell information into the OMC-R

1

Log in as omcadmin.

From the Front Panel, select Xterm to bring up an xterm window.

Execute the following command:

/usr/omc/current/sbin/pcellImport <argument(s)>

Table 8-58 shows the command line options for pcellImport.

Table 8-58 Command line options for pcellImport

Argument

Description

-i<pathname>

Specifies the path where the file is located.

-i<pathname1><pathname2> <pathname3>

Specifies the paths for more than one file.

-d<directory_name>

Specifies a directory to import all files from.

NOTE
-i and -d options are mutually exclusive: only one can be used.
-a<omcName1><omcName2>

8-158

Specifies the name of the OMC-R to import

data from.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Use of neighbor information in the import file

NOTE

Each field in the import file must be separated by tabs. The first line must
contain the name of the parameters to import. Each subsequent line represents
cell values, one line per cell.

Help on the import feature is available by executing the following from the
command line: /usr/omc/current/sbin/pcellImport -help

It is possible to concatenate data from multiple OMC-R proxy cell data files into
a single file before importing.

It is also possible to manually add data from cells belonging to non Motorola
OMC-Rs before importing.

To check the progress of the import, examine the usr audit log files.

The name of the active OMC-R should be different on all the OMC-Rs in the
network.

Use of neighbor information in the import file

If the proxy cell import file contains neighborGsmCellIds at the end of a cell entry, the OMC-R
searches for CELLs with these cell ids in its database. For each cell found, the OMC-R creates a
Source object for it with the source_gsmCellId set to the gsmCellId included at the beginning of
the proxy cell import file cell entry. The omc_name of the Source is the same as the omc_name
in the proxy cell import file entry. This ensures that when a CELL has a Neighbor that exists
at another OMC-R, the Source object is created on the remote OMC-R whenever proxy cell
synchronization is performed across OMC-Rs. In this way, if OMC-Rs are regularly synchronized,
all source and neighbor information is consistent across all OMC-Rs.
If the Source object exists in the OMC-R importing the file, but the omc_name of the Source is
different to the omc_name at the beginning of the proxy cell import file cell entry, the omc_name
of the Source is updated to match the omc_name at the beginning of the proxy cell import file
cell entry.
If the gsmCellId of the Source object matches the gsmCellId at the beginning of the import
file cell entry, but the gsmCellId of the parent CELL of the Source is not found in the
neighborGsmCellIds in the entry, the Source object is deleted.
For further information on Neighbors and Source objects, see Neighbors, Sources and
Reciprocal Neighbors on page 8-106.

68P02901W17-T

8-159
Jan 2010

Synchronizing all OMC-R proxy cells within a network

Chapter 8: Configuring cells

Synchronizing all OMC-R proxy cells within a network

Synchronizing all OMC-R proxy cells

If more than one OMC-R exists on the network, the proxy cell information may be synchronized
between all OMC-Rs by running the script:
/usr/omc/current/sbin/pcellSync
All the proxy cell information for each OMC-R on the network is exported to one file. The file is
transferred to all the OMC-Rs on the network and imported automatically.
Synchronization can be started from any OMC-R on the network.
The following conditions must be set to allow proxy cell synchronization to occur between all
OMC-Rs on the network:

Once the first (Active) OMC-R has been created on the Navigation Tree, the remainder
of the OMC-Rs in the network must be created as inactive. The OMC-R names should be
unique across the network.

Each OMC-R must include all the other OMC-Rs entries in its /etc/hosts and
/etc/hosts.equiv files.

A file hostname.txt must be created in directory /usr/omc/config/global. This file must

contain the UNIX hostname of other OMC-Rs in the network, with one name per line.

Be careful to enter the correct UNIX hostname of each OMC-R, when creating OMC-R
objects in the MIB.

Changing LAC-CI of proxy cell

The associated proxy cell of a neighbor OMC-R must be updated if a BSS has a LAC-CI change.
Change this associated proxy cell through the OMC-R GUI with the following procedure:

Procedure 8-43 Change associated proxy cell from the OMC-R GUI
1

Select the proxy cell.

Select Edit mode.

Enter the new LAC-CI.

From the menu bar, select File Save to save the changes.
The save propagates the change to the affected
sources/neighbors/DRI/RTF/parent site and child objects.
The MIB Propagation form is displayed.
Continued

8-160

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Procedure 8-43
5

Changing LAC-CI of proxy cell

Change associated proxy cell from the OMC-R GUI (Continued)

Check the propagation is successful for all sources/neighbors affected.

A single source cell may not be updated due to a lock on the object.

NOTE
The failures, and resolve manually (open affected Neighbor
Detailed View and edit).
6

68P02901W17-T

Upload each affected NE database to the OMC-R.

8-161
Jan 2010

Dynamic propagation of proxy cell data to OMC-Rs

Chapter 8: Configuring cells

Dynamic propagation of proxy cell data to OMC-Rs

Overview of dynamic propagation

If a proxy cell related Cell parameter is changed, for example through a Detailed View, the
cell change may be propagated to the relevant proxy cells in all other OMC-Rs. This occurs
automatically if the environment variable PROXYCELL_UPDATE is enabled, that is, the variable
is set to 1.
Refer to: Introduction to proxy cells on page 8-141 for details.

Prerequisites for dynamic propagation

The following steps must be carried out to allow dynamic propagation to occur between all
OMC-Rs on the network.

Once the first (Active) OMC-R has been created on the Navigation tree, the remainder of
the OMC-Rs in the network must be created as inactive.

When creating each OMC-R on the network, the UNIX Host Name must be entered.

Each OMC-R must include all the other OMC-Rs entries in its /etc/hosts and
/etc/hosts.equiv files.

Rules for dynamic propagation

It is not possible to have multiple dynamic updates occurring on an OMC-R at the same time. An
example where this may occur is during an audit.
If a situation arises that a dynamic propagation is occurring on an OMC-R and another is
initiated, the values are stored in a file on the OMC-R. The file is stored in the following location:
/usr/omc/ne_data/proxycell_data/ProxyCellUpdate.<omc_name>
After a period of time which is specified by the parameter PROXYCELL_UPDATE_PERIOD,
the file is used to update the proxy cell data.

8-162

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Expanding the capacity of a cell

Expanding the capacity of a cell

Recommendation for expanding cell capacity

Expansion of a cell involves the addition of new DRIs and RTFs. To carry out this cell expansion,
Motorola recommends using the Navigation Tree.

Prerequisites for expanding cell capacity

Before expanding the capacity of a cell, ensure:

A BCCH RTF exists for the cell.

The site has the capacity for the extra RF hardware.

Expanding cell capacity

To add extra capacity to a cell, follow these steps:

Procedure 8-44 Add extra capacity to a cell

1

Find the DRI and RTF groups matching the cell to be expanded.

NOTE
The DRIs and RTFs must have the same group number (that
is, DRI 0 0 matches RTF 0 0 or RTF 0 1. DRI 0 0 does not
bring RTF 1 0 or RTF 1 1 into service).
2

Configure the RTFs and DRIs under these DRI/RTF groups that provide
the RF hardware to bring the timeslots on air.

Configure hopping as part of the RTF create.

Configure up to four Frequency Hopping objects, as required,

using the FreqHopSys object under the cell using the Navigation
Tree.

Add the RTFs to the paths configured for the site.

Unlock the new DRI/RTF and ensure each DRI and RTF configured
for the cell is in service.

If required, increase the number of SDCCHs allocated to the cell.

Continued

68P02901W17-T

8-163
Jan 2010

Expanding cell capacity

Chapter 8: Configuring cells

Procedure 8-44

8-164

Add extra capacity to a cell (Continued)

Verify that the cell is processing calls on the new RTF, using the
disp_rtf_chan and disp_cell_status TTY commands.

If cells within the SITE are not processing calls, refer to Checking
key site parameters on page 7-59, which describes how to check the
settings of tru_id, max_dris per GPROC and antenna_select number.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring frequency hopping

Configuring frequency hopping

Frequency hopping
Frequency hopping enables each timeslot to use a set of frequencies defined in one of four
frequency hopping systems. For further details of frequency hopping, see Frequency hopping on
page 2-4

Methods for configuring frequency hopping

To configure frequency hopping, use one of the following methods:

OMC-R GUI Navigation Tree, see Configuring frequency hopping using the OMC-R GUI
on page 8-167.

TTY interface, see Configuring frequency hopping using the TTY interface on page 8-175.

To check existing frequency hopping for a cell, see Checking frequency hopping configuration
for cells on page 8-178.

Frequency hopping parameters

Table 8-59 describes the frequency hopping-related cell parameters. Refer to: Technical
Description: BSS Command Reference (68P02901W23) for complete information on commands
and database parameters.

Table 8-59 Frequency hopping cell parameters

Field name/parameter name

Brief description

hopping_support

Defines the type of frequency hopping available; no

hopping, synthesizer hopping, or baseband hopping. This
can be configured from the CELL Detailed View. See
Frequency hopping on page 2-4 for more information about
frequency hopping.

hopping_systems_enabled

Provided for each of the four frequency hopping systems

to permit enabling and disabling hopping systems
individually. This can be configured from either of the four
FreqHopSys Detailed Views.
Continued

68P02901W17-T

8-165
Jan 2010

Frequency hopping parameters

Table 8-59

Chapter 8: Configuring cells

Frequency hopping cell parameters (Continued)

Field name/parameter name

Brief description

hopping_systems_hsn

Provided for each of the 16 frequency hopping systems to

define either cyclic or one of 63 pseudo-random hopping
sequence algorithms. The HSN (hopping sequence
[generator] number) is defined in GSM Recommendation
5.02. A pseudo-random hopping sequence algorithm
provides better interferer diversity than the cyclic
sequence. This can be configured from either of the four
FreqHopSys Detailed Views.

hopping_systems_mobile_alloc

Provided for each of the four frequency hopping systems

and contains a list of the carrier frequencies used in the
hopping system. This can be configured from either of the
four FreqHopSys Detailed Views.

NOTE
The hopping parameters are defined using the chg_element command or using the
OMC-R GUI Cell and FreqHopSys Detailed Views.

8-166

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring frequency hopping using the OMC-R GUI

Configuring frequency hopping using the OMC-R GUI

Overview of configuring frequency hopping using the OMC-R

GUI
Configuring frequency hopping using the OMC-R GUI is a two stage process:
1.

Configuring frequency hopping for a cell, see Configuring frequency hopping for a
cell using the OMC-R GUI in this section.
Once a FreqHopSys has been configured under a cell, it is available to all of the timeslots
in all of the RTFs for that cell (frequency planning limits excluded).

2.

Assigning a hopping system to each RTF hopping timeslot. For further details see
Configuring an RTF function on page 9-182.

Description of configuring frequency hopping using the OMC-R

GUI
Two windows are available in the OMC-R GUI to configure frequency hopping; the Mobile
Allocation Selector window (displayed from the FreqHopSys Detailed View) and the Frequency
Hopping View.
The information displayed in the FreqHopSys Detailed View is created during an audit and
cannot be changed.

Mobile Allocation Selector window

The Mobile Allocation Selector window enables the operator to set the BSS database parameter
hopping_systems_mobile_alloc for the FreqHopSys object. hopping_systems_mobile_alloc
allocates the Absolute Radio Frequency Channel Number (ARFCN) frequencies for hopping
(either baseband hopping or synthesizer hopping).
The maximum number of frequencies that can be configured is 64.
For a PCS1900 cell, when the BSS:pcs_freq_blocks attribute is 0, the Mobile Allocation
Selector form is not displayed. Instead, a message appears stating that there are no frequencies
to select from.
If the GSM900 Extended range cell is being configured, and if the cell attribute egsm_bcch_sd
is enabled, frequencies from both the normal GSM900 range and the GSM900 Extended
range can be selected at the same time. If this attribute is disabled, then attempting to select
frequencies from both ranges results in a warning message being displayed to the user.

68P02901W17-T

8-167
Jan 2010

Mobile allocation at a DCS1800 or PCS1900 site

Chapter 8: Configuring cells

Frequency Hopping View

The Frequency Hopping View enables the operator to view all the frequency hopping information
associated with all of the carriers in a cell (see Figure 8-8). The Frequency Hopping View is
a read only window with no editable fields.
The operation of these two forms is described in the following procedures.

NOTE
If the BCCH ARFCN is not included in the frequencies selected, then the maximum
number of frequencies that can be configured is reduced to 63.

Mobile allocation at a DCS1800 or PCS1900 site

The Mobile Allocation Selector window shown in Figure 8-7 is shown with values appropriate for
a GSM 900 cell. If the cell in question was at a DCS 1800 site, then the values presented would
be in the range 512 - 885. Similarly, if the cell supported PCS 1900, then the range presented
would be in the range 512 - 810, based on the individual bit settings of the BSS:pcs_freq_blocks
attribute as follows:
Bit 0: channels 512 to 585 (Frequency Block A)
Bit 1: channels 587 to 610 (Frequency Block D)
Bit 2: channels 612 to 685 (Frequency Block B)
Bit 3: channels 687 to 710 (Frequency Block E)
Bit 4: channels 712 to 735 (Frequency Block F)
Bit 5: channels 737 to 810 (Frequency Block C)
If the GSM 900 extended range of frequencies is being presented (0 - 124 and 975 - 1023), then
it is not possible to select frequencies from both the normal GSM 900 range (1 - 124) and
the extended GSM 900 range (0, 975 - 1023) at the same time unless the cell:egsm.bcch.sd
attribute is enabled.
Table 8-60 lists the maximum number of frequencies that may be allocated to the mobile
allocation list for a given cell frequency range, when configuring cell frequency hopping.

NOTE
If EGSM carrier Configuration is enabled, then it is allowed to mix PGSM and EGSM
extension band frequencies in the mobile allocation list.

8-168

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Impact of BCCH and SDCCH in the EGSM band

Table 8-60 Frequency hopping maximum frequency number

Frequency cell range
(ARFCNs used)

Maximum Number of frequencies allocated in mobile

allocation list.

1 to 124

64

975 to 1023

49

1 to 124, 975 to 1023

16

0,1 to 124

17

0,975 to 1023

17

0,1 to 124, 975 to 1023

17

If the containing cell is a dual band cell, the hopping_systems_mobile_alloc parameter can be
allocated frequencies from either the band specified in the frequency_type cell parameter or
the band specified in the secondary_frequency cell parameter, but not both.

Impact of BCCH and SDCCH in the EGSM band

If a cell has been configured with BCCH and SDCCH in the EGSM band, frequency hopping
systems can support the EGSM frequency bands (PGSM and GSM900 extension bands) in a dual
band system. For an EGSM cell, if the egsm_bcch_sd is not enabled, only the PGSM frequencies
or the extension band frequencies are put in the mobile allocation list, not both. See Configuring
a cell with BCCH and SDCCH in the EGSM band on page 8-179 for further details.

Configuring frequency hopping for a cell using the OMC-R GUI

To configure frequency hopping for a cell using the OMC-R GUI, follow these steps:

Procedure 8-45 Configure frequency hopping for a cell using the OMC-R GUI

68P02901W17-T

Navigate to and select the required FreqHopSys instance button

in the Navigation Tree (BSS BSS instance SITE SITE instance
Radio Frequency cell FreqHopSys FreqHopSys 0 to 3).
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details.
The FreqHopSys instance button changes color.

Select Edit Detailed View from the Navigation Tree menu bar.
The OMC-R displays the FreqHopSys Detailed View form.

Select Edit Edit from the menu bar.

The Detailed View changes from Monitor to Edit mode.

Complete the fields in the Identification, Additional Information, and

General groupings, as detailed in FreqHopSys Detailed View fields.

8-169
Jan 2010

Configuring frequency hopping for a cell using the OMC-R GUI

Chapter 8: Configuring cells

Specifying mobile allocation frequencies

To specify the mobile allocation frequencies, follow these steps:

Procedure 8-46 Specify mobile allocation frequencies

8-170

Select Edit Mobile Allocation from the FreqHopSys Detailed View

menu bar.
The OMC-R displays the Mobile Allocation Selector window (see
Figure 8-7). This window contains a list of available Absolute Radio
Frequency Channel Numbers (ARFCNs) from which new values may
be selected and old values deselected when in Edit mode. Figure 8-7
shows radio frequencies for a GSM 900 site, if required also see
Mobile allocation at a DCS1800 or PCS1900 site.

Select new frequencies for the mobile allocation ARFCN values by

clicking the appropriate frequency values.
To remove a selected frequency, click it.

Click OK when all the required frequencies have been selected.

If only one frequency is selected in the Mobile Allocation Selector
window, a message is displayed prompting for at least two frequencies.
The frequency values are transferred to the FreqHopSys Detailed View
form Mobile Allocation grouping ARFCN fields in ascending order.
To cancel a selection at any stage, click Cancel.

Select File Save from the menu bar to save the Detailed View and
set the value of the hopping_systems_mobile_alloc parameter at
the remote BSS.

Repeat from Procedure 8-45, step 4 for each FreqHopSys object, if

necessary.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

FreqHopSys Detailed View fields

Figure 8-7 Mobile Allocation Selector window - for a GSM 900 cell

ti-GSM-MobileAllocationSelectorwindow-foraGSM900cell-00805-ai-sw

FreqHopSys Detailed View fields

The following sections list and briefly describe the parameter fields in the FreqHopSys Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

68P02901W17-T

8-171
Jan 2010

FreqHopSys Detailed View fields

Chapter 8: Configuring cells

Identification grouping
Table 8-61 describes the fields in the Identification grouping of the FreqHopSys Detailed View.

Table 8-61 FreqHopSys Detailed View fields - Identification grouping

Field name

Brief description

Values

RDN Class

See description in Table 4-1.

Default is the
class name.

RDN Instance

See description in Table 3-1.

0 - 3.

NMC RDN Value

The OMC-R supports an interface to a

Network Management Centre (NMC).
This is identifier of the object on the
NMC interface.

Parent Detailed
View

Displays the parent cell name. Click

to display the parent CELL Detailed
View.

Mandatory or
Optional?

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this frequency hopping
system. Where additional notes are not required, close this field by clicking the toggle button
next to the Additional Information header.

General grouping
Table 8-62 describes the fields in the General grouping of the FreqHopSys Detailed View.

Table 8-62 FreqHopSys Detailed View fields - General grouping

Field name

Brief description

Values

Hopping Systems
Enabled

Enables or disables this frequency

hopping system.

Enabled (1) or
Disabled (0).

Hopping
Sequence
Number

The hopping sequence number to be

used by the frequency hopping system.

0 - 63.

Mandatory or
Optional?
Mandatory.
Optional.

Mobile allocation grouping

See Figure 8-7 for details.

8-172

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Viewing frequency hopping details for a cell

Viewing frequency hopping details for a cell

Displaying the Frequency Hopping View
To display a Frequency Hopping View, follow these steps:

Procedure 8-47 Display a Frequency Hopping View

1

Select the required cell in the OMC-R GUI Navigation Tree.

Select Config Mgt - Frequency Hopping from the Navigation Tree

menu bar.
The OMC-R displays the Frequency Hopping View window as shown in
Figure 8-8.
Alternatively, the Frequency Hopping View window can be displayed
from the CELL Detailed View by selecting Options - Frequency Hopping
from the menu bar.

Figure 8-8 Frequency Hopping View

ti-GSM-FrequencyHoppingView-00806-ai-sw

68P02901W17-T

8-173
Jan 2010

Viewing frequency hopping details for a cell

Chapter 8: Configuring cells

Displaying an RTF Detailed View

To display an RTF Detailed View form for one of the RTFs listed in the Frequency Hopping
View, follow these steps:

Procedure 8-48 Display RTF Detailed View form for an RTF listed in the Frequency
Hopping View
1

Double-click the required RTF line.

The OMC-R displays the RTF Detailed View form.

View or edit RTF Detailed View form as required.

Closing the Frequency Hopping View

To close the Frequency Hopping View, select File -Close from the Frequency Hopping View
window to close the form.
Alternatively, use File Save As to save the information in a file name.

Displaying a FreqHopSys Detailed View

To display a FreqHopSys Detailed View form for one of the Hopping Systems, follow these steps:

Procedure 8-49 Display a FreqHopSys Detailed View form for one of the Hopping
Systems

8-174

Navigate to the required cell and select the required FreqHopSys

instance.

Click the FreqHopSys button for which you want to display details.
The OMC-R displays the FreqHopSys Detailed View the corresponding
frequency hopping object in Monitor mode.

To edit the form, select Edit Edit from the menu bar.

Make the required changes.

Save the changes, and exit the form.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring frequency hopping using the TTY interface

Configuring frequency hopping using the TTY interface

Introduction to configuring frequency hopping using the TTY

interface
Defining frequency hopping systems is a SYSGEN process. The procedures described in this
section use the baseband hopping system as described in Frequency hopping on page 2-4.

Methods for configuring frequency hopping using the TTY

interface
Defining a hopping system for a cell using the TTY interface requires:
1.

Setting frequency hopping-related cell parameters using the TTY interface.

2.

Assigning a hopping system to each RTF timeslot.

These steps are described in the following sections.

Setting frequency hopping parameters using the TTY interface

To set up hopping-related cell parameters, follow these steps:

Procedure 8-50 Set up hopping-related cell parameters

68P02901W17-T

To establish the type of hopping supported at the cell, enter the

following command. All cells at the site must either be non-hopping or
use the same type of hopping system.
disp_element hopping_support <location> cell = <cell_desc>

To enable each of the four hopping systems for the cell, enter the
command:
chg_element hopping_systems_enabled,<fhi> <element_value>
<location> cell = <cell_desc>

To define the HSN for each hopping system, enter the command:
chg_element hopping_systems_hsn,<index> <element_value>
<location> <cell_number>

To define the mobile allocation for the frequency hopping system that
does not hop through the BCCH timeslot, enter the command:
chg_hop_params <cell_desc> <fhi> <f1> <f2> [f3]. . . <fn>

Repeat step 4 for the hopping system that does hop through the BCCH
timeslot.

8-175
Jan 2010

Assigning a hopping system to each RTF timeslot

Chapter 8: Configuring cells

Example

NOTE
The commands and examples shown in this section are typical instances for
demonstration purposes only. Enter only parameters specified by the system
engineers.
The following is example of setting up hopping-related cell parameters using the TTY interface.
-> disp_element hopping_support 0 0 0 1 0 1 1 3
COMMAND ACCEPTED
hopping = 0
-> chg_element hopping_systems_enabled,0 1 0 0 0 1 0 1 1 3
COMMAND ACCEPTED
->
chg_element hopping_systems_enabled,1 1 0 0 0 1 0 1 1 3
COMMAND ACCEPTED
->
chg_element hopping_systems_hsn,0 3 0 0 0 1 0 1 1 3
COMMAND ACCEPTED
->
chg_element hopping_systems_hsn,1 3 0 0 0 1 0 1 1 3
COMMAND ACCEPTED

Assigning a hopping system to each RTF timeslot

Once the hopping-related cell parameters have been set up, the next step is to assign a
frequency hopping system to each timeslot to enable it to hop. To assign a hopping system to
each timeslot using the TTY interface, use the equip command, and repeat for each non-BCCH
RTF function at the cell.
The following is example of assigning a hopping system to each RTF timeslot using the TTY
interface, and shows typical user input in bold text. Hopping is disabled for the BCCH carrier
timeslots as follows:
-> equip 0 RTF
Enter type of carrier:
Enter the 1st and 2nd RTF id:

8-176

0 1

Enter the GSM cell assigned to this carrier:

0 0 1 0 1 1 3

Enter carrier absolute radio freq.

52

channel:

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Assigning a hopping system to each RTF timeslot

Enter the 8 carrier frequency hopping indicators:

255

255 255 255 255 255 255 255

:
COMMAND ACCEPTED
-> equip 0 RTF
Enter type of carrier:

NON_BCCH

Enter the 1st and 2nd RTF id:

0 1

Enter carrier absolute radio freq.

channel:

32

Enter the 8 carrier frequency hopping indicators:

1 1 2 2 2 1 1 2

:
COMMAND ACCEPTED
Only certain RTF parameters are shown in the example above. Refer to: Technical Description:
BSS Command Reference (68P02901W23) for comprehensive command and parameter
information and Configuring an RTF function on page 9-182.

68P02901W17-T

8-177
Jan 2010

Checking frequency hopping configuration for cells

Chapter 8: Configuring cells

Checking frequency hopping configuration for cells

Overview to checking cell frequency hopping

NOTE
Customers extracting hopping and path information on a regular basis (part of data
harvest nightly, for example) should contact Motorola OMC-R Customer Support
for further information.

Checking a single hopping object using the OMC-R GUI

To check a single hopping object using the OMC-R GUI, proceed as follows:

Procedure 8-51 Check a single hopping object using the OMC-R GUI
1

Open a FreqHopSys Detailed View (BSS - BSS instance - SITE - SITE

instance - Radio Frequency - cell - FreqHopSys - FreqHopSys 0 to 3).

Check the Mobile Alloc settings.

To check the Frequency Hopping Indicator settings for the carriers

of the cell:

Open its associated RTF(s) or TRX(s).

Check under the Carrier 1 Information grouping.

Checking multiple hopping objects using cmutil

All the data for a FreqHopSys object can be viewed from a FreqHopSys Detailed View. However,
some of the data of each FreqHopSys object is stored in its generic table in the MIB DBMS
(freqhopsystable2). The only way to extract full information for multiple FreqHopSys objects
from the CM MIB is by using cmutil, see Chapter 15 cmutil for details.

Multiple hopping checks of OMC-R using cmutil

To check multiple hopping objects throughout the OMC-R using cmutil, see Chapter 15 cmutil.

8-178

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a cell with BCCH and SDCCH in the EGSM band

Configuring a cell with BCCH and SDCCH in the EGSM

band

Introduction to BCCH and SDCCH in the EGSM band

The Broadcast Control CHannel (BCCH) and Standalone Dedicated Control CHannel (SDCCH)
can be configured to operate in the Extended GSM900 (EGSM) band. If SDCCH is placed in
the EGSM, non-EGSM mobiles may not have service because they are unable to access the
BCCH frequency and SDCCH channels in the EGSM band. This enables a multi-band/dual-band
network with EGSM as one of the supported frequency bands, for example, EGSM and DCS1800.
The EGSM band can also be selected as the preferred band over the DCS1800 or GSM900.
The cell parameter egsm_bcch_sd (CELL Detailed View field: EGSM Carrier Configuration
Information) enables or disables the BCCH and SDCCH channels in the EGSM band. If the
Frequency Type field in the CELL Detailed View is set to a value other than EGSM900 (2), this
field is grayed-out in the OMC-R GUI and displays Disabled (0).
For an EGSM cell, if egsm_bcch_sd is disabled only either PGSM or Extension band frequencies
can be entered in the mobile allocation list, not both.

Impact on Frequency Hopping (FreqHopSys)

This feature also allows frequency hopping systems to support the EGSM frequency bands
(PGSM and GSM900 extension bands) in a dual band system. For an EGSM cell, if egsm_bcch_sd
is not enabled, only the PGSM frequencies or the extension band frequencies are put in the
mobile allocation list, not both.

Impact on RTFs
When egsm_bcch_sd is enabled for a cell and carrier type is BCCH, the RTF parameter field
Carrier 1 ARFCN (BSS parameter name: arfcn) can be set to EGSM band frequencies.

Impact on Proxy cells

The frequency range for proxy cells also includes EGSM band frequencies.

Methods of configuring BCCH and SDCCH in the EGSM band

To configure a cell to use BCCH and SDCCH in the EGSM band, use either the:

OMC-R GUI CELL Detailed View, using the EGSM Carrier Configuration Information field
(egsm_bcch_sd), see Table 8-2.

TTY interface to set the egsm_bcch_sd parameter to Enabled (1).

68P02901W17-T

8-179
Jan 2010

Prerequisites for disabling BCCH and SDCCH in the EGSM band

Chapter 8: Configuring cells

Prerequisites for disabling BCCH and SDCCH in the EGSM band

The parameter egsm_bcch_sd can only be disabled if:

BCCH is not in the EGSM.

sd_load is zero for all carriers in the EGSM.

Hopping systems (enabled and disabled) do not contain a combination of PGSM and EGSM
band frequencies.

Neighbor BCCH frequencies are not in the EGSM band.

Configuring a cell with BCCH and SDCCH on EGSM using the

TTY interface
To create a cell with BCCH and SDCCH in the EGSM using the TTY interface, follow these steps:

Procedure 8-52

8-180

Create a cell with BCCH and SDCCH in the EGSM using TTY interface

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Use the frequency_type parameter to set the cell frequency to 2

(EGSM900).

Enable the egsm_bcch_sd parameter by setting it to 1. For example:

chg_element egsm_bcch_sd 1 3 cell00101121
A typical OMC-R response is shown below, for example:
Set egsm_bcch_sd for site 3 in cell 00101121 such that the
BCCH frequency and SDCCH channels are allowed in the GSM
Extension band for an EGSM cell:
chg_element egsm_bcch_sd 1 3 cell 0 0 1 0 1 1 2 1
COMMAND ACCEPTED
See Technical Description: BSS Command Reference (68P02901W23)
for further details of these command and parameters.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a cell for coincident multiband handovers

Configuring a cell for coincident multiband handovers

Overview of coincident multiband handovers

A coincident cell is a cell that has a collocated neighbor cell, and both cells have the same cell
boundaries but each cell operates on a different frequency (such as 900, 1800, or 1900). A
coincident cell can hand over calls to its collocated neighbor.
For a detailed description of coincident multiband handover, see Technical Description: BSS

Implementation (68P02901W36).
Coincident multiband handovers (controlled using coincident_mb) and the Dual Band Cells
feature cannot be enabled at the same time. For example, when inner_zone_alg is set to Dual
Band Cells (3) and an attempt is made to set the value of coincident_mb to anything other
than 0, an error message is displayed. Alternatively, in the OMC-R GUI the coincident_mb
field is grayed-out.

Interaction with other features

This feature interacts with the IMRM feature, see for further details.

Coincident multiband handover parameters

Table 8-63 details the parameters associated with coincident multiband handover.

Table 8-63 Coincident multiband handover parameters

OMC-R GUI field
name/BSS parameter
name
Coincident MB HO
Status
coincident_mb

Description
See Table 2-5 for details of this parameter.

Continued

68P02901W17-T

8-181
Jan 2010

Prerequisites to configuring a coincident multiband cell

Chapter 8: Configuring cells

Table 8-63 Coincident multiband handover parameters (Continued)

OMC-R GUI field
name/BSS parameter
name

Description

Coincident Cell
coincident_cell

Displayed in the General section, Coincident Multiband HO grouping,

of the CELL Detailed View.
Specifies the cell (unique GSM cell identifier) that is coincident to
the cell specified in the chg_cell_element coincident_mb prompt
or the disp_cell command. This parameter may only be changed
if the Coincident MultiBand Handover option is unrestricted. If
coincident_mb is set to 1 or 2, both cells must be SACCH neighbors
of each other. If coincident_mb is set to 2, both cells must be at the
same site, the cells must be neighbors of each other, and the basic
settings must be the same. A cell cannot be coincident to itself.
In the CELL Detailed View, to enter the coincident cell id as a name,
rather than as a decimal or hexadecimal number, click the CellId
button.
This field is grayed-out if the Coincident MB HO Status parameter
field is set to Disabled (0).
The MCC and MNC subfields within the cell id can be edited. The
MCC and MNC fields cannot be edited for n-1 or n-2 BSS.

Coincident Offset to
HO Margin
coincident_offset

Displayed in the General section, Coincident Multiband HO grouping,

of the CELL Detailed View.
Specifies the value added to the handover margin (ho_margin) when
handover is based on receive level from the serving cell. Valid value
range is: -63 to +63. The default is 0. This value is only used when
the handover of a multiband MS is based on the receive level from
the serving cell. Enter a value in the range -63 to 63. The default is 0.

Coincident Low Sig

Threshold
low_sig_thresh

Displayed in the General section, Coincident Multiband HO grouping,

of the CELL Detailed View.
Specifies the value of receive level that must be exceeded by a
coincident cell to cause a handover to that cell. Valid value range is:
0 - 63. The default is 0. low_sig_thres of the external neighbors
cannot be accessed.

Prerequisites to configuring a coincident multiband cell

Before a cell can be defined as a coincident multiband handover cell, the Multiband Inter-cell
Handover feature (mbInterCellHoOpt) must be unrestricted (enabled) at the BSS.
Before Cell A can be defined as coincident to Cell B, Cell A must be added to the neighbor list
of Cell B.

8-182

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Methods of configuring a cell for coincident multiband handover

Methods of configuring a cell for coincident multiband handover

A cell can be configured for coincident multiband handover, using either of the following
methods:

OMC-R GUI CELL Detailed View General section, Coincident Multiband HO grouping.

TTY interface, see Configuring a coincident multiband handover cell using the
TTY interface.

Configuring a coincident multiband handover cell using the

TTY interface
The TTY interface can be used to configure a cell. The following sections indicate the BSS
commands and parameters that can be used to create, display, and modify coincident multiband
handover parameters.
For further details of these commands and parameters see the Technical Description: BSS
Command Reference (68P02901W23) manual. Also see Table 8-63 in this section for details of
the coincident multiband handover parameters.

Creating a coincident multiband handover cell

To create a cell and specify all the cell parameters, including the coincident multiband handover
parameters, use the following command:
add_cell <gsm_cell_id> <location>
The BSS then prompts for each of the cell parameters.

Enabling/Disabling coincident multiband handover for a cell

First, to display whether the coincident multiband has been enabled or disabled, use either the
disp_cell or disp_element commands, and coincident_mb parameter. For example, the
following command displays whether coincident multiband is enabled for cell 001 01 17:
disp_element coincident_mb 1 cell 0 0 1 0 1 1 7
To enable or disable coincident multiband, use either chg_element or chg_cell_element
commands and the parameter coincident_mb. For example, the following command enables
(without redirection) coincident multiband at gsmcellid: 0010117:
chg_cell_element coincident_mb 1 1 cell 0 0 1 0 1 1 7
The system prompts for the coincident cell id (an example user response is shown in bold text):
Enter the coincident cell:

68P02901W17-T

0 0 1 0 1 1 6

8-183
Jan 2010

Configuring a coincident multiband handover cell using the TTY interface

Chapter 8: Configuring cells

Changing the value added to the handover margin using the TTY interface
First, display the current value added to the H0_margin, using the disp_element command and
the coincident_offset parameter, for example:
chg_element coincident_offset 1 cell 0 0 1 0 1 1 7
The system replies with the current setting.
To change the value added to the ho_margin, use the chg_element or chg_cell_element
commands. For example, the following command adds the value 60 to the handover margin at
gsmcellid: 0010117:
chg_element coincident_offset 60 1 cell 0 0 1 0 1 1 7

Changing the receive value for low signal handover using the TTY interface
First, display the current value of the low signal handover threshold, using the disp_element
command and the low_sig_thresh parameters, for example:
chg_element low_sig_thresh 1 cell 0 0 1 0 1 1 7
The system replies with the current setting.
To change the value of the low signal handover threshold, use the chg_cell_element or
chg_element commands. For example, the following command sets the handover threshold to
60 at gsmcellid: 0010117:
chg_element low_sig_thresh 60 1 cell 0 0 1 0 1 1 7

Displaying the coincident cell of a cell

To display the id of a coincident cell, use the coincident_cell parameter and the disp_element
command, for example:
disp_element coincident_cell 1 cell 0 0 1 0 1 1 7
The system replies with the gsmcellid of the coincident cell.

8-184

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a cell for adaptive handovers

Configuring a cell for adaptive handovers

Overview of adaptive handovers

A cell that can perform adaptive handovers hands over calls to the next cell more rapidly when
call conditions are deteriorating quickly. Likewise, when call conditions are only marginally
poor, the calls are handed over less quickly. The cell therefore performs adaptive handovers
based on the rate at which the radio conditions change for the mobile.
Adaptive handovers can only occur at microcell sites.
Handovers normally occur based on a voting criteria, that is, when a specified quantity of the
most recent measurement averages meet a specific criterion then the need for a handover is
recognized. For adaptive handovers, a cumulative area is maintained and updated with each
new measurement. As long as a marginal need for a handover exists the cumulative area is
incremented (except for adaptive power budget handovers where the leaky bucket criteria is
used). The cumulative area is set to zero when there is no marginal need for a handover. When
the cumulative area exceeds a user-defined threshold value, a handover is triggered.
Adaptive handovers can be enabled for:

Power budget handovers

Uplink and downlink quality handovers

Uplink and downlink level handovers

A cumulative area threshold value for each type of handover can be defined. For quality
handovers if cell hopping has been enabled, alternative cumulative area thresholds can be
defined.
The cumulative area for the power budget handover algorithm can be set on a per cell or
per neighbor basis. The cumulative area for adaptive level and quality handovers remain on
a per cell basis only.
The way in which Type 3 and Type 5 handover algorithms function have also been modified in
line with this feature.
For a detailed description of handovers, adaptive handovers, and handover algorithms, see the
manual Technical Description: BSS Implementation (68P02901W36).

Adaptive handover parameters

Table 8-64 details the parameters associated with adaptive handovers. A full description
of BSS database parameters is provided in Technical Description: BSS Command Reference
(68P02901W23).

68P02901W17-T

8-185
Jan 2010

Adaptive handover parameters

Chapter 8: Configuring cells

Table 8-64 Adaptive handover parameters

OMC-R GUI field name/BSS
parameter name
Adaptive Pwr Budget HO
Alg
adap_ho_pbgt

Description
Displayed in the CELL Detailed View Handover section,
Adaptive Handovers grouping.
Specifies which of the following power budget handover
algorithms is used:

Standard power budget handover algorithm (0).

Adaptive power budget handover algorithm on a per cell

basis for a cumulative area (1).

Adaptive power budget handover algorithm on a per

neighbor basis for a cumulative area (2).

Also see Configuring a neighbor cell for adaptive handovers

on page 8-190.
Adaptive Pwr Budget HO
Trigger
adap_trigger_pbgt

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies the value used as a threshold with the adaptive power
budget handover algorithm on a per cell basis used to determine
when handover should occur. Valid value range: 0 - 255. The
default is 0.

Neighbor Adap Pbgt HO

Trigger
adap_trigger_pbgt_nbr
(OMC-R database name:
adap_trg_pbgt_nbr)

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies the value used as a threshold with the adaptive power
budget handover algorithm on a per neighbor basis used to
determine when handover should occur. Valid value range: 0 255. The default is 40.

Adaptive Rxlev HO Alg

adap_ho_rxlev

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies whether the adaptive receive level handover algorithm
is Enabled (1) or Disabled (0). The default is Disabled (0).

Adaptive Rxlev HO Trigger

on DL
adap_trigger_rxlev_dl
(OMC-R database
parameter name:
adap_trig_rl_dl)

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies the value used to determine when to handover when
using the Adaptive Receive Level Handover Trigger algorithm
on the downlink (BSS to MS). Valid value range: 0 - 255. The
default is 0.

Adaptive Rxlev HO Trigger

on UL
adap_trigger_rxlev_ul
(OMC-R database
parameter name:
adap_trig_rl_ul)

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies the value used to determine when to handover when
using the Adaptive Receive Level Handover Trigger algorithm
on the uplink (MS to BSS). Valid value range: 0 - 255. The
default is 0.

Adaptive Rxqual HO Alg

adap_ho
_rxqual

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies whether the adaptive receive quality handover
algorithm is Enabled (1) or Disabled (0). The default is Disabled
(0).
Continued

8-186

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adaptive handover parameters

Table 8-64 Adaptive handover parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Adaptive Rxqual HO
Trigger on DL
adap_trigger
_rxqual_dl
(OMC-R database
parameter name:
adap_trig_rq_dl)

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies the value used to determine when to handover when
using the Adaptive Receive Quality Handover Trigger on the
downlink. Valid value range: 0 - 65535. The default is 0.

Adaptive Rxqual HO
Trigger on UL
adap_trigger
_rxqual_ul
(OMC-R database
parameter name:
adap_trig_rq_ul)

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies the value used to determine when to handover when
using the Adaptive Receive Quality Handover Trigger on the
uplink. Valid value range: 0 - 65535. The default is 0.

Adaptive Alt Trigger Rxqual

HO
adap_ho_alt_trigger
_rxqual
(OMC-R database
parameter name:
adap_ho_al_trg_rq)

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies whether the adaptive alternate trigger receive quality
handover algorithm is Enabled (1) or Disabled (0). The default
is Disabled (0).

Adap Rxqual Hop HO

Trigger DL
adap_trigger_hop
_rxqual_dl
(OMC-R database
parameter name:
adap_trg_hop_rqdl)

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies the value used to determine when to handover when
using the Adaptive Receive Quality Hopping Handover algorithm
on the downlink. Valid value range: 0 - 65535. The default is 0.

Adap Rxqual Hop HO

Trigger UL
adap_trigger_hop
_rxqual_ul
(OMC-R database
parameter name:
adap_trg_hop_rqul)

Displayed in the CELL Detailed View Handover section,

Adaptive Handovers grouping.
Specifies the value used to determine when to handover when
using the Adaptive Receive Quality Hopping Handover algorithm
on the uplink. Valid value range: 0 - 65535. The default is 0.

Type 5 HO Margin
ho_margin_type5

Specifies the value used to determine the handover margin used

in the Optimized Type 5 Handover Algorithm, or whether the
Optimized Type 5 Handover Algorithm is disabled (63). Valid
value range is -63 to 63. The default is 63.
In theory, a Power Budget value of 63 can never be reached,
therefore setting this parameter to 63 is seen as disabling the
Optimized Type 5 Handover algorithm.

68P02901W17-T

8-187
Jan 2010

Methods of configuring a cell for adaptive handovers

Chapter 8: Configuring cells

Methods of configuring a cell for adaptive handovers

To configure a cell for adaptive handovers, use either of the following methods:

OMC-R GUI CELL Detailed View Handover section, Adaptive Handovers grouping.

TTY interface, see Configuring a cell for adaptive handovers using the TTY interface
in this section.

Configuring a cell for adaptive handovers using the TTY

interface
The TTY interface can be used to configure a cell, including specifying the adaptive handover
parameters. The following sections indicate the BSS commands and parameters that can be
used to create, display, and modify adaptive handover parameters.
For further details of these commands and parameters, see the Technical Description: BSS
Command Reference (68P02901W23) manual. Also see Table 8-64 in this section for details of
the adaptive handover parameters.
Security Level 2 is needed to enter these TTY commands.

Creating an adaptive handover cell

To create a cell and specify all the cell parameters, including the adaptive handover parameters,
use the add_cell command. In response to this command, the BSS prompts for each of the
cell parameters.

Enabling/Disabling adaptive handovers for an existing cell

First, to display whether adaptive handovers have been enabled or disabled, use either the
disp_cell or disp_element commands, and the appropriate adap_ho_pbgt, adap_ho_rxlev,
adap_ho_rxqual, adap_ho_al_trg_rq parameter. For example, the following command displays
whether Adaptive Power Budget Handover is enabled at BSC (site 0) for cell 001 01 17:
disp_element adap_ho_pbgt 0 cell 0 0 1 0 1 1 7
To enable or disable, use either chg_element or chg_cell_element commands and
the appropriate parameter: adap_ho_pbgt, adap_ho_rxlev, adap_ho_rxqual or
adap_ho_al_trg_rq. For example, the following command enables Adaptive Power Budget
Handovers on a per neighbor basis at the BSC (site 0) at the cell 0010117:
chg_cell_element adap_ho_pbgt 2 0 cell 0 0 1 0 1 1 7

8-188

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Configuring a cell for adaptive handovers using the TTY interface

Changing the value of an adaptive handover trigger threshold

First, display the current value of the adaptive handover triggers, using the
disp_element or disp_cell command and the appropriate handover trigger parameter:
adap_trigger_pbgt, adap_trigger_rxlev_dl, adap_trigger_rxlev_ul, adap_trigger_rxqual_dl
adap_trigger_rxqual_ul, adap_trigger_hop_rxqual_dl l or adap_trigger_hop_rxqual_d. For
example, the following command displays the current setting of the cumulative trigger for the
Adaptive Power Budget Handovers at BSC (site 0) at cell 0010117:
disp_element adap_trigger_pbgt 0 cell 0 0 1 0 1 1 7
The system replies with the current setting of the threshold.
To change the value of adap_trigger_pbgt, adap_trigger_rxlev_dl, adap_trigger_rxlev_ul,
adap_trigger_rxqual_dl adap_trigger_rxqual_ul, adap_trigger_hop_rxqual_dl l or
adap_trigger_hop_rxqual_d use the chg_element or chg_cell_element command. For
example, the following command sets the cumulative area threshold for the Adaptive Power
Budget Handovers to 1000 at BSC (site 0) at cell 0010117:
chg_element adap_trigger_pbgt 1000 0 cell 0 0 1 0 1 1 7

68P02901W17-T

8-189
Jan 2010

Configuring a neighbor cell for adaptive handovers

Chapter 8: Configuring cells

Configuring a neighbor cell for adaptive handovers

Overview of configuring a neighbor cell for adaptive handovers

To configure a neighbor cell for handovers it may be necessary to:

Set a handover margin for the Optimized Type 5 Handover algorithm, using:
Neighbor Detailed View form.
BSS database parameter ho_margin_type5.
The Optimized Type 5 Handover algorithm (macrocell to microcell handover) is
explained in Technical Description: BSS Implementation (68P02901W36).

Define the trigger value for the Adaptive Power Budget Handover algorithm, if the cell is
functioning on a neighbor basis. (If the cell is functioning on a cell basis, see Configuring a
cell for adaptive handovers on page 8-185). This can be done using:
Neighbor Detailed View form.
BSS database parameter adap_trigger_pbgt_nbr.

Configuring a neighbor cell for adaptive handovers using the

OMC-R GUI
To configure a neighbor cell for adaptive handovers using the OMC-R GUI for a new or existing
neighbor cell, following these steps:

Procedure 8-53 Configure a neighbor cell for adaptive handovers using the OMC-R
GUI
1

Display the required Neighbor Detailed View form.

If modifying an existing neighbor cell, select Edit Edit to change

from Monitor to Edit mode. Otherwise go to step 1.

Defining the Adaptive Power Budget Handover algorithm threshold

To set the handover threshold for the Adaptive Power Budget Handover algorithm, enter a value
in the range 0 - 255 in the Neighbor Adap Pbgt HO trigger field in the General parameter
grouping. See Table 8-64 for further details for this parameter, or use the online context
sensitive help for the field.

8-190

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Configuring a neighbor cell for handovers using the TTY interface

Setting the Optimized Type 5 Handover algorithm handover margin

To set the handover threshold for the Optimized Type 5 Handover algorithm, follow these steps:

Procedure 8-54 Set the handover threshold for the Optimized Type 5 Handover
algorithm
1

Use the scroll bar to display the Power Budget Algorithm parameter
grouping.

Enter a value for the handover margin for the Optimized Type 5
Handover algorithm in the Type 5 HO Margin field. See Table 8-64 for
further details for this parameter, or use the online context sensitive
help for the field.

Saving and closing

To save and close the Detailed View form, follow these steps:

Procedure 8-55

Save and close the Detailed View form

Complete or modify other neighbor fields, as required.

Select File Save from the menu bar to save the changes.

Select File Close to close the Neighbor Detailed View form.

Configuring a neighbor cell for handovers using the TTY

interface
The TTY interface can be used to configure a neighbor cell. The following sections indicate how
to create, display, and modify the ho_margin_type5 and adap_trigger_pbgt_nbr parameter.
For further details of these commands and parameters, see the Technical Description: BSS
Command Reference (68P02901W23) manual. Also see Table 8-64 in this section for details of
the ho_margin_type5 and adap_trigger_pbgt_nbr parameters.
Security Level 2 is needed to enter these TTY commands.

Displaying the current neighbor settings

First, display the current value of ho_margin_type5 or adap_trigger_pbgt_nbr using the
disp_neighbour command. For example, the following command displays the current settings
in the neighboring cell 001 0112 of cell 0010114:
disp_neigh 0 0 1 0 1 1 4 0 0 1 0 1 1 2
The system replies with the current settings for the neighbor cell, including the setting for
Optimized Type 5 Handover algorithm margin and the Adaptive Power Budget Handover
algorithm threshold.

68P02901W17-T

8-191
Jan 2010

Configuring a neighbor cell for handovers using the TTY interface

Chapter 8: Configuring cells

Changing the current settings

To change the value of ho_margin_type5 and adap_trigger_pbgt_nbr use the
modify_neighbor command.
For example, the following command sets the margin for the Optimized Type 5 Handover
algorithm to 10 in the neighboring cell 001 0112 of cell 0010114:
modify_neighbor 0 0 1 0 1 1 4 0 0 1 0 1 1 2 ho_margin_type5 10
The following command sets the adaptive handover power budget threshold trigger to 38
for neighbor cell 001 0112 of cell 0010111:
modify_neighbor 0 0 1 0 1 1 1 0 0 1 0 1 1 2 adap_trigger_pbgt_nbr 38

8-192

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Limiting Ping-Pong handovers between cell zones

Limiting Ping-Pong handovers between cell zones

The system provides control over the frequency of inter-zone ping-pong handovers. This
prevents a call from constantly changing zones, which, in turn, improves voice quality and
reduces the workload on the BSS.

Ping-Pong handover limitation parameters

Table 8-65 shows the parameters used to configure ping-pong control. These can be set using
MMI or in the OMC-R GUI and are supported by the cmutil tool.

Table 8-65 Ping Pong limitation parameters

OMC-R GUI field name/BSS
parameter name

Description

Interzone PingPong
Allowed Count
zone_pingpong_count

Displayed in the CELL Detailed View General

grouping. Indicates how many times zone ping-pong
handover is allowed during the time in which the
frequency of interzone ping-pong handovers are
measured (as set by zone_pingpong_enable_win).

Interzone PingPong
Enabled Timer
zone_pingpong_enable
_win

Displayed in the CELL Detailed View General

grouping. Indicates the length of time in which the
frequency of interzone ping-pong handovers are
measured (seconds).

Interzone_PingPong
Disabled Timer
zone_pingpong_disable
_win

Displayed in the CELL Detailed View General

grouping. Indicates the length of time during
which zone ping-pong handovers are not allowed
during the time in which the frequency of interzone
ping-pong handovers are measured (as set by
zone_pingpong_enable_win) after ping-pong
handover has happened zone_pingpong_count times.

Preferred PingPong Target

Zone zone_pingpong
_preferred_zone

Displayed in the CELL Detailed View General

grouping. Indicates which zone is preferred as the hop
target zone.

68P02901W17-T

8-193
Jan 2010

Configuring Ping-Pong handover parameters using the OMC-R GUI

Chapter 8: Configuring cells

Configuring Ping-Pong handover parameters using the OMC-R

GUI
To set the ping-pong handover parameters, follow the steps in Procedure 8-56.

Procedure 8-56 Setting ping-pong handover parameters

View the General grouping in the BSS Detailed View form (see General
grouping on page 4-19).

Locate the parameter(s) to be configured.

Enter the values as appropriate in the parameter fields.

NOTE
The range values of the parameters are provided in Table 4-7.
4

Save and close the BSS Detailed View form.

Configuring Ping-Pong handover parameters using the TTY

interface
The TTY interface can be used to configure ping-pong handover parameters. To display
and change the ping-pong parameters use the disp_element and chg_element commands
respectively.
For example, to display zone_pingpong_enable_win, use the following command:
disp_element zone_pingpong_enable_win 0
To change the value of zone_pingpong_preferred_zone to inner zone, use the following
command:
chg_element zone_pingpong_preferred_zone 1 0
For further details of these commands and parameters, see the Technical Description: BSS
Command Reference (68P02901W23) manual.

8-194

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a cell for flexible neighbor cell processing

Configuring a cell for flexible neighbor cell processing

Introduction to flexible neighbor cell processing

The handover decision process can be modified by adding more flexibility to the way in which
neighbor cell processing is performed for handovers.
Flexible neighbor cell processing can be configured to:

Allow neighbors with a lower RxLev than the serving cell to be valid candidates for
handover.

Include neighbor cells whose disuse count is less than or equal to the maximum disuse
count. Disuse count is defined as the number of consecutive measurement reports a
previously reported neighbor is not reported by the MS.

Use RxQual or RxLev handovers only when the BTS or MS is at full power. Removes all
candidates for interference handovers until BTS or MS reach full power. Applicable only
for decision algorithm 1.

Allow no warm-up period for neighbors. Averaging and power budget calculations begin
immediately. Uses a RxLev of 0 if missing a measurement report.

For full details of the flexible neighbor cell processing feature, see the manual Technical
Description: BSS Implementation (68P02901W36).

Flexible neighbor cell processing parameters

Table 8-66 shows the parameters associated with flexible neighbor cell processing. A full
description of BSS database parameters is provided in Technical Description: BSS Command
Reference (68P02901W23).

Table 8-66 Flexible neighbor processing parameters

OMC-R GUI field
name/BSS parameter
name
HO to Nbr with Lower
Rxlev
worse_neighbor_ho
(OMC-R database
name:
worse_nei_ho)

Description
Displayed in the CELL Detailed View Handover section, Downlink
RxLev Handover grouping. Specifies whether handovers can be
made to neighbors with a worse RxLev. Valid values are:

True - allows neighbors with a lower RxLev than the serving

cell to be considered as valid handover candidates.

False - disables the potential to handover to worse cells.

Continued

68P02901W17-T

8-195
Jan 2010

Flexible neighbor cell processing parameters

Chapter 8: Configuring cells

Table 8-66 Flexible neighbor processing parameters (Continued)

OMC-R GUI field
name/BSS parameter
name
Max Disuse Count
based on Hreqave
disuse_cnt_hreqave
(OMC-R database
name:
disuse_cnt_flag)

HO UL/DL with MS/BSS

at Full Pwr
ho_only_max_pwr
(OMC-R database
name:
ho_onlymax_pwr)

Nbr Journaling
neighbor_journal
(OMC-R database
name:
neighbor_journ)

Description
Displayed in the CELL Detailed View Handover section, Handover
- General grouping. Specifies whether to include the disuse count of
neighbor cells when it is less than or equal to the maximum disuse
count. Valid values are:

True - means the maximum disuse count is defined by the

surrounding cell Hreqave. Neighbors with a disuse count less
than or equal to the maximum disuse count are still considered
as valid candidates for a handover.

False - disables maximum disuse count.

Displayed in the CELL Detailed View Handover section, Handover

- General grouping. Specifies whether RxQual or RxLev handovers
are allowed when the BTS or MS is at full power. Valid values are:

True - means ensure that the MS or BTS is at full power for

RxLev or RxQual handovers. That is, for an uplink the MS must
be at full power, for a downlink the BTS must be at full power.

False - disables maximum disuse count.

Displayed in the CELL Detailed View Handover section, Handover

- General grouping. Specifies whether warm up periods are allowed
for neighbors. Valid values are:

True - means:
Neighbor power level calculations begin immediately.
If the mobile does not send the neighbor measurement
reports to the BTS, the BTS substitutes missing reports
with zeros.
Disuse count needs to reach the Hreqave of the cell
before being removed from the list of cell candidates for
handover.

False - means:
The neighbor power level calculations do not begin until
Hreqave reports are received.
If the mobile does not send the neighbor measurement
reports to the BTS, the BTS substitutes missing reports
with the last RxLev received.
Disuse count needs to reach 8 before being removed from
the list of cell candidates for handover.

8-196

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Methods of configuring a cell for flexible neighbor processing

Methods of configuring a cell for flexible neighbor processing

A cell can be configured for flexible neighbor processing, using either of the following methods:

OMC-R GUI CELL Detailed View Handover section.

TTY interface, see Configuring a cell for flexible neighbor processing using the TTY
interface in this section.

Configuring a cell for flexible neighbor processing using the

TTY interface
The TTY interface can be used to configure a cell, including specifying the flexible neighbor
processing requirements. The following sections indicate the BSS commands and parameters
that can be used to create, display, and modify flexible neighbor processing parameters.
For further details of these commands and parameters, see the Technical Description: BSS
Command Reference (68P02901W23) manual. Also see Table 8-66 in this section for details of
the parameters.
Security Level 2 is required to enter these TTY commands.

Creating a flexible neighbor processing cell

To create a cell and specify all the cell parameters, including the flexible neighbor processing
parameters, use the add_cell command. In response to this command, the BSS prompts for
each of the cell parameters.

Enabling/Disabling flexible neighbor processing for an existing cell

First, to display whether flexible neighbor processing has been enabled or disabled, use
either the disp_cell or disp_element commands, and the appropriate worse_neighbor_ho,
disuse_cnt_hreqave, ho_only_max_pwr, neighbor_journal parameter. For example, the
following command displays whether handover to a neighbor with a lower RxLev is enabled
at BSC (site 0) for cell 001 01 17:
disp_element neighbor_journal 0 cell 0 0 1 0 1 1 7
To enable or disable, use either chg_element or chg_cell_element and the appropriate
parameter:worse_neighbor_ho, disuse_cnt_hreqave, ho_only_max_pwr, neighbor_journal.
For example, the following command enables handover to a neighbor with a lower RxLev at the
BSC (site 0) at the cell 0010117:
chg_cell_element neighbor_journal 1 0 cell 0 0 1 0 1 1 7

68P02901W17-T

8-197
Jan 2010

Configuring enhanced SDCCH to TCH band assignment

Chapter 8: Configuring cells

Configuring enhanced SDCCH to TCH band assignment

Introduction to enhanced SDCCH to TCH band assignment

Enhanced SDCCH to TCH band assignment increases the success rate of assignment to the
preferred band cell.
The multiband handover feature allows a user to select a Band Preference Mode
(band_preference_mode), see Multiband handover grouping on page 8-29. When setting
this mode to 1, 3, 5, or 6, the system attempts to move all the calls to the neighbor cell of
the preferred band at the time of the SDCCH to TCH assignment. At the time of the TCH
assignment, call processing queries the received signal strength for the qualified neighbor cells
of the preferred frequency band. If the MS has not reported the qualified signal strength for a
preferred band neighbor cell, the MS is assigned a TCH from the serving cell. In many cases the
MS does not report on neighbor cells from other frequency bands quick enough to allow TCH
assignment to the preferred band neighbor cell.

Methods of configuring enhanced SDCCH to TCH band

assignment
To configure enhanced SDCCH to TCH band assignment, use either of the following:

OMC-R GUI CELL Detailed View General section, Multiband handover grouping.

TTY interface and the sdcch_tch_band_reassign_delay parameter.

Prerequisites for configuring enhanced SDCCH to TCH band

assignment
The parent BSS must have the MultiBand Inter-Cell H/O Feature (mbInterCellhoOpt) set to
Enabled (1). Otherwise, the SDCCH to TCH Band Reassign Delay field is grayed-out in the
CELL Detailed View.

8-198

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Enhanced SDCCH to TCH band assignment parameter

Enhanced SDCCH to TCH band assignment parameter

The parameter sdcch_tch_band_reassign_delay (cell Detail View field: SDCCH to TCH Band
Reassign Delay field) defines the number of measurement report periods to wait before the
preferred band neighbors are reported.

NOTE
Use of this parameter may impose up to a two second delay in call setup.
Determine the optimal value for this parameter which increases the number of SDCCH to TCH
(preferred band) assignments without an unacceptable delay in call setup time.
The sdcch_tch_band_reassign_delay parameter can be set to one of the following options:

No delay (0).

One measurement report (1).

Two measurement reports (2).

Three measurement reports (3).

Four measurement reports (4).

The default value is 0.

Setting enhanced SDCCH to TCH band assignment using the

TTY interface
To set Enhanced SDCCH to TCH band assignment using the TTY interface, follow these steps:

Procedure 8-57 Set Enhanced SDCCH to TCH band assignment using the TTY
interface
1

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Enter the command:

chg_element sdcch_tch_band_reassign_del <value> <location>
cell = <cell_desc>

A full description of commands and parameters is provided in Technical Description: BSS

Command Reference (68P02901W23).

68P02901W17-T

8-199
Jan 2010

Displaying enhanced SDCCH to TCH band assignment using the TTY interface

Chapter 8: Configuring cells

Displaying enhanced SDCCH to TCH band assignment using

the TTY interface
To set Enhanced SDCCH to TCH band assignment using the TTY interface, follow these steps:

Procedure 8-58 Set Enhanced SDCCH to TCH band assignment using the TTY
interface
1

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Enter the command:

disp_element sdcch_tch_band_reassign_del <location> cell =
<cell_desc>
or use:
disp_cell <cell_desc>

A full description of commands and parameters is provided in Technical Description: BSS

Command Reference (68P02901W23).

8-200

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a cell for extended cell range prioritization

Configuring a cell for extended cell range prioritization

Introduction to extended cell range prioritization

A user can configure a cell and set the extended range cell prioritization threshold. This
determines the timing advance range at which an extended range neighbor is prioritized to
the top of the candidate list.

Extended cell range prioritization parameter

Table 8-67 gives details of the erc_ta_priority parameter.

Table 8-67

erc_ta_priority parameter

OMC-R GUI field

name/BSS database
parameter name
Ext Range Neighbor
Priority
erc_ta_priority

Description
Displayed in the CELL Detailed View, General section, General
grouping.
Extended range cell prioritization allows a priority threshold to be
set, which allows the default value of 50 to be overridden. If the
absolute timing advance is greater than the priority threshold, then
the ERC neighbors are placed at the top of the list of sorted handover
candidates. Otherwise, the ERC neighbors are appended to the end
of the list of candidates. Valid value in the range 0 - 63.
The default is 50.

Methods of configuring a cell for extended cell range

prioritization
A cell can be configured for extended cell range prioritization using either of the following
methods:

OMC-R GUI CELL Detailed View, General section, General grouping (Table 8-2).

TTY interface, see Configuring a cell for extended range cell prioritization using
the TTY interface.

68P02901W17-T

8-201
Jan 2010

Configuring a cell for extended range cell prioritization using the TTY interface

Chapter 8: Configuring cells

Configuring a cell for extended range cell prioritization using

the TTY interface
To configure a cell for extended range cell prioritization, use the erc_ta_priority parameter and
the chg_element command. The user needs Security Level 2 to enter these TTY commands.
For example, the following command sets the timing advance prioritization to 60 at the BSC
(SITE 0) in the cell 0010112:
chg_element erc_ta_priority 60 0 cell_number = 0 0 1 0 1 1 2
Use the erc_ta_priority parameter and the disp_cell or disp_element command to display
all current details or a specific parameter setting for a cell.
For further details of commands and parameters, see the Technical Description: BSS Command

Reference (68P02901W23) manual.

8-202

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a cell for power control optimization

Configuring a cell for power control optimization

Introduction to cell power control optimization

To optimize uplink and downlink power control for a cell, a user can set the following:

Uplink power control step sizes for power increments and decrements.

Downlink power control step sizes for power increments and decrements.

Enable or disable a power control step adjustment algorithm. This algorithm dynamically
modifies the power control step sizes to quickly return the power level to a level within a
pre-defined range.

Optimized power control extends the range of power control steps for power increments to allow
2, 4, 6,10,12 and 14 dB. It also adds power oscillation prevention for downlink power control.

Cell power control optimization parameters

Table 8-68 shows the parameters used to configure cell power control optimization. For
further details of these parameters see the Technical Description: BSS Command Reference
(68P02901W23) manual.

Table 8-68 Optimizing cell power control parameters

OMC-R GUI field name/BSS
parameter name

Description

Pwr Increase Step Size

UL
pow_inc_step_size_ul
(OMC-R parameter
name:
pow_inc_stepsz_ul)

Displayed in the CELL Detailed View, Power Control section,

Uplink Power Control grouping.
Specifies the step size for power increases from the MS to the BTS
(uplink). Valid values are: 2, 4, 6, 8, 10, 12, 14 dB. The default is 2
dB.
This parameter must be greater than or equal to
pow_red_stepsz_ul.

Pwr Increase Step Size

DL
pow_inc_step_size_dl
(OMC-R parameter
name:
pow_inc_stepsz_dl)

Displayed in the CELL Detailed View, Power Control section,

Downlink Power Control grouping.
Specifies the step size for power increases from the BTS to the MS
(downlink). Valid values are: 2, 4, 6, 8, 10, 12, 14 dB. The default
is 2 dB.
This attribute must be greater than or equal to pow_red_stepsz_dl.
Continued

68P02901W17-T

8-203
Jan 2010

Dynamic BTS Power control for Horizonmicro2

Chapter 8: Configuring cells

Table 8-68 Optimizing cell power control parameters (Continued)

OMC-R GUI field name/BSS
parameter name

Description

Pwr Reduction Step Size

UL
pow_red_step_size_ul
(OMC-R parameter
name:
pow_red_stepsz_ul)

Displayed in the CELL Detailed View, Power Control section,

Uplink Power Control grouping.

Pwr Reduction Step Size

DL
pow_red_step_size_dl
(OMC-R parameter
name:
pow_red_stepsz_dl)

Displayed in the CELL Detailed View, Power Control section,

Downlink Power Control grouping.
Specifies the step size for power decreases from the BTS to the
MS (downlink). Valid values are: 2 or 4 dB. The default is 2.
This parameter must be less than or equal to pow_inc_stepsz_dl.

Dynamic Step
Adjustment Alg
dyn_step_adj

Displayed in the CELL Detailed View, Power Control section,

Downlink Power Control grouping.
Enables or disables the uplink and downlink dynamic step
adjustment algorithm for the step size. Valid values are: Disabled
(0), Enabled without dynamic Pwr Reduction (1), or Enabled
without dynamic Pwr Reduction (1). The default is Disabled (0).

Factor of Max Pwr

Reduction
dyn_step_adj_fmpr

Displayed in the CELL Detailed View, Power Control section,

Downlink Power Control grouping.
Specifies the percentage power reduction used in the dynamic
power reduction calculation. Valid range of values: 0 - 10. The
default is 10.

Specifies the step size for power decreases from the MS to the
BTS (uplink). Valid values are: 2 or 4 dB. The default is 2.
This parameter must be less than or equal to pow_inc_stepsz_ul.

Dynamic BTS Power control for Horizonmicro2

Dynamic BTS Power Control is supported for Horizonmicro2, which allows the BTS transmit
power to be modified on a per carrier timeslot basis. When enabled, Dynamic BTS Power
Control reduces the power consumption of a Horizonmicro2. The absolute power range of
a Horizonmicro2 is 0 to 10 in steps of 2 dB.

Methods for configuring power control optimization

Cell power control optimization can be configured using either of the following methods:

8-204

OMC-R GUI CELL Detailed View, Power Control section, Uplink and Downlink Power
Control groupings.

TTY interface, see Configuring cell power control optimization using the TTY
interface.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

cell power control optimization using the TTY interface

Configuring

Configuring cell power control optimization using the TTY

interface
The TTY interface can be used to control the cell power control optimization parameters. The
following sections indicate the BSS commands and parameters that can be used to create,
display, and modify these parameters.
For further details of these commands and parameters see the Technical Description: BSS
Command Reference (68P02901W23) manual. Also see Table 8-68 in this section for details of
the cell power control optimization parameters.

Creating a cell with power control optimized

To create a cell and specify all the cell parameters, including the power control optimization
parameters (see Table 8-68), use the following command:
add_cell <gsm_cell_id> <location>
The BSS then prompts for each of the cell parameters.

Enabling/disabling the dynamic step adjustment algorithm

To display whether the dynamic step adjustment algorithm is enabled or disabled, use either of
the following commands:
disp_cell cell = <cell_desc>
disp_element dyn_step_adj <location> cell = <cell_desc>
To enable or disable the dynamic step adjustment algorithm, use either of the following
commands:
chg_element dyn_step_adj <value> <location> cell = <cell_desc>
chg_cell_element dyn_step_adj <value> [cell = ]<cell_desc>

Displaying and changing the power reduction percentage

To display the current percentage power reduction, use either of the following commands:
disp_cell cell = <cell_desc>
disp_element dyn_step_adj_fmpr <location> cell = <cell_desc>
To change the percentage power reduction, use either of the following commands:
chg_element dyn_step_adj_fmpr <value> <location> cell = <cell_desc>
chg_cell_element dyn_step_adj_fmpr <value> [cell = ]<cell_desc>

Displaying and changing the step size for power increases (uplink)
To display the current step size for power increases from the MS to the BTS, use either of
the following commands:
disp_cell <cell_desc>
disp_element pow_inc_step_size_ul <location> cell = <cell_desc>
To change the current step size for power increases from the MS to the BTS, use either of
the following commands:
chg_element pow_inc_step_size_ul <value> <location> cell = <cell_desc>
chg_cell_element pow_inc_step_size_ul <value> [cell = ]<cell_desc>

68P02901W17-T

8-205
Jan 2010

Configuring cell power control optimization using the TTY interface

Chapter 8: Configuring cells

Displaying and changing the step size for power increases (downlink)
To display the current step size for power increases from the BTS to the MS, use either of
the following commands:
disp_cell <cell_desc>
disp_element pow_inc_step_size_dl <location> cell = <cell_desc>
To change the current step size for power increases from the BTS to the MS, use either of
the following commands:
chg_element pow_inc_step_size_dl <value> <location> cell = <cell_desc>
chg_cell_element pow_inc_step_size_dl <value> [cell = ]<cell_desc>

Displaying and changing the step size for power decreases (uplink)
To display the current step size for power decreases from the MS to the BTS, use either of
the following commands:
disp_cell <cell_desc>
disp_element pow_red_step_size_ul <location> cell = <cell_desc>
To change the current step size for power decreases from the MS to the BTS, use either of
the following commands:
chg_element pow_red_step_size_ul <value> <location> cell = <cell_desc>
chg_cell_element pow_red_step_size_ul <value> [cell = ]<cell_desc>

Displaying and changing the step size for power decreases (downlink)
To display the current step size for power decreases from the BTS to the MS, use either of
the following commands:
disp_cell <cell_desc>
disp_element pow_red_step_size_dl <location> cell = <cell_desc>
To change the current step size for power decreases from the BTS to the MS, use either of
the following commands:
chg_element pow_red_step_size_dl <value> <location> cell = <cell_desc>
chg_cell_element pow_red_step_size_dl <value> [cell = ]<cell_desc>

8-206

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a cell for multiple GPRS carriers

Configuring a cell for multiple GPRS carriers

Introduction to multiple GPRS carriers per cell

Multiple GPRS carriers can be configured in a cell to increase GPRS data throughput. A user
can configure multiple GPRS carriers per cell for:

Performance (using the PCU Performance algorithm)

Specific to needs (using the Operator Specified algorithm)

By default, multiple GPRS carriers per cell is configured for performance. This allows the
network to configure all the reserved and switchable GPRS timeslots in a cell contiguously
to maximize performance.
When a carrier with GPRS timeslots goes out of service (OOS), GPRS timeslots are reconfigured
on a different carrier, which supports GPRS, based on radio resources available in the cell.
For a full description, see Technical Description: BSS Implementation (68P02901W36).

Configured for performance

Table 8-69 shows an example of when multiple GPRS carriers per cell have been configured for
performance. In this example, the cell has five GPRS carriers, 10 reserved timeslots and 11
switchable timeslots.

Table 8-69
Carrier
name

Timeslots on multiple GPRS carriers configured for performance

TS0

TS1

TS2

TS3

TS4

TS5

TS6

TS7

BCCH

SDCCH

RES

RES

RES

RES

RES

RES

SW

SW

SW

SW

RES

RES

RES

RES

Non-BCCH TCH
carrier
2

SW

SW

SW

SW

SW

SW

SW

Non-BCCH TCH
carrier
3

TCH

TCH

TCH

TCH

TCH

TCH

TCH

Non-BCCH TCH
carrier
4

TCH

TCH

TCH

TCH

TCH

TCH

TCH

BCCH
Carrier
Non-BCCH
carrier
1

68P02901W17-T

8-207
Jan 2010

Prerequisites for configuring multiple GPRS carriers per cell

Chapter 8: Configuring cells

Configured for Operator Specified

Table 8-70 shows an example of when multiple GPRS carriers per cell have been configured
using Operator Specified Algorithm (OSA). In this example, GPRS timeslots are distributed over
carriers in the cell. The cell has five GPRS carriers, 10 reserved timeslots and 11 switchable
timeslots, and max_gprs_ts_per_carrier is set to 6.

Table 8-70
Carrier
name

Timeslots on multiple GPRS carriers configured using OSA

TS0

TS1

TS2

TS3

TS4

TS5

TS6

TS7

BCCH

SDCCH

RES

RES

RES

RES

RES

RES

Non-BCCH TCH
carrier
1

TCH

SW

SW

RES

RES

RES

RES

Non-BCCH TCH
carrier
2

TCH

SW

SW

SW

SW

SW

SW

Non-BCCH TCH
carrier
3

TCH

TCH

TCH

TCH

SW

SW

SW

Non-BCCH TCH
carrier
4

TCH

TCH

TCH

TCH

TCH

TCH

TCH

BCCH
Carrier

Prerequisites for configuring multiple GPRS carriers per cell

Before multiple GPRS carriers per cell can be configured:

GPRS Feature (parameter name: gprsOpt) must have been purchased and set to Enabled
(1) in the BSS Detailed View.

GPRS Enabled (parameter name: gprs_enabled) in the CELL Detailed View is set to
Enabled (1).

If these parameters are not set, the parameters detailed in Table 8-71 are grayed-out in the
CELL Detailed View.

Multiple GPRS carriers per cell parameters

Table 8-71 details the multiple GPRS carriers per cell parameters. OMC-R parameter names are
the same as BSS parameter names, unless stated otherwise.

8-208

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Multiple GPRS carriers per cell parameters

Table 8-71 Multiple GPRS carriers per cell parameters

OMC-R GUI field
name/BSS parameter
name
Reserved GPRS Data
Timeslots
res_gprs_pdchs

Switchable GPRS
Data Timeslots
switch_gprs_pdchs

Switchable PDCHs
When One carrier
Goes OOS
sw_ts_less_one
_carrier
(OMC-R parameter
name:
switch_less_one_cr)

Description
Displayed in the GPRS grouping in the CELL Detailed View form.
Indicates the number of timeslots the BSS attempts to reserve as
PDCH timeslots in the cell. Must not exceed the DYNET capacity,
when the DYNET feature is enabled. The number can only be
increased if:

There are enough timeslots available on all the carriers in the

cell.

The sum of the values of res_gprs_pdchs and

switch_gprs_pdchs exceeds the DYNET capacity.

Displayed in the GPRS grouping in the CELL Detailed View form.

Indicates the number of timeslots the BSS attempts to allocate as
switchable TCH and PDCH timeslots in the cell. The number can
only be increased if:

There are enough timeslots available on all the carriers in the

cell.

The sum of the values of res_gprs_pdchs and

switch_gprs_pdchs exceeds the DYNET capacity.

Displayed in the GPRS grouping in the CELL Detailed View form.

Indicates the number of switchable GPRS timeslots the BSS allocates
on its GPRS carriers when one of the carriers becomes OOS. Only
used when one of the carriers in the cell becomes unavailable.
Valid values: 0 - 30, 255.
Default: unset or current value of switch_gprs_pdchs.
Cannot be changed in Create mode. Can be modified by a user in Edit
mode, but the following warning message is displayed:
GPRS traffic may be disrupted while GPRS timeslots are
being reconfigured
Can be modified for any cell if there are enough timeslots available
on all its carriers and the combined value of res_gprs_pdchs and
switch_gprs_pdchs is in the range 0 to 30. If there are insufficient
RTFs, the following message is displayed:
No Timeslots left on carrier(s) for res_ts_less_one_cr and
sw_ts_less_one_cr
Continued

68P02901W17-T

8-209
Jan 2010

Multiple GPRS carriers per cell parameters

Chapter 8: Configuring cells

Table 8-71 Multiple GPRS carriers per cell parameters (Continued)

OMC-R GUI field
name/BSS parameter
name

Description

Reserved PDCHs
When One carrier
Goes OOS
res_ts_less_one
_carrier
(OMC-R parameter
name:
res_less_one_cr)

Displayed in the GPRS grouping in the CELL Detailed View

form. Indicates the maximum number of reserved GPRS PDCHs
the BSS allocates if one carrier becomes unavailable. For each
additional carrier that is lost the maximum number of reserved
GPRS PDCHs to configure is adjusted by res_gprs_pdchs minus
res_ts_less_one_carrier. Valid values: 0 - 30, 255.
Default: unset or current value of res_gprs_pdchs. Cannot be
changed in Create mode. Can be modified by a user in Edit mode, but
the following warning message is displayed in the GUI:
GPRS traffic may be disrupted while GPRS timeslots are
being reconfigured. Can be modified for any cell if there are
enough timeslots available on all its carriers and the combined value
of sw_ts_less_one_carrier and res_ts_less_one_carrier does not
exceed 30. If there are insufficient RTFs, the following message is
displayed:
No Timeslots left on carrier(s) for res_ts_less_one_cr and
sw_ts_less_one_cr

Use BCCH Carrier for

GPRS
use_bcch_for_gprs

Displayed in the GPRS grouping in the CELL Detailed View form.

Indicates if reserved and switchable GPRS timeslots are allocated
on a BCCH carrier. If the value is set to 0 the BSS verifies that
there are enough non-BCCH carriers equipped and that they have
enough timeslots available to configure and support the values
of res_gprs_pdchs, switch_gprs_pdchs, res_les s_one_cr and
sw_less_one_cr. If use_bcch_for_gprs is being set to 0 (whether the
cell is already GPRS enabled) then:

There must be enough timeslots available on carriers for

res_gprs_pdchs and switch_gprs_pdchs configuration.

There must be enough carriers to support

res_ts_less_one_carrier and sw_ts_less_one_carrier values.

The allow_32K_trau parameter cannot be set to yes.

When gprs_enabled is already set to 1 and use_bcch_for_gprs is

being changed from 0 to 1 or from 1 to 0, then some GPRS timeslots
may become unavailable while they are being reconfigured for that
cell. The BSS rejects the request if there is insufficient number of
timeslots available on Non-BCCH Carrier(s).
Valid Values: 0 or 1, where 0 means use BCCH carrier for PDs as
the last priority, and 1 means use BCCH carrier for PDs as the first
priority. Default is 1.
Continued

8-210

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Methods for configuring multiple GPRS carriers per cell

Table 8-71 Multiple GPRS carriers per cell parameters (Continued)

OMC-R GUI field
name/BSS parameter
name
GPRS Timeslot
Configuration
Algorithm
gprs_ts_config_alg
(OMC-R parameter
name:
gprs_ts_confg_alg)

Description
Displayed in the GPRS grouping in the CELL Detailed View form.
Indicates the type of algorithm the BSS uses to allocate switchable
and reserved GPRS timeslots.
Valid values: 0 - 1, where:

0 - PCU Performance Algorithm.

1 - Customer Specified Algorithm.

gprs_enabled is changed from disabled (0) to enabled (1) for the cell.
Otherwise an error message is displayed.
Maximum GPRS Data
Timeslots per Carrier
max_gprs_ts_per
_carrier
(OMC-R parameter
name:
max_ts_per_cr)

Displayed in the GPRS grouping in the CELL Detailed View form.

Indicates the maximum number of switchable and reserved GPRS
timeslots the BSS can allocate on a per-carrier basis in the cell.
Valid values: 1 - 8. Default: 8.
This parameter can only be used when gprs_ts_config_alg is set to 1
(Customer Specified Algorithm).
When this parameter is modified the BSS verifies that there are
enough timeslots available on its carriers:

for res_gprs_pdchs and switch_gprs_pdchs configuration.

to support res_ts_less_one_carrier and sw_ts_less_one_carrier

values.

Methods for configuring multiple GPRS carriers per cell

A cell can be configured for multiple GPRS carriers using:

OMC-R GUI, using the GPRS grouping parameters in the CELL Detailed View as detailed
in Table 8-71.

TTY interface, see Configuring a cell for multiple GPRS carriers using the TTY
interface.

Configuring a cell for multiple GPRS carriers using the TTY

interface
Commands used to configure multiple GPRS carriers
The following commands can be used through the TTY interface to configure a cell for multiple
GPRS carriers.

disp_element to display the current value of a parameter listed in Table 8-71.

chg_element to change the current value of a parameter listed in Table 8-71.

68P02901W17-T

8-211
Jan 2010

Configuring a cell for multiple GPRS carriers using the TTY interface

Chapter 8: Configuring cells

See Technical Description: BSS Command Reference (68P02901W23) for full descriptions of
commands and parameters.

Examples of displaying multiple GPRS carriers per cell parameters

The following command displays the current value of res_gprs_pdchs at cell 0010116:
disp_element res_gprs_pdchs cell 0 0 1 0 1 1 6
The system replies, for example:
res_gprs_pdchs = 5

Examples of modifying multiple GPRS carriers per cell parameters

The following command changes the current value of res_gprs_pdchs to 7 at cell 0010116:
chg_element res_gprs_pdchs 7 cell = 0 0 1 0 1 1 6
The system replies, for example (bold text shows typical user replies):
WARNING: GPRS traffic may be disrupted while GPRS timeslots are being configured.
Are you sure (y = yes, n = no)?

COMMAND ACCEPTED

Enabling GPRS for a cell using the TTY interface

The following command changes gprs_enabled to 1 (GPRS Enabled) at cell 0010116:
chg_cell_element gprs_enabled 1 cell 0 0 1 0 1 1 6
The system then prompts the user to enter values for the parameters listed in Table 8-71.
See Technical Description: BSS Command Reference (68P02901W23) for full details of these
prompts.

8-212

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Changing a BCCH carrier frequency

Changing a BCCH carrier frequency

Changing BCCH carrier frequency using the OMC-R GUI

The BCCH carrier frequency should only be changed using the Navigation Tree (not the TTY
interface). This is because the Navigation Tree method automatically changes neighbor BCCH
records.
To change a BCCH carrier frequency using the OMC-R GUI, follow these steps:

Procedure 8-59 Change a BCCH carrier frequency using the OMC-R GUI

68P02901W17-T

Navigate to and select the RTF instance button in the Navigation Tree
(BSS BSS instance SITE SITE instance Radio Frequency
RTFGroup RTFGroup instance RTF RTF instance). If necessary,
see Navigating to a network object class or instance on page 1-28 for
further details. The RTF instance button changes color.

Select Edit Detailed View to open the RTF Detailed View form.

Select Edit Edit from the menu bar.

Change the frequency in the Carrier 1 ARFCN field to the desired

value.
The following message is displayed:
WARNING: Modifying this attribute may cause a carrier to be
taken out of service and calls affected by this carrier may
be lost. Loss of calls depends on the availability of other
carriers and timeslots not affected by the carrier being
disabled. If the carrier is baseband hopping, it will be
removed from the hopping system until the next site reset.
Do you wish to modify ?

Select either OK or Cancel.

Select File Save from the menu bar. This frequency change is
transmitted to the BSS and the BCCH carrier is automatically taken
out of service while the frequency change takes effect. After successful
modification of the frequency at the BSS, the MIB is updated. The MIB
Propagation form is displayed, as shown in Figure 8-9.

8-213
Jan 2010

Checking the status of a site

Chapter 8: Configuring cells

Figure 8-9 MIB Propagation Dialog Form

ti-GSM-MIBPropagationDialogForm-00807-ai-sw

Checking the status of a site

The following procedure is the fastest way to locate the BCCH carrier in a multiple cell site.

NOTE
Refer to the Network Operator System Engineering Drawings for customer specific
details of equipment interconnections.
To check the status of a site, proceed as follows:

Procedure 8-60 Check status of a site

1

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Use the disp_equipment to list all equipment for the site.

In the list displayed, BCCH RTF is identified as follows:
RTF x 0 0
Where:
x is the cell (0...5) for this site.
Continued

8-214

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking the status of a site

Procedure 8-60 Check status of a site (Continued)

3

Use the following command to display the function of the RTF

(identified in Step 4):
disp_equipment <location> RTF <rtf_id1> <rtf_id2> <rtf_id3>
In the list displayed, the following item indicates the BCCH frequency
channel number:
Carrier absolute radio freq. channel
From the list displayed, record the number of the GSM cell to which
this carrier is assigned, as this is required later.

Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the BSS commands discussed in this procedure.

68P02901W17-T

8-215
Jan 2010

Changing a non-BCCH carrier frequency

Chapter 8: Configuring cells

Changing a non-BCCH carrier frequency

Methods of changing non-BCCH carrier frequency for a cell

The non-BCCH carrier frequency for a cell can be changed using either the:

OMC-R GUI.

TTY interface.

Changing non-BCCH carrier frequency for a cell using the

OMC-R GUI
To change a non-BCCH carrier frequency using the OMC-R GUI, follow these steps:

Procedure 8-61 Change a non-BCCH carrier frequency using the OMC-R GUI
1

Navigate to and select the RTF instance button in the Navigation Tree
(BSS BSS instance SITE SITE instance Radio Frequency
RTFGroup RTFGroup instance RTF - RTF instance). If necessary,
see Navigating to a network object class or instance on page 1-28 for
further details.
The RTF instance button changes color.

Select Edit Detailed View from the menu bar.

The OMC-R displays the RTF Detailed View form.

Select Edit Edit from the menu bar.

Change the frequency in the Carrier 1 ARFCN field to the desired

value.
The following message is displayed:
WARNING: Modifying this attribute may cause a carrier to be
taken out of service and calls affected by this carrier may
be lost. Loss of calls depends on the availability of other
carriers and timeslots not affected by the carrier being
disabled. If the carrier is baseband hopping, it will be
removed from the hopping system until the next site reset.
Do you wish to modify ?
Continued

8-216

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Changing non-BCCH carrier frequency using the TTY interface

Procedure 8-61 Change a non-BCCH carrier frequency using the OMC-R GUI
(Continued)
5

Select either OK or Cancel.

If OK is selected, the following message is displayed:
COMMAND ACCEPTED

NOTE
Select File Revert before saving an edited detailed view
to return changed fields to the state they were in before
editing took place.
6

Select File Save from the menu bar to save the new value.
This frequency change is transmitted to the BSS and the BCCH carrier
is automatically taken out of service while the frequency change takes
effect.
After successful modification of the frequency at the BSS, the MIB
is updated.

Select the RTF which is associated with the non-BCCH carrier for the
cell of interest.

Open a detailed view form for the selected RTF by selecting Edit
Detailed View from the menu bar, or by double-clicking the required
RTF.
A detailed view is displayed with all fields in fully opened view.
Click View Carrier 1 information to display Carrier 1 information.

Select Edit Edit from the menu bar.

10

Change the frequency in the Carrier 1 ARFCN field to the desired

value.
The following message is displayed:
WARNING: Modifying this attribute will cause an RTF to be
temporarily unequipped and then re-equipped with the new
frequency. This has the following effects:
If baseband hopping, all calls on an in-service carrier will
be lost and hopping for this carrier will be disabled until
the site is reset.
If synthesized hopping, all calls on an in-service RTF will
be lost.
Do you wish to modify ?

11

Select either OK or Cancel.

12

Select File Save from the menu bar to save the new value.
This frequency change is transmitted to the BSS and the non-BCCH
carrier is automatically taken out of service while the frequency change
takes effect.
After successful modification of the frequency at the BSS, the MIB
is updated.

Changing non-BCCH carrier frequency using the TTY interface

A non-BCCH carrier frequency may also be changed using the TTY interface. Refer to: Technical
Description: BSS Command Reference (68P02901W23) for complete information on the MMI
commands discussed in this procedure.
68P02901W17-T

8-217
Jan 2010

Changing non-BCCH carrier frequency using the TTY interface

Chapter 8: Configuring cells

To change a non-BCCH frequency channel number using the TTY interface, proceed as follows:

Procedure 8-62 Change a non-BCCH frequency channel number using the TTY
interface
1

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Use the following command to display a list of all equipment for the
site:
disp_equipment <location>

From the list, identify the RTF non-BCCH that requires amendment.

Use the following command to display the function of this RTF:

disp_equipment <location> RTF <rtf_id1> <rtf_id2> <rtf_id3>
In the list displayed, the following item indicates the non-BCCH
frequency channel number:
Carrier absolute radio freq. channel

Use the following command to change the non-BCCH frequency

channel number:
chg_rtf_freq <frequency> <location> <rtf_id1> <rtf_id2>

Answer the prompt.

If y is input, the following message is displayed:
COMMAND ACCEPTED

To check that the non-BCCH is set to the new frequency channel

number, enter the following command:
disp_equipment <location> RTF <rtf_id1> <rtf_id2> <rtf_id3>
In the list displayed, the following item indicates the new frequency
channel number:
Carrier absolute radio freq. channel

8-218

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Changing a BSIC

Changing a BSIC

Recommendation and overview to BSIC change

The Base Transceiver Station Identity Code (BSIC) is a block of code, consisting of the GSM
PLMN color code and a base station color code. The BSIC allows a mobile station to distinguish
between different neighboring base stations, and is encoded on the Synchronization Channel.
A BSIC may be reused, but neighbor cells must not share the same BSIC or the same BCCH RF
carrier. Immediate neighbor cells must not have BSIC values in multiples of eight of the cell
being configured. Examples are:

Cell BSIC = 8, Neis = 16, 24, 32, 40 or

Cell BSIC = 9, Neis = 17, 25, 33, 41.

Motorola recommends using the OMC-R GUI CELL Detailed View to change the BSIC of a
cell. This enables MIB propagation to update all sources/neighbors configured in the network
under that OMC-R.
When the Base Station Identity Code (BSIC) or CCCH Configuration fields are changed, the
CM MIB does not propagate the training sequence codes (TSC) changes. Instead, the BSS
propagates the changes in accordance with the method specified in the Update TSCs field
(tsc_update_method parameter) in the BSS Detailed View. The BSS then sends the attribute
value change events to OMC-R and the RTF TSCs are updated automatically. This means there
is no need to delete the RTF. See Changing a TSC for a BCCH on page 8-221 for further details.
An audit is only required after a BSIC change, if the OML was out of service.

Changing a BSIC with no hopping using the OMC-R GUI

To change a BSIC when not using frequency hopping, follow these steps:

Procedure 8-63

Change a BSIC when not using frequency hopping

Navigate to the required cell in the Navigation Tree or use the Find
function on the Front Panel to locate the required cell.

Double-click the required cell instance to open the CELL Detailed View.

Select Edit Edit from the menu bar.

If necessary, stop calls on the cells by gracefully shutting down the

DRIs using shutdown_device option on the Navigation Tree.
Shut down the non-BCCH DRIs first, to prevent the BCCH hopping to
another in service RTF.
Allow 60 seconds for existing calls to be transferred.

Continued

68P02901W17-T

8-219
Jan 2010

Changing a BSIC with hopping

Chapter 8: Configuring cells

Procedure 8-63 Change a BSIC when not using frequency hopping (Continued)
5

Enter the new BSIC value in the Base Station Identity Code (BSIC) field
in the Identification section of the CELL Detailed View.
The OMC-R displays a warning message that the cell will temporarily
lose calls.

Select either OK or Cancel.

This frequency change is transmitted to the BSS, and the BCCH carrier
is automatically taken out of service while the change takes effect.
After successful modification at the BSS, the MIB is updated.
The MIB Propagation form is displayed.

Save the changes and close the Detailed View.

Changing a BSIC with hopping

To change a BSIC when using frequency hopping, follow these steps:

Procedure 8-64 Change a BSIC when using frequency hopping

8-220

Change the BSIC for the cell using the procedure Changing a BSIC
with no hopping using OMC-R GUI in the previous section.

Delete the sources/neighbors for the cell.

Unconfigure the frequency hopping for the RTF.

Delete the RTF from the paths configured for the site, using the
del_rtf_path command.

Delete the RTF using the Delete option in the Navigation Tree.

Re-equip the RTF with the new TSC codes in all timeslots.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Changing a TSC for a BCCH

Changing a TSC for a BCCH

Overview to TSC change

If for any reason the BCC part of the BSIC is changed, the Training Sequence Code (TSC) for
the BCCH RTF must also be changed.
Motorola recommends using the OMC-R GUI CELL Detailed View to change the BSIC of a cell.

NOTE
The MIB does not propagate updates to sources/neighbors configured in the network
under that OMC-R.
When the BSIC is changed, the BSS does not propagate the change of the associated TSC of the
BCCH RTF to the training sequence codes. The BSS propagates the changes for the RTF::TSCs
that have been modified. However, if frequency hopping is configured, all TSC timeslots have to
be updated. The only way to update all TSC timeslots is to delete and then re-equip the RTF.

Changing a TSC
To change the TSC, proceed as follows:

Procedure 8-65 Change the TSC

1

Stop calls on the Cell by gracefully shutting down the DRIs using
shutdown_device option on the Navigation Tree. Shut down the non
BCCH DRIs first to prevent the BCCH hopping to another in service
RTF. Typically allow between 30 and 60 seconds to terminate all
existing calls.

Change the BSIC for the cell using the procedure described in
Changing a BSIC on page 8-219.

Delete the BCCH RTF by the following:

68P02901W17-T

Delete the sources/neighbors for the cell.

Unconfigure the frequency hopping for the RTF.

Delete the RTF from the paths configured for the SITE, using
the del_rtf_path command.

Delete the BCCH RTF using the Delete option in the Navigation
Tree.

Re-equip the RTF with the new TSC codes in all timeslots.

8-221
Jan 2010

Propagating TSC updates

Chapter 8: Configuring cells

Propagating TSC updates

Overview of TSC update propagation

The Training Sequence Codes (TSCs) of the BCCH/CCCH must match the BCC. The BCC is the
lower three bits of the Base Transceiver Station Identity Code (BSIC) value.
When a BSIC or Configuration CCCH is changed for a cell, it is possible to specify how the TSC
updates are propagated to the timeslots of RTF(s) in a cell using the tsc_update_method
parameter.
tsc_update_method can have the following values:

Only of BCCH/CCCH timeslots (0)

The TSCs are updated on the BCCH/CCCH timeslots only according to the value of the
ccch_conf parameter. This is the default method.

Of all timeslots on BCCH carrier (1)

All TSCs on the BCCH carrier only are updated.

Of all timeslots on all carriers of the cell (2)

All TSCs on all carriers in the cell are updated.

Methods of specifying the propagation of TSC updates

To specify the TSC propagation method at a BSS level, use either of the following:

OMC-R GUI BSS Detailed View.

TTY interface.

Prerequisites for changing TSC propagation

The TSC update method can only be modified when no RTFs are equipped in the database.

Modifying the TSC update propagation method using the TTY

interface
To modify the TSC update propagation method using the TTY interface, use the following
command:
chg_element tsc_update_method <value> <location>

8-222

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying the TSC update propagation method using the TTY

For example, the following command sets the update method to 1 (update TSCs on all timeslots
on the BCCH carrier only) at site 0:
chg_element tsc_update_method 1 0
For further details of the tsc_update_method parameter and BSS commands, see Technical
Description: BSS Command Reference (68P02901W23).

Displaying the TSC update propagation method using the TTY

To display the current TSC update method, use the following command:
disp_element tsc_update_method <location>
The system responds, for example:
tsc_update_method = 1
For further details of the tsc_update_method parameter and BSS MMI commands, see Technical
Description: BSS Command Reference (68P02901W23).

68P02901W17-T

8-223
Jan 2010

Assigning a quality of 7 to missing measurement reports

Chapter 8: Configuring cells

Assigning a quality of 7 to missing measurement

reports

Introduction to quality 7 for missing reports

If a measurement report does not arrive, the corresponding measurement report slot is assigned
the quality value from the previous measurement report. Usually it is the mobile portion of the
measurement report that is missing. The result in a less drastic change in quality. Instead, a cell
can be configured to assign a quality of 7 (bad) to any missing measurement report.

Quality of 7 for missing measurement reports parameter

Table 8-72 shows details of the rpt_bad_qual_no_mr parameter.

Table 8-72 rpt_bad_qual_no_mr parameter

OMC-R GUI field
name/BSS parameter
name
Rpt Bad Quality on a
Missing Rpt
rpt_bad_qual_no_mr
(OMC-R parameter
name:
rpt_bad_qual_mr)

Description
Displayed in the CELL Detailed View, General section, General
grouping.
Records the quality of 7 to lost measurement reports.
Valid values are:

0 - Worst quality value (7) is not used to signify the quality

should the measurement report not arrive. (Default)

1 - Worst quality value (7) is used to signify the quality should

the measurement report not arrive.

Methods of assigning a quality of 7 to missing measurement

reports
To record quality 7 for missing measurement reports, use either of the following methods:

8-224

OMC-R GUI CELL Detailed View, General section, General grouping (Table 8-2).

TTY interface, see Recording missing measurement reports as quality 7 using the
TTY interface.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

missing measurement reports as quality 7 using the TTY interface

Recording

Recording missing measurement reports as quality 7 using

the TTY interface
To configure a cell to record missing measurement reports as quality 7, which means bad quality,
use the rpt_bad_quality_no_mr parameter and the chg_element command. The user needs
Security Level 2 to enter these TTY commands. For example, the following command enables
quality report of 7 on missing measurement reports at the BSC (SITE 0) in the cell 0010112:
chg_element rpt_bad_qual_no_mr 1 0 cell_number = 0 0 1 0 1 1 2
Use the rpt_bad_quality_no_mr parameter and the disp_cell or disp_element command to
display all current details or a specific parameter setting for a cell.
For further details of commands and parameters, see the Technical Description: BSS Command
Reference (68P02901W23) manual. Also, see Table 8-73 in this section for details of the
rpt_bad_quality_no_mr parameters.

68P02901W17-T

8-225
Jan 2010

Changing the number of allocated SDCCHs

Chapter 8: Configuring cells

Changing the number of allocated SDCCHs

Introduction to determining the number of SDCCHs

Determining the requirement for the number of Standalone Dedicated Control Channels
(SDCCHs) required for signaling during call set-up and location update in a cell, is a vital part of
the planning process, and once it is set there it is rarely altered.

NOTE
There is no requirement to lock the site for this facility.

Changing the number of SDCCHs: associated parameters

Once the BSS is call processing, the Cell Resource Manager (CRM) is capable of dynamic
channel reconfiguration. This means that the CRM is capable of changing the mix of channel
configuration. If a high proportion of SDCCHs are in use, the CRM is able to reconfigure a
TCH timeslot into SDCCHs. The channel reconfiguration switch in the BSS database specifies
whether the CRM may or may not perform dynamic channel reconfiguration. If SDCCHs in a
cell have to be reconfigured, the parameters shown in Table 8-73 may need amending. Refer to:
Technical Description: BSS Command Reference (68P02901W23) for complete information on
these database parameters.

NOTE
All of the parameters shown in Table 8-73 are displayed in the CELL Detailed View,
General section, Radio Channel Configuration grouping.

8-226

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Changing the number of SDCCHs: associated parameters

Table 8-73 SDCCH parameters

OMC-R GUI field name/BSS
parameter name
Channel Reconfiguration
channel_reconfiguration_
switch(OMC-R database
parameter name:
channelReconfig)

Description
Enables and disables dynamic channel reconfiguration
(reassignment) of traffic channels to Standalone
Dedicated Control Channels (SDCCHs). The Cell
Resource Manager (CRM) may attempt to reconfigure
an idle TCH into an SDCCH if a high proportion of
SDCCHs are in use and additional SDCCH requests
are received. The reconfiguration process continues
until the number of idle SDCCHs reaches the
sdcch_need_high_water_mark value. The reconfiguration
process stops when the number of idle TCHs goes below
the tch_full_need_low_water_mark value or when
the total number of SDCCHs configured reaches the
max_number_of sdcchs value. Valid values are:

0 - Channel reconfiguration disabled in the cell.

1 - Channel reconfiguration enabled in the cell.

Preferred Number of SDCCH

number_sdcchs_preferred
(OMC-R parameter name:
numSdcchsPref)

Defines the preferred number of SDCCHs that the

reconfiguration algorithm tries to manage. If channel
reconfiguration is switched on then the Cell Resource
Manager (CRM) tries to make the required number of
SDCCHs available for immediate assignment. Valid values
are dependent on the setting of ccch_conf (see below).
If ccch_conf is 1, valid values are 12, 20, 28, 36, 44, 52, 60,
68, 76, 84, 92, 100, 108, 116, 124.
If ccch_conf is 0, 2, 4 or 6, valid values are 16, 24, 32, 40,
48, 56, 64, 72, 80, 88, 96, 104, 112, 120, 128.
Refer to Table 8-74 and Table 8-75 for the required
parameter settings.
Ensure that the following relationship is maintained:
Preferred Number of SDCCH <Maximum Number of
SDCCH.

Number of Reserved Access

Grant Blocks
bs_ag_blks_res

Determines the number of blocks which are reserved for

access grant for each 51 TDMA multiframe. The number
of reserved blocks is broadcast on the Broadcast Control
Channel (BCCH) beginning with block 0. The number of
available paging blocks is reduced by the number of blocks
reserved for access grant messages.
Valid values are:

0 - 2, blocks reserved for ccch_conf = 001.

0 - 7, blocks for all other values of ccch_conf.

Continued

68P02901W17-T

8-227
Jan 2010

Changing the number of SDCCHs: associated parameters

Chapter 8: Configuring cells

Table 8-73 SDCCH parameters (Continued)

OMC-R GUI field name/BSS
parameter name
CCCH Configuration
ccch_conf

Description
Determines the organization of the Common Control
Channels (CCCHs) on the BCCH. This parameter
determines whether the CCCHs are being combined on the
physical channel together with the SDCCH and the SACCH.
The value depends on specific planning conditions in each
individual network.
Valid values represent (three bits coded):

0=000

1=001

2=010

4=100

6=110

If pccch_enabled is set to 1 and the operator tries to

change ccch_conf, a warning is displayed when the
PBCCH/PCCCH feature is unrestricted.
SDCCH Need High Water Mark
sdcch_need_high_water_mark
(OMC-R parameter name:
sdcchNeedHighWm)

Determines the number of idle SDCCHs that trigger

reconfiguration of a traffic channel to an SDCCH.
Valid values are 1 - 11 9, which indicate the number of
SDCCHs. The default is 2.
Ensure that the following relationship is maintained:
SDCCH Need High Water Mark < SDCCH Need Low Water
Mark.

SDCCH Need Low Water Mark

sdcch_need_low_water_mark
(OMC-R parameter name:
sdcchNeedLowWm)

Determines the number of idle SDCCHs that

trigger reconfiguration of an SDCCH (from previous
reconfigurations) back to a traffic channel.
Valid values are 10 - 128, which indicate number of
SDCCHs. The default is 12.

TCH Full Need Low Water Mark

tch_full_need_low_water_mark
(OMC-R parameter name:
tchFullNeedLowWm)

Sets the low need water mark used by the CRM

to determine the need for reconfiguration of full
rate traffic channels to SDCCHs. The value of the
tch_full_need_low_water_mark represents the minimum
number of TCHs the system tries to maintain when dynamic
reconfiguration is enabled.channelReconfig (BSS naming:
channel_reconfiguration_switch) needs to be enabled for
this reconfiguration to take place.
Valid values are 0 - 255, which indicates number of
channels. The default is 255.
Continued

8-228

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Changing the number of SDCCHs: associated parameters

Table 8-73 SDCCH parameters (Continued)

OMC-R GUI field name/BSS
parameter name
Maximum Number of SDCCH
max_number_of_sdcchs
(OMC-R parameter name:
maxNumberOfSdcch)

Description
Determines the number of SDCCHs that can be reached in
the reconfiguration process. It determines the upper limit
for the number of SDCCHs that the CRM can manage.
Valid values are dependent on the setting of ccch_conf. If
ccch_conf is 1, valid values are 12, 20, 28, 36, 44, 52, 60,
68, 76, 84, 92, 100, 108, 116, 124. If ccch_conf is 0, 2, 4, or
6 valid values are 16, 24, 32, 40, 48, 56, 64, 72, 80, 88, 96,
104, 112, 120, 128.
Set this field to 28 for a combined channel configuration
and set it to 32 for a non-combined channel configuration.
When changing between a combined and non-combined
configuration, it may be necessary to adjust the value of
Number of Reserved Access Grant Blocks, observing the
dependencies to CCCH Configuration. That is, if CCCH
Configuration is 1, the valid range of values for Number of
Reserved Access Grant Blocks is 0 - 2, otherwise, the valid
range is 0 - 7.

Table 8-74 SDCCH parameters with combined channel configurations

OMC-R GUI Field and BSS
Parameter Name

Value for 4
SDCCHs

Value for 12
SDCCHs

Value for 20
SDCCHs

Value for 28
SDCCHs

CCCH Configuration
ccch_conf

Preferred Number of SDCCH

number_sdcchs_preferred

12

20

28

SDCCH Need High Water Mark

sdcch_need_high_water_mark

SDCCH Need Low Water Mark

sdcch_need_low_water_mark

11

11

18

26

Table 8-75 SDCCH parameters with NON-combined channel configurations

68P02901W17-T

OMC-R GUI Field and BSS

Parameter Name

Value for 8
SDCCHs

Value for 16
SDCCHs

Value for 24
SDCCHs

Value for 32
SDCCHs

CCCH Configuration
ccch_conf

Preferred Number of SDCCH

number_sdcchs_preferred

16

24

32

SDCCH Need High Water Mark

sdcch_need_high_water_mark

SDCCH Need Low Water Mark

sdcch_need_low_water_mark

11

14

22

30

8-229
Jan 2010

Methods of reconfiguring the number of SDCCHs

Chapter 8: Configuring cells

Methods of reconfiguring the number of SDCCHs

To configure the number if SDCCHs used for signaling, use either of the following methods:

OMC-R GUI CELL Detailed View, General section, Radio Channel Configuration grouping
(parameters also shown in Table 8-73).

TTY interface, see Reconfiguring the number of SDCCHs using the TTY interface.

Reconfiguring the number of SDCCHs using the TTY interface

To reconfigure the number of SDCCHs using the TTY interface, proceed as follows:

Procedure 8-66 Reconfiguring the number of SDCCHs using TTY

1

Remotely login to the BSS and change security levels, see Remotely
logging in to a BSS site from the OMC-R on page 1-39.

Display the cell parameters, using the following command:

disp_cell [<cell_desc>] [full]

The current settings of the parameters are shown in Table 8-73.

NOTE
When the number of allocated SDCCHs are changed, the
parameter relationships described in this procedure must
be maintained.

Set the parameters for the required number of SDCCH.

Refer to Table 8-74 and Table 8-75 for the required parameter settings.
4

Compare the intended value of ccch_conf with the value currently

stored in the database.
If the value remains the same, continue to step 6. Otherwise, go to
step 5.

NOTE
There is no requirement to lock the site for this facility.
Continued

8-230

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reconfiguring the number of SDCCHs using the TTY interface

Procedure 8-66 Reconfiguring the number of SDCCHs using TTY (Continued)

5

Change the value of ccch_conf using the following command:

chg_cell_element ccch_conf <value> <cell_desc_opt>
The response is as follows:
WARNING: The ccch_conf command will cause an RTF to be
temporarily unequipped, and then re-equipped. This has the
following effects:
If baseband hopping, all calls on an in-service carrier will
be lost, and hopping for this carrier will be disabled until
the site is reset.
If synthesizer hopping, all calls on an in-service carrier
will be lost.
Are you sure? (y = yes, n = no).
If y is input, then the user is prompted for the following information:
Enter CRM maximum number of SDCCHs.
Enter CRM SDCCH low water mark.
Enter CRM SDCCH high water mark.
Enter number of SDCCHs preferred.
Enter RSS blocks reserved for access grant.
Depending on the value assigned to ccch_conf, set the values for the
five prompts according to the following conditions:
If ccch_conf = 0, 2, 4, or 6, values for the following parameters must
meet specific criteria:

number_sdcchs_preferred must be in multiples of 8 with no

offset (divisible by 8) (that is, 16,...,128).

number_sdcchs_preferred must be less than or equal to

sdcch_need_low_water_mark.

The minimum number of SDCCHs must be divisible by 8.

max_number_of_sdcchs must be divisible by 8.

0 bs_ag_blks_res 7.

If ccch_conf = 1, values for the following parameters must meet

specific criteria:

number_sdcchs_preferred must be in multiples of 8, with an

offset of 4 (that is, 12,...,124).

The minimum number of SDCCHs must be a multiple of 8 (+4).

max_number_of_sdcchs must be a multiple of 8 (+4).

0 bs_ag_blks_res 2.

Proceed to step 9.
Continued

68P02901W17-T

8-231
Jan 2010

Reconfiguring the number of SDCCHs using the TTY interface

Chapter 8: Configuring cells

Procedure 8-66 Reconfiguring the number of SDCCHs using TTY (Continued)

6

Should it be necessary to change the value of

sdcch_need_high_water_mark use the following command:
chg_element sdcch_need_high_water_mark <element value>
<location> cell = <cell_desc>
Ensure that the following relationship is maintained:
sdcch_need_high_water_mark < sdcch_need_low_water_mark

Change the value for number_sdcchs_preferred using the following

command:
chg_element number_sdcchs_preferred <element value>
<location> cell = <cell_desc>
Refer to Table 8-74 and Table 8-75 for the required parameter setting.
Ensure that the following relationship is maintained:
number_sdcchs_preferred max_number_of_sdcchs
When increasing the number of allocated SDCCHs, the value of
number_sdcchs_preferred must be increased first.

Set the max_number_of_sdcchs to 28 for a combined channel

configuration and to 32 for a non-combined channel configuration.
When changing between a combined and non-combined configuration,
it may be necessary to adjust the value of bs_ag_blks_res, observing
the dependencies to ccch_conf, that is, if ccch_conf is 1, the valid
range of values for bs_ag_blks_res is 0 - 2, otherwise, the valid range
is 0 - 7.
To change thebs_ag_blks_res parameter use the following command:
chg_element bs_ag_blks_res <element value> <location> cell
= <cell_desc>

Determine the site lock/unlock status.

NOTE
Each radio can support a maximum of 16 SDCCHs.
Therefore, when changing to 24 or more SDCCHs, two
non-BCCH DRIs (if available) that do not already contain
SDCCHs should be locked and unlocked.

To confirm that the changes have been implemented use the following
command:
disp_cell <cell_desc>

Example of TTY reconfiguration

For example, enter the following commands to change a cell 200 with LAC 1234 from 8 to
12 SDCCHs at site 2.
disp_cell 2 6 2 0 1 1234 200
OMC-R response indicates that current settings are:
ccch_conf = 1
number_sdcchs_preferred = 8

8-232

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking SDCCH configuration for multiple cells using SQL

max_number_of_sdcchs = 32
sdcch_need_high_water_mark = 8
chg_element sdcch_need_high_water_mark 12 2 cell_number = 2 6 2 0 1 1234 200
chg_element number_sdcchs_preferred 12 2 cell_number = 2 6 2 0 1 1234 200

Checking SDCCH configuration for multiple cells using SQL

To check SDCCH configuration for multiple cells using SQL proceed as follows:

Procedure 8-67 Check SDCCH configuration for multiple cells using SQL

68P02901W17-T

Use SQL to get the information for all cells in the MIB.
The following example SQL query extracts the SDCCH config
information for all cells in the OMC-R:
select
bsstable2.name BSC,
sitetable2.name SITE,
celltable2.gsmcellid CID,
celltable2.ccch_conf ccch_conf,
celltable2.channelreconfig chan_rec,
celltable2.sdcchneedhighwm sd_hiwm,
celltable2.sdcchneedlowwm sd_lowm,
celltable2.numsdcchspref numsd_pref,
celltable2.maxnumberofsdcch max_num_sd,
celltable2.rr_t3101 rr_t3101
from
celltable2,
drigrouptable2,
sitetable2,
bsstable2
where
celltable2.containerinstrite = sitetable2.oidinstrite
and celltable2.containerinstleft = sitetable2.oidinstleft
and sitetable2.containerinstrite = bsstable2.oidinstrite
and sitetable2.containerinstleft = bsstable2.oidinstleft
order by
BSC, SITE, CID

Create a file called sdcch.sql with this query.

As omcadmin user, enter:
mib_env
isql mib_16xx <sdcch.sql> sdcch.op
Where mib_16xx is the name of the database.
The file called sdcch.op contains all the data for analysis or further
parsing.

8-233
Jan 2010

Establishing a cell boundary by changing transmit power

Chapter 8: Configuring cells

Establishing a cell boundary by changing transmit

power

Introduction to establishing a cell boundary by changing

transmit power
To establish a cell boundary, it is necessary to change the maximum output power of the cell.
Use the Maximum Transmit Power for BTS field (BSS parameter name: max_tx_bts) in the
CELL Detailed View, Power Control section, Downlink Power grouping.
The range of values for max_tx_bts is shown in Table 8-76.

Table 8-76 Value ranges for max_tx_bts

Cell frequency or Cabinet type

Min. value

Max. value

PGSM, EGSM, DCS1800 cells

-1

21

PCS1900 cells

21

M-Cell6, Horizonmacro,
or Horizon II macro BTS
controlling cabinet

-1

21

The steps vary according to the associated BTS type and cell frequency. For example for PGSM,
EGSM, and PCS1900:

-1 represents 45 dBm (valid only for BTS sites with M-Cell6, Horizonmacro, or Horizon II
macro as the controlling cabinet and with frequencies PGSM, EGSM, or DCS1800).

0 represents 43 dBm.

12 represents 19 dBm.

21 represents 1 dBm.

The default is 43 dBm Macro, 12 dBm Pico (0).

NOTE
The BCCH is transmitted at the power level set by max_tx_bts.
Table 8-77 lists the values for the (R)CTU4. The values represent the calibrated output power
at the top of the cabinet without any stage of external combining in single density or values
without external combining in double density mode.

8-234

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

establishing a cell boundary by changing transmit power

Introduction to

NOTE
The (R)CTU4 values represent the calibrated output power after reducing the
combining loss of 0 dB, 3 dB, and 6 dB without any stage of combining. This is when
the maximum densities of two transmission paths are working at (0+1 or 1+1 mode),
or (0+2 or 1+2, or 2+2 mode), or (0+3 or 1+3, or 2+3, or 3+3 mode) accordingly.

68P02901W17-T

If the (R)CTU4 is working at 1+0, 1+1 carrier mode, the max_tx_bts is the same,
for example, at the radio output: max_tx_bts 0->46dBm, 1->44dBm, 2->42dBm.

If the (R)CTU4 is working at 2+0, 2+1, 2+2 carrier mode, the (R)CTU4 has
extra 3dB attenuation. For example, at the radio output: max_tx_bts 0->43dBm,
1->41dBm, 2->39dBm.

If the (R)CTU4 is working at 3+0, 3+1, 3+2, 3+3 carrier mode, the (R)CTU4 has
extra 6dB attenuation. For example, at the radio output: max_tx_bts 0->40dBm,
1->38dBm, 2->36dBm.

8-235
Jan 2010

Methods of changing the maximum output of a cell

Chapter 8: Configuring cells

Table 8-77 (R)CTU4 output values without any stage of combining

Valid input

(R)CTU4 working at 0+1

or 1+1 mode
1800 Mhz

900 Mhz

(R)CTU4 working at 0+2

or 1+2, or 2+2 mode
1800 Mhz

900 Mhz

(R)CTU4 working at 0+3 or

1+3, or 2+3, or 3+3 mode
1800 Mhz

900 Mhz

45 dBm

46 dBm

42 dBm

43 dBm

39 dBm

40 dBm

43 dBm

44 dBm

40 dBm

41 dBm

37 dBm

38 dBm

41 dBm

42 dBm

38 dBm

39 dBm

35 dBm

36 dBm

39 dBm

40 dBm

36 dBm

37 dBm

33 dBm

34 dBm

37 dBm

38 dBm

34 dBm

35 dBm

31 dBm

32 dBm

35 dBm

36 dBm

32 dBm

33 dBm

29 dBm

30 dBm

33 dBm

34 dBm

30 dBm

31 dBm

27 dBm

28 dBm

31 dBm

32 dBm

28 dBm

29 dBm

25 dBm

26 dBm

29 dBm

30 dBm

26 dBm

27 dBm

23 dBm

24 dBm

27 dBm

28 dBm

24 dBm

25 dBm

21 dBm

22 dBm

10

25 dBm

26 dBm

22 dBm

23 dBm

19 dBm

20 dBm

11

23 dBm

24 dBm

20 dBm

21 dBm

17 dBm

18 dBm

12

21 dBm

22 dBm

18 dBm

19 dBm

15 dBm

16 dBm

13

19 dBm

20 dBm

16 dBm

17 dBm

13 dBm

14 dBm

14

17 dBm

18 dBm

14 dBm

15 dBm

11 dBm

12 dBm

15

15 dBm

16 dBm

12 dBm

13 dBm

9 dBm

10 dBm

16

13 dBm

14 dBm

10 dBm

11 dBm

7 dBm

8 dBm

17

11 dBm

12 dBm

8 dBm

9 dBm

5 dBm

6 dBm

18

9 dBm

10 dBm

6 dBm

7 dBm

3 dBm

4 dBm

19

7 dBm

8 dBm

4 dBm

5 dBm

1 dBm

2 dBm

20

5 dBm

6 dBm

2 dBm

3 dBm

-1 dBm

0 dBm

21

3 dBm

4 dBm

0 dBm

1 dBm

-3 dBm

-2 dBm

NOTE
Set the same value for the (R)CTU4 maximum densities of two transmission paths in
one cell to ensure the same output power for carriers in one cell.

Methods of changing the maximum output of a cell

To change the maximum output of a cell, use either of the following methods:

8-236

OMC-R GUI CELL Detailed View, Power Control section, Downlink Power Control grouping.

TTY interface and the max_tx_bts parameter.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Setting all channels at full power

Setting all channels at full power

Introduction to setting channel power level

The full power feature can be configured for either a cell or a SITE. It sets all the channels in
the selected cells (or all cells in the SITE) to broadcast at a constant power level. The full power
level is configured as the maximum transmit power level for the cell. The feature can be useful
in worst case interference monitoring for network optimization. The full power mode can be
terminated manually at any time, or automatically stopped by the BSS on expiration of a timer
set when the full power mode is activated.

Description of set_full_power process

A cell must be equipped and in a state other than OOS for the command to be accepted. The
set_full_power command can be entered whether the cell is already in full power mode or not.
A time entered in any subsequent set_full_power command overrides any previously running
timer for that cell. If a carrier state transitions from UNLOCKED to BUSY occurs while a cell is
operating in full power mode, that carrier is not be set to full power mode.
When full power mode is activated, active channels are affected as follows:

Downlink power changes to the value of max_tx_bts.

Downlink DTx is disabled.

Dynamic downlink power control is disabled.

When full power mode is deactivated, active channels are affected as follows:

Downlink DTx remains off for any calls which are active. New calls are able to use
downlink DTx.

Downlink power control is resumed if it is enabled.

The set_full_power command can be entered from the OMC-R using Rlogin, MMI at the BSC,
or at the SITE where the affected cells are located.

Displaying the status of full power mode using the TTY interface
To display the status of the full power mode for a cell, use the disp_cell_status command.
Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the set_full_power and disp_cell_status command.

68P02901W17-T

8-237
Jan 2010

Enabling full power on all channels using the TTY interface

Chapter 8: Configuring cells

Enabling full power on all channels using the TTY interface

To turn on full power mode, proceed as follows:

Procedure 8-68 Turn on full power mode

1

Remotely login to the BSS, see Remotely logging in to a BSS site from
the OMC-R on page 1-39.

For a specific cell, enter the following command:

set_full_power [<cell_desc>] on <minutes>
For all cells at a specific SITE, enter the following command:
set_full_power <location> on <minutes>

Disabling full power on all channels using the TTY interface

To turn off full power mode, proceed as follows:

Procedure 8-69 Turn off full power mode

1

Remotely login to the BSS, see Remotely logging in to a BSS site from
the OMC-R on page 1-39.

For a specific cell, enter the following command:

set_full_power <cell_desc> off
For all cells at a specific SITE, enter the following command:
set_full_power <location> off

8-238

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Barring calls at a cell

Barring calls at a cell

Overview of barring options

The following options are available to bar (prevent) calls to a cell:

Each cell has a Subscriber Access to Cell Class field (BSS database parameter name:
cell_bar_access_switch, OMC-R database parameter name: cellBarAccess) which
determines whether a subscriber is barred (prevented) access to a cell. When a mobile
is given access to a cell, this means that it is capable of decoding BCCH data. BCCH
data indicates that a mobile is part of the selected Public Land Mobile Network (PLMN)
and is Not Barred.
The Subscriber Access to Cell field is displayed in the OMC-R GUI CELL Detailed View,
General section, System Access grouping, see Table 8-3. Valid values for the field are: Cell
is Not barred (0), Cell is barred (1). The default is Not Barred (0).

To prevent a cell setting up or receiving calls, shut down all the DRIs of the cell using
shutdown_device. Shut down the non BCCH DRIs first to prevent the BCCH hopping to
another in service RTF. Allow 60 seconds for existing calls to be transferred.

To prevent a site setting up or receiving calls, lock the SITE. For busy periods, first
gracefully shut down the DRIs using shutdown_device.

To stop a cell receiving incoming handovers, see Barring of incoming handovers on page
8-240 for details.

To stop call processing in a cell, but still leave all the hardware in service, disable both:

Procedure 8-70 Stop a cell call processing

1

Disable the capability to set up MS calls by entering the command:

cell_bar_access_switch

Disable the capability to receive incoming handovers by entering the

command: en_incom_ho

Displaying cells where calls are barred

To display a list of cells where calls are barred, use the User Barred Cells form. To display the
User Barred Cells form, select the network object in either the Navigation Tree, Contained
Devices, or Map form, then Select User Barred Cells from the Display menu.
These methods are only available if a Network, BSS, or SITE instance is selected. If the user
is omcadmin and Network is selected, then all user barred cells in that Network/Region are
displayed. If the user is not omcadmin and their own Region is selected, then all barred calls in
that Region are displayed.

68P02901W17-T

8-239
Jan 2010

Barring of incoming handovers

Chapter 8: Configuring cells

The User Barred Cells form is then displayed. It displays the GSM Cell ID of all user barred
cells within the selected network object, and their respective SITE name sorted by SITE name
in ascending order. The title bar of the form shows the name of the context, that is, Network,
Region, BSS, or SITE.
To open a Detailed View of a cell, double click a cell in the list. The CELL Detailed View can
be edited if required.

Unbarring calls
To unbar a call using User Barred Cells form, select one or more cells in the User Barred Cells
form, then click the Unbar button at the bottom of the User Barred Cells form. The unbarred
cells are then removed from the User Barred Cells form.
Unbarred call operations are logged in the usrauditlog file.

Barring of incoming handovers

The en_incom_ho parameter bars incoming handovers into the cell. It is displayed in the OMC-R
GUI CELL Detailed View, Handover section, Handover - General grouping, Enable Incoming
Handovers Class field (Table 8-18). The default is Disable Incoming Handovers (0).
Additionally, choose whether a neighbor is specified as one or both of the following in the BA
lists:

A SACCH neighbor (call mode only).

A BCCH neighbor (idle mode only).

The Neighbor Detailed View contains a List Type field setting which supports the selection of
the two independent BA lists on a per neighbor basis.
The neighbor list is supplied to the MS in call mode as a list in which the MS must monitor the
signal strength of each cell and report these to the BSS. The decision to hand over to one
of these cells is taken by the BSS and/or the MSC. In idle mode, the MS monitors the list of
cells provided by the BSS, and uses an internal algorithm to decide when to reselect to a new
cell. The BSS and MSC are not involved, and are not informed unless this reselection is to a
new location area. For example, it is possible to reserve a cell for call originations only. This
can be done by removing the cell BCCH frequency from the BA_SACCH so that handovers
from MSs in call mode are barred.
If the subscriber population is mostly mobile across a large geographical area of cells, with units
frequently turned off, all BCCH frequencies can be included in the BA_BCCH list. This inclusion,
of BCCH frequencies, decreases the average time it takes an MS to come back into service.

Changing neighbor BA lists

The recommended method of modifying the BA lists of neighbors is using the OMC-R GUI
Neighbor Detailed View. The modified parameters are propagated first to the BSS and, if
accepted, then updated in the MIB. Refer to Modifying a neighbor on page 8-130 for further
information.

8-240

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Barring calls at a site

Barring calls at a site

To bar calls at a site, see Barring calls at a site using the TTY interface on page 7-55.

68P02901W17-T

8-241
Jan 2010

Changing LAC and/or CI

Chapter 8: Configuring cells

Changing LAC and/or CI

GSM Cell identifier

The GSM Cell identifier is made up of the following:

Mobile Country Code (MCC).

Mobile Network Code (MNC).

Location Area Code (LAC).

Cell Identity (CI).

See Technical Description: BSS Command Reference (68P02901W23) for further details of
GSM Cell Id formats.

Recommendation for changing LAC and/or CI

To change the Location Area Code (LAC) or GSM Cell ID (CI) of a cell, use:

OMC-R GUI CELL Detailed View.

cmutil.

These methods use the Neighbor Propagation feature of the MIB, so that all LAC-CI cell changes
automatically update associated sources, neighbors, DRIs, and RTFs.
Alternatively, use the off-line MIB and DataGen.

Changing a single LAC and/or CI using the OMC-R GUI

To make a single change to LAC and/or CI using the OMC-R GUI, proceed as follows:

Procedure 8-71 Change a single LAC and/or CI using the OMC-R GUI
1

Navigate to and select the cell instance button in the Navigation Tree.
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details.
The cell instance button changes color.

Select Edit Detailed View to display the CELL Detailed View.

Select Edit Edit.

Continued

8-242

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Procedure 8-71
4

Changing multiple LACs and/or CIs using cmutil

Change a single LAC and/or CI using the OMC-R GUI (Continued)

Move to the GSM Cell ID field and change the LAC or CI or both.

NOTE
To obtain parameter information, select Help - On Context
from the menu, drag the ? prompt to the appropriate field
and click. A context-sensitive help page is displayed.
5

If required, modify the name of the cell in the Name field to reflect
the change.

From the menu bar, select File Save to save the

changes. The save propagates the change to the affected
sources/neighbors/DRI/RTF/parent site and child objects. The MIB
Propagation form is displayed.

Select File Close to close the CELL Detailed View.

Check the propagation is successful for all sources/neighbors affected.

Sometimes a single source cell is not updated due to a lock on the
object.

NOTE
The failures are to be noted and resolved manually. (open
affected Neighbor Detailed View and edit).
9

Upload each affected NE database to the OMC-R.

Changing multiple LACs and/or CIs using cmutil

To make multiple LAC and/or CI changes using cmutil, see Chapter 15 cmutil.

68P02901W17-T

8-243
Jan 2010

Viewing and editing the SMS-CB message using the OMC-R GUI

Chapter 8: Configuring cells

Viewing and editing the SMS-CB message using the

OMC-R GUI

Using the SMS CB Detailed View

View and edit the SMS-CB message using the SMSCBmsg Detailed View window. To display the
SMSCBmsg Detailed View from the Navigation Tree, follow these steps:

Procedure 8-72 Displaying the SMSCBmsg Detailed View

1

Using the Navigation Tree, select the appropriate cell.

Open the SMSCBmsg Detailed View from the SMSCBmsg instance.

To edit the message or associated parameters, select Edit Edit from

the menu bar. This switches the form in to Edit mode.

If required, edit the SMSCB message or the associated parameters.

See SMSCBmsg Detailed View fields for details.

Select File Save to save the changes.

Select File Close to close the Detailed View.

SMSCBmsg Detailed View fields

The following sections list and briefly describe the parameter fields in the SMSCBMsg Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

8-244

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

SMSCBmsg Detailed View fields

Identification grouping
Table 8-78 SMSCBmsg Detailed View fields - Identification grouping
Field name

Brief description

Values

RDN Class

See Table 4-1 description.

Default is the
device class.

RDN Instance

See Table 3-1 description.

0 - 3.
Default is 0.

NMC RDN Value

See Table 4-1 description.

Parent Detailed
View

Displays the name of the parent cell.

Click to display the parent CELL
Detailed View.

Mandatory or
Optional?

Message Text grouping

The message text for this SMSCB message. Up to 93 characters can be displayed. This is a
mandatory field.

Additional Information
Use the Additional Information window to input any notes relating to this message. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

SMS Information grouping

Table 8-79

SMSCBmsg Detailed View fields - SMS Information grouping

Field name

Brief description

Values

Mandatory or
Optional?

Geographical
Scope

The geographical scope of this

message.

0 - 3.
Immediate, Cell
Wide (0),
Normal, PLMN
wide (1),
Normal,
Location Area
Wide (2),
Normal, Cell
wide (3).

Mandatory.

Data Coding
Scheme

The data coding scheme for this

message, such as, English (1) or
Norwegian (10).

0 - 255.

Mandatory.

Continued

68P02901W17-T

8-245
Jan 2010

SMSCBmsg Detailed View fields

Chapter 8: Configuring cells

Table 8-79 SMSCBmsg Detailed View fields - SMS Information grouping (Continued)
Field name

8-246

Brief description

Values

Mandatory or
Optional?

Message Code

The message code for the message,

used to differentiate between SMSCB
messages with the same message
identifier.

0 - 1023.

Mandatory.

Message Identifier

Identifies the source and type of the

message. When the message identifier
is combined with the message code,
the SMSCB message is uniquely
identified.

0 - 65535.

Mandatory.

Update Number

The update number of this message.

0 - 15.

Mandatory.

68P02901W17-T
Jan 2010

Chapter

9
Configuring Devices and Functions

Typically, all required devices and functions are equipped when the BSS database is first
created. This enables the site configured cells to be operational. However, devices and functions
in a site/BSC may need to be manually added, removed, or changed from time to time. When
all the necessary hardware components of the network have been created, and the site and
the necessary cabinets and cages have been created/equipped, each device and function can
be created/equipped to inform the BSS system software of its existence. For each device or
function, specific configuration information is provided, such as prerequisites, parameters, slot
details (where appropriate), and so on. The devices and functions are described alphabetically
for ease of reference.
The following topics are described:

Methods of configuring individual devices and functions on page 9-3.

Methods of configuring multiple devices and functions on page 9-8.

Reassigning SITE, MTL, and CBL devices between GPROCs on page 9-14.

Displaying Channel and Circuit Status on page 9-20.

Hierarchy of devices and functions on page 9-29.

Configuring a BSP device on page 9-35.

Configuring a BTP device on page 9-39.

Configuring a CBL on page 9-43.

Configuring a CIC on page 9-46.

Configuring a COMB device on page 9-49.

Configuring a CSFP device on page 9-54.

Configuring a DHP device on page 9-59.

Configuring a DRI on page 9-63.

Reassigning a DRI device on page 9-77.

Remotely calibrating DRIs on page 9-79.

Creating a standard configuration for DRI calibration on page 9-84.

Remotely calibrating DRIs from the OMC-R on page 9-93.

Managing existing standard configurations on page 9-99.

Configuring an EAS device on page 9-101.

68P02901W17-T
Jan 2010

9-1

SMSCBmsg Detailed View fields

9-2

Chapter 9: Configuring Devices and Functions

User-definable EAS BSC/BSS and BTS alarm strings on page 9-102.

Defining EAS alarms in the alarm table using the TTY interface on page 9-103.

Changing EAS alarms in the alarms table using the TTY interface on page 9-104.

Creating an EAS device using the OMC-R GUI on page 9-106.

Configuring an EAS using the TTY interface on page 9-111.

Configuring the EAS physical relay states using the TTY interface on page 9-112.

Configuring a GCLK device on page 9-113.

Configuring a GPROC device on page 9-116.

Configuring a KSWpair device on page 9-120.

Configuring a KSW (or DSW) device on page 9-123.

Configuring an LCF function on page 9-127.

Configuring an LMTL device on page 9-131.

Modifying LMTL loadsharing granularity on page 9-134.

Configuring an MSI device on page 9-137.

Configuring Enhanced GDP provisioning on page 9-146.

Configuring an MTL device on page 9-152.

Modifying MTL loadsharing granularity on page 9-155.

Configuring an OMF function on page 9-158.

Configuring an OML device on page 9-160.

Configuring a path device on page 9-162.

Creating a path on page 9-164.

Deleting a path on page 9-170.

Extending and reparenting a path on page 9-172.

Checking path connectivity on page 9-174.

Configuring an RSL device on page 9-176.

Configuring an RTF function on page 9-182.

Creating an RTF function on page 9-185.

Deleting an RTF on page 9-193.

Configuring an XBL device on page 9-197.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Methods of configuring individual devices and functions

Methods of configuring individual devices and functions

Introduction to configuring individual devices and functions

Most devices and functions detailed in this chapter can be configured using one of the following
methods:

OMC-R GUI Navigation Tree and Detailed Views.

TTY interface and BSS commands.

General procedures for using each of these methods for the following activities are described
in this section:

Creating/equipping

Displaying

Modifying

Deleting/unequipping

When only one method is available, it is stated in the appropriate device or function section.
When configuring many devices or functions, Motorola recommends specific or other methods,
see Methods of configuring multiple devices and functions on page 9-8.

Creating/equipping individual devices and functions

Using the OMC-R GUI
To create individual devices or functions, use the OMC-R GUI Navigation Tree. The procedure is
described for each device and function in this chapter. For a general procedure, see Creating a
network object using the OMC-R GUI on page 1-32.
If possible, use the Save Defaults menu option in the Detailed View when saving a
device/function of the same type. The saved information is then used as the default information
when another device/function of the same type is created.

NOTE
The default files, created while executing the previous steps, are preserved during
the machine cut-over to prevent loss of user-specific default data.
Once equipped, a device/function must be unlocked to bring it into service.

68P02901W17-T

9-3
Jan 2010

Modifying individual devices and functions

Chapter 9: Configuring Devices and Functions

Using the TTY interface

To create (referred to as equip) any device or function detailed in this chapter using the TTY
interface, follow these steps:

Procedure 9-1 Create device or function using TTY interface

1

Remote login to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39 and Changing
security level (for TTY interface commands) on page 1-43, respectively.

Use the equip command. For example, the following command equips
a BSP at the BSC:
equip bsc BSP
The system responds by displaying prompts for specific device or
function parameter information. For example, when equipping a BSP
the system displays the following prompts (bold text shows typical
user replies):
Enter the BSP identifier:
0
Enter the cage number:
1
Enter the slot number:
20
Enter the maximum MTLs this BSP may manage:
0
COMMAND ACCEPTED

Reply to each prompt with the required information. Refer to:

Technical Description: BSS Command Reference (68P02901W23) for

complete information on the equip command and the system prompts
displayed for each device and function.
4

Once equipped, a device must be unlocked to bring it into service.

Modifying individual devices and functions

Using the OMC-R GUI
To modify existing devices/functions, use the Navigation Tree. See the general procedure in
Modifying a network object using the OMC-R GUI on page 1-34.
Also, small scale RF parameter changes to RTFs, cells, and neighbors should be carried out
using the Navigation Tree (and editing the Detailed Views). This is because OMC-R neighbor
and cell parameter propagation features are available through the Navigation Tree only.

9-4

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying individual device and function details

Using the TTY interface

To modify an individual device or function parameter using the TTY interface, follow these steps:

Procedure 9-2 Modify device or function using TTY interface

1

Remote login to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39 and Changing
security level (for TTY interface commands) on page 1-43, respectively.

Use the BSS parameter name with either of the following commands:
chg_element or modify_value. For example, the following command
changes the parameter lmtl_loadshare_granularity to 1 at SITE 0:
chg_element lmtl_loadshare_granularity 1 0
The following command changes the parameter max_lmtls of LCF
0 to 1:
modify_value bsc max_lmtls 1 LCF 0

Technical Description: BSS Command Reference (68P02901W23)

describes all commands in detail.

Displaying individual device and function details

Using OMC-R GUI
To display details for an existing individual device or function, open its Detailed View.

Using the TTY interface

To display details of an individual device or function using the TTY interface, follow
Procedure 9-3:

Procedure 9-3 Display device or function using TTY interface

1

Remote login to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39 and Changing
security level (for TTY interface commands) on page 1-43, respectively.
Continued

68P02901W17-T

9-5
Jan 2010

Deleting/unequipping individual devices and functions

Chapter 9: Configuring Devices and Functions

Procedure 9-3 Display device or function using TTY interface (Continued)

2

Use the disp_equipment command in the following format:

disp_equipment <location> <device/function name> <device
ids>
For example, the follow command displays details for XBL 200:
disp_equipment 0 xbl 2 0 0
The system responds by displaying information about the device or
function. For example:
AXCDR device identifier for the XBL: 2
Second device identifier for the XBL: 0
Data rate for the XBL (kbit/s): 64 K
First MMS identifier for this device: 0
Second MMS identifier for this device: 0Timeslot on MMS
where this device appears: 9
LAPD T200 Timer value for this device is [lapd_t200_timer]:
2500
LAPD N200 value for this device is [lapd_n200]: 3
LAPD K value for this device is [lapd_k]: 7

Technical Description: BSS Command Reference (68P02901W23)

describes all commands and prompts in detail.

Deleting/unequipping individual devices and functions

Using the OMC-R GUI
Use the Delete option in the Navigation Tree to delete individual devices or functions, see the
general deletion procedure in Deleting a network object using the OMC-R GUI on page 1-37.

Using the TTY interface

NOTE
Before deleting some devices and functions, specific prerequisites must be met. When
required, these prerequisites are listed in the appropriate section in this chapter.
To delete an individual device or function, follow these steps:

Procedure 9-4

Delete device or function using TTY interface

Remote login to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39 and Changing
security level (for TTY interface commands) on page 1-43, respectively.

Unlock the device or function, as appropriate.

Continued

9-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting/unequipping individual devices and functions

Procedure 9-4 Delete device or function using TTY interface (Continued)

3

Use the unequip command in the following format:

unequip <location> <device or function name> <1st device id>
<2nd device id>
For example, the following command unequips MSI 2 0 0:
unequip 2 msi 2 0 0
Refer to: Technical Description: BSS Command Reference
(68P02901W23) for complete information on the unequip command.

68P02901W17-T

9-7
Jan 2010

Methods of configuring multiple devices and functions

Chapter 9: Configuring Devices and Functions

Methods of configuring multiple devices and functions

Introduction to configuring multiple devices and function

This section provides recommendations for creating, modifying, and deleting multiple devices
and functions, for example, when more than three devices or functions are created.

Creating multiple devices or functions using a batch_rlogin

script
Motorola recommends creating multiple devices/functions as part of a new BSS database build.
The quickest way to create multiple devices/functions online is to create a batch rlogin script,
and run the script for the appropriate SITEs/BSSs.
After creating the devices, unlock each device to bring it into service.

Methods of modifying multiple devices and functions

Multiple devices or functions can be modified using the following methods:

cmutil (see Chapter 15 cmutil for further information).

batch_rlogin.

The advantage of using cmutil over batch_rlogin is that cmutil can update all BSSs if required,
whereas batch_rlogin operates only on a single BSS.

Modifying multiple devices or functions using batch_rlogin

A batch_rlogin using the TTY rlogin commands can be used to modify multiple
devices/functions. This is typically done using the following commands.

chg_element
When used with the all input parameter, this command changes the database element to the
specified value for all cells at the specified location.
For example, to change the database element max_tx_bts to value 10 for all cells at site 1, the
following TTY command is required: chg_element max_tx_bts 10 1 all

9-8

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting multiple devices or functions using a script

modify_value
When used with the all input parameter, this command modifies values for MMS, RSL or
XBL devices.
For example, to modify lapd_t200_timer to 2500 ms for every equipped RSL, the following TTY
command in SYSGEN mode is required: modify_value all lapd_t200_timer 2500 rsl

Deleting multiple devices or functions using a script

Before deleting a device, lock the device to take the device or associated function out of service.
Multiple devices/functions are best deleted as part of a new BSS database build.
The quickest way to delete multiple devices/functions online is to create a batch rlogin script
file, and run the script for the appropriate SITEs/BSSs.

68P02901W17-T

9-9
Jan 2010

Checking the hardware version/serial number/FRU

Chapter 9: Configuring Devices and Functions

Checking the hardware version/serial number/FRU

Overview to tracking devices

NOTE
Motorola recommends using the Generic Lookup Utility (GLU). See Recommendations
for Configuration Management on page 1-2 for further details.
The following devices contain information which allow them to be tracked for inventory and
fault diagnostic purposes:

BSP.

BTP.

COMB.

CSFP.

DHP.

DRI.

GPROC.

GCLK.

KSW.

MSI.

This tracking is done by extracting information on the following parameters:

9-10

Kit number.

Serial number.

Field replaceable unit (FRU).

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking a single device using the OMC-R GUI

Checking a single device using the OMC-R GUI

To check a single device using the GUI, proceed as follow:

Procedure 9-5

Check single device using OMC-R GUI

Open a Detailed View from the Navigation Tree for any of the devices
listed above.

Check the settings contained under the Identification parameter

grouping, Kit number, Serial number, and FRU fields.

Checking a single SITE using the TTY interface

The disp_equipment command allows an optional parameter, full, which can be used to display
the hardware-specific information for a device, in addition to the configuration information
entered when the device is equipped. When this option is used to display all of the equipment at
a site, the output is a table which includes kit and serial numbers.

Checking multiple devices using SQL

Use SQL to get the information for all devices in the MIB. For example, the following SQL query
extracts DRI and DRCU/TCU/CTU hardware details for all DRIs in the OMC-R:
select
dritable2.kitnumber dri_kit,
dritable2.fru dri_fru,
dritable2.serialnumber dri_sn,
dritable2.assockitnumber rtf_kit,
dritable2.assocfru rtf_fru,
dritable2.assocserialnumber rtf_sn,
dritable2.rdninstance id0,
drigrouptable2.rdninstance id1,
sitetable2.name SITE,
bsstable2.name BSC
from
dritable2,
drigrouptable2,
sitetable2,
bsstable2
where
dritable2.containerinstrite = drigrouptable2.oidinstrite
and dritable2.containerinstleft = drigrouptable2.oidinstleft
and drigrouptable2.containerinstrite = sitetable2.oidinstrite

68P02901W17-T

9-11
Jan 2010

Making multiple checks using scripting and TTY interface

Chapter 9: Configuring Devices and Functions

and drigrouptable2.containerinstleft = sitetable2.oidinstleft

and sitetable2.containerinstrite = bsstable2.oidinstrite
and sitetable2.containerinstleft = bsstable2.oidinstleft
order by
bsc, site, id1, id0
To check multiple devices using SQL, follow these steps:

Procedure 9-6

Checking multiple devices using SQL

Create a file called dri_hw.sql with this query.

As omcadmin user, enter:

mib_env
isql mib_16xx <dri_hw.sql> dri_hw.op
where mib_16xx is the name of the database.
The file called dri_hw.op contains all the data, which can then be
analyzed or further parsed as required.

Making multiple checks using scripting and TTY interface

UNIX shell scripting can be combined with TTY commands to make multiple checks. The output
can be logged to a file for further analysis or parsing. The script in the following example checks
the GCLK version on all sites, and logs this GCLK data to a file. The script operates on the basis
that BSS loads are correctly named (for example, BSGSM) during load install.
#!/bin/ksh
# Script to check the GCLK version on all sites under this OMC
# Written by Motorola Field Engineer on 17/11/98
bscs =grep BSGSM /usr/omc/config/global/NE.MAP|awk '{print $2}'
for i in echo $bscs
do
bsc_num = grep $i /usr/omc/config/global/NE.MAP|awk '{print $4}'
site_nums = grep SITE 31 $bsc_num /usr/omc/config/global/SITE.MAP|awk
' \ { print $5}' |cut -c9-10 |grep -v 00
for j in echo $site_nums
do
echo disp_eq $j gclk * * full >>bsc_cmd.file
done
echo bscname $i >>gclk_version.log
batch_rlogin $i <bsc_cmd.file >>gclk_version.log
sleep 10

9-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Making multiple checks using scripting and TTY interface

rm bsc_cmd.file
done
echo Log file is in $PWD/gclk_version.log.

68P02901W17-T

9-13
Jan 2010

Reassigning SITE, MTL, and CBL devices between GPROCs

Chapter 9: Configuring Devices and Functions

Reassigning SITE, MTL, and CBL devices between

GPROCs

Device redistribution
Device redistribution is used to equalize the load incurred by GPROC devices. Any GPROC
experiencing high processor utilization is a candidate to have some of the devices which it
supports moved to another GPROC.
This section primarily deals with the reassigning of the CBL, MTL, and SITE devices from one
GPROC device to another. The GPROC device is referred to as the parent, and the devices
which it supports as the child devices.
The LCF exists only in a BSC type 1 or 2 system. In a BSC type 0 system, all functionality is
supported by the BSP GPROC. The purpose of the LCF is to off load functionality from the BSP
in a larger configuration. The functionality supported by the LCF as it relates to this feature is
the support of the MTL, CBL, and (remote) site devices. The MTL is the link supporting the
A interface between the MSC and BSS, whereas the CBL is the link supporting the interface
between the CBC and the BSS. A CBL is only allowed to exist in a BSC type 1 or 2 system and
therefore is never supported by the BSP. The site device as it relates to this feature represents
the BTS portion of the BSS.

Reassignment controlling factors

The maximum number of child devices (SITE, MTL, and CBL) which can be supported by a
GPROC is controlled by two factors:

The GPROC device - equip parameters, such as the maximum number of MTLs/CBLs for
a BSP or LCF, establish the maximum number of these links which can be supported
by a GPROC. The maximum number of sites supported by a GPROC device is not user
configurable.

The physical resources available on a GPROC - the HDLC channels of the GPROC.
Normally HDLC channels are not of customer concern, except when planning the required
equipment for the BSS, and usually does not factor into operational commands for a BSS
after initial installation. However, reassigning essentially involves the replanning of
equipment resources for the BSC.

See System Information: BSS Equipment Planning (68P02900W21) to ensure that capacity
guidelines are not exceeded.

9-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reassignment capacity issues

Reassignment capacity issues

When deciding on the distribution of child devices to GPROC devices, one of the capacity issues
of concern is the number of link devices that can be supported by the GPROC device. The
number of HDLC channels available for a GPROC may restrict the number of link devices that a
GPROC can support. Ultimately, the number of link devices which can be supported by a GPROC
device is the lesser of the number indicated in the customer database and the number that can
be physically supported by the GPROC device. It is for this reason that the HDLC capacity of a
GPROC is a prominent issue. Mechanisms for viewing HDLC channel assignments of a GPROC
device are provided. Warning messages are also displayed when the number of HDLC channels
is a limiting factor for device redistribution or modifications of link maximums. HDLC channels
are only assigned during the initialization of a GPROC device. Any changes to the HDLC channel
layout would require the reset of the GPROC device.

NOTE

This feature does not perform any automatic SITE reassignments under any
circumstances.

Perform site assignments in accordance with the rules provided in the System
Information: BSS Equipment Planning (68P02900W21) manual.

Refer to: Technical Description: BSS Command Reference (68P02901W23) for full details of
the commands used.

Reassigning devices using the OMC-R GUI

The OMC-R GUI supports the reassign action for some devices. For DRIs, this operation is used
to move control of the DRI from GPROC to GPROC. DRIs that were assigned to a DHP can be
moved to a BHP or another DHP. The reassign operation removes the DRI from service until the
action has been completed. SITEs, CBLs, and MTLs can also be reassigned from/to LCF devices.
The reassign option is available from the Fault Mgt menu in the Navigation Tree (see OMC-R
Online Help, Network Operations for further details). The reassign operation can also be
invoked from DRI, SITE, CBL, and MTL Detailed Views.

Reassigning devices using the TTY interface

The following procedures for reassigning a SITE, MTL, and CBL device using the TTY interface
are described in the following sections:

Displaying current devices assigned to an LCF.

Displaying High-level Data Link Control (HDLC) channel types of in-service GPROC.

Modifying the value of the maximum number of MTLs and CBLs supported by an LCF.

Reassigning a device to an LCF.

Displaying HDLC channel assignment types.

68P02901W17-T

9-15
Jan 2010

Displaying current devices assigned to LCF

Chapter 9: Configuring Devices and Functions

Refer to: Technical Description: BSS Command Reference (68P02901W23) for full details of
commands and parameters.

Displaying current devices assigned to LCF

To ensure that the LCF has the capacity to cope with the reassignment of devices, the current
devices assigned to the LCF are determined using the disp_equipment command. For example,
to display the current devices assigned to LCF 0 0 0 use the following command:
disp_equipment 0 LCF 0 0 0
The current devices assigned to the LCF are displayed.

Displaying HDLC layout

To view the HDLC channel assignment types of an in-service GPROC and to ensure that the LCF
has the capacity to cope with the reassignment of devices, use the disp_hdlc command.

Displaying HDLC layout

To display the HDLC layout, use the following command:
disp_hdlc <location> <GPROC device> <device_id1> <device_id2>

NOTE

Any changes to the HDLC channel layout would require the reset of the GPROC.

The maximum number of HDLC channels supported is controlled by the

gproc_slots parameter, which can only be modified in SYSGEN mode.

If the command is successful then the output includes:

9-16

GPROC device.

GPROC device's CPU identifier.

GPROC function, that is, LCF.

Indication of how the channels have been configured.

Indication of whether the channel is currently in use.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Modifying max_mtls and max_cbls supported by LCF

Example of successful invocation

disp_hdlc 0 LCF 0 0 0
Device

GPROC 0 0 0 (CPU ID: 0x114)

Function:
LCF 0 0 0
Legend:* = In Use;
HDLC Channel

HDLC

Channel Offset
----------Range

---------------------------------------------0

0-7

Test

MTL*

CBL*

RSL

RSL

RSL

RSL

RSL

8-15

RSL

RSL

RSL

RSL

RSL

RSL

RSL

RSL

COMMAND ACCEPTED
The output indicates that LCF 0 0 0 is assigned to GPROC 0 0 0 which is currently supporting an
active MTL and CBL device. All other channels are free and configured for the RSL device.

Example of unsuccessful invocation

disp_hdlc 1 LCF 0 0 0
Request made for an unknown function.

Modifying max_mtls and max_cbls supported by LCF

Use the disp_equipment command to ensure that the LCF has the capacity to cope with the
redistribution of the MTL and CBL. This command displays the current settings of the max_mtls
and max_cbls parameters assigned to the LCF when it was equipped.
Use the modify_value command to set the value of the parameters. If the value is acceptable
then a message is displayed that indicates acceptance. For example,

Modify max_mtls and max_cbls supported by LCF

To modify max_mtls and max_cbls use the modify value following command.
For example:
modify_value 0 max_mtls 1 LCF 0 0 0
New maximum can be immediately supported by the parent device.COMMAND ACCEPTED
If the value is not acceptable then a message is displayed that indicates that the device needs
to be reset before the value can be accepted. For example:
modify_value 0 max_cbls 1 LCF 1 0 0
Parent device must be reset before new maximum can be observedCOMMAND REJECTED

68P02901W17-T

9-17
Jan 2010

Reassigning child devices using reassign command

Chapter 9: Configuring Devices and Functions

Reassigning child devices using reassign command

Use the reassign command to change the assignment of a child device (an MTL, CBL, DRI, or
SITE) from its current parent (LCF/DHP) to a new LCF/DHP.

Examples of successful reassignments

To reassign MTL 1 0 0 to LCF 0 0 0 use:
reassign 0 MTL 1 0 0 to LCF 0 0 0
COMMAND ACCEPTED
To reassign CBL 1 0 0 to LCF 0 0 0 use:
reassign 0 CBL 1 0 0 to LCF 0 0 0
COMMAND ACCEPTED

Examples of unsuccessful reassignments

Reassigning MTL 2 0 0 to LCF 0 0 0 when the reassignment would exceed the maximum number
of devices supported by the device:
reassign 0 MTL 2 0 0 to LCF 0 0 0
COMMAND REJECTED: Reassignment would exceed maximum supported by device
Reassigning MTL 2 0 0 to LCF 0 0 0 when the reassignment request cannot be supported due to
an insufficient number of HDLC channels being available on the parent GPROC device:
reassign 0 MTL 2 0 0 to LCF 0 0 0
COMMAND REJECTED: Insufficient GPROC HDLC Channels to support request
Reassigning CBL 0 0 0 to LCF 2 0 0 when the reassignment request cannot be supported due to
the parent GPROC device being out of service:
reassign 0 CBL 0 0 0 to LCF 2 0 0
COMMAND REJECTED: Reassignment attempted to parent which is not in service

Example of successful reassignment

To reassign SITE 1 0 0 to LCF 0 0 0 use:
reassign 0 SITE 1 0 0 to LCF 0 0 0
LCF 0 0 0 now supports Sites: 4 5 6 7 1
COMMAND ACCEPTED

9-18

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reassigning child devices using reassign command

Examples of unsuccessful reassignments

Reassigning SITE 1 0 0 to LCF 0 0 0 when the reassignment would exceed the maximum number
of devices supported by the device:
reassign 0 SITE 1 0 0 to LCF 0 0 0
LCF 0 0 0 already supports Sites: 4 5 6 7 10 2 3 8
COMMAND REJECTED: Reassignment would exceed maximum supported by device
Reassigning SITE 12 0 0 to LCF 0 0 0 when the reassignment request cannot be supported due
to an insufficient number of HDLC channels being available on the parent GPROC device:
reassign 0 SITE 12 0 0 to LCF 0 0 0
COMMAND REJECTED: Insufficient GPROC HDLC Channels to support request
Reassigning SITE 1 0 0 to LCF 2 0 0 when the reassignment request cannot be supported due to
the parent GPROC device being out of service:
reassign 0 SITE 1 0 0 to LCF 2 0 0
COMMAND REJECTED: Reassignment attempted to parent which is not in service

68P02901W17-T

9-19
Jan 2010

Displaying Channel and Circuit Status

Chapter 9: Configuring Devices and Functions

Displaying Channel and Circuit Status

Overview
To monitor timeslot usage on an MMS link (that is, usage of the 32 timeslots on the terrestrial
circuit), use the Circuit Status form.
To view the status of all eight timeslots on an RTF carrier, and the VersaTRAU channel, use
the Channel Status form.
These forms are refreshed periodically at an interval set by a user. Both forms can be used for
diagnostic purposes.

Description
The Circuit Status form provides a GUI front end to the BSS MMI command disp_mms_ts_usage.
This command is issued to the BSS when the Circuit Status form is opened for an MMS, or when
the form is refreshed periodically, or on demand. The command collects the information from
the BSS and sends it back to the OMC-R through a remote login session, and then displays
the information in the Circuit Status form.
The Channel Status form provides a GUI front end to the BSS MMI command disp_rtf_channel.
This command is issued to the BSS when the Channel Status form is opened for an RTF, or when
the form is refreshed periodically, or on demand. The command collects the information from
the BSS and sends it back to the OMC-R through a remote login session, and then displays
the information in the Channel Status form
The parameters required for these commands are gathered from the selected node. The
corresponding generated MMI commands are sent to the remote login process.

Circuit Status form

Displaying the Circuit Status form
To display the Circuit Status form, use one of the following methods:

9-20

Select an MMS from the Navigation Tree, then select the Circuit Status menu from the
menu bar or pop-up menu.

From an MMS Detailed View, select Options-Circuit Status.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Circuit Status form

Description of the Circuit Status form

The Circuit Status form (shown in Figure 9-1) displays the following information:

Site name

Site type.

MSI Id.

MMS Id.

The status of each of the 32 MMS timeslots.

The following values can be displayed for the timeslots:

Unavailable.

Unused (denoted by .).

Active.

Blocked.

Idle.

Unequipped.

Unknown.

RSL.

GBL.

GSL.

GPRS data.

XBL.

OML.

MTL.

CIC.

CBL.

RXCDR link.

DYNET.

16 k DYN RSL.

64 k RSL.

Reserved.

Nailed.

Nailed Path.

68P02901W17-T

9-21
Jan 2010

Circuit Status form

9-22

Chapter 9: Configuring Devices and Functions

Channel.

XBL.

Ater.

Ater*.

RTF.

Sub-equipped RTF.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Circuit Status form

Figure 9-1 Circuit Status form

ti-GSM-CircuitStatusform-00808-ai-sw

Updating the information displayed

To update the information displayed, click the Refresh button.
68P02901W17-T

9-23
Jan 2010

Channel Status form

Chapter 9: Configuring Devices and Functions

Setting a refresh interval

To set a refresh interval for the information displayed in the form, enter a value between 15300
(seconds) in the Refresh Every field in the Options pane at the bottom of the form, then click
Apply.

Logging the information displayed

The information displayed in the form can be logged to the file:
/usr/omc/logs/FORMS/LOG_DIR/CircuitStatus/<filename>
To log information to this file, click the Log to a file checkbox in the Options pane at the bottom
of the form, then click the Apply button.
The <filename> is created using the BSS name, MSI Id, MMS Id, and time, separated by an
underscore, followed by the extension .log, for example:
BSS1029_8_1_20031006_04:03.log
The permission of the folder needs to be set with the t-bit (drwxrwxrwt) and the log files are in
the 0644 (-rw-r--r--) permission. Any user is permitted to view the log file but only the owner
of the log file or the omcadmin has the permission to delete it. The log file can be deleted
while the Circuit Status form is still active. However, a new log file is recreated on the next
refresh if the Log to a file checkbox is selected.

Exceeding the maximum number of logins

If the number of active remote logins sessions reaches 8, the OMC-R is not able to create
another remote login session to collect the necessary data from the node and displays the
following error message:
Unable to launch the Circuit Status dialog.
sessions has been reached.

The maximum number of remote login

Channel Status form

The purpose of the Channel Status form is to:

9-24

Indicate the channels and sub-channel utilizing each RTF timeslot.

Display the status of each channel/sub-channel.

Display the GPRS type, where applicable.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Channel Status form

Displaying the Channel Status form

To display the Channel Status form, use one of the following methods:

Select an RTF from the Navigation Tree, then select the Channel Status menu from the
menu bar or pop-up menu.

From an RTF Detailed View, select Options-Channel Status.

If an RTF is selected and its operational state is not Busy Equipped, the Channel Status form is
not displayed, and the following message is displayed in the message area:
Unable to launch Channel Status dialog RTF <RTF group id, RTF Id> is <Operational
State>

Description of the Channel Status form

The Channel Status form (shown in Figure 9-2) displays the following information:

Site name

Site type

RTF group Id

RTF Id

The following information for each of the eight RTF channel timeslots:
Channel and sub-channel types utilizing each timeslot, for example TCH/R or SDCCH
Status of each channel or sub-channel, for example:

Active

Idle

Intrans (A-I), that is, Active to Idle

Intrans (I-A), that is, Idle to Active

Intrans (U-A), that is, Unavailable to Active

OOS

Unavail(Hopping), that is, timeslot is unavailable due to hopping reconfiguration

Unavail(Band), that is, timeslot is unavailable due to poor interference band

Unavail(Operator), that is, the operator has sub-equipped an RTF

Unavail(Terrestrial), that is, the carrier is unavailable due to a problem with

the terrestrial link

GPRS type, that is, reserved or switchable for the timeslots that support GPRS
If an RTF with pkt_radio_type set to 64 k is EGPRS capable, information on the VersaTRAU
(VT) channel is displayed as follows, regardless of whether the VersaTRAU feature is
restricted or unrestricted:

68P02901W17-T

9-25
Jan 2010

Channel Status form

Chapter 9: Configuring Devices and Functions

The identifier of each DS0 sub-channel in the range 0 - 7.

Status for each DS0, as shown in Table 9-1.
For a DS0 configured for GSM, the status can be:

ACTIVE when there is at least one circuit switched call configured on the DS0.

IDLE when there are no circuit switched calls configured on the DS0, but it
can also be used for circuit switched calls.

N/A unused.

For a DS0 configured for GPRS, the status can be:

ACTIVE .the DS0 is configured for VersaTRAU channel and the DS0 is in-service
(part of a VersaTRAU channel width). The state from the CCU is idle.

ERROR_PCU_CONFIG no acknowledgment on a GPRS VT Config or GPRS

Timeslot Status messages.

ERROR_CCU_CONFIG no acknowledgment on a VT Config messages.

ERROR_CCU_QUERY on acknowledgment for a VT Query message.

ERROR_MISMATCH mismatch between CRM and CCU based on results of

the VT Query message.

ERROR generic errors.

INTRANS the DS0 of a VersaTRAU channel is in one of the following states

from CCU: Initial state I, II, or Static state.

UNUSED when not configured either for GSM or GPRS.

Configuration, as shown in Table 9-1.

Table 9-1 VersaTRAU (VT) channel information in Channel Status form

9-26

DS0

Status

ACTIVE

IDLE

Config

GSM

GSM

UNUSED UNUSED UNUSED INTRANS INTRANS

N/A

N/A

N/A

N/A

GPRS

ACTIVE
GPRS

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Channel Status form

Figure 9-2 Channel Status form

ti-GSM-ChannelStatusform-00809-ai-sw

Updating the information displayed

To update the information displayed, click the Refresh button.

Setting a refresh interval

To set a refresh interval for the information displayed in the form, enter a value between 15300
(seconds) in the Refresh Every field in the Options pane at the bottom of the form, then click
Apply.

68P02901W17-T

9-27
Jan 2010

Channel Status form

Chapter 9: Configuring Devices and Functions

Logging the information displayed

The information displayed in the form can be logged to the file:
/usr/omc/logs/FORMS/LOG_DIR/ChannelStatus/<filename>
To log information to this file, click the Log to a file checkbox in the Options pane at the bottom
of the form, then click the Apply button.
The <filename> is created using the BSS name, RTF Group, RTF Id, and time, separated by
an underscore, followed by the extension .log, for example:
BSS1029_2_2_20031006_04:03.log
The permission of the folder needs to be set with the t-bit (drwxrwxrwt) and the log files are in
the 0644 (-rw-r--r--) permission. Any user is permitted to view the log file but only the owner of
the log file or the omcadmin has the permission to delete it. The log file can be deleted while the
Channel Status form is still active. However, new log file is recreated on the next refresh if the
Log to a file checkbox is selected.

Exceeding the maximum number of logins

If the number of active remote logins sessions reaches 8, the OMC-R cannot create another
remote login session to collect the necessary data from the node and displays the following
error message:
Unable to launch the Channel Status dialog.
sessions has been reached

9-28

The maximum number of remote login

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Hierarchy of devices and functions

Hierarchy of devices and functions

Introduction to the hierarchy of devices and functions

There is a strict hierarchy for creating/equipping devices and functions in the Configuration
Management (MIB) database. Certain devices or functions can only be created/equipped if a
specific sequence is followed. This hierarchy is shown, in part, in the Navigation Tree, and
is illustrated in Figure 9-4 to Figure 9-10. The order in which devices/functions should be
created/equipped is indicated by reading left to right on each level in the following charts.
This hierarchy is also referred to as containment or the parent/child relationship.

BSS/RXCDR containment
Figure 9-3 shows the containment for a BSS or RXCDR.

Figure 9-3 Hierarchy for BSS or RXCDR devices and functions

BSS/RXCDR
(including NESoftware)

DYNETGroup

Assoc_RXCDR/
Assoc_BSS

SITE

PCU

DYNET
XBL

Conn_Link
ti-GSM-HierarchyforBSSorRXCDRdevicesandfunctions-00810-ai-sw

NOTE
DYNETGroup and DYNETs are only visible when BTS-BSC dynamic allocation is
enabled. An Assoc_RXCDR/BSS is only visible under a remotely transcoding site.

68P02901W17-T

9-29
Jan 2010

SITE containment

Chapter 9: Configuring Devices and Functions

SITE containment
Figure 9-4 shows the hierarchy for a SITE.

Figure 9-4 Hierarchy for SITE devices and functions

BSS

SITE

Hardware Devices

Software Functions
(BSC only)

Logical Links

Radio Frequency
(BTS only)

ti-GSM-HierarchyforSITEdevicesandfunctions-00811-ai-sw

9-30

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

SITE containment

SITE - Hardware Devices

Figure 9-5 shows the hierarchy for SITE - Hardware Devices.

Figure 9-5 Hierarchy for Hardware Devices

HARDWARE DEVICES

Cabinet Cage

DHP
(BTS only)

KSWpair

IAS

COMB
(BTS
only)

EAS

GCLK

LAN

TDM

MSI

Processors

KSW

MSS

CSFP

BTP (BTS only)

or BSP (BSC or
RXCDRonly)

GPROC

ti-GSM-HierarchyforHardwareDevices-00812-ai-sw

NOTE
For a Horizonmicro/Horizoncompact cabinet, the DHP is under processors.

SITE - software functions

Figure 9-6 shows the hierarchy for SITE - Software Functions.

Figure 9-6 Hierarchy for Software Functions at BSC only

SOFTWARE FUNCTIONS (BSC only)

LCF

OMF
ti-GSM-HierarchyforSoftwareFunctionsatBSConly-00813-ai-sw

68P02901W17-T

9-31
Jan 2010

SITE containment

Chapter 9: Configuring Devices and Functions

SITE - Logical Links

Figure 9-7 shows the hierarchy for SITE - Logical Links.

Figure 9-7 Hierarchy for Logical Links containment

LOGICAL LINKS (BSC & RXCDR only)

CBL
(BSC only)

MTL/LMTL
(BSC only)

OML

LOGICAL LINKS (BTS)

RSL

PATH

RSL0

ti-GSM-HierarchyforLogicalLinkscontainment-00814-ai-sw

9-32

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

SITE containment

SITE - Radio Frequency

Figure 9-8 shows the hierarchy for SITE - Radio Frequency.

Figure 9-8

Hierarchy for Radio Frequency containment

RADIO FREQUENCY
(BTS ONLY)

CELL

RTFGROUP

RTFGROUP: 0

RTF

DRIGROUP

DRIGROUP: 0

DRI

ti-GSM-HierarchyforRadioFrequencycontainment-00815-ai-sw

68P02901W17-T

9-33
Jan 2010

Motorola product equipage hierarchy

Chapter 9: Configuring Devices and Functions

SITE - Radio frequency - Cell

Figure 9-9 shows the hierarchy for SITE - Radio Frequency - Cell.

Figure 9-9 Hierarchy for Cell containment

CELL
(BTS ONLY)

BLINDSRCHNBR
FREQHOPSYS

HANDOVER POWER
CONTROL

NEIGHBOR

UTRANNBR

SMSCBMSG

TRX

TESTNEIGHBOR

ti-GSM-HierarchyforCellcontainment-00816-ai-sw

SITE - Radio frequency - Cell - handover and power control

Figure 9-10 shows the hierarchy for SITE - Radio Frequency - Cell - handover/power control.

Figure 9-10

Hierarchy for Handover/Power Control containment

HANDOVER/POWER CONTROL
(BTS only)

RELTIMADVHC

RXLEVUIHC

RXQUALUIHC

RXLEVDIHC RXQUALDIHC

RXQUALDIPC

RXLEVDIPC

SURRNDCELLHCR RXLEVUIPC

RXQUALUIPC

ti-GSM-HierarchyforHandoverPowerControlcontainment-00817-ai-sw

Motorola product equipage hierarchy

For further equipage hierarchy information for InCell, M-Cell and Horizonmacro, and M-Cell
Remote Transcoder (RXCDR) systems, see Technical Description: BSS Command Reference
(68P02901W23).

9-34

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a BSP device

Configuring a BSP device

Introduction
The BSP must be a GPROC3.

Definition of a BSP
A Base Site Control Processor (BSP) is the device type of the main BSC/RXCDR control GPROC
in the BSS. A BSP exists at SITE 0 only.

BSP cage and slot restrictions

BSPs may only be equipped on GPROCs with the cage and slot restrictions, based on site type
shown in Table 9-2.

Table 9-2 BSP cage and slot restrictions

Site

Cage number

Slot number

BSC sites

01

20, 2420

RXCDR sites

01

25, 2625

Creating a BSP using the OMC-R GUI

To create a BSP device using the OMC-R GUI, proceed as follows:

Procedure 9-7

68P02901W17-T

Create a BSP device using the OMC-R GUI

Navigate to and select the BSP class button in the Navigation Tree
(BSS BSS instance SITE SITE instance (SITE 0 only)
Hardware Devices Processors BSP). If necessary, see Navigating
to a network object class or instance on page 1-28 for further details.

Select Edit Create from the menu bar. The OMC-R displays the BSP
Detailed View.

Enter all required information, see BSP Detailed View fields for
details.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

9-35
Jan 2010

BSP Detailed View fields

Chapter 9: Configuring Devices and Functions

BSP Detailed View fields

The following sections list and briefly describe the parameter fields in the BSP Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-3 describes the fields in the Identification grouping of the BSP Detailed View.

Table 9-3 BSP Detailed View fields - Identification grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

RDN Class

See description in Table 4-1.

Default is the
device class.

RDN Instance

BSP identifier, see description in

Table 3-1.

0 or 1.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

site. Click to display the parent SITE
Detailed View.

Kit Number

The kit number of the device.

Optional.

Field Replacement
Unit (FRU)
fru_unit
(OMC-R parameter
name:
FR_unit)

The hardware field replaceable unit.

See Maintenance Information: BSS

Optional.

Serial Number

The serial number of the device.

Field Troubleshooting (68P02901W51)

for details of the values displayed for
this and other devices/functions.
Optional.
Continued

9-36

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 9-3

BSP Detailed View fields

BSP Detailed View fields - Identification grouping (Continued)

Field name/BSS
parameter name
Maximum Number
of MTLs
max_mtls

Values

Brief description

Mandatory or
Optional?

0 or 1.
Default is 0.

The number of message transfer links

(A interface) that the BSP handles.
The maximum MTLs prompt is
only applicable for BSC type 0
configurations. It is only visible when
the BSP is in a non-equipped condition.
For a BSC type 0, non-RXCDR system,
the value must be non-zero and equal
for all BSPs. For a BSS type 0, RXCDR
system, the value must be zero.

Mandatory.

Cage and Slot Information grouping

Table 9-4 describes the fields in the Cage and Slot grouping of the BSP Detailed View.

Table 9-4 BSP Detailed View fields - Cage and Slot Information grouping
Field name

Brief description

Values

Mandatory or
Optional?

Cage Identifier
(OMC-R parameter
name:
cageId)

The cage (shelf) number

in which the device
resides.

The range varies depending

on whether the cage is in the
BSC or the BTS. For a BSC or
RXCDR cage the range is 0 13, while a BTS cage is 2 - 5.
For a BSP, see Table 9-2.

Mandatory.

Slot
Number(OMC-R
parameter name:
slot_id)

The slot in which the

device resides.

The range varies depending

on the device. For a BSP, see
Table 9-2.

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

68P02901W17-T

9-37
Jan 2010

Equipping a BSP using the TTY interface

Chapter 9: Configuring Devices and Functions

Equipping a BSP using the TTY interface

To equip a BSP device using the TTY interface, see Modifying a neighbor on page 8-130. The
following is an example of equipping a BSP at the BSC:
-> equip bsc BSP
Enter the BSP identifier: 0
Enter the cage number: 1
Enter the slot number: 20
Enter the maximum MTLs this BSP may manage: 0
COMMAND ACCEPTED

9-38

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a BTP device

Configuring a BTP device

Definition of a BTP
A BTP is the device type of the main BTS control GPROC.

Creating and deleting a BTP in a Horizon II macro cabinet

Creating and deleting the first BTP in a Horizon II macro cabinet causes the automatic creation
or deletion of MSI, CSFP, and GCLK devices.
For example, when the first BTP (RDN 0) is created in a Horizon II macro BTS cabinet, the
following devices are created automatically:

MSI (RDN 0)

CSFP (RDN 0)

GCLK (RDN number will be the same as the BTP number)

When the BTP is deleted these devices are also automatically deleted.

BTP in Horizon II mini cabinet

The OMC-R supports a maximum of one BTP device at a Horizon II mini site (BTP 0). There is no
redundancy available so creation of a redundant BTP is not allowed. Any attempt to create a
second BTP is rejected and the following error message is displayed:
BTP 1 cannot be equipped to this cabinet type.
A Horizon II mini BTS supports only one site controller (HIISC).

BTP cage and slot restrictions

BTPs may only be equipped on GPROCs with the cage and slot restrictions based on site type, as
shown in Table 9-5.

Table 9-5 BTP cage and slot restrictions

Site

Cage number

BSC/RXCDR sites
BTS sites

68P02901W17-T

Slot number
NOT ALLOWED

1514

20 or 2420

9-39
Jan 2010

Creating a BTP from the OMC-R GUI

Chapter 9: Configuring Devices and Functions

Creating a BTP from the OMC-R GUI

To create a BTP device, proceed as follows:

Procedure 9-8 Create a BTP device

1

Navigate to and select the BTP class button in the Navigation Tree
(BSS BSS instance SITE SITE instance (BTS only) - Hardware
Devices Processors BTP). If necessary, see Navigating to a
network object class or instance on page 1-28 for further details.

Select Edit Create from the menu bar. The OMC-R displays the BTP
Detailed View.

Enter all required information in this form. See BTP Detailed View
fields for details.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

BTP Detailed View fields

The following sections list and briefly describe the parameter fields in the BTP Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-6 describes the fields in the Identification grouping of the BTP Detailed View.

Table 9-6

BTP Detailed View fields - Identification grouping

Field name/BSS
parameter name

Brief description

Values

RDN Class

See description in Table 4-1.

Default is the device

class.

RDN Instance

BTP identifier, see description

in Table 3-1.

0 or 1
Default is 0.

NMC RDN Value

See description in Table 4-1.

Mandatory or
Optional?

Continued

9-40

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BTP Detailed View fields

Table 9-6 BTP Detailed View fields - Identification grouping (Continued)

Field name/BSS
parameter name

Brief description

Parent Detailed
View

Displays the name of the parent

SITE. Click to display the parent
SITE Detailed View.

Kit Number

See description in Table 9-3.

Field Replacement
Unit (FRU)

See description in Table 9-3

HIISC is displayed for a BTP at a
Horizon II macro and a Horizon
II mini site.

Serial Number

See description in Table 9-3.

Maximum number
of DRIs
btp_max_dris

The maximum number of DRIs

that can be supported by this
BTP. Cannot be set at M-Cell
sites.

Mandatory or
Optional?

Values

0 - 24.
0 - 6 (if site is
non-M-Cell).
2 (if site is M-Cellmicro,
Horizonmicro2,
Horizoncompact2).
24 (if site is M-Cell2,
M-Cell6, Horizonmacro,
Horizon II macro, or
Horizon II mini).

Mandatory

Cage and Slot Information grouping

Table 9-7 describes the fields in the Cage and Slot Information grouping of the BTP Detailed
View.

Table 9-7 BTP Detailed View fields - Cage and Slot Information grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Cage Identifier

See description in Table 9-4.

See Table 9-5.

Mandatory.

Slot Number

See description in Table 9-4.

See Table 9-5.

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

68P02901W17-T

9-41
Jan 2010

Equipping a BTP using the TTY interface

Chapter 9: Configuring Devices and Functions

State grouping
Table 9-8 describes the unique fields in the State Identification grouping of the BTP Detailed
View. For descriptions of the standard State Information fields, see Table 4-2.

Table 9-8

BTP Detailed View fields - State Information grouping

Field name/OMC-R
parameter name
Assigned DRIs
related_dris
(OMC-R only parameter)

Brief description
Identifiers of the DRIs
assigned to this BTP.

Values

Mandatory or
Optional?
Optional.

Equipping a BTP using the TTY interface

To equip a BTP using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.
The following is an example of equipping a BTP:
-> equip 0 BTP
Enter BTP identifier: 0
Enter the cage number: 15
Enter the slot number: 20
Enter maximum DRIs supported by this BTP: 1
COMMAND ACCEPTED
->

9-42

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a CBL

Configuring a CBL

Definition of a CBL
A CBL is a Cell Broadcast Link. A CBL is contained only within site 0 (BSC) at a BSS.

Creating a CBL using the OMC-R GUI

To Create a CBL using the OMC-R GUI, proceed as follows:

Procedure 9-9 Create a CBL using the OMC-R GUI

1

Navigate to and select the CBL class button in the Navigation Tree
(BSS BSS instance SITE SITE instance (SITE 0 only) Logical
Links CBL). If necessary, see Navigating to a network object class
or instance on page 1-28 for further details.

Select Edit Create from the menu bar. The OMC-R displays the CBL
Detailed View.

Enter all the required information. See CBL Detailed View fields
for details.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

CBL Detailed View fields

The following sections list and briefly describe the parameter fields in the CBL Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

68P02901W17-T

9-43
Jan 2010

Equipping a CBL using the TTY interface

Chapter 9: Configuring Devices and Functions

Identification grouping
Table 9-9 describes the fields in the Identification grouping of the CBL Detailed View.

Table 9-9

CBL Detailed View fields - Identification grouping

Field name/BSS
parameter name

Values

Brief description

Mandatory or
Optional?

MSI Identifier

The particular link for this

device.

0 - 95.

Mandatory.

MMS Timeslot
Identifier

The identifier of the timeslot

for this device.

1 - 31 for E1 links.

Mandatory.

RDN Class

See description in Table 4-1.

Default is the
device class.

RDN Instance

CBL identifier, see description

in Table 3-1.

Default is 0.

Mandatory.

NMC RDN Value

See description in Table 4-1.

Parent Detailed View

Displays the name of the

parent site. Click to display
the parent SITE Detailed
View.

BSC Operator
BSC_Operator

The name of the BSC operator.

Any string (up to

20 characters)
enclosed in ( ).

Mandatory.

CBC Operator
CBC_Operator

The name of the CBC

operator.

Any string (up to

20 characters)
enclosed in ( ).

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Equipping a CBL using the TTY interface

To equip a CBL using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.
The following is an example of equipping a CBL device.
->
equip 0 CBL

9-44

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping a CBL using the TTY interface

Enter the device id for the CBL: 0

Enter the first MMS description for this device: 1
Enter the second MMS description for this device: 1
Enter timeslot on MMS where this device appears: 6
Enter the BSS operator: jenny
Enter the CBC operator: becky
COMMAND ACCEPTED
->

68P02901W17-T

9-45
Jan 2010

Configuring a CIC

Chapter 9: Configuring Devices and Functions

Configuring a CIC

Introduction to configuring CICs

CICs equipped at the BSC are children of their associated AXCDR. CICs equipped at the RXCDR
are children of their ABSS.
If either the Enhanced BSC Capacity feature or the GSM HR and/or AMR features have not been
purchased and enabled, then only a maximum of 2400 CICs can be equipped at a BSC.
If the Enhanced BSC Capacity on page 2-94 feature has been purchased and enabled, a
maximum of 3200 CICs and 600 carriers can be equipped at a BSC.
If either the GSM HR and/or AMR feature have been purchased and enabled, a maximum of
4800 CICs can be equipped at an RXCDR site.

NOTE
CICs cannot be created, modified, or deleted using the OMC-R GUI.

Impact of Enhanced GDP Provisioning on a CIC

If a user attempts to specify the MMS belonging to a secondary GDP as the MSC MMS for a CIC
device, an error message is displayed. For more information of Enhanced GDP Provisioning, see
Configuring Enhanced GDP provisioning on page 9-146.

Equipping CICs using the TTY interface

To equip a CIC using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.

NOTE
The Local Maintenance flag does not prevent the equipage, unequipping, or any other
management of the CIC device from the MMI interface.

9-46

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying CIC information using the TTY interface

Equipping at a local transcoding BSC

For example, the following command equips CICs 10 to 15 on MMS 4 0 at a local transcoding
BSC:
-> equip 0 cic
Enter CIC(s): 10 to 15
Enter the MMS ID to the MSC: 4 0
Enter the starting timeslot: 1
COMMAND ACCEPTED
When equipping a CIC at a remote transcoding BSC, the AXCDR providing the TRAU resource
for the CIC must be specified.

Equipping at an RXCDR
When equipping a CIC at an RXCDR, the system prompts for the id of the ABSS managing the
CIC. The user can use the same CIC number for multiple ABSSs.
For example, the following command equips CICs 255 to 286 on MMS 4 1 at RXCDR 42. The
same range of CICs is managed by ABSS 16 and assigned to MMS 17 0 between the RXCDR
and the MSC:
->
equip 0 cic
Enter CIC(s):

255 to 286

Enter the ABSS which manages the CIC(s):

16

Enter the MMS ID to the ABSS: 4 1

Enter the starting timeslot:

Enter the starting subgroup:

Enter the MMS ID to the MSC: 17 0

Enter the starting timeslot:

COMMAND ACCEPTED

Displaying CIC information using the TTY interface

To display information about a CIC using the TTY interface, see Methods of configuring
individual devices and functions on page 9-3.

Displaying at a local transcoding BSC

For example, the following command displays information for CIC 282 on MMS 1 0 at BSS
21 (where the CIC goes through AXCDR 32):
disp_equipment 0 CIC 282

68P02901W17-T

9-47
Jan 2010

Displaying CIC information using the TTY interface

Chapter 9: Configuring Devices and Functions

Displaying at an RXCDR
For example, the following command displays information for CIC 286 at RXCDR 42 (where
the CIC is managed by ABSS 16):
disp_equipment 0 CIC 286
CIC ID

ABSS ID

ATER MMS
ID

9-48

TS

TRAU MMS
GRP

ID

TS

------

-------

--- --- ---

--- ----

286

16

4 1

17 0

COMMENTS/REASON
---------------

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a COMB device

Configuring a COMB device

Definition of COMB
A Combiner (COMB) can be either a Remote Tuneable Combiner (RTC) or a Cavity Combining
Block (CCB). COMBs cannot be equipped at M-Cellmicro, M-Cellaccess, M-Cellcity,
Horizonmicro, or Horizoncompact sites.
Alarms occurring from COMBs are displayed in the Alarms window at the OMC-R.

Configuration of RTC
An RTC includes two processors and five cavities. Up to 14 combiners may be equipped at
a BTS site. A combiner can be arranged to provide a single antenna output from inputs of
five transceivers (Tx/Rx) or two outputs. One output can be associated with three transceiver
inputs, and the other output with two transceiver inputs. Additionally, two combiners can be
interconnected to provide a common output from inputs of ten transceivers.
Each of the two combiner processors is assigned a DRI to provide tuning commands, and
accept tuning verification responses. The physical layer for these links includes both the
DRI/DRIX-transceiver fiber optic connections, and the transceiver-COMB transmit coaxial cable.

NOTE
Tuning control for all cavities can be controlled by a single DRI.
Figure 9-11 illustrates the configuration of an RTC.

68P02901W17-T

9-49
Jan 2010

RTC hardware addresses

Chapter 9: Configuring Devices and Functions

Figure 9-11 Configuration of RTC (InCell)

CO MB 0 ADDRE SS 45
ID = 0 0

DRI

DRIX

Tx /Rx

ID = 0 1

DRI

DRIX

Tx /Rx

ID = 0 2

DRI

DRIX

Tx /Rx

ID = 0 3

DRI

DRIX

Tx /Rx

ID = 0 4

DRI

DRIX

Tx /Rx

TO ANTE NNA

INDIV IDUA L CAVITY TUNING CO NTRO L USES

SER IAL DATA (1200 BAU D) OVER TRANSM IT
CA BLE FRO M TX/RX . AFTER TUNING , COMB
PR OCESSO R SEN DS VER IFICATION TO TX/RX.
EQUIP PING THE COMB IDENTIFIES CONTROLLING
AND STANDB Y DRIS FOR THE TUNING LINK.

CO MB 1 ADDRE SS 46
ID = 1 5

DRI

DRIX

Tx /Rx

ID = 1 6

DRI

DRIX

Tx /Rx
TO ANTE NNA

ID = 1 7

DRI

DRIX

Tx /Rx

ID = 2 8

DRI

DRIX

Tx /Rx
TO ANTE NNA

ID = 2 9

DRI

DRIX

Tx /Rx
ti-GSM-SC01W17-000074-eps-sw

RTC hardware addresses

Identical RTC hardware addresses at a site are not permitted. The addresses should be
allocated as in Figure 9-12.

9-50

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Figure 9-12

RTC hardware addresses

CAB 15

CAB 14

ADRS7
ADRS6
ADRS5
ADRS4
ADRS3
ADRS2
ADRS1
ADRS0
RS232A
RS232B
CAV5 LINKA
CAV5 LINKB
CAV4 LINKA
CAV4 LINKB
CAV3 LINKA
CAV3 LINKB
CAV2 LINKA
CAV2 LINKB
CAV1 LINKA
CAV1 LINKB
CAV0 LINKA
CAV0 LINKB
PARKING
PARKING
PARKING

GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND

DRI and Combiner configuration

ADDRESS 255

GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND

CAB 13

ADRS7
ADRS6
ADRS5
ADRS4
ADRS3
ADRS2
ADRS1
ADRS0
RS232A
RS232B
CAV5 LINKA
CAV5 LINKB
CAV4 LINKA
CAV4 LINKB
CAV3 LINKA
CAV3 LINKB
CAV2 LINKA
CAV2 LINKB
CAV1 LINKA
CAV1 LINKB
CAV0 LINKA
CAV0 LINKB
PARKING
PARKING
PARKING

GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND

ADDRESS 254

ADRS7
ADRS6
ADRS5
ADRS4
ADRS3
ADRS2
ADRS1
ADRS0
RS232A
RS232B
CAV5 LINKA
CAV5 LINKB
CAV4 LINKA
CAV4 LINKB
CAV3 LINKA
CAV3 LINKB
CAV2 LINKA
CAV2 LINKB
CAV1 LINKA
CAV1 LINKB
CAV0 LINKA
CAV0 LINKB
PARKING
PARKING
PARKING

ADDRESS 253
ti-GSM-RTChardwareaddresses-00819-ai-sw

DRI and Combiner configuration

See Configuring a DRI on page 9-63 for further information of configuring DRIs and
Combiners.

Creating a COMB device using the OMC-R GUI

To create an instance of a COMB device, proceed as follows:

Procedure 9-10 Create an instance of a COMB device

68P02901W17-T

Navigate to and select the CBL class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Hardware Devices
COMB). If necessary, see Navigating to a network object class or
instance on page 1-28 for further details.

Select Edit Create from the menu bar. The OMC-R displays the
COMB Detailed View.

Enter all the required information. See COMB Detailed View fields
for details of the fields.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

9-51
Jan 2010

COMB Detailed View fields

Chapter 9: Configuring Devices and Functions

COMB Detailed View fields

The following sections list and briefly describe the parameter fields in the COMB Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-10 describes the fields in the Identification grouping of the COMB Detailed View.

Table 9-10

COMB Detailed View fields - Identification grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

RDN Class

See description in Table 4-1.

Default is
device class.

RDN instance

See description in Table 3-1.

0 - 13.
Default is 0.

Mandatory.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

SITE. Click to display the parent SITE
Detailed View.

Kit Number

See description in Table 9-3.

Field Replacement
Unit (FRU)

See description in Table 9-3.

Serial Number

See description in Table 9-3.

Combiner Address
combiner_address

The address recognized by the DRIs for

the identified combiner. This address
must be unique.
Can be specified during creation, or
later, if necessary.

0 - 255.

Mandatory.

Controlling DRI 0
control_dri0

The DRI that links to the combiner

processor 0.
Because DRIs do not have to be
equipped before COMBs, the fields First
Controlling DRI and Second Controlling
DRI 1 may contain NULL.

Optional.

Continued

9-52

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 9-10

Equipping a COMB using the TTY interface

COMB Detailed View fields - Identification grouping (Continued)

Field name/BSS
parameter name
Controlling DRI 1
control_dri1

Brief description

Values

The DRI that links to the combiner

processor 1.
Because DRIs do not have to be
equipped before COMBs, the fields First
Controlling DRI and Second Controlling
DRI 1 may contain NULL.

Mandatory or
Optional?
Optional.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details. Additional Last OMC
Administrator field shows username of OMC Administrator.

Equipping a COMB using the TTY interface

To equip a COMB using the TTY interface, see Methods of configuring individual devices
and functions on page 9-3.

Displaying COMB details using the TTY interface

To display information about a COMB using the TTY interface, see Methods of configuring
individual devices and functions on page 9-3.
For example, the following command displays COMB details:
disp_equipment 0 COMB 0

68P02901W17-T

9-53
Jan 2010

Configuring a CSFP device

Chapter 9: Configuring Devices and Functions

Configuring a CSFP device

Definition of a CSFP
A Code Storage Facility Processor (CSFP) is a GPROC device which facilitates the propagation
of new software instances with reduced system downtime. A software instance is a complete set
of software/firmware and database objects.

NOTE
DHPs, LCFs and in-service BTPs/BSPs may NOT be configured as a CSFP. Only
standby BSPs/BTPs or unused GPROCs may be configured as a CSFP.
CSFPs cannot be equipped/unequipped/configured/unconfigured by a user at an M-Cell site.
CSFP 0 is automatically equipped at an M-Cell site when the first BTP at a site is equipped. A
second CSFP can be equipped at the BSC for BSS loads.

Methods of creating a CSFP

Two basic methods exist to configure a CSFP, as follows:

Use the Configure CSFP option from the OMC-R GUI Navigation Tree. The BSS scans
all sites for GPROCs with potential to become CSFPs. At each site where a candidate
is located, a CSFP is equipped. If no candidate is found, no CSFP is created at that
site and the next site is scanned. This method facilitates simple equipage of the CSFP,
leaving the choice of GPROC and logistics of equipage to the BSS based upon a stealing
algorithm. The equipage can be undone either by the Navigation Tree or the unequip or
unconfigure_csfp commands. The configure_csfp and unconfigure_csfp commands
are BSS wide commands.

To equip a CSFP using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3. This method creates a CSFP on a specific GPROC at a specific site.

GPROC cage and slot restrictions

CSFPs may only be equipped on GPROCs with cage and slot restrictions based on site type, as
shown in Table 9-11.

9-54

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

CSFP Detailed View fields

Table 9-11 GPROC cage and slot restrictions

Site

Cage numbers

Slot numbers

BSC sites

0 to 13

18 to 25

BTS sites

2 to 15

18 to 25

RXCDR sites

0 to 13

25 or 26

CSFP Detailed View fields

The following sections list and briefly describe the parameter fields in the CSFP Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-12 describes the fields in the Identification grouping of the CSFP Detailed View.

Table 9-12 CSFP Detailed View fields - Identification grouping

Field name/OMC-R
parameter name

Brief description

Values

RDN Class

See description in Table 4-1.

Default is device class.

RDN instance

See description in Table 3-1.

0 - 1.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

SITE. Click to display the parent
SITE Detailed View.

Kit Number

See description in Table 9-3.

Field
Replacement
Unit (FRU)

See description in Table 9-3.

Serial Number

See description in Table 9-3.

Site Number
csfpSiteName

The name of the containing site.

Cage Identifier

See description in Table 9-4.

Mandatory or
Optional?

Mandatory.
See Table 9-11.

Optional
Continued

68P02901W17-T

9-55
Jan 2010

Creating a CSFP device using the OMC-R GUI

Chapter 9: Configuring Devices and Functions

Table 9-12 CSFP Detailed View fields - Identification grouping (Continued)

Field name/OMC-R
parameter name

Mandatory or
Optional?

Values

Brief description

Slot Number

See description in Table 9-4.

See Table 9-11.

Optional

Equipage Type
equip

How the CSFP was equipped.

Through equip_device
(5) or config_csfp (6).
At an M-Cell site, the
default is 5 for the
auto-created CSFP.

Mandatory

CSFP Acquired
From
conf_id

The device from which the CSFP

was acquired.

At M-Cell site, when

CSFP is auto-created,
contains the value of
GPROC.
Displays NULL for
equipped CSFPs,
as it only applies to
configured CSFPs.

Mandatory

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Creating a CSFP device using the OMC-R GUI

To configure a CSFP device from the Navigation Tree using the default setting of ANY for
the stealing algorithm, proceed as follows:

Procedure 9-11 Configure a CSFP device using the OMC-R GUI

1

Select the required BSS/RXCDR in the Navigation Tree.

Click and hold down the right mouse button to display the Navigation
Tree popup menu.

Select Load Mgt NESoftware from the menu to display the

NESoftware Detail View.

Select Edit Edit from the menu bar.

Select CSFP Configure CSFP from the menu bar.

A confirmation box is displayed.
Continued

9-56

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Unconfiguring CSFP devices using the OMC-R GUI

Procedure 9-11 Configure a CSFP device using the OMC-R GUI (Continued)
6

Select OK to send a request to the parent NE to configure a CSFP

device at each of its sites.
To abort the request, select Cancel.

Save and close the Detailed View.

To configure a CSFP device using one of the other settings for the stealing algorithm, refer to
Equipping a CSFP device using the TTY interface in this section.

Unconfiguring CSFP devices using the OMC-R GUI

To unconfigure a CSFP device using the OMC-R GUI, proceed as follows:

Procedure 9-12 Unconfiguring a CSFP device using the OMC-R GUI

1

Display the NESoftware Detail View. See steps 1 to 4 in Creating a

CSFP device using the OMC-R GUI.

Select CSFP - Unconfigure CSFP from the menu bar. A confirmation

box is displayed.

Select OK to send a request to the parent NE to unconfigure CSFP

devices at each of its sites. To abort the request, select Cancel.

Save and close the Detailed View.

Equipping a CSFP device using the TTY interface

To equip a CSFP using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.
The following is an example of equipping a CSFP:
->
equip bsc CSFP
Enter the CSFP identifier:
Enter the cage number:

13

Enter the slot number:

20

COMMAND ACCEPTED
->

68P02901W17-T

9-57
Jan 2010

Using other settings of stealing algorithm

Chapter 9: Configuring Devices and Functions

Using other settings of stealing algorithm

To configure a CSFP device using one of the other settings for the stealing algorithm, proceed
as follows:

Procedure 9-13 Configure a CSFP device using one of the other settings for the
stealing algorithm
1

Remote login to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39 and Changing
security level (for TTY interface commands) on page 1-43, respectively.

To display the per-site CSFP algorithm and thus confirm the current
setting of the stealing algorithm, enter the command:
disp_csfp <location> algorithm
For example, to show the CSFP stealing algorithm at the BSC, use
the command:
disp_csfp bsc algorithm

To change the value of the stealing algorithm or the flow control,

enter the command:
chg_csfp <element> <value> <location>
For example, to set the stealing algorithm at the BSC to use only
pooled GPROCs, the command is:
chg_csfp algorithm POOL bsc

Log out of the TTY session and return to the Front Panel.

Follow the procedure described in Creating a CSFP device using the

OMC-R GUI to configure the CSFPs.

For a detailed description of the disp_csfp and the chg_csfp commands refer to: Technical
Description: BSS Command Reference (68P02901W23).

9-58

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a DHP device

Configuring a DHP device

Definition of a DHP
A Digital Host Processor (DHP) is the device type of the DRI control processor. The underlying
GPROC does not have to be equipped to equip a DHP.

DHP cage and slot restrictions

Valid cage and slot numbers are dependent on the site type, as shown in Table 9-13.

Table 9-13 DHP cage and slot restrictions

Site

Cage number

Slot number

BTS sites

2 to 15

18 to 25

Horizonmicro2 and Horizoncompact2 DHPs

In Horizonmicro2 and Horizoncompact2 the slave BTS main control units (MCUs)
are represented by Digital Host Processor (DHP) devices. Before Horizonmicro2 and
Horizoncompact2 were introduced, DHP devices could not exist at an M-Cell or Horizon BTS
site. However, DHP devices do exist at InCell BTS sites.
The BSS software supports two DHPs at a Horizonmicro2 and Horizoncompact2 BTS site.
The operation of a Horizonmicro2 and Horizoncompact2 is different to the operation of an InCell
BTS DHP device. At a Horizonmicro2 and Horizoncompact2 BTS site, DRI devices are statically
assigned to a Cabinet device (rather than a Cage), and a parent-child relationship exists
between the DHP device of the Cabinet and the DRI devices assigned to it. The DHP device id is
equal to the device id of the Cabinet device to which it corresponds.
The Cabinet device first identifier is equal to the number of the fiber port which is used to
connect to the slave BTS. The Horizonmicro2 and Horizoncompact2 BTS DHP device can
therefore have an id of 1 0 0 or 2 0 0.
See Introduction to BSC and BTS sites on page 7-2 for further details of Horizonmicro2 and
Horizoncompact2.

68P02901W17-T

9-59
Jan 2010

Configuring a DHP at a Horizonmicro2 or Horizoncompact2 BTS

Chapter 9: Configuring Devices and Functions

Configuring a DHP at a Horizonmicro2 or Horizoncompact2 BTS

When creating a Cabinet for a Horizonmicro2 or Horizoncompact2 BTS, the OMC-R
automatically creates a DHP. This is referred to as autoequipping. Likewise when a Cabinet
is deleted for a Horizonmicro2 or Horizoncompact2 BTS, the OMC-R deletes the DHP. For
this reason, the Edit Create and Edit Delete Navigation Tree menu options, and the
Delete menu option in the DHP Detailed View, are grayed-out when a Horizonmicro2 or
Horizoncompact2 BTS is selected.

Creating a DHP using the OMC-R GUI

To create a DHP device, follow these steps:

Procedure 9-14 Create a DHP device

1

Navigate to and select the DHP class button in the Navigation Tree
(BSS - BSS instance - SITE - SITE instance - Hardware Devices - Cage Cage instance - DHP). If necessary, see Navigating to a network object
class or instance on page 1-28 for further details.

NOTE
For Horizonmicro/Horizonmicro2 and
Horizoncompact/Horizoncompact2 the DHP device resides
under SITE - Processors group, because these products
do not have Cages.
2

Select Edit Create from the menu bar. The OMC-R displays the DHP
Detailed View form.

Enter all required information. See DHP Detailed View fields for
details of the fields.

Create and close the Detailed View. If required, see Creating a network
object using the OMC-R GUI on page 1-32 for further details.

DHP Detailed View fields

The following sections list and briefly describe the parameter fields in the DHP Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

9-60

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DHP Detailed View fields

Identification grouping
Table 9-14 describes the fields in the Identification grouping of the DHP Detailed View.

Table 9-14 DHP Detailed View fields - Identification grouping

Field name/OMC-R
parameter name

Brief description

Values

RDN Class

See description in Table 4-1.

Default is
device class.

RDN instance

See description in Table 3-1.

0 - 7.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent Cage.

Click to display the parent Cage
Detailed View.

Kit Number

See description in Table 9-3.

Field
Replacement Unit
(FRU)

See description in Table 9-3.

Serial Number

See description in Table 9-3.

Maximum
Number of DRIs
dhp_max_dris

Defines the number of DRI devices the

DHP can support.

Mandatory or
Optional?

1 - 6.
Mandatory.
At a
Horizonmicro2
or
Horizoncompact2,
set to 2.

Cage and Slot Information grouping

Table 9-15 describes the fields in the Cage and Slot Information grouping of the DHP Detailed
View.

Table 9-15

DHP Detailed View fields - Cage and Slot Information grouping

Field name

Brief description

Values

Cage Id

See description in Table 9-4.

See Table 9-13.

Slot Number

See description in Table 9-4.

See Table 9-13.

68P02901W17-T

Mandatory or
Optional?

9-61
Jan 2010

Equipping a DHP using the TTY interface

Chapter 9: Configuring Devices and Functions

State grouping
Table 9-16 describes the unique fields in the State Identification grouping of the DHP Detailed
View. For descriptions of the standard State Information fields, see Table 4-2.

Table 9-16 DHP Detailed View fields - State Information grouping

Field name/OMC-R
parameter name
Assigned DRIs
related_dris
(OMC-R only attribute)

Values

Brief description

Mandatory or
Optional?

Identifiers of the DRIs

assigned to this DHP.

Optional.

Equipping a DHP using the TTY interface

To equip a DHP device using the TTY interface, see Methods of configuring individual devices
and functions on page 9-3.
The following is an example of equipping a DHP:
->
equip 1 DHP
Enter the cage number for this DHP (identifier 1):

15

Enter the unique DHP number in the cage (identifier 2):

Enter the slot number:

18

Enter the maximum number of DRIs supported by this DHP: 1

COMMAND ACCEPTED
->

Equipping multiple DHP devices

To equip multiple DHP devices, proceed as follows:

Procedure 9-15 Equip multiple DHP devices

9-62

If necessary, lock the site, either from the Navigation Tree, or by using
the lock_device command.

Equip the DHPs.

If necessary, unlock the site, either from the Navigation Tree, or by

using the unlock_device command.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a DRI

Configuring a DRI

Definition of a DRI
The Digital Radio Interface (DRI) provides the logical interface between the Radio Channel Unit
(RCU) and the TDM bus.
A DRI is contained within an DRIGroup.

NOTE
Once equipped, the DRI can be reassigned to another GPROC by using the reassign
command or the Reassign option of the Misc menu from the MML Command
Constructor window. Refer to Reassigning a DRI device on page 9-77 for more
information.
For a non-M-Cell site there can be up to 36 DRIs on a TDM highway.
DRI cardinality depends on the following conditions:

Non-M-Cell site: 12 (0 to 11) per DRIGroup.

M-Cellmicro site: 2 (0 to 1) per DRIGroup.

Horizonmicro2/Horizoncompact2 site: 2 (0 to 1) per DRIGroup.

Horizonmacro, Horizonmacro_ext, Horizon II macro, Horizon II macro_ext BTS sites: 12

per DRI Group. If11 DRIs exist, a Single density DRI can be changed to a Double density
DRI, but a Single density DRI cannot be created.

Horizonmacro/Horizon II macro/M-Cell6 BTS site: 24 DRIs.

For details of Voltage Standing Wave Ratio (VSWR), see OMC-R Online Help, Network
Operations and Installation and Configuration: BSS Optimization (68P02901W43).

DRIGroup
The DRIGroup object class describes a single DRI function grouping within the site. A DRIGroup
consists of one or more DRIs which are connected to the same antenna and which use the same
portion of the TDM bus. Instances of this object are only created as placeholders for contained
DRI object instances. There is a DRIGroup Detailed View in the OMC-R GUI.

68P02901W17-T

9-63
Jan 2010

Prerequisites for configuring a DRI

Chapter 9: Configuring Devices and Functions

Prerequisites for configuring a DRI

Before a DRI can be created:

The Algorithm Number field (parameter name: alg_num) in each of the nine cell algorithm
Detailed View forms must be changed from Unused (255) to another setting.

At a remote BTS, one or more Receive Transmit Functions (RTF) must be equipped. (An
RTF is the function that supports the air interface channel and the DRI/transceiver pair.)

Impact of Dual Band Cells feature on DRI/RTFs

When the Dual Band Cells feature is enabled for a cell, DRIs and RTFs within the dual band cell
must have different DRI or RTFGroup identifiers. When equipping DRIs, the two DRI/RTFGroup
identifiers are allowed if the cell is dual band.
For a dual band cell, the secondary and primary band frequency types must be allowed by the
cabinet(s) to which the DRI(s) in each zone are equipped.
For non-dual band cells, all DRIs and RTFs equipped to a cell must be configured in a single
DRI/RTFGroup.

Horizonmicro2 and Horizoncompact2 DRIs

Horizonmicro2 and Horizoncompact2 BTS sites can support up to six DRIs, two at the master
BTS and two at each slave BTS. It is necessary therefore that Digital Radio Interface (DRI)
devices are equipped to represent the radio equipment at each slave BTS.
A maximum of two DRI devices are equipped for each slave BTS cabinet. The DHP device at a
slave BTS must be in service before a DRI device at that BTS can come into service, therefore,
there exists a parent-child relationship between the DHP and DRI device.
A maximum of three DRIGroups can exist at a Horizonmicro2 and Horizoncompact2 BTS. The
DRIs in a DRIGroup are associated with the same Cabinet and are assigned to the DHP residing
below it. The BSS displays an error message if an attempt is made to equip a DRI to a DRIGroup
and a Cabinet, if the Cabinet already has a DRI assigned to it but in a different DRIGroup.
Both DRIs must be in the same cell, and of the same frequency. Therefore even if the DRI
devices belong to a dual band cell, both DRIs must be in the same DRIGroup.
When a DHP device comes into service, an attempt is made to bring that DHP device child
DRIs into service. Similarly, when a DHP goes out of service, that DHP device child DRIs are
taken out of service.
DRI transition functionality for the slave BTS DRIs are the same as that for the master BTS DRIs
with two main exceptions.

The first exception accounts for the fact that the DRI is located at a slave BTS and not
at the master BTS.

The second exception concerns the DHP-DRI parent-child relationship, a new device state
and several new device state transitions are needed for the slave BTS DRI devices.

The TRAU data is switched from the radios to the fiber link at the slave BTS, and from the
fiber link to the E1 link at the master BTS.

9-64

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DRI and Combiner configuration

See Introduction to BSC and BTS sites on page 7-2 for further details of Horizonmicro2 and
Horizoncompact2.

DRI and Combiner configuration

DRI and Combiner equipage hierarchy allows DRIs be created before the Combiner. Therefore,
DRIs and Combiners do not follow a strict parent-child relationship.
When the DRI and Combiner have been created, at a later date, if reconfiguration is required,
some of the DRI-COMB configuration parameters can be modified. This prevents the need to
unequip and then re-equip DRIs and Combiners.
The role of the DRI in the system-combining is specified when the DRI is equipped, as opposed to
when the COMB is equipped. See Configuring a COMB device on page 9-49 for further details.
All operational activities performed are applied to a single device. Indirect control of each
Combiner can be achieved using commands directed at the respective controlling DRI. All
commands provide a complete set of Combiner device information, including address and
cavity assignments.
Figure 9-13 shows DRI-Combiner configuration.

Figure 9-13 DRI-Combiner configuration

Single Combiner Device
COMB 0

First
Controlling DRI

DRI 0 0

DRI 0 1

Second
Controlling DRI

ti-GSM-DRI-Combinerconfiguration-00820-ai-sw

68P02901W17-T

9-65
Jan 2010

Double Density DRIs in a Horizon II mini

Chapter 9: Configuring Devices and Functions

Double Density DRIs in a Horizon II mini

A DRI residing in a Horizon II mini or Horizon II mini extension cabinet can be equipped as
double density.
A Horizon II mini cabinet can support a maximum of two physical CTU2/CTU2-D devices and
allows the following combinations:

1 x SD CTU2/CTU2-D (1 DRI)

2 x SD CTU2/CTU2-D (2 DRIs)

1 x DD CTU2/CTU2-D (2 DRIs)

1 x DD CTU2/CTU2-D + 1 x SD CTU2/CTU2-D (3 DRIs)

2 x DD CTU2/CTU2-D (4 DRIs)

The OMC-R supports a maximum of four DRIs (two physical CTU2s) at a Horizon II mini or
Horizon II mini extension cabinet.

Configuring Double density DRIs

Creating
When the cabinet type in which the DRI resides is a Horizon II mini, Horizon II mini extension,
Horizon II macro, Horizon II macro_ext, Horizonmacro, or Horizonmacro_ext, the DRI can be
specified as Single or Double density using the DRI Density (dri_density) parameter. When
the DRI is specified as Double density, the RDN of the associated DRI (assoc_dri_id) must be
specified.
The OMC-R then automatically creates the associated DRI with the specified RDN. The
autocreated DRI inherits the properties of the original DRI, apart from the Associated DRI Id
(assoc_dri_id), Preferred RTF Group Id (pref_rtf_group_id), Preferred RTF Id (pref_rtf_id),
and Transceiver Flag (transceiver_flag) parameters. The Associated DRI Id (assoc_dri_id) of
the autocreated DRI is the original DRI id. The Preferred RTF Group Id (pref_rtf_group_id),
and Preferred RTF Id (pref_rtf_id) parameters can be entered by the user after autocreation. If
the transceiver_flag is set to 0 in the original DRI, it is set to 1 in the autocreated DRI. If the
transceiver_flag is set to 1 in the original DRI, it is set to 0 in the autocreated DRI.
Two DRIs operating together for Double density operation are referred to as DRI pair.
See DRI Detailed View fields for further details of the Double density parameter fields
mentioned in this section.
In a non-Horizon II macro BTS where a cell is set to baseband hopping (that is, hopping_support
= 2), the DRI cannot be set to Double density.

9-66

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring Double density DRIs

Double density mode is not supported simultaneously with four branch receive diversity.
The configuration of a Dual Band cell with 4 Branch Receive Diversity capability is possible
with the restriction that the cell contains multiple Single Band cabinets, 1 or more of each
frequency band type.
If the DRI Density (dri_density) parameter is changed from Double density to Single density,
the associated DRI is automatically deleted. The dri_density parameter can only be changed
from Double density to Single density, if the DRI and associated DRI are both locked.
To modify the Associated DRI Id (assoc_dri_id) parameter of a DRI using the DRI Detailed
View, follow these steps:

Procedure 9-16 Modify the Associated DRI Id

1

Lock both DRIs in the DRI pair.

Change DRI Density (dri_density) to Single (1).

Save the DRI Detailed View with the changed details.

Change DRI Density (dri_density) to Double (2) or Capacity (3).

Enter the new Associated DRI Id (assoc_dri_id).

Save the DRI Detailed View with the changed details.

Deleting
Before deleting one DRI in a DRI pair, both DRIs must be locked. When one DRI in a DRI pair is
deleted, the dri_density of other DRI is set to Single, the assoc_dri_id is greyed-out and the
transceiver_flag is set to 0 and greyed-out

Resetting
If an attempt is made to reset a DRI in a DRI pair, the following message is displayed:
WARNING: The reset will affect the DRI and the associated DRI. Do you wish to
continue?
If the user opts to continue, both DRIs in the DRI pair are reset.

68P02901W17-T

9-67
Jan 2010

Creating a DRI using the OMC-R GUI

Chapter 9: Configuring Devices and Functions

Creating a DRI using the OMC-R GUI

To create a DRI device using the OMC-R GUI, proceed as follows:

Procedure 9-17 Create a DRI device

1

Navigate to and select the DRI class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Radio Frequency
DRIGROUP DRIGROUP instance DRI). If necessary, see Navigating
to a network object class or instance on page 1-28 for further details.

Select Edit Create from the menu bar. The OMC-R displays the DRI
Detailed View form.

Enter all required information. See DRI Detailed View fields for
details of the fields.

Create and close the Detailed View. If required, see Creating a network
object using the OMC-R GUI on page 1-32 for further details.

DRI Detailed View fields

The following sections list and briefly describe the parameter fields in the DRI Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-17 describes the fields in the Identification grouping of the DRI Detailed View.

9-68

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DRI Detailed View fields

Table 9-17 DRI Detailed View fields - Identification grouping

Field name/BSS
parameter name

Mandatory or
Optional?

Brief description

Values

DRI Type
(OMC-R
parameter
name:
DRI_type)

Device type of this DRI instance.

Currently, a DRI can only be
created as type DRIM (0) at a
non-M-Cell site. DRI-DRIM and
DRI-ACM type DRIs can only be
created at a non-M-Cell site.

0, 2 or 9, where:
DRIM (0),
TCU (2),
RF-UNIT (9).
When the associated
SITE has a
Cabinet type of
Horizonmacro
or Horizonmacro
extension, the
option CTU (10)
can be selected.

Mandatory.

Diversity Flag
diversity_flag
(OMC-R
parameter
name:
diversityFlag)

The diversity flag for the DRI. If

BSS parameter diversityOpt is
restricted, must be set to 0.

No Diversity (0) 2
branch Diversity (1),
4 Branch diversity
(2).

Optional.

RDN Class

See description in Table 4-1.

Default is the device

class.

RDN Instance

DRI identifier, see description in

Table 3-1.

0 - 11.
Default is 0.

Mandatory.

Cell Type
fm_cell_type

The type of cell structure

supported at the BTS in which
this DRI resides.

0 - 4.
OMNI cell (0).20
degree cell (1).60
degree cell (2).
Shared Diversity
cell (3) Full
Diversity cell (4).

Mandatory.

NMC RDN
Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

DRIGroup. Click to display the
parent DRIGroup Detailed View.

Kit Number

See description in Table 9-3.

Field
Replacement
Unit (FRU)

See description in Table 9-3.

Serial Number

See description in Table 9-3.

Cabinet
Identifier
cabinet_id

Identifier of the cabinet in which

the DRI resides.

0 - 15.

Mandatory.

Associated
FRU Kit
Number

The kit number of the

RCU/DRCU.

0 - 15.

Optional.

Continued

68P02901W17-T

9-69
Jan 2010

DRI Detailed View fields

Table 9-17

Chapter 9: Configuring Devices and Functions

DRI Detailed View fields - Identification grouping (Continued)

Field name/BSS
parameter name

Values

Brief description

Mandatory or
Optional?

Associated
FRU Serial
Number

The serial number of the

RCU/DRCU.

0 - 15.

Optional.

Associated
FRU

The type of the RCU device.

Default is null.

Optional

DRI Density
(OMC-R
parameter
name:
dri_density)

Only applicable if the DRI

resides in one of the following
cabinet types: Horizon II mini,
Horizon II mini extension,
Horizon II macro, Horizon II
macro_ext, Horizonmacro, or
Horizonmacro_ext. Grayed-out
for all other cabinet types.
Double density can only be
selected for the cabinet types
listed above. If this field is to
set to 2, the user must specify a
value for assoc_dri_id. The DRI
must be locked before this field
can be changed from 1 to 2. The
DRI and the associated DRI must
be locked before this field can be
changed from 2 to 1.
If dri_density is set to 3,
assoc_dri_id becomes sensitive
and editable. The DRI must be
locked before this field can be
changed to 3. The value 3 is only
valid if:

1 or 2.
Single (1),
Double (2).
Capacity (3).
Default is 1.

Optional.

The configured DRI is in a

HII family cabinet (Horizon
II mini, Horizon II micro or
Horizon II macro including
ext cabs).

The master SITE cabinet

is a HII family cabinet
(Horizon II mini, Horizon II
micro or Horizon II macro).

CTU2D Capacity feature

(ctu2dcapOpt) is Enabled
at the BSS.

See Configuring Double density

DRIs on page 9-66 for further
details.
Double Density mode is not
supported simultaneously with
4 Branch Receive Diversity.
Continued
9-70

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 9-17

DRI Detailed View fields

DRI Detailed View fields - Identification grouping (Continued)

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Set the diversity_flag to 2 for

a Single Density Mode DRI
configured in a Horizon II macro
cabinet for 4 branch receive
diversity.
Continued

68P02901W17-T

9-71
Jan 2010

DRI Detailed View fields

Table 9-17

Chapter 9: Configuring Devices and Functions

DRI Detailed View fields - Identification grouping (Continued)

Field name/BSS
parameter name
RDN of
Associated DRI
(OMC-R
parameter
name:
assoc_dri_id)

Values

Brief description
The RDN number of the other
DRI which is autocreated to
provide double density. (The
other DRI is created in the same
DRIGroup.) Only applicable if:

The DRI resides in one

of the following cabinet
types: Horizon macro,
Horizon macro_ext,
Horizon II macro, Horizon
II macro_ext, Horizon II
mini, or Horizon II mini
extension. This field is
grayed-out for all other
cabinet types.

dri_density is set to Double

(2) or Capacity (3).
The associated DRI RDN
must:

Mandatory or
Optional?

0 - 11.

Optional.

Valid range 0 to 1
0 - Primary DRI
1 - Associated DRI

Optional

Be different than the

DRI to which it is
being associated.
Not be an existing DRI
id.
Otherwise an error message is
displayed when the details are
saved.
See Configuring Double density
DRIs on page 9-66 for further
details.
Transceiver
The transceiver_flag parameter
Flag
indicates DRI type for double
transceiver_flag density CTU-2, and double
density and capacity mode
CTU-2D.

9-72

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DRI Detailed View fields

Cage and Slot Information grouping

Table 9-18 describes the fields in the Cage and Slot Information grouping of the DRI Detailed
View.

Table 9-18 DRI Detailed View fields - Cage and Slot Information grouping
Field name

Brief description

Values

Mandatory or Optional?

Cage Identifier

See description in
Table 9-4.

Mandatory.

Slot Number

See description in
Table 9-4.

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this DRI. Where additional
notes are not required, close this field by clicking the toggle button next to the Additional
Information header.

State grouping
Table 9-19 describes the unique fields in the State Identification grouping of the DRI Detailed
View. For descriptions of the standard State Information fields, see Table 4-2.

Table 9-19 DRI Detailed View fields - Additional State Information grouping
Field name/OMC-R
parameter name
Related RTF
related_rtf
(OMC-R only
attribute)

Brief description

Values

The RTF which the

DRI is servicing.

Mandatory or Optional?
Optional.

Preferred RTF grouping

Table 9-20 describes the fields in the Preferred RTF grouping of the DRI Detailed View.

Table 9-20 DRI Detailed View fields - Preferred RTF grouping

Field name/OMC-R
parameter name

Brief description

Preferred RTF Group

Id
pref_rtf_group_id

The id for the

preferred RTF Group
for this DRI.

0 - 23.
Default is null.

Optional.

Preferred RTF Id
pref_rtf_id

The preferred RTF

function for this DRI.

0 - 11.
Default is null.

Optional.

68P02901W17-T

Values

Mandatory or Optional?

9-73
Jan 2010

DRI Detailed View fields

Chapter 9: Configuring Devices and Functions

DRI RCU grouping

Table 9-21 describes the fields in the DRI RCU grouping of the DRI Detailed View.

Table 9-21 DRI Detailed View fields - DRI RCU grouping

Field name/
parameter name
Topcell Radio Unit
Identifier
tru_id
(OMC-R parameter
name:
truId)

Values

Brief description
Indicates the Top Cell
Radio Unit. Only
valid when DRI_type
is DRIM, ACM.

Mandatory or Optional?

1 - 6.
Default is null.

Optional.

Combiner 1 grouping
Table 9-22 describes the fields in the Combiner 1 grouping of the DRI Detailed View.

Table 9-22

DRI Detailed View fields - Combiner 1 grouping

Field name/OMC-R
parameter name

Mandatory or
Optional?

Brief description

Values

Combining Type
combining_type

Determines if the DRI is using a remote

tuning combiner.
When set to None (0), Combiner
Identifier and Combiner Cavity
Identifier fields are grayed-out.
Grayed-out when the DRI is Double
density or Capacity. For a DRI equipped
in a Horizon II macro, Horizon II macro
extension, Horizon II mini, or Horizon
II mini extension cabinet, this field is
grayed-out. Also see Configuring a
COMB device on page 9-49.

0 - 2.
None (0),
Non-Controlling
(1),
Controlling (2).
Default is None
(0).

Optional.

Combiner
Identifier
combiner_1_id

The identifier for the first combiner

connected to the DRI. Can be entered
at creation time, but can also be
modified at a later date. Not valid for
M-Cellmicro sites. Grayed-out when the
DRI is Double density or Capacity.

0 - 13.

Optional.

Combiner Cavity
Identifier
cavity
(OMC-R
parameter name:
combiner_1_
cav_id)

Cavity in the first combiner that the

DRI is connected to. Can be entered at
creation time, but can also be modified
at a later date.

0 - 5.

Optional.

NOTE
For M-Cellmicro and Pico
sites, this attribute is set
to NULL and cannot be
changed by the operator.
Grayed-out when the DRI is
Double density or Capacity.

9-74

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DRI Detailed View fields

Shared Cells grouping

Table 9-23 describes the fields in the Shared Cells grouping of the DRI Detailed View.

Table 9-23 DRI Detailed View fields - Shared Cells grouping

Field name/BSS
parameter name
Cell 1 GSM
Cell Identifier
cell1_gsmCellId

Values

Brief description

Mandatory.

The GSM cell id for the first cell. The

MCC and MNC sub-fields can be edited
in Create mode. The MCC and MNC
sub-fields cannot be edited for n-1 or
n-2 BSS.

Cell 1 Antennae
The receiver antenna select number
Select
for the first shared cell. For a DRI
antenna_select
equipped in a Horizon II mini or
Horizon II mini extension cabinet, only
(OMC-R
values 1 or 2 apply.
parameter name:
cell1AntennaSelct)

Mandatory or
Optional?

1 - 3.

Optional.

Mobile Detection Thresholds grouping

Not currently used.

Port Connections grouping

Table 9-24 describes the fields in the Port Connections grouping of the DRI Detailed View.

Table 9-24 DRI Detailed View fields - Port Connections grouping

Field name/BSS
parameter name

Values

Brief description

Mandatory or
Optional?

Connection to BTP
tcu_connection
(OMC-R database
parameter name:
foxFmuxConn)

Indicates what type of

connection is used by a
M-Cell TCU. Also known as
the TCU connection.

0 - 4.
When the
associated SITE
has a Cabinet type
Horizonmacro or
Horizonmacro
extension,
displays Master
(0) rather than
Fox (0).
Does not include
the Direct option.

Optional.

Port Connection
tcu_port

Indicates the port connection

used by a TCU device. For
a DRI equipped in a Horizon
II mini or Horizon II mini
extension cabinet, only values
of 0 or 1 are allowed.
For a DRI equipped in a
Horizon II micro cabinet only
0 is allowed.

0 - 5.

Optional.

68P02901W17-T

9-75
Jan 2010

Other DRI configuration tasks

Chapter 9: Configuring Devices and Functions

Power Distribution Board grouping

Table 9-25 describes the fields in the Power Distribution Board grouping of the DRI Detailed
View.

Table 9-25 DRI Detailed View fields - Power Distribution Board grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

PDB FRU Kit Number

Kit number of the PDB

(Power Distribution Board) at
an M-Cellmicro site.

0 - 15.

Optional.

PDB FRU Serial

Number

The serial number of the PDB.

0 - 15.

Optional.

PDB Field
Replacement Unit
pdb_fr_unit

Indicates the type of the RCU

device.

Default is NULL if
the information is
not available.

Optional.

Other DRI configuration tasks

To modify, delete, display, or equip a DRI device using the TTY interface, see Methods of
configuring individual devices and functions on page 9-3.

9-76

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reassigning a DRI device

Reassigning a DRI device

Introduction to reassigning
Reassigning is moving control of a DRI from one GPROC to another using the reassign
command. Refer to: Technical Description: BSS Command Reference (68P02901W23) for
complete information on the reassign command. Reassigning devices is also described in
OMC-R Online Help, Network Operations.

Reassigning a Horizonmicro2 or Horizoncompact2 BTS

A DRI cannot be reassigned at a Horizonmicro2 or a Horizoncompact2 BTS. Whenever a
reassign cannot be executed, the Reassign option in the Navigation Tree and DRI Detailed
View is grayed-out.

Reassigning a DRI using the OMC-R GUI

To reassign a DRI using the OMC-R GUI Navigation Tree, follow these steps:

Procedure 9-18 Reassign a DRI

68P02901W17-T

Navigate to the required DRI instance in the Navigation Tree (BSS BSS instance - SITE - SITE instance - Radio Frequency - DRIGROUP DRIGROUP instance - DRI - DRI instance). If necessary, see Navigating
to a network object class or instance on page 1-28 for further details.

Select Fault Mgt - Reassign from the Navigation Tree menu bar. A
Reassign box is displayed listing all DHP, and BTP in the same cage as
the DRI device (see Figure 9-14). The list box shows the operational
state and administrative state for each device.

Select a device in the window and click the Reassign button. A

confirmation dialogue box is displayed with the following message: Do
you wish to reassign <device1> from <device2> to <device3>
at <SITE>?

Click OK.

9-77
Jan 2010

Reassigning a DRI using the TTY interface

Chapter 9: Configuring Devices and Functions

Figure 9-14 DRI Reassign box

ti-GSM-DRIReassignbox-00821-ai-sw

Reassigning a DRI using the TTY interface

To move control of a DRI from one GPROC to another using the TTY interface, follow these steps:

Procedure 9-19 Move control of a DRI

1

Remote login to the BSS and change to security level 2, see Remotely
logging in to a BSS site from the OMC-R on page 1-39 and Changing
security level (for TTY interface commands) on page 1-43, respectively.

Enter the command:

reassign <location> <child_dev_name> <child_dev_id>
<child_dev_id_2> <child_dev_id_3> [<to>]
<parent_dev_funct_name> <parent_dev_id_1> <parent_dev_id_2>
<parent_dev_id_3>
For example, to reassign DRI 0 2 0 from its current GPROC at BTS 4 to
DHP 4 2 0 use the following command:
reassign 4 DRI 0 2 0 DHP 4 2 0
Refer to: Technical Description: BSS Command Reference
(68P02901W23) for a compete description of the commands and
parameters.

9-78

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Remotely calibrating DRIs

Remotely calibrating DRIs

Introduction to the Remote Bay Level Calibration facility

The Remote Bay Level Calibration facility allows a user to remotely calibrate DRIs contained
at a site (that is, a BTS only) from the OMC-R GUI. DRIs can still be calibrated on-site
by an installation engineer visiting the site. For further information, see Installation and
Configuration: BSS Optimization (68P02901W43).
The OMC-R has a database of known calibration values. Values exist for all known BTS product
ranges (such as InCell, M-Cell, Horizonmacro, Horizon II macro, and so on). When a radio is
inserted or reconfigured by an installation engineer on-site, an operator at the OMC-R can use
the OMC-R GUI interface to select or define the standard configuration to be used, and then
select all or some of the radios within the site for calibration. The OMC-R then transfers the
calibration values for the specified site configuration to the BSC database where they are
used by the selected BTS. The next time the DRI is brought in-service, it is calibrated with the
values in the BSC database.

NOTE
The Remote Bay Level Calibration facility only propagates the information to the BSC.
The Preserve Transceiver Calibration feature (controlled by store_cal_data) must be
enabled to propagate the information to the BTS. See Installation and Configuration:
BSS Optimization (68P02901W43) and Technical Description: BSS Implementation
(68P02901W36) for further details.

NOTE
This facility is not a true calibration activity. Instead, the values that are downloaded
to the BTS from the BSC are average values that have been determined by Motorola
by analyzing test results from factory production test procedures. The result is that
expected calibration errors should be evened out across the network.

Enabling the Preserve Transceiver Calibration feature at the

OMC-R
Before starting the preserve calibration procedure, consult the site specific documentation to
determine the BSC/BTS and cage slot allocation.

68P02901W17-T

9-79
Jan 2010

Standard configurations used for a calibration

Chapter 9: Configuring Devices and Functions

Proceed as follows:

Procedure 9-20 Enable the Preserve Transceiver Calibration feature

1

Remotely log in to the required base site controller (BSC).

To enable the Preserve Transceiver Calibration feature type:

store_cal_data <site_id>
Result: All calibration data will be stored in the master CM database
at the BSC, which is then used to update the CM database copy at
the BTS only if the data is valid.

Standard configurations used for a calibration

A standard configuration is created which is used to calibrate DRIs at a site. This configuration
can be saved and used as a template to calibrate other DRIs. A user can create, edit, or delete
standard configurations. The user can create a maximum of 100 standard configurations.
The last standard configuration used to calibrate the site is shown in the Configuration used on
last Calibrate field in the SITE Detailed View.

Calibration restrictions

NOTE
The calibration function is not available for all cabinets types.
The calibrate function is not available when:

The parent of the BSC or site is an RXCDR.

Where a site has been specified with a specific cabinet type. The equivalent values for
the cabinet_type parameter can be found in the Technical Description: BSS Command
Reference (68P02901W23) manual.

A site contains a cell where the frequency_type is set to 8 (PCS1900).

OMC-R calibration checks

When a calibration is initiated, the OMC-R makes the following checks before performing
the calibration:

For every cabinet under the site:

That there is a cabinet under the Standard Configuration with a matching rdnInstance.
If the cabinet_type of the site is 0,1,4,6,7,8 or 9 (that is, InCell), there is a
corresponding cabinet_type under the standard configuration with the same cabinet
types.

9-80

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Enabling the bay level calibration facility

If the cabinet_type of the site is 10 or 12 (that is, M-Cell 2), there is a

correspondingcabinet_type under the standard configuration with the same type.
If the cabinet_type of the site is 11 or 13 (that is, M-Cell 6), there is a
correspondingcabinet_type under the standard configuration with the same type.
If the cabinet_type of the site is 18 or 19 (that is, Horizon macro), there is a
corresponding cabinet_type under the standard configuration with the same types.
If the cabinet_type of the site is 24 or 25 (that is, Horizon macro), there is a
corresponding cabinet_type under the standard configuration with the same types.

For every DRI under the site:

That there is a DRI under the Standard Configuration with a matching DRIGroup
rdnInstance and DRI rdnInstance.
If the frequency_type of the associated cell is 1 or 2 (that is 900 MHz) that the
corresponding DRI under the Standard Configuration also has a frequency_type
of 900 MHz.
If the frequency_type of the associated cell is 4 (that is 1800 MHz) that the
corresponding DRI under the Standard Configuration also has a frequency_type
of 1800 MHz.
If any check fails, the OMC-R displays an error message and the calibration is not
performed.

Enabling the bay level calibration facility

To enable or disable the bay level calibration facility, use the environmental variable
BAY_LEV_CAL. By default, BAY_LEV_CAL is set to FALSE.
When the BAY_LEV_CAL environmental variable is set to FALSE, the Calibrate option is not
displayed in the menu bars, and the related calibration fields are not displayed in the site
Detailed View form.

Enabling on a per user basis

To enable bay level calibration, enter the following command at the GUI> prompt (which is
displayed in the window from which the OMC-R GUI is launched):
setenv BAY_LEV_CAL TRUE

NOTE
If an ampersand (and) sign is used after the command to launch the OMC-R GUI, the
GUI> prompt is not displayed.
If BAY_LEV_CAL is changed, close and reopen the OMC GUI for the changes to take effect.

68P02901W17-T

9-81
Jan 2010

Bay level calibration parameters

Chapter 9: Configuring Devices and Functions

Enabling for any user starting GUI from the CDE

To enable bay level calibration for any user starting the GUI from the CDE, follow these steps on
the SPLAT and on the MMI server:

Procedure 9-21 Enable bay level calibration

1

Add the following lines to /usr/omc/config/global/env/Common.sh:

BAY_LEV_CAL = TRUE
export BAY_LEV_CAL

Add the following line to /usr/omc/config/global/env/Common.csh:

setenv BAY_LEV_CAL TRUE

Bay level calibration parameters

Table 9-26 lists the parameters relating to bay level calibration.

Table 9-26 Bay level calibration parameters

OMC-R GUI field
name

BSS parameter name

Description

Calibrate Enabled

Calibrate_flag

Displayed in the SITE Detailed View.

Determines whether the site can be remotely
calibrated. If set to No (0) (default), when
the user selects the calibrate function from
the menu bar, the OMC-R displays a message
in the status bar to indicate that this flag
needs to be set to Yes (1) in the site Detailed
View form. If set to Yes, the site can be
remotely calibrated.

Configuration
used on last
Calibrate

Config_type_on_
last_cal

Displayed in the SITE Detailed View.

Displays the name of the last Standard
Configuration used to calibrate the DRIs at
the site.

(not visible in the

OMC-R GUI)

rx_cal_data_a
rx_cal_data_b

Used to set default bay level calibration

offset values for each DRI receive path. Valid
values: 1 - 94.

Enabling a site to be remotely calibrated

Restrictions for calibration
Calibration at a site cannot be enabled if:

9-82

The site is BSC.

The parent of the site is an RXCDR.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Remote DRI calibration procedures

Also see the restrictions listed in Calibration restrictions earlier in this section.

Setting the Calibrate Enabled field

The DRIs at a site can only be remotely calibrated, if calibration for the site has been enabled.
To enable remote calibration at a site, set the Calibrate Enabled field in the site Detailed View
form to Yes (1).

NOTE
The Calibrate Enabled field in the SITE Detailed View is only displayed if the bay
level calibration facility has been enabled, see Enabling the bay level calibration
facility.

Remote DRI calibration procedures

These DRI calibration related procedures are detailed in the following sections:

Creating a standard configuration for DRI calibration on page 9-84

Remotely calibrating DRIs from the OMC-R on page 9-93

Managing existing standard configurations on page 9-99

68P02901W17-T

9-83
Jan 2010

Creating a standard configuration for DRI calibration

Chapter 9: Configuring Devices and Functions

Creating a standard configuration for DRI calibration

Introduction to DRI calibration

Before a site can be calibrated remotely, one or more standard configurations must exist. A
standard configuration determines the default values that are used to calibrate one or more
DRIs at a site.
A user can create a standard configuration using the OMC-R GUI.
Up to 100 standard configurations can be created.

Prerequisites to DRI calibrations

Before a standard configuration can be created:

Bay Level Calibration facility must be enabled, see Remotely calibrating DRIs on page 9-79.

Remote calibration at the site must be allowed, Remotely calibrating DRIs on page 9-79.

At least one DRI must exist for the site.

A Master Cabinet (rdnInstance 0) must exist for the site.

Creating a standard configuration

To create a standard configuration, follow these steps:

Procedure 9-22 Create a standard configuration

1

Navigate to the site to be calibrated using the Navigation Tree. If

necessary, see Navigating to a network object class or instance on
page 1-28 for further details.

Select the site instance to be calibrated. The color of the site changes.

Select Options - Calibrate from the menu bar. Alternatively, select

Options - Calibrate from the menu bar of the site Detailed View or
Map window.
Result: After a few moments, the OMC-R opens the Calibrate site
form as shown in Figure 9-15. By default, the site name is shown in
the site field, and cabinet type of the master cabinet is shown in the
Master Cabinet field (for example, M-Cell2).
Continued

9-84

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating a standard configuration

Procedure 9-22 Create a standard configuration (Continued)

4

Click the All DRIs button in the Calibrate DRI(s) section of the form
shown in Figure 9-15, if not already selected. This must be selected
when a standard configuration is being created. Later, when a standard
configuration is being applied, a subset of DRIs can be selected.

Click the New button in the Standard Configuration section of the

Calibrate site form.
Result: The OMC-R displays the New Standard Configuration form
as shown in Figure 9-16. By default, the form shows cabinet and
associated DRI details for the first cabinet (Cabinet 0). For each DRI
within the selected cabinet, the form shows the following information:

Slot number.

Frequency.

Receiver A (RX A).

Receiver B (RX B).

The Slot No. fields display the following information:

DRI with rdnInstance 0 to 5, defaults to Slot 0 to Slot 5,

respectively.

DRI with rdnInstance 6, defaults to Slot 0.

DRI with rdnInstance 7, defaults to Slot 1, and so on.

DRI with rdnInstance 11, defaults to Slot 5.

Click the Cabinet tab for which you want to specify details.

Enter the name to be given to the new Standard Configuration in the

Name field. Enter a maximum of 30 characters. This is a mandatory
field.

Click the Cabinet Class button to display a dropdown list of menu

options, and select a cabinet class. By default, this field displays the
following options:

Cabinet with rdnInstance 0, defaults to Master.

Cabinet with rdnInstance 1, defaults to Extender1.

Cabinet with rdnInstance 2, defaults to Extender2.

Cabinet with rdnInstance 3, defaults to Extender3.

Cabinet with rdnInstance greater than 3, defaults to Extender3.

Click the DRI <no> Slot No. button to display a dropdown list of
slot numbers in the range 0 - 5, and select the required slot number
for this DRI.
Continued

68P02901W17-T

9-85
Jan 2010

Creating a standard configuration

Chapter 9: Configuring Devices and Functions

Procedure 9-22 Create a standard configuration (Continued)

10

Click the Rx A button to display a dropdown menu of receive path

options, and select the required option. By default, the first option is
displayed. The OMC-R displays only valid receive path options for the
selected cabinet type and DRI frequency, see Table 9-27.

11

Click the Rx B button to display a dropdown menu of receive path

options, and select the required option. See Table 9-27.

12

Repeat steps 9 to 11 to configure each DRI required.

13

Repeat steps 6 to 12 to configure each cabinet required.

14

Click the Save button to save the new Standard Configuration under
the specified name.
Result: The OMC-R displays the Calibrate Site form. If the name of
the Standard Configuration already exists, the OMC-R displays an
error message.
Alternatively, to cancel the configuration, click Close.

9-86

15

To calibrate the selected site go to step 1 of the procedure Remotely

calibrating DRIs from the OMC-R on page 9-93.

16

To exit, click Close.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Figure 9-15

Creating a standard configuration

Calibrate Site form

ti-GSM-CalibrateSiteform-00822-ai-sw

68P02901W17-T

9-87
Jan 2010

Rx A and Rx B receive path options

Chapter 9: Configuring Devices and Functions

Figure 9-16 New Standard Configuration form

ti-GSM-NewStandardConfigurationform-00823-ai-sw

Rx A and Rx B receive path options

Table 9-27 shows the receive path options the OMC-R displays for each cabinet type in the Rx A
and Rx B fields in the New Standard Configuration form (see Figure 9-16). Where:

9-88

cabinet_type is the cabinet type of the current cabinet.

Cabinet-0: cabinet_type is the cabinet_type of the master cabinet (Cab 0).

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Rx A and Rx B receive path options

Table 9-27 Rx A and Rx B receive path options

Cabinet type

Receive path options displayed

If...

InCell900 MHz

cabinet_type =
0,1,4,6,7,8 or 9 and
frequency_type
= 900 MHz

Local DPP

InCell1800 MHz

cabinet_type =
0,1,4,6,7,8 or 9 and
frequency_type
= 1800 MHz

Local
Local
Local
Local
Local
Local
Local
Local
Local

M-Cell2 900 MHz

cabinet_type = 10 or 12
and
frequency_type
= 900 MHz

Local DLNB
Local DLNB + Local MPD

M-Cell2 1800 MHz

cabinet_type = 10 or 12
and
frequency_type
= 1800 MHz

Local
Local
Local
Local
Local
Local
Local
Local
Local

M-Cell6 900 MHz

cabinet_type = 11 or 13
and Cabinet-0::
cabinet_type
= 11 or 13 and
frequency_type
= 900 MHz

Local DLNB
Local DLNB +
Local MPD
Remote DLNB
Remote DLNB
+ Remote MPD
Local DLNB
+ Remote MPD
Remote DLNB (3m) +
Local MPD (3m)
Local DLNB +
Remote MPD (3m)

LNA fixed gain

LNA switched low
LNA switched high
LNA fixed gain +
MPD
LNA switched low +
MPD
LNA switched high +
MPD

LNA fixed gain

LNA switched low
LNA switched high
LNA fixed gain +
MPD
LNA switched low +
MPD
LNA switched high +
MPD

Continued

68P02901W17-T

9-89
Jan 2010

Rx A and Rx B receive path options

Chapter 9: Configuring Devices and Functions

Table 9-27 Rx A and Rx B receive path options (Continued)

Cabinet type

If...

M-Cell6 1800 MHz

cabinet_type = 11 or 13
and Cabinet-0::
cabinet_type
= 11 or 13 and
frequency_type
= 1800 MHz

Horizon 900 MHz

Horizon 1800 MHz

Horizon II 900
MHz

cabinet_type = 18 or 19
and Cabinet-0::
cabinet_type
= 18 or 19 and
frequency_type
= 900 MHz

cabinet_type = 18 or 19
and Cabinet-0::
cabinet_type
= 18 or 19and
frequency_type
= 1800 MHz

cabinet_type = 24 or
25and Cabinet-0::
cabinet_gen
= 24 or 25 and
frequency_type
= 900 MHz

Receive path options displayed

Local LNA fixed gain
Local LNA switched low
Local LNA switched high
Local LNA fixed gain +
Local MPD
Local LNA switched low +
Local MPD
Local LNA switched high +
Local MPD
Remote LNA switched high
Local LNA fixed gain
Remote LNA switched high
Local LNA switched low
Remote LNA switched high
Local LNA fixed gain +
Remote MPD
Remote LNA switched high
Local LNA switched low +
Remote MPD
Local SURF
Local SURF +
Local SURF +
Local SURF +
Remote SURF
Local SURF
Remote SURF
Local SURF
Remote SURF
Local SURF
Remote SURF
Local SURF
Local SURF
Local SURF +
Local SURF +
Local SURF +
Remote SURF
Local SURF
Remote SURF
Local SURF
Remote SURF
Local SURF
Remote SURF
Local SURF

+
+
+

TDF
DCF
DDF
+
+ TDF +
+ DCF +
+ DDF +

TDF
DCF
DDF
+
+ TDF +
+ DCF +
+ DDF +

Local SURF2
Local SURF2 + DUP
Remote SURF2 +
Local SURF2
Remote SURF2 + DUP +
Local SURF2
Continued

9-90

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Rx A and Rx B receive path options

Table 9-27 Rx A and Rx B receive path options (Continued)

Cabinet type

If...

Receive path options displayed

Horizon II 1800
MHz

cabinet_type = 24 or 25
and Cabinet-0::
cabinet_gen
= 24 or 25 and
frequency_type
= 1800 MHz

Local SURF2
Local SURF2 + DUP
Remote SURF2 +
Local SURF2
Remote SURF2 + DUP +
Local SURF2

M-Cell6/
Horizon
Interoperability
900 MHz

cabinet_type = 18 or 19
and Cabinet-0::
cabinet_type
= 11 or 13 and
frequency_type
= 900 MHz OR
cabinet_type
= 11 or 13 and Cabinet-0::
cabinet_type
= 18 or 19 and
frequency_type
= 1800 MHz

Local SURF + Remote DLNB

Local SURF + Remote DLNB + Remote
MPD
Remote SURF (TCU in M-Cell6 Cabinet)
Remote SURF + TDF (TCU in M-Cell6
Cabinet)
Remote SURF + DCF (TCU in M-Cell6
Cabinet)
Remote SURF + DDF (TCU in M-Cell6
Cabinet)

M-Cell6/
Horizon
Interoperability
1800 MHz

cabinet_type
= 18 or 19 and Cabinet-0::
cabinet_type
= 11 or 13
frequency_type
= 1800 MHz OR
cabinet_type
= 11 or 13 and Cabinet-0::
cabinet_type
= 18 or 19 and
frequency_type
= 1800 MHz

Remote LNA fixed gain +

Local SURF
Remote LNA switched low +
Local SURF
Remote LNA fixed gain +
Remote MPD + Local SURF
Remote LNA switched low + Remote MPD +
Local SURF
Remote SURF + Local LNA fixed gain (TCU
in M-Cell6 Cabinet)
Remote SURF + Local LNA switched low
(TCU in M-Cell6 Cabinet)
Remote SURF + TDF +
Local LNA fixed gain (TCU in M-Cell6
Cabinet)
Remote SURF + DCF+
Local LNA fixed gain (TCU in M-Cell6
Cabinet)
Remote SURF + DDF+ Local LNA fixed gain
(TCU in M-Cell6 Cabinet)
Remote SURF + TDF+ Local LNA switched
low (TCU in M-Cell6 Cabinet)
Remote SURF + DCF+ Local LNA switched
low (TCU in M-Cell6 Cabinet)
Remote SURF + DDF+ Local LNA switched
low (TCU in M-Cell6 Cabinet)
Remote LNA switched high + attenuator +
Local SURF
Remote LNA switched high +
Remote MPD + attenuator +
Local SURF
Continued

68P02901W17-T

9-91
Jan 2010

Rx A and Rx B receive path options

Chapter 9: Configuring Devices and Functions

Table 9-27 Rx A and Rx B receive path options (Continued)

Cabinet type

9-92

If...

Receive path options displayed

M-Cell6/
Horizon II
Interoperability
900 MHz

cabinet_type = 24 or 25
and Cabinet-0::
cabinet_type
= 11 or 13 and
frequency_type
= 900 MHz

Local SURF2 + Remote DLNB

Local SURF2 + Remote DLNB +
Remote MPD
Remote SURF2 (TCU2 in M-Cell6 Cabinet)
Remote SURF2 + DUP (TCU2 in M-Cell6
Cabinet)

M-Cell6/
Horizon II
Interoperability
1800 MHz

cabinet_type = 24 or 25
and Cabinet-0::
cabinet_type
= 11 or 13 and
frequency_type
= 1800 MHz

Remote LNA fixed gain +

Local SURF2
Remote LNA switched low +
Local SURF2
Remote LNA fixed gain +
Remote MPD + Local SURF2
Remote LNA switched low +
Remote MPD + Local SURF2
Remote SURF2 + Local LNA fixed gain
(TCU2 in M-Cell6 Cabinet)
Remote SURF2 + Local LNA switched low
(TCU2 in M-Cell6 Cabinet)
Remote SURF2 + DUP + Local LNA fixed
gain (TCU2 in M-Cell6 Cabinet)
Remote SURF2 + DUP +
Local LNA switched low (TCU2 in M-Cell6
Cabinet)
Remote LNA switched high +
attenuator + Local SURF2
Remote LNA switched high +
Remote MPD + attenuator +
Local SURF2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Remotely calibrating DRIs from the OMC-R

Remotely calibrating DRIs from the OMC-R

Prerequisites for remotely calibrating DRIs

Before DRIs at a site can be calibrated remotely using the OMC-R GUI:

Bay Level Calibration facility must be enabled, see Remotely calibrating DRIs on page 9-79.

Remote calibration at the site must be allowed, Remotely calibrating DRIs on page 9-79.

A standard configuration must exist. To create a standard configuration, see Creating a

standard configuration for DRI calibration on page 9-84.

Calibrating DRIs from the OMC-R

To calibrate DRIs at a site from the OMC-R using the OMC-R GUI, follow these steps:

Procedure 9-23 Calibrate DRIs at a site

1

Navigate to the site to be calibrated using the Navigation Tree. If

necessary, see Navigating to a network object class or instance on
page 1-28 for further details.

Select the site instance to be calibrated. The color of the site changes.

Select Options - Calibrate from the menu bar. Alternatively, select

Options - Calibrate from the menu bar of the site Detailed View or
Map window.
Result: By default, the site name is shown in the site field, and cabinet
type of the master cabinet is shown in the Master Cabinet field (for
example, M-Cell2). The OMC-R opens the Calibrate site form as shown
in Figure 9-15.

Selecting a standard configuration

To select a standard configuration, select a name from the list of Standard Configurations in the
central pane of the form. The OMC-R highlights the name. Use the scroll bar in the pane to
scroll the list up and down.
If a standard configuration does not exist, or if you want to create a standard configuration, see
Creating a standard configuration for DRI calibration on page 9-84 for further details.
To edit an existing standard configuration, see Managing existing standard configurations on
page 9-99.
To delete an existing standard configuration, see Managing existing standard configurations on
page 9-99.

68P02901W17-T

9-93
Jan 2010

Calibrating DRIs from the OMC-R

Chapter 9: Configuring Devices and Functions

Otherwise, repeat the action.

Selecting all or some DRIs for calibration

To select which DRI(s) are to be calibrated, follow these steps:

Procedure 9-24 Select all or some DRIs for calibration

1

Click the All DRIs bullet button in the Calibrate DRI(s) section to
calibrate all DRIs at the selected site, then proceed to step 1 of
Initiating the calibration.
Alternatively, click the Sub-set of DRI(s) bullet button to manually pick
the DRIs to be calibrated, then go to the next step.

Click the Select button. The Select button is available only when the
Sub-set of DRIs button has been selected. The OMC-R displays the
Select DRI(s) form as shown in Figure 9-17.
Result: The Select DRI(s) form shows the site name and the cabinet
type of the master cabinet. In the main section of the form are two
panes. The left-hand pane labeled DRI(s) to Calibrate is empty by
default. The right pane has no label and displays a list of all the DRIs
in the selected site.

Select the name of a DRI you want to calibrate from the list of DRIs
shown in the right pane. The OMC-R highlights the DRI name.

Click the <Add button. The DRI name highlighted is moved from the
right pane to the DRI(s) to Calibrate pane.
Alternatively, double-clicking the DRI name, moves the names directly
to the left pane without having to use the <Add button.
If moving the wrong DRI name, select the name in the left pane and
click the Remove>. The OMC-R moves the DRI name back to the
right pane.

Repeat steps 3 and 4 until all the required DRIs to be calibrated are
moved to the DRI(s) to Calibrate pane.

Click OK at the bottom of the screen to calibrate all the DRIs displayed
in the DRI(s) to Calibrate pane.
Result: The OMC-R displays the Calibrate site form. Selections are
shown in the Selected Configuration to Apply to NE field, for example
Sub-set of DRI(s) - <standard configuration name>.

9-94

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Figure 9-17

Calibrating DRIs from the OMC-R

Select DRI(s) form

ti-GSM-SelectDRI_s_form-00824-ai-sw

Viewing and revising the calibration selections

To check or revise selections:

Procedure 9-25 View and revise DRI calibration selections

1

Click the Preview/Revise button.

Result: The OMC-R makes the OMC-R checks listed in Remotely
calibrating DRIs on page 9-79. If the checks fail, the OMC-R
displays an error message in the status bar.If the checks pass, the
OMC-R displays the Preview/Revise Calibration Values form which
contains the same fields as the New Standard Configuration form
shown in Figure 9-16.
Continued

68P02901W17-T

9-95
Jan 2010

Calibrating DRIs from the OMC-R

Chapter 9: Configuring Devices and Functions

Procedure 9-25 View and revise DRI calibration selections (Continued)

2

Revise the calibration fields as required. See Creating a standard

configuration for DRI calibration on page 9-84 for field details.

NOTE
A revised standard configuration cannot be saved, because
it is intended to be used for one-off changes only.
3

Click OK to use changes, or Cancel to cancel without changing

anything.

Initiating the calibration

To start the calibration, follow these steps:

Procedure 9-26 Initiate a DRI calibration

1

Click Apply to NE button at the bottom of the form.

Result: The OMC-R makes the checks listed in Remotely calibrating
DRIs on page 9-79 before it begins the calibration. If the checks fail,
the OMC-R displays an appropriate warning or error message in the
status bar. If the checks pass, the OMC-R:

Sends the calibration values to the BSC database as multiple set

operations of the rx_cal_data_a and rx_cal_data_b attributes
on the DRI class for any selected DRIs.

Displays the following warning message: The selected DRI(s)

will not be calibrated until a lock and unlock is
performed.

Click OK to acknowledge the warning message.

Result: The OMC-R displays the Calibration data set at BSS form as
shown in Figure 9-18. For each DRI the Calibration data set at BSS
form shows whether the calibration was a Success or Failed. Success
means that the default calibration values have been set in the BSC
database. Failed means that the download of the calibration values to
the BSC was unsuccessful.

9-96

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Calibrating DRIs from the OMC-R

Figure 9-18 Calibration data set at BSS form

ti-GSM-CalibrationdatasetatBSSform-00825-ai-sw

Saving the calibration results to a file

To save the calibration results to an ASCII file, follow these steps:

Procedure 9-27 Save DRI calibration results

1

Click Save at the bottom of the Calibration data set at BSS form. The
OMC-R displays a Save As dialogue box.

Type the file name and select the directory name where the results
are to be stored.

Click Save to save the data to the file.

Result: The OMC-R also updates the field: Configuration used in last
Calibrate' in the SITE Detailed View form (see Table 7-5) with the name
of the Standard Configuration used to calibrate the site.

68P02901W17-T

Click Close to exit the Calibrate site form.

9-97
Jan 2010

Calibrating DRIs from the OMC-R

Chapter 9: Configuring Devices and Functions

Resetting the calibrated DRI

Lock and unlock the DRIs so that the default offset values can take effect at the BTS. See OMC-R
Online Help, Network Operations for further details of fault management activities.

NOTE
The Remote Bay Level Calibration facility only propagates the information to the BSC.
The Preserve Transceiver Calibration feature (controlled by store_cal_data) must be
enabled to propagate the information to the BTS. See Installation and Configuration:
BSS Optimization (68P02901W43) and Technical Description: BSS Implementation
(68P02901W36) for further details.

9-98

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Managing existing standard configurations

Managing existing standard configurations

Viewing and editing an existing standard configuration

To view or edit a standard configuration, follow these steps:

Procedure 9-28 View or edit an existing standard calibration

1

Navigate to the SITE to be calibrated using the Navigation Tree. If

necessary, see Navigating to a network object class or instance on
page 1-28 for further details.

Select the SITE instance to be calibrated. The color of the SITE

changes.

Select Options - Calibrate from the menu bar. Alternatively, select

Options - Calibrate from the menu bar of the SITE Detailed View or
Map window.
Result: By default, the site name is shown in the site field, and cabinet
type of the master cabinet is shown in the Master Cabinet field. The
OMC-R opens the Calibrate Site form as shown in Figure 9-15.

Select the name of the standard configuration to be edited from the list
of Standard Configurations in the central pane of the form.
Result: The OMC-R highlights the name. Use the scroll bar in the
pane to scroll the list up and down.

Click the All DRIs button in the Calibrate DRI(s) section of the form, if
not already selected. Select this button when a standard configuration
is being viewed or modified. When a standard configuration is being
applied, a subset of DRIs can be selected.

Click the Edit button in the Standard Configuration section of the

Calibrate Site form.
Result: The OMC-R displays the Edit Standard Configuration form,
which contains the same fields as the New Standard Configuration
form. The name of the standard configuration is displayed in the Name
field and the details for the first cabinet and its DRIs are displayed.
The Slot No. field displays the saved slot number.

68P02901W17-T

Revise the calibration fields as required. See Creating a standard

configuration for DRI calibration on page 9-84 for field details.

Click the Save button to save your changes and overwrite the previous
version of the file, or Close to cancel without making any changes.

Click Close to exit the Calibrate site form.

9-99
Jan 2010

Deleting a standard configuration

Chapter 9: Configuring Devices and Functions

Deleting a standard configuration

To delete a standard configuration, follow these steps:

Procedure 9-29 Delete a standard configuration

1

Navigate to the SITE to be calibrated. If necessary, see Navigating to a

network object class or instance on page 1-28 for further details.

Select the site instance to be calibrated using the Navigation Tree.

Result: The color of the site changes.

Select Options - Calibrate from the menu bar. Alternatively, select

Options - Calibrate from the menu bar of the SITE Detailed View or
Map window.
Result: By default, the site name is shown in the site field, and cabinet
type of the master cabinet is shown in the Master Cabinet field. The
OMC-R opens the Calibrate Site form as shown in Figure 9-15.

Select the name of the Standard Configuration you want to delete from
the list in the central pane.
Result: The OMC-R highlights the name. Use the scroll bar in the
pane to scroll the list up and down.

Click the Delete button in the Standard Configuration section of the

Calibrate Site form.
Result: The OMC-R displays a Confirmation box.

9-100

Click OK to confirm the deletion. To cancel the deletion, click Cancel

and then reselect the correct Standard Configuration name.

Click Close to exit the Calibrate site form.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring an EAS device

Configuring an EAS device

Definition of EAS device

An External Alarm System (EAS) allows the definition of external alarms at InCell, M-Cell, and
Horizon sites. The alarm text issued when the alarm condition is met is taken from the EAS
alarm table. A user can define the text strings for each alarm index in the EAS alarm table.
One or two EAS devices can be configured per cabinet. There is a maximum of eight at a InCell
site, and a maximum of 16 at an M-Cell or Horizon site. The EAS function supports up to eight
optocouplers for In-Cell sites, and up to sixteen optocouplers for M-Cell and Horizon sites. These
are used to detect external alarms at a site, for example, temperature and smoke detectors.
The Parallel I/O Extender (PIX) board is the hardware device that provides the EAS (External
Alarm System) function.

EAS configuration procedures: overview

To configure an EAS when logged in to the BSS, follow these steps:

Procedure 9-30 Configure an EAS

1

If required, customize alarm text and severity levels for entries in

the EAS alarm table. The text and severity level are reported to the
OMC-R. This table is common to the BSC/BSS and its associated BTSs,
and specific for an RXCDR. See Defining EAS alarms in the alarm table
using the TTY interface on page 9-103 for further details.
Alternatively, and if required, modify the alarm text and severity level
for individual EAS alarm table entries. See Changing EAS alarms in the
alarms table using the TTY interface on page 9-104 for further details.

Create one or more EAS devices at the BSC/BSS, BTS, and RXCDR
sites.

Define which alarm conditions are to be reported.

Define the no alarm state for each of the optocouplers.

Assign an alarm index number to each alarm condition.

Define the relay wiring state. Use the following:

OMC-R GUI Navigation Tree, see Creating an EAS device
using the OMC-R GUI on page 9-106.
TTY interface, see Configuring an EAS using the TTY
interface on page 9-111 and Configuring the EAS physical
relay states using the TTY interface on page 9-112.

Alarms can be subscribed to when the EAS is functional.

68P02901W17-T

9-101
Jan 2010

User-definable EAS BSC/BSS and BTS alarm strings

Chapter 9: Configuring Devices and Functions

User-definable EAS BSC/BSS and BTS alarm strings

Introduction to user-definable alarm strings

Up to 34 alarm strings and severity levels can be defined for the BSC/BSS and associated BTSs
using the chg_eas_alarm command.
The alarm strings and severity levels are maintained in the EAS alarm table and are reported
to the OMC-R. Each optocoupler input at the different sites can be associated with any one of
these table entries.

Rules for defining EAS alarms

There are some basic rules to consider when working with user-defined EAS alarms at the BSS:

Each of the 34 EAS alarm table entries consist of an alarm string and a severity level.

Each alarm string can be up to 24 characters long.

Alarm strings and severity levels are required for each EAS alarm table index number.

When the table is modified, the BSC/BSS and all associated BTSs are affected.

Alarm severity levels

Table 9-28 shows the alarm severity level definitions.

Table 9-28

Severity level definitions

Severity level

Description

Investigate (not appropriate for EAS).

Critical.

Major.

Minor.

Warning.

EAS alarm strings

Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the chg_eas_alarm command and the alarm strings in the default EAS alarm
table.

9-102

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Defining EAS alarms in the alarm table using the TTY interface

Defining EAS alarms in the alarm table using the TTY

interface

Using chg_eas_alarm command

Use the chg_eas_alarm command to define all EAS alarm strings and severity levels. This data
is maintained in the EAS alarm table (see the Technical Description: BSS Command Reference
(68P02901W23) manual) at the BSC or RXCDR, and is used for the BSC/BSS and associated
BTSs or RXCDR.
Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the chg_eas_alarm command.

Defining EAS alarms using the TTY interface

To define EAS alarm strings and severity levels follow these steps:

Procedure 9-31 Define EAS alarm strings and severity levels

1

Enter the following command:

chg_eas_alarm <alarm_table_index> <alarm_severity_level>
<new_alarm_string>

Repeat step 1 for each of the alarm table entries.

Example
In the following example, severity level 4 is selected and Door 2 Alarm is defined as the alarm
string for table entry 1: -> chg_eas_alarm 1 4 Door 2 Alarm

68P02901W17-T

9-103
Jan 2010

Changing EAS alarms in the alarms table using the TTY interface

Chapter 9: Configuring Devices and Functions

Changing EAS alarms in the alarms table using the TTY

interface

Using the chg_eas_alarm command

Use the chg_eas_alarm command to change EAS alarm strings and severity levels.
Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the chg_eas_alarm, disp_element and chg_element commands and the
eas_alarm and eas_severity database parameters.

Displaying parameters
It is helpful to execute the disp_equipment command before changing the EAS parameters to
display all parameters associated with the EAS device. Refer to the Configuring an EAS using
the TTY interface on page 9-111 for more information.

Changing EAS alarm strings and security levels using the TTY
interface
To change EAS alarm strings and severity levels follow these steps:

Procedure 9-32 Change EAS alarm strings and severity levels

9-104

The current setting of the required EAS alarm string and severity level
may be viewed using the disp_element eas_alarm command and the
disp_element eas_severity command, respectively.

Enter the command:

chg_eas_alarm <alarm_table_index> <alarm_severity_level>
<new_alarm_string>

Repeat this procedure for each required alarm table entry.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

alarm strings and security levels using the TTY interface

Changing EAS

Example
For example, to select severity level 4 and define Low Room Temperature as the alarm string for
table entry 17, enter the command:
chg_eas_alarm 17 4 Low Room Temperature
The following shows examples of the displaying/defining and changing EAS alarms and the
subsequent system responses: -> disp_element eas_alarm 1 bsc
eas_alarm = Door 4 Alarm
-> disp_element eas_severity 1 bsc
eas_severity = 2
-> chg_eas_alarm 1 4 Door 5 Alarm
COMMAND ACCEPTED
-> disp_element eas_alarm 1 bsc
eas_alarm = Door 5 Alarm
-> disp_element eas_severity 1 bsc
eas_severity = 4
-> disp_element eas_alarm 17 bsc
eas_alarm = High Room Temperature
-> disp_element eas_severity 17 bsc
eas_severity = 3
-> chg_eas_alarm 17 4 Low Room Temperature
COMMAND ACCEPTED

68P02901W17-T

9-105
Jan 2010

Creating an EAS device using the OMC-R GUI

Chapter 9: Configuring Devices and Functions

Creating an EAS device using the OMC-R GUI

Introduction to creating an EAS using the OMC-R GUI

To create an EAS using the OMC-R GUI, use the EAS Detailed View.

Creating an EAS using the Navigation Tree

To create an instance of an EAS device, follow these steps:

Procedure 9-33 Create an instance of an EAS device

1

Navigate to and select the EAS class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Hardware Devices
EAS). If necessary, see Navigating to a network object class or instance
on page 1-28 for further details.

Select Edit Create from the menu bar. The OMC-R displays the DRI
Detailed View form.

Enter the required information in this form. See EAS Detailed View
fields for details.
Result: If EAS Alarm is selected in the Alarm Id field, the EAS Alarms
Dialog window is displayed, see Figure 9-19.

Double-click the alarm text to be displayed when an alarm is reported

for the optocoupler.
Result: The OMC-R displays the selected alarm in the Alarm Id field.

9-106

Repeat for each optocoupler for which an alarm is to be assigned.

Create and close the Detailed View form.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating an EAS using the Navigation Tree

Figure 9-19 EAS Alarms Dialog

ti-GSM-EASAlarmsDialog-00826-ai-sw

68P02901W17-T

9-107
Jan 2010

EAS Detailed View fields

Chapter 9: Configuring Devices and Functions

EAS Detailed View fields

The following sections list and briefly describe the parameter fields in the EAS Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-29 describes the fields in the Identification grouping of the EAS Detailed View.

Table 9-29 EAS Detailed View fields - Identification grouping

Field name

Brief description

Values

RDN Class

See description in Table 4-1.

Default is
device class.

RDN instance

EAS identifier, see description in

Table 3-1.

0 - 15.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

site. Click to display the parent SITE
Detailed View.

Mandatory or
Optional?

Cage and Slot Information grouping

Table 9-30 describes the fields in the Cage and Slot Information grouping of the EAS Detailed
View.

NOTE
An M-Cell and Horizon BTS, does not have a cage or slot. The slot identity is replaced
by the cabinet identity where the Main Control Unit (MCU) resides.

9-108

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

EAS Detailed View fields

Table 9-30 EAS Detailed View fields - Cage and Slot Information grouping
Field name

Values

Brief description

Cage Identifier

Identifier of the cage where the PIX

board is located.

Default is null.

Daughter Card
Slot Number

Identifier of the daughter slot where

the PIX board is located. Not valid at
an M-Cell site.

15 - 18.

Mandatory or
Optional?

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Optocoupler groupings
Each Optocoupler group displays the fields shown in Table 9-31, where <no.> is the Optocoupler
number (1 to 16, 9 to 16 at M-Cell site only).

For a Horizon II mini or Horizon II mini extension, Optocouplers 13 to 16 are not displayed
in the EAS Detailed View.
An EAS device can be equipped with Optocouplers 1 - 6 at Horizon II micro master and
extension cabinets; 7 - 16 are out of range.

NOTE
PIX inputs 7 to 16 are hard wired in Horizon II micro and therefore not available
for customer use. This does not decrease the size of the EAS Optocoupler array, it
only inhibits access to part of it.
For an EAS device equipped to a Horizon II mini or Horizon II mini extension cabinet, the
OMC-R displays the following details for Optocoupler 1 to 12 only:

Alarm Reporting.

No Alarm When.

Alarm Id.

68P02901W17-T

9-109
Jan 2010

EAS Detailed View fields

Chapter 9: Configuring Devices and Functions

Table 9-31 EAS Detailed View fields - OptoCoupler groupings

Field name/BSS
parameter name

Mandatory or
Optional?

Values

Brief description

Alarm Reporting
opto<no.>
_reporting

Specifies whether the

alarm is reported when
the optocoupler enters the
alarm state.

Enabled (1) or Disabled

(0).
Default is Disabled.

Mandatory.

No Alarm When
opto<no.>_state

Specifies the no alarm state

for the optocoupler. This
field is grayed-out if the
Alarm Reporting field is set to
Disabled.

Optocoupler is open or
Optocoupler is closed.

Mandatory.

Alarm Id
opto<no.>
_alarm_id

Specifies which alarm

is reported when this
optocoupler enters the
alarm state. Only displayed if
the Alarm Reporting field is
set to Enabled, otherwise it is
grayed-out.

Main Power Failure (125)

or EAS Alarm (0 to 33).
If EAS Alarm is selected,
Figure 9-19 can be used
to select an alarm.

Optional.

Relay Information grouping

Table 9-32 describes the fields in the Relay Information grouping of the EAS Detailed View. The
Horizon II Micro BTS software disables access to relay 4.

Table 9-32 EAS Detailed View fields - Relay Information grouping

9-110

Mandatory or
Optional?

Field name

Brief description

Values

Relay 1 to 4 Wiring

Initial state of the relay, whether the

relay wiring is Normally Closed or
Normally Open. Relay 1 Wiring can
be specified only during creation.

Normally
Closed (1) or
Normally Open
(0).

Mandatory.

Relay 1 to 4 State

Whether the relay state is Normally

Closed or Normally Open. These
fields are grayed-out in Create mode.
The fields can only be changed when
editing the form in Edit mode after it
has been created.

Normally
Closed (1) or
Normally Open
(0).

Optional.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring an EAS using the TTY interface

Configuring an EAS using the TTY interface

Equipping an EAS using the equip command

EAS and the equip command
When equipping an EAS device, the equip command is used to specify whether the alarm is
to be reported. For example, with the no alarm condition for optocoupler 7 equal to 0 and
reporting of optocoupler 7 state changes is enabled, the OMC-R receives an alarm notification
when the associated input changes from low to high impedance. Assuming optocoupler 7 is
assigned EAS alarm index 4, the alarm string and severity level for that EAS alarm table entry
is reported. In addition, the OMC-R receives a clear alarm notification when the optocoupler
input state changes back to low impedance.

Using the equip command to equip an EAS

To equip an EAS device using the TTY interface, see subsection Introduction to configuring
individual devices and functions on page 9-3 in Methods of configuring individual devices
and functions on page 9-3.

Modifying EAS details using the TTY interface

To modify information about an EAS using the TTY interface, see Methods of configuring
individual devices and functions on page 9-3.
Use the modify_value command and the opto_reporting parameter to modify EAS device
details, such as:

Optocouplers for which state changes should or should not be reported.

Alarm index (that is, the alarm text string in the EAS alarm table) to be displayed for
an optocoupler.

Displaying EAS details using the TTY interface

To display information about an EAS using the TTY interface, see Methods of configuring
individual devices and functions on page 9-3.

68P02901W17-T

9-111
Jan 2010

Configuring the EAS physical relay states using the TTY interface

Chapter 9: Configuring Devices and Functions

Configuring the EAS physical relay states using the TTY

interface

Displaying the physical relay states for an EAS

To display the physical relay states for EAS device use the disp_relay_contact command. For
example, the following command displays the relay states for an EAS device:
disp_relay_contact 0 0
Relay 1: Closed
Relay 2: Open
Relay 3: Open~
Relay 4: Closed
COMMAND ACCEPTED
Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the disp_relay_contact command.

Setting the physical relay states for an EAS

To set the physical relay states for EAS device, use the set_relay_contact command. For
example to set the physical relay 4 of EAS 0 0 0 to a closed circuit, use the following command:
set_relay_contact 0 0 2 1
Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete
information on the set_relay_contact command.

9-112

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a GCLK device

Configuring a GCLK device

Definition of a GCLK
The Generic Clock (GCLK) device generates all timing reference signals required at the site.
The clock signals are distributed over optical fiber cables, which are terminated on CLKX and
KSWX boards.
A GCLK cannot be explicitly created in an M-Cell site. For an M-Cell site:

GCLK instance 0 is auto created (equipped) by the BSS when BTP instance 0 is created
(equipped).

GCLK instance 1 is auto created (equipped) by the BSS when BTP instance 1 is created
(equipped).

For GCLK synchronization, see GCLK synchronization on page 7-43.

Rules for configuring a GCLK

GCLK A and GCLK B must be equipped in the same cage.

GCLK slot restrictions

The slot assigned to the GCLK is based on the device id. If the device id is set to 0, the GCLK is
assigned to slot 5. If the device id is set to 1, the GCLK is assigned to slot 3.

Creating a GCLK device using the OMC-R GUI

To create a GCLK device, proceed as follows:

Procedure 9-34 Create a GCLK device

68P02901W17-T

Navigate to and select the GCLK class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Hardware Devices
GCLK). If necessary, see Navigating to a network object class or
instance on page 1-28 for further details.

Select Edit Create from the menu bar. The OMC-R displays the
GCLK Detailed View form.

Enter all required information in this form. See GCLK Detailed View
fields for details.

Create and close the Detailed View. If required, see Creating a network
object using the OMC-R GUI on page 1-32 for further details.

9-113
Jan 2010

GCLK Detailed View fields

Chapter 9: Configuring Devices and Functions

GCLK Detailed View fields

The following sections list and briefly describe the parameter fields in the GCLK Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-33 describes the fields in the Identification grouping of the GCLK Detailed View.

Table 9-33 GCLK Detailed View fields - Identification grouping

Field name

Brief description

Values

Mandatory or Optional?

RDN Class

See description in
Table 4-1.

Default is the device

class.

RDN Instance

GCLK identifier,
see description in
Table 3-1.

0 or 1. Default is 0.

NMC RDN Value

See description in
Table 4-1.

Parent Detailed View

Displays the name of

the parent SITE. Click
to display the parent
SITE Detailed View.

Kit Number

See description in
Table 9-3.

Field Replacement
Unit (FRU)

See description
in Table 9-3. The
option HIISC is also
available for
a GCLK.

Serial Number

See description in
Table 9-3.

Clock Extender 0

(slot U7) Indicates

whether CLKX 0 is
present for this GCLK.

CLKX0 is not present

(0) or CLKX0 is
present (1).

Optional.

Clock Extender 1

(slot U6) Indicates

whether CLKX 1 is
present for this GCLK.

CLKX1 is not present

(0) or CLKX1 is
present (1).

Optional.

Continued
9-114

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping a GCLK device using the TTY interface

Table 9-33 GCLK Detailed View fields - Identification grouping (Continued)

Field name
Clock Extender 2

Brief description

Values

Mandatory or Optional?

(slot U5) Indicates

whether CLKX 2 is
present for this GCLK.

CLKX2 is not present

(0) or CLKX2 is
present (1).

Optional.

Cage and Slot Information grouping

Table 9-34 describes the fields in the Cage and Slot Information grouping of the GCLK Detailed
View.

Table 9-34

GCLK Detailed View fields - Cage and Slot Information grouping

Field name

Values

Brief description

Cage Identifier

See description in
Table 9-4.

Slot Number

See description in
Table 9-4.

Mandatory or Optional?

0 or 1.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Equipping a GCLK device using the TTY interface

To equip a GCLK using the TTY interface, see Methods of configuring individual devices
and functions on page 9-3.

68P02901W17-T

9-115
Jan 2010

Configuring a GPROC device

Chapter 9: Configuring Devices and Functions

Configuring a GPROC device

Definition of a GPROC
The Generic Processor (GPROC) performs all control functions for the BSC, BTS, or RXCDR. Not
valid at an M-Cell site. GPROC2 or GPROC3 are required for all configurations.
The last GPROC instance within a site cannot be deleted.

Prerequisites for configuring a GPROC

Before equipping Generic Processors (GPROCs), KSWs MUST be equipped.
When equipping a GPROC at a remote BTS, a Base Transceiver Processor (BTP) MUST be
equipped.
When equipping a GPROC device at a BSC or RXCDR, a Base Site Control Processor (BSP)
MUST be equipped.

GPROC slot restrictions

Table 9-35 shows valid cage and slot numbers which are dependent on the site type.

Table 9-35 GPROC cage and slot numbers

Site

Cage numbers

Slot numbers

BSC sites

0 - 13

18 - 25

RXCDR sites

0 - 13

25, 26

NOTE
The values for the slot numbers assume that slots 20 and 24 are the master slots for
the BSC/BTS, and slot 25 is the master slot for the RXCDR.

9-116

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating a GPROC device using the OMC-R GUI

Creating a GPROC device using the OMC-R GUI

To create an instance of a GPROC device, proceed as follows:

Procedure 9-35 Create an instance of a GPROC device

1

Navigate to and select the GPROC class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Hardware Devices
Processors - GPROC). If necessary, see Navigating to a network object
class or instance on page 1-28 for further details.

Select Edit Create from the menu bar.

Result: The OMC-R displays the GPROC Detailed View form.

Enter all required information in this form. See GPROC Detailed

View fields for details of the fields.

Create and close the Detailed View. If required, see Creating a network
object using the OMC-R GUI on page 1-32 for further details.

GPROC Detailed View fields

The following sections list and briefly describe the parameter fields in the GPROC Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-36 describes the fields in the Identification grouping of the GPROC Detailed View.

Table 9-36

GPROC Detailed View fields - Identification grouping

Field name

Brief description

Values

RDN Class

See description in
Table 4-1.

Default is the device

class.

RDN Instance

GPROC identifier,
see description in
Table 3-1.

0 or 111
Default is 0.

Mandatory or Optional?

Continued

68P02901W17-T

9-117
Jan 2010

GPROC Detailed View fields

Chapter 9: Configuring Devices and Functions

Table 9-36 GPROC Detailed View fields - Identification grouping (Continued)

Field name

Brief description

NMC RDN Value

See description in
Table 4-1.

Parent Detailed View

Displays the name of

the parent site. Click
to display the parent
SITE Detailed View.

Kit Number

See description in
Table 9-3.

Field Replacement
Unit (FRU)

See description in
Table 9-3.

Serial Number

See description in
Table 9-3.

Values

Mandatory or Optional?

Cage and Slot Information grouping

Table 9-37 describes the fields in the Cage and Slot Information grouping of the GPROC
Detailed View.

Table 9-37 GPROC Detailed View fields - Cage and Slot Information grouping
Field name

Brief description

Values

Cage Identifier

See description in
Table 9-4.

See Table 9-35.

Slot Number

See description in
Table 9-4.

See Table 9-35.

Mandatory or Optional?

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Table 9-38 describes the unique fields in the State Identification grouping of the GPROC
Detailed View. For descriptions of the standard State Information fields, see Table 4-2.

Table 9-38

GPROC Detailed View fields - State Information grouping

Field name
Assigned Function
(OMC-R only
attribute)

9-118

Brief description
The software function
within which the
GPROC is busy.

Values

Mandatory or Optional?
Optional.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping a GPROC device using the TTY interface

Equipping a GPROC device using the TTY interface

To equip a GPROC using the TTY interface, see Methods of configuring individual devices
and functions.

Equipping a GPROC at a BSC or BSS site

When equipping a GPROC at a BSC or BSS site, refer to (for BSC type 1 and 2).

68P02901W17-T

9-119
Jan 2010

Configuring a KSWpair device

Chapter 9: Configuring Devices and Functions

Configuring a KSWpair device

Definition of a KSWpair
A KSWpair groups a pair of KSW devices which manage a single TDM highway. The KSW object
instances that are contained below this KSWpair define the two KSW devices. (Basically a
KSWpair is a placeholder for the underlying KSW instances.
When the parent SITE is created, all KSWpair instances contained by that SITE instance are
autocreated by the BSS.

KSWpair Detailed View fields

The following sections list and briefly describe the parameter fields in the KSWpair Detailed
View according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-39 describes the fields in the Identification grouping of the KSWpair Detailed View.

Table 9-39 KSWpair Detailed View fields - Identification grouping

Field name

Brief description

Values

RDN Class

See description in
Table 4-1.

Default is the device

class.

RDN Instance

KSWpair identifier,
see description in
Table 3-1.

0 or 3.
Default is 0.

NMC RDN Value

See description in
Table 4-1.

Mandatory or Optional?

Continued

9-120

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

KSWpair Detailed View fields

Table 9-39 KSWpair Detailed View fields - Identification grouping (Continued)

Field name

Brief description

Values

Parent Detailed View

Displays the name of

the parent SITE. Click
to display the parent
SITE Detailed View.

Controlling KSWX for

Highway 0

Indicates which
KSWX daughter card
is used to control the
first 1024 timeslots
on the TDM highway.
First device id must
match the KSW pair
in the cage where
the KSW is being
equipped.

0 - 3.
Default is 0.
The KSW controls the
first 1024 timeslots
(0).
Expansion KSWX
A0/B0 is connected
to the cage that
controls the first
1024 timeslots (1).
Expansion KSWX
A1/B1 is connected
to the cage that
controls the first
1024 timeslots (2).
Expansion KSWX
A2/B2 is connected
to the cage that
controls the first
1024 timeslots (3).

Mandatory.

Controlling KSWX for

Highway 1

Indicates which
KSWX daughter card
is used to control the
second 1024 timeslots
on the TDM highway.
First device id must
match the KSW pair
in the cage where
the KSW is being
equipped.

Default is 1.

Mandatory.

Controlling KSWX for

Highway 2

Indicates which
KSWX daughter card
is used to control the
third 1024 timeslots
on the TDM highway.
First device id must
match the KSW pair
in the cage where
the KSW is being
equipped.

Default is 2.

Mandatory.

Mandatory or Optional?

Continued

68P02901W17-T

9-121
Jan 2010

KSWpair Detailed View fields

Chapter 9: Configuring Devices and Functions

Table 9-39 KSWpair Detailed View fields - Identification grouping (Continued)

Field name

Brief description

Controlling KSWX for

Highway 3

Indicates which
KSWX daughter card
is used to control the
fourth 1024 timeslots
on the TDM highway.
First device id must
match the KSW pair
in the cage where
the KSW is being
equipped.

Values
Default is 3.

Mandatory or Optional?
Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

9-122

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a KSW (or DSW) device

Configuring a KSW (or DSW) device

Definition of a KSW and KSWX

The Kiloport Switch (KSW) is a time-division digital switch. The KSW takes information from the
inbound Time Division Multiplexed (TDM) highway, and transposes it to another timeslot on
the outbound TDM highway.
KSW instances are not applicable at M-Cell sites.
A KSWX is a Kiloport Switch board extension.

Rules for configuring a KSW

A minimum of one non-redundant KSW is required at every BSC. Up to four KSW modules may
be interconnected using optical fiber cables. This provides a total switching capacity of 4096
x 64 kbit/s ports (16 384 x 16 kbit/s ports), and an increased switching rate of 256 Mbit/s for
each TDM highway (2 TDM highways total).

Slot restrictions for KSW

The KSW slot is assigned based on the second device id. If this value is 0, the KSW is assigned
to slot 27. If it is set to 1, the KSW is assigned to slot 1.

Definition of a DSW and DSWX

A Double Kiloport Switch (DSW) is an enhanced version of the KSW. It supports twice as many
ports and extended subrate switching capability down to 8 kbit/s (single bit). For the double
rate TDM bus the bandwidth is increased to 128 Mbps, partitioned into 2048 timeslots.
A DSWX is a Double Kiloport Switch board extension.
The DSW/DXWX replaces the existing KSW/KSWX for 8 kbit/s switching in support of the
Adaptive MultiRate (AMR) Half Rate (HR) feature, see Adaptive Multi-Rate (AMR) on page
2-129 for details.
The Enhance BSC Capacity Using DSW feature doubles the number of TDM timeslots that are
available within the BSC. The maximum supported extension is 4 x 2048 = 8192 TDM timeslots
when four expansion cages are configured. For details about this feature see, Maintenance
Information: BSS Field Troubleshooting (68P02901W51).
To create a DSW using the OMC-R GUI, use the KSW Detailed View form.

68P02901W17-T

9-123
Jan 2010

Creating a KSW or DSW device using the OMC-R GUI

Chapter 9: Configuring Devices and Functions

Creating a KSW or DSW device using the OMC-R GUI

To create an instance of a KSW or DSW device, proceed as follows:

Procedure 9-36 Create an instance of a KSW or DSW device

1

Navigate to and select the KSW class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Hardware Devices
KSWpair KSWpair instance KSW). If necessary, see Navigating to
a network object class or instance on page 1-28 for further details.

Select Edit Create from the menu bar.

The OMC-R displays the KSW Detailed View.

Enter all required information in this form. See KSW Detailed View
fields for further details.

Create and close the Detailed View. If required, see Creating a network
object using the OMC-R GUI on page 1-32 for further details.

KSW Detailed View fields

The following sections list and briefly describe the parameter fields in the KSW Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details.

Identification grouping
Table 9-40 describes the fields in the Identification grouping of the KSW Detailed View.

Table 9-40

KSW Detailed View fields - Identification grouping

Field name

Brief description

RDN Class

See description in
Table 4-1.

RDN Instance

KSW or DSW
identifier, see
description in
Table 3-1.

Values

Mandatory or Optional?

Default is the device

class.
0 or 1.
Default is 0.

Continued

9-124

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

KSW Detailed View fields

Table 9-40 KSW Detailed View fields - Identification grouping (Continued)

Field name

Brief description

NMC RDN Value

See description in
Table 4-1.

Parent Detailed View

Displays the name of

the parent KSWpair.
Click to display the
parent KSWpair
Detailed View.

Kit Number

See description in
Table 9-3.

Field Replacement
Unit (FRU)

See description in
Table 9-3. For a
KSW board, KSW
is displayed. For a
DSW board, KSW is
displayed.

Serial Number

See description in
Table 9-3.

Values

Mandatory or Optional?

Cage and Slot Information grouping

Table 9-41 describes the fields in the Cage and Slot Information grouping of the KSW Detailed
View.

Table 9-41 KSW Detailed View fields - Cage and Slot Information grouping
Field name

Brief description

Cage Identifier

See description in
Table 9-4.

Slot Number

See description in
Table 9-4.

Values

Mandatory or Optional?

See Slot restrictions

for KSW.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

68P02901W17-T

9-125
Jan 2010

Equipping a KSW device using the TTY interface

Chapter 9: Configuring Devices and Functions

Equipping a KSW device using the TTY interface

To equip a KSW using the TTY interface, see Methods of configuring individual devices
and functions.

NOTE
Answer the final KSW equip prompt in the same way for the two KSWs that make
up the same portion of the TDM. The first device id must match the KSW pair in the
cage where the KSW is being equipped.
The following is an example of equipping a KSW:
-> equip bsc KSW
Enter Portion of TDM Highway Managed (identifier 1): 0
Enter the TDM identifier (identifier 2):

Enter the cage number: 0

COMMAND ACCEPTED

Displaying DSW or KSW details using the TTY interface

To display details of a DSW or KSW use the disp_equipment command. For example the
following command displays equipment information for DSW at the BSC:
disp_equipment 0 KSW 0 1 0 full
The system responds, for example:
Portion of TDM Highway Managed (identifier 1): 0
TDM Identifier (identifier 2): 1
Cage number: 0
Slot number: 1
DRIs allowed on highway managed by this KSW?: NO
Hardware Information:
FRU: DSW
Kit Number: hvn = 6
Serial Number: Not Applicable

9-126

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring an LCF function

Configuring an LCF function

Introduction to configuring an LCF

When equipping an MSI device in a BSC, the Link Control Function (LCF) may be added for
traffic considerations.
An LCF can only be created under SITE 0 (the BSC), where up to 25 LCFs can be equipped.
For a BSS to support a BSS-based SMLC, at least one LCF must manage one or more LMTL
devices. Otherwise, an error message is displayed. Up to two LMTL devices can be managed
by an LCF.
An LCF cannot simultaneously manage an LMTL and MTL.
Each LCF can support up to 12 GSLs.

Prerequisites to configuring an LCF

Before adding LCF functions, the GPROCs must be equipped.
Before unequipping or deleting an LCF, all GSLs on the LCF must be unequipped or reassigned
to other LCFs.

Creating an LCF function using the OMC-R GUI

To create an instance of an LCF device, proceed as follows:

Procedure 9-37 Create an instance of an LCF

1

Navigate to and select the LCF class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Software Functions
LCF). If necessary, see Navigating to a network object class or instance
on page 1-28 for further details.

Select Edit Create from the menu bar.

Result: The OMC-R displays the LCF Detailed View form.

68P02901W17-T

Enter all required information in this form. See LCF Detailed View
fields for details.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

9-127
Jan 2010

LCF Detailed View fields

Chapter 9: Configuring Devices and Functions

LCF Detailed View fields

The following sections list and briefly describe the parameter fields in the LCF Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-42 describes the fields in the Cage and Slot Information grouping of the LCF Detailed
View.

Table 9-42

LCF Detailed View fields - Identification grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

RDN Class

See description in Table 4-1.

Default is the
device class.

RDN Instance

LCF identifier, see description in

Table 3-1.

0 - 24.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

SITE. Click to display the parent
SITE Detailed View.

Maximum Number
of CBLs
max_cbls

The maximum number of CBLs the

LCF can manage.

0 or 1.

Mandatory.

Maximum Number
of MTLs
max_mtls

The maximum number of MTLs the

LCF can manage.

0 - 20, 1, or
2 for GPROC2
boards.

Mandatary.

Maximum Number
of GSLs
max_gsls

The maximum number of GSLs the

LCF can manage. Only displayed if
the GPRS feature is unrestricted.

0 - 12.

Optional.

Continued

9-128

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 9-42

Equipping an LCF function using the TTY interface

LCF Detailed View fields - Identification grouping (Continued)

Field name/BSS
parameter name

Values

Brief description

0 - 2.
No default.

Mandatory or
Optional?

Max Number of
LMTLs max_lmtls

The maximum number of LMTLs the

LCF can manage. This parameter
can only be used when the when
the BSS is configured to support a
BSS-supported SMLC.
If an attempt is made to equip an
LCF accommodating both LMTLs and
MTLs, the command is rejected and
an error message is displayed.

SITEs Managed

The sites managed by this LCF.

Optional.

Controlled CBLs

The CBLs controlled by this LCF.

Optional.

Controlled MTLs

The MTLs controlled by this LCF.

Optional.

Controlled GSLs
(OMC-R only
attribute)

The GSLs controlled by this LCF.

Only displayed if the GPRS feature is
unrestricted.

Optional.

Controlled LMTLs

The LMTLs controlled by this LCF.

Only displayed, if the Location
Services feature is unrestricted.

Optional.

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Equipping an LCF function using the TTY interface

To equip an LCF using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.
The following provides an example of equipping an LCF function.
-> equip bsc LCF
Enter the function ID for the LCF: 0
Enter the number of MTLs the LCF can manage:

Enter the number of CBLs the LCF can manage:

COMMAND ACCEPTED
->

68P02901W17-T

9-129
Jan 2010

Displaying LCF settings using the TTY interface

Chapter 9: Configuring Devices and Functions

When the BSS is configured to support a BSS-supported SMLC, the following prompt is also
displayed:
Enter the number of LMTLs the LCF can manage:
See Table 9-42 for details of the max_lmtls parameter.

Displaying LCF settings using the TTY interface

To display information about a CIC using the TTY interface, see Methods of configuring
individual devices and functions on page 9-3.
For example, the following command displays current settings for an LCF device:
disp_equipment 0 LCF 0

Modifying LCF settings using the TTY interface

Use the modify_value command to modify an LCF parameter. For example, the following
command changes the max_lmtls setting of LCF 0 to 1: modify_value bsc max_lmtls 1 LCF 0
See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS
commands, prompts, and parameters.

9-130

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring an LMTL device

Configuring an LMTL device

Definition of an LMTL
The Location Services Message Transfer Link (LMTL) is the signaling link between the BSC and
the BSS-based SMLC over which runs the MTP protocol. The LMTL represents the Lb interface.
The LMTL is a 64 kbit/s MPRT on the MMS device. The LMTL uses SS7 MTP and SCCP
protocols (with variations specified by GSM standards) for communication between the BSC
and the BSS-based SMLC.
An LMTL can only be equipped at a BSC (SITE0).
Up to 16 LMTLs can be supported by a BSC.
An LMTL is a child of an MMS device.
An LMTL is managed by an LCF. Up to two LMTLs can be managed by an LCF.
Also see Modifying LMTL loadsharing granularity on page 9-134, if appropriate.

LMTL restrictions
If an attempt is made to equip an LMTL to an MMS which is already associated with a non-Lb
device, the command is accepted but an MMS usage conflict message is displayed.

Prerequisites for creating an LMTL

An LMTL can only be created if the Location Features feature has been purchased and is
unrestricted, and the BSS must support a BSS-based SMLC (see Location Features mode in
Table 2-18).

LMTL parameters
Table 9-43 details the LMTL parameters.

Table 9-43 LMTL parameters

Field name

Description

LMTL Device
Identification

A unique identifier for the LMTL device. Valid values: 0 v 15. No

default.

First MMS Identifier

The identity of the first MMS to which the LMTL is equipped. Valid
values: 0 - 55. No default.
Continued

68P02901W17-T

9-131
Jan 2010

Creating an LMTL device using the OMC-R GUI

Chapter 9: Configuring Devices and Functions

Table 9-43 LMTL parameters (Continued)

Field name

Description

Second MMS identifier

The identity of the second MMS to which the LMTL is equipped.

Valid values: 0 - 1. No default.

Timeslot

The identity of the timeslot used by the LMTL on the MMS. Valid
values: For E1, 1 - 31. No default.

Creating an LMTL device using the OMC-R GUI

To create an instance of an LMTL device using the OMC-R GUI, follow these steps:

Procedure 9-38 Create an instance of an LMTL device

1

Navigate to and select the LMTL class button in the Navigation Tree
(BSS BSS instance SITE SITE instance (SITE 0 only) Logical
Links LMTL). If necessary, see Navigating to a network object class
or instance on page 1-28 for further details.

Select Edit Create from the menu bar.

Result: The OMC-R displays the LMTL Detailed View form.

Enter all required information in this form. See Table 9-43 for details
of the LMTL parameters.

NOTE
To obtain the relevant information for a parameter, select
Help - On Context from the menu bar and drag the ?
prompt to the appropriate field and click that field. A
context-sensitive help page is displayed.
4

Create and close the Detailed View. See Creating a network object
using the OMC-R GUI on page 1-32 for further details.

Commands used to configure an LMTL using the TTY interface

From the OMC-R, the following commands can be used to configure an LMTL device through
the remote login TTY interface:

9-132

equip

disp_equip

unequip

state

lock_device

unlock device

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

ins_device

reset_device

shut_down device

disp_hdlc

disp_processor

disp_mms_ts_usage

Creating an LMTL using the TTY interface

These commands and their parameters are fully detailed in Technical Description: BSS

Command Reference (68P02901W23)

Creating an LMTL using the TTY interface

To equip an LMTL device using the TTY interface, see Methods of configuring individual devices
and functions on page 9-3.
For example, the following command equips an LMTL:
equip 0 LMTL
Enter the device identification for this LMTL: 0
Enter the first MMS identifier for this device:
Enter the second MMS identifier for this device:

1
2

Enter the timeslot on MMS where this device appears:

29

COMMAND ACCEPTED
->

68P02901W17-T

9-133
Jan 2010

Modifying LMTL loadsharing granularity

Chapter 9: Configuring Devices and Functions

Modifying LMTL loadsharing granularity

Overview of LMTL loadsharing granularity

The loadsharing of traffic on the Location Services Message Transfer Links (LMTLs) in the
uplink direction from the BSS to the BSS-based SMLC can be specified.
However, loadsharing from the BSS-based SMLC to the BSC is based on the routing function
implemented at the BSS-based SMLC, and cannot be modified.
The granularity of the loadsharing can be set to 16 (regular granularity) or 64 (enhanced
granularity) virtual circuits. The greater the number of circuits, the more even the traffic
distribution is across the LMTLs.

NOTE
LMTL loadsharing granularity can be changed at any time, but the change does not
take effect until all the LMTLs are locked. If the element is changed in SYSGEN
mode, the change immediately takes effect.

Detailed description of BSS routing function

Call signaling traffic can be distributed over 16 or 64 virtual circuits.
The virtual circuits are evenly spread over active LMTLs. The message routing label consists of
the originating point code field (OPC), the destination point code field (DPC), and the signaling
link selection field (SLS). A signaling point is required to route all message traffic based on the
three fields in the routing label. The SLS is a 4-bit field used for loadsharing between multiple
links in the same linkset. The typical signaling point always routes messages with the same
routing label over the same physical link. routing messages in this way ensures that messages
are delivered in order. For a given originating point code (OPC) and destination point code
(DPC), the SLS field is the equivalent of a virtual circuit identifier.
When 64 virtual circuits are used to distribute signaling traffic originating at the BSS, a router
index in the range of 0 - 63 is randomly assigned to each call block when a call is established.
Random assignment results in even distribution of routing indices to call blocks. The router
index identifies the virtual circuit for all signaling messages associated with the call block. The
64 virtual circuits are evenly spread over the active LMTLs. This routing function is compliant
with the SS7 protocol because the BSS still routes all messaging associated with a given call
over the same physical LMTL.
Although the SLS is not used to perform routing at the BSS, the SLS field is completed. The SLS
may be used for message routing by the BSS-based SMLC. The SLS field of the routing label is
filled in with the lower 4 bits of the router index. This technique guarantees that all messages
associated with a call block have the same SLS field and it results in an even distribution
of SLS values to routing labels. Messages without a connection are assigned a randomly
generated router index. The SLS field is completed using the same technique described above
for connection oriented messages.

9-134

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Methods of modifying LMTL loadsharing granularity

Methods of modifying LMTL loadsharing granularity

The LMTL loadsharing granularity can be set using:

The OMC-R GUI BSS Detailed View.

TTY interface and the lmtl_loadshare_granularity parameter.

LMTL Loadshare Granularity field

Table 9-44 describes the LMTL Loadshare Granularity parameter.

Table 9-44 LMTL Loadshare Granularity parameter

OMC-R GUI field name/BSS
parameter name
LMTL Loadshare
Granularity
lmtl_loadshare
_granularity

Description
Displayed in the LCS grouping of the BSS Detailed View.
Valid values: 0 or 1, where:0 - 16 Virtual Circuits (regular
granularity). 1 - 64 Virtual Circuits (enhanced granularity).
Default is 0 (16 Virtual Circuits).

Modifying LMTL loadsharing granularity using the OMC-R GUI

To modify LMTL loadsharing granularity, follow these steps:

Procedure 9-39 Modify LMTL loadsharing granularity

1

Navigate to and select the BSS instance button in the Navigation Tree
(BSS BSS instance). If necessary, see Navigating to a network object
class or instance on page 1-28 for further details.

Select Edit Detailed View from the menu bar.

Result: The OMC-R displays the BSS Detailed View form in Monitor
mode.

Select Edit Edit.

Change the LMTL Loadshare Granularity field in the LCS grouping to

the required value. See Table 9-44 for details.
Result: The OMC-R displays the following message: This change
will not take effect until all LMTLs are in a Locked state.

Save and close the Detailed View.

Modifying LMTL loadsharing granularity using the TTY interface

To modify the LMTL loadsharing granularity using the TTY interface, use the following command:
chg_element lmtl_loadshare_granularity <value> 0

68P02901W17-T

9-135
Jan 2010

Displaying LMTL loadsharing granularity using the TTY interface

Chapter 9: Configuring Devices and Functions

For a detailed description of the lmtl_loadshare_granularity parameter and the chg_element

command, see Technical Description: BSS Command Reference (68P02901W23).

Displaying LMTL loadsharing granularity using the TTY interface

To display the LMTL loadsharing granularity using the TTY interface, use the following
command:
disp_element lmtl_loadshare_granularity 0
The system responds with the following information, for example:
LMTL_LOADSHARE_GRANULARITY = 1
For a detailed description of the lmtl_loadshare_granularity parameter and the
disp_element command, see Technical Description: BSS Command Reference (68P02901W23).

9-136

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring an MSI device

Configuring an MSI device

Definition of MSI
The Message Transfer Link (MTL) is the link between the MSC and the BSC over which MTP
protocol is run. When equipping an MSI device at a BSC, the MTL can be added for traffic
considerations.
An MSI device provides one of two types of interface between 2 Mbit/s links in the network.
These are a 64 kbit/s to 64 kbit/s channel interface for type 0 (MSI), and a 64 kbit/s to 16 or 64
kbit/s channel interface for type 1 (XCDR) and type 2 (GDP).
MSI 64 kbit/s to 16 or 64 kbit/s (XCDR) devices interface between 2 Mbit/s link to convert
between 64 kbit/s traffic channels and GSM-defined 16 kbit/s traffic channels. Although this
transcoding function may be performed at BSCs, the examples provided for these procedures
have the function performed remotely at the MSC.
Once the transcoding function is accomplished, an MSI 64 kbit/s to 64 kbit/s device can have its
64 kbit/s channels submultiplexed with four 16 kbit/s traffic channels.
See Technical Description: BSS Implementation (68P02901W36) and Maintenance Information:
Device State Transitions (68P02901W57) for a full description of an MSI.
See Configuring Enhanced GDP provisioning on page 9-146 for further information of
configuring MSI parameters for Enhanced GDP Provisioning.

MSI hierarchy requirements

When equipping an MSI device at a BSC, there may also be a requirement to equip an Operation
and Maintenance Link (OML). The first two OML devices are active/standby defaults.
When equipping an MSI for initial land circuits, there may be a requirement to equip a Radio
Signaling Link (RSL) device. The RSL carries the control and signaling information for the
site. At least one RSL must be equipped per site; two for redundancy. Up to eight RSLs may
be equipped for heavier signaling capacity. An RSL is NOT required for every MSI, or for
every 2 Mbit/s link.

Additional database changes required

Equipping MSI/XCDR devices requires the following additional database changes:

Connections through the remote transcoder.

Circuit assignments at the BSC.

Circuit assignments at the MSC.

68P02901W17-T

9-137
Jan 2010

Autocreation and deletion of MSI 0 and MMSs at a Horizon II macro BTS

Chapter 9: Configuring Devices and Functions

Link parameters
Once the MSI is equipped, two link parameters are automatically set in the firmware:

ber_oos_mon_period which determines the amount of time that an in-service MMS must
be above a set BER before it is taken out of service. Its default value is one second.

ber_restore_mon_period which determines the amount of time that an out-of-service

MMS must be below a specified BER before it is brought back into service. Its default
value is 6000 (ten minutes).

The value of these link parameters can later be modified using the modify_value command or
the Misc - Modify Value option of the BSS MML Command Constructor window. For additional
information concerning the modify_value command, refer to: Technical Description: BSS
Command Reference (68P02901W23).

Autocreation and deletion of MSI 0 and MMSs at a Horizon II

macro BTS
When the first BTP is created at a Horizon II macro BTS, MSI (MSI 0) is automatically created.
This MSI is the only one that can exist at a Horizon II macro BTS. When the BTP is deleted the
corresponding MSI is automatically deleted. An MSI, therefore, cannot be created, modified or
deleted by a user in a Horizon II macro BTS.
When the MSI is automatically created, six MMS devices are automatically created for the MSI
(MSI 0). When the MSI is automatically deleted, the six MMS devices are automatically deleted.

Creating an MSI using the OMC-R GUI

To create an instance of an MSI device, follow these steps:

Procedure 9-40 Create an instance of an MSI device

1

Navigate to and select the MSI class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Hardware Devices
MSI). If necessary, see Navigating to a network object class or instance
on page 1-28 for further details.

Select Edit Create from the menu bar.

Result: The OMC-R displays the MSI Detailed View form.

9-138

Enter all required information in this form. See MSI Detailed View
fields for details. Also see Configuring Enhanced GDP provisioning
on page 9-146 for further information of configuring MSI fields for
Enhanced GDP Provisioning.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

MSI Detailed View fields

MSI Detailed View fields

The following sections list and briefly describe the parameter fields in the MSI Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

Identification grouping
Table 9-45 describes the fields in the Identification grouping of the MSI Detailed View.

Table 9-45 MSI Detailed View fields - Identification grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

MSI Type
msi_type

See Configuring Enhanced GDP

provisioning on page 9-146 for
ways in which the MSI type can
be modified. Also see Adaptive
Multi-Rate (AMR) on page 2-129
and Configuring Enhanced GDP
provisioning on page 9-146.

0 - 3,
Mandatory.
7 - 9,
12, 14,
20 and 21:
MSI-MSI (0),
MSI-XCDR (1),
MSI-GDP (2),
MSI-NIU (3),
MSI-EXT-HDSL
(7),
MSI-NIU-HDSL
(8),
MSI-NIU-EXT-HDSL
(9),
MSI-RF_Unit
(12),
MSI-E1_PMC
(14),
MSI-GDP2
(20),
NIU2 (21)

MCU Card Frame

Only valid when MSI type is NIU.

The MCU card frame where this
MSI-NIU device resides.

0 or 1.

RDN Class

See description in Table 3-1.

Default is the
device class.

Optional.

Continued

68P02901W17-T

9-139
Jan 2010

MSI Detailed View fields

Chapter 9: Configuring Devices and Functions

Table 9-45 MSI Detailed View fields - Identification grouping (Continued)

Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

RDN Instance

MSI identifier, see description in

Table 3-1.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

SITE. Click to display the parent SITE
Detailed View.

Kit Number

See description in Table 9-3.

Field Replacement
Unit (FRU)

See description in Table 9-3. The

option NIU2 is also available for an
MSI. For an MSI of type MSI-GDP2,
the FRU is set to GDP2.

Serial Number

See description in Table 9-3.

Related MMS

The NMC name of the MMS on the

BSC connected to this XCDR.

Optional.

Transcoding
Capability

See Configuring Enhanced GDP

provisioning on page 9-146 for
further details.

Optional.

MSI ID to the MSC

See Configuring Enhanced GDP

provisioning on page 9-146 for
further details.

Optional.

MMS ID to the MSC

See Configuring Enhanced GDP

provisioning on page 9-146 for
further details.

Optional

0 or 123.
Default is 0.

Cage and Slot Information grouping

Table 9-46 describes the fields in the Cage and Slot Information grouping of the MSI Detailed
View.

Table 9-46 MSI Detailed View fields - Cage and Slot Information grouping
Field name

Brief description

Cage Identifier

See description in Table 9-4. This field

is insensitive if the MSI
Type is NIU2.

Slot Number

See description in Table 9-4. This field

is insensitive if the MSI
Type is NIU2.

Values

Mandatory or
Optional?

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.
9-140

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

MSI Detailed View fields

State grouping
Standard network object state fields, see Table 4-2 for details.

Reconfiguration Information grouping

Currently, not used.

MMS HDSL Information grouping

Table 9-47 describes the fields in the MMS HDSL Information grouping of the MSI Detailed
View. These fields are grayed-out if Integrated M-Cell HDSL Feature (hdslOpt) is restricted.

Table 9-47 MSI Detailed View fields - MMS HDSL Information grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Link Protocol Type for

MMS 0
MMS0_link_type

The link protocol type utilized by

MMS 0 on the MSI. Only used if
msi_type is MSI-NIU-HDSL,
MSI-NIU-EXT-HDSL, or
MSI-EXT-HDSL.

E1 (0) or HDSL
(6).

Optional.

Number of Timeslots
MMS 0 supports
MMS0_timeslots

The number of timeslots that

MMS 0 supports. Only used if the
MSI type is MSI-NIU-HDSL,
MSI-NIU-EXT-HDSL or
MSI-EXT-HDSL.
Only used if MMS0_link_type is
HDSL.

16 or 32.

Optional.

Modem Setting
Utilized by
MMS 0
mms0_hdsl_modem
_setting
(OMC-R parameter
name:
MMS0_hdsl_mdm_set)

The modem setting utilized by

MMS 0. Only used if the MSI
type is MSI-NIU-HDSL, and
MMS0_link_type is HDSL.

Master (1) or
Slave (2).

Optional.

Link Protocol Type for

MMS 1
MMS1_link_type

The link protocol type utilized

by MMS 1 on the MSI. See
Link Protocol Type for MMS 0
description.

E1 (0) or HDSL
(6).

Optional.

Number of Timeslots
MMS 1 supports
MMS1_timeslots

Number of timeslots that MMS 1

supports. See Number of Timeslots
MMS 0 supports description.

16 or 32.

Optional.

Continued

68P02901W17-T

9-141
Jan 2010

Equipping an MSI using the TTY interface

Table 9-47

Chapter 9: Configuring Devices and Functions

MSI Detailed View fields - MMS HDSL Information grouping (Continued)

Field name/BSS
parameter name

Values

Brief description

Modem Setting
The modem setting utilized by
Utilized by
MMS 1. See Modem Setting
MMS 1
Utilized by MMS 0 description.
mms1_hdsl_modem
_setting
(OMC-R parameter
name:
MMS1_hdsl_mdm_set)
Data Processor

The unique id of the DPROC on

which the MSI resides. Only valid
if msi_type is MSI-E1_PMC.

Data Processor Socket

The socket on the DPROC on which

this MSI resides. Only valid if
msi_type is MSI-E1_PMC.

Master (1) or
Slave (2).

Mandatory or
Optional?
Optional.

Optional.

1 or 2.

Optional.

Equipping an MSI using the TTY interface

To equip an MSI using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.

Equipping an MSI at a BSC or BSS site

When equipping an MSI at a BSC or BSS site and the expansion increases the MSC-BSC
trunking enough so that an additional MTL/LCF is required, refer to the following procedures:

Configuring an MTL device on page 9-152.

Configuring an LCF function on page 9-127 (for BSC type 1 and 2).

Equipping an MSI at a remote or integrated BTS

When equipping an MSI at a remote or integrated BTS and the expansion increases the BSC-BTS
traffic to require another control link, refer to Configuring an RSL device on page 9-176.

Examples of equipping an MSI

The following provides an example of equipping an MSI device at a InCell site:
-> equip bsc MSI
Enter the device identification for the MSI/MMS id 1:
Enter the cage number:

Enter the slot number:

Enter the MSI type:

9-142

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping an MSI using the TTY interface

COMMAND ACCEPTED
->
The following provides an example of equipping an MSI device at an M-Cell site:
-> equip <site number> MSI
Enter the MSI identification:

Enter MCU card frame in which the NIU exists:

Enter the NIU slot number:

COMMAND ACCEPTED
->

The following example equips a primary GDP for Enhanced GDP Provisioning:
-> equip 0 MSI
Enter the MSI identifier:
Enter the cage number:

Enter the slot number:

14

Enter the MSI type:

gdp

Enter the MSS ID to the MSC: 1 0

Enter the transcoding capability:

enhanced

COMMAND ACCEPTED
->
The following example equips a secondary GDP for Enhanced GDP Provisioning:
-> equip 0 MSI
Enter the MSI identifier:
Enter the cage number:

Enter the slot number:

14

Enter the MSI type:

gdp

Enter the MSS ID to the MSC: 1 0

COMMAND ACCEPTED
->

68P02901W17-T

9-143
Jan 2010

Equipping an MSI at a BSC or BSS site

Chapter 9: Configuring Devices and Functions

Equipping an MSI at a BSC or BSS site

When equipping an MSI at a BSC or BSS site and the expansion increases the MSC-BSC
trunking enough so that an additional MTL/LCF is required, refer to the following procedures:

Configuring an MTL device on page 9-152.

Configuring an LCF function on page 9-127 (for BSC type 1 and 2).

Displaying CICs using transcoding resources

To display the CICs using the transcoding resources of GDPs or XCDRs, use the
disp_transcoding command. The system responds by displaying information under the
following headings, as appropriate:

MSC MMS id (two values: MSC MSI id, MSC MMS id).

Transcoding Board id (two values).

ABSS Id, if appropriate.

CIC Id.

For example, the following command and system response shows which boards are providing
the transcoding for CICs at a remote transcoder:
disp_transcoding
MSC MMS Transcoding Board
1 0 1 0

ABSS ID CIC IDs

1,2,3,4,5,6,7,8,9,10,11,12,13

14,15
2 0

16,17,18,19,20,21,22,23,24,25

26,27,28,29,30
3 0 3 0

3 0

100,101,102,103,104,105,106,

107,108,109,110,111,112,113,
114
4 0

3 0

115,116,117,118,119,120,121,

122,123,124,125,126,127,128,
129

Other MSI configuration tasks

To modify, delete, or display MSI device, see Methods of configuring individual devices and
functions on page 9-3.
For example, the following command displays details for an enhanced transcoding GDP:
disp_equipment 0 msi 1 0 0

9-144

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Other MSI configuration tasks

For example, the following command modifies the MSC MMS id (msc_mms_id) to 3 for a GDP.
The second identifier defaults to 0:
modify_value 0 msc_mms_id 3 msi 1 0 0
The following command modifies a Basic GDP to a Primary GDP:
modify_value 0 transcoding_capability enhanced msi 1 0 0

NOTE
When modifying transcoding_capability, the CICs need to be unequipped first.
The following command modifies an MSI to a Secondary GDP:
modify_value 0 msi_type GDP msi 1 0 0

68P02901W17-T

9-145
Jan 2010

Configuring Enhanced GDP provisioning

Chapter 9: Configuring Devices and Functions

Configuring Enhanced GDP provisioning

Definition of a GDP
A GDP is a Generic Digital Signal Processor (DSP) Processor board. It is interchangeable
with the XCDR board.
A GDP can provide either Basic or Enhanced transcoding.

Types of transcoding
A user can select the type of transcoding used by a GDP. The transcoding types are:

Basic - Transcoding for GSM Full Rate speech, Enhanced Full Rate speech and phase 2
data services.

Enhanced - Transcoding for future applications, particularly AMR speech coding, in

addition to existing GSM Full Rate speech, Enhanced Full Rate speech and phase 2 data
services.

Enhanced GDP provisioning

Enhanced GDP provisioning:

Supports GDPs that are capable of enhanced transcoding, particularly Adaptive Multirate
(AMR) speech coding, in addition to supporting current transcoding services.

Allows the replacement of MSI boards, which currently terminate the Ater or Abis E1 links,
with GDPs. The GDPs provide transcoding resources (DSPs) in addition to an E1 interface.

Allows GDPs to provide additional enhanced transcoding resources only without making
use of the E1 line interface.

For a full description of this feature, see Technical Description: BSS Implementation
(68P02901W36).

Primary and secondary GDPs

A GDP can be either a primary or Secondary GDP.

9-146

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Prerequisites for enhanced GDP provisioning

A primary GDP provides an E1 interface to the MSC. The GDP may provide basic
transcoding, or be paired with a secondary GDP to provide enhanced transcoding. Primary
GDP can provide enhanced transcoding only.

A secondary GSD in a pair provides DSPs for transcoding for a set of CIC devices routed to
the MSC through the E1 interface of a primary GDP. secondary GDP can provide enhanced
transcoding only.

Prerequisites for enhanced GDP provisioning

For Enhanced GDP Provisioning to be used for new transcoding applications, the following
feature must also be implemented:

Adaptive Multirate (AMR) Speech Coding.

The related MMS must exist before specifying it as an MSC MMS for a secondary GDP or, if
the MSC MMS is the GDP's own MMS, it must be equipped at the same time. A GDP can only
provide an MSC MMS for one secondary GDP.

Enhanced GDP provisioning parameters

Table 9-48 details the Enhanced GDP Provisioning parameters.

Table 9-48

Enhanced GDP Provisioning parameters

OMC-R GUI field

name/BSS parameter
name
Transcoding
Capability
transcoding
_capability
(OMC-R parameter
name:
trans_capability)

Description
Displayed in the Identification grouping of the MSI Detailed View
form. Indicates the transcoding functionality of the GDP board. Valid
values: 0, 1, or 2, where:

0 - Basic transcoding.

1 - Enhanced transcoding.

2 - GDP_2E1 (available when the MSI type is MSI-GDP2 (20))

Default is 0. When set to GDP_2E1 (2), the MSI supports two MMSs.
If the MSI type is not GDP or GDP2, this field is grayed-out in the MSI
Detailed View. This field cannot be changed unless the MSI is locked.
The GDP_2E1 mode is allowed irrespective of whether the AMR, AMR
Enhanced Capacity or GSM HR features are restricted. Also see
Restrictions when changing the MSI type and Enhanced GDP
Provisioning parameters in this section for a list of the restrictions
associated with this parameter. When changing this parameter, the
CICs need to be unequipped first.
MSI ID TO THE MSC
msc_msi_id

Displayed in the Identification grouping of the MSI Detailed View

form.
The MSI identifier of a GDP whose MMS is available for routing the
transcoding circuits of a secondary GDP towards the MSC. Valid
Continued

68P02901W17-T

9-147
Jan 2010

Restrictions: changing MSI type and enhanced GDP provisioning parameters Chapter 9: Configuring Devices and Functions

Table 9-48 Enhanced GDP Provisioning parameters (Continued)

OMC-R GUI field
name/BSS parameter
name

Description
values are 0 to 1
23. Default is: value of the GDP's own MSI identifier. When
creating an MSI of type GDP, this parameter cannot be changed until
Transcoding Capability is changed to Enhanced. The user can then
create a Secondary GDP. The user can create the Secondary GDP by
changing msc_msi_id to a value other than the GDP's own MSI id.
This is only true as long as the value belongs to an existing
Enhanced GDP which is not already paired.
When creating a new MSI of type GDP, while this parameter remains
unchanged from the default value, the user can create either a Basic
GDP or a Primary GDP by selecting Transcoding Capability as either
Basic or Enhanced, respectively. (Primary and Secondary GDPs
provide enhanced Transcoding only). Grayed-out in the MSI Detailed
View, if MSI type is not GDP or GDP2. Cannot be changed unless the
MSI is locked. Also see Restrictions when changing the MSI type
and Enhanced GDP Provisioning parameters in this section for a
list of the restrictions associated with this parameter.

MMS ID TO THE MSC

msc_mms_id

Displayed in the Identification grouping of the MSI Detailed View

form. The MSC MMS is always zero, because MSIs cannot be used
to provide MSC MMSs. Default is: 0 (identity of GDP's own second
MMS identifier), which cannot be changed. Grayed-out in the MSI
Detailed View, if MSI type is not GDP or GDP2. Also see Restrictions
when changing the MSI type and Enhanced GDP Provisioning
parameters in this section for a list of the restrictions associated
with this parameter.

Restrictions: changing MSI type and enhanced GDP

provisioning parameters
Enhanced GDP Provisioning enforces the following restrictions when changing the MSI
parameters.

Unequipping a primary GDP

If a user attempts to unequip a primary GDP, and there is a secondary GDP with which it is
paired, an error message is displayed.

9-148

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

changing MSI type and enhanced GDP provisioning parameters

Restrictions:

Changing MSI type from GDP

If the MSI type is GDP, a user can change the MSI type to MSI, XCDR or GDP2. However,
it can only be changed to an MSI if it is a secondary GDP/GDP2 and to an XCDR if it is
a basic GDP/GDP2

Before a user can change the MSI type from GDP to XCDR, trans_capability must be
changed to Basic.

If a user changes MSI type from GDP to XCDR, msc_msi_id, msc_mms_id and
trans_capability are grayed-out.

In reverse modification of MSI type from GDP to MSI, the MSI's second MMS (MMS
X,1, 0) is equipped.

If a user attempts to change Basic GDP to anything other than XCDR or Primary GDP, an
error message is displayed.

A user can only change MSI type from GDP to MSI, only when GDP is Secondary GDP, that
is, when msc_msi_id is other than GDP's own MSI id and trans_capability is enhanced.

If user changes MSI type from GDP to MSI, msc_msi_id, msc_mms_id and
trans_capability are grayed-out.

Changing MSI type from or to MSI-GDP2

An MSI type: MSI-GDP2 can be modified to either an MSI-XDCR, MSI-GDP, or MSI-MSI.

If the MSI type is changed from MSI-GDP2 to MSI-XCDR, trans_capability, msc_msi_id

and msc_mms_id are set to NULL and are grayed-out in the MSI Detailed View.

If the MSI type is changed from MSI-XCDR to MSI-GDP2, trans_capability, msc_msi_id

and msc_mms_id are set to their default values and cannot be modified in the same step.

If the MSI type is changed from MSI-GDP2 to MSI-GDP, or from MSI-GDP to MSI-GDP2,
trans_capability, msc_msi_id and msc_mms_id cannot be modified in the same step.

Changing MSI type from XCDR

If the MSI type is XCDR, a user can only change to Basic GDP.

If the MSI type is XCDR and a user changes the type to GDP, msc_msi_id and
trans_capability fields become available. msc_msi_id defaults to the GDP's own MSD
ID and trans_capability defaults to Basic.

68P02901W17-T

9-149
Jan 2010

Restrictions: changing MSI type and enhanced GDP provisioning parameters Chapter 9: Configuring Devices and Functions

Changing MSI type from MSI

If the MSI type is MSI and a user changes the type to GDP, msc_msi_id and
trans_capability are selectable, msc_msi_id is cleared and the user is forced to enter a
value other than the GDP's own MSI ID.

If a user changes the MSI type from MSI to GDP, trans_capability is set to Enhanced.

If a user attempts to change from MSI to anything other than Secondary GDP, an error
message is displayed.

If MSI type is changed from MSI to GDP, the MSI's second MMS (MMS X,1, 0) is
unequipped.

Changing trans_capability

A user can only change trans_capability from Enhanced to Basic, if msc_msi_id is GDP's
own MSI id (that is if it is a primary GDP).

If a user attempts to change trans_capability from Enhanced to Basic, and there is a

Secondary GDP with which it is paired, an error message is displayed.

If a user attempts to modify trans_capability and there are CICs equipped to the GDP, an
error message is displayed.

If trans_capability is changed from Basic (0) to Enhanced (1) at an MSI-GDP2 type MSI,
msc_msi_id cannot be modified.

The trans_capability of an MSI-GDP2 type MSI can be modified from Enhanced (1) to
Basic (0), if msc_msi_id is already saved to the RDN value of the MSI (Primary GDP2).

If trans_capability is changed from Basic (0) to GDP_2E1 (2) at an MSI-GDP2 type MSI,
msc_msi_id and msc_mms_id cannot be modified.

The trans_capability of an MSI-GDP2 type MSI can be changed from GDP_2E1 (2) to
Basic (0), if msc_msi_id is already saved to the RDN value of the MSI and msc_mms_id is
saved to value 0 (Primary GDP2).

For an MSI type MSI-GDP2, if trans_capability is set to GDP_2E1 (2), msc_mms_id is

always set to a value of 0, and msc_msi_id is always set to the RDN value.

Changing from Primary GDP

9-150

If a user attempts to change Primary GDP to anything other than Basic GDP or Secondary
GDP, an error message is displayed.

A user can only change from Primary GDP to Secondary GDP, if msc_msi_id is modified
to anything other than GDP's own MSI only when trans_capability is Enhanced and
msc_msi_id is GDP's own MSI ID.

If the user attempts to change a Primary GDP to a Secondary GDP when the Primary GDP
is already paired with another Secondary GDP, an error message is displayed.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

changing MSI type and enhanced GDP provisioning parameters

Restrictions:

Changing from Secondary GDP

To create a Secondary GDP, the Primary GDP must exist before specifying it as a
mcs_msi_id for a Secondary GDP.

A user can only change from Secondary GDP to Primary GDP by modifying msc_msi_id to
GDP's own MSI ID only when trans_capability is Enhanced and msc_msi_id is anything
other than GDP's own MSI ID.

If a user attempts to change Secondary GDP to anything other than Primary GDP or MSI
or another Secondary GDP, an error message is displayed.

A user can change from one Secondary GDP to another Secondary GDP by modifying
msc_msi_id of Secondary GDP to allow pairing with a different Primary GDP.

Changing msc_msi_id

If a user attempts to specify msc_msi_id of a GDP if the MMS corresponding to the

specified msc_msi_id belongs to a non-GDP, an error message is displayed.

If a user attempts to specify msc_msi_id of a GDP if the MMS corresponding to the

specified msc_msi_id belongs to a Secondary GDP, a warning is displayed indicating that
the CICs will be out of service.

If a user attempts to specify msc_msi_id of a GDP if the MMS corresponding to the

specified msc_msi_id belongs to a Basic GDP, an error message is displayed. A Secondary
GDP can only be paired with a Primary GDP.

If a user attempts to specify msc_msi_id for a GDP, and the specified MMS (that is
msc_msi_id, 0) belongs to a Primary GDP with which it is paired, an error message is
displayed. Two Secondary GDPs cannot be paired with the same Primary GDP.

68P02901W17-T

9-151
Jan 2010

Configuring an MTL device

Chapter 9: Configuring Devices and Functions

Configuring an MTL device

MTL hierarchy requirements

When equipping an MSI device at a BSC, the Message Transfer Link (MTL) (A-Interface) can
be added for traffic considerations. The MTL is the link between the MSC and the BSC over
which MTP protocol is run. An MTL only exists at site 0 (BSC).
When equipping an MTL device, the link must be passed to the MSC database. Refer to the
procedures provided by the MSC vendor for more information on adding links to the MSC.

Creating an MTL using the OMC-R GUI

To create an instance of an MTL device, proceed as follows:

Procedure 9-41

Create an instance of an MTL device

Navigate to and select the MTL class button in the Navigation Tree
(BSS BSS instance SITE SITE instance (SITE 0 only) Logical
Links MTL). If necessary, see Navigating to a network object class
or instance on page 1-28 for further details.

Select Edit Create from the menu bar.

Result: The OMC-R displays the MTL Detailed View form.

Enter all required information in this form. See MTL Detailed View
fields for details.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

MTL Detailed View fields

The following sections list and briefly describe the parameter fields in the MTL Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these parameters.

9-152

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping an MTL using the TTY interface

Identification grouping
Table 9-49 describes the fields in the Identification grouping of the MTL Detailed View.

Table 9-49 MTL Detailed View fields - Identification grouping

Field name

Values

Brief description

Mandatory
or Optional?

MSI Identifier

The MSI device on which the logical

link resides.

0 - 123.

Mandatory.

MMS Identifier

The MMS device on which the logical

link resides.

0 or 1.

Mandatory.

MMS Timeslot
Identifier

The MMS timeslot on which the

logical link resides.

1 - 31 (for E1),

Mandatory.

RDN Class

See description in Table 4-1.

Default is the
device class.

RDN Instance

MTL identifier, see description in

Table 3-1.

0 - 15.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

site. Click to display the parent SITE
Detailed View.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Equipping an MTL using the TTY interface

To equip an MTL using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.
The following is an example of equipping an MTL:
-> equip bsc MTL
Enter the device identification for this MTL: 1
Enter the first MMS description for this device:

68P02901W17-T

9-153
Jan 2010

Equipping an MTL using the TTY interface

Chapter 9: Configuring Devices and Functions

Enter the second MMS description for this device:

Enter timeslot on MMS where this device appears:

0
19

COMMAND ACCEPTED
->

9-154

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Modifying MTL loadsharing granularity

Modifying MTL loadsharing granularity

Overview of MTL loadsharing granularity

The loadsharing of traffic on the Message Transfer Links (MTLs) in the uplink direction from the
BSS to the MSC can be specified.
However, loadsharing from the MSC to the BSC is based on the routing function implemented at
the MSC, and cannot be modified.
The granularity of the loadsharing can be set to 16 (regular granularity) or 64 (enhanced
granularity) virtual circuits. The greater the number of circuits, the more even the traffic
distribution is across the MTLs.

NOTE
MTL loadsharing granularity can be changed at any time, but the change does not
take effect until all the MTLs are locked. If the element is changed in SYSGEN mode,
the change immediately takes effect.

Detailed description of BSS routing function

Call signaling traffic can be distributed over 16 or 64 virtual circuits.
The virtual circuits are evenly spread over active MTLs. The message routing label consists of
the originating point code field (OPC), the destination point code field (DPC), and the signaling
link selection field (SLS). A signaling point is required to route all message traffic based on the
three fields in the routing label. The SLS is a 4-bit field used for loadsharing between multiple
links in the same linkset. The typical signaling point always routes messages with the same
routing label over the same physical link. routing messages in this way ensures that messages
are delivered in order. For a given originating point code (OPC) and destination point code
(DPC), the SLS field is the equivalent of a virtual circuit identifier.
When 64 virtual circuits are used to distribute signaling traffic originating at the BSS, a router
index in the range of 0 - 63 is randomly assigned to each call block when a call is established.
Random assignment results in even distribution of routing indices to call blocks. The router
index identifies the virtual circuit for all signaling messages associated with the call block. The
64 virtual circuits are evenly spread over the active MTLs. This routing function is compliant
with the SS7 protocol because the BSS still routes all messaging associated with a given call
over the same physical MTL.
Although the SLS is not used to perform routing at the BSS, the SLS field is completed. The
SLS may be used for message routing by the MSC or some other signaling point in the SS7
network. The SLS field of the routing label is filled in with the lower 4 bits of the router index.
This technique guarantees that all messages associated with a call block have the same SLS
field and it results in an even distribution of SLS values to routing labels. Messages without a
connection are assigned a randomly generated router index. The SLS field is completed using
the same technique used for connection-oriented messages.

68P02901W17-T

9-155
Jan 2010

Methods of modifying MTL loadsharing granularity

Chapter 9: Configuring Devices and Functions

Methods of modifying MTL loadsharing granularity

The MTL loadsharing granularity can be set using:

The OMC-R GUI BSS Detailed View.

TTY interface and the mtl_loadshare_granularity parameter.

MTL Loadshare Granularity field

Table 9-50 describes the MTL Loadshare Granularity parameter.

Table 9-50 MTL Loadshare Granularity parameter

OMC-R GUI field name/BSS
parameter name

Description

MTL Loadshare Granularity

Displayed in the General grouping of the BSS Detailed View.
mtl_loadshare_granularity Valid values: 0 or 1, where: 16 Virtual Circuits (0) (regular
granularity). 64 Virtual Circuits (1) (enhanced granularity).
Default is 16 Virtual Circuits (0).

Modifying MTL loadsharing granularity using the OMC-R GUI

To modify MTL loadsharing granularity, follow these steps:

Procedure 9-42 Modify MTL loadsharing granularity

1

Navigate to and select the BSS instance button in the Navigation Tree
(BSS BSS instance). If necessary, see Navigating to a network object
class or instance on page 1-28 for further details.

Select Edit Detailed View from the menu bar.

Result: The OMC-R displays the BSS Detailed View form in Monitor
mode.

Select Edit Edit.

Change the MTL Loadshare Granularity field in the General grouping

to the required value. See Table 9-50 for details.
Result: The OMC-R displays the following message: This change
will not take effect until all MTLs are in a Locked state.

Save and close the Detailed View.

Modifying MTL loadsharing granularity using the TTY interface

To modify the MTL loadsharing granularity using the TTY interface, use the following command:
chg_element mtl_loadshare_granularity <value> 0

9-156

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying MTL loadsharing granularity using the TTY interface

For a detailed description of the mtl_loadshare_granularity parameter and the chg_element

command, see Technical Description: BSS Command Reference (68P02901W23).

Displaying MTL loadsharing granularity using the TTY interface

To display the MTL loadsharing granularity using the TTY interface, use the following command:
disp_element mtl_loadshare_granularity 0
The system responds with the following information, for example:
MTL_LOADSHARE_GRANULARITY = 1
For a detailed description of the mtl_loadshare_granularity parameter and the disp_element
command, see Technical Description: BSS Command Reference (68P02901W23).

68P02901W17-T

9-157
Jan 2010

Configuring an OMF function

Chapter 9: Configuring Devices and Functions

Configuring an OMF function

Prerequisites to the configuring of an OMF function

An Operations and Maintenance Facility (OMF) can only be equipped at BSC (SITE 0), or a BSS
where the BSC type is 2.
Equip GPROCs before adding OMF functions.

Creating an OMF device instance using the OMC-R GUI

To create an instance of an OMF, proceed as follows:

Procedure 9-43 Create an instance of an OMF

1

Navigate to and select the OMF class button in the Navigation Tree
(BSS BSS instance SITE SITE instance (SITE 0 only) Software
Functions OMF). If necessary, see Navigating to a network object
class or instance on page 1-28 for further details.

Select Edit Create from the menu bar.

Result: The OMC-R displays the OMF Detailed View form.

Enter all required information in this form. See OMF Detailed View
fields for further details.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

OMF Detailed View fields

The following sections list and briefly describe the parameter fields in the OMF Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these BSS parameters.

9-158

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping an OMF function using the TTY interface

Identification grouping
Table 9-51 describes the fields in the Identification grouping of the OMF Detailed View.

Table 9-51 OMF Detailed View fields - Identification grouping

Field name

Values

Brief description

Mandatory or
Optional?

RDN Class

See description in Table 4-1.

Default is
device class.

RDN instance

See description in Table 3-1.

0 only.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

site. Click to display the parent SITE
Detailed View.

Controlled OMLs

OMLs controlled by this OMF. Valid

only at SITE 0.

0 - 3.

Optional.

Controlled XBLs

XBLs controlled by this OMF. Valid

only at SITE 0.

0 - 31.

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Equipping an OMF function using the TTY interface

To equip an OMF using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.
For example, the following command equips an OMF at the BSC:
equip 0 OMF
No parameter prompts are displayed when equipping an OMF.

68P02901W17-T

9-159
Jan 2010

Configuring an OML device

Chapter 9: Configuring Devices and Functions

Configuring an OML device

OML hierarchy requirements

When equipping an MSI device at a BSC, there may also be a requirement to equip an Operation
and Maintenance Link (OML). The first two OML devices are active/standby defaults.
An OML is contained only within an RXCDR or site 0 (BSC) at a BSS.

Creating an OML using the OMC-R GUI

To create an instance of an OML device using the OMC-R GUI, proceed as follows:

Procedure 9-44 Create an instance of an OML device

1

Navigate to and select the OML class button in the Navigation Tree
(BSS BSS instance SITE SITE instance (SITE 0 only) Logical
Links OML). If necessary, see Navigating to a network object class
or instance on page 1-28 for further details.

Select Edit Create from the menu bar.

Result: The OMC-R displays the OML Detailed View form.

Enter all required information in this form. See OML Detailed View
fields for further details.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

OML Detailed View fields

The following sections list and briefly describe the parameter fields in the OML Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these BSS parameters.

9-160

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping an OML device using the TTY interface

Identification grouping
Table 9-52 describes the fields in the Identification grouping of the OML Detailed View.

Table 9-52 OML Detailed View fields - Identification grouping

Field name

Brief description

Values

Mandatory or
Optional?

MSI Identifier

The MSI related to this OML.

Mandatory.

MMS Identifier

The MMS related to this OML.

Mandatory.

MMS Timeslot
Identifier

The MMS timeslot related to this

OML.

Mandatory.

RDN Class

See description in Table 4-1.

Default is
device class.

RDN instance

See description in Table 3-1.

0 - 3.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed View

Displays the name of the parent

site. Click to display the parent SITE
Detailed View.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Equipping an OML device using the TTY interface

To equip an OML using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.

68P02901W17-T

9-161
Jan 2010

Configuring a path device

Chapter 9: Configuring Devices and Functions

Configuring a path device

Definition of a path
A path is a unique identification of a route through MSI/MMS links over 2.048 Mbit/s links
and intervening BTS sites, to the site with which the RTF or RSL is associated. The site with
which the RTF or RSL is associated is referred to as the terminating site for the path, as shown
in Figure 9-20.

Figure 9-20

Network showing paths and terminating site

ti-GSM-Networkshowingpathsandterminatingsite-00827-ai-sw

Paths are required at all BTS sites. A path can include a maximum of ten BTSs.
A path device must always be equipped before equipping a receive/transmit (RTF) function or a
Radio Signaling Link (RSL) device.
When RTF functions are equipped, specify a primary path. Once equipped, this path cannot be
changed without first unequipping the RTF. For this reason, future network changes should be
considered before equipping RTFs. The optional secondary path can be specified when the RTF
is first equipped. The secondary path can be added or changed at a later time.

9-162

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

path devices for a DYNET

An important concept relating to RTF paths is that whenever there are two paths equipped,
the shortest path (fewer intervening BTS sites) is used. For example, if the secondary path is
the shorter after being added or changed, it is chosen as the primary path. When paths are
equal in length, the primary path is selected. When the selected path is not available, the
RTF is switched over to the alternate path. The RTF switches back to the shortest path when
availability is restored.

path devices for a DYNET

When a DYNET is equipped for BSC-BTS dynamic allocation, the OMC-R automatically creates
the path devices and assigns path identifiers in the range 0 - 5. These values indicate that
the path has been automatically equipped.
When BSC-BTS dynamic allocation is enabled at the corresponding site, valid path identifiers
are in the range 6 - 9. Identifiers 0 to 5 are reserved for automatic equipage of paths for Dynets.
When BSC-BTS dynamic allocation is disabled at the corresponding site, valid path identifiers
are in the range 0 - 9.
For DYNETs configured in a spoke or daisy chain configuration, one path device is automatically
equipped. For closed loop, daisy chain loop configuration, two path devices are automatically
equipped.
See Dynamic allocation of BSC-BTS backing resources (DYNET) for further details.

path configuration topics

These path configuration tasks are detailed in the following sections:

Creating a path on page 9-164.

Deleting a path on page 9-170.

Extending and reparenting a path on page 9-172.

Checking path connectivity on page 9-174.

Modifying a path
Once a path has been created, it cannot be modified.

68P02901W17-T

9-163
Jan 2010

Creating a path

Chapter 9: Configuring Devices and Functions

Creating a path

Methods of creating a path

A path can be created using any of the following methods:

Using the TTY interface and the equip command to create a path online. This is the
recommended method, and allows the user to verify that the MMSs used are free.

Using Path Configure OMC-R GUI menu option, see Configuring a path using Path
Configure menu option on page 11-73 in Chapter 11 Network Expansion.

Using the OMC-R GUI path Detailed View form.

As part of a new BSS database build.

Prerequisites for creating a path

Before creating a path, install the physical SITEs and 2 Mbit/s links. Enter them n the CM
database.

NOTE
The SITE does not need to be out of service to create a path.

Creating a path using the TTY interface (recommended method)

To create and configure a path using the TTY interface, proceed as follows:

Procedure 9-45 Create and configure a path using TTY

1

Identify the free MMSs at the BSC, the terminating site and, if required,
the upstream and downstream MMSs in the intermediary sites. This
can be done using the Network Operator System Engineering Drawings
for customer specific details of equipment interconnections, or by
using the MMI commands disp_link_usage or disp_mms_ts_usage.

Create the path using the equip command:

equip <location> PATH
Refer to: Technical Description: BSS Command Reference
(68P02901W23) for complete information on the equip command.
Continued

9-164

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Creating a path using the TTY interface (recommended method)

Procedure 9-45 Create and configure a path using TTY (Continued)

3

At the prompts, enter the appropriate configuration information

according to the BTS type:

InCell BTS the PATH intended for the first default RSL must
terminate at MMS 0 of the MSI equipped in cage 15, slot 16. The
PATH intended for the second default RSL must terminate as:
MMS 1 of the MSI equipped in cage 15, slot 16 for a BTS
with a single MSI.
MMS 0 of the MSI equipped in cage 15, slot 14 for a BTS
with a single cage.
MMS 0 of the MSI equipped in cage 14, slot 16 for a BTS
with two or more cages.

Horizon II macro the PATH intended for the first default RSL must
terminate on Card Frame A, NIU2 0, Span 0, Timeslot 1. The
PATH intended for the remainder RSL must terminate as follows:
Card frame A, NIU2 0, Span 1, Timeslot 2.
Card frame A, NIU2 0, Span 2, Timeslot 2.

Non Horizon II macro the PATH intended for the first default RSL
must terminate on Card Frame A, NIU 0, Span 0, Timeslot 1. The
PATH intended for the remainder RSL must terminate as follows:
Card frame A, NIU 0, Span 1, Timeslot 2.
Card frame B, NIU 0, Span 0, Timeslot 2.

Unlock the path using the unlock command.

Add the RSLs to the PATH. Motorola recommends that RSL 0 is

assigned to the first default RSL, and RSL 1 to the second default. The
connection to be made are dependant on the BTS type:

InCell BTS the default RSLs use specific timeslots of the Abis link,
depending on cage, as shown in Table 9-53

Horizon II macro Site use specific timeslots, the default

connections depending on the card frame as shown in Table 9-54

Non Horizon II macro Site use default specific timeslots, the

default connections depending on the card frame as shown in
Table 9-55

Unlock the RSL using the unlock command.

Add the RTFs to the primary path as part of the equip rtf command.
Result: The primary path assignment cannot be changed or deleted.
Continued

68P02901W17-T

9-165
Jan 2010

Creating a path using the TTY interface (recommended method)

Chapter 9: Configuring Devices and Functions

Procedure 9-45 Create and configure a path using TTY (Continued)

8

If required, add the RTFs at the secondary path at a later time using
add_rtf_path. If the added secondary path is shorter than the primary
path, the secondary path is used for the RTF.

Verify that the paths have been correctly assigned by entering:

disp_traffic <location> <unique PATH identifier>

10

Verify that the timeslots of the path on which the RTFs are configured
is processing calls, using the disp_rtf_chan and disp_cell_status
TTY commands.

11

Check the 2 Mbit/s link is operating correctly by opening the MMS

Detailed View and selecting Options - Circuit Status.

Table 9-53 Abis link cage timeslots

Cage 15
MSI slot number

MMS group

Abis timeslot used

16

16

14

Cage 14
MSI slot number

MMS group

Abis timeslot used

16

Table 9-54 Default RSLs - Timeslots and Card frame for Horizon II macro Site
Card frame

NIU2 Number

Span

Timeslot Used

Table 9-55

Card frame

NIU Number

Span

Timeslot Used

9-166

Default RSLs - Timeslots and Card frame for non Horizon II macro Site

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating a path device using the OMC-R GUI

Creating a path device using the OMC-R GUI

NOTE
The recommended Motorola method to add a path online is using the equip TTY
command.
To create an instance of a path device using the OMC-R GUI, follow these steps:

Procedure 9-46 Create an instance of a path device

1

Navigate to and select the PATH class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Logical Links
PATH). If necessary, see Navigating to a network object class or
instance on page 1-28 for further details.
Result: The class button changes color.

Select Edit Create from the menu bar.

Result: The OMC-R displays the PATH Detailed View form.

Enter all required information in this form. See PATH Detailed View
fields for details of the fields.

Create and close the Detailed View. See Creating a network object
using the OMC-R GUI on page 1-32 for further details.

PATH Detailed View fields

The following sections list and briefly describe the parameter fields in the PATH Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.
Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these BSS parameters.

68P02901W17-T

9-167
Jan 2010

PATH Detailed View fields

Chapter 9: Configuring Devices and Functions

Identification grouping
Table 9-56 describes the fields in the Identification grouping of the PATH Detailed View.

Table 9-56 PATH Detailed View fields - Identification grouping

Field name

Mandatory
or Optional?

Values

Brief description

RDN Class

See description in Table 4-1.

Default is device
class.

Optional.

RDN Instance

Identifier assigned to the path. This

number is unique for this path among
the other paths at this terminating
site. Also see description in Table 3-1.

0 - 9.
6 - 9, if the
terminating BTS
uses dynamic
allocations.
Default is 0.

Optional.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent

site. Click to display the parent SITE
Detailed View.

Additional Information
Use the Additional Information window to input any notes relating to this device or function.
Where additional notes are not required, close this field by clicking the toggle button next to
the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Path information grouping

Table 9-57 describes the fields in the Path information grouping of the PATH Detailed View.

Table 9-57 PATH Detailed View fields - Path information grouping

Field name/OMC-R
parameter name

Mandatory or
Optional?

Values

Brief description

Number of sites in
path
numinsequence

Indicates the number of

links, which also indicates
which link attributes are
valid for this instance.

1 - 11.
When a value of 2 or more
is specified, additional
rows are added for each
site.

Mandatory.

BSC MSI identifier

Id of the MSI at the BSC used

to start the path.

0 - 95.

Mandatory.

BSC MMS
identifier

MMS Id of the MSI at the

BSC.

0 or 1.

Mandatory.

Continued

9-168

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

PATH Detailed View fields

Table 9-57 PATH Detailed View fields - Path information grouping (Continued)
Field name/OMC-R
parameter name

Values

Brief description

Mandatory or
Optional?

SITE Id

Site id on the path. The

first site entered is the one
nearest to the BSC. The field
(and prompt in TTY input)
is repeated until the site
furthest from the BSC on
the path (terminating site) is
entered.

1 - 100, or ts_switch.

Mandatory.

Upstream MSI
identifier

Number of the MSI at the

site which looks towards the
BSC.

0
0
0
0
0
0
0
0
0

Mandatory.

Upstream MMS
identifier

MMS of the MSI above.

0 or 1.

Mandatory.

Downstream MSI
identifier

Number of the MSI at the

BSC which looks towards the
site.

0
0
0
0
0
0
0
0
0

Mandatory.

Downstream MMS
identifier

MMS of the MSI above.

0 or 1.

TS Switch

(Displayed in PATH Detailed

View only).
Indicates a TS switching site
(254).

68P02901W17-T

- 95 (BSC).
- 9 (BTS InCell).
- 3 (M-Cell6).
- 1 (M-Cell2).
(M-Cellmicro).
(M-Cellcity).
- 3 (Horizonmacro).
(Horizonmicro).
(Horizoncompact).

- 95 (BSC).
- 9 (BTS InCell).
- 3 (M-Cell6).
- 1 (M-Cell2).
(M-Cellmicro).
(M-Cellcity).
- 3 (Horizonmacro).
(Horizonmicro).
(Horizoncompact).

Mandatory.

9-169
Jan 2010

Deleting a path

Chapter 9: Configuring Devices and Functions

Deleting a path

Methods of deleting a path

A path can be deleted using any of the following methods:

Using the TTY interface (recommended method).

Using the OMC-R GUI Path Configure menu option, see Deleting a path using the Path
Configure menu option on page 11-81 in Chapter 11 Network Expansion.

Using OMC-R GUI Navigation Tree. Refer to the general deletion procedure in Deleting a
network object using the OMC-R GUI for details.

Prerequisites to deleting a path

Before deleting a path ensure that:

All RTFs, which refer to the path to be deleted, are deleted. For example, if an RTF has the
path to be deleted named in its First Path Id field, delete that RTF before you delete the
path. However, if an RTF has the path named in its Second Path Id field, set the Second
Path Id field to null before deleting the path.

Delete (or unequip) any RSLs or RTFs associated with the path.

NOTE
The site does not need to be out of service to delete a path. However, removing
a primary path takes the site out of service.

Deleting a path online using the TTY interface (recommended

method)
Where possible, paths should be removed as part of a new BSS database build.

9-170

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

a path online using the TTY interface (recommended method)

Deleting

To delete a path online using the TTY interface, proceed as follows:

Procedure 9-47

Delete a path online using TTY

Determine the RSL and RTF equipage for the path by entering:
disp_traffic <location> <unique PATH identifier>

Lock the RSLs by entering:

lock_device 0 RSL <1st device id> <2nd device id>

Lock the path by entering:

lock_device 0 PATH <1st device id> <2nd device id>

Remove the RTFs from the path by using del_rtf_path. The primary
path assignment for an RTF cannot be deleted without first removing
neighbor/sources from the cell assigned to the RTF.

If required, unequip the RTF by entering:

unequip <location> RTF <1st device id> <2nd device id>

NOTE
This command also removes frequencies from operation.

68P02901W17-T

If required, unequip the RSL by entering:

unequip 0 RSL <1st device id> <2nd device id>

Unequip the path by entering.

unequip 0 PATH <1st device id> <2nd device id>

9-171
Jan 2010

Extending and reparenting a path

Chapter 9: Configuring Devices and Functions

Extending and reparenting a path

Extending an existing path to a new site

To extend an existing path to a new site, see Configuring a path using Path Configure menu
option on page 11-73 in Chapter 11 Network Expansion.
A path can also be extended using the copy_path command, see Extending an existing path to a
new site using the TTY interface on page 7-40 for further details.

Reparenting a path online (recommended method)

Reparenting a path involves one of the following:

Removing/adding a site in the chain between the terminating site and the BSC.

Rerouting the path through different MMS(s) for the same sites.

Motorola recommends reparenting paths as part of a new BSS database build. This is because a
reparent is effectively a delete/add, so that if the primary path is involved, an outage cannot
be avoided. The procedure outlined here, while still involving an outage, is the fastest way to
reparent online. The procedure uses a dummy path, avoiding the need to remove the RTFs
(Cells) sources/neighbors.

NOTE
The site does not need to be taken out of service to reparent a path. However,
reparenting a primary path takes the site out of service unless a secondary path
can be brought into service for the duration of the reparent. The physical sites and
2 Mbit/s links in the newly reconfigured chain must be installed first, and must be
entered in the CM database
To reparent a path online, proceed as follows:

Procedure 9-48 Reparenting a path online using TTY

1

Add a dummy path using dummy MMSs at the site and the BSC.

Add the RTFs of the path to be reparented to the dummy path using
the add_rtf_path command.
Continued

9-172

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reparenting a path online (recommended method)

Procedure 9-48 Reparenting a path online using TTY (Continued)

3

Before deleting the path to be reparented, ensure MMSs are in

service at the BSC and the terminating site. If required, ensure
that the upstream and downstream MMSs in the intermediary sites
used in the new path configuration are also in service (use Network
Operator System Engineering Drawings and/or the disp_link_usage
or disp_mms_ts_usage MMI commands to ensure that the MMSs are
free, then use the state command to check the MMSs are in service).

Delete the path to be reparented. Refer to Deleting a path on page

9-170.

NOTE
The prompt will not ask to remove the RTFs
sources/neighbors as part of the del_rtf_path, if there is
secondary path in service or a dummy path described in
step 1 and step 2.
5

Add the path again, using the newly required configuration. Refer to
Creating a path on page 9-164.

Verify that the new path is in service.

Remove the dummy path if used as part of this procedure.

NOTE
Only if there is no secondary path for the RTFs, step 1, step 2 and step 7 (detailing
use of a dummy path) are required.

68P02901W17-T

9-173
Jan 2010

Checking path connectivity

Chapter 9: Configuring Devices and Functions

Checking path connectivity

Overview to path connectivity

NOTE

Customers extracting hopping and path information on a regular basis (part of

data harvest nightly, for example), should contact Motorola OMC-R Customer
Support for further information.

Motorola recommends using the Generic Lookup Utility (GLU). GLU is an

optional tool, available from Motorola, capable of extracting configuration
information on connectivity.

This section describes the following methods of checking path connectivity:

Checking a single path using the GUI.

Checking multiple paths using the command line.

Single site or NE path check using cmutil.

Multiple path checks at OMC-R using cmutil.

See Chapter 15 cmutil for further details.

Checking a single path using the OMC-R GUI

To check a single path using the GUI:

Procedure 9-49 Check the single path

1

Open a Path Detailed View from the Navigation Tree.

Check the connectivity settings (under Path Information grouping) to

the MMS identification settings for the site(s) in the path.

Checking multiple paths using cmutil

All the data for a path can be viewed from a Detailed View. However, some of the data of
each path object is not stored in its generic table in the MIB DBMS (pathtable2). This makes
extraction through SQL queries difficult. The only way to extract full information for multiple
paths objects from the CM MIB is by using cmutil, see Chapter 15 cmutil for further information.

9-174

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking single site or NE path using cmutil

Checking single site or NE path using cmutil

To check path connectivity of a single site or NE using cmutil, see Chapter 15 cmutil.

Checking multiple paths in the OMC-R using cmutil

To check path connectivity throughout the OMC-R using cmutil, see Chapter 15 cmutil.

68P02901W17-T

9-175
Jan 2010

Configuring an RSL device

Chapter 9: Configuring Devices and Functions

Configuring an RSL device

Definition of an RSL device

The RSL carries the control and signaling information for the site. An RSL can only be contained
within the remote BTS in which it terminates.
When equipping an MSI for initial land circuits, there may be a requirement to equip a Radio
Signaling Link (RSL) device.
At least one RSL must be equipped per site and two for redundancy.
Up to eight RSLs may be equipped for heavier signaling capacity.
An RSL is not required for every MSI, or for every 2 Mbit/s link.

RSL congestion control

Congestion control can be configured for RSLs at a BSS, see RSL Congestion Control on page
2-170 for further details.

RSL timeslot restrictions

Default RSLs use specific timeslots of the Abis link. See Table 9-53.

Impact of BSC-BTS dynamic allocation on RTFs/RSLs

If BSC-BTSdynamic allocation is enabled for the site containing the selected RSL, the following
parameter fields in the RTF Detailed View window are grayed-out and cannot be modified
by an operator:

Associated RSL for First Path Id (BSS Naming convention: rsl_id1).

Associated RSL for Second Path Id (BSS Naming convention: rsl_id2).

Likewise, the system does not prompt for these parameters in the equip command.

RSLs at a Horizon II macro BTS

Up to six RSLs can be equipped at an MSI of type NIU2 at a Horizon II macro BTS.
Up to four RSLs can be equipped on a single MMS at a Horizon II macro BTS.

9-176

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Methods of configuring an RSL

Methods of configuring an RSL

An RSL can be configured using any of the following methods:

OMC-R GUI Navigation Tree and Detailed Views.

TTY interface and BSS commands.

The path configure facility, see Configuring a path using Path Configure menu option
on page 11-73.

Creating an RSL using the OMC-R GUI

To create an instance of an RSL device, proceed as follows:

Procedure 9-50

Create an RSL device

Navigate to and select the RSL class button in the Navigation Tree
(BSS BSS instance SITE SITE instance Logical Links RSL).
If necessary, see Navigating to a network object class or instance on
page 1-28 for further details.

Select Edit Create from the menu bar. The OMC-R displays the RSL
Detailed View.

Enter all required information in this form. See RSL Detailed View
fields for further details.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

NOTE
Device information is stored in flat files when creating an RSL with timeslot(s). If an
unexpected exit from the GUI occurs, this file can be used to access the reserved
timeslot(s) information on the mmi prompt using the chg_ts_usage command. See
Using flat files on page 11-94 for more details.

RSL Detailed View fields

The following sections list and briefly describe the parameter fields in the RSL Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

68P02901W17-T

9-177
Jan 2010

RSL Detailed View fields

Chapter 9: Configuring Devices and Functions

Also see Technical Description: BSS Command Reference (68P02901W23) for further details
of these BSS parameters.

Identification grouping
Table 9-58 describes the fields in the Identification grouping of the RSL Detailed View.

Table 9-58 RSL Detailed View fields - Identification grouping

Field name

Values

Brief description

RDN Class

See description in Table 4-1.

Default is the
device class.

RDN Instance

See description in Table 3-1.

0 - 7.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detailed
View

Displays the name of the parent site.

Click to display the parent SITE Detailed
View.

PATH Identifier

The path on which the RSL resides.

0 - 9.

Mandatory
or Optional?

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this device. Where
additional notes are not required, close this field by clicking the toggle button next to the
Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

LapD Information grouping

Table 9-59 describes the fields in the LapD Information grouping of the RSL Detailed View.

Table 9-59 RSL Detailed View fields - LapD Information grouping

Field name

9-178

Brief description

Values

Mandatory or
Optional?

LapD T200 Timer

Used to time the acknowledgments

of a transmitted frame. On timeout a
counter is incremented. If the value if
this counter equals the value in LAPD
N200, then an error has occurred.

1400 - 5000 ms
(in multiples of
50).
Default: 2500.

Mandatory.

LapD N200 value

Indicates the maximum number of

retransmissions of a frame.

1 - 5.
Default: 3.

Mandatory.

LAPD K Frame
Window

Indicates the maximum number of

unacknowledged information frames
(I-frames).

1 - 10.
Default: 7.

Mandatory.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping an RSL using the TTY interface

MMS Timeslots grouping

The MMS Timeslots grouping is only viewable when creating or re-assigning an RSL using the
Path Configure menu option (see Creating an RSL at a site using the Path Configure menu
option on page 11-93) on a path containing one or more TS Switches. The fields in this grouping
are not maintained outside a Path Configure operation, and are only used by the OMC-R.
Table 9-60 describes the fields in the MMS Timeslots grouping of the RSL Detailed View.

Table 9-60 RSL Detailed View fields - MMS Timeslots grouping

Values

Mandatory or
Optional?

Field name

Brief description

Upstream TS MMS
(OMC only name:
path_upst_ts)

The timeslot number on which the

RSL is equipped, in the upstream
MMS directly connected to a TS
switch.

0 - 31.

Optional.

DownStream TS
MMS
(OMC only name:
path_downst_ts)

The timeslot number on which the

RSL is equipped, in the downstream
MMS directly connected to a TS
switch.

0 - 31.

Optional.

Equipping an RSL using the TTY interface

To equip an RSL using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.
The following provides an example of equipping an RSL device.
-> equip bsc RSL
Enter the 1st device ID for the RSL: 1
Enter the 2nd device ID for the RSL: 0
Enter the Unique PATH identifier:

Enter LAPD T200 Timer value for this device:

Enter LAPD N200 value for this device:
Enter LAPD K value for this device:

2500

COMMAND ACCEPTED
->

68P02901W17-T

9-179
Jan 2010

Unequipping an RSL using the TTY interface

Chapter 9: Configuring Devices and Functions

Unequipping an RSL using the TTY interface

To unequip an RSL, follow these steps:

Procedure 9-51 Unequip an RSL

1

Determine the RSL equipage at the BTS using:

disp_equipment <location>

Lock the RSL by entering:

lock_device 0 RSL <1st device id> <2nd device id>

Repeat step 2 to lock all additional RSLs.

Lock the path by entering:

lock_device 0 PATH <1st device id> <2nd device id>

Repeat step 4 to lock all additional paths.

Remove neighbor/source cell data from neighboring cells.

Unequip the RTF by entering:

unequip <location> RTF <1st device id> <2nd device id>

NOTE
This command also removes frequencies.
8

Unequip the RSL by entering:

unequip 0 RSL <1st device id> <2nd device id>

Repeat step 8 to unequip all additional RSLs.

Example
The following is an example of unequipping an RTF and an RSL:
-> disp_equipment 2
GPROC 0 0 0
GPROC 1 0 0
.
.
SITE
0 0 0
-> shutdown_device 2 DRI 0 0 0 60
COMMAND ACCEPTED
-> lock_device 0 SITE 2 0 0
COMMAND ACCEPTED
-> lock_device 0 RSL 2 0 0

9-180

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Other RSL configuration tasks

COMMAND ACCEPTED
-> lock_device 0 PATH 2 0 0
COMMAND ACCEPTED
.
.
-> unequip 2 RTF 0 0 0
COMMAND ACCEPTED
.
.
-> unequip 0 RSL 2 0 0
COMMAND ACCEPTED

Other RSL configuration tasks

To perform other configuration tasks for an RSL device, see Methods of configuring individual
devices and functions on page 9-3.

68P02901W17-T

9-181
Jan 2010

Configuring an RTF function

Chapter 9: Configuring Devices and Functions

Configuring an RTF function

Definition of an RTF function

An RTF is the function that supports the air interface channel and the DRI/RCU pair. A BSS can
support up to 30 GPRS timeslots per cell. Up to 64 SDCCHs can be supported per carrier.
An RTF is contained within an RTFGroup.

RTFGroup
The RTFGroup object class describes a single RTF function grouping within the site. Instances
of this object are only created as placeholders for contained RTF instances. There is an
RTFGroup Detailed View in the OMC-R GUI.

TRX creation and deletion

A cell logically contains transceivers. Transceiving functionality is implemented in the BSS
by the RTF in conjunction with the DRI hardware. When an RTF is created, the OMC-R
automatically creates a TRX (transceiver) under the cell specified in GSM Cell Id field (BSS
parameter carrier1GsmCellID) of the RTF. The TRX is automatically deleted when the RTF
is deleted.

Impact of Dual Band Cells feature on RTFs and DRIs

When the Dual Band Cells feature is enabled for a cell, DRIs and RTFs within the dual band cell
must have different DRI or RTFGroup identifiers. When equipping DRIs, the two DRI/RTFGroup
identifiers are allowed if the cell is dual band.
Also in a dual band cell, primary and secondary band RTFs need to be configured with the
DRI/RTFGroup identifiers associated with their band. If an attempt is made to use the same
DRI/RTFGroup identifier for RTFs in both the secondary and primary bands of a dual band
cell, an error message is displayed.
For a dual band cell, the secondary and primary band frequency types must be allowed by the
cabinet(s) to which the DRI(s) in each zone are equipped.
For non-dual band cells, all DRIs and RTFs equipped to a cell must be configured in a single
DRI/RTFGroup.
Also when the cell parameter inner_zone_alg is set to 3 indicating that the cell is dual band, the
valid range for the ARFCN of an RTF configured for the inner zone is defined by the frequency
type defined for the secondary band.
When an RTF is equipped for the secondary band in a dual band cell, the parameter Transmit
Power Reduction is not required.

9-182

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Impact of VersaTRAU feature on an RTF

Impact of VersaTRAU feature on an RTF

A VersaTRAU RTF can only be configured on a single density CTU2 or a double density CTU2-D.
If the value of rtf_ds0_count exceeds the number of free terrestrial timeslots on the RTF path
between the BSC and BTS, the equipage of a 64 k RTF is not allowed.
If VersaTRAU is enabled while trying to equip an RTF, if the GDS capacity is exceeded, the
following warning message is displayed:
WARNING: Insufficient GDS resources available for all PDTCHs on the PCU.
64 k and 16 k half rates are mutually exclusive for a carrier. That is, if a carrier is configured
to be 64 k and other existing conditions allow half rate to be enabled, then half rate can
only be enabled if 8 k TRAU is allowed. 16 k half_rate is not supported on carriers with
pkt_radio_typeas 64 k.
When pkt_radio_type is set to 64 k and half_rate_enabled is set to Enabled (1), if
allow_8k_trau is set to No (0) during a create operation the following message is displayed:
ERROR: allow_8k_trau must be set to Yes (1) for 64 k carrier if half rate is
enabled.
When half_rate_enabled is set to Enabled (1) and allow_8k_trau is set to No (0), any
modification of pkt_radio_type from None (0), 16 k (1) or 32 k (2) to 64 k (3) displays the
following error message:
ERROR: allow_8k_trau must be set to 1 for 64 k carrier if half rate is enabled
If pkt_radio_type is either None (0)/16 k(1)/32 k(2) and half_rate_enabled is set to Enabled
(1), then allow_8k_trau can be set to Yes (1) or No (0).
See VersaTRAU on page 2-172 for further details.

Impact of BSC-BTS dynamic allocation on an RTF

If BSC-BTS dynamic allocation is enabled for the site containing the selected RTF, the equip
command does not prompt for the following parameters. Likewise, the corresponding parameter
fields in the RTF Detailed View form are grayed-out.

First Path Id (BSS Naming convention: path_id1).

Second Path Id (BSS Naming convention: path_id2).

Associated RSL for First Path Id (BSS Naming convention: rsl_id1).

Associated RSL for Second Path Id (BSS Naming convention: rsl_id2).

Packet Radio Type (BSS Naming convention: pkt_radio_type).

If BSC-BTS dynamic allocation is enabled for the site containing the selected RTF, the parameter
field: RTF Capacity (BSS naming convention: rtf_capacity) in the RTF Detailed View form is
set to RTF FULL, and cannot be changed by a user.

68P02901W17-T

9-183
Jan 2010

Impact of BCCH and SDCCH in the EGSM band on an RTF

Chapter 9: Configuring Devices and Functions

Impact of BCCH and SDCCH in the EGSM band on an RTF

When egsm_bcch_sd is enabled for a cell and carrier type is BCCH, the RTF parameter field:
Carrier 1 ARFCN (BSS parameter name: arfcn) can be set to EGSM band frequencies. See
Configuring a cell with BCCH and SDCCH in the EGSM band on page 8-179 for further details.

Timeslots and frequency hopping

Timeslots on a carrier do not have to have the same training sequence code or frequency
hopping parameters.

Methods of configuring an RTF

An RTF can be configured using any of the following methods:

OMC-R GUI Navigation Tree and Detailed Views.

TTY interface and BSS commands.

The Path Configure facility, see Configuring a path using Path Configure menu option
on page 11-73.

Additional information for RTFs

Refer to the following sections in this manual for associated information:

9-184

Creating an RTF function on page 9-185.

Deleting an RTF on page 9-193.

Changing a BCCH carrier frequency on page 8-213.

Changing a non-BCCH carrier frequency on page 8-216.

Changing a TSC for a BCCH on page 8-221.

Configuring frequency hopping on page 8-165.

Configuring a KSW (or DSW) device on page 9-123.

Changing the number of allocated SDCCHs on page 8-226.

Displaying Channel and Circuit Status on page 9-20.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating an RTF function

Creating an RTF function

Prerequisites to creating an RTF

Before an RTF can be created, the Algorithm Number field (parameter name: alg_num) in each
of the nine cell algorithm Detailed View forms must be changed from
Unused (255) to another setting.
When equipping a DRI at a remote BTS, one or more Receive Transmit Functions (RTF) must be
equipped.

Creating an RTF using the OMC-R GUI

To create an instance of an RTF function using the OMC-R GUI, proceed as follows:
1.

Navigate to and select the RTF class button in the Navigation Tree (BSS BSS instance
SITE SITE instance Radio Frequency RTFGroup RTFGroup instance
RTF). If necessary, see Navigating to a network object class or instance on page 1-28
for further details.

2.

Select Edit Create from the menu bar. The OMC-R displays the RTF Detailed View form.

3.

Complete the fields, as required. See RTF Detailed View fields for further details.

4.

Create and close the Detailed View. If necessary, see Creating a network object using the
OMC-R GUI on page 1-32 for further details.

NOTE
Device information is stored in flat files when creating an RTF with timeslot(s). If an
unexpected exit from the GUI occurs, this file can be used to access the reserved
timeslot(s) information on the mmi prompt using the chg_ts_usage command. See
Using flat files on page 11-94 for more details.

RTF Detailed View fields

The following sections list and briefly describe the parameter fields in the RTF Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help - On Context from the menu
and drag the ? prompt to the appropriate field and click that field. A context-sensitive
help page is displayed.

68P02901W17-T

9-185
Jan 2010

RTF Detailed View fields

Chapter 9: Configuring Devices and Functions

Identification grouping
Table 9-61 describes the fields in the Identification grouping of the RTF Detailed View.

Table 9-61 RTF Detailed View fields - Identification grouping

Field name/BSS
parameter name

Values

Brief description

Carrier Type

The carrier type of the RTF.

BCCH carrier
(0) or
Non-BCCH
carrier (1).
Default is
BCCH (0).

KSW Pair
ksw_pair

The KSW pair managing this carrier.

Not valid for an RTF in an M-Cell site.

0-3

RDN Class

See description in Table 4-1.

Default is the
device class.

RDN Instance

See description in Table 3-1.

0 to 11.
Default is 0.

NMC RDN Value

See description in Table 4-1.

Parent Detail
View

Displays the name of the parent

RTFgroup. Click to display the parent
RTFGroup Detailed View.

First Path
Id (OMC-R
parameter name:
path_id1)

The primary Unique PATH. Not valid if

the site in which this RTF is contained
is site 0 (BSC). Not applicable when
BSC-BTSdynamic allocation ts_sharing
is enabled (1).

Associated RSL
for First Path
Id (OMC-R
parameter name:
rsl_id1)

The first associated 16 kbit/s RSL.

Second Path
Id (OMC-R
parameter name:
path_id2)

The optional secondary Unique PATH.

Not valid if the site in which this RTF is
contained is site 0 (BSC).
Not applicable when BSC-BTSdynamic
allocation ts_sharing is enabled (1).

0 to 9

Mandatory or
Optional?
Mandatory.

Optional.

Mandatory
for creation.
Thereafter,
optional.
Optional.

Optional for
creation.

Continued

9-186

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 9-61

RTF Detailed View fields

RTF Detailed View fields - Identification grouping (Continued)

Field name/BSS
parameter name

Values

Brief description

Associated RSL
for Second
Path Id (OMC-R
parameter name:
rsl_id2)

The second associated 16 kbit/s RSL

RTF Capacity
rtf_capacity

Whether the reduced or full number of

time slots are used on E1 link.

Mandatory or
Optional?
Optional.

RTF_FULL (0)
or RTF_SUB
(1).
Default is 0.

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this RTF. Where additional
notes are not required, close this field by clicking the toggle button next to the Additional
Information header.

State grouping
Standard network object state fields, see Table 4-2 for details. The Related Device field is
grayed-out by default.

Carrier 1 Information grouping

Table 9-62 describes the fields in the Carrier 1 Information grouping of the RTF Detailed View.

Table 9-62 RTF Detailed View fields - Carrier 1 Information grouping

Mandatory
or Optional?

Field name

Brief description

Values

Carrier 1 ARFCN

The absolute radio frequency

channel for the carrier.

For PGSM: 0 - 124.

For EGSM: BCCH carrier:
0 - 124, 975 - 1023.
Non-BCCH carrier: 0 124, 975 - 1023.
For DCS 1800: 512 - 885.
PCS 1900: 512 - 810.
Default is 0.

Mandatory.

Freq Hopping Ind

for TS 0 to 7

The frequency hopping

indicator for GSM air timeslots
0 to 7 on the carrier.

0 - 3, or 255 (no hopping).

Default is 255.

Optional.

Continued

68P02901W17-T

9-187
Jan 2010

RTF Detailed View fields

Table 9-62

Chapter 9: Configuring Devices and Functions

RTF Detailed View fields - Carrier 1 Information grouping (Continued)

Field name
GSM Cell Id
(OMC-R
parameter name:
carrier1Gsm
CellId)

Brief description

Mandatory
or Optional?

Values

GSM cell id assigned to the

carrier. The MCC and MNC
sub-fields can be edited in
Create mode. The MCC and
MNC sub-fields cannot be
edited for n-1 or n-2 BSS.
If the environment variable
AUTO_POP_CELLID is set
to On (see Operating

Mandatory.

Information: OMC-R
System Administration
(68P02901W19) for further
details) and an RTF has
already been created under
the associated RTF Group,
the OMC-R automatically
populates the GSM Cell ID
field with the Cell ID to which
the RTF Group belongs.
When creating an RTF in an
RTFGroup where no other
RTF exists, the GSM Cell ID
field is auto-populated with
a default value of <MCC>
<MNC> 0 0.

9-188

Training Seq Code

for TS 0 to 7

The training sequence code

for the GSM air timeslots 0 to
7 on the carrier.

0 - 7.
Default is 0.

Mandatory.

SDCCH Load
sd_load

The maximum number

of timeslots that can be
configured as SDCCHs for this
carrier. If a CTU2 is equipped
in a cell to operate in double
density mode, then sd_load
should not be set higher than
3.

0 - 8.
Default is 2.

Mandatory.

SDCCH
Placement
Priority
sd_priority

The SDCCH placement

priority for a carrier (RTF).
The BSS configures SDCCHs
on carriers with the highest
priority, up to their SDCCH
load (sd_load).

0 (high priority) - 255 (low

priority).
Default is 0.

Optional.

Channel
Allocation Priority

The channel allocation priority

of a carrier.

0 (high priority) - 250 (low

priority).
Default is 0.

Mandatory.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

RTF Detailed View fields

Concentric cells grouping

Table 9-63 describes the fields in the Concentric Cells grouping of the RTF Detailed View.

Table 9-63 RTF Detailed View fields - Concentric cells grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory or Optional?

Concentric Cell Zone

cell_zone

In which zone the

RTF is located. Only
used for non-BCCH
carriers.

Outer zone (0) or

Inner zone (1).
Default is Outer zone
(0).

Optional.

Transmit Power
Reduction
trx_pwr_red

Amount of power
reduction for a
particular RTF
carrier.

0 - 21 dBm.
For PGSM, EGSM,
DCS1800 cells,
and M-Cell6,
Horizonmacro or
Horizon II macro
BTSs, the range is: -1
to 21. For PCS1900
cells, the range is 0 21.

Optional.

GPRS grouping
Table 9-64 describes the fields in the GPRS grouping of the RTF Detailed View.

Table 9-64 RTF Detailed View fields - GPRS grouping

OMC-R GUI field
name

Brief description

Values

Mandatory or
Optional?

Packet Radio Type

See GPRS and EGPRS coding schemes

on page 2-39 and VersaTRAU on page
2-172 for further details.

Optional.

Number of
Backhaul
Timeslots on
Carrier

See VersaTRAU on page 2-172 for

details.

Optional.

MMS Timeslots grouping

Table 9-65 describes the fields in the MMS Timeslots grouping of the RTF Detailed View.
The MMS Timeslot grouping is only viewable when creating or re-assigning an RTF using the
Path Configure menu option (see Creating an RTF at a site using the Path Configure menu
option on page 11-92) on a path containing one or more adjacent TS Switches. The fields
in this grouping are not maintained outside a Path Configure operation, and are only used
by the OMC-R.

68P02901W17-T

9-189
Jan 2010

RTF Detailed View fields

Chapter 9: Configuring Devices and Functions

Table 9-65 RTF Detailed View fields - MMS Timeslot grouping

Brief description

Values

Mandatory or
Optional?

First Path
Upstream TS
MMS
(OMC name:
path1_upst
_ts1)

The first timeslot number on which the

RTF is equipped, on the primary path, in
the upstream MMS directly connected to
a TS switch. For example if the value is 2,
the RTF is equipped on timeslot 2 in the
case of a sub-equipped RTF. Whereas the
RTF is equipped on timeslots 2 and 3 in
the case of a fully equipped RTF.

0 - 31.

Optional.

First Path
DownStream
TS MMS
(OMC name:
path1_downst
_ts1)

The first timeslot number on which the

RTF is equipped, on the primary path, in
the downstream MMS directly connected
to a TS switch. For example if the value
is 2, the RTF is equipped on timeslot 2 in
the case of a sub-equipped RTF. Whereas
the RTF is equipped on timeslots 2 and 3
in the case of a fully equipped RTF.

0 - 31.

Optional.

Second Path
Upstream TS
MMS
(OMC name:
path2_upst
_ts1)

The first timeslot number on which the

RTF is equipped, on the secondary path,
in the upstream MMS directly connected
to a TS switch. For example if the value
is 2, the RTF is equipped on timeslot 2 in
the case of a sub-equipped RTF. Whereas
the RTF is equipped on timeslots 2 and 3
in the case of a fully equipped RTF.

0 - 31.

Optional.

Second Path
DownStream TS
MMS
(OMC name:
path2_downst
_ts1)

The first timeslot number on which the

RTF is equipped, on the secondary path, in
the downstream MMS directly connected
to a TS switch. For example if the value
is 2, the RTF is equipped on timeslot 2 in
the case of a sub-equipped RTF. Whereas
the RTF is equipped on timeslots 2 and 3
in the case of a fully equipped RTF.

0 - 31.

Optional.

Field name

General grouping
Table 9-66 describes the fields in the General grouping of the RTF Detailed View.

Table 9-66 RTF Detailed View fields - General grouping

Field name
Extended Range
Timeslots
ext_timeslots

9-190

Brief description
The number of Extended Range
timeslots that are configured when
ext_range_cell is 1 (enabled as a
boundary cell).

Values

Mandatory or
Optional?

0 - 4.

Optional.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

RTF Detailed View fields

AMR/GSM Half Rate grouping

Table 9-67 describes the fields in the AMR/GSM Half Rate grouping of the RTF Detailed View.
Fields in this grouping can be accessed if:

The AMR Feature (amrOpt) is unrestricted (Enabled) at the BSS or the GSM HR Feature
(gsmHalfRateOpt) is unrestricted (Enabled) at the BSS.

The site is half rate capable.

The BSS features amrTCUAOpt and amrTCUBOpt are restricted and the site has only
M-Cell2 and/or M-Cell6 cabinets.

See Adaptive Multi-Rate (AMR) on page 2-129 for details.

Table 9-67 RTF Detailed View fields - AMR/GSM Half Rate grouping
Field name/BSS
parameter name

Brief description

Values

Mandatory or
Optional?

Half Rate
half_rate_
enabled

Enables and disables Half Rate for

the RTF. If the site has Horizonmacro
and/or Horizonmacro_ext cabinets,
and the BSS has the amrTCUAOpt
and amrTCUBOpt features
restricted, this field remains
selectable. Also see VersaTRAU on
page 2-172.

Enabled (1),
Disabled (0).
Default is 0.

Optional.

8 k TRAU Allowed
allow_8k_trau

Whether 8 k backhaul calls are

allowed.
Cannot be accessed if:

Yes (1),
No (0).
Default is Yes
(1).

Optional.

The BSS feature

amrEnhancedCapOpt is
restricted.

gsmHalfRateOpt is restricted.

half_rate_enabled is disabled,
in which case allow_8k_trau
is set to Yes (1).

Cell parameter amr_hr_acs is

set to 7.95 kbit/s, in which case
allow_8k_trau is set to No (0).

The site is not AMR capable.

If any RTF serving a cell has

allow_8k_trau set to Yes (1), the
option 7.95 kbit/s is not available for
cell parameter amr_hr_acs. Also
see VersaTRAU on page 2-172.

68P02901W17-T

9-191
Jan 2010

Equipping an RTF function using the TTY interface

Chapter 9: Configuring Devices and Functions

Equipping an RTF function using the TTY interface

To equip an RTF using the TTY interface, see Methods of configuring individual devices and
functions on page 9-3.

NOTE

9-192

When equipping an RTF using the TTY interface, if half_rate_enabled is

set to 0, the system does not prompt for allow_8k_trau. This is because
allow_8k_trau is set to Yes (1) by default.

Similarly, half_rate_enabled can be set to 1. In this instance, the system does

prompt for allow_8k_trau.

Also if the cell parameter amr_hr_acs is set to 7.95 kbit/s, allow_8k_trau

cannot be set to Yes (1).

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting an RTF

Deleting an RTF

Restrictions when deleting an RTF

An RTF can be deleted if the cell uses Coding Schemes 1 or 2 (that is, init_dl_cs and init_ul_cs
are not set to values 2 or 3).

Methods of deleting an RTF

An RTF can be deleted using any of the following methods:

The Navigation Tree, see Methods of configuring individual devices and functions on
page 9-3.

The TTY interface, see below.

The Path Configure menu option, see Configuring a path using Path Configure menu option
on page 11-73 in Chapter 11 Network Expansion.

NOTE
When a BCCH RTF is to be deleted, the opportunity to export the incoming neighbors
associated with this RTF is provided. The method used is described in Exporting
incoming neighbors on deletion of BCCH RTFs on page 9-195.

Deleting an RTF using the TTY interface

To unequip RSLs and RTFs, follow these steps:

Procedure 9-52 Unequip RSLs and RTFs

1

Determine the RSL, PATH, and RTF equipage at the BTS using:
disp_equipment <location>

Lock the RSL by entering:

lock_device 0 RSL <1st device id> <2nd device id>

Repeat step 2 to lock all additional RSLs.

Lock the path by entering:

lock_device 0 PATH <1st device id> <2nd device id>

Repeat step 4 to lock all additional paths.

Remove neighbor/source cell data from neighboring cells.

Continued

68P02901W17-T

9-193
Jan 2010

Deleting an RTF using the TTY interface

Chapter 9: Configuring Devices and Functions

Procedure 9-52 Unequip RSLs and RTFs (Continued)

7

Unequip the RTF (and remove frequencies) by entering:

unequip <location> RTF <1st device id> <2nd device id>

Unequip the RSL by entering:

unequip 0 RSL <1st device id> <2nd device id>

Repeat step 8 to unequip all additional RSLs.

Example
The following is an example of unequipping an RTF and RSL:
-> disp_equipment 2
GPROC 0 0 0
GPROC 1 0 0
.
.
SITE 0 0 0
->
shutdown_device 2 DRI 0 0 0 60
COMMAND ACCEPTED
.
.->
lock_device 0 SITE 2 0 0
COMMAND ACCEPTED
->
lock_device 0 RSL 2 0 0
COMMAND ACCEPTED
.
->
lock_device 0 PATH 2 0 0
COMMAND ACCEPTED
.
.

->
unequip 2 RTF 0 0 0

9-194

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Exporting incoming neighbors on deletion of BCCH RTFs

COMMAND ACCEPTED
.
->
unequip 0 RSL 2 0 0
COMMAND ACCEPTED

Exporting incoming neighbors on deletion of BCCH RTFs

When deleting a BCCH RTF using the OMC-R GUI, the opportunity to export the neighbors
associated with it is provided. If used, the neighbors are saved to a file using the Cell-X-Export
facility where they can be accessed and re-created at a later date. This facility is used as follows:

Procedure 9-53 Exporting incoming neighbors on deletion of BCCH RTFs

Navigate to and select the BCCH RTF to delete.

Select Edit Delete from the menu bar.

Result: The OMC-R displays the deletion confirmation window.

Press the Export Neighbors button.

Result: The Cell X Export Watcher window is displayed (see
Figure 12-1).

From the Cell X Export Watcher window, select Options - Start menu
bar to begin the export.
Result: The neighbor and cell file is exported to
/usr/omc/config/global/cellX.

When the export is complete, close the Cell X Export Watcher window.

In the deletion confirmation window, click OK to confirm the BCCH

RTF deletion.

The neighbor information can be retrieved at a later date by using the Cell-X-Import facility
as described in Cell-X-Import on page 12-17.

NOTE
This facility is only available for BCCH RTFs. It is not available for non-BCCH RTFs.

Other RTF configuration tasks

For general information on additional RTF configuration tasks, such as displaying and modifying,
see Methods of configuring individual devices and functions on page 9-3.

68P02901W17-T

9-195
Jan 2010

Other RTF configuration tasks

Chapter 9: Configuring Devices and Functions

For example, the following command displays all information for RTF 0 1:
disp_equipment 2 rtf 0 1
For example, the following command sets the pkt_radio_type RTF parameter to 32k TRAU at
RTF 0 1 respectively:
modify_value 1 pkt_radio_type 2 rtf 0 1

9-196

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring an XBL device

Configuring an XBL device

Definition of an XBL
The purpose of the XBL is to enable notification of failed traffic circuits at the RXCDR being
sent to the BSC. If failures occur, the BSC disables these circuits by sending the appropriate
blocking messages to the MSC along an MTL.
The XBL is the link between the RXCDR and the BSC which provides fault management
communications link for the devices at the RXCDR. The XBL uses a dedicated 64 kbit/s timeslot
on the RXCDR to BSC 2 Mbit/s link. It provides bi-directional communications between GPROC
in the BSC and GPROC in RXCDR, consequently four traffic channels (TCH) are lost. If
multiple BSCs are supported by the same RXCDR, then the second XBL should be equipped
to a physically different 2 Mbit/s link to enhance redundancy.
A maximum of 20 XBLs can be supported.
An XBL can only exist at SITE 0 (BSC), but are not allowed at SITE 0 (BSC) of a BSS if the
BSC is a transcoding site.
In the Navigation Tree, an XBL is contained under an Assoc_BSS or Assoc_RXCDRs.
Also see Enhanced XBL (EXBL) on page 2-11.

Prerequisites for creating an XBL

To equip an XBL link between an RXCDR and BSC, an XBL device must be equipped at both the
RXCDR and BSC using the same physical MMS and timeslot.
The BSS rejects an attempt to equip an XBL device at the BSC, if the MMS identifier specified
does not exist (that is, not in the RXCDR to BSC Connectivity Table).
Before equipping the XBL at the RXCDR, the XBL must have been equipped at the BSC.
The BSS rejects an attempt to equip an XBL device at the RXCDR if the MMS identifier specified
does not exist (that is, not in the BSC to RXCDR Connectivity Table).

SYSGEN rules for XBLs

XBL devices may be equipped either in or out of SYSGEN mode. The number of XBL devices
that may be equipped is limited by the number of available LAPD connections on the associated
GPROC device.
XBL devices equipped inside SYSGEN mode attempt to come into service when SYSGEN mode
is turned off. If successful, the XBL state is Busy-Unlocked.
XBL devices equipped outside SYSGEN mode enter the Enabled-Locked state. The XBL device
at each end of the link must then be unlocked for the XBL to become Busy-Unlocked.

68P02901W17-T

9-197
Jan 2010

Creating an XBL for an Assoc_RXCDR using the OMC-R GUI

Chapter 9: Configuring Devices and Functions

Creating an XBL for an Assoc_RXCDR using the OMC-R GUI

Prerequisites to creating an XBL
An XBL can only be created if an Assoc_RXCDR and Assoc_BSS exist.
An XBL can be added to either an Assoc_RXCDR or an Assoc_BSS, that is: Network - RXCDR
- Assoc_BSS - XBL
orNetwork - BSS - Assoc_RXCDRs - XBL

Creating an XBL
To add an XBL to the network using the OMC-R GUI, follow these steps:

Procedure 9-54 Add an XBL to the network

1

Navigate to and select the XBL class button in the Navigation Tree
(BSS BSS instance Assoc_RXCDR Assoc_RXCDR instance
XBL). If necessary, see Navigating to a network object class or instance
on page 1-28 for further details.

Select Edit Create from the menu bar.

Result: The OMC-R displays the XBL Detailed View form.

Enter all required information in this form. See XBL Detailed View
fields for details.

Create and close the Detailed View. If necessary, see Creating a

network object using the OMC-R GUI on page 1-32 for further details.

XBL Detailed View fields

The following sections list and briefly describe the parameter fields in the XBL Detailed View
according to their parameter grouping.

NOTE
To obtain further information for a parameter, select Help On Context from
the menu and drag the ? prompt to the appropriate field and click that field. A
context-sensitive help page is displayed.

9-198

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

XBL Detailed View fields

Identification grouping
Table 9-68 describes the fields in the Identification grouping of the XBL Detailed View.

Table 9-68 XBL Detailed View fields - Identification grouping

Field name/BSS
parameter name

Brief description

Values

Mandatory
or
Optional?

MSI Identifier

The particular MSI for the link.

BSC: 0 - 95.
RXCDR: 0 - 123.

Mandatory.

MMS Identifier

The 2.048 Mbit/s link on the MSI.

0 or 1.

Mandatory.

MMS Timeslot
Identifier

The XBL timeslot for the link.

E1: 1 - 31.

Mandatory.

XBL Rate
xbl_rate

The rate of the XBL to a SITE. Displayed

if the XBL 16 kbit/s LAPD Feature
(xbl_rateOpt) is enabled (unrestricted)
at the BSS. If XBL 16 kbit/s LAPD Feature
is disabled (restricted), the rate is 64
kbit/s.

16 kbit/s (0) or
64 kbit/s(3).
Default is 0.

Mandatory.

XBL Group

The XBL group. Only used if XBL data

rate is 16.

0 - 3.

RDN Class

See description in Table 4-1.

Default is the
device class.

RDN Instance

Device id for the XBL - the particular link

between the RXCDR and the BSC. Also
see description in Table 3-1.

0 - 19.

NMC RDN Value

See description in Table 4-1.

Parent Detail View

Displays the name of the parent

Assoc_RXCDR. Click to display the parent
Assoc_RXCDR Detailed View.

Associated BSS

Valid for XBLs equipped at an RXCDR.

Specifies with which Assoc_BSS device
the XBL communicates. Click to display
the BSS Detailed View for the BSS
associated with this XBL.

1 - 128.

Mandatory.

Associated RXCDR

Valid for XBLs equipped at a BSS.

Specifies with which Assoc_RXCDR
device the XBL communicates. Click to
display the RXCDR Detailed View for the
RXCDR associated with this XBL.

1 - 128.

Mandatory.

Optional.

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this XBL. Where additional
notes are not required, close this field by clicking the toggle button next to the Additional
Information header.

68P02901W17-T

9-199
Jan 2010

Creating an XBL for an Assoc_BSS using the OMC-R GUI

Chapter 9: Configuring Devices and Functions

State grouping
Standard network object state fields, see Table 4-2 for details.

LapD Information grouping

Table 9-69 describes the fields in the LapD Information grouping of the XBL Detailed View.

Table 9-69 XBL Detailed View fields - LapD Information grouping

Field name

Brief description

Mandatory or
Optional?

Values

LapD T200 Timer

Used to time the acknowledgments of

a transmitted frame. On timeoutmms
a counter is incremented. If the
value if this counter equals the value
in LAPD N200, then an error has
occurred.

1400 - 5000 ms
(in multiples of
50).
Default: 2500.

Mandatory.

LapD N200 value

Indicates the maximum number of

retransmissions of a frame.

1 - 5.
Default: 3.

Mandatory.

LAPD K Frame
Window

Indicates the maximum number of

unacknowledged information frames
(I-frames).

1 - 10.
Default: 7.

Mandatory.

Creating an XBL for an Assoc_BSS using the OMC-R GUI

To create an XBL for an Assoc_BSS see Creating an XBL for an Assoc_RXCDR using the
OMC-R GUI in the previous subsection, but instead of selecting the Assoc_RXCDR in step 1,
select the required Assoc_BSS.

Deleting an XBL from a Assoc_RXCDR or Assoc_BSS using the

OMC-R GUI
To delete an XBL device from an Assoc_RXCDR or Assoc_BSS using the OMC-R GUI, see the
general procedure in Deleting a network object using the OMC-R GUI on page 1-37.

Equipping an XBL device at a BSC using the TTY interface

To equip an XBL at a BSC using the TTY interface, follow these steps:

Procedure 9-55 Equip an XBL at a BSC using TTY

9-200

See Methods of configuring individual devices and functions on page

9-3.

Equip the XBL at the BSC.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Equipping an XBL device at an RXCDR using the TTY interface

Example of equipping an XBL at a BSC

The following provides an example of equipping an XBL device at a BSC.
-> equip 0 XBL
Enter the AXCDR device ID for the XBL: 2
Enter the second device ID for the

Enter the data rate for the XBL: 16

Enter the first MMS description for this device:
Enter the second MMS description for this device:
Enter timeslot on MMS where this device appears:

1
1
6

Enter the group of the timeslot where this device appears:

Enter LAPD T200 timer value for this device:

2500

Enter LAPD N200 timer value for this device:

Enter LAPD K value for this device:

COMMAND ACCEPTED
->

Equipping an XBL device at an RXCDR using the TTY interface

To equip an XBL at an RXCDR using the TTY interface, follow these steps:

Procedure 9-56 Equip an XBL at an RXCDR using TTY

1

See Methods of configuring individual devices and functions on page

9-3.

NOTE
The timeslot on the MMS must be identical to that entered
when equipping the XBL at the BSC. The other information
can be different as long as it relates to the same physical link.
2

68P02901W17-T

Arbitrarily number the BSCs connected to the RXCDR. This is to ensure

that different BSCs can be distinguished from the RXCDR. Refer to
Configuring a Conn_Link on page 5-5 for further information.

9-201
Jan 2010

Equipping an XBL device at an RXCDR using the TTY interface

Chapter 9: Configuring Devices and Functions

Example of equipping an XBL at an RXCDR using the TTY interface

The following provides an example of equipping an XBL device at an RXCDR using the TTY.
-> equip 0 XBL
Enter the ABSS device ID for the XBL: 2
Enter the second device ID for the XBL: 0
Enter the data rate for the XBL: 64
Enter the first MMS description for this device:
Enter the second MMS description for this device:
Enter timeslot on MMS where this device appears:
Enter LAPD T200 timer value for this device:

2500

Enter LAPD N200 timer value for this device:

Enter LAPD K value for this device:

1
1
6

COMMAND ACCEPTED
->

9-202

68P02901W17-T
Jan 2010

Chapter

10
Auditing

Auditing allows on-demand checks of the OMC-R CM MIB against the CM databases of a
selected Network, Region, BSS/RXCDRs, PCU, or sites in the GSM Network. The following
auditing topics are described in this chapter:

Introduction to auditing on page 10-2.

Auditing recommendations on page 10-8.

Auditing the network using the OMC-R GUI on page 10-12.

Auditing a BSS/RXCDR using the OMC-R GUI on page 10-14.

Multiple site audits on page 10-17.

Multiple BSS/RXCDR audits on page 10-18.

Scheduling an audit on page 10-19.

Managing audit logs on page 10-29.

Propagating cell changes to neighbor cells after an audit on page 10-35.

Time of the last audit on page 10-38.

NOTE
Audit-related activities performed by the OMC-R System Administrator are described
in Operating Information: OMC-R System Administration (68P02901W19).

68P02901W17-T
Jan 2010

10-1

Introduction to auditing

Chapter 10: Auditing

Introduction to auditing

Overview of auditing
Purpose
The purpose of an audit is to perform on-demand checks of the OMC-R CM MIB against the CM
databases of selected Network, Region, BSS/RXCDRs, PCU, or sites in the GSM Network.

NOTE

An audit can only compare objects that are supported in both the OMC-R and
BSS.

Permission must be obtained from the OMC-R system administrator before

auditing a network.

Functionality
The BSS and OMC-R MIB BTS objects become out of synchronization if the BSS contains a CM
change which has not been applied to the same device/function in the CM MIB.
When an audit is initiated, the audit process checks if objects and object attributes are
consistent at the NE and the CM MIB. An inconsistency list is produced if:

An object exists in the MIB and not in the BSS.

An object exists in the BSS and not in the MIB.

An object exists in both the MIB and BSS but the attribute values differ.

An object exists on both sides but are different versions.

When the inconsistencies are applied to the OMC-R (either by the user or automatically by
the OMC-R), objects not in the NE database (but in the OMC-R database) are deleted at the
OMC-R. New objects in the NE database are created in the OMC-R database, and attribute value
inconsistencies are updated in the OMC-R database to become the same as attributes in the NE.
After a BSS or RXCDR has been upgraded to a new version of software, the OMC-R MIB may
contain objects that are no longer supported by the new BSS/RXCDR software. An audit
detects if there are any objects in the OMC-R MIB that are no longer supported by the version
of software running on the BSS or RXCDR. Audit then deletes from the OMC-R MIB, objects
that are no longer supported by the BSS/RXCDR software load.

10-2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Intelligent audit

NOTE
The entire BSS is still audited if there is a CSFP swap of new databases, or
downloading of a new database.
An RXCDR and its child objects, and a PCU and its child objects, do not have a
counter, so an audit of these objects always proceeds.

Intelligent audit

Intelligent Audit enhances the usability of the Audit functionality. The major enhancement
is to allow the user to intervene on pending and blocked-pending scheduled audits. Other
enhancements allow the user to:

Expand or contract the hierarchical tree of objects on the Navigation Tree, during the
Audit gather and apply phases. The objects contained by the node have read-only access.

Expand or contract the NE and site level nodes on the Contained Devices, during the Audit
gather and apply phases. The objects contained by the node have read-only access.

Open the Detailed Views of the contained devices, during the Audit gather and apply phases
of the container NE or site. The objects contained by the node have read-only access.

Initiate an Apply to OMC from the Audit Logs form, and details such as success, error
or failure of an applied audit can be viewed from the Audit Logs form (see Managing
audit logs on page 10-29 for further details).

Look up the completion time of the last Audit Gather and Audit Apply phase for a Network,
Region, BSS, RXCDR, PCU, or site using the appropriate Detailed View (see Time of the
last audit on page 10-38 for further details).

Defer scheduled audits (that is, with a pending status) to a later time. At times, it becomes
essential for the operator to defer pending operations to increase or decrease the priority
of the scheduled Audit operation. This allows the operator to place all scheduled audits
into an intervene or suspend state for a certain time, perhaps while Audits considered to
be more important can be initiated or attended to (for example, immediately after a replan
deployment through CSFP swap or NE download). To defer a pending scheduled audits,
menu options are provided in Audit Log form. Here, the user can specify the date and
time to which the scheduled audit is to be deferred (see Deferring a scheduled audit on
page 10-25 for further details).

Configure the Audit Gather phase and specify whether Call Trace objects at a BSS need to
be audited (see Configuring the Audit Gather phase on page 10-5 for further details).

During the apply of audit inconsistencies, any object locks in the database are ignored. For
example, if a device Detailed View is already open in Edit mode before the audit was initiated,
the Detailed View is closed if any inconsistencies are applicable to that device Detailed View.

68P02901W17-T

10-3
Jan 2010

Multiple BSS/RXCDR Audit

Chapter 10: Auditing

Multiple BSS/RXCDR Audit

An audit can be initiated for a Network, Region, PCU, one or more sites or, with the introduction
of the Multiple BSS Audit feature, on one or more BSS/RXCDRs (that is, more than one
BSS/RXCDR can be audited in parallel).
If a configuration management task has affected two or more BSS/RXCDRs, there are now two
ways in which the audit can be performed:

Select each affected BSS/RXCDR in turn and perform an audit on each.

Schedule a one-off audit for the affected BSS/RXCDRs.

The Multiple BSS/RXCDR Audit feature enables a network-wide audit on a fully configured 120
k TCH system to be kept within at an acceptable time level.

Description of Gather phase activities

When an audit is selected for the Network, the gather phase occurs for each BSS/RXCDR in
the network in parallel. Once the network-wide inconsistency report has been generated, the
user can apply it to the Network.
When an audit is selected for one BSS/RXCDR, when the gather phase is complete for the
BSS/RXCDR, the user can apply the inconsistency report to the OMC-R.
When one or more sites have been selected for auditing, the gather phase occurs in parallel for
sites on different BSSs, and in sequence within a BSS. The selected sites can span more than
one BSS/RXCDR. Then the user can apply the inconsistency list to the OMC-R.
The gather phase of the audit for multiple BSS/RXCDRs occurs in parallel. This decreases the
time required to execute the audit gather procedures involving multiple network elements.

NOTE
If multiple BSSs or RXCDRs are audited, only one inconsistency report is generated,
even though the inconsistencies may be generated in parallel for each network
element. This single inconsistency report can only be applied to the OMC-R when the
audit gather phase is complete for all the selected network elements.

Configuring Multiple BSS Audit

The total number of BSSs or RXCDRs that can have audit gather phases occurring in parallel,
spanning multiple parallel active audits can be defined using the ParallelAudits variable in the
audit.cfg file located in /usr/omc/config/global. This is set to 8 (BSSs/RXCDRs) by default for
non-120 k systems and 16 (BSSs/RXCDRs) by default for 120 k systems.
If the number of parallel audits configured in the ParallelAudits variable is less than 1 or
greater than 8/16 (8 for non-120 k systems; 16 for 120 k systems), then the number defaults to 8
or 16 (depending on the system) and an error is logged in the omc audit file.

Initiating a Multiple BSS Audit

To initiate a multiple BSS audit, see Multiple BSS/RXCDR audits on page 10-18.

10-4

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Audit logs and temporary files

Audit logs and temporary files

Each audit has an audit log which users can view. The log is stored in the MIB. The user can set
the number of days for which these logs can be kept.
Audit also creates temporary files in /tmp/LISTDIR in the MIB.
These files contain objects and their attributes if audit finds that these objects do not
exist in either the BSS or MIB. These temporary files should not be altered in any way.
Aborted/unapplied audits store files in this directory. All files in this directory which are older
than three days can be deleted.
See Managing audit logs on page 10-29 for further details.

Audit restrictions
An audit can only be used to upload information about network elements (NEs) or Commslinks
which exist, and are correctly configured as child elements of added BSSs and RXCDRs. An
audit only obtains information on Commslinks internal to the BSS, that is, between sites. It
does not provide information on Commslinks between NEs, such as BSS to RXCDR, RXCDR to
OMC-R or RXCDR to MSC.

Scheduled audits queuing support

Queuing support is used if more than one audit is scheduled, and if the first audit has not
completed before the start time of the next audit is reached (or a resync, Network Expansion,
or cmutil is also running). Queuing support ensures that an audit is queued, and run after a
previous audit is completed.

Initiating an audit
The audit function can be invoked manually from Navigation Tree, or scheduled using the
Audit Scheduler.
Audit can be invoked from the UNIX command line. This means that the OMC-R GUI does not
have to be started to initiate an audit. Use the following command:
cmdLineAudit [NETWORK | REGION | BSS | RXCDR | SITE | PCU ] <Network Elements>
This command checks the permissions for the user invoking the audit, and then executes an
audit gather and apply to the OMC-R. The audit status and inconsistencies found can be checked
from the audit logs on the OMC-R GUI.

Configuring the Audit Gather phase

An audit process has two phases; gather and apply. The gather phase can be configured to
collect or ignore Call Trace objects. This can be achieved using the audit.cfg file.

68P02901W17-T

10-5
Jan 2010

Per Site Audit feature

Chapter 10: Auditing

Procedure 10-1 Configuring the Audit Gather phase

To enable or disable the collection of Call Trace details, open the audit
configuration file:
/usr/omc/config/global/audit.cfg .

Set the flag GATHER_CALLTRACE to 1 to collect Call Trace objects during

audit gather phase, or set it to 0 to omit Call Trace objects. The default is
0 (omit Call Trace objects).

Save the configuration file.

Per Site Audit feature

Description
The Per Site Audit (PSA) feature significantly speeds up the gather phase when used as part
of daily operations to keep the CM databases of the BSS and OMC MIB in synchronization.
It is of particular use when a daily unload of CM data is required for applications such as
a Master CM OMC.
Both the BSS and OMC MIB BTS objects contain a counter designed to track the CM changes
(effectively everything on the 02 object which holds the BSS configuration). This counter goes
out of synchronization if the site on the BSS contains a CM change not applied to the site on
the MIB. When an audit of a BTS, BSS, or Network is invoked, first the counter of each site is
checked, and the audit collect phase only runs for a site if the counter of that site is out of
synchronization. Since the gather phase of audit can take 90-98% of the total audit time, when
there are only a few sites in a BSS with inconsistencies, the gather phase is faster.
All parameters required for radio frequency and transmission replanning, or expansion, are
supported. This could provide a significant saving where there is a need to run Network audits
on a nightly basis. PSA can also be utilized in conjunction with Multiple Site Audit (Cherry
Picking).
The initial PSA design does not support the hardware inventory management. The serial
numbers of the boards are not stored in the BSS 02 object, and are checked for separately. The
serial numbers are not checked if the CM database of the site shows no change.

Enabling and disabling the Per Site Audit functionality

The PerSiteAuditLevel flag determines whether a Per Site Audit functionality is used. This
flag is set to 0 (Off), by default, in the file:
/usr/omc/config/global/audit.cfg
Also the environment variables PER_SITE_AUDIT and PER_SITE_AUDIT_DEBUG must be
enabled in:
/usr/omc/config/global/env/Common.csh

10-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Per Site Audit feature

See Operating Information: OMC-R System Administration (68P02901W19) for further details.
The PER_SITE_AUDIT environment variable should only be switched on once, and controls
the site audit counters for the MIB.
To enable Per Site Audit functionality, follow these steps:

Procedure 10-2 Enable Per Site Audit functionality

1

In /usr/omc/config/global/audit.cfg , change the PerSiteAuditLevel

value to 1 (On) as follows:
PerSiteAuditLevel 1
Result: The audit.cfg file is parsed before each audit is performed, so
an OMC-R stop/start is not required to reset the flag.

To enable the PER_SITE_AUDIT and PER_SITE_AUDIT_DEBUG

environment variables, type the following lines in
/usr/omc/config/global/env/Common.csh:
setenv PER_SITE_AUDIT ON
setenv PER_SITE_AUDIT_DEBUG ON

An OMC-R start/stop is required if the settings of PER_SITE_AUDIT or PER_SITE_AUDIT_DEBUG

are changed.

NOTE
Per Site Audit can also be enabled per audit using the Audit Type field in the
auSchedule Detailed View, see Selecting the Audit Type on page 10-22 for details.

Limitations
When PSA is enabled, the entire BSS is still audited in the following cases:

CSFP swap of new database.

Downloading of new database.

When PSA is enabled, the following changes can occur without affecting the PSA Site counters:

Call Traces can be created and/or deleted.

Hardware Version Numbers (HVNs), Serial numbers, Kit numbers, FRUs, and FR_UNIT of
boards can change. PSA does not support Inventory management. The serial numbers of
the boards are not stored in the BSS 02 object, and are checked for separately. The serial
numbers are not checked if the CM database of the site shows no change.

NOTE
An RXCDR and its child objects, and a PCU and its child objects, do not have a
PSA counter, so an audit of these objects always proceeds.

68P02901W17-T

10-7
Jan 2010

Auditing recommendations

Chapter 10: Auditing

Auditing recommendations

Recommended use of audit

The following are recommendations for using audit:

Use the Audit scheduler to implement auditing of the network. Schedule each BSS to be
audited at least once per week, or once daily if Per Site Audit is being used. Use Audit
Scheduler->Periodic->Apply to OMC. The Apply to OMC option requires no operator
interaction.

Use One Shot Audits (using the Navigation Tree or Scheduler) after a new BSS download,
or if the OML has been down for a long time and there has been local maintenance work on
the BSS.

NOTE
Normal CM changes through rlogin do not require an audit of the BSS. If the
OML is in service, and there is no MIB lock on the corresponding object, any
database changes to existing devices/functions through rlogin are immediately
propagated to the MIB. These are logged through attributeStateChangeEvents
(AVCs) in the event logs. Any new devices created/deleted have corresponding
objects created/deleted for them in the MIB. These are also logged through
objectCreateEvents/ objectDeleteEvents in the event logs.

10-8

Network-wide audits should only be scheduled where audit is expected to highlight minor
network configuration changes. Each Network-wide audit should be completed before the
beginning of the CM morning operator shift. Evaluate how long on average it takes to
complete a Network-wide audit on the Network. If it takes too long, use the BSS Audit.

Do not run One Shot Audits if they conflict with Resync, Network Expansion, or cmutil. Set
up scheduled audits, as they are queued if another process has control of the MIB lockfile.

Audits can only be aborted during the collection phase. The apply phase is usually quite
fast and Motorola recommends it is allowed to complete. However, if problems do occur,
the only way to stop the audit is to initiate an OMC-R stop/start.

Always check the Audit Inconsistencies logfile for failures on the Apply phase. One of the
most common causes of failure to apply is dummy LACs-CIDs in the MIB which prevent
real Cells/Neighbors being audited in.

For multiple OMC-Rs, set up shell scripts which search the omcaudit logfiles for au: and
cm: messages and report on failures. The OMC-R showing the most failures should be
investigated before investigation of other OMC-Rs. See Operating Information: OMC-R
System Administration (68P02901W19) for further details.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Auditing scenarios and NE basis

Auditing scenarios and NE basis

Typically, Audit is used in the following scenarios:

Scenario A: OMC-R started for the first time (a newly installed OMC-R system).

Scenario B: New NEs added to the network.

Scenario C: BSS receives a new database download due to a replan.

Scenario D: Sites/paths are reparented.

Scenario E: Network data is thought to be different from that in the CM MIB. Typically, an
audit would be requested in any of the following situations:
Following a long OML outage, where it is obvious events have been lost.
X.25 links have been unstable and data sent from the BSS may have been lost.
Changes through TTY rlogin did not update the MIB. This may be caused by Detailed
Views remaining open in Edit mode, or MO locks remaining, resulting from another
application not finishing cleanly, which locks the MIB.

Scenario F: Operator scheduled periodic audit at the OMC-R.

Audit on a NE basis
Audit on a per NE basis is the preferred way of using audit and is the recommended way to
capture significant network changes. This includes Scenarios A to E. In these scenarios, audits
should be carried out and completed one NE at a time.

Network-wide audits
In general, Network-wide audits are not recommended, though it is a selectable option from the
Navigation Tree on the OMC-R GUI and from the audit scheduler.
Field experience has shown that a Network-wide audit, initiated at the end of the last CM
operator shift (typically 22.00 hours), has often not completed before the beginning of the
morning CM operator shift. The audit locks the CM MIB while collecting/applying and if the
Apply phase is running the audit cannot be aborted.
The recommendations for Network-wide audits are as follows:

Network-wide audits should only be used in cases where audit is expected to highlight
minor network configuration changes (Scenarios E and F), and only if the changes are
minor.

Network-wide audits should not be done on a network when there are NEs in the network
that have not been previously audited (Scenarios A to D, and Scenarios E and F if the
changes are major).

68P02901W17-T

10-9
Jan 2010

Audit logs and expired logs

Chapter 10: Auditing

Audit logs and expired logs

Audit logs require significant memory, so the number of audit logs retained on the system
should be kept to a minimum. The number of days that the audit logs are held is determined by
the attribute setting of the Audit Log Management window (GUI Front Panel-> Admin->Audit
Log Management). Audit logfiles older than this setting are deleted the next time an audit
initiates. The recommended setting is one day.
For a scheduled audit, once an audit has collected the inconsistencies, the audit log can
sometimes have a status of Expired on the logfile. Expired means that the audit did not apply
the inconsistencies to the OMC-R. The audit log is set to expired if an OMC-R stop/start occurs
before the audit is applied.

Auditing problems
Most common causes of audit failure are:

A new gsmcellid for the BSS is detected on the network which exists in a different BSS in
the same OMC-R. In this case the entire audit apply fails.
Solution: Carefully choose the order of the BSSs to be audited, especially when
reparenting has occurred. If many BTS and LAC-CI reparents have occurred, it may be
faster to use HierDelete to delete the BSSs, recreate the BSS objects, and rerun the audits

The BSS does not have sufficient resource.

Solution: Check that the BSS has sufficient LCFs and, if necessary, an OMF. Sometimes,
for example, audits can fail if the LCF is code loading. Solution: Equip the appropriate
OMF or LCF, and rerun the Audit.

OML reset occurs in the middle of the outage.

Solution: Rerun the Audit after OML comes back into service.

OMC Event Interface fails in the middle of the collect.

Solution: Rerun the Audit after the Event Interface comes back into service

OMC is stop-started.
Solution: Rerun the Audit after OMC stop start.

NOTE
Completed audit collects cannot have their inconsistencies applied after an
OMC Stop-Start.

MIB corruptions.
Solution: Run the /usr/omc/current/sbin/cleanMib script in cleanup mode and then
rerun the audit. For more information on this script, please refer to the OMC-R Software
Release Notes.

10-10

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

of Audit, Proxy Cell sync, Network Expansion, and propagation

Proper use

Proper use of Audit, Proxy Cell sync, Network Expansion, and

propagation
Misuse of the Configuration Management procedures as described in Audit Problems can
compromise the integrity of real network data. This can lead to Neighbors having the wrong
LAC-CI, and causing handovers to fail. There are three typical scenarios in which this can occur:

Immediately after a reconfiguration of the network.

When a replan or expansion of the network resulted in LACs, BSICs, or ARFCNs being
deployed using CSFP swap.

A conventional download of a new (02 object) BSS CM database.

NOTE
It is important that all BSSs involved in an audit have been audited into the MIB
before any online propagation changes, or proxy cell synchronization (pcell
sync) between OMCs are run.

Immediately after a replan, Motorola recommends disabling the routine BSS scheduled audits
and concentrating only on those involved in the CSFP swap. Monitor the progress of the Audits
carefully in the Audit Logs GUI. If any problems occur, diagnose the cause of the problem (open
the omcaudit logfile if necessary), fix the problem, and then rerun the audit.

68P02901W17-T

10-11
Jan 2010

Auditing the network using the OMC-R GUI

Chapter 10: Auditing

Auditing the network using the OMC-R GUI

Introduction
An audit can only be used to upload information about network elements (NEs) or Commslinks
which exist and are correctly configured as child elements of added BSSs and RXCDRs.
An audit only obtains information on Commslinks internal to the BSS, that is, between sites. It
does not provide information on Commslinks between NEs, such as BSS to RXCDR, RXCDR to
OMC-R or RXCDR to MSC.
Use the procedures detailed elsewhere in this manual to manually create MSCs, OMC-Rs, BSSs
and RXCDRs, and the Commslinks between them.

NOTE
Obtain permission from the OMC-R System Administrator before auditing a network.

Auditing the network using the Navigation Tree

The network can be audited either from the Network Detailed View form or from the Navigation
Tree. To audit the entire network from the Navigation Tree, use the following procedure:

Procedure 10-3 Audit the network using the Navigation Tree

1

From the Front Panel, click the Config Mgt icon to display the
Navigation Tree.

Click the network instance button. This changes the color of the
network button.

Select Config Mgt - Audit from the Navigation Tree menu bar.
Result: The network audit is initiated and a confirmation box is
displayed. The message requests the user to look at the audit logs
for the status.

Displaying the Audit Logs

To display the Audit Logs, select Config Mgt - Audit logs from the Navigation Tree menu bar
(or through the Admin icon on the Front Panel - Audit logs).
The Audit Logs form opens and contains the active audit log.

10-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Auditing the network using the Navigation Tree

Applying audit inconsistencies to OMC from the Audit Logs form

To apply audit inconsistencies to OMC from the Audit Logs form, use the following procedure.

NOTE

Audit inconsistencies can also be applied from the Audit Inconsistency List

During the application of audit inconsistencies, any object locks in the database
are ignored. For example, if a device Detailed View is already open in Edit mode
before the audit is initiated, the Detailed View is closed if any inconsistencies
are applicable to that device Detailed View.

Procedure 10-4 Apply audit inconsistencies to OMC from the Audit Logs form
1

Refer to Viewing an audit log list on page 10-29 and follow steps 1-3.
Result: The Audit Logs form is opened.

Select an audit with inconsistencies from the list of audits displayed.

The selected audit must have the status Finished, otherwise the Apply
to OMC option cannot be selected.

Select the Apply to OMC option from the Options menu. This starts the
process of applying the inconsistencies to the OMC-R.

Displaying the results of an apply inconsistencies process

To display the results of an Apply to OMC process, use the following procedure.

Procedure 10-5 Display the results of an Apply to OMC process

1

To display the results of an Apply to OMC activity, select an audit with the
status Applied to OMC.

From the Display menu, select All, Success, Error, or Failure.

Selecting All, opens the Audit Inconsistency List form with all the records
displayed. The status bar shows the total number of success, error, and
failure records.
Selecting Success, opens the Audit Inconsistency List form showing a list of
success records. The status bar displays a count of the success records.
Selecting Error, opens the Audit Inconsistency List form showing a list of
error records. The status bar display a count of the error records.
Selecting Failure, opens the Audit Inconsistency List form showing a list of
failure records. The status bar display a count of the failure records.

Closing the audit logs window

Close the audit window by selecting File Close from the menu bar.

68P02901W17-T

10-13
Jan 2010

Auditing a BSS/RXCDR using the OMC-R GUI

Chapter 10: Auditing

Auditing a BSS/RXCDR using the OMC-R GUI

Auditing a BSS or RXCDR using the Navigation Tree

To audit an individual BSS or RXCDR, use the following procedure:

Procedure 10-6 Audit a BSS or RXCDR using the Navigation Tree

1

From the Front Panel, click the Config Mgt icon to display the
Navigation Tree.

If the BSS/RXCDR button is not visible, click the folder icon next to the
network name to expand the Navigation Tree to the second level.

Click the folder item next to the BSS/RXCDR button to display all
existing BSS/RXCDR instances.

Click the required BSS/RXCDR button.

Result: The button changes color.

Select Config Mgt Audit from the Navigation Tree menu bar.
(Alternatively, an audit can be initiated from the BSS or RXCDR
Detailed View form by selecting Edit Detailed View Options
Audit).
Result: The BSS or RXCDR audit is initiated and a confirmation box
displayed. The message requests the user to look at the audit logs
for the status.

Displaying the Audit Logs

To display the Audit Logs form, select Config Mgt - Audit logs from the Navigation Tree menu
bar (or through the Admin icon on the Front Panel - Audit logs).
The Audit Logs form opens and contains the active audit log.

Applying audit inconsistencies to OMC from the Audit Logs form

To apply audit inconsistencies to OMC from the Audit Logs form, use the following procedure.
(Audit inconsistencies can also be applied from the Audit Inconsistency List.)

NOTE
During the apply of audit inconsistencies, any object locks in the database are
ignored. For example, if a device Detailed View is being displayed in Edit mode it is
closed automatically when the Audit Apply is initiated.

10-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Auditing a BSS or RXCDR using the Navigation Tree

Procedure 10-7 Apply audit inconsistencies to OMC from the Audit Logs form
1

Refer to Viewing an audit log list on page 10-29 and follow steps 1-3.
Result: The Audit Logs form is opened.

Select an audit with inconsistencies from the list of audits displayed.

The selected audit must have the status Finished, otherwise the Apply
to OMC option cannot be selected.

Select the Apply to OMC option from the Options menu. This starts the
process of applying the inconsistencies to the OMC-R.

NOTE
After applying the inconsistencies to the OMC-R, if the Network Entity Ids of a BSS
or RXCDR are duplicated, an NE Id Inconsistency List window appears. Use the
information in the window to resolve the inconsistency, see Resolving auditing NE Id
inconsistencies on page 10-16.

Displaying the results of an apply inconsistencies process

To display the results of an Apply to OMC process, use the following procedure.

Procedure 10-8 Display the results of an Apply to OMC process

1

To display the results of an Apply to OMC activity, select an audit with the
status Applied to OMC.

From the Display menu, select All, Success, Error, or Failure.

Selecting All, opens the Audit Inconsistency List form with all the records
displayed. The status bar shows the total number of success, error, and
failure records.
Selecting Success, opens the Audit Inconsistency List form showing a list of
success records. The status bar displays a count of the success records.
Selecting Error, opens the Audit Inconsistency List form showing a list of
error records. The status bar display a count of the error records.
Selecting Failure, opens the Audit Inconsistency List form showing a list of
failure records. The status bar display a count of the failure records.

Closing the audit logs window

Close the audit window by selecting File Close from the menu bar.

68P02901W17-T

10-15
Jan 2010

Resolving auditing NE Id inconsistencies

Chapter 10: Auditing

Resolving auditing NE Id inconsistencies

To resolve auditing inconsistencies using the NE Id Inconsistency List, follow these steps:

Procedure 10-9 Resolve auditing NE Id inconsistencies

1

If the NE Id Inconsistency List window is not displayed as a result of

an inconsistency found by the audit process, select the Network or the
required BSS or RXCDR in the Navigation Tree and select Options - NE
id Inconsistencies from the menu bar.
Result: If Network is selected, the window lists the Name and Network
Entity Id of all the NEs that have duplicate Network Entity ids. When
a BSS or RXCDR is selected, the window lists the Name and Network
Entity Id of all the Network Entity Ids which are the same as selected
NE. The list is sorted by Network Entity Ids in ascending order.

Select the network element to be corrected.

Result: The NE is highlighted.

Click the Make Unique button.

Result: A new dialogue box opens.

Enter a unique Network Entity id for the selected network element,

or click the Get Free Id button to enter the next free unique network
entity id in the Enter New Network Entity Id field.

Click OK to reset the Network Entity Id. (Clicking Cancel cancels the
operation.)
Result: The OMC-R displays the following warning message if a BSS
is selected: Warning: Changing the Network Entity Id will
result in cycling all Associated RXCDR devices which are
BUSY_UNLOCKED. Cycling these devices will result in the loss
of all call traffic from this BSS to those RXCDRs. This
loss of call traffic may be avoided if cic_validation is
disabled at the BSS. The connected remote Associated BSS
entities may need to be updated at the following RXCDRs:
<list of RXCDRs> Do you wish to continue? The OMC-R displays
the following warning message if an RXCDR is selected: Warning:
Changing the Network Entity Id will result in cycling all
Associated BSS devices which are BUSY_UNLOCKED. Cycling
these devices will result in the loss of all call traffic
from those BSSs to this RXCDR. This loss of call traffic may
be avoided if cic_validation is disabled at the BSS for this
RXCDR. The connected remote Associated RXCDR entities may
need to be updated at the following BSSs: <list of BSSs> Do
you wish to continue?

10-16

Click OK to continue or Cancel to cancel.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Multiple site audits

Multiple site audits

Selecting multiple site audits

Perform the following procedure to select multiple site auditing:

Procedure 10-10 Select multiple site audits

1

Click the Config Mgt icon on the Front Panel.

Result: The OMC-R GUI Navigation Tree opens.

Select multiple sites by holding down the Ctrl key while making the
selections.

NOTE
A maximum of 50 sites can be selected for a Multiple Site
Audit.
3

Select Config Mgt - Audit from the menu bar.

Result: The following message is displayed in the status bar:
Audit Operation successfully dispatched. Followed by: Audit
Started. Check Audit Logs for Status.

68P02901W17-T

10-17
Jan 2010

Multiple BSS/RXCDR audits

Chapter 10: Auditing

Multiple BSS/RXCDR audits

Auditing multiple BSS/RXCDRs

Two or more BSSs or RXCDRs can be audited from the OMC-GUI.

Selecting multiple BSS/RXCDRs for auditing

Perform the following procedure to select multiple BSSs or RXDCRs for auditing:

Procedure 10-11
1

Selecting multiple BSS/RXCDR audits

Click the Config Mgt icon on the Front Panel.

Result: The OMC-R GUI Navigation Tree opens.

Select Multiple BSSs or RXCDRs by holding down the Ctrl key while
making the selections.

Select Config Mgt - Audit from the menu bar.

Result: The following message is displayed in the status bar: Audit
Operation successfully dispatched., followed by: Audit Started.
Check Audit Logs for Status.

Viewing the status of Multiple BSS Audits

To view the status of a multiple BSS audit, see Displaying the status of a Multiple BSS Audit
on page 10-26.

10-18

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Scheduling an audit

Scheduling an audit

List of scheduling procedures

The following is a list of procedures that are performed using the Audit Scheduler Admin Option.
These activities are described in the following subsections.

Creating a scheduled audit.

Modifying a scheduled audit.

Printing a scheduled audit list.

Deleting a scheduled audit list.

NOTE
If the OMC-R timezone incorporates a daylight-saving scheme where a one or
two hour offset is applied to the OMC-R during the summer months, care should
be taken not to schedule an audit when the time is moved back at the end of
the summer, it could accidentally run twice; or when the clock is moved forward
at the start of the summer, it might not run at all. The change from summer to
winter time, and the change from winter to summer time, usually occurs in the
hours after midnight on a Friday, Saturday, or Sunday, depending on the country.

Creating a scheduled audit

To schedule an audit, use the following procedures.

Creating a scheduled audit

To create the audit schedule, follow these steps:

Procedure 10-12 Create an audit schedule

1

Select the Admin icon from the Front Panel to open the Admin Options
window.

Select the Audit Scheduler option in the Admin Options window.

Continued

68P02901W17-T

10-19
Jan 2010

Creating a scheduled audit

Chapter 10: Auditing

Procedure 10-12 Create an audit schedule (Continued)

3

Click OK.
Result: The Audit Scheduler window opens and displays a list of
all scheduled audits, detailing their Name, Status, Deferred Time (if
applicable), Start and End Times, Intervals, Execute Mode, Update
Mode, Audit Type, Per Site Logging, Neighbor Propagation, and
Operator.

To create an audit, select Edit Create from the Audit Scheduler

window.
Result: The auSchedule Detailed View window is displayed.

Entering the audit schedule details

To enter the details of the audit schedule, follow these steps:

Procedure 10-13 Enter audit schedule details

1

Click the Scheduled Elements button in the auSchedule Detailed View.

Result: The Navigation Tree is displayed.

Select to the network objects to be audited.

NOTE
It is possible to select:

One or more BSS/RXCDRs.

One or more sites.

A region.

A single PCU.

Network (omcadmin only).

Select Audit from the Config Mgmt menu.

Result: The Navigation Tree window closes and the Scheduled
Elements field in the Schedule Detailed View displays:

10-20

The name of the selected network object.

Multiple BSS/RXCDRs, if multiple BSS/RXCDRs have been

selected.

Multiple sites, if multiple sites have been selected.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating a scheduled audit

Setting the execute mode and times

There are two Execute modes to choose from on the auSchedule Detailed View: Oneshot and
Periodic. Setting the Execute Mode field to Oneshot means that an audit can be scheduled to
start at a set time, and once completed, it will not be rescheduled. Setting the Execute Mode to
Periodic schedules an audit of a Network Element to start at a set time, to run to completion,
and to be repeated after the time specified in the Interval field has elapsed. This continues to
repeat until the End Time has been achieved.
To set the Execute Mode, follow these steps:

Procedure 10-14 Set the Execute Mode

1

To change the Execute Mode field from Periodic to Oneshot, or Oneshot

to Periodic, click the Execute Mode button.

Hold the left mouse button down, and scroll to the required option.
Once the option is highlighted, release the mouse button.
Result: The selected mode is displayed in the field.

Click the Start Time or End Time field depending on which one needs
changing.
Result: The selected parameter is highlighted in black.

NOTE
Only the Start time field needs to be specified for Oneshot
auditing. The date and times are shown in the following
format: Month/Day/Year Hour:Minute:Second
4

Use the up/down arrow symbols to the right of the Start Time field to
change the date and time to the required value.

For Periodic Auditing, the End Time field must be set in the same way
as for the Start Time field. This field should be set to the date and time
after which this Audit function will not be restarted.

NOTE
This does not mean that an audit in progress will be stopped
when this time has been achieved.

68P02901W17-T

For Oneshot Auditing, the End Time and Interval fields are disabled, so
go to Setting the Update Mode.

For Periodic Auditing, the Interval field must be set corresponding to

the number of hours between the start of corresponding audits.

The User Name field contains the name under which the user has
logged on to the system. This may be changed for the purpose of the
current audit only.

10-21
Jan 2010

Creating a scheduled audit

Chapter 10: Auditing

Setting the Update Mode

When an audit is performed, the information obtained can be:

Used to update the network element in question.

Applied to the OMC-R.

Performed in interactive mode.

To set the Update Mode, follow these steps:

Procedure 10-15

Set the Update Mode

Click the Update Mode field.

Click the button to select the required Update Mode.

NOTE
Use the Audit scheduler to implement auditing of the
network. Ensure that each BSS is scheduled to be audited at
least once per week. Use the menu options: Audit Scheduler
- Periodic - Apply to OMC. The Apply to OMC menu option
does not need operator interaction. If Audit is invoked from
the Navigation Form, the Apply to OMC menu option is not
available.

Selecting the Audit Type

The type of audit to be performed can also be selected in the auSchedule Detailed View, using
either of the following Audit Type field options:

Full Audit (that is, a full audit is performed on all sites).

Per Site Audit.

To set the Audit Type, follow these steps:

Procedure 10-16 Set the Audit Type

1

Click the Audit Type field.

Click the button to select the required Audit Type.

Continued

10-22

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Creating a scheduled audit

Procedure 10-16 Set the Audit Type (Continued)

NOTE
If the environment variable PER_SITE_AUDIT is set, and
if the environment variable PerSiteAuditLevel is 0 in the
audit.cfg file, the default Audit Type is Full Audit. If
PerSiteAuditLevel is equal to 1, 2 or 3, the default Audit
Type is Per Site Audit. If the audit.cfg file is not present, the
default Audit Type is Full Audit. If the environment variable
PER_SITE_AUDIT is not set, the default Audit Type is Full
Audit. See Per Site Audit feature on page 10-6 for further
details.

Specifying the contents of Per Site Logging

If Per Site Audit has been selected in the Audit Type field in the auSchedule Detailed View,
the content of the Per Site Logging field can be specified using one of the following Per Site
Logging field options:

List All Sites meaning all sites are logged, regardless of whether a full or Per-Site audit
is performed on the site.

List Audited Sites meaning only those sites for which a full audit is performed are logged.

List Unaudited Sites meaning only those sites for which a full audit is not performed
should be logged.

To specify the content of Per Site Logging, follow these steps:

Procedure 10-17

Specifying the contents of Per Site Logging

Click the Per Site Logging field.

Click the button to select the required Per Site Logging content.

NOTE
If the environment variable PER_SITE_AUDIT is set, and if
the environmental variable PerSiteAuditLevel is set to 1 in
audit.cfg file, the default of Per Site Logging is List All Sites.
If PerSiteAuditLevel is 2, the default of Per Site Logging is
List Audited Sites. If PerSiteAuditLevel is 3, the default is
List Unaudited Sites. See Per Site Audit feature on page
10-6 for further details.

68P02901W17-T

10-23
Jan 2010

Modifying a scheduled audit

Chapter 10: Auditing

Selecting Neighbor Propagation after Audit

It is possible to select whether neighbor propagation occurs after the audit using one of the
following Neighbor Propagation after Audit field options:

Yes (default if the environment variable NBR_PROP_AFTER_AUDIT is set, see Propagating

cell changes to neighbor cells after an audit on page 10-35 for further details).

No (default if the environment variable NBR_PROP_AFTER_AUDIT is not set, see

Propagating cell changes to neighbor cells after an audit on page 10-35 for further details).

To select Neighbor Propagation after Audit, follow these steps:

Procedure 10-18 Selecting Neighbor Propagation after Audit

1

Click the Neighbor Propagation after Audit field.

Click the button to select whether Neighbor Propagation after Audit

is to occur.

Initiating the scheduled audit

When all the information has been entered into the auSchedule Detailed View window, the
scheduled audit can be created. Follow Procedure 10-19 to create the scheduled audit:

Procedure 10-19 Initiate the scheduled audit

1

Select File Create from the menu bar. The new Scheduled Audit is
created and can be viewed in the Audit Scheduler window. Make the
required changes to a created network. Refer to Modifying a scheduled
audit on page 10-24 for more information.

Close the Detailed View window by selecting File Close from the
menu bar.

Close the Audit Scheduler window by selecting File Close from

the menu bar.

Modifying a scheduled audit

All limitations which apply to Auditing must be adhered to when altering a Scheduled Audit. To
modify a scheduled audit, use the following procedure:

Procedure 10-20 Modify a scheduled audit

1

Open an Audit Scheduler window. For details, see Creating a scheduled

audit on page 10-19.
Continued

10-24

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deferring a scheduled audit

Procedure 10-20 Modify a scheduled audit (Continued)

2

Select the audit to be modified.

Result: The selection is highlighted.
Select Edit Modify from the Audit Scheduler window.

Result: The auSchedule Detailed View window is displayed.

4

Select Edit Edit from the menu bar.

When the required fields have been changed, select File Save.

Close the Detailed view by selecting File Close from the menu bar.

NOTE
The altered Scheduled Audit can be viewed in the Audit
Scheduler window.
7

Close the Audit Scheduler window by selecting File Close from

the menu bar.

Deferring a scheduled audit

It may be necessary to defer a scheduled pending audit to a later time. Use the following
procedure to defer an audit:

Procedure 10-21 Deferring a scheduled audit

68P02901W17-T

Open the Audit Scheduler window.

Select one or more pending or blocked-pending scheduled audits from the

list displayed.

Select either Defer, Defer All, Undefer or Undefer All from the Edit menu.
(Alternatively, select an audit from the Audit Scheduler window and then
select Detailed View from the Edit menu). The auSchedule Detailed View is
displayed.
Defer All and Undefer All options are available to an omcadmin user only.
The Defer and Undefer options are only sensitive for the pending and
blocked-pending scheduled audits owned by the user. If more than one audit
is selected and if any of the selected items is not owned by the user or if
the status of any of the selected items is not pending or blocked-pending,
the Defer and Undefer options cannot be selected. Selecting Edit-Defer
displays the Defer window. If more than one audit has been selected, the
Defer Multiple Scheduled Audits window is displayed.
Selecting Edit Defer All displays the Defer All window.

Enter the date and time the audit is to be deferred to. Use the up or down
arrow buttons to change a value.

Click OK to apply the deferred time to the selected audit.

10-25
Jan 2010

Displaying the network elements in a scheduled audit

Chapter 10: Auditing

Displaying the network elements in a scheduled audit

To display the network elements in a scheduled audit, use the following procedure:

Procedure 10-22 Displaying the network elements in a scheduled audit

Open the Audit Scheduler window.

Select a scheduled audit from the list displayed.

Select NE List from the Edit menu. The NE List window is displayed with the
name of the scheduled audit shown in the title bar. (If a Multiple Site audit
is selected NE List Multiple Sites is displayed in the title bar.) The network
element name is shown for each network element in the scheduled audit.

If required, use the Print option in the File menu to print the status.

Use the Close option in the File menu to close the window.

Displaying the status of a Multiple BSS Audit

To display the status of a Multiple BSS Audit, use the following procedure:

Procedure 10-23 Displaying the status of a Multiple BSS Audit

Select Config Mgt - Audit logs from the Navigation Tree menu bar (or
through the Admin icon on the Front Panel - Audit logs). The Audit Logs
window is displayed.

Select the audited item from the list displayed.

Select Audit Progress from the Options menu. The Audit Progress window is
displayed with the name of the audit item shown in the title bar.
For each element of the audit, the following details are shown:

10-26

Network Element name.

Status: can be either Pending Gather, Gather in Progress, Pending

Apply, Apply in Progress, Apply Complete, Aborted, or Timeout
Occurred.

Actual Start Time: the date and time the audit process started.

Actual End Time: this is the date and time the Apply phase completed.

If required, use the Print option in the File menu to print the status.

Use the Close option in the File menu to close the window.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Printing a list of scheduled audits

Printing a list of scheduled audits

To print a list of scheduled audits, use the following procedure:

Procedure 10-24 Print a list of scheduled audits

1

Refer to Creating a scheduled audit on page 10-19 and follow steps 1-3.

Select File Print from the Audit Scheduler window menu bar.
Result: The print process is documented in the status bar at the
bottom of the window.

Close the Audit Scheduler window by selecting File Quit from the
menu bar.

Close the Admin Options window by clicking Cancel.

Deleting a scheduled audit

Delete Expired Scheduled Audits from time to time to avoid excess memory being used.

CAUTION
Obtain permission from an OMC-R System Administrator before deleting pending
scheduled audits.
To delete a scheduled audit, use the following procedure:

Procedure 10-25 Delete a scheduled audit

1

Refer to Creating a scheduled audit on page 10-19 and follow steps 1-3.

Select the audit to be deleted in the Audit Scheduler window.

Result: The selection is highlighted.

Select Edit Delete from the Audit Scheduler window.

Result: A confirmation window is displayed.

Click OK.
Result: The Scheduled Audit disappears from the Audit Scheduler
window.

68P02901W17-T

Close the Audit Scheduler window by selecting File Close from

the menu bar.

10-27
Jan 2010

Deleting all scheduled audits

Chapter 10: Auditing

Deleting all scheduled audits

CAUTION
Permission must be obtained from the OMC-R System Administrator before deleting
the scheduled audits.
To delete all scheduled audits, perform the following procedure:

Procedure 10-26 Delete all scheduled audits

10-28

Refer to Procedure 10-12 Create an audit schedule on page 10-19 and follow
step 1 to step 3.

Select Edit Delete All from the Audit Scheduler window.

Result: A confirmation window is displayed.

Click OK.
Result: All non-active Scheduled Audits disappear from the Audit Scheduler
window.

Close the Audit Scheduler window by selecting File Close from the menu
bar.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Managing audit logs

Managing audit logs

Viewing an audit log list

After an audit has taken place, information relating to this audit is placed in an audit log.
This information can be viewed and printed.
To view an audit log list, use the following procedure:

Procedure 10-27 View an audit log list

1

Select the Admin icon on the Front Panel to open the Admin Options
window.

Select Audit Logs option, then click OK.

Result: The Audit Logs window opens and contains a list of
all completed audits, detailing the Audited Item, Status, Errors
experienced, Times, Types, and Owner.

Close the Audit Logs window by selecting File Close from the menu
bar.

Printing an audit log list

To print an audit log list, use the following procedure:

Procedure 10-28 Print an audit log list

1

Refer to Viewing an audit log list on page 10-29 and follow steps 1 to 3.

To print the list of Audit Logs, select File Print from the Audit Logs
window menu bar.
Result: The output is sent to the default printer, the progress of the
printing is detailed in the status bar.

Close the Audit Log window by selecting File Close from the menu
bar.

Aborting an audit in progress

As soon as an audit commences, details of the audit are displayed in the Audit Log list.

68P02901W17-T

10-29
Jan 2010

Viewing an audit inconsistency report

Chapter 10: Auditing

NOTE
When an audit is in progress (known as the collection phase) the Status field in the
Audit Log list is set to Active. Audits can only be aborted during the collection phase.
The apply phase of an audit is quite quick and it is recommended that it is allowed to
complete. However, if problems occur during the apply phase, the only way to stop
the audit is to do an OMC-R stop/start.
To abort an audit in progress, use the following procedure:

Procedure 10-29 Abort an audit in progress

1

Refer to Viewing an audit log list on page 10-29 and follow steps 1-3.
Result: The Audit Logs window opens.

From the Audit Log list, select the audit to be aborted.

NOTE
An audit in progress is denoted in the Audit Log list by the
setting of the Status field to Active.
3

Select Options Abort from the menu bar.

Result: A confirmation window is displayed.

Click OK.
Result: The Audit Log list is updated and the Status field displays
Aborted.

Close the Audit Log window by selecting File Close from the menu
bar.

Viewing an audit inconsistency report

Types of inconsistencies
After an audit has taken place, information relating to the audit is placed in an Audit Log. Any
inconsistencies found between the NE and OMC-R configuration database are placed in an
inconsistency list. This information can be viewed and printed.
An inconsistency list is produced if an object exists in the:

10-30

MIB but not in the BSS.

BSS but not in the MIB.

MIB and the BSS, but the attribute values differ.

MIB and the BSS, but the versions differ.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Printing an inconsistency report

Viewing an audit inconsistency report

To view an audit inconsistency report for a particular audit, use the following procedure:

Procedure 10-30 View an audit inconsistency report

1

Refer to Viewing an audit log list on page 10-29 and follow steps 1-3.
Result: The Audit Logs window is opened.

From the audit log list, select the audit from which any inconsistencies
should be viewed.
Result: The selected audit is highlighted.

NOTE
An audit inconsistency report is only valid for an audit with a
status field of either Finished or Applied.
3

Select File Open from the menu bar.

Result: An audit inconsistency report window is displayed detailing all
elements where inconsistencies were found during the audit.

Close the audit inconsistency report by selecting File Close from

the menu bar.

Printing an inconsistency report

To print an audit inconsistency report, use the following procedure:

Procedure 10-31 Print an audit inconsistency report

1

Refer to Viewing an audit log list on page 10-29 and follow steps 1-3.
Result: The Audit Logs window is opened.

Select an audit log from which the audit inconsistencies are to be

printed.

Select File Open from the menu bar.

Result: An Audit Inconsistency report window is displayed.
Continued

68P02901W17-T

10-31
Jan 2010

Updating the database with inconsistencies

Chapter 10: Auditing

Procedure 10-31 Print an audit inconsistency report (Continued)

4

To print the Audit Inconsistency List, select File Print View from the
Audit Inconsistency List window.
Result: The output is sent to the default printer.

Close the Audit Inconsistency List by selecting File Close from the
menu bar.

Close the Audit Log window by selecting File Close from the menu
bar.

Close the Admin Options window by clicking Cancel.

Updating the database with inconsistencies

To update the database with the inconsistencies found during an audit, use the following
procedure:

Procedure 10-32 Update the database with inconsistencies

1

Refer to Viewing an audit inconsistency report on page 10-30 to open

an Audit Inconsistency report window. If the Status column is set to
Finished, the collection phase of the audit has completed.

Select Options Apply to OMC, to update the configuration database

at the OMC-R.
Result: A confirmation window is displayed.

Click OK to continue or Cancel to abort.

Result: The progress of the procedure is documented in the status bar.

NOTE
When an audit is in progress (known as the collection phase)
the Status field in the Audit Log list is set to Active. Audits
can only be aborted during the collection phase. The apply
phase of an audit is quick and it is recommended that it is
allowed to complete. However, if problems occur during
the apply phase, the only way to stop the audit is to do an
OMC-R stop/start.
4

10-32

When complete, select File Close to close the window.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting audit logs

Deleting audit logs

Audit Log Management deletes Audit logs after a predefined period. The period is configurable
between one and seven days. The logs may also be deleted manually.

NOTE
If the OMC-R is stop/started, the Audit Logs remain undeleted until the period is
reached after the restart.

Setting the audit logs delete period

A period of time can be set to retain the audit log files, after which the OMC-R automatically
deletes the files. The default setting does not delete the Audit Logs. To set the delete period,
use the following procedure:

Procedure 10-33

Set the audit logs delete period

Select the Admin icon on the Front Panel. The Admin Options window
opens.

Select the Audit Log Management option, then click OK.

Result: The Audit Log Management window is displayed.

Select Edit Edit.

Enter the period after which the Audit Logs are to be deleted.

Select File Save to complete the procedure.

Select File Close to close the window.

Deleting an audit log

Audits, which have had their inconsistencies applied to the OMC-R, are automatically deleted
at the start of a new audit. The following procedure deletes the audit logs that have not had
their inconsistencies applied to the OMC-R.
To delete an Audit Log, use the following procedure:

Procedure 10-34 Delete an Audit Log

1

Refer to Viewing an audit log list on page 10-29 and follow steps 1 to 3.
Result: The Audit Logs window is opened.

Select the Audit Log to be deleted.

Select Edit Delete from the menu bar. It is also possible to select
Edit Delete All if all the logs require deletion.
Continued

68P02901W17-T

10-33
Jan 2010

Deleting audit logs

Chapter 10: Auditing

Procedure 10-34 Delete an Audit Log (Continued)

4

Click OK in the confirmation box.

Result: The box closes and the selected Audit Log is removed from
the list.

10-34

Close the Audit Log window by selecting File Close from the menu
bar.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Propagating cell changes to neighbor cells after an audit

Propagating cell changes to neighbor cells after an

audit

Propagation of cell changes after audit

When an audit is complete and the audit inconsistencies have been applied by a user (or
automatically by the OMC-R), the OMC-R can be configured to automatically propagate
to neighbor cells any cell details which have changed. This feature is controlled by the
environmental variable: NBR_PROP_AFTER_AUDIT, which by default is set to Off (0). When
enabled, the propagation to neighbor cells process takes no more than five minutes to complete,
but may prevent users from performing other activities until the process is complete. If the
neighbor propagation is successful, a message is logged in the omc audit log file, along with
details of all the neighbor details which have been changed. If the propagation is unsuccessful
for a neighbor cell, an error message is logged in the omc audit log file and the propagation
process moves to the next neighbor.

Cell details propagated after an audit

For example, if the cell id value (CELL::gsmCellId) for a cell changes as a result of an audit,
the new value is automatically propagated to all neighbor cells pointing to that cell (providing
the neighbor cell contains the original cell id value). Likewise, cell id is also propagated to all
sources pointing to that cell. Table 10-1 gives details of all the values propagated after an audit.

Table 10-1 Values propagated after an audit

Changed cell value

Propagated to

If...

D/base

CELL::gsmCellId

Neighbor::neighbor
GsmCellId in all
neighbors pointing
to the cell.

CELL::gsmCellId

Source::source_gsm
CellId in all sources
pointing to the cell.

CELL::bsic

Neighbor::bsic for
neighbors pointing
to the cell.

bsic of the neighbor

cell differs from the
Cell::bsic.

CM MIB and BSS

CELL::max_tx_ms

Neighbor::ms_txpwr
_max_cell for the
neighbors pointing
to the cell.

ms_txpwr_max_cell
of the neighbor
differs from the
Cell::max_tx_ms
value.

CM MIB and BSS

neighbor cell
contained the original
cell id value.

CM MIB and BSS

CM MIB

Continued

68P02901W17-T

10-35
Jan 2010

Enabling the propagation after audit facility

Chapter 10: Auditing

Table 10-1 Values propagated after an audit (Continued)

Changed cell value

Propagated to

If...

D/base

For a BCCH RTF

RTF::carrier1_arfcn

Neighbor::bcch
Frequency Num for
the neighbors
pointing to the cell
identified by
RTF::carrier1
GsmCellId.

bcchFrequencyNum
for neighbor differs
from the new
RTF::Carrier1_arfcn
value.

CM MIB and BSS

When a new cell

is created, the
following values
are propagated:
CELL::bisc and
CELL::max_tx_ms

Pre-existing
neighbors
(if any) pointing to
the cell.

bsic and
ms_txpwr_max_cell
values for the
neighbor are
different from the
CELL::bisc and
CELL::max_tx_ms.

CM MIB and BSS

New BCCH
RTF is created,
RTF::carrier1
_arfcnvalue

Neighbor::bcch
FrequencyNum for
all neighbors pointing
to the call identified
by the RTF::carrier1
GsmCellId.

bcchFrequencyNum
of neighbors
differs from
RTF::carrier1_arfcn
value.

CM MIB and BSS

Enabling the propagation after audit facility

By default, the propagation after audit facility is disabled. To enable the propagation to
neighbors after audit facility, follow these steps:

Procedure 10-35 Enable the propagation after audit facility

1

Use a text editor to edit the configuration files Common.csh and

Common.sh, which can be found in the following location:
/usr/omc/config/global/env

Set the NBR_PROP_AFTER_AUDIT to ON (1).

Save the configuration file.

Restart the OMC-R.

Result: The restart process uses the new setting.

10-36

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reasons for disabling propagation after audit facility

Reasons for disabling propagation after audit facility

By default, the propagation after audit facility is disabled. However, if the facility has been
enabled, it may need to be disabled at a later date. For example, the facility may need to be
disabled for the following reasons:

To avoid the system being tied up with propagation activities after the audit.

When NBR_PROP_AFTER_AUDIT is set to ON (1), whenever a neighbor is created or updated

in the OMC database by the audit process, the CM MIB searches for the source cells. If the
source cells are not found, the CM MIB creates proxy cells.
In some cases, this is unnecessary because the source cells are in the neighboring BSS
which will be audited into the OMC later. This could generate inconsistencies. For
this reason, it is recommended that NBR_PROP_AFTER_AUDIT is set to OFF during initial
configuration of the network, or an upgrade. NBR_PROP_AFTER_AUDIT can then be set to ON
when the upgrade and audit of all BSSs have completed.

Disabling the propagation after audit facility

To disable the propagation to neighbors after audit facility, follow these steps:

Procedure 10-36 Disable the propagation after audit facility

1

Use a text editor to edit the configuration files Common.csh and

Common.sh, which can be found in the following location:
/usr/omc/config/global/env

Set the NBR_PROP_AFTER_AUDIT to OFF (0).

Save the configuration file.

Restart the OMC-R.

Result: The restart process uses the setting.

68P02901W17-T

10-37
Jan 2010

Time of the last audit

Chapter 10: Auditing

Time of the last audit

Looking up the time of the last audit

To see when the last audit Gather and Apply phases were completed for a Network, Region,
BSS, RXCDR, PCU or site, look at the following fields in the State grouping in the Network,
Region, BSS, RXCDR, PCU or SITE Detailed View, as appropriate:

10-38

Time of Last Audit Gather Complete (timeOfLastAuGatherComplete)

Time of Last Audit Apply Complete (timeOfLastAuApplyComplete)

68P02901W17-T
Jan 2010

Chapter

11
Network Expansion

Network expansion provides mechanisms for copying and pasting existing BTSs, reparenting,
and deleting BTSs, including performing these activities in a daisy chain configuration.
Information about network expansion procedures is given here. The following topics are
described:

Introduction to network expansion on page 11-2.

Copying and pasting a BTS on page 11-6.

Reparenting a BTS on page 11-22.

Deleting a BTS on page 11-34.

Network expansion in a daisy chain configuration on page 11-37.

Troubleshooting Network expansion on page 11-52.

Scheduling network expansion on page 11-54.

Network expansion logs on page 11-67.

Managing network expansion logs on page 11-72.

Configuring a path using Path Configure menu option on page 11-73.

Using flat files on page 11-94.

68P02901W17-T
Jan 2010

11-1

Introduction to network expansion

Chapter 11: Network Expansion

Introduction to network expansion

Overview of network expansion

Network expansion can be performed either on the Off-Line MIB (DataGen) or OMC-R (online)
platform.
Network expansion activities that are available only on the Off-Line MIB (DataGen) are marked
as such in this section.
Network expansion is achieved from the Navigation Tree by being able to:

Create a BTS site by copying and pasting an existing BTS into a BSS configuration.

Reparent a BTS:
By copying a BTS and swapping LACs (this can be intra- or inter-BSS (alternative
reparent)).
Using the reparent option of inter/intra BSS (offline environment only).

Delete a BTS with its associated hardware devices and software functions in a single
operation.

Batch and schedule network expansion operations to run at an appropriate time.

Review transaction logs and maintain a historical record of operations. It allows the
operator to progress intervened batch mode operations.

Configure a path.

Configure timeslot switch support for path configure.

NOTE
Only one network expansion operation can be run at a time (except for path configure).

Fault management functions

If deleting a site, then the site is gracefully shutdown, for example, DRIs are shut down and
RSLs are locked.

NOTE
In the case of online operations, the network expansion application performs
mandatory fault management procedures.

11-2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Prerequisites for using network expansion

Performance management functions

For both platforms, the network expansion application maintains performance management data
on devices. During a copy site operation, the application copies the performance management
configuration (enables statistics, thresholds, and so on) from the original site to the new
site. Similarly during a reparent site operation, the application maintains the performance
management configuration.
Maintenance of performance management is limited to those statistics configured within
the containment of a BTS site. Statistics configured within a BTS site (cell or carrier level)
for example, RF LOSSES TCH or CALL VOLUME DRI, are manipulated during network
expansion. Statistics outside the BTS site at the BSS level, for example CPU_USAGE MAX, are
not manipulated. These sites inherit the configurations from the parent BSS for inter-BSS
operations.

Prerequisites for using network expansion

The command partitioning feature provides a means of partitioning OMC-R users into different
security areas. Before invoking any network expansion facility, enable the network expansion
command partition within the user profile.
By default, the omcadmin user has access to all command partitions. network expansion can
be performed by any user on the Off-Line MIB.

Network expansion restrictions

Network expansion has the following restrictions:

While performing copy site on a gprs enabled cell, the GSL should be equipped.

Before the gprs_enabled parameter can be set, the user must set the parameter
gprs_sig_bvci.

The gprs_enabled command will be rejected under the following conditions:

If the value of the rac is not set for the cell.
If the value of ra_colour is not set for the cell.
pcch_enabled is 1 and there are no res_gprs_pdchs available.
PCU is not equipped.
PCU is equipped, but PSP is not equipped at the PCU.
PCU is equipped, PSP is equipped at the PCU, but there is no default GSL at the PCU.
PCU is equipped, PSP is equipped at the PCU, there is a default GSL at the PCU, but
there is no NSVC in the PCU.
PCU is equipped, PSP is equipped at the PCU, there is a default GSL at the PCU, and
at least one NSVC is present in the PCU.
There is not enough ts for res + switch_gprs_pdchs.
The GPRS feature is restricted.

68P02901W17-T

11-3
Jan 2010

Path error messages recorded in omcaudit log file

Chapter 11: Network Expansion

It is only possible to copy and paste BTSs between BSSs of the same BSGSM software
version and BSSs with the same purchased options/features.

Expansion of circuits, channels, and timeslots are not supported. These may be modified
by using DataGen MCDF tables.

Interactive delete and copy operations are allowed on terminating BTS sites as well sites
within a daisy chain. However, these operations are not supported for daisy chains which
have timeslot switching sites.

Reparent is allowed on a terminating site only.

Batch operations delete, copy, and reparent are allowed on terminating sites only.

Only one network expansion operation is allowed at any one time (except for Path
Configure).

Configuration of collocated RXCDRs or RXCDR sites are not supported.

Path error messages recorded in omcaudit log file

The omcaudit file is a general-purpose log file which records OMC-R system activity. The file
can be found in /usr/omc/logs/omcaudit.
When a BTS is copied and pasted, or reparented, using Network Expansion, the OMC-R creates
error messages in the omcaudit file when it tries to create the associated new paths. These
error messages can be ignored.
These error messages are produced because the OMC-R tries to create a path from the BSC
through any daisy chained sites to the site being created or reparented. When part of the path
exists, the OMC-R tries to recreate it. This produces error messages in the omcaudit file. The
following example shows the error messages which can be generated in the omcaudit file.
2002-07-09 09:58:54 cm: Initiating remote operation - Create PATH
2002-07-09 09:58:56 cm: object created : PATH : NPI_BSS6:SITE-azmi::PATH 0
2002-07-09 09:58:56 cm: object created : Relationship
2002-07-09 09:58:56 cm: error: relationship already exists
2002-07-09 09:58:56 cm: error: relationship already exists
2002-07-09 09:58:56 cm: error: relationship already exists
2002-07-09 09:58:56 cm: error: relationship already exists
2002-07-09 09:58:56 cm: error: relationship already exists
2002-07-09 09:58:56 cm: error: relationship already exists
2002-07-09 09:58:56 cm: error: relationship already exists
2002-07-09 09:58:56 cm: error: relationship already exists
2002-07-09 09:58:56 cm: Initiating remote operation - Create RSL

11-4

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Defining network expansion environment variables

Defining network expansion environment variables

The behavior of network expansion can be configured through the use of environment variables.

Time period for shutdown

The amount of time to do a controlled shutdown is controlled by the environment variable
NX_SHUTDOWN_TIMEOUT. By default, the value is set to 30 seconds. Execute the following
commands to alter the variable:

Procedure 11-1 Modify NX_SHUTDOWN_TIMEOUT

1

Exit the OLM and shut down DataGen (offline environment only refer to System Information: DataGen (68P02900W22). Otherwise,
shutdown the OMC-R (online environment only).

To set the variable, execute the following command from the Xterm
window that the OMC-R starts from:
setenv NX_SHUTDOWN_TIMEOUT <number of Seconds>
where the minimum is 5, the maximum is 300.

Restart DataGen and OLM (offline environment only - refer to System

Information: DataGen (68P02900W22). Otherwise, restart the OMC-R
(online environment only).

Options for selecting an MMS

During a copy or reparent procedure, it is possible to auto-select an MSS (Multiple Serial Link
Interface) when completing a Path Details form. This selection is controlled by the environment
variable NX_PATH_MMS_SELECTION. By default, the first suitable MMS is selected. Execute
the following commands to alter the default:

Procedure 11-2 Modify NX_PATH_MMS_SELECTION

68P02901W17-T

Select the Xterm icon from the OMC-R front panel display.

Edit the Common.csh file by executing the following command:

vi /usr/omc/config/global/env/Common.csh

Add the following lines under the section Network Expansion Variables:
setenv NX_PATH_MMS_SELECTION <0 or 1 or 2>
where:
First suitable MMS is 0
Suitable MMS with the least available timeslots is 1
Suitable MMS with the most available timeslots is 2

Restart DataGen and the OLM (offline environment only - refer to

System Information: DataGen (68P02900W22) Otherwise, restart the
OMC-R (online environment only).

11-5
Jan 2010

Copying and pasting a BTS

Chapter 11: Network Expansion

Copying and pasting a BTS

Introduction to copying and pasting a BTS

To copy and paste a BTS into a BSS, an existing BTS is copied and used as a template to create a
BTS. The new BTS is pasted into the same BSS or another BSS. This is the recommended way
of adding a BTS to a BSS.
Details of the new BTS are entered into a Control form which is made up of three steps:

Step 1 - Equip SITE Hardware Devices.

Step 2 - Equip SITE Logical Link Devices.

Step 3 - Equip SITE Radio Frequency Devices.

Mandatory and optional information must be entered in sequence for each step to complete
the operation successfully. Once each step is complete, the associated devices are equipped.
For example, the site hardware devices (for example, Cabinet, Cage, EAS) are equipped after
completing Step 1. The devices that are equipped in each step are reflected in the Navigation
Tree.
If error messages appear in the omcaudit file during a copy and paste BTS operation, see
Introduction to network expansion on page 11-2, section for details.

Copying and pasting a Horizon II macro BTS

When copying a Horizon II macro BTS, the following devices are not copied:

MSI.

CSFP.

GCLK.

MMS.
Instead, each of these devices is automatically created when the BTP is created at the
new BTS.

Six MMS devices are automatically created at the new Horizon II macro BTS.

Restrictions to copy and pasting a BTS

Only a terminating or spoke BTS in an open daisy chain configuration may be copied and pasted
using this procedure. To copy and paste a site in a daisy chain configuration, see Network
expansion in a daisy chain configuration on page 11-37.

11-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Procedure for copying a BTS

NetEx does not allow a site to be copied from one BSS to another, if one site has the Fast Call
(FastCallOpt) feature unrestricted and the other one has it restricted.
If copying and pasting a BTS causes a Cell, and then an RTF to be created, the following occurs:
1.

Cell parameters init_dl_cs and/or init_ul_cs defined as Coding Schemes 3 or 4 are reset
to Coding Scheme 2.

2.

When an RTF is created for the Cell, the Cell parameters init_dl_cs and/or init_ul_cs
are reset to their original values.

Procedure for copying a BTS

To expand the network by copying an existing BTS, execute the following procedure:

Procedure 11-3 Copy an existing BTS

68P02901W17-T

Select the Config Mgt icon from the Front Panel to display the
Navigation Tree.

From the Navigation Tree, click the BTS to use as a template.

Select Config Mgt - Copy SITE from the menu. The Copy SITE form
is displayed, see Figure 11-1.

11-7
Jan 2010

Entering hardware devices

Chapter 11: Network Expansion

Figure 11-1 Copy SITE form

ti-GSM-CopySITEform-00828-ai-sw

Entering hardware devices

To enter the site hardware device information, execute the following procedure:

Procedure 11-4 Enter hardware devices

1

Click Copy SITE from the Copy SITE form (Step1), refer to Figure 11-1.
The status bar at the bottom of the form displays the progress of the
action.
Result: The Site <Create> form is displayed, refer to Figure 11-2.

Click the Upstream Site button to select an existing site within the
network as the upstream site for the new BTS.
Result: The system displays a Navigation Tree.

Navigate to the site to be the upstream site.

Continued

11-8

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Entering hardware devices

Procedure 11-4 Enter hardware devices (Continued)

4

Double-click the upstream site in the Navigation Tree.

Result: The Upstream Site field is updated with the selected site
name. If the selected site is BSC type 0, then the controlling function
BSP (0) is displayed in the BSP/LCF Flag field in the SITE form.
Otherwise, LCF (1) is displayed.

If the new BTS is to be connected to a downstream site, click the

Downstream Site button to select a downstream site for the new BTS.
Result: The system displays a Navigation Tree. If the new BTS is to
be a spoke-connected site from the upstream site, a downstream site
does not need to be selected, so go to step 8.

Navigate to the site to be the downstream site.

NOTE
The Downstream Site button cannot be used in batch copy
or batch reparent operations.
7

Double-click the downstream site in the Navigation Tree.

Result: If the upstream site is selected an error message is displayed.
The Navigation Tree closes and the Downstream Site field is updated
with the selected site name.

If not automatically completed by the system, the controlling function

LCF must be entered in the field: LCF managing this site. Select
Options Auto-Select LCF from the menu bar of the SITE form.
Result: A valid LCF number is auto-selected and displayed in the field:
LCF managing this site. Otherwise, enter the LCF number.

NOTE
If copying a site into a daisy chain configuration, now go
to step 4 in Copying and inserting a site in a daisy chain
on page 11-46.
Continued

68P02901W17-T

11-9
Jan 2010

Entering hardware devices

Chapter 11: Network Expansion

Procedure 11-4 Enter hardware devices (Continued)

9

Select File Save (Equip) from the menu bar.

Result: A Copy SITE Progress Dialog window is displayed. This
contains a list of the Device name, Device Type, Operation Type, Apply
Status, and Errors/Warnings/Comments (if appropriate) fields. The
Copy SITE Progress Dialog information is updated as the process
continues.

NOTE
The Progress Dialog window is not displayed if scheduling a
copy operation. Refer to Scheduling network expansion on
page 11-54 for details on batch scheduling procedures.
If the hardware devices are successfully equipped, the following
message is displayed in the status bar at the bottom of the Copy SITE
window: SUCCESS: All of the applicable Hardware devices were
equipped at the NE (see Progress Dialog)

NOTE
If scheduling a copy operation the following message is
displayed: SUCCESS: The new details have been updated.
Refer to Scheduling network expansion on page 11-54 for
details on batch scheduling procedures.

The <Create> form automatically closes. Step 2: Entering Logical

Link Devices in the Copy SITE form is now sensitized.

NOTE
The Progress Dialog window may be closed, by selecting
File - Close from the menu.

11-10

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Entering hardware devices

Figure 11-2 SITE <Create> form

ti-GSM-SITECreateform-00829-ai-sw

68P02901W17-T

11-11
Jan 2010

Entering logical links

Chapter 11: Network Expansion

Entering logical links

To enter the logical link device information in the Copy SITE form execute the following
procedure:

Procedure 11-5 Enter logical links

1

Click Copy PATH from the Copy SITE form.

Result: The Path Details form is displayed as in Figure 11-3.

Select Options - Auto-Select MMSs from the menu.

Result: The MSI Id and the MMS Id for the BSC and any intermediate
sites are auto-selected within the form. Alternatively, enter the MSI
and MMS ids manually, if required.

NOTE
The Auto-Select MMSs option is not available if scheduling
a copy operation.
The terminating site path information is copied from the original site.
3

If None is displayed in any of the MSI or MMS fields then no suitable

value is available. Enter the missing MSI Id or MMS Id.

Select the Upstream and Downstream TS MMS values for the path.
This is sensitive only if the path contains one Time Slot (TS) switch or
multiple adjacent switches. The values represent the time slots on
the Multiple Serial Link Interface (MMS) directly connected to the
TS switch.

NOTE

The Upstream and Downstream TS MMS options are

not available if the corresponding path contains no
time slot switch or multiple non-adjacent switches. To
enable the Upstream and Downstream TS MMS options
the NX_ENABLE_TIMESLOTS environment variable
must be set, see Operating Information: OMC-R System
Administration (68P02901W19) for further details.

If copying a site into a Daisy Chain there is no time

slot switch support.
Continued

11-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Entering logical links

Procedure 11-5 Enter logical links (Continued)

5

Select File Save(Equip) from the menu.

Result: A Progress Dialog window is displayed. Any errors or warning
are displayed in the window. The Path Details form automatically
closes.

NOTE

If scheduling a copy operation the Progress Dialog

window is not displayed. Refer to Scheduling network
expansion on page 11-54 for details on batch scheduling
procedures.

If scheduling a copy operation the following message is

displayed:
:SUCCESS: The New Logical Link device details have
been updated

Refer to Scheduling network expansion on page 11-54

for details on batch scheduling procedures.

For each path that exists repeat steps 2 to 5.

NOTE
The number of new paths that need to be created must be
the same as the original site. Each path must be equipped
before equipping the Radio Frequency devices.
If the path is equipped successfully, the following message is displayed
in the status bar at the bottom of the Copy SITE form:
SUCCESS: All of the applicable Logical Link devices were
equipped at the NE (see Progress Dialog).

68P02901W17-T

11-13
Jan 2010

Entering logical links

Chapter 11: Network Expansion

Figure 11-3 Path Details form

ti-GSM-PathDetailsform-00830-ai-sw

11-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Entering radio frequency device information

Entering radio frequency device information

To enter the radio frequency device information, execute the following procedure:

Procedure 11-6 Enter radio frequency device information

1

Click Copy CELL from the Copy SITE form (Figure 11-1).
Result: This displays the Cell Details Form as in Figure 11-4.

Enter the Location Area Code (LAC) in the third field of the New GSM
Cell Id.

NOTE
The MCC and MNC subfields in the New GSM Cell ID field in
the Cell Details Form (see Figure 11-4) can also be changed
as required.
3

Enter the Cell Identity (CI) in the fourth field of the New GSM Cell Id.

Enter the new Cell Name (optional).

Enter the new Cell Base Transceiver Station Identification Code (BSIC).

Click YES or NO to Copy ALL Frequency Hopping Systems.

NOTE
By default, the option button is set to Yes to assist in Radio
Frequency reuse.
7

To view the original Frequency Hopping values, select Options Frequency Hopping from the menu. Otherwise Select File Close to
return to the Cell Details Form.

Click External and/or Internal to Copy External/Internal SITE

Neighbors Relations (Refer to Errors when copying neighbor relations
on page 11-18 for details).

To view the original Cell Source and Neighbor view parameters, select
Options - Source and Neighbors from the menu. Otherwise proceed
to the next step.

10

Enter the BVCI Value.

11

Enter the ARFCN numbers. By default, the values are taken from the
original site.

NOTE
If the Frequency Hopping System is copied, then it is not
possible to modify the Absolute Radio Frequency Channel
Number (ARFCN).
Continued

68P02901W17-T

11-15
Jan 2010

Entering radio frequency device information

Chapter 11: Network Expansion

Procedure 11-6 Enter radio frequency device information (Continued)

12

Enter the First Path Id values.

NOTE
By default, these values are taken from the original site. This
value must be a valid path number. This value cannot be null.
13

Select the Upstream and Downstream TS MMS values for the Primary
Path Id.

NOTE

14

This is sensitive only if the path contains one Time Slot

(TS) switch or multiple adjacent switches. The values
represent the time slots on the Multiple Serial Link
Interface (MMS) directly connected to the TS switch.

The Upstream and Downstream TS MMS options are

not available if the corresponding path contains no
time slot switch or multiple non-adjacent switches. To
enable the Upstream and Downstream TS MMS options
the NX_ENABLE_TIMESLOTS environment variable
must be set, see Operating Information: OMC-R System
Administration (68P02901W19) for further details.

Enter the Second Path Id values.

NOTE
By default, these values are taken from the original site.
This value must be a valid path number.
Continued

11-16

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Entering radio frequency device information

Procedure 11-6 Enter radio frequency device information (Continued)

15

Select the Upstream and Downstream TS MMS values for the

Secondary Path Id.

NOTE
This is sensitive only if the path contains one Time Slot (TS)
switch or multiple adjacent switches. The values represent
the time slots on the Multiple Serial Link Interface (MMS)
directly connected to the TS switch.
16

Select File Save (Equip) from the menu.

Result: A Progress Dialog window is displayed. Any error or warnings
are displayed in this window.

NOTE
If scheduling a copy operation the Progress Dialog window
is not displayed. Refer to: Scheduling network expansion on
page 11-54 for details on batch scheduling procedures.
The Cell and Frequency Form automatically closes.
17

For each Cell that exists, repeat the procedure above.

Result: If the operation is successful, the following message is
displayed in the status bar at the bottom of the Copy SITE form:
SUCCESS: All of the applicable Site Radio Frequency devices
were equipped at the NE (see Progress Dialog).

NOTE

68P02901W17-T

If scheduling a copy operation the following message is

displayed:
SUCCESS: The New Radio frequencies device details
have been updated.

Refer to: Scheduling network expansion on page 11-54

for details on batch scheduling procedures.

To close the Progress Dialog window at any time select

File Close from the menu of the Progress Dialog
window.

11-17
Jan 2010

Errors when copying neighbor relations

Chapter 11: Network Expansion

Figure 11-4 Cell Details Form

ti-GSM-CellDetailsForm-00831-ai-sw

Errors when copying neighbor relations

Cells within a site are equipped sequentially, external neighbor relations cannot be equipped
until both the source and target cells have been provisioned by Network Expansion.
Internal neighbor relations can only be copied if both the source and target cells have internal
site neighbor relations copied. If either the source or target cells do not have Internal site
neighbor relations selected then the neighbor relation are not copied. In the Progress Dialog
window, the following error message is displayed:
Error/Warnings/Comments
Neighbor is not created because conflicting answers between the cell
and neighbor cell.

11-18

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Completing or terminating the operation

Completing or terminating the operation

Once the site, path and cell and frequency forms are completed successfully, the site hardware
and software devices are equipped at the NE and MIB. Follow these steps to complete or
terminate the operation:

Procedure 11-7 Complete or terminate the operation

1

Select File Close from the Controlling Form menu.

NOTE
Closing the Controlling Form automatically closes the
Progress Dialog window.
Result: If the operation is complete, a confirmation window is
displayed: Do you want to close the Network Expansion form?
perform step 2 only. If the operation is not complete, a confirmation
window is displayed: Warning: The new site is only partially
equipped. You may manually complete the site using the
Progress Dialog Form and Device Management or you may delete
the new site. Do you wish to close the Network Expansion
form ? perform step 3 only.
2

Click OK to return to the Navigation Tree.

Click Abort to stop the operation and close the Controlling Form or
Cancel to continue.

NOTE
At any stage during the copy operation, it is possible to abort
the operation. Refer to Aborting the copy operation on page
11-19 for details.

Aborting the copy operation

A copy operation can be aborted at any stage. The current task is completed, for example,
provisioning a site, and then the copy is aborted. To abort a copy operation in progress, follow
these steps:

Procedure 11-8
1

Abort the copy operation

Select Options - Abort from the Copy SITE Progress window.

Result: A confirmation window is displayed:
Do you want to Abort the Copy operation ?
Continued

68P02901W17-T

11-19
Jan 2010

Printing a Progress Dialog window

Chapter 11: Network Expansion

Procedure 11-8 Abort the copy operation (Continued)

2

Click OK to abort the copy or Cancel to continue with the copy

operation.

NOTE
If the copy operation is to copy a site into a daisy chain, the
OMC-R prompts to complete, rollback or abort.

Printing a Progress Dialog window

To print a Progress Dialog window, use the following procedure:

Procedure 11-9 Print a Progress Dialog window

1

Select Display Progress Dialog from the Controlling Form menu.

Select File Print from the menu.

Result: The output is sent to the default printer. The progress is
displayed in the status bar at the bottom of the window.

Close the Progress Dialog window by selecting File Close.

Filtering criteria - Progress Dialog window

The filter option filters Devices and Status Values in the Progress Dialog window.

Procedure 11-10 Filter Devices and Status Values

11-20

From the Progress Dialog window (shown in Figure 11-5), select Filter
- Show Filters from the menu.

Click the button to the left of Apply Status to display the status options.

Click the required status settings.

Click the button to the left of Devices to display the device options.

Click the required devices settings.

Select Filter - Apply Filters from the menu.

To close the filter section of the window, select Filter - Hide Filters
from the menu.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Filtering criteria - Progress Dialog window

Figure 11-5 Copy SITE Progress Dialog window - applying filters

ti-GSM-CopySITEProgressDialogwindow-applyingfilters-00832-ai-sw

68P02901W17-T

11-21
Jan 2010

Reparenting a BTS

Chapter 11: Network Expansion

Reparenting a BTS

Introduction to reparenting a BTS

There are two methods available for reparenting a BTS.

By copying a BTS and swapping LACs (this can be intra or inter-BSS (alternative reparent)).

Using the reparent option of inter/intra BSS (offline environment only)

Online method (copying and swapping LACs)

Reparent a BTS using the following steps:

Procedure 11-11 Reparent a BTS using the Online method

1

Select the BTS and copy it.

Result: All Cells in the copied site are given the same dummy or false
LAC.

Swap the dummy LACs with the original site LACs.

Delete the original BTS.

This procedure can also be used to reparent a site in a daisy chain configuration.
In the situation where site downtime is an issue this method allows the new site to be equipped
in full, while the old site configuration remains in service until the last possible moment. Then
a LAC change is carried out which brings the old site Cells out of service and brings the new
site Cells into service.
If error messages appear in the omcaudit file during a reparent BTS operation, see Introduction
to network expansion on page 11-2 for details.

Offline method (within the same BSS or to another BSS)

Reparent a BTS within the same BSS or to another BSS using the following steps:

Procedure 11-12 Reparent a BTS using the Offline method

11-22

Select the BTS to reparent.

Reparent the SITE hardware devices.

Reparent the SITE logical links devices.

Reparent the radio frequency devices which includes deleting the

original BTS.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Prerequisites for swapping site LAC and CI operations

Prerequisites for swapping site LAC and CI operations

Swapping site LAC operations
During a swap site Local Area Code (LAC) operation, neighbor relationships of a cell for the
old site are copied to the cell with the same Cell Identifier (CI) at the new site. Cell mapping
is carried out based on the value of the Cell Identifier. For a swap site LAC operation to be
successful, ensure that the following conditions are met:

The cell Identifier in the GSM Cell Id field for cells of the old site are unique within the
old site. Similarly, the Cell Identifier in the GSM cell Id field for cells of the new site
must be unique within the new site.

Each cell in the new site must have the same Cell Identifier as a corresponding cell
in the old site.

The following are examples of successful and unsuccessful swap site LAC operations.
Example 1: Table 11-1 shows a successful swap site LAC operation, that is CELL1's neighbor
relationships are copied to CELL3 and CELL2's neighbor relationships are copied to CELL4.

Table 11-1 Example of a successful swap site LAC operation

Old site

New site

GSM Cell ID

Cell Name

Neighbors?

GSM Cell ID

Cell Name

Neighbors?

0010111

CELL1

Yes

11111101

CELL3

No

2222212

CELL2

Yes

33333102

CELL4

No

Example 2: Table 11-2 shows an unsuccessful Swap site LAC operation. It failed for the
following reasons:

The Cell Identifiers of the old site (CELL1 and CELL2) are not unique.

CELL4 of the new site does not have a corresponding Cell at the old site with the same
Cell Identifier.

Table 11-2

Example of an unsuccessful swap site LAC operation

Old site

New site

GSM Cell ID

Cell Name

Neighbors?

GSM Cell ID

Cell Name

Neighbors?

4444421

CELL1

Yes

66666201

CELL3

No

5555521

CELL2

Yes

77777202

CELL4

No

Example 3: Table 11-3 shows an unsuccessful Swap site LAC operation. It failed because the
Cell Identifier of the cells of the new site (CELL3 and CELL4) are not unique.

68P02901W17-T

11-23
Jan 2010

Reparenting a BTS by copying and swapping LACs (online only)

Table 11-3

Chapter 11: Network Expansion

Example of an unsuccessful swap site LAC operation

Old site

New site

GSM Cell ID

Cell Name

Neighbors?

GSM Cell ID

Cell Name

Neighbors?

1231231

CELL1

Yes

45645301

CELL3

No

2342332

CELL2

Yes

56778301

CELL4

No

Swapping site CI operations

During a swap site Cell Identifier (CI) operation, neighbor relationships of a cell for the old site
are copied to a Cell which has the same Location Area Code (LAC) at the new site. Cell mapping
is carried out based on the value of the Location Area Code. For a Swap site CI to be successful,
ensure that the following conditions are met:

The LAC in the GSM Cell Id field for cells of the old site are unique within the old site.
Similarly, the LAC in the GSM Cell Id field for cells of the new site must be unique with the
new site.

Each cell in the new site has the same LAC as a corresponding cell in the old site.

Reparenting a BTS by copying and swapping LACs (online only)

This procedure can also be used to reparent a site in a daisy chain configuration.

Prerequisites
See Prerequisites for swapping site LAC and CI operations on page 11-23 for details.

Selecting and Copying a BTS

To reparent a BTS using the Copy and Swap LACs procedure, execute the following steps:

Procedure 11-13 Select and copy a BTS

1

Click the Config Mgt icon from the Front Panel to display the
Navigation Tree.

From the Navigation Tree, click the BTS to reparent.

Select Config Mgt - Copy SITE from the menu.

Result: The Copy SITE form is displayed, see Figure 11-1.

Refer to Copying and pasting a BTS on page 11-6 and only execute
the following procedures:

Entering hardware devices.

Entering logical links.

Continued

11-24

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Reparenting a BTS by copying and swapping LACs (online only)

Procedure 11-13
5

Select and copy a BTS (Continued)

When required to enter the radio frequency device information in the

Copy SITE form, click Copy CELL.
Result: This displays the Cell Details Form, see Figure 11-4.

Enter a false or dummy LAC in the third field of the New GSM Cell ID.

NOTE

For each Cell that exists in the site, enter the same
dummy LAC number.

The MCC and MNC subfields in the New GSM Cell ID

field in the Cell Details Form (see Figure 11-4) can also
be changed as required.

Enter the original (old) CI in the fourth field of the NewGSM Cell Id.

NOTE
In the General section of the form, ensure that NO is
selected to the option Copy all Frequency Hopping
Systems and that the Copy SITE Neighbors Relations
option is deselected.
8

Select File Save (Equip) from the menu.

Result: A Progress Dialog window is displayed. Any error or
warnings are displayed in the window. The Cell and Frequency Form
automatically closes.If the operation is successful, the following
message is displayed in the status bar at the bottom of the Copy SITE
form: SUCCESS: All of the applicable Site Radio Frequency
devices were equipped at the NE (see Progress Dialog).

For each Cell that exists, repeat step 5 to step 8.

10

Close the Progress Dialog window by selecting File Close from the
window.

11

Select File Close from the Copy site form menu once the site, path,
and cell detail forms are completed successfully.
Result: Once complete, a confirmation window is displayed: Do you
want to close the Network Expansion form?

12

68P02901W17-T

Click OK to return to the Navigation Tree.

11-25
Jan 2010

Reparenting a BTS by copying and swapping LACs (online only)

Chapter 11: Network Expansion

Swapping cell LACs

To copy the original cell LACs to the copied BTS, execute the following procedure:

Procedure 11-14

Swap Cell LACs

From the Navigation Tree, click the new BTS.

Select Config Mgt - Swap SITE LACs from the menu.

Result: The Swap site LACs form is displayed containing the new
site details (as shown in Figure 11-6). For each cell in the new site,
the New site pane shows the dummy LACs entered at step 6 of the
Selecting and Copying a BTS on page 11-24.

NOTE
If there are any neighbors relations for any of the Cells
under the site, then a warning appears indicating the swap
site LACs operation is not possible.
3

Click Select Old site.

Result: The Navigation Tree is displayed.

From the Navigation Tree, double click the original (old) BTS.
Result: The Swap site LACs Form displays the original (old) site
information.

If required, click Copy Neighbors?, to delete all neighbor relations for

the original site and recreate the relations in the new BTS.

Click Perform Swap.

Result: This copies the original site LAC numbers to the new site,
and the OMC-R automatically sets the original site LAC numbers to a
dummy value at the old site. When the operation is complete the Status
is set to Changed for both the New and Old site.

11-26

Click Close to return to the Navigation Tree when the operation is

complete.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

within the same BSS or to another BSS (offline only)

Figure 11-6

Reparenting a BTS

Swap site LACs Form

ti-GSM-SwapsiteLACsForm-00833-ai-sw

Deleting the original BTS

When required, delete the original BTS referring to Deleting a BTS on page 11-34 for details.

Reparenting a BTS within the same BSS or to another BSS

(offline only)
Selecting the site to Reparent
To reparent a BTS from one BSS to another, follow Procedure 11-15.

68P02901W17-T

11-27
Jan 2010

Reparenting a BTS within the same BSS or to another BSS (offline only)

Chapter 11: Network Expansion

Procedure 11-15 Reparent a BTS within the same BSS or to another BSS (offline
only)
1

Click the Config Mgt icon on the Front Panel to display the Navigation
Tree.

From the Navigation Tree, click the BTS to reparent.

Select Config Mgt - Reparent SITE from the menu.

Result: The Reparent SITE controlling form is displayed as in
Figure 11-7.

Figure 11-7 Reparent SITE controlling form

ti-GSM-ReparentSITEcontrollingform-00834-ai-sw

11-28

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

within the same BSS or to another BSS (offline only)

Reparenting a BTS

Entering hardware device information

To enter the hardware device information, execute the following procedure:

Procedure 11-16 Enter hardware device information

1

Click Reparent SITE from the Reparent SITE controlling form (see
Figure 11-7).
Result: This displays the SITE Details form.

Click Parent BSS.

Result: A list of BSS instances is displayed.

Select the new parent BSS and click OK.

Result: On selecting a valid Parent BSS, the SITE Number and Name
is auto-selected within the form. For example, the next available site
instance within the parent BSS is selected.If the BSC is of type 0 for
the parent BSS, then the controlling function, BSP (0), is auto-selected
within the form. Otherwise, select the controlling function, LCF Select
Options - Auto-Select LCF from the menu of the SITE Details form. A
valid LCF number is auto-selected.

If Null is displayed, enter a valid LCF number.

Select File Save from the menu. A Progress window is displayed.

This contains a list of the Device Names, Device Type, Operation Type,
Apply Status, and Errors/Warnings/Comments (if appropriate) fields.

NOTE
If scheduling a reparent operation, the Progress window is
not displayed. Refer to Scheduling network expansion on
page 11-54 for details on batch scheduling procedures.
Result: If the hardware devices are successfully equipped, the
following message is displayed in the status bar at the bottom of the
window: SUCCESS: All of the applicable Hardware devices were
equipped at the NE (see Progress Dialog).

NOTE
If scheduling a reparent operation, the following message is
displayed:
SUCCESS: The New SITE details have been updated. Refer
to Scheduling network expansion on page 11-54 for details
on batch scheduling procedures.

The SITE Details form automatically closes. Step 2: Reparent the

SITE Logical Links Devices in the Reparent SITE controlling form is
now available.

68P02901W17-T

11-29
Jan 2010

Reparenting a BTS within the same BSS or to another BSS (offline only)

Chapter 11: Network Expansion

Entering logical links

To enter the logical link device information, execute the following procedure:

Procedure 11-17 Enter logical link device information

1

Click Reparent PATH from the Reparent SITE controlling form.

Result: This displays the Path Details form.

Select Options Auto-Select MMS from the menu.

Result: The MSI Id and the MMS Id for the BSC and any intermediate
sites are auto-selected within the form and the terminating site path
information is copied from the original site.

If None is displayed in any of the MSI or MMS fields, then no suitable

value is available. Enter the missing MSI Id or MMS Id.

Select File Save(Equip) from the menu.

Result: A Progress window is displayed. Any errors or warning are
displayed in the window.

NOTE
If scheduling a reparent operation the Progress window is
not displayed. Refer to Scheduling network expansion on
page 11-54 for details on batch scheduling procedures.

If the path is equipped successful, the following message is displayed

in the status bar at the bottom of the Reparent SITE controlling form
window:
SUCCESS: All of the applicable Logical Link devices were
equipped at the NE (see Progress Dialog).

NOTE
If scheduling a reparent operation, the following message is
displayed:
SUCCESS: The New Logical Link device details have been
updated. Refer to Scheduling network expansion on page
11-54 for details on batch scheduling procedures.
5

The Path Details form automatically closes. For each path, repeat steps
1 to 4. On completion of the last path the next part of the form, Step
3: Reparent Radio Frequency Devices becomes available.

NOTE
The number of new paths that are created must be the same
as the original site. Each path must be equipped before
equipping the RF Devices.

11-30

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

within the same BSS or to another BSS (offline only)

Reparenting a BTS

Reparenting RF devices

NOTE
If scheduling a reparent operation, this section of the Controlling Form is not
displayed. Refer to Scheduling network expansion on page 11-54 for details on batch
scheduling procedures.
To enter Radio Frequency device information, use the following procedure:

Procedure 11-18 Enter Radio Frequency device information

1

Click Reparent Radio Frequency Devices from the Reparent SITE

controlling form.
Result: A confirmation window displays the following message:
Warning: To Equip the Radio Frequency Devices, the old site
will be locked and unequipped.

Click OK to continue.
Result: A Progress window is displayed. This contains a list of the
Device Names, Device Type, Operation Type, Apply Status, and
Errors/Warnings/Comments fields.If the operation is successful, the
following message is displayed in the status bar at the bottom of the
Controlling Form window: SUCCESS: All of the applicable Site
Radio Frequency devices were reparented at the new NE (see
Progress Dialog).

In the case of online operations (OMC), mandatory Fault Management procedures are carried
out and reflected in the Progress window. Refer to Table 11-4 for details on Device Transition
States.
For example, when a site is reparented, the original site is deleted. A DRI is shut down
gracefully within a two-minute interval and an RSL/path/site must be locked before being
deleted. Refer to Defining Network Expansion environment variables for details on how to
modify the time interval.
When complete, the Navigation Tree shows the site at the new location.

Typical transition states when reparenting a site.

Refer to Table 11-4 for examples of OMC Device Transition States when reparenting a site.

Table 11-4 Reparent site - Examples of OMC Device Transition States

Device Transition

Action on Device

Operation Type

Status

Initially

Device to Reparent

Not applied.

Shutdown Action

Device to Shutdown

Shutting Down.

Successful Shutdown
Action

Device to Shutdown

Locked.

Continued

68P02901W17-T

11-31
Jan 2010

BTS rollback to original BSS

Chapter 11: Network Expansion

Table 11-4 Reparent site - Examples of OMC Device Transition States (Continued)
Device Transition

Action on Device

Operation Type

Status

Lock Action

Device to Lock

Not applied.

Successful Lock Action

Device to Lock

Locked.

Reparent Action

Device to Reparent

Not applied or Locked.

Successful Reparent
Action

Device to Reparent

Success.

Failed Reparent Action

Device to Reparent

Failed.

Valid transition states for a DRI: 1, 2, 3, 6, 7 or 8.

Valid transition states for a RSL/path/site: 1, 4, 5, 6, 7 or 8.

NOTE
The transition states within the offline MIB for all devices that are undergoing
reparenting are between:
Not applied to Success or Failed.
The rules for neighbor relations during a reparenting operation are outlined below:
Step

Rules for Neighbor relations

External neighbors to cells that are in the new BSS are changed to internal
neighbors.

Internal neighbors to cells in the old BSS are changed to external neighbors.

Other neighbor relations are unchanged.

BTS rollback to original BSS

At any stage during a reparenting procedure, it is possible to revert the site back to its original
BSS.
To carry out a rollback:

Procedure 11-19 Roll back to the original BSS

1

Select Options - Rollback from the Reparent site controlling form

or Progress window menu.
Result: A confirmation window is displayed as in Figure 11-8.

11-32

Click OK to rollback the site or Cancel to abort the rollback.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

BTS rollback to original BSS

Figure 11-8 Confirmation window after selecting rollback

ti-GSM-Confirmationwindowafterselectingrollback-00835-ai-sw

NOTE
In the reparent SITE operation, the rollback option is disabled during the source
SITE deletion sub-phase in the reparent radio frequency devices phase, if the SITE
has (R)CTU4 associated DRIs.

68P02901W17-T

11-33
Jan 2010

Deleting a BTS

Chapter 11: Network Expansion

Deleting a BTS

Restrictions to deleting a BTS

Only a terminating or spoke BTS in an open daisy chain configuration may be deleted using
this procedure. To delete a Site in a daisy chain configuration, see Network expansion in a
daisy chain configuration on page 11-37.
When devices or functions are deleted as part of a Network Expansion operation (such as
RTFs), the same restrictions apply to the device or function as detailed in for example, section
Deleting an RTF on page 9-193.

CAUTION
The Network Expansion GUI delete site option is strongly recommended as the best
practice for deleting sites.

CAUTION
The site being deleted should not be expanded on the OMC-R GUI navigation form
while the delete site operation is in progress. This is irrespective of the way the site
is being deleted, that is, through Network Expansion, Batch Rlogin, Hierdelete, or
the delete option from the detailed view.

Procedure for deleting a BTS

To delete a BTS and its associated hardware and software objects from the Navigation Tree,
follow these steps:

Procedure 11-20 Delete a BTS

1

From the Navigation Tree, select the SITE to delete.

NOTE
It is also possible to invoke a delete from the Site Detailed
View form in Edit mode.
2

Select Edit Delete from the menu.

Result:
A confirmation window is displayed stating:Do you want to delete
this object and all its containees ?
Continued

11-34

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Procedure for deleting a BTS

Procedure 11-20 Delete a BTS (Continued)

3

Click OK to continue.
Result: A Delete SITE Progress Dialog window is displayed. This
window may not be closed until the site has been deleted.

NOTE
To cancel a delete in progress, select Option - Abort from
the menu of the Progress window. Refer to Aborting a
delete operation for details.
4

Select File Close to return to the Navigation Tree.

Result: A confirmation window is displayed:Do you want to close
the Progress Dialog Form?

Click OK to continue.
Result: The Navigation Tree is automatically updated.

NOTE
In the case of online operations (OMC-R), mandatory Fault
Management procedures are carried out and reflected in
the Progress Dialog window. A DRI is shut down gracefully
within a two-minute interval and an RSL/Path/Site must be
locked before being deleted. Refer to Table 11-5 for details
on the typical transition states.
When complete, the status bar at the bottom of the Delete
Site Progress Dialog window states:Delete SITE operation
completed.

Figure 11-9 Delete SITE Progress Dialog window.

ti-GSM-DeleteSITEProgressDialogwindow-00836-ai-sw

68P02901W17-T

11-35
Jan 2010

Aborting a delete operation

Chapter 11: Network Expansion

Typical transition states when deleting a SITE

Table 11-5 Delete SITE - Examples of OMC-R Device Transition States
Device Transition

Action on Device

Operation Type

Status

Initially

Device to Delete

Not applied

Shutdown Action

Device to Shutdown

Shutting Down...

Successful Shutdown
Action

Device to Shutdown

Locked

Lock Action

Device to Lock

Not applied

Successful Lock
Action

Device to Lock

Locked

Delete Action

Device to Delete

Not applied or Locked

Successful Delete
Action

Device to Delete

Success

Failed Delete Action

Device to Delete

Failed

Valid transition states for a DRI: 1, 2, 3, 6, 7 or 8.

Valid transition states for a RSL/Path/Site: 1, 4, 5, 6, 7 or 8.

NOTE
The transition states within the offline MIB for all devices that are undergoing
deletion are:
Not applied to Success or Failed.

Aborting a delete operation

At any stage during the deletion of a terminating Site, it is possible to abort the operation. If
the Site is within a daisy chain configuration, a delete operation can only be rolled back (see
Deleting a Site in a daisy chain configuration on page 11-38 for details).
To abort the deletion of a terminating Site, follow these steps:

Procedure 11-21 Abort a delete operation

1

Select Options - Abort from the Delete SITE Progress window.

Result: A confirmation window is displayed:Do you want to Abort
the Delete SITE operation?

11-36

Click OK to abort the delete operation or Cancel to continue.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Network expansion in a daisy chain configuration

Network expansion in a daisy chain configuration

Introduction to network expansion in a daisy chain

A user can perform any of the following activities in a static daisy chain configuration using
network expansion functions:

Delete a site between two existing sites, see Deleting a Site in a daisy chain configuration
on page 11-38.

Copy a site into an existing link between two existing sites, see Copying a site and inserting
it in a daisy chain configuration on page 11-45.

Reparent a site that is between two existing sites, see Reparenting a BTS on page 11-22.

NOTE
These daisy chain configuration activities cannot be performed using batch
operations.

Restrictions on network expansion operations

Network expansion operations cannot be used on dynamic sites within DYNET devices.

68P02901W17-T

11-37
Jan 2010

Deleting a Site in a daisy chain configuration

Chapter 11: Network Expansion

Deleting a Site in a daisy chain configuration

Introduction to deleting a Site in a daisy chain

Deleting a Site in a daisy chain is a two stage process:
1.

Select the Site to be deleted.

2.

Reconfigure the associated MMS links to specify the target MMS connectivity of the daisy
chain configuration. This occurs after the system has completed the Network Expansion
operation.

Each of these stages is described in this section.

Prerequisites to deleting a Site in a daisy chain configuration

A Site can only be deleted using the Delete option in the Edit menu in the Navigation Tree, if it
is a static Site within a daisy chain configuration.
A Site that is not within a daisy chain, cannot be deleted.
If deleting a Site in a daisy chain configuration causes an RTF to be deleted or unassigned, the
RTF deletion or unassignment is successful only if the Cell is not using Coding Schemes 3 or 4
for its parameters init_dl_cs and/or init_ul_cs.

CAUTION
The site being deleted should not be expanded on the OMC-R GUI navigation form
while the delete site operation is in progress. This is irrespective of the way the site
is being deleted that is; through Network Expansion, Batch Rlogin, Hierdelete, or
the delete option from the detailed view.

Selecting the Site to be deleted

To delete a Site from a daisy chain configuration, follow Procedure 11-22.

11-38

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Selecting the Site to be deleted

Procedure 11-22 Delete a Site from a daisy chain configuration

1

Select required Site in the Navigation Tree.

Result: The Site instance changes color.

Select Edit Delete from the Navigation Tree menu bar.

Result: The Delete SITE daisy chain operation confirmation form is
displayed, see Figure 11-10.The Delete SITE daisy chain operation
confirmation form displays all SITEs, PATHs, and devices affected
by the deletion, and warns that all these devices and paths will be
temporarily deleted.

Click OK to confirm the deletion.

Result: The Delete SITE daisy chain operation confirmation form
closes. Alternatively, to close the form and cancel the deletion, click
Cancel.

Figure 11-10 Delete SITE daisy chain operation confirmation form

ti-GSM-DeleteSITEdaisychainoperationconfirmationform-00837-ai-sw

68P02901W17-T

11-39
Jan 2010

Reconfiguring MMSs for a deleted Site

Chapter 11: Network Expansion

Reconfiguring MMSs for a deleted Site

Delete SITE <name> MMS Reconfiguration form
After confirming the deletion of the site, the Delete SITE daisy chain operation confirmation
form closes, and the MMS Reconfiguration form opens (see Figure 11-11).

Figure 11-11 MMS Reconfiguration form

ti-GSM-MMSReconfigurationform-00838-ai-sw

The MMS Reconfiguration form displays a read-only list of all the links affected by the Site
deletion in the pane labeled: Affected PATH's MMS Connectivity List. The first link is
selected by default. For each link, the following information is displayed:

11-40

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reconfiguring MMSs for a deleted Site

SiteId - the Upstream Site Id.

Dnstream MMS - the downstream MMS for the upstream Site Id.
SiteId - the Downstream Site Id.
Upstream MMS - the upstream MMS for the downstream Site Id.
PathId - the Path Id
Term. SiteId - the terminating Site Id.
For each link selected in the Affected PATH's MMS connectivity List, details are displayed
in the following fields in the top half of the form:

Upstream SITE
SiteId - the upstream site id.
Dnstream MMS - the downstream MMS (two digits) for the upstream site.

Dnstream SITE:
SiteId - the downstream site id.
Upstream MMS - the upstream MMS id (two digits) for the downstream site.

Procedure to reconfigure MMSs for a deleted site

To reconfigure MMSs, follow these steps:

Procedure 11-23 Reconfigure MMSs for a deleted site

1

Select a link from the Affected PATH's MMS Connectivity List.

Result: Details of the selected links are displayed in the Upstream and
Downstream SITE fields.

Modify the values for the Upstream and Downstream MMS values,
as required.

NOTE
The downstream SiteId and upstream SiteId fields cannot
be changed.
3

Click the Update List button to update the information.

Result: The system checks that the:

Site Ids exist

MMS ids exist at the Site.

MMSs are available for use.

If the update is successful, the link list is updated accordingly.
Continued

68P02901W17-T

11-41
Jan 2010

Reconfiguring MMSs for a deleted Site

Chapter 11: Network Expansion

Procedure 11-23 Reconfigure MMSs for a deleted site (Continued)

4

Select File Save to save the amendments.

Result: The system checks there are no conflicts in the new
configuration, and continues the deletion operation.
Alternatively, to close the Delete SITE <name> MMS Reconfiguration
form and abort the Delete Site operation, select File Close, and then
confirm the abortion.

NOTE
Before performing the site deletion, the system deletes all
the affected devices, Paths and neighbors. If an RTF is
equipped on two paths, and only one path is to be deleted,
the RTF is temporarily unassigned from the path to be
deleted, and remains equipped to the other path. If a BCCH
is deleted, the system deletes all incoming neighbors.
The progress of all operations is displayed in the Delete SITE
<name> Progress Dialog form (see Figure 11-12).
If the delete Site operation is successful, the system attempts
to recreate all the paths according to the information
entered in the MMS Reconfiguration Window. It recreates
all devices and neighbors with their original settings.
If the delete site operation is aborted, the system displays a
Delete Site Abort Confirmation Dialog form stating that the
system will rollback to the initial configuration. In a daisy
chain operation, only a Rollback option is available.
If there is a GUI crash, the system rolls back to the initial
configuration.
A Network Expansion log file is generated containing all
transactions involved in the deletion.

11-42

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Rolling back a delete operation

Figure 11-12 Delete SITE <name> Progress Dialog form

ti-GSM-DeleteSITEnameProgressDialogform-00839-ai-sw

Rolling back a delete operation

An operation to delete a Site in a daisy chain configuration can be interrupted and rolled back
to the initial configuration.

68P02901W17-T

11-43
Jan 2010

Rolling back a delete operation

Chapter 11: Network Expansion

To rollback the deletion of a daisy chain configuration Site, follow these steps:

Procedure 11-24 Roll back the deletion of a daisy configuration

1

Select Options - Rollback from the Delete SITE Progress window.

Result: A confirmation window is displayed:Do you want to
Rollback the Delete SITE operation?

11-44

Click OK to rollback the delete operation or Cancel to abort the

rollback.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Copying a site and inserting it in a daisy chain configuration

Copying a site and inserting it in a daisy chain

configuration

Introduction to copying a site in a daisy chain

Copying a site in a daisy chain is a two stage process:
1.

Select the site to be copied.

2.

Reconfigure the associated MMS links to specify the target MMS connectivity of the daisy
chain configuration. This occurs after the system has completed the network expansion
operation.

Each of these stages is described in this section.

Prerequisites to copying and inserting a site in a daisy chain

A site can only be copied using the Copy option in the Config Mgt menu in the Navigation Tree,
if it is a static site within daisy chain configuration.
A site can only be copied into a daisy chain configuration if the chain has less than ten sites (that
is numInSequence cannot be greater than 10 for a path).
If copying and pasting a site in a daisy chain causes a Cell and then an RTF to be created,
the following occurs:
1.

Cell parameters init_dl_cs and/or init_ul_cs defined as Coding Schemes 3 or 4 are reset
to Coding Scheme 2.

2.

When an RTF is created for the Cell, the Cell parameters init_dl_cs and/or init_ul_cs
are reset to their original values.

If copying a site in a daisy chain configuration causes an RTF to be deleted, the RTF deletion
will only be successful if the Cell is not using Coding Schemes 3 or 4 for its parameters
init_dl_cs and/or init_ul_cs.
If the RTF deletion is successful, the Cell parameters are restored after creating the Path
and RTF.

68P02901W17-T

11-45
Jan 2010

Copying and inserting a site in a daisy chain

Chapter 11: Network Expansion

Copying and inserting a site in a daisy chain

To copy a site and insert it in a daisy chain configuration, follow these steps:

Procedure 11-25 Copy and insert a site in a daisy chain

1

Select required site in the Navigation Tree.

Result: The site instance changes color.

Select Config Mgt - Copy from the Navigation Tree menu bar.
Result: The SITE <Create> form is displayed (refer to Figure 11-2).

Perform steps step 2 to step 8 of Entering hardware devices on page

11-8 in Copying and pasting a BTS on page 11-6.

Select File Save (Equip) to save the details in the SITE form.
Result: If the selected upstream and downstream sites specified
in the SITE form are in a daisy chain configuration and are linked,
the Copy SITE daisy chain operation confirmation form is displayed
after the site has been equipped, see Figure 11-13. The Copy SITE
daisy chain operation confirmation form states that the selected site
is to be inserted in a daisy chain and displays all sites, paths, the
devices affected by the insertion. It also warns that all paths and
path-dependant devices will be temporarily deleted. The Copy SITE
daisy chain operation confirmation form is only displayed when there
are affected paths connecting both the Upstream and Downstream
Sites.

NOTE
If a downstream site has not been specified in the SITE
details form, go to step 4 of the Procedure to reconfigure
MMSs for the new site.
5

Click OK to confirm the copy.

Result: The Copy SITE daisy chain operation confirmation forms
closes and the MMS Reconfiguration form opens (see Figure 11-14).
Alternatively, click Cancel to cancel the copy.

11-46

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Figure 11-13

Copying and inserting a site in a daisy chain

Copy SITE daisy chain operation confirmation form

ti-GSM-CopySITEdaisychainoperationconfirmationform-00840-ai-sw

68P02901W17-T

11-47
Jan 2010

Copying and inserting a site in a daisy chain

Chapter 11: Network Expansion

Figure 11-14 MMS Reconfiguration form

ti-GSM-MMSReconfigurationform-00841-ai-sw

NOTE
A description of the MMS Reconfiguration form is given in Reconfiguring MMSs
for a copied Site.

11-48

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reconfiguring MMSs for a copied site

Reconfiguring MMSs for a copied site

MMSs may be reconfigured for a copied site using the MMS Reconfiguration form as follows:

Description of the Copy SITE <name> MMS Reconfiguration form

The MMS Reconfiguration form displays a read-only list of all the links affected by the site copy
in the pane labeled: Affected PATH's MMS connectivity List. The first link is selected by
default. For each link, the following information is displayed:

SiteId - the Upstream Site Id.

Dnstream MMS - the downstream MMS for the upstream Site Id.
New SiteId
Dnstream MMS - the downstream MMS for the new Site Id.
Upstream MMS - the upstream MMS for the new Site Id.
SiteId - the Downstream Site Id
Upstream MMS - the upstream MMS for the downstream Site Id.
PathId - the affected Path Id.
Term. SiteId - the terminating site Id.
For each link selected in the Affected PATH's MMS connectivity List, details are
displayed in the following fields in the top half of the form:

Upstream SITE
SiteId - the upstream site id.
Dnstream MMS - the downstream MMS (two digits) for the upstream site.

New SITE:
SiteId - the id of the new site.
Dnstream MMS - the downstream MMS (two digits) for the new site.
Upstream MMS - the upstream MMS (two digits) for the new site.

Dnstream SITE:
SiteId - the downstream site id.
Upstream MMS - the upstream MMS id (two digits) for the downstream site.

68P02901W17-T

11-49
Jan 2010

Reconfiguring MMSs for a copied site

Chapter 11: Network Expansion

Procedure to reconfigure MMSs for the new site

To reconfigure MMSs for the new site, follow these steps:

Procedure 11-26 Reconfigure MMSs for the new site

1

Select a link from the Affected PATH's MMS connectivity List.

Details of the selected links are displayed in the Upstream SITE, New
SITE, and Downstream SITE fields at the top of the screen.

Modify the values for the Upstream and Downstream MMS values,
as required.

NOTE
The downstream, new, and upstream SiteId fields cannot
be changed.
3

Click the Update List button to update the information.

Result: The system checks that the:

Site Ids exist.

MMS ids exist at the Site.

MMSs are available for use.

If update is successful, the link list is updated accordingly.
Alternatively, click Cancel to cancel the changes and display the
SITE form (in Edit mode) again.
Continued

11-50

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reconfiguring MMSs for a copied site

Procedure 11-26 Reconfigure MMSs for the new site (Continued)

4

Select File Save to save the amendments.

Result: The system checks there are no conflicts in the new
configuration, and continues the copy operation.
Alternatively, to close the MMS Reconfiguration form and abort the
Copy Site operation, select File Close, and then confirm the abortion.

NOTE
Before performing the site copy, the system deletes all
affected devices and paths. If an RTF is equipped on
two paths, and only one path is to be deleted, the RTF is
temporarily unassigned from the path to be deleted, and
remains equipped to the other path. If a BCCH is deleted,
the system deletes all incoming neighbors.
The progress of all operations is displayed in the copy site
Progress Dialog form. An example is shown in Figure 11-12.
When the site copy operation is completed, the system
recreates all the paths according to the information entered
in the MMS Reconfiguration form. It recreates all devices
and neighbors with their original settings.
If there is a GUI crash during the copy site operation, or the
copy operation is aborted, the system rolls back to the initial
configuration. If the new site has been partially equipped,
then it is not deleted.
If the copy operation is aborted during the un-equip or
re-equip phases, a confirmation box is displayed prompting
whether to rollback, abort or complete. If the new site has
been partially equipped, it is not deleted.
The network expansion log file for the copy operation is
generated with all the transaction information.

68P02901W17-T

11-51
Jan 2010

Troubleshooting Network expansion

Chapter 11: Network Expansion

Troubleshooting Network expansion

Introduction to troubleshooting
If problems arise and it is necessary to contact the local office the following information may
assist in solving the problem:

A copy of the original binary object file (.002) before a network expansion was carried out.

A printout of the Progress Dialog window.

Hierarchical extract of the problem site.

A copy of the saved binary object file (.002) after the problematic network expansion
operation was carried out.

A printout of the log files.

Reporting problems
If problems occur during a Network Expansion, carry out the following procedure to obtain
the required information:

Procedure 11-27 Report problems

1

Open an Xterm window and copy the binary object file (.002), if a copy
of the original does not exist.

Print out a copy of the Progress Dialog window. Refer to Copying and
pasting a BTS on page 11-6, Printing a Progress window for details,
where:

Record status filter is set to All statuses.

Device filter is set to All Devices.

Continued

11-52

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Restore binary object file

Procedure 11-27 Report problems (Continued)

3

If errors occur during a Copy or Delete then abort the operation. If the
problems arise during a Reparent then rollback the operation. Note
any problems during the rollback. Refer to Network expansion logs on
page 11-67, Aborting/Rollback network expansion for details.

NOTE
Wait until the operation is finished before completing the
procedure.
4

Perform a hierarchical extract of the site by using cmutil:

Extract the source site.

Extract the destination site if a copy procedure is being carried

out.
For further information about cmutil, see Chapter 15 cmutil.

Save the binary object file.

Restore binary object file

To restore the original binary object file (.002), execute the following procedure:

Procedure 11-28 Restore the original binary object file

1

Open an Xterm window and replace the corrupted BSS binary object
file with the original BSS binary object file.

NOTE
The binary object file is located in:
/usr/omc/DataGen/olm/<network configuration name>

68P02901W17-T

Upload the NE database if you are in an online environment (see

Uploading an NE database to the OMC-R on page 1-24) or, from
the Navigation Tree, reload the NE database if you are in an offline
environment (refer to System Information: DataGen (68P02900W22).

View the:

CM MIB audit log (online environment only).

Offline MIB audit log (offline environment only) - refer to System

Information: DataGen (68P02900W22).

11-53
Jan 2010

Scheduling network expansion

Chapter 11: Network Expansion

Scheduling network expansion

Overview of scheduling
Instead of carrying out individual interactive procedures the following network expansion
activities can be batched and saved to a spreadsheet. The spreadsheet can then be scheduled to
run at a convenient time.

Copy.

Reparent (only available in the Off-Line MIB (Datagen)).

Delete.

CellX import.

CellX export

The spreadsheet is stored and maybe rescheduled, amended, or used as a starting point to
create a batch.

List of procedures
From the Network Expansion Scheduler window, it is possible to:

Create a network expansion batch.

View a batch log file.

Abort a batch.

Scheduling a network expansion

To schedule a network expansion, use the following procedures:

11-54

Display the Network Scheduler window.

Create a spreadsheet.

Select the date and time to run.

Save the batch file.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Scheduling a network expansion

Displaying the network scheduler

To display the Network Scheduler, perform the following steps:

Procedure 11-29 Display the network scheduler

1

Do one of the following:

Click the Admin icon from the Front Panel to display the Admin
Options window (online environment only).

Click the Admin icon from the DataGen OLM Front Panel to
display the Admin Options window.

Select the Network Expansion Scheduler option.

Result: The selection is highlighted.

Click OK.
Result: The Network Expansion Scheduler window opens. This
contains a list of all the scheduled network expansion items including
Name, Status, Start, and Expire Times, Last validation Time, and
Operator.

Creating a spreadsheet
To create a spreadsheet, perform the following steps:

Procedure 11-30 Create a spreadsheet

1

Select Edit Create from the Network Expansion Scheduler menu.

Result: The Network Expansion Scheduler Detail View window opens,
as shown in Figure 11-15.

NOTE
To use an existing spreadsheet as the starting point for a
new Network Expansion, click Select Batch File from the
Network Expansion Scheduler Detail View form and enter
the path and name of the spreadsheet.
2

Click Copy, Delete, Reparent (only available in the Off-Line MIB

(Datagen)), CellX Import, or CellX Export from the Populate Batch
Files section of the form.
Result: When creating a schedule for copy, delete, reparent (only
available in the Off-Line MIB (Datagen)), cell import/export the
Navigation Tree opens.

Refer to Scheduling a new operation for details of how to proceed

for each procedure.
Continued

68P02901W17-T

11-55
Jan 2010

Scheduling a network expansion

Chapter 11: Network Expansion

Procedure 11-30 Create a spreadsheet (Continued)

4

Once the required information has been entered, each operation is

displayed in the Scheduled Operation List window. To modify or delete
an operation refer to Modifying a scheduled Network Expansion
and carry out steps 5 to 8.

Enter the name of the batch in the Batch Files Information section of
the form. The name must have a .item extension and by default is
located in: /usr/omc/config/global/nxBatch/<namedate>/
Result: The Cell-X-Import and Cell-X-Export operation data is written
to the Cell-X-Import Cell-X-Export spreadsheet files, respectively.
The Cell-X-Import spreadsheet file name is batch_name.import and
the Cell-X-Export spreadsheet file name is batch_name.export. The
name is automatically inserted into the Scheduled Batch Name in the
Identification section of the form.

11-56

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Scheduling a network expansion

Figure 11-15 Network Expansion Scheduler Detailed View window

ti-GSM-NetworkExpansionSchedulerDetailedViewwindow-00842-ai-sw

68P02901W17-T

11-57
Jan 2010

Scheduling a network expansion

Chapter 11: Network Expansion

Selecting the date and time to run

To select the date and time to run the network expansion batch, perform the following steps:

Procedure 11-31 Select the date and time

1

Enter a start time to commence the network expansion batch. Use the
up/down arrow symbols to the right of the Time field to change the
parameter to the required value.

NOTE
Enter all date and time formats in Day/Month/Year
Hour:Minute:Second.
2

Enter a time after which the operation expires. Use the up/down arrow
symbols to the right of the Time field to change the parameter to the
required value.

NOTE
Before a batch starts, a validation is carried out between the
content of the spreadsheet versus the content of the MIB.
The time and date when this occurs is entered automatically
into the Network Expansion Scheduler Detailed View
window. This is read only and is automatically updated each
time a validation is invoked.

Saving the batch file

NOTE
If errors occur during a copy or reparent scheduled operation, a set of default
actions are applied. To modify these settings, refer to Changing default settings
for further information.
To save the batch file, perform the following steps:

Procedure 11-32 Save the batch file

1

Select File Create to create the batch file.

Select File Save to save the batch file.

Select File Close from the menu bar to close the window and return
to the Network Expansion Scheduler window.
Result: The list contains the new scheduled item.

11-58

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Scheduling a new operation

Scheduling a new operation

Copy, Delete, Reparent (only available in the Off-Line MIB (Datagen)), Cell-X Import and Cell-X
Export site operations can be batched and saved to a spreadsheet.

Selecting a site to copy

To select a site to copy, carry out the following procedure from the Network Expansion
Scheduler Detailed View window:

Procedure 11-33 Select a site to copy

1

From the Network Expansion Scheduler Detailed View window, click

Copy to display the Navigation Tree.

Move to the BTS level on the Navigation Tree and double click the
BTS to copy.
Result: This displays the Copy SITE form.

Refer to Copying and pasting a BTS on page 11-6, and complete the
following sections:

Entering Hardware devices and omit Step 6, as it is not possible

to auto select an LCF in batch mode. If Null is entered, the auto
selection takes place at runtime.

Entering Logical Links and omit Step 2, as it is not possible to

auto select MMSs in batch mode.

NOTE
It is necessary to enter the MSI id and the MMS id
for the BSC and intermediate sites when scheduling a
copy operation.

Entering Radio Frequencies and carry out steps 1 to 12.

Select File Close from the Copy SITE form.

Result: A confirmation window is displayed.

Click OK to return to the Network Expansion Scheduler Detailed View

window.
Result: The Scheduled Operations list is updated with the new copy
operation.

68P02901W17-T

11-59
Jan 2010

Scheduling a new operation

Chapter 11: Network Expansion

Selecting a site to delete

To select a site to delete carry out the following procedure from the Network Expansion
Scheduler Detailed View window:

Procedure 11-34 Select a site to delete

1

From the Network Expansion Scheduler Detailed View window, click

Delete to display the Navigation Tree.

Move to the BTS level on the Navigation Tree and double click the BTS
to mark for delete.
Result: The Navigation Tree closes and the Scheduled Operations list
is updated with the new delete operation.

Selecting a site to Reparent

To select a site and reparent carry out the following procedure from the Network Expansion
Scheduler Detailed View window:

Procedure 11-35 Select a site to reparent

1

From the Network Expansion Scheduler Detailed View window, click

Reparent to display the Navigation Tree.

Move to the BTS level on the Navigation Tree and double click the
BTS to reparent.
Result: The Reparent SITE form is displayed.

Refer to Reparenting a BTS on page 11-22 and complete the following

sections:
Entering Hardware devices and omit Step 5, as it is not possible to
auto select an LCF in batch mode. If Null is entered, the auto selection
takes place at runtime.
Entering Logical Links and omit Step 2.

NOTE
It is necessary to enter the MSI id and the MMS id for the
BSC and intermediate sites when scheduling a reparent
operation.
4

Select File Close from the Reparent SITE controlling form.

Result: A confirmation window is displayed.

Click OK to return to the Network Expansion Scheduler Detailed View

window.
Result: The Scheduled Operations list is updated with the new
reparent operation.

11-60

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Scheduling a new operation

Selecting a network object to Cell-X Import

To select a network object to Cell-X Import, carry out the following procedure:

Procedure 11-36 Select a network object to Cell-X Import

1

From the Network Expansion Scheduler Detailed View window, click

the Cell-X Import button to display the Navigation Tree.

If the Region feature is in use, select the appropriate Region.

Select the level at which the import is required on the Navigation Tree
and double click the object to mark it for cell import.
Result: The Cell-X-Import Watcher window appears, see Figure 12-3.

Refer to Cell-X-Import, and perform the procedures in Selecting

configuration files and Selecting import options only.

Select Options Start from the Cell-X Import Watcher window menu
bar to begin the import.
Result: The OMC-R displays the following warning message:
WARNING! You are about to import Cell and RF data to a LIVE
OMC System. This may cause carriers to go out of service,
Sites to reset and Neighbors to be deleted. To continue
select the Continue' button. Select Cancel' to abort the
data import.

If appropriate, click Continue to proceed.

Result: The Cell-X-Import Watcher window closes and the
Cell-X-Import operation appears in the Scheduled Operations List of
the Network Expansion Scheduler Detailed View window. The system
checks that the Configuration file exists.

Return to step 4 in the procedure Scheduling a network expansion.

Selecting a network object to Cell-X Export

To select a network object to Cell-X Export, carry out the following procedure:

Procedure 11-37 Select a network object to Cell-X Export

1

From the Network Expansion Scheduler Detailed View window, click

the Cell-X Export button to display the Navigation Tree.

If the Region feature is in use, select the appropriate Region.

Select the level at which the export is required on the Navigation Tree
and double click the object to mark it for cell export.
Result: The Cell-X-Export Watcher window appears, see
Figure 12-1.
Continued

68P02901W17-T

11-61
Jan 2010

Changing default settings

Chapter 11: Network Expansion

Procedure 11-37 Select a network object to Cell-X Export (Continued)

4

Refer to Cell-X-Export, and perform the procedure in Selecting

configuration files only.

Select Options Start from the Cell-X-Export Watcher window menu

bar to begin the export.
Result: The Cell-X-Export Watcher window closes and the
Cell-X-Export operation appears in the Scheduled Operations List of
the Network Expansion Scheduler Detailed View window.The system
checks that the site RF Planning, Cell RF Planning, Neighbor RF
Planning, RTF/DRI RF Planning, and Configuration file exists.

Return to step 4 in the procedure Scheduling a network expansion.

Changing default settings

Default actions
Table 11-6 shows the default actions that apply if errors are found that cause a Failure, Partial
Success or time expires when copying, deleting or reparenting a site. The alternative defaults
are shown between the < > symbols.

Table 11-6

Default Actions when copying, deleting, reparenting a site

Operation Result

Copy Action

Delete Action

Reparent Action

Partial Success

Abort<Await
Operator
Intervention>
<Abandon>

N/A

Rollback<Await
Operator
Intervention>

Failure

Abort<Await
Operator
Intervention>

N/A

Rollback<Await
Operator
Intervention>

Expire Time

Abort

Abort

Rollback

Where:

11-62

is:
Abort

Tries to complete current task

and stops.

Abandon

Skips problem step and

continues on to the next step.

Rollback

Returns BSS to its original

state.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Changing default settings

Changing default actions

To change the defaults for all copy or reparent actions carry out the following procedure from
the Network Expansion Scheduler Detailed View window:

Procedure 11-38 Change default actions

1

Select Options Default Actions Copy Actions or select Options

Default Actions Reparent Actions.
Copy Actions displays the default actions that apply if errors are
encountered during any copy operation.
Reparent Actions displays the default actions that apply if errors are
encountered during any reparent operation.

NOTE
The Network Expansion Scheduler Detailed View menu
option Options Default Actions does not exist for
Cell-X-Import or Cell-X-Export operations.
Result: This displays the Copy or Reparent SITE Operation Default
Behavior window.
2

Click the button to the right of the Partial Success Action field and
from the list select an alternative default action. Refer to Figure 11-16.

Click the button to the right of the Failure Action field and from the
list change the default action.

Select File Save.

Result: The message Default 'Operation Action' configuration saved
for <'Copy SITE or Reparent SITE'> is displayed in the status bar at
the bottom of the Operation Default Behavior window.

Select File Close and in all subsequent windows to return to the

Network Expansion Scheduler window.

NOTE
To change the default setting for a single operation
within the batch, select the operation from the Scheduled
Operations List. Select the Modify Behavior button, then
repeat steps 2 to 5.

68P02901W17-T

11-63
Jan 2010

Viewing a batch log

Chapter 11: Network Expansion

Figure 11-16 Copy SITE Operation Default Behavior window

ti-GSM-CopySITEOperationDefaultBehaviourwindow-00843-ai-sw

Viewing a batch log

To view a summary of the batch activity of a completed batch, carry out the following procedure:

Procedure 11-39 View a batch log

1

Open the Network Expansion Scheduler window from the Admin

Options window.

Select the schedule item to view the batch log.

Result: The selection is highlighted in black.

Select Display Batch Log from the menu.

Result: The log file is displayed.

11-64

Select File Close to return to the Network Expansion Scheduler

window.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Modifying a scheduled network expansion

Modifying a scheduled network expansion

To modify a scheduled Network Expansion, carry out the following procedure:

Procedure 11-40 Modify a scheduled Network Expansion

1

Open the Network Expansion Scheduler window from the Admin

Options window.

Select the schedule to be modified.

Result: The selection is highlighted in black.

Select Edit Modify from the menu to display the Network Expansion
Schedule Detailed View window.

From the main menu of the Detail View select Edit Edit.

Select the operation to modify from the Scheduled Operation List.

Click Modify Behavior or Modify Operation or Remove Operation.

Modify Behavior - Displays the Copy or Reparent default behavior
actions. Refer to Changing default settingsand carry out steps 2 to 5.

NOTE
If a Cell-X-Import or Cell-X-Export operation is selected in
the Scheduled Operations List, the Modify Behavior button
is grayed-out.

Modify Operation - Displays the Site Controlling Form. It is possible

to modify already entered details or add new operation details. Refer
to Scheduling a new operation for details.
Remove Operation: Deletes the operation from the list. Confirmation
is required before the delete operation is carried out.

NOTE
To revert back to the previously saved spreadsheet select
File Revert from the menu.
7

Select File Save to save the spreadsheet.

Select File Close from the menu bar to close the window and return
to the Network Expansion Scheduler window.
Result: The list contains the updated scheduled item.

68P02901W17-T

11-65
Jan 2010

Deleting all scheduled network expansions

Chapter 11: Network Expansion

Deleting all scheduled network expansions

CAUTION
Obtain permission from the OMC-R System Administrator before deleting the
scheduled network expansions.
To delete all scheduled network expansions, perform the following procedure:

Procedure 11-41 Delete all scheduled network expansions

Select the Admin icon from the Front Panel to open the Admin Options window.

Select the Network Expansion Scheduler option in the Admin Options window.

Select Edit Delete All from the Network Expansion Scheduler window.
Result: A confirmation window is displayed.

Click OK.
Result: All non-active Scheduled network expansions disappear from the
Network Expansion Scheduler window.

Close the Network Expansion Scheduler window by selecting File Close

from the menu bar.

Aborting a scheduled batch operation

A scheduled batch operation can be aborted. If a batch operation containing several network
expansion operations is aborted, the current operation is aborted and the subsequent operations
in the batch are canceled. To abort a single operation within a batch operation see Abandoning
a single Network Expansion operation in Network expansion logs on page 11-67.
To abort a scheduled batch operation follow these steps:

Procedure 11-42 Abort a scheduled batch operation

1

Select the batch schedule in the Network Expansion Scheduler window.

Select Options - Abort Batch from the menu bar.

Result: The following message is displayed in the status bar: Note:
If the current operation is Cell-X-Export, it cannot be
aborted. Subsequent batch operations will be aborted.

Aborting a Cell-X-Export
A scheduled Cell-X-Export cannot be aborted.

11-66

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Network expansion logs

Network expansion logs

Procedures for network expansion logs

The following is a list of procedures that can be performed using Network Expansion logs:

Viewing a Network Expansion log.

Deleting a specific or all completed operation logs.

Abort or rollback an operation in progress.

Retry an operation.

Abandon an operation in a batch.

Viewing a network expansion log

The Network Expansion Log window lists all active and completed network expansion
operations, detailing when the operation was started/completed, by whom and the result of
the operation.

NOTE
Cell-X-export and Cell-X-import log entries are also displayed in the Network
Expansion Log window. The Cell-X-import log file cannot be displayed from the
Network Expansion Log window.
To view the Network Expansion Log window, carry out the following procedure:

Procedure 11-43 View the Network Expansion Log window

1

Click the Admin icon from the Front Panel to display the Admin options
window.

NOTE
It is also possible to view the logs from the Navigation Tree
by selecting Config Mgt - Network Expansion Logs from
the menu bar.
Continued

68P02901W17-T

11-67
Jan 2010

Viewing a network expansion log

Procedure 11-43
2

Chapter 11: Network Expansion

View the Network Expansion Log window (Continued)

Select the Network Expansion Logs option and click OK.

Result: The Network Expansion Logs window is displayed.
Figure 11-17 and Figure 11-18 shows the Network Expansion Logs
window. The Network Expansion Logs window lists of all Operations,
Source Devices, Destination Devices, Actual Start Times, Actual End
Times, Scheduled Items (that is, batch or interactive), Operator, Status
of the overall operation and that of its subsections, Hardware, Logical
Links, and Radio Frequency.

Close the Network Expansion Log window by selecting File Close

from the menu bar.

Figure 11-17 Network Expansion Log window (part 1)

ti-GSM-NetworkExpansionLogwindow_part1_-00844-ai-sw

11-68

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting network expansion logs

Figure 11-18 Network Expansion Log window (part 2)

ti-GSM-NetworkExpansionLogwindow_part2_-00845-ai-sw

Deleting network expansion logs

To delete a Network Expansion log, carry out the following procedure:

Procedure 11-44 Delete Network Expansion logs

1

Refer to Viewing a Network Expansion log and follow steps 1 to 3.

Result: The Network Expansion log window is displayed.

Select the log to be deleted.

Result: The selection is highlighted in inverse text.

Select Edit Delete from the menu bar.

Result: A confirmation window opens.

NOTE
It also possible to select Edit Delete All, to delete all
completed logs.
4

Click OK.
Result: The selected log is removed from the list.

68P02901W17-T

Close the Network Expansion log window by selecting File Close

from the menu bar.

11-69
Jan 2010

Aborting/Rollback network expansion

Chapter 11: Network Expansion

Aborting/Rollback network expansion

As soon as a scheduled Network Expansion commences, the details are displayed in the Network
Expansion log window.
To abort or rollback a Network Expansion in progress, carry out the following procedure:

Procedure 11-45 Abort or roll back a Network Expansion

1

Refer to Viewing a Network Expansion log and follow steps 1 to 3.

Result: The Network Expansion log window is displayed.

From the Network Expansion log window, select the active operation
to abort or rollback.
Result: The selected operation is highlighted in inverse text.

NOTE
An operation in progress is denoted in the list by the setting
Active or intervened in the Status field.
3

Select Options Abort or Rollback from the menu bar.

Result: A confirmation window opens.

NOTE
Abort - completes the current task and then terminates the
operation. This option is applicable to Copy, Delete, and
Cell-X-Import operations.
Rollback - returns the BSS to its original state. This option
is applicable to Reparent operations.
4

Click OK.
Result: The confirmation window disappears and the Network
Expansion list is updated, with the Status field changed to Aborted
or Rollback.

Close the Network Expansion log window by selecting File Close

from the menu bar.

Retrying network expansion

During a Network Expansion if an operation is only partially successful, it is possible to select
and retry the operation.

11-70

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Abandoning a single network expansion operation

To retry an operation, carry out the following procedure:

Procedure 11-46 Retry Network Expansion

1

Refer to Viewing a Network Expansion log and follow steps 1 to 3.

Result: The Network Expansion log window is displayed.

From the Network Expansion log window, select the active or

intervened operation.
Result: The selected operation is highlighted in inverse text.

Select Options Retry from the menu bar.

Result: A confirmation window opens.

Click OK.
Result: The confirmation window disappears and the network
expansion list is updated.

Close the Network Expansion log window by selecting File Close

from the menu bar.

Abandoning a single network expansion operation

During a batched operation, it is possible to select and abandon a problem operation.

NOTE
A scheduled Cell-X-Export cannot be aborted.
To abandon a problem task during a Network Expansion, carry out the following procedure:

Procedure 11-47 Abandon a single Network Expansion operation

1

Refer to Viewing a network expansion log on page 11-67 and follow

steps 1 to 3.
Result: The Network Expansion log window is displayed.

From the Network Expansion log window, select the active or

intervened operation.

Select Options Abandon from the menu bar.

Result: A confirmation window is displayed.

Click OK.
Result: The confirmation window disappears and the Network
Expansion list is updated.

68P02901W17-T

Close the Network Expansion log window by selecting File Close

from the menu bar.

11-71
Jan 2010

Managing network expansion logs

Chapter 11: Network Expansion

Managing network expansion logs

Overview of log management

Network expansion log management, deletes Network Expansion logs after a predefined period.
The period is configurable between one and seven days. The logs can also be deleted manually
refer to Network expansion logs on page 11-67 for details.

Setting the delete period

The operator should set a period to retain the Network Expansion log files. The OLM or OMC-R
automatically deletes the files after this time period elapses.
The log files are deleted at 15-minute intervals, provided no other priority operation, such
as Network Expansion or Audit, is running.
To set the delete period, use the following procedure:

Procedure 11-48 Set the delete period

1

Select the Admin icon from the Front Panel.

Result: This displays the Admin Options window.

Select Network Expansion Log Management and click OK.

Result: This displays the Network Expansion Management window.

Select Edit Edit from the menu bar.

Enter the number of days after which the logs are to be deleted.

Select File Save from the menu bar.

Result: The following message is displayed: Save Complete.

NOTE
To quit without saving, select File Close from the menu
bar. A confirmation window is displayed, click OK to exit the
current interface without saving.
6

11-72

Select File Close from the menu bar to close the window.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Configuring a path using Path Configure menu option

Configuring a path using Path Configure menu option

Introduction to configuring a path using Path Configure menu

option
A user can configure a path between a BSC and a BTS using the Path Configure menu option in
the Navigation Tree. The Path Configure menu option can also be used to configure paths in
daisy chain configurations.
The Path Configure facility allows a user to:

View all paths of the selected site and only the affected paths of the other sites within
the configuration.

View devices associated with a path.

Temporarily unassign a device from a path.

Temporarily unassign a device from a path.

Delete a device.

Create new paths.

Delete a path and delete or unassign all devices associated with the path.

View all path devices associated with a site.

Reassign devices (that have been unassigned) to a secondary path.

Reassign devices (that have been unassigned) to a primary path.

Definition of terms used in this section

In this section, and related sections, the following terms are used:

Devices, referring to RTFs and RSLs.

Disabled devices, referring to devices that are not equipped against a path, not in the NE
and MIB databases, and are temporarily stored by the system.

Path, connectivity between a BSC and a BTS.

Path-dependant devices - devices that are equipped against a path.

Site - remote BTS.

68P02901W17-T

11-73
Jan 2010

Prerequisites for using configure path facility

Chapter 11: Network Expansion

Prerequisites for using configure path facility

The configure path facility is part of network expansion and therefore requires the same
prerequisites, see Introduction to network expansion on page 11-2 for details.

Benefits of using the configure path facility

The following are typical reasons for using the configure path facility:

Unequipping an MSI
Sometimes it is necessary to unequip and re-equip an MSI at a site. For example, if the site
is within a daisy chain and the MSI is involved in the daisy chain connectivity, it can be
complex and time-consuming to unequip and re-equip all the paths and devices that are
dependent on the MSI. Instead, the configure path facility can be used.

Assigning a path to a different MSI

The configure path facility allows all the path devices to be temporarily unassigned before
moving the path to a different MSI. The devices can then be easily reassigned to the path.

Splitting a path into two paths

The configure path facility allows individual devices to be moved from one path to another.

Joining two paths together

The configure path facility allows all devices to be moved from one path to another. The
original path can then be deleted.

Deleting a path
The configure path facility automatically unassigns all the path dependant devices.

Restrictions to configuring a path

When a Path Configure operation is running, it is not possible to start any of the following
processes on the same BSS:

11-74

Audit.

Resync.

CMutil.

Cell parameter propagation.

Network expansion.

Bay levelcCalibration.

CellXchange.

OLM database operations.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Restrictions to configuring a path

Likewise, it is not possible to start a path configure operation when any of the above processes
are running.

68P02901W17-T

11-75
Jan 2010

Initiating a path configure

Chapter 11: Network Expansion

Initiating a path configure

Displaying the Path Configure form

To configure a path, use the Path Configure form.
To display the Path Configure form for a site, follow these steps:

Procedure 11-49 Display the Path Configure form

1

Select the required site in the Navigation Tree (site 0 cannot be

selected).
Result: The site instance changes color.

Select Config Mgt - Path Configure from the Navigation Tree menu
bar.
Result: The system displays the Path Configure form, see Figure 11-19.

11-76

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Description of the Path Configure form

Figure 11-19 Path Configure form

ti-GSM-PathConfigureform-00846-ai-sw

Description of the Path Configure form

Only one Path Configure form can be open at a time for sites within the same configuration and
for sites in different configurations. The Path Configure form is dynamically updated with
any changes occurring in the MIB.

68P02901W17-T

11-77
Jan 2010

Displaying Detailed Views from the Path Configure form

Chapter 11: Network Expansion

Contents
The Path Configure form displays the following information:

SITE(s) - a read-only list of all sites in the configuration. The selected site is highlighted.

PATH(s) - a read-only list of the paths at the selected site. If a site is selected in the SITE(s)
field, the relevant path information is displayed. The first path is highlighted by default.

Device(s) - a read-only list of devices with their primary and secondary path equipage
status. The list of devices displayed is determined by the filter option selected using the
Display Devices on button. The options are:
Selected Path - (default) - displays a list of devices equipped against the selected path.
Selected site - displays a list of all devices equipped at the selected site.
All sites - displays a list of all the affected devices equipped at all sites in the
configuration. When selected, it is not possible to perform any operation on the listed
devices. Also the last site highlighted in the SITE(s) list and the last path highlighted
in the PATH(s) list remain highlighted.

Equipage statuses
The equipage status of a device can be:

A valid Path id, such as 0 or 1.

N/A - for the secondary path for an RSL. This is because an RSL does not have a redundant
path.

Null - if the value Null was originally set for the device before running a Path Configure
operation.

Unassigned (PATH <id.>) - if the device has been unequipped from the Path <id.> using
the current Path Configure operation.

Displaying Detailed Views from the Path Configure form

To display a Detailed View form for any site, path, or device listed in the Path Configure form,
follow these steps:

Procedure 11-50 Display a Detailed View from the Path Configure form
1

Display the Path Configure form, see Displaying the Path Configure
form.

Double-click any site, path, or device shown in the form.

Result: The system displays the appropriate Detailed View form in
Monitor mode. If a device is selected and it is not assigned to any path,
the View, Find, and File Close menu options are available in the
associated Detailed View.

11-78

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Tasks available in the Path Configure form

Tasks available in the Path Configure form

Use the Path Configure form to perform the following tasks:

Creating a path using the Path Configure menu option on page 11-80.

Deleting a path using the Path Configure menu option on page 11-81.

Unassigning a device on a path using Path Configure menu option on page 11-85.

Reassigning a device on the primary path using Path Configure menu option on page 11-87.

Reassigning an RTF on the secondary path on page 11-89.

Deleting a device from a site using Path Configure menu option on page 11-91.

Creating an RTF at a site using the Path Configure menu option on page 11-92.

Creating an RSL at a site using the Path Configure menu option on page 11-93.

68P02901W17-T

11-79
Jan 2010

Creating a path using the Path Configure menu option

Chapter 11: Network Expansion

Creating a path using the Path Configure menu option

Prerequisites to creating a path using the Path Configure menu

option
Before a user can create a path using the Path Configure menu option, network expansion must
have been included in user profile of the user.

Creating a path using Path Configure menu option

To create a path, follow these steps:

Procedure 11-51 Create a path using Path Configure menu option

1

Display the PATH Configure form, see Initiating a path configure on

page 11-76.

Select the site in which the path is to be created from the SITE(s) pane.

Click the Create Path button.

Result: The system displays the Path Detailed View.

11-80

Create the path using the Path Detailed View as described in Creating
a path on page 9-164.

Click Close to close the Path Configure form.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a path using the Path Configure menu option

Deleting a path using the Path Configure menu option

Introduction to deleting a path using the Path Configure menu

option
A path at a site can be deleted. Any devices associated with the path can be either deleted or
unassigned, according to further device requirements.

Prerequisites to deleting a path using the Path Configure menu

option
Before a user can delete a path using the Path Configure menu option:

Network expansion must have been included in user profile of the user.

A path must exist for the selected site.

If deleting a path causes an RTF to be deleted or unassigned, the RTF deletion or unassignment
is successful only if the Cell is not using Coding Schemes 3 or 4 for its parameters init_dl_cs
and/or init_ul_cs.

Deleting a path using Path Configure menu option

To delete a path, use the following procedure:

Select the site and path.

Delete or unassign the devices on that path.

Confirm the deletion

68P02901W17-T

11-81
Jan 2010

Deleting a path using Path Configure menu option

Chapter 11: Network Expansion

Selecting the site and path

To select the site and path, follow these steps:

Procedure 11-52 Select the site and path

1

Display the Path Configure form, see Initiating a path configure on

page 11-76.

Select the required site in the SITE(s) pane.

Select a path in the PATH(s) pane.

Click the Delete Path button.

Result: A Delete Path Confirmation window appears, see Figure 11-20.

NOTE
If the selected path contains devices, these are listed in
the Delete Path Confirmation window. Go to Deleting
or unassigning the devices on the Path to continue.
Otherwise, go to Confirming the deletion.

11-82

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a path using Path Configure menu option

Figure 11-20 Delete Path Confirmation window

ti-GSM-DeletePathConfirmationwindow-00847-ai-sw

Deleting or unassigning the devices on the path

If devices are listed in the Delete Path Confirmation window, click :

Unassign Device(s) button (default) to temporarily unassign all the dependant devices
listed, or

Delete Device(s) button to permanently delete all dependant devices listed, before the
path is deleted.

68P02901W17-T

11-83
Jan 2010

Deleting a path using Path Configure menu option

Chapter 11: Network Expansion

Confirming the deletion

To confirm the deletion (or unassignment) of the selected objects, follow these steps:

Procedure 11-53 Confirm the deletion

1

Click OK to confirm the deletion. Otherwise, click Cancel to cancel

the deletion.
Result: The path is deleted from the current site and the PATH(s)
list is updated accordingly. If Unassign Device(s) is selected, all
path-dependant devices are temporarily unassigned, then the path is
deleted, and finally all lists are updated accordingly. If Delete Device(s)
is selected, all path-dependant devices are permanently unassigned,
then the path is deleted, and finally all lists are updated accordingly. If
any operation fails, a message displayed in the Path Configure form
status bar.

Click Close to close the Path Configure form.

Result: A confirmation dialog box is displayed and warns that all
disabled devices will be permanently deleted.

11-84

Click Confirm to permanently delete all disabled devices. Alternatively,

if disabled devices are not to be deleted, click Cancel.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Unassigning a device on a path using Path Configure menu option

Unassigning a device on a path using Path Configure

menu option

Prerequisites to unassigning a device on a path

Before a user can unassign a device on a path using the Path Configure menu option:

Network expansion must have been included in user profile of the user.

A path must exist for the selected site.

The unassignment of an RTF using the Path Configure menu option is successful only if the Cell
is not using Coding Schemes 3 or 4 for its parameters init_dl_cs and/or init_ul_cs.
If the unassignment is successful, the original values of the cell parameters init_dl_cs and
init_ul_cs are stored by the OMC-R, so that they can be restored when the RTF is reassigned.

Unassigning a device on a path using Path Configure menu

option
To unassign one or more devices on a path, follow these steps:

Procedure 11-54

Unassign a device on a path using Path Configure menu option

Display the Path Configure form, see Initiating a path configure on

page 11-76.

Select the required site in the SITE(s) field.

Select a path in the PATH(s) field.

Select Selected Path using the Display Devices on button, if not already
selected.

Select one or more devices from the Selected Path Device(s) list.

Click the Unassign Device button located below the Selected Path
Device(s) pane.
Continued

68P02901W17-T

11-85
Jan 2010

Unassigning a device on a path using Path Configure menu option

Chapter 11: Network Expansion

Procedure 11-54 Unassign a device on a path using Path Configure menu option
(Continued)
7

Click OK to confirm the unassign. Otherwise, click Cancel to cancel.

Result: The device(s) are unassigned from the current path. If the
selected device is not assigned to any other path, it is permanently
deleted from the site, however, the device still appears in all lists as
unassigned and all device parameters are stored so the device can
be re-equipped at a later date. A device in this state is referred to
as Disabled. An RSL with an associated RTF cannot be unassigned
or deleted. An RTF with an associated RSL can be unassigned and
deleted, and a warning message is displayed. If a BCCH RTF is deleted,
all incoming neighbors can be exported by selecting the Export
Neighbors option in the delete confirmation window (see Exporting
incoming neighbors on deletion of BCCH RTFs on page 9-195). If
an unassign fails, an error message is displayed in the status bar. If
multiple devices are selected, and an unassign fails for one device,
the system continues to unassign the remaining devices. When a
device is successfully unassigned, the device is shown with the status
Unassigned together with the original path name in the Selected site
Device(s) list and the Selected Path Device(s) list for the device.

Click the Close button to close the PATH Configuration form.

Result: A confirmation dialog box is displayed and warns that all
disabled devices will be permanently deleted.

Click Confirm to permanently delete all disabled devices. Alternatively,

if disabled devices are not to be deleted, click Cancel.

NOTE
It is possible to store device information from a Path Configure form (that is, each
attribute with their respective value) to a flat file. If, for example, an unexpected exit
from the GUI occurs when devices are unassigned, the flat file can be used as a
cmutil input file to create the device at the OMC. The user must, however, include the
container information to this file before invoking cmutil for creation. If an unexpected
exit from the GUI occurs while a device is unassigned on any path, the user needs to
manually equip the devices, referring to the flat file for configuration details. When a
device is reassigned successfully, the relevant flat file is deleted. See Using flat files
on page 11-94 for more details.

11-86

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

device on the primary path using Path Configure menu option

Reassigning a

Reassigning a device on the primary path using Path

Configure menu option

Prerequisites to reassigning a device on a primary path

Before a user can reassign a device on a primary path using the Path Configure menu option:

Network expansion must have been included in user profile of the user.

A path must exist for the selected site.

The device must not be equipped against the currently selected path.

The device must have its primary path as unassigned.

When the RTF is reassigned, the original values of parameters init_dl_cs and init_ul_cs are
restored to the cell from which this RTF was unassigned. If at the time of unassignment the
cell parameters were modified, the values of these parameters are restored when the RTF
is reassigned.

Reassigning a device on a primary path using Path Configure

menu option
To reassign one or more devices on the primary path using the Path Configure menu option,
follow these steps:

Procedure 11-55 Reassign a device on the primary path using path Configure
menu option
1

Display the Path Configure form, see Initiating a path configure on

page 11-76.

Select the required site in the SITE(s) pane.

Select a path in the PATH(s) pane.

Select Selected site using the Display Devices on button.

Select one or more devices from the Selected site Device(s) pane.
Continued

68P02901W17-T

11-87
Jan 2010

Reassigning a device on a primary path using Path Configure menu option

Chapter 11: Network Expansion

Procedure 11-55 Reassign a device on the primary path using path Configure menu
option (Continued)
6

Click the Reassign on Primary PATH button.

Result: The selected devices are reassigned at the site against the
selected path. The device status is updated to reflect its new path
details in all lists. If the reassign fails, an error message is displayed
in the status bar.If a BCCH RTF is recreated, all previously disabled
incoming neighbors are recreated with their previous settings.

If a selected device is unassigned and the new path contains one or

more adjacent TS switches, the OMC-R displays: Do you want to
equip the device on a particular timelot?
Select OK or Cancel, as required.
If the path does not contain a TS switch, or No is selected, go to step 10.

If Yes is selected, the OMC-R displays the RTF or RSL Detailed View, as
appropriate.
Using the Upstream and Downstream TS MMS fields in the MMS
Timeslots grouping of the RTF and RSL Detailed Views, select the
timeslots (on the MMS directly connected to the TS switch) on which
the RTF or RSL is to be equipped. See Creating an RTF function on
page 9-185 or Configuring an RSL device on page 9-176 for details. All
other fields in the Detailed Views are grayed-out.

Select File Reassign to save the timeslot details and close the
Detailed View.
Result: The selected device(s) are reassigned at the Site against
the selected path and timeslot, or, if the device(s) was previously
unassigned, it is reassigned. The device status is updated to show the
Path id of the path it has been assigned on. If the reassign or recreate
fails, an error message is displayed in the status bar. If a BCCH RTF is
recreated, all previously disabled incoming neighbors are re-enabled
with their previous settings.

10

Click the Close button to close the Path Configure form.

NOTE
It is possible to store device information from a Path Configure form (that is, each
attribute with their respective value) to a flat file. If, for example, an unexpected exit
from the GUI occurs when devices are unassigned, the flat file can be used as a
cmutil input file to create the device at the OMC. The user must, however, include the
container information to this file before invoking cmutil for creation. If an unexpected
exit from the GUI occurs while a device is unassigned on any path, the user needs to
manually equip the devices, referring to the flat file for configuration details. When a
device is reassigned successfully, the relevant flat file is deleted. See Using flat files
on page 11-94 for more details.

11-88

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Reassigning an RTF on the secondary path

Reassigning an RTF on the secondary path

Prerequisites to reassigning an RTF on a secondary path

Before a user can reassign an RTF on a secondary path:

Network expansion must have been included in user profile of the user.

A path must exist for the selected site.

The RTF must be assigned on the primary path.

The RTF must not be equipped against the currently selected path.

The RTF must have its secondary path unassigned.

Reassigning an RTF on a secondary path using Path Configure

menu option
To reassign one or more RTFs on the secondary path, follow these steps:

Procedure 11-56
option

Reassign an RTF on a secondary path using Path Configure menu

Display the Path Configure form, see Initiating a path configure on

page 11-76.

Select the required site in the SITE(s) pane.

Select a path in the PATH(s) pane.

Select Selected Site using the Display Devices on button.

Select one or more RTF devices with its secondary path unassigned
from the Selected Site Device(s) pane.

Click the Reassign on Secondary PATH button.

Result: The RTF(s) are reassigned at the Site against the selected
path. The device(s) is updated in the three device lists. If the reassign
fails, an error message is displayed in the status bar.
Continued

68P02901W17-T

11-89
Jan 2010

Reassigning an RTF on a secondary path using Path Configure menu option

Chapter 11: Network Expansion

Procedure 11-56 Reassign an RTF on a secondary path using Path Configure menu
option (Continued)
7

If a selected device is unassigned and the new path contains one or

more adjacent TS switches, the OMC-R displays: Do you want to
equip the device on a particular timeslot?
Select OK or Cancel, as required.
If the path does not contain a TS switch, or No is selected, go to step 9.

If Yes is selected, the OMC-R displays the RTF or RSL Detailed View, as
appropriate.
Using the Upstream and Downstream TS MMS fields in the MMS
Timeslots grouping of the RTF Detailed View, select the timeslots (on
the MMS directly connected to the TS switch) on which the RTF is to
be equipped. SeeCreating an RTF function on page 9-185 for details.
All other fields in the Detailed View are grayed-out.

Select File Reassign to save the timeslot details and close the
Detailed View.
Result: The selected RTF(s) are reassigned at the Site against the
selected path and timeslot, or, if the device was previously unassigned,
it is reassigned. The device status is updated to show the Path-Id of the
path it has been assigned to. If the reassign fails, an error message is
displayed in the status bar.

10

Click Close to close the Path Configure form.

NOTE
It is possible to store device information from a Path Configure form (that is, each
attribute with their respective value) to a flat file. If, for example, an unexpected exit
from the GUI occurs when devices are unassigned, the flat file can be used as a
cmutil input file to create the device at the OMC. The user must, however, include the
container information to this file before invoking cmutil for creation. If an unexpected
exit from the GUI occurs while a device is unassigned on any path, the user needs to
manually equip the devices, referring to the flat file for configuration details. When a
device is reassigned successfully, the relevant flat file is deleted. See Using flat files
on page 11-94 for more details.

11-90

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Deleting a device from a site using Path Configure menu option

Deleting a device from a site using Path Configure

menu option

Prerequisites to deleting a device from a site

Before a user can delete a device from a site using the Path Configure menu option:

Network expansion must have been included in user profile of the user.

A path must exist for the selected site.

The deletion of an RTF using the Path Configure menu option is successful only if the cell is not
using Coding Schemes 3 or 4 for its parameters init_dl_cs and/or init_ul_cs.

Deleting a device from a site using Path Configure menu option

To delete a device from a Site, follow these steps:

Procedure 11-57 Delete a device from a site using Path Configure menu option
1

Display the Path Configure form, see Initiating a path configure on

page 11-76.

Select the required site in the SITE(s) pane.

Select Selected Site using the Display Devices on button.

Select one or more devices in the Selected Site Device(s) list.

Click the Delete Device button located below the Selected Site
Device(s) pane.

Click OK to confirm the deletion.

Result: The device(s) is permanently deleted and removed from the
Selected Site Device(s) list. Alternatively, click Cancel to cancel the
deletion.

Click Close to close the Path Configure form.

NOTE
In the instance of deleting a BCCH RTF, the deletion confirmation window displays
a further option to allow the incoming neighbors to be exported. This is further
described in Exporting incoming neighbors on deletion of BCCH RTFs on page 9-195.

68P02901W17-T

11-91
Jan 2010

Creating an RTF at a site using the Path Configure menu option

Chapter 11: Network Expansion

Creating an RTF at a site using the Path Configure

menu option

Prerequisites to creating an RTF at a site

Before creating an RTF at a site using the Path Configure menu option:

Network expansion must have been included in user profile of the user.

A path must exist for the selected site.

At least one RTF group must exist at the selected site.

Creating an RTF at a site using Path Configure menu option

To create an RTF, follow these steps:

Procedure 11-58 Create an RTF at a site using Path Configure menu option
1

Display the Path Configure form, see Initiating a path configure on

page 11-76.

Select the required site in the SITE(s) pane.

Click the Create RTF button.

Result: The system displays the RTF groups form, which shows all the
RTF Groups at the selected Site.

Select the required RTF group from the RTF groups form. This is the
RTF group under which the RTF is created.
Result: The system displays the RTF Detailed View form.

Create the RTF using the RTF Detailed View, as detailed in Creating
an RTF function on page 9-185.
Result: After creation, the RTF appears in all the relevant lists in
the Path Configure form.

11-92

Click Close to close the Path Configure form.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration Creating an RSL at a site using the Path Configure menu option

Creating an RSL at a site using the Path Configure

menu option

Prerequisites to creating an RSL at a site

Before creating an RSL at a site using the Path Configure menu option:

Network expansion must have been included in User Profile of the user.

A path must exist for the selected site.

Creating an RSL at a Site using Path Configure menu option

To create an RSL, follow these steps:

Procedure 11-59 Create an RSL at a site using Path Configure menu option
1

Display the Path Configure form, see Initiating a path configure on

page 11-76.

Select the required Site in the SITE(s) pane.

Click the Create RSL button.

Result: The system displays the RSL Detailed View form.

Create the RSL using RSL Detailed View as detailed in Configuring an

RSL device on page 9-176.
Result: After creation, the RSL appears in all the relevant lists in
the Path Configure form.

68P02901W17-T

Click the Close button to close the Path Configure form.

11-93
Jan 2010

Using flat files

Chapter 11: Network Expansion

Using flat files

It is possible to store device information from a Path Configure form (that is, each attribute with
their respective value) to a flat file.
If, for example, an unexpected exit from the GUI occurs when devices are unassigned, the flat
file can be used as a cmutil input file to create the devices at the OMC. The user must, however,
include the container information to this file before invoking cmutil for creation.
If an unexpected exit from the GUI occurs while a device is unassigned on any path, the user
needs to manually equip the devices, referring to the flat file for configuration details. When a
device is reassigned successfully, the relevant flat file is deleted.
Information is also stored in flat files when creating an RSL or RTF with timeslot(s). If an
unexpected exit from the GUI occurs, this file can be used to access the reserved timeslot(s)
information on the mmi prompt using the chg_ts_usage command.

Unassigning and reassigning RSLs using flat files

To unassign and reassign RSLs using flat files, follow these steps:

Procedure 11-60 Unassign and reassign RSLs using flat files

1

Open the Path Configure form and unassign the RSL, selecting a
particular path.
Result: When an unassign of the RSL is complete, the RSL
details are stored in a flat file at the following location:
/usr/omc/config/global/PathConfigureLogs in the format _RSL_.

Reassign the RSL (previously unassigned through the Path Configure

form).
Result: The flat file with the name _RSL_ is automatically deleted if
the reassign is successful.

NOTE
If an unexpected exit from the Path Configure form occurs, with device details still
present in the /usr/omc/config/global/PathConfigureLogs directory, the user is
informed about the file when the Path Configure file is re-opened.

11-94

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Unassigning and reassigning RTFs using flat files

Unassigning and reassigning RTFs using flat files

To unassign and reassign RTFs using flat files, follow these steps:

Procedure 11-61 Unassign and reassign RTFs using flat files

1

Open the Path Configure form and unassign the RTF from both paths.
Result: When an unassign of the RTF is complete on both paths,
the RTF details are stored in a flat file at the following location:
/usr/omc/config/global/PathConfigureLogs in the format _RTF_.

Reassign the RTF (previously unassigned from both paths through

the Path Configure form).
Result: The flat file with the name _RTF_ is automatically deleted if
the reassign is successful.

NOTE
If an unexpected exit from the Path Configure form occurs, with device details still
present in the /usr/omc/config/global/PathConfigureLogs directory, the user is
informed of the file when the Path Configure file is re-opened.

Unassigning and reassigning BCCH RTFs using flat files

If a BCCH RTF is unassigned, then the neighbor information is stored in a flat file. To unassign
and reassign BCCH RTFs using flat files, follow these steps:

Procedure 11-62
1

Unassign and reassign BCCH RTFs using flat files

Unassign the BCCH RTF from both paths that has incoming neighbors
to it.
Result: When an unassign of the BCCH RTF is complete, the BCCH
RTF neighbor information is stored in a flat file at the following
location: /usr/omc/config/global/PathConfigureLogs.

Reassign the BCCH RTF (previously unassigned from both paths

through the Path Configure form).
Result: The neighbor-related flat file is automatically deleted if the
reassign is successful.

NOTE
If an unexpected exit from the Path Configure form occurs, with device details still
present in the /usr/omc/config/global/PathConfigureLogs directory, the user is
informed of the file when the Path Configure file is re-opened.

68P02901W17-T

11-95
Jan 2010

Checking if RSL/RTF details are written to a flat file

Chapter 11: Network Expansion

Checking if RSL/RTF details are written to a flat file

To check if RSL/RTF details are written to the flat file, follow these steps:

Procedure 11-63 Check RSL/RTF details

1

Open the Path Configure form and unassign a RSL/RTF, selecting a

particular path.

Reassign the RSL/RTF on a different path that has a timeslot switch

present.

Select upstream and downstream MMS's timeslot id and invoke a

reassign noting the timeslots selected.

Unassign the devices.

Result: The RSL/RTF details are stored at the following location:
/usr/omc/config/global/PathConfigureLogs/TimeSlotLogs in the
format <bssname>_<sitename>_MSI_<id>_MMS_<id> and they
are deleted once the reassign is successful.

Checking if a flat file is present

To check for the presence of a flat file, follow these steps:

Procedure 11-64 Check flat file presence

1

Open the Path Configure form for a site and unassign RSL/RTF device.

Reassign RSL/RTF device on a path that has a timeslot switch equipped.

Select a particular timeslot for the device creation/reassign.

Type exit at the GUI prompt immediately after the flat file creation.

Restart the GUI and open the Path Configure form for any site of the
previously opened BSS.
Result: A dialog box is displayed containing information about the file
presence as shown in Figure 11-21.

11-96

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking if a flat file is present

Figure 11-21 Flat file information dialog box

ti-GSM-Flatfileinformationdialogbox-00848-ai-sw

68P02901W17-T
Jan 2010

11-97

Checking if a flat file is present

11-98

Chapter 11: Network Expansion

68P02901W17-T
Jan 2010

Chapter

12
CellXchange

Descriptions about how to import and export cell parameters using the OMC-R GUI CellXchange
facility is provided here. This action may be necessary to replan network frequency. The
following topics are described:

Guidelines for implementing a new frequency plan on page 12-2.

Introduction to CellXchange on page 12-5.

Cell-X-Export on page 12-9.

Cell-X-Import on page 12-17.

Defining CellXchange parameters from the GUI on page 12-28.

CellXchange using the command line on page 12-35.

CellXchange command line utilities on page 12-43.

Troubleshooting Cell-X-Import on page 12-52

CellXchange import and export tables on page 12-53.

NOTE
To schedule a Cell-X-Export or Cell-X-Import, see Scheduling network expansion
on page 11-54.

68P02901W17-T
Jan 2010

12-1

Guidelines for implementing a new frequency plan

Chapter 12: CellXchange

Guidelines for implementing a new frequency plan

Overview to frequency replanning

GSM networks are typically updated in sections. In response to statistical information, it may be
necessary to organize a frequency replan for at least one section every six to eight weeks. This
involves:

Extracting the current Radio Frequency (RF) data from the relevant part of the network
from the OMC-R(s) involved.

Exporting the data to a third-party product.

Deploying the new RF data to the network.

The current method of deploying the new data is to build new BSS databases with the new RF
data and download them to the BSS through CSFP. The new databases can be swapped in at a
quiet time (for example, 03.00 hours). Audit all the affected BSSs to synchronize the MIB.
The following features are available to support frequency replanning:

Off-Line MIB (OLM) - requires DataGen.

CellXchange - available on a live OMC-R and/or as part of OLM feature in DataGen.

Off-Line MIB (OLM)

The Off-Line MIB puts the OMC-R configuration subsystem on to the DataGen platform, enabling
the existing DataGen functionality and OMC-R CM functionality to work side-by-side. DataGen
users are able to link a number of BSS binary files together to form a network configuration.
Batch commands can be run on all the areas in the network, alleviating difficulties arising from
the area-only orientation of the DataGen tool.

DataGen and Offline MIB Hybrid

MIB functionality added to the current MMI-based DataGen provides a hybrid platform, which
enables OMC-R MIB applications to be used alongside the current DataGen applications. The
current DataGen and MIB parts of the hybrid communicate through the BSS binary file. The
current DataGen product can read from, and write to, this file using RevGen or Compile. The
MIB is able to read from, or modify, this file using existing OMC-R processes.

12-2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

CellXchange

Advantages
The implementation of the hybrid DataGen and MIB product provides the following advantages
to the user over the existing DataGen product:

Provides view of the Network.

Supports the propagation of cell parameters.

Supports the propagation of neighbor ARFCN and BSIC.

Enables graphical editing through the Navigation Tree, or through the MCDF spreadsheet.

Continues to support MMI commands. This is important for customers who prefer to
perform certain tasks using MMI scripts.

Provides a product platform for common OMC-R/DataGen CM task applications. For

example, RF Import and Network Expansion.

CellXchange
CellXchange consists of Cell-X-Export and Cell-X-Import facilities.

Cell-X-Export
Cell-X-Export exports Cell, Site, DRI/RTF, and Neighbor data for the entire OMC-R network
configuration into tab-delimited ASCII files. The ASCII files:

Can be imported into an RF Planning tool.

Are available on the live OMC-R Navigation Tree or on the OLM Navigation Tree (Through
Nav Tree - Config Mgt - Cell-X-Export).

The output files are:

/usr/omc/config/global/cellX/RFPlanCell.out

/usr/omc/config/global/cellX/RFPlanSite.out

/usr/omc/config/global/cellX/RFPlanDRIRTF.out

/usr/omc/config/global/cellX/RFPlanNeighbour.out

Cell-X-Export is available on the live OMC-R Navigation Tree or the OLM Navigation Tree
(Through Nav Tree - Config Mgt - Cell-X-Export). It can also be achieved using command line
utilities. Cell-X-Export operates on the basis that the files contain information for all the BSSs in
the network configuration.
CellX exports 2G and UTRAN neighbors as normal to the neighbor file. CellX also exports Blind
Search neighbors to the end of the neighbor file.

68P02901W17-T

12-3
Jan 2010

CellXchange

Chapter 12: CellXchange

Cell-X-Import
Cell-X-Import imports the following RF planning files for the entire network configuration:

/usr/omc/config/global/cellX/RFPlanCell.in

/usr/omc/config/global/cellX/RFPlanSite.in

/usr/omc/config/global/cellX/RFPlanDRIRTF.in

/usr/omc/config/global/cellX/RFPlanNeighbour.in

Cell-X-Import is available on the live OMC-R Navigation Tree or the OLM Navigation Tree
(Through Nav Tree - Config Mgt - Cell-X-Import). It can also be achieved using command line
utilities. Cell-X-Import operates on the basis that the files contain information for all the BSSs in
the network configuration.

12-4

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Introduction to CellXchange

Introduction to CellXchange

Overview of CellXchange
CellXchange enables the following:

Export of parameters from the CM MIB into a tab delimited format, see Cell-X-Export
on page 12-9.

Import of parameters from a tab delimited format into the CM MIB, see Cell-X-Import
on page 12-17.

CellXchange can also be carried out in an off-line environment using the Offline MIB (OLM)
and the DataGen product.

NOTE
Current parameters may be exported/imported from the live OMC-R.

Export and import files

The export/import function generates an ASCII tab delimited file for each of the following,
as requested by the user:

Cell parameters - a list of cells, their BSICS, frequencies and other information.

Site parameters - a list of sites, including their BSS name and site number.

DRI/RTF parameters - a list of DRI/RTFs, including their Cell Id, DRI/RTF Group number
and DRI/RTF number.

Neighbors parameters - for each cell.

By default, only cell and neighbor parameters are exported/imported. If site and/or DRI/RTF
parameters are to be exported, the user must specify the requirements. The parameters to be
exported or imported can be defined by the user (see Defining CellXchange parameters from the
GUI on page 12-28) and are saved in the Configuration file (RF.CNFG). The export/import file
format is published and is in ASCII format. RF planning tools, for example, NetPlan can import
these files and use it to carry out a network frequency replan. These files may be used to modify
other parameters and the modified file may be imported back to the CM MIB.
The output of the frequency replan can be imported into the CM MIB, and then used to update
the relevant network elements, new BSICS and frequencies are propagated to neighbor
relations. CellXchange can be carried out from the Navigation Tree, or from the command
line (see CellXchange using the command line on page 12-35). Read-only parameters can
be exported, but they cannot be imported.

68P02901W17-T

12-5
Jan 2010

Configuration file (RF.CNFG)

Chapter 12: CellXchange

Configuration file (RF.CNFG)

The export/import Configuration file holds user-selected parameters for export/import. The file
is named RF.CNFG and is located in /usr/omc/config/global/cellX. The configuration file shows
the status of each parameter using:

RW - read/write.

RO - read only .

RC - read/create.

The configuration file also shows whether the parameter is BSS-only or MIB-only, by prefixing
the RO, RW or RC information with:

Bss

Mib

The format of the configuration file is, for example:

ti-GSM-CellXExportWatcherwindow-00849-ai-sw

12-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Import/Export progress information

Import/Export progress information

While the import/export is in progress, the process displays the following information:

Number of sites and cells to be imported/exported.

Number of sites and cells that have been imported/exported so far. For example, 2 of
20 sites imported, 4 of 50 cells imported.

Name of the site or cell currently being imported/exported.

If there is a problem in one of the import/export files, the name of the file and the number
of the line where the error occurred are displayed.

CellXchange log files

General import/export information
Entries for a cell import or export operation are recorded in the following log file, along with
entries relating to other OMC-R operations:
/usr/omc/logs/omcaudit<yyyymmdd>
For example, the following import entries could appear in this log file:
rfi : process starting
rfi : process initializing
rfi : process cleaning up

Import changes
If a change is made to cell or neighbor cell as a result of a cell import, the following log file
is also created:
/usr/omc/logs/usrauditlogs/rfi<yyyymmdd>
This log file contains details of the cells and neighbors which were updated, as well as the
parameter which was changed.
The file rfi<yyyymmdd> can be viewed with a text editor, or by selecting Display - RF Log
from the menu bar.
The RF log file is accessible from a GUI Server or a GUI Client.
Log entries for both Cell-X-export and Cell-X-import operations are also displayed in the
Network Expansion Log window. From this window, it is possible to view the log file for a
Cell-X-import only. See Network expansion logs on page 11-67 for further details.

68P02901W17-T

12-7
Jan 2010

Setting up automatic deletion of backup files

Chapter 12: CellXchange

Setting up automatic deletion of backup files

CellXchange backup files are stored in:
/usr/omc/config/global/cellX
These can be automatically deleted by enabling the environment variable DEL_CELLX_FILES.
By default, DEL_CELLX_FILES is switched OFF.
To switch on the auto-deletion of backup files, see the full description of DEL_CELLX_FILES
and other environment variables in Operating Information: OMC-R System Administration
(68P02901W19).

12-8

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell-X-Export

Cell-X-Export

Cell-X-Export procedure list

The following is a list of procedures that are carried out when doing a Cell-X-Export:

Selecting the entire Network or a specific BSS.

Selecting Configuration files.

NOTE
This is only necessary if files other than the default are required.

Selecting export options.

Starting and monitoring a Cell-X-Export.

Selecting the network or a specific BSS

To export site, cell, DRI/RTF, and neighbor information for the entire network or a specific
BSS, use the following procedure:

Procedure 12-1 Export site, cell, DRI/RTF, and neighbor information

1

Click the Config Mgt icon from the Front Panel to display the
Navigation Tree.

Select the network or a specific BSS.

Select Config Mgt Cell-X-Export from the menu bar.

Result: The Cell X Export Watcher window is displayed. Refer to
Figure 12-1.

NOTE
The network should include all BSSs containing cells
which are affected by the frequency replan, including cells
impacted by neighbor propagation.

68P02901W17-T

12-9
Jan 2010

Selecting configuration files

Chapter 12: CellXchange

Figure 12-1 Cell X Export Watcher window

ti-GSM-CellXExportWatcherwindow-00849-ai-sw

Selecting configuration files

To select a site, cell, DRI/RTF, Neighbor, or configuration file other than the default, carry out
the following procedures from the Cell X Export Watcher window:

12-10

Select a Site RF Planning file.

Select a Cell RF Planning file.

Select a Neighbor RF Planning file.

Select a DRI/RTF RF Planning file.

Select an RF Configuration file.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Selecting configuration files

NOTE
When using CellXchange on the OMC-R, maintain all input, output, and configuration
files in the /usr/omc/config/global/cellX directory, as this is accessible to all
workstations on the OMC-R network. However, it is possible to export to other
directories if required.

Selecting a Site RF Planning file

To select a Site RF Planning file, follow these steps:

Procedure 12-2 Select a Site RF Planning file

1

Click Site RF Planning file to change the name of the file and export
location.
Result: The File Selection window is displayed. Refer to: Figure 12-2.

NOTE
The Site export RF Planning file by default
is named RFPlanSite.out and is exported to:
/usr/omc/config/global/cellX/RFPlanSite.out.
2

Select the directory in the Directories list box and click Filter.

Enter the new name in the Selection text box. Click OK to return to
the Cell X Export Watcher window.
Result: The window displays the new name and path.

68P02901W17-T

12-11
Jan 2010

Selecting configuration files

Chapter 12: CellXchange

Figure 12-2 File Selection window

ti-GSM-FileSelectionwindow-00850-ai-sw

Selecting a Cell RF Planning file

To select a Cell RF Planning file, follow these steps:

Procedure 12-3 Select a Cell RF Planning file

1

Click cell RF Planning file to change the name of the file and export
location.
Result: The File Selection window is displayed. Refer to: Figure 12-2.

NOTE
The Cell export RF Planning file by default is named
RFPlanCell.out and is exported to:
/usr/omc/config/global/cellX/RFPlanCell.out
2

Select the directory in the Directories list box and click Filter.

Enter the new name in the Selection text box. Click OK to return to
the Cell X Export Watcher window.
Result: The window displays the new name and path.

12-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Selecting configuration files

Selecting a Neighbor RF Planning file

To select a Neighbor RF Planning file, follow these steps:

Procedure 12-4 Select a Neighbor RF Planning file

1

Click Neighbor RF Planning file to change the name of the file and
export location.
Result: The file selection window is displayed.

NOTE
By default, the Neighbor RF Planning file is named
RFPlanNeighbor.out and is exported to:
/usr/omc/config/global/cellX/RFPlanNeighbour.out
2

Select the directory in the Directories list box and click Filter.

Enter the new name in the Selection text box. Click OK to return to
the Cell X Export Watcher window.
Result: The window displays the new name and path.

Selecting a DRI/RTF RF Planning file

To select a DRI/RTF RF Planning file, follow these steps:

Procedure 12-5 Select a DRI/RTF Planning file

1

Click DRI/RTF RF Planning file to change the name of the file and
export location.
Result: The file selection window is displayed.

NOTE
By default, the DRI/RTF RF Planning file is named
RFPlanDRIRTF.out and is exported to:
/usr/omc/config/global/cellX/RFPlanDRIRTF.out.
2

Select the directory in the Directories list box and click Filter.

Enter the new name in the Selection text box. Click OK to return to
the Cell X Export Watcher window.
Result: The window displays the new name and path.

68P02901W17-T

12-13
Jan 2010

Selecting export options

Chapter 12: CellXchange

Selecting an RF Configuration file

To select an RF Configuration file, follow these steps:

Procedure 12-6 Select an RF Configuration file

1

Click Configuration file to select an alternative configuration file.

Result: The File Selection window is displayed. Refer to: Defining
CellXchange parameters from the GUI for details on how to change
the configuration file.

NOTE
By default, the RF configuration file is named RF.CNFG and
is located in: /usr/omc/config/global/cellX/RF.CNFG.
2

Select the directory in the Directories list box and click Filter.

Select the configuration file from the Files list box.

Click OK to return to the Cell X Export Watcher window.

Result: The monitor window displays the new path and configuration
file.

Selecting export options

By default, only cell and neighbor parameters are exported. To change the default and select
further export options, carry out the following procedure referring to Figure 12-1 Cell X
Export Watcher window:

Procedure 12-7 Select export options

1

Click YES against Process Site Parameters to export site parameters.

NOTE
NO is the default.
2

Click NO if cell parameter export is not required.

NOTE
YES is the default for Process Cell Parameters, which
exports cell parameters, but not neighbor parameters. The
cell and neighbor options are mutually exclusive.
Continued

12-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Selecting export options

Procedure 12-7 Select export options (Continued)

3

Click NO if neighbor parameter export is not required.

NOTE
YES is the default for Process Neighbor Parameters, which
exports neighbor parameters, but not cell parameters. The
cell and neighbor options are mutually exclusive. If neighbor
parameters or DRI/RTF parameters are exported then cell
parameters are also automatically exported.
4

Click YES against Process DRI/RTF Parameters to export DRI/RTF

parameters.

NOTE
NO is the default. If neighbor parameters or DRI/RTF
parameters are exported then cell parameters are also
automatically exported.

68P02901W17-T

12-15
Jan 2010

Starting and monitoring a Cell-X-Export

Chapter 12: CellXchange

Starting and monitoring a Cell-X-Export

To start and monitor the export follow Procedure 12-8 from the Cell X Export Watcher window:

Procedure 12-8 Start and monitor a Cell-X Export

1

Select Options Start from the menu bar to begin the export.
Result: The watcher window monitors the progress of the
export. When the export is complete, the export watcher
window displays the appropriate information. For example,
the following messages are displayed when cell and neighbor
parameters only are exported: Initializing RF Export.....
Performing a Network wide RF Export Output Files are
: </usr/omc/config/global/cellX/RFPlanCell.out> and
</usr/omc/config/global/cellX/RFPanNeighbour.out> Process
Complete. where <directory & filename> is the default or User
defined.

NOTE
Each time an export is carried out, the current
default output files are saved with a date stamp, in
the format RFPlanCell.out<yyyymmdd>.BACKUP and
RFPlanNeighbour.out<yyyymmdd>.BACKUP.
User-defined output files are saved in the format:
<user_defined>< yyyymmdd>.BACKUP.

12-16

Select Options Clear from the menu bar to delete the current
messages.

Select File Close to return to the Navigation Tree.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell-X-Import

Cell-X-Import

Prerequisites to Cell-X-Import
Observe the following criteria before attempting to import RF Planning information into the
CM MIB or the OLM.

The format of the files should be ASCII tab delimited and must contain the columns
as defined in the RF.CNFG file. Refer to CellXchange import and export tables on page
12-53 for details.

NOTE
If the network contains neighbor cells which are not specified in the import
file, the neighbors are deleted in the MIB. To prevent this from happening, an
option not to allow neighbor deletes may be selected from the Radio Frequency
import monitor window.

All BSSs, cells, and RTFs that are in the frequency replan file, must exist in the MIB for the
import to be successful. However, if inconsistencies are found, the user has the option
to continue with consistent cells.

List of procedures
The following is a list of procedures that are carried out when performing a Cell-X-Import:

Selecting a Network or BSS.

Selecting Configuration files.

NOTE
This is only necessary if files other than the default are required.

Selecting Import options.

Starting and monitoring a Cell-X-Import.

68P02901W17-T

12-17
Jan 2010

Selecting a network or a specific BSS

Chapter 12: CellXchange

Selecting a network or a specific BSS

To import site, cell, DRI/RTF, and neighbor information for a network or a specific BSS, use the
following procedure:

Procedure 12-9 Import site, cell, DRI/RTF and neighbor information

1

Click the Config Mgt icon from the Front Panel to display the
Navigation Tree.

Select the network or an individual BSS.

Select Config Mgt - Cell-X-Import from the menu bar.

Result: The Cell X Import Watcher window is displayed as in
Figure 12-3.

Figure 12-3

Cell X Import Watcher window

ti-GSM-CellXImportWatcherwindow-00851-ai-sw

12-18

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Selecting configuration files

Selecting configuration files

To select a site, cell, DRI/RTF, Neighbor, or configuration file other than the default, carry out
the following procedures from the Cell X Import Watcher window:

Select a Site RF Planning file.

Select a Cell RF Planning file.

Select a Neighbor RF Planning file.

Select a DRI/RTF RF Planning file.

Select an RF Configuration file.

NOTE
If using CellXchange on the OMC-R, maintain all input, output, and configuration files
in the /usr/omc/config/global/cellX directory, as this is accessible to all workstations on
the OMC-R network. However, it is possible to export to other directories if required.

Selecting a Site RF Planning file

To select a Site RF Planning file, follow these steps:

Procedure 12-10 Select a Site RF Planning file

1

Click Site RF Planning file to change the name of the file and its
location.
Result: The File Selection window is displayed. Refer to Figure 12-4.

NOTE
The Site import RF planning file by default
is named RFPlanSite.in and is located in:
/usr/omc/config/global/cellX/RFPlanSite.in.
2

Select the directory in the Directories list box and click Filter.

Select the import file from the Files list box.

Click OK to return to the Cell X Import Watcher window.

Result: The monitor window displays the new name and path.

68P02901W17-T

12-19
Jan 2010

Selecting configuration files

Chapter 12: CellXchange

Figure 12-4 File Selection window

ti-GSM-FileSelectionwindow-00852-ai-sw

12-20

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Selecting configuration files

Selecting a Cell RF Planning file

To select a Cell RF Planning file, follow these steps:

Procedure 12-11 Select a Cell RF Planning file

1

Click Cell RF Planning file to change the name of the file and its
location.
Result: The File Selection window is displayed. Refer to Figure 12-4.

NOTE
The Cell import RF planning file by default
is named RFPlanCell.in and is located in:
/usr/omc/config/global/cellX/RFPlanCell.in.
2

Select the directory in the Directories list box and click Filter.

Select the import file from the Files list box.

Click OK to return to the Cell X Import Watcher monitor window.

Result: The monitor window displays the new name and path.

Selecting a Neighbor RF Planning file

To select a Neighbor RF Planning file, follow these steps:

Procedure 12-12
1

Select a Neighbor RF Planning file

Click Neighbor RF Planning file to change the name of the file and
location.
Result: The File Selection window is displayed. Refer to Figure 12-4.

NOTE
By default, the Neighbor Planning file is named,
RFPlanNeighbor.in and is located in:
/usr/omc/config/global/cellX/RFPlanNeighbour.in.
2

Select the directory in the Directories list box and click Filter.

Select the import file from the Files list box.

Click OK to return to the Cell X Import Watcher monitor window.

Result: The monitor window displays the new name and path.

68P02901W17-T

12-21
Jan 2010

Selecting import options

Chapter 12: CellXchange

Selecting a DRI/RTF RF Planning file

To select a DRI/RTF RF Planning file, follow these steps:

Procedure 12-13 Select a DRI/RTF Planning file

1

Click DRI/RTF RF Planning file to change the name of the file and
location.
Result: The File Selection window is displayed. Refer to Figure 12-4.

NOTE
By default, the Neighbor Planning file is
named RFPlanDRIRTF.in and is located in:
/usr/omc/config/global/cellX/RFPlanDRIRTF.in.
2

Select the directory in the Directories list box and click Filter.

Select the import file from the Files list box.

Click OK to return to the Cell X Import Watcher monitor window.

Result: The monitor window displays the new name and path.

Selecting an RF Configuration file

To select an RF Configuration file, follow these steps:

Procedure 12-14 Select an RF Configuration file

1

Click Configuration file to select an alternative configuration file.

Refer to: Defining CellXchange parameters from the GUI for
details on how to change the configuration file.

NOTE
By default, the RF configuration file is named RF.CNFG and
is located in: /usr/omc/config/global/cellX/RF.CNFG.
2

Select the directory in the Directories list box and click Filter.

Select the configuration file from the Files list box.

Click OK to return to the Cell X Import Watcher window.

Result: The monitor window displays the new path and configuration
file.

Selecting import options

By default, only cell and neighbor parameters are imported. To change the default and select
further import options, carry out the following procedure referring to Figure 12-3 Cell X
Import Watcher window:

12-22

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Selecting import options

Procedure 12-15 Select import options

1

Click YES for Correct RTFs? to allow RTFs to be created or deleted (as
necessary) in the MIB to match the number of RTFs in the import file.

NOTE
NO is the default.
2

Click YES for Correct DRIs? to allow DRIs to be created or deleted (as
necessary) in the MIB to match the number of DRIs in the import file.

NOTE
NO is the default.
3

Motorola recommends the following settings for BSS Deployment:

For the OMC-R, select Parallel mode. This means that the update
commands are sent to each BSS, which results in less loading on
the OMC-R because each BSS carries out its own updates.

For the OLM, select Sequential mode. Each BSS binary on the
OLM has its own process running, so running in Parallel mode on
the OLM would mean sending out a large number of commands
at the same time. All of these commands are run on the same
machine, so the loading for all the BSS changes is therefore on
the OML machine.

Click NO for Allow Neighbor Deletes? to prevent neighbors from being

deleted from the MIB to match the number of neighbors in the import
file.

NOTE
YES is the default, that is, neighbors are deleted in the MIB
to match the number of neighbors in the import file.
5

Click YES for Process Site Parameters to import site parameters.

NOTE
NO is the default.
6

Click NO if cell parameter import is not required.

NOTE
YES is the default for Process Cell Parameters, which
imports cell parameters, but not neighbor parameters. The
cell and neighbor options are mutually exclusive.
Continued

68P02901W17-T

12-23
Jan 2010

Selecting import options

Chapter 12: CellXchange

Procedure 12-15
7

Select import options (Continued)

Click NO if neighbor parameter import is not required.

NOTE
YES is the default for Process Neighbor Parameters, which
imports neighbor parameters, but not cell parameters.
The cell and neighbor options are mutually exclusive. If
neighbor parameters or DRI/RTF parameters are imported,
the information contained in the cell file is used to perform
the import, even if the cell parameters are not imported.
8

Click YES for Process DRI/RTF Parameters to import DRI/RTF

parameters.

NOTE
NO is the default. If neighbor parameters or DRI/RTF
parameters are imported, the information contained in
the cell file is used to perform the import, even if the cell
parameters are not imported.

12-24

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Starting and monitoring a Cell-X-Import

Starting and monitoring a Cell-X-Import

To start and monitor the import for the network or BSS, carry out the following procedure:

Procedure 12-16 Start and monitor a Cell-X Import

1

Select Options - Start from the Cell X Import Watcher monitor window
menu bar to begin the import.
Result: If selected on a live OMC-R, the OMC-R displays the following
warning message: WARNING! You are about to import Cell and RF
data to a LIVE OMC System. This may cause carriers to go
out of service, Sites to reset and Neighbors to be deleted.
To continue select the Continue' button. Select Cancel'
to abort the data import.

If appropriate, click Continue to proceed.

Result: The watcher window monitors the progress of the import.

NOTE
It is possible to abort the operation at any stage during the
import. Refer to Aborting a Cell-X-Import on page 12-26 for
details.

During the import, the import watcher window displays the following
messages if no inconsistencies are present:
RF Import Initializing...
Performing Network wide RF Import or Performing an RF Import
for BSS <BSS name>
Process Complete.
3

If inconsistencies are present between the input file and the database, a
warning window displays giving the option to Abort or Continue. Select
Continue to apply consistent data only or Abort to stop the operation.

Select Options - Clear from the menu bar to delete the current
messages.

To view the inconsistencies, select Display - Inconsistencies from the

menu bar.
Result: The RFImportInconsistencies report is displayed, which is
stored in the following directory: /usr/omc/config/global/cellX

NOTE
Each time an inconsistency report is generated, the
current file is saved with a date stamp, in the format
RFImportInconsistencies<yyyymmdd>.BACKUP
6

Select File Close to return to the Navigation Tree.

NOTE
When the import is complete, the system performs an
rfNCheck to detect errors during neighbor propagation.

68P02901W17-T

12-25
Jan 2010

Aborting a Cell-X-Import

Chapter 12: CellXchange

Cell-X-Import changes to double-density or single-density DRIs

Cell-X-Import automatically locks and unlocks a DRI when changing it from double density to
single density.
If the DRI/RTF Planning input file contains the dri_density attribute with a change in value from
single density (1) to double density (2), then the Cell-X-Import operation locks the DRI, makes
the change to dri_density, and then unlocks the DRI (the associated DRI is auto created). The
Associated DRI is also be unlocked. The user can specify the value of assoc_dri_id (the rdn of
the associated DRI) when changing the DRI attribute dri_density from 1 to 2 or 3 (assuming
that the user has configured the parameter).
If the DRI/RTF Planning input file contains the dri_density attribute with a change in value from
double density (2) to single density (1), then Cell-X-Import automatically locks the DRI and
the associated DRI, makes the change, and then unlocks the DRI (the associated DRI is auto
deleted). The DRI locking and unlocking is recorded in the RF log file.
The user cannot modify the attribute assoc_dri_id directly (in one step). To modify the attribute
assoc_dri_id, carry out the following procedure:

Procedure 12-17 Modifying the attribute assoc_dri_id

1

Change the dri_density to 1 using an import (CellX automatically locks both

DRIs and unlocks the original DRI).

Perform an export.

Change dri_density to 2 or 3 and specify the new assoc_dri_id value in

a second import.

Cell-X-Import changes for (R)CTU4 DRI

Cell-X-Import automatically locks and unlocks a DRI while changing the values of the
tx_0_dri_density or tx_1_dri_density parameter.
If the DRI/RTF planning input file contains the tx_0_dri_density or tx_1_dri_density attribute
with a changed value; the Cell-X-Import operation locks the DRI, makes the changes to the
tx_0_dri_density or tx_1_dri_density, and unlocks the DRI. The associated DRIs are automatically
created and unlocked.
The user can specify the value of the associated DRIs (the rdn of the associated DRIs) while
changing the value of the DRI attribute tx_0_dri_density or tx_1_dri_density.

Aborting a Cell-X-Import
At any stage during a Cell-X-Import it is possible to abort the operation. To abort a Cell-X-Import,
follow Procedure 12-18.

12-26

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Displaying the RF log file

Procedure 12-18 Abort a Cell-X Import

1

Select Options - Abort from the Cell X Import Watcher menu. Refer
to Figure 12-3.
Result: A confirmation window is displayed: ABORT: Are you sure
you want to abort the current import? Once aborted the
Import will complete the current operation and then exit

Click OK to abort the import or Cancel to continue with the import.

Result: The message Process complete is displayed in the status bar
at the bottom of the Cell X Import Watcher window when the import
is aborted.

NOTE
Aborting an operation may take some time as it completes
the current operation on the cell before aborting.

Displaying the RF log file

The OMC-R writes information to the RF log file during the Cell-X-Import process when a
cell or neighbor is changed by the import. To display the RF log file at any time during the
Cell-X-Import process, select Display - RF Log from the menu bar.
The RF log file is accessible from a GUI Server or a GUI Client.

68P02901W17-T

12-27
Jan 2010

Defining CellXchange parameters from the GUI

Chapter 12: CellXchange

Defining CellXchange parameters from the GUI

Overview of defining CellXchange parameters

It is possible to select the list of parameters that are imported or exported by means of a GUI
interface when carrying out RF Planning. The parameters are stored by default in the file
RF.CNFG which is located in:
/usr/gsm/config/global/cellX.
The parameters that can be selected are:

General, which includes Frequency Hopping Support.

Device configuration, where site, cell, DRI/RTF, and Neighbor parameters can be selected.

Handover and Power Control data.

Site Summary parameters.

CellX exports 2G and UTRAN neighbors to the neighbor file, and Blind Search neighbors to
the end of the neighbor file.

Defining CellXchange parameters

To define the parameters to be exported or imported, use the following procedure:

Display the Radio Frequency Import/Export configuration form.

Complete the General section.

Select the device parameters for import/export.

Select Handover/Power Control objects.

Save the selected import/export information.

Displaying the Radio Frequency Import/Export configuration form

To display the RF Import/Export configuration form, follow Procedure 12-19.

12-28

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Defining CellXchange parameters

Procedure 12-19 Display the RF Import/Export configuration form

1

Click the Config Mgt icon from the Front Panel to display the
Navigation Tree.

Select the network or a specific BSS.

Select Config Mgt - Cell-X-Configure from the menu bar.

Result: The Radio Frequency Import/Export configuration form is
displayed as shown in Figure 12-5.

Figure 12-5

Radio Frequency Import/Export configuration form (partial)

ti-GSM-RadioFrequencyImportExportconfigurationform_partial_-00853-ai-sw

68P02901W17-T

12-29
Jan 2010

Defining CellXchange parameters

Chapter 12: CellXchange

Completing the General section

To complete the General section of the RF Import/Export configuration form, follow these steps:

Procedure 12-20 Complete the General section of the RF Import/Export

configuration form
1

Click NO to Standard RF Import/Export at the top of the form to define

options for export or import.

Click Yes or No for each option in the General section of the window.
Refer to Table 12-1 for details.

NOTE
If Yes is selected for the Standard RF Import/Export option,
all other options in the General section of the window are
disabled.

Table 12-1 RF General Options

Parameter

Value

Description

Standard RF
Import/Export

Yes

Cell-X-Export creates cell and neighbor spreadsheets with

default values. Cell-X-Import only accepts spreadsheets
with default fields.

Enable cell priority

handling

Yes

Produces a column at the start of the cell file which may

be used to indicate the order in which cells are updated
on import. Not applicable to export.

Allow Neighbor
reciprocation

Yes

The neighbor file contains an extra column Reciprocate,

which is set to N/A on export.
If set to yes

Map Frequency
Hopping Indicator

Yes

The Frequency Hopping indicators (FHI) for each of the

RTFs are output. This information is contained in the Cell
file if the DRI/RTF file is not exported. Otherwise, it is
contained in the DRI/RTF file.

Use Frequency
Hopping System
[0..3]

Yes

Outputs the HSN (Hopping Sequence Number), MA

(Mobile allocation) and Hopping enable attributes for the
relevant Hopping system.
Continued

12-30

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Defining CellXchange parameters

Table 12-1 RF General Options (Continued)

Parameter
Enable Site
Summary

68P02901W17-T

Value
Yes

Description
Site summary details are included as extra columns in
the RFPlanSite.out

SW LoadVersion - the Site software version, for

example, 06.05.00.b4.

Cabinet Count - number of cabinets per Site.

Cabinet Type - type of cabinets in use, for example,

BTS4D_16V (0).

Frequency Type - for example, PGSM.

Path Count - number of Paths on a Site.

RSL Count - number of RSLs on a Site.

RTF Count Per Site - number of RTFs on a Site.

Cell Count Per Site - number of Cells on a Site.

RTF Count Per Cell - number of RTFs per Cell. For

example, if there are two RTFs for the first cell, three
for the second cell, and five for the third cell, this
is represented as 2/3/5.

900 - number of RTFs with the frequency 900. For

example, if the first cell has one RTF with frequency
900, the second cell has none, and the third has two,
this is represented as 1/0/2.

1800 - number of RTFs with the frequency 1800. For

example, if the first cell has one RTF with frequency
900, the second cell has none, and the third has two,
this is represented as 1/0/2.

DualBand Enabled - displays Y for Yes if at least one

Cell beneath the Site is a dualband cell, that is, the
Cell has inner_zone_alg set to Dual Band Cells Use
Algorithm. Otherwise, displays N for No.

12-31
Jan 2010

Defining CellXchange parameters

Chapter 12: CellXchange

Selecting device parameters for import/export

To select device parameters for import/export, follow Procedure 12-21.

Procedure 12-21 Select device parameters for import/export

1

To select the parameters to be imported/exported for each device, click

one of the following buttons. Refer to Figure 12-5.

DRI parameters: Configure.

RTF parameters: Configure.

SITE parameters: Configure.

Cell parameters: Configure.

Neighbor parameters: Configure.

Utran neighbor parameters: Configure.

Blind Search neighbor parameters: Configure.

The relevant device Config Detail View form is displayed. See

Figure 12-6 for an example of a cell RF Config Detailed View form.
2

Click the button next to each parameter in the Config Detail View form.
Result: The selected parameters are exported/imported.

NOTE
To obtain the relevant information for a parameter, select
On Context from the Help menu. Select and drag the
? prompt to the appropriate field and click that field. A
context-sensitive help page is displayed.
3

Select File Apply to save the new settings.

Select File Cancel to close the Config Detail View form.

Selecting Handover/Power Control objects

Click the appropriate BIN number for each Handover/Power Control object in the Radio
Frequency Import/Export configuration form (see Figure 12-5). The selected Handover/Power
Control object bins are imported/exported.

12-32

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Defining CellXchange parameters

Saving the selected import/export information

To save the selected import/export information, follow .

Procedure 12-22 Save the selected import/export information

1

Select File Save from the menu bar of the Radio Frequency
Import/Export configuration window.

Select File Close from the main menu bar to return to the Navigation
Tree.

Figure 12-6 Cell RF Config Detail View form

ti-GSM-CellRFConfigDetailViewform-00854-ai-sw

68P02901W17-T

12-33
Jan 2010

Creating an RF configuration file

Chapter 12: CellXchange

Creating an RF configuration file

The RF.CNFG file is read only. Create an RF configuration file to define options other than the
defaults. To create an RF configuration file, followProcedure 12-23.

Procedure 12-23
1

Create an RF configuration file

Refer to: Defining CellXchange parameters from the GUI on page

12-28, and carry out steps 1 to 3.
Result: The Radio Frequency Import/Export configuration window
is displayed.

To rename the file or save it to another directory, select File Save As

from the menu bar.
Result: The File Selection window is displayed.

Select the directory in the Directories list box and click Filter.

Enter the new name in the Selection text box.

Click OK to save the file and close the window.

Result: The following message is displayed in the status bar at
the bottom of the RF configuration window: Generation of RF
Import/export configuration file completed.

12-34

Select File Close from the main menu bar to return to the Navigation
Tree.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

CellXchange using the command line

CellXchange using the command line

Overview of command line utilities

It is possible to alter the configuration file (RF.CNFG) and execute Cell-X-Import or Cell-X-Export
from the command line.
The following parameters may be configured from the command line:

Configurable Cell Parameters.

Configurable Neighbor Parameters.

Support for Frequency Hopping Attributes.

Improved Performance.

Site parameters.

DRI/RTF parameters.

The following lists the five command line utilities which may be used:
rf_export

Exports the data from the MIB to ASCII files.

rf_import

Imports the data from ASCII files to the MIB.

rfNcheck

Checks and corrects Neighbor BSIC and BCCH ARFCN values.

correct_rtfs

Automatically creates/deletes RTFs to match data files.

chg_lac_ci

Allows bulk updates to LAC and CI of cells.

Task list
The following is the sequence in which the procedures should be performed when using
CellXchange from the command line:

Define the environment variables DBNAME and RFI_SEQUENTIAL_BSS_APPLY (offline

only).

Configure the configuration file (RF.CNFG) for the options required.

Execute the relevant commands.

Defining environment variables (offline only)

The CellXchange feature runs on the OLM. Therefore, before executing any of the commands,
open the corresponding Network Configuration. Refer to System Information: DataGen
(68P02900W22) for details.
68P02901W17-T

12-35
Jan 2010

Configuration file overview

Chapter 12: CellXchange

NOTE
Before using CellXchange the environment variable DBNAME and
RFI_SEQUENTIAL_BSS_APPLY must be configured.

DBNAME
If there is a single standard Network Configuration name used, then the environment variable
may be set in the users .cshrc file, alternatively this variable should be set in the appropriate
Xterm window.
To set the variable, enter the following command:
setenv DBNAME <Network Configuration Name>
Where:

is:

Network Configuration Name

the name of OLM Network Configuration in use.

RFI_SEQUENTIAL_BSS_APPLY
This environment variable improves performance of an import when changing data in multiple
BSS objects on the OLM.
Add the following line to each user's .cshrc file before using this feature:
setenv RFI_SEQUENTIAL_BSS_APPLY ON

Configuration file overview

The operation of both the export and import is controlled by a configuration file. This file by
default is called RF.CNFG and is stored in:
/usr/omc/config/global/cellX
However, if required, the name and path to the configuration file can be specified by the user.
The file contains the following sections:

12-36

Initial Comment Section.

Flags.

List of Cell Parameters.

Handover/Power Control Objects.

List of Neighbor Parameters (including Blind Search, UTRAN, and 2G neighbor

parameters).

List of site parameters.

List of DRI/RTF parameters.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Description of flags section

The file is a standard ASCII text file and can be edited using the vi editor or any suitable editor.
The # character is used to indicate a comment within the file.

NOTE
A complete RF.CNFG file is shipped with the feature. All the options are disabled
within the file. It is recommended to make a backup copy for reference before
making changes.

Description of flags section

Table 12-2 shows the flags contained within the Configuration File:

Table 12-2

Configuration file parameters

Flag name
STANDARD
_IMPORT_EXPORT

Description
If set to ON the remainder of the file is ignored and the standard fixed
file format is used.

MAP_FREQ
If set to ON the FHIs for each of the RTFs are output.
_HOP_INDICATORS
FREQHOP
SYSTEM.[0..3]

Four flags, one for each of the Hopping Systems in a cell, if set to ON the
HSN, MA, and Hopping Enabled attributes are output for all cells.

CELL_PRIORITY
_DEFINED

Produces a column at the start of the cell file which indicates the order
in which cells should be updated on import. When used the column
should numerically list the order in which the cells should be updated,
starting with the lowest number first. Duplicate numbers are allowed.
Not applicable on export.

ALLOW
_RECIPROCATION

Produces a column at the end of the Neighbor file where the option for
Neighbor reciprocation can be specified as Yes or No. Not applicable on
export.

Example of setting flags

The flags should be set at the beginning of the configuration file and must be preceded by
the keyword FLAG followed by a:
FLAG : MAP_FREQ_HOP_INDICATORS = ON
FLAG : FREQHOPSYSTEM.0 = ON
FLAG : FREQHOPSYSTEM.1 = OFF

NOTE
In the default configuration file, all flags are set to OFF.

68P02901W17-T

12-37
Jan 2010

Description of cell parameter section

Chapter 12: CellXchange

Description of cell parameter section

The operation of the export / import for cell parameters is controlled by the cell parameter
section of the configuration file. This section contains a list of cell parameters, each on a
separate line, enclosed within two specified delimiters.

Example of setting cell parameters

The order of the parameters within the list, determines the order of the columns within the
exported/imported cell file.
To enable a parameter within the configuration file, remove the # from the start of the line. To
disable a parameter, insert a# at the start of the line.
The following is an example of enabling cell parameters:
BEGIN : CELL_PARAMETERS
bsic
frequency_type
rxlev_access_min
END : CELL_PARAMETERS

NOTE
The default configuration file contains a list of all supported cell parameters. By
default, they are all disabled.

Description of neighbor parameter section

The operation of the export/import for neighbor parameters is controlled by the neighbor
parameter section of the configuration file. This section contains a list of neighbor parameters,
each on a separate line, enclosed within two specified delimiters.

12-38

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Description of handover and power control objects section

Example of setting neighbor parameters

The order of the parameters within the list determines the order of the columns within the
exported / imported neighbor file.
To enable a parameter within the configuration file remove the # from the start of the line. To
disable a parameter insert a # at the start of the line. The following is an example of enabling
Neighbor parameters:
BEGIN : NEIGHBOR_PARAMETERS
ho_margin_cell
ho_margin_rxqual
synchronized
END : NEIGHBOR_PARAMETERS

NOTE
The default configuration file contains a list of all supported neighbor parameters. By
default, they are all disabled.

Description of handover and power control objects section

The operation of the export/import for the handover and power control objects is controlled by
the handover and power control section of the configuration file. This section contains a list of
objects with their bin number, each on a separate line, enclosed within two specified delimiters.

Example of setting handover and power control objects

The order of the parameters within the list determines the order of the columns within the
exported or imported neighbor file.
To enable a parameter within the configuration file remove the # from the start of the line. To
disable a parameter insert a
#
at the start of the line.
The following is an example of enabling Handover and Power Control objects:
BEGIN : POWER_HANDOVER_OBJECTS
BIN:0 :

RelTimAdvHC

BIN:1 :

RxlevDlHC

END : POWER_HANDOVER_OBJECTS

NOTE
The default configuration file contains a list of all supported neighbor Handover and
Power Control objects. By default, they are all disabled.

68P02901W17-T

12-39
Jan 2010

Description of site parameter section

Chapter 12: CellXchange

Description of site parameter section

The operation of the export / import for site parameters is controlled by the site parameter
section of the configuration file. This section contains a list of site parameters, each on a
separate line, enclosed within two specified delimiters.

Example of setting site parameters

The order of the parameters within the list determines the order of the columns within the
exported/imported site file.
To enable a parameter within the configuration file remove the # from the start of the line. To
disable a parameter insert a # at the start of the line.
The following is an example of enabling Site parameters:
BEGIN : SITE_PARAMETERS
fm_site_type // Site Type // 1613 1620 1650 // BssRO
bts_type //BTS Configuration Type // 1613 1620 1650 //BssRW
lcf_id // LCF managing this site // 1613 1620 1650 //BssRW
bsp_lcf_id // BSP/LCF Flag // 1613 1620 1650 //BssRC
END : SITE_PARAMETERS

NOTE
The default configuration file contains a list of all supported site parameters. By
default, they are all disabled.

Description of DRI/RTF parameter section

The operation of the export/import for DRI/RTF parameters is controlled by the DRI/RTF
parameter section of the configuration file. This section contains a list of DRI/RTF parameters,
each on a separate line, enclosed within two specified delimiters.

12-40

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Description of UTRAN neighbor parameter section

Example of setting DRI/RTF parameters

The order of the parameters within the list determines the order of the columns within the
exported/imported DRI/RTF file.
To enable a parameter within the configuration file remove the # from the start of the line. To
disable a parameter insert a # at the start of the line.
The following is an example of enabling DRI parameters:
BEGIN : DRI_PARAMETERS
DRI_type //DRI type // 1613 1620 1650 // BssRC
foxFmuxConn //Connection to BTP // 1613 1620 1650 //BssRC
opto_state // No Alarm when // 1613 1620 1650 // BssRC
END : DRI_PARAMETERS
The following is an example of enabling RTF parameters:
BEGIN : RTF_PARAMETERS
Carrier_type //Carrier_type // 1613 1620 1650 //BssRC
ksw_pair //KSW pair // 1613 1620 1650 // BssRC
rtf_capacity //RTF capacity // 1613 1620 1650 // BssRC
carrier1_arfcn //carrier 1 ARFCN // 1613 1620 1650 // BssRW
END : RTF_PARAMETERS

NOTE
The default configuration file contains a list of all supported DRI/RTF parameters. By
default, they are all disabled.

Description of UTRAN neighbor parameter section

The operation of the export/import for UTRAN Neighbor parameters is controlled by the UTRAN
Neighbor parameter section of the configuration file. This section contains a list of UTRAN
Neighbor parameters, each on a separate line, enclosed within two specified delimiters.

68P02901W17-T

12-41
Jan 2010

Description of UTRAN neighbor parameter section

Chapter 12: CellXchange

Example of setting UTRAN neighbor parameters

The order of the parameters within the list determines the order of the columns within the
exported/imported UTRAN Neighbor file.
To enable a parameter within the configuration file remove the # from the start of the line. To
disable a parameter insert a # at the start of the line.
The following is an example of enabling UTRAN Neighbor parameters:
BEGIN : UTRAN_NEIGHBOUR_PARAMETERS
name
fdd_arfcn
scr_code
diversity_enabled
nmcrdninstance
END : UTRAN_NEIGHBOUR_PARAMETERS

NOTE
The default configuration file contains a list of all supported neighbor parameters. By
default, they are all disabled.

12-42

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

CellXchange command line utilities

CellXchange command line utilities

Overview of command line utilities

After setting the environment variables and configuring the RF.CNFG file, the following section
describes the utilities that may be used.
The command line utilities which may be used are:
rf_export

Exports the data from the MIB to ASCII files.

rf_import

Imports the data from ASCII files to the MIB.

rfNcheck

Checks and corrects Neighbor BSIC and BCCH ARFCN

values.

correct_rtfs

Automatically creates/deletes RTFs to match data files.

chg_lac_ci

Allows bulk updates to LAC and CI of cells.

rf_export
rf_export can be used to specify whether site, cell, DRI/RTF, neighbor, or all these parameters
are exported for the entire network, or one or more specific BSSs.

Synopsis (online environment)

rf_export [-BSS <BSS name>] [-site <site file>] [-drirtf <DRI/RTF file>] [-c
<cell file> -n <neighbor file> -s <site file> -d <dri/rtf file> -all] [-cnfg
<configuration file>]

Synopsis (offline environment)

rf_export [-db <DBname>] [-BSS <BSS name>] [-site <site file>] [-drirtf <DRI/RTF
file>] [-c <cell file> -n <neighbor file> -s <site file> -d <dri/rtf file> -all]
[-cnfg <configuration file>]
Refer to Table 12-3 for option descriptions.

68P02901W17-T

12-43
Jan 2010

rf_export

Chapter 12: CellXchange

Description
This utility exports the contents of the MIB database and produces ASCII tab delimited files for
site, cell, DRI/RTF, and neighbor parameters, if required. The columns within these files are
made up of some mandatory columns for example, the MSC name, OMC-R name, BSS name, and
also some user-defined parameters as specified in the configuration file.
The files are output to the directory: /usr/omc/config/global/cellX/<RFPlanCell.out>,
<RFPlanSite.out>, <RFPlanDRIRTF.out> or <RFPlanNeighbor.out> by default. The user can
also specify an alternative location.

Command line options

An explanation of the command line options for rf_export is given in Table 12-3.

Table 12-3 Command line options (rf_export)

Option

12-44

Description

-db <Database name>

(offline environment only)

Defines the database to be exported, applies specifically to the

Offline MIB where multiple databases may exist. If not defined,
the default of DBNAME

-BSS <BSS name>

Only export data within the specified BSS or BSSs, all other
data is ignored. If not specified the entire network is used. For
example, the following command exports data for BSSs BSSnorth
and BSSeast only: rf_export -BSS BSSnorth, BSSeast

-site <site file name>

Use to export a Site file only. This option exports the file to its
default location with its default name.

-drirtf <DRI/RTF file

name>

Use to export a DRI/RTF file only. This option exports the file to
its default location with its default name.

-c <Cell File Name and

Path>

Defines the output cell filename and path. For example, the
following command creates a cell file only for export called
mycellfile.out/usr/omc/config/global/cellXrf_export
-cell -c /usr/omc/config/global/cellX/
mycellfile.out

-n <Neighbor File Name

and Path>

Defines the output neighbor filename and path.

-s <Site File Name and

Path>

Defines the output site filename and path.

-d <DRI/RTF File Name

and Path>

Defines the output DRI/RTF filename and path.

-all

Exports all parameters to the appropriate default .out

- cnfg <Configuration File

Name and Path>

Defines the configuration file name and path to be used. If not

specified the default of /usr/omc/config/global/cellX/RF.CNFG

no arguments

If none of the above arguments are supplied, the

process exports cell and neighbor files only to
/usr/omc/config/global/cellX/RFPlanCell.out/usr/omc/
config/global/cellX/RFPlanNeighbour.out

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

rf_import

rf_import
rf_import can be used to specify whether site, cell, DRI/RTF, neighbor, or all these parameters
are imported into the network, or one or more specific BSSs.

Synopsis (online environment)

rf_import [-BSS <BSS name>] [-site <site file name>]
[-drirtf <DRI/RTF file name>][-c <cell file>
-n <neighbor file> -s <site file> -d <dri/rtf file> -all] [-cnfg <configuration
file>] [-A] [-conly] [-nonly] [-nodeletes] [-sequential] [-consistencyCheck]
[-correct_rtfs] [-correct_dris] [-no_omc_warn] [-bcchSFHenabled]

Synopsis (offline environment)

rf_import [-db <DBname>] [-BSS <BSS name>] [-site <site file name>] [-drirtf
<DRI/RTF file name>][-c <cell file>
-n <neighbor file> -s <site file> -d <dri/rtf file> -all] [-cnfg <configuration
file>] [-A] [-conly] [-nonly] [-nodeletes] [-sequential] [-consistencyCheck]
[-correct_rtfs] [-correct_dris] [-no_omc_warn] [-bcchSFHenabled]
Refer to: Table 12-4 for option descriptions.

Description
This utility reads ASCII tab delimited files and compares each attribute value in the files to
the value in MIB. If the values are different the process attempts to update the MIB with the
value from the file.

Command line options

An explanation of the command line options rf_import is given in Table 12-4.

Table 12-4 Command line options (rf_import)

Option

Description

-db <Database Name>

(offline environment only)

Defines the database name, applies specifically to the Offline MIB

where multiple databases may exist. If not defined, the default
of DBNAME

-BSS <BSS name>

Only import data within the specified BSS, all other data is
ignored. If not specified the entire network is used.
For example, the following command imports data for BSSs
BSSnorth and BSSeast only: rf_import -BSS BSSnorth,
BSSeast

-site <site file name>

Use to import a site file only.

Continued

68P02901W17-T

12-45
Jan 2010

rf_import

Chapter 12: CellXchange

Table 12-4 Command line options (rf_import) (Continued)

Option

12-46

Description

-drirtf <DRI/RTF file

name>

Use to import a DRI/RTF file only.

-c <Cell File Name and

Path>

Defines the cell file name and path. For example,

the following command imports a cell file called
mycellfile.in/usr/omc/config/global/cellXrf_import -cell
-c /usr/omc/config/global/cellX/
mycellfile.in

-n <Neighbor File Name

and Path>

Defines the neighbor file input name.

-s <Site File Name and

Path>

Defines the site input file name.

-d <DRI/RTF File Name

and Path>

Defines the DRI/RTF input file name.

- cnfg <Configuration File

Name and Path>

Defines the name and path of configuration file to use

during the import. If not specified then the default of
/usr/omc/config/global/cellX/RF.CNFG

no arguments

If none of the above arguments are supplied, the

process imports cell and neighbor files only to
/usr/omc/config/global/cellX/RFPlanCell.in/usr/omc/
config/global/cellX/RFPlanNeighbour.in

-all

Imports all parameters from the appropriate default .in

-A

Attempt to set all data from files to the MIB. Use this option
only when the integrity of the MIB data is in doubt.

-conly

Update cell information only (for backward compatibility only).

-nonly

Update neighbor information only (for backward compatibility).

-nodeletes

No neighbor deletes are performed during the import, neighbors

are created and updated if required.

-sequential

Updates are made to each BSS sequentially.

This option is not recommended at an OMC-R.

-consistencyCheck

This option performs an import up to the consistency check point

to ensure, that all cells referenced in the MIB are present in the
Import files and vice-versa.

-correct_rtfs

Automatically runs the correct_rtfs utility before performing the

import. Refer to: correct_rtfs section for details.

-correct_dris

Automatically runs the correct_dris utility before performing the

import.

-no_omc_warn

Prevents warnings being displayed at the OMC-R. When this

option is used, the following system prompts are not displayed:
You are importing on a live OMC,
do you want to continue?Inconsistencies have been
detected,
do you want to continue?

-bcchSFHenabled

Updates are not made to hopping systems which affect the BCCH
carrier for the cell.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

rfNcheck

rfNcheck
rfNcheck compares the BSIC and BCCH ARFCN of each Neighbor defined in the MIB, with the
data in the cell (provided the cell exists in the MIB).

Synopsis (online environment)

rfNcheck [-sequential]

Synopsis (offline environment)

rfNcheck [-db <DBname>] [-sequential]
Refer to: Table 12-5 for option descriptions.

Description
Once the comparison is complete and if the values specified in the Neighbor do not match the
cell values, then the Neighbor is automatically updated to the correct value.
In the case where the cell is not in the MIB then each occurrence of the relevant Neighbor is
compared against each other and if inconsistencies are found it is reported to the user but
not corrected.

Command line options

An explanation of the command line options for rfNcheck is given in Table 12-5.

Table 12-5 Command line options (rfNcheck)

Description

Option
-db <Database Name>
(offline environment
only)

Defines the database name. If not defined, the default of DBNAME

-sequential

Updates are made to each BSS in the network sequentially.

NOTE
This option is not recommended at an OMC-R.

correct_rtfs
correct_rtfs attempts to correct the number of RTFs equipped in the MIB against the number
of TRXs defined in the import cell file.

68P02901W17-T

12-47
Jan 2010

correct_rtfs

Chapter 12: CellXchange

Synopsis (online environment)

correct_rtfs [-BSS <BSS name>] [-c <cell file> -n <neighbor file> -d <DRI/RTF
file>] [-cnfg <configuration file>] [-sequential]

Synopsis (offline environment)

correct_rtfs [-db <DBname>] [-BSS <BSS name>] [-c <cell file> -n <neighbor file>
-d <DRI/RTF file>] [-cnfg <configuration file>] [-sequential]
Refer to: Table 12-6 for option descriptions.

Description
This utility creates or deletes automatically RTFs, if the number equipped in the MIB does not
match the number specified in the import cell file.
For example, where a cell in the MIB has no RTFs currently equipped then an RTF Group, BCCH
RTF and subsequent Non-BCCH RTFs are equipped.

NOTE
Only the RTFs are created or deleted. It is assumed that the dependant hardware for
RTFs, for example, DRIs are equipped.

Command line options

An explanation of the command line options for correct_rtfs is given in Table 12-6.

Table 12-6 Command line options (correct_rtfs)

Option

Description

-db <Database Name>

(offline environment only)

Defines the database name. If not defined, the default of DBNAME

is used.

-BSS <BSS name>

Only import data for cells within the specified BSS, all other data
is ignored. If not specified the entire network is used.

-c <Cell File Name and

Path>

Defines the cell file name and path. If not specified then the
default of /usr/omc/config/global/cellX/RFPlanCell.in is used.

-n <Neighbor File Name

and Path>

Defines the neighbor file input name. If not specified then the
default of /usr/omc/config/global/cellX/RFPlanNeighbour.in is
used.

-d <DRI/RTF File Name

and Path>

Defines the DRI/RTF file input name. If not specified then the
default of /usr/omc/config/global/cellX/RFPlanDRIRTF.in is used.

- cnfg <Configuration File

Name and Path>

Defines the name and path of the configuration file to use

during the import. If not specified then the default of
/usr/omc/config/global/cellX/RF.CNFG is used.
Continued

12-48

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

correct_rtfs

Table 12-6 Command line options (correct_rtfs) (Continued)

Description

Option
-sequential

Updates are made to each BSS in the network sequentially.

NOTE
This option is not recommended at an OMC-R.

Additional information - correct_rtfs

The correct_rtfs command creates or deletes automatically RTFs. This occurs when the
number equipped in the MIB does not match the number specified in the import cell or DRI/RTF
file.
Table 12-7 describes the initialization values applied when an RTF is created.

Creating an RTF
Table 12-7 RTF attributes
Parameter

Value obtained from

Carrier Type

Cell or DRI/RTF import file.

KSW Pair

Default 0.

Path Id1

Default 0, if fails path is set to 1.

RTF Capacity

Default 0.

ARFCN

Cell or DRI/RTF import file.

FHI1 - FHI8

Cell or DRI/RTF import file, if not specified, the default is 255.

Cell ID

Cell or DRI/RTF import file.

TSC 1 - TSC 8

Determined from BSIC in cell import file.

rdnInstance

Assigned next available value.

cell_zone

Default 0.

ext_timeslots

Default 0.

sd_load

Default 2 or 0 depending on cell frequency type.

chanAllocPriority

Default 0.

68P02901W17-T

12-49
Jan 2010

chg_lac_ci

Chapter 12: CellXchange

Deleting an RTF
If an RTF is deleted the last (highest) rdnInstance is deleted.
When an RTF cannot be deleted, an appropriate error message is output to the following log
file: /usr/omc/logs/usrauditlogs/rfi<yyyymmdd>. For example, an RTF cannot be deleted when
the RTF is enabled by GPRS.

NOTE
Only the RTFs are created or deleted. It is assumed that the dependent hardware for
RTFs, for example, DRIs are equipped.

chg_lac_ci
chg_lac_ci may change the Location Area Code (LAC) or Cell ID(CI) of a cell or cells within a
network.

Synopsis (online environment)

chg_lac_ci -f <filename>

Synopsis (offline environment)

chg_lac_ci -f <filename> -db <DBname>
Where:

is:

filename

the name and path of a spreadsheet file.

Description
A spreadsheet file may be created with five tab delimited columns using a text editor of choice.
The wildcard (*) character denotes match any and may be used within any column.

12-50

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

chg_lac_ci

Example
Example of chg_lac_ci spreadsheet:
BSS Name

Old LAC

Old CI

New LAC

New CI

100

200

100

200

BSS 1

100

200

Row two changes all cells within the network, with a LAC of 100 and CI of 4 to a new LAC
of 200 and CI of 8.
Row three changes all cells within the network, with a LAC of 100 to 200 retaining the same CI.
Row four changes only cells within BSS 1, with a LAC of 100 to 200 retaining the same CI.

68P02901W17-T

12-51
Jan 2010

Troubleshooting Cell-X-Import

Chapter 12: CellXchange

Troubleshooting Cell-X-Import

Overview of Cell-X-Import file

The order of TRXs in the import file is important for CellXchange. The import of cell information
assumes that the TRXs are ordered by the RTF identifier. If the order is not maintained in the
import file then a number of arfcn clashes occur during the import.
If the ordering of the TRXs cannot be maintained in the import file, then it is necessary to set up
a dummy or unused ARFCN frequency to allow the import to work.

Setting up a dummy ARFCN

To define a dummy ARFCN the following environment variable must be set in the user's .cshrc
file:
setenv RFI_USE_DUMMY_ARFCNS ON
Then depending on the frequency type within the network, set the appropriate dummy
frequency environment variable:
setenv RFI_DUMMY_ARFCN_PGSM <unused frequency>
setenv RFI_DUMMY_ARFCN_EGSM <unused frequency>
setenv RFI_DUMMY_ARFCN_DCS1800 <unused frequency>
setenv RFI_DUMMY_ARFCN_PCS1900 <unused frequency>

12-52

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

CellXchange import and export tables

CellXchange import and export tables

Introduction to exporting/importing parameters

The following tables show the Cell, Neighbor, site, RTF, and DRI parameters that may be
exported or imported.

NOTE
For further information on the values for BCCH, ARFCN and TRX refer to: Technical

Description: BSS Command Reference (68P02901W23).

NOTE
When performing an import, if any of the following are changing on a cell that
has frequency hopping enabled, include the parameter hopping_support in the
configuration file used with the import:

ARFCN.

FHIs.

MA list.

HSN.

FHSs

Hopping_support.

Creation/deletion of RTFs.

Cell parameters
Table 12-8 and Table 12-9 show the cell parameters that can be exported/imported. Table 12-8
shows the cell parameters that will be exported/imported by default when cell parameter export
is specified. Table 12-9 shows a list of the cell parameters from which the user can select
the parameters to be exported/imported, see Defining CellXchange parameters from the GUI
on page 12-28 for further details.

68P02901W17-T

12-53
Jan 2010

Cell parameters

Chapter 12: CellXchange

NOTE
Some RTF information appears in the cell import/export file, such as frequency
hopping and ARFCN parameters. If the user chooses not to export a DRI/RTF file, the
RTF information remains in the cell export/import file. However, if the user chooses
to export a DRI/RTF file, the RTF information is included in the DRI/RFT files instead
of in the cell file.

Default RF cell parameters

Table 12-8 lists the GUI field names of the cell parameters that are exported or imported if
default RF cell settings are used.

Table 12-8 RFPlanCell default parameters

Field

12-54

Description

MSC Name

Specifies the MSC name which is responsible for the cell.

OMC Name

Specifies the OMC-R name which is responsible for the cell.

BSS Name

Specifies the BSS name to which the cell belongs.

Site Name

Specifies the site name within the BSS.

Site Lat

Specifies the geographical latitude in decimal of the logical site. In most cases,
it is identical to Cell Latitude. An exception is Top Cell.

Site Long

Specifies the geographical longitude in decimal of the logical site. In most

cases, it is identical to Cell Longitude. An exception is Top Cell.

Cell Lat

Specifies the latitude of the cell in decimal notation.

Cell Long

Specifies the longitude of the cell in decimal notation.

Freq Type

Specifies the frequency type of the cell. The value must be in the form of
an integer in the set {1,2,4,8}, where 1 = PGSM900, 2 = EGSM900, 4 =
DCS1800, 8 = PCS1900.

MCC

Specifies the Mobile Country Code for the cell.

MNC

Specifies the Mobile Network Code for the cell.

LAC

Specifies the Location Area Code for the cell.

CI

Specifies the Cell ID of the cell.

BSIC

Specifies the Base Station Identity Code for the cell.

Beam Width

Specifies the beam width of the antenna in an integer number of degrees.

Orientation

Specifies the direction of the antenna in an integer number of degrees.

Layer Type

Specifies the layer type of a cell. The value must be in the form of an integer in
the set {0,1,2},. where 0 = Macro Layer, 1 = Micro Layer (Street coverage), 3
= Pico Layer (In-Building coverage).

BCCH
ARFCN

Specifies a BCCH frequency for the cell. The value allowed depends on the
Frequency Type.

TRX

Specifies a non BCCH frequency for the cell. The value allowed depends on
the Freq type. This column may be repeated up to the maximum numbers of
carriers allowed (25 including BCCH carriers).

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell parameters

User selectable cell parameters

Table 12-9 lists the cell parameters, and their GUI field names, that can be selected by a user for
inclusion in the cell export/import file.

Table 12-9 User selectable cell parameters

OMC-R Parameter Name

Description

adap_ho_al_trg_rq

Adaptive Alt Trigger Rxqual HO.

adap_ho_pbgt

Adaptive Pwr Budget HO Alg.

adap_ho_rxlev

Adaptive Rxlev HO Alg.

adap_ho_rxqual

Adaptive Rxqual HO Alg.

adap_trg_hop_rqdl

Adap Rxqual Hop HO Trigger DL

adap_trg_hop_rqul

Adap Rxqual Hop HO Trigger UL

adap_trig_rl_dl

Adaptive Rxlev HO Trigger on DL.

adap_trig_rl_ul

Adaptive Rxlev HO Trigger on UL

adap_trig_rq_dl

Adaptive Rxqual HO Trigger on DL

adap_trig_rq_ul

Adaptive Rxqual HO Trigger on UL

adap_trigger_pbgt

Adaptive Pwr Budget HO Trigger.

alt_qual_proc

Alt Quality Procedure.

amr_fr_acs

AMR Full Rate Active Codec Set.

amr_fr_dl_hys1

AMR Full Rate Downlink Hysteresis 1.

amr_fr_dl_hys1Hop

AMR Full Rate Downlink Hysteresis 1 Hopping.

amr_fr_dl_hys2

AMR Full Rate Downlink Hysteresis 2.

amr_fr_dl_hys2Hop

AMR Full Rate Downlink Hysteresis 2 Hopping.

amr_fr_dl_hys3

AMR Full Rate Downlink Hysteresis 3.

amr_fr_dl_hys3Hop

AMR Full Rate Downlink Hysteresis 3 Hopping.

amr_fr_dl_thr1

AMR Full Rate Downlink Threshold 1.

amr_fr_dl_thr1Hop

AMR Full Rate Downlink Threshold 1 Hopping.

amr_fr_dl_thr2

AMR Full Rate Downlink Threshold 2.

amr_fr_dl_thr2Hop

AMR Full Rate Downlink Threshold 2 Hopping.

amr_fr_dl_thr3

AMR Full Rate Downlink Threshold 3.

amr_fr_dl_thr3Hop

AMR Full Rate Downlink Threshold 3 Hopping.

amr_fr_enabled

AMR Full Rate Enabled

amr_fr_icm

AMR Full Rate Initial Codec Mode.

amr_fr_ul_hys1

AMR Full Rate Uplink Hysteresis 1.

amr_fr_ul_hys1Hop

AMR Full Rate Uplink Hysteresis 1 Hopping.

amr_fr_ul_hys2

AMR Full Rate Uplink Hysteresis 2.

Continued

68P02901W17-T

12-55
Jan 2010

Cell parameters

Chapter 12: CellXchange

Table 12-9 User selectable cell parameters (Continued)

OMC-R Parameter Name

Description

amr_fr_ul_hys2Hop

AMR Full Rate Uplink Hysteresis 2 Hopping.

amr_fr_ul_hys3

AMR Full Rate Uplink Hysteresis 3.

amr_fr_ul_hys3Hop

AMR Full Rate Uplink Hysteresis 3 Hopping.

amr_fr_ul_thr1

AMR Full Rate Uplink Threshold 1.

amr_fr_ul_thr1Hop

AMR Full Rate Uplink Threshold 1 Hopping.

amr_fr_ul_thr2

AMR Full Rate Uplink Threshold 2.

amr_fr_ul_thr2Hop

AMR Full Rate Uplink Threshold 2 Hopping.

amr_fr_ul_thr3

AMR Full Rate Uplink Threshold 3.

amr_fr_ul_thr3Hop

AMR Full Rate Uplink Threshold 3 Hopping.

amr_hr_acs

AMR Half Rate Active Codec Set.

amr_hr_dl_hys1

AMR Half Rate Downlink Hysteresis 1.

amr_hr_dl_hys1Hop

AMR Half Rate Downlink Hysteresis 1 Hopping.

amr_hr_dl_hys2

AMR Half Rate Downlink Hysteresis 2.

amr_hr_dl_hys2Hop

AMR Half Rate Downlink Hysteresis 2 Hopping.

amr_hr_dl_hys3

AMR Half Rate Downlink Hysteresis 3.

amr_hr_dl_hys3Hop

AMR Half Rate Downlink Hysteresis 3 Hopping.

amr_hr_dl_thr1

AMR Half Rate Downlink Threshold 1.

amr_hr_dl_thr1Hop

AMR Half Rate Downlink Threshold 1 Hopping.

amr_hr_dl_thr2

AMR Half Rate Downlink Threshold 2.

amr_hr_dl_thr2Hop

AMR Half Rate Downlink Threshold 2 Hopping.

amr_hr_dl_thr3

AMR Half Rate Downlink Threshold 3.

amr_hr_dl_thr3Hop

AMR Half Rate Downlink Threshold 3 Hopping.

amr_hr_icm

AMR Half Rate Initial Codec Mode.

amr_hr_ul_hys1

AMR Half Rate Uplink Hysteresis 1.

amr_hr_ul_hys1Hop

AMR Half Rate Uplink Hysteresis 1 Hopping.

amr_hr_ul_hys2

AMR Half Rate Uplink Hysteresis 2.

amr_hr_ul_hys2Hop

AMR Half Rate Uplink Hysteresis 2 Hopping.

amr_hr_ul_hys3

AMR Half Rate Uplink Hysteresis 3.

amr_hr_ul_hys3Hop

AMR Half Rate Uplink Hysteresis 3 Hopping.

amr_hr_ul_thr1

AMR Half Rate Uplink Threshold 1.

amr_hr_ul_thr1Hop

AMR Half Rate Uplink Threshold 1 Hopping.

amr_hr_ul_thr2

AMR Half Rate Uplink Threshold 2.

amr_hr_ul_thr2Hop

AMR Half Rate Uplink Threshold 2 Hopping.

amr_hr_ul_thr3

AMR Half Rate Uplink Threshold 3.

Continued

12-56

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell parameters

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

amr_hr_ul_thr3Hop

AMR Half Rate Uplink Threshold 3 Hopping.

AmrFrDlLaEnabled

AMR FR Downlink Link Adaptation Enabled.

AmrFrUlLaEnabled

AMR FR Uplink Link Adaptation Enabled.

AmrHrUlLaEnabled

AMR HR Uplink Link Adaptation Enabled.

AmrHrDlLaEnabled

AMR HR Downlink Link Adaptation Enabled.

AmrHrIntHoAllwd

AMR Half Rate Intracell Handover Allowed.

antennaDirection

The direction of the antenna.

attach_detach

IMSI Attach/Detach.

auto_rf_loss

Automatic RF Loss Trace Reporting.

ba_alloc_proc

BA Re-Initialization.

band_pref_mode

Band Preference Mode.

band_preference

Band Preference.

bandReassignDelay

SDCCH to TCH Band Reassign Delay.

beamWidth

The beam width of the antenna.

blindSearchPref

Blind Search Preference.

bnce_prt_cong_tmr

Bounce Protect Congestion HandOver Timer.

bnce_prt_mgn

Bounce Protect HandOver Margin.

bnce_prt_qual_tmr

Bounce Protect Quality HandOver Timer.

bs_ag_blks_res

Number of Reserved Access Grant Blocks.

bs_pa_mfrms

Period Between Mobile Paging Messages.

bs_pag_blks_res

Number of PAGCH Blocks per Multiframe.

bs_pbcch_blks

Number of Blocks Allocated to PBCCH.

bs_pcc_chans

Number of PCCCH timeslots.

bs_prach_blks

Number of PRACH Blocks per Multiframe.

bts_p_con_ack

BTS Power Control Acknowledgment.

bts_p_con_intervl

BTS Power Level Changes Min Interval.

btsPwrCntlAllowed

BTS Power Control.

btsTxPwrMax_inner

BTS Max Transmit Pwr for Inner Zone.

bvci

BVCI.

c31_hyst

C31 Hysteresis.

c32_qual

C32 Exception Rule.

cbch_enabled

Cell Broadcast Channel (CBCH).

ccch_conf

CCCH Configuration.

ccch_load_period

CCCH Load Period.

Continued

68P02901W17-T

12-57
Jan 2010

Cell parameters

Chapter 12: CellXchange

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

cell_bar_qualify

Low Cell Selection Priority.

cellBarAccClass

Cell Barred Access Class.

cellBarAccess

Subscriber Access to Cell.

cellReselectHys

Cell Reselect Hysteresis Level.

cellReselectOffs

Cell Reselect Offset.

cellReselParamInd

Cell Reselection Parameters.

channelReconfig

Channel Reconfiguration.

coincident_cell

Coincident Cell.

coincident_mb

Coincident MB HO Status.

coincident_offset

Coincident Offset to HO Margin.

congest_at_source

Congestion at Source Cell.

congest_at_target

Congestion at Target Cell.

current_pcu

Current PCU.

data_qual_enabled

Alt Data Quality Thresholds.

dealloc_inact

Deallocate Inactive Timer.

dec1DlRxlevAv_h

Downlink Signal Strength HandOver Bin.

dec1DlRxlevAv_ih

Downlink Signal Interference HandOver Bin.

dec1DlRxlevAv_p

DL Signal Strength Power Change Bin.

dec1DlRxqualAv_h

Downlink Receive Quality HandOver Bin.

dec1DlRxqualAv_p

DL Receive Quality Power Change Bin.

dec1NcellRxlevAvH

Neighbor Cell Signal Strength HandOver Bin.

dec1PBgtRxlevAv_h

Power Budget HandOver Bin.

dec1TimAdvAv_alg

Mobile Station Distance HandOver Bin.

dec1UlRxlevAv_h

Uplink Signal Strength HandOver Bin.

dec1UlRxlevAv_ih

Uplink Signal Interference HandOver Bin.

dec1UlRxlevAv_p

UL Signal Strength Power Change Bin.

dec1UlRxqualAv_h

Uplink Receive Quality HandOver Bin.

dec1UlRxqualAv_p

UL Receive Quality Power Change Bin.

decision_1_n1

Decision Algorithm Parameter N1.

decision_1_n2

Decision Algorithm Parameter N2.

decision_1_n3

Decision Algorithm Parameter N3.

decision_1_n4

Decision Algorithm Parameter N4.

decision_1_n5

Decision Algorithm Parameter N5.

decision_1_n6

Decision Algorithm Parameter N6.

Continued

12-58

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell parameters

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

decision_1_n7

Decision Algorithm Parameter N7.

decision_1_n8

Decision Algorithm Parameter N8.

decision_1_p1

Decision Algorithm Parameter P1.

decision_1_p2

Decision Algorithm Parameter P2.

decision_1_p3

Decision Algorithm Parameter P3.

decision_1_p4

Decision Algorithm Parameter P4.

decision_1_p5

Decision Algorithm Parameter P5.

decision_1_p6

Decision Algorithm Parameter P6.

decision_1_p7

Decision Algorithm Parameter P7.

decision_1_p8

Decision Algorithm Parameter P8.

decision_alg_type

Decision Algorithm Type.

disuse_cnt_flag

Max Disuse Count based on Hreqave.

dl_dtx_voice_data

Downlink DTX for Voice/Data.

dlRxlevHoAllowed

Downlink Receive Level Handover.

dlRxqualHoAllowed

Downlink Receive Quality. Handover

dr_ho_dur_assign

Directed Retry HandOver during Assign.

dr_in_zon_thresh

Direct Inner Zone Threshold

dr_std_congest

Directed Retry Standard Congestion Allowed.

dtx_required

Discontinuous Transmission Mode.

dualBand_offset

Dual Band Offset.

dyn_step_adj

Dynamic Step Adjustment Alg.

dyn_step_adj_fmpr

Factor of Max Pwr Reduction.

egprs_init_dl_cs

EGPRS Initial Downlink Coding Scheme.

egprs_init_ul_cs

EGPRS Initial Uplink Coding Scheme.

egsm_bcch_sd

EGSM Carrier Configuration Information.

egsm_ho_thresh

EGSM Handover Threshold.

emergencyClass

Emergency Class Switch.

en_incom_ho

Enable Incoming Handovers.

enhanced_relief

Enhanced Relief.

erc_ta_priority

Ext Range Neighbor Priority.

exRtryCandPrd

External Retry Period Timer.

ext_range_cell

Extended Range Cell.

extendedPagingAct

Activate Extended Paging.

fdd_gprs_qoffset

FDD Cell Reselection Offset.

Continued

68P02901W17-T

12-59
Jan 2010

Cell parameters

Chapter 12: CellXchange

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

fdd_qmin

Minimum Ec/No Threshold.

fdd_qoffset

Receive Signal Code Power Threshold.

fdd_rep_quant

UTRAN Reporting Quality.

fddMultiratRprtng

Number of UTRAN FDD cells to report.

flow_control_t1

Flow Control T1 Timer.

flow_control_t2

Flow Control T2 Timer.

frequency_type

Frequency Type.

full_pwr_rfloss

Full Power Radio Frequency Before Loss.

gprs_bs_cv_max

Max MS Count Down Value.

gprs_cr_margin

PMR Threshold.

gprs_drx_time_max

Max MS Non-DRX Mode Request Time.

gprs_enabled

GPRS Enabled.

gprs_intraho_allw

GPRS Intra-Cell HO Allowed.

gprs_min_prr_blks

Minimal Number of Dynamic PRR Blocks.

gprs_ms_pan_dec

MS Counter N3102 Decrement.

gprs_ms_pan_inc

MS Counter N3102 Increment.

gprs_ms_pan_max

Max MS Counter N3102.

gprs_ms_txpwr_cch

GPRS Max CCH Transmit Power.

gprs_mx_txpwr_cch

GPRS MS Max Transmit Power.

gprs_num_pmrs

Bad PMRs.

gprs_par_wait_ind

PAR Waiting Time.

gprs_pb

BCCH Blocks Power Reduction.

gprs_pc_alpha

Power Offset Multiplier.

gprs_penalty_time

GPRS Penalty Time.

gprs_rec_idle_tch

Reconfig Idle TCH Threshold.

gprs_reselect_hys

GPRS Cell Reselection Hysteresis.

gprs_rxlev_ac_min

GPRS Minimum Receive Level.

gprs_smg30_t3192

T3192 (SMG24-SMG30).

gprs_t3168

T3168.

gprs_t3192

T3192.

gprs_temp_offset

GPRS Negative C32 Offset.

gprs_ts_confg_alg

GPRS Timeslot Configuration Algorithm.

gprsReselectOffs

GPRS Cell Reselect Offset.

handoverPwrLevel

Mobile Station HandOver Power Level.

Continued

12-60

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell parameters

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

handoverRecPeriod

Minimum Handover Recognized Period.

hcs_thr

HCS Signal Strength.

ho_ack

Handover Acknowledgment Timer.

ho_exist_congest

Handover existing calls.

ho_margin_def

Handover Margin Default.

ho_mgn_use_flag

Handover Margin Usage Flag.

ho_onlymax_pwr

HandOver UL/DL with MS/BSS at Full Pwr.

hop_count

Hop Count.

hop_count_timer

Hop Count Timer.

hop_qual_enabled

Alt Hopping Quality Thresholds.

hopping_support

Hopping Support.

hoPwrLevel_inner

HO Power level for Inner Zone.

hr_enabled

Half Rate Enabled.

hr_fr_hop_count

HR FR Hop Count.

hr_intracell_ho_allowed

Half Rate Intracell Allowed.

hr_res_ts

Half Rate Reserved Timeslot.

imrm_dcs18_weight

IMRM DCS1800 Weighting (0-100).

imrm_egsm_weight

IMRM EGSM Weighting (0-100).

imrm_force_recalc

IMRM Force Recalculation.

imrm_pgsm_weight

IMRM PGSM Weighting (0100).

imrm_umts_weight

IMRM UMTS Weighting (0-100).

init_dl_cs

Initial Downlink Coding Scheme.

init_ul_cs

Initial Uplink Coding Scheme.

inner_zone_alg

Inner Zone Algorithm.

InnHrUseThres

Inner Half Rate Usage Threshold.

intave

Interference Average.

inter_rat_enabled

Inter-RAT Handovers Enabled.

interbandHoAllwd

Interband Handover Allowed.

interCellHoAllowd

Inter-Cell Handover.

interfer_band0

Interference Band 0.

interfer_band1

Interference Band 1.

interfer_band2

Interference Band 2.

interfer_band3

Interference Band 3.

interfer_band4

Interference Band 4.
Continued

68P02901W17-T

12-61
Jan 2010

Cell parameters

Chapter 12: CellXchange

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

interferHoAllowed

Interference Handover.

intraCellHoAllowd

Intra-Cell Handover.

l_rxlev_dl_h

Lower Downlink Receive Level (HandOver).

l_rxlev_dl_p

Lower DownLink Receive Level (Pwr)

l_rxlev_ul_h

Lower Uplink Receive Level (HandOver).

l_rxlev_ul_p

Lower Uplink Receive Level (Pwr).

l_rxqual_dl_h

Lower Downlink Receive Quality (HandOver).

l_rxqual_dl_p

Lower Downlink Receive Quality (Pwr).

l_rxqual_ul_h

Lower Uplink Receive Quality (HandOver).

l_rxqual_ul_p

Lower Uplink Signal Quality (Pwr).

latitude

The latitude of the Cell.

layer_number

Layer Number.

link_fail

Link Fail Threshold.

linkAboutToFail

Link About To Fail Threshold.

longitude

The longitude of the Cell.

low_sig_thresh

Coincident Low Sig Threshold.

lRxqualDlHData

Lower Downlink Rcv Qual (HO) Data.

lRxqualDlHHopping

Lower Downlink Rcv Qual (HO) Hopping.

lRxqualDlPData

Lower Downlink Rcv Qual (Pwr) Data.

lRxqualDlPHopping

Lower Downlink Rcv Qual (Pwr) Hopping.

lRxqualUlHData

Lower Uplink Rcv Qual (HO) Data.

lRxqualUlHHopping

Lower Uplink Rcv Qual (HO) Hopping.

lRxqualUlPData

Lower Uplink Rcv Qual (Pwr) Data.

lRxqualUlPHopping

Lower Uplink Rcv Qual (Pwr) Hopping.

lRxqUlHHopAmrFr

AMR FR Lower Uplink Rcv Qual (HO) Hopping.

lRxqualUlHAmrFr

AMR FR Lower Uplink Receive Quality (HO).

lRxqualDlHAmrFr

AMR FR Lower Downlink Receive Quality (HO).

lRxqDlHHopAmrFr

AMR FR Lower Downlink Rcv Qual (HO) Hopping.

lRxqualUlPAmrFr

AMR FR Lower Uplink Signal Quality (Pwr).

lRxqUlPHopAmrFr

AMR FR Lower Uplink Rcv Qual (Pwr) Hopping.

lRxqualDlPAmrFr

AMR FR Lower Downlink Receive Quality (Pwr).

lRxqDlPHopAmrFr

AMR FR Lower Downlink Rcv Qual (Pwr) Hopping.

lRxqualUlHHr

HR Lower Uplink Receive Qual (HO).

lRxqUlHHopHr

HR Lower Uplink Rcv Qual (HO) Hopping.

Continued

12-62

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell parameters

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

lRxqualDlHHr

HR Lower Downlink Rcv Qual (HO).

lRxqDlPHopHr

HR Lower Downlink Rcv Qual (Pwr) Hopping.

lRxqualDlPHr

HR Lower Downlink Rcv Qual (Pwr).

lRxqDlHHopHr

HR Lower Downlink Rcv Qual (HO) Hopping.

lRxqualUlPHr

HR Lower Uplink Signal Quality (Pwr).

lRxqUlPHopHr

HR Lower Uplink Rcv Qual (Pwr) Hopping.

uRxqualDlPHr

HR Upper Downlink Signal Qual (Pwr).

uRxqualUlPHr

HR Upper Uplink Signal Quality (Pwr).

max_ts_per_cr

Maximum GPRS Data Timeslots per Carrier.

max_ms_dl_buffer

Max MS Downlink Buffer.

max_ms_dl_rate

Max MS Downlink Rate.

max_retran

Maximum Retransmissions.

max_tx_bts

Maximum Transmit Power for BTS.

max_tx_ms

Maximum Mobile Station Transmit Power.

maxNumberOfSdcch

Maximum Number of SDCCH.

maxQLengthChan

Max Queue Length Channel.

maxQLgtFullRtChan

Max Queue Length Full Rate Channel.

maxQLgtSdcchs

Maximum Queue Length SDCCH.

mb_tch_cong_thres

MB TCH Congestion Threshold.

missing_rpt

Missing Measurement Report.

ms_max_range

Mobile Station Maximum Timing Advance.

ms_p_con_ack

MS Power Control Message Acknowledge.

ms_p_con_interval

Mobile Station Power Control Interval.

ms_power_offset

Mobile Station Power Offset.

ms_txpwr_max_cch

Maximum Control Channel Transmit Power.

ms_txpwr_max_def

Maximum Default Transmit Power.

msc_preference

MSC Preference.

msDistanceAllowed

Mobile Station Distance Handover.

msPowerCntlAllowd

MS Power Control.

mspwr_alg

MS Power Control Processing.

mstxpwr_max_inner

Max MS Transmit Pwr When HO to Inner Zone.

multibandRprtng

MultiBand Reporting.

n_avg

Radio Blocks.

n_avg_i

Signal Strength Measurements.

Continued

68P02901W17-T

12-63
Jan 2010

Cell parameters

Chapter 12: CellXchange

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

nccOfPlmnAllowed

NCC of PLMN Allowed.

nch_position

NCH Position.

nei_rpt_timer

Concentric Cell Neighbor Report Timer.

neighbor_journ

Nbr Journaling.

network_ctrl_order

Network Control Order.

new_calls_hr

New Calls Half Rate.

numOfPrefCells

Maximum Number of Preferred Cells.

numSdcchsPref

Preferred Number of SDCCH.

outzone_usage_lev

Outer Zone Usage Level.

pbgt_mode

Power Budget Mode.

pc_meas_chan

Downlink Power Measurment Chan.

pcch_drx_max_t

Non-DRX Mode Transfer Period Duration.

pcch_enabled

PBCCH/PCCCH enabled.

penalty_time

Penalty Time.

persistent_lvl_1 to 4

Persistent Level 1 to 4.

pow_inc_stepsz_dl

Power Increase Step Size DL.

pow_inc_stepsz_ul

Power Increase Step Size UL.

pow_red_stepsz_dl

Power Reduction Step Size DL.

pow_red_stepsz_ul

Power Reduction Step Size UL.

prach_mx_retran_1 to 4

Retransmissions Allowed for Radio Priority 1 to 4.

prach_s

Slots Between Channel Request.

prach_tx_int

Slots to Spread Random Access Transmission.

primary_pcu

Primary PCU.

prior_micro

Prioritize Microcell

priority_class

HCS Priority Class.

protect_last_ts

GPRS Protect Last Timeslot.

psi1_repeat_prd

Time Interval for Scheduling PSI Messages.

pwrc

Power Excluding Broadcast Ctrl Channels.

pwrHoAllowed

Power Budget Handover.

qos_mtbr_i1_dl

Downlink MTBR for Interactive THP 1.

qos_mtbr_i1_ul

Uplink MTBR for Interactive THP 1.

qos_mtbr_i2_dl

Downlink MTBR for Interactive THP 2.

qos_mtbr_i2_ul

Uplink MTBR for Interactive THP 2.

qos_mtbr_i3_dl

Downlink MTBR for Interactive THP 3.

Continued

12-64

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Cell parameters

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

qos_mtbr_i3_ul

Uplink MTBR for Interactive THP 3.

qos_mtbr_be_dl

Downlink MTBR for Best Effort Traffic Class.

qos_mtbr_be_ul

Uplink MTBR for Best Effort Traffic Class.

qos_mtbr_bg_dl

Downlink MTBR for Background Traffic Class.

qos_mtbr_bg_ul

Uplink MTBR for Background Traffic Class.

qsearch_c

SACCH RF Signal Level Threshold.

qsearch_c_initial

Use BCCH RF Signal Level Threshold.

qsearch_i

BCCH RF Signal Level Threshold.

qsearch_p

3G Cell Threshold for Multi-RAT MS.

queueMgtInfo

Queue Length Management Information.

ra_colour

Routing Area Color.

ra_reselect_hyst

Routing Area Reselect Hysteresis.

rac

Routing Area Code.

rach_load_period

Random Access Channel Load Period.

rach_load_thresh

Random Access Channel Load Threshold.

radioLinkTimeout

Radio Link Timeout.

rapid_pwr_down

Rapid Power Down Procedure.

ReconfigFrToHr

Reconfigure Full Rate to Half Rate.

reestablishAllwd

Call Re-Establishment.

repResTchFHighWm

Report Resource TCH Full High Water Mark.

repResTchFLowWm

Report Resource TCH Full Low Water Mark.

res_gprs_pdchs

Reserved GPRS PDCH timeslots.

res_less_one_cr

Reserved PDCHs When One Carrier Goes OOS.

retry_cand_period

Retry Candidate Period Timer.

rf_chan_rel_ack

RF Channel Release Acknowledgment Timer.

rpd_offset

Rapid Power Down Offset.

rpd_period

Rapid Power Down Period.

rpd_trigger

Rapid Power Down Trigger.

rpt_bad_qual_mr

Rpt Bad Quality on a Missing Rpt.

rr_ny1_rep

RR_NY1_REP Timer.

rr_t3101

RR_T3101 Timer.

rr_t3103

RR_T3103 Timer.

rr_t3105

RR_T3105 Timer.

rr_t3109

RR_T3109 Timer.
Continued

68P02901W17-T

12-65
Jan 2010

Cell parameters

Chapter 12: CellXchange

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

rr_t3111_sd

RR_T3111_SD Timer.

rr_t3111_tch

RR_T3111_TCH Timer.

rr_t3212

RR_T3212 Timer.

rxlev_access_min

Min Received Signal Level For Access.

rxlev_dl_zone

Inner Zone DownLink Receive Level Threshold.

rxlev_min_def

Minimum Receive Level Default.

rxlev_ul_zone

Inner Zone UpLink Receive Level Threshold.

sdcch_ho

SDCCH Handover Allowed.

sdcch_timer_ho

SDCCH Timer Handover.

sdcchNeedHighWm

SDCCH Need High Water Mark.

sdcchNeedLowWm

SDCCH Need Low Water Mark.

search_prio_3g

Allow Search for 3G Cells.

second_freq_type

Secondary Frequency Type.

servBandReporting

Number of Serving Band cells to report.

stop_dri_tx_time

Time From Cell-Outage to RF Termination (seconds).

switch_gprs_pdchs

Switchable GPRS PDCHs timeslots.

sw_less_one_cr

Switchable PDCHs When One carrier Goes OOS.

t_avg_t

C Averaging in Transfer Mode.

t_avg_w

C Averaging in Wait State.

tch_congprev_thr

TCH Congest Prevent Threshold.

tch_flow_control

Traffic Channel Flow Control.

tch_usage_thrsld

TCH Usage Threshold.

tchFullNeedLowWm

Traffic Channel Full Need Low Water Mark.

tdd_qoffset

Receive Signal Code Power Threshold for

TD-SCDMA neighbor.

temporary_offset

Temporary Offset.

threshold

Threshold.

timingAdvPeriod

Timing Advance Period.

ts_in_usf_active

Max Number of TS In Pre-load USF Active State.

tx_integer

No of RACH Slots Between Access Retries.

tx_power_cap

Cell Transmit Power.

u_rxlev_dl_ih

Upper DL Receive Interfer Level (HandOver).

u_rxlev_dl_p

Upper Downlink Receive Level (Pwr).

u_rxlev_ul_ih

Upper Uplink Receive Interfere Level (HandOver).

Continued

12-66

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Neighbor parameters

Table 12-9 User selectable cell parameters (Continued)

Description

OMC-R Parameter Name

u_rxlev_ul_p

Upper Uplink Signal Level (Pwr).

u_rxqual_dl_p

Upper Downlink Signal Quality (Pwr).

u_rxqual_ul_p

Upper Uplink Signal Quality (Pwr).

ulRxlevHoAllowed

Uplink Receive Level Handover.

ulRxqualHoAllowed

Uplink Receive Quality Handover.

update_c

Update C.

umtsBandPreferred

UMTS Band Preferred.

umtsCpichEcNoMin

Threshold when FDD_REP_QUANT is Ec/No.

umtsCpichRscpMin

Threshold when FDD_REP_QUANT is RSCP

use_bcch_for_gprs

Use BCCH Carrier for GPRS.

use_drv_ho_pwr

BSS Derive HO Power.

useNeiPbgtHreqave

Use Neighbor Power Budget Hreqave.

validCandPeriod

Valid Candidate Period Timer.

waitIndicParams

Wait Indication Parameters.

worse_nei_ho

HandOver to Nbr with Lower RxLev.

zone_ho_hyst

Inner Zone Handover Hysteresis.

User selectable cell parameters with GSM Half Rate unrestricted

Table 12-10 lists the cell parameters, and their GUI field names, that can be selected by a user
for inclusion in the cell export/import file if the Half Rate feature is unrestricted.

Table 12-10 User selectable cell parameters with GSM Half Rate unrestricted
OMC-R Parameter Name

Description

gsm_half_rate_enabled

GSM Half Rate Enabled.

Neighbor parameters
Table 12-11 and Table 12-12 show the neighbor parameters that can be exported/imported.
Table 12-11 shows the neighbor parameters that will be exported/imported by default when
neighbor parameter export is specified. Table 12-12 shows a list of the neighbor parameters
from which the user can select the parameters to be exported/imported, see Defining
CellXchange parameters from the GUI on page 12-28 for further details.

68P02901W17-T

12-67
Jan 2010

Neighbor parameters

Chapter 12: CellXchange

Default RF Neighbor parameters

Table 12-11 shows the GUI field names of the parameters that are exported or imported for
neighbor cells if the default settings are used.

Table 12-11 RFPlanNeighbor default parameters

Field

Description

MSC Name

Specifies the MSC name which is responsible for the cell.

OMC Name

Specifies the OMC-R name which is responsible for the cell.

BSS Name

Specifies the BSS name to which the cell belongs.

Site Name

Specifies the site name within the BSS.

Source MCC

Specifies the Mobile Country Code for the Source Cell of the neighbor
relation.

Source MNC

Specifies the Mobile Network Code for the Source Cell of the neighbor
relation.

Source LAC

Specifies the Location Area Code for the Source Cell of the neighbor
relation.

Source CI

Specifies the Cell Id for the Source Cell of the neighbor relation.

Dest MCC

Specifies the Mobile Country Code for the cell which is the neighbor in
the neighbor relation.

Dest MNC

Specifies the Mobile Network Code for the cell which is the neighbor in
the neighbor relation.

Dest LAC

Specifies the Location Area Code which is the neighbor in the neighbor
relation.

Dest CI
Dest BCCH
ARFCN
Dest BSIC

Specifies the Cell Id of the cell which is the neighbor in the neighbor
relation.
Specifies the BCCH frequency of the neighbor cell.
Specifies the BSIC of the neighbor cell.

User selectable Neighbor parameters

Table 12-12 lists the neighbor parameters, and their GUI field names, that can be selected by a
user for inclusion in the neighbor export/import file.

12-68

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Table 12-12

Neighbor parameters

User selectable Neighbor parameters

Parameter

Description

adap_trg_pbgt_nbr

Neighbor Adap Pbgt HO Trigger

adj_chn_intf_tst

Adjacent Channel Interference Test

adj_chn_rxlev_dif

Adjacent Channel Receive Level Difference

ba_type

BA Type

bs_fdd_arfcn

Blind Search FDD ARFCN

congest_ho_margin

Congestion Handover Margin

dr_allowed

Directed Retry Allowed

frequency_type

Frequency Type of Neighbor

ho_margin_cell

Handover Margin Cell

ho_margin_rxlev

Rxlev Handover Margin

ho_margin_rxqual

Rxqual Handover Margin

ho_margin_type5

Type 5 HO Margin

inner_zone_thresh

Inner Zone Threshold

inner_zone_margin

Inner Zone Margin

interfering_nei

Interfering Neighbor

ms_txpwr_max_cell

Mobile Station Maximum Transmit Power

neighbouringRange

Neighboring Range

noReciprocal

Reciprocate Neighbor

pbgt_alg_data0

Power Budget Algorithm Data 0

pbgt_alg_data1

Power Budget Algorithm Data 1

pbgt_alg_data2

Power Budget Algorithm Data 2

pbgt_alg_type

Power Budget Algorithm Type

pbgtSrcellHreqave

Power Budget Surround Cell Hreqave

rxlev_min_cell

Minimum Cell Receive Level

tdd_arfcn

TD-SCDMA ARFCN

tdd_cell_param

TD-SCDMA Cell Parameter

tdd_tstd_mode

TD-SCDMA Time Switched Transmit Diversity Mode

tdd_sctd_mode

TD-SCDMA Space Code Transmit Diversity Mode

umts_ba_type

UMTS BA Type

umts_meas_margin

UMTS Measurement Margin

umtsNcellAvgPrd

Averaging Period

68P02901W17-T

12-69
Jan 2010

Site parameters

Chapter 12: CellXchange

Site parameters
Table 12-13 shows the site parameters that will be exported or imported by default, if site
parameter import/export is specified. If only a subset of these parameters is required in
the import/export file, use the Radio Frequency Import/Export configuration form to specify
which site parameters are to be included in the import/export file, see Defining CellXchange
parameters from the GUI on page 12-28 for further details.
The column headings for the Site import/export parameter file are:

MSC Name.

OMC Name

BSS Name.

Site Number.

Configurable.

NOTE
The lcf_id parameter can only be changed on its own using rf_import.

Table 12-13 Site parameters

Parameter

Description

add_access_class

Add Access Class Timer

asym_edge_enabled

Asymmetric EDGE Enabled

bcch_info

TM BCCH Information Timer

ber_loss_daily

MSI Bit Error Rate Daily Alarm Level

ber_loss_hourly

MSI Bit Error Rate Hourly Alarm Level

bsp_lcf_type

BSP/LCF Flag

bssmap_t10

BSSMAP_T10 Timer

bssmap_t11

BSSMAP_T11 Timer

bssmap_t14

BSSMAP_T14 Timer

bssmap_t8

BSSMAP_T8 Timer

bts_audit

BTS Audit Timer

bts_type

BTS Configuration Type

btsAuditResponse

BTS Audit Response Timer

Calibrate_flag

Calibrate Enabled

carrierDisableTm

Carrier Disable Time

carrierFreeImmed

Carrier Free Immediately Timer

carriersInsPwrFl

Carriers Ins Power Fail

Continued

12-70

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Site parameters

Table 12-13 Site parameters (Continued)

Parameter

Description

cbch_1

CBCH 1 Timer

cbch_2

CBCH 2 Timer

cbch_3

CBCH 3 Timer

cbs_outage_cntr

CBC to CBS Outage Counter

channel_act

TM Channel Activate Timer

channel_teardown

Channel Teardown Timer

cipher_comp_ms

Cipher Mode Complete from a MS Timer

clkSrcFailResPer

Clock Source Fail Reset Period

Configtypelastcal

Configuration used on last Calibrate

csfp_alg

CSFP Algorithm

csfp_flow

CSFP Flow Value

dlSyncTimer

Downlink Sync Timer (msec)

emerg_reserved

Emergency Reserved Timer

fm_site_type

Site Type

gclk_qwarm_flag

Fast GCLK Warm Up Flag

gproc_slots

GPROC Timeslots

guiLabel

Map label

guiState

Service State

hdsl_losw_oos

MSI Loss of Sync Word OOS Time

hdsl_losw_restore

MSI Loss of Sync Word Restore Time

hdsl_snr_daily

MSI SNR Daily Alarm Level (in 0.5 dB units)

hdsl_snr_daly_prd

MSI SNR Daily Alarm Monitor Period

hdsl_snr_hourly

MSI SNR Hourly Alarm Level (in 0.5 dB units)

hdsl_snr_hrly_prd

MSI SNR Hourly Alarm Monitor Period

hdsl_snr_oos

MSI SNR OOS Threshold (in 0.5 dB units)

hdsl_snr_restore

MSI SNR Restore Threshold (in 0.5 dB units)

ho_complete

Handover Complete Timer

initSyncTimer

Initial Sync Timer (msec)

latitude

Latitude

lcf_id

LCF managing this site

longitude

Longitude

lta_alarm_range

LTA Alarm Range

mms_config_type

MMS Configuration Type

mode_modify

TM Mode Modify Timer

Continued

68P02901W17-T

12-71
Jan 2010

Site parameters

Chapter 12: CellXchange

Table 12-13 Site parameters (Continued)

Parameter

Description

modeRRModifyAc

Mode Modify Acknowledgment Timer

ms_sapi3_est

MS SAPI3 Establishment Timer

name

Name

num_audit_retries

Number Of Audit Retries

per_site_counter

(not displayed in OMC-R GUI)

percent_traf_cs

Percentage of RSL Reserved for CS

phase_lock_gclk

Phase Lock GCLK

phase_lock_retry

Phase Lock Retry Interval

poorInitialAssign

Poor Initial Assignment

rach_load_type

RACH Load Type

red_loss_daily

MSI Red Loss Daily Alarm Level

red_loss_hourly

MSI Red Loss Hourly Alarm Level

red_loss_oos

MSI Red Loss OOS Alarm Level

red_loss_restore

MSI Red Loss Restoral Time

red_time_oos

MSI Red Time OOS Alarm Level

red_time_restore

MSI Red Time Restoral Time

register_exp

Register Exp Timer

remote_loss_daily

MSI Remote Loss Daily Alarm Level

remote_loss_oos

MSI Remote Loss OOS Alarm Level

remote_time_oos

MSI Remote Time OOS Alarm Level

remoteLossHourly

MSI Remote Loss Hourly Alarm Level

remoteLossRestore

MSI Red Time Restoral Time

remoteTimeRestore

MSI Remote Time Restoral Time

rf_res_ind_period

RF Resource Indication Period

rsl_rate

RSL Rate

sacch_info

TM SACCH Information Timer

siteDbLevelNum

Site DB Level Number

siteGeneration

Site Generation

slip_loss_daily

MSI Frame Slip Daily Alarm Level

slip_loss_hourly

MSI Frame Slip Hourly Alarm Level

slip_loss_oos

MSI Frame Slip OOS Alarm Level

slip_loss_restore

MSI Frame Slip Restoral Time

sms_dl_allowed

SMS Downlink Allowed

sms_tch_chan

SMS TCH Channel

Continued

12-72

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DRI/RTF parameters

Table 12-13 Site parameters (Continued)

Parameter

Description

sms_ul_allowed

SMS Uplink Allowed

static_sync_timer

Static Sync Timer

sync_loss_daily

MSI Sync Loss Daily Alarm Level

sync_loss_hourly

MSI Sync Loss Hourly Alarm Level

sync_loss_oos

MSI Sync Loss OOS Alarm Level

sync_loss_restore

MSI Sync Loss Restoral Time

sync_time_oos

MSI Sync Loss Time OOS Alarm Level

sync_time_restore

MSI Sync Loss Restoral Time

tchBusyCrtThrshd

TCH Busy Critical Threshold

tchBusyNrmThrshd

TCH Busy Norm Threshold

ts_alloc_flag

Timeslot Allocation Flag

ts_sharing

Timeslot Sharing

ulSyncTimer

Uplink Sync Timer (msec)

waitForReselect

Wait For Reselection

DRI/RTF parameters
Table 12-14 and Table 12-15 show the DRI and RTF parameters that will be exported or imported
by default, if DRI/RTF parameter import/export is specified. If only a subset of these parameters
is required in the import/export file, use the Radio Frequency Import/Export configuration form
to specify which DRI/RTF parameters are to be included in the import/export file, see Defining
CellXchange parameters from the GUI on page 12-28 for further details.
Both DRI and RTF parameters are included in the DRI/RTF export/import file. DRI header
information appears first, followed by the DRI parameters, then the RTF header information,
followed by the RTF parameters.

NOTE
Some RTF information appears in the cell import/export file, such as frequency
hopping and ARFCN parameters. If the user chooses not to export a DRI/RTF file, the
RTF information remains in the cell export/import file. However, if the user chooses
to export a DRI/RTF file, the RTF information is included in the DRI/RTF files instead
of in the cell file.

DRI parameters
The column headings for the DRI section of the DRI/RTF import/export parameter file are:

MSC Name.

OMC Name

68P02901W17-T

12-73
Jan 2010

DRI/RTF parameters

Chapter 12: CellXchange

BSS Name.

Cell ID.

DRI Group Number.

DRI Number.

Configurable (that is, any other additional parameters specified in the Configuration file,
RF.CNFG)

Table 12-14 DRI parameters

Parameter

Description

assoc_dri_id

RDN of Associated DRI (if applicable).

assoc_fr_unit

Associated FRU.

associated_mms

Associated MMS.

assocKitNumber

Associated FRU Kit Number.

assocSerialNumber

Associated FRU Serial Number.

cabinet_id

Cabinet Identifier.

cageId

Cage Identifier.

cell1_gsmCellId

Cell 1 GSM Cell Identifier.

cell1AntennaSelct

Cell 1 Antenna Select.

combiner_1_cav_id

Combiner 1 Cavity Identifier.

combiner_1_id

Combiner 1 Identifier.

combining_type

Combining Type.

diversityFlag

Diversity Flag.

dri_density

DRI Density (if applicable).

DRI_type

DRI Type.

{34371G} first_dev_type

First Component.

{34371G} first_dev_id

First Component Device Id1.

{34371G} first_dev_dri_id

First Component Device Id2.

{34371G} first_dev_port

First Component Port

fm_cell_type

Cell Type.

foxFmuxConn

Connection to BTP.

FR_unit

Field Replaceable Unit (FRU).

{34371G} ingress_1_port

First Ingress SFP Port.

{34371G} ingress_2_port

Second Ingress SFP Port.

kitNumber

Kit Number.

{34371G} lowest_arfcn

ARFCN number.
Continued

12-74

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DRI/RTF parameters

Table 12-14 DRI parameters (Continued)

Parameter

Description

opto_alarm_index

Alarm Index.

opto_reporting

Alarm Reporting.

opto_state

No alarm state for the optocoupler.

pdb_fr_unit

PDB Field Replaceable Unit.

pdbKitNumber

PDB FRU Kit Number.

pdbSerialNumber

PDB FRU Serial Number.

port_connection

Port Connection.

pref_rtf_group_id

Preferred RTF Group Id.

pref_rtf_id

Preferred RTF Id.

{34371G}
second_dev_type

Second Component.

{34371G} second_dev_id

Second Component Device Id1.

{34371G}
second_dev_port

Second Component Port.

serialNumber

Serial Number.

slot_id

Slot Number.

{34371G} slot_num

Slot Number.

truId

Topcell Radio Unit Identifier.

{34371G}
tx_0_dri_density

DRI density on Tx Port 0.

{34371G}
tx_l_dri_density

DRI density on Tx Port 1.

{34371G} tx_port

Tx port being used by the DRI.

{34371G}
assoc_dri_id1_tx0

DRI id of the first associated DRI of Tx Port 0.

{34371G}
assoc_dri_id2_tx0

DRI id of the second associated DRI of Tx Port 0.

{34371G}
assoc_dri_id3_tx0

DRI id of the third associated DRI of Tx Port 0.

{34371G}
assoc_dri_id1_tx1

DRI id of the first associated DRI of Tx Port 1.

{34371G}
assoc_dri_id2_tx1

DRI id of the second associated DRI of Tx Port 1.

{34371G}
assoc_dri_id3_tx1

DRI id of the third associated DRI of Tx Port 1.

RTF parameters
The column headings for the RTF section of the DRI/RTF import/export parameter file are:

68P02901W17-T

12-75
Jan 2010

DRI/RTF parameters

Chapter 12: CellXchange

MSC Name.

OMC Name

BSS Name.

Cell ID.

RTF Group Number.

RTF Number.

Configurable (that is, any other additional parameters specified in the Configuration file,
RF.CNFG).

Table 12-15 RTF parameters

Parameter

Description

amr_hr_enabled

AMR Half Rate Enabled.

carrier_type

Carrier Type.

carrier1_arfcn

Carrier 1 ARFCN.

carrier1_fhi1

Freq Hopping Ind for TS 0.

carrier1_fhi2

Freq Hopping Ind for TS 1.

carrier1_fhi3

Freq Hopping Ind for TS 2.

carrier1_fhi4

Freq Hopping Ind for TS 3.

carrier1_fhi5

Freq Hopping Ind for TS 4.

carrier1_fhi6

Freq Hopping Ind for TS 5.

carrier1_fhi7

Freq Hopping Ind for TS 6.

carrier1_fhi8

Freq Hopping Ind for TS 7.

carrier1_tsc1

Training Seq Code for TS 0.

carrier1_tsc2

Training Seq Code for TS 1.

carrier1_tsc3

Training Seq Code for TS 2.

carrier1_tsc4

Training Seq Code for TS 3.

carrier1_tsc5

Training Seq Code for TS 4.

carrier1_tsc6

Training Seq Code for TS 5.

carrier1_tsc7

Training Seq Code for TS 6.

carrier1_tsc8

Training Seq Code for TS 7.

carrier1GsmCellId

GSM Cell Id.

cell_zone

Concentric Cell Zone.

chanAllocPriority

Channel Allocation Priority.

ext_timeslots

Extended Range Timeslots.

ksw_pair

KSW Pair.
Continued

12-76

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

DRI/RTF parameters

Table 12-15 RTF parameters (Continued)

Parameter

Description

max_gprs_pdch

Maximum GPRS Data Timeslots.

path1_upst_ts1

First Path Upstream TS MMS.

path1_downst_ts1

First Path Downstream TS MMS.

path2_upst_ts1

Second Path Upstream TS MMS.

path2_downst_ts1

Second Path Downstream TS MMS.

path_id1

First Path Id.

path_id2

Second Path Id.

pkt_radio_type

Packet Radio Type.

res_gprs_pdch

Reserved GPRS Data Timeslots.

rsl_id1

Associated RSL for First Path Id.

rsl_id2

Associated RSL for Second Path Id.

rtf_capacity

RTF Capacity.

rtf_ds0_count

Number of Backhaul Timeslots on Carrier.

sd_load

SDCCH Load.

sd_priority

SDCCH Placement Priority.

trx_pwr_red

Transmit Power Reduction.

68P02901W17-T
Jan 2010

12-77

DRI/RTF parameters

12-78

Chapter 12: CellXchange

68P02901W17-T
Jan 2010

Chapter

13
Manipulating Maps

The information here describes the facilities available to manipulate background geographical
maps. The following topics are described:

Adding and deleting a user-defined regional map on page 13-2.

Adding and changing a background to a map on page 13-4.

Adding and deleting a map node on page 13-6.

Adding and deleting a map link on page 13-11.

68P02901W17-T
Jan 2010

13-1

Adding and deleting a user-defined regional map

Chapter 13: Manipulating Maps

Adding and deleting a user-defined regional map

Procedures for adding and deleting user-defined regional maps

This section describes the procedures to add a user-defined regional map to the OMC-R, and
delete it, using the following:

OMC-R GUI Navigation Tree.

cmutil.

Adding a map using the OMC-R GUI

To add a user-defined regional map using the OMC-R GUI, use the following procedure:

Procedure 13-1 Add a map

1

From the Front Panel, select the maps icon to display a Map List
window.

Select Edit Create from the menu bar to display a blank Map
Detailed View form.

Assign Map Background attribute to the required default map.

NOTE
The associated .map file should exist in
/usr/omc/config/global/maps.
4

Enter the other required attributes and select File Create to add
the map to the Map List.

Double click this map from the Map List to display the map.

To create map nodes and map links for this map, refer to these
procedures:

Adding and deleting a map node on page 13-6.

Adding and deleting a map link on page 13-11.

Adding a map using cmutil

To add a new map using cmutil, see Chapter 15 cmutil.

13-2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a map using the OMC-R GUI

Deleting a map using the OMC-R GUI

To delete a user-defined map use the following procedure:

Procedure 13-2

Delete a map

From the Front Panel, select the Network icon to display a Map List
window.

Click the name of the user-defined map to be deleted. The name is

highlighted.

NOTE
Default maps cannot be deleted. Maps can only be deleted
using this procedure if they do not contain any objects.
3

Select Edit Delete from the menu bar. A delete confirmation box
is displayed.

Click OK to confirm.
Result: The following message is displayed in the status bar: Element
Deleted

Deleting a map using cmutil

To remove a map from the MIB database using cmutil, see Chapter 15 cmutil.

Storing updated map data using cmutil

When a map has been modified, store a copy of it using cmutil, see Chapter 15 cmutil.

68P02901W17-T

13-3
Jan 2010

Adding and changing a background to a map

Chapter 13: Manipulating Maps

Adding and changing a background to a map

Overview of adding or changing a map background

It is possible to change the background, or add a geographical background to a network map
using the OMC-R GUI or cmutil (see Chapter 15 cmutil for further details of cmutil).
Adding a geographical background to a network map using the OMC-R GUI is a two stage
process:
1.

Installing the map background file.

2.

Selecting and displaying the geographical map background.

These stages are explained as follows.

Obtaining a geographical map background

Your Local Office can advise you on where to obtain a geographical map background.

Installing a map background file

To install a map background file on the OMC-R, load the file from the System Processor tape
drive using the following procedure:

Procedure 13-3 Install a map background file

1

At the System Processor, log in as omcadmin.

Open a shell and change to the directory containing the map

background files:
cd $OMC_TOP/config/global/maps

Load the tape containing the map background file into the System
Processor tape drive, then load the map background file:
tar -xvfop /dev/rst0
where /dev/rst0 is the default tape drive.

List the contents of the current directory:

ls -lai
Continued

13-4

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Selecting and displaying the geographical map background

Procedure 13-3 Install a map background file (Continued)

5

Verify that the map background file has been loaded into the directory,
and that the file is owned by the user omcadmin. All files in this
directory should have a .map extension. If any files do not have the
.map extension, use the command shown in the following example to
add the extension:
mv MAP_<name> MAP__<name>.map

Use the following command to change the permissions on the files in

this directory so that all users have execute permission:
chmod a+x *

Log out from the System Processor.

Selecting and displaying the geographical map background

To select and display the geographical map background, follow these steps:

Procedure 13-4 Select and display the geographical map background

1

From the OMC-R Front Panel, select the Maps icon to open a Map
List window.
Result: This window displays a list of maps. The list includes
automatically generated and user-defined maps.

Double-click a map name to view a map and its current background.

Select File Close to close the map.

Click a map name from the Map List window, then select Edit Detail
View from the menu bar.
Result: The Map Detailed View form is displayed showing the Name,
Map Label, and Map Background fields.

Select Edit Edit from the menu bar.

Click the Map Background field and select the desired map.

NOTE
The name must match an existing file in
/usr/omc/config/global/maps in order to be valid.
Add the file name without the file extension name.
If necessary, open an Xterm window to check the contents
of /usr/omc/config/global/maps to check if the map
background file exists in this directory.
7

Select File Save from the menu bar to save the new configuration.

Select File Close from the menu bar.

Result: The Detailed View window closes.

68P02901W17-T

Double-click the map name to open the map and view the new
background.

13-5
Jan 2010

Adding and deleting a map node

Chapter 13: Manipulating Maps

Adding and deleting a map node

Adding a map node

NEs are represented on maps as map nodes. To add a node to a map, or to represent a NE
on a map, carry out the following procedure:

Procedure 13-5 Add a map node

1

From the Front Panel, select the Maps icon to display a Map List
window.

Highlight the required map from the list and then select File Open
from the menu bar, or double-click a map name to display a map. The
Map window is displayed.

Select Edit Map Node Create from the Map window menu bar.
Result: The MapNode Detailed View window is displayed.

Complete the X Co-ordinate and Y Co-ordinate fields of the node.

NOTE
These fields can be left blank and the map nodes positioned
after they have been created. Refer to: OMC-R Online Help,
Network Operations.
5

Click the Source Node button.

Result: The Navigation Tree is displayed.

In the Navigation Tree, navigate to and double-click the network

element instance button to be added to the map.
Result: The MapNode Detailed View window is redisplayed.

NOTE
If any class of element other than an instance button is
selected, a message is displayed in the status bar at the
bottom of the Navigation Tree:
Choose an instance button
Continued

13-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adding NEs and links to a map

Procedure 13-5 Add a map node (Continued)

7

Select File Create from the menu bar.

Result: The message Create Complete is displayed in the message
area at the bottom of the screen.

NOTE
A message Create Failed is displayed at the bottom of the
Detailed View window if the network element already exists
on the map. In this case, select File Close from the menu
bar, and begin the procedure again.
8

Select File Close from the menu bar to close the Map Node Detailed
view.

Adding NEs and links to a map

To add NEs and links to a map, follow these steps:

Procedure 13-6 Add NEs and links to a map

1

Log in as omcadmin at the System Processor.

Open a shell and change to the directory containing the temporary

work files:
cd $OMC_TOP/config/local/cm_mib_db/temp_files

To add NE and Link data, first use an editor to create a criteria file
containing the definition of the MapNodes and MapLinks to be added,
as shown below:
MapNode
{
source = NE_type:<MapNode_name>,
container = Map:<Map_name>
}
MapLink
{
source = CommsLink:<Link_name>,
container = Map:<Map_<name>
}
where <MapNode> and
<MapLink>
are the types of data to be added and
<MapNode_name> and
<Link_name>
are the names of the types of data to be added.
Continued

68P02901W17-T

13-7
Jan 2010

Deleting a map node

Chapter 13: Manipulating Maps

Procedure 13-6 Add NEs and links to a map (Continued)

4

Save the criteria file and exit the editor.

Before adding the new MapNodes and MapLinks to the MIB database,
the file must be checked for syntax. Use the following cmutil command
to check the file syntax:
cmutil -s -i criteria

NOTE
If the file syntax check cannot be completed, error messages
are displayed.
6

Once the criteria file has been checked for correct syntax, add it to
the MIB:
cmutil -a -i criteria

Store the updated map data using the procedure described previously.

Log out from the System Processor.

For further information about cmutil, see Chapter 15 cmutil.

Deleting a map node

Map nodes can be deleted independently of the associated NE. Deleting an NE however,
automatically deletes all map nodes associated with it.
To delete a map node on a user-defined map, carry out the following procedure:

Procedure 13-7
1

Delete a map node

From the Front Panel, select the network icon to display the Map List
window.
Result: This window displays a list of map names.

Double-click a map name to display a map.

Select the map node to be deleted.

Result: The map node changes color.

Select Edit Map Node Delete.

Result: A confirmation box is displayed with the message: Delete
this Object?

Click OK.
Result: The map node is now deleted.

13-8

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Removing NEs and links from a map

Removing NEs and links from a map

Use the following procedures to remove NEs and Links from a map:

Procedure 13-8 Remove NEs and links from a map

1

Log in as omcadmin at the System Processor.

Open a shell and change to the directory containing the temporary

work files:
cd $OMC_TOP/config/local/cm_mib_db/temp_files

To delete NE and Link data, first use an editor to create a criteria file
containing the definition of the MapNodes and MapLinks to be deleted,
as shown in the following example:
MapNode
{
source = NE_type:<MapNode_name>,
container = Map:<Map_name>
}
MapLink
{
source = CommsLink: <Link_name>
container = Map:<Map_name>
}
where <MapNode> and
<MapLink>
are the types of data to be deleted,
<MapNode_name> and
<Link_name>
are the names of the types of data to be deleted and
<NE_type> is one of the following:
NETWORK
MSC
BSS
RXCDR
OMC
SITE

NOTE

If a MapNode is deleted then its attached Maplinks

(any links coming from that node) are automatically
removed.

There is no hierarchical structure for MapNodes,

that is, if a MapNode for a BSS is deleted then the
MapNodes for sites contained within that BSS are not
removed for the specific map.

Save the criteria file and exit the editor.

Continued

68P02901W17-T

13-9
Jan 2010

Removing NEs and links from a map

Chapter 13: Manipulating Maps

Procedure 13-8 Remove NEs and links from a map (Continued)

5

Delete the NE and Link data using cmutil:

cmutil -d -i criteria

Store the updated map data using the procedure described previously.

Log out from the System Processor.

For further information about cmutil, see Chapter 15 cmutil.

13-10

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adding and deleting a map link

Adding and deleting a map link

Introduction to adding a CommsLink

A map link is a CommsLink between two NEs represented on a map.

Adding a map link using the OMC-R GUI

NOTE
Adding a map link is only possible on customized maps, that is, maps which have been
user-created and not those normally populated by an audit.
To add a link between two nodes on a map, carry out the following procedure:

Procedure 13-9 Add a map link

1

From the Front Panel, select the Maps icon to open a Map List window.

Select File Open from the menu bar, or double-click a map name
to open a map.

Select Edit Map Link Create from the menu bar.

Result: The MapLink Detailed View window opens.

Click the Source CommsLink button.

Result: The CommsLink list opens (see Figure 5-1 for an example).

Click the Node A button.

Result: The Navigation Tree opens.

In the Navigation Tree, double-click an instance button of the

CommsLink element to be added to the map.

Double-click the required CommsLink in the list.

Result: The CommsLink list is redisplayed.

Click the Node B: button.

Result: The Navigation Tree window is displayed.
Continued

68P02901W17-T

13-11
Jan 2010

Adding map links using cmutil

Chapter 13: Manipulating Maps

Procedure 13-9 Add a map link (Continued)

9

Repeat Step 6 for the node at the other end of the CommsLink.

10

Click the Apply Filter button.

11

Double-click the required CommsLink in the list.

NOTE
If no CommsLink is shown on the list, select the Node A
button to open the Navigation Tree window and add a
CommsLink as described earlier.
12

Select File Create on the Map Link Detailed View.

13

Select File Close to close the detailed view.

Result: The map link is now created and can be seen on the map.

Adding map links using cmutil

To add map links to existing sites using cmutil, see Chapter 15 cmutil.

Deleting a map link using the OMC-R GUI

To delete a map link on a user-defined map carry out the following procedure:

Procedure 13-10
1

Delete a map link

From the Front Panel, select the network icon to display the Map List
window.
Result: This window displays a list of map names.

Double-click a map name to display a map.

Select the map link to be deleted.

Result: The map link changes color (the default color is purple).

Select Edit, and then select Map Link Detailed View from the dropdown
menu.
Result: The Map Link Detailed View window is displayed.

Select Edit Edit from the menu at the top of the window.

Select File Delete from the menu.

Result: A confirmation box is displayed with the message: Delete
this Object?

Click OK in the confirmation box.

Result: The map link is now deleted.

13-12

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting map links using cmutil

Deleting map links using cmutil

To delete map links from existing sites using cmutil, see Chapter 15 cmutil.

68P02901W17-T
Jan 2010

13-13

Deleting map links using cmutil

13-14

Chapter 13: Manipulating Maps

68P02901W17-T
Jan 2010

Chapter

14
Optimizing the Network

Information about how to optimize a network while located at the OMC-R is described here.

NOTE
Only the optimization of a macrocellular system is described. However, the techniques
used to collect and analyze the data could also be applied to the optimization of a
microcellular system. The same techniques apply to any frequency band, although
there are significant differences in the RF propagation properties. The Intelligent
Optimization Product (IOP) and Intelligent Optimization System (IOS) tools can also
be used to optimize a network.
The following topics are described:

Preparing for optimization on page 14-4.

Checking and changing the current network status on page 14-5.

Collecting information about the current network on page 14-8.

Checking for and rectifying Out Of Service (OOS) devices on page 14-9.

Checking for and rectifying hardware defects on page 14-10.

Checking for and rectifying database errors on page 14-11.

Using call trace to detect problems on page 14-14.

Monitoring network changes on page 14-15.

68P02901W17-T
Jan 2010

14-1

Overview of optimization

Chapter 14: Optimizing the Network

Overview of optimization

Overview of the optimization process

Optimization is the task of improving the call success rate for mobile subscribers.
In a newly deployed network, problems emerge. These problems are due to any or all of the
following:

Set up of the database parameters.

Installation of the equipment.

Orientation of antennas.

There may also be problems with congestion in busy parts of the network.
As a network matures from an initial coverage priority to handling more subscribers, some of
the original cells have to be modified or removed from the network.
The optimization of an entire network with hundreds or thousands of cells is a time-consuming
and slow process. It shows little improvement in overall network quality in the short term.
However, this chapter describes a practical method of optimizing a network by attacking the
worst ten performing cells. Dealing with the worst ten cells in each optimization exercise,
slowly resolves the problems and raises the overall quality of service available to subscribers.
As the network expands each new cell integrated into the network is automatically assessed
along with all the original cells.
The overall performance of a network which has had little or no upgrading can also be improved
by implementing newer features or operating practices.

Stages in an optimization exercise

The optimization process can be divided into the following stages:

Preparing for an optimization exercise from the OMC-R.

This involves reviewing network administration procedures and feature implementation to
determine where areas can be modified to increase efficiency and unnecessary diagnostic
effort. See Preparing for optimization on page 14-4 in this chapter for further details.

14-2

Checking, collecting, and researching network information from the OMC-R. See sections
in this chapter for further details.

Analyzing, diagnosing, and rectifying network problem areas from the OMC-R. See
sections in this chapter for further details.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Stages in an optimization exercise

Drive testing, if required.

When necessary, drive testing is often a significant stage in optimizing a network. It
involves driving around an area testing signal strengths and call handling. Drive testing
is described in detail in the manual: Installation and Configuration: BSS Optimization
(68P02901W43). Drive testing is labor intensive and slow. Drive test teams cannot cover
cells that are geographically widely separated. Instead, statistical analysis of the network
from the OMC-R can be quicker, but in other circumstances drive testing may still be
necessary.

68P02901W17-T

Analyzing and resolving any outstanding problem cells using actual data, logs, and tick
sheets collected during the drive tests, see manual Installation and Configuration: BSS
Optimization (68P02901W43) for further details.

14-3
Jan 2010

Preparing for optimization

Chapter 14: Optimizing the Network

Preparing for optimization

Collecting information
Before starting an optimization process, collect all the required information. It becomes easy
to analyze data.

Learning from past experiences

The performance of some networks can be improved by incorporating knowledge and experience
gained from optimizing other networks. Sharing lessons learnt can resolve many issues before
they occur and avoid duplicating effort.
Collect as much optimization knowledge and experience as possible, before beginning an
optimization exercise.

Prerequisites
Before attempting to optimize a GSM network, install sites and ensure all are in-service.
For example, Call Success Monitor can be used to detect sleeping devices, see OMC-R Online
Help, Network Operations for further details.

14-4

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking and changing the current network status

Checking and changing the current network status

Checking and changing network status

After preparing for the optimization, the next stage is to check the current network status, and
change some settings according to the information provided in this section.
This involves:

Enabling, disabling, and setting key features.

Performing sanity checks.

Configuring GPROCs.

Setting network-related parameters.

Setting network-related timers.

Enabling, disabling, and setting key features

The following settings provide a marked improvement in call success and overall network
performance. Some settings may be in use already, but poorly configured. These setting are
recommendations only, they are not mandatory and their omission does not significantly affect
the optimization process itself.

Ensure RxLev handovers are disabled across the network.

Ensure RxQual handovers are enabled and parameters are optimized across the network.

Ensure that the Uplink Power Control feature is enabled across the network.

Ensure that the Downlink DTX feature is enabled across the network.

Ensure Downlink DTX and VAD is enabled at the transcoder.

Ensure that the Fast MS Power Down feature is enabled across the network.

Ensure that the Congestion Relief or Directed Retry features are enabled.

Ensure that the Congestion Relief feature is enabled with zero margin triggering at 90%.

68P02901W17-T

14-5
Jan 2010

Performing sanity checks

Chapter 14: Optimizing the Network

Performing sanity checks

Perform the following sanity checks:

Check location area dimensioning, keeping multiple boundaries to a minimum. This

increases the call setup success rate and reduces SDCCH blocking.
Each location area should have similar paging loads.
Reduce the size of a location area with a high paging load to relieve SDCCH blocking.
Increase the size of a location area with a low paging load to reduce the overall
number of location areas.
Refer to manual Maintenance Information: GSM Statistics Application
(68P02901W56) for further information on paging load.

Perform a frequency plan sanity check to reduce probable interference issues.

Check all cell BCCH frequencies against the hopping and non-hopping lists. It is
recommended that BCCH carrier/frequencies are not utilized for hopping purposes.

Ensure that paging is done by location area as opposed to Paging by cell id. This reduces
MTL blocking and avoids paging overload due to cell identity database mismatches.

Configuring GPROCs
Configure the GPROCs with the following settings:

Maintain the mean value of BSS statistic CPU_USAGE at or below 70% for all GPROCs.
If high, investigate the DRI distribution across GPROCs to reallocate the load, or replace
the GPROCs with GPROC2s (and/or GPROC3s).

Ensure GPROCs are configured to reflect:

Excessive carriers per LCF are not equipped.
Single GPROC LCP can control up to eight BTSs (15 RSLs).
Single GPROC2 LCP can control up to 15 BTSs (31 RSLs) (provided all GPROCs at the
BSC are GPROC2s and/or GPROC3s).
Ensure MTLs and RSLs are not equipped on the same LCF.
LCPs should not be configured to support BTSs and MTLs.
A BTP should have a maximum of one DRI assigned to it.
A DHP should have a maximum of two DRIs assigned to it.

14-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Setting network-related parameters

Setting network-related parameters

Set the following network-related parameters:

Ensure path balance is correct across the network.

Ensure that handover margins are optimized, that is, 4 dB for adjacent frequencies, 6 dB
for cells without adjacent frequencies across the network.

Set the parameter assign_successful to 15000 across the network.

Set the parameter ho_successful to 15000 across the network.

Set the parameter extended_paging_active to 1 across the network.

Set the parameter interfer_bands for band 4 to 63 across the network.

Set the parameter link_fail to 3.

Set the parameter radio_link_timeout to 3, and set timer rr_t3109 to 8000.

Set the parameter link_about_to_fail to 2 across the network.

The manual Technical Description: BSS Command Reference (68P02901W23) describes BSS
parameters in detail.

Setting network-related timers

Set the following network-related timers:

Set the timer rr_t3103 to 15000 across the network.

Set the timers rr_t3111_tch and rr_t3111_sd to 1200 ms across the network.

Set the timer rr_t3212 to be the same as the MSC database implicit detach timer and it
should be similar across all cells within the network.

The manual Maintenance Information: BSS Timers (68P02901W58) describes BSS timers
in more detail.

68P02901W17-T

14-7
Jan 2010

Collecting information about the current network

Chapter 14: Optimizing the Network

Collecting information about the current network

Collecting statistics
Collect the following statistics to diagnose network health symptoms:

Worst ten cells for handover failure.

Worst ten cells for call failure due to drop.

Worst ten cells for call failure due to call set-up.

Worst ten cells for poor quality of service (QOS).

Worst ten cells for blocking.

The mean value for BSS statistic CPU_USAGE for all GPROCs.

OMC-R Online Help, Network Operations describes how to create reports to show this
information.

Collecting customer complaints and issues

To assist in diagnosing quality affecting issues, collect complaints of poorly performing cells.
The Customer Services Department is a good source for this information. For example, find
out about:

14-8

No audio calls - where, when, and under what conditions they occur.

Noisy calls - where, when, and under what conditions they occur.

Areas of patchy or no service.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking for and rectifying Out Of Service (OOS) devices

Checking for and rectifying Out Of Service (OOS)

devices

Auditing sites
Audit the sites under review to ensure all RF resources are available.

Changing devices to INS

Any out-of-service devices should be put in-service (INS).
If an OOS device comes back into service and cures the problem, monitor the device to ensure it
does not go OOS again. If the device does go OOS again, investigate the cause.
If there are no OOS devices or bringing devices back into service does not clear the problem,
check for hardware defects.

OMC-R Online Help, Network Operations describes fault management activities, such as, OOS
and INS.

68P02901W17-T

14-9
Jan 2010

Checking for and rectifying hardware defects

Chapter 14: Optimizing the Network

Checking for and rectifying hardware defects

Introduction to checking and rectifying hardware defects

Check each site for any hardware defects to ensure that all RF resources are available and
working at their optimum efficiency.

OMC-R Online Help, Network Operations describes fault management activities.

Hardware defect checks

The following checks highlight any areas that would restrict the performance of a cell:

Use call trace to ensure that subscriber calls are being made on all the carriers in the
affected cell.

Use call trace logs for path imbalance to identify any RF hardware integrity issues, that is,
faulty antennas, low gain LNAs, and so on. +20 dBs indicates Rx path failure.

Check the OMC-R alarm and event logs (or ECT) to see if any device is causing problems.
Faulty devices adversely affect the overall network performance. See OMC-R Online Help,
Network Operations for details.

If practical, reset the associated DHP for the site to clear any issues relating to sleeping
cells.

If a site has redundant equipment, swap devices and take the suspect device out of service.
If the fault clears, send field staff to the site for further investigation with a view to
replacing the faulty device.

If the fault did not clear, the problem is probably not a hardware defect.

Rectifying hardware defects

There is no point in attempting to optimize a site which has RF resources unavailable for use.
Therefore, rectify site hardware defects as follows:

14-10

Send field staff to physically replace any faulty hardware at the site.

Monitor the replacement hardware over a period of time to ensure that the fault does not
reappear. If the fault does reoccur, it indicates a cause other than that originally diagnosed.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking for and rectifying database errors

Checking for and rectifying database errors

Introduction to checking for database errors

Checking for database errors involves performing:

Handover failure checks.

Dropped call checks.

Call setup failure checks.

Poor quality call checks.

SDCCH blocking checks.

Other miscellaneous checks.

These checks are described in the following sections.

Further information for BSS parameters and commands

For further details on:

BSS parameters detailed in this section, see the manual Technical Description: BSS
Command Reference (68P02901W23).

BSS timers detailed in this section, see the manual Maintenance Information: BSS Timers
(68P02901W58).

Handover failure checks

For handover failures, check that:

RxLev handovers are disabled.

RxQual handovers are enabled.

Path balance is correct.

Handover margins are optimized. Standard setting is 4 dB for adjacent frequencies and 6
dB for cells without adjacent frequencies.

68P02901W17-T

14-11
Jan 2010

Dropped call checks

Chapter 14: Optimizing the Network

Parameter assign_successful is set to 15000.

Parameter ho_successful is set to 15000.

Timer rr_t3103 is set to 15000.

Neighbor list is correct.

Dropped call checks

For call failure due to drop, check that:

Parameter link_about_to_fail is set to 2.

Uplink power control feature is enabled.

Call setup failure checks

For call failure due to call setup, check that:

Parameter extended_paging is set to 1.

Parameter interfer_bands for band 4 is set to 63.

Poor quality checks

For poor quality of service (QOS), check that:

Downlink DTX feature is enabled for all sites.

Downlink DTX and VAD is enabled at the transcoder.

Fast MS power down feature is enabled.

SDCCH blocking checks

For SDCCH blocking, check that:

14-12

Each location area has similar paging loads.

A location area with a high paging load is increased in size to relieve SDCCH blocking.

Set timers rr_t3111_tch and rr_t3111_sd to 1200 ms across the network.

Timer rr_t3212 is less than the MSC database implicit detach timer and is similar across
all cells.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

TCH Blocking checks

TCH Blocking checks

For TCH blocking:

Check that the congestion relief feature is enabled with zero margin triggering at 90%.

Check that the optimize handover margin is 4 dB for adjacent frequencies and 6 dB for
cells without adjacent frequencies.

Reduce the power budget margin to move traffic to neighboring cells.

Consider reducing antenna height.

Consider increasing antenna tilt to a maximum of 12.

For sites suffering SDCCH and TCH blocking, a cell expansion is required.

Set the timers rr_t3111_tch and rr_t3111_sdto 1200 ms across the network.

Set the parameter link_fail to 3.

Set the parameter radio_link_timeout to 3 and timer rr_t3109 to 8000.

Other miscellaneous checks

The following activities can also be used to rectify a problem:

Cut and paste a database from another cell, which is known to be clear of the same problem.

Reconfigure the cut database to include the correct channel numbers, site ids, neighbors,
and so on.

Monitor for repetition or clearing of the problem.

68P02901W17-T

14-13
Jan 2010

Using call trace to detect problems

Chapter 14: Optimizing the Network

Using call trace to detect problems

Using call trace at the OMC-R

Use the call trace feature at the OMC-R to:

Monitor subscriber RF data for the affected cells to diagnose cell problems.

Optimize the network with respect to subscribers, not drive test teams.

Ensure that subscriber calls are being made on all TCHs in the affected cell and its
neighbors.

Use call trace log files for path imbalance to identify any RF hardware integrity issues, such as,
faulty antennas, low gain LNAs, and so on. +20 dBs indicates Rx path failure.

Using the Call Trace tool (CTP NT)

CTP NT is an advanced cell optimization and diagnostics tool that uses call trace data for
analysis purposes.
BSS equipment has the ability to trace normal subscriber calls and to store that data on the
OMC-R. CTP NT makes use of a collection service to gather Call Trace files and also MIB
configuration data from one or more OMC-Rs. The CTP NT collection service then copies the
gathered data to an SQL database at a CTP NT Server installation. Then the data is available
to one or more connected CTP NT clients.
As well as making use of an automatic collection service, CTP NT also allows Call Trace files
to be manually imported.
Using the call trace database, CTP NT allows:

14-14

Statistical analysis of measurement report data for individual cells or arbitrary groupings
of cells.

Call analysis in which measurement report data and Layer3 messages may be viewed on
a call by call basis.

Filtering of call trace files by any combination of network elements, date range, message
type, call type, and DTX. Filtering can also be applied to MR Distributions reports.

Generation of pre-defined CTP reports which can be run over the Call Trace database.

Exporting of tabular and graphical data to other MS Office applications.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Monitoring network changes

Monitoring network changes

Collecting new statistics

If any changes are made to the network as a result of the checks and activities detailed in the
previous sections, gather new statistics to confirm improved network performance. These
statistics are:

Worst ten cells for handover failure.

Worst ten cells for call failure due to drop.

Worst ten cells for call failure due to call setup.

Worst ten cells for poor quality of service (QOS).

Worst ten cells for blocking.

The mean value for BSS statistic CPU_USAGE for all GPROCs.

If no physical or database changes have not been made, or no performance improvement is

apparent, investigate the cells further using a drive test.

68P02901W17-T
Jan 2010

14-15

Collecting new statistics

14-16

Chapter 14: Optimizing the Network

68P02901W17-T
Jan 2010

Chapter

15
cmutil

cmutil is a powerful and comprehensive utility, which can be used to perform Configuration
Management tasks directly on the CM MIB database. It can be used as an alternative to using
the OMC-R GUI or TTY interface to perform specific configuration tasks. Descriptions are
provided here about how to use cmutil to perform various configuration tasks.
The following sections provide information such as cmutil syntax and rules:

Introduction to cmutil on page 15-2.

cmutil command syntax on page 15-5.

ASCII file content used with cmutil on page 15-7.

ASCII file rules used with cmutil on page 15-10.

Object definition in cmutil ASCII files on page 15-12.

cmutil status messages on page 15-16.

cmutil script files on page 15-17.

The following sections provide information such as adding, deleting, modifying, and extracting
information from the MIB using cmutil:

Using cmutil to add, delete, and modify CM MIB data on page 15-18.

Ways of extracting data from the CM MIB on page 15-24.

Configuring CommsLinks using cmutil on page 15-36.

Configuring multiple proxy cells using cmutil on page 15-38.

Checking paths using cmutil on page 15-40.

Managing maps using cmutil on page 15-44.

Using cmutil to perform other specific tasks on page 15-51.

68P02901W17-T
Jan 2010

15-1

Introduction to cmutil

Chapter 15: cmutil

Introduction to cmutil

Purpose of cmutil
cmutil has two basic purposes. It allows a user to:

Configure the network and map configuration files that make up the CM MIB database.

Amend existing information in a MIB database. Amending MIB information is necessary

where there has been a change in the network, such as adding additional equipment, or
implementing revisions to the geographical coverage of the network.

cmutil supports both GSM and GPRS files and information.

Configuring new networks using cmutil

In the initial stages of configuring a new network, the MIB database is devoid of structural
information. It needs to be populated with information describing the network objects, their
relationships to each other, and the links between them. In addition to populating the MIB
database, background maps must be installed and configured. cmutil performs this initial
information population process.

When to use cmutil

Most network objects can be created from the GUI (see Configuring network objects using
the OMC-R GUI on page 1-26), others have to be created using the cmutil tool. However, all
objects can be created using cmutil.
cmutil provides a means of carrying over the OMC-R specific data for each class from one
release to another. This type of data includes user-friendly names and map coordinates. Without
the cmutil tool, all these objects would have to be created manually.

NOTE
Most cmutil operations can be performed using the OMC-R GUI. In most cases, and
when circumstances allow, it is recommended that these operations are performed
using OMC-R GUI rather than cmutil.

15-2

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Maximum number of parallel cmutil operations

Maximum number of parallel cmutil operations

The maximum number of cmutil operations that can be run in parallel can be set using the
environment variable: MAX_CMUTIL_OPS, see MIB locking on page 1-14 for further details.

Definition of cmutil terms: container and containee

cmutil can be used to manipulate container and containee information in the MIB database. A
container is a network object containing one or more other network objects. For example, a BSS
is a container. A containee is a network object contained within another network object. For
example, a site is a containee of a BSS. This is also referred to as the parent-child relationship,
where a parent is the container and a child is the containee.
For further information on containment, child-parent relationships, and the hierarchy of network
objects, see Management Information Base (MIB) on page 1-11.

Prerequisites for using cmutil

cmutil is run from a command line. Therefore, before using cmutil, a user should be:

Familiar with the operating system commands.

Able to navigate between directories.

Operate an ASCII based editor.

Using cmutil means that vital network data is exposed. Therefore, the user should also have a
complete understanding of the ramifications of changing this data.

Logging in for cmutil

To use cmutil, log in as omcadmin using one of the following procedures:

Log in from the System Processor.

Log in indirectly from an operator terminal

NOTE
To prevent possible system processor loading problems, Motorola recommends
omcadmin sessions are started remotely from an operator terminal.

68P02901W17-T

15-3
Jan 2010

Logging in for cmutil

Chapter 15: cmutil

Log in from the system processor

To log in from the System Processor, proceed as follows:

Procedure 15-1 Log in from the system processor

1

Log in as omcadmin using the user id:

omcadmin

Enter the appropriate password when requested.

If necessary, source the correct database using: mib_env

Log in indirectly from an operator terminal

To log in indirectly from an operator terminal, proceed as follows:

Procedure 15-2 Log in indirectly from an operator terminal

15-4

Remote login to the system processor:

rlogin <hostname>
where <hostname> is the name of the system processor.

Enter the appropriate password when requested.

If not omcadmin, change user by entering the command:

su - omcadmin

Enter the password when requested.

If necessary, source the correct database using:

mib_env

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

cmutil command syntax

cmutil command syntax

Introduction to cmutil command syntax

This section specifies the arguments and parameters required to perform the various cmutil
functions.

General syntax
The general syntax of the cmutil utility command is as follows:
cmutil -[primarg] -[secarg] <secparam>
The arguments and parameters are described as follows:

primarg (primary argument)

Primary arguments start a particular function. Only one primary argument can be used when
running cmutil. The full list is as follows:
-a
Specifies that objects are to be added to the MIB database (referred to as add mode).
-d
Specifies that objects are to be deleted from the MIB database.
-e
Specifies that details are to be extracted from the MIB database using a specified macro
script file.
-s
Specifies that the input file is to be syntax checked only.
-u
Specifies that objects are to be updated in the MIB database (referred to as update mode).
-x
Specifies that details are to be extracted from the MIB database (referred to as extract mode
or dump mode).

68P02901W17-T

15-5
Jan 2010

secarg (secondary argument)

Chapter 15: cmutil

secarg (secondary argument)

One of five secondary arguments which are used to supply additional information for a selected
function. More than one secondary argument can be used when executing cmutil. The full
list is as follows:
-h
Specifies a hierarchical operation with the extract (-x) option. Operations are applied to
specified objects and their children. (Sometimes referred to a hierarchical dump mode.)
-i
Direction switch. This argument is followed by the file-name secondary parameter to detail the
input file used with the add (-a), delete (-d), syntax check (-s) and update (-u) options.
-n
Used only with the -t CommsLink option and followed by the objectReference secondary
parameter. Specifies that only CommsLinks with the particular object reference as a node will
be extracted from the MIB database.
-o
Direction switch. This argument is followed by the file-name secondary parameter to detail the
output file used with all MIB database operations.
-t
Used with the objectType secondary parameter to specify that only objects of a certain type are
extracted from the MIB database.

secparam (secondary parameter)

One of three parameters associated with the secondary argument of the command. The list of
parameters and the arguments with which they are used are as follows:
file-name
Used with the -i and -o secondary arguments to specify the ASCII input or output file.
objectReference
Used with the -n secondary argument to specify the object reference.
objectType
Used with the -t secondary argument to specify the object type.

CAUTION
Do NOT use the object type Network.

15-6

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

ASCII file content used with cmutil

ASCII file content used with cmutil

Introduction to ASCII file content

For most cmutil operations an ASCII input file is required to provide the necessary information
for the activity. For example, the name of the Site to be deleted.
The data required in the ASCII file varies for the different operations of cmutil. For example,
it is not necessary to provide as much information to delete an object from the MIB database
as is required to create an object.
This section describes the content required in the ASCII file for the different operations of
cmutil.
The content of ASCII files to perform the following operations are described:

Adding objects to the CM MIB database.

Deleting objects from the CM MIB database.

Modifying objects in the CM MIB database.

Extracting objects from the CM MIB database.

ASCII file content when adding objects using cmutil

When used to input data to the MIB database, the cmutil utility configures the MIB database by
reading one or more ASCII files. Although it is possible to describe an entire configuration in
one file, it is suggested that it be divided into the following:

One file which describes the Network, OMC-R, and MSC managed objects.

A file for each BSS, RXCDR, or other parent in the system which describes the BSS or
RXCDR itself, all its contained sites, the objects within the site and their children.

One file which describes the links to the OMC-R and MSC/RXCDR as well as the intra
BSS, RXCDR, and site links.

A file for each user-defined map and its MapNodes and Maplinks as required.

68P02901W17-T

15-7
Jan 2010

ASCII file content when deleting objects using cmutil

Chapter 15: cmutil

Object and attribute description

The ASCII files listed contain descriptions of the objects that are to be added to the CM MIB
database by the cmutil utility. The objects are defined with all their attributes set exactly as
required for the selected MIB database operation. Attributes can be optional or mandatory
when creating objects. Optional attributes are those which do not require a defined value
for correct creation of the object.

NOTE
The optional flag indicates whether the attribute requires an assigned value when
creating an object with which this attribute is associated.

ASCII file content when deleting objects using cmutil

The ASCII file used to delete an object from the MIB database must specify sufficient attributes
of the object for it to be uniquely identified. Object identification is described in the MIB
object identification section.

ASCII file content when modifying objects using cmutil

The ASCII file used to modify an object in the MIB database must specify sufficient attributes to
uniquely identify the object and the attribute to be modified must be set as required. Object
identification is described in the MIB object identification section.

ASCII file content when extracting objects using cmutil

The ASCII file used to identify an object for which MIB database data is to be extracted must
specify sufficient information to uniquely identify the object. Object identification is described in
the MIB object identification on page 15-8 section.

MIB object identification

Most objects in the MIB database can be uniquely identified by a combination of some of the
following:

15-8

name.

rdnInstance.

gsmCellId.

object type.

object container.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

MIB object identification

Objects which are identified by a combination of elements, not listed above, are:

An MSI object is identified by its rdnInstance attribute and the site which contains the
MSI.

An MMS object is identified by the rdnInstance and parent of the MSI object which
contains the MMS and the rdnInstance of the MMS.

A MapNode object is identified by the name and type of the MapNode sourceNE and the
name of the Map on which the MapNode is displayed.

A MapLink object is identified by the name of the CommsLink, associated with the
MapLink, and the name of the Map on which the MapLink is displayed.

68P02901W17-T

15-9
Jan 2010

ASCII file rules used with cmutil

Chapter 15: cmutil

ASCII file rules used with cmutil

Introduction to ASCII file rules

ASCII files used with cmutil are governed by certain rules. These rules ensure consistency of
operation of cmutil and help prevent errors.
Each ASCII file is governed by rules for the following:

File syntax.

File content.

ASCII file syntax

The ASCII file syntax rules are as follows:

An object must exist in the MIB database before it can be referenced by any other object.
Hence when adding objects to the MIB database the order of object inclusion in the ASCII
file is important.

The character set permitted is printable ASCII characters only (ASCII values from 32 126 decimal inclusive) with the addition of <CR>, <LF> and <FF> (ASCII 13, 10 and
12 respectively) which are all treated as the end of line delimiter, and <TAB> (ASCII 9)
which is treated as a space.

Case is significant.

Blank lines, spaces, and tabs are permitted. Spaces and tabs are significant only within
quotes. Blank lines are not permitted within quotes.

\<character> combinations have the following special meanings within a quoted string,
that is, within quotation marks ( ):
To include the () character in a string use \.
To include a carriage return (CR) in a string use \r.
To include a linefeed (LF) in a string use \n.
To include the backslash character (\) in a string use \\.

15-10

Lines can be a maximum of 256 characters in length. Where \<character> pairs are
included, their length is equivalent to a single character.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

ASCII file content

ASCII file content

The ASCII file contents include the following:

Object definitions.

Comments.

Include directives.

Ignore directives.

Object definitions
An object definition is a standard format used to describe an object, in an ASCII file, used by
cmutil. The format of object definitions is described in the Object definition in cmutil ASCII
files on page 15-12.

Comments
Comment lines begin with one of the following:

The (//) characters.

The (#) character, which does not precede a valid directive.

All text after the two slash characters to the end of the line is ignored. The format of a comment
is as follows:
// this is a comment
# this is also a comment

Include directives
An include directive begins with a #include character string. The include directive allows a
configuration file to include other configuration files. The format of an include directive is
as follows: #include fileName
The fileName is the name of the required file. It can be an absolute path, otherwise the file
must be located in the current directory. There is no limit to the number of files (nesting)
which can be included.

Ignore directives
An ignore directive begins with a #ignoremib character string. The ignore directive is used
to identify data included in the ASCII file to be ignored by the cmutil utility. The format of
the ignore directive is: #ignoremib string
The string is the <attributeName> part of an attribute definition. The attribute definition is
then ignored. A full description of attribute definitions is given in Object definition in cmutil
ASCII files on page 15-12.

68P02901W17-T

15-11
Jan 2010

Object definition in cmutil ASCII files

Chapter 15: cmutil

Object definition in cmutil ASCII files

Introduction to object definition

An object definition is a standard format used to describe an object, in an ASCII file, used
by cmutil.

Description of object definition

An object is defined in the following format:
<objectType>
{
<attributeValueList>
}
Where:

is:

<objectType>

the type of object being created, modified, or deleted.

<attribute
ValueList>

a series of attribute definitions separated by commas. Refer to

Attribute definitions on page 15-12.

The order of object definitions is significant. Objects added from the same file must be ordered
so that objects are created before they are referenced by other objects. For example, parents
must be created before their children.

Attribute definitions
The attribute value list of any object contains a series of attribute definitions which determine
the characteristics of the object and its relationships with other objects in the CM MIB database.
The order of the attribute definitions within an attribute value list is not significant. Their
format is as follows:
<attributeName> = <attributeValue>

15-12

Where:

is:

<attribute
Name>

the name of the attribute.

<attribute
Value>

the value of the attribute and can be one of the

following:<integerValue>
<enumerationValue>
<stringValue>
<objectReference>

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Integer value

NOTE
Rules for attribute names are described in the Attribute names section.

Integer value
An integer value is specified as a series of numeric characters, possibly preceded by a minus
sign.

Enumeration value
An enumeration value is one of the following:

Site types (BSC-BTS, BSC, BTS, RXCDR). The RXCDR type is used because the single
site under an RXCDR is of type RXCDR.

Boolean (TRUE, FALSE).

String value
A string value is specified by a series of zero or more characters enclosed in quotation marks
( ). Spaces are significant between quotes. Only printable ASCII characters are permitted.
Attributes with the following types are entered as string values:

String.

Complex GSM Cell ID.

Complex connectivity.

Object ID.

Object ID List.

Object reference
An object reference is specified in one of three forms as follows:

68P02901W17-T

15-13
Jan 2010

Object reference

Chapter 15: cmutil

Form 1
<type>:<Name>
Where:

is:

<type>

the type of the following <Name> chosen from the valid NE_types
set. All objects with the attribute <Name> can be referenced.
For backward compatibility, NETWORK_NE, MSC_NE, OMC_NE,
BSS_NE, RXCDR_NE, and SITE_NE are also valid types.

<Name>

the name of an MIB database object, with a name attribute, in

quotation marks ( ).

Example:
BSS_NE:Cork specifies the BSS named Cork.
RXCDR_NE:Cork specifies the RXCDR named Cork.

Form 2
<type>:<Name><deviceType>:<deviceId1><deviceType>:<deviceId2>
Where:

is:

<type>

the type of the following <Name> chosen from the valid

NE_types set. All objects with the attribute <Name> can
be referenced. For backward compatibility, NETWORK_NE,
MSC_NE, OMC_NE, BSS_NE, RXCDR_NE, and SITE_NE are also
valid types.

<Name>

the name of an MIB database object, with a name attribute, in

quotation marks ( ).

<deviceType>

the type of device contained within the site.

<deviceId1>

the first device identifier.

<deviceId2>

the second device identifier.

Example:
SITE: Cork MSI:1MMS:0 specifies MMS 0 on MSI 1 in the Cork SITE.

Form 3
<type>:<Name> : <deviceType> <deviceId1> <deviceId2> <deviceId3>
Where:

is:

<type>

the type of the following <Name> chosen from the valid

NE_types set. All objects with the attribute <Name> can
be referenced. For backward compatibility, NETWORK_NE,
MSC_NE, OMC_NE, BSS_NE, RXCDR_NE, and SITE_NE are also
valid types.
Continued

15-14

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Attribute names

Where:

is:

<Name>

the name of an MIB database object, with a name attribute, in

quotation marks ( ).

<deviceType>

the type of device contained within the site.

<deviceId1>

the first device identifier.

<deviceId2>

the second device identifier.

<deviceId3>

the third device identifier.

Example:
SITE_NE: Mahon: MSI 3 0 0 specifies MSI 3 in the Mahon SITE.

NOTE

An <objectReference> must not exceed one line.

The colons can optionally be preceded and followed by a single space.

Attribute names
The rules for attribute names are as follows:

Attribute names are case sensitive.

latitude and longitude have attribute values in degrees*100, where the fractional part of
a degree is specified in decimal form, rather than in minutes. For example, Latitude 51
degrees, 24 minutes is entered as 5140.

Rules when name is the attribute are as follows:

Names within objects of the same type in the CM MIB database must be unique.

NOTE
This means that the same site name cannot be re-used under a different BSS.

A name changed after creation cannot be altered to a name already in use in that class.

A second name attribute is used only when the name attribute is being changed. This one
is called newname, and it may appear in any attribute value list for an object which has a
name attribute. Where present, the newname attribute must obey the same rules as the
name attribute in the same attribute value list.

68P02901W17-T

15-15
Jan 2010

cmutil status messages

Chapter 15: cmutil

cmutil status messages

Introduction to cmutil status messages

As objects are created or updated in the MIB database, cmutil returns status messages. The
messages identify the current object being processed and the status of the operation.

Definition of cmutil status messages

A message may be a successful operation report, a warning report, or an error report. In the
event of an error report, cmutil exits and further lines from the input file are not processed.

cmutil warning messages

Some typical warning messages are shown below. These messages result from an attempt to
update read-create attributes in the MIB database. The cmutil input file was named TESTA.
TESTA, Line:4: warning: Attribute MCC read create (cannot be updated)
TESTA, Line:5: warning: Attribute MNC read create (cannot be updated)
TESTA, Line:6: warning: Attribute rdnInstance read create (cannot be updated)
Update succeeded for Network.
A common source of cmutil warnings results from an attempt to add existing objects to the MIB
database. These warnings can be ignored.

cmutil error messages

Errors result from syntax errors, type errors, and violation of MIB database integrity. Examples
of error messages and warning messages are shown below. The error results from the inclusion
of an invalid attribute, MNC, for the BSS object in the input file TESTB.
TESTB, Line:4: warning: Attribute MCC read create (cannot be updated)
TESTB, Line:5: warning: Attribute MNC read create (cannot be updated)
TESTB, Line:6: warning: Attribute rdnInstance read create (cannot be updated)
TESTB, Line:18: error: Attribute/Operation MNC not in class BSS
1 error(s) encountered
When an error is encountered, cmutil exits and the remaining contents of the input file are
not read.
15-16

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

cmutil script files

cmutil script files

Introduction to cmutil script files

Two script files are included as standard with the cmutil utility. These files provide added
functionality for common operations not supported by cmutil alone.
The following scripts are included:

MoveCommsLinks.

HierDelete.

MoveCommsLinks
The MoveCommsLinks script takes a cmutil hierarchical dump file of the network as input and
creates an output file identical to the input file, but with the CommsLink structures (and their
devices, if any) moved to the end of the file. This new file is named <input file>.filtered. When
this file is used as an input file to cmutil in add mode, objects are created in the MIB database
before the CommsLinks are created. This ensures that objects referenced by CommsLinks exist
before they are referenced. The following command syntax is used:
MoveCommsLinks <input file>
Where:

is:

<input file>

the name of the ASCII file containing the hierarchical dump.

HierDelete
The HierDelete script uses MIB internal functionality to locally delete a BSS, RXCDR, or site
from the MIB. The MIB internal functionality is invoked using cmutil.
HierDelete has the following command syntax:
HierDelete <object class> <object name>
Where:

is:

<object class>

BSS
RXCDR
SITE

<object name>

for example, BSS1-site3

HierDelete cannot be used to delete a Network. Instead, use the InitMib script to clean the
MIB database.
For further details of how to use HierDelete to delete a BSS/RXCDR, see Deleting a BSS/RXCDR
on page 4-44.

68P02901W17-T

15-17
Jan 2010

Using cmutil to add, delete, and modify CM MIB data

Chapter 15: cmutil

Using cmutil to add, delete, and modify CM MIB data

Introduction to using cmutil

This section describes how to use cmutil to perform basic tasks, such as adding and deleting
data in the CM MIB.
The functions described are:

Checking the syntax of an ASCII input file.

Adding objects to the CM MIB database.

Deleting objects from the CM MIB database.

Updating data in the CM MIB database.

Checking input file syntax

Most of the tasks described in this section use an input file to supply information to cmutil.
Before being used with cmutil, check the input file for correct syntax. The following syntax is
used:
cmutil -s -i <input file>
Where:

is:

<input file>

the name of the ASCII file to be checked.

Adding objects using cmutil

To add object(s) to the CM MIB database from an input file, the following syntax is used:
cmutil -a -i <input file>
Where:

is:

<input file>

the name of the ASCII file containing the object(s) to be added.

NOTE
When creating an object in the MIB database, the remote attribute of the object
determines whether the object is created over the OMC-R-BSS interface. This flag is
included for all BSS objects but is only significant for Neighbor and Algorithm objects
which can be created across the interface. All other objects can be created locally.

15-18

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adding objects using cmutil

Example: Adding a new BSS using cmutil

To add a BSS to the MIB using cmutil, follow these steps:

Procedure 15-3 Add a new BSS using cmutil

1

Create an input file describing the BSS and its children.

NOTE
The file needs to have the BSS described before its sites and
each further contained object before its children. It may be
convenient to dump details of another BSS in hierarchical
mode and then use this file as a guide.
2

Run cmutil utility in add mode to create the BSS and its children.

NOTE
If the add fails, correct the file if necessary, and resubmit.
3

Add CommsLinks, MapLinks, and MapNodes to the MIB database in

a separate standard format file.

If any of the objects created are to appear on more than one map, more
than one set of MapNodes and MapLinks has to be created.

If the default positions on the map are not satisfactory, move the
objects manually using the GUI.

NOTE
A default map is created whenever a new BSS or RXCDR
is added.

Recommendation
Following a MIB database update, it is recommended that the new MIB database information be
extracted to an ASCII file using the cmutil in extract mode. This allows for recreation of the
MIB database in the event of system failure.

68P02901W17-T

15-19
Jan 2010

Deleting objects using cmutil

Chapter 15: cmutil

Deleting objects using cmutil

To delete object(s) from the CM MIB database according to the contents of an input file, the
following syntax is used:
cmutil -d -i <input file>
Where:

is:

<input file>

the name of the ASCII file containing the object(s) to be deleted.

Use of deleteLocal and remote attributes when deleting

NOTE
During a cmutil -d -i operation, the value of the deleteLocal attribute in the input
file is never used. If the deleteLocal attribute has been set to TRUE previously in
the MIB database (either through a cmutil create or cmutil update) then the value of
remote attribute in the input file is not used. In other words, the deletion is always
local due to the deleteLocal attribute having been set to TRUE previously in the
MIB database. If the deleteLocal attribute has been set to FALSE previously in the
MIB database (either through a cmutil create or cmutil update) then the value of the
remote attribute in the input file is used. Therefore in the case of remote = TRUE,
an attempt is made to delete the device at the BSS and the OMC. In the case of
remote = FALSE, an attempt is made to delete the device only at the OMC.
When deleting an object from the MIB database, the deleteLocal attribute of the object
determines whether the object is only deleted locally at the OMC-R. The remote attribute
determines whether the object is deleted remotely (that is, deleted over the OMC-R-BSS
interface). To delete an object locally on the OMC-R only: set the deleteLocal attribute of the
object to TRUE and remote attribute to FALSE, then run the cmutil delete option. To delete an
object locally and remotely (that is, locally at the OMC-R, and over the OMC-R-BSS interface),
set the deleteLocal attribute of the object to FALSE and the remote attribute to TRUE, then
run the cmutil delete option.
The following list describes the outcome for all deleteLocal and remote attribute combinations:

deleteLocal= TRUE and remote= TRUE the object is only deleted locally at the OMC-R.

deleteLocal= FALSE and remote= TRUE the object is deleted locally at the OMC-R and
remotely over the OMC-R-BSS interface.

deleteLocal= FALSE and remote= FALSE the object is deleted locally at the OMC-R
and remotely over the OMC-R-BSS interface.

deleteLocal= T RUE and remote= FALSE means the object is only deleted locally
at the OMC-R.

To delete a device locally using cmutil, the deleteLocal attribute of the device must have been

previously set to TRUE. It is not sufficient to set the deleteLocal attribute to TRUE in the input
file at the time of deletion. The deleteLocal attribute can be set to TRUE at the time of creation
using cmutil -a -i or by updating the attribute using cmutil -u -i.

15-20

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Updating objects using cmutil

Updating objects using cmutil

Syntax
To update the CM MIB database according to the contents of an input file, the following
syntax is used:
cmutil -u -i <input file>
Where:

is:

<input file>

the name of the ASCII file containing the data to be updated.

NOTE
When updating an object in the MIB database, the remote attribute of the object
determines whether the objects attributes are updated over the OMC-R-BSS
interface. The value remote = true will update objects attributes over the OMC-R-BSS
interface and remote = false will not send information across OMC-R-BSS interface
(see Use of deleteLocal and remote attributes when deleting on page 15-20 for
further details). This flag is included for all BSS objects.

Example: Extracting, modifying, and updating NE details using cmutil

For example, to extract, modify, and update NE details using cmutil, follow these steps:

Procedure 15-4 Extract, modify, and update NE details using cmutil

1

Create an input file with the description of one object, in the standard
form.

NOTE
The file needs to have sufficient details to identify the object.
For example, the file to identify a site could read:
SITE
{
name = Mahon,
container = BSS:Cork
}
2

Input the file to the cmutil utility in non-hierarchical extract mode.

cmutil dumps the full site details into a file.

CommsLink information needs to be dumped separately (use -t -n

<SITE object reference>).
Continued

68P02901W17-T

15-21
Jan 2010

Modifying multiple devices or functions using cmutil

Chapter 15: cmutil

Procedure 15-4 Extract, modify, and update NE details using cmutil (Continued)
4

Edit the site details file to make the necessary changes.

Run cmutil in update mode with this file as input, as shown in the
syntax section.
Result: The CM MIB is updated.

Recommendation
Following a MIB database update, it is recommended that the new MIB database information be
extracted to an ASCII file using the cmutil in extract mode. This allows for recreation of the
MIB database in the event of system failure.

Modifying multiple devices or functions using cmutil

Overview of procedure
To use cmutil to modify multiple devices or functions, follow these steps:

Procedure 15-5 Modify multiple devices or functions using cmutil

1

Extract the required data only from the MIB using cmutil, as described
in the following subsection.

Insert new values by editing the extracted file, as described in the

following subsection.

Run cmutil in update mode to reinsert the new values.

Extracting data for a single site or NE

To extract data for a single site or NE using cmutil, create a cmutil input file called bss.ip,
specifying either a single BSS or site, and extract all data for a BSS or site by entering:
cmutil -x -h -i <input file> -o <output file>
Examples of cmutil input files and extraction of data are shown in Extracting data from the CM
MIB using cmutil on page 15-25.
The following shows how to extract only devices/functions (MIB objects) of a specific type
from the hierarchical output file:
awk '/<object_type> /, /}/' bss.op > /tmp/bss_dri_strip
The following shows how to extract a devices/functions substitute (for example DRI) for the
<object_name>:
awk '/DRI /, /}/' bss.op > /tmp/bss_dri_strip

15-22

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Modifying multiple devices or functions using cmutil

Extracting data for all objects of specific type

To extract all objects of specific type from the MIB, enter:
cmutil -x -t <object_type> -o \ <device_type>_all.op
The file extracted through cmutil contains all the MIB data for the device. This data can then
be analyzed or further parsed. For example, extract all DRI objects from MIB by entering:
cmutil -x -t DRI -o DRI_all.op
The file extracted using cmutil contains all the MIB data for the DRI devices. This data can
then be modified and reinserted in to the MIB.

Modifying extracted MIB data

The file extracted using cmutil contains all the MIB data for the device. This data can then be
further parsed. The following example strips down the extracted cmutil output to only the data
to be modified (example is cell1AntennaSelct):
awk '$1 == DRI || $1 == container || $1 == \ cell1AntennaSelct
|| $1 == { || $1 == } || $1 == \ rdnInstance {print}'
DRI_all.op > DRI_all.op.strip
The following example changes the value for cell1AntennaSelct for all objects:
sed 's/cell1AntennaSelct = 1/cell1AntennaSelct = 2/g' \
DRI_all.op.strip > DRI_all.op.strip.upd

Updating the MIB with the new data

The following shows how to use cmutil in update mode to change the parameters, both in the
network and in the MIB:
cmutil -u -i <modified_data_file>
The following example reinserts the modified DRI data:
cmutil -u -i DRI_all.op.strip.upd
This changes the value for cell1AntennaSelct for all objects.

68P02901W17-T

15-23
Jan 2010

Ways of extracting data from the CM MIB

Chapter 15: cmutil

Ways of extracting data from the CM MIB

Overview
Two main tools can be used to extract data from the CM MIB:

cmutil, see Extracting data from the CM MIB using cmutil on page 15-25.
The cmutil utility is the recommended tool, as it is the only tool which extracts the data as
it appears on the Detailed View. However, the data has to be further parsed if analyzing
large amounts of data.

15-24

Direct sql queries, see Extracting data from the CM MIB using SQL on page 15-30.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Extracting data from the CM MIB using cmutil

Extracting data from the CM MIB using cmutil

Overview of extracting data from the CM MIB using cmutil

The recommended method of extracting information from the CM MIB is to use cmutil. cmutil
can extract all the attributes associated with each object, contained in single or multiple MIB
DBMS tables.
Data may be extracted from the MIB using cmutil in a number of ways. Examples of extracts
using cmutil are:

cmutil -x -t PATH -o <o/p file_name> - extracts path data.

cmutil -x -t FreqHopSys -o <o/p file_name> - extracts FreqHopSys data.

cmutil -x -h -t CommsLink -o <o/p file_name> - extracts CommsLink data.

cmutil e <macro_name> -i <i/p file_name> -o <o/p file_name> - extracts data

according to the macro script listed in the input file (macro script file), see Extracting
information using a macro script on page 15-28.

Examples of input files and extraction commands

Examples of cmutil input files and extraction of data are shown below:
Input file for a single BSS, called bss.ip for example:
BSS
{
name = BSS_Cork
}
Input file for a single site, called site.ip for example:
SITE
{
name = Mahon_site_2
}
Input file for a single PCU, called pcu.ip for example:
PCU
{
name = Mahon_pcu
}

68P02901W17-T

15-25
Jan 2010

cmutil data extraction examples

Chapter 15: cmutil

To extract all data for a BSS:

cmutil -x -h -i bss.ip -o bss.op
To extract all data for a site:
cmutil -x -h -i site.ip -o site.op
To extract all data for a PCU:
cmutil -x -h -i pcu.ip -o pcu.op

cmutil data extraction examples

NOTE

In Extracting objects using cmutil on page 15-26 and Extracting objects and
hierarchy of children using cmutil on page 15-27, the input file has to have a
description of one unique object in the standard form. This file is input to the
cmutil utility in non-hierarchical dump mode. As an example, the file to identify
a site can read:
SITE
(
name = SITE_Mahon

The utility dumps the full site details into a file.

CommsLink information needs to be dumped separately (using -t -n <SITE

object reference>). Edit the site details file to make the necessary changes.

Extracting objects using cmutil

Details of the objects listed in an input file can be extracted from the MIB and written to an
output file using the following syntax:
cmutil -x -i <input file> -o <output file>
For example, to extract the BSS software data for a specific BSS, enter the following:
mib_env cmutil -x -i BSS1017.ip -o BSS1017.op awk '$1 == versionString || $1 ==
neLoadVersion' \ bss1017.op
The output resulting from the awk command in the example above is:
versionString = 1600,
neLoadVersion = 06.00.00.15,
Also see Extracting information using a macro script on page 15-28.

15-26

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Extracting objects and hierarchy of children using cmutil

Extracting objects and hierarchy of children using cmutil

Details of objects and hierarchy of parents (objects listed in an input file, along with their
children and associated devices (in the case of CommsLinks)), can be extracted from the MIB
and written to an output file using the following syntax:
cmutil -x -h -i <input file> -o <output file>

Example: Checking the hardware deployed for a single site, PCU, or NE

using cmutil
For example, to check the hardware deployed for a single site, PCU or NE using cmutil, create
a cmutil input file, for example bss.ip, specifying either a single BSS, PCU or site, and extract
all data for a BSS, PCU or site by entering:
cmutil -x -h -i <input file> -o <output file>

Extracting objects and hierarchy of children of specific type

Details of objects and hierarchy of children of a specified type, can be extracted from the MIB
and written to an output file using the following syntax:
cmutil -x -h -t <objectType> -o <output file>

Extracting objects with no children of specific type

Details of objects with no children of specific type, can be extracted from the MIB and written
to an output file using the following syntax:
cmutil -x -t <objectType> -o <output file>

Extracting software version information for more than one NE

For example, to extract software version information for more than one NE, enter the following:
cmutil -x -t NESoftware -o NESoftware.op
Each NE contains a currentSW line containing the current version setting.
The following is an example of a NE instance NESoftware.op file:
NESoftware
{
downloadFlag = TRUE,
currentSW = OMC:omc SWInventory:only SoftwareLoad:BSGSM1600f3,
newSWLoad = OMC:omc SWInventory:only SoftwareLoad:BSGSM1600f3,
forcedFlag = FALSE,
container = BSS:bss1017
}

68P02901W17-T

15-27
Jan 2010

Extracting CommsLinks and associated devices

Chapter 15: cmutil

Extracting a device type in the network using cmutil

To extract all objects of specific type from the MIB, enter:
cmutil -x -t DRI -o dri_all.op

Extracting CommsLinks and associated devices

Details of CommsLinks and associated devices with a specified reference such as a node can be
extracted from the MIB and written to an output file using the following syntax:
cmutil -x -h -t CommsLink -n <ObjectReference> -o <output file>
<ObjectReference> examples:
BSS_NE:Cork specifies the BSS named Cork.
RXCDR_NE:Cor_RX specifies the RXCDR named Cor_Rx.
SITE:CorkMSI:1MMS:0 specifies MMS 0 on MSI 1 in the Cork SITE.
SITE_NE:Mahon:

MSI 3 0 0 specifies MSI 3 in the Mahon SITE.

NOTE

An <objectReference> must not exceed one line.

The colons can optionally be preceded and followed by a single space.

The following example extracts all link information for a BSS called Cork:
mib_env cmutil -x -h -t CommsLink -n BSS_NE:Cork -o Co_links.op
Details of all CommsLinks can be extracted from the MIB, and written to an output file, using
the following syntax:
cmutil -x -t CommsLink -o <output file>

Extracting information using a macro script

A macro script contains coding to perform a specific operation.
Some macro scripts are provided by Motorola, and are listed in
/usr/omc/current/config/cmuinit. Any of the macros listed in this location can be run
using the -e option.
For example, the macro file called basedumphierSWInventory contains the following coding:

15-28

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Extracting information using a macro script

{
OIDList SWInventoryList;
OIDList oidlist;
SWInventoryList = SWInventory {};
Print( ,SWInventoryList);
oidlist = GetContainees(SWInventoryList, TRUE);
Print( , oidlist);
}
To run cmutil with the e option the syntax is:
cmutil e [macro name] o [output filename]
For example, the following command runs the macro script called basedumphierSWInventory
and outputs the results to a file called SWInventory.out:
cmutil e basedumphierSWInventory o SWInventory.out
The following is an example of the contents of the output file SWInventory.out:
SWinventory
{
container = OMC:somc143
}
SoftwareLoad
{
loadname = BSGSME-17600d.tar,
loadVersion = 07.06.00.0d,
NEType = 0,
numObjects = 120,
container = OMC:somc143 SWInventory:only
}
To run a macro script not provided by Motorola (for example, a macro script you have created)
use the following syntax:
cmutil e [macro name] i [input filename] o [output filename]
Where, [input filename] is the name of the file where the macro script resides.

68P02901W17-T

15-29
Jan 2010

Extracting data from the CM MIB using SQL

Chapter 15: cmutil

Extracting data from the CM MIB using SQL

Overview of extracting data using SQL

Motorola recommends using cmutil to extract data from the MIB database. It is also possible,
but not recommended or supported, to extract data from the MIB using SQL and the ACE
report writer.

NOTE
Only experienced database programmers should write scripts to access the MIB
database.

When not to use SQL to extract data

NOTE
Motorola does not recommend direct sql queries on the MIB during busy hours
(08:00 - 24:00) as sql queries add a load to the system processor. The CM MIB is not a
standard DBMS reason, hence sql cannot be used all the time. The schema is created
by and runs under, OSP. OSP is a middleware product, mapping application-defined
objects to and from relational databases.

Extracting data using SQL queries

Tables in the MIB
Objects usually have all the data that can be viewed from a Detailed View stored in their generic
table in the MIB DBMS (<objectname>table2), for example, DRI data is stored in dritable2.
This can be extracted using SQL queries. However, some MIB objects do not have all their
attributes stored under their corresponding table name, the most obvious examples being the
Frequency hopping object, and the path object.

15-30

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

SQL script rules

NOTE
The new mangled table names where applicable, as well as the mangled attribute
names are to be noted.

Basic procedure information

The following list gives basic information for extracting information from the MIB using sql.

Run SQL on the System Processor.

The database environment must be established by invoking one of the following, as

appropriate:
/usr/omc/config/global/env/mibInfxUserConfig.csh
or
/usr/omc/config/global/env/mibInfxUserConfig.sh
Then use one of the following to access the database: $INFORMIXDIR/bin/dbaccess or
$INFORMIXDIR/bin/sacego
The name of the database can be retrieved from the DBNAME variable, declared in:
/usr/omc/config/global/env/mibProcConfig.csh

Dirty Read isolation must be set to protect the OMC processes. When using dbaccess,
after selecting the database, execute the command:
set isolation to dirty read;

When using the ACE report writer, the environment variable SACE_ISOL must be set to
the value dirty read before running sacego.

SQL script rules

To write SQL scripts which retrieve the OMC-R objects, the SQL script writer needs to know the
following:

The OSP/OMC-R internally generated object class codes and object attribute codes.

Object class tables.

Attribute location in class tables.

The algorithm that OSP uses to name-mangle tables and columns because of the
INFORMIX[Symbol_registersans] 17 character table/column limit. This algorithm uses
the generated class and attribute codes.

OMC-R object oid attributes point to another OMC-R object stored in another table.

Each multi-valued (list) attribute is stored in a separate MVA table. The MVA table is
joined with the main object-class table to yield a single multi-valued attribute for a given
object class.

68P02901W17-T

15-31
Jan 2010

SQL script rules

Chapter 15: cmutil

Obtaining object-attribute information out of a database is achieved by reproducing some of

the functionality that OSP provides in C++/ESQL/cursor programming. A simple SQL scripting
interface is not always sufficient enough to do the same task.

Objects which do not have all data in a single table

Objects which do not have all data in a single table can be viewed from a Detailed View. The
Detailed View is stored in the object generic table in the MIB DBMS (<objectname>table2).
Objects of this type are listed:

Assoc_BSSs.

BTP.

DHP.

FreqHopSys.

PATH.

NOTE
The only guaranteed way to extract full information for multi-tabled objects is
from the CM MIB by using cmutil.

Assoc_BSSs
The Detailed View also contains a links section which is read from the information contained in
the child Conn_link objects.

BTP and DHP

The Assigned DRI information contained in the BTP and DHP objects are stored as
complex_connectivity datatype in a different table of the MIB DBMS:

BTP Assigned DRI information is not stored in btptable2.

DHP Assigned DRI information is not stored in dhptable2.

FreqHopSys
Each of the mobile allocation attributes, FreqHopSys, are stored in the MIB as an octet string.
Each mobile allocation attribute is stored in an INFORMIX BLOB space. The attributes can only
be extracted using cmutil. The details of FreqHopSys attributes are shown in Table 15-1.

15-32

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

SQL script rules

Table 15-1 FreqHopSys attribute details

Attribute

mobile_alloc

Description

This attribute defines mobile allocation.

Values

The string is a set of 64 arfcn values. Each arfcn is

specified by a 2 octet integer.

Datatype

OCTET_STRING.

Displayable text for DV

Mobile allocation.

bssAccess

RO.

bssSysgenAccess

RW.

Path
Table 15-2 and Table 15-3 show attributes containing the link information for each path object.
The attributes are stored in different tables to pathtable2 in the MIB DBMS.

Table 15-2

Path attributes link(1 ... 10) (stored outside pathtable2, in intlisttable2)

Description

Datatype

There are ten of these

attributes, link1 to
link10, describing the
links in the path.

COMPLEX
_CONNECTIVITY.

Values
Terminating Site: 0 - 40, 254.
Upstream MSI: 0 - 50, 254.
Upstream MMS: 0 or 1, 254.
Downstream MSI: 0 - 50, 254.
Downstream MMS: 0 or 1, 254.
254 is used for the TS
switching site. The Site and
Upstream/Downstream MSI/MMS
identifiers contain 254 if this link
specifies a TS Switch.

This attribute is not on the PATH Detailed View

Table 15-3 Path attribute commsLinkList (stored outside pathtable2 in oidlisttable2)

Description

Datatype

Values

When paths are created, appropriate

CommsLinks are created to represent the
point-to-point links specified in link1 to link
10. Each path has a list of CommsLinks
which are associated with that path. The
commsLinkList attribute stores this information.

OID_LIST.

1 - 10 (number
of links in path).

68P02901W17-T

15-33
Jan 2010

SQL script rules

Chapter 15: cmutil

The effect of the OSP port on MIB

The OSP can affect old queries in two ways:

Name mangling, whereby names of either tables or attributes are shortened by substituting
numbers for the characters in the name, and

Storing the instance attribute as three separate attributes in the DBMS.

Table 15-4 shows mangled object classes with resulting table names.

Table 15-4 Mangled object classes with resulting table names

MIB object

MIB DBMS table name

Software Load

softwa28258table2.

SurrndCellHC

surrnd16209table2.

TestNeighbor

testne16421table.

Table 15-5 shows examples of OIDs mangled in OSP 4. Any queries which do not mangle
these OIDs will fail.

Table 15-5 Example of OIDs mangled in OSP 4

OID

Mangled version

Assigned Function (GPROC)

assigne16499class, assigne16499tomid, assi16499instrite,

assi16499instleft.

neighbor template (neighbor)

nbrt16188instrite, nbrt16188instleft.

initial SW Load (BSS, RXCDR)

init12064instrite, init12064instleft.

default map (BSS, RXCDR)

defa12059instrite, defa12059instleft.

defaultmap (Network)

defa28004instrite, defa28004instleft.

related device (CBL, DRI, LCF,

MTL, OMF, OML, RTF, RSL,
XBL)

rela12127instrite, rela12127instleft.

related RTF (DRI)

rela16498instrite, rela16498instleft.

current CSFP SW load

(NESoftware)

curr28278instrite, curr28278instleft.

new CSFPLoad (NESoftware)

new16188instrite, new16188instleft.

current DRI

curr16269instrite, curr16269instleft.

schedule

sched5010instrite, sched5010instleft.

omc Object

omcob8028instrite, omcob8028instleft.

alarmedevice

alar12145instrite, alar12145instleft.

Storing the instance attribute as three separate attributes in the DBMS

Instance attributes, used in indexing and relationships, have been split into three separate
attributes.

15-34

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Tips on using SQL queries for MIB

Tips on using SQL queries for MIB

Order of queries:
Attributes of type OID (such as oid, source, target, container) used in where clauses should be
ordered as follows:

class

instleft

instrite

tomid

If there are attributes additional to the OID types they should come after the OID attributes
in the clauses.

68P02901W17-T

15-35
Jan 2010

Configuring CommsLinks using cmutil

Chapter 15: cmutil

Configuring CommsLinks using cmutil

Introduction to configuring CommsLinks using cmutil

Connections between NEs are specified using CommsLinks, with MapLinks being used to show
the CommsLinks on a Map.
The set of devices which is associated with a CommsLink may be changed.

Recommendation
Following a MIB database update, it is recommended that the new MIB database information
be extracted to an ASCII file using cmutil in extract mode. This allows for recreation of the
MIB database in the event of system failure.

Changing CommsLinks using cmutil

To change a connection, follow these steps:

Procedure 15-6 Change a CommsLink using cmutil

1

Delete the appropriate CommsLink using cmutil.

Create a CommsLink with the correct NEs using cmutil.

All associated MapLinks (on different maps) are deleted automatically when their source
CommsLink is deleted.

Adding CommsLinks to existing sites using cmutil

To add links to existing sites, follow Procedure 15-7 .

Procedure 15-7 Add CommsLinks to existing sites using cmutil

1

Open a shell and change to the temporary work directory:

cd $OMC_TOP/config/local/cm_mib_db/temp_files
Continued

15-36

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting CommsLinks from existing sites using cmutil

Procedure 15-7 Add CommsLinks to existing sites using cmutil (Continued)

2

Use an editor to create a file named new_link, which defines the

CommsLink between the two sites to be connected. For example, Cork
and Douglas Sites exist, but are currently not linked.
// Link from Cork BTS to Douglas BTS
//
CommsLink
{
name = Cork_BTS-Douglas_BTS,
nodeA = SITE:Cork,
nodeB = SITE:Douglas,
}
CommsLink:Cork_BTS-Douglas_BTS_01->AddDevice(SITE:Cork :
MMS 0 0 0)
CommsLink:Cork_BTS-Douglas_BTS_02->AddDevice(SITE:Douglas
: MMS 0 1 0)

Syntax check and add the new links using the following commands,
respectively:
cmutil -s -i new_link
cmutil -a -i new_link

As new CommsLinks have been added, use DB Export to extract the

latest BSS configuration.

Deleting CommsLinks from existing sites using cmutil

To delete links from existing sites, proceed as follows:

Procedure 15-8 Delete CommsLinks from existing sites using cmutil

1

Open a shell and change to the temporary work directory:

cd $OMC_TOP/config/local/cm_mib_db/temp_files

Extract the link information for the site in question, using:

cmutil -x -h -t CommsLink -n 'SITE:<name>' -o links

Delete the links, using:

cmutil -d -i links

68P02901W17-T

The default network map is modified along with any user-defined

maps containing these links. As links have been deleted, no node
positioning is required. Follow the procedure described in Chapter 13
Manipulating Maps, to dump the modified map.

15-37
Jan 2010

Configuring multiple proxy cells using cmutil

Chapter 15: cmutil

Configuring multiple proxy cells using cmutil

Creating multiple proxy cells

The usual requirement is for multiple proxy cells to be configured at a given time. The
recommended way to create the proxy cells is to use the pcellImport utility. See Exporting and
importing proxy cell information between OMC-Rs on page 8-155.
Alternatively, to create multiple proxy cells using cmutil proceed as follows:

Procedure 15-9 Create multiple proxy cells using cmutil

1

Extract all the proxy cell objects to an output file, proxy.cmu, by

entering:
cmutil -x -t ProxyCell -o proxy.cmu

Use vi or another editor to create, from the data, a list of proxy cells
to be added.

Use the cmutil utility in add mode (-a) to insert the additions into the
MIB:
cmutil -a -i proxy.cmu

Modifying multiple proxy cells

To modify multiple proxy cells, proceed as follows:

Procedure 15-10 Modify multiple proxy cells

1

Extract all the proxy cell objects to an output file, proxy.cmu, by

entering:
cmutil -x -t ProxyCell -o proxy.cmu

Use vi or another editor to change the data (other than LAC-CI) and
save the changes.

Use the cmutil utility in update mode (-u) to insert the changes back
into the MIB:
cmutil -u -i proxy.cmu

15-38

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting multiple proxy cells

Deleting multiple proxy cells

CAUTION
Always consult the CM supervisor before deleting a proxy cell, as deleting a proxy cell
also deletes any neighbors in the MIB with the same gsmCellid. This may remove
live neighbors.
To delete multiple proxy cells, proceed as follows:

Procedure 15-11 Delete multiple proxy cells

68P02901W17-T

Extract all the proxy cell objects to an output file, proxy.cmu, by

entering:
cmutil -x -t ProxyCell -o proxy.cmu

Use vi or another editor to create, from the data, a list of proxy cells to
be deleted.

Use the cmutil utility in delete mode (-d) to make the deletions from
the MIB:
cmutil -d -i proxy.cmu

15-39
Jan 2010

Checking paths using cmutil

Chapter 15: cmutil

Checking paths using cmutil

Checking multiple paths using cmutil

All the data for a path can be viewed from a Detailed View. However, some of the data of
each path object is not stored in its generic table in the MIB DBMS (pathtable2). This makes
extraction through SQL queries difficult. The only way to extract full information for multiple
paths objects from the CM MIB is to use cmutil.

Checking a path for a single site or NE using cmutil

To check path connectivity of a single site or NE, proceed as follows:

Procedure 15-12 Check path connectivity for a single site or NE using cmutil
1

To extract all the data for a BSS or site, create a cmutil input file
called bss.ip specifying either a single BSS or site by entering:
cmutil -x -h -i <input file> -o <output file>

NOTE
Examples of cmutil input files and extraction of data are
shown in Extracting data from the CM MIB using cmutil on
page 15-25.
2

To extract path only objects, parse the data by entering:

awk '/Path /, /}/'bss.op > /tmp/bss_PATH_strip

Checking multiple paths in the OMC-R using cmutil

To check path connectivity throughout the OMC-R, extract all path objects from MIB by entering:
cmutil -x -t PATH -o path_all.op
The file extracted through cmutil contains all the MIB data for the path devices. This data can
then be analyzed or further parsed.

15-40

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Comparison of cmutil path output with TTY rlogin output

Comparison of cmutil path output with TTY rlogin output

Example 1 Two Sites in path (site 12 to BSC through Site 3):
Figure 15-1 shows an example of cmutil output for two sites in path, with columns and specific
labels marked.

Figure 15-1 Two sites cmutil output example

COLUMNS
1

link2 = [

12,

0,

1,

3,

0] ,

link1 = [

3,

1,

0,

5,

0],

Terminating site

PATH

Unique PATH Identifier

numInSequence = 2 ,
rdnInstance = 1 ,
container = SITE: ?SITE-12:Snake_Road" ,

}
ti-GSM-Twositescmutiloutputexample-00855-ai-sw

The columns shown in Figure 15-1 are used as shown in Table 15-6.

Table 15-6

cmutil output use of columns

Use

Column
1

Site identifiers. The terminating site is always on the top row. Link2 in the
example in Figure 15-1 gives site 12 as the terminating site.

Upstream MSI identifier of site.

NOTE
BSC downstream MSI identifier connection is always link1 row.
Continued

68P02901W17-T

15-41
Jan 2010

Comparison of cmutil path output with TTY rlogin output

Table 15-6

cmutil output use of columns (Continued)

Use

Column
3

Chapter 15: cmutil

Upstream MMS identifier of site.

NOTE
BSC downstream MMS identifier connection is always link1 row.
4

Downstream MSI identifier of site.

NOTE
BSC upstream MSI identifier connection is always link1 row.
5

Downstream MMS identifier of site.

NOTE
BSC upstream MMS identifier connection is always link1 row.
The TTY rlogin output of the example in Figure 15-1 is shown for comparison:
The terminating SITE id is: 12
The Unique PATH Identifier is: 1
The BSC MSI identifier is: 5
The BSC MMS identifier is: 0
SITE identifier: 3
The upstream MSI identifier is: 1
The upstream MMS identifier is: 0
The downstream MSI identifier is: 3
The downstream MMS identifier is: 0
SITE identifier: 12
The upstream MC identifier is: 0
The upstream MMS identifier is: 1

Example 2 One site in path (site 12 direct to BSC):

cmutil o/p:
Figure 15-2 shows an example of cmutil output for one site in path, with columns and specific
labels marked.

15-42

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Figure 15-2

Comparison of cmutil path output with TTY rlogin output

One site cmutil example with columns and specific labels marked
COLUMNS
1

12,

0,

0,

4,

0] ,

Terminating site

PATH

{
link1 = [

Unique PATH Identifier

numInSequence = 1 ,
rdnInstance = 0 ,
container = SITE: ?SITE-12:Snake_Road" ,

ti-GSM-Onesitecmutilexamplewithcolumnsandspecificlabelsmarked-00856-ai-sw

The columns shown in Figure 15-2 are used as shown in Table 15-6.
The TTY output of the example in Figure 15-2 is shown below for comparison:
MMI-RAM 0115 -> disp_eq 0 PATH 12 0 0
The terminating SITE id is: 12
The Unique PATH Identifier is: 0
The BSC MSI identifier is: 4
The BSC MMS identifier is: 0
SITE identifier: 12
The upstream MSI identifier is: 0
The upstream MMS identifier is: 0

68P02901W17-T

15-43
Jan 2010

Managing maps using cmutil

Chapter 15: cmutil

Managing maps using cmutil

Creating new maps

When creating new user-defined maps, create a separate file for each map with the associated
MapNodes and MapLinks.
Map names may be changed by updating their details. MapLinks cannot be updated and must
be deleted and recreated. Only the x and y attributes of MapNodes can be changed.
The nodes on a map may be listed using hierarchical dump starting with an input file containing
a named map.
CommsLinks can exist independently of MapLinks, but the reverse is not true. Deleting a
CommsLink deletes any associated MapLinks on all maps. Similarly, deleting an NE causes the
deletion of any associated MapNodes MapLinks and CommsLinks.

Adding a map using cmutil

To add a new map using cmutil, a new input file must be created, and the data added to the
MIB. Use the following procedure to add a new map using cmutil:

Procedure 15-13 Add a new map using cmutil

1

Open a shell and change to the directory containing the map

configuration files:
cd $OMC_TOP/config/local/cm_mib_db/map_files

Use an editor to open a <map_name>.map file.

where <map_name> is the name of the user-defined map to be created.

Create map object definitions in the <map_name>.map file according

to the cmutil syntax rules.

NOTE
The file must contain object definitions for all map nodes
and map links associated with the particular map. It must
also contain one map object definition, specifying a unique
map name.
4

Save the <map_name>.map file and exit the editor.

Continued

15-44

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Example map input file

Procedure 15-13 Add a new map using cmutil (Continued)

5

Before adding the new map to the MIB database, check the file for
syntax. Use the following cmutil command to check the file syntax:
cmutil -s -i <map_name>.map
where <map_name>.map is the name of a map file.
If the file syntax check cannot be completed, self-explanatory error
messages are displayed.

Repeat steps 2 to 5 for each user-defined map to be added to the

network.

Once the input file has been created and checked for correct syntax,
add it to the MIB database using the following command:
cmutil -a -i <map_name>.map
where <map_name>.map is the name of a map file to be added to the
MIB database.

Store the new input file as a .0 file which can then be used if the MIB
database is to be reinitialized. Use the following command to rename
the files as original files with a .0 extension:
mv <map_name>.map <map_name>.map.0

Recommendation
Following a MIB database update, it is recommended that the new MIB database information
be extracted to an ASCII file using the cmutil extract facility. This allows for recreation of the
MIB database in the event of system failure.

Example map input file

The following example shows a map input file with all its contained objects. The map file (for
example, Ireland.map) must exist in the directory: $OMC_TOP/config/global/map
A blank background may be specified by using the filename empty. The node name within the
MapNode definition is the name of the NE which is to be displayed on the map, for example:
node = BSS:Cork. The CommsLink within the MapLink definition is the CommsLink that has
been defined for the two connecting nodes (NEs).
//
// MAP Configuration File.
//
// 5-March-1993
//
Map
{
name = Ireland-Map,
background = Ireland
}

68P02901W17-T

15-45
Jan 2010

Example map input file

Chapter 15: cmutil

MapNode
{
source = OMC:OMC,
container = Map:Ireland-Map
}
MapNode
{
source = MSC:Cork-MSC,
container = Map:Ireland-Map
}
MapNode
{
source = BSS:Cork,
container = Map:Ireland-Map
}
MapNode
{
source = SITE:Cork-BSC/BTS,
container = Map:Ireland-Map
}
MapNode
{
source = SITE:Mahon,
container = Map:Ireland-Map
}
MapLink
{
source = CommsLink:OMC-Cork-BSC/BTS,
container = Map:Ireland-Map
}
MapLink
{
source = CommsLink:Cork-MSC-Cork-BSC/BTS,
container = Map:Ireland-Map
}
MapLink
{
source = CommsLink:Cork-BSC/BTS-Mahon,
container = Map:Ireland-Map
}

15-46

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Deleting a map using cmutil

Deleting a map using cmutil

To remove a map from the MIB database using cmutil, follow these steps:

Procedure 15-14 Delete a map using cmutil

1

Open a shell and change to the directory containing the temporary

work files:
cd $OMC_TOP/config/local/cm_mib_db/temp_files

To remove a map from the system, first use an editor to create a

criteria file containing the name of the map to be deleted, as shown in
the following example:
Map
{
name = <map_name>
}
where <map_name> is the name of the map to be deleted.

Save the criteria file and exit the editor.

Delete the map data using:

cmutil -d -h -i criteria

If the map which has been removed from the system is likely to be
needed in the future then perform step 6 and step 7, otherwise remove
the map file:
rm <map_name>.map

Rename the original map configuration file using:

mv <map_name>.map.0 <map_name>.map.0.del

If a modified file exists, rename the file using:

mv <map_name>.map <map_name>.map.del

Storing updated map data

When a map has been modified, store a copy of it. Follow Procedure 15-15 to store updated
map data:

Procedure 15-15 Store updated map data

1

Open a shell and change to the directory containing the temporary

work files:
cd $OMC_TOP/config/local/cm_mib_db/temp_files
Continued

68P02901W17-T

15-47
Jan 2010

Changing a map background using cmutil

Chapter 15: cmutil

Procedure 15-15 Store updated map data (Continued)

2

Use an editor to create a file called map_criteria that contains the

definition of the map to be extracted as shown in the following example:
Map
{
name = <map_name>
}
where <map_name> is the name of the map whose configuration is to
be extracted.

Exit the editor.

Use the following command to extract the updated map configuration

to a file:
cmutil -x -h -i map_criteria -o <map_name>.map
where <map_name> is the name of the map whose MIB data is to be
extracted.

Move the <map_name>.map file to the map files directory:

mv <map_name>.map
$OMC_TOP/config/local/cm_mib_db/map_files/<map_name>.map

Changing a map background using cmutil

To change a map background using cmutil, follow these steps:

Procedure 15-16 Change a map background using cmutil

1

Open a shell and change to the directory containing the temporary

work files:
cd $OMC_TOP/config/local/cm_mib_db/temp_files

To change a map background, first use an editor to create a criteria

file containing the definition of the new map background, as shown
in the following example:
Map
{
name = <Map_name>,
background = <Background_Map_File>
}
where <Map.name> is the name of the map whose background is to be
changed and <Background_Map_File> is the name of the new map
background.
The <.map> extension in the filename must both be specified.
Continued

15-48

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Adding map links using cmutil

Procedure 15-16 Change a map background using cmutil (Continued)

3

Save the criteria file and exit the editor.

Before updating the MIB database, check the criteria file for syntax.
Use the following cmutil command to check the file syntax:
cmutil -s -i criteria

NOTE
If the file syntax check cannot be completed, self-explanatory
error messages are displayed.
5

Once the criteria file has been checked for correct syntax, update
the MIB database using:
cmutil -u -i criteria

Store the updated map data using the procedure described later in
this section.

Adding map links using cmutil

To add map links to existing sites, proceed as follows:

Procedure 15-17 Add map links using cmutil

1

Open a shell and change to the temporary work directory:

cd $OMC_TOP/config/local/cm_mib_db/temp_files

Use an editor to create a file named new_link, which defines the

CommsLink between the two sites to be connected. For example:
Cork and Douglas Sites exist, but are currently not linked.
// Link from Cork BTS to Douglas BTS
//
CommsLink
{
name = Cork_BTS-Douglas_BTS,
nodeA = SITE:Cork,
nodeB = SITE:Douglas,
}
CommsLink:Cork_BTS-Douglas_BTS_01->AddDevice(SITE:Cork :
MMS 0 0 0)
CommsLink:Cork_BTS-Douglas_BTS_02->AddDevice(SITE:Douglas
: MMS 0 1 0)
Continued

68P02901W17-T

15-49
Jan 2010

Deleting map links using cmutil

Chapter 15: cmutil

Procedure 15-17 Add map links using cmutil (Continued)

3

Syntax check and add the new links:

cmutil -s -i new_link
cmutil -a -i new_link

As new CommsLinks have been added, extract the latest BSS

configuration.

Deleting map links using cmutil

To delete map links from existing sites, proceed as follows:

Procedure 15-18 Delete map links using cmutil

1

Open a shell and change to the temporary work directory:

cd $OMC_TOP/config/local/cm_mib_db/temp_files

Extract the link information for the site in question, using:

cmutil -x -h -t CommsLink -n 'SITE:<name>' -o
links
where <name> is the name of the SITE in question.

15-50

Delete the links, using:

cmutil -d -i links

The default network map has been modified and possibly any
user-defined maps. As links have been deleted, no node positioning is
required. Follow the procedure described in the Storing updated map
data in Adding and deleting a user-defined regional map on page 13-2,
to remove the modified map.

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Using cmutil to perform other specific tasks

Using cmutil to perform other specific tasks

Introduction to other specific tasks

The tasks can be performed using cmutil and ate described in the following sections:

Populating a new MIB database.

Dumping the entire MIB database to a file.

Managing regions.

Changing multiple LACs and/or CIs.

Modifying multiple neighbors of same site or NE.

Checking multiple hopping objects.

NOTE
Most of these cmutil operations can also be done from the Navigation Tree.

Populating a new MIB database using cmutil

Recommendations
When used to input data to the MIB database, cmutil configures the MIB database by reading
one or more ASCII files. Although it is possible to describe an entire configuration in one file, it
is suggested that the configuration information be divided into the following:

A file which describes the Network, OMC-R, and MSC managed objects.

A file for each BSS, RXCDR, or other parent in the system which describes the BSS or
RXCDR itself, all its contained sites, the objects within the site and their children.

A file which describes the links to the OMC-R and MSC/RXCDR as well as the intra BSS,
RXCDR, and site links.

A file for each user-defined map and its MapNodes and Maplinks as required.

68P02901W17-T

15-51
Jan 2010

Dumping the entire CM MIB to a file using cmutil

Chapter 15: cmutil

Using cmutil
To use cmutil to populate a new MIB, follow these steps:

Procedure 15-19 Populate a new MIB using cmutil

1

Run cmutil in add mode on each file, creating the Network, OMC-R
and MSCs first.

Create the BSSs, RXCDRs and their hierarchies, followed by the

CommsLinks, and finally the user-defined Maps, MapNodes and
MapLinks for each map.
Result: Each file should be successfully processed before starting the
program with the next file. If an error occurs, that file can be edited
and corrected, if necessary, before a rerun.

Dumping the entire CM MIB to a file using cmutil

NOTE
This method is not envisaged as a means of backing up the MIB database.
To dump all NE-related details to a file, along with any CommsLinks and their devices, perform
a cmutil hierarchical dump starting with the network object.
To retrieve all the map information, use the cmutil hierarchical dump with the type specifier
set to Map.
If the dump files are to be used to populate an empty MIB database, use the script file
MoveCommsLinks to pre-process the files. This script creates a file in the correct format (for
example, CommsLinks occurring after the objects they reference) for adding to a MIB database.
MoveCommsLinks is described in cmutil script files on page 15-17.

Managing regions using cmutil

cmutil can be used to add a region to the MIB. The OMC Administrator must create a cmutil
input file containing the region name, the user identification, and a list of the network elements
to be added to the region.
The OMC Administrator can also add, update, or delete network elements in existing regions
using cmutil.
The OMC Administrator can also use cmutil to list the regions in a network by either outputting
the region information to file or performing a hierarchical extraction. Likewise, the OMC
Administrator can output details of a particular region to an output file.

15-52

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Changing multiple LACs and/or CIs using cmutil

Changing multiple LACs and/or CIs using cmutil

To make multiple LAC and/or CI changes, proceed as follows:

Procedure 15-20 Change multiple LACs and/or CIs using cmutil

1

To extract all the data for a BSS or site, create a cmutil input file,
bss.ip specifying either a single BSS or site by entering:
cmutil -x -h -i <input file> -o <output file>

NOTE
Examples of cmutil input files and extraction of data are
shown in Extracting data from the CM MIB using cmutil on
page 15-25.
2

To extract cell only objects, parse the data by entering:

awk '/CELL /, /}/'bss.cmu > cell.cmu

This parsed file can then be further parsed, to extract only the cell
gsmCellid attribute line, per cell object. Input the following as one line:
awk '$1 == CELL|| $1 == gsmCellId || $1 == { || $1 ==
} {print}' Cell.cmu > Cell_upd.cmu

Use vi or another editor to change cell_upd.cmu.

Insert a new line for every cell object requiring an update. Each update
line should contain the new gsmCellid attribute with new LAC and/or
CI setting:
CELL
{
gsmCellId = 001-01-12-66,
newGsmCellId = 001-01-444-66
}

Save the changes to cell_upd.cmu.

Use the cmutil utility in update mode (-u) to insert the changes back
into the MIB:
cmutil -u -i cell_upd.cmu
Result: The MIB Propagation form is displayed.

Check the propagation is successful for all sources/neighbors affected.

NOTE
A single source cell may not be updated due to a lock on
the object. Note the failures, and resolve them manually by
opening the affected Neighbor Detailed View and correcting.
9

68P02901W17-T

Upload each affected NE database to the OMC-R.

15-53
Jan 2010

Modifying multiple neighbors of same site or NE using cmutil

Chapter 15: cmutil

Modifying multiple neighbors of same site or NE using cmutil

To modify multiple neighbors of the same site or NE, use the following procedure:

Procedure 15-21 Modify multiple neighbors of the same site or NE using cmutil
1

To extract all the data for a BSS or site, create a cmutil input file
called bss.ipspecifying either a single BSS or site by entering:
cmutil -x -h -i <input file> -o <output file>

NOTE
Examples of cmutil input files and extraction of data are
shown in Extracting data from the CM MIB using cmutil on
page 15-25.
2

To extract neighbor-only objects, parse the data by entering:

awk '/Neighbor /, /}/'bss.cmu > nei.cmu

Use vi, or another editor, to change the data (other than LAC-CI).

Save the changes to nei.cmu.

Use the cmutil utility in update mode (-u) to insert the changes back
into the MIB by entering:
cmutil -u -i nei.cmu

Checking multiple hopping objects using cmutil

All the data for a FreqHopSys object can be viewed from a FreqHopSys Detailed View. However,
some of the data of each FreqHopSys object is stored in its generic table in the MIB DBMS
(freqhopsystable2). The only way to extract full information for multiple FreqHopSys objects
from the CM MIB is by using cmutil.
To check multiple hopping objects using the TTY interface, follow Procedure 15-22.

15-54

68P02901W17-T
Jan 2010

Installation and Configuration: GSM System Configuration

Checking multiple hopping objects using cmutil

Procedure 15-22 Check multiple hopping objects using cmutil

1

To extract all the data for a BSS or site, create a cmutil input file
called bss.ipspecifying either a single BSS or site by entering:
cmutil -x -h -i <input file> -o <output file>

NOTE
Examples of cmutil input files and extraction of data are
shown in Extracting data from the CM MIB using cmutil on
page 15-25.
2

To extract FreqHopSys only objects, parse the data by entering:

awk '/FreqHopSys /, /}/'bss.op > /tmp/HopSys_strip

To check multiple hopping objects throughout the OMC-R using cmutil, extract all FreqHopSys
objects from MIB by entering:
cmutil -x -t FreqHopSys -o FreqHopSys_all.op
The file extracted using cmutil contains all the MIB data for the FreqHopSys devices. This
data can then be analyzed or further parsed.

68P02901W17-T
Jan 2010

15-55

Checking multiple hopping objects using cmutil

Chapter 15: cmutil

15-56

68P02901W17-T
Jan 2010

Index

Index

A
A interface . . . . . . . . . . . . . . . .
5-22
ABSS
Assoc_BSS . . . . . . . . . . . . . . .
4-68
adap_ho_al_trg_rq. . . . . . . . . 8-185, 8-188
adap_ho_pbgt . . . . . . . . . . . . . . . 8-185
adap_ho_rxlev . . . . . . . . . . . 8-185, 8-188
adap_ho_rxqual . . . . . . . . . . 8-185, 8-188
adap_trigger_hop_rxqual_dl . . . . 8-185, 8-188
adap_trigger_hop_rxqual_ul . . . . 8-185, 8-188
adap_trigger_pbgt. . . . . . . . . 8-185, 8-188
adap_trigger_pbgt_nbr . . 8-185, 8-190 to 8-191
adap_trigger_rxlev_dl . . . . . . . 8-185, 8-188
adap_trigger_rxlev_ul . . . . . . . 8-185, 8-188
adap_trigger_rxqual_ul . . . . . . 8-185, 8-188
adaptive handovers
configuring . . . . . . . . . . . . . . . 8-188
for a cell . . . . . . . . . . . . . . . 8-185
for a neighbour . . . . . . . . . . . . 8-190
using OMC-R GUI . . . . . . . . . . . 8-188
configuring for a neighbour
using OMC-R GUI . . . . . . . . . . . 8-190
using TTY interface . . . . . . . . . . 8-191
overview . . . . . . . . . . . . . . . . 8-185
parameters . . . . . . . . . . . 8-185, 8-188
Add new PCU hardware to increase GPRS
capacity . . . . . . . . . . . . . . . . . . 2-190
add_cell command . . . . . . . . . . . .
8-10
add_circuit . . . . . . . . . . . . . . . . . 5-2
add_conn . . . . . . . . . . . . . . . . . . 5-8
Adding a BSS/RXCDR
overview . . . . . . . . . . . . . . . . . 4-2
Adding a BTS
using copy_path command . . . . . . .
7-40
Adding a cell
recommended procedure . . . . . . . . . 8-6
using copy/change . . . . . . . . . . . . 8-8
using the OMC-R GUI . . . . . . . . . .
8-11
using TTY interface . . . . . . . . . . .
8-10
Adding a map link . . . . . . . . . . . . . 13-11
Adding a map node . . . . . . . . . . . .
13-6
Adding a nailed connection . . . . . . . .
5-25
Adding an Assoc_BSS
using the OMC-R GUI . . . . . . . . . .
4-68
Adding an XBL
using OMC-R GUI . . . . . . . . . . . . 9-200
Adding BSC-RXCDR connectivity . . . . . . 5-8
using OMC-R GUI . . . . . . . . . . . . . 5-5
using TTY interface . . . . . . . . . . . . 5-7
68P02901W17-T
Jan 2010

Adding multiple neighbours

add_nei utility . . . . . . . . . . . . . . 8-129
Adding network objects
using cmutil . . . . . . . . . . . . . . . 15-18
algorithm Detailed View
description of fields . . . . . . . . . . .
8-96
grouping
General . . . . . . . . . . . . . . . .
8-97
algorithms
adding
using chg_cell_element command . . .
8-98
autocreation and autodeletion . . . . .
8-13
creating/deleting
overview . . . . . . . . . . . . . . .
8-94
defining
overview . . . . . . . . . . . . . . .
8-94
deleting . . . . . . . . . . . . . . . . .
8-93
modifying default
using OMC-R GUI . . . . . . . . . . .
8-95
using TTY interface . . . . . . . . . .
8-98
allow_8k_trau . . . . . . . . . . . . . . . 2-173
AlmEgsmOPT parameter . . . . . . . . .
2-79
AMR
Full Rate . . . . . . . . . . . . . . . . 2-129
Half Rate . . . . . . . . . . . . . . . . 2-129
amr_bss_half_rate_enabled
changing using TTY interface . . . . . .
4-77
Antenna_Select number
checking . . . . . . . . . . . . . . . .
7-59
Apply audit inconsistencies
displaying results . . . . . . . . 10-13, 10-15
Assigning a hopping system to each RTF timeslot
using TTY interface . . . . . . . . . . . 8-176
Assigning quality 7 to missing measurement
reports . . . . . . . . . . . . . . . . . . 8-224
using OMC-R GUI . . . . . . . . . . . . 8-224
using TTY interface . . . . . . . . . . . 8-225
Assoc_BSS
adding to the network
using OMC-R GUI . . . . . . . . . . .
4-68
changing NE ID
using OMC-R GUI . . . . . . . . . . .
4-80
configuring . . . . . . . . . . . . . . .
4-68
creating . . . . . . . . . . . . . . . . .
4-70
deleting
using OMC-R GUI . . . . . . . . . . .
4-70
using TTY interface . . . . . . . . . .
4-71
description . . . . . . . . . . . . . . .
4-68
IX-1

Index

Audit logs
deleting . . . . . . . . . . . . . . . . .
managing . . . . . . . . . . . . . . . .
printing list of . . . . . . . . . . . . . .
setting the delete period . . . . . . . .
viewing . . . . . . . . . . . . . . . . .
Auditing
a BSS or RXCDR
using OMC-R GUI . . . . . . . . . . .
a network
using OMC-R GUI . . . . . . . . . . .
aborting while in progress . . . . . . .
deleting audit logs . . . . . . . . . . .
functionality . . . . . . . . . . . . . .
log files . . . . . . . . . . . . . . 10-5,
managing logs . . . . . . . . . . . . .
multiple sites . . . . . . . . . . . . . .
overview . . . . . . . . . . . . . . . .
Per Site Audit feature . . . . . . . . . .
per Site audit functionality
enabling . . . . . . . . . . . . . . .
printing an inconsistency report . . . .
problems and solutions . . . . . . . . .
propagation of changes to neighbour
cells . . . . . . . . . . . . . . . . . . .
disabling . . . . . . . . . . . . . . .
enabling . . . . . . . . . . . . . . .
proper use of CM procedures . . . . . .
recommendations . . . . . . . . . . . .
recommended use. . . . . . . . . . . .
scenarios . . . . . . . . . . . . . . . .
scheduling . . . . . . . . . 10-5, 10-8,
deleting . . . . . . . . . . . . . . . .
modifying . . . . . . . . . . . . . . .
printing . . . . . . . . . . . . . . . .
using OMC-R GUI . . . . . . . . . . .
updating database with inconsistencies . . . . . . . . . . . . . . . . . . .
viewing an inconsistency report. . . . .
viewing audit logs. . . . . . . . . . . .
auSchedule Detailed View window . . . .
Autocreation of a proxy cell . . . . . . . .
using OMC-R GUI . . . . . . . . . . . .
AXCDR
Assoc_RXCDR . . . . . . . . . . . . . .

Assoc_BSS (contd.)
displaying details
using TTY interface . . . . . . . . . .
4-71
setting parameters
using TTY interface . . . . . . . . . .
4-71
Assoc_BSS Detailed View
description of fields . . . . . . . . . . .
4-69
grouping
Identification . . . . . . . . . . . . .
4-69
State . . . . . . . . . . . . . . . . .
4-70
Assoc_RXCDR
changing NE ID
using OMC-R GUI . . . . . . . . . . .
4-80
configuring . . . . . . . . . . . . . . .
4-72
creating
using OMC-R GUI . . . . . . . . . . .
4-72
using TTY interface . . . . . . . . . .
4-76
deleting
using OMC-R GUI . . . . . . . . . . .
4-79
using TTY interface . . . . . . . . . .
4-79
description . . . . . . . . . . . . . . .
4-72
displaying details
using TTY interface . . . . . . . . . .
4-76
Assoc_RXCDR Detailed View
description of fields . . . . . . . . . . .
4-73
grouping
Channel Mode Usage (AMR Full Rate & Half
Rate/GSM Half Rate) . . . . . . . . .
4-75
Identification . . . . . . . . . . . . .
4-73
Local Routing Information . . . . . .
4-74
state . . . . . . . . . . . . . . . . .
4-74
Audit
displaying the time of the last audit . . . 10-38
Intelligent . . . . . . . . . . . . . . . .
10-3
of multiple BSS . . . . . . . . . . 10-4, 10-18
Audit gather phase
configuring . . . . . . . . . . . . . . .
10-5
Audit inconsistencies
applying from the Audit Logs form . . . 10-13
to 10-14
Audit inconsistency report . . . . . . . . 10-30
printing . . . . . . . . . . . . . . . . . 10-31
updating database . . . . . . . . . . . 10-32
updating the database . . . . . . . . . 10-32
viewing . . . . . . . . . . . . . . . . . 10-30

10-33
10-29
10-29
10-33
10-29

10-14
10-12
10-29
10-33
10-2
10-10
10-29
10-17
10-2
10-6
10-6
10-31
10-10
10-35
10-37
10-36
10-11
10-8
10-8
10-9
10-19
10-27
10-24
10-27
10-19
10-32
10-30
10-29
10-19
8-150
8-152
4-72

B
BA list . . . . . . . . .
Backup files
RF.CNFG . . . . . .
band_preference . . .
band_preference_mode
Barred Cells form . . .
Barring
calls

IX-2

. . . . . . . . . . 8-240
.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

. . . .
12-8
. 2-34, 2-152
. 2-35, 2-153
. . . . 8-239

Barring (contd.)
calls (contd.)
at a cell . . . . . . . . .
at a site . . . . . . . . .
incoming handovers. . . .
Barring calls
displaying barred cells . .
Baseband frequency hopping

. . . . . . . 8-239
. . . . . . .
7-55
. . . . . . . 8-240
. . . . . . . 8-239

68P02901W17-T
Jan 2010

Index

Baseband frequency hopping (contd.)

defining . . . . . . . . . . . . . . .
description . . . . . . . . . . . . .
guidelines for use . . . . . . . . . .
Batch rlogin script
using to create a BTS . . . . . . . .
Batch session
running script file . . . . . . . . . .
Batch templates
use in configuring sites . . . . . . .
Bay Level Calibration facility
enabling. . . . . . . . . . . . . . .
BAY_LEV_CAL environmental variable
BCCH carrier frequency
changing
using OMC-R GUI . . . . . . . . .
locating at a multiple cell site . . . .
training sequence code
changing . . . . . . . . . . . . .
bep_period . . . . . . . . . . . . . .
bep_period2 . . . . . . . . . . . . . .
ber_oos_mon_period parameter . . . .
ber_restore_mon_period parameter . .
bs_ag_blks_res parameter. . . . . . .
BSC
creating
using OMC-R GUI . . . . . . . . .
enhanced capacity feature . . . . .
BSC High Load Protection Mechanism
2 . . . . . . . . . . . . . . . . . . .
BSC sites
introduction . . . . . . . . . . . . .
BSC-BTS dynamic allocation
considerations at a BTS . . . . . . .
displaying details for a BTS
using TTY interface . . . . . . . .
displaying resources
using TTY interface . . . . . . . .
DYNETs and DYNETGroups
Configuring . . . . . . . . . . . .
enabling at a BTS . . . . . . . . . .
using OMC-R GUI . . . . . . . . .
using TTY interface . . . . . . . .
impact on RSLs . . . . . . . . . . .
impact on RTFs . . . . . . . . . . .
overview . . . . . . . . . . . . . .
parameters . . . . . . . . . . . . .
BSC-RXCDR connectivity
adding . . . . . . . . . . . . . . .
using OMC-R GUI . . . . . . . . .
using TTY interface . . . . . . . .
connectivity table . . . . . . . . . .
deleting . . . . . . . . . . . . . . .
using OMC-R GUI . . . . . . . . .
using TTY interface . . . . . . . .
displaying
using TTY interface . . . . . . . .
BSCBTSDynAllocOpt parameter . . .

68P02901W17-T
Jan 2010

. . 8-175
. . . 2-9
. .
2-10
. .

7-14

. .

7-15

. .

7-14

. .
. .

9-81
9-81

. . 8-213
. . 8-214
.
.
.
.
.
.

.
.
.
.
.
.

8-221
8-76
8-76
9-138
9-138
8-226

. .
7-26
. .
2-94
Phase
. . 2-183
. . .

7-2

. . .

7-7

. .

2-21

. .

4-98

.
.
.
.
.
.
.
.

.
4-90
.
4-90
.
2-21
.
2-21
. 9-176
. 9-183
.
2-19
.
2-20

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

5-8
5-5
5-7
5-8
5-8
5-7
5-8

. . . 5-8
. .
2-20

BSIC
changing . . . . . . . . . . . . . . . . 8-219
BSP
cage and slot details . . . . . . . . . .
9-35
configuring . . . . . . . . . . . . . . .
9-35
creating
using OMC-R GUI . . . . . . . . . . .
9-35
equipping
using TTY interface . . . . . . . . . .
9-38
parameters . . . . . . . . . . . . . . .
9-36
BSP CPU utilization reduction for higher call
handling capacity . . . . . . . . . . . . . 2-200
BSP Detailed View
description of fields . . . . . . . . . . .
9-36
grouping
Cage and Slot . . . . . . . . . . . . .
9-37
Identification . . . . . . . . . . . . .
9-36
State . . . . . . . . . . 9-37, 9-115, 9-118
BSS
adding
assigning DTE X.121 addresses . . . .
5-19
creating database . . . . . . . . . . .
4-41
using cmutil. . . . . . . . . . . . . . 15-19
adding to network
overview process . . . . . . . . . . . . 4-2
configurations. . . . . . . . . . . . . . . 7-3
configuring MSC to BSS overload
control . . . . . . . . . . . . . . . . .
2-25
using TTY interface . . . . . . . . . .
2-23
containment. . . . . . . . . . . . . . .
9-29
creating
using the OMC-R GUI . . . . . . . . . . 4-6
database
uploading . . . . . . . . . . . . . . .
1-24
definition of . . . . . . . . . . . . . . .
1-23
deleting . . . . . . . . . . . . . . . . .
4-44
deleting at MUX . . . . . . . . . . . .
4-48
configuration changes . . . . . . . .
4-49
dependencies . . . . . . . . . . . . .
4-49
removing the cabling . . . . . . . . .
4-48
removing the NE . . . . . . . . . . .
4-49
removing the NE link . . . . . . . . .
4-50
deleting at OMC-R . . . . . . . . . . .
4-44
deleting at packet switch . . . . . . . .
4-48
configuration changes . . . . . . . .
4-48
deleting routeing table entries . . . .
4-48
removing the cabling . . . . . . . . .
4-48
description of routeing function. . . .
9-134,
9-155
list of features. . . . . . . . . . . . . .
4-12
logfiles . . . . . . . . . . . . . . . . . . 1-9
modifying details
using the OMC-R GUI . . . . . . . . .
4-38
parameter names
viewing in a Detailed View form . . .
1-30
remotely logging in from the OMC-R . .
1-39
remotely logging in using WebMMI . . .
1-45
reparenting . . . . . . . . . . . . . . . 4-100

IX-3

Index

BSS (contd.)

BSS/RXCDR database (contd.)

reparenting to a different OMC-R . . . . 4-101

reparenting to a different RXCDR . . . . 4-104
setting overload control of call barring. .
2-23
to RXCDR
checking connectivity . . . . . . . . . . 5-2
BSS Detailed View
description of fields . . . . . . . . . . . . 4-8
grouping
A5 Algorithms. . . . . . . . . . . . .
4-19
Call Trace . . . . . . . . . . . . . . .
4-34
CERM . . . . . . . . . . . . . . . . .
4-30
Channel Mode Usage (AMR Full Rate & Half
Rate/GSM Half Rate) . . . . . . . 4-35, 4-37
CLM Timers. . . . . . . . . . . . . .
4-28
Directed Retry . . . . . . . . . . . .
4-29
ECERM . . . . . . . . . . . . . . . .
4-30
Enhanced Full Rate . . . . . . . . . .
4-30
Flash Information . . . . . . . . . . .
4-27
General . . . . . . . . . . . . . . . .
4-19
GPRS . . . . . . . . . . . . . . . . .
4-30
Identification . . . . . . . . . . . . . . 4-9
LCS . . . . . . . . . . . . . . . . . .
4-35
Map Information . . . . . . . . . . .
4-33
MTP Timers . . . . . . . . . . . . . .
4-28
Multiband . . . . . . . . . . . . . . .
4-29
NCCR . . . . . . . . . . . . . . . . .
4-35
Network Addresses . . . . . . . . . .
4-11
Network Assisted Cell Change . . . .
4-34
Optional Features . . . . . . . . . . .
4-12
PCS 1900 Frequency . . . . . . . . .
4-27
Pre-empt . . . . . . . . . . . . . . .
4-38
Quality of Service . . . . . . . . . . .
4-35
RSL Congestion . . . . . . . . . . . .
4-38
Signalling Information . . . . . . . .
4-16
SMS Information . . . . . . . . . . .
4-34
SSM Timers . . . . . . . . . . . . . .
4-28
State . . . . . . . . . . . . . . . . .
4-10
Traffic Parameters . . . . . . . . . .
4-34
Trunk Information . . . . . . . . . .
4-28
BSS Naming menu option . . . . . . . . .
1-30
BSS software features
Intelligent Multi Layer Resource Management . . . . . . . . . . . . . . . . . . 2-150
BSS User Security Management . . . . . 2-201
bss_egsm_alm_allowed parameter . . . .
2-79
bss_msc_overload_allowed . . . . . . . .
2-25
BSS_NAMING environment variable . . .
1-30
BSS/RXCDR database

configuration management database

object . . . . . . . . . . . . . . . . . .
4-41
database script file . . . . . . . . . . .
4-41
definition . . . . . . . . . . . . . . . .
4-41
directory structure . . . . . . . . . . .
4-43
NE database checks. . . . . . . . . . .
4-42
script file . . . . . . . . . . . . . . . .
4-41
types . . . . . . . . . . . . . . . . . .
4-41
BTP
cage and slot details . . . . . . . . . .
9-39
configuring . . . . . . . . . . . . . . .
9-39
creating
using OMC-R GUI . . . . . . . . . . .
9-40
equipping . . . . . . . . . . . . . . . .
9-42
parameters . . . . . . . . . . . . . . .
9-40
BTP Detailed View
description of fields . . . . . . . . . . .
9-40
grouping
Cage and Slot . . . . . . . . . . . . .
9-41
Identification . . . . . . . . . . . . .
9-40
State . . . . . . . . . . . . . . . . .
9-42
BTS
adding
equipping BTS site . . . . . . . . . .
7-21
methods. . . . . . . . . . . . . . . .
7-34
on-line . . . . . . . . . . . . . . . .
7-14
overview . . . . . . . . . . . . . . .
7-12
rocommended method . . . . . . . .
11-6
using a batch rlogin script . . . . . .
7-14
using copy_path command . . . . . .
7-40
using TTY interface . . . . . . . . . .
7-17
BSC configurations . . . . . . . . . . . . 7-3
changing transmit power . . . . 8-234, 8-236
concentration . . . . . . . . . . . . . .
2-19
configuring . . . . . . . . . . . . . . . . 7-1
configuring Horizonmicro and Horizoncompact . . . . . . . . . . . . . . . . . . . . 7-7
copying and pasting. . . . . . . . . . .
11-6
creating
using OMC-R GUI . . . . . . . . . . .
7-26
deleting . . . . . . . . . . . . . . . . . 11-34
displaying details of
using TTY interface . . . . . . . . . .
2-21
enabling remote calibration . . . . . . .
9-82
Horizon II . . . . . . . . . . . . . . . . . 7-8
Horizon II macro . . . . . . . . . . . .
7-10
BTS sites
introduction . . . . . . . . . . . . . . . . 7-2
bts_txpwr_max_inner . . . . . . . . 2-31 to 2-32

C
Cabinet
creating
using OMC-R GUI . . . . . . . . . . .

IX-4

Cabinet (contd.)
4-54

displaying for a PCU . . . . . . . . . .

equipping at a BSS site

6-16

68P02901W17-T
Jan 2010

Index

Cabinet (contd.)
equipping at a BSS site (contd.)
overview . . . . . . . . . . . . . . .
4-51
equipping at a remote BTS
example . . . . . . . . . . . . . . . .
7-36
equipping using TTY . . . . . . . . . .
4-58
Horizon II macro and macro_ext . . . .
4-51
modifying for a PCU . . . . . . . . . .
6-16
TCU/CTU
deleting . . . . . . . . . . . . . . . .
7-39
unequipping . . . . . . . . . . . . .
7-39
Cabinet Detailed View
description of fields . . . . . . . . . . .
4-54
grouping
General . . . . . . . . . . . . . . . .
4-57
Identification . . . . . . . . . . . . .
4-55
State . . . . . . . . . . . . . . . . .
4-56
Cage
configuring . . . . . . . . . . . . . . .
4-59
creating
using OMC-R GUI . . . . . . . . . . .
4-59
displaying for a PCU . . . . . . . . . .
6-17
equipping at a BSS site
overview . . . . . . . . . . . . . . .
4-51
equipping at a remote BTS
example . . . . . . . . . . . . . . . .
7-36
equipping from TTY interface . . . . . .
4-61
modifying for a PCU . . . . . . . . . .
6-17
Cage Detailed View
description of fields . . . . . . . . . . .
4-59
grouping
Identification . . . . . . . . . . . . .
4-60
State . . . . . . . . . . . . . . . . .
4-60
Calibrating DRIs
creating a standard configuration . . . .
9-84
from the OMC-R . . . . . . . . . . . .
9-93
managing existing standard configurations . . . . . . . . . . . . . . . . . .
9-99
Call Success Monitor
detecting sleeping devices . . . . . . .
14-4
Call trace
configuring flow control
using TTY interface . . . . . . . . . .
2-65
displaying flow control
using TTY interface . . . . . . . . . .
2-66
flow control . . . . . . . . . . . . . 2-63, 2-65
flow control parameters. . . . . . . . .
2-63
logfile names . . . . . . . . . . . . . .
2-61
MSC initiated IMSI and IMEI call
trace . . . . . . . . . . . . . . . . . .
2-60
using to detect network problems. . . . 14-14
call_trace_options . . . . . . . . . . . . .
2-60
calls
barring at a site
using TTY interface . . . . . . . . . .
7-55
cbc_intface_vers . . . . . . . 2-46, 2-49 to 2-50
cbc_vbind_cntr . . . . . . . . 2-46, 2-49 to 2-50
CBCH

68P02901W17-T
Jan 2010

CBCH (contd.)
enabling/disabling
using TTY interface . . . . . . . . . .
2-51
CBL
configuring . . . . . . . . . . . . . . .
9-43
creating
using OMC-R GUI . . . . . . . . . . .
9-43
equipping
using TTY interface . . . . . . . . . .
9-44
reassigning . . . . . . . . . . . . . . .
9-14
CBL Detailed View
description of fields . . . . . . . . . . .
9-43
grouping
Identification . . . . . . . . . . . . .
9-44
State . . . . . . . . . . . . . . . . .
9-44
CBL feature . . . . . . . . . . . . . . . . 2-145
parameters . . . . . . . . . . . . . . . 2-145
cbs_outage_cntr. . . . . . . . 2-46, 2-49 to 2-50
ccch_conf parameter . . . . . . . . . . . 8-226
CELL Detailed View
description of fields . . . 8-14, 8-48, 8-63, 8-70
editing . . . . . . . . . . . . . . . . .
8-89
grouping . . . . . . . . . . . . . . 8-15, 8-64
Adaptive Handovers. . . . . . . . . .
8-51
AMR Full Rate . . . . . . . . . . . .
8-33
AMR/GSM Half Rate . . . . 8-39, 8-46, 8-60
Cell Selection - Reseletcion . . . . . .
8-20
Channel Allocation - Deallocation . . .
8-25
Channel Mode Usage (AMR Full Rate & Half
Rate/GSM Half Rate) . . . . . . . . .
8-32
Coincident Multiband Handover . . .
8-32
Concentric and Dualband Cells . . . .
8-28
Congestion Relief . . . . . . . . . . .
8-26
Directed Retry . . . . . . . . . . . .
8-28
Distance Handover . . . . . . . . . .
8-57
Downlink Interference Handover . . .
8-57
Downlink Power Control . . . . . . .
8-65
Downlink Rxlev Handover. . . . . . .
8-56
Downlink RxQual Handover . . . . . .
8-54
Flow Control . . . . . . . . . . . . .
8-24
GPRS . . . . . . . . . . . . . . . . .
8-70
Handover - General . . . . . . . . . .
8-48
Handover Thresholds . . . . . . . . .
8-50
Handover Timer. . . . . . . . . . . .
8-51
Handover Types Allowed . . . . . . .
8-51
Handover-AMR Full Rate . . . . . . .
8-60
Identification . . . . . . . . . . . 8-14, 8-97
Inter-RAT Handover. . . . . . . . . .
8-59
Multiband Handover . . . . . . . . .
8-29
Network Controlled Cell Reselection . . . . . . . . . . . . . . . . . .
8-77
Power Budget Handover . . . . . . .
8-58
Power Control - AMR Full Rate . . . .
8-67
Power Control - AMR/GSM Half
Rate. . . . . . . . . . . . . . . . . .
8-68
Power Control - General . . . . . . .
8-63
Quality of Service . . . . . . . . . . .
8-78
Queuing. . . . . . . . . . . . . . . .
8-23

IX-5

Index

CELL Detailed View (contd.)

grouping (contd.)
Radio Channel Configuration . . . . .
8-21
Radio Link Control . . . . . . . . . .
8-26
SDCCH Handover . . . . . . . . . . .
8-59
State . . . . . . . . . . . . . . . . .
8-15
System Access . . . . . . . . . . . .
8-19
Uplink Interference Handover . . . .
8-56
Uplink Power Control . . . . . . . . .
8-64
Uplink Rxlev Handover . . . . . . . .
8-55
Uplink RxQual Handover . . . . . . .
8-52
overview of using . . . . . . . . . . . .
8-11
propagating parameters . . . . . . . .
8-89
scope of propagation . . . . . . . . . .
8-79
Cell parameters
changing LAC and/or CI. . . . . . . . . 8-242
changing number of SDCCHs . . . . . . 8-226
flexible neighbour cell processing. . . . 8-195
General . . . . . . . . . . . . . . . . .
8-14
GPRS . . . . . . . . . . . 8-70, 8-208, 8-211
Handover . . . . . . . . . . . . . . . .
8-48
Power Control. . . . . . . . . . . . . .
8-63
propagating
from OMC-R GUI . . . . . . . . . . .
1-50
cell_bar_access_switch . . . . . . . . . . 8-239
Cell-X-Export . . . . . . . . . . . . . 12-3, 12-9
Cell-X-Import . . . . . . . . . . . . 12-4, 12-17
troubleshooting . . . . . . . . . . . . . 12-52
cell_zone . . . . . . . . . . . . . . . . .
2-34
Cells
adaptive handovers . . . . . . . . . . . 8-190
at a neighbour cell . . . . . . . . . . 8-185
adding . . . . . . . . . . . . . . . 8-10, 8-70
defining General parameters . . . . .
8-14
defining GPRS parameters . . . . . .
8-70
defining handover parameters . . . .
8-48
defining Power Control parameters . .
8-63
methods of . . . . . . . . . . . . . . . 8-5
recommended procedure . . . . . . . . 8-6
using copy/change . . . . . . . . . . . 8-8
using OMC-R GUI . . . . . . . . . . .
8-11
using TTY interface . . . . . . . . . .
8-10
barring calls . . . . . . . . . . . . . . 8-239
changing LAC-CI . . . . . . . . . . . . 8-242
changing number of SDCCHs . . . . . . 8-226
checking for frequency hopping configuration . . . . . . . . . . . . . . . 8-178, 15-54
using cmutil. . . . . . . . . . 8-178, 15-54
using OMC-R GUI . . . . . . . . . . . 8-178
coincident multiband handover . . . . . 8-181
concentric. . . . . . . . . . . . . . . .
2-30
configuring for dual band operation. . .
2-28
using TTY Interface . . . . . . . . . .
2-37
configuring for flexible neighbour cell
processing . . . . . . . . . . . . . . . 8-195
configuring for handovers. . . . . . . . 8-185
configuring power control optimization . . . . . . . . . . . . . . . . . . . 8-203

IX-6

Cells (contd.)
configuring power control optimization (contd.)
parameters . . . . . . . . . . . . . . 8-204
using the TTY . . . . . . . . . . . . . 8-205
configuring with BCCH and SDCCH in the
EGSM . . . . . . . . . . . . . . . . . . 8-179
using OMC-R GUI . . . . . . . . . . . 8-179
using TTY interface . . . . . . . . . . 8-180
containment. . . . . . . . . . . . . . .
9-34
creating
using CELL Detailed View . . . . . .
8-11
creating a neighbour . . . . . . . . . . 8-121
defining GPRS parameters . . . 8-207, 8-211
deleting . . . . . . . . . . . . . . . . .
8-92
using OMC-R GUI . . . . . . . . . . .
8-93
establishing a cell boundary . . . . . . 8-234
expanding capacity of . . . . . . . . . . 8-163
flexible neighbour cell processing. . . . 8-195
General parameter section . . . . . . .
8-14
GPRS parameter naming . . . . . . . .
8-70
GPRS parameter section . . . . . . . .
8-70
Handover parameter group . . . . . . .
8-48
Handover parameter section . . . . . .
8-48
modifying a neighbour . . . . . . . . . 8-130
modifying neighbours . . . . . . . . . . 8-130
modifying parameters
using OMC-R GUI . . . . . . . . . . .
8-13
multiband inter-cell handover . . . . . .
2-30
neighbour . . . . . . . . . . . . . . . . 8-106
ping-pong handovers . . . . . . . . . . 8-193
Power Control parameter group . . . .
8-63
Power Control parameter section . . . .
8-63
propagatable parameters . . . . . . . .
8-79
propagating . . . . . . . . . . . . . . .
8-89
reciprocal neighbours . . . . . . . . . . 8-107
setting all channels at full power . . . . 8-237
source object . . . . . . . . . . . . . . 8-106
viewing neighbours . . . . . . . . . . . 8-109
viewing reciprocals . . . . . . . . . . . 8-109
viewing sources . . . . . . . . . . . . . 8-109
CellXchange
command line utilities. . . . . . . . . . 12-43
configuration file . . . . . . . . . . . .
12-6
defining parameters for import/export . . . . . . . . . . . . . . . . . . . 12-28
deleting Backup files . . . . . . . . . .
12-8
export/import files . . . . . . . . . . .
12-5
import and export parameter tables . . 12-53
introduction . . . . . . . . . . . . . . .
12-5
log files . . . . . . . . . . . . . . . . .
12-7
overview . . . . . . . . . . . . . . . .
12-3
Radio Frequency Planning . . . . . . .
12-5
using the command line . . . . . . . . . 12-35
defining environment variables . . . . 12-35
CERM
enhanced . . . . . . . . . . . . . . . .
2-70
Changing a BSIC . . . . . . . . . . . . . 8-219
Changing frequency

68P02901W17-T
Jan 2010

Index

Changing frequency (contd.)

BCCH carrier frequency
using OMC-R GUI . . . . . . . . . . . 8-213
non-BCCH carrier frequency . . . . . . 8-216
Changing LAC-CI
of cells . . . . . . . . . . . . . . . . . 8-242
of proxy cells . . . . . . . . . . . . . . 8-160
Changing NE ID
an Assoc_BSS
log files . . . . . . . . . . . . . . . .
4-81
resuming a suspended process . . . .
4-88
an Assoc_RXCDR
log files . . . . . . . . . . . . . . . .
4-81
resuming the suspended process . . .
4-88
of an Assoc_BSS. . . . . . . . . . . . .
4-80
of an Assoc_RXCDR . . . . . . . . . . .
4-80
Changing security levels . . . . . . . . .
1-43
Changing the number of allocated SDCCHs . . . . . . . . . . . . . . . . . . . . 8-226
Changing the transmit power for a BTS . . 8-234
Channel status
displaying . . . . . . . . . . . . . . . .
9-20
Channel Status form . . . . . . . . . . .
9-24
channel_reconfiguration_switch parameter . . . . . . . . . . . . . . . . . . . . 8-226
Checking and changing current network
status . . . . . . . . . . . . . . . . . . .
14-5
Checking connectivity
BSS to RXCDR . . . . . . . . . . . . . . 5-2
Path . . . . . . . . . . . . . . . . . . . 9-174
RXCDR to MSC . . . . . . . . . . . . . . 5-2
RXCDR/BSS to OMC-R (OML) . . . . . .
5-15
Checking device type
using cmutil . . . . . . . . . . . . . . .
7-58
Checking for and rectifying database
errors . . . . . . . . . . . . . . . . . . . 14-11
Checking for and rectifying hardware
defects . . . . . . . . . . . . . . . . . . 14-10
Checking for and rectifying OOS devices . . . . . . . . . . . . . . . . . . .
14-9
Checking frequency hopping configuration for
cells . . . . . . . . . . . . . . . . . . . . 8-178
using cmutil . . . . . . . . . . . 8-178, 15-54
using OMC-R GUI . . . . . . . . . . . . 8-178
Checking FRU . . . . . . . . . . . . . .
9-10
Checking GCLK synchronization for a
SITE . . . . . . . . . . . . . . . . . . .
7-52
Checking hardware
at a single SITE . . . . . . . . . . 7-57, 15-27
at each SITE . . . . . . . . . . . . . .
7-56
using OMC-R GUI . . . . . . . . . . .
7-56
using TTY interface . . . . . . . . . .
7-56
at multiple SITEs
using TTY interface and scripting . . .
7-56
Checking hardware version . . . . . . . .
9-10
Checking input file syntax
using cmutil . . . . . . . . . . . . . . . 15-18
Checking key SITE parameters . . . . . .
7-59

68P02901W17-T
Jan 2010

Checking OMLs
for a single NE
using OMC-R GUI . . . . . . . . . . .
5-15
for multiple NEs
using SQL . . . . . . . . . . . . . . .
5-15
Checking PCU
using cmutil . . . . . . . . . . . . 7-57, 15-27
Checking RXCDR/BSS to OMC-R connectivity . . . . . . . . . . . . . . . . . . . . .
5-15
Checking serial number . . . . . . . . . .
9-10
Checking SITE or NE
analysis or parsing . . . . . . . . 7-57, 15-23
using cmutil . . . . . . . . . . . . 7-57, 15-27
Checking software version
for a BSS . . . . . . . . . . . . . . . . 4-108
for a single NE
using cmutil. . . . . . . . . . 4-109, 15-26
using OMC-R GUI . . . . . . . . . . . 4-108
for an OMC-R . . . . . . . . . 4-108 to 4-109
for an RXCDR . . . . . . . . . . . . . . 4-108
for BSSs/RXCDRs/OMCs . . . . . . . . 4-108
for multiple NEs
using cmutil. . . . . . . . . . 4-109, 15-27
using OMC-R GUI . . . . . . . . . . . 4-109
checkvalidLockPID utility . . . . . . . . .
1-19
chg_A5_alg_pr command
using for wide area modifications . . . .
1-49
chg_acs_params. . . . . . . . . . . . . . 2-139
chg_csfp command . . . . . . . . . . . .
9-58
chg_eas_alarm command . . . . 9-103 to 9-104
chg_element command
use in configuring sites . . . . . . . . .
7-34
using the all parameter . . . . . . . . .
1-49
chg_lac_ci . . . . . . . . . . . . . . . . . 12-50
chg_smsch_msg . . . . . . . . . . . . . .
2-51
chg_ts_usage . . . . . . . . . . . . . . . . 5-3
chg_ts_usage free . . . . . . . . . . . . .
5-24
chg_ts_usage nail . . . . . . . . . . . . .
5-25
chg_ts_usage nail_path . . . . . . . . . .
5-25
chg_ts_usage reserve . . . . . . . . . . .
5-24
chg_ts_usage_free_path . . . . . . . . . .
5-24
CIC
blocking and validation . . . . . . . . .
2-12
configuring
using TTY interface . . . . . . . . . .
9-46
displaying information for
using TTY interface . . . . . . . . . .
9-47
equipping
using TTY interface . . . . . . . . . .
9-46
validation . . . . . . . . . . . . . . . .
2-12
with transcoding resources
displaying . . . . . . . . . . . . . . . 9-144
cic_block_thresh
changing . . . . . . . . . . . . . . . .
4-77
cic_unblock_thresh
changing using TTY interface . . . . . .
4-77
cic_validation . . . . . . . . . . 2-12, 2-14, 4-76
Circuit status

IX-7

Index

Circuit status (contd.)

displaying . . . . . . . . . .
Circuit Status form . . . . . .
cmutil
adding a BSS . . . . . . . .
adding objects . . . . . . .
ASCII file content . . . . . .
ASCII file rules . . . . . . .
ASCII files
object definition. . . . . .
changing NE connections . .
changing NE details. . . . .
checking input file syntax . .
command syntax . . . . . .
common operations . . . . .
deleting objects . . . . . . .
deleting/adding CommLinks
dump mode . . . . . . . . .
dumping CM MIB . . . . . .
extract mode . . . . . . . .
extracting data from the MIB
to 15-25
examples . . . . . . . . .
general syntax . . . . . . .
hierarchical dump mode . .
logging in . . . . . . . . . .
overview . . . . . . . . . .
Path output
comparison with TTY . . .
populating new MIB . . . .
primary arguments . . . . .
purpose . . . . . . . . . . .
reparenting RXCDR . . . . .
script files. . . . . . . . . .
status messages. . . . . . .
update mode . . . . . . . .
updating objects . . . . . .
use with maps. . . . . . . .
using to
add, delete, modifying data
manage Regions . . . . .
using to modify devices and
tions . . . . . . . . . . . .
Coding Schemes
configuring . . . . . . . . .
using OMC-R GUI . . . . .
GPRS and EGPRS . . . . . .
coincident multiband handover
configuring . . . . . . . . .
using OMC-R GUI . . . . .
using TTY interface . . . .
overview . . . . . . . . . .
parameters . . . . . . . . .
coincident_cell parameter. . .
coincident_mb. . . . . . . . .
coincident_mb parameter . . .
coincident_offset parameter .

IX-8

. . . . . .
. . . . . .

9-20
9-20

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

. 15-19
. 15-18
.
15-7
. 15-10

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

. 15-26
.
15-5
.
15-6
.
15-3
.
15-2

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

15-12
15-36
15-21
15-18
15-5
15-51
15-20
15-36
15-5
15-52
15-5
15-24

15-41
15-51
15-5
15-2
4-106
15-17
15-16
15-5
15-21
15-44

. . . . . . 15-18
. . . . . . 15-52
func. . . . . . 15-22
. . . . . .
. . . . . .
. . . . . .
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.

2-39
2-43
2-39

. . . 8-181
. . . 8-183
. . . 8-183
. . . 8-181
. . . 8-181
8-181, 8-183
. . 2-31, 2-33
8-181, 8-183
8-181, 8-183

Collecting information about the current

network . . . . . . . . . . . . . . . . . .
14-8
colocated_dris. . . . . . . . . . . . 2-16 to 2-17
COMB. . . . . . . . . . . . . . . . . . .
9-49
configuring . . . . . . . . . . . . . . .
9-49
creating
using OMC-R GUI . . . . . . . . . . .
9-51
displaying details
using TTY interface . . . . . . . . . .
9-53
DRI-COMB configuration . . . . . . 9-51, 9-65
equipping
using TTY interface . . . . . . . . . .
9-53
parameters . . . . . . . . . . . . . . .
9-52
COMB Detailed View
description of fields . . . . . . . . . . .
9-52
grouping
Identification . . . . . . . . . . . . .
9-52
State . . . . . . . . . . . . . . . . .
9-53
Command partitioning
using OMC-R GUI . . . . . . . . . . . . . 1-5
Commslink . . . . . . . . . . . . . . . . . 5-3
adding . . . . . . . . . . . . . . . . . 13-11
using cmutil. . . . . . . . . . . . . . 15-36
adding to a map . . . . . . . . . . . . . 13-11
adding using cmutil . . . . . . . 13-12, 15-49
autocreation/autodeletion . . . . . . . .
5-10
configuring
using OMC-R GUI . . . . . . . . . . .
5-10
creating
using OMC-R GUI . . . . . . . . . . .
5-10
deleting . . . . . . . . . . . . . 15-36, 15-50
using cmutil. . . . . . . . . . . . . . 13-13
using OMC-R GUI . . . . . . . . . . .
5-14
filtering . . . . . . . . . . . . . . . . .
5-13
outputting to a file . . . . . . . . . . . 15-17
CommsLink Detailed View
description of fields . . . . . . . . . . .
5-12
grouping
CommsLink Related Devices . . . . .
5-13
Identification . . . . . . . . . . . . .
5-13
Map Information . . . . . . . . . . .
5-13
Concentric cells feature . . . . . . . . . .
2-30
Configuration Management
recommendations . . . . . . . . . . . . . 1-2
Configuring a BSS/RXCDR
deleting BSS/RXCDR . . . . . . . . . .
4-44
deleting at MUX . . . . . . . . . . .
4-48
deleting at packet switch . . . . . . .
4-48
Configuring a cage . . . . . . . . . . . .
4-59
Configuring a cell
adding
using TTY interface . . . . . . . . . .
8-10
for adapative handovers . . . . . . . . 8-185
for adaptive handovers . . . . . . . . . 8-188
using TTY interface . . . . . . . . . . 8-188
for coincident multiband handover
using OMC-R GUI . . . . . . . . . . . 8-183
using TTY interface . . . . . . . . . . 8-183

68P02901W17-T
Jan 2010

Index

Configuring a cell (contd.)

for coincident multiband handovers. .
using TTY interface . . . . . . . . .
for dual band operation . . . . . . . .
overview . . . . . . . . . . . . . .
using TTY interface . . . . . . . . .
for extended cell range prioritization .
using OMC-R GUI . . . . . . . . . .
using TTY interface . . . . . . . . .
for flexible neighbour cell processing .
using OMC-R GUI . . . . . . . . . .
using TTY interface . . . . . . . . .
for GPRS
using TTY interface . . . . . . . . .
for multiple GPRS carriers . . . . . .
for power control optimization . . . .
using the OMC-R GUI . . . . . . . .
using TTY interface . . . . . . . . .
with BCCH and SDCCH in the EGSM .
Configuring a CIC . . . . . . . . . . . .
Configuring a COMB . . . . . . . . . .
Configuring a CommsLink
using OMC-R GUI . . . . . . . . . . .
Configuring a CSFP . . . . . . . . . . .
Configuring a DHP device. . . . . . . .
Configuring a DPROC
using OMC-R GUI . . . . . . . . . . .
Configuring a DRI . . . . . . . . . . . .
Configuring a DSW
overview . . . . . . . . . . . . . . .
Configuring a DYNET . . . . . . . . . .
using the TTY interface . . . . . . . .
Configuring a DYNETGroup. . . . . . .
Configuring a GBL
using OMC-R GUI . . . . . . . . . . .
Configuring a GDS
using OMC-R GUI . . . . . . . . . . .
Configuring a GSL
using OMC-R GUI . . . . . . . . . . .
Configuring a KSW
overview . . . . . . . . . . . . . . .
Configuring a neighbour cell
for adaptive handovers . . . . . . . .
using OMC-R GUI . . . . . . . . . .
using TTY interface . . . . . . . . .
Configuring a Network instance
using OMC-R GUI . . . . . . . . . . .
Configuring a Path
using Path Configure menu option
overview . . . . . . . . . . . . . .
Configuring a PATH device . . . . . . .
Configuring a Path using Path Configure
option
initiating . . . . . . . . . . . . . . .
Configuring a PCU
devices
using OMC-R GUI . . . . . . . . . .
using TTY interface . . . . . . . . .

68P02901W17-T
Jan 2010

.
.
.
.
.
.
.
.
.
.
.

8-181
8-183
2-28
2-28
2-37
8-201
8-201
8-202
8-195
8-197
8-197

.
.
.
.
.
.
.
.

8-212
8-207
8-203
8-204
8-205
8-179
9-46
9-49

.
.
.

5-10
9-54
9-59

.
.

6-18
9-63

. 9-123
.
4-94
.
4-97
.
4-92
.

6-38

6-29

6-34

. 9-123
. 8-190
. 8-190
. 8-191
. .

3-2

. 11-73
. 9-162
menu
. 11-76

. . 6-8
.
6-52

Configuring a proxy cell. . . . . . . . . . 8-143

Configuring a PSP
using OMC-R GUI . . . . . . . . . . . .
6-22
Configuring a UTRAN neighbour . . . . . 8-135
Configuring a UTRAN proxy cell . . . . . 8-146
Configuring Advanced Load Management for
EGSM . . . . . . . . . . . . . . . . . . .
2-78
Configuring an Assoc_BSS . . . . . . . .
4-68
Configuring an Assoc_RXCDR . . . . . . .
4-72
Configuring an EAS . . . . . . . . . . . . 9-101
using TTY interface . . . . . . . . . . . 9-111
Configuring an LCF . . . . . . . . . . . . 9-127
Configuring an LMTL device . . . . . . . 9-131
Configuring an MSC . . . . . . . . . . . . 3-7
Configuring an MSI . . . . . . . . . . . . 9-137
Configuring an MTL. . . . . . . . . . . . 9-152
Configuring an NSVC
using OMC-R GUI . . . . . . . . . . . .
6-43
Configuring an OMC-R . . . . . . . . . . . 3-7
Configuring an OMF . . . . . . . . . . . 9-158
using OMC-R GUI . . . . . . . . . . . . 9-158
Configuring an OML . . . . . . . . . . . 9-160
Configuring an RSL device
overview . . . . . . . . . . . . . . . . 9-176
Configuring an RSL function
using Path Configure . . . . . . . . . . 11-73
Configuring an RTF function
overview . . . . . . . . . . . . . . . . 9-182
using Path Configure . . . . . . . . . . 11-73
Configuring an SGSN
using OMC-R GUI . . . . . . . . . . . .
6-49
Configuring an XBL
overview . . . . . . . . . . . . . . . . 9-197
Configuring call trace flow control . . . .
2-63
using OMC-R GUI
configuring using OMC-R GUI . . . .
2-65
using TTY interface . . . . . . . . . . .
2-65
Configuring devices/functions
recommendations
for individual . . . . . . . . . . . . . . 9-3
for multiple . . . . . . . . . . . . . . . 9-8
Configuring encryption algorithms . . . .
2-26
Configuring Enhanced Circuit Error Rate
Monitor . . . . . . . . . . . . . . . . . .
2-70
Configuring Enhanced GDP Provisioning . . . . . . . . . . . . . . . . . . . . 9-146
Configuring Enhanced GPRS One Phase Access
using OMC-R GUI . . . . . . . . . . . . 2-115
using TTY interface . . . . . . . . . . . 2-115
Configuring Enhanced Scheduling
using OMC-R GUI . . . . . . . . . . . . 2-148
using TTY interface . . . . . . . . . . . 2-148
Configuring enhanced SDCCH to TCH band
assignment . . . . . . . . . . . . . . . . 8-198
Configuring frequency hopping
overview . . . . . . . . . . . . . . . . 8-165
using OMC-R GUI . . . . . . . . . . . . 8-167
using TTY interface . . . . . . . . . . . 8-175

IX-9

Index

Configuring GPRS interleaving TBFs . .

methods of . . . . . . . . . . . . . .
Configuring Inter-RAT Handover
using OMC-R GUI . . . . . . . . . . .
using TTY interface . . . . . . . . . .
Configuring Location Services . . . . .
methods of . . . . . . . . . . . . . .
using TTY interface . . . . . . . . . .
Configuring MSC to BSS overload control . . . . . . . . . . . . . . . . . . .
using TTY interface . . . . . . . . . .
Configuring NCCR . . . . . . . . . . .
methods of . . . . . . . . . . . . . .
using TTY interface . . . . . . . . . .
Configuring networks
MIB . . . . . . . . . . . . . . . . . .
Configuring PCR
using OMC-R GUI . . . . . . . . . . .
Configuring SCR . . . . . . . . . . . .
methods of . . . . . . . . . . . . . .
using TTY interface . . . . . . . . . .
Configuring sites
adding a BTS
on-line . . . . . . . . . . . . . . .
using batch rlogin script . . . . . .
using copy_path command . . . . .
using TTY interface . . . . . . . . .
BSS links & control functions . . . . .
BSS topology and PATH limitations . .
BTS sites . . . . . . . . . . . . . . .
chg_element command . . . . . . . .
creating a SITE
using OMC-R GUI . . . . . . . . . .
defining site parameters
responsibilities . . . . . . . . . . .
hypothetical BSS site . . . . . . . . .
modify_value command . . . . . . . .
MSI & RSL restrictions . . . . . . . .
overview . . . . . . . . . . . . . . .
overview of methods . . . . . . . . .
PATH devices . . . . . . . . . . . . .
RSL considerations . . . . . . . . . .
RTF considerations . . . . . . . . . .
simplified network diagram . . . . . .
use of batch templates . . . . . . . .
using copy_path command
equipping a BTS site . . . . . . . .
Configuring SMS-CB
at a CELL
using OMC-R GUI . . . . . . . . . .
using OMC-R GUI . . . . . . . . . . .
using TTY interface . . . . . . . . . .
Configuring the MIB
using audit . . . . . . . . . . . . . .
Configuring the physical relay states
using TTY interface . . . . . . . . . .
Conn_Link
adding

IX-10

.
.

2-89
2-92

.
.
.
.
.

2-102
2-102
2-104
2-111
2-111

.
.
.
.
.

2-23
2-25
2-81
2-85
2-86

15-2

.
2-57
. 2-142
. 2-143
. 2-144

.
7-14
.
7-14
.
7-40
.
7-17
. . 7-2
. . 7-3
. . 7-1
.
7-34
.
.
.
.
.
.
.
.
.
.
.
.
.

7-26

.
.

.
.
.
.

7-12
7-3
7-34
7-5
7-34
7-34
7-3
7-7
7-6
7-2
7-14
7-21

. 8-244
.
2-48
.
2-48
.

10-2

. 9-112

Conn_Link (contd.)
adding (contd.)
using OMC-R GUI . . . . . . . . . . .
using TTY interface . . . . . . . . . .
autocreation/deletion of CommsLinks . .
creating
using OMC-R GUI . . . . . . . . . . .
deleting . . . . . . . . . . . . . . . . .
using OMC-R GUI . . . . . . . . . . .
Conn_Link Detailed View
description of fields . . . . . . . . . . .
grouping
Connectivity Information . . . . . . .
Identification . . . . . . . . . . . . .
Connection report
displaying . . . . . . . . . . . . . . . .
Connectivity
checking BSS to RXCDR . . . . . . . .
checking Path . . . . . . . . . . . . . .
checking RXCDR to MSC . . . . . . . .
containee
definition . . . . . . . . . . . . . . . .
container
definition . . . . . . . . . . . . . . . .
Containment
MIB . . . . . . . . . . . . . . . . . . .
rules . . . . . . . . . . . . . . . . . .
Controlling an MSC call trace
using TTY interface . . . . . . . . . . .
COP
GLU tool . . . . . . . . . . . . . . . .
copy_cell command . . . . . . . . . . . .
Copying a cell . . . . . . . . . . . . . . .
Copying a Site in a daisy chain configuration . . . . . . . . . . . . . . . . . . . .
Copying and pasting a BTS . . . . . . . .
correct_rtfs . . . . . . . . . . . . . . . .
Creating
network objects . . . . . . . . . . . . .
Creating a BSP
using OMC-R GUI . . . . . . . . . . . .
Creating a BSS
creating a cabinet
using the OMC-R GUI . . . . . . . . .
using the OMC-R GUI . . . . . . . . . .
Creating a BSS/RXCDR database . . . . .
Creating a BTP
from the OMC-R GUI . . . . . . . . . .
Creating a CBL
using OMC-R GUI . . . . . . . . . . . .
Creating a cell
defining General parameters
using OMC-R GUI . . . . . . . . . . .
defining GPRS parameters
using OMC-R GUI . . . . . . . . . . .
defining Handover parameters
using OMC-R GUI . . . . . . . . . . .
defining Power Control parameters

.
.

5-5
5-7
5-10

.
.
.

5-5
5-8
5-7

5-5

.
.

5-6
5-6

5-2

. 5-2
9-174
. 5-2
15-3
15-3
1-12
1-13
2-60

.
.

1-10
8-8
8-8

11-45
11-6
12-47
1-32
9-35

4-54
4-6
4-41
9-40
9-43

8-14
8-70
8-48

68P02901W17-T
Jan 2010

Index

Creating an OML
using OMC-R GUI . . . . . . . . . .
Creating an RSL at a Site . . . . . . .
Creating an RSL device
from the OMC-R GUI . . . . . . . .
Creating an RTF . . . . . . . . . . .
using OMC-R GUI . . . . . . . . . .
Creating an RTF at a Site
using Path Configure menu option .
Creating an RXCDR
using the OMC-R GUI . . . . . . . .
Creating an RXCDR cabinet
using the OMC-R GUI . . . . . . . .
Creating an RXCDR cage
using the OMC-R GUI . . . . . . . .
Creating an XBL
using OMC-R GUI . . . . . . . . . .
Creating multiple devices or functions
recommendation . . . . . . . . . .
Creating network objects
general description and procedure .
using cmutil . . . . . . . . . . . . .
CS3/CS4
description . . . . . . . . . . . . .
cs34Opt . . . . . . . . . . . . . . . .
CSFP
creating
using OMC-R GUI . . . . . . . . .
definition . . . . . . . . . . . . . .
equipping
using TTY interface . . . . . . . .
methods of creating . . . . . . . . .
parameters . . . . . . . . . . . . .
slot and cage restrictions . . . . . .
stealing algorithm. . . . . . . . . .
unconfiguring
using OMC-R GUI . . . . . . . . .
CSFP Detailed View
description of fields . . . . . . . . .
grouping
Identification . . . . . . . . . . .
State . . . . . . . . . . . . . . .
ct_fc_lo_level
ct_fc_hi_level . . . . . . . . . . . .
CTP
using to detect network problems. .
CTP NT tool . . . . . . . . . . . . . .
CTU2 radio
in Horizon II . . . . . . . . . . . .
Current Bucket Level feature
see CBL feature . . . . . . . . . . .

Creating a cell (contd.)

defining Power Control parameters (contd.)
using OMC-R GUI . . . . . . . .
using CELL Detailed View
overview . . . . . . . . . . . .
Creating a COMB
using OMC-R GUI . . . . . . . . .
Creating a Conn_Link
using OMC-R GUI . . . . . . . . .
Creating a DRI
from the OMC-R GUI . . . . . . .
Creating a DSW
using OMC-R GUI . . . . . . . . .
Creating a DYNET
using the OMC-R GUI . . . . . . .
using the TTY interface . . . . . .
Creating a DYNETGroup
using the OMC-R GUI . . . . . . .
using the TTY interface . . . . . .
Creating a GCLK
using OMC-R GUI . . . . . . . . .
Creating a GPROC
using OMC-R GUI . . . . . . . . .
Creating a KSW
using OMC-R GUI . . . . . . . . .
Creating a Path
using Path Configure menu option
Creating a PATH device
using the OMC-R GUI . . . . . . .
Creating a proxy cell
using OMC-R GUI . . . . . . . . .
Creating a single device or function
recommendation . . . . . . . . .
Creating a standard configuration
for DRI calibration . . . . . . . .
Creating a UTRAN proxy cell
using OMC-R GUI . . . . . . . . .
Creating an Assoc_BSS
using TTY interface . . . . . . . .
Creating an Assoc_RXCDR
using OMC-R GUI . . . . . . . . .
using TTY interface . . . . . . . .
Creating an EAS
using OMC-R GUI . . . . . . . . .
Creating an LCF
using OMC-R GUI . . . . . . . . .
Creating an LMTL device
using OMC-R GUI . . . . . . . . .
using TTY interface . . . . . . . .
Creating an MTL
using OMC-R GUI . . . . . . . . .

. . .

8-63

. . .

8-11

. . .

9-51

. . . .
. . .

5-5
9-68

. . . 9-124
. . .
. . .

4-94
4-97

. . .
. . .

4-92
4-93

. . . 9-113
. . . 9-117
. . . 9-124
. . . 11-80
. . . 9-167
. . . 8-143
. . . .
. . .

9-3
9-84

. . . 8-146
. . .

4-70

. . .
. . .

4-72
4-76

. . . 9-106
. . . 9-127
. . . 9-132
. . . 9-133
. . . 9-152

. . 9-160
. . 11-93
. . 9-177
. . 9-185
. . 9-185
. . 11-92
. .

4-39

. .

4-62

. .

4-64

. . 9-198
. . .

9-8

. .
. .

1-26
15-2

. .
. .

2-39
2-40

. .
. .

9-56
9-54

. .
. .
. .
. .
9-54,

9-57
9-54
9-55
9-54
9-56

. .

9-57

. .

9-55

. .
. .

9-55
9-56

. .

2-64

. . 14-14
. . 14-14
. . .

7-9

. . 2-145

D
DARBC . . . . . . . . . . . . . . . . . .
2-13
Auto-connect mode . . . . . . . . . 2-12, 2-14

68P02901W17-T
Jan 2010

IX-11

Index

DARBC (contd.)
Backwards Compatibility (Static)
mode . . . . . . . . . . . . . . . . . .
2-12
Backwards Compatibility mode . . . . .
2-14
DataGen . . . . . . . . . . . . . . . . .
12-2
Defining algorithms . . . . . . . . . . . .
8-94
Defining CellXchange parameters
from the GUI . . . . . . . . . . . . . . 12-28
Defining EAS alarms in the alarm table
using TTY interface . . . . . . 9-103 to 9-104
del_conn . . . . . . . . . . . . . . . . . . 5-8
del_neighbor command
using the all parameter . . . . . . . . .
1-49
del_smscb_msg . . . . . . . . . . . . . .
2-52
Delayed Uplink TBF release. . . . . . . .
2-90
deleteLocal attribute . . . . . . . . . . . 15-20
Deleting
device and functions
using OMC-R GUI . . . . . . . . . . . . 9-6
using TTY interface . . . . . . . . . . . 9-6
network objects . . . . . . . . . . . . .
1-37
TCU/CTU cabinets at M-Cell and Horizonmacro
sites. . . . . . . . . . . . . . . . . . .
7-39
Deleting a BTS . . . . . . . . . . . . . . 11-34
Deleting a cell
Deleting cells . . . . . . . . . . . 8-92 to 8-93
Deleting a Conn_Link
using OMC-R GUI . . . . . . . . . . . . . 5-7
Deleting a device from a Site
using Path Configure menu option . . . 11-91
Deleting a DYNET
using the OMC-R GUI . . . . . . . . . .
4-97
Deleting a DYNETGroup
using OMC-R GUI . . . . . . . . . . . .
4-93
Deleting a map link
using cmutil . . . . . . . . . . . 13-13, 15-50
using OMC-R GUI . . . . . . . . . . . . 13-12
Deleting a map node . . . . . . . . . . .
13-8
Deleting a network object
using OMC-R GUI . . . . . . . . . . . .
1-37
Deleting a Path
deleting devices
using Path Configure menu option . . 11-81
using Path Configure menu option . . . 11-81
Deleting a PATH device
recommended method . . . . . . . . . 9-170
Deleting a proxy cell
using OMC-R GUI . . . . . . . . . . . . 8-145
Deleting a Site in a daisy chain configuration . . . . . . . . . . . . . . . . . . . . 11-38
Deleting a UTRAN proxy cell
using OMC-R GUI . . . . . . . . . . . . 8-149
Deleting an Assoc_BSS
using the OMC-R GUI . . . . . . . . . .
4-70
using the TTY interface . . . . . . . . .
4-71
Deleting an Assoc_RXCDR
using OMC-R GUI . . . . . . . . . . . .
4-79
using TTY interface . . . . . . . . . . .
4-79

IX-12

Deleting an RTF
exporting incoming neigbours . . .
using OMC-R GUI . . . . . . . . . .
Deleting an XBL
from an Assoc_RXCDR/Assoc_BSS
using OMC-R GUI . . . . . . . . .
Deleting BSC-RXCDR connectivity
using del_conn command . . . . . .
using OMC-R GUI . . . . . . . . . .
using TTY interface . . . . . . . . .
Deleting multiple devices or functions
recommendations . . . . . . . . . .
Deleting neighbours
multiple
using del_nei utility . . . . . . . .
using del_neighbour command . .
using the Navigation Tree. . . . . .
Deleting network objects
general description and procedure .
using cmutil . . . . . . . . . . . . .
Detailed Views
algorithms . . . . . . . . . . . . .
Assoc_BSS . . . . . . . . . . . . .
Assoc_RXCDR . . . . . . . . . . . .
BSP . . . . . . . . . . . . . . . . .
BSS . . . . . . . . . . . . . . . . .
BTP . . . . . . . . . . . . . . . . .
Cabinet . . . . . . . . . . . . . . .
Cage . . . . . . . . . . . . . . . .
CBL . . . . . . . . . . . . . . . . .
CELL
General . . . . . . . . . . . . . .
GPRS . . . . . . . . . . . . . . .
Handover . . . . . . . . . . . . .
Power Control. . . . . . . . . . .
closing . . . . . . . . . . . . . . .
COMB. . . . . . . . . . . . . . . .
CommsLink . . . . . . . . . . . . .
Conn_Link. . . . . . . . . . . . . .
creating . . . . . . . . . . . . . . .
CSFP . . . . . . . . . . . . . . . .
deleting . . . . . . . . . . . . . . .
description . . . . . . . . . . . . .
DHP. . . . . . . . . . . . . . . . .
displaying OMC-R or BSS names . .
DPROC . . . . . . . . . . . . . . .
DRI . . . . . . . . . . . . . . . . .
DYNET . . . . . . . . . . . . . . .
DYNETGroup . . . . . . . . . . . .
EAS . . . . . . . . . . . . . . . . .
editing . . . . . . . . . . . . . . .
example in Edit mode . . . . . . . .
FreqHopSys. . . . . . . . . . . . .
GCLK . . . . . . . . . . . . . . . .
GPROC . . . . . . . . . . . . . . .
KSW . . . . . . . . . . . . . . . .
KSWpair . . . . . . . . . . . . . .
LCF . . . . . . . . . . . . . . . . .

. . 9-195
. . 9-193

. . 9-200
. . .
. . .
. . .

5-8
5-7
5-8

. . .

9-9

. . 8-132
. . 8-132
. . 8-131
. .
1-26
. . 15-20
.
.
.
.
.
.
.
.
.

.
8-96
.
4-69
.
4-73
.
9-36
. . 4-8
.
9-40
.
4-54
.
4-59
.
9-43

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

8-14
8-70
8-48
8-63
1-32
9-52
5-12
. 5-5
1-32
9-55
1-37
1-30
9-60
1-30
6-19
9-68
4-95
4-92
9-108
1-34
1-36
8-171
9-114
9-117
9-124
9-120
9-128

68P02901W17-T
Jan 2010

Index

Detailed Views (contd.)

MSC . . . . . . . . . . . . . .
MSI . . . . . . . . . . . . . . .
MTL. . . . . . . . . . . . . . .
navigating to . . . . . . . . . .
Neighbour . . . . . . . . . . .
Network . . . . . . . . . . . .
OMC . . . . . . . . . . . . . .
OMF . . . . . . . . . . . . . .
OML . . . . . . . . . . . . . .
PATH . . . . . . . . . . . . . .
PCU . . . . . . . . . . . . . . .
PCU GBL . . . . . . . . . . . .
PCU GDS . . . . . . . . . . . .
PCU GSL . . . . . . . . . . . .
PCU MSI . . . . . . . . . . . .
PCU NSVC . . . . . . . . . . .
PCU PSP . . . . . . . . . . . .
Proxycell . . . . . . . . . . . .
reverting to saved information .
RSL . . . . . . . . . . . . . . .
RTF . . . . . . . . . . . . . . .
saving . . . . . . . . . . . . . .
SGSN . . . . . . . . . . . . . .
SITE . . . . . . . . . . . . . .
SMSCBmsg . . . . . . . . . . .
using . . . . . . . . . . . . . .
UTRAN Blind Search Neighbour
UTRAN Proxycell . . . . . . . .
devices
creating individual . . . . . . .
recommendation . . . . . . .
creating multiple
recommendation . . . . . . .
deleting
using TTY interface . . . . . .
deleting from a Site . . . . . . .
deleting multiple
recommendations . . . . . . .
displaying
using OMC-R GUI . . . . . . .
using TTY interface . . . . . .
equipping
using TTY interface . . . . . .
hierarchy . . . . . . . . . . . .
methods for configuring
individual . . . . . . . . . . .
multiple . . . . . . . . . . . .
modifying
using OMC-R GUI . . . . . . .
using TTY interface . . . . . .
modifying multiple . . . . . . .
using batch rlogin. . . . . . .
using cmutil. . . . . . . . . .
reassigning on a primary Path .
tracking . . . . . . . . . . . . .
unassigning from a Path . . . .
unequipping

68P02901W17-T
Jan 2010

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

. 3-7
9-139
9-152
1-32
8-121
. 3-3
. 3-7
9-158
9-160
9-167
. 6-9
6-39
6-31
6-35
6-25
6-44
6-22
8-143
1-34
9-177
9-185
1-32
6-50
7-27
8-244
1-30
8-140
8-146

. . . . .
. . . . .

9-3
9-3

. . . . .

9-8

. . . 9-4, 9-6
. . . . 11-91
. . . . .

9-9

. . . . .
. . . . .

9-5
9-5

. . . . . 9-4
. . . .
9-29
. . . . .
. . . . .
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

9-3
9-8

. 9-4
. 9-5
. 9-8
. 9-8
15-22
11-87
9-10
11-85

devices (contd.)
unequipping (contd.)
using TTY interface . . . . . . . . . . . 9-6
using OMC-R GUI . . . . . . . . . . . . . 9-6
DHP
at Horizonmicro2 and Horizoncompact2 . . . . . . . . . . . . . . . . . .
9-60
configuring . . . . . . . . . . . . . . .
9-59
creating
using OMC-R GUI . . . . . . . . . . .
9-60
definition . . . . . . . . . . . . . . . .
9-59
equipping
multiple devices. . . . . . . . . . . .
9-62
using TTY interface . . . . . . . . . .
9-62
parameters . . . . . . . . . . . . . . .
9-60
DHP Detailed View
description of fields . . . . . . . . . . .
9-60
grouping
Cage and Slot . . . . . . . . . . . . .
9-61
Identification . . . . . . . . . . . . .
9-61
State . . . . . . . . . . . . . . . . .
9-62
Directory structure
database . . . . . . . . . . . . . . . .
4-43
Disabling CIC validation
at an AXCDR
using TTY interface . . . . . . . . . .
4-76
disp_acs . . . . . . . . . . . . . . . . . . 2-138
disp_cbch_state . . . . . . . . . . . . . .
2-48
disp_conn . . . . . . . . . . . . . . . . 5-3, 5-8
disp_csfp command . . . . . . . . . . . .
9-58
disp_mms_ts_usage . . . . . . . . . . 4-98, 5-2
disp_relay_contact command . . . . . . . 9-112
disp_transcoding command . . . . . . . . 9-144
disp_version command . . . . . . . . . . 4-109
Displaying
device and function details . . . . . . . . 9-5
Displaying a PCU Cabinet . . . . . . . . .
6-16
Displaying a PCU Cage . . . . . . . . . .
6-17
Displaying a PCU MMS . . . . . . . . . .
6-27
Displaying an Assoc_BSS
using TTY interface . . . . . . . . . . .
4-71
Displaying an Assoc_RXCDR
using TTY interface . . . . . . . . . . .
4-76
Displaying BSC-BTS dynamic allocation details
at a BTS. . . . . . . . . . . . . . . . .
2-21
Displaying BSC-BTS dynamic allocation resources
using the TTY interface . . . . . . . . .
4-98
Displaying BSC-RXCDR connectivity
using disp_conn command . . . . . . . . 5-8
Displaying call trace flow control
using TTY interface . . . . . . . . . . .
2-66
Displaying DSW
using TTY interface . . . . . . . . . . . 9-126
Displaying EAS
using TTY interface . . . . . . . . . . . 9-111
Displaying KSW
using TTY interface . . . . . . . . . . . 9-126
Displaying LMTL loadsharing granularity

IX-13

Index

DSWX
definition . . . . . . . . . . . . . . . . 9-123
DTE X.121 addresses
assigning at NE . . . . . . . . . . . . .
5-19
assigning at OMC-R . . . . . . . . . . .
5-17
OMC-R addresses rules . . . . . . . . .
5-20
setting OML addresses . . . . . . . . .
5-19
slot:port settings for OMLs . . . . . . .
5-19
use of PC . . . . . . . . . . . . . . . .
5-19
Dual Band Cells feature
configuring . . . . . . . . . . . . . 2-28, 2-37
impact on DRIs and RTFs . . . . . 9-64, 9-182
parameters . . . . . . . . . . . . . . .
2-31
dual_band_offset . . . . . . . . . . 2-31 to 2-32
dualBandCellOpt . . . . . . . . . . . . .
2-31
dyn_step_adj . . . . . . . . . . . 8-203, 8-205
dyn_step_adj_fmpr
dyn_step_adj . . . . . . . . . . 8-203, 8-205
Dynamic allocation
of BSC-BTS terrestrial backing resources . . . . . . . . . . . . . . . . .
2-19
of RXCDR-BSC circuits . . . . . . . . .
2-13
Dynamic propagation
proxy cell data to OMC-Rs . . . . . . . 8-162
DYNET . . . . . . . . . . . . . . . . . .
2-19
configuring . . . . . . . . . . . . . 4-94, 4-97
creating . . . . . . . . . . . . . . . 4-94, 4-97
creating PATHs . . . . . . . . . . . . .
4-94
deleting . . . . . . . . . . . . . . . 4-97, 4-99
displaying . . . . . . . . . . . . . . . .
4-98
modifying . . . . . . . . . . . . . . . .
4-98
overview . . . . . . . . . . . . . . . .
4-90
path devices . . . . . . . . . . . . . . 9-163
viewing and editing . . . . . . . . . . .
4-97
DYNET Detailed View
description of fields . . . . . . . . . . .
4-95
grouping . . . . . . . . . . . . . 4-95 to 4-96
dynet_retry_time . . . . . . . . . . . . .
2-20
dynet_tchs_rsvd . . . . . . . . . . . . . .
2-20
DYNETGroup
configuring . . . . . . . . . . . . . . .
4-92
creating . . . . . . . . . . . . . . 4-92 to 4-93
deleting . . . . . . . . . . . . . . . . .
4-93
overview . . . . . . . . . . . . . . . .
4-90
restrictions . . . . . . . . . . . . . . .
4-91
DYNETGroup Detailed View
description of fields . . . . . . . . . . .
4-92
grouping . . . . . . . . . . . . . . . .
4-93

Displaying LMTL loadsharing granularity (contd.)

using TTY interface . . . . . . . . . . . 9-136
Displaying MTL loadsharing granularity
using TTY interface . . . . . . . . . . . 9-157
disuse_cnt_hreqave . . . . . . . . 8-195, 8-197
Double density DRI
introduction . . . . . . . . . . . . . . . . 7-9
Double density DRIs . . . . . . . . . . .
9-66
DPROC
configuring . . . . . . . . . . . . . . .
6-18
creating . . . . . . . . . . . . . . . . .
6-18
deleting . . . . . . . . . . . . . . . . .
6-21
modifying . . . . . . . . . . . . . . . .
6-20
types . . . . . . . . . . . . . . . . . .
6-18
DPROC Detailed View
description of fields . . . . . . . . . . .
6-19
grouping . . . . . . . . . . . . . 6-19 to 6-20
DRI
configuring . . . . . . . . . . . . . . .
9-63
creating . . . . . . . . . . . . . . . 9-68, 9-76
definition . . . . . . . . . . . . . . . .
9-63
displaying, modifying, deleting . . . . .
9-76
Double density . . . . . . . . . . . . .
9-66
DRI-Combiner configuration . . . . 9-51, 9-65
for Horizonmicro and Horizoncompact . . . . . . . . . . . . . . . . . . .
9-64
parameters . . . . . . . . . . . . . . .
9-68
reassigning . . . . . . . . . . . . 9-77 to 9-78
reassigning to a different GPROC . . . .
9-77
remotely calibrating . . 9-79, 9-84, 9-93, 9-99
DRI Detailed View
description of fields . . . . . . . . . . .
9-68
grouping . . . . . . . . . . 9-68, 9-73 to 9-76
DRIGroup . . . . . . . . . . . . . . . . .
9-63
for Horizonmicro and Horizoncompact . . . . . . . . . . . . . . . . . . .
9-64
impact of the Dual Band Cells feature . . 9-64,
9-182
Drive testing
Drive test . . . . . . . . . . . . . 14-3, 14-15
DSW
configuring
overview . . . . . . . . . . . . . . . 9-123
creating
using OMC-R GUI . . . . . . . . . . . 9-124
definition . . . . . . . . . . . . . . . . 9-123
displaying details
using TTY interface . . . . . . . . . . 9-126

E
eac_mode
changing . . . . . . . . . . . . . . . .
4-77
changing using TTY interface . . . . . .
4-77
EAS
alarm strings . . . . . . . . . . . . . . 9-102

IX-14

EAS (contd.)
alarm table . . . . . . .
changing alarm strings .
chg_eas_alarm command
configuring . . . . . . .

.
.
.
.

.
.
.
.

.
.
.
.

. . . . .
. . . . .
. . . . .
. 9-101,

9-102
9-104
9-103
9-111

68P02901W17-T
Jan 2010

Index

EAS (contd.)
configuring physical relay states . . . . 9-112
creating . . . . . . . . . . . . . . . . . 9-106
defining alarms in the alarm table . . . 9-103
definition . . . . . . . . . . . . . . . . 9-101
displaying . . . . . . . . . . . . . . . . 9-111
displaying EAS relay states . . . . . . . 9-112
equipping using TTY . . . . . . . . . . 9-111
modifying . . . . . . . . . . . . . . . . 9-111
parameters . . . . . . . . . . . . . . . 9-108
setting EAS relay states . . . . . . . . . 9-112
user definable alarm strings . . . . . . 9-102
EAS Detailed View
description of fields . . . . . . . . . . . 9-108
grouping . . . . . . . . . . . 9-108 to 9-110
ECERM
configuring . . . . . . . . . . . . . 2-70, 2-76
to 2-77, 2-127 to 2-128
parameters . . . . . . . . . . . . 2-71, 2-119
using TTY interface . . . . . . . . 2-77, 2-128
ecermOpt . . . . . . . . . . . . . . 2-71, 2-119
Editing network objects
general description and procedure . . .
1-26
EGPRS Coding Schemes
parameters . . . . . . . . . . . . . . .
2-40
egprsOpt parameter . . . . . . . . . . .
4-14
EGSM
configuring advanced load management . . . . . . . . . . . . . . . . . .
2-78
configuring advanced load mangement . . . . . . . . . . . . . . . . . .
2-79
configuring BCCH and SDCCH . . . . . 8-179
egsm_alm_allowed parameter
bss_egsm_alm_allowed parameter . . .
2-79
egsm_bcch_sd . . . . . . . . . . . . . . . 8-179
egsmOpt . . . . . . . . . . . . . . . . .
4-12
eMLPP
See Enhanced Multi-level Precedence and
Pre-emption . . . . . . . . . . . . . . . 2-165
en_incom_ho
barring incoming handovers . . . . . . 8-240
Enabling a Site to be remotely calibrated. . . . . . . . . . . . . . . . . . .
9-82
Enabling autocreation of proxy cells . . . 8-151
Enabling Bay Level Calibration facility . .
9-81
Enabling BSC-BTS dynamic allocation
at a BTS. . . . . . . . . . . . . . . . .
2-21
Enabling CIC validation
at an AXCDR
using TTY interface . . . . . . . . . .
4-76
Encryption algorithms
activating . . . . . . . . . . . . . . . .
2-26
displaying prioritized list . . . . . . . .
2-27
prioritizing . . . . . . . . . . . . . . .
2-27
setting . . . . . . . . . . . . . . . . .
2-26
Enhanced BSC capacity . . . . . . . . . .
2-94
Enhanced Circuit Error Rate Monitor
see ECERM . . . . . . . . . . . . . . .
2-70

68P02901W17-T
Jan 2010

Enhanced GPRS One Phase Access . . . . 2-113

configuring
using OMC-R GUI . . . . . . . . . . . 2-115
using TTY interface . . . . . . . . . . 2-115
parameters . . . . . . . . . . . . . . . 2-113
Enhanced Inter-RAT. . . . . . . . . . . .
2-96
Enhanced Inter-RAT Handover
parameters . . . . . . . . . . . . . . .
2-96
Enhanced Multi-level Precedence and
Pre-emption (eMLPP) . . . . . . . . . . . 2-165
associated parameters . . . . . . . . . 2-166
Enhanced Scheduling . . . . . . . . . . . 2-146
configuring
using OMC-R GUI . . . . . . . . . . . 2-148
using TTY interface . . . . . . . . . . 2-148
parameters . . . . . . . . . . . . . . . 2-146
Enhanced SDCCH to TCH band assignment
configuring . . . . . . . . . . . . . . . 8-198
parameter. . . . . . . . . . . . . . . . 8-199
Enhanced XBL . . . . . . . . . . . . . .
2-11
enhanced_relief . . . . . . . . . . . . 2-30, 8-28
EnhancedInterRatOpt . . . . . . . . . . .
2-96
enhancedMLPPOpt . . . . . . . . . . . . 2-166
Environment variables
CellXchange . . . . . . . . . . . . . . 12-35
network expansion . . . . . . . . . . .
11-5
eop_enabled. . . . . . . . . . . . 2-113, 2-146
eopOpt . . . . . . . . . . . . . . 2-113, 2-146
equipage hierarchy . . . . . . . . . . . .
9-34
Equipping BSP
using TTY interface . . . . . . . . . . .
9-38
Equipping BTP
using TTY interface . . . . . . . . . . .
9-42
Equipping BTS site . . . . . . . . . . . .
7-21
adding PATH
procedure . . . . . . . . . . . . . . .
7-22
adding PATH, RSL and RTF
procedure . . . . . . . . . . . . . . .
7-19
adding RSL
procedure . . . . . . . . . . . . . . .
7-24
adding RSL devices
procedure . . . . . . . . . . . . . . .
7-19
adding RTF
example . . . . . . . . . . . . . . . .
7-25
procedure . . . . . . . . . . . . . . .
7-25
adding RTF functions . . . . . . . . . .
7-20
procedure . . . . . . . . . . . . . . 7-19, 7-21
Equipping cabinets
using TTY interface . . . . . . . . . . .
4-58
Equipping cabinets & cages
remote BTS
example . . . . . . . . . . . . . . . .
7-36
Equipping CBL
parameters . . . . . . . . . . . . . . .
9-43
using TTY interface . . . . . . . . . . .
9-44
Equipping COMB
RTC hardware addresses . . . . . . . .
9-50
Equipping EAS

IX-15

Index

Equipping XBL
at a BSC
using TTY interface . . . . . . . . . . 9-200
at an RXCDR
using TTY interface . . . . . . . . . . 9-201
numbering the BSCs . . . . . . . . . . . 5-8
erc_ta_priority . . . . . . . . . 8-201 to 8-202
Establishing a cell boundary . . . . . . . 8-234
event logs . . . . . . . . . . . . . . . . . . 1-7
EXBL
Enhanced XBL . . . . . . . . . . . . .
2-11
Expanding the network . . . . . . . . . .
11-2
EXPORT__CELLS . . . . . . . . . 8-141, 8-157
Exporting and importing proxy cells . . . 8-155
Exporting proxy cells . . . . . . . . . . . 8-157
Extended cell range prioritization
configuring . . . . . . . . . . . . . . . 8-201
using OMC-R GUI . . . . . . . . . . . 8-201
using TTY interface . . . . . . . . . . 8-202
parameters . . . . . . . . . . . . . . . 8-201
Extracting data from the CM MIB
using cmutil . . . . . . . . . . 15-24 to 15-25
examples . . . . . . . . . . . . . . . 15-26
using SQL . . . . . . . . . . . . . . . . 15-30
using sql queries . . . . . . . . . . . . 15-30

Equipping EAS (contd.)

using TTY interface . . .
Equipping GCLK
using TTY interface . . .
Equipping GPROC
using TTY interface . . .
Equipping KSW
using TTY interface . . .
Equipping LCF
using TTY interface . . .
Equipping MSI
cage & slot restrictions .
Equipping MTL
using TTY interface . . .
Equipping OMF
using TTY interface . . .
Equipping OML
using TTY interface . . .
Equipping PCU
from the TTY interface .
Equipping PCU devices
Equipping a PCU devices
Equipping RTF
using TTY interface . . .
Equipping RXCDR cabinet
using TTY interface . . .

. . . . . . . . 9-111
. . . . . . . . 9-115
. . . . . . . . 9-119
. . . . . . . . 9-126
. . . . . . . . 9-129
. . . . . . . . 9-138
. . . . . . . . 9-153
. . . . . . . . 9-159
. . . . . . . . 9-161
. . . . . . . .

6-52

. . . . . . . .

6-52

. . . . . . . . 9-192
. . . . . . . .
4-65
. . . . . . 4-63, 4-66

F
Fast Call Setup . . . . . . . . . . . . . . 2-168
associated parameters . . . . . . . . . 2-168
FastCallOpt . . . . . . . . . . . . . . . . 2-169
fdd_qmin . . . . . . . . . . . . . . . . .
2-96
fdd_qoffset . . . . . . . . . . . . . . . .
2-96
Feature
22168 . . . . . . . . . . . . . . . . . . 2-182
23306 . . . . . . . . . . . . . . . . . . 2-182
25423 . . . . . . . . . . . . . . . . . . . 4-7
26481 . . . . . . . . . . . . . . . 4-55 to 4-56
26740 . . . . . . . . . . . . . . . . . .
6-29
27508 . . . . . . . . . . . . 1-5 to 1-6, 2-201
27703A . . . . . . . . . . . . . . . . 2-40 to
2-41, 2-61 to 2-62, 2-120, 2-198
27955A . . . . . . . . . 2-198, 4-31, 6-9, 8-75
28333 . . . . . . . . . . . . . . . . . . 2-182
28337 . . . . . . . . . . . . . . . . . . 2-182
28340 . . . . . . . . . . . . . . 2-182, 2-200
28351 . . . . . . . . . 2-198, 6-18, 6-29, 6-34
28938 . . . . . . . . . . . . . . . . . . 2-199
Finding a network object . . . . . . . . .
1-29
Fix Object load
identifying . . . . . . . . . . . . . . . 4-108
flexible neighbour cell processing
configuring
for a cell . . . . . . . . . . . . . . . 8-195
using OMC-R GUI . . . . . . . . . . . 8-197

IX-16

flexible neighbour cell processing (contd.)

configuring (contd.)
using TTY interface . . . .
overview . . . . . . . . . .
flow_control_t1 . . . . . . . .
flow_control_t2 . . . . . . . .
fm_site_type. . . . . . . . . .
Freeing a timeslot
at the same site . . . . . . .
between different sites . . .
FreqHopSys Detailed View
description of fields . . . . .
grouping . . . . . . . . . .
General . . . . . . . . . .
Identification . . . . . . .
Frequency change
BCCH . . . . . . . . . . . .
non BCCH. . . . . . . . . .
Frequency hopping
assigning to each timeslot
using TTY interface . . . .
baseband frequency hopping
configuring
using OMC-R GUI . . . . .
using TTY interface . . . .
constraints . . . . . . . . .
overview . . . . . . . . . .

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

. . 8-197
. . 8-195
2-23, 2-25
2-23, 2-25
. .
2-16

. . . . . .
. . . . . .
.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

5-24
5-24
8-171
8-172
8-172
8-172

. . . . . . 8-213
. . . . . . 8-216

. . . . . . 8-176
. . . . . . . 2-9
.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

. . 8-167
. . 8-175
. . . 2-4
2-4, 8-165

68P02901W17-T
Jan 2010

Index

Frequency hopping (contd.)

functions (contd.)

planning . . . . . . . . . . .
setting parameters
using TTY interface . . . . .
synthesizer frequency hopping
Frequency replanning. . . . . .
frequency_type . . . . . . . . .
front panel . . . . . . . . . . .
FRU
checking . . . . . . . . . . .
functions
creating individual . . . . . .
recommendation . . . . . .
creating multiple
recommendation . . . . . .
deleting
using OMC-R GUI . . . . . .
using TTY interface . . . . .
deleting multiple
recommendations . . . . . .

. . . . . .
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

2-4

displaying
using OMC-R GUI . . .
using TTY interface . .
equipping
using TTY interface . .
hierarchy . . . . . . . .
methods for configuring
individual . . . . . . .
multiple . . . . . . . .
modifying
using OMC-R GUI . . .
using TTY interface . .
modifying multiple . . .
using batch rlogin. . .
using cmutil. . . . . .
unequipping
using TTY interface . .

. . 8-175
. . . 2-5
. .
12-2
2-31, 2-33
. .
1-40

. . . . .

9-10

. . . . . .
. . . . . .

9-3
9-3

. . . . . .

9-8

. . . . . . 9-6
. . . . 9-4, 9-6
. . . . . .

. . . . . . . . .
. . . . . . . . .

9-5
9-5

. . . . . . . . . 9-4
. . . . . . . .
9-29
. . . . . . . . .
. . . . . . . . .
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

9-3
9-8

. 9-4
. 9-5
. 9-8
. 9-8
15-22

. . . . . . . . .

9-6

9-9

G
GBL . . . . . . . . . . . . .
configuring
using OMC-R GUI . . . .
creating
using OMC-R GUI . . . .
deleting
using OMC-R GUI . . . .
GBL Detailed View (PCU)
description of fields . . . .
grouping
Connectivity Information
Frame Relay Information
Identification . . . . . .
State . . . . . . . . . .
GCLK
configuring . . . . . . . .
creating
using OMC-R GUI . . . .
equipping
using TTY interface . . .
parameters . . . . . . . .
slot restrictions . . . . . .
GCLK Detailed View
description of fields . . . .
grouping
Cage and Slot . . . . . .
Identification . . . . . .
GCLK synchronization . . .
checking for a SITE . . . .
commands and parameters
configuration restrictions .
description . . . . . . . .
enabling. . . . . . . . . .

68P02901W17-T
Jan 2010

. . . . . . . .

6-2

. . . . . . .

6-38

. . . . . . .

6-38

. . . . . . .

6-41

. . . . . . .

6-39

.
.
.
.

6-39
6-40
6-39
6-40

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

. . . . . . . 9-113
. . . . . . . 9-113
. . . . . . . 9-115
. . . . . . . 9-114
. . . . . . . 9-113
. . . . . . . 9-114
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

. 9-115
. 9-114
.
7-43
.
7-52
.
7-44
.
7-44
.
7-43
.
7-48

GCLK synchronization (contd.)

mms_priority . . . . . . . . . . .
modes of operation . . . . . . . .
multiple SITE checks . . . . . . .
no. of GCLKs per site . . . . . . .
parameter descriptions . . . . . .
phase_lock_duration . . . . . . .
using TTY interface . . . . . . . .
examples . . . . . . . . . . . .
GDP
configuring enhanced provisioning
parameters . . . . . . . . . . .
definition . . . . . . . . . . . . .
enhanced . . . . . . . . . . . . .
primary and secondary . . . . . .
types . . . . . . . . . . . . . . .
GDS
configuring
using OMC-R GUI . . . . . . . .
creating
using OMC-R GUI . . . . . . . .
deleting
using OMC-R GUI . . . . . . . .
modifying
using OMC-R GUI . . . . . . . .
GDS Detailed View (PCU)
description of fields . . . . . . . .
grouping
Connectivity Information . . . .
Identification . . . . . . . . . .
State . . . . . . . . . . . . . .
GDS on PRP . . . . . . . . . . . . .
General

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

7-46
7-46
7-52
7-43
7-45
7-46
7-47
7-47

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

9-147
9-146
9-146
9-146
9-146
9-146

. . .

6-29

. . .

6-30

. . .

6-33

. . .

6-32

. . .

6-31

.
.
.
.

6-32
6-31
6-32
6-18

.
.
.
.

.
.
.
.

IX-17

Index

GPRS Coding Schemes 3 & 4

configuring
using TTY interface . . . . . . . . . .
2-44
GPRS interleaving TBFs
configuring
using OMC-R GUI . . . . . . . . . . .
2-92
GPRS Seamless Cell Reselection
configuring . . . . . . . . . . . . . . . 2-142
GPRS Suspend/Resume . . . . . . . . . . 2-178
GPRS Trace feature
gprsOpt . . . . . . . . . . . . . . . . .
4-15
gprs_enabled parameter . . . . . 8-208, 8-212
gprs_mac_mode parameter . . . . . . . .
2-92
gprs_sched_beta . . . . . . . . . . . . . 2-157
gprs_type5_alg . . . . . . . . . . . . . . 2-164
gprsOpt parameter . . . . . . . . . . . .
4-14
GSL
configuring
using OMC-R GUI . . . . . . . . . . .
6-34
creating
using OMC-R GUI . . . . . . . . . . .
6-35
deleting
using OMC-R GUI . . . . . . . . . . .
6-36
GSL Detailed View (PCU)
description of fields . . . . . . . . . . .
6-35
grouping
Identification . . . . . . . . . . . . .
6-36
State . . . . . . . . . . . . . . . . .
6-36
gsl_lcf_mapping . . . . . . . . . . . . . .
6-34
GSM
Half Rate . . . . . . . . . . . . 2-130, 2-140
changing mode using TTY. . . . . . .
4-78
Channel Mode Usage grouping . . . . 4-35,
4-75
Channel Mode Usage grouping with GSM
Half Rate . . . . . . . . . . . . . 4-37, 8-32
GSM Cell id
components of . . . . . . . . . . . . . 8-242

General (contd.)
grouping . . . . . . . . . . . . . . .
Generic clock synchronization
GCLK synchronization . . . . . . . .
Geographic Command Partition feature .
Global Locking . . . . . . . . . . . . .
GLU tool
using to interrogate the network . . .
GPROC
cage and slot details . . . . . . . . .
cage and slot restrictions . . . . . . .
configuring
for optimization . . . . . . . . . . .
overview . . . . . . . . . . . . . .
creating
using OMC-R GUI . . . . . . . . . .
equipping
using TTY interface . . . . . . . . .
parameters . . . . . . . . . . . . . .
GPROC Detailed View
description of fields . . . . . . . . . .
grouping
Cage and Slot . . . . . . . . . . . .
Identification . . . . . . . . . . . .
GPRS . . . . . . . . . . . . . . . . . .
enabling/changing for a cell
using TTY interface . . . . . . . . .
Enhanced GPRS One Phase Access . .
Enhanced Scheduling . . . . . . . . .
interleaving TBFs . . . . . . . . . . .
parameters . . . . . . . . . . . . .
multiple GPRS carriers per cell . . . .
parameter naming . . . . . . . . . .
parameters . . . . . . . . . . . . . .
propagatable cell parameters . . . . .
GPRS - Suspend/Resume . . . . . . . .
GPRS Coding Scheme
parameters . . . . . . . . . . . . . .

. 9-190
.
.
.

7-43
1-26
1-15

1-10

.
9-54
. 9-116
.
14-6
. 9-116
. 9-117
. 9-119
. 9-117
. 9-117
. 9-118
. 9-117
. . 6-2
.
.
.
.
.
.
.
.
.
.

8-212
2-113
2-146
2-89
2-90
8-207
8-70
4-14
8-79
2-179

2-40

H
Half Rate (GSM) . . .
half_rate_enabled . . .
handover_power_level
Handovers
adaptive
at a cell . . . . . .
at a neighbour . .
coincident multiband
ping-pong . . . . . .
hardware
checking at each site
hardware version
checking . . . . . .
HDLC
display hdlc layout .

IX-18

. . . . . . . . . . 2-140
. . . . . . . . . . 2-173
. . . . . . . . . .
2-35

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

. 8-185,
. . . . .
. . . . .
. . . . .

8-195
8-190
8-181
8-193

. . . . . . . . . .

7-56

. . . . . . . . . .

9-10

. . . . . . . . . .

9-16

hierarchy of devices and functions . . . .

9-29
HierDelete . . . . . . . . . . . . . . . .
4-47
script file . . . . . . . . . . . . . . . . 15-17
High Bandwidth interconnection between BSC
and PCU (PSI). . . . . . . . . . . . . . . 2-194
ho_margin_type5 . . . . . 8-185, 8-190 to 8-191
ho_only_max_pwr . . . . . . . . . 8-195, 8-197
ho_pwr_level_inner . . . . . . . . . 2-31 to 2-32
hopping_support . . . . . . . . . . . . . 8-165
hopping_systems_hsn . . . . . . . . . . . 8-165
hopping_systems_mobile_alloc . . . . . . 8-165
Horizon II BTS
introduction . . . . . . . . . . . . . . . . 7-8
Horizon II macro . . . . . . . . . . . . .
4-52
functionality . . . . . . . . . . . . . .
7-10

68P02901W17-T
Jan 2010

Index

Horizon II macro and Horizon II macro_ext

cabinets . . . . . . . . . . . . . . . . .
4-51
Horizon II mini . . . . . . . . . . . . 4-52, 7-11
BTP . . . . . . . . . . . . . . . . . . .
9-39
Double Density DRIs . . . . . . . . . .
9-66
EAS . . . . . . . . . . . . . . . . . . . 9-109

Horizonmicro/compact BTS
configuring
overview . . . . . . . . . . . . . . . . 7-7
HSP MTL . . . . . . . . . . . . 2-185 to 2-186

I
Import Radio Frequency values .
Importing proxy cells . . . . . .
Improved Timeslot Sharing . . .
parameters . . . . . . . . . .
imrm_force_recalc . . . . . . .
imrmOpt . . . . . . . . . . . .
Increase the Throughput of PRP
PCU . . . . . . . . . . . . . . .
Increased Network Capacity . .
Interaction with other features
Increased PRP capacity . . . . .
InitMib
script file . . . . . . . . . . .
inner_zone_alg . . . . . . . . .
Installing map background
using cmutil . . . . . . . . . .
Intelligent Locking . . . . . . .
Intelligent Multi Layer Resource
ment . . . . . . . . . . . . . .

. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
with the
. . . . .
. . . . .
. . . . .
. . . . .

12-17
8-158
2-176
2-176
2-152
2-151

Intelligent Multilayer Resource Management

(IMRM)
associated parameters . . . . . . . . . 2-151
prerequisites . . . . . . . . . . . . . . 2-151
weightings parameters . . . . . . . . . 2-152
Inter-RAT
enhanced . . . . . . . . . . . . . . . .
2-96
Inter-RAT Handover. . . . . . . . . . . .
2-95
configuring
using OMC-R GUI . . . . . . . . . . . 2-102
using TTY interface . . . . . . . . . . 2-102
parameters . . . . . . . . . . . . . . .
2-96
inter_rat_enabled . . . . . . . . . . . 2-96, 2-98
InterRatOpt . . . . . . . . . . . . . . . .
2-96
Interrogating the network
using COP tool . . . . . . . . . . . . .
1-10
using the COP GLU tool . . . . . . . . .
1-10
intra_cell_handover_allowed . . . . . . .
2-35

2-197
2-181
2-182
2-146

. . . . . 15-17
. . . . .
2-31
. . . . .
13-4
. . . . .
1-15
Manage. . . . . 2-150

K
KSW
configuring
overview . . . . .
creating
using OMC-R GUI .
definition . . . . . .
displaying details
using TTY interface
equipping
using TTY interface
parameters . . . . .
KSW Detailed View
description of fields .
grouping
Cage and Slot . . .

KSW Detailed View (contd.)

grouping (contd.)
Identification . . .
State . . . . . . .
KSWpair
configuring
overview . . . . .
parameters . . . . .
KSWpair Detailed View
description of fields .
grouping
Identification . . .
KSWX
definition . . . . . .

. . . . . . . . . . 9-123
. . . . . . . . . . 9-124
. . . . . . . . . . 9-123
. . . . . . . . . . 9-126
. . . . . . . . . . 9-126
. . . . . . . . . . 9-124
. . . . . . . . . . 9-124

. . . . . . . . . . 9-124
. . . . . . . . . . 9-125

. . . . . . . . . . 9-120
. . . . . . . . . . 9-120
. . . . . . . . . . 9-120
. . . . . . . . . . 9-120
. . . . . . . . . . 9-123

. . . . . . . . . . 9-125

L
LAC and/or CI
changing . . . . . . . . . . . . . . . . 8-242
multiple changes . . . . . . . . 8-243, 15-53
68P02901W17-T
Jan 2010

LAC and/or CI (contd.)

of a cell . . . . . . . . . . . . . . . . . 8-242
of proxy cell . . . . . . . . . . . . . . . 8-160
IX-19

Index

LAC and/or CI (contd.)

LMTL (contd.)

single change procedure . . . . . . . . 8-242

Lb interface
parameters . . . . . . . . . . . . . . . 2-105
LCF
configuring . . . . . . . . . . . . . . . 9-127
creating
using OMC-R GUI . . . . . . . . . . . 9-127
display current devices assigned to
LCF . . . . . . . . . . . . . . . . . . .
9-16
equipping
using TTY interface . . . . . . . . . . 9-129
modify max_mtls and max_cbls supported by
LCF . . . . . . . . . . . . . . . . . . .
9-17
parameters . . . . . . . . . . . . . . . 9-128
LCF Detailed View
description of fields . . . . . . . . . . . 9-128
grouping
Identification . . . . . . . . . . . . . 9-128
State . . . . . . . . . . . . . . . . . 9-129
LCS
see Location Services . . . . . . . . . . 2-104
Link Adaptation
Full Rate . . . . . . . . . . . . . . . . 2-130
MS Monitor . . . . . . . . . . . . . . 2-131
Half Rate . . . . . . . . . . . . . . . . 2-130
Link parameters
ber_oos_mon_period . . . . . . . . . . 9-138
ber_restore_mon_period . . . . . . . . 9-138
LMTL
configuring . . . . . . . . . . . . . . . 9-131
creating
using TTY interface . . . . . . . . . . 9-133
definition . . . . . . . . . . . . . . . . 9-131

description of loadsharing granularity . . . . . . . . . . . . . . . . . . . . 9-134

displaying loadsharing granularity
using TTY interface . . . . . . . . . . 9-136
modifying loadsharing granularity . . . 9-134
using the OMC-R GUI . . . . . . . . . 9-135
using TTY interface . . . . . . . . . . 9-135
parameters . . . . . . . . . . . . . . . 9-131
lmtl_loadshare_granularity . . . . . . . . 9-135
Local maintenance parameter
preventing rlogin . . . . . . . . . . . . . 1-4
local_transcoding . . . . . . . . . . 2-16 to 2-17
Location Services
configuring . . . . . . . . . . . . . . . 2-104
using OMC-R GUI . . . . . . . . . . . 2-111
using TTY interface . . . . . . . . . . 2-111
parameters . . . . . . . . . . . . . . . 2-105
LockUtility . . . . . . . . . . . . . . . .
1-18
Log files
for CellXchange . . . . . . . . . . . . .
12-7
viewing Network expansion logs . . . . 11-67
Logging in
as omcadmin . . . . . . . . . . . . . .
15-3
to a BSS from OMC-R . . . . . . . . . .
1-39
Logs
BSS . . . . . . . . . . . . . . . . . . . . 1-9
cellXchange . . . . . . . . . . . . . . .
12-7
CM changes. . . . . . . . . . . . . . . . 1-7
event logs . . . . . . . . . . . . . . . . . 1-7
network expansion . . . . . . . . . . . 11-67
omcaudit . . . . . . . . . . . . . . . . . 1-8
usraudit . . . . . . . . . . . . . . . . . . 1-8
low_sig_thresh parameter . . . . . 8-181, 8-183
lscOpt . . . . . . . . . . . . . . . . . . . 2-104

M
M interface . . . . . . . . . . . .
Making wide area modifications .
using TTY interface . . . . . . .
Managed objects . . . . . . . . .
Management Information Base
MIB . . . . . . . . . . . . . . .
Managing audit logs . . . . . . .
Managing standard configurations
for DRI calibration . . . . . . .
Maps
adding a regional map . . . . .
using cmutil. . . . . . . . . .
adding map link . . . . . . . . .
adding NEs & links
using cmutil. . . . . . . . . .
adding regional . . . . . . . . .
adding regional map
using OMC-R GUI . . . . . . .

IX-20

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

5-22
1-49
1-49
1-11

. . . .
1-11
. . . . 10-29
. . . .

9-99

. . . . 15-44
. . . .
13-2
. . . . 13-11
. . . .
. . . .

13-7
13-2

. . . .

13-2

Maps (contd.)
adding/changing map background
changing map background . . . .
using cmutil. . . . . . . . . . .
creating using cmutil . . . . . . .
deleting . . . . . . . . . . . . . .
using OMC-R GUI . . . . . . . .
deleting map link . . . . . . . . .
deleting map node . . . . . . . .
installing . . . . . . . . . . . . .
storing updated data . . . . . . .
using cmutil. . . . . . . . . . .
Max DRIs per GPROC
checking . . . . . . . . . . . . .
MAX_CM_OPS . . . . . . . . . . .
MAX_CMUTIL_OPS . . . . . . . . .
max_number_of_sdcchs parameter .
MAX_PARALLEL_AUDITS variable .

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

13-4
15-48
13-4
15-44
15-47
13-3
13-12
13-8
13-4
15-47
13-3

.
.
.
.
.

. .
7-59
. .
1-19
1-19, 15-3
. . 8-226
. .
10-4

68P02901W17-T
Jan 2010

Index

max_tx_bts . . . . . . . . . . . . . . . .
2-35
max_tx_bts parameter. . . . . . . . . . . 8-234
max_tx_ms . . . . . . . . . . . . . . . .
2-35
mb_preference . . . . . . . . . . . . 2-31, 2-33
MIB
adding a BSS . . . . . . . . . . . . . . 15-19
adding objects . . . . . . . . . . . . . 15-18
content of ASCII files . . . . . . . . .
15-7
adding/changing map background . . .
13-4
adding/deleting map link . . . . . . . . 13-11
adding/deleting regional map . . . . . .
13-2
auditing a BSS or RXCDR . . . . . . . . 10-14
auditing network . . . . . . . . . . . . 10-12
backing up . . . . . . . . . . . . . . .
1-11
changing connections between NEs. . . 15-36
changing NE details. . . . . . . . . . . 15-21
complete dump of . . . . . . . . . . . . 15-52
configuring . . . . . . . . . . . . . . .
15-2
using audit . . . . . . . . . . . . . .
10-2
containment. . . . . . . . . . . . . . .
1-11
creating maps
using cmutil. . . . . . . . . . . . . . 15-44
definition . . . . . . . . . . . . . . . .
1-11
deleting objects . . . . . . . . . . . . . 15-20
content of ASCII files . . . . . . . . .
15-8
extracting data . . . . . . . . . 15-24, 15-26
using cmutil. . . . . . . . . . . . . . 15-25
using SQL . . . . . . . . . . . . . . . 15-30
using sql queries . . . . . . . . . . . 15-30
extracting objects
content of ASCII files . . . . . . . . .
15-8
initializing of . . . . . . . . . . . . . .
1-11
locking . . . . . . . . . . . . . . . 1-14, 15-3
modifying objects
content of ASCII files . . . . . . . . .
15-8
object identification . . . . . . . . . . .
15-8
Off-Line . . . . . . . . . . . . . . . . .
12-2
populating new . . . . . . . . . . . . . 15-51
storing . . . . . . . . . . . . . . . . .
1-11
updating objects . . . . . . . . . . . . 15-21
MIB Locking . . . . . . . . . . . . . 1-14, 15-3
mib_locks.cfg . . . . . . . . . . . . . . .
1-15
min_number_of_sdcchs parameter . . . . 8-226
missing measurement reports
assigning a quality of 7
parameter. . . . . . . . . . . . . . . 8-224
using the OMC-R GUI . . . . . . . . . 8-224
using the TTY interface . . . . . . . . 8-225
assigning quality = 7 . . . . . . . . . . 8-224
MMS (PCU)
displaying . . . . . . . . . . . . . . . .
6-27
modifying . . . . . . . . . . . . . . . .
6-27
Mobile Allocation Selector window . . . . 8-171
Mobis interface . . . . . . . . . . . . . .
5-22
modify_value command
use in configuring sites . . . . . . . . .
7-34
using the all parameter . . . . . . . . .
1-50
modifying

68P02901W17-T
Jan 2010

modifying (contd.)
for a wide area . . . . . . . . . . . . .
1-49
Modifying
device and functions
using OMC-R GUI . . . . . . . . . . . . 9-4
using TTY interface . . . . . . . . . . . 9-5
network objects . . . . . . . . . . . . .
1-34
Modifying a neighbour
using OMC-R GUI . . . . . . . . . . . . 8-130
Modifying a network object
using OMC-R GUI . . . . . . . . . . . .
1-34
Modifying A, M & Mobis interfaces
A and M interfaces . . . . . . . . . . .
5-23
definitions. . . . . . . . . . . . . . . .
5-22
displaying interface status . . . . . . .
5-23
Mobis interface . . . . . . . . . . . . .
5-23
procedure . . . . . . . . . . . . . . . .
5-22
Modifying an Assoc_BSS
using TTY interface . . . . . . . . . . .
4-71
Modifying CELL Detailed View . . . . . .
8-79
Modifying cell parameters
using OMC-R GUI . . . . . . . . . . . .
8-13
Modifying default algorithms
using OMC-R GUI . . . . . . . . . . . .
8-95
using TTY interface . . . . . . . . . . .
8-98
Modifying EAS
using TTY interface . . . . . . . . . . . 9-111
Modifying LMTL loadsharing granularity . . . . . . . . . . . . . . . . . . . . . 9-134
using the OMC-R GUI . . . . . . . . . . 9-135
using TTY interface . . . . . . . . . . . 9-135
Modifying MTL loadsharing granularity . . . . . . . . . . . . . . . . . . . . . 9-155
using the OMC-R GUI . . . . . . . . . . 9-156
using TTY interface . . . . . . . . . . . 9-156
Modifying multiple devices or functions. . . 9-8
using batch rlogin. . . . . . . . . . . . . 9-8
using cmutil . . . . . . . . . . . . . . . 15-22
Modifying PCU Cabinet . . . . . . . . . .
6-16
Modifying PCU Cage . . . . . . . . . . .
6-17
Modifying PCU MMS . . . . . . . . . . .
6-27
Modifying proxy cell
using OMC-R GUI . . . . . . . . . . . . 8-145
Modifying UTRAN proxy cell
using OMC-R GUI . . . . . . . . . . . . 8-148
Monitoring network changes . . . . . . . 14-15
MoveCommsLinks
script file . . . . . . . . . . . . . . . . 15-17
ms_txpwr_max_cch . . . . . . . . . . . .
2-35
ms_txpwr_max_def . . . . . . . . . . . .
2-35
ms_txpwr_max_inner . . . . . . . . . 2-31, 2-33
MSC
call trace . . . . . . . . . . . . . . . .
2-60
configuring . . . . . . . . . . . . . . . . 3-7
configuring overload control . . . . . .
2-23
using TTY interface . . . . . . . . . .
2-25
controlling MS access class barring for overload
control

IX-21

Index

MSC (contd.)
controlling MS access class barring for overload
control (contd.)
using TTY interface . . . . . . . .
creating . . . . . . . . . . . . . . .
deleting . . . . . . . . . . . . . . .
displaying status of overload control
using TTY interface . . . . . . . .
enabling/disabling overload control
using TTY interface . . . . . . . .
MSC Detailed View
description of fields . . . . . . . . .
grouping
Identification . . . . . . . . . . .
Map Information . . . . . . . . .
State . . . . . . . . . . . . . . .
MSC initiated imsi & imei call trace .
impact summary . . . . . . . . . .
msc_release . . . . . . . . . . . . . .
MSI
cage & slot restrictions . . . . . . .
configuring . . . . . . . . . . . . .
creating
using OMC-R GUI . . . . . . . . .
definition . . . . . . . . . . . . . .
displaying, modifying, deleting . . .
equipping
using TTY interface . . . . . . . .
parameters . . . . . . . . . . . . .
MSI (PCU)
configuring
using OMC-R GUI . . . . . . . . .
creating
using OMC-R GUI . . . . . . . . .
deleting
using OMC-R GUI . . . . . . . . .
modifying
using OMC-R GUI . . . . . . . . .
MSI Detailed View
description of fields . . . . . . . . .

MSI Detailed View (contd.)

grouping
Cage and Slot . . . . . . . . . . . . .
Identification . . . . . . . . . . . . .
MMS HDSL Information . . . . . . .
Reconfiguration Information . . . . .
State . . . . . . . . . . . . . . . . .
MSI Detailed View (PCU)
description of fields . . . . . . . . . . .
grouping
Cage and Slot Information . . . . . .
Identification . . . . . . . . . . . . .
State . . . . . . . . . . . . . . . . .
MTL
configuring . . . . . . . . . . . . . . .
creating
using the OMC-R GUI . . . . . . . . .
description of loadsharing granularity . . . . . . . . . . . . . . . . . . . .
displaying loadsharing granularity
using TTY interface . . . . . . . . . .
equipping
using TTY interface . . . . . . . . . .
modifying loadsharing granularity . . .
using the OMC-R GUI . . . . . . . . .
using TTY interface . . . . . . . . . .
parameters . . . . . . . . . . . . . . .
reassigning . . . . . . . . . . . . . . .
MTL Detailed View
description of fields . . . . . . . . . . .
grouping
Identification . . . . . . . . . . . . .
State . . . . . . . . . . . . . . . . .
mtl_loadshare_granularity . . . . . . . .
MultiBand Inter-Cell handover feature . .
Multiple BSS Audit . . . . . . . . . 10-4,
Multiple GPRS carriers
cell parameters . . . . . . . . . . . . .
configuring for a cell . . . . . . . . . .

. .
2-25
. . . 3-7
. . . 3-9
. .

2-25

. .

2-25

. . .
.
.
.
.
.
.

3-7

. . 3-8
. . 3-9
. . 3-9
.
2-60
.
2-60
.
2-96

. . 9-138
. . 9-137
. . 9-138
. . 9-137
. . 9-144
. . 9-142
. . 9-139

. .

6-24

. .

6-24

. .

6-26

. .

6-26

9-140
9-139
9-141
9-141
9-141
6-25
6-25
6-25
6-26
9-152
9-152
9-155
9-157
9-153
9-155
9-156
9-156
9-152
9-14
9-152
9-153
9-153
9-156
2-30
10-18
8-208
8-207

. . 9-139

N
NACC
See Network Assisted Cell Change
nacc_enabled . . . . . . . . . . . .
naccOpt . . . . . . . . . . . . . . .
Navigating
to a network instance or class. . .
Navigation Tree . . . . . . . . . . .
buttons . . . . . . . . . . . . . .
recommendations . . . . . . . . .
using . . . . . . . . . . . . . . .
NBR_PROP_AFTER_AUDIT
environmental variable . . . . . .
NCCR

IX-22

NCCR (contd.)
. . . 2-162
. . . 2-164
. . . 2-163
.
.
.
.
.

.
.
.
.
.

.
1-28
.
1-12
.
1-28
. . 1-4
.
1-28

. . . 10-35

changes to Detailed Views . . .

changes to neighbour commands
configuring . . . . . . . . . . .
using OMC-R GUI . . . . . . .
using TTY interface . . . . . .
parameters . . . . . . . . . . .
nccrOpt . . . . . . . . . . . . . .
NE
definition of . . . . . . . . . . .
types of . . . . . . . . . . . . .
NE ID
changing

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

2-85
2-86
2-81
2-85
2-86
2-82
2-82

. . . .
. . . .

1-23
1-23

68P02901W17-T
Jan 2010

Index

NE ID (contd.)
changing (contd.)
for an Assoc_BSS . . . . . . . . . . .
4-80
for an Assoc_RXCDR . . . . . . . . .
4-80
NE Id Inconsistency List . . . . . . . . . 10-16
neighbor_journal . . . . . . . . . 8-195, 8-197
Neighbour Detailed View
description of fields . . . . . . . . . . . 8-121
grouping
Concentric Cells . . . . . . . . . . . 8-126
Directed Retry . . . . . . . . . . . . 8-126
General grouping . . . . . . . . . . . 8-123
Identification . . . . . . . . . . . . . 8-121
Power Budget Algorithm . . . . . . . 8-125
Neighbour templates . . . . . . . . . . . 8-133
creating . . . . . . . . . . . . . . . . . 8-133
deleting . . . . . . . . . . . . . . . . . 8-134
displaying a list of. . . . . . . . . . . . 8-133
editing . . . . . . . . . . . . . . . . . 8-134
neighbours
exporting on deletion of BCCH RTFs . . 9-195
UTRAN blind search . . . . . . . . . . 8-140
Neighbours
adding multiple
using add_nei . . . . . . . . . . . . . 8-129
configuring for adaptive handovers . . . 8-190
creating . . . . . . . . . . . . . 8-115, 8-121
methods. . . . . . . . . . . . . . . . 8-121
definition . . . . . . . . . . . . . . . . 8-106
deleting . . . . . . . . . . . . . . . . . 8-115
multiple . . . . . . . . . . . . . . . . 8-132
using the Navigation Tree. . . . . . . 8-131
displaying for more than one cell . . . . 8-109
modifying . . . . . . . . . . . . . . . . 8-130
using OMC-R GUI . . . . . . . . . . . 8-130
multiple modifying
same cell . . . . . . . . . . . . . . . 8-130
same SITE or NE . . . . . . . 8-130, 15-54
overview . . . . . . . . . . . . . . . . 8-106
reciprocal . . . . . . . . . . . . . . . . 8-107
automatic creation . . . . . . . . . . 8-107
creating . . . . . . . . . . . . . . . . 8-115
deleting . . . . . . . . . . . . . . . . 8-115
templates . . . . . . . . . . . . . . . . 8-133
viewing . . . . . . . . . . . . . . . . . 8-109
Network
change recommendations
on-line and off-line . . . . . . . . . . . 1-3
configuring the MIB. . . . . . . . . . .
15-2
deleting hierarchies . . . . . . . . . . . 15-17
expanding . . . . . . . . . . . . . . . .
11-2
interrogating using GLU . . . . . . . .
1-10
optimization. . . . . . . . . . . . . . .
14-2
Network Assisted Cell Change (NACC)
associated parameters . . . . . . . . . 2-163
interaction with QoS . . . . . . . . . . 2-163
naccOpt . . . . . . . . . . . . . . . . . 2-163
Network Controlled Cell Reselection

68P02901W17-T
Jan 2010

Network Controlled Cell Reselection (contd.)

see NCCR . . . . . . . . . . .
Network Detailed View
description of fields . . . . . .
grouping
Identification . . . . . . . .
Map Information . . . . . .
State . . . . . . . . . . . .
Network Element
databases
uploading . . . . . . . . . .
definition of . . . . . . . . . .
types of . . . . . . . . . . . .
Network Elements
database
checks . . . . . . . . . . .
Network Expansion
aborting
a batch . . . . . . . . . . .
a single operation in a batch
environment variables . . . .
in a daisy chain configuration .
copying a site . . . . . . . .
deleting a site . . . . . . . .
introduction . . . . . . . . . .
overview . . . . . . . . . . .
prerequisites . . . . . . . . .
reparenting a BTS
rollback . . . . . . . . . . .
restrictions . . . . . . . . . .
scheduling . . . . . . . . . .
Network instance
configuring . . . . . . . . . .
creating using OMC-R GUI . .
deleting . . . . . . . . . . . .
network objects
adding
using cmutil. . . . . . . . .
configuring
using OMC-R GUI . . . . . .
creating . . . . . . . . . . . .
using cmutil. . . . . . . . .
using Navigation Tree . . .
deleting . . . . . . . . . . . .
using cmutil. . . . . . . . .
using OMC-R GUI . . . . . .
modifying . . . . . . . . . . .
navigating to . . . . . . . . .
updating
using cmutil. . . . . . . . .
network_entity_id . . . . . . . .
non BCCH carrier frequency
changing . . . . . . . . . . .
NSVC
creating
using OMC-R GUI . . . . . .
deleting
using OMC-R GUI . . . . . .

. . . . .

2-81

. . . . . .

3-3

. . . . . .
. . . . . .
. . . . . .

3-4
3-6
3-6

. . . . .
. . . . .
. . . . .

1-24
1-23
1-23

. . . . .

4-42

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

11-66
11-71
11-5
11-37
11-45
11-38
11-2
11-2
11-3

. . . . . 11-32
. . . . .
11-3
. . . . . 11-54
. . . . . .
. . . . . .
. . . . . .

3-2
3-2
3-6

. . . . . 15-18
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
1-26
.
1-26
.
15-2
.
1-32
.
1-26
. 15-20
.
1-37
.
1-26
.
1-28

. . . . . 15-21
. . 2-16 to 2-17
. . . . . 8-216

. . . . .

6-43

. . . . .

6-48

IX-23

Index

NSVC (contd.)

NSVC Detailed View (PCU) (contd.)

modifying
using OMC-R GUI . . . . . . . . . . .
NSVC Detailed View (PCU)
description of fields . . . . . . . . . . .

grouping
Identification . . . . . . . . . . . . .
6-44
NS Information . . . . . . . . . . . .
6-45
number_sdcchs_preferred parameter . . . 8-226

6-46
6-44

O
Objects
adding to the MIB . . . . . . . .
commslink . . . . . . . . . . .
data in multiple tables . . . . .
deleting from the MIB. . . . . .
extracting from the MIB . . . .
identifying in cmutil ASCII files .
identifying in the MIB . . . . . .
modifying in the MIB . . . . . .
using cmutil . . . . . . . . . . .
Off-Line MIB . . . . . . . . . . .
OLM . . . . . . . . . . . . . . .
OMC Detailed View
description of fields . . . . . . .
grouping
Identification . . . . . . . . .
Map Information . . . . . . .
State . . . . . . . . . . . . .
OMC Naming menu option . . . .
OMC-R
addresses . . . . . . . . . . . .
configuring . . . . . . . . . . .
creating . . . . . . . . . . . . .
deleting . . . . . . . . . . . . .
synchronizing proxy cells . . . .
OMC-R parameter names
viewing in a Detailed View form.
omcaudit file
Path error messages . . . . . .
omcaudit log file . . . . . . . . .
OMF
configuring . . . . . . . . . . .
using OMC-R GUI . . . . . . .
equipping . . . . . . . . . . . .
parameters . . . . . . . . . . .
OMF Detailed View
description of fields . . . . . . .
grouping
Identification . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.

15-7
. 5-3
15-31
15-8
15-8
15-12
15-8
15-8
. 5-3
12-2
12-2

. . . . .

OMF Detailed View (contd.)

grouping (contd.)
State . . . . . . . . . . .
OML
checking . . . . . . . . . .
using OMC-R-GUI . . . . .
using SQL . . . . . . . . .
configuring . . . . . . . . .
creating
using OMC-R GUI . . . . .
equipping
using TTY interface . . . .
parameters . . . . . . . . .
setting addresses . . . . . .
slot:port settings . . . . . .
OML Detailed View
description of fields . . . . .
grouping
Identification . . . . . . .
State . . . . . . . . . . .
Optimization
checking and rectifying
database errors . . . . . .
hardware defects . . . . .
OOS devices . . . . . . .
collecting information
about the current network
monitoring network changes
overview . . . . . . . . . .
preparing . . . . . . . . . .
stages . . . . . . . . . . . .
using call trace and CTP
to detect problems . . . .
optional features
list of . . . . . . . . . . . .
opto_reporting parameter . . .
outer_zone_usage_level . . . .
overload control
MSC to BSS . . . . . . . . .

3-7

.
.
.
.

.
.
.
.

.
.
.
.

. . 3-8
. . 3-9
. . 3-9
.
1-30

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

5-20
. 3-7
. 3-7
. 3-9
8-160

. . . .

1-30

. . . .
11-4
. . . . . 1-8
.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

9-158
9-158
9-159
9-158

. . . . 9-158
. . . . 9-159

. . . . . . 9-159
.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
5-15
.
5-15
.
5-15
. 9-160

. . . . . . 9-160
.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

. 9-161
. 9-160
.
5-19
.
5-19

. . . . . . 9-160
. . . . . . 9-161
. . . . . . 9-161

. . . . . . 14-11
. . . . . . 14-10
. . . . . .
14-9
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
14-8
. 14-15
.
14-2
.
14-4
.
14-2

. . . . . . 14-14
. . . . . .
4-12
. . . . . . 9-111
. . . . . .
2-34
. . . . . .

2-23

P
ParallelAudits variable .
PATH . . . . . . . . . .
checking connectivity .
using cmutil. . . . .
IX-24

.
.
.
.

. . . . .
. . . . .
. . . . .
9-174 to

. . .
10-4
. . . . 7-3
. . . 9-174
9-175, 15-40

PATH (contd.)
checking connectivity (contd.)
using OMC-R GUI . . . . . . . . . . . 9-174
configuring . . . . . . . . . . . . . . . 9-162
68P02901W17-T
Jan 2010

Index

PATH (contd.)
configuring (contd.)
creating using Path Configure menu
option . . . . . . . . . . . . . . . . . 11-80
deleting using Path Configure menu
option . . . . . . . . . . . . . . . . . 11-81
initiating using Path Configure menu
option . . . . . . . . . . . . . . . . . 11-76
reassigning a device on a primary Path using
Path Configure menu option . . . . . 11-87
reassigning a device on a secondary Path
using Path Configure menu option . . 11-89
unassigning a device using Path Configure
menu option. . . . . . . . . . . . . . 11-85
using Path Configure menu option overview . . . . . . . . . . . . . . . 11-73
creating
from the OMC-R GUI . . . . . . . . . 9-167
methods of . . . . . . . . . . 9-164, 9-170
creating (recommended method)
using TTY interface . . . . . . . . . . 9-164
creating for a DYNET . . . . . . . . . .
4-94
definition . . . . . . . . . . . . . . . . 9-162
deleting
recommended method . . . . . . . . 9-170
deleting devices
using Path Configure menu option . . 11-81
extending . . . . . . . . . . . . . . . . 9-172
for a DYNET . . . . . . . . . . . . . . 9-163
limitations. . . . . . . . . . . . . . . . . 7-3
modifying . . . . . . . . . . . . . . . . 9-163
parameters . . . . . . . . . . . . . . . 9-167
reparenting . . . . . . . . . . . . . . . 9-172
recommended method . . . . . . . . 9-172
unassigning devices
using Path Configure menu option . . 11-81
PATH Configure form . . . . . . . . . . . 11-77
PATH Detailed View
description of fields . . . . . . . . . . . 9-167
grouping
Identification . . . . . . . . . . . . . 9-168
Path Information . . . . . . . . . . . 9-168
State . . . . . . . . . . . . . . . . . 9-168
PBCCH/PCCCH feature
configuring . . . . . . . . . . . . . . . 2-117
pbgt_mode . . . . . . . . . . . . . 2-31 to 2-32
pccch_enabled . . . . . . . . . . . . . . 2-119
pccchOpt . . . . . . . . . . . . . . . . . 2-119
PCR
configuring . . . . . . . . . . . . . . .
2-57
Preventative Cyclic Retransmission . . .
2-56
PCU
checking
using cmutil. . . . . . . . . . . 7-57, 15-27
configuring
overview . . . . . . . . . . . . . . . . 6-6
using OMC-R GUI . . . . . . . . . . . . 6-8
containment in the Navigation Tree. . . . 6-5

68P02901W17-T
Jan 2010

PCU (contd.)
creating
using OMC-R GUI . . . . . . . . . . . . 6-8
deleting
using OMC-R GUI . . . . . . . . . . .
6-15
displaying the MMS . . . . . . . . . . .
6-27
equipage hierarchy chart . . . . . . . . . 6-3
equipping
using TTY interface . . . . . . . . . .
6-52
equipping a cabinet . . . . . . . . . . . . 6-3
equipping a cage . . . . . . . . . . . . . 6-3
introduction . . . . . . . . . . . . . . . . 6-2
list of contained devices. . . . . . . . . . 6-2
modifying
using OMC-R GUI . . . . . . . . . . .
6-14
PCU Detailed View
description of fields . . . . . . . . . . . . 6-9
grouping
Address Information . . . . . . . . .
6-14
Air Interface Information . . . . . . .
6-11
Alarm Information . . . . . . . . . .
6-10
BSSGP Information . . . . . . . . . .
6-11
Gb Mapping Information . . . . . . .
6-11
Gb Statistics Configuration . . . . . .
6-12
Identification . . . . . . . . . . . . . . 6-9
Map Information . . . . . . . . . . .
6-13
NS Information . . . . . . . . . . . .
6-13
Quality of Service . . . . . . . . . . .
6-14
State . . . . . . . . . . . . . . . 6-10, 6-23
PCU devices
equipping
using TTY interface . . . . . . . . . .
6-52
in the Navigation Tree . . . . . . . . . . 6-5
to be equipped . . . . . . . . . . . . . . 6-5
ping-pong handovers
limiting
for a neighbour . . . . . . . . . . . . 8-193
pkt_radio_type . . . . . . . . . . . . . . 2-173
pkt_radio_type parameter . . . . . . . . .
2-40
Planning
frequency hopping systems . . . . . . . . 2-4
frequency replanning . . . . . . . . . .
12-2
pow_inc_step_size_dl . . . . . . . 8-203, 8-205
pow_inc_step_size_ul . . . . . . . 8-203, 8-205
pow_red_step_size_dl . . . . . . . 8-203, 8-205
pow_red_step_size_ul . . . . . . . 8-203, 8-205
power control optimization
for a cell . . . . . . . . . . . 8-203 to 8-205
Preparing for optimization . . . . . . . .
14-4
Preserve Transceiver Calibration feature
enabling at the OMC-R . . . . . . . . .
9-79
Preserving site names. . . . . . . . . . . 4-100
Preventing rlogin
using local maintenance parameter . . . . 1-4
Preventive Cyclic Retransmission . . . . .
2-56
range and default values for timers . . .
2-56
Primary arguments
in cmutil . . . . . . . . . . . . . . . .
15-5

IX-25

Index

Propagating cell changes to neighbours

after an audit . . . . . . . . . . . . . .
Propagating cell parameters
using the OMC-R GUI . . . . . . . . . .
Propagating TSC updates . . . . . . . . .
Proxy cells
autocreation . . . . . . . . . . . . . .
autocreation using OMC-R GUI . . . . .
changing LAC-CI . . . . . . . . . . . .
configuring . . . . . . . . . . . . . . .
configuring multiple
using cmutil. . . . . . . . . . 8-154,
creating
using OMC-R GUI . . . . . . . . . . .
creating multiple
using cmutil. . . . . . . . . . 8-154,
deleting
using OMC-R GUI . . . . . . . . . . .
deleting multiple
using cmutil. . . . . . . . . . 8-154,
dynamic propagation of data to
OMC-Rs . . . . . . . . . . . . . . . . .
enabling autocreation . . . . . . . . . .
enabling proxy cell export. . . . . . . .
exporting . . . . . . . . . . . . . . . .
importing . . . . . . . . . . . . . . . .
importing and exporting from/to
OMC-R . . . . . . . . . . . . . . . . .
list of environmental variables . . . . .
modifying

10-35

Proxy cells (contd.)

modifying (contd.)
using OMC-R GUI . . . . . .
modifying multiple
using cmutil. . . . . . . . .
OMC-R synchronization . . . .
overview . . . . . . . . . . .
ProxyCell Detailed View
description of fields . . . . . .
grouping
Identification . . . . . . . .
Proxy Cell Data . . . . . . .
PROXYCELL_AUTOCREATE . .
environmental variable . . . .
PROXYCELL_UPDATE. . . . . .
PROXYCELL_UPDATE_PERIOD .
PRP
GDS direct connection . . . .
PRR blocks
dynamic allocation of . . . . .
PSP
configuring
using OMC-R GUI . . . . . .
modifying
using OMC-R GUI . . . . . .
PSP Detailed View (PCU)
description of fields . . . . . .
grouping
Cage and Slot Information .
Identification . . . . . . . .

8-79
8-222
8-150
8-152
8-160
8-143
15-38
8-143
15-38
8-145
15-39
8-162
8-151
8-157
8-157
8-158
8-155
8-141

. . . . . 8-145
. 8-154, 15-38
. . . . . 8-160
. . . . . 8-141
. . . . . 8-143
.
.
.
.
.
.

. . . .
. . . .
8-141,
. . . .
. . . .
. . . .

. . . . .

8-144
8-144
8-150
8-151
8-141
8-141
6-18

. . . . . 2-146

. . . . .

6-22

. . . . .

6-22

. . . . .

6-22

. . . . .
. . . . .

6-23
6-23

Q
qosOpt . . . . . . . . . . . . . . . . . . 2-155
qsearch_c_initial . . . . . . . . . . . . .
2-96
qsearch_i . . . . . . . . . . . . . . . . .
2-96
Quality of Service (QoS)

Quality of Service (QoS) (contd.)

associated parameters . . . . . . . . . 2-154
prerequisites . . . . . . . . . . . . . . 2-154
Quality of Service Phase II . . . . . . . . 2-212

R
Radio Frequency
changes
large scale recommendations .
small scale recommendations .
changing
recommendations . . . . . . .
data
exporting . . . . . . . . . . .
import. . . . . . . . . . . . .
planning . . . . . . . . . . . .
Radio Frequency Planning
overview . . . . . . . . . . . .
RCU
configuring . . . . . . . . . . .
IX-26

. . . . .
. . . . .

8-4
8-4

. . . . .

8-4

. . . .
. . . .
. . . .

12-3
12-4
12-2

. . . .

12-5

. . . .

9-49

reassign command . . . . . . . . . . . .
9-18
Reassigning a device on a primary Path
using Path Configure menu option . . . 11-87
Reassigning a device on a secondary Path
using Path Configure menu option . . . 11-89
Reassigning a DRI
to a different GPROC . . . . . . . . . .
9-77
using OMC-R GUI . . . . . . . . . . . .
9-77
using TTY interface . . . . . . . . . . .
9-78
Reassigning a SITE/MTL/CBL device
display current devices assigned to
LCF . . . . . . . . . . . . . . . . . . .
9-16
modify max_mtls and max_cbls supported by
LCF . . . . . . . . . . . . . . . . . . .
9-17
68P02901W17-T
Jan 2010

Index

Reassigning SITE, MTL, and CBL devices

between GPROCs . . . . . . . . . . . .
using OMC-R GUI . . . . . . . . . . .
using TTY interface . . . . . . . . . .
displaying current devices assigned to
LCF . . . . . . . . . . . . . . . . . . .
Reciprocal neighbours
automatic creation . . . . . . . . . . .
creating . . . . . . . . . . . . . . . . .
definition . . . . . . . . . . . . . . . .
deleting . . . . . . . . . . . . . . . . .
overview . . . . . . . . . . . . . . . .
viewing . . . . . . . . . . . . . . . . .
RECIPROCATE_NBR environment variable . . . . . . . . . . . . . . . . . . . .
Recommendations
CM work practice . . . . . . . . . . . .
configuring
individual devices and functions . . .
multiple devices and functions . . . .
for Configuration Management . . . . .
network changes . . . . . . . . . . . .
weekly procedures . . . . . . . . . . .
Regional map
adding . . . . . . . . . . . . . . . . .
Regions
managing using cmutil . . . . . . . . .
selecting from the Navigation Tree . . .
remote attribute . . . . . . . . . . . . .
Remote Bay Level Calibration facility . . .
related parameters . . . . . . . . . . .
Remotely calibrating DRIs
creating a standard configuration . . . .
from the OMC-R . . . . . . . . . . . .
overview . . . . . . . . . . . . . . . .
Remotely logging into a BSS
from the OMC-R . . . . . . . . . . . .
using WebMMI . . . . . . . . . . . . .
Remotely tuneable combiner device
COMB. . . . . . . . . . . . . . . . . .
Removing NEs & links from map
using cmutil . . . . . . . . . . . . . . .
Renaming
an Assoc_BSS . . . . . . . . . . . . . .
an Assoc_RXCDR . . . . . . . . . . . .
Reparenting
an RXCDR
using cmutil. . . . . . . . . . . . . .
an RXCDR to a different MSC . . . . . .
BSS . . . . . . . . . . . . . . . . . . .
BSS to a different OMC-R . . . . . . . .
BSS to a different RXCDR . . . . . . . .
PATH
recommended method . . . . . . . .
Reparenting a BTS . . . . . . . . . . . .
Reserving a timeslot . . . . . . . . . . .
Reverting to saved data
Detailed View menu option . . . . . . .

68P02901W17-T
Jan 2010

9-14
9-15
9-15
9-16
8-107
8-115
8-107
8-115
8-106
8-109
8-107
.

1-4

.
.
.
.
.

9-3
9-8
1-2
1-3
1-2
13-2

15-52
1-26
15-20
9-79
9-82
9-84
9-93
9-79
1-39
1-45
9-49
13-9
4-80
4-80

4-106
4-106
4-100
4-101
4-104
9-172
11-22
5-24
1-34

Reverting to saved information . . . . . .

1-35
RF configuration file
creating . . . . . . . . . . . . . . . . . 12-34
RF.CNFG . . . . . . . . . . . . . . . . .
12-6
rfexport . . . . . . . . . . . . . . . . . . 12-43
rfimport . . . . . . . . . . . . . . . . . . 12-45
rfNcheck . . . . . . . . . . . . . . . . . 12-47
rlogin
advantages and disadvantages . . . . . . 1-4
maximum number of sessions . . . . . .
1-39
preventing . . . . . . . . . . . . . . . . 1-4
to a BSS. . . . . . . . . . . . . . . . .
1-39
rpt_bad_qual_no_mr. . . . . . . 8-224 to 8-225
RSL
configuring
overview . . . . . . . . . . . . . . . 9-176
using Path Configure . . . . . . . . . 11-73
Congestion Control feature . . . 2-170, 9-176
creating
from OMC-R GUI . . . . . . . . . . . 9-177
creating at a Site
using Path Configure menu option . . 11-93
definition . . . . . . . . . . . . . . . . 9-176
displaying, modifying, deleting . . . . . 9-181
equipping
using TTY interface . . . . . . . . . . 9-179
parameters . . . . . . . . . . . . . . . 9-177
unequipping
using TTY interface . . . . . . . . . . 9-180
RSL Congestion Control. . . . . . 2-170, 9-176
associated parameters . . . . . . . . . 2-170
RSL Detailed View
description of fields . . . . . . . . . . . 9-177
grouping
Identification . . . . . . . . . . . . . 9-178
LapD Information . . . . . . . . . . . 9-178
MMS Timeslots . . . . . . . . . . . . 9-179
State . . . . . . . . . . . . . . . . . 9-178
RTC
configuring
equipping COMB . . . . . . . . . . .
9-49
hardware addresses. . . . . . . . . . .
9-50
RTF
adding . . . . . . . . . . . . . . . 7-20, 7-25
configuring
overview . . . . . . . . . . . . . . . 9-182
using Path Configure . . . . . . . . . 11-73
creating . . . . . . . . . . . . . . . . . 9-185
using OMC-R GUI . . . . . . . . . . . 9-185
creating at a Site
using Path Configure menu option . . 11-92
deleting
exporting incoming neighbours . . . . 9-195
using OMC-R GUI . . . . . . . . . . . 9-193
displaying
using TTY interface . . . . . . . . . . 9-195
equipping
using TTY interface . . . . . . . . . . 9-192

IX-27

Index

RTF (contd.)

RXCDR (contd.)

functions
adding . . . . . . . . . . . . . . .
impact of VersaTRAU feature . . . . .
modifying
using TTY interface . . . . . . . . .
reassigning on the secondary Path . .
RTF Detailed View
description of fields . . . . . . . . . .
grouping
AMR/GSM Half Rate grouping . . .
Carrier 1 Information . . . . . . . .
Concentric Cells . . . . . . . . . .
GPRS . . . . . . . . . . . . . . . .
Identification . . . . . . . . . . . .
MMS Timeslots . . . . . . . . . . .
State . . . . . . . . . . . . . . . .
rtf_ds0_count . . . . . . . . . . 2-173
RTFGroup . . . . . . . . . . . . . . . .
impact of Dual Band Cells feature. . .
9-182
RXCDR
adding
assigning DTE X.121 addresses . . .
creating database . . . . . . . . . .
adding to network
overview process . . . . . . . . . .
containment. . . . . . . . . . . . . .
creating
using the OMC-R GUI . . . . . . . .
creating a cabinet
using OMC-R GUI . . . . . . . . . .

creating a cage
using OMC-R GUI . . . . . . .
database
uploading . . . . . . . . . . .
definition of . . . . . . . . . . .
deleting . . . . . . . . . . . . .
deleting at MUX . . . . . . . .
configuration changes . . . .
dependencies . . . . . . . . .
removing the cabling . . . . .
removing the NE . . . . . . .
removing the NE link . . . . .
deleting at OMC-R . . . . . . .
deleting at packet switch . . . .
configuration changes . . . .
deleting routeing table entries
removing the cabling . . . . .
equipping a cabinet . . . . . . .
example . . . . . . . . . . . .
modifying details . . . . . . . .
reparenting to a different MSC .
to BSS. . . . . . . . . . . . . .
RXCDR-BSC dynamic allocation
overview . . . . . . . . . . . .
parameters . . . . . . . . . . .
RXCDR/BSS to OMC-R
connectivity . . . . . . . . . . .
rxlev_dl_zone . . . . . . . . . . .
rxlev_ul_zone . . . . . . . . . . .

.
7-25
. 9-183
. 9-195
. 11-89
. 9-185
.
.
.
.
.
.
.
to
.
.

9-191
9-187
9-189
9-189
9-186
9-189
9-187
2-174
9-182
9-64,

.
.

5-19
4-41

. . 4-2
.
9-29
.

4-39

4-62

. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

4-64

. .
1-24
. .
1-23
. .
4-44
. .
4-48
. .
4-49
. .
4-49
. .
4-48
. .
4-49
. .
4-50
. .
4-44
. .
4-48
. .
4-48
. .
4-48
. .
4-48
4-63, 4-66
. .
4-65
. .
4-40
. . 4-106
. . . 5-2

. . . .
2-13
. 2-16 to 2-17
. . . .
. . . .
. . . .

5-15
2-34
2-34

S
Save Defaults menu option
using . . . . . . . . . . . . . .
Saving data
Detailed View menu option . . .
Scheduled audit
deferring . . . . . . . . . . . .
displaying the network elements
status of Multiple BSS audit . .
Scheduling
network expansion . . . . . . .
Scheduling an audit . . . . . . . .
deleting . . . . . . . . . . . . .
modifying . . . . . . . . . . . .
printing . . . . . . . . . . . . .
warning . . . . . . . . . . . . .
SCR
configuring . . . . . . . . . . .
using OMC-R GUI . . . . . . .
using TTY interface . . . . . .
parameters . . . . . . . . . . .
Script files

IX-28

Script files (contd.)

. . . . .
. . . .

9-3
1-34

. . . . 10-25
. . . . 10-26
. . . . 10-26
.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

11-54
10-19
10-27
10-24
10-27
10-19

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

2-143
2-142
2-144
2-143

cmutil . . . . . . . . . . . . . . . . . . 15-17
HierDelete . . . . . . . . . . . . . . . 15-17
MoveCommsLinks. . . . . . . . . . . . 15-17
preserve_site_names . . . . . . . . . . 4-100
SDCCH
changing number of allocated. . . . . . 8-226
changing the number of allocated
using OMC-R GUI . . . . . . . 8-230, 8-236
using TTY interface . . . . . . . . . . 8-230
configuration
checking multiple cells . . . . . . . . 8-233
sdcch_need_high_water_mark parameter . . . . . . . . . . . . . . . . . . . . 8-226
sdcch_need_low_water_mark parameter . . . . . . . . . . . . . . . . . . . . 8-226
sdcch_tch_band_reassign_delay . . . . . . 8-198
to 8-199
Seamless Cell Reselection (GPRS)
see SCR . . . . . . . . . . . . . . . . . 2-142
secondary_freq_type . . . . . . . . 2-31 to 2-32

68P02901W17-T
Jan 2010

Index

security levels
changing . . . . . . . . . . . . . . . .
1-43
using TTY interface . . . . . . . . . .
1-43
serial number
checking . . . . . . . . . . . . . . . .
9-10
set_full_power command . . . . . . . . . 8-237
set_relay_contact command . . . . . . . . 9-112
Setting frequency hopping parameters
using TTY interface . . . . . . . . . . . 8-175
SFH
Synthesizer frequency hopping . . . . . . 2-5
SGSN . . . . . . . . . . . . . . . . . . . . 6-2
configuring . . . . . . . . . . . . . . .
6-49
creating
using OMC-R GUI . . . . . . . . . . .
6-49
deleting
using OMC-R GUI . . . . . . . . . . .
6-51
modifying
using OMC-R GUI . . . . . . . . . . .
6-51
multiple . . . . . . . . . . . . . . . . .
6-49
network topology . . . . . . . . . . . .
6-49
SGSN Detailed View
description of fields . . . . . . . . . . .
6-50
grouping
Identification . . . . . . . . . . . . .
6-50
Map Information . . . . . . . . . . .
6-50
State . . . . . . . . . . . . . . . . .
6-50
Short message service - point to point . .
2-53
displaying the downlink logical channel . . . . . . . . . . . . . . . . . . .
2-55
displaying the state of MS originated point to
point sms . . . . . . . . . . . . . . . .
2-54
displaying the state of MS terminated
smsptp . . . . . . . . . . . . . . . . .
2-55
enabling and disabling MS originated point to
point sms . . . . . . . . . . . . . . . .
2-54
enabling and disabling MS terminated
smsptp . . . . . . . . . . . . . . . . .
2-54
specifying downlink logical channel. . .
2-55
Short message service-CB
CBC to BSS interface information
using TTY interface . . . . . . . . . .
2-50
CBC to BSS successful VBINDs before
negotiation
using TTY interface . . . . . . . . . .
2-50
configuring
using OMC-R GUI . . . . . . . . . . .
2-48
using TTY interface . . . . . . . . . .
2-48
creating and transmitting
using TTY interface . . . . . . . . . .
2-51
creating background messages . . . . .
2-45
delay between outage and CBS halting
transmission
using TTY interface . . . . . . . . . .
2-50
deleting background messages
using TTY interface . . . . . . . . . .
2-52
determining CBCH status
using TTY interface . . . . . . . . . .
2-48

68P02901W17-T
Jan 2010

Short message service-CB (contd.)

editing and viewing at a CELL
using OMC-R GUI . . . . . . . . . . . 8-244
enabling and disabling CBCH
using TTY interface . . . . . . . . . .
2-51
enabling and disabling counter statistics
using TTY interface . . . . . . . . . .
2-51
overview . . . . . . . . . . . . . . . .
2-45
parameters . . . . . . . . . . . . . . .
2-46
procedures . . . . . . . . . . . . . . .
2-48
selecting interface version between BSS and
CBCchannel
using TTY interface . . . . . . . . . .
2-49
setting a delay between outage and CBC halting
transmission
using TTY interface . . . . . . . . . .
2-49
setting no. of successful VBINDs
using TTY interface . . . . . . . . . .
2-49
viewing and editing at a CELL
using OMC-R GUI . . . . . . . . . . . 8-244
Single BCCH for a dual band cell . . . . .
2-28
Single BCCH for Dual Band Cells feature
configuring . . . . . . . . . . . . . . .
2-28
SITE
containment. . . . . . . . . . . . . . .
9-30
hardware devices . . . . . . . . . . .
9-31
logical links . . . . . . . . . . . . . .
9-32
radio frequency . . . . . . . . . . . .
9-33
software functions . . . . . . . . . .
9-31
SITE Detailed View
description of fields . . . . . . . . . . .
7-27
grouping
Alarm Information . . . . . . . . . .
7-31
Circuit Error Rate Monitor . . . . . .
7-32
CRM Timers . . . . . . . . . . . . .
7-32
GPRS . . . . . . . . . . . . . . . . .
7-32
Identification . . . . . . . . . . . . .
7-27
Local Routing . . . . . . . . . . . . .
7-28
Map Information . . . . . . . . . . .
7-33
RRSM Timers . . . . . . . . . . . . .
7-32
RSS Timers . . . . . . . . . . . . . .
7-32
SMS Information . . . . . . . . . . .
7-31
State . . . . . . . . . . . . . . . . .
7-28
Sites
adding
overview . . . . . . . . . . . . . . .
7-34
adding BTS
overview . . . . . . . . . . . . . . .
7-12
BSS links & control functions . . . . . . . 7-2
checking hardware deployed . . . . . .
7-56
checking status . . . . . . . . . . . . . 8-214
configuring . . . . . . . . . . . . . . . . 7-1
creating
using OMC-R GUI . . . . . . . . . . .
7-26
deleting a device
using Path Configure menu option . . 11-91
description . . . . . . . . . . . . . . . . 7-2
preserving names . . . . . . . . . . . . 4-100

IX-29

Index

Sites (contd.)

Source cell (contd.)

setting at full power. . . . . . . . . . . 8-237

simplified network diagram . . . . . . . . 7-2
Site . . . . . . . . . . . . . . . . . . .
9-14
unequipping using TTY . . . . . . . . .
7-25
SMS-CB
Short message service - CB . . . . . . .
2-45
sms_fast_select . . . . . . . . . . . . . .
2-47
sms_no_bcast_msg . . . . . . . . . . . .
2-51
SMS-PTP
Short message service - point to point. .
2-53
SMSCBmsg
parameters . . . . . . . . . . . . . . . 8-244
SMSCBmsg Detailed View
description of fields . . . . . . . . . . . 8-244
grouping
Identification . . . . . . . . . . . . . 8-245
SMS Information . . . . . . . . . . . 8-245
Software patching and PCU Software Upgrade
with no BSC Outage. . . . . . . . . . . . 2-188
software version number
checking . . . . . . . . . . . . . . . . 4-108
format. . . . . . . . . . . . . . . . . . 4-108
software versions
checking . . . . . . . . . . . . . . . . 4-108
Source & Neighbour View . . . . . . . . 8-109
Source cell

definition . . . . . . . . . . . . . .
deleting . . . . . . . . . . . . . . .
overview . . . . . . . . . . . . . .
viewing for more than one cell . . .
Source cells
creating . . . . . . . . . . . . . . .
Source object
definition . . . . . . . . . . . . . .
SQL
data extraction . . . . . . . . . . .
queries
containment relationships . . . .
order . . . . . . . . . . . . . . .
script knowledge required . . . . .
Stealing algorithm . . . . . . . . . .
other settings . . . . . . . . . . . .
using default setting . . . . . . . .
Support of Incell as an optional feature
Suspend/Resume
parameters . . . . . . . . . . . . .
Syntax
cmutil . . . . . . . . . . . . . . . .
Synthesizer frequency hopping
BCCH frequency excluded . . . . .
BCCH frequency included. . . . . .
description . . . . . . . . . . . . .

.
.
.
.

.
.
.
.

8-106
8-115
8-106
8-109

. . 8-115
. . 8-106
. . 15-30
.
.
.
.
.
.
.

.
.
.
.
.
.
.

15-35
15-35
15-31
9-54
9-58
9-56
2-199

. . 2-179
. .

15-5

. . .
. . .
. . .

2-6
2-8
2-5

T
TBF
delayed uplink release
description . . . . . .
interleaving . . . . . .
parameters . . . . .
terminating site
definition . . . . . . .
Timeslot usage
displaying . . . . . . .
tlli_blk_coding. . . . . .
Troubleshooting
network expansion . .
TRU_id (TopCell SITE)
checking . . . . . . .

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

TRX
creating . . . . . . . . . . .
deleting . . . . . . . . . . .
ts_in_usf_active . . . . . . . .
ts_sharing . . . . . . . . . . .
TSC
changing for a BCCH . . . .
propagating updates . . . .
using OMC-R GUI . . . . .
using TTY interface . . . .
tsc_update_method . . . . . .
tx_power_cap . . . . . . . . .
Types of BSS/RXCDR database

2-90
2-89
2-89
2-90

. . . . . . . . . 9-162
. . . . . . . . .
. . . . . . . . .

9-20
8-77

. . . . . . . . . 11-52
. . . . . . . . .

.
.
.
.

. . . . .
. . . . .
. 2-113,
. . . . .

9-182
9-182
2-146
2-20

.
.
.
.
.
.
.

. . . . . 8-221
8-222 to 8-223
. . . . . 8-222
. . . . . 8-222
8-222 to 8-223
. . . 2-31, 2-33
. . . . .
4-41

7-59

U
Unassigning a Path
using Path Configure menu
Unequipping
a DYNET . . . . . . . . .
device and functions
using TTY interface . . .
RSL . . . . . . . . . . . .
IX-30

Unequipping (contd.)
option . . . 11-85
. . . . . . .

4-99

. . . . . . . . 9-6
. . . . . . . 9-193

RTF . . . . . . . . . . . . . . .
TCU/CTU cabinets at M-Cell and
sites. . . . . . . . . . . . . . .
Updating network objects
using cmutil . . . . . . . . . . .
Uploading NE database . . . . . .

. . . . 9-193
Horizonmacro
. . . .
7-39
. . . . 15-21
. . . .
1-24
68P02901W17-T
Jan 2010

Index

user access
to functions . . . . . . . . . . . . . . .
1-27
User-definable EAS BSC/BSS and BTS alarm
strings . . . . . . . . . . . . . . . . . . 9-102
Using call trace to detect problems . . . . 14-14
usraudit log file . . . . . . . . . . . . . . . 1-8
UTRAN Blind Search Neighbour . . . . . 8-140
creating . . . . . . . . . . . . . . . . . 8-140
UTRAN Blind Search Neighbour Detailed View
description of fields . . . . . . . . . . . 8-140
grouping
General . . . . . . . . . . . . . . . . 8-140
Identification . . . . . . . . . . . . . 8-140
UTRAN neighbour
configuring . . . . . . . . . . . . . . . 8-135
using TTY interface . . . . . . . . . . 8-137
creating
using OMC-R GUI . . . . . . . . . . . 8-136

UTRAN neighbour (contd.)

definition . . . . . . . . . . .
parameters . . . . . . . . . .
UTRAN Proxy cells
configuring . . . . . . . . . .
creating
using OMC-R GUI . . . . . .
deleting
using OMC-R GUI . . . . . .
modifying
using OMC-R GUI . . . . . .
UTRAN ProxyCell Detailed View
description of fields . . . . . .
grouping
Identification . . . . . . . .
UTRAN Proxy Cell Data . . .

. . . . . 8-135
. . . . . 8-135
. . . . . 8-146
. . . . . 8-146
. . . . . 8-149
. . . . . 8-148
. . . . . 8-146
. . . . . 8-147
. . . . . 8-147

V
VersaTRAU . . . . . . . . . . . . . .
backhaul timeslot values . . . . . .
impact on RTF . . . . . . . . . . .
information in Channel Status form .
parameters . . . . . . . . . . . . .
versTrauOpt . . . . . . . . . . . . .
Viewing
BSS/OMC-R parameters names
in a Detailed View. . . . . . . . .

.
.
.
.
.
.

.
.
.
.
.
.

. .

2-172
2-173
9-183
9-25
2-174
2-174

Viewing (contd.)
cell sources, neighbours and reciprocals . . . . . . . . . . . . . . . . . .
neighbours . . . . . . . . . . . . . .
reciprocal neighbours . . . . . . . . .
Viewing and editing a DYNET
using the OMC-R GUI . . . . . . . . .

. 8-109
. 8-109
. 8-109
.

4-97

1-30

W
WebMMI
setting up and using . . . . . . . . . .
1-46
using to access a BSS . . . . . . . . . .
1-45
Weekly procedures
recommendations . . . . . . . . . . . . . 1-2

Work practice
CM recommendations . . . . . . . . . . . 1-4
worse_neighbor_ho . . . . . . . . 8-195, 8-197

X
X.121 DTE addresses
storage at OMC-R .
x25_config file. . .
entries in . . . .
x25_config file
entries in . . . . .
format. . . . . . .
location . . . . . .
X.121 addresses in
XBL
adding
68P02901W17-T
Jan 2010

. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .

5-17
5-17
5-18

.
.
.
.

5-18
5-17
5-17
5-17

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

XBL (contd.)
adding (contd.)
using OMC-R GUI . . . . . . . .
configuring
overview . . . . . . . . . . . .
creating
using OMC-R GUI . . . . . . . .
definition . . . . . . . . . . . . .
deleting
using OMC-R GUI . . . . . . . .
determining the number required.

. . . 9-200
. . . 9-197
. . . 9-198
. . . 9-197
. . . 9-200
. . .
2-15
IX-31

Index

XBL Detailed View

description of fields .
grouping
Identification . . .
LapD Information .
State . . . . . . .

XBL (contd.)
enhanced . . . . . .
equipping at BSC
using TTY interface
equipping at RXCDR
using TTY interface
parameters . . . . .

. . . . . . . . . .

2-11

. . . . . . . . . . 9-200
. . . . . . . . . . 9-201
. . . . . . . . . . 9-198

. . . . . . . . . . 9-198
. . . . . . . . . . 9-199
. . . . . . . . . . 9-200
. . . . . . . . . . 9-200

Z
zone_ho_hyst . . . . . . . . . . . . . 2-31, 2-33

IX-32

68P02901W17-T
Jan 2010