Telecommunication is a very important part of its life. This technology is used in a very sophisticated area like safety and security purpose. Using the GSM technology, telecommunication is conducive to save its life as well as households from fire a
Full description
Ericsson-gsm-system-survey-pdfFull description
PR Case (Motorola's Quest for Quality)Full description
Motorola standardsFull description
Descripción: g
In this paper, describes about how to control home appliances, auto door sliding motor, fan and lighting using GSM technology by using android application through android mobile phone. Performing of these tasks with a single android device makes ever
The main aim of the project is to develop a system, which uses mobile technology that keep control of the various units of the automobiles, which executes with respect to the signal sent by mobile. In today's time every system is automated in order t
GSM System Information Type 2quater Scheduling
Home Automation System is used to control home appliances. With the use of computers and electronics technology electrical appliances can be controlled from any part of the world. Consequently, greater amount of energy will be saved and hence the nat
gbdfbhfhmhmmhmhmbmb vmhmhm mhmmmm b mhmhmhmhmhmhmhmh mhmmmmmbmvbmvbmvb gvngvbngvgvbvcbvbgbgbgbnn
Attendance recording in educational institutions is an important task. But now a day's manual data entry procedures are used to take the attendance. Traditional ways of recording attendance involve manual entering of individual attendance on a sheet
A vehicle tracking system is very useful for tracking the movement of a vehicle from any location at any time. An efficient vehicle tracking system is designed and implemented for tracking the movement of any equipped vehicle from any location at any
Accuracy While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Motorola products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Motorola intends to announce such Motorola products, programming, or services in your country. Copyrights This document, Motorola products, and 3rd Party Software products described in this document may include or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed, merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product. Restrictions Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola, Inc. License Agreements The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement. High Risk Materials Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities. Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center (CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
Installation and Configuration: GSM System Configuration ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
What is covered in this manual? This manual provides information and procedures to enable an experienced and qualified user at the OMC-R to configure Motorola GSM Network Elements and objects, and to populate the Configuration Management database. This manual should be used with the OMC-R operating on one of the following series platforms: •
SunFire 4800 and SunFire 4900
•
Netra20
•
SunBlade 150
•
Netra 440 platform
Chapter 1 Configuration Management general information: This chapter provides useful information to assist in the configuration of a GSM system. For example, this chapter includes: •
Recommended working practices.
•
Description of the CM Management Information Base (MIB).
•
Uploading an NE database to the OMC-R.
•
Using the Navigation Tree and Detailed Views to create, modify and delete network objects.
•
Remotely logging in to a BSS from the OMC-R GUI and changing security levels.
Chapter 2 Configuring BSS features: This chapter provides an overview of BSS features and how to configure them from the OMC-R. Chapter 3 Configuring Network, OMC-R and MSC instances: This chapter describes the procedures to be followed to add a Network, OMC-R or MSC object to the OMC-R Navigation Tree.
68P02901W17-S Dec 2009
1
Chapter 4 Configuring a BSS/RXCDR: This chapter describes how to configure a BSS or RXCDR. It covers topics such as: •
Adding a BSS/RXCDR to a network.
•
Creating a BSS/RXCDR database.
•
Equipping cabinets and cages.
•
Configuring an Assoc_BSS and Assoc_RXCDR.
•
Changing the NE ID of an Assoc_BSS/Assoc_RXCDR.
•
Reparenting a BSS/RXCDR.
•
Creating Dynets and DynetGroups.
Chapter 5 Configuring connectivity: This chapter describes how to create and check connectivity between the following: •
Network Elements and OMC-R
•
BSS and MSC (through an RXCDR)
•
BSS/RXCDR and OMC-R
Chapter 6 Configuring a PCU for GPRS: This chapter describes configuring a Packet Control Unit (PCU). It covers General Packet Radio Service (GPRS) PCU topology, equipping PCU contained devices, and configuring a Serving GPRS Support Node (SGSN). Chapter 7 Configuring a site: This chapter describes configuring BTS and BSC sites. It covers topics such as: •
Description of sites.
•
Adding, deleting, and modifying sites.
•
Equipping cabinets and cages at a remote BTS.
•
Extending paths.
•
Generic clock synchronization.
•
Barring calls at a site.
Chapter 8 Configuring cells: This chapter describes how to configure cells, neighbors, and proxy cells from the OMC-R GUI using Detailed Views or TTY interface commands. In addition, this chapter includes procedures to manipulate specific cell parameters, and bar calls at a cell. Chapter 9 Configuring devices and functions: This chapter describes equipping devices and functions using the OMC-R GUI Navigation Tree or TTY interface. These procedures are referenced throughout the manual but are collected together in this chapter for convenience. Chapter 10 Auditing: This chapter describes the purpose of an audit, and how to run and schedule an audit. Chapter 11 Network Expansion: This chapter describes how to expand the network, including copying and reparenting a BTS.
2
68P02901W17-S Dec 2009
Chapter 12 CellXchange: This chapter describes how to use the OMC-R GUI CellXchange facility to import and export cell parameters. This may be necessary in order to replan network frequencies. Chapter 13 Manipulating maps: This chapter describes the facilities available to manipulate background geographical maps. The procedures described use both the OMC-R GUI Navigation Tree and the cmutil utility. The following procedures are described, for example: •
Adding and deleting a user-defined regional map.
•
Adding and changing a map background.
•
Adding and deleting a map node.
•
Adding and deleting a map link.
Chapter 14 Optimizing the network: This chapter gives advice, guidelines and recommendations about how to perform an optimization of the network from the OMC-R. Chapter 15 cmutil: This chapter describes the cmutil utility, and the configuration management operations it can perform.
68P02901W17-S Dec 2009
3
Revision history
Revision history ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The following sections show the revision status of this document.
Version information The following table lists the supported versions of this manual in order of issue: Issue
Date of issue
Remarks
Q
Sep 2004
Issue Q - GSM Software release 7 Half Rate
R
Nov 2006
Issue R - GSM Software release 8 (GMR-02)
S
Apr 2008
Issue S - GSM Software Release GSR9
S
Dec 2009
Issue S - GSM Software Release 9 FP1
Resolution of Service Requests The following Service Requests are resolved in this document: Service Request
CMBP Number
Remarks
N/A
N/A
N/A
Incorporation of Change Notices The following Change Notices (CN) are incorporated in this document:
4
CN Date
CN Number
Title
N/A
N/A
N/A
68P02901W17-S Dec 2009
General information
General information ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Purpose Motorola documents are intended to instruct and assist personnel in the operation, installation, and maintenance of the Motorola equipment and ancillary devices. It is recommended that all personnel engaged in such activities be properly trained by Motorola. Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the customer's behalf, to abide by the instructions, system parameters, or recommendations made in this document. These documents are not intended to replace the system and equipment training offered by Motorola. They can be used to supplement and enhance the knowledge gained through such training.
NOTE If this document was obtained when attending a Motorola training course, it is not updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then Motorola automatically supplies corrections and posts on the Motorola customer website.
Cross references References made to external publications are shown in italics. Other cross references, emphasized in blue text in electronic versions, are active links to the references. This document is divided into numbered chapters that are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents.
68P02901W17-S Dec 2009
5
Text conventions
Text conventions The following conventions are used in the Motorola documents to represent keyboard input text, screen output text, and special key sequences.
Input Characters typed in at the keyboard are shown like this sentence. Items of interest within a command appear like this sentence.
Output Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this sentence. Items of interest within a screen display appear like this sentence.
Special key sequences Special key sequences are represented as follows:
6
CTRL-c or CTRL+C
Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or CTRL+SHIFT+C
Press the Ctrl, Shift, and C keys at the same time.
ALT-f or ALT+F
Press the Alt and F keys at the same time.
ALT+SHIFT+F11
Press the Alt, Shift and F11 keys at the same time.
¦
Press the pipe symbol key.
RETURN or ENTER
Press the Return or Enter key.
68P02901W17-S Dec 2009
Contacting Motorola
Contacting Motorola ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Motorola appreciates feedback from the users of our documents.
24–hour support If you have problems regarding the operation of your equipment, contact the Customer Network Resolution Center (CNRC) for immediate assistance. The 24–hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
Questions and comments Send questions and comments regarding user documentation to the email address: [email protected].
Errors To report a documentation error, call the CNRC (Customer Network Resolution Center) and provide the following information to enable CNRC to open an SR (Service Request): •
The document type
•
The document title, part number, and revision character
•
The page number with the error
•
A detailed description of the error and if possible the proposed solution
68P02901W17-S Dec 2009
7
Security advice
Security advice ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Motorola systems and equipment provide security parameters that the operator configures based on their particular operating environment. Motorola recommends setting and using these parameters following industry recognized security practices. Consider protecting the confidentiality, integrity, and availability of information and assets. Assets include the ability to communicate, information about the nature of the communications, and information about the parties involved. In certain instances, Motorola makes specific recommendations regarding security practices. The implementation of these recommendations and final responsibility for the security of the system lies with the operator of the system. Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information, from the menu located to the left of the Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
8
68P02901W17-S Dec 2009
Warnings, cautions, and notes
Warnings, cautions, and notes ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The following describes how warnings and cautions are used in this document and in all documents of this Motorola document set.
Warnings Warnings precede instructions that contain potentially hazardous situations. Warnings are used to alert the reader to possible hazards that could cause loss of life or physical injury. A warning has the following format:
WARNING Warning text and consequence for not following the instructions in the warning.
Cautions Cautions precede instructions and are used when there is a possibility of damage to systems, software, or individual items of equipment within a system. However, this damage presents no danger to personnel. A caution has the following format:
CAUTION Caution text and consequence for not following the instructions in the caution.
Notes A note means that there is a possibility of an undesirable situation or provides additional information to help the reader understand a topic or concept. A note has the following format:
NOTE Note text.
68P02901W17-S Dec 2009
9
Safety
Safety ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
General safety The following general safety guidelines apply to Motorola equipment: •
The power jack and mating plug of the power cable must meet International Electrotechnical Commission (IEC) safety standards.
NOTE Refer to Grounding Guideline for Cellular Radio Installations – 68P81150E62.
•
Power down or unplug the equipment before servicing.
•
Using non-Motorola parts for repair could damage the equipment or void warranty. Contact Motorola Warranty and Repair for service and repair instructions.
•
Portions of Motorola equipment may be damaged from exposure to electrostatic discharge. Use precautions to prevent damage.
Electromagnetic energy Relevant standards (USA and EC) applicable when working with RF equipment are:
10
•
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
•
Council recommendation of 12 July 1999 on the limitation of exposure of the general public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national regulations.
•
Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on the minimum health and safety requirements regarding the exposure of workers to the risks arising from physical agents (electromagnetic fields) (18th individual Directive within the meaning of Article 16(1) of Directive 89/391/EEC).
68P02901W17-S Dec 2009
Caring for the environment
Caring for the environment ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The following information describes national or regional requirements for the disposal of Motorola supplied equipment and for the approved disposal of surplus packaging. Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
EU countries The following information is provided to enable regulatory compliance with the European Union (EU) directives and any amendments to these directives when using Motorola equipment in EU countries.
Disposal of Motorola equipment European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction with a recycling partner ensures that equipment is collected and recycled according to the requirements of EU environmental law.
Disposal of surplus packaging European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipient’s responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU environmental law.
Non-EU countries In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance with national and regional regulations.
68P02901W17-S Dec 2009
11
Non-EU countries
Turkey Article 7 of the European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic
Equipment (WEEE) The Government of Turkey requests a statement of conformity with the EEE regulation be provided with all electrical and electronic equipment. This statement of EEE conformity (in Turkish) is: EEE Yönetmeliğine Uygundur.
12
68P02901W17-S Dec 2009
CMM labeling and disclosure table
CMM labeling and disclosure table ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The People’s Republic of China requires that our products comply with China Management Methods (CMM) environmental regulations. (China Management Methods refers to the regulation Management Methods for Controlling Pollution by Electronic Information Products.) Two items are used to demonstrate compliance; the label and the disclosure table. The label is placed in a customer visible position on the product. •
Logo 1 means the product contains no substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation.
•
Logo 2 means that the product may contain substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation, and has an Environmental Friendly Use Period (EFUP) in years. The example shown uses 50 years.
Logo 1
Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP) will not leak or mutate causing environmental pollution or bodily injury from the use of the EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain field-replaceable parts, such as battery modules, can have a different EFUP and are marked separately. The Disclosure table is intended only to communicate compliance with China requirements. It is not intended to communicate compliance with EU RoHS or any other environmental requirements.
68P02901W17-S Dec 2009
13
Motorola document set
Motorola document set ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The Motorola document sets provide the information to operate, install, and maintain the Motorola equipment.
Ordering documents and CD-ROMs With internet access available, to view, download, or order documents (original or revised), visit the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or contact your Motorola account representative. Without internet access available, order hard-copy documents or CD-ROMs from your Motorola Local Office or Representative. If Motorola changes the content of a document after the original printing date, Motorola publishes a new version with the same part number but a different revision character.
Document banner definitions A banner indicates that some information contained in the document is not yet approved for general customer use. A banner is oversized text on the bottom of the page, for example, PRELIMINARY — UNDER DEVELOPMENT.
Data encryption In order to avoid electronic eavesdropping, data passing between certain elements in the network is encrypted. In order to comply with the export and import requirements of particular countries, this encryption occurs at different levels. The encryption may be individually standardized or may not be present at all in some parts of the network in which it is normally implemented. The document set covers encryption as if fully implemented. Limitations on the encryption included in the particular software being delivered, are covered in the Release Notes that accompany the individual software release.
14
68P02901W17-S Dec 2009
Chapter
1 Configuration Management General Information ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
General information relating to the configuration of a GSM network from the OMC-R is provided here. The following topics are described: •
Recommendations for Configuration Management on page 1-2.
•
Management Information Base (MIB) on page 1-11.
•
Definition of a Network Element (NE) on page 1-23.
•
Uploading an NE database to the OMC-R on page 1-24.
•
Configuring network objects using the OMC-R GUI on page 1-26.
•
Navigating to a network object class or instance on page 1-28.
•
Using Detailed Views on page 1-30.
•
Creating a network object using the OMC-R GUI on page 1-32.
•
Modifying a network object using the OMC-R GUI on page 1-34.
•
Deleting a network object using the OMC-R GUI on page 1-37.
•
Remotely logging in to a BSS site from the OMC-R on page 1-39.
•
Changing security level (for TTY interface commands) on page 1-43.
•
Remotely logging in to a BSS using WebMMI on page 1-45.
•
Making wide area modifications on page 1-49.
68P02901W17-S Dec 2009
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: •
Recommended weekly procedures The following weekly procedures are recommended: •
Check Audit schedules and the resulting update of OMC-R CM database.
•
Carry out NE database checks.
•
Hold a weekly meeting. Schedule a weekly meeting between all concerned parties to discuss the following: Any outstanding service affecting faults from the previous week. Review configuration changes and planned maintenance work from the previous week.
1-2
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Off-line and online network change recommendation
Planned work for the week ahead. Any issues relating to the future planning or expansion of the network. Prepare a summary weekly report before the meeting. Circulate the actions agreed upon at the meeting.
NOTE Further information about recommended weekly procedures can be found in OMC-R Online Help, Network Operations.
Off-line and online network change recommendation Network Configuration Management takes two forms, off-line configuration and online configuration.
Off-line Configuration Management Off-line Configuration Management is used for large scale network changes, such as frequency replanning, and rapid network expansion which involves rolling out new CM database. The DataGen tool is the recommended method of producing new database. The DataGen tool features RevGen Upgrader, Compiler, and MCDF tables. The DataGen tool also has an off-line MIB feature which allows the online MIB to be recreated off-line. See System Information: DataGen (68P02900W22) for further details.
Online Configuration Management Online Configuration Management is used for small scale network changes. It is performed by a dedicated online CM team working on live BSSs, based on job orders from other groups, such as the optimization or BSS roll out team. The OMC-R GUI is the preferred tool for online expansion. The recommended method is using Detailed Views accessed using the OMC-R GUI Navigation Tree. The other method is to use Remote Login (Rlogin) and type TTY interface commands directly into the BSS. The export and import of RF planning data to/from a third-party planning tool can also take place online using the OMC-R GUI. When using the Remote Login method, if the OML to the network element is in service and there is no MIB lock on the corresponding object, any database changes are propagated to the MIB. These changes are logged using attributeStateChangeEvents, objectCreateEvents, or objectDeleteEvents in the event logs.
68P02901W17-S
1-3 Dec 2009
Working practice recommendation
Chapter 1: Configuration Management General Information
Working practice recommendation The following work practices are recommended: •
Always consult with the CM supervisor before carrying out work on any site which involves changes to the CM Database setup.
•
Always inform the FM supervisor before resetting any live devices.
•
If possible, restrict the number of users working on a BSS to one at a time.
•
Only one user can carry out work on a site at a time.
•
Disable download to the BSS for the duration of the CM work.
•
Always upload the database upon completion of a job order.
•
The recommended method of making changes to devices is using the Navigation Tree and Detailed Views in Edit mode. This method ensures that the device being worked on is locked in the MIB database, preventing other users from making changes on that object. See Configuring network objects using the OMC-R GUI on page 1-26 for details.
Preventing remote login Rlogin functionality is still frequently used, and is the preferred method of configuration for some users who are familiar with TTY commands and database parameters. Others prefer to use the OMC-R GUI with its user-friendly interface. Rlogin functionality is designed independently of MIB, and changes can be made using the rlogin method regardless of whether the object is locked or not. There are advantages and disadvantages to this method:
1-4
•
Main advantage is that changes can be made to the BSS CM database regardless of the state of the CM MIB. The BSS CM database is the live (revenue generating) database. The CM MIB is a model of this data used centrally to manage the network. Therefore any change can be applied retrospectively to the MIB (using Audit) with no effect on the revenue stream.
•
Main disadvantage is that if strict work practices are not implemented to restrict CM staff changing BSS parameters, then the network manager can lose control of the network configuration. As result revenue opportunities may be missed. For example, if uncontrolled changes are made to the frequency plan, they could introduce excess interference into the network and reduce the available capacity.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Command partitioning using the GUI
Local maintenance parameter Rlogin users and local maintenance terminal users can be prevented from accessing a BSS. This ensures that changes are only made using the OMC-R GUI. Set the local maintenance (BSS parameter name: Local_maintenance) parameter field to Yes in the BSS Detailed View. This method is secure, because the rlogin user cannot reset this parameter without going to SYSGEN mode. The procedure can therefore be: 1.
Before starting a job order, set local maintenance parameter to No.
2.
After completing a job order, set local maintenance parameter to Yes.
3.
After completing a job order, exit Edit mode of Detailed View.
Applying the local maintenance parameter for a single BSS Use the following procedure to apply the local maintenance parameter for a single BSS:
Procedure 1-1
Apply local maintenance parameter for a single BSS
1
Edit the BSS Detailed View in the Navigation Tree.
2
Set the Local Maintenance parameter field in the Identification grouping to No (0).
3
Save the changes by selecting File à Save from the menu bar.
4
Exit the Detailed View.
Applying the local maintenance parameter for whole OMC-R The local maintenance parameter can be set to Yes or No for a whole OMC-R. Create a simple shell script that reads NE.MAP to get the different BSSs and runs a cmutil update script for each of the BSSs found.
Command partitioning using the GUI The command partitioning facility provides a means of partitioning OMC-R users into different security areas. Depending on which security area a user has access to, options that could be used to alter OMC-R/BSS information are allowed/disallowed on the OMC-R GUI. Command partitioning also improves OMC-R usability by giving users a smaller, easier, and more applicable selection of menu options from which to choose. Only the GUI is command partitioned, OMC-R UNIX scripts still need existing permissions to run. Setting up command partitioning is detailed in: OMC-R Online Help, Network Operations. {27508} This feature provides the operator with the ability to determine which commands can be assigned to a specific level through the use of a new MMI command as part of command partitioning control.
68P02901W17-S
1-5 Dec 2009
Command partitioning using the GUI
Chapter 1: Configuration Management General Information
{27508} A user is authenticated at the OMC-R whenever they first login using a UNIX account setup by OMCADMIN. When a user uses remote login to access a NE from the OMC-R, the user is automatically authenticated using their UNIX login. If regions are enabled, the username is compared to a list of NEs held at the OMC-R to determine if the user has access to the NE. Each OMC-R user has an access level of 1 to 4 defined in a user profile table. This determines what level of MMI and/or EMON command access they have, once logged in. If they have access rights to a particular NE while logged into the OMC-R, their user ID and user profile are compared to determine the level of command access. Command partitioning is assigned as follows: Levels 1 to 4 for MMI commands and levels 1 to 2 for EMON commands.
Table 1-1
Access levels
Access levels
MMI Access Level
EMON Access Level
1
1
0
2
2
0
3
3
1
4
4
2
By default, all OMC-R account users have access level 4, which allows all the commands to be executed. Follow Procedure 1-2 to change the access levels for a user.
Procedure 1-2
1-6
Changing the access levels for a user
1
Start the OMC-R GUI as omcadmin.
2
Open the Admin menu from the OMC-R GUI front panel and select the Access Control option.
3
Double click the user ID to access the user profile detailed view.
4
Select Edit à Edit to enter edit mode. Go to the NE Access section of the form and change to the appropriate value.
5
Select File à Save.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Tracking logged CM changes
Table 1-2 shows the recommended CM command partitioning configuration.
Table 1-2
Recommended CM command partitioning configuration
Subject
Person usually responsible
Load Management (LM)
Supervisor
All action options under load management in the GUI.
BSS rlogin (RLog)
Supervisor/Operator
TTY and batch rlogin.
Subscription Management (Subs)
Supervisor
Changes to the subscriptions and subscription lists.
Alarm handling (Alarms)
Alarm handler (Not required for CM)
Handle alarms option in alarm window.
Fault Management commands (FM)
Supervisor/Operator
Device administration of BSS devices after creation.
Statistics Management (Stat)
Supervisor/Operator
Enabling/disabling statistics on BSS through GUI.
Map Management (Map)
Supervisor/Operator
Create, save, and delete options under network icon.
Configuration Management (CM)
Supervisor/Operator
Create/delete/edit of all detailed views/commslinks.
Audit
Supervisor
Audit scheduler and logs. All audit and PM resync options using GUI.
Resync
Supervisor
Resync scheduler and logs options listed.
Cell Propagation (CellProp)
Supervisor/Operator
Cell parameter propagation.
Access Control (Access)
OMC-R Administrator or Access Controller (Not required for CM)
Changing command partitioning options for all users.
OMC-R Administration (Admin)
OMC-R Administrator (Not required for CM)
Modifying blacklist and pager subscriptions.
Functions enabled
Tracking logged CM changes There are several ways of monitoring changes to the network. These are explained in this section.
Event logs - logging of all CM changes The recommended method of tracking logged CM changes to the network is using the attributeStateChangeEvents and objectCreateEvents stored in the event logs. Any database changes to existing devices/functions made using the Navigation Tree, Audit, or rlogin are logged using attributeStateChangeEvents (AVCs) in the event logs. Any new devices created/deleted are also logged using objectCreateEvents / objectDeleteEvents in the event logs.
68P02901W17-S
1-7 Dec 2009
Tracking logged CM changes
Chapter 1: Configuration Management General Information
omcaudit log file - logs all CM changes The omcaudit log file is a general-purpose log file, which records OMC-R system activity. The file can be found in: /usr/omc/logs/ A new omcaudit log file is created each day. The date of creation is included in the omcaudit log file name in the following format: omcaudit For example, the omcaudit log file for 14th December 2004, would be named: omcaudit20041214. When an omcaudit log file becomes full, the OMC-R automatically creates a file. To distinguish between omcaudit log files for a specific day, the dated log files are also sequentially numbered using the convention shown in Table 1-3. Table 1-3 shows three omcaudit log files created for the same day, that is, 14th December 2004.
Table 1-3
Same day omcaudit log file naming convention Description
omcaudit log file omcaudit20041214_1
The first full omcaudit log file of the day.
omcaudit20041214_2
The second full omcaudit log file of the day.
omcaudit20041214
The third omcaudit log file of the day. On the 14th December 2004, this file would have been the log file to which the OMC-R was currently writing. If this file had become full, it would have been renamed omcaudit20041214_3, and so on.
An omcaudit log file can be viewed using the commands: cat or more. For example: cat omcaudit20041214_1 or more omcaudit20041214_1 Use the following command to track CM only changes: grep “ cm :
“ /usr/omc/logs/omcaudit* >/tmp/omcaudit_stripped
usraudit log file Messages from the GUI are logged in the usraudit log file. The file can be found in: /usr/omc/logs/usrauditlogs
1-8
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Online Configuration Management setup
BSS log files - logging of rlogin changes (TTY and batch rlogin changes) Two environment variables (in Common.csh) determine where these logs are kept, and if they are enabled. Log files are stored on a per BSS/per session basis. •
RL_BSSLOGDIR identifies the directory used for storing all files detailing BSS command activity. Use: setenv RL_BSSLOGDIR $OMC_TOP/logs/bss
•
RL_LOGCMDS controls the logging facility for BSS commands.
See Operating Information: OMC-R System Administration (68P02901W19) for further details of these environment variables, how to use them, and how to manage log files.
Online Configuration Management setup This section describes how to set up online CM for one or more OMC-Rs.
For a single OMC-R Use the following procedure when there is one OMC-R:
Procedure 1-3
Online CM set up for single OMC-R
1
Each user should have access to an OMC-R GUI. Command partitioning should have been set up for each user.
2
Edit the file /usr/omc/config/global/AUTOINIT.CNFG and ensure it contains all the windows that are required at GUI start-up.
3
Placing an AUTOINIT.CNFG in the home account allows the users to customize what appears at start-up. Refer to OMC-R Online Help, Network Operations for further details on configuring AUTOINIT.CNFG.
4
Set up periodic audits and turn on CM logging.
NOTE If the GUI is not available (for example on a remote site where the overhead is not economic), rlogin to the SITE using the command: RLstart
68P02901W17-S
1-9 Dec 2009
Interrogating the network using the COP GLU tool
Chapter 1: Configuration Management General Information
Multiple OMC-R Use the following procedure when there are multiple OMC-Rs:
Procedure 1-4
Online CM set up for multiple OMC-Rs
1
Configure each operator workstation with a CDE window per OMC-R, and name appropriately.
2
Set up the CDE pull-across windows to start GUIs for the different OMC-Rs.
3
Set up the CDE pull-across windows to allow access to the database utilities of each OMC-R.
4
Install the utilities available on CD ROM aid some CM operations (such as Adding Neighbors across MIBs) in a multi-OMC-R environment. Refer to the Software Release Notes supplied with the software for further details.
Interrogating the network using the COP GLU tool Motorola recommends using the COP Generic Lookup Utility (GLU) tool to interrogate an existing network. GLU is an optional tool, available from Motorola, capable of extracting configuration information on hardware version/serial number/FRU. For full details about COP and GLU, see System Information: Cell Optimization (COP) (68P02900W90). Other methods for interrogating the network, include using Detailed Views and cmutil.
1-10
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Management Information Base (MIB)
Management Information Base (MIB) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Definition of the MIB The Management Information Base (MIB) is the set of network and map configuration data stored in a database. It contains all the necessary network configuration information required to check the devices contained in the network, how they are configured, and the settings of the parameters.
Initializing the MIB The MIB database is initialized as follows:
Procedure 1-5
Initializing the MIB database
1
Populate the OMC-R MIB database with enough information to allow it to communicate with each Network Element. In practice, this means that the Network, OMC-R, BSS, RXCDR, and MSC objects must be created in the MIB database.
2
The OMC-R reads in information from the BSS about its associated BTS sites, links, cells, and cell parameter data. This information is retrieved using the audit process. The audit can be configured so that any differences detected between the OMC-R and the BSS are automatically applied to the MIB database.
Backing up MIB configuration data Regularly back up the MIB database. See Operating Information: OMC-R System Administration (68P02901W19) for further details.
68P02901W17-S
1-11 Dec 2009
Containment
Chapter 1: Configuration Management General Information
Containment The data stored in the MIB database has a hierarchical structure; the relationship of which is reflected in the Configuration Management Navigation Tree (see Figure 1-1). The relationship between two objects is known as a parent-child, or a containment relationship.
Figure 1-1
CM Navigation Tree showing containment relationship
Map
Network MapNode
MapLink
BSS
RXCDR CommsLink
MSC
OMC-R
SGSN
SWInventory DYNETGroup
Assoc_RXCDRs/ Assoc_BSSs
NESoftware
PCU (BSS only)
SITE
SoftwareLoad
Dynet XBL
Conn_link
Software Functions
Hardware Devices
LCF
Logical Links
OMF
CBL
MTL
OML
LMTL
Radio Frequency
PATH
RSL
RTFGroup
RTF
Cabinet
Cage
Processors
EAS
COMB
KSWpair
DHP
GPROC
FreqHopSys
GCLK
IAS
LAN
KSW
BSP/ BTP
TDM
DRIGroup
CELL
DRI
MSI
MMS
CSFP
SMSCBmsg
UtranNbr
Neighbour
BlindSrchNbr
TestNeighbour
Handover*/ Power Control**
TRX
* The Handover Control Objects are: RelTimAdvHC, RxlevDlHC, RxlevUlHC, RxqualDlHC, RxqualUlHC, SurrndCellHC ** The Power Control Objects are : RxlevDlPC, RxlevUlPC, RxqualDlPC, RxqualUlPC ti-GSM-CM Navigation Tree showing containment relationship-00772-ai-sw
See Hierarchy of devices and functions on page 9-29 for further details.
1-12
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Containment rules
Containment rules Some of the rules that apply to the containment of objects are as follows:
Network object •
There can be only one network instance.
OMC-R objects •
The maximum number of OMC-Rs is 51 (0 to 50).
•
Each active OMC-R contains one SWInventory and each SWInventory can contain n Software Loads.
•
In the network, only one active OMC-R is allowed.
GUI sessions •
The maximum number of simultaneous GUI sessions supported per OMC-R is 60 (provided the appropriate number and size of GUI servers are available). This includes 60 MMI processes, one started by each GUI.
•
Only five GUI sessions can start in parallel across all connected GUI server platforms. If more than five sessions are started at the same time, then the additional sessions wait for the other sessions to complete initialization before commencing their own initialization.
•
The maximum number of GUI Clients that can be started on the SunBlade 150 server is 12. If more than 12 are started an error message is displayed.
•
The maximum number of MSCs allowed is 101 (0 to 100).
MSCs
BSS/RXCDR •
On a SunFire 4800, SunFire 4900 and SunBlade 150, the OMC-R supports a maximum of 254 RXCDRs, or 254 BSSs. (On a SunFire 4800, SunFire 4900 and SunBlade 150, the OMC-R supports a maximum of 254 combined BSSs and RXCDRs).
•
A BSS node can contain up to 100 sites.
•
An RXCDR node contains one site (SITE 0).
•
A BSS can support up to three PCUs (for GPRS).
•
A BSS can support up to three NSEIs, one per PCU. The NSEIs must be unique.
•
Each BSS and RXCDR contains one NESoftware object, which identifies software loads.
68P02901W17-S
1-13 Dec 2009
MIB locking
Chapter 1: Configuration Management General Information
BSC and BTSs •
A BSC can support up to {22169} 96 MSI to MSI connections.
•
A BSC can support up to {22169} 96 MSI to XCDR connections.
•
A BSC SITE can contain up to 175 (0 to 174) MSIs and XCDRs.
•
Up to ten RXCDRs can be connected to each BSC, and ten BSCs can be connected to each RXCDR.
•
A BTS SITE can contain up to 10 (0 to 9) MSIs and XCDRs.
•
A BTS can contain up to 24 cells.
•
A site can contain one CSFP.
•
An MSI can contain up to six MMSs depending on the cabinet type.
•
Each XCDR contains one MMS.
•
A cell can contain up to 64 GSM Neighbor cells.
•
A cell can contain up to 16 UTRAN Neighbor cells.
•
A cell can contain up to 31 GSM Neighbor cells when the cell contains one or more UTRAN Neighbors.
•
A cell can contain up to four Handover Control objects, four Power Control objects and one InterferAlg.
MSI
XCDR
Cells
MIB locking
MIB locking is an intelligent locking scheme which allows applications to run simultaneously if they meet certain criteria.
NOTE Regardless of the introduction of MIB Locking, only one network expansion operation can be run at a time (except for Path Configure). See Chapter 11 Network Expansion for further details.
1-14
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
MIB locking
Types of locking Instead of locking the entire MIB, it is possible to specify that only specific network elements (BSS/RXCDR) are locked. In this way, multiple operations can run in parallel if they do not use the same BSS(s)/RXCDR(s) and contained devices. The following is an overview of the types of locks which are configurable per application type: •
Intelligent Locking - allows the OMC-R to identify and lock only the BSS(s)/RXCDR(s) that are affected by a particular operation for the duration of the operation. However, in the case of an Audit Gather for a Network or multiple NEs, a lock is released when the application has finished with an NE rather than waiting until the entire operation has finished. If there is a Resync operation, intelligent locking takes the form of no locking. This is because Resync only affects state and MO locks can be broken to update the state without affecting an audit or other CM operation.
•
Global Locking puts a lock on the entire network for the duration of the operation. This is supported purely for backward compatibility.
mib_locks.cfg file The lock configuration for each application can be defined and stored in the /usr/omc/config/global/mib_locks.cfg file. The /usr/omc/config/global/mib_locks.cfg file is copied over from one OMC release to the next to maintain the customer lock configuration.
Recommended settings for the mib_locks.cfg file The following default configurations are recommended for the /usr/omc/config/global/ mib_locks.cfg file: •
Audit Gather = Intelligent.
•
Audit Apply = Intelligent.
•
Cell Prop = Intelligent.
•
Resync = Intelligent.
•
NetEx = Intelligent.
•
CellEx = Intelligent.
•
Bay Level Cal = Intelligent.
•
Cmutil = Intelligent.
•
OLM = Intelligent.
•
Proxy Cell = Intelligent.
CleanMib always uses global locking.
68P02901W17-S
1-15 Dec 2009
MIB locking
Chapter 1: Configuration Management General Information
Lock files Lock files are created for the Audit, Resync, CMutil, NetEx, CellEx, Cell Propagation, Bay Level Calibration, OLM and Proxy Cell Import/Export applications, and are stored in the directory: /usr/omc/config/global/locks. The OMC-R removes all lock files from /usr/omc/config/global/locks on startup of the OMC. The name of a lock file depends on the type of locking specified: •
A lock file with a name in the format 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 , where AUDIT_TAG is AG to indicate an Audit Gather lock file. For example, 28034-131072-1120583512-AG.
•
A file called ALL-GLOBAL is created for Global Locking.
•
A file called ALL-INTELLIGENT-NETWORK is created when Intelligent Locking is configured for an application and where the operation affects the entire network. For example, Cell-X-export for a network, Cell-X-import for a network, CMutil network operation, CMutil type extraction, Proxy Cell Export, and Network Realignment on the OLM. It is also applicable when the Verify NE and Save NE Database options are initiated through the OLM Operations menu option when the Network icon on the Navigation Tree has been selected.
The OMC-R does not lock the MIB for an operator-initiated neighbor propagation procedure from a Cell or RTF Detailed View.
LOCK_LOGGING option The LOCK_LOGGING option determines the type of logging that occurs for the MIB Locking feature. If set to 0 (Off), limited locking data is logged to the omcauditlog files, that is, the logged information just indicates the creation and deletion of a lock for an NE. If set to 1 (On), then extra locking information is logged in the omcauditlog files. It consists of the location of the lock file, the name of the lock file and the lock file contents, for example: 2004-04-16 16:29:02 gui: Lock File : /usr/omc/config/global/locks/28034 -131089- 1080813742 2004-04-16 16:29:02 gui : Populating File with the following info 2004-04-16 16:29:02 gui : Ne Name : BSS1011 2004-04-16 16:29:02 gui : Process Name : Path Configure 2004-04-16 16:29:02 gui : Process ID : 11041 2004-04-16 16:29:02 gui : User Name : alynch010 2004-04-16 16:29:02 gui : IP Address : 10.131.2.192 2004-04-16 16:29:02 gui : Host Name : liath192 The default is 0 (Off). The LOCK_LOGGING option is contained in the /usr/omc/config/global/mib_locks.cfg configuration file.
1-16
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
MIB locking
Examples of the MIB locking strategy in operation Example 1: Intelligent Locking set The following procedure illustrates how the MIB locking strategy is used for the Audit Gather operation on a BSS/RXCDR when Intelligent Locking (recommended setting) is set:
Procedure 1-6
68P02901W17-S
Example 1: Audit Gather operation when Intelligent Locking is set
1
The operator selects the BSS(s)/RXCDR(s) to Audit from either the Navigation Tree, BSS/RXCDR Detailed View, Map, or LM applications.
2
The operator selects the Audit option from the Config Mgt Menu.
3
The OMC-R checks the /usr/omc/config/global/mib_locks.cfg file where Intelligent Locking has been set for Audit Gather operations.
4
For each BSS/RXCDR to be audited, the OMC-R creates a lock file. The lock file name has the format: where AG signifies the Audit Gather operation, and can be found in /usr/omc/config/global/locks. Each file contains the NE name, the process name, the PID, user ID of the person initiating the operation, and the IP address of the machine on which the operation is running.
5
For each BSS/RXCDR locked in Step 4, the system logs the following information to the omcauditlogs: YYYY-MM-DD HH:MM:SS au : Audit Gather locking : (PID) For each BSS/RXCDR locked by the Audit Gather, steps 6 to 8 and then performed.
6
The system determines a list of audit inconsistencies for the BSS/RXCDR.
7
The system removes the lock file created in Step 4 for that BSS/RXCDR.
8
The system logs the following information in the omcauditlogs for the released lock: YYYY-MM-DD HH:MM:SS au : Audit Gather releasing : (PID)
9
The system verifies that all BSS(s)/RXCDR(s) selected in Step 1 have been audited.
1-17 Dec 2009
MIB locking
Chapter 1: Configuration Management General Information
Example 2: Global Locking set The following procedure illustrates how the MIB locking strategy is used for the Audit Gather operation on a BSS/RXCDR when Global Locking is set:
Procedure 1-7
Example 2: Audit Gather operation when Global Locking is set
1
The operator selects the BSS(s)/RXCDR(s) to Audit from either the Navigation Tree, BSS/RXCDR Detailed View, Map, or LM applications.
2
The operator selects the Audit option from the Config Mgt menu.
3
The OMC-R checks the /usr/omc/config/global/mib_locks.cfg file where Global Locking has been set for Audit Gather operations.
4
The system creates a lock file called ALL-GLOBAL in /usr/omc/config/global/locks which contains the process name, the PID, user ID of the person initiating the operation, and the IP address of the machine on which the operation is running.
5
The system logs the following information to the omcauditlogs: YYYY-MM-DD HH:MM:SS au : Audit Gather locking ALL-GLOBAL: (PID)
6
The system determines a list of audit inconsistencies for the selected BSS(s)/RXCDR(s).
7
The system removes the lock file created in Step 4.
8
The system logs the following information to the omcauditlogs: YYYY-MM-DD HH:MM:SS au : Audit Gather releasing ALL-GLOBAL: (PID)
Lock error messages If the OMC-R is unable to lock a network object, the OMC-R logs the information to the omcauditlogs. For example, if the OMC-R could not lock an NE during an Audit Gather operation, the following message is logged to the omcauditlogs: YYYY-MM-DD HH:MM:SS au : Audit Gather unable to lock due to the existence of one or more locks. Run utility ‘/usr/omc/current/sbin/LockUtility’ to list the NE(s) on which a lock exists.
LockUtility To view the locks that currently exist, run the LockUtility found in: /usr/omc/current/sbin/. LockUtility displays the following information for each lock found in /usr/omc/config/global/locks:
1-18
•
Id.
•
BSS/RXCDR Name.
•
Application Type.
•
PID. 68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
•
Lock Type.
•
Time.
•
User.
MIB locking
The omcadmin can either Remove Lock, Remove All Locks, or Exit. If a lock is removed, the following information is logged to the omcauditlogs: YYYY-MM-DD HH:MM:SS: Lock Utility releasing :
(PID)
checkValidLockPID utility To ensure that locks do not exist for processes that have died, the checkValidLockPID utility can be deployed. Set up a cronjob on every GUI server and the SPLAT to run the checkValidLockPID utility every 15 minutes. The checkValidLockPID utility checks for lock files in /usr/omc/config/global/locks containing the same IP address as the machine on which it is running. For each lock file with the same IP address, checkValidLockPID verifies that the PID associated with the lock file is still alive and running. If it is not alive and running, checkValidLockPID removes the associated lock file.
Limiting the number of parallel CM operations The MAX_CM_OPS and MAX_CMUTIL_OPS system parameters are defined in the /usr/omc/config/global/mib_locks.cfg file on the system processor. It is not necessary to perform an OMC Stop/Start when these parameters are modified. The parameters are maintained on a point release cutover.
MAX_CM_OPS The MAX_CM_OPS parameter defines the maximum number of locked NEs, above which no new configuration management operations that require a lock on an NE can be started.
NOTE Audit Gathers are not included in the MAX_CM_OPS count.
68P02901W17-S
1-19 Dec 2009
MIB locking
Chapter 1: Configuration Management General Information
Minimum, Maximum, and Default Values The MAX_CM_OPS minimum, maximum, and default values are listed in Table 1-4:
Table 1-4
MAX_CM_OPS Minimum, maximum, and default Values MAX_CM_OPS MINIMUM
MAX_CM_OPS MAXIMUM
MAX_CM_OPS DEFAULT
120 k TCH
1
17
12
All other platforms
1
9
5
Off Line MIB on any DataGen supported system specifications
1
3
2
System TCH Capacity
NOTE The MAX_CM_OPS system parameter cannot be set to values outside the ranges specified in Table 1-4 for the different TCH capacity systems.
Starting a new configuration management operation Before starting a new configuration management operation, the system performs the following:
•
Counts the number of NE lock files on the system (not including Audit Gathers).
•
Compares the number of configuration management operations currently running to the system parameter (MAX_CM_OPS).
If the number of NE lock files is less than MAX_CM_OPS, the new configuration management operation starts. Example 1: If the value of MAX_CM_OPS is set to 5 and the following configuration management operations (that is, five NE lock files) are currently running: Path configure. Delete site with no neighbors. CellEx Export with no neighbors. CellEx Import with no neighbors. CMutil extract BSS. Another new configuration management operation would not be allowed to start.
1-20
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
MIB locking
Example 2: If the value of MAX_CM_OPS is set to 5 and the following configuration management operations are currently running: Path configure. Delete site with no neighbors. CellEx Export with no neighbors. Audit Gather. Audit Gather. Audit Gather. CMutil extract BSS. Because there are four configuration management operations running (four NE lock files), a new configuration management operation would be allowed to start as Audit Gathers are not included.
MAX_CMUTIL_OPS The MAX_CMUTIL_OPS parameter defines the maximum number of Cmutil operations allowed in parallel.
Minimum, Maximum, and Default Values The MAX_CMUTIL_OPS minimum, maximum, and default values are listed in Table 1-5.
Table 1-5
MAX_CMUTIL_OPS minimum, maximum, and default values MAX_CMUTIL_OPS minimum
MAX_CMUTIL_OPS maximum
MAX_CMUTIL_OPS default
120 K TCH
1
2
2
All other platforms
1
1
1
Off Line MIB on any DataGen supported system specifications
1
1
1
System TCH
NOTE
68P02901W17-S
•
The MAX_CMUTIL_OPS system parameters cannot be set to values outside the ranges specified in Table 1-5 for the different TCH capacity systems.
•
Cmutil operations are counted as part of the MAX_CM_OPS total.
•
A HierDelete operation is classified as ONE cmutil operation. This Cmutil operation is part of the MAX_CMUTIL_OPS total.
1-21 Dec 2009
MIB locking
Chapter 1: Configuration Management General Information
Starting a new Cmutil operation Example 1: If the number of Cmutil operations currently running is less than MAX_CMUTIL_OPS, and the total number of NEs locked is less than MAX_CM_OPS, the new Cmutil operation is started. If the value of MAX_CM_OPS is set to 5, MAX_CMUTIL_OPS is set to 2 and the following configuration management operations are currently running: Path configure Delete site with no neighbors CellEx Export with no neighbors HierDelete BSS CMutil extract BSS Because there are four configuration management operations running (four NE lock files), and one CMutil operation (one NE lock file), another new Cmutil operation would not be allowed to start. Example 2: If the value of MAX_CM_OPS is set to 5, MAX_CMUTIL_OPS is set to 2 and the following configuration management operations are currently running: Path configure. Delete site with no neighbors. CellEx Export with no neighbors. Audit Gather. Audit Gather. Audit Gather. CMutil extract BSS. Because there are three configuration management operations running (three NE lock files), and one CMutil operation running (one lock file), a new CMutil operation would be allowed to start as Audit Gathers are not included.
1-22
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Definition of a Network Element (NE)
Definition of a Network Element (NE) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Types of Network Element There are two types of Network Element (NE): •
Base Station System (BSS).
•
Remote Transcoder (RXCDR).
Base Station System (BSS) A Base Station System (BSS) is the system between the Mobile Switching Centre (MSC) and the Mobile Stations (MSs). This system requires Base Station Controller (BSC) and Base Transceiver Station (BTS) functions and can include a local transcoding function. The BSS consists of one or more of the following sites: •
BSC site. This is a BSS with all BTS functions at remote locations. This BSC provides the interface between the MSC and the remote BTS sites.
•
Remote BTS site. These sites provide the interface between the BSC and the MSC or MSs, performing the base transceiver functions.
•
BSS site with local transcoding. Local transcoding can be included at any type of site except BTS.
NOTE Transcoding can be included at any type of site except a BTS.
RXCDR Transcoding is the digital signal processing required to interface between the MSC 64 kbit/s circuits and the MS air interface 13 kbit/s circuits. Transcoding is a BSS function that can be performed at a BSC and/or remote BTS sites. A Remote Transcoder (RXCDR), typically located at the MSC, provides transcoding for multiple BSSs.
68P02901W17-S
1-23 Dec 2009
Uploading an NE database to the OMC-R
Chapter 1: Configuration Management General Information
Uploading an NE database to the OMC-R ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
BSS and RXCDR databases The Base Station Controller (BSC) holds the master copy of the database for the BSS, known as the BSS database. The BSS database can be downloaded to a BTS when required. The master copy of the BSS database can be manually uploaded to the OMC-R when necessary. For example, it may be necessary to upload the BSS database to the OMC-R to preserve the most recent changes in the event of a power loss or similar event at the BSS/RXCDR node. Likewise, the RXCDR holds an RXCDR database, which can be uploaded to the OMC-R database, when required.
When to upload an NE database Upload the NE database after any of the following events has occurred: •
A new database has been downloaded to the site since the last upload.
•
One or more MMI commands have been performed on the site either locally or from the OMC-R.
•
A week has elapsed since the last upload from the BSC.
NOTE If any changes are made to the BSS database, using BSS commands or Detailed Views, upload the BSS database to the OMC-R.
Uploading the NE database to the OMC-R Use the following procedure to upload the NE database to the OMC-R:
Procedure 1-8
Upload NE database to the OMC-R
1
From the Front Panel, select the Config Mgt icon to display the Navigation Tree.
2
For each affected BSS NE, open the Detailed View by either double clicking the required NE, or by selecting Edit à Detailed View from the menu bar.
3
Select Options à NESoftware to open the NESoftware window. Continued
1-24
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Procedure 1-8
Uploading the NE database to the OMC-R
Upload NE database to the OMC-R (Continued)
4
Select Load Mgt à Upload Object to open the Upload box.
5
Select Database in the Object Type field.
6
Click OK to initiate an upload of the NE database so that the database has the recent cell id and neighbor updates. An information box is displayed with the following message: Upload Operation Started...
7
Click OK. The information box closes.
8
In the NESoftware window, select File à Close from the menu bar.
Use the following procedure to monitor the upload status during the upload process:
Procedure 1-9
68P02901W17-S
Monitor upload process
1
Select the Load Mgt icon from the Front Panel. the Load Mgt Options window is displayed.
2
Select the Upload Status option on the Upload window to display the Upload Status window.
3
Monitor the status of the upload in the Upload Status window.
4
When the upload is complete, close the Upload Status window.
5
Repeat Procedure 1-8 and Procedure 1-9 for all affected BSS NEs.
1-25 Dec 2009
Configuring network objects using the OMC-R GUI
Chapter 1: Configuration Management General Information
Configuring network objects using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to creating, editing, and deleting network objects Network objects can be created using any of the following methods: •
OMC-R GUI Navigation Tree.
•
Remote login and the TTY interface, see Remotely logging in to a BSS site from the OMC-R on page 1-39.
•
cmutil, see Chapter 15 cmutil.
This section provides a general procedure for creating, modifying, and deleting network objects using the OMC-R GUI Navigation Tree and Detailed View forms.
Activities available in Navigation Tree The OMC-R GUI Navigation Tree can be used to: •
Create network objects.
•
Display details of network objects.
•
Modify network objects.
•
Delete network objects.
Other activities initiated from the Navigation Tree are detailed in OMC-R Online Help, Network Operations. Network objects are created and modified using Detailed View forms.
Selecting regions using the Navigation Tree If the geographic command partitioning and region support feature is in operation, it may also be necessary for a user to select the appropriate region before creating or managing a network object. Select the required region name from the list displayed above the panner window in the Navigation Tree. The selected region and its network elements are then displayed in the Navigation Tree. See OMC-R Online Help, Network Operations for further details of geographic command partitioning and region support feature.
1-26
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
User access to OMC-R GUI functions
User access to OMC-R GUI functions A user can only create/modify/delete network objects if the system administrator has allocated the user to specific command partitioning areas. If a user does not have access to certain functions, the menu options are grayed-out and cannot be selected. OMC-R Online Help, Network Operations describes how command partitioning and user access privileges are set up.
Related topics The following sections describe related topics: •
Navigating to a network object class or instance on page 1-28.
•
Using Detailed Views on page 1-30.
•
Creating a network object using the OMC-R GUI on page 1-32.
•
Modifying a network object using the OMC-R GUI on page 1-34.
•
Deleting a network object using the OMC-R GUI on page 1-37.
68P02901W17-S
1-27 Dec 2009
Navigating to a network object class or instance
Chapter 1: Configuration Management General Information
Navigating to a network object class or instance ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Network object class and network object instance buttons Network objects are divided into classes in the Navigation Tree, for example, BSS, SITE, Processors, Logical Links, Cage, and so on. A button in the Navigation Tree represents each class. Network object instances are actual network objects and have their own Detailed View. To display a network object instance, click the folder button next to the network object class button. If network object instances have been created, they are displayed in the Navigation Tree.
Introduction to using the Navigation Tree To create a network object instance using the OMC-R GUI, the network object class must be visible in the Navigation Tree. To modify, display or delete a network object instance the network object instance must be visible in the Navigation Tree. Open the branches of the Navigation Tree to make these objects visible. This action is referred to as navigating to a network object.
Navigating to the network object Use the following procedure to navigate to a network object:
Procedure 1-10
1-28
Navigate to network object
1
From the Front Panel, click the Config Mgt icon to display the Navigation Tree.
2
Click the folder icon buttons next to the network object class and network object instance buttons to open the Navigation Tree levels until the network class button required in visible. See Figure 1-1 for information about network object containment. If necessary, see OMC-R Online Help, Network Operations for further details of how to use the Navigation Tree.
3
Click the folder icon button next to network object class button. If any network object instances have been created, the OMC-R displays them.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Representation of a navigation route to a network object
Representation of a navigation route to a network object In this manual, the navigation route to a network object is represented in parentheses and shows the type and instance buttons which have to be selected to display the destination network object button or network object type button. For example, the following shows the navigation route to a BTP instance: (Network - BSS - BSS instance -Site - Site instance (BTS only) - Hardware Devices - Processors BTP - BTP instance). Double clicking a BTP instance button would display the BTP Detailed View.
Closing the Navigation Tree Close the Navigation Tree window by selecting File à Close from the Navigation Tree menu bar.
Using the FIND option to locate a network object To find a network object (such as a BSS, site, PCU or cell) quickly, use the Find icon on the Front Panel, or select Find from the Navigation Tree. The Find function displays a Navigation Tree starting at the network object defined in the Find criteria. See OMC-R Online Help, Network Operations for further details.
68P02901W17-S
1-29 Dec 2009
Using Detailed Views
Chapter 1: Configuration Management General Information
Using Detailed Views ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description of Detailed Views A Detailed View form contains fields representing specific parameters for a network object. Detailed View forms can be displayed for most network objects, for example, for all NEs, sites, cells, and most devices, functions and links. Detailed Views provide a user-friendly method of defining network object parameters. Alternatively, network object parameters can be defined and modified by remotely logging in to a BSS, and then using the TTY interface and MMI BSS commands. Refer to Remotely logging in to a BSS site from the OMC-R on page 1-39. The appropriate sections of this manual list and provide a brief description of the fields in each Detailed View. For each Detailed View description, the following information is provided, where possible: •
OMC-R GUI field name. Where pertinent, the BSS database parameter name is also shown. If the OMC-R database parameter name is different from the BSS database parameter name, then the OMC-R database parameter name is also shown. The BSS parameter names are always used in TTY interface commands.
•
Brief description of the field.
•
Valid values that can be entered for the field.
•
If the field is Mandatory or Optional, which indicates whether the field requires a value when creating an instance of the class.
Displaying Detailed Views with BSS or OMC-R names Fields in the OMC-R GUI Detailed View forms can be displayed as: •
A plain English description - known as the OMC-R Naming. When space is limited, field names are shown in an abbreviated form.
•
BSS and OMC-R database parameter name - known as the BSS Naming.
For example, the BTS Power Control Acknowledgment field in the CELL Detailed View form can be displayed as bts_p_con_ack, which is the name of the parameter in the BSS and OMC-R database. (An OMC-R attribute is also referred to as a parameter.)
NOTE Some parameters can have slightly different names in the OMC-R and BSS databases.
1-30
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displaying Detailed Views with BSS or OMC-R names
Changing naming for all Detailed Views If necessary, BSS parameter names can always be displayed in Detailed Views by setting the environment variable: BSS_NAMING. By default, BSS_NAMING is not set (meaning that OMC-R parameter names are displayed by default in Detailed Views). Set BSS_NAMING before starting the GUI, otherwise the GUI needs to be stopped and then restarted in order for the variable to take effect. To set BSS_NAMING, type the following line in the file mmiProcConfig.csh, which can be found in /usr/omc/config/global/env: setenv BSS_NAMING To unset BSS_NAMING, comment-out, or delete the variable in the mmiProcConfig.csh file. Environment variables are detailed in Operating Information: OMC-R System Administration (68P02901W19).
Changing naming for a single Detailed View To switch between the OMC-R and BSS naming conventions in a Detailed View, select View à OMC Naming, or View à BSS Naming from the Detailed View menu bar.
68P02901W17-S
1-31 Dec 2009
Creating a network object using the OMC-R GUI
Chapter 1: Configuration Management General Information
Creating a network object using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of creating a network object using the Navigation Tree Creating a network object using the Navigation Tree involves: 1.
Creating a Detailed View for the required network object.
2.
Defining the Detailed View parameter fields for the network object.
3.
Saving the information and closing the Detailed View.
4.
Unlock the device to bring it into service. (This step is not required when creating a Network instance.)
Creating the Detailed View for the network object Use the following procedure to create a Detailed View for the network object:
Procedure 1-11
1-32
Create Detailed View for network object
1
Navigate to and select the network object class button in the Navigation Tree. If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object class button changes color.
2
Select Edit à Create from the Navigation Tree menu bar. The OMC-R displays the Detailed View for the network object in Create mode.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Defining the parameter fields for the network object
Defining the parameter fields for the network object Use the following procedure to define the required parameter settings for the network object:
Procedure 1-12
Define parameter fields for network object
1
Create the Detailed View for the network object.
2
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.
3
Use the scroll bar on the right-hand side of the window to scroll all the way to the top and bottom of the window to ensure that all the fields in the Detailed View have been completed. The proportion of window which is invisible depends on the physical size of the window displayed.
Saving information and closing the Detailed View When all the fields have been completed as required in the Detailed View, use the following procedure to create the network object and close the Detailed View:
Procedure 1-13
68P02901W17-S
Saving and closing Detailed View
1
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.
2
Select File à Close from the menu bar to close the Detailed View window. If you chose not to create or save the information in the Detailed View, the OMC-R displays a confirmation window, asking whether the changes are to be discarded or saved. Reply as required.
1-33 Dec 2009
Modifying a network object using the OMC-R GUI
Chapter 1: Configuration Management General Information
Modifying a network object using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to modifying a network object using the Navigation Tree The parameters for a network object may have to be modified from time to time, perhaps as a result of reconfiguring the network. To modify a network object, edit the Detailed View for the object. When editing a Detailed View, the modified parameters are propagated to the BSS and, if acceptable, are sent back for storage in the MIB database.
Non-editable fields in Detailed Views A user cannot change some fields in a Detailed View (read-only) for the following reasons: •
The OMC-R generates the information in the field, for example, the current status of a network object.
•
The information in the field can only be entered when the object is created, that is, when the Detailed View is in Create mode. When the Detailed View is in Monitor or Edit mode some fields can no longer be modified.
Displaying and modifying a Detailed View Before a Detailed View form can be modified, it must have been created and saved as part of the current network. To display and edit a Detailed View, use the following procedure:
Procedure 1-14
Display and edit a Detailed View
1
Navigate to and select the network object instance button in the Navigation Tree. If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object instance button changes color. Alternatively, use the Find icon on the Front Panel to locate a network object, see OMC-R Online Help, Network Operations for further details.
2
Select Edit à Detailed View from the menu bar. The OMC-R displays the Detailed View in Monitor mode. Alternatively, double-click the network object instance button to display the Detailed View form. Continued
1-34
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Procedure 1-14
Displaying and modifying a Detailed View
Display and edit a Detailed View (Continued)
3
To modify fields, select Edit à Edit from the menu bar. The Detailed View changes from Monitor to Edit mode. It is only possible to change fields in the Detailed View when it is in Edit mode. Figure 1-2 shows an example of a Detailed View in Edit mode.
4
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.
5
Click the required field. The field information can be changed using the arrow and Backspace keys. Where an entry with a list of options is to be changed: 1.
Open the option list by pointing at the current selection and holding down the left mouse button.
2.
Keeping the button depressed, use the mouse to scroll up or down through the available options.
3.
When the required option has been highlighted, release the mouse button. The new selection replaces the previous selection.
Saving the information Use the following procedure to save the information:
Procedure 1-15 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.
NOTE It is impossible to revert to a previous version after an edited version has been saved. 2
68P02901W17-S
Close the Detailed View by selecting File à Close from the menu bar.
1-35 Dec 2009
Displaying and modifying a Detailed View
Figure 1-2
Chapter 1: Configuration Management General Information
Installation and Configuration: GSM System Configuration
Deleting a network object using the OMC-R GUI
Deleting a network object using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Methods of deleting a network object A network object can be deleted from either the: •
Navigation Tree.
•
Detailed View.
Prerequisites for deleting network objects Before a network object can be deleted, child objects should be deleted and the network object should be locked.
Deleting a network object from the Navigation Tree Use the following procedure to delete a network object using the Navigation Tree:
Procedure 1-16
Delete network object using Navigation Tree
1
Navigate to and select the network object instance button in the Navigation Tree. If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object class button changes color.
2
Select Edit Detailed View à Delete from the menu bar. The OMC-R displays a deletion confirmation window.
3
To cancel the deletion, click Cancel. The confirmation window closes and the OMC-R displays the Navigation Tree.
4
To confirm the deletion, click OK. The deletion process is documented in the status bar. When completed, the message: Delete Complete is displayed. After a few seconds, the OMC-R deletes the network object from the Navigation Tree.
5
Select File à Close from the menu bar to close the Navigation Tree window.
NOTE In the instance of deleting a BCCH RTF, the deletion confirmation window displays a further option to allow the incoming neighbors to be exported. This is further described in Exporting incoming neighbors on deletion of BCCH RTFs on page 9-195.
68P02901W17-S
1-37 Dec 2009
Deleting a network object from a Detailed View
Chapter 1: Configuration Management General Information
Deleting a network object from a Detailed View Use the following procedure to delete a network object using the Detailed Views:
Procedure 1-17
Delete network object from Detailed View
1
Display the Detailed View for the network object to be deleted.
2
Select Edit àEdit from the menu bar to enter Edit mode.
3
Select File à Delete from the menu bar. The OMC-R displays a deletion confirmation window.
4
Either click OK to confirm the deletion, or click Cancel to cancel the deletion. The confirmation window closes and the OMC-R displays the Navigation Tree. The deletion process is documented in the status bar. When completed, the message: Delete Complete is displayed. After a few seconds, the OMC-R deletes the network object from the Navigation Tree.
5
Select File à Close from the menu bar to close the Detailed View.
6
Select File à Close from the menu bar to close the Navigation Tree window.
NOTE In the instance of deleting a BCCH RTF, the deletion confirmation window displays a further option to allow the incoming neighbors to be exported. This is further described in Exporting incoming neighbors on deletion of BCCH RTFs on page 9-195.
1-38
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Remotely logging in to a BSS site from the OMC-R
Remotely logging in to a BSS site from the OMC-R ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to remote login to a BSS Once a BSS or RXCDR has been created, it is possible to log in to it from the OMC-R. A user can then set up and manage the BSS using BSS MMI commands and parameters through the TTY interface. This is referred to as Remote Login or Rlogin. Remote login involves: 1.
Logging in to a BSS.
2.
Changing security level, as necessary, according to the commands to be used, see Changing security level (for TTY interface commands) on page 1-43.
Maximum number of remote login sessions The maximum number of concurrent remote logins supported by the OMC-R is 90. The default number of concurrent remote logins supported is 60. The maximum simultaneous remote login sessions to a single node are defined by the number of GPROCs available at that node to receive the rlogin requests. For example, two GPROCs support a maximum of two simultaneous rlogins.
Logging in remotely to a BSS Use the following procedure to log in remotely to a BSS from the OMC-R:
Procedure 1-18
Remote log in to a BSS
1
Select the Remote Login icon from the Front Panel as shown in Figure 1-3. The OMC-R displays the RLogin window (see Figure 1-4) which lists all the current network elements in alphabetical order.
2
Select the network element required. Continued
68P02901W17-S
1-39 Dec 2009
Logging in remotely to a BSS
Chapter 1: Configuration Management General Information
Procedure 1-18 3
Remote log in to a BSS (Continued)
Click the TTY button to start a TTY interface session. The OMC-R displays a window for the site and an MMI prompt. The BATCH button displays the Batch File Selection window (see Figure 1-5), which lists the available batch files in the default batch directory. Use this window to: •
Select, view, edit, and run the batch files.
•
Search for, and manipulate, files in other directories.
4
Change to security level 2 once logged in, see Changing security level (for TTY interface commands) on page 1-43.
5
Use any of the BSS commands mentioned in this manual or detailed in the Technical Description: BSS Command Reference (68P02901W23).
Figure 1-3
OMC-R front panel
ti-GSM-OMC-Rfrontpanel-00774-ai-sw
1-40
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Figure 1-4
Logging in remotely to a BSS
RLogin window
ti-GSM-Rloginwindow-00775-ai-sw
68P02901W17-S
1-41 Dec 2009
Logging in remotely to a BSS
Figure 1-5
Chapter 1: Configuration Management General Information
Introduction to changing security levels System configuration and administration commands, such as those used in equipping devices and functions, may only be performed in security level 2. Some activities require the user to log in at security level 3. Technical Description: BSS Command Reference (68P02901W23) specifies the security level for each command.
Using the TTY interface to change to security level 2 Use the following procedure to change to security level 2 using the TTY interface:
Procedure 1-19
Change security level at TTY interface
1
From the RLogin window (see Figure 1-4), click the TTY button. The OMC-R displays a window for the site and an MMI prompt.
2
Type chg_level and press Return.
3
Enter the password for security level 2 and press Return.
NOTE step 1 and step 2 can only be done if the password is the Return character. If the password has been changed, it is necessary to enter the changed password.
For example, the system displays: OMC> Login completed successfully -> chg_level Enter password for security level you wish to access:... Current security level is 2 {27508} The chg_level command no longer fulfills any function in GSR9. It is supported in GSR9 only as a dummy command to ensure OMC-R scripts which require this command function correctly. It does not change the access level for a user as each user has a fixed access level which can only be changed by an omcadmin user. This command prompts for two passwords and the output is always: Current security level is 3.
68P02901W17-S
1-43 Dec 2009
Using the TTY interface to change to security level 2
Chapter 1: Configuration Management General Information
An example of an rlogin script using level two security is provided as follows: chg_level trace_call cell_number= all all no nth=10 2 200 no omc When executed on a GSR9 BSS, this script fails because the chg_level command expects two passwords to be entered. The solution is to modify the script so that it contains both the level three passwords instead of the level two password. This ensures that the script executes correctly on both GSR9 and pre-GSR9 BSS. The same script modified to use level three passwords is provided as follows: chg_level <1st level 3 password> <2nd level 3 password> trace_call cell_number= all all no nth=10 2 200 no omc
1-44
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Remotely logging in to a BSS using WebMMI
Remotely logging in to a BSS using WebMMI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to WebMMI WebMMI allows a user to access a BSS from any part of the world through a PC and the network operator's intranet, providing the PCU is attached to the Ethernet. For a full technical description of the WebMMI feature, see Technical Description: BSS Implementation (68P02901W36). When the connection to the PCU is established a WebMMI GUI is displayed through which a user can manage the BSS using BSS MMI commands.
WebMMI GUI The WebMMI GUI acts like a telnet session, where any commands allowed by the MMI or Executive Monitor (EMON) can be entered (as determined by the current security level). A user can also perform the following activities using the WebMMI GUI, as required: •
Logging - allows the user to store the data entered and displayed in the WebMMI GUI to a file on the hard drive. The MMI Shell and the EMON Shell can be logged to different files at the same time.
•
Script catting - allows the user to load a file from their hard drive and run the contents at either the MMI Shell or EMON Shell.
•
Repetitive commands - allows the user to run a single command at the MMI Shell or the EMON Shell any number of times, at any time required.
•
Aliasing - provides a GUI interface to the MMI and EMON command alias.
•
Quick-key aliasing - allows the user to assign commands to keystrokes.
•
BSS element descriptions - allows the user to display a short description of an element by typing the element name at the prompt. Element names can also be entered as part of a command, such as disp_element . 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-S
1-45 Dec 2009
Prerequisites for WebMMI
Chapter 1: Configuration Management General Information
Prerequisites for WebMMI At the BSS Before using WebMMI, ensure that the following requirements are met at the BSS: •
PCU is connected to the BSS.
•
Ethernet cable connects the PCU MPROC to either: the network operator's intranet, or a local dial-in server located next to the PCU. If MPROC redundancy is in use, the Ethernet cable must also be connected to the redundant MPROC.
At the PC Before using WebMMI, ensure that the following requirements are met at the PC: •
Windows™ or UNIX operating system is installed suitable for running a web browser.
•
A web browser, such as Microsoft® Internet Explorer Version 4+ or Netscape[Symbol_registersans] Navigator Version 4+ is available on the PC.
•
Java™ Runtime Environment version 1.3 (minimum) is available on the PC. If this is not already installed on the PC, the web browser displays prompts to load it before WebMMI can run.
Setting up and using WebMMI To set up WebMMI, complete the following procedures:
1-46
1.
Identify the Internet address details of the PCU to be connected to. If the details have not been set, enter the appropriate details.
2.
Load the WebMMI applet from the PCU to the PC. Once the applet is loaded at the PC, the WebMMI GUI appears.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Setting up and using WebMMI
These procedures are detailed as follows.
Identifying the PCU address details Use the following procedure to identify the PCU Internet address details (perform the steps only once for a PCU):
Procedure 1-20 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-8.
NOTE If a dial-in server is used, all the PCUs could have the same IP address since each PCU would be on its own network with its dial-in server installed on a PC next to it. Otherwise, if the PCUs are connected directly to hubs which connect into the network, each PCU should have its own IP address. 2
If the IP address, Router IP address and Subnet Mask fields have not been completed, and assuming the PCU device on the BSC is in a Busy-Unlocked State, enter the appropriate values. Alternatively, enter the following commands from either a terminal connected to the BSP TTY port at the BSC, or through a rlogin session at the OMC-R: modify_value pcu ip_address psp 0 modify_value pcu router_ip_address psp 0 modify_value pcu subnet_mask psp 0 If the system uses MPROC redundancy, type the following commands: modify_value 0 ip_address pcu 0 modify_value 0 router_ip_address pcu 0 modify_value 0 subnet_mask pcu 0
3
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 The system replies that the site is alive. If the site is not alive, check the network connections. If the PCU is connected to a dial-in server, dial-in to the server, log in to the network remotely, and then proceed.
Loading the WebMMI applet to the PC Before a PC can use WebMMI, an applet must be uploaded from the PCU to the PC. Perform the following procedure at the PC (which has access to the network on which the PCU resides).
68P02901W17-S
1-47 Dec 2009
Setting up and using WebMMI
Procedure 1-21
Chapter 1: Configuration Management General Information
Load WebMMI applet to PC
1
Start a web browsing tool (such as, Microsoft Internet Explorer 4+ or Netscape Navigator 4+).
2
Go to the following website: http:///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.
3
Once the applet is downloaded, Java Runtime Environment 1.3+ runs the applet. If the .java.policy file does not contain the necessary permissions (for example, when the PC accesses a new PCU), a window appears containing the required text. Copy and paste this text into the .java.policy file. The .java.policy file is located in your home directory (for example, in Microsoft® Windows™ inprofiles/ directory). If the .java.policy is updated, exit, and restart the web browser. Once the permissions are sufficient, the WebMMI GUI appears allowing the MMI Shell window to be opened. If security level 3 has been accessed, the EMON Shell window can also be opened.
Using the WebMMI GUI at the PC Use the following procedure to use the WebMMI GUI at a PC:
Procedure 1-22
Use WebMMI GUI at PC
1
Click the MMI Shell checkbox in the WebMMI GUI window. The MMIShell window opens. (If security level 3 has been accessed, the EMON Shell checkbox is also displayed.)
2
Enter the appropriate BSS MMI commands and parameters to manage the BSS, as required.
Exiting the WebMMI GUI To exit the WebMMI GUI at a PC, close the web browser, or go to a different web page (not WebMMI), or click the EXIT button in the WebMMI GUI window. (To exit a rlogin session in the EMON Shell, type exit.)
1-48
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Making wide area modifications
Making wide area modifications ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to wide area modifications Wide area modifications involve making amendments to database elements that are applicable to all sites, all BTSs, or all cells at a site.
Wide area modifications using the TTY interface Some BSS commands exist which permit wide area modifications. Some of the commonly used commands are listed and examples are given of using the commands with the all parameter. However, it is not sufficient just to issue the command; in some cases, an audit must be performed to update the OMC-R. The Local Maintenance flag must also be set so that TTY commands can be issued from the OMC-R (see Recommendations for Configuration Management on page 1-2 in this chapter for further details). Full details relating to the prerequisites, limitations of use, and the full syntax for all the commands detailed in this section are included in: Technical Description: BSS Command Reference (68P02901W23).
chg_element When used with the all input parameter, this command changes the database element to the specified value for all cells at the specified location. For example, to change the database element max_tx_bts to value 10 for all cells at site 1, issue the following command at the TTY command line interface: chg_element max_tx_bts 10 1 all
chg_A5_alg_pr Specifies A5 encryption algorithms in the order in which they are used by the BSS. For example, to prioritize the algorithms in the following order: A5/1, A5/2 for a BSS, issue the following command at the TTY command line: chg_a5_alg_pr 1 2
del_neighbor When used with the all input parameter, this command deletes all neighbor cells from a cell neighbor list. For example, to delete all cells from the neighbor list of cell 5 4 3 2 1 61986 34944, issue the following command at the TTY command line interface: del_neighbor 5 4 3 2 1 61986 34944 all
68P02901W17-S
1-49 Dec 2009
Propagating cell parameters using the OMC-R GUI
Chapter 1: Configuration Management General Information
modify_value When used with the all input parameter, this command modifies values for MMS, RSL or XBL devices. For example, to modify lapd_t200_timer to 2500 ms for every equipped RSL, issue the following command at the TTY command line interface: In SYSGEN mode: modify_value all lapd_t200_timer 2500 rsl
reset_site Used selectively to reboot available sites without remotely logging in. Typical scenarios could be: all sites including BSC, all sites excluding BSC, multiple sites and single site. For example to reboot all sites, issue the following command from the BSC: reset_site all_sites
Propagating cell parameters using the OMC-R GUI While chg_element is a useful command, it lacks the functionality provided by cell/neighbor parameter propagation features available from the OMC-R GUI. Cell parameters can be modified using the OMC-R GUI CELL Detailed View. The modified parameters are updated at the BSS and, if accepted, are then updated at the MIB. The user can propagate the settings to the appropriate cells under control of the OMC-R. A user can propagate cell modifications to: •
All cells within the site associated with the selected cell.
•
All cells within the BSS associated with the selected cell.
•
All cells controlled by the OMC-R in BSCs running the same version of BSC software.
•
All cells within the user's Region(s).
See Propagating cell parameters on page 8-76 for further details.
1-50
68P02901W17-S Dec 2009
Chapter
2 Configuring BSS Features ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The information provided here shows how BSS features can be configured to align to the requirements of the service provider. The following topics are described: •
Frequency hopping on page 2-3.
•
Enhanced XBL (EXBL) on page 2-10.
•
Dynamic Allocation of RXCDR-BSC Circuits (DARBC) on page 2-12.
•
Dynamic allocation of BSC-BTS Backing Resources (DYNET) on page 2-18.
•
MSC to BSS overload control on page 2-22.
•
Encryption algorithms on page 2-25.
•
Dual band cells option on page 2-27.
•
GPRS and EGPRS coding schemes on page 2-38.
•
Short Message Service - Cell Broadcast on page 2-43.
•
Short Message Service - Point-To-Point on page 2-51.
•
Preventive Cyclic Retransmission (PCR) on page 2-54.
•
MSC initiated IMSI and IMEI call trace on page 2-58.
•
Call trace flow control on page 2-61.
•
GPRS Trace on page 2-66
•
Enhanced Circuit Error Rate Monitor (ECERM) on page 2-68.
•
Advanced Load Management for EGSM on page 2-76.
•
Network Controlled Cell Reselection on page 2-79.
•
GPRS Interleaving TBFs on page 2-87.
•
GSM location services on page 2-102.
•
Enhanced GPRS One Phase Access on page 2-111.
•
Intelligent Multilayer Resource Management (IMRM) on page 2-148.
•
Quality of Service (QoS) on page 2-157.
•
Network Assisted Cell Change (NACC) on page 2-165.
68P02901W17-S Dec 2009
2-1
Propagating cell parameters using the OMC-R GUI
2-2
Chapter 2: Configuring BSS Features
•
Enhanced Multi-level Precedence and Pre-emption (eMLPP) on page 2-168.
•
Fast Call Setup on page 2-171.
•
RSL Congestion Control on page 2-173.
•
VersaTRAU on page 2-175.
•
Feature Capacity Licensing and Audit on page 2-178.
•
Improved Timeslot Sharing on page 2-179.
•
{27717} GPRS - Suspend/Resume on page 2-181.
•
{28398} Increased Network Capacity on page 2-184.
•
{23306} BSC High Load Protection Mechanism Phase 2 on page 2-186.
•
{28337} HSP MTL on page 2-188.
•
{25423} Software patching and PCU Software Upgrade with no BSC Outage on page 2-191.
•
{26740} High Bandwidth interconnection between BSC and PCU (PSI) on page 2-197.
•
{28351} Add new PCU hardware to increase GPRS capacity on page 2-193.
•
{28000} Increase the Throughput of PRP with the PCU on page 2-200.
•
{28938} Support of Incell as an optional feature on page 2-202.
•
{28340} BSP CPU utilization reduction for higher call handling capacity on page 2-203.
•
{27508} BSS User Security Management on page 2-204.
•
{27703A} Quality of Service Phase II on page 2-215.
•
{30828} CTU2-D on page 2-228.
•
{32340} Cell OOS Timer Enhancement on page 2-232.
•
{25002} TDM Availability Enhancements on page 2-233.
•
{31400} TD-SCDMA and GSM interworking on page 2-234.
•
{26881} Extended Uplink TBF (Temporary Block Flow) on page 2-237.
•
{23292} Extended Dynamic Allocation Medium Access Mode (EDMAC) on page 2-239.
•
{29693A} Adjustable FER Bins on page 2-241.
•
{34164} Critical Statistics Reporting in 5 minutes on page 2-242.
•
{34320G} SW enabler for PA bias switch on/off on CTU2D on page 2-244.
•
{34303} Dual Abis aware BTS on page 2-246.
•
{23311A} Extended Range Cell (ERC) for Data on page 2-248.
•
{34321}Cage Management on page 2-250
68P02901W17-S Dec 2009
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 signaling/traffic channel timeslot every frame, any RF channel interference is averaged with interference free channels. Restated, frequency hopping provides higher-quality communications when compared to the following: •
Frequency diversity.
•
Interference diversity.
Frequency hopping is described in detail in Technical Description: BSS Implementation (68P02901W36). Also see Configuring frequency hopping on page 8-163 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-165.
•
TTY interface, see Configuring frequency hopping using the TTY interface on page 8-173.
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-S
2-3 Dec 2009
Types of 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.
NOTE For EGPRS, baseband hopping is supported, but there are some restrictions due to the Horizon II macro controller: •
If the master cabinet is anything other than a Horizon II macro, baseband hopping cannot be supported.
•
EGPRS RTFs must be in a different hopping system from GPRS RTFs. There is no such restriction for synthesizer hopping. Firstly, Second,
Synthesizer frequency hopping (SFH)
NOTE Synthesizer frequency hopping cannot be implemented when RTCs (Remotely Tunable Combiners) are used. With synthesizer frequency hopping (SFH), both the transmit and receive RF carrier frequencies are changed each timeslot. This is accomplished by retuning the Radio Channel Unit (RCU). A cell equipped with a minimum of two DRI/RCU (RF carriers) can support hopping over a maximum of 64 frequencies. One DRI/RCU is dedicated for the BCCH (broadcast control channel) carrier. Cells with a small number of RF carriers are suited for SFH. Such cells are easily implemented with hybrid combiners, a requirement for SFH.
2-4
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
SFH guidelines (BCCH frequency excluded) with example
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. It is not determined by the cell RF channel allocation.
•
The mobile allocations for these hopping systems must exclude the BCCH carrier channel.
•
The non-BCCH timeslots of the BCCH carrier must not hop when using SFH so that mobiles can locate the BCCH carrier. This is a principle of GSM.
•
Excluding the BCCH carrier, the mobile allocation for these systems can include part of or all the cell allocation.
•
The mobile allocation must equal or exceed the number of DRIs in the cell that are to use the hopping system.
•
Select different HSNs in distant cells that share the same mobile allocation, avoiding HSN 0.
68P02901W17-S
2-5 Dec 2009
SFH guidelines (BCCH frequency excluded) with example
Chapter 2: Configuring BSS Features
Example of SFH with BCCH frequency excluded A typical cell allocation could include a BCCH RF channel and ten non-BCCH channels. Assuming that the cell is equipped with one DRI dedicated to the BCCH carrier and four DRIs dedicated to non-BCCH carriers, each SFH system would have to include at least four RF channels. The typical mobile allocations shown in Figure 2-1 split the non-BCCH cell allocation in half for two frequency hopping systems.
Figure 2-1
Typical SFH mobile allocations with BCCH frequency excluded
CELL ALLOCATION
MOBILE ALLOCATIONS
1 9
FREQUENCY
FREQUENCY
HOPPING SYSTEM 0
HOPPING SYSTEM 1
12 16
9
1
22
16
12
29
29
22
32
46
46 BCCH
88
32 69
52
RF CHANNEL
69 88 ti-GSM-SC01W17-000041-eps-sw
2-6
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
SFH guidelines (BCCH frequency included) with example
SFH guidelines (BCCH frequency included) with example Refer to the following guidelines to use SFH with BCCH frequency included: •
With SFH, the number of transceivers required in the cell is determined by the number of traffic channels to be supported; not by the cell RF channel allocation.
•
One of the mobile allocations for these hopping systems must exclude the BCCH carrier channel for assignment to the BCCH timeslot of the non-BCCH carriers.
•
Excluding the BCCH carrier, the mobile allocation for these hopping systems can include part of or all the cell allocation.
•
The mobile allocation must equal or exceed the number of DRIs in the cell that are to use the hopping system.
•
Select different HSNs in distant cells that share the same mobile allocation, avoiding HSN 0.
•
If using the BCCH frequency on non-BCCH carriers, then the non-BCCH timeslots cannot be used for traffic channels (hopping through the BCCH).
•
If not using the BCCH frequency on non-BCCH carriers, then the non-BCCH timeslots can be used for traffic channels. These channels are broadcasted at the maximum cell power.
Example of SFH with BCCH included A typical cell allocation could include a BCCH RF channel and ten non-BCCH channels. Assuming that hopping is to be assigned to all DRIs and that the cell is equipped with one DRI dedicated to the BCCH carrier and four DRIs dedicated to non-BCCH carriers: •
A system that hops through the BCCH channel would have to include at least five RF channels.
•
A system that does not hop through the BCCH channel would have to include at least four RF channels.
•
The typical mobile allocations shown in Figure 2-2 split the cell allocation into:
•
A 5-frequency allocation that does not include the BCCH frequency.
•
A 6-frequency allocation that includes the BCCH frequency.
68P02901W17-S
2-7 Dec 2009
Baseband frequency hopping (BBH)
Figure 2-2
Chapter 2: Configuring BSS Features
Typical SFH mobile allocations with BCCH frequency included
CELL ALLOCATION
1 9
MOBILE ALLOCATIONS
FREQUENCY
FREQUENCY
HOPPING SYSTEM 0
HOPPING SYSTEM 1
12
BCCH
16
9
1
22
16
12
29
29
22
32
46
32
46
88
69
52
RF CHANNEL
69 88 ti-GSM-SC01W17-000041-eps-sw
Baseband frequency hopping (BBH) With baseband frequency hopping (BBH), only the receive RF carrier frequencies are changed each timeslot; the transmit RF carrier is obtained from a different, fixed tuned Radio Channel Unit (RCU) each timeslot. A cell equipped with up to 25 DRI/RCU (RF carriers) can support hopping over a maximum of 25 frequencies. Cells with a large number of RF carriers are well suited for BBH. Such cells are usually implemented with Remotely Tuneable Combiners (RTCs) and therefore restrict the selection to BBH at the site.
NOTE Timeslot 0 of the BCCH cannot baseband hop.
2-8
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
BBH guidelines with typical example
BBH guidelines with typical example Refer to the following guidelines to use baseband frequency hopping: •
With BBH, the number of transceivers required in the cell is determined by the number of RF channels in the mobile allocation; not by the number of traffic channels to be supported.
•
The mobile allocation in a system to be assigned to the BCCH timeslot of non-BCCH carriers must exclude the BCCH carrier channel.
•
Select different HSNs in distant cells that share the same mobile allocation, avoiding HSN 0.
A typical cell allocation would include a BCCH RF channel and four non-BCCH channels in a cell equipped with one DRI dedicated to the BCCH carrier and four DRIs dedicated to non-BCCH carriers. The typical mobile allocations shown in Figure 2-3 split the cell allocation into: •
A 4-frequency allocation that does not include the BCCH frequency.
•
A 5-frequency allocation that includes the BCCH frequency.
Figure 2-3
Typical example of BBH mobile allocations
CELL ALLOCATION
MOBILE ALLOCATIONS
FREQUENCY HOPPING SYSTEM 0
FREQUENCY HOPPING SYSTEM 1
32 32 46
32 46
BCCH
46 52
RF CHANNEL
52 69 69
69
88 88
88
ti-GSM-SC01W17-000043-eps-sw
68P02901W17-S
2-9 Dec 2009
Enhanced XBL (EXBL)
Chapter 2: Configuring BSS Features
Enhanced XBL (EXBL) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of Enhanced XBL Enhanced XBL (EXBL) provides communication between the BSC and the RXCDR. To maintain this communication, the RXCDR and BSC have information stored in their databases which details all the other RXCDRs and BSCs with which with they can communicate. To ensure that traffic pathways are properly established, the EXBL feature performs runtime checks of database consistency and connectivity between the BSC and RXCDR. These checks ensure that the user has configured both the RXCDR and BSS databases correctly. •
The connectivity checks verify that for each E1 device, which the BSS database has indicated is connected to an RXCDR, there exists a corresponding E1 device in the RXCDR connected to the BSS.
•
The consistency checks verify that for each CIC (Circuit Identity Code) device equipped to a particular E1 device at the BSC, there exists a corresponding RXCDR channel in the RXCDR database.
If any of these consistency or connectivity checks fail, the user is notified so that they can take the appropriate action. The BSS also automatically disables the relevant CIC devices to ensure they are not used. Another user visible aspect is that indications regarding maintenance activity or faults occurring at the RXCDR which indirectly affect BSC link devices are forwarded to the BSC for processing. For example, if the MMS at the RXCDR which is carrying the OML link from the BSC is locked, the RXCDR forwards this information to the BSC. The BSC then disables the OML. Support of the signaling link between the RXCDR and BSC is not new, however, EXBL significantly changes the RXCDR and BSC interface. For example, CIC validation is enabled and provisioning of at least one XBL per RXCDR-BSC pair is mandatory to ensure that the traffic carrying capability of the interface is available. EXBL supports RXCDRs which use either existing nailed connect information or CIC information available from the DARBC feature. 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).
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.
2-10
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
CIC blocking and validation
CIC blocking and validation
NOTE This section applies when XBLs are in use and CIC validation is enabled at the BSC for a given XBL. To ensure that the BSS is always using valid traffic circuit identity codes (CIC) to carry calls, the BSS blocks any CIC at the BSC which cannot be verified to be in good working order. Blocking a CIC informs the MSC that the CIC should not be used for calls. When using remote transcoding, the only way to determine if a CIC is in good working order is to communicate with the RXCDR. If nothing is wrong at the RXCDR that would affect the CIC, the BSC allows the CIC to remain in operation provided no other blocking condition exists. If the RXCDR indicates that something is wrong, the BSC blocks the CIC from use. If the BSC cannot communicate with the RXCDR, the BSC has no way to determine the validity of any CIC connected through that RXCDR. In this case, the BSC blocks all the CICs connected to the RXCDR to ensure no calls use the potentially corrupt CICs. The user must enable the CIC validation option before CICs can be blocked due to RXCDR/BSC communication failure, see Configuring an Assoc_RXCDR on page 4-73.
Enabling CIC validation To specify whether the BSC performs CIC validation when the XBL linkset to the RXCDR comes in-service, or when the XBL linkset is already in service, use the field: CIC Validation (BSS naming convention: cic_validation) in the Local Routing Information grouping of the Assoc_RXCDR Detailed View. This parameter can be set to Disabled (No) or Enabled (Yes). When cic_validation is Disabled (No), the RXCDR can be referred to as in Backwards Compatibility mode or Static mode. This refers to a BSC or RXCDR in which the Ater channels and CICs are statically switch connected. This mode does not provide any fault tolerance or CIC validation, and is intended only to provide an upgrade path. When the BSC and RXCDR are upgraded, the use of Auto-connect mode is recommended. When cic_validation is Enabled (Yes), the RXCDR enters Auto-connect mode. In Auto-connect mode, Ater channels are allocated and released dynamically as resources are provisioned, un-provisioned, or during handling of fault condition. Auto-connect mode provides fault tolerance along with the call processing efficiency of Backwards compatibility mode. This is the recommended mode of operation for the BSC.
NOTE If CIC Validation is enabled, XBLs must be equipped on the RXCDR and BSC. If no XBLs are equipped and the AXCDR is operating in Auto-connect mode, all CICs at the BSC associated with the AXCDR are blocked and no call traffic goes to the AXCDR.
68P02901W17-S
2-11 Dec 2009
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 The dynamic allocation of Remote Transcoder (RXCDR) to BSC Circuits (DARBC) feature provides fault management for call traffic on the BSC to RXCDR interface (referred to as the Ater interface) by managing the individual 16 kbit/s channels (called Ater channels) on this interface. In addition, this feature provides for validation of the Circuit Identity Code (CIC). It also provides Ater channel provisioning between the BSC and RXCDR to ensure that calls are placed on the correct circuit between the BSC and the MSC. Without this feature in place, fault management of the Ater channels is not possible. In addition, all Ater and CIC information would have to be manually verified by the user. This feature is consistent with the Terrestrial Circuit Device Management (TCDM) feature with respect to how the operator is permitted to manage the CIC devices. DARBC is an unrestricted feature. For further technical details, see Technical Description: BSS Implementation (68P02901W36).
BSC and RXCDR responsibilities The DARBC feature redefines the roles for both the BSC and RXCDR within the BSS network. However, these changes are transparent to other GSM network entities, such as BTSs and MSCs. In redefining the responsibilities, a client/server approach is used where the BSC is the client to the RXCDR server. For example, the RXCDR has the resources (CICs) that the BSC wants to access, yet the BSC has the intelligence to know which CIC to use. The BSC responsibilities are as follows:
2-12
•
Track CIC utilization.
•
Track Ater channel utilization.
•
Allocate/deallocate Ater channels, as necessary.
•
Instruct the RXCDR to make switch connections between the Ater channel and transcoder and rate adaptor unit (TRAU).
•
Initiate and execute audits of the CIC and Ater information.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Auto-connect mode or backwards compatibility (static) mode
The RXCDR responsibilities are as follows: •
Inform the BSC when activity (due to faults or operator actions) at the RXCDR affects the usability of Ater channels and/or CICs.
•
Make switch connections between the Ater channels and TRAU resource when instructed by the BSC.
•
Ensure that Ater channels and CICs are switch-connected to the proper idle tone at the proper times.
•
Provide the BSC with the necessary CIC and Ater information for auditing.
•
Handle the error case where the BSC does not initiate the audit procedure.
Auto-connect mode or backwards compatibility (static) mode Auto-connect mode This is a user-selectable mode which refers to a BSC in which Ater channels are allocated and released dynamically as resources are provisioned, un-provisioned, or during handling of a fault condition (as opposed to a per-cell basis). Auto-connect mode provides fault tolerance along with the call processing efficiency of backwards compatibility mode. BSC controls the Auto-connect mode.
NOTE Before the introduction of this feature, all Ater channels were statically assigned and the use of XBL links was not mandatory. If an operator decides to use the Auto-connect mode, it becomes imperative to equip XBL links on the RXCDR and BSC. If no XBLs are equipped, and the AXCDR is operating in the Auto-connect mode, all CICs at the BSC associated with the AXCDR become blocked and call traffic does not go to the AXCDR. Auto-connect mode is the recommended mode of operation for the BSC. Auto-connect mode is set using the AXCDR parameter cic_validation, see Enhanced XBL (EXBL) on page 2-10 for further details. For example, if there are six RXCDRs connected to the BSC, enable cic_validation for the six corresponding AXCDRs.
Backwards compatibility mode (or static mode) This is a user-selectable mode which refers to a BSC and/or RXCDR in which the Ater channels and CICs are statically switch connected. (Before DARBC, all Ater channels were statically assigned) This mode does not provide any fault tolerance or CIC validations. When upgrading the network (especially when upgrading the BSC before the RXCDR), Backward compatibility mode should be used for the corresponding AXCDR, otherwise all the associated CICs become blocked. Once both BSC and RXCDR are upgraded, the use of Auto-connect mode is recommended. Backwards compatibility mode is set using the parameter cic_validation, see Enhanced XBL (EXBL) on page 2-10 for further details. 68P02901W17-S
2-13 Dec 2009
Determining the number of XBLs required
Chapter 2: Configuring BSS Features
Network provisioning issues for dynamic allocation Moving from a static allocation system to a dynamic allocation system (Auto-connect mode) presents some issues that should be considered when planning and provisioning the BSC/RXCDR network. For example, when in Auto-connect mode, a CIC no longer has a fixed position on the Ater interface. Instead, a CIC may be seen as belonging to a pool of CICs where a separate pool is maintained for each RXCDR connected to the BSC. When a call is assigned to a CIC, the BSC allocates an Ater channel that goes to the same RXCDR as the assigned CIC. One implication of such a pooling is that the number of CICs equipped that go through the RXCDR may not be the same as the number of Ater channels from the BSC to the RXCDR, as compared to the static allocation system.
NOTE The allocation information used by DARBC relies on what is entered when equipping CICs, both at the BSC and RXCDR plus how a particular MMS is provisioned (that is, using chg_ts_usage or equip of a link). Therefore, the use of equip and disp_equip of CICs, disp_mms_ts_usage and disp_connectivity commands are essential for the user to properly manage and maintain the system.
Determining the number of XBLs required XBLs carry the signaling traffic between BSC and RXCDR. The number of XBL links required depends upon the number of CICs and/or the number of Ater interface channels.
Planning considerations The following factors are considered when planning the number of XBL links from BSC to RXCDR:
2-14
•
Determine the traffic requirements of the BSC and/or the number of trunks (CICs) used between the BSC and AXCDR.
•
Determine the mode (Backward Compatibility or Auto-connect) in which the BSC and RXCDR operate.
•
A maximum of 20 XBLs (64 kbit/s or 16 kbit/s) can be configured for a BSC/RXCDR.
•
A BSC can connect to a maximum of ten RXCDRs.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
RXCDR-BSC dynamic allocation parameters
Provisioning The number of XBL links depends on the number of trunks on the BSC-RXCDR interface and whether the Auto-connect mode is enabled at the RXCDR/BSC. Table 2-1 details the minimum number of XBLs required to support the given number of trunks between the BSC and RXCDR, with Auto-connect mode.
Table 2-1
Number of BSC to RXCDR signaling links
N = number of MSC to BSC trunks
No redundancy
With redundancy
Number of 64 kbit/s XBLs
Number of 16 kbit/s XBLs
Number of 64 kbit/s XBLs
Number of 16 kbit/s XBLs
N < 1200
1
4
2
8
1200 < N < 2400
2
8
4
16
NOTE The figures mentioned in Table 2-1 , only apply to Auto-connect mode. The redundancy values are two times the non-redundancy values. When using Backwards Compatibility mode (cic_validation is off for the corresponding AXCDR device), technically there is no requirement to equip any XBLs, but it is good practice to equip at least two 16 kbit XBLs for each AXCDR. In Backwards Compatibility mode, the only traffic on the XBL is CIC block/unblock information, which is very minimal; although one XBL link is sufficient, built in redundancy should also be considered.
RXCDR-BSC dynamic allocation parameters Table 2-2 details the parameters associated with RXCDR-BSC dynamic allocation. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of commands and parameters, see Technical Description: BSS Command Reference (68P02901W23).
Table 2-2
RXCDR-BSCdynamic allocation parameters
OMC-R GUI field name/BSS parameter name Network Entity Id network_entity_id
Description Located in the Identification grouping of the BSS Detailed View. Indicates the unique identification of the network element. When the BSS is created from the BSS, the user must assign a unique value to this parameter in the range 1 254. When a user creates a BSS from the OMC-R, the default identifier is the next free number in the range.
Values 1 - 254
Continued
68P02901W17-S
2-15 Dec 2009
Methods of configuring dynamic allocation of RXCDR-BSC circuits
Displayed in the Identification grouping of the BSS Detailed View. Indicates whether transcoding is performed locally at the BSS or remotely at an RXCDR. Once set (at BSS creation), it cannot be changed. Instead the BSS must be deleted/unequipped and recreated.
Local (1) Remote (0) Default: Remote (0).
fm_site_type
Indicates the configuration of the site. Not visible to a user (it is derived internally from other parameters).
BSC (1) BTS (2) RXCDR (3)
Also see parameter cic_validation in Enhanced XBL (EXBL) on page 2-10.
Methods of configuring dynamic allocation of RXCDR-BSC circuits RXCDR-BSC dynamic allocation parameters can be configured using: •
OMC-R GUI BSS Detailed View and the fields detailed in Table 2-2.
•
TTY interface, see Configuring RXCDR-BSC dynamic allocation using the TTY interface.
Configuring RXCDR-BSC dynamic allocation using the TTY interface Displaying information for a BSS To display information for a BSS, use the disp_equipment or disp_bss commands. For example, the following command displays information for the local transcoding BSS 16: disp_equip 0 BSS 16
Changing the network entity id of a BSS To change the network entity identity of a BSS, use the modify_value command and the network_entity_id parameter. For example, the following command changes the local transcoding BSS id 17 from 17 to 16: modify_value 0 network_entity_id 16 BSS 17 If an attempt is made to change the network_entity_id of a remote transcoding BSS, the following message is displayed: Changing the BSS id will cause all AXCDRs to be cycled which will result in the
2-16
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration RXCDR-BSC dynamic allocation using the TTY interface
Configuring
loss of all call traffic. Are you sure (yes/no)?
Displaying the RXCDR-BSC dynamic allocation settings To display the current local_transcoding setting, use the disp_equipment or disp_bss commands. For example: disp_equip 0 BSS 22 The system responds by displaying the following information, for example: BSS Identifier: 22 Is transcoding performed at the BSC? No
Equipping CICs See Configuring a CIC on page 9-46 for details of how to configure CICs.
68P02901W17-S
2-17 Dec 2009
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)
NOTE BSC-BTS dynamic allocation is not supported for M-Cell and Horizon products. It is only available for InCell and in-building systems. BSC-BTS dynamic allocation is an alternative mechanism for allocating radio resources between a BSC and a BTS. BSC-BTS Dynamic allocation is also referred to as BTS concentration or Dynamic Network of BTSs (DYNET). Before BSC-BTS Dynamic allocation was available, terrestrial backing resources between the BSC and BTS were allocated when RTFs were equipped. This mechanism can still be used, but BSC-BTS dynamic allocation allows the operator to enable dynamic allocation of terrestrial backing resources for each BTS. When BSC-BTS dynamic allocation is enabled, when a call is placed on a TCH the terrestrial backing resource is allocated. When the call leaves a TCH, the terrestrial backing resource is freed. The terrestrial backing resource is a 16 kbit/s portion of a timeslot on a span and is allocated by the BSC from a pool of available resources. This pool is shared by every BTS the user specifies, and which are within the same network configuration. BSC-BTS dynamic allocation can be used for spoke, daisy chain and closed loop daisy chain network configurations. Two network objects are required for BSC-BTS dynamic allocation; a Dynet, and a DynetGroup. For a full technical description of BSC-BTS dynamic allocation, see Technical Description: BSS Implementation (68P02901W36).
RSL TCHs used for backhaul If the RSL at the BTS containing the cell is set to use 16 kbit/s (parameter: rsl_rate) and ts_sharing is enabled at the BTS, the remaining three 16 kbit/s TCHs on the RSL 64 kbit/s timeslot are used for backhaul for that BTS only. This means there are three additional TCHs that can be used by any cell at that BTS only. In addition, the three additional TCHs are reserved only for cells at the site with 16 kbit/s RSL. Other BTSs in the Dynet may not use the additional three TCHs. For example, if there are 10 timeslots in the Dynet, 40 TCHs are available to all cells in the Dynet. If BTS1 has a 16 kbit/s RSL and BTS2 has 64 kbit/s RSL, then cells at BTS1 have 43 TCHs available to share with the other cells at BTS1. In this example, the maximum number of TCHs allocated to all cells in the Dynet cannot exceed 43. If all RSLs are 64 kbit/s in the Dynet, the maximum TCHs allocated cannot exceed 40.
2-18
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Prerequisites to enabling BSC-BTS dynamic allocation at a BTS
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-91 for details of associated BSC-BTS dynamic allocation Dynet parameters.
Displayed in the BSS Detailed View à Optional Features grouping. Displays whether BSC-BTS dynamic allocation for the BSS is enabled or disabled. A user cannot change it.
Enabled (1) Disabled (0)
Timeslot Sharing ts_sharing
Displayed in the SITE Detailed View, Local Routing Information grouping. This parameter field is grayed out for SITE0 (BSC). Enables or disables BSC-BTS dynamic allocation for the BTS at the time of creation only. Once a BTS has been created, it cannot be reset. Only accessible when BSC-BTS dynamic allocation is Enabled (1).
Enabled (1) Disabled (0) Default: Disabled (0)
Dynet Retry Time dynet_retry_time
Displayed in the BTS SITE Detailed View, Local Routing grouping. This parameter field is grayed out for SITE0 (BSC).
150 - 3000 ms Default: 1000
Values
The retry time used by the BTS when requesting a terrestrial backing resource from the BSC. The BTS tries three times to get terrestrial backing resources before deciding a TCH cannot be allocated due to lack of resources. Only accessible when BSC-BTS dynamic allocation and Timeslot Sharing are Enabled (1). Continued
68P02901W17-S
2-19 Dec 2009
Displaying if BSC-BTS dynamic allocation is unrestricted at a BSS
Table 2-3
Chapter 2: Configuring BSS Features
BSC-BTS dynamic allocation parameters (Continued)
OMC-R GUI field name/BSS parameter name Total TCHs Reserved dynet_tchs_reserved (OMC-R parameter name: dynet_tchs_rsvd)
Description Displayed in the CELL Detailed View, General section, Local Routing Information grouping. The amount of terrestrial backing resources (TCHs) reserved for a cell. Only available when BSC-BTS dynamic allocation is enabled for the BTS containing this cell (that is, ts_sharing is enabled). Otherwise the field is grayed-out in the CELL Detailed View and is set to 0. If the user attempts to set a value so that the total reserved cell capacity exceeds the terrestrial backing resources for the BTS network, the BSS rejects the request.
Values 0 - 32 traffic channels Default: 0
Displaying if BSC-BTS dynamic allocation is unrestricted at a BSS To display if the optional BSC-BTS dynamic allocation feature is unrestricted (enabled) at a BSS using the OMC-R GUI, look in the Optional Features grouping of the BSS Detailed View. If the feature is unrestricted, Enabled (1) is displayed in the BSC-BTS dynamic allocation Feature field (BSS parameter name: BSCBTSDynAllocOpt). If the feature is restricted, Disabled (0) is displayed.
Enabling BSC-BTS dynamic allocation at a BTS To enable BSC-BTS dynamic allocation at a BTS using the OMC-R GUI, use the SITE Detailed View and the Local Routing grouping parameters as detailed in Table 2-3. To enable BSC-BTS dynamic allocation at a BTS using the TTY interface, use the equip command. For full details of the equip command, see Technical Description: BSS Command Reference (68P02901W23).
Displaying details of an equipped BTS using the TTY interface To display details for an equipped BTS, including whether BSC-BTS dynamic allocation is enabled, use the disp_equip command. For example, to display the details for BTS 1, enter the following command: disp_equip 0 site 1 The system responds by displaying all the BTS details. For full details of the disp_equip command, see Technical Description: BSS Command Reference (68P02901W23).
2-20
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Other dynamic allocation features
Other dynamic allocation features Dynamic allocation of RXCDR-BSC circuits (DARBC) enables E1 connection between the RXCDR and BSC channels between the RXCDR and BSC to be assigned to calls as needed, rather than statistically assigning such channels to CIC. See Dynamic Allocation of RXCDR-BSC Circuits (DARBC) on page 2-12 for further details.
68P02901W17-S
2-21 Dec 2009
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. 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-22
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-4
Methods of configuring MSC to BSS overload control
Timer parameters for mobile access class barring
OMC-R GUI field name/BSS parameter name
Description
Flow Control T1 Timer flow_control_t1
Displayed in the CELL Detailed View, Flow Control parameter grouping. Indicates the time that must elapse before new overload messages are considered by the Flow Control mechanism. Multiple OVERLOAD messages may be sent from the MSC to the BSS. There is a danger that the access classes will be barred far too rapidly, resulting in all access classes being restricted throughout the BSS. To guard against this a timer is started on reception of an OVERLOAD message. This timer is called T17. The BSS ignores all subsequent OVERLOAD messages received after the first instance until T17 expires. When T17 has expired the next OVERLOAD message received by the BSS results in the next access class being barred and T17 is restarted. Timer T17 duration is set by flow_control_t1. Valid values are: 0 - 1000000 (ms). Default is 20000.
Flow Control T2 Timer flow_control_t2
Displayed in the CELL Detailed View, Flow Control parameter grouping. Indicates the time that must elapse before a previously flow control barred access class is brought back in service. There is no message sent from the MSC to the BSS notifying the BSS that the MSC processor overload condition has cleared. The unbarring of the access classes to increase the traffic to the MSC is controlled by a timer. This timer is called T18. This timer is also started when the first OVERLOAD message is received. If no subsequent OVERLOAD message has been received when the T18 timer expires then the BSS will unbar an access class. The T18 timer is then restarted, unless all of the access classes are now unbarred. Timer T18 duration is set by the flow_control_t2 parameter. The reception of an OVERLOAD message after the expiry of T17, but before the expiry of T18, results in the barring of a mobile access class and both timers T17 and T18 are restarted. Valid values are 0 - 1000000 (ms). Default is 3000.
Methods of configuring MSC to BSS overload control A user can configure MSC to BSS Overload Control, using either of the following methods: •
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-S
2-23 Dec 2009
Configuring MSC to BSS overload control using the TTY interface
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 ms for flow_control_t1, use the chg_element command as follows: chg_element flow_control_t1 1500
2-24
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Encryption algorithms
Encryption algorithms ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to encryption algorithms Encryption/decryption provides security for user speech, data, and signaling information. The encryption feature is optional and for effective use must be deployed at the MSC, BSS, and the MS. Parallel operation of the A5/1, A5/2 and Null encryption algorithms are supported at BSS level.
Prerequisites for configuring encryption algorithms To configure encryption algorithms, the encryption feature (multiEncryptOpt) must be unrestricted (Enabled).
Encryption algorithm procedures These procedures are described in the following sub-sections: •
Activating the specific encryption algorithm using the chg_element command.
•
Prioritizing the order in which the encryption algorithms are to be used by the BSS using the chg_a5_alg_pr command.
•
Displaying the prioritized list of encryption algorithms used at the BSS using the disp_a5_alg_pr command.
Activating the encryption algorithms To activate the encryption algorithms, use the chg_element command and either the option_alg_a5_1 (A5/1) or option_alg_a5_2 (A5/2) parameter (detailed in Table 4-6). For complete details of the commands used, refer to: Technical Description: BSS Command Reference (68P02901W23).
68P02901W17-S
2-25 Dec 2009
Prioritizing the 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 [] [] [] [] [] [] [] For example, to prioritize the encryption algorithms in the following order: A5/2, A5/1, the command is: chg_a5_alg_pr 2 1 To set no encryption, the command is: chg_a5_alg_pr 0 The BSS provides the capability to send a Cipher Mode Reject message to the MSC (if the MSC supports this message). This message is sent when a problem is encountered during the signaling encryption process when the MS and the system are attempting to perform encryption. To enable this capability, the command is: chg_element ciph_mode_rej_allowed 1 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-26
68P02901W17-S Dec 2009
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. Configure all SDCCHs in the cell on the primary band/outer zone. (This is consistent with the Concentric Cells feature, which requires the BCCH and SDCCHs to be configured in the outer zone carriers.) An example of a system which could utilize the Single BCCH for Dual Band Cells feature is an established PGSM network with access to DCS1800 frequencies, and a subscriber base populated with a sufficient number of multiband capable mobiles. In this situation, the DCS1800 frequencies can be allocated as non-BCCH carriers added to existing PGSM cells. The PGSM is the primary band and the DCS1800 is the secondary band for the dual band cell. Single BCCH for Dual Band Cells feature permits configuration of carriers with only two different frequency types at the cell level for the following frequency bands: •
PGSM/EGSM.
•
DCS1800.
Either of these bands can be assigned as the primary band for the cell. When the Dual Band Cells feature is enabled for a cell, the frequency type is managed on a per zone basis. Primary band carriers are configured in the outer zone (providing total cell coverage), and secondary band carriers are configured for the inner zone. GPRS is not supported on the secondary band within a Dual Band cell. See Technical Description: BSS Implementation (68P02901W36) for a full description of this feature.
68P02901W17-S
2-27 Dec 2009
Overview of the single BCCH for a dual band cells feature
Chapter 2: Configuring BSS Features
Benefits Single BCCH for Dual Band Cells feature provides a: •
Convenient way of expanding system capacity by utilizing frequencies from the secondary band (provided sufficient multiband subscriber population exists). This enables system capacity to be increased without modifying either the frequency plan of the primary frequency or the associated neighbor list.
•
Reduction in the number of cells required in the database.
•
Reduction in the management of neighbor lists.
Areas impacted The areas primarily impacted by the Single BCCH for Dual Band Cells feature include configuration, inner zone use algorithms, channel selection algorithms, and handover and power control. Also, the BSS: •
Supports two different frequency bands within a single cell using a concentric cells configuration.
•
Allows the network operator to define the coverage area of the primary and secondary bands independently using BSS parameters.
•
Enhances the channel allocation algorithms to incorporate selection of channels from different frequency bands and ensure that the allocation of the secondary band inner zone) resource at TCH assignment when qualifications are met.
•
Provides power level conversions for intra-cell channel changes and incoming inter-cell handovers between channels on different frequency bands.
Impact on RTFs and DRIs Normally, there is an RTFGroup for each cell, and one of these RTFs is a BCCH RTF. The Dual Band Cells Option 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:
2-28
•
Are non-BCCH.
•
Are in the inner cell zone.
•
Have ARFCN frequencies in the secondary band.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Interaction with other features
Influence of concentric cells, multiband, and congestion relief features The single BCCH for dual band cells feature requires inter-zone traffic management to control the two frequency bands within the single cell. This is provided by the concentric cells feature (concentricCellOpt). The concentric cells feature inter-zone traffic management is handled by the power based use algorithm which manages traffic between zones using algorithms based on uplink and downlink receive levels, as well as network operator preferences defined by the outer_zone_usage_level parameter. Traffic is managed between frequency bands of different cells using the MultiBand Inter-Cell H/O feature (mbInterCellHoOpt) by using algorithms based on frequency types of the serving cell neighbor cells, as well as network operator preferences defined by the band_preference and band_preference_mode parameters. To achieve a satisfactory algorithm for inter-zone traffic management with the dual band cells feature, the concentric cells feature power-based use algorithm has been enhanced with the MultiBand Inter-Cell H/O feature inter-band traffic management shifted from an inter-cell level to an intra-cell level. The resulting inner zone use algorithm for dual band cells feature verifies that the MS supports the frequency band of the inner zone before evaluation of the receive levels. If unrestricted and enabled, the alternative congestion relief Feature (congestReliefOpt) (that is, Directed Retry alternatives) is applied to dual band cells. This can also include enabling Enhanced Congestion Relief (ECR) (enhanced_relief). See BSS and CELL Detailed Views for the related parameter fields.
Interaction with other features This feature interacts with the IMRM feature, see Intelligent Multilayer Resource Management (IMRM) on page 2-148 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.
68P02901W17-S
2-29 Dec 2009
Dual band cells option parameters
Chapter 2: Configuring BSS Features
Dual band cells option parameters Table 2-5 shows the parameters associated with the Dual Band Cells feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. A full description of BSS database parameters is provided in Technical Description: BSS Command Reference (68P02901W23).
Table 2-5
Single BCCH parameters
OMC-R GUI field name/BSS parameter name Dual Band Cells Option (OMC-R parameter name: dualBandCellOpt)
Inner Zone Algorithm inner_zone_alg
Description Displayed in the BSS Detailed View à Optional Features grouping. Displays whether the Dual Band Cells feature has been enabled for this BSS. Valid values are: •
Enabled (1)
•
Disabled (0)
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. Displays the algorithm used to hand into the inner zone. Valid values are: •
Disabled (0).
•
Power Based Use Algorithm (1).
•
Interference based Use Algorithm (2).
•
Dual Band Cell Use Algorithm (3).
The Interference based Use algorithm (2) determines that an intra-cell handover should occur based on interference levels from neighbor cells which use an interfering frequency. The Power based Use Algorithm (1) determines that an intra-cell handover should occur based on power control algorithms. The Dual Band Cell Use Algorithm (3) can only be used when the Dual Band Cell option is enabled. This algorithm provides the capability to manage cells with carriers from two different frequency bands. When the Dual Band Cells feature and MultiBand (mb_preference) are enabled for a BSS, no RTFs are equipped for the inner zone, and coincident_mb is disabled, this parameter can be set to Dual Band Cell Use Algorithm (3). This indicates the cell is a dual band cell. If the primary frequency_type is PCS1900, this parameter cannot be set to 3. When set to 3, prompts for the following are displayed: BTS Max Transmit Pwr for Inner Zone (bts_txpwr_max_inner), Secondary Frequency Type (secondary_freq_type), Max MS Transmit Power When HO to Inner zone (ms_txpwr_max_inner), Inner Zone Handover Hysteresis (zone_ho_hyst), Inner Zone DL Receive Level Threshold (rxlev_dl_zone), Inner Zone UL Receive Level Threshold (rxlev_ul_zone) and HO Power level for Inner Zone (ho_pwr_level_inner). Continued
2-30
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-5
Dual band cells option parameters
Single BCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Dual Band Offset dual_band_offset (OMC-R parameter name: dualBand_offset)
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. Specifies the offset used when calculating the power budget using measurement information from a secondary band channel. Valid value range is: -63 to +63. The default is 0.
Power Budget Mode pbgt_mode
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. Specifies for the preferred method of compensating for a mismatch in frequency types between the serving channel and the neighbor cell BCCH when calculating power budget. Valid values are:
Second Frequency Type secondary_freq_type (OMC-R parameter name: second_freq_type)
•
0 - the MS uses the serving channel measurements for the secondary band with the addition of the dual_band_offset to calculate the power budget.
•
1 - the MS uses the reported serving cell signal strength for the primary band (Through modified SACCH System Information messages) to calculate the power budget. The BCCH frequency of the serving cell is added to the BA SACCH neighbor cell list of the serving cell.
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. When a cell is configured as dual band, this parameter specifies the frequency type of the inner zone, secondary band of the cell. Valid values are: •
PGSM (1).
•
EGSM (2).
•
DCS1800 (4).
BTS Max Transmit Pwr For Inner Zone bts_txpwr_max_inner (OMC-R parameter name: btsTxPwrMax_inner)
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. When inner_zone_alg is set to 3, indicating the cell is a dual band cell, this parameter specifies the BTS maximum transmit power for the secondary band/inner zone. Valid values depend on the equipment type and are detailed in Technical Description: BSS Command Reference (68P02901W23). For example, for PGSM, EGSM and DCS1800 cells, and M-Cell6, Horizonmacro or Horizon II macro controlling BTS cabinets, the range is -1 to 21.
HO Power level for Inner Zone ho_pwr_level_inner (OMC-R parameter name: hoPwrLevel_inner)
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. When the cell is configured as a dual band cell, this parameter specifies the handover power level for the inner zone. Valid range is: 0 - 19 and 29 - 31 (that is, the same as for handover_power_level except based on the secondary_freq_type, not the primary frequency_type). The default value is 2. Can only be modified when Dual Band Cell Option is enabled. Continued
68P02901W17-S
2-31 Dec 2009
Dual band cells option parameters
Table 2-5
Chapter 2: Configuring BSS Features
Single BCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Coincident MB HO Status coincident_mb
Displayed in the CELL Detailed View, General section, Coincident Multiband HO grouping. Determines whether the Coincident Multiband HO feature is enabled or disabled at the cell. Can only be modified if the MultiBand feature is unrestricted. Cannot be enabled if the cell is configured as a dual band cell (that is, inner_zone_alg is set to 3) Valid values are 0 - 3: 0 - Coincident MultiBand is disabled at this cell. 1 - Coincident cell handovers are enabled 2 - Coincident cell handovers and coincident cell redirections are enabled 3 - Intra BSC handovers behave the same as coincident_mb = 2. But for inter BSC handovers, the call is targeted at the primary cell.
MultiBand Enabled mb_preference
Displayed in the BSS Detailed View, Multiband grouping. Determines whether the MultiBand feature is enabled or disabled for the BSS. Can only be modified if the MultiBand Inter-Cell Handover feature is unrestricted (Enabled). Cannot be disabled if there are cells at this BSS that are configured as a dual band cell (that is, inner_zone_alg is set to 3).
Cell Transmit Power tx_power_cap
Displayed in the CELL Detailed View, General section, General grouping. Determines whether the cell transmits at high or low power. Only valid for cells that are configured as dual band cells (that is, inner_zone_alg is set to 3), regardless of the frequency type of the cell.
Max MS Transmit Pwr When HO to Inner Zone ms_txpwr_max_inner
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. Determines the maximum transmit power of the mobile station when handing over from the outer zone to the inner zone. Only valid for cells that are configured as dual band cells (that is, inner_zone_alg is set to 3). The valid range is then dependent on the secondary band frequency type. Otherwise, the range is dependent on the primary frequency type.
Inner Zone Handover Hysteresis zone_ho_hyst
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. Determines the hysteresis added to the threshold to determine if an outer zone to inner zone handover should take place. Only valid for cells that are configured as dual band cells (that is, inner_zone_alg is set to 3). The valid range is then -63 to 63. Otherwise the range is 0 - 30.
Frequency Type frequency_type
Displayed in the CELL Detailed View, General section, General grouping. Specifies the single frequency band capability of the cell. When the cell is a dual band cells (that is, inner_zone_alg is set to 3), and secondary_freq_type is EGSM or PGSM, frequency_type can only be set to DCS1800. When the cell is a dual band cells (that is, inner_zone_alg is set to 3), and secondary_freq_type is DCS1800, frequency_type can only be set to PGSM or EGSM. Continued
2-32
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-5
Dual band cells option parameters
Single BCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Inner Zone DL Receive Level Threshold rxlev_dl_zone
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. The downlink receive threshold that must be crossed for a handover to take place from the outer zone to the inner zone in a concentric cell or dual band cell. Only used if the CELL inner_zone_alg type is set to the Power Based or the Dual Band Cell Use Algorithms. Valid values are 0 - 63, where: 0 = -110 dBm. 1 = -109 dBm. 2 = 108 dBm. .. 63 = -47 dBm.
Inner Zone DL Receive Level Threshold rxlev_ul_zone
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. The uplink receive threshold that must be crossed for a handover to take place from the outer zone to the inner zone in a Concentric cell or Dual Band cell. Only used if the Cell inner_zone_alg type is set to the Power Based or the Dual Band Cell Use Algorithms. Valid values are 0 - 63, where: 0 = -110 dBm. 1 = -109 dBm. 63 = -47 dBm.
Concentric Cell Zone cell_zone
Displayed in the RTF Detailed View, Concentric cells Grouping. Determines in which zone the RTF is located. Only used for non-BCCH carriers. Valid values are: Outer zone (0), Inner zone (1). Default is Outer zone (0).
Outer Zone Usage Level outer_zone_usage_ level
Displayed in the CELL Detailed View, General section, Concentric, and Dual-Band Cells grouping. Defines the usage level required before inner zone resources are allocated for traffic and phone calls are handed into the inner zone. Valid values are: 0 - 100 (percentage).
Band Preference band_preference
Displayed in the CELL Detailed View, General section, Multiband Handover grouping. Determines the destination frequency band preferred for an Inter-Cell handover. The value of this element indicates to which band this cell prefers to assign or hand over. Valid values are: 1 = PGSM, 2 = EGSM, 4 = DCS1800, 8 = PCS1900. 16 = DYNAMIC. Cannot be modified unless the MultiBand Inter-Cell Handover feature is enabled (unrestricted). Not used if Cell band_pref_mode has a value of 0. Default value is the frequency_type of the Cell. A value of 16 (Dynamic) indicates that the Intelligent Multilayer (IMRM) feature is enabled (unrestricted) for the cell. Can only be set to 16 (Dynamic) if the Intelligent Multilayer Resource Management feature (imrmOpt) is enabled (unrestricted) for the BSS (See Intelligent Multilayer Resource Management (IMRM) on page 2-148 for details). If set to 16 (Dynamic) and all weightings are set to 0, the following message is displayed: “WARNING: IMRM weights set to unsupported. The BSS applies internal defaults.” Continued
68P02901W17-S
2-33 Dec 2009
Overview of configuring single BCCH for dual band cells feature
Table 2-5
Chapter 2: Configuring BSS Features
Single BCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name Band Preference Mode band_preference_ mode
Description Displayed in the CELL Detailed View, General section, Multiband Handover grouping. Determines the method that is used to have a MultiBand MS use the band of preference for a given cell in the BSS. Can only be modified if the MultiBand Inter-Cell Handover feature is unrestricted (enabled). (See Intelligent Multilayer Resource Management (IMRM) on page 2-148 for details)
Mobile Station HO Displayed in the CELL Detailed View, Handover section, General Power Level grouping. Indicates the maximum Dedicated Control Channel (CCH) handover_power_level power level allowed for a Mobile Station (MS) after a handover to this cell. Valid range depends on the setting of Cell frequency_type. Maximum Transmit Power for BTS max_tx_bts
Displayed in the CELL Detailed View, Power Control section, Downlink Power Control grouping. Indicates the maximum output power for the base station transmitter. Can be used to establish a cell boundary. Valid range depends on the setting of Cell frequency_type. For example, for PGSM, EGSM and DCS1800 cells, and M-Cell6, Horizonmacro or Horizon II macro controlling BTS cabinets, the range is -1 to 21.
Maximum Mobile Station Transmit Power max_tx_ms
Displayed in the CELL Detailed View, Power Control section, Uplink Power Control grouping. Indicates the maximum MS output power which can be used in this cell. Regardless of the power class of the mobile, the mobile is not told to use a higher output power. The values should be chosen to balance the up and down links in a cell. Valid range depends on the setting of Cell frequency_type.
Maximum Control Channel Transmit Power ms_txpwr_max_cch
Displayed in the CELL Detailed View, General section, System Access grouping. Defines maximum random access power available for a mobile station, on a control channel (CCCH) in a cell. Valid range depends on the setting of Cell frequency_type.
Maximum Default Transmit Power ms_txpwr_max_def
Displayed in the CELL Detailed View, Power Control section, General grouping. Contains the default value to be used for a neighbor cell when the Neighbor ms_txpwr_max_cell is not defined in an underlying Neighbor instance. Valid range depends on the setting of Cell frequency_type.
Displayed in the CELL Detailed View, Handover section, Handover Types Allowed grouping. Disables or enables intra-cell handovers. Valid values are 0 - 2. Default is BSC Controlled Handover (1).
Overview of configuring single BCCH for dual band cells feature A network operator with an existing single band network and the necessary restricted features enabled, can change cells from a single band configuration to a dual band configuration without interruption of service on the primary band. The procedure is:
2-34
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Procedure 2-1
Methods of configuring the dual band cells option
Change cells from single band to dual band configuration
1
Modify the inner_zone_alg parameter for the cell to Dual Band Cell (3).
2
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.
3
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.
4
Define the percentage in the Outer Zone Usage Level field (outer_zone_usage_level) (that is, outer zone TCHs) that need to be in use before the assignment of secondary band channels.
The dual band cell is fully operational when the secondary band DRIs are brought in to service.
Methods of configuring the dual band cells option The Dual Band Cells Option can be configured using either of the following methods: •
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-S
2-35 Dec 2009
Configuring the dual band cells option using the TTY interface
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-36
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring the dual band cells option using the TTY interface
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-S
2-37 Dec 2009
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 8–PSK. For further information of EGPRS Coding Schemes 1 to 9, see Technical Description: BSS Implementation (68P02901W36).
2-38
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
GPRS and EGPRS coding scheme parameters
GPRS and EGPRS coding scheme parameters Table 2-6 details the parameters associated with configuring GPRS and EGPRS coding schemes.
Displayed in the Optional Features grouping in the BSS Detailed View form. Displays whether the GPRS Coding Schemes 3 and 4 (CS3/CS4) feature is unrestricted (Enabled) or restricted (disabled) for the BSS. Valid values: Disabled (0) or Enabled (1). Default is 0. Cannot be modified by a user. Grayed-out if the GPRS feature (gprsOpt) is restricted at the BSS.
EGPRS Feature egprsOpt
Displayed in the Optional Features grouping in the BSS Detailed View form. Displays whether the EGPRS feature is unrestricted (enabled) or restricted (disabled) for the BSS. Valid values: Disabled (0) or Enabled (1). Cannot be modified by a user.
Displayed in the GPRS grouping in the CELL Detailed View. {27703A} The init_dl_cs parameter is used to specify the initial downlink Coding Scheme (CS) configuration information for a cell. This parameter is also used for QoS capacity determination. The value of this parameter cannot be changed when gprs_enabled equals 1. Valid values: 0 - 3, where: 0 - CS-1 1 - CS-2 2 - CS-3 3 - CS-4 The OMC-R disregards any RTF parameters when determining valid values for init_dl_cs. (pkt_radio_type will not be prompted during the equipage of an RTF and the option to select CS-3 or CS-4 is disabled). Grayed-out if the GPRS feature (gprsOpt) is restricted at the BSS. Continued
68P02901W17-S
2-39 Dec 2009
GPRS and EGPRS coding scheme parameters
Table 2-6
Chapter 2: Configuring BSS Features
GPRS and EGPRS coding schemes parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Initial Uplink Coding Scheme init_ul_cs
Displayed in the GPRS grouping in the CELL Detailed View. {27703A} The init_ul_cs attribute is used to specify the initial uplink Coding Scheme (CS) configuration information for a cell. This parameter is also used for QoS capacity determination. The value of this parameter cannot be changed when gprs_enabled equals 1. Valid values: 0 - 3, where: 0 - CS-1 1 - CS-2 2 - CS-3 3 - CS-4 The OMC-R disregards any RTF attributes when determining legal values for init_ul_cs CELL DV attribute. (pkt_radio_type will not be prompted during the equipage of an RTF and the option to select CS-3 or CS-4 is disabled). Grayed-out if the GPRS feature (gprsOpt) is restricted at the BSS.
Displayed in the GPRS grouping in the CELL Detailed View. {27703A} The egprs_init_dl_cs attribute specifies the initial downlink coding scheme to be used for an EGPRS TBF in a cell. This parameter is also used for QoS capacity determination. The EGPRS feature must be unrestricted. The value of this parameter cannot be changed when gprs_enabled equals 1. Grayed-out if the EGPRS feature (egprsOpt) is restricted at the BSS.
Displayed in the GPRS grouping in the CELL Detailed View. {27703A} The egprs_init_ul_cs attribute specifies the initial uplink coding scheme to be used for an EGPRS TBF in the cell. This parameter is also used for QoS capacity determination. The EGPRS feature must be unrestricted. The value of this parameter cannot be changed when gprs_enabled equals 1. Grayed-out if the EGPRS feature (egprsOpt) is restricted at the BSS.
RTF Parameter: Packet Radio Type pkt_radio_type
Displayed in the RTF Detailed View in the GPRS group. This parameter replaces allow_32k_trau, and indicates whether the RTF can carry GPRS or EGPRS data. SDCCH allocation favors carriers with low values. Valid values are: 0 - 3, where: 0 - None 1 - 16 k 2 - 32 k 3 - 64 k
Continued
2-40
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-6
GPRS and EGPRS coding scheme parameters
GPRS and EGPRS coding schemes parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description Dependency on other parameters: Grayed out if the parent BSS has the GPRS feature (gprsOpt) restricted. The 32 k option is not displayed if the Coding Schemes 3 and 4 feature (cs34Opt) is restricted (Disabled) in the associated BSS. The 64 k option is not displayed if the EGPRS feature (egprsOpt) is restricted (Disabled) for the associated BSS. The 32 k and 64 k options are not displayed if the RTF cell_zone parameter is set to inner zone (1). RTF cell_zone is restricted to outer zone (0) if pkt_radio_type value is 32 k or 64 k. The 32 k and 64 k options are not displayed if the associated SITE ts_sharing value is set to BSC-BTSdynamic allocation supported (1). The 32 k and 64 k options are not displayed if the RTFrtf_capacity value is RTF_SUB (1) (sub-equipped). The RTFrtf_capacity value of RTF_SUB (1) (sub-equipped) is not displayed if the pkt_radio_type value is 32 k or 64 k. The 64 k option is not displayed if the RTF ext_timeslots value is non-zero. RTF ext_timeslots value is restricted to 0 if the RTF pkt_radio_type value is 64 k. The 64 k option is displayed if the associated SITE contains at least one of the following cabinets: Horizon macro, Horizon macro extension , Horizon II macro, Horizon II macro extension, Horizon II mini or Horizon II mini extension. If a user changes pkt_radio_type in edit mode, the OMC-R issues a warning message that the configuration change results in a temporary outage of the RT and requests operator confirmation before proceeding. While creating or modifying an RTF, when the pkt_radio_type is changed to 3 and versatrau is purchased, rtf_ds0_count is set to its default value 3. Also, while modifying an RTF, the status bar displays the following message: Modify the value of rtf_ds0_count attribute. If the user does not change the value, the BSS takes the default value. The OMC sends the rtf_ds0_count to the BSS in this case.
NOTE If DRIM-based carriers are used, and if any of the timeslots are used for GPRS, then all timeslots must have backing for 32 kbit/s TRAU due to the processing limitations within the DRIM hardware.
68P02901W17-S
2-41 Dec 2009
Methods for configuring GPRS and EGPRS coding schemes
Chapter 2: Configuring BSS Features
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 kbit/s TRAU timeslots for RTF 0 1. modify_value 1 pkt_radio_type 2 rtf 0 1
2-42
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Short Message Service - Cell Broadcast
Short Message Service - Cell Broadcast ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of SMS-CB The Short Message Service - Cell Broadcast (SMS-CB) is an optional feature that provides a means of unilaterally transmitting background messages to MSs on a per cell basis, using the Cell Broadcast Channel (CBCH). Each BSC is connected to a single Cell Broadcast Centre (CBC), which is responsible for downloading cell broadcast messages to the BSC together with indications of the repetition rate and the number of broadcasts required per message. The BSC is responsible for transmitting these updates to the BTSs affected, which then ensures that the message is transmitted as requested.
Message details for SMS-CB Message handling The maximum number of concatenated messages (pages) forming one macromessage is 15 for a maximum of 128 cells. The length of this message cannot be more than 2.5 kbytes, otherwise the CBL resets, and an alarm is raised. Each page in a micromessage has the same message identifier, indicating the source of the message, and the same serial number. The maximum storage capacity at the BTS is 650 pages. The BSS divides into segments messages larger than 576 bytes received from the CBC.
Message categories The CBC categorizes messages as: •
High.
•
Normal.
•
Background.
High priority messages are scheduled into Reserved slots allocated by the CBC in the current schedule period. Thereafter, they are treated as normal messages. Background priority messages are accepted from the CBC and scheduled into slots remaining from those occupied by High and Normal priority messages.
68P02901W17-S
2-43 Dec 2009
SMS-CB parameters
Chapter 2: Configuring BSS Features
CBC configurable DRX period A DRX message can be configured, which can be switched on or off by messages from the CBC. The period of the DRX can also be set through the CBC.
Alphabets supported by the SMS Various default alphabets are supported by the Short Message Service feature. The default alphabets enable background messages to be broadcast in the following languages: •
Czech.
•
Danish.
•
Dutch.
•
English.
•
Finnish.
•
French.
•
German.
•
Greek.
•
Hungarian.
•
Italian.
•
Norwegian.
•
Polish.
•
Portuguese.
•
Spanish.
•
Swedish.
•
Turkish.
SMS-CB parameters Table 2-7 details the SMS-CB parameters. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. Refer to: Technical Description: BSS Command Reference (68P02901W23) for full details of the commands and parameters used.
2-44
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-7
SMS-CB parameters
SMS-CB parameters
OMC-R GUI field name/BSS parameter name
Description
Values
CBC to BSC Interface Version cbc_intface_vers
Displayed in the BSS Detailed View SMS Information grouping. Used to select the BSS to CBC interface. Select (on a per BTS site basis) either the existing interface, or the enhanced interface with the new interpretation of the repetition rate and CBCH loading fields. This selects the protocol used across the SMS CB interface. The new maximum broadcast repetition rate is one 8 x 51 multiframe sequence which corresponds to a frequency period of 1.883 seconds. The current interface selected can also be displayed.
Existing (0). Existing with new interpretation of repetition rate (1). The default is Existing (0).
CBC VBIND Counter cbc_vbind_cntr
Displayed in the BSS Detailed View SMS Information grouping. Used to set (on a per BTS site basis) the number of successful Version Binds (VBINDS) that must be sent by the BSS to the CBC before a negotiation takes place within the next VBIND sent. The VBIND includes a version parameter which indicates what version of the specifications is supported by the CBC/BSS sending the VBIND, and the version of the interface the system wants to use on the established SVC. The number of successful VBINDS sent to the CBC before negotiation takes place can also be displayed. This value is the number of successful Version Binds (VBINDS) that must be sent by the BSS to the CBC before a negotiation takes place.
A value in the range 0 - 255. The default is 0.
SMS Fast Select sms_fast_select
Displayed in the BSS Detailed View SMS Information grouping. Indicates what type of X.25 network is being used. Enabled (1) indicates the BSS and CBC attempts to exchange user data in the network connection and network connection release phases of X.25. Disabled (0) means the BSS and CBC will not exchange user data in the network connection and network connection release phases of X.25. If a user changes this field the system displays a message to warn that the CBL will be recycled.
Enabled (1) or Disabled (0).
CBC to CBS Outage Counter cbs_outage_cntr
Displayed in the SITE Detailed View SMS Information grouping. Specifies (on a per BTS site basis) how many broadcast slots the CBS should wait before considering the CBC sourced messages invalid in the case of an outage. This introduces a delay between the outage occurring and the CBS halting transmission of CBC originated messages. The current delay, on a per BTS basis, can also be displayed.
0 - 255.
68P02901W17-S
2-45 Dec 2009
Methods of configuring SMS-CB
Chapter 2: Configuring BSS Features
Methods of configuring SMS-CB The SMS-CB can be configured using the following methods: •
OMC-R GUI, BSS and SITE Detailed Views, and the parameters detailed in Table 2-7.
•
TTY interface, see Configuring SMS-CB using the TTY interface.
An SMS-CB message can be edited and viewed using the OMC-R GUI, see Viewing and editing the SMS-CB message using the OMC-R GUI on page 8-241.
Configuring SMS-CB using the TTY interface For further details of the commands and parameters detailed in the following sections, refer to: Technical Description: BSS Command Reference (68P02901W23).
Determining status of CBCH using the TTY interface To determine the status of the CBCH, use the disp_cbch_state command. For example, the following command displays the status of message number 3 at cell 543 21 61986 3494: disp_cbch_state 3 543 21 61986 3494 The system response depends on the state of the CBCH.
Displaying state of CBCH using the TTY interface To display the state of the CBCH, use the command disp_element and the cbch_enabled parameter. For example: disp_element cbch_enabled 0 cell_number = 5 4 3 2 1 61986 34944 The response is one of the following: cbch_enabled = 0 (CBCH disabled). cbch_enabled = 1 (CBCH enabled).
Displaying counter statistic state using the TTY interface To display the state of the counter statistic, use the command disp_stats. For example: disp_stats sms_no_bcast_msg cell 5 4 3 2 1 62259 784 The response is one of the following:
2-46
•
No stats data available.
•
Valid stats info from specified interval.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring SMS-CB using the TTY interface
Selecting the interface version between the BSS and CBC using the TTY interface To select the interface version between the BSS and CBC, use the chg_element command and the cbc_intface_vers parameter. For example, to select the existing interface with a new interpretation of the repetition rate and CBCH loading fields at BSC, use the following command: chg_element cbc_intface_vers 1 0 The command is rejected in the following instances: •
If a BTS location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element requires a location parameter of 0
•
If a BSC location with a bsc type 0 is entered in the command, the following error message is displayed: COMMAND REJECTED: bsc_type not compatible with specified element
•
If an RXCDR location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element specified not allowed at an RXCDR site.
Setting number of successful VBINDs using the TTY interface To set number of successful VBINDs sent between a BSS and CBC in a BSC site before a negotiate is needed, use the chg_element command and the cbc_vbind_cntr parameter. For example, to set the number of successful VBINDs to 3 before a negotiate becomes necessary, use the following command: chg_element cbc_vbind_cntr 3 bsc The command is rejected in the following instances: •
If a BTS location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element requires a location parameter of 0
•
If a BSC location with a bsc type 0 is entered in the command, the following error message is displayed:COMMAND REJECTED: bsc_type not compatible with specified element
•
If an RXCDR location is entered in the command, the following error message is displayed:COMMAND REJECTED: Element specified not allowed at an RXCDR site.
Setting delay between outage and halting transmission using the TTY interface To set a delay between an outage occurring and the CBS halting transmission of CBC messages, use the chg_element command and the cbs_outage_cntr parameter. For example, to set the delay to 20 for site 1 use the following command: chg_element cbs_outage_cntr 20 1 The command is rejected in the following instances: •
If a stand alone BSC location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element specified not allowed at a stand alone BSC
•
If an RXCDR location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element specified not allowed at an RXCDR site.
68P02901W17-S
2-47 Dec 2009
Configuring SMS-CB using the TTY interface
Chapter 2: Configuring BSS Features
Displaying CBC to BSS interface information using the TTY interface To display the CBC to BSS interface version being used by BSC sites, use the following disp_element command and the cbc_intface_vers parameter. For example: disp_element cbc_intface_vers 0 If the command is accepted, the system responds: cbc_intface_vers = 0 The command is rejected in the following instances: •
If a BTS location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element requires a location parameter of 0
•
If a BSC location with a bsc type 0 is entered in the command, the following error message is displayed: COMMAND REJECTED: bsc_type not compatible with specified element
•
If an RXCDR location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element specified not allowed at an RXCDR site.
Displaying number of successful VBINDs using the TTY interface To display the number of successful VBINDs sent between a BSS and CBC in a BSC site before a negotiation is needed, use the disp_element command and the cbc_vbind_cntr parameter. For example: disp_element cbc_vbind_cntr 0 If the command is accepted, the system responds: cbc_vbind_cntr = 0 The command is rejected in the following instances: •
If a BTS location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element requires a location parameter of 0
•
If a BSC location with a bsc type 0 is entered in the command, the following error message is displayed: COMMAND REJECTED: bsc_type not compatible with specified element
•
If an RXCDR location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element specified not allowed at an RXCDR site.
Displaying delay between an outage and halting transmission using the TTY interface To display the delay between an outage occurring and the CBS halting transmission of CBC messages at a BTS site, use the disp_element command and the cbs_outage_cntr parameter. For example, use the following command to display the value of the cbs_outage_cntr at site 2: disp_element cbs_outage_cntr 2 If the command is accepted, the system responds: cbc_vbind_cntr = 0 The command is rejected in the following instances:
2-48
•
If a standalone BSC location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element specified not allowed at a stand alone BSC
•
If an RXCDR location is entered in the command, the following error message is displayed: COMMAND REJECTED: Element specified not allowed at an RXCDR site.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring SMS-CB using the TTY interface
Enabling and disabling CBCH using the TTY Interface To enable the CBCH use the chg_element command and cbch_enabled parameter. For example: chg_element cbch_enabled 1 0 cell = 5 4 3 2 1 61986 34944 To disable the CBCH use the chg_element command and cbch_enabled parameter. For example: chg_element cbch_enabled 0 0 cell = 5 4 3 2 1 61986 34944
Enabling and disabling counter statistic using the TTY interface To enable the counter statistic use the stat_mode command and sms_no_bcast_msg parameter. For example: stat_mode sms_no_bcast_msg ON cell = 5 4 3 2 1 61986 34944
Disabling counter statistic To disable the counter statistic use the stat_mode command and sms_no_bcast_msg parameter. For example: stat_mode sms_no_bcast_msg OFF cell = 5 4 3 2 1 61 986 34944
Creating and transmitting background messages using the TTY interface To create and transmit background messages, use the chg_smscb_msg command. For example, to send a background message to cell number = 5 4 3 2 1 61986 34944 with a message number of 0, a message id of 1234, scope of immediate, cell wide, a code of 0, the language set to English and an update number of 0, follow these steps:
Procedure 2-2
Create and transmit background messages at the TTY interface
1
Enter the following command: chg_smscb_msg 0 1234 0 0 0 1 5 4 3 2 1 61986 34944 The following is displayed: Enter the Message:
2
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.
68P02901W17-S
2-49 Dec 2009
Configuring SMS-CB using the TTY interface
Chapter 2: Configuring BSS Features
Deleting background messages using the TTY interface One or more background messages may be deleted using the del_smscb_msg command. The following can be deleted: •
A single message at a single cell.
•
A single message at all cells in the BSC.
•
All messages at a single cell.
•
All messages at all cells in the BSC.
For example, to delete a single message at a single cell (message number 0 at cell number 5 4 3 2 1 61986 34944) use the following command: del_smscb_msg 0 5 4 3 2 1 61986 34944
Technical Description: BSS Command Reference (68P02901W23) contains further examples of this command.
2-50
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Short Message Service - Point-To-Point
Short Message Service - Point-To-Point ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to setting up SMS-PTP The Short Message Service - Point-to-Point (SMS-PTP) is an option that provides a means of two-way transmission between the network and the MS. The parameters associated with this feature permit selective MS originated or MS terminated Point-to-Point SMS. The downlink logical channel may also be specified for MS terminated point-to-point sms. The timing constraints on the SACCH allow a block to be transferred every 104 frames, while the FACCH allows a block to be delivered every 8 frames. The disadvantage of the FACCH is that frames are stolen, with adverse effects on the audio quality or data transmission. Stealing frames on the FACCH would be more noticeable as the size of the short message increases, but using the SACCH for larger messages means longer delivery times. If the logical channel is selected by the BSS, the selection depends on the status of the MS. If.....
Then.....
the MS is idle
SDCCH is used.
the MS is on SDCCH
SDCCH is used.
the MS is busy
SACCH or FACCH is used.
Refer to: Technical Description: BSS Command Reference (68P02901W23) for full details of the commands used.
SMS-PTP procedures The following SMS-PTP procedures are described in the following sections: •
Enabling the MS originated point-to-point SMS.
•
Displaying the MS originated point-to-point SMS.
•
Enabling the MS terminated point-to-point SMS.
•
Displaying the MS terminated point-to-point SMS.
•
Specifying the downlink logical channel.
SMS-PTP prerequisites This feature is automatically enabled when the system is purchased. It is disabled when either the MS originated SMS-PTP feature or the MS terminated SMS-PTP feature are themselves disabled. It requires a Service Centre which stores and forwards the messages. The transfer of short messages between the Service Centre and the MS needs the support of the GSM PLMN.
68P02901W17-S
2-51 Dec 2009
Enabling and disabling MS originated Point to Point SMS at a site
Chapter 2: Configuring BSS Features
Enabling and disabling MS originated Point to Point SMS at a site For further details of the commands and parameters detailed in the following sections, refer to Technical Description: BSS Command Reference (68P02901W23).
Enabling MS originated SMS-PTP To enable MS originated SMS-PTP on an individual site basis, use the following command: chg_element sms_ul_allowed 1 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 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 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 For example to enable MS terminated SMS-PTP at site 0, use: chg_element sms_dl_allowed 1 0
2-52
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displaying the state of MS terminated SMS-PTP at a site
Disabling MS terminated SMS-PTP The MS terminated SMS-PTP may be disabled on an individual site basis by using the following command: chg_element sms_dl_allowed 0 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 For example, to display the status of MS terminated SMS-PTP at site 1, use: disp_element sms_dl_allowed 1 The system responds, for example: sms_dl_allowed = 1
Specifying the downlink logical channel The downlink logical channel may be specified on an individual site basis by using the following command: chg_element sms_tch_chan 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 For example to display the downlink logical channel at site 1, use: disp_element sms_tch_chan 1 The system responds, for example: sms_tch_chan = 1
68P02901W17-S
2-53 Dec 2009
Preventive Cyclic Retransmission (PCR)
Chapter 2: Configuring BSS Features
Preventive Cyclic Retransmission (PCR) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to PCR The Preventive Cyclic Retransmission (PCR) method of error correction is supported by the Multiple Serial Interface, and is advantageous where large transmission delays are experienced, as in satellite links. At initialization, the database is checked by the Layer 2 code to ensure that PCR error correction has been enabled for use. If PCR error correction is not enabled for use, the default is Basic error correction. When using PCR, a Message Signaling Unit (MSU) which has been transmitted is retained at the transmitting signaling link terminal until a positive acknowledgment for that MSU has been received. During a period when there are no new MSUs to be transmitted, or when the maximum number of unacknowledged messages has been reached, all of the MSUs which have not been positively acknowledged are transmitted cyclically. PCR is clearly defined in CCITT Q.703 section 6 (reference #2).
Range and default values for Timers The range and default values of the 7 MTP level 2 timer parameters are listed in Table 2-8.
Table 2-8
7 MTP level 2 timer parameters
Timer
Range (ms)
Default
Index Value
T1 (alignment ready)
40000 - 50000
50000
0
T2 (not aligned)
5000 - 150000
25000
1
1000 - 1500
1400
2
T4 (emergency)
400 - 600
600
3
T5 (sending SIB)
80 - 120
100
4
3000 - 6000
5000
5
800 - 2000
1000
6
T3 (aligned)
T6 (remote congestion) T7 (excessive delay of acknowledgment)
These timers are displayed and can be configured in the BSS Detailed View MTP Timers parameter grouping or using the TTY interface.
2-54
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Range and default values for N-value parameters
Range and default values for N-value parameters The default values of the two N-value parameters are listed in Table 2-9.
Table 2-9
3 N-value parameters
N-value
Parameter
Range
Default
N1 (threshold)
pcr_n1
32-127 MSUs
127 MSUs.
N2 (threshold)
pcr_n2
950-3750 (octets)
3750 octets.
The third N-value parameter, pcr_enable, is the flag required to change the error correction from basic error mode to PCR error correction mode. When this element is set to 1, PCR error correction is in the enabled state, and when it is set to 0, the PCR error correction is disabled, and the basic error correction mode is enabled.
Methods of configuring PCR PCR can be configured using the following methods: •
OMC-R GUI, BSS Detailed View, and the parameters detailed in the Signaling Information grouping (see Table 4-5).
•
TTY interface, see Configuring PCR using the TTY interface below.
Configuring PCR using the TTY interface The following PCR TTY interface procedures are described in this section: •
Enabling and disabling PCR.
•
Displaying the status of PCR.
•
Setting up message signaling units.
•
Setting up message unit octets.
•
Displaying the current value of a PCR parameter.
•
Setting up timer values.
Refer to Technical Description: BSS Command Reference (68P02901W23) for full details of the commands used in the subsequent sections.
68P02901W17-S
2-55 Dec 2009
Configuring PCR using the TTY interface
Chapter 2: Configuring BSS Features
Enabling and disabling PCR using the TTY interface To display the status of the PCR error correction feature at the BSC, use the following command: disp_element pcr_enable 0 The system responds with a message stating whether PCR error correction is Enabled or Disabled. To enable the PCR error correction mode at the BSC, use the following command: chg_element pcr_enable 1 0 To disable the PCR error correction mode at the BSC, use the following command: chg_element pcr_enable 0 0 To set up the number of Message Signaling Units use the following command: chg_element pcr_n1 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 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*
2-56
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Where:
Configuring PCR using the TTY interface
is: t*
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.
Refer to Table 2-8 for the range and default values of the MTP level 2 timers.
68P02901W17-S
2-57 Dec 2009
MSC initiated IMSI and IMEI call trace
Chapter 2: Configuring BSS Features
MSC initiated IMSI and IMEI call trace ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to MSC initiated call trace The MSC initiated IMSI and IMEI call trace allows an MS to be tracked as it moves across the network. The MSC invokes call tracing at the BSS, which collects call trace data for either the International Mobile Subscriber Identity (IMSI) or the International Mobile Equipment Identity (IMEI), based upon the invoking message. This call trace data is then forwarded to the OMC-R. A call trace started by an MSC request, has the call trace data sent to the OMC-R for storage in a call trace logfile. This call trace data can also be forwarded to the Network Management Centre (NMC) if necessary. The percentage of BSS resources to be reserved for MSC initiated traces can be specified through the call_trace_options parameter. The maximum number of call traces allowed at any one time is 16 for each BSS. The maximum number of traces the OMC-R can support is 40,000.
OMC-R Online Help, Network Operations describes how to initiate and manage a standard call trace using the OMC-R GUI and TTY interface.
Controlling an MSC initiated call trace The call_trace_options parameter enables or disables MSC initiated call traces for the entire BSS. The value of the call_trace_options parameter indicates the percentage of traces to be reserved exclusively for use by MSC initiated traces on a per-LCF basis. Entering a value between 0 and 100 indicates the percentage of traces reserved for MSC initiated traces on a per LCF basis. Entering a value of 255 indicates that MSC traces are blocked (barred). The default value is 0.
Example 1 To enable the MSC call trace feature and set the percentage of traces reserved for MSC initiated traces to 1 percent, enter the command: chg_element call_trace_options 1 0 If the command is executed successfully, the following is displayed: COMMAND ACCEPTED
Example 2 To bar the MSC call trace feature, enter the command: chg_element call_trace_options 255 0 If the command is executed successfully, the following is displayed: COMMAND ACCEPTED
2-58
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Naming of call trace log files
Example 3 To display the current setting of the call_trace_options parameter, enter the command: disp_element call_trace_options 0 If the command is executed successfully, the following is displayed: call_trace_options = 1
Naming of call trace log files Each logfile name includes a timestamp consisting of the day of the month, the hour, the minute and the second at which the logfile was created. This is to cater to situations where a call which is being traced goes outside the scope of that trace (moves from one cell to another) and re-enters the original scope.
GSM Trace Log file {27703A} The naming convention for the GSM Call Trace Log file is modified. The file name is in the following format: ct_____. A few examples of file naming conventions are as follows: ct_MSC_0000000023_1900_00257_0933472.28175502 ct_MMI_0000000005_1800_00508_1132800.23181320 ct_OMC_0000000222_1760_00009_0531712.14155138
NOTE
68P02901W17-S
•
A timestamp consists of the following fields: , where each field consists of 2 digits. The field indicates a number between 1 and 31.
•
If the OMC-R fails to get the version of a BSS, it inserts 0000 in place of the BSSVersion.
2-59 Dec 2009
Naming of call trace log files
Chapter 2: Configuring BSS Features
GPRS Trace Log file {27703A} The naming convention for the GPRS Trace Log file is modified. The file name is in the following format: gt______. A few examples of file naming conventions are as follows: gt_MMI_0000000003_1900_00004_0_e8003d7d.16165815 gt_OMC_0000000002_1800_00010_0_c0f0a94d.17114120
NOTE
2-60
•
A timestamp consists of the following fields: , where each field consists of 2 digits. The field indicates a number between 1 and 31.
•
If the OMC-R fails to get the version of a BSS, it inserts 0000 in place of the BSSVersion.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Call trace flow control
Call trace flow control ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of call trace flow control Call traces can generate large and excessive amounts of trace data, which can load other parts of the system. OMC-R Online Help, Network Operations describes how to initiate and manage a standard call trace using the OMC-R GUI and TTY interface. Call trace flow control is a mechanism that reduces the number of call traces that can be initiated. The BSS enables or disables call trace flow control by monitoring the OML buffer availability. When the Operations and Maintenance Link (OML) buffer reaches a predefined user level, the BSS enables or disables call trace flow control. When enabled the BSS temporarily suspends the triggering and the dynamic adjustment of the call trace criteria by the BSS. The BSS displays the current call trace flow control setting in the BSS Detailed View window. When call trace flow control is disabled (default), a user can initiate call traces from a BSS, SITE, CELL, or RTF. When call trace flow control is enabled, a user cannot initiate a call trace from a BSS, SITE, CELL, or RTF. If a user attempts this procedure, the OMC-R displays an error message in the status bar.
NOTE When a BSS is reset, call trace flow control is set to Disabled (0). MSC traces are generally considered to be of greater importance than other types of traces, and are less likely to collect excessive trace data than, for example, nth call traces. MSC traces only exist for the life of the call upon which they were invoked. For this reason, call traces initiated from an MSC can be enabled or disabled, when the call trace flow control is enabled.
Call trace flow control parameters Table 2-10 shows the parameters associated with Call Trace Flow Control. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
68P02901W17-S
2-61 Dec 2009
Call trace flow control parameters
Table 2-10
Chapter 2: Configuring BSS Features
Call trace flow control parameters
OMC-R GUI field name/BSS parameter name
Description
Valid Input
Flow Control by BSS ct_flow_control_bss_ enabled (OMC-R parameter name: ct_fc_bss_enabled)
Displayed in the GSM/GPRS Trace Information grouping of the BSS Detailed View. Automatically set by the BSS when the ct_fc_hi_level or ct_fc_lo_level is reached (see below). Displays whether a user can initiate a call trace from a BSS, SITE, CELL or RTF. This parameter is set to 0 (zero) when the BSS is reset. This field cannot be modified by a user.
0 to 2. Disabled (0): meaning a user can initiate a call trace from a BSS, site, cell or RTF. Enabled (1): meaning a user cannot initiate a call trace from a BSS, site, cell or RTF. Halted (2). Default is Disabled (0).
Flow Control High Threshold ct_flow_control_hi_level (OMC-R parameter name: ct_fc_hi_level)
Displayed in the GSM/GPRS Trace Information grouping of the BSS Detailed View. Specifies the percentage of the call trace OML buffer space that has to be used before flow control is automatically enabled. When this limit is reached, ct_fc_bss_enabled is automatically set to Enabled (1). This parameter must be greater than or equal to ct_fc_lo_level plus 20. Setting this parameter to 100% effectively disables call trace flow control.
20 to 100. Default is 60%.
Flow Control Low Threshold ct_flow_control_lo_level (OMC-R parameter name: ct_fc_lo_level)
Displayed in the GSM/GPRS grouping of the BSS Detailed View. Specifies the percentage of the call trace OML buffer space that has to be used before flow control is automatically disabled. When this limit is reached, ct_fc_bss_enabled is automatically set to Disabled (0). This parameter must be less than or equal to ct_fc_hi_level minus 20. For example, if ct_fc_hi_level is set to 75% and ct_fc_lo_level is set to 25%, call trace flow control is automatically enabled when the OML buffer capacity reaches 75%, and call trace flow control is automatically disabled when the OML buffer capacity reaches 25%.
0 to 80. Default is 20%.
Continued
2-62
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-10
Methods of configuring call trace flow control
Call trace flow control parameters (Continued)
OMC-R GUI field name/BSS parameter name Apply Flow Control to MSC Trace ct_flow_control_msc_ enabled (OMC-R parameter name: ct_fc_msc_trace)
Description Displayed in the GSM/GPRS Trace Information grouping of the BSS Detailed View. Enables or disables the initiation of call traces from an MSC, when call trace flow control is enabled. For example, when BSS, SITE, CELL, and RTF call traces are prevented using ct_fc_bss_enabled = 1, MSC initiated call traces can be initiated when ct_fc_msc_trace is set to Disabled (0). This parameter can only operate when call trace flow control is enabled, that is, ct_fc_bss_enabled is set to 1, and MSC traces have not been barred using the call_trace_options parameter.
Valid Input Disabled (0): meaning that MSC traces are allowed while flow control is enabled. Enabled (1): meaning that MSC traces are not allowed while flow control is enabled. Default is Disabled (0).
Methods of configuring call trace flow control Call trace flow control can be configured using either of the following methods: •
OMC-R GUI BSS Detailed View and the fields detailed in Table 2-10.
•
TTY interface, see Configuring Call Trace Flow Control using the TTY interface.
Configuring call trace flow control using the TTY interface Configuring call trace flow control using chg_element To configure the call trace flow control, use the chg_element command and the appropriate call trace flow control parameter as shown in Table 2-10. See Technical Description: BSS Command Reference (68P02901W23) for further details of BSS commands and parameters.
Setting the high level of the OML buffer To set the level of the OML buffer at which the BSS enables call trace flow control, use the chg_element command and the ct_fc_hi_level parameter. For example, the following command sets the OML at 85%: chg_element ct_fc_hi_level 85
68P02901W17-S
2-63 Dec 2009
Configuring call trace flow control using the TTY interface
Chapter 2: Configuring BSS Features
Setting the low level of the OML buffer To set the level of the OML buffer at which the BSS disables call trace flow control, use the chg_element command and the ct_fc_lo_level parameter. For example, the following command sets the OML at 60%: chg_element ct_fc_lo_level 60
Disabling MSC call trace flow control To allow call traces to be initiated from an MSC only, when call trace flow control is enabled, use the chg_element command and the ct_fc_msc_trace parameter. For example, to enable MSC call traces, disable MSC Call Trace Flow Control using in the following command: chg_element ct_fc_msc_trace 0
Enabling MSC call trace flow control To prevent call traces being initiated at an MSC, when call trace flow control is enabled, use the chg_element command and the ct_fc_msc_trace parameter. For example, to prevent MSC call traces, enable MSC call trace flow control use the following command: chg_element ct_fc_msc_trace 1
Displaying call trace flow control using the TTY interface To display the call trace flow control settings, use the disp_element command and the appropriate call trace flow control parameter as shown in Table 2-10. To display the level of the OML buffer at which the BSS enables call trace flow control, for example, enter the following command: disp_element ct_fc_hi_level The system responds: ct_flow_control_hi_level = 85% To display the level of the OML buffer at which the BSS disables call trace flow control, use the following command: disp_element ct_fc_ho_level The system responds, for example: ct_flow_control_hi_level = 60% To display whether MSC call trace flow control is enabled, use the following command: disp_element ct_fc_msc_trace The system responds, for example: ct_flow_control_msc_trace = 0
2-64
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring call trace flow control using the TTY interface
Displaying whether call trace flow control is enabled, disabled, or halted To display whether call trace flow control is enabled or disabled, use the following command: disp_element ct_fc_bss_enabled The system responds, for example: ct_flow_control_bss_enabled = 0
68P02901W17-S
2-65 Dec 2009
GPRS Trace
Chapter 2: Configuring BSS Features
GPRS Trace ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Feature Description The GPRS Trace feature is an extension of the existing GSM Call Trace implementation. The GPRS Trace feature enables users to trace information on GPRS MSs. It provides similar functionality to GSM Call Trace. GPRS Trace differs from GSM Call Trace in the following respects: •
GPRS signaling is more frequent due to the bursty packet nature of GPRS data transfers.
•
GPRS MSs may leave a cell without informing the BSS. Therefore, the “continue beyond scope” option is not applicable in GPRS Trace. However, for ease of implementation, a “continue beyond scope” value is always included in the trace Create action. This value is ignored by the BSS, if the trace type is GPRS.
•
For GPRS Trace, the lifetime of an invoked trace corresponds to the lifetime of a GPRS MS meeting the GPRS Trace criteria within a PCU. A number of GPRS data transfers may occur within this period. Due to cell reselection, a GPRS MS may leave the scope of the criteria and/or the PCU without prior warning. When the PCU detects that a GPRS MS has left, the invoked trace ends. Since cell reselection can take up to 15 seconds, the PCU waits 15 seconds for the MS to reappear before ending the invoked trace. This differs from GSM Call Trace, where the lifetime of an invoked trace and corresponding log file corresponds to a single call.
•
GPRS Trace is created and managed from the OMC and BSS MMI only.
NOTE Unlike GSM Call Trace, creation of GPRS Trace criteria is not supported from the MSC. GPRS Trace Records are forwarded to the NMC. The GPRS trace create criteria includes:
2-66
•
Trace scope – options for GPRS Trace: BSS, site, Cell, RTF (as for GSM).
•
Trace selector – options for GPRS Trace: IMSI (International Mobile Subscriber Identity).
•
TLLI (Temporary Logical Link Identity), Nth GPRS MS.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
•
Feature Description
GPRS Trace Record type: Basic or Radio. If Radio is selected, the user may select some or all of the following: LLC (Logical Link Control) information. BSSGP (BSS GPRS protocol) messages.
•
RLC/MAC (Radio link control / Medium Access Control) messages. GPRS Power Control and Coding Scheme, including UL/DL measurement data. Packet Measurement Reports. Every RLC/MAC PDAK.
•
Trace start/stop times.
•
Total number of GPRS MSs to be traced.
NOTE This information is counted per-PRP. The trace criteria are complete at the BSS, when the total number of MSs have been traced for at least one PRP. The overall number of MSs traced during this period may exceed the total number setting. This behavior is like the counting of total number of calls at the LCF level for Call Trace.
•
Measurement interval: This value applies for Packet Measurement Reports and UL/DL Measurement data.
•
Maximum number of simultaneous MSs to be traced (applicable only if Trace selector is set to Nth GPRS MS).
NOTE This information is counted per-PRP. Therefore, the number of simultaneous calls at any specific time may exceed the maximum number setting. The user may request a combined trace of both GSM and GPRS information in the specific case of an IMSI trace selector. In this case, the BSS forwards trace records relating to both GSM calls and GPRS data transfers for that IMSI. GSM and GPRS trace information is written to separate log files.
68P02901W17-S
2-67 Dec 2009
Enhanced Circuit Error Rate Monitor (ECERM)
Chapter 2: Configuring BSS Features
Enhanced Circuit Error Rate Monitor (ECERM) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of ECERM Enhanced Circuit Error Rate Monitor (ECERM) monitors the continuity of circuits. A circuit is a path along which the connection is made from the entry point in the BSS to the exit point in the BSS. Enhanced Circuit Error Rate Monitor (ECERM) is an enhancement to the existing Circuit Error Rate Monitor feature (see OMC-R Online Help, Network Operations for details). ECERM increases the number of monitor points along the circuit path to narrow down the identification of potentially faulty devices. ECERM does not confirm that a device is faulty; the user must determine this. The circuit path points monitored by CERM are: •
CIC (Circuit Identity Code) - a timeslot on the link between the RXCDR or BSC and the MSC.
•
RCI (Radio Channel Identifier) - the radio hardware.
In addition to these points, ECERM also monitors the following new points: •
ACI (Ater Channel Identifier) - the timeslot group on the link between the RXCDR and the BSC.
•
PIC (Path Identity Code) - the timeslot in the link between the BSC and the BTS.
•
GCI (GPRS Circuit Identifier) - a timeslot on the link between the BSC and the PCU.
These points are monitored on a per-timeslot basis. For a full description of ECERM, see Technical Description: BSS Implementation (68P02901W36). For details of the alarms generated by CERM and the ECERM feature, see Maintenance Information: Alarm Handling at the OMC-R (68P02901W26).
Prerequisites to configuring ECERM Before configuring ECERM, ensure that the following features have been enabled: •
ECERM (ecermOpt parameter).
•
GPRS (gprsOpt parameter).
Table 2-11 indicates which ECERM parameters require these parameters to be enabled. For example, existing CERM parameters cannot be restricted.
2-68
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Determining whether ECERM has been enabled
Determining whether ECERM has been enabled ECERM is an optional feature, which must be enabled before it can be used.
Using the OMC-R GUI To check if ECERM has been enabled using the OMC-R GUI, display the setting of the Enhanced CERM Feature field in the Optional Features grouping in the BSS Detailed View. The values for ecermOpt are: •
Disabled (0).
•
Enabled (1).
The default is Disabled (0).
Using the TTY interface To check if ECERM has been enabled using the TTY interface, enter the following command: disp_options all If the ECERM optional feature has been enabled, and is therefore unrestricted, the system displays the following in the unrestricted list: <43> Enhanced Circuit Error Rate Monitor
ECERM parameters Table 2-11 details the ECERM parameters. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
Displayed in the Optional Features grouping in the BSS Detailed View. Indicates whether the ECERM feature is enabled. Valid values are 0 or 1, where: •
0 - Disabled.
•
1 - Enabled. Continued
68P02901W17-S
2-69 Dec 2009
ECERM parameters
Chapter 2: Configuring BSS Features
Table 2-11
ECERM parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
CIC Error Gen Threshold cic_error_gen_thresh
Displayed in the Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the CIC error count threshold at the BSC. Once this threshold is reached, further CIC errors do not increase the CIC error count. When this threshold is reached or exceeded a CIC alarm is generated. Valid range: 2 - 255. Default value: 6. If a user changes the threshold value, an alarm is not immediately generated. The new threshold only takes effect when the CIC error count changes. This parameter must be two greater than cic_error_clr_thresh.
CIC Error Clear Threshold cic_error_clr_thresh
Displayed in the Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the CIC error count clearing threshold at the BSC. When the error count reaches or falls below this threshold the alarm clears. Valid range: 0 - 253. Default value: 0. Must be two less than cic_error_gen_thresh.
CIC Error Increment cic_error_inc
Displayed in the Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the CIC error increment value. The system updates the CIC error count by this value whenever an error is detected. Valid range: 0 (Disabled) - 255. Default value: 1. If a user sets the value to 0, an error message is displayed indicating that no more CIC alarms will be generated.
ACI Error Gen Threshold aci_error_gen_ thresh (OMC-R parameter name: aciErrGenThresh).
Displayed in the Enhanced Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the ACI error count threshold at the BSC. Once this threshold is reached, further ACI errors do not increase the ACI error count. When this threshold is reached or exceeded, an ACI alarm is generated. Valid values: 2 - 255. Default value: 6. If a user changes the threshold value, an alarm is not immediately generated. The new threshold only takes effect when the ACI error count changes. Grayed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. Continued
2-70
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displayed in the Enhanced Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the value which the error count must be equal to or less than for an ACI alarm to be cleared. Valid values: 0 - 253. Default value: 0. If a user changes the threshold value, an alarm is not immediately cleared. The new threshold only takes effect when the ACI error count changes. Grayed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC.
Displayed in the Enhanced Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the ACI error increment value. The system updates the ACI error count by this value whenever an error is detected. Valid range: 0 (Disabled) - 255. Default value: 1. If a user sets the value to 0, an error message is displayed indicating that no more ACI alarms will be generated. Set to 0, if the ECERM feature is disabled. Grayed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC.
GCI Error Gen Threshold gci_error_gen_thresh (OMC-R parameter name: gciErrGenThresh)
Displayed in the Enhanced Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the GCI error count threshold at the BSC. Once this threshold is reached, further GCI errors do not increase the GCI error count. When this threshold is reached or exceeded a GCI alarm is generated. Valid values: 2 - 255. Default value: 6. If a user changes the threshold value, an alarm is not immediately generated. The new threshold only takes effect when the GCI error count changes. Grayed-out if the GPRS Feature (gprsOpt) or ECERM Feature (ecermOpt) is disabled. Exists only at a BSC.
Displayed in the Enhanced Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the value which the error count must be equal to or less than for a GCI alarm to be cleared. Valid values: 0 - 253. Default value: 0. If a user changes the threshold value, an alarm is not immediately cleared. The new threshold only takes effect when the GCI error count changes. Grayed-out if the GPRS Feature (gprsOpt) or ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. Continued
Displayed in the Enhanced Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the GCI error increment value. The system updates the GCI error count by this value whenever an error is detected. Valid range: 0 (Disabled) - 255. Default value: 1. If a user set the value to 0, an error message is displayed indicating that no more GCI alarms will be generated. Set to 0, if either the GPRS or ECERM feature is disabled. Grayed-out if the GPRS Feature (gprsOpt) or ECERM Feature (ecermOpt) is disabled. Exists only at a BSC.
GPRS Alarm Time gprs_alarm_time (OMC-R parameter name: gprsAlarmTime)
Displayed in the Enhanced Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the time period in which the error counters are incremented if an error indication is received for a GCI, or decremented if no error indication is received. Valid values: 0 (Disabled), 5 - 240 seconds. Default values: •
60, when GPRS and ECERM are enabled.
•
0, if either GPRS or ECERM is disabled.
Grayed-out if the GPRS Feature (gprsOpt) or ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. PIC Error Gen Threshold pic_error_gen_thresh (OMC-R parameter name: picErrGenThresh)
Displayed in the Enhanced Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the PIC error count threshold at the BSC. Once this threshold is reached, further PIC errors do not increase the PIC error count. When this threshold is reached or exceeded a PIC alarm is generated. Valid values: 2 - 255. Default value: 6. If a user changes the threshold value, an alarm is not immediately generated. The new threshold only takes effect when the PIC error count changes. Grayed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC. Continued
2-72
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displayed in the Enhanced Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the value which the error count must be equal to or less than for a PIC alarm to be cleared. Valid values: 0 - 253. Default value: 0. If a user changes the threshold value, an alarm is not immediately cleared. The new threshold only takes effect when the PIC error count changes. Grayed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC.
Displayed in the Enhanced Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the PIC error increment value. The system updates the PIC error count by this value whenever an error is detected. Valid range: 0 (Disabled) - 255. Default value: 1. If a user set the value to 0, an error message is displayed indicating that no more PIC alarms will be generated. Set to 0, if the ECERM feature is disabled. Grayed-out if the ECERM Feature (ecermOpt) is disabled. Exists only at a BSC.
RCI Error Gen Threshold rci_error_gen_thresh
Displayed in the Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the RCI error count threshold at the BSC. Once this threshold is reached, further RCI errors do not increase the RCI error count. When this threshold is reached or exceeded, an RCI alarm is generated. Valid range: 2 - 255. Default value: 6. If a user changes the threshold value, an alarm is not immediately generated. The new threshold only takes effect when the RCI error count changes. Must be two greater than rci_error_clr_thresh.
RCI Error Clear Threshold rci_error_clr_thresh
Displayed in the Circuit Error Rate Monitor grouping in the BSS Detailed View form. Specifies the Radio Channel Identifier (RCI) error count clearing threshold at the BSC. When the error count reaches or falls below this threshold the alarm clears. Valid range: 0 - 253. Default value: 0. Must be two less than rci_error_gen_thresh. Continued
68P02901W17-S
2-73 Dec 2009
Methods for configuring ECERM
Table 2-11
Chapter 2: Configuring BSS Features
ECERM parameters (Continued)
OMC-R GUI field name/BSS parameter name RCI Error Increment rci_error_inc
Description Displayed in the Circuit Error Rate Monitor grouping in the BSS Detailed View. Specifies the Radio Channel Identifier (RCI) error increment value. The system updates the RCI error count by this value whenever an error is detected. Valid range: 0 (Disabled) - 255. Default value: 1. If a user set the value to 0, an error message is displayed indicating that no more RCI alarms will be generated.
Displayed in the Circuit Error Rate Monitor grouping in the SITE Detailed View. This parameter is supported at BTS sites. If a user changes this parameter, a warning message is displayed indicating that a site reset occurs when the value is saved.
Displayed in the Circuit Error Rate Monitor grouping in the SITE Detailed View. This parameter is supported at BTS sites. If a user changes this parameter, a warning message is displayed indicating that a site reset occurs when the value is saved.
Displayed in the Circuit Error Rate Monitor grouping in the SITE Detailed View form. This parameter is supported at BTS sites. If a user changes this parameter, a warning message is displayed indicating that a site reset occurs when the value is saved.
Static Sync Timer static_sync_timer
Displayed in the GPRS grouping in the SITE Detailed View. This parameter is supported at BTS sites. If a user changes this parameter, a warning message is displayed indicating that a site reset occurs when the value is saved. Valid values: 1 - 65535, when the GPRS Feature is enabled. Default value: 0, when the GPRS feature is disabled. Grayed-out in the SITE 0 Detailed View if the GPRS Feature (gprsOpt) is disabled.
Methods for configuring ECERM The ECERM feature can be configured using:
2-74
•
OMC-R GUI, using the BSS Detailed View (Circuit Error Rate Monitor grouping), and SITE Detailed View (Circuit Error Rate Monitor grouping), and the fields detailed in Table 2-11.
•
TTY interface, see Configuring ECERM using the TTY interface.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring ECERM using the TTY interface
Configuring ECERM using the TTY interface Using chg_ and disp_element commands The chg_element and disp_element commands can be used to configure and change the ECERM parameters shown in Table 2-11. Some examples are also given in the following sections. See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS commands, prompts, and parameters.
Displaying the current GPRS alarm increment/decrement period Use the disp_element command to display the current GPRS Alarm Increment/Decrement Period parameter of the BSC. For example, the following command displays the current setting at the BSC: disp_element gprs_alarm_time 0 The system replies, for example: gprs_alarm_time = 30
Setting the GPRS alarm increment/decrement period Use the chg_element command to change the GPRS Alarm Increment/Decrement Period parameter. For example, the following command changes the GPRS Alarm Increment/Decrement Period parameter to 40 at the BSC: chg_element gprs_alarm_time 40 0 COMMAND ACCEPTED
Changing the initial sync timer parameter Use the chg_element command to change the Initial Sync Timer parameter. For example, the following command changes the Initial Sync Timer to 2000 at the BSC: chg_element initial_sync_timer 2000 0 The system responds with the following prompts for further information (bold text shows typical user responses): Enter value for downlink sync timer: 1000 Enter value for uplink sync timer: 1000 Enter value for static sync timer: 1000 WARNING: Changing initial_sync_timer will cycle device SITE. Are you sure (y = yes, n = no)? y COMMAND ACCEPTED
68P02901W17-S
2-75 Dec 2009
Advanced Load Management for EGSM
Chapter 2: Configuring BSS Features
Advanced Load Management for EGSM ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to Advanced Load Management for EGSM The Advanced Load Management (ALM) for EGSM feature is an optional feature. It enables an EGSM mobile to handover to an EGSM resource on a neighboring cell rather than allowing it to be handed over to a neighboring cell which may not contain EGSM carriers. Before the introduction of the Advanced Load Management for EGSM feature, EGSM carriers in a PGSM/EGSM and DCS1800 multiband network were under utilized because of the interaction with the multiband handover feature. A typical example of this is when an EGSM mobile is established on a PGSM cell (which has EGSM capabilities) and the neighbor cell uses the Multiband Handover feature with the band preference set to DCS1800, and the band preference mode set to 4. If there is idle EGSM TCH capacity, the mobile is assigned to the EGSM TCH resource and when a handover is triggered, the mobile is targeted to the DCS 1800 band. The result is EGSM resources are under utilized. To allow EGSM resources to be fully utilized, the Advanced Load Management for EGSM feature introduces an EGSM targeting algorithm which the operator can enable in the BSS software. The EGSM targeting algorithm selects an internal EGSM capable neighbor cell, rather than a non-EGSM cell, when a handover is triggered. For a full description of Advanced Load Management for EGSM, see Technical Description: BSS Implementation (68P02901W36).
Restrictions and dependencies to ALM for EGSM Before Advanced Load Management for EGSM can be enabled, there must not be any: •
Coincident multiband cells.
•
EGSM BCCH frequencies.
•
Hopping through EGSM frequencies within a PGSM/EGSM cell.
Also external handovers assume that a cell with PGSM BCCH is a PGSM only cell.
Interaction with other features This feature interacts with the IMRM feature, see Intelligent Multilayer Resource Management (IMRM) on page 2-148 for further details.
2-76
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
ALM for EGSM parameters
ALM for EGSM parameters Table 2-12 details the parameters associated with configuring Advanced Load Management for EGSM. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
Table 2-12
Advanced Load Management for EGSM parameters
OMC-R GUI field name/BSS parameter name ALM Enhancement for EGSM Carriers (OMC-R parameter name: AlmEgsmOpt)
Description Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether Advanced Load Management for EGSM feature is unrestricted at the BSS. Valid values: 0 or 1, where: •
0 - Disabled (restricted).
•
1 - Enabled (unrestricted).
Displayed in the General grouping of the BSS Detailed View. Indicates whether Advanced Load Management for EGSM is enabled or disabled at the BSS. Valid values: 0 or 1, where: •
0 - Disabled.
•
1 - Enabled.
This field is grayed-out if the field: ALM Enhancement for EGSM Carriers (parameter name:AlmEgsmOpt) has been set to Disabled (0).
Methods of configuring ALM for EGSM ALM for EGSM can be configured using: •
OMC-R GUI BSS Detailed View and the fields shown in Table 2-12.
•
TTY interface, see Configuring ALM for EGSM using the TTY interface.
Configuring ALM for EGSM using the TTY interface Displaying current setting of ALM for EGSM using the TTY interface To display the current setting for Advanced Load Management for EGSM feature (that is, whether it is restricted or unrestricted at the BSS) using the TTY interface, use the disp_element command. For example: disp_element bss_egsm_alm_allowed bsc If Advanced Load Management for EGSM is unrestricted (enabled), the system displays: bss_egsm_alm_allowed = 1 68P02901W17-S
2-77 Dec 2009
Configuring ALM for EGSM using the TTY interface
Chapter 2: Configuring BSS Features
If Advanced Load Management for EGSM is restricted (disabled), the system displays: bss_egsm_alm_allowed = 0
Enabling and disabling ALM for EGSM using the TTY interface To modify the current setting for Advanced Load Management for EGSM (that is, to enable or disable the feature at the BSS) using the TTY interface, use the chg_element command and the bss_egsm_alm_allowed parameter. The feature can only be enabled at the BSC. For example, the following command enables Advanced Load Management for EGSM at a BSC: chg_element bss_egsm_alm_allowed 1 bsc
2-78
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Network Controlled Cell Reselection
Network Controlled Cell Reselection ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description of Network Controlled Cell Reselection (NCCR) In a GPRS network, cell reselection is the equivalent of a GSM circuit switched handover. In general, as the location of a mobile or RF conditions change, or cells get congested, cell reselection offers mobility and performs network traffic management. The different modes of cell reselection in GPRS network are referred to as: •
NC0.
•
NC1.
•
NC2.
•
RESET.
The main objective of Network Controlled Cell Reselection (NCCR) and congestion relief is to increase network capacity and provide a tool for network planning and improved quality of service. The operator can specify GPRS cell reselection mode on a per cell basis providing the flexibility of virtual zones within the network of cells with same cell reselection order. Table 2-13 details the cell reselection modes offered by Motorola.
Table 2-13
GPRS cell reselection modes
Cell Reselection Mode
Responsible Network Element
Functionality
NC0
MS control
Normal GPRS mobile control. The mobile performs autonomous cell reselection based on the radio environment.
Enhanced NC0
MS control
Includes all functionality provided by NC0 mode. BSS sends cell reselection commands to GPRS MS to change reselection mode.
NC1
MS control
GPRS mobile control with measurement reports to the BSS. MS performs autonomous cell reselection.
Enhanced NC1
MS control
All functionality in NC1 mode. BSS sends cell reselection command to GPRS mobile to change cell reselection mode.
NC2
Network control
Network control. GPRS MS sends measurement reports to the BSS. BSS sends cell reselection commands and instructs mobile to perform cell reselection.
For a full description of NCCR, see Technical Description: BSS Implementation (68P02901W36).
68P02901W17-S
2-79 Dec 2009
Determining whether Network Controlled Cell Reselection (NCCR) is enabled
Chapter 2: Configuring BSS Features
Determining whether Network Controlled Cell Reselection (NCCR) is enabled NCCR is an optional feature, which must be unrestricted for a BSS in order for it to be used. If NCCR is enabled, the GPRS option must also be enabled.
Using the OMC-R GUI To check if NCCR is restricted or unrestricted, using the OMC-R GUI, display the setting of the Network Controlled Cell Reselection Feature field in the Optional Features grouping in the BSS Detailed View. The values for nccrOpt are: •
Disabled (0).
•
Enabled (1).
•
Default is Disabled (0).
This field cannot be changed by a user.
Using the TTY interface To check if NCCR is unrestricted using the TTY interface, enter the following command: disp_options all If the NCCR optional feature is unrestricted, the system displays the following in the unrestricted list: 43 Network Controlled Cell Reselection
Network Controlled Cell Reselection parameters Table 2-14 details the Network Controlled Cell Reselection parameters. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference
(68P02901W23).
2-80
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-14
Network Controlled Cell Reselection parameters
Network Controlled Cell Reselection parameters
OMC-R GUI field name/BSS parameter name
Description
NCCR Enabled nccr_enabled
Displayed in the Network Controlled Cell Reselection grouping in the BSS Detailed View form. Indicates whether the Network Controlled Cell Reselection feature is Enabled (1) or Disabled (0). The default is Disabled (0). This field can be modified by a user. This field is grayed-out if the BSS Detailed View field: Network Controlled Cell Reselection Feature (parameter name: nccrOpt) is set to Disabled (0).
NC Reporting Period Idle nc_reporting_period_i
Displayed in the Network Controlled Cell Reselection grouping in the BSS Detailed View form. Indicates the time interval between successive measurement reports from a GPRS MS to the BSS when the MS is idle. Valid values are: 4 - 6, where: 4 - 15.36 seconds 5 - 30.72 seconds 6 - 61.44 seconds The default is 6, that is, 61.44 seconds. This field is grayed-out if the BSS Detailed View field: Network Controlled Cell Reselection Feature (parameter name: nccrOpt) is set to Disabled (0).
NC Non Drx Period nc_non_drx_period
Displayed in the Network Controlled Cell Reselection grouping in the BSS Detailed View form. Indicates the time interval the BSS expects the MS to read the paging channel (CCCH) for a control message (PCCO). Valid values are: 0 - 7, where: 0 - No non_drx_period after a measurement report has been sent. 1 - 0.24 seconds 2 - 0.48 seconds 3 - 0.72 seconds 4 - 0.96 seconds 5 - 1.20 seconds 6 - 1.44 seconds 7 - 1.92 seconds The default is 2, that is, 0.48 seconds. This field is grayed-out if the BSS Detailed View field: Network Controlled Cell Reselection Feature (parameter name: nccrOpt) is set to Disabled (0). Continued
NC Reporting Period Transfer nc_reporting_period_t
Displayed in the Network Controlled Cell Reselection grouping in the BSS Detailed View form. Indicates the time interval between successive measurement reports from a GPRS MS to the BSS when the MS is transferring packet data. Valid values are: 0 - 6, where: 0 - 0.96 seconds 1 - 1.92 seconds 2 - 3.84 seconds 3 - 7.68 seconds 4 - 15.36 seconds 5 - 30.72 seconds 6 - 61.44 seconds The default is 2, that is, 3.84 seconds. This field is grayed-out if the BSS Detailed View field: Network Controlled Cell Reselection Feature (parameter name: nccrOpt) is set to Disabled (0).
Network Control Order network_control_order (OMC-R parameter name: netwk_ctrl_order)
Displayed in the General - Cell Selection-Reselection grouping in the CELL Detailed View form. Indicates the network entity responsible for cell reselection. Valid values are: 0 - 4, where: 0 - NC0 1 - NC1 2 - NC2 3 - Enhanced NC0 4 - Enhanced NC1 The default is 0. This parameter can be modified regardless of whether the cell is GPRS enabled/disabled. This field is grayed-out if the BSS Detailed View field: Network Controlled Cell Reselection Feature (parameter name: nccrOpt) is set to Disabled (0). Cannot be set to 1, 2, 3 or 4, if inter_rat_enabled is set to 1 (Idle) and the PBCCH/PCCCH feature (pccchOpt) is unrestricted.
Bad PMRs gprs_num_pmrs
Displayed in the GPRS - Network Controlled Cell Reselection grouping of the CELL Detailed View. Indicates the number of bad Packet Resource Reports (PMR) that are received before the PCU initiates network controlled cell reselection. (A bad PMR is one in which the difference between the serving cell's rxlev and the serving cell's configured value of rxlev_access_min is less than gprs_cr_margin.) Grayed-out if the Network Controlled Cell Reselection Feature (nccrOpt) is Disabled (0) for the BSS. Valid values: 1 - 10. The default is 3. Continued
2-82
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
OMC-R GUI field name/BSS parameter name PMR Threshold gprs_cr_margin
Description Displayed in the GPRS - Network Controlled Cell Reselection grouping of the CELL Detailed View. Indicates the threshold at which the network determines the Packet Resource Report (PMR) received from the MS is a bad PMR. Grayed-out if the Network Controlled Cell Reselection Feature (nccrOpt) is Disabled (0) for the BSS. Valid values: 5 - 40. The default is 30.
NCCR changes to Detailed Views The NCCR feature adds a GPRS checkbox to the BA Type field (parameter ba_type) in the following OMC-R GUI Detailed Views: •
Neighbor Detailed View*
•
TestNeighbor Detailed View*
•
Neighbor Template Detailed View*
•
Multiple TestNeighbor Create Form*
•
Neighbor Template View Form
•
Source/Neighbor View Form
An asterisk (*) in the list above indicates that the GPRS checkbox is grayed-out if the Network Controlled Cell Reselection Feature (parameter name: nccrOpt) field is set to Disabled (0) in the Optional Features grouping of the BSS Detailed View. Also, at least one of the checkboxes in the BA Type field must be checked before the Detailed View can be saved. It is possible to select the following combinations in the BA Type field: •
SACCH or BCCH or GPRS
•
SACCH or BCCH
•
SACCH and GPRS
•
BCCH and GPRS
•
SACCH and BCCH and GPRS
Methods for configuring NCCR The NCCR feature can be configured using: •
OMC-R GUI BSS and CELL Detailed Views and the fields shown in Table 2-14.
•
TTY interface, see Configuring NCCR using the TTY interface.
68P02901W17-S
2-83 Dec 2009
Configuring NCCR using the TTY interface
Chapter 2: Configuring BSS Features
Configuring NCCR using the TTY interface Using chg_element and disp_element commands to change NCCR parameters The chg_element and disp_element commands can be used to configure and change the NCCR parameters shown in Table 2-14. Some examples are also given in the following sections. See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS commands, prompts, and parameters.
Displaying the current NCCR parameter values Use the disp_element command to display the current values of NCCR parameters shown in Table 2-14. For example, the following command displays the value of nc_reporting_period_i at site 5: disp_element nc_reporting_period_i 5 The system replies, for example: nc_reporting_period_i = 6 The following command displays the value of the network_control_order parameter at site 5, cell id 0010116: disp_element network_control_order 5 cell 0 0 1 0 1 1 6
Changing the NCCR parameter values To change the NCCR parameter values, use chg_element. For example, the following command changes the value of nc_reporting_period_i to 4 at site 5: chg_element nc_reporting_period_i 4 5
Changing the network_control_order parameter To change the network_control_order parameter, use the chg_cell_element command. for example, the following command changes the value of network_control_order to 2 (for NC2) at site 3, cell 0010116: chg_cell_element 3 network_control_order 2 cell 0 0 1 0 1 1 6
NCCR changes to neighbor commands The NCCR feature modifies the add_neighbor, modify_neighbor, and disp_neighbor commands. •
New add_neighbor prompts: Table 2-15 details the additional system prompts for NCCR information when the add_neighbor is used.
2-84
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-15
Configuring NCCR using the TTY interface
add_neighbor NCCR-related prompts Prompt
Values
Default
Add neighbor to the BA BCCH list (yes/no)?
yes or no
yes
Add neighbor to the BA SACCH list (yes/no)?
yes or no
yes
Add neighbor to the BA GPRS list (yes/no)? (Only displayed if NCCR is restricted for the BSS.)
yes or no
yes
0 - 63
None
Enter base station identity code (bsic): (Prompted for all external neighbors.)
If an attempt is made to create a neighbor, which is not present in any of the BCCH, SACCH or GPRS lists, the command is rejected and an error message is displayed. •
modify_neighbor NCCR changes: The modify_neighbor command can be used to specify if a previously added frequency should be added or removed from the ba_gprs list. For example, the following command attempts to delete the neighbor 0010112 of cell 0010111 from the GPRS list, when the neighbor is not present in both the SACCH and BCCH lists: modify_neighbor 0 0 1 0 1 1 1 0 0 1 0 1 1 2 ba_gprs delete COMMAND REJECTED: Neighbor not present in SACCH list: remove from BCCH/GPRS list.
must be deleted to
The following command adds the neighbor 0010112 of cell 0010111 on the GPRS list, when NCCR is unrestricted in the BSS: modify_neighbor 0 0 1 0 1 1 1 0 0 1 0 1 1 2 ba_gprs add COMMAND ACCEPTED If a user attempts to include a neighbor's frequency on the GPRS list when the NCCR feature is restricted at the BSS, the command is rejected and an error message is displayed. •
disp_neighbor NCCR changes: The disp_neighbor command can be used to display whether the frequencies of the neighboring cells are part of the ba_gprs list. For example, the following command displays all neighbor cells of cell 0010111, when NCCR is unrestricted at the BSS: disp_neighbor 0 0 1 0 1 1 1 all The system responds by displaying a report including a GPRS column.
68P02901W17-S
2-85 Dec 2009
Configuring NCCR using the TTY interface
Chapter 2: Configuring BSS Features
The following command displays all neighbor information for neighbor cell 0010114 of cell 0010111, when NCCR is unrestricted at the BSS: disp_neighbor 0 0 1 0 1 1 4 0 0 1 0 1 1 1 The system responds by displaying a report including Frequency in the ba_type list information. See Technical Description: BSS Command Reference (68P02901W23) for full details of the reports displayed. •
del_neighbor NCCR changes: The del_neighbor command can be used to delete the frequencies of the neighboring cells from the ba_type list. For example, the following command deletes the cell 0010114 from the neighbor list of cell 0010111: del_neighbor 0 0 1 0 1 1 1 0 0 1 0 1 1 4
2-86
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
GPRS Interleaving TBFs
GPRS Interleaving TBFs ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description of TBF A Temporary Block Flow (TBF) is a logical connection used by the two GPRS RR entities to support unidirectional transfer of LLC PDUs on packet data physical channels. The TBF is allocated a radio resource on one or more PDCHs and comprises a number of RLC/MAC blocks carrying one or more LLC PDUs. A TBF is temporary and is maintained only for the duration of a data transfer; that is, until there are no more RLC/MAC blocks to be transmitted and, in RLC acknowledged mode, all of the transmitted RLC/MAC blocks have been successfully acknowledged by the receiving entity.
Description of GPRS interleaving TBFs Interleaving TBFs allow the rapid multiplexing of RLC data blocks of many different mobiles on to a common air resource. Many mobiles can then share a common air resource (although the effective throughput of each mobile on the shared resource may be decreased). Each mobile sharing a common air resource is given a percentage of the bandwidth of the shared resource. For example, if two mobiles are interleaved on the same air timeslot, one mobile can be given 70% of the timeslot, and the second mobile is given the remaining 30%. Interleaving increases the number of users on a single timeslot, therefore increasing the overall capacity (in terms of number of users) of a serving cell. Interleaving TBFs in the uplink and downlink use Block-by-Block multiplexing, which involves multiplexing two or more mobiles on a timeslot with the capability of switching between mobiles every block period. All mobiles on a timeslot are simultaneously active in TBFs. The TBF setup, release, and data transfer phases of the TBF for one mobile can overlap the TBF setup, release, and data transfer phases of other TBFs belonging to other mobiles. For a full description of this feature, see Technical Description: BSS Implementation (68P02901W36).
Delayed Downlink TBF Release When in Delayed Downlink TBF Release mode, the BSS sends dummy data blocks at least every 24 block periods to the MS if no new data is available. If new downlink data does not arrive within a predetermined number of block periods, downlink TBF is released. If new data arrives for an MS in Delayed Downlink TBF Release mode, then the BSS exits Delayed Downlink TBF Release mode and continues in data transfer mode. The BSS parameter delay_dl_rel_dur determines the number of block periods in which the network delays the release of a downlink TBF. See Table 2-16 for details.
68P02901W17-S
2-87 Dec 2009
Delayed Downlink TBF Release Control
Chapter 2: Configuring BSS Features
Delayed Downlink TBF Release Control When Delayed Downlink TBF Release Control is enabled, the BSS monitors and calculates the availability of timeslot resources in the cell as cell availability, and terminates one or more downlink TBFs in Delayed Downlink Release mode if the cell is under congestion. The downlink TBFs terminated due to cell availability will be in Delayed Downlink TBF Release mode for less than the number of blocks determined by delay_dl_rel_dur. Delayed Downlink TBF Release Duration as a function of cell availability is enabled and disabled using the BSS parameter ddtr_ctrl_enabled. See Table 2-16 for details.
Delayed Uplink TBF Release When a downlink TBF does not exist for the MS, the BSS extends the uplink TBF of the MS by delaying the release of the uplink TBF. If a new downlink TBF is not established for the MS within the predetermined number of block periods, uplink TBF is released. If a new downlink TBF is established for the MS, the BSS releases the uplink TBF immediately. The BSS parameter delay_ul_rel_dur determines the number of block periods in which the network delays the release of an uplink TBF. See Table 2-16 for details.
GPRS interleaving TBFs capacity The BSS can support: •
Up to four unique mobiles in both the Uplink and Downlink directions on a timeslot.
•
Up to 120 active downlink TBFs per PRP board.
•
Up to 120 active uplink TBFs per PRP board.
•
Up to 120 active mobiles per PRP board.
GPRS interleaving TBFs parameters Table 2-16 details the GPRS interleaving parameters for a BSS and cell. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
2-88
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displayed in the GPRS grouping in the BSS Detailed View form. The number of block periods in which the network delays the release of a downlink TBF. One block period is 20 ms. Valid values: 15 - 600 blocks. Default is 50 blocks. Can only be modified if the GPRS Feature (gprsOpt) is unrestricted (Enabled) in the BSS Detailed View. Otherwise, the field is grayed-out in the Detailed View form.
Displayed in the GPRS grouping in the BSS Detailed View form. The number of block periods in which the network delays the release of an uplink TBF. Valid values: 10 - 50 blocks. Default is 18 blocks. Grayed-out if the GPRS feature (gprsOpt) is restricted at the BSS.
Delayed Downlink TBF Release Control ddtr_ctrl_enabled
Displayed in the GPRS grouping in the BSS Detailed View form. Whether the BSS supports the feature for Delayed Downlink TBF Release Duration as a function of cell availability. Valid values: Disabled (0) or Enabled (1). Default is 0. Grayed-out if either the GPRS feature (gprsOpt) or Increased PRP Capacity feature is restricted at the BSS. {26881} The ddtr_ctrl_enabled parameter enables or disables the functionality related to delayed downlink TBF release duration and extended uplink TBF duration of cell availability. Valid values: 0 or 1 0 - Disable the functionality related to delayed downlink TBF release duration and extended uplink TBF duration of cell availability. 1 - Enable the functionality related to delayed downlink TBF release duration and extended uplink TBF duration of cell availability. This element requires the GPRS feature and Increased PRP Capacity feature to be unrestricted.
Auto Downlink Duration auto_dl_dur
Displayed in the GPRS grouping in the BSS Detailed View form. The number of block periods in which the network keeps a new downlink TBF, which was created through the auto downlink mechanism, alive while waiting for new downlink data to arrive. One block period is 20 ms. Valid values: 15 - 250 blocks. Default is 50 blocks. Can only be modified if the GPRS Feature (gprsOpt) is unrestricted (Enabled) in the BSS Detailed View. Otherwise, the field is grayed-out in the Detailed View form. Continued
68P02901W17-S
2-89 Dec 2009
Impact of GPRS interleaving TBFs on a BSS
Table 2-16
Chapter 2: Configuring BSS Features
GPRS interleaving BSS and cell parameters (Continued)
OMC-R GUI field name/BSS parameter name GPRS Scheduling Beta Algorithm gprs_sched_beta
Description Displayed in the GPRS grouping in the BSS Detailed View form. The scheduling beta algorithm at the BSS. Valid values: 0 - 2, where: •
0 - Each MS throughput in bps is the same.
•
1 - Each MS transfers the same number of blocks as every other mobile.
•
2 - MS with the higher coding scheme is preferred.
Can only be modified, if the GPRS Feature (gprsOpt) is unrestricted (Enabled) in the BSS Detailed View. Otherwise, the field is grayed-out. If gprs_sched_beta is modified and saved while the QoS feature (see Quality of Service (QoS) on page 2-157) is enabled, the following message is displayed: “WARNING: Changes to gprs_sched_beta are overridden while QoS is enabled”. Cell Parameter: Max Number of TS In Pre-load USF Active State ts_in_usf_active
Displayed in the GPRS grouping in the CELL Detailed View form. The maximum number of non-BCCH timeslots allowed to be in preload USF (Uplink State Flag) active state in the cell at the same time. (That is, the number of non-BCCH timeslots that are broadcast continuously at full power even when no mobile is active on the timeslot.) Valid values are 0 - 3. If not set by a user at cell creation time, defaults to 1 timeslot. Can only be modified, if the GPRS Feature (gprsOpt) and Enhanced GPRS One Phase feature are unrestricted (Enabled) in the BSS Detailed View. Otherwise, the field is grayed-out in the CELL Detailed View form.
Impact of GPRS interleaving TBFs on a BSS The introduction of GPRS interleaving TBFs modifies the BSS parameter gprs_mac_mode, which determines the medium access mode to be used by the BSS. gprs_mac_mode now only supports dynamic access mode (1), which is also the default. For example, the following command changes gprs_mac_mode to dynamic access mode: chg_element gprs_mac_mode 1 bsc
Methods for configuring GPRS interleaving TBFs The GPRS interleaving TBFs feature can be configured using:
2-90
•
OMC-R GUI BSS and CELL Detailed Views and the fields shown in Table 2-16.
•
TTY interface, see Configuring GPRS interleaving TBFs using the TTY interface.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring GPRS interleaving TBFs using the TTY interface
Configuring GPRS interleaving TBFs using the TTY interface Displaying the current GPRS interleaving TBF BSS parameter values Use the disp_element command to display the current value of a BSS GPRS interleaving TBFs parameter detailed in Table 2-16. For example, the following command displays the current value of auto_dl_dur: disp_element auto_dl_dur 0 The system replies, for example: auto_dl_dur = 20
Modifying GPRS interleaving TBF BSS parameter values Use the chg_element command to change the value of a BSS GPRS interleaving TBFs parameter detailed in Table 2-16. For example, the following command changes auto_dl_dur to 20: chg_element auto_dl_dur 20 0
Displaying the current value of ts_in_usf_active Use the disp_element command to display the current value of the GPRS interleaving TBFs cell parameter ts_in_usf_active detailed in Table 2-16. For example, the following command displays the current value of ts_in_usf_active at the BSC, cell 0010111: disp_element ts_in_usf_active 0 cell 0 0 1 0 1 1 1 The system replies, for example: ts_in_usf_active = 1
Modifying the current value of ts_in_usf_active Use the chg_element or chg_cell_element command to display the current value of the GPRS interleaving TBFs cell parameter ts_in_usf_active detailed in Table 2-16. For example, the following commands change ts_in_usf_active to 1 at cell 0010111: chg_cell_element ts_in_usf_active 1 0 0 1 0 1 1 1 chg_element ts_in_usf_active 1 0 cell 0 0 1 0 1 1 1
68P02901W17-S
2-91 Dec 2009
Enhanced BSC Capacity
Chapter 2: Configuring BSS Features
Enhanced BSC Capacity ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to the Enhanced BSC Capacity feature The Enhanced BSC Capacity feature is an optional feature, which increases the capacity of the BSC from 384 carriers and 2400 circuits (CICs) to 512 carriers and 3200 circuits (CICs).
NOTE If either GSM HR and/or AMR has been purchased and enabled, a maximum of 4800 CICs can be equipped at an RXCDR site. The Enhanced BSC Capacity feature also increases the number of entries in the BSC-RXCDR connectivity table to 27.
Determining whether Enhanced BSC Capacity is enabled Using the OMC-R GUI To check if the Enhanced BSC Capacity feature has been enabled using the OMC-R GUI, display the setting of the Enhanced BSC Capacity Feature (ebscOpt) field in the Optional Features grouping in the BSS Detailed View. The values for Enhanced BSC Capacity Feature field are: •
Disabled (0).
•
Enabled (1).
•
Default is Disabled (0).
Using the TTY interface To check if Enhanced BSC Capacity has been enabled using the TTY interface, enter the following command: disp_options all If the Enhanced BSC Capacity is unrestricted (enabled) the system displays the following in the unrestricted list: 49 Enhanced BSC Capacity
2-92
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Overview of Inter-RAT Handover Initially, when network operators provide a UMTS service, there may only be small pockets of UMTS coverage in a predominantly GSM coverage network. In this situation, when a UMTS subscriber leaves a UMTS coverage area, the call may be dropped. UMTS subscribers may also face problems establishing a UMTS call when the traffic in the UMTS coverage area is high. To avoid these problems, the Inter-RAT Handover feature can be enabled. The Inter-RAT Handover feature allows a multi-RAT mobile station (MS) to perform 2G to 3G cell selection/reselection in idle mode, and 3G to 2G handovers in circuit-switched dedicated mode. When the Inter-RAT Handover feature is enabled at a BSS, the BSS broadcasts new system information messages to allow a multi-RAT MS to perform measurements on UMTS FDD (UTRAN) neighbor cells for handover and cell selection/reselection purposes. When in dedicated mode, Inter-RAT Handover provides 3G measurement control parameters to the MS. When the Inter-RAT Handover feature is enabled at a BSS, it can then be enabled or disabled for individual cells.
Inter-RAT Handover dependencies The Inter-RAT Handover feature requires: •
Multi-RAT mobile stations, which are capable of accessing the Core Network (CN) from a UMTS coverage area and a GSM coverage area. The MS must be capable of operating in either GSM or UMTS cells including execution of procedures such as PLMN selection, cell reselection, measurements in idle mode and dedicated mode, and so on.
•
A UMTS network including 2G/3G compatible MSC.
•
Existing 2G CN nodes must be able to interact with the 3G CN nodes through MAP procedures defined on the E-interface between a 3G CN node and 2G CN node.
68P02901W17-S
2-93 Dec 2009
Enhanced Inter-RAT Handover feature
Chapter 2: Configuring BSS Features
Enhanced Inter-RAT Handover feature The Enhanced 2G/3G Handover and Cell Reselection feature (also referred to as the Enhanced Inter-RAT Handover feature) provides support in the BSS for: •
Outgoing dedicated mode handover from 2G to 3G (basic measurement-based and service-based handover triggers).
•
BSS control for measurement reporting by multi-RAT MS, UTRAN early classmark sending blind search for cell reselection from 2G to 3G.
•
Inter-RAT related performance measurements.
The Enhanced Inter-RAT feature also introduces a new device called a Blind Search Neighbor, which is supported under a cell, and represents the blind search neighbors of a cell. See UTRAN blind search neighbor on page 8-138 for further details.
Additional information For further details of the Inter-RAT Handover feature and the Enhanced Inter-RAT Handover feature, see Technical Description: BSS Implementation (68P02901W36).
Interaction with other features This feature interacts with the IMRM feature, see Intelligent Multilayer Resource Management (IMRM) on page 2-148 for further details.
Inter-RAT Handover and Enhanced Inter-RAT Handover parameters Table 2-17 lists the parameters associated with the Inter-RAT Handover and Enhanced Inter-RAT Handover features. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
2-94
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration Handover and Enhanced Inter-RAT Handover parameters
Table 2-17
Inter-RAT
Inter-RAT Handover and Enhanced Inter-RAT handover parameters
Displayed in the Optional Features grouping of the BSS Detailed View form. Indicates whether the Inter-RAT Handover Feature is restricted (disabled) or unrestricted (enabled) in the BSS software. This parameter cannot be modified by a user. When the Enhanced Inter-RAT Handover Feature (EnhncdInterRatOpt) is set to 1 (Enabled), InterRatOpt is automatically set to 1 (Enabled).
0 or 1, where: Disabled (0). Enabled (1). Default is Disabled (0).
Displayed in the Optional Features grouping of the BSS Detailed View form. Indicates whether the Enhanced Inter-RAT Handover Feature is restricted (disabled) or unrestricted (enabled) for the BSS. This parameter cannot be modified by a user. When the Enhanced Inter-RAT Handover Feature (EnhncdInterRatOpt) is set to 1 (Enabled), InterRatOpt is automatically set to 1 (Enabled).
0 or 1, where: Disabled (0). Enabled (1). Default is Disabled (0).
MSC Release msc_release
Displayed in the General grouping of the BSS Detailed View form. Indicates the release of the MSC to which this BSS is connected.
0 or 1, where: Release 1998 or older (0). Release 1999 or newer (1). Default is 0. Continued
68P02901W17-S
2-95 Dec 2009
Inter-RAT Handover and Enhanced Inter-RAT Handover parameters
Table 2-17 (Continued)
Chapter 2: Configuring BSS Features
Inter-RAT Handover and Enhanced Inter-RAT handover parameters
OMC-R GUI field name/BSS parameter name
Description
Values
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Indicates whether idle mode, dedicated mode, or idle mode and dedicated mode functionality of the Inter-RAT Handover feature are enabled for this cell. This field is grayed-out if the Inter-RAT Handover Feature (InterRatOpt) is restricted (disabled) for the BSS. Can only be set to 1 (Idle) if network_control_order is set to 0 (NC0). This field cannot be set to 4, 5, 6 or 7 if the container BSS has EnhancedInterRatOpt set to Disabled (0). If modified to either of 4, 5, 6 or 7 and the container BSS has earlyClassmarkSndset to 0 or 1, the following warning is displayed: “Enhanced 2G/3G requires early_classmark_sending to be enabled across both the A and Air Interfaces”. If modified to either of 4, 5, 6 or 7 and the container BSS has phase2ClssmkAld not set to 2, the following warning is displayed: “Enhanced 2G/3G requires phase2_classmark_allowed to be configured to support multiband”.
Installation and Configuration: GSM System Configuration Handover and Enhanced Inter-RAT Handover parameters
Table 2-17 (Continued)
Inter-RAT
Inter-RAT Handover and Enhanced Inter-RAT handover parameters
OMC-R GUI field name/BSS parameter name
Description
Values
BCCH RF Signal Level Threshold qsearch_i
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Used by the MS to determine when to start measuring a UTRAN neighbor cell. When the received RF signal level of the BCCH carrier in the serving GSM cell is below or above the qsearch_i value, the MS starts measurement of the UTRAN neighbor cells. This field is grayed-out if Inter-RAT Handover Feature (InterRatOpt) and TD-SCDMA Feature (tdOpt) are restricted (disabled) for the BSS. {31400} This parameter is modified to be capable of access when either tdOpt / InterRATOpt / EnhancedInterRATOpt is unrestricted.
Use BCCH RF Signal Level Threshold qsearch_c_initial
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. The value of this parameter is broadcast on the BCCH using the SYSTEM INFORMATION TYPE 2quater message, and determines if qsearch_I is used by the MS in dedicated mode after certain instances of MEASUREMENT INFORMATION messages are received, OR if the MS should always search. Modifying this parameter causes the SI2ter_MP_CHANGE_MARK and SI2quater MP_CHANGE_MARK to be toggled. This field is grayed-out if Inter-RAT Handover Feature (InterRatOpt) and TD-SCDMA Feature (tdOpt) are restricted (disabled) for the BSS. {31400} This parameter is modified to be capable of access when either tdOpt / InterRATOpt / EnhancedInterRATOpt is unrestricted.
0 or 1, where: 0 = Use Q Search_I 1 = Infinity (always) Default is 0.
Continued
68P02901W17-S
2-97 Dec 2009
Inter-RAT Handover and Enhanced Inter-RAT Handover parameters
Table 2-17 (Continued)
Chapter 2: Configuring BSS Features
Inter-RAT Handover and Enhanced Inter-RAT handover parameters
OMC-R GUI field name/BSS parameter name
Description
Values
Receive Signal Code Power (RSCP) Threshold fdd_qoffset
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Used by the MS in the cell reselection algorithm. This field is grayed-out if Inter-RAT Handover Feature (InterRatOpt) is restricted (disabled) for the BSS.
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Used by the MS in the cell reselection algorithm. This field is grayed-out if Inter-RAT Handover Feature (InterRatOpt) is restricted (disabled) for the BSS.
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Used by the MS in dedicated mode to decide when to start measurement of a UTRAN neighbor cell. This field is grayed-out if EnhncdInterRatOpt is Disabled (0).
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Indicates the measurement quantity to be reported for a UTRAN FDD cell. Grayed out if EnhncdInterRatOpt is Disabled (0).
0 or 1, where: 0 = RSCP. 1 = Ec/No. Default is 1 (Ec/No). Continued
2-98
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration Handover and Enhanced Inter-RAT Handover parameters
Table 2-17 (Continued)
Inter-RAT
Inter-RAT Handover and Enhanced Inter-RAT handover parameters
OMC-R GUI field name/BSS parameter name
Description
Values
Number of Serving Band cells to report serving_band_reporting
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Indicates the number of cells to be reported from the frequency band to which the serving GSM cell belongs. Grayed out if EnhncdInterRatOpt is Disabled (0).
Values: 0 - 3. Default is 3.
Number of UTRAN FDD cells to report fdd_multirat_reporting
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Indicates the number of UTRAN FDD cells to be reported in the list of strongest cells in the measurement report. Grayed out if EnhncdInterRatOpt is Disabled (0).
0 - 3. Default is 1.
Blind Search Preference blind_search_preference
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Indicates the preference for blind search in idle mode and/or dedicated mode. Grayed out if EnhncdInterRatOpt is Disabled (0). If modified from 0 to 1, and there are no UTRAN blind search neighbors equipped to that cell, the following warning message is displayed: “There are no Blind Search neighbors equipped for this cell”.
0 or 1, where: 0 = No blind search in idle mode. 1 = Blind search in idle mode. Default is 0 (No blind search in idle mode).
UMTS Band Preferred umts_band_preferred
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. Indicates whether handover to UMTS band is preferred. Grayed out if EnhncdInterRatOpt is Disabled (0)
0 or 1, where: 0 = No. 1 = Yes. Default is 0 (No).
Threshold when FDD_REP_QUANT is Ec/No umts_cpich_ec_no_min
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. It is a threshold parameter used by the handover algorithm when fdd_rep_quant is Ec/No(1). Grayed out if EnhncdInterRatOpt is Disabled (0).
-20 dBm to 0 dBm. Default is -15 dBm.
Threshold when FDD_REP_QUANT is RSCP umts_cpich_rscp_min
Displayed in the Inter-RAT Handover grouping of the CELL Detailed View form. It is a threshold parameter used by the handover algorithm when fdd_rep_quant is RSCP (0). Grayed out if EnhncdInterRatOpt is Disabled (0).
-53 dBm to -115 dBm. Default is -90 dBm.
Continued
68P02901W17-S
2-99 Dec 2009
Methods of configuring Inter-RAT Handover
Table 2-17 (Continued)
Chapter 2: Configuring BSS Features
Inter-RAT Handover and Enhanced Inter-RAT handover parameters
Displayed in the Identification parameter grouping in the UTRAN Detailed View form. It is a measurement parameter used by the handover algorithm. Grayed out if EnhncdInterRatOpt is Disabled (0).
0 dB to 20 dB. Default is 3 dB.
Averaging Period umtsNcellAvgPrd
Displayed in the General parameter grouping in the UTRAN Detailed View form. Indicates UTRAN neighbor cell measurement averaging period. Grayed out if EnhncdInterRatOpt is Disabled (0).
0 - 12. Default is 6.
UMTS BA Type umts_ba_type
Displayed in the General parameter grouping in the UTRAN Detailed View form. Specifies the neighbor lists: BCCH, SACCH, or BCCH and SACCH. Grayed out if EnhncdInterRatOpt is Disabled (0).
1 - 3, where: 1 = BCCH. 2 = SACCH. 3 = BCCH. and SACCH. Default is 3 (both buttons checked). If the SACCH option is selected, it cannot be modified after creation (whether selected or not).
Blind Search Neighbor parameters
See UTRAN blind search neighbor on page 8-138 for details.
Methods of configuring Inter-RAT Handover Inter-RAT Handover can be configured using: •
OMC-R GUI BSS and CELL Detail Views and the fields shown in Table 2-17.
•
TTY interface, see Configuring Inter-RAT Handover using the TTY interface.
Configuring Inter-RAT Handover using the TTY interface Checking if Inter-RAT Handover is unrestricted To check if the Inter-RAT Handover feature is unrestricted (enabled) using the TTY interface, enter the following command: disp_options
2-100
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring Inter-RAT Handover using the TTY interface
If Inter-RAT Handover is unrestricted, the following is displayed: 36 InterRat Handover 2G>3G Cell Reselection, 3G>2G Dedicated Mode.
Displaying and modifying Inter-RAT Handover parameters The disp_element, disp_cell, chg_element and chg_cell_element commands can be used to display and configure the Inter-RAT Handover cell parameters shown in Table 2-17. Some examples are also given in the following sections. See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS commands, prompts, and parameters.
Displaying whether Inter-RAT handover is enabled at a cell Use the disp_element command to display whether Inter-RAT Handover is enabled for a cell. For example, the following command displays the current setting at cell 0010114, site 0: disp_element inter_rat_enabled 0 cell_number = 0 0 1 0 1 1 4 The system replies, for example: inter_rat_enabled = 0
Setting cell parameters for Inter-RAT Handover Use the chg_cell_element command to change an Inter-RAT Handover cell parameter. For example, the following command changes qsearch_i to 10 for cell 0010114: chg_cell_element qsearch_i 10 0 0 1 0 1 1 4
68P02901W17-S
2-101 Dec 2009
GSM location services
Chapter 2: Configuring BSS Features
GSM location services ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description of Location Services Location services (LCS) is an optional feature, which identifies the physical location of a Mobile Station (MS) by using one or more positioning mechanisms. The location services feature provides support for a Motorola or third-party mobile positioning application. The positioning process involves two main steps: 1.
Signal measurement.
2.
Location estimate computation based on the measured signal.
Location services have been identified by operators, service providers and Motorola as being a key application enabler. For example, through applications tailored to use the position of the mobile device directly (Where am I?), to deliver tailored content (Location Specific Advertising) or to determine the routing of voice traffic (Location Sensitive Routing). Location services support is through: •
NSS-based Servicing Mobile Location Centre (SMLC), which is an SMLC communicating with an MSC through the Ls interface.
•
BSS-based SMLC, which is an SMLC communicating with the BSS through the Lb interface.
For a full description of location services, see Technical Description: BSS Implementation (68P02901W36).
Location services and the LMTL device The Location Services Message Transfer Link (LMTL) device is present in a BSS-based implementation of the LCS feature. The LMTL device refers to both the physical and logical interface between the BSC and the BSS-based SMLC. See Configuring an LMTL device on page 9-130 for details of how to configure an LMTL device.
Determining whether location services is unrestricted Location services is an optional feature.
Using the OMC-R GUI To check if location services is unrestricted (enabled) using the OMC-R GUI, display the setting of the Location Services field in the Optional Features grouping in the BSS Detailed View.
2-102
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Location services parameters
Using the TTY interface To check if location services feature is unrestricted using the TTY interface, enter the following command: disp_options all If the location services optional feature is unrestricted the system displays the following in the unrestricted list: 43 Location Services
Location services parameters Location services configurable parameters are divided into the following categories: •
General Location Services Timers.
•
General Location Services Database Elements.
•
Lb Interface MTP Layer 2 Timers.
•
Lb Interface MTP Layer 3 Timers.
•
Lb Interface MTP Layer 3 Elements.
•
Lb Interface Call Processing (CP) Timers.
•
Lb Interface Call Processing (CP) Elements.
Table 2-18 details these Location Services parameters. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
Table 2-18
Location Services parameters
OMC-R GUI field name/BSS parameter name
Description
General Location Services Timers: LCS Perform Location Timer (ms) lcs_perf_location
Displayed in the LCS grouping in the BSS Detailed View form. Guards the receipt of a BSSMAP-LE perform Location Response from a BSS-based SMLC. Valid values: 0 - 1,000,000 ms. Default is 300,000 ms.
LCS Supervision Timer (ms) lcs_supervision
Displayed in the LCS grouping in the BSS Detailed View form. Supervises the overall operation of a location request. Valid values: 0 - 1,000,000 ms. Default is 30,000 ms. The value of this parameter should be less than the value of the LCS Perform Location timer.
LCS Segmentation Timer (ms) lcs_segmentation
Displayed in the LCS grouping in the BSS Detailed View form. Supervises an LCS segmentation operation. Valid values: 0 1,000,000 ms. Default is 10,000 ms. The value of this parameter should be less than the value of the LCS Supervision timer. Continued
68P02901W17-S
2-103 Dec 2009
Location services parameters
Table 2-18
Chapter 2: Configuring BSS Features
Location Services parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
General Location Services Database Elements: LCS Mode lcs_mode
Displayed in the LCS grouping of the BSS Detailed View. Specifies the LCS mode of the BSS. Valid values: 0 - LCS disabled, SMLC not supported. 1 - LCS enabled, BSC supports a NSS-based SMLC.2 - LCS enabled, BSC supports a BSS-based SMLC. Can only be modified in SYSGEN mode. If LCS is enabled and early_classmark_sending is not enabled across the A-interface and the Air-interface, an error message is displayed. If LCS is enabled and phase2_classmark_allowed is not configured to support multiband, an error message is displayed. If LCS is disabled and one or more LMTL devices are equipped, an error message is displayed.
Displayed in the LCS grouping in the BSS Detailed View form. The alignment ready timer (ITU Q.703) associated with the Lb interface. The valid values are dependent on the value of the ss7_mode parameter. If ss7_mode is 0, values are 40,000 - 50,000 ms. Default is 50,000 ms. If ss7_mode is 1, values are 13,000 - 30,000 ms. Default is 13,000 ms. This parameter is automatically changed to the appropriate default value if the value of ss7_mode is changed.
Displayed in the LCS grouping in the BSS Detailed View form. The not aligned timer (ITU Q.703) associated with the Lb interface. The valid values are dependent on the value of the ss7_mode parameter. If ss7_mode is 0, values are 5,000 - 150,000 ms. Default is 25,000 ms. If ss7_mode is 1, values are 5,000 - 30,000 ms. Default is 23,000 ms. This parameter is automatically changed to the appropriate default value if the value of ss7_mode is changed.
Lb Interface MTP Layer 2 T3 timer (ms) lb_int_ss7_l2_t3
Displayed in the LCS grouping in the BSS Detailed View form. The aligned timer (ITU Q.703) associated with the Lb interface. The valid values are dependent on the value of the ss7_mode parameter. If ss7_mode is 0, values are 1,000 - 1,500 ms. Default is 1,400 ms. If ss7_mode is 1, values are 5,000 - 14,000 ms. Default is 11,500 ms. This parameter is automatically changed to the appropriate default value if the value of ss7_mode is changed. Continued
2-104
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displayed in the LCS grouping in the BSS Detailed View form. The emergency proving period timer (ITU Q.703) associated with the Lb interface. Valid values: 400 - 600 ms. Default is 600 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The sending SIB timer (ITU Q.703) associated with the Lb interface. Valid values: 80 - 120 ms. Default is 100 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The remote congestion timer (ITU Q.703) associated with the Lb interface. The valid values are dependent on the value of the ss7_mode parameter. If ss7_mode is 0, values are 3,000 - 6,000 ms. Default is 5000 ms. If ss7_mode is 1, values are 1,000 - 6,000 ms. Default is 5,000 ms. This parameter is automatically changed to the appropriate default value if the value of ss7_mode is changed.
Displayed in the LCS grouping in the BSS Detailed View form. The excessive delay of acknowledgment timer (ITU Q.703) associated with the Lb interface. Valid values: 500 - 2,000 ms. Default is 1,000 ms.
Lb Interface MTP Layer 3 Timers:
Displayed in the LCS grouping in the BSS Detailed View form. The delay to avoid mis-sequencing on changeover timer (ITU Q.704) associated with the Lb interface. Valid values: 500 - 1,200 ms. Default is 850 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The waiting for changeover acknowledgment timer (ITU Q.704) associated with the Lb interface. Valid values: 700 - 2,000 ms. Default is 1,400 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The waiting for changeback acknowledgment (first attempt) timer (ITU Q.704) associated with the Lb interface. Valid values: 500 - 1,20 ms. Default is 850 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The waiting for changeback acknowledgment (second attempt) timer (ITU Q.704) associated with the Lb interface. Valid values: 500 - 1,200 ms. Default is 850 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The waiting for uninhibit acknowledgment timer (ITU Q.704) associated with the Lb interface. Valid values: 800 - 1,500 ms. Default is 1,150 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The waiting for force uninhibit timer (ITU Q.704) associated with the Lb interface. Valid values: 800 - 1,500 ms. Default is 1,150 ms. Continued
Displayed in the LCS grouping in the BSS Detailed View form. The waiting for inhibition acknowledgment timer (ITU Q.704) associated with the Lb interface. Valid values: 2,000 - 3,000 ms. Default is 2,500 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The delay to avoid oscillation of initial alignment failure and link restart timer (ITU Q.704) associated with the Lb interface. Valid values: 800 - 1,500 ms. Default is 1,150 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The local inhibit test timer (ITU Q.704) associated with the Lb interface. The valid values are dependent on the value of the ss7_mode parameter. If ss7_mode is 0, values are 180,000 - 360,000 ms. Default is 270,000 ms. If ss7_mode is 1, values are 90,000 - 120,000 ms. Default is 90,000 ms. This parameter is automatically changed to the appropriate default value if the value of ss7_mode is changed.
Displayed in the LCS grouping in the BSS Detailed View form. The remote inhibit test timer (ITU Q.704) associated with the Lb interface. The valid values are dependent on the value of the ss7_mode parameter. If ss7_mode is 0, values are 180,000 - 360,000 ms. Default is 270000 ms. If ss7_mode is 1, values are 90,000 - 120,000 ms. Default is 90,000 ms. This parameter is automatically changed to the appropriate default value if the value of ss7_mode is changed.
Lb Interface SS7 Link Test T1 timer (ms) lb_int_ss7_slt_t1
Displayed in the LCS grouping in the BSS Detailed View form. The supervision timer for signaling link test acknowledgment message timer (ITU Q.707) associated with the Lb interface. Valid values: 4,000 - 12,000 ms. Default is 8,000 ms.
Displayed in the LCS grouping in the BSS Detailed View form. Specifies if the calling party address is to be included in the SCCP message Connect Request messages that travel over the Lb interface. Valid values: 0 or 1. Default is 0. 0 - not included. 1 - included.
Lb Interface Destination Point Code (DPC) lb_int_dpc
Displayed in the LCS grouping in the BSS Detailed View form. The point code of a BSS-based SMLC. The valid values are dependent on the value of the ss7_mode parameter. If ss7_mode is 0, values are 0 - 16383 ms. No default. If ss7_mode is 1, values are 0 - 16,777,215. No default. For a live system, lb_int_dpc should not be the same as the opc. Continued
2-106
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-18
Location services parameters
Location Services parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Lb Int PC Included Called Party Flag lb_int_called_pci
Displayed in the LCS grouping in the BSS Detailed View form. Specifies if the point code is included in the called party address in the SCCP messages that travel over the Lb interface. Valid values: 0 or 1. The default is None. 0 - point code not included. 1 - point code is included.
Lb Int PC Included Calling Party Flag lb_int_calling_pci (OMC-R parameter name: lb_calling_pci)
Displayed in the LCS grouping in the BSS Detailed View form. Specifies if the point code is included in the calling party address in the SCCP messages that travel over the Lb interface. Valid values: 0 or 1. The default is None. 0 - point code not included. 1 - point code is included.
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 - 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 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 - 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 1,000,000 ms. Default is 30,000 ms.
Continued
68P02901W17-S
2-107 Dec 2009
Location services parameters
Table 2-18
Chapter 2: Configuring BSS Features
Location Services parameters (Continued)
OMC-R GUI field name/BSS parameter name Lb Interface SCCP TIAR Timer (ms) lb_int_sccp_tiar
Description Displayed in the LCS grouping in the BSS Detailed View form. The receive inactivity control timer (GSM 8.08-3.23: all BSSMAP timers, TIAR) for the Lb interface. Valid values: 0 1,000,000 ms. Default is 30,000 ms. The value of this parameter should be: •
Displayed in the LCS grouping in the BSS Detailed View form. The wait for SCCP release complete timer for the LB interface. Valid values: 4000 - 15,000 ms. Default is 10,000 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The wait for SCCP released message from BSS-based SMLC timer. Valid values: 0 - 1,000,000 ms. Default is 30,000 ms.
Displayed in the LCS grouping in the BSS Detailed View form. The send activity control timer (GSM 8.08-3.23: all BSSMAP timers, TIAS) for the Lb interface. Valid values: 0 - 1,000,000 ms. Default is 30,000 ms. The value of this parameter should be less than the lb_int_sccp_tiar parameter.
Lb Interface SPI Timer (ms) lb_int_spi
Displayed in the LCS grouping in the BSS Detailed View form. Specifies the amount of time the BSS shall wait before initiating an internal reset after either Subsystem Prohibited (SSP) or SPI has occurred over the Lb interface. Valid values: 10,000 1,000,000 ms. Default is 60,000 ms.
Lb Subsystem Status Test Timer (ms) lb_int_t_stat_info (OMC-R parameter name: lb_t_stat_info)
Displayed in the LCS grouping in the BSS Detailed View form. Specifies the amount of time between sending Subsystem Status Test (SST) messages to the BSS-based SMLC. Valid values: 0 1,000,000 ms. Default is 90,000 ms.
Displayed in the LCS grouping in the BSS Detailed View form. Specifies the number of times the global reset procedure on the Lb interface is allowed to repeat before an alarm is generated. Valid values: 0 - 255. Default is 0.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Restrictions for Location Services parameters
Restrictions for Location Services parameters •
If Location Services mode (LSC_mode) is enabled and a user attempts to change the early_classmark_sending parameter to a value which does not support early classmark sending on both the A-interface and the Air-interface, the command shall be rejected and an error message shall be displayed.
•
If Location Services mode is enabled and a user attempts to change the phase2_classmark_allowed parameter to a value which does not support multiband, the command is rejected and an error message is displayed.
•
If a user changes the opc parameter to the same value as the Lb Interface DPC, a warning message is displayed indicating the effects of the modification.
•
If a user attempts to change the ss7_mode parameter to a value which would cause the Lb Interface DPC to be out of range, the command is rejected and an error message is displayed.
Methods for configuring Location Services The Location Services feature can be configured using: •
OMC-R GUI, using the LCS grouping parameters in the BSS Detailed View and the fields detailed in Table 2-18.
•
TTY interface, see Configuring Location Services using the TTY interface.
Configuring GSM Location Services using the TTY interface Using chg_ and disp_element to change Location Services parameters and timers The chg_element and disp_element commands can be used to configure and change the Location Services-related parameters shown in Table 2-18. Some examples are also given in the following sections. The chg_element and disp_element commands are only accepted at certain locations. Table 2-19 shows the accepted locations.
Table 2-19
chg_element and disp_element accepted locations
Command
BTS
BSC
RXCDR
chg_element disp_element See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS commands, prompts, and parameters.
68P02901W17-S
2-109 Dec 2009
Configuring GSM Location Services using the TTY interface
Chapter 2: Configuring BSS Features
Displaying the current BSS Location Services mode Use the disp_element command to display the Location Services mode of the BSS. For example, the following command displays the current Location Services mode. disp_element lcs_mode bsc The system replies, for example: lcs_mode = 1
Setting the BSS Location Services mode In SYSGEN mode, use the chg_element command to change the Location Services mode of the BSS. For example, the following command changes the Location Services mode to 1 (Location Services enabled, BSC supports a NSS-based SMLC): chg_element lcs_mode 1 bsc
Displaying and changing lcs_perf_location timer To display and change the Location Services perform location timer, use the disp_element and chg_element, respectively. For example, the following command displays the current setting: disp_element lcs_perf_location bsc The system replies, for example: lcs_perform_location = 50000 The following command changes the value of lcs_perf_location to 60,000 ms: chg_element lcs_perf_location 60000 bsc
2-110
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Enhanced GPRS One Phase Access
Enhanced GPRS One Phase Access ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of Enhanced GPRS One Phase Access In a GPRS network there are two packet access procedures a mobile station (MS) can use to establish an uplink Temporary Block Flow (TBF). The packet access can be done in either one phase or two phases. Until now the GPRS architecture only supported the two-phase access process. The Enhanced GPRS One Phase Access feature provides the one phase access, and also provides improvements to both procedures. To summarize, the Enhanced GPRS One Phase Access feature provides: •
The one phase uplink TBF access procedure, also see GPRS Interleaving TBFs on page 2-87.
•
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.
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).
Displayed in the Optional Features grouping of the BSS Detailed View form. Indicates whether the Enhanced GPRS One Phase Access feature is restricted (disabled) or unrestricted (enabled) in the BSS software. This parameter cannot be modified by a user. The field is grayed-out in the OMC-R GUI if the GPRS feature is restricted (disabled).
0 or 1, where: Disabled (0). Enabled (1). Default is Disabled (0).
Enhanced One Phase Access eop_enabled
Displayed in the GPRS grouping of the BSS Detailed View form. Indicates whether Enhanced GPRS One Phase Access feature is enabled or disabled for the BSS. This parameter can be modified by a user. The field is grayed-out in the OMC-R GUI if the Enhanced GPRS One Phase Access Feature (eopOpt) and GPRS feature are restricted (disabled). The QoS feature (see Quality of Service (QoS) on page 2-157) modifies the behavior of this parameter. If bssgp_pfc_bit is set to On (1), any modification to eop_enabled is overridden. If eop_enabled is modified and saved while QoS is enabled and bssgp_pfc_bit is set to on (1), the following message is displayed: WARNING: Changes to eop_enabled are overridden while QoS is enabled.
0 or 1, where: Disabled (0). Enabled (1). Default is Disabled (0).
Displayed in the GPRS grouping of the CELL Detailed View form. The maximum number of non-BCCH timeslots allowed to be in preload USF (Uplink State Flag) active state in the cell at the same time. (That is, the number of non-BCCH timeslots that are broadcast continuously at full power even when no mobile is active on the timeslot.) Can only be modified, if the GPRS Feature (gprsOpt) and Enhanced GPRS One Phase feature are unrestricted (Enabled) in the BSS Detailed View and GPRS Enabled (gprs_enabled) is Yes (1) in the CELL Detailed View. Otherwise, the field is grayed-out in the CELL Detailed View form.
0 - 3. If not set by a user at cell creation time, defaults to 1 timeslot.
CELL parameters: Number of TS In Pre-load USF Active State ts_in_usf_active
2-112
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Methods of configuring Enhanced GPRS one phase access
Methods of configuring Enhanced GPRS one phase access Enhanced GPRS one phase access can be configured using: •
OMC-R GUI BSS and CELL Detail Views and the fields shown in Table 2-20.
•
TTY interface, see Configuring Enhanced GPRS one phase access using the TTY interface.
Configuring Enhanced GPRS one phase access using the TTY interface Checking if Enhanced GPRS one phase access is unrestricted To check if the Enhanced GPRS one phase access feature is unrestricted (enabled) using the TTY interface, enter the following command: disp_options If Enhanced GPRS one phase access is unrestricted, the following is displayed: 44 Enhanced One Phase Access
Displaying and modifying Enhanced GPRS one phase access parameters The disp_element, disp_cell, chg_element and chg_cell_element commands can be used to display and configure the Enhanced GPRS one phase access BSS and cell parameters shown in Table 2-20. Some examples are also given in the following sections. See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS commands, prompts, and parameters.
Displaying whether Enhanced GPRS One Phase Access is enabled at a BSS Use the disp_element command to display whether Enhanced GPRS One Phase Access is enabled for a BSS. For example, the following command displays the current setting of eop_enabled: disp_element eop_enabled 0 The system replies, for example: eop_enabled = 1
68P02901W17-S
2-113 Dec 2009
Configuring Enhanced GPRS one phase access using the TTY interface
Chapter 2: Configuring BSS Features
Displaying the current setting of ts_in_usf_active Use the disp_element command to display the value of ts_in_usf_active. For example, the following command displays the current value of ts_in_usf_active at site 1: disp_element ts_in_usf_active 1 cell_number = 0010111 The system replies, for example: ts_in_usf_active = 1
Setting BSS and cell parameters for Enhanced GPRS One Phase Access Use the chg_element command to change Enhanced GPRS One Phase Access BSS parameters and chg_cell_element command to change Enhanced GPRS One Phase Access cell parameter. For example, the following command changes eop_enabled to 1: chg_element eop_enabled 1 0 The following command changes ts_in_usf_active to 2 at cell 0010111: chg_cell_element ts_in_usf_active 2 0 0 1 0 1 1 1
2-114
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
PBCCH/PCCCH feature
PBCCH/PCCCH feature ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of PBCCH/PCCCH feature Packet Broadcast Control Channel/Packet Common Control Channel (PBCCH/PCCCH) is the packet data logical channels dedicated to GPRS signaling. When the PBCCH/PCCCH feature is configured for a cell, the MS reads system information on PBCCH and performs packet access activities on PCCCH. Table 2-21 shows the functionality of each packet logical channel on PBCCH/PCCCH.
Table 2-21
PBCCH/PCCCH parameters Packet Transfer Direction
Functionality
Uplink only
Used by MS to initiate uplink transfer for data or signaling information.
Packet Access Grant Channel (PAGCH) (on PCCCH)
Downlink only
Used by BSS to send resource assignment to an MS before packet transfer.
Packet Paging Channel (PPCH) (on PCCCH)
Downlink only
Used by BSS to page an MS for Packet Switched (PS) or Circuit Switched (CS).
Packet Broadcast Control Channel (PBCCH)
Downlink only
Used by BSS to broadcast packet data-specific System Information.
Packet Notification Channel (PNCH)
Downlink only
Not supported.
Packet Logical Channels Packet Random Access Channel (PRACH) (on PCCCH)
If the PBCCH/PCCCH feature is not configured for a cell, GPRS-related information is broadcast on the Broadcast Control Channel (BCCH) and GPRS-accessing signaling is conducted on the Common Control Channel (CCCH) channels. In a lightly loaded GSM/GPRS network, BCCH/CCCH has sufficient signaling capacity for both GSM and GPRS. In a highly loaded GSM/GPRS network, PBCCH/PCCCH provides more signaling capabilities for both the GSM voice and GPRS service. In addition, if PBCCH/PCCCH is enabled, there is reduced internal traffic over the GPRS Signaling Link (GSL) and Radio Signaling Link (RSL) because there are fewer requests, assignments, or paging messages over GSL and RSL. The PBCCH/PCCCH feature also facilitates both MS controlled (C31/C32) and network controlled cell reselection (PSI 3, PSI 3bis and PSI 5) by broadcasting cell reselection parameters to the MS.
68P02901W17-S
2-115 Dec 2009
Prerequisites to configuring PBCCH/PCCCH
Chapter 2: Configuring BSS Features
When the PBCCH/PCCCH feature is enabled, a BSS supports the following messages: •
PSI1.
•
PSI2.
•
PSI3.
•
PSI3bis.
•
PSI3quater.
•
PSI5.
•
PSI8.
PSI3ter, PSI4, PSI6, and PSI7 messages are not supported. PSI13 is supported on PACCH. For a full description of the PBCCH/PCCCH feature, see Technical Description: BSS Implementation (68P02901W36).
Prerequisites to configuring PBCCH/PCCCH Before configuring the PBCCH/PCCCH feature, ensure that the following have been enabled at the BSS: •
PBCCH/PCCCH Feature (pccchOpt).
•
GPRS Feature (gprsOpt).
PBCCH/PCCCH can only be enabled for a cell, if the cell: •
Operates in the normal range. That is, ext_range_cell must set to 0 meaning Extended Range Cell is disabled.
•
BCCH carrier is non-hopping.
If the cell parameter GPRS enabled (gprs_enabled) is set to 1 (Enabled), the cell parameter: PBCCH/PCCCH enabled (pccch_enabled) cannot be modified. To change PBCCH/PCCCH for a GPRS cell, use the following procedure:
Procedure 2-3
2-116
Change PBCCH/PCCCH for a cell
1
Set gprs_enabled to 0 (Disabled).
2
Set pccch_enabled to 1 (Enabled).
3
Set gprs_enabled to 1 (Enabled).
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Determining whether PBCCH/PCCCH is unrestricted at the BSS
Determining whether PBCCH/PCCCH is unrestricted at the BSS PBCCH/PCCCH is an optional feature, which must be unrestricted at the BSS before it can be used.
Using the OMC-R GUI To check if PBCCH/PCCCH feature is unrestricted at the BSS using the OMC-R GUI, display the setting of the PBCCH/PCCCH Feature field (pccchOpt) in the Optional Features grouping in the BSS Detailed View. The values are: •
Disabled (0).
•
Enabled (1).
The default is Disabled (0).
Using the TTY interface To check if PBCCH/PCCCH is unrestricted using the TTY interface, enter the following command: disp_options all If the PBCCH/PCCCH optional feature is unrestricted, and is therefore enabled at the BSS, the system displays the following in the unrestricted list: <51> PBCCH/PCCCH
PBCCH/PCCCH parameters Table 2-22 details the PBCCH/PCCCH parameters. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
Table 2-22
PBCCH/PCCCH parameters
OMC-R GUI field name/BSS parameter name
Description
BSS parameters: PBCCH/PCCCH Feature pccchOpt
Displayed in the Optional Features grouping in the BSS Detailed View. Indicates whether the PBCCH/PCCCH feature is enabled for the BSS. Valid values are 0 or 1, where: •
0 - Disabled.
•
1 - Enabled. Continued
68P02901W17-S
2-117 Dec 2009
PBCCH/PCCCH parameters
Table 2-22
Chapter 2: Configuring BSS Features
PBCCH/PCCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name SGSN Release sgsn_release
Description Displayed in the GPRS grouping in the BSS Detailed View. Specifies the SGSN release version. {27703A} Valid values are 0 - 2 Default is 0 0 - SGSN is compliant with 3GPP release 1998 or older. 1 - SGSN is compliant with 3GPP release 1999 to any version before Release 6. 2 - SGSN is compliant with 3GPP release 6 to newer.
Displayed in the GPRS grouping in the CELL Detailed View. Indicates whether the PBCCH/PCCCH feature is enabled for the cell. Valid values are 0 or 1, where: •
0 - False.
•
1 - True.
when: PBCCH/PCCCH feature is unrestricted. gprs_enabled is 0. BSS has configured the BCCH carrier of a cell as a non-hopping carrier. Cell is a normal range cell. ts_sharing is set to 0 (Disabled) on the same cell site. Number of PCCCH Timeslots bs_pcc_chans
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the number of PCCCH timeslots. Indicates the number of physical channels carrying PCCCHs including the physical channel carrying the PBCCH. Valid value is 1. Default: 1.
Number of Blocks Allocated to PBCCH bs_pbcch_blks
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the number of PBCCH blocks per 52-frame-multiframe. Valid values are 1 - 4. Default: 2.
Number of PAGCH Blocks per Multiframe bs_pag_blks_res
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the number of PAGCH blocks per 52-frame-multiframe. Can only be set to a value of (bs_pbcch_blks + bs_pag_blks_res) within range of 1 - 11. Valid values are 0 - 10. Default: 3.
Number of PRACH Blocks per Multiframe bs_prach_blks
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the number of PRACH blocks per 52-frame-multiframe. Valid values are 1 - 12. Default: 4. When psi1_repeat_period is set to 1, bs_pbcch_blks cannot be set to 1 or 2. Continued
2-118
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-22
PBCCH/PCCCH parameters
PBCCH/PCCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Time Interval for Scheduling PSI Messages psi1_repeat_period (OMC-R parameter name: psi1_repeat_prd)
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the time interval between consecutive PSI 1 messages in 52-multiframes. Valid values are 0 - 16. Default: 5. If in range 1 - 16, the BSS uses the value of psi1_repeat_period to scheduling PSI messages. If psi1_repeat_period is 0, the BSS algorithmically determines the value of psi1_repeat_period based upon the value of bs_pbcch_blks and the number of PSI instances in low repetition rate group. When psi1_repeat_period is set to 1, bs_pbcch_blks cannot be set to 1 or 2.
Non-DRX Mode Transfer Period Duration pccch_drx_timer_max (OMC-R parameter name: pccch_drx_max_t)
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the duration of the transfer non-DRX mode period on PCCCH. This field is the binary representation of the parameter DRX_TIMER_MAX. Valid values are 0 - 7, where: •
0 = 0 seconds.
•
1 = 1 second.
•
2 = 2 seconds.
•
3 = 4 seconds.
•
4 = 8 seconds.
•
5 = 16 seconds.
•
6 = 32 seconds.
•
7 = 64 seconds. Continued
68P02901W17-S
2-119 Dec 2009
PBCCH/PCCCH parameters
Table 2-22
Chapter 2: Configuring BSS Features
PBCCH/PCCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name Slots Between Channel Request prach_s
Persistence Level 1 to 4 persistence_lvl_0 persistence_lvl_1 persistence_lvl_2 persistence_lvl_3
Description Displayed in the GPRS grouping in the CELL Detailed View. Specifies the minimum number of frames between two successive Packet Channel Request messages. Valid values are 0 - 9, where: •
0 - S = 12.
•
1 - S = 15.
•
2 - S = 20.
•
3 - S = 30.
•
4- S = 41.
•
5 - S = 55.
•
6 - S = 76.
•
7 - S = 109.
•
8 - S = 163.
•
9 - S = 217.
Displayed in the GPRS grouping in the CELL Detailed View. Specify the values of the access persistence level P(i) for each priority i (i = 1 to 4), where radio priority 1 represents the highest radio priority. Valid values are 0 - 15, where: •
0 - persistence level 0.
•
1 - persistence level 1.
•
2 - persistence level 2.
•
...
•
14 - persistence level 14.
•
15 - persistence level 16. Continued
2-120
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-22
PBCCH/PCCCH parameters
PBCCH/PCCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name Retransmissions Allowed for Radio Priority 1 to 4 prach_mx_retran_0 prach_mx_retran_1 prach_mx_retran_2 prach_mx_retran_3
Slots to Spread Random Access Transmission prach_tx_int
Description Displayed in the GPRS grouping in the CELL Detailed View. Specifies the maximum number of retransmissions allowed for each radio priority i, where radio priority 1 represents the highest radio priority. Valid values are 0 - 3, where: •
0 - 1 retransmission allowed.
•
1 - 2 retransmissions allowed.
•
2 - 4 retransmissions allowed.
•
3 - 7 retransmissions allowed.
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the number of frames to spread transmission of the random access. Valid values are 0 - 15, where: •
0 - two slots used to spread transmission.
•
1 - three slots used to spread transmission.
•
2 - four slots used to spread transmission.
•
...
•
8 - 10 slots used to spread transmission.
•
9 -12 slots used to spread transmission.
•
10 - 14 slots used to spread transmission.
•
11 - 16 slots used to spread transmission.
•
12 - 20 slots used to spread transmission.
•
13 - 25 slots used to spread transmission.
•
14 - 32 slots used to spread transmission.
•
15 - 50 slots used to spread transmission.
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the minimum received signal level at the MS required to access the system. Valid values are 0 - 63 (representing -110 dB to -47 dB). Default: 0. Continued
68P02901W17-S
2-121 Dec 2009
PBCCH/PCCCH parameters
Table 2-22
Chapter 2: Configuring BSS Features
PBCCH/PCCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name GPRS MS Max Transmit Power gprs_ms_txpwr_max_cch (OMC-R parameter name: gprs_mx_txpwr_cch)
Description Displayed in the GPRS grouping in the CELL Detailed View. Specifies the maximum power level an MS may use when accessing the system. Valid values are 0 - 31. The valid range depends on the value of frequency_type, that is, whether a cell is PGSM and EGSM, DCS1800, or PCS 1900. Defaults: •
22 for PGSM and EGSM.
•
0 for DCS1800.
•
30 for PCS1900.
HCS Priority Class priority_class
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the Hierarchical Cell Structures (HCS) priority class. Valid values are 0 - 7. Default: 0 (Lowest Priority).
HCS Signal Strength hcs_thr
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the HCS signal strength threshold. Each step is + 2 dBm. Valid values are 0 - 31, where: •
0 means -110 dBm.
•
1 means -108 dBm.
•
...
•
31 means -48 dBm.
GPRS Cell Reselect Displayed in the GPRS grouping in the CELL Detailed View. Hysteresis Specifies the additional hysteresis that applies in ready state gprs_cell_reselect_hysteresis for cells in the same Routing Area (RA). (OMC-R parameter name: Valid values are 0 - 7, where: gprs_reselect_hys) • 0 = 0 dB.
C32 Exception Rule c32_qual
•
1 = 2 dB.
•
2 = 4 dB.
•
...
•
7 = 14 dB.
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the exception rule for gprs_reselect_offset. Valid values are 0 or 1, where: •
0 - Exception not allowed.
•
1 - Exception allowed. Continued
2-122
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-22
PBCCH/PCCCH parameters
PBCCH/PCCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name C31 Hysteresis c31_hyst
Routing Area Reselect Hysteresis ra_reselect_hysteresis (OMC-R parameter name: ra_reselect_hyst)
Description Displayed in the GPRS grouping in the CELL Detailed View. Specifies if hysteresis is applied to C31. Valid values are 0 or 1, where: •
0 - Hysteresis is not applied to C31.
•
1 - Hysteresis is applied to C31.
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the additional hysteresis that applies when selecting a cell in a new routing area. Valid values are 0 - 7, where: •
0 = 0 dB.
•
1 = 2 dB.
•
2 = 4 dB.
•
...
•
7 = 14 dB.
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the negative offset to C32 that the MS uses for duration of gprs_penalty_time. Valid values are 0 - 7, where: •
0 = 0 dB.
•
1 = 10 dB.
•
2 = 20 dB.
•
3 = 30 dB.
•
...
•
6 = 60 dB.
•
7 = infinity.
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the length of time for which gprs_temporary_offset is active. One step equals 10 seconds. Valid values are 0 31, where: •
0 = 10 seconds.
•
1 = 20 seconds.
•
...
•
31 = 320 seconds. Continued
68P02901W17-S
2-123 Dec 2009
PBCCH/PCCCH parameters
Table 2-22
Chapter 2: Configuring BSS Features
PBCCH/PCCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name GPRS Cell Reselect Offset gprs_reselect_offset (OMC-R parameter name: gprsReselectOffs)
3G Cell Threshold for Multi-RAT MS qsearch_p
Description Displayed in the GPRS grouping in the CELL Detailed View. Specifies the negative or positive offset and a hysteresis to the GPRS cell reselection criteria. Valid values are 0 - 31, where: •
0 = -52 dB.
•
1 = -48 dB.
•
...
•
10 = -12 dB.
•
11 = -10 dB.
•
...
•
22 = +12 dB.
•
23 = +16 dB.
•
...
•
31 = +48 dB.
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the threshold for a multi-RAT MS to search for 3G cells. Valid values are 0 - 15, where: •
Search for 3G cells if the signal level is below a threshold of: 0 : -98 dBm. 1 : -94 dBm. 2 : -90 dBm. 3 : -86 dBm. 4 : -82 dBm. 5 : -78 dBm. 6 : -74 dBm. 7 : Infinity, always search for 3G cells.
•
Search for 3G cells if the signal level is above a threshold of: 8 : -78 dBm. 9 : -74 dBm. 10 : -70 dBm. 11 : -66 dBm. 12 : -62 dBm. 13 : -58 dBm. 14 : -54 dBm 15 : Infinity, never search for 3G cells. Continued
2-124
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-22
Methods for configuring PBCCH/PCCCH
PBCCH/PCCCH parameters (Continued)
OMC-R GUI field name/BSS parameter name Allow Search for 3G Cells search_prio_3g
FDD Cell Reselection Offset fdd_gprs_qoffset
Description Displayed in the GPRS grouping in the CELL Detailed View. Indicates whether 3G cells are searched when BSIC decoding is required. Valid values are 0 or 1, where: •
0 - False (not searched).
•
1 - True (searched).
Displayed in the GPRS grouping in the CELL Detailed View. Specifies the offset to RLA_P for cell reselection to access technology/mode FDD. Valid values are 0 - 15, where: •
0 = - infinity (always select a cell if acceptable).
•
1 = -28 dB.
•
2 = -24 dB.
•
3 = -20 dB.
•
...
•
8 = 0 dB.
•
9 = 4 dB.
•
...
•
15 = 28 dB.
Methods for configuring PBCCH/PCCCH The PBCCH/PCCCH feature can be configured using: •
OMC-R GUI, using the BSS Detailed View (Optional Features and GPRS groupings), and CELL Detailed View (GPRS grouping), and the fields detailed in Table 2-22.
•
TTY interface, see Configuring PBCCH/PCCCH using TTY interface.
68P02901W17-S
2-125 Dec 2009
Configuring PBCCH/PCCCH using TTY interface
Chapter 2: Configuring BSS Features
Configuring PBCCH/PCCCH using TTY interface Using chg_ and disp_element commands The chg_element and disp_element commands can be used to configure and change the PBCCH/PCCCH parameters shown in Table 2-22. Some examples are also given in the following sections. See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS commands, prompts, and parameters. For example, use the following disp_element command to display the current setting of the parameter: GPRS Network Operation Mode (gprs_network_operation_mode): disp_element gprs_network_operation_mode 0 The system replies, for example: gprs_network_operation_mode = 3 To change the setting of gprs_network_operation_mode to 1, use the following command: chg_element gprs_network_operation_mode 1 0
Enabling PBCCH/PCCCH at a cell Use the chg_element command to change the cell parameter: PBCCH/PCCCH enabled. For example, the following command enables the PBCCH/PCCCH feature at cell 0010111: chg_element pccch_enabled 1 1 cell_number = 0 0 1 0 1 1 1 The following example illustrates the system response if an attempt is made to modify pccch_enabled when gprs_enabled is 1 (enabled): chg_element pccch_enabled 1 1 cell_number = 0 0 1 0 1 1 1 ERROR: gprs_enabled must be disabled before pccch can be enabled. COMMAND REJECTED
Changing the time interval for scheduling PSI messages Use the chg_element command to change the Time Interval for Scheduling PSI Messages (psi1_repeat_period) parameter. For example, the following command changes the time interval for scheduling PSI messages to 1 at the cell 0010111 when bs_pbcch_blks is set to 3 or 4: chg_element psi1_repeat_period 1 1 cell_number = 0 0 1 0 1 1 1 COMMAND ACCEPTED.
2-126
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Adaptive Multi-Rate (AMR)
Adaptive Multi-Rate (AMR) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of the AMR feature AMR Full Rate (FR) channel mode The AMR feature improves overall speech quality. Unlike existing GSM speech Codec (FR and EFR), which operate at a fixed rate and constant error protection level, the AMR speech Codec includes a set of fixed rate speech Codec modes for full rate operation with the possibility to switch between the different channel coding modes as a function of the propagation error conditions. Each Codec mode provides a different level of error protection through a dedicated distribution of the available gross bit rate between source coding and channel coding. The actual speech rate used for each speech frame depends on the existing radio channel and traffic conditions. Table 2-23 shows the Full Rate and Half Rate Codec modes. In Table 2-23, a high the bit rate mode means high speech rate but low error correction rate.
Table 2-23
Active Codec set modes
Codec mode value
Meaning (kbit/s)
Available at Full Rate (FR)
Available at Half Rate (HR)
0
12.20
YES
NO
1
10.20
YES
NO
2
7.95
NO
YES
3
7.4
YES
YES
4
6.7
YES
YES
5
5.9
NO
YES
6
5.15
YES
YES
7
4.75
NO
NO
AMR Half Rate (HR) channel mode AMR Half Rate (HR) for speech feature provides enhanced capacity over the air interface and speech quality by means of Codec mode adaptation. AMR selects the optimum channel (HR or FR) and Codec to deliver the best combination of speech quality and system capacity. AMR Half Rate offers capacity increase over the air interface relative to FR or EFR by pairing half rate channels together within one air timeslot. AMR Half Rate (HR) channel mode allows two AMR calls to be placed on a single air interface timeslot. This increases cell capacity without the need for extra radio hardware. When AMR Half Rate is enabled, the BCCH and SDCCH channels in any cell operate identically for Full Rate and Half Rate, however, the requirement for SDCCHs may increase. The dual rate channel allocation algorithm pairs a half rate speech with another half rate channel. This algorithm can be manually controlled or automatically controlled by a predefined traffic threshold.
68P02901W17-S
2-127 Dec 2009
Link Adaptation
Chapter 2: Configuring BSS Features
AMR Half Rate and GSM Half Rate The GSM Half Rate feature builds on the AMR Half Rate feature. It 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-138.
AMR hardware and software utilization The AMR feature is only available on the following radio platforms: •
CTU.
•
CTU2.
•
TCU-A.
•
TCU-B.
The BSC and RXCDR software supports 8 kbit/s switching so that half-rate enabled RTFs are provisioned on only two E1 timeslots between the BSC and BTS, that is, 8 kbit/s backhaul is utilized. However, 7.95 capable RTFs are provisioned on an additional two E1 timeslots between the BSC and BTS, because 7.95 kbit/s mode only fits in 16 kbit/s TRAU frame format between the BSC and BTS. The GPD2 boards are used to double the transcoding capability. Each GDP2 board can handle up to 60 channels. The backhaul saving is achieved by replacing KSWs with DSWs in the BSC and RXCDR.
Link Adaptation Full Rate Link Adaptation When Full Rate Link Adaptation is used in conjunction with AMR, speech quality in poor RF environments is improved by adapting the speech rates and level of error correction on a call. For example, in a poor RF environment speech quality is reduced by reducing the speech rate and increasing the level of error correction. Full Rate AMR Link Adaptation enables the BSS to adapt the speech Codec modes in an AMR codec set on the uplink and downlink of an AMR FR call to provide the most suitable level of error correction for the RF environment. Uplink and Downlink Codec modes are considered separately and can be adapted separately. With Full Rate Link Adaptation up to four Codec modes can be included in the Full Rate Active Codec Set for a cell. A call is then adapted over this Active Codec Set according to the quality of the link between the mobile and the BSS. The Full Rate Codec modes supported are shown in Table 2-23.
2-128
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
AMR Full Rate - MS Monitor function
Half Rate Link Adaptation Half Rate AMR Link Adaptation provides similar functionality to the Full Rate AMR Link Adaptation, but for the Half Rate AMR channel. In Half Rate AMR Link Adaptation there is a different Half Rate Active Codec Set, which can contain up to four of the Half Rate Codec modes supported in the Hardware Capable Codec Set for the CTU/TCU-B/TCU-A platforms. The Half Rate Codec modes supported in the Hardware Capable Codec Set for the CTU/TCU-B/TCU-A radios are shown in Table 2-23. There is also a different Half Rate Initial Codec Mode and different uplink and downlink Codec mode thresholds and hysteresis values for Half Rate AMR calls. 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).
68P02901W17-S
2-129 Dec 2009
Prerequisites for enabling AMR
Chapter 2: Configuring BSS Features
Prerequisites for enabling AMR AMR can only be enabled for a BSS, if its Assoc_RXCDR has CIC Validation (cic_validation) enabled. If a site contains Horizonmacro and/or M-Cell2/6 type cabinets, including Horizonmacro Extension cabinets, the site is AMR capable. The AMR associated Cell and RTF parameters can only be modified if the container site is AMR capable, and the AMR feature (amrOpt) is unrestricted (Enabled) for the NE.
Configuring AMR at a cell AMR is an optional feature for a BSS. If the AMR feature is unrestricted (Enabled) at the BSS, then AMR Full Rate and AMR Half Rate can be enabled or disabled on a BSS and Cell basis. When a cell is created, the following can be defined: •
A set of Active Codec Modes for calls on the carriers of the cell (separate Active Codec Sets can be defined for Full and Half Rate).
•
Initial Codec modes for both Half Rate and Full Rate.
•
Uplink and downlink thresholds for mode adaptation between Codec modes in the Active Codec Set.
These settings can also be modified to fine tune performance as required. Within the Cell, RTFs can then be configured to be Half Rate channel mode capable.
Determining whether the AMR features are unrestricted AMR, AMR Enhanced GDP, AMR Enhanced Capacity, AMR TCU-A, and AMR TCU-B are optional features, which must be unrestricted before they can be used.
Using the OMC-R GUI To check if AMR, AMR Enhanced GDP, AMR Enhanced Capacity, AMR TCU-A, and AMR TCU-B features are unrestricted using the OMC-R GUI, display the settings of the following fields in the Optional Features grouping in the BSS Detailed View:
2-130
•
AMR Feature (amrOpt).
•
AMR Enhanced GDP Feature (amrEGDPProOpt).
•
AMR Enhanced Capacity Feature (amrEnhancedCapOpt).
•
AMR TCU-A Feature (amrTCUAOpt).
•
AMR TCU-B Feature (amrTCUBOpt).
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
AMR parameters
The values for these fields are: •
Disabled (0) - meaning the feature is restricted.
•
Enabled (1) - meaning the feature is unrestricted.
The default for these fields is Disabled (0), and cannot be changed by a user.
Using the TTY interface To check if AMR features are unrestricted using the TTY interface, enter the following command: disp_options all If an AMR feature is unrestricted, the system displays it in the Unrestricted list. For example, if all the AMR features are unrestricted, the following would be included in the unrestricted list: 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
Details
AMR BSS parameters: amrOpt
Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether the Adaptive Multi-Rate (AMR) feature is restricted (Disabled) or unrestricted (Enabled) for the BSS.
amrEGDPProOpt
Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether the Adaptive Multi-Rate (AMR) using Enhanced GDP feature is restricted (Disabled) or unrestricted (Enabled) for the BSS.
amrEnhancedCapOpt
Displayed in the Optional Features grouping of the BSS and RXCDR Detailed View. Indicates whether the Adaptive Multi-Rate (AMR) Enhanced Capacity feature is restricted (Disabled) or unrestricted (Enabled) for the BSS or RXCDR. If this feature is enabled, the RXCDR supports 4800 CICs and 8 kbit/s switching. Continued
68P02901W17-S
2-131 Dec 2009
AMR parameters
Chapter 2: Configuring BSS Features
Table 2-24
AMR parameters (Continued) Details
BSS parameter name amrTCUAOpt
Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether the Adaptive Multi-Rate (AMR) TCU-A feature is restricted (Disabled) or unrestricted (Enabled) for the BSS. If this feature is enabled, TCU-A support for AMR is provided.
amrTCUBOpt
Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether the Adaptive Multi-Rate (AMR) TCU-B feature is restricted (Disabled) or unrestricted (Enabled) for the BSS. If this feature is enabled, TCU-B support for AMR is provided.
Half Rate AMR BSS parameters: amr_bss_half_rate_enabled force_hr_usage
See BSS Detailed View fields - ( Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping on page 4-35) for details of these parameters.
Full Rate AMR BSS parameters: amr_bss_full_rate
See BSS Detailed View fields - ( Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping on page 4-35) for details of these parameters.
Link Adaptation BSS parameters: amr_dl_thresh_adjust amr_dl_la_mode_chg_min
See BSS Detailed View fields - ( Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping on page 4-35) for details of these parameters.
See BSS Detailed View fields - ( Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping on page 4-35) for details of these parameters.
General AMR Cell parameters: hr_fr_hop_count
See CELL Detailed View fields, General - ( Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping on page 8-31) for further details.
Full Rate AMR Cell parameters: amr_full_rate
See CELL Detailed View fields, General - ( AMR Full Rate grouping on page 8-32) for details. Continued
2-132
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-24
AMR parameters
AMR parameters (Continued) Details
BSS parameter name Half Rate AMR Cell parameters: amr_half_rate_enabled hr_res_ts hr_intracell_ho_allowed inner_hr_usage_thres new_calls_hr reconfig_fr_to_hr
See CELL Detailed View fields, General - grouping ( AMR/GSM Half Rate grouping on page 8-38) for details of these parameters.
Full Rate Active Codec Set (ACS) Cell parameters: See CELL Detailed View fields, General - ( AMR Full amr_fr_acs Rate grouping on page 8-32) for details. 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 Continued
68P02901W17-S
2-133 Dec 2009
AMR parameters
Chapter 2: Configuring BSS Features
Table 2-24
AMR parameters (Continued) Details
BSS parameter name Half Rate Active Codec Set (ACS) Cell parameters:
See CELL Detailed View fields, General - ( AMR/GSM Half Rate grouping on page 8-38) for details.
See Assoc_RXCDR Detailed View fields, Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping () for details.
Methods of configuring AMR AMR can be configured using: •
OMC-R GUI BSS, Cell and RTF Detailed View and the parameters shown in Table 2-24.
•
TTY interface, see Configuring AMR using the TTY interface.
Configuring AMR using the TTY interface The following sections give examples of using the TTY interface to configure AMR. For further details of the commands and parameters shown in these examples, see Technical Description: BSS Command Reference (68P02901W23).
68P02901W17-S
2-135 Dec 2009
Configuring AMR using the TTY interface
Chapter 2: Configuring BSS Features
Displaying AMR cell parameters using the TTY interface To display the current value of an AMR cell parameter use either of the commands disp_element, or disp_cell with the full option. For example, the following command displays the current value of amr_fr_ul_la_enabled for cell 4960114 at site 0: disp_element amr_fr_ul_la_enabled 0 cell 4 9 6 0 1 1 4 amr_fr_ul_la_enabled = 1
Modifying AMR cell parameters using the TTY interface To modify the current value of an AMR cell parameter use the chg_element or chg_cell_element command. For example, the following command enables AMR uplink codec mode adaptation for cell 4960114 at site 1: chg_element amr_fr_ul_la_enabled 1 1 cell 4 9 6 0 1 1 4 The chg_cell_element command prompts for dependant cell parameters when necessary. For example, the AMR RXqual Handover and Power Control parameters are prompted for when changing the value of alt_qual_proc and hopping related parameters are prompted for when changing hop_qual_enabled to 1, for example: chg_cell_ele alt_qual_proc 0 cell 0 0 1 0 1 98 75 chg_cell_ele hop_qual_enabled 1 cell 0 0 1 0 1 98 75
Displaying AMR BSS parameters using the TTY interface To display the current value of an AMR BSS parameter, use the disp_element command. For example, the following command displays the current value of amr_ms_monitor_period for the BSS: disp_element amr_ms_monitor_period 0 amr_ms_monitor_period = 25
Modifying AMR BSS parameters using the TTY interface To modify the current value of an AMR BSS parameter use the chg_element command. For example, the following command changes the MS monitor period to 25 at the BSS: chg_element amr_ms_monitor_period 25 0
Displaying the Active Codec Set To display the Active Codec Set for an AMR cell, use the disp_acs command, and security level 3. For example the following command displays the active codec set for cell 4960111: disp_acs 4 9 6 0 1 1 1 The system then displays the Active Codec Set modes, associated threshold and hysteresis values for the cell.
2-136
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring AMR using the TTY interface
Specifying the Active Codec Set To specify the Active Codec Set for an AMR cell, use the chg_acs_params command, and security level 3. For example the following command sets four Full Rate codec modes in the active codec set for cell 4960111, where previously only one mode was configured: chg_acs_params 0 4 9 6 0 1 1 1 The system then prompts for the Active Codec Set modes, associated threshold and hysteresis values for the cell.
68P02901W17-S
2-137 Dec 2009
GSM Half Rate
Chapter 2: Configuring BSS Features
GSM Half Rate ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The GSM Half Rate feature offers enhanced capability over the air interface, corresponding to the proportion of mobiles within a coverage area that support Half Rate. An air timeslot is split into two sub-channels, each containing a half rate channel. Although speech quality is considered inferior to other speech codecs, the penetration level is high making it a viable option for high density areas. A full technical description of GSM HR can be found in Technical Description: BSS Implementation (68P02901W36).
Prerequisites for enabling GSM HR GSM HR can only be enabled for a BSS if the GSM HR feature (gsmHalfRateOpt) is unrestricted (Enabled) for the NE.
Configuring GSM HR GSM HR is an optional feature for a BSS. If the GSM HR feature is unrestricted (Enabled) at the BSS, then GSM HR can be enabled or disabled on a BSS, Cell or RTF basis.
Interaction with other features This feature interacts with the IMRM feature, see Intelligent Multilayer Resource Management (IMRM) on page 2-148 for further details.
Determining whether the GSM HR feature is unrestricted GSM HR is an optional feature, which must be unrestricted before it can be used.
Using the OMC-R GUI To check if GSM HR is unrestricted (enabled) using the OMC-R GUI, display the setting of the GSM HR feature (gsmHalfRateOpt) in the Optional Features grouping in the BSS Detailed View.
2-138
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
GSM HR parameters
Using the TTY interface To check if the GSM HR feature is unrestricted using the TTY interface, enter the following command: disp_options 22064 If the GSM HR feature is unrestricted, the system displays it in the Unrestricted list as follows: <22064> GSM Half Rate
GSM HR parameters Table 2-25 lists the additional parameters specific to configuring GSM HR.
Table 2-25
GSM HR-specific parameters Details
BSS parameter name GSM HR BSS parameters: gsmHalfRateOpt
Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether the GSM Half Rate (HR) feature is restricted (Disabled) or unrestricted (Enabled) for the BSS.
See BSS Detailed View fields - Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate ( Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping with GSM Half Rate on page 4-37) for details of these parameters.
See CELL Detailed View fields, General AMR/GSM Half Rate grouping ( AMR/GSM Half Rate grouping with GSM Half Rate on page 8-45) for details of these parameters.
2-139 Dec 2009
GPRS Seamless Cell Reselection
Chapter 2: Configuring BSS Features
GPRS Seamless Cell Reselection ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description of GPRS Seamless Cell Reselection (SCR) The GPRS receiver performs cell selection based on the receive level (RxLev) from the neighboring cells due to cell reselection. During cell reselection, when buffered data is still being transferred from the original cell to the target cell, the MS may select yet another cell and the buffered data can be lost. The GPRS Seamless Cell Reselection feature transfers data from the source cell to the target cell to avoid data loss and to minimize the retransmissions at the TCP layer, thus boosting performance. GPRS Seamless Cell Reselection feature ensures completion of the cell change procedure at the RLC/MAC layers in a controlled manner so that the higher layers (specifically TCP) do not notice the effect. For further details of the GPRS Seamless Cell Reselection feature, see Technical Description: BSS Implementation (68P02901W36).
Determining whether GPRS Seamless Cell Reselection (SCR) is unrestricted SCR is an optional feature, which must be unrestricted for a BSS in order for it to be used. The GPRS feature (gprsOpt) must also be unrestricted at the BSS in order for SCR to function.
Using the OMC-R GUI To check if SCR is restricted or unrestricted, using the OMC-R GUI, display the setting of the GPRS Seamless Cell Reselection Feature field (scrOpt) in the Optional Features grouping in the BSS Detailed View. The values for scrOpt are: •
Disabled (0) - data from the source cell to the target cell is discarded.
•
Enabled (1) - data is forwarded from the source cell to the target cell.
•
Default is Disabled (0).
This field cannot be changed by a user.
2-140
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
GPRS Seamless Cell Reselection parameters
Using the TTY interface To check if SCR is restricted or unrestricted using the TTY interface, enter the following command: disp_options all If the SCR optional feature is unrestricted, the system displays the following in the unrestricted list: 54 Seamless Cell Reselection
OMC-R GUI field name/ parameter name GPRS Seamless Cell Reselection Enabled scr_enabled
Description
Attributes
Displayed in the GPRS Seamless Cell Reselection grouping in the BSS Detailed View form. Indicates whether the GPRS Seamless Cell Reselection feature is Enabled (1) or Disabled (0). The default is Disabled (0). Can be modified by a user. Grayed-out if the BSS Detailed View field: GPRS Seamless Cell Reselection Feature (parameter name: scrOpt) is set to Disabled (0).
gprs_cr_margin This attribute specifies the threshold at which the network considers the PMR received from the MS as a “bad” PMR. gprs_num_pmrs This attribute specifies the number of “bad” PMRs the network receives before initiating a network controlled cell reselection.
Methods for configuring SCR The SCR feature can be configured using: •
OMC-R GUI BSS and CELL Detailed Views and the fields shown in Table 2-26.
•
TTY interface, see Configuring SCR using TTY interface.
68P02901W17-S
2-141 Dec 2009
Configuring SCR using TTY interface
Chapter 2: Configuring BSS Features
Configuring SCR using TTY interface See Technical Description: BSS Command Reference (68P02901W23) for full details of BSS commands, prompts, and parameters.
Displaying whether SCR is enabled for a BSS Use the disp_element command to display whether SCR is enabled for a BSS. For example, the following command displays the value of scr_enabled: disp_element scr_enabled bsc The system replies, for example: scr_enabled = 1
Enabling and disabling SCR for a BSS Use the chg_element command to enable or disabled SCR at a BSS. For example, the following command sets scr_enabled to 1 (enabled) at a BSS: chg_element scr_enabled 1 bsc
2-142
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Current Bucket Level (CBL) feature
Current Bucket Level (CBL) feature ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of the Current Bucket Level feature The Current Bucket Level (CBL) feature is essential for the correct working of BSSGP flow control. When the Current Bucket Level (CBL) feature is enabled, a current bucket level (buffer full percentage) is included with every flow control message, to correct the estimation error in the SGSN. The Current Bucket Level feature can be enabled or disabled for each BSS using the Current Bucket Level Feature field (bssgp_cbl_bit) in the BSS Detailed View. For further details of the Current Bucket Level feature, see Technical Description: BSS Implementation (68P02901W36).
Prerequisite for Current Bucket Level feature The GPRS feature (gprsOpt) must be unrestricted at the BSS, before CBL can be enabled.
Current Bucket Level parameters Table 2-27 details the Current Bucket Level parameters.
Table 2-27
Current Bucket Level parameters
OMC-R GUI field name/BSS parameter name Current Bucket Level Feature bssgp_cbl_bit
68P02901W17-S
Description Displayed in the GPRS grouping in the BSS Detailed View form. Indicates whether the Current Bucket Level (CBL) feature is used at the PCU. Values are Disabled (0) or Enabled (1). The default is 0. Grayed-out if the GPRS Feature (gprsOpt) is Disabled (0) at the BSS. The OMC-R displays the following message if the value is changed: WARNING: Changing this element may trigger a negotiation with the SGSN, resulting in the reset of signaling BVCI. CBL feature shall be enabled/disabled subject to this negotiation. Ongoing data transfers will be affected due to signaling reset. Do you wish to continue?
2-143 Dec 2009
Enhanced Scheduling
Chapter 2: Configuring BSS Features
Enhanced Scheduling ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview The Enhanced Scheduling feature provides mechanisms that allow the BSS to dynamically select the most appropriate access method, allowing fast access whilst reducing the load on the signaling links.
Enhanced Scheduling sub-features The Enhanced Scheduling feature comprises the following sub-features: •
Increased PRP Capacity - Increased number of GPRS MSs that can be serviced by each Packet Resource Processor (PRP) (that is, more than 120 MSs) (using the BSS parameters prp_capacity_opt and inc_prp_cap_ena).
•
Dynamic allocation of reserved Packet Resource Request (PRR) blocks for two-phase access (using cell parameter gprs_min_prr_blks and BSS parameter prr_aggr_factor).
•
Provides control for the percentage of RSL bandwidth reserved for circuit switched (CS) traffic (using the cell parameter percent_traf_cs).
•
Advanced UL/DL bias detection to optimize MS throughput (using the BSS parameter gprs_ul_dl_bias and gprs_com_ms_class).
These changes together increase scheduling efficiency leading to a greater amount of GPRS traffic handling capacity in a given cell whilst reducing the impact of the data traffic on circuit switched traffic. For further details of the Enhanced Scheduling, see Technical Description: BSS Implementation (68P02901W36).
Enhanced Scheduling dependencies The Enhanced Scheduling feature requires the GPRS feature (gprsOpt) to be unrestricted (enabled).
Enhanced Scheduling parameters Table 2-28 lists the parameters associated with the Enhanced Scheduling feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
2-144
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displayed in the Optional Features grouping of the BSS Detailed View form. Indicates whether the increased PRP capacity feature is restricted (disabled) or unrestricted (enabled) in the BSS software. This parameter cannot be modified by a user. The field is grayed-out in the OMC-R GUI if the GPRS feature is restricted (disabled).
0 or 1, where: Disabled (0). Enabled (1). Default is Disabled (0).
Displayed in the GPRS grouping of the BSS Detailed View form. Indicates whether increased PRP capacity is enabled (1) or disabled (0). If disabled (0), the concept of short and long GPRS sessions do not apply. This field cannot be set to True (1), if the Increased PRP Capacity Feature (prp_capacity_opt) is Disabled (0).
True (1) or False (0). Default is False (0).
Most Common Multislot of GPRS Mobiles gprs_com_ms_class
Displayed in the GPRS grouping of the BSS Detailed View form. Determines the maximum number of DL timeslots allocated to a mobile for EOP and one-phase access.
1, 2, 4 or 8, where: 1 - multislot class1. 2 - multislot class 2, 3, 5.4 - multislot class 4, 6, 7. 8 - multislot class 8 to 29. Default is 8.
Displayed in the GPRS grouping of the BSS Detailed View form. Represents a coefficient for a linear function to dynamically allocate/deallocate reserved PRR blocks. An aggressiveness factor of 0 means that each cell in the BSS has PRR blocks allocated according to the value of the gprs_min_prr_blks cell parameter. This field has no effect on cells that have pccch_enabled set to 1 (Enabled).
0 - 4. Default is 3.
Continued
68P02901W17-S
2-145 Dec 2009
Methods of configuring enhanced scheduling
Table 2-28
Chapter 2: Configuring BSS Features
Enhanced Scheduling parameters (Continued)
OMC-R GUI field name/BSS parameter name GPRS Uplink or Downlink bias gprs_ul_dl_bias
Description
Values
Displayed in the GPRS grouping of the BSS Detailed View form. {23292} This parameter is applied if the operator wants more UL timeslots to be allocated to mobiles initially with multislot class 6, 10, 11 and 12 as well as any multislot class that maps to class 6, 10, 11 and 12.
UL (0) or DL (1). Default is DL (1).
Displayed in the GPRS grouping of the CELL Detailed View form. Indicates the minimum number of reserved PRR blocks created per cell, when measured over four multiframes. This field has no effect on cells that have pccch_enabled set to 1 (Enabled).
0 - 24. Default is 0.
Displayed in the GPRS grouping of the BTS SITE Detailed View form. Indicates the percentage of RSL traffic reserved for circuit switch (CS) traffic per site. This field can only be modified if GPRS is enabled.
0 - 90. Default is 55.
CELL parameters: Minimal number of dynamic PRR blocks gprs_min_prr_blks
BTS site parameters: Percentage of RSL Reserved for CS percent_traf_cs
Methods of configuring enhanced scheduling Enhanced scheduling can be configured using: •
OMC-R GUI BSS, site and CELL Detail Views and the fields shown in Table 2-28.
•
TTY interface, see Configuring enhanced scheduling using the TTY interface on page 2-146.
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
2-146
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring enhanced scheduling using the TTY interface
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
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
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 set 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 neighboring cells either within the same BSS or different BSSs.
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 optimize resource utilization 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:
2-148
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Benefits of IMRM
•
Imbalance between bands, for example, the DCS1800 is heavily utilized whilst other bands are not.
•
Imbalance between layers, that is, macro overlay running at very high utilization 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-utilization in the macro layer and under-utilization 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 prioritize traffic allocation by both band and layer.
•
Optimizes 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.
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.
68P02901W17-S
2-149 Dec 2009
Description of IMRM feature settings
Chapter 2: Configuring BSS Features
•
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 neighboring 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 affect 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
Default Band weightings for EGSM and non-EGSM enabled systems
EGSM Support
PGSM
EGSM
DCS1800
UMTS
YES
45
10
45
0
NO
50
0
50
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. Unlike existing behavior 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 to 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 is used to define target resources on initial resource allocation and/or handover behavior. See Table 2-32 for further details.
2-150
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Description of IMRM feature settings
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.
NOTE 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
Per-call Preferred Band (PCPB) settings Preferred Band
1
PGSM.
2
EGSM.
3
DCS1800.
4
UMTS.
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 behavior 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 behaviors. Table 2-32 describes the band selection algorithms per band preference mode that are invoked on assignment and handover request.
Table 2-31
Summary of band preference modes and their associated behaviors
Setting
68P02901W17-S
Comment
0
Attempt to handover to strongest reported neighbor.
1
Attempt assignment to strongest preferred band reported neighbor (SDCCH TCH).
2
Attempt handover to strongest preferred band reported neighbor.
3
1 and 2 above.
4
Attempt assignment to strongest preferred band TCH immediately after initial assignment.
5
1 or 4 above.
6
1 or 4 above.
2-151 Dec 2009
Description of IMRM feature settings
Chapter 2: Configuring BSS Features
Correct setting of the band-preference mode is important in optimizing 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 Assignment and Handover band selection algorithms for the band preference modes Setting
Assignment
Handover
0
Outer Zone
Strongest. Inner Zone continual.
1
Local preferred then / or Neighbor preferred then Local non-preferred
Strongest. Inner Zone continual when preferred.
2
Outer Zone preferred then / or Outer Zone non-preferred
Inner Zone continual when preferred. Normal / Congestion to preferred.
3
Local preferred then / or Neighbor preferred then Local non-preferred Outer Zone
Inner Zone continual when preferred. Normal / Congestion to preferred.
4
Outer Zone preferred then / or Outer Zone non-preferred
Inner Zone continual when preferred. Preferred neighbor continual. Normal / Congestion to preferred.
5
Local preferred then / or Neighbor preferred then Local non-preferred Outer Zone
Inner Zone continual when preferred. Preferred neighbor continual. Normal / Congestion to preferred.
6
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 neighborhood. In this case, the difference between BPM 2 and 3, and 4 and 5 is that in the former handover to the preferred band takes 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 neighbor, whether it is in the same cell or not) is attempted immediately after assignment. Motorola currently advises 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.
NOTE 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 signaling, and on how quickly the call is established after the initial TCH assignment.
2-152
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Interaction with other features
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 is 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. Where the IMRM Force Recalculation (imrm_force_recalc) flag is set, the PCPB of that cell is 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 then determines at what point a handover may take place.
NOTE Outer to Inner zone handovers (where the Inner zone is the Preferred band) still take place as soon as the Inner zone qualifies, as per ALM.
Neighbor List Selection For multi-band handover, ensure that the neighbor list length in each band is sensibly matched to the IMRM weightings and band preference mode. The neighbor lists are defined in each cell on a per-band basis. When a call has entered an IMRM enabled cell, it is assigned a PCPB. The combination of the PCPB and the band preference mode determine the MS's handover behavior; when and how it attempts handover, and whether that handover may involve band reassignment. If the ratio of IMRM band weightings varies significantly from the ratio of qualifying neighbors 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 neighbors. This scenario is most likely to be seen in dense urban areas suffering from canyoning, and in gateway regions such as airport terminals 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 have on IMRM and other features.
NOTE For information about the interaction of IMRM with other BSS features, see Intelligent Multilayer Resource Management Field Optimization Guide
(GSM-BSS-22404-FOG-001).
68P02901W17-S
2-153 Dec 2009
Prerequisites to configuring Intelligent Multilayer Resource Management
Chapter 2: Configuring BSS Features
Prerequisites to configuring Intelligent Multilayer Resource Management Before configuring IMRM, ensure that the Multiband Inter-Cell Handover (mbInterCellHoOpt parameter) has been enabled: See Table 4-4, Configuring enhanced SDCCH to TCH band assignment on page 8-196 and Configuring a cell for coincident multiband handovers on page 8-179 for details
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).
Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether IMRM feature is unrestricted (enabled) or restricted (disabled).
0 or 1, where: Disabled (0). Enabled (1).
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-76.
1, 2, 4, 8, or 16.
CELL parameters: Band Preference band_preference
Continued
2-154
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displayed in the CELL Detailed View, General section, Multiband handover grouping. When the IMRM feature (imrmOpt) is enabled, displays whether a recalculation on the preferred band to handover to is executed on the cell. See Use of IMRM Force Recalculation flag on page 2-153 for further details of how to set this parameter.
0 or 1, where: 0 = Disabled. 1 = Enabled. Default is 0.
PGSM Weighting (0–100) imrm_pgsm_weight
Displayed in the CELL Detailed View, General section, Multiband handover grouping. When the IMRM feature (imrmOpt) is enabled, displays the weighting for the PGSM frequency. Only one weighting can be set to 100, otherwise the following error message is displayed: “Cannot set more than one IMRM band weight to the max value.” See Layer weightings on page 2-149 for further details of how to set this parameter.
0 - 100. Default is 0.
IMRM EGSM Weighting (0-100) imrm_egsm_weight
Displayed in the CELL Detailed View, General section, Multiband handover grouping. When the IMRM feature (imrmOpt) is enabled, displays the weighting for the EGSM frequency. Only one weighting can be set to 100, otherwise the following error message is displayed: “Cannot set more than one IMRM band weight to the max value.” See Layer weightings on page 2-149 for further details of how to set this parameter.
IMRM DCS1800 Weighting (0-100) imrm_dcs1800_weight (Field name in OMC-R database table: mrm_dcs18_weight)
Displayed in the CELL Detailed View, General section, Multiband handover grouping. When the IMRM feature (imrmOpt) is enabled, displays the weighting for the DCS1800 frequency. Only one weighting can be set to 100, otherwise the following error message is displayed: “Cannot set more than one IMRM band weight to the max value.” See Layer weightings on page 2-149 for further details of how to set this parameter.
0 - 100. Default is 0.
IMRM UMTS Weighting (0-100) imrm_umts_weight
Displayed in the CELL Detailed View, General section, Multiband handover grouping. When the IMRM feature (imrmOpt) is enabled, displays the weighting for the UMTS frequency. Only one weighting can be set to 100, otherwise the following error message is displayed: “Cannot set more than one IMRM band weight to the max value.” Grayed-out if either the IMRM or 2G3G feature is restricted. See Layer weightings on page 2-149 for further details of how to set this parameter.
0 - 100. Default is 0.
Band Preference Mode band_preference_mode
Displayed in the CELL Detailed View, General section, Multiband Handover grouping. Determines the method used to have a MultiBand MS use the band of preference for a given cell in the BSS. Can only be modified if the MultiBand Inter-Cell Handover feature is unrestricted (enabled). See Use of Band Preference Mode on page 2-151 for recommended settings when used in conjunction with IMRM.
0 - 6. Default is 0.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Quality of Service (QoS)
Quality of Service (QoS) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of QoS In R99 of the 3GPP specifications, Packet Flow Management (PFM) procedures were added to the BSSGP protocol. These procedures provide for aggregation of similar QoS profiles into a single Packet Flow Context and allow the BSS to negotiate and modify QoS parameters. The Aggregate BSS QoS Profile (ABQP) field, contained in PFM signals, describes the QoS characteristics for a single PFC, identified by a Packet Flow Identifier (PFI). The ABQP field contains a full set of QoS parameters: traffic class, Traffic Handling Priority (THP), maximum bit rates and guaranteed bit rates for uplink/downlink, transfer delay, and other fields describing error rate/ratio characteristics are parameters included in the ABQP to provide a more specific differentiation of services to users. With the added parameters contained in the ABQP field, and the ability to negotiate and modify these QoS parameters, the BSS can now provide differentiated services to users in line with the QoS requested by the mobile and consistent to those offered to the mobile by the other network entities, thus providing a more consistent QoS E2E. For a full description of QoS, see Technical Description: BSS Implementation (68P02901W36).
Prerequisites to configuring QoS Before configuring QoS, ensure that the following features have been enabled: •
Network Assisted Cell Change (NACC) (naccOpt parameter). See Network Assisted Cell Change (NACC) on page 2-165 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-S
2-157 Dec 2009
Quality of Service parameters
Table 2-34
Chapter 2: Configuring BSS Features
Quality of Service parameters
OMC-R GUI field name/BSS parameter name
Description
Values
Quality Of Service Feature qosOpt
Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether QoS feature is enabled or disabled.
0 or 1, where: Disabled (0). Enabled (1). If the feature has been purchased the default is Enabled (1), otherwise the default is Disabled (0).
BSS support of PFM on BSSGP (for QoS) bssgp_pfc_bit
Displayed in the Quality of Service grouping in the BSS Detailed View. Specifies whether PFM procedures are enabled. Grayed out if QoS feature is not purchased and NACC feature is not enabled in the BSS. If modified the following warning message is displayed: “WARNING: Changing this element may trigger a negotiation with the SGSN, resulting in the reset of signaling BVCI. QoS feature shall be enabled/disabled subject to this negotiation. Ongoing data transfers will be affected due to signaling reset. Do you wish to modify?”
0 or 1, where: Off (0). On (1). Default is Off (0).
ARP Signaling Selection arp_signal_sele
Displayed in the Quality of Service grouping in the BSS Detailed View. Indicates which ARP signaling selection option is used for R99/R4 mobiles. Grayed out if QoS Feature is not purchased. If bssgp_pfc_bit set to On (1) and arp_signal_sele is modified the following message is displayed: “WARNING: Changing arp_signal_sele when QoS is enabled will only affect new PFCs”.
0, 1, or 2, where: Fixed ARP Value of 3 (0). Map precedence class values to ARP(1, 2, 3) (1), Map Traffic Handling Priority to ARP (2) Default is Map precedence class values to ARP(1, 2, 3) (1).
BSS parameters:
Continued
2-158
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-34
Quality of Service parameters
Quality of Service parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Values
THP Weight of Interactive 2 Class thp_i2_weight
Displayed in the Quality of Service grouping in the BSS Detailed View. Specifies the THP weight of interactive 2 class. Traffic Handling Priority controls relative throughput of PFCs by assigning a “weighting factor” for interactive 2 class. Grayed out if QoS Feature is not purchased. Field becomes read only if bssgp_pfc_bit is set to On (1). If thp_i2_weight is modified and then bssgp_pfc_bit is set from 0 to 1, the BSS Detailed View reverts back to previously saved value for thp_i2_weight.
10 - 40 Default is 40.
THP Weight of Interactive 3 Class thp_i3_weight
Displayed in the Quality of Service grouping in the BSS Detailed View. Specifies the THP weight of interactive 3 class. Traffic Handling Priority controls relative throughput of PFCs by assigning a “weighting factor” for interactive 3 class. Grayed out if QoS Feature is not purchased. Field becomes read only if bssgp_pfc_bit is set to On (1). If thp_i3_weight is modified and then bssgp_pfc_bit is set from 0 to 1, the BSS Detailed View reverts back to previously saved value for thp_i3_weight. thp_i3_weight must be less than or equal to the value of thp_i2_weight.
10 - 40 Default is 40.
THP Weight of Background Class thp_bg_weight
Displayed in the Quality of Service grouping in the BSS Detailed View. Specifies the THP weight of background class. Traffic Handling Priority controls relative throughput of PFCs by assigning a “weighting factor” for background class. Grayed-out if QoS Feature is not purchased. Field becomes read only if bssgp_pfc_bit is set to On (1). If thp_bg_weight is modified and then bssgp_pfc_bit is set from 0 to 1, the BSS Detailed View reverts back to previously saved value for thp_bg_weight. thp_bg_weight must be less than or equal to the value of thp_i3_weight.
10 - 40 Default is 40.
Continued
68P02901W17-S
2-159 Dec 2009
Quality of Service parameters
Table 2-34
Chapter 2: Configuring BSS Features
Quality of Service parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Values
THP Weight of Best Effort Class thp_be_weight
Displayed in the Quality of Service grouping in the BSS Detailed View. Specifies the THP weight of best effort class. Traffic Handling Priority controls relative throughput of PFCs by assigning a “weighting factor” for best effort class. Grayed-out if QoS Feature is not purchased. Field becomes read only if bssgp_pfc_bit is set to On (1). If thp_be_weight is modified and then bssgp_pfc_bit is set from 0 to 1, the BSS Detailed View reverts back to previously saved value for thp_be_weight. thp_be_weight must be less than or equal to the value of thp_i3_weight.
0 - 40 Default is 40.
ARP Parameter for Best Effort Class PFCs pfc_be_arp
Displayed in the Quality of Service grouping in the BSS Detailed View. Specifies choices for ARP parameter for PFCs belonging to best effort traffic class. Grayed-out if QoS Feature is not purchased. If arp_signal_sele is set to ‘Disable ARP across BSS (0)’, any attempt to modify pfc_be_arp displays the following message: “WARNING: Any changes to pfc_be_arp do not change system behavior when arp_signal_sele is equal to 0”.
0, 1, 2, or 3, where: ARP mapped from precedence class (0), ARP 1 (1), ARP 2 (2), ARP 3 (3). Default is ARP mapped from precedence class (0).
GPRS Scheduling Beta Algorithm gprs_sched_beta
Displayed in the GPRS grouping in the BSS Detailed View. QoS modifies the behavior of this parameter. If gprs_sched_beta is modified and saved while QoS is enabled, the following message is displayed: “WARNING: Changes to gprs_sched_beta are overridden while QoS is enabled”.
Enhanced One Phase Access eop_enabled
Displayed in the GPRS grouping in the BSS Detailed View. QoS modifies the behavior of this parameter. If bssgp_pfc_bit is set to On (1), any modification to eop_enabled is overridden. If eop_enabled is modified and saved while QoS is enabled and bssgp_pfc_bit is set to on(1), the following message is displayed: “WARNING: Changes to eop_enabled are overridden while QoS is enabled”. Continued
2-160
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-34
Quality of Service parameters
Quality of Service parameters (Continued)
OMC-R GUI field name/BSS parameter name CELL parameters:
Description
Values
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the downlink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2 - 24 for Interactive traffic class, traffic handling priority 1. Grayed-out if QoS Feature is not purchased. read only if bssgp_pfc_bit is set to On (1).
2 - 24. Default 2.
Uplink MTBR for Interactive THP 1 qos_mtbr_i1_ul
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2 - 6 for Interactive traffic class, traffic handling priority 1. Grayed-out if QoS Feature is not purchased. read only if bssgp_pfc_bit is set to On (1).
2 - 6. Default is 2.
Uplink MTBR for Interactive THP qos_mtbr_i1_ul
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2-6 for Interactive traffic class, traffic handling priority 1. Grayed-out if QoS Feature is not purchased. Read only if bssgp_pfc_bit is set to On (1).
2 - 6. Default is 2.
Downlink MTBR for Interactive THP 2 qos_mtbr_i2_dl
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the downlink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2-24 for Interactive traffic class, traffic handling priority 2. Must be less than or equal to the value of qos_mtbr_i1_dl. Grayed-out if QoS Feature is not purchased. Read only if bssgb_pfc_bit is set to On (1).
2 - 24. Default is 2.
MTBR for Interactive THP 1 qos_mtbr_i1_dl
Continued
68P02901W17-S
2-161 Dec 2009
Quality of Service parameters
Table 2-34
Chapter 2: Configuring BSS Features
Quality of Service parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Values
Uplink MTBR for Interactive THP 2 qos_mtbr_i2_ul
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2-6 for Interactive traffic class, traffic handling priority 2. Grayed-out if QoS Feature is not purchased. Must be less than or equal to the value of qos_mtbr_i1_ul. Grayed-out if QoS Feature is not purchased. Read only if bssgp_pfc_bit is set to On (1).
2 - 6. Default is 2.
Downlink MTBR for Interactive THP 3 qos_mtbr_i3_dl
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the downlink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2-6 for Interactive traffic class, traffic handling priority 3. Grayed-out if QoS Feature is not purchased. Must be less than or equal to the value of qos_mtbr_i2_dl. read only if bssgp_pfc_bit is set to On (1).
2 - 6. Default is 2.
Uplink MTBR for Interactive THP 3 qos_mtbr_i3_ul
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2-6 for Interactive traffic class, traffic handling priority 3. Grayed-out if QoS Feature is not purchased. Must be less than or equal to the value of qos_mtbr_i2_ul. Read only if bssgp_pfc_bit is set to On (1).
2 - 6. Default is 2.
Downlink MTBR for Best Effort Traffic Class qos_mtbr_be_dl
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the downlink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2-6 for Best Effort traffic class. Grayed-out if QoS Feature is not purchased. Read only if bssgp_pfc_bit is set to On (1).
2 - 6. Default is 2.
Continued
2-162
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-34
Quality of Service parameters
Quality of Service parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Values
Uplink MTBR for Best Effort Traffic Class qos_mtbr_be_ul
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2-6 for Best Effort traffic class. Grayed-out if QoS Feature is not purchased. Read only if bssgp_pfc_bit is set to On (1).
2 - 6. Default is 2.
Downlink MTBR for Background Traffic Class qos_mtbr_bg_dl
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the downlink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2-6 for Background traffic class. Grayed-out if QoS Feature is not purchased. Read only if bssgp_pfc_bit is set to On (1).
2 - 6. Default is 2.
Uplink MTBR for Background Traffic Class qos_mtbr_bg_ul
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies the uplink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2-6 for Background traffic class. Grayed-out if QoS Feature is not purchased. Read only if bssgp_pfc_bit is set to On (1).
2 - 6. Default is 2.
PAR Waiting Time gprs_par_wait_ind
Displayed in the Quality of Service grouping in the CELL Detailed View, GPRS section. Specifies how long the mobile needs to wait before Re-Raching into the cell. Grayed-out if GPRS Feature is not purchased.
100 - 750. Default is 150. The unit is Block Periods; one Block Period is 20 ms.
Displayed in the Quality of Service grouping in the PCU Detailed View. Guards the DOWNLOAD-BSS-PFC procedure. Grayed out if the QoS feature (qosOpt) is restricted. Set to read only if bssgp_pfc_bit is set to 1 (On).
Displayed in the Quality of Service grouping in the PCU Detailed View. Guards the MODIFY-BSS-PFC procedure. Grayed out if the QoS feature (qosOpt) is restricted. Set to read only if bssgp_pfc_bit is set to 1 (On).
Displayed in the Quality of Service grouping in the PCU Detailed View. Guards the RA-CAPABILITY-UPDATE procedure. Grayed out if the GPRS feature (gprsOpt) is restricted.
1000 - 30000. Default is 3000.
Maximum Number of Retries for PFC Download bssgp_dwnld_retry
Displayed in the Quality of Service grouping in the PCU Detailed View. Indicates the maximum number of retries for PFC Download. Grayed out if the QoS feature (qosOpt) is restricted.
1 - 3. Default is 3 (tries).
Negotiated value of CBL Bit cbl_bit_negotiate
Displayed in the Quality of Service grouping in the PCU Detailed View. Indicates the negotiated value of CBL Bit.
0 or 1. 0 = CBL feature at PCU disabled. 1 = CBL feature at PCU enabled. No default. Read only.
Negotiated Value of PFC Bit pfc_bit_negotiate
Displayed in the Quality of Service grouping in the PCU Detailed View. Indicates the negotiated value of PFC Bit.
0 or 1. 0 = QoS feature at PCU disabled. 1 = QoS feature at PCU enabled. No default. Read only.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Network Assisted Cell Change (NACC)
Network Assisted Cell Change (NACC) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview The Network Assisted Cell Change (NACC) feature reduces the overhead associated with cell selection.
Description The Network Assisted Cell Change feature consists of two independent procedures. The first procedure allows the MS to indicate to the network the need for a cell change. In the second procedure, the network provides neighbor cell data to the MS. For a full description of NACC, see Technical Description: BSS Implementation (68P02901W36).
Procedure 1: PCCN procedure The MS notifies the network using a Packet Cell Change Notification (PCCN) message when a cell reselection is needed and delays the cell reselection to let the network respond with neighbor cell system information. This procedure allows the BSS to play a part in deciding the best target cell to which the MS should move. The BSS considers the following to make a decision: •
If the neighbor cell is internal or external to the BSS
•
RxLev measurements of the serving and the neighbor cell as reported by the MS
•
QoS capabilities of the serving and neighbor cells and the QoS profile of the mobile station
•
EGPRS/GPRS availability on the target cells
•
Whether the target cells are in the same routing area
•
Whether the target cells are on the same PRP board
•
Whether the proposed target cell/neighbor cell is a macro or a micro cell
•
If the neighbor cell is within the same PCU
Procedure 2: Neighbor cell data After the target cell has been determined, the network sends the MS a Packet Neighbor Cell Data (PNCD) message containing the information needed for the MS to access the target cell. The neighbor cell information is sent to the MS in the source cell before the MS performs cell reselection so that the MS can perform packet access without reading all of the system information in the target cell. This procedure could also be an extension of Procedure 1 if the network has information about the target cell.
68P02901W17-S
2-165 Dec 2009
Interaction with QoS (Quality of Service)
Chapter 2: Configuring BSS Features
Interaction with QoS (Quality of Service) The areas where QoS and NACC/NCCR interact are detailed in the following sections.
Congestion Relief When performing congestion relief, QoS has to be considered so as to not move high priority users for the sake of reducing congestion. QoS signals if a cell is congested and also sends a candidate list of mobiles preferable for cell reselection. Cell congestion and PRP congestion are indicated separately by QoS. In both cases the candidate list of mobiles are the only list of mobiles considered for cell reselection due to congestion relief. However, when PRP congestion is indicated, only the mobiles that can be reselected to cells that are not on the congested PRP are considered for cell reselection.
Idle Mode Cell Reselection When MSs are in idle mode, the QoS congestion level is used to determine how to logically size the cell for the idle mobiles in the cell. Idle mode congestion relief would help in QoS admission control as it would reduce the number of mobiles waiting for resources in the cell.
Interaction with other features This feature interacts with the IMRM feature, see Intelligent Multilayer Resource Management (IMRM) on page 2-148 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).
Displayed in the Optional Features grouping of the BSS Detailed View. Displays whether the Network Assisted Cell Change Feature is Unrestricted or Restricted for the BSS.
0 or 1, where: Restricted (0). Unrestricted (1). It cannot be modified by a user. Continued
2-166
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
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: Disabled (0). Enabled (1).
GPRS Type 5 Algorithm Enabled gprs_type5_alg
Displayed in the GPRS grouping of the BSS Detailed View. Allows enabling and disabling of the GPRS type-5 microcellular algorithm for the BSS. Enabling the GPRS type 5 algorithm is only allowed when the NACC feature, microcellular feature and NCCR feature are enabled for the BSS.
0 or 1, where: 0 = GPRS type-5 algorithm is disabled. 1 = GPRS type-5 algorithm is enabled.
Congestion Threshold gprs_cell_cgt_thr
Removed by introduction of the QoS feature.
68P02901W17-S
2-167 Dec 2009
Enhanced Multi-level Precedence and Pre-emption (eMLPP)
Chapter 2: Configuring BSS Features
Enhanced Multi-level Precedence and Pre-emption (eMLPP) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview Enhanced Multi-Level Precedence and Pre-emption (eMLPP) feature enhances the control of call traffic by adding multi level precedence and pre-emption to the existing functionality of prioritizing the calls and call queuing.
Background Previous software allowed only two levels of priority; high priority and low priority. Emergency calls were classified as high priority calls and non-emergency calls were classified as low priority calls. Hence, only pre-emption of non-emergency calls by emergency calls was supported by the system. The pre-emption was implemented within the BSS. The BSS ignored the PCI and PVI information in the assignment request message from MSC. Pre-emption was performed in the following: •
TCH pre-emption – emergency calls (high priority) calls are allowed to pre-empt the non-emergency calls (low priority). TCH pre-emption during initial establishment is supported for the emergency calls only when the ECP feature is enabled.
•
Ater pre-emption – supported for the emergency calls (including Ater switchover) as an option only when the ECP feature is enabled.
•
Mobis channel pre-emption – supported for emergency calls by BTS concentration only when the ECP feature is enabled.
Description of eMLPP The eMLPP feature adds multi level priority (precedence), to which an originating and incoming external handover call can be assigned. The BSS conforms to 3GPP 48.008 standards in supporting the full set of priority and pre-emption procedures. Three kinds of resource pre-emption are supported: TCH, Ater channel, and queue block. Pre-emption is supported for:
2-168
•
New call set up
•
External handover that comes into the BSS
•
Internal imperative handover (not queue block)
•
Call switchover by which calls do not necessarily need to be terminated due to a single failure on the link set (not queue block).
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
eMLPP parameters
When eMLPP is enabled: •
In EAC mode (irrespective of whether ECP functionality is enabled), Ater pre-emption based on priority is supported for call setup, external handover and internal imperative handover requests.
•
In EAC/AC mode, Ater pre-emption is supported for call switchover.
It is responsibility of MSC to ensure that the priority, pci/pvi, and QA are set consistently for emergency calls and non-emergency calls. It is responsibility of MSC to protect a TS12 call from pre-emption by setting pvi = 0 to this kind of call. The BSS follows the pci/pvi and priority settings as per MSC assigned values without any modification or validation. For example, if the MSC mistakenly set pvi = 1 to an emergency call, this call is not protected and can be pre-empted in BSS. For a full description of NACC, see Technical Description: BSS Implementation (68P02901W36).
eMLPP parameters Table 2-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).
Table 2-36
Enhanced Multi-level Precedence and Pre-emption (eMLPP) parameters
OMC-R GUI field name/BSS parameter name EMLPP Feature enhancedMLPPOpt
Description Displayed in the Optional Features grouping of the BSS Detailed View. Displays whether the Enhanced Multi-Level Precedence and Preemption (eMLPP) feature is unrestricted or restricted.
Values 0 or 1, where: Restricted (0). Unrestricted (1).
Continued
68P02901W17-S
2-169 Dec 2009
eMLPP parameters
Table 2-36 (Continued)
Chapter 2: Configuring BSS Features
Enhanced Multi-level Precedence and Pre-emption (eMLPP) parameters
OMC-R GUI field name/BSS parameter name
2-170
Description
Values
Preemption Options option_preempt (previously called option_emergency_ preempt)
Displayed in the Pre-emption grouping in the BSS Detailed View. Displays the selected pre-emption option.
0 - 3, or, 0 or 1. If enhancedMLPPOpt is enabled, the range is 0 - 3, where: ECP and eMLPP Disabled (0) ECP Enabled eMLPP Disabled (1) ECP Disabled eMLPP Enabled (2) ECP and eMLPP Enabled (3). If enhancedMLPPOpt is disabled, the range is 0 - 1, where: ECP Disabled (0) ECP Enabled (1). Default is 0.
Emergency Group Priority emergency_ group_priority
Displayed in the Pre-emption grouping in the BSS Detailed View. Defines a priority level threshold for calls. Any call (including handovers) with higher or equal priority than emergency_group_priority is exempt from certain congestion mechanisms. Grayed out if enhancedMLPPOpt is disabled.
0 - 14. Default is 0 meaning no calls are exempt (disabled) from certain congestion mechanisms.
PDTCH Priority sw_pdtch_priority
Displayed in the Pre-emption grouping in the BSS Detailed View. Indicates the priority level for switchable PDTCH resources. This ensures that the equal or lower priority calls to the PDTCH do not steal the PDTCH resources. Grayed out if enhancedMLPPOpt is disabled.
1 - 14. Default is 14, meaning priority protection is disabled allowing all calls to allocate switchable PDTCH resources.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Fast Call Setup
Fast Call Setup ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview The Fast Call Setup feature speeds up the time taken to set up a standard voice call.
Description The Fast Call Setup feature assigns the MS directly to the TCH during the IMMEDIATE ASSIGNMENT message, when the available TCHs for the BCCH band are below the operator-configured threshold. Once the TCH usage for the outer zone has equaled or exceeded this threshold, the BSS performs assignment through the SDCCH. The benefits of this direct assignment are: •
Returning the MS from the SDCCH to the TCH is avoided.
•
Establishing the main signaling (LAPDm) is only done once.
•
The data throughput on the TCH is faster than that of the SDCCH.
•
The operator–configured thresholds can help avoid cell congestion due to “phantom RACHs”.
Interaction with other features This feature interacts with the IMRM feature, see Intelligent Multilayer Resource Management (IMRM) on page 2-148 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-S
2-171 Dec 2009
Fast Call Setup parameters
Table 2-37
Chapter 2: Configuring BSS Features
Fast Call Setup parameters
OMC-R GUI field name/BSS parameter name
Description
Values
BSS parameters: 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) is disabled. This field is grayed-out if the Fast Call Service feature (FastCallOpt) is restricted (Disabled (0)).
Installation and Configuration: GSM System Configuration
RSL Congestion Control
RSL Congestion Control ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview The Radio Signaling Link (RSL) Congestion Control feature protects downlink RSLs from GSM paging surges, which can occur during events such as Formula 1 car crashes, football goal scoring and so on. The controls are scalable, fault tolerant of message losses in the BSC's LAN, and interact with the MSC.
Description The purpose of RSL Congestion Control is to detect the onset of RSL congestion. When RSL congestion is detected, any new service requirements are rejected and the MSC is notified with an OVERLOAD message until the congestion abates. During the congestion, the BSS alarms the OMC-R and provides a statistic with the amount of time a processor was in a congested state and the number of OVERLOAD messages that were sent to the MSC.
RSL congestion control parameters Table 2-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).
Table 2-38
RSL congestion control parameters
OMC-R GUI field name/BSS parameter name RSL Congestion Upper Threshold (%) rsl_lcf_congestion_thi
Description
Values
Displayed in the RSL Congestion grouping of the BSS Detailed View. The high threshold to detect RSL congestion on an RSL–LCF. If the RSL–LCF board detects the number of congested RSL links are more than this percentage of the total number of RSLs it services, then the RSL–LCF board is in congestion status.
1 - 100. Default is 60%. If set to 0%, the BSS does not send out XOFF information on RSL–LCF.
Displayed in the RSL Congestion grouping of the BSS Detailed View. The low threshold to detect RSL–LCF not in a congested state. If the RSL–LCF board detects the number of congested RSL links are less than this percentage of the total number of RSLs it services, then the RSL–LCF 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.
1000 - 1000000 (ms). Default is 12500 (ms).
RSL Congestion Alarm Clear Time (ms) rsl_congestion_alarm _timer
Displayed in the RSL Congestion grouping of the BSS Detailed View. Defines the minimum interval between reporting and clearing RSL congestion alarms to the OMC-R on a per RSL–LCF basis.
Displayed in the RSL Congestion grouping of the BSS Detailed View. Enables or disables the BSC to send an OVERLOAD message to the MSC when there is RSL congestion.
0 or 1, where: Disabled (0), Enabled (1). Default is Disabled (0).
Max Number of Page Messages per Second max_pagenum_per_sec
Displayed in the RSL Congestion grouping of the BSS Detailed View. Defines the maximum number of PAGE messages that can be sent from the BSC to a BTS in a second.
70 - 65535. Default is 65535.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
VersaTRAU
VersaTRAU ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
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 optimize backhaul usage and reduce costs. This feature is only available if the EGPRS (egprsOpt) feature is unrestricted (enabled). VersaTRAU channel information is displayed in the Channel Status form, see Displaying Channel and Circuit Status on page 9-20.
NOTE A 16 k TRAU Half Rate call is not supported on a 64 k carrier, regardless of whether VersaTRAU is restricted or unrestricted. A VersaTRAU Backhaul Summary report can be displayed from the Navigation Tree by right-clicking the site instance and then selecting VersaTrau Backhaul Summary option from the drop-down list, see OMC-R Online Help, Network Operations for further details.
Description The VersaTRAU feature reduces backhaul costs by taking advantage of statistical multiplexing that can be achieved when packing variable size radio blocks, to be sent over PDCHs on a carrier, into one large TRAU frame associated with the carrier. This feature creates a pool of DS0s connections between the BTS and PCU for an EDGE carrier. The size of the pool is allocated by the operator depending on anticipated data traffic for the site. EDGE data packets are routed onto this pool as required. The VersaTRAU feature eliminates the static mapping between a PDCH and backhaul resources. All the PDCHs on a 64 k carrier shares a group of DS0s defined by a VersaTRAU channel. The feature eliminates the need for one-to-one mapping of air TSs and TRAU slots and instead allows configuration of a versatile TRAU backhaul that will carry the data load for a carrier. The impacts to backhaul synchronization are minimal; expanding and contracting the number of air timeslots and/or TRAU timeslots is done seamlessly as long as at least one air timeslot on the VersaTRAU carrier is in synchronization
68P02901W17-S
2-175 Dec 2009
Permissible values for RTF backhaul timeslots
Chapter 2: Configuring BSS Features
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-185).
Table 2-39 Possible values for RFT field: Number of Backhaul Timeslots on Carrier (rtf_ds0_count)
2-176
Packet Radio Type field
EGPRS enabled
VersaTRAU enabled
64 k (3)
YES
64 k (3)
BCCH
Half Rate field
8k TRAU Allowed field
Valid range
Default
Sensitivity?
YES
YES
Disabled
N/A
3 to 7
3
Sensitive
YES
YES
YES
Enabled
YES
3 to 7
3
Sensitive
64 k (3)
YES
YES
NO
Disabled
N/A
3 to 8
3
Sensitive
64 k (3)
YES
YES
NO
Enabled
YES
3 to 8
3
Sensitive
64 k (3)
YES
NO
YES
N/A
N/A
7
Value of 7 sent from BSS.
Insensitive
64 k (3)
YES
NO
NO
N/A
N/A
8
Value of 8 sent from BSS.
Insensitive
None
N/A
N/A
N/A
N/A
N/A
1 to 8
Value sent from BSS.
Grayedout
16 k (1)
N/A
N/A
N/A
N/A
N/A
1 to 8
Value sent from BSS.
Grayedout
32 k (2)
N/A
N/A
N/A
N/A
N/A
1 to 8
Value sent from BSS.
Grayedout
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
VersaTRAU parameters
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).
Table 2-40
VersaTRAU parameters
OMC-R GUI field name/BSS parameter name
Description
Values
BSS parameters: VersaTRAU Feature versaTrauOpt
Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether versaTRAU feature is unrestricted (enabled) or restricted (disabled). Cannot be modified by a user. This feature is only available if the EGPRS feature (egprsOpt) is unrestricted (enabled).
0 or 1, where: Disabled (0). Enabled (1).
Displayed in the GPRS grouping of the RTF Detailed View. If the VersaTRAU feature is enabled, defines the number of DS0s for RTF backhaul, when equipping an EGPRS capable RTF (64 k RTF). Modifying this field displays the following message: WARNING: This operation may cause a carrier to be taken out of service and calls affected by this carrier may be lost. Loss of calls depends on the availability of other carriers. Do you wish to modify?
1 - 8. See Table 2-39 for details of possible values and defaults.
RTF parameters: Number of Backhaul Timeslots on Carrier rtf_ds0_count
68P02901W17-S
2-177 Dec 2009
Feature Capacity Licensing and Audit
Chapter 2: Configuring BSS Features
Feature Capacity Licensing and Audit ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
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 is extended on each release to incorporate new features in the audit functions. For each customer, a license file is issued which contains the information on current licensed capacity for every licensable feature. A single license key is provided to control this information per network. The License Audit Tool is distributed with the OMC software, and installed and configured by the user. The audit is triggered by a configurable interval parameter in the OMC software. If the interval parameter is not set, or set outside the permissible range [2 hours, 48 hours], the default value of 12 hours is used. The result of the audit (actual usage) is compared with the license file per feature. An alarm is generated when the carrier usage for one or more features exceeds the carriers purchased for those features. If the usage is within the limit, the License Audit Tool generates an event which indicates that the carrier usage is within the license purchase. The alarms and events are displayed at one or all OMC(s) in the network as previously configured during installation and configuration. The License Audit Tool produces a report which is stored in a predefined location containing the result of the latest audit and license file comparison. Users and Motorola have access to this report by physically accessing the location where the file is stored.
Configuration and operation Details regarding the configuration and operation of the License Audit tool are described in the manual System Information: License Audit (68P02901W59).
2-178
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Improved Timeslot Sharing
Improved Timeslot Sharing ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview Improved Timeslot Sharing (ITS) feature is an optional feature, which supports Enhanced GPRS (EGPRS) on a Double Density (DD) CTU2. It requires no hardware changes to the CTU2, BSS software and Horizon II firmware. In that way the EGPRS PDTCH (Packet Data Traffic Channel) can only be configured on Carrier A of a DD CTU2 while the corresponding timeslots on the paired Carrier B must be blanked out. Improved Timeslot Sharing (ITS) feature is only available if the EGPRS (egprsOpt) and VersaTRAU (versaTrauOpt) are unrestricted (enabled). ITS provides more channels to service voice users with EGPRS service in parallel and when implemented in the EGPRS network it further improves the network capacity.
Interaction with other features ITS interacts with the following features: •
VersaTRAU
•
Enhanced Multi-level Precedence and Pre-emption (eMLPP)
NOTE The ITS feature requires the EGPRS and VersaTRAU features to be unrestricted.
ITS parameters Table 2-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.
Table 2-41
ITS parameters
OMC-R GUI field name/BSS parameter name Improved Timeslot Sharing Feature itsOpt
Description
Values
Displayed in the Optional Features grouping of the BSS Detailed View. Indicates whether ITS is unrestricted (enabled) or restricted (disabled).
0 or 1, where: Disabled (0). Enabled (1).
Continued 68P02901W17-S
2-179 Dec 2009
ITS parameters
Chapter 2: Configuring BSS Features
Table 2-41
ITS parameters (Continued)
OMC-R GUI field name/BSS parameter name Improved Timeslot Sharing Enabled improve_ts_enabled (OMC-R parameter name: its_enabled)
2-180
Description
Values
Displayed in the Improved Timeslot Sharing group of the BSS Detailed View.
0 or 1, where: Disabled (0). Enabled (1).
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
GPRS - Suspend/Resume
GPRS - Suspend/Resume ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{27717}
Overview of GPRS – Suspend/Resume The GPRS Suspend and Resume feature provides the BSS system the ability to suspend and resume GPRS services.
Description of GPRS – Suspend/Resume The MS requests the network for a suspension of GPRS services by sending a Suspend message to the network if the following conditions exist: •
A GPRS attached MS enters dedicated mode and the support of Class A mode of operation is not possible.
•
An MS in Class A mode of operation is handed over to cell and the Class A mode of operation is not possible.
The BSC tracks the MS status as Suspended after receiving a Suspend Ack message from the SGSN. Once the conditions for the suspension of GPRS services no longer exist the BSS sends a Resume message to the SGSN. If a Resume Ack message is received from the SGSN, the BSS sends a GPRS Resumption message to the MS to notify the MS that it can resume GPRS service. The MS resumes GPRS services by sending a Routing Area Update Request to the SGSN if one of the following conditions exist: •
If the BSS fails to request the SGSN to resume GPRS services.
•
If the RR Channel Release message was not received before the MS left dedicated mode.
•
If the MS locally determines that the conditions for GPRS suspension have disappeared.
NOTE The GPRS Resume functionality is supported at the intraBSC level only.
Measuring Suspend/Resume statistic The database statistic NUM_SUSP_RESU_RCVD measures per BSS the number of: •
Responses received for Suspend and Resume.
•
No responses received for Suspend and Resume.
•
Resume not triggered due to different reasons.
68P02901W17-S
2-181 Dec 2009
GPRS - Suspend/Resume dependencies
Chapter 2: Configuring BSS Features
See Maintenance Information: GSM Statistics Application (68P02901W56) for full statistics details.
GPRS - Suspend/Resume dependencies The GPRS - Suspend/Resume requires the GPRS feature (gprsOpt) to be unrestricted (enabled).
GPRS - Suspend/Resume parameters Table 2-40 details the parameters associated with GPRS - Suspend/Resume feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
Displayed in the SSM Timers grouping of the BSS Detailed View. Indicates the timer used to guard the GPRS Suspend /Resume procedures. The PCU starts this timer once RESUME PDU or SUSPEND PDU is sent out to an SGSN. The timer stops when the PCU receives a RESUME ACK/NACK PDU or SUSPEND ACK/NACK PDU from the SGSN.
100 - 10000 ms Default: 800.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration Suspend/Resume parameter using the TTY interface
Configuring GPRS -
Configuring GPRS - Suspend/Resume parameter using the TTY interface The disp_element and chg_element commands can be used to display and configure the GPRS - Suspend/Resume parameter bssgp_t4_timer. Use the disp_element command to display the value of the bssgp_t4_timer. For example, the following command displays the current value of the bssgp_t4_timer at BSS location 0: disp_element bssgp_t4_timer 0 The system replies, for example: bssgp_t4_timer = 800 Use the chg_element command to modify the value of the bssgp_t4_timer. For example, the following command modifies the current value of the bssgp_t4_timer at BSS location 0, to 300 ms. chg_element bssgp_t4_timer 300 0 The system replies: COMMAND ACCEPTED
68P02901W17-S
2-183 Dec 2009
Increased Network Capacity
Chapter 2: Configuring BSS Features
Increased Network Capacity ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{28398}
Overview of Increased Network Capacity The Increased Network Capacity feature is an optional feature. This feature increases the system capacity limits as follows: •
Maximum Carriers per BSC from 512 to 1000
•
Maximum Sites per BSC from 100 to 140
•
Maximum Circuits per BSC from 3200 to 6200
•
Maximum number of BSC-XCDR connections a BSC can support increases from 27 to 60
Determining whether Increased Network Capacity is enabled It is possible to use the OMC-R GUI or the TTY interface to determine if Increased Network Capacity is enabled.
Using the OMC-R GUI To check if the Increased Network feature has been enabled using the OMC-R GUI, display the setting of Increased Network Capacity Feature (incNetCapacityOpt) field. This field is located in the Optional Features grouping in the BSS Detailed View. The values for Increased Network Feature field are: •
Disabled (0)
•
Enabled (1)
Using the TTY interface To check if Increased Network feature has been enabled using the TTY interface, enter the following command: disp_options all If the Increased Network Capacity is unrestricted (enabled) the system displays the following in the unrestricted list: 81 Increased Network Capacity
2-184
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Interaction with other features
Interaction with other features The Increased network Capacity feature interacts with the following features: •
Enhanced BSC capacity using DSW{22168}
•
BSC High Load Protection Mechanism Phase 2 {23306}
•
LAN Packing {28333}
•
HSP MTL {28337}
•
BSP CPU utilization reduction for higher Call handling Capacity {28340}
68P02901W17-S
2-185 Dec 2009
BSC High Load Protection Mechanism Phase 2
Chapter 2: Configuring BSS Features
BSC High Load Protection Mechanism Phase 2 ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{23306}
Overview of BSC High Load Protection Mechanism Phase 2 The BSC High Load Protection Mechanism feature allows the BSC to operate reliably during periods of high utilization and to deal efficiently when traffic surges occur. It provides this reliability by monitoring the Base Site control Processor (BSP) CPU utilization inreal-time. When the BSP CPU utilization reaches the overload threshold, this feature starts controlling the amount of calls and handovers to be handled by the system, so that the CPU utilization of the BSP can be kept under a safe level. This mechanism allows the BSP to operate reliably at 90% utilization.
BSC High Load Protection Mechanism Phase 2 parameters Table 2-43 details the parameters associated with the BSC High Load Protection Mechanism feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description:
BSS Command Reference (68P02901W23)
Table 2-43
BSC High Load Protection Mechanism Phase 2 parameters
Displayed in the BSP Overload Protection group of the BSS Detailed View. Enables or disables the monitoring of the BSP CPU utilization.
0 or 1, where: Disabled (0) Enabled (1) Default is Disabled (0)
Configuring BSC High Load Protection Mechanism Phase 2 It is possible to use the OMC-R GUI or the TTY interface to enable or disable BSC High Load Protection Mechanism Phase 2 feature.
Using the OMC-R GUI To check if the BSC High Load Protection Mechanism Phase 2 feature has been enabled using the OMC-R GUI, display the setting of BSP CPU Overload Protection (bsp_overload_protection) field. This field is located in the BSP Overload Protection grouping in the BSS Detailed View. The values are detailed in Table 2-43.
2-186
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring BSC High Load Protection Mechanism Phase 2
Using the TTY interface The disp_element and chg_element commands can be used to display and enable or disable the BSP CPU Overload Protection parameter bsp_overload_protection. To check if the BSC High Load Protection Mechanism Phase 2 feature has been enabled using the TTY interface, enter the following command: disp_element bsp_overload_protection . For example, the following command displays the current value of the bsp_overload_protection at BSS location bsc: disp_element bsp_overload_protection bsc The system replies, for example: bsp_overload_protection = 1 Use the chg_element command, chg_element bsp_overload_protection to enable or disable the value of the bsp_overload_protection. For example, the following command disables the bsp_overload_protection at location bsc. chg_element bsp_overload_protection 0 bsc The system replies: COMMAND ACCEPTED
68P02901W17-S
2-187 Dec 2009
HSP MTL
Chapter 2: Configuring BSS Features
HSP MTL ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{28337}
HSP MTL The HSP MTL feature increases the capacity and the flexibility of the Signaling Links Set between the BSC and each MSC. Each BSC is connected to each MSC with a Signaling Link Set (SLS). Each Signaling Link Set can accommodate up to 16 distinct Signaling Links (SL). At present the BSC supports each Signaling Link with a 64kbit/s DS0. As a result of the BSC capacity increasing it is now necessary to increase the capacity of the MTLs (MTP Transport Layer Link (A-Interface)). This feature introduces a new High Speed MTL which increases the maximum number of message transfer links to 31. For a full description of HSP MTL, see Technical Description: BSS Implementation (68P02901W36).
Prerequisites to configuring HSP MTL Before configuring HSP MTL ensure that the Increased Network feature incNetCapacityOpt has been enabled. See Increased Network Capacity on page 2-184 for further details.
HSP MTL parameters Table 2-44 details the parameters associated with the HSP MTL feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command
Reference (68P02901W23).
2-188
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-44
HSP MTL parameters
HSP MTL parameters
OMC-R GUI field name/BSS parameter name
Description
Values
mtl_rate
Displayed in the Identification grouping of the MTL Detailed View. Defines the type of MTL to create.
If the Increased Network feature is enabled valid values are 1 or 31. 1= 64k MTL 31 = HSP MTL Default is 1.
ss7_hsp_l2_t1
Displayed in the MTP Timers grouping of the BSS Detailed View. Can only be modified, if incNetCapacityOpt is unrestricted (enabled). Otherwise, the field is grayed out in the BSS Detailed View form.
Valid values: 25000 350,000 ms. Default is 300,000 ms.
max_mtls
Displayed in the Identification grouping of the BSP Detailed View. The number of message transfer links that the BSP can handle. The values 0 to 2 are for 64k MTL and 31 for HSP MTL.
0, 1, 2 or 31. 31 is valid only if the Increased Network feature is enabled.
Displayed in the Identification grouping of the LCF Detailed View. The number of message transfer links that the LCF can handle. The values 0 to 2 are for 64k MTL and 31 for HSP MTL.
0, 1, 2 or 31. 31 is valid only if the Increased Network feature is enabled.
BSS parameters:
Continued
68P02901W17-S
2-189 Dec 2009
HSP MTL parameters
Table 2-44
Chapter 2: Configuring BSS Features
HSP MTL parameters (Continued)
OMC-R GUI field name/BSS parameter name max_gsls
max_cbls
2-190
Description Displayed in the Identification grouping of the LCF Detailed View. The maximum number of GSLs the LCF can manage. Only displayed if:
•
GPRS feature is unrestricted.
•
Sum of max_gsls is greater than or equal to the total number of GSLs equipped.
•
Value of max_gsls must not exceed the available LCF HDLC channel capacity.
•
max_gsls can be changed to non zero value only when max_mtls is not equal to 31.
Displayed in the Identification grouping of the LCF Detailed View. The maximum number of CBLs the LCF can manage.
Values 0 - 12.
0 or 1 1 is valid only if max_mtls is not equal to 31.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration patching and PCU Software Upgrade with no BSC Outage
Software
Software patching and PCU Software Upgrade with no BSC Outage ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{25423}
Overview of Software patching and PCU Software Upgrade with no BSC Outage The software patching section of this feature allows the NE software to be dynamically modified without requiring an NE Element restart. The software patch (Patch Object) contains NE Software changes which after downloading modifies all existing objects. A Patch Object is made up of one or more patch levels compiled together into a Patch Object. The Patch Level corresponds to a patch (fix) or group of patches which address a single problem. The PCU Software Upgrade section of this feature allows new PCU objects to be downloaded and installed at the PCU without requiring a BSS outage. The new PCU objects can be downloaded to the BSC using CSFP download, and from there downloaded to the PCU. After download is completed a swap code object is carried out.
Software patching and PCU Software Upgrade with no BSC Outage parameters Table 2-45 details the parameters associated with the Software patching and PCU Software Upgrade with no BSC Outage feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
68P02901W17-S
2-191 Dec 2009
Software patching and PCU Software Upgrade with no BSC Outage parameters
Table 2-45 parameters
Chapter 2: Configuring BSS Features
Software patching and PCU Software Upgrade with no BSC Outage
OMC-R GUI field name/BSS parameter name
Description
Values
BSS and RXCDR parameters: NE Patch Object Version nePatchObjectVer
Displayed in the Identification grouping of the BSS or RXCDR Detailed View form. Displays the version of the Patch Object. The value 0 indicates that no Patch Object is installed. This parameter cannot be modified by a user and is not displayed for a BSS or RXCDR with Pre-GSR9 software loads.
0 - 255 Default is 0
NE Patch Object Level nePatchObjectLev
Displayed in the Identification grouping of the BSS or RXCDR Detailed View form. Displays the Patch Object Level number set for the NE. The range is the maximum Patch Level of that Patch Object. The value 0 indicates that no Patch Level is installed. This parameter cannot be modified by a user and is not displayed for a BSS or RXCDR with Pre-GSR9 software loads.
0–255 Default is 0
Displayed in the General grouping of the PCU Detailed View form. Displays the CSFP flow control value that controls the amount of GSL link utilization that a CSFP download from BSC to PCU uses. This parameter is also applicable for BTS CSFP. For BTS CSFP, this parameter controls the RSL utilization for CSFP download. This is the pre-GSR9 legacy function.
10 –100 Select in increments of 10. Default is 10.
PCU parameters: CSFP Flow Value csfp_flow
2-192
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Add new PCU hardware to increase GPRS capacity
Add new PCU hardware to increase GPRS capacity ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{28351}
Overview This feature introduces new hardware named Universal DPROC2 (U-DPROC2) to replace all existing legacy DPROCs and increase GPRS capacity. The U-DPROC2 creates a functionality called PXP, which combines PRP and PICP functionality on the same board. The boards are connected with the PSI board in BSC through a Gigabit Ethernet link (GbE). E1 GDS connectivity is supported on PRP/PICP, but not on the PXP. The PRP part of PXP functionality is lost if the Ethernet link goes OOS. U-DPROC2 can be configured as a PRP and PICP (legacy configuration). U-DPROC2 can coexist with a legacy DPROC, which serves as PRP or PICP. It can function as PRP or PICP. Each U-DPROC2 must be paired with a U-DPROC2 RTM (Rear Transition Module). Pairing a U-DPROC2 board with a legacy RTM module or pairing a legacy DPROC board with a U-DPROC2 RTM module is not supported. The PCU supports hot swap capability and provides thermal monitoring for U-DPROC2 boards. The PCU is controlled by a single BSC. This feature reduces the PCU maintenance requirements and configuration complexity.
Add new PCU hardware to increase GPRS capacity parameters Table 2-46 details the parameters associated with the feature Add new PCU hardware to increase GPRS capacity. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, refer to
Add new PCU hardware to increase GPRS capacity parameters
Table 2-46
Chapter 2: Configuring BSS Features
Add new PCU hardware to increase GPRS capacity parameters
OMC-R GUI field name/BSS parameter name
Description
Values
eth_rx_errors_threshold
It specifies the maximum allowable percentage of error among the Ethernet frames received. The percentage parameter is on a per BSS basis. 0 indicates that there is no alarm generated. This parameter changes inside and outside of SYSGEN mode.
0 - 100 Default is 10
eth_tx_errors_threshold
It specifies the maximum allowable percentage of Ethernet transmit errors of all frames transmitted. The percentage parameter is on a per BSS basis. 0 indicates that there is no alarm generated. This parameter changes inside and outside of SYSGEN mode.
0 - 100 Default is 10
psi_trau_fill_frames_ threshold
It specifies the maximum allowable percentage of all TRAU frames transmitted that can be fill frames. The percentage parameter is on a per BSS basis. 0 indicates that there is no alarm generated. This parameter changes inside and outside of SYSGEN mode.
0 - 100 Default is 10
prpThptOpt
This parameter indicates whether the Increase PRP Throughput with PCU feature is unrestricted in the BSS software. If the prpThptOpt flag indicates that Increase the Throughput of PRP with PCU is restricted, attempts to change this feature-specific database parameters are rejected.
0 - restricted 1 – unrestricted
Continued
2-194
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-46
Add new PCU hardware to increase GPRS capacity parameters
Add new PCU hardware to increase GPRS capacity parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Values
dsp_error_inc
This is a new database parameter which identifies the value by which the error count is incremented if an error indication is received for a DSP during a GPRS Alarm Increment Time Period. This parameter defaults to 1 when the ECERM feature is unrestricted and it defaults to 0 when the ECERM feature is restricted. It exists only at a BSC and it is modified inside or outside of SYSGEN mode.
0 - 255 Default is 1
dsp_error_gen_thresh
This is a new database parameter which identifies the value that the error count must be equal to or greater than for an alarm to be generated for a DSP. This parameter is restricted by the ECERM restrictable feature and is modified inside or outside of SYSGEN mode. It exists only at a BSC. If the value of this parameter is reduced, no alarms are generated for those DSPs whose current error counts are equal to or exceed the new value.
2 - 255 Default is 6
dsp_error_clr_thresh
This is a new database parameter which identifies the value that the error count must be equal or less than for an alarm to be cleared for a DSP. This parameter is restricted by the ECERM restrictable feature. It is modified inside or outside of SYSGEN mode and exists only at a BSC. If the value of this parameter is increased, no alarms are cleared for those DSPs whose current error counts are now equal to or below the new value until another GPRS Alarm Increment Time Period passes without error for the DSP.
0 - 253 Default is 0
Continued
68P02901W17-S
2-195 Dec 2009
Dependencies
Chapter 2: Configuring BSS Features
Table 2-46
Add new PCU hardware to increase GPRS capacity parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Values
gds_connectivity
This parameter indicates GDS connectivity.
Minimum value is 0 or E1. Maximum value is 1 or Ethernet.
bsc_eth
This parameter describes the Ethernet connectivity. psi_id indicates a unique PSI ID. bsc_eth_port indicates the BSC Ethernet port.
Minimum value: psi_id - 0 bsc_eth_port - 0
pcu_eth
This parameter describes the Ethernet connectivity. dproc_id indicates a unique DPROC ID. pcu_eth_port indicates the PCU Ethernet port.
Dependencies This feature depends on the following:
2-196
•
High Bandwidth interconnection between BSC and PCU (PSI)
•
Increase the PCU database capacity
•
Packet/Coaxial Interface Module
•
Air Flow Improvements for the PCU Cabinet
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
High Bandwidth interconnection between BSC and PCU (PSI)
High Bandwidth interconnection between BSC and PCU (PSI) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{26740}
Overview This feature uses a PSI (Packet Subrate Interface) to reduce the number of cables between the BSC and the PCU. This enables the BSC to handle higher capacity configurations. The PSI provides an Ethernet link from the BSC to the PCU. Instead of using two MSIs to allow up to 120 timeslots of EDGE data, one slot is occupied by a PSI to allow configurable timeslots from 64 - 320. The freed MSI slot can be used for 2 downstream or upstream span lines.
High Bandwidth interconnection between BSC and PCU parameters Table 2-47 details the parameters associated with the feature High Bandwidth interconnection between BSC and PCU. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, refer to
High Bandwidth interconnection between BSC and PCU parameters
OMC-R GUI field name/BSS parameter name
Description
Value
eth_rx_errors_threshold
It specifies the maximum allowable percentage of error among the Ethernet frames received. The percentage parameter is on a per BSS basis. 0 indicates that there is no alarm generated. This parameter changes inside and outside of SYSGEN mode.
0 – 100 Default is 10
eth_tx_errors_threshold
It specifies the maximum allowable percentage of Ethernet transmit errors of all frames transmitted. The percentage parameter is on a per BSS basis. 0 indicates that there is no alarm generated. This parameter changes inside and outside of SYSGEN mode.
0 – 100 Default is 10
Continued
68P02901W17-S
2-197 Dec 2009
High Bandwidth interconnection between BSC and PCU parameters
Table 2-47 (Continued)
Chapter 2: Configuring BSS Features
High Bandwidth interconnection between BSC and PCU parameters
OMC-R GUI field name/BSS parameter name
Description
Value 0 – 100 Default is 10
psi_trau_fill_frames_ threshold
It specifies the maximum allowable percentage of all TRAU frames transmitted that can be fill frames. The percentage parameter is on a per BSS basis. 0 indicates that there is no alarm generated. This parameter changes inside and outside of SYSGEN mode.
dsp_error_inc
This is a new database parameter which identifies the value by which the error count is incremented if an error indication is received for a DSP during a GPRS Alarm Increment Time Period. This parameter defaults to 1 when the ECERM feature is unrestricted and it defaults to 0 when the ECERM feature is restricted. It exists only at a BSC and is modified inside or outside of SYSGEN mode.
0 – 255 Default is 1
dsp_error_gen_thresh
This is a new database parameter which identifies the value that the error count must be equal to or greater than for an alarm to be generated for a DSP. This parameter is restricted by the ECERM restrictable feature. It is modified inside or outside of SYSGEN mode and exists only at a BSC. If the value of this parameter is reduced, no alarms are generated for those DSPs whose current error counts are equal to or exceed the new value.
2 – 255 Default is 6
Continued
2-198
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-47 (Continued)
Interaction with other features
High Bandwidth interconnection between BSC and PCU parameters
OMC-R GUI field name/BSS parameter name dsp_error_clr_thresh
Description
Value
This is a new database parameter which identifies the value that the error count must be equal or less than for an alarm to be cleared for a DSP. This parameter is restricted by the ECERM restrictable feature. It is modified inside or outside of SYSGEN mode and exists only at a BSC. If the value of this parameter is increased, no alarms are cleared for those DSPs whose current error counts are now equal to or below the new value until another GPRS Alarm Increment Time Period passes without error for the DSP.
0 – 253 Default is 0
Interaction with other features This feature interacts with the following: •
Add New PCU hardware to increase GPRS capacity
•
Increase the PCU database capacity
•
Packet/Coaxial Interface Module
•
Increase throughput of PRP
68P02901W17-S
2-199 Dec 2009
Increase the Throughput of PRP with the PCU
Chapter 2: Configuring BSS Features
Increase the Throughput of PRP with the PCU ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{28000}
Overview The current PRP processor has a fanout of 120 PDCHs but only has a throughput of 30 PDCHs. A rolling blackout mechanism is used to choose which 30 of the 120 PDCHs are serviced in a 20 ms block period. Increase the throughput of PRP with the PCU is an optional feature that provides an option to disable the rolling blackout mechanism on the PCU so that the throughput of the PRP processor is the same as the fanout of the PRP. It provides two options, mode 1 and mode 2. Refer to Table 2-48 for the processing capacity in mode 1 and mode 2. This feature resides on the BSC and PCU. When the rolling blackout mechanism is enabled, a maximum of X timeslots in a PRP are allowed to perform data transfers in each direction (uplink and downlink) during every block period. Without rolling blackout mechanism, all timeslots configured in a PRP are allowed to perform data transfers in both uplink and downlink directions. A PXP configured by the UDPROC-2 board has higher capacity and throughput. The increased throughput of the PRP offers improved support for high throughput services such as HTTP, PoC, and video streaming.
Table 2-48
PRP capacity
DPROC configuration
Total Fanout/Throughput/Number of mobiles Mode 1
Mode 2
DPROC/PRP or U-DPROC2/PRP
120/30/120
60/60/60
U-DPROC2/PXP
280/70/280
140/140/280
Increase the Throughput of PRP with the PCU parameters Table 2-49 details the parameters associated with Increase the Throughput of PRP with the PCU feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, refer to Technical Description: BSS Command Reference (68P02901W23).
2-200
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-49
Interaction with other features
Increase the Throughput of PRP with the PCU parameters
OMC-R GUI field name/BSS parameter name
Description
Values
prpThptOpt
The prpThptOpt parameter indicates whether the Increase PRP Throughput with PCU feature is unrestricted in the BSS software. If the prpThptOpt flag indicates that Increase the Throughput of PRP with PCU is restricted, attempts to change this feature-specific database parameter are rejected.
0 - 1 0 - restricted 1 - unrestricted
prp_fanout_mode
The prp_fanout_mode parameter indicates the PDCHs fanout mode of the PRP in the PCU. The fanout mode of the PRP provides the preference of more PDCH capacity or higher throughput of the PRP. When prp_fanout_mode is in mode 1, more PDCHs can be configured in a PRP, and RLC data blocks can be only scheduled on a number of PDCHs. The rest of the PDCHs in the PRP can be used for RLC control blocks. When prp_fanout_mode is in mode 2, this allows higher throughput of the PRP with fewer PDCHs configured. RLC data blocks are scheduled on all the PDCHs in the PRP. This parameter can only be modified if the optional feature Increase the Throughput of PRP with PCU is unrestricted.
1 - 2 Default is 1 1 - the rolling blackout mechanism is enabled at the PCU 2 - the rolling blackout mechanism is disabled at the PCU
Interaction with other features This feature interacts with the following: •
Add new PCU hardware to increase GPRS capacity {28351}
•
Software on old platform without new hardware {27955A}
•
QoS Streaming {27703A}
68P02901W17-S
2-201 Dec 2009
Support of Incell as an optional feature
Chapter 2: Configuring BSS Features
Support of Incell as an optional feature ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{28938}
Overview This feature provides the option to restrict the use of Incell BTS sites within a network if required. During the database upgrade (upgrading GSR8 database to GSR9) the system does not allow any Incell site to be equipped in the database unless the customer has purchased this feature. This feature also restricts the adding of Incell hardware if the option has not been purchased.
Support of Incell as an optional feature parameters Table 2-50 details the parameters associated with Support of Incell as an optional feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, refer to Technical Description: BSS Command Reference (68P02901W23).
Table 2-50
Support of Incell as an optional feature parameters
OMC-R GUI field name/BSS parameter name IncellOpt
2-202
Description
Values
This parameter indicates whether the Incell Support feature functionality is unrestricted in the BSS software. If the IncellOpt flag indicates that Incell Support is restricted, attempts to change Incell Support specific database parameters are rejected.
0 - 1 0 - restricted 1 - unrestricted
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
BSP CPU utilization reduction for higher call handling capacity
BSP CPU utilization reduction for higher call handling capacity ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{28340}
Overview With the memory restriction removed, the CPU efficiency can be improved at the cost of higher memory usage. A list-based Ater search algorithm is used to allocate resources when a new call (mobile originated, mobile terminated, external handover from MSC), CIC remap, or Ater switchover is initiated or for calls with rate change. The Aters are allocated from the top of the available lists to minimize the search. This ensures that the mean BSP CPU utilization does not exceed 70%.
68P02901W17-S
2-203 Dec 2009
BSS User Security Management
Chapter 2: Configuring BSS Features
BSS User Security Management ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{27508}
Overview The BSS User Security Management feature provides enhanced user security functionality to a customer network, by providing the operator with the ability to define individual user names and passwords for BSS access from the OMC-R, and also locally at the BSS TTY. This provides information about the users logged into the network through their user name and ID. The user names and passwords have standard password control features such as complexity checking, ageing and storage in encrypted format, and are managed from the OMC-R. A user profile is associated with each user name, which provides controlled access to a partitioned command set at the BSS. Both standard BSS commands and EMON commands are partitioned. The OMC-R administrator can create user name and assign a profile to each user which defines the BSS and EMON command sets that the user can access at the BSS. Authentication is carried out at the OMC-R when the user first logs in, using a UNIX account setup by OMCADMIN. When a user uses remote login to access a NE from the OMC-R, the user is automatically authenticated using their UNIX login. If regions are enabled, the username is compared to a list of NEs held at the OMC-R to determine if the user has access to the NE. The OMC authenticates the user account and password for qcomm which are sent from BSS. Passwords need be to be encrypted in BSS and decrypted in OMC. When the OML link is not in service, only the field engineer can qcomm on BSS. Users that qcomm from BSS are logged. The user name, time stamp, commands name and board id are also logged. This feature supports two types of login:
2-204
•
OMC-R accounts: These are the same UNIX accounts used to login to the OMC-R and are maintained at the OMC-R. Each account has an access level which defines the set of commands that can be accessed by the user. There are 4 access levels (numbered 1 to 4), where level 1 provides read only commands and level 4 allows access to all commands. Passwords for these accounts are managed through the existing OMC-R administration procedures. Authentication is performed at the OMC-R. These accounts cannot be used when the OML is out of service.
•
Field engineering accounts: These are for use by field engineers when executing MMI/emon commands locally on the NE equipment. There are 3 instances of these accounts, each of which has a fixed access level that cannot be changed. These accounts cannot be used for remote login from the OMC-R. They are intended to be used when the OML is out of service, or by engineers who do not have OMC-R user accounts. When the OML is out of service, these are the only accounts that can be used to access the NE. The passwords for these accounts are managed at the OMC-R, which propagates them to the network elements. Authentication is performed locally at the NE. When initially deployed, the BSS has default passwords which are used until it is connected to the OMC-R. The OMC-R then updates the BSS database with the current passwords and these passwords are used for all subsequent authentication.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-51
BSS User Security Management parameters
Field engineering accounts
Account
Access Level
fieldeng2
level 2
fieldeng3
level 3
fieldeng4
level 4
BSS User Security Management parameters Table 2-52 details the parameters associated with the feature BSS User Security Management. The following parameters are OMC only attributes and the BSS name is not applicable. For further details of these and other parameters, refer to Technical Description: BSS Command Reference (68P02901W23).
Table 2-52
BSS User Security Management parameters
OMC-R GUI field name/BSS parameter name
Description
Values
fieldeng_always_enabled
The fieldeng_always_enabled parameter specifies whether the field engineering accounts at the BSS/RXCDR are used only when the OML link is down or irrespective of whether the OML link is up or down.
0 - 1 Default is 1. 0 - fieldengX accounts can be used only when the OML link is down. 1 - fieldengX accounts can be used whether the OML link is up or down.
ExpLoginCount
This parameter is a counter used by CM MIB to keep track of the number of login attempts by a normal NE user after the password expires.
Minimum - 0 Maximum - 5 Default is 5.
fieldeng2_pass
This parameter is a computed field, hence the default value cannot be stated. This has to be taken care of by the cutover or clean install script while doing the MIB upgrade which invokes the encryption algorithm to compute the value. The maximum value of 8 characters is to store the encrypted password in the MIB.
Minimum - 6 characters Maximum - 8 characters
Continued
68P02901W17-S
2-205 Dec 2009
BSS User Security Management parameters
Table 2-52
Chapter 2: Configuring BSS Features
BSS User Security Management parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
Values
fieldeng3_pass
This parameter is a computed field, hence the default value cannot be stated. This has to be taken care of by the cutover or clean install script while doing the MIB upgrade which invokes the encryption algorithm to compute the value. The maximum value of 8 characters is to store the encrypted password in the MIB.
Minimum - 6 characters Maximum - 8 characters
fieldeng4_pass
This parameter is a computed field, hence the default value cannot be stated. This has to be taken care of by the cutover or clean install script while doing the MIB upgrade which invokes the encryption algorithm to compute the value. The maximum value of 8 characters is to store the encrypted password in the MIB.
Minimum - 6 characters Maximum - 8 characters
ne_banner
This parameter specifies the NE usage policy for users and is provided by the NE to the user at the time of lmt login with both fieldengX account and normal user account. The default message is as follows: “This network element is protected by the Motorola BSS security feature. Access by unauthorized persons is prohibited and all users are verified. For further information, contact the OMC-R systems administrator.”
Minimum - 1 character Maximum - 255 characters
Continued
2-206
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration through a local maintenance terminal using the login command
Table 2-52
Logging in to the BSS
BSS User Security Management parameters (Continued)
OMC-R GUI field name/BSS parameter name
Description
FieldEng2Chg
This parameter is used to specify the date when the fieldeng2 password was changed. The range and default values of this field cannot be specified as this is inserted by the OMC-R when the fieldeng2 passwords are changed. Also, this parameter is not visible on the GUI.
FieldEng3Chg
This parameter is used to specify the date when the fieldeng3 password was changed. The range and default values of this field cannot be specified as this is inserted by the OMC-R when the fieldeng3 passwords are changed. Also, this parameter is not visible on the GUI.
FieldEng4Chg
This parameter is used to specify the date when the fieldeng4 password was changed. The range and default values of this field cannot be specified as this is inserted by the OMC-R when the fieldeng4 passwords are changed. Also, this parameter is not visible on the GUI.
NEAccessLevel
This parameter specifies the NE command access level for the user.
Values
Minimum - 1 Maximum - 4 Default is 4 (For omcadmin user and non omcadmin users)
Logging in to the BSS through a local maintenance terminal using the login command This feature introduces a new command called login. This command is used when logging in to a BSS through a local maintenance terminal (for example: a laptop connected to the master GPROC). It is used to authenticate the user and assign the user the appropriate command access level.
68P02901W17-S
2-207 Dec 2009
verify_field_pass and .field_pass utilities
Chapter 2: Configuring BSS Features
This command requires the user to login using either a UNIX account (the same account used to login to the OMC-R) or a field engineer account (fieldeng2, fieldeng3 or fieldeng4). The login requested depends on the status of the OML and the setting of the fieldeng_always_enabled parameter. By default it is possible to login using either account.
Example MMI-RAM 0115 -> login [BANNER TEXT] Please input your UNIX account or Field Engineer account information Login:
user1
Password:
********
COMMAND ACCEPTED A user is provided three opportunities to enter the correct username and password. If the user enters incorrect information thrice in succession, the user is blocked from logging in for 10 minutes. This block applies only to the board to which the user is currently connected.
verify_field_pass and .field_pass utilities The BSS user security feature introduces two new OMC-R scripts to support the checking of field engineer accounts. •
The utility verify_field_pass authenticates the field engineer account passwords. This utility accepts the field engineer user name and password, and compares this with the encrypted field engineer user stored in MIB. This utility has execute permission for all users.
•
The utility .field_pass displays all the field engineering passwords in plain text. It has execute permission only for the omcadmin user and is stored as a hidden file.
Both these utilities are located in the /usr/omc/current/bin directory on the OMC-R.
2-208
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Setting fieldeng_always_enabled parameter
Setting fieldeng_always_enabled parameter
Figure 2-4
BSS Detailed View
The BSS Detailed View and RXCDR Detailed View are updated to display a new BSS parameter fieldeng_always_enabled. The CMMIB supports a new parameter fieldeng_always_enabled for both BSS and RXCDR class which is used to specify whether the fieldengX accounts at the NE (BSS / RXCDR) are used only when the OML link is down or under all the scenarios, that is, irrespective of whether the OML link is up or down. The new parameter fielding_always_enabled is displayed on OMC-R BSS/RXCDR DV with the name Field Engineer Always Enabled.
68P02901W17-S
2-209 Dec 2009
Password management and banner text management
Procedure 2-4
Chapter 2: Configuring BSS Features
Setting fieldeng_always_enabled parameter
1
Set the parameter fieldeng_always_enabled to 0 (FALSE) to enable the field engineer user accounts to be used only when the OML link is down.
2
Set the parameter fieldeng_always_enabled to 1 (TRUE) to enable the field engineer user accounts to be used when the OML link is up or down.
Password management and banner text management
NOTE The Admin Options window is updated with two new options NE Field Engineer Password Management and NE Banner Text Management. Figure 2-5 displays the Admin Options window.
2-210
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Figure 2-5
Password management and banner text management
Admin options window
Setting the field engineering password The NE Field Engineer Password Management window is used to change the Field Engineer password for all the NEs connected to the OMC-R.
NOTE The omcadmin user and users with omcadmin privileges can invoke the NE Field Engineer Password Management window.
Procedure 2-5
Setting the field engineering password
1
Login to the OMC-R GUI server as omcadmin user.
2
Click the Admin Option on the main OMC-R GUI front panel. The Admin Options window is displayed, as shown in Figure 2-5. Continued
68P02901W17-S
2-211 Dec 2009
Password management and banner text management
Procedure 2-5
Chapter 2: Configuring BSS Features
Setting the field engineering password (Continued)
3
Click the option NE Field Engineering Password Management to display the NE Field Engineering Password Management window.
4
Select Edit à Edit from the menu.
5
Click the Checkboxes and enter the values for the following parameters: Fieldeng2 Password, Fieldeng2 Password Confirm Fieldeng3 Password, Fieldeng3 Password Confirm Fieldeng4 Password, Fieldeng4 Password Confirm.
6
Select File à Propagate to propagate all fieldengX passwords across the network.
NOTE This option is grayed out when the NE Field Engineer Password Management window is in the Monitor mode.
Select Propagate to Failed to propagate the field engineering passwords to all those NEs to which the password propagation has failed in the previous attempt. This option can be enabled only when the NE Field Engineer Password Management window is in the Monitor mode. Run Propagate to Failed in the Monitor mode if any of the previous propagation attempts have failed. 7
Select File à Close to close the NE Field Engineer Password Management window without propagating the changes to fieldengX passwords across the network. This option is enabled both in the Monitor and Edit state of the window. The following warning dialog is displayed if the user tries to close the window after editing but without propagating the changes: “There have been changes since you last saved. Exit without saving changes?”
8
Select OK and close the NE Field Engineer Password Management window.
9
Select Xterm from the OMC-R GUI to launch an Xterm.
10
At the Xterm command prompt, enter the following command: /usr/omc/current/bin/verify_field_pass fieldeng2 Enter Password: ***********
11
Enter the password for the Fieldeng2 user which was entered in step 5.
12
Verify that the authentication is successful, confirming that the password was updated successfully in the MIB.
13
Repeat step 10 to step 12 for each field engineering account.
14
At the Xterm command prompt, enter the following command: /usr/omc/current/bin/.field_pass
15
Enter the omcadmin password when prompted. The tool display the field engineering passwords stored at the MIB. Verify that they match the passwords entered in step 5.
NOTE Performing step 10 to step 15 ensures that the passwords are updated at the NE.
2-212
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Figure 2-6
Password management and banner text management
NE Field Engineer Password Management status dialog
NE Banner Text Management Window When the user logs into NE, NE provides a banner text containing a brief outline of the NE usage policy and legal matters that are relevant to NE usage. The NE banner text can be customized at the OMC-R. The NE Banner Text Management GUI is used to update the Banner Text, and to synchronize with all the NEs connected to the OMC-R.
NOTE The omcadmin user and users with omcadmin privileges can invoke the NE Banner Text Management window.
Procedure 2-6
NE Banner Text Management
1
Login into the OMC-R system processor as omcadmin user on the GUI server.
2
Click the Admin Option on the main OMC-R GUI front panel. Continued
68P02901W17-S
2-213 Dec 2009
Password management and banner text management
Procedure 2-6
Chapter 2: Configuring BSS Features
NE Banner Text Management (Continued)
3
In the Admin Options window, click the option NE Banner Text Management and verify that the following text is displayed in the NE Banner Text Management Window: “This Network Element is protected by the Motorola BSS Security Feature. Access by unauthorized persons is prohibited and all users will be verified. For further information contact the OMC-R Systems Administrator”.
4
Select Edit à Edit and enter the text for the NE_banner parameter.
5
Select File à Propagate to propagate the banner text across the network and to store the banner text in the MIB.
NOTE This option is grayed out when the NE Banner Text Management window is in the Monitor mode and it is enabled in the Edit mode.
Select Propagate to Failed to propagate the currently set banner text to all those NEs to which the Banner Text propagation has failed in the previous attempt. This option is enabled only when the NE Banner Text Management window is in the Monitor mode. Run Propagate to Failed in the Monitor mode if any of the previous propagation attempts have failed.
2-214
6
Select File à Close. A warning dialog is displayed if the user tries to close the window after editing but without propagating the changes: “There have been changes since you last saved. Exit without saving changes?”
7
Select OK and close the NE banner text management window.
8
Login to the BSS/XCDR locally from a laptop or through the qcomm application from the qcomm server as a normal user or field engineer and verify that the displayed text is the same text as in step 3.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Quality of Service Phase II
Quality of Service Phase II ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{27703A}
Overview Quality of Service (QoS) architecture aims at providing a framework for differentiation of services and users for GPRS/EGPRS and UMTS. The key components of GSR9 QoS implementation are as follows: •
Add support for Streaming Traffic class
•
Max bit-rate enforcement as per the QoS Profile
•
Capacity is based on a less conservative budget
Support for Streaming Traffic Class allows the operator to specify a service requiring constraints on delay and jitter as well as minimum bit rate. Support for PFCs requesting streaming traffic class can be enabled/disabled using the streaming_enabled BSS parameter. If support for streaming traffic class is disabled, BSS tries to admit the streaming traffic classes as one of the matching interactive traffic classes (determined based on the MTBR settings). Guaranteed Bit Rate as per the 3GPP specification is defined as the guaranteed number of bits delivered at a SAP within a period of time (provided that there is data to deliver), divided by the duration of the period. For the GPRS RAN, the guaranteed bit rate is defined as the bit rate at the LLC layer. GSR8 QoS introduced the internal BSS concept of an MTBR (minimum throughput budget requirement) associated with each PFC. The Guaranteed Bit Rate for each PFC is an extension of this concept except that the GBR needs to be enforced as a true guarantee and not just a commitment. The MTBR is measured as the raw air throughput at the RLC/MAC layer whereas the GBR measurements exclude any RLC retransmissions. Transfer Delay (definition as per 23.107) indicates maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a bearer service, where delay for an SDU is defined as the time from a request to transfer an SDU at one SAP to its delivery at the other SAP. Transfer delay of an arbitrary SDU is not meaningful for a bursty source (applicable only to real-time traffic classes – streaming/conversational). In addition, the transfer delay for Radio Access Bearer may be smaller than the overall requested transfer delay, as transport through the core network uses a part of the acceptable delay. Transfer delay as all other attributes in the Aggregate BSS QoS Profile is negotiable. GSR9 QoS is based on the GSR8 implementation and all the PFCs for a given user share the same TBF over the air interface to transfer data for the PFCs. GSR9 enhances the LLC scheduling within the same TBF such that the real-time service is prioritized appropriately over the non real-time services where necessary but at the RLC layer, all PFCs for the mobile still share the same pipe. GSR9 streaming support is limited to at most one active real-time PFC per user at any given time.
68P02901W17-S
2-215 Dec 2009
Quality of Service Phase II parameters
Chapter 2: Configuring BSS Features
Maximum Bit Rate enforcement allows the BSS to throttle the throughput of user to the max bit rate stated in the QoS parameters (ABQP) even if there is a capacity to provide the user a higher throughput. The key requirement here is to modify the scheduling algorithms to enforce Max-bit rate as per the negotiated QoS profile. The main purpose of maximum bit rate enforcement from an operator’s perspective is to limit the delivered bit rate to applications or external networks and to allow maximum required/permitted bit rate to be defined for applications able to operate with different rates. The Maximum bit rate applies to all traffic classes.
Quality of Service Phase II parameters Table 2-53 details the Quality of Service Phase II parameters. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
Table 2-53
Quality of Service Phase II parameters
OMC-R GUI field name/BSS parameter name streaming_enabled
Description
Values
The parameter streaming_enabled provides streaming support per BSS when enabled and if the operator disables the parameter, then the support for all streaming traffic classes, all existing streaming/conversational PFCs are deleted by the BSS. Future streaming/conversational users are downgraded and mapped to an appropriate interactive traffic class using rules described in GSR8 QoS.
0 - 1 Default is 0 0 - Disabled 1 - Enabled
NOTE This attribute can only be modified if Qos Phase II is enabled/unrestricted at the OMC. Continued
2-216
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-53
Quality of Service Phase II parameters
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name qos_mbr_enabled
Description
Values
The parameter qos_mbr_enabled enables or disables support of Max Bit Rate or Peak Bit Rate enforcement on a per BSS basis. When this parameter is enabled, the throughput of all the subscribers in this BSS is limited by the Maximum Bit Rate defined in HLR.
0 - 1 Default is 0 0 - Disabled 1 - Enabled
NOTE This attribute can only be modified if Qos Phase II is enabled/unrestricted at the OMC. stream_downgrade_ enabled
The parameter stream_downgrade_enabled enables or disables the downgrading of GBR and Transfer Delay of an admitted PFC during future retention procedures to a lower value than was initially committed. Any changes to this parameter only affect future retention procedures. This parameter controls the negotiation of GBR, TD, MaxSDUsize, besides RT-nRT downgrade.
0 - 1 Default is 1 0 - Not allowed to set the GBR to a lower value than committed 1 - Allowed to set the GBR to a lower value than committed
NOTE This attribute can only be modified if Qos Phase II is enabled/unrestricted at the OMC. thp_stream_weight
The parameter thp_stream_weight specifies the THP weight of the streaming traffic class. The thp_stream_weight is restricted by the QoS Phase 2 feature. When streaming_enabled parameter is equal to 1, this attribute cannot be changed.
10 - 40 Default is 40 All values in the range of 10 - 40 are valid, the higher the value, the more precedence it is given.
Continued
68P02901W17-S
2-217 Dec 2009
Quality of Service Phase II parameters
Table 2-53
Chapter 2: Configuring BSS Features
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name mtbr_downgrade_enabled
Description
Values
The parameter mtbr_downgrade_enabled enables or disables downgrading the MTBR of an admitted PFC during future retention procedures to a lower value than was initially committed.
0 - 1 Default is 1 0 - Not allowed to set the MTBR to a lower value than committed 1 - Allowed to set the MTBR to a lower value than committed.
NOTE This attribute can only be modified if Qos is enabled/unrestricted at the OMC. pfm_sig_enabled
The parameter pfm_sig_enabled enables or disables support of PFC modification signaling to SGSN when there is downgrade or upgrade for non-real time PFC on a per BSS basis.
NOTE This attribute can only be modified if Qos is enabled/unrestricted at the OMC.
0 - 1 Default is 1 0 - No PFC modification message sent to SGSN when there is an upgrade or downgrade for non real-time PFC. 1 - PFC modification message is sent to SGSN when there is an upgrade or downgrade for non real-time PFC. Continued
2-218
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-53
Quality of Service Phase II parameters
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name arp_streaming_1
Description
Values
The parameter arp_streaming_1 specifies the Allocation and Retention Priority (ARP) value of streaming traffic class, precedence class 1. The OMC-R interprets the decimal value into decimal value of four parts: qa, priority level/arp value, pci, and pvi according to ARP IE structure. This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN. The value of this attribute is converted to binary and the bits are interpreted as follows to obtain the pci, pvi and the priority level/arp value: 8 - spare 7 - pci 6,5,4,3 - priority level 2 - qa 1 - pvi The value of qa bit is not used in GSR9.
4 - 123 Default is 68 (pci - 1, priority level - 1, pvi - 0) All values in the range of 4 - 123 except 60, 61, 62, 63, 64, 65, 66 and 67 are valid.
NOTE This item can only be modified if the QoS Phase 2 feature is unrestricted. The priority level value of arp_streaming_1 must be less than or equal to those of arp_streaming_2 and arp_streaming_3. The OMC-R supports a message string in the status bar of the BSS DV when attribute arp_streaming_1, is modified. The message displays the pci, pvi and priority level based on the value entered in the BSS DV. Continued
68P02901W17-S
2-219 Dec 2009
Quality of Service Phase II parameters
Table 2-53
Chapter 2: Configuring BSS Features
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name arp_streaming_2
Description
Values
The parameter arp_streaming_2 specifies the allocation and retention Priority (ARP) value of streaming traffic class, precedence class 2. The OMC-R interprets the decimal value into a decimal value of four parts: qa, priority level/arp value, pci, and pvi according to ARP IE structure. This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN. The value of qa bit is not used in GSR9.
4 - 123 Default is 73 (pci - 1, priority level - 7, pvi - 0) All values in the range of 4 - 123 except 60, 61, 62, 63, 64, 65, 66 and 67 are valid.
NOTE This item can only be modified if the QoS Phase 2 feature is unrestricted.
The priority level value of arp_streaming_2 must be less than or equal to that of arp_streaming_3 and greater than or equal to that of arp_streaming_1. The OMC-R supports a message string in the status bar of the BSS DV when attribute arp_streaming_2, is modified. The message displays the pci, pvi, and priority level based on the value entered in the BSS DV. Continued
2-220
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-53
Quality of Service Phase II parameters
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name arp_streaming_3
Description
Values
The parameter arp_streaming_3 specifies the allocation and retention Priority (ARP) value of streaming traffic class, precedence class 3. The OMC-R interprets the decimal value into decimal value of four parts: qa, priority level/arp value, pci and pvi according to ARP IE structure. This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN.
4 - 123 Default is 77 (pci - 0, priority level - 14, pvi - 1) All values in the range of 4 - 123 except 60, 61, 62, 63, 64, 65, 66 and 67 are valid.
NOTE This item can only be modified if the QoS Phase 2 feature is unrestricted. The priority level value of arp_streaming_3 must be greater than or equal to those of arp_streaming_1 and arp_streaming_2. The OMC-R supports a message string in the status bar of the BSS DV when the attribute arp_streaming_3, is modified. The message displays the pci, pvi and priority level based on the value entered in the BSS DV. Continued
68P02901W17-S
2-221 Dec 2009
Quality of Service Phase II parameters
Table 2-53
Chapter 2: Configuring BSS Features
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name arp_i_be_1
Description
Values
The parameter arp_i_be_1 specifies the Allocation and Retention Priority (ARP) value of Interactive or Best Effort traffic class, precedence class 1. The OMC-R interprets the decimal value into a decimal value of four parts: qa, priority level/arp value, pci, and pvi according to ARP IE structure. This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN.
4 - 123 Default is 93 (pci - 1, priority level - 1, pvi - 0) All values in the range of 4 - 123 except 60, 61, 62, 63, 64, 65, 66 and 67 are valid.
NOTE This item can only be modified if the QoS feature is unrestricted. The priority level value of arp_i_be_1 must be less than or equal to those of arp_i_be_2 and arp_i_be_3. The OMC-R supports a message string in the status bar of the BSS DV when the attribute arp_i_be_1, is modified. The message displays the pci, pvi, and priority level based on the value entered in the BSS DV. Continued
2-222
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-53
Quality of Service Phase II parameters
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name arp_i_be_2
Description
Values
The parameter arp_i_be_2 specifies the Allocation and Retention Priority (ARP) value of Interactive or Best Effort traffic class, precedence class 2. The OMC-R interprets the decimal value into a decimal value of four parts: qa, priority level/arp value, pci and pvi according to ARP IE structure. This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN.
4 - 123 Default is 97 (pci - 1, priority level - 7, pvi - 1) All values in the range of 4 - 123 except 60, 61, 62, 63, 64, 65, 66 and 67 are valid.
NOTE This item can only be modified if the QoS feature is unrestricted. The priority level value of arp_i_be_2 must be less than or equal to that of arp_i_be_3 and greater than or equal to that of arp_i_be_1. The OMC-R supports a message string in the status bar of the BSS DV when attribute arp_i_be_2, is modified. The message displays the pci, pvi and priority level based on the value entered in the BSS DV. Continued
68P02901W17-S
2-223 Dec 2009
Quality of Service Phase II parameters
Table 2-53
Chapter 2: Configuring BSS Features
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name arp_i_be_3
Description
Values
The parameter arp_i_be_3 specifies the Allocation and Retention Priority (ARP) value of Interactive or Best Effort traffic class, precedence class 3. The OMC-R interprets the decimal value into a decimal value of four parts: qa, priority level/arp value, pci and pvi according to ARP IE structure. This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN.
4 - 123 Default is 101 (pci - 0, priority level - 14, pvi - 1) All values in the range of 4 - 123 except 60, 61, 62, 63, 64, 65, 66 and 67 are valid.
NOTE This item can only be modified if the QoS feature is unrestricted. The priority level value of arp_i_be_3 must be greater than or equal to those of arp_i_be_1 and arp_i_be_2. The OMC-R supports a message string in the status bar of the BSS DV when attribute arp_i_be_3, is modified. The message displays the pci, pvi and priority level based on the value entered in the BSS DV. Continued
2-224
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-53
Quality of Service Phase II parameters
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name arp_bg_1
Description
Values
The parameter arp_bg_1 specifies the Allocation and Retention Priority (ARP) value of Background traffic class, precedence class 1. The OMC-R interprets the decimal value into decimal value of four parts: qa, priority level/arp value, pci and pvi according to ARP IE structure. This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN.
4 - 123 Default is 49 (pci - 1, priority level - 1, pvi - 0) All values in the range of 4 - 123 except 60, 61, 62, 63, 64, 65, 66 and 67 are valid.
NOTE This item can only be modified if the QoS feature is unrestricted. The priority level value of arp_bg_1 must be less than or equal to those of arp_bg_2 and arp_bg_3. The OMC-R supports a message string in the status bar of the BSS DV when attribute arp_bg_1, is modified. The message displays the pci, pvi and priority level based on the value entered in the BSS DV. Continued
68P02901W17-S
2-225 Dec 2009
Quality of Service Phase II parameters
Table 2-53
Chapter 2: Configuring BSS Features
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name arp_bg_2
Description
Values
The parameter arp_bg_2 specifies the Allocation and Retention Priority (ARP) value of Background class, precedence class 2. The OMC-R interprets the decimal value into a decimal value of four parts: qa, priority level/arp value, pci and pvi according to ARP IE structure. This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN.
4 - 123 Default is 53 (pci - 1, priority level - 7, pvi - 1) All values in the range of 4 - 123 except 60, 61, 62, 63, 64, 65, 66 and 67 are valid.
NOTE This item can only be modified if the QoS feature is unrestricted. The priority level value of arp_bg_2 must be less than or equal to that of arp_bg_3 and greater than or equal to that of arp_bg_1. The OMC-R supports a message string in the status bar of the BSS DV when attribute arp_bg_2, is modified. The message displays the pci, pvi and priority level based on the value entered in the BSS DV. Continued
2-226
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-53
Quality of Service Phase II parameters
Quality of Service Phase II parameters (Continued)
OMC-R GUI field name/BSS parameter name arp_bg_3
Description
Values
The parameter arp_bg_3 specifies the Allocation and Retention Priority (ARP) value of Background traffic class, precedence class 3. The OMC-R interprets the decimal value into decimal value of four parts: qa, priority level/arp value, pci and pvi according to ARP IE structure. This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN.
4 - 123 Default is 57 (pci - 0, priority level - 14, pvi - 1) All values in the range of 4 - 123 except 60, 61, 62, 63, 64, 65, 66 and 67 are valid.
NOTE This item can only be modified if the QoS feature is unrestricted. The priority level value of arp_bg_3 must be greater than or equal to those of arp_bg_1 and arp_bg_2. The OMC-R supports a message string in the status bar of the BSS DV when attribute arp_bg_3, is modified. The message displays the pci, pvi and priority level based on the value entered in the BSS DV.
68P02901W17-S
2-227 Dec 2009
CTU2-D
Chapter 2: Configuring BSS Features
CTU2-D ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{30828}
Description With the introduction of the CTU2-D feature, the new CTU2-D radios can support both SD and DD EDGE architectures, in addition to the various modes supported by the legacy CTU2 radios. According to the CTU2, Carrier A/B definitions and nomenclature also apply to CTU2-D. The following are the different Edge modes that the CTU2-D radio supports: •
CTU2D SD This mode is identical in operation to the existing CTU2 SD and is only included for reference.
•
CTU2D PWR This mode is also known as ITS Mode whereby the CTU2 and CTU2D operations are identical. Of the two carriers, if the TS on carrier A is supporting an EDGE TS, then the corresponding TS on carrier B is blanked, that is, it does not support anything. Carrier B TS is capable of supporting only TCH or GPRS PDs while the corresponding TS on carrier A does not have an EDGE TS. The maximum output power of both carriers whether in GMSK or 8PSK mode is 20 W* as shown in Figure 2-7.
Figure 2-7
•
CTU2D PWR mode
CTU2D CAP Of the two carriers, carrier A is fully EDGE-capable, while carrier B supports GPRS/TCH. TS blanking is not required. The maximum output power of carrier A in 8PSK mode is 10 W* and GMSK mode is 20 W*. The maximum output power carrier B (GMSK only) is always 20 W* as shown in Figure 2-8.
2-228
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Figure 2-8
•
CTU2-D dependencies
CTU2D CAP mode
{30830} CTU2D ASYM Of the two carriers, carrier A is fully EDGE-capable, while carrier B supports EDGE on the DL and GMSK (EDGE) on the UL. The maximum output power of carrier A in 8PSK mode is 10 W* and GMSK mode is 20 W*. The maximum output power of carrier B in GMSK mode is 20 W*, as shown in Figure 2-9.
Figure 2-9
CTU2D ASYM mode
NOTE * The output powers listed are for 900 MHz frequency. For all other frequencies, the output power may vary. The capacity of the overall BSS remains unchanged. However, due to the elimination of timeslot blanking in DD mode, the capacity of the radio in DD CAP and ASYM mode increases.
CTU2-D dependencies •
CTU2-D is supported on Horizon II macro, Horizon II mini, and Horizon II micro sites only. When the master cabinets are Horizon II macro and Horizon II mini, the extension H2 cabinets support CTU2-D; legacy Mcell and H1 extension cabinets do not support CTU2-D and remain OOS.
•
The CTU2-D capacity feature requires EGPRS to be unrestricted.
•
The CTU2-D asymmetric operation requires both EGPRS and capacity feature to be unrestricted.
•
For the asymmetric mode to be operational, asym_edge_enabled should be enabled and dri_density should be set to Capacity mode.
68P02901W17-S
2-229 Dec 2009
CTU2-D parameters
Chapter 2: Configuring BSS Features
CTU2-D parameters Table 2-54 details the parameters associated with the CTU2-D feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, refer to Technical Description: BSS Command Reference (68P02901W23).
Table 2-54
CTU2-D parameters
OMC-R GUI field name/BSS parameter name
Description
Values
ctu2dcapOpt
The ctu2dcapOpt parameter indicates whether the CTU2-D Capacity feature is restricted or unrestricted in the BSS. The CTU2-D capacity feature requires the EGPRS feature to be unrestricted.
0 - 1 0 - Disabled 1 - Enabled
{30830} ctu2dasymOpt
The ctu2dasymOpt parameter indicates whether the CTU2-D Asymmetric EDGE feature is restricted/unrestricted in the BSS. The Asymmetric EDGE feature requires the EGPRS feature and the CTU2-D Capacity feature to be unrestricted.
0 - 1 0 - Disabled 1 - Enabled
The asym_edge_enabled parameter enables or disables the Asymmetric EDGE feature available on the CTU2-D hardware on a per-SITE basis. Changing this parameter requires the site to be reset manually for the change to take effect. This is a type 1 parameter. The OMC-R displays a message to the operator to reset the SITE. This attribute can only be enabled at sites where the master SITE cabinet is a member of the H2 family (Horizon II macro, Horizon II mini and Horizon II micro).
0 to 1 Default is 0. 0 - Asymmetric EDGE is disabled. 1 - Asymmetric EDGE is enabled.
SITE parameter {30830} asym_edge_enabled
2-230
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Interaction with other features
Interaction with other features This feature interacts with the following: •
Quality of Service Phase II
•
CTU2 Debug and Diagnostics
•
Improved Timeslot Sharing
•
VersaTRAU
•
Four branch Diversity
68P02901W17-S
2-231 Dec 2009
Cell OOS Timer Enhancement
Chapter 2: Configuring BSS Features
Cell OOS Timer Enhancement ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{32340}
Description This feature introduces an operator configurable delay to postpone the system information update message for SIs 1, 2, 2bis, 3 and 4 to the MS when the BSC is undergoing reset during master BSP failover (BRM feature). This delays the MS cell reselection procedure during global reset. This feature is designed to extend the amount of time that the mobile remains on the network which is undergoing a reset procedure. This enables operators to maintain roaming subscribers and reduce revenue loss. Call processing at the BSS is responsible for the delay of system information update message to the mobile while the BSS is undergoing reset. OM is responsible for providing the mechanism to configure the value of the delay.
Cell OOS Timer Enhancement parameters Table 2-55 details the parameters associated with Cell OOS Timer Enhancement. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
Table 2-55
Cell OOS Timer Enhancement parameters
OMC-R GUI field name/BSS parameter name cell_barred_delay
2-232
Description
Values
The BSS parameter cell_barred_delay specifies how long the BSS delays sending SystemInformationUpdate message to the MS during the global reset procedure. This element can be updated both in or out of sysgen mode.
0 - 180 seconds. Default is 0.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
TDM Availability Enhancements
TDM Availability Enhancements ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{25002}
Overview This feature increases the availability of the system by enhancing the existing fault recovery and detection mechanism of the TDM buses in the BSC. These enhancements also apply to the RXCDR. Previously, operator intervention was required to initiate certain types of TDM swap which resulted in a long service outage. Modification to the hardware fault management (HWFM) of the KSW/DSW2 Expansion matrix was carried out to ensure that the TDM highways are handled properly. Currently, upon detecting a fault in the active Expansion Matrix with a Redundant Expansion Matrix equipped, the fault manager maintains call processing but does not initiate a TDM swap. The system waits for the OMC to command a swap to the redundant TDM bus and associated expansion matrix. There are two parts to the modified behavior. The first part causes the system to automatically swap to the redundant TDM highway upon detection of a fault. The second allows for an automatic daily swap to the redundant highway.
TDM Availability Enhancements parameters Table 2-56 details the parameters associated with TDM Availability Enhancements. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
Table 2-56
TDM Availability Enhancements parameters
OMC-R GUI field name/BSS parameter name tdm_switch
68P02901W17-S
Description
Values
A switch is added to the OMC in order to control the TDM Availability Enhancements feature. When the switch is open, the feature is activated. When the switch is closed, the feature is disabled. The switch is denoted by the parameter tdm_switch. The definition of the values is based on the states of the switch.
0 - Close 1 - Open Default is 0.
2-233 Dec 2009
TD-SCDMA and GSM interworking
Chapter 2: Configuring BSS Features
TD-SCDMA and GSM interworking ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{31400}
Overview This feature supports intersystem cell reselection between TD-SCDMA and GSM/GPRS in order that: •
Subscribers do not lose service when they reach the edge of TD-SCDMA coverage.
•
Subscribers gain the benefits of the more advanced TD-SCDMA system when they enter its coverage area.
This feature performs the following functions: •
Supports GSM/GPRS to TD-SCDMA cell reselection in circuit-switched idle mode and packet idle mode by broadcasting TD-SCDMA neighbor list and the corresponding 3G measurement parameters in SI2ter, SI2Quater.
•
Supports GSM/GPRS to TD-SCDMA cell reselection in packet transfer mode.
•
Supports TD-SCDMA to GSM/GPRS cell reselection.
•
Supports TD-SCDMA to GSM handover in circuit-switched dedicated mode.
TD-SCDMA and GSM interworking dependencies This feature is supported on Mcell, Horizon, and Horizon II platforms. Incell is not supported. The TD-SCDMA and GSM interworking feature requires: •
Multi-RAT mobile stations, which are capable of accessing the Core Network (CN) from a UMTS TD-SCDMA coverage area and a GSM coverage area. The MS must be capable of operating in either GSM or UMTS TD-SCDMA cells, including execution of procedures such as PLMN selection, cell reselection, measurements in idle mode and dedicated mode, and so on.
•
A UMTS network including 2G/3G compatible MSC.
•
Existing 2G CN nodes must be able to interact with the 3G CN nodes through MAP procedures defined on the E-interface between a 3G CN node and 2G CN node.
TD-SCDMA and GSM interworking parameters Table 2-57 details the parameters associated with TD-SCDMA and GSM interworking. Unless stated otherwise, the OMC-R parameter name is usually same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23). 2-234
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-57
TD-SCDMA and GSM interworking parameters
TD-SCDMA and GSM interworking parameters
OMC-R GUI field name/BSS parameter name
Description
Values
TD-SCDMA Inter-working Feature tdOpt
Displayed in the Optional Features grouping of the BSS Detailed View Form. This parameter indicates whether the TD-SCDMA interworking feature is restricted or unrestricted in the BSS. When tdOpt is restricted, attempts to add TD-SCDMA neighbor cell and modify/display TD-SCDMA measurement parameters are rejected.
0 - 1 0 - Restricted 1 - Unrestricted
TD-SCDMA Inter-working Enabled td_enabled
Displayed in the General grouping of the BSS Detailed View Form. This parameter allows the user to enable or disable the TD-SCDMA inter-working feature at the BSS level. When the TD-SCDMA inter-working feature (tdOpt) is restricted, this parameter cannot be modified. When InterRATOpt or EnhancedInterRatOpt feature is unrestricted, this parameter cannot be modified from 0 to 1. If tdOpt is unrestricted, this parameter is sent across the OMC-BSS interface. When the parameter is not 1, the user cannot add TD-SCDMA Neighbor.
0 - 1 0 - Off 1 - On Default is 0.
The offset for cell reselection to TD-SCDMA tdd_qoffset
Displayed in the General grouping of the CELL Detailed View Form. This parameter is used in the cell reselection algorithm followed by the MS for the UMTS TDD neighbor cell. When tdOpt is restricted, this parameter cannot be modified. If tdOpt is unrestricted, this parameter is sent across the OMC_BSS interface. This parameter applies an offset to RLA_C for cell reselection to access the TD-SCDMA mode. This is a configurable parameter.
0 - 15 where 0 = - ∞ 1 = - 28 dB 2 = - 24 dB ...... 15 = 28 dB Default is 8.
TD-SCDMA ARFCN tdd_arfcn
This parameter indicates the TD-SCDMA frequency. This is a Read-Write parameter of the UTRAN Neighbor Cell. When tdOpt is restricted, this parameter cannot be modified.
10054 - 10121
Continued
68P02901W17-S
2-235 Dec 2009
TD-SCDMA and GSM interworking parameters
Table 2-57
TD-SCDMA and GSM interworking parameters (Continued)
OMC-R GUI field name/BSS parameter name
2-236
Chapter 2: Configuring BSS Features
Description
Values
TD-SCDMA Cell Parameter tdd_cell_param
This parameter indicates the TD-SCDMA cell parameter. This is a Read-Write parameter of the UTRAN Neighbor Cell. When tdOpt is restricted, this parameter cannot be modified.
0 to 127
TD-SCDMA Time Switched Transmit Diversity Mode tdd_tstd_mode
This parameter indicates the TD-SCDMA Time Switched Transmit Diversity mode. This is a Read-Write parameter of the UTRAN Neighbor Cell. When tdOpt is restricted, this parameter cannot be modified.
0 to 1 0 - Disabled 1 - Enabled Default is 0.
TD-SCDMA Space Code Transmit Diversity Mode tdd_sctd_mode
This parameter indicates the TD-SCDMA cell diversity capability (Space Code Transmit Diversity). This is a Read-Write parameter of the UTRAN Neighbor Cell. When tdOpt is restricted, this parameter cannot be modified.
0 to 1 0 - Disabled 1 - Enabled Default is 0.
BCCH RF Signal Level Threshold qsearch_i
Refer to Inter-RAT Handover and Enhanced Inter-RAT Handover parameters on page 2-94 for further details.
Use BCCH RF Signal Level Threshold qsearch_c_initial
Refer to Inter-RAT Handover and Enhanced Inter-RAT Handover parameters on page 2-94 for further details.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Extended Uplink TBF (Temporary Block Flow)
Extended Uplink TBF (Temporary Block Flow) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{26881}
Overview The Extended Uplink TBF feature enhances uplink/downlink data performance by minimizing the interruptions of uplink data flow in GPRS/EGPRS networks due to frequent release and establishment of uplink TBF. The uplink TBF is maintained during temporary inactive periods, when the mobile station has no RLC information to send. The network determines the release of the uplink TBF. The network continues to allocate USFs for the mobile station during the period of inactivity. The mobile station sends Uplink Dummy Control Blocks if indicated or RLC data blocks when new RLC data blocks become available. This feature requires the GPRS Feature to be unrestricted.
Extended Uplink TBF (Temporary Block Flow) parameters Table 2-58 details the parameters associated with the Extended Uplink TBF (Temporary Block Flow) feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, refer to Technical Description: BSS Command Reference (68P02901W23).
OMC-R GUI field name/BSS parameter name extuplinkOpt
Description
Values
The extuplinkOpt parameter indicates whether or not the Extended Uplink TBF feature functionality is unrestricted in the BSS software. If the extuplinkOpt flag indicates that extended uplink TBF feature is restricted, attempts to change extended uplink TBF specific database parameters are rejected.
OMC-R GUI field name/BSS parameter name ext_ul_dur
Description
Values
The ext_ul_dur parameter indicates the maximum duration in block periods (1 bp = 20 ms) for which uplink TBF operates in extended mode without receiving any new real RLC data block. When the extended uplink feature is unrestricted 0 indicates that the extended uplink feature is disabled. By default the extended uplink feature is disabled. When the feature is unrestricted, the range 24 to 250 represents the possible values for ext_ul_duration and selecting any value in this range enables the feature. This parameter changes inside and outside of SYSGEN mode.
0, 24 to 250 Default is 0.
The ext_utbf_nodata parameter indicates to the mobile station during extended uplink TBF mode whether or not to send any PACKET UPLINK DUMMY CONTROL BLOCK message when there is no other RLC/MAC block ready to send for this TBF. It is broadcasted to the MS in (PACKET) SYSTEM INFORMATION message. This element cannot be modified if the Extended Uplink TBF feature is restricted. This element is modified in or out of SYSGEN mode.
0 to 1 Default is 0. 0 - The mobile station sends a PACKET UPLINK DUMMY CONTROL BLOCK during extended uplink mode. 1 - The mobile station refrains from sending a PACKET UPLINK DUMMY CONTROL BLOCK during extended uplink mode.
Cell parameters ext_utbf_nodata
Interaction with other features Extended Dynamic Allocation Medium Access Mode (EDMAC) {23292} on Block Scheduling algorithm during extended uplink TBF mode for EDMAC mobiles.
2-238
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Extended Dynamic Allocation Medium Access Mode (EDMAC)
Extended Dynamic Allocation Medium Access Mode (EDMAC) ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{23292}
Overview This is an optional feature for the network. It is an enhancement of the Dynamic Allocation Medium Access Mode (DA). In EDMAC mode, the mobile station monitors its assigned PDCHs starting with the lowest numbered PDCH, then the next lowest numbered PDCH, and so on. Whenever the mobile station detects an assigned Uplink Status Flag (USF) value on an assigned PDCH, the mobile station transmits a single RLC/MAC block on the same PDCH and all higher numbered assigned PDCHs. When a class 11 or 12 mobile requests an uplink TBF, the network assigns the EDMAC for the uplink TBF if the mobile supports EDMAC and the TBF allocation requires EDMAC mode. The network assigns the lowest numbered timeslot in the allocation as PACCH timeslot. The PCU attempts to assign the maximum possible number of UL timeslots (3 for class 11 and 4 for class 12) to the mobile if gprs_ul_dl_bias is set to UL bias. During the uplink TBF in EDMAC, the network schedules USFs in the lowest timeslot in the allocation, and the mobile station transmits a single RLC/MAC block on the same PDCH and all higher numbered assigned PDCHs. The PCU schedules periodic PUAKs for 3 or 4 UL TBFs frequent enough to prevent stalling dependent on the number of uplink timeslots (3 or 4) used and GPRS or EGPRS TBF mode. This feature requires the GPRS feature to be unrestricted.
Extended Dynamic Allocation Medium Access Mode (EDMAC) parameters Table 2-59 details the parameters associated with the Extended Dynamic Allocation Medium Access Mode (EDMAC) feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, refer to Technical Description: BSS Command Reference (68P02901W23).
Table 2-59
Extended Dynamic Allocation Medium Access Mode (EDMAC) parameters
OMC-R GUI field name/BSS parameter name edaOpt
68P02901W17-S
Description
Values
This parameter indicates whether or not the Extended Dynamic Allocation feature functionality is unrestricted in BSS software.
0 to 1 Default is 0 0 - restricted 1 - unrestricted
2-239 Dec 2009
Interaction with other features
Chapter 2: Configuring BSS Features
Interaction with other features This feature interacts with the following: •
2-240
Extended Uplink TBF {26881}
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Adjustable FER Bins
Adjustable FER Bins ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{29693A}
Overview This feature modifies the Frame Erasure Rate (FER) bins and the measurement period calculation. It provides adjustable bins for all the FER counters so that all the thresholds are shared, and can be configured by the user. It also introduces a method to calculate the measurement period of the FER, by tracing the number of SACCH multiframes.
Adjustable FER Bins parameters Table 2-60details the parameters associated with Adjustable FER Bins. Unless stated otherwise, the OMC-R parameter name is same as the BSS parameter name. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
Table 2-60
Adjustable FER Bins parameters
OMC-R GUI field name/BSS parameter name fer_meas_period
68P02901W17-S
Description
Values
The parameter fer_meas_period is displayed in the BSS Detailed View. This parameter allows the customer to configure the FER measuring period. The value indicates the multiple of 24 speech frames that is used as the measuring period of FER family statistics.
0 - Disabled Use 24 speech frames as the measuring period of FER family statistics. 1 to 255 - The multiple of 24 speech frames that is used as the measuring period of FER family statistics.
2-241 Dec 2009
Critical Statistics Reporting in 5 minutes
Chapter 2: Configuring BSS Features
Critical Statistics Reporting in 5 minutes ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{34164}
Overview While carrying out system performance optimization, the user can tune system parameters in 5 minutes, once the parameter takes effect. Earlier, the user had to wait for at least one statistics interval to obtain system performance measurements to make an adjustment in the next interval. After the second interval, they could observe the adjustment results. With this feature, the interval can be reduced to 5 minutes. The user can check the status of the following top 6 customer prioritized statistics: 1.
Number of discarded CS paging messages per cell.
2.
Number of paging received from MSC per cell.
3.
Number of unsuccessful full rate and half rate allocations of a TCH within a cell for both call origination and hand-in.
4.
The number of times that an attempt at SDCCH seizure was rejected because of SDCCH congestion.
5.
Number of Short Message Service (SMS) transactions that occurred on a cell.
6.
Total number of calls originated for each cell on the BSS.
When the system performance is stable and optimization is complete, this feature can be disabled.
Critical Statistics Reporting in 5 minutes parameters Table 2-61details the parameters associated with Critical Statistics Reporting in 5 minutes. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
2-242
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-61
Critical Statistics Reporting in 5 minutes parameters
Critical Statistics Reporting in 5 minutes parameters
OMC-R GUI field name/BSS parameter name
Description
_bss_data,1
This parameter enables or disables the function of statistics uploading in a 5 minute interval. This parameter can be accessed/updated both in and out of sysgen mode.
_cell_data,21
This parameter enables or disables the function of statistics uploading in a 5 minute interval for each cell. If it has a different value from _bss_data,1, the BSS level parameter has higher priority. This parameter can only be accessed/updated out of sysgen mode.
68P02901W17-S
Values 0 to 1. Default is 0. 0 - Disable the function of statistics uploading in a 5 minute interval. 1 - Enable the function of statistics uploading in a 5 minute interval. 0 to 1. Default is 0. 0 - Disable the function of statistics uploading in a 5 minute interval for the cell. 1 - Enable the function of statistics uploading in a 5 minute interval for the cell.
2-243 Dec 2009
SW enabler for PA bias switch on/off on CTU2D
Chapter 2: Configuring BSS Features
SW enabler for PA bias switch on/off on CTU2D ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{34320G}
Overview The new CTU2D-CPI radio hardware has the capability to turn off the bias to a Power Amplifier (PA) for individual idle Time Slots (TS) that are not occupied for any traffic. This is known as PA Bias on/off capability. This feature provides software capability to control (enable/disable) the PA bias on/off. This feature is applicable only where the master SITE cabinet is a member of the Horizon II family, that is, Horizon II macro, Horizon II mini and Horizon II micro. This is an optional feature based on customer requirement and can be enabled or disabled using the OMC-R. Two obsolete parameters are reused in this feature. The parameter BSC_BTS_DYNAMIC_ALLOCATION is reused as Pw_Save_SwitchOpt, and the parameter dynet_retry_time is reused as power_save_enable.
NOTE The parameters BSC_BTS_DYNAMIC_ALLOCATION and dynet_retry_time are obsolete in GSR8 and GSR9. Due to GSR9 MIT modification restriction, the OMC-R reuses these parameters.
Enabling and disabling the SW enabler for PA bias switch on/off on CTU2D feature The OMC-R GUI provides the interface to enable or disable the feature and in the CM, supports the sending of these messages to BSS. In the GUI, this feature can be enabled or disabled only if the Pw_Save_SwitchOpt is unrestricted. Also the CMMib ensures that the enable/disable information is sent to the BSS only if Pw_Save_SwitchOpt is unrestricted.
SW enabler for PA bias switch on/off on CTU2D parameters Table 2-62 details the parameters associated with SW enabler for PA bias switch on/off on CTU2D feature. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
2-244
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-62
Operability impacts
SW enabler for PA bias switch on/off on CTU2D parameters
OMC-R GUI field name/BSS parameter name
Description
Values
SW enabler PA bias switch on/off on CTU2D Pw_Save_SwitchOpt
This attribute describes whether this feature is restricted or unrestricted at the BSS. It is displayed on the BSS Detailed View on the GUI.
0 to 1 0 - disabled 1 - enabled
power save enable power_save_enable
This parameter enables or disables this feature. Enabling/disabling this parameter is acknowledged by a message at the OMC event management window. The OMC-R displays a message to the Operator if it receives an out of range value in a Create/Set operation.
0 to 1 Default is 0 0 - disabled 1 - enabled
Operability impacts BSCBTSDynAllocOpt and dynet_retry_time have dependencies with another attribute ts_sharing. The attribute ts_sharing is made insensitive if the BSS version is greater or equal to 1900. This ensures that the customer inadvertently does not set the values of ts_sharing.
68P02901W17-S
2-245 Dec 2009
Dual Abis aware BTS
Chapter 2: Configuring BSS Features
Dual Abis aware BTS ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{34303}
Overview The Dual Abis aware BTS feature supports the BSC6 (RSR) program.
NOTE BSC6 and Abis functionality is beyond the scope of GSR10 documentation and is described in the RSR documentation. This feature enables Horizon and Horizon II base stations to detect the Standard Abis interface used by the BSC6, in addition to the existing Mobis interface used by the BSC2. It allows migration (or large scale migration) from a current BSC2 to a new BSC6 (or from a BSC6 to a BSC2) to be implemented with minimum downtime. The following BTSs can be migrated to a BSC6: •
Horizon I macro
•
Horizon II macro
•
Horizon II micro
•
Horizon II mini
This feature requires the dual boot functionality delivered in the BSC6 program to enable the BTS to establish the Abis-OML connection, and to download the full Abis load from the BSC6 and then work under that BSC6. The disp_option command displays this feature option at the BSS.
Dual Abis aware BTS parameters Table 2-63 details the parameters associated with the Dual Abis aware BTS feature. For further details of these and other parameters, refer to Technical Description: BSS Command Reference (68P02901W23).
2-246
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-63
68P02901W17-S
Dual Abis aware BTS parameters
Dual Abis aware BTS parameters
BSS parameter name
Description
_site_data, 5
This element enables or disables the Horizon I or Horizon II BTS to connect to the Abis interface. For other BTS types, this element is always set to 0.
Values 0 to 2. Default is 0. 0 = Abis_Disable 1 = Abis_Enable_Conv 2 = Abis_Enable_CSFP
2-247 Dec 2009
Extended Range Cell (ERC) for Data
Chapter 2: Configuring BSS Features
Extended Range Cell (ERC) for Data ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{23311A}
Overview This feature allows a much larger diameter of cell sites in areas where there is not much traffic, thereby reducing equipment needs in sparsely populated areas. A normal GSM/ GPRS cell has a coverage of 35 km radius. An extended range GSM cell can cover up to 121 km radius. In the normal range, the maximum timing advance value of a mobile can only go up to 63 bits. To accommodate the additional propagation delay in the extended range, an extended range timeslot needs to support a timing advance value of up to 219 bits. An extended range timeslot is created by coupling two regular TDMA timeslots to support the extended timing advance. Only the even numbered timeslot in an extended range pair is operational over the air. GPRS/EGPRS channel type (PDCH) can also be supported on an extended timeslot. A mobile in extended range can only be allocated on an extended PDCH, while a mobile in normal range can be allocated on normal PDCH and/or extended PDCH. In this feature, the extended timeslot can also be configured as GPRS/EGPRS channel type (that is, 16K/32K/64K PDCH) for ERC data. In order to support EGPRS service for mobile in extended range, extended timeslot can be supported on 64K RTF. Both extended PDCH and extended TCH can be configured on the extended timeslot of 64K RTF. This feature is configured on a per cell basis, and can be configured with extended PDCH only on one RTF per cell. If this feature is enabled, the BSC supports only synthesizer hopping in the cell. Baseband hopping is not supported. The BSC supports Extended Range Cell for Data only when the PCCCH feature and ASYM feature are disabled, and erc_range_cell is enabled. The BTS supports extended range PDCHs only on CTU-2 radios and CTU2D radios. This is an optional feature in GSR9. Table 2-64 details the parameters associated with the Extended Range Cell (ERC) for Data feature. Unless stated otherwise, the OMC-R parameter name is usually the same as the BSS parameter name. For further details of these and other parameters, refer to Technical Description: BSS Command Reference (68P02901W23).
2-248
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-64
Overview
Extended Range Cell (ERC) for Data parameters
OMC-R GUI field name/BSS parameter name
Description
Values
ext_pdchs
This element indicates the number of extended range PDCH supported by the RTF, and also indicates whether Extended Range Cell for Data feature is enabled or disabled. This parameter is valid only if ercgprsOpt is set to non-restricted.
0 to 4. Default is 0. 0 indicates an extended PDCH on this RTF is disabled, and extended PDCH number = 0. At the same time, 0 indicates ERC for Data feature is disabled. 1 indicates an extended PDCH on this RTF is enabled, and extended PDCH number = 1. 2 indicates an extended PDCH on this RTF is enabled, and extended PDCH number = 2. 3 indicates an extended PDCH on this RTF is enabled, and extended PDCH number = 3. 4 indicates an extended PDCH on this RTF is enabled, and extended PDCH number = 4. A value of 1,2,3, or 4 indicates that ERC for Data feature is enabled.
ercgprsOpt
This parameter indicates whether the Extended Range Cell (ERC) for Data feature is restricted or unrestricted.
0 to 1. 0 - Restricted. 1 - Unrestricted.
68P02901W17-S
2-249 Dec 2009
Cage Management
Chapter 2: Configuring BSS Features
Cage Management ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{34321}
Overview of Cage Management The Cage Management feature is a reliability and availability enhancement based on the existing GSR9 BSC/XCDR hardware and software platform. This enhancement allows isolation of non-master cages without causing a site reset and increases the availability by reducing service outage to partial outage. The RAN supports the BSC/XCDR cage management in taking a non-master cage and the possible child extension cage out of service manually or automatically by fatal fault detection. It keeps the remaining BSC/XCDR cages operational, and resumes the service of the OOS cages after maintenance operations.
NOTE The BSC/XCDR performs a BSC/XCDR reset when the master cage fails, or when both the active and the standby LAN fail. The OSS supports the Cage Management as a baseline feature.
Enabling and disabling the Cage Management feature The Cage Management feature can be enabled or disabled by the MMI command-line configuration, or Sysgen configuration script. The configuration is effective immediately after the operation and persistent throughout the lifecycle of the database. The BSC/XCDR disables the Cage Management feature by default for better control of the feature during deployment.
Cage Management parameters Table 2-65 details the parameters associated with Cage Management feature. For further details of these and other parameters, see Technical Description: BSS Command Reference (68P02901W23).
2-250
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 2-65
Operability impacts
Cage management parameters
OMC-R GUI field name/ BSS parameter name _bss_data,10
Description The per-BSS element _bss_data,10 allows the customer to enable or disable the functionality of the Cage Management feature. This element can be accessed and updated both in and out of sysgen mode. In GSR8 to GSR9 upgrade, the element _bss_data,10 is reused from GSR8, therefore an upgrade warning to set to GSR9 default value is prompted.
Values 0 to 1 Default is 0.
Operability impacts A BSC/XCDR resets if one of the following occurs: •
Fatal failure of a master cage causes a BSC/XCDR reset
•
When both the active and redundant LAN fail, it causes a BSC/XCDR reset.
•
If any cage is powered off, it causes a BSC/XCDR reset.
68P02901W17-S Dec 2009
2-251
Operability impacts
2-252
Chapter 2: Configuring BSS Features
68P02901W17-S Dec 2009
Chapter
3 Configuring Network, OMC-R, and MSC Instances ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The information here describes how to create Network, OMC-R, and MSC instances in the OMC-R GUI. The following topics are described: •
Configuring a network instance on page 3-2.
•
Configuring an OMC-R or MSC instance on page 3-7.
68P02901W17-S Dec 2009
3-1
Configuring a network instance
Chapter 3: Configuring Network, OMC-R, and MSC Instances
Configuring a network instance ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to configuring a network instance A network instance must be the first network object to be created in the OMC-R GUI Navigation Tree. It must be configured before a BSS can be configured. Only one Network instance should be configured for a GSM system. This section describes how to: •
Create a Network instance.
•
Delete a Network instance.
To modify a Network instance, see Modifying a network object using the OMC-R GUI on page 1-34.
Creating a Network instance using the OMC-R GUI To create a Network instance to the OMC-R Navigation Tree, use the following procedure:
Procedure 3-1
Create Network instance using OMC-R GUI
1
From the Front Panel, click the Config Mgt icon to display the Navigation Tree.
2
Select Edit à Create Network from the menu bar to open a new Network Detailed View.
NOTE If a Network instance has already been created, the Create Network menu option is not displayed. 3
Complete the fields as required. See Network Detailed View fields on page 3-3 for details. Continued
3-2
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Procedure 3-1 4
Network Detailed View fields
Create Network instance using OMC-R GUI (Continued)
Complete the Map Information section using the name selected for the network as it is required to appear on the relevant map. For the Name field, enter the name of the map where the network is to be placed. This will probably be a new map name, since a new network is being created. The Map label name is created by default to coincide with the name of the new network. Only input a name where there is a special requirement to do so. When a special background to a map is required, for example a geographical display, type the name of the file (without the .map extension) under which the background is stored.
NOTE A background display to a map is only possible where the relevant file has been defined and placed in the directory: /usr/omc/config/global/maps.
Where the map background is to be blank, or where no geographical backgrounds are available, allow the field to default to Empty. 5
Select File à Save from the menu bar to save the new configuration.
6
Select File à Close to close the Map Network Detailed View window.
7
Select File à Create from the menu bar.
8
Select File à Close from the menu bar to close the Network Detailed View.
Network Detailed View fields The following sections list and briefly describe the parameter fields in the Network Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
68P02901W17-S
3-3 Dec 2009
Network Detailed View fields
Chapter 3: Configuring Network, OMC-R, and MSC Instances
Identification grouping Table 3-1 details the fields in the Identification grouping of the Network Detailed View.
The instance identifier of the object. Together with the rdnClass, it makes up the Relative Distinguished Name (RDN) of an object. When the Environment Variable AUTO_GEN_RDN is set to On (default) (see Operating Information: OMC-R System Administration (68P02901W19) for further details), the RDN Instance field is automatically populated by the OMC-R with the next available RDN instance id when the following objects are created: BSS, RXCDR, AssocRXCDR, AssocBSC, SITE, Region, CELL, Neighbor, UtranNbr, RTF Group, RTF, DRI Group, DRI, SMSCBmsg, RSL, Cabinet, Cage, DHP, EAS, COMB, KSW, GCLK, MSI, Conn Link, PATH, XBL, PCU, PSP, GDS, GBL, GSL, OML, OMF, LCF, CBL, MTL, CSFP, TestNeighbour, DYNETGroup, DYNET, GPROC, BSP and BTP. The RDN Instance is not automatically populated for the following auto-created objects: IAS, KSWpair, LAN, TDM, TRX, FreqHopSys, Handover/Power Control algorithms. Neither is it auto-populated for a DPROC because the valid set for the DPROC RDN Instance is 1 to 6 or 11 to 16. There is no RDN Instance field for object NSVC. The RDN Instance field is auto-populated in sequential order. Although the RDN instance is created automatically by the OMC-R, a user can still type in a different valid RDN instance when creating the object, if required.
Default is 0.
Mandatory.
NMC Value
The OMC-R supports an interface to a Network Management Centre (NMC). This is the instance identifier of the object on the NMC interface.
Optional.
Additional Information Use the Additional Information window to input any notes relating to this Network. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
68P02901W17-S
3-5 Dec 2009
Deleting a Network instance
Chapter 3: Configuring Network, OMC-R, and MSC Instances
State grouping Table 3-2
Network Detailed View fields - State grouping Mandatory or Optional?
Field name
Brief description
Values
Time of Last Audit Gather Complete timeOfLastAuGather Complete
Shows the last time the Gather phase of a network Audit was completed.
Date and Time (ddmmyy hhmm).
Read-only.
Time of Last Audit Apply Complete timeOfLastAuApply Complete
Shows the last time the Apply phase of a network Audit was completed.
Date and Time (ddmmyy hhmm).
Read-only.
Map Information grouping Table 3-3 details the fields in the Map Information grouping of the Network Detailed View.
Table 3-3
Network Detailed View fields - Map Information grouping
Field name
Brief description
Default Map
When a Network is created, the OMC-R creates a default Network map. This is the object identifier of the default map. As each node (BSS, RXCDR, SITE, OMC, MSC) is created, appropriate map nodes are created on the Network's default map. In edit mode, click the button to display the Map Network Detailed View, which shows the Map Background setting.
Values
Mandatory or Optional? Optional.
Deleting a Network instance A Network instance can only be deleted if all its child instances have also been deleted. That is, BSSs, RXCDRs, OMC-Rs, MSCs and Commslinks must also have been deleted. Any attempt to delete a network containing any network elements is refused. To delete a Network instance, see Deleting a network object using the OMC-R GUI on page 1-37.
3-6
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring an OMC-R or MSC instance
Configuring an OMC-R or MSC instance ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to configuring an OMC-R or MSC instance An OMC instance must be configured before a BSS can be configured. This section describes how to: •
Create an OMC or MSC instance.
•
Delete an OMC or MSC instance.
To modify an OMC or MSC instance, see Modifying a network object using the OMC-R GUI on page 1-34.
Creating an OMC-R or MSC instance An OMC-R or MSC can only be created if a Network instance (that is, the parent) has already been created. To create an OMC-R or MSC instance, use the following procedure:
Procedure 3-2
Create an OMC-R or MSC instance
1
Navigate to and select the OMC-R or MSC class button. If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object class button changes color.
2
From the menu bar, select Edit à Create. The OMC-R or MSC Detailed View window in Create mode is displayed.
3
Complete the fields, as required. See OMC and MSC Detailed View fields on page 3-7 for further details.
4
Save and close the Detailed View as detailed in Creating a network object using the OMC-R GUI on page 1-32.
OMC and MSC Detailed View fields The following sections list and briefly describe the parameter fields in the OMC and MSC Detailed Views according to their parameter grouping.
68P02901W17-S
3-7 Dec 2009
OMC and MSC Detailed View fields
Chapter 3: Configuring Network, OMC-R, and MSC Instances
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
NOTE Without write permission on the fields, it is not possible to change any values in the Active fields. In this case, delete the OMC-R and recreate it in Edit mode.
Identification grouping Table 3-4 details the fields in the Identification grouping of the OMC and MSC Detailed Views.
Table 3-4
OMC and MSC Detailed View fields - Identification grouping
Field name Name
Active (OMC only)
Brief description
Values
Mandatory or Optional?
Unique OMC or MSC name.
Up to 31 characters plus the NULL character.
Mandatory.
Multiple OMCs can be created in the MIB, but only one represents the actual in-situ OMC. This is the active OMC where, for example, the SoftwareLoads will be installed. Select Yes if this is the first OMC-R. It is essential that the first OMC-R in a network is created with Active flag set at True, or software download is impossible. Subsequent OMC-Rs have to be created with Active flag set at False, as there can only be one active OMC-R in a network.
No (0) and Yes (1). Default is No (0)
Optional.
Continued
3-8
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 3-4
Deleting an OMC-R or MSC
OMC and MSC Detailed View fields - Identification grouping (Continued)
Field name
Brief description
Values
Mandatory or Optional?
Host name (OMC only)
Name of the UNIX host machine. Mainly used to support the ProxyCell synchronization feature for inter-OMC ProxyCell updates.
0 - 24
Mandatory.
RDN Class
See description in Table 3-1.
Default is OMC or MSC
Optional.
RDN Instance
See description in Table 3-1.
OMC is 0 - 50. MSC is 0 - 100. Default is 0.
Optional.
NMC RDN Value
See description in Table 3-1.
Optional.
Displays the name of the parent. Click to display the parent Network Detailed View.
Not applicable.
Parent Detail View
Additional Information Use the Additional Information window to input any notes relating to this OMC or MSC. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
State grouping Standard network object state fields, see Table 4-2 for details.
Map Information grouping Standard map information fields, see Table 4-15 for details.
Deleting an OMC-R or MSC An OMC-R or MSC must only be deleted after authorization has been obtained in advance from the OMC-R System Administrator. All software loads associated with the active OMC-R must be deleted before an OMC-R can be deleted. To delete an OMC-R or MSC, see Deleting a network object using the OMC-R GUI on page 1-37.
68P02901W17-S Dec 2009
3-9
Deleting an OMC-R or MSC
3-10
Chapter 3: Configuring Network, OMC-R, and MSC Instances
68P02901W17-S Dec 2009
Chapter
4 Configuring a BSS/RXCDR ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The procedures to be followed to configure a BSS and/or RXCDR are provided here. The following topics are described: •
Overview of adding a BSS or RXCDR on page 4-2.
•
Creating a BSS using the OMC-R GUI on page 4-6.
•
Creating an RXCDR using the OMC-R GUI on page 4-39.
•
MSC to BSS overload control on page 2-22.
•
Deleting a BSS/RXCDR on page 4-44.
•
Reparenting a BSS on page 4-101.
•
Equipping cabinets and cages at a BSS site on page 4-51.
•
Configuring an RXCDR cabinet on page 4-62.
•
Configuring an Assoc_BSS on page 4-69.
•
Configuring an Assoc_RXCDR on page 4-73.
•
Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR on page 4-81.
•
Configuring DYNETs and DYNETGroups on page 4-91.
•
Configuring a DYNETGroup on page 4-93.
•
Configuring a DYNET on page 4-95.
•
Reparenting a BSS on page 4-101.
•
Reparenting an RXCDR to a different MSC on page 4-107.
68P02901W17-S Dec 2009
4-1
Overview of adding a BSS or RXCDR
Chapter 4: Configuring a BSS/RXCDR
Overview of adding a BSS or RXCDR ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to adding a BSS/RXCDR This section provides a high-level overview of all the procedures required to add a BSS or RXCDR to a network. The information should be used as an initial explanation, and later as a quick reference guide.
Prerequisites for adding BSS/RXCDR Prerequisites at BSS Before adding a BSS, check that: •
The BSC hardware has been installed and commissioned.
•
Physical links exist between BSC and ING 6525 packet switch, 6250 MUX, or 6560 MPRouter.
•
Physical links exist between OMC-R and ING 6525 packet switch, 6250 MUX, or 6560 MPRouter.
•
The BSS has valid DTE addresses (BSS address is set and OMC-R DTE addresses point to the appropriate OMC-R). Refer to Assigning DTE X.121 addresses at the NE on page 5-19.
•
The BSC has had its software load and NE database object LAN loaded. This is confirmed if the database object has been uploaded to the OMC-R, immediately after the BSS has been created at the OMC-R.
Prerequisites at the OMC-R Before adding a BSS, check the following at the OMC-R:
4-2
•
The network, OMC-R, and MSC objects are already added to the Navigation Tree. Refer to Chapter 3 Configuring Network, OMC-R, and MSC Instances for details.
•
Ensure that the software load for running the BSS has been installed on the OMC-R. Refer to OMC-R Online Help, Network Operations.
•
If the BSS is not already operational (software load and NE database object not LAN loaded) and requires a code download, ensure that the NE database object is available to be loaded and activated once the BSS has been created. Ensure that the database version matches the required software load version. Refer to OMC-R Online Help, Network Operations.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Overview procedure for adding BSS/RXCDR to the network
Overview procedure for adding BSS/RXCDR to the network To add a BSS/RXCDR to the network, follow this overall procedure:
Procedure 4-1
68P02901W17-S
Add BSS/RXCDR to the network
1
Create the BSS or RXCDR. Refer to Creating a BSS using the OMC-R GUI on page 4-6 and Creating an RXCDR using the OMC-R GUI on page 4-39. If the BSS already contains a load and database, and has its X.25 connections and OML properly configured, the BSS will be able to connect to the OMC-R once the BSS object has been created in the MIB.
2
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.
3
If the alarm exists, cycle the X.25 port on the packet switch/MUX and check if the OML comes into service. If this works, the alarm clears and the BSS begins sending events and statistics files to the OMC-R.
4
If the alarm has not cleared, configure the packet switch/MUX. Refer to . The red X.25 link failure alarm clears, when the OML connects to the OMC-R.
5
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.
6
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.
7
Rlogin to the BSS, see Remotely logging in to a BSS site from the OMC-R on page 1-39. If the BSS name appears, and the rlogin is successful, then NE.MAP has been configured properly.
4-3 Dec 2009
Overview procedure for adding BSS/RXCDR to the network
Chapter 4: Configuring a BSS/RXCDR
Performing an audit Now an audit should be performed for the BSS/RXCDR. To perform the audit follow these steps:
Procedure 4-2
Perform an audit for the BSS/RXCDR
1
Initiate an audit of the BSS/RXCDR, using Audit Scheduler from the Admin icon on the GUI front panel. Create a new Audit for the new BSS, using One-shot/Apply to OMC-R. See Introduction to auditing on page 10-2 for further details.
2
Once the audit is completed, verify that the destination point code and originating point code are set correctly. Otherwise the BSS is unable to communicate properly with the MSC. Use the BSS Detailed View Signaling Information grouping to check.
3
Verify all SITEs and cells have been audited properly.
Verifying information Verify the BSS/RXCDR settings using the following procedure:
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.
NOTE At the OMC-R, if PM_HOURLY_STATS environment variable is not set for the system processor, then the default collection interval is 30 minutes. Access is by: cd/usr/omc/config/global grep PM_HOURLY_STATS * 2
If necessary, change the SITE names. Refer to Reparenting a BSS on page 4-101.
3
Verify that all SITEs under the BSC have come into service, using the TTY command: state 0 site * *
NOTE Some sites may be dummy sites, and may be D-U or D-L.
4-4
4
Verify that the raw statistics files are being uploaded for the BSS, using the Event window to monitor for filetransferCompletedEvents. Refer to OMC-R Online Help, Network Operations for further details.
5
Verify that the PM reports are available for the BSS. Refer to OMC-R Online Help, Network Operations for further details.
6
If necessary, edit the appropriate subscription lists to add the new BSS to them. Refer to OMC-R Online Help, Network Operations for further details.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Overview procedure for adding BSS/RXCDR to the network
Configuring connectivity The next stage is to configure connectivity. Configure BSS to RXCDR connectivity. From Network Operator System Engineering Drawings, identify the RXCDRs connecting to the BSS. Create the RXCDR - Associated BSS objects, filling in the appropriate 2 Mbit/s link information.
Checking the maps Use the following procedure to check the maps:
Procedure 4-4
Check maps
1
If using the Map feature, when a new BSS/RXCDR is added, a new default map is created for the BSS/RXCDR. The NEs are incorrectly positioned on this new default map. Before storing the updated MIB data in backup files, select the new BSS from the map list and then select Organize Nodes menu option to reposition the BTSs. Then move the nodes to required positions on the map background. Refer to OMC-R Online Help, Network Operations for a description of how to move the NEs on a map.
2
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.
3
If using the Map feature, add Commslinks from the BSS to devices such as RXCDRs, OMC-R and MSC, so that they are displayed on the map. Refer to Adding and deleting a map link on page 13-11 in Chapter 13.
4
If using the Map feature, add the BSS to any customized regional maps.
Making backups The final stage is to make backups. Store the following updated MIB data in backup files: •
BSS object.
•
NE Software object.
•
SITE names.
•
All Map data.
•
Updated RXCDR connectivity information.
68P02901W17-S
4-5 Dec 2009
Creating a BSS using the OMC-R GUI
Chapter 4: Configuring a BSS/RXCDR
Creating a BSS using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to creating a BSS using OMC-R GUI The BSS object class in the OMC-R GUI is used to hold BSS-wide information within the BSS. This section describes how to create and modify a BSS using the OMC-R GUI.
Prerequisites to creating a BSS A BSS should be created in the OMC-R GUI before physically connecting it to the OMC-R. It can only be created if a Network (that is, the parent) has been defined in advance. Before creating a BSS, Commslinks from it to devices such as RXCDRs, OMC-R and MSC should have been created.
NOTE A BSS that supports the GPRS feature can only be created if the gprsOpt parameter is unrestricted.
4-6
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Creating a BSS using the OMC-R GUI
Creating a BSS using the OMC-R GUI To create a BSS using the OMC-R GUI, use the following procedure:
Procedure 4-5
Create BSS using OMC-R GUI
1
Navigate to and select the BSS class button in the Navigation Tree. If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The BSS class button changes color.
2
From the menu bar, select Edit à Create. The OMC-R displays the initial BSS Detailed View in Create mode, see Figure 4-1.
3
Click the Initial Software Load button to display a Software Inventory Dialog window.
4
Double-click one of the software loads displayed to select it and enter it in the initial BSS Detailed View.
5
{25423} Click the Initial Patch Level button to display the Initial Patch Level Details Dialog window.
NOTE The initial patch level is set to the default patch level if there is a patch object contained in the software load selected. Otherwise 0 is displayed. 6
{25423} Double-click one of the patch levels displayed to select it and enter it in the initial BSS Detailed View.
NOTE The initial patch level can only be selected if there is a patch object contained in the software load.
68P02901W17-S
7
Select Options à Initialize Form from the BSS Detailed View menu bar. The OMC-R displays the complete BSS Detailed View window.
8
Complete the fields in the Detailed View as required. See BSS Detailed View fields for details.
9
Select File à Create from the menu bar.
10
Select File à Close from the menu bar to close the Detailed View.
BSS Detailed View fields The following sections list and briefly describe the parameter fields in the BSS Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
4-8
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
BSS Detailed View fields
Identification grouping Table 4-1 describes the fields in the Identification grouping of the BSS Detailed View.
Automatically set to the next available network element identifier. See Dynamic Allocation of RXCDR-BSC Circuits (DARBC) on page 2-12 for details.
1 - 254
Mandatory.
NMC RDN Value
The OMC-R supports an interface to a Network Management Centre (NMC). This is the instance identifier of the object on the NMC interface.
4 - 11 digits.
Optional.
Parent Detailed View
Click to display the parent Network Detailed View.
OMC/NE Load Version
Version number of the software load active in the Network Element.
OMC/NE Load Version Create Time
Date and time at which the current NE load was created.
Mandatory.
Initial Software Load
Initial Software Load installed when NE was created.
Mandatory.
Local Maintenance local_maintenance
Can be set to Yes to warn operators that the BSS is out of service. See Recommendations for Configuration Management on page 1-2 for further information on how to set this parameter.
Yes (1) or No (0). Default is Yes (1).
Mandatory.
BSC Configuration Type bsc_type
The BSC configuration type. This attribute has no function at an RXCDR.
1 - 3. 1 = Non-Abis, Type 1. 2 = Non-Abis, Type 2 3 = Abis, Type 0. Default is Non-Abis, Type 0 (0)
Field name/BSS parameter name Transcoding local_transcoding
Brief description
Values
Whether transcoding is performed locally at the BSC, or remotely at one or more RXCDR. See Dynamic Allocation of RXCDR-BSC Circuits (DARBC) on page 2-12 for details.
Local (1) or Remote (0). Default is 0.
Mandatory or Optional? Mandatory.
Additional information Use the Additional Information window to input any notes relating to this BSS. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
State grouping The OMC-R updates the state parameter fields and shows the current status of the object. A user cannot update any of the fields in this section. When an object is being created, these fields are not up-to-date. Only when an object has been created, does the OMC-R keep these fields up-to-date. Table 4-2 describes the fields in the State grouping of the BSS Detailed View.
The OMC-R's first and second Event Virtual Circuit X.121 address stored in the Network Element's Non Volatile RAM. Only necessary to complete the first OMC-R X.121 Event Address 1 (always nnnnnnnn03) to create the NE. The rest of the DTE addresses are set through Audit.
The OMC-R's Remote Login Virtual Circuit X.121 address stored in the Network Element's Non Volatile RAM.
0 - 14 characters
Mandatory.
OMC X.121 Upload Address
The OMC's Upload Virtual Circuit X.121 address stored in the Network Element's Non Volatile RAM.
0 - 14 characters
Mandatory.
OMC X.121 Spare Address (two fields)
The OMC-R's Spare Virtual Circuit X.121 address stored in the Network Element's Non Volatile RAM.
0 - 14 characters
Mandatory.
CBC X.121 Address
Cell Broadcast Center (CBC) X.121 address.
0 - 14 characters
Mandatory.
BSC CBC X.121 Address bsc_cbc
X.121 address at the BSC used to communicate with the Cell Broadcast Center (CBC).
0 - 14 characters
Mandatory.
Optional Features grouping Table 4-4 shows the fields in the Optional Features grouping. These fields show whether an optional BSS feature is unrestricted (Enabled (1)) or restricted (Disabled (0)). All fields are Read Only (RO) and cannot be modified by a user.
Table 4-4
BSS Detailed View fields - Optional Features grouping
Field name/OMC-R parameter name
Brief description
Frequency Hopping Baseband Feature basebandHopOpt
See Frequency hopping on page 2-3 for details.
Concentric Cells Feature concentricCellOpt
Affects the ability of the system to process a request to configure Concentric Cells.
See Preventive Cyclic Retransmission (PCR) on page 2-54 for details. If disabled, the BSS parameters pcr_enable, pcr_n1, pcr_n2 cannot be used.
Daisy Chaining Feature daisyChainOpt
If this feature is restricted, the creation of non-spoke PATH instance is not allowed.
Receiver Spatial Diversity Feature diversityOpt
If this feature is unrestricted (enabled), the DRI diversity_flag can be used (see Table 9-17).
Extended GSM 900 Feature egsmOpt
If this feature is unrestricted (enabled), the CELL parameter egsm_ho_thresh can be used (see Table 8-18). Continued
4-12
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 4-4
BSS Detailed View fields
BSS Detailed View fields - Optional Features grouping (Continued)
Field name/OMC-R parameter name
Brief description
Extended Range Cell Feature ercOpt
If this feature is unrestricted (enabled), the CELL parameter ext_range_cell can be used (see Table 8-2).
A and Um Interface - GSM Phase 2 Feature gsmPhase2Opt
System Information: GSM Overview (68P02901W01) for a
Whether the A and Um Interface feature is restricted. See description of this feature. Also see Table 4-7 for related BSS parameters.
GSM Half Rate gsmHalfRateOpt
See GSM Half Rate on page 2-138 for details.
Heterogeneous Cabinet Feature heteroCabFreqOpt
Whether the Heterogeneous Cabinet Feature is restricted. Cannot be enabled without homoCabFreqType also being enabled.
Homogeneous Cabinet Feature homoCabFreqOpt
Whether the Homogeneous Cabinet Frequency Type is restricted.
MultiBand Inter-Cell H/O Feature mbInterCellHoOpt
See Configuring enhanced SDCCH to TCH band assignment on page 8-196 and Configuring a cell for coincident multiband handovers on page 8-179 for details. Also see Table 8-10 CELL Detailed View Congestion Relief parameter grouping.
MicroCell Feature microcellOpt
Whether the Microcell feature is restricted. See Table 8-28, Table 8-47 and Table 8-48 for associated parameters.
Multiple Encryption Feature multiEncryptOpt
Whether the Multiple Encryption feature is restricted. See Table 4-6 for related parameters. Also see Encryption algorithms on page 2-25 and Technical Description: BSS Implementation (68P02901W36) for details of this feature.
Add Nail Connections Feature nailConnectsOpt
Whether the Add Nail Connections feature is restricted. See
Technical Description: BSS Implementation (68P02901W36) for details of this feature.
Reserved Timeslot Feature resTimeslotOpt
Whether the Reserved Timeslot feature is restricted. See
Technical Description: BSS Implementation (68P02901W36) for details of this feature.
Sub-equipped RTF Feature rtf_capacityOpt
Whether the Sub-equipped RTF feature is restricted. See
Technical Description: BSS Implementation (68P02901W36) for details of this feature.
Whether the RTF PATH Fault Containment feature is restricted. See Technical Description: BSS Implementation (68P02901W36) for details of this feature.
16 kbit/s LAPD RSL Feature rsl_rateOpt
Whether the 16 kbit/s LAPD RSL RTF feature is restricted. See Technical Description: BSS Implementation (68P02901W36) for details of this feature.
Alternative Congestion Relief Feature congestReliefOpt
Whether the Alternative Congestion Relief feature is restricted. See Table 8-10 and Table 8-49 for details of the Cell and Neighbor Detailed View fields associated with this feature. Also see System Information: GSM Overview (68P02901W01) for a description of this feature. Continued
68P02901W17-S
4-13 Dec 2009
BSS Detailed View fields
Table 4-4
Chapter 4: Configuring a BSS/RXCDR
BSS Detailed View fields - Optional Features grouping (Continued)
Field name/OMC-R parameter name
Brief description
Directed Retry Feature directedRetryOpt
Whether the Directed Retry feature is restricted. See Table 4-11, Table 8-11 and Table 8-49 for details of the BSS, cell, and neighbor parameters associated with this feature. Also see Technical Description: BSS Implementation (68P02901W36) for details of this feature.
SMS Cell Broadcast Feature smsCellBroadOpt
See Short Message Service - Cell Broadcast on page 2-43 for details.
SMS Point to Point Feature smsPntToPntOpt
See Short Message Service - Point-To-Point on page 2-51 for details.
Frequency Hopping Synthesizer Feature synthHoppingOpt
See Frequency hopping on page 2-3 for details.
SMS Service Centre Feature smsServCenterOpt
Whether the SMS Service Centre feature is restricted. Affects the ability of the system to process a request to equip/create a CBL.
Aggregate Abis Feature aggAbisOpt
Whether the Aggregate Abis feature is restricted. If this attribute is enabled, the link attributes in the Path Managed Object between a BSC and a BTS can have a TS-Switching site. See Technical Description: BSS Implementation (68P02901W36) for details of this feature.
Integrated M-Cell HDSL Feature hdslOpt
Whether Integrated M-Cell HDSL feature is restricted. See site Detailed View HDSL Information grouping, and Table 9-47 for detailed of the site and MSI fields associated with this feature. See Technical Description: BSS Implementation (68P02901W36) for details of this feature.
GPRS Feature gprsOpt
Whether GPRS feature is restricted. See the GPRS parameter groupings of the BSS, Cell, and site Detailed Views for detailed of the associated parameters. Also see System Information: GSM Overview (68P02901W01) for a description of this feature.
EGPRS Feature egprsOpt
Whether EGPRS feature is restricted. See GPRS and EGPRS coding schemes on page 2-38 for details of configuring EGPRS Coding Schemes. See the GPRS parameter groupings of the BSS, Cell and site Detailed Views for detailed of the associated parameters. Also see System Information: GSM Overview (68P02901W01) for a description of this feature.
Dual Band Cells Option dualBandCellOpt
See Dual band cells option on page 2-27 for details.
See Network Controlled Cell Reselection on page 2-79 for details.
Coding Scheme 3 and 4 cs34Opt
See GPRS and EGPRS coding schemes on page 2-38 for details.
Enhanced BSC Feature ebscOpt
See Enhanced BSC Capacity on page 2-92 for details.
Enhanced One Phase Access Feature eopOpt
See Enhanced GPRS One Phase Access on page 2-111 for details.
Inter-RAT Handover Feature InterRatOpt
See Inter-Radio Access Technology (Inter-RAT) Handover on page 2-93 for details. Whenever EnhncdInterRatOpt is set to 1, InterRatOpt is also set to 1.
XBL 16 kbit/s LAPD Feature xbl_rateOpt
Whether the XBL 16 kbit/s LAPD feature is restricted. See Table 9-68 for details of the XBL parameters associated with this feature.
PBCCH/PCCCH Feature
See PBCCH/PCCCH feature on page 2-115 for details.
Enhanced Full Rate Feature EFROpt
Whether the Enhanced Full Rate feature is restricted. See Table 4-13 for the associated parameters. Also see Technical Description: BSS Implementation (68P02901W36) for details of this feature.
GDP Volume Control Feature gdpVolContOpt
Whether the GDP Volume Control feature is restricted. Determines whether the BSS and Assoc_BSS parameter volume_control_type can be used (see Table 4-7 and Table 4-30). Also see Technical Description: BSS Implementation (68P02901W36) for details of this feature.
Fast GCLK Warm Up Feature FastWarmGclkOpt
Whether the Fast GCLK Warm Up feature is restricted. Determines whether the site parameter gclk_qwarm_flag can be used (see Table 7-5).
Location Services Feature lcsOpt
See GSM location services on page 2-102 for details.
GPRS Trace Feature gprsTraceOpt
Whether the GPRS Trace feature is enabled or disabled. See OMC-R Online Help, Network Operations for details of this feature.
AMR Feature amrOpt
See Adaptive Multi-Rate (AMR) on page 2-127 for details.
AMR Enhanced GDP Feature amrEGDPProOpt
See Adaptive Multi-Rate (AMR) on page 2-127 for details. Grayed-out if the AMR Feature (amrOpt) is restricted (Disabled). Continued
68P02901W17-S
4-15 Dec 2009
BSS Detailed View fields
Table 4-4
Chapter 4: Configuring a BSS/RXCDR
BSS Detailed View fields - Optional Features grouping (Continued)
Field name/OMC-R parameter name
4-16
Brief description
AMR Enhanced Capacity Feature amrEnhancedCapOpt
See Adaptive Multi-Rate (AMR) on page 2-127 for details.
AMR TCU-A Feature amrTCUAOpt
See Adaptive Multi-Rate (AMR) on page 2-127 for details.
AMR TCU-B Feature amrTCUBOpt
See Configuring a network instance on page 3-2 for details.
GPRS Seamless Cell Reselection Feature scrOpt
See GPRS Seamless Cell Reselection on page 2-140 for details.
See Enhanced Scheduling on page 2-144 for details. This feature can only be enabled if GPRS is enabled.
Intelligent Multilayer Feature imrmOpt
Whether the Intelligent Multilayer Resource Management feature is restricted. See Intelligent Multilayer Resource Management (IMRM) on page 2-148 for further details.
Fast Call Service Feature FastCallOpt
Whether the Fast Call Service feature is restricted or unrestricted. See Fast Call Setup on page 2-171 for further details.
Enhanced Inter RAT Handover Feature EnhancedInterRatOpt
Where the Enhanced Inter RAT Handover feature has been restricted. Whenever EnhncdInterRatOpt is set to 1, InterRatOpt is also set to 1. See Enhanced Inter-RAT Handover feature on page 2-94 for further details.
Network Assisted Cell Change Feature naccOpt
Whether the Network Assisted Cell Change feature is restricted (disabled) or unrestricted (enabled). See Network Assisted Cell Change (NACC) on page 2-165 for further details.
EMLPP Feature enhancedMLPPOpt
Whether the Enhanced Multi-Level Precedence and Preemption (eMLPP) is restricted or unrestricted for the BSS. See Enhanced Multi-level Precedence and Pre-emption (eMLPP) on page 2-168 for further details.
Quality of Service qosOpt
Whether Quality of Service feature is restricted or unrestricted. See Quality of Service (QoS) on page 2-157 for further details.
VersaTRAU Feature versaTrauOpt
Displays whether the VersaTRAU feature is restricted (Disabled (0)) or unrestricted (Enabled (1)). See VersaTRAU on page 2-175 for further details.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
BSS Detailed View fields
Signaling Information grouping Table 4-5 describes the fields in the Signaling Information grouping of the BSS Detailed View.
Table 4-5
BSS Detailed View fields - Signaling Information grouping
Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
Establishes a method of differentiation between international and national messages.
0 - 3. International Network (0), Spare (for international use only) (1), National Network (2), Reserved for national use (3). Default is 2.
Mandatory.
Originating Point Code
0 - 16777215. 0 - 16777215, if ss7_mode is ANSI SS7. 0 - 16383, if ss7_mode is not ANSI SS7.
Mandatory.
Destination Point Code
0 - 16777215. 0 - 16777215, if ss7_mode is ANSI SS7. 0 - 16383, if ss7_mode is not ANSI SS7.
Mandatory.
Network Indicator Code
Called Point Code Included
Whether point code is included (enabled) in called party (call receiver) address in the SCCP messages.
Disabled (0) or Enabled (1).
Mandatory.
Calling PCI
Whether point code is included in calling party (call originator) address in the SCCP messages.
Disabled (0) or Enabled (1).
Mandatory.
Connection Request Calling
Whether calling party address is included in the SCCP message Connection Request.
Disabled (0) or Enabled (1). Default is 0.
Mandatory.
Continued
68P02901W17-S
4-17 Dec 2009
BSS Detailed View fields
Table 4-5
Chapter 4: Configuring a BSS/RXCDR
BSS Detailed View fields - Signaling Information grouping (Continued)
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-54 for further details.
Disabled (0) or Enabled (1). Default is 0.
Preventative Cyclic Retransmission N1 pcr_n1
See Preventive Cyclic Retransmission (PCR) on page 2-54 for further details.
Mandatory.
Preventative Cyclic Retransmission N2 pcr_n2
See Preventive Cyclic Retransmission (PCR) on page 2-54 for further details.
Mandatory.
SCCP BSSAP Management Flag
When enabled, detects Signaling Point Inaccessible, and loss of BSSAP subsystem, and handles the following messages: User Part Unavailable (UPU), Subsystem prohibited (SSP), Subsystem Allowed (SSA), and Subsystem Test (SST). When disabled, the BSS responds to an SST with an SSA message.
SS7 Mode ss7_mode
Indicates which SS7 definition is supported.
BSSAP Subsystem Number
Mandatory.
Disabled (0) or Enabled (1). Default is 0.
Mandatory.
SS7 defined by CCITT (0) or SS7 defined by ANSI (1). Default is 0.
Mandatory.
The BSS AP subsystem number.
0 - 255. Defaults to 254.
Mandatory.
STP PC stp_pc_enabled
Used for enabling the stp_pc.
Disabled (0) or Enabled (1). Default is 0.
Mandatory.
STP Point Code stp_pc
The STP (signaling transfer point) point code. This point code should be used by MTPL3 and not by SCCP. Only used when stp_pc_enabled is 1.
0 - 16777215. 0 - 16777215 if ss7_mode is ANSI SS7.0 to 16383 if ss7_mode is not ANSI SS7.
Mandatory.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
BSS Detailed View fields
A5 Algorithms grouping Table 4-6 describes the fields in the A5 Algorithms grouping of the BSS Detailed View.
Table 4-6
BSS Detailed View fields - A5 Algorithms grouping
Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
A5 Algorithm Priority 1
The A5 encryption algorithm with priority 1 (highest) to be used by the BSS.
0 - 7. Default is 0 (No Encryption).
Mandatory.
A5 Algorithm Priority 2 - 7
As above but for Priority 2 to 7.
0 - 7. Default is null.
Optional.
A5 Algorithm Priority 8
No encryption algorithm associated.
0 or null. Default is null.
Optional.
Encryption Algorithm A5/1 to 7 Allowed option_alg_a5_1 to 7
These fields enable or disable encryption algorithm A5/1 to 7. multiEncryptOpt must be enabled.
Disabled (0) or Enabled (1). Default is Disabled (0).
Mandatory.
68P02901W17-S
4-19 Dec 2009
BSS Detailed View fields
Chapter 4: Configuring a BSS/RXCDR
General grouping Table 4-7 describes the fields in the General grouping of the BSS Detailed View.
Table 4-7
BSS Detailed View fields - General grouping
Field name/BSS parameter name
Brief description
Mandatory or Optional?
Values
Land Layer 1 Mode
The layer 1 mode of the land network TELCO connection type.
CEPT (E1) (0). Default is 0.
Mandatory.
MMS Critical Alarm Threshold Enable
Turns the MMS critical alarm threshold (cat) on or off. When enabled, takes the MMS out of service if it goes in and out of service ten times within a ten-minute period. If disabled, keeps the MMS in service even if it goes in and out of service ten times in a ten minute period.
Disabled (0) or Enable (1). Default is 0.
Mandatory.
XCDR Downlink VAD/DTX Enable
Whether downlink Voice Activity Detection/Discontinuous Transmission (VAD/DTX) is enabled.
Disabled (1) or VAD/DTX Enable (0). Default is 0.
Optional.
XCDR MSC Quiet Tone
Identifies a generated tone which is transmitted over a traffic channel when a voice is not being transmitted.
0 - 255 (Number identifying the tone). Default is 0
Mandatory.
Statistics Interval
The time in minutes in which the statistics file should be reported.
5 - 60 (in minutes). Default is 30
Mandatory.
OML X.25 Layer 3 Packet Size
Used to negotiate the Packet Size in the X.25 Call Request Packet.
128, 256 or 512. Default is 128
Mandatory.
OML X.25 Layer 3 Window Size
Used to negotiate the Window Size in the X.25 Call Request Packet.
2 - 7. Default 2.
Mandatory.
Illegal Circuit ID
An identifier to describe a circuit that is never used. It is used as an internal placeholder in call processing to show that no circuit has been assigned to a call.
Whether the Cipher Mode Reject message is sent to the MSC. Generated when the Cipher Mode Command message from the MSC specifies ciphering that the BSS or MS is unable to perform. Only used if the BSS optional feature gsmPhase2Opt is unrestricted.
Cipher Mode Reject message is not sent (0) or Cipher Mode Reject message is sent (1)
Mandatory.
Continued
4-20
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 4-7
BSS Detailed View fields
BSS Detailed View fields - General grouping (Continued)
Whether the BSS sends Confusion messages over the A-interface when an erroneous message is received from the MSC. If disabled, an alarm is sent instead to the MSC. Only used if the BSS optional feature gsmPhase2Opt is unrestricted.
Disabled (0) or Enable (1). Default is 0.
Mandatory.
Reset Circuit Message Flag
Whether the Reset Circuit message is sent to the MSC.
Message not sent (0), or Message sent (1). Default is 0.
Mandatory.
Radio Resource Status Flag
Whether a RR status message is sent to the mobile. The RR status message is sent to report certain error conditions in the messages received from the mobile.
The audio uplink volume control. Affects background and comfort noise, not data.
-15 to 15 (in dB) Default is 0.
Mandatory.
Global Reset Repetitions global_reset _repetitions(OMC-R parameter name: globalResetReps)
Allows the reset procedure to continue indefinitely, or stops the procedure after a fixed number of repetitions. The global reset procedure is only repeated if the MSC fails to acknowledge the BSS. Only used if the BSS optional feature gsmPhase2Opt is unrestricted.
0 - 255 (number of repetitions) Default is 0.
Mandatory.
Group Block Unblock Allowed group_block _unblock_allowed (OMC-R parameter name: grpBlkUnblkAllwd)
Allows the A-interface to be more efficient by enabling support of the group blocking/unblocking procedure if MSC supports circuit group block and circuit group unblock messages. Only used if the BSS optional feature gsmPhase2Opt is unrestricted.
Disabled (0) or Enable (1). Default is 0.
Mandatory.
Continued
68P02901W17-S
4-21 Dec 2009
BSS Detailed View fields
Table 4-7
Chapter 4: Configuring a BSS/RXCDR
BSS Detailed View fields - General grouping (Continued)
Field name/BSS parameter name
Brief description
Mandatory or Optional?
Values
The format of the GSM cell id sent by the BSS to the MSC.
0 - 2. Whole CGI (0), (LAC) and CI (1), or CI (2). Default is 1.
Max Reset Circuit Timer Expirations
Number of times the reset circuit message is repeated if an acknowledgment is not received from the MSC.
0 - 100 (number of repeats). Default is 1.
Mandatory.
Phase 2 Classmark Allowed
The format of the classmark parameter sent to the MSC based on GSM phases.
Formatted for Phase 1 (0), Formatted for Phase 2 (1), Formatted for Phase 2 with MultiBand (2) Default is 0.
The format used to send Resource Indication messages to the MSC. Only used if the BSS optional feature gsmPhase2Opt is unrestricted.
GSM Phase 1 format (0) or GSM Phase 2 format (1). Default is 0.
Mandatory.
SSM Critical Overload Threshold
The usage of call information blocks, as expressed by the ratio of the number of active calls to the maximum number of calls the SSM can handle (250).
0 - 100 (Percentage of Call Information Blocks in Use). Default is 80.
Mandatory.
SSM Normal Overload Threshold
The usage of call information blocks, as expressed by the ratio of the number of active calls to the maximum number of calls the SSM can handle (250). Every time the usage equals or exceeds this threshold, one access class is barred.
0 - 100. Default is 70.
Mandatory.
Site Statistics Process Burst Delay
The delay between bursts of messages sent from the Site Statistics Process (SSP) to the Central Statistics Process (CSP).
0 - 2500 (in ms). Default is 200.
Mandatory.
GSM Cell ID Format gsm_cell_id_format (OMC-R parameter name: gsm_cell_id_fmt)
Mandatory.
Continued
4-22
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 4-7
BSS Detailed View fields
BSS Detailed View fields - General grouping (Continued)
Field name/BSS parameter name
Brief description
Values
Mandatory or Optional?
Site Statistics Process Burst Limit
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 - 2. Send alarm to OMC (0), Send message to MSC (1), Send alarm to OMC and message to MSC (2). Default is 0.
Mandatory.
Call Traces Options
Reserved space for MSC-initiated Call Traces in the BSS, or to block MSC-initiated Call Traces. The values are specified as a percentage of traces reserved per LCF.
0 - No space Mandatory. reserved for MSC-initiated Call Traces. 1 to 100 Percentage of space reserved for MSC-initiated Call Traces. 255 MSC-initiated Call Traces blocked. Default is 0.
Override Intra Bss Pre Transfer
Whether SSM should send a pre-transfer request to SM when the handover allocation message is received during an inter-cell handover.
Send (0) or Do not send (1). Default is 0.
Mandatory.
Current Channel in HO Required Msg
Determines if the optional element current channel is included in the Handover Required message to the MSC.
Disabled (0) or Enabled (1). Default is 0.
Mandatory.
CBL X.25 Layer 3 Packet Size
Used to negotiate the Packet Size in the X.25 Call Request Packet.
128, 256 or 512. Default is 128.
Mandatory.
CBL X.25 Layer 3 Window Size
Used to negotiate the Window Size in the X.25 Call Request Packet.
2 - 7. Default is 2
Mandatory.
RTF PATH Fault Containment Status
Whether the functionality for the RTF PATH Fault Containment Feature is enabled or disabled.
Disabled (0) or Enabled (1). Default is 0.
Optional.
Continued 68P02901W17-S
4-23 Dec 2009
BSS Detailed View fields
Table 4-7
Chapter 4: Configuring a BSS/RXCDR
BSS Detailed View fields - General grouping (Continued)
Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
Handover Reject Message Required
Disables or enables the delivery of a handover required reject message from the MSC to the source BSS, in the event that a target cannot be found for a requested handover.
Reject message not required (0), Reject message required (1) Default is 1.
Mandatory.
Frequency Types Allowed
Determines the values that can be used for the Cabinet frequency_type and the CELL frequency_type.
1 - 15. Default is PGSM900 (1).
Mandatory.
Uplink and Downlink Volume Control Type volume_control _type(OMC-R parameter name: volContType)
Cannot be changed if the GDP Volume Control feature (gdpVolContOpt) is restricted (disabled).
CCDSP Volume Control (0), GDP Volume Control (1). Default is 0.
Mandatory.
BSS EGSM ALM Allowed egsm_alm_allowed
See Advanced Load Management for EGSM on page 2-76 for details.
MMI Cell ID Format
Format of the cell id accepted on the MMI command line.
0 or 1. 7-Parameter Cell Id Format Used On Command Line (0) 4-Parameter Cell Id Format Used On Command Line. Default is 0.
Mandatory.
Call Trace Msgs Before Handover
The number of messages of each type of handover data (RSS, Abis, and MS Power Control) collected immediately before a handover attempt has been completed, when handover data is requested by the operator.
0 - 8. Default is 5.
Mandatory.
Call Trace Msgs After Handover
The number of messages of each type of handover data (RSS, Abis, and MS Power Control) collected immediately after a handover attempt has been completed, when handover data is requested by the operator.
0 - 8. Default is 5.
Mandatory.
Optional.
Continued
4-24
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 4-7
BSS Detailed View fields
BSS Detailed View fields - General grouping (Continued)
Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
Second Assignment Procedure
Whether Second Assignment Procedure has been enabled at the BSS.
Enabled (1) or Disabled (0). Default is Disabled (0).
Optional.
MSC Overload Control bss_msc_overload _allowed
See MSC to BSS overload control on page 2-22 for further details.
Enabled (1) or Disabled (0). Default is Disabled (0).
Optional.
Update TSCs tsc_update_method
See Propagating TSC updates on page 8-220 for further details.
Default is 0.
Optional.
Pool GPROC Preemption
The preemption level for the pool GPROC functions.
0 - 2. No replacement (0), Based on Function Priority (1), Based on Function and Intra-function priorities (2). Default is 1.
Optional.
MTPL3 Signaling Link Test
Whether the MTPL3 signaling link test is enabled when the MTL comes in service.
Allowed (1) or Disallowed (0). Default is Allowed (1).
Mandatory.
SCCP Inactivity Control
Enables or disables the SCCP Inactivity Control.
Enabled (1) or Disabled (0). Default is Enabled (1).
See Modifying MTL loadsharing granularity on page 9-154 for details.
Optional.
Continued
68P02901W17-S
4-25 Dec 2009
BSS Detailed View fields
Table 4-7
Chapter 4: Configuring a BSS/RXCDR
BSS Detailed View fields - General grouping (Continued)
Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
Terminate RF when Cell goes OOS stop_dri_tx_enable
It takes time to stop RF transmission in a cell after it has been OOS. To avoid adding additional time to a short cell outage (for example caused by the momentary interruption of a non-redundant RSL), this field allows a user to specify the amount of time a DRI should continue RF transmission after the cell in which it is contained goes OOS. If set to Yes (1), the DRIs continue transmitting for the length of time specified in stop_dri_tx_time before transitioning to the D-U: CELL OOS state. If set to No (0) (default), the DRIs do not stop transmitting when the cell goes OOS.
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 during which zone ping-pong handovers are not allowed during the time in which the frequency of interzone ping-pong handovers are measured (as set by zone_pingpong_enable_win) after ping-pong handover has happened zone_pingpong_count times.
0 - 255. Default is 30.
Optional.
Mandatory.
Optional.
Continued
4-26
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Table 4-7
BSS Detailed View fields
BSS Detailed View fields - General grouping (Continued)
Field name/BSS parameter name Preferred PingPong Target Zone zone_pingpong _preferred_zone
Mandatory or Optional?
Brief description
Values
Indicates which zone is preferred as the hop target zone.
0 (outer zone preferred), 1 (inner zone preferred) or 255 (current zone). Default is 255.
Optional.
PCS 1900 Frequency grouping Table 4-8 describes the fields in the PCS 1900 Frequency grouping of the BSS Detailed View.
Table 4-8
BSS Detailed View fields - PCS 1900 Frequency grouping Mandatory or Optional?
Field name
Brief description
Values
Address Indicator bit 8
Specifies whether bit 8 of the address indicator in a PCS 1900 is set or unset.
0 or 1. Default is Unset (0).
Mandatory.
PCS 1900 Frequency Blocks
The PCS 1900 Frequency Blocks which determine the Absolute Radio Frequency Channels (ARFCNs) that the BSS is allowed to use for the PCS 1900 frequency type.
Click buttons A to F.
Mandatory.
Flash Information grouping Table 4-9 describes the fields in the Flash Information grouping of the BSS Detailed View.
Table 4-9
BSS Detailed View fields - Flash Information grouping Brief description
Values
Mandatory or Optional?
Flash Information
Version information of the current Flash EEPROM load.
4 - 11 digits.
Mandatory.
Flash Time
Date and time when current Flash EEPROM load was created.
Flash Checksum
Checksum value of the current Flash EEPROM load.
-2147483648 2147483647.
Mandatory.
Flash Size
The size of the current Flash EEPROM load.
-2147483648 2147483647. Size in Bytes
Mandatory.
Field name
68P02901W17-S
Mandatory.
4-27 Dec 2009
BSS Detailed View fields
Chapter 4: Configuring a BSS/RXCDR
Trunk Information grouping Table 4-10 describes the fields in the Trunk Information grouping of the BSS Detailed View.
Table 4-10
BSS Detailed View fields - Trunk Information grouping
Field name
Brief description
Values
Mandatory or Optional?
Trunk Critical Threshold
Used to determine the severity assignment of alarms and maintenance actions affecting trunks.
0 - 100 (Represents a percent of the capacity lost). Default is 50.
Mandatory.
Trunk Major Threshold
Used to determine the severity assignment of alarms and maintenance actions affecting trunks.
0 - 99 (Represents a percent of the capacity lost). Default is 10.
Mandatory.
CLM Timers grouping This grouping contains all the CLM timers, such as BSSMAP_T20 (CLM_T20). See Maintenance Information: BSS Timers (68P02901W58) for further details.
MTP Timers grouping This grouping contains all the MTP timers, such as SS7_L2_T1 (Alignment Ready). See Maintenance Information: BSS Timers (68P02901W58) and Preventive Cyclic Retransmission (PCR) on page 2-54for details.
SSM Timers grouping This grouping contains all the SSM timers, such as SCCP_TCONN_EST. See Maintenance Information: BSS Timers (68P02901W58) for further details.
4-28
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
BSS Detailed View fields
Directed Retry grouping Table 4-11 describes the fields in the Directed Retry grouping of the BSS Detailed View. Only used when the Directed Retry BSS feature (directedRetryOpt) is unrestricted.
Whether a channel mode modify procedure follows a successful handover in which the channel mode changed.
Enabled (1) or Disabled (0) (perform channel mode modify procedure after a handover for a Phase 1 MS in which the channel mode changed to full rate speech). Default is 0.
Optional.
Multiband grouping Table 4-12 describes the fields in the Multiband grouping of the BSS Detailed View.
Table 4-12
BSS Detailed View fields - Multiband grouping
Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
MultiBand Enabled mb_preference
Can only be modified if the MultiBand Inter-Cell Handover feature is unrestricted (enabled).
Enabled (1) or Disabled (0). Default is 0.
Mandatory.
Early Classmark Sending early_classmark _send(OMC-R parameter name: earlyClassmarkSnd)
Determines if the BSS suppresses the early sending of the Classmark Update message to the MSC.
0 - 3. Disabled on A-Interface and Air-Interface (0), Enabled on A-Interface, disable on Air-Interface (1), Disabled on A-Interface, and enabled on Air-Interface (2), Enabled on A-Interface and Air-Interface (3). Default is 0.
Mandatory.
Early Classmark Delay
The duration the BSS delays before sending the Classmark Update message to the MSC in the case of controlled early classmark sending.
0 - 100000 ms. Default is 0.
Mandatory.
68P02901W17-S
4-29 Dec 2009
BSS Detailed View fields
Chapter 4: Configuring a BSS/RXCDR
Enhanced Full Rate grouping Table 4-13 describes the fields in the Directed Retry grouping of the BSS Detailed View.
Table 4-13
BSS Detailed View fields - Enhanced Full Rate grouping
Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
Enhanced Full Rate Enabled efr_enabled
Whether Enhanced Full Rate (EFR) has been enabled at the BSS. Only valid when the Enhanced Full Rate feature EFROpt is unrestricted.
Disabled (0), Enabled (1). Default is 0.
Optional.
HO Req Speech Version Used handover_required _sp_ver_used (OMC-R parameter name: ho_req_spver_used)
Whether the speech version used can be built into the Handover Required message. Cannot be disabled:
Disabled (0), Enabled (1). Default is 0.
Mandatory.
•
Unless efr_enabled is disabled.
•
If either AMR Full Rate Enabled (amr_fr_enabled) or AMR Half Rate Enabled (amr_hr_enabled) is enabled at the BSS.
Circuit Error Rate Monitor grouping See Enhanced Circuit Error Rate Monitor (ECERM) on page 2-68 for further details.
Enhanced Circuit Error Rate Monitor grouping See Enhanced Circuit Error Rate Monitor (ECERM) on page 2-68 for further details.
GPRS grouping Table 4-14 describes the fields in the GPRS grouping of the BSS Detailed View. These fields are grayed-out, if the GPRS feature (gprsOpt) is restricted at the BSS.
Table 4-14
BSS Detailed View fields - GPRS grouping
Field name/BSS parameter name
Brief description
Values
SMG Gb Protocol Version smg_gb_vers
The SMG version adopted by the BSS over the Gb interface.
24 - 31 (SMG Gb version). Default is 31.
Related SGSN
Serving GPRS support node object identifier associated with this BSS.
Mandatory or Optional? Optional.
Optional.
Continued
4-30
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
The Medium Access mode that should be used by the PCUs. {23292} This element is restricted by the GPRS optional feature. It can be set to the value 2 only if the Extended Dynamic Allocation feature is unrestricted.
Whether a GPRS is present between the MSC and the SGSN.
1 to 3. Default is 3.
Mandatory.
GPRS Dual Power Mode gprs_dl_pwr_mode
The downlink power control mode the PCUs uses to broadcast data blocks to the mobile.
No power mode (0), Mode A (1), Mode B (2). Default is Mode A (1).
Optional.
SGSN Release sgsn_release
See PBCCH/PCCCH feature on page 2-115 for details.
Optional.
Current Bucket Level Feature bssgp_cbl_bit
See Current Bucket Level (CBL) feature on page 2-143 for details.
Mandatory.
Increased PRP Capacity Feature Enabled
See Enhanced Scheduling on page 2-144 for details.
Mandatory.
Max Number of UL timeslots per mobile PRR Blocks Reservation Aggressiveness Factor GPRS Uplink or Downlink bias Most Common Multislot of GPRS Mobiles
See Enhanced Scheduling on page 2-144 for details.
Optional.
Redundant PSP Audit Timer red_psp_audit_tmr
Audit mechanism used to determine the health of the secondary MPROC. Grayed-out if the GPRS feature is restricted at the BSS.
GPRS Type 5 Algorithm Enabled gprs_type5_alg
See Network Assisted Cell Change (NACC) on page 2-165 for further details.
0 to 24. Default 24.
Optional.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
BSS Detailed View fields
Map Information grouping Table 4-15 describes the fields in the Map Information grouping of the BSS Detailed View.
Table 4-15
BSS Detailed View fields - Map Information grouping
Field name
Values
Mandatory or Optional?
-18000 to 18000.
Optional.
-9000 to 9000.
Optional.
INS, OOS or Unknown. Currently, INS is defined as Enabled-Unlocked or Busy-Unlocked, and OOS is Disabled-Locked or Disabled-Unlocked.
Optional.
Brief description
Longitude
Longitude position of the displayable node.
Latitude
Latitude position of the displayable node.
Service State
The state of a node or link on a map.
Default Map
See description in Table 3-3.
GSM/GPRS Trace Information grouping See Call trace flow control on page 2-61 for details of these parameters.
SMS Information grouping See Short Message Service - Cell Broadcast on page 2-43 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.
The ratio of intra-BSC handovers to all handovers. OMC only attribute.
0.0 - 1.0. Default is 0.
Optional.
Location Update factor
A function of the ratio of location updates to calls, the ratio of IMSI detaches to calls and whether the short message sequence or long message sequence is used for IMSI detach.
0.0 - 30.0. Default is 0.
Optional.
Call Duration seconds
The average call duration during the busiest period of the day.
0 - 1200. Default is 0.
Optional.
0 - 20. Default is 0.
Optional.
Paging rate in pages per second
Network Assisted Cell Change (NACC) grouping Table 4-17 describes the fields in the Network Assisted Cell Change grouping of the BSS Detailed View.
Field name Cell Change Notification Enabled nacc_enabled
Brief description
Values
Mandatory or Optional?
See Network Assisted Cell Change (NACC) on page 2-165 for further details.
Quality of Service (QoS) grouping See Quality of Service (QoS) on page 2-157 for details of these fields.
LCS grouping See GSM location services on page 2-102 for details of these fields.
Network Controlled Cell Reselection grouping See Network Controlled Cell Reselection on page 2-79 for further details of these fields.
4-34
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
BSS Detailed View fields
GPRS Seamless Cell Reselection Table 4-18 describes the fields in the GPRS Seamless Cell Reselection grouping of the BSS Detailed View. These fields are grayed-out if the GPRS Seamless Cell Reselection Feature (scrOpt) in the Optional Features grouping of the BSS Detailed View is unrestricted (Disabled (0)).
Field name/ parameter name GPRS Seamless Cell Reselection Feature scr_enabled
Brief description
Values
Mandatory or Optional? Mandatory.
See GPRS Seamless Cell Reselection on page 2-140 for details.
Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping Table 4-19 describes the fields in the Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping of the BSS Detailed View. Unless stated otherwise, the OMC-R database parameter names are the same as the BSS database parameter names. Fields in this grouping can be accessed if the AMR Feature (amrOpt) or the GSM HR Feature (gsmHalfRateOpt) are unrestricted (Enabled) at the BSS, see Adaptive Multi-Rate (AMR) on page 2-127 for details.
Table 4-19 grouping
Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)
Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
AMR Full Rate Enabled amr_bss_full _rate_enabled (OMC-R parameter name: amr_fr_enabled)
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.
0 or 1. Enabled (1), Disabled (0). Default is 0.
Optional.
AMR Half Rate Enabled amr_bss_half_rate _enabled(OMC-R parameter name: amr_hr_enabled)
Enables and disables AMR Half Rate (HR) for the BSS. Cannot be enabled if ho_req_spver_used is disabled at the BSS, or if CIC Validation (cic_validation) is disabled at the Assoc_RXCDR.
0 or 1. Enabled (1), Disabled (0). Default is 0.
Optional.
Continued
68P02901W17-S
4-35 Dec 2009
BSS Detailed View fields
Chapter 4: Configuring a BSS/RXCDR
Table 4-19 Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping (Continued) Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
AMR MS Monitor Period amr_ms_monitor _period(OMC-R parameter name: AmrMsMonPeriod)
Used to detect MSs continually requesting the highest or lowest modes.
0, or 10 - 120 SACCH periods. 0 disables the MS Monitor function. Default is 40.
Optional.
AMR MS Low CMR amr_ms_low_cmr
The percentage of the monitor period for which an individual MS can request the lowest Codec mode.
50 - 100%. Default is 95%.
Optional.
AMR MS Low If the MS is consistently RXQUAL requesting lowest rate amr_ms_low_rxqual Codec mode but reports RXQUAL values less than defined, the BSS uses this value to decrease the Down Link adaptation Thresholds.
0 - 7 Qband units. Default is 2 Qbands or 0.5% BER.
Optional.
AMR MS High CMR amr_ms_high_cmr
The percentage of the monitor period for which an individual MS can request the highest Codec mode.
50 - 100% Default is 99%.
Optional.
AMR MS High RXQUAL amr_ms_high_rxqual (OMC-R parameter name: AmrMsHighRxqual)
If the MS is consistently requesting the highest rate Codec mode but reports RXQUAL values less than defined, the BSS uses this value to increase the Down Link adaptation Thresholds.
0 - 7 Qband units. Default is 4 Qbands, or 2.5% BER.
Optional.
AMR Downlink Threshold Adjustment amr_dl_thresh _adjust(OMC-R parameter name: AmrDlThreshAdj)
Used to increase or decrease C/I adaptation thresholds according to the values for AmrMsHighRxqual and amr_ms_low_rxqual.
1 - 7 dB. Default is 3.
Optional.
Continued
4-36
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
BSS Detailed View fields
Table 4-19 Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping (Continued) Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
AMR Force Half Rate Usage force_hr_usage (OMC-R parameter name: force_hr_use)
Overrides MSC provided preference, and forces Half Rate usage for all AMR/GSM Half Rate capable calls within the BSS. Does not apply when the MSC has specified that rate changes are not allowed. For example, if hr_intracell_ho_allowed is set such that full-rate only is allowed, force_hr_usage is ignored.
0 or 1. Disabled (0) Enabled (1). Default is Disabled (0).
Optional.
AMR Downlink LA Mode Change Min amr_dl_la_mode _chg_min(OMC-R parameter name: AmrDlLaMode ChgMin)
Used for the downlink adaptation procedure to set the minimum time period between initiating changes in the downlink Codec mode. The delay is only added, if set to less than the inherent delay in the adaptation (including zero).
0 - 255 ms. Default is 100.
Optional.
Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping with GSM Half Rate Table 4-20 describes the 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-138 for details.
Table 4-20 grouping
Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)
Field name/BSS parameter name GSM BSS Half Rate Enabled gsm_bss_half_rate _enabled(OMC-R parameter name: gsm_bss_half_rate _enabled)
68P02901W17-S
Brief description
Values
Enables and disables GSM Half Rate (HR) for the BSS. Cannot be enabled (grayed-out) if GSM Half Rate Feature is restricted, or if CIC Validation (cic_validation) is disabled at the Assoc_RXCDR.
0 or 1. Enabled (1), Disabled (0).Default is 0.
Mandatory or Optional? Optional.
4-37 Dec 2009
Modifying BSS details using the OMC-R GUI
Chapter 4: Configuring a BSS/RXCDR
Pre-empt grouping See Enhanced Multi-level Precedence and Pre-emption (eMLPP) on page 2-168 for details of these parameters.
RSL Congestion grouping See RSL Congestion Control on page 2-173 for details of these parameters.
Modifying BSS details using the OMC-R GUI To change BSS details, see Modifying a network object using the OMC-R GUI on page 1-34. For information about changing specific fields in the BSS Detailed View, see the following section.
Changing the Network Entity Id field after BSS creation Modifying the Network Entity Id field in the Identification grouping after the BSS has been created to a value that is already in use, causes the OMC-R to reject the value and display the following warning message: The Network Entity Identifier must be unique within the network When the Transcoding field is set to Remote (0), and an attempt is made to modify the value in the Network Entity Id field, the OMC-R displays the following warning message: Warning: Changing Network Entity Id will result in cycling all Associated RXCDR devices which are BUSY_UNLOCKED. Cycling these devices will result in loss of all call traffic from this BSS to those RXCDRs. This loss of call traffic may be avoided if cic_validation is disabled at the BSS. The connected remote Associated BSS entities may need to the updated at the following RXCDRs: RXCDR_ RXCDR_ ... Do you wish to continue? Click OK to continue or Cancel to cancel the cycling. However, these messages are not displayed if the Transcoding field in the BSS Detailed View is set to Local (1).
4-38
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Creating an RXCDR using the OMC-R GUI
Creating an RXCDR using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Prerequisites to creating an RXCDR An RXCDR should be created in the OMC-R GUI before physically connecting to the OMC-R. It can only be added if a network (that is, the parent) has been defined in advance.
Creating an RXCDR using the OMC-R GUI To create an RXCDR using the OMC-R GUI, use the following procedure:
Procedure 4-6
Create an RXCDR using the OMC-R GUI
1
Navigate to and select the RXCDR class button in the Navigation Tree. If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The RXCDR class button changes color.
2
From the menu bar, select Edit à Create. The OMC-R displays the RXCDR Detailed View in Create mode
3
Click the Initial Software Load button to display a Software Inventory Dialog window.
4
Double-click one of the software loads to select it and enter it in the RXCDR Detailed View.
5
From the menu bar of the RXCDR Detailed View window, select Options à Initialize Form. The OMC-R displays the RXCDR Detailed View window.
6
Complete the fields in the RXCDR Detailed View as required. See Table 4-1 to Table 4-16 for guidance.
NOTE To obtain the relevant information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
68P02901W17-S
7
Once all the required information has been entered in the RXCDR Detailed View, select File à Create from the menu bar.
8
Select File à Close from the menu bar to close the Detailed View.
4-39 Dec 2009
Modifying RXCDR details using the OMC-R GUI
Chapter 4: Configuring a BSS/RXCDR
Modifying RXCDR details using the OMC-R GUI To change RXCDR details, see Modifying a network object using the OMC-R GUI on page 1-34. For information about changing specific fields in the RXCDR Detailed View, refer to the following section.
Changing the Network Entity Id field after RXCDR creation Any attempt to modify the Network Entity Id parameter field in the Identification grouping after the RXCDR has been created to a value that is already in use, results in the OMC-R rejecting the value and displaying the following warning message: The Network Entity Identifier must be unique within the network Any attempt to modify this field after the RXCDR has been created, results in the OMC-R displaying the following warning message: Warning: Changing Network Entity Id will result in cycling all Associated BSS devices which are BUSY_UNLOCKED. Cycling these devices will result in loss of all call traffic from those BSSs to this RXCDR. This loss of call traffic may be avoided if cic_validation is disabled at the BSS for this RXCDR. The connected remote Associated RXCDR entities may need to be updated at the following BSSs: BSS_ BSS_ ... Do you wish to continue? Click OK to continue or Cancel to cancel the cycling. If the Network Entity Id field is changed, later when the RXCDR Detailed View window is saved, the OMC-R displays the following warning message: Warning: Changing the Network Entity Identifier will cause all the associated BSSs to be cycled which may result in the loss of all active calls. Do you wish to continue? Click OK to continue or Cancel to cancel the cycling.
4-40
68P02901W17-S Dec 2009
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-S
4-41 Dec 2009
NE database checks
Chapter 4: Configuring a BSS/RXCDR
This script can be LAN loaded onto the BSC to create the database object during the installation and commissioning of a BSC.
Figure 4-2
Example of a script file
ti-GSM-Exampleofascriptfile-00781-ai-sw
NE database checks Network Element (NE) database checks are required for the following reasons:
4-42
•
To ensure that the NE has the same database as the OMC-R.
•
To clear out old databases. Only the last three databases are kept.
•
To check if an upload has been made after NE database changes. When changes are made, they must be logged using any method selected by the customer.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Typical database directory structure
When configuration changes at an NE database are made, the MIB is updated by performing an audit. The OMC-R must also be updated, by uploading the NE database. There should be a maximum of three databases on the system for any BSS or RXCDR at any one time. For more information on the database checking procedure see Operating Information: OMC-R System Administration, (68P02901W19).
Typical database directory structure Typically, the database is stored in the following directory: usr/omc/ne_data/dbroot. A typical BSS database directory structure is shown in Figure 4-3. There is a similar directory structure for an RXCDR.
CSFP directory dbComment download.list OTHER BSSs ti-GSM-SC01W17-000049-eps-sw
68P02901W17-S
4-43 Dec 2009
Deleting a BSS/RXCDR
Chapter 4: Configuring a BSS/RXCDR
Deleting a BSS/RXCDR ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to deleting a BSS/RXCDR This section describes the procedure to delete a BSS/RXCDR from the OMC-R, and the two additional procedures required to delete the BSS/RXCDR from the X.25 network.
CAUTION Removing a BSS or RXCDR prevents the OMC-R from communicating with the BSS/RXCDR. Failure to physically disconnect the BSS/RXCDR from the OMC-R may result in unnecessary traffic across the GSM network.
Impact of deleting a BSS on an Assoc_BSS If a BSS, which has been specified as an Associated BSS, is deleted from the network, the Associated BSS field in the Assoc_BSS Detailed View is set to NULL. This indicates that the Assoc_BSS does not correspond to any BSS device.
Impact of deleting an RXCDR on an Assoc_RXCDR If an RXCDR, which has been specified as an Associated RXCDR is deleted from the network, the Associated RXCDR field in the Assoc_RXCDR Detailed View is set to NULL. This indicates that the Assoc_RXCDR does not correspond to any RXCDR device.
Prerequisites before deleting a BSS/RXCDR A BSS/RXCDR should be deleted only after authorization has been obtained in advance from the Network planning team. This procedure only applies to a BSS to be decommissioned. If the BSS is being moved to a different OMC-R or RXCDR, refer to the Reparenting a BSS on page 4-101 or Reparenting an RXCDR to a different MSC on page 4-107 procedures.
4-44
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Removing a BSS/RXCDR from the network
Removing a BSS/RXCDR from the network Perform the following tasks to remove a BSS or RXCDR from the network:
Procedure 4-7
Remove a BSS or RXCDR from the network
1
Carry out Deleting a BSS/RXCDR from the OMC-Rin this section.
2
Remove the BSS/RXCDR from the X.25 network by deleting a BSS/RXCDR at the packet switch, see Reparenting a BSS on page 4-101.
Deleting a BSS/RXCDR from the OMC-R To delete a NE from the OMC-R carry out the following procedure:
Preparing to delete The following preparation is required before deleting a BSS/RXCDR:
Procedure 4-8 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.
NOTE This can be done locally at the BSC or remotely using rlogin. 2
68P02901W17-S
Physically disconnect the cable between the OMC-R and BSS/RXCDR.
4-45 Dec 2009
Deleting a BSS/RXCDR from the OMC-R
Chapter 4: Configuring a BSS/RXCDR
Deleting the BSS/RXCDR Follow Procedure 4-9 to delete the BSS/RXCDR:
Procedure 4-9 1
Delete BSS/RXCDR
Using the Navigation Tree, display the BSS/RXCDR to be deleted.
NOTE Configuration information can be extracted if the BSS is to be added at a later date. Refer to Extracting data from the CM MIB using cmutil on page 15-25 for further details. 2
As omcadmin, delete the BSS from the MIB using the following command:
NOTE This step requires authorization in advance from the OMC-R System Administrator. HierDelete BSS
The following confirmation message is displayed: Do you really want to delete the BSS ? The gui might core if any of the forms for the objects are open for edit Please ensure this is not the case and will not be at any time while this script is running (Warning: this operation cannot be aborted once started. Type Y to proceed, anything else will abort operation now). 3
Press Y to proceed. The deletion is complete when the BSS/RXCDR has been removed from the Navigation Tree. No further deletes should be performed until this occurs.
NOTE
4-46
•
The BSS software directory is renamed in a similar manner to after the activation of a new BSS software load.
•
The relevant entries in the PM database are renamed to ~xx where xx is a two digit number.
•
The relevant entries in the NE.MAP and SITE.MAP are commented out. The old names must not be re-used until the PM statistics have cleared (after approximately five days) and the entries deleted using delete_BSS, delete_SITE or delete_CELL commands.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Deleting a BSS/RXCDR from the OMC-R
Follow up activities after deletion of the BSS/RXCDR When the BSS/RXCDR has been deleted, perform the following procedure:
Procedure 4-10
Follow up after deleting BSS/RXCDR
1
If the cells of the BSS are being decommissioned, or reused under different BSSs, external neighbors which point to these cells may require removal. The HierDelete utility does not remove these external neighbors from other BSSs. The neighbors should be removed from other BSS databases during the next frequency replan.
2
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.
3
Remove the BSS directory from the following location: /usr/omc/ne_data/dbroot/BSS/BSSspecific
4
Edit any appropriate subscription lists to remove the BSS from them. See OMC-R Online Help, Network Operations for details of subscription lists.
NOTE Once the BSS has been deleted, the following are also removed: Event and Alarm windows for the BSS and the BSS SITES, if subscriptions are exclusive to them.
68P02901W17-S
5
Remove the appropriate RXCDR - Associated BSS objects from the RXCDRs which are connected to the BSS.
6
Remove any entries for the NE from the packet switch/MUX, see Reparenting a BSS on page 4-101.
7
Delete the default network map and any user-defined map files containing the deleted BSS information.
8
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.
9
If using the Map feature, open the network map from the GUI and check the impact of the BSS/RXCDR removal on the remaining NEs. Move the remaining nodes to any desired new positions on the map background. When the NEs are in the desired position, save the network map and the new default map, by selecting File à Save from the menu bar. Refer to: OMC-R Online Help, Network Operations for a description of how to move the NEs on a map.
4-47 Dec 2009
Deleting a BSS/RXCDR at the packet switch/MUX
Chapter 4: Configuring a BSS/RXCDR
Deleting a BSS/RXCDR at the packet switch/MUX ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to Deleting the BSS/RXCDR at the packet switch This section describes the procedure to delete a BSS/RXCDR at the packet switch, and at the MUX. Refer to Operating Information: OMC-R System Administration (68P02901W19) for further details about the packet switch/MUX.
Configuration changes at the packet switch The following configuration changes must be made to the packet switch when removing a BSS/RXCDR from the network:
Procedure 4-11
Change packet switch configuration before deleting BSS/RXCDR
1
At the packet switch delete the routing table entry, if necessary.
2
Remove the cabling between the packet switch and MUX.
Deleting the routing table entry The removal of an NE from the network may not require any actions to be carried out at the packet switch. There is no path through the MUX to the packet switch and the NE should have been removed from the OMC-R NE nodes file so that data is not routed to it. However, the OMC-R System Administrator may wish to modify the routing table entry for the NE by deleting the address field as a precautionary procedure.
Removing the cabling between packet switch and MUX If a complete 2 Mbit/s link is to be removed:
Procedure 4-12
4-48
Remove complete 2 Mbit/s link before deleting BSS/RXCDR
1
Disconnect the cable from the access link port and the cable between ports used between the MUX and packet switch.
2
Use the configuration table to determine to which ports these cables are connected.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuration changes at the MUX
Configuration changes at the MUX The following configuration changes must be made to the MUX when removing a BSS/RXCDR from the network:
Procedure 4-13
Change MUX configuration before deleting BSS/RXCDR
1
Delete the link, endpoints, and circuit entries from the MUX configuration.
2
Remove the cabling between the packet switch and MUX.
Dependencies on NE removal from the MUX Actions at the MUX are dependent on whether the NE being removed is: •
On its own 2 Mbit/s link.
•
On a single timeslot on a shared link.
If the NE is on its own 2 Mbit/s link, an additional action is required as detailed in the following section Removing the NE from the MUX.
Removing the NE from the MUX Removing configuration information If the NE is on its own 2 Mbit/s link, remove the access link entry from the MUX configuration, before removing the configuration information:
Procedure 4-14
68P02901W17-S
Remove configuration information
1
Use the MUX configuration table to determine the linkname, endpoints and circuit name, that have to be removed from the MUX configuration.
2
Continue with the next procedure, Removing the NE link to the MUX, to remove the links to the MUX.
4-49 Dec 2009
Removing the NE link to the MUX
Chapter 4: Configuring a BSS/RXCDR
Removing the NE link to the MUX To remove an NE link to the MUX:
Procedure 4-15
4-50
Remove NE link to the MUX
1
Log in to the MUX.
2
Remove the access link entry if a 2 Mbit/s link is being disconnected using the following command: d l -r
3
Remove circuit entries using the following command: d c -r
4
Remove endpoint entries using the following command: d e -r d e -r
5
Log out of the MUX by pressing Ctrl-L.
6
Remove the cabling.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Equipping cabinets and cages at a BSS site
Equipping cabinets and cages at a BSS site ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of equipping cabinets and cages at a BSS Cabinets and cages can be created using either the: •
OMC-R GUI Navigation Tree.
•
equip BSS command from a TTY session.
Equipping cabinets and cages can be carried out either in SYSGEN mode or outside of SYSGEN mode with the site locked. See Configuring a cabinet on page 4-54 and Configuring a cage on page 4-59 in the following sections.
Horizonmicro2 and Horizoncompact2 BTS cabinets A maximum of three Cabinets can exist at a Horizonmicro2 and Horizoncompact2 BTS. Each Cabinet can be seen as a BTS. The first Cabinet equipped (Cabinet:0) represents the master BTS. Further Cabinets (Cabinet:1 and Cabinet: 2) represent slave BTSs. The slave Cabinets are attached to the master Cabinet through fiber ports 1 and 2, respectively. The master Cabinet must be equipped before the slave Cabinets. When a slave Cabinet is equipped, the BTS Configuration Type field (BSS parameter name: bts_type) in the BTS Detailed View of the parent BTS is set to 1, meaning Non-Abis, Type 1. If Cabinet devices 1 and 2 exists, the BSS autoequips the related DHP(s) devices with the ids 1 and 2. See Introduction to BSC and BTS sites on page 7-2 for further details of Horizonmicro2.
Horizon II macro and Horizon II macro_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 cabinet's type cannot be modified from any other type to Horizon II macro. However, a cabinet with cabinet type Horizonmacro_ext, TCU 6, or TCU 2 can be modified to Horizon II macro_ext. A Horizon II macro or Horizon II macro_ext cabinet type can support only one of the following frequencies at a time: •
PGSM900.
•
EGSM900.
•
DCS1800.
68P02901W17-S
4-51 Dec 2009
Horizon II mini and Horizon II macro cabinets
Chapter 4: Configuring a BSS/RXCDR
A maximum of three extension cabinets can be connected to a Horizon II macro cabinet type, as shown in Table 4-21.
Table 4-21
Extension cabinets for Horizon II macro
Master cabinet
Extension
Horizon II macro
TCU_6. Horizonmacro_ext. Horizon II macro_ext.
A Horizon II macro_ext cabinet type can be equipped to the cabinet types shown in Table 4-22.
Table 4-22
Cabinet types allowing Horizon II macro_ext as an extension type
Extension
Master cabinet
Horizon II macro_ext
M-Cell6. Horizonmacro. Horizon II macro.
Horizon II mini and Horizon II macro cabinets Horizon II macro functionality can be applied to a Horizon II mini, that is, whatever a Horizon II macro cabinet with two CTU2s and a single BTP can do, a Horizon II mini can also do, except where otherwise stated. Modification of cabinet type from Horizon II mini to Horizon II macro is permitted as long as there are no DRI or EAS devices equipped. Modification from Horizon II macro to Horizon II mini is permitted as long as the site has one or fewer BTPs, no EASs, and no DRIs equipped to it. All other changes involving Horizon II mini and Horizon II macro master cabinet are disallowed. The frequency type of the source and destination cabinet remain the same. A Horizon II mini or Horizon II mini extension cabinet can support only one type of frequency at any one time. A Horizon II mini cannot support dual band. It can support PGSM, EGSM, and DCS1800 but only one band per cabinet. A Horizon II mini can be the master of, or slave to, a Horizon II macro cabinet. Table 4-23 shows extension cabinets to which a Horizon II mini can be master.
Table 4-23
Extension cabinet types allowed for Horizon II mini
Master cabinet Horizon II mini
Extension cabinet Horizon II mini extension. Horizon II macro
extension. Horizon macro extension. TCU6.
4-52
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Horizon II mini and Horizon II macro cabinets
Table 4-24 shows the master cabinets to which a Horizon II mini extension can be equipped.
Table 4-24
Master cabinet types allowed for Horizon II mini extension
Extension cabinet
Master cabinet
Horizon II mini extension
Horizon II mini. Horizon II macro. Horizon macro. MCELL6.
68P02901W17-S
4-53 Dec 2009
Configuring a cabinet
Chapter 4: Configuring a BSS/RXCDR
Configuring a cabinet ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Creating a cabinet for a site using the OMC-R GUI To create an instance of a Cabinet, proceed as follows:
Procedure 4-16
Create Cabinet instance using the OMC-R GUI
1
Navigate to and select the Cabinet class button in the Navigation Tree (BSS à BSS instance à SITE à SITE instance à Hardware Devices à Cabinet). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object class button changes color.
2
Select Edit à Create from the Navigation Tree menu bar.
3
Complete the fields, as required. See Cabinet Detailed View fields for further details.
4
Select File à Create from the menu bar to create a Cabinet instance.
5
Select File à Close from the menu bar to close the Detailed View form.
Cabinet Detailed View fields The following sections list and briefly describe the parameter fields in the Cabinet Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
4-54
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Cabinet Detailed View fields
Identification grouping Table 4-25 describes the fields in the Identification grouping of the Cabinet Detailed View.
{26481} This parameter represents a physical cabinet within a BSC/RXCDR/BTS site. 28 or HORIZON2MICRO indicates that the cabinet is a H2micro. 29 or HORIZON2MICRO_EXT indicates that the cabinet is a H2micro extension.
0 - 29.
Mandatory.
RDN Class
See description in Table 4-1.
Default is Cabinet.
RDN Instance
See description in Table 3-1.
0 - 15.
NMC RDN Value
See description in Table 4-1.
Parent Detailed View
Displays the name of the parent site. Click to display the parent site Detailed View.
Kit Number
Not displayed for a Horizonmacro or Horizon II macro BTS. Grayed-out if site is not a Horizonmicro or Horizoncompact. For a Horizonmicro or Horizoncompact, this field is inherited from the Hardware Version Number (HVN), and cannot be changed.
Field Replacement Unit (FRU)
See Maintenance Information: BSS Field Troubleshooting (68P02901W51) for
Field name
Serial Number
68P02901W17-S
0 - 15 characters
Optional.
Optional.
details of all the possible values that can be displayed. Displayed when cabinet_type is: Horizon II mini, Horizon II macro, Horizon macro, 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. Grayed-out if site is not a Horizonmicro or Horizoncompact. For a Horizonmicro or Horizoncompact, this field is inherited from the Hardware Version Number (HVN), and cannot be changed.
0 - 15 characters
Optional.
4-55 Dec 2009
Cabinet Detailed View fields
Chapter 4: Configuring a BSS/RXCDR
Permitted cabinet_type modifications and restrictions {26481} The BSS allows the operator to modify the value of cabinet_type as shown in Table 4-26.
Table 4-26
Permitted cabinet_type modifications and restrictions
Source cab type
Target cab type
Restrictions on source cab
HORIZONMACRO2
HORIZON2MINI or HORIZON2MICRO
Fewer than 2 BTPs equipped; DRI and EAS not equipped; single frequency type.
HORIZON2MINI or HORIZON2MICRO
HORIZON2MACRO or HORIZON2MINI or HORIZON2MICRO
DRI and EAS not equipped.
TCU_2 or TCU_6 or HORIZONMACRO_EXT or HORIZONMACRO2_EXT or HORIZON2MINI_EXT
HORIZON2MICRO_EXT
DRI and EAS not equipped; single frequency type excluding PCS1900.
HORIZON2MICRO_EXT
HORIZONMACRO2_EXT or HORIZON2MINI_EXT
DRI and EAS not equipped.
Additional Information Use the Additional Information window to input any notes relating to this Cabinet. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
State grouping Standard network object state fields, see Table 4-2 for details.
4-56
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Cabinet Detailed View fields
General grouping Table 4-27 describes the fields in the General grouping of the Cabinet Detailed View.
Table 4-27
Cabinet Detailed View fields - General grouping Brief description
Values
Mandatory or Optional?
Frequency Type frequency_type (OMC-R parameter name: freq_type)
The frequency band capability of the Cabinet. If the Infrastructure Sharing Homogeneous Cabinet feature is restricted, then only required for the first Cabinet created at a site. Thereafter, the frequency type of future Cabinets should be forced to the freq_type of the first Cabinet. If cabinet_type is M-Cellmicro, then only one frequency type is allowed regardless of whether the Infrastructure Sharing Homogenous or Heterogenous features are restricted (disabled) or not. Horizon II and Horizon II mini sites can support one of the following frequencies: PGSM, EGSM, or DCS1800.
1 - 15.
Optional.
Power Supply Unit 1 to 4 psu_fru_1 to psu_fru_4
The type of the first, second, third, and fourth power supply units (PSUs) out of four PSUs installed in the cabinet, if any. PSUs 1 to 3 are valid for Horizonmacro, Horizonmacro_ext, Horizon II macro and Horizon II macro_ext cabinet types. PSU 4 is only valid for Horizon II macro and Horizon II macro_ext cabinet types. When cabinet-type is a Horizon II mini psu_fru_1 and psu_fru_2 are displayed. psu_fru_1 displays hardware information for the Power Supply Unit at the Horizon II mini cabinet. psu_fru_2 indicates whether a battery hold-up unit is present in the Horizon II mini cabinet. These fields are not visible for any other cabinet types. Cannot be modified by a user (read only).
Indicates whether an internal HDSL modem is present in the cabinet. When cabinet type is Horizonmacro, or Horizonmacro_ext this field is grayed-out. For a Horizon II mini, Horizon II mini extension, Horizon II macro, and Horizon II macro extension, this field does not appear.
Field name/BSS parameter name
Optional.
0 or 1. Internal HDSL modem is not present (0). Internal HDSL modem is present (1).
Optional.
Continued
68P02901W17-S
4-57 Dec 2009
Equipping a cabinet using the TTY interface
Table 4-27
Chapter 4: Configuring a BSS/RXCDR
Cabinet Detailed View fields - General grouping (Continued)
Field name/BSS parameter name Internal Integrated Antennae int_integrated _ant
Brief description Indicates whether an internal integrated antenna is present in the cabinet. When cabinet type is Horizonmacro or Horizonmacro_ext this field is grayed-out. For a Horizon II mini, Horizon II mini extension, Horizon II macro, and Horizon II macro extension, this field does not appear.
Mandatory or Optional?
Values 0 or 1. Internal integrated antenna is not present (0). Internal integrated antenna is present (1).
Optional.
Equipping a cabinet using the TTY interface To equip a cabinet at a previously equipped BSC site, follow these steps:
Procedure 4-17 1
Equip a Cabinet at the TTY interface
Enter the following command: equip CAB The system prompts for further configuration information, for example: Enter the CABINET: Enter the cabinet type: Enter the frequency type:
2
At the prompts, enter the required configuration information.
Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete information on BSS commands, parameters, and prompts.
4-58
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring a cage
Configuring a cage ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Creating a cage using the OMC-R GUI To create an instance of a Cage device using the OMC-R GUI, proceed as follows:
Procedure 4-18
Create a Cage instance using the OMC-R GUI
1
Navigate to and select the Cage class button in the Navigation Tree (BSS à BSS instance à SITE à SITE instance à Hardware Devices à Cage). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object class button changes color.
2
Select Edit à Create from the Navigation Tree menu bar. The Cage Detailed View form is displayed.
3
Enter all required information in this form. See Cage Detailed View fields for further details.
4
Select File à Create from the menu bar to create the cage instance.
5
Select File à Close from the menu bar to close the Detailed View.
Cage Detailed View fields The following sections list and briefly describe the parameter fields in the Cage Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
68P02901W17-S
4-59 Dec 2009
Cage Detailed View fields
Chapter 4: Configuring a BSS/RXCDR
Identification grouping Table 4-28 describes the fields in the Identification grouping of the Cage Detailed View.
For a BSC or RXCDR, cage range is 0 - 13. For a BTS, cage range is 2-15.
NMC RDN Value
See Table 4-1 description.
Parent Detailed View
Displays the name of the parent site (BSC or BTS). Click to display the parent site Detailed View.
Cabinet Identifier
The identifier of the cabinet in which this cage resides.
IAS Connected
Whether an IAS is connected to this cage. Not used if cabinet_type is PCU.
IAS not connected, or IAS is connected.
Mandatory.
KSWX Number 0
The KSWX device which is connecting the cage to a KSW for TDM0 in another cage. Not used if TDM0 or the KSW resides in this cage. Not used if cabinet_type is PCU.
0 - 4
Optional.
KSWX Number 1
The KSWX device which is connecting the cage to a KSW for TDM1 in another cage. Not used if TDM1 or the KSW resides in this cage. Not used if cabinet_type is PCU.
0 - 4
Optional.
KSW Pair
The KSW pair managing this cage. Not used if cabinet_type is PCU.
0 - 3
Optional.
Mandatory.
Additional Information Use the Additional Information window to input any notes relating to this Cage. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
State grouping Standard network object state fields, see Table 4-2 for details.
4-60
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Equipping a cage from the TTY interface
Equipping a cage from the TTY interface To equip a cage using the TTY interface, follow these steps:
Procedure 4-19 1
Equip a Cage at the TTY interface
Enter the following command: equip CAGE The system responds with the prompts for further information.
2
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-S
4-61 Dec 2009
Configuring an RXCDR cabinet
Chapter 4: Configuring a BSS/RXCDR
Configuring an RXCDR cabinet ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of configuring an RXCDR cabinet Equipping a cabinet can be carried out using either the: •
OMC-R GUI.
•
equip command from a TTY session.
RXCDR cabinet numbers When equipping cabinets at an RXCDR, the numbers 0 to 15 may be assigned for reference purposes.
Creating an RXCDR cabinet using the OMC-R GUI To create an RXCDR cabinet Navigation Tree, proceed as follows:
Procedure 4-20
Create an RXCDR cabinet using the OMC-R GUI
1
Navigate to and select the Cabinet class button in the Navigation Tree (RXCDR à RXCDR instance à SITE à SITE instance à Hardware Devices à Cabinet). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object class button changes color.
2
Select Edit à Create from the Navigation Tree menu bar. A Cabinet Detailed View form is displayed.
3
Enter all required information in this form. See Configuring a cabinet on page 4-54 for details of the Cabinet Detailed View fields.
NOTE To obtain the relevant information for a parameter, click Help at the top right of the window, select On Context and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
4-62
4
Select File à Create from the menu bar to create an RXCDR cabinet.
5
Select File à Close to close the Detailed View form.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Equipping an RXCDR cabinet using the TTY interface
Equipping an RXCDR cabinet using the TTY interface See Example of equipping an RXCDR cabinet and cage using the TTY interface on page 4-66.
68P02901W17-S
4-63 Dec 2009
Configuring an RXCDR cage
Chapter 4: Configuring a BSS/RXCDR
Configuring an RXCDR cage ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of configuring an RXCDR cage Configuring a cage can be carried out using either the: •
OMC-R GUI.
•
equip command from a TTY session.
RXCDR cage numbers When equipping cages at an RXCDR, the numbers 0 to 13 may be assigned with the first equipped cage assigned number 0, the second cage assigned number 1, and so on.
Creating an RXCDR cage using the OMC-R GUI To create an instance of a Cage device using the OMC-R GUI, proceed as follows:
Procedure 4-21
Create an RXCDR Cage instance using the OMC-R GUI
1
Navigate to and select the Cage class button in the Navigation Tree (RXCDR à RXCDR instance à SITE à SITE instance à Hardware Devices à Cage). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object class button changes color.
2
Select Edit à Create from the Navigation Tree menu bar. A CAGE Detailed View form is displayed.
3
Enter all required information in this form. See Configuring a cage on page 4-59 for details of the Cage Detailed View fields.
NOTE To obtain the relevant information for a parameter, click Help at the top right of the window, select On Context and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
4-64
4
Select File à Create from the menu bar to create an RXCDR cage.
5
Select File à Close from the menu bar to close the Detailed View form.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Equipping an RXCDR cage using the TTY interface
Equipping an RXCDR cage using the TTY interface See Example of equipping an RXCDR cabinet and cage using the TTY interface on page 4-66.
68P02901W17-S
4-65 Dec 2009
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 is equipped at MSC_XCDR. The following information is available: •
The RXCDR cabinet is number 0.
•
The cabinet is equipped with one cage, numbered 0.
NOTE The RXCDR examples shown in this section are for demonstration purposes only. Parameters are system specific and will vary.
Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete information on the BSS commands, parameters, and prompts.
Equipment Cage 0 is equipped with the following required and optional devices:
4-66
•
EAS (half size PIX module).
•
MSI.
•
XCDR.
•
KSW A and KSW B.
•
GCLK A and GCLK B.
•
GPROC.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Overall procedure list
Additional equipment Although there is no equip procedure for the following devices, they must be physically inserted when more than one cage is equipped: •
CLKX (half size modules, cage 0 only).
•
KSWX (half size modules).
NOTE The Bus Terminator Card (BTC) is always provided in a BSC (or BTS or RXCDR) cage.
Overall procedure list The following steps are required when equipping cabinets and cages at an RXCDR site using the TTY interface:
Procedure 4-22
Equip RXCDR cabinet and cages using TTY interface
1
Select the RXCDR site and change to security level 2, see Remotely logging in to a BSS site from the OMC-R on page 1-39.
2
Equip the cabinet using the equip command, see the following sections.
3
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 ->
68P02901W17-S
4-67 Dec 2009
Equipping the RXCDR cage using the TTY interface
Chapter 4: Configuring a BSS/RXCDR
Equipping the RXCDR cage using the TTY interface At an RXCDR site, cage numbers are unique. The numbers can range from 0 - 13; the first equipped cage assigned number 0 and the second assigned number 1. The following provides example input and output for equipping the BSUs using the example data. -> equip 0 CAGE Enter the identifier for the CAGE: 0 Enter the KSW pair that manages the CAGE: 1 Enter the KSWX connecting cage to KSW for TDM 0: Enter the KSWX connecting cage to KSW for TDM 1: Enter cabinet to which the cage belongs: 0 Is an IAS connected?:
no
COMMAND ACCEPTED ->
4-68
68P02901W17-S Dec 2009
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. When an Assoc_BSS is created, a CommsLink is automatically created. Likewise, when an Assoc_BSS is deleted, the CommsLink is automatically deleted.
Prerequisites to creating an Assoc_BSS An Assoc_BSS can only be created if: •
The BSS exists.
•
The parent device has been defined in advance, that is, an RXCDR.
Creating an Assoc_BSS using the OMC-R GUI To create an Assoc_BSS to the network using the OMC-R GUI, follow these steps:
Procedure 4-23
Create an Assoc_BSS to the network using OMC-R GUI
1
Navigate to and select the Assoc_BSS class button in the Navigation Tree (RXCDR à RXCDR instance à Assoc_BSS). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The Assoc_BSS class button changes color.
2
Select Edit à Create from the Navigation Tree menu bar. The OMC-R displays the Assoc_BSS Detailed View in Create mode.
3
Click the Associated BSS button. The OMC-R displays a popup window which lists all the BSSs currently in the network. Continued
68P02901W17-S
4-69 Dec 2009
Assoc_BSS Detailed View fields
Chapter 4: Configuring a BSS/RXCDR
Procedure 4-23
Create an Assoc_BSS to the network using OMC-R GUI (Continued)
4
Select the BSS to be associated with this RXCDR. This highlights the BSS.
5
Click OK. The OMC-R displays the name of the selected BSS in the Associated BSS field.
6
Complete the remaining fields as required. See Assoc_BSS Detailed View fields for details of these fields.
NOTE To obtain the relevant information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed. 7
From the menu bar, select File à Create to create the Assoc_BSS details.
8
From the menu bar, select File à Close to close the Detailed View.
Assoc_BSS Detailed View fields The following sections list and briefly describe the parameter fields in the Assoc_BSS Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
Identification grouping Table 4-29 describes the fields in the Identification grouping of the Assoc_BSS Detailed View.
Displays the name of the parent object. Click to display the parent RXCDR Detailed View.
Associated BSS
Displays the identifier of the associated BSS.
Values
Mandatory or Optional? Not applicable.
Mandatory.
Additional Information Use the Additional Information window to input any notes relating to this Assoc_BSS. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
State grouping Standard object status information fields, see Table 4-2 for details.
General grouping Table 4-30 describes the fields in the General grouping of the Assoc_BSS Detailed View.
Table 4-30
Assoc_BSS Detailed View fields - General grouping
Field name
Brief description
UL and DL Volume Control Type
See description in Table 4-7.
Downlink Audio Level Offset
See description in Table 4-7.
Uplink Audio Level Offset
See description in Table 4-7.
Values
Mandatory or Optional?
Deleting an Assoc_BSS using the OMC-R GUI To delete an existing instance of an Assoc_BSS using the OMC-R GUI, refer to the general procedure in Deleting a network object using the OMC-R GUI.
Creating an Assoc_BSS using the TTY interface To add an Assoc_BSS to the network using the TTY interface, use the equip command. For example: equip 0 ABSS
68P02901W17-S
4-71 Dec 2009
Displaying Assoc_BSS details using the TTY interface
Chapter 4: Configuring a BSS/RXCDR
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-72
68P02901W17-S Dec 2009
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. When an Assoc_RXDCR is created, a CommsLink is automatically created. Likewise, when an Assoc_RXCDR is deleted, the CommsLink is automatically deleted.
Prerequisites to creating an Assoc_RXCDR An Assoc_RXCDR can only be created if: •
Remote transcoding has been specified at the BSS.
•
The RXCDR exists in the network.
•
A BSS exists in the network.
Creating an Assoc_RXCDR using the OMC-R GUI To create an Assoc_RXCDR using the OMC-R GUI, follow these steps:
Procedure 4-24
Create an Assoc_RXCDR using the OMC-R GUI
1
Navigate to and select the Assoc_RXCDR class button in the Navigation Tree (RXCDR à RXCDR instance à Assoc_RXCDR). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The Assoc_RXCDR class button changes color.
2
Select Edit à Create from the Navigation Tree menu bar. The OMC-R displays the Assoc_RXCDR Detailed View in Create mode. Continued
68P02901W17-S
4-73 Dec 2009
Assoc_RXCDR Detailed View fields
Procedure 4-24
Chapter 4: Configuring a BSS/RXCDR
Create an Assoc_RXCDR using the OMC-R GUI (Continued)
3
Click the Associated RXCDR button. The OMC-R displays a popup window which lists all the RXCDRs currently in the network.
4
Select the RXCDR to be associated with this BSS. This highlights the RXCDR.
5
Click OK. The OMC-R displays the name of the selected RXCDR in the Associated RXCDR field.
6
Complete the remaining fields, as required. See Assoc_RXCDR Detailed View fields for further details.
7
From the menu bar, select File à Create to create the Assoc_RXCDR.
8
From the menu bar, select File à Close to close the Detailed View.
Assoc_RXCDR Detailed View fields The following sections list and briefly describe the parameter fields in the Assoc_RXCDR Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
Identification grouping Table 4-31 describes the fields in the Identification grouping of the Assoc_RXCDR Detailed View.
Installation and Configuration: GSM System Configuration
Assoc_RXCDR Detailed View fields
Additional Information Use the Additional Information window to input any notes relating to this Assoc_RXCDR. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
State grouping Standard object status information fields, see Table 4-2 for details.
Local Routing Information grouping Table 4-32 describes the fields in the Local Routing Information grouping of the Assoc_RXCDR Detailed View.
Table 4-32
Assoc_RXCDR Detailed View fields - Local Routing Information grouping
Field name/BSS parameter name
Brief description
CIC Validation cic_validation
See Enhanced XBL (EXBL) on page 2-10 for further details.
Values
Mandatory or Optional? Mandatory.
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 grayed-out if both amrEnhancedCapOpt and gsmHalfRateOpt are restricted. (see Adaptive Multi-Rate (AMR) on page 2-127 and GSM Half Rate on page 2-138 for additional information).
Table 4-33 grouping
Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate)
Field name/BSS parameter name Enhanced Auto Connect Modeeac_mode
Brief description
Values
Whether the BSC-RXCDR interface is using the available resources for half rate calls with 8 kbit/s Ater allocations. If cic_validation (see Table 4-32) is disabled, this field is grayed-out and set to Disabled (0).
0 or 1. Disabled (0) or Enabled (1). Default is 0.
Mandatory or Optional? Optional.
Continued
68P02901W17-S
4-75 Dec 2009
Creating an Assoc_RXCDR using the TTY interface
Chapter 4: Configuring a BSS/RXCDR
Table 4-33 Channel Mode Usage (AMR Full Rate and Half Rate/GSM Half Rate) grouping (Continued) Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
CIC Blocking Thresho ld cic_block_thresh
Threshold used to block CICs according to the availability of IDLE Aters. Only sensitive if eac_mode is set to Enabled (1) and if AMR and/or GSM HR features are unrestricted.
Threshold used to unblock CICs according to the availability of IDLE Aters. Only sensitive if eac_mode is set to Enabled (1) and the AMR and/or GSM HR features are unrestricted. cic_unblock_thresh must be greater than cic_block_thresh by a value of 10 or more.
0, 11 - 255. Default is 0.
Optional.
NOTE The CIC blocking mechanism can be formally disable by setting cic_block_thresh and cic_unblock_thresh to 245 and 255 respectively. It should be noted however, that if no 16 kbit/s ATERs are available, then full rate calls are prevented from being set up and only half rate calls are accepted.
Creating an Assoc_RXCDR using the TTY interface To create an Assoc_RXCDR using the TTY interface, use the equip command. For example: equip 0 AXCDR The system responds by displaying the following prompts (bold text shows example user responses): Enter the AXCDR device id: Perform CIC validation:
1
YES
Enable Enhanced Auto-Connect Mode:
yes
Enter the CIC blocking threshold:
Enter the CIC unblocking threshold:
COMMAND ACCEPTED
4-76
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displaying Assoc_RXCDR details using the TTY interface
Displaying Assoc_RXCDR details using the TTY interface To display information for an Assoc_RXCDR using the TTY interface, use the disp_equipment command. For example: disp_equipment 0 AXCDR 1 The system responds by displaying details of the Assoc_RXCDR. See Technical Description: BSS Command Reference (68P02901W23) for further details.
Enabling/Disabling CIC Validation at an Assoc_RXCDR using the TTY interface To enable CIC Validation at an RXCDR using the TTY interface, use the modify_value command. For example: modify_value 0 cic_validation YES AXCDR 1 The system responds: WARNING: Any CIC equipage inconsistencies between BSC and RXCDR may result in dropped calls. Do you want to continue (Y/N) : Y COMMAND ACCEPTED To disable CIC Validation at an Assoc_RXCDR, use the modify_value command. For example, the following command disables cic_validation (sysgen on) whether AMR Half Rate, GSM Half Rate, and eac_mode are enabled: modify_value 0 cic_validation NO AXCDR 1 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
68P02901W17-S
4-77 Dec 2009
Changing AMR Half Rate mode using the TTY interface
Chapter 4: Configuring a BSS/RXCDR
The system responds: COMMAND ACCEPTED WARNING: AMR and GSM Half Rate is currently disabled at this BSC. To disable eac_mode when AMR and GSM Half Rate features are unrestricted, (with SYSGEN on or off), cic_validation, amr_bss_half_rate_enabled and gsm_bss_half_rate_enabled enabled, use the modify_value command. For example, the following command modifies eac_mode to No at Assoc_RXCDR 128: modify_value 1 eac_mode no AXCDR 128 The system responds: WARNING: Disabling enhanced auto connect mode will terminate all active calls through this Associated RXCDR from this BSC, and reconfigure the CIC Ater assignments as for Auto Connect Mode. The following command modifies cic_unblock_thresh to 100 at Assoc_RXCDR 128: modify_value 0 cic_unblock_thresh 100 AXCDR 128 The following command attempts to modify cic_unblock_thresh to 10 at Assoc_RXCDR 128: modify_value 0 cic_unblock_thresh 10 AXCDR 128 The system responds: COMMAND REJECTED: The valid range is 0 to disable cic_unblock_thresh or 11-255 to enable it. The following command attempts to modify cic_unblock_thresh to 29 when cic_unblock_thresh is currently 40 and cic_block_thresh is 20: modify_value 0 cic_unblock_thresh 29 AXCDR 128 The system responds: COMMAND REJECTED: CIC unblocking threshold must be greater than the CIC blocking threshold by a value of 10. The following command attempts to modify cic_unblock_thresh to 20 at Assoc_RXCDR 128 when eac_mode is disabled: modify_value 0 cic_unblock_thresh 20 AXCDR 128 The system responds: COMMAND REJECTED: Cannot modify CIC blocking or unblocking thresholds if Enhanced Auto-Connect Mode is disabled
Changing AMR Half Rate mode using the TTY interface The following command disables amr_bss_half_rate_enabled (with SYSGEN on or off) with either cic_validation and/or eac_mode enabled: chg_element amr_bss_half_rate_enabled no 0 The system responds:
4-78
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Changing GSM Half Rate mode using the TTY interface
WARNING: AXCDR CIC validation and/or enhanced auto connect mode are currently enabled COMMAND ACCEPTED
Changing GSM Half Rate mode using the TTY interface The following command disables gsm_bss_half_rate_enabled (with SYSGEN on or off) with either cic_validation and/or eac_mode enabled: chg_element gsm_bss_half_rate_enabled 1 0 The system responds: WARNING: This may cause a short delay in a new call setup during reconfiguration. COMMAND ACCEPTED
NOTE •
If an AXCDR with cic_validation enabled does not exist, the system also responds: 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
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.
68P02901W17-S
4-79 Dec 2009
Deleting an Assoc_RXCDR using the TTY interface
Chapter 4: Configuring a BSS/RXCDR
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
4-80
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR
Changing the NE ID of an Assoc_BSSs or Assoc_RXCDR ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to changing the NE ID of an AXCDR or ABSS After configuring either an Assoc_RXCDR (AXCDR) or Assoc_BSS (ABSS), the user may realize they have given the ABSS or AXCDR the wrong Network Entity (NE) id. The user can change the NE ID of the AXCDR or ABSS using the OMC-R GUI, which then propagates the new NE ID to all the related connections. For example, a user connected an RXCDR to a BSC and labeled the NEs: RXCDR-5, BSC-10, and AXCDR-5. The user then performed up to 21 add_conn commands (which all referenced AXCDR-5), equipped 20 XBLs, and up to 2400 CICs. The user then discovers that the RXCDR connected to BSC-10 has an NE id of 7 instead of 5. To correct this problem, the user would have to unequip all CICs, XBLs, and connectivity entries referencing AXCDR-5 and then re-equip these devices to the new AXCDR-7. Instead, the user can initiate a single request at the OMC-R GUI to propagate changes to all the affected devices and connectivity entries. This is done using the Change Assoc NE ID menu option. The same situation could occur for a ABSS device in an RXCDR database. The change assoc NE ID operation only changes the identifier of an AXCDR (or ABSS) in a BSS (or RXCDR) database. If the user changes the identifier of an NE, the user must also change the identifier in the NE database and, if necessary, use the change assoc NE ID operation to change the associated device id in each database which includes the NE as an associated device. For example, BSS-1 and BSS-2 are connected to RXCDR-3, and AXCDR-3 is equipped in BSS-1 and BSS-2 databases. To change the NE id for RXCDR from 3 to 5, the user must change the id of the RXCDR in the RXCDR database, and then start the change assoc NE ID operation on AXCDR-3 at BSS-1 and BSS-2 to set the new AXCDR id to 5.
NOTE Once the change assoc NE ID process has started, if the GUI is closed for some reason the change assoc NE ID process continues.
Phases in the change assoc NE ID process The change assoc NE ID operation has three phases: •
Extract.
•
Unequip.
•
Re-equip
The progress of the change assoc NE ID operation is displayed in the status bar and also in the change assoc NE ID process log file, which is displayed in an Xterm window when the change assoc NE ID process is initiated.
68P02901W17-S
4-81 Dec 2009
Change assoc NE ID process log files
Chapter 4: Configuring a BSS/RXCDR
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: __. Where: is the name of the BSS or RXCDR to which the ABSS/AXCDR being changed is associated. is the current (old) network entity id of the network element to be changed. is the new network entity id of the network element. 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.
4-82
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Restrictions to changing an NE ID
Restrictions to changing an NE ID Do not modify the database of the NE being changed until the change assoc NE ID process is complete. Do not start a change assoc NE ID operation for an associated device, if: •
An Audit, Resync, Network Expansion, CellXchange, Bay Level Calibration, or cell parameter propagation operation is in progress for the container NE.
•
cmutil updates are in progress in the container NE database.
Likewise, if a change assoc NE ID operation is in progress: •
An Audit, Resync, Network Expansion, CellXchange, Bay Level Calibration, or cell parameter propagation should not be started for the container NE.
•
A cmutil operation cannot be invoked for an NE or its containers.
Changing the NE ID of an ABSS or AXCDR using the OMC-R GUI To change the NE ID of an Assoc_BSS or Assoc_RXCDR using the OMC-R GUI, follow these steps:
Procedure 4-25
68P02901W17-S
Change NE ID of Assoc_BSS or Assoc_RXCDR using the OMC-R GUI
1
Navigate to and select the Assoc_BSS or Assoc_RXCDR instance button in the Navigation Tree (for an Assoc_BSS, select: RXCDR - RXCDR instance - Assoc_BSS - Assoc_BSS instance. For an Assoc_RXCDR, select: BSS - BSS instance - Assoc_RXCDR Assoc_RXCDR instance. The instance button changes color.
2
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.
3
Enter the new network entity id for the Assoc_BSS or Assoc_RXCDR in the New Assoc NE ID field. Enter a unique value in the range 1 - 128. If the new network entity id number is not unique, the OMC-R displays a message in the status bar and rejects the new number. Enter a new unique network entity number. If the new network entity id is not known, go to Viewing network entity ids step 1. Otherwise, go to Starting the change assoc NE ID process - step 1.
4-83 Dec 2009
Changing the NE ID of an ABSS or AXCDR using the OMC-R GUI
Figure 4-4
Chapter 4: Configuring a BSS/RXCDR
Change Assoc NE ID form (for an Assoc_RXCDR instance)
Viewing network entity ids To display a list of all the network entities managed by the OMC-R, follow these steps:
Procedure 4-26 1
Display network entities
Click the View NE IDs button. The BSSs or RXCDRs list form is displayed. For example, if the selected element is a ABSS, a list of all BSSs is shown. The BSSs/RXCDRs list form displays the following information for each BSS or RXCDR managed by the OMC-R: •
NE ID - the network entity id.
•
Version - the version number of the software load active in the Network Element (BSS database parameter neLoadVersion).
•
Network Element - the name of the network element.
If required, click the Print button to print the list of NEs to the printer specified in the PRINTER environmental variable. 2
Click the required network element in the list. The OMC-R highlights the selection. To exit the list and return to the Change Assoc NE ID form, click Cancel. Continued
4-84
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration Changing the NE ID of an ABSS or AXCDR using the OMC-R GUI
Procedure 4-26
Display network entities (Continued)
3
Click OK. The network entity id of the selected NE is copied into the New Network Entity Id field in the Change Assoc NE ID form. Double-clicking the network element in the NE List form has the same result.
4
Now go to Starting the change assoc NE ID process - step 1.
Starting the change assoc NE ID process To start the change assoc NE ID process, follow these steps:
Procedure 4-27
Start the change assoc NE ID process
1
Click OK. When changing the NE ID of an Assoc_RXCDR, the OMC-R displays the following message. An equivalent message is displayed when changing an Assoc_BSS NE id. Use the scroll bars to display all of the message. WARNING: Changing the Network Entity Id will result in loss of all calls and communication between this RXCDR and the BSS. The operation will first delete all the XBLs, CICs, Conn_Links and Assoc_RXCDRs between this RXCDR and the BSS in the BSS database. Then it will re-equip all the XBLs, CICs, Conn_Links and Assoc_RXCDRs as it was originally in the BSS database but with the new Network Entity Id. The operation may take a long time to complete. Do you wish to continue?
2
Click OK to continue with the change assoc NE ID process. To close the confirmation box and return to the Change Assoc NE ID form, click Cancel.
3
The OMC-R displays the status of the NE id change process in the status bar, and the .process log file in an Xterm window. By default, the status bar is one line deep. To expand the status bar, click the [Symbol_triangledown] button to the right of the status bar. To shrink the status bar back to its original size, click the [Symbol_triangleup] button.
4
To view the active log file for the change assoc NE ID process, go to Viewing other log files below.
Figure 4-5 shows an example of the .progress log file with the Extracting phase complete, and the Unequipping phase in progress.
68P02901W17-S
4-85 Dec 2009
Viewing other log files
Figure 4-5
Chapter 4: Configuring a BSS/RXCDR
.progress log file
ti-GSM-progresslogfile-00784-ai-sw
Viewing other log files To view other change assoc NE ID process log files, select Options - View Log from the menu bar of the Change Assoc NE ID form. The OMC-R opens a Log File Selection window. An example is shown in Figure 4-6.
4-86
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Figure 4-6
Viewing other log files
Log File Selection window
ti-GSM-LogFileSelectionwindow-00785-ai-sw
Selecting an .active log file To select an .active log file, follow these steps:
Procedure 4-28
68P02901W17-S
View an active log file
1
Select the .active log file in the Files pane of the Log File Selection window.
2
Click the View Active Log button to view the .active log file. The text editor displays the contents of the .active log file in an Xterm window (see Figure 4-7, for example). If necessary, use the Return key to scroll through the log file. If an active log file does not exist, the View Active Log button is grayed-out and cannot be selected.
3
Now go to Closing the log file window step 1.
4-87 Dec 2009
Viewing other log files
Figure 4-7
Chapter 4: Configuring a BSS/RXCDR
.active log file
ti-GSM-activelogfile-00786-ai-sw
4-88
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Resuming a suspended change assoc NE ID process
Viewing an inactive log file To view an inactive log file (such as, .complete log file) follow these steps:
Procedure 4-29
View an inactive log file
1
Navigate to another directory using the Filter line and button, and select a log file. Or, if necessary: Click Cancel to close the window and return to the Change Assoc NE ID window.
2
Click the View Log button to view the contents of an inactive log file. The text editor displays the contents of the log file in an Xterm window. Use the Return key to scroll through the log file.
Closing the log file window To close the log file window, follow these steps:
Procedure 4-30
Close the log file window
1
Left-click the button in the top left corner of the window.
2
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 (.resume) exists for the suspended change NE ID process.
NOTE Before resuming a change assoc NE ID operation, ensure that no changes were made to the database since the suspension and before the resume. Otherwise, the change assoc NE ID reconfigurations may not be successful.
68P02901W17-S
4-89 Dec 2009
Resuming a suspended change assoc NE ID process
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-90
68P02901W17-S Dec 2009
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-18 for further details. A DYNET is contained in a DYNETGroup. When the user creates the first DYNET using the TTY interface, a DYNETGroup is automatically created. When the last DYNET in a DYNETGroup is deleted, the DYNETGroup is automatically deleted.
Equipping path devices When a DYNET is equipped, the path devices for the BTSs that supported the dynamic allocation are also equipped.
Equipping RSLs RSLs for BTS sites that support dynamic allocation must be equipped to the automatically equipped paths associated with the DYNET.
DYNET restrictions Restrictions and exceptions for a DYNET are as follows: •
A DYNET can be equipped and unequipped, but cannot be locked, unlocked, or shutdown.
•
A DYNET can include BTSs with the SITE Detailed View field: Timeslot Sharing (parameter name ts_sharing) disabled.
•
A DYNET can include BTSs with timeslot (TS) marker sites (switching sites).
•
All DYNETs that share the same first identifier must have the same BTSs, or marker sites (switching sites), in the same order.
•
DYNETs must have different E1 links for the BTSs that have the SITE Detailed View field: Timeslot Sharing (parameter name ts_sharing) enabled.
•
Equipping the DYNET also equips path devices for the BTSs supporting dynamic allocation (that is, BTSs with Timeslot Sharing field (parameter name ts_sharing) enabled). For any non-DYNET BTSs, paths have to be manually created.
•
DYNETs must include at least one BTS that has the Timeslot Sharing field (parameter name ts_sharing) enabled.
68P02901W17-S
4-91 Dec 2009
DYNETGroup
Chapter 4: Configuring a BSS/RXCDR
•
A DYNET device can only be equipped to a BSC.
•
There can be only three DYNETs per DYNETGroup.
•
More than one E1 link can exist between BTSs for dynamic sharing purposes.
DYNETGroup A DYNETGroup represents a grouping of DYNETs. When the user creates the first DYNET using the TTY interface, a DYNETGroup is automatically created. A DYNETGroup is contained by a BSS.
DYNETGroup restrictions Restrictions and exceptions for a DYNETGroup are: •
A maximum of 20 DYNETGroup objects can be supported per BSS.
•
A DYNETGroup is only visible on the Navigation Tree when BSC-BTSdynamic allocation is enabled at the BSS (that is, the BSCBTSDynAllocOptparameter is set to Enabled (1)).
•
The DYNETGroup can include BTSs with the SITE Detailed View field: Timeslot Sharing (parameter name ts_sharing) disabled.
•
A maximum of three DYNETs can be supported per DYNETGroup.
•
Fault management activities are not supported for a DYNETGroup object.
DYNETGroup and DYNET topics The following sections contain further information about DYNETGroups and DYNETs:
4-92
•
Configuring a DYNETGroup on page 4-93, including creating and deleting using GUI or TTY interface.
•
Configuring a DYNET on page 4-95, including creating, viewing, editing and deleting using GUI or TTY interface.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring a DYNETGroup
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-18 for further details.
Creating a DYNETGroup using the OMC-R GUI To create a DYNETGroup using the OMC-R GUI, follow these steps:
Procedure 4-31
Create a DYNETGroup using the OMC-R GUI
1
Navigate to and select the DYNETGroup class button in the Navigation Tree (BSS à BSS instance à DYNETGroup). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The class button changes color.
2
Select Edit à Create from the menu bar. The OMC-R displays the DYNETGroup Detailed View form in Create mode.
3
Complete the fields as required. See DYNETGroup Detailed View fields for further information.
4
Select File à Create from the menu bar to create the DYNETGroup.
5
Select File à Close from the menu bar to close the DYNETGroup Detailed View.
DYNETGroup Detailed View fields The following sections list and briefly describe the parameter fields in the DYNETGroup Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
68P02901W17-S
4-93 Dec 2009
Equipping a DYNETGroup using the TTY interface
Chapter 4: Configuring a BSS/RXCDR
Identification grouping Table 4-34 describes the fields in the Identification grouping of the DYNETGroup Detailed View.
Additional Information Use the Additional Information window to input any notes relating to this DYNETGroup. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
Equipping a DYNETGroup using the TTY interface When creating the first DYNET using the TTY interface, the OMC-R automatically creates a DYNETGroup. A DYNETGroup cannot be equipped using the TTY interface.
Deleting a DYNETGroup using the OMC-R GUI A DYNETGroup cannot be deleted until all the DYNETs it contains have been deleted. When the last DYNET is deleted, the OMC-R automatically deletes the DYNETGroup.
4-94
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring a DYNET
Configuring a DYNET ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Path devices for a DYNET When a DYNET is equipped for BSC-BTSdynamic allocation, the OMC-R automatically creates the path devices and assigns path identifiers in the range 0 - 5. These values indicate that the path has been automatically equipped. When dynamic allocation is enabled at the corresponding site, valid path identifiers are available in the range 6 - 9. When dynamic allocation is disabled at the corresponding site, valid path identifiers are available in the range 0 - 9. See Dynamic allocation of BSC-BTS Backing Resources (DYNET) on page 2-18 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-18.
Creating a DYNET using the OMC-R GUI Prerequisite Before creating a DYNET using the OMC-R GUI, a DYNETGroup must have been created.
Procedure To create a DYNET, follow these steps:
Procedure 4-32
Create a DYNET using the OMC-R GUI
1
Navigate to and select the DYNET class button in the Navigation Tree (BSS à BSS instance à DYNETGroup à DYNETGroup instance à DYNET). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The class button changes color.
2
Select Edit à Create from the Navigation Tree menu bar. The OMC-R displays the DYNET Detailed View form in Create mode. Continued
68P02901W17-S
4-95 Dec 2009
DYNET Detailed View fields
Chapter 4: Configuring a BSS/RXCDR
Procedure 4-32
Create a DYNET using the OMC-R GUI (Continued)
3
Complete the fields as required. See DYNET Detailed View fields for further details.
4
Select File à Create from the menu bar to create the DYNET.
5
Select File à Close from the menu bar to close the DYNET Detailed View.
DYNET Detailed View fields The following sections list and briefly describe the parameter fields in the DYNET Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
Identification grouping Table 4-35 describes the fields in the Identification grouping of the DYNET Detailed View.
Click to display the parent DYNET Group Detailed View.
Mandatory or Optional?
Additional Information Use the Additional Information window to input any notes relating to this DYNET. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
4-96
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
DYNET Detailed View fields
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
Field name/BSS parameter name Shared Timeslots shared_timeslots
Brief description
Values
The number of timeslots reserved at a DYNET for BSC-BTSdynamic allocation.
0 - 31. Default: 0.
Mandatory or Optional? Mandatory.
Path information grouping Table 4-37 describes the fields in the path Information grouping of the DYNET Detailed View.
Table 4-37
DYNET Detailed View fields - path Information grouping
Field name/BSS parameter name No of Links numInSequence
Brief description Number of links in the sequence for the DYNET. A DYNET can have up to 11 links.
BSC MSI Id msi_id
The MSI id at the BSC where the MMS resides.
BSC MMS Id mms_id
The MMS id for the BSC network definition.
Values
Mandatory or Optional?
1 - 11.
Mandatory.
{22169} 0 - 95.
Mandatory.
0 or 1.
Mandatory.
Site Id Site_id
The BTS site identifier, that is, the terminating site.
1 to 100.
Mandatory.
Link 1 to Link 6 DYNET_link1 to DYNET_link6
The first to sixth link in the DYNET path.
Site Id (0..100, 254). Upstream MSI (0..55, 254). Upstream MMS (0..1, 254). Downstream MSI (0..55, 254). Downstream MMS (0..1, 254).
Link 1 is mandatory, Link 2 to 6 are optional.
Continued
68P02901W17-S
4-97 Dec 2009
Modifying and deleting a DYNET using the OMC-R GUI
Table 4-37
Chapter 4: Configuring a BSS/RXCDR
DYNET Detailed View fields - path Information grouping (Continued)
Field name/BSS parameter name
Mandatory or Optional?
Brief description
Values
Link 7, 8, 9, 10 (DYNET_link7)
The seventh, eight, ninth and tenth links in the DYNET path.
Site Id (0..100, 254). Upstream MSI (0..55, 254). Upstream MMS (0..1, 254). Downstream MSI (0..55, 254). Downstream MMS (0..1, 254).
Optional.
Link 11 (DYNET_link11)
The eleventh link in the DYNET path. It can only be used to make the final loop-closing link back to the BSC.
Site Id (0) Upstream MSI (0..55) Upstream MMS (0..1) Downstream MSI (0..55) Downstream MMS (0..1).
Optional.
TS Switch (GUI only)
Determines whether the site is a timeslot switching site.
Button on or off.
Modifying and deleting a DYNET using the OMC-R GUI To modify DYNET parameters, see the general procedure in Modifying a network object using the OMC-R GUI on page 1-34. To delete a DYNET, see the general procedure in Deleting a network object using the OMC-R GUI on page 1-37.
Configuring a DYNET using the TTY interface For full details of command and parameters mentioned in the following sections, see Technical Description: BSS Command Reference (68P02901W23).
Creating a DYNET using the TTY interface When creating the first DYNET using the TTY interface, the OMC-R automatically creates a DYNETGroup. To equip a DYNET, use the equip command. Example 1: To equip a BTS network that contains a single BTS that does not loop back to the BSC, enter the following command: equip 0 DYNET
4-98
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring a DYNET using the TTY interface
The system responds with prompts for further information. Bold text shows examples of user responses: Enter 1st and 2nd DYNET identifiers: Enter BSC MMS identifiers: Enter SITE identifier:
1 0
0 0
1
Enter upstream MMS identifiers:
0 0
Enter downstream MMS identifiers: COMMAND ACCEPTED Example 2: To equip a second set of E1 links for the BTS network defined in Example 1, enter the following command: equip 0 DYNET The system responds with the following prompts. Bold text shows examples of user responses: Enter 1st and 2nd DYNET identifiers: Enter BSC MMS identifier: Enter SITE identifier:
1 1
1 0
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
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
68P02901W17-S
4-99 Dec 2009
Configuring a DYNET using the TTY interface
Chapter 4: Configuring a BSS/RXCDR
Deleting a DYNET using the TTY interface When the last DYNET is deleted, the OMC-R automatically deletes the DYNETGroup. To delete a DYNET using the TTY interface, use the unequip command. For example, to unequip a BTS network, enter the following command: unequip 0 DYNET 1 0 The system responds: WARNING: Calls on this DYNET may be dropped. Are you sure (Y = Yes, N = No)? COMMAND ACCEPTED
4-100
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Reparenting a BSS
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-102.
•
Reparenting a BSS to a different RXCDR (same OMC-R) on page 4-105.
•
Reparenting an RXCDR to a different MSC on page 4-107.
Some reparenting procedures detailed in the following sections use cmutil. For further information about cmutil, see Chapter 15 cmutil.
Preserving SITE names The script preserve_site_names can be used to preserve site names during a reparent or drop or recreate of MIB or MIB migration. This script is available in the /usr/omc/current/sbin directory as part of the OMC-R product. To use the preserve_site_names script, follow these steps:
Procedure 4-33 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 .upd. This file should be stored in a new folder in /usr/omc/ne_data/.
2
68P02901W17-S
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
4-101 Dec 2009
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. Use OML to get the changes to take effect. The old OMC-R then loses the connection to the BSS.
•
Ensure that the OML links between the BSS and old OMC-R have been disconnected.
•
Ensure that the OML links between the BSS and the new OMC-R have been properly configured, by joining with the BSS field engineer.
•
If required, reconfigure the entries for the NE from the packet switch/MUX.
Reparenting a BSS to a different OMC-R To assign a BSS (reparent a BSS) to a different OMC-R, the BSS must be removed from its original (old) OMC-R and then added to the new OMC-R. This requires reparenting procedures at the: •
Old OMC-R.
•
New OMC-R.
Old OMC-R At the old OMC-R, proceed as follows:
Procedure 4-34 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 .op This file is required to create proxy cells, and also for keeping the site names. Continued
4-102
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Procedure 4-34
Reparenting a BSS to a different OMC-R
At the old OMC-R, reparent a BSS to a different OMC-R (Continued)
2
Locate which cells of the BSS still have external neighbors in the old OMC-R. These cells are added as proxy cells to the old OMC-R, once the BSS has been HierDeleted.
3
Create a proxy cell input file from the extracted cells in the bss_name.op file. Name the file proxycell.ip
4
If using custom SITE names, obtain the script preserve_site_names, as detailed in Preserving SITE names. As omcadmin, run the preserve_site_names script in extract mode as follows: preserve_site_names BSS This extracts the site names for the BSS to be reparented. For example: preserve_site_names BSS BSS1019 The script creates the file /usr/omc/ne_data/.upd.
5
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 This updates the site names for the BSS which has been reparented. For example: preserve_site_names update BSS1019
6
At the old OMC-R, delete the BSS/RXCDR. Refer to Deleting a BSS/RXCDR on page 4-44.
7
Add the proxy cells to the old OMC-R using the proxycell.ip file as follows: cmutil -a -i proxycell.ip
New OMC-R At the new OMC-R, proceed as follows:
Procedure 4-35
At the new OMC-R reparent the BSS
1
Create the BSS. Refer to Overview of adding a BSS or RXCDR on page 4-2. Ensure that the BSS name given when creating the new BSS on the Navigation Tree matches the name originally used in the old OMC-R.
2
Audit in the new BSS. Continued
68P02901W17-S
4-103 Dec 2009
Reparenting a BSS to a different OMC-R
Procedure 4-35 3
Chapter 4: Configuring a BSS/RXCDR
At the new OMC-R reparent the BSS (Continued)
If using custom SITE names, after the audit, copy the file /usr/omc/ne_data/ .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
This updates the site names for the BSS which has been reparented. For example: preserve_site_names update BSS1019
4-104
68P02901W17-S Dec 2009
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 that the links between the BSS and original RXCDR have been disconnected, with the help of BSS field engineer.
•
If required, reconfigure the entries for the NE from the packet switch/MUX (see ).
•
Ensure that the links between the BSS and the new RXCDR have been connected, and are in service.
•
Verify that the destination point code and originating point code are set correctly, to ensure full communication between the BSS and the MSC. Verify by using the BSS Detailed View Signaling Information grouping.
•
Verify that calls are going to the MSC.
Reparenting a BSS to a different RXCDR To reparent a BSS to a different RXCDR, follow these steps at the System Processor:
Procedure 4-36
Reparent a BSS to a different RXCDR
1
Clean up BSS - RXCDR connectivity.
2
Remove the appropriate RXCDR - Associated BSS objects from the old RXCDRs which are connected to the BSS.
3
From the engineering diagram, identify the new RXCDRs connecting to the BSS. Create the RXCDR - Associated BSS objects completing the appropriate link information.
4
If using the Map feature, proceed to Reparenting a BSS to a different RXCDR on page 4-105. If not, the procedure is finished. Continued
68P02901W17-S
4-105 Dec 2009
Reparenting a BSS to a different RXCDR
Procedure 4-36
Chapter 4: Configuring a BSS/RXCDR
Reparent a BSS to a different RXCDR (Continued)
To reparent a BSS to a different RXCDR when using the Map feature, follow these steps at the System Processor:
Procedure 4-37
Reparent a BSS to a different RXCDR when using the Map feature
1
If using the Map feature, first complete all steps in Procedure 4-36.
2
Log in to the system processor as omcadmin.
3
Open a shell and change to the temporary work directory: cd $OMC_TOP/config/local/cm_mib_db/temp_files
4
Extract the link information between the BSS to be reparented and its RXCDR: mib_env cmutil -x -h -t CommsLink -n BSS:““ -o current_links cp current_links current_links_del
5
Remove the links between the BSS and its current parent RXCDR using the following command: cmutil -d -i current_links_del
6
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.
7
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.
4-106
8
Use the following command to add the links between the BSS and its new parent RXCDR: cmutil -a -i current_links
9
When the BSS has been reparented, it is necessary to extract the BSS configuration from the MIB database as it now contains link information for the newly parented RXCDR. This is done using the procedure described in step 4 .
10
As a result of reparenting, links may have been deleted from the user-defined maps. Refer to: Adding and deleting a map link on page 13-11 for the procedure on adding links between the BSS and the new RXCDR for relevant user-defined maps.
11
The default network map is modified. The map nodes are not deleted and re-added, so the node positioning is correct. Only the map links have changed. Follow the procedure described in step 4 , to extract the new information for the network map.
12
Log out from the system processor by typing: logout
68P02901W17-S Dec 2009
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 a different MSC To move an RXCDR to a different MSC, the RXCDR must be removed from its original parent MSC and then added to the new MSC. The following prerequisites apply: •
Ensure that the links between the RXCDR and original MSC have been disconnected, with the help of BSS field engineer.
•
Ensure that the links between the RXCDR and the new MSC have been connected, and are in service.
•
Verify that the destination point code and originating point code are set correctly to ensure full communication between the BSSs under the RXCDR and the MSC. Verify by using the BSS Detailed View Signaling Information grouping.
•
Verify that calls are going to the MSC.
Reparenting RXCDR commslinks Carry out the following procedure to move an RXCDR:
Procedure 4-38
Reparent an RXCDR commslink
1
At the System Processor, log in as omcadmin.
2
Open a shell and change to the temporary work directory: cd $OMC_TOP/config/local/cm_mib_db/temp_files
3
Extract the link information between the RXCDR and RXCDR SITE and the MSC: cmutil -x -h -t CommsLink -n RXCDR:““ current_links
4
Remove the links between the RXCDR and its MSC: cmutil -d -i current_links
5
Use an editor to edit current_links and replace all instances of the old MSC_name with the new MSC_name.
6
Use the following command to check the file syntax of the file current_links. cmutil -s -i current_links If the file syntax check reveals errors, self-explanatory error messages are displayed. Continued
68P02901W17-S
4-107 Dec 2009
Reparenting RXCDR commslinks
Procedure 4-38
4-108
Chapter 4: Configuring a BSS/RXCDR
Reparent an RXCDR commslink (Continued)
7
Use the following command to add the links between the RXCDR and its new MSC: cmutil -a -i current_links
8
When the RXCDR has been moved to a new MSC, it is necessary to extract the RXCDR configuration from the MIB as it now contains new link information for the RXCDR.
9
Log out from the system processor: logout
68P02901W17-S Dec 2009
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
NOTE An f in the fifth character position of the number shown in Version column indicates a Fix Object load. For example, 06.00.f3.c4 is a Fix Object load, whereas 06.00.03.c4 is a standard load. However, the Fix Object number does not indicate the point release to which it applies, and the result returned by the disp_ver command does not show the point release information. If this information is needed, contact CNRC or the SDLC group for assistance.
Checking a single NE using the OMC-R GUI To check the software version of a single NE using the OMC-R GUI, proceed as follows:
Procedure 4-39
68P02901W17-S
Check software version of single NE
1
Open a BSS/RXCDR Detailed View from the Navigation Tree.
2
Check the setting of OMC-R/NE load version field (in the Identification parameter group) to obtain current software load version number.
3
Select Options - NE Software from the BSS/RXCDR Detailed View menu bar, to check all other load versions associated with the selected NE.
4-109 Dec 2009
Checking multiple NEs using the OMC-R GUI
Chapter 4: Configuring a BSS/RXCDR
Checking multiple NEs using the OMC-R GUI To check the software version of multiple NEs, follow these steps:
Procedure 4-40
Check software version of multiple NEs
1
Click the Load Management icon on the front panel. This displays the Software Load Management window. The software load setting is displayed in the Current Software Load column. If required, use options File à Save As to save this information to a text file.
2
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-110
68P02901W17-S Dec 2009
Chapter
5 Configuring Connectivity ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The information here shows how to check and create connectivity between a BSS and MSC (Through RXCDR), and a BSS/RXCDR and OMC-R. The following topics are described: •
Checking BSS to MSC (Through RXCDR) connectivity on page 5-2.
•
Configuring a Conn_Link on page 5-5.
•
Configuring a CommsLink using the OMC-R GUI on page 5-10.
•
Checking RXCDR/BSS to OMC-R (OML) connectivity on page 5-15.
•
DTE X.121 addresses at the OMC-R on page 5-17 - contains details of the x25_config file, which contains the DTE X.121 addresses necessary for the OMC-R to communicate with Network Elements.
•
Assigning DTE X.121 addresses at the NE on page 5-19.
•
Modifying configurations on A, M, and Mobis interfaces on page 5-22.
68P02901W17-S Dec 2009
5-1
Checking BSS to MSC (Through RXCDR) connectivity
Chapter 5: Configuring Connectivity
Checking BSS to MSC (Through RXCDR) connectivity ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
BSS to MSC connectivity BSC to RXCDR connections are tracked by engineering diagrams. They are not modeled automatically by the OMC-R MIB. However, Commslinks or Associated_BSSs can be created between the BSSs and RXCDRs to track the MMS connections. The timeslot usage, and circuit groupings can only be checked using the TTY commands.
NOTE Motorola recommends using the Generic Lookup Utility (GLU). GLU is an optional tool, available from Motorola, capable of extracting configuration information on connectivity.
Connection report Description A Connection report can be displayed for any NE, that is, any BSS or RXCDR. A Connection report displays the following information:
Table 5-1
Example Connection report for BSS1015
Connection name
NE
Device
Connected NE
Device
Conn 3:0
BSS1015
MMS 1 0
RXCDR-1
MMS 22 0
Conn 3:1
BSS1015
MMS 1 0
RXCDR-1
MMS 22 1
Conn 3:2
BSS1015
MMS 1 1
RXCDR-1
MMS 22 1
Displaying a Connection report To display a Connection report from the Navigation Tree, click the BSS or RXCDR for which the report is required, and select Connection Report from the Options menu.
Checking BSS connections Links and timeslots to the RXCDR are configured using the add_circuit and del_circuit commands. The timeslot usage of a link is not modeled at the OMC-R. To see how timeslots are configured, use the disp_mms_ts_usage command.
5-2
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Checking RXCDR connections
Checking RXCDR connections Conn_Links A Conn_Link describes the connections (links) between a BSS (BSC) and RXCDR. At the RXCDR side, the add_conn and del_conn commands configure the E1 links (Conn_Links) connected between the RXCDR and each BSS. disp_conn command lists the links connected between the RXCDR and each BSS. Each BSS has its own BSS_id. Use the BSS rdn instance (from MIB or NE.MAP file) as the BSS_id entry. Conn_Links can also be created using the OMC-GUI, see Configuring a Conn_Link on page 5-5. Up to 60 Conn_Links can exist per BSS-RXCDR connection, if any one of the following options are enabled: Increased Network Capacity, the AMR Enhanced Capacity and Half Rate options. Up to 27 Conn_Links can exist per BSS-RXCDR connection, if the Enhanced BSC Capacity feature is enabled. If none of the above features are enabled, then up to 21 Conn_Links can exist.
Timeslots The disp_mms_ts_usage command lists the incoming (from BSS) and outgoing timeslots (to MSC) through the RXCDR and gives its associated group. disp_links also lists the nailed connections through the RXCDR for features such as SMS.
Creating and extracting CommsLink details Creating CommsLinks CommsLinks can be created between the BSSs and RXCDRs to track the connections. These are OMC-R only objects and must be manually updated if a configuration changes. See Configuring a CommsLink using the OMC-R GUI on page 5-10 for details. The advantage of using CommsLinks is that all path connectivity is automatically tracked by CommsLinks. By manually configuring the BSS to RXCDR links all link information can be extracted for a particular BSS from one MIB object.
Extracting CommsLinks To extract CommsLinks details on a per object basis, or to extract all CommsLinks details, see Chapter 15 cmutil.
Checking BSS to RXCDR connectivity The BSS to RXCDR MMS data can be kept in the MIB by manually updating from the Assoc_BSS object of the RXCDR. This MIB data consists of OMC-R only objects and must be manually updated if a configuration changes.
68P02901W17-S
5-3 Dec 2009
Checking BSS to RXCDR connectivity
Chapter 5: Configuring Connectivity
To check BSS to RXCDR connectivity, proceed as follows:
Procedure 5-1
5-4
Check BSS to RXCDR connectivity
1
Create a job order to associate each BSS with RXCDR.
2
Using the Navigation Tree, create an Assoc_BSS object for each connection (see Configuring an Assoc_BSS on page 4-69). Each connection can be identified from disp_bss_conn output.
3
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
4
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 /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-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring a Conn_Link
Configuring a Conn_Link ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Creating a Conn_Link using the OMC-R GUI Prerequisites Before a Conn_Link can be created, the corresponding Assoc_RXCDR (AXCDR) or Assoc_BSS (ABSS) must exist.
Procedure If no Conn_Link exists for the MMS on the BSC, create a Conn_Link using the OMC-R GUI. Use the following procedure to create a Conn_Link:
Procedure 5-2
Create Conn_Link using the OMC-R GUI
1
Navigate to and select the Conn_Link class button in the Navigation Tree (BSS à BSS instance à Assoc_RXCDR à Assoc_RXCDR instance à Conn_Link). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object class button changes color.
2
Select Edit à Create from the Navigation Tree menu bar. The OMC-R displays the Conn_Link Detailed View in Create mode.
3
Complete the required fields. See Conn_Link Detailed View fields for details.
4
Select File à Create from the menu bar to create the Conn_Link.
5
Select File à Close from the menu bar to close the Detailed View.
Conn_Link Detailed View fields The following sections list and briefly describe the parameter fields in the Conn_Link Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
68P02901W17-S
5-5 Dec 2009
Conn_Link Detailed View fields
Chapter 5: Configuring Connectivity
Identification grouping Table 5-2 describes the fields in the Identification grouping of the Conn_Link Detailed View.
The id of the Associated RXCDR. Click to display the parent Assoc_RXCDR Detailed View.
Additional Information Use the Additional Information window to input any notes relating to this Conn_Link. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
Connectivity Information grouping Table 5-3 describes the fields in the Connectivity Information grouping of the Conn_Link Detailed View.
Table 5-3
Conn_Link Detailed View fields - Connectivity Information grouping
Field name
5-6
Brief description
Values
Mandatory or Optional?
RXCDR
Identifier of the container RXCDR.
Mandatory.
BSS
Identifier of the BSS connected to the RXCDR through this Conn_Link.
Mandatory.
Local MMS
The local MMS id for the XBL connectivity, that is, the MMS id at the site (BSS or RXCDR) at which the Conn_Link is being created.
Mandatory.
Remote MMS
The remote MMS id for the XBL connectivity, that is, the MMS id of the site between which the Conn_link is being created.
Mandatory
Connected Associated RXCDR
Id of the connected Associated RXCDR.
Mandatory.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Deleting a Conn_Link using the OMC-R GUI
Deleting a Conn_Link using the OMC-R GUI Prerequisites The connectivity for an MMS pair cannot be deleted when the Transcoding field (BSS naming convention: local_transcoding) located in the Identification section of the BSS Detailed View form, is set to Remote (0).
Other deletions required to delete a Conn_Link To delete a Conn_Link from the OMC-R GUI, it is also necessary to delete the following: •
The contained XBLs.
•
All the CICs equipped on the MMS used by the Conn_Link connectivity.
Procedure To delete a Conn_Link using the OMC-R GUI, see the general procedure in Deleting a network object using the OMC-R GUI on page 1-37.
Adding a Conn_Link using the TTY interface Prerequisites Before arbitrarily numbering the BSCs connected to the RXCDR, the XBL must have been equipped at the BSC and the RXCDR. This is so that different BSCs can be distinguished from the RXCDR.
68P02901W17-S
5-7 Dec 2009
Displaying connectivity using the TTY interface
Chapter 5: Configuring Connectivity
Adding connectivity - add_conn command For correct XBL operation, network connectivity information must be supplied in the database SYSGEN using the add_conn command. The add_conn command adds MMS connectivity between the RXCDR and the BSS. Connectivity may be added for a maximum of 21 MMSs at a BSC or RXCDR regardless of how many RXCDRs or BSSs are connected. If the Enhanced BSC Capacity feature is enabled, connectivity can be added for up to 27 MMSs.
NOTE The add_conn command can also be used outside of SYSGEN. This command allows the operator to specify the E1 connectivity information identifying which RXCDR is associated with the E1 link and the device identity within the RXCDR to which the E1 link is connected. This connectivity information must be specified for each E1 link connecting to an RXCDR. Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete information on the add_conn command.
Displaying connectivity using the TTY interface To display the contents of the XBL connectivity, at the RXCDR site, use the disp_conn command.
Deleting a Conn_Link using the TTY interface del_conn command To delete a particular connection between an MMS at the BSC and an MMS at the RXCDR, use the DEL_CONN command. Connectivity may not be removed for an MMS pair if the BSC is operating in static mode and CICs are statically assigned to that MMS pair. This only applies to remote transcoding BSC and RXCDR sites. Refer to: Technical Description: BSS Command Reference (68P02901W23) for complete information on the del_conn command.
Example of deleting a Conn_Link The following example deletes connectivity information for MMS 4 0 at the BSC: del_conn 4 0 The following example deletes connectivity information for MMS 3 0 at the RXCDR: del_conn 3 0
5-8
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Deleting a Conn_Link using the TTY interface
Other deletions required to delete a Conn_Link To delete a Conn_Link, it is also necessary to delete the following: •
The contained XBLs.
•
All the CICs equipped on the MMS used by the Conn_Link connectivity.
68P02901W17-S
5-9 Dec 2009
Configuring a CommsLink using the OMC-R GUI
Chapter 5: Configuring Connectivity
Configuring a CommsLink using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to configuring a CommsLink This section describes how to configure a CommsLink using the OMC-R GUI. To add and delete links to existing sites using cmutil, see Chapter 15 cmutil.
Autocreation and deletion of CommsLinks If a CommsLink does not exist, when a Conn_Link is created between a BSC and an RXCDR, the CommsLink is automatically created in the CM MIB to represent the point-to-point links between BSSs and RXCDRs, and the Conn_Link added to it.
NOTE The CommsLink is created only after validating the end nodes, the container BSC/RXCDR and the associated RXCDR/BSC. Auto-created CommsLinks can only be auto-deleted. Manually created CommsLinks can only be manually deleted. Manually deleted CommsLinks do not delete corresponding Conn_Links or paths.
Creating a CommsLink using the OMC-R GUI Prerequisites for creating a CommsLink A CommsLink can only be created if the two nodes it connects have been defined in advance.
Procedure To create a CommsLink using the OMC-R GUI, use the following procedure:
5-10
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Procedure 5-3
68P02901W17-S
Creating a CommsLink using the OMC-R GUI
Create a CommsLink using the OMC-R GUI
1
Navigate to and select the CommsLink class button in the Navigation Tree. If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object class button changes color.
2
Click the folder icon next to the CommsLink class button. The OMC-R displays the CommsLink List window as shown in Figure 5-1 for GPRS networks.
3
Select Edit à Create from the Navigation Tree menu bar. A CommsLink Detailed View window is displayed.
4
Complete the Name field, preferably choosing a name relating to the two nodes the link connects, separated by a hyphen (-).
5
To input a node name, click the Node A button. A Navigation Tree is displayed. Navigate through the Navigation Tree in the usual way, and when the required network element is reached, double-click the left mouse button. This NE is recorded as node A in the Node A field.
6
Repeat step 5 for Node B at the other end of the CommsLink.
7
Select File à Create from the menu bar.
8
Close the Detailed View window by selecting File à Close from the menu bar, and by selecting OK from the subsequent Confirmation window.
5-11 Dec 2009
CommsLink Detailed View fields
Figure 5-1
Chapter 5: Configuring Connectivity
CommsLink List showing GPRS links
ti-GSM-CommsLinkListshowingGPRSlinks-00787-ai-sw
CommsLink Detailed View fields The following sections list and briefly describe the parameter fields in the CommsLink Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
5-12
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Filtering the CommsLink list window
Identification grouping Table 5-4 describes the fields in the Identification grouping of the CommsLink Detailed View.
A CommsLink has two end points, A and B. This is the object at point A. Click to display the Detailed View of Node A.
Mandatory.
Node B
A CommsLink has two end points, A and B. This is the object at point B. Click to display the Detailed View of Node B.
Mandatory.
Parent Detailed View
Displays the name of the parent. Click to display the Detailed View of the parent. A CommsLink can only have the network as a parent.
Map Information grouping Table 5-5 describes the fields in the Identification grouping of the CommsLink Detailed View.
Table 5-5
CommsLink Detailed View fields - Map Information grouping
Field name Service State
Brief description
Values
The state of a node or link on a map.
INS, OOS or Unknown.
Mandatory or Optional? Optional.
CommsLink Related Devices grouping Displays the devices related to this CommsLink. The Name, Operational State, and Administration state of each device is displayed.
Filtering the CommsLink list window For anything other than a very small network, the number of links in the CommsLink list window grows to a large number. This makes it difficult to find a particular link when sites are being modified and the CommsLink Detailed View is to be edited. The filtering feature can be used to help.
68P02901W17-S
5-13 Dec 2009
Deleting a CommsLink using the OMC-R GUI
Chapter 5: Configuring Connectivity
To filter for links between two nodes, proceed as follows:
Procedure 5-4
Apply filter for links between two nodes
1
From the Navigation Tree, click the folder icon next to the CommsLink type button. The CommsLink list is displayed.
2
Click the Node A button. The Navigation Tree is displayed.
3
Double-click one of the nodes that is attached to one end of the link to be accessed.
4
Click the Node B button. The Navigation Tree is redisplayed.
5
Double-click the node that is attached to the other end of the link to be accessed.
6
Click the Apply Filter button.
Only the links that are configured between the two selected nodes are now displayed in the CommsLink list.
Deleting a CommsLink using the OMC-R GUI To delete a Commslink using the OMC-R GUI, use the following procedure:
Procedure 5-5
5-14
Delete a Commslink using the OMC-R GUI
1
Navigate to and select the CommsLink class button in the Navigation Tree. If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The network object class button changes color.
2
Click the folder icon next to the Commslink class button, to display the Commslink List window.
3
Select the Commslink to be deleted. The selection is highlighted.
4
Select Edit à Delete from the menu bar. A confirmation window is displayed.
5
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.
6
Close the Commslink List window by selecting File à Close from the menu bar.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Checking RXCDR/BSS to OMC-R (OML) connectivity
Checking RXCDR/BSS to OMC-R (OML) connectivity ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview to OML connectivity Checking RXCDR/SS to OMC-R (OML) connectivity can be carried out using one of two methods: •
Checking OMLs for a single NE using the OMC-R GUI.
•
Checking OMLs for multiple NEs using SQL.
To create an OML see Configuring an OML device on page 9-159.
Checking OMLs for a single NE using the OMC-R GUI To check OMLs for a single NE using the GUI, proceed as follows:
Procedure 5-6
Check OMLs for a single NE using the GUI
1
Open a Navigation Tree to show OMLs (BSS - SITE - - Logical links - OML).
2
Check number of configured OMLs. There are usually two OMLs configured (one active and one standby).
3
Open the Detailed Views and check the associated MMS id and timeslot. The MMSs of the active and standby OMLs are usually equipped in slots 16 and 14 of the BSC cage. This allows utilization of the dual OML feature which speeds up software downloads.
Checking OMLs for multiple NEs using SQL Use SQL to get the information for all OMLs in the MIB. Use the following example SQL query procedure to extract the state (whether it is active or standby or OOS), and MMS configuration information for all OMLs in the OMC-R:
68P02901W17-S
5-15 Dec 2009
Checking OMLs for multiple NEs using SQL
Procedure 5-7
Chapter 5: Configuring Connectivity
Check OMLs for multiple NEs using SQL
1
Create the following script: select bsstable2.name BSC, sitetable2.name SITE, omltable2.rdninstance RDN, omltable2.opstate opstate, omltable2.adminsate adminstate, omltable2.msi_id MSI, omltable2.mms_id MMS, omltable2.timeslot TIMESLOT from omltable2, sitetable2, bsstable2 where omltable2.containerinstrite = sitetable2.oidinstrite and omltable2.containerinstleft = sitetable2.oidinstleft and sitetable2.containerinstrite = bsstable2.oidinstrite and sitetable2.containerinstleft = bsstable2.oidinstleft order by BSC, SITE, RDN
2
Create a file called oml.sql with this query.
3
As an omcadmin user, enter: mib_env isql mib_16xx oml.op Where mib_16xx is the name of the database. The file called oml.op contains all the data for analysis or further parsing.
5-16
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
DTE X.121 addresses at the OMC-R
DTE X.121 addresses at the OMC-R ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to DTE X.121 addresses For the OMC-R to communicate with the various network elements, certain addresses must be set at the OMC-R in the x25_config file. Initial addresses are assigned during staging and need not be altered. When new network elements are added, the new addresses of the network elements are added to the x25_config.
x25_config file location The OMC-R X.121 addresses are stored in the x25_config file, located at /usr/omc/config/global on the system processor.
x25_config file fields Each line in this file contains eleven fields, each separated by a space. The fields are:
Record number within the file.
X.25 channel number (specified as x25_chan).
no.>
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.
addr.>
Interface identifier. 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.
call char>
process>
Type of X.25 application process which may be any of the following: OMC_BL Bootload. OMC_EI Event Interface. OMC_RL Remote Login. OMC_PU Upload.
Protocol being used by a process. The only valid value in this field is X.25.
Packet size.
Window size.
Timeout value.
68P02901W17-S
5-17 Dec 2009
x25_config file entries
Chapter 5: Configuring Connectivity
x25_config file entries Each entry associates an X.121 DTE address with a sync controller port on the system processor. The contents of a typical file are shown in Figure 5-2.
Sun For the HSI configuration, the link numbers in the x25_config file must correspond to the Sunlink X.25 link numbers. A typical x25_config file for the Sun HS/IS is shown in Figure 5-2.
Installation and Configuration: GSM System Configuration
Assigning DTE X.121 addresses at the NE
Assigning DTE X.121 addresses at the NE ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to assigning DTE X.121 addresses The X.121 address of the NE and the X.121 addresses of the OMC-R must be assigned at the NE. The purpose of the address is to verify the calling address on the inbound X.25 packet. The NE rejects any connections where the address does not match. For further details of DTE X.121 addresses, see DTE X.121 addresses at the OMC-R on page 5-17.
Setting X.121 addresses To set all X.121 addresses at the NE, arrange for the changes to be entered at the NE using a PC.
Slot: port settings for OMLs In RAM, only address 0 is used. In ROM, however, the addresses are link dependent. Table 5-6 shows the slot: port settings for the 2 Mbit/s link carrying the OMLs. In ROM mode, the site uses link number 0 by default, if this is not available then it uses link number 1, if this link does not work it uses link number 2 and, finally, link number 3. Table 5-6 should be used in conjunction with the subsequent procedures.
Table 5-6
Slot: port settings for OML link
link_num
RXCDR (slot: port)
BSS (slot: port)
0
10:0
16:0
1
10:1
16:1
2
8:0
14:0
3
*10:0 (*denotes cage 2)
*16:0 (*denotes cage 2)
Setting OML addresses using the TTY interface Set the OML(s) DTE addresses (0 to 3) with reference to Table 5-6.
68P02901W17-S
5-19 Dec 2009
OMC-R addresses - general rules
Procedure 5-8 1
Chapter 5: Configuring Connectivity
Set OML(s) DTE addresses
Set the DTE addresses using the command: chg_dte bsc .... 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
2
Verify the value set using the disp_dte command.
NOTE The address in bsc 0 must always be set, even if the primary OMC-R connection is not used. The bsc 0 address is used by the BSC or RXCDR in RAM. The slot number refers to the MSI board which carries the OML in the BSC cabinet and the port number refers to the MMS.
For full details of BSS commands, refer to Technical Description: BSS Command Reference (68P02901W23).
OMC-R addresses - general rules The general rules for the OMC-R addresses can be summarized as follows: •
Always 14 digits for the address length.
•
Address byte(s): 1, 2 and 3 are the country code. 4 and 5 are the network code. 6 and 7 indicate the location and are set at staging. 8 is equipment type (BSS = 1, RXCDR = 2, OMC-R = 3). 9 and 10 are the number of the OMC-R, that is, 01 is the first, 02 the second, and so on. 11 is the sync controller board at the OMC-R and can be 0 or 1. 12 is the port on the sync controller board and can be 0, 1, 2 or 3 representing ports a, b, c or d.
5-20
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
•
OMC-R addresses - general rules
13 and 14 identify the address usage, and are allocated as follows: 41 – Event/alarm Interface 42 – Event/alarm interface 61 – Download/Bootload 62 – Download/Bootload 99 – Upload 00 – Rlogin
68P02901W17-S
5-21 Dec 2009
Modifying configurations on A, M, and Mobis interfaces
Chapter 5: Configuring Connectivity
Modifying configurations on A, M, and Mobis interfaces ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to A, M, Mobis interfaces The A interface signaling link is the link between the MSC and the RXCDR. The M interface signaling link is the link between the RXCDR and the BSC. The Mobis interface signaling link is the link between the BSC and the BTS. The devices available on the A and M interfaces are the Message Transfer Link (MTL) and the Transcoder-Base Station Link (XBL). The devices/functions available on the Mobis interface are Radio Signaling Link (RSL) and Receive Transmit Function (RTF).
Methods for modifying configurations on A, M, and Mobis interfaces Generally, modifying configurations on the A, M and Mobis interfaces must be performed using the TTY interface, although the Equip Function RTF option is available from the Configuration menu of the BSS MML Command Constructor window.
Prerequisites to modifying A, M, and Mobis interfaces
NOTE The following have to be noted when modifying interfaces: •
Before any modification of an interface, display the current status of that interface using either the display features of the BSS MML Command Constructor window, or the TTY interface commands such as disp_traffic or disp_mms_ts_usage
•
Implement the required configuration changes from the TTY interface using the equip, add_conn and chg_ts_usage commands, although there is some functionality available from the OMC-R GUI.
Refer to: OMC-R Online Help, Network Operations for information on displaying the status using the BSS MML Command Constructor window. Full details of the syntax for these TTY commands can be found in: Technical Description: BSS Command Reference (68P02901W23).
5-22
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displaying interface status
Displaying interface status The interface status can be displayed using the BSS MML Command Constructor window, or the TTY interface, using MMI commands. Commands available to display the status of the interfaces are: •
disp_traffic to display all traffic equipped to a particular path device, that is, all RSL devices and RTF devices (Mobis interface).
•
disp_mms_ts_usage to display the utilization of all timeslots for a specified 2 Mbit/s link. This gives the status of each timeslot in the form unallocated/allocated to RSL, allocated to RTF and reserved, and Dynet timeslot or shared timeslot.
Equipping and unequipping A and M interfaces using the TTY interface To alter the configuration of the devices/functions on the A and M interfaces, use the following commands: unequip MTL equip MTL For the M interface only, use: unequip XBL equip 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 RSL equip RSL or unequip RTF equip RTF
68P02901W17-S
5-23 Dec 2009
Modifying the Mobis interface using the TTY interface
Chapter 5: Configuring Connectivity
Reserving a timeslot Timeslots on specified E1 links can be barred from use by a BSS, that is reserved for other uses. To reserve timeslots the chg_ts_usage reserve command is used (refer to: Technical Description: BSS Command Reference (68P02901W23) for full details of the syntax). To illustrate the steps required to use the command refer to the following example: For example, to reserve the range of timeslots between 6 and 9 at BTS 12 for MMS 1 0, follow these steps:
Procedure 5-9
Reserve a timeslot
1
Remotely login to the BSS and change security levels, see Remotely logging in to a BSS site from the OMC-R on page 1-39.
2
Enter the following command:chg_ts_usage reserve 12 1 0 6 9
Freeing a timeslot - at the same site To free timeslots that have been reserved or nailed at the same site, use the chg_ts_usage free command (refer to: Technical Description: BSS Command Reference (68P02901W23) for full details). For example, to free the range of timeslots between 6 and 9 at BTS 12 for MMS 1 0, follow these steps:
Procedure 5-10
Free a timeslot at the same site
1
Remotely login to the BSS and change security levels, see Remotely logging in to a BSS site from the OMC-R on page 1-39.
2
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
5-24
Free a timeslot between different sites
1
Remotely login to the BSS and change security levels, see Remotely logging in to a BSS site from the OMC-R on page 1-39.
2
Enter the following command: chg_ts_usage free_path 3 0 0 1 0 5 3 0 1 7 1
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Modifying the Mobis interface using the TTY interface
Adding a nailed connection Nailed connections can be added to enable third party non-GSM calls to be connected through GSM nodes. A nailed connection can be established between two timeslots at the same site or different sites. To nail connections between two timeslots at the same site the chg_ts_usage nail command is used. To nail connections between two timeslots at different sites the chg_ts_usage nail_path command is used.
NOTE Full syntax details of the chg_ts_usage command are in the Technical Description: BSS Command Reference (68P02901W23) manual. To illustrate the steps required to use the command, refer to the following examples. Example 1: To nail timeslots 5 to 8 of MMS 1 0 to timeslots 7 to 10 of MMS 0 1 at the same site.
Procedure 5-12
Nail a timeslot
1
Remotely login to the BSS and change security levels, see Remotely logging in to a BSS site from the OMC-R on page 1-39.
2
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
68P02901W17-S Dec 2009
Nail a path
1
Remotely login to the BSS and change security levels, see Remotely logging in to a BSS site from the OMC-R on page 1-39.
2
Enter the following command: chg_ts_usage nail_path 3 0 0 1 0 5 3 0 1 7 1
5-25
Modifying the Mobis interface using the TTY interface
5-26
Chapter 5: Configuring Connectivity
68P02901W17-S Dec 2009
Chapter
6 Configuring a PCU for GPRS ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The procedures here show how to configure a PCU (for GPRS) and its devices. The following topics are described: •
Introduction to the PCU and its devices on page 6-2.
•
Overview of configuring a PCU and its devices on page 6-6.
•
Configuring a PCU using the OMC-R GUI on page 6-8.
•
Displaying and modifying PCU cabinet details on page 6-16.
•
Displaying and modifying PCU cage details on page 6-17.
•
Configuring a DPROC using the OMC-R GUI on page 6-18.
•
Displaying and modifying PSP details on page 6-22.
•
Configuring a PCU MSI using the OMC-R GUI on page 6-24.
•
Displaying and modifying PCU MMS details on page 6-27.
•
Configuring a GDS using the OMC-R GUI on page 6-29.
•
Configuring a GSL using the OMC-R GUI on page 6-34.
•
Configuring a GBL using the OMC-R GUI on page 6-38.
•
Configuring a GSL using the OMC-R GUI on page 6-34.
•
Configuring an SGSN (GPRS) using the OMC-R GUI on page 6-49.
•
Configuring the PCU and its devices from the TTY interface on page 6-52.
68P02901W17-S Dec 2009
6-1
Introduction to the PCU and its devices
Chapter 6: Configuring a PCU for GPRS
Introduction to the PCU and its devices ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Overview of GPRS GPRS is a service which allows for the packet-mode transmission of data within a GSM network. Using GPRS, an MS can send and receive data in an end-to-end packet transfer mode. GPRS enables a more cost effective and efficient use of network resources for data transfer.
Introduction to PCU GSM Packet Radio Service (GPRS) functionality needs a Packet Control Unit (PCU) to manage the packet radio interface and link the Serving GPRS Support Node (SGSN) into each GSM BSC. The SGSN is connected to the PCU by the Gb link (GBL). PCUs are located at the BSS, and up to three PCU can be equipped, with identifiers in the range 0 - 2. PCUs and SGSN are visible in the OMC-R GUI once they have been configured.
List of PCU contained devices A PCU has the following contained devices: •
Hardware devices: Cabinet. Cage. Processors: ◊
DPROC (types: PICP and PRP).
◊
PSP.
MSI: ◊
•
MMS.
Logical Links: GDS (types: TRAU and LAPD) GSL GBL NSVC
6-2
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
PCU equipage hierarchy chart
PCU equipage hierarchy chart Figure 6-1 shows the device and equipment hierarchy for a PCU. It shows that a Cabinet and a Cage are created (also referred to as equipped) automatically when a PCU is created using the TTY or OMC-R GUI interface. An MMS is automatically created when an MSI is created using the TTY or GUI interface.
68P02901W17-S
6-3 Dec 2009
PCU equipage hierarchy chart
Figure 6-1
Chapter 6: Configuring a PCU for GPRS
Device and equipment hierarchy for a PCU BSC
PCU
PCU
PCU
CAB1
CAGE1
PSP1
DPROC (PICP)
MSI
MMS2
DPROC (PRP)
MSI
MMS2
GDS (TRAU)
GBL
GDS (TRAU)
GDS (LAPD)
GSL
LEGEND 1 indicates automatically equipped device, when a PCU is equipped. 2 Indicates automatically equipped device, when an MSI is equipped. ti-GSM-DeviceandequipmenthierarchyforaPCU-00789-ai-sw
6-4
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
PCU contained devices in the Navigation Tree
PCU contained devices in the Navigation Tree Figure 6-2 shows an example of PCU containment as shown in the Navigation Tree.
PCU contained devices to be equipped When a PCU device is equipped, the contained devices shown in Table 6-1 must also be equipped/created.
Table 6-1
68P02901W17-S
PCU contained devices Contained device
Device acronym
Data Processor
DPROC.
PCU System Processor
PSP.
GPRS Data Stream
GDS.
GPRS Signaling Link
GSL.
Multiple Serial Interface board
MSI.
Gb Link
GBL.
Network Service Virtual Connection
NSVC.
6-5 Dec 2009
Overview of configuring a PCU and its devices
Chapter 6: Configuring a PCU for GPRS
Overview of configuring a PCU and its devices ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Recommended method for configuring a PCU The recommended method for configuring a PCU is to: 1.
Install the PCU equipment.
2.
Create a batch_rlogin script file containing equip commands for each of the required PCU devices and functions. See Configuring the PCU and its devices from the TTY interface on page 6-52 for guidance.
3.
Load the batch_rlogin script file into the BSS database.
4.
Run an audit at the OMC-R. The PCU and its devices then appear in the OMC-R GUI Navigation Tree.
Creating a batch_rlogin script file is also recommended for creating a BTS.
Other PCU configuration methods A PCU and its contained devices can be configured using any of the following methods: •
OMC-R GUI, specifically the Navigation Tree, see Configuring a PCU using the OMC-R GUI on page 6-8.
•
From the OMC-R, log in to a BSC remotely (rlogin) and then use the TTY interface, see Configuring the PCU and its devices from the TTY interface on page 6-52.
•
Using the MMI interface and TTY interface locally at the BSC, see Configuring the PCU and its devices from the TTY interface on page 6-52.
Locking, unlocking, and other event and fault management activities are described in: OMC-R Online Help, Network Operations.
6-6
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Recommended list of PCU configuration procedures
Recommended list of PCU configuration procedures When creating a PCU and its contained devices, perform the procedures in the following order: 1.
Create a PCU using the Navigation Tree (seeConfiguring a PCU using the OMC-R GUI on page 6-8) or the equip command (see Configuring the PCU and its devices from the TTY interface on page 6-52).
2.
Create an SGSN using the Navigation Tree (see Configuring an SGSN (GPRS) using the OMC-R GUI on page 6-49).
3.
If necessary, modify any PCU Cabinet details, see Displaying and modifying PCU cabinet details on page 6-16.
4.
If necessary, modify any PCU Cage details, see Displaying and modifying PCU cage details on page 6-17.
5.
Create a DPROC, see Configuring a DPROC using the OMC-R GUI on page 6-18 or Configuring the PCU and its devices from the TTY interface on page 6-52.
6.
Modify a PSP, see Displaying and modifying PSP details on page 6-22 or Configuring the PCU and its devices from the TTY interface on page 6-52.
7.
Create an MSI, see Configuring a PCU MSI using the OMC-R GUI on page 6-24 or Configuring the PCU and its devices from the TTY interface on page 6-52.
8.
Create an MMS, see Displaying and modifying PCU MMS details on page 6-27 or Configuring the PCU and its devices from the TTY interface on page 6-52.
9.
Create a GDS, see Configuring a GDS using the OMC-R GUI on page 6-29 or Configuring the PCU and its devices from the TTY interface on page 6-52.
10. Create a GSL, see Configuring a GSL using the OMC-R GUI on page 6-34 or Configuring the PCU and its devices from the TTY interface on page 6-52. 11. Create a GBL, see Configuring a GBL using the OMC-R GUI on page 6-38 or Configuring the PCU and its devices from the TTY interface on page 6-52. 12. Create an NSVC, see Configuring an NSVC using the OMC-R GUI on page 6-43 or Configuring the PCU and its devices from the TTY interface on page 6-52.
68P02901W17-S
6-7 Dec 2009
Configuring a PCU using the OMC-R GUI
Chapter 6: Configuring a PCU for GPRS
Configuring a PCU using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to configuring a PCU using the OMC-R GUI A PCU can be added to the network using the OMC-R GUI Navigation Tree. Up to three PCUs can exist at a BSS. A PCU can be locked, unlocked, INS, and reset from the OMC-R GUI. See OMC-R Online Help, Network Operations for further details. When a PCU is created, the OMC-R automatically creates a: •
Cage, see Displaying and modifying PCU cage details on page 6-17.
•
Cabinet, see Displaying and modifying PCU cabinet details on page 6-16.
•
PSP 0 and PSP 1, see Displaying and modifying PSP details on page 6-22.
SYSGEN mode cannot be exited if a PCU has been created but a PSP has not been created for it.
Prerequisites for configuring a PCU using the OMC-R GUI Before configuring a PCU, ensure that the: •
GPRS Feature field (BSS parameter name: gprsOpt) in the associated BSS Detailed View form is set to Enabled (1). If this is not enabled, the PCU is not displayed in the Navigation Tree.
•
Land Layer 1 Mode field (BSS parameter name: ManagedNENode::landLayer1Mode) in the associated BSS Detailed View form is set to CEPT (E1) (0), which is the default. This parameter can only be changed in SYSGEN mode.
Creating a PCU using the OMC-R GUI To add a PCU to the network using the OMC-R GUI, follow these steps:
Procedure 6-1
Add a PCU to the network using the OMC-R GUI
1
Navigate to and select the PCU class button in the Navigation Tree (BSS à BSS instance à PCU). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The PCU class button changes color.
2
Select Edit à Create from the menu bar. The OMC-R displays the PCU Detailed View in Create mode. Continued
6-8
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Procedure 6-1
PCU Detailed View fields
Add a PCU to the network using the OMC-R GUI (Continued)
3
Complete the fields, as required. See PCU Detailed View fields for details.
4
Select File à Create from the menu bar.
5
Close the PCU Detailed View window by selecting File à Close from the menu bar.
PCU Detailed View fields The following sections list and briefly describe the parameter fields in the PCU Detailed View according to their parameter grouping.
NOTE •
To obtain further detailed information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
•
The PCU Detailed View shows all cells that are currently mapped to the PCU.
Identification grouping Table 6-2 describes the fields in the Identification grouping of the PCU Detailed View.
The unique PCU name. This name must be unique to the OMC-R. If a PCU is created during an audit, the OMC-R auto-generates a name for the PCU.
RDN Class
See description in Table 4-1.
Default is PCU.
{27955A} RDN Instance
See description in Table 3-1.
0.
NMC RDN Value
See description in Table 4-1.
Parent Detailed View
Click to display the parent BSS Detailed View.
68P02901W17-S
Values Up to 31 characters. Format of an auto-generated PCU name is: :PCU-0.
Mandatory or Optional? Mandatory.
6-9 Dec 2009
PCU Detailed View fields
Chapter 6: Configuring a PCU for GPRS
Additional Information Use the Additional Information window to input any notes relating to this PCU. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
State grouping Standard network object state fields, see Table 4-2 for details.
Alarm Information grouping Table 6-3 describes the fields in the Alarm Information grouping of the PCU Detailed View. The alarm information is used for all MSIs within this container.
Table 6-3
PCU Detailed View fields - Alarm Information grouping
Field name
6-10
Mandatory or Optional?
Brief description
Values
MSI Remote Loss Daily Alarm Level
The number of alarms in this level.
0 - 65535. Default is 16.
Mandatory.
MSI Remote Loss Hourly Alarm Level
The number of alarms in this level.
0 - 65535. Default is 20.
Mandatory.
MSI Remote Loss OOS Alarm Level
The number of alarms in this level.
0 - 65535. Default is 511.
Mandatory.
MSI Remote Time OOS Alarm Level
The number of alarms in this level.
0 - 65535. Default is 25.
Mandatory.
MSI Remote Time Restoral Time
Each step is 100 ms.
0 - 65535. Default is 600.
Mandatory.
MSI Sync Loss Daily Alarm Level
The number of alarms in this level.
0 - 65535. Default is 16.
Mandatory.
MSI Sync Loss Hourly Alarm Level
The number of alarms in this level.
0 - 65535. Default is 20.
Mandatory.
MSI Sync Loss OOS Alarm Level
The number of alarms in this level.
0 - 65535. Default is 511.
Mandatory.
MSI Sync Loss Time OOS Alarm Level
The number of alarms in this level.
0 - 65535. Default is 25.
Mandatory.
MSI Sync Loss Restoral Time (time)
Each step is 100 ms.
0 - 65535. Default is 600.
Mandatory.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
PCU Detailed View fields
BSSGP Information grouping Table 6-4 describes the fields in the BSSGP Information grouping of the PCU Detailed View.
Table 6-4
PCU Detailed View fields - BSSGP Information grouping
Field name
Mandatory or Optional?
Brief description
Values
T1 (Un)Blocking Guard Timer
The guard timer used for cell blocking and unblocking procedures with the SGSN.
1 - 120 Seconds. Default is 3.
Mandatory.
T2 Reset Guard Timer
The guard timer used during Reset procedures with the SGSN (BSSGP T2).
1 - 120 Seconds. Default is 60.
Mandatory.
Cell Block Retry Messages
Number of retries for a cell block message to the SGSN.
1 - 3. Default is 3.
Mandatory.
Cell Unblock Retry Messages
Number of retries for a cell unblock message to the SGSN.
1 - 3. Default is 3.
Mandatory.
Cell Reset Retry Messages
Number of retries for a cell reset message to the SGSN.
1 - 3. Default is 3.
Mandatory.
Flow Control Period
Configures flow control frequency from the PCU to the SGSN.
1 - 1000 tenths of seconds. Default is 10.
Mandatory.
RA Capability Update Retries
Number of retries the BSS generates for RA-Capability-Update messages to the SGSN.
1 - 3. Default is 3.
Mandatory.
Gb Mapping Information and Air Interface grouping Table 6-5 describes the fields in the Gb Mapping Information grouping of the PCU Detailed View.
Table 6-5
PCU Detailed View fields - Gb Mapping Information grouping
Field name/ parameter name Signaling BVCI
Brief description
Values
Mandatory or Optional?
The signaling BSSGP Virtual Connection Identifier (BVCI) for the BSS. Cannot be modified if gprs_enabled is Enabled (1) for any cells in the BSS.
0 - 65535.
Mandatory.
Continued
68P02901W17-S
6-11 Dec 2009
PCU Detailed View fields
Chapter 6: Configuring a PCU for GPRS
Table 6-5
PCU Detailed View fields - Gb Mapping Information grouping (Continued)
Field name/ parameter name
Brief description
Network Operation Mode Whether a GS is present (OMC-R parameter name: between the MSC and gprs_net_op_mode the SGSN. BSS parameter name: gprs_network_operation_mode)
Values 1 or 3.1 - the network sends a CS paging message for a GPRS attached mobile on the GPRS paging channel, which is the PCH or the PPCH depending on whether there is a PCCCH in the cell, or on a GPRS PDTCH.3 - if allocate, the network sends CS pages for a GPRS attached mobile on the CCCH and PS pages on the PCCC., Default is 3. Cannot be set to a value of 2.
Mandatory or Optional? Mandatory.
Gb Statistics Configuration grouping Table 6-6 describes the fields in the Gb Statistics Configuration grouping of the PCU Detailed View.
Field name/ parameter name PCU MMS Configuration Type
Values
Brief description The type of connection wanted for the TELCO connection.
0 or 1. For CEPT(E1): Timeslot 0 multiframe (CRC is on) (0), No timeslot 0 multiframe (CRC is off).
Mandatory or Optional? Mandatory.
NS Information grouping Table 6-7 describes the fields in the NS Information grouping of the PCU Detailed View.
Table 6-7
PCU Detailed View fields - NS Information grouping
Field name
Values
Brief description
Mandatory or Optional?
NSVC (Un)Block Guard Timer
Guards the NS-VC blocking and unblocking.
1 - 30 (Seconds). Default is 3.
Mandatory.
NSVC Reset Guard Timer
Guards the NS-VC reset procedure.
1 - 120 (Seconds). Default is 40.
Mandatory.
NSVC Test Period
The period of NS-VC test procedure.
1 - 60 (Seconds). Default is 30.
Mandatory.
NSVC Test Guard Timer
Guards the NS-VC test procedure.
1 - 30 (Seconds). Default is 3.
Mandatory.
NSVC Block Retry Messages
The number of retries when attempting to block an NS-VC.
1 - 3. Default is 3.
Mandatory.
NSVC Unblock Retry Messages
The number of retries when attempting to unblock an NS-VC.
1 - 3. Default is 3.
Mandatory.
NSVC Alive Retry Messages
The number of retries generated when establishing whether an NS-VC is alive.
1 - 10. Default is 3.
Mandatory.
NSVC Reset Period
The period during which the PCU attempts to reset an NS-VC.
1 - 250 (Seconds). Default is 125.
Mandatory.
Network Service Entity Identifier nsei
The NSEI used by the PCU over the Gb Interface.
0 to 65535.
Mandatory.
Map Information grouping Standard map information fields, see Table 4-15 for details.
68P02901W17-S
6-13 Dec 2009
Modifying PCU details from the OMC-R GUI
Chapter 6: Configuring a PCU for GPRS
Address Information grouping Table 6-8 describes the fields in the Address Information grouping of the PCU Detailed View.
Table 6-8
PCU Detailed View fields - Address Information grouping
Field name/ parameter name
Mandatory or Optional?
Brief description
Values
IP Address ip_address
The Internet Protocol (IP) address of the PCU. Used by the WebMMI facility, see Remotely logging in to a BSS using WebMMI on page 1-45.
0.0.0.0 to 223.255.255.255. Default: 127.0.0.1.
Optional.
Subnet Mask subnet_mask
The subnet mask to use with Internet Protocol (IP). Used by the WebMMI facility, see Remotely logging in to a BSS using WebMMI on page 1-45.
0.0.0.0 to 255.255.255.255. Default: 255.255.255.255.
Optional.
Router IP Address router_ip_address
The IP address of the default router when sending IP data. Used by the WebMMI facility, see Remotely logging in to a BSS using WebMMI on page 1-45.
0.0.0.0 to 223.255.255.255. Default: 127.0.0.1.
Optional.
Quality of Service (QoS) grouping See Quality of Service (QoS) on page 2-157 for further details of the PCU parameters in this grouping.
Modifying PCU details from the OMC-R GUI To modify PCU details from the Navigation Tree, see the general procedure described in Modifying a network object using the OMC-R GUI on page 1-34.
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.
6-14
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Deleting a PCU using the OMC-R GUI
Deleting a PCU using the OMC-R GUI Deleting a PCU also deletes all PCU contained devices. To delete a PCU from the Navigation Tree, see the general procedure in Deleting a network object using the OMC-R GUI on page 1-37.
Prerequisites to deleting a PCU Before deleting a PCU, ensure that: •
GPRS Enabled field (BSS parameter name: gprs_enabled) in all the associated CELL Detailed View forms is set to False (0). Use the cell propagation facility options in the CELL Detailed View menu bar to propagate changes to other cells.
•
Land Layer 1 Mode field (BSS parameter name: ManagedNENode::landLayer1Mode) in the associated BSS Detailed View form is set to (CEPT (E1) (0)), which is the default. This parameter can only be changed in SYSGEN mode.
•
All GDSs and GSLs have been deleted.
68P02901W17-S
6-15 Dec 2009
Displaying and modifying PCU cabinet details
Chapter 6: Configuring a PCU for GPRS
Displaying and modifying PCU cabinet details ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to displaying and modifying PCU cabinet details When a PCU is created, the OMC-R automatically creates a PCU cabinet. Likewise when a PCU is deleted, the OMC-R automatically deletes the PCU cabinet. A cabinet is a child of a PCU (and can also be a child of a site). A PCU cabinet cannot be created from the OMC-R Navigation Tree. However, details of the PCU cabinet can be displayed and modified using Cabinet Detailed View form (see Configuring a cabinet on page 4-54 for details). When the cabinet type (cabinet_type) of a cabinet is PCU, the Cabinet Detailed View form displays only the following information: •
cabinet type.
•
rdnClass.
•
RdnInstance.
•
nmcRDNInstance.
•
Parent.
•
additionalInfo.
•
opState.
•
adminState.
•
reasonCode
•
timeOfLastTrans
•
OMC-RUser
Displaying and modifying a PCU cabinet Detailed View To display and modify details for a PCU cabinet using the Navigation Tree, see the general procedure in Modifying a network object using the OMC-R GUI on page 1-34. The Cabinet Detailed View fields are described in Configuring a cabinet on page 4-54. Some PCU cabinet fields cannot be modified and are set by the OMC-R, for example: •
Type: PCU RdnInstance
6-16
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displaying and modifying PCU cage details
Displaying and modifying PCU cage details ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to displaying and modifying PCU cage details When a PCU is created, the OMC-R automatically creates a PCU cage. Likewise when a PCU is deleted, the OMC-R automatically deletes the PCU cage. A cage is a child of a PCU (and can also be a child of a site). A PCU can only have one cage. No child objects for a PCU cage are displayed in the Navigation Tree (for example, DHP class). A PCU cage cannot be created by a user from the OMC-R Navigation Tree. However, the user can display and modify details of the PCU Cage using Cage Detailed View (see Configuring a cage on page 4-59 for details). When displayed for a PCU Cage, the Cage Detailed View form displays only the following information: •
rdnClass.
•
RdnInstance.
•
nmcRDNInstance.
•
Parent.
•
cabinet.
•
additionalInfo.
•
opState.
•
adminState.
•
reasonCode.
•
timeOfLastTrans.
•
OMC-RUser.
Displaying and modifying a PCU cage Detailed View To display and modify details for a PCU cage using the Navigation Tree, see the general procedure in Modifying a network object using the OMC-R GUI on page 1-34. The Cage Detailed View fields are described in Configuring a cage on page 4-59.
68P02901W17-S
6-17 Dec 2009
Configuring a DPROC using the OMC-R GUI
Chapter 6: Configuring a PCU for GPRS
Configuring a DPROC using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to DPROCs A DPROC is a child of a PCU. There are two types of DPROC: •
Packet Interface Control Processor (PICP). A maximum of six DPROCs with the type PICP can be created.
•
Packet Resource Processor (PRP). A maximum of ten DPROCs with the type PRP can be created.
The total number of PICP DPROCs and PRP DPROCs cannot exceed 12. {28351} When U-DPROC2 replaces legacy DPROC boards, the GPRS capacity is increased by combining PRP and PICP into PXP functionality. Refer to the section Add new PCU hardware to increase GPRS capacity on page 2-193 for further details. The links to a PCU are normally controlled by PICPs. If, in special circumstances, a direct link is made to a PRP, the relatedDev parameters of the GDS contain the information needed by the PICP for link control. See Technical Description: BSS Command Reference (68P02901W23) for the GDS parameters. A DPROC PICP must be created in either slot 1 or slot 2 of the PCU Cage.
Prerequisites to creating a DPROC Before creating a DPROC, a PCU must exist.
Creating a DPROC using the OMC-R GUI To add a DPROC to the network using the OMC-R GUI, use the following procedure:
Procedure 6-2 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-28 for further details. The DPROC class button changes color. Continued
6-18
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Procedure 6-2
DPROC Detailed View fields
Add a DPROC to the network using the OMC-R GUI (Continued)
2
Select Edit à Create from the menu bar. The OMC-R displays the DPROC Detailed View in Create mode.
3
Complete the fields, as required. See DPROC Detailed View fields for details.
4
Select File à Create from the menu bar.
5
Select File à Close from the menu bar.
DPROC Detailed View fields The following sections list and briefly describe the parameter fields in the DPROC Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
Identification grouping Table 6-9 describes the fields in the Identification grouping of the DPROC Detailed View.
Displays the name of the parent site (PCU). Click to display the parent PCU Detailed View.
PCI Vendor ID
Identifier unique to the PCI Device Vendor.
Optional.
PCI Device ID
Identifier unique to the PCI Device.
Optional.
PCI Device Revision
The revision number of the PCI device.
Optional.
Additional Information Use the Additional Information window to input any notes relating to this device. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
State grouping Standard network object state fields, see Table 4-2 for details.
Modifying DPROC details from the OMC-R GUI To display and modify details for DPROC details using the Navigation Tree, see the general procedure in Modifying a network object using the OMC-R GUI on page 1-34. The following fields cannot be modified:
6-20
•
DPROC Type.
•
RDN class.
•
RdnInstance.
•
PCI Vendor ID.
•
PCI Device ID.
•
PCI Device Revision.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Deleting a DPROC using the OMC-R GUI
Deleting a DPROC using the OMC-R GUI Deleting a DPROC When a DPROC is deleted, the delete instruction is sent to the BSS, where the DPROC information is deleted from the BSS database. The BSS then sends the delete instruction information to the OMC-R database, where the DPROC information is deleted from the OMC-R database.
Prerequisites to deleting a DPROC Only delete a DPROC when: •
The DPROC is locked.
•
The associated child MSIs have been deleted.
For a PRP DPROC only, a user can only delete it when the remaining total PRP timeslots resources available at the PCU is sufficient to support the GPRS timeslot resources for cells where the field: GPRS Enabled (BSS parameter name: gprs_enabled) is True.
Procedure to delete a DPROC To delete a DPROC using the Navigation Tree, see the general procedure in Deleting a network object using the OMC-R GUI on page 1-37.
68P02901W17-S
6-21 Dec 2009
Displaying and modifying PSP details
Chapter 6: Configuring a PCU for GPRS
Displaying and modifying PSP details ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to PSP A PCU System Processor (PSP) is a child of a PCU. Up to two PSP can exist per PCU. A PSP is used as the master processor at the PCU, and is necessary for GPRS functionality. Because the PSP is the main system processor and without it the PCU cannot function, a PSP cannot be deleted. When a PCU is created, PSP 0 and PSP 1 are automatically created (auto-equipped). When a PCU is deleted, the PSPs are also deleted automatically. A user cannot create or delete a PSP. All commands used by PSP 0 are also supported for PSP 1. A PSP must be in slot 7 or slot 9 of the PCU cage. PSP 0 is auto-equipped as the PSP device in slot 7. PSP 1 is auto-equipped in slot 9. A user cannot change these values. Device management of the MPROC boards is available through the PCU PSP device. A PSP cannot be locked.
Displaying and modifying PSP details from the OMC-R GUI To display and modify PSP details from the Navigation Tree, follow these steps:
Procedure 6-3
Display and modify PSP details from the Navigation Tree
1
Navigate to and select the PSP instance button in the Navigation Tree (BSS - BSS instance - PCU - PCU instance - Hardware Devices Processors - PSP - PSP instance). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The PSP instance button changes color.
2
See the general procedure in Modifying a network object using the OMC-R GUI on page 1-34. The OMC-R displays the PSP Detailed View in Monitor mode. See PSP Detailed View fields for details.
PSP Detailed View fields The following sections list and briefly describe the parameter fields in the PSP Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
6-22
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
PSP Detailed View fields
Identification grouping Table 6-10 describes the fields in the Identification grouping of the PSP Detailed View.
The PSP Identifier field. Also see description in Table 3-1.
0 or 1. Default is 0.
NMC RDN Value
See description in Table 4-1.
Parent Detailed View
Displays the parent PCU name. Click to display the parent PCU Detailed View.
PCI Vendor ID
See description in Table 6-9.
Optional.
PCI Device ID
See description in Table 6-9.
Optional.
PCI Device Revision
See description in Table 6-9.
Optional.
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
Field name
Brief description
PCU Slot
The slot in the PCU cage where the PSP is located.
Values 7 or 9. Default for PSP 0 is 7. Default for PSP 1 is 9.
Mandatory or Optional? Optional.
Additional Information Use the Additional Information window to input any notes relating to this PSP. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
State grouping Standard network object state fields, see Table 4-2 for details.
68P02901W17-S
6-23 Dec 2009
Configuring a PCU MSI using the OMC-R GUI
Chapter 6: Configuring a PCU for GPRS
Configuring a PCU MSI using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to configuring a PCU MSI using the OMC-R GUI An MSI is a child of a PCU (and a SITE). No more than 24 MSI objects can be created. A PCU MSI has the MSI type: MSI-E1_PMC (14). Two MMS object instances are contained under an MSI. For code download to the PCU, there must be a DPROC in either slot 1 or slot 2 of the PCU with the MSI on socket 1 of that DPROC.
Prerequisites to creating a PCU MSI Before creating a PCU MSI, the following must exist: •
PCU.
•
DPROC.
Creating a PCU MSI using the OMC-R GUI To add an MSI to a PCU using the OMC-R GUI, follow these steps:
Procedure 6-4
6-24
Add an MSI to a PCU using the OMC-R GUI
1
Navigate to and select the MSI class button in the Navigation Tree (BSS à BSS instance à PCU à PCU instance à Hardware Devices à MSI). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The MSI class button changes color.
2
Select Edit à Create from the menu bar. The OMC-R displays the MSI Detailed View in Create mode.
3
Complete the fields, as required. See PCU MSI Detailed View fields for details.
4
Select File à Create from the menu bar.
5
Select File à Close from the menu bar.
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
PCU MSI Detailed View fields
PCU MSI Detailed View fields The following sections list and briefly describe the parameter fields in the PCU MSI Detailed View according to their parameter grouping.
NOTE To obtain further information for a parameter, select Help - On Context from the menu and drag the ? prompt to the appropriate field and click that field. A context-sensitive help page is displayed.
Identification grouping Table 6-12 describes the fields in the Identification grouping of the PCU MSI Detailed View.
Displays the parent PCU name. Click to display the parent PCU Detailed View.
Default is MSI-E1_PMC (14). Only available if BSS gprsOpt is enabled (1).
Mandatory or Optional? Mandatory.
Cage and Slot Information grouping Table 6-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
Field name
Brief description
Data Processor
The unique id of the DPROC where the MSI resides. Only valid if msi_type is MSI-E1_PMC.
Data Processor Socket
The socket on the DPROC on which the MSI resides. Only valid if msi_type is MSI-E1_PMC.
68P02901W17-S
Values
Mandatory or Optional?
The default is null.
Optional.
Socket 1 or Socket 2. Default is Socket 1.
Optional.
6-25 Dec 2009
Modifying PCU MSI details from the OMC-R GUI
Chapter 6: Configuring a PCU for GPRS
Additional Information Use the Additional Information window to input any notes relating to this device. Where additional notes are not required, close this field by clicking the toggle button next to the Additional Information header.
State grouping Standard network object state fields, see Table 4-2 for details.
Modifying PCU MSI details from the OMC-R GUI To modify PCU MSI details from the Navigation Tree, see the general procedure in Modifying a network object using the OMC-R GUI on page 1-34. The following MSI fields cannot be changed:
•
Data Processor.
•
Data Processor Socket.
Deleting a PCU MSI using the OMC-R GUI Introduction to deleting an MSI When a PCU MSI is deleted, the OMC-R automatically deletes the MMS objects beneath it. MMS objects are connected to a GDS and a GBL. If a user attempts to delete a PCU MSI when a GDS or GBL object exists and the PCU MMS fields in the GDS or GBL Detailed View contain an MMS object identifier contained within the MSI, the delete operation is rejected by the BSS.
Prerequisites to deleting an MSI A PCU MSI can only be deleted if: •
The MSI has been locked.
•
The GDS and/or GBL related to the MMS of the MMI have been deleted.
Procedure to delete an MSI To delete a PCU MSI using the Navigation Tree, see the general procedure in Deleting a network object using the OMC-R GUI on page 1-37.
6-26
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Displaying and modifying PCU MMS details
Displaying and modifying PCU MMS details ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to displaying and modifying PCU MMS details When a PCU MSI is created, the OMC-R automatically creates a PCU MMS. Likewise when a PCU MSI is deleted, the OMC-R automatically deletes the PCU MMS. A PCU MMS is a child of an MSI under a PCU (and can also be a child of an MSI under a site). A user cannot create or delete a PCU MSI from the OMC-R Navigation Tree. However, the user can display and modify details of the PCU MSI using the MSI Detailed View form. When displayed for a PCU MMS, the MMS Detailed View form displays only the following information: •
rdnClass.
•
RdnInstance.
•
nmcRDNInstance.
•
Parent.
•
additionalInfo.
•
opState.
•
adminState.
•
adminState.
•
reasonCode.
•
timeOfLastTrans.
•
omcUser.
Prerequisites to viewing and modifying a PCU MMS Before a PCU MMS details can be viewed or modified: •
A PCU must exist.
•
An MSI must exist.
68P02901W17-S
6-27 Dec 2009
Displaying and modifying an MMS Detailed View
Chapter 6: Configuring a PCU for GPRS
Displaying and modifying an MMS Detailed View To display and modify details for a PCU MMS using the Navigation Tree, follow these steps:
Procedure 6-5
Display and modify details for a PCU MMS using the Navigation Tree
1
Navigate to and select the MMS instance button in the Navigation Tree (BSS - BSS instance - PCU - PCU instance - Hardware Devices MSI - MSI instance). If necessary, see Navigating to a network object class or instance on page 1-28 for further details. The MSI instance button changes color.
2
See the general procedure in Modifying a network object using the OMC-R GUI on page 1-34.
Monitoring timeslot usage on MMS link To monitor timeslot usage on an MMS link, see Displaying Channel and Circuit Status on page 9-20.
6-28
68P02901W17-S Dec 2009
Installation and Configuration: GSM System Configuration
Configuring a GDS using the OMC-R GUI
Configuring a GDS using the OMC-R GUI ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Introduction to configuring a GDS using the OMC-R GUI A GPRS Data Stream (GDS) is a child of a PCU. The GDS provides the link between the BSC and the PCU. It is used to load code into the PCU. There are three types of GDS: •
Transcoder Rate Adaption Unit (TRAU). TRAU carries the GPRS traffic and is the default type.
•
Link Access Protocol Data (LAPD) LAPD carries the GPRS signaling link (GSL).
•
{28351} LAPD_TRAU When there is Ethernet connectivity between the BSC and the PCU, the GDS type is LAPD_TRAU. LAPD_TRAU GDSs can carry both GSL and TRAU traffic. Up to 30 GSLs can be equipped on a GDS and each GSL requires one TDM 64 kbit/s timeslot for LAPD signaling. All the remaining TDM 64 kbit/s timeslots on the GDS are unused. {26740} The PSI provides the Ethernet link.
•
TRAU type GDS is equipped only in PRP
•
LAPD type GDS is equipped only in PICP
•
LAPD_TRAU type GDS is equipped only in PXP
NOTE A TRAU type GDS creation fails, if it is terminated on an MSI equipped on a PICP DPROC and an appropriate message is displayed. {26740} The GDS can be configured over the Ethernet as a child device of ETH. For this new GDS configuration, the BSC GDS is introduced in pair with the PXP GDS. The legacy GDS configuration (over E1) changes when the PCU E1 GDS is equipped. BSC side also has a BSC GDS. The BSC GDS is automatically equipped when the PCU GDS is equipped on the PXP. A GDS cannot be configured to an MMS on a PICP MSI when the PICP of the other MMS is supporting a GBL. The PCU can support a maximum of 36 TRAU GDSs and 2 LAPD GDSs. A GDS and a GBL cannot be equipped to the same MSI at the PCU.
68P02901W17-S
6-29 Dec 2009
Fault Management of a GDS
Chapter 6: Configuring a PCU for GPRS
Fault Management of a GDS If an attempt is made to lock, INS, or reset a GDS device, the following warning message is displayed: Warning: The GDS carries GPRS data traffic between the BSC and the PCU. Loss of a GDS device will reduce GPRS traffic capacity between the BSC and the PCU. A PXP or PRP DPROC with no GDSs in service will not be able to schedule any GPRS traffic. Do you wish to device:
