You are on page 1of 1421

GSM SYSTEM CONFIGURATION INSTALLATION AND CONFIGURATION

GSM SOFTWARE RELEASE 8

GSR8
GMR-01
68P02901W17-R

GSM SOFTWARE RELEASE 8

GMR-01

GSM SYSTEM CONFIGURATION INSTALLATION AND CONFIGURATION

68P02901W17-R

GSR8

Installation and Configuration: GSM System Configuration

1994 - 2006 Motorola, Inc. All Rights Reserved

GMR-01

68P02901W17-R 14 Apr 2006

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

GMR-01

14 Apr 2006

Table of Contents

Contents

Installation and Configuration: GSM System Configuration


Issue status of this manual . General information . . . . Reporting safety issues . . Warnings and cautions . . . General warnings . . . . . General cautions . . . . . Devices sensitive to static . Caring for the environment. Motorola manual set . . . . Manual amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6 9 10 12 16 17 18 19 20

Chapter 1: Configuration Management General Information


Recommendations for Configuration Management . . . Management Information Base (MIB) . . . . . . . . Definition of a Network Element (NE) . . . . . . . . Uploading an NE database to the OMC-R . . . . . . . Configuring network objects using the OMC-R GUI . . Navigating to a network object class or instance . . . . Using Detailed Views . . . . . . . . . . . . . . . . Creating a network object using the OMC-R GUI . . . Modifying a network object using the OMC-R GUI . . Deleting a network object using the OMC-R GUI . . . Remotely logging in to a BSS site from the OMC-R . . Changing security level (for TTY interface commands) Remotely logging in to a BSS using WebMMI. . . . . Making wide area modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1-16 1-29 1-31 1-33 1-35 1-37 1-39 1-41 1-44 1-46 1-50 1-51 1-55

Chapter 2: Configuring BSS Features


Frequency hopping . . . . . . . . . . . . . . . . . . . . . Enhanced XBL (EXBL) . . . . . . . . . . . . . . . . . . . Dynamic Allocation of RXCDR-BSC Circuits (DARBC) . . . Dynamic allocation of BSC-BTS Backing Resources (DYNET) MSC to BSS overload control . . . . . . . . . . . . . . . . Encryption algorithms . . . . . . . . . . . . . . . . . . . . Dual band cells option . . . . . . . . . . . . . . . . . . . . GPRS and EGPRS coding schemes . . . . . . . . . . . . . . Short Message Service - Cell Broadcast . . . . . . . . . . . . 68P02901W17-R 14 Apr 2006 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 2-11 2-14 2-20 2-24 2-27 2-29 2-40 2-46
i

GMR-01

Contents

Short Message Service - Point-To-Point . . . . . . . . . . . Preventive Cyclic Retransmission (PCR) . . . . . . . . . . MSC initiated IMSI and IMEI call trace. . . . . . . . . . . Call trace flow control . . . . . . . . . . . . . . . . . . . GPRS Trace. . . . . . . . . . . . . . . . . . . . . . . . Enhanced Circuit Error Rate Monitor (ECERM) . . . . . . . Advanced Load Management for EGSM . . . . . . . . . . Network Controlled Cell Reselection . . . . . . . . . . . . GPRS Interleaving TBFs. . . . . . . . . . . . . . . . . . Enhanced BSC Capacity . . . . . . . . . . . . . . . . . . Inter-Radio Access Technology (Inter-RAT) Handover . . . . GSM location services . . . . . . . . . . . . . . . . . . . Enhanced GPRS One Phase Access . . . . . . . . . . . . PBCCH/PCCCH feature . . . . . . . . . . . . . . . . . . Adaptive Multi-Rate (AMR) . . . . . . . . . . . . . . . . GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . GPRS Seamless Cell Reselection . . . . . . . . . . . . . . Current Bucket Level (CBL) feature . . . . . . . . . . . . Enhanced Scheduling . . . . . . . . . . . . . . . . . . . Intelligent Multilayer Resource Management (IMRM) . . . . Quality of Service (QoS). . . . . . . . . . . . . . . . . . Network Assisted Cell Change (NACC) . . . . . . . . . . Enhanced Multi-level Precedence and Pre-emption (eMLPP) . Fast Call Setup . . . . . . . . . . . . . . . . . . . . . . RSL Congestion Control . . . . . . . . . . . . . . . . . . VersaTRAU. . . . . . . . . . . . . . . . . . . . . . . . Feature Capacity Licensing and Audit . . . . . . . . . . . Improved Timeslot Sharing . . . . . . . . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

2-55 2-59 2-62 2-64 2-69 2-73 2-82 2-85 2-94 2-99 2-100 2-109 2-120 2-124 2-138 2-149 2-151 2-154 2-156 2-161 2-171 2-181 2-185 2-189 2-191 2-194 2-197 2-198

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


Configuring a network instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring an OMC-R or MSC instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 3-7

Chapter 4: Configuring a BSS/RXCDR


Overview of adding a BSS or RXCDR . . . . . . . . . . . . . . . . . . Creating a BSS using the OMC-R GUI . . . . . . . . . . . . . . . . . . Creating an RXCDR using the OMC-R GUI . . . . . . . . . . . . . . . Configuring the packet switch/MUX for a BSS . . . . . . . . . . . . . . Creating a BSS/RXCDR database . . . . . . . . . . . . . . . . . . . . Deleting a BSS/RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a BSS/RXCDR at the packet switch/MUX . . . . . . . . . . . . Equipping cabinets and cages at a BSS site . . . . . . . . . . . . . . . . Configuring a cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring a cage . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring an RXCDR cabinet . . . . . . . . . . . . . . . . . . . . . Configuring an RXCDR cage . . . . . . . . . . . . . . . . . . . . . . Example of equipping an RXCDR cabinet and cage using the TTY interface Configuring an Assoc_BSS . . . . . . . . . . . . . . . . . . . . . . . Configuring an Assoc_RXCDR . . . . . . . . . . . . . . . . . . . . . Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR. . . . . . . . . Configuring DYNETs and DYNETGroups . . . . . . . . . . . . . . . . Configuring a DYNETGroup. . . . . . . . . . . . . . . . . . . . . . . Configuring a DYNET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 4-7 4-43 4-45 4-47 4-50 4-54 4-57 4-60 4-65 4-68 4-70 4-72 4-75 4-79 4-88 4-99 4-102 4-104

ii

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Contents

Reparenting a BSS . . . . . . . . . . . . . . . . . . . Reparenting a BSS to a different OMC-R . . . . . . . . . Reparenting a BSS to a different RXCDR (same OMC-R) . Reparenting an RXCDR to a different MSC . . . . . . . . Checking the software version for a BSS/RXCDR/OMC-R.

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

4-110 4-112 4-115 4-117 4-119

Chapter 5: Configuring Connectivity


Checking BSS to MSC (Through RXCDR) connectivity . Configuring a Conn_Link . . . . . . . . . . . . . . . Configuring a CommsLink using the OMC-R GUI. . . . Checking RXCDR/BSS to OMC-R (OML) connectivity . DTE X.121 addresses at the OMC-R . . . . . . . . . . Assigning DTE X.121 addresses at the NE . . . . . . . Modifying configurations on A, M, and Mobis interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 5-6 5-11 5-16 5-18 5-21 5-24

Chapter 6: Configuring a PCU for GPRS


Introduction to the PCU and its devices . . . . . . . . . . . Overview of configuring a PCU and its devices . . . . . . . Configuring a PCU using the OMC-R GUI . . . . . . . . . Displaying and modifying PCU cabinet details . . . . . . . Displaying and modifying PCU cage details . . . . . . . . . Configuring a DPROC using the OMC-R GUI . . . . . . . Displaying and modifying PSP details . . . . . . . . . . . Configuring a PCU MSI using the OMC-R GUI . . . . . . . Displaying and modifying PCU MMS details . . . . . . . . Configuring a GDS using the OMC-R GUI . . . . . . . . . Configuring a GSL using the OMC-R GUI . . . . . . . . . Configuring a GBL using the OMC-R GUI . . . . . . . . . Configuring an NSVC using the OMC-R GUI . . . . . . . . Configuring an SGSN (GPRS) using the OMC-R GUI . . . . Configuring the PCU and its devices from the TTY interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 6-7 6-11 6-21 6-22 6-23 6-27 6-30 6-34 6-36 6-40 6-44 6-51 6-58 6-61

Chapter 7: Configuring a Site


Introduction to BSC and BTS sites . . . . . . . . . . . . . . Overview of adding a BTS . . . . . . . . . . . . . . . . . . Adding a BTS using a batch rlogin script . . . . . . . . . . . Adding a BTS using the TTY interface (example 1) . . . . . . Adding a BTS using the TTY interface (example 2) . . . . . . Creating a SITE using the OMC-R GUI . . . . . . . . . . . . Modifying SITE parameters . . . . . . . . . . . . . . . . . Equipping cabinets and cages at a remote BTS . . . . . . . . Deleting and unequipping TCU/CTU cabinets . . . . . . . . . Extending an existing path to a new site using the TTY interface GCLK synchronization . . . . . . . . . . . . . . . . . . . Checking GCLK synchronisation for a site . . . . . . . . . . Barring calls at a site using the TTY interface . . . . . . . . . Checking the hardware deployed at each site . . . . . . . . . Checking key site parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 7-12 7-14 7-17 7-23 7-28 7-36 7-38 7-41 7-42 7-45 7-54 7-56 7-57 7-60

Chapter 8: Configuring Cells


General information for configuring cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

68P02901W17-R 14 Apr 2006

GMR-01

iii

Contents

Adding a cell (recommended procedure) . . . . . . . . . . . . Adding a cell using the copy/change method . . . . . . . . . . Adding a cell using the TTY interface . . . . . . . . . . . . . Adding a cell using the OMC-R GUI . . . . . . . . . . . . . . General cell parameter section . . . . . . . . . . . . . . . . . Handover cell parameter section . . . . . . . . . . . . . . . . Power control cell parameter section . . . . . . . . . . . . . . GPRS cell parameter section . . . . . . . . . . . . . . . . . . Propagating cell parameters . . . . . . . . . . . . . . . . . . Deleting a cell. . . . . . . . . . . . . . . . . . . . . . . . . Defining algorithms . . . . . . . . . . . . . . . . . . . . . . Modifying default algorithms using the OMC-R GUI . . . . . . Modifying default algorithms using the TTY interface . . . . . . Neighbours, Sources and Reciprocal Neighbours . . . . . . . . Viewing Sources, Neighbours and Reciprocals . . . . . . . . . Creating and deleting Sources, Neighbours and Reciprocals . . . Creating neighbours using Neighbour Detailed View. . . . . . . Modifying a neighbour . . . . . . . . . . . . . . . . . . . . Deleting neighbours using the Navigation Tree Delete option . . . Neighbour templates. . . . . . . . . . . . . . . . . . . . . . Configuring a UTRAN neighbour . . . . . . . . . . . . . . . UTRAN blind search neighbour . . . . . . . . . . . . . . . . Proxy cells . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring a single proxy cell . . . . . . . . . . . . . . . . . Autocreation of a proxy cell . . . . . . . . . . . . . . . . . . Configuring multiple proxy cells using cmutil . . . . . . . . . . Exporting and importing proxy cell information between OMC-Rs Synchronizing all OMC-R proxy cells within a network . . . . . Dynamic propagation of proxy cell data to OMC-Rs . . . . . . . Expanding the capacity of a cell . . . . . . . . . . . . . . . . Configuring frequency hopping . . . . . . . . . . . . . . . . Configuring frequency hopping using the OMC-R GUI . . . . . Configuring frequency hopping using the TTY interface . . . . . Checking frequency hopping configuration for cells . . . . . . . Configuring a cell with BCCH and SDCCH in the EGSM band . . Configuring a cell for coincident multiband handovers . . . . . . Configuring a cell for adaptive handovers . . . . . . . . . . . . Configuring a neighbour cell for adaptive handovers . . . . . . . Limiting Ping-Pong handovers between cell zones . . . . . . . . Configuring a cell for flexible neighbour cell processing . . . . . Configuring enhanced SDCCH to TCH band assignment . . . . . Configuring a cell for extended cell range prioritization . . . . . Configuring a cell for power control optimization . . . . . . . . Configuring a cell for multiple GPRS carriers . . . . . . . . . . Changing a BCCH carrier frequency . . . . . . . . . . . . . . Changing a non-BCCH carrier frequency . . . . . . . . . . . . Changing a BSIC . . . . . . . . . . . . . . . . . . . . . . . Changing a TSC for a BCCH. . . . . . . . . . . . . . . . . . Propagating TSC updates . . . . . . . . . . . . . . . . . . . Assigning a quality of 7 to missing measurement reports . . . . . Changing the number of allocated SDCCHs . . . . . . . . . . . Establishing a cell boundary by changing transmit power. . . . . Setting all channels at full power . . . . . . . . . . . . . . . . Barring calls at a cell . . . . . . . . . . . . . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

8-6 8-8 8-10 8-11 8-14 8-50 8-67 8-74 8-83 8-106 8-108 8-109 8-113 8-121 8-124 8-129 8-134 8-144 8-145 8-147 8-149 8-153 8-155 8-157 8-161 8-165 8-166 8-172 8-174 8-175 8-177 8-179 8-187 8-190 8-192 8-194 8-198 8-203 8-206 8-208 8-212 8-215 8-217 8-222 8-228 8-231 8-234 8-236 8-238 8-240 8-242 8-253 8-255 8-257

iv

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Contents

Changing LAC and/or CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing and editing the SMS-CB message using the OMC-R GUI . . . . . . . . . . . . . . . . . . . .

8-260 8-262

Chapter 9: Configuring Devices and Functions


Methods of configuring individual devices and functions . . . . . Methods of configuring multiple devices and functions. . . . . . Checking the hardware version/serial number/FRU . . . . . . . Reassigning SITE, MTL, and CBL devices between GPROCs . . Displaying Channel and Circuit Status . . . . . . . . . . . . . Hierarchy of devices and functions . . . . . . . . . . . . . . . Configuring a BSP device . . . . . . . . . . . . . . . . . . . Configuring a BTP device . . . . . . . . . . . . . . . . . . . Configuring a CBL . . . . . . . . . . . . . . . . . . . . . . Configuring a CIC. . . . . . . . . . . . . . . . . . . . . . . Configuring a COMB device . . . . . . . . . . . . . . . . . . Configuring a CSFP device . . . . . . . . . . . . . . . . . . Configuring a DHP device . . . . . . . . . . . . . . . . . . . Configuring a DRI . . . . . . . . . . . . . . . . . . . . . . Reassigning a DRI device . . . . . . . . . . . . . . . . . . . Remotely calibrating DRIs . . . . . . . . . . . . . . . . . . . Creating a standard configuration for DRI calibration . . . . . . Remotely calibrating DRIs from the OMC-R . . . . . . . . . . Managing existing standard configurations . . . . . . . . . . . Configuring an EAS device . . . . . . . . . . . . . . . . . . User-definable EAS BSC/BSS and BTS alarm strings . . . . . . Defining EAS alarms in the alarm table using the TTY interface . Changing EAS alarms in the alarms table using the TTY interface Creating an EAS device using the OMC-R GUI . . . . . . . . . Configuring an EAS using the TTY interface . . . . . . . . . . Configuring the EAS physical relay states using the TTY interface Configuring a GCLK device . . . . . . . . . . . . . . . . . . Configuring a GPROC device . . . . . . . . . . . . . . . . . Configuring a KSWpair device . . . . . . . . . . . . . . . . . Configuring a KSW (or DSW) device. . . . . . . . . . . . . . Configuring an LCF function. . . . . . . . . . . . . . . . . . Configuring an LMTL device . . . . . . . . . . . . . . . . . Modifying LMTL loadsharing granularity . . . . . . . . . . . . Configuring an MSI device . . . . . . . . . . . . . . . . . . Configuring Enhanced GDP provisioning . . . . . . . . . . . . Configuring an MTL device . . . . . . . . . . . . . . . . . . Modifying MTL loadsharing granularity . . . . . . . . . . . . Configuring an OMF function . . . . . . . . . . . . . . . . . Configuring an OML device . . . . . . . . . . . . . . . . . . Configuring a path device . . . . . . . . . . . . . . . . . . . Creating a path . . . . . . . . . . . . . . . . . . . . . . . . Deleting a path . . . . . . . . . . . . . . . . . . . . . . . . Extending and reparenting a path . . . . . . . . . . . . . . . . Checking path connectivity . . . . . . . . . . . . . . . . . . Configuring an RSL device . . . . . . . . . . . . . . . . . . Configuring an RTF function . . . . . . . . . . . . . . . . . . Creating an RTF function . . . . . . . . . . . . . . . . . . . Deleting an RTF. . . . . . . . . . . . . . . . . . . . . . . . Configuring an XBL device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 9-9 9-11 9-15 9-21 9-30 9-37 9-41 9-45 9-48 9-50 9-56 9-61 9-66 9-80 9-82 9-88 9-98 9-104 9-106 9-108 9-110 9-111 9-113 9-118 9-119 9-120 9-124 9-128 9-131 9-135 9-139 9-142 9-145 9-155 9-162 9-165 9-168 9-170 9-172 9-174 9-181 9-183 9-185 9-187 9-194 9-198 9-209 9-213

68P02901W17-R 14 Apr 2006

GMR-01

Contents

Chapter 10: Auditing


Introduction to auditing . . . . . . . . . . . . . . . . Auditing recommendations. . . . . . . . . . . . . . . Auditing the network using the OMC-R GUI . . . . . . Auditing a BSS/RXCDR using the OMC-R GUI. . . . . Multiple site audits . . . . . . . . . . . . . . . . . . Multiple BSS/RXCDR audits . . . . . . . . . . . . . Scheduling an audit . . . . . . . . . . . . . . . . . . Managing audit logs . . . . . . . . . . . . . . . . . . Propagating cell changes to neighbour cells after an audit Time of the last audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 10-10 10-14 10-17 10-21 10-22 10-23 10-35 10-41 10-44

Chapter 11: Network Expansion


Introduction to network expansion . . . . . . . . . . . . . . . . . . . . Copying and pasting a BTS . . . . . . . . . . . . . . . . . . . . . . . Reparenting a BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network expansion in a daisy chain configuration . . . . . . . . . . . . . Deleting a Site in a daisy chain configuration . . . . . . . . . . . . . . . Copying a site and inserting it in a daisy chain configuration . . . . . . . . Troubleshooting Network expansion . . . . . . . . . . . . . . . . . . . Scheduling network expansion . . . . . . . . . . . . . . . . . . . . . . Network expansion logs . . . . . . . . . . . . . . . . . . . . . . . . . Managing network expansion logs . . . . . . . . . . . . . . . . . . . . Configuring a path using Path Configure menu option . . . . . . . . . . . Initiating a path configure . . . . . . . . . . . . . . . . . . . . . . . . Creating a path using the Path Configure menu option . . . . . . . . . . . Deleting a path using the Path Configure menu option . . . . . . . . . . . Unassigning a device on a path using Path Configure menu option . . . . . Reassigning a device on the primary path using Path Configure menu option Reassigning an RTF on the secondary path . . . . . . . . . . . . . . . . Deleting a device from a site using Path Configure menu option . . . . . . Creating an RTF at a site using the Path Configure menu option . . . . . . Creating an RSL at a site using the Path Configure menu option . . . . . . Using flat files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 11-6 11-22 11-35 11-39 11-40 11-47 11-54 11-57 11-71 11-77 11-78 11-81 11-85 11-86 11-90 11-92 11-94 11-96 11-97 11-98 11-99

Chapter 12: CellXchange


Guidelines for implementing a new frequency plan Introduction to CellXchange . . . . . . . . . . . Cell-X-Export. . . . . . . . . . . . . . . . . . Cell-X-Import. . . . . . . . . . . . . . . . . . Defining CellXchange parameters from the GUI. . CellXchange using the command line . . . . . . . CellXchange command line utilities . . . . . . . Troubleshooting Cell-X-Import. . . . . . . . . . CellXchange import and export tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2 12-5 12-9 12-18 12-29 12-36 12-45 12-54 12-55

Chapter 13: Manipulating Maps


Adding and deleting a user-defined regional map Adding and changing a background to a map . . Adding and deleting a map node . . . . . . . . Adding and deleting a map link. . . . . . . . .
vi

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

13-2 13-4 13-7 13-12

GMR-01

68P02901W17-R 14 Apr 2006

Contents

Chapter 14: Optimizing the Network


Overview of optimization . . . . . . . . . . . . . . . . Preparing for optimization . . . . . . . . . . . . . . . . Checking and changing the current network status . . . . . Collecting information about the current network . . . . . Checking for and rectifying Out Of Service (OOS) devices . Checking for and rectifying hardware defects . . . . . . . Checking for and rectifying database errors . . . . . . . . Using call trace to detect problems . . . . . . . . . . . . Monitoring network changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2 14-4 14-5 14-8 14-9 14-10 14-11 14-15 14-16

Chapter 15: cmutil


Introduction to cmutil . . . . . . . . . . . . . . . cmutil command syntax . . . . . . . . . . . . . . ASCII file content used with cmutil. . . . . . . . . ASCII file rules used with cmutil . . . . . . . . . . Object definition in cmutil ASCII files . . . . . . . cmutil status messages . . . . . . . . . . . . . . . cmutil script files . . . . . . . . . . . . . . . . . Using cmutil to add, delete and modify CM MIB data Ways of extracting data from the CM MIB . . . . . Extracting data from the CM MIB using cmutil . . . Extracting data from the CM MIB using SQL . . . . Configuring CommsLinks using cmutil . . . . . . . Configuring multiple proxy cells using cmutil . . . . Checking paths using cmutil . . . . . . . . . . . . Managing maps using cmutil . . . . . . . . . . . . Using cmutil to perform other specific tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2 15-5 15-7 15-10 15-12 15-17 15-18 15-20 15-29 15-30 15-35 15-42 15-44 15-46 15-50 15-58

68P02901W17-R 14 Apr 2006

GMR-01

vii

Contents

This page intentionally left blank.

viii

GMR-01

68P02901W17-R 14 Apr 2006

List of Figures

List of Figures

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

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 . . . . . . . . . . . . . . . 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 buttons . Sources and Neighbours View window in Monitor mode . . . . . . . . . Power budget algorithm prompt . . . . . . . . . . . . . . . . . . . . . Neighbour 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 . . . . . . . . . . . Hierarchy for SITE devices and functions . . . . . . . . . . . . . . . . Hierarchy for Hardware Devices . . . . . . . . . . . . . . . . . . . . Hierarchy for Software Functions at BSC only . . . . . . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

1-17 1-43 1-47 1-48 1-49 2-6 2-8 2-10 4-8 4-48 4-49 4-91 4-94 4-95 4-96 5-13 5-20 6-4 6-5 7-2 7-3 7-17 7-22 7-23 7-25 7-28 7-43 8-13 8-105 8-110 8-126 8-131 8-131 8-183 8-185 8-229 9-24 9-28 9-30 9-31 9-32 9-33
ix

68P02901W17-R 14 Apr 2006

GMR-01

List of Figures

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

9-34 9-35 9-35 9-36 9-51 9-52 9-68 9-81 9-91 9-92 9-100 9-102 9-114 9-172 11-8 11-11 11-14 11-18 11-21 11-28 11-29 11-34 11-37 11-41 11-42 11-45 11-49 11-50 11-60 11-68 11-72 11-73 11-82 11-88 11-102 12-10 12-12 12-19 12-21 12-30 12-34 15-47 15-49

GMR-01

68P02901W17-R 14 Apr 2006

List of Tables

List of Tables

Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2: Service requests resolved in this manual . . . . . . . . . . . . . . . . . . . . . . Table 3: CDCNs incorporated in this manual . . . . . . . . . . . . . . . . . . . . . . . . Table 1-1: Recommended CM command partitioning configuration . . . . . . . . . . . . . . Table 1-2: Same day omcaudit log file naming convention . . . . . . . . . . . . . . . . . . Table 1-3: Vanguard router required software loads . . . . . . . . . . . . . . . . . . . . . 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 signalling 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 for EGSM and non-EGSM enabled systems . . . . . . . Table 2-30: Per-call Preferred Band (PCPB) settings . . . . . . . . . . . . . . . . . . . . . Table 2-31: Summary of band preference modes and their associated behaviours. . . . . . . . Table 2-32: Assignment and Handover band selection algorithms for the band preference modes Table 2-33: Intelligent Multilayer Resource Management parameters . . . . . . . . . . . . . Table 2-34: Quality of Service parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W17-R 14 Apr 2006

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

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

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

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

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

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

4 5 5 1-8 1-9 1-12 1-26 1-27 2-17 2-18 2-22 2-25 2-32 2-41 2-48 2-59 2-60 2-65 2-74 2-83 2-86 2-87 2-92 2-96 2-102 2-110 2-118 2-121 2-124 2-127 2-138 2-142 2-150 2-152 2-155 2-157 2-163 2-164 2-165 2-165 2-168 2-172
xi

GMR-01

List of Tables

Table 2-35: Network Assisted Cell Change (NACC) parameters . . . . . . . . . . . . . . . . . . Table 2-36: Enhanced Multi-level Precedence and Pre-emption (eMLPP) parameters. . . . . . . . . Table 2-37: Fast Call Setup parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-38: RSL congestion control parameters . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-39: Possible values for RFT field: Number of Backhaul Timeslots on Carrier (rtf_ds0_count) . Table 2-40: VersaTRAU parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-41: ITS parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-1: Network Detailed View fields - Identification grouping . . . . . . . . . . . . . . . . . Table 3-2: Network Detailed View fields - State grouping . . . . . . . . . . . . . . . . . . . . . Table 3-3: Network Detailed View fields - Map Information grouping. . . . . . . . . . . . . . . . Table 3-4: OMC and MSC Detailed View fields - Identification grouping . . . . . . . . . . . . . . Table 4-1: BSS Detailed View fields - Identification grouping . . . . . . . . . . . . . . . . . . . Table 4-2: BSS Detailed View fields - State grouping . . . . . . . . . . . . . . . . . . . . . . . Table 4-3: BSS Detailed View fields - Network Addresses grouping . . . . . . . . . . . . . . . . Table 4-4: BSS Detailed View fields - Optional Features grouping . . . . . . . . . . . . . . . . . Table 4-5: BSS Detailed View fields - Signalling Information grouping . . . . . . . . . . . . . . . Table 4-6: BSS Detailed View fields - A5 Algorithms grouping. . . . . . . . . . . . . . . . . . . Table 4-7: BSS Detailed View fields - General grouping . . . . . . . . . . . . . . . . . . . . . . Table 4-8: BSS Detailed View fields - PCS 1900 Frequency grouping . . . . . . . . . . . . . . . . Table 4-9: BSS Detailed View fields - Flash Information grouping . . . . . . . . . . . . . . . . . Table 4-10: BSS Detailed View fields - Trunk Information grouping . . . . . . . . . . . . . . . . Table 4-11: BSS Detailed View fields - Directed Retry grouping . . . . . . . . . . . . . . . . . . Table 4-12: BSS Detailed View fields - Multiband grouping . . . . . . . . . . . . . . . . . . . . Table 4-13: BSS Detailed View fields - Enhanced Full Rate grouping . . . . . . . . . . . . . . . . Table 4-14: BSS Detailed View fields - GPRS grouping . . . . . . . . . . . . . . . . . . . . . . Table 4-15: BSS Detailed View fields - Map Information grouping . . . . . . . . . . . . . . . . . Table 4-16: BSS Detailed View fields - Traffic Parameters grouping . . . . . . . . . . . . . . . . Table 4-17: BSS Detailed View fields - Network Assisted Cell Change grouping . . . . . . . . . . Table 4-18: BSS Detailed View fields - GPRS Seamless Cell Reselection grouping . . . . . . . . . Table 4-19: Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping . . . . . Table 4-20: Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping . . . . . Table 4-21: BSS Detailed View fields - Improved Timeslot Sharing. . . . . . . . . . . . . . . . . Table 4-22: Extension cabinets for Horizon II macro . . . . . . . . . . . . . . . . . . . . . . . . Table 4-23: Cabinet types allowing Horizon II macro_ext as an extension type . . . . . . . . . . . Table 4-24: Extension cabinet types allowed for Horizon II mini . . . . . . . . . . . . . . . . . . Table 4-25: Master cabinet types allowed for Horizon II mini extension . . . . . . . . . . . . . . . Table 4-26: Cabinet Detailed View fields - Identification grouping . . . . . . . . . . . . . . . . . Table 4-27: Cabinet Detailed View fields - General grouping . . . . . . . . . . . . . . . . . . . . Table 4-28: Cage Detailed View fields - Identification grouping . . . . . . . . . . . . . . . . . . Table 4-29: Assoc_BSS Detailed View fields - Identification grouping . . . . . . . . . . . . . . . Table 4-30: Assoc_BSS Detailed View fields - General grouping . . . . . . . . . . . . . . . . . . Table 4-31: Assoc_RXCDR Detailed View fields - Identification grouping . . . . . . . . . . . . . Table 4-32: Assoc_RXCDR Detailed View fields - Local Routing Information grouping . . . . . . . Table 4-33: Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping . . . . . Table 4-34: DYNETGroup Detailed View fields - Identification grouping . . . . . . . . . . . . . . Table 4-35: DYNET Detailed View fields - Identification grouping . . . . . . . . . . . . . . . . . Table 4-36: DYNET Detailed View fields - Local Routing Information grouping . . . . . . . . . . Table 4-37: DYNET Detailed View fields - path Information grouping . . . . . . . . . . . . . . . Table 5-1: Example Connection report for BSS1015 . . . . . . . . . . . . . . . . . . . . . . . . Table 5-2: Conn_Link Detailed View fields - Identification grouping . . . . . . . . . . . . . . . . Table 5-3: Conn_Link Detailed View fields - Connectivity Information grouping . . . . . . . . . . Table 5-4: CommsLink Detailed View fields - Identification grouping . . . . . . . . . . . . . . . Table 5-5: CommsLink Detailed View fields - Map Information grouping . . . . . . . . . . . . . . Table 5-6: Slot: port settings for OML link . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

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

2-183 2-187 2-190 2-192 2-195 2-196 2-199 3-4 3-6 3-6 3-9 4-10 4-12 4-13 4-14 4-19 4-21 4-21 4-29 4-29 4-30 4-31 4-32 4-33 4-34 4-36 4-37 4-37 4-38 4-38 4-40 4-41 4-58 4-58 4-59 4-59 4-61 4-63 4-66 4-77 4-77 4-81 4-81 4-82 4-103 4-106 4-106 4-107 5-2 5-7 5-8 5-14 5-14 5-21

xii

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

List of Tables

Table 6-1: PCU contained devices . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-2: PCU Detailed View fields - Identification grouping . . . . . . . . . . . . . . Table 6-3: PCU Detailed View fields - Alarm Information grouping. . . . . . . . . . . . Table 6-4: PCU Detailed View fields - BSSGP Information grouping . . . . . . . . . . . Table 6-5: PCU Detailed View fields - Gb Mapping Information grouping. . . . . . . . . Table 6-6: PCU Detailed View fields - Gb Statistics Configuration grouping. . . . . . . . Table 6-7: PCU Detailed View fields - NS Information grouping . . . . . . . . . . . . . Table 6-8: PCU Detailed View fields - Address Information grouping . . . . . . . . . . . Table 6-9: DPROC Detailed View fields - Identification grouping . . . . . . . . . . . . Table 6-10: PSP Detailed View fields - Identification grouping . . . . . . . . . . . . . . Table 6-11: PSP Detailed View fields - Cage and Slot Information grouping . . . . . . . . Table 6-12: PCU MSI Detailed View fields - Identification grouping . . . . . . . . . . . Table 6-13: PCU MSI Detailed View fields - Cage and Slot Information grouping . . . . . Table 6-14: GDS Detailed View fields - Identification grouping . . . . . . . . . . . . . Table 6-15: GDS Detailed View fields - Connectivity Information grouping . . . . . . . . Table 6-16: gsl_lcf_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-17: GSL Detailed View fields - Identification grouping. . . . . . . . . . . . . . Table 6-18: GBL Detailed View fields - Identification grouping . . . . . . . . . . . . . Table 6-19: GBL Detailed View fields - Connectivity Information grouping . . . . . . . . Table 6-20: GBL Detailed View fields - Frame Relay Information grouping . . . . . . . . Table 6-21: NSVC Detailed View fields - Identification grouping . . . . . . . . . . . . . Table 6-22: NSVC Detailed View fields - NS Information grouping. . . . . . . . . . . . Table 6-23: SGSN Detailed View fields - Identification grouping . . . . . . . . . . . . . Table 7-1: Default RSLs - Timeslots and Cages . . . . . . . . . . . . . . . . . . . . . Table 7-2: Default RSLs - Timeslots and Card frame for Horizon II macro Site . . . . . . Table 7-3: Default RSLs - Timeslots and Card frame for non Horizon II macro Site . . . . Table 7-4: SITE Detailed View fields - Identification grouping . . . . . . . . . . . . . . Table 7-5: SITE Detailed View fields - General grouping. . . . . . . . . . . . . . . . . Table 7-6: SITE Detailed View fields - SMS Information grouping . . . . . . . . . . . . Table 7-7: SITE Detailed View fields - GPRS grouping . . . . . . . . . . . . . . . . . Table 7-8: BSS commands for GCLK synchronization . . . . . . . . . . . . . . . . . . Table 7-9: BSS parameters for GCLK synchronization . . . . . . . . . . . . . . . . . . Table 8-1: CELL Detailed View, General - Identification grouping . . . . . . . . . . . . Table 8-2: CELL Detailed View fields, General - General grouping . . . . . . . . . . . . Table 8-3: CELL Detailed View fields, General - System Access grouping . . . . . . . . Table 8-4: CELL Detailed View fields, General - Cell Selection/Reselection grouping . . . Table 8-5: CELL Detailed View fields, General - Radio Channel Config grouping . . . . . Table 8-6: CELL Detailed View fields, General - Queuing grouping . . . . . . . . . . . Table 8-7: CELL Detailed View fields, General - Flow Control grouping . . . . . . . . . Table 8-8: CELL Detailed View fields, general - channel allocation-deallocation grouping . Table 8-9: CELL Detailed View fields, general - radio link control grouping. . . . . . . . Table 8-10: CELL Detailed View fields, general - congestion relief grouping . . . . . . . Table 8-11: CELL Detailed View fields, general - directed retry grouping . . . . . . . . . Table 8-12: CELL Detailed View fields, general - multiband handover grouping . . . . . . Table 8-13: Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping Table 8-14: CELL Detailed View fields, General - AMR full rate grouping . . . . . . . . Table 8-15: CELL Detailed View fields, General - AMR/GSM Half Rate grouping . . . . Table 8-16: CELL Detailed View fields, General - AMR/GSM Half Rate grouping . . . . Table 8-17: CELL Detailed View, Handover - Handover - General grouping. . . . . . . . Table 8-18: CELL Detailed View, Handover - Handover Thresholds grouping . . . . . . . Table 8-19: CELL Detailed View, Handover - Handover types allowed grouping. . . . . . Table 8-20: CELL Detailed View, Handover - Handover Timer grouping . . . . . . . . . Table 8-21: CELL Detailed View, Handover - Uplink RxQual Handover grouping . . . . . Table 8-22: CELL Detailed View, Handover - Downlink RxQual handover grouping . . . .

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

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

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

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

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

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

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

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

6-6 6-13 6-14 6-15 6-16 6-17 6-18 6-19 6-25 6-28 6-29 6-31 6-32 6-38 6-38 6-40 6-42 6-46 6-47 6-48 6-53 6-54 6-59 7-6 7-6 7-6 7-30 7-31 7-34 7-35 7-47 7-49 8-14 8-16 8-18 8-21 8-22 8-24 8-25 8-26 8-27 8-28 8-30 8-31 8-36 8-36 8-42 8-49 8-50 8-52 8-53 8-54 8-55 8-57

68P02901W17-R 14 Apr 2006

GMR-01

xiii

List of Tables

Table 8-23: CELL Detailed View, Handover - Uplink RxLev Handover grouping . . . . Table 8-24: CELL Detailed View, Handover - Downlink RxLev Handover grouping . . . Table 8-25: CELL Detailed View, Handover - Uplink Interference Handover grouping . . Table 8-26: CELL Detailed View, Handover - Downlink Interference Handover grouping Table 8-27: CELL Detailed View, Handover - Distance Handover grouping . . . . . . . Table 8-28: CELL Detailed View, Handover - Power Budget Handover grouping . . . . Table 8-29: CELL Detailed View, Handover - SDCCH Handover grouping . . . . . . . Table 8-30: CELL Detailed View, Handover - Handover - AMR Full Rate grouping . . . Table 8-31: CELL Detailed View, Handover - Handover - AMR/GSM Half Rate grouping Table 8-32: CELL Detailed View, Power Control - Power Control - General grouping . . Table 8-33: CELL Detailed View, Power Control - Rapid MS Power Down grouping . . Table 8-34: CELL Detailed View, Power Control - Uplink Power Control grouping . . . Table 8-35: CELL Detailed View, Power Control - Downlink Power Control grouping . . Table 8-36: CELL Detailed View, Pwr Ctrl - Pwr Ctrl - AMR Full Rate grouping . . . . Table 8-37: CELL Detailed View, Pwr Ctrl - Pwr Ctrl - AMR/GSM Half Rate grouping . Table 8-38: CELL Detailed View, GPRS grouping . . . . . . . . . . . . . . . . . . . Table 8-39: CELL Detailed View fields, GPRS - Ntwk Ctrld Cell Reselection grouping . Table 8-40: GSM cell propagation parameters . . . . . . . . . . . . . . . . . . . . Table 8-41: GSM cell propagation parameters with GSM Half Rate unrestricted . . . . . Table 8-42: Algorithm Detailed View - Identification grouping . . . . . . . . . . . . . Table 8-43: Algorithm Detailed View - General grouping . . . . . . . . . . . . . . . Table 8-44: chg_cell_element rel_tim_adv and chg_cell_element surround_cell . . . . . Table 8-45: chg_cell_element rxlev_dl_ho and chg_cell_element rxlev_ul_ho . . . . . . Table 8-46: Neighbour Detailed View fields - Identification grouping . . . . . . . . . . Table 8-47: Neighbour Detailed View fields - General grouping . . . . . . . . . . . . Table 8-48: Neighbour Detailed View fields - Power Budget Algorithm grouping . . . . Table 8-49: Neighbour Detailed View fields - Directed Retry grouping . . . . . . . . . Table 8-50: Neighbour Detailed View fields - Concentric Cells grouping . . . . . . . . Table 8-51: UTRAN neighbour parameters and values . . . . . . . . . . . . . . . . . Table 8-52: UTRAN Blind Search Neighbour Detailed View Fields General grouping. Table 8-53: ProxyCELL Detailed View fields - Identification grouping . . . . . . . . . Table 8-54: ProxyCELL Detailed View fields - Proxy Cell Data grouping . . . . . . . . Table 8-55: Command line options for pcellImport . . . . . . . . . . . . . . . . . . Table 8-56: Frequency hopping cell parameters . . . . . . . . . . . . . . . . . . . . Table 8-57: Frequency hopping maximum frequency number. . . . . . . . . . . . . . Table 8-58: FreqHopSys Detailed View fields - Identification grouping . . . . . . . . . Table 8-59: FreqHopSys Detailed View fields - General grouping. . . . . . . . . . . . Table 8-60: Coincident multiband handover parameters . . . . . . . . . . . . . . . . Table 8-61: Adaptive handover parameters . . . . . . . . . . . . . . . . . . . . . . Table 8-62: Ping Pong limitation parameters . . . . . . . . . . . . . . . . . . . . . Table 8-63: Flexible neighbour processing parameters . . . . . . . . . . . . . . . . . Table 8-64: erc_ta_priority parameter . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-65: Optimizing cell power control parameters . . . . . . . . . . . . . . . . . Table 8-66: Timeslots on multiple GPRS carriers configured for performance . . . . . . Table 8-67: Timeslots on multiple GPRS carriers configured using OSA . . . . . . . . Table 8-68: Multiple GPRS carriers per cell parameters . . . . . . . . . . . . . . . . Table 8-69: rpt_bad_qual_no_mr parameter . . . . . . . . . . . . . . . . . . . . . . Table 8-70: SDCCH parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-71: SDCCH parameters with combined channel configurations . . . . . . . . . Table 8-72: SDCCH parameters with NON-combined channel configurations . . . . . . Table 8-73: Value ranges for max_tx_bts . . . . . . . . . . . . . . . . . . . . . . . Table 8-74: SMSCBmsg Detailed View fields - Identification grouping . . . . . . . . . Table 8-75: SMSCBmsg Detailed View fields - SMS Information grouping . . . . . . . Table 9-1: VersaTRAU (VT) channel information in Channel Status form . . . . . . . .

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

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

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

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

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

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

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

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

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

8-58 8-59 8-60 8-61 8-62 8-63 8-64 8-65 8-66 8-68 8-68 8-69 8-70 8-72 8-73 8-75 8-82 8-84 8-102 8-111 8-112 8-115 8-117 8-135 8-136 8-138 8-139 8-140 8-150 8-153 8-158 8-159 8-170 8-178 8-181 8-184 8-184 8-195 8-199 8-206 8-209 8-215 8-218 8-222 8-223 8-224 8-240 8-243 8-246 8-247 8-253 8-263 8-264 9-28

xiv

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

List of Tables

Table 9-2: BSP cage and slot restrictions . . . . . . . . . . . . . . . . . . . . . Table 9-3: BSP Detailed View fields - Identification grouping . . . . . . . . . . . Table 9-4: BSP Detailed View fields - Cage and Slot Information grouping . . . . . Table 9-5: BTP cage and slot restrictions . . . . . . . . . . . . . . . . . . . . . Table 9-6: BTP Detailed View fields - Identification grouping . . . . . . . . . . . Table 9-7: BTP Detailed View fields - Cage and Slot Information grouping . . . . . Table 9-8: BTP Detailed View fields - State Information grouping . . . . . . . . . Table 9-9: CBL Detailed View fields - Identification grouping . . . . . . . . . . . Table 9-10: COMB Detailed View fields - Identification grouping . . . . . . . . . Table 9-11: GPROC cage and slot restrictions . . . . . . . . . . . . . . . . . . . Table 9-12: CSFP Detailed View fields - Identification grouping . . . . . . . . . . Table 9-13: DHP cage and slot restrictions . . . . . . . . . . . . . . . . . . . . Table 9-14: DHP Detailed View fields - Identification grouping . . . . . . . . . . Table 9-15: DHP Detailed View fields - Cage and Slot Information grouping . . . . Table 9-16: DHP Detailed View fields - State Information grouping. . . . . . . . . Table 9-17: DRI Detailed View fields - Identification grouping . . . . . . . . . . . Table 9-18: DRI Detailed View fields - Cage and Slot Information grouping. . . . . Table 9-19: DRI Detailed View fields - Additional State Information grouping. . . . Table 9-20: DRI Detailed View fields - Preferred RTF grouping . . . . . . . . . . Table 9-21: DRI Detailed View fields - DRI RCU grouping . . . . . . . . . . . . Table 9-22: DRI Detailed View fields - Combiner 1 grouping. . . . . . . . . . . . Table 9-23: DRI Detailed View fields - Shared Cells grouping . . . . . . . . . . . Table 9-24: DRI Detailed View fields - Port Connections grouping . . . . . . . . . Table 9-25: DRI Detailed View fields - Power Distribution Board grouping . . . . . Table 9-26: Bay level calibration parameters . . . . . . . . . . . . . . . . . . . Table 9-27: Rx A and Rx B receive path options. . . . . . . . . . . . . . . . . . Table 9-28: Severity level definitions . . . . . . . . . . . . . . . . . . . . . . . Table 9-29: EAS Detailed View fields - Identification grouping. . . . . . . . . . . Table 9-30: EAS Detailed View fields - Cage and Slot Information grouping . . . . Table 9-31: EAS Detailed View fields - OptoCoupler groupings . . . . . . . . . . Table 9-32: EAS Detailed View fields - Relay Information grouping . . . . . . . . Table 9-33: GCLK Detailed View fields - Identification grouping. . . . . . . . . . Table 9-34: GCLK Detailed View fields - Cage and Slot Information grouping . . . Table 9-35: GPROC cage and slot numbers . . . . . . . . . . . . . . . . . . . . Table 9-36: GPROC Detailed View fields - Identification grouping . . . . . . . . . Table 9-37: GPROC Detailed View fields - Cage and Slot Information grouping . . . Table 9-38: GPROC Detailed View fields - State Information grouping . . . . . . . Table 9-39: KSWpair Detailed View fields - Identification grouping . . . . . . . . Table 9-40: KSW Detailed View fields - Identification grouping . . . . . . . . . . Table 9-41: KSW Detailed View fields - Cage and Slot Information grouping . . . . Table 9-42: LCF Detailed View fields - Identification grouping . . . . . . . . . . . Table 9-43: LMTL parameters . . . . . . . . . . . . . . . . . . . . . . . . . . Table 9-44: LMTL Loadshare Granularity parameter. . . . . . . . . . . . . . . . Table 9-45: MSI Detailed View fields - Identification grouping . . . . . . . . . . . Table 9-46: MSI Detailed View fields - Cage and Slot Information grouping. . . . . Table 9-47: MSI Detailed View fields - MMS HDSL Information grouping . . . . . Table 9-48: Enhanced GDP Provisioning parameters. . . . . . . . . . . . . . . . Table 9-49: MTL Detailed View fields - Identification grouping . . . . . . . . . . Table 9-50: MTL Loadshare Granularity parameter . . . . . . . . . . . . . . . . Table 9-51: OMF Detailed View fields - Identification grouping . . . . . . . . . . Table 9-52: OML Detailed View fields - Identification grouping . . . . . . . . . . Table 9-53: Abis link cage timeslots . . . . . . . . . . . . . . . . . . . . . . . Table 9-54: Default RSLs - Timeslots and Card frame for Horizon II macro Site . . Table 9-55: Default RSLs - Timeslots and Card frame for non Horizon II macro Site .

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

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

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

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

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

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

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

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

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

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

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

9-37 9-39 9-40 9-42 9-43 9-44 9-44 9-46 9-54 9-57 9-58 9-61 9-63 9-64 9-64 9-72 9-75 9-75 9-76 9-76 9-77 9-78 9-79 9-79 9-86 9-93 9-108 9-115 9-116 9-117 9-117 9-122 9-123 9-124 9-126 9-126 9-127 9-129 9-133 9-133 9-136 9-140 9-143 9-147 9-149 9-150 9-157 9-163 9-166 9-169 9-171 9-177 9-177 9-177

68P02901W17-R 14 Apr 2006

GMR-01

xv

List of Tables

Table 9-56: PATH Detailed View fields - Identification grouping . . . . . . . . . . Table 9-57: PATH Detailed View fields - Path information grouping . . . . . . . . Table 9-58: RSL Detailed View fields - Identification grouping . . . . . . . . . . . Table 9-59: RSL Detailed View fields - LapD Information grouping . . . . . . . . Table 9-60: RSL Detailed View fields - MMS Timeslots grouping . . . . . . . . . Table 9-61: RTF Detailed View fields - Identification grouping . . . . . . . . . . . Table 9-62: RTF Detailed View fields - Carrier 1 Information grouping . . . . . . . Table 9-63: RTF Detailed View fields - Concentric cells grouping . . . . . . . . . Table 9-64: RTF Detailed View fields - GPRS grouping . . . . . . . . . . . . . . Table 9-65: RTF Detailed View fields - MMS Timeslot grouping . . . . . . . . . . Table 9-66: RTF Detailed View fields - General grouping . . . . . . . . . . . . . Table 9-67: RTF Detailed View fields - AMR/GSM Half Rate grouping . . . . . . . Table 9-68: XBL Detailed View fields - Identification grouping . . . . . . . . . . Table 9-69: XBL Detailed View fields - LapD Information grouping . . . . . . . . Table 10-1: Values propagated after an audit . . . . . . . . . . . . . . . . . . . Table 11-1: Example of a successful swap site LAC operation . . . . . . . . . . . Table 11-2: Example of an unsuccessful swap site LAC operation . . . . . . . . . Table 11-3: Example of an unsuccessful swap site LAC operation . . . . . . . . . Table 11-4: Reparent site - Examples of OMC Device Transition States . . . . . . . Table 11-5: Delete SITE - Examples of OMC-R Device Transition States . . . . . . Table 11-6: Default Actions when copying, deleting, reparenting a site . . . . . . . Table 12-1: RF General Options. . . . . . . . . . . . . . . . . . . . . . . . . Table 12-2: Configuration file parameters . . . . . . . . . . . . . . . . . . . . . Table 12-3: Command line options (rf_export) . . . . . . . . . . . . . . . . . . Table 12-4: Command line options (rf_import) . . . . . . . . . . . . . . . . . . Table 12-5: Command line options (rfNcheck) . . . . . . . . . . . . . . . . . . Table 12-6: Command line options (correct_rtfs) . . . . . . . . . . . . . . . . . Table 12-7: RTF attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 12-8: RFPlanCell default parameters . . . . . . . . . . . . . . . . . . . . Table 12-9: User selectable cell parameters . . . . . . . . . . . . . . . . . . . . Table 12-10: User selectable cell parameters with GSM Half Rate unrestricted. . . . Table 12-11: RFPlanNeighbour default parameters . . . . . . . . . . . . . . . . Table 12-12: User selectable Neighbour parameters . . . . . . . . . . . . . . . . Table 12-13: Site parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 12-14: DRI parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . Table 12-15: RTF parameters . . . . . . . . . . . . . . . . . . . . . . . . . . Table 15-1: FreqHopSys attribute details . . . . . . . . . . . . . . . . . . . . . Table 15-2: Path attributes link(1 ... 10) (stored outside pathtable2, in intlisttable2) . Table 15-3: Path attribute commsLinkList (stored outside pathtable2 in oidlisttable2) Table 15-4: Mangled object classes with resulting table names . . . . . . . . . . . Table 15-5: Example of OIDs mangled in OSP 4 . . . . . . . . . . . . . . . . . Table 15-6: cmutil output use of columns . . . . . . . . . . . . . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

9-179 9-180 9-189 9-190 9-191 9-199 9-201 9-203 9-204 9-205 9-206 9-207 9-215 9-217 10-42 11-24 11-24 11-24 11-33 11-38 11-66 12-31 12-39 12-46 12-47 12-50 12-51 12-52 12-57 12-58 12-71 12-72 12-73 12-74 12-78 12-79 15-38 15-38 15-39 15-40 15-40 15-48

xvi

GMR-01

68P02901W17-R 14 Apr 2006

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 so populate the Configuration Management database. This manual should be used with the OMC-R running on one of following series platforms: E3500. SunFire 4800 and SunFire 4900. Netra20. {23370} SunBlade 150. {23370} Ultra 5 platform. 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-R 14 Apr 2006

GMR-01

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 Network Elements and the OMC-R, BSS and MSC (Through an RXCDR), and 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 synchronisation. Barring calls at a site.

Chapter 8 Configuring cells This chapter describes how to configure cells, neighbours, 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. 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.

GMR-01

68P02901W17-R 14 Apr 2006

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 Optimising 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-R 14 Apr 2006

GMR-01

Issue status of this manual

Issue status of this manual


The following shows the issue status of this manual since it was first released.

Version information
The following table lists the versions of this manual in order of issue: Table 1 Manual version history Date of issue 03 Oct 1994 30 Dec 1994 01 Sep 1995 28 Mar 1997 29 Aug 1997 27 April 1998 12 Mar 1999 15 July 2000 31 Jul 2001 31 May 2002 20 Nov 2002 02 May 2003 13 Nov 2003 09 Sep 2004 14 Apr 2006 Remarks Original issue - Software release GSR 1.2.2.x. Issue A - Software release 1.2.3.x. Issue C - Software release 1.4.0.x. Issue D - Software release 1.4.1.x. Issue E - GSM Software release 2. Issue F - GSM Software release 3. Issue G - GSM Software release 4. Issue H - GSM Software release 4.1. Issue J - GSM Software release 5. Issue K - GSM Software release 5.1. Issue L - GSM Software release 6. Issue M - GSM Software release 6 (Horizon II). Issue P - GSM Software release 7. Issue Q - GSM Software release 7 Half Rate. Issue R - GSM Software release 8 (GMR-01).

Manual issue O A C D E F G H J K L M P Q R

GMR-01

68P02901W17-R 14 Apr 2006

Issue status of this manual

Resolution of service requests


The following Service Requests are now resolved in this manual: Table 2 Service requests resolved in this manual GMR Number GMR-01 Remarks Updated the following sections to incorporate default RSLs for InCell, Horizon II macro and non Horizon II macro sites: Introduction to BSC and BTS sites, see Chapter 7. Configuring a PATH device, see Chapter 9.

Service Request 2002502

Incorporation of CDCNs
The following CDCNs are now incorporated in this manual: Table 3 CDCNs incorporated in this manual GMR Number GMR-01 Remarks Issued to resolve SR 2002502.

CDCN 01W17-004

68P02901W17-R 14 Apr 2006

GMR-01

General information

General information

Motorola disclaims all liability whatsoever, implied or express, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the customers behalf, to abide by the instructions, system parameters or recommendations made in this manual. If this manual was obtained when attending a Motorola training course, it will not be updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then corrections will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs) or Customer Documentation Change Notices (CDCNs).

Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel in the operation, installation and maintenance of the Motorola cellular infrastructure equipment and ancillary devices. It is recommended that all personnel engaged in such activities be properly trained by Motorola.

Failure to comply with Motorolas operation, installation and maintenance instructions may, in exceptional circumstances, lead to serious injury or death.

These manuals are not intended to replace the system and equipment training offered by Motorola, although they can be used to supplement and enhance the knowledge gained through such training.

Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features released at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In these manuals, new and amended features are tagged to help users to assess the impact on installed networks. The tags are the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and Development Prioritization (RDP) numbers. The tags include index references which are listed in the manual Index. The Index includes the entry feature which is followed by a list of the RDB or RDP numbers for the released features, with page references and hot links in electronic copy.

GMR-01

68P02901W17-R 14 Apr 2006

General information

The tags have the format: {nnnn} or {nnnnn} Where: {nnnn} {nnnnn} The tags are positioned in text as follows: New and amended feature information Complete new sections of content as follows: All sections under a main heading. All paragraphs under subheadings. Tag position in text In the heading immediately after the heading content as follows: Single paragraphs of new or amended text. New or amended complete Figures and Tables. Warning, Caution and Notes. General command syntax, operator input (in special fonts). Computer output displays (in special fonts). Main heading {nnnn} Subheading {nnnn} is: the RDB number. the RDP number.

Immediately before the affected paragraph. After the Figure or Table number and before the title text. Immediately before the affected text in the Warning, Caution or Note. On a separate line immediately above the affected item or immediately before the affected item. On a separate line immediately above the affected item or immediately before the affected item.

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

Cross references
Throughout this manual, references are made to external publications, chapter numbers and section names. The references to external publications are shown in italics, chapter and section name cross references are emphasised blue in text. This manual is divided into uniquely identified and numbered chapters that, in turn, are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents.

68P02901W17-R 14 Apr 2006

GMR-01

General information

Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and GPRS network is encrypted. In order to comply with the export and import requirements of particular countries, this encryption occurs at different levels as individually standardised, or may not be present at all in some parts of the network in which it is normally implemented. The manual set, of which this manual is a part, covers encryption as if fully implemented. Because the rules differ in individual countries, limitations on the encryption included in the particular software being delivered, are covered in the Release Notes that accompany the individual software release.

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

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

Output
Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this.

Special key sequences


Special key sequences are represented as follows: CTRL-c ALT-f CR or RETURN Press the Control and c keys at the same time. Press the Alt and f keys at the same time. Press the pipe symbol key. Press the Return key.

GMR-01

68P02901W17-R 14 Apr 2006

Reporting safety issues

Reporting safety issues


Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all site personnel are familiar with this procedure.

Procedure
Whenever a safety issue arises: Procedure 1 1 2 3 Safety issue reporting Make the equipment concerned safe, for example by removing power. Make no further attempt to adjust or rectify the equipment. Report the problem directly to the Customer Network Resolution Centre, Swindon +44 (0)1793 565444 or China +86 10 88417733 (telephone) and follow up with a written report by fax, Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax). Collect evidence from the equipment under the guidance of the Customer Network Resolution Centre.

68P02901W17-R 14 Apr 2006

GMR-01

Warnings and cautions

Warnings and cautions


The following describes how warnings and cautions are used in this manual and in all manuals of this Motorola manual set.

Warnings
A definition and example follow below:

Definition of warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents, as well as those inherent in the equipment.

Example and format

Do not look directly into fibre optic cables or data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.

Failure to comply with warnings


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

Cautions
A definition and example follow below:

10

GMR-01

68P02901W17-R 14 Apr 2006

Warnings and cautions

Definition of caution
A caution means that there is a possibility of damage to systems, software or individual items of equipment within a system. However, this presents no danger to personnel.

Example and format

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

68P02901W17-R 14 Apr 2006

GMR-01

11

General warnings

General warnings

Observe the following specific warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola manuals: Potentially hazardous voltage. Electric shock. RF radiation. Laser radiation. Heavy equipment. Parts substitution. Battery supplies. Lithium batteries.

Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.

Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning labels must not be removed, painted over or obscured in any way.

Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will be incorporated into procedures as applicable. These must be observed by all personnel at all times when working with the equipment, as must any other warnings given in text, in the illustrations and on the equipment.

12

GMR-01

68P02901W17-R 14 Apr 2006

General warnings

Potentially hazardous voltage

This equipment operates from a potentially hazardous voltage of 230 V ac single phase or 415 V ac three phase supply. To achieve isolation of the equipment from the ac supply, the ac input isolator must be set to off and locked. When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989 (UK), or to the relevant electricity at work legislation for the country in which the equipment is used.

Motorola GSM equipment does not utilise high voltages.

Electric shock

Do not touch the victim with your bare hands until the electric circuit is broken. Switch off. If this is not possible, protect yourself with dry insulating material and pull or push the victim clear of the conductor. ALWAYS send for trained first aid or medical assistance IMMEDIATELY. In cases of low voltage electric shock (including public supply voltages), serious injuries and even death, may result. Direct electrical contact can stun a casualty causing breathing, and even the heart, to stop. It can also cause skin burns at the points of entry and exit of the current. In the event of an electric shock it may be necessary to carry out artificial respiration. If the casualty is also suffering from burns, flood the affected area with cold water to cool, until trained first aid or medical assistance arrives.

RF radiation

High RF potentials and electromagnetic fields are present in this equipment when in operation. Ensure that all transmitters are switched off when any antenna connections have to be changed. Do not key transmitters connected to unterminated cavities or feeders. Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are: 68P02901W17-R 14 Apr 2006
13

GMR-01

General warnings

ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz. CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10 kHz to 300 GHz).

Laser radiation

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

Lifting equipment

When dismantling heavy assemblies, or removing or replacing equipment, a competent responsible person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for these operations. When equipment has to be manhandled, reference must be made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation for the country in which the equipment is used.

Parts substitution

Do not install substitute parts or perform any unauthorized modification of equipment, because of the danger of introducing additional hazards. Contact Motorola if in doubt to ensure that safety features are maintained.

14

GMR-01

68P02901W17-R 14 Apr 2006

General warnings

Battery supplies

Do not wear earth straps when working with stand-by battery supplies. Use only insulated tools.

Lithium batteries

Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithium batteries must not be removed or replaced. Any boards containing defective lithium batteries must be returned to Motorola for repair. Contact your local Motorola office for how to return defective lithium batteries.

68P02901W17-R 14 Apr 2006

GMR-01

15

General cautions

General cautions

Observe the following cautions during operation, installation and maintenance of the equipment described in the Motorola manuals. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.

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

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

Fibre optics

Fibre optic cables must not be bent in a radius of less than 30 mm.

Static discharge

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

16

GMR-01

68P02901W17-R 14 Apr 2006

Devices sensitive to static

Devices sensitive to static


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

Special handling techniques


In the event of one of these devices having to be replaced, observe the following precautions when handling the replacement: Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. All metal tools should be used and when not in use they should be placed on an earthed surface. Take care when removing components connected to electrostatic sensitive devices. These components may be providing protection to the device.

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

68P02901W17-R 14 Apr 2006

GMR-01

17

Caring for the environment

Caring for the environment


The following information is provided to enable regulatory compliance with the European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) when using Motorola Networks equipment in EU countries.

Disposal of Motorola Networks equipment in EU countries

Please do not dispose of Motorola Networks equipment in landfill sites. In the EU, Motorola Networks in conjunction with a recycling partner will ensure that equipment is collected and recycled according to the requirements of EU environmental law. Please contact the Customer Network Resolution Centre (CNRC) for assistance. The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com/. Select Customer Network Resolution Centre contact information. Alternatively if you do not have access to CNRC or the Internet, contact the local Motorola office.

Disposal of Motorola Networks equipment in non-EU countries


In non-EU countries, dispose of Motorola Networks equipment in accordance with national and regional regulations.

18

GMR-01

68P02901W17-R 14 Apr 2006

Motorola manual set

Motorola manual set


The Motorola manual sets provide the information needed to operate, install and maintain the Motorola equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media: Printed hard copy. Electronic, as fully navigable PDF files on: The Motorola customer support web site at: (https://mynetworksupport.motorola.com/index.asp). CD-ROM produced in support of a major system software release.

Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software release, together with current versions of appropriate hardware manuals, and has additional navigation facilities. A snapshot copy of on-line documentation is also included, though it will not be updated in line with subsequent point releases. The CD-ROM does not include Release Notes or documentation supporting specialist products such as MARS or COP.

Ordering manuals and CD-ROMs


Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs. All orders must be placed with your Motorola Local Office or Representative.

68P02901W17-R 14 Apr 2006

GMR-01

19

Manual amendment

Manual amendment

Changes to a manual that occur after the printing date are incorporated into the manual using either Customer Documentation Change Notices (CDCNs) or General Manual Revisions (GMRs). Small changes are published in CDCNs. These describe the changes rather than replacing large sections of the manual. They are sent directly to customers and Motorola Local Offices and are accessible on the Motorola Extranet. CDCNs are numbered in sequence using the format: Shortened manual order number. Issue identifier. CDCN number.

For example: 01W23-M-CDCN01 would be the first CDCN produced for 68P2901W23M. Major changes are effected by publishing a GMR. GMRs are also produced in order to incorporate CDCNs when the numbers applying to a particular manual become significant. In this case, the CDCNs numbers are listed in "Incorporation of CDCNs" on page 5 in the issue status section of the manual. GMRs are issued to correct Motorola manuals as and when required. A GMR has the same identity as the target manual. Each GMR is identified by a number in a sequence that starts at 01 for each manual at each issue.

GMR availability
GMRs are published as follows: Printed hard copy - Complete replacement content or loose leaf pages with amendment list. Remove and replace pages in this manual, as detailed on the GMR instruction sheet.

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

CDCN availability
CDCNs are published as follows:

20

GMR-01

68P02901W17-R 14 Apr 2006

Manual amendment

PDF distributed electronically - Description of changes, occasionally with replacement loose leaf pages. Motorola service web - Updated at the same time as hard copies.

CDCN instructions
When a CDCN is incorporated in this manual, the record below is completed to record the amendment. Retain the instruction sheet that accompanies each CDCN and insert it in a suitable place in this manual for future reference.

CDCN amendment record


Record the manual insertion of CDCNs in this manual in the following table: CDCN number Incorporated by (signature) Date

68P02901W17-R 14 Apr 2006

GMR-01

21

Manual amendment

This page intentionally left blank.

22

GMR-01

68P02901W17-R 14 Apr 2006

Chapter

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-16. "Definition of a Network Element (NE)" on page 1-29. "Uploading an NE database to the OMC-R" on page 1-31. "Configuring network objects using the OMC-R GUI" on page 1-33. "Navigating to a network object class or instance" on page 1-35. "Using Detailed Views" on page 1-37. "Creating a network object using the OMC-R GUI" on page 1-39. "Modifying a network object using the OMC-R GUI" on page 1-41. "Deleting a network object using the OMC-R GUI" on page 1-44. "Remotely logging in to a BSS site from the OMC-R" on page 1-46. "Changing security level (for TTY interface commands)" on page 1-50. "Remotely logging in to a BSS using WebMMI" on page 1-51. "Making wide area modifications" on page 1-55.

68P02901W17-R 14 Apr 2006

GMR-01

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. Off-line and on-line network changes. Working practices. Preventing rlogin. Command partitioning. Tracking logged Configuration Management (CM) changes. On-line CM setup. Interrogating the network using the COP GLU tool. Upgrade information. Checking Vanguard Router software loads.

1-2

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Recommendations for Configuration Management

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. It is recommended that a weekly meeting be scheduled between all concerned parties to discuss: Any outstanding service affecting faults from the previous week. Review configuration changes and planned maintenance work from the previous week. Planned work for the week ahead. Any issues relating to the future planning or expansion of the network. A summary weekly report should be prepared prior to the meeting, and actions agreed at the meeting should be recorded and circulated.

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

Off-line and on-line network change recommendation


Network Configuration Management takes two forms, off-line configuration and on-line 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 on-line MIB to be recreated off-line. See System Information: DataGen (68P02900W22) for further details.

On-line Configuration Management


On-line Configuration Management is used for small scale network changes, usually performed by a dedicated on-line CM team working on live BSSs, based on job orders from other groups, such as the optimization or BSS roll out team.

68P02901W17-R 14 Apr 2006

GMR-01

1-3

Recommendations for Configuration Management

Chapter 1: Configuration Management General Information

The OMC-R GUI is the preferred tool for on-line 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 on-line 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 are logged using attributeStateChangeEvents, objectCreateEvents, or objectDeleteEvents in the event logs.

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. At no stage should more than one user 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 ensures 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-33 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. Other users prefer to use the OMC-R GUI with its user-friendly interface.

1-4

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Recommendations for Configuration Management

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: 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 to centrally 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 to the extent that revenue opportunities may be missed. For example, if uncontrolled changes are made to the frequency plan these could introduce excess interference into the network and reduce the available capacity.

68P02901W17-R 14 Apr 2006

GMR-01

1-5

Recommendations for Configuration Management

Chapter 1: Configuration Management General Information

Local maintenance parameter


Rlogin users and local maintenance terminal users can be prevented from accessing a BSS. This ensures changes are only made using the OMC-R GUI. This is achieved by setting the local maintenance (BSS parameter name: Local_maintenance) parameter field to Yes in the BSS Detailed View. This is a secure method, because the rlogin user cannot reset this parameter without going to SYSGEN mode. The procedure can therefore be: 1. 2. 3. Before starting a job order, set local maintenance parameter to No. After completing a job order, set local maintenance parameter to Yes. 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 1 2 3 4 Apply local maintenance parameter for a single BSS

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. This can be achieved by creating 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. {22636} As omcadmin user it is possible to lock out a BSS/RXCDR from all CM changes by toggling the Local Maintenance Flag of the BSS/RXCDR. The flag can be toggled in two ways: Via the GUI Detailed View form of the BSS or RXCDR Using a new script called /usr/gsm/current/sbin/updateLocalMaint

If the flag is set to YES (ON) then all CM operations on the BSS/RXCDR are allowed, however if the flag is set to NO (OFF) then all CM operations on the BSS/RXCDR are disallowed. See OMC-R Online Help, Network Operations for further details.

Using the updateLocalMaint script


{24637} The updateLocalMaint script can be used to copy the BSS from a displayed list rather than entering each BSS from the command line. It is possible to toggle the Local Maintenance flag for a BSS or a Region when using the Geographical Command Partition option.

1-6

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Recommendations for Configuration Management

The updateLocalMaint script can be used to display or set a Local Maintenance flag for a BSS, this can be carried out by an omcadmin user only.

To run the updateLocalMaint script the environmental variable CM_LOCAL_MAINT must be set to true in /usr/omc/current/env/.cshrc The updateLoaclMaint script can be used in display mode to list BSSs or Regions that match a query. The following are some examples: updateLocalMaint -disp bss updateLocalMaint -disp bss -region all

The updateLoaclMaint script can be used in set mode to toggle the Local Maintenance flag for required BSSs or Regions that are displayed. The following are some examples: updateLocalMaint 1 -bss BSS101, BSS102 updateLocalMaint 1 -bss all updateLocalMaint 1 -region Region1

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. Table 1-1 shows the recommended CM command partitioning configuration.

68P02901W17-R 14 Apr 2006

GMR-01

1-7

Recommendations for Configuration Management

Chapter 1: Configuration Management General Information

Table 1-1 Subject

Recommended CM command partitioning configuration Person usually responsible Supervisor Supervisor/Operator Supervisor Alarm handler (Not required for CM) Supervisor/Operator Supervisor/Operator Supervisor/Operator Supervisor/Operator Supervisor Supervisor Supervisor/Operator OMC-R Administrator or Access Controller (Not required for CM) OMC-R Administrator (Not required for CM) Functions enabled All action options under load management in the GUI. TTY and batch rlogin. Changes to the subscriptions and subscription lists. Handle alarms option in alarm window. Device administration of BSS devices after creation. Enabling/disabling statistics on BSS through GUI. Create, save and delete options under network icon. Create/delete/edit of all detailed views/commslinks. Audit scheduler and logs. All audit and PM resync options using GUI. Resync scheduler and logs options listed. Cell parameter propagation. Changing command partitioning options for all users. Modifying blacklist and pager subscriptions.

Load Management (LM) BSS rlogin (RLog) Subscription Management (Subs) Alarm handling (Alarms) Fault Management commands (FM) Statistics Management (Stat) Map Management (Map) Configuration Management (CM) Audit Resync Cell Propagation (CellProp) Access Control (Access)

OMC-R Administration (Admin)

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.

1-8

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Recommendations for Configuration Management

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, a new file is automatically created by the OMC-R. 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-2. Table 1-2 shows three omcaudit log files created for the same day, that is, 14th December 2004. Table 1-2 Same day omcaudit log file naming convention omcaudit log file omcaudit20041214_1 omcaudit20041214_2 omcaudit20041214 Description The first full omcaudit log file of the day. The second full omcaudit log file of the day. The third omcaudit log file of the day. On the 14th December 2004 this 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

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.

68P02901W17-R 14 Apr 2006

GMR-01

1-9

Recommendations for Configuration Management

Chapter 1: Configuration Management General Information

On-line Configuration Management setup


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

For a single OMC-R


Use the following procedure when there is one OMC-R: Procedure 1-2 1 2 3 On-line CM set up for single OMC-R

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 further customize what appears at start-up. Refer to OMC-R Online Help, Network Operations for further details on configuring AUTOINIT.CNFG. Periodic Audits should be set up and CM logging turned on.

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>

Multiple OMC-R
Use the following procedure when there are multiple OMC-Rs: Procedure 1-3 1 2 3 4 On-line CM set up for multiple OMC-Rs

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 which will aid some CM operations (such as Adding Neighbours across MIBs) in a multi-OMC-R environment. Refer to the Software Release Notes supplied with the software for further details.

1-10

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Recommendations for Configuration Management

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.

Important software upgrade information for 1614 to 1650


When upgrading from software load 1614 to 1650, the RXCDR must be upgraded before the BSS. This is due to changes that have been made to the RXCDR between the 1614 and 1620 loads. However, customers upgrading from 1620 to 1650 can upgrade either the BSS or RXCDR first.

Checking the Vanguard router software versions


If the software load on the equipment listed in Table 1-3 is not at the required level, then it will not be supported. Motorola recommends that the software loads are checked and, if found not to be at the required level, an upgrade be scheduled from your local CNRC office. The procedures to check the software loads are detailed in the following sections: "Checking the software version on Vanguard 6520/320 routers" on page 1-13. "Checking the software version on Vanguard 6560 routers" on page 1-15.

68P02901W17-R 14 Apr 2006

GMR-01

1-11

Recommendations for Configuration Management

Chapter 1: Configuration Management General Information

Table 1-3

Vanguard router required software loads Required Software Load Version 5.1M (Y2K Load) Memory Required The upgrade of the Codex 6525/PLUS platform is no longer a supported path (see Bulletin Number: GSM_G_OMCR_019) as all Codex 6525 and 6525 plus routers should have been upgraded in 1999 to take account of the Y2K (Year 2000) load. This was the last available software load for these systems (see ISB GSM-99-30 Dated August 1999). If the Vanguard unit currently has 4 MB Global DRAM, you will need to order 4 MB Global DRAM Upgrade. If the Vanguard unit currently has 4 MB Global DRAM, you will need to order 8 MB DRAM Upgrade. If the Vanguard unit has: 4 MB Global DRAM, you will need to order 4 MB Global DRAM. 8 MB Local DRAM, you will need to order 8 MB Local DRAM.

Equipment Type Codex 6525/PLUS

Vanguard 6520

Version 5.5

Vanguard 320

Version 6.0

Vanguard 6560

Version 6.0

Some hardware upgrade (memory) may be required on some systems. The amount of memory required for the Vanguard 6560 is based on customised Vanguard software load as issued bu OSSD OMC Development and is also based on the assumption that the recommended configuration is used (see Installation and Configuration: OMC-R Clean Install (68P02901W47)). If the defaults are exceeded, the capacity of performance of the packet switch could be degraded. Customers that are currently running Version 5.4 of the Vanguard software on their 6560 switch and do not foresee any major configuration changes occurring on their network, may decode to stay on this release of the software. If major expansion is planned, Motorola recommends the installation of the CISCO 3662 router as detailed in bulletin GSM_G_OMCR_043.

1-12

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Recommendations for Configuration Management

Checking the software version on Vanguard 6520/320 routers


Before beginning the procedure for checking the software version for Vanguard 6520/320 routers ensure the following prerequisites have been met: The router has been configured as per the configuration procedures in "Configuring the packet switch/MUX for a BSS" on page 4-45.

As the connection between remote MMI and the OMC server may implement two of either 6520/320 or a combination of both, the local 6520/320 is defined as connected to the same LAN as the OMC server. The remote 6520/320 is defined as connected to the same LAN as the MMI. The IP addresses of the 6520/320 routers, the OMC server and the remote MMI are known. Telnet will be used to connect to the local 6520/320 from the OMC server and to the remote 6520/320 from the remote MMI machine.

The default router IP address can be found in the PCU Detailed View field (see Table 6-8). The root passwords of the OMC server and remote MMI are known.

68P02901W17-R 14 Apr 2006

GMR-01

1-13

Recommendations for Configuration Management

Chapter 1: Configuration Management General Information

Procedure 1-4 1

Checking the software version on Vanguard 6520/320 routers

Login into the local or remote 6520/320 from the OMC-R or remote MMI by entering: telnet <ip address of router>. Result: If the OK prompt is displayed, go to step 2. If the * prompt is displayed, go to step 3. If the password dialogue is displayed, go to step 4.

2 3 4

Type atds0 and press Return. Result: The password dialogue is displayed - go to step 4. Type .ctp and press Return. Result: The password dialogue is displayed - go to step 4. Make a note of the software version from the password dialogue which should now be visible. For example, in the display below the router type is Vanguard 320 and the software version running is version 6.0:
OK atds0 CONNECT Connected to the Control Port on Node Local, at 18-APR-2004 19:31:17 VANGUARD 320, Version V6.0.R00A_@v320v6_v320 Copyright (C) 1989-2001 VanguardMS LLC Copyright (c) 1995 by Age Logic Inc., San Diego, CA All rights reserved Enter Password

Type CTRL-d to exit from the telnet session.

1-14

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Recommendations for Configuration Management

Checking the software version on Vanguard 6560 routers


Before beginning the procedure for checking the software version for Vanguard 6520/320 routers ensure the following prerequisites have been met: The router has been configured as per the configuration procedures in "Configuring the packet switch/MUX for a BSS" on page 4-45 and therefore, connection is through the pad functionality of the OMC-R. Access to the OMC-R through console or telnet is available. The root password or the omcadmin password are known. The box number of the 6560 router being called using the pad session is known.

The box number is made up of the X.121 address and the sub-address (see Installation and Configuration: OMC-R Clean Install (68P02901W47) for more details).

Procedure 1-5 1 2 3 4

Checking the software version on Vanguard 6560 routers

Login to the OMC-R as user root or omcadmin. Change directory as follows: cd /opt/SUNWconn/bin Connect to the router using the X.121 pad functionality as follows: ./pad <box_number> Make a note of the software version from the output displayed. For example, in the display below the software version running is version 5.3:
OK atds0 CONNECT (3) Codex2 03-APR-2003 11:52 ATCIF-3 CONNECTED TO ControlPort Connected to the Control Port on Node Codex2, at 3-APR-2003 11:52:48 Motorola 6560 Regional Node, Version V5.3_@MOTOROLA_6560 Copyright (C) 1989-1995 Motorola, Inc. Information Systems Group Copyright (c) 1995 by Age Logic Inc., San Diego, CA All rights reserved Enter Password

Type CTRL-d to exit from the telnet session.

68P02901W17-R 14 Apr 2006

GMR-01

1-15

Management Information Base (MIB)

Chapter 1: Configuration Management General Information

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 needed 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 initialised as follows: Procedure 1-6 1 Initializing the MIB database

The OMC-R MIB database must be populated 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


The MIB database should be regularly backed up. See Operating Information: OMC-R System Administration (68P02901W19) for further details.

1-16

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Management Information Base (MIB)

Containment
{22879} 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 SWInventory

SGSN

DYNETGroup Dynet

Assoc_RXCDRs/ Assoc_BSSs

NESoftware

SITE

PCU (BSS only)

SoftwareLoad

XBL

Conn_link

Hardware Devices

Software Functions

Logical Links

Radio Frequency

LCF

OMF

CBL

MTL

OML

LMTL

PATH

RSL RTFGroup

DRIGroup

CELL

RTF

DRI

Cabinet

Cage

EAS

Processors

COMB

KSWpair KSW

GCLK

IAS

LAN

TDM

MSI

DHP

MMS

GPROC

BSP/ BTP

CSFP

FreqHopSys

SMSCBmsg

Neighbour

UtranNbr

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

See "Hierarchy of devices and functions" on page 9-30 for further details.

68P02901W17-R 14 Apr 2006

GMR-01

1-17

Management Information Base (MIB)

Chapter 1: Configuration Management General Information

Containment rules
Some of the rules that apply to the containment of objects are given below:

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
{23370} 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. {23370} 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 initialisation before commencing their own initialisation. {23370} 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. If performance degradation at the GUI Server occurs, then the number of GUI Clients operating from the GUI Server should be reduced. The performance of an OMC GUI server is directly proportional to the number of GUI Clients and is also directly proportional to the number of events arriving per second. Event rates vary depending on the system activity. See OMC-R Online Help, Network Operations for details.

MSCs
The maximum number of MSCs allowed is 101 (0 to 100).

1-18

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Management Information Base (MIB)

BSS/RXCDR
{23370} 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.

BSC and BTSs


A BSC can support up to 56 MSI to MSI connections. A BSC can support up to 56 MSI to XCDR connections. A BSC SITE can contain up to 175 (0 to 174) MSIs and XCDRs. Up to 10 RXCDRs can be connected to each BSC, and 10 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.

MSI
An MSI can contain up to six MMSs depending on the cabinet type.

XCDR
Each XCDR contains one MMS.

Cells
A cell can contain up to 64 GSM Neighbour cells. A cell can contain up to 16 UTRAN Neighbour cells. A cell can contain up to 31 GSM Neighbour cells when the cell contains one or more UTRAN Neighbours. A cell can contain up to four Handover Control objects, four Power Control objects and one InterferAlg.

68P02901W17-R 14 Apr 2006

GMR-01

1-19

Management Information Base (MIB)

Chapter 1: Configuration Management General Information

MIB locking
{23370} In pre-GSR8 versions, the CM-MIB was locked exclusively when any of the following applications were started; Audit, Resync, Cell Propagation, NetEx, CellX, Bay Level Calibration, Cmutil, Proxy Cell Import/Export, and CleanMIB. GSR8 introduces MIB locking, an intelligent locking scheme which allows applications to run simultaneously if they meet certain criteria.

Regardless of the introduction of MIB Locking, only one network expansion operation can be run at a time (with the exception of Path Configure). See Chapter 11, "Network Expansion" for further details.

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. In the case of a Resync operation, intelligent locking takes the form of no locking. This is because Resync only affects state and MO locks can be broken in order to update the state without affecting an audit or other CM operation. Global Locking - mimics the pre-GSR8, that is, it 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 will be copied over from one OMC release to the next in order to maintain the customer lock configuration.

1-20

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Management Information Base (MIB)

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.

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 neighbour propagation procedure from a Cell or RTF Detailed View.

68P02901W17-R 14 Apr 2006

GMR-01

1-21

Management Information Base (MIB)

Chapter 1: Configuration Management General Information

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, and will consist 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.

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:

1-22

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Management Information Base (MIB)

Procedure 1-7 1 2 3 4

Example 1: Audit Gather operation when Intelligent Locking is set

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, userid 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 : Name> : <UserId> (PID) Audit Gather locking <BSS/RXCDR

For each BSS/RXCDR locked by the Audit Gather, steps 6 to 8 and then performed. 6 7 8 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 : Name> : <UserId> (PID) Audit Gather releasing <BSS/RXCDR

The system verifies that all BSS(s)/RXCDR(s) selected in Step 1 have been audited.

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:

68P02901W17-R 14 Apr 2006

GMR-01

1-23

Management Information Base (MIB)

Chapter 1: Configuration Management General Information

Procedure 1-8 1 2 3 4

Example 2: Audit Gather operation when Global Locking is set

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, userid 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 : <user id> (PID) Audit Gather locking ALL-GLOBAL:

6 7 8

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 : <user id>(PID) Audit Gather releasing ALL-GLOBAL:

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.

1-24

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Management Information Base (MIB)

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: Id. BSS/RXCDR Name. Application Type. PID. Lock Type. Time. User.

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. To do this, 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.

Audit Gathers are not included in the MAX_CM_OPS count.

68P02901W17-R 14 Apr 2006

GMR-01

1-25

Management Information Base (MIB)

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 MAX_CM_OPS MAX_CM_OPS MINIMUM MAXIMUM DEFAULT 1 1 1 17 9 3 12 5 2

System TCH Capacity 120 K TCH All other platforms Off Line MIB on any DataGen supported system specifications

The MAX_CM_OPS system parameter cannot be set to values outside the ranges specified above 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 neighbours. CellEx Export with no neighbours. CellEx Import with no neighbours. CMutil extract BSS. Another new configuration management operation would not be allowed to start.

1-26

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Management Information Base (MIB)

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 neighbours. CellEx Export with no neighbours. 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 1 1 1 MAX_CMUTIL_OPS maximum 2 1 1 MAX_CMUTIL_OPS default 2 1 1

System TCH 120 K TCH All other platforms Off Line MIB on any DataGen supported system specifications

The MAX_CMUTIL_OPS system parameters cannot be set to values outside the ranges specified above 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.

68P02901W17-R 14 Apr 2006

GMR-01

1-27

Management Information Base (MIB)

Chapter 1: Configuration Management General Information

Starting a new Cmutil operation


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 will be started. Example 1: 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 neighbours CellEx Export with no neighbours 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 neighbours. CellEx Export with no neighbours. Audit Gather. Audit Gather. Audit Gather. CMutil extract BSS. Because there are three configuration management operations running (three NE lock files), and 1 CMutil operation running (1 lock file), a new CMutil operation would be allowed to start as Audit Gathers are not included.

1-28

GMR-01

68P02901W17-R 14 Apr 2006

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.

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.

68P02901W17-R 14 Apr 2006

GMR-01

1-29

Definition of a Network Element (NE)

Chapter 1: Configuration Management General Information

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.

1-30

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Uploading an NE database to the OMC-R

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.

If any changes are made to the BSS database, using BSS commands or Detailed Views, the BSS database must be uploaded to the OMC-R. {24190} The Upload scheduler can be used to schedule uploads. See OMC-R Online Help, Network Operations for details.

68P02901W17-R 14 Apr 2006

GMR-01

1-31

Uploading an NE database to the OMC-R

Chapter 1: Configuration Management General Information

Uploading the NE database to the OMC-R


Use the following procedure to upload the NE database to the OMC-R: Procedure 1-9 1 2 3 4 5 6 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 on the required NE, or by selecting Edit - Detailed View from the menu bar. Select Options - NESoftware to open the NESoftware window. Select Load Mgt - Upload Object to open the Upload box. Select Database in the Object Type field. Click on OK to initiate an upload of the NE database so that the database has the recent cell id and neighbour updates. An information box is displayed with the following message:
Upload Operation Started...

7 8

Click on 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-10 1 2 3 4 5 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-9 and Procedure 1-10 for all affected BSS NEs.

1-32

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring network objects using the OMC-R GUI

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-46. 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. To do this, 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.

68P02901W17-R 14 Apr 2006

GMR-01

1-33

Configuring network objects using the OMC-R GUI

Chapter 1: Configuration Management General Information

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 greyed-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-35. "Using Detailed Views" on page 1-37. "Creating a network object using the OMC-R GUI" on page 1-39. "Modifying a network object using the OMC-R GUI" on page 1-41. "Deleting a network object using the OMC-R GUI" on page 1-44.

1-34

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Navigating to a network object class or instance

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. Each class is represented by a button in the Navigation Tree. Network object instances are actual network objects and have their own Detailed View. To display a network object instance, click on 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. Making these objects visible requires the branches (or levels) of the Navigation Tree to be opened. This 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-11 1 2 Navigate to network object

From the Front Panel, click on the Config Mgt icon to display the Navigation Tree. Click on 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 on the folder icon button next to network object class button. If any network object instances have been created, the OMC-R displays them.

68P02901W17-R 14 Apr 2006

GMR-01

1-35

Navigating to a network object class or instance

Chapter 1: Configuration Management General Information

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 need 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 on 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.

1-36

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Using Detailed Views

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 (see "Remotely logging in to a BSS site from the OMC-R" on page 1-46). 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. Whether the field is Mandatory or Optional, which indicates whether or not 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 Acknowledgement 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.)

Some parameters can have slightly different names in the OMC-R and BSS databases.

68P02901W17-R 14 Apr 2006

GMR-01

1-37

Using Detailed Views

Chapter 1: Configuration Management General Information

Changing naming for all Detailed Views


If required, 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 will need 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.

1-38

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a network object using the OMC-R GUI

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. 2. 3. 4. Creating a Detailed View for the required network object. Defining the Detailed View parameter fields for the network object. Saving the information and closing the Detailed View. 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-12 1 Create Detailed View for network object

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-35 for further details. The network object class button changes colour. Select Edit - Create from the Navigation Tree menu bar. The OMC-R displays the Detailed View for the network object in Create mode.

68P02901W17-R 14 Apr 2006

GMR-01

1-39

Creating a network object using the OMC-R GUI

Chapter 1: Configuration Management General Information

Defining the parameter fields for the network object


Use the following procedure to define the required parameter settings for the network object: Procedure 1-13 1 2 Define parameter fields for network object

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. This ensures 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 new the network object and close the Detailed View: Procedure 1-14 1 Saving and closing Detailed View

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

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Modifying a network object using the OMC-R GUI

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 need 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


Some fields in a Detailed View cannot be changed by a user (read-only) for the following reasons: The information in the field is generated by the OMC-R, 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 an existing Detailed View, use the following procedure:

68P02901W17-R 14 Apr 2006

GMR-01

1-41

Modifying a network object using the OMC-R GUI

Chapter 1: Configuration Management General Information

Procedure 1-15 1

Display and edit an existing Detailed View

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-35 for further details. The network object instance button changes colour. 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 on the network object instance button to display the Detailed View form. 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 on 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-16 1 Save information in Detailed View

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.

It is impossible to revert to a previous version after an edited version has been saved. 2 Close the Detailed View by selecting File - Close from the menu bar.

1-42

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Modifying a network object using the OMC-R GUI

Figure 1-2

Example of a Detailed View in Edit mode

68P02901W17-R 14 Apr 2006

GMR-01

1-43

Deleting a network object using the OMC-R GUI

Chapter 1: Configuration Management General Information

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-17 1 Delete network object using Navigation Tree

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-35 for further details. The network object class button changes colour. Select Edit - Delete from the menu bar. The OMC-R displays a deletion confirmation window. To cancel the deletion, click on Cancel. The confirmation window closes and the OMC-R displays the Navigation Tree. To confirm the deletion, click on 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.

2 3 4

1-44

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Deleting a network object using the OMC-R GUI

In the instance of deleting a BCCH RTF, the deletion confirmation window displays a further option to allow the incoming neighbours to be exported. This is further described in "Exporting incoming neighbours on deletion of BCCH RTFs" on page 9-212.

Deleting a network object from a Detailed View


Use the following procedure to delete a network object using the Detailed Views: Procedure 1-18 1 2 3 4 Delete network object from Detailed View

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 on OK to confirm the deletion, or click on 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. 5 6 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.

In the instance of deleting a BCCH RTF, the deletion confirmation window displays a further option to allow the incoming neighbours to be exported. This is further described in "Exporting incoming neighbours on deletion of BCCH RTFs" on page 9-212.

68P02901W17-R 14 Apr 2006

GMR-01

1-45

Remotely logging in to a BSS site from the OMC-R

Chapter 1: Configuration Management General Information

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. 2. Logging in to a BSS. Changing security level, as necessary, according to the commands to be used, see "Changing security level (for TTY interface commands)" on page 1-50.

Maximum number of remote login sessions


{23370} 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 is 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.

1-46

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Remotely logging in to a BSS site from the OMC-R

Logging in remotely to a BSS


Use the following procedure to remotely log in to a BSS from the OMC-R: Procedure 1-19 1 Remote log in to a BSS

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. Click on 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.

2 3

4 5

Change to security level 2 once logged in, see "Changing security level (for TTY interface commands)" on page 1-50. 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

68P02901W17-R 14 Apr 2006

GMR-01

1-47

Remotely logging in to a BSS site from the OMC-R

Chapter 1: Configuration Management General Information

Figure 1-4

RLogin window

1-48

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Remotely logging in to a BSS site from the OMC-R

Figure 1-5

Batch File Selection window for a BSS

68P02901W17-R 14 Apr 2006

GMR-01

1-49

Changing security level (for TTY interface commands)

Chapter 1: Configuration Management General Information

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 login 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-20 1 2 3 Change security level at TTY interface

From the RLogin window (see Figure 1-4), click on 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.

The above steps 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

1-50

GMR-01

68P02901W17-R 14 Apr 2006

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 operators 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-R 14 Apr 2006

GMR-01

1-51

Remotely logging in to a BSS using WebMMI

Chapter 1: Configuration Management General Information

Prerequisites for WebMMI


At the BSS
Before using WebMMI ensure the following requirements are met at the BSS: PCU is connected to the BSS. Ethernet cable connects the PCU MPROC to either: the network operators 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 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, the following procedures need to be completed: 1. 2. Identify the Internet address details of the PCU to be connected to. If the details have not already be set, enter the appropriate details. Load the WebMMI applet from the PCU to the PC. Once the applet is loaded at the PC, the WebMMI GUI appears.

These procedures are detailed below.

1-52

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Remotely logging in to a BSS using WebMMI

Identifying the PCU address details


Use the following procedure to identify the PCU Internet address details (the steps only need to be performed once for a PCU): Procedure 1-21 1 Identify PCU Internet address

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

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 an 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 instead of the command listed above: 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.

68P02901W17-R 14 Apr 2006

GMR-01

1-53

Remotely logging in to a BSS using WebMMI

Chapter 1: Configuration Management General Information

Loading the WebMMI applet to the PC


Before a PC can use WebMMI, an applet must be uploaded from the PCU to the PC. To do this, perform the following procedure at the PC (which has access to the network on which the PCU resides): Procedure 1-22 1 2 Load WebMMI applet to PC

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 a new PCU is accessed by the PC), 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-23 1 Use WebMMI GUI at PC

Click on 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 on the EXIT button in the WebMMI GUI window. (To exit a rlogin session in the EMON Shell, type exit.)

1-54

GMR-01

68P02901W17-R 14 Apr 2006

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


A number of BSS commands exist which permit wide area modifications. Some of the commonly used commands are listed below, and examples are given of using the commands with the all parameter. However, it is not sufficient to just issue the command; in some cases, an audit must be performed to update the OMC-R and 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, the following command needs to be issued 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 to be used by the BSS. For example, to prioritize the algorithms in the following order: A5/1, A5/2 for a BSS, the following command needs to be issued at the TTY command line: chg_a5_alg_pr 1 2

del_neighbor
When used with the all input parameter, this command deletes all neighbour cells from a cells neighbour list. For example, to delete all cells from the neighbour list of cell 5 4 3 2 1 61986 34944, the following command needs to be issued at the TTY command line interface: del_neighbor 5 4 3 2 1 61986 34944 all

68P02901W17-R 14 Apr 2006

GMR-01

1-55

Making wide area modifications

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 msecs for every equipped RSL, the following command needs to be issued at the TTY command line interface: In SYSGEN mode: modify_value all lapd_t200_timer 2500 rsl

reset_site
Used to selectively 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, the following command needs to be issued 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/neighbour 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 users Region(s).

See "Propagating cell parameters" on page 8-83 for further details.

1-56

GMR-01

68P02901W17-R 14 Apr 2006

Chapter

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-3. "Enhanced XBL (EXBL)" on page 2-11. "Dynamic Allocation of RXCDR-BSC Circuits (DARBC)" on page 2-14. "Dynamic allocation of BSC-BTS Backing Resources (DYNET)" on page 2-20. "MSC to BSS overload control" on page 2-24. "Encryption algorithms" on page 2-27. "Dual band cells option" on page 2-29. "GPRS and EGPRS coding schemes" on page 2-40. "Short Message Service - Cell Broadcast" on page 2-46. "Short Message Service - Point-To-Point" on page 2-55. "Preventive Cyclic Retransmission (PCR)" on page 2-59. "MSC initiated IMSI and IMEI call trace" on page 2-62. "Call trace flow control" on page 2-64. "GPRS Trace" on page 2-69 "Enhanced Circuit Error Rate Monitor (ECERM)" on page 2-73. "Advanced Load Management for EGSM" on page 2-82. "Network Controlled Cell Reselection" on page 2-85. "GPRS Interleaving TBFs" on page 2-94. "GSM location services" on page 2-109. "Enhanced GPRS One Phase Access " on page 2-120. "Intelligent Multilayer Resource Management (IMRM)" on page 2-161. "Quality of Service (QoS)" on page 2-171.

68P02901W17-R 14 Apr 2006

GMR-01

2-1

Making wide area modifications

Chapter 2: Configuring BSS Features

"Network Assisted Cell Change (NACC)" on page 2-181. "Enhanced Multi-level Precedence and Pre-emption (eMLPP)" on page 2-185. "Fast Call Setup" on page 2-189. "RSL Congestion Control" on page 2-191. "VersaTRAU" on page 2-194. "Feature Capacity Licensing and Audit" on page 2-197.

2-2

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Frequency hopping

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 signalling/traffic channel timeslot every frame, any RF channel interference is averaged with interference free channels. Restated, frequency hopping provides higher-quality communications than: Frequency diversity. Interference diversity.

Frequency hopping is described in detail in Technical Description: BSS Implementation (68P02901W36). Also see "Configuring frequency hopping" on page 8-177 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-179. TTY interface, see "Configuring frequency hopping using the TTY interface" on page 8-187.

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: 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-R 14 Apr 2006

GMR-01

2-3

Frequency hopping

Chapter 2: Configuring BSS Features

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.

For EGPRS, baseband hopping is supported, but there are some restrictions due to the Horizon II macro controller. Firstly, if the master cabinet is anything other than a Horizon II macro, then baseband hopping cannot be supported. Secondly, EGPRS RTFs need to be in a different hopping system to that used by GPRS RTFs. There is no such restriction for synthesizer hopping.

Synthesizer frequency hopping (SFH)

Synthesizer frequency hopping cannot be implemented when RTCs (Remotely Tuneable 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 well suited for SFH. Such cells are easily implemented with hybrid combiners, a requirement for SFH.

2-4

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Frequency hopping

SFH guidelines (BCCH frequency excluded) with example


Refer to the following guidelines to use SFH with BCCH frequency excluded: 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. 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.

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.

68P02901W17-R 14 Apr 2006

GMR-01

2-5

Frequency hopping

Chapter 2: Configuring BSS Features

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 12 16 22 29 32 46
BCCH RF CHANNEL

FREQUENCY HOPPING SYSTEM 0

FREQUENCY HOPPING SYSTEM 1

9 16 29 46 88

1 12 22 32 69

52 69 88
ti-GSM-SC01W17-000041-eps-sw

2-6

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Frequency hopping

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 will be broadcast at the maximum cell power.

68P02901W17-R 14 Apr 2006

GMR-01

2-7

Frequency hopping

Chapter 2: Configuring BSS Features

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: 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. Typical SFH mobile allocations with BCCH frequency included

Figure 2-2

CELL ALLOCATION

MOBILE ALLOCATIONS

1 9 12 16 22 29 32 46
BCCH RF CHANNEL

FREQUENCY HOPPING SYSTEM 0

FREQUENCY HOPPING SYSTEM 1

9 16 29 46 88

1 12 22 32 69

52 69 88
ti-GSM-SC01W17-000041-eps-sw

2-8

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Frequency hopping

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.

Timeslot 0 of the BCCH cannot baseband hop.

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.

68P02901W17-R 14 Apr 2006

GMR-01

2-9

Frequency hopping

Chapter 2: Configuring BSS Features

Figure 2-3

Typical example of BBH mobile allocations

CELL ALLOCATION

MOBILE ALLOCATIONS

FREQUENCY HOPPING SYSTEM 0

FREQUENCY HOPPING SYSTEM 1

32 32 46
BCCH

32 46 46

52
RF CHANNEL

52 69 69

69

88 88

88

ti-GSM-SC01W17-000043-eps-sw

2-10

GMR-01

68P02901W17-R 14 Apr 2006

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/T1 device, which the BSS database has indicated is connected to an RXCDR, there exists a corresponding E1/T1 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/T1 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 signalling 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 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. EXBL introduces a new containment for XBLs, that is, XBLs are contained by the Assoc_RXCDR or Assoc_BSS. For further technical details, see Technical Description: BSS Implementation (68P02901W36).

68P02901W17-R 14 Apr 2006

GMR-01

2-11

Enhanced XBL (EXBL)

Chapter 2: Configuring BSS Features

Assoc_BSS and Assoc_RXCDR devices


Enhanced XBL introduces two new devices: Assoc_RXCDR (AXCDR) Assoc_BSS (ABSS)

Chapter 4, "Configuring a BSS/RXCDR" explains how to create and manage these devices.

CIC blocking and validation

This section applies when XBLs are in use and CIC validation is enabled at the BSC for a given XBL. To ensure 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-79.

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.

2-12

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced XBL (EXBL)

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.

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.

68P02901W17-R 14 Apr 2006

GMR-01

2-13

Dynamic Allocation of RXCDR-BSC Circuits (DARBC)

Chapter 2: Configuring BSS Features

Dynamic Allocation of RXCDR-BSC Circuits (DARBC)


Overview of dynamic allocation of RXCDR-BSC Circuits


Thedynamic 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) and Ater channel provisioning between the BSC and RXCDR to ensure that calls are placed on the correct circuit between the BSC and the MSC. Without this feature in place, no fault management of the Ater channels would be possible, and all Ater and CIC information would need 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.

2-14

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dynamic Allocation of RXCDR-BSC Circuits (DARBC)

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. Auto-connect mode is controlled by the BSC.

Prior to the introduction of this feature, all Ater channels were statically assigned and the use of XBL links was not mandatory. From release GSR5, should an operator decide 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 will become blocked and no call traffic will 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, cic_validation must be enabled 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 will become blocked. Once both BSC and RXCDR are upgraded, the use of Auto-connect mode is recommended.

68P02901W17-R 14 Apr 2006

GMR-01

2-15

Dynamic Allocation of RXCDR-BSC Circuits (DARBC)

Chapter 2: Configuring BSS Features

Backwards compatibility mode is set using the parameter cic_validation, see "Enhanced XBL (EXBL)" on page 2-11 for further details.

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.

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 signalling 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 need to be 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 10 RXCDRs and vice versa.

Provisioning
The number of XBL links depends on the number of trunks on the BSC-RXCDR interface and whether or not 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.

2-16

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dynamic Allocation of RXCDR-BSC Circuits (DARBC)

Table 2-1

Number of BSC to RXCDR signalling links No redundancy Number of 64 kbit/s XBLs Number of 16 kbit/s XBLs 4 8 With redundancy Number of 64 kbit/s XBLs 2 4 Number of 16 kbit/s XBLs 8 16

N = number of MSC to BSC trunks

N < 1200 1200 < N < 2400

1 2

The figures above, 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 leas 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.

68P02901W17-R 14 Apr 2006

GMR-01

2-17

Dynamic Allocation of RXCDR-BSC Circuits (DARBC)

Chapter 2: Configuring BSS Features

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 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 to 254. When a user creates a BSS from the OMC-R, the default identifier is the next free number in the range. 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 re-created. Indicates the configuration of the site. Not visible to a user (it is derived internally from other parameters). Values {23370} 1-254

OMC-R GUI field name/BSS parameter name Network Entity Id network_entity_id

Transcoding local_transcoding

Local (1) Remote (0) Default: Remote (0).

fm_site_type

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.

2-18

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dynamic Allocation of RXCDR-BSC Circuits (DARBC)

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 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-48 for details of how to configure CICs.

68P02901W17-R 14 Apr 2006

GMR-01

2-19

Dynamic allocation of BSC-BTS Backing Resources (DYNET)

Chapter 2: Configuring BSS Features

Dynamic allocation of BSC-BTS Backing Resources (DYNET)


Overview of BSC-BTS dynamic allocation (DYNET)

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

2-20

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dynamic allocation of BSC-BTS Backing Resources (DYNET)

RSL TCHs used for backhaul


If the RSL at the BTS containing the cell is set to use 16 Kbps (parameter: rsl_rate) and ts_sharing is enabled at the BTS, the remaining three 16 Kbps TCHs on the RSL 64 Kbps 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 Kbps 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 Kbps RSL and BTS2 has 64 Kbps 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 were 64 Kbps in the Dynet, the maximum TCHs allocated cannot exceed 40.

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-99 for details of associated BSC-BTS dynamic allocation Dynet parameters.

68P02901W17-R 14 Apr 2006

GMR-01

2-21

Dynamic allocation of BSC-BTS Backing Resources (DYNET)

Chapter 2: Configuring BSS Features

Table 2-3

BSC-BTS dynamic allocation parameters Description Displayed in the BSS Detailed View - Optional Features grouping. Displays whether BSC-BTS dynamic allocation for the BSS is enabled or disabled. It cannot be changed by a user. Displayed in the SITE Detailed View, Local Routing Information grouping. This parameter field is greyed 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). Displayed in the BTS SITE Detailed View, Local Routing grouping. This parameter field is greyed out for SITE0 (BSC). 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). Values Enabled (1) Disabled (0)

OMC-R GUI field name/BSS parameter name BSC-BTS dynamic allocation Feature (OMC-R parameter name: BSCBTSDynAllocOpt) Timeslot Sharing ts_sharing

Enabled (1) Disabled (0) Default: Disabled (0)

Dynet Retry Time dynet_retry_time

150 to 3000 milliseconds Default: 1000

Total TCHs Reserved dynet_tchs_reserved (OMC-R parameter name: dynet_tchs_rsvd)

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

0 to 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.

2-22

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dynamic allocation of BSC-BTS Backing Resources (DYNET)

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 or not 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).

Other dynamic allocation features


Dynamic allocation of RXCDR-BSC circuits (DARBC) enables E1/T1 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-14 for further details.

68P02901W17-R 14 Apr 2006

GMR-01

2-23

MSC to BSS overload control

Chapter 2: Configuring BSS Features

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

2-24

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

MSC to BSS overload control

Table 2-4

Timer parameters for mobile access class barring Description 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 will result 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 (milliseconds). Default is 20000. 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, will result in the barring of a mobile access class and both timers T17 and T18 are restarted. Valid values are 0 - 1000000 (milliseconds). Default is 3000.

OMC-R GUI field name/BSS parameter name Flow Control T1 Timer flow_control_t1

Flow Control T2 Timer flow_control_t2

Methods of configuring MSC to BSS overload control


A user can configure MSC to BSS Overload Control, using either of the following methods: 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-R 14 Apr 2006

GMR-01

2-25

MSC to BSS overload control

Chapter 2: Configuring BSS Features

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 milliseconds for flow_control_t1, use the chg_element command as follows: chg_element flow_control_t1 1500 <location> <celldescription>

2-26

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Encryption algorithms

Encryption algorithms

Introduction to encryption algorithms


Encryption/decryption provides security for user speech, data and signalling information. The encryption feature is optional and for effective use must be deployed at the MSC, BSS and the MS. The BSS supports the parallel operation of A5/1, A5/2 and Null encryption algorithms on a per cell basis.

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 full details of the commands used refer to: Technical Description: BSS Command Reference (68P02901W23).

68P02901W17-R 14 Apr 2006

GMR-01

2-27

Encryption algorithms

Chapter 2: Configuring BSS Features

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 signalling 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: 0

For full details of the commands used refer to: Technical Description: BSS Command Reference (68P02901W23).

2-28

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dual band cells option

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. All SDCCHs in the cell must be configured 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 utilise 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.

68P02901W17-R 14 Apr 2006

GMR-01

2-29

Dual band cells option

Chapter 2: Configuring BSS Features

Benefits
Single BCCH for Dual Band Cells feature provides a: Convenient way of expanding system capacity by utilising 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 neighbour list. Reduction in the number of cells required in the database. Reduction in the management of neighbour 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 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 introduces the concept of 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.

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.

2-30

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dual band cells option

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 neighbour 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 prior to 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


{22404} This feature interacts with the IMRM feature, see "Intelligent Multilayer Resource Management (IMRM)" on page 2-161 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.

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

68P02901W17-R 14 Apr 2006

GMR-01

2-31

Dual band cells option

Chapter 2: Configuring BSS Features

Table 2-5

Single BCCH parameters Description Displayed in the BSS Detailed View - Optional Features grouping. Displays whether or not the Dual Band Cells feature has been enabled for this BSS. Valid values are: Enabled (1) Disabled (0)

OMC-R GUI field name/BSS parameter name Dual Band Cells Option (OMC-R parameter name: dualBandCellOpt)

Inner Zone Algorithm inner_zone_alg

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 neighbour 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). 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. Cont.

2-32

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dual band cells option

Table 2-5

Single BCCH parameters (Continued) Description 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 neighbour cell BCCH when calculating power budget. Valid values are: 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 neighbour cell list of the serving cell.

OMC-R GUI field name/BSS parameter name Power Budget Mode pbgt_mode

Second Frequency Type secondary_freq_type (OMC-R parameter name: second_freq_type)

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. 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 to 19 and 29 to 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. 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)

HO Power level for Inner Zone ho_pwr_level_inner (OMC-R parameter name: hoPwrLevel_inner)

Coincident MB HO Status coincident_mb

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-33

Dual band cells option

Chapter 2: Configuring BSS Features

Table 2-5

Single BCCH parameters (Continued) Description Valid values are 0 to 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 will behave the same as coincident_mb = 2. But for inter BSC handovers, the call will be targeted at the primary cell.

OMC-R GUI field name/BSS parameter name

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). 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 a dual band cells (that is, inner_zone_alg is set to 3), regardless of the frequency type of the cell. 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 a 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. 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 a 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 to 30. 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. 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. Cont.

Cell Transmit Power tx_power_cap

Max MS Transmit Pwr When HO to Inner Zone ms_txpwr_max_inner

Inner Zone Handover Hysteresis zone_ho_hyst

Frequency Type frequency_type

Inner Zone DL Receive Level Threshold rxlev_dl_zone

2-34

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dual band cells option

Table 2-5

Single BCCH parameters (Continued) Description Valid values are 0 to 63, where: 0 = -110 dBm. 1 = -109 dBm. 2 = 108 dBm. .. 63 = -47 dBm.

OMC-R GUI field name/BSS parameter name

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 to 63, where: 0 = -110 dBm. 1 = -109 dBm. ... 63 = -47 dBm. 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). 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). 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 handover. Valid values are: 1 = PGSM, 2 = EGSM, 4 = DCS1800, 8 = PCS1900. {22404} 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. {22404} 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 "Intelligent Multilayer Resource Management (IMRM)" on page 2-161 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 shall apply internal defaults. Cont.

Concentric Cell Zone cell_zone Outer Zone Usage Level outer_zone_usage_level

Band Preference band_preference

68P02901W17-R 14 Apr 2006

GMR-01

2-35

Dual band cells option

Chapter 2: Configuring BSS Features

Table 2-5

Single BCCH parameters (Continued) Description Displayed in the CELL Detailed View, General section, Multiband Handover grouping. Determines the method that will be 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 "Intelligent Multilayer Resource Management (IMRM)" on page 2-161 for details) Displayed in the CELL Detailed View, Handover section, General grouping. Indicates the maximum Dedicated Control Channel (CCH) power level allowed for a Mobile Station (MS) after a handover to this cell. Valid range depends on the setting of Cell frequency_type. 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. 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 will not be told to use a higher output power. The values should be chosen in order to balance the up and down links in a cell. Valid range depends on the setting of Cell frequency_type. 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. Displayed in the CELL Detailed View, Power Control section, General grouping. Contains the default value to be used for a neighbour cell when the Neighbour ms_txpwr_max_cell is not defined in a underlying Neighbour instance. Valid range depends on the setting of Cell frequency_type.

OMC-R GUI field name/BSS parameter name Band Preference Mode band_preference_mode

Mobile Station HO Power Level handover_power_level Maximum Transmit Power for BTS max_tx_bts

Maximum Mobile Station Transmit Power max_tx_ms

Maximum Control Channel Transmit Power ms_txpwr_max_cch Maximum Default Transmit Power ms_txpwr_max_def

Intra-Cell Handover Displayed in the CELL Detailed View, Handover section, Handover Types Allowed Allowed grouping. intra_cell_handover_allowed Disables or enables intra-cell handovers. Valid values are 0 to 2. Default is BSC Controlled Handover (1).

2-36

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dual band cells option

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: Procedure 2-1 1 2 Change cells from single band to dual band configuration

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 prior to 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: 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-R 14 Apr 2006

GMR-01

2-37

Dual band cells option

Chapter 2: Configuring BSS Features

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

2-38

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Dual band cells option

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

68P02901W17-R 14 Apr 2006

GMR-01

2-39

GPRS and EGPRS coding schemes

Chapter 2: Configuring BSS Features

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

EGPRS Coding Schemes are valid only for software release 1740 (EGPRS) or later.

2-40

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GPRS and EGPRS coding schemes

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 Description

OMC-R GUI field name/BSS parameter name 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. Greyed-out if the GPRS feature (gprsOpt) is restricted at the BSS. 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.

EGPRS Feature egprsOpt

Cell Parameters: Initial Downlink Coding Scheme init_dl_cs Displayed in the GPRS grouping in the CELL Detailed View. Indicates the initial coding scheme for a downlink TBF. Valid values: 0 to 3, where: 0 - CS-1 1 - CS-2 2 - CS-3 3 - CS-4 Previously, parameter allow_32k_trau had to be enabled for at least one RTF in a given cell in order to use Coding Schemes 3 and 4. For software release 1740 (EGPRS) or later, allow_32k_trau is replaced by pkt_radio_type and the dependency between the parameters is removed. That is, the OMC-R disregards any RTF parameters when determining valid values for CELLinit_dl_cs. (pkt_radio_type will not be prompted for during the equipage of an RTF and the option to select CS-3 or CS-4 is disabled). Greyed-out if the GPRS feature (gprsOpt) is restricted at the BSS. Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-41

GPRS and EGPRS coding schemes

Chapter 2: Configuring BSS Features

Table 2-6

GPRS and EGPRS coding schemes parameters (Continued) Description Displayed in the GPRS grouping in the CELL Detailed View. Indicates the initial coding scheme for a uplink TBF. Valid values: 0 to 3, where: 0 - CS-1 1 - CS-2 2 - CS-3 3 - CS-4 Previously, parameter allow_32k_trau had to be enabled for at least one RTF in a given cell to use Coding Schemes 3 and 4. For software release 1740 (EGPRS) or later, allow_32k_trau is replaced by pkt_radio_type and the dependency between the parameters is removed. That is, 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 for during the equipage of an RTF and the option to select CS-3 or CS-4 is disabled). Greyed-out if the GPRS feature (gprsOpt) is restricted at the BSS. Displayed in the GPRS grouping in the CELL Detailed View. Indicates the initial EGPRS coding scheme for a downlink MCS value. Valid values: 0 to 8, where: 0 - MCS-1 1 - MCS-2 2 - MCS-3 3 - MCS-4 4 - MCS-5 5 - MCS-6 6 - MCS-7 7 - MCS-8 8 - MCS-9 Default is 2 (MCS-3). Greyed-out if the EGPRS feature (egprsOpt) is restricted at the BSS. Cont.

OMC-R GUI field name/BSS parameter name Initial Uplink Coding Scheme init_ul_cs

EGPRS Initial Downlink Coding Scheme egprs_init_dl_cs

2-42

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GPRS and EGPRS coding schemes

Table 2-6

GPRS and EGPRS coding schemes parameters (Continued) Description Displayed in the GPRS grouping in the CELL Detailed View. Indicates the initial EGPRS coding scheme for an uplink MCS value. Valid values: 0 to 8, where: 0 - MCS-1 1 - MCS-2 2 - MCS-3 3 - MCS-4 4 - MCS-5 5 - MCS-6 6 - MCS-7 7 - MCS-8 8 - MCS-9 Default is 2 (MCS-3). Greyed-out if the EGPRS feature (egprsOpt) is restricted at the BSS. Cont.

OMC-R GUI field name/BSS parameter name EGPRS Initial Uplink Coding Scheme egprs_init_ul_cs

68P02901W17-R 14 Apr 2006

GMR-01

2-43

GPRS and EGPRS coding schemes

Chapter 2: Configuring BSS Features

Table 2-6

GPRS and EGPRS coding schemes parameters (Continued) Description

OMC-R GUI field name/BSS parameter name 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 or not the RTF can carry GPRS or EGPRS data. SDCCH allocation favours carriers with low values. Valid values are: 0 - 3, where: 0 - None 1 - 16 k 2 - 32 k 3 - 64 k Greyed 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, {24281} 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 will result in a temporary outage of the RT and requesting operator confirmation before proceeding.

2-44

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GPRS and EGPRS coding schemes

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.

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 Kbps TRAU timeslots for RTF 0 1. modify_value 1 pkt_radio_type 2 rtf 0 1

68P02901W17-R 14 Apr 2006

GMR-01

2-45

Short Message Service - Cell Broadcast

Chapter 2: Configuring BSS Features

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.

2-46

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Short Message Service - Cell Broadcast

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.

68P02901W17-R 14 Apr 2006

GMR-01

2-47

Short Message Service - Cell Broadcast

Chapter 2: Configuring BSS Features

Table 2-7

SMS-CB parameters Description 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. 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 ETSI 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. Values Existing (0). Existing with new interpretation of repetition rate (1). The default is Existing (0).

OMC-R GUI field name/BSS parameter name CBC to BSC Interface Version cbc_intface_vers

CBC VBIND Counter cbc_vbind_cntr

A value in the range 0 to 255. The default is 0.

Cont.

2-48

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Short Message Service - Cell Broadcast

Table 2-7

SMS-CB parameters (Continued) Description 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 will attempt 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. 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. Values Enabled (1) or Disabled (0).

OMC-R GUI field name/BSS parameter name SMS Fast Select sms_fast_select

CBC to CBS Outage Counter cbs_outage_cntr

0 to 255.

68P02901W17-R 14 Apr 2006

GMR-01

2-49

Short Message Service - Cell Broadcast

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

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: No stats data available. Valid stats info from specified interval.

2-50

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Short Message Service - Cell Broadcast

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 a 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 is needed 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 will be 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 will be displayed: COMMAND REJECTED: bsc_type not compatible with specified
element

If an RXCDR location is entered in the command, the following error message will be displayed: COMMAND REJECTED: Element specified not allowed at a 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 a RXCDR site.

68P02901W17-R 14 Apr 2006

GMR-01

2-51

Short Message Service - Cell Broadcast

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 a 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 a RXCDR site.

2-52

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Short Message Service - Cell Broadcast

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: 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 a RXCDR site.

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:

68P02901W17-R 14 Apr 2006

GMR-01

2-53

Short Message Service - Cell Broadcast

Chapter 2: Configuring BSS Features

Procedure 2-2 1

Create and transmit background messages at the TTY interface

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

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-54

GMR-01

68P02901W17-R 14 Apr 2006

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 will be dependent on the status of the MS. If..... the MS is idle the MS is on SDCCH the MS is busy Then..... SDCCH is used. SDCCH is used. 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.

68P02901W17-R 14 Apr 2006

GMR-01

2-55

Short Message Service - Point-To-Point

Chapter 2: Configuring BSS Features

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.

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>

2-56

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Short Message Service - Point-To-Point

For example to enable MS terminated SMS-PTP at site 0, use: chg_element sms_dl_allowed 1 0

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

68P02901W17-R 14 Apr 2006

GMR-01

2-57

Short Message Service - Point-To-Point

Chapter 2: Configuring BSS Features

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

2-58

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Preventive Cyclic Retransmission (PCR)

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 Signalling Unit (MSU) which has been transmitted is retained at the transmitting signalling link terminal until a positive acknowledgement 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 Range (ms) 40000 - 50000 5000 - 150000 1000 - 1500 400 - 600 80 - 120 3000 - 6000 800 - 2000 Default 50000 25000 1400 600 100 5000 1000 Index Value 0 1 2 3 4 5 6

Timer T1 (alignment ready) T2 (not aligned) T3 (aligned) T4 (emergency) T5 (sending SIB) T6 (remote congestion) T7 (excessive delay of acknowledgement)

These timers are displayed and can be configured in the BSS Detailed View MTP Timers parameter grouping or using the TTY interface.

68P02901W17-R 14 Apr 2006

GMR-01

2-59

Preventive Cyclic Retransmission (PCR)

Chapter 2: Configuring BSS Features

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 Parameter pcr_n1 pcr_n2 Range 32-127 MSUs 950-3750 (octets) Default 127 MSUs. 3750 octets.

N-value N1 (threshold) N2 (threshold)

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 Signalling 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 signalling 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.

2-60

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Preventive Cyclic Retransmission (PCR)

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 Signalling 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> Where: t* <element value> is: T1 to T7 (inclusive) the value within the range for the particular timer shown in the table below. the location identifier, either 0 or bsc.

<location>

Refer to Table 2-8 for the range and default values of the MTP level 2 timers.

68P02901W17-R 14 Apr 2006

GMR-01

2-61

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 a 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 required. The percentage of BSS resources to be reserved for MSC initiated traces can be specified through the call_trace_options parameter. {23370} 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-62

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

MSC initiated IMSI and IMEI call trace

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


The logfile naming convention allows the user to determine to which invoked trace it corresponds, and is as follows: ct_<source_id>_<BSS id>_<Trace Reference>_<SCCP number>.<dd><hh><mm><ss> 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 for the situation whereby, 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.

MMI activated trace logfile name:


A typical logfile for a MMI activated trace is shown below: ct_MMI_0000001234_00005_0006789.1405251

MSC activated trace logfile name:


A typical logfile for a MSC activated trace is shown below: ct_MSC_0000001234_00005_0006789.14052956

68P02901W17-R 14 Apr 2006

GMR-01

2-63

Call trace flow control

Chapter 2: Configuring BSS Features

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 to do this, the OMC-R displays an error message in the status bar.

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

2-64

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Call trace flow control

Table 2-10

Call trace flow control parameters Description 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. 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. Valid Input 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).

OMC-R GUI field name/BSS parameter name {22407} Flow Control by BSS ct_flow_control_bss_enabled (OMC-R parameter name: ct_fc_bss_enabled)

{22407} Flow Control High Threshold ct_flow_control_hi_level (OMC-R parameter name: ct_fc_hi_level)

20 to 100. Default is 60%.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-65

Call trace flow control

Chapter 2: Configuring BSS Features

Table 2-10

Call trace flow control parameters (Continued) Description 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%. 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 0 to 80. Default is 20%.

OMC-R GUI field name/BSS parameter name {22407} Flow Control Low Threshold ct_flow_control_lo_level (OMC-R parameter name: ct_fc_lo_level)

Apply Flow Control to MSC Trace ct_flow_control_msc_enabled (OMC-R parameter name: ct_fc_msc_trace)

Disabled (0): meaning MSC traces are allowed while flow control is enabled. Enabled (1): meaning MSC traces are not allowed while flow control is enabled. Default is Disabled (0).

2-66

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Call trace flow control

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

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

68P02901W17-R 14 Apr 2006

GMR-01

2-67

Call trace flow control

Chapter 2: Configuring BSS Features

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 or not 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

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

2-68

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GPRS Trace

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 signalling 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 will not be applicable in GPRS Trace. However, for ease of implementation, a continue beyond scope value will always be included in the trace Create action. This value will be ignored by the BSS, if the trace type is GPRS. For GPRS Trace, the lifetime of an invoked trace will correspond to the lifetime of a GPRS MS meeting the GPRS Trace criteria within a PCU. A number of GPRS data transfers may occur within this period. Due to cell reselection, a GPRS MS may leave the scope of the criteria and/or the PCU without prior warning. When the PCU detects that a GPRS MS has left, the invoked trace ends. Since cell reselection can take up to 15 seconds, the PCU waits 15 seconds for the MS to reappear before ending the invoked trace. This differs from GSM Call Trace, where the lifetime of an invoked trace and corresponding log file corresponds to a single call. GPRS Trace is created and managed from the OMC and BSS MMI only.

Unlike GSM Call Trace, creation of GPRS Trace criteria is not supported from the MSC. Also in the GSR8 release, GPRS Trace Records are forwarded to the NMC.

68P02901W17-R 14 Apr 2006

GMR-01

2-69

GPRS Trace

Chapter 2: Configuring BSS Features

The GPRS trace create criteria includes: 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. 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.

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 behaviour is similar to the counting of total number of calls at the LCF level for Call Trace. Measurement interval: This value applies for Packet Measurement Reports and UL/DL Measurement data. Maximum number of simultaneous MSs to be traced (applicable only if Trace selector is set to Nth GPRS MS).

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 will forward trace records relating to both GSM calls and GPRS data transfers for that IMSI. GSM and GPRS trace information will be written to separate log files.

2-70

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GPRS Trace

Recommended number of GPRS traces


Due to the nature of GPRS Trace and the different scenarios possible, it is difficult to correlate the number of GPRS trace events arriving at the OMC-R and the number of active GPRS traces running. The OMC-R enforces no limits on the number of GPRS traces that can be active at any one time. It is recommended to send eight or less GPRS Traces simultaneously to the OMC-R. If the OMC-R detects that the GPRS Trace Data rate is too high (which may impact the receipt of alarms or raw statistic files), it can drop the GPRS trace data, because alarms and statistics are considered to be a higher priority for Network Operations. In the event of this occurring, a Critical OMC alarm is generated: [30054] Call Traces being dropped due to high event rate

Factors influencing number of GPRS Call trace events arriving at OMC-R


The number of GPRS trace events arriving at the OMC-R depends on the following factors:

68P02901W17-R 14 Apr 2006

GMR-01

2-71

GPRS Trace

Chapter 2: Configuring BSS Features

Process 2-1

Factors influencing the number of GPRS Call trace events Type of mobile used: The mobile may support some or all of the following trace features. Radio environment information GPRS Mobility management information GPRS Session management information RLC/MAC information Protocol messages monitoring Quality of Service

Type of call: 2 Voice Data

Type of signalling that is being traced: The GPRS trace create criteria includes: 3 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 mobile GPRS Trace Record type: Basic or Radio. If Radio is selected, then the operator 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

4 5

Communications infrastructure Urban and or Rural Frequency of Handover between cells: Increased handover activity will cause more trace logs and event activity.

2-72

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced Circuit Error Rate Monitor (ECERM)

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.

68P02901W17-R 14 Apr 2006

GMR-01

2-73

Enhanced Circuit Error Rate Monitor (ECERM)

Chapter 2: Configuring BSS Features

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 Description 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. Cont.

OMC-R GUI field name/BSS parameter name BSS parameters: ECERM Feature (OMC-R parameter name: ecermOpt)

2-74

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced Circuit Error Rate Monitor (ECERM)

Table 2-11

ECERM parameters (Continued) Description 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 to 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. 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 to 253. Default value: 0. Must be two less than cic_error_gen_thresh.

OMC-R GUI field name/BSS parameter name CIC Error Gen Threshold cic_error_gen_thresh

Prior to GSR6, this parameter was named cic_error_gen_threshold. (OMC-R parameter name: cicErrGenThresh).

CIC Error Clear Threshold cic_error_clr_thresh

Prior to GSR6, this parameter was named cic_error_clr_threshold. (OMC-R parameter name: cicErrClrThresh). CIC Error Increment cic_error_inc

Prior to GSR6, this parameter was named cic_error_increment. (OMC-R parameter name: cicErrorInc).

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) to 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.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-75

Enhanced Circuit Error Rate Monitor (ECERM)

Chapter 2: Configuring BSS Features

Table 2-11

ECERM parameters (Continued) Description 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 a ACI alarm is generated. Valid values: 2 to 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. Greyed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. 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 to 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. Greyed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. 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) to 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. Greyed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. Cont.

OMC-R GUI field name/BSS parameter name ACI Error Gen Threshold aci_error_gen_ thresh (OMC-R parameter name: aciErrGenThresh).

ACI Error Clear Threshold aci_error_clr_ thresh (OMC-R parameter name: aciErrClrThresh).

ACI Error Increment aci_error_inc (OMC-R parameter name: aciErrorInc)

2-76

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced Circuit Error Rate Monitor (ECERM)

Table 2-11

ECERM parameters (Continued) Description 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 to 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. Greyed-out if the GPRS Feature (gprsOpt) or ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. 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 to 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. Greyed-out if the GPRS Feature (gprsOpt) or ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. 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) to 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. Greyed-out if the GPRS Feature (gprsOpt) or ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. Cont.

OMC-R GUI field name/BSS parameter name GCI Error Gen Threshold gci_error_gen_thresh (OMC-R parameter name: gciErrGenThresh)

GCI Error Clear Threshold gci_error_clr_thresh (OMC-R parameter name: gciErrClrThresh)

GCI Error Increment gci_error_inc (OMC-R parameter name: gciErrorInc)

68P02901W17-R 14 Apr 2006

GMR-01

2-77

Enhanced Circuit Error Rate Monitor (ECERM)

Chapter 2: Configuring BSS Features

Table 2-11

ECERM parameters (Continued) Description 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 to 240 seconds. Default values: 60, when GPRS and ECERM are enabled. 0, if either GPRS or ECERM is disabled.

OMC-R GUI field name/BSS parameter name GPRS Alarm Time gprs_alarm_time (OMC-R parameter name: gprsAlarmTime)

Greyed-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 to 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. Greyed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. 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 to 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. Greyed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. Cont.

PIC Error Clear Threshold pic_error_clr_thresh (OMC-R parameter name: picErrClrThresh)

2-78

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced Circuit Error Rate Monitor (ECERM)

Table 2-11

ECERM parameters (Continued) Description 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) to 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. Greyed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. 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 a RCI alarm is generated. Valid range: 2 to 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. 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 to 253. Default value: 0. Must be two less than rci_error_gen_thresh.

OMC-R GUI field name/BSS parameter name PIC Error Increment pic_error_inc (OMC-R parameter name: picErrorInc)

RCI Error Gen Threshold rci_error_gen_thresh

Prior to GSR6, this parameter was named rci_error_gen_threshold. (OMC-R parameter name: rciErrGenThresh), RCI Error Clear Threshold rci_error_clr_thresh

prior to GSR6 this parameter was named rci_error_clr_threshold. (OMC-R parameter name: rciErrClrThresh).

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-79

Enhanced Circuit Error Rate Monitor (ECERM)

Chapter 2: Configuring BSS Features

Table 2-11

ECERM parameters (Continued) 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 will update the RCI error count by this value whenever an error is detected. Valid range: 0 (Disabled) to 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.

OMC-R GUI field name/BSS parameter name RCI Error Increment rci_error_inc

Prior to GSR6 this parameter was named rci_error_increment (OMC-R parameter name: rciErrorInc). 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. From GSR6 onwards, this parameter is supported at BTS sites. If a user changes this parameter, an warning message is displayed indicating that a site reset will occur when the value is saved. Displayed in the Circuit Error Rate Monitor grouping in the SITE Detailed View. From GSR6 onwards, this parameter is supported at BTS sites. If a user changes this parameter, an warning message is displayed indicating that a site reset will occur when the value is saved. Displayed in the Circuit Error Rate Monitor grouping in the SITE Detailed View form. From GSR6 onwards, this parameter is supported at BTS sites. If a user changes this parameter, an warning message is displayed indicating that a site reset will occur when the value is saved. Displayed in the GPRS grouping in the SITE Detailed View. From GSR6 onwards, this parameter is supported at BTS sites. If a user changes this parameter, an warning message is displayed indicating that a site reset will occur when the value is saved. Valid values: 1 to 65535, when the GPRS Feature is enabled. Default value: 0, when the GPRS feature is disabled. Greyed-out in the SITE 0 Detailed View if the GPRS Feature (gprsOpt) is disabled.

Uplink Sync Timer (msec) uplink_sync_timer (OMC-R parameter name: ulSyncTimer)

Downlink Sync Timer (msec) downlink_sync_timer (OMC-R parameter name: dlSyncTimer)

Static Sync Timer static_sync_timer

2-80

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced Circuit Error Rate Monitor (ECERM)

Methods for configuring ECERM


The ECERM feature can be configured using: 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.

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-R 14 Apr 2006

GMR-01

2-81

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 neighbouring cell rather than allowing it to be handed over to a neighbouring 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 neighbour 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 introduces an EGSM targeting algorithm which the operator can enable in the BSS software. The EGSM targeting algorithm selects an internal EGSM capable neighbour 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 will assume that a cell with PGSM BCCH is a PGSM only cell.

Interaction with other features


{22404} This feature interacts with the IMRM feature, see "Intelligent Multilayer Resource Management (IMRM)" on page 2-161 for further details.

2-82

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Advanced Load Management for EGSM

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 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: BSS EGSM ALM ALLOWED bss_egsm_alm_allowed (OMC-R parameter name: egsm_alm_allowed) 0 - Disabled (restricted). 1 - Enabled (unrestricted).

OMC-R GUI field name/BSS parameter name ALM Enhancement for EGSM Carriers (OMC-R parameter name: AlmEgsmOpt)

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 greyed-out if the field: ALM Enhancement for EGSM Carriers (parameter name:AlmEgsmOpt) has been set to Disabled (0).

68P02901W17-R 14 Apr 2006

GMR-01

2-83

Advanced Load Management for EGSM

Chapter 2: Configuring BSS Features

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

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

GMR-01

68P02901W17-R 14 Apr 2006

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.

68P02901W17-R 14 Apr 2006

GMR-01

2-85

Network Controlled Cell Reselection

Chapter 2: Configuring BSS Features

Table 2-13

GPRS cell reselection modes Responsible Network Element MS control Functionality Normal GPRS mobile control. The mobile performs autonomous cell reselection based on the radio environment. Includes all functionality provided by NC0 mode. BSS sends cell reselection commands to GPRS MS to change reselection mode. GPRS mobile control with measurement reports to the BSS. MS performs autonomous cell reselection. All functionality in NC1 mode. BSS sends cell reselection command to GPRS mobile to change cell reselection mode. Network control. GPRS MS sends measurement reports to the BSS. BSS sends cell reselection commands and instructs mobile to perform cell reselection.

Cell Reselection Mode NC0

Enhanced NC0

MS control

NC1

MS control

Enhanced NC1

MS control

NC2

Network control

For a full description of NCCR, see Technical Description: BSS Implementation (68P02901W36).

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

2-86

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Network Controlled Cell Reselection

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). Table 2-14 Network Controlled Cell Reselection parameters Description 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 greyed-out if the BSS Detailed View field: Network Controlled Cell Reselection Feature (parameter name: nccrOpt) is set to Disabled (0). 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 to 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 greyed-out if the BSS Detailed View field: Network Controlled Cell Reselection Feature (parameter name: nccrOpt) is set to Disabled (0). Cont.

OMC-R GUI field name/BSS parameter name NCCR Enabled nccr_enabled

NC Reporting Period Idle nc_reporting_period_i

68P02901W17-R 14 Apr 2006

GMR-01

2-87

Network Controlled Cell Reselection

Chapter 2: Configuring BSS Features

Table 2-14

Network Controlled Cell Reselection parameters (Continued) Description 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 to 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 greyed-out if the BSS Detailed View field: Network Controlled Cell Reselection Feature (parameter name: nccrOpt) is set to Disabled (0). 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 to 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 greyed-out if the BSS Detailed View field: Network Controlled Cell Reselection Feature (parameter name: nccrOpt) is set to Disabled (0). Cont.

OMC-R GUI field name/BSS parameter name NC Non Drx Period nc_non_drx_period

NC Reporting Period Transfer nc_reporting_period_t

2-88

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Network Controlled Cell Reselection

Table 2-14

Network Controlled Cell Reselection parameters (Continued) Description 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 to 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 greyed-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. Displayed in the GPRS - Network Controlled Cell Reselection grouping of the CELL Detailed View. Indicates the number of bad Packet Resource Reports (PMR) that will be received before the PCU initiates network controlled cell reselection. (A bad PMR is one in which the difference between the serving cells rxlev and the serving cells configured value of rxlev_access_min is less than gprs_cr_margin.) Greyed-out if the Network Controlled Cell Reselection Feature (nccrOpt) is Disabled (0) for the BSS. Valid values: 1 to 10. The default is 3. 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. Greyed-out if the Network Controlled Cell Reselection Feature (nccrOpt) is Disabled (0) for the BSS. Valid values: 5 to 40. The default is 30.

OMC-R GUI field name/BSS parameter name Network Control Order network_control_order (OMC-R parameter name: netwk_ctrl_order)

Bad PMRs gprs_num_pmrs

PMR Threshold gprs_cr_margin

68P02901W17-R 14 Apr 2006

GMR-01

2-89

Network Controlled Cell Reselection

Chapter 2: Configuring BSS Features

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: Neighbour Detailed View* TestNeighbour Detailed View* Neighbour Template Detailed View* Multiple TestNeighbour Create Form* Neighbour Template View Form Source/Neighbour View Form

An asterisk (*) in the list above indicates that the GPRS checkbox is greyed-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.

2-90

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Network Controlled Cell Reselection

Configuring NCCR using the TTY interface


Using chg_ 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

68P02901W17-R 14 Apr 2006

GMR-01

2-91

Network Controlled Cell Reselection

Chapter 2: Configuring BSS Features

NCCR changes to neighbour 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. Table 2-15 add_neighbor NCCR-related prompts Prompt Add neighbour to the BA BCCH list (yes/no)? Add neighbour to the BA SACCH list (yes/no)? Add neighbour to the BA GPRS list (yes/no)? (Only displayed if NCCR is restricted for the BSS.) Enter base station identity code (bsic): (Prompted for all external neighbours.) Values yes or no yes or no yes or no Default yes yes yes

0 to 63

None

If an attempt is made to create a neighbour, 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 neighbour 0010112 of cell 0010111 from the GPRS list, when the neighbour 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: Neighbour not present in SACCH list: deleted to remove from BCCH/GPRS list. must be

The following command adds the neighbour 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 neighbours frequency on the GPRS list when the NCCR feature is restricted at the BSS, the command is rejected and an error message is displayed.

2-92

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Network Controlled Cell Reselection

disp_neighbor NCCR changes: The disp_neighbor command can be used to display whether or not the frequencies of the neighbouring cells are part of the ba_gprs list. For example, the following command displays all neighbour 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. The following command displays all neighbour information for neighbour 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 neighbouring cells from the ba_type list. For example, the following command deletes the cell 0010114 from the neighbour list of cell 0010111: del_neighbor 0 0 1 0 1 1 1 0 0 1 0 1 1 4

68P02901W17-R 14 Apr 2006

GMR-01

2-93

GPRS Interleaving TBFs

Chapter 2: Configuring BSS Features

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.

2-94

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GPRS Interleaving TBFs

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 MSs uplink TBF 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).

68P02901W17-R 14 Apr 2006

GMR-01

2-95

GPRS Interleaving TBFs

Chapter 2: Configuring BSS Features

Table 2-16

GPRS interleaving BSS and cell parameters Description 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 to 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 greyed-out in the Detailed View form. 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 to 50 blocks. Default is 18 blocks. Greyed-out if the GPRS feature (gprsOpt) is restricted at the BSS. 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. Greyed-out if the either the GPRS feature (gprsOpt) or Increased PRP Capacity feature is restricted at the BSS. 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 to 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 greyed-out in the Detailed View form. Cont.

OMC-R GUI field name/BSS parameter name BSS Parameters: Delayed Downlink TBF Release Duration delay_dl_rel_dur

Delayed Uplink TBF Release Duration delay_ul_rel_dur

Delayed Downlink TBF Release Control ddtr_ctrl_enabled

Auto Downlink Duration auto_dl_dur

2-96

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GPRS Interleaving TBFs

Table 2-16

GPRS interleaving BSS and cell parameters (Continued) Description Displayed in the GPRS grouping in the BSS Detailed View form. The scheduling beta algorithm at the BSS. Valid values: 0 to 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.

OMC-R GUI field name/BSS parameter name GPRS Scheduling Beta Algorithm gprs_sched_beta

Can only be modified, if the GPRS Feature (gprsOpt) is unrestricted (Enabled) in the BSS Detailed View. Otherwise, the field is greyed-out. {23956} If gprs_sched_beta is modified and saved while the QoS feature (see "Quality of Service (QoS)" on page 2-171) 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 to 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 greyed-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

68P02901W17-R 14 Apr 2006

GMR-01

2-97

GPRS Interleaving TBFs

Chapter 2: Configuring BSS Features

Methods for configuring GPRS interleaving TBFs


The GPRS interleaving TBFs feature can be configured using: 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.

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

2-98

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced BSC Capacity

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

If either GSM HR and/or AMR has been purchased and enabled, a maximum of 4800 CICs can be equipped at a 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

68P02901W17-R 14 Apr 2006

GMR-01

2-99

Inter-Radio Access Technology (Inter-RAT) Handover

Chapter 2: Configuring BSS Features

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) neighbour 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.

2-100

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Inter-Radio Access Technology (Inter-RAT) Handover

Enhanced Inter-RAT Handover feature


{22879} 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 introduces a new device called a Blind Search Neighbour, which is supported under a cell, and represents the blind search neighbours of a cell. See "UTRAN blind search neighbour" on page 8-153 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


{22404} This feature interacts with the IMRM feature, see "Intelligent Multilayer Resource Management (IMRM)" on page 2-161 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).

68P02901W17-R 14 Apr 2006

GMR-01

2-101

Inter-Radio Access Technology (Inter-RAT) Handover

Chapter 2: Configuring BSS Features

Table 2-17

Inter-RAT Handover and Enhanced Inter-RAT handover parameters Description Values

OMC-R GUI field name/BSS parameter name BSS parameters: Inter-RAT Handover Feature InterRatOpt

Displayed in the Optional Features grouping of the BSS Detailed View form. Indicates whether or not the Inter-RAT Handover Feature is restricted (disabled) or unrestricted (enabled) in the BSS software. This parameter cannot be modified by a user. {22879}When the Enhanced Inter-RAT Handover Feature (EnhncdInterRatOpt) is set to 1 (Enabled), InterRatOpt is automatically set to 1 (Enabled). Displayed in the Optional Features grouping of the BSS Detailed View form. Indicates whether or not 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). 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: Disabled (0). Enabled (1). Default is Disabled (0).

{22879} Enhanced Inter-RAT Handover Feature EnhancedInterRatOpt (OMC parameter name: EnhncdInterRatOpt)

0 or 1, where: Disabled (0). Enabled (1). Default is Disabled (0).

MSC Release msc_release

0 or 1, where: Release 1998 or older (0). Release 1999 or newer (1). Default is 0. Cont.

2-102

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Inter-Radio Access Technology (Inter-RAT) Handover

Table 2-17

Inter-RAT Handover and Enhanced Inter-RAT handover parameters (Continued) Description Values

OMC-R GUI field name/BSS parameter name CELL parameters: Inter-RAT Handovers Enabled inter_rat_enabled

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

{22879} 0 to 7, where: 0 - OFF. 1 - 2 3G Idle. 2 - 3 2G Dedicated. 3 - 2 3G Idle and 3-2G Dedicated. {22879} 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.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-103

Inter-Radio Access Technology (Inter-RAT) Handover

Chapter 2: Configuring BSS Features

Table 2-17

Inter-RAT Handover and Enhanced Inter-RAT handover parameters (Continued) Description 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 neighbour 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 neighbour cells. This field is greyed-out if Inter-RAT Handover Feature (InterRatOpt) is restricted (disabled) for the BSS. 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 will cause the SI2ter_MP_CHANGE_MARK and SI2quater MP_CHANGE_MARK to be toggled. This field is greyed-out if Inter-RAT Handover Feature (InterRatOpt) is restricted (disabled) for the BSS. Values 0 to 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 (irrespective of threshold value). 8 = Above -78 dBm. 9 = Above -74 dBm. 10 = -70 dBm. .... 14 = -54 dBm. 15 = Never Search. Default is 15. 0 or 1, where: 0 = Use Q Search_I. 1 = Use Q Search_C. Default is 0.

OMC-R GUI field name/BSS parameter name BCCH RF Signal Level Threshold qsearch_i

Use BCCH RF Signal Level Threshold qsearch_c_initial

Cont.

2-104

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Inter-Radio Access Technology (Inter-RAT) Handover

Table 2-17

Inter-RAT Handover and Enhanced Inter-RAT handover parameters (Continued) Description 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 greyed-out if Inter-RAT Handover Feature (InterRatOpt) is restricted (disabled) for the BSS. 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 greyed-out if Inter-RAT Handover Feature (InterRatOpt) is restricted (disabled) for the BSS. 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 neighbour cell. This field is greyed-out if EnhncdInterRatOpt is Disabled (0). Values 0 to 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). 0 to 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). 0 to 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).

OMC-R GUI field name/BSS parameter name Receive Signal Code Power (RSCP) Threshold fdd_qoffset

Minimum Ec/No Threshold fdd_qmin

{22879} SACCH RF Signal Level Threshold qsearch_c

{22879} 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. Greyed out if EnhncdInterRatOpt is Disabled (0).

0 or 1, where: 0 = RSCP. 1 = Ec/No. Default is 1 (Ec/No).

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-105

Inter-Radio Access Technology (Inter-RAT) Handover

Chapter 2: Configuring BSS Features

Table 2-17

Inter-RAT Handover and Enhanced Inter-RAT handover parameters (Continued) Description 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. Greyed out if EnhncdInterRatOpt is Disabled (0). 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. Greyed out if EnhncdInterRatOpt is Disabled (0). 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. Greyed out if EnhncdInterRatOpt is Disabled (0). If modified from 0 to 1, and there are no UTRAN blind search neighbours equipped to that cell, the following warning message is displayed: There are no Blind Search neighbours equipped for this cell. Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Indicates whether or not handover to UMTS band is preferred. Greyed out if EnhncdInterRatOpt is Disabled (0) 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). Greyed out if EnhncdInterRatOpt is Disabled (0). Values Values: 0 to 3. Default is 3.

OMC-R GUI field name/BSS parameter name {22879} Number of Serving Band cells to report serving_band_reporting

{22879} Number of UTRAN FDD cells to report fdd_multirat_reporting

0 to 3. Default is 1.

{22879} Blind Search Preference blind_search_preference

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

{22879}UMTS Band Preferred umts_band_preferred

0 or 1, where: 0 = No. 1 = Yes. Default is 0 (No).

{22879}Threshold when FDD_REP_QUANT is Ec/No umts_cpich_ec_no_min

-20 dBm to 0 dBm. Default is -15 dBm.

Cont.

2-106

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Inter-Radio Access Technology (Inter-RAT) Handover

Table 2-17

Inter-RAT Handover and Enhanced Inter-RAT handover parameters (Continued) Description 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). Greyed out if EnhncdInterRatOpt is Disabled (0). Displayed in the Identification parameter grouping in the UTRAN Detailed View form. It is a measurement parameter used by the handover algorithm. Greyed out if EnhncdInterRatOpt is Disabled (0). Displayed in the General parameter grouping in the UTRAN Detailed View form. Indicates UTRAN neighbour cell measurement averaging period. Greyed out if EnhncdInterRatOpt is Disabled (0). Displayed in the General parameter grouping in the UTRAN Detailed View form. Specifies the neighbour lists: BCCH, SACCH, or BCCH and SACCH. Greyed out if EnhncdInterRatOpt is Disabled (0). Values -53 dBm to -115 dBm. Default is -90 dBm.

OMC-R GUI field name/BSS parameter name {22879}Threshold when FDD_REP_QUANT is RSCP umts_cpich_rscp_min

UTRAN parameters: {22879} UMTS Measurement Margin umts_meas_margin 0 dB to 20 dB. Default is 3 dB.

{22879} Averaging Period umtsNcellAvgPrd

0 to 12. Default is 6.

{22879} UMTS BA Type umts_ba_type

1 to 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).

{22879} Blind Search Neighbour parameters

See "UTRAN blind search neighbour" on page 8-153 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.

68P02901W17-R 14 Apr 2006

GMR-01

2-107

Inter-Radio Access Technology (Inter-RAT) Handover

Chapter 2: Configuring BSS Features

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

2-108

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GSM location services

GSM location services


Description of Location Services


Location services is an optional feature, which identifies the physical location of a Mobile Station (MS) by using one or more positioning mechanisms. Location services is also referred to as LCS. The location services feature provides support for a Motorola or third-party mobile positioning application. The positioning process involves two main steps: 1. 2. Signal measurement. 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 the both the physical and logical interface between the BSC and the BSS-based SMLC. See "Configuring an LMTL device" on page 9-139 for details of how to configure an LMTL device.

Determining whether location services is unrestricted


Location services is an optional feature.

68P02901W17-R 14 Apr 2006

GMR-01

2-109

GSM location services

Chapter 2: Configuring BSS Features

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.

Using the TTY interface


To check if location services 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 Description 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 to 1,000,000 ms. Default is 300,000 ms. Cont.

OMC-R GUI field name/BSS parameter name General Location Services Timers: LCS Perform Location Timer (ms) lcs_perf_location

2-110

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GSM location services

Table 2-18

Location Services parameters (Continued) Description Displayed in the LCS grouping in the BSS Detailed View form. Supervises the overall operation of a location request. Valid values: 0 to 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. Displayed in the LCS grouping in the BSS Detailed View form. Supervises an LCS segmentation operation. Valid values: 0 to 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. 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. 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 to 50,000 ms. Default is 50,000 ms. If ss7_mode is 1, values are 13,000 to 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. Cont.

OMC-R GUI field name/BSS parameter name LCS Supervision Timer (ms) lcs_supervision

LCS Segmentation Timer (ms) lcs_segmentation

General Location Services Database Elements: LCS Mode lcs_mode

Lb Interface MTP Layer 2 Timers: Lb Interface MTP Layer 2 T1 timer (ms) lb_int_ss7_l2_t1

68P02901W17-R 14 Apr 2006

GMR-01

2-111

GSM location services

Chapter 2: Configuring BSS Features

Table 2-18

Location Services parameters (Continued) Description 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 to 150,000 ms. Default is 25,000 ms. If ss7_mode is 1, values are 5,000 to 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. 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 to 1,500 ms. Default is 1,400 ms. If ss7_mode is 1, values are 5,000 to 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. 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 to 600 ms. Default is 600 ms. 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 to 120 ms. Default is 100 ms. 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 to 6,000 ms. Default is 5000 ms. If ss7_mode is 1, values are 1,000 to 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. Cont.

OMC-R GUI field name/BSS parameter name Lb Interface MTP Layer 2 T2 timer (ms) lb_int_ss7_l2_t2

Lb Interface MTP Layer 2 T3 timer (ms) lb_int_ss7_l2_t3

Lb Interface MTP Layer 2 T4 timer (ms) lb_int_ss7_l2_t4

Lb Interface MTP Layer 2 T5 timer (ms) lb_int_ss7_l2_t5

Lb Interface MTP Layer 2 T6 timer (ms) lb_int_ss7_l2_t6

2-112

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GSM location services

Table 2-18

Location Services parameters (Continued) Description 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 to 2,000 ms. Default is 1,000 ms.

OMC-R GUI field name/BSS parameter name Lb Interface MTP Layer 2 T7 timer (ms) lb_int_ss7_l2_t7

Lb Interface MTP Layer 3 Timers: Interface MTP Layer 3 T1 timer (ms) lb_int_ss7_l3_t1 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 to 1,200 ms. Default is 850 ms. Displayed in the LCS grouping in the BSS Detailed View form. The waiting for changeover acknowledgement" timer (ITU Q.704) associated with the Lb interface. Valid values: 700 to 2,000 ms. Default is 1,400 ms. Displayed in the LCS grouping in the BSS Detailed View form. The waiting for changeback acknowledgement (first attempt)" timer (ITU Q.704) associated with the Lb interface. Valid values: 500 to 1,20 ms. Default is 850 ms. Displayed in the LCS grouping in the BSS Detailed View form. The waiting for changeback acknowledgement (second attempt)" timer (ITU Q.704) associated with the Lb interface. Valid values: 500 to 1,200 ms. Default is 850 ms. Displayed in the LCS grouping in the BSS Detailed View form. The waiting for uninhibit acknowledgement" timer (ITU Q.704) associated with the Lb interface. Valid values: 800 to 1,500 ms. Default is 1,150 ms. 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 to 1,500 ms. Default is 1,150 ms. Displayed in the LCS grouping in the BSS Detailed View form. The waiting for inhibition acknowledgement" timer (ITU Q.704) associated with the Lb interface. Valid values: 2,000 to 3,000 ms. Default is 2,500 ms. Cont.

Lb Interface MTP Layer 3 T2 timer (ms) lb_int_ss7_l3_t2

Lb Interface MTP Layer 3 T4 timer (ms) lb_int_ss7_l3_t4

Lb Interface MTP Layer 3 T5 timer (ms) lb_int_ss7_l3_t5

Lb Interface MTP Layer 3 T12 timer (ms) lb_int_ss7_l3_t12

Lb Interface MTP Layer 3 T13 timer (ms) lb_int_ss7_l3_t13

Lb Interface MTP Layer 3 T14 timer (ms) lb_int_ss7_l3_t14

68P02901W17-R 14 Apr 2006

GMR-01

2-113

GSM location services

Chapter 2: Configuring BSS Features

Table 2-18

Location Services parameters (Continued) Description 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 to 1,500 ms. Default is 1,150 ms. 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 to 360,000 ms. Default is 270,000 ms. If ss7_mode is 1, values are 90,000 to 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. 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 to 360,000 ms. Default is 270000 ms. If ss7_mode is 1, values are 90,000 to 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. Displayed in the LCS grouping in the BSS Detailed View form. The supervision timer for signalling link test acknowledgement message" timer (ITU Q.707) associated with the Lb interface. Valid values: 4,000 to 12,000 ms. Default is 8,000 ms.

OMC-R GUI field name/BSS parameter name Lb Interface MTP Layer 3 T17 timer (ms) lb_int_ss7_l3_t17

Lb Interface MTP Layer 3 T22 timer (ms) lb_int_ss7_l3_t22

Lb Interface MTP Layer 3 T23 timer (ms) lb_int_ss7_l3_t23

Lb Interface SS7 Link Test T1 timer (ms) lb_int_ss7_slt_t1

Lb Interface MTP Layer 3 Elements: Cont.

2-114

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GSM location services

Table 2-18

Location Services parameters (Continued) Description 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. 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 to 16383 ms. No default. If ss7_mode is 1, values are 0 to 16,777,215. No default. For a live system, lb_int_dpc should not be the same as the opc. 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. 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. Cont.

OMC-R GUI field name/BSS parameter name Lb Interface CR Calling lb_int_cr_calling

Lb Interface Destination Point Code (DPC) lb_int_dpc

Lb Int PC Included Called Party Flag lb_int_called_pci

Lb Int PC Included Calling Party Flag lb_int_calling_pci (OMC-R parameter name: lb_calling_pci)

68P02901W17-R 14 Apr 2006

GMR-01

2-115

GSM location services

Chapter 2: Configuring BSS Features

Table 2-18

Location Services parameters (Continued) Description 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. 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 to 1,000,000 ms. The default is 50,000 ms. 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 to 1,000,000 ms. Default is 40,000 ms. 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 to 1,000,000 ms. Default is 30,000 ms. 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 to 1,000,000 ms. Default is 30,000 ms. 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 to 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. Cont.

OMC-R GUI field name/BSS parameter name LMTL Load Share Granularity lmtl_loadshare_granularity (OMC-R parameter name: lmtl_loadshare)

Lb Interface CP Timers: Lb Interface BSSMAP T4 Timer (ms) lb_int_bssmap_t4

Lb Interface BSSMAP T13 Timer (ms) lb_int_bssmap_t13

Lb Interface Clear Command Timer (ms) lb_clear_command

Lb Interface SCCP Conn Conf Timer (ms) lb_int_sccp_tconn_est (OMC-R parameter name: lb_sccp_tconn_est)

Lb Interface SCCP TIAR Timer (ms) lb_int_sccp_tiar

2-116

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GSM location services

Table 2-18

Location Services parameters (Continued) Description 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 to 15,000 ms. Default is 10,000 ms. 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 to 1,000,000 ms. Default is 30,000 ms. 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 to 1,000,000 ms. Default is 30,000 ms. The value of this parameter should be less than the lb_int_sccp_tiar parameter. 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 to 1,000,000 ms. Default is 60,000 ms. 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 to 1,000,000 ms. Default is 90,000 ms. 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 to 255. Default is 0.

OMC-R GUI field name/BSS parameter name Lb Interface SCCP Rel Complete Timer (ms) lb_int_sccp_trel

Lb Interface SCCP Rel Timer (ms) lb_int_sccp_released (OMC-R parameter name: lb_sccp_released) Lb Interface SCCP TIAS Timer (ms) lb_int_sccp_tias

Lb Interface SPI Timer (ms) lb_int_spi

Lb Subsystem Status Test Timer (ms) lb_int_t_stat_info (OMC-R parameter name: lb_t_stat_info)

Lb Interface CP Elements: Lb Interface Global Reset Repetitions lb_int_global_reset_repetitions (OMC-R parameter name: lb_globresetReps)

68P02901W17-R 14 Apr 2006

GMR-01

2-117

GSM location services

Chapter 2: Configuring BSS Features

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 BTS BSC RXCDR

Command chg_element disp_element

See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS commands, prompts, and parameters.

2-118

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GSM location services

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

68P02901W17-R 14 Apr 2006

GMR-01

2-119

Enhanced GPRS One Phase Access

Chapter 2: Configuring BSS Features

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 summarise, the Enhanced GPRS One Phase Access feature provides: The one phase uplink TBF access procedure, also see "GPRS Interleaving TBFs" on page 2-94. 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).

2-120

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced GPRS One Phase Access

Table 2-20

Enhanced GPRS One Phase Access parameters Description Values

OMC-R GUI field name/BSS parameter name 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 or not 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 greyed-out in the OMC-R GUI if the GPRS feature is restricted (disabled). Displayed in the GPRS grouping of the BSS Detailed View form. Indicates whether or not Enhanced GPRS One Phase Access feature is enabled or disabled for the BSS. This parameter can be modified by a user. The field is greyed-out in the OMC-R GUI if the Enhanced GPRS One Phase Access Feature (eopOpt) and GPRS feature are restricted (disabled). {23956} The QoS feature (see "Quality of Service (QoS)" on page 2-171) modifies the behaviour of this parameter. If bssgp_pfc_bit is set to On (1), any modification to eop_enabled will be 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).

Enhanced One Phase Access eop_enabled

0 or 1, where: Disabled (0). Enabled (1). Default is Disabled (0).

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-121

Enhanced GPRS One Phase Access

Chapter 2: Configuring BSS Features

Table 2-20

Enhanced GPRS One Phase Access parameters (Continued) Description Values

OMC-R GUI field name/BSS parameter name CELL parameters: Number of TS In Pre-load USF Active State ts_in_usf_active

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 greyed-out in the CELL Detailed View form.

0 to 3. If not set by a user at cell creation time, defaults to 1 timeslot.

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

2-122

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced GPRS 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

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

68P02901W17-R 14 Apr 2006

GMR-01

2-123

PBCCH/PCCCH feature

Chapter 2: Configuring BSS Features

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 signalling. 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 Uplink only Functionality Used by MS to initiate uplink transfer for data or signalling information. Used by BSS to send resource assignment to an MS prior to packet transfer. Used by BSS to page an MS for Packet Switched (PS) or Circuit Switched (CS). Used by BSS to broadcast packet data specific System Information. Not supported.

Packet Logical Channels Packet Random Access Channel (PRACH) (on PCCCH) Packet Access Grant Channel (PAGCH) (on PCCCH) Packet Paging Channel (PPCH) (on PCCCH) Packet Broadcast Control Channel (PBCCH) Packet Notification Channel (PNCH)

Downlink only

Downlink only

Downlink only Downlink only

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 signalling is conducted on the Common Control Channel (CCCH) channels. In a lightly loaded GSM/GPRS network, BCCH/CCCH has sufficient signalling capacity for both GSM and GPRS. In a highly loaded GSM/GPRS network, PBCCH/PCCCH provides more signalling capabilities for both the GSM voice and GPRS service. In addition, if PBCCH/PCCCH is enabled, there is reduced internal traffic over the GPRS Signalling Link (GSL) and Radio Signalling 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.

2-124

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH feature

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 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 1 2 3 Change PBCCH/PCCCH for a cell

Set gprs_enabled to 0 (Disabled). Set pccch_enabled to 1 (Enabled). Set gprs_enabled to 1 (Enabled).

68P02901W17-R 14 Apr 2006

GMR-01

2-125

PBCCH/PCCCH feature

Chapter 2: Configuring BSS Features

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

2-126

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH feature

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 Description 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: SGSN Release sgsn_release 0 - Disabled. 1 - Enabled.

OMC-R GUI field name/BSS parameter name BSS parameters: PBCCH/PCCCH Feature pccchOpt

Displayed in the GPRS grouping in the BSS Detailed View. Specifies the SGSN release version. Valid values are 0 or 1, where: 0 - The SGSN is Release 98 or older. 1 - The SGSN is Release 99 onwards.

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

68P02901W17-R 14 Apr 2006

GMR-01

2-127

PBCCH/PCCCH feature

Chapter 2: Configuring BSS Features

Table 2-22

PBCCH/PCCCH parameters (Continued) Description 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 values are 1. Default: 1. Displayed in the GPRS grouping in the CELL Detailed View. Specifies the number of PBCCH blocks per 52-frame-multiframe. Valid values are 1 to 4. Default: 2. 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 to 11. Valid values are 0 to 10. Default: 3. Displayed in the GPRS grouping in the CELL Detailed View. Specifies the number of PRACH blocks per 52-frame-multiframe. Valid values are 1 to 12. Default: 4. When psi1_repeat_period is set to 1, bs_pbcch_blks cannot be set to 1 or 2. 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 to 16. Default: 5. If in range 1 to 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. Cont.

OMC-R GUI field name/BSS parameter name Number of PCCCH Timeslots bs_pcc_chans

Number of Blocks Allocated to PBCCH bs_pbcch_blks

Number of PAGCH Blocks per Multiframe bs_pag_blks_res

Number of PRACH Blocks per Multiframe bs_prach_blks

Time Interval for Scheduling PSI Messages psi1_repeat_period (OMC-R parameter name: psi1_repeat_prd)

2-128

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH feature

Table 2-22

PBCCH/PCCCH parameters (Continued) Description 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 to 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.

OMC-R GUI field name/BSS parameter name Non-DRX Mode Transfer Period Duration pccch_drx_timer_max (OMC-R parameter name: pccch_drx_max_t)

Slots Between Channel Request prach_s

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 to 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. Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-129

PBCCH/PCCCH feature

Chapter 2: Configuring BSS Features

Table 2-22

PBCCH/PCCCH parameters (Continued) Description 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 to 15, where: 0 - persistence level 0. 1 - persistence level 1. 2 - persistence level 2. ... 14 - persistence level 14. 15 - persistence level 16.

OMC-R GUI field name/BSS parameter name Persistence Level 1 to 4 persistence_lvl_0 persistence_lvl_1 persistence_lvl_2 persistence_lvl_3

Retransmissions Allowed for Radio Priority 1 to 4 prach_mx_retran_0 prach_mx_retran_1 prach_mx_retran_2 prach_mx_retran_3

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 to 3, where: 0 - 1 retransmission allowed. 1 - 2 retransmissions allowed. 2 - 4 retransmissions allowed. 3 - 7 retransmissions allowed. Cont.

2-130

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH feature

Table 2-22

PBCCH/PCCCH parameters (Continued) Description 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 to 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.

OMC-R GUI field name/BSS parameter name 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)

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 to 63 (representing -110 dB to -47 dB). Default: 0. 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 to 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. Cont.

GPRS MS Max Transmit Power gprs_ms_txpwr_max_cch (OMC-R parameter name: gprs_mx_txpwr_cch)

68P02901W17-R 14 Apr 2006

GMR-01

2-131

PBCCH/PCCCH feature

Chapter 2: Configuring BSS Features

Table 2-22

PBCCH/PCCCH parameters (Continued) Description Displayed in the GPRS grouping in the CELL Detailed View. Specifies the Hierarchical Cell Structures (HCS) priority class. Valid values are 0 to 7. Default: 0 (Lowest Priority). 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 to 31, where: 0 means -110 dBm. 1 means -108 dBm. ... 31 means -48 dBm.

OMC-R GUI field name/BSS parameter name HCS Priority Class priority_class

HCS Signal Strength hcs_thr

GPRS Cell Reselect Hysteresis gprs_cell_reselect_hysteresis (OMC-R parameter name: gprs_reselect_hys)

Displayed in the GPRS grouping in the CELL Detailed View. Specifies the additional hysteresis that applies in ready state for cells in the same Routing Area (RA). Valid values are 0 to 7, where: 0 = 0 dB. 1 = 2 dB. 2 = 4 dB. ... 7 = 14 dB.

C32 Exception Rule c32_qual

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.

C31 Hysteresis c31_hyst

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

2-132

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH feature

Table 2-22

PBCCH/PCCCH parameters (Continued) Description 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 to 7, where: 0 = 0 dB. 1 = 2 dB. 2 = 4 dB. ... 7 = 14 dB.

OMC-R GUI field name/BSS parameter name 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)

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 to 7, where: 0 = 0 dB. 1 = 10 dB. 2 = 20 dB. 3 = 30 dB. ... 6 = 60 dB. 7 = infinity.

GPRS Penalty Time gprs_penalty_time

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 to 31, where: 0 = 10 seconds. 1 = 20 seconds. ... 31 = 320 seconds. Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-133

PBCCH/PCCCH feature

Chapter 2: Configuring BSS Features

Table 2-22

PBCCH/PCCCH parameters (Continued) 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 to 31, where: 0 = -52 dB. 1 = -48 dB. ... 10 = -12 dB. 11 = -10 dB. ... 22 = +12 dB. 23 = +16 dB. ... 31 = +48 dB. Cont.

OMC-R GUI field name/BSS parameter name GPRS Cell Reselect Offset gprs_reselect_offset (OMC-R parameter name: gprsReselectOffs)

2-134

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH feature

Table 2-22

PBCCH/PCCCH parameters (Continued) Description 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 to 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. Cont.

OMC-R GUI field name/BSS parameter name 3G Cell Threshold for Multi-RAT MS qsearch_p

68P02901W17-R 14 Apr 2006

GMR-01

2-135

PBCCH/PCCCH feature

Chapter 2: Configuring BSS Features

Table 2-22

PBCCH/PCCCH parameters (Continued) 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).

OMC-R GUI field name/BSS parameter name Allow Search for 3G Cells search_prio_3g

FDD Cell Reselection Offset fdd_gprs_qoffset

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

2-136

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

PBCCH/PCCCH feature

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.

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 PCU parameter: GPRS Network Operation Mode (gprs_network_operation_mode): disp_element gprs_network_operation_mode pcu 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 pcu

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.

68P02901W17-R 14 Apr 2006

GMR-01

2-137

Adaptive Multi-Rate (AMR)

Chapter 2: Configuring BSS Features

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 Meaning (Kbps) 12.20 10.20 7.95 7.4 6.7 5.9 5.15 4.75 Available at Full Rate (FR) YES YES NO YES YES NO YES NO Available at Half Rate (HR) NO NO YES YES YES YES YES NO

Codec mode value 0 1 2 3 4 5 6 7

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.

2-138

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Adaptive Multi-Rate (AMR)

AMR Half Rate and GSM Half Rate


The GSM Half Rate feature builds on the AMR Half Rate feature. It introduces 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-149.

AMR hardware and software utilisation


The AMR feature is only available on the following radio platforms: CTU. CTU2. TCU-A. TCU-B.

The BSC and RXCDR software supports 8 Kbps switching so that half-rate enabled RTFs are provisioned on only two E1 timeslots between the BSC and BTS, that is, 8 Kbps backhaul is utilised. However, 7.95 capable RTFs are provisioned on an additional two E1 timeslots between the BSC and BTS, because 7.95 Kbps mode only fits in 16 Kbps 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.

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.

68P02901W17-R 14 Apr 2006

GMR-01

2-139

Adaptive Multi-Rate (AMR)

Chapter 2: Configuring BSS Features

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. The existing GSM Handover and Power Control algorithms are still used for the Half Rate AMR channel, but, similar to Full Rate Link Adaptation, a new set of Handover and Power control thresholds are introduced.

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

2-140

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Adaptive Multi-Rate (AMR)

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: AMR Feature (amrOpt). AMR Enhanced GDP Feature (amrEGDPProOpt). AMR Enhanced Capacity Feature (amrEnhancedCapOpt). AMR TCU-A Feature (amrTCUAOpt). AMR TCU-B Feature (amrTCUBOpt).

68P02901W17-R 14 Apr 2006

GMR-01

2-141

Adaptive Multi-Rate (AMR)

Chapter 2: Configuring BSS Features

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 <feature <feature <feature <feature no.> no.> no.> no.> no.> AMR AMR Using Enhanced GDP AMR Enhanced Capacity TCU-A support for AMR 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 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. 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. 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. {24541} If this feature is enabled, the RXCDR will support 4800 CICs and 8 kbit/s switching. Cont. Details

amrEGDPProOpt

amrEnhancedCapOpt

2-142

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Adaptive Multi-Rate (AMR)

Table 2-24

AMR parameters (Continued) BSS parameter name Details 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. 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. See BSS Detailed View fields - ("Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping" on page 4-38) for details of these parameters. See BSS Detailed View fields - ("Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping" on page 4-38) for details of these parameters. See BSS Detailed View fields - ("Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping" on page 4-38) for details of these parameters. See BSS Detailed View fields - ("Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping" on page 4-38) for details of these parameters.

amrTCUAOpt

amrTCUBOpt

Half Rate AMR BSS parameters: amr_bss_half_rate_enabled force_hr_usage

Full Rate AMR BSS parameters: amr_bss_full_rate

Link Adaptation BSS parameters: amr_dl_thresh_adjust amr_dl_la_mode_chg_min

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 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-35) for further details. See CELL Detailed View fields, General - ("AMR Full Rate grouping" on page 8-36) for details.

Full Rate AMR Cell parameters: amr_full_rate

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-143

Adaptive Multi-Rate (AMR)

Chapter 2: Configuring BSS Features

Table 2-24

AMR parameters (Continued) BSS parameter name Details See CELL Detailed View fields, General - grouping ("AMR/GSM Half Rate grouping" on page 8-42) for details of these parameters.

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 Full Rate Active Codec Set (ACS) Cell parameters: amr_fr_acs amr_fr_icm 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 See CELL Detailed View fields, General - ("AMR Full Rate grouping" on page 8-36) for details.

Cont.

2-144

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Adaptive Multi-Rate (AMR)

Table 2-24

AMR parameters (Continued) BSS parameter name Details

Half Rate Active Codec Set (ACS) Cell parameters: 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 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 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-66) for details of these parameters. See CELL Detailed View fields ("Power control AMR Full Rate" on page 8-71) for details of these parameters. See CELL Detailed View fields, General - ("AMR Full Rate grouping" on page 8-36) for details. See CELL Detailed View fields, General ("AMR/GSM Half Rate grouping" on page 8-42) for details.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-145

Adaptive Multi-Rate (AMR)

Chapter 2: Configuring BSS Features

Table 2-24

AMR parameters (Continued) BSS parameter name Details

Half Rate AMR Cell Power Control 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 Full Rate Link Adaptation Cell parameters: amr_fr_dl_la_enabled amr_fr_ul_la_enabled Half Rate RTF parameters: half_rate_enabled allow_8k_trau 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 (Table 4-33) for details. See RTF Detailed View fields, Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping (Table 9-67) for details. CELL Detailed View fields, General - AMR Full Rate grouping (Table 8-14) for details of these parameters. See CELL Detailed View fields, General - AMR Half Rate grouping (Table 8-15) for details of these parameters. See CELL Detailed View fields, ("Power control AMR/GSM Half Rate" on page 8-72) for details of these parameters.

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

2-146

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Adaptive Multi-Rate (AMR)

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.

68P02901W17-R 14 Apr 2006

GMR-01

2-147

Adaptive Multi-Rate (AMR)

Chapter 2: Configuring BSS Features

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.

2-148

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GSM Half Rate

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


{22404} This feature interacts with the IMRM feature, see "Intelligent Multilayer Resource Management (IMRM)" on page 2-161 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.

68P02901W17-R 14 Apr 2006

GMR-01

2-149

GSM Half Rate

Chapter 2: Configuring BSS Features

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 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. 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-40) for details of these parameters. See CELL Detailed View fields, General AMR/GSM Half Rate grouping ("AMR/GSM Half Rate grouping with GSM Half Rate" on page 8-49) for details of these parameters. Details

GSM Half Rate Channel Mode Usage BSS parameters: gsm_bss_half_rate_enabled

AMR/GSM Half Rate Cell parameters: gsm_half_rate_enabled

2-150

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GPRS Seamless Cell Reselection

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

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

68P02901W17-R 14 Apr 2006

GMR-01

2-151

GPRS Seamless Cell Reselection

Chapter 2: Configuring BSS Features

GPRS Seamless Cell Reselection parameters


Table 2-26 details the GPRS Seamless Cell Reselection parameters. Table 2-26 Seamless Cell Reselection parameters Description 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. Greyed-out if the BSS Detailed View field: GPRS Seamless Cell Reselection Feature (parameter name: scrOpt) is set to Disabled (0). Attributes 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.

OMC-R GUI field name/ parameter name GPRS Seamless Cell Reselection Enabled scr_enabled

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.

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

2-152

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

GPRS Seamless Cell Reselection

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

68P02901W17-R 14 Apr 2006

GMR-01

2-153

Current Bucket Level (CBL) feature

Chapter 2: Configuring BSS Features

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.

2-154

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Current Bucket Level (CBL) feature

Current Bucket Level parameters


Table 2-27 details the Current Bucket Level parameters. Table 2-27 Current Bucket Level parameters 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. Greyed-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 signalling BVCI. CBL feature shall be enabled/disabled subject to this negotiation. Ongoing data transfers will be affected due to signalling reset. Do you wish to continue?

OMC-R GUI field name/BSS parameter name Current Bucket Level Feature bssgp_cbl_bit

68P02901W17-R 14 Apr 2006

GMR-01

2-155

Enhanced Scheduling

Chapter 2: Configuring BSS Features

Enhanced Scheduling

Overview
In GSR6 GPRS Enhanced One-Phase (EOP) access, when a Random Access CHannel (RACH) was received at a BTS, the BTS used an EOP assignment if available. When the EOP assignments were exhausted, and the RACH throttle threshold had not been reached, the RACH was sent to the PCU. The PCU then responded by sending a one-phase immediate assignment message back to BTS for transmission to the mobile station (MS). Two-phase access was only used if the MS explicitly requested it. The two-phase RACH was processed at the PCU and the required messaging was carried over the RSL/GSL. The number of messages exchanged between the PCU and BTS over the RSL by these different TBF establishment methods may have caused the RSL to overload at high RACH arrival rates. This overloading may have adversely affected circuit switched traffic and reduced GPRS traffic handling capability. The Enhanced Scheduling feature introduces mechanisms that allows 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 optimise 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).

2-156

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced Scheduling

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). Table 2-28 Enhanced Scheduling parameters Description Values

OMC-R GUI field name/BSS parameter name BSS parameters: Increased PRP Capacity Feature Supported prp_capacity_opt

Displayed in the Optional Features grouping of the BSS Detailed View form. Indicates whether or not 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 greyed-out in the OMC-R GUI if the GPRS feature is restricted (disabled). 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). 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.

0 or 1, where: Disabled (0). Enabled (1). Default is Disabled (0).

Increased PRP Capacity Feature Enabled inc_prp_cap_ena

True (1) or False (0). Default is False (0).

Most Common Multislot of GPRS Mobiles gprs_com_ms_class

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

68P02901W17-R 14 Apr 2006

GMR-01

2-157

Enhanced Scheduling

Chapter 2: Configuring BSS Features

Table 2-28

Enhanced Scheduling parameters (Continued) Description 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). Displayed in the GPRS grouping of the BSS Detailed View form. Determines whether Uplink or Downlink bias is applied to mobiles of multislot class 6 and 10. 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). 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 to 4. Default is 3. Values

OMC-R GUI field name/BSS parameter name PRR Blocks Reservation Aggressiveness Factor prr_aggr_factor

GPRS Uplink or Downlink bias gprs_ul_dl_bias

UL (0) or DL (1). Default is DL (1).

CELL parameters: Minimal number of dynamic PRR blocks gprs_min_prr_blks 0 to 24. Default is 0.

BTS site parameters: Percentage of RSL Reserved for CS percent_traf_cs 0 to 90. Default is 55.

2-158

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced Scheduling

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

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.

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

68P02901W17-R 14 Apr 2006

GMR-01

2-159

Enhanced Scheduling

Chapter 2: Configuring BSS Features

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

2-160

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Intelligent Multilayer Resource Management (IMRM)

Intelligent Multilayer Resource Management (IMRM)


{22404}

Overview of IMRM
The Intelligent Multilayer Resource Management (IMRM) feature enables optimal traffic management by utilizing all available frequency bands deployed in a particular area: Multi-band (PGSM, EGSM, DCS1800, and so on) Multi-layer (macro and micro) Multi-RAT (GSM and UMTS) networks

The existing Advanced Load Management (ALM) feature allowed an operator to re-direct mobile traffic to a preferred band by setting certain parameters in each cell. However, the ALM feature has difficulty managing the increased number of different layers within the BSS (for example, macro, micro, pico, PGSM, EGSM, DCS1800 and UMTS). Using the ALM feature with more than two bands resulted in mobiles, in some circumstances, handing over to macro layers when the operator wanted the mobile to be maintained on the micro layer. EGSM Layer Management, or ALM for EGSM carriers, overrides the preferred band set by the ALM feature so that the EGSM layer is not under utilized. The IMRM feature is an enhancement to the Advanced Load Management (ALM) feature and EGSM Layer Management. IMRM uses a weight-based algorithm that distributes calls between all available bands before congestion is encountered. On call establishment or when handover from the existing serving cell is required, the algorithm chooses a "preferred" band based on the band weightings and mobile capabilities. The preferred band is biased by operator settable parameters to reflect intrinsic capacity available on each band, number of mobiles users capable of accessing that band, and service consideration. The IMRM and the ALM algorithms cannot be operated in the same cell. The two algorithms may be operated in neighbouring cells either within the same BSS or different BSSs.

68P02901W17-R 14 Apr 2006

GMR-01

2-161

Intelligent Multilayer Resource Management (IMRM)

Chapter 2: Configuring BSS Features

Background to IMRM
Over many years, numerous features have been introduced to aid in the management of multi-frequency band networks. Some to support the initial introduction of a new frequency band, that is DCS1800 and later EGSM, and others to try and optimise resource utilisation across the multitude of different bands, for example Multiband Handover, SBCCH and EGSM Layer Management. These algorithms, generally are in competition rather than complimentary, and heavily biased towards a mobile capability profile (in terms of frequency band support), though valid at the time of introduction, no longer applicable and leads to less than optimal network performance. The two main areas of concern impacted by the IMRM feature are: Imbalance between bands, for example, the DCS1800 is heavily utilised whilst other bands are not. Imbalance between layers, that is, macro overlay running at very high utilisation levels, whilst micro underlay can be very lightly used.

The first of these has a direct impact on the second, that is, where the micro underlay is not the same frequency type as the macro preference, then traffic which should be supported on the micro layer is targeted to the preferred band macro layer. This causes the effect of over-utilisation in the macro layer and under-utilisation in the micro layer. By addressing the band imbalance, that is, allowing for better distribution of traffic across all available frequency bands, IMRM has a positive effect on the layer imbalance (no distinction made between micro layer band capability and macro layer band capability). The key drivers for traffic distribution are network capacity for the supported frequency bands in conjunction with multi-band mobile penetration. These vary between networks and also within a single network over a period of time a typical example of this would be the gradual increase in penetration levels of DCS1800 capable mobiles.

Benefits of IMRM
The following are the benefits of the IMRM feature: Simplicity of operation and deployment. Efficient use of spectrum resource as a result of the ability to prioritise traffic allocation by both band and layer. Optimises Voice and CS Data usage with available resources. Traffic management between systems from different vendors. Balanced traffic across radio access technologies. Unified and scalable solution to resource management. Reduced drop call rate and improved Quality of Service.

2-162

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Intelligent Multilayer Resource Management (IMRM)

Description of IMRM feature settings


Layer weightings
IMRM introduces the concept of Layer Weightings which are definable on a per-cell basis, with the supported layers covering: PGSM. EGSM (the EGSM weighting covers the EGSM frequencies only, not the combination of EGSM and PGSM frequencies). DCS1800. PCS850 (for future support). PCS1900 (for future support) GSM450 (for future support). UMTS.

The actual weightings should be defined based on the available capacity (directly within the cell, but should also consider neighbouring cells, micro underlay and/or macro overlay and so on), as well as mobile penetration levels supporting the particular band/RAT. The statically defined weightings are then dynamically combined with the capabilities of the mobile requesting network resources, to define a Band Preference for targeting of network resources for allocation. The mobile capabilities are used to discount layers that the mobile cannot support, the remaining layer weightings are then scaled to represent a probability weighting for each of the individual layers. A random element is then introduced to effect the distribution across the available layers. The higher the weighting is set for a particular band (relative to other bands), the more chance that the layer will be selected. Setting a layer to the maximum weighting removes the distribution effect and emulates ALM. A default mode of operation is supported whereby the system applies an internally defined set of weightings where an operator has enabled IMRM but not configured band weightings in that cell. There are two sets of internal weightings based on whether EGSM is supported or not in the current cell. These are shown in Table 2-29. Table 2-29 EGSM Support YES NO Default Band weightings for EGSM and non-EGSM enabled systems PGSM 45 50 EGSM 10 0 DCS1800 45 50 UMTS 0 0

These internally defined weight values are used as a direct replacement for the per-cell configuration items where all items have been left undefined. Defining any of the supported weights results in the algorithm using the configuration items rather than the internal defaults. The internal defaults are not configurable.

68P02901W17-R 14 Apr 2006

GMR-01

2-163

Intelligent Multilayer Resource Management (IMRM)

Chapter 2: Configuring BSS Features

Unlike existing behaviour whereby band preference is defined statically for a cell (using the band_preference parameter), IMRM supports the dynamic calculation of the Preferred Band on a per-call basis. This is be performed as per the following: On initial Assignment. On in-coming External Handover. On in-coming Internal Handover whereby: Source cell does not have the Preferred Band defined (non-IMRM Cell). Source cell defined Preferred Band not supported in target cell. Target cell configured to force recalculation.

The dynamically calculated Preferred Band is then applied as for (and in replacement of) the current statically defined band_preference, and in conjunction with (the current) band_preference_mode, it will be used to define target resources on initial resource allocation and/or handover behaviour. See Table 2-32 for further details. UMTS support is included, but is currently limited by a number of factors, such as limited coverage, the expected limited penetration of multi-RAT capable handsets and limitations on resource allocation between RATs on service request.

Therefore it is currently not recommended that IMRM is used to control 2G-3G handovers.

Use of Band Preference Mode


Band preference mode (band_preference_mode) is a parameter that can be set by an operator on a per-cell basis. It originates with the Advanced Load Management (ALM) feature (a forerunner of IMRM). The ALM feature allows the network operator to redirect mobile traffic to a network operator preferred band by setting the band_preference and band_preference_mode parameters per cell. A preference for a particular band is set by the band_preference parameter; in IMRM this is replaced by the per-call preferred band (PCPB) parameter, which performs the same function, but on a per-call rather than a per-cell basis. The possible settings of the PCPB are shown in Table 2-30. Table 2-30 Setting 1 2 3 4 Per-call Preferred Band (PCPB) settings Preferred Band PGSM. EGSM. DCS1800. UMTS.

2-164

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Intelligent Multilayer Resource Management (IMRM)

In an IMRM-enabled cell the PCPB is determined by the application of the IMRM algorithm, based on the band-weightings within that cell. The band preference mode determines the behaviour of all mobiles that are currently in dedicated mode (that is, have a TCH up) within that cell. Table 2-31 summarizes the possible values that the band preference mode can take, along with the resulting system behaviours. Table 2-32 describes the band selection algorithms per band preference mode that are invoked on assignment and handover request. Table 2-31 Setting 0 1 2 3 4 5 6 Summary of band preference modes and their associated behaviours Comment Attempt to handover to strongest reported neighbour. Attempt assignment to strongest preferred band reported neighbour (SDCCH TCH). Attempt handover to strongest preferred band reported neighbour. 1 and 2 above. Attempt assignment to strongest preferred band TCH immediately after initial assignment. 1 or 4 above. 1 or 4 above.

Correct setting of the band-preference mode is important in optimising an IMRM-enabled system as it controls the interaction between cells, and important in moderating the interaction of other features with IMRM. Table 2-32 Setting 0 1 Assignment and Handover band selection algorithms for the band preference modes Assignment Outer Zone Local preferred then / or Neighbour preferred then Local non-preferred Outer Zone preferred then / or Outer Zone non-preferred Handover Strongest. Inner Zone continual. Strongest. Inner Zone continual when preferred. Inner Zone continual when preferred. Normal / Congestion to preferred. Inner Zone continual when preferred. Normal / Congestion to preferred. Inner Zone continual when preferred. Preferred neighbour continual. Normal / Congestion to preferred. Cont. 68P02901W17-R 14 Apr 2006 2-165

Local preferred then / or Neighbour preferred then Local non-preferred Outer Zone Outer Zone preferred then / or Outer Zone non-preferred

GMR-01

Intelligent Multilayer Resource Management (IMRM)

Chapter 2: Configuring BSS Features

Table 2-32 Assignment and Handover band selection algorithms for the band preference modes (Continued) Setting 5 Assignment Local preferred then / or Neighbour preferred then Local non-preferred Outer Zone Handover Inner Zone continual when preferred. Preferred neighbour continual. Normal / Congestion to preferred.

Same as 5.

In addition, Band Preference Modes (BPM) 4 and 5 both allow assignment to the strongest preferred band cell immediately after initial TCH assignment. If the PCPB differs from the BCCH band, then an intercell handover may take place immediately after the TCH has been assigned. The selection of band preference mode 4 or 5 should be based on the desired cell selection algorithm, and the configuration of cells within the neighbourhood. In this case, the difference between BPM 2 and 3, and 4 and 5 is that in the former handover to the preferred band will take place immediately on qualification if the preferred band is in the IZ in a dual band cell, whereas in the latter handover to any preferred band cell (that is, not just intra-cell handover, but handover to the optimal preferred band neighbour, whether it is in the same cell or not) will be attempted immediately after assignment. Motorola currently advise BPM 2 or 3 over 4 or 5, as these perform a local handover only, and are therefore unlike to consume the same level as system resources as the inter BTS or external handover that may be triggered by BPM 4 or 5.

An immediate handover from the initial assignment band to the PCPB may impact voice quality for affected handsets. This may also be dependent on the speed of the signalling, and on how quickly the call is established after the initial TCH assignment.

Use of IMRM Force Recalculation flag


The IMRM Force Recalculation (imrm_force_recalc) flag allows an operator to specify that upon handover into a particular cell, the PCPB for that call will be recomputed based on the Band Weightings applicable to that cell. Cells that may be considered as gateways into particular geographic areas or groups of cells (for example, covering main line stations or autoroute exits) may require this flag to be set in order to ensure good load-balancing across calls entering these areas.

2-166

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Intelligent Multilayer Resource Management (IMRM)

Where the IMRM Force Recalculation (imrm_force_recalc) flag is set, the PCPB of that cell will be recomputed based on the Band Weightings of the current cell. This may or may not change the PCPB (depending on the original PCPB, the MS capabilities and the Band Weightings). The band preference mode applied in that cell will then determine at what point a handover may then take place.

Outer to Inner zone handovers (where the Inner zone is the Preferred band) will still take place as soon as the Inner zone qualifies, as per ALM.

Neighbour List Selection


For multi-band handover, ensure that the neighbour list length in each band is sensibly matched to the IMRM weightings and band preference mode. The neighbour lists are defined in each cell on a per-band basis. When a call has entered an IMRM enabled cell, it will be assigned a PCPB. The combination of the PCPB and the band preference mode will determine the MSs handover behaviour; when and how it attempts handover, and whether that handover may involve band reassignment. If the ratio of IMRM band weightings vary significantly from the ratio of qualifying neighbours for each band, then congestion problems may result, due to the IMRM algorithm attempting to assign or handover calls into a band with few qualifying neighbours. This scenario is most likely to be seen in dense urban areas suffering from canyoning, and in gateway regions such as airport termini and railway stations, which are likely to be served by micro and macro cells.

Interaction with other features


IMRM interacts with a number of features and it is important to understand the implications of adjusting system parameters and the impact they will have on IMRM and other features.

For information about the interaction of IMRM with other BSS features, see Intelligent Multilayer Resource Management Field Optimization Guide (GSM-BSS-22404-FOG-001).

Prerequisites to configuring Intelligent Multilayer Resource Management


Before configuring IMRM, ensure the Multiband Inter-Cell Handover (mbInterCellHoOpt parameter) has been enabled: See Table 4-4, "Configuring enhanced SDCCH to TCH band assignment" on page 8-212 and "Configuring a cell for coincident multiband handovers" on page 8-194 for details

68P02901W17-R 14 Apr 2006

GMR-01

2-167

Intelligent Multilayer Resource Management (IMRM)

Chapter 2: Configuring BSS Features

Intelligent Multilayer Resource Management parameters


Table 2-33 details the parameters associated with the Intelligent Multilayer 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-33 Intelligent Multilayer Resource Management parameters Description Values

OMC-R GUI field name/BSS parameter name BSS parameters: Intelligent Multilayer Feature imrmOpt

Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether IMRM feature is unrestricted (enabled) or restricted (disabled). 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 Multilayer 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-82. Displayed in the CELL Detailed View, General section, Multiband handover grouping. When the IMRM feature (imrmOpt) is enabled, displays whether or not a recalculation on the preferred band to handover to is executed on the cell. See "Use of IMRM Force Recalculation flag" on page 2-166 for further details of how to set this parameter.

0 or 1, where: Disabled (0). Enabled (1).

CELL parameters: Band Preference band_preference 1, 2, 4, 8, or 16.

IMRM Force Recalculation imrm_force_recalc

0 or 1, where: 0 = Disabled. 1 = Enabled. Default is 0.

Cont.

2-168

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Intelligent Multilayer Resource Management (IMRM)

Table 2-33

Intelligent Multilayer Resource Management parameters (Continued) Description 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 "Layer weightings" on page 2-163 for further details of how to set this parameter. 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 "Layer weightings" on page 2-163 for further details of how to set this parameter. 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 "Layer weightings" on page 2-163 for further details of how to set this parameter. Values 0 to 100. Default is 0.

OMC-R GUI field name/BSS parameter name PGSM Weighting (0100) imrm_pgsm_weight

IMRM EGSM Weighting (0-100) imrm_egsm_weight

0 to 100. Default is 0.

IMRM DCS1800 Weighting (0-100) imrm_dcs1800_weight (Field name in OMC-R database table: mrm_dcs18_weight)

0 to 100. Default is 0.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-169

Intelligent Multilayer Resource Management (IMRM)

Chapter 2: Configuring BSS Features

Table 2-33

Intelligent Multilayer Resource Management parameters (Continued) Description 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. Greyed-out if either the IMRM or 2G3G feature is restricted. See "Layer weightings" on page 2-163 for further details of how to set this parameter. 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 "Use of Band Preference Mode" on page 2-164 for recommended settings when used in conjunction with IMRM. Values 0 to 100. Default is 0.

OMC-R GUI field name/BSS parameter name IMRM UMTS Weighting (0-100) imrm_umts_weight

Band Preference Mode band_preference_mode

0 to 6. Default is 0.

2-170

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Quality of Service (QoS)

Quality of Service (QoS)


{23956}

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 the following features have been enabled: Network Assisted Cell Change (NACC) (naccOpt parameter). See "Network Assisted Cell Change (NACC)" on page 2-181 for further details. GPRS (gprsOpt parameter).

Quality of Service parameters


Table 2-34 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).

68P02901W17-R 14 Apr 2006

GMR-01

2-171

Quality of Service (QoS)

Chapter 2: Configuring BSS Features

Table 2-34

Quality of Service parameters Description Values

OMC-R GUI field name/BSS parameter name BSS parameters: 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). 0 or 1, where: Off (0). On (1). Default is Off (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. Greyed 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 signalling BVCI. QoS feature shall be enabled/disabled subject to this negotiation. Ongoing data transfers will be affected due to signalling reset. Do you wish to modify? Displayed in the Quality of Service grouping in the BSS Detailed View. Indicates which ARP signalling selection option is used for R99/R4 mobiles. Greyed 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.

ARP Signaling Selection arp_signal_sele

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

Cont.

2-172

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Quality of Service (QoS)

Table 2-34

Quality of Service parameters (Continued) Description 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. Greyed 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. 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. Greyed 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. Values 10 to 40 Default is 40.

OMC-R GUI field name/BSS parameter name THP Weight of Interactive 2 Class thp_i2_weight

THP Weight of Interactive 3 Class thp_i3_weight

10 to 40 Default is 40.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-173

Quality of Service (QoS)

Chapter 2: Configuring BSS Features

Table 2-34

Quality of Service parameters (Continued) Description 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. Greyed-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. 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. Greyed-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. Values 10 to 40 Default is 40.

OMC-R GUI field name/BSS parameter name THP Weight of Background Class thp_bg_weight

THP Weight of Best Effort Class thp_be_weight

0 to 40 Default is 40.

Cont.

2-174

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Quality of Service (QoS)

Table 2-34

Quality of Service parameters (Continued) Description 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. Greyed-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 will display the following message: WARNING: Any changes to pfc_be_arp do not change system behaviour when arp_signal_sele is equal to 0. Displayed in the GPRS grouping in the BSS Detailed View. QoS modifies the behaviour 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. Displayed in the GPRS grouping in the BSS Detailed View. QoS modifies the behaviour of this parameter. If bssgp_pfc_bit is set to On (1), any modification to eop_enabled will be 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. Values 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).

OMC-R GUI field name/BSS parameter name ARP Parameter for Best Effort Class PFCs pfc_be_arp

GPRS Scheduling Beta Algorithm gprs_sched_beta

Enhanced One Phase Access eop_enabled

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-175

Quality of Service (QoS)

Chapter 2: Configuring BSS Features

Table 2-34

Quality of Service parameters (Continued) Description Values

OMC-R GUI field name/BSS parameter name CELL parameters: MTBR for Interactive THP 1 qos_mtbr_i1_dl

Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the downlink Minimum Throughput Budget Requirement (in Kbps) ranges from 2-24 for Interactive traffic class, traffic handling priority 1. Greyed-out if QoS Feature is not purchased. Read-only if bssgp_pfc_bit is set to On (1). Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in Kbps) ranges from 2-6 for Interactive traffic class, traffic handling priority 1. Greyed-out if QoS Feature is not purchased. Read-only if bssgp_pfc_bit is set to On (1). Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in Kbps) ranges from 2-6 for Interactive traffic class, traffic handling priority 1. Greyed-out if QoS Feature is not purchased. Read-only if bssgp_pfc_bit is set to On (1).

2 to 24. Default 2.

Uplink MTBR for Interactive THP 1 qos_mtbr_i1_ul

2 to 6. Default is 2.

Uplink MTBR for Interactive THP qos_mtbr_i1_ul

2 to 6. Default is 2.

Cont.

2-176

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Quality of Service (QoS)

Table 2-34

Quality of Service parameters (Continued) Description Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the downlink Minimum Throughput Budget Requirement (in Kbps) 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. Greyed-out if QoS Feature is not purchased. Read-only if bssgb_pfc_bit is set to On (1). Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in Kbps) ranges from 2-6 for Interactive traffic class, traffic handling priority 2. Greyed-out if QoS Feature is not purchased. Must be less than or equal to the value of qos_mtbr_i1_ul. Greyed-out if QoS Feature is not purchased. Read-only if bssgp_pfc_bit is set to On (1). Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the downlink Minimum Throughput Budget Requirement (in Kbps) ranges from 2-6 for Interactive traffic class, traffic handling priority 3. Greyed-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 - 24. Default is 2. Values

OMC-R GUI field name/BSS parameter name Downlink MTBR for Interactive THP 2 qos_mtbr_i2_dl

Uplink MTBR for Interactive THP 2 qos_mtbr_i2_ul

2 to 6. Default is 2.

Downlink MTBR for Interactive THP 3 qos_mtbr_i3_dl

2 to 6. Default is 2.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-177

Quality of Service (QoS)

Chapter 2: Configuring BSS Features

Table 2-34

Quality of Service parameters (Continued) Description Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in Kbps) ranges from 2-6 for Interactive traffic class, traffic handling priority 3. Greyed-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). Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the downlink Minimum Throughput Budget Requirement (in Kbps) ranges from 2-6 for Best Effort traffic class. Greyed-out if QoS Feature is not purchased. Read-only if bssgp_pfc_bit is set to On (1). Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in Kbps) ranges from 2-6 for Best Effort traffic class. Greyed-out if QoS Feature is not purchased. Read-only if bssgp_pfc_bit is set to On (1). Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the downlink Minimum Throughput Budget Requirement (in Kbps) ranges from 2-6 for Background traffic class. Greyed-out if QoS Feature is not purchased. Read-only if bssgp_pfc_bit is set to On (1). 2 to 6. Default is 2. Values

OMC-R GUI field name/BSS parameter name Uplink MTBR for Interactive THP 3 qos_mtbr_i3_ul

Downlink MTBR for Best Effort Traffic Class qos_mtbr_be_dl

2 to 6. Default is 2.

Uplink MTBR for Best Effort Traffic Class qos_mtbr_be_ul

2 to 6. Default is 2.

Downlink MTBR for Background Traffic Class qos_mtbr_bg_dl

2 to 6. Default is 2.

Cont. 2-178 68P02901W17-R 14 Apr 2006

GMR-01

Installation and Configuration: GSM System Configuration

Quality of Service (QoS)

Table 2-34

Quality of Service parameters (Continued) Description Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in Kbps) ranges from 2-6 for Background traffic class. Greyed-out if QoS Feature is not purchased. Read-only if bssgp_pfc_bit is set to On (1). 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. Greyed-out if GPRS Feature is not purchased. Displayed in the Quality of Service grouping in the PCU Detailed View. Guards the DOWNLOAD-BSS-PFC procedure. Greyed out if the QoS feature (qosOpt) is restricted. Set to read-only if bssgp_pfc_bit is set to 1 (On). Displayed in the Quality of Service grouping in the PCU Detailed View. Guards the MODIFY-BSS-PFC procedure. Greyed out if the QoS feature (qosOpt) is restricted. Set to read-only if bssgp_pfc_bit is set to 1 (On). Displayed in the Quality of Service grouping in the PCU Detailed View. Guards the RA-CAPABILITY-UPDATE procedure. Greyed out if the GPRS feature (gprsOpt) is restricted. 2 to 6. Default is 2. Values

OMC-R GUI field name/BSS parameter name Uplink MTBR for Background Traffic Class qos_mtbr_bg_ul

PAR Waiting Time gprs_par_wait_ind

100 to 750. Default is 150. The unit is Block Periods; one Block Period is 20 ms.

PCU parameters: DOWNLOAD-BSS-PFC Procedure Guard Timer bssgp_t6_timer 100 to 10000. Default is 3000.

MODIFY-BSS-PFC Procedure Guard Timer bssgp_t8_timer

100 to 10000. Default is 3000.

RA-CAPABILITY-UPDATE Procedure Guard Timer bssgp_t5_timer

1000 to 30000. Default is 3000.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-179

Quality of Service (QoS)

Chapter 2: Configuring BSS Features

Table 2-34

Quality of Service parameters (Continued) Description Displayed in the Quality of Service grouping in the PCU Detailed View. Indicates the maximum number of retries for PFC Download. Greyed out if the QoS feature (qosOpt) is restricted. Displayed in the Quality of Service grouping in the PCU Detailed View. Indicates the negotiated value of CBL Bit. Displayed in the Quality of Service grouping in the PCU Detailed View. Indicates the negotiated value of PFC Bit. Values 1 to 3. Default is 3 (tries).

OMC-R GUI field name/BSS parameter name Maximum Number of Retries for PFC Download bssgp_dwnld_retry

Negotiated value of CBL Bit cbl_bit_negotiate

0 or 1. 0 = CBL feature at PCU disabled. 1 = CBL feature at PCU enabled. No default. Read-only. 0 or 1. 0 = QoS feature at PCU disabled. 1 = QoS feature at PCU enabled. No default. Read-only.

Negotiated Value of PFC Bit pfc_bit_negotiate

2-180

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Network Assisted Cell Change (NACC)

Network Assisted Cell Change (NACC)


{22708}

Overview
In systems prior to GSR8, there were performance degradations when the MS performed an autonomous cell reselection. These were caused for the following reasons: Since the MS has limited information about the target cell that it performs cell reselection to, the mobile station might perform a cell reselection to a target cell that is congested or might even select a cell with GPRS/EGPRS service disabled. The MS has to read a consistent set of target cell system information messages before resuming the data transfer on the target cell. This procedure may delay the data transfer resumption depending upon the periodicity of the broadcast system information messages in the network.

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 neighbour cell data to the MS. For a full description of NACC, see Technical Description: BSS Implementation (68P02901W36).

68P02901W17-R 14 Apr 2006

GMR-01

2-181

Network Assisted Cell Change (NACC)

Chapter 2: Configuring BSS Features

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 neighbour 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 neighbour cell is internal or external to the BSS RxLev measurements of the serving and the neighbour cell as reported by the MS QoS capabilities of the serving and neighbour 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/neighbour cell is a macro or a micro cell If the neighbour cell is within the same PCU

Procedure 2: Neighbour cell data


After the target cell has been determined, the network sends the MS a Packet Neighbour Cell Data (PNCD) message containing the information needed for the MS to access the target cell. The neighbour 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.

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 would signal if a cell is congested and will also send a candidate list of mobiles preferable for cell reselection. Cell congestion and PRP congestion will be 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.

2-182

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Network Assisted Cell Change (NACC)

Interaction with other features


{22404} This feature interacts with the IMRM feature, see "Intelligent Multilayer Resource Management (IMRM)" on page 2-161 for further details.

Network Assisted Cell Change (NACC) parameters


Table 2-35 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-35 Network Assisted Cell Change (NACC) parameters Description Values

OMC-R GUI field name/BSS parameter name 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. Displayed in the Network Assisted Cell Change grouping of the BSS Detailed View. Indicates whether Cell Change Notification (CCN) is 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.

0 or 1, where: Restricted (0). Unrestricted (1). It cannot be modified by a user.

Cell Change Notification Enabled nacc_enabled

0 or 1, where: Disabled (0). Enabled (1).

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-183

Network Assisted Cell Change (NACC)

Chapter 2: Configuring BSS Features

Table 2-35

Network Assisted Cell Change (NACC) parameters (Continued) Description 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. Removed by introduction of the QoS feature. Values 0 or 1, where: 0 = GPRS type-5 algorithm is disabled. 1 = GPRS type-5 algorithm is enabled.

OMC-R GUI field name/BSS parameter name GPRS Type 5 Algorithm Enabled gprs_type5_alg

Congestion Threshold gprs_cell_cgt_thr

2-184

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced Multi-level Precedence and Pre-emption (eMLPP)

Enhanced Multi-level Precedence and Pre-emption (eMLPP)


{24347}

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

68P02901W17-R 14 Apr 2006

GMR-01

2-185

Enhanced Multi-level Precedence and Pre-emption (eMLPP)

Chapter 2: Configuring BSS Features

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

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 will follow 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-36 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).

2-186

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Enhanced Multi-level Precedence and Pre-emption (eMLPP)

Table 2-36

Enhanced Multi-level Precedence and Pre-emption (eMLPP) parameters 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. Displayed in the Pre-emption grouping in the BSS Detailed View. Displays the selected pre-emption option. Values 0 or 1, where: Restricted (0). Unrestricted (1).

OMC-R GUI field name/BSS parameter name EMLPP Feature enhancedMLPPOpt

Preemption Options option_preempt (previously called option_emergency_preempt)

0 to 3, or, 0 or 1. If enhancedMLPPOpt is enabled, the range is 0 to 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 to 1, where: ECP Disabled (0) ECP Enabled (1). Default is 0. Cont.

68P02901W17-R 14 Apr 2006

GMR-01

2-187

Enhanced Multi-level Precedence and Pre-emption (eMLPP)

Chapter 2: Configuring BSS Features

Table 2-36

Enhanced Multi-level Precedence and Pre-emption (eMLPP) parameters (Continued) Description 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. Greyed out if enhancedMLPPOpt is disabled. 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. Greyed out if enhancedMLPPOpt is disabled. Values 0 to 14. Default is 0 meaning no calls are exempt (disabled) from certain congestion mechanisms.

OMC-R GUI field name/BSS parameter name Emergency Group Priority emergency_ group_priority

PDTCH Priority sw_pdtch_priority

1 to 14. Default is 14, meaning priority protection is disabled allowing all calls to allocate switchable PDTCH resources.

2-188

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Fast Call Setup

Fast Call Setup


{24620}

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 equalled 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 signalling (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


{22404} This feature interacts with the IMRM feature, see "Intelligent Multilayer Resource Management (IMRM)" on page 2-161 for further details.

Fast Call Setup parameters


Table 2-37 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).

68P02901W17-R 14 Apr 2006

GMR-01

2-189

Fast Call Setup

Chapter 2: Configuring BSS Features

Table 2-37

Fast Call Setup parameters Description Values

OMC-R GUI field name/BSS parameter name 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. 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) will be disabled. This field is greyed-out if the Fast Call Service feature (FastCallOpt) is restricted (Disabled (0)). Deleted by the Fast Call Setup feature.

0 or 1, where: Disabled (0), Enabled (1).

CELL parameters: TCH Usage Threshold tch_usage_ threshold (OMC-R parameter name: tch_usage_thrsld) 0 to 100. Default is 0.

Immediate Assign Mode immediate_assign_mode (OMC-R parameter name: immediateAssMode)

2-190

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

RSL Congestion Control

RSL Congestion Control


{24660/24661}

Overview
The Radio Signalling 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 BSCs 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-38 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).

68P02901W17-R 14 Apr 2006

GMR-01

2-191

RSL Congestion Control

Chapter 2: Configuring BSS Features

Table 2-38

RSL congestion control parameters Description Displayed in the RSL Congestion grouping of the BSS Detailed View. The high threshold to detect RSL congestion on a 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. 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. 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. 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. Values 1 to 100. Default is 60%. If set to 0%, the BSS does not send out XOFF information on RSLLCF.

OMC-R GUI field name/BSS parameter name RSL Congestion Upper Threshold (%) rsl_lcf_congestion_thi

RSL Congestion Lower Threshold (%) rsl_lcf_congestion_tlow

0 to 99. Default is 25%.

Overload Messages Timer Interval (ms) bss_overload_control

1000 to 1000000 (ms). Default is 12500 (ms).

RSL Congestion Alarm Clear Time (ms) rsl_congestion_alarm_timer

1000 to 600000 (ms) Default is 60000 (ms).

Cont.

2-192

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

RSL Congestion Control

Table 2-38

RSL congestion control parameters (Continued) Description 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. 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. Values 0 or 1, where: Disabled (0), Enabled (1). Default is Disabled (0).

OMC-R GUI field name/BSS parameter name Send Overload Messages to MSC msc_bss_overload_allowed (OMC-R parameter name: msc_bss_ovld_alw)

Max Number of Page Messages per Second max_pagenum_per_sec

70 to 65535. Default is 65535.

68P02901W17-R 14 Apr 2006

GMR-01

2-193

VersaTRAU

Chapter 2: Configuring BSS Features

VersaTRAU

{23769}

Overview
The VersaTRAU feature is an extension to the GSM BSS software architecture introduced by the General Packet Radio Service (GPRS) feature 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 optimise 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-21.

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-194

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

VersaTRAU

Permissible values for RTF backhaul timeslots


Table 2-39 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-40). 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-198). Table 2-39 Packet Radio Type field 64 K (3) 64 K (3) 64 K (3) 64 K (3) 64 K (3) Possible values for RFT field: Number of Backhaul Timeslots on Carrier (rtf_ds0_count) EGPRS enabled YES YES YES YES YES VersaTRAU enabled YES YES YES YES NO Half Rate field Disabled Enabled Disabled Enabled N/A 8K TRAU Allowed field N/A YES N/A YES N/A Valid range 3 to 7 3 to 7 3 to 8 3 to 8 7 Sensitivity? Sensitive Sensitive Sensitive Sensitive Insensitive

BCCH YES YES NO NO YES

Default 3 3 3 3 Value of 7 sent from BSS. Value of 8 sent from BSS. Value sent from BSS. Value sent from BSS. Value sent from BSS.

64 K (3)

YES

NO

NO

N/A

N/A

Insensitive

None

N/A

N/A

N/A

N/A

N/A

1 to 8

Greyedout Greyedout Greyedout

16 K (1)

N/A

N/A

N/A

N/A

N/A

1 to 8

32 K (2)

N/A

N/A

N/A

N/A

N/A

1 to 8

VersaTRAU parameters
Table 2-40 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).

68P02901W17-R 14 Apr 2006

GMR-01

2-195

VersaTRAU

Chapter 2: Configuring BSS Features

Table 2-40

VersaTRAU parameters Description Values

OMC-R GUI field name/BSS parameter name 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). 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?

0 or 1, where: Disabled (0). Enabled (1).

RTF parameters: Number of Backhaul Timeslots on Carrier rtf_ds0_count 1 to 8. See Table 2-39 for details of possible values and defaults.

2-196

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Feature Capacity Licensing and Audit

Feature Capacity Licensing and Audit


{24452}

Feature description
The License Audit tool introduced a mechanism to monitor the usage of the carriers across the customer network on a per feature basis. Information is gathered by running scheduled audits against the OMC-R Configuration Management database to produce a report indicating how many RTF(s) are equipped in the database to support each feature. This feature extends the License Audit only functionality to provide license file comparison and customer notification of license overruns. Each software release has a list of features that are monitored for carrier capacity usage. The OMC software triggers the License Audit tool at pre-defined intervals, which can be configured by the customer. The License Audit tool will be extended on each release to incorporate new features in the audit functions. For each customer, a license file is issued which contains the information on current licensed capacity for every licensable feature. A single license key is provided to control this information per network. The License Audit Tool is distributed with the OMC software, and installed and configured by the user. The audit is triggered by a configurable interval parameter in the OMC software. If the interval parameter is not set, or set outside the permissible range [2 hours, 48 hours], the default value of 12 hours is used. The result of the audit (actual usage) is compared with the license file per feature. An alarm is generated when the carrier usage for one or more features exceeds the carriers purchased for those features. If the usage is within the limit, the License Audit Tool generates an event which indicates that the carrier usage is within the license 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-R 14 Apr 2006

GMR-01

2-197

Improved Timeslot Sharing

Chapter 2: Configuring BSS Features

Improved Timeslot Sharing


{28075}

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 unrestircted (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 {23769} Enhanced Multi-level Precedence and Pre-emption (eMLPP) {24347}

The ITS feature requires the EGPRS and VersaTRAU features to be unrestricted.

ITS parameters
Table 2-41 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.

2-198

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Improved Timeslot Sharing

Table 2-41

ITS parameters Description Values

OMC-R GUI field name/BSS parameter name Improved Timeslot Sharing Feature itsOpt

Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether ITS is unrestricted (enabled) or restricted (disabled). Displayed in the Improved Timeslot Sharing group of the BSS Detailed View.

0 or 1, where: Disabled (0). Enabled (1).

Improved Timeslot Sharing Enabled improve_ts_enabled (OMC-R parameter name: its_enabled)

0 or 1, where: Disabled (0). Enabled (1).

68P02901W17-R 14 Apr 2006

GMR-01

2-199

Improved Timeslot Sharing

Chapter 2: Configuring BSS Features

This page intentionally left blank.

2-200

GMR-01

68P02901W17-R 14 Apr 2006

Chapter

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-R 14 Apr 2006

GMR-01

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

Creating a new Network instance using the OMC-R GUI


To create a new Network instance to the OMC-R Navigation Tree, use the following procedure:

3-2

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a network instance

Procedure 3-1 1 2

Create Network instance using OMC-R GUI

From the Front Panel, click on the Config Mgt icon to display the Navigation Tree. Select Edit - Create Network from the menu bar to open a new Network Detailed View.

If a Network instance has already been created, the Create Network menu option is not displayed. 3 4 Complete the fields as required. See "Network Detailed View fields" on page 3-3 for details. 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.

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 6 7 8 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.

68P02901W17-R 14 Apr 2006

GMR-01

3-3

Configuring a network instance

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

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

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 Brief description Unique Network name. The MCC for the network. The MNC for the network. Whether or not the OMC-R initiates a Resync of the Network on system start-up. The object class identifier. 3 digits. 2 or 3 digits. Yes (1) or No (0). Default is 1. Default is Network. Values Mandatory or Optional? Mandatory. Mandatory. Mandatory. Optional.

Field name Name Mobile Country Code Mobile Network Code Resync on Startup

RDN Class

Optional. Cont.

3-4

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a network instance

Table 3-1

Network Detailed View fields - Identification grouping (Continued) Brief description The instance identifier of the object. Together with the rdnClass, it makes up the Relative Distinguished Name (RDN) of an object. {24636} 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, Neighbour, 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. The OMC-R supports an interface to a Network Management Centre (NMC). This is the instance identifier of the object on the NMC interface. Values Default is 0. Mandatory or Optional? Mandatory.

Field name RDN Instance

NMC Value

Optional.

68P02901W17-R 14 Apr 2006

GMR-01

3-5

Configuring a network instance

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

Additional Information
Use the Additional Information window to input any notes relating to this Network. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

State grouping
{22904} Table 3-2 Network Detailed View fields - State grouping Field name Brief description Values Date and Time (ddmmyy hhmm). Date and Time (ddmmyy hhmm). Mandatory or Optional? Read only.

Time of Last Audit Gather Shows the last time the Gather Complete phase of a network Audit was timeOfLastAuGatherComplete completed. Time of Last Audit Apply Complete timeOfLastAuApplyComplete Shows the last time the Apply phase of a network Audit was completed.

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 Brief description 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 Networks default map. In edit mode, click on button to display the Map Network Detailed View, which shows the Map Background setting. Values Mandatory or Optional? Optional.

Field name Default Map

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 will be refused. To delete a Network instance, see "Deleting a network object using the OMC-R GUI" on page 1-44.

3-6

GMR-01

68P02901W17-R 14 Apr 2006

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

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 a new OMC-R or MSC instance, use the following procedure: Procedure 3-2 1 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-35 for further details. The network object class button changes colour. 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-8 for further details. Save and close the Detailed View as detailed in "Creating a network object using the OMC-R GUI" on page 1-39.

2 3 4

68P02901W17-R 14 Apr 2006

GMR-01

3-7

Configuring an OMC-R or MSC instance

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

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.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

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.

3-8

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an OMC-R or MSC instance

Table 3-4

OMC and MSC Detailed View fields - Identification grouping Brief description Unique OMC or MSC name. 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 will be 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. Name of the UNIX host machine. Mainly used to support the ProxyCell synchronization feature for inter-OMC ProxyCell updates. See description in Table 3-1. See description in Table 3-1. No (0) and Yes (1). Default is No (0) Values Mandatory or Optional? Mandatory. Optional.

Field name Name Active (OMC only)

Host name (OMC only)

0 to 24

Mandatory.

RDN Class RDN Instance

Default is OMC or MSC OMC is 0 to 50. MSC is 0 to 100. Default is 0.

Optional. Optional.

NMC RDN Value Parent Detail View

See description in Table 3-1. Displays the name of the parent. Click to display the parent Network Detailed View.

Optional. Not applicable.

Additional Information
Use the Additional Information window to input any notes relating to this OMC or MSC. Where additional notes are not required, it is advisable to close this field by clicking on 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.

68P02901W17-R 14 Apr 2006

GMR-01

3-9

Configuring an OMC-R or MSC instance

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

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

3-10

GMR-01

68P02901W17-R 14 Apr 2006

Chapter

Configuring a BSS/RXCDR

The procedures to be followed in order 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-7. "Creating an RXCDR using the OMC-R GUI" on page 4-43. "Configuring the packet switch/MUX for a BSS" on page 4-45. "MSC to BSS overload control" on page 2-24. "Deleting a BSS/RXCDR" on page 4-50. "Deleting a BSS/RXCDR at the packet switch/MUX" on page 4-54. "Equipping cabinets and cages at a BSS site" on page 4-57. "Configuring an RXCDR cabinet" on page 4-68. "Configuring an Assoc_BSS" on page 4-75. "Configuring an Assoc_RXCDR" on page 4-79. "Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR" on page 4-88. "Configuring DYNETs and DYNETGroups" on page 4-99. "Configuring a DYNETGroup" on page 4-102. "Configuring a DYNET" on page 4-104. "Reparenting a BSS" on page 4-110. "Reparenting an RXCDR to a different MSC" on page 4-117.

68P02901W17-R 14 Apr 2006

GMR-01

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-21. 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: 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 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 the NE database object is available to be loaded and activated once the BSS has been created. Ensure the database version matches the required software load version. Refer to OMC-R Online Help, Network Operations.

4-2

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Overview of adding a BSS or RXCDR

Overview procedure for adding BSS/RXCDR to the network


To add a BSS/RXCDR to the network, follow this overall procedure: Procedure 4-1 1 Add BSS/RXCDR to the network

Create the new BSS or RXCDR. Refer to "Creating a BSS using the OMC-R GUI" on page 4-7 and "Creating an RXCDR using the OMC-R GUI" on page 4-43. 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 to see if this brings the OML into service. If this works, the alarm will clear and the BSS will begin sending events and statistics files to the OMC-R. If the alarm has not cleared, configure the packet switch/MUX. Refer to "Configuring the packet switch/MUX for a BSS" on page 4-45. The red X.25 link failure alarm will clear, 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-46. If the BSS name appears, and the rlogin is successful, then NE.MAP has been configured properly.

68P02901W17-R 14 Apr 2006

GMR-01

4-3

Overview of adding a BSS or RXCDR

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 1 Perform an audit for the BSS/RXCDR

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 will not communicate properly with the MSC. Use the BSS Detailed View Signalling Information grouping to check. Verify all SITEs and cells have been audited properly.

4-4

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Overview of adding a BSS or RXCDR

Verifying information
Next the BSS/RXCDR settings should be verified. To do this follow these steps: Procedure 4-3 1 Verify RSS.RXCDR settings

Verify that the Statistics collection interval matches that set for the OMC-R, using the BSS Detailed View General grouping to check BSS setting.

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 3 If required, change the SITE names. Refer to "Reparenting a BSS" on page 4-110. Verify that all SITEs under the BSC have come into service, using the TTY command: state 0 site * *

Some sites may be dummy sites, and may be D-U or D-L. 4 Verify the raw statistics files are being uploaded for the BSS, using the Event window to monitor for filexransferCompletedEvents. Refer to OMC-R Online Help, Network Operations for further details. Verify the PM reports are available for the BSS. Refer to OMC-R Online Help, Network Operations for further details. If required, edit the appropriate subscription lists to add the new BSS to them. Refer to OMC-R Online Help, Network Operations for further details.

5 6

Configuring connectivity
The next stage is to configure connectivity. To do this, 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.

68P02901W17-R 14 Apr 2006

GMR-01

4-5

Overview of adding a BSS or RXCDR

Chapter 4: Configuring a BSS/RXCDR

Checking the maps


Now the maps should be checked. To do this, follow these steps: Procedure 4-4 1 Check maps

If using the Map feature, when a new BSS/RXCDR is added, a new default map is created for the BSS/RXCDR. The NEs will not be correctly 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-12 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. To do this, Store the following updated MIB data in backup files: BSS object. NE Software object. SITE names. All Map data. Updated RXCDR connectivity information.

4-6

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

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.

A BSS that supports the GPRS feature can only be created if the gprsOpt parameter is unrestricted.

Creating a BSS using the OMC-R GUI


To create a BSS using the OMC-R GUI, use the following procedure:

68P02901W17-R 14 Apr 2006

GMR-01

4-7

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Procedure 4-5 1

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-35 for further details. The BSS class button changes colour. From the menu bar, select Edit - Create. The OMC-R displays the initial BSS Detailed View in Create mode, see Figure 4-1. Click on the Initial Software Load button to display a Software Inventory Dialog window. Double-click on one of the software loads displayed to select it and enter it in the initial BSS Detailed View. 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. Select File - Close from the menu bar to close the Detailed View.

2 3 4 5 6 7 8

Figure 4-1

Initial BSS Detailed View in Create mode

4-8

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

BSS Detailed View fields


The following sections list and briefly describe the parameter fields in the BSS Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

68P02901W17-R 14 Apr 2006

GMR-01

4-9

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

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 Brief description Unique BSS name. The object class identifier. Automatically set to the next available network element identifier. See "Dynamic Allocation of RXCDR-BSC Circuits (DARBC)" on page 2-14 for details. The OMC-R supports an interface to a Network Management Centre (NMC). This is the instance identifier of the object on the NMC interface. Click to display the parent Network Detailed View. Version number of the software load active in the Network Element. Date and time at which the current NE load was created. Initial Software Load installed when NE was created. 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. The BSC configuration type. This attribute has no function at an RXCDR. Yes (1) or No (0). Default is Yes (1). 4 to 11 digits. Default is BSS. {23370} 1 to 254 Values Mandatory or Optional? Mandatory. Optional. Mandatory.

Field name/BSS parameter name Name RDN Class Network Entity Id

NMC RDN Value

4 to 11 digits.

Optional.

Parent Detailed View OMC/NE Load Version OMC/NE Load Version Create Time Initial Software Load Local Maintenance local_maintenance

Not applicable. Mandatory. Mandatory. Mandatory. Mandatory.

BSC Configuration Type bsc_type

1 to 3. 1 = Non-Abis, Type 1. 2 = Non-Abis, Type 2 3 = Abis, Type 0. Default is Non-Abis, Type 0 (0) Local (1) or Remote (0). Default is 0.

Mandatory.

Transcoding local_transcoding

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-14 for details.

Mandatory.

4-10

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Additional information
Use the Additional Information window to input any notes relating to this BSS. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

State grouping
The state parameter fields are updated by the OMC-R only, and show 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.

68P02901W17-R 14 Apr 2006

GMR-01

4-11

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-2

BSS Detailed View fields - State grouping Field name Brief description The operational state of the NE. Values 0 to 3. UNDEFINED (0), DISABLED (1), ENABLED (2), BUSY (3). Mandatory or Optional? Optional.

Operational State

Administration State

The administration state of the NE.

0 to 5. UNDEFINED (0), NOT EQUIPPED (1), EQUIPPED (2), LOCKED (3), UNLOCKED (4), SHUTTINGDOWN (5). 0 to 65535.

Optional.

Reason Code Time of Last Transition

The reason code why the state changed. The time of the last state transition.

Optional. Mandatory.

{22904} Time of Last Audit The date and time when the Gather Complete Audit (Gather phase) of the timeOfLastAuGatherComplete device was last performed. {22904} Time of Last Audit Apply Complete timeOfLastAuApplyComplete 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. The identifiers of any related devices. The date and time when the audit (apply phase) of the device was last performed.

Date and time - in the format ddmmyy hh:mm. Date and Time - in the format ddmmyy hh:mm

Read-only.

Read-only.

Mandatory.

Related Device (not shown in BSS Detailed View)

Optional.

4-12

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

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 Brief description 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-18 file. The OMC-Rs first and second Event Virtual Circuit X.121 address stored in the Network Elements 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. The OMC-Rs first and second Download Virtual Circuit X.121 address stored in the Network Elements Non Volatile RAM. The OMC-Rs Remote Login Virtual Circuit X.121 address stored in the Network Elements Non Volatile RAM. The OMCs Upload Virtual Circuit X.121 address stored in the Network Elements Non Volatile RAM. The OMC-Rs Spare Virtual Circuit X.121 address stored in the Network Elements Non Volatile RAM. Cell Broadcast Center (CBC) X.121 address. X.121 address at the BSC used to communicate with the Cell Broadcast Center (CBC). Values 1 to 14 characters Mandatory or Optional? Mandatory.

Field name/BSS parameter name Network Element X.121 Address

OMC X.121 Event Address 1 OMC X.121 Event Address 2

1 to 14 characters

Mandatory.

OMC X.121 Download Address 1 OMC X.121 Download Address 2 OMC X.121 Remote Login Address

0 to 14 characters

Mandatory.

0 to 14 characters

Mandatory.

OMC X.121 Upload Address

0 to 14 characters

Mandatory.

OMC X.121 Spare Address (two fields)

0 to 14 characters

Mandatory.

CBC X.121 Address BSC CBC X.121 Address bsc_cbc

0 to 14 characters 0 to 14 characters

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

68P02901W17-R 14 Apr 2006

GMR-01

4-13

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-4

BSS Detailed View fields - Optional Features grouping Brief description See "Frequency hopping" on page 2-3 for details. Affects the ability of the system to process a request to configure Concentric Cells. See "Preventive Cyclic Retransmission (PCR)" on page 2-59 for details. If disabled, the BSS parameters pcr_enable, pcr_n1, pcr_n2 cannot be used. If this feature is restricted, the creation of non-spoke PATH instance is not allowed. If this feature is unrestricted (enabled), the DRI diversity_flag can be used (see Table 9-17). If this feature is unrestricted (enabled), the CELL parameter egsm_ho_thresh can be used (see Table 8-18). If this feature is unrestricted (enabled), the CELL parameter ext_range_cell can be used (see Table 8-2). Whether the A and Um Interface feature is restricted. See System Information: Overview (68P02901W01) for a description of this feature. Also see Table 4-7 for related BSS parameters. See "GSM Half Rate" on page 2-149 for details. Whether the Heterogeneous Cabinet Feature is restricted. Cannot be enabled without homoCabFreqType also being enabled. Whether the Homogeneous Cabinet Frequency Type is restricted. See "Configuring enhanced SDCCH to TCH band assignment" on page 8-212 and "Configuring a cell for coincident multiband handovers" on page 8-194 for details. Also see Table 8-10 CELL Detailed View Congestion Relief parameter grouping. Whether the Microcell feature is restricted. See Table 8-28, Table 8-47 and Table 8-48 for associated parameters. Whether the Multiple Encryption feature is restricted. See Table 4-6 for related parameters. Also see "Encryption algorithms" on page 2-27 and Technical Description: BSS Implementation (68P02901W36) for details of this feature. Cont.

Field name/OMC-R parameter name Frequency Hopping Baseband Feature basebandHopOpt Concentric Cells Feature concentricCellOpt Preventative Cyclic Retransmission Feature cycRetranPrevOpt

Daisy Chaining Feature daisyChainOpt Receiver Spatial Diversity Feature diversityOpt Extended GSM 900 Feature egsmOpt Extended Range Cell Feature ercOpt A and Um Interface - GSM Phase 2 Feature gsmPhase2Opt

GSM Half Rate gsmHalfRateOpt Heterogeneous Cabinet Feature heteroCabFreqOpt Homogeneous Cabinet Feature homoCabFreqOpt MultiBand Inter-Cell H/O Feature mbInterCellHoOpt

MicroCell Feature microcellOpt Multiple Encryption Feature multiEncryptOpt

4-14

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Table 4-4

BSS Detailed View fields - Optional Features grouping (Continued) Brief description Whether the Add Nail Connections feature is restricted. See Technical Description: BSS Implementation (68P02901W36) for details of this feature. Whether the Reserved Timeslot feature is restricted. See Technical Description: BSS Implementation (68P02901W36) for details of this feature. Whether the Sub-equipped RTF feature is restricted. See Technical Description: BSS Implementation (68P02901W36) for details of this feature. Whether the RTF PATH Fault Containment feature is restricted. See Technical Description: BSS Implementation (68P02901W36) for details of this feature. Whether the 16 Kbps LAPD RSL RTF feature is restricted. See Technical Description: BSS Implementation (68P02901W36) for details of this feature. Whether the Alternative Congestion Relief feature is restricted. See Table 8-10 and Table 8-49 for details of the Cell and Neighbour Detailed View fields associated with this feature. Also see System Information: Overview (68P02901W01) for a description of this feature. Whether the Directed Retry feature is restricted. See Table 4-11, Table 8-11 and Table 8-49 for details of the BSS, cell, and neighbour parameters associated with this feature. Also see Technical Description: BSS Implementation (68P02901W36) for details of this feature. See "Short Message Service - Cell Broadcast" on page 2-46 for details. See "Short Message Service - Point-To-Point" on page 2-55 for details. See "Frequency hopping" on page 2-3 for details. Whether the SMS Service Centre feature is restricted. Affects the ability of the system to process a request to equip/create a CBL. Cont.

Field name/OMC-R parameter name Add Nail Connections Feature nailConnectsOpt

Reserved Timeslot Feature resTimeslotOpt Sub-equipped RTF Feature rtf_capacityOpt RTF PATH Fault Containment Feature RTFPathEnableOpt

16 Kbps LAPD RSL Feature rsl_rateOpt

Alternative Congestion Relief Feature congestReliefOpt

Directed Retry Feature directedRetryOpt

SMS Cell Broadcast Feature smsCellBroadOpt SMS Point to Point Feature smsPntToPntOpt Frequency Hopping Synthesizer Feature synthHoppingOpt SMS Service Centre Feature smsServCenterOpt

68P02901W17-R 14 Apr 2006

GMR-01

4-15

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-4

BSS Detailed View fields - Optional Features grouping (Continued) Brief description 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. 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. 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: Overview (68P02901W01) for a description of this feature. Whether EGPRS feature is restricted. See "GPRS and EGPRS coding schemes" on page 2-40 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: Overview (68P02901W01) for a description of this feature. See "Dual band cells option" on page 2-29 for details. Whether the HorizonMicro/HorizonCompact feature is restricted. See "Enhanced Circuit Error Rate Monitor (ECERM)" on page 2-73 for details. See "Advanced Load Management for EGSM" on page 2-82 for details. See "Network Controlled Cell Reselection" on page 2-85 for details. See "GPRS and EGPRS coding schemes" on page 2-40 for details. See "Enhanced BSC Capacity" on page 2-99 for details. See "Enhanced GPRS One Phase Access " on page 2-120 for details. Cont.

Field name/OMC-R parameter name Aggregate Abis Feature aggAbisOpt

Integrated M-Cell HDSL Feature hdslOpt

GPRS Feature gprsOpt

EGPRS Feature egprsOpt

Dual Band Cells Option dualBandCellOpt HorizonMicro/HorizonCompact Feature HorizonMicCom2Opt ECERM Feature ecermOpt ALM Enhancement for EGSM Carriers AlmEgsmOpt Network Controlled Cell Reselection Feature nccrOpt Coding Scheme 3 and 4 cs34Opt Enhanced BSC Feature ebscOpt Enhanced One Phase Access Feature eopOpt

4-16

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Table 4-4

BSS Detailed View fields - Optional Features grouping (Continued) Brief description See "Inter-Radio Access Technology (Inter-RAT) Handover" on page 2-100 for details. {22879} Whenever EnhncdInterRatOpt is set to 1, InterRatOpt also will be set to 1. Whether the XBL 16 Kbps LAPD feature is restricted. See Table 9-68 for details of the XBL parameters associated with this feature. Whether the Level 3 Password feature is restricted. See Technical Description: BSS Implementation (68P02901W36) for details of this feature. See "PBCCH/PCCCH feature" on page 2-124 for details. 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. 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. Whether the Fast GCLK Warm Up feature is restricted. Determines whether the site parameter gclk_qwarm_flag can be used (see Table 7-5). See "GSM location services" on page 2-109 for details. Whether or not the GPRS Trace feature is enabled or disabled. See OMC-R Online Help, Network Operations for details of this feature. See "Adaptive Multi-Rate (AMR)" on page 2-138 for details. See "Adaptive Multi-Rate (AMR)" on page 2-138 for details. Greyed-out if the AMR Feature (amrOpt) is restricted (Disabled). See "Adaptive Multi-Rate (AMR)" on page 2-138 for details. See "Adaptive Multi-Rate (AMR)" on page 2-138 for details. See "Adaptive Multi-Rate (AMR)" on page 2-138 for details. Cont.

Field name/OMC-R parameter name Inter-RAT Handover Feature InterRatOpt

XBL 16 Kbps LAPD Feature xbl_rateOpt Level 3 Password Feature level3PassOpt PBCCH/PCCCH Feature Enhanced Full Rate Feature EFROpt

GDP Volume Control Feature gdpVolContOpt

Fast GCLK Warm Up Feature FastWarmGclkOpt Location Services Feature lcsOpt {22407} GPRS Trace Feature gprsTraceOpt AMR Feature amrOpt AMR Enhanced GDP Feature amrEGDPProOpt AMR Enhanced Capacity Feature amrEnhancedCapOpt AMR TCU-A Feature amrTCUAOpt AMR TCU-B Feature amrTCUBOpt

68P02901W17-R 14 Apr 2006

GMR-01

4-17

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-4

BSS Detailed View fields - Optional Features grouping (Continued) Brief description See "GPRS Seamless Cell Reselection" on page 2-151 for details. See "Enhanced Scheduling" on page 2-156 for details. This feature can only be enabled if GPRS is enabled. Whether the Intelligent Multilayer Resource Management feature is restricted. See "Intelligent Multilayer Resource Management (IMRM)" on page 2-161 for further details. Whether the Fast Call Service feature is restricted or unrestricted. See "Fast Call Setup" on page 2-189 for further details. Where the Enhanced Inter RAT Handover feature has been restricted. Whenever EnhncdInterRatOpt is set to 1, InterRatOpt also will be set to 1. See "Enhanced Inter-RAT Handover feature" on page 2-101 for further details. Whether the Network Assisted Cell Change feature is restricted (disabled) or unrestricted (enabled). See "Network Assisted Cell Change (NACC)" on page 2-181 for further details. 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-185 for further details. Whether or not Quality of Service feature is restricted or unrestricted. See "Quality of Service (QoS)" on page 2-171 for further details. Displays whether the VersaTRAU feature is restricted (Disabled (0)) or unrestricted (Enabled (1)). See "VersaTRAU" on page 2-194 for further details. Displays whether the Improved Timeslot Sharing Feature is restricted (Disabled (0)) or unrestricted (Enabled (1)).

Field name/OMC-R parameter name GPRS Seamless Cell Reselection Feature scrOpt Increased PRP Capacity Feature Supported prp_capacity_opt {22404} Intelligent Multilayer Feature imrmOpt

{24620} Fast Call Service Feature FastCallOpt {22879} Enhanced Inter RAT Handover Feature EnhancedInterRatOpt

{22708} Network Assisted Cell Change Feature naccOpt

{24347} EMLPP Feature enhancedMLPPOpt

{23956} Quality of Service qosOpt {23769} VersaTRAU Feature versaTrauOpt

{28075}Improved Timeslot Sharing Feature itsOpt

4-18

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Signalling Information grouping


Table 4-5 describes the fields in the Signalling Information grouping of the BSS Detailed View. Table 4-5 BSS Detailed View fields - Signalling Information grouping Brief description Establishes a method of differentiation between international and national messages. Values 0 to 3. International Network (0), Spare (for international use only) (1), National Network (2), Reserved for national use (3). Default is 2. 0 to 16777215. 0 to 16777215, if ss7_mode is ANSI SS7. 0 to 16383, if ss7_mode is not ANSI SS7. 0 to 16777215. 0 to 16777215, if ss7_mode is ANSI SS7. 0 to 16383, if ss7_mode is not ANSI SS7. Whether or not point code is included (enabled) in called party (call receiver) address in the SCCP messages. Whether or not point code is included in calling party (call originator) address in the SCCP messages. Whether or not calling party address is included in the SCCP message Connection Request. Disabled (0) or Enabled (1). Mandatory or Optional? Mandatory.

Field name/BSS parameter name Network Indicator Code

Originating Point Code

Mandatory.

Destination Point Code

Mandatory.

Called Point Code Included

Mandatory.

Calling PCI

Disabled (0) or Enabled (1).

Mandatory.

Connection Request Calling

Disabled (0) or Enabled (1). Default is 0.

Mandatory.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

4-19

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-5

BSS Detailed View fields - Signalling Information grouping (Continued) Brief description 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-59 for further details. See "Preventive Cyclic Retransmission (PCR)" on page 2-59 for further details. See "Preventive Cyclic Retransmission (PCR)" on page 2-59 for further details. When enabled, detects Signalling 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. Indicates which SS7 definition is supported. Disabled (0) or Enabled (1). Default is 0. Values Disabled (0) or Enabled (1). Default is 0. Mandatory or Optional? Mandatory.

Field name/BSS parameter name Preventative Cyclic Retransmission Enable pcr_enable

Preventative Cyclic Retransmission N1 pcr_n1 Preventative Cyclic Retransmission N2 pcr_n2 SCCP BSSAP Management Flag

Mandatory.

Mandatory.

Mandatory.

SS7 Mode ss7_mode

SS7 defined by CCITT (0) or SS7 defined by ANSI (1). Default is 0. 0 to 255. Defaults to 254. Disabled (0) or Enabled (1). Default is 0. 0 to 16777215.0 to 16777215 if ss7_mode is ANSI SS7.0 to 16383 if ss7_mode is not ANSI SS7.

Mandatory.

BSSAP Subsystem Number STP PC stp_pc_enabled STP Point Code stp_pc

The BSS AP subsystem number. Used for enabling the stp_pc.

Mandatory. Mandatory.

The STP (signalling transfer point) point code. This point code should be used by MTPL3 and not by SCCP. Only used when stp_pc_enabled is 1.

Mandatory.

A5 Algorithms grouping
Table 4-6 describes the fields in the A5 Algorithms grouping of the BSS Detailed View.

4-20

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Table 4-6

BSS Detailed View fields - A5 Algorithms grouping Brief description The A5 encryption algorithm with priority 1 (highest) to be used by the BSS. As above but for Priority 2 to 7. No encryption algorithm associated. These fields enable or disable encryption algorithm A5/1 to 7. multiEncryptOpt must be enabled. Values 0 to 7. Default is 0 (No Encryption). 0 to 7. Default is null. 0 or null. Default is null. Disabled (0) or Enabled (1). Default is Disabled (0). Mandatory or Optional? Mandatory.

Field name/BSS parameter name A5 Algorithm Priority 1

A5 Algorithm Priority 2 -7 A5 Algorithm Priority 8 Encryption Algorithm A5/1 to 7 Allowed option_alg_a5_1 to 7

Optional. Optional. 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 Brief description The layer 1 mode of the land network TELCO connection type. 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. Whether downlink Voice Activity Detection/Discontinuous Transmission (VAD/DTX) is enabled. Identifies a generated tone which is transmitted over a traffic channel when a voice is not being transmitted. The time in minutes in which the statistics file should be reported. Values CEPT (E1) (0) or T1 (1). Default is 0. Disabled (0) or Enable (1). Default is 0. Mandatory or Optional? Mandatory.

Field name/BSS parameter name Land Layer 1 Mode

MMS Critical Alarm Threshold Enable

Mandatory.

XCDR Downlink VAD/DTX Enable

Disabled (1) or VAD/DTX Enable (0). Default is 0. 0 to 255 (Number identifying the tone). Default is 0 5 to 60 (in minutes). Default is 30

Optional.

XCDR MSC Quiet Tone

Mandatory.

Statistics Interval

Mandatory.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

4-21

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-7

BSS Detailed View fields - General grouping (Continued) Brief description Used to negotiate the Packet Size in the X.25 Call Request Packet. Used to negotiate the Window Size in the X.25 Call Request Packet. An identifier to describe a circuit that will never be used. It is used as an internal placeholder in call processing to show that no circuit has been assigned to a call. Whether or not 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. Whether or not 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. Whether or not the Reset Circuit message is sent to the MSC. Whether or not 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. The audio downlink volume control. Affects background and comfort noise, not data. Values 128, 256 or 512. Default is 128 2 to 7. Default 2. 0 to 65535. Default is 0. Mandatory or Optional? Mandatory. Mandatory.

Field name/BSS parameter name OML X.25 Layer 3 Packet Size OML X.25 Layer 3 Window Size Illegal Circuit ID

Mandatory.

Cipher Mode Reject Message Allowed ciph_mode_rej_allowed (OMC-R parameter name: ciphModeRejAllwd)

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)

Disabled (0) or Enable (1). Default is 0.

Mandatory.

Reset Circuit Message Flag Radio Resource Status Flag

Message not sent (0), or Message sent (1). Default is 0. Disabled (0) or Enabled (1). Default is 0.

Mandatory.

Mandatory.

Downlink Audio Level Offset dl_audio_lev_offset (OMC-R parameter name: dlAudioLevOff)

-15 to 15 (in dB) Default is 0.

Mandatory.

Cont.

4-22

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Table 4-7

BSS Detailed View fields - General grouping (Continued) Brief description The audio uplink volume control. Affects background and comfort noise, not data. Values -15 to 15 (in dB) Default is 0. Mandatory or Optional? Mandatory.

Field name/BSS parameter name Uplink Audio Level Offset ul_audio_lev_offset (OMC-R parameter name: ulAudioLevOff) 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. 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. The format of the GSM cell id sent by the BSS to the MSC.

0 - 255 (number of repetitions) Default is 0.

Mandatory.

Group Block Unblock Allowed group_block _unblock_allowed (OMC-R parameter name: grpBlkUnblkAllwd)

Disabled (0) or Enable (1). Default is 0.

Mandatory.

GSM Cell ID Format gsm_cell_id_format (OMC-R parameter name: gsm_cell_id_fmt) Max Reset Circuit Timer Expirations

0 to 2. Whole CGI (0), (LAC) and CI (1), or CI (2). Default is 1. 0 to 100 (number of repeats). Default is 1. Formatted for Phase 1 (0), Formatted for Phase 2 (1), Formatted for Phase 2 with MultiBand (2) Default is 0.

Mandatory.

Number of times the reset circuit message is repeated if an acknowledgement is not received from the MSC. The format of the classmark parameter sent to the MSC based on GSM phases.

Mandatory.

Phase 2 Classmark Allowed

Mandatory.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

4-23

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-7

BSS Detailed View fields - General grouping (Continued) Brief description The format used to send Resource Indication messages to the MSC. Only used if the BSS optional feature gsmPhase2Opt is unrestricted. Values GSM Phase 1 format (0) or GSM Phase 2 format (1). Default is 0. Mandatory or Optional? Mandatory.

Field name/BSS parameter name Phase Resource Indication phase2_resource_ind_ allowed (OMC-R parameter name: phase2ResIndAllwd) 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). 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 will be barred. The delay between bursts of messages sent from the Site Statistics Process (SSP) to the Central Statistics Process (CSP). Number of messages Site Statistics Process (SSP) can forward to Central Statistics Process (CSP) in one burst. 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 to 100 (Percentage of Call Information Blocks in Use). Default is 80. 0 to 100. Default is 70.

Mandatory.

SSM Normal Overload Threshold

Mandatory.

Site Statistics Process Burst Delay

0 to 2500 (in milliseconds). Default is 200. 1 to 65535 (number of messages). Default is 10. 0 to 2. Send alarm to OMC (0), Send message to MSC (1), Send alarm to OMC and message to MSC (2). Default is 0.

Mandatory.

Site Statistics Process Burst Limit

Mandatory.

Unequipped Circuit Allowed unequipped_circuit_ allowed (OMC-R parameter name: uneqCctAlld)

Mandatory.

Cont.

4-24

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Table 4-7

BSS Detailed View fields - General grouping (Continued) Brief description 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. Values 0 - No space 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. Send (0) or Do not send (1). Default is 0. Mandatory or Optional? Mandatory.

Field name/BSS parameter name Call Traces Options

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. Determines if the optional element current channel is included in the Handover Required message to the MSC. Used to negotiate the Packet Size in the X.25 Call Request Packet. Used to negotiate the Window Size in the X.25 Call Request Packet. Whether the functionality for the RTF PATH Fault Containment Feature is enabled or disabled. 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. Determines the values that can be used for the Cabinet frequency_type and the CELL frequency_type. Cannot be changed if the GDP Volume Control feature (gdpVolContOpt) is restricted (disabled).

Mandatory.

Current Channel in HO Required Msg

Disabled (0) or Enabled (1). Default is 0. 128, 256 or 512. Default is 128. 2 to 7. Default is 2 Disabled (0) or Enabled (1). Default is 0. Reject message not required (0), Reject message required (1) Default is 1. 1 to 15. Default is PGSM900 (1). CCDSP Volume Control (0), GDP Volume Control (1). Default is 0.

Mandatory.

CBL X.25 Layer 3 Packet Size CBL X.25 Layer 3 Window Size RTF PATH Fault Containment Status Handover Reject Message Required

Mandatory. Mandatory.

Optional.

Mandatory.

Frequency Types Allowed

Mandatory.

Uplink and Downlink Volume Control Type volume_control_type (OMC-R parameter name: volContType)

Mandatory.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

4-25

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-7

BSS Detailed View fields - General grouping (Continued) Brief description See "Advanced Load Management for EGSM" on page 2-82 for details. 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. 0 to 8. Default is 5. Values Mandatory or Optional? Optional.

Field name/BSS parameter name BSS EGSM ALM Allowed egsm_alm_allowed MMI Cell ID Format

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. 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. Whether Second Assignment Procedure has been enabled at the BSS. See "MSC to BSS overload control" on page 2-24 for further details. See "Propagating TSC updates" on page 8-238 for further details. The preemption level for the pool GPROC functions.

Mandatory.

Call Trace Msgs After Handover

0 to 8. Default is 5.

Mandatory.

Second Assignment Procedure

Enabled (1) or Disabled (0). Default is Disabled (0). Enabled (1) or Disabled (0). Default is Disabled (0). Default is 0. 0 to 2. No replacement (0), Based on Function Priority (1), Based on Function and Intra-function priorities (2). Default is 1.

Optional.

MSC Overload Control bss_msc_overload_ allowed Update TSCs tsc_update_method Pool GPROC Preemption

Optional.

Optional. Optional.

Cont.

4-26

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Table 4-7

BSS Detailed View fields - General grouping (Continued) Brief description Whether the MTPL3 signalling link test is enabled when the MTL comes in service. Enables or disables the SCCP Inactivity Control. See "Modifying MTL loadsharing granularity" on page 9-165 for details. 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 will 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. See "Modifying LMTL loadsharing granularity" on page 9-142 for details. 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. 0 or 1 where: 0 = No 1 = Yes. Default is No (0). Values Allowed (1) or Disallowed (0). Default is Allowed (1). Enabled (1) or Disabled (0). Default is Enabled (1). Mandatory or Optional? Mandatory.

Field name/BSS parameter name MTPL3 Signalling Link Test

SCCP Inactivity Control

Mandatory.

MTL Loadshare Granularity mtl_loadshare_ granularity {22076} Terminate RF when Cell goes OOS stop_dri_tx_enable

Optional.

Mandatory.

LMTL Loadshare Granularity lmtl_loadshare_ granularity MSC Release

Optional.

Optional.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

4-27

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-7

BSS Detailed View fields - General grouping (Continued) Brief description 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). Indicates the length of time in which the frequency of interzone ping-pong handovers are measured (seconds). 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. Indicates which zone is preferred as the hop target zone. Values 0 to 255. Default is 3. Mandatory or Optional? Optional.

Field name/BSS parameter name Interzone PingPong Allowed Count zone_pingpong_count

Interzone PingPong Enabled Timer zone_pingpong_ enable_win Interzone PingPong Disabled Timer zone_pingpong_ disable_win

0 to 255. Default is 30.

Optional.

0 to 255. Default is 30.

Optional.

Preferred PingPong Target Zone zone_pingpong_ preferred_zone

0 (outer zone preferred), 1 (inner zone preferred) or 255 (current zone). Default is 255.

Optional.

4-28

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

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 Brief description Specifies whether bit 8 of the address indicator in a PCS 1900 is set or unset. 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. Values 0 or 1. Default is Unset (0). Click buttons A to F. Mandatory or Optional? Mandatory.

Field name Address Indicator bit 8

PCS 1900 Frequency Blocks

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 Version information of the current Flash EEPROM load. Date and time when current Flash EEPROM load was created. Checksum value of the current Flash EEPROM load. The size of the current Flash EEPROM load. -2147483648 to 2147483647. -2147483648 to 2147483647. Size in Bytes Values 4 to 11 digits. Mandatory or Optional? Mandatory. Mandatory. Mandatory. Mandatory.

Field name Flash Information Flash Time Flash Checksum Flash Size

Trunk Information grouping


Table 4-10 describes the fields in the Trunk Information grouping of the BSS Detailed View.

68P02901W17-R 14 Apr 2006

GMR-01

4-29

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-10

BSS Detailed View fields - Trunk Information grouping Brief description Used to determine the severity assignment of alarms and maintenance actions affecting trunks. Used to determine the severity assignment of alarms and maintenance actions affecting trunks. Values 0 to 100 (Represents a percent of the capacity lost). Default is 50. 0 to 99 (Represents a percent of the capacity lost). Default is 10. Mandatory or Optional? Mandatory.

Field name Trunk Critical Threshold

Trunk Major Threshold

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-59for 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.

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.

4-30

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Table 4-11

BSS Detailed View fields - Directed Retry grouping Brief description Whether the MSC can be involved when a directed retry procedure is necessary. Whether a channel mode modify procedure follows a successful handover in which the channel mode changed. Values Enabled (1) or Disabled (0). Default is 0. 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. Mandatory or Optional? Optional.

Field name/BSS parameter name Directed Retry Preference dr_preference Directed Retry Channel Mode Modify dr_chan_mode_modify (OMC-R parameter name: dr_chan_mode_mod)

Optional.

68P02901W17-R 14 Apr 2006

GMR-01

4-31

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

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 Brief description Can only be modified if the MultiBand Inter-Cell Handover feature is unrestricted (enabled). Determines if the BSS suppresses the early sending of the Classmark Update message to the MSC. Values Enabled (1) or Disabled (0). Default is 0. 0 to 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. 0 - 100000 milliseconds. Default is 0. Mandatory or Optional? Mandatory.

Field name/BSS parameter name MultiBand Enabled mb_preference Early Classmark Sending early_classmark_send (OMC-R parameter name: earlyClassmarkSnd)

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.

Mandatory.

4-32

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

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 Brief description Whether Enhanced Full Rate (EFR) has been enabled at the BSS. Only valid when the Enhanced Full Rate feature EFROpt is unrestricted. Whether the speech version used can be built into the Handover Required message. Cannot be disabled: 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. Values Disabled (0), Enabled (1). Default is 0. Mandatory or Optional? Optional.

Field name/BSS parameter name Enhanced Full Rate Enabled efr_enabled

HO Req Speech Version Used handover_required_ sp_ver_used (OMC-R parameter name: ho_req_spver_used)

Disabled (0), Enabled (1). Default is 0.

Mandatory.

Circuit Error Rate Monitor grouping


See "Enhanced Circuit Error Rate Monitor (ECERM)" on page 2-73 for further details.

Enhanced Circuit Error Rate Monitor grouping


See "Enhanced Circuit Error Rate Monitor (ECERM)" on page 2-73 for further details.

GPRS grouping
Table 4-14 describes the fields in the GPRS grouping of the BSS Detailed View. These fields are greyed-out, if the GPRS feature (gprsOpt) is restricted at the BSS.

68P02901W17-R 14 Apr 2006

GMR-01

4-33

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Table 4-14

BSS Detailed View fields - GPRS grouping Brief description The SMG version adopted by the BSS over the Gb interface. Serving GPRS support node object identifier associated with this BSS. See "GPRS Interleaving TBFs" on page 2-94 for further details. See "GPRS Interleaving TBFs" on page 2-94 for further details. See "GPRS Interleaving TBFs" on page 2-94 for further details. See "GPRS Interleaving TBFs" on page 2-94 for further details. See "GPRS Interleaving TBFs" on page 2-94 for further details. See "Enhanced GPRS One Phase Access " on page 2-120 for details. Indicates whether or not the BSC allows PCU redundancy. See "Overview of configuring a PCU and its devices " on page 6-7 for details of the 3x PCU feature. Identifier of the first redundant PCU for PCU 0. Greyed-out if pcu_redundancy is set to False. Identifier of the second redundant PCU for PCU 0. Greyed-out if pcu_redundancy is set to False. Identifier of the first redundant PCU for PCU 1. Greyed-out if pcu_redundancy is set to False. Identifier of the second redundant PCU for PCU 1. Greyed-out if pcu_redundancy is set to False. True or False. Default is True. Values 24 to 31 (SMG Gb version). Default is 31. Mandatory or Optional? Optional.

Field name/BSS parameter name SMG Gb Protocol Version smg_gb_vers Related SGSN

Optional.

Delayed Downlink TBF Release Duration Delayed Uplink TBF Release Duration Delayed Downlink TBF Release Control Auto Downlink Duration GPRS Scheduling Beta Algorithm Enhanced One Phase Access eop_enabled PCU Redundancy Status pcu_redundancy

Optional. Optional. Optional. Optional. Optional. Mandatory.

Mandatory.

1st Redundant for PCU 0 pcu_red_map_01 2nd Redundant for PCU 0 pcu_red_map_02 1st Redundant for PCU 1 pcu_red_map_11 2nd Redundant for PCU 1 pcu_red_map_12

-1 to 2. Default is -1. -1 to 2. Default is -1. -1 to 2. Default is -1. -1 to 2. Default is -1.

Optional.

Optional.

Optional.

Optional.

Cont.

4-34

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Table 4-14

BSS Detailed View fields - GPRS grouping (Continued) Brief description Identifier of the first redundant PCU for PCU 2. Greyed-out if pcu_redundancy is set to False. Identifier of the second redundant PCU for PCU 2. Greyed-out if pcu_redundancy is set to False. The Medium Access mode that should be used by the PCUs. Values -1 to 2. Default is -1. Mandatory or Optional? Optional.

Field name/BSS parameter name 1st Redundant for PCU 2 pcu_red_map_21

2nd Redundant for PCU 2 pcu_red_map_22

-1 to 2. Default is -1.

Optional.

Medium Access Control Mode gprs_mac_mode Network Operation Mode gprs_network_ operation_mode GPRS Dual Power Mode gprs_dl_pwr_mode

Fixed access mode (0), Dynamic access mode (1). Default is 1. 1 to 3. Default is 3.

Mandatory.

Whether a GPRS is present between the MSC and the SGSN.

Mandatory.

The downlink power control mode the PCUs uses to broadcast data blocks to the mobile. See "PBCCH/PCCCH feature" on page 2-124 for details. See "Current Bucket Level (CBL) feature" on page 2-154 for details. See "Enhanced Scheduling" on page 2-156 for details. See "Enhanced Scheduling" on page 2-156 for details.

No power mode (0), Mode A (1), Mode B (2). Default is Mode A (1).

Optional.

SGSN Release sgsn_release Current Bucket Level Feature bssgp_cbl_bit Increased PRP Capacity Feature Enabled Max Number of UL timeslots per mobile PRR Blocks Reservation Aggressiveness Factor GPRS Uplink or Downlink bias Most Common Multislot of GPRS Mobiles Redundant PSP Audit Timer red_psp_audit_tmr

Optional. Mandatory.

Mandatory. Optional.

Audit mechanism used to determine the health of the secondary MPROC. Greyed-out if the GPRS feature is restricted at the BSS. See "Network Assisted Cell Change (NACC)" on page 2-181 for further details.

0 to 24. Default 24.

Optional.

{22708} GPRS Type 5 Algorithm Enabled gprs_type5_alg

68P02901W17-R 14 Apr 2006

GMR-01

4-35

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

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 Brief description Longitude position of the displayable node. Latitude position of the displayable node. The state of a node or link on a map. Values -18000 to 18000. -9000 to 9000. INS, OOS or Unknown. Currently, INS is defined as Enabled-Unlocked or Busy-Unlocked, and OOS is Disabled-Locked or Disabled-Unlocked. Mandatory or Optional? Optional. Optional. Optional.

Field name Longitude Latitude Service State

Default Map

See description in Table 3-3.

GSM/GPRS Trace Information grouping


See "Call trace flow control" on page 2-64 for details of these parameters.

SMS Information grouping


See "Short Message Service - Cell Broadcast" on page 2-46 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.

4-36

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Table 4-16

BSS Detailed View fields - Traffic Parameters grouping Brief description Number of SMS messages compared to calls, expressed as a ratio. OMC only attribute. Average number of handovers per call. OMC only attribute. The ratio of intra-BSC handovers to all handovers. OMC only attribute. 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. The average call duration during the busiest period of the day. Values 0.0 to 1.0. Default is 0. 0.0 to 15.0. Default is 0. 0.0 to 1.0. Default is 0. 0.0 to 30.0. Default is 0. Mandatory or Optional? Optional.

Field name Ratio of SMSs to calls

Number of handovers per call Ratio of Intra-BSC handovers to all handovers Location Update factor

Optional. Optional.

Optional.

Call Duration - seconds Paging rate in pages per second

0 to 1200. Default is 0. 0 to 20. Default is 0.

Optional. Optional.

Network Assisted Cell Change (NACC) grouping


{22708} 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 Brief description See "Network Assisted Cell Change (NACC)" on page 2-181 for further details. Values Mandatory or Optional?

Field name Cell Change Notification Enabled nacc_enabled

Quality of Service (QoS) grouping


{23956} See "Quality of Service (QoS)" on page 2-171 for details of these fields.

LCS grouping
See "GSM location services" on page 2-109 for details of these fields.

Network Controlled Cell Reselection grouping


See "Network Controlled Cell Reselection" on page 2-85 for further details of these fields.

68P02901W17-R 14 Apr 2006

GMR-01

4-37

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

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 greyed-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 Brief description See "GPRS Seamless Cell Reselection" on page 2-151 for details. Values Mandatory or Optional? Mandatory.

Field name/ parameter name GPRS Seamless Cell Reselection Feature scr_enabled

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 {22064} GSM HR Feature (gsmHalfRateOpt) are unrestricted (Enabled) at the BSS, see "Adaptive Multi-Rate (AMR)" on page 2-138 for details. Table 4-19 Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping Brief description 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 (cic_validation) is disabled at the Assoc_RXCDR. 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. Values 0 or 1. Enabled (1), Disabled (0). Default is 0. Mandatory or Optional? Optional.

Field name/BSS parameter name AMR Full Rate Enabled amr_bss_full_ rate_enabled (OMC-R parameter name: amr_fr_enabled) AMR Half Rate Enabled amr_bss_half_rate_ enabled (OMC-R parameter name: amr_hr_enabled)

0 or 1. Enabled (1), Disabled (0). Default is 0.

Optional.

AMR MS Monitor Used to detect MSs continually Period requesting the highest or lowest amr_ms_monitor_period modes. (OMC-R parameter name: AmrMsMonPeriod) 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.

0, or 10 to 120 SACCH periods.0 disables the MS Monitor function. Default is 40. 50 to 100%. Default is 95%.

Optional.

Optional.

Cont.

4-38

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Table 4-19 Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping (Continued) Field name/BSS parameter name AMR MS Low RXQUAL amr_ms_low_rxqual Brief description If the MS is consistently requesting lowest rate Codec mode but reports RXQUAL values less than defined, the BSS uses this value to decrease the Down Link adaptation Thresholds. The percentage of the monitor period for which an individual MS can request the highest Codec mode. 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. Used to increase or decrease C/I adaptation thresholds according to the values for AmrMsHighRxqual and amr_ms_low_rxqual. Overrides MSC provided preference, and forces Half Rate usage for all AMR/GSM Half Rate capable calls within the BSS. {22064}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. 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). Values 0 to 7 Qband units. Default is 2 Qbands or 0.5% BER. Mandatory or Optional? Optional.

AMR MS High CMR amr_ms_high_cmr

50 to 100% Default is 99%.

Optional.

AMR MS High RXQUAL amr_ms_high_rxqual (OMC-R parameter name: AmrMsHighRxqual) AMR Downlink Threshold Adjustment amr_dl_thresh_adjust (OMC-R parameter name: AmrDlThreshAdj) AMR Force Half Rate Usage force_hr_usage (OMC-R parameter name: force_hr_use)

0 to 7 Qband units. Default is 4 Qbands, or 2.5% BER.

Optional.

1 to 7 dB. Default is 3.

Optional.

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: AmrDlLaModeChgMin)

0 to 255 ms. Default is 100.

Optional.

68P02901W17-R 14 Apr 2006

GMR-01

4-39

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping with GSM Half Rate
Table 4-20 describes the new 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-149 for details. Table 4-20 Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping Brief description Enables and disables GSM Half Rate (HR) for the BSS. Cannot be enabled (greyed-out) if GSM Half Rate Feature is restricted, or if CIC Validation (cic_validation) is disabled at the Assoc_RXCDR. Values 0 or 1. Enabled (1), Disabled (0). Default is 0. Mandatory or Optional? Optional.

Field name/BSS parameter name GSM BSS Half Rate Enabled gsm_bss_half_rate_ enabled (OMC-R parameter name: gsm_bss_half_rate_ enabled)

4-40

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS using the OMC-R GUI

Pre-empt grouping
{24347} See "Enhanced Multi-level Precedence and Pre-emption (eMLPP)" on page 2-185 for details of these parameters.

RSL Congestion grouping


{24660/24661} See "RSL Congestion Control" on page 2-191 for details of these parameters.

Improved Timeslot Sharing grouping


{28075} Table 4-21 describes the field in the Improved Timeslot Sharing grouping of the BSS Detailed View. The field is greyed-out if the ITS feature (itsOpt) in the Optional Features grouping of the BSS Detailed View is restricted (Disabled (0)). Table 4-21 BSS Detailed View fields - Improved Timeslot Sharing Brief description Enables and disables the ITS feature on the BSS. It can only be modified if the itsOpt is enabled. Values 0 or 1. Enabled (1), Disabled (0). Mandatory or Optional? Optional

Field name/BSS parameter name Improved Timeslot Sharing Enabled improve_ts_enabled (OMC-R parameter name: its_enabled

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-41. 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:

68P02901W17-R 14 Apr 2006

GMR-01

4-41

Creating a BSS using the OMC-R GUI

Chapter 4: Configuring a BSS/RXCDR

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 be updated at the following RXCDRs: RXCDR_<name> RXCDR_<name> ... Do you wish to continue?

Click on 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-42

GMR-01

68P02901W17-R 14 Apr 2006

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 prior to 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 1 Create an RXCDR using the OMC-R GUI

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-35 for further details. The RXCDR class button changes colour. From the menu bar, select Edit - Create. The OMC-R displays the RXCDR Detailed View in Create mode Click on the Initial Software Load button to display a Software Inventory Dialog window. Double-click on 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.

2 3 4 5 6

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 on that field. A context sensitive help page is displayed. 7 8 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.

68P02901W17-R 14 Apr 2006

GMR-01

4-43

Creating an RXCDR 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-41. 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 on 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 on OK to continue or Cancel to cancel the cycling.

4-44

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring the packet switch/MUX for a BSS

Configuring the packet switch/MUX for a BSS


Introduction to packet switch configuration


This section gives an overview only of how to connect a new BSS to existing packet switch equipment. For full details of how to connect and configure a Vanguard 6560 MPRouter, 6525 X.25 packet switch, and 6525 MUX from scratch, see Installation and Configuration: OMC-R Clean Install (68P02901W47) and Operating Information: OMC-R System Administration (68P02901W19). For full details of how to check the Vanguard router software versions, see "Checking the Vanguard router software versions" on page 1-11.

If the software load on the Vanguard equipment is not at the required level, then it will not be supported. Motorola recommends that the software loads are checked. There have been several generations of packet switch/MUX. The latest is the Vanguard 6560 MPRouter. The 6525 packet switch and 6250 MUX are previous-generation equipment. The Vanguard 6560 MPRouter combines the functionality of both. When a new BSS/RXCDR is added to the GSM network, the OML from the NE must be connected to the OMC-R through the X.25 network. This requires that the packet switch is configured for the new NE and the OML connected to it.

Overview of configuring a Vanguard 6560 MPRouter for a new BSS


Prerequisites
To perform configuration changes on the Vanguard 6560 MPRouter, an asynchronous terminal or a PC with an asynchronous emulation software is required. The following procedure assumes that the router has already been set up, and that an additional BSS is being added. To set up a Vanguard 6560 MPRouter, see Installation and Configuration: OMC-R Clean Install (68P02901W47).

68P02901W17-R 14 Apr 2006

GMR-01

4-45

Configuring the packet switch/MUX for a BSS

Chapter 4: Configuring a BSS/RXCDR

Adding an additional BSS to the router


To connect a new BSS to the router, follow these steps. Refer to: Installation and Configuration: OMC-R Clean Install (68P02901W47) for further information. Procedure 4-7 1 Connect a new BSS to the router

Connect to the Vanguard 6560 MPRouter, using telnet over the LAN or PAD within the OMC-R.

If using telnet, type atds at the OK prompt. 2 3 4 5 6 7 8 9 10 Supply the password to the router. Check which Virtual Ports are available for the BSS to connect to. Configure the new Virtual Port, if it has not already been done, or copy another Virtual Port to the new one. Check the Virtual Port Mapping Tables, to identify which timeslot can be allocated to the Virtual Port. Allocate a timeslot to the Virtual Port. Identify the next available entry in the Route Selection Tables. Configure the Routing Selection tables to identify which 6560 is connected to the new BSS. Configure routing Tables on all other Routers, if necessary. This identifies the route to be taken to the BSS from each 6560. Carry out a warm reboot. This reboots the Route Selection Tables, inserting the changes.

To manage the packet switch, refer to Operating Information: OMC-R System Administration (68P02901W19).

4-46

GMR-01

68P02901W17-R 14 Apr 2006

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-R 14 Apr 2006

GMR-01

4-47

Creating a BSS/RXCDR database

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

NE database checks
Network Element (NE) database checks are required for the following reasons: 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.

4-48

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a BSS/RXCDR database

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 database.list $DBROOT/ BSSspecific/ BSS<name> dbComment download.list 00.00.03.fd.02.Z db950228122300 database.list dbComment 00.00.03.fd.02 database.list CSFP directory dbComment download.list OTHER BSSs
ti-GSM-SC01W17-000049-eps-sw

current database

fallback database for current load

CSFP database

68P02901W17-R 14 Apr 2006

GMR-01

4-49

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.

Removing a BSS or RXCDR will prevent 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-110 or "Reparenting an RXCDR to a different MSC" on page 4-117 procedures.

4-50

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Deleting a BSS/RXCDR

Removing a BSS/RXCDR from the network


Perform the following tasks to remove a BSS or RXCDR from the network: Procedure 4-8 1 2 Remove a BSS or RXCDR from the network

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 "Deleting a BSS/RXCDR at the packet switch/MUX" on page 4-54.

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-9 1 Prepare to delete BSS/DXCDR

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.

This can be done locally at the BSC or remotely using rlogin. 2 Physically disconnect the cable between the OMC-R and BSS/RXCDR.

68P02901W17-R 14 Apr 2006

GMR-01

4-51

Deleting a BSS/RXCDR

Chapter 4: Configuring a BSS/RXCDR

Deleting the BSS/RXCDR


Now the BSS/RXCDR can be deleted. To do this follow these steps: Procedure 4-10 1 Delete BSS/RXCDR

Using the Navigation Tree, display the BSS/RXCDR to be deleted.

Configuration information may still need to be extracted if the BSS is to be added at a later date. To do this, see "Extracting data from the CM MIB using cmutil" on page 15-30. 2 As omcadmin, delete the BSS from the MIB using the following command:

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

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.

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 5 days) and the entries deleted using delete_BSS, delete_SITE or delete_CELL commands.

4-52

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Deleting a BSS/RXCDR

Follow up activities after deletion of the BSS/RXCDR


When the BSS/RXCDR has been deleted the following steps may need to be performed: Procedure 4-11 1 Follow up after deleting BSS/RXCDR

If the cells of the BSS are being decommissioned, or reused under different BSSs, external neighbours which point to these cells may require removal. The HierDelete utility does not remove these external neighbours from other BSSs. The neighbours 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

3 4

Edit any appropriate subscription lists to remove the BSS from them. See OMC-R Online Help, Network Operations for details of subscription lists.

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. 5 6 7 8 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 "Deleting a BSS/RXCDR at the packet switch/MUX" on page 4-54. 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.

68P02901W17-R 14 Apr 2006

GMR-01

4-53

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-12 1 2 Change packet switch configuration prior to deleting BSS/RXCDR

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 made at the packet switch. No path through the MUX to the packet switch will exist and the NE should have been removed from the OMC-R NE nodes file so that no data will be 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.

4-54

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Deleting a BSS/RXCDR at the packet switch/MUX

Removing the cabling between packet switch and MUX


If a complete 2 Mbit/s link is to be removed: Procedure 4-13 1 2 Remove complete 2 Mbit/s link prior to deleting BSS/RXCDR

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.

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-14 1 2 Change MUX configuration prior to deleting BSS/RXCDR

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 sub-section Removing the NE from the MUX.

68P02901W17-R 14 Apr 2006

GMR-01

4-55

Deleting a BSS/RXCDR at the packet switch/MUX

Chapter 4: Configuring a BSS/RXCDR

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-15 1 2 Remove configuration information

Use the MUX configuration table to determine the linkname, endpoints and circuit name, that need 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.

Removing the NE link to the MUX


To remove an NE link to the MUX: Procedure 4-16 1 2 Remove NE link to the MUX

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.

3 4

5 6

4-56

GMR-01

68P02901W17-R 14 Apr 2006

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-60 and "Configuring a cage" on page 4-65 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 fibre 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_ext 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 cabinets 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.

68P02901W17-R 14 Apr 2006

GMR-01

4-57

Equipping cabinets and cages at a BSS site

Chapter 4: Configuring a BSS/RXCDR

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.

A maximum of three extension cabinets can be connected to a Horizon II macro cabinet type, as shown in Table 4-22. Table 4-22 Extension cabinets for Horizon II macro Master cabinet Horizon II macro Extension 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-23. Table 4-23 Cabinet types allowing Horizon II macro_ext as an extension type Extension Horizon II macro_ext Master cabinet M-Cell6. Horizonmacro. Horizon II macro.

Horizon II mini and Horizon II macro cabinets


{24281} 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 will 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-24 shows extension cabinets to which a Horizon II mini can be master.

4-58

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Equipping cabinets and cages at a BSS site

Table 4-24

Extension cabinet types allowed for Horizon II mini Extension cabinet Horizon II mini extension. Horizon II macro extension. Horizon macro extension. TCU6.

Master cabinet Horizon II mini

Table 4-25 shows the master cabinets to which a Horizon II mini extension can be equipped. Table 4-25 Master cabinet types allowed for Horizon II mini extension Master cabinet Horizon II mini. Horizon II macro. Horizon macro. MCELL6.

Extension cabinet Horizon II mini extension

68P02901W17-R 14 Apr 2006

GMR-01

4-59

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-17 1 Create Cabinet instance using the OMC-R GUI

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-35 for further details. The network object class button changes colour. 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.

2 3 4 5

Cabinet Detailed View fields


The following sections list and briefly describe the parameter fields in the Cabinet Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

4-60

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a cabinet

Identification grouping
Table 4-26 describes the fields in the Identification grouping of the Cabinet Detailed View. Table 4-26 Cabinet Detailed View fields - Identification grouping Brief description The type of this cabinet. See description in Table 4-1. See description in Table 3-1. See description in Table 4-1. Displays the name of the parent site. Click to display the parent site Detailed View. Not displayed for a Horizonmacro or Horizon II macro BTS. Greyed-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 to 15 characters Optional. Values {24281} 0 to 27. Default is Cabinet. 0 to 15. Mandatory or Optional? Mandatory.

Field name Cabinet Type cabinet_type RDN Class RDN Instance NMC RDN Value Parent Detailed View

Kit Number

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

4-61

Configuring a cabinet

Chapter 4: Configuring a BSS/RXCDR

Table 4-26

Cabinet Detailed View fields - Identification grouping (Continued) Brief description See Maintenance Information: BSS Field Troubleshooting (68P02901W51) for details of all the possible values that can be displayed. {24281} Displayed when cabinet_type is: Horizon II mini, Horizon II macro, Horizon macro, MCell6 or MCell2. 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. Not displayed for a Horizonmacro or Horizon II macro BTS. Greyed-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 to 15 characters Values Mandatory or Optional? Optional.

Field name Field Replacement Unit (FRU)

Serial Number

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this Cabinet. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

General grouping
Table 4-27 describes the fields in the General grouping of the Cabinet Detailed View.

4-62

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a cabinet

Table 4-27

Cabinet Detailed View fields - General grouping Brief description 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 {24281} Horizon II mini sites can support one of the following frequencies: PGSM, EGSM, or DCS1800. 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. {24281} 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 or not 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). Values 1 to 15. Mandatory or Optional? Optional.

Field name/BSS parameter name Frequency Type frequency_type (OMC-R parameter name: freq_type)

Power Supply Unit 1 to 4 psu_fru_1 to psu_fru_4

Optional.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

4-63

Configuring a cabinet

Chapter 4: Configuring a BSS/RXCDR

Table 4-27

Cabinet Detailed View fields - General grouping (Continued) Brief description Indicates whether an internal HDSL modem is present in the cabinet. When cabinet type is Horizonmacro, or Horizonmacro_ext this field is greyed-out. For a {24281} Horizon II mini, Horizon II mini extension, Horizon II macro, and Horizon II macro extension, this field does not appear. Indicates whether an internal integrated antenna is present in the cabinet. When cabinet type is Horizonmacro or Horizonmacro_ext this field is greyed-out. {24281} For a Horizon II mini, Horizon II mini extension, Horizon II macro, and Horizon II macro extension, this field does not appear. Values 0 or 1. Internal HDSL modem is not present (0). Internal HDSL modem is present (1). Mandatory or Optional? Optional.

Field name/BSS parameter name Internal HDSL Modem (OMC-R parameter name: int_hdsl_modem)

Internal Integrated Antennae int_integrated _ant

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-18 1 Equip a Cabinet at the TTY interface

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-64

GMR-01

68P02901W17-R 14 Apr 2006

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-19 1 Create a Cage instance using the OMC-R GUI

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-35 for further details. The network object class button changes colour. 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.

2 3 4 5

Cage Detailed View fields


The following sections list and briefly describe the parameter fields in the Cage Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

68P02901W17-R 14 Apr 2006

GMR-01

4-65

Configuring a cage

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 Brief description See Table 4-1 description. See Table 3-1 description. Values Default is Cage. For a BSC or RXCDR, cage range is 0-13. For a BTS, cage range is 2-15. Mandatory or Optional?

Field name RDN Class RDN Instance

NMC RDN Value Parent Detailed View

See Table 4-1 description. Displays the name of the parent site (BSC or BTS). Click to display the parent site Detailed View. The identifier of the cabinet in which this cage resides. Whether an IAS is connected to this cage. Not used if cabinet_type is PCU. 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. 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. The KSW pair managing this cage. Not used if cabinet_type is PCU. IAS not connected, or IAS is connected. 0 - 4 Mandatory. Mandatory.

Cabinet Identifier IAS Connected

KSWX Number 0

Optional.

KSWX Number 1

0 - 4

Optional.

KSW Pair

0 - 3

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this Cage. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

4-66

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a cage

Equipping a cage from the TTY interface


To equip a cage using the TTY interface, follow these steps: Procedure 4-20 1 Equip a Cage at the TTY interface

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-R 14 Apr 2006

GMR-01

4-67

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-21 1 Create a RXCDR cabinet using the OMC-R GUI

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-35 for further details. The network object class button changes colour. 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-60 for details of the Cabinet Detailed View fields.

2 3

To obtain the relevant information for a parameter, click on Help at the top right of the window, select On Context and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed. 4 5 Select File - Create from the menu bar to create an RXCDR cabinet. Select File - Close to close the Detailed View form.

4-68

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an RXCDR cabinet

Equipping an RXCDR cabinet using the TTY interface


See "Example of equipping an RXCDR cabinet and cage using the TTY interface" on page 4-72.

68P02901W17-R 14 Apr 2006

GMR-01

4-69

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.

4-70

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an RXCDR cage

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-22 1 Create a RXCDR Cage instance using the OMC-R GUI

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-35 for further details. The network object class button changes colour. 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-65 for details of the Cage Detailed View fields.

2 3

To obtain the relevant information for a parameter, click on Help at the top right of the window, select On Context and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed. 4 5 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.

Equipping an RXCDR cage using the TTY interface


See "Example of equipping an RXCDR cabinet and cage using the TTY interface" on page 4-72.

68P02901W17-R 14 Apr 2006

GMR-01

4-71

Example of equipping an RXCDR cabinet and cage using the TTY interface

Chapter 4: Configuring a BSS/RXCDR

Example of equipping an RXCDR cabinet and cage using the TTY interface

Scenario
In this example, an RXCDR cabinet will be equipped at MSC_XCDR. The following information is available: The RXCDR cabinet will be number 0. The cabinet will be equipped with one cage, numbered 0.

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.

4-72

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Example of equipping an RXCDR cabinet and cage using the TTY interface

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

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-23 1 2 3 Equip RXCDR cabinet and cages using TTY interface

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

Equipping the RXCDR cage using the TTY interface


At an RXCDR site, cage numbers are unique. The numbers can range from 0 to 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.

68P02901W17-R 14 Apr 2006

GMR-01

4-73

Example of equipping an RXCDR cabinet and cage using the TTY interface

Chapter 4: Configuring a BSS/RXCDR

-> equip 0 CAGE Enter the identifier for the CAGE: 0 Enter the KSW pair that manages the CAGE: Enter the KSWX connecting cage to KSW for Enter the KSWX connecting cage to KSW for Enter cabinet to which the cage belongs: Is an IAS connected?: no COMMAND ACCEPTED ->

1
TDM 0: TDM 1:

4-74

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an Assoc_BSS

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. {23683} 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 already exists. The parent device has been defined in advance, that is, an RXCDR.

68P02901W17-R 14 Apr 2006

GMR-01

4-75

Configuring an Assoc_BSS

Chapter 4: Configuring a BSS/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-24 1 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-35 for further details. The Assoc_BSS class button changes colour. Select Edit - Create from the Navigation Tree menu bar. The OMC-R displays the Assoc_BSS Detailed View in Create mode. Click on the Associated BSS button. The OMC-R displays a popup window which lists all the BSSs currently in the network. Select the BSS to be associated with this RXCDR. This highlights the BSS. Click on 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.

2 3

4 5 6

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 on that field. A context sensitive help page is displayed. 7 8 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.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

4-76

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an Assoc_BSS

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 Brief description See Table 4-1 description. See Table 3-1 description. See Table 4-1 description. Displays the name of the parent object. Click to display the parent RXCDR Detailed View. Displays the identifier of the associated BSS. Not applicable. Values Default is Assoc_BSS. 1 to 128. Mandatory or Optional?

Field name RDN Class RDN Instance NMC RDN Value Parent Detailed View

Associated BSS

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this Assoc_BSS. Where additional notes are not required, it is advisable to close this field by clicking on 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 Brief description See description in Table 4-7. See description in Table 4-7. See description in Table 4-7. Values Mandatory or Optional?

Field name UL and DL Volume Control Type Downlink Audio Level Offset Uplink Audio Level Offset

68P02901W17-R 14 Apr 2006

GMR-01

4-77

Configuring an Assoc_BSS

Chapter 4: Configuring a BSS/RXCDR

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

4-78

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an Assoc_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. {23683} 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 already exists in the network. A BSS exists in the network.

68P02901W17-R 14 Apr 2006

GMR-01

4-79

Configuring an Assoc_RXCDR

Chapter 4: Configuring a BSS/RXCDR

Creating an Assoc_RXCDR using the OMC-R GUI


To create an Assoc_RXCDR using the OMC-R GUI, follow these steps: Procedure 4-25 1 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-35 for further details. The Assoc_RXCDR class button changes colour. Select Edit - Create from the Navigation Tree menu bar. The OMC-R displays the Assoc_RXCDR Detailed View in Create mode. Click on 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 on 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 new Assoc_RXCDR. From the menu bar, select File - Close to close the Detailed View.

2 3 4 5 6 7 8

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.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on 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.

4-80

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an Assoc_RXCDR

Table 4-31

Assoc_RXCDR Detailed View fields - Identification grouping Brief description See Table 4-1 description. See Table 3-1 description. See Table 4-1 description. Displays the parent BSS Detailed View. Displays the name of the associated RXCDR. Mandatory. Values Default is Assoc_RXCDR. 1 to 128. Mandatory or Optional?

Field name RDN Class RDN Instance NMC RDN Value Parent Detailed View Associated RXCDR

Additional Information
Use the Additional Information window to input any notes relating to this Assoc_RXCDR. Where additional notes are not required, it is advisable to close this field by clicking on 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 Brief description See "Enhanced XBL (EXBL)" on page 2-11 for further details. Values Mandatory or Optional? Mandatory.

Field name/BSS parameter name CIC Validation cic_validation

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping
Table 4-33 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 greyed-out if both amrEnhancedCapOpt and gsmHalfRateOpt are restricted. (see "Adaptive Multi-Rate (AMR)" on page 2-138 and "GSM Half Rate" on page 2-149 for additional information).

68P02901W17-R 14 Apr 2006

GMR-01

4-81

Configuring an Assoc_RXCDR

Chapter 4: Configuring a BSS/RXCDR

Table 4-33

Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping Brief description Whether the BSC-RXCDR interface is using the available resources for half rate calls with 8 Kbps Ater allocations. If cic_validation (see Table 4-32) is disabled, this field is greyed-out and set to Disabled (0). 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. 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. Values 0 or 1. Disabled (0) or Enabled (1). Default is 0. Mandatory or Optional? Optional.

Field name/BSS parameter name Enhanced Auto Connect Mode eac_mode

CIC Blocking Threshold cic_block_thresh

0 to 245. Default is 0.

Optional.

CIC Unblocking Threshold cic_unblock_thresh (OMC-R parameter name: CicUnblockThresh)

0, 11 to 255. Default is 0.

Optional.

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 Kbps ATERs are available, then full rate calls will be prevented from being set up and only half rate calls will be accepted.

4-82

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an Assoc_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: 1 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 or not AMR Half Rate, GSM Half Rate and eac_mode are enabled: modify_value 0 cic_validation NO AXCDR 1

68P02901W17-R 14 Apr 2006

GMR-01

4-83

Configuring an Assoc_RXCDR

Chapter 4: Configuring a BSS/RXCDR

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

4-84

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an Assoc_RXCDR

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

68P02901W17-R 14 Apr 2006

GMR-01

4-85

Configuring an Assoc_RXCDR

Chapter 4: Configuring a BSS/RXCDR

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

If an AXCDR with cic_validation enabled does not exist, the system also responds:
WARNING: AXCDR CIC validation must be enabled for AMR or GSM HR.

If the parameter handover_required_sp_ver_used is disabled in the BSS Detailed View, the system responds:
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: 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

4-86

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an Assoc_RXCDR

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-R 14 Apr 2006

GMR-01

4-87

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 labelled 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 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 of doing this, 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.

Once the change assoc NE ID process has started, if the GUI is closed for some reason the change assoc NE ID process will continue.

Phases in the change assoc NE ID process


The change assoc NE ID operation has three phases: 1. 2. 3. Extract. Unequip. Re-equip.

4-88

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

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.

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-R 14 Apr 2006

GMR-01

4-89

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

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-26 1 Change NE ID of Assoc_BSS or Assoc_RXCDR using the OMC-R GUI

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 colour. 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 to 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.

4-90

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

Figure 4-4

Change Assoc NE ID form (for an Assoc_RXCDR instance)

68P02901W17-R 14 Apr 2006

GMR-01

4-91

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

Chapter 4: Configuring a BSS/RXCDR

Viewing network entity ids


To display a list of all the network entities managed by the OMC-R, follow these steps: Procedure 4-27 1 Display network entities

Click on 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 on the Print button to print the list of NEs to the printer specified in the PRINTER environmental variable. 2 Click on 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 on Cancel. Click on 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.

4-92

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

Starting the change assoc NE ID process


To start the change assoc NE ID process, follow these steps: Procedure 4-28 1 Start the change assoc NE ID process

Click on 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 on 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 on 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 on the [Symbol_triangledown] button to the right of the status bar. To shrink the status bar back to its original size, click on the [Symbol_triangleup] button. To view the active log file for the change assoc NE ID process, go to Viewing other log files below.

68P02901W17-R 14 Apr 2006

GMR-01

4-93

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

Chapter 4: Configuring a BSS/RXCDR

Figure 4-5 shows an example of the .progress log file with the Extracting phase complete, and the Unequipping phase in progress. Figure 4-5 .progress log file

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.

4-94

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

Figure 4-6

Log File Selection window

Selecting an .active log file


To select an .active log file, follow these steps: Procedure 4-29 1 2 View an active log file

Select the .active log file in the Files pane of the Log File Selection window. Click on 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 greyed-out and cannot be selected. Now go to Closing the log file window step 1.

68P02901W17-R 14 Apr 2006

GMR-01

4-95

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

Chapter 4: Configuring a BSS/RXCDR

Figure 4-7

.active log file

4-96

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

Viewing an inactive log file


To view an inactive log file (such as, .complete log file) follow these steps: Procedure 4-30 1 View an inactive log file

Navigate to another directory using the Filter line and button, and select a log file. Or, if necessary: Click on Cancel to close the window and return to the Change Assoc NE ID window. Click on 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-31 1 2 Close the log file window

Left-click on 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.

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.

68P02901W17-R 14 Apr 2006

GMR-01

4-97

Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR

Chapter 4: Configuring a BSS/RXCDR

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.

4-98

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring DYNETs and DYNETGroups

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

68P02901W17-R 14 Apr 2006

GMR-01

4-99

Configuring DYNETs and DYNETGroups

Chapter 4: Configuring a BSS/RXCDR

DYNET restrictions
Restrictions and exceptions for a DYNET are as follows: 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 exactly the same BTSs, or marker sites (switching sites), in the same order. DYNETs must have different E1/T1 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. A DYNET device can only be equipped to a BSC. There can be only three DYNETs per DYNETGroup. More than one E1/T1 link can exist between BTSs for dynamic sharing purposes.

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.

4-100

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring DYNETs and DYNETGroups

DYNETGroup and DYNET topics


The following sections contain further information about DYNETGroups and DYNETs: "Configuring a DYNETGroup" on page 4-102, including creating and deleting using GUI or TTY interface. "Configuring a DYNET" on page 4-104, including creating, viewing, editing and deleting using GUI or TTY interface.

68P02901W17-R 14 Apr 2006

GMR-01

4-101

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-20 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-32 1 Create a DYNETGroup using the OMC-R GUI

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-35 for further details. The class button changes colour. 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.

2 3 4 5

DYNETGroup Detailed View fields


The following sections list and briefly describe the parameter fields in the DYNETGroup Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

4-102

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a DYNETGroup

Identification grouping
Table 4-34 describes the fields in the Identification grouping of the DYNETGroup Detailed View. Table 4-34 DYNETGroup Detailed View fields - Identification grouping Brief description See Table 4-1 description. See Table 3-1 description. See Table 4-1 description. Click to display the parent BSS Detailed View. Values Default is DYNET Group. 0 to 19. Mandatory or Optional?

Field name RDN Class RDN Instance NMC RDN Value Parent Detailed View

Additional Information
Use the Additional Information window to input any notes relating to this DYNETGroup. Where additional notes are not required, it is advisable to close this field by clicking on 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-R 14 Apr 2006

GMR-01

4-103

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 to 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 to 9. When dynamic allocation is disabled at the corresponding site, valid path identifiers are available in the range 0 to 9. See "Dynamic allocation of BSC-BTS Backing Resources (DYNET)" on page 2-20 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-20.

Creating a DYNET using the OMC-R GUI


Prerequisite
Before creating a DYNET using the OMC-R GUI, a DYNETGroup must have been created.

4-104

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a DYNET

Procedure
To create a DYNET, follow these steps: Procedure 4-33 1 Create a DYNET using the OMC-R GUI

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-35 for further details. The class button changes colour. Select Edit - Create from the Navigation Tree menu bar. The OMC-R displays the DYNET Detailed View form in Create mode. 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.

2 3 4 5

DYNET Detailed View fields


The following sections list and briefly describe the parameter fields in the DYNET Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

Identification grouping
Table 4-35 describes the fields in the Identification grouping of the DYNET Detailed View.

68P02901W17-R 14 Apr 2006

GMR-01

4-105

Configuring a DYNET

Chapter 4: Configuring a BSS/RXCDR

Table 4-35

DYNET Detailed View fields - Identification grouping Brief description See Table 4-1 description. See Table 3-1 description. See Table 4-1 description. Click to display the parent DYNET Group Detailed View. Values Default is BSS. 0 to 2. Mandatory or Optional?

Field name RDN Class RDN Instance NMC RDN Value Parent Detailed View

Additional Information
Use the Additional Information window to input any notes relating to this DYNET. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

Local Routing Information grouping


Table 4-36 describes the fields in the Local Routing Information grouping of the DYNET Detailed View. Table 4-36 DYNET Detailed View fields - Local Routing Information grouping Brief description The number of timeslots reserved at a DYNET for BSC-BTSdynamic allocation. Values 0 - 31. Default: 0. Mandatory or Optional? Mandatory.

Field name/BSS parameter name Shared Timeslots shared_timeslots

Path information grouping


Table 4-37 describes the fields in the path Information grouping of the DYNET Detailed View.

4-106

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a DYNET

Table 4-37

DYNET Detailed View fields - path Information grouping Brief description Number of links in the sequence for the DYNET. A DYNET can have up to 11 links. The MSI id at the BSC where the MMS resides. The MMS id for the BSC network definition. The BTS site identifier, that is, the terminating site. The first to sixth link in the DYNET path. Values 1 to 11. Mandatory or Optional? Mandatory.

Field name/BSS parameter name No of Links numInSequence BSC MSI Id msi_id BSC MMS Id mms_id Site Id Siteid Link 1 to Link 6 DYNET_link1 to DYNET_link6

0 to 55. 0 or 1. 1 to 100. Site Id (0..120, 254). Upstream MSI (0..55, 254). Upstream MMS (0..1, 254). Downstream MSI (0..55, 254). Downstream MMS (0..1, 254). Site Id (0..120, 254). Upstream MSI (0..55, 254). Upstream MMS (0..1, 254). Downstream MSI (0..55, 254). Downstream MMS (0..1, 254). Site Id (0) Upstream MSI (0..55) Upstream MMS (0..1) Downstream MSI (0..55) Downstream MMS (0..1). Button on or off.

Mandatory. Mandatory. Mandatory. Link 1 is mandatory, Link 2 to 6 are optional.

Link 7, 8, 9, 10 (DYNET_link7)

The seventh, eight, ninth and tenth links in the DYNET path.

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.

Optional.

TS Switch (GUI only)

Determines whether the site is a timeslot switching site.

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

68P02901W17-R 14 Apr 2006

GMR-01

4-107

Configuring a DYNET

Chapter 4: Configuring a BSS/RXCDR

To delete a DYNET, see the general procedure in "Deleting a network object using the OMC-R GUI" on page 1-44.

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, see examples below:. 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 The system responds with prompts for further information. Bold text shows examples of user responses: Enter 1st and 2nd DYNET identifiers: 1 0 Enter BSC MMS identifiers: 0 0 Enter SITE identifier: 1 Enter upstream MMS identifiers: 0 0
Enter downstream MMS identifiers: COMMAND ACCEPTED

Example 2: To equip a second set of E1/T1 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: 1 1 Enter BSC MMS identifier: 1 0 Enter SITE identifier: 1 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

4-108

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a DYNET

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

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 systems responds:
WARNING: Calls on this DYNET may be dropped. COMMAND ACCEPTED Are you sure (Y = Yes, N = No)?

68P02901W17-R 14 Apr 2006

GMR-01

4-109

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-112. "Reparenting a BSS to a different RXCDR (same OMC-R)" on page 4-115. "Reparenting an RXCDR to a different MSC" on page 4-117.

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/recreate of MIB or MIB migration. This script can be obtained from the CNRC through your local office.

4-110

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Reparenting a BSS

To use the preserve_site_names script, follow these steps: Procedure 4-34 1 Use preserve_site_names script

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 the new OMC-R /usr/omc/ne_data/.

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-R 14 Apr 2006

GMR-01

4-111

Reparenting a BSS to a different OMC-R

Chapter 4: Configuring a BSS/RXCDR

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. Ins the OML to get the changes to take effect. The old OMC-R will then lose connection to the BSS. Ensure the OML links between the BSS and old OMC-R have been disconnected. Ensure the OML links between the BSS and the new OMC-R have been properly configured, by liaising with the BSS field engineer. If required, reconfigure the entries for the NE from the packet switch/MUX. Refer to "Configuring the packet switch/MUX for a BSS" on page 4-45.

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.

4-112

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Reparenting a BSS to a different OMC-R

At the old OMC-R


At the old OMC-R, proceed as follows: Procedure 4-35 1 At the old OMC-R, reparent a BSS to a different OMC-R

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.

Find which cells of the BSS still have external neighbours in the old OMC-R. These cells will need to be 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 scriptpreserve_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> his 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

3 4

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

6 7

At the old OMC-R, delete the BSS/RXCDR. Refer to "Deleting a BSS/RXCDR" on page 4-50. Add in the proxy cells to the old OMC-R using the proxycell.ip file is as follows: cmutil -a -i proxycell.ip

68P02901W17-R 14 Apr 2006

GMR-01

4-113

Reparenting a BSS to a different OMC-R

Chapter 4: Configuring a BSS/RXCDR

At the new OMC-R


At the new OMC-R, proceed as follows: Procedure 4-36 1 At the new OMC-R reparent the BSS

Create the BSS. Refer to "Overview of adding a BSS or RXCDR" on page 4-2. Ensure 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. 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

2 3

If the BSS had to be renamed (for example, due to a move to a different MSC), edit the <bss_name>.ip file and change the name given for the container entries: sed s/"old BSS name"/"new BSS name"/g\ <<BSS_name>.upd> <new_BSS_name>.upd The script should then be run in update mode as follows: preserve_site_names update <new_BSS_name>

4-114

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Reparenting a BSS to a different RXCDR (same OMC-R)

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 the links between the BSS and original RXCDR have been disconnected, by liaising with the BSS field engineer. If required, reconfigure the entries for the NE from the packet switch/MUX (see "Configuring the packet switch/MUX for a BSS" on page 4-45). Ensure 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 Signalling 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-37 1 2 3 Reparent a BSS to a different RXCDR

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 Procedure 4-38. If not, the procedure is finished.

68P02901W17-R 14 Apr 2006

GMR-01

4-115

Reparenting a BSS to a different RXCDR (same OMC-R)

Chapter 4: Configuring a BSS/RXCDR

Procedure 4-38 1 2 3 4

Reparent a BSS to a different RXCDR when using the Map feature

If using the Map feature, first complete all steps in Procedure 4-37. 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.

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 will now contain link information for the newly parented RXCDR. This is done using the procedure described in step 4 above. 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-12 for the procedure on adding links between the BSS and the new RXCDR for relevant user-defined maps. The default network map will have been modified. The map nodes will not have been deleted and re-added, so the node positioning is correct. Only the map links will have changed. Follow the procedure described in step 4 above, to extract the new information for the network map. Log out from the system processor by typing: logout

10

11

12

4-116

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Reparenting an RXCDR to a different MSC

Reparenting an RXCDR to a different MSC


Introduction to reparenting an RXCDR to different a 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 the links between the RXCDR and original MSC have been disconnected, by liaising with the BSS field engineer. Ensure 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 Signalling Information grouping. Verify that calls are going to the MSC.

68P02901W17-R 14 Apr 2006

GMR-01

4-117

Reparenting an RXCDR to a different MSC

Chapter 4: Configuring a BSS/RXCDR

Reparenting RXCDR commslinks


Carry out the following procedure to move an RXCDR: Procedure 4-39 1 2 3 Reparent a RXCDR commslink

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.

4 5 6

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 will now contain new link information for the RXCDR. Log out from the system processor: logout

4-118

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Checking the software version for a BSS/RXCDR/OMC-R

Checking the software version for a BSS/RXCDR/OMC-R


Software version number format

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-40 1 2 3 Check software version of single NE

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.

Checking multiple NEs using the OMC-R GUI


To check the software version of multiple NEs, follow these steps:

68P02901W17-R 14 Apr 2006

GMR-01

4-119

Checking the software version for a BSS/RXCDR/OMC-R

Chapter 4: Configuring a BSS/RXCDR

Procedure 4-41 1

Check software version of multiple NEs

Click on 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.

4-120

GMR-01

68P02901W17-R 14 Apr 2006

Chapter

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-6. "Configuring a CommsLink using the OMC-R GUI" on page 5-11. "Checking RXCDR/BSS to OMC-R (OML) connectivity" on page 5-16. "DTE X.121 addresses at the OMC-R" on page 5-18 - 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-21. "Modifying configurations on A, M, and Mobis interfaces" on page 5-24.

68P02901W17-R 14 Apr 2006

GMR-01

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 usually tracked by engineering diagrams. They are not modelled 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.

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
{23683/28094}

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 NE BSS1015 BSS1015 BSS1015 Device MMS 1 0 MMS 1 0 MMS 1 1 Connected NE RXCDR-1 RXCDR-1 RXCDR-1 Device MMS 22 0 MMS 22 1 MMS 22 1

Connection name Conn 3:0 Conn 3:1 Conn 3:2

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.

5-2

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Checking BSS to MSC (Through RXCDR) connectivity

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 modelled at the OMC-R. To see how timeslots are configured, use the disp_mms_ts_usage command.

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/T1 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. It is recommended to 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-6. If the "Enhanced BSC Capacity" on page 2-99 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-11 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".

68P02901W17-R 14 Apr 2006

GMR-01

5-3

Checking BSS to MSC (Through RXCDR) connectivity

Chapter 5: Configuring Connectivity

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.

5-4

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Checking BSS to MSC (Through RXCDR) connectivity

To check BSS to RXCDR connectivity, proceed as follows: Procedure 5-1 Check BSS to RXCDR connectivity 1 2 Create a job order to associate each BSS with RXCDR. Using the Navigation Tree, create a new Assoc_BSS object for each connection (see "Configuring an Assoc_BSS" on page 4-75). 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-R 14 Apr 2006

GMR-01

5-5

Configuring a Conn_Link

Chapter 5: Configuring Connectivity

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. To do this, follow these steps: Procedure 5-2 1 Create Conn_Link using the OMC-R GUI

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-35 for further details. The network object class button changes colour. 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.

2 3 4 5

5-6

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a Conn_Link

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.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

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 Brief description See Table 4-1 description. See Table 3-1 description. See Table 4-1 description. The id of the Associated RXCDR. Click to display the parent Assoc_RXCDR Detailed View. Values Default is Conn_Link. 0 to 26. Mandatory or Optional?

Field name RDN Class RDN Instance NMC RDN Value Parent Detailed View

Additional Information
Use the Additional Information window to input any notes relating to this Conn_Link. Where additional notes are not required, it is advisable to close this field by clicking on 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.

68P02901W17-R 14 Apr 2006

GMR-01

5-7

Configuring a Conn_Link

Chapter 5: Configuring Connectivity

Table 5-3

Conn_Link Detailed View fields - Connectivity Information grouping Brief description Identifier of the container RXCDR. Identifier of the BSS connected to the RXCDR through this Conn_Link. 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. The remote MMS id for the XBL connectivity, that is, the MMS id of the site between which the Conn_link is being created. Id of the connected Associated RXCDR. Values Mandatory or Optional? Mandatory. Mandatory.

Field name RXCDR BSS

Local MMS

Mandatory.

Remote MMS

Mandatory

Connected Associated RXCDR

Mandatory.

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

5-8

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a Conn_Link

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.

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.

The add_conn command can also be used outside of SYSGEN. This command allows the operator to specify the E1/T1 connectivity information identifying which RXCDR is associated with the E1/T1 link and the device identity within the RXCDR to which the E1/T1 link is connected. This connectivity information must be specified for each E1/T1 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.

68P02901W17-R 14 Apr 2006

GMR-01

5-9

Configuring a Conn_Link

Chapter 5: Configuring Connectivity

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

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.

5-10

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a CommsLink using the OMC-R GUI

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

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.

68P02901W17-R 14 Apr 2006

GMR-01

5-11

Configuring a CommsLink using the OMC-R GUI

Chapter 5: Configuring Connectivity

Procedure
To create a CommsLink using the OMC-R GUI, use the following procedure: Procedure 5-3 1 Create a CommsLink using the OMC-R GUI

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-35 for further details. The network object class button changes colour. Click on 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 on 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 will be recorded as node A in the Node A field. Repeat step 5 for Node B at the other end of the CommsLink. Once all the above information has been input to the Detailed view 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.

3 4 5

6 7 8

5-12

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a CommsLink using the OMC-R GUI

Figure 5-1

CommsLink List showing GPRS links

CommsLink Detailed View fields


The following sections list and briefly describe the parameter fields in the CommsLink Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

68P02901W17-R 14 Apr 2006

GMR-01

5-13

Configuring a CommsLink using the OMC-R GUI

Chapter 5: Configuring Connectivity

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 Brief description The name of the CommsLink. 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. 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. 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. Values Mandatory or Optional? Mandatory. Mandatory.

Field name Name Node A

Node B

Mandatory.

Parent Detailed View

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 Brief description The state of a node or link on a map. Values INS, OOS or Unknown. Mandatory or Optional? Optional.

Field name Service State

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 will grow to a large number. This will make finding a particular link difficult when sites are being modified and the CommsLink Detailed View is to be edited. The filtering feature can be used to help.

5-14

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a CommsLink using the OMC-R GUI

To filter for links between two nodes, proceed as follows: Procedure 5-4 1 Apply filter for links between two nodes

From the Navigation Tree, click on the folder icon next to the CommsLink type button. The CommsLink list is displayed. Click on the Node A button. The Navigation Tree is displayed. Double-click on one of the nodes that is attached to one end of the link to be accessed. Click on the Node B button. The Navigation Tree is redisplayed. Double-click on the node that is attached to the other end of the link to be accessed. Click on the Apply Filter button.

2 3 4 5 6

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 1 Delete a Commslink using the OMC-R GUI

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-35 for further details. The network object class button changes colour. Click on 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.

2 3 4 5

68P02901W17-R 14 Apr 2006

GMR-01

5-15

Checking RXCDR/BSS to OMC-R (OML) connectivity

Chapter 5: Configuring 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-170.

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 1 2 3 Check OMLs for a single NE using the GUI

Open a Navigation Tree to show OMLs (BSS - SITE - <Site:0> - Logical links - OML). Check number of configured OMLs. There will usually be 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 utilisation of the dual OML feature which speeds up software downloads.

5-16

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Checking RXCDR/BSS to OMC-R (OML) connectivity

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: Procedure 5-7 1 Check OMLs for multiple NEs using SQL

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

2 3

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 will contain all the data for analysis or further parsing.

68P02901W17-R 14 Apr 2006

GMR-01

5-17

DTE X.121 addresses at the OMC-R

Chapter 5: Configuring Connectivity

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 should not need to be altered. When new network elements are added, the new addresses of the network elements need to be 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.

5-18

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

DTE X.121 addresses at the OMC-R

x25_config file fields


Each line in this file contains eleven fields, each separated by a space. The fields are: <record no.> <x25 chan. no.> Record number within the file. X.25 channel number (specified as x25_chan<channel 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. 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. Interface identifier (used for internal software purposes). It is H for Sunlink HSI. 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. 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 being used by a process. The only valid value in this field is X.25. Packet size. Window size. Timeout value.

<link number>

<x121 app.

addr.>

<internal instance> <proc. call char>

<app.

process>

<protocol> <packet size> <window size> <timeout parameter>

68P02901W17-R 14 Apr 2006

GMR-01

5-19

DTE X.121 addresses at the OMC-R

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 .

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


x25 Channel Number

2 3 0 1 0 2 3

26800623010061 26800623011062 26800623010141 26800623011142 26800623010200 26800623011299 26800623011299


x121 Application address

H H H H H H H

g_bootload g_bootload g_ei g_ei -

OMC_BL OMC_BL OMC_EI OMC_EI OMC_RL OMC_PU OMC_PU

X25 X25 X25 X25 X25 X25 X25

128 128 128 128 128 128 128


Packet Size

2 2 2 2 2 2 2

50 50 500 500 500 50 50

Record Number

}
Link Number
5-20

GMR-01

Process Calchar

Application Process

Time out Parameter

Internal Instance Identifier

Protocol

Window Size

ti-GSM-SC01W17-000052-eps-sw

68P02901W17-R 14 Apr 2006

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

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 will use link number 0 by default, if this is not available then it will use link number 1, if this link does not work it will use 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 0 1 2 3 RXCDR (slot: port) 10:0 10:1 8:0 *10:0 (*denotes cage 2) BSS (slot: port) 16:0 16:1 14:0 *16:0 (*denotes cage 2)

68P02901W17-R 14 Apr 2006

GMR-01

5-21

Assigning DTE X.121 addresses at the NE

Chapter 5: Configuring Connectivity

Setting OML addresses using the TTY interface


Set the OML(s) DTE addresses (0 to 3) with reference to Table 5-6. Procedure 5-8 1 Set OML(s) DTE addresses

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.

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

5-22

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Assigning DTE X.121 addresses at the NE

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. 13 and 14 identify the address usage, and are generally allocated as follows: 41 42 61 62 99 00 Event/alarm Interface Event/alarm interface Download/Bootload Download/Bootload Upload Rlogin

68P02901W17-R 14 Apr 2006

GMR-01

5-23

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 signalling link is the link between the MSC and the RXCDR. The M interface signalling link is the link between the RXCDR and the BSC. The Mobis interface signalling 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 Signalling 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

The following have to be noted when modifying interfaces: 1. Prior to 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. 2. 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.

5-24

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Modifying configurations on A, M, and Mobis interfaces

Full details of the syntax for these TTY commands can be found in: Technical Description: BSS Command Reference (68P02901W23).

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

Reserving a timeslot
Timeslots on specified E1/T1 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:

68P02901W17-R 14 Apr 2006

GMR-01

5-25

Modifying configurations on A, M, and Mobis interfaces

Chapter 5: Configuring Connectivity

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 1 2 Reserve a timeslot

Remotely login to the BSS and change security levels, see "Remotely logging in to a BSS site from the OMC-R" on page 1-46. 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 1 2 Free a timeslot at the same site

Remotely login to the BSS and change security levels, see "Remotely logging in to a BSS site from the OMC-R" on page 1-46. 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 1 2 Free a timeslot between different sites

Remotely login to the BSS and change security levels, see "Remotely logging in to a BSS site from the OMC-R" on page 1-46. Enter the following command: chg_ts_usage free_path 3 0 0 1 0 5 3 0 1 7 1

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.

5-26

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Modifying configurations on A, M, and Mobis interfaces

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 1 2 Nail a timeslot

Remotely login to the BSS and change security levels, see "Remotely logging in to a BSS site from the OMC-R" on page 1-46. 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 1 2 Nail a path

Remotely login to the BSS and change security levels, see "Remotely logging in to a BSS site from the OMC-R" on page 1-46. Enter the following command: chg_ts_usage nail_path 3 0 0 1 0 5 3 0 1 7 1

68P02901W17-R 14 Apr 2006

GMR-01

5-27

Modifying configurations on A, M, and Mobis interfaces

Chapter 5: Configuring Connectivity

This page intentionally left blank.

5-28

GMR-01

68P02901W17-R 14 Apr 2006

Chapter

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-7. "Configuring a PCU using the OMC-R GUI" on page 6-11. "Displaying and modifying PCU cabinet details" on page 6-21. "Displaying and modifying PCU cage details" on page 6-22. "Configuring a DPROC using the OMC-R GUI" on page 6-23. "Displaying and modifying PSP details" on page 6-27. "Configuring a PCU MSI using the OMC-R GUI" on page 6-30. "Displaying and modifying PCU MMS details" on page 6-34. "Configuring a GDS using the OMC-R GUI" on page 6-36. "Configuring a GSL using the OMC-R GUI" on page 6-40. "Configuring a GBL using the OMC-R GUI" on page 6-44. "Configuring a GSL using the OMC-R GUI" on page 6-40. "Configuring an SGSN (GPRS) using the OMC-R GUI" on page 6-58. "Configuring the PCU and its devices from the TTY interface" on page 6-61.

68P02901W17-R 14 Apr 2006

GMR-01

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. This 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 to 2. PCUs and SGSN are visible in the OMC-R GUI once they have been configured.

6-2

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Introduction to the PCU and its devices

List of PCU contained devices


A PCU has the following contained devices: Hardware devices: Cabinet. Cage. Processors: MSI: MMS. DPROC (types: PICP and PRP). PSP.

Logical Links: GDS (types: TRAU and LAPD) GSL GBL NSVC

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, and an MMS is automatically created when an MSI is created using the TTY or GUI interface.

68P02901W17-R 14 Apr 2006

GMR-01

6-3

Introduction to the PCU and its devices

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)

DPROC (PRP)

MSI

MSI

MMS2

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.

6-4

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Introduction to the PCU and its devices

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

68P02901W17-R 14 Apr 2006

GMR-01

6-5

Introduction to the PCU and its devices

Chapter 6: Configuring a PCU for GPRS

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 PCU contained devices Contained device Data Processor PCU System Processor GPRS Data Stream GPRS Signalling Link Multiple Serial Interface board Gb Link Network Service Virtual Connection Device acronym DPROC. PSP. GDS. GSL. MSI. GBL. NSVC.

None of the contained devices can be equipped unless the containing PCU has been equipped.

6-6

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Overview of configuring a PCU and its devices

Overview of configuring a PCU and its devices


Configuring the 3x PCU feature


PCU redundancy
A single BSC can manage up to three PCUs. This means that a BSC can manage zero to three PCUs. However, the PCUs cannot communicate directly with each other. This configuration creates a fault recovery system referred to as PCU redundancy. PCU redundancy can be switched on or off for all PCUs at a BSS using the pcu_redundancy parameter field in the GPRS grouping of the BSS Detailed View. When redundancy is off and a PCU goes OOS, the primary cells on that PCU are not moved to another PCU. Consequently the GPRS feature of the affected cells will not be available.

Defining PCU rating


When PCU redundancy is switched on for a BSS, cells are serviced by a PCU as follows: Primary PCU A Primary PCU is the home PCU for a cell and is the PCU to which a cell is first mapped. When more than one PCU is equipped at the BSS, a Primary PCU must be specified for each cell where GPRS is enabled. To do this use the Primary PCU field (primary_pcu) in the GPRS section of the CELL Detailed View. First Redundant PCU When more than one PCU is equipped at a BSS, a first (and second) redundant PCU for each PCU can be specified. If the Primary PCU goes out-of-service (OOS), the cells mapped to the Primary PCU are remapped to the First Redundant PCU specified for the OOS PCU. When the Primary PCU for a cell comes back in-service, the cell is mapped back to the Primary PCU. The First Redundant PCU for a PCU is specified using the 1st Redundant For PCUx field (pcu_red_map_x1) in the GPRS grouping of the BSS Detailed View, where x can be 0, 1 or 2. Second Redundant PCU When three PCUs are equipped at a BSS, a second redundant PCU can be equipped for each PCU. If the First Redundant PCU goes OOS, the cells are remapped to the Second Redundant PCU. When either the Primary or First Redundant PCU comes back in-service, the cells are mapped back to the Primary or First Redundant PCU. When both the Primary and First Redundant PCUs come back in-service, the cells are mapped back to the Primary PCU. The Second Redundant PCU for a PCU is specified using the 2st Redundant For PCUx field (pcu_red_map_x2) in the GPRS grouping of the BSS Detailed View, where x can be 0, 1 or 2. Cells can be mapped to specific PCUs, and Redundant PCUs can be specified using either the OMC-R GUI or the TTY interface. The 3x PCU feature is described in detail in Technical Description: BSS Implementation (68P02901W36). 68P02901W17-R 14 Apr 2006 6-7

GMR-01

Overview of configuring a PCU and its devices

Chapter 6: Configuring a PCU for GPRS

Displaying cells mapped to a PCU


The PCU Detailed View can be used to show all cells currently mapped to the PCU. To display the cells currently mapped to a PCU using the TTY interface, use the disp_cell_map command. For example, the following command displays cell mapping for PCU 1 and 2: disp_cell_map PCU_1 PCU_2

A PCU Detailed View does display all cells currently mapped to this PCU but the Detailed View needs to closed and re-opened to correctly display an updated list. So for instance, when a cell is moved to its first redundant PCU, it will not be listed in the redundant PCU Detailed View immediately. But if the PCU Detailed View is closed and re-opened, the new Cell will be seen in the list. The system responds by displaying the cell ids and their GPRS status. The following command displays the current PCU mapping for an individual cell (cell 0010114): disp_cell_map 0 0 1 0 1 1 4 The system responds by displaying the current PCU site id.

Recommended method for configuring a PCU


The recommended method for configuring a PCU is to: 1. 2. Install the PCU equipment. 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-61 for guidance. Load the batch_rlogin script file into the BSS database. Run an audit at the OMC-R. The PCU and its devices then appear in the OMC-R GUI Navigation Tree.

3. 4.

Creating a batch_rlogin script file is also recommended for creating a BTS.

6-8

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Overview of configuring a PCU and its devices

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-11. 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-61. 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-61.

Locking, unlocking, and other event and fault management activities are described in: OMC-R Online Help, Network Operations.

68P02901W17-R 14 Apr 2006

GMR-01

6-9

Overview of configuring a PCU and its devices

Chapter 6: Configuring a PCU for GPRS

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 (see"Configuring a PCU using the OMC-R GUI" on page 6-11) or the equip command (see "Configuring the PCU and its devices from the TTY interface" on page 6-61). Create an SGSN using the Navigation Tree (see "Configuring an SGSN (GPRS) using the OMC-R GUI" on page 6-58). If required, modify any PCU Cabinet details, see "Displaying and modifying PCU cabinet details" on page 6-21. If required, modify any PCU Cage details, see "Displaying and modifying PCU cage details" on page 6-22. Create a DPROC, see "Configuring a DPROC using the OMC-R GUI" on page 6-23 or "Configuring the PCU and its devices from the TTY interface" on page 6-61. Modify a PSP, see "Displaying and modifying PSP details" on page 6-27 or "Configuring the PCU and its devices from the TTY interface" on page 6-61. Create an MSI, see "Configuring a PCU MSI using the OMC-R GUI" on page 6-30 or "Configuring the PCU and its devices from the TTY interface" on page 6-61. Create an MMS, see "Displaying and modifying PCU MMS details" on page 6-34 or "Configuring the PCU and its devices from the TTY interface" on page 6-61. Create a GDS, see "Configuring a GDS using the OMC-R GUI" on page 6-36 or "Configuring the PCU and its devices from the TTY interface" on page 6-61. Create a GSL, see "Configuring a GSL using the OMC-R GUI" on page 6-40 or "Configuring the PCU and its devices from the TTY interface" on page 6-61. Create a GBL, see "Configuring a GBL using the OMC-R GUI" on page 6-44 or "Configuring the PCU and its devices from the TTY interface" on page 6-61. Create an NSVC, see "Configuring an NSVC using the OMC-R GUI" on page 6-51 or "Configuring the PCU and its devices from the TTY interface" on page 6-61.

2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12.

6-10

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a PCU using the OMC-R GUI

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-22. Cabinet, see "Displaying and modifying PCU cabinet details" on page 6-21. PSP 0 and PSP 1, see "Displaying and modifying PSP details" on page 6-27.

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.

68P02901W17-R 14 Apr 2006

GMR-01

6-11

Configuring a PCU using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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 1 Add a PCU to the network using the OMC-R GUI

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-35 for further details. The PCU class button changes colour. Select Edit - Create from the menu bar. The OMC-R displays the PCU Detailed View in Create mode. 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.

2 3 4 5

PCU Detailed View fields


The following sections list and briefly describe the parameter fields in the PCU Detailed View according to their parameter grouping.

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 on that field. A context sensitive help page is displayed.

The PCU Detailed View shows all cells that are currently mapped to the PCU.

6-12

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a PCU using the OMC-R GUI

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 Brief description 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. See description in Table 4-1. See description in Table 3-1. See description in Table 4-1. Click to display the parent BSS Detailed View. Values Up to 31 characters. Format of an auto-generated PCU name is: <BSSname>:PCU-0. Default is PCU. 0 to 2. Default is 0. Mandatory or Optional? Mandatory.

Field name Name

RDN Class RDN Instance NMC RDN Value Parent Detailed View

Additional Information
Use the Additional Information window to input any notes relating to this PCU. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

68P02901W17-R 14 Apr 2006

GMR-01

6-13

Configuring a PCU using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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 Brief description The number of alarms in this level. The number of alarms in this level. The number of alarms in this level. The number of alarms in this level. Each step is 100 milliseconds. The number of alarms in this level. The number of alarms in this level. The number of alarms in this level. The number of alarms in this level. Each step is 100 milliseconds. Values 0 - 65535. Default is 16. 0 - 65535. Default is 20. 0 - 65535. Default is 511. 0 - 65535. Default is 25. 0 - 65535. Default is 600. 0 - 65535. Default is 16. 0 - 65535. Default is 20. 0 - 65535. Default is 511. 0 - 65535. Default is 25. 0 - 65535. Default is 600. Mandatory or Optional? Mandatory. Mandatory. Mandatory. Mandatory. Mandatory. Mandatory. Mandatory. Mandatory. Mandatory. Mandatory.

Field name MSI Remote Loss Daily Alarm Level MSI Remote Loss Hourly Alarm Level MSI Remote Loss OOS Alarm Level MSI Remote Time OOS Alarm Level MSI Remote Time Restoral Time MSI Sync Loss Daily Alarm Level MSI Sync Loss Hourly Alarm Level MSI Sync Loss OOS Alarm Level MSI Sync Loss Time OOS Alarm Level MSI Sync Loss Restoral Time (time)

6-14

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a PCU using the OMC-R GUI

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 Brief description The guard timer used for cell blocking and unblocking procedures with the SGSN. The guard timer used during Reset procedures with the SGSN (BSSGP T2). Number of retries for a cell block message to the SGSN. Number of retries for a cell unblock message to the SGSN. Number of retries for a cell reset message to the SGSN. Configures flow control frequency from the PCU to the SGSN. Number of retries the BSS generates for RA-Capability-Update messages to the SGSN. Values 1 - 120 Seconds. Default is 3. 1 - 120 Seconds. Default is 60. 1 - 3. Default is 3. 1 - 3. Default is 3. 1 - 3. Default is 3. 1 - 1000 tenths of seconds. Default is 10. 1 - 3. Default is 3. Mandatory or Optional? Mandatory.

Field name T1 (Un)Blocking Guard Timer T2 Reset Guard Timer

Mandatory.

Cell Block Retry Messages Cell Unblock Retry Messages Cell Reset Retry Messages Flow Control Period

Mandatory. Mandatory. Mandatory. Mandatory.

RA Capability Update Retries

Mandatory.

68P02901W17-R 14 Apr 2006

GMR-01

6-15

Configuring a PCU using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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 Brief description The signalling BSSGP Virtual Connection Identifier (BVCI) for the BSS. Cannot be modified if CELL gprs_enabled is Enabled (1) for any cells in the BSS. Values 0 - 65535. Mandatory or Optional? Mandatory.

Field name/ parameter name Signalling BVCI

Network Operation Whether a GS is present between Mode the MSC and the SGSN. (OMC-R parameter name: gprs_net_op_mode BSS parameter name: gprs_network_operation_mode)

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 - the network sends CS pages for a GPRS attached mobile on the CCCH and PS pages on the PCCCH, if allocated. Default is 3. Cannot be set to a value of 2.

Mandatory.

6-16

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a PCU using the OMC-R GUI

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 Brief description The time period used to compute GBL_UL_DATA_ THRPUT and GBL_DL_DATA_ THRPUT statistics. Number of samples used to compute the GBL_UL_DATA_ THRPUT statistics. Number of samples used to compute the GBL_DL_DATA_ THRPUT statistics. The type of connection wanted for the TELCO connection. Values 1 - 255 (10ths of a second). Default is 50. 1 - 10. Default is 10. 1 - 10. Default is 10. 0 or 1. For CEPT(E1): Timeslot 0 multiframe (CRC is on) (0), No timeslot 0 multiframe (CRC is off) (1). For T1: ESF (0), D3/D4 (1). Default is 0. Mandatory or Optional? Mandatory.

Field name/ parameter name GBL Throughput Period

GBL Uplink Throughput Samples GBL Downlink Throughput Samples PCU MMS Configuration Type

Mandatory.

Mandatory.

Mandatory.

68P02901W17-R 14 Apr 2006

GMR-01

6-17

Configuring a PCU using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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 Brief description Guards the NS-VC blocking and unblocking. Guards the NS-VC reset procedure. The period of NS-VC test procedure. Guards the NS-VC test procedure. The number of retries when attempting to block an NS-VC. The number of retries when attempting to unblock an NS-VC. The number of retries generated when establishing whether an NS-VC is alive. The period during which the PCU attempts to reset a NS-VC. The NSEI used by the PCU over the Gb Interface. Values 1 - 30 (Seconds). Default is 3. 1 - 120 (Seconds). Default is 40. 1 - 60 (Seconds). Default is 30. 1 - 30 (Seconds). Default is 3. 1 - 3. Default is 3. 1 - 3. Default is 3. 1 - 10. Default is 3. 1 - 250 (Seconds). Default is 125. 0 to 65535. Mandatory or Optional? Mandatory. Mandatory. Mandatory. Mandatory. Mandatory. Mandatory. Mandatory.

Field name NSVC (Un)Block Guard Timer NSVC Reset Guard Timer NSVC Test Period NSVC Test Guard Timer NSVC Block Retry Messages NSVC Unblock Retry Messages NSVC Alive Retry Messages NSVC Reset Period Network Service Entity Identifier nsei

Mandatory. Mandatory.

6-18

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a PCU using the OMC-R GUI

Map Information grouping


Standard map information fields, see Table 4-15 for details.

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 Brief description 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-51. 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-51. 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-51. Values 0.0.0.0 to 223.255.255.255. Default: 127.0.0.1. Mandatory or Optional? Optional.

Field name/ parameter name IP Address ip_address

Subnet Mask subnet_mask

0.0.0.0 to 255.255.255.255. Default: 255.255.255.255. 0.0.0.0 to 223.255.255.255. Default: 127.0.0.1.

Optional.

Router IP Address router_ip_address

Optional.

Quality of Service (QoS) grouping


{23956} See "Quality of Service (QoS)" on page 2-171 for further details of the PCU parameters in this grouping.

68P02901W17-R 14 Apr 2006

GMR-01

6-19

Configuring a PCU using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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

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

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.

6-20

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Displaying and modifying PCU cabinet details

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-60 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-41. The Cabinet Detailed View fields are described in "Configuring a cabinet" on page 4-60. Some PCU cabinet fields cannot be modified and are set by the OMC-R, for example: Type: PCU RdnInstance

68P02901W17-R 14 Apr 2006

GMR-01

6-21

Displaying and modifying PCU cage details

Chapter 6: Configuring a PCU for GPRS

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-65 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-41. The Cage Detailed View fields are described in "Configuring a cage" on page 4-65.

6-22

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a DPROC using the OMC-R GUI

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. 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 will contain the information needed by the PICP for link control. See Technical Description: BSS Command Reference (68P02903W18) 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.

68P02901W17-R 14 Apr 2006

GMR-01

6-23

Configuring a DPROC using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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 1 Add a DPROC to the network using the OMC-R GUI

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-35 for further details. The DPROC class button changes colour. 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.

2 3 4 5

DPROC Detailed View fields


The following sections list and briefly describe the parameter fields in the DPROC Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

6-24

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a DPROC using the OMC-R GUI

Identification grouping
Table 6-9 describes the fields in the Identification grouping of the DPROC Detailed View. Table 6-9 DPROC Detailed View fields - Identification grouping Brief description The functionality to be performed by the DPROC. See the description in Table 4-1. See the description in Table 3-1. When creating the first device or function for the PCU, the default value is unique and will not need to be changed. See the description in Table 4-1. Displays the name of the parent site (PCU). Click to display the parent PCU Detailed View. Identifier unique to the PCI Device Vendor. Identifier unique to the PCI Device. The revision number of the PCI device. Optional. Optional. Optional. Values PRP (1) or PICP (2). Default is 1. Default is DPROC. 1 to 6 or 11 to 16. Default is 0. Mandatory or Optional? Mandatory.

Field name DPROC Type

RDN Class RDN Instance

NMC RDN Value Parent Detailed View

PCI Vendor ID PCI Device ID PCI Device Revision

Additional Information
Use the Additional Information window to input any notes relating to this device. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

68P02901W17-R 14 Apr 2006

GMR-01

6-25

Configuring a DPROC using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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-41. The following fields cannot be modified: DPROC Type. RDN class. RdnInstance. PCI Vendor ID. PCI Device ID. PCI Device Revision.

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

6-26

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Displaying and modifying PSP details

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. These values cannot be changed by a user. 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 1 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-35 for further details. The PSP instance button changes colour. See the general procedure in "Modifying a network object using the OMC-R GUI" on page 1-41. The OMC-R displays the PSP Detailed View in Monitor mode. See PSP Detailed View fields for details.

68P02901W17-R 14 Apr 2006

GMR-01

6-27

Displaying and modifying PSP details

Chapter 6: Configuring a PCU for GPRS

PSP Detailed View fields


The following sections list and briefly describe the parameter fields in the PSP Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

Identification grouping
Table 6-10 describes the fields in the Identification grouping of the PSP Detailed View. Table 6-10 PSP Detailed View fields - Identification grouping Brief description See description in Table 4-1. The PSP Identifier field. Also see description in Table 3-1. See description in Table 4-1. Displays the parent PCU name. Click to display the parent PCU Detailed View. See description in Table 6-9. See description in Table 6-9. See description in Table 6-9. Optional. Optional. Optional. Values Default is PSP. 0 or 1. Default is 0. Mandatory or Optional?

Field name RDN Class RDN Instance NMC RDN Value Parent Detailed View

PCI Vendor ID PCI Device ID PCI Device Revision

6-28

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Displaying and modifying PSP details

Cage and Slot Information grouping


Table 6-11 describes the fields in the Cage and Slot Information grouping of the PSP Detailed View. Table 6-11 PSP Detailed View fields - Cage and Slot Information grouping Brief description 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.

Field name PCU Slot

Additional Information
Use the Additional Information window to input any notes relating to this PSP. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

68P02901W17-R 14 Apr 2006

GMR-01

6-29

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 a MSI to a PCU using the OMC-R GUI, follow these steps: Procedure 6-4 1 Add a MSI to a PCU using the OMC-R GUI

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-35 for further details. The MSI class button changes colour. 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.

2 3 4 5

6-30

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a PCU MSI using the OMC-R GUI

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.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

Identification grouping
Table 6-12 describes the fields in the Identification grouping of the PCU MSI Detailed View. Table 6-12 PCU MSI Detailed View fields - Identification grouping Brief description The MSI device type. Values Default is MSIE1_PMC (14). Only available if BSS gprsOpt is enabled (1). Default is MSI. 0 or 1. Default is 0. Mandatory or Optional? Mandatory.

Field name/ parameter name MSI Type msi_type

RDN Class RDN Instance NMC RDN Value Parent Detailed View

See description in Table 4-1. See description in Table 3-1. See description in Table 4-1. Displays the parent PCU name. Click to display the parent PCU Detailed View.

68P02901W17-R 14 Apr 2006

GMR-01

6-31

Configuring a PCU MSI using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Cage and Slot Information grouping


Table 6-13 describes the fields in the Cage and Slot Information grouping of the PCU MSI Detailed View. Table 6-13 PCU MSI Detailed View fields - Cage and Slot Information grouping Brief description The unique id of the DPROC where the MSI resides. Only valid if msi_type is MSI-E1_PMC. The socket on the DPROC on which the MSI resides. Only valid if msi_type is MSI-E1_PMC. Values The default is null. Mandatory or Optional? Optional.

Field name Data Processor

Data Processor Socket

Socket 1 or Socket 2. Default is Socket 1.

Optional.

Additional Information
Use the Additional Information window to input any notes relating to this device. Where additional notes are not required, it is advisable to close this field by clicking on 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-41. The following MSI fields cannot be changed: Data Processor. Data Processor Socket.

6-32

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a PCU MSI using the OMC-R GUI

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 an 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-44.

68P02901W17-R 14 Apr 2006

GMR-01

6-33

Displaying and modifying PCU MMS details

Chapter 6: Configuring a PCU for GPRS

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 a MSI under a PCU (and can also be a child of an MSI under a site). A PCU MSI cannot be created or deleted by a user 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.

6-34

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Displaying and modifying PCU MMS details

Prerequisites to viewing and modifying a PCU MMS


Before a PCU MMS details can be viewed or modified: A PCU must exist. A MSI must exist.

Displaying and modifying a MMS Detailed View


To display and modify details for a PCU MMS using the Navigation Tree, follow these steps: Procedure 6-5 1 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-35 for further details. The MSI instance button changes colour. See the general procedure in "Modifying a network object using the OMC-R GUI" on page 1-41.

Monitoring timeslot usage on MMS link


To monitor timeslot usage on an MMS link, see "Displaying Channel and Circuit Status" on page 9-21.

68P02901W17-R 14 Apr 2006

GMR-01

6-35

Configuring a GDS using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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 two types of GDS: Transcoder Rate Adaption Unit (TRAU). This carries the GPRS traffic and is the default type. Link Access Protocol Data (LAPD) This carries the GPRS signalling link (GSL). A GDS created on a MSI, which was created on a PRP DPROC, can only support TRAU. A TRAU type GDS can only be created, if it is terminated on an MSI equipped on a PRP DPROC.

A TRAU type GDS creation will fail if it is terminated on an MSI equipped on a PICP DPROC and an appropriate message will be displayed. 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.

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 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 on either OK or Cancel to continue the FM activity, or cancel to abandon the FM activity.

6-36

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a GDS using the OMC-R GUI

Prerequisites to creating a GDS


Before creating a GDS, the following must exist: PCU. DPROC. MSI and a child MMS.

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 1 Add a GDS to the network using the OMC-R GUI

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-35 for further details. The GDS class button changes colour. Select Edit - Create from the menu bar. The OMC-R displays the GDS Detailed View in Create mode. 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.

2 3 4 5

GDS Detailed View fields


The following sections list and briefly describe the parameter fields in the GDS Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

Identification grouping
Table 6-14 describes the fields in the Identification grouping of the GDS Detailed View.

68P02901W17-R 14 Apr 2006

GMR-01

6-37

Configuring a GDS using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Table 6-14

GDS Detailed View fields - Identification grouping Brief description The function type of the GDS. Values TRAU (0) or LAPD (1). Default is 0. Default is GDS. 0 - 19. Mandatory or Optional? Mandatory.

Field name GDS Type

RDN Class RDN Instance NMC RDN Value Parent Detailed View

See description in Table 4-1. See description in Table 3-1. See description in Table 4-1. Displays the parent PCU name. Click to display the parent PCU Detailed View.

Additional Information
Use the Additional Information window to input any notes relating to this device. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

Connectivity Information grouping


Table 6-15 describes the fields in the Connectivity Information grouping of the GDS Detailed View. Table 6-15 GDS Detailed View fields - Connectivity Information grouping Brief description The identifier of the MMS at the BSS (SITE 0) end of the GDS link. The identifier of the MMS at the PCU end of the GDS link. Values Mandatory or Optional? Mandatory.

Field name BSC MMS

PCU MMS

Mandatory.

6-38

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a GDS using the OMC-R GUI

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-41. 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-44.

68P02901W17-R 14 Apr 2006

GMR-01

6-39

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 Signalling Link (GSL) is a child of a PCU. A GSL is used for signalling, communications to and from the BSC, and for loading code on to the PCU. A GSL can only be created on a LAPD type GDS. A maximum of 60 GSLs can be created for a PCU, and 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 and 2 LAPD GDSs can be equipped on a PICP DPROC). The first GSL created for a GDS uses timeslot 1 on the MMS. When a GSL is created the BSS ensures there are sufficient LCF resources to manage it. In 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-16 gives gsl_lcf_mapping details. Table 6-16 gsl_lcf_mapping Brief description 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.

Parameter name gsl_lcf_mapping

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

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a GSL using the OMC-R GUI

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 1 Add a GSL to the network using the OMC-R GUI

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-35 for further details. The GSL class button changes colour. 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.

2 3 4 5

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.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

68P02901W17-R 14 Apr 2006

GMR-01

6-41

Configuring a GSL using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Identification grouping
Table 6-17 describes the fields in the Identification grouping of the GSL Detailed View. Table 6-17 GSL Detailed View fields - Identification grouping Brief description See description in Table 4-1. See description in Table 3-1. See description in Table 4-1. Displays the parent PCU name. Click to display the parent PCU Detailed View. Identifier of the GDS on which this GSL resides. Cannot be modified. Determines the LCF to which the GSL is equipped. Only displayed when gsl_lcf_mapping is set to Manual, see Table 6-16 for details. 0 to 37. Mandatory. Values Default is GSL. 0 to 59. Mandatory or Optional? Optional.

Field name RDN Class RDN Instance NMC RDN Value Parent Detailed View

GDS Identifier

LCF Identifier

0 to 24.

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this device. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

State grouping
Standard network object state fields, see Table 6-22 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.

When the last GSL is locked, the PCU becomes OOS.

6-42

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring 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-44.

68P02901W17-R 14 Apr 2006

GMR-01

6-43

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 1 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-35 for further details. The GBL class button changes colour. 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.

2 3 4 5

6-44

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a GBL using the OMC-R GUI

GBL Detailed View fields


The following sections list and briefly describe the parameter fields in the GBL Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

68P02901W17-R 14 Apr 2006

GMR-01

6-45

Configuring a GBL 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 GBL Detailed View. Table 6-18 GBL Detailed View fields - Identification grouping Brief description 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). The last timeslot for the GBL on the span. Also see start_ts. See description in Table 4-1. See description in Table 3-1. See description in Table 4-1. Displays the parent PCU name. Click to display the parent PCU Detailed View. Values 1 to 31 (the timeslot number on the span). Mandatory or Optional? Mandatory.

Field name/BSS parameter name First GBL Timeslot start_ts.

Last GBL Timeslot end_ts. RDN Class. RDN Instance. NMC RDN Value. Parent Detailed View.

1 to 31 (the timeslot number on the span). Default is GBL. 0 - 3. The default is 0.

Mandatory.

6-46

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a GBL using the OMC-R GUI

Connectivity Information grouping


Table 6-19 describes the fields in the Connectivity Information grouping of the GBL Detailed View. Table 6-19 GBL Detailed View fields - Connectivity Information grouping Brief description The identifier of the MMS at the PCU end of the GBL. Cannot be modified. Values The default is 0. Mandatory or Optional? Mandatory.

Field name PCU MMS

Additional Information
Use the Additional Information window to input any notes relating to this device. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

State grouping
Standard network object state fields, see Table 4-2 for details.

68P02901W17-R 14 Apr 2006

GMR-01

6-47

Configuring a GBL using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Frame Relay Information grouping


Table 6-20 describes the fields in the Frame Relay Information grouping of the GBL Detailed View. Table 6-20 GBL Detailed View fields - Frame Relay Information grouping Brief description The value of the Frame Relay default link Integrity Verification Polling Timer in seconds. The value of the Frame Relay default polling Verification Timer in seconds. The Frame Relay default Full Status Polling Counter, specified as a number of polling cycles. The Frame Relay default value for Error Threshold Counter, specified as a number of errors. The Frame Relay default value for Monitored Events Counter, specified as a number of events. The Frame Relay Access rate specified in Kbps. Cannot be modified. Values 5-30. Default is 10. 5-30. Default is 15. 1-255. Default is 6. 1-10. Default is 3. 1-10. Default is 4. 64 - 1984 (Kbps in steps of 64). Default is 64. Mandatory or Optional? Mandatory.

Field name Link Integrity Timer T391 Polling Verification Timer T392 Full Status Polling Counter N391 Error Threshold Counter N392 Monitored Events Counter N393 NS Access Rate

Mandatory.

Mandatory.

Mandatory.

Mandatory.

Mandatory.

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

6-48

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring a GBL using the OMC-R GUI

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.

68P02901W17-R 14 Apr 2006

GMR-01

6-49

Configuring a GBL using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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 forms must be set to False (0) before the GBL can be deleted.

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

6-50

GMR-01

68P02901W17-R 14 Apr 2006

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


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

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.

68P02901W17-R 14 Apr 2006

GMR-01

6-51

Configuring an NSVC using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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 1 Add an NSVC to the network using the OMC-R GUI

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-35 for further details. The NSVC class button changes colour. Select Edit - Create from the menu bar. The OMC-R displays the NSVC Detailed View in Create mode.

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 4 5 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.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

Identification grouping
Table 6-21 describes the fields in the Identification grouping of the NSVC Detailed View.

6-52

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an NSVC using the OMC-R GUI

Table 6-21 Field name

NSVC Detailed View fields - Identification grouping Brief description The Data Link Connection Identifier on the GBL. The object identifier of the GBL. See description in Table 4-1. A unique NSVC identifier. When creating the first NSVC for the PCU the default value (0) will be unique and will not need to be changed. See description in Table 4-1. Displays the parent PCU name. Click to display the parent PCU Detailed View. Values 16 - 991. 0 to 11. Default is NSVC. 0 - 65535. The default is 0. Mandatory or Optional? Mandatory. Mandatory.

Data Link Connection Identifier GBL Identifier RDN Class NSVCI

NMC RDN Value Parent Detailed View

Additional Information
Use the Additional Information window to input any notes relating to this device. Where additional notes are not required, it is advisable to close this field by clicking on the toggle button next to the Additional Information header.

68P02901W17-R 14 Apr 2006

GMR-01

6-53

Configuring an NSVC using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

NS Information grouping
Table 6-22 describes the fields in the NS Information grouping of the NSVC Detailed View. Table 6-22 NSVC Detailed View fields - NS Information grouping Brief description The committed information rate in Kbps 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. Specifies burst rate in Kbps 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. Specifies burst rate in Kbps for this NSVC. The fields BS Burst Size and NS Burst Excess must not both have a value of 0. Values 0 - 1984. There is no default value. Mandatory or Optional? Mandatory.

Field name NS Committed Information Rate

NS Burst Size

0 - 1984. There is no default value.

Mandatory.

NS Burst Excess

0 - 1984. There is no default value.

Mandatory.

Modifying NSVC details from the OMC-R GUI


Introduction to modifying NSVC details
The BSS ensures that the last NSVC in the BSS may not be modified until all the GBLs have been locked.

The NSVC state of a PCU is only displayed after an Audit.

Prerequisites to modifying NSVC details


Before NSVC details can be modified, the GPRS Enabled field must be set 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:

6-54

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an NSVC using the OMC-R GUI

Procedure 6-10 1

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

3 4

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.) Select Edit - Edit from the menu bar of the NSVC Detailed View form. Cont.

68P02901W17-R 14 Apr 2006

GMR-01

6-55

Configuring an NSVC using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

Procedure 6-10 6

Modify NSVC details from the Navigation Tree (Continued)

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 will be 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.

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 on OK or Cancel as required. 8 Select File - Close from the menu bar to close the NSVC Detailed View.

6-56

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an NSVC using the OMC-R GUI

Deleting an NSVC using the OMC-R GUI


To delete an NSVC using the Navigation Tree, follow these steps: Procedure 6-11 1 Delete a 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-35 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 on OK to confirm the deletion. After a few seconds, the OMC-R deletes the NSVC from the NSVC List.

3 4 5

68P02901W17-R 14 Apr 2006

GMR-01

6-57

Configuring an SGSN (GPRS) using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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 1 Create a 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-35 for further details. The SGSN class button changes colour. 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.

2 3 4

6-58

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring an SGSN (GPRS) using the OMC-R GUI

SGSN Detailed View fields


The following sections list and briefly describe the parameter fields in the SGSN Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

Identification grouping
Table 6-23 describes the fields in the Identification grouping of the SGSN Detailed View. Table 6-23 SGSN Detailed View fields - Identification grouping Brief description Unique SGSN name. See description in Table 4-1. See description in Table 3-1. See description in Table 4-1. Click to display the parent Network Detailed View. Default is SGSN. Default is 0. Values Mandatory or Optional? Mandatory.

Field name Name RDN Class RDN Instance NMC RDN Value Parent Detailed View

Additional Information
Use the Additional Information window to input any notes relating to this SGSN. Where additional notes are not required, it is advisable to close this field by clicking on 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.

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

68P02901W17-R 14 Apr 2006

GMR-01

6-59

Configuring an SGSN (GPRS) using the OMC-R GUI

Chapter 6: Configuring a PCU for GPRS

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

6-60

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Configuring the PCU and its devices from the TTY interface

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): 1 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: 5 COMMAND ACCEPTED

192.168.53.254

Equipping a PCU device


The general form of the equip command for PCU devices is: equip PCU<_id> <device_id>

68P02901W17-R 14 Apr 2006

GMR-01

6-61

Configuring the PCU and its devices from the TTY interface

Chapter 6: Configuring a PCU for GPRS

Where _id is the PCU identifier (in the range 0 to 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).

6-62

GMR-01

68P02901W17-R 14 Apr 2006

Chapter

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-23. "Creating a SITE using the OMC-R GUI" on page 7-28. "Modifying SITE parameters" on page 7-36. "Equipping cabinets and cages at a remote BTS" on page 7-38. "Deleting and unequipping TCU/CTU cabinets" on page 7-41. "Extending an existing path to a new site using the TTY interface" on page 7-42. "GCLK synchronization" on page 7-45. "Barring calls at a site using the TTY interface" on page 7-56.

For full details on the design considerations of a BTS site, refer to System Information: BSS Equipment Planning (68P02900W21).

68P02901W17-R 14 Apr 2006

GMR-01

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/T1 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. At least one default RSL must be equipped. 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

MSC (SMLC)

MTL (LMTL) TRAFFIC

BSC

RSL RTF

BTS

TYPE 1 or 2 - LCF 0 to 16

7-2

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Introduction to BSC and BTS sites

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

A and B indicate parallel E1/T1 links


28 22 18 A B 14 8 2

29

23 BSC

30

24

10

31

25

19

15

11

32

26

20

16

12

Net02_4_14

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 no longer have to be 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-R 14 Apr 2006

GMR-01

7-3

Introduction to BSC and BTS sites

Chapter 7: Configuring a Site

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

The BTS will code load 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 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 those that are still available can be equipped.

7-4

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Introduction to BSC and BTS sites

MSI and RSL restrictions


MSI devices at a remote BTS have the following restrictions: A maximum of ten MSIs (numbered 0 to 9) may be equipped, which provides twenty MMS circuits. A site can have up to ten paths, the remaining MMS circuits are available for paths that terminate at other BTSs.

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.

68P02901W17-R 14 Apr 2006

GMR-01

7-5

Introduction to BSC and BTS sites

Chapter 7: Configuring a Site

Table 7-1

Default RSLs - Timeslots and Cages Cage 15 MSI Slot Number 16 16 14 14 16 MMS Group 0 1 0 0 Abis Timeslot Used 1 2 2 2

This table only applies to InCell BTS sites only. 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.

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 a Horizon II macro site. Table 7-3 identifies the default RSLs for a non Horizon II macro site.

Table 7-2

Default RSLs - Timeslots and Card frame for Horizon II macro Site Card frame A A NIU2 Number 0 0 0 Span 0 1 2 Timeslot Used 1 2 2

Table 7-3

Default RSLs - Timeslots and Card frame for non Horizon II macro Site Card frame A B NIU Number 0 0 0 Span 0 1 0 Timeslot Used 1 2 2

7-6

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Introduction to BSC and BTS sites

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

An important concept relating to RTF paths is that whenever there are two paths equipped, the shortest path (fewer intervening BTS sites) will be used. For example, if the secondary path is shorter after being added or changed, it will be 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.

RSL/TCH and BSC-BTS dynamic allocation considerations


If the RSL at a BTS is set to use 16 Kbps (SITE parameter: rsl_rate) and ts_sharing is enabled at the BTS, the remaining three 16 Kbps TCHs on the 64 Kbps 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 Kbps 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 Kbps RSL and BTS2 has 64 Kbps 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 Kbps and BTS2 cannot use the three TCHs from the 16 Kbps RSL at BTS1.

900/1800 Horizonmicro2 and Horizoncompact2 BTS


Overview
The BTS equipment models available are: Horizonmicro2. Horizoncompact2.

68P02901W17-R 14 Apr 2006

GMR-01

7-7

Introduction to BSC and BTS sites

Chapter 7: Configuring a Site

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.

Horizonmicro2 and Horizoncompact2 configuration


This BTS consists of a master BTS device, and one or two slave BTS devices. At an 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/T1 lines terminate at the master Horizonmicro2 and Horizoncompact2, so a device determines whether it is a master or a slave according to whether or not it has a E1/T1 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,

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 required) the slave. See "Equipping cabinets and cages at a BSS site" on page 4-57 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-61 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-66 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: CTU2 radio Horizon II macro BTS cabinet hardware

7-8

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Introduction to BSC and BTS sites

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-66 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. 900 or 1800 MHz.

68P02901W17-R 14 Apr 2006

GMR-01

7-9

Introduction to BSC and BTS sites

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. Each CTU2 FRU can support two independent carriers simultaneously, therefore up to 12 carriers can be supported in a Horizon II macro cabinet. 900 and 1800 MHz cabinets. Support of MCUF functionality with the H2SC.

The H2SC is not backward compatible with MCU/MCUF and cannot be used as a direct replacement for a MCU(F) in a Horizon 1/Mcell cabinet. The Horizon II macro Site Controller (H2SC) acts as the main processor card with the Horizon II macro cabinet. It performs the same functions as 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 H2SC slot in the digital card cage. Site I/O panel In the Horizon II macro cabinet, the fibre connectors are consolidated on to the Site I/O panel. Increased RSL functionality The integrated NIU on the H2SC supports up to six E1 span connections, with up to four RSL devices per span. The RSl devices can be provisioned with either 16 Kbps or 64 Kbps 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 H2SC 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). H2-SURF (Sectorized Unified Receiver Front-end). H2-SURF in the Horizon II macro cabinet provides the same functionality as the SURF in the Horizonmacro cabinet. H2-SURF also supports additional functionality, such as four branch receive diversity. For further technical details, see the Horizon II product documentation.

7-10

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Introduction to BSC and BTS sites

Horizon II Mini
{24281} 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 MCELL, Horizonmacro, or Horizon II Macrocabinet 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 may be equipped to a Horizon II Mini cabinet. The Horizon II Mini BSS software generates a new cabinet type to identify the Mini cabinet to the OMC-R.

In GSR 8, Horizon II Micro shares the Horizon II Mini cabinets identifiers. Use the Horizon II Mini cabinet identifiers when equipping Horizon II Micro in the database. The Horizon II Mini BSS software also supports the EGPRS (egprsOpt) feature. For further technical details, see the Horizon II mini product documentation.

68P02901W17-R 14 Apr 2006

GMR-01

7-11

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

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 will provide the appropriate site parameter inputs needed to create or customize a BTS SITE.

Prerequisites to adding a BTS


Prior to any of the following procedures, the new BTS must have been: Installed and commissioned. Connected to the BSS network through E1/T1 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

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Overview of 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-23. "Creating a SITE using the OMC-R GUI" on page 7-28.

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

68P02901W17-R 14 Apr 2006

GMR-01

7-13

Adding a BTS using a batch rlogin script

Chapter 7: Configuring a Site

Adding a BTS using a batch rlogin script


Adding a BTS on-line 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.

7-14

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Adding a BTS using a batch rlogin script

Procedure list
The following steps are required to add a remote BTS to a BSS: Procedure 7-1 1 Add remote BTS to a BSS

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-46 for further details. 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.

2 3 4 5

Each of these steps is described in detail in the following subsections.

Beginning a batch session


To begin the batch session: Procedure 7-2 1 Begin a batch session

From the Rlogin window, click the Batch button. If templates are used, a chg_level command needs to 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.

68P02901W17-R 14 Apr 2006

GMR-01

7-15

Adding a BTS using a batch rlogin script

Chapter 7: Configuring a Site

Running script file


To run the BTS script file: Procedure 7-3 1 2 Run the BTS script file

Click on the Run button to execute the selected BTS script file. On successful completion, close the Batch window and return to the Front Panel.

Checks to perform after adding a BTS


The following checks should be performed, after adding a BTS: Procedure 7-4 1 2 Checks after adding a BTS

If required, 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 required, unlock the SITE and associated RSLs. Verify the raw statistics files are enabled for the BTS. Wait one statistic interval before verifying the PM reports are available for the BTS.

3 4 5

7-16

GMR-01

68P02901W17-R 14 Apr 2006

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 will be 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 0 MMS 1 MSI 0 MMS 0

MSI 17 MMS 0 BSC

MSI 1 MMS 0 BTS 1 BTS 2

MSI 18 MMS 1

MSI 1 MMS 1

MSI 2 MMS 1

MSI 1 MMS 0

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 1 2 3 Add BTS using TTY interface

Select the BSS and change security level, see "Remotely logging in to a BSS site from the OMC-R" on page 1-46 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.

68P02901W17-R 14 Apr 2006

GMR-01

7-17

Adding a BTS using the TTY interface (example 1)

Chapter 7: Configuring a Site

Equipping BTS devices and functions


To fully equip a BTS site, devices and functions must also be equipped/created, that is: The devices: DRI, GPROC, and so on. Two MSIs. path. RSL. RTF.

7-18

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Adding a BTS using the TTY interface (example 1)

Creation order for devices and functions


The order in which devices/functions should be created/equipped is shown below. 1. Hardware: 2. 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.

3.

Radio: Cells (including Short Message Service, Hopping, Surround Cell, Power Budgets, Enabling Statistics, and so on). Neighbours. RTF. DRI.

68P02901W17-R 14 Apr 2006

GMR-01

7-19

Adding a BTS using the TTY interface (example 1)

Chapter 7: Configuring 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 1 Equip the new site, devices and functions

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.

2 3

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.

7-20

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Adding a BTS using the TTY interface (example 1)

Adding RSL devices


To add RSL devices: Procedure 7-7 1 Add RSL devices

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.

RSL devices 0 and 1 must be assigned to the primary/secondary default slots.

Adding RTF functions


To add RTF functions follow these steps: Procedure 7-8 1 Add RTF functions

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 will be used for the RTF. The example shown in Figure 7-4 deletes the PATH 1 assignment and adds a PATH 3 assignment.

68P02901W17-R 14 Apr 2006

GMR-01

7-21

Adding a BTS using the TTY interface (example 1)

Chapter 7: Configuring a Site

Figure 7-4
BSC

Path assignment example


PATH 0 BTS 1 PATH 0 MSI 0 MMS 0 MSI 1 PATH 1 PATH 1 Slot 16 Cage 14 BTS 2 Slot 16 Cage 15

PATH 2

MSI 1 PATH 2 MMS 0 Slot 16 Cage 14

Slot 14 Cage 15

PATH 3

7-22

GMR-01

68P02901W17-R 14 Apr 2006

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 will be used as the basis for the E1/T1 link-related command parameters in this procedure. To equip a SITE and MSIs using the equip command: Procedure 7-9 1 2 3 Equip a SITE and MSIs

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. Example of equipping a SITE and MSIs
MSI 16 MMS 0 MSI 0 MMS 0 MSI 0 MMS 1 MSI 0 MMS 0 MSI 0 MMS 1 MSI 0 MMS 0

Figure 7-5

MSI 17 MMS 0

MSI 1 MMS 0

MSI 1 MMS 1

MSI 1 MMS 0

MSI 1 MMS 1

MSI 1 MMS 0

BSC

MSI 18 MMS 1

MSI 2 MMS 0

BTS 1

MSI 2 MMS 1

MSI 2 MMS 0

BTS 2

MSI 2 MMS 1

MSI 1 MMS 1

BTS 3

MSI 19 MMS 0

MSI 3 MMS 0

MSI 3 MMS 1

MSI 2 MMS 0

68P02901W17-R 14 Apr 2006

GMR-01

7-23

Adding a BTS using the TTY interface (example 2)

Chapter 7: Configuring a Site

The following is an example input and output for equipping a SITE and MSI devices: -> equip bsc SITE
Enter the SITE identifier: 2 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: 16 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: 0 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: 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: 0 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: master COMMAND ACCEPTED

16

16

16

16

7-24

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Adding a BTS using the TTY interface (example 2)

Equipping path devices using the TTY interface


The network drawing shown in Figure 7-6 will be used as the basis for the path-related command parameters in this procedure. Figure 7-6
BSC PATH 0

Example of equipping paths


BTS 1 BTS 2 PATH 0 MSI 1 MMS 0 PATH 1 MSI 1 MMS 1
Slot 14 Cage 15 Slot 14 Cage 15

MSI 0 MMS 0

BTS 3
Slot 16 Cage 15

PATH 0

PATH 1

PATH 1

PATH 2

PATH 2

MSI 2 MMS 0
Slot 16 Cage 14

PATH 3

To add path devices proceed as follows: Procedure 7-10 1 2 3 4 Add path devices

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.

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-R 14 Apr 2006

GMR-01

7-25

Adding a BTS using the TTY interface (example 2)

Chapter 7: Configuring a Site

Adding RSL devices using equip command


To add RSL devices proceed as follows: Procedure 7-11 1 Add RSL devices

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: Enter the 2nd device ID for the RSL: Enter the unique PATH identifier: 0 Enter LAPD T200 timer value for this Enter LAPD N200 timer value for this 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: 3 COMMAND ACCEPTED

3 0
device: device:

2500 3

7-26

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Adding a BTS using the TTY interface (example 2)

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.

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 will be 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: 3 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-R 14 Apr 2006

GMR-01

7-27

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

7-28

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a SITE using the OMC-R GUI

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.

Procedure
To create a site using the OMC-R GUI, follow these steps: Procedure 7-13 1 Create a site using the OMC-R GUI

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-35 for further details. The SITE class button changes colour. 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.

2 3 4 5

SITE Detailed View fields


The following sections list and briefly describe the parameter fields in the SITE Detailed View according to their parameter grouping.

To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click on that field. A context sensitive help page is displayed.

68P02901W17-R 14 Apr 2006

GMR-01

7-29

Creating a SITE using the OMC-R GUI

Chapter 7: Configuring a Site

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 Brief description Unique SITE name. Displayed for a BTS site only. 0 or 1. Non-Abis, Type 0 (0). Non-Abis, Type 1 (1). Default is null. Default is SITE. Values Mandatory or Optional? Mandatory. Optional.

Field name/BSS parameter name Name BTS Configuration Type bts_type

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. 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. See description in Table 4-1. Displays the parent BSS name. Click to display the parent BSS Detailed View. The type of hardware contained by this SITE. Set to M-Cell for a Horizonmacro or Horizonmacro_ext site.

Optional.

RDN Instance

Default is 0.

Optional.

NMC RDN Value Parent Detailed View

Site Generation

0 to 2. InCell (0), M-Cell (1), M-Cell-Micro (2).

Mandatory.

Additional Information
Use the Additional Information window to input any notes relating to this SITE. Where additional notes are not required, it is advisable to close this field by clicking on 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.

7-30

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a SITE using the OMC-R GUI

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 Brief description Only valid for a remote BTS. Whether a BSP or LCF manages this site. Only valid for a remote BTS. The time to wait in seconds before a carrier is disabled while the site is in power saving mode. The number of carriers to remain in service in the event of a main power failure. Not displayed for SITE 0 (BSC). 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). Controls the amount of BSC-BTS link bandwidth which the CSFP download consumes. Only valid in a BTS. Enables phase locking for the GCLK board. Phase locking means the GCLK board is synchronized to a clock at an uplink site. Values 0 to 24. Default is null. BSP (0) or LCF (1). Mandatory or Optional? Optional. Optional.

Field name/BSS parameter name LCF managing this site BSP/LCF Flag

Carrier Disable Time

120 to 65535 (seconds). Default is 120. 0 to 30 (number of RCUs). Default is 30. 1 to 4. Default is ANY (1).

Optional.

Carriers Ins Power Fail

Optional.

CSFP Algorithm

Mandatory.

CSFP Flow Value

10 to 100 (step size of 10). Default is 10.

Optional.

Phase Lock GCLK

Enabled (1) or Disabled (0). Default is Disabled (0).

Mandatory.

Clock Source Fail Reset Period GPROC Timeslots The number of timeslots to be allocated to all GPROCs for the TDM highway. The alarm range on the allowed long term average (LTA) variation. The number of times CP processes audit each other with regard to a particular connection.

1-255 (in hours). Default is 24. 16 or 32. Default is 16.

Mandatory. Mandatory.

LTA Alarm Range

1 to 255 (no units). Default is 7. 0 to 5. Default is 1.

Optional.

Number Of Audit Retries

Mandatory.

Cont.

68P02901W17-R 14 Apr 2006

GMR-01

7-31

Creating a SITE using the OMC-R GUI

Chapter 7: Configuring a Site

Table 7-5

SITE Detailed View fields - General grouping (Continued) Brief description Enables or disables the flag which checks the timing advance on a Random Access Channel (RACH). Not displayed for SITE 0 (BSC). The RACH loading calculation method to be used. Not displayed for SITE 0 (BSC). The handover RF response to indicate the period of the idle channel categories. Not displayed for SITE 0 (BSC). Specifies the signalling and control information rate of the RSL. Only valid at a BTS. If the BSS feature 16 Kbps LAPD RSL (rsl_rateOpt) is restricted, can only be set to RATE_64 Kbps. 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 will be barred. Not displayed for SITE 0 (BSC). 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 will be barred. Not displayed for SITE 0 (BSC). The time that the site will wait before selecting a new MMS for clock extract after an MMS has a reference failure alarm. The type of connection wanted for the TELCO connection. Not displayed for SITE 0 (BSC). Values Enabled (1) or Disabled (0). Default is Disabled (0). Mandatory or Optional? Mandatory.

Field name/BSS parameter name Poor Initial Assignment

RACH Load Type

0 or 1. Default is 0 (Motorola method). 1 to 127 (in SACCH Multiframes). Default is 10. Default is RATE_64 Kbps (0).

Mandatory.

RF Resource Indication Period

Mandatory.

RSL Rate rsl_rate

Optional.

TCH Busy Critical Threshold

81 to 100. Default is 100.

Mandatory.

TCH Busy Norm Threshold

0 to 100. Default is 100.

Mandatory.

Wait For Reselection

0 to 86400 (in seconds). Default is 10. 0 or 1. Default is 0.

Mandatory.

MMS Configuration Type

Mandatory

Cont.

7-32

GMR-01

68P02901W17-R 14 Apr 2006

Installation and Configuration: GSM System Configuration

Creating a SITE using the OMC-R GUI

Table 7-5

SITE Detailed View fields - General grouping (Continued) Brief description The cept timeslot mapping algorithm at sites adjacent to a TS_SWITCH. Greyed-out for SITE 0 (BSC). Whether the GCLK is active after the normal 30 minute warm up period or after a 15 minute warm up period. Greyed-out for SITE 0 (BSC). Only valid if the Fast GCLK Warm Up feature (FastWarmGclkOpt) is unrestricted (Enabled). Specifies the time in minutes which would be used by the FM Sync process to retry phase locking automatically after it fails. Greyed-out for SITE 0 (BSC). Whether or not the SITE can be calibrated. Only displayed if the bay level calibration facility has been enabled. See "Remotely calibrating DRIs" on page 9-82 for further details. 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-82 for further details. Values 0 or 1. Default is Existing timeslot algorithm (0). Default is GCLK to warm up in 30 mins (0). Mandatory or Optional? Optional.

Field name/BSS parameter name Timeslot Allocation Flag

Fast GCLK Warm Up Flag gclk_qwarm_flag

Optional.

Phase Lock Retry Interval

0 - 255 (minutes). Default is 255.

Optional.

Calibrate Enabled calibrate_flag