BSS Command Reference

Technical Description

GSR10
68P02901W23-T

2010 Motorola, Inc. All Rights Reserved.

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

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

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

Jan 2010
 Table
of
Contents

Contents

Technical Description: BSS Command Reference

Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 1: Introduction to commands

Version updates due to this software release. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
GSR10 new/modified parameters user reference form . . . . . . . . . . . . . . . . . . . . . . 1-6
BSS MMI functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
BSS task-oriented command usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Command/database parameter security levels . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Command/database parameter types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Commands to be used with caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Parameters to be used with caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Entering MMI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
MMI command availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
GSM cell ID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Indices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
SYSGEN mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40

Chapter 2: Equipping the CM database

Introduction to equipping the CM database . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Using the equip command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Equipage hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Information for equipping devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Information for equipping functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

Chapter 3: Device/function related commands

Command reference presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Device-related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Device identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Function related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Function identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
equip/unequip command matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Alarm devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
add_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
add_conn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
add_neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
add_nsvc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

68P02901W23-T i
Jan 2010
Contents

add_rtf_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
alarm_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
assess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
cage_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
cell_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
chg_acs_params . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
chg_a5_alg_pr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
chg_audit_sched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
chg_cell_element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
chg_cell_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-96
chg_cmd_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100
chg_csfp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
chg_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
chg_eas_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108
chg_element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-112
chg_hop_params . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-145
chg_ksw_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-154
chg_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-160
chg_rtf_freq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-162
chg_severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-167
chg_smscb_msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-170
chg_throttle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-176
chg_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-178
chg_ts_usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-181
chg_x25config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-186
clear_cal_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-189
clear_database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-191
clear_gclk_avgs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193
configure_csfp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-195
connection_code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-197
copy_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-199
copy_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-207
del_act_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-210
del_cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-212
del_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-215
del_neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-217
del_nsvc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-222
del_rtf_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-224
del_smscb_msg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-226
device_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-230
diagnose_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-238
disp_a5_alg_pr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-242
disp_acs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-244
disp_act_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-246
disp_bss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-249
disp_bssgp_f_bmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-251
disp_cal_data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-253
disp_cbch_state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-257
disp_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-261
disp_cell_map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-264
disp_cell_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-267
disp_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-282
disp_csfp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-284
disp_csfp_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-288
disp_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-291
disp_element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-294
disp_equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-315
disp_exp_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-341

ii 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Contents

disp_flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-343
disp_gclk_avgs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-345
disp_gclk_cal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-347
disp_gsm_cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-350
disp_hdlc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-353
disp_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-356
disp_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-361
disp_link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-362
disp_link_usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-364
disp_mms_ts_usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-366
disp_neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-379
disp_nsvc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-389
disp_options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-393
disp_processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-407
disp_relay_contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-414
disp_rtf_channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-416
disp_rtf_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-422
disp_severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-424
disp_site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-426
disp_throttle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-427
disp_time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-430
disp_trace_call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-432
disp_traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-436
disp_transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-439
disp_version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-441
disp_x25config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-443
equip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-445
fpanel_codeload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-462
freq_types_allowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-465
gclk_cal_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-469
ins_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-471
lock_device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-478
Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-489
Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-491
mod_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-492
mod_nsvc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-495
modify_neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-498
modify_value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-507
nacc_nc2_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-529
page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-530
query_audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-532
reassign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-537
reattempt_pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-542
reset_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-544
reset_site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-553
set_full_power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-557
set_relay_contact. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-561
shutdown_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-563
site_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-568
soft_reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-572
state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-576
status_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-592
store_cal_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-596
swap_devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-599
sysgen_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-603
time_stamp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-611
trace_call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-613
trace_connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-625

68P02901W23-T iii
Jan 2010
Contents

trace_stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-627
unconfigure_csfp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-631
unequip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-633
unlock_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-645
_bss_data,6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-652
_bss_data,10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-653

Chapter 4: UNIX commands

alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
man . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
unalias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Chapter 5: Statistics commands

Statistical operations and information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
chg_stat_prop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
disp_enable_stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
disp_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
disp_stat_prop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
disp_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
stat_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56

Chapter 6: CM database parameters

CM database parameters presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
_bss_data,2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
_site_data, 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
abis_auto_swap_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
abis_state_element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
aci_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
aci_error_gen_thresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
aci_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
adap_ho_alt_trigger_rxqual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
adap_ho_pbgt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
adap_ho_rxlev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
adap_ho_rxqual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
adap_trigger_hop_rxqual_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
adap_trigger_hop_rxqual_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
adap_trigger_pbgt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
adap_trigger_pbgt_nbr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
adap_trigger_rxlev_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
adap_trigger_rxlev_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
adap_trigger_rxqual_dl. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
agch_flow_control_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
aggressive_rach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
allow_8k_trau . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
alt_qual_proc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
amr_bss_half_rate_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
amr_bss_full_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35
amr_dl_la_mode_chg_min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36
amr_dl_thresh_adjust . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37
amr_fr_dl_la_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
amr_fr_ul_la_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39
amr_full_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40
amr_half_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42

iv 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Contents

amr_home_filter_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
amr_hr_dl_la_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
amr_hr_ul_la_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47
amr_ms_high_cmr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48
amr_ms_high_rxqual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-49
amr_ms_low_cmr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
amr_ms_low_rxqual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-51
amr_ms_monitor_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
arp_bg_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-53
arp_bg_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-55
arp_bg_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57
arp_i_be_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59
arp_i_be_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
arp_i_be_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63
arp_streaming_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65
arp_streaming_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-67
arp_streaming_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69
asym_edge_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-71
attach_detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-72
auto_rf_loss_trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74
ba_alloc_proc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76
band_preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-78
band_preference_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80
base_ip_address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83
ber_loss_daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85
ber_loss_hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86
blind_search_preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-87
bounce_protect_margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-88
bs_ag_blks_res . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89
bs_pa_mfrms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-91
bs_pag_blks_res . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-93
bs_pbcch_blks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-94
bs_pcc_chans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95
bs_prach_blks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96
bsc_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-97
bsic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-99
bsp_overload_protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-102
bss_egsm_alm_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-103
bss_msc_overload_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-104
bssgp_block_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-105
bssgp_cbl_bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106
bssgp_dwnld_retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-108
bssgp_pfc_bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-109
bssgp_racap_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-111
bssgp_reset_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-112
bssgp_unblock_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-113
bts_p_con_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-114
bts_p_con_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116
bts_power_control_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-118
bts_txpwr_max_inner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-120
bts_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-126
bvci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-128
cage_manage_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-130
call_trace_options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-131
called_pci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-133
calling_pci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-134
carrier_disable_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-135
carriers_ins_pwr_fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136

68P02901W23-T v
Jan 2010
Contents

cbc_fast_select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-138
cbc_intface_vers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-140
cbc_vbind_cntr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-141
cbch_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-142
cbs_outage_cntr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-143
ccch_conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-144
ccch_load_period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-147
cell_bar_access_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-149
cell_bar_access_switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-152
cell_bar_qualify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-154
cell_barred_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-156
cell_reselect_hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-157
cell_reselect_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-159
cell_reselect_param_ind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-161
channel_reconfiguration_switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-163
cic_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-165
cic_error_gen_thresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-166
cic_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-167
cic_validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-168
ciph_mode_rej_allowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-169
clk_src_fail_reset_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-170
coincident_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-171
coincident_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-173
coincident_mb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-174
confusion_msg_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-176
congest_at_source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-177
congest_at_target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-179
congest_ho_margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-180
congest_pd_expand_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-181
cp_option_reset_ckt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-182
cp_option_rr_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-183
cr_calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-184
cstats_bss_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-185
cstats_cell_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-186
ct_flow_control_hi_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-187
ct_flow_control_lo_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-188
ct_flow_control_msc_trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-189
ctu2d_asym_opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-190
ctu2d_cap_opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-191
CTU8Opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-192
c31_hyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-194
c32_qual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-196
dat_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-198
data_qual_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-200
ddtr_ctrl_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-202
decision_1_ncell_rxlev_av_h_calc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-203
decision_1_dl_rxlev_av_ih . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-204
decision_1_dl_rxqual_av_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-205
decision_1_dl_rxlev_av_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-206
decision_1_dl_rxqual_av_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-207
decision_1_n1/decision_1_p1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-208
decision_1_n2/decision_1_p2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-210
decision_1_n3/decision_1_p3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-212
decision_1_n4/decision_1_p4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-214
decision_1_n5/decision_1_p5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-216
decision_1_n6/decision_1_p6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-218
decision_1_n7/decision_1_p7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-220
decision_1_n8/decision_1_p8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-222

vi 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Contents

decision_1_p_bgt_rxlev_av_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-224
decision_1_tim_adv_av_alg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-225
decision_1_ul_rxlev_av_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-226
decision_1_ul_rxlev_av_ih . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-227
decision_1_ul_rxlev_av_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-228
decision_1_ul_rxqual_av_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-229
decision_1_ul_rxqual_av_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-230
decision_alg_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-231
direct_inner_zone_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-233
disuse_cnt_hreqave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-234
dl_audio_lev_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-236
dl_dtx_voice_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-238
dl_rxlev_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-239
dl_rxqual_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-241
dnlk_vad_dtx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-243
dpc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-244
dproc_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-246
dr_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-247
dr_chan_mode_modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-248
dr_ho_during_assign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-250
dr_preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-252
dr_standard_congest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-253
dri_density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-255
dsp_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-257
dsp_error_gen_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-258
dsp_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-259
dtx_required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-260
dual_band_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-262
dyn_step_adj . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-263
dyn_step_adj_fmpr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-264
dynet_tchs_reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-265
early_classmark_sending. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-267
eas_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-269
eas_alarm_type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-270
eas_report_opto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-272
eas_severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-273
edge_asym_mismatch_cita . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-275
efr_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-276
egprs_init_dl_cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-278
egprs_init_ul_cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-280
egsm_bcch_sd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-282
egsm_handover_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-284
emergency_class_switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-286
emergency_group_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-288
en_incom_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-290
enhanced_relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-292
eop_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-293
ercgprsOpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-295
erc_ta_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-296
erroneous_lapdm_discard_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-297
eth_rx_errors_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-298
eth_tx_errors_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-299
ext_range_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-300
ext_ul_dur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-302
ext_utbf_nodata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-303
extended_paging_active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-305
extuplinkOpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-307
fdd_multirat_reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-308

68P02901W23-T vii
Jan 2010
Contents

fdd_gprs_qoffset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-309
fdd_qmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-311
fdd_qoffset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-312
fdd_rep_quant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-313
fer_meas_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-314
fieldeng_always _enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-315
force_hr_usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-316
free_run_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-317
frequency_type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-318
full_pwr_rfloss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-320
gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-321
gb_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-323
GboIPOpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-324
gci_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-325
gci_error_gen_thresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-326
gci_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-327
gclk_24_alarm_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-328
gclk_24_high_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-329
gclk_24_low_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-330
gclk_qwarm_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-331
global_reset_repetitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-332
gmsk_capability_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-334
gproc_slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-336
gprs_alarm_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-338
gprs_asym_mismatch_delta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-339
gprs_bs_cv_max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-340
gprs_cell_reselect_hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-341
gprs_com_ms_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-343
gprs_cr_margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-344
gprs_dl_pwr_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-346
gprs_drx_timer_max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-348
gprs_edge_mismatch_sigma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-349
gprs_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-351
gprs_intraho_allwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-353
gprs_mac_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-355
gprs_min_prr_blks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-356
gprs_ms_pan_dec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-357
gprs_ms_pan_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-359
gprs_ms_pan_max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-361
gprs_ms_txpwr_max_cch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-363
gprs_network_operation_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-366
gprs_num_pmrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-368
gprs_par_wait_ind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-370
gprs_pb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-371
gprs_pc_alpha . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-372
gprs_pc_meas_chan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-373
gprs_reconfig_thresh_idle_tch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-374
gprs_reselect_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-376
gprs_rxlev_access_min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-378
gprs_sched_beta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-380
gprs_sig_bvci. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-382
gprs_temporary_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-383
gprs_type5_alg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-385
gprs_ts_config_alg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-387
gprs_ul_dl_bias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-389
group_block_unblock_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-390
gsl_lcf_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-392
gsm_bss_half_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-394

viii 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Contents

gsm_cell_id_format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-396
gsm_half_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-398
half_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-399
handover_power_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-400
handover_required_curr_ch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-403
handover_required_reject_switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-404
handover_required_sp_ver_used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-406
hcs_thr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-408
hdsl_losw_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-409
hdsl_losw_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-410
hdsl_snr_daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-411
hdsl_snr_daily_mon_period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-413
hdsl_snr_hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-414
hdsl_snr_hourly_mon_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-416
hdsl_snr_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-417
hdsl_snr_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-419
ho_exist_congest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-421
ho_margin_def . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-423
ho_margin_type5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-425
ho_margin_usage_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-426
ho_only_max_pwr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-428
ho_pwr_level_inner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-429
hop_count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-431
hop_qual_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-432
hopping_support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-434
hopping_systems_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-436
hopping_systems_hsn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-438
hopping_systems_mobile_alloc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-440
hr_fr_hop_count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-442
hr_intracell_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-443
hr_res_ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-445
illegal_circuit_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-446
Improve_ts_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-447
imrm_dcs1800_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-450
imrm_egsm_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-451
imrm_force_recalc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-453
imrm_pgsm_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-455
imrm_umts_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-457
IncellOpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-459
inc_prp_cap_ena . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-460
init_dl_cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-462
init_ul_cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-464
inner_amr_hr_usage_thres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-466
inner_hr_usage_thres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-468
inner_zone_alg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-469
intave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-472
inter_cell_handover_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-474
inter_rat_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-476
interband_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-478
interfer_bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-480
interfer_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-482
intra_cell_handover_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-483
ip_address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-485
isp_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-487
ksw_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-488
l_rxlev_dl_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-490
l_rxlev_dl_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-492
l_rxlev_ul_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-494

68P02901W23-T ix
Jan 2010
Contents

l_rxlev_ul_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-496
l_rxqual_dl_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-498
l_rxqual_dl_h_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-500
l_rxqual_dl_h_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-501
l_rxqual_dl_h_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-503
l_rxqual_dl_h_hopping_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-505
l_rxqual_dl_h_hopping_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-507
l_rxqual_dl_h_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-509
l_rxqual_dl_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-510
l_rxqual_dl_p_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-512
l_rxqual_dl_p_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-514
l_rxqual_dl_p_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-516
l_rxqual_dl_p_hopping_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-518
l_rxqual_dl_p_hopping_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-520
l_rxqual_dl_p_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-522
l_rxqual_ul_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-524
l_rxqual_ul_h_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-526
l_rxqual_ul_h_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-527
l_rxqual_ul_h_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-529
l_rxqual_ul_h_hopping_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-531
l_rxqual_ul_h_hopping_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-533
l_rxqual_ul_h_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-535
l_rxqual_ul_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-536
l_rxqual_ul_p_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-538
l_rxqual_ul_p_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-540
l_rxqual_ul_p_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-542
l_rxqual_ul_p_hopping_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-544
l_rxqual_ul_p_hopping_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-546
l_rxqual_ul_p_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-548
land_layer1_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-550
last_rsl_alarm_persistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-551
layer_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-552
lb_int_called_pci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-553
lb_int_calling_pci. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-554
lb_int_cr_calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-555
lb_int_dpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-556
lb_int_global_reset_repetitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-557
lcs_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-558
link_about_to_fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-561
link_fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-563
lmtl_loadshare_granularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-565
local_maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-566
low_sig_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-569
lta_alarm_range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-570
max_gprs_ts_per_carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-571
max_ms_dl_buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-573
max_ms_dl_rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-575
max_number_of_sdcchs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-576
max_pagenum_per_sec. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-578
max_q_length_channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-579
max_q_length_sdcch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-581
max_retran. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-582
max_rst_ckt_timer_exps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-584
max_sum_timeslot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-585
max_tx_bts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-586
max_tx_bts_standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-592
max_tx_ms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-593
mb_preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-595

x 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Contents

mb_tch_congest_thres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-596
MCBTSR8Opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-597
missing_rpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-599
mmi_cell_id_format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-600
mms_cat_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-601
mms_config_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-603
ms_distance_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-605
ms_flow_control_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-607
ms_max_range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-608
ms_p_con_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-610
ms_p_con_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-612
ms_power_control_allowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-614
ms_power_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-616
ms_txpwr_max_cch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-617
ms_txpwr_max_cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-620
ms_txpwr_max_def . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-622
ms_txpwr_max_inner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-624
msc_bss_overload_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-625
msc_preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-626
msc_qt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-628
msc_release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-630
mspwr_alg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-631
mtbr_downgrade_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-632
mtl_loadshare_granularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-633
multiband_reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-634
nacc_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-636
n_avg_i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-637
ncc_of_plmn_allowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-638
nccr_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-640
nccrOpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-641
neighbor_journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-642
network_control_order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-644
new_calls_amr_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-646
new_calls_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-648
ni . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-649
ns_alive_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-651
ns_block_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-652
ns_unblock_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-653
nsei . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-654
num_audit_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-655
num_emerg_access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-656
num_emerg_rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-657
num_emerg_tch_kill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-658
num_emerg_term_sdcch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-659
num_gbl_dl_thrput_samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-660
num_gbl_ul_thrput_samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-661
number_of_preferred_cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-662
number_sdcchs_preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-664
opc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-666
option_alg_a5_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-668
option_alg_a5_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-669
option_alg_a5_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-670
option_alg_a5_4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-671
option_alg_a5_5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-672
option_alg_a5_6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-673
option_alg_a5_7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-674
option_preempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-675
outer_zone_usage_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-677

68P02901W23-T xi
Jan 2010
Contents

override_intra_bss_pre_transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-678
pbgt_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-679
pccch_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-680
pccchOpt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-682
pch_queue_length_ctr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-683
pcr_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-684
pcr_n1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-685
pcr_n2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-686
pcu_redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-687
percent_traf_cs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-689
persistence_level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-690
pfm_sig_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-692
phase_lock_gclk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-693
phase_lock_retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-694
phase2_classmark_allowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-695
phase2_resource_ind_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-697
pic_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-698
pic_error_gen_thresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-699
pic_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-700
pool_gproc_preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-701
poor_initial_assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-702
pow_inc_step_size_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-703
pow_inc_step_size_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-705
pow_red_step_size_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-707
pow_red_step_size_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-709
power_save_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-710
prach_max_retran . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-712
prach_s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-713
prach_tx_int . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-715
primary_pcu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-717
prioritize_microcell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-719
priority_class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-720
protect_last_ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-721
prp_capacity_opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-723
prp_fanout_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-724
prpThptOpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-725
prr_aggr_factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-726
psi_trau_fill_frames_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-727
puak_compress_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-728
Pw_Save_SwitchOpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-729
pwr_handover_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-730
pwrc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-732
qosP2Opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-734
qos_mbr_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-735
qos_mtbr_be_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-736
qos_mtbr_be_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-737
qos_mtbr_bg_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-738
qos_mtbr_bg_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-739
qos_mtbr_i1_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-740
qos_mtbr_i1_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-741
qos_mtbr_i2_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-742
qos_mtbr_i2_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-743
qos_mtbr_i3_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-744
qos_mtbr_i3_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-745
qsearch_c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-746
qsearch_c_initial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-747
qsearch_i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-749
qsearch_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-751

xii 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Contents

queue_management_information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-753
ra_color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-754
ra_reselect_hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-756
rac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-758
rach_load_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-760
rach_load_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-762
rach_load_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-764
radio_link_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-765
rapid_pwr_down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-767
rci_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-768
rci_error_gen_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-769
rci_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-770
reconfig_fr_to_amr_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-771
reconfig_fr_to_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-773
red_loss_daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-774
red_loss_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-775
red_loss_hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-776
red_time_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-777
red_loss_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-778
reestablish_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-779
rel_tim_adv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-781
remote_ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-783
remote_loss_daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-785
remote_loss_hourly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-786
remote_loss_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-787
remote_loss_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-788
remote_time_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-789
red_time_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-790
report_resource_tch_f_high_water_mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-791
report_resource_tch_f_low_water_mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-793
res_gprs_pdchs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-795
res_ts_less_one_carrier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-797
rf_res_ind_period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-799
rpd_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-800
rpd_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-801
rpd_trigger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-802
rpt_bad_qual_no_mr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-804
rsl_lcf_congestion_thi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-806
rsl_lcf_congestion_tlow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-807
rtf_path_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-808
rxlev_access_min. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-809
rxlev_dl_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-811
rxlev_dl_pc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-813
rxlev_dl_zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-815
rxlev_min_def . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-817
rxlev_ul_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-819
rxlev_ul_pc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-821
remote_time_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-823
rxlev_ul_zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-824
rxqual_dl_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-826
rxqual_dl_pc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-828
rxqual_ul_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-830
rxqual_ul_pc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-832
sap_audit_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-834
sap_device_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-835
sap_end_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-836
sap_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-837
sap_start_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-838

68P02901W23-T xiii
Jan 2010
Contents

sccp_bssap_mgt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-839
scr_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-840
score_mcs_thres_a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-841
score_mcs_thres_b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-842
sdcch_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-843
sdcch_need_high_water_mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-845
sdcch_need_low_water_mark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-847
sdcch_tch_band_reassign_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-849
sdcch_timer_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-850
search_prio_3g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-852
second_asgnmnt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-853
secondary_freq_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-855
serving_band_reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-857
sgsn_release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-858
sig_lnk_tst_allow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-859
sig_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-860
slip_loss_daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-862
slip_loss_hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-863
slip_loss_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-864
slip_loss_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-865
smg_gb_vers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-866
sms_dl_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-867
sms_tch_chan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-868
sms_ul_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-870
ss7_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-871
ssm_critical_overload_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-873
ssm_normal_overload_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-875
ssp_burst_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-876
ssp_burst_limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-877
stat_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-878
stop_dri_tx_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-879
stp_pc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-880
stp_pc_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-881
stream_downgrade_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-882
streaming_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-883
subnet_mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-884
super_bts_indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-886
surround_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-887
sw_pdtch_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-889
sw_ts_less_one_carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-890
swfm_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-892
switch_gprs_pdchs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-893
sync_loss_daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-895
sync_loss_hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-896
sync_loss_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-897
sync_loss_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-898
sync_time_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-899
sync_time_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-900
t_avg_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-901
t_avg_w . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-902
t_terrestrial_fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-904
tch_busy_critical_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-905
tch_busy_norm_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-906
tch_congest_prevent_thres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-907
tch_flow_control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-908
tch_full_need_low_water_mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-910
tch_usage_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-911
tdd_qoffset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-912

xiv 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Contents

td_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-913
tdm_switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-914
tdm_ts_blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-915
temporary_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-916
terr_or_sate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-918
thp_be_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-920
thp_bg_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-921
thp_i2_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-922
thp_i3_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-923
thp_stream_weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-924
threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-925
timing_advance_period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-926
tlli_blk_coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-928
trace_msgs_after_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-929
trace_msgs_before_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-930
trunk_critical_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-931
trunk_major_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-932
ts_alloc_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-933
ts_in_usf_active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-935
tsc_update_method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-936
tx_integer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-938
tx_power_cap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-940
udp_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-942
u_rxlev_dl_ih . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-944
u_rxlev_dl_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-946
u_rxlev_ul_ih . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-948
u_rxlev_ul_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-950
u_rxqual_dl_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-952
u_rxqual_dl_p_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-954
u_rxqual_ul_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-956
u_rxqual_ul_p_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-958
ul_audio_lev_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-960
ul_rxlev_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-961
ul_rxqual_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-963
umts_band_preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-965
umts_cpich_ec_no_min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-966
umts_cpich_rscp_min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-967
unequipped_circuit_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-968
use_bcch_for_gprs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-970
use_derived_ho_power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-971
use_neighbor_pbgt_hreqave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-972
volume_control_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-973
wait_for_reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-975
wait_indication_parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-976
worse_neighbor_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-978
zone_ho_hyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-979
zone_pingpong_count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-981
zone_pingpong_preferred_zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-982

Chapter 7: Timer parameters

add_access_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
assign_successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
auto_dl_dur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
bcch_info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
bep_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
bep_period2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
bounce_protect_cong_tmr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

68P02901W23-T xv
Jan 2010
Contents

bounce_protect_qual_tmr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
bsc_audit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
bsc_audit_response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
bss_overload_control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
bssgp_fc_period_c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
bssgp_t1_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
bssgp_t2_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
bssgp_t4_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
bssgp_t5_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
bssgp_t6_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
bssgp_t8_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
bssmap_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
bssmap_t4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
bssmap_t7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
bssmap_t8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
bssmap_t10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
bssmap_t11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
bssmap_t13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
bssmap_t19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
bssmap_t20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
bssmap_tqho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
bts_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
bts_audit_response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
bts_escalation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
carrier_free_immediate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
cbch_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
cbch_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
cbch_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
channel_act . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
channel_teardown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
cipher_comp_ms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
ciphering_successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52
circuit_reset_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54
clear_cmd_ext_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-55
clear_command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56
dealloc_inact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57
delay_dl_rel_dur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58
delay_ul_rel_dur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59
downlink_sync_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60
dynet_retry_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62
early_classmark_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
emerg_reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
ext_ho_allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
ext_rtry_cand_prd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
flow_control_t1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
flow_control_t2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69
gbl_thrput_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70
gprs_penalty_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-71
gprs_smg30_t3192 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72
gprs_t3168 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
gprs_t3192 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74
handover_recognized_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75
ho_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77
ho_allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78
ho_complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79
ho_request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
ho_successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-81
hop_count_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82

xvi 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Contents

initial_sync_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-83
lb_int_bssmap_t4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-85
lb_int_bssmap_t13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-86
lb_int_clear_command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-87
lb_int_sccp_released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88
lb_int_sccp_tconn_est . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-89
lb_int_sccp_tiar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-90
lb_int_sccp_tias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-91
lb_int_sccp_trel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-92
lb_int_spi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-93
lb_int_ss7_l2_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-94
lb_int_ss7_l2_t2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-95
lb_int_ss7_l2_t3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-96
lb_int_ss7_l2_t4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-97
lb_int_ss7_l2_t5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-98
lb_int_ss7_l2_t6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-99
lb_int_ss7_l2_t7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-100
lb_int_ss7_l3_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-101
lb_int_ss7_l3_t2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-102
lb_int_ss7_l3_t4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-103
lb_int_ss7_l3_t5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-104
lb_int_ss7_l3_t12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-105
lb_int_ss7_l3_t13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-106
lb_int_ss7_l3_t14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-107
lb_int_ss7_l3_t17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-108
lb_int_ss7_l3_t22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-109
lb_int_ss7_l3_t23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-111
lb_int_ss7_slt_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-112
lb_int_t_stat_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-113
lcs_perf_location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-114
lcs_segmentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-115
lcs_supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-116
mode_modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-117
mode_rr_modify_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-118
ms_sapi3_est . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-120
nc_non_drx_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-122
nc_reporting_period_i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-124
nc_reporting_period_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-125
neighbor_report_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-127
ns_alive_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-128
ns_block_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-129
ns_reset_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-130
ns_reset_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-132
ns_test_timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-133
pccch_drx_timer_max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-135
penalty_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-137
phase_lock_duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-139
psi1_repeat_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-140
radio_chan_released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-142
red_psp_audit_tmr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-143
register_exp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-144
rf_chan_rel_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-145
rr_ny1_rep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-146
rr_t3103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-148
rr_t3101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-150
rr_t3105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-151
rr_t3109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-153
rr_t3111_sd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-155

68P02901W23-T xvii
Jan 2010
Contents

rr_t3111_tch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-157
rr_t3212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-159
rsl_congestion_alarm_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-161
rtry_cand_prd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-162
sacch_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-164
sccp_released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-166
sccp_tconn_est . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-167
sccp_tiar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-168
sccp_tias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-170
sccp_trel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-171
sm_audit_response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-172
spi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-173
ss7_l2_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-175
ss7_hsp_l2_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-177
ss7_l2_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-179
ss7_l2_t2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-181
ss7_l2_t3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-183
ss7_l2_t4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-185
ss7_l2_t5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-186
ss7_l2_t6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-187
ss7_l2_t7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-189
ss7_l3_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-190
ss7_l3_t2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-191
ss7_l3_t4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-192
ss7_l3_t5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-193
ss7_l3_t12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-194
ss7_l3_t13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-195
ss7_l3_t14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-196
ss7_l3_t17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-197
ss7_l3_t22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-198
ss7_l3_t23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-200
ss7_slt_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-202
start_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-203
static_sync_timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-204
stop_dri_tx_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-206
t_stat_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-207
uplink_sync_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-208
valid_candidate_period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-210
zone_pingpong_disable_win . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-211
zone_pingpong_enable_win . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-212

Chapter 8: Device/Function parameters

Device and function database parameters presentation . . . . . . . . . . . . . . . . . . . . . 8-2
antenna_select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
bbu_attached. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
bbu_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
ber_oos_mon_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
ber_restore_mon_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
bsc_cbc_operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
cabinet_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Cavity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
cbc_operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
cell_zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
chan_alloc_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
cic_block_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
clkx0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
clkx1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28

xviii 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Contents

clkx2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
combiner_address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32
combiner_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33
combining_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34
cpu_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36
dri_density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37
ext_pdchs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39
ext_timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41
first_device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43
first_dev_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44
fm_cell_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-45
frequency_type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-47
hdsl_modem_setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-49
hdsl_oos_mon_period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-51
hdsl_restore_mon_period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-53
ias_connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-55
first_ingress_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-56
second_ingress_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-57
int_antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58
int_hdsl_modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59
inter_bbu_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-60
lapd_k . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-61
lapd_n200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-63
lapd_t200_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-65
lowest_arfcn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-67
max_cbls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68
max_dris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-69
max_gsls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-71
max_mtls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-72
mms_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-74
msc_mms_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-75
msi_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-76
n391 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78
n392 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-79
n393 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-80
nbit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-81
ne_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-82
opto_reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-83
pkt_radio_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-85
pref_rtf_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88
rsl_rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-89
rtf_ds0_count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-90
sd_load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-92
sd_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-94
second_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-95
second_device_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-96
shared_timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-97
slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98
slot_num . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-99
start_ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-100
t391 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-101
t392 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-102
tcu_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-103
tdOpt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-105
transceiver_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-106
transcoding_capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-107
tru_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108
trx_pwr_red . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-109

68P02901W23-T xix
Jan 2010
Contents

tx_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-114
tx0_dri_density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-115
tx1_dri_density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-116

xx 68P02901W23-T
Jan 2010
 List
of
Figures

List of Figures

Figure 2-1: Remote Transcoder (RXCDR) devices and functions . . . . . . . . . . . . . . . . . 2-7

Figure 2-2: BSC and InCell BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Figure 2-3: M-Cell and Horizon macro equipage hierarchy chart . . . . . . . . . . . . . . . . 2-9
Figure 2-4: Horizon II macro equipage hierarchy chart . . . . . . . . . . . . . . . . . . . . . 2-10
Figure 2-5: GPRS PCU devices and functions . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

68P02901W23-T xxi
Jan 2010
List of Figures

xxii 68P02901W23-T
Jan 2010
 List
of
Tables

List of Tables

Table 1-1: Commands status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Table 1-2: Database parameters status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Table 1-3: Task-oriented MMI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Table 1-4: MMI command availability by location . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Table 1-5: MMI command availability by SYSGEN mode . . . . . . . . . . . . . . . . . . . . . 1-29
Table 1-6: Device Indices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
Table 1-7: Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
Table 3-1: Device literals and descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Table 3-2: Device and command relationship . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Table 3-3: Device ID requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Table 3-4: Function related commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Table 3-5: Function ID requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Table 3-6: Valid slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Table 3-7: Equip/Unequip command matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Table 3-8: Alarm devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Table 3-9: add_cell command prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Table 3-10: add_conn valid ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Table 3-11: Neighbor frequency and number with an EGSM or PGSM source cell . . . . . . . . 3-35
Table 3-12: Neighbor frequency and number with DCS1800 source cell . . . . . . . . . . . . . 3-36
Table 3-13: Prompted Parameters for TD-SCDMA Neighbors . . . . . . . . . . . . . . . . . . 3-39
Table 3-14: add_neighbor command prompts for GSM BA BCCH and SACCH neighbors. . . . 3-43
Table 3-15: add_neighbor command prompts for UTRAN BCCH and SACCH neighbors . . . . 3-45
Table 3-16: add_neighbor command prompts for Blind Search neighbors. . . . . . . . . . . . 3-46
Table 3-17: Codec Mode Values / Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Table 3-18: Full Rate attribute values for chg_acs_params command. . . . . . . . . . . . . . 3-67
Table 3-19: Half Rate attribute values for chg_acs_params command . . . . . . . . . . . . . 3-68
Table 3-20: Full Rate prompts for the chg_acs_params command . . . . . . . . . . . . . . . 3-69
Table 3-21: Half Rate prompts for chg_acs_params command . . . . . . . . . . . . . . . . . 3-70
Table 3-22: Device scheduling defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Table 3-23: RXCDR default DTE addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Table 3-24: BSC default DTE addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Table 3-25: EAS default alarm strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110
Table 3-26: Baseband and Synthesizer frequency hopping restrictions . . . . . . . . . . . . . 3-147
Table 3-27: chg_hop_params prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-151
Table 3-28: Cell frequencies/mobile allocation . . . . . . . . . . . . . . . . . . . . . . . . . . 3-152
Table 3-29: Restrictions on related commands . . . . . . . . . . . . . . . . . . . . . . . . . . 3-153
Table 3-30: SMS special characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-174
Table 3-31: copy_path command prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-208
Table 3-32: mod_conn valid ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-493
Table 3-33: Operational states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-590
Table 3-34: Administrative states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-590
Table 3-35: Device states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-590
Table 3-36: Reason codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-591
Table 3-37: trace_call prompts and values for a GSM Trace and GPRS Trace. . . . . . . . . . 3-621
Table 5-1: Counter and gauge statistic type prompts . . . . . . . . . . . . . . . . . . . . . . 5-12

68P02901W23-T xxiii
Jan 2010
List of Tables

Table 5-2: Normal and weighted distribution statistic type prompts . . . . . . . . . . . . . . . 5-12
Table 6-1: alt_qual_proc=0 parameter values. . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
Table 6-2: alt_qual_proc=1 parameter values. . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
Table 6-3: Base Station Identity Code - Hexadecimal Values . . . . . . . . . . . . . . . . . . . 6-101
Table 6-4: Base Station Identity Code - Decimal Values . . . . . . . . . . . . . . . . . . . . . 6-101
Table 6-5: CTU2 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-121
Table 6-6: (R)CTU4 output values without any stage of combining. . . . . . . . . . . . . . . . 6-122
Table 6-7: Cabinet antenna connector maximum output power (Watts) . . . . . . . . . . . . . 6-123
Table 6-8: Values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro sites . . . . . . . . . 6-123
Table 6-9: Values for DCS1800 and M-Cellaccess, sites . . . . . . . . . . . . . . . . . . . . . 6-124
Table 6-10: Sample output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-124
Table 6-11: Values for barring classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-150
Table 6-12: Maximum mobile power level for PGSM, EGSM and GSM850 cells . . . . . . . . . 6-364
Table 6-13: Maximum mobile power level for DCS1800 cells . . . . . . . . . . . . . . . . . . 6-364
Table 6-14: Maximum mobile power level for PCS1900 cells. . . . . . . . . . . . . . . . . . . 6-365
Table 6-15: Modes for gprs_network_operation_mode . . . . . . . . . . . . . . . . . . . . 6-366
Table 6-16: Max MS power level for PGSM and EGSM. . . . . . . . . . . . . . . . . . . . . . 6-401
Table 6-17: Max MS power level for DCS1800 and PCS1900 cells . . . . . . . . . . . . . . . . 6-401
Table 6-18: Max MS power level for class 3 mobiles . . . . . . . . . . . . . . . . . . . . . . . 6-401
Table 6-19: Max MS power level for PGSM and EGSM cells . . . . . . . . . . . . . . . . . . . 6-430
Table 6-20: Max MS power level for DCS1800 and PCS1900 cells . . . . . . . . . . . . . . . . 6-430
Table 6-21: Max MS level for class 3 mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . 6-430
Table 6-22: Prompted parameters for Dual Band Cell use . . . . . . . . . . . . . . . . . . . . 6-471
Table 6-23: CTU2 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-588
Table 6-24: (R)CTU4 output values without any stage of combining . . . . . . . . . . . . . . . 6-589
Table 6-25: Cabinet antenna connector maximum output power (Watts) . . . . . . . . . . . . . 6-590
Table 6-26: Values for PGSM, EGSM, DCS1800 and PCS1900 sites . . . . . . . . . . . . . . . 6-591
Table 6-27: ms_max_range values for normal cells . . . . . . . . . . . . . . . . . . . . . . . 6-609
Table 6-28: ms_max_range values for Extended Range cells . . . . . . . . . . . . . . . . . . 6-609
Table 6-29: Maximum mobile power level for PGSM and EGSM cells . . . . . . . . . . . . . . 6-618
Table 6-30: Maximum mobile power level for DCS1800 cells . . . . . . . . . . . . . . . . . . 6-618
Table 6-31: Maximum mobile power level for PCS1900 cells. . . . . . . . . . . . . . . . . . . 6-619
Table 6-32: Bit mapping of ncc_of_plmn_allowed. . . . . . . . . . . . . . . . . . . . . . . . 6-639
Table 6-33: Configurations for network_control_order . . . . . . . . . . . . . . . . . . . . . 6-644
Table 6-34: Values for prach_tx_int representing number of frame slots . . . . . . . . . . . . 6-716
Table 6-35: qsearch_p attribute values below threshold. . . . . . . . . . . . . . . . . . . . . 6-752
Table 6-36: qsearch_p attribute values above threshold. . . . . . . . . . . . . . . . . . . . . 6-752
Table 6-37: Example cell configurations for rach_load_threshold . . . . . . . . . . . . . . . 6-762
Table 7-1: Impermissible combinations of psi1_repeat_period and bs_pbcch_blks . . . . . . 7-141
Table 8-1: Cabinets/ Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Table 8-2: Permitted CAB modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Table 8-3: Values for PGSM, EGSM and PCS 1900 sites . . . . . . . . . . . . . . . . . . . . . 8-110
Table 8-4: Values for DCS 1800 sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-111
Table 8-5: Values for PGSM and EGSM M-Cellmicro sites . . . . . . . . . . . . . . . . . . . . 8-112
Table 8-6: Values for DCS 1800 for M-Cell6, Horizonmacro, Horizonmacro2, Horizon II micro
and Horizon II mini sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-112
Table 8-7: Values for DCS 1800 and PCS 1900 M-Cellmicro sites . . . . . . . . . . . . . . . . 8-113

xxiv 68P02901W23-T
Jan 2010
 About
This
Manual

Technical Description: BSS Command

Reference

What is covered in this manual?

This manual is a reference document containing descriptions of the Man-Machine Interface

(MMI) commands and parameters used within the Motorola GSM system.

This document supports the following Motorola BSS equipment: BTS4, BTS5, BTS6,
BSSC, BSSC2, ExCell 4, ExCell 6, TopCell, M-Cell TM2, M-Cell6, M-Cellmicro, M-Cellcity,
Horizonmicro, Horizoncompact, M-Cellaccess, Horizonmacro, Horizon II macro, Horizonmicro2,
Horizoncompact2, Horizon II mini and Packet Control Unit (PCU).

Lists of the additions, changes, and deletions to commands and parameters introduced by the
particular software release version in this issue of the BSS Command Reference manual, is
provided in Version updates due to this software release on page 1-2.

A customer reference form for recording local settings of new/modified GSR10 parameters is
provided in GSR10 new/modified parameters user reference form on page 1-6.

68P02901W23-T 1
Jan 2010
Revision history

Revision history

The following sections show the revision status of this document.

Version information

The following table describes the changes made to this document:

Version Date of issue Description

S Apr 2008 GSM Software Release 9
S Jun 2009 GSM Software Release FP 1
T Jan 2010 GSM Software Release 10

Release information

This section describes the changes in this document between release GSR9 and GSR10. The
following features have been incorporated:
Gb over IP

Enhanced Horizon II Site Controller

Reduced number of LCFs

CTU4

PA bias in mixed radio Horizon II sites

Changing scratchpad parameters into CM parameters

E-EDGE (Dual Downlink Carrier)

CTU4 and RCTU4 8 carrier support

Abis Auto Swap

2 68P02901W23-T
Jan 2010
 Resolution of Service Requests

Resolution of Service Requests

The following Service Requests are resolved in this document:

Service
CMBP Number Description
Request

68P02901W23-T 3
Jan 2010
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.

4 68P02901W23-T
Jan 2010
 Text conventions

Text conventions

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

Input

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

Items of interest within a command appear like this sentence.

Output

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

variables that appear on the screen are shown like this sentence.
Items of interest within a screen display appear like this sentence.

Special key sequences

Special key sequences are represented as follows:

CTRL-c or CTRL+C Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or Press the Ctrl, Shift, and C keys at the same time.
CTRL+SHIFT+C
ALT-f or ALT+F Press the Alt and F keys at the same time.
ALT+SHIFT+F11 Press the Alt, Shift and F11 keys at the same time.
Press the pipe symbol key.
RETURN or ENTER Press the Return or Enter key.

68P02901W23-T 5
Jan 2010
Contacting Motorola

Contacting Motorola

Motorola appreciates feedback from the users of our documents.

24hour support

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

Questions and comments

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

Errors

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

The document title, part number, and revision character

The page number with the error

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

6 68P02901W23-T
Jan 2010
 Chapter

Introduction to commands

This chapter provides an introduction to the Base Station System (BSS), Man Machine Interface
(MMI) functions, commands, and parameters including SYSGEN modes of operation.

The following topics are contained in this chapter:

Version updates due to this software release on page 1-2: lists the commands and
parameters that are created, changed, and deleted by this software release.

GSR10 new/modified parameters user reference form on page 1-6: provides a

customer reference form for recording local settings of GSR10 parameters.

BSS MMI functions on page 1-12: provides an overview of BSS MMI functions for
managing the network.

BSS task-oriented command usage on page 1-15: lists the MMI commands for
performing BSS function related tasks.

Command/database parameter security levels on page 1-19: describes the

command/database access security levels.

Command/database parameter types on page 1-20: describes the command/database

parameter classification.

Commands to be used with caution on page 1-21: lists commands that cause a device
to cycle and must be used with caution.

Parameters to be used with caution on page 1-22: lists parameters that cause a device
to cycle and must be used with caution.

Entering MMI commands on page 1-23: provides guidelines on entering MMI

commands and use of the correct syntax.

MMI command availability on page 1-25: lists MMI command availability by location
and by SYSGEN mode.

GSM cell ID format on page 1-34: describes the two types of GSM cell ID format.

Indices on page 1-37: describes the indices for devices, including data array location,
bin numbers, alarm thresholds, and EAS alarm table.

SYSGEN mode on page 1-40: describes the SYSGEN modes of working.

68P02901W23-T 1-1
Jan 2010
Version updates due to this software release Chapter 1: Introduction to commands

Version updates due to this software release

MMI commands and parameters that are new, modified, deleted, or renamed as a result of the
introduction of software release GSR10, are listed separately.

For information about the features included in this software release, refer to Motorola manual
System Information: GSM Overview (68P02901W01).

New, modified and deleted commands

Table 1-1 Commands status

Feature Command Status

{34371G} chg_audit_sched on page 3-76 Modified
chg_hop_params on page 3-145 Modified
chg_rtf_freq on page 3-162 Modified
device_audit on page 3-230 Modified
disp_csfp_status on page 3-288 Modified
disp_equipment on page 3-315 Modified
disp_options on page 3-393 Modified
disp_processor on page 3-407 Modified
equip on page 3-445 Modified
ins_device on page 3-471 Modified
lock_device on page 3-478 Modified
modify_value on page 3-507 Modified
query_audits on page 3-532 Modified
reset_device on page 3-544 Modified
state on page 3-576 Modified
unequip on page 3-633 Modified
unlock_device on page 3-645 Modified
chg_stat_prop on page 5-5 Modified
disp_enable_stat on page 5-14 Modified
disp_stats on page 5-39 Modified
disp_stat_prop on page 5-26 Modified
stat_mode on page 5-56 Modified
{26638} add_nsvc on page 3-47 Modified

Continued

1-2 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference New, modified and deleted commands

Table 1-1 Commands status (Continued)

Feature Command Status
{26638} chg_element on page 3-112 Modified
del_nsvc on page 3-222 Modified
disp_element on page 3-294 Modified
disp_equipment on page 3-315 Modified
disp_nsvc on page 3-389 Modified
disp_options on page 3-393 Modified
equip on page 3-445 Modified
mod_nsvc on page 3-495 Modified
modify_value on page 3-507 Modified
unequip on page 3-633 Modified
{34282} chg_severity on page 3-167 Modified
modify_value on page 3-507 Modified
{34416} chg_element on page 3-112 Modified
{34452} agch_flow_control_mode on page 6-25 Modified
chg_element on page 3-112 Modified
disp_element on page 3-294 Modified
disp_options on page 3-393 Modified
{33254} fpanel_codeload on page 3-462 New
{35200G} disp_equipment on page 3-315 Modified
disp_options on page 3-393 Modified
modify_value on page 3-507 Modified
{36039G} chg_element on page 3-112 Modified
disp_element on page 3-294 Modified
disp_equipment on page 3-315 Modified
disp_options on page 3-393 Modified
equip on page 3-445 Modified
modify_value on page 3-507 Modified
swap_devices on page 3-599 Modified

68P02901W23-T 1-3
Jan 2010
New, modified and deleted database parameters Chapter 1: Introduction to commands

New, modified and deleted database parameters

Table 1-2 Database parameters status

Feature Parameter Status

{34371G} bbu_attached on page 8-8 New
bbu_id on page 8-9 New
first_device on page 8-43 New
first_ingress_port on page 8-56 New
second_ingress_port on page 8-57 New
inter_bbu_port on page 8-60 New
lowest_arfcn on page 8-67 New
MCBTSR8Opt on page 6-597 New
second_device on page 8-95 New
slot_num on page 8-99 New
tx_port on page 8-114 New
tx0_dri_density on page 8-115 New
tx1_dri_density on page 8-116 New
{26638} dat_weight on page 6-198 New
dproc_id on page 6-246 New
gateway on page 6-321 New
gb_mode on page 6-323 New
GboIPOpt on page 6-324 New
ip_address on page 6-485 New
remote_ip on page 6-783 New
sig_weight on page 6-860 New
subnet_mask on page 6-884 New
udp_port on page 6-942 New
{34282} cpu_threshold on page 8-36 New
ssm_critical_overload_threshold on page 6-873 Modified
ssm_normal_overload_threshold on page 6-875 Modified
{34416} power_save_enable on page 6-710 Modified
{34452} aggressive_rach on page 6-27 New
amr_home_filter_enabled on page 6-44 New
cage_manage_enabled on page 6-130 New
congest_pd_expand_enabled on page 6-181 New
{34452} cstats_bss_enabled on page 6-185 New

Continued

1-4 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference New, modified and deleted database parameters

Table 1-2 Database parameters status (Continued)

Feature Parameter Status
cstats_cell_enabled on page 6-186 New
edge_asym_mismatch_cita on page 6-275 New
gmsk_capability_mode on page 6-334 New
gprs_asym_mismatch_delta on page 6-339 New
gprs_edge_mismatch_sigma on page 6-349 New
inner_amr_hr_usage_thres on page 6-466 New
isp_enabled on page 6-487 New
ms_flow_control_enabled on page 6-607 New
new_calls_amr_hr on page 6-646 New
pch_queue_length_ctr on page 6-683 New
puak_compress_mode on page 6-728 New
reconfig_fr_to_amr_hr on page 6-771 New
{35200G} CTU8Opt on page 6-192 New
MCBTSR8Opt on page 6-597 Modified
tx0_dri_density on page 8-115 Modified
tx1_dri_density on page 8-116 Modified
{36039G} abis_auto_swap_enabled on page 6-7 New
max_tx_bts_standby on page 6-592 New
super_bts_indicator on page 6-886 New
t_terrestrial_fail on page 6-904 New
terr_or_sate on page 6-918 New

68P02901W23-T 1-5
Jan 2010
GSR10 new/modified parameters user reference form Chapter 1: Introduction to commands

GSR10 new/modified parameters user reference form

This section provides a customer form for recording current values set locally for the GSR10
new/modified parameters. The form also lists the relevant GSR10 feature, valid range, and
default values for each new or modified parameter.

Required editing software

Adobe Reader 7.0 or later is required to enter data on this form electronically.

Adobe Reader can be installed from the CD-ROM for this manual or downloaded free from
http://www.adobe.com.

Using the form

To use this form, enter customer values for the GSR10 new/modified parameters in the Local
Setting column either by:
Printing the form and entering the local value of the parameter manually,

or,

Clicking in the appropriate cell in the Local Setting column and typing the local value for
the parameter. Then printing the completed form for further use (see NOTE).

Storing an image of the completed form

To retain an image of the completed form, take a screen grab (Alt + Print Screen) of the full
page. Then paste it into a suitable file, such as a Word document, and store in the appropriate
manner.

1-6 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference GSR10 new/modified parameters reference form

GSR10 new/modified parameters reference form

Parameter Status Feature Valid range Default value Local value

bbu_attached New CTU4 feature 0 - 1 None
{34371G}
bbu_id New CTU4 feature 0 - 1 None
{34371G}
first_device New CTU4 feature 0 - l (BBU) None
{34371G} 0 - 5 (CTU4)
first_ingress_port New CTU4 feature 0 - 1 None
{34371G}
second_ingress_port New CTU4 feature 0 - 1 None
{34371G}
inter_bbu_port New CTU4 feature 0 - 2 None
{34371G}
lowest_arfcn New CTU4 feature 1 - 124 (PGSM) None
{34371G} 0, 1 - 124, 975 -
1023 (EGSM)
512 - 885
(DCS1800)
MCBTSR8Opt New CTU4 feature 0 or 1 N/A
{34371G}
second_device New CTU4 feature 0 - 1 (BBU) None
{34371G}
slot_num New CTU4 feature 0 - 5 (Horizon II None
{34371G} Macro)
0 - 1 (Horizon II
Mini)
tx_port New CTU4 feature 0 - 1 None
{34371G}
tx0_dri_density New CTU4 feature 0 - 2 (3) None
{34371G}
tx1_dri_density New CTU4 feature 0 - 2 (3) None
{34371G}
dat_weight New Gb over IP feature 0 - 255 N/A
{26638}
dproc_id New Gb over IP feature 1 - 6 N/A
{26638} 11 - 16

Continued

68P02901W23-T 1-7
Jan 2010
GSR10 new/modified parameters reference form Chapter 1: Introduction to commands

Parameter Status Feature Valid range Default value Local value

gateway New Gb over IP feature 0.0.0.0 - N/A
{26638} 223.255.255.255
128.0.0.0 -
223.255.255.255
Minimum
0 -
126.255.255.255
maximum
gb_mode New Gb over IP feature 0 or 1 0
{26638}
GboIPOpt New Gb over IP feature 0 or 1 N/A
{26638}
ip_address New Gb over IP feature 128.0.0.0 - N/A
{26638} 223.255.255.255
0 -
126.255.255.255
remote_ip New Gb over IP feature 0.0.0.0 - N/A
{26638} 223.255.255.255
Exception is
127.x.x.x
sig_weight New Gb over IP feature 0 - 255 N/A
{26638}
subnet_mask New Gb over IP feature 128.0.0.0 - N/A
{26638} 225.255.255.255
udp_port New Gb over IP feature 0 - 65535 N/A
{26638}
cpu_threshold New Increase RSL-LCF 0 to 100 100
capacity on
GPROC3/GPROC3-2
{34282}
power_save_enable Modified Using PA bias 0 to 2 0
feature in mixed
radio Horizon II
sites {34416}
agch_flow_control New Changing 0 to 2 1
_mode parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}

Continued

1-8 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference GSR10 new/modified parameters reference form

Parameter Status Feature Valid range Default value Local value

amr_home_filter New Changing 0 to 1 0
_enabled parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
cage_manage New Changing 0 to 1 1
_enabled parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
congest_pd_expand New Changing 0 to 1 0
_enabled parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
cstats_bss_enabled New Changing 0 to 1 0
parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
cstats_cell_enabled New Changing 0 to 1 0
parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
edge_asym New Changing 0 to 100 30
_mismatch_cita parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
gmsk_capability_mode New Changing 0 to 2 0
parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}

Continued

68P02901W23-T 1-9
Jan 2010
GSR10 new/modified parameters reference form Chapter 1: Introduction to commands

Parameter Status Feature Valid range Default value Local value

gprs_asym_ New Changing 0 to 100 10
mismatch_delta parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
gprs_edge_ New Changing 0 to 100 60
mismatch_sigma parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
inner_amr_hr New Changing 0 to 101 101
_usage_thres parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
isp_enabled New Changing 0 to 1 0
parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
ms_flow_control New Changing 0 to 1 1
_enabled parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
new_calls_amr_hr New Changing 0 to 101 101
parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
pch_queue_length New Changing 1 to 2 2
_ctr parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}

Continued

1-10 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference GSR10 new/modified parameters reference form

Parameter Status Feature Valid range Default value Local value

puak_compress_mode New Changing 0 to 2 0
parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
reconfig_fr_to_amr New Changing 0 to 101 101
_hr parameters
implemented
by scratchpad
parameters into
real CM parameters
{34452}
CTU8Opt New CTU4 and RCTU4 0 or 1 N/A
8 carrier support
{35200G}
abis_auto_swap_enabledNew Abis auto swap 0 or 1 0
{36039G}
max_tx_bts_standby New Abis auto swap -1 to 21 0
{36039G}
super_bts_indicator New Abis auto swap 0 or 1 0
{36039G}
t_terrestrial_fail New Abis auto swap 6 to 30 6
{36039G}
terr_or_sate New Abis auto swap 0 or 1 0
{36039G}

68P02901W23-T 1-11
Jan 2010
BSS MMI functions Chapter 1: Introduction to commands

BSS MMI functions

In the GSM system, Man-Machine Interface (MMI) commands are part of the Network
Management function. The Network Management function can be subdivided into
task-orientated categories.

On a Base Station System (BSS), MMI commands are responsible for these activities:
BSS Initialization Process (IP).

Security management, such as controlling system access.

Maintenance or Fault Management (FM).

System change control or Configuration Management (CM).

Call Processing maintenance.

Central statistics processing.

Miscellaneous.

BSS Initialization Process

The Initialization Process (IP) load codes from three sources:

GPROC.

Operation and Maintenance Center (OMC-R).

LAN connection to a personal computer (PC).

Upon initialization, code is loaded on the BSS. Initialization occurs when the BSS is reset, the
existing code is damaged, or a new version of code exists.

Early MMI interaction

The MMI prompt is presented before the initialization process is complete. Early interaction is
only permitted with CM process commands.

Security management

Passwords are required to access the system. These passwords ensure that only authorized
persons have access and establish a system/command permission level commensurate with
the person.

If an incorrect password is entered, access to a security level is denied.

1-12 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Fault Management

Fault Management

Fault Management commands are used to display and modify the administrative state of devices
or functions. Alarms are one example of this type of control.

Configuration Management

Configuration Management commands are used to:

Configure the Base Station System.

Populate the database during SYSGEN.

Modify the CM database.

Display information from the CM database.

Call processing

Call processing commands are used to trace the progress of a specified call, through random
trace, either by call rate, or SCCP connection number. The total data resulting from the call
progress events can be collected for later analysis.

Central statistics processing

Statistics commands are used to:

Enable/Disable statistics.

Display/Modify statistics for devices or cells.

Modify statistics time interval for system.

Monitor active (enabled) statistics for system.

Report statistics data.

68P02901W23-T 1-13
Jan 2010
Miscellaneous commands Chapter 1: Introduction to commands

Miscellaneous commands

Miscellaneous commands do not conveniently fit into the categories already outlined. These
commands are used to:
Begin/End a SYSGEN session.

Reset the entire BSS.

Clear database contents.

Display/Modify time function (time-stamp).

Display version of a software load.

Perform miscellaneous procedures, such as displaying the DTE link address, ROM
checksum, and so on.

1-14 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference BSS task-oriented command usage

BSS task-oriented command usage

Table 1-3 shows Network Management activities at the BSS MMI and the related task-oriented
MMI commands.

Table 1-3 Task-oriented MMI commands

Task Related commands

Maintenance (Fault Management) commands:
Display the administrative disp_processor on page state on page 3-576.
state of devices or 3-407,
functions.
Modify the administrative ins_device on page 3-471, lock_device on page 3-478.
state of devices and unlock_device on page 3-645,
associated functions.
Enable, modify, disable, alarm_mode on page 3-52, assess on page 3-54,
and display alarms. chg_eas_alarm on page chg_severity on page 3-167,
3-108, del_act_alarm on page 3-210,
chg_throttle on page 3-176, disp_severity on page 3-424.
disp_act_alarm on page
3-246,
disp_throttle on page 3-427,
System change control (Configuration Management Database) commands:
Configure the BSS. add_cell on page 3-22, add_cell on page 3-22,
add_neighbor on page 3-35, add_nsvc on page 3-47,
add_rtf_path on page 3-50, cell_name on page 3-62,
configure_csfp on page equip on page 3-445,
3-195, reset_device on page 3-544,
reassign on page 3-537, shutdown_device on page
set_full_power on page 3-563.
3-557,
soft_reset on page 3-572,
Modify the CM database. chg_a5_alg_pr on page 3-73, chg_acs_params on page 3-65,
chg_audit_sched on page chg_cell_element on page
3-76, 3-84,
chg_cell_id on page 3-96, chg_csfp on page 3-101,
chg_dte on page 3-104, chg_element on page 3-112,
chg_hop_params on page chg_ksw_config on page 3-154,
3-145, chg_ts_usage on page 3-181,
chg_rtf_freq on page 3-162, copy_cell on page 3-199,
chg_x25config on page del_cell on page 3-212,
3-186,
copy_path on page 3-207,

Continued

68P02901W23-T 1-15
Jan 2010
BSS task-oriented command usage Chapter 1: Introduction to commands

Table 1-3 Task-oriented MMI commands (Continued)

Task Related commands
del_conn on page 3-215, del_neighbor on page 3-217,
del_nsvc on page 3-222, modify_neighbor on page
modify_value on page 3-507, 3-498,set_relay_contact on
unconfigure_csfp on page page 3-561,
3-631, unequip on page 3-633.
Populate the database All MMI commands except the following:
during SYSGEN ON.
alarm_mode, assess,
cage_audit, clear_cal_data,
clear_gclk_avgs, del_act_alarm,
device_audit, diagnose_device
disp_act_alarm, disp_bss,
disp_cal_data, disp_cell_status,
disp_csfp_status, disp_gclk_avgs,
disp_gclk_cal, disp_hdlc,
disp_interval, disp_link_usage,
disp_processor, disp_relay_contact,
disp_rtf_channel, disp_stats,
disp_trace_call, disp_version,
enable_alarm, gclk_cal_mode,
ins_device, lock_device,
query_audits, reattempt_pl,
reset_device, set_full_power,
set_relay_contact, shutdown_device,
site_audit, state,
status_mode, store_cal_data,
swap_devices, trace_call,
trace_stop, unlock_devices.

Display information from cage_audit on page 3-58, disp_a5_alg_pr on page 3-242,

the CM database. disp_acs on page 3-244,
disp_cell on page 3-261,
disp_cell_status on page
3-267,
disp_csfp on page 3-284,
disp_element on page 3-294,
disp_exp_config on page
3-341,
disp_hdlc on page 3-353,
disp_link on page 3-362,
disp_mms_ts_usage on page
3-366,
disp_nsvc on page 3-389,
disp_relay_contact on page
3-414,
disp_rtf_path on page 3-422,
disp_transcoding on page
3-439,
disp_bss on page 3-249,
disp_cell_map on page 3-264,
disp_conn on page 3-282,
disp_csfp_status on page
3-288,
disp_equipment on page 3-315,
disp_gsm_cells on page 3-350,
disp_hopping on page 3-356,
disp_link_usage on page 3-364,
disp_neighbor on page 3-379,
disp_options on page 3-393,

Continued

1-16 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference
Table 1-3 Task-oriented MMI commands (Continued)
Task
Call processing (Database) commands:
Trace the progress of a
specified call by random
trace (by call rate).
Trace the progress of a
specified call by random
trace (by SCCP connection
number).
Report call processing
data.
Stop an existing trace or a
specified call
Statistics (Central Statistics Processing Database) commands:
Enable/disable statistics.
Display/modify statistics
for devices or cells.
Modify statistics time
interval for system.
Monitor active (enabled)
statistics for system.
Report statistics data.
Begin/end a SYSGEN
session (see SYSGEN
mode on page 1-40).
Reset the entire BSS.
Clear database contents.
Modify/display time
function (time-stamp).
Display version of software
load
68P02901W23-T
BSS task-oriented command usage
Related commands
freq_types_allowed on page disp_rtf_channel on page
3-465, 3-416,
site_audit on page 3-568, disp_traffic on page 3-436,
disp_x25config on page 3-443,
query_audits on page 3-532.
disp_trace_call on page trace_call on page 3-613.
3-432,
trace_call on page 3-613.
trace_connection on page
3-625.
trace_stop on page 3-627.
stat_mode on page 5-56.
chg_stat_prop on page 5-5, disp_stats on page 5-39.
disp_interval on page 5-24.
disp_enable_stat on page
5-14.
disp_stat_prop on page 5-26.
Miscellaneous commands:
sysgen_mode on page 3-603.
reset_site on page 3-553.
clear_cal_data on page clear_database on page 3-191,
3-189,
clear_gclk_avgs on page
3-193.
chg_time on page 3-178, chg_throttle on page 3-176.
disp_version on page 3-441.
Continued
1-17
Jan 2010
BSS task-oriented command usage
Table 1-3 Task-oriented MMI commands (Continued)
Task Related commands
Perform miscellaneous chg_level on page 3-160,
tasks (display DTE link, chg_smscb_msg on page
ROM checksum, and so 3-170,
on). del_smscb_msg on page
3-226,
diagnose_device on page
3-238,
disp_cbch_state on page
3-257,
disp_flash on page 3-343,
disp_gclk_cal on page 3-347,
disp_site on page 3-426,
page on page 3-530,
status_mode on page 3-592,
swap_devices on page 3-599,
1-18
Chapter 1: Introduction to commands
connection_code on page
3-197,
device_audit on page 3-230,
disp_cal_data on page 3-253,
disp_dte on page 3-291,
disp_gclk_avgs on page 3-345,
disp_level on page 3-361,
gclk_cal_mode on page 3-469,
reattempt_pl on page 3-542,
store_cal_data on page 3-596,
time_stamp on page 3-611.
68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Command/database parameter security levels

Command/database parameter security levels

Four security levels are provided in the system to control command and database access. Access
to each level is controlled using passwords.

Each command in the system is assigned a security level. Refer to the command description for
a specific command security level.

Level 1

This level permits the display of system parameters. Access is restricted primarily to system
monitoring commands.

Level 2

This level permits access to all system commands, including the ability to change the system
database.

This security level also permits the operator to change passwords for both Level 1 and Level 2
users.

Level 3

This level provides all the features accessible in security Level 2 plus the executive monitor.
Two passwords are required to access security Level 3.

The passwords for this level cannot be changed unless the Optional Level 3 Password Feature
is purchased. This feature enhances BSS security by allowing the Level 3 passwords to be
changed in the event the Level 3 passwords are compromised.

Level 4

This level provides all the features accessible in security Level 3 plus the executive monitor.
Two passwords are required to access security Level 4.

The passwords for this level cannot be changed unless the Optional Level 4 Password Feature is
purchased.

68P02901W23-T 1-19
Jan 2010
Command/database parameter types Chapter 1: Introduction to commands

Command/database parameter types

MMI commands and database parameters are classified based on a user action. If the user
action is required to enter the command, or change the value of the database parameter

Type A commands and parameters

No special user action is required to enter a Type A command, or change a Type A database
parameter.

Type B commands and parameters

The operator is required to perform one or more actions when entering a Type B command,
or changing a Type B database parameter. Operator actions are required before or after the
command entry or database change.

Specific required actions are listed in the Operator actions section of each command and
database parameter description.

1-20 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Commands to be used with caution

Commands to be used with caution

The following commands cause a device to cycle. Before the device is cycled, a prompt is
displayed and must be acknowledged.

add_cell disp_cbch_state
add_nsvc disp_gclk_cal
add_rtf_path disp_hopping
chg_a5_alg_pr equip
chg_cell_element (depends on parameter) freq_types_allowed
chg_dte ins_device
chg_element (depends on parameter) mod_conn
chg_level mod_nsvc
ksw_config modify_value (depends on parameter)
chg_rtf_f reset_device
clear_cal_datareq reset_site
clear_database set_full_power
configure_csfp shutdown_device
copy_cell soft_reset
diagnose_device swap_devices
disp_a5_alg_pr sysgen_mode
disp_act_alarm unconfigure_csfp
disp_hdsl_settings unequip
disp_severity unlock_device

68P02901W23-T 1-21
Jan 2010
Parameters to be used with caution Chapter 1: Introduction to commands

Parameters to be used with caution

The following parameters cause a device to cycle. Before the device is cycled, a prompt is
displayed and must be acknowledged.

bsic downlink_sync_timer
bs_ag_blks_res initial_sync_timer
bs_pa_mfrms smg_gb_vers
cbc_fast_select swfm_enable
ccch_conf uplink_sync_timer

1-22 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Entering MMI commands

Entering MMI commands

Commands are entered by typing the command string followed by pressing the Return key (or
its equivalent).

The following conventions are used to present command strings:

A character sequence that is enclosed in angle brackets <> represents a mandatory
parameter. Wherein a specific variable (value or character string) replaces the string. For
example:<start_time_hour> is entered as an hour between 00 and23.

A character sequence in bold serif type such as example represents a mandatory parameter
that must be entered as is. For example: dri

A character sequence enclosed in [ ] indicates that the parameter is optional. For example:
[<start_time_hour>] or [dri].

Command syntax

The following guidelines must be followed when entering MMI commands.

Command names are case sensitive and cannot be entered as mixed upper and lower
case characters in a command string. Exceptions to this rule are made clear in the text.

An underscore character _ must be used between command keywords, for example

add_cell.

A space character is used between parameters as a command separator.

Example

BSS PROMPT --> add_rtf_path 3 2 1 1

MMI Command First Command Parameter

Space separating Command Parameter

ti-gsm-entering_00018-ai-sw

68P02901W23-T 1-23
Jan 2010
Timeouts Chapter 1: Introduction to commands

The following demonstrates how MMI command examples are represented in this manual:
chg_element bsic 1 0 cell number= 5 4 3 2 1 61986 34944

Where: is:
bsic element_name
1 value
0 location
5 4 3 2 1 61986 34944 cell_desc

System response

COMMAND ACCEPTED

Timeouts

If a response is not entered within 60 sec, the command, or response is rejected, and the
following message displays:

COMMAND REJECTED: No response to prompt.

Ambiguous command response

If the command name is entered incorrectly, the system displays a message stating that the
entered command was ambiguous and lists commands with similar command names.

Example:

MMI-RAM 0115 -> disp_rtf

disp_rtf: Command ambiguous with: disp_rtf_calls disp_rtf_channel disp_rtf_path

Entering hexadecimal values

Some fields accept hexadecimal (hex) values. To specify a hex value:

Lead the value with a 0 (zero).

Type an h at the end of the value.

For example, the hex equivalent for 255 is ff. To specify this hex value, type:

0ffh

1-24 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference MMI command availability

MMI command availability

MMI commands are available according to the site location and whether SYSGEN mode is
On or Off.

Command availability by location

Table 1-4 indicates the sites at which commands can be entered; not the location string
availability for command execution.

Table 1-4 MMI command availability by location

Locations Allowed
Command MMI ROM
BSC BTS RXCDR
add_cell X
add_conn X X
add_neighbor X
add_rtf_path X
alias X X X
assess X X X
cage_audit X X X
cell_name X
chg_a5_alg_pr X
chg_audit_sched X X
chg_cell_element X
chg_cell_id X
chg_csfp X X
chg_dte X X
chg_eas_alarm X X
chg_element X (1) X X
chg_hop_params X
chg_ksw_config X X
chg_level X X X X
chg_rtf_freq X
chg_severity X X
chg_smscb_msg X

Continued

68P02901W23-T 1-25
Jan 2010
Command availability by location Chapter 1: Introduction to commands

Table 1-4 MMI command availability by location (Continued)

Locations Allowed
Command MMI ROM
BSC BTS RXCDR
chg_stat_prop X X
chg_throttle X X
chg_time X X X
chg_ts_usage X X
chg_x25config X X X
clear_cal_data X
clear_database X X
clear_gclk_avgs X X
copy_cell X
copy_path X
del_act_alarm X X X
del_cell X
del_conn X X
del_channel X
del_neighbor X
del_nsvc X
del_rtf_path X
del_smscb_msg X
device_audit X X X
disp_a5_alg_pr X X
disp_act_alarm X X X
disp_bss X X
disp_bssgp_f_bmap X
disp_cal_data X X
disp_cbch_state X X
disp_cell X X
disp_cell_map X X
disp_cell_status X X
disp_conn X X
disp_csfp X X X
disp_csfp_status X X X
disp_dte X X
disp_element X (1) X X X

Continued

1-26 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Command availability by location

Table 1-4 MMI command availability by location (Continued)

Locations Allowed
Command MMI ROM
BSC BTS RXCDR
disp_enable_stat X X X
disp_equipment X X X
disp_flash X X X
disp_gclk_avgs X X X
disp_gclk_cal X X X
disp_gsm_cells X X
disp_hdlc X X X
disp_hopping X X
disp_interval X X X
disp_level X X X
disp_link_usage X X
disp_mms_ts_usage X X X
disp_neighbor X X
disp_nsvc X
disp_options X X X
disp_processor X X X
disp_relay_contact X X X
disp_rtf_channel X X
disp_rtf_path X X
disp_severity X X X
disp_site X X X
disp_stats X X X
disp_stat_prop X X X
disp_throttle X X X
disp_time X X X
disp_trace_call X X
disp_traffic X X
disp_version X X X
disp_x25config X (2) X X
equip X X
freq_types_allowed X
gclk_cal_mode X
help X X X

Continued

68P02901W23-T 1-27
Jan 2010
Command availability by location Chapter 1: Introduction to commands

Table 1-4 MMI command availability by location (Continued)

Locations Allowed
Command MMI ROM
BSC BTS RXCDR
history X X X
ins_device X X X
lock_device X X X
man X X X
mod_conn X X
map_eas_opto X X
mod_nsvc X
modify_neighbor X
modify_value X X
page X X X
query_audits X X X
reassign X X
reattempt_pl X X X
reset_device X X X
reset_site X X X
set_full_power X X
set_relay_contact X X X
shutdown_device X X X
site_audit X X X
soft_reset X X
stat_mode X X
state X X X
status_mode X X X
store_cal_data X
sysgen_mode X X
swap_devices X X X
swfm_enable X X X
time_stamp X X X
trace_call X X
trace_stop X X

Continued

1-28 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Command availability by SYSGEN mode

Table 1-4 MMI command availability by location (Continued)

Locations Allowed
Command MMI ROM
BSC BTS RXCDR
unalias X X X
unconfigure_csfp X X
unequip X X
unlock_device X X X

These commands are not available for MMI ROM processes running on TCU boards.
Also note that these commands do not accept the location or cell parameters used
in the RAM version of these commands.

These commands are only available for MMI ROM processes running on GPROC boards.

Command availability by SYSGEN mode

Table 1-5 shows the availability of commands in the various SYSGEN modes.

Table 1-5 MMI command availability by SYSGEN mode

SYSGEN SYSGEN MODE OFF

Command
MODE ON MMI READY CM READY SITE READY
add_cell X X
add_conn X X
add_neighbor X X
add_nsvc X X
add_rtf_path X X
alarm_mode X
alias X X X X
assess X
cage_audit X
cell_name X X
chg_a5_alg_pr X X
chg_audit_sched X X
chg_cell_element X X
chg_cell_id X X
chg_csfp X X
chg_dte X X
chg_eas_alarm X X

Continued

68P02901W23-T 1-29
Jan 2010
Command availability by SYSGEN mode Chapter 1: Introduction to commands

Table 1-5 MMI command availability by SYSGEN mode (Continued)

SYSGEN SYSGEN MODE OFF

Command
MODE ON MMI READY CM READY SITE READY
chg_element X X
chg_hop_params X X
chg_ksw_config X X
chg_level X X X X
chg_rtf_freq X X
chg_severity X X
chg_smscb_msg X X
chg_stat_prop X X
chg_throttle X X
chg_time X X
chg_ts_usage X X
chg_x25config X X
clear_cal_data X
clear_database X
clear_gclk_avgs X
configure_csfp X
connection_code X X
copy_cell X X
copy_path X X
del_act_alarm X
del_cell X X
del_conn X X
del_neighbor X X
del_nsvc X X
del_rtf_path X X
del_smscb_msg X X
device_audit X
diagnose_device X
disp_a5_alg_pr X X X
disp_act_alarm X
disp_bss X
disp_bssgp_f_bmap X
disp_conn X X X

Continued

1-30 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Command availability by SYSGEN mode

Table 1-5 MMI command availability by SYSGEN mode (Continued)

SYSGEN SYSGEN MODE OFF

Command
MODE ON MMI READY CM READY SITE READY
disp_cal_data X
disp_cbch_state X X
disp_cell X X X
disp_cell_status X
disp_csfp X X X
disp_csfp_status X
disp_dte X X X
disp_element X X X
disp_enable_stat X X X
disp_equipment X X X
disp_flash X X X
disp_gsm_cells X X X
disp_gclk_avgs X
disp_gclk_cal X
disp_hdlc X
disp_hopping X X
disp_interval X
disp_level X X X
disp_link X X X
disp_link_usage X X
disp_mms_ts_usage X X
disp_neighbor X X X
disp_nsvc X X X
disp_options X X X
disp_processor X
disp_relay_contact X
disp_rtf_channel X
disp_rtf_path X X
disp_severity X X
disp_site X X X
disp_stats X
disp_stat_prop X X X
disp_throttle X X X

Continued

68P02901W23-T 1-31
Jan 2010
Command availability by SYSGEN mode Chapter 1: Introduction to commands

Table 1-5 MMI command availability by SYSGEN mode (Continued)

SYSGEN SYSGEN MODE OFF

Command
MODE ON MMI READY CM READY SITE READY
disp_time X X X
disp_trace_call X
disp_traffic X X
disp_version X
disp_x25config X X X
equip X X
freq_types_allowed X X
gclk_cal_mode X
help X X X X
history X X X X
ins_device X
lock_device X
man X X X X
map_eas_opto X X
mod_conn X X
mod_nsvc X X
modify_neighbor X X
modify_value X X
page X X X
query_audits X
reassign X X
reattempt_pl X
reset_device X
reset_site X X X X
set_full_power X
set_relay_contact X
shutdown_device X
site_audit X
soft_reset X X
stat_mode X X
state X
status_mode X
store_cal_data X

Continued

1-32 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Command availability by SYSGEN mode

Table 1-5 MMI command availability by SYSGEN mode (Continued)

SYSGEN SYSGEN MODE OFF

Command
MODE ON MMI READY CM READY SITE READY
swap_devices X
swfm_enable X X
sysgen_mode X X X X
time_stamp X X X
trace_call X
trace_connection X X
trace_stop X
unalias X X X X
unconfigure_csfp X
unequip X X
unlock_device X

68P02901W23-T 1-33
Jan 2010
GSM cell ID format Chapter 1: Introduction to commands

GSM cell ID format

Cell ids are required parameter entries for many commands. The GSM cell ID format consists of
four fields:
MCC - Mobile Country Code

MNC - Mobile Network Code

LAC - Location Area Code

CI - Cell Identity

The GSM cell ID is typically displayed in the following format:

543 021 61986 (F222h) 34944 (8880h)

Where: is:
543 MCC
021 MNC
61986 LAC
34944 CI

NOTE
The LAC and CI values are displayed as hexadecimal values in parentheses, depending
on the command.

Input format

Two types of GSM cell ID input format, seven elements or four elements, can be used. The
format is set with the mmi_cell_id_format parameter.

1-34 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Input format

Seven-element format

The system uses the seven-element format when the mmi_cell_id_format parameter = 0.

cell=5 4 3 2 1 61986 34944

Where: is:
5 first digit of MCC
4 second digit of MCC
3 third digit of MCC
2 first digit of MNC
1 second digit of MNC
61986 LAC
34944 CI

This format cannot be used if the optional third MNC digit is necessary. It is valid for PGSM,
EGSM, DCS 1800 and PCS 1900 systems.

Four-element format

The system uses the four-element format when the mmi_cell_id_format parameter = 1.

cell=543 021 61986 34944

Where: is:
5 first digit of MCC
4 second digit of MCC
3 third digit of MCC
0 first digit MNC
2 second digit of MNC
1 third digit of MNC
61986 LAC
34944 CI

This format must be used if the optional third MNC digit is necessary. It can be used for PGSM,
EGSM, and DCS 1800 systems.

If the first and/or second digit of the MCC is a zero, it can be omitted from the input. The system
recognizes both of the following examples as valid format:

001 011 98765 543211 011 98765 54321

68P02901W23-T 1-35
Jan 2010
Cell name Chapter 1: Introduction to commands

NOTE
If the third MNC digit is required, all three MNC digits must be entered. For example,
if the MNC = 001 and the third MNC digit is required, the MNC must be entered as
001. If the MNC is entered as 01 or 1, the system interprets the entry as MNC=01,
which is incorrect.

Cell name

Each GSM cell is assigned a cell name using the cell_name command. The cell_name is used in
place of the GSM cell ID in most of the BSS MMI commands. Refer to the individual command
descriptions to determine if the cell_name can be used for a specific command.

1-36 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Indices

Indices

Indices are used to display information or locate information in a data array.

Device indices

Device indices are used with the disp_element command for displaying information associated
with the System Audit Process (SAP). Table 1-6 lists the device types and associated indices.

Table 1-6 Device Indices

Device Type Index

KSW 0
KSW 1
(internal loopback tests)
MSI 2
DRI 4
GCLK 6
GPROC 8
BSP 12
BTP 14
DHP 16
SITE 18
TDM 20
PCU 22
PSP 24
DPROC 26

For example, the command string

disp_element sap_start_time,12 0

displays the audit start time for BSPs (index 12) at location 0.

68P02901W23-T 1-37
Jan 2010
Data array location Chapter 1: Introduction to commands

Data array location

An index is used to identify the location of information in a data array.

Single index number

A single index number can identify the column in a single row array where a data element is
located. The following example shows the command string used to display the value of the
interference level for index level 0 (band 1), in an interfer_bands parameter:

disp_element interfer_bands,0 1 cell=0 0 1 0 1 1 1

Two index numbers

Some statistical elements require two index numbers. The first index number is the row
number. The second index number is the position of the element in the row. For example,
the command string
disp_element sap_audit_type,0,1 0
displays the value of the sap_audit_type parameter located in row 0, column 1 of a multi-row
data array.

Bins

A single row of a data array can be referred to as a bin. If a command uses bin numbers to specify
the row in a data array, the index number specifies the position of the data element in the bin.

The following represents an array with four bins with 32 elements in each bin:

bin 0 [0 1 2 ... 31]

bin 1 [0 1 2 ... 31]

bin 2 [0 1 2 ... 31]

bin 3 [0 1 2 ... 31]

The following example shows the command string that is used to assign or change the value of
the rxlev_ul_ho parameter. The value of the parameter is located in the first column (index = 0)
of the second bin (bin_num = 1):

chg_cell_element rxlev_ul_ho 2 6 2 0 2 2868 3100 1 0 8,0

The following example shows the command string that is used to display the contents of a bin.
The index value used with the disp_element command is the bin number used when assigning
or changing the value of one of the elements of the parameter:

disp_element rxlev_dl_ho,1 0 cell_number=2 6 2 0 2 2868 3100

rxlev_dl_ho = alg_num: 1 alg_data: 8 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

1-38 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Thresholds

Thresholds

Gauge and some counter statistics can be assigned thresholds. An alarm is sent to the OMC-R
when the threshold is exceeded. The severity of the alarm associated with a statistical
parameter can be displayed using the disp_element command using an index value of 1. For
example, the command string

disp_element invalid_frames_rx,1 0

displays the severity of the alarm associated with the invalid_frames_rx statistical parameter:

invalid_frames_rx = 2

Table 1-7 lists the alarm severities.

Table 1-7 Alarm Severities

Alarm Number Severity

0 Investigate
1 Critical
2 Major
3 Minor
4 Warning
5 Clear

EAS alarm table

The EAS table consists of 34 indexed pairs. Each pair includes a severity level and up to 24
text characters. Both the text and severity level are assigned when the EAS alarm table is
initialized using the chg_eas_alarm command. After initialization, the text and severity level
can be displayed independently using the disp_element eas_alarm or the disp_element
eas_severity commands respectively.

The severity level can be modified independently using the chg_element eas_severity
command.

68P02901W23-T 1-39
Jan 2010
SYSGEN mode Chapter 1: Introduction to commands

SYSGEN mode

SYSGEN mode ensures that database entries are checked at system initialization or after a
change in database parameters. SYSGEN mode must be On to allow entry of some commands or
changes to certain parameters. SYSGEN mode is set On or Off using the sysgen_mode command
(see sysgen_mode on page 3-603).

SYSGEN OFF

The SYSGEN OFF mode is the normal system mode of operation. The sysgen_mode off
command places the system in the SYSGEN OFF mode.

If the system is in the SYSGEN ON mode and the sysgen_mode off command is entered, any
changes made to the database are checked and the following displayed:

*******VERIFYING DATABASE BEFORE COMPLETING SYSGEN*******

Frequency hopping verification in progress.
SITE 0 Verification.
DB Verification passed.
COMMAND ACCEPTED.

After the system initializes, it is in the SYSGEN OFF mode.

If the system is in the SYSGEN OFF mode and the sysgen_mode off command is entered, the
command is rejected and the following message displays:

COMMAND REJECTED: sysgen mode is already off

SYSGEN ON

The system must be placed in the SYSGEN ON mode of operation to enter some commands or
change some parameters. Until the system is returned to its normal mode of operation, changes
can be entered into the database without being checked.

CAUTION
Do NOT enter the sysgen_mode on or the sysgen_mode off commands at the
OMC-R.

If the system is in the SYSGEN OFF mode and the sysgen_mode on command is entered, the
system prompts the user to reinitialize the site:

COMMAND ACCEPTED: You must re-init the site to start SYSGEN

1-40 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Database changes in SYSGEN ON mode

If the system is in the SYSGEN ON mode and the sysgen_mode on command is entered, the
command is rejected and the following message displays:

COMMAND REJECTED: sysgen mode is already on

The system rejects the sysgen_mode command if it is entered at a GPROC that is not acting as
the master GPROC:

COMMAND REJECTED: Command only allowed at active BSP.

Database changes in SYSGEN ON mode

In a network, the BSC connects to an OMC-R and a copy of the BSC database is stored at the
OMC-R. Sometimes a difference is detected between the database load in the OMC-R and the
BSC. Then the OMC-R automatically downloads a copy of the database in its memory to the
BSC. Any changes made while the BSC was in the SYSGEN ON mode are overwritten by the
download from the OMC-R.

If the changes to be made while the BSC is in SYSGEN ON mode are to be retained, the
following procedure must be used:

Procedure 1-1 Retain database changes made in SYSGEN ON mode

1 Disable downloads for network elements at the OMC-R.

2 Enter the sysgen_mode on command at the BSC
3 Enter the reset_site 0 command.
4 After the system has reset, modify or enter the commands to the
database as necessary.

NOTE
Commands must be entered within 10 minutes after the MMI
RAM: prompt is presented. If a command is not entered, the
system resets.
5 Enter the sysgen_mode off command at the BSC.
6 After the system has returned to service, upload the modified database
from the BSC to the OMC-R. The upload is done at the OMC-R.
7 Re-enable downloads for network elements at the OMC-R.

68P02901W23-T 1-41
Jan 2010
Initial SYSGEN mode Chapter 1: Introduction to commands

Initial SYSGEN mode

The initial SYSGEN mode occurs when the system is placed in the SYSGEN ON mode without
a Configuration Management (CM) database. The initial SYSGEN mode is used to load the
CM database using a script.

CAUTION
Personnel who fully understand the consequences must use the clear_database
command.

The system is placed in the initial SYSGEN mode by placing the system in the SYSGEN ON mode
then entering the clear_database command.

Scripts

A script is a file that contains a series of commands which load the CM database into the system.

A script is loaded in the initial SYSGEN mode and permits large amounts of information to be
loaded efficiently onto the system.

After the database is loaded using a script, the system must be returned to the SYSGEN OFF
mode to verify the script contents. If errors are detected, the system does not return to the
SYSGEN OFF mode. Correct the script and reload before the system returns to its normal
operating state.

SYSGEN safety features

Automatic GPROC addition

If the initial SYSGEN mode is entered from a GPROC which is not included in the script, a
GPROC is added automatically to the slot from which the initial SYSGEN mode was entered.

Enter the initial SYSGEN mode from the same type of system for which the database is being
loaded. For example, if the script to be loaded is for an RXCDR, enter the initial SYSGEN mode
from the master slot of an RXCDR (011ah). If the script to be loaded is for a BSS, the initial
SYSGEN mode must be entered from the master slot of a BSC (0115h).

Safety timer

If the system is in the SYSGEN ON mode, a timer is used to ensure that a GPROC cannot be
left in the SYSGEN ON mode indefinitely. The timer is started when no activity is detected
from the TTY terminal. If activity is detected before the timer expires, the timer is reset to its
initial value and restarted.

If the timer expires, the GPROC is reset with a Global Kill SWFM. Within the SWFM, a message
includes a textual description that the timer expired.

1-42 68P02901W23-T
Jan 2010
 Chapter

Equipping the CM database

This chapter provides information on equipping the CM database at a site. The following topics
are in this chapter:
Introduction to equipping the CM database on page 2-2: introducing equip
command, and listing prerequisites for equipping the database, restrictions on equipping a
site, and equip related commands.

Using the equip command on page 2-5: providing information on the format and usage
of equip command at the MMI.

Equipage hierarchy on page 2-6: containing information and hierarchical charts for
equipping devices and functions in different systems.

Information for equipping devices on page 2-12: detailing the conditions, rules, and
command prompts for each device that can be equipped in the CM database.

Information for equipping functions on page 2-57: detailing the conditions, rules, and
command prompts for each function that can be equipped in the CM database.

68P02901W23-T 2-1
Jan 2010
Introduction to equipping the CM database Chapter 2: Equipping the CM database

Introduction to equipping the CM database

Devices and functions are added to the Fault Management portion of the CM database using
equip command (see equip on page 3-445). Since each device and function has specific
parameters, there is a corresponding set of prompts. Each device and function also has specific
restrictions for equipage.

Command prompt details and equipage restrictions for each device/function are provided in
this chapter.

Devices and functions that can be equipped

The following devices and functions can be equipped in the CM database using equip command:

Devices
ABSS AXCDR BSP BSS
BTP CAB CAGE CBL
CIC COMB CSFP DHP
DPROC DRI DYNET EAS
GBL GCLK GDS GPROC
GSL KSW LMTL MSI
MTL OML OPL PATH
PCU PSP PSI RSL
RXCDR SITE XBL ETH

Functions
LCF OMF RTF

Prerequisites for equipage tasks

The following prerequisites requiring operator actions can apply before using equip command:
Some devices and functions require the system to be in the SYSGEN ON mode. To enter
this mode, enter the sysgen_mode on command. To exit this mode, use the sysgen_mode
off command (see sysgen_mode on page 3-603).

Some devices require the site to be locked. To lock the site, enter the lock_device
command (see lock_device on page 3-478). To unlock the site, enter the unlock_device
command (see unlock_device on page 3-645).

2-2 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Equipage restrictions

Some devices and functions can be equipped only after other devices have been equipped.
Refer to Equipage hierarchy on page 2-6 for further information.

GPRS devices can be equipped only if the GPRS feature is unrestricted.

The LMTL can be equipped only if the Location Services support feature is unrestricted
and the BSS can support a BSS-based SMLC.

To equip a device or function with a frequency, it first must be set as allowable with the
freq_types_allowed command (see freq_types_allowed on page 3-465).

Refer to the instructions included with each device or function for specific actions to be taken
when using equip command.

Equipage restrictions

The following restrictions apply at the BSC when equipping the CM database:
A BSC of type 1 or 2 must equip remote sites with an LCF.

No more than three PCUs can be equipped per BSC.

In addition, each device and function has specific restrictions for equip age.

NOTE
The equip command can be entered only at the BSC. This command does not work at
a BTS site. Contact the OMC-R for help in setting up a BTS site.

Equip related commands

The following MMI commands are related to equipping devices and functions:
disp_equipment on page 3-315: Used to display equipped devices and functions.

freq_types_allowed on page 3-465: Used to set the frequency types and blocks available at
the BSS.

lock_device on page 3-478: Used to lock a site to equip certain devices.

modify_value on page 3-507: Used to modify the parameter values of an equipped device
or function.

reassign on page 3-537: Used to reassign a child device from its current parent function
to a new parent function.

shutdown_device on page 3-563: Used to shut down a device before modifying or

unequipping the device.

68P02901W23-T 2-3
Jan 2010
Equip related commands Chapter 2: Equipping the CM database

state on page 3-576: Used to display the status of devices and functions in the system.

unequip on page 3-633: Used to unequip an equipped device or function.

unlock_device on page 3-645: Used to unlock a site after equipping certain devices.

2-4 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Using the equip command

Using the equip command

Enter equip command at the MMI. Specify the site location and the name of the particular
device or function to be added to the CM database.

The equip command can be entered only at the BSC. It does not work at a BTS.

The system responds with a series of command prompts for further operator input. The
information requested is dependent on the particular device or function being equipped. If
a device or function parameter is optional, there is no need to enter data, simply press the
ENTER key at the prompt.

The equip command can be exited at any time by entering done in response to any prompt.

Format of equip command

The format of equip command entered at the MMI prompt is:

equip <location> <dev/func_name>

Where: is:
location The location of the device or function, one of:
0 or bsc for a BSC.
0 - 140 for a BTS.
pcu or pcu_0 for a PCU.
dev/funcc_name The name of the device or function being
equipped.

System response

The system responds with an appropriate set of prompts for the particular device or function
being equipped. Enter the correct information in response to the prompts and conditions for
equipping the particular device or function. The system indicates execution with COMMAND
ACCEPTED message which can be accompanied with a WARNING message. If incorrect
information is entered or the particular equip conditions are not met, a COMMAND REJECTED
with reason message is issued.

Equip conditions and system prompts are provided in:

Information for equipping devices on page 2-12.

Information for equipping functions on page 2-57.

68P02901W23-T 2-5
Jan 2010
Equipage hierarchy Chapter 2: Equipping the CM database

Equipage hierarchy

Devices and functions have a hierarchical structure which can differ between systems.

Some devices and functions can only be equipped after other devices have been equipped. For
example, a CAGE must be equipped before a BTP can be equipped.

Other devices are automatically equipped. For example, an MMS is equipped automatically
when equipping an MSI.

Equipage hierarchy charts in this section show the order in which devices and functions are
equipped for the following systems:
RXCDR

InCell

M-Cell and Horizon macro

GPRS

RXCDR

Figure 2-1 shows the device and function hierarchy for RXCDR systems. In this system, an MMS
is automatically equipped when an MSI is equipped.

2-6 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference RXCDR

Figure 2-1 Remote Transcoder (RXCDR) devices and functions

NOTE
* indicates an automatically equipped device.

68P02901W23-T 2-7
Jan 2010
InCell Chapter 2: Equipping the CM database

InCell

Figure 2-2 shows the device and function hierarchy for InCell systems. In these systems, an
MMS is automatically equipped when an MSI is equipped.

Figure 2-2 BSC and InCell BTS

BSS SITE (BSC)

CAB PCU DYNET AXCDR

Conn_Link
CAGE

PSI KSW GCLK BSP GPROC CSFP EAS MSI

ETH LCF OMF

MMS*

RF_Unit
GDS
(LAPD_TRAU)
GSL MTL OML CIC
GSL LMTL CBL XBL
ti-GSM-BSC Incell BTS-00015-eps-sw

NOTE
* indicates an automatically equipped device.

2-8 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference M-Cell and Horizon macro

M-Cell and Horizon macro

Figure 2-3 shows the device and equipment hierarchy for M-Cell and Horizon macro systems.
In these systems, GCLK and CSFP functionality are built into an MCU and are automatically
equipped when a BTP is equipped.

Figure 2-3 M-Cell and Horizon macro equipage hierarchy chart

NOTE
* indicates an automatically equipped device.

68P02901W23-T 2-9
Jan 2010
Horizon II macro Chapter 2: Equipping the CM database

Horizon II macro

{33254}

Figure 2-4 shows the device and equipment hierarchy for the Horizon II macro systems.

Figure 2-4 Horizon II macro equipage hierarchy chart

BSS

SITE

CELL CAB (HII macro/micro/mini)

CTU/CTU2 BTP (HIISC2-E/S) NIU (MSI) COMB

(DRI)
MCU

GCLK* CSFP

PATH

RTF 16kbit/s RSL 64kbit/s RSL

ti-gsm-horizonmacro_II_equipage-00020-ai-sw

NOTE
* indicates an automatically equipped device.

2-10 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference GPRS

GPRS

Figure 2-5 shows the device and function hierarchy for the PCU device in a GPRS system. In the
GPRS system, the CAB and CAGE devices are automatically equipped when a PCU is equipped.
Also an MMS is automatically equipped when an MSI is equipped.

Figure 2-5 GPRS PCU devices and functions

BSS SITE (BSC)

PCU

CAB*

CAGE*

MPROC (PSP*) DPROC (PICP) DPROC (PRP) DPROC (PXP)

PPROC* ETH MSI *

MSI (PMC) MSI (PMC) MSI (PMC)

MMS* MMS*
MMS* MMS* GDS*
(LAPD_TRAU)

GBL GDS (LAPD) GDS (TRAU) GBL*

GSL*
GSL
ti-GSM-PCU_devices_and_functions-00017-eps-sw

NOTE
* indicates an automatically equipped device.

68P02901W23-T 2-11
Jan 2010
Information for equipping devices Chapter 2: Equipping the CM database

Information for equipping devices

This section references conditional information for the rules on equipping various devices, and
equip command prompts that occur with each of the following devices:

ABSS on page 2-12 AXCDR on page 2-13 BSP on page 2-14

BSS on page 2-14 BTP on page 2-15 CAB on page 2-16
CAGE on page 2-19 CBL on page 2-20 CIC on page 2-20
COMB on page 2-22 CSFP on page 2-23 DHP on page 2-24
DPROC on page 2-25 DRI (InCell sites) on page DRI (M-Cell and Horizon
2-25 macro sites) on page 2-27
DYNET on page 2-31 EAS (InCell sites) on page EAS (M-Cell sites) on page
2-33 2-34
GBL on page 2-35 GCLK on page 2-37 GDS on page 2-38
GPROC on page 2-39 GSL on page 2-39 KSW on page 2-40
LMTL on page 2-41 MSI (InCell, BSC, and RXCDR MSI (M-Cell sites) on page
sites) on page 2-41 2-44
MSI (PCU only) on page 2-45 MTL on page 2-47 OML on page 2-48
OPL on page 2-48 PATH on page 2-49 PCU on page 2-51
PSI on page 2-52 PSP on page 2-53 RSL on page 2-53
RXCDR on page 2-54 SITE on page 2-54 XBL on page 2-55

ABSS

Equip conditions

The Associated Base Station Subsystem (ABSS) can be equipped with the system in SYSGEN
ON mode.

This device can also be equipped when the system is outside the SYSGEN ON mode and it is
to be the standby device.

An ABSS device can only be equipped at an RXCDR site. The maximum number of ABBSs
that can be equipped at an RXCDR site is 10.

If an ABSS device is referenced in the BSS-RXCDR connectivity table, it cannot be unequipped.

The BSS-RXCDR connectivity table is created using the add_conn command.

2-12 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference AXCDR

Command prompts

Prompt Optional Range Default Comments

Enter the ABSS N 1 - 254 None This value corresponds to the BSS
device ID: network entity that this device
represents.

AXCDR

Equip conditions

The Associated RXCDR (AXCDR) can be equipped with the system in SYSGEN ON mode.

This device also can be equipped when the system is outside the SYSGEN ON mode and it is
the standby device.

The AXCDR can be equipped only at a BSC that is set to remote transcoding. The maximum
number of AXCDRs that can be equipped at a BSC site is 10.

The AXCDR cannot be unequipped if it is referenced in the BSS-RXCDR connectivity table.

Command prompts

Prompt Optional Range Default Comments

Enter the AXCDR N 1 - 254 None This value corresponds to the
device ID: RXCDR network entity that this
device represents.
Perform CIC N yes or no None CIC validation must be enabled to
validation?: set eac_mode to 1 (enabled).
Enable Enhanced 0 or 1 0 The eac_mode can only be set to
Auto-Connect Mode: 1 (enabled) if the AMR Enhanced
Capacity feature and/or the GSM
Half Rate feature is unrestricted.
Enter the N 0 - 245 0 A prompt for this value is
CIC blocking presented only if the eac_mode is
threshold: enabled.
Enter the CIC N 1 - 225 0 A prompt for this value is
unblocking presented only if the eac_mode is
threshold: enabled.

68P02901W23-T 2-13
Jan 2010
BSP Chapter 2: Equipping the CM database

BSP

Equip conditions

The Base Station Processor (BSP) can be equipped with the system in SYSGEN ON mode.

The BSP can also be equipped when the system is outside the SYSGEN ON mode and it is
to be the standby device.

Command prompts

Prompt Optional Range Default Comments

Enter the BSP N 0 or 1 None
identifier:
Enter the cage N 0 or 1 None BSPs can be only GPROCs with
number: the following Cage and Slot
restrictions based on site type:
Enter the slot N 20, 24, None
BSC and BSS sites:
number: 25, 26
- cage 0, slots 20, 24
- cage 1, slot 20.
RXCDR sites:
- cage 0, slots 25, 26
- cage 1, slot 25.
BTS sites: not allowed.

BSS

Equip conditions

The Base Station Subsystem (BSS) must be the first device equipped by the operator during
SYSGEN mode at a BSS site.

Command prompts

Prompt Optional Range Default Comments

Enter the BSS N 1 - 254 None
identifier:
Is local N yes or no None
transcoding
performed at the
BSC (yes/no):

2-14 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference BTP

BTP

Equip conditions

The Base Transceiver Processor (BTP) can be equipped with the system in SYSGEN ON mode.

This device also can be equipped when the system is outside the SYSGEN ON mode and it is
to be the standby device.

When equipping BTPs to M-Cell sites, BTP 0 must be the first BTP equipped.

This device can be equipped only at a BTS site.

For a bts_type of 0, no more than two radios must be equipped.

For a Horizon II macro controlling cabinet, the BTP manages the auto-equip (and auto-unequip)
of the MSI device 0 0 0 (with three associated MMS devices) at the BTS site.

Only one BTP can be equipped at a site with a Horizon II mini master cabinet.

Command prompts

The following prompts do not display for all installations. Some devices set certain parameters
automatically. The system does not prompt for values set automatically.

Prompt Optional Range Default Comments

Enter BTP N 0 or 1 None For M-Cell2 and M-Cell6 sites, this
identifier: prompt has the following meaning:
0 = card frame 0,
1 = card frame 1.
Enter the cage N 14 or 15 None BTPs can only be GPROCs with
number: the following Cage and Slot
restrictions based on site type:
Enter the slot N 20 or 24 None
number: BSC, BSS, and RXCDR sites: not
allowed
BTS sites:
- cage 15, slots 20, 24,
- cage 14, slot 20.
Enter maximum DRIs N 0 - 6 None If the BTS type is 0, the maximum
supported by this number of DRIs cannot be 0.
BTP:

68P02901W23-T 2-15
Jan 2010
CAB Chapter 2: Equipping the CM database

CAB

Equip conditions

The Cabinet (CAB) can be equipped with the system in SYSGEN ON mode.

This device also can be equipped when the system is outside the SYSGEN ON mode and it is
to be the standby device.

If the CAB is equipped for GPRS, the system rejects the equip CAB command. The CAB is
automatically equipped when the PCU is equipped.

If the frequency_type is not supported for the cab_type, the system rejects the equip CAB
command.

The following dependencies govern what type of cabinets can be equipped at different sites:
M-Cell and transceiver cabinets cannot be equipped at site 0 (BSC).

M-Cell and transceiver cabinets cannot be equipped at an InCell site.

InCell cabinets cannot be equipped at an M-Cell site.

Horizon II macro and Horizon II macro extension cabinets can be combined with the
following at a BTS site:
M-Cell6

TCU_6

Horizon macro

Horizon macro extension cabinets

Command prompts

Prompt Optional Range Default Comments

Enter the N 0 - 15 None
CABINET
identifier:
Enter the N None M-Cell and transceiver cabinets cannot be
cabinet type:
0 - 27 equipped at an InCell site.
InCell cabinets cannot be equipped at an
M-Cell site.
The system rejects the command if:

The bts_type is not 0, and

The cabinet_type = 10, 11, 14, 15, 16 or

20.
Enter this value either as a number or string:

Continued

2-16 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference CAB

Prompt Optional Range Default Comments

No String Cabinet type
0 bts4d_48v BTS4D 48 volt
1 bts4d_27v BTS4D +27 volt
2 bssc_48v BSSC 48 volt
3 bssc_27v BSSC +27 volt
4 bts_dab BTS with DAB
5 bssc_dab BSSC with DAB
6 excell_4 ExCell 4
7 excell_6 ExCell 6
8 topcell TopCell
9 bts_5 BTS 5
10 m_cell_2 M-Cell 2
11 m_cell_6 M-Cell 6
12 tcu_2 TCU-2
13 tcu_6 TCU-6
14 m_cellmicro M-Cellmicro
15 m_cellcity M-Cellcity
16 m_cellarena M-Cellarena
18 Horizon macro Horizon macro
master cabinet
19 Horizonmacro_ext Horizon macro
extension cabinet
20 m_cell M-Cellarena macro
arena_macro BTS (Horizon
compact)
22 horizon Horizonmicro2
micro2 BTS
23 horizon horizoncompact2
compact2 BTS
24 horizonmacro2 Horizon II macro
cabinet
25 horizonmacro2_ext Horizon II macro
extension cabinet
26 Horizon II mini/ HorizonII mini /
Horizon II micro Horizon II micro
27 Horizon II mini_ext Horizon II mini
Horizon II extension /
micro_ext Horizon II micro
extension

Continued

68P02901W23-T 2-17
Jan 2010
CAB Chapter 2: Equipping the CM database

Prompt Optional Range Default Comments

Enter the N 1 to 15 None This value can be entered by number or as a
frequency string:
type:
No String
1 pgsm
2 egsm
3 pgsm, egsm
4 dcs1800
5 pgsm, dcs1800
6 egsm, dcs1800
7 pgsm, egsm, dcs1800
8 pcs1900
9 pgsm, pcs1900
10 egsm, pcs1900
11 pgsm, egsm, pcs1900
12 dcs1800, pcs1900
13 pgsm, dcs1800, pcs1900
14 egsm, dcs1800, pcs1900
15 pgsm, egsm, dcs1800, pcs1900
Combinations of frequency types can also be
entered:

Numbers and strings can be combined in

a single command.

A comma must separate different

frequency types, for example: pgsm, 2, 4

Horizon II macro and Horizon II macro

extension cabinets can only be equipped with
frequency type 1, 2, 4 or 6.
For the four Branch Receive Diversity to be
enabled, Horizon II macro and Horizon II
macro extension cabinets can only be equipped
with frequency types 1, 2 and 4.
Is an Y yes or None This prompt is only displayed if the site type is
internal no M-Cellcity, Horizon micro or Horizon compact.
HDSL modem
present?:
Is an Y yes or None This prompt is only displayed if the site type is
internal no M-Cell city or Horizon micro.
integrated
antenna
present?:

2-18 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference CAGE

CAGE

Equip conditions

A Cage (CAGE) can be equipped with the system in SYSGEN ON mode.

This device also can be equipped when the system is outside the SYSGEN ON mode and it is
to be the standby device.

The master slots are contained in cages 0 and 1 for BSS, BSC, and RXCDR sites and in cages
14 and 15 for BTS sites. For this reason, cage 0 and/or 1 for BSS, BSC, or RXCDR type sites
and cage 14 and/or 15 must be equipped at BTS type sites.

If the cage is equipped for GPRS, the system rejects the equip CAGE command. The cage is
automatically equipped when the PCU is equipped.

At M-Cell sites, the CAGE device cannot be equipped. The cage is automatically equipped when
the first BTP at a site is equipped.

Command prompts

Prompt Optional Range Default Comments

Enter the device N 0 - 15 None The cage number (ID) must be
identification for equal to the setting on the LANX
the cage: card.
Valid identifiers for a BSS, BSC,
or RXCDR Cage are 0 to 13. Valid
identifiers for a BTS cage are 2 to
15.
Enter the KSW pair N 0 - 3 None See NOTE.
that manages the
cage:
Enter the KSWX Y 0 - 4 None See NOTE.
connecting cage
to KSW for TDM 0:
Enter KSWX Y 0 - 4 None See NOTE.
connecting cage
to KSW for TDM 1:
Enter the cabinet N 0 - 23 None
to which the cage
belongs:
Is an IAS Y yes or yes
connected?: no

NOTE
Slots U2 through U7 can contain CLKX cards or KSWX cards. The system checks
the contents of these slots any time a change implies the existence of a new CLKX,
EXP KSWX, or remote KSWX card. The system rejects the change if the new card
occupies a slot that is already occupied.

68P02901W23-T 2-19
Jan 2010
CBL Chapter 2: Equipping the CM database

CBL

Equip conditions

The Cell Broadcast Link (CBL) can be equipped with the system in either the SYSGEN ON or
SYSGEN OFF mode.

The CBL cannot be equipped at an RXCDR site.

The CBL can be equipped only at a BSC (site 0).

The CBL cannot be equipped on an HDSL link.

Command prompts

Prompt Optional Range Default Comments

Enter the device Y 0 0
ID for the CBL:
Enter the first N 0 - 9 None
MMS identifier for
this device:
Enter the second N 0 or 1 None
MMS identifier for
this device:
Enter the timeslot N 1 - 31 for None
on MMS where this E1 links
device appears:
Enter the BSS N up to 20 None The BSS operator must be in
Operator: alphabetic quotation marks.
characters
Enter the CBC N up to 20 None The CBC operator must be in
Operator: alphabetic quotation marks.
characters

CIC

Equip conditions

The Circuit Identity Code (CIC) can be equipped with the system in either SYSGEN ON or
SYSGEN OFF mode.

A single CIC or a range of unique CICs can be equipped for each MMS.

If all CICs in the range can be equipped when equipping a range of CICs, the equip CIC
command is accepted. If one or more CICs cannot be equipped, the command is still accepted.
However, the CICs that cannot be equipped are listed in a display with the reason that each
could not be equipped. If none of the CICs in a range can be equipped, the command is rejected
and the reason displayed.

2-20 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference CIC

The parent MMS must be equipped before equipping the CIC. If the MMS on which the CIC is to
be equipped does not appear in the CM Database, the equip CIC command is rejected.

The equip CIC command is rejected if the CIC is not unique or if the timeslot/group is not
available.

The CIC can be equipped only at a BSC or RXCDR (site 0).

The CIC cannot be equipped on an HDSL link.

Equipping CICs at a BSC

When equipping a CIC at a remote transcoding BSC, the RXCDR providing the TRAU for the
CIC must be specified.

The operator is also prompted for a static MMS timeslot to the RXCDR. However, if the BSC is
operating in static mode, it is not required. In this case, the CIC is blocked.

In autoconnect (non-static) mode, the static MMS is not required. If the CIC is equipped in this
way and the BSC is in backwards compatibility (static) mode, the CIC is blocked.

Usually, all TRAU circuits must be equipped to GDP boards when efr_enabled is set to 1
(enabled) for the BSS.

NOTE
The call downgrade feature is an exception. For example, an RXCDR has two CICs
equipped. The first to an XCDR (Full rate support only) and the second to GDP
(Enhanced Full and Full rate support). On the BSC, the efr_enabled is set to 1,
allowing Enhanced Full rate calls on the second CIC and Full rate calls on first CIC.
The TRAU circuits do need not be equipped to GDP just because efr_enabled is
enabled.

Equipping CICs at an RXCDR

When equipping a CIC at an RXCDR, the BSS managing the CIC must be specified.

The operator also is prompted for a static MMS timeslot to the BSS. However, if the BSC is
operating in static mode, it is not required. In this case, the CIC is blocked.

The same CIC identifier can be equipped multiple times at an RXCDR as it can be used for
multiple BSSs.

68P02901W23-T 2-21
Jan 2010
COMB Chapter 2: Equipping the CM database

Command prompts

Prompt Optional Range Default Comments

Enter the CIC(s): N 0 - 65535 None No more than 128 CICs can be
equipped at a time (for remote
transcoding). For RXCDR and
local transcoder BSS, only 30
CICs can be equipped.
Multiple CICs can be entered
using the format: CIC# to CIC#
(for example, 255 - 286).
Which RXCDR is N 1 - 128 None This prompt only appears for
providing the TRAU remote transcoding BSC sites
resource(s): only.
Which BSS is N 1 - 128 None This prompt only appears for
managing the RXCDR sites only.
CIC(s):
Enter the MMS ID to Y None This prompt only appears for
the RXCDR: remote transcoding BSC sites
only.
Enter the MMS ID to Y None This prompt only appears for
the BSS: RXCDR sites only.
Enter starting N 1 - 31 (E1 None This prompt appears only if an
timeslot: links) MMS ID is specified.
Enter starting N 0 - 3 None This prompt appears only if there
subgroup: is remote transcoding and an
MMS is specified.
Enter the MMS ID to N None This prompt appears for RXCDR
MSC: sites and local transcodings only.
Enter starting N 1 - 31 (E1 None This prompt appears for RXCDR
timeslot: links) sites and local transcodings only.

COMB

Equip conditions

The Combiner (COMB) can be equipped with the system in either the SYSGEN ON or SYSGEN
OFF mode.

2-22 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference CSFP

Command prompts

Prompt Optional Range Default Comments

Enter the N 0 - 13 None
first COMBiner
identifier:
Enter the COMBiner N 0 - 255 None The COMB address must be
address: unique at the same site. If the
COMB address is not unique, the
command is rejected.

CSFP

Equip conditions

The Code Storage Facility Processor (CSFP) can be equipped with the system in either the
SYSGEN ON or SYSGEN OFF mode.

At an M-Cell site, the operator cannot explicitly equip the CSFP. Instead the CSFP is
automatically equipped when the first BTP at a site is equipped.

Command prompts

Prompt Optional Range Default Comments

Enter the CSFP N 0 or 1 None This prompt only appears at a
identifier: BSC.
Enter the cage N See None BSS sites: cages 0 to 13, slots 18
number: Comments to 25.
BSC sites: cages 0 to 13, slots 18
to 25.
BTS sites: cages 2 to 15, slots 18
to 25.
RXCDR sites: cages 0 to 13, slots
25 and 26.
Enter the slot N See None BSS sites: cages 0 to 13, slots 18
number: Comments to 25.
BSC sites: cages 0 to 13, slots 18
to 25.
BTS sites: cages 2 to 15, slots 18
to 25.
RXCDR sites: cages 0 to 13, slots
25 and 26.

NOTE
A CSFP should be equipped in the same physical slots in the database between
different loads during upgrade and rollback.

68P02901W23-T 2-23
Jan 2010
DHP Chapter 2: Equipping the CM database

DHP

Equip conditions

The Digital Radio Host Processor (DHP) can be equipped with the system in either the SYSGEN
ON or SYSGEN OFF mode.

The DHP can be equipped only at a BSS or a BTS site.

The DHP cannot be equipped at an M-Cell site.

The underlying GPROC need not be equipped to equip a DHP.

Command prompts

Prompt Optional Range Default Comments

Enter the cage N 0 - 15 None This identifier must be equal to
number for this the cage number where the DHP
DHP (identifier 1): is to reside. A maximum of eight
GPROCs can exist in a single
cage.
Enter the unique N 0 - 7 None BSS sites: cages 0 to 13: slots
DHP number in this 18 to 25.
cage (identifier BTS sites: cages 2 to 15: slots
2): 18 to 25.
Enter the slot N 18 - 25 None
number:
Enter the maximum N 1 - 6 None
number of DRIs
supported by this
DHP:

NOTE
The modify_value parameter max_dris is automatically set to 6, which is the
maximum number of DRIs supported by a DHP.

2-24 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference DPROC

DPROC

Equip conditions

The Data Processor (DPROC) can be equipped with the system in either the SYSGEN ON or
SYSGEN OFF mode.

The DPROC can be equipped only if the GPRS feature is unrestricted.

The DPROC can be equipped only at a GPRS PCU site. A DPROC can be equipped in the PCU
cabinet to be used as a Packet Interface Control Processor (PICP), Packet Resource Processor
(PRP) or a processor with PRP and PICP function (PXP).

At least one PRP and one PICP DPROC are required per PCU.

A PICP DPROC can support 0 to 2 LAPD GDS devices.

A PRP DPROC can support from 0 to 4 TRAU GDS devices.

There can be a maximum of 10 PRP DPROCs equipped per PCU

DPROCs are not redundant.

NOTE
A DPROC can be equipped only if the PCU is equipped.

Command prompts

Prompt Optional Range Default

Enter the DPROC ID: N 1 - 6 or None
11 - 16
Enter the DPROC type: N PICP or None
PRP or PXP

DRI (InCell sites)

Equip conditions

The Digital Radio Interface (DRI) for a InCell site can only be equipped at a BSS or a BTS site.

The DRI can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode.

If an RTF device ID is to be entered for a DRI, the RTF must be equipped before the DRI.

If a DRI is added to an existing group (same first identifier), the GSM cell ID of the new DRI
must be like the other DRIs in the group. If the Cell ID is different, the equip DRI command is
rejected.

68P02901W23-T 2-25
Jan 2010
DRI (InCell sites) Chapter 2: Equipping the CM database

DRIs/RTFs within a dual band cell with different frequency types must have different DRI/RTF
group identifiers. The equip RTF command allows two group identifiers for a cell only if the cell
is dual band. The equip cabinet command allows the secondary and primary band frequency
types in each zone to which the DRIs are equipped.

A DRI can be equipped to a Horizon II mini cabinet using antenna_select values of 1 or 2 only.
A Horizon II mini cabinet supports a maximum of two CTU2s and two cells. Thus, dependent on
whether the CTU2s are single or double density equipped, 1 to 4 DRIs are allowed. That is, 1
DRI per single density CTU2, and 2 DRI per double density CTU2.

Command prompts

Prompt Optional Range Default Comments

Enter the first N First: 0 - 5, None This identifier indicates a
and second DRI ID: Second: 0 user-defined redundancy
- 11 group within a cell. To qualify
a redundancy group, a DRI
must be connected to the
same antenna as the rest of
the group. Also, the DRI must
be using the same portion of
the TDM highway.
Enter the cabinet N 0 - 15 None If the cabinet ID does not exist
identifier: in the database the system
rejects the command.
Enter the DRI N drim or 0 None
board type:
Enter the cage N 0 - 15 None This prompt is presented only
number: if the entered board type is
DRIM.
Enter the slot N 7 - 17 None This prompt is presented only
number: if the entered board type is
DRIM.
Odd values only.
Enter the TRU Y 0 - 6 0 This prompt is presented only
identifier: if the entered board type is
DRIM.
No entry or a zero entered for
this field represents a non-Top
Cell Radio Unit (TRU).
Enter the first Y 0 - 5, None The RTF entered in this field
and second RTF ID: 0 - 11 must be equipped.
One DRI prefers the RTF.
If another DRI prefers the
RTF, the system rejects the
command.
Enter the GSM cell N GSM cell None The cell number can be in
ID where the DRI ID or either seven parameter format
appears: cell_name or four parameter format.

Continued

2-26 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference DRI (M-Cell and Horizon macro sites)

Prompt Optional Range Default Comments

Enter antenna N 1 - 6 None
select number for
this cell:
Enter COMB first Y 0 - 13, None COMB must be separately
and second ID: 0 or 1 equipped.
Enter cavity Y 0 - 5 This prompt is displayed only
number: if COMB ID is entered for the
previous prompt.
Enter the N 0 - 2 None 0 = no rx diversity
diversity flag for 1 = 2 branch rx diversity
this DRI: 2 = 4 branch rx diversity
Does this DRI use Y yes or no yes
tunable combining:
Enter the tunable Y 0, 1, or 2 0 Prompted only when DRI uses
combining type: tuneable combining.
0 = none
1 = non-controlling
2 = controlling
Enter the COMB N 0 - 13 None Prompted only when DRI uses
identifier: tuneable combining.
Enter the cavity N 0 - 5 None Prompted only when DRI uses
number for this tuneable combining.
COMB:
Enter the fm cell N 0 - 4 None 0 = non-diversity
type: 1 = 120 degree cell (not
currently supported)
2 = 60 degree cell (not
currently supported)
3 = shared diversity (not
currently supported)
4 = full diversity

DRI (M-Cell and Horizon macro sites)

Equip conditions

The Digital Radio Interface (DRI) for an M-Cell or a Horizon macro site can be equipped only at
a BSS or a BTS site.

The DRI can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode.

If an RTF device ID is to be entered for a DRI being equipped, the RTF must be equipped
before the DRI.

If a DRI is added to an existing group (same first identifier), the GSM cell ID of the new DRI must
be like the other DRIs in the group. If the Cell ID is different, the equip command is rejected.

Two DRI devices can be associated with each other (double density). Neither DRI has a higher
precedence than the other in the DRI pair.

68P02901W23-T 2-27
Jan 2010
DRI (M-Cell and Horizon macro sites) Chapter 2: Equipping the CM database

When equipping DRIs in a single Horizon II macro cabinet for a Dual Band configuration,
the system checks for the correct Dual Band cabinet setup. That is, all 900 MHz radios in
either slots 02 or 35, with the 1800 MHz radios being equipped in the other three slots. A
Horizon II macro cabinet with frequency_type supporting Dual Band can be equipped with
radios supporting a single frequency.

For enabling the four Branch Receive Diversity, the DRIs must be equipped in a single Horizon II
macro cabinet for single band configuration.

Command prompts

{34371G} (R)CTU4 DRI is only supported at the Horizon II site. At the Horizon II site, the
operator must first set the board_type. If the board_type is set to TCU, then the prompts are
displayed. If the board_type is set to RH, the prompts for (R)CTU4 are displayed as follows:

Prompt Optional Range Default Comments

{34371G} Enter the N TCU, None TCU: Old generation DRI for the
DRI board type: RH new generation site.
RH (Radio Head): New generation
DRI that works with BBU. If the
operator types RH, the prompts
set for the new generation DRI are
printed.
{34371G} Enter Y 0 - 15 None For (R)CTU4, no input required,
the cabinet directly pressing Enter indicates
identifier: that it is (R)CTU4.
(R)CTU4 does not have cabinet and
slot information as it does not reside
in any cabinet.
For CTU4, the value for cabinet
identifier indicates the radio
location.
{34371G} Enter the N 0 - 5 for Horizon None This prompt does not appear if the
slot number: II macro; cabinet identifier is skipped.
0 - 1 for
Horizon II mini;
0 for Horizon
II micro
{34371G} Enter the N BBU, None
first component to CTU4
attach:
{34371G} Enter the N 0 - 1 for BBU, None If the first component to attach is
first device ID: 0 - 5, 0 - 11 BBU, the device id value range is 0
for CTU4 to 1.
If the first component to attach is
CTU4, the device id value range is
(0 to 5, 0 to 11).
Any DRI in that (R)CTU4 can
represent the (R)CTU4.
{34371G} Enter the N 0 - 2 for BBU, None BBU has 3 SFP ports and (R)CTU4
first device port: 0 - 1 for CTU4 has 2 SFP ports.

Continued

2-28 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference DRI (M-Cell and Horizon macro sites)

Prompt Optional Range Default Comments

{34371G} Enter the N 0 - 1 None The ingress SFP port used to
first CTU4 ingress connect the first device.
SFP port:
{34371G} Enter the Y BBU None This prompt does not appear when
2nd component to either,
attach: the 1st component to attach is
CTU4,
or the D4+ link between two BBUs
is existent.
No input is required, directly
pressing Enter indicates that there
is no second component attached.
{34371G} Enter the N 0 - 1 None This prompt does not appear if the
second device ID: second component is skipped.
{34371G} Enter N 0 - 2 None This prompt does not appear if the
the second device second component is skipped.
port:
{34371G} Enter the N 0 - 1 None This prompt does not appear if the
second 2nd CTU4 second component is skipped.
ingress SFP port: The ingress SFP port is used to
connect the second device.
{34371G} Enter the N GSM cell ID or None The cell number can be in either the
GSM cell ID where cell_name seven parameter format or the four
the DRI appears: parameter format.
{34371G} Enter N PGSM: 1 - 124, None The (R)CTU4 works
the ARFCN of the EGSM: 0, 1 - at lowest_frequency ~
lowest frequency: 124, 975 - 1023, lowest_frequency + 20 MHz.
DCS1800:
512 - 885
{34371G} Enter N 1 - 3 None
antenna select
number for this
cell:
{34371G} Enter the N 0 - 4 None
fm cell type:
{34371G} Enter N 0 - 2 None (R)CTU4 does not support four
diversity flag for Branch Rx Diversity.
this DRI:
{34371G} Enter the N 0 - 5 None DRI group ID for all associated DRIs
1st DRI id of all in (R)CTU4.
associated DRIs:

Continued

68P02901W23-T 2-29
Jan 2010
DRI (M-Cell and Horizon macro sites) Chapter 2: Equipping the CM database

Prompt Optional Range Default Comments

{34371G} Enter the N 0 - 2 (3) None Supports up to two density per Tx
density of DRI on {35200G} 0 - 4 port (value range is 0 - 2).
Tx Port 0: If the MCBTSR8Opt parameter is
unrestricted, three density per Tx
port can be supported (value range
is 0 - 3).
{35200G} If CTU8Opt is
unrestricted, up to 4 density
per Tx port can be supported (value
range is 0 - 4).
{34371G} Enter N 0 - 11 None This prompt does not appear if
the second DRI tx0_dri_density =0.
id of the first
associated DRI of
Tx port 0:
{34371G} Enter the Y 0 - 5, None This prompt does not appear if
1st and second 2nd 0 - 11 tx0_dri_density =0.
RTF id: The RTF must be equipped already.
{34371G} Enter Y 0 - 11 None This prompt does not appear if
the second DRI id tx0_dri_density <2.
of the second nd
associated DRI of
Tx Port 0:
{34371G} Enter the Y 0 - 5, None This prompt does not appear if
1st and second RTF 0 - 11 tx0_dri_density <2.
id: The RTF must be equipped already.
{34371G} Enter N 0 - 11 None This prompt does not appear if
the second DRI tx0_dri_density <3.
id of the third
associated DRI of
Tx Port 0:
{34371G} Enter the Y 0 - 5, None This prompt does not appear if
first and second 0 - 11 tx0_dri_density <3.
RTF id: The RTF must be equipped already.
{35200G} Enter the N 0 - 11 None This prompt does not appear if
2nd DRI id of the tx0_dri_density <4.
4th associated DRI
of Tx Port 0:
{35200G} Enter the Y 0 - 5, None This prompt does not appear if
1st and 2nd RTF 0 - 11 tx0_dri_density <4. The RTF must
id: be equipped already.

Continued

2-30 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference DYNET

Prompt Optional Range Default Comments

{34371G} Enter the N 0 - 2 (3) None Supports up to two density per Tx
density of DRI on {35200G} 0 - 4 port (value range is 0 - 2).
Tx Port 1: If the MCBTSR8Opt parameter is
unrestricted, three density per Tx
port can be supported (value range
is 0 - 3).
{35200G} If CTU8Opt is
unrestricted, up to 4 density
per Tx port can be supported (value
range is 0 - 4).
{34371G} Enter N 0 - 11 None This prompt does not appear if
the second DRI tx1_dri_density =0.
id of the first
associated DRI of
Tx Port 1:
{34371G} Enter the Y 0 - 5, None This prompt does not appear if
1st and second 2nd 0 - 11 tx1_dri_density = 0.
RTF id: The RTF must be equipped already.
{34371G} Enter N 0 - 11 None This prompt does not appear if
the second DRI tx1_dri_density <2.
id of the second
associated DRI of
Tx Port 1:
{34371G} Enter the Y 0 - 5, None This prompt does not appear if
1st and 2nd RTF 0 - 11 tx1_dri_density <2.
id: The RTF must be equipped already.
{34371G} Enter N 0 - 11 None This prompt does not appear if
the second DRI tx1_dri_density <3.
id of the third
associated DRI 0f
Tx Port 1:
{34371G} Enter the Y 0 - 5, None This prompt does not appear if
first and second 0 - 11 tx1_dri_density <3.
RTF id: The RTF must be equipped already.
{35200G} Enter the N 0 - 11 None This prompt does not appear if
2nd DRI id of the tx1_dri_density <4.
4th associated DRI
of Tx Port 1:
{35200G} Enter the Y 0 - 5, None This prompt does not appear if
1st and 2nd RTF 0 - 11 tx1_dri_density <4. The RTF must
id: be equipped already.

DYNET

The Dynamic Network of BTSs (DYNET) shares terrestrial backing resources. The network
can include timeslot switching sites.

68P02901W23-T 2-31
Jan 2010
DYNET Chapter 2: Equipping the CM database

Equip conditions

All DYNETs that share the same first identifier must have the same BTSs or timeslot switching
sites in the same order. Also, these DYNETs must have different E1 links used by the BTSs
within the BTS network. These limitations allow definition of multiple link BTS networks for
sharing purposes, while limiting the configuration to simplify sharing.

An open loop DYNET has an automatically equipped PATH for an open loop daisy chain, with a
second identifier equal to the second identifier of the DYNET times two. A closed loop DYNET
has two PATHs automatically equipped. The identifier of the first PATH is equal to the identifier
of the DYNET multiplied by 2. The identifier of the second PATH is equal to the identifier of
the DYNET multiplied by 2 and with 1 added.

The automatically equipped PATH in closed loop daisy chains has a second identifier one greater
than second identifier of the first PATH automatically equipped.

The identifiers of the PATHs that can be automatically equipped when a DYNET is equipped are
not allowed when equipping or unequipping the PATH device.

The system does not verify whether this feature is available when a DYNET is equipped.

Command prompts

Prompt Optional Range Default Comments

Enter 1st N First identifier: 0 None If the ID exists in the
and 2nd - 19, database, the command
unique DYNET Second identifier: is rejected.
identifiers: 0-2
Enter BSC MMS N 0 - 890 or 1 None This prompt requires
identifier: two values:

First value is MSI

at the BSC where
MMS resides.

Second value is
MMS for the BSC
network definition.
Enter SITE N 0 - 140 None The TS site number,
identifier: ts_switch, BSC timeslot switching site,
or the BSC.
Enter the N For BTS4, BTS5, None This prompt requires
upstream MMS BTS6, TopCell, two values:
identifiers: and ExCell:
0 - 9, First value is MSI
0 or 1. at the BTS where
For M-Cell2: MMS resides.
0 - 1,
0 - 1. Second value is
For M-Cell6: MMS for the BTS
0 - 3, network definition.
0 - 1.

Continued

2-32 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference EAS (InCell sites)

Prompt Optional Range Default Comments

Enter the Y For BTS4, BTS5, None This prompt requires
downstream MMS BTS6, TopCell, two values:
identifiers: and ExCell:
0 - 9, The first value is
0 or 1. the MSI at the BTS
For M-Cell2: where the MMS
0 - 1, resides.
0 - 1.
For M-Cell6: The second value
0 - 3, is the MMS for
0 - 1. the BTS network
definition.
This prompt can be left
blank.

EAS (InCell sites)

Equip conditions

The External Alarm System (EAS) for sites that are InCell sites can be equipped with the system
in either SYSGEN ON or SYSGEN OFF mode.

Command prompts

Prompt Optional Range Default Comments

Enter the first N 0 - 7 None If the ID exists in the database
device ID for the the command is rejected.
EAS:
Enter the cage N 0 - 15 None
where the PIX is
connected:
Enter the daughter N 15 - 18 None
slot where the PIX
is located:
Enter the relay N 0 or 1 None Enter four values, each
wiring of the four separated by a space.
relays:

Continued

68P02901W23-T 2-33
Jan 2010
EAS (M-Cell sites) Chapter 2: Equipping the CM database

Prompt Optional Range Default Comments

Enter the no alarm N 0 or 1 None Enter eight values, each
condition for the separated by a space.
eight optos (0 -
closed, 1 - open):
Enter each opto. N 1 - 8 None Enter eight values, each
Report state separated by a space.
changes:
Enter the N 0 - 33 None Enter eight values, each
user-defined alarm separated by a space.
index for the eight Enter the string mpf in place
optos: of one of the integers to indicate
which opto is used for the EAS
Mail Power Failure alarm.
Enter each opto. Y 1 - 8 for None Operator can enter up to 8
Report state InCell values for an InCell site and up
changes: sites. to 16 values for an M-Cell site.
1 - 16 for Separate values with either a
M-Cell space or a comma.
sites. If no value is entered in the
range prompt, then no state
changes are reported for any
opto-coupler. The values can be
entered in any order.
The operator also has the option
of entering all and of entering
a range of optos.
Enter the Y 0 - 33 and None The operator must enter one
user-defined alarm 128 value indicating the index of
index for opto n: the user-defined alarm string
for the opto-coupler specified
by 'n'. The text string mpf is
interpreted as the value 128.
No default is accepted for
this prompt. A prompt is
displayed for each reporting
opto-coupler specified in the
previous prompt.

EAS (M-Cell sites)

Equip conditions

The External Alarm System (EAS) for M-Cell sites can be equipped with the system in either
SYSGEN ON or SYSGEN OFF mode. When equipping the EAS, the physical wiring of each relay
must be specified. Whether the relay is open or closed when deactivated must also be specified.
All relays are deactivated during site initialization. Once the EAS is Busy-Unlocked, the relay
state is controlled by using the set_relay_contact command. Only opto reporting for alarms 1
to 12 can be enabled or disabled for a Horizon II mini cabinet type.

2-34 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference GBL

Command prompts

Prompt Optional Range Default Comments

Enter the first N 0 - 15 None Cabinet identifier.
device ID (Cabinet
ID) for the EAS:
Enter the relay N 0 or 1 None 0 = deactivate the relay
wiring of the 4 1 = activate the relay
relays: Enter four values, each
separated by a space.
Enter the no alarm N 0 or 1 None Enter 16 values, each separated
condition for by a space.
the 16 optos (0 - Only 12 optos are available for
closed, 1 - open): Horizon II mini.
Enter each opto N 1 - 16 None Enter 16 values, each separated
Report state by a space. Only 12 optos are
changes: available for Horizon II mini.
Enter the N 0 - 33 None Enter 16 values, each separated
user-defined alarm by a space.
index for the 16 Enter the string mpf in place of
optos: one of the integers to indicate
which opto is used for the EAS
Mail Power Failure alarm.
Only 12 optos are available for
Horizon II mini.

GBL

The Gb Link (GBL) is the communication link between the PCU cabinet and the SGSN.

Equip conditions

This device can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode.

The GBL can be equipped only if the GPRS feature is unrestricted.

To support EGPRS the GBL bandwidth between the PCU and the SGSN has been increased.
The amount of bandwidth necessary for a maximal configured PCU is 12 E1s of GBL, and
for a maximal configured BSS is 20 E1s. This maximum number of GBLs can be configured
independent of whether EGPRS is restricted or not.

68P02901W23-T 2-35
Jan 2010
GBL Chapter 2: Equipping the CM database

Command prompts

Prompt Optional Range Default Comments

Enter the GBL N 0 - 35 None Unique identifier of the GBL.
identifier:
Enter the 1st and N 0 - 23, None A GBL must be equipped on a
2nd MMS identifier: 0 - 1 DPROC PICP MSI at a PCU.
A GBL must not be equipped to
an MMS on the last PICP MSI
which is designated for code
download, when a default GSL
has not already been equipped.
Enter the starting N 1 - 31 None Element name start_ts. First
timeslot: GBL timeslot on the span.
Enter the ending N 1 - 31 None Element name end_ts. Last
timeslot: GBL timeslot on the span.
Enter the t391 Y 5 - 29 10 Element name t391. Value of
timer: the Frame Relay default Link
Integrity Verification Polling
Timer in seconds.
Enter the t392 Y 6 - 30 15 Element name t392. Value of
timer: the Frame Relay default Polling
Verification Timer in seconds.
Enter the n391 Y 1 - 255 6 Element name n391. Frame
counter: Relay default Full Status Polling
Counter, as number of polling
cycles.
Enter the n392 Y 1 - 10 3 Element name n392. Frame
counter: Relay default value for Error
Threshold Counter, as number
of errors.
Enter the n393 Y 1 - 10 6 Element name n393. Frame
counter: Relay default value for
Monitored Events Counter,
as number of events.

NOTE
The Frame Relay Access Rate ns_access_rate (in kbit/s) is not prompted for as it is
calculated from ((end_ts + 1) - start_ts) * 64, then defaulted to this value.

2-36 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference GCLK

GCLK

Equip conditions

The Generic Clock (GCLK) can be equipped with the system in either the SYSGEN ON or
SYSGEN OFF mode.

The GCLK cannot be explicitly equipped at M-Cell sites. This device is automatically equipped
when a BTP is equipped.

Some devices do not require all the prompts. Therefore, the system cannot always display
all the prompts provided in the next section.

Command prompts

Prompt Optional Range Default Comments

Enter the device N 0 or 1 None The GCLK slot is assigned based
identification for on the device ID:
the GCLK: If the device ID is set to 0, the
GCLK is assigned to slot 5.
If the device ID is set to 1, the
GCLK is assigned to slot 3.
Enter the cage N 0 - 15 None
number:
Is CLKX 0 (slot U7) Y yes or no no The slot number displayed in the
present? prompt depends on the GCLK
ID.
The alternate slot number for
GLKX 0 is U4. (See also NOTE.)
Is CLKX 1 (slot U6) Y yes or no no The slot number displayed in the
present? prompt depends on the GCLK
ID.
The alternate slot number for
GLKX 1 is U3. (See also NOTE.)
Is CLKX 2 (slot U5) Y yes or no no The slot number displayed in the
present? prompt depends on the GCLK
ID.
The alternate slot number for
GLKX 2 is U2. (See also NOTE.)

NOTE
Slots U2 through U7 can contain CLKX cards or KSWX cards. The system checks
the contents of these slots any time a change implies the existence of a new CLKX,
EXP KSWX, or remote KSWX card. The system rejects the change if the new card
occupies a slot that is already occupied.

68P02901W23-T 2-37
Jan 2010
GDS Chapter 2: Equipping the CM database

GDS

Equip conditions

This device can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode.
The GPRS Data Stream (GDS) can be equipped only if the GPRS feature is unrestricted. A GDS
must not be unequipped until all GSLs on that GDS have been unequipped.

NOTE
Locking the GDS causes the GSLs to go OOS. This differs from pre-GSR10 behavior
where there was no hierarchal relationship between the GDS and the GSL.

The BSS rejects an attempt to equip a GDS to an MMS at the BSC where the mms_priority of
the MMS is a non-zero value.

The GDS device allows a maximum of 72 E1 links to be configured as TRAU GDS per BSS. The
device also allows a maximum of 36 E1 links to be configured as TRAU GDS per PCU. The
maximum number of TRAU GDSs that can be configured is independent of whether EGPRS is
restricted or not. The number of LAPD GDS devices is two per PCU and six per BSS.

Command prompts

Prompt Optional Range Default Notes

Enter the GDS N 0 - 37 None Unique identifier of the GDS.
identifier:
Enter the GDS N E1 or None
connectivity: ETHERNET
When GDS connectivity is equal to ETHERNET, the following will be prompted:
Enter the BSC ETH N 0 - 11 None
identifier: 0 - 0
Enter the PCU ETH N 0 - 16 None
identifier: 0 - 0
When GDS connectivity is equal to E1, the following will be prompted:
Enter the BSC MMS N 0 - 95, None
identifier: 0 - 1
Enter the PCU MMS N 0 - 23, None
identifier: 0 - 1
Enter the GDS type: N TRAU or None
LAPD

NOTE
BSC MMSs which are equipped to GDS devices cannot be selected as clock sources.

2-38 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference GPROC

GPROC

Equip conditions

The Generic Processor (GPROC) can be equipped with the system in either the SYSGEN ON or
SYSGEN OFF mode.

This device cannot be equipped at M-Cell sites.

Command prompts

Prompt Optional Range Default Comments

Enter the GPROC N 1 - 111 None
identifier:
Enter the cage N See None Valid cage numbers are
number: Comments dependent on the site:
BSS sites: cages 0 to 13.
BSC sites: cages 0 to 13.
BTS sites: cages 2 to 15.
RXCDR sites: cages 0 to 13.
Enter the slot N See None Valid slot numbers are
number: Comments dependent on the site:
BSC, BSS, and BTS sites:
slots 18 to 25.
RXCDR sites: slots 25 to 26.

GSL

Equip conditions

The GPRS Signaling Link (GSL) can be equipped only if the GPRS feature is unrestricted.

The GSL can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode.

The equipage of a GSL is allowed only if the remaining GDS timeslot resources available to the
PCU are sufficient to support the GPRS timeslot resources for cells for which GPRS is enabled.

The GSL is allowed only on an LAPD GDS.

30 GSLs can be equipped to a LAPD GDS. All 60 could be equipped to one DPROC that has two
GDSs equipped on it. However, for redundancy, two DPROCs are required each with a LAPD
GDS equipped with 30 GSLs.

To bring the GSL in service, unlock the GSL at either the OMC-R or MMI prompt.

68P02901W23-T 2-39
Jan 2010
KSW Chapter 2: Equipping the CM database

NOTE
The equip GSL command fails if the total max_gsls for all LCFs becomes less than
the total number of equipped GSLs.

Command prompts

Prompt Optional Range Default Notes

Enter the GSL N 0 - 59 None
identifier:
Enter the unique N 0 - 37 None
GDS identifier:

KSW

Equip conditions

The Kiloport Switch (KSW) can be equipped with the system in either the SYSGEN ON or
SYSGEN OFF mode.

The KSW cannot be equipped at M-Cell sites.

Command prompts

Prompt Optional Range Default Comments

Enter Portion of N 0 - 3 None The first device ID for the KSW

TDM Highway Managed must match the KSW pair in the
(identifier 1): cage where the KSW is being
equipped.
Enter TDM N 0 or 1 None The KSW slot is assigned based
identifier on the second device ID;
(identifier 2): If the second device ID is set to
0, the KSW is assigned to slot
27.
If the second device ID is set to
1, the KSW is assigned to slot 1.
Enter the cage N 0 - 15 None
number:
Are DRIs allowed on N Y or N None This prompt does not occur at
highway managed by a BSC.
this KSW:

2-40 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference LMTL

LMTL

The Location Message Transfer Link (LMTL) device applies only to the BSC (location 0).

Equip conditions

The Location Services feature must be unrestricted.

For LMTLs to be equipped, the BSC must be configured to support a BSS-based SMLC.

When an LMTL is equipped on an MMS that hosts other non-Lb-interface links, a warning
message displays indicating a conflict in MMS timeslot usage.

Command prompts

Prompt Optional Range Default Comments

Enter the device N 0 - 15 None Location Services must be
identification for unrestricted.
this LMTL:
Enter the first MMS N 0 or 95 None
identifier for this
device:
Enter the second MMS N 0 - 1 None
identifier for this
device:
Enter the timeslot N 31 (E1) None
on MMS where this
device appears:

MSI (InCell, BSC, and RXCDR sites)

Equip conditions

The Multiport Serial Interface (MSI) for InCell, BSC, or RXCDR sites can be equipped with the
system in either the SYSGEN ON or SYSGEN OFF mode.

An MSI with msi_type of msi_ext_hdsl cannot be equipped with the protocol types of both
MMSs entered as E1 at a BSC or an InCell BTS site.

68P02901W23-T 2-41
Jan 2010
MSI (InCell, BSC, and RXCDR sites) Chapter 2: Equipping the CM database

Command prompts

Prompt Optional Range Default Comments

Enter the device N BSC: 0 - 95 None
identification for RXCDR: 0 -
the MSI: 123
BTS: 0 - 9
(InCell)
Enter the cage N 0 - 15 None
number:
Enter the slot N BSS and None Valid slot numbers are based
number: BSC sites: on site type and MSI type.
All MSI type
slots 6 - 17.
BTS sites:
MSI type 0
slots 6 - 17,
MSI type
1 or 2 not
allowed.
RXCDR
sites
MSI type 0
slots 6 - 10,
MSI type 1
or 2 slots
6-24
Enter the MSI type: N 0 or msi, None The input can be the numeric
1 or xcdr, value or the text string. (The
2 or gdp, value of 5 is reserved.)
7 or MSI types xcdr or gdp are
msi_ext_hdsl, only allowed at sites where
12 or transcoding occurs.
RF_unit,
20 or gdp2.
Enter MMS0 protocol Y E1 or HDSL HDSL Prompt appears only if the
type: Integrated MCell HDSL
feature is enabled, and
the msi_type is niu_hdsl,
niu_ext_hdsl, or msi_ext_hdsl.
Enter the number Y 16 or 32 32 Prompt appears only if the
of time slots Integrated MCell HDSL
supported on MMS0: feature is enabled, and
the MSI type is niu_hdsl,
niu_ext_hdsl, or msi_ext_hdsl,
and the protocol type is
HDSL.

Continued

2-42 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference MSI (InCell, BSC, and RXCDR sites)

Prompt Optional Range Default Comments

Enter MMS0 modem Y master or None Prompt appears only if the
setting: slave Integrated MCell HDSL
feature is enabled, the
protocol is HDSL, and the
MSI type is niu_hdsl.
Enter MMS1 protocol Y E1 or HDSL HDSL Prompt appears only if the
type: Integrated MCell HDSL
feature is enabled, and
the MSI type is niu_hdsl,
niu_ext_hdsl, or msi_ext_hdsl.
Enter the number Y 16 or 32 32 Prompt appears only if the
of time slots Integrated MCell HDSL
supported on MMS1: feature is enabled, and the
msi_type is msi_ext_hdsl, with
a protocol type of HDSL for
this MMS.
Enter MMS1 modem Y master or None Prompt appears only if the
setting: slave Integrated MCell HDSL
feature is enabled, the
protocol is HDSL, and the
msi_type is niu_hdsl.
Enter the MSI ID to Y BSC: 0 - 95 Value MSI identifier of GDP with
the MSC: RXCDR: 0 - of GDPs MMS available for routing
123 own the transcoding circuits of a
MSDI ID secondary GDP towards the
MSC. Read-Write (can be set
only when the MSI device is
created).
0 Value MSC MMS always zero
of GDPs because MSIs cannot provide
own MSC MMSs. Read-Write (can
second ID only be set when the MSI
device is created).
Prompt appears only if MSI
type entered as 2 or gdp.
Enter the N 0 or Basic, None Prompt appears only if MSI
transcoding 1 or type entered as 2 or gdp, or
capability: Enhanced, as 20 or gdp2.
2 or
GDP_2E1.

NOTE
The default values in the table apply only if nothing is entered at the prompts.

68P02901W23-T 2-43
Jan 2010
MSI (M-Cell sites) Chapter 2: Equipping the CM database

MSI (M-Cell sites)

Equip conditions

The Multiport Serial Interface (MSI) for M-Cell sites can be equipped with the system in either
the SYSGEN ON or SYSGEN OFF mode.

M-Cell sites do not use MSI boards. The Network Interface Unit (NIU) performs the MSI
function in an M-Cell2 or M-Cell6 cabinet. That is why the system prompts refer to the NIU.
The msi_type of niu_hdsl is only supported at M-Cellcity, Horizon micro or Horizon
compact sites.

The msi_type of niu_ext_hdsl is supported at M-Cell2, M-Cell6, M-Cellcity, M-Cellmicro,

Horizon micro, and Horizon compact sites.

A warning is issued if the protocol types of both MMSs of an MSI, with an msi_type of
niu_hdsl at an M-Cellcity, M-Cellmicro, Horizon micro, or Horizon compact site, are
entered as E1.

An MSI with msi_type of niu_ext_hdsl cannot be equipped with the protocol types of
both MMSs entered as E1 at an M-Cell2, M-Cell6, M-Cellmicro, M-Cellcity, Horizon micro
or Horizon compact site.

The msi_type niu_ext_hdsl can be equipped in slot 1 of a card frame (at an M-Cell6 site)
only if the protocol type of MMS0 is entered as HDSL.

When equipping an HDSL NIU, the new hdsl_oos_mon_period and hdsl_re-

store_mon_period durations default to known software values.

NOTE
The default values in the following table apply only if nothing is entered at the
prompts.

Command prompts

Prompt Optional Range Default Comments

Enter the device
identification for
the MSI:
Enter the MCU card
frame in which the
NIU exits:
Enter the NIU slot
number:
N See None M-Cell 2 BTS: 0 or 1
comments M-Cell 6 BTS: 0 to 3
M-Cellmicro: 0
N 0 or 1 (See None 0 is the only valid value for
comments) this field if equipping to
M-Cellmicro.
N 0 or 1 (See None 0 is the only valid value for
comments) this field if equipping to
M-Cellmicro and M-Cell2.

Continued

2-44 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference MSI (PCU only)

Prompt Optional Range Default Comments

Enter the MSI type: N 3 or niu, niu The input can be either the
8 or numeric value or the text
niu_hdsl, string.
9 or
niu_ext_hdsl
Enter the MMS0 Y E1 or HDSL HDSL If the Integrated M-Cell
protocol type: HDSL feature is enabled,
and the msi_type is niu_hdsl
or niu_ext_hdsl, the prompt
appears.
Enter the number Y 16 or 32 32 If the Integrated M-Cell
of time slots HDSL feature is enabled, and
supported on MMS0: the msi_type is niu_hdsl or
niu_ext_hdsl, with a protocol
type of HDSL for this MMS,
the prompt appears.
Enter MMS0 modem Y master or master If the Integrated M-Cell
setting: slave HDSL feature is enabled,
and the msi_type is niu_hdsl
with a protocol type of HDSL
for this MMS, the prompt
appears
Enter the MMS1 Y E1 or HDSL HDSL If the Integrated M-Cell
protocol type: HDSL feature is enabled,
and the msi_type is niu_hdsl,
or niu_ext_hdsl, the prompt
appears.
Enter the number Y 16 or 32 32 If the Integrated M-Cell
of time slots HDSL feature is enabled, and
supported on MMS1: the msi_type is niu_hdsl or
niu_ext_hdsl with a protocol
type of HDSL for this MMS,
the prompt appears.
Enter MMS1 modem Y master or slave If the Integrated M-Cell
setting: slave HDSL feature is enabled,
and the msi_type is niu_hdsl
with a protocol type of HDSL
for this MMS, the prompt
appears.

MSI (PCU only)

Equip conditions

The Multiport Serial Interface (MSI) for PCU sites can be equipped with the system in SYSGEN
ON mode.

This device can also be equipped when the system is outside the SYSGEN ON mode. The site
must not be locked when this device is equipped outside SYSGEN ON mode.

68P02901W23-T 2-45
Jan 2010
MSI (PCU only) Chapter 2: Equipping the CM database

A modified MSI device is used to describe the serial interface device which can be equipped
to DPROC boards. It is a child class of PCU.

The GPRS MSI type is not available when the GPRS feature is restricted.

The BSS supports equipage of a GBL to a PICP MMS.

The BSS supports equipage of a GDS at the PCU.

The BSS supports equipage of a GDS to an HDSL MSI when the child MMS of the MSI is of
type E1.

The BSS does not support the modification of the msi_type for an MSI.

The BSS supports equipage of up to two MSIs per DPROC board.

A DPROC board must be equipped before an MSI can be equipped to the same DPROC.

The PCU supports a unique identifier for each MSI equipped within the PCU.

Two MMS devices are automatically equipped with each PCU MSI equip.

All MMSs on the same MSI must be configured for the same destination: BSC or SGSN.

If only one MSI is available, then the MSI must be equipped in PMC socket 1 of a DPROC in
either slot 1 or slot 2.

Command prompts

Prompt Optional Range Default Comments

Enter the MSI N 0 - 23 None The MSI identifier.
identifier:
Enter the DPROC ID: N 1 or 6 None The identifier of the DPROC in
11 - 16 the PCU cabinet on which the
MSI resides.
Only appears if the MMS ID to
the MSC was not entered, or
was the same as the MSI device
identifier of the device being
equipped.
Enter the DPROC N 1 or 2 None PMC module identifier on the
socket: DPROC board to which the MSI
is being equipped.

2-46 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference MTL

MTL

Equip conditions

The Message Transfer Links (MTL) is not allowed at an RXCDR site and can be equipped only
at site 0.

The MTL cannot be equipped on an HDSL link.

The MTL can be equipped only at the BSC.

Command prompts

Prompt Optional Range Default

Enter the device identification for this N 0 - 15 None
MTL:
Enter the number of DSO channels for this N* 1: 64 1
MTL: kbps MTL
31: HSP
MTL
Other
values
reserved
Enter the first MMS description for this N 0 - 123 None
device:
Enter the second MMS description for this N 0 or 1 None
device:
Enter timeslot on MMS where this device N** 1 - 31 (E1) None
appears:

NOTE

* Only when the increased network capacity feature is unrestricted, this value
can be set to 31. If the user attempts to equip 64 kbps MTLs after the mtl_rate
of existing MTL has already been set to 31, the equip command is rejected. If
the user attempts to equip an HSP MTL while the mtl_rate has already been set
to 1, the equip command is rejected.
** If the mtl_rate is 31, this value must be 1.

If an MMS has another timeslot that conflicts when equipping an MTL, the system generates
the following warning:

COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to

verify.

Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another is
connected to a different type of device. That is, RXCDR, OML, and so on.

68P02901W23-T 2-47
Jan 2010
OML Chapter 2: Equipping the CM database

OML

Equip conditions

The Operations and Maintenance Link (OML) cannot be equipped on an HDSL link.

The OML can be equipped only at site 0.

Command prompts

Prompt Optional Range Default

Enter the device ID for the OML: N 0 - 3 None
Enter the first MMS description for this N BSC: 0 - 95 None
device: RXCDR:
0 - 123
Enter the second MMS description for this N 0 or 1 None
device:
Enter timeslot on MMS where this device N E1: 1 - 31 None
appears:

If an MMS has another timeslot that conflicts when equipping an OML, the system generates
the following warning:COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display
timeslot usage to verify.

Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another is
connected to a different type of device. That is, RXCDR, OML, and so on.

OPL

Equip conditions

The Optimization Link (OPL) is used to carry measurement report data out of the BSC. The link
is a dedicated 64 kbit/s link HDLC link between the BSC and the IOS platform equipped to a
E1 timeslot on an existing MMS.

To equip the OPL follow the given steps:

1. Select the least utilized LCF on BSC.

2. Modify the selected LCF to support OPL using the command

modify_value bsc

max_opls one lcf <id1> <id2> <id3>

3. Equip OPL on the desired timeslot.

NOTE
OPL cannot be equipped on the LCF controlling a CBL.

2-48 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference PATH

Command prompts

Prompt Optional Range Default

Enter the device ID N 0 - 3 None
for the OPL
Enter the first MMS N BSC: 0 - 95 None
identifier for this RXCDR: 0 - 123
device
Enter the second N 0 or 1 None
MMS identifier for
this device
Enter the timeslot N E1: 1 - 31 None
on MMS where this
device appears

PATH

Equip conditions

The Path (PATH) can be equipped when the system is in either the SYSGEN ON or SYSGEN
OFF mode.

Prompts to equip a path are presented for each link in the path.

If one of the MSIs is msi_type RF_Unit, the system rejects the equip path command.

A path for an HDSL link must have the same number of time slots, identical link protocol types,
and HDSL modems that are in a master/slave configuration. The single exception to this rule
is when the system cannot check master/slave settings because the HDSL link consists of
two external modems.

Command prompts

Prompt Optional Range Default Comments

Enter terminating N 0 - 140 None
SITE ID:
Enter the Unique N See Comments None The availability of a PATH
PATH identifier: identifier depends on
whether the terminating
site uses dynamic
allocation:
- no dynamic allocation: 0
to 9.
- dynamic allocation: 6 to
9.

Continued

68P02901W23-T 2-49
Jan 2010
PATH Chapter 2: Equipping the CM database

Prompt Optional Range Default Comments

Enter the BSC MMS N 0 - 95 (MSI), None Type two values,
identifier: 0 or 1 (MMS) separated by a space;
the first value is the MSI
ID; the second value is the
MMS ID.
Enter SITE N 0 - 140, or None If the Aggregate Abis
identifier: ts_switch feature is enabled the
(See comments) system accepts ts_switch
as the site ID.
If ts_switch is used,
the system does not
prompt for upstream
MSI, upstream MMS,
downstream MSI, and
downstream MMS
identifiers.
Enter the upstream N BSC: 0 - 95, None The upstream MMS
MMS identifier: BTS: identifier cannot
0 (Horizon correspond to an RF_Unit
II macro, MSI.
Horizon II mini, MMS ID 2 is 0 - 1.
0 - 9 (In-Cell,
Horizon macro),
0 - 3 (M-Cell6),
0 - 1 (M-Cell2).

The following sequence of prompts repeats until the specified site identifier matches the
terminating site (maximum of nine sequences):

Prompt Optional Range Default Comments

Enter the N BSC: 0 - 95, None
downstream MMS BTS:
identifier: 0 - 9 (InCell),
0 - 3 (M-Cell6),
0 - 1 (M-Cell2).
Enter the SITE N 0 - 140, or None If the Aggregate Abis
identifier: ts_switch feature is enabled the
(See comments) system accepts ts_switch
as the site ID.
If ts_switch is used,
the system does not
prompt for upstream
MSI, upstream MMS,
downstream MSI, and
downstream MMS
identifiers.

Continued

2-50 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference PCU

Prompt Optional Range Default Comments

Enter the upstream N BSC: 0 - 95, None The range for the MMS ID
MMS identifier: BTS: 2 is 0 - 1.
0 - 9 (InCell),
0 - 3 (M-Cell6),
0 - 1 (M-Cell2).

If an MMS has another timeslot that conflicts when equipping a PATH, the system generates
the following warning:

COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to

verify.

Conflicting usage is when at least one timeslot provides connectivity to a BTS and another
type of device (such as, an RXCDR).

NOTE
The upstream MMS ID cannot correspond to an RF_Unit MSI.

PCU

Equip conditions

The Packet Control Unit (PCU) can be equipped with the system in SYSGEN ON mode.

With the enhanced PCU (ePCU) in GSR10, 3xPCU configuration is not required to achieve the
target GPRS capacity. That is, supporting 3240 PDTCH (810 active, 2430 standby). 3xPCU
configuration is disabled in GSR10.

When a PCU is equipped, a corresponding CAB device and CAGE device are automatically
equipped.

A PCU can be equipped only if the parameter land_layer1_mode is set to E1

Command prompts

Prompt Default
Enter the PCU Identifier: 0
Enter the PCU base GDS IP Address: 127.0.0.1
Enter the PCU GDS Subnet Mask: 255.255.0.0
Enter the WEBMMI IP Address: 127.0.0.1
Enter the WEBMMI Subnet Mask: 255.255.0.0
Enter the WEBMMI Router IP Address: 127.0.0.1
ENTER the NSEI value: 10
Enter the PRP Fanout Mode: 1

68P02901W23-T 2-51
Jan 2010
PSI Chapter 2: Equipping the CM database

PSI

Equip conditions

The PSI (Packet Subrate Interface) is designed to be a generic interface to an external packet
network through the Ethernet. The primary function of the PSI card is to terminate GPRS TRAU
and transfer the TRAU payload to the PCU over Ethernet.

The PSI device is equipped inside or outside SYSGEN mode.

The PSI device is equipped only at a BSS or BSC sites.

The BSC supports a maximum of 4 PSIs per cage.

Command prompts

Prompt Optional Range Default Comments

Enter the PSI
Identifier:
Enter the cage number
Identifier:
Enter the slot number:
Enter the number of TDM
timeslot blocks:
Enter the maximum number
of GSLs on this PSI:
Enter the base IP
address for the PSI:
Enter the subnet mask:
Enter the router IP
address:
N 0 - 11 None
N 0 - 13 None
N 6 - 13 None Valid slot number is 6, 7,
12 and 13.
Y 2 - 10 2
Y 0 - 30 0
N 1.0.0.1 - None The base IP address is
223.255.255 used for the MCU.
.237 17 contiguous addresses
are available after the
base address for the
DSPs.
The IP address is entered
in dotted quad notation.
Y 128.0.0.0 - 255.255.
255.255.255.0 255.0
Y 0.0.0.0 - 0.0.0.0 The IP address of the
255.255.255 router.
.254 The value of 0.0.0.0
means that no router is
in use.

2-52 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference PSP

PSP

Equip conditions

The PCU System Processors (PSPs) are equipped only when the GPRS feature is unrestricted.

The PSPs can only be fitted at a PCU. Two PSPs can be installed in each PCU.

The PSPs must be physically installed before code download can start to the PCU.

The site must not be locked when this device is equipped outside the SYSGEN ON mode.

The PSPs are auto-equipped.

The system uses a default value for the PSP slot; therefore, the operator is not prompted.

RSL

Equip conditions

The location for the Radio System Link (RSL) must be the BSC (site 0).

Only one RSL can be equipped to an NIU in slot 1 of an M-Cell terminating site.

Only four RSL devices can be enabled per E1 span. Previously, the number of RSL devices
supported on an NIU and an E1 span were the same.

Command prompts

Prompt Optional Range Default Comments

Enter the 1st device ID N 0 - 140 None
for the RSL:
Enter the 2nd device ID N 0 - 7 None The range depends on
for the RSL: See the site type:
Comments InCell: 0 - 7.
M-Cell 2/6 BTS: 0 - 5.
Enter the Unique PATH N 0 - 9 None
ID:
Enter LAPD T200 Timer Y 1400 - 5000 2500 Values must be in
value: multiples of 50.
Enter LAPD N200 value: Y 1 - 5 3
Enter LAPD K value: Y 1 - 10 7

NOTE
The equip RSL command automatically equips an additional 16 K RSL when a 16
K RSL is equipped to an auto-equipped PATH that is part of a closed loop DYNET.
The equip command does not allow an RSL to be equipped to a PATH that is not
automatically created at a site that supports dynamic allocation.

68P02901W23-T 2-53
Jan 2010
RXCDR Chapter 2: Equipping the CM database

RXCDR

Equip conditions

The Remote Transcoder (RXCDR) must be the first device equipped by the operator in the
SYSGEN ON mode at an RXCDR site.

If an RXCDR device is equipped at a BSS site, it is actually an Associate RXCDR (AXCDR)

device (see AXCDR on page 2-13).

Command prompts

Prompt Optional Range Default Comments

Enter the RXCDR ID: N 1 - 254 None

SITE

Equip conditions

A BTS Site (SITE) can be equipped with the system in SYSGEN ON mode or the SYSGEN OFF
mode.

The system rejects the equip site command if the new site exceeds the site capacity of the
LCF. The LCF site capacity equals gproc_slots minus 1 (for the test channel).

Command prompts

Prompt Optional Range Default Comments

Enter the device
identifier for the
site:
Enter the type of BSP
or LCF:
Enter the function
identifier for the
LCF:
Enter the RSL type:
N 0 - 140 None 0 is the only valid value for
an RXCDR site type.
N BSP or None
LCF
N 0 or 1 None
(BSP).
0 - 24
(LCF).
N 16 or 64 None The system displays this
prompt only if the site is
remote and the 16 K RSL
option is enabled.

Continued

2-54 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference XBL

Prompt Optional Range Default Comments

Does the site use N Y or N None This prompt only appears if:
dynamic allocation of
terrestrial backing The Dynamic
resources?: Allocation feature
is unrestricted.

The site being

equipped is a BTS.

XBL

Equip conditions

The RXCDR to BSC Fault Management Link (XBL) cannot be equipped on an HDSL link.

The maximum number of XBLs that can be equipped at a BSC or an RXCDR site is 20.

Command prompts

Prompt Optional Range Default Comments

Enter the ABSS device
ID for the XBL:
Enter the AXCDR device
ID for the XBL:
Enter the second device
ID for the XBL:
Enter the data rate for
the XBL (16/64 kbit/s):
N 1 - 254 None This prompt is displayed
only at an RXCDR site.
This value is valid for XBLs
equipped at an RXCDR.
This value specifies the
ABSS device with which
this XBL communicates and
represents the first device
ID for the XBL.
N 1 - 254 None This prompt is only displayed
at a BSC site.
This value is valid for XBLs
equipped at a BSS.
This value specifies the
RXCDR device with which
the XBL communicates and
represents the first device
ID for the XBL.
N 0 - 9 None The is the value for the XBL
device.
Y 16 or 64 Prompted only if the 16
kbit/s option is unrestricted.

Continued

68P02901W23-T 2-55
Jan 2010
XBL Chapter 2: Equipping the CM database

Prompt Optional Range Default Comments

Enter the first MMS N BSC: None This prompt appears only if
description for this 0 - 95. the XBL data rate is set to
device: RXCDR: 16.
0 - 123.
Enter the second MMS N 0 or 1 None
description for this
device:
Enter the timeslot on N E1: None
MMS where this device 1 - 31.
appears:
Enter the group of the Y 0 - 3 Prompted only if the 16
timeslot where this kbit/s option is unrestricted
device appears: and the XBL data rate is set
to 16 kbit/s.
Enter LAPD T200 time Y 1400 - 2500 Values must be in multiples
value for the device: 5000 of 50.
Enter LAPD N200 value: Y 1 - 5 3
Enter LAPD K value: Y 1 - 127 7

If an MMS has another timeslot that conflicts when equipping an XBL, the system generates
the following warning:

COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to

verify.

Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another is
connected to a different type of device. That is, RXCDR, OML, and so on.

2-56 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Information for equipping functions

Information for equipping functions

This section provides conditional information for the rules on equipping the following functions,
and lists equip command prompts that occur with each function:

LCF on page 2-57 OMF on page 2-58 RTF on page 2-58

LCF

Equip conditions

The Link Control Function (LCF) can only be equipped at BSC site types where the BSC type is
not zero.

At least, one LCF must have a max_mtls value greater than zero.

The sum of all GSLs (GPRS) specified by the equipped LCFs must be greater than or equal to
the total number of equipped GSLs.

Command prompts

Prompt Optional Range Default Comments

Enter the function N 0 - 24 None
identifier for the LCF:
Enter the number of DSO N 0, 1, 2, None
channels the LCF can 31*
manage as MTLs:
Enter the number of Y** 0 - 2 None
LMTLs the LCF can
manage:
Enter the number of CBLs Y** 0 - 1 None
the LCF can manage:
Enter the number of GSLs Y** 0 - 12 None Prompted only when
the LCF can manage: the GPRS feature is
unrestricted.

NOTE

*: For processing 64 k MTL, the valid value is 0, 1 or 2 for all types of GPROC. For
HSP MTL, the valid value is 31. In GSR10, values between 3 and 30 are invalid.
** These prompts are displayed when MTL DS0 channels handled by the LCF
is set to 0, 1 or 2.
An LCF cannot simultaneously manage both MTLs and LMTLs.

68P02901W23-T 2-57
Jan 2010
OMF Chapter 2: Equipping the CM database

OMF

Equip conditions

The Operation and Maintenance Function (OMF) can only be equipped at BSC or BSS site
types where the BSC type is set to 2.

This function can be equipped with the system in SYSGEN ON mode or outside the SYSGEN ON
mode. The site must not be locked when this function is equipped outside SYSGEN ON mode.

Command prompts

No parameter prompts are displayed when equipping the Operations and Maintenance Facility
(OMF).

RTF

Equip conditions

The Radio Transceiver Function (RTF) can be equipped with the system in either SYSGEN
ON or SYSGEN OFF mode.

When equipping the RTF, the system enforces the following dependencies:
An RTF cannot be equipped in SYSGEN OFF mode if:
All the RTF time slots are non-hopping (255); and other non-hopping RTFs or enabled
frequency hopping systems in the cell are already using the maximum number of
frequencies.

The RTF hops through one or more time slots which cause frequency collisions.

A frequency collision occurs when two enabled FHIs hop through the same ARFCN
and one RTF uses one FHI in the same timeslot and another RTF uses the other FHI.

If the site is not in a DYNET, an RTF cannot be equipped to a site using dynamic allocation.

Due to the restrictions imposed by the BSS, Base Band Hopping (BBH) is not supported
on 64 kbit/s RTF, of which carrier A is EGPRS capable, when it is equipped on a double
density CTU2.
When an attempt is made to equip a new RTF in and out of Sysgen mode, and the requested
PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request. It also
issues a warning to indicate that there is not enough GDS or PMC resource available.

If one or more PCS1900 frequency blocks are available to the BSS and an ARFCN is entered
which is one of the block edges, the max_tx_bts for the cell assigned to this RTF cannot be less
than or equal to 3 (which corresponds to greater than 36 dBm).

2-58 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference RTF

The channel numbers at the block edges are:

512 610 687 735

585 612 710 737
587 685 712 810

These channel numbers do not apply if:

The frequency at the assigned cell does not include PCS1900.

The available frequency blocks for the BSS are contiguous (such as A and D) and the
ARFCN is on the adjacent border of the selected blocks.

The Concentric Cells feature is enabled, the power-based use algorithm is used, and the
block edge frequency is defined to be an inner zone carrier with a maximum transmit
power level (tx_pwr_red) less than 36 dBm.

When the Dual Band Cells option is enabled, the frequency type is managed on a zone basis.
Primary band carriers are configured in the outer zone and secondary band carriers are
configured in the inner zone.

DRIs/RTFs within a dual band cell with different frequency types must have different DRI/RTF
group identifiers. The equip RTF command allows two group identifiers for a cell only if the cell
is dual band. The equip cabinet command allows the secondary and primary band frequency
types in each zone to which the DRIs are equipped. The frequency type of the secondary band
defines the valid range for the ARFCN of an RTF configured for the inner zone.

equip RTF for the secondary band in a dual band cell does not prompt for TRX power reduction.

For a dual band cell, an attempt to equip RTF for a BCCH RTF in the inner zone is rejected.

When equipping an RTF to a dual band cell, the specified FHIs can contain only the frequencies
in the band of the RTF.

The pkt_radio_type parameter specifies the terrestrial resource capability of an RTF. The
mutually exclusive options are 16 kbit/s, 32 kbit/s, 64 kbit/s, and none. An EGPRS-capable
RTF can carry EGPRS PDTCHs and can allocate 64 kbit/s terrestrial channels to support the
EGPRS coding schemes on the air time slots. For a complete description of this parameter,
refer to pkt_radio_type on page 8-85.

Warning messages

The following warning message displays when an attempt is made to equip a new RTF and the
requested PDTCHs exceed the GDS or PMC capacity on the PCU:

COMMAND ACCEPTED: WARNING: Insufficient GDS resources available for

all PDTCHs on the PCU.

The following warning message displays if a frequency is specified that is already in use
at the site:

COMMAND ACCEPTED: WARNING: Specified ARFCN exists at specified site.

The following warning message displays if a frequency is specified that is already used at a cell:

COMMAND ACCEPTED: WARNING: Specified ARFCN exists in this cell.

68P02901W23-T 2-59
Jan 2010
RTF Chapter 2: Equipping the CM database

Reject messages

The following message displays if the max_tx_bts for the cell must be reduced before an RTF
can use the specified ARFCN:

COMMAND REJECTED: Block edge ARFCN not allowed for max_tx_bts level of the cell

The following message displays if the ARFCN specified for the RTF is not valid for the cell:

COMMAND REJECTED: An out of range frequency was entered for this frequency.

The following message displays if the trx_pwr_red for the carrier must be reduced before
the RTF can use a specified ARFCN:

COMMAND REJECTED: Power level is not allowed for a Carrier with a PCS block edge
ARFCN.

Error messages

The following error messages occur when attempting to equip an RTF for EGPRS:
For a site which has no Horizon macro, Horizonmacro2 or M-Cell family of cabinets
equipped:

COMMAND REJECTED: Horizonmacro, Horizonmacro2, or Mcell family of cabinets

required for EGPRS.

With 32 kbit/s packet radio capabilities, when the Coding Scheme 3 and 4 feature is
restricted:

COMMAND REJECTED: Received a request to modify a restricted optional feature.

With 64 kbit/s packet radio capabilities, when the EGPRS feature is restricted:

COMMAND REJECTED: Received a request to modify a restricted optional feature.

Which is baseband hopping through other non-EGPRS RTFs:

COMMAND REJECTED: EGPRS and non-EGPRS carriers cannot have the same FHI

That is subequipped:

COMMAND REJECTED: 32 kbit/s / 64 kbit/s TRAU rate is not allowed for

sub-equipped RTFs

With an associated RSL:

COMMAND REJECTED: Multiplexed RSL is not allowed with 64 K RTFs

At a site that supports dynamic allocation:

COMMAND REJECTED: 32 kbit/s / 64 kbit/s TRAU rate is not allowed at sites

using dynamic allocation.

If a non-zero value of extended range time slots is entered for an RTF with 64 kbit/s packet
radio capabilities:

COMMAND REJECTED: Extended range time slots are not allowed for EGPRS
carriers.

2-60 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference RTF

With a valid FHI, outside Sysgen mode:

If the RTF is at a site whose master cabinet is not a Horizon II macro.

If the hopping system is set to baseband hopping.

COMMAND REJECTED: Master cabinet must be Horizonmacro2 for EGPRS RTFs to hop
in baseband hopping.

To be in the inner zone of a concentric cell:

COMMAND REJECTED: EGPRS/GPRS carriers must be in the outer zone of a

concentric cell.

Command prompts

Prompt Optional Range Default Comments

Enter capacity of N FULL or This prompt does not
carrier: SUB display if:
- the RTF is equipped
to a BTS using dynamic
allocation.
- the subequipped RTF
feature is not available.
Enter the type of N bcch or None
carrier: non_bcch
Enter the 1st and 2nd N Valid first None
RTF ID: RTF ID:
0 - 5.
Valid
second
RTF ID:
0 - 11,
0 - 1 for
M-Cell.
Enter the primary N 0 - 9 None If the BTS type is 16 k RSL,
Unique PATH ID: the system displays the
next prompt. Otherwise,
proceed with the Enter
the optional secondary
Unique Path ID prompt.
This prompt displays if the
RTF is equipped to a BTS
using dynamic allocation.
Enter the optional N micro: 0 - 1. None If the RTF is equipped
2nd identifier for the M-Cell: to a BTS using dynamic
associated RSL: 0 - 5. allocation, this prompt
InCell: 0 - 7. does not display.

Continued

68P02901W23-T 2-61
Jan 2010
RTF Chapter 2: Equipping the CM database

Prompt Optional Range Default Comments

Enter the optional Y 0 - 9
secondary Unique Path
ID:
Enter the GSM cell to N GSM cell
which this carrier is
assigned:
Enter the carrier N See
absolute radio freq.
channel:
Enter the eight N 0 - 3 and
carrier frequency
hopping indicators:
None This prompt is provided for
only RTFs at remote BTS
sites.
This prompt does not
display if the RTF is
equipped to a BTS using
dynamic allocation.
None The cell number can be
ID or in either seven parameter
cell_name format or four parameter
format.
None The first channel from
Comments. which to hop, as set in the
MA (Mobile Allocation).
Used to set the MA index
offset, which defines the
channel from which the MS
is to hop.
PGSM
BCCH (not extended) 1-124
NON_BCCH (not extended)
1-124
EGSM
BCCH (extended) 0, 1-124,
or 975-1023
NON_BCCH (extended) 0,
1-124 or 975-1023
DCS1800
BCCH (not extended)
512-885
NON_BCCH (not extended)
512-885
PCS1900
BCCH (not extended)
512-810
NON-BCCH (not extended)
512-810
255 The eight frequency
255 hopping indicators are
entered on a single line
with one space separating
each value. The input for
this value must include all
eight values or no values.
A value of 255 means no
hopping.
A value of 255 is required
for all M-Cellcity sites.

Continued

2-62 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference
Prompt
Enter the eight
carrier training
sequence codes:
Enter KSW pair that
manages this carrier:
Enter the cell zone:
Enter the TRX transmit
power reduction:
Enter the number of
extended range time
slots allowed:
Enter the SDCCH load
Enter the SDCCH
placement priority:
Enter the channel
allocation priority:
Enter the packet radio
capability:
Enter the
rtf_ds0_count:
68P02901W23-T
RTF
Optional Range Default Comments
N 0 - 7 None The eight carrier training
sequence codes are entered
on a single line with one
space separating each
value.
N 0 - 3 None This prompt does not
appear when equipping the
RTF to an M-Cell site.
N 0 or 1 0 0 = Outer zone
1 = Inner zone
This prompt appears
only for NON-BCCH
carriers and only if the
Concentric Cells feature is
unrestricted.
Y same Only prompted when the
value as Concentric Cells feature is
max_tx_bts enabled. Only prompted
for inner zone carriers.
Y 0 - 4 Only prompted for outer
zone carriers. Only
prompted when the
Extended Range Cell
feature is unrestricted.
Y 0 - 2 The system displays this
prompt for outer zone
carriers (cell_zone = 0)
only.
Y 0 - 250 The system displays this
prompt if:
for outer zone carriers
(cell_zone = 0) only, and
sdcch_load is not set to 0
( 0).
Y 0 - 250
N 0 - 3, or 0 (None) This prompt only occurs
None, 16 K, if the GPRS feature is
32 K, 64 K unrestricted and if it is an
outer zone carrier.
For a complete description
of this parameter, refer to
Chapter 8 Device/Function
parameters.
Y 3 - 8 3 This prompt only occurs
if the VersaTRAU (VT)
feature is unrestricted.
Continued
2-63
Jan 2010
RTF Chapter 2: Equipping the CM database

Prompt Optional Range Default Comments

Enter the value for
Half Rate enabled:
Is 8 kbit/s TRAU
allowed (yes/no):
0 or 1 0 This prompt only occurs
at Half Rate capable
BTSs such as M-Cell2,
M-Cell6, Horizon macro
and Horizon II macro, if
AMR and/or GSM HR are/is
unrestricted.
Y Y or N Y This prompt only occurs
at Half Rate capable
BTSs such as M-Cell2,
M-Cell6, Horizon macro,
and Horizon II macro when
half_rate_enabled is set
to 1.

NOTE
When the equip RTF is completed, check the state of the RTF. If the RTF is not in the
BUSY_ENABLED state, check the DRI that supports the new RTF. If the DRI is not
in service (DU INHIBITED) use the MMI to place the DRI in service. The DRI must
be BUSY_UNLOCKED.

2-64 68P02901W23-T
Jan 2010
 Chapter

Device/function related commands

Device/function commands are commands that can be entered at the MMI to create, modify,
display, delete devices and functions within the BSS.

This chapter contains relevant information on device related and function related commands,
together with individual descriptions for the following types of Man Machine Interface (MMI)
commands:
Maintenance (Fault Management)

System Change Control (Configuration Management)

Call Processing

Miscellaneous

NOTE
Statistical commands are described in Chapter 5 Statistics commands.

68P02901W23-T 3-1
Jan 2010
Command reference presentation Chapter 3: Device/function related commands

Command reference presentation

The individual MMI command descriptions are presented in alphabetical order in the following
command reference layout:

Command title - the actual command reference which appears at the head of the page,
and in the contents and the index of this manual.

Description - provides a description of the MMI command function and includes:

Security level - the access security level for the command.

Supported by OMC-R GUI - whether the command is supported at the OMC-R GUI.

Command type - whether type A (no operator actions) or type B.

Prerequisites - conditions that must be met or exist for the command to be accepted.

Operator actions - actions required by the operator for type B commands. If no

actions are required, this field is not shown.

Format - includes the input command:

Syntax - the structure of the command and input parameter string.

Input parameters - descriptions of each command input parameter.

Examples - provides various examples of command input and the expected response.

References - includes where appropriate:

Related information - any relevant information, such as command prompts, specific
responses.

Related commands - any commands that are related.

3-2 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Device-related commands

Device-related commands

This section provides tables listing the devices and the literals by which they are identified in
device-related commands, and the specific commands as relevant to the devices.

Device literals

Table 3-1 lists the device literals and their descriptions.

Table 3-1 Device literals and descriptions

Literal Description
ABSS Associated Base Station Substation
AXCDR Associated RXCDR
{34371G} BBU Baseband Unit
BSS Base Station Substation
BSP Base Site Processor (at BSC)
BTP Base Transceiver Processor (at BTS)
CAB Cabinet
CAGE Cage
CBL Cell Broadcast Link
CBUS Clock Bus
CELL Cell
CIC Circuit Identity Code
COMB Combiner
CSFP Code Storage Facility Processor (at BSC or BTS)
DHP Digital radio Host Processor
DPROC Data Processor board (GPRS)
DRI Digital Radio Interface
DYNET Dynamic Network of BTSs
EAS External Alarm System
ETH Ethernet port
GBL Gb Link (GPRS)
GCLK Generic Clock
GDS GPRS Data Stream (GPRS)
GPROC Generic Processor

Continued

68P02901W23-T 3-3
Jan 2010
Devices and commands Chapter 3: Device/function related commands

Table 3-1 Device literals and descriptions (Continued)

Literal Description
GPROC2 Generic Processor 2
GPROC3 Generic Processor 3
GSL GPRS Signaling Link (GPRS)
KSW Kilo-port Switch
LAN Local Area Network
LMTL Location Message Transfer Link
MMS 1.544/2.048 Mbit/s link on an MSI board
MPRT 1.544/2.048 Mbit/s Port
MSI 1.544/2.048 Mbit/s Interface board
MTL Message Transfer Link
OML Operations and Maintenance Link
OPL OPtimization Link
PATH Path
PBUS Processor (MCAP) Bus
PCHN Physical Channel
PCU PCU Device (GPRS)
PSI Packet Subrate Interface
PSP PCU System Processor (GPRS)
RSL Radio System Link (Abis)
SBUS Serial Bus
SITE BSC or BTS
TBUS TDM Bus
TDM Time Division Multiplex
XBL RXCDR to BSC fault management Link

Devices and commands

Table 3-2 lists the specific commands as relevant to the devices.

3-4 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Devices and commands

Table 3-2 Device and command relationship

Device Commands Affected Notes

{34371G} BBU disp_equipment, disp_process, state,
reset_device, lock_device, unlock_device,
ins_device, device_audit, query_audits,
chg_audit_sched, disp_stats

BSP equip, unequip, unlock_device, state, disp_equipment includes

disp_equipment, device_audit Hardware Version Number
(HVN).
lock_device, ins_device, reset_device Cause a hard reset of the
device.
BTP equip, unequip, unlock_device, state, disp_equipment includes
disp_equipment, device_audit HVN.
lock_device, ins_device, reset_device Cause a hard reset of the
device.
CAB equip, state, disp_equipment
CAB(PCU) state Valid for GPRS only.
CAGE equip, state, disp_equipment Valid for BSC and InCell
BTS.
CAGE (PCU) equip, state, disp_equipment, device_audit, Valid for GPRS only.
cage_audit
CBL equip, unequip, lock_device, unlock_device, Valid for BSC only.
state, disp_equipment, ins_device,
reset_device
CBUS state Valid for BSC and InCell
BTS.
CELL state
CIC equip, unequip, lock_device, unlock_device, Valid for BSC only.
state, disp_equipment, ins_device,
reset_device, shutdown_device
COMB equip, unequip, lock_device, unlock_device,
state, disp_equipment, ins_device,
reset_device, swap_devices
CSFP state, disp_equipment
equip, unequip, lock_device, unlock_device, Valid for BSC and InCell
ins_device, reset_device BTS.
DHP equip, unequip, lock_device, unlock_device, Valid for BSC and InCell
state, disp_equipment, ins_device, BTS
reset_device, device_audit disp_equipment includes
HVN.
DPROC equip, unequip, lock_device, unlock_device, Valid for GPRS only.
state, disp_equipment, ins_device,
reset_device, device_audit

Continued

68P02901W23-T 3-5
Jan 2010
Devices and commands Chapter 3: Device/function related commands

Table 3-2 Device and command relationship (Continued)

Device Commands Affected Notes
DRI equip, unequip, lock_device, unlock_device, disp_equipment includes
state, disp_equipment, ins_device, HVN.
reset_device, device_audit, shutdown_device
EAS equip, unequip, lock_device, unlock_device,
state, disp_equipment, ins_device,
reset_device
ETH lock_device, unlock_device, state,
disp_equipment, ins_device
GBL equip, unequip, lock_device, unlock_device, Valid for GPRS only.
state, disp_equipment, ins_device,
reset_device
GCLK equip, unequip, lock_device, unlock_device, Valid for BSC and InCell
state, disp_equipment, ins_device, BTS.
reset_device, swap_devices, device_audit disp_equipment includes
HVN.
GDS equip, unequip, lock_device, unlock_device, Valid for GPRS only.
state, disp_equipment, ins_device,
reset_device
GPROC equip, unequip, unlock_device, state, Valid for BSC and InCell
disp_equipment, device_audit BTS.
disp_equipment includes
HVN.
lock_device, ins_device, reset_device Valid for BSC and InCell
BTS.
Cause a hard reset of the
device.
GPROC2 equip, unequip, unlock_device, state, Valid for BSC and InCell
disp_equipment, device_audit BTS.
disp_equipment includes
HVN.
lock_device, ins_device, reset_device Valid for BSC and InCell
BTS.
Cause a hard reset of the
device.
GPROC3 equip, unequip, unlock_device, state, Valid for BSC and InCell
disp_equipment, device_audit BTS.
disp_equipment includes
HVN.
lock_device, ins_device, reset_device Valid for BSC and InCell
BTS.
Cause a hard reset of the
device.
GSL equip, unequip, lock_device, unlock_device, GPRS only.
state, disp_equipment, ins_device,
reset_device

Continued

3-6 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Devices and commands

Table 3-2 Device and command relationship (Continued)

Device Commands Affected Notes
KSW equip, unequip, unlock_device, state, Valid for BSC and InCell
disp_equipment, device_audit, ins_device BTS.
disp_equipment includes
HVN.
lock_device, reset_device Valid for BSC and InCell
BTS.
Cause a hard reset of the
device.
LAN state, swap_devices Valid for BSC and InCell
BTS.
MMS lock_device, unlock_device, state,
disp_equipment, ins_device, reset_device
MPRT shutdown_device Valid for BSC only.
MSI equip, unequip, lock_device, unlock_device, disp_equipment includes
state, disp_equipment, ins_device, HVN.
device_audit
reset_device Causes a hard reset of the
device.
MTL equip, unequip, lock_device, unlock_device, Valid for BSC only.
state, disp_equipment, ins_device,
reset_device, shutdown_device
OML equip, unequip, lock_device, unlock_device, Valid for BSC only.
state, disp_equipment, ins_device,
reset_device
OPL equip, unequip, lock_device, unlock_device, Valid for BSC only.
state, disp_equipment, ins_device,
reset_device
PATH equip, unequip, lock_device, unlock_device, Valid for BSC only.
state, disp_equipment, ins_device,
reset_device
PBUS state Valid for BSC and InCell
BTS.
PCHN state, lock_device, unlock_device, ins_device,
reset_device
PCU equip, unequip, lock_device, unlock_device, Valid for GPRS only.
state, disp_equipment, ins_device,
reset_device site_audit, base_ip_address
PPROC lock_device, unlock_device, state,
disp_equipment, reset_device,
base_ip_address
PSI equip, unequip, lock_device, unlock_device,
state, disp_equipment, reset_device,
ins_device, device_audit, chg_audit_sched,
modify_value, query_audits, tdm_ts_blocks

Continued

68P02901W23-T 3-7
Jan 2010
Devices and commands Chapter 3: Device/function related commands

Table 3-2 Device and command relationship (Continued)

Device Commands Affected Notes
PSP equip, state, disp_equipment, device_audit, Valid for GPRS only.
unequip
RSL lock_device, unlock_device, state,
disp_equipment, ins_device, reset_device
RSL equip, unequip Valid for BSC only.
SBUS state Valid for BSC and InCell
BTS.
SITE equip, unequip, lock_device, unlock_device, Valid for BSC only.
state, disp_equipment, ins_device,
reset_device
TBUS state Valid for BSC and InCell
BTS.
TDM state, swap_devices, device_audit Valid for BSC and InCell
BTS.
XBL equip, unequip, lock_device, unlock_device, Valid for BSC only.
state, disp_equipment, ins_device,
reset_device

3-8 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Device identifiers

Device identifiers

A device is specified in the system by three identifiers. However, not all devices have three
device IDs. For devices that have only one or two device identifiers, zeros must be entered for
the remaining device identifier parameters as place holders.

Device ID requirements

Table 3-3 lists and defines the device ID requirements.

Table 3-3 Device ID requirements

Device
Range Definition
Names/IDs
ABSS Associated Base Station Processor
device ID 1 0 - 254 Corresponds to the BSS network entity that this device represents.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
AXCDR Associated XCDR
device ID 1 0 - 254 Corresponds to the RXCDR network entity that this device
represents.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
{34371G} BBU Baseband unit
device ID 1 0 - 1
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
BCUP BSS Controller Unit Power Supply per cage.
device ID 1 0 - 15 Identifies the cage number.
device ID 2 0 - 2 Identifies which power supply (of the three possible per cage).
device ID 3 0 Serves as place holder.
BSP Base Site Processor, BSC
device ID 1 0 or 1 Identifies which BSP board is active and which is redundant
(standby). (None at a BTS.)
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
BSS Base Station System

Continued

68P02901W23-T 3-9
Jan 2010
Device ID requirements Chapter 3: Device/function related commands

Table 3-3 Device ID requirements (Continued)

Device
Range Definition
Names/IDs
device ID 1 0 - 254 Identifies BSS.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
BTP Base Transceiver Processor, BTS
device ID 1 1 Identifies which BTP board is active and which is redundant
(standby). (None at a BSC or RXCDR.)
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
CAB CABinet
device ID 1 0 - 20 Identifies cabinet number.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
CAGE CAGE
device ID 1 0 - 15 Identifies the value at which the LANX card, dial is set.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
CBL Cell Broadcast Link
device ID 1 0 Optional entry. (None at a BTS or RXCDR.)
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
CBUS Clock BUS
device ID 1 0 - 15 Identifies the cage where a specific GCLK is located.
device ID 2 0 or 1 Identifies the GCLK.
device ID 3 0 Serves as place holder.
COMB COMBiner
device ID 1 0 - 13 Identifies specific combiner cavities (13 active, 13 standby).
(None at an RXCDR.)
device ID 2 0 or 1 Identifies each individual processor in a combiner unit (of the two
present within a redundant pair).
device ID 3 0 Serves as place holder.
CSFP Code Storage Facility Processor
device ID 1 10 CSFP identifier (only at a BSC) - not M-Cell, automatically
equipped/unequipped.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.

Continued

3-10 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Device ID requirements

Table 3-3 Device ID requirements (Continued)

Device
Range Definition
Names/IDs
DHP Digital radio Host Processor, BTS
device ID 1 0 - 5 Identifies a digital module shelf (cage number) in a specific
cabinet. (None at an RXCDR.)
device ID 2 0 - 7 Identifies which DHP board is active and which is redundant
(standby).
device ID 3 0 Serves as place holder.
DPROC Digital Processor (GPRS)
device ID 1 1 - 6 or Identifies a specific DPROC Board.
11 - 16
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
DRI Digital Radio Interface
device ID 1 0 - 5 Identifies a user-defined DRI group within a site. The DRIs which
belong to this group must be allocated to the same cell and must
be connected to the same antenna. (None at an RXCDR.)
device ID 2 0 - 11 Identifies a specific DRI board.
device ID 3 0 Serves as place holder.
EAS External Alarm System
device ID 1 0 - 7 Identifies a specific PIX card at a site - not M-Cell.
0 - 15 M-Cell
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
GBL Gb Link (GPRS)
device ID 1 0 - 35 Identifies a specific GBL link
device ID 2 0 Serves as place holder
device ID 3 0 Serves as place holder
GCLK General CLocK
device ID 1 0 or 1 Identifies which GCLK board is active and which is redundant
(standby).
0=A side GCLK (slot A controls) - slot 5
1=B side GCLK (slot B controls) - slot 3
0 M-cell, automatically equipped/unequipped.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
GDS GPRS Data Stream (GPRS)
device ID 1 0 - 37 Identifies a specific GPRS data stream.
device ID 2 0 Serves as place holder.

Continued

68P02901W23-T 3-11
Jan 2010
Device ID requirements Chapter 3: Device/function related commands

Table 3-3 Device ID requirements (Continued)

Device
Range Definition
Names/IDs
device ID 3 0 Serves as place holder.
GPROC Generic PROCessor, device used for functions.
device ID 1 0 - 111 Identifies a specific GPROC board.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
GSL GPRS Signaling Link (GPRS)
device ID 1 0 - 59 Identifies a specific GPRS signaling link.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
KSW Kiloport SWitch
device ID 1 0 - 3 Identifies a section (timeslot) of TDM highway.
M-Cell not applicable.
device ID 2 0 or 1 Identifies which KSW board (highway, A side, or B side) is active
and which is redundant (standby). (0 is slot 27 and 1 is slot 1.)
device ID 3 0 Serves as place holder.
LAN Local Area Network
device ID 1 0 or 1 Identifies which LAN board (A side or B side) is active and which
is redundant (standby).
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
MMS The E1 Mbit/s line on a Multiple Serial Interface board.
device ID 1 0 - 95 Matches the first ID of the host MSI with 0 - 95
9 for BSC and 0 - 123 for RXCDR.
3 BTS only: not M-Cell
1 BTS only: M-Cell6
0 BTS only: M-Cell2
BTS only: M-Cellmicro
device ID 2 0 or 1 Identifies a specific MMS.
device ID 3 0 Serves as place holder.
MSI Multiple Serial Interface board
device ID 1 Identifies a specific MSI board:
BSC
0 - 95 RXCDR
0 - 71 BTS only: not M-Cell
9 BTS only: M-Cell6
3 BTS only: M-Cell2
1 BTS only: M-Cellmicro
0
device ID 2 0 Serves as place holder.

Continued

3-12 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Device ID requirements

Table 3-3 Device ID requirements (Continued)

Device
Range Definition
Names/IDs
device ID 3 0 Serves as place holder.
MTL Message Transfer Link
device ID 1 0 - 15 Identifies a specific MTP link (per ITU-TSS spec).
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
OML Operations and Maintenance Link
device ID 1 0 - 3 Identifies a specific connection (link) between the BSC and the
OMC-R (BSC or RXCDR).
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
OPL OPtimization Link
device ID 1 0 - 3 Identifies a specific connection (link) between the BSC and the
IOS platform.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
PATH
device ID 1 0 - 140 Identifies the terminating site (BSC only).
device ID 2 0 - 9 Identifies a unique PATH ID.
device ID 3 0 Serves as place holder.
PBUS Processor (MCAP) BUS
device ID 1 0 - 15 Identifies the cage at that location.
device ID 2 0 or 1 Identifies which PBUS (A side or B side) is active and which is
redundant (standby).
device ID 3 0 Serves as place holder.
RSL Radio System Link
device ID 1 0 - 140 Identifies the site to which the RSL is connecting (BSC only).
device ID 2 0 - 7 Identifies a specific link set (not M-Cell):
5 M-Cell2 and M-Cell6
1 M-Cellmicro
device ID 3 0 Serves as place holder.
RTF Receive Transmit Function
device ID 1 0 - 5 Identifies the cell group.
device ID 2 0 - 11 Identifies a unique function within the cell group.
device ID 3 0 Serves as place holder.
RXCDR Remote transcoder

Continued

68P02901W23-T 3-13
Jan 2010
Device ID requirements Chapter 3: Device/function related commands

Table 3-3 Device ID requirements (Continued)

Device
Range Definition
Names/IDs
device ID 1 0 - 254
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
SITE BTS SITE
device ID 1 0 - 140 Identifies the site for which commands are being executed.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
SBUS Serial BUS
device ID 1 0 - 15 Identifies the cage at that location.
device ID 2 0 or 1 Identifies which SBUS (A side or B side) is active and which is
redundant (standby).
device ID 3 0 Serves as place holder.
TBUS TDM BUS
device ID 1 0 - 15 Identifies the cage at that location.
device ID 2 0 or 1 Identifies which TBUS (A side or B side) is active and which is
redundant (standby).
TDM Time Division Multiplex Highway
device ID 1 0 or 1 Identifies which side (A side or B side) of the TDM highway is
active and which is redundant (standby).
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.
XBL RXCDR to BSC Fault Management Link.
device ID 1 0 - 9 Identifies a specific connection (link) between the RXCDR and
the BSC.
device ID 2 0 Serves as place holder.
device ID 3 0 Serves as place holder.

3-14 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Function related commands

Function related commands

The function-related commands that affect the functions are listed in Table 3-4.
The first column gives the function literal.

The second column gives the function name.

The remaining columns show the commands that are supported for each function.

Table 3-4 Function related commands

Device name / Commands

Literal
description unequip equip state disp_equipment
LCF Link Control X X X X
Function, BSC
OMF Operation and X X X X
Maintenance
Function, BSC
RTF Receive Transmit X X X X
Function
RXF Receive Function X
TXF Transmit Function X

68P02901W23-T 3-15
Jan 2010
Function identifiers Chapter 3: Device/function related commands

Function identifiers

A function is identified in the system by up to three identifiers, however, not all functions have
three device IDs. For functions that have only one or two device identifiers, zeros must be
entered for the remaining function identifiers as place holders.

Function ID requirements

Table 3-5 lists and defines the Function ID requirements.

Table 3-5 Function ID requirements

Device
Range Definition
Names / IDs
BTF Base Transceiver Function (BTS only)
function ID 1 0-2 Identifies maximum number of DRIs supported by this BTF (not
1 M-Cell)
M-Cell only
function ID 2 0 Serves as a place holder
function ID 3 0 Serves as a place holder
LCF Link Control Function (BSC only)
function ID 1 0 - 24 Identifies specific control links to the MSC and/or the BTS
function ID 2 0 Serves as a place holder
function ID 3 0 Serves as a place holder
OMF Operation and Maintenance Function (BSC and RXCDR only)
function ID 1 None Identifies the OMF (BSC or BSS sites where BSC type is 2)
function ID 2 0 Serves as a place holder
function ID 3 0 Serves as a place holder
RTF Receive Transmit Function (BSC and BTS only)
function ID 1 0 - 29 Identifies the RTF group to which the RTF belongs
function ID 2 0 - 24 Identifies a specific RTF function
function ID 3 0 Serves as a place holder

3-16 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Slots

Slots

Cage slots are allocated to devices dependent on the site function.

Valid slots table

Table 3-6 lists the cage slots that are valid for the software supported devices.

Table 3-6 Valid slots

Device BSS BSC BTS RXCDR

BSP cage = 0 cage = 0 N/A cage = 0
slot = 20 or 24 slot = 20 or 24 slot = 25 or 26
or or or
cage = 1 cage = 1 cage = 1
slot = 20 slot = 20 slot = 25
BTP N/A N/A cage = 15 N/A
slot = 20 or 24
or
cage = 14
slot = 20
CSFP 18 - 25 18 - 25 18 - 25 25 or 26
cage 0 - 13 cage 0 - 13 cage 2 - 15 cage 0 - 13
DHP 18 - 25 N/A 18 - 25 N/A
cage 0 - 13 cage 2 - 15
DRI 7, 9, 11, 13, 15, 17 N/A 7, 9, 11, 13, 15, 17 N/A
EAS 15 - 18 15 - 18 15 - 18 15 - 18
(daughter slots) (daughter slots) (daughter slots) (daughter slots)
GCLK device_id1 = 0 device_id1 = 0 device_id1 = 0 device_id1 = 0
slot = 5 slot = 5 slot = 5 slot = 5
or or or or
device_id1 = 1 device_id1 = 1 device_id1 = 1 device_id1 = 1
slot = 3 slot = 3 slot = 3 slot = 3
GPROC 18 - 25 18 - 25 18 - 25 25 or 26
cage 0 - 13 cage 0 - 13 cage 2 - 15 cage 0 - 13
MSI 6 - 17 6 - 17 MSI type = 0 MSI type = 0
slot = 6 - 17 slot = 6 - 10
or or
MSI type = 1, 255 MSI type = 1, 255
(slot = N/A) slot = 6 - 24

68P02901W23-T 3-17
Jan 2010
equip/unequip command matrix Chapter 3: Device/function related commands

equip/unequip command matrix

Table 3-7 is a matrix showing which devices and functions can be equipped and unequipped
inside and outside of the SYSGEN ON mode.

Table 3-7 Equip/Unequip command matrix

Device/ Equip in Equip outside Unequip in Unequip outside

Function SYSGEN SYSGEN SYSGEN SYSGEN
BSP Supported Supported Supported Supported only if
standby device.
BTP Supported Supported Supported Supported only
standby device.
CAB Supported Type B command: Unsupported Unsupported
lock the site before
entering the equip or
unequip commands.
CAGE Supported Type B command: Unsupported Unsupported
lock the site before
entering the equip or
unequip commands.
CBL Supported Supported Supported Supported
COMB Supported Supported Supported Supported
CSFP Supported Supported Supported Supported
DHP Supported Supported Supported Supported
DRI Supported Supported Supported Supported
EAS Supported Supported Supported Supported
GCLK Supported Supported Supported Supported
GPROC Supported Supported Supported Supported
KSW Supported Supported Supported Supported
LCF Supported Supported Unequip LCF is only supported if no
sites exist on the LCF.
MSI Supported Supported Supported Supported

NOTE
The equip and unequip commands do not support the MSIs of type NIU2 (that
is, an MSI at a Horizon II site).
MTL Supported Unsupported Supported Supported
OMF Supported Supported Supported Unsupported
OML Supported Unsupported Supported Supported

Continued

3-18 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference equip/unequip command matrix

Table 3-7 Equip/Unequip command matrix (Continued)

Device/ Equip in Equip outside Unequip in Unequip outside
Function SYSGEN SYSGEN SYSGEN SYSGEN
OPL Supported Unsupported Supported Supported
PATH Supported Supported Supported Supported
PSI Supported Supported Supported Supported

RSL Supported Supported Supported Supported

RTF Supported Supported Supported Supported
SITE Supported Supported Supported Supported
XBL Supported Supported Supported Supported

68P02901W23-T 3-19
Jan 2010
Alarm devices Chapter 3: Device/function related commands

Alarm devices

Table 3-8 shows the valid alarm reporting devices and alarm devices that are subject to
throttling. For the associated alarm code ranges, refer to Maintenance Information: Alarm
Handling at the OMC-R (68P02901W26) in which alarms are fully described.

Table 3-8 Alarm devices

Device Name Valid Alarm Reporting Device Valid Alarm Throttle Device
{34371G} BBU YES NO
BCUP YES NO
BSP YES YES
BSS YES YES
BTP YES YES
CAB NO NO
CAGE YES YES
CBL YES NO
CBUS YES NO
CELL YES NO
COMB YES NO
CSFP NO NO
DHP YES NO
DRI YES YES
EAS YES NO
GCLK YES YES
GPROC YES YES
IAS YES NO
KSW YES YES
LAN YES NO
MMS YES YES
MSI YES YES
MTL YES YES
OMC YES NO
OML YES NO
OPL YES NO
PATH YES NO
PBUS YES NO

Continued

3-20 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Alarm devices

Table 3-8 Alarm devices (Continued)

Device Name Valid Alarm Reporting Device Valid Alarm Throttle Device
RSL YES YES
SBUS YES NO
SITE YES NO
TBUS YES NO
TDM YES NO
TRU YES NO
TSLOT YES NO
XBL YES YES
XCDR YES YES

68P02901W23-T 3-21
Jan 2010
add_cell Chapter 3: Device/function related commands

add_cell

Description

The add_cell command adds a cell to the CM database. The add_cell command is invoked
with the location and gsm_cell_idparameters. After the command is entered, a series of
prompts to define the cell are displayed. The prompted parameters are described in Related
information on page 3-25.

Different sites can be equipped with various numbers of cells.

Only one cell is permitted at an M-Cellcity, Horizonmicro or Horizoncompact site. The system
rejects the add_cell command if it is entered for one of these sites, where a cell exists.

Sites can have up to six cells. The system rejects the add_cell command if it is entered for a
site where six cells exist.

This command can be abandoned at any time by entering done in response to any prompt. If a
database parameter has a default, the default value can be entered by pressing the RETURN
key. If a database parameter has a default value and a value outside the parameter valid range
is typed, the system uses the default value.

If the database parameter does not have a default value and no value or a value outside the
parameter valid range is entered, the command is abandoned, losing any previously entered
parameters.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites The add_cell command is not allowed at an RXCDR.
Operator actions Reply to prompts as displayed, directly or in a script.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

add_cell <gsm_cell_id> <location> [cell_name]

3-22 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Input parameters

gsm_cell_id

Specifies the GSM cell ID for the cell to be added.

The format for the GSM cell ID depends on:

The system being used (PGSM, EGSM, DCS1800, PCS1900, or GSM850)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled:

Seven parameter format:

a b c d e f g

Where: is:
a first digit of the MCC (Mobile Country Code).
b second digit of the MCC.
c third digit of the MCC.
d first digit of the MNC (Mobile Network Code).
e second digit of the MNC.
f LAC (Local Area Code).
g CI (Cell Identity).

Four parameter format:

abc zde f g

Where: is:
a first digit of the MCC (Mobile Country Code).
b second digit of the MCC.
c third digit of the MCC.
z first digit of the MNC (Mobile Network Code).
d second digit of the MNC.
e third digit of the MNC.
f LAC (Local Area Code).
g CI (Cell Identity).

Only PCS1900 and GSM850 systems can use a three-digit MNC.

NOTE
A cell_name as defined by the cell_name command is not valid in add_cell commands.

68P02901W23-T 3-23
Jan 2010
Examples Chapter 3: Device/function related commands

location

Specifies the location of the cell:

0 - 140 BTS

cell_name

The name to be assigned to the Cell ID. The cell name must be entered inside double quotation
marks.

The cell name can be from one to 31 alphanumeric characters. The dash character can be used
as a separator. The underscore character cannot be used as part of the name or as a separator.
Double quotation marks cannot be used as part of a cell name.

Cell names cannot be equivalent to the following character strings in upper or lower case:

all no name defined name not available

Entering two consecutive double quotation marks removes the current cell name.

If no value is entered for this parameter, the current cell name displays.

Examples

Example 1

In this example, a cell with GSM cell ID 5 4 3 2 1 61986 34944 at site 0 is added to the CM
database:

add_cell 5 4 3 2 1 61986 34944 0

Where: is:
5 4 3 2 1 61986 34944 GSM cell ID.
0 location.

System response

Prompts are displayed for the parameters to define the cell.

Example 2

In this example, a cell with GSM cell ID 5 4 3 2 1 61986 34944 at site 5 (a BTS site) is added
to the CM database.

add_cell 5 4 3 2 1 61986 34944 5

Where: is:
5 4 3 2 1 61986 34944 GSM cell ID.
5 location.

3-24 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

Prompts are displayed for the parameters to define the cell.

Example 3

In this example, a PCS1900 cell with GSM cell ID 5 4 3 7 2 1 61986 34944 is added to the CM
database. This example shows the four-parameter GSM cell ID format.

add_cell 543 721 61986 34944 0

Where: is:
543 721 61986 34944 GSM cell ID.
0 location.

System response

Prompts are displayed for the parameters to define the cell.

References

Related information

Table 3-9 lists the prompts for the add_cell command.

Parameters are assigned by entering the parameter value only, or the contents of the input
column of the add_cell command prompts table exactly as presented, where x is the parameter
value. For example, a CRM wait indication parameter value of 5 can be assigned by entering
the following at the prompt:

wait_indication_parameters=5

The word odd in the Range column indicates that only odd values are accepted. Similarly, the
word even indicates that only even values are accepted.

If a parameter has a default value, the default value can be entered for the parameter by
pressing the RETURN key. If the parameter has a default value and an invalid value is entered,
an error message is presented and the parameter is assigned the default value.

If a parameter does not have a default value and the response to the prompt is not correct, or if
no response to the prompt is entered, the system aborts the add_cell command and displays
the system prompt. All values entered to that point are lost and must be re-entered if the cell is
to be added using the add_cell command.

There is a time limit of 30 seconds in which to enter a response to a prompt. If a proper response
is not entered within the time limit, the command aborts and all values entered up to that point
are lost. To abort the command manually, type done after any prompt.

68P02901W23-T 3-25
Jan 2010
References Chapter 3: Device/function related commands

NOTE
The copy_cell command description includes two alphabetical listings of which
parameters are included for that command and which are not included.

Table 3-9 add_cell command prompts

Prompt Input Range Default

Enter base station bsic=x 0 - 63 None
identity code:
Enter the Frequency Type: frequency_type=x 1 (pgsm) None
2 (egsm)
4 (dcs1800)
8 (pcs1900)
16 (gsm850)
Use numeric
values or text
string.
Enter wait indication wait_indication_parameters=x 0 - 255 5
parameters:
Enter common control ccch_conf=x 0, 1, 2, 4, or 6 0
channel configuration:
Enter blocks reserved for bs_ag_blks_res=x 0 - 7 0
access grant:
Enter bs_pa_mfrms=x 0 - 7 0
multiframes between
transmissions of
paging messages:
Enter extended paging extended_paging_active=x 0 or 1 0
active:
Enter number of SDCCHs number_sdcchs_preferred=x 4 - 44 8
preferred: (if ccch_conf=1)
8 - 48
(if ccch_conf1)
Enter enable incoming en_incom_ho=x 0 or 1 1
handover:
Enter intra cell handover intra_cell_handover_allowed=x 0 - 2 1
allowed:
Enter inter cell handover inter_cell_handover_allowed=x 0 - 3 1
allowed:
Enter number of preferred number_of_preferred_cells=x 1 - 16 16
cells:
Enter handover margin ho_margin_def=x -63 to 63 8
default:
Enter handover recognized handover_recognized_period=x 2 - 64 2
period:

Continued

3-26 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 3-9 add_cell command prompts (Continued)

Prompt Input Range Default
Enter uplink rxqual ul_rxqual_ho_allowed=x 0 or 1 1
handover allowed:
Enter downlink rxqual dl_rxqual_ho_allowed=x 0 or 1 1
handover allowed:
Enter uplink rxlev ul_rxlev_ho_allowed=x 0 or 1 1
handover allowed
Enter downlink rxlev dl_rxlev_ho_allowed=x 0 or 1 1
handover allowed:
Enter alternate flag for sdcch_ho=x 0 or 1 1
SDCCH handover:
Enter alternate SDCCH sdcch_timer_ho=x 1 - 31 1
handover timer value:
Enter interference interfer_ho_allowed=x 0 or 1 1
handover allowed:
Enter power handover pwr_handover_allowed=x 0 or 1 1
allowed:
Enter MS distance allowed: ms_distance_allowed=x 0 or 1 0
Enter alternate flag mspwr_alg=x 0 or 1 0
for MS power control
processing:
Enter handover power handover_power_level=x 2 - 19 None
level:
Enter power control pwrc=x 0 or 1 1
indicator for hopping
through BCCH:
Enter interference intave=x 1 - 31 8
measurement averaging
period (intave):
Enter timing advance timing_advance_period=x 1 - 31 4
period:
Enter MS power control ms_p_con_interval=x 0 - 31 2
period:
Enter MS timeout for MS ms_p_con_ack=x 0 - 31 2
power control:
Enter MS power control ms_power_control_allowed=x 0 or 1 1
allowed:
Enter BTS power control bts_p_con_interval=x 0 - 31 2
interval:
Enter BTS timeout for BTS bts_p_con_ack=x 0 - 31 1
power control:
Enter BTS power control bts_power_control_allowed=x 0 or 1 0
allowed: (0 for M-Cellmicro)

Continued

68P02901W23-T 3-27
Jan 2010
References Chapter 3: Device/function related commands

Table 3-9 add_cell command prompts (Continued)

Prompt Input Range Default
Enter power increment step pow_inc_step_size_ul=x 2 - 14 EVEN 2
size for uplink:
Enter power increment step pow_inc_step_size_dl=x 2 - 14 EVEN 2
size for downlink:
Enter power reduction step pow_red_step_size_ul=x 2 - 4 EVEN 2
size for uplink:
Enter power reduction step pow_red_step_size_dl=x 2 - 4 EVEN 2
size for downlink:
Enter dynamic step adjust dyn_step_adj=x 0 or 1 0
algorithm:
Enter factor of maximum dyn_step_adj_fmpr=x 0 - 10 10
power reduction:
Enter maximum BTS transmit max_tx_bts=x 0 - 21 0
power: (0 - 6 for
M-Cellmicro)
Enter maximum transmit MS: max_tx_ms=x 5 - 39 odd only 39
(PGSM or EGSM). 36
0 - 36 even 33
only (DCS1800).
0 - 32 even only,
and 33 (PCS1900).
Enter receive level rxlev_min_def=x 0 - 63 15
minimum default:
Enter MS transmit power ms_txpwr_max_def=x 5 - 39 odd only 39
maximum default: (PGSM or EGSM). 36
0 - 36 even 33
only (DCS1800).
0 - 32 even only,
and 33 (PCS1900).
Enter decision algorithm decision_alg_type=x 0 - 31 0
number:
Enter decision alg 1 dl decision_1_dl_rxlev_av_h 0 - 3 0
rxlev avg h: =x
Enter decision alg 1 dl decision_1_dl_rxlev_av_ih 0 - 3 0
rxlev avg ih: =x
Enter decision alg 1 dl decision_1_dl_rxlev_av_p 0 - 3 0
rxlev avg p: =x
Enter decision alg 1 dl decision_1_dl_rxqual_av_h 0 - 3 0
rxqual avg h: =x
Enter decision alg 1 dl decision_1_dl_rxqual_av_p 0 - 3 0
rxqual avg p: =x
Enter decision alg 1 n1: decision_1_n1=x 1 - 31 1
Enter decision alg 1 n2: decision_1_n2=x 1 - 31 1

Continued

3-28 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 3-9 add_cell command prompts (Continued)

Prompt Input Range Default
Enter decision alg 1 n3: decision_1_n3=x 1 - 31 1
Enter decision alg 1 n4: decision_1_n4=x 1 - 31 1
Enter decision alg 1 n5: decision_1_n5=x 1 - 31 1
Enter RSS decision alg 1 decision_1_n6=x 1 - 31 1
n6:
Enter RSS decision alg 1 decision_1_n7=x 1 - 31 1
n7:
Enter RSS decision alg 1 decision_1_n8=x 1 - 31 1
n8:
Enter decision alg 1 ncell decision_1_ncell_rxlev_av_h_calc 0 - 3 0
rxlev avg h calc: =x
Enter decision alg 1 p1: decision_1_p1=x 1 - 31 1
Enter decision alg 1 p2: decision_1_p2=x 1 - 31 1
Enter decision alg 1 p3: decision_1_p3=x 1 - 31 1
Enter decision alg 1 p4: decision_1_p4=x 1 - 31 1
Enter decision alg 1 p5: decision_1_p5=x 1 - 31 1
Enter decision alg 1 p6: decision_1_p6=x 1 - 31 1
Enter decision alg 1 p7: decision_1_p7=x 1 - 31 1
Enter decision alg 1 p8: decision_1_p8=x 1 - 31 1
Enter decision alg 1 power decision_1_p_bgt_rxlev_av_h 0 - 3 0
budget rxlev: =x
Enter decision alg 1 decision_1_tim_adv_av_alg 0 - 3 0
timing advance alg: =x
Enter decision alg 1 ul decision_1_ul_rxlev_av_h 0 - 3 0
rxlev avg h: =x
Enter decision alg 1 ul decision_1_ul_rxlev_av_ih 0 - 3 0
rxlev avg ih: =x
Enter decision alg 1 ul decision_1_ul_rxlev_av_p 0 - 3 0
rxlev avg p: =x
Enter decision alg 1 ul decision_1_ul_rxqual_av_h 0 - 3 0
rxqual avg h: =x
Enter decision alg 1 ul decision_1_ul_rxqual_av_p 0 - 3 0
rxqual avg p: =x
Enter quality band alt_qual_proc=x 0 or 1 0
processing allowed:

Continued

68P02901W23-T 3-29
Jan 2010
References Chapter 3: Device/function related commands

Table 3-9 add_cell command prompts (Continued)

Prompt Input Range Default
Enter power control l_rxqual_ul_p=x If alt_qual_proc 226 BER
threshold l_rxqual_ul_p: = 0, or
0 - 1810. 4 QBand
If alt_qual_proc
= 1,
0 - 7.
Enter power control l_rxqual_dl_p=x If alt_qual_proc 226 BER
threshold l_rxqual_dl_p: = 0, or
0 - 1810. 4 QBand
If alt_qual_proc
= 1,
0 - 7.
Enter power control u_rxqual_ul_p=x If alt_qual_proc 28 BER
threshold u_rxqual_ul_p: = 0, or
0 - 1810. 1 QBand
If alt_qual_proc
= 1,
0 - 7.
Enter power control u_rxqual_dl_p=x If alt_qual_proc 28 BER
threshold u_rxqual_dl_p: = 0, or
0 - 1810. 1 QBand
If alt_qual_proc
= 1,
0 - 7.
Enter handover threshold l_rxqual_ul_h=x If alt_qual_proc 453 BER
l_rxqual_ul_h: = 0, or
0 - 1810. 5 QBand
If alt_qual_proc
= 1,
0 - 7.
Enter handover threshold l_rxqual_dl_h=x If alt_qual_proc 453 BER
l_rxqual_dl_h: = 0, or
0 - 1810. 5 QBand
If alt_qual_proc
= 1,
0 - 7.
Enter handover threshold l_rxlev_ul_h=x 0 - 63 10
l_rxlev_ul_h:
Enter handover threshold l_rxlev_dl_h=x 0 - 63 1
l_rxlev_dl_h:
Enter handover threshold u_rxlev_ul_ih=x 0 - 63 45
u_rxlev_ul_ih:
Enter handover threshold u_rxlev_dl_ih=x 0 - 63 45
u_rxlev_dl_ih:

Continued

3-30 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 3-9 add_cell command prompts (Continued)

Prompt Input Range Default
Enter handover threshold ms_max_range=x 0 - 63 (only if None
mobile max range: ext_range_cell=0).
0 - 219 (if
ext_range_cell=1).
Enter power control l_rxlev_ul_p=x 0 - 63 30
threshold l_rxlev_ul_p:
Enter power control l_rxlev_dl_p=x 0 - 63 30
threshold l_rxlev_dl_p:
Enter power control u_rxlev_ul_p=x 0 - 63 40
threshold u_rxlev_ul_p:
Enter power control u_rxlev_dl_p=x 0 - 63 40
threshold u_rxlev_dl_p:
Enter Alternate flag for missing_rpt=x 0 or 1 0
missing report:
Enter Alternate flag for ba_alloc_proc=x 0 or 1 0
BA allocating process:
Enter RSS link fail: link_fail=x 0 - 15 4
Enter link about to fail: link_about_to_fail=x 0 - 15 2
Enter Alternate flag for full_pwr_rfloss=x 0 or 1 0
full power RF loss:
Enter cell bar access cell_bar_access_switch=x 0 or 1 0
switch:
Enter cell bar access cell_bar_access_class=x 0 - 65535 0
class:
Enter emergency class emergency_class_switch=x 0 or 1 0
switch:
Enter report resource TCH report_resource_tch_f_high_ 0 - 255 2
full high water mark: water_mark=x
Enter report resource TCH report_resource_tch_f_low_ 0 - 255 12
full low water mark: water_mark=x

NOTE
The value for report_resource_tch_f_high_water_mark must be
set less than the value for report_resource_tch_f_low_water_mark.
If report_resource_tch_f_high_water_mark, is greater than
report_resource_tch_f_low_water_mark the system rejects the add_cell
command.
Enter receive level access rxlev_access_min=x 0 - 63 None
minimum:
Enter uplink dtx dtx_required=x 0 - 2 2
preference:
Enter IMSI attach detach: attach_detach=x 0 or 1 0

Continued

68P02901W23-T 3-31
Jan 2010
References Chapter 3: Device/function related commands

Table 3-9 add_cell command prompts (Continued)

Prompt Input Range Default
Enter NCC of PLMN allowed: ncc_of_plmn_allowed=x 0 - 255 255
Enter maximum max_retran=x 0 - 3 0
retransmissions on RACH:
Enter maximum mobile ms_txpwr_max_cch=x 5 - 39 odd 2
transmit power on CCCH: only (PGSM
and EGSM).
0 - 36 even
only (DCS1800).
0 - 32 even only,
and 33 (PCS1900).
Enter tx_integer for RACH tx_integer=x 0 - 15 4
retransmit spacing:
Enter radio link timeout: radio_link_timeout=x 0 - 15 4
Enter MS reestablish reestablish_allowed=x 0 or 1 0
allowed:
Enter cell reselect cell_reselect_hysteresis=x 0 - 7 None
hysteresis:
EnterC2 cell reselection cell_reselect_param_ind=x 0 or 1 0
parameter indicator:
Enter C2 cell bar qualify: cell_bar_qualify=x 0 or 1 0
Enter C2 cell reselection cell_reselect_offset=x 0 - 63 0
offset:
Enter C2 temporary offset: temporary_offset=x 0 - 7 0
Enter C2 penalty time: penalty_time=x 0 - 31 0
Enter rapid power down rapid_pwr_down=x 0 or 1 0
procedure active:
Enter rapid power down rpd_trigger=x 0 - 63 45
trigger threshold:
Enter rapid power down rpd_offset=x 0 - 63 8
level offset:
Enter rapid power down rpd_period=x 1 - 32 2
averaging period:

Related commands

copy_cell on page 3-199 del_cell on page 3-212 disp_cell on page 3-261

disp_gsm_cells on page 3-350 freq_types_allowed on page
3-465

3-32 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference add_conn

add_conn

Description

The add_conn command adds MMS connectivity between the RXCDR and the BSS. Connectivity
can be added for a maximum of 21 MMSs at a BSC or RXCDR regardless of how many RXCDRs
or BSSs are connected.

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.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator action)
Prerequisites Enter this command at the BSC or RXCDR only.

Format

Syntax

add_conn <local_mms_id_1> <local_mms_id_2> <network_entity_id>

<remote_mms_id_1><remote_mms_id_2>

Input parameters

local_mms_id_1

First identifier of the MMS at the local site. The term local site refers to the site where the
command is being entered.

local_mms_id_2

Second identifier of the MMS at the local site.

network_entity_id

The AXCDR or ABSS device identifier that represents the actual RXCDR or BSS with which
this MMS is communicating.

remote_mms_id_1

First identifier of the MMS at the remote site. The term remote site refers to the site to which
the local site is being connected.

68P02901W23-T 3-33
Jan 2010
Example Chapter 3: Device/function related commands

remote_mms_id_2

Second identifier of the MMS at the remote site.

The add_conn command can be executed from either the BSC or RXCDR. Table 3-10 shows the
ranges for several input parameters dependent on where the command is executed.

Table 3-10 add_conn valid ranges

Execution location
Input parameter
BSC RXCDR
local_mms_id_1 0 - 95 0 - 123
local_mms_id_2 0 or 1 0 or 1
network_entity_id 1 - 254 1 - 254
remote_mms_id_1 0 - 123 0 - 95
remote_mms_id_2 0 or 1 0 or 1

Example

This example adds MMS connectivity between BSC MMS 4 1 and RXCDR MMS 9 0 of RXCDR 3,
represented by the equipped device AXCDR 3.

add_conn 4 1 3 9 0

Where: is:
4 local_mms_id_1
1 local_mms_id_2
3 network_entity_id
9 remote_mms_id_1
0 remote_mms_id_2

System response

COMMAND ACCEPTED

References

Related commands

del_conn on page 3-215 disp_conn on page 3-282 mod_conn on page 3-492

3-34 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference add_neighbor

add_neighbor

Description

The add_neighbor command adds a GSM or UTRAN neighbor to an existing cell Neighbor
Cell List.

Addition of TD-SCDMA neighbor cells is only allowed when TD-SCDMA and GSM interworking
feature is enabled (td_enabled set to 1).

The maximum number of TD-SCDMA neighbors per GSM cell is increased from 16 to 32.

A GSM cell can have up to 64 GSM neighbors. A maximum of 64 GSM neighbors can be in the
BA_BCCH list but only 32 can be effective. A maximum of 32 GSM neighbors can be in the
BA_SACCH list and a maximum of 32 GSM neighbors can be in the BA_GPRS list.

The neighbor frequency can change from one range to another (with respect to Table 3-11
and Table 3-12) when adding or deleting a neighbor for a particular source cell. Hence the
maximum number of neighbors that can be added to a source cell can change depending upon
the frequency range of the neighbor cells:
If the source frequency type is DCS1800, a neighbor cannot have a frequency type of
PCS1900. If the source frequency type is PCS1900, a neighbor cannot have a frequency
type of DCS1800.

If a DCS1800 neighbor exists in a neighbor list, no PCS1900 neighbors can be added.

If a PCS1900 neighbor exists in a neighbor list, no DCS1800 neighbors can be added.

Table 3-11 lists the frequency range and maximum number of neighbors for an EGSM or PGSM
source cell.

Table 3-11 Neighbor frequency and number with an EGSM or PGSM source cell

Neighbor frequency
Maximum number of neighbors
range
1 - 124 64
975 - 1023 49
0, 1 - 124 64
0, 975 - 1023 50 if the source frequency is in the EGSM frequency, that is: 0, 975 -
1023
17 if the source frequency is in the PGSM frequency, that is: 1 - 124

Continued

68P02901W23-T 3-35
Jan 2010
Description Chapter 3: Device/function related commands

Table 3-11 Neighbor frequency and number with an EGSM or PGSM source cell
(Continued)
Neighbor frequency
Maximum number of neighbors
range
1 - 124, 975 - 1023 64 if the source frequency is zero, where the number of EGSM
neighbors is less than or equal to 16.
0, 1 - 124, 975 - 1023 64 if the source frequency is in the EGSM frequency range, where
the number of EGSM neighbors is less than or equal to 16.
64 if the source frequency is in the PGSM frequency range, where
the number of EGSM frequencies is less than or equal to 17.
512 - 885 64

Table 3-12 lists the frequency range and maximum number of neighbors for a DCS 1800
source cell.

Table 3-12 Neighbor frequency and number with DCS1800 source cell

Neighbor frequency range Maximum number of neighbors

1 - 124 64
975 - 1023 49
0, 1 - 124 17
0, 975 - 1023 17
1 - 124 and 975 - 1023 16
0, 1 - 124 and 975 - 1023 17
512 - 885 64

The system updates the maximum number of GSM neighbor cells (refer Table 3-11 and
Table 3-12). Then check the maximum number of GSM neighbor cells based on the BA_BCCH
list and BA_SACCH list options provided in the following table.

One or more Max no. of Max no. of

Add neighbor Add neighbor Max no. of
UTRAN neighbor cells neighbor cells
to the BA to the BA GSM neighbor
neighbor that can be that can be
BCCH list SACCH list cells that can
exists equipped for equipped for
(Yes/No)? (Yes/No)? be equipped
(Yes/No)? BA BCCH list BA SACCH list
Yes No 64 -
No No Yes - 32 64
Yes Yes - 32
Yes No 31
Yes No Yes - 31 62
Yes Yes - 31

3-36 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Description

NOTE

If there are no UTRAN BCCH neighbors, a maximum of 64 BCCH neighbors can

be equipped for GSM. Alternatively, if there are one or more UTRAN BCCH
neighbors, a maximum of 31 BCCH neighbors can be equipped for GSM.
If there are no UTRAN SACCH neighbors, a maximum of 32 SACCH neighbors
can be equipped for GSM. Alternatively, if there are one or more UTRAN SACCH
neighbors, a maximum of 31 SACCH neighbors can be equipped for GSM.

For UTRAN neighbor cells, when the Enhanced 2G/3G Handover feature is unrestricted, up to
32 UTRAN BCCH neighbors, 32 UTRAN SACCH neighbors and eight Blind Search neighbors
can be added per cell. A total of 64 UTRAN neighbors can be created but a maximum of 32 can
be on the UTRAN BA_BCCH list only.

After the add_neighbor command is entered, a series of prompts are presented where
parameters defining the GSM or UTRAN neighbor are entered. The prompted parameters are
described in the Related information on page 3-42.

The required input parameters depend on whether the neighbor cell is internal to the BSS or
external to the BSS. The parameters also depend on whether the neighbor is a GSM, UTRAN,
or Blind Search cell.

When the source cell is a PGSM or EGSM cell, the maximum number of EGSM and PGSM band
neighbor cells allowed is restrained (refer Table 3-11).

When the source cell is a DCS1800 or PCS1900 cell, the maximum number of EGSM and PGSM
band neighbor cells allowed is restrained (refer Table 3-12).

If the Inter_RAT (Radio Access Technology) Handover feature and/or Enhanced 2G/3G Handover
feature is unrestricted, this command supports the UTRAN cell identity format.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites To be on the Neighbor Cell List, a cell must be the
destination of handovers from the Neighbor List owner.
Synchronized handovers are allowed only between cells
that are at the same site.
For a PGSM or EGSM site, only external neighbor cells
with BCCH ARFCNs in the 1 - 124 can be added.
For a GSM 850 site, only external neighbor cells with BCCH
ARFCNs in the following ranges can be added: 0 - 124 128
- 251 512 - 885, and 975 - 1023.
For handovers to UTRAN cells, the Inter-RAT Handover
feature and/or the Enhanced 2G/3G Handover feature must
be unrestricted.
Operator action Reply to prompts as displayed, directly or in a script.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

68P02901W23-T 3-37
Jan 2010
Format Chapter 3: Device/function related commands

Format

Syntax

add_neighbor <source_cell_id> <neighbor_cell_id> <placement>

The cell_name can be used for the neighbor when the neighbor is internal.

Input parameters

source_cell_id

GSM cell ID of the cell to which a neighbor cell is to be assigned.

The format for the GSM cell ID depends on:

The system being used (PGSM, EGSM, DCS1800, PCS1900, GSM 850)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

Whether the cell is a UTRAN cell.

The name of the cell created using the cell_name command can be entered in place of the
cell_id. When the cell name is entered, insert within double quotation marks.

Only PCS1900 and GSM 850 systems can use a three-digit MNC.

neighbor_cell_id

GSM cell ID of the cell being assigned as a neighbor cell.

The name of the cell created using the cell_name command can be entered in place of the
cell_id. When the cell name is entered, insert within double quotation marks. The cell_name can
only be entered in place of the neighbor_cell_id for internal neighbor cells.

Only PCS1900 and GSM 850 systems can use a three-digit MNC.

The string test <num> can be entered for this field where <num> is a value from 1 to 64.
This permits test neighbors to be added to the BA_SACCH and/or BA_BCCH lists. When a test
neighbor is added, the value entered in the placement field is ignored and the frequency is the
only prompted parameter.

The system checks the BSIC of the neighbor cell against the ncc_of_plmn value of the source
cell. If they are incompatible, the system rejects the command. See the descriptions for bsic on
page 6-99 and ncc_of_plmn_allowed on page 6-638 for more information.

NOTE
A cell_name cannot be associated with UMTS neighbor.

3-38 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

placement

internal The neighbor cell to be added is inside the BSS.

external The neighbor cell to be added is outside the BSS.
umts_fdd The neighbor cell to be added is a UTRAN BCCH or
SACCH neighbor.
umts_fdd_blind The neighbor cell is a UTRAN Blind Search neighbor.
umts_tdd Specifies that the new neighbor is a TD-SCDMA neighbor.

Table 3-13 Prompted Parameters for TD-SCDMA Neighbors

Prompt Required Value Definition/Range/Default

Enter the UTRAN Absolute Yes 10054 - 10121
Radio Freq Chan Number:
Enter the TD-SCDMA cell Yes 0 - 127
parameter:
Enter the Time Switched No 0 Disabled
Transmit Diversity Flag: 1 Enabled
Default: 0 (Disabled)
Enter the Space Code No 0 Disabled
Transmit Diversity Flag: 1 Enabled
Default: 0 (Disabled)

Examples

Example 1

In this example, a cell with ID 5 4 3 2 1 61986 34945 is added to the Neighbor Cell List of a cell
with ID 5 4 3 2 1 61986 34944. The example demonstrates adding a cell to the Neighbor Cell List
that is internal to that neighbor cell. The word, internal follows the second cell ID indicating
that the cell being added is internal to, and shares the same BSS of the src_gsm_cell_id.

add_neighbor 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 internal

Where: is:
5 4 3 2 1 61986 34944 source_cell_id
5 4 3 2 1 61986 34945 neighbor_cell_id
internal placement

68P02901W23-T 3-39
Jan 2010
Examples Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED

After verification of the command, the MMI prompts for the required parameters to describe the
neighbor cell being added (see Table 3-14 in Related information).

Example 2

In this example, a cell with ID 5 4 3 2 1 61986 34944 is added to the Neighbor Cell List of a cell
with ID 5 4 3 2 1 71543 12444. The example demonstrates adding a cell to the Neighbor Cell List
that is external to that neighbor cell. The word, external follows the second cell ID indicating
that the cell being added is external to, and does not share the BSS of the src_gsm_cell_id.

add_neighbor 5 4 3 2 1 71543 12444 5 4 3 2 1 61986 34944 external

Where: is:
5 4 3 2 1 71543 12444 source_cell_id
5 4 3 2 1 61986 34944 neighbor_cell_id
external placement

System response

COMMAND ACCEPTED

After verification of the command, the MMI prompts for the required parameters to describe the
neighbor cell being added (see Table 3-14 in Related information).

Example 3

In this example, a cell with ID 5 4 3 2 1 61986 34945 is added to the internal Neighbor Cell List
of a cell with the cell name north-london:

add_neighbor north-london 5 4 3 2 1 61986 34945 internal

Where: is:
north-london source_cell_name
5 4 3 2 1 61986 34945 neighbor_id
internal placement

System response

COMMAND ACCEPTED

After verification of the command, the MMI prompts for the required parameters to describe the
neighbor cell being added (see Table 3-14 in Related information).

3-40 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 4

In this example, a PCS1900 cell with ID 543 721 61986 34945 is added to the internal Neighbor
Cell List of a cell with ID 543 721 61986 34944:

add_neighbor 543 721 61986 34944 543 721 61986 34945 internal

Where: is:
543 721 61986 34944 source_cell_id
543 7211 61986 34945 neighbor_cell_id
internal placement

System response

COMMAND ACCEPTED

After verification of the command, the MMI prompts for the required parameters to describe the
neighbor cell being added (see Table 3-14 in Related information).

Example 5

In this example, UTRAN cell ID 4 9 6 2 3 1 1 1 1 is specified as a neighbor of GSM cell ID 0 0 1 0

1 1 4 with all values entered for all parameters.

add_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_fdd

Where: is:
0010114 GSM cell ID
496231111 neighbor cell ID
umts_fdd placement

System response

Add neighbor to UTRAN BCCH list (Yes/No)? Yes

Add neighbor to UTRAN SACCH list (Yes/No)? Yes
Enter the UTRAN Absolute Radio Freq Chan Number: 10762
Enter the Scrambling Code: 200
Enter the Diversity Enabled Flag: 1
Enter the UMTS measurement margin: 15
Enter the neighbor measurement avg period: 10
COMMAND ACCEPTED

68P02901W23-T 3-41
Jan 2010
References Chapter 3: Device/function related commands

Example 6

In this example, the FDD_ARFCN 10755 is specified as a UTRAN Blind Search neighbor of
GSM cell 0 0 1 0 1 1 4.
add_neighbor 0 0 1 0 1 1 4 umts_fdd_blind

Where: is:
0010114 GSM cell ID
umts_fdd_blind placement type

System response

Enter the UTRAN Absolute Radio Freq Chan Number: 10755

COMMAND ACCEPTED

Example 7

This example specifies TD-SCDMA cell 4 9 6 3 2 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4

with all values entered for all parameters when TD-SCDMA inter-working is enabled.

add_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_tdd

Where: is:
0010114 GSM cell ID
496231111 neighbor cell ID
umts_tdd placement type

System response

Enter the UTRAN Absolute Radio Freq Chan Number: 10110

Enter the TD-SCDMA cell parameter: 100
Enter the Time Switched Transmit Diversity Flag: 1
Enter the Space Code Transmit Diversity Flag: 1
COMMAND ACCEPTED

References

Related information

There is a time limit of 30 seconds in which to enter responses to the parameter prompts
that are presented. If a proper response is not entered within the time limit, the command is
abandoned and all values entered up to that point are lost.

Table 3-14 lists the add_neighbor command prompts for GSM BA BCCH and SACCH neighbors.

3-42 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 3-14 add_neighbor command prompts for GSM BA BCCH and SACCH
neighbors.

Prompt Range Default Notes

Add neighbor to the BA yes yes
BCCH list (yes/no)? no These three prompts
appear only if the Network
Add neighbor to the BA yes yes
Controlled Cell Reselection
SACCH list (yes/no)? no
feature (NCCR) is
Add neighbor to the yes yes unrestricted.
BAGPRS list (yes/no)? no
Enter the neighbor cell pgsm, egsm, None N/A for internal neighbors.
frequency type: dcs1800,
pcs1900,
gsm850.
Enable synchronization: 1 (Yes) 0 N/A for external neighbors
0 (No)
Enter the BCCH frequency 1 - 124 for None N/A for internal neighbors.
number: PGSM, A value MUST EGSM BCCH frequencies
0 1 - 124, be entered at 0, 975 - 1023 are not
975 - 1023 for this prompt. available when the
EGSM, egsm_bcch_sd parameter
512 - 885 for is disabled.
DCS1800,
512 - 810 for
PCS1900.
Enter base station 0 - 63 None N/A for internal neighbors
identity code (bsic): A value MUST
be entered at
this prompt.
Enter MS transmit power 5 - 39 (odd 39 for PGSM N/A for internal neighbors
maximum: values only) and EGSM.
for PGSM and 36 for
EGSM, DCS1800
0 - 36 (even 33 for
values only) for PCS1900.
DCS1800,
0 - 32 (even
values only)
and 33, for
PCS1900.
Enter neighbor receive 0 - 63 rxlev_min_def Required for external
level minimum: of neighbor neighbors
cell
Enter neighbor handover -63 to 63 ho_margin_def Required for external
margin: of neighbor neighbors.
cell Refer to the description
of the ho_margin_def
parameter.
Enter the power budget 1 - 31 8
surrounding cell hreqave:

Continued

68P02901W23-T 3-43
Jan 2010
References Chapter 3: Device/function related commands

Table 3-14 add_neighbor command prompts for GSM BA BCCH and SACCH
neighbors. (Continued)
Prompt Range Default Notes
Enable adjacent channel 1 (Yes) 0 (No) N/A if Microcell is not
interference avoidance 0 (No) purchased.
test?:
Enter rxlev difference -63 to 63 0 N/A if Microcell is not
for adjacent channel purchased.
interference avoidance This prompt applies if
test: previous answer is 1
Enter the power budget 1-7 1 N/A if Microcell is not
algorithm type: purchased.
Enter the adjacent -63 to 63 ho_margin_cell This prompt only appears
channel interference if pbgt_alg_type=7.
detection handover
margin:
Enter the uplink receive 0 - 255 None N/A if Microcell is not
level threshold of the A value MUST purchased and
serving cell: be entered at pbgt_alg_type 0 3
this prompt.
Enter the downlink 0 - 255 None N/A if Microcell is not
receive level threshold purchased and
of the serving cell: pbgt_alg_type 0 3
Enter the qualifying time 0 - 255 0 SACCH N/A if Microcell is not
threshold: periods purchased and
pbgt_alg_type 0 4
Enter the qualifying 0 - 255 0 SACCH N/A if Microcell is not
delay time: periods purchased and
pbgt_alg_type 0 5
Enter the neighbor cell 0 - 63 None N/A if Microcell is not
receive level threshold: A value MUST purchased and
be entered at pbgt_alg_type 0 5
this prompt.
Enter the delay time: 0 - 255 0 SACCH N/A if Microcell is not
periods purchased and
pbgt_alg_type 0 6
Enter the handover static 0 - 127 0 N/A if Microcell is not
offset: purchased and
pbgt_alg_type 0 6
Enter the handover 0 - 127 0 N/A if Microcell is not
dynamic offset: purchased and
pbgt_alg_type 0 6

Continued

3-44 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 3-14 add_neighbor command prompts for GSM BA BCCH and SACCH
neighbors. (Continued)
Prompt Range Default Notes
Enter neighbor congestion -63 to 63 None. A value Value must be less
handover margin: To disable MUST be than or equal to the
congestion entered at this ho_margin_cell of the
handovers to prompt. neighbor cell.
this neighbor, This prompt is only
set the value to presented if directed
63 retry or congestion relief is
purchased.
Is directed retry allowed 1 (Yes) 1 N/A when adding internal
at this external neighbor 0 (No) neighbors.
cell?: This prompt is only
presented if directed
retry or congestion relief is
purchased.
Does this neighbor 1 (Yes) 0 Only prompted if
have a carrier with an 0 (No) inner_zone_alg for the
interfering frequency? source cell is set to 2,
and the neighbor is being
added to the SACCH list.
Enter the threshold for 0 - 63 0 Only prompted if Does
inner zone handover: the neighbor have a
carrier with an interfering
frequency? = 1 (yes).
Enter the margin for 0 - 63 0 Only prompted if Does
inner zone handover: the neighbor have a
carrier with an interfering
frequency? = 1 (yes).
Enter the range of the normal Normal This prompt is only
neighbor cell: extended presented if the Extended
Range Cells feature is
unrestricted.

Table 3-15 lists the add_neighbor command prompted parameters for UTRAN BCCH and SACCH
neighbors. If the Enhanced 2G-3G feature is restricted, these parameters are not prompted.

Table 3-15 add_neighbor command prompts for UTRAN BCCH and SACCH
neighbors

Prompt Range Default Notes

Add neighbor to UTRAN BCCH
list (Yes/No)?
Add neighbor to UTRAN SACCH
list (Yes/No)?
Yes or No Yes The values of the BCCH
and SACCH prompts
determine the value of
Yes or No Yes
the umts_ba_type attribute
where:
BCCH/SACCH is Yes/No 1,
BCCH/SACCH is No/Yes 2,
BCCH/SACCH is Yes/Yes 3.

Continued

68P02901W23-T 3-45
Jan 2010
References Chapter 3: Device/function related commands

Table 3-15 add_neighbor command prompts for UTRAN BCCH and SACCH
neighbors (Continued)
Prompt Range Default Notes
Enter the UTRAN Absolute 10562 - 10838 None This sets the fdd_arfcn
Radio Freq Chan Number: attribute.
Enter the Scrambling Code: 0 - 511 None This sets the scr_code
attribute that indicates the
primary scrambling code of
the UTRAN neighbor.
Enter the Diversity Enabled 0 or 1 0
Flag:
Enter the UMTS measurement 0 - 20 3 This sets the
margin: umts_meas_margin
parameter used by the
handover algorithm.
Enter the neighbor 1 - 12 6 This sets the UTRAN
measurement avg period: neighbor cell measurement
averaging period
umts_ncell_avg_period
attribute.

Table 3-16 lists the add_neighbor command prompted parameters for Blind Search neighbors.
Table 3-16 add_neighbor command prompts for Blind Search neighbors.

Prompt Range Default Notes

Enter the UTRAN Absolute 10562 - 10838 None This sets the
Radio Freq Chan Number bs_fdd_arfcn blind
search neighbor
attribute.
This is not prompted
for if the Enhanced
2G-3G feature is
restricted.

When adding UTRAN neighbors, checks are made to ensure the maximum number of UTRAN
BCCH and SACCH neighbors has not been reached, the maximum number of UTRAN BCCH
and SACCH neighbors per FDD_ARFCN has not been reached and the maximum number of
FDD-ARFCN per GSM cell has not been reached.

Related commands

add_cell on page 3-22 copy_cell on page 3-199 del_cell on page 3-212

del_neighbor on page 3-217 disp_cell on page 3-261 disp_gsm_cells on page 3-350
disp_neighbor on page 3-379 modify_neighbor on page
3-498

3-46 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference add_nsvc

add_nsvc

Description

The add_nsvc command enables the operator to map a Network Service-Virtual Connection
Identifier (NSVCI) and Data Link Connection Identifier (DLCI) to a specific GBL.

{26638} The BSC will support to add IP based NSVC if gb_mode is set to static IP mode, and
support to add frame relay NSVC if gb_mode is set to frame relay mode.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator action)
Prerequisites The GPRS feature must be unrestricted.

Format

Syntax

{26638}

add_nsvc <pcu_n> <ns_vci> <gbl_id> <dlci> if gb_mode is in frame relay mode.

add_nsvc <pcu_n> <ns_vci> <gbl_id> if gb_mode is in static IP mode.

Input parameters

pcu_n pcu or pcu_0 The PCU at which the NSVCI or DLCI is to be

mapped to the specific GBL.
ns_vci 0 - 65535 The virtual connection on a GBL
Unique identifier of the NSVCI mapping and
identifier of the object.
gbl_id 0 - 35 Object identifier of the GBL
dlci 16 - 991 Local identifier for a virtual connection on a GBL.

Prompts are then displayed as follows:

Enter the Committed Information rate:

Enter the Committed Burst Size:
Enter the Burst Excess:

68P02901W23-T 3-47
Jan 2010
Example Chapter 3: Device/function related commands

{26638} Prompts are displayed as follows:

#If <Gb over IP feature unrestricted and gb_mode set to 'Static IP' mode> then:

Prompt Required Value Definition/Range/Default

--------- --------- ------------------

Enter the SGSN side Yes IPv4 address of remote IP endpoint,

IP Address: Class A/B/C IPv4 address except loopback
127.x.x.x, no default.

Enter the SGSN side Yes UDP port of remote IP endpoint, Range
UDP port: 1024-65535,no default.

Enter the SGSN side Yes Signaling weight associated with remote
signaling weight: IP endpoint, Range 0-255,no default.

Enter the SGSN side Yes Date weight associated with remote
data weight: IP endpoint, Range 0-255,no default.

#End If

Example

Example 1

The following example adds NSVCI 10 to GBL 0 with a DLCI of 50 on PCU 0:

add_nsvc pcu_0 10 0 50

Where: is:
pcu_0 PCU 0
10 NSVC
0 GBL ID
50 DLCI

System response

Enter the Committed Information Rate:150

Enter the Committed Burst Size:300
Enter the Burst Excess:400

COMMAND ACCEPTED

3-48 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 2

{26638}

This example adds the NSVC 1 to GBL 0 with the remote IP endpoint 200.30.0.1:1099, signaling
weight 0 and data weight 50. The gb_mode parameter is set to static IP mode.

add_nsvc pcu 1 0

Where: is:
pcu location
1 NSVC
0 GBL ID

System response

Enter the SGSN side IP Address: 200.30.0.1

Enter the SGSN side UDP port: 1099
Enter the SGSN side signaling weight: 0
Enter the SGSN side data weight: 50

COMMAND ACCEPTED

References

Related commands

del_nsvc on page 3-222 mod_nsvc on page 3-495

68P02901W23-T 3-49
Jan 2010
add_rtf_path Chapter 3: Device/function related commands

add_rtf_path

Description

The add_rtf_path command allows the addition of a redundant PATH device to an equipped
RTF function in the CM database.

The parameters that identify a particular PATH are location and Unique_PATH_identifier. Adding
a redundant path that is shorter than the current path causes a switch to the shorter path.

If an RTF path is being added to an RTF with multiplexed 16 k RSLs the system prompts for
the identifier of the associated RSL.

The system rejects attempts to modify the PATHs used by RTFs at sites that use dynamic
allocation. RTFs automatically use the PATHs defined for these types of sites. RTFs do not use
PATHs equipped by the operator for these types of sites.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator action)
Prerequisites This command can only be executed at the BSC.
If no redundant PATH is equipped, then first equip any
necessary MSI before equipping the PATH.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

add_rtf_path <location> <1st_RTF_identifier> <2nd_RTF_identifier>

<unique_PATH_identifier>

3-50 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Input parameters

location

Indicates the number of the BTS where the RTF is located. The range of values is 0 to 140.

1st_RTF_identifier

Specifies the first RTF identifier. The range of values is:

2nd_RTF_identifier

Specifies the second RTF identifier. The range of values is:

0 to 11 for InCell.

0 or 1 for M-Cell.

unique_PATH_identifier

Specifies the unique PATH to a particular site. The range of values is 0 to 9.

Example

This example adds a redundant RTF PATH to site 3, RTF identifiers 2 1, unique PATH identifier 1.

add_rtf_path 3 2 1 1

Where: is:
3 location
2 1st_RTF_identifier
1 2nd_RTF_identifier
1 unique_PATH_identifier

System response

COMMAND ACCEPTED

References

Related commands

copy_path on page 3-207 del_rtf_path on page 3-224 disp_rtf_path on page 3-422

disp_traffic on page 3-436

68P02901W23-T 3-51
Jan 2010
alarm_mode Chapter 3: Device/function related commands

alarm_mode

Description

The alarm_mode command registers or deregisters the MMI to receive device,

non-reconfiguration type, and statistical alarm reports for the specified sites. If no mode is
specified, this command displays whether alarms are enabled or disabled. If the location is
specified as all from a BSC, alarms for all sites are affected (either displayed, enabled, or
disabled).

Security level 1
Supported by OMC-R GUI No
Command type A (no operator action)
Prerequisites The GPRS must be unrestricted to assess a PCU site.

Format

Syntax

alarm_mode <location>[<location>,<location>] [<mode>]

Input parameters

location

Specifies the site location:

0 or bsc BSC
0 - 140 BTS
pcu or pcu_0 PCU

mode

on alarm reporting activated

off alarm reporting deactivated

3-52 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

Specifies alarm mode as On for BSC 0:

alarm_mode 0 on

System response

SITE MODE
----- -----------------------
0 Alarm reporting enabled

Example 2

Specifies alarm mode as Off for PCU site 0:

alarm_mode pcu_0 off

System response

SITE MODE
----- ------------------------
pcu_0 Alarm reporting disabled

68P02901W23-T 3-53
Jan 2010
assess Chapter 3: Device/function related commands

assess

Description

The assess command displays different types of information, depending on whether a SITE
or device is specified, as follows:

SITE

When a site is specified, information on the status of Functional Units (FUs) and which device
types contribute to that status is reported. The information is presented in a concise format that
indicates where problems are and what must be done. Only the FUs and device types which have
non-CLEAR status are listed. Complete device IDs are not listed. The FU statuses are defined as:

MAJOR = Loss of Capacity.

MINOR = Loss of Redundancy.

CRITICAL = Loss of Service.

Device

A device can be specified individually, with wild cards, or for all sites. When multiple devices
and/or functions have gone OOS (Out Of Service) as part of separate reconfigurations, multiple
reports are generated.

If multiple reports are generated as part of a single assess command, one report is generated
for each active reconfiguration that satisfies the request. For the purposes of this command,
active means any reconfiguration with:
One or more alarms active against it.

One or more devices still OOS.

Both active alarms and OOS devices.

Only one report is displayed if wild cards are used and all devices that match the wild cards
go OOS as part of the same reconfiguration.

Functions are not displayed as an OOS device because there is no maintenance action to
perform on a function. Once all devices are restored to an in-service state, the functions must
be assigned to the appropriate devices and cease to affect the FUs.

Device reports are displayed in the following format:

Alarm Device:
of :
Cause: Outcome:
Functional Unit:
-- Status: Current Status:
-- OOS Devices Affecting Functional Unit:

3-54 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

The Alarm Device is the primary alarm for the reconfiguration. The alarm is displayed even if it
has been cleared already. An alarm and the alarm device are not displayed for a reconfiguration
that does not have an active alarm yet has OOS devices. However, the message No Primary
Alarm for this Reconfiguration is displayed.

A Functional Unit (and its status) is displayed for each FU which is impacted by the
reconfiguration and has a non-CLEAR status at the end of the reconfiguration.

The line, OOS Devices Affecting Functional Unit, displays when devices are OOS and are
still associated with this reconfiguration. For each device impacting the listed FU, the device ID
and state are listed one per line.

If the FU no longer has any OOS devices impacting it, the line, No devices remain OOS as a
result of this configuration is displayed instead of the previous line.

NOTE
This report does not list a config_tag or a time stamp. This information can be
displayed with either the state or disp_act_alarm command.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator action)
Prerequisites The GPRS feature must be unrestricted to assess a PCU
site.

Format

Syntax

assess <location> [all] [<dev/func name> <dev/func id> <dev/func id>] [*]

Input parameters

location

Specifies the site location:

0 or bsc BSC
0 - 140 BTS
pcu or pcu_0 PCU
all All active sites

68P02901W23-T 3-55
Jan 2010
Examples Chapter 3: Device/function related commands

dev/func name

Specifies the device or function.

dev/func id

Specifies the ID for the device or function. The system accepts the wildcard character (*) for
the device or function ID.

Examples

Example 1

In the following example, BSC has been initialized. The operator wishes to see if there are
any problems at the BSC:

assess 0

Where: is:
0 location

System response

SITE / CELL DEVICE/FUNCTION SEVERITY

------------------------ --------------- --------------------------
SITE 0 MAJOR (Loss of Capacity)
BSP MAJOR (Loss of Capacity)
OML MAJOR (Loss of Capacity)
CBUS MINOR (Loss of Redundancy)
SITE 3 MAJOR (Loss of Capacity)
RSL MAJOR (Loss of Capacity)
CELL 001 01 1 2 MINOR (Loss of Redundancy)
DRI MINOR (Loss of Redundancy)

Example 2

In the following example, the operator is concerned about the OMLs contributing to the severity
of MAJOR. In this particular scenario, both OMLs have been OOS since site initialization:

assess 0 oml 0

Where: is:
0 location
oml device name
0 device ID

3-56 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

ASSESS REPORT BEGIN

(242) Device(s) OOS due to action on this device
Alarm Device: SITE 0 0 0
ENABLE of SITE: 0 0 0
Cause: INITIALIZATION Outcome: Alarm
Functional Unit: SITE 0
-- Status: MAJOR Current Status: MAJOR
-- OOS Devices Affecting Functional Unit:
OML 0 0 0 DISABLED UNLOCKED MMS Not In Service
OML 0 0 0 DISABLED UNLOCKED MMS Not In Service
Functional Unit: SITE 3
-- Status: MINOR Current Status: MAJOR
-- No devices remain OOS as a result of this configuration
Functional Unit: CELL 001 01 1 2
-- Status: MAJOR Current Status: MINOR
-- OOS Devices Affecting Functional Unit:
DRI 1 4 0 DISABLED UNLOCKED DRI Not Detected
ASSESS REPORT COMPLETE

Example 3

The following example shows an assess display for PCU site 0:

assess pcu_0

Where: is:
pcu_0 location

System response

SITE / CELL DEVICE/FUNCTION SEVERITY

------------------------------------- --------------- ---------
PCU 0 CRITICAL
GBL CRITICAL
GSL MAJOR
DPROC MAJOR
MSI MAJOR
COMMAND ACCEPTED

68P02901W23-T 3-57
Jan 2010
cage_audit Chapter 3: Device/function related commands

cage_audit

Description

The cage_audit command performs two different functions. The first function allows the
execution of safe tests or all audits for all the devices within a specific cage. The second function
permits the suspension or resumption of all audits at a specific site.

There are only two possible System Responses to a cage_audit command:

The display of results.

ERROR.

The ERROR response is due to a non-device related cause. An error description is also displayed.

Devices listed within the CAGE can also generate messages specific to the device.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

NOTE
This command does not work at an M-Cell site. Contact the OMC-R for help.

Format

Syntax

cage_audit <location> <audit_type> <cage_number>

cage_audit <location> <control> <cage_number>

3-58 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Input parameters

location

Specifies the audit location:

0 or bsc BSC
0 - 140 BTS
pcu or pcu_0 PCU

audit_type

Specifies the type of audit:

safe initiates safe tests

All initiates all audits

control

Specifies the audit status:

on Resumes all site audits within a cage at a specific site.

off Suspends all site audits within a cage at a specific site.

cage_number

Specifies the cage number:

0 - 13 for a BSC
2 - 15 for a BTS

Examples

Example 1

This example executes all audits for all devices for cage 0 at site 0.

cage_audit 0 all 0

Where: is:
0 location
all audit_type
0 cage_number

68P02901W23-T 3-59
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Device: KSW Device id: 0 0 0

Year: 1994 Month: 11 Day: 12 Hour: 0 Min: 26 Sec: 26 MSec: 495
Audit Type: SAFE Result: PASS
Device: KSW Device id: 0 0 0
Year: 1994 Month: 11 Day: 12 Hour: 0 in: 26 Sec: 27 MSec: 860
Audit Type: INT LPBK Result: PASS
Device: MSI Device id: 3 0 0
Year: 1994 Month: 11 Day: 12 Hour: 0 Min: 26 Sec: 28 MSec: 630
Audit Type: SAFE Result: PASS
Device: MSI Device id: 1 0 0
Year: 1994 Month: 11 Day: 12 Hour: 0 Min: 26 Sec: 29 MSec: 665
Audit Type: SAFE Result: PASS
Device: DRI Device id: 0 1 0
Year: 1994 Month: 11 Day: 12 Hour: 0 Min: 26 Sec: 29 MSec: 665
Audit Type: SAFE Result: PASS
Device: GPROC Device id: 1 0 0
Year: 1994 Month: 11 Day: 12 Hour: 0 Min: 26 Sec: 31 MSec: 595
Audit Type: SAFE Result: ERROR
ERROR: Audit not available for this device.

Example 2

The following example suspends audits for all devices in cage 9 at site 4:

cage_audit 4 off 9

Where: is:
4 location
off control
9 cage_number

System response

COMMAND ACCEPTED

3-60 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related commands

chg_audit_sched on page 3-76 device_audit on page 3-230 query_audits on page 3-532

site_audit on page 3-568

68P02901W23-T 3-61
Jan 2010
cell_name Chapter 3: Device/function related commands

cell_name

Description

The cell_name command assigns a unique name to a Cell ID, renames a cell, or displays the
name assigned to a Cell ID. The name can be a text string up to 31 alphanumeric characters in
length, including dash characters used for separation.

The system does not permit duplicate cell names to be entered.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites A security level of 2 is required to create or modify a cell
name.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

cell_name <gsm_cell_id> [<cell_name>]

Input parameters

gsm_cell_id

The GSM cell ID of the cell for which the cell name is to be created, displayed, or modified.

The format for the GSM cell ID depends on is:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

3-62 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

cell_name

The name to be assigned to the Cell ID. The cell name must be entered inside double quotation
marks.

The cell name can be from one to 31 alphanumeric characters. The dash character can be used
as a separator. The underscore character cannot be used as part of the name or as a separator.
Double quotation marks cannot be used as part of a cell name.

Cell names must not be equivalent to the following character strings in upper or lower case:
all

no name defined

name not available

Entering two consecutive double quotation marks removes the current cell name.

If no value is entered for this parameter, the current cell name displays.

Examples

Example 1

In this example, the Cell ID 5 4 3 2 1 61986 34944 is assigned the cell name london-west.

cell_name 5 4 3 2 1 61986 34944 london-west

Where: is:
5 4 3 2 1 61986 34944 cell_number
london-west cell_name

System response

COMMAND ACCEPTED:

Example 2

In this example, the cell name assigned to Cell ID 5 4 3 2 1 61986 34944 displays. The
cell_name displays inside double quotes.

cell_name 5 4 3 2 1 61986 34944

Where: is:
5 4 3 2 1 61986 34944 cell_number

68P02901W23-T 3-63
Jan 2010
Examples Chapter 3: Device/function related commands

System response

GSM Cell [ 5 4 3 2 1 61986 (f222h) 34944 (8880h) ] = london-west

NOTE
If there is no cell name, the system response is:

No textual name exists for this cell

Example 3

In this example, the existing cell name london-west is removed.

cell_name 5 4 3 2 1 61986 34944

Where: is:
5 4 3 2 1 61986 34944 cell_number
cell_name

System response

COMMAND ACCEPTED

Example 4

In this example, the PCS1900 Cell ID 543 721 61986 34944 is assigned the name london-west.

cell_name 543 721 61986 34944 london-west

Where: is:
543 721 61986 34944 cell_number
london-west cell_name

System response

COMMAND ACCEPTED

3-64 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference chg_acs_params

chg_acs_params

Description

The chg_acs_params command specifies up to four codec modes to be used in the Active Codec
Set (ACS), the initial codec mode, and the uplink and downlink adaptation threshold, and
hysteresis values for Full Rate (FR), Half Rate (HR), or both.

The term Active Codec Set refers to the set of up to four Adaptive Multi-Rate (AMR) code
modes and related thresholds, and hysteresis that can be used for any given voice call in the
uplink and downlink directions. The operator configures the ACS on a per cell basis.

There are two sets of thresholds and hysteresis per ACS; one for downlink codec mode
adaptation and one for uplink codec mode adaptation. The threshold is used as the lower
decision threshold for switching between the codec modes. The sum of the threshold and the
hysteresis constitutes the upper threshold between the codec modes.

There is a separate ACS for Full Rate and Half Rate.

The term Adaptive Multi-Rate codec refers to the speech and channel codec capable of
operating at gross bit-rates of 11.4 kbits/s (Half-Rate) and at 22.8 kbits/s (Full Rate) over the air
interface. Plus, the codec can operate at various combinations of speech and channel coding
(codec mode) bit-rate for each channel mode.

Security level 4
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites The AMR feature must be unrestricted.
The site must be an AMR-capable BTS.
Dependencies Either AMR Full-Rate or Half-Rate must be enabled in the
cell for the AMR parameters to come into effect.
Parameters can be set before or after the AMR is enabled
in the cell. Thus performance is optimized for calls initiated
in the cell.

Format

Syntax

chg_acs_params <mode> <cell_number=>

The system responds with a series of prompts for threshold and hysteresis values (see Table 3-20
and Table 3-21).

68P02901W23-T 3-65
Jan 2010
Format Chapter 3: Device/function related commands

NOTE
The sum of the values for threshold and hysteresis must be less than 63.

Input parameters

mode

This parameter specifies the rate where:

0 = Full Rate

1 = Half Rate

2 = Both Rates

cell_number=

This parameter is the GSM cell ID of the cell to be changed.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

Only PCS1900 systems can use a three-digit MNC.

The codec mode values and associated rates are listed in Table 3-17:

Table 3-17 Codec Mode Values / Rates

Codec Mode Value Associated Rate

0 12.20 kbit/s
1 10.20 kbit/s
2 7.95 kbit/s
3 7.40 kbit/s

4 6.70 kbit/s
5 5.90 kbit/s
6 5.15 kbit/s

Full Rate attribute values for the chg_acs_params command are listed in Table 3-18, and the
Half Rate attribute values are listed in Table 3-19.

NOTE
The range values 0 - 63 and 0 - 15 in Table 3-18 and Table 3-19 are in steps of 0.5 dB.

3-66 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Table 3-18 Full Rate attribute values for chg_acs_params command

Attribute Range Default Notes

amr_fr_acs 0, 1, 3, 0, 1, 3, 6 Up to four AMR codec modes
4, 6 which can be used for any
given voice call in the uplink
or downlink direction.
amr_fr_initial_codec_mode 0, 1, 3, 1 Codec mode used at the
4, 6 beginning of a call. If one
mode is entered for the Full
Rate ACS, then the Full Rate
Initial Codec Mode defaults to
this value (if valid).
amr_fr_uplink_threshold3 0 - 63 26 Lower Full Rate uplink
amr_fr_uplink_threshold2 0 - 63 20 decision threshold for
amr_fr_uplink_threshold1 0 - 63 14 switching from one mode
to another.
amr_fr_uplink_hysteresis3 0 - 15 1 The sum of the associated
amr_fr_uplink_hysteresis2 0 - 15 1 threshold and hysteresis is
amr_fr_uplink_hysteresis1 0 - 15 1 used as the upper decision
threshold for switching the
codec mode.
amr_fr_downlink_threshold3 0 - 63 30 Lower Full Rate downlink
amr_fr_downlink_threshold2 0 - 63 24 decision threshold for
amr_fr_downlink_threshold1 0 - 63 19 switching from one mode
to another.
amr_fr_downlink_threshold3 0 - 15 1 The sum of the associated
amr_fr_downlink_threshold2 0 - 15 1 threshold and hysteresis is
amr_fr_downlink_threshold1 0 - 15 1 used as the upper decision
threshold for switching the
codec mode.
amr_fr_uplink_threshold3_hopping 0 - 63 26 Uplink switching thresholds
amr_fr_uplink_threshold2_hopping 0 - 63 20 applied to frequency hopping
amr_fr_uplink_threshold1_hopping 0 - 63 14 channels.
amr_fr_uplink_hysteresis3_hopping 0 - 15 1 Uplink hysteresis applied to
amr_fr_uplink_hysteresis2_hopping 0 - 15 1 frequency hopping channels.
amr_fr_uplink_hysteresis1_hopping 0 - 15 1
amr_fr_downlink_threshold3_hopping 0 - 63 26 Downlink switching thresholds
amr_fr_downlink_threshold2_hopping 0 - 63 21 applied to frequency hopping
amr_fr_downlink_threshold1_hopping 0 - 63 14 channels.
amr_fr_downlink_hysteresis3_hopping 0 - 15 1 Downlink hysteresis applied to
amr_fr_downlink_hysteresis2_hopping 0 - 15 1 frequency hopping channels.
amr_fr_downlink_hysteresis1_hopping 0 - 15 1

68P02901W23-T 3-67
Jan 2010
Format Chapter 3: Device/function related commands

Table 3-19 Half Rate attribute values for chg_acs_params command

Attribute Range Default Notes

amr_hr_acs 2, 3, 4, 3, 5, 6 Up to four AMR codec modes
5, 6 which can be used for any
given voice call in the uplink
or downlink direction.
amr_hr_initial_codec_mode 2, 3, 4, 5 Codec mode used at the
5, 6 beginning of a call. If one
mode is entered for the Half
Rate ACS, then the Half Rate
Initial Codec Mode defaults to
this value (if valid).
amr_hr_uplink_threshold3 0 - 63 28 Lower Half Rate uplink
amr_hr_uplink_threshold2 0 - 63 22 decision threshold for
amr_hr_uplink_threshold1 0 - 63 switching from one mode
to another.
amr_hr_uplink_hysteresis3 0 - 15 1 The sum of the associated
amr_hr_uplink_hysteresis2 0 - 15 1 threshold and hysteresis is
amr_hr_uplink_hysteresis1 0 - 15 used as the upper decision
threshold for switching the
codec mode.
amr_hr_downlink_threshold3 0 - 63 30 Lower Half Rate downlink
amr_hr_downlink_threshold2 0 - 63 24 decision threshold for
amr_hr_downlink_threshold1 0 - 63 switching from one mode
to another.
amr_hr_downlink_threshold3 0 - 15 1 The sum of the associated
amr_hr_downlink_threshold2 0 - 15 1 threshold and hysteresis is
amr_hr_downlink_threshold1 0 - 15 used as the upper decision
threshold for switching the
codec mode.
amr_hr_uplink_threshold3_hopping 0 - 63 28 Uplink switching thresholds
amr_hr_uplink_threshold2_hopping 0 - 63 22 applied to frequency hopping
amr_hr_uplink_threshold1_hopping 0 - 63 channels.
amr_hr_uplink_hysteresis3_hopping 0 - 15 1 Uplink hysteresis applied to
amr_hr_uplink_hysteresis2_hopping 0 - 15 1 frequency hopping channels.
amr_hr_uplink_hysteresis1_hopping 0 - 15
amr_hr_downlink_threshold3_hopping 0 - 63 30 Downlink switching thresholds
amr_hr_downlink_threshold2_hopping 0 - 63 23 applied to frequency hopping
amr_hr_downlink_threshold1_hopping 0 - 63 channels.
amr_hr_downlink_hysteresis3_hopping 0 - 15 1 Downlink hysteresis applied to
amr_hr_downlink_hysteresis2_hopping 0 - 15 1 frequency hopping channels.
amr_hr_downlink_hysteresis1_hopping 0 - 15

Full Rate prompts for the chg_acs_params command are listed in Table 3-20, and the Half Rate
prompts are listed in Table 3-21.

3-68 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Table 3-20 Full Rate prompts for the chg_acs_params command

Prompt Required Value Definition Conditions

Enter AMR Full Rate Yes Up to four codec mode Prompt displays if the AMR
active codec set: values (codec rates) feature is unrestricted, the
are entered in order BTS type is AMR-capable, and
of descending bit-rate the mode specified is 0 or 2.
(ascending field value 0
- 7, see Table 3-17).
Enter AMR Full Rate Yes The value must be one Prompt displays if the ACS
initial codec mode: of the rates included in contains more than one codec
the Active Codec Set. mode.
Enter AMR Full Rate Yes Enter up to three Prompt displays if the ACS
uplink adaptation uplink threshold values contains more than one codec
thresholds: in order of descending mode.
C/I estimation. One uplink value for each
adjacent pair of codec modes
in ACS.
Enter AMR Full Rate Yes Enter up to three uplink Prompt displays if the ACS
uplink adaptation hysteresis values. contains more than one codec
hysteresis: mode.
One uplink value for each
adjacent pair of codec modes
in ACS.
Enter AMR Full Rate Yes Enter up to three Prompt displays if the ACS
downlink adaptation downlink threshold contains more than one codec
thresholds: values in order mode.
of descending C/I One downlink value for each
estimation. adjacent pair of codec modes
in ACS.
Enter AMR Full Rate Yes Enter up to three Prompt displays if the ACS
downlink adaptation downlink hysteresis contains more than one codec
hysteresis: values. mode.
One downlink value for each
adjacent pair of codec modes
in ACS.
Enter AMR Full Rate Yes Enter up to three Prompt displays if the ACS
uplink adaptation values. contains more than one codec
thresholds for mode.
frequency hopping: One value for each adjacent
pair of codec modes in ACS.
Enter AMR Full Rate Yes Enter up to three Prompt displays if the ACS
uplink adaptation values. contains more than one codec
hysteresis for mode.
frequency hopping: One value for each adjacent
pair of codec modes in ACS.
Enter AMR Full Rate Yes Enter up to three Prompt displays if the ACS
downlink adaptation values. contains more than one codec
thresholds for mode.
frequency hopping: One value for each adjacent
pair of codec modes in ACS.

Continued

68P02901W23-T 3-69
Jan 2010
Format Chapter 3: Device/function related commands

Table 3-20 Full Rate prompts for the chg_acs_params command (Continued)
Prompt Required Value Definition Conditions
Enter AMR Full Rate Yes Enter up to three Prompt displays if the ACS
downlink adaptation values. contains more than one codec
hysteresis for mode.
frequency hopping: One value for each adjacent
pair of codec modes in ACS.

Table 3-21 Half Rate prompts for chg_acs_params command

Prompt Required Value Definition Conditions

Enter AMR Half Rate Yes
active codec set:
Enter AMR Half Rate Yes
initial codec mode:
Enter AMR Half Rate Yes
uplink adaptation
thresholds:
Enter AMR Half Rate Yes
uplink adaptation
hysteresis:
Enter AMR Half Rate Yes
downlink adaptation
thresholds:
Enter AMR Half Rate Yes
downlink adaptation
hysteresis:
Enter AMR Half Rate Yes
uplink adaptation
thresholds for
frequency hopping:
Up to four codec mode Prompt displays if the AMR
values (codec rates) feature is unrestricted, the
are entered in order BTS type is AMR-capable, and
of descending bit-rate the mode specified is 0 or 2.
(ascending field value
0 - 7, see Table 3-17)
The value must be one Prompt displays if the ACS
of the rates included in contains more than one codec
the Active Codec Set. mode.
Enter up to three Prompt displays if the ACS
uplink threshold values contains more than one codec
in order of descending mode.
C/I estimation. One uplink value for each
adjacent pair of codec modes
in ACS.
Enter up to three uplink Prompt displays if the ACS
hysteresis values. contains more than one codec
mode.
One uplink value for each
adjacent pair of codec modes
in ACS.
Enter up to three Prompt displays if the ACS
downlink threshold contains more than one codec
values in order mode.
of descending C/I One downlink value for each
estimation. adjacent pair of codec modes
in ACS.
Enter up to three Prompt displays if the ACS
downlink hysteresis contains more than one codec
values. mode.
One downlink value for each
adjacent pair of codec modes
in ACS.
Enter up to three Prompt displays if the ACS
values. contains more than one codec
mode.
One value for each adjacent
pair of codec modes in ACS.

Continued

3-70 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Table 3-21 Half Rate prompts for chg_acs_params command (Continued)

Prompt Required Value Definition Conditions
Enter AMR Half Rate Yes Enter up to three Prompt displays if the ACS
uplink adaptation values. contains more than one codec
hysteresis for mode.
frequency hopping: One value for each adjacent
pair of codec modes in ACS.
Enter AMR Half Rate Yes Enter up to three Prompt displays if the ACS
downlink adaptation values. contains more than one codec
thresholds for mode.
frequency hopping: One value for each adjacent
pair of codec modes in ACS.
Enter AMR Half Rate Yes Enter up to three Prompt displays if the ACS
downlink adaptation values. contains more than one codec
hysteresis for mode.
frequency hopping: One value for each adjacent
pair of codec modes in ACS.

Example

This example sets four Full Rate codec modes in the active codec set for cell 2 9 6 0 1 1 1,
where previously only one mode was configured.

chg_acs_params 1 cell_number=2 9 6 0 1 1 1

Where: is:
0 mode
4960111 cell ID

System response

AMR Half Rate active codec set:2 3 4 5

AMR Half Rate initial codec mode:1
AMR Half Rate uplink adaptation thresholds:40 30 20
AMR Half Rate uplink adaptation hysteresis:5 8 8
AMR Half Rate downlink adaptation thresholds:41 31 21
AMR Half Rate downlink adaptation hysteresis:4 4 4
AMR Half Rate uplink adaptation thresholds for frequency hopping:38 28 21
AMR Half Rate uplink adaptation hysteresis for frequency hopping:1 1 1
AMR Half Rate downlink adaptation thresholds for frequency hopping:40 30 20
AMR Half Rate downlink adaptation hysteresis for frequency hopping:1 1 1
Enter AMR Half Rate active codec set: 4
COMMAND ACCEPTED

68P02901W23-T 3-71
Jan 2010
References Chapter 3: Device/function related commands

References

Related commands

disp_acs on page 3-244.

3-72 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference chg_a5_alg_pr

chg_a5_alg_pr

Description

The chg_a5_alg_pr command specifies the A5 encryption algorithms in the order in which
the BSS uses them.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites The encryption feature must be unrestricted.
To include an algorithm in the priority list, it must
be enabled with the associated database parameter
(option_alg_a5_1 through option_alg_a5_7).
Operator actions The encryption feature must be activated first.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

chg_a5_alg_pr <first_alg> [<second_alg>] [<third_alg>] [<fourth_alg>]

[<fifth_alg>] [<sixth_alg>] [<seventh_alg>] [<eighth_alg>]

68P02901W23-T 3-73
Jan 2010
Format Chapter 3: Device/function related commands

Input parameters

The following values specify the GSM encryption algorithm:

Value GSM Algorithm

0 No encryption; any algorithms listed after 0 are ignored.
1 A5/1
2 A5/2
3 A5/3
4 A5/4
5 A5/5
6 A5/6
7 A5/7

first_alg

first algorithm choice (0 - 7)

second_alg

second algorithm choice (0 - 7)

NOTE
The system uses only the first and second algorithm choices. Values entered for
the remaining parameters are ignored.

third_alg

third algorithm choice (0 - 7)

fourth_alg

fourth algorithm choice (0 - 7)

fifth_alg

fifth algorithm choice (0 - 7)

sixth_alg

sixth algorithm choice (0 - 7)

seventh_alg

seventh algorithm choice (0 - 7)

eighth_alg

eighth algorithm choice (0 - 7)

3-74 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

In this example, the algorithms ordered as follows: A5/1, A5/2:

chg_a5_alg_pr 1 2

Where: is:
1 A5/1 Algorithm
2 A5/2 Algorithm

System response

COMMAND ACCEPTED

Example 2

In this example, no encryption is used:

chg_a5_alg_pr 0

Where: is:
0 no encryption

System response

COMMAND ACCEPTED

References

Related commands

disp_a5_alg_pr on page 3-242 chg_element on page 3-112

68P02901W23-T 3-75
Jan 2010
chg_audit_sched Chapter 3: Device/function related commands

chg_audit_sched

Description

The chg_audit_sched command schedules audits of selected devices at specified site based on
device type and audit type.

The chg_audit_sched is modified to support the swap_test type audit on the TDM device
at site 0 (BSC or RXCDR).

Audits can run in parallel or in series.

Audits of different devices run in parallel, that is, the system can audit different devices at
the same time. For example, audits of the DRI and GCLK run in parallel.

Audits of similar devices run sequentially that is, the audit of one device must end before
the second device audit can begin. For example, the system audits all GPROCs at a site
sequentially.

Use the device_audit command to turn off the audits.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites An operator at the OMC-R must rlogin to a site before an
audit can be scheduled.
Only one audit can be run at a time. If a log exists from a
previous audit, it is overwritten with the log created by
the current audit.

NOTE
Enter this command only at the BSC or a specified PCU at a GPRS site. This command
does not work at a BTS site. Contact the OMC-R for help.

Format

Syntax

chg_audit_sched <location> <device_name> <audit_type> <start_time_hour>

<start_time_min> <end_time_hour> <end_time_min> <interval_hour> <interval_min>

3-76 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Input parameters

location

Specifies the audit location:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

device_name

Name that uniquely identifies the device.

The following devices can be audited at InCell sites using this command:

BSP BTP DHP DRI GCLK

GPROC KSW MSI SITE TDM

The following devices can be audited at M-Cell sites using this command:

{34371G} BBU BTP DRI MSI SITE

The following devices can be audited at a PCU using this command:

DPROC MSI PSP

audit_type

Type of audit Value Tests Available Locations

all 0 BSC, BTS, and PCU
safe 1 Safe tests KSW
int_lpbk 2 Internal loopback RXCDR at a remote
transcoding BSC
self_test 3 All BSC and BTS only
swap_test 4 Expanded cage

start_time_hour

Start time hour (00 to 23)

start_time_min

Start time minutes (00 to 59)

end_time_hour

End time hour (00 to 23)

end_time_min

End time minutes (00 to 59)

interval_hour

68P02901W23-T 3-77
Jan 2010
Format
The interval hour (00 to 23)
interval_min
The interval minutes (00 to 59)
Scheduling types
There are three scheduling types:
Continuous Scheduling
Range Scheduling
Once-Per-Day Scheduling
Device scheduling defaults
Table 3-22 lists the device scheduling defaults.
Table 3-22 Device scheduling defaults
Device
{34371G} BBU
KSW safe test audit
KSW internal loopback audit
GCLK safe test audit
GPROC safe test audit
DHP safe test audit
TDM safe test audit
BSP safe test audit
BTP safe test audit
MSI safe test audit
DRI safe test audit
SITE safe test audit
AXCDR safe test audit
3-78
Chapter 3: Device/function related commands
The system schedules continuous audits if:
The start_time and end_time both have a value of
00:00.
The interval time is 0.
If the end_time is greater than the start_time, the
system schedules the range audits.
The interval time is 0.
The system schedules range audits if:
The start_time equals the end_time.
The interval time is 00:00.
Default schedule
continuously every 10 minutes
continuously every hour
from 2:00 am to 4:00 am every 15 minutes
continuously every hour
continuously every 10 minutes
once a day at 1:00 am
continuously every 10 minutes
continuously every 1 minute
continuously every 30 minutes
continuously every 10 minutes
68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Query Audit information

The following command string format can be used to display an audit scheduled for devices:
query_audits <location> <audit_type> <device_name> <device_id1>
<device_id2><device_id3>

Refer to the description of the query_audits parameter. Alternatively multiple disp_element

commands can be used as listed in the following section.

Display information

The following command string format can be used to display the audit_type scheduled for
a device:

disp_element sap_audit_type,<index> <location>

Refer to the description of the sap_audit_type parameter.

The following command string format displays the device_type scheduled for a device:

disp_element sap_device_type,<index> <location>

Refer to the description of the sap_device_type parameter.

The following command string format displays the start_time_hour and start_time_min
scheduled for a device:

disp_element sap_start_time,<index> <location>

Refer to the description of the sap_start_time.

The following command string format can be used to display the end_time_hour and
end_time_min scheduled for a device:

disp_element sap_end_time,<index> <location>

Refer to the description of the sap_end_time parameter.

The following command string format displays the interval_hour and interval_min scheduled
for a device:

disp_element sap_interval,<index> <location>

Refer to the description of the sap_interval parameter.

68P02901W23-T 3-79
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

In this example of range scheduling, the audit schedule is changed so that the DRI is audited
for safe tests every 15 minutes from 9:30 am until 10:30 pm:

chg_audit_sched bsc dri safe 9 30 22 30 0 15

Where: is:
bsc location
dri device_name
safe audit_type
9 30 start_time
22 30 end_time
0 15 interval

System response

COMMAND ACCEPTED

Example 2

In this example of GPRS range scheduling, the audit schedule is changed so that the PICP MSI 0
is audited for safe tests every 45 minutes from 9 am until 5:30 pm:

chg_audit_sched pcu_0 msi safe 9 0 17 30 0 45

Where: is:
pcu_0 location
msi device_name
safe audit_type
9 00 start_time
17 30 end_time
0 45 interval

System response

COMMAND ACCEPTED

3-80 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 3

In this example, the audit is scheduled for the PSI device from 9:30 am to 10:30 pm with an
interval of 15 minutes.

chg_audit_sched bsc psi safe 9 30 22 30 0 15

Where: is:
bsc location
psi device_name
safe audit_type
9 30 start_time
22 30 end_time
0 15 interval

System response

COMMAND ACCEPTED

Example 4

In this example, the audit is scheduled for the tdm device at 3:00 am daily.

chg_audit_sched 0 tdm swap_test 3 0 3 0 0 0

Where: is:
0 location
tdm device_name
swap_test audit_type
30 start_time
30 end_time
00 interval

System Response

COMMAND ACCEPTED

68P02901W23-T 3-81
Jan 2010
Examples Chapter 3: Device/function related commands

Example 5

This example reschedules safe audit execution for DRI devices at location 1. The audit starts at
09:30 and ends at 22:30 and runs every 15 minutes.

chg_audit_sched 1 DRI safe 9 30 22 30 0 15

Where: is:
1 location
DRI device_name
safe audit_type
9 30 start_time
22 30 end_time
0 15 interval

System response

COMMAND ACCEPTED

Example 6

This example causes the swap test to occur at 2:50 am every day.

chg_audit_sched 0 tdm swap_test 2 50 5 0 0 0

Where: is:
0 location
tdm device_name
swap_test audit_type
2 50 start_time
50 end_time
00 interval

System response

COMMAND ACCEPTED

3-82 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 7

{34371G}

This example reschedules a SAFE audit for the BBU device for 9:30 AM until 10:30 PM with
an interval of 15 minutes.

chg_audit_sched 23 BBU safe 9 30 22 30 0 15

Where: is:
23 location
BBU device_name
safe audit_type
9 30 start_time
22 30 end_time
0 15 interval

System Response

COMMAND ACCEPTED

References

Related commands

cage_audit on page 3-58 device_audit on page 3-230 query_audits on page 3-532

site_audit on page 3-568

68P02901W23-T 3-83
Jan 2010
chg_cell_element Chapter 3: Device/function related commands

chg_cell_element

Description

The chg_cell_element command changes the value of cell-related parameters. This command
supports only non-statistical cell elements.

Prompts are presented for dependent cell parameters where necessary.

Security level 4
Supported by OMC-R GUI Yes.
Command type Dependent upon the database parameter being
changed.
Prerequisites None
Operator actions Respond to the dependent parameter prompts
associated with the cell element being modified.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

chg_cell_element [<location>] <element> [,<index>] <value> <cell_desc_opt>

chg_cell_element <location> <element> [,<index>] <value> all

NOTE
When an attempt is made to change cell elements ccch_conf, gprs_enabled,
gprs_ts_config_alg, max_gprs_ts_per_carrier, primary_pcu, res_gprs_pdchs,
res_ts_less_one_carrier, switch_gprs_pdchs, or sw_ts_less_one_carrier, and the
requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts
the request and issues a warning to indicate that sufficient GDS or PMC resource is
not available.

3-84 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Input parameters

location

The location can also be entered as all to change the value of the specified element for all
available cells in the system.

element

The cell parameter to be changed

NOTE
The all option does not work for the coincident_mb parameter.

index

The index of the element being changed, if any.

value

The value being assigned to the element.

cell_desc_opt

The GSM cell ID of the affected cell. cell_number= can precede the GSM cell ID (optional).

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

Only PCS1900 systems can use a three-digit MNC.

The cell_desc can also be a cell name created using the cell_name command. When the cell
name is entered, it must be placed inside double quotation marks. cell_name= can precede the
cell name (optional).

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

With some parameters, all can be entered. If this command is used, <location> or all must
also be used for the site. See the individual parameter descriptions.

68P02901W23-T 3-85
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

In this example, the hop_qual_enabled parameter is changed to 1 for a cell with GSM Half
Rate enabled:

chg_cell_element hop_qual_enabled 0 cell_number =0 0 1 0 1 98 75

Where: is:
hop_qual_enabled cell element
1 element value
cell=0 0 1 0 1 98 75 cell description

System response

Enter RSS handover threshold l_rxqual_dl_h_hopping: 250

Enter RSS handover threshold l_rxqual_ul_h_hopping: 250
Enter RSS handover threshold l_rxqual_dl_p_hopping: 250
Enter RSS handover threshold l_rxqual_ul_p_hopping: 250
Enter RSS handover threshold l_rxqual_ul_h_hopping_hr: 250
Enter RSS handover threshold l_rxqual_ul_p_hopping_hr: 250
Enter RSS handover threshold l_rxqual_dl_h_hopping_hr: 200
Enter RSS handover threshold l_rxqual_dl_p_hopping_hr: 200
COMMAND ACCEPTED

NOTE
The following AMR Full Rate HDPC parameters are only prompted for if AMR is
unrestricted.

Enter RSS handover threshold l_rxqual_ul_h_hopping_amr_fr:

Enter RSS handover threshold l_rxqual_ul_p_hopping_amr_fr:
Enter RSS handover threshold l_rxqual_dl_h_hopping_amr_fr:
Enter RSS handover threshold l_rxqual_dl_p_hopping_amr_fr:

3-86 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 2

This example turns on IMRM band_preference for a cell using the numeric value 16, and
set all weighting parameters to 0.

chg_cell_element band_preference 16 cell_number=0 0 1 0 1 1 12

Where: is:
band_prefernce element
16 element value
cell=0 0 1 0 1 1 12 cell number

System response

Enter the weighting for PGSM: 0

Enter the weighting for EGSM: 0

Enter the weighting for DCS1800: 0

Enter the weighting for UMTS: 0

COMMAND ACCEPTED: WARNING: All IMRM band weights set to unsupported. The BSS
shall apply internal defaults in the IMRM band selection algorithm

Example 3

This example changes the value of the database element isp_enabled to 1 for cell 0 0 1 0 1 1 4.

chg_cell_element ext_utbf_nodata 1 cell 0 0 1 0 1 1 4

Where: is:
isp_enabled cell element
1 element value
0010114 cell number

System response

COMMAND ACCEPTED

68P02901W23-T 3-87
Jan 2010
Examples Chapter 3: Device/function related commands

Example 4

This example enables the functionality of AGCH flow control, any one of the triggers associated
with IA and IAR can trigger AGCH overload.

chg_cell_element agch_flow_control_mode 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
agch_flow_control_mode element
1 element value
5 4 3 2 1 61986 34944 cell number

System Response

COMMAND ACCEPTED

Example 5

This example modifies the value of cstats_cell_enabled from 0 to 1 to enable the 5 minute
statistics uploading for cell 4 6 0 0 0 23 1101 under site 11.

chg_cell_element cstats_cell_enabled 1 cell=4 6 0 0 0 23 1101

Where: is:
cstats_cell_enabled element
1 element value
4 6 0 0 0 23 1101 cell number

System Response

COMMAND ACCEPTED

Example 6

This example attempts to disable the Extended Range Cell for GSM (ext_range_cell = 0) when
ext_pdchs is set to non-zero for any RTF in the cell.

chg_cell_ele ext_range_cell 0 cell 0 0 1 0 1 1 18

Where: is:
ext_range_cell element being changed
0 new element value
0 0 1 0 1 1 18 cell number

3-88 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System Response

COMMAND REJECTED: Value of ext_pdchs shall be 0 when ext_range_cell is disabled

for the cell

Example 7

This example attempts to enable baseband hopping (hopping_support = 2) when ext_pdchs

in any RTF of the cell > 0.

chg_cell_ele hopping_support 2 cell 0 0 1 0 1 1 18

Where: is:
hopping_support element being changed
2 new element value
0 0 1 0 1 1 18 cell number

System Response

COMMAND REJECTED: Value of ext_pdchs shall be 0 when Baseband hopping is enabled

for the cell

Example 8

{34452}

This example modifies the value of the new_calls_amr_hr parameter to 10 for cell 4 6 0 0
0 23 1101 under site 11.

chg_cell_el new_calls_amr_hr 10 cell=4 6 0 0 0 23 1101

Where: is:
new_calls_amr_hr element name
10 value
4 6 0 0 0 23 1101 cell number

System Response

COMMAND ACCEPTED

68P02901W23-T 3-89
Jan 2010
Examples Chapter 3: Device/function related commands

Example 9

{34452}

This example modifies the value of the reconfig_fr_to_amr_hr parameter to 10 for cell
4 6 0 0 0 23 1101 under site 11.

chg_cell_el reconfig_fr_to_amr_hr 10 4 6 0 0 0 23 1101

Where: is:
reconfig_fr_to_amr_hr element name
10 value
4 6 0 0 0 23 1101 cell number

System Response

COMMAND ACCEPTED

Example 10

{34452}

This example modifies the value of the inner_amr_hr_usage_thres parameter to 10 for cell 4 6
0 0 0 23 1101 under site 11.

chg_cell_el inner_amr_hr_usage_thres 10 cell=4 6 0 0 0 23 1101

Where: is:
inner_amr_hr_usage_thres element name
10 value
4 6 0 0 0 23 1101 cell number

System Response

COMMAND ACCEPTED

3-90 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 11

{34452}

This example modifies the value of the pch_queue_length_ctr parameter to 1 to set the PCH
queue length to 648 for cell 4 6 0 0 0 23 1101 under site 11.

chg_cell_el pch_queue_length_ctr 1 cell=4 6 0 0 0 23 1101

Where: is:
pch_queue_length_ctr element name
1 value
4 6 0 0 0 23 1101 cell number

System Response

COMMAND ACCEPTED

Example 12

{34452}

This example enables the function of Intelligent Selective Paging.

chg_cell_element isp_enabled 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
isp_enabled element name
1 value
5 4 3 2 1 61986 34944 cell number

System Response

COMMAND ACCEPTED

68P02901W23-T 3-91
Jan 2010
Examples Chapter 3: Device/function related commands

Example 13

{34452}

This example enables the functionality of the AGCH flow control, any one of the triggers
associated with IA and IAR can trigger AGCH overload.

chg_cell_element agch_flow_control_mode 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
agch_flow_control_mode element name
1 value
5 4 3 2 1 61986 34944 cell number

System Response

COMMAND ACCEPTED

Example 14

{34452}

This example modifies the value of the cstats_cell_enabled parameter from 0 to 1 to enable the
5 minutes statistics uploading for cell 4 6 0 0 0 23 1101 under site 11.

chg_cell_el cstats_cell_enabled 1 cell=4 6 0 0 0 23 1101

Where: is:
cstats_cell_enabled element name
1 value
4 6 0 0 0 23 1101 cell number

System Response

COMMAND ACCEPTED

3-92 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 15

{34452}

This example modifies the value of the new_calls_amr_hr parameter to 70 at cell 0 0 1 0 1 1 1.

chg_cell_ele new_calls_amr_hr 70 cell 0 0 1 0 1 1 1

Where: is:
new_calls_amr_hr element name
70 value
0010111 cell number

System Response

COMMAND ACCEPTED

Example 16

{34452}

This example modifies the value of the new_calls_hr parameter to 70 at cell 0 0 1 0 1 1 1,

when the new_calls_amr_hr parameter is 75.

chg_cell_ele new_calls_hr 70 cell 0 0 1 0 1 1 1

Where: is:
new_calls_hr element name
70 value
0010111 cell number

System Response

ERROR: new_calls_amr_hr must be less than or equal to new_calls_hr

COMMAND REJECTED.

68P02901W23-T 3-93
Jan 2010
Examples Chapter 3: Device/function related commands

Example 17

{34452}

This example modifies the value of the reconfig_fr_to_amr_hr parameter to 70 at cell 0 0

1 0 1 1 1.

chg_cell_ele reconfig_fr_to_amr_hr 70 cell 0 0 1 0 1 1 1

Where: is:
reconfig_fr_to_amr_hr element name
70 value
0010111 cell number

System Response

COMMAND ACCEPTED

Example 18

{34452}

This example attempts to modify the value of the reconfig_fr_to_hr parameter to 70 at cell 0 0
1 0 1 1 1, when the reconfig_fr_to_amr_hr parameter is 75.

chg_cell_ele reconfig_fr_to_hr 70 cell 0 0 1 0 1 1 1

Where: is:
reconfig_fr_to_hr element name
70 value
0010111 cell number

System Response

ERROR: reconfig_fr_to_amr_hr must be less than or equal to reconfig_fr_to_hr

COMMAND REJECTED.

3-94 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 19

{34452}

This example modifies the value of the inner_amr_hr_usage_thres parameter to 70 at cell 0 0

1 0 1 1 1.

chg_cell_ele inner_amr_hr_usage_thres 70 cell 0 0 1 0 1 1 1

Where: is:
inner_amr_hr_usage_thres element name
70 value
0010111 cell number

System Response

COMMAND ACCEPTED

Example 20

{34452}

This example attempts to modify the value of the inner_hr_usage_thres parameter to 70 at cell
0 0 1 0 1 1 1, when the inner_amr_hr_usage_thres parameter is 75.

chg_cell_ele inner_hr_usage_thres 70 cell 0 0 1 0 1 1 1

Where: is:
inner_hr_usage_thres element name
70 value
0010111 cell number

System Response

ERROR: inner_amr_hr_usage_thres must be less than or equal to inner_hr_usage_thres

COMMAND REJECTED.

68P02901W23-T 3-95
Jan 2010
chg_cell_id Chapter 3: Device/function related commands

chg_cell_id

Description

The chg_cell_id command changes the GSM cell ID of a specified cell.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

Only PCS1900 systems can use a three-digit MNC.

The format to enter PGSM, EGSM, or DCS1800 Cell ID is: a b c d e f g

The format to enter a PCS1900 Cell ID is: abc zde f g

Where: is:
a the first digit of the MCC (Mobile Country Code).
b the second digit of the MCC.
c the third digit of the MCC.
z the first digit of the MNC (Mobile Network Code) for
PCS1900 systems. This digit only applies to PCS1900
systems. EGSM, PGSM, and DCS1800 systems still use
the two-digit MNC, beginning with d, shown in the next
row.
d either:

the second digit of the PCS1900 MNC, or

the first digit of the PGSM, EGSM, or DCS1800

MNC.
e either:

the third digit of the MNC, or

the third digit of the PCS1900 MNC, or

the second digit of the PGSM, EGSM or DCS1800

MNC, or
Only PCS1900 systems use a three-digit MNC.
f the LAC (Local Area Code).
g the CI (Cell Identity).

3-96 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

When the GSM cell ID is changed using this command, it is not propagated throughout the CM
database. A warning message is presented when this command is successfully entered.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

chg_cell_id <old_cell_desc> <new_cell_desc>

Input parameters

old_cell_desc

Original Cell ID of the cell.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

Only PCS1900 systems can use a three-digit MNC.

The old_cell_desc can also be a cell name created using the cell_name command. When the
cell name is entered, it must be placed inside double quotation marks.

new_cell_desc

New GSM cell ID of the cell.

68P02901W23-T 3-97
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

In this example, the GSM cell ID is changed:

chg_cell_id 5 4 3 2 1 61986 34944 5 4 3 2 1 61985 37982

Where: is:
5 4 3 2 1 61986 34944 old_cell_desc
5 4 3 2 1 61985 37982 new_cell_desc

System response

WARNING: Verify OML state to ensure change propagated to all neighbors.

COMMAND ACCEPTED

Example 2

In this example, the affected cell is identified using the cell_name london-north:

chg_cell_id london-north 5 4 3 2 1 61985 37982

Where: is:
london-north old_cell_desc (using cell name)
5 4 3 2 1 61985 37982 new_cell_desc

System response

WARNING: Verify OML state to ensure change propagated to all neighbors.

COMMAND ACCEPTED

Example 3

In this example, the GSM cell ID is changed for a PCS1900 cell:

chg_cell_id 543 021 61986 34944 543 021 61985 37982

Where: is:
543 021 61986 34944 old_cell_desc
543 021 61985 37982 new_cell_desc

3-98 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

WARNING: Verify OML state to ensure change propagated to all neighbors.

COMMAND ACCEPTED

References

Related commands

add_cell on page 3-22 cell_name on page 3-62 copy_cell on page 3-199

del_cell on page 3-212 disp_cell on page 3-261

68P02901W23-T 3-99
Jan 2010
chg_cmd_level Chapter 3: Device/function related commands

chg_cmd_level

Description

The chg_cmd_level command modifies the current level of MMI command to a certain security
level.

Security level 4
Supported by OMC GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

chg_cmd_level <command> <level you want the command to change>

Example

Example 1

This example modifies the level of disp_equipment to 2.

chg_cmd_level disp_equipment 2

Where: is:
disp_equipment command
2 level

System response

COMMAND ACCEPTED

3-100 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference chg_csfp

chg_csfp

Description

The chg_csfp command changes the CSFP algorithm or flow control values.

The CSFP algorithm selects the CSFP algorithm method used when configuring CSFPs using the
configure_csfp command or through the OMC-R.

The flow_control selects the CSFP flow control value that controls the amount of RSL link
utilization that a CSFP download from BSC to BTS can use.

A value of 100 does not mean that the link is 100% utilized during the download. Only the CSFP
downloads can proceed at the maximum throughput rate.

Security level 4
Supported by OMC GUI Yes
Command type A (no operator actions)
Prerequisites None

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

chg_csfp <element> <value> <location>

68P02901W23-T 3-101
Jan 2010
Examples Chapter 3: Device/function related commands

Input parameters

element

Two selections are available:

algorithm Selects the CSFP algorithm method. The location values that can be
entered for this element are 0 (or bsc) to 140.
flow_control Selects the CSFP flow control value. The location values that can be
entered for this element are 1 - 140.

value

Either an algorithm or a flow control value can be entered but not both. The value that can be
used is dependent upon the selected element:

algorithm none (4) No CSFP device is to be configured at this site

stby (2) Select only standby BSP/BTP GPROCs

pool (3) Select only pool GPROCs
any (1) Select POOL GPROCs first followed by STBY GPROCs.
Default value for this algorithm.
flow_control Selectable in a range from 10 to 100 in steps of 10. The default value is 10%.

location

Specifies the element location.

0 or bsc BSC
1 - 140 BTS
pcu PCU

Examples

Example 1

This example shows the inputs required to update the CSFP algorithm at the BSC to be only
pool GPROCs.

chg_csfp algorithm pool bsc

Where: is:
algorithm element
pool Only pool GPROCs
bsc location

3-102 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

COMMAND ACCEPTED

Example 2

This example shows the inputs required to update the CSFP flow control at site 3 to be 10%.

chg_csfp flow_control 10 3

Where: is:
flow_control element
10 flow control percentage
3 location

System response

COMMAND ACCEPTED

Example 3

This example updates the csfp flow control value of PCU.

chg_csfp flow_control 40 pcu

Where: is:
flow_control element
40 flow control percentage
pcu location

System response

COMMAND ACCEPTED

References

Related command

disp_csfp on page 3-284

68P02901W23-T 3-103
Jan 2010
chg_dte Chapter 3: Device/function related commands

chg_dte

Description

The chg_dte command assigns the DTE addresses to allow connections between the BSC and
the OMC-R or CBC.

The mapping of DTE addresses used and the default timeslots to contact the OMC while the
network is in ROM are shown in Table 3-23 for the RXCDR and in Table 3-24 for the BSC.

Table 3-23 RXCDR default DTE addresses

Cage MSI slot MMS Default timeslot RXCDR DTE address

0 10 0 1 0
0 10 1 1 1
0 8 0 1 2
1 10 0 1 3

Table 3-24 BSC default DTE addresses

Cage MSI slot MMS Default timeslot RXCDR DTE address

0 16 0 1 0
0 16 1 1 1
0 14 0 1 2
1 16 0 1 3

Security level 3
Supported by OMC-R GUI Yes
Command type B (Operator actions required)
Prerequisites The OML link affected by this command must be reset for
the changes to take effect.
Operator actions Reset the OML after changes have been entered with this
command.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

3-104 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Format

Syntax

chg_dte <link> [<link_num>] <address_length> [<address_byte>] . . .

[<address_byte>]

Input parameters

link

Specifies the link location:

bsc The communication link between the BSC and the OMC-R.
omcr OMC-R
cbc CBC
bcs_cbc The communication link between the BSC and CBC.

link_num

The link location type determines the range of values:

0-3 bsc
0-7 omcr
0 bsc_cbc or cbc. If the address_length is 0, a link_num is required for
cbc and bsc_cbc.

address_length

The number of valid address bytes that are added to the list. The range of values is 0 - 14.

address_byte

The value of a particular address byte. The range of values is 0 - 9. The number of address bytes
entered must equal the number entered for the address_length parameter.

An address_byte value is not required when the address_length is zero.

68P02901W23-T 3-105
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

In this example, the DTE address of the third BSC is changed to 12345:

chg_dte bsc 3 5 1 2 3 4 5

Where: is:
bsc location
3 link_num
5 address_length
12345 address_byte (5 bytes)

System response

BSS DTE addresses:

Address #0: 23466811570001

Address #1: 41224643654225

Address #2: 31777619565738

Address #3: 12345

OMCR DTE addresses:

Address #0: 23466823020041

Address #1: 24885902667864

Address #2: 38959620015151

Address #3: 122876465567

Address #4: 2301

Address #5: 6811570001

Address #6: Zero length address

Address #7: Zero length address

COMMAND ACCEPTED

3-106 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 2

In this example, a zero length DTE address is created:

chg_dte omcr 2 0

Where: is:
omcr location
2 link_num
0 address_length

System response

BSS DTE addresses:

Address #0: 23466811570001

Address #1: 41224643654225

Address #2: 31777619565738

Address #3: 12345

OMCR DTE addresses:

Address #0: 23466823020041

Address #1: 24885902667864

Address #2: Zero length address

Address #3: 122876465567

Address #4: 2301

Address #5: 6811570001

Address #5: 6811570001

Address #6: Zero length address

Address #7: Zero length address

COMMAND ACCEPTED

References

Related command

disp_dte on page 3-291.

68P02901W23-T 3-107
Jan 2010
chg_eas_alarm Chapter 3: Device/function related commands

chg_eas_alarm

Description

The chg_eas_alarm command initializes and modifies the EAS (External Alarm System) alarm
table. The EAS alarm table contains 34 indexed pairs. Each pair includes a severity level and
up to 24 text characters for each BSS. Each pair corresponds to the output of an equipped
EAS/PIX module.

This command permits individual EAS alarms to be reported as text strings.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The EAS device must be equipped before a severity level
and text characters can be assigned.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

chg_eas_alarm <alarm_table_index> <alarm_severity_level> <new_alarm_string>

3-108 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Input parameters

alarm_table_index

Specifies the index number assigned to a user-defined alarm text string in the EAS Alarm Table
on the following page. The range of values is 0 - 33.

alarm_severity_level
Specifies the alarm level for a specific alarm string. Valid values are:

0 investigate
1 critical
2 major
3 minor
4 warning

new_alarm_string

Assigns the alarm text string that corresponds to an alarm_table_index value in the EAS Alarm
Table. The alarm string must be entered inside double quotation marks. The alarm text string
can be a maximum of 24 characters, including spaces.

Example

In this example, an alarm string of door open is assigned to the first index (1) of the alarm
string table. This text string contains nine characters; the alarm is classified minor (3); and the
string signifies that a cabinet door is open:

chg_eas_alarm 1 3 cabinet door open

Where: is:
1 alarm_table_index
3 alarm_severity_level
cabinet_door_open new_alarm_string

System response

COMMAND ACCEPTED

68P02901W23-T 3-109
Jan 2010
References Chapter 3: Device/function related commands

References

Related information

Table 3-25 lists the EAS default alarm strings.

Table 3-25 EAS default alarm strings

alarm_table_index Default alarm string

0 Burglar
1 Door Open
2 Fire
3 High Temperature
4 Low Temperature
5 High Humidity
6 Low Humidity
7 Tower Beacon Outage
8 Surge Arrester Failure
9 Microwave Trans. Failure
10 AC Power Failure
11 Generator Running
12 Generator Failed
13 PSU Rectifier
14 PSU Battery
15 PSU Fuse
16 Personnel on Site
17 General Alarm 1
18 General Alarm 2
19 General Alarm 3
20 PCU Over Temperature
21 PCU Customer Defined 1
22 PCU Door Open
23 PCU DC Fail
24 PCU Circuit Breaker
25 PCU AC Fail
26 PCU Comms Equipment

Continued

3-110 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 3-25 EAS default alarm strings (Continued)

alarm_table_index Default alarm string
27 TDU Over Temperature
28 TDU Door Open
29 TDU Circuit Breaker
30 TDU Battery
31 TDU Customer Defined 1
32 TDU Customer Defined 2
33 TDU Customer Defined 3

Related commands

chg_element on page 3-112 disp_element on page 3-294

68P02901W23-T 3-111
Jan 2010
chg_element Chapter 3: Device/function related commands

chg_element

Description

The chg_element command modifies database parameters in the CM database.

Security level 4
Supported by OMC-R GUI Yes
Command type Dependent on the database parameter being changed.
Prerequisites None
Operator actions Respond to the dependent parameter prompts associated
with the cell element being modified.

NOTE

Only the chg_ele phase_lock_gclk parameter is moved to security level 3.

Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

chg_element <element_name> [,<index1>][,<index2>] <element_value>

<location>[<cell_desc>]
chg_element <element_name> [,<index1>][,<index2>] <element_value> all
chg_element <element_name> [,<index1>][,<index2>] <element_value> <location>all

NOTE
When an attempt is made to change cell elements ccch_conf, gprs_enabled,
gprs_ts_config_alg, max_gprs_ts_per_carrier, primary_pcu, res_gprs_pdchs,
res_ts_less_one_carrier, sw_ts_less_one_carrier, or switch_gprs_pdchs, and the
requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts
the request and issues a warning to indicate that enough GDS or PMC resource is
not available.

3-112 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Input parameters

element_name

String identifying the database parameter in the CM database.

index1

Some database parameters require an index. They are highlighted with an asterisk in the table
in the Related Information section. A comma is required before the index number.

index2

Database parameters requiring a second index are highlighted in the table shown in the
Related Information section. A comma is required before the index number. index2 is used
only with statistical database parameter names normal and weighted distribution statistical
database parameter names require the use of index2.

value

New value for the element_name.

location

Specifies the site location:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU
all Specifies all sites.
Restrictions on the use of all locations are:

Allowed outside SYSGEN mode only for type A elements.

Not allowed outside SYSGEN mode for type B elements.

Allowed for BY_CELL and BY_SITE elements only.

cell_desc

GSM cell ID of the cell to be changed, preceded by cell_number=

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

Only PCS1900 systems can use a three-digit MNC.

The name of the cell created using the cell_name command can be entered in place of the
cell_number. When the cell name is entered, it must be placed inside double quotation marks,
and cell_name= must precede it.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

68P02901W23-T 3-113
Jan 2010
Examples Chapter 3: Device/function related commands

The value all is also a valid input for the cell_desc, which changes element_name to value for
all cells at the specified location.

Restrictions on the use of all cells are:

Not allowed for elements that cause the site to reset.

Not allowed outside SYSGEN mode.

Allowed for BY_CELL and BY_SITE elements only.

Sites that are not equipped are not affected.

Examples

The following examples only demonstrate how specific parameters are changed using the
chg_element command. The examples shown can be part of a larger procedure. Refer to the
appropriate documentation for detailed explanations of these procedures.

Example 1

In this example, the bsic value is changed to 1 for site number 1, cell_number=5 4 3 2 1
61986 34944:

chg_element bsic 1 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
bsic element name
1 value
1 location
5 4 3 2 1 61986 34944 cell description

System response

WARNING: Changing this element will reset all DRIs associated with this cell and
will not be propagated through out the neighbor list

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

Selecting y or Y causes the system to make the change and reset.

Selecting n or N causes the system to abandon the command without changing the parameter.

3-114 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 2

In this example, the database parameter transcoder_location is changed to a value of 1 for

site number 0:

chg_element transcoder_location 1 0

Where: is:
transcoder_location element name
1 value
0 location

System response

COMMAND ACCEPTED

NOTE
Example 2 works only at site 0 in SYSGEN ON mode.

Example 3

In this example, the severity of EAS alarm 6 at location 0 is changed to level 2:

chg_element eas_severity,6 2 0

Where: is:
eas_severity element name
6 index
2 value
0 location

System response

COMMAND ACCEPTED

68P02901W23-T 3-115
Jan 2010
Examples Chapter 3: Device/function related commands

Example 4

In this example, the affected cell is identified using the cell_name london-north:

chg_element bsic 1 1 cell_name= london-north

Where: is:
bsic element name
1 value
1 location
london-north cell name

System response

WARNING: Changing this element will reset all DRIs associated with this cell and
will not be propagated through out the neighbor list

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

Selecting y or Y causes the system to make the change and reset.

Selecting n or N causes the system to abandon the command without changing the parameter.

Example 5

In this example, the base station identity code (bsic) value is changed to 1 for PCS 1900 site
number 0, cell_desc=543 721 61986 34944:

chg_element bsic 1 1 cell_number= 543 721 61986 34944

Where: is:
bsic element name
1 value
1 location
543 721 61986 34944 cell description

System response

WARNING: Changing this element will reset all DRIs associated with this cell and
will not be propagated through out the neighbor list

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

Selecting y or Y causes the system to make the change and reset.

Selecting n or N causes the system to abandon the command without changing the parameter.

3-116 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 6

This example attempts to change primary_pcu from 1 to 0 when PCU 0 does not have enough
PMC resources for the Cell.

chg_element primary_pcu 0 1 cell_number= 0 0 1 0 1 1 1

Where: is:
primary_pcu element name
0 value
1 location
0010111 cell description

System response

WARNING: GPRS traffic may be disrupted while GPRS timeslots are being
reconfigured

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

WARNING: Insufficient PMC resources available for all PDTCHs on the PCU.

Example 7

In this example, the value of improve_ts_enabled is changed to 0 when the improved timeslot
sharing feature is unrestricted.

chg_element improve_ts_enabled 0 bsc

Where: is:
improve_ts_enabled element name
0 value
bsc location

System Response

WARNING: B-U DD CTU2 DRIs must be cycled to deactivate ITS at specific sites or
reset BTS site.

COMMAND ACCEPTED

68P02901W23-T 3-117
Jan 2010
Examples Chapter 3: Device/function related commands

Example 8

In this example, the value of the database element ss7_hsp_12_t1 is modified to 255000 when
the increased network capacity feature is unrestricted.

chg_element ss7_hsp_12_t1 255000 0

Where: is:
ss7_hsp_12_t1 element name
255000 value
0 location

System response

COMMAND ACCEPTED

Example 9

This example enables the rolling blackout mechanism on PCU. The PRP throughput increase
feature is deactivated.

chg_element prp_fanout_mode 1 pcu

Where: is:
prp_fanout_mode element name
1 value
pcu location

System response

WARNING: Changing prp_fanout_mode will cycle device PCU.

Are you sure (y=yes,n=no)?

Example 10

This example modifies the value of streaming_enabled to 1 to enable support of streaming

when the QoS phase 2 feature is unrestricted.

chg_element streaming_enabled 1 0

Where: is:
streaming_enabled element name
1 value
0 location

3-118 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

COMMAND ACCEPTED

Example 11

In this example, the value of td_enabled is changed to 0, when RDB 4225 Inter-RAT feature
(InterRatOpt) and Enhanced Inter-RAT handover feature (EnhancedInterRatOpt) are both
restricted, and TD-SCDMA inter-working feature (tdOpt) is unrestricted.

chg_element td_enabled 0 0

Where: is:
td_enabled element name
0 value
0 location

System response

WARNING: TD-SCDMA inter-working function will be disabled, if the operator

changes td_enabled element.
Are you sure (y=yes, n=no)? y
COMMAND ACCEPTED

Example 12

This example modifies the fieldeng_always_enabled parameter to 1.

chg_ele fieldeng_always_enabled 1 0

Where: is:
fieldeng_always_enabled element name
1 value
0 location

System response

COMMAND ACCEPTED

68P02901W23-T 3-119
Jan 2010
Examples Chapter 3: Device/function related commands

Example 13

This example allows the operator to change the value of cell barred delay to 180 seconds.

chg_element cell_barred_delay 180 0

Where: is:
cell_barred_delay element name
180 value
0 location

System response

COMMAND ACCEPTED

Example 14

In this example, the value of dsp_error_inc is changed to 0 to restrict the ECERM feature.

chg_element dsp_error_inc 0 0

Where: is:
dsp_error_inc element name
0 value
0 location

System Response

WARNING: Setting this attribute to a value of 0 will result in no more DSP

alarms being generated for this BSS while the value remains 0.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

Example 15

In this example, the value of the database element gprs_mac_mode is changed to 2 when the
EDA feature is unrestricted.

chg_ele gprs_mac_mode 2 bsc

Where: is:
gprs_mac_mode element name
2 value
bsc location

3-120 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System Response

COMMAND ACCEPTED

Example 16

In this example, the value of the database element ext_ul_dur is changed to valid value (24 -
250) when the extended uplink TBF feature is unrestricted.

chg_element ext_ul_dur 24 0

Where: is:
ext_ul_dur element name
24 value
0 location

System Response

COMMAND ACCEPTED

Example 17

This example enables the functionality of the AGCH flow control, any one of the triggers
associated with IA and IAR can trigger AGCH overload.

chg_element agch_flow_control_mode 1 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
agch_flow_control_mode element name
1 value
1 location
5 4 3 2 1 61986 34944 cell description

System Response

COMMAND ACCEPTED

68P02901W23-T 3-121
Jan 2010
Examples Chapter 3: Device/function related commands

Example 18

In this example, the value of sig_lnk_tst_allow is changed to 0.

chg_elem sig_lnk_tst_allow 0 0

Where: is:
sig_lnk_tst_allow element name
0 value
0 location

System Response

COMMAND ACCEPTED

Example 19

In this example, the value of sig_lnk_tst_allow is changed to 1.

chg_elem sig_lnk_tst_allow 1 0

Where: is:
sig_lnk_tst_allow element name
1 value
0 location

System Response

COMMAND ACCEPTED

Example 20

This example modifies the value of fer_meas_period to 2 to double the measuring period.

chg_element fer_meas_period 2 0

Where: is:
fer_meas_period element name
2 value
0 location

System Response

COMMAND ACCEPTED

3-122 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 21

This example modifies the value of cstats_bss_enabled from 0 to 1 to enable the 5 minute
statistics uploading.

chg_element cstats_bss_enabled 1 0

Where: is:
cstats_bss_enabled element name
1 value
0 location

System Response

COMMAND ACCEPTED

Example 22

This example modifies the value of cstats_cell_enabled from 0 to 1 to enable the 5 minute
statistics uploading for cell 0 0 1 0 1 99 72 under site 114.

chg_element cstats_cell_enabled 1 114 cell 0 0 1 0 1 99 72

Where: is:
cstats_cell_enabled element name
1 value
114 location
0 0 1 0 1 99 72 cell description

System Response

COMMAND ACCEPTED

Example 23

This example modifies the value of power_save_enable to 1 on site 1 when SW enabler for PA
bias switch on/off on CTU2D feature is enabled.

chg_element power_save_enable 1 1

Where: is:
power_save_enable element name
1 value
1 location

68P02901W23-T 3-123
Jan 2010
Examples Chapter 3: Device/function related commands

System Response

COMMAND ACCEPTED

Example 24

This example attempts to modify power_save_enable on site 15 when the BTS is not a Horizon
II cabinet.

chg_element power_save_enable 1 15

Where: is:
power_save_enable element name
1 value
15 location

System Response

ERROR: The site location is not a power saving capable BTS type.
COMMAND REJECTED

Example 25

This example attempts to modify the value of the Abis status element to 0 to disable the Abis
connection for Horizon site (Site id = 1) when the Dual Abis Aware feature is enabled.

chg_element abis_state_element 0 1

Where: is:
abis_state_element element name
0 value
1 location

System Response

COMMAND ACCEPTED

3-124 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 26

This example attempts to modify the value of the Abis status element to 1 to enable the Abis
connection for Horizon site (Site id = 1). The site 1 is the relay node of a route to the BSC and
its downstream node (Site 2) can only connect to the BSC through site 1.

chg_element abis_state_element 1 1

Where: is:
abis_state_element element name
1 value
1 location

System Response

WARNING: Migrate this site may cause its downstream node sites to be isolated.
Are you sure (y=yes, n=no)? Y

COMMAND ACCEPTED

Example 27

This example attempts to modify the value of the Abis status element to 1 to enable the Abis
connection for the Horizonmacro site (Site id = 1) with a Horizon II mini expansion when the
Dual Abis Aware feature is enabled.

chg_element abis_state_element 1 1

Where: is:
abis_state_element element name
1 value
1 location

System Response

Error: Unsupported combination of cabinets for migration.

COMMAND REJECTED

68P02901W23-T 3-125
Jan 2010
Examples Chapter 3: Device/function related commands

Example 28

This example attempts to enable the Abis connections of all the BTS sites of the BSC when the
Dual Abis Aware feature is enabled. Ensure that each of the sites has a direct route to the BSC.

chg_element abis_state_element 1 all

Where: is:
abis_state_element element name
1 value
all location

System Response

WARNING: Enable Abis status for all the BTS sites under BSC?
Are you sure (y=yes, n=no)? Y
Site 0:
-----------
COMMAND REJECTED: Unallowable BTS type.

Site 10:
-----------
COMMAND REJECTED: BTS is not B-U.

Site 11:
-----------
COMMAND REJECTED: Unallowable BTS type.

COMMAND ACCEPTED: WARNING: Not all sites were updated; errors occurred.

Example 29

This example changes the value of the bsp_overload_protection parameter to 0.

chg_element bsp_overload_protection 0 bsc

Where: is:
bsp_overload_protection element name
0 value
bsc location

3-126 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

COMMAND ACCEPTED

Example 30

This example attempts to change the value of the bsp_overload_protection parameter to 2.

chg_element bsp_overload_protection 2 bsc

Where: is:
bsp_overload_protection element name
2 value
bsc location

System response

ERROR: Range Error, parameter number: 2

COMMAND REJECTED

Example 31

This example modifies the value of ss7_hsp_l2_t1 to 255000 when the increased network
capacity feature is enabled.

chg_element ss7_hsp_l2_t1 255000 0

Where: is:
ss7_hsp_l2_t1 element name
255000 value
0 location

System response

COMMAND ACCEPTED

68P02901W23-T 3-127
Jan 2010
Examples Chapter 3: Device/function related commands

Example 32

This example changes the value of tdm_switch to 1.

chg_element tdm_switch 1 0

Where: is:
tdm_switch element name
1 value
0 location

System response

COMMAND ACCEPTED

Example 33

This example changes the value of tdm_switch to 0.

chg_element tdm_switch 0 0

Where: is:
tdm_switch element name
0 value
0 location

System response

WARNING: TDM Availability Enhancements function will be disabled, if the

operator changes tdm_switch element.
Are you sure (y=yes, n=no)? y
COMMAND ACCEPTED

Example 34

This example attempts to modify the value of the Abis status element to 0 to disable the Abis
connection for H1 site (Site id = 1) when the Dual Abis Aware feature is enabled.

chg_element _site_data, 5 0 1

Where: is:
_site_data, 5 element name
0 value
1 location

3-128 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System Response

COMMAND ACCEPTED

Example 35

This example attempts to modify the value of the Abis status element to 1 to enable the Abis
connection for H1 site (Site id = 1). The site 1 is the relay node of a route to the BSC and its
downstream node (Site 2) can only connect to the BSC through site 1.

chg_element _site_data, 5 1 1

Where: is:
_site_data, 5 element name
1 value
1 location

System Response

WARNING: Migrate this site may cause its downstream node sites to be isolated.
Are you sure (y=yes, n=no)? Y

COMMAND ACCEPTED

Example 36

This example attempts to modify the value of the Abis status element to 1 to enable the Abis
connection for the Horizonmacro site (Site id = 1) with a Horizon II mini expansion when the
Dual Abis Aware feature is enabled.

chg_element _site_data, 5 1 1

Where: is:
_site_data, 5 element name
1 value
1 location

System Response

Error: Unsupported combination of cabinets for migration.

COMMAND REJECTED

68P02901W23-T 3-129
Jan 2010
Examples Chapter 3: Device/function related commands

Example 37

This example attempts to enable the Abis connections of all the BTS sites of the BSC when the
Dual Abis Aware feature is enabled. Ensure that each of the sites has a direct route to the BSC.

chg_element _site_data, 5 1 all

Where: is:
_site_data, 5 element name
1 value
all location

System Response

WARNING: Enable Abis status for all the BTS sites under BSC?
Are you sure (y=yes, n=no)? Y
Site 0:
-----------
COMMAND REJECTED: Unallowable BTS type.

Site 10:
-----------
COMMAND REJECTED: BTS is not B-U.

Site 11:
-----------
COMMAND REJECTED: Unallowable BTS type.

COMMAND ACCEPTED: WARNING: Not all sites were updated; errors occurred.

Example 38

This example attempts to enable baseband hopping (hopping_support = 2) when ext_pdchs

in any RTF of the cell > 0.

chg_element hopping_support 2 16

Where: is:
hopping_support element name
2 value
16 location

3-130 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System Response

COMMAND REJECTED: Value of ext_pdchs shall be 0 when Baseband hopping is enabled

for the cell.

COMMAND ACCEPTED

Example 39

This example attempts to enable asym_edge_enabled = 1 when ext_pdchs > 0 for any RTF
in the site.

chg_element asym_edge_enabled 1 16

Where: is:
asym_edge_enabled element name
1 value
16 location

System Response

COMMAND REJECTED: Value of ext_pdchs shall be 0 when ASYM feature is enabled for
the site

COMMAND ACCEPTED

Example 40

{26638}

This example enables the Gb over IP function.

chg_element gb_mode 1 0

Where: is:
gb_mode element name
1 value
0 location

68P02901W23-T 3-131
Jan 2010
Examples Chapter 3: Device/function related commands

System Response

WARNING: Static IP gb_mode requires PSI and PXP U-DPROCII to be configured.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

Example 41

{34416}

This example modifies the value of the power_save_enable parameter to 2 on site 1 when
the SW enabler for PA bias switch on/off on CTU2D and Using PA bias feature in mixed radio
Horizon II sites features are enabled.

chg_element power_save_enable 2 1

Where: is:
power_save_enable element name
2 value
1 location

System Response

COMMAND ACCEPTED

Example 42

{34452}

This example disables the mobile flow control for PS call.

chg_element ms_flow_control_enabled 0 0

Where: is:
ms_flow_control_enabled element name
0 value
0 location

System Response

COMMAND ACCEPTED

3-132 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 43

{34452}

This example modifies the value of the cstats_bss_enabled parameter to 1 to enable the 5
minutes statistics uploading.

chg_element cstats_bss_enabled 1 0

Where: is:
cstats_bss_enabled element name
1 value
0 location

System Response

COMMAND ACCEPTED

Example 44

{34452}

This example modifies the value of the cage_manage_enabled parameter to 1 to enable the
cage management feature.

chg_element cage_manage_enabled 1 0

Where: is:
cage_manage_enabled element name
1 value
0 location

System Response

COMMAND ACCEPTED

68P02901W23-T 3-133
Jan 2010
Examples Chapter 3: Device/function related commands

Example 45

{34452}

This example attempts to switch PRM detect mode to the PRM which does not send the USF to
the GPRS mobile in GMSK blocks.

chg_element gmsk_capability_mode 1 0

Where: is:
gmsk_capability_mode element name
1 value
0 location

System Response

COMMAND ACCEPTED

Example 46

{34452}

This example attempts to switch PUAK mode to forced compressed PUAK mode.

chg_element puak_compress_mode 1 0

Where: is:
puak_compress_mode element name
1 value
0 location

System Response

COMMAND ACCEPTED

3-134 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 47

{34452}

This example disables the AMR homing sequence filter.

chg_element amr_home_filter_enabled 0 0

Where: is:
amr_home_filter_enabled element name
0 value
0 location

System Response

COMMAND ACCEPTED

Example 48

{34452}

This example enables the function of using idle TCH for burst packet traffic.

chg_element congest_pd_expand_enabled 1 pcu

Where: is:
congest_pd_expand_enabled element name
1 value
pcu location

System Response

COMMAND ACCEPTED

68P02901W23-T 3-135
Jan 2010
Examples Chapter 3: Device/function related commands

Example 49

{34452}

This example modifies the value of the gprs_edge_mismatch_sigma parameter to 50 for

cell 0 0 1 0 1 99 72 under site 114.

chg_element gprs_edge_mismatch_sigma 50 114 cell 0 0 1 0 1 99 72

Where: is:
gprs_edge_mismatch_sigma element name
50 value
114 location
0 0 1 0 1 99 72 cell description

System Response

COMMAND ACCEPTED

Example 50

{34452}

This example modifies the value of the gprs_asym_mismatch_delta parameter to 50 for cell
0 0 1 0 1 99 72 under site 114.

chg_element gprs_asym_mismatch_delta 50 114 cell 0 0 1 0 1 99 72

Where: is:
gprs_asym_mismatch_delta element name
50 value
114 location
0 0 1 0 1 99 72 cell description

System Response

COMMAND ACCEPTED

3-136 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 51

{34452}

This example modifies the value of the edge_asym_mismatch_cita parameter to 50 for cell 0 0
1 0 1 99 72 under site 114.

chg_element edge_asym_mismatch_cita 50 114 cell 0 0 1 0 1 99 72

Where: is:
edge_asym_mismatch_cita element name
50 value
114 location
0 0 1 0 1 99 72 cell description

System Response

COMMAND ACCEPTED

Example 52

{34452}

This example modifies the value of the pch_queue_length_ctr parameter to 1 to set the PCH
queue length to 648 for cell 0 0 1 0 1 99 72 under site 114.

chg_element pch_queue_length_ctr 1 114 cell 0 0 1 0 1 99 72

Where: is:
pch_queue_length_ctr element name
1 value
114 location
0 0 1 0 1 99 72 cell description

System Response

COMMAND ACCEPTED

68P02901W23-T 3-137
Jan 2010
Examples Chapter 3: Device/function related commands

Example 53

{34452}

This example enables the function of Intelligent Selective Paging.

chg_element isp_enabled 1 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
isp_enabled element name
1 value
1 location
5 4 3 2 1 61986 34944 cell description

System Response

COMMAND ACCEPTED

Example 54

{34452}

This example enables the functionality of AGCH flow control, any one of the triggers associated
with IA and IAR can trigger AGCH overload.

chg_element agch_flow_control_mode 1 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
agch_flow_control_mode element name
1 value
1 location
5 4 3 2 1 61986 34944 cell description

System Response

COMMAND ACCEPTED

3-138 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 55

{34452}

This example modifies the value of the cstats_cell_enabled parameter from 0 to 1 to enable the
5 minutes statistics uploading for cell 0 0 1 0 1 99 72 under site 114.

chg_element cstats_cell_enabled 1 114 cell 0 0 1 0 1 99 72

Where: is:
cstats_cell_enabled element name
1 value
114 location
0 0 1 0 1 99 72 cell description

System Response

COMMAND ACCEPTED

Example 56

{34452}

This example modifies the value of the new_calls_amr_hr parameter to 70 at cell 0 0 1 0 1 1 1.

chg_ele new_calls_amr_hr 70 1 cell 0 0 1 0 1 1 1

Where: is:
new_calls_amr_hr element name
70 value
1 location
0010111 cell description

System Response

COMMAND ACCEPTED

68P02901W23-T 3-139
Jan 2010
Examples Chapter 3: Device/function related commands

Example 57

{34452}

This example modifies the value of the reconfig_fr_to_amr_hr parameter to 70 at cell 0 0

1 0 1 1 1.

chg_ele reconfig_fr_to_amr_hr 70 1 cell 0 0 1 0 1 1 1

Where: is:
reconfig_fr_to_amr_hr element name
70 value
1 location
0010111 cell description

System Response

COMMAND ACCEPTED

Example 58

{34452}

This example modifies the value of the inner_amr_hr_usage_thres parameter to 70 at cell 0 0

1 0 1 1 1.

chg_ele inner_amr_hr_usage_thres 70 1 cell 0 0 1 0 1 1 1

Where: is:
inner_amr_hr_usage_thres element name
70 value
1 location
0010111 cell description

System Response

COMMAND ACCEPTED

3-140 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 59

This example modifies the value of _bss_data,10 from 0 to 1 to enable the cage management
feature.

chg_element _bss_data,10 1 0

Where: is:
_bss_data,10 element name
1 value
0 location

System Response

COMMAND ACCEPTED

Example 60

When the TD-SCDMA inter-working feature (tdOpt) is unrestricted, change the value of
_bss_data,6 to 1 when the TD-SCDMA inter-working feature is disabled (td_enabled = 0).

chg_element _bss_data,6 1 0

Where: is:
_bss_data,6 element name
1 value
0 location

System Response

COMMAND ACCEPTED

Example 61

This example modifies the value of nacc_nc2_enabled from 0 to 1 to enable the NC2 mode
of NACC.

chg_element nacc_nc2_enabled 1 0

Where: is:
nacc_nc2_enabled element name
1 value
0 location

System Response

COMMAND ACCEPTED

68P02901W23-T 3-141
Jan 2010
Examples Chapter 3: Device/function related commands

Example 62

{36039G}

This example changes the value of the parameter to 1, when the Abis auto swap feature
(abisautoswapOpt) is enabled.

chg_element abis_auto_swap_enabled 1 0

Where: is:
abis_auto_swap_enabled element name
1 value
0 location

System Response

COMMAND ACCEPTED

Example 63

{36039G}

This example changes the value of the timer to 10, when the Abis auto swap feature
(abisautoswapOpt) is enabled.

chg_element t_terrestrial_fail 10 0

Where: is:
t_terrestrial_fail element name
10 value
0 location

System Response

COMMAND ACCEPTED

3-142 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 64

{36039G}

This example changes the value of the parameter to 1, when the Abis auto swap feature
(abisautoswapOpt) is enabled.

chg_element max_tx_bts_standby 1 13 cell = 0 0 1 0 1 121 13

Where: is:
max_tx_bts_standby element name
1 value
13 location
0 0 1 0 1 121 13 cell_desc

System Response

COMMAND ACCEPTED

Example 65

{36039G}

This example attempts to set the parameter to -1 in the cell which is residing in an extending
Horizon I micro cabinet, but the master cabinet is Horizon II macro.

chg_element max_tx_bts_standby 13 -1 cell = 0 0 1 0 1 121 13

Where: is:
max_tx_bts_standby element name
13 value
-1 location
0 0 1 0 1 121 13 cell_desc

System Response

Error: Such value can not be set to the cell contains DRI
not in Horizon II cabinet or not Single Density.
COMMAND REJECTED

68P02901W23-T 3-143
Jan 2010
References Chapter 3: Device/function related commands

References

Related information

Details of the database parameters that can be changed using this command are given in the
relevant parameter descriptions in Chapter 6 CM database parameters of this manual.

Related command

chg_element on page 3-112.

3-144 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference chg_hop_params

chg_hop_params

Description

The chg_hop_params command permits changing multiple hopping parameters for a site at one
time. The changes are verified outside SYSGEN and when exiting SYSGEN mode.

Synthesizer hopping and baseband hopping can be enabled in different cells at the same site. It
is also possible to mix non-hopping cells and hopping cells at the same site.

When the system accepts the chg_hop_params command for a particular cell, the system rejects
other chg_hop_params commands until the system reconfiguration due to the first command is
complete.

Once the system accepts the chg_hop_params command, the system displays a warning
message. If the system operator has enabled, disabled, or changed an enabled hopping system
which is synthesizer hopping through the BCCH RTF, the warning message states that the site
resets. The operator can abort the command to prevent a site reset.

If all FHIs for the cell are disabled, the operator can change hopping support from no hopping
to baseband hopping, or from no hopping to synthesizer hopping.

Although the chg_hop_params parameter allows a hopping system corresponding to a Dual

Band Cell to contain frequencies from either the primary or the secondary frequency band, it
does not allow both at the same time. If this is attempted, an error message displays.

Each cell takes about 90 seconds to finish the hopping reconfiguration.

If duplicated frequencies are entered, a warning message is presented. The system ignores
the duplicated frequencies. If this warning message occurs, the command must be re-entered
without the duplication.

This command runs the hopping verification on all cells in the specified site, even if the cells in
the site are not modified.

An EGPRS RTF cannot baseband hop in the same FHIs as non-EGPRS RTFs.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)

Prerequisites If hopping_systems verification fails, the system rejects this command

outside SYSGEN. The system does not verify hopping systems inside
SYSGEN until SYSGEN is off.

If the Extended Range feature is unrestricted:

Both timeslots in the Extended Range timeslot pair must have the
same FHI if they are part of a hopping system.

68P02901W23-T 3-145
Jan 2010
Format Chapter 3: Device/function related commands

Baseband and synthesizer hopping systems can only be configured

among timeslots of the same type (such as Extended or Normal).

Synthesizer Frequency Hopping systems in Extended Range cells

must have the FHIs for the BCCH carrier timeslots set to 0xffh
(255).
If a Remotely Tuneable Combiner is equipped at the cell, synthesizer
hopping is not allowed in a cell. The system rejects this command for
microsites that are not equipped with Horizonmicro or Horizoncompact
cabinets.

The same chg_hop_params command cannot be used to change hopping

support to 0 and disable an enabled FHI simultaneously.

When using SFH with GSM 1800, there is a limit of 18 frequencies when
the frequency range is set to more than 256. If the range is more than
112, only 29 frequencies are allowed. If the range is less than 112, only
64 frequencies are allowed.

In a GSM 850 cell, the ARFCN range is 128 - 251.

The master cabinet at the site must be a Horizon II macro in order for
an EGPRS RTF to baseband hop.

NOTE
This command can be entered only at the BSC. To change multiple hopping
parameters at a BTS site, contact the OMC-R for help.

Format

Syntax

chg_hop_params [<location>]

chg_hop_params [<cell_desc_opt>]

Input parameters

The location parameter and the cell_desc parameter cannot be used together in the
chg_hop_params command. If neither is entered, all cells at the location are assumed.

location

Specifies the site location:

0 or bsc BSC
1 - 140 BTS

cell_desc_opt

3-146 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

The GSM cell ID of the affected cell. cell_number= can precede the GSM cell ID.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

Only PCS1900 systems can use a three-digit MNC.

The cell_desc_opt can also be a cell name created using the cell_name command. When the
cell name is entered, it must be placed inside double quotation marks. cell_number= can
precede the cell name.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

Table 3-26 shows the baseband and synthesizer frequency hopping restrictions on the setting of
the chg_hop_params command. The numbers in the columns refer to the notes that follow.

Table 3-26 Baseband and Synthesizer frequency hopping restrictions

Synthesizer Frequency SFH through BCCH

FHI state Baseband
(SFH)
E = Enabled E D E D E D
D = Disabled
Enable FHI Yes Yes2,3 Yes Yes2,3 Yes Yes2,4
Disable FHI Yes3 Yes Yes3 Yes Yes4 Yes
Change MA No5 Yes2 Yes2,3,5 Yes2 Yes2,4 Yes
Change HSN Yes3 Yes Yes3 Yes Yes4 Yes
Change to no hopping No Yes No Yes No Yes
Change to baseband Yes Yes No No No No
Change to synthesizer No No Yes Yes Yes Yes

1. The reference to the Frequency Hopping Indicator (FHI) is only to that FHI assigned to
the BCCH RTF. All other FHIs in the cell are treated like the SFH column.

2. Performs hopping verification.

3. Notifies the Cell Resource Machine (CRM) of the changes made.

4. Causes the affected site to be reset.

5. The MA can be changed in synthesizer frequency hopping only as long as the new MA
contains all the ARFCNs of the equipped RTFs in the hopping system.

68P02901W23-T 3-147
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

In this example, FHIs 2 and 3 for cell 5 4 3 2 1 62259 8736 and FHI 0 and 2 for cell 0013211
have been disabled previously:

chg_hop_params 2

Where: is:
2 BTS site 2

System response

Hopping systems (FHIs) to be modified in cell 5 4 3 2 1 62259 (0xF333)

8736 (0x2220) (RETURN=no change for this cell): 3 2
Hopping support: 2
FHI 2 status (enable/disable):
Mobile allocation (ARFCNs) for FHI 3: 20 60 90
Mobile allocation (ARFCNs) for FHI 2: 20 30 70
HSN for FHI 2: 25
FHI 3 status (enable/disable): disable
HSN for FHI 3:
Hopping systems (FHIs) to be modified in cell 0 0 1 3 2 1 1
(RETURN=no change for this cell): 2 0
Hopping support: 2
FHI 0 status (enable/disable): 1
Mobile allocation (ARFCNs) for FHI 0: 21 31 71
HSN for FHI 0: 1
FHI 2 status (enable/disable): 1
Mobile allocation (ARFCNs) for FHI 2: 21 61 91
HSN for FHI 2:
WARNING: The site will be reset if the operator enabled, disabled or changed
an enabled hopping system which is synthesizer hopping through the BCCH RTF
Are you sure (y=yes, n=no) ? y

Responding n to the Are you sure? prompt aborts the command.

Example 2

In this example, hopping system 2 is disabled for cell 0 0 1 0 1 1 21 at site 7:

chg_hop_params cell_number=0 0 1 0 1 1 21

3-148 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Hopping systems (FHIs) to be modified in cell 0 0 1 0 1 1 21

cellname3 (RETURN=no change for this cell): 2 0
Hopping support: 2
FHI 2 status (enable/disable): 0
Mobile allocation (ARFCNs) for FHI 2:
HSN for FHI 2:
WARNING: The site will be reset if the operator enabled, disabled or changed
an enabled hopping system which is synthesizer hopping through the BCCH RTF
Are you sure (y=yes, n=no) ? y

NOTE
If PBCCH/PCCCH is enabled, hopping cannot be enabled on TS0 and TS1 (restriction
added with this feature) of the BCCH carrier. The WARNING is part of the output and
is printed even if the hopping system in use is baseband hopping.

Example 3

This example attempts to enable baseband hopping (hopping_support = 2) when ext_pdchs

in any RTF of the cell > 0.

chg_hop_params 0 0 1 0 1 1 21

Where: is:
0 0 1 0 1 1 21 cell description

System response

Hopping systems (FHIs) to be modified in cell 0 0 1 0 1 1 21

cellname3 (RETURN=no change for this cell): 2
Hopping support: 2
FHI 2 status (enable/disable):0
Mobile allocation (ARFCNs) for FHI 2:
HSN for FHI 2:
WARNING: The site will be reset if the operator enabled, disabled or changed
an enabled hopping system which is synthesizer hopping through the BCCH RTF
Are you sure (y=yes, n=no) ? y
COMMAND REJECTED: Value of ext_pdchs shall be 0 when Baseband hopping is enabled
for the cell.

68P02901W23-T 3-149
Jan 2010
Examples Chapter 3: Device/function related commands

Example 4

{34371G}

This example modifies the frequency hopping system of a cell.

chg_hop_params 2

Where: is:
2 location

System response

Warning: Baseband hopping with (R)CTU4-supported DRI and CTU2(D)-supported DRI

in the same hopping group is not supported.
Baseband frequency hopping and/or Synthesiser frequency hopping using (R)CTU4
requires that all carriers in the hopping group reside within a 20MHz bandwidth.

Hopping systems (FHIs) to be modified in cell 001 01 1 (0001h) 3 (0003h)

(RETURN=no change for this cell):1
Hopping support:2
FHI 1 status (enable/disable):1
Mobile allocation (ARFCNs) for FHI 1:45 55 65
HSN for FHI 1:1

WARNING: The site will be reset if the operator enabled, disabled, or changed
an enabled hopping system which is synthesizer hopping through the BCCH RTF.

Are you sure (y=yes,n=no)? y

3-150 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related information

Table 3-27 lists the prompts for the chg_hop_params command; x indicates a value supplied
by the system.

Table 3-27 chg_hop_params prompts

Prompt Range Default

Hopping support: 0-2 0
where:
0 = No hopping in this cell
1 = Synthesizer hopping
2 = Baseband hopping
See NOTE.
FHI x status 0 or 1 0
(enable/disable): where:
0 = disable the hopping system
1 = enable the hopping system
Mobile allocation ARFCN depends on the frequency type for the Current value
(ARFCNs) for FHI x: cell.
If the cell is PGSM the range is 1 - 124.
If the cell is EGSM the range is either:

1 to 124, or

975 to 1023
If using EGSM, all of the specified ARFCNs
must be in the lower range (1 - 124) or the
higher range (975 - 1023, 0).
If the cell is DCS1800, the range is 512 - 885.
If the cell is PCS1900 the range is 512 - 810.
For GSM850, the ARFCN range is 128 - 251.
HSN for FHI x: 0 - 63 Current value
where:
0 is cyclic, and
1 - 63 is random

68P02901W23-T 3-151
Jan 2010
References Chapter 3: Device/function related commands

NOTE
If any FHIs are enabled, hopping support cannot be 0.

The system rejects the chg_hop_params command if:

(1) hopping support: = 1 and the Synthesizer Hopping feature is restricted or

(2) hopping support: = 2 and the Baseband Hopping feature is restricted.

Table 3-28 lists the maximum number of frequencies in the mobile allocation. The table also
provides the frequency range of the cell (which includes a combination of PGSM and GSM
Extension band frequencies) as determined by System Information Type 1 size limitations in the
GSM 04.08 Specification Annex J and Cell Channel Description.

Table 3-28 Cell frequencies/mobile allocation

Frequencies of the cell (ARFCNs used) Maximum number of frequencies in the mobile allocation
1 - 124 64
975 - 1023 49
1 - 124, 975 - 1023 16
0, 1 - 124 17
0, 957 - 1023 17
0, 1 - 124, 975 - 1023 17

Related command

disp_hopping on page 3-356.

Table 3-29 lists the restrictions on related commands.

3-152 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 3-29 Restrictions on related commands

Current hopping chg_hop_params command

support and FHI change hopping
status disable FHI enable FHI change MA change HSN
support
Baseband Command Command Command Command Command
hopping FHI allowed allowed rejected; allowed. rejected.
is enabled cannot FHI must be
change MA disabled before
of an enabled changing hopping
FHI. support
Disable the
FHI and
equip the
RTF before
changing the
MA
Baseband Command Command Command Command Command allowed
hopping FHI allowed allowed. allowed allowed
is disabled
Synthesizer Command Command Command Command Command
hopping FHI allowed allowed allowed. allowed rejected.
is enabled MA can FHI must be
change so disabled before
long as the changing hopping
new MA support
contains
all the
ARFCNs of
the equipped
RTFs in the
hopping
system.
Synthesizer Command Command Command Command Command allowed
hopping FHI allowed allowed allowed allowed
is disabled
Synthesizer Command Command Command Command Command
through BCCH allowed; allowed allowed; allowed; rejected.
hopping FHI is resets the resets the resets the FHI must be
enabled site site site disabled before
changing hopping
support
Synthesizer Command Command Command Command Command allowed
through BCCH allowed allowed; allowed allowed
hopping FHI is resets the
disabled site

68P02901W23-T 3-153
Jan 2010
chg_ksw_config Chapter 3: Device/function related commands

chg_ksw_config

Description

The chg_ksw_config command indicates how KSWs are physically connected when two or
more KSW pairs are equipped at a site. KSWs are connected through the EXP KSWX cards to
form a larger switching network.

The TDM highway of a site can consist of up to four portions. A different KSW pair handles
each portion. The first identifier of a KSW is the portion of the TDM highway handled by that
KSW. The highway portions are defined as:

Highway Portion 0 TDM timeslots 0 - 1023 handled by KSW pair 0.

Highway Portion 1 TDM timeslots 1024 - 2047 handled by KSW pair 1.
Highway Portion 2 TDM timeslots 2048 - 3071 handled by KSW pair 2.
Highway Portion 3 TDM timeslots 3072 - 4095 handled by KSW pair 3.

Two TDM highways are supported, TDM 0 and TDM 1. One TDM highway is active and the other
is a redundant standby. KSW 0 0, KSW 1 0, KSW 2 0, and KSW 3 0 can be interconnected to
form TDM 0. KSW 0 1, KSW 1 1, KSW 2 1, and KSW 3 1 can be interconnected to form TDM 1.
The second KSW identifier indicates to which TDM highway the KSW belongs.

Expansion KSW (KSWX) cards are used to interconnect the KSW pairs. The KSWX cards are
required in each cage with a KSW pair. The chg_ksw_config command specifies the fiber optic
connections between the KSWX cards. The KSWX cards for TDM 0 are located in slots U21,
U22, and U23. The KSWX cards for TDM 1 are located in slots U9, U8, and U7. The KSWX
fiber optic connections for TDM 1 must match the KSWX fiber optic connections for TDM 0.
The KSWX in slot U9 mirrors the connections of the KSWX in slot U21. The KSWX in slot U8
mirrors the connections of the KSWX in slot U22. The KSWX in slot U7 mirrors the connections
of the KSWX in slot U23.

A chg_ksw_config command is required for each KSW pair equipped at the site when more than
one KSW pair is equipped. Only one command is required per KSW pair because the fiber optic
connections for TDM 0 and TDM 1 match.

A warning prompt displays when this command is entered, from which the operator can abort
the command.

A warning displays when coming out of SYSGEN mode if each set of TDM highway identifiers
are not unique in each cage.

3-154 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

The command is only issued for InCell sites. The command does not apply to M-Cell sites.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites See the Service Manual BSC/RXCDR (68P02901W38) for
information regarding the hardware layout of the KSW
pairs.
Operator actions Check the information regarding the hardware layout of
the KSW pairs.
Respond to the warning prompt after entry of the command.
This command is executed in or out of SYSGEN mode.

Format

Syntax

chg_ksw_config <location> <ksw_pair> <kswx_connected_to_hwy_0>

[<kswx_connected_to_hwy_1>] [<kswx_connected_to_hwy_2>]
[<kswx_connected_to_hwy_3>]

Input parameters

location

Specifies the KSW location:

0 or bsc BSC or RXCDR

1 - 140 BTS

ksw_pair

The KSW pair being configured. The range of values is 0 - 3:

0 KSW pair 0 corresponds to KSW 0 0 and KSW 0 1

1 KSW pair 1 corresponds to KSW 1 0 and KSW 1 1
2 KSW pair 2 corresponds to KSW 2 0 and KSW 2 1
3 KSW pair 3 corresponds to KSW 3 0 and KSW 3 1

kswx_connected_to_hwy_0

The KSWX pair that connects this KSW pair to highway portion 0. The KSWX pair is in the same
cage as the KSW pair being configured. Valid values are 0 - 3.

68P02901W23-T 3-155
Jan 2010
Examples Chapter 3: Device/function related commands

KSWX pairs are defined as:

0 The highway portion is the same as the KSW pair being configured.
1 KSWX cards in slots U21 (EXP KSWX A0) and U9 (EXP KSWX B0).
2 KSWX cards in slots U22 (EXP KSWX A1) and U8 (EXP KSWX B1).
3 KSWX cards in slots U23 (EXP KSWX A2) and U7 (EXP KSWX B2).

kswx_connected_to_hwy_1

The KSWX pair that connects this KSW pair to highway portion 1. The KSWX pair is in the same
cage as the KSW pair being configured. This parameter is not required if KSW pairs 1, 2, and
3 are not equipped. Valid values are 0 - 3.

kswx_connected_to_hwy_2

The KSWX pair that connects this KSW pair to highway portion 2. The KSWX pair is in the same
cage as the KSW pair being configured. This parameter is not required if KSW pairs 2 and
3 are not equipped. Valid values are 0 - 3.

kswx_connected_to_hwy_3

The KSWX pair that connects this KSW pair to highway portion 3. The KSWX pair is in the same
cage as the KSW pair being configured. This parameter is not required if KSW pair 3 is not
equipped. Valid values are 0 - 3.

Examples

Example 1

This example describes the KSWX fiber optic connections for a standard 4 cage expanded BSC
with redundancy. The chg_ksw_config commands for configuring the following expanded
setup are described.

CAGE 0:

KSW 0 0 and KSW 0 1 (KSW Pair 0) are equipped in CAGE 0

KSWX in slot U21 is connected to KSWX in cage 1 slot U21

KSWX in slot U22 is connected to KSWX in cage 2 slot U21

KSWX in slot U23 is connected to KSWX in cage 3 slot U21

KSWX in slot U9 is connected to KSWX in cage 1 slot U9

KSWX in slot U8 is connected to KSWX in cage 2 slot U9

KSWX in slot U7 is connected to KSWX in cage 3 slot U9

CAGE 1:

KSW 1 0 and KSW 1 1 (KSW pair 1) are equipped in CAGE 1

KSWX in slot U21 is connected to KSWX in cage 0 slot U21

KSWX in slot U22 is connected to KSWX in cage 2 slot U22

3-156 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

KSWX in slot U23 is connected to KSWX in cage 3 slot U22

KSWX in slot U9 is connected to KSWX in cage 0 slot U9

KSWX in slot U8 is connected to KSWX in cage 2 slot U8

KSWX in slot U7 is connected to KSWX in cage 3 slot U8

CAGE 2:

KSW 2 0 and KSW 2 1 (KSW pair 2) are equipped in CAGE 2

KSWX in slot U21 is connected to KSWX in cage 0 slot U22

KSWX in slot U22 is connected to KSWX in cage 1 slot U22

KSWX in slot U23 is connected to KSWX in cage 3 slot U23

KSWX in slot U9 is connected to KSWX in cage 0 slot U8

KSWX in slot U8 is connected to KSWX in cage 1 slot U8

KSWX in slot U7 is connected to KSWX in cage 3 slot U7

CAGE 3:

KSW 3 0 and KSW 3 1 (KSW pair 3) are equipped in CAGE 3

KSWX in slot U21 is connected to KSWX in cage 0 slot U23

KSWX in slot U22 is connected to KSWX in cage 1 slot U23

KSWX in slot U23 is connected to KSWX in cage 2 slot U23

KSWX in slot U9 is connected to KSWX in cage 0 slot U7

KSWX in slot U8 is connected to KSWX in cage 1 slot U7

KSWX in slot U7 is connected to KSWX in cage 2 slot U7

The commands for configuring the expansion are:

chg_ksw_config 0 0 0 1 2 3

chg_ksw_config 0 1 1 0 2 3

chg_ksw_config 0 2 1 2 0 3

chg_ksw_config 0 3 1 2 3 0

68P02901W23-T 3-157
Jan 2010
Examples Chapter 3: Device/function related commands

For example, in the command chg_ksw_config 0 2 1 2 0 3 for KSW pair 2:

Parameter... with indicates that...

value...
location
ksw_pair
kswx_connected_to_hwy_0
kswx_connected_to_hwy_1
kswx_connected_to_hwy_2
kswx_connected_to_hwy_3
0 this parameter is the BSC.
2 this parameter is for the KSW pair 2 which
is in cage 2.
1 the KSWXs in slot U21 and U9 in the cage
with KSW pair 2, connect to the cage with
KSW pair 0.
2 the KSWXs in slot U22 and U8 in the cage
with KSW pair 2, connect to the cage with
KSW pair 1.
0 the highway number is the same as the KSW
pair number.
3 the KSWXs in slot U23 and U7 in the cage
with KSW pair 2, connect to the cage with
KSW pair 3.

Example 2

Slot U7 can contain a CLKX card or a KSWX card. If a chg_ksw_config command applies to slot
U7, the BSC checks to see if a CLKX card has been equipped in the slot. CLKX slot utilization is
specified in the GCLK equip command. In this example, the BSC rejects a change because a
CLKX has been equipped in slot U7:

equip 0 gclk

System response

Enter the device identifier for the GCLK: 0

Enter the cage number: 0
Is CLKX 0 (slot U7) present?: yes
Is CLKX 1 (slot U6) present?: no
Is CLKX 2 (slot U5) present?: no
COMMAND ACCEPTED
MMI-RAM 0115 ->

chg_ksw_config bsc 0 0 3 2 1

COMMAND REJECTED: Slot U7 is in use by a CLKX card.

3-158 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related command

disp_element on page 3-294.

68P02901W23-T 3-159
Jan 2010
chg_level Chapter 3: Device/function related commands

chg_level

Description

The chg_level command is a dummy command provided to support customer scripts which
require this command to change to a different security level.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

chg_level

Input parameters

There are no input parameters since the command is interactive.

Examples

Example 1

In the following example, the security level is not changed. The password is not displayed
when entered:

chg_level

System response

Enter password for security level you wish to access: 3stooges

Enter password for security level you wish to access: 4beatles
Current security level is unchanged

3-160 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 2

In the following example, the security level is not changed. The password is not displayed
when entered:

chg_level

System response

Enter password for security level you wish to access: anything

Enter password for security level you wish to access: random
Current security level is unchanged

References

Related command

disp_level on page 3-361.

68P02901W23-T 3-161
Jan 2010
chg_rtf_freq Chapter 3: Device/function related commands

chg_rtf_freq

Description

The chg_rtf_freq command changes the absolute radio frequency channel for a particular RTF.

This operation causes a carrier to be taken out of service. Calls are lost if no other carrier is
available.

A long warning prompt is presented when this command is invoked. The operator aborts the
command at the warning.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites In a synthesizer hopping system:

If the frequency is already defined as hopping in all

the RTF hopping systems, a new frequency is added
when hopping is enabled. Applicable for non-BCCH
RTF only.

If FHIs are enabled, it is not allowed for BCCH RTFs.

The new frequency is added when hopping is disabled

regardless of whether the frequency is already a
hopping frequency.
In a baseband hopping system:

This command is rejected outside SYSGEN ON mode if

the RTF has hopping FHIs and any FHIs are enabled.

This command automatically updates the frequency in

the mobile allocation if all associated FHIs are disabled
and the original frequency is already in the MA list.
In a Dual Band system:

When the Dual Band Cells option is enabled, the

frequency type is managed on a per zone basis.
Primary band carriers are configured in the outer zone
and secondary band carriers are configured in the
inner zone.

3-162 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Description

To have different DRI/RTF group identifiers, the BSS

requires DRI/RTFs within a cell to have different
frequency types.

When the inner_zone_alg parameter is set to

3 (specifying Dual Band), the frequency type as
defined by the secondary band determines the
ARFCN range for an inner zone RTF.

The BSS requires primary and secondary band

RTFs in a Dual Band Cell to be configured with the
DRI/RTF group identifier associated with their band.
If there is an attempt to use the same DRI/RTF
group identifier for RTFs in both the primary and
secondary bands of a Dual Band Cell, an error
message is printed and the command is rejected.

The cabinets to which the DRIs in each zone are

equipped must allow the primary and secondary
band frequency types.
Dependencies In PCS 1900 systems, the maximum transmit power
(max_tx_bts) limits the frequency entered. If the
frequency is a block edge ARFCN, the max_tx_bts must
be greater than or equal to 4 (less than 36 dBm) unless
one of the following are true:

The block edge ARFCN is between the adjacent

frequency blocks that are available to the BTS.
ARFCNs 512 and 810 are always limited.

The inner_zone_alg parameter is set in a

chg_cell_element command to value 1. That
is, Concentric Cell feature enabled and the
power-based use algorithm used. The block edge
frequency is defined to be an inner zone carrier with
a maximum transmit power level less that 36 dBm.
Block edges are 512, 585, 587, 610, 612, 685, 687,
710, 712, 735, 737, and 810.
Operator actions Respond to the warning prompt presented when this
command is entered.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

68P02901W23-T 3-163
Jan 2010
Format Chapter 3: Device/function related commands

Format

Syntax

chg_rtf_freq <frequency> <location> <rtf_id1> <rtf_id2>

Input parameters

frequency

Identifies the absolute radio frequency channel. The range of valid values varies by frequency
type.

The range of values is:

1 - 124 (PGSM)
0, 1 - 124, 975 - 1023 (EGSM)
512 - 885 (DCS1800)
512 - 810 (PCS1900)
128 - 251 (GSM850)

NOTE
The EGSM values are available only if the egsm_bcch_sd parameter is enabled.

location

Specifies the radio frequency channel location:

0 or bsc BSC
1 - 140 BTS

rtf_id1

First device identifier. The range of values is 0 - 5.

rtf_id2

Second device identifier. The range of values is 0 - 11.

3-164 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

This example changes the frequency channel to 99 for RTF 5 11 at BTS 40.

chg_rtf_freq 99 40 5 11

Where: is:
99 frequency
40 location
5 rtf_id1
11 rtf_id2

System response

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.

Are you sure (y=yes,n=no)?

COMMAND ACCEPTED

Example 2

{34371G}

This example attempts to change the frequency of one RTF which has been preferred by one
(R)CTU4 DRI. The new frequency is out of range of (R)CTU4 20MHz working bandwidth.

chg_rtf_freq 3 23 0 1

Where: is:
3 frequency
23 location
0 rtf_id1
1 rtf_id2

System response

COMMAND REJECTED: The preferred RTF(s) on (R)CTU4 violate 20MHz restriction.

68P02901W23-T 3-165
Jan 2010
References Chapter 3: Device/function related commands

References

Related information

The range of values for GSM Phase 2 is:

PGSM RTF_BCCH 1 - 124

RTF_NON_BCCH 1 - 124
EGSM RTF_BCCH 1 - 124
RTF_NON_BCCH 1 - 124 or
0, 975 - 1023
DCS1800 RTF_BCCH 512 - 885
RTF_NON_BCCH 512 - 885
PCS1900 RTF_BCCH 512 - 810
RTF_NON_BCCH 512 - 810

Related commands

add_rtf_path on page 3-50 copy_path on page 3-207 del_rtf_path on page 3-224

disp_rtf_path on page 3-422

3-166 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference chg_severity

chg_severity

Description

The chg_severity command changes the severity of device and non-reconfiguration alarms.

The number of alarms that can be modified is limited to 100.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

NOTE
Enter this command at the BSC or RXCDR only. This command does not work at a
BTS site. Contact the OMC-R for help.

Format

Syntax

chg_severity <device_name> <alarm_code> <severity>

Input parameters

device_name

The name of the device, such as GPROC, MSI or DRI, to be modified.

alarm code

The decimal number identifying the alarm code for the device to be modified.
Refer to Alarm devices on page 3-20 for the ranges of alarm codes for each device.

Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26)

manual for a list of all alarms and the corresponding alarm codes for each device.

68P02901W23-T 3-167
Jan 2010
Examples Chapter 3: Device/function related commands

severity

The desired severity for the alarm. The available values are:

investigate
critical
major
minor
warning

Examples

Example 1

This example shows how to change the severity of GPROC alarm code 8 from MAJOR to
CRITICAL.

chg_severity gproc 8 critical

Where: is:
gproc device_name
8 alarm_code
critical severity

System response

COMMAND ACCEPTED

Example 2

{34282}

This example changes the severity of the GPROC alarm code 54 to MAJOR.

chg_severity GPROC 54 major

Where: is:
GPROC device_name
54 alarm_code
major severity

3-168 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

COMMAND ACCEPTED

References

Related command

disp_severity on page 3-424.

68P02901W23-T 3-169
Jan 2010
chg_smscb_msg Chapter 3: Device/function related commands

chg_smscb_msg

Description

The chg_smscb_msg command changes a selected CBCH background message and the language
in which it is presented. Message numbers uniquely identify the background messages.

The background message in all cells at all sites connected to the BSC can be modified.

When the command is entered, the MMI responds with an Enter the message prompt. Enter
the CBCH background message after the MMI prompt. The GSM standard message can
consist of up to 93 characters, entered in hexadecimal or ASCII notation, and terminated by
pressing the RETURN key. The ASCII and hexadecimal methods of input can be interspersed in
the same message.

The following two messages are equivalent:

Motorola Cellular

\4d\6f\74\6f\72\6f\6c\61 \43\65\6c\6c\75\6c\61\72

Because terminals handle automatic truncation in different ways, it is recommended that

messages longer than one line are truncated explicitly by the operator, to form strings shorter
than the length of one line. A message can be truncated anywhere by keying \ followed by
RETURN. The \ must not separate a hexadecimal character otherwise the two parts read as two
separate ASCII characters.

The message created using this command is displayed using the disp_cbch_state command.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites Short Message Service (SMS) is a purchasable option
which must be installed on the system. The chg_element
cbch_enabled command must be used before the
chg_smscb_msg command is successfully used.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

3-170 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Format

Syntax

chg_smscb_msg <msg_num> <message_id> <gs> <msg_code> <update_number>

<data_coding_scheme><cell_desc>

chg_smscb_msg <msg_num> <message_id> <gs> <msg_code> <update_number>

<data_coding_scheme>all

Input parameters

msg_num

Uniquely identifies the number of the message for a given cell. The range of values is 0 - 3.

message_id

The ITU standard identifier for the background message. The range of values is 0 - 65535.

gs

Geographical scope. This parameter indicates the area over which the message is unique.
The range of values is 0 - 3, where:

0 Immediate, Cell Wide

1 Normal, PLMN Wide
2 Normal, Location Area Wide
3 Normal, Cell Wide

msg_code

The ITU standard message code; used to differentiate between messages of the same source
and type. The range of values is 0 - 1023.

update_number

Refers to the number of an update to an existing message. The range of values is 0 - 15. This
number used to be automatically incremented for each update to a message. As an input
parameter, it now allows the operator to specify a particular update. For example, the same
update of a message in a new cell is used as in the existing cells.

68P02901W23-T 3-171
Jan 2010
Format Chapter 3: Device/function related commands

data_coding_scheme

This parameter determines the language for the CBCH background message. The following
languages are available:

0 - German 7 - Danish 14 - Polish

1 - English 8 - Portuguese 32 - Czech

2 - Italian 9 - Finnish
3 - French 10 - Norwegian
4 - Spanish 11 - Greek
5 - Dutch 12 - Turkish
6 - Swedish 13 - Hungarian

NOTE
The values of 15 - 31 and 33 - 255 are not specified for the data_coding_scheme.
Only the listed languages are currently available.

cell_desc

The GSM cell identifier (either the cell name or cell number) for the cell being modified.

GSM cell ID of the cell to be modified, preceded by cell_number=.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format is enabled.

The name of the cell created using the cell_name command is entered in place of the
cell_number. When the cell name is entered, it must be placed inside double quotation marks
and cell_name= must precede it.

The value all is a valid input for cell_desc; this value changes the specified messages for
all cells at the BSS.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

3-172 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

This example changes the CBCH background message for cell_desc=5 4 3 2 1 61986 34944 to
have a message number of 0, a message ID of 1234, a geographical scope of 2, a message code
of 0, an update number of 0, and a language ID of 1.

chg_smscb_msg 0 1234 2 0 0 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
0 message_number
1234 message_id
2 geographical_scope
0 message_code
0 update_number
1 data_coding_scheme
cell_number=5 4 3 2 1 61986 cell_desc
34944

System response

Enter the Message:

<This is the first line of the message

. . . .

This is the last line of the message.>

COMMAND ACCEPTED

68P02901W23-T 3-173
Jan 2010
References Chapter 3: Device/function related commands

Example 2

This example changes the CBCH background message for all cells to have a message ID of
1234 and a language ID of 1.

chg_smscb_msg 0 1234 2 0 0 1 all

Where: is:
0 message_number
1234 message_id

2 geographical_scope
0 message_code
0 update_number
1 data_coding_scheme
all cell_desc; indicates changes to all cells

System response

Enter the Message:

<This is the only line of the message.>

COMMAND ACCEPTED

References

Related information

Table 3-30 lists SMS special characters. Alphabetical characters that cannot be directly entered
from the keyboard are included in messages by using the backslash (\) character followed by a
two character value. The first character is a number from 0 to 7. The second character is a
hexadecimal value (0 to F) corresponding to the row in the table. For example, the city of Kln
could be included in a message by entering K\7Cln.

Table 3-30 SMS special characters

0 1 2 3 4 5 6 7
0 @ Space 0 P p
1 _ ! 1 A Q a q
2 $ 2 B R b r
3 # 3 C S c s
4 4 D T d t

Continued

3-174 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 3-30 SMS special characters (Continued)

0 1 2 3 4 5 6 7
5 % 5 E U e u

6 & 6 F V f v

7 ' 7 G W g w

8 ( 8 H X h x

9 ) 9 I Y i y
A Line * : J Z j z
Feed
B Not + ; K k
Used
C , < L l
D Carriage - = M m
Return
E . > N n

F / ? O o

GSM technical specification

The permitted alphabet is defined in 03.38.

Related commands

del_smscb_msg on page 3-226 disp_cbch_state on page 3-257

68P02901W23-T 3-175
Jan 2010
chg_throttle Chapter 3: Device/function related commands

chg_throttle

Description

The chg_throttle command changes the throttle period for an intermittent alarm.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

chg_throttle <device_name> <alarm_code> <throttle_count>

Input parameters

device_name

Name that uniquely identifies the device.

alarm_code

Identifies the alarm to be throttled; the range is 0 - 254. Some of the codes are obsolete, refer
to the manual Maintenance Information: Alarm handling at the OMC-R (68P02901W26) for
usable alarm codes.

throttle_count

Specifies the new throttle count in minutes. A value of 0 means throttling is disabled. The
range of values is 0 - 1440.

3-176 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Example

This example changes the throttle period for alarm code 1 of an MMS to 10 minutes.
chg_throttle mms 1 10

Where: is:
mms device_name
1 alarm_code
10 throttle_count

System response

COMMAND ACCEPTED

References

Related command

disp_throttle on page 3-427.

68P02901W23-T 3-177
Jan 2010
chg_time Chapter 3: Device/function related commands

chg_time

Description

The chg_time command sets the real-time system clock. The clock can be set to a specific date
and time of day or changed relative to the current time of day. The relative change is useful for
changing the clock for daylight savings time.

Security level 4
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

chg_time <year> <month> <day> <hour> <minute> <second>

or
chg_time <+/-> <hours> <minutes>

Input parameters

year

Value identifying the year. The year is entered in the four-digit format. The range of values
is 1980 - 2100.

month

Value identifying the month. The range of values is 1 - 12.

day

Value identifying the day of the month. The range of values is 1 - 31.

3-178 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

<+/->

A plus or minus, as the first argument, adds or subtracts the specified number of hours and
minutes from the current time on the system clock.

hour

Value identifying the hour. The range of values is 0 - 23. This value can also be used to specify
the number of hours to be added or subtracted to the current system time.

minute

Value identifying the minute. The range of values is 0 - 59.

This value can also be used to specify the number of minutes to be added or subtracted to
the current system time.

second

Value identifying the second. The range of values is 0 - 59.

Examples

Example 1

In this example, the system clock is set to year (1993), month (November), day (12th), and
time (09:23:00):

chg_time 1993 11 12 9 23 0

Where: is:
1993 year
11 month
12 day
9 hour
23 minute
0 second

System response

Mon Nov 12 09:23:00 1993

68P02901W23-T 3-179
Jan 2010
References Chapter 3: Device/function related commands

Example 2

In this example, one hour is added to the current time for daylight savings time:

chg_time + 1 0

Where: is:
+ add to the system clock time.
1 hours to be added.
0 minutes to be added.

System response

Mon Nov 12 10:23:00 1995

References

Related commands

chg_throttle on page 3-176 time_stamp on page 3-611

3-180 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference chg_ts_usage

chg_ts_usage

Description

The chg_ts_usage command does the following:

Reserves timeslots

Nails timeslots

Frees reserved timeslots

Frees nailed timeslots

The chg_ts_usage command supports the following operations:

RESERVE This operation reserves timeslots. A timeslot cannot be used for any
connections when it is reserved.
FREE This operation frees timeslots that have been reserved or nailed using
the NAIL or RESERVE operations. It does not free timeslots that have
been nailed using the NAIL_PATH operation. Timeslots freed using
this operation become unused and can be used for any connections.
FREE_PATH This operation frees the timeslots of a NAIL_PATH nailed connection
between different sites. Timeslots freed using this operation become
unused and can be used for normal connections.
NAIL This operation establishes a nailed connection between two timeslots
at the same site.
NAIL_PATH This operation establishes a nailed connection between two timeslots
at different sites.

The E1 timeslot mapping on an HDSL link that supports 16 E1 timeslots restricts the timeslots
available to a number within the range 0 - 31.

The number of timeslots that can be RESERVE, NAIL, FREE_PATH, or NAIL_PATH is restricted
to 1 on HDSL links where only 16 timeslots are available.

The system rejects a chg_ts_usage nail_path command when the path contains a ts_switch.

Security level 4
Supported by OMC-R GUI No
Command type B (operator actions)
Prerequisites MSIs must be equipped before timeslots can be nailed or
reserved using the chg_ts_usage command.
The system rejects the chg_ts_usage command when a 16
kbit/s XBL link is equipped on the timeslot.
Operator actions Respond to command prompts.

68P02901W23-T 3-181
Jan 2010
Format Chapter 3: Device/function related commands

NOTE
Enter this command at the BSC and RXCDR only. This command does not work at a
BTS site. Contact the OMC-R for help.

Format

Syntax

chg_ts_usage

The system responds with a series of prompts for input parameters dependent on the action
requested.

Input parameters

The parameters used with this command are prompted for in the system response and are
dependent upon the specified operation. Refer to the descriptions for function and valid values
of the input parameter prompts:

Enter Action:

The type of operation to be performed. This field is entered as upper or lower case characters
with one of:

RESERVE Reserve timeslots.

FREE Free timeslots that have been reserved or nailed using the NAIL or
RESERVE operations.
NAIL Establish a nailed connection between two timeslots at the same site.
FREE_PATH Free the timeslots of a nailed connection between different sites.
NAIL_PATH Establish a nailed connection between two timeslots at different sites.

Enter Site Identifier:

Specifies the location of the MMS at one end of the E1 Mbit/s link for FREE, RESERVE, and
NAIL operations only. Values are:

0 or bsc BSC
1 to 140 BTS

Enter MMS 1 Identifiers:

First and second identifiers of the MMS at one end of the E1 link. Values are:

3-182 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

First identifier:
0 to 55 BSC
0 to 123 RXCDR
0 to 9 BTS
Second identifier:
0 or 1
0 to 5 for
Horizon II site.

Enter MMS 2 Identifiers:

First and second identifiers of the MMS at the other end of the E1 link. Values are:

First identifier:
0 to 55 BSC
0 to 123 RXCDR
0 to 9 BTS
Second identifier:
0 or 1
0 to 5 for
Horizon II site.

Enter Starting Timeslot:

First of the contiguous timeslots to be reserved or freed using the RESERVE or FREE operations
only. Values are:

1 to 31 For 2.048 Mbit/s E1 Links, including a 32/16 timeslot HDSL link

Enter Starting Timeslot for MMS 1:

Start timeslot number for MMS1 used with the NAIL, NAIL_PATH, or FREE_PATH operations
only. Values are:

1 to 31 For 2.048 Mbit/s E1 Links

Enter Starting Timeslot for MMS 2:

Start timeslot number for MMS2 used with the Nail, NAIL_PATH, or FREE_PATH operations
only. Values are:

1 to 31 For 2.048 Mbit/s E1 Links

Enter Start Site:

68P02901W23-T 3-183
Jan 2010
Examples Chapter 3: Device/function related commands

The start SITE to be nailed or freed using the NAIL_PATH or FREE_PATH operations only.
Values are:

0 to 100 BSC or BTS

Enter End Site:

The end SITE to be nailed or freed using the NAIL_PATH or FREE_PATH operations only.
Values are:

0 to 100 BTS or BSC

Enter Path Identifiers

The PATH to be nailed or freed using the NAIL_PATH or FREE_PATH operations only. This
represents the terminating site of the path. Values are:

0 to 100 BSC or BTS

Enter Number of Timeslots Requested:

The number of contiguous timeslots to be reserved, nailed, or freed. Values are:

1 to 31 For 2.048 Mbit/s E1 Links

Examples

Example 1

In this example, the contiguous timeslots from 16 through 31 at BTS 26 for MMS 1 0 are
reserved:

chg_ts_usage

System response

Enter action: RESERVE

Enter Site Identifier: 26

Enter MMS Identifiers: 1 0

Enter Starting Timeslot: 16

Enter Number of Timeslots Requested: 16

3-184 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 2

In this example, a PATH is nailed from timeslot 5 of MMS 1 0 to timeslot 7 of MMS 0 1 at BTS 26:

chg_ts_usage

System response

Enter Action: NAIL

Enter Site Identifier: 26

Enter MMS 1 Identifiers: 1 0

Enter Starting Timeslot for MMS 1: 5

Enter MMS 2 Identifiers: 0 1

Enter Starting Timeslot for MMS 2: 7

Enter Number of Timeslots Requested: 3

Example 3

In this example, the PATH identifier is 1 1 and timeslot 5 of site 1 is nailed to timeslot 6 of site 2:

chg_ts_usage

System response

Enter action: NAIL_PATH

Enter Path Identifiers: 1 1

Enter Start Site: 1

Enter MMS 1 Identifiers: 0 0

Enter Starting Timeslot for MMS 1: 5

Enter End Site: 2

Enter MMS 2 Identifiers: 1 0

Enter Starting Timeslot for MMS 2: 6

Enter Number of Timeslots Requested: 3

References

Related command

disp_mms_ts_usage on page 3-366.

68P02901W23-T 3-185
Jan 2010
chg_x25config Chapter 3: Device/function related commands

chg_x25config

Description

The chg_x25config command changes the X.25 link parameters.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

chg_x25config <link type> <x25_parameter> <value>

Input parameters

link type

Specifies the type of X.25 link:

oml change parameters for all OMLs in the BSS

cbl change parameters for all CBLs in the BSS

NOTE
OML parameters are stored in NVRAM on the GPROCs at the BSC; they are not
stored in the database. Therefore, OML parameters cannot be changed.

3-186 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

x25_parameter

Specifies the type of X.25 parameter being changed for all OMLs or CBLs:

packet_size
window_size

The type of X.25 parameter is shown in the OMC GUI window in BSS View as config_packet_size
and config_window_size respectively.

value

Specifies the new value of the X.25 link:

packet_size 128, 256, 512

window_size 2-7

Examples

Example 1

The following example changes the X.25 settings for all BSS OMLs:

chg_x25 oml window_size 6

Where: is:
oml link type
window_size x25_parameter
6 value

System response:

COMMAND ACCEPTED

Example 2

The following example changes the X.25 settings for all BSS CBLs:

chg_x25 cbl packet_size 256

Where: is:
cbl link type
packet_size x25_parameter
256 value

68P02901W23-T 3-187
Jan 2010
References Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED

References

Related command

disp_x25config on page 3-443.

3-188 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference clear_cal_data

clear_cal_data

Description

The clear_cal_data command clears calibration data previously stored (at the BSC) for a
specified radio unit on a per DRI basis.

When this command is entered, a warning is displayed that the calibration data for the specified
transceiver is cleared.

Security level 3
Supported by OMC-R GUI No
Command type B (operator action required)
Prerequisites This command is not available while in SYSGEN ON mode.
This command is not entered at a BTS.
The DRI device must be locked.
Operator actions Respond to the warning prompt.

Format

Syntax

clear_cal_data <location> dri <dev_id> <dev_id> [<dev_id>]

Input parameters

location

0 or bsc BSC

dri

The DRI is the only device permitted for this command.

dev_id

The first device identifier. The range is 0 - 5.

dev_id

The second device identifier. The range is 0 - 11.

68P02901W23-T 3-189
Jan 2010
Example Chapter 3: Device/function related commands

dev_id

The third device identifier. This value defaults to 0 if no value is entered.

Example

The following example clears the calibration data for DRI 5 3 0 at site 21:

clear_cal_data 21 dri 5 3 0

Where: is:
21 site
dri dri device
5 first dev_id
3 second dev_id
0 third dev_id

System response

Warning: This will clear the calibration data for this transceiver
Are you sure (y=yes,n=no)? y
COMMAND ACCEPTED

References

Related commands

disp_cal_data on page 3-253 store_cal_data on page 3-596

3-190 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference clear_database

clear_database

Description

The clear_database command deletes the contents of the CM database.

CAUTION
This command must be used only by personnel who fully understand the consequences.

The system is placed in the initial SYSGEN mode when this command is entered. Refer to
SYSGEN mode on page 1-40.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites This command can only be entered in the SYSGEN ON
mode.
Operator actions Place the system in the SYSGEN ON mode before entering
this command.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

clear_database

Input parameters

There are no input parameters associated with this command.

68P02901W23-T 3-191
Jan 2010
Example Chapter 3: Device/function related commands

Example

In this example, the CM database is cleared with the system in SYSGEN ON mode:

clear_database

System response

COMMAND ACCEPTED

3-192 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference clear_gclk_avgs

clear_gclk_avgs

Description

The clear_gclk_avgs command clears the stored LTA values and the stored samples for a
specified GCLK or MMS. If this command is entered, the LTA value is set to 80 h and the
frequency register readings are cleared.
If this command is entered at an InCell site, a prompt for a GCLK ID displays.

If this command is entered at a non-InCell site, a prompt for an MMS ID displays.

Clear the LTA values under the following circumstances:

The GCLK is replaced.

The GCLK is recalibrated.

The uplink site does not provide a stable clock source.

Security level 3
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed while in the SYSGEN ON
mode.

Format

Syntax

clear_gclk_avgs <location>

Input parameter

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS

68P02901W23-T 3-193
Jan 2010
Example Chapter 3: Device/function related commands

Example

In this example, the LTA values for GCLK 1 at InCell SITE 0 are cleared:

clear_gclk_avgs 0

Where: is:
0 location

System response

Enter the gclk_id: 1

COMMAND ACCEPTED

References

Related information

The system reads the clock frequency register of each GCLK once every half hour after
synchronization when the GCLK is in phase_locked mode. A rolling average for each GCLK is
calculated from up to 48 clock frequency register readings. This average is the Long Term
Average (LTA).

An alarm is generated if 25% or more of the stored clock frequency readings differ from the
calculated LTA by more than the value that the lta_alarm_range parameter defines.

Related commands

disp_gclk_avgs on page 3-345 disp_gclk_cal on page 3-347

3-194 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference configure_csfp

configure_csfp

Description

The configure_csfp command configures CSFP (Code Storage Facility Processor) devices to
sites in the BSS network. This command selects a BSP, BTP, or pool GPROC device, dependent
on the CSFP algorithm setting for that site, and converts the selected device to a CSFP device.

Security level 4
Supported by OMC-R GUI Yes
Command type B (Operator actions required)
Prerequisites This command can only be executed when the system is
SYSGEN ON mode
Operator actions Put the system into SYSGEN ON mode before executing
this command.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Refer to the OMC-R for help.

Format

Syntax

configure_csfp

Input parameters

There are no input parameters associated with this command.

Example

This example shows the input required to configure the CSFP devices to sites in the BSS network.

configure_csfp

68P02901W23-T 3-195
Jan 2010
References Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED

References

Related information

Depending on the CSFP stealing algorithm (set using the chg_csfp command), the device stolen
to become the CSFP can vary. If the algorithm is set to any (the default value), an equipped
GPROC is chosen first instead of choosing the redundant BSP or BTP device.

Algorithm set

NONE No CSFPs are configured at the site. The location does not matter.
STBY If location is BSC and two BSPs are equipped then one is configured
as CSFP. If location is a remote BTS and two BTPs are equipped then
one is configured as CSFP.
POOL For either BSC or remote BTS locations, an equipped GPROC is
configured as CSFP.
ANY First the POOL algorithm is applied and then the STBY algorithm is
applied. ANY is the default algorithm.

NOTE
If there is only one GPROC in the second cage, it cannot be chosen as a configured
CSFP.NOTE.

Related Commands

chg_csfp on page 3-101 disp_csfp on page 3-284 unconfigure_csfp on page

3-631

3-196 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference connection_code

connection_code

Description

The connection_code command is used for the following:

To change operator-defined code that triggers the resource trace of a call.

To turn the Call Connectivity Trace feature off.

To display the current value of operator-defined code.

Security level 2
Supported by OMC-R GUI No
Command type A (no operator action required)
Prerequisites The GPRS must be unrestricted to assess a PCU site.

Format

Syntax

connection_code [<operator-defined code>]

Input parameter

operator-defined code

Six-digit number; each digit can be from 0 to 9.

Examples

Example 1

The following example changes the value of the operator-defined code to 123456:

connection_code 123456

Where: is:
123456 the operator-defined code.

68P02901W23-T 3-197
Jan 2010
Examples Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED

Example 2

The following example turns off the Call Connectivity Trace feature:

connection_code

System response

COMMAND ACCEPTED

Example 3

The following example displays the current value for the operator-defined code:

connection_code

System response

Connection code is: 123456

NOTE
If there is no connection code, the system response is: No Connection code exists.

3-198 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference copy_cell

copy_cell

Description

The copy_cell command creates a cell by copying the information in an existing cell.

This command cannot copy a cell source or neighbor information. Also, the cell BSIC is not
copied and a new BSIC must be entered for the cell being created (destination cell).

If dynamic allocation is in use at the source cell, the system sets the value of the
dynet_tchs_reserved parameter to the default (0), regardless of the setting in the source
cell. The value of dynet_tchs_reserved does not change at the source cell. The value of the
dynet_tchs_reserved parameter at the destination cell is always defaulted to 0.

This command is rejected if it is entered for an M-Cellcity, Horizonmicro or Horizoncompact site

where a cell exists. Only one cell is permitted at these sites.

An extended source cell is copied as an extended destination cell.

If used on a coincident cell, the copy_cell command sets the coincident cell to an invalid value,
and the coincident_mb to 0 at the new cell.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites None
Operator actions Respond to the warning prompt presented when this
command is entered.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help

Format

Syntax

copy_cell <source_cell_id> <dest_gsm_cell_id> <dest_location>

<dest_bsic>[cell_name]

68P02901W23-T 3-199
Jan 2010
Format Chapter 3: Device/function related commands

Input parameters

source_cell_id

GSM cell ID of the existing cell being copied.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The cell name created using the cell_name command is entered in place of the source_cell_id.
When the cell name is entered, it must be placed inside double quotation marks.

dest_gsm_cell_id

GSM cell ID of the new cell to be created. A cell name is not entered for the destination Cell ID.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

dest_location

Specifies the location of the new cell. Values are:

0 or bsc BSC
1 - 140 BTS

dest_bsic

Specifies the BSIC of the new cell. The range of values for the bsic is 0 - 63.

cell_name

A cell name can be specified for the dest_gsm_cell_id, as if created using the cell_name
command. This cell name must be placed inside double quotation marks. The full format is
given in the cell_name parameter description.

Inclusions

The following parameters are copied when the copy_cell command is executed:

alt_qual_proc en_incom_ho ms_txpwr_max_cch

attach_detach extended_paging_active ms_txpwr_max_def

3-200 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

ba_alloc_proc frequency_type mspwr_alg

bs_ag_blks_res full_pwr_rfloss ncc_of_plmn_allowed
bs_pa_mfrms gprs_par_wait_ind new_calls_hr
bep_period handover_power_level number_of_preferred_cells
bep_period2 handover_recognized_period number_sdcchs_preferred
bsic ho_margin_def penalty_time
bts_p_con_ack hr_fr_hop_count pfc_be_arp
bts_p_con_interval hr_intracell_ho_allowed pow_inc_step_size_dl
bts_power_control_allowed hr_res_ts
ccch_conf imrm_dcs1800_weight pow_red_step_size_dl
cell_bar_access_class imrm_egsm_weight pow_inc_step_size_ul
cell_bar_access_switch imrm_force_recalc pwr_handover_allowed
cell_bar_qualify imrm_pgsm_weight pwrc

cell_reselect_hysteresis imrm_umts_weight qos_mtbr_be_dl

cell_reselect_offset inner_hr_usage_thres qos_mtbr_be_ul
cell_reselect_param_ind intave qos_mtbr_bg_dl
decision_1_dl_rxlev_av_h inter_cell_handover_allowed qos_mtbr_bg_ul
decision_1_dl_rxlev_av_ih interfer_ho_allowed qos_mtbr_i1_dl
decision_1_dl_rxlev_av_p intr_cell_handover_allowed qos_mtbr_i1_ul
decision_1_dl_rxqual_av_h l_rxlev_dl_h qos_mtbr_i2_dl
decision_1_dl_rxqual_av_p l_rxlev_dl_p qos_mtbr_i2_ul
decision_1_n1 l_rxlev_ul_h qos_mtbr_i3_dl
decision_1_n2 l_rxlev_ul_p qos_mtbr_i3_ul
decision_1_n3 l_rxqual_dl_h radio_link_timeout
decision_1_n4 l_rxqual_dl_h_hopping_hr rapid_pwr_down
decision_1_n5 l_rxqual_dl_h_hr reconfig_fr_to_hr
decision_1_n6 l_rxqual_dl_p
decision_1_n7 l_rxqual_dl_p_hopping_hr reestablish_allowed
decision_1_n8 l_rxqual_dl_p_hr report_resource_tch_f_high_
water_mark
decision_1_ncell_rxlev_ l_rxqual_ul_h report_resource_tch_f_low_
av_h_calc water_mark
decision_1_p_bgt_rxlev_av_h l_rxqual_ul_h_hopping_hr rpd_offset
decision_1_p1 l_rxqual_ul_h_hr rpd_period
decision_1_p2 l_rxqual_ul_p rpd_trigger

68P02901W23-T 3-201
Jan 2010
Format Chapter 3: Device/function related commands

decision_1_p3 l_rxqual_ul_p_hopping_hr rxlev_access_min

decision_1_p4 l_rxqual_ul_p_hr rxlev_min_def
decision_1_p5 l_rxqual_ul_p_amr_fr sdcch_ho
decision_1_p6 l_rxqual_dl_p_amr_fr ms_txpwr_max_cch
decision_1_p7 en_incom_ho ms_txpwr_max_def
alt_qual_proc extended_paging_active mspwr_alg
attach_detach frequency_type ncc_of_plmn_allowed
ba_alloc_proc full_pwr_rfloss new_calls_hr
bs_ag_blks_res gprs_par_wait_ind number_of_preferred_cells
bs_pa_mfrms handover_power_level number_sdcchs_preferred
bep_period handover_recognized_period penalty_time
bep_period2 ho_margin_def pfc_be_arp
bsic hr_fr_hop_count pow_inc_step_size_dl
bts_p_con_ack hr_intracell_ho_allowed pow_red_step_size_dl
bts_p_con_interval hr_res_ts pow_inc_step_size_ul
bts_power_control_allowed imrm_dcs1800_weight pwr_handover_allowed
ccch_conf imrm_egsm_weight pwrc

cell_bar_access_class imrm_force_recalc qos_mtbr_be_dl

cell_bar_access_switch imrm_pgsm_weight qos_mtbr_be_ul
cell_bar_qualify imrm_umts_weight qos_mtbr_bg_dl
cell_reselect_hysteresis inner_hr_usage_thres qos_mtbr_bg_ul
cell_reselect_offset intave qos_mtbr_i1_dl
cell_reselect_param_ind inter_cell_handover_allowed qos_mtbr_i1_ul
decision_1_dl_rxlev_av_h interfer_ho_allowed qos_mtbr_i2_dl
decision_1_dl_rxlev_av_ih intr_cell_handover_allowed qos_mtbr_i2_ul
decision_1_dl_rxlev_av_p l_rxlev_dl_h qos_mtbr_i3_dl
decision_1_dl_rxqual_av_h l_rxlev_dl_p qos_mtbr_i3_ul
decision_1_dl_rxqual_av_p l_rxlev_ul_h radio_link_timeout
decision_1_n1 l_rxlev_ul_p rapid_pwr_down
decision_1_n2 l_rxqual_dl_h reconfig_fr_to_hr
decision_1_n3 l_rxqual_dl_h_hopping_hr reestablish_allowed
decision_1_n4 l_rxqual_dl_h_hr report_resource_tch_f_high_
water_mark
decision_1_n5 l_rxqual_dl_p report_resource_tch_f_low_
water_mark

3-202 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

decision_1_n6 l_rxqual_dl_p_hopping_hr rpd_offset

decision_1_n7 l_rxqual_dl_p_hr rpd_period
decision_1_n8 l_rxqual_ul_h rpd_trigger
decision_1_ncell_rxlev_ l_rxqual_ul_h_hopping_hr rxlev_access_min
av_h_calc
decision_1_p_bgt_rxlev_av_h l_rxqual_ul_h_hr rxlev_min_def
decision_1_p1 l_rxqual_ul_p sdcch_ho
decision_1_p2 l_rxqual_ul_p_hopping_hr sdcch_timer_ho
decision_1_p3 l_rxqual_ul_p_hr temporary_offset
decision_1_p4 l_rxqual_ul_p_amr_fr timing_advance_period
decision_1_p5 l_rxqual_dl_p_amr_fr tlli_blk_coding
decision_1_p6 l_rxqual_ul_h_amr_fr tx_integer
decision_1_p7 l_rxqual_dl_h_amr_fr u_rxlev_dl_ih
decision_1_p8 l_rxqual_dl_h_hopping_amr_fr u_rxlev_dl_p
decision_1_tim_adv_av_alg l_rxqual_ul_h_hopping_amr_fr ul_rxlev_ho_allowed
decision_1_ul_rxlev_av_h l_rxqual_dl_p_hopping_amr_fr u_rxlev_ul_ih
decision_1_ul_rxlev_av_ih l_rxqual_ul_p_hopping_amr_fr u_rxlev_ul_p
decision_1_ul_rxlev_av_p link_about_to_fail u_rxqual_dl_p
decision_1_ul_rxqual_av_h link_fail ul_rxqual_ho_allowed
decision_1_ul_rxqual_av_p max_retran u_rxqual_ul_p
dl_rxlev_ho_allowed max_tx_bts u_rxqual_dl_p_hr
dl_rxqual_ho_allowed max_tx_ms u_rxqual_ul_p_hr
dtx_required missing_rpt wait_indication_parameters
dyn_step_adj ms_distance_allowed
dyn_step_adj_fmpr ms_p_con_ack
egprs_init_dl_cs ms_p_con_interval
egprs_init_ul_cs ms_power_control_allowed
emergency_class_switch
ext_ul_no_dat

NOTE
If the Inter-RAT handover option is unrestricted, and UTRAN cells are copied with
copy_cell, the following parameters are defaulted in the new cell: fdd_qmin,
fdd_qoffset, qsearch_c_initial, qsearch_i, and inter_rat_enabled.

68P02901W23-T 3-203
Jan 2010
Examples Chapter 3: Device/function related commands

Exceptions

The following is a list of parameters that are not copied, and instead the parameter default
values are used when the copy_cell command is executed:

bsic fdd_multirat_reporting res_ts_less_one_carrier

bcch_frequency fdd_rep_quant source_cells
freq_share_table_pointer sw_ts_less_one_carrier
blind_search_preference gsm_cell_id serving_band_reporting
cbch_enabled gsm_half_rate_enabled switch_gprs_pdchs
cell_name hopping_support tch_usage_threshold
coincident_index inner_zone_alg thresholds
coincident_mb inter_rat_enable tx_power_cap
dynet_tchs_reserved ms_max_range trx_pwr_carriers.num_carriers
equipment_share_table_pointer multiband_reporting umts_band_preferred
ext_range_cell qsearch_c umts_cpich_ec_no_min
umts_cpich_rscp_min

The neighbor definitions also are not copied. If the GPRS feature is unrestricted, the copy_cell
command copies the GPRS elements at a cell, except for the following:

bvci ra_colour
gprs_enabled

Examples

Example 1

In this example, information from a cell with cell_number=5 4 3 2 1 61986 34944 is copied to
create a cell with cell_number=5 4 3 2 1 61986 34945 at site 0:

copy_cell 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 0 6

Where: is:
5 4 3 2 1 61986 34944 source_cell_id
5 4 3 2 1 61986 34945 dest_gsm_cell_id
0 dest_location
6 dest_bsic

System response

COMMAND ACCEPTED

3-204 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 2

In this example, the source cell is identified using the cell_name london-south.

copy_cell london-south 5 4 3 2 1 61986 34945 0 6

Where: is:
london-south cell_name
5 4 3 2 1 61986 34945 dest_gsm_cell_id
0 dest_location
6 dest_bsic

System response

COMMAND ACCEPTED

Example 3

In this example, information from a PCS1900 cell with cell_number=543 721 61986 34944 is
copied to create a cell with cell_number=543 721 61986 34945 at site 0, with the cell name
of paris:

copy_cell 543 721 61986 34944 543 721 61986 34945 0 6 paris

Where: is:
543 721 61986 34944 source_cell_id
543 721 61986 34945 dest_gsm_cell_id
0 dest_location
6 dest_bsic
paris cell_name

System response

COMMAND ACCEPTED

68P02901W23-T 3-205
Jan 2010
References Chapter 3: Device/function related commands

Example 4

In this example, gsm_half_rate_enabled is set to 1 in the source cell and a new cell is created
using the command copy_cell.

copy_cell 0 0 1 0 1 1 3 0 0 1 0 1 1 44 2 7

Where: is:
0010113 source_cell_id
0 0 1 0 1 1 44 dest_gsm_cell_id
2 dest_location
7 dest_bsic

System response

COMMAND ACCEPTED: WARNING: The GSM half rate per cell enable parameter has been
modified

References

Related information

The GSM cell ID entry format is: a b c d e f g

Where: is:
a the first digit of the MCC (Mobile Country Code).
b the second digit of the MCC.
c the third digit of the MCC.
d the first digit of the MNC (Mobile Network Code).
e the second digit of the MNC.
f the LAC (Local Area Code).
g the CI (Cell Identity).

Related commands

add_cell on page 3-22 del_cell on page 3-212 disp_cell on page 3-261

3-206 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference copy_path

copy_path

Description

The copy_path command equips a new PATH device by copying an existing path and extending
it to a new site. This facility is useful when adding paths to the network or creating a long
branch. The first path to the first BTS can be configured when a path is created using the
equip command. This path can be copied or extended to the next BTS. The process can then
be repeated to construct paths to all BTS sites on the branch.

This command ensures that an HDSL link is only copied between MMSs that support the same
number of timeslots, identical link protocol types and HDSL modems that are in a master/slave
configuration. The single exception to this rule is when the system cannot check master/slave
settings because the HDSL link consists of two external modems.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

copy_path

Input parameters

There are no input parameters since this command is interactive. Table 3-31 lists the prompts
and values that must be entered.

68P02901W23-T 3-207
Jan 2010
Example Chapter 3: Device/function related commands

Table 3-31 copy_path command prompts

Prompt Range Default

Enter the terminating SITE id to be copied: 0 - 140 None
Enter the Unique PATH id to be copied: 0 - 9 None
6 - 9
(see NOTE)

NOTE
If the terminating BTS uses dynamic allocation, the range is 6 - 9. If the terminating
BTS does not use dynamic allocation, the range is 0 - 9.
Enter the new terminating site id: 0 - 140 None
Enter the unique PATH id: 0 - 9 None
Enter the downstream MSI identifier: 0 - 9 None
Enter the downstream MMS identifier: 0 or 1 None
Enter the upstream MSI identifier: 0 - 9 None
Enter the upstream MMS identifier: 0 or 1 None

Example

This example shows a typical dialogue.

copy_path

System response

Enter the terminating SITE id to be copied: 4

Enter the Unique PATH id to be copied: 0
Enter the new terminating SITE id: 5
Enter the new Unique PATH id: 0
Enter the downstream MSI identifier: 3
Enter the downstream MMS identifier: 0
Enter the upstream MSI identifier: 3
Enter the upstream MMS identifier: 1
COMMAND ACCEPTED

3-208 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related information

The following figure illustrates that downstream always refers to the direction from the BSC to
the BTS. The upstream always describes the direction from the BTS to the BSC.

Related commands

add_rtf_path on page 3-50 chg_rtf_freq on page 3-162 del_rtf_path on page 3-224

disp_rtf_path on page 3-422

68P02901W23-T 3-209
Jan 2010
del_act_alarm Chapter 3: Device/function related commands

del_act_alarm

Description

The del_act_alarm command deletes an alarm that an active operator can clear.

NOTE
The disp_act_alarm command displays the alarms that the operator can delete. See
disp_act_alarm on page 3-246.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

del_act_alarm <location> <device_name> <dev_id1> <dev_id2> <dev_id3> <alarm_code>

Input parameters

location

Specifies the alarm location:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

3-210 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

device_name

Device name that uniquely identifies the device.

dev_id1

First device identifier. The range of values is 1 - 128.

dev_id2

Second device identifier. The range of values is 0 - 99.

dev_id3

Third device identifier. The range of values is 0 - 99.

alarm_code

Alarm to be deleted. The range of values is 0 - 254.

Example

This example deletes an active alarm for KSW 1 0 0, alarm code 2, at the BSC.

del_act_alarm 0 ksw 1 0 0 2

Where: is:
0 location
ksw device_name
1 dev_id1
0 dev_id2
0 dev_id3
2 alarm_code

System response

COMMAND ACCEPTED

References

Related commands

disp_act_alarm on page 3-246.

68P02901W23-T 3-211
Jan 2010
del_cell Chapter 3: Device/function related commands

del_cell

Description

The del_cell command deletes a cell from the CM database.

The del_cell command is rejected if the cell specified for deletion is a coincident cell of any
other cell at a site that has the Coincident Multiband Handover option enabled. The command is
also rejected if any Trace Criteria is with scope as the specified cell.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites If a cell is currently in a DRI descriptor, it cannot be
removed. To remove a cell that is included in a DRI
descriptor, the DRI must be unequipped first.
All trace criteria with scope as the specified cell must be
deleted.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

del_cell <cell_id>

Input parameter

cell_id

GSM cell ID of the cell to be deleted.

The format for the GSM cell ID depends on:

The system being used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

3-212 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

The name of the cell created using the cell_name command is entered in place of the cell_id.
When the cell name is entered, it must be placed inside double quotation marks.

Examples

Example 1

In this example, the cell with cell_number 5 4 3 2 1 61986 34944 (using the seven parameter
format) at site number 0 is deleted from the CM database:

del_cell 5 4 3 2 1 61986 34944

Where: is:
5 4 3 2 1 61986 34944 cell_id

System response

COMMAND ACCEPTED

Example 2

In this example, the cell with cell_number 987 654 12345 67809 (using the four parameter
format) at site number 0 is deleted from the CM database:

del_cell 987 654 12345 67809

Where: is:
987 654 12345 67809 cell_id

System response

COMMAND ACCEPTED

Example 3

In this example, the affected cell is identified using the cell_name london-south.

del_cell london-south

Where: is:
london-south cell_name

68P02901W23-T 3-213
Jan 2010
References Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED

Example 4

In this example, an attempt is made to delete cell 5 4 3 2 1 61986 34944 which has trace
criteria with scope as the specified cell.

del_cell 5 4 3 2 1 61986 34944

Where: is:
5 4 3 2 1 61986 34944 cell_id

System response

COMMAND REJECTED: Delete all Trace Criteria with scope as the specified
cell/RTF/site.

References

Related commands

add_cell on page 3-22 copy_cell on page 3-199 disp_cell on page 3-261

disp_gsm_cells on page 3-350

3-214 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference del_conn

del_conn

Description

The del_conn command updates the BSS database to delete a particular connection between an
MMS at the BSC and an MMS at the RXCDR.

If the BSC is operating in static mode and CICs are statically assigned to that MMS pair,
connectivity cannot be removed for an MMS pair. This only applies to remote transcoding
BSC and RXCDR sites.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites All CICs and XBLs must be unequipped before deleting
MMS connectivity information.
This command can only be entered at the BSC or RXCDR
site.

Format

Syntax

del_conn <local_mms_id_1> <local_mms_id_2>

Input parameters

local_mms_id_1

First identifier of the MMS at the local site. The term local site refers to the site where the
command is entered. The range of values vary from 0 - 95 when this command is executed from
a BSC. The range varies from 0 to 123 when executed from an RXCDR.

local_mms_id_2

Second identifier of the MMS at the local site. Values are 0 or 1.

68P02901W23-T 3-215
Jan 2010
Example Chapter 3: Device/function related commands

Example

This example shows connectivity information deleted for MMS 4 0 at the BSC.

del_conn 4 0

Where: is:
4 local_mms_id_1
0 local_mms_id_2

System response

COMMAND ACCEPTED

References

Related commands

add_conn on page 3-33 disp_conn on page 3-282 mod_conn on page 3-492

3-216 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference del_neighbor

del_neighbor

Description

The del_neighbor command deletes neighbor cells, including Blind Search Neighbors, from
a cell neighbor list. If two Cell IDs are entered, the second Cell ID is removed from the first
cell neighbor list.

If all is entered in place of the second cell ID, then every neighbor in the specified cell neighbor
list is deleted. If all is entered in place of the first Cell ID, then the cell is deleted from all
associated neighbor lists.

If the Inter_RAT (Radio Access Technology) Handover feature and/or the Enhanced 2G/3G
Handover feature is unrestricted, this command supports the UTRAN cell identity format.

NOTE
If all is entered for a BTS at which the Coincident MultiBand Handover option is
enabled, and contains any coincident cells, the command is rejected.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites To be on a Neighbor Cell List, a cell must be the destination
of handovers from the Neighbor List owner.
For handovers to UTRAN cells, the Inter-RAT Handover
feature and/or the Enhanced 2G/3G Handover feature must
be unrestricted.
The specified UMTS cell identifier must exist as a neighbor
cell of the GSM source cell.
The GSM source cell must exist.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

68P02901W23-T 3-217
Jan 2010
Format Chapter 3: Device/function related commands

Format

Syntax

del_neighbor <source_cell_id>

[<neighbor_cell_id>] <placement> [<FDD-ARFCN>]

del_neighbor <source_cell_id> all

del_neighbor all <neighbor_cell_id>

Input parameters

source_cell_id

GSM or UTRAN Cell ID of the Neighbor List owner.

GSM cell ID of the Neighbor List owner.

The format for the GSM cell ID depends on:

The system being used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command is entered in place of the cell_id.
When the cell name is entered, it must be placed inside double quotation marks.

NOTE
A cell_name cannot be associated with a UMTS neighbor.

neighbor_cell_id

GSM or UTRAN Cell ID of the cell specified to be removed from the Neighbor List.

GSM cell ID of the cell specified to be removed from the Neighbor List.

This attribute is NOT allowed for Blind Search neighbors.

The format for the GSM cell ID depends on:

The system being used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command is entered in place of the cell_id.
When the cell name is entered, it must be placed inside double quotation marks.

The string test <num> is entered for this field where <num> is a value from 1 to 64. This
permits test neighbors to be removed from the BA_SACCH and/or BA_BCCH lists.

placement

3-218 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Defines the placement type where umts_fdd_blind specifies that the neighbor is a Blind Search
neighbor.

This parameter is not allowed if the Enhanced 2G/3G Handover feature is restricted.

FDD-ARFCN

Specifies the FDD-ARFCN of the neighbor to be deleted.

This parameter is not allowed if the Enhanced 2G/3G Handover feature is restricted.

<source_cell_id>all

This syntax removes all neighbor cells from the source cell neighbor list.

all <neighbor_cell_id>

This syntax removes the neighbor cell from all source cell neighbor lists.

Examples

Example 1

In this example, cell_id 5 4 3 2 1 61986 34945 is removed from the neighbor list of cell_id 5 4
3 2 161986 34944:

del_neighbor 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945

Where: is:
5 4 3 2 1 61986 34944 source_cell_id
5 4 3 2 1 61986 34945 neighbor_cell_id

System response

COMMAND ACCEPTED

Example 2

In this example, all neighbor cells are removed from the neighbor list of cell_id 5 4 3 2 1
61986 34944:

del_neighbor 5 4 3 2 1 61986 34944 all

Where: is:
5 4 3 2 1 61986 34944 source_cell_id
all neighbor_cell_id

68P02901W23-T 3-219
Jan 2010
Examples Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED

Example 3

In this example, cell_id 5 4 3 2 1 61986 34944 is removed from all neighbor lists:

del_neighbor all 5 4 3 2 1 61986 34944

Where: is:
all source_cell_id
5 4 3 2 1 61986 34944 neighbor_cell_id

System response

COMMAND ACCEPTED

Example 4

In this example, cell_id 987 654 12345 34567 (using the four parameter format) is removed
from all neighbor lists:

del_neighbor all 987 654 12345 34567

Where: is:
all source_cell_id
987 654 12345 34567 neighbor_cell_id

System response

COMMAND ACCEPTED

3-220 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 5

In this example, FDD-ARFCN cell ID 10762 is removed from the neighbor list of source cell
ID 0 0 1 0 1 1 4. where 10762 is the last blind search neighbor of this cell and blind search
preference is on.

del_neighbor 0 0 1 0 1 1 4 umts_fdd_blind 10762

Where: is:
0010114 source_cell_id
10762 FDD-ARFCN

System response

COMMAND ACCEPTED
WARNING: The last Blind Search neighbor has been deleted for this cell.

References

Related commands

add_cell on page 3-22 add_neighbor on page 3-35 copy_cell on page 3-199

del_cell on page 3-212 disp_cell on page 3-261 disp_gsm_cells on page 3-350
disp_neighbor on page 3-379

68P02901W23-T 3-221
Jan 2010
del_nsvc Chapter 3: Device/function related commands

del_nsvc

Description

The del_nsvc command enables the operator to remove one or more mappings between a
Network Service-Virtual Connection Identifier (NSVCI), Data Link Connection Identifier (DLCI)
and a GBL at a specific PCU.

{23368} The BSC will support to delete IP based NSVC if gb_mode is set to static IP mode, and
support to delete frame relay NSVC if gb_mode is set to frame relay mode.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The GPRS feature must be unrestricted.

Format

Syntax

del_nsvc <pcu_id> <ns_vci_1> [<ns_vci_2> ... <ns_vci_8>]

Input parameters:

pcu_id

Specifies the specific PCU, as pcu or pcu_0.

ns_vci_1

Specifies the unique identifier of the first NSVCI mapping and identifier of the object. Range =
0 - 65535.

ns_vci_2 ... ns_vci_8

Specifies the unique identifiers of subsequent NSVCI mapping and the objects (up to 8).
Range= 0 - 65535.

3-222 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Example

Example 1

The following example deletes NSVCI 580 at the first equipped PCU.

del_nsvc pcu_0 580

Where: is:
pcu_0 PCU identifier (first equipped)

580 NSVC identifier

System response

COMMAND ACCEPTED

Example 2

{26638}

The following example attempts to delete the last NSVC with non-zero signaling weight, while
the gprs_enabled parameter is set to 1 for any cell and the gb_mode parameter is in static
IP mode.

del_nsvc pcu 7

Where: is:
pcu PCU identifier
7 NSVC identifier

System response:

COMMAND REJECTED: gprs_enabled must be set to zero before removing last NSVC
with non-zero signaling weight.

References

Related commands

add_nsvc on page 3-47 mod_nsvc on page 3-495

68P02901W23-T 3-223
Jan 2010
del_rtf_path Chapter 3: Device/function related commands

del_rtf_path

Description

The del_rtf_path command deletes a redundant PATH device from an equipped RTF function
in the Configuration Management (CM) database.

The system rejects attempts to modify the PATHs used by RTFs at sites that use dynamic
allocation. RTFs automatically use the PATHs defined for these types of sites. RTFs do not use
PATHs equipped by the operator for these types of sites.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

del_rtf_path <location> <1st_RTF_identifier> <2nd_RTF_identifier>

<unique_PATH_identifier>

Input parameters

location

The number of the BTS where the RTF is located. The range of values is 0 - 140.

1st_RTF_identifier

The first RTF identifier from which the path is removed. The range of values is 0 - 5.

2nd_RTF_identifier

The second RTF identifier from which the path is removed. The range of values is 0 - 11.

unique_PATH_identifier

The unique PATH to be removed. The range of values is 0 - 9.

3-224 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Example

This example deletes a redundant RTF PATH from site 36, RTF identifiers 5 20, unique PATH
identifier 8.

del_rtf_path 36 5 20 8

Where: is:
36 location
5 1st_RTF_identifier
20 2nd_RTF_identifier
8 unique_PATH_identifier

System response

This may reduce the number of Traffic Channels available.

Are you sure? (y=yes, n=no)?y
COMMAND ACCEPTED

References

Related information

If a redundant path does not exist, the command is rejected.

When deleting a redundant path, the path is automatically switched over to the remaining paths.

Related commands

add_rtf_path on page 3-50 chg_rtf_freq on page 3-162 disp_rtf_path on page 3-422

copy_path on page 3-207

68P02901W23-T 3-225
Jan 2010
del_smscb_msg Chapter 3: Device/function related commands

del_smscb_msg

Description

The del_smscb_msg command deletes the CBCH background message.

This command is used to delete:

A single message at a single cell.

A single message at all cells in the BSS.

All messages at a single cell.

All messages at all cells in the BSS.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

del_smscb_msg <msg_num|all> <cell_desc|all>

Input parameters

msg_num

A number that uniquely identifies the message to be deleted.

The value all is also a valid input for the msg_num to specify all messages at the specified cells.

3-226 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

cell_desc

This parameter is the GSM cell ID of the cell at which messages are to be deleted, preceded by
cell_number=.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command is entered in place of the
cell_number. When the cell name is entered, it must be placed inside double quotation marks,
and cell_name=. must precede it.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

The value all is also a valid input for the cell_desc, to delete the specified messages at all
cells at the BSS.

Examples

Example 1

This example deletes CBCH background message number 4 for cell_number=5 4 3 2 1 61986
34944.

del_smscb_msg 3 cell_number=5 4 3 2 1 61986 34944

Where: is:
3 msg_num
cell_number=5 4 3 2 1 61986 34944 cell_desc

System response

COMMAND ACCEPTED

68P02901W23-T 3-227
Jan 2010
Examples Chapter 3: Device/function related commands

Example 2

This example deletes all CBCH background messages for all cells.

del_smscb_msg all all

Where: is:
all all background messages
all cell_desc (all cells)

System response

COMMAND ACCEPTED

Example 3

In this example, the affected cell is identified using the cell_name london-south.

del_smscb_msg 3 cell_name=london-south

Where: is:
3 msg_num
cell_name=london-south cell_desc

System response

COMMAND ACCEPTED

Example 4

This example deletes CBCH background message number 4 for cell_number=987 654 13579
24689 (using the four parameter format).

del_smscb_msg 3 cell_number=987 654 13579 24689

Where: is:
3 msg_num
cell_number=987 654 13579 24689 cell_desc

System response

COMMAND ACCEPTED

3-228 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related commands

chg_smscb_msg on page disp_cbch_state on page

3-170 3-257

68P02901W23-T 3-229
Jan 2010
device_audit Chapter 3: Device/function related commands

device_audit

Description

The device_audit command suspends or resumes audits at a specific site. This command is
also used to execute a specific test on a specific device.

The device_audit supports display of swap_type on the TDM device at location 0 (BSC or
RXCDR).

When this command is used to execute an audit at the BSC for an RXCDR that is in the
BUSY-UNLOCKED state, the BSC performs an audit.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator action)
Prerequisites This command is not allowed while in SYSGEN ON mode.
The operator at the OMC-R must rlogin to a site before
an audit can be performed.

Format

Syntax

device_audit <location> <control> <audit type> <device_name> <device_id1>

<device_id2> <device_id3>

device_audit <location> <audit type> <device_name> <device_id1> <device_id2>

<device_id3>

Input parameters

location

Specifies the audit location:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU
pcu_1 Specifies the PCU site 1.
pcu_2 Specifies the PCU site 2.

3-230 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

control

Site audit status:

on Resumes all site audits within a cage at a specific site.

off Suspends all site audits within a cage at a specific site.

audit_type

Type of audit:

Specifies the type of audit:

0 All audits

1 Safe audits

2 Internal loopback audit

3 Self audits

4 Swap_test

NOTE

If all is entered as the control parameter value, multiple devices can be audited.
The format for each of the additional devices is the same as it is for the first
device.
The SWAP_TEST audit only applies to the expanded cage. The SWAP_TEST
audit is done at 2:50 every day.

device_name

Name that uniquely identifies the device.

Not all devices can be audited at all site types. It is only possible to audit the device that are
equipped at the site. Given these conditions, the following devices can be audited with this
command:

BSP GPROC SBUS

BTP KSW TDM
DHP MSI AXCDR
DRI RXCDR

The following devices can be audited at M-Cell sites using this command:

{34371G} BBU BTP DRI MSI

The following devices can be audited at PCU using this command:

MSI DPROC PSP

68P02901W23-T 3-231
Jan 2010
Examples Chapter 3: Device/function related commands

device_id1

First device identifier. Identifier value is dependent upon the device.

device_id2

Second device identifier. Identifier value is dependent upon the device.

device_id3

Third device identifier. Identifier value is dependent upon the device.

Examples

Example 1

The following example executes the safe audits for KSW device ID 0 0 0:

device_audit bsc safe ksw 0 0 0

Where: is:
bsc location
safe audit_type
ksw device_name
0 device_id1
0 device_id2
0 device_id3

System response

Device: KSW Device id: 0 0 0

Year:1994 Month:11 Day:12 Hour:0 Min:26 Sec:29 MSec:665
Audit Type: SAFE Result: PASS

3-232 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 2

The following example suspends audits for a KSW device with ID 1 0 0 at site 4:

device_audit 4 off ksw 1 0 0

Where: is:
4 location
off control
ksw device_name
1 device_id1
0 device_id2
0 device_id3

System response

COMMAND ACCEPTED

If audits for the device is already turned off, the response is:

COMMAND REJECTED: Audits already turned off for this device.

Example 3

The following example resumes audits for a KSW device with ID 1 0 0 at site 4:

device_audit 4 on KSW 1 0 0

Where: is:
4 location
on control
ksw device_name
1 device_id1
0 device_id2
0 device_id3

System response

COMMAND ACCEPTED

68P02901W23-T 3-233
Jan 2010
Examples Chapter 3: Device/function related commands

Example 4

The following example performs a device audit at RXCDR 14 where CIC mismatches are found:

device_audit 0 all RXCDR 14

Where: is:
0 location
all audit_type
RXCDR device_name
14 device_id1

System response

Device: MSI Device id: 2 0 0

Year:1999 Month:1 Day:22 Hour:17 Min:56 Sec:12 MSec:470
Audit Type: SAFE Result: PASS

Example 5

The following example performs a device audit to execute a safe audit on a PSI device.

device_audit 1 safe PSI 1 0

Where: is:
1 location
safe audit_type
PSI device_name
1 device_id1
0 device_id2

System response

Device: PSI Device id: 1 0 0

Year: 1999 Month: 1 Day: 22 Hour: 17 Min: 56 Sec: 12 MSec: 470
Audit Type: SAFE Result: PASS

3-234 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 6

The following example executes audits for the swap_test device ID 1.

device_audit 0 swap_test tdm 1

Where: is:
0 location
swap_test audit_type
tdm device_name
1 device_id1

System Response

WARNING: The Swap_test audit will take about 2 minutes.

Are you sure (y=yes,n=no)? yes
Device: TDM Device id: 1 0 0
Year: 2007 Month: 1 Day: 30 Hour: 15 Min: 0 Sec: 44 MSec: 0
Audit Type: SWAP_TEST Result: PASS

Example 7

The following example attempts to execute the audits for the swap_test device.

device_audit 0 swap_test tdm 0

Where: is:
0 location
swap_test audit_type
tdm device_name
0 device_id1

System response

WARNING: The Swap_test audit will take about 2 minutes.

Are you sure (y=yes,n=no)? yes
Device: TDM Device id: 0 0 0
Year: 2007 Month: 1 Day: 30 Hour: 15 Min: 0 Sec: 15 MSec: 665
Audit Type: SWAP_TEST Result: ERROR

68P02901W23-T 3-235
Jan 2010
Examples Chapter 3: Device/function related commands

Example 8

In this example, device audit cannot be executed on the standby TDM bus.

device_audit 0 all tdm 1

Where: is:
0 location
all audit_type
tdm device_name
1 device_id1

System response

WARNING: Both Safe audit and Swap_test audit will be executed.It will take
about 2 minutes.
Are you sure (y=yes,n=no)? yes
Device: TDM Device id: 1 0 0
Year: 2007 Month: 6 Day: 21 Hour: 16 Min: 54 Sec: 13 MSec: 800
Audit Type: SAFE Result: ERROR
ERROR: Device not in auditable state
Device: TDM Device id: 1 0 0
Year: 2007 Month: 6 Day: 21 Hour: 16 Min: 54 Sec: 13 MSec: 800
Audit Type: SWAP_TEST Result: ERROR
ERROR: Device not in auditable state.

Example 9

{34371G}

This example executes a SAFE audit on a BBU device.

device_audit 23 safe BBU 1 0 0

Where: is:
23 location
safe audit_type
BBU device_name
1 device_id1
0 device_id2
0 device_id3

3-236 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System Response

Device: BBU Device id: 1 0 0

Year: 2008 Month: 12 Day: 22 Hour: 17 Min: 56 Sec: 12 MSec: 470
Audit Type: SAFE Result: PASS

References

Related commands

cage_audit on page 3-58 chg_audit_sched on page 3-76 query_audits on page 3-532

site_audit on page 3-568

68P02901W23-T 3-237
Jan 2010
diagnose_device Chapter 3: Device/function related commands

diagnose_device

Description

The diagnose_device command performs the specified diagnostic on the specified device.

Security level 4
Supported by OMC-R GUI No
Command type B (operator actions required)
Prerequisites This command is supported only in the SYSGEN OFF mode.
For there to be free RTFs for DRI diagnostics, all standby
DRIs must be locked before using this command. Only DRI
devices at Horizonmacro sites are supported.
Operator actions The operator must lock the DRI before using this command.
The RTF cannot be in the active Mobile Allocation List.

Format

Syntax

diagnose_device <location> <device> <id0> <id1> <id2>

Input parameters

location

Specifies the device location:

1 - 140 BTS

device

Specifies the ASCII device name. The only available device is the DRI.

id0

Specifies the first identifier. The range is 0 - 255.

id1

Specifies the second identifier. The range is 0 - 255.

id2

Specifies the third identifier. The range is 0 - 255.

3-238 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Prompted parameter

After specifying the input parameters, the operator is prompted for the type of diagnostic to be
performed. The following types are available:

Device Diagnostic
DRI rf_loopback
vswr_test

Examples

Example 1

In this example, the Receive Preamplifier Input Loopback test fails, but RCU Output Loopback
passes (indicating a possible problem with the receive front end).

diagnose_device 1 DRI 0 0 0

System response

Diagnostic Type: rf_loopback

REPORT FOR DRI 0 0 0 AT SITE 1
-------------------------------------------
RELATED RTF: RTF 0 0 0 (ARFCN 60)
RX preamp input loopback: FAIL
RX preamp Input Loopback RXLEV (Branch 1): -128 dBm
RX preamp Input Loopback RXLEV (Branch 2): -128 dBm
RCU Output Loopback: PASS
RCU Output Loopback RXLEV (Branch 1): 50 dBm
RCU Output Loopback RXLEV (Branch 2): 50 dBm
END OF REPORT

Example 2

In this example, the Receive Preamplifier Input Loopback test passes, indicating that the
diagnostic passes (RCU Output Loopback is not run).

diagnose_device 1 DRI 0 0 0

68P02901W23-T 3-239
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Diagnostic Type: rf_loopback

REPORT FOR DRI 0 0 0 AT SITE 1
-------------------------------------------
RELATED RTF: RTF 0 0 0 (ARFCN 60)
RX Preamp input loopback: PASS
RX preamp Input Loopback RXLEV (Branch 1): -50 dBm
RX preamp Input Loopback RXLEV (Branch 2): -50 dBm
RCU Output Loopback: NOT RUN
RCU Output Loopback RXLEV (Branch 1): N/A
RCU Output Loopback RXLEV (Branch 2): N/A
END OF REPORT

Example 3

In this example, with the 4 branch diversity feature enabled, the Receive Preamplifier Input
Loopback test and the RCU Output Loopback test passes, indicating that the diagnostic passes.

diagnose_device 6 DRI 1 0 0

System response

diagnose_device 6 DRI 0 0 0

Diagnostic Type: rf_loopback

Report for DRI 1 0 0 at SITE 6
-------------------------------------------
Related RTF: RTF 1 0 0 (ARFCN 2)
RX Preamp Input Loopback (Branch 1): PASS
RX Preamp Input Loopback (Branch 2): PASS
RX Preamp Input Loopback (Branch 3): PASS
RX Preamp Input Loopback (Branch 4): PASS
RX Preamp Input Loopback RXLEV (Branch 1): -74 dBm
RX Preamp Input Loopback RXLEV (Branch 2): -74 dBm
RX Preamp Input Loopback RXLEV (Branch 3): -74 dBm

3-240 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

RX Preamp Input Loopback RXLEV (Branch 4): -74 dBm

RCU Output Loopback (Branch 1): PASS
RCU Output Loopback (Branch 2): PASS
RCU Output Loopback (Branch 3): PASS
RCU Output Loopback (Branch 4): PASS
RCU Output Loopback RXLEV (Branch 1): -75 dBm
RCU Output Loopback RXLEV (Branch 2): -75 dBm
RCU Output Loopback RXLEV (Branch 3): -75 dBm
RCU Output Loopback RXLEV (Branch 4): -75 dBm
End of Report

68P02901W23-T 3-241
Jan 2010
disp_a5_alg_pr Chapter 3: Device/function related commands

disp_a5_alg_pr

Description

The disp_a5_alg_pr command displays the current list of prioritized encryption algorithms.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_a5_alg_pr

Input parameters

There are no input parameters associated with this command.

Examples

Example 1

This example shows the order in which two ciphering algorithms were used.

disp_a5_alg_pr

System response

Ciphering Algorithms are prioritized as follows: 2 1 0

Example 2

This example shows that no ciphering algorithms were used.

disp_a5_alg_pr

3-242 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

Ciphering Algorithms are prioritized as follows: 0

References

Related commands

chg_a5_alg_pr on page 3-73 page on page 3-530

68P02901W23-T 3-243
Jan 2010
disp_acs Chapter 3: Device/function related commands

disp_acs

Description

The disp_acs command displays the Active Codec Set and associated parameters.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The AMR feature must be unrestricted.
The site must be an AMR-capable BTS.

Format

disp_acs <cell_id>

Input parameters

cell_id

GSM cell ID or cell name of the cell to be changed.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

Only PCS1900 systems can use a three-digit MNC.

The name of the cell created using the cell_name command is entered in place of the Cell ID.
When the cell name is entered, it must be placed inside double quotation marks.

The Cell ID or the cell_name must be entered directly without any preceding qualifier.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

Example

This example displays the codec modes for a given cell.

3-244 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

disp_acs 4 9 6 0 1 1 1

Where: is:
4960111 cell_id

System response

AMR Full Rate active codec set: 0 1 3 6

AMR Full Rate initial codec mode: 1

AMR Full Rate uplink adaptation thresholds: 26 20 14

AMR Full Rate uplink adaptation hysteresis: 1 1 1

AMR Full Rate downlink adaptation thresholds: 30 24 19

AMR Full Rate downlink adaptation hysteresis: 1 1 1

AMR Full Rate uplink adaptation thresholds for frequency hopping: 26 20 14

AMR Full Rate uplink adaptation hysteresis for frequency hopping: 1 1 1

AMR Full Rate downlink adaptation thresholds for frequency hopping: 26 21 14

AMR Full Rate downlink adaptation hysteresis for frequency hopping: 1 1 1

AMR Half Rate active codec set: 3 5 6

AMR Half Rate initial codec mode: 5

AMR Half Rate uplink adaptation thresholds: 28 22

AMR Half Rate uplink adaptation hysteresis: 1 1

AMR Half Rate downlink adaptation thresholds: 30 24

AMR Half Rate downlink adaptation hysteresis: 1 1

AMR Half Rate uplink adaptation thresholds for frequency hopping: 28 22

AMR Half Rate uplink adaptation hysteresis for frequency hopping: 1 1

A MR Half Rate downlink adaptation thresholds for frequency hopping: 30 23

AMR Half Rate downlink adaptation hysteresis for frequency hopping: 1 1

References

Related command

chg_acs_params on page 3-65

68P02901W23-T 3-245
Jan 2010
disp_act_alarm Chapter 3: Device/function related commands

disp_act_alarm

Description

The disp_act_alarm command displays the active Operator Initiated Clear (OIC) alarms and
the active Fault Management Initiated Clear (FMIC) alarms only. Those alarms that have been
designated as Intermittent do not appear in the active alarm list.

Each device has an active alarm list limit of 200. If there are more than 200 active alarms on
the device, only the first 200 are displayed and monitored. The number of alarms displayed
after entering disp_act_alarm <location> does not get affected. The output of this command
displays up to 200 alarms for each device in the site.

Security level 1

Supported by OMC-R GUI No

Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.

Format

Syntax

disp_act_alarm <location> [<device_name>

<dev_id1><dev_id2> <dev_id3>]

disp_act_alarm <location>

Input parameters

location

Specifies the alarm location:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU
all Specifies all sites.

3-246 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

device_name

Device name that uniquely identifies the device.

dev_id1

First device identifier. The range of values is 0 to 99.

dev_id2

Second device identifier. The range of values is 0 to 99.

dev_id3

Third device identifier. The range of values is 0 to 99.

Examples

Example 1

This example displays all active Operator Initiated Clear, and Fault Management alarms. The
command does not show all active alarms, since any uncleared intermittent alarm is considered
an active alarm, but it cannot appear on any list using the disp_act_alarm command:

disp_act_al 0

Where: is:
0 location

System response

ACTIVE ALARM INFORMATION FOR LOCATION 0:

Device Alarm Clear Tag ADI (hex) Date/Time Description
(Subtype) Code Type (hex)
MMS 1 1 0 16 FMIC 00000001 12-02-2009 Synchronization
12:15:23 Loss OOS Timer
Expired
Estimated
restoral-60.0 secs
MTL 0 0 0 0 FMIC 00000001 020A010000FF 12-02-2009 Signalling Link
12:13:36 Failure
IAS 0 0 0 59 FMIC Untagged 12-02-2009 Battery Backup
12:14:47 Output Failure
SITE 0 0 0 0 FMIC Untagged 0102030405 12-02-2009 Last RSL Link
14:49:22 Failure
END OF REPORT

68P02901W23-T 3-247
Jan 2010
References Chapter 3: Device/function related commands

Example 2

This example displays the output when there are no active alarms at site 2.

disp_act_alarm 2

Where: is:
2 location

System response

There are no active alarms at site 2.

References

Related information

The following responses are received when the disp_act_alarm command is entered:

There are no active alarms at site <location>.

There are no active alarms on that device.
Unknown alarm device
Unknown alarm code
Error: Could not retrieve alarm description
UNKNOWN
INVALID CELL

If the GPRS option is unrestricted the response is:

There are no active alarms at the PCU.

3-248 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_bss

disp_bss

Description

The disp_bss command displays specific status information for all sites in a BSS site. The BSS
device identifier where the command is entered is included in the output.

The status information shows the following:

Sites that are equipped and their status.

Number of sectors, or 1 if the site is OMNI.

The GSM cell ID that is equipped for each site.

Broadcast Control Channel (BCCH) frequency for each of the cells.

The functional Unit Status shows the status of the BSC sites or of the associated cells. The
possible values are:
Critical - indicates a loss of service.

Major - indicates a loss of capacity.

Minor - indicates a loss of redundancy.

Clear - indicates normal operations.

Read the Functional Unit Status across the display. In the example, Site 0 is in Critical status.
Cell 4, which is associated with Site 0 is in Clear status, and Cell 5 is in Critical status.

If the GPRS feature is unrestricted, a line containing GPRS information appears in the output.
This includes the (pcu or pcu_0) PCU, if it is equipped, and values of the RAC and BVCI
associated with each cell.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.

Format

Syntax

disp_bss

68P02901W23-T 3-249
Jan 2010
Example Chapter 3: Device/function related commands

Input parameters

There are no input parameters associated with this command.

Example

This example shows the format of a typical output of the disp_bss command.

disp_bss

System response

OPER STATES: D:Disabled E:Enabled B:Busy

ADMIN STATES: L:Locked U:Unlocked E:Equipped NE:Not Equipped S:Shutdown

Status for BSS 1:
SITE FU STATUS GSM CELL id FREQ BCCH
SITE STATE LOSS OF MCC MNC LAC CI LCI RAC TYPE FREQ
---- ----- ------------- ----------------------------- --- ---- ------- ------
0 B-U Service
PCU_0 B-U Capacity
1 D-U UNAVAILABLE
UNAVAILABLE 001 01 1 (0001h) 1 (0001h) 0 N/A PGSM 26
UNAVAILABLE 001 01 1 (0001h) 6 (0006h) 1 4 PGSM 75
2 B-U Capacity
Capacity 001 01 1 (0001h) 3 (0001h) 2 4 PGSM 30
CLEAR 001 01 1 (0001h) 8 (0006h) 5 4 PGSM 31
3 D-U UNAVAILABLE
UNAVAILABLE 001 01 1 (0001h) 33 (0001h) 3 4 PGSM 10
4 D-U UNAVAILABLE
UNAVAILABLE 001 01 1 (0001h) 18 (0012h) 4 N/A DCS1800 570

References

Related command

assess on page 3-54.

3-250 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_bssgp_f_bmap

disp_bssgp_f_bmap

Description

The disp_bssgp_f_bmap command prints out the database values and SGSN negotiated values
of BSSGP features. It prints out values of bssgp_cbl_bit. If the QoS is unrestricted, the
command also prints out values of bssgp_pfc_bit.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The GPRS feature must be unrestricted.
This command is only available at the BSC, when sysgen
mode is off.

Format

Syntax

disp_bssgp_f_bmap <all> <PCU_id>

Input parameters

<all>

Displays cell mapping at all equipped PCUs.

<PCU_id>

Specifies the specific PCU, as pcu, pcu_0

Example

disp_bssgp_f_bmap PCU_1

Where: is:
PCU_1 PCU ID

68P02901W23-T 3-251
Jan 2010
Example Chapter 3: Device/function related commands

System response

PCU Site 1:
Feature-bit DB value Negotiated Value
CBL 0 (bssgp_cbl_bit) 0 (CBL feature at PCU disabled)
PFC 0 (bssgp_pfc_bit) 0 (QoS feature at PCU disabled)
END OF REPORT

3-252 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_cal_data

disp_cal_data

Description

The disp_cal_data command displays the transceiver calibration data stored on the transceiver
or in the BSC database on a per DRI basis.

If the BSC and BTS are set for PGSM operation, 16 values are displayed.

If the system is set so that the frequency_type parameter is EGSM, then all 22 values are
displayed. The first six are for EGSM and the next 16 are for PGSM.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.
This command is not available at an RXCDR.

Format

Syntax

disp_cal_data <location> dri <dev_id1> <dev_id2> [<dev_id3>]

Input parameters

location

0 or bsc BSC
1 - 140 BTS

dri

The DRI is the only device permitted for this command.

dev_id1

The first device identifier.

dev_id2

The second device identifier.

68P02901W23-T 3-253
Jan 2010
Example 1 Chapter 3: Device/function related commands

dev_id3

The third device identifier. This value defaults to 0 if no value is entered.

Example 1

The following example displays the calibration data for transceiver 5 3 0 at site 21:

disp_cal_data 21 dri 5 3 0

Where: is:
21 site
dri dri device
5 first dev_id
3 second dev_id
0 third dev_id

System response

DRI ID 5 3 0
Data read from transceiver
Store Calibration Data: enabled
Calibration data (All values in Hex):
Transmit Power Offsets = 0
Receiver System Data:

Antenna Number 1 2 3 4 5 6
--------------------------------------------------
f00, 1100, 114d, 1100, 1066, 1066,
10cd, 1100, 1033, 1100, 104d, 104d,
1100, 1100, 1033, 1100, 1033, 1033,
10e6, 1100, 1033, 1100, 101a, 101a,
10cd, 10cd, 1000, 10cd, 1000, 1000,
10b3, 10b3, 1000, 10b3, fcd, fcd,
10cd, 10cd, f66, 10cd, fe6, fe6,
1033, 10cd, f9a, 10cd, fcd, fcd,

3-254 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example 1

1066, 10cd, fcd, 10cd, fcd, fcd,

1066, 10cd, fcd, 10cd, f9a, f9a,
1033, 10b3, f9a, 10b3, f66, f66,
1066, 10b3, fcd, 10b3, f9a, f9a,
1066, 109a, fb3, 109a, f66, f66,
c9a, 1066, db3, 1066, f80, f80,
f9a, 1066, ecd, 1066, f33, f33,
f9a, 1000, ecd, 1000, eb3, eb3,

NOTE
The second line of the system response indicates whether the data is read from
the transceiver or the database. In example 1, the information is read from the
transceiver.

Example 2

The following example displays the calibration data for a DRI that has 4 Branch Receive
Diversity enabled.

disp_cal_data 40 dri 0 0 0

Where: is:
40 site
dri dri device
0 first dev_id
0 second dev_id
0 third dev_id

68P02901W23-T 3-255
Jan 2010
References Chapter 3: Device/function related commands

System response

DRI ID: 0 0 0
Data read from transceiver
Store Calibration Data:disabled
Calibration Data (All values in Hex):
Transmit Power Offsets = 12
Receiver System Data:
AntennaNumber 1 2 3 4 5 6 7 8 9 10 11 12
b89, e80, e80, c4e, e80, e80, b89, e80, e80, c4e, e80, e80,
b7f, e80, e80, ca2, e80, e80, b7f, e80, e80, ca2, e80, e80,
b8d, e80, e80, c74, e80, e80, b8d, e80, e80, c74, e80, e80,
b8d, e80, e80, c9d, e80, e80, b8d, e80, e80, c9d, e80, e80,
b61, e80, e80, c65, e80, e80, b61, e80, e80, c65, e80, e80,
b19, e80, e80, c0c, e80, e80, b19, e80, e80, c0c, e80, e80,
aff, e80, e80, bd3, e80, e80, aff, e80, e80, bd3, e80, e80,
b1d, e80, e80, b54, e80, e80, b1d, e80, e80, b54, e80, e80,
b4b, e80, e80, b9f, e80, e80, b4b, e80, e80, b9f, e80, e80,
b5b, e80, e80, b85, e80, e80, b5b, e80, e80, b85, e80, e80,
b4f, e80, e80, b53, e80, e80, b4f, e80, e80, b53, e80, e80,
b4a, e80, e80, b71, e80, e80, b4a, e80, e80, b71, e80, e80,
b2d, e80, e80, b59, e80, e80, b2d, e80, e80, b59, e80, e80,
b1e, e80, e80, b29, e80, e80, b1e, e80, e80, b29, e80, e80,
b08, e80, e80, aab, e80, e80, b08, e80, e80, aab, e80, e80,
a8f, e80, e80, a9f, e80, e80, a8f, e80, e80, a9f, e80, e80,

References

Related commands

clear_cal_data on page 3-189 store_cal_data on page 3-596

3-256 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_cbch_state

disp_cbch_state

Description

The disp_cbch_state command displays the value of the cbch_enabled field for a specific cell.
In addition, the specified background message in a cell is presented. If the CBCH is hopping,
the frequency hopping index (fhi) for the CBCH timeslot is also displayed.

If the all option is selected for the message number parameter, all background messages
associated with the indicated cell display.

Security level 1
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites To successfully execute this command, purchase, install,
and activate the background message feature.
Operator actions The Background Message feature must be unrestricted.

Format

Syntax

disp_cbch_state <msg_num> <cell_desc>

disp_cbch_state all <cell_desc>

Input parameters

msg_num

Uniquely identifies the number of the message for a given cell by sequence received (up to
4). The range of values is 0 to 3.

cell_desc

The GSM cell ID of the cell preceded by cell_number=.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

68P02901W23-T 3-257
Jan 2010
Examples Chapter 3: Device/function related commands

The name of the cell created using the cell_name command is entered in place of the
cell_number. When the cell name is entered, place it inside double quotation marks and
preceded by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

Examples

Example 1

This example displays the output where the CBCH is not enabled and no background message is
defined for the specified msg_num. The cell_number parameter uses the seven parameter
format.

disp_cbch_state 3 cell_number=5 4 3 2 1 61986 3494

Where: is:
3 msg_num
5 4 3 2 1 61986 3494 cell_number

System response

Message Number 3 is not defined for the CBCH.

The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled.

Example 2

This example displays the output where the CBCH is not enabled and no background message
is defined for the specified msg_num. The cell_number parameter uses the four parameter
format.

disp_cbch_state 3 cell_number=543 21 61986 3494

Where: is:
3 msg_num
543 21 61986 3494 cell_number

System response

Message Number 3 is not defined for the CBCH.

The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled.

3-258 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 3

In this example, the affected cell is identified using the cell_name london-south.

disp_cbch_state 3 cell_name=london-south

Where: is:
3 msg_num
london-south cell_name

System response

Message Number 3 is not defined for the CBCH.

The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled.

Example 4

This is an example of the command succeeding if the CBCH is active and hopping with a
background message defined:

disp_cbch_state 2 cell_number=5 4 3 2 1 61986 3494

Where: is:
2 msg_num
5 4 3 2 1 61986 3494 cell_number

System response

Message Number 2 for the CBCH is:

This is the background message. Non alphabetic characters are displayed in

their escape format

The Message Identifier is 1009

The Geographical Scope is 1 (Normal - PLMN Wide).

The Message Code is 0.

The update number is 0.

The Language Identifier is 3 (French).

The CBCH for cell 5 4 3 2 1 61986 3494 is active.

The channel description is:

Channel Type: SDCCH/4 Subchannel number 2

Timeslot Number = 0

ARFCN = 107 (BCCH Carrier)

68P02901W23-T 3-259
Jan 2010
References Chapter 3: Device/function related commands

References

Related commands

chg_smscb_msg on page del_smscb_msg on page 3-226

3-170

3-260 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_cell

disp_cell

Description

The disp_cell command reads back and displays all programmable database parameters
for a specified cell.

If the disp_cell command is used with the cell description and the optional full parameter,
the system displays all cell-related elements.

If the disp_cell command is used with the cell_description only, the system displays the
elements used in theadd_cell command.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_cell <cell_id> [full]

Input parameters

cell_desc

GSM cell number of the cell to be displayed.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

cell_id is an invalid parameter. The operator cannot input the cell_number or cell_name
preceded by the GSM cell ID or GSM cell name. BSS system responds input error.

full

This optional parameter displays all elements related to the cell.

The system displays the elements with non-indexed parameters first, in alphabetical order,
followed by the indexed parameters also in alphabetical order.

68P02901W23-T 3-261
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

This example displays the programmable database parameters for a GSM cell with a Cell ID
of 5 4 3 2 1 61986 34944.

disp_cell 5 4 3 2 1 61986 34944

Where: is:
5 4 3 2 1 61986 34944 cell_id

System response

The system displays the cell information specified in the add_cell command at creation of
cell 5 4 3 2 1 61986 34944.

Example 2

In this example, the cell is identified using the cell_name london-south:

disp_cell london-south

Where: is:
london-south cell_id

System response

The system displays the cell information specified in the add_cell command at creation of
cell london-south.

Example 3

In this example, the cell is identified in the four parameter format, using the cell_number
543 721 62259 08736:

disp_cell 543 721 62259 08736

Where: is:
543 721 62259 08736 cell_id

System response

The system displays the cell information specified in the add_cell command at creation of
cell 543 721 62259 08736.

3-262 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 4

In this example, all cell-related elements for cell 0 0 1 0 1 1 2 are displayed by using the
parameter full.

disp_cell 0 0 1 0 1 1 2 full

Where: is:
0010112 cell_id
full full option (display all cell-related elements).

System response

The system displays a complete list of all elements related to cell 0 0 1 0 1 1 2.

Non-indexed parameters are displayed first, in alphabetical order, followed by the indexed
parameters also in alphabetical order.

Example 5

This example displays the cell information about cell 0 0 1 0 1 1 4.

disp_cell 0 0 1 0 1 1 4 FULL

Where: is:
0010114 cell_id
full full option (display all cell-related elements).

System response

The system displays a complete list of all elements related to cell 0 0 1 0 1 1 4.

References

Related commands

add_cell on page 3-22 copy_cell on page 3-199 del_cell on page 3-212

disp_gsm_cells on page 3-350

68P02901W23-T 3-263
Jan 2010
disp_cell_map Chapter 3: Device/function related commands

disp_cell_map

Description

Because of the dynamic cell migration in case of failure and recovery, a cell can be mapped
to any equipped PCU site. The disp_cell_map command displays the current cell mapping
information to a particular PCU. The displayed information includes EGPRS availability.

NOTE
The disp_cell_status command shows the status details of the PCU that is currently
serving a cell.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.

Format

Syntax

disp_cell_map all|location|cell_id

Input parameters

all Displays cell mapping at all equipped PCUs.

location pcu, pcu_0 to pcu_2.
cell_id Identifier of cell for which mapping to a PCU is required.

3-264 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

Display cell mapping at PCUs 1 and 2:

disp_cell_map pcu_1 pcu_2

Where: is:
pcu_1 location (site 1)
pcu_2 location (site 2)

System response

PCU Site 1:

CELL ID GPRS STATUS

-------------------------- --------------------

001 01 1 (0001h) 4 (0004h) Barred

001 01 1 (0001h) 5 (0005h) Unbarred

PCU Site 2:

CELL ID GPRS STATUS

-------------------------- --------------------

001 01 1 (0001h) 7 (0007h) Barred

001 01 1 (0001h) 8 (0008h) Unbarred

END OF REPORT

Example 2

Display current PCU mapping of cell 0 0 1 0 1 1 4:

disp_cell_map 0 0 1 0 1 1 4

Where: is:
0010114 cell_desc

System response

Current PCU site: PCU_1

68P02901W23-T 3-265
Jan 2010
Examples Chapter 3: Device/function related commands

Example 3

Display cell mapping at all PCUs:

disp_cell_map all

Where: is:
all all option (display cell mapping at all equipped PCUs).

System response

PCU Site 0:

CELL ID GPRS STATUS

-------------------------- --------------------

001 01 1 (0001h) 4 (0004h) Barred

001 01 1 (0001h) 5 (0005h) Unbarred

PCU Site 1:

CELL ID GPRS STATUS

-------------------------- --------------------

001 01 1 (0001h) 7 (0007h) Barred

001 01 1 (0001h) 8 (0008h) Unbarred

PCU Site 2:

CELL ID GPRS STATUS

-------------------------- --------------------

001 01 1 (0001h) 1 (0001h) Barred

001 01 1 (0001h) 2 (0002h) Unbarred

END OF REPORT

3-266 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_cell_status

disp_cell_status

Description

The disp_cell_status command displays information and channel counters of a single GSM
cell or all GSM cells at a specific site.

Because of the dynamic cell migration in case of failure and recovery, a cell can be mapped to
any equipped PCU site. The disp_cell_status command includes the information on the
cell active PCU.

When the status of a single cell is requested, the cell_name is included in the command output.

When the status of all the cells at a location with more than three cells is requested, the
information on the first two cells displays, followed with a prompt to continue. The cell_name is
not included when all the cells at a site are displayed.

If the BTF is not in service for any reason, the system displays an error message.

If both the GSM and AMR Half Rate modes are disabled either at the BSS or Cell level for a
given cell, the BSS when generating the disp_cell_status command, regards:
Free generic traffic timeslots in that cell as free full-rate traffic channels.

Unavailable generic traffic timeslots in that cell as unavailable full-rate traffic channels.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.

Format

Syntax

disp_cell_status <cell_desc>

disp_cell_status <location> <high>

68P02901W23-T 3-267
Jan 2010
Format Chapter 3: Device/function related commands

Input parameters

cell_desc

The GSM cell ID of the cell to be displayed, preceded by cell_number=.

The format for the GSM cell ID depends on:

The system being used (PGSM, EGSM, DCS1800, PCS1900, or GSM850)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command is entered in place of the
cell_number. When the cell name is entered, place it inside double quotation marks and
precede by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

location

Specifies the element location:

0 or bsc BSC
1 - 140 BTS

high

Indicate that this command is executed in high priority mode which implies that
disp_cell_status is handled by BTS and PCU with high priority.

Output fields

RAC

This field shows the Routing Area Code (part of the cell identifier for GPRS cells).

Status

Barred - A MS cannot access the cell.

Unbarred - A MS can access the cell.

GPRS Status

This field shows the status of a GPRS cell (barred/unbarred) and (when unbarred) whether
EGPRS is available.

GPRS Congestion Status

3-268 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

This field shows the cell GPRS congestion status (TRUE / FALSE / NA) when the GPRS/EDGE
feature is unrestricted.
TRUE - Indicates that the cell GPRS cell utilization has reached the higher threshold
without dropping below the lower threshold. The additional switchable PDTCH is allocated
during this status.

FALSE - Indicates that the cell GPRS cell utilization does not reach the higher threshold.
No additional switchable PDTCH is allocated during this status.

NA - Indicates that the status is not applicable.

PDCH Status

This field shows the GPRS Packet Data traffic channel status.

Reset In Progress

Yes - A reset is in progress. The cell is barred while a reset is in progress.

No - A reset is not in progress.

GPRS Reset in Prog

This field shows whether a PCU is currently undergoing a Reset.

SPI in Progress

Yes - An SPI (Signaling Point Inaccessibility) is in progress. The cell is barred while an
SPI is in progress.

No - An SPI is not in progress.

BSS BSSAP Prhb

Yes - The BSS BSSAP (Base Station System Application Part) Prohibited flag is set to true.
The cell is barred while the BSS BSSAP Prohibited flag is true.

No - The BSS BSSAP Prohibited flag is not set to true.

N/A - Not applicable; the value of this element is not relevant to the status of the cell.

MSC BSSAP Prhb

Yes - The MSC BSSAP Prohibited flag is set to true. The cell is barred while the MSC
BSSAP Prohibited flag is true.

No - The MSC BSSAP Prohibited flag is not set to true.

N/A - Not applicable; the value of this element is not relevant to the status of the cell.

68P02901W23-T 3-269
Jan 2010
Format Chapter 3: Device/function related commands

SPI/MSC SCCP Prhb

Yes - The SPI/MSC BSSAP Prohibited flag is set to true. The cell is barred while the
SPI/MSC BSSAP Prohibited flag is true.

No - The SPI/MSC BSSAP Prohibited flag is not set to true.

N/A - Not applicable; the value of this element is not relevant to the status of the cell.

AccCLASS Bar

This field specifies the access classes of MSs that are barred from the cell. The access class
is presented as a decimal value, separated by commas. If the cell is barred or OOS, this field
contains N/A. If the cell is unbarred, this field contains None when all access classes have been
unbarred.

GPRS AccClass Bar

This field shows any access class barring of GPRS cells.

EGPRS Chan Req

This field indicates if 11-bit EGPRS one-phase access is supported in the cell. EPCR is only
available in the cell if the BCCH RTF is mapped to a CTU II radio.

Full Power Mode

This field indicates if the cell is in the full power mode.

Ext Range Mode

This field shows whether the Extended Range Feature is enabled (on) or disabled (off).

SDCCH: FREE; INUSE; UNAVL

These fields specify the number of Standalone Dedicated Control Channels (SDCCH) in the cell,
that are currently free, in use or unavailable.

Norm Outer TCH/F: FREE; INUSE; UNAVL

These fields specify the number of Full Rate Traffic Channels (TCH/F) in the outer zone
concentric cell that are currently free, in use or unavailable.

NOTE
The UNAVL field includes timeslots that are locked or out of service due to a fault
condition. Any timeslot which is unavailable due to being locked or out of service
is counted as an unavailable TCH (not SDCCH). This field does not include entire
carriers which are out of service.

Norm Outer TCH/F: FREE; INUSE; UNAVL

3-270 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

These fields specify the number of Full Rate Traffic Channels (TCH/H) in the outer zone
concentric cell that are currently free, in use or unavailable.

Norm Inner TCH/F: FREE; INUSE; UNAVL

These fields specify the number of Full Rate Traffic Channels (TCH/F) in the inner zone
concentric cell that are currently free, in use or unavailable.

Ext Outer TCH/F: FREE; INUSE; UNAVL

These fields specify the number of Full Rate Traffic Channels (TCH/F) in the extended outer
concentric cell that are currently free, in use or unavailable.

Norm Inner TCH/H: FREE; INUSE; UNAVL

These fields specify the number of Half Rate Traffic Channels (TCH/H) in the inner zone
concentric cell that are currently free, in use or unavailable.

Norm Outer TCH/G: FREE; INUSE; UNAVL

These fields specify the number of Generic Traffic Channels (TCH/G) in the outer zone
concentric cell that are currently free, in use or unavailable.

Norm Inner TCH/G: FREE; INUSE; UNAVL

These fields specify the number of Generic Traffic Channels (TCH/G) in the inner zone
concentric cell that are currently free, in use or unavailable.

PD CHANNEL

This field shows the GPRS Packet Data traffic channels currently free, in use or unavailable.

EGPRS PD CHANNEL

This field shows the EGPRS Packet Data traffic channels currently free, in use or unavailable.

RES PDCH Requested

This field shows the RES PDCH requested.

SW PDCH Requested

This field shows the SW PDCH requested.

68P02901W23-T 3-271
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

This example displays the status of Cell ID 5 4 3 2 1 61986 34944 (in decimal and in seven
parameter format).

disp_cell_status 5 4 3 2 1 61986 34944

Where: is:
5 4 3 2 1 61986 34944 cell_number

System response

GSM CELL ID MCC 543 MNC 21

LAC CI

(dec) 61986 34944

(hex) f222h 8880h

(name) london-south

--------------------------------------

Frequency Type PGSM

BCCH Frequency 100

--------------------------------------

Status OOS

Reset in Prog No

SPI in Prog Yes

BSS BSSAP Prhb Yes

MSC BSSAP Prhb Yes

SPI/MSC SCCP Prhb Yes

AccClass Bar NA

Full Power Mode OFF

Extend Range Mode OFF

3-272 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

FREE INUSE UNAVL

----- ----- -----

SDCCH 0 0 0

Norm Outer TCH/F 0 0 0

Norm Inner TCH/F 0 0 0

Ext Outer TCH/F 0 0 0

End of Report.

Example 2

This example identifies the cell using the cell_name london-south.

disp_cell_status cell_name=london-south

Where: is:
london-south cell_name

System response

GSM CELL ID MCC 543 MNC 21

LAC CI

(dec) 61986 34944

(hex) f222h 8880h

(name) london-south

------------------------------------

Status Barred

Reset In Prog No

SPI in Prog Yes

BSS BSSAP Prhb Yes

MSC BSSAP Prhb No

SPI/MSC SCCP Prhb No

AccCLASS Bar NA

Ext Range Mode OFF

68P02901W23-T 3-273
Jan 2010
Examples Chapter 3: Device/function related commands

FREE INUSE UNAVL

----- ----- -----

SDCCH 0 0 0

Norm Outer TCH/F 0 0 0

Norm Inner TCH/F 0 0 0

Ext Outer TCH/F 0 0 0

End of Report

Example 3

This example shows the display for a cell where the Concentric Cells feature is enabled.

disp_cell_status 0

Where: is:
0 cell_number

System response

Start of report for LOCATION 39:

GSM CELL ID MCC 001 MNC 01

LAC CI

(dec) 1 39001

(hex) 0001h 9859h

--------------------------------------

Frequency Type PGSM

BCCH Frequency 62

--------------------------------------

Status Unbarred

Reset in Prog No

SPI in Prog No

BSS BSSAP Prhb NA

MSC BSSAP Prhb NA

SPI/MSC SCCP Prhb NA

AccClass Bar None

3-274 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

FREE INUSE UNAVL

----- ----- -----

SDCCH 0 0 0

Norm Outer TCH/F 0 0 0

Norm Inner TCH/F 0 0 0

Ext Outer TCH/F 0 0 0

End of Report.

Example 4

This example displays the status of a BTS site.

disp_cell_status 30

Where: is:
30 location

System response

Start of report for LOCATION 30:

GSM CELL ID

MCC 001 001

MNC 01 01

LAC 17 (0011h) 17 (0011h)

CI 31 (001Fh) 33 (0021h)

RAC NA NA

------------------------------------------------------------

Primary Freq Type EGSM EGSM

Secondary Freq Type N/A N/A

BCCH Frequency 5 64

------------------------------------------------------------

68P02901W23-T 3-275
Jan 2010
Examples Chapter 3: Device/function related commands

Status Unbarred Unbarred

GPRS Status NA NA

PDCH Status Unknown Unknown

RES PDCH Requested NA NA

SW PCDH Requested NA NA

Reset in Prog No No

GPRS Reset in Prog NA NA

SPI in Prog No No

BSS BSSAP Prhb NA NA

MSC BSSAP Prhb NA NA

SPI/MSC SCCP Prhb NA NA

AccClass Bar None None

GPRS AccClass Bar NA NA

Full Power Mode OFF OFF

Ext Range Mode OFF OFF

Active PCU site NA NA

FREE INUSE UNAVL FREE INUSE UNAVL

----- ----- ----- ----- ----- -----

SDCCH 8 0 0 8 0 0

Norm Outer TCH/F 0 0 0 0 0 0

Ext Outer TCH/F 0 0 0 0 0 0

Norm Outer TCH/H 0 0 0 0 0 0

Norm Inner TCH/H 0 0 0 0 0 0

Norm Outer TCH/G 14 NA 0 6 NA 0

Norm Inner TCH/G 0 NA 0 0 NA 0

PD CHANNEL NA NA NA NA NA NA

End of Report.

3-276 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 5

This example shows the display when a location is entered and the GPRS feature is unrestricted.

disp_cell_status bsc

Where: is:
bsc location

System response

Start of report for LOCATION 0:

GSM CELL ID

MCC 001 001

MNC 01 01

LAC 1 (0001h) 1 (0001h)

CI 1 (0001h) 6 (0006h)

RAC 8 (0008h) NA

-------------------------------------------------------------

Primary Freq Type PGSM PGSM

Secondary Freq Type N/A N/A

BCCH Frequency 65 85

-------------------------------------------------------------

Status Unbarred Barred

GPRS Status Unbarred Barred

PDCH Status PD Available Unknown

RES PDCH Requested 3 NA

SW PDCH Requested 5 NA

Reset in Prog No No

GPRS Reset in Prog No No

SPI in Prog No No

BSS BSSAP Prhb NA NA

MSC BSSAP Prhb NA NA

SPI/MSC SCCP Prhb NA NA

AccClass Bar None NA

GPRS AccClass Bar 4 NA

Full Power Mode OFF OFF

68P02901W23-T 3-277
Jan 2010
Examples Chapter 3: Device/function related commands

Ext Range Mode OFF OFF

Active PCU site 1 N/A

FREE INUSE UNAVL FREE INUSE UNAVL

----- ----- ----- ----- ----- -----

SDCCH 4 0 0 0 0 0

Norm Outer TCH/F 7 0 0 0 0 0

Norm Inner TCH/F 0 0 0 0 0 0

Ext Outer TCH/F 0 0 0 0 0 0

PD CHANNEL 8 0 0 NA NA NA

End of Report

Example 6

This example displays the status of an in-service cell when the GPRS status is unbarred and
congestion status is TRUE from the PCU, irrelevant of EGPRS in ON or OFF status. The EGPRS
status is displayed in the field.

disp_cell_s 3

Where: is:
3 location

System response

Start of report for LOCATION 3:

GSM CELL ID

MCC 001

MNC 01

LAC 1 (0001h)

CI 1 (0028h)

RAC NA

Primary Freq Type EGSM

Secondary Freq Type N/A

BCCH Frequency 14

Status Unbarred

GPRS Status Unbarred EGPRS Avail

3-278 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

GPRS Congestion TRUE

PDCH Status PD Available
RES PDCH Requested 10
SW PDCH Requested 5
Reset in Prog No
GPRS Reset in Prog No
SPI in Prog No
BSS BSSAP Prhb No
MSC BSSAP Prhb No
SPI/MSC SCCP Prhb No
AccClass Bar NA
GPRS AccClass Bar 4
EGPRS Chan Req Avail
Full Power Mode OFF
Ext Range Mode OFF
Active PCU Site 0

FREE INUSE UNAVL

SDCCH 8 0 0
Norm Outer TCH/F 14 0 0
Norm Inner TCH/F 0 0 0
Ext Outer TCH/F 0 0 0
Norm Outer TCH/H 0 0 0
Norm Inner TCH/H 0 0 0
Norm Outer TCH/G 0 NA 0
Norm Inner TCH/G 0 NA 0
PD CHANNEL 1 6 0
EGPRS PD CHANNEL 6 2 0
End of Report.

Example 7

This example runs the disp_cell_status in high priority mode, BTS times out.

disp_cell_status 15 high

Where: is:
15 location
high high priority

68P02901W23-T 3-279
Jan 2010
Examples Chapter 3: Device/function related commands

System response

COMMAND REJECTED: The BTS is very busy, please try again later.

Example 8

This example displays the cell status with both the Extended Range Cell for Data feature
(ercgprsOpt) and EGPRS feature (egprsOpt) unrestricted.

disp_cell_s 3

Where: is:
3 location

System response

Start of report for LOCATION 3:

GSM CELL ID
MCC 001
MNC 01
LAC 1 (0001h)
CI 40 (0028h)
RAC N/A
Primary Freq Type EGSM
Secondary Freq Type N/A
BCCH Frequency 14
Status Unbarred
GPRS Status Unbarred, EGPRS Avail
PDCH Status PD Available
RES PDCH Requested 10
SW PDCH Requested 5
Reset in Prog No
GPRS Reset in Prog No
SPI in Prog No
BSS BSSAP Prhb No
MSC BSSAP Prhb No
SPI/MSC SCCP Prhb No
AccClass Bar N/A
GPRS AccClass Bar 4
EGPRS Chan Req Avail
Full Power Mode OFF
Ext Range Mode ON
Active PCU Site 0

3-280 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

FREE INUSE UNAVL

----- ----- -----

SDCCH 8 0 0

Norm Outer TCH/F 14 0 0

Norm Inner TCH/F 0 0 0

Ext Outer TCH/F 0 0 0

Norm Outer TCH/H 0 0 0

Norm Inner TCH/H 0 0 0

Norm Outer TCH/G 0 NA 0

Norm Inner TCH/G 0 NA 0

PD CHANNEL 1 6 0

EGPRS PD CHANNEL 2 2 0

Ext PD CHANNEL 2 0 0

Ext EGPRS PD CHANNEL 2 0 0

End of Report.

68P02901W23-T 3-281
Jan 2010
disp_conn Chapter 3: Device/function related commands

disp_conn

Description

The disp_conn command displays the MSS connectivity between the RXCDR and the BSS
sites connected to it.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is only available at a BSC or RXCDR site.

NOTE
The term local site refers to the site at which the command is executed; the term
remote site refers to the site to which the local site is connected.

Format

Syntax

disp_conn [<remote_entity_id>]

Input parameters

remote_entity_id

The network identity of the remote site. The valid range is 1 to 254.

Examples

Example 1

Display all the MMS connectivity between the BSS and all RXCDRs which are connected to it,
and are specified by equipped AXCDR devices at the BSC.

disp_conn

3-282 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

The BSS to RXCDR connectivity is as follows:

BSS MMS id 0 1 is connected to RXCDR 4 - MMS id 9 0

BSS MMS id 1 1 is connected to RXCDR 5 - MMS id 4 0

Finished displaying BSS to RXCDR connectivity

Example 2

Display the MMS connectivity between the BSS and RXCDR 5, which is represented by equipped
device AXCDR 5 at the BSC.

disp_conn 5

Where: is:
5 remote entity ID.

System response

The BSS to RXCDR connectivity is as follows:

BSS MMS id 1 1 is connected to RXCDR 5 - MMS id 4 0

Finished displaying BSS to RXCDR connectivity

68P02901W23-T 3-283
Jan 2010
disp_csfp Chapter 3: Device/function related commands

disp_csfp

Description

The disp_csfp command displays the per site CSFP algorithm or flow control values.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

disp_csfp <location> [<element>]

Input parameters

location

Specifies the element location:

0 or bsc BSC
1 - 140 BTS
pcu PCU

element

algorithm Selects the CSFP algorithm method

flow_control Selects the flow control value

3-284 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

This example shows the inputs required to display the CSFP algorithm at the BSC.

disp_csfp bsc algorithm

Where: is:
bsc location
algorithm element

System response

Site Algorithm

---- ---------

0 ANY

Example 2

his example shows the required inputs required to display the CSFP flow control at site 3:

disp_csfp 3 flow_control

Where: is:
3 location
flow_control element

System response

Site Flow Control

---- ------------

3 10

68P02901W23-T 3-285
Jan 2010
Examples Chapter 3: Device/function related commands

Example 3

This example shows the required inputs required to display all elements at site 7.

disp_csfp 7

Where: is:
7 location

System response

Site Flow Control Algorithm

---- ------------ ---------

7 10 ANY

Example 4

This example displays the csfp flow control value of PCU.

disp_csfp pcu flow_control

Where: is:
pcu location

System response

Site Flow Control Algorithm

---- ------------ ---------

PCU 10 N/A

Example 5

This example displays the status of PCU CSFP.

disp_csfp_status

3-286 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

SITE, ID CSFP EQUIP STATUS

CODE LOADED
0,0 YES
*
0,1 NO
CODE LOADED
1,0 YES
SITE/LINK OOS
3,0 YES

... ... ...

... ... ...

PCU,0 YES CODE LOADED

References

Related command

chg_csfp on page 3-101.

68P02901W23-T 3-287
Jan 2010
disp_csfp_status Chapter 3: Device/function related commands

disp_csfp_status

Description

The disp_csfp_status command displays the status of all CSFPs equipped in the BSS network.

{34371G} The command has two formats: without the parameter location, the command
displays the status of all CSFPs equipped in the BSS network. With the parameter location, the
command displays the status of all CSFPs that reside on HIISC2 and (R)CTU4 at a site. The
OMC GUI does not support the command format with location parameter. This command is
allowed only in SYSGEN OFF mode.

The output generated by this command is a three column listing with the following information:

SITE ID The site number

CSFP EQUIP or Equipped indicator (YES or NO)

{34371G} FRU TYPE FRU type for the device (HIISC2 for BTP, CTU4 or (R)CTU4
for DRI).
STATUS The status of the CSFP device as shown below:

Where: is:
* printed only with unequipped indicator.
NOT EQUIPPED the CSFP equipment is not installed.
DEVICE LOCKED the CSFP device is locked.
CODE LOADED the CSFP device is busy-unlocked, and the device is
code loaded.
AWAITING CODE the CSFP device is enabled-unlocked, and the device
is in a queue to be loaded, or is currently being
downloaded with code.
CSFP OOS the CSFP device is out of service.
NO CODE the CSFP device is disabled-unlocked, and the device
does not contain a valid software instance.
SITE/LINK OOS link is out of service.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.

3-288 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Format

Syntax

disp_csfp_status

{34371G}

disp_csfp_status <location>

Input parameters

{34371G}

location

Specifies the site location:

1 to 140 BTS

Examples

This example shows the input required to display the status of the CSFP devices in the BSS
network and the output when only one device is equipped and is loaded with code.

disp_csfp_status

Example 1

System response

SITE,ID CSFP EQUIP STATUS

0,0 YES CODE LOADED

Example 2

{34371G}

This example displays the status of CSFPs that reside on HIISC2 and (R)CTU4 at site 23.

disp_csfp_status 23

Where: is:
23 location

68P02901W23-T 3-289
Jan 2010
References Chapter 3: Device/function related commands

System response

SITE DEVICE ID FRU TYPE STATUS

23 BTP 0 0 BBU-E CODE LOADED

23 BTP 1 0 BBU-E NO CODE

23 DRI 0 0 CTU4 CODE LOADED

23 DRI 0 1 CTU4 CODE LOADED

23 DRI 0 2 CTU4 CODE LOADED

23 DRI 0 3 CTU4 CODE LOADED

23 DRI 0 4 CTU4 NO CODE

23 DRI 0 5 CTU4 NO CODE

23 DRI 0 6 CTU4 NO CODE

23 DRI 0 7 CTU4 NO CODE

23 DRI 1 0 RCTU4 NO CODE

23 DRI 1 1 RCTU4 NO CODE

23 DRI 1 2 RCTU4 NO CODE

23 DRI 1 3 RCTU4 NO CODE

References

Related command

chg_csfp on page 3-101.

3-290 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_dte

disp_dte

Description

The disp_dte command displays DTE addresses. This command is primarily for use by field
technicians or installers.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_dte [<link> <link_number>]

If no input parameters are specified, all BSS and OMC-R DTE addresses are displayed.

Input parameters

link

The location of the link:

bsc BSC
omcr OMC-R
cbc Cell Broadcast Center (CBC)
bsc_cbc BSC DTE Address for the CBC

link_num

The link number range:

0 to 3 link at BSC
0 to 7 link at OMC-R
0 link at CBC or BSC_CBC

68P02901W23-T 3-291
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

In this example, the DTE link addresses are displayed (in binary coded decimal) when the
command is entered:

disp_dte

System response

BSS DTE addresses:

Address #0: 31070863210701

Address #1: 31070863210701

Address #2: 31070863210701

Address #3: 31070863210701

OMCR DTE addresses:

Address #0: 31031263245610

Address #1: 31031263245620

Address #2: 31031263245630

Address #3: 31031263245640

Address #4: 31031263245650

Address #5: 31031263245660

Address #6: 31031263245670

Address #7: 31031263245680

Example 2

In this example, the DTE link address and link numbers are displayed when the command
is entered:

disp_dte bsc 2

Where: is:
bsc location
2 link_num

System response

Address #2: 31070863210701

3-292 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related command

chg_dte on page 3-104.

68P02901W23-T 3-293
Jan 2010
disp_element Chapter 3: Device/function related commands

disp_element

Description

The disp_element command displays the value of a database parameter in the CM database.

NOTE
The syntax required to display each CM database parameter is included in the
parameter description in Chapter 6 CM database parameters.

Security level 1

Supported by OMC-R GUI Yes

Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_element <database_parameter>[,<index1>][,<index2>] <location> [<cell_desc>]

Input parameters

database_parameter

String identifying the database parameter in the CM database.

index1

If a database parameter value to be displayed requires an index, the index value must be entered
immediately after the database parameter name separated by a comma.

Database parameters modified using the chg_cell_element command are stored in a four row
data array. The rows in the data array are specified as bins in the chg_cell_element command.
Individual database parameter values modified using the chg_cell_element command cannot
be displayed using the disp_element command.

When the disp_element command is used to display the values of parameters modified using
the chg_cell_element command, the row (bin_num) is entered as the index1 value. All 32
values located in the entered row number are displayed. An example is included at the end of
the description of this command.

3-294 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

location

Specifies the site location:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

all Specifies all sites.

cell_desc

GSM cell ID of the cell to be displayed, preceded by cell_number=.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command is entered in place of the
cell_number. When the cell name is entered, it must be placed inside double quotation marks
and be preceded by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

The cell_desc can also be specified as all.

Examples

Example 1

In this example, the bit error rate loss threshold per day is 16 for site number 0:

disp_element ber_loss_daily 0

Where: is:
ber_loss_daily database_parameter
0 location

System response

ber_loss_daily = 16

68P02901W23-T 3-295
Jan 2010
Examples Chapter 3: Device/function related commands

Example 2

In this example, the values of a database element modified using the chg_cell_element
command are displayed. The bin number (0) is entered as the index value.

disp_element rxlev_dl_ho,0 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
rxlev_dl_ho database_parameter
0 index (bin num)
1 location
5 4 3 2 1 61986 34944 cell_desc

NOTE
This example could have been entered as:
disp_element rxlev_dl_ho,0 1 cell_name=london-south
where the command cell_name had been used to assign the name london-south to
the cell with ID = 5 4 3 2 1 61986 34944.

System response

rxlev_dl_ho[0] = alg_num: 0 alg_data: 8

Example 3

In this example, the value of the database element ss7_hsp_12_t1 is displayed.

disp_element ss7_hsp_l2_t1 0

Where: is:
ss7_hsp_12_t1 database_parameter
0 location

System response

ss7_hsp_l2_t1 = 300000

3-296 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 4

This example displays the prp_fanout_mode parameter.

disp_element prp_fanout_mode pcu

Where: is:
prp_fanout_mode database_parameter
pcu location

System response

prp_fanout_mode = 1

Example 5

This example displays the value of td_enabled element.

disp_element td_enabled 0

Where: is:
td_enabled database_parameter
0 location

System response

td_enabled = 0

Example 6

This example displays the fieldeng_always_enabled element.

disp_element fieldeng_always_enabled 0

Where: is:
fieldeng_always_enabled database_parameter
0 location

System response

fieldeng_always_enabled = 1

68P02901W23-T 3-297
Jan 2010
Examples Chapter 3: Device/function related commands

Example 7

This example allows the operator to display the value of cell barred delay (in seconds).

disp_element cell_barred_delay 0

Where: is:
cell_barred_delay database_parameter
0 location

System response

cell_barred_delay = 180
COMMAND ACCEPTED

Example 8

This example displays the value of dsp_error_inc element.

disp_element dsp_error_inc 0

Where: is:
dsp_error_inc database_parameter
0 location

System response

dsp_error_inc = 30

Example 9

This example displays the value of ext_ul_dur.

disp_element ext_ul_dur 0

Where: is:
ext_ul_dur database_parameter
0 location

System response

ext_ul_dur = 24

3-298 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 10

This example displays the status of the switch for AGCH flow control.

disp_element agch_flow_control_mode 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
agch_flow_control_mode database_parameter
1 location
5 4 3 2 1 61986 34944 cell description

System Response

agch_flow_control_mode = 1

Example 11

This example displays the value of sig_lnk_tst_allow.

disp_elem sig_lnk_tst_allow 0

Where: is:
sig_lnk_tst_allow database_parameter
0 location

System Response

sig_lnk_tst_allow = 1

Example 12

This example displays the value of sig_lnk_tst_allow.

disp_elem sig_lnk_tst_allow 0

Where: is:
sig_lnk_tst_allow database_parameter
0 location

System Response

sig_lnk_tst_allow = 0

68P02901W23-T 3-299
Jan 2010
Examples Chapter 3: Device/function related commands

Example 13

This example displays the fer_meas_period value.

disp_element fer_meas_period 0

Where: is:
fer_meas_period database_parameter
0 location

System Response

fer_meas_period = 1

Example 14

This example displays the cstats_bss_enabled value.

disp_element cstats_bss_enabled 0

Where: is:
cstats_bss_enabled database_parameter
0 location

System Response

cstats_bss_enabled = 1

Example 15

This example displays the cstats_cell_enabled value of cell 0 0 1 0 1 99 72 under site 114.

disp_element cstats_cell_enabled 114 cell 0 0 1 0 1 99 72

Where: is:
cstats_cell_enabled database_parameter
114 location
0 0 1 0 1 99 72 cell description

System Response

cstats_cell_enabled = 1

3-300 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 16

This example displays the status of the PA Bias feature at site 2 with the feature enabled.

disp_element power_save_enable 2

Where: is:
power_save_enable element name
2 location

System Response

power_save_enable = 1

Example 17

This example displays the value of the Abis status element for Horizon BTS (Site id = 1) when
the Dual Abis Aware feature is enabled.

disp_element abis_state_element 1

Where: is:
abis_state_element database_parameter
1 location

System Response

abis_state_element = 0

Example 18

This example displays the value of the Abis status element for all the BTS sites when the Dual
Abis Aware feature is enabled.

disp_element abis_state_element all

Where: is:
abis_state_element database_parameter
all location

68P02901W23-T 3-301
Jan 2010
Examples Chapter 3: Device/function related commands

System Response

ELEMENT: abis_state_element
SITE ELEMENT VALUE
---- -------------
0 0
11 1
12 0

Example 19

This example displays the value of the bsp_overload_protection parameter.

disp_element bsp_overload_protection bsc

Where: is:
bsp_overload_protection database_parameter
bsc location

System response

bsp_overload_protection = 0

Example 20

This example displays the value of the Abis status element for H1 BTS (Site id = 1) when the
Dual Abis Aware feature is enabled.

disp_element _site_data,5 1

Where: is:
_site_data, 5 database_parameter
1 location

System Response

_site_data,5 = 0

3-302 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 21

This example displays the value of the Abis status element for all the BTS sites when the Dual
Abis Aware feature is enabled.

disp_element _site_data, 5 all

Where: is:
_site_data, 5 database_parameter
all location

System Response

ELEMENT: _site_data
SITE ELEMENT VALUE
---- -------------
0 0
11 1
12 0

Example 22

{26638}

This example displays the gb_mode parameter when it is set as static IP.

disp_element gb_mode 0

Where: is:
gb_mode element name
0 location

System Response

gb_mode = 1

68P02901W23-T 3-303
Jan 2010
Examples Chapter 3: Device/function related commands

Example 23

{34452}

This example displays the mobile flow control enabled state when the mobile works in flow
control disabled state.

disp_element ms_flow_control_enabled 0

Where: is:
ms_flow_control_enabled element name
0 location

System Response

ms_flow_control_enabled = 0

Example 24

{34452}

This example displays the value of the cstats_bss_enabled parameter.

disp_element cstats_bss_enabled 0

Where: is:
cstats_bss_enabled element name
0 location

System Response

cstats_bss_enabled = 1

Example 25

{34452}

This example displays the value of the cage_manage_enabled parameter.

disp_element cage_manage_enabled 0

Where: is:
cage_manage_enabled element name
0 location

3-304 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System Response

cage_manage_enabled = 1

Example 26

{34452}

This example displays the PRM detect mode when PRM can send the USF to all the GPRS
mobiles in the GMSK blocks.

disp_element gmsk_capability_mode 0

Where: is:
gmsk_capability_mode element name
0 location

System Response

gmsk_capability_mode = 0

Example 27

{34452}

This example displays the PUAK working mode when working on forced uncompressed PUAK
mode.

disp_element puak_compress_mode 0

Where: is:
puak_compress_mode element name
0 location

System Response

puak_compress_mode = 2

68P02901W23-T 3-305
Jan 2010
Examples Chapter 3: Device/function related commands

Example 28

{34452}

This example displays whether the AMR homing sequence filter is enabled when working on the
disabled AMR homing sequence filter.

disp_element amr_home_filter_enabled 0

Where: is:
amr_home_filter_enabled element name
0 location

System Response

amr_home_filter_enabled = 0

Example 29

{34452}

This example displays the status of using idle TCH for burst packet traffic function, irrelevant
to EDGE purchase or on/off status.

disp_element congest_pd_expand_enabled pcu

Where: is:
congest_pd_expand_enabled element name
pcu location

System Response

congest_pd_expand_enabled = 1

Example 30

{34452}

This example displays the value of the gprs_edge_mismatch_sigma parameter for cell 0 0 1
0 1 99 72 under site 114.

disp_element gprs_edge_mismatch_sigma 114 cell 0 0 1 0 1 99 72

Where: is:
gprs_edge_mismatch_sigma element name
114 location
0 0 1 0 1 99 72 cell number

3-306 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System Response

gprs_edge_mismatch_sigma = 20

Example 31

{34452}

This example displays the value of the gprs_asym_mismatch_delta parameter for cell 0 0 1
0 1 99 72 under site 114.

disp_ele gprs_asym_mismatch_delta 114 cell 0 0 1 0 1 99 72

Where: is:
gprs_asym_mismatch_delta element name
114 location
0 0 1 0 1 99 72 cell number

System Response

gprs_asym_mismatch_delta = 20

Example 32

{34452}

This example displays the value of the edge_asym_mismatch_cita parameter for cell 0 0 1
0 1 99 72 under site 114.

disp_ele edge_asym_mismatch_cita 114 cell 0 0 1 0 1 99 72

Where: is:
edge_asym_mismatch_cita element name
114 location
0 0 1 0 1 99 72 cell number

System Response

edge_asym_mismatch_cita = 20

68P02901W23-T 3-307
Jan 2010
Examples Chapter 3: Device/function related commands

Example 33

{34452}

This example displays the value of the pch_queue_length_ctr parameter for cell 0 0 1 0 1
99 72 under site 114.

disp_ele pch_queue_length_ctr 114 cell 0 0 1 0 1 99 72

Where: is:
pch_queue_length_ctr element name
114 location
0 0 1 0 1 99 72 cell number

System Response

pch_queue_length_ctr = 1

Example 34

{34452}

This example displays the status of Intelligent Selective Paging.

disp_element isp_enabled 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
isp_enabled element name
1 location
5 4 3 2 1 61986 34944 cell number

System Response

isp_enabled = 1

3-308 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 35

{34452}

This example displays the status of the switch for AGCH flow control.

disp_element agch_flow_control_mode 1 cell_number=5 4 3 2 1 61986 34944

Where: is:
agch_flow_control_mode element name
1 location
5 4 3 2 1 61986 34944 cell number

System Response

agch_flow_control_mode = 1

Example 36

{34452}

This example displays the value of the cstats_cell_enabled parameter for cell 0 0 1 0 1 99 72
under site 114.

disp_ele cstats_cell_enabled 114 cell 0 0 1 0 1 99 72

Where: is:
cstats_cell_enabled element name
114 location
0 0 1 0 1 99 72 cell number

System Response

cstats_cell_enabled = 1

68P02901W23-T 3-309
Jan 2010
Examples Chapter 3: Device/function related commands

Example 37

{34452}

This example displays the value of the new_calls_amr_hr parameter for cell 0 0 1 0 1 1 4
at site 2.

disp_element new_calls_amr_hr 2 cell 0 0 1 0 1 1 4

Where: is:
new_calls_amr_hr element name
2 location
0010114 cell number

System Response

new_calls_amr_hr = 10

Example 38

{34452}

This example displays the value of the reconfig_fr_to_amr_hr parameter for cell 0 0 1 0 1 1 4
at site 2.

disp_element reconfig_fr_to_amr_hr 2 cell 0 0 1 0 1 1 4

Where: is:
reconfig_fr_to_amr_hr element name
2 location
0010114 cell number

System Response

reconfig_fr_to_amr_hr = 101

3-310 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 39

{34452}

This example displays the value of the inner_amr_hr_usage_thres parameter for cell 0 0 1 0
1 1 4 at site 2.

disp_element inner_amr_hr_usage_thres 2 cell 0 0 1 0 1 1 4

Where: is:
inner_amr_hr_usage_thres element name
2 location
0010114 cell number

System Response

inner_amr_hr_usage_thres = 101

Example 40

This example displays the _bss_data,10 value.

disp_element _bss_data,10 0

Where: is:

_bss_data,10 element name

0 location

System Response

_bss_data,10 = 1

Example 41

This example displays the value of _bss_data,6.

disp_element _bss_data,6 0

Where: is:
_bss_data,6 element name
0 location

System Response

_bss_data,6 = 0

68P02901W23-T 3-311
Jan 2010
Examples Chapter 3: Device/function related commands

Example 42

This example displays the nacc_nc2_enabled value.

disp_element nacc_nc2_enabled 0

Where: is:
nacc_nc2_enabled element name
0 location

System Response

nacc_nc2_enabled = 1

Example 43

{36039G}

This example displays the value of the abis_auto_swap_enabled parameter.

disp_element abis_auto_swap_enabled 0

Where: is:
abis_auto_swap_enabled element name
0 location

System Response

abis_auto_swap_enabled = 0

Example 44

{36039G}

This example displays the value of the timer.

disp_element t_terrestrial_fail 0

Where: is:
t_terrestrial_fail element name
0 location

System Response

t_terrestrial_fail = 6

3-312 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 45

{36039G}

This example displays the value of max_tx_bts_standby.

disp_element max_tx_bts_standby 13 cell = 0 0 1 0 1 121 13

Where: is:
max_tx_bts_standby element name
13 location
0 0 1 0 1 121 13 cell_desc

System Response

max_tx_bts_standby = 0

Example 46

{36039G}

This example displays the value of super_bts_indicator to see if site 69 is a super BTS.

disp_element super_bts_indicator 69

Where: is:
super_bts_indicator element name
69 location

System Response

super_bts_indicator = 0

Example 47

{36039G}

This example displays the value of super_bts_indicator of all the BTS sites under the BSC to
see the super BTS status.

disp_element super_bts_indicator all

Where: is:
super_bts_indicator element name
all location

68P02901W23-T 3-313
Jan 2010
References Chapter 3: Device/function related commands

System Response

ELEMENT: super_bts_indicator
SITE ELEMENT VALUE
---- -------------
0 1
11 0
12 1
15 1

References

Related information

For detailed information on database parameters, refer to CM database parameters

presentation on page 6-2.

Related commands

chg_element on page 3-112.

3-314 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_equipment

disp_equipment

Description

The disp_equipment command displays the software and hardware information of equipped
devices and functions. Information displayed includes the parameters entered for a specific
device or function using the equip command.

The disp_equipment command displays the actual cell GPRS configuration information per
PCU and PRP/PXP level along with the existing equipment information.

Equipment configurations typically vary by location, therefore, the devices and functions
available for display vary from site to site. This command is used to identify the site equipment
configuration using location as the only command argument.

The full option permits hardware information to be displayed in addition to the equipment
parameters. This hardware information includes the hardware version number (hvn) displayed
as a numerical value. A single hvn represents one or more kit numbers for a specific printed
circuit board. The relationship of the hvn to the kit number is dependent on the equipment
configuration.

In later releases, a kit number is displayed in place of a hvn. A kit number includes the current
hardware and firmware revisions of the printed circuit board. Kit numbers are incremented in
response to either a hardware or firmware change. More than one firmware version can exist
for any given hardware version of a printed circuit board.

Kit numbers use the following format:

SLN7133BA

Where: is:
SLN7133 a unique value identifying a specific printed circuit board.
B the hardware version of the printed circuit board
represented as an alphabetical value.
A the firmware version of the printed circuit board.

This can then be followed by further information, dependent on the particular hardware and
its revision level, such as:

EFGH Each letter corresponds to a miscellaneous change

made to the printed circuit board in the manufacturing
process that did not require new hardware or firmware.
REV 0 This numerical value represents the current revision
level of the most recent change.
MEM 0238 - BIT ERROR RATE This is additional descriptive information related to the
TEST last revision to the printed circuit board.

68P02901W23-T 3-315
Jan 2010
Format Chapter 3: Device/function related commands

The disp_equipment command does not report the hvns for half size boards.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_equipment <location> [<dev/func name> <id1> [<id2>] [<id3>]] [full]

Input parameters

location

Specifies the equipment location:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

dev/func name

Literal that uniquely identifies the device or function

id1

First identifier or the wild-card character *.

id2

Second identifier or the wild-card character *.

id3

Third identifier or the wild-card character *.

full

This is an optional parameter that is used to display the hardware-specific information for a
device in addition to the configuration information entered when the device is equipped. When
this option is used to display all of the equipment at a site, the output is a table which includes
kit and serial numbers.

NOTE
The full option is not allowed while in SYSGEN ON mode.

3-316 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

CIC syntax

Because the Circuit Identity Code (CIC) device can be specified in different ways, the different
forms of syntax are detailed as follows:

Valid for local transcoding:

disp_equipment <location> CIC <cic_num1>

Valid for remote transcoding:

disp_equipment <location> CIC <cic_num1>

disp_equipment <location> CIC <mms_id1> <mms_id2> <timeslot1>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS

CIC

Literal that uniquely identifies the CIC device.

cic_num1

First CIC device number.

cic_num2

Last CIC device number in a range.

mms_id1

First MMS identifier.

mms_id2

Second MMS identifier, or last in a range if TO is used.

timeslot1

First timeslot.

timeslot2

Second timeslot, or last in a range if TO is used.

group1

First group.

group2

Second group.

68P02901W23-T 3-317
Jan 2010
Examples Chapter 3: Device/function related commands

Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

Examples

Example 1

In the following example, all equipment at location 0 are displayed:

disp_equipment 0 full

Where: is:
0 location
full full option

System response

Device FRU Kit Number Serial Number HVN

---------------- -------------- ----------------- --------------- ----

GPROC 2 0 0 GPROC2 Not Applicable Not Applicable 4

GPROC 3 0 0 Unavailable Unavailable Unavailable 255

GPROC 1 0 0 GPROC2 Not Applicable Not Applicable 4

BSP 0 0 0 GPROC2 Not Applicable Not Applicable 4

CSFP 0 0 0 Unavailable Unavailable Unavailable 255

MSI 0 0 0 MSII Not Applicable Not Applicable 4

MMS 0 0 0 Unavailable Unavailable Unavailable 255

MMS 0 0 0 Unavailable Unavailable Unavailable 255

MTL 0 0 0 Unavailable Unavailable Unavailable 255

RSL 2 0 0 Unavailable Unavailable Unavailable 255

RSL 3 0 0 Unavailable Unavailable Unavailable 255

SITE 3 0 0 Unavailable Unavailable Unavailable 255

SITE 4 0 0 Unavailable Unavailable Unavailable 255

PATH 1 0 0 Unavailable Unavailable Unavailable 255

3-318 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

BSS 1 0 0 Not Applicable

LCF 1 0 0 Not Applicable

Type Cage Slot HVN

------- -------- -------- -----

KSWX 0 21 48

Example 2

In the following example, only KSWX at location 0 are displayed:

disp_equipment 0 kswx * * * full

Where: is:
0 location
kswx device/function name
*** 1st, 2nd, and 3rd identifier wild cards.
full full option

System response

Type Cage Slot HVN

----- -------- -------- --------

KSWX 0 21 48

Example 3

This example shows the values entered when RTF 0 1 at location 2 was equipped.

disp_equipment 2 rtf 0 1

Where: is:
2 location
rtf device/func name
0 first identifier
1 second identifier

68P02901W23-T 3-319
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Capacity of carrier: FULL

Type of carrier: NON_BCCH

RTF identifier: 0 1

The primary Unique PATH id is: 0

GSM cell to which this carrier is assigned: 262 01 510 211

Carrier absolute radio freq. channel: 61

Carrier frequency hopping indicators: 0 0 0 0 0 0 0 0

Carrier training sequence codes: 5 5 5 5 5 5 5 5

KSW pair that manages this carrier: 0

Cell zone: 0

Number of extended range timeslots allowed: 0

SDCCH load: 2

SDCCH placement priority: 2

Channel allocation priority: 2

The maximum number of PDCHs: 4

The number of reserved PDCHs: 2

32 kbps GPRS TRAU allowed: yes

Example 4

This example displays information for PCU 0 (3 TRAU GDS and 2 PMCs equipped on 2 PRPs, 8
64 K air PDTCHs, 81 16 K air PDTCHs) when EGPRS is unrestricted.

disp_equipment 0 PCU 0

Where: is:
0 location
PCU device/func name
0 PCU identifier

3-320 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

PCU identifier: 0

PCU IP Address[ip_address]: 127.0.0.1

PCU Subnet Mask[subnet_mask]: 255.255.255.255

PCU Router IP Address[router_ip_address]: 127.0.0.1

NSEI: 27

Primary Cells:

001 01 1 1

001 01 1 6

001 01 1 3

001 01 1 33

001 01 1 18

Provisioned Requested

-------------------------

Usable PRP PDTCHs: 240 89

Usable 16 K GDS Resources: 372 113

64 K or 32 K or 16 K

--- ---- ----

Max Configurable PDTCHs: 64 75 151

Example 5

This example displays information for HSP MTL.

disp_equipment 0 mtl 1 0

Where: is:
0 location
mtl device/func name
1 first identifier
0 second identifier

68P02901W23-T 3-321
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Device ID for the MTL: 1

DS0 channels for this MTL: 31
First MMS identifier for this device: 0
Second MMS identifier for this device: 1
Timeslot on MMS where this device appears: 1

Example 6

This example displays information for 64 k MTL.

disp_equipment 0 mtl 10 0

Where: is:
0 location
mtl device/func name
10 first identifier
0 second identifier

System response

Device identification for this MTL: 10

DS0 channels for this MTL: 1
First MMS identifier for this device: 1
Second MMS identifier for this device: 0
Timeslot on MMS where this device appears: 8

Example 7

This example displays an MTL LCF handling the HSP MTL.

disp_eq 0 lcf 1

Where: is:
0 location
lcf device/func name
1 first identifier

3-322 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Function ID for the LCF: 1

Number of DS0 channels the LCF can manage as MTLs [max_mtls]: 31
Number of CBLs the LCF can manage[max_cbls]: 0
Number of GSLs the LCF can manage[max_gsls]: 0

Example 8

This example displays the PXP DPROC with the FULL option.

disp_equipment pcu_0 dproc 4 0 full

Where: is:
pcu_0 location
dproc device/function name
4 first identifier
0 second identifier
full option

System response

DPROC id: 4
DPROC type: PXP
Hardware Information:
PCI Vendor Id: 1223h
PCI Device Id: 0048h
PCI Revision Id: 1h
PCI Type: UNKNOWN
HSC Type: UNKNOWN
IP Address Information:
DPROC (750): 10.0.130.1
Current Cell Mapping:
GSM CELL ID SITE MCC MNC LAC CI LCI
---- ------------------------------------ ---
11 001 01 403 (0193h) 11 (000Bh) 0

68P02901W23-T 3-323
Jan 2010
Examples Chapter 3: Device/function related commands

Example 9

The example displays a PXP DPROC.

disp_equipment PCU DPROC 1

Where: is:
PCU location
DPROC device/function name
1 first identifier

System response

DPROC id: 1
DPROC type: PXP

Example 10

This example displays the ETH device.

disp_equipment bsc eth 1 0 0

Where: is:
bsc location
eth device/function name
1 first identifier
0 second identifier
0 third identifier

System response

PSI identifier: 1
Ethernet port id: 0

3-324 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 11

This example displays Horizon II micro cabinet at site 5.

disp_equip 5 CAB 15 0 0

Where: is:
5 location
CAB device/function name
15 first identifier
0 second identifier
0 third identifier

System response

CABINET identifier: 15
Cabinet type: HORIZON2MINI_EXT
Frequency type: PGSM

Example 12

This example displays the information for PCU 0 without full option.

disp_equipment 0 PCU 0

Where: is:
0 location
PCU device/function name
0 first identifier

68P02901W23-T 3-325
Jan 2010
Examples Chapter 3: Device/function related commands

System response

PCU identifier: 0

PCU IP Address[ip_address]: 127.0.0.1

PCU Subnet Mask[subnet_mask]: 255.255.255.255

PCU Router IP Address[router_ip_address]: 127.0.0.1

NSEI: 27

PRP Fanout Mode: 1

GSM CELL ID

MCC MNC LAC CI LCI

--- --- --- --- ---

001 01 696 26 0

001 01 696 27 2

001 01 696 16 1

001 01 696 72 3

Provisioned Requested

-------------------------

Usable PRP PDTCHs: 240 89

Usable 16 K GDS Resources: 372 113

64 K or 32 K or 16 K

--- ---- ----

Max Configurable PDTCHs: 64 75 151

Example 13

This example displays the information for PCU 0 with full option.

disp_equipment 0 PCU 0 full

Where: is:
0 location
PCU device/function name
0 first identifier
full option

System response

PCU identifier: 0

3-326 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

PCU IP Address[ip_address]: 127.0.0.1

PCU Subnet Mask[subnet_mask]: 255.255.255.255

PCU Router IP Address[router_ip_address]: 127.0.0.1

NSEI: 27

PRP Fanout Mode: 1

GSM CELL ID

MCC MNC LAC CI LCI

--- --- --- --- ---

001 01 696 26 0

001 01 696 27 2

001 01 696 16 1

001 01 696 72 3

Provisioned Requested

-------------------------

Usable PRP PDTCHs: 240 89

Usable 16 K GDS Resources: 372 113

64 K or 32 K or 16 K

--- ---- ----

Max Configurable PDTCHs: 64 75 151

Hardware Information: Not Applicable

Configured Database GDS All PD
SITE LCI PRP 16/32/64k RES/SW 16/32/64k Configured
---- ------------------------------------ -- --
1 0 1 6/0/6 8/4 6/0/6 Yes
10 2 1 0/12/0 8/4 0/12/0 Yes
10 1 2 2/0/6 7/4 2/0/6 No
1 3 2 5/0/3 4/4 5/0/2 Yes
NUMBER OF ACTUAL CONNECTED GCIs: 93
NUMBER OF ACTUAL 16K GCIs: 13 RCIs: 13
NUMBER OF ACTUAL 32K GCIs: 24 RCIs: 12
NUMBER OF ACTUAL 64K GCIs: 56 RCIs: 15
NUMBER OF ACTUAL FREE GCI COUNT: 31
NUMBER OF FREE DS0: 7

68P02901W23-T 3-327
Jan 2010
Examples Chapter 3: Device/function related commands

Example 14

This example displays the information for PRP DPROC 4 0 0 on PCU 0.

disp_equipment pcu DPROC 4 0 0 FULL

Where: is:
PCU location
DPROC device/function name
4 first identifier
0 second identifier
0 third identifier
FULL option

System response

DPROC id: 4
DPROC type: PRP
Hardware Information:
PCI Vendor Id: 1146h
PCI Device Id: 6750h
PCI Revision Id: 1h
PCI Type: UNKNOWN
HSC Type: UNKNOWN
Current Cell Mapping:
GSM CELL ID Configured Database GDS All PD
SITE MCC MNC LAC CI LCI 16/32/64k RES/SW 16/32/64k Configured
---- ------------------------------------ -- -- --
1 001 01 696 26 0 6/0/6 8/4 6/0/6 Yes
10 001 01 696 27 2 0/12/0 8/4 0/12/0 Yes
10 001 01 696 16 1 2/0/6 7/4 2/0/6 No
1 001 01 696 72 3 5/0/3 4/4 2/0/2 Yes
NUMBER OF ACTUAL CONNECTED GCIs: 93
NUMBER OF ACTUAL 16K GCIs: 13 RCIs: 13
NUMBER OF ACTUAL 32K GCIs: 24 RCIs: 12
NUMBER OF ACTUAL 64K GCIs: 56 RCIs: 15

The output is explained as follows:

PRP: indicates the PRP device ID. (PXP PPROC Device ID equals to PXP DPROC Device ID
plus 16.)

Configured 16k: indicates the actual configured 16k INS PDTCH number in a specific cell,
which is obtained from PCU.

3-328 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Configured 32k: indicates the actual configured 32k INS PDTCH number in a specific cell,
which is obtained from PCU.

Configured 64k: indicates the actual configured 64k INS PDTCH number in a specific cell,
which is obtained from PCU.

Database SW: indicates the switchable PDTCH demands configured in the database (sw_pdtch)
for a specific cell.

Database RES: indicates the reserved PDTCH demands configured in the database (res_pdtch)
for a specific cell.

GDS 16k: indicates the number of INS 16k GDS actually configured for these specific cells.
Currently, this number is exactly equal to the number of configured 16k PDTCHs.

GDS 32k: indicates the number of INS 32k GDS actually configured for these specific cells.
Currently, this number is exactly equal to the number of configured 32k PDTCHs.

GDS 64k: indicates the number of 64k INS GDS DS0 actually configured for all 64k RTF in
specific cells.

All PD configured: indicates whether all PDTCH demands required in the database are
actually configured in the cells.

Yes: When the sum of all configured 16k, 32k, 64k INS PDTCH is greater or equal to the sum of
switchable (sw_pdtch) and reserved PDTCH (res_pdtch) demands in the database.

No: When the sum of all configured 16k, 32k, 64k INS PDTCH is less than the sum of switchable
(sw_pdtch) and reserved PDTCH (res_pdtch) demands in the database.

NUMBER OF ACTUAL CONNECTED GCIs: indicates the total GCI actually used in this PCU,
PRP/PXP DPROC and PPROC. 1 for one 16k GDS, 2 for one 32k GDS and 4 for one 64k GDS.

NUMBER OF ACTUAL 16K/32K/64K GCIs: indicates the 16k/32k/64k GCI actually used in
this PCU, PRP/PXP DPROC and PPROC. 1 for one 16k GDS, 2 for one 32k GDS and 4 for one
64k GDS.

NUMBER OF ACTUAL 16K/32K/64K RCIs: indicates the 16k/32k/64k radio resource actually
used in this PCU, PRP/PXP DPROC and PPROC. 1 for one 16k/32k/64k PDTCH.

NUMBER OF ACTUAL FREE GCI COUNT: indicates the free 16k GCI in this PCU. The total
16k GCI depends on the number of TRAU GDSs equipped in a PCU. (Only applicable for per
PCU query.)

NOTE
If EGPRS is not purchased and 2 GDSs are equipped on a PMC, only 124 GCIs can
be used.

NUMBER OF FREE DS0: indicates the free 64k GDS DS0 in this PCU. It is similar to the
number of actual free 16k GCI in 64k DS0 format. (Only applicable for per PCU query.)

68P02901W23-T 3-329
Jan 2010
Examples Chapter 3: Device/function related commands

NOTE

Only when the Support the usage of idle TCH for packet burst traffic feature is
enabled, the sum of all configured 16 k, 32 k and 64 k PDTCH is greater than the
sum of switchable and reserved PDTCH demands in the database.
All reasons of PDTCH shrink (including stolen by voice call, PDTCH OOS, carrier
OOS and insufficient GPRS processing or backhaul resources, and so on) and
causes the actual PDTCH number to be less than the demands value in the
database is treated as NOT all PDTCH configured.

Example 15

This example displays the information for PXP DPROC 4 0 0 on PCU 0.

disp_equipment pcu DPROC 4 0 0 FULL

Where: is:
PCU location
DPROC device/function name
4 first identifier
0 second identifier
0 third identifier
FULL option

3-330 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

DPROC id: 4
DPROC type: PXP
Hardware Information:
PCI Vendor Id: 1146h
PCI Device Id: 6750h
PCI Revision Id: 1h
PCI Type: UNKNOWN
HSC Type: UNKNOWN
IP Address Information:
DPROC (750): 10.0.130.1
Current Cell Mapping:
GSM CELL ID Configured Database GDS All PD
SITE MCC MNC LAC CI LCI 16/32/64k RES/SW 16/32/64k Configured
---- ------------------------------------ -- -- --
1 001 01 696 26 0 6/0/6 8/4 6/0/6 Yes
10 001 01 696 27 2 0/12/0 8/4 0/12/0 Yes
10 001 01 696 16 1 2/0/6 7/4 2/0/6 No
1 001 01 696 72 3 5/0/3 4/4 2/0/2 Yes
NUMBER OF ACTUAL CONNECTED GCIs: 93
NUMBER OF ACTUAL 16K GCIs: 13 RCIs: 13
NUMBER OF ACTUAL 32K GCIs: 24 RCIs: 12
NUMBER OF ACTUAL 64K GCIs: 56 RCIs: 15

Example 16

This example displays information for PPROC 4 0 0 on PCU 0.

disp_equipment pcu PPROC 4 0 0 FULL

Where: is:
PCU location
PPROC device/function name
4 first identifier
0 second identifier
0 third identifier
FULL option

68P02901W23-T 3-331
Jan 2010
Examples Chapter 3: Device/function related commands

System response

PPROC id: 4
Hardware Information:
PCI Vendor Id: 1146h
PCI Device Id: 6750h
PCI Revision Id: 1h
PCI Type: UNKNOWN
HSC Type: UNKNOWN
IP Address Information:
PPROC: 10.0.130.33
Current Cell Mapping:
GSM CELL ID Configured Database GDS All PD
SITE MCC MNC LAC CI LCI 16/32/64k RES/SW 16/32/64k Configured
---- ------------------------------------ -- -- --
1 001 01 696 26 0 6/0/6 8/4 6/0/6 Yes
10 001 01 696 27 2 0/12/0 8/4 0/12/0 Yes
10 001 01 696 16 1 2/0/6 7/4 2/0/6 No
1 001 01 696 72 3 5/0/3 4/4 2/0/2 Yes
NUMBER OF ACTUAL CONNECTED GCIs: 93
NUMBER OF ACTUAL 16K GCIs: 13 RCIs: 13
NUMBER OF ACTUAL 32K GCIs: 24 RCIs: 12
NUMBER OF ACTUAL 64K GCIs: 56 RCIs: 15

Example 17

This example attempts to display information for PRP DPROC 4 0 0 on PCU 0 with full option
which is rejected due to the same query being performed by the other MMI session.

NOTE
The rejection output is similar for the simultaneous PCU, PXP DPROC and PPROC
query by several MMI sessions.

disp_equipment pcu DPROC 4 0 0 FULL

Where: is:
PCU location
DPROC device/function name
4 first identifier
0 second identifier
0 third identifier
FULL option

3-332 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

DPROC id: 4
DPROC type: PRP
Hardware Information:
PCI Vendor Id: 1146h
PCI Device Id: 6750h
PCI Revision Id: 1h
PCI Type: UNKNOWN
HSC Type: UNKNOWN
Current Cell Mapping:
GSM CELL ID Configured Database GDS All PD
SITE MCC MNC LAC CI LCI 16/32/64k RES/SW 16/32/64k Configured
---- ------------------------------------ -- -- --
Command Rejected: System Busy.

Example 18

In this example, the BSS supports the display of disp_eq CAB with full information for
high-power Horizon II micro with FRU type as HORIZON II MICRO_HIGH_PWR.

disp_eq 4 cab 1 0 full

Where: is:
4 location
cab device/function name
1 first identifier
0 second identifier
FULL option

68P02901W23-T 3-333
Jan 2010
Examples Chapter 3: Device/function related commands

System response

CABINET identifier: 1
Cabinet type[cabinet_type]: HORIZON2MICRO_EXT
Frequency Type[frequency_type]: DCS1800 [4]
Hardware Information:
FRU: HORIZON II MICRO_HIGH_PWR
Kit Number: Not Applicable
Serial Number: Not Applicable
Hardware Version Number: Unavailable
PSU: M14 +27 DC
Kit Number: Not Applicable
Serial Number: Not Applicable
Hardware Version Number: Unavailable
PSU: No Battery
Kit Number: Not Applicable
Serial Number: Not Applicable
Hardware Version Number: Unavailable

Example 19

This example displays RTF when the Extended Range Cell for Data feature is unrestricted
(ercgprsOpt = 1), and also ext_timeslots and ext_pdchs are displayed.

NOTE
ext_pdchs is not displayed if the Extended Range Cell for Data feature is restricted
(ercgprsOpt = 0).

disp_eq 62 rtf 2 0

Where: is:
62 location
rtf device/function name
2 first identifier
0 second identifier

3-334 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Capacity of carrier: FULL

Type of carrier: NON_BCCH
RTF identifier: 2 0
Primary Unique PATH id is: 0
GSM cell to which this carrier is assigned: 001 01 105 6202
Carrier absolute radio freq. channel: 647
Carrier frequency hopping indicators: 255 255 255 255 255 255 255 255
Carrier training sequence codes: 0 0 0 0 0 0 0 0
Number of extended range timeslots allowed[ext_timeslots]: 0
Number of extended range PDCHs allowed[ext_pdchs]: 0
SDCCH load[sd_load]: 4
SDCCH placement priority[sd_priority]: 0
Channel allocation priority[chan_alloc_priority]: 0
Packet Radio Capability[pkt_radio_type]: 32K
Half Rate enabled: 0
allow_8k_trau: Yes

Example 20

{26638}

This example displays the equip information of GBL on PxP when the Gb over IP feature is
unrestricted and the gb_mode parameter is set to static IP mode.

disp_equipment pcu gbl 0

Where: is:
pcu location
gbl device/function name
0 first identifier

System response

Device ID for the GBL: 0

DPROC id where Gb Ethernet located: 5
IP address for Gb Ethernet[ip_address]: 196.182.12.30
Subnet mask for Gb Ethernet[subnet_mask]: 255.255.255.0
UDP port for Gb Ethernet[udp_port]: 8192
Default gateway for Gb Ethernet[gateway]: 196.182.12.254

68P02901W23-T 3-335
Jan 2010
Examples Chapter 3: Device/function related commands

Example 21

{34371G}

This example displays the BTP 0 at site 7 with hardware information.

disp_equipment 7 BTP 0 0 0 full

Where: is:
7 location
BTP device/function name
0 first identifier
0 second identifier
0 third identifier
full option

System response

BTP identifier: 0
BBU attached [bbu_attached]: Yes

Hardware Information:
FRU: BBU-E
Kit Number: SYLNzzzzxx
Serial Number: xxxxxxxxxx
Hardware Version Number: Unavailable

Example 22

{34371G}

This example displays all the associated BTP devices (which are the same BBU-E variants) at a
particular site with hardware information.

disp_eq 7 btp * * full

Where: is:
7 location
BTP device/function name
* first identifier
* second identifier
full option

3-336 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Device FRU Kit Number Serial Number

------ ------ ----------- --------------
BTP 0 0 0 BBU-E SYLNzzzzxx xxxxxxxxxx
BTP 1 0 0 BBU-E SYLNzzzzxx xxxxxxxxxx

Example 23

{34371G}

This example displays a BTP with a BBU attached on the Horizon II macro, Horizon II micro
and Horizon II mini sites.

disp_equipment 23 BTP 0 0 0

Where: is:
23 location
BTP device/function name
0 first identifier
0 second identifier
0 third identifier

System response

BTP identifier: 0
BBU attached[bbu_attached]: Yes

Example 24

{34371G}

This example displays the BBU 0 0 0 on site 23 and there is a BBU port reserved for D4+
link between 2 BBUs.

disp_equipment 23 bbu 0 0 0

Where: is:
23 location
bbu device/function name
0 first identifier
0 second identifier
0 third identifier

68P02901W23-T 3-337
Jan 2010
Examples Chapter 3: Device/function related commands

System response

BBU identifier: 0
BBU port reserved: 0

Example 25

{34371G}

This example displays an (R)CTU4 DRI attached to two BBUs and operating in 4(2+2) density.

disp_equipment 23 DRI 0 0 0

Where: is:
23 location
DRI device/function name
0 first identifier
0 second identifier
0 third identifier

System response

DRI identifier: 0 0
1st device: BBU 0
1st device port: 0
1st CTU4 ingress SFP port: 0
2nd device: BBU 1
2nd device port: 0
2nd CTU4 ingress SFP port: 1
DRI Tx0 density[tx0_dri_density]: 2
DRI Tx1 density[tx1_dri_density]: 2
GSM cell ID where the DRI appears: 0 0 1 0 1 1 1
ARFCN of the lowest frequency[lowest_arfcn]: 10
Antenna select number for this cell[antenna_select]: 1 or 3
Tx port where the DRI appears: 0
The diversity flag for this DRI[diversity_flag]: 0
The fm cell type is[fm_cell_type]: 0
RTF identifier[pref_rtf_id]:
Tx0 Associated DRI identifier: (0 1)
Tx1 Associated DRI identifier: (0 2)(0 3)

3-338 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 26

{35200G}

This example displays a CTU4 DRI operating in 8(4+4) carrier mode.

disp_equipment 23 DRI 0 0 0

Where: is:
23 location
DRI device/function name
0 first identifier
0 second identifier
0 third identifier

System response

DRI identifier: 0 0
Cabinet identifier: 0
Slot number[slot_num]: 2
1st device: BBU 0
1st device port: 0
1st CTU4 ingress SFP port: 0
DRI Tx0 density[tx0_dri_density]: 4
DRI Tx1 density[tx1_dri_density]: 4
GSM cell ID where the DRI appears: 0 0 1 0 1 1 1
ARFCN of the lowest frequency[lowest_arfcn]: 10
Antenna select number for this cell[antenna_select]: 1 or 3
Tx port where the DRI appears: 0
The diversity flag for this DRI[diversity_flag]: 0
The fm cell type is[fm_cell_type]: 0
RTF identifier[pref_rtf_id]:
Tx0 Associated DRI identifier: (0 1)(0 2)(0 3)
Tx1 Associated DRI identifier: (0 4)(0 5)(0 6)(0 7)

68P02901W23-T 3-339
Jan 2010
References Chapter 3: Device/function related commands

Example 27

{36039G}

This example displays the equipment attribute of mms 8 1.

disp_eq 0 mms 8 1

Where: is:
0 location
mms device/function name
8 first identifier
1 second identifier

System response

MSI identifier: 8
MMS identifier: 1
The N-bit value for this device is[nbit]: 0
The BER OOS monitor period for this device is[ber_oos_mon_period]: 8
The BER restoral monitor period for this device is[ber_restore_mon_period]: 600
The Priority rating is[mms_priority]: 0
The Lock Duration for this device (in seconds) is[phase_lock_duration]: 0
The transport bearing of the mms[terr_or_sate]: 0

References

Related information

The hardware requirements and revision levels are given in Release Notes specific to each
software release.

Related commands

equip on page 3-445 modify_value on page 3-507

3-340 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_exp_config

disp_exp_config

Description

The disp_exp_config command displays the CM database configuration of the TDM highway
expansion at the specified site (either BSC or BTS).

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_exp_config <location>

Input parameters

location

Specifies the location of the site. Values are:

0 or bsc BSC
1 - 140 BTS

Example

The following example displays the TDM highway configuration of the BSC:

disp_exp_config 0

Where: is:
0 the location

68P02901W23-T 3-341
Jan 2010
Example Chapter 3: Device/function related commands

System response

Highway 0 (CAGE 0)

-----------------

Connected to highway 1 by EXP 0 (U21 U9)

Connected to highway 2 by EXP 1 (U22 U8)

Connected to highway 3 by EXP 2 (U23 U7)

Highway 1 (CAGE 1)

-----------------

Connected to highway 0 by EXP 0 (U21 U9)

Connected to highway 2 by EXP 1 (U22 U8)

Connected to highway 3 by EXP 2 (U23 U7)

Highway 2 (CAGE 2)

-----------------

Connected to highway 0 by EXP 0 (U21 U9)

Connected to highway 1 by EXP 1 (U22 U8)

Connected to highway 3 by EXP 2 (U23 U7)

Highway 3 (CAGE 3)

-----------------

Connected to highway 0 by EXP 0 (U21 U9)

Connected to highway 1 by EXP 1 (U22 U8)

Connected to highway 2 by EXP 2 (U23 U7)

3-342 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_flash

disp_flash

Description

The disp_flash command displays the version information of the current flash EEPROM load.

Use this command to view the software version number, EEPROM creation date, checksum,
and size.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_flash

Input parameters

There are no input parameters associated with this command.

Example

The following example shows the version information of the flash EEPROM:
disp_flash

68P02901W23-T 3-343
Jan 2010
Example Chapter 3: Device/function related commands

System response

Version : 1.5.0.0.8

Date : 01/04/97 23:51

Checksum: 0x3D691A2

Size : 838702 Bytes

Where: is:
Version the version of the software the system is currently
running.
Date the date and time the current Flash EEPROM load
was created.
The date is in date/month/year format.
Checksum the checksum value of the current Flash EEPROM
load.
Size the size of the current EEPROM load, measured in
bytes.

3-344 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_gclk_avgs

disp_gclk_avgs

Description

The disp_gclk_avgs command displays the Long Term Average (LTA) values for a specific GCLK.

The system reads the clock frequency register of each GCLK once every half hour after
synchronization if the GCLK is phase locked. A rolling average for each GCLK is calculated of up
to 48 clock frequency register readings. This average is the LTA.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.
This command is not allowed for M-Cell sites.

Format

Syntax

disp_gclk_avgs <location> <gclk_id>

Input parameters

location

Specifies the location of the GCLK. Values are:

0 or bsc BSC
1 - 140 BTS

gclk_id

Identifier for GCLK. Values are 0 or 1.

68P02901W23-T 3-345
Jan 2010
Example Chapter 3: Device/function related commands

Example

In this example, the LTA values for GCLK 1 at BSC 0 are displayed:

disp_gclk_avgs 0 1

Where: is:
0 location
1 gclk ID

System response

The GCLK 1 0 0 Frequency Register values at Site 0 are:

80 80 80 80 8F 8F

Long Term Average = 80

Since the system reads the frequency every 30 minutes, these six samples represent 3 hours.
The first value in the display is the oldest. 80 is the value of a GCLK calibrated to 16.384 MHz.

References

Related information

An alarm is generated if 25% or more of the stored clock frequency readings differ from the
calculated LTA by more than the value that is defined by the lta_alarm_range parameter.

Related command

clear_gclk_avgs on page 3-193.

3-346 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_gclk_cal

disp_gclk_cal

Description

The disp_gclk_cal command displays the contents of the clock frequency register when
the GCLK is in the phase-lock mode. The clock frequency register gives an indication of the
calibration status of the GCLK.

When the command is entered the system displays a value in hexadecimal figures. A perfectly
calibrated clock displays a reading of 80. Any value more than or less than 80 indicates the
degree the GCLK calibration has drifted. As the GCLK ages the value shown in the clock
frequency register drifts towards the upper or lower-level GCLK calibration limits. If the upper
or lower calibration thresholds are met or exceeded, the system generates a recalibration alarm.

Using the clock frequency register value can give an estimate of how far the GCLK has drifted
from its original calibration and how long it is until the GCLK requires recalibration. Since each
GCLK has different aging characteristics, this estimate is not exact.
The upper level of all GCLKs is E9 (hexadecimal).

The lower level is 38 (hex) for revisions 0 through 8.

The lower level is 1a (hex) for revision 9.

Use the disp_hardware_version command to view the revision number.

This command also reports if the clock is not in phase lock.

Security level 1
Supported by OMC GUI-R No
Command type A (no operator actions)
Prerequisites This command is not allowed while in the SYSGEN ON
mode.
This command is not allowed for M-Cell sites.

Format

Syntax

disp_gclk_cal <location> <gclk_id>

68P02901W23-T 3-347
Jan 2010
Examples Chapter 3: Device/function related commands

Input parameters

location

Specifies the location of the GCLK:

0 or bsc BSC
1 - 140 BTS

gclk_id

Specifies the identity of the GCLK. Values are 0 or 1.

Examples

Example 1

In this example, GCLK 0 at BSC 0 is not in phase lock mode:

disp_gclk_cal 0 0

Where: is:
0 location
0 gclk_id

System response

GCLK 0 0 0 not in phase lock

Example 2

In this example, GCLK 0 at BSC 0 is in phase lock mode:

disp_gclk_cal 0 0

Where: is:
0 location
0 gclk_id

System response

GCLK 0 Clock frequency register value = 99

3-348 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related information

The system reads the clock frequency register of each GCLK once every half hour after
synchronization after the GCLK has phase_locked. A rolling average for each GCLK is calculated
of up to 48 clock frequency register readings. This average is the Long Term Average (LTA).

An alarm generates if 25% or more of the stored clock frequency readings differ from the
calculated LTA by more than the value that is defined by the lta_alarm_range parameter.

Related commands

clear_gclk_avgs on page disp_gclk_avgs on page 3-345

3-193

68P02901W23-T 3-349
Jan 2010
disp_gsm_cells Chapter 3: Device/function related commands

disp_gsm_cells

Description

The disp_gsm_cells command displays the GSM cells associated with a specific site (BTS or
BSC). Both primary and secondary frequencies are displayed for Dual Band Cells.

Primary and secondary frequency types are displayed for dual band cells.

Security level 1
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_gsm_cells <location>

Input parameter

location

Specifies the site for which associated GSM cells are to be displayed:

0 or bsc BSC
1 - 140 BTS

Examples

Example 1

In this example, no GSM cells are associated with the BSC:

disp_gsm_cells 0

Where: is:
0 location

3-350 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

There are no associated GSM cells

Example 2

In this example, the GSM cells associated with a BTS are displayed:

disp_gsm_cells 11

Where: is:
11 location

System response

Associated GSM cells:

GSM CELL ID

Freq

MCC MNC LAC CI LCI Type Cell Name

--- --- --------------- -------------- --- ----- ----------------

543 21 61713 (0xF111h) 4368 (0x1110h) 0 EGSM london-south

RAC: 8 (0x8h) BVCI: N/A

543 21 61713 (0xF111h) 8736 (0x2220h) 1 EGSM london-north

RAC: 96 (0x60h) BVCI: N/A

543 21 61713 (0xF111h) 13114 (0x222Ah) 2 EGSM bexley-west

RAC: N/A BVCI: N/A

Number of Sectors: 3

68P02901W23-T 3-351
Jan 2010
References Chapter 3: Device/function related commands

References

Related commands

add_cell on page 3-22 copy_cell on page 3-199 del_cell on page 3-212

disp_cell on page 3-261

3-352 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_hdlc

disp_hdlc

Description

The disp_hdlc command displays the HDLC channel assignment types of an in-service GPROC
device or function.

This command permits retrieval of:

Device, function, and CPU values.

The channel configuration and status for every HDLC channel on a GPROC device.

The total number of LAPD devices (RSLs or XBLs) equipped on a GPROC device.

An indication whether the current HDLC layout matches the current database settings.

Channels allocated to GSLs when the GPRS feature is unrestricted at the site.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites The disp_hdlc command cannot be used for CSPF GPROCs
or M-Cell sites.

Format

Syntax

disp_hdlc <location> <device/function name> <dev_func_id_1>

<dev_func_id_2><dev_func_id_3>

Input parameters

location

Specifies the equipment location:

0 or bsc BSC
1 - 140 BTS
all All sites

68P02901W23-T 3-353
Jan 2010
Example Chapter 3: Device/function related commands

dev/func name

Literal that uniquely identifies the device or function

dev/func_id_1

First device or function identifier.

dev_func_id_2

Second device or function identifier.

dev_func_id_3

Third device or function identifier.

Example

Example 1

This example shows how to display the HDLC channel assignments for BSP 0 0 0 at the BSC.

disp_hdlc bsc BSP 0 0 0

Where: is:
bsc location
BSP device / function name
0 device / function ID
0 device / function ID
0 device / function ID

System response

Device: BSP 0 0 0 (CPU ID: 0x0115)

Function: N/A

Number of LAPD Static Links (RSLs/XBLs) allocated to current board: 1

HDLC Channel HDLC Channel Offset

Range 0 1 2 3

------------ ----------------------------------------------------

00-03 Test Free OML 0 0 0 OML Free OML Free

04-07 OML Free XBL 0 0 0 RSL Free RSL Free

08-11 RSL Free RSL Free RSL Free RSL Free

12-15 RSL Free RSL Free RSL Free RSL Free

3-354 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Example 2

This example displays the HDLC channel assignments for LCF 2 0 which has HSP MTL.

disp_hdlc 0 lcf 2

Where: is:
0 location
lcf device/function name
2 device/function ID

System response

Device: GPROC 5 0 0 (CPU ID: 0x0114)

Function: LCF 2 0 0

Number of static LAPD Links (RSLs/XBLs) allocated to current board: N/A

Legend: G/RSL = Free channel configured for a GSL or RSL.

HDLC Channel HDLC Channel Offset

Range 0 1 2 3

------------ ----------------------------------------------------------------

00-03 Test Free MTL 1 0 0 MTL 1 0 0 MTL 1 0 0

04-07 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0
08-11 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0
12-15 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0
16-19 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0
20-23 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0
24-27 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0
28-31 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0

68P02901W23-T 3-355
Jan 2010
disp_hopping Chapter 3: Device/function related commands

disp_hopping

Description

The disp_hopping command displays the hopping information for a cell (identified by
cell_desc), based on the arguments entered with the command.

cell_desc only

If the cell_desc only is entered, the command displays hopping systems for the specific cell.
The following information is displayed:
Frequency hopping indicators (fhi).

Hopping sequence numbers.

Mobile allocations.

cell_desc and fhi

If the fhi is entered along with the cell_desc, a more detailed output of the particular hopping
systems is provided. The following information is displayed:
Carriers that are using the specified hopping system.

Timeslots that are using the specified hopping system.

cell_desc and active string

If the string active is entered together with the cell_desc, all of the currently active hopping
systems for the cell are displayed. The following information is displayed:
Active hopping systems on a carrier and timeslot basis.

Frequency hopping indicators (FHIs).

Hopping sequence numbers (HSNs) for each FHI.

Mobile allocations.

3-356 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Security level 1
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites This command is not allowed while in SYSGEN ON mode
when the active option is used.
Operator actions Place the system in the SYSGEN OFF mode if the active
option is used before entering this command.

Format

Syntax

disp_hopping <site> [active]

disp_hopping <cell_desc> [<fhi> | active]

Input parameters

site

Specifies the location:

0 or bsc BSC
1 - 140 BTS

The system rejects the disp_hopping command at a BTS if the specified cell or site is not local.

cell_desc

Identifies the GSM cell ID of the cell for which the hopping information is to be displayed,
preceded by cell_number=.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command is entered in place of the
cell_number. When the cell name is entered, it must be placed inside double quotation marks
and be preceded by cell_name=.

68P02901W23-T 3-357
Jan 2010
Examples Chapter 3: Device/function related commands

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

fhi

Frequency hopping indicator.

active

The active option displays the currently active hopping systems.

Examples

Example 1

In this example, only the GSM cell ID in seven parameter format is entered and the related
hopping information for the cell is displayed.

disp_hopping cell_number=5 4 3 2 1 61986 34944

Where: is:
5 4 3 2 1 61986 34944 cell_desc

The example below shows the same cell number in four parameter format:

disp_hopping cell_number=543 21 61986 34944

Where: is:
543 21 61986 34944 cell_desc

System response

GSM CELL: 543 21 61986 (f222h) 34944 (8880h)

Baseband (BBH) Hopping

FHI: 0 HSN = 0 MA = 12 30 45

FHI: 1 HSN = 7 MA = 31 37 50

FHI: 2 HSN = 9 MA = 31 32 33 34 45 46

FHI: 3 HSN = 12 MA = 33 76 91

3-358 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 2

In this example, the fhi is entered together with the GSM cell ID. The output contains the
carriers using the hopping system number in addition to all of the timeslots for each carrier.

disp_hopping cell_number=5 4 3 2 1 61986 34944 1

Where: is:
5 4 3 2 1 61986 34944 cell_desc
1 fhi

System response

GSM CELL: 543 21 61986 (f222h) 34944 (8880h)

Carrier arfcn: 33 Timeslots: 0 1

Carrier arfcn: 76 Timeslots: 1 2 3 5 7

Carrier arfcn: 91 Timeslots: 0 1 2 3 4 5 6 7

Example 3

In this example, the active string is entered together with the GSM cell Id.

disp_hopping cell_number=5 4 3 2 1 61986 34944 active

Where: is:
5 4 3 2 1 61986 34944 cell_desc
active active string

System response

GSM CELL: 543 21 61986 (f222h) 34944 (8880h)

Active Hopping Systems:

Carrier arfcn: 33

Timeslot: 0 FHI: 3 HSN: 0 MA: 33 76 91

Timeslot: 1 FHI: 3 HSN: 0 MA: 33 76 91

Timeslot: 2 FHI: 0xFF HSN: 0 MA: (no MA)

68P02901W23-T 3-359
Jan 2010
References Chapter 3: Device/function related commands

References

Related command

chg_element on page 3-112.

3-360 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_level

disp_level

Description

The disp_level command displays the current security level.

Security level 4
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_level

Input parameters

There are no input parameters associated with this command.

Example

This example displays the output of the disp_level command.

disp_level

System response

Current security level is 1

References

Related commands

chg_level on page 3-160 sysgen_mode on page 3-603

68P02901W23-T 3-361
Jan 2010
disp_link Chapter 3: Device/function related commands

disp_link

Description

The disp_link command displays RXCDR, OML, MTL, and CBL links between two sites. The
sites are the BSC) and either the MSC, the OMC, or the Cell Broadcast Center, when an RXCDR
is being used.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is only available on an RXCDR.

Format

Syntax

disp_link

Input parameters

There are no input parameters associated with this command.

Example

In this example, the RXCDR OML and RXCDR MTL links between the BSC and the MSC are
displayed:

disp_link

3-362 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

System response

The CEPT nailed connections are as follows:-

Incoming mms id: 0 0 Timeslot: 16 Outgoing MMS Id 1 0 Timeslot: 16

incoming mms id: 0 0 Timeslot: 17 Outgoing MMS Id 1 0 Timeslot: 17

incoming mms id: 0 0 Timeslot: 18 Outgoing MMS Id 1 0 Timeslot: 18

incoming mms id: 0 0 Timeslot: 19 Outgoing MMS Id 1 0 Timeslot: 19

incoming mms id: 0 0 Timeslot: 20 Outgoing MMS Id 1 0 Timeslot: 20

incoming mms id: 0 0 Timeslot: 21 Outgoing MMS Id 1 0 Timeslot: 21

incoming mms id: 0 0 Timeslot: 22 Outgoing MMS Id 1 0 Timeslot: 22

incoming mms id: 0 0 Timeslot: 23 Outgoing MMS Id 1 0 Timeslot: 23

incoming mms id: 0 0 Timeslot: 24 Outgoing MMS Id 1 0 Timeslot: 24

incoming mms id: 0 0 Timeslot: 25 Outgoing MMS Id 1 0 Timeslot: 25

Finished displaying all nailed connections

68P02901W23-T 3-363
Jan 2010
disp_link_usage Chapter 3: Device/function related commands

disp_link_usage

Description

The disp_link_usage command displays all PATH devices equipped through a particular
MSI/MMS combination at a site.

The output from this command is system configuration dependent.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites An MSI and an MMS must be equipped at the site_device.

Format

Syntax

disp_link_usage <location> <MSI_identifier> <MMS_identifier>

Input parameters

location

Specifies the location of PATH device:

0 or bsc Indicates that the MSI/MMS combination is at the BSC

0 to 140 Indicates the site number of the BTS, if the MSI/MMS combination is
at a BTS

MSI_identifier

Specifies the MSI identifier to be displayed.

0 to 95 the MSI is at the BSC.

0 to 9 the MSI is at a BTS.

MMS_identifier

Specifies the MMS identifier to be displayed. Values are 0 or 1.

3-364 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Example

This example displays the PATH devices equipped on MSI/MMS combination 1 0 at site 1.

disp_link_usage 1 1 0

Where: is:
1 location
1 MSI_identifier
0 MMS_identifier

System response

Start of Report: End of Report

SITE ID : 1

MSI ID : 1

MMS ID : 0

PATH 1 0 0

PATH 2 0 0

PATH 3 0 0

PATH 4 0 0

PATH 5 0 0

PATH 6 0 0

PATH 7 0 0

PATH 8 0 0

PATH 9 0 0

68P02901W23-T 3-365
Jan 2010
disp_mms_ts_usage Chapter 3: Device/function related commands

disp_mms_ts_usage

Description

The disp_mms_ts_usage command displays the timeslot usage on any MMS link. The output
gives the status of each timeslot in the form of:
Unavailable for use (UNAVAILABLE)

Unallocated (UNUSED)

Allocated to RSL (RSL)

Allocated to RTF (RTF)

Allocated to GBL (GBL)

Allocated to GSL (GSL)

Allocated to GDS (GPRS_DATA)

Allocated to XBL (XBL)

Allocated to OML (OML)

Allocated to MTL (MTL)

Allocated to terrestrial circuit (CIC)

Allocated to CBL (CBL)

Allocated to RXCDR link (RXCDR_LINK)

Reserved (RESERVED)

Nailed (NAILED)

Nailed on a path (NAILED PATH Timeslot Usage)

It also displays the timeslots that are reserved for dynamic allocation.

NOTE
16K_DYN_RSL always falls under a 16 K RSL timeslot as the first group. It indicates
that 3 extra timeslots are reserved for dynamic allocation.

3-366 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

The display includes the device or function identifiers and the site where the device or function
is equipped.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites To display timeslot usage at a PCU, the GPRS feature must
be unrestricted.

Format

Syntax

disp_mms_ts_usage <location> <mms_id1> <mms_id2>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

mms_id1

Specifies the 1st digit of the MMS identifier, accordingly:

0 to 5:

0 to 1 is valid for MMS range for MCell-2.

0 to 3 is valid for MMS range for MCell-6.

0 is valid for MMS for MCell micro.

mms_id2

Specifies the 2nd digit of the MMS identifier.

The header in the display depends on where the MMS is being viewed.
If the MMS is viewed from a BSC and RXCDR, the header looks like this:

TS Port Size Usage Device ID Type Site CIC State RTF Site RTF TS

68P02901W23-T 3-367
Jan 2010
Examples Chapter 3: Device/function related commands

If the MMS is viewed from a BTS, the header looks like this:

TS Group Usage Device ID Type Site TS

If the MMS is for an HDSL link, only the top line of the display changes slightly to look
like this:

Site: 3 HDSL (32 timeslot) MMS: 0 0

The remainder of the display is the same as shown in the examples that follow.

NOTE
Using this command with the Integrated MCell HDSL feature enabled,
disp_mms_ts_usage indicates whether the MMS supports a 16 or 32 kbit/s
timeslot HDSL link.

Examples

Example 1

This example displays timeslot usage on a span at site 0 (BSC), MMS 1 0.

disp_mms_ts_usage 0 1 0

Where: is:
0 location
1 1st digit of MMS identifier
0 2nd digit of MMS identifier

System Response

Start of Report:

Site: 0

MMS: 1 0

General Timeslot Usage:

TS Port Size Usage Device ID Type Site CIC State RTF Site RTF TS

3-368 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

0 UNAVAILABLE

1 0-1 Ater* 1 IDLE

2-3 Ater* 2 IDLE

4-5 Ater* 3 IDLE

6-7 Ater* 4 IDLE

2 0-1 Ater* 5 IDLE

2-3 Ater* 6 IDLE

4-5 Ater* 7 IDLE

6-7 Ater* 8 IDLE

3 0-1 Ater 9 IDLE

2-3 Ater 10 IDLE

4-5 Ater IDLE

6-7 Ater IDLE

4 64 K_XBL 128 0 0 64 K 0

5 0-7 Ater IDLE

6 0-1 Ater IDLE

2-3 Ater IDLE

4-5 Ater IDLE

6-7 Ater IDLE

7 0-7 Ater IDLE

8 0-7 Ater IDLE

9 0-7 Ater IDLE

68P02901W23-T 3-369
Jan 2010
Examples Chapter 3: Device/function related commands

10 0-7 Ater IDLE

11 0-7 Ater IDLE

12 0-7 Ater IDLE

13 0-7 Ater IDLE

14 0-7 Ater IDLE

15 0-7 Ater IDLE

16 0-7 Ater IDLE

17 0-7 Ater IDLE

19 0-7 Ater IDLE

20 0-7 Ater IDLE

21 0-7 Ater IDLE

22 0-7 Ater IDLE

23 0-7 Ater IDLE

24 0-7 Ater IDLE

25 0-7 Ater IDLE

26 0-7 Ater IDLE

27 0-7 Ater IDLE

28 0-7 Ater IDLE

29 0-7 Ater IDLE

30 0-7 Ater IDLE

31 0-7 Ater IDLE

Ater*: Timeslot is an Ater but has CIC(s) equipped on it.

3-370 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

End of Report.

Example 2

This example displays the output on an RXCDR MMS showing the status of Ater channels, the
Ater channel status, and CICs assigned to the Ater channels.

disp_mms_ts_usage 0 18 0

Where: is:
0 location
18 1st digit of MMS identifier
0 2nd digit of MMS identifier

System response

Start of Report:

Site: 0 MMS: 18 0

General Timeslot Usage:

A S S O C I A T E D

TS Port Usage Device ID Type BSS State CIC MMS TS Port

Size Size

0 UNAVAILABLE

1 0-1 Ater UNKNOWN

2-3 Ater* UNKNOWN 63 4 0 31

4-5 Ater* UNKNOWN 62 4 0 30

6-7 Ater UNKNOWN

2 64 K_XBL 2 1 0 64 K 0

3 0-1 Ater* UNKNOWN 36 4 0 4

2-3 Ater* UNKNOWN 35 4 0 3

68P02901W23-T 3-371
Jan 2010
Examples Chapter 3: Device/function related commands

4-5 Ater* UNKNOWN 34 4 0 2

6-7 Ater* UNKNOWN 33 4 0 1

4 0-1 Ater* UNKNOWN 40 4 0 8

2-3 Ater* UNKNOWN 39 4 0 7

Ater*: Timeslot is an Ater but has CIC(s) equipped on it.

End of Report.

Example 3

The following example displays the timeslot utilization on MMS 0 0 at the BSC, with a 16 kbit/s
XBL equipped on timeslot 8, group 3 and a 64 kbit/s XBL equipped on timeslot 9.
disp_mms_ts_usage 0 0 0

Where: is:
0 location
0 1st digit of MMS identifier
0 2nd digit of MMS identifier

System response:

Site: 0

MMS: 0 0

General Timeslot Usage:

TS Usage Device ID Type Site CIC Group CIC State TS Group RTF Site RTF TS

TS Usage Device ID Type Site CIC Group CIC State TS Group RTF Site RTF TS

0 UNAVAILABLE

1 CIC 60 0 IDLE

CIC 61 1 IDLE

CIC 62 2 IDLE

3-372 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

CIC 63 3 IDLE

2 CIC 64 0 IDLE

CIC 65 1 IDLE

CIC 66 2 IDLE

CIC 67 3 IDLE

3 CIC 68 0 IDLE

4 NAILED 0 1 0 11

5 UNUSED

6 UNUSED

7 RESERVED

8 CIC 64 0 IDLE

CIC 65 1 IDLE

CIC 66 2 IDLE

XBL 1 0 0 16 0 3

9 XBL 2 0 0 64 0

10 UNUSED

11 UNUSED

12 UNUSED

13 UNUSED

14 UNUSED

15 UNUSED

16 MTL 3 0 0 0

68P02901W23-T 3-373
Jan 2010
Examples Chapter 3: Device/function related commands

17 NAILED 1 0 0 17

18 UNUSED

19 UNUSED

20 UNUSED

21 UNUSED

22 UNUSED

23 UNUSED

24 UNUSED

25 UNUSED

26 UNUSED

27 UNUSED

28 UNUSED

29 UNUSED

30 UNUSED

31 UNUSED

Example 4

This example displays the timeslot usage for an E1 link supporting a GBL. The link runs from a
PICP MMS in PCU 0 cabinet to the SGSN.

disp_mms_ts_usage pcu_0 6 0

Where: is:
pcu_0 location
6 1st digit of MMS identifier
0 2nd digit of MMS identifier

3-374 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Start of Report:

Site: PCU_0

MMS: 6 0

General Timeslot Usage:

TS Usage Device ID Site

0 UNAVAILABLE

1 UNUSED

2 GBL 0 0 0 PCU_0

3 GBL 0 0 0 PCU_0

4 GBL 0 0 0 PCU_0

5 GBL 0 0 0 PCU_0

6 GBL 0 0 0 PCU_0

7 GBL 0 0 0 PCU_0

8 GBL 0 0 0 PCU_0

9 GBL 0 0 0 PCU_0

10 GBL 0 0 0 PCU_0

11 GBL 0 0 0 PCU_0

12 UNUSED

13 UNUSED

14 UNUSED

68P02901W23-T 3-375
Jan 2010
Examples Chapter 3: Device/function related commands

15 UNUSED

16 UNUSED

17 UNUSED

18 UNUSED

19 UNUSED

20 UNUSED

21 UNUSED

22 UNUSED

23 UNUSED

24 UNUSED

25 UNUSED

26 UNUSED

27 UNUSED

28 UNUSED

29 UNUSED

30 UNUSED

31 UNUSED

End of Report.

3-376 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 5

This example displays the timeslot usage on MMS which includes the HSP MTL.

disp_mms_ts_usage 0 8 0

Where: is:
0 location
8 1st digit of MMS identifier
0 2nd digit of MMS identifier

System response

Start of Report:

Site: 0 MMS: 8 0

General Timeslot Usage:

TS Port Usage Device ID Type

Size Site CIC State

RTF Site RTF TS

0 UNAVAILABLE
1 MTL 0 0 0 0
2 MTL 0 0 0 0
3 MTL 0 0 0 0
4 MTL 0 0 0 0
5 MTL 0 0 0 0
6 MTL 0 0 0 0
7 MTL 0 0 0 0
8 MTL 0 0 0 0
9 MTL 0 0 0 0
10 MTL 0 0 0 0
11 MTL 0 0 0 0
12 MTL 0 0 0 0
13 MTL 0 0 0 0

68P02901W23-T 3-377
Jan 2010
References Chapter 3: Device/function related commands

14 MTL 0 0 0 0
15 MTL 0 0 0 0
16 MTL 0 0 0 0
17 MTL 0 0 0 0
18 MTL 0 0 0 0
19 MTL 0 0 0 0
20 MTL 0 0 0 0
21 MTL 0 0 0 0
22 MTL 0 0 0 0
23 MTL 0 0 0 0
24 MTL 0 0 0 0
25 MTL 0 0 0 0
26 MTL 0 0 0 0
27 MTL 0 0 0 0
28 MTL 0 0 0 0
29 MTL 0 0 0 0
30 MTL 0 0 0 0
31 MTL 0 0 0 0

End of Report.

References

Related information

The timeslots states display as UNKNOWN when running in sysgen mode.

Related command

chg_ts_usage on page 3-181.

3-378 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_neighbor

disp_neighbor

Description

The disp_neighbor command displays information of a specific neighbor cell or all neighbor
cells. It also displays additional information for UTRAN and Blind Search neighbor cells.

A neighbor cell can be internal or external. An internal neighbor cell is inside the BSS in which
the source cell is located. An external neighbor cell is outside of the BSS in which the source
cell is located.

The cell_name created using the cell_name command is used to specify the source cell in place
of the src_gsm_cell_id. A cell_name is also used to specify an internal neighbor cell in place of
the neighbor_cell_id. A cell_name cannot be used to specify an external neighbor cell.

When the all option is used, the cell_name for each of the internal neighbor cells is
displayed immediately after the neighbor_cell_id. If a cell_name has not been assigned
to a neighbor_cell_id, No Name Defined is presented in the Neighbor cell name field. The
cell_name for an external neighbor cell is not displayed. If a neighbor cell is an external cell,
N/A. is presented in the Neighbor cell name field.

If the Inter_RAT (Radio Access Technology) Handover and/or the Enhanced 2G/3G Handover
features are unrestricted, this command supports the UTRAN cell identity format.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites For handovers to UTRAN cells, the Inter-RAT handover
feature and/or the Enhanced 2G/3G Handover feature must
be unrestricted.

Format

Syntax

disp_neighbor <src_cell_desc> [<neighbor_cell_desc>|all]

disp_neighbor <src_cell_desc> [TEST <test neighbor_cell_desc>]

68P02901W23-T 3-379
Jan 2010
Examples Chapter 3: Device/function related commands

Input parameters

src_cell_desc

GSM cell ID of the neighbor list owner cell to be displayed.

GSM or UTRAN Cell ID of the neighbor list owner cell to be displayed.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command is entered in place of the
cell_number. When the cell name is entered, it must be placed inside double quotation marks.

neighbor_cell_desc

GSM cell ID of a neighbor cell.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command is entered in place of the
cell_number. When the cell name is entered, it must be placed inside double quotation marks.

test neighbor_cell_desc

A test cell can be created to be used for testing. This argument is entered using the string
TEST, a space, and a test cell number (1 to 64). An asterisk character (*) is used in place of a
test cell number to indicate all test neighbors.

Examples

The examples below are possible displays. If the pbgt_alg_type for a cell is any number
between 3 and 7 or the adj_chan_intf_test for a cell equals yes or 1, the system presents
additional prompts. Refer to the description of the add_neighbor command for the prompted
power budget parameter values.

3-380 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 1

In this example, a cell has no neighbor cells. This example uses the seven parameter format
for the cell number.

disp_neighbor 5 4 3 2 1 61986 34944 all

Where: is:
5 4 3 2 1 61986 34944 src_cell_desc
all all neighbor cells

The example below shows the same cell number in the four parameter format:

disp_neighbor 543 21 61986 34944 all

Where: is:
543 21 61986 34944 src_cell_desc
all all neighbor cells

System response

There are no associated neighbor cells

Example 2

In this example, the information describing a neighbor cell is displayed.

disp_neighbor 0 0 1 0 1 1 4 0 0 1 0 1 1 1

Where: is:
0010114 src_cell_desc
0010111 neighbor_cell_desc

System response

Neighbor cell id: 00101 1 (0001h) 1 (0001h)

Neighbor cell name: N/A
Neighbor cell frequency type: PGSM
Placement: External
Synchronization enabled: N/A
Frequency in the ba_sacch list: 1(yes)
Frequency in the ba_bcch list: 1(yes)

68P02901W23-T 3-381
Jan 2010
Examples Chapter 3: Device/function related commands

BCCH frequency number: 60

Base station identity code: 16
MS transmit power maximum: 37
Neighbor receive level minimum: 15
Neighbor handover margin: 8
Power budget surrounding cell hreqave: 8
Receive quality handover margin: -63
Receive level handover margin: -63
Neighbor type 5 handover margin: 63
Neighbor adaptive handover pbgt trigger: 40
Adjacent channel interference test enabled: 0 (no)
Power budget algorithm type: 1
Neighbor congestion handover margin: 8
Range of the neighbor cell: Normal
End of report

Example 3

In this example, the information describing all of the neighbor cells is displayed. The cell name
london-north is used in place of the src_cell_desc.

disp_neighbor london-north all

Where: is:
london-north cell_name
all all internal neighbor cells

System response

Neighbor cell id: 54 3 2 1 633 347

Neighbor cell name: london-south
Placement: Internal
Synchronization enabled: 1
Frequency in the ba_sacch list: 1
Frequency in the ba_bcch list: 0
BCCH frequency number: 60
Base station identity code (bsic): 16
MS transmit power maximum: 37
Neighbor receive level minimum: 15
Neighbor handover margin: 8
Power budget surrounding cell hreqave: 9
Adjacent channel interference test enabled: 0 (no)

3-382 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Power budget algorithm type: 7

Adjacent channel intf detection ho margin: -5
Neighbor congestion handover margin: -8
Neighbor cell id: 54 3 2 1 633 348
Neighbor cell name: No Name Defined
Placement: Internal
Synchronization enabled: 1
Frequency in the ba_sacch list: 1
Frequency in the ba_bcch list: 0
BCCH frequency number: 60
Base station identity code (bsic): 16
MS transmit power maximum: 37
Neighbor receive level minimum: 15
Neighbor handover margin: 8
Power budget surrounding cell hreqave: 9
Adjacent channel interference test enabled: 0 (no)
Power budget algorithm type: 7
Adjacent channel intf detection ho margin: -5
Neighbor congestion handover margin: -8
Neighbor cell id: 5 4 3 2 1 633 349
Neighbor cell name: N/A
Placement: External
Synchronization enabled: N/A
Frequency in the ba_sacch list: 1
Frequency in the ba_bcch list: 0
BCCH frequency number: 100
Base station identity code (bsic): 50
MS transmit power maximum: 37
Neighbor receive level minimum: 15
Neighbor handover margin: 8
Power budget surrounding cell hreqave: 9
Adjacent channel interference test enabled: 0 (no)
Power budget algorithm type: 7
Adjacent channel intf detection ho margin: -5

68P02901W23-T 3-383
Jan 2010
Examples Chapter 3: Device/function related commands

Example 4

This example displays the information for all test cells.

disp_neighbor 5 4 3 2 1 619 394 TEST *

Where: is:
5 4 3 2 1 619 394 src_cell_desc
TEST * all test cells

System response

MCC MNC LAC CI LOC SYNC SACCH BCCH FREQ BSIC

-------------------------------- ------- ----- ---- ---- ----

TEST 7 N/A N/A NO YES 91 N/A

TEST 12 N/A N/A YES YES 101 N/A
GSM CELL ID BA_ BCCH

Example 5

This example displays the information for an external neighbor cell with the Multiband Inter-Cell
Handover feature enabled.

disp_neighbor 0 0 1 0 1 1 1 0 0 1 0 1 1 2

Where: is:
0010111 src_cell_desc
0010112 neighbor_cell_desc

System response

Neighbor cell id: 00101 1 (0001h) 2 (0002h)

Neighbor cell name: N/A
Neighbor cell frequency type: PGSM
Placement: Internal
Synchronization enabled: 0(no)
Frequency in the ba_sacch list: 1(yes)
Frequency in the ba_bcch list: 1(yes)
BCCH frequency number: 60
Base station identity code: 16

3-384 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

MS transmit power maximum: 37

Neighbor receive level minimum: 15
Neighbor handover margin: 8
Power budget surrounding cell hreqave: 8
Receive quality handover margin: -63
Receive level handover margin: -63
Neighbor type 5 handover margin: 63
Neighbor adaptive handover pbgt trigger: 40
Adjacent channel interference test enabled: 0 (no)
Power budget algorithm type: 1
Neighbor congestion handover margin: 8
Range of the neighbor cell: Normal

Example 6

This example displays the information for all neighbor cells associated with a cell when the
Network Controlled cell reselection feature is enabled.

disp_neighbor 0 0 1 0 1 1 1

Where: is:
0010111 src_cell_desc

System response

Start of neighbor report:

S
A B G
C C P
GSM CELL ID C C R FREQ BCCH
MCC MNC LAC CI LOC SYNC H H S TYPE FREQ BSIC
---------------------------------- --- ---- ------- ------- ---- ----
001 01 1 (0001h) 6 (0006h) INT NO X X X PGSM 75 16
001 01 1 (0001h) 3 (0003h) INT NO X X X PGSM 30 16
001 01 1 (0001h) 33 (0021h) INT NO X X X PGSM 10 16
001 01 1 (0001h) 41 (0029h) INT NO X X X PGSM 90 16
001 01 1 (0001h) 11 (000Bh) EXT N/A X X X EGSM 80 16
001 01 1 (0001h) 90 (005Ah) EXT N/A X X X PGSM 17 16
End of report

68P02901W23-T 3-385
Jan 2010
Examples Chapter 3: Device/function related commands

Example 7

This example displays UTRAN cell 4 9 6 2 3 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4.

disp_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1

Where: is:
0010114 src_cell_desc
496231111 neighbor_cell_desc

System response

Start of neighbor report:

UTRAN cell id: 496 231 1 (0001h) 1 (0001h) 1 (0001h)
UTRAN BCCH Neighbor: Yes
UTRAN SACCH Neighbor: Yes
FDD-ARFCN: 10762
Scrambling code: 200
Diversity enabled: 0 (no)
UMTS measurement margin: 3
Neighbor measurement avg period: 6
End of report

Example 8

This example displays neighbors of GSM cell 0 0 1 0 1 1 4, which has two GSM neighbors, two
UTRAN neighbors and two Blind Search neighbors.

disp_neighbor 0 0 1 0 1 1 4

Where: is:
0010114 src_cell_desc

System response

Start of neighbor report:

S
A B
C C
UTRAN CELL ID C C

3-386 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

MCC MNC LAC RNC id CI H H ARFCN SC DF

--------------------------------------------- ----- ----- --- --
496 231 1 (0001h) 1 (0001h) 1 (0001h) X X 10762 200 1
496 231 1 (0001h) 2 (0001h) 1 (0001h) X X 10762 201 0
Blind Search FDD-ARFCN
----------------------
10765
10786
S
A B G
C C P
GSM CELL ID C C R FREQ BCCH
MCC MNC LAC CI LOC SYNC H H S TYPE FREQ BSIC
------------------------------------ --- ---- ------- ------- ---- ----
001 01 1 (0001h) 106 (006Ah) INT NO X X X PGSM 75 16
001 01 1 (0001h) 103 (0067h) INT NO X X X PGSM 30 16
End of report

Example 9

This example displays TD-SCDMA cell 4 9 6 2 3 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4.

disp_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1

Where: is:
0010114 src_cell_desc
496231111 neighbor_cell_desc

System response

Start of neighbor report:

S
A B
C C
UTRAN CELL ID C C
MCC MNC LAC RNC id CI H H ARFCN Param TSTD SCTD
--------------------------------------------- ----- ----- --- --
496 231 1 (0001h) 1 (0001h) 1 (0001h) X 10110 100 0 0
End of report

68P02901W23-T 3-387
Jan 2010
References Chapter 3: Device/function related commands

References

Related commands

add_cell on page 3-22 add_neighbor on page 3-35 copy_cell on page 3-199

del_cell on page 3-212 disp_cell on page 3-261 disp_gsm_cells on page 3-350

3-388 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_nsvc

disp_nsvc

Description

The disp_nsvc command displays the requested NSVCs and their configurations.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator action)
Prerequisites None (If GPRS is restricted, the display still shows the
headings.)

Format

Syntax

disp_nsvc <NS_VCI> <value>|<pcu_id> <GBL> <value>

Input parameters

NS_VCI

Specifies the NSVCI as defined by value.

pcu_id

Specifies the pcu or pcu_0 at which the GBL is defined.

GBL

Specifies the GBL as defined by value.

value

Varies according to the option chosen.

68P02901W23-T 3-389
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

The following example displays NSVCI 68:

disp_nsvc NS_VCI 68

Where: is:
NS_VCI NSVCI
68 NSVCI ID

System response

Start of Report:
NS-VCI NSEI PCU GBL STATUS DLCI BC BE CIR
------ ---- ---- --- ---------- ----- ---- ---- ----
68 15 0 0 Unblocked 22 0 64 64
68 16 1 0 Unblocked 22 0 64 64
End of Report.

Example 2

The following example displays all the NSVCIs associated with GBL 0 at PCU site 0 during
SYSGEN:

disp_nsvc pcu_0 GBL 0

Where: is:
pcu_0 PCU (second equipped)
GBL GBL
0 GBL 0

3-390 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Start of Report:
Site: PCU_0
NS Access Rate: 64
GBL NS-VCI STATUS DLCI BC BE CIR
--- ------- ---------- ----- ---- ---- ----
0 68 PCU OOS 22 0 64 64
27 PCU OOS 239 0 64 64
102 PCU OOS 91 0 64 64
198 PCU OOS 240 0 64 64
10 PCU OOS 16 0 64 64
23 PCU OOS 200 0 64 64
21 PCU OOS 204 0 64 64
78 PCU OOS 119 0 64 64
69 PCU OOS 213 0 64 64
End of Report.

Example 3

{26638}

The following example displays the information for NSVC 68 when the gb_mode parameter is
set to static IP mode.

disp_nsvc NS_VCI 68

Where: is:
NS_VCI NSVCI
68 NSVCI ID

System response

Start of Report:
NS-VCI NSEI PCU GBL STATUS REMOTE IP UDP PORT SIG-WT DAT-WT
------ ---- ---- --- ---------- ---------- ------- ----- -----
68 68 0 0 Unblocked 200.30.0.1 1099 0 50
End of Report.

68P02901W23-T 3-391
Jan 2010
References Chapter 3: Device/function related commands

References

Related commands

add_nsvc on page 3-47 del_nsvc on page 3-222

3-392 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_options

disp_options

Description

The disp_options command displays the unrestricted and restricted optional features.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_options [all]

Input parameter

all

Displays both the unrestricted and restricted options. If this parameter is not entered, only the
unrestricted options are displayed.

Examples

Example 1

In this example, only the unrestricted options are displayed.

disp_options

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining

68P02901W23-T 3-393
Jan 2010
Examples Chapter 3: Device/function related commands

3 Encryption Multiple Encryption

4 Frequency Hopping Baseband
5 Frequency Hopping Synthesizer
6 Receiver Spatial Diversity
7 Reserved Timeslots
8 SMS Cell Broadcast (Multiple Background Messages)
9 SMS Point to Point
10 Preventative Cyclic Retransmission
11 Microcell
12 Extended GSM 900
13 SMS Cell Broadcast (CBC Support)
14 Add Nail Connections
15 Directed Retry
16 Alternative Congestion Relief
17 Level 3 Password
18 A5_1 Encryption
19 A5_2 Encryption
20 A5_3 Encryption
21 A5_4 Encryption
22 A5_5 Encryption
23 A5_6 Encryption
24 A5_7 Encryption
25 RTF-PATH Fault Containment
26 Sub-Equipped RTF
27 16 Kbps LAPD RSL
28 16 Kbps LAPD XBL
29 Infrastructure sharing Homogeneous Cabinet
30 Infrastructure Sharing Heterogeneous Cabinet
31 MultiBand Inter-Cell Handover
32 Concentric Cells
33 Aggregate Abis
34 Extended Range Cells
35 Downloadable Transcoder Volume Control (Uplink and Downlink)
36 Enhanced Full Rate
37 Fast GCLK Warmup
38 Integrated M-Cell HDSL Interface
39 BTS Concentration
40 General Packet Radio Service
41 Dual Band Cells
42 900/1800 Horizon micro2 / Horizoncompact2
43 Enhanced Circuit Error Rate Monitor
44 Network Controlled Cell Reselection

3-394 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

45 Location Services
47 Coding Scheme 3&4 Enabled
48 Enhanced One Phase Access
49 Enhanced Capacity BSC
50 InterRAT Handover 2G>3G Cell Relocation 3G>2G Dedicated Mode
51 Adaptive Multi-Rate
52 AMR Using Enhanced GDP
53 PBCCH/PCCCH
54 Seamless Cell Reselection
55 AMR Enhanced Capacity
57 TCU-B Support for AMR
58 Prp Capacity
59 Enhanced General Packet Radio Service
60 GSM Half Rate
61 MMSs at Horizonmacro2
62 Quality of Service
63 GPRS Trace
64 Versa Trau
65 Dual Transfer Mode
83 CTU2D Capicity
86 TD-SCDMA inter-working

NOTE
The actual output of this command depends on the delivery of other optional features.

Example 2

In this example, both the unrestricted and restricted options are displayed.

disp_options all

Where: is:
all all options

68P02901W23-T 3-395
Jan 2010
Examples Chapter 3: Device/function related commands

System response

The following optional features have unrestricted use:

1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
3 Encryption Multiple Encryption
4 Frequency Hopping Baseband
5 Frequency Hopping Synthesizer
6 Receiver Spatial Diversity
7 Reserved Timeslots
8 SMS Cell Broadcast (Multiple Background Messages)
9 SMS Point to Point
10 Preventative Cyclic Retransmission
11 Microcell
12 Extended GSM 900
13 SMS Cell Broadcast (CBC Support)
14 Add Nail Connections
15 Directed Retry
16 Alternative Congestion Relief
17 Level 3 Password
18 A5_1 Encryption
19 A5_2 Encryption
20 A5_3 Encryption
21 A5_4 Encryption
22 A5_5 Encryption
23 A5_6 Encryption
24 A5_7 Encryption
25 RTF-PATH Fault Containment
26 Sub-Equipped RTF
27 16 Kbps LAPD RSL
28 16 Kbps LAPD XBL
29 Infrastructure sharing Homogeneous Cabinet
30 Infrastructure Sharing Heterogeneous Cabinet
31 MultiBand Inter-Cell Handover
32 Concentric Cells
33 Aggregate Abis
34 Extended Range Cells
35 Downloadable Transcoder Volume Control (Uplink and Downlink)
36 Enhanced Full Rate
37 Fast GCLK Warmup
38 Integrated M-Cell HDSL Interface
40 General Packet Radio Service

3-396 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

41 Dual Band Cells

42 900/1800 Horizonmicro2 / Horizoncompact2
43 Enhanced Circuit Error Rate Monitor
44 Network Controlled Cell Reselection
45 Location Services
46 ALM for EGSM carriers
47 Coding Scheme 3&4 Enabled
48 Enhanced One Phase Access
49 Enhanced Capacity BSC
50 InterRAT Handover 2G>3G Cell Relocation 3G>2G Dedicated Mode
51 Adaptive Multi-Rate
52 AMR Using Enhanced GDP
54 Seamless Cell Reselection
55 AMR Enhanced Capacity
56 TCU-A Support for AMR
57 TCU-B Support for AMR
58 Prp Capacity
59 Enhanced General Packet Radio Service
60 GSM Half Rate
61 MMSs at Horizonmacro2
62 SDCCH Increase
63 Network Assisted Cell Change
64 Quality Of Service
65 GPRS Trace
66 Fast Call Setup
67 Enhanced 2G/3G Handover and Cell Reselection
68 Enhanced Multi-level Precedence and Pre-emption Service
69 Intelligent Multi-layer Resource Management
70 VersaTRAU
The following optional features have restricted use:
---------------------------------------------------------------------
39 BTS Concentration
72 Reserved option

73 Improved Timeslot Sharing

--------------------------------------------------------------------

68P02901W23-T 3-397
Jan 2010
Examples Chapter 3: Device/function related commands

Example 3

In this example, the operator performs the disp_options command when only the Enhanced
Circuit Error Rate Monitor feature is restricted.

disp_options all

Where: is:
all all options

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
. . .
. . .
59 Enhanced General Packet Radio Service
60 GSM Half Rate
61 MMSs at Horizonmacro2
62 SDCCH Increase
63 Network Assisted Cell Change
64 Quality Of Service
65 GPRS Trace
66 Fast Call Setup
67 Enhanced 2G/3G Handover and Cell Reselection
68 Enhanced Multi-level Precedence and Pre-emption Service
69 Intelligent Multi-layer Resource Management
70 VersaTRAU
73 Improved Timeslot Sharing
74 Restricted
The following optional features have restricted use:
---------------------------------------------------------------------
43 Enhanced Circuit Error Rate Monitor

3-398 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 4

In this example, the operator performs the disp_options command when no features are
restricted.

disp_options all

Where: is:
all options

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
. . .
. . .
39 BTS Concentration
. . .
. . .
43 Enhanced Circuit Error Rate Monitor
. . .
. . .
59 Enhanced General Packet Radio Service
60 GSM Half Rate
61 MMSs at Horizonmacro2
62 SDCCH Increase
63 Network Assisted Cell Change
64 Quality Of Service
65 GPRS Trace
66 Fast Call Setup
67 Enhanced 2G/3G Handover and Cell Reselection
68 Enhanced Multi-level Precedence and Pre-emption Service
69 Intelligent Multi-layer Resource Management
70 VersaTRAU
73 Improved Timeslot Sharing
74 Restricted

68P02901W23-T 3-399
Jan 2010
Examples Chapter 3: Device/function related commands

Example 5

This example displays the status of an extended uplink TBF feature when its status is restricted.

disp_options all

Where: is:
all options

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
. . .
. . .
56 TCU-A support for AMR
57 TCU-B support for AMR
58 Prp Capacity
The following optional features have restricted use:
---------------------------------------------------------------------
46 ALM for EGSM Carriers
60 Extended Uplink TBF

Example 6

This example displays the list of unrestricted features at the BSS. The SW enabler for PA bias
switch on/off on the CTU2D feature is displayed in this list if the feature is enabled.

disp_options

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
.
.
59 Quality Of Service
60 Network Assisted Cell Change
61 SW enabler for PA bias switch on/off on CTU2D

3-400 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 7

This example displays the list of unrestricted features at the BSS.

disp_options

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
.
.
62 Quality Of Service
63 GPRS Trace
64 VersaTrau
65 Dual Transfer Mode
.
.
74 Incell Support

Example 8

This example displays the list of unrestricted features at the BSS.

disp_options all

System response

WARNING: The feature option information object will not be downloaded to NE

for "Set NE Patch Level" on OMC. So the old version before the operation
will be displayed. PCU objects only upgrade and Patch only upgrade do not
require BSC reset, so that any feature option changes will not take effect
and they are not recommended in case of feature option changes upgrade.
UK_Motorola_Swindon_NPI options for BSGSM-1.9.0.0.15-t1 (26/04/07)
The following optional features have unrestricted use:
---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining

68P02901W23-T 3-401
Jan 2010
Examples Chapter 3: Device/function related commands

Example 9

This example verifies if the Extended Range Cell support for GPRS feature is unrestricted
at the BSS.

disp_options

System response

The following optional features are unrestricted:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
.
.
56 TCU-A support for AMR
57 TCU-B support for AMR
58 Prp Capacity
59 Enhanced 2G/3G Handover and Cell Reselection
60 Extended Uplink TBF
61 Extended Range Cell Support for GPRS

NOTE
The actual output of this command depends on the delivery of other new restricted
features.

Example 10

This example displays the status of the Extended Range Cell support for the GPRS feature
when its status is restricted.

disp_options all

Where: is:
all all options

3-402 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
.
.
56 TCU-A support for AMR
57 TCU-B support for AMR
58 Prp Capacity
The following optional features have restricted use:
---------------------------------------------------------------------
46 ALM for EGSM Carriers
60 Extended Uplink TBF
61 Extended Range Cell Support for GPRS

NOTE
The actual output of this command depends on the delivery of other new restricted
features.

Example 11

{26638}

This example displays the list of non-restricted features at the BSS. The Gb over IP feature is
displayed in this list if the flag indicates that the feature is unrestricted.

disp_options

68P02901W23-T 3-403
Jan 2010
Examples Chapter 3: Device/function related commands

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
.
.
62 Quality Of Service
63 GPRS Trace
64 VersaTrau
65 Dual Transfer Mode
.
.
89 Gb over IP

Example 12

{34452}

This example displays the list of unrestricted features at the BSS. The Intelligent Selective
Paging feature is displayed in this list.

disp_options

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
.
.
17 Intelligent Selective Paging
.
.

Example 13

{34371G}

This example displays the (R)CTU4 in 3 carriers mode per Tx port if the flag indicates that
the function is unrestricted.

disp_options

3-404 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
.
.
88 Support (R)CTU4 in 3 carriers per Tx port

Example 14

{35200G}

This example displays the (R)CTU4 in 4 carrier mode per Tx port if the flag indicates that
the function is unrestricted.

disp_options

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
.
.
95 Support (R)CTU4 with up to 4 carriers per Tx port

Example 15

{36039G}

This example displays the list of non-restricted features at the BSS.

disp_options

68P02901W23-T 3-405
Jan 2010
Examples Chapter 3: Device/function related commands

System response

The following optional features have unrestricted use:

---------------------------------------------------------------------
1 A & Um Interface - GSM Phase 2
2 Daisy Chaining
.
.
94 Abis Auto Swap

3-406 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_processor

disp_processor

Description

The disp_processor command displays the status of all processor boards at a specific site
or all sites.

At InCell sites, this command also displays the related devices and functions associated with the
processors. If a GPROC is not detected on the LAN in InCell sites, the Off LAN value displays.

At M-Cell and Horizonmacro sites, this command displays transceivers, CPU numbers, DRI
IDs, and associated RTFs (if any). The Related Device and Related Function columns are not
applicable to M-Cell sites. If a DRI is not detected at the MCU ASIC, the No Sync value displays.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode
or during site initialization.

Format

Syntax

disp_processor <location>

Input parameter

location

Indicates the number of the BTS or the BSC where the processors are located.

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU
all All locations

68P02901W23-T 3-407
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

In this example, the status of all processor boards at all InCell sites displays.

disp_processor all

Where: is:
all all sites

System response

PROCESSOR STATUS INFORMATION FOR LOCATION 0:END OF STATUS REPORT

OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped NE:Not Equipped
Related Related
CPU# Processor Name State Reason Device Function
---- -------------------- ----- ----------------- --------- --------
0115 BSP 0 0 B-U NO REASON N/A N/A
0117 CSFP 0 0 D-U NO CODE N/A N/A
0118 GPROC 2 0 (Off LAN) D-U GPROC Not On LAN N/A N/A
011a GPROC 1 0 (LCF 0) B-U NO REASON SITE 1 0 N/A
PROCESSOR STATUS INFORMATION FOR LOCATION 2:
OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped NE:Not Equipped
Related Related
CPU# Processor Name State Reason Device Function
---- --------------------- ----- ----------------- --------- --------
1015 BTP 0 0 B-U NO REASON DRI 0 1 RTF 0 0
DRI 0 0 RTF 0 1
1019 CSFP 0 0 (Off LAN) D-U NO REASON N/A N/A

Example 2

In this example, the status of all processor boards at an M-Cell site displays.

disp_processor 1

Where: is:
1 an M-Cell site ID.

3-408 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

PROCESSOR STATUS INFORMATION FOR LOCATION 1:

OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped NE: Not Equipped
Related Related
CPU# Processor Name State Reason Device Function
---------------------------------------------------------------------
1015 BTP 0 0 B-U NO REASON N/A N/A
2001 DRI 0 0 (RTF 0 0) B-U COMB Controller N/A N/A
2002 DRI 0 1 (RTF 0 2) B-U NO REASON N/A N/A
2003 DRI 0 2 (RTF 0 3) B-U NO REASON N/A N/A
2004 DRI 0 3 (RTF 0 1) B-U NO REASON N/A N/A
2005 DRI 0 4 E-L NO REASON N/A N/A
2006 DRI 0 5 (No Sync) D-L NO REASON N/A N/A
END OF STATUS REPORT

Example 3

In this example, the status of the GPRS PCU processor boards are displayed.

A single DPROC (PICP) configuration provides support up to 20 TRAU GDS links.

disp_processor pcu_0

Where: is:
pcu_0 the first equipped PCU.

System response

MMI-RAM 0115 -> disp_proc pcu_0

NC: Not Connected
CPU# Processor Name State Reason Related Related
PROCESSOR STATUS INFORMATION FOR LOCATION PCU 0:
OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped NE:Not Equipped
Device Function
---- ------------------ ------ ------------------ -------- --------
1107 PSP 0 0 B-U NO REASON N/A N/A
1109 PSP 1 0 (NC) D-U Bad or Missing Board N/A N/A
1101 DPROC (PICP) 1 0 B-U NO REASON MSI 0 0 N/A
GDS 0 0 N/A
GSL 0 0 N/A

68P02901W23-T 3-409
Jan 2010
Examples Chapter 3: Device/function related commands

GSL 2 0 N/A
GSL 4 0 N/A
GSL 6 0 N/A
GSL 10 0 N/A
GSL 8 0 N/A
MSI 1 0 N/A
GBL 0 0 N/A
(GDS 5 0) N/A
(GDS 10 0) N/A
(GDS 11 0) N/A
(GDS 12 0) N/A
(GDS 14 0) N/A
(GDS 16 0) N/A
1102 DPROC (PRP) 2 0 B-U NO REASON MSI 5 0 N/A
GDS 2 0 N/A
MSI 14 0 N/A
GDS 11 0 N/A
1103 DPROC (PICP) 3 0 B-U NO REASON MSI 4 0 N/A
GBL 2 0 N/A
GBL 3 0 N/A
(GDS 4 0) N/A
(GDS 7 0) N/A
(GDS 3 0) N/A
1104 DPROC (PRP) 4 0 B-U NO REASON MSI 6 0 N/A
GDS 3 0 N/A
MSI 15 0 N/A
GDS 12 0 N/A
1105 DPROC (PRP) 5 0 B-U NO REASON MSI 7 0 N/A
GDS 4 0 N/A
MSI 16 0 N/A
GDS 13 0 N/A
1106 DPROC (PRP) 6 0 B-U NO REASON MSI 8 0 N/A
GDS 5 0 N/A
MSI 17 0 N/A
GDS 14 0 N/A
110b DPROC (PICP) 11 0 B-U NO REASON MSI 2 0 N/A
GDS 1 0 N/A
GSL 1 0 N/A
GSL 3 0 N/A
GSL 5 0 N/A
GSL 7 0 N/A
GSL 9 0 N/A

3-410 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

GSL 11 0 N/A
MSI 3 0 N/A
GBL 1 0 N/A
(GDS 8 0) N/A
(GDS 2 0) N/A
(GDS 6 0) N/A
110c DPROC (PRP) 12 0 B-U NO REASON MSI 9 0 N/A
GDS 6 0 N/A
MSI 18 0 N/A
GDS 15 0 N/A
110d DPROC (PRP) 13 0 B-U NO REASON MSI 10 0 N/A
GDS 7 0 N/A
MSI 19 0 N/A
GDS 16 0 N/A
110e DPROC (PRP) 14 0 B-U NO REASON MSI 11 0 N/A
GDS 8 0 N/A
MSI 20 0 N/A
GDS 17 0 N/A
110f DPROC (PRP) 15 0 B-U NO REASON MSI 12 0 N/A
GDS 9 0 N/A
MSI 21 0 N/A
GDS 18 0 N/A
1110 DPROC (PRP) 16 0 B-U NO REASON MSI 13 0 N/A
GDS 10 0 N/A
MSI 22 0 N/A
GDS 19 0 N/A
END OF STATUS REPORT

Example 4

In this example, the BSC modifies the disp_processor command to support a PXP DPROC.

disp_processor pcu

Where: is:
pcu the equipped PCU.

68P02901W23-T 3-411
Jan 2010
Examples Chapter 3: Device/function related commands

System response

PROCESSOR STATUS INFORMATION FOR LOCATION PCU 0:

OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped NE:Not Equipped
NC: Not Connected
Related Related
CPU# Processor Name State Reason Device Function
---- ---------------------- ----- ------------------------- ----- --------
1107 PSP 0 0 B-U NO REASON N/A N/A
1109 PSP 1 0 (NC) D-U Bad or Missing Board N/A N/A
1101 DPROC (PICP) 1 0 B-U NO REASON MSI 1 0 N/A
GDS 1 0 N/A
GSL 0 1 N/A
Unknown device found
1102 DPROC (PICP) 2 0 B-U NO REASON MSI 2 0 N/A
Unknown device found
1103 DPROC (PXP) 3 0 B-U No GDS in service MSI 3 0 N/A
GBL 0 0 N/A
GDS 3 0 N/A
GSL 0 3 N/A
Unknown device found
1104 DPROC (PRP) 4 0 B-U NO REASON MSI 4 0 N/A
GDS 4 0 N/A
Unknown device found
1105 DPROC (PXP) 5 0 B-U NO REASON MSI 5 0 N/A

NOTE
CA queries pCA. PPROC is displayed only when U-DPROC2 is configured as PXP.
roglin command is used for querying when the board is configured as PXP.

Example 5

{34371G}

This example displays the processor status on site 23, which contains 2 BBU devices.

disp_process 23

Where: is:
23 location.

3-412 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

PROCESSOR STATUS INFORMATION FOR LOCATION 23:

OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L: Locked U: Unlocked E: Equipped NE: Not Equipped
NC: Not Connected
Related Related
CPU# Processor Name State Reason Device Function
---- ---------------------- ----- ------- -------------- ---------- ---------
1015 BTP 0 0 B-U NO REASON BBU 0 0 N/A
1019 BTP 1 0 E-U NO REASON BBU 1 0 N/A
2079 BBU 0 0 B-U NO REASON 0:DRI 0 0 (RTF 0 0) N/A
1:DRI 0 1 (RTF 0 1)
3:DRI 0 2 (RTF 0 2)
4:DRI 0 3 (RTF 0 3)
6:DRI 1 0 (RTF 1 0)
7:DRI 1 1 (RTF 1 1)
8:DRI 1 2 (RTF 1 2)
9:DRI 1 3 (RTF 1 3)
207a BBU 1 0 B-U NO REASON 0:DRI 2 0 (RTF 2 0) N/A
2:DRI 2 1 (RTF 2 1)
3:DRI 2 2 (RTF 2 2)
5:DRI 2 3 (RTF 2 3)
2001 DRI 3 0 (RTF 3 0) B-U NO REASON DRI 3 1 N/A
2001 DRI 3 1 (RTF 3 1) B-U NO REASON DRI 3 0 N/A

END OF STATUS REPORT

68P02901W23-T 3-413
Jan 2010
disp_relay_contact Chapter 3: Device/function related commands

disp_relay_contact

Description

The disp_relay_contact command displays the relay state (open or closed circuit) for an EAS
device when the device is Busy-Unlocked. The relays are in the deactivated state, as defined
during equip EAS, when the EAS is not Busy-Unlocked.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The EAS device must be equipped and the EAS device
parameters established using the equip eas command.
Seeequip on page 3-445.

Format

Syntax

disp_relay_contact <location> <device_id>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS

device_id

Specifies the device ID of the specific PIX card associated with an EAS device.

0 to 7 InCell sites
0 to 15 M-Cell and Horizonmacro sites

3-414 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Example

This example displays the relay contacts for all EAS devices.

disp_relay_contact

System response

Relay 1: Closed

Relay 2: Open
Relay 3: Open
Relay 4: Closed

References

Related command

equip on page 3-445

68P02901W23-T 3-415
Jan 2010
disp_rtf_channel Chapter 3: Device/function related commands

disp_rtf_channel

Description

The disp_rtf_channel command displays the status of all timeslots or a single timeslot on a
carrier. The display output indicates whether the RTF is equipped for GPRS and EGPRS, and if
capable of supporting EGPRS

If either AMR or GSM Half Rate channel mode is enabled at both the BSS level and the Cell
level for a given cell, the BSS user interface displays generic traffic channels as TCH/G in the
output when the disp_rtf_channel command is executed for a half rate RTF in that cell.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.

Format

Syntax

disp_rtf_channel <location> <rtf_id_1> <rtf_id_2> [<timeslot_number>]

Input parameter

location

Specifies the location:

0 or bsc BSC
1 - 140 BTS

rtf_id_1

The first identifier of the RTF. The range of values is 0 to 5.

rtf_id_2

The second identifier of the RTF. The range of values is 0 to 11.

timeslot_number

Specifies the timeslot number. The range of values is 0 to 7.

When an Extended Range timeslot number is displayed, the word Extended is appended to
the timeslot number.

3-416 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Carrier states

The carrier states that can be displayed include:

ACTIVE - the timeslot is active.

IDLE - the timeslot is idle.

INTRANS - the timeslot is in transition:

from active to idle, or

from idle to active, or

from unavailable to active.

OOS - the timeslot is out of service.

Due to EGPRS PDs on double density CTU2 carrier A, the paired timeslots on carrier B is
blanked out and displayed as OOS.

UNAVAILABLE (HOPPING) - the timeslot is unavailable due to hopping reconfiguration.

UNAVAILABLE (IBAND) - the timeslot is unavailable due to a poor interference band

(Iband).

UNAVAILABLE (OPERATOR) - the operator has subequipped an RTF.

UNAVAILABLE (TERRESTRIAL) - the carrier is unavailable due to a problem with a

terrestrial link.

N/A - for a PDTCH, the timeslot is not configured for GPRS.

The GPRS types that can be displayed include:

SWITCHABLE - the GPRS timeslot is switchable.

RESERVED - the GPRS timeslot is reserved.

Examples

Example 1

This example displays the status of RTF 0 2 at Site 1 when both EGPRS and GPRS are restricted.

disp_rtf_channel 1 0 2

Where: is:
1 location
0 rtf_id_1
2 rtf_id_2

68P02901W23-T 3-417
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Start of report for RTF 0 2 at location 1:

TIMESLOT SUB-CHAN STATE

-------------------------------------------------------
0 (TCH/F) 0 ACTIVE
1 (TCH/F) 0 ACTIVE
2 (TCH/F) 0 ACTIVE
3 (TCH/F) 0 ACTIVE
4 (TCH/F) 0 ACTIVE
5 (TCH/F) 0 ACTIVE
6 (TCH/F) 0 ACTIVE
7 (TCH/F) 0 ACTIVE

Example 2

This example displays the status of RTF 0 0 at Site 1 when the RTF is configured for EGPRS and
is assigned to a DRI capable of supporting EGPRS (that is, a single density CTU2).

disp_rtf_channel 1 0 0

Where: is:
1 location
0 rtf_id_1
0 rtf_id_2

System response

Start of report for RTF 0 0 at location 1:

Packet Radio
Capabilities: 64 K
RTF currently capable of supporting EGPRS?: YES
TIMESLOT GPRS TYPE SUB-CHAN STATE
----------------------------------------------------------------
0 (BCCH) N/A 0 ACTIVE
1 (TCH/F) N/A 0 ACTIVE

3-418 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

2 (TCH/F) N/A 0 ACTIVE

3 (64 K PDTCH) Switchable 0 N/A
4 (64 K PDTCH) Reserved 0 N/A
5 (64 K PDTCH) Reserved 0 N/A
6 (64 K PDTCH) Reserved 0 N/A
7 (64 K PDTCH) Reserved 0 N/A

Example 3

This example displays the carrier states of RTF 1 0, timeslot 5 (a generic traffic channel) at site
1 with half_rate_enabled element set to 1 (enabled).

disp_rtf_channel 1 1 0 5

Where: is:
1 location
1 rtf_id_1
0 rtf_id_2
5 timeslot

System response

TIMESLOT SUB-CHAN STATE.

-------------------------------------
5 (TCH/G) 0 IDLE
End of Report

Example 4

This example displays the timeslot status of Carrier B when Carrier A has three EGPRS PDs
on timeslots 5 to 7.

disp_rtf_channel 1 0 2

Where: is:
1 location
0 rtf_id_1
2 rtf_id_2
5 timeslot

68P02901W23-T 3-419
Jan 2010
Examples Chapter 3: Device/function related commands

System Response

Start of report for RTF 0 2 at location 1

Packet Radio Capabilities: None

RTF currently capable of supporting EGPRS? No

TIMESLOT GPRS TYPE SUB-CHAN STATE

0 (TCH/F) N/A 0 ACTIVE

1 (TCH/F) N/A 0 ACTIVE

2 (TCH/F) N/A 0 ACTIVE

3 (TCH/F) N/A 0 ACTIVE

4 (TCH/F) N/A 0 ACTIVE

5 (TCH/F) N/A 0 OOS

6 (TCH/F) N/A 0 OOS

7 (TCH/F) N/A 0 OOS

Example 5

This example displays the carrier status of all the timeslots for an RTF channel with extended
timeslots pair (2,3), configured as extended PDCHs.

disp_rtf_channel 1 0 0

Where: is:
1 location
0 rtf_id_1
0 rtf_id_2

3-420 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Start of report for RTF 0 0 at location 1:

Packet Radio Capabilities: 64k
RTF currently capable of supporting EGPRS?: YES
TIMESLOT GPRS TYPE SUB-CHAN STATE
----------------------------------------------------------------
0 (TCH/F) N/A 0 ACTIVE
1 (Extended)
2 (64k PDTCH) Reserved 0 N/A
3 (Extended)
4 (64k PDTCH) Reserved 0 N/A
5 (64k PDTCH) Reserved 0 N/A
6 (64k PDTCH) Reserved 0 N/A
7 (64k PDTCH) Reserved 0 N/A

68P02901W23-T 3-421
Jan 2010
disp_rtf_path Chapter 3: Device/function related commands

disp_rtf_path

Description

The disp_rtf_path command displays all PATH devices to which the RTF is assigned, including
the status of the RTF on that PATH. The status of the RTF is shown as Connected or Redundant.

The system shows whether a site supports dynamic allocation. The PATH status includes the
designation of SHARED in addition to the CONNECTED and REDUNDANT status. All PATHs
which could be used to carry the RTF to the BSC are displayed. For spoke and daisy chain
configurations, no redundant PATHs exist.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites This command is available only on RTF functions that are
equipped on a remote BTS.

Format

Syntax

disp_rtf_path <location> <rtf_id_1> <rtf_id_2>

Input parameters

location

Specifies the number of the BTS where the RTF is located. The range of values is 0 to 140.

rtf_id_1

Specifies the 1st RTF identifier. The range of values is 0 to 5.

rtf_id_2

Specifies the 2nd RTF identifier. The range of values is 0 to 11.

3-422 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Example

This example displays all the PATH devices assigned to RTF 0 0 at BTS 12.

disp_rtf_path 12 0 0

Where: is:
12 location
0 rtf_id_1
0 rtf_id_2

System response

Start of Report:

SITE ID: 12
1st RTF Identifier: 0
2nd RTF Identifier: 0
PATH 12 0 0 Status: CONNECTED Busy Unlocked
End of Report

References

Related commands

add_rtf_path on page 3-50 chg_rtf_freq on page 3-162 copy_path on page 3-207

del_rtf_path on page 3-224

68P02901W23-T 3-423
Jan 2010
disp_severity Chapter 3: Device/function related commands

disp_severity

Description

Use the disp_severity command to view the current severity level for device alarms and
non-reconfiguration alarms.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_severity <device_name> <alarm_code>

Input parameters

device_name

The name of the device, such as GPROC, that is being modified.

alarm_code

The decimal number or range that identifies the alarm code or codes for the device that is being
modified. The alarm code is defined by all valid numeric values in the range 0 to 254.
Refer to Alarm devices on page 3-20 for the ranges of alarm codes for each device.

Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26)

manual for a list of all alarms and the corresponding alarm codes for each device.

3-424 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Example

This example shows how to display the severity of GPROC alarm code 8.

disp_severity gproc 8

Where: is:
gproc device_name
8 alarm_code

System response

GPROC Alarm code 8 severity: Investigate

68P02901W23-T 3-425
Jan 2010
disp_site Chapter 3: Device/function related commands

disp_site

Description

The disp_site command displays the site, BSC, or BTS, with which the operator is interacting.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_site

Input parameters

There are no input parameters associated with this command.

Example

This example displays the current site.

disp_site

System response

Current site number is 6

References

Related command

equip on page 3-445.

3-426 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_throttle

disp_throttle

Description

The disp_throttle command displays the throttle period for an intermittent alarm. To display
the throttle time period for all intermittent alarms, the command is executed with no input
parameters.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_throttle [<device_name> <alarm_code>]

Input parameters

device_name

Device name that uniquely identifies the device.

alarm_code

Identifies the alarm to be throttled. The range of values for the alarm_code is 0 to 254.

68P02901W23-T 3-427
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

This example displays the throttle period for device DRI, alarm code 66.

disp_throttle dri 66

Where: is:
dri device_name
66 alarm_code

System response

Alarm Alarm Throttle

Source Code Time Alarm Description
------ ----- -------- -----------------------------------
DRI 66 5 Superframe Counter Error

Example 2

This example displays the throttle period for all of the intermittent alarms.

disp_throttle

System response

Alarm Alarm Throttle

Source Code Time Alarm Description
-------- ------ --------- -------------------------------------
MMS 0 15 Synch Loss Daily Threshold Exceeded
MMS 1 1 Synch Loss Hourly Threshold Exceeded
MMS 4 1 Remote Alarm Daily Threshold Exceeded
....
DRI 1 10 Bad Host Message
....

3-428 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related command

chg_throttle on page 3-176.

68P02901W23-T 3-429
Jan 2010
disp_time Chapter 3: Device/function related commands

disp_time

Description

The disp_time command displays the current real time of the system. The format of the real
time is:
Day of the week

Month

Day of the month

Hour

Minutes

Seconds

Year

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_time

Input parameters

There are no input parameters associated with this command.

Example

In this example, the system time is displayed.

disp_time

3-430 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

Fri Nov 12 14:13:48 2002

References

Related commands

chg_time on page 3-178 time_stamp on page 3-611

68P02901W23-T 3-431
Jan 2010
disp_trace_call Chapter 3: Device/function related commands

disp_trace_call

Description

The disp_trace_cell command displays the mode, value, and trace data currently enabled in
the BSS and the destination of the trace report.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed when in SYSGEN ON mode.

Format

Syntax

disp_trace_call [reference_number]

Input parameter

reference_number

A number that identifies a particular trace reference. The number can range from 0 to
4294967295.

Using a reference number is optional. If the reference number is not used, the system displays
all call traces.

Examples

Example 1

The following example displays the Call/GPRS Trace criteria that are currently at the BSS.
disp_trace_call

System response

Start of Trace Report

Trace Reference: 1h

3-432 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Scope: 0 0 1 0 1 1(0001h) 4(0004h)

Trigger Event: combined_all (All Call Trace and GPRS Trace)

Trace Data: Basic, DTAP, Abis

GPRS trace Data: Basic, LLC, BSSGP

Trigger Enabled Time: Not Specified

Data during handover only: No

Mode IMSI=003456789012345

Total calls to be traced: 20

Trace beyond scope: No

Destination of Trace data: OMC

Triggering enabled: No

Trace Reference: 67A67h

Scope: BSS wide

Trigger Event: gprs (GPRS Trace)

GPRS Trace Data: Basic, LLC, BSSGP

Data during handover only: No

Mode TLLI=c0010329h

Trigger Enabled Time: Not Specified

Total calls to be traced: 20

Trace beyond scope: No

Destination of Trace data: OMC

Triggering enabled: No

Total mobiles currently traced

Trace Reference Count

----------------- -----

1h 8

67A67h 5

Total calls currently traced

Trace Reference Count

----------------- -----

1h 3

Automatic Flow Control: Not Halted for this BSS.

Automatic Flow Control: Activated by BSS.

68P02901W23-T 3-433
Jan 2010
Examples Chapter 3: Device/function related commands

Automatic Flow Control: De-activated by OMC.

Example 2

The following is an example of the specified call trace instance (trace reference 067A67h)
currently active in the BSS.

disp_trace_call 067A67h

Where: is:
067A67h reference_number

System response

Start of Trace Report

Trace Reference: 067A67h

Scope: BSS wide

Trigger Event: gprs (GPRS Trace)

GPRS Trace Data: Basic, LLC, BSSGP, PMRs

Interval (x480msec): 20

Data during handover only: No

Mode NthGPRSmobile=5

Trigger Enabled time Not specified

Total calls to be traced: 20

Trace beyond scope: No

Destination of Trace data: OMC

Trigger enabled: No

Total mobiles currently traced

Trace Reference Count

--------------- -----

067A67h 5

Total calls currently being traced

Trace Reference Count

--------------- -----

Automatic Flow Control: Not Halted for this BSS.

Automatic Flow Control: Activated by BSS.

Automatic Flow Control: De-activated by OMC.

3-434 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related commands

trace_call on page 3-613 trace_stop on page 3-627

68P02901W23-T 3-435
Jan 2010
disp_traffic Chapter 3: Device/function related commands

disp_traffic

Description

The disp_traffic command displays all RSL and RTFs equipped to a particular PATH at a
BTS or all GSLs equipped to a GDS at a PCU.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The GPRS feature must be unrestricted to display PCU
data.

Format

Syntax

disp_traffic <location> <unique_PATH_identifier>

Input parameters

location

Specifies the equipment location:

pcu or pcu_0 PCU

1 - 140 BTS

unique_PATH_identifier

Specifies the unique PATH to a particular BTS. The range of values is 0 to 11.

3-436 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

This example displays the RSL devices and RTF functions equipped on unique PATH 3 at site 1.

disp_traffic 1 3

Where: is:
1 location
3 unique_PATH_identifier

System response

Start of Report:

SITE ID: 1
Unique PATH ID: 3
RSL 1 0 0
RTF 0 0 0
RTF 0 1 0
RTF 0 2 0
End of Report

Example 2

This example displays the PCU data.

disp_traffic pcu 0

Where: is:
pcu location
0 unique_PATH_identifier

System response

Start of Report:
SITE ID: PCU
Unique GDS ID: 0
GPRS
End of Report

68P02901W23-T 3-437
Jan 2010
References Chapter 3: Device/function related commands

Example 3

This example displays the data for GDS.

disp_traffic pcu_0 0

Where: is:
pcu_0 location
0 unique_PATH_identifier

System response

SITE ID: PCU 0

Unique GDS ID: 0
GSL 0 0 0
GSL 0 2 0
GSL 0 4 0
GSL 0 6 0
GSL 0 8 0
GSL 0 10 0
GPRS DATA
End of report

References

Related command

add_rtf_path on page 3-50.

3-438 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_transcoding

disp_transcoding

Description

The disp_transcoding command displays which Circuit Identifier Codes (CICs) are using the
transcoding resources of which GDPs and XCDRs.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The enhanced GDP provisioning feature must be
unrestricted.

Format

Syntax

disp_transcoding

Input parameters

There are no parameters for this command.

Example

This example displays the transcoding data.

disp_transcoding

68P02901W23-T 3-439
Jan 2010
Example Chapter 3: Device/function related commands

System response

MSC MMS Transcoding Board CIC IDs

------- ----------------- -------
1 0 1 0 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

4 0 4 0 No CICs associated to this GDP/XCDR

-------
n/a: not applicable
N-E: not equipped

3-440 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_version

disp_version

Description

The disp_version command displays the current software version, patch object version and
patch object level.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.

Format

Syntax

disp_version

Input parameters

There are no input parameters associated with this command.

Example

Example 1

To display the version, revision numbers, patch version, and patch level of the current software
load.

disp_version

68P02901W23-T 3-441
Jan 2010
Example Chapter 3: Device/function related commands

System response

BSP Code Version: 8.0.0.E

BSP Patch Object Version: 5
BSP Patch Level: 3
BSP Database Level Number: 2C3F
CSFP Code Version: -
CSFP Patch Object Version: -
CSFP Database Level Number: -
BSP Code Version: 8.0.0.E
BSP Patch Object Version:
BSP Patch Level:
BSP Database Level Number: 2C3F
CSFP Code Version: -
CSFP Patch Object Version: -
CSFP Database Level Number: -
BSP Code Version: 8.0.0.E
BSP Patch Object Version: 5
BSP Patch Level: 0
BSP Database Level Number: 2C3F
CSFP Code Version: -
CSFP Patch Object Version: -
CSFP Database Level Number: -

3-442 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_x25config

disp_x25config

Description

The disp_x25config command displays the X.25 configuration for all the CBLs or OMLs at a
BSS.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_x25config <link type>

Input parameter

link type

Specifies the type of X.25 link:

oml displays parameters for all OMLs in the BSS.

Must be used out of SYSGEN.
cbl displays parameters for all CBLs in the BSS.

Example

The following example displays the X.25 settings for all BSS OMLs.

disp_x25 oml

Where: is:
oml link type

68P02901W23-T 3-443
Jan 2010
References Chapter 3: Device/function related commands

System response:

X.25 Packet Size: 128

X.25 Window Size: 2

References

Related command

chg_x25config on page 3-186.

3-444 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference equip

equip

Description

The equip command adds devices and functions to the Fault Management portion of the CM
database. Since each device and function has specific parameters, there is a corresponding
set of prompts. Each device and function also has specific restrictions for equipage. Details of
the command prompts and restrictions for equipping the devices and functions are provided
in Chapter 2 Equipping the CM database, which also includes charts showing equipage
hierarchy.

Some devices and functions require the system to be in the SYSGEN ON mode. To enter this
mode, enter the sysgen_mode on command. To exit this mode, use the sysgen_mode off
command.

Some devices require the site to be locked. To lock the site, enter the lock command. To
unlock the site, enter the unlock command.

If a device or function parameter is optional, there is no need to enter data. Press the ENTER key
at the prompt.

The equip command can be exited at any time by entering done in response to any prompt.

NOTE

The equip command can be entered only at the BSC. This command does not
work at a BTS site. Contact the OMC-R for help in setting up a BTS site.
{34371G} Adding an R/CTU4 into a chain of R/CTU4s (rather than adding at
the end of the chain) results in incorrect operation unless the operator sets up
the database from scratch (which means reinitializing the system, including
reconfiguration from scratch through the MMI).

68P02901W23-T 3-445
Jan 2010
Format Chapter 3: Device/function related commands

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites Some devices and functions can be equipped only after
other devices have been equipped.
To equip or modify some devices, the system must be in the
SYSGEN ON mode.
Some devices require the site to be locked.
To equip a device or function with a frequency, it must
be first set as allowable with the freq_types_allowed
command.
The LMTL can be equipped only if the Location Services
support feature is unrestricted and the BSS
can support a BSS-based SMLC.
GPRS devices can be equipped only if the GPRS feature is
unrestricted.
HSP MTL can be equipped only when the increased
network capacity feature is enabled.
Operator actions Refer to the instructions included with each device or
function for specific actions to be taken when using this
command (see Chapter 2 Equipping the CM database).

Format

Syntax

equip <location> <dev/func_name>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

NOTE
A BSC of type 1 or 2 must equip remote sites with an LCF.

dev/func_name

Identifies the device or function being equipped.

3-446 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

The following devices can be equipped with this command:

ABSS AXCDR BSP BSS BTP CAB

CAGE CBL CIC COMB CSFP DHP
DPROC DRI DYNET EAS GBL GCLK
GDS GPROC GSL KSW LMTL MSI
MTL OML OPL PATH PCU PSP
RSL RXCDR SITE XBL

The following functions can be equipped with this command:

LCF OMF RTF

NOTE
The system responds with a series of command prompts for further input which
is dependent on the particular device/function being equipped (see Chapter 2
Equipping the CM database for equipage rules/conditions and system command
prompts).

Examples

Example 1

In this example, a second CAGE is being equipped at the BSC using expansion:

equip bsc cage

Where: is:
bsc location.
cage device being equipped.

System response

Enter the device identification for the cage: 1

Enter the KSW pair that manages the cage: 1
Enter the KSWX connecting cage to KSW for TDM 0:
Enter KSWX connecting cage to KSW for TDM 1:
Enter the cabinet to which the cage belongs: 1
Is an IAS connected?: Y
COMMAND ACCEPTED

68P02901W23-T 3-447
Jan 2010
Examples Chapter 3: Device/function related commands

Example 2

In this example, a path with two links is equipped to site 2. All the prompts that define the
path are included in this example.

equip 0 path

Where: is:
0 location.
path the device being equipped.

System response

Enter the terminating SITE id: 2

Enter the Unique PATH identifier: 0
Enter the BSC MSI identifier: 0 0
Enter the SITE identifier: 1
Enter the upstream MSI identifier: 2 0
Enter the downstream MSI identifier: 2 1
Enter the SITE identifier: 2
Enter the upstream MSI identifier: 2 1
COMMAND ACCEPTED

Example 3

This example equips a 64 K RTF at BTS site 2 with a warning that not enough GDS resources
are available to handle PDTCHs.

equip 2 rtf

Where: is:
2 location

3-448 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Enter capacity of carrier: FULL

Enter type of carrier: NON_BCCH
Enter the 1st and 2nd RTF id: 0 5
Enter primary Unique PATH id: 1
Enter the optional secondary Unique PATH id:
Enter the GSM cell to which this carrier is assigned: 0 0 1 0 1 1 3
Enter carrier absolute radio freq. channel: 620
Enter the 8 carrier frequency hopping indicators: 255 255 255 255 255 255 255 255
Enter the 8 carrier training sequence codes: 0 0 0 0 0 0 0 0
Enter cell zone: 0
Enter the number of extended range timeslots allowed: 0
Enter SDCCH load: 0
Enter channel allocation priority: 0
Enter the packet radio capability (NONE/16 K/32 K/64 K)?: 64K
Enter the value for AMR half-rate enabled = 0
COMMAND ACCEPTED:
WARNING: Insufficient GDS resources available for all PDTCHs on the PCU.

Example 4

In this example, a PCU site 0 is equipped at the BSC:

equip 0 PCU

Where: is:
0 location

System response

Enter the PCU identifier (default 0): 0

Enter the PCU IP address: 127.0.0.2
Enter the PCU subnet mask: 255.255.255.0
Enter the PCU router IP address: 127.0.0.1
Enter the NSEI value: 5047
COMMAND ACCEPTED

The COMMAND ACCEPTED message is replaced by an error message if a PCU with the same ID
exists at the BSC, or the IP address entered is already assigned to another PCU.

68P02901W23-T 3-449
Jan 2010
Examples Chapter 3: Device/function related commands

Example 5

This example attempts to equip pcu_0 as the pcu identifier.

equip 0 PCU

Where: is:
0 location

System response

Enter the PCU Identifier: 1

Enter the PCU base GDS IP Address: 10.15.255.222
Enter the PCU GDS Subnet Mask: 255.255.255.248
Enter the PCU GDS Router IP Address: 25.134.15.33
Enter the WebMMI IP address: 127.0.0.2
Enter the WebMMI subnet mask: 255.255.255.0
Enter the WebMMI router IP address: 127.0.0.1
Enter the NSEI value: 5047
COMMAND REJECTED

ERROR: Range Error, parameter number: 1.

Example 6

In this example, a 64 k MTL is equipped successfully when the increased network capacity
feature is unrestricted.

equip 0 mtl

Where: is:
0 location.
mtl device being equipped.

System response

Enter the device identification for this MTL: 4

Enter the number of DS0 channels for this MTL: 1
Enter the first MMS description for this device: 10
Enter the second MMS description for this device: 0
Enter start timeslot on MMS where this device appears: 15
COMMAND ACCEPTED

3-450 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 7

This example equips an LCF which manages an HSP MTL.

equip 0 lcf

Where: is:
0 location.
lcf device being equipped.

System response

Enter the function identification for the LCF: 1

Enter the number of DS0 channels the LCF can manage as MTLs: 31
WARNING: HSP LCF equipage may trigger GPROC preemption. Are you sure (y=yes,n=no)? y
COMMAND ACCEPTED

Example 8

This example attempts to equip an LCF when the gproc_slot does not equal 32.

equip 0 lcf

Where: is:
0 location.
lcf device being equipped.

System response

Enter the function identification for the LCF: 1

Enter the number of DS0 channels the LCF can manage as MTLs: 31
WARNING: HSP LCF equipage may trigger GPROC preemption. Are you sure (y=yes,n=no)? y
COMMAND REJECTED: Insufficient GPROC timeslots available.

Example 9

In this example, the PCU is equipped when the increase in the throughput of PRP is restricted.

equip 0 pcu

Where: is:
0 location.
pcu device being equipped.

68P02901W23-T 3-451
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Enter the PCU Identifier: 0

Enter the PCU base GDS IP Address: 10.15.255.222
Enter the PCU GDS Subnet Mask: 255.255.255.0
Enter the WebMMI IP address: 127.0.0.2
Enter the WebMMI subnet mask: equip
Enter the WebMMI router IP address: 127.0.0.1
Enter the NSEI value:equip
COMMAND ACCEPTED

Example 10

In this example, two MSI devices of type E1_PMC is supported by the BSC on PXP DPROC.

equip pcu msi

Where: is:
pcu device being equipped.
msi dev_name

System response

Enter the MSI Identifier: 1

Enter the DPROC id: 5
Enter the DPROC socket: 1
COMMAND ACCEPTED

Example 11

In this example, a PSI device is equipped at the BSC.

NOTE
The PSI device is equipped only at a BSS or BSC sites.

equip bsc psi

Where: is:
bsc device being equipped.
psi dev_name

3-452 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Enter the PSI Identifier: 1

Enter the cage number: 0
Enter the slot number: 6
Enter the number of TDM timeslot blocks: 3
Enter the maximum number of GSLs on this PSI: 5
Enter the base IP address for the PSI: 10.0.16.4
Enter the subnet mask: 255.255.255.0
COMMAND ACCEPTED

Example 12

The BSC rejects the equip command for a PSI device if the slot number is not 6, 7, 12 or 13.

NOTE
The BSC rejects the equip command for a PSI device if it is unable to allocate the
specified number of timeslot blocks on the TDM highway.

equip bsc psi

Where: is:
bsc device being equipped.
psi dev_name

System response

Enter the PSI Identifier: 3

Enter the cage number: 0
Enter the slot number: 8
Enter the number of TDM timeslot blocks: 3
Enter the maximum number of GSLs on this PSI: 5
Enter the base IP address for the PSI: 10.3.16.4
Enter the subnet mask: 255.255.255.0
COMMAND REJECTED: Received a request for an invalid slot

68P02901W23-T 3-453
Jan 2010
Examples Chapter 3: Device/function related commands

Example 13

In this example, pcu is equipped when Increase PRP Throughput feature is unrestricted.

equip 0 pcu

Where: is:
0 device being equipped.
pcu dev_name

System response

Enter the PCU Identifier: 0

Enter the PCU base GDS IP Address: 10.15.255.222
Enter the PCU GDS Subnet Mask: 255.255.255.248
Enter the PCU GDS Router IP Address: 10.15.255.221
Enter the WebMMI IP address: 127.0.0.2
Enter the WebMMI subnet mask: 255.255.255.0
Enter the WebMMI router IP address: 127.0.0.1
Enter the NSEI value: 5047
Enter the PRP Fanout Mode: 1
COMMAND ACCEPTED

Example 14

In this example, the operator attempts to enable the opto alarm (out of range 1-6) for EAS
equipped to Horizon II micro cabinet 0 0 0.

equip 8 eas

Where: is:
8 device being equipped.
eas dev_name

System response

Enter the first device ID (Cabinet ID) for the EAS: 0

Enter the relay wiring of the 3 relays (0 - N/O, 1 - N/C): 1 1 1
Enter the no alarm condition for the 6 optos(0 - closed, 1 - open): 1 1 0 0 1 1 0 0 1
ERROR: Extra Parameters, received: 9.

3-454 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 15

This example equips a Horizon II micro extension cabinet to site 12, that is, HORIZONMACRO
master cab.

equip 12 CAB

Where: is:

12 device being equipped.

CAB dev_name

System response

Enter the CABINET identifier: 1

Enter the cabinet type: HORIZON2MICRO_EXT
Enter the frequency type: DCS1800
COMMAND ACCEPTED

Example 16

This example equips a DRI in double density capacity mode to site 7, resulting in DRI devices 0
0 0 and 0 1 0 being equipped when CTU2-D capacity feature is enabled.

equip 7 DRI

Where: is:
7 device being equipped.
dri dev_name

System response

Enter the 1st and 2nd DRI id: 0 0

Enter the density of this DRI: CAPACITY
Enter the 2nd DRI id of the associated DRI: 1
Enter the cabinet type identifier: 0
Enter the type of connection to the BTP: direct
Enter the port to which the TCU is connected: 0
Enter the 1st and 2nd RTF id:
Enter the GSM cell ID where the DRI appears: 0 0 1 0 1 1 1
Enter the antenna select number for this cell: 0
Enter diversity flag for this DRI: 0
Enter the fm cell type: 0
COMMAND ACCEPTED

68P02901W23-T 3-455
Jan 2010
Examples Chapter 3: Device/function related commands

Example 17

This example equips a DRI in double density capacity mode to site 7, resulting in DRI devices 0
0 0 and 0 1 0 equipage being rejected when the CTU2-D capacity feature is restricted.

equip 7 DRI

Where: is:
7 device being equipped.
dri dev_name

System response

Enter the 1st and 2nd DRI id: 0 0

Enter the density of this DRI: CAPACITY
Enter the 2nd DRI id of the associated DRI: 1
Enter the cabinet type identifier: 0
Enter the type of connection to the BTP: direct
Enter the port to which the TCU is connected: 0
Enter the 1st and 2nd RTF id:
Enter the GSM cell ID where the DRI appears: 0 0 1 0 1 1 1
Enter the antenna select number for this cell: 0
Enter diversity flag for this DRI: 0
Enter the fm cell type: 0
COMMAND REJECTED: Received a request to modify a restricted optional feature

Example 18

This example attempts to set ext_pdchs when the Extended Range Cell for Data feature is
restricted (ercgprsOpt = 0), ext_pdchs is not prompted, and BSC is internally set ext_pdchs = 0.

equip 0 RTF

Where: is:
0 device being equipped.
RTF dev_name.

3-456 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Enter type of carrier: NON_BCCH

Enter the 1st and 2nd RTF identifier: 5 11
Enter the GSM cell assigned to this carrier: 0 0 1 0 1 1 18
Enter carrier absolute radio freq. channel: 70
Enter the 8 carrier frequency hopping indicators: 0 0 0 0 0 0 0 0
Enter the 8 carrier training sequence codes: 0 0 0 0 0 0 0 0
Enter KSW pair that manages this carrier: 0
Enter the number of extended range timeslots allowed: 2
Enter SDCCH load: 0
Enter the packet radio capability: 32k
Enter the value for AMR half-rate enabled = 1
Is 8kbps TRAU allowed (yes/no)?: yes
COMMAND ACCEPTED

Example 19

{26638}

This example equips a GBL 0 on the PxP dproc 5 and the Ethernet IP is 196.182.12.30, mask is
255.255.255.0, UDP port is 8192 and gateway IP is 196.182.12.254.

equip pcu gbl

Where: is:
pcu device being equipped.
gbl dev_name.

System response

Enter the GBL identifier: 0

Enter the DPROC id where Gb Ethernet located: 5
Enter the IP address for Gb Ethernet: 196.182.12.30
Enter the subnet mask for Gb Ethernet: 255.255.255.0
Enter the UDP port for Gb Ethernet: 8192
Enter the default gateway for Gb Ethernet: 196.182.12.254

COMMAND ACCEPTED

68P02901W23-T 3-457
Jan 2010
Examples Chapter 3: Device/function related commands

Example 20

{34371G}

This example equips a BTP in the Horizon II macro cabinet. The operator has designated a BBU
attached to the BTP, resulting in a BBU being auto-equipped.

equip 23 BTP

Where: is:
23 location.
BTP device being equipped.

System response

Enter BTP identifier: 1

Is BBU attached: yes
Enter BBU port for inter-BBU connection: 0

COMMAND ACCEPTED

Example 21

{34371G}

This example equips RCTU4 DRI attached to two BBUs and operating in 4 (2+2) density mode.

equip 23 DRI

Where: is:
23 location.
DRI device being equipped.

3-458 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Enter the DRI board type: RH

Enter the cabinet identifier:
Enter the 1st component to attach: BBU
Enter the 1st device ID: 0
Enter the 1st device port: 0
Enter the 1st CTU4 ingress SFP port: 0
Enter the 2nd component to attach: BBU
Enter the 2nd device ID: 1
Enter the 2nd device port: 2
Enter the 2nd CTU4 ingress SFP port: 1
Enter the GSM cell ID where the DRI appears: 0 0 1 0 1 1 1
Enter the ARFCN of the lowest frequency: 10
Enter antenna select number for this cell: 1
Enter the fm cell type: 4
Enter diversity flag for this DRI: 1
Enter the 1st DRI id of all associated DRI: 0
Enter the density of DRI on Tx Port 0: 2
Enter the 2nd DRI id of the 1st associated DRI of Tx port 0: 0
Enter the 1st and 2nd RTF id:
Enter the 2nd DRI id of the 2nd associated DRI of Tx port 0: 1
Enter the 1st and 2nd RTF id:
Enter the density of DRI on Tx Port 1: 2
Enter the 2nd DRI id of the 1st associated DRI of Tx port 1: 2
Enter the 1st and 2nd RTF id:
Enter the 2nd DRI id of the 2nd associated DRI of Tx port 1: 3
Enter the 1st and 2nd RTF id:

COMMAND ACCEPTED

Example 22

{34371G}

This example equips an RTF whose frequency is outside the working bandwidth of an (R)CTU4
in the same cell. A warning message is displayed.

equip 23 RTF

Where: is:
23 location.
RTF device being equipped.

68P02901W23-T 3-459
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Enter capacity of carrier: FULL

Enter type of carrier: BCCH
Enter the 1st and 2nd RTF id: 1 0
Enter primary Unique PATH id: 0
Enter the optional secondary Unique PATH id:
Enter the GSM cell to which this carrier is assigned: 0 0 1 0 1 1 1
Enter carrier absolute radio freq. channel: 113
Enter the 8 carrier frequency hopping indicators: 255 255 255 255 255 255 255 255
Enter the 8 carrier training sequence codes: 0 0 0 0 0 0 0 0
Enter the number of extended range timeslots allowed: 0
Enter SDCCH load: 2
Enter SDCCH placement priority: 0
Enter channel allocation priority: 0
Enter the packet radio capability (NONE/16K/32K/64K)?:
Enter the value for Half Rate enabled: 1
Is 8kbps TRAU allowed (yes/no)?: yes

COMMAND ACCEPTED: WARNING: Some RTF(s) may not be assigned to (R)CTU4

DRI(s) due to 20MHz restriction of (R)CTU4.

Example 23

{36039G}

This example attempts to equip the path with the right MMS being configured.

equip 0 PATH

Where: is:
0 device being equipped.
PATH dev_name.

System response

Enter terminating SITE id: 34

Enter the Unique PATH Identifier: 0
Enter the BSC MMS identifier: 41 0
Enter SITE identifier: 34
Enter the upstream MMS identifier: 0 0
COMMAND ACCEPTED

3-460 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 24

{36039G}

This example attempts to equip the path for a daisy chain link, but one of the MMS is configured
as satellite mode.

equip 0 path

Where: is:
0 device being equipped.
PATH dev_name.

System response

Enter terminating SITE id: 56

Enter the Unique PATH Identifier: 1
Enter the BSC MMS identifier: 1 0
Enter SITE identifier: 53
Enter the upstream MMS identifier: 0 1
Enter SITE identifier: 56
Enter the upstream MMS identifier: 0 1
COMMAND REJECTED: Daisy chain path can not use the mms in satellite mode.

References

Related commands

disp_equipment on page freq_types_allowed on page lock_device on page 3-478

3-315 3-465
modify_value on page 3-507 reassign on page 3-537 shutdown_device on page
3-563
state on page 3-576 unequip on page 3-633 unlock_device on page 3-645

Related information

The order and conditions in which devices and functions can be equipped, and the corresponding
command prompts that are generated during the execution of the equip command are provided
in Chapter 2 Equipping the CM database.

68P02901W23-T 3-461
Jan 2010
fpanel_codeload Chapter 3: Device/function related commands

fpanel_codeload

{33254}

Description

The fpanel_codeload command with the start parameter specifies the following:
Starts the front panel codeload guard timer.

Enables the sFTP client write access to the RAMdisk area.

Clears the objects from the RAMdisk.

The fpanel_codeload command with the commit parameter specifies the following:
Stops the front panel codeload guard timer.

Removes the sFTP client write access to the RAMdisk area.

Copies and checks code objects from the RAMDISK to the non-volatile memory.

Initiates a reset to enable the new objects to load.

For the success of the front panel Ethernet codeload of even a single new code object (including
the CPLD boot object), add a version of the following three boot code objects:
FPGA

BOOT ROM

VXWorks Kernel
These boot code objects must be included (even if they are not being updated) with the objects
that are actually being updated.

Security level 2
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites None
Operator actions This command allows the operator to initiate and complete
the transfer of objects placed in the Ethernet accessible
area of SC-2 memory, when:

The RSL is either physically disconnected from the

BTS cabinet or locked from the OMC.
OR

The SC-2 board is in the Disabled Unlocked state in a

cabinet already containing an H2SC which is acting
as the master site controller.

3-462 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Format

Syntax

fpanel_codeload [{start | commit}]

Input parameter

<start>

Starts the Remove all objects in RAM Disk and Enable write function for the SFTP client.

<commit>

Commits Check all uploaded objects and saves the objects into the bulk flash and initiates a
site reset.

Example

Example 1

This example clears the RAMdisk area of memory in preparation for the new objects.

fpanel_codeload start

System response

This command will clear the RAMdisk and provide you with a 20 minute period in which
you can write new codeobjects to this RAMdisk area using your sFTP client.
Are you sure you wish to proceed (y=yes, n=no)? y

NOTE
The operators load the RAMdisk area with the valid code objects (including the
mandatory subset of boot objects) using an sFTP client within the 20 minute period.

Example 2

This example checks all the uploaded objects.

fpanel_codeload commit

68P02901W23-T 3-463
Jan 2010
Example Chapter 3: Device/function related commands

System response

This command will terminate the RAMdisk write permissions and associated write
period timer, and initiate checks on any objects codeloaded.
Are you sure you wish to proceed (y=yes, n=no)? y

[ Object checking identifies new objects, including one boot object which
is different to that already in use ]
Front panel codeload object transfer to non-volatile memory transfer complete.
Preparing for fast flash programming.
Start Programming <object name>
BOOT objects flash successfully completed.
An automatic site reset will now be initiated.

3-464 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference freq_types_allowed

freq_types_allowed

Description

The freq_types_allowed command specifies the following:

The frequency types available to the BSS (PGSM, EGSM, DCS1800, PCS1900 systems).

The PCS1900 frequency blocks available at the BSS (PCS1900 systems only).

The following are valid frequency types:

PGSM systems (default value) Channels 1 to 124

EGSM systems Channels 0, 1 to 124, 975 to 1023
DCS1800 systems Channels 512 to 885
PCS1900 systems Channels 512 to 810

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites None
Dependencies The frequency types of extended neighbor cells must be
allowed at the BSS.
Operator actions All existing types and blocks must be entered when
specifying a frequency type or frequency block (unless all
types or blocks are specified).
If the system is in SYSGEN OFF mode, the system does
not allow modifying the frequency types if an existing
frequency type or frequency block is not entered. If the
system is in SYSGEN ON mode, and an existing frequency
block or type is not entered, the system deletes that
frequency block or type from the list of allowed types.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

68P02901W23-T 3-465
Jan 2010
Format Chapter 3: Device/function related commands

Format

Syntax

freq_types_allowed [<types>]

Input parameter

types

Specifies the frequency types available to the BSS. The value is entered as: a text string, a
number, or a list of text strings and numbers. The string all specifies all frequency types.
Possible values and text strings are:

Numeric value Text string

1 pgsm
2 egsm
3 pgsm,egsm
4 dcs1800
5 pgsm, dcs1800
6 egsm, dcs1800
7 pgsm, egsm, dcs1800
8 pcs1900
9 pgsm, pcs1900
10 egsm, pcs1900
11 pgsm, egsm, pcs1900
12 dcs1800, pcs1900
13 pgsm, dcs1800, pcs1900
14 egsm, dcs1800, pcs1900
15 pgsm, egsm, dcs1800, pcs1900

More than one frequency type can be entered. See Example 2, below.

If no values are entered, the command displays the frequency types that are currently available.

3-466 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Prompted parameters

The prompt for PCS 1900 frequency blocks appear only if all, pcs1900 or the number 8 is
specified in the command line. If the prompt appears, enter at least one frequency block.

Possible values are:

a Frequency block A Channels 512 to 585

b Frequency block B Channels 612 to 685
c Frequency block C Channels 737 to 810
d Frequency block D Channels 587 to 610
e Frequency block E Channels 687 to 710
f Frequency block F Channels 712 to 735
all all PCS1900 frequency blocks allowed in the BSS

See Example 3, below, for an example of the prompts.

Examples

Example 1

This example displays the allowed frequency types.

freq_types_allowed

System response:

Frequency Blocks Allowed:

PGSM (1 - 124)

Example 2

This example modifies the frequency types allowed to include PGSM when DCS 1800 is already
allowed.

freq_types_allowed pgsm,dcs1800

Where: is:
pgsm frequency type for PGSM frequencies.
dcs1800 frequency type for DCS1800 frequencies.

68P02901W23-T 3-467
Jan 2010
Examples Chapter 3: Device/function related commands

System response:

COMMAND ACCEPTED

Example 3

This example modifies the allowed frequency blocks to include A and D when blocks C and F
are already allowed.

freq_types_allowed pcs1900

Where: is:
8 frequency type for PCS1900 frequencies.

System response:

Enter PCS 1900 frequency blocks: a,c,d,f

COMMAND ACCEPTED

3-468 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gclk_cal_mode

gclk_cal_mode

Description

The gclk_cal_mode command specifies the synchronization function and MCU (Main Control
Unit) software that a calibration is to be performed.

A prompt displays describing the results of entering the command. The prompt must be
acknowledged with a y (yes) to begin the calibration.

No call processing can occur involving this MCU during the calibration mode.

The MCU resets when the calibration is complete.

Security level 2
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed when in the SYSGEN ON
mode.
This command can be executed only at M-Cell sites.

Format

Syntax

gclk_cal_mode

Input parameters

There are no input parameters associated with this command.

Example

In this example, the GCLK calibration at the local site is started:

gclk_cal_mode

68P02901W23-T 3-469
Jan 2010
Example Chapter 3: Device/function related commands

System response

Site <local site number> starting GCLK CALIBRATION MODE.

single MCU site, the site will be down until calibration is complete.
If this is a two MCU site, the site will be down until the redundant
MCU takes over.
If this a Are you sure (y=yes,n=no)? y
COMMAND ACCEPTED

3-470 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ins_device

ins_device

Description

The ins_device command brings a device into service by locking and then unlocking the device.

The following devices are supported:

ABSS AXCDR {34371G} BBU BSP BTP

CAB CAGE CBL CIC COMB
CSFP DHP DRI EAS GCLK
GPROC KSW MMS MSI MTL
OML OPL PATH PCHN PSI
RSL SITE XBL TDM

The ins_device command supports only extension cabinets of type TCU_2, TCU_6, and
HORIZONMACRO_EXT. No other extension cabinet types are supported.

A standby KSW must be available to use this command on a KSW. When the BSC is operating in
enhanced capacity mode, if a redundant DSW is swapped and replaced by a KSW, then the BSS
SW at a BSS rejects an attempt to ins a KSW device, the system displays COMMAND REJECTED:
KSW transition not allowed in Dual Mode configuration message.

If the BSC with the KSW in the cage is reset, the BSC initializes in single rate mode.

If the ins_device command is applied to an active GCLK, and the standby GCLK is phase
locking, the system displays an additional warning message.

The following GPRS devices are supported if the GPRS feature is unrestricted:

ETH DPROC GBL GDS

GSL PCU

The following warning message is displayed when the TS1 of the BCCH carrier of a cell is
INSed and PBCCH/PCCCH is enabled.

WARNING: PBCCH/PCCCH timeslot would be lost which can cause GPRS traffic to be
disrupted. Are you sure (y=yes, n=no)?.

The following device is brought into service at a PCU using this command:

MSI

68P02901W23-T 3-471
Jan 2010
Format Chapter 3: Device/function related commands

A hard reset occurs when this command is entered for the following devices:

BSP BTP DHP GPROC

Security level 2
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites This command is not allowed while in SYSGEN ON mode.
This command can be entered irrespective of whether the
device is locked or unlocked.
Operator actions Respond to the verification request prompt for an ABSS,
AXCDR, BSP, BTP, DHP, GPROC or RSL.
Respond to the verification request prompt for an MSI or
MMS equipped with an OML.

Format

General syntax

ins_device <location> <device_name> <device_id1> <device_id2> <device_id3>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
0 to 140 BTS
pcu or pcu_0 PCU

device_name

Literal that uniquely identifies the device.

device_id1

First device identifier. This definition varies with each device.

device_id2

Second device identifier. This definition varies with each device.

device_id3

Third device identifier. This definition varies with each device.

3-472 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

CIC syntax

A form of syntax is available for each method of specifying a CIC.

The following CIC syntax applies to local transcoding:

ins_device <location> CIC <cic_num1>

ins_device <location> CIC <cic_num1> TO <cic_num2>

ins_device <location> CIC <mms_id1> <mms_id2>

ins_device <location> CIC <mms_id1> <mms_id2> <timeslot1>

ins_device <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2>

The following CIC syntax applies to remote transcoding:

NOTE
For remote transcoding BSC sites, the ins_device command cannot be used for CICs
on a per-MMS basis when the BSC is operating in the dynamic allocation mode.

ins_device <location> CIC <cic_num1>

ins_device <location> CIC <cic_num1> TO <cic_num2>

ins_device <location> CIC <mms_id1> <mms_id2>

ins_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group>

ins_device <location> CIC <mms_id1> <mms_id2> <timeslot1> *

ins_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2>

<group2>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
0 to 140 BTS
pcu, pcu_0 to pcu_2 PCU

CIC

Literal that uniquely identifies the CIC device.

cic_num1

First CIC device number.

68P02901W23-T 3-473
Jan 2010
Examples Chapter 3: Device/function related commands

cic_num2

Last CIC device number in a range.

mms_id1

First MMS identifier.

mms_id2

Second MMS identifier, or last in a range if TO is used.

timeslot1

First timeslot.

timeslot2

Second timeslot, or last in a range if TO is used.

group1

First group.

group2

Second group.

Indicates all CICs on the MMSs specified in the timeslot, regardless of the group.

Examples

Example 1

This example brings an MSI into service with ID 1 0 at the BSC.

ins_device bsc msi 1 0 0

Where: is:
bsc location
msi device_name
1 device_id1
0 device_id2
0 device_id3

System response

COMMAND ACCEPTED

3-474 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 2

This example brings a range of CICs (remote transcoder) into service; the range is specified by
their MMS, TS, and group.

ins_device bsc cic 2 1 3 1 TO 5 1

Where: is:
bsc location
cic CIC (device_name)
2 mms_id1
1 mms_id2
3 timeslot 3
1 group 1
5 timeslot 5
1 group 1

System response

COMMAND ACCEPTED

Example 3

This example attempts to bring a KSW into service if the BSC is under enhanced capacity mode.

ins 0 KSW 1 0

Where: is:
0 location
KSW device_name
1 device_id1
0 device_id2

System Response

COMMAND REJECTED: KSW transition not allowed in Dual Mode configuration.

68P02901W23-T 3-475
Jan 2010
Examples Chapter 3: Device/function related commands

Example 4

{34371G}

This example attempts to INS the standby BTP 1 0 0 and there is a BBU attached to the BTP.

ins_device 23 btp 1 0 0

Where: is:
23 location
btp device_name
1 device_id1
0 device_id2
0 device_id3

System response

WARNING: Associated BBU and DRIs are affected by this command

Are you sure (y=yes,n=no)?y

COMMAND ACCEPTED

Example 5

{34371G}

This example attempts to INS BBU 0 0 0.

ins_device 23 bbu 0 0 0

Where: is:
23 location
bbu device_name
0 device_id1
0 device_id2
0 device_id3

WARNING: Associated DRIs and potential another BBU are affected by this command
Are you sure (y=yes,n=no)?y

COMMAND ACCEPTED

3-476 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 3

This example brings a cage into service and displays a confirmed command. A warning about
the cage INS is displayed.

ins_device bsc cage 3 0

Where: is:
bsc location
cage device_name
3 device_id1
0 device_id2

System response

CAGE 3 This will affect all devices in this CAGE and any associated
Extension CAGEs.
Are you sure (y=yes,n=no)? yes
COMMAND ACCEPTED

References

Related commands

lock_device on page 3-478 reset_device on page 3-544 unlock_device on page 3-645

68P02901W23-T 3-477
Jan 2010
lock_device Chapter 3: Device/function related commands

lock_device

Description

The lock_device command locks a specified device.

Security level 2
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.
This command is only valid when the device is in the
UNLOCKED state.

Format

General syntax

lock_device <location> <device_name> <device_id1> <device_id2> [<device_id3>]

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

The location must be bsc or 0 when specifying the device SITE. A PCU or a PCU device (for
example, MSI) can also be locked.

device_name

Device name that uniquely identifies the device.

The following devices can be locked using this command:

ABSS AXCDR {34371G} BSP BTP CAB CAGE CBL

BBU
CIC COMB CSFP DHP DRI DPROC EAS GBL
GCLK GDS GPROC GSL KSW MMS MSI MTL
OML OPL PATH PCHN PCU RSL SITE XBL

3-478 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

The shutdown_device command is available for non-intrusive locking of CIC, DRI, MPRT, and
MTL devices.

If an MMS at an RXCDR is locked, it does not lock any OMLs or MTLs that are carried on its
associated 2 Mbit/s link. However, any traffic circuit carried on this 2 Mbit/s link is blocked.
This prevents any inadvertently locking devices at the RXCDR, where their existence on a 2
Mbit/s link is not visible.

If locking the MTL or OML is necessary, they should be addressed as individual devices.

Entering the lock_device command where the MSI or MMS carries an OML causes the system
to display a verification request before actually locking the device.

Locking the link between an RXCDR and the BSC MMS makes the associated XBL go out of
service (OOS). This means that XBL does not block the circuits.

When locking an ABSS or AXCDR, the system presents a warning prompt and a verification
prompt.

If XBLs are equipped on the first and second links, and the XBL on the first link is locked, the
XBL on the first link goes OOS; the XBL on the second link blocks the circuits.

If the lock_device command is applied to an active GCLK, and the standby GCLK is phase
locked, the system displays an additional warning message.

This command is rejected for a KSW if no standby KSW is available. When a KSW is locked, all
calls currently on the KSW are lost. Normal call processing resumes when the KSW is unlocked.

For remote transcoding BSC sites, CICs cannot be locked on a per-MMS basis when the BSC is
operating in the dynamic allocation mode.

The lock_device command supports the following extension cabinets: TCU_2, TCU_6,
Horizonmacro_EXT, Horizon2macro_ext, Horizon2micro_ext, and Horizon2mini_ext. DRIs and
EASs equipped to the cabinet are disabled. No other cabinet types are supported.

The following warning message is displayed when the TS1 of the BCCH carrier of a cell is
locked and PBCCH/PCCCH is enabled.

WARNING: PBCCH/PCCCH timeslot would be lost which can cause GPRS traffic to be
disrupted. Are you sure (y=yes, n=no)?

A hard reset occurs when this command is entered for the following devices:

BSP DHP
BTP GPROC

device_id1

First device identifier. This value varies with each device.

device_id2

Second device identifier. This value varies with each device.

device_id3

Third device identifier. This value varies with each device.

If the specified device is a PCU, the PCU identifier must be entered as device_id1. A PCU or
PCU device (for example MSI) can also be locked as a location.

68P02901W23-T 3-479
Jan 2010
Format Chapter 3: Device/function related commands

CIC syntax

A form of syntax is available for each method of specifying a CIC.

The following CIC syntax applies to local transcoding:

lock_device <location> CIC <cic_num1>

lock_device <location> CIC <cic_num1> TO <cic_num2>

lock_device <location> CIC <mms_id1> <mms_id2>

lock_device <location> CIC <mms_id1> <mms_id2> <timeslot1>

lock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2>

The following CIC syntax applies to remote transcoding:

lock_device <location> CIC <cic_num1>

lock_device <location> CIC <cic_num1> TO <cic_num2>

lock_device <location> CIC <mms_id1> <mms_id2>

lock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group>

lock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> *

lock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO

<timeslot2> <group2>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS

CIC

Literal that uniquely identifies the CIC device.

cic_num1

First CIC device number.

cic_num2

Last CIC device number in a range.

3-480 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

mms_id1

First MMS identifier.

mms_id2

Second MMS identifier, or last in a range if TO is used.

timeslot1

First timeslot.

timeslot2

Second timeslot, or last in a range if TO is used.

group1

First group.

group2

Second group.

Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

Examples

Example 1

This example locks an MSI with ID 1 at the BSC from further use.

lock_device bsc msi 1 0 0

Where: is:
bsc location
msi device_name
1 device_id1
0 device_id2
0 device_id3

System response

COMMAND ACCEPTED

68P02901W23-T 3-481
Jan 2010
Examples Chapter 3: Device/function related commands

Example 2

This example locks a range of CICs; the range is specified by their MMS, TS, and group.

lock_device bsc cic 2 1 3 1 TO 5 1

Where: is:
BSC location
CIC device_name
2 mms_id1
1 mms_id2
3 timeslot 3
1 group 1
5 timeslot 5
1 group 1

System response

COMMAND ACCEPTED

Example 3

This example displays PXP DPROC information.

lock pcu_0 dproc 4 0

Where: is:
pcu_0 location
dproc device_name
4 mms_id1
0 mms_id2

System response

This command will affect the following link devices

---------------------------------------------------
GDS 4 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.
GSL 0 0 The GSL carries signaling traffic between the BSC and the PCU.
If there are no B-U GSL devices, the PCU will go out of service.
GSL 0 2 The GSL carries signaling traffic between the BSC and the PCU.

3-482 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

If there are no B-U GSL devices, the PCU will go out of service.
Are you sure (y=yes,n=no)?

Example 4

This example locks a cage and displays a confirmed command. A warning about the cage lock
is issued.

lock_device bsc cage 1 0

Where: is:
bsc location
cage device_name
1 device_id1
0 device_id2

System response

CAGE 1 This will affect all devices in this CAGE and any associated
Extension CAGEs.
Are you sure (y=yes,n=no)? yes
COMMAND ACCEPTED

Example 5

This example locks a cage when the lock command action results in the standby BSP going
out of service.

lock_device bsc cage 1 0

Where: is:
bsc location
cage device_name
1 device_id1
0 device_id2

System response

CAGE 1 This will affect all devices in this CAGE and any associated
Extension CAGEs.
WARNING: This will result in the loss of the standby BSP at this BSC.
Are you sure (y=yes,n=no)? yes
COMMAND ACCEPTED

68P02901W23-T 3-483
Jan 2010
Examples Chapter 3: Device/function related commands

Example 6

This example displays warning about links impacted by a cage transition.

lock_device 0 cage 1 0 0

Where: is:
0 location
cage device_name
1 device_id1
0 device_id2
0 device_id3

System response

CAGE 1 This will affect all devices in this CAGE and any associated
Extension CAGEs.
This command will affect the following link devices:
----------------------------------------------------

OML 1 The OML carries operations and maintenance traffic between

the BSS and the OMC. If there are no B-U OML devices, the
OMC will not be able to manage the BSS.

MTL 0 The MTL carries signaling traffic between the BSS and the
MSC. If there are no B-U MTL devices, all cells in the BSS
will become blocked.

MTL 2 The MTL carries signaling traffic between the BSS and the
MSC. If there are no B-U MTL devices, all cells in the BSS
will become blocked.

RSL 7 0 This command may affect service to the BTS. Use the state
command to verify if this is the last RSL to the BTS. The RSL
carries signaling traffic between the BSC and a BTS. If there
are no B-U RSL devices to a given BTS, all access to the site
will be lost.

RSL 7 1 This command may affect service to the BTS. Use the state
command to verify if this is the last RSL to the BTS. The RSL
carries signaling traffic between the BSC and a BTS. If there
are no B-U RSL devices to a given BTS, all access to the site
will be lost.

RSL 11 0 This command may affect service to the BTS. Use the state
command to verify if this is the last RSL to the BTS. The RSL
carries signaling traffic between the BSC and a BTS. If there
are no B-U RSL devices to a given BTS, all access to the site
Continued

3-484 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

will be lost.

RSL 12 0 This command may affect service to the BTS. Use the state
command to verify if this is the last RSL to the BTS. The RSL
carries signaling traffic between the BSC and a BTS. If there
are no B-U RSL devices to a given BTS, all access to the site
will be lost.

Are you sure (y=yes,n=no)? yes

COMMAND ACCEPTED

Example 7

{34371G}

This example attempts to lock the standby BTP 1 0 0 and there is a BBU attached to the BTP.

lock_device 23 btp 1 0 0

Where: is:
23 location
btp device_name
1 device_id1
0 device_id2
0 device_id3

System response

WARNING: Associated BBU and DRIs are affected by this command

Are you sure (y=yes,n=no)?y

COMMAND ACCEPTED

Example 8

{34371G}

This example attempts to lock the BBU 0 0 0.

lock_device 23 bbu 0 0 0

68P02901W23-T 3-485
Jan 2010
Examples Chapter 3: Device/function related commands

Where: is:
23 location
bbu device_name
0 device_id1
0 device_id2
0 device_id3

System response

WARNING: Associated DRIs and potential another BBU are affected by this command
Are you sure (y=yes,n=no)?y

COMMAND ACCEPTED

Example 9

This example successfully locks a pool GPROC or a GPROC supporting a function other than
the OMF.

lock 0 gproc 1 0

Where: is:
0 location
gproc device_name
1 mms_id1
0 mms_id2

System response

GPROC 1 0 A function may reside on this GPROC. If there are no available

B-U GPROCs the related function may go OOS and if the function
is the OMF OML OOS will occur. Use the disp_processor
command to confirm if a related function exists.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED.

3-486 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 10

This example successfully locks the GPROC supporting the OMF when there is an
Enabled-Unlocked GPROC available to support the OMF.

lock 0 gproc 9 0

Where: is:
0 location
gproc device_name
9 mms_id1
0 mms_id2

System response

GPROC 9 0 A function may reside on this GPROC. If there are no available

B-U GPROCs the related function may go OOS and if the function
is the OMF OML OOS will occur. Use the disp_processor
command to confirm if a related function exists.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED.

Example 11

This example successfully locks the GPROC supporting the OMF when the GPROC pre-emption
is enabled (that is pool_gproc_preemption = 1 or 2) and pre-emption is required to obtain a
new GPROC to support the OMF.

lock 0 gproc 9 0

Where: is:
0 location
gproc device_name
9 mms_id1
0 mms_id2

68P02901W23-T 3-487
Jan 2010
References Chapter 3: Device/function related commands

System response

GPROC 9 0 A function may reside on this GPROC. If there are no available

B-U GPROCs the related function may go OOS and if the function
is the OMF OML OOS will occur. Use the disp_processor
command to confirm if a related function exists.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED: GPROC pre-emption will be triggered to allocate a new GPROC.

References

Related commands

disp_equipment on page equip on page 3-445 reset_device on page 3-544

3-315
shutdown_device on page state on page 3-576 unequip on page 3-633
3-563
unlock_device on page 3-645

3-488 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Login

Login

Description

The login command authenticates a qcomm user of certain access level.

Security level 1

Supported by OMC-R GUI No

Command type B (operator actions required)
Prerequisites None

Format

Syntax

login

Example

NOTE

BSS does not support login command to be executed twice without logout.

The password shown in this example is only for information. The passwords are
not displayed when entered.

Example 1

This example authenticates an operator to log in with the unix account information or field
engineer user information.

login

68P02901W23-T 3-489
Jan 2010
Example Chapter 3: Device/function related commands

System response

Please input your UNIX account information.

Login: abcdef
Password: abcdef
COMMAND ACCEPTED

Example 2

In this example, the OML link is up and fieldeng_always_enabled is set to 0

login

System response

Please input your UNIX account information.

Login: abcdef
Password: abcdef
COMMAND ACCEPTED

Example 3

In this example, the OML link is down and fieldeng_always_enabled is set to 0

login

System response

Please input your Field Engineer account information.

Login: abcd
Password: abcdef
WARNING: Login incorrect
Please input your Field Engineer account information.
Login: abcd
Password: abcdef
WARNING: Login incorrect
Please input your Field Engineer account information.
Login: abcd
Password: abcdef
WARNING: Login incorrect
COMMAND REJECTED: Login Blocked.

3-490 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Logout

Logout

Description

The logout command terminates all the activities of the current operator.

Security level 1
Supported by OMC-R GUI No
Command type B (operator actions required)
Prerequisites None

Format

Syntax

logout

68P02901W23-T 3-491
Jan 2010
mod_conn Chapter 3: Device/function related commands

mod_conn

Description

The mod_conn command modifies the MMS connectivity between the RXCDR and the BSS.

This command allows the operator to change 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.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites The AXCDR or ABSS device specified in the command must
be equipped in the BSS database.
No XBL devices can be equipped that use the local MMS
when changing the BSS or RXCDR network entity identifier.
The local MMS must be locked before the connectivity is
modified.
Operator actions Change the security level to 2.
Lock the local MMS before modifying the connectivity.

Format

Syntax

mod_conn <local_mms_id_1> <local_mms_id_2> <network_entity_id>

<remote_mms_id_1><remote_mms_id_2>

Input parameters

local_mms_id_1

First identifier of the MMS at the local site. The term local site refers to the site where the
command is being entered.

local_mms_id_2

Second identifier of the MMS at the local site.

3-492 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

network_entity_id

The AXCDR or ABSS device identifier that represents the actual RXCDR or BSS with which
this MMS is communicating.

remote_mms_id_1

First identifier of the MMS at the remote site. The term remote site refers to the site to
which the local site is connected.

remote_mms_id_2

Second identifier of the MMS at the remote site.

The mod_conn command can be executed from either the BSC or the RXCDR. The ranges for
several input parameters depend on where the command is executed, as shown in Table 3-32.

Table 3-32 mod_conn valid ranges

Execution location
Input parameter
BSC RXCDR
local_mms_id_1 0 to 95 0 to 123
local_mms_id_2 0 or 1 0 or 1
network_entity_id 1 to 254 1 to 254
remote_mms_id_1 0 to 123 0 to 95
remote_mms_id_2 0 or 1 0 or 1

Example

This example changes MMS connectivity between BSC MMS 4 1 and RXCDR MMS 9 0 of
RXCDR 3, which is represented by equipped device AXCDR 3.

mod_conn 4 1 3 9 0

Where: is:
4 local_mms_id_1
1 local_mms_id_2
3 network_entity_id
9 remote_mms_id_1
0 remote_mms_id_2

System response:

COMMAND ACCEPTED

68P02901W23-T 3-493
Jan 2010
References Chapter 3: Device/function related commands

References

Related commands

add_conn on page 3-33 del_conn on page 3-215 disp_conn on page 3-282

3-494 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference mod_nsvc

mod_nsvc

Description

The mod_nsvc command modifies the frame relay committed information rate, the frame relay
burst size, and the frame relay burst excess for a specified Network Service - Virtual Connection
Identifier (NSVCI), at a specific PCU.

{26638} The BSC will support to modify IP based NSVC if gb_mode is set to static IP mode,
and support to modify frame relay NSVC if gb_mode is set to frame relay mode.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites The GPRS feature must be unrestricted.
Operator action The operator must answer the prompts.

Format

Syntax

mod_nsvc <pcu_id> <ns_vci>

Input parameter

pcu_id

Specifies the unique identifier of the PCU, as pcu or pcu_0.

ns_vci

Specifies the unique identifier of the NSVC mapping and identifier of the object. The range
is 0 to 65535.

Prompts are then displayed as follows:

Enter the Committed Information rate:

Enter the Committed Burst Size:
Enter the Burst Excess:

The first prompt specifies the frame relay committed information rate ns_commit_info_rate
(0 to 1984). There is no default.

The second specifies the frame relay burst size ns_burst_size (0 to 1984). There is no default.

68P02901W23-T 3-495
Jan 2010
Example Chapter 3: Device/function related commands

The third specifies the frame relay burst excess ns_burst_excess (0 to 1984). There is no
default.

NOTE
ns_burst_size and ns_burst_excess, both must not be 0. If either
ns_commit_info_rate or ns_burst_size is 0, then both must be 0.

{26638} The following prompts are displayed:

#If <Gb over IP feature unrestricted and gb_mode set to 'Static IP' mode> then:

Prompt Required Value Definition/Range/Default

--------- --------- ------------------

Enter the SGSN side Yes IPv4 address of remote IP endpoint,

IP Address: Class A/B/C IPv4 address except loopback
127.x.x.x, no default.

Enter the SGSN side Yes UDP port of remote IP endpoint, Range
UDP port: 0-65535,no default.

Enter the SGSN side Yes Signaling weight associated with remote
signaling weight: IP endpoint, Range 0-255,no default.

Enter the SGSN side Yes Date weight associated with remote
data weight: IP endpoint, Range 0-255,no default.

#End If

Example

Example 1

The following example modifies the frame relay committed information rate, the frame relay
burst size, and the frame relay burst excess for NSVCI 6, at PCU_2 site.

mod_nsvc pcu_2 6

Where: is:
pcu_2 PCU site 2
6 NSVCI identifier

3-496 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

Enter the Committed Information Rate:64

Enter the Committed Burst Size:64
Enter the Burst Excess:64

WARNING: This may cause a loss of data.

Are you sure (y=yes, n=no) ? y

COMMAND ACCEPTED

Example 2

{26638}

This example modifies the parameters of NSVC 7 at pcu 0 when the gb_mode parameter is
set to static IP mode.

mod_nsvc pcu 7

Where: is:
pcu PCU site
7 NSVCI identifier

System response

Enter the SGSN side IP Address: 10.1.2.3

Enter the SGSN side UDP port: 2048
Enter the SGSN side signaling weight: 0
Enter the SGSN side data weight: 100

COMMAND ACCEPTED

References

Related commands

del_nsvc on page 3-222 add_nsvc on page 3-47

68P02901W23-T 3-497
Jan 2010
modify_neighbor Chapter 3: Device/function related commands

modify_neighbor

Description

The modify_neighbor command modifies the value of a GSM or UTRAN neighbor cell
parameter. The neighbor_cell_id can be a test cell neighbor.

The changing of the ba_bcch parameter is only allowed for test neighbors which are on the
BA_SACCH list of the cell. To add a neighbor to the BA_BCCH list without adding to the
BA_SACCH list, use the add_neighbor command. To remove a neighbor from the BA_BCCH list
which is not on the BA_SACCH list, use the del_neighbor command.

When pgbt_mode is set to 1, a new neighbor is auto-equipped with its BCCH frequency set
to the BCCH frequency of the serving cell. This neighbor cell cannot be modified by the
modify_neighbor command.

If the Inter-RAT handover feature or Enhanced 2G/3G handover feature (which includes
Enhanced Inter-RAT handover) is unrestricted, handovers can be made to UTRAN cells.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The changing of the synchronized parameter is only
allowed for neighbors at the site of the source cell.
If the neighbor is a UTRAN cell, the Inter-RAT handover
feature must be unrestricted.
A UTRAN neighbor-specific parameter cannot be modified
for a GSM neighbor cell.
A GSM neighbor-specific parameter cannot be modified for
a UTRAN neighbor cell.
The specified UTRAN cell identifier must exist as a
neighbor cell of the GSM source cell.
If the neighbor is a UTRAN cell, the Inter-RAT handover
feature or Enhanced 2G/3G handover feature must be
unrestricted.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

3-498 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Format

Syntax

modify_neighbor <source_cell_id> <neighbor_cell_id> <parameter> <value>

Input parameters

source_cell_id

Cell identity of the source cell.

neighbor_cell_id

Cell identity of the neighbor cell whose parameter value is being changed.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

Whether the cell is a UTRAN cell. The cell_id can also be a cell name created using the
cell_name command. When the cell name is entered, it must be placed inside double
quotation marks.

For an internal neighbor cell only, the cell_id can also be a cell name created using the
cell_name command. A cell_name cannot be used to specify an external neighbor cell. When
the cell name is entered, it must be placed inside double quotation marks.

parameter

Neighbor cell parameter to be changed, one of:

Parameter Action
adap_trigger_pbgt_nbr Specifies the cumulative area for the adaptive handover
power budget algorithm; valid only for SACCH and
SACCH/BCCH neighbors.
adj_chan_intf_test Turns adjacent channel interference on or off.
ba_bcch Adds or deletes a neighbor cell from the BA_BCCH list.
ba_gprs Adds or deletes a neighbor cell from the BA_GPRS list.
congest_ho_margin Determines the handover margin to be used in the event
of congestion. This value is only changed when either the
Directed Retry or alternate congestion relief feature is
enabled. This attribute is only valid for SACCH neighbors.
If the directed retry feature is not enabled, the value
defaults to the value of the ho_margin_cell of the neighbor.
The system does not prompt for the congest_ho_margin
value if the Directed Retry option was not purchased.

Continued

68P02901W23-T 3-499
Jan 2010
Format Chapter 3: Device/function related commands

Parameter Action
dr_allowed Allows a directed retry to an external neighbor during
the assignment procedure. An external handover is
only initiated if either the dr_standard_congest or
dr_ho_during_assign parameter is enabled. This attribute
is only valid for SACCH neighbors.
The system does not prompt for the dr_allowed value if the
Directed Retry option was not purchased.
ho_margin_cell Changes handover margin of a neighbor cell.
ho_margin_rxlev Sets the value to be applied to the power budget calculation
when calls are handed over due to transmission levels
(rxlev).
If the power budget value minus the ho_margin_rxlev is
less than 0 for a cell, that cell is excluded from the neighbor
list.
This parameter also interacts with the bounce_protect_mar
to prevent reverse handovers due to power budget reasons.
Refer to the bounce_protect_mar description.
ho_margin_rxqual Sets the value to be applied to the power budget calculation
when calls are handed over due to transmission quality
levels (rxqual).
If the power budget value minus the ho_margin_rxqual is
less than 0 for a cell, that cell is excluded from the neighbor
list.
This parameter also interacts with the bounce_protect_mar
to prevent reverse handovers due to power budget reasons.
Refer to the bounce_protect_mar description.
interfering_nbr Enables or disables the interference algorithm for the inner
zone for this neighbor. This is allowed only if both:

The Concentric Cells feature is enabled.

The inner_zone_alg is set to 2.

If the interfering_nbr parameter is enabled, the
system displays the inner_zone_threshold and
inner_zone_margin prompts.
Pressing the Return (Enter) key without entering
new values for the inner_zone_threshold and the
inner_zone_margin prompts will keep any existing
values.
ms_txpwr_max_cell Changes the maximum MS transmitted power for a neighbor
cell.
neighboring_range Changes which range the neighbor borders on in an
extended cell.
pbgt_alg_type Changes the power budget algorithm type.
pbgt_hreqave Changes the power budget hreqave.
rxlev_min_cell Changes minimum receive level for a neighbor cell.
synchronized Allows synchronized handovers for neighbor cells.
fdd_arfcn Indicates the frequency of a UTRAN cell.

Continued

3-500 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Parameter Action
scr_code Indicates the primary scrambling code of a UTRAN cell.
diversity_enabled Indicates whether diversity is applied in a UTRAN cell.
umts_meas_margin Defines the per neighbor handover threshold. Only valid
when a UTRAN BCCH or SACCH neighbor cell is specified.
umts_ncell_avg_period Defines the per neighbor averaging period. Only valid when
a UTRAN BCCH or SACCH neighbor cell is specified.
umts_ba_bcch Adds or deletes a UTRAN BCCH neighbor from the
UMTS_BA_BCCH list.
tdd_arfcn Indicates the TD-SCDMA frequency. This is a Read-Write
attribute of the UTRAN Neighbor Cell. When tdOpt is
restricted, this parameter cannot be modified.
tdd_cell_param Indicates the TD-SCDMA cell parameter as defined in
TS25.223. This is a Read-Write attribute of the UTRAN
Neighbor Cell. When tdOpt is restricted, this parameter
cannot be modified.
tdd_tstd_mode Indicates the TD-SCDMA Time Switched Transmit Diversity
mode. This is a Read-Write attribute of the UTRAN Neighbor
Cell. When tdOpt is restricted, this parameter cannot be
modified.
tdd_sctd_mode Indicates the TD-SCDMA cell diversity capability (Space
Code Transmit Diversity). This is a Read-Write attribute of
the UTRAN Neighbor Cell.

value

The new value of the selected neighbor cell parameter. Values for this field are dependent
upon the selected parameter.

Parameter Value
adap_trigger_pbgt_nbr 0 to 255; default is 40 (the value of 40 corresponds to an
hreqave of 8 and a handover margin of 5)
adj_chan_intf_test 0 (no) or 1 (yes)
ba_bcch add or delete
congest_ho_margin -63 to 63
dr_allowed 0 (no) or 1 (yes)
ho_margin_cell -63 to 63
ho_margin_rxlev -63 to 63
ho_margin_rxqual -63 to 63
ho_margin_type5 -63 to 63
interfering_nbr 0 (no) or 1 (yes)
ms_txpwr_max_cell PGSM or EGSM: 5 to 39 (odd values only)
DCS1800: 0 to 30 (even values only)
PCS1900: 0 to 30 (even values only)
GSM850: 5 to 39 (odd values only)

Continued

68P02901W23-T 3-501
Jan 2010
Examples Chapter 3: Device/function related commands

Parameter Value
neighboring_range normal (neighbor is a normal range cell)
extended (neighbor is an extended range cell)
pbgt_alg_type 1 to 6
pbgt_hreqave 1 to 31
rxlev_min_cell 0 to 63
synchronized yes or no

fdd_arfcn 10562 to 10838

scr_code 0 to 511
diversity_enabled 0 or 1
umts_meas_margin 0 to 20 dB; default is 3 dB (for UTRAN BCCH or UTRAN
SACCH neighbors if 2G/3G Handover feature is unrestricted)
umts_ncell_avg_period 1 to 12; default is 6 (for UTRAN BCCH or UTRAN SACCH
neighbors if 2G/3G Handover feature is unrestricted)
umts_ba_bcch Add or delete (for UTRAN BCCH neighbors only)
tdd_arfcn 10054 to 10121
tdd_cell_param 0 to 127
tdd_tstd_mode 0 (Disabled) or 1 (Enabled); default is 0
tdd_sctd_mode 0 (Disabled) or 1 (Enabled); default is 0

NOTE
If the pbgt_alg_type, adj_chan_intf_test or interfering_nbr is modified by this
command, additional prompts display. Refer to the description of the add_neighbor
command for the prompted parameter values.

Examples

Example 1

This example adds the frequency of neighbor cell 5 4 3 2 1 4344 9755 to the BA_BCCH list of
source cell 5 4 3 2 1 676 8645. The cell numbers are in seven parameter format.

modify_neighbor 5 4 3 2 1 676 8645 5 4 3 2 1 4344 9755 ba_bcch add

Where: is:
5 4 3 2 1 676 8645 src_cell_id
5 4 3 2 1 4344 9755 neighbor_cell_id
ba_bcch the parameter to be modified.
add the parameter value.

3-502 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

COMMAND ACCEPTED

Example 2

The example below shows the same cell numbers in four parameter format:

modify_neighbor 543 21 676 8645 543 21 4344 9755 ba_bcch add

Where: is:
543 21 676 8645 src_cell_id
543 21 4344 9755 neighbor_cell_id
ba_bcch the parameter to be modified.
add the parameter value.

System response

COMMAND ACCEPTED

Example 3

This example changes the power budget algorithm to 3 for neighbor cell 5 4 3 2 1 344 975 of
src_cell 5 4 3 2 1 667 865. Additional prompts display.

NOTE
This example shows interaction associated with the M-Cellmicro option.

modify_neighbor 5 4 3 2 1 667 865 5 4 3 2 1 344 975 pbgt_alg_type 3

Where: is:
5 4 3 2 1 667 865 src_cell_id
5 4 3 2 1 344 975 neighbor_cell_id
pbgt_alg_type the parameter to be modified.
3 the parameter value.

System response

Enter the uplink receive level threshold of the serving cell: 25

COMMAND ACCEPTED

Enter the downlink receive level threshold of the serving cell: 25

68P02901W23-T 3-503
Jan 2010
Examples Chapter 3: Device/function related commands

Example 4

This example sets the interfering_nbr to 1 (yes).

modify_neighbor 5 4 3 2 1 667 865 5 4 3 2 1 344 975 interfering_nbr 1

Where: is:
5 4 3 2 1 667 865 src_cell_id
5 4 3 2 1 344 975 neighbor_cell_id
interfering_nbr the parameter to be modified.
1 the parameter value.

System response

Enter the threshold for inner zone handover: 1

Enter the margin for inner zone handover: 1

COMMAND ACCEPTED

Example 5

This example modifies the scr_code element of UTRAN neighbor cell 4 9 6 2 3 1 1 1 1 to a value
of 5 as a neighbor of source GSM cell 0 0 1 0 1 1 4.

modify_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 scr_code 5

Where: is:
0010114 src_cell_id (GSM)
496231111 neighbor_cell_id (UTRAN)
scr_code the parameter to be modified.
5 the parameter value.

System response

COMMAND ACCEPTED

3-504 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 6

This example modifies the umts_ba_type for UTRAN BCCH neighbor l 4 9 6 2 3 1 1 1 1 of GSM
cell 0 0 1 0 1 1 4 to include it in the UTRAN BCCH neighbor list.

modify_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_ba_bcch add

Where: is:
0010114 src_cell_id (GSM)
496231111 neighbor_cell_id (UTRAN)
umts_ba_bcch the parameter to be modified.
add the parameter value.

System response

COMMAND ACCEPTED

Example 7

This example modifies the tdd_cell_param attribute to a value of 100 for TD-SCDMA cell 4 9 6
2 3 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4.

modify_nieghbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 tdd_cell_parameter 100

Where: is:
0010114 src_cell_id (GSM)
496231111 neighbor_cell_id (UTRAN)
tdd_cell_param the parameter to be modified.
100 the parameter value.

System response

COMMAND ACCEPTED

NOTE
This response is also applied for tdd_arfcn, tstd_mode, and tdd_diversity_enabled
for TD-SCDMA neighbor cell attributes.

68P02901W23-T 3-505
Jan 2010
References Chapter 3: Device/function related commands

References

Related commands

add_cell on page 3-22 add_neighbor on page 3-35 copy_cell on page 3-199

del_cell on page 3-212 del_neighbor on page 3-217 disp_cell on page 3-261
disp_gsm_cells on page 3-350 disp_neighbor on page 3-379

3-506 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference modify_value

modify_value

Description

The modify_value command modifies parameter values for equipped devices or functions.
These values can be displayed using the disp_equipment command.

This command is rejected if a dual band Horizon II macro cabinet contains an invalid Horizon II
Dual Band DRI setup.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Security level 4
Supported by OMC-R GUI Yes
Command type The type is dependent on the parameter being modified.
Prerequisites The modify_value command can only be entered at the
BSC.
Individual prerequisites are given for modify_value
parameters as relevant.
The GPRS PICP MSI type is not supported by this command.
Operator actions To use all as the location parameter, place the system in
the SYSGEN ON mode before entering the command.

NOTE
Refer to the descriptions of individual parameters for additional operator actions.

Format

Syntax

modify_value <location> <value_name> <new_value> <dev_func>

<dev_func_id1><dev_func_id2> <dev_func_id3>

Input parameters

location

68P02901W23-T 3-507
Jan 2010
Format Chapter 3: Device/function related commands

Specifies the location of the device. Values are:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU
all Every equipped device or function of the specified type.
Only applicable to MMS, RSL, and XBL.
This value is only applicable during SYSGEN ON mode.
If it is entered, the parameters dev_func_id1, dev_func_id2
and dev_func_id3 are not required.

value_name

The device or function parameter name. Refer to the individual parameter listing in Chapter 8
Device/Function parameters for descriptions and valid values of these parameters.

new_value

The value to be assigned to the named parameter. Refer to the individual parameter descriptions
in Chapter 8 Device/Function parameters for valid values.

dev_func

This value identifies the device or function affected by the modified parameter. For example,
BSP, GCLK, SITE, as relevant to the value_name parameter. See Chapter 8 Device/Function
parameters.

dev_func_id1

Values are dependent on the device or function type.

dev_func_id2

Values are dependent on the device or function type.

dev_func_id3

Values are dependent on the device or function type.

NOTE

When changing certain cabinet types with this command, the following message
is displayed:
Cannot change to new cab type as bts power control is enabled.
When an attempt is made to modify ext_timeslots, or pkt_radio_type, and
the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS
accepts the request and issues a warning to indicate that there is not enough
GDS or PMC resource available.

3-508 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

In this example, the maximum number of DRIs on DHP 4 2 0 at site 7 is changed to 5:

modify_value 7 max_dris 5 dhp 4 2 0

Where: is:
7 location
max_dris value_name
5 new_value
dhp dev_func
4 dev_func_id1
2 dev_func_id2
0 dev_func_id3

System response

COMMAND ACCEPTED

Example 2

This example modifies the value of cic_unblock_thresh when eac_mode is enabled and AMR
or GSM HR is unrestricted for an AXCDR at site 0.

modify_value 0 cic_unblock_thresh 250 AXCDR 1 2 8

Where: is:
0 location
cic_unblock_thresh value_name
250 new_value
AXCDR dev_func
1 dev_func_id1
2 dev_func_id2
8 dev_func_id3

System response

COMMAND ACCEPTED

68P02901W23-T 3-509
Jan 2010
Examples Chapter 3: Device/function related commands

Example 3

This example disables eac_mode whether AMR HR or GSM HR is enabled or not for an AXCDR
at site 0.

modify_value 0 eac_mode no AXCDR 1 2 8

Where: is:
0 location
eac_mode value_name
no new_value
AXCDR dev_func
1 dev_func_id1
2 dev_func_id2
8 dev_func_id3

System response

WARNING: Disabling enhanced auto connect mode will terminate all active
calls through this Associated RXCDR from the BSC, and configure the CIC Ater
assignments as for Auto Connect mode
Are you sure (y/n) y
COMMAND ACCEPTED

Example 4

This example enables eac_mode with cic_validation enabled and amr_bss_half_rate_enabled

and gsm_bss_half_rate_enabled disabled for an AXCDR at site 0.

modify_value 0 eac_mode yes AXCDR 1 2 8

Where: is:
0 location
eac_mode value_name
yes new_value
AXCDR dev_func
1 dev_func_id1
2 dev_func_id2
8 dev_func_id3

3-510 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

WARNING: AMR and GSM Half Rate is currently disabled at this BSC.
COMMAND ACCEPTED

Example 5

In this example, the frequency_type for a Horizon II macro cabinet is modified from
EGSM90000 to EGSM900 and DCS1800 for Dual band on a single cabinet:

modify_value 7 frequency_type 6 CAB 0 0 0

Where: is:
7 location
frequency_type value_name
6 new_value
CAB dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

COMMAND ACCEPTED

Example 6

This example modifies the type of cabinet 15 0 0 from Horizon macro extension to Horizon II
mini extension, where the current cabinet has no dependent devices.
modify_value 5 cabinet_type 27 CAB 15 0 0

Where: is:
5 location
cabinet_type value_name
27 new_value
CAB dev_func
15 dev_func_id1
0 dev_func_id2
0 dev_func_id3

68P02901W23-T 3-511
Jan 2010
Examples Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED

Example 7

This example modifies pkt_radio_type from 1 to 3 with a warning that not enough GDS
resources handle PDTCHs.

modify_value 1 pkt_radio_type 3 rtf 1 1

Where: is:
1 location
pkt_radio_type value_name
3 new_value
rtf dev_func
1 dev_func_id1
1 dev_func_id2

System response

Enter the rtf_ds0_count: 6

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.
Are you sure (y=yes, n=no)? y

COMMAND ACCEPTED: WARNING: Insufficient GDS resources available

for all PDTCHs on the PCU.

3-512 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 8

This example modifies max_mtls values to 31 on GPROC3-2.

modify_value 0 max_mtls 31 LCF 0 0 0

Where: is:
0 location
max_mtls value_name
31 new_value
LCF dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

WARNING: HSP LCF equipage may trigger GPROC preemption.

Are you sure (y=yes,n=no)? y
COMMAND ACCEPTED.
WARNING: Resources are not currently available.
Parent entity must be manually reset before change takes effect.

Example 9

This example attempts to modify the max_mtls value to 31 on GPROC3.

modify_value 0 max_mtls 31 LCF 1 0 0

Where: is:
0 location
max_mtls value_name
31 new_value
LCF dev_func
1 dev_func_id1
0 dev_func_id2
0 dev_func_id3

68P02901W23-T 3-513
Jan 2010
Examples Chapter 3: Device/function related commands

System response

WARNING: HSP LCF equipage may trigger GPROC preemption.

Are you sure (y=yes,n=no)? y
COMMAND ACCEPTED.
WARNING: Resources are not currently available.
Parent entity must be manually reset before change takes effect.

Example 10

This example attempts to increase the max_gsls value from 0 on LCF which has already
managed HSP MTL.

modify_value 0 max_gsls 1 LCF 1 0 0

Where: is:
0 location
max_mtls value_name
1 new_value
LCF dev_func
1 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

COMMAND REJECTED: Insufficient GPROC timeslots available

3-514 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 11

This example attempts to increase the max_cbls value from 0 on LCF which has already
managed HSP MTL.

modify_value 0 max_cbls 1 LCF 1 0 0

Where: is:
0 location
max_cbls value_name
1 new_value
LCF dev_func
1 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

COMMAND REJECTED: Insufficient GPROC timeslots available

Example 12

This example attempts to increase the max_opls value from 0 on LCF which has already
managed HSP MTL.

modify_value 0 max_opls 1 LCF 1 0 0

Where: is:
0 location
max_opls value_name
1 new_value
LCF dev_func
1 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

COMMAND REJECTED: Insufficient GPROC timeslots available

68P02901W23-T 3-515
Jan 2010
Examples Chapter 3: Device/function related commands

Example 13

This example modifies the base IP address of the PCU.

modify_value 0 base_ip_address 10.3.16.36 pcu 0

Where: is:
0 location
base_ip_address value_name
10.3.16.36 new_value
pcu dev_func
0 dev_func_id1

System response

Enter the GDS subnet mask: 255.255.192.0

WARNING: Changing base_ip_address will cycle device PCU.
Are you sure (y=yes,n=no)? y
COMMAND ACCEPTED

Example 14

This example modifies the subnet mask of the PCU.

modify_value 0 gds_subnet_mask 255.255.255.22 pcu 0

Where: is:
0 location
gds_subnet_mask value_name
255.255.255.22 new_value
pcu dev_func
0 dev_func_id1

System response

WARNING: Changing gds_subnet_mask will cycle device PCU.

Are you sure (y=yes,n=no)? y
COMMAND ACCEPTED

3-516 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 15

In this example, the operator attempts to enable opto alarm (out of range 1-6) through
modify_val for EAS equipped to Horizon II microcabinet.

modify_value 8 opto_reporting on eas 0 0 0

Where: is:
8 location
opto_reporting value_name
on new_value
eas dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

Enter the opto(s) whose state changes should now be reported: 3 6 9

ERROR: Range Error, parameter number: 3.

Example 16

This example modifies the base IP address of the PSI.

modify_value 0 base_ip_address 10.3.16.36 psi 1

Where: is:
0 location
base_ip_address value_name
10.3.16.36 new_value
psi dev_func
1 dev_func_id1

System response

Enter the subnet mask: 255.255.255.0

WARNING: Changing base IP address, subnet mask will cycle device ETH.
Are you sure (y=yes,n=no)? y
COMMAND ACCEPTED

68P02901W23-T 3-517
Jan 2010
Examples Chapter 3: Device/function related commands

Example 17

This example sets the number of extended PDCHs to 3 for RTF 5,11 in site 3.

modify_val 3 ext_pdchs 3 rtf 5 11

Where: is:
3 location
ext_pdchs value_name
3 new_value
rtf dev_func
5 dev_func_id1
11 dev_func_id2

System response

COMMAND ACCEPTED

Example 18

This example attempts to set ext_timeslots for the RTF (5,11) to 2 when RTF 5,11 is configured
for Extended GPRS and ext_pdchs is set to 3.

modify_value 5 ext_timeslots 2 rtf 5 11

Where: is:
5 location
ext_timeslots value_name
2 new_value
rtf dev_func
5 dev_func_id1
11 dev_func_id2

System response

COMMAND REJECTED: Value of ext_timeslots shall be >= ext_pdchs for ERC GPRS RTF

3-518 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 19

This example attempts to change pkt_radio_type = None for the RTF (5,11) when ext_pdchs in
the RTF is set to 3.

modify_value 5 pkt_radio_type None rtf 5 11

Where: is:
5 location
pkt_radio_type value_name
None new_value
rtf dev_func
5 dev_func_id1
11 dev_func_id2

System response

COMMAND REJECTED: Value of ext_pdchs shall be 0 when pkt_radio_type = NONE for

the RTF

Example 20

{26638}

This example attempts to modify the ip_address of GBL 0 to 192.178.11.23 out of SYSGEN
mode.

modify_value pcu ip_address 192.178.11.23 gbl 0

Where: is:
pcu location
ip_address value_name
192.178.11.23 new_value
gbl dev_func
0 dev_func_id1

68P02901W23-T 3-519
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Enter the subnet mask for Gb Ethernet:

Enter the default gateway for Gb Ethernet:

WARNING: This will cause GBL 0 0 0 at the specified PCU to reinitialize.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

Example 21

{26638}

This example attempts to modify the subnet_mask of GBL 0 to 255.255.255.240 out of SYSGEN
mode.

modify_value pcu subnet_mask 255.255.255.240 gbl 0

Where: is:
pcu location
subnet_mask value_name
255.255.255.240 new_value
gbl dev_func
0 dev_func_id1

System response

WARNING: This will cause GBL 0 0 0 at the specified PCU to reinitialize.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

3-520 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 22

{26638}

This example attempts to modify the udp_port of GBL 0 to 1067 out of SYSGEN mode.

modify_value pcu udp_port 1067 gbl 0

Where: is:
pcu location
udp_port value_name
1067 new_value
gbl dev_func
0 dev_func_id1

System response

WARNING: This will cause GBL 0 0 0 at the specified PCU to reinitialize.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

Example 23

{26638}

This example attempts to modify the gateway of GBL 0 to 192.168.10.254 out of SYSGEN mode.

modify_value pcu gateway 192.168.10.254 gbl 0

Where: is:
pcu location
gateway value_name
192.168.10.254 new_value
gbl dev_func
0 dev_func_id1

68P02901W23-T 3-521
Jan 2010
Examples Chapter 3: Device/function related commands

System response

WARNING: This will cause GBL 0 0 0 at the specified PCU to reinitialize.

Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

Example 24

{26638}

This example attempts to modify the value of start_ts to 2 of GBL 0 when the Gb over IP feature
is unrestricted and the gb_mode parameter is set to 1.

modify_value pcu start_ts 2 gbl 0

Where: is:
pcu location
start_ts value_name
2 new_value
gbl dev_func
0 dev_func_id1

System response

COMMAND REJECTED: Can not modify this value when gb_mode is 1(Static IP mode).

3-522 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 25

{34282}

This example modifies the value of the cpu_threshold parameter to 70 for LCF 1 0 0 at site 0.

modify_value 0 cpu_threshold 70 LCF 1 0 0

Where: is:
0 location
cpu_threshold value_name
70 new_value
LCF dev_func
1 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

COMMAND ACCEPTED

Example 26

{34371G}

This example attempts to modify the bbu_attached parameter from 0 (No) to 1(Yes) on the
Horizon II macro site.

modify_value 23 bbu_attached 1 BTP 0 0 0

Where: is:
23 location
bbu_attached value_name
1 new_value
BTP dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

Enter BBU port for inter-BBU connection: 2

COMMAND ACCEPTED

68P02901W23-T 3-523
Jan 2010
Examples Chapter 3: Device/function related commands

Example 27

{34371G}

This example attempts to modify the slot_num parameter of CTU4 DRI 0 0 0 from 1 to 2.

modify_value 23 slot_num 2 DRI 0 0 0

Where: is:
23 location
slot_num value_name
2 new_value
DRI dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

COMMAND ACCEPTED: WARNING: This change has been propagated to all

associated DRIs in (R)CTU4.

Example 28

{34371G}

This example attempts to modify the lowest_arfcn parameter of (R)CTU4 DRI 0 0 0.

modify_value 23 lowest_arfcn 20 DRI 0 0 0

Where: is:
23 location
lowest_arfcn value_name
20 new_value
DRI dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

COMMAND ACCEPTED

3-524 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 29

{34371G}

This example attempts to modify the tx0_dri_density parameter of (R)CTU4 DRI 0 0 0 from 1 to
2. This results in DRI 0 1 0 being auto-equipped.

modify_value 23 tx0_dri_density 2 DRI 0 0 0

Where: is:
23 location
tx0_dri_density value_name
2 new_value
DRI dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

Enter the 2nd DRI id of the 1st associated DRI of the Tx Port: 1
Enter the 1st and 2nd RTF id:

COMMAND ACCEPTED

Example 30

{34371G}

This example attempts to modify the antenna_select parameter of (R)CTU4 DRI 0 0 0 in the
(R)CTU4 which operates on the 4(2+2) density mode. After the modification, the parameter
of all associated DRIs in (R)CTU4 are modified successfully.

modify_value 7 antenna_select 2 DRI 0 0 0

Where: is:
7 location
antenna_select value_name
2 new_value
DRI dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

68P02901W23-T 3-525
Jan 2010
Examples Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED: WARNING: This change has been propagated to all

associated DRIs in (R)CTU4.

Example 31

{34371G}

This example attempts to modify the fm_cell_type parameter of (R)CTU4 DRI 0 0 0 in the
(R)CTU4 which operates on the 4(2+2) density mode. After the modification, the parameter
of all associated DRIs in (R)CTU4 are modified successfully.

modify_value 23 fm_cell_type 2 DRI 0 0 0

Where: is:
23 location
fm_cell_type value_name
2 new_value
DRI dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

COMMAND ACCEPTED: WARNING: This change has been propagated to all

associated DRIs in (R)CTU4.

3-526 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 32

{34371G}

This example attempts to modify the dri_density parameter of (R)CTU4 DRI 0 0 0.

modify_value 23 dri_density 2 DRI 0 0 0

Where: is:
23 location
dri_density value_name
2 new_value
DRI dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

COMMAND REJECTED: Invalid element for a RH.

Example 33

{35200G}

This example attempts to modify the tx0_dri_density parameter of (R)CTU4 DRI 0 0 0 from 2
to 4 when CTU8Opt is restricted.

modify_value 23 tx0_dri_density 4 DRI 0 0 0

Where: is:
23 location
tx0_dri_density value_name
4 new_value
DRI dev_func
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

68P02901W23-T 3-527
Jan 2010
References Chapter 3: Device/function related commands

System response

Enter the 2nd DRI id of the 1st associated DRI of the Tx Port: 2
Enter the 1st and 2nd RTF id:
Enter the 2nd DRI id of the 2nd associated DRI of the Tx Port: 3
Enter the 1st and 2nd RTF id:
COMMAND REJECTED: Received a request to modify a restricted optional feature.

Example 34

{36039G}

This example attempts to change the equipment attribute of mms 8 1, when the Abis auto
swap feature (abisautoswapOpt) is enabled.

modify_value 0 terr_or_sate 1 mms 8 1

Where: is:
0 location
terr_or_sate value_name
1 new_value
mms dev_func
8 mms_id1
1 mms_id2

System response

COMMAND ACCEPTED

References

Related commands

disp_equipment on page equip on page 3-445 reassign on page 3-537

3-315

3-528 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference nacc_nc2_enabled

nacc_nc2_enabled

Description

The per-BSS element nacc_nc2_enabled allows the customer to enable or disable the NC2
mode of NACC.

This element can be accessed and updated both in and out of Sysgen mode.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element nacc_nc2_enabled <value> <location>

Display command string

disp_element nacc_nc2_enabled <location>

Values

Value type Boolean

Valid range 0 to 1
0 Disables the NC2 mode of NACC.
1 Enables the NC2 mode of NACC.
Default value 0

68P02901W23-T 3-529
Jan 2010
page Chapter 3: Device/function related commands

page

Description

The page command enables or disables pagination for display commands. The page command
can also specify the number of lines displayed per page for display commands.

NOTE
The page command applies only to the current session and the current processor
board (GPROC, GPROC2, or GPROC3). Setting it from an OMC-R rlogin does not
affect any other OMC-R rlogins or TTY MMI logins. Setting it from a TTY MMI login
does not affect any other TTY MMI logins or OMC-R rlogins. At every new login, it
is reset to off.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

page <input>

Input parameter

input

Valid input formats are as follows:

Input Action Range

off Disables pagination. No range. This is the default value.
<lines per page> Enables pagination and sets the Any numeric value between 20 and
number of lines displayed per page. 255.
none Displays current page setting. Not applicable.

3-530 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

This example shows that pagination has been enabled, and displays show 30 lines per page.

page 30

Example 2

This example shows that pagination has been disabled.

page off

Example 3

This example shows no line number entered. The current setting is displayed.

page 25

References

Related commands

The page command affects the output from the following commands.

assess on page 3-54 disp_act_alarm on page 3-246 disp_bss on page 3-249

disp_cal_data on page 3-253
disp_cell_status on page
3-267
disp_dte on page 3-291
disp_gsm_cells on page 3-350
disp_link on page 3-362
disp_neighbor on page 3-379
disp_rtf_channel on page
3-416
disp_stat_prop on page 5-26
disp_traffic on page 3-436
state on page 3-576
disp_cbch_state on page
3-257
disp_csfp on page 3-284
disp_enable_stat on page 5-14
disp_hdlc on page 3-353
disp_link_usage on page
3-364
disp_options on page 3-393
disp_rtf_path on page 3-422
disp_throttle on page 3-427
man on page 4-8
status_mode on page 3-592
disp_cell on page 3-261
disp_csfp_status on page
3-288
disp_equipment on page
3-315
disp_hopping on page 3-356
disp_mms_ts_usage on page
3-366
disp_processor on page 3-407
disp_stats on page 5-39
disp_trace_call on page 3-432
site_audit on page 3-568

68P02901W23-T 3-531
Jan 2010
query_audits Chapter 3: Device/function related commands

query_audits

Description

The query_audits command performs two different functions. The first is to provide a list of all
information for all audits for a specific device at the customer site. The second function provides
a list of the audits in progress for a specific device at the customer site.

The query_audits supports display of swap_type on TDM devices at location 0 (BSC or RXCDR).

The short option displays the state of all audits for a specific device at a site.

The long option displays the information for all of the audits for a specific device at the site.
The information includes the state and schedule information.

There are only three possible System Responses to a query_audits command:

The display of results.

A COMMAND REJECTED message, with the reason (for example, the device is not in
the database).

ERROR.

The ERROR response is followed by a display of the error description from the following list:

Audit not available for unequipped devices.

Audit can only be executed on expanded TDM configuration.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites An operator at the OMC-R must rlogin to a site before an
audit can be performed.
To audit a PCU site, the GPRS feature must be unrestricted.

Format

Syntax

query_audits <location> <audit_type> <device_name> <device_id1>

<device_id2> <device_id3>

3-532 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Input parameters

location

Specifies the audit location:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

audit_type

Specifies the amount of information required.

short Displays all the audits in progress for a specific device at a customer site.
long Lists the state and schedule information for all the audits for the
specified device.

device_name

The name that uniquely identifies the device. The valid device names are:

{34371G} BBU DHP GPROC TDM

BSP DRI KSW
BTP GCLK MSI

The following device can be audited at a PCU site using this command:

DPROC MSI PSP

device_id1

First device identifier. The range of values is 0 to 99.

device_id2

Second device identifier. The range of values is 0 to 99.

device_id3

Third device identifier. The range of values is 0 to 99.

NOTE
Not all devices require all three device IDs.

68P02901W23-T 3-533
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

In the following example, the query lists an audit that is idle for a KSW device at the BSC
with ID 0 0 0:

query_audits 0 long ksw 0 0 0

Where: is:
0 location
long audit_type
ksw device_name
0 device_id1
0 device_id2
0 device_id3

System response

Device: KSW Device id: 0 0 0

Start Time: 00:00 End Time: 00:00 Interval: 01:00
Audit Type: SAFE Idle/Active State: IDLE
On/Off State: Site Audit: ON Cage Audit: ON Device Audit: ON

Device: KSW Device id: 0 0 0

Start Time: 02:00 End Time: 04:00 Interval: 00:15
Audit Type: INT_LPBK Idle/Active State: IDLE
On/Off State: Site Audit: ON Cage Audit: ON Device Audit: ON

Example 2

The following example lists the audits in progress on the PCU MSI device:

query_audits PCU short MSI 0

Where: is:
PCU location
short audit_type
MSI device_name
0 device_id1

3-534 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Device: MSI Device id: 0 0 0

Audit Type: SAFE Idle/Active State: IDLE
On/Off State: Site Audit: ON Cage Audit: ON Device Audit: ON

Example 3

The following example lists in long format, the audits in progress on the MSI device at the
first PCU:

query_audits PCU_0 long MSI 0

Where: is:
PCU_0 location (PCU site 0)
long audit_type
MSI device_name
0 device_id1

System response

Device: MSI Device id: 0 0 0

Start Time: 00:00 End Time: 00:00 Interval: 00:10
Audit Type:SAFE Idle/Active State:IDLE
On/Off State: Site audit:ON Cage audit:ON Device audit:ON

Example 4

The following example lists in long format, the audits in progress on the tdm device:

query_audit 0 long tdm 0

Where: is:
0 location
long audit_type
tdm device_name
0 device_id1

68P02901W23-T 3-535
Jan 2010
References Chapter 3: Device/function related commands

System Response

Device: TDM Device id : 0 0 0

Start Time: 01:00 End Time: 01:00 Interval: 00:00
Audit Type: SAFE Idle/Active State: IDLE
On/Off State: Site Audit: ON Cage Audit: ON Device Audit: ON

Device: TDM Device id : 0 0 0

Start Time: 03:00 End Time: 03:00 Interval: 00:00
Audit Type: SWAP_TEST Idle/Active State: IDLE
On/Off State: Site Audit: ON Cage Audit: ON Device Audit: ON

Example 5

{34371G}

This example query audits on a BBU device.

query_audits 23 short BBU 1 0 0

Where: is:
23 location
short audit_type
BBU device_name
1 device_id1
0 device_id2
0 device_id3

System Response

Device: BBU Device id : 1 0 0

Audit Type: SAFE Idle/Active State: IDLE
On/Off State: Site Audit: ON Cage Audit: ON Device Audit: ON

References

Related commands

cage_audit on page 3-58 chg_audit_sched on page 3-76 device_audit on page 3-230

site_audit on page 3-568

3-536 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference reassign

reassign

Description

The reassign command changes the assignment of a child_dev device from its current
parent_func to a new parent_func.

For example, a DRI can be reassigned from one DHP, BTP, or BTF to another DHP, BTP, or BTF.
The reassign command removes the device from service until the command is accepted.

If the DRI is locked after it has been reassigned, the DRI is assigned to the least loaded GPROC
when the DRI is unlocked.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites DRIs can only be assigned to GPROCs in the same cage as
the DRI.
A site device can be reassigned whether in Sysgen mode or
not in Sysgen mode. All other devices must be reassigned
when not in Sysgen mode.
All GPROCs at the BSC (including the BSP) must be stable
for at least five consecutive minutes since any GPROC has
been transitioned.
No BTS sites can be in the process of code loading.

Format

Syntax

reassign <location> <child_dev_name> <child_dev_id_1>

<child_dev_id_2><child_dev_id_3> [<to>] <parent_func_name>
<parent_func_id_1><parent_func_id_2> <parent_func_id_3>

Input parameters

location

Specifies the location of the GPROC from which control of a DRI is to be moved. The values are:

0 or bsc BSC
1 - 140 BTS
pcu, pcu_0 to pcu_2 PCU

child_name

68P02901W23-T 3-537
Jan 2010
Example Chapter 3: Device/function related commands

Literal that uniquely identifies the device. Current values are:

CBL DRI GSL MTL SITE

child_dev_id_1

The first child device identifier. Values are in the range 0 to 5.

child_dev_id_2

The second child device identifier. Values are in the range 0 to 24.

child_dev_id_3

The third child device identifier. Valid value is 0.

to

Optional text that can be entered to make the command more readable.

parent_func_name

The literal that defines where the device or function is reassigned. Current values are:

BTP Apply to DRIs

BTF
DHP
LCF Applies to: CBL, GSL, MTL, SITE

parent_func_id_1

Values are dependent on the device or function type.

parent_func_id_2

Values are dependent on the device or function type.

parent_func_id_3

Values are dependent on the device or function type.

Example

Example 1

In this example, DRI 0 7 0 is reassigned from its current GPROC at BTS 8 to DHP 14 2 0:

reassign 8 dri 0 7 0 to dhp 14 2 0

Where: is:
8 location
dri child_dev_name
0 dri_id_1

Continued

3-538 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Where: is:
7 dri_id_2
0 dri_id_3
to option text used to make command more readable.
dhp parent_func_name
14 parent_func_id_1
2 parent_func_id_2
0 parent_func_id_3

System response:

WARNING: This will cause the link to temporarily go out of service.

Are you sure (y=yes,n=no)? y

Example 2

In this example, HSP MTL is reassigned onto a GPROC32.

reassign 0 MTL 1 0 0 LCF 0 0 0

Where: is:
0 location
MTL child_dev_name
1 child_dev_id_1
0 child_dev_id_2
0 child_dev_id_3
LCF parent_func_name
0 parent_func_id_1
0 parent_func_id_2
0 parent_func_id_3

System response:

COMMAND ACCEPTED

68P02901W23-T 3-539
Jan 2010
Example Chapter 3: Device/function related commands

Example 3

In this example, HSP MTL is reassigned onto a GPROC3.

reassign 0 MTL 1 0 0 LCF 2 0 0

Where: is:
0 location
MTL child_dev_name
1 child_dev_id_1
0 child_dev_id_2
0 child_dev_id_3
LCF parent_func_name
2 parent_func_id_1
0 parent_func_id_2
0 parent_func_id_3

System response

COMMAND REJECTED
Wrong GPROC type, display MTL LCF GPROC type to verify.

Example 4

In this example, HSP MTL is reassigned onto a non HSP LCF on a GPROC3-2.

reassign 0 MTL 1 0 0 LCF 3 0 0

Where: is:
0 location
MTL child_dev_name
1 child_dev_id_1
0 child_dev_id_2
0 child_dev_id_3
LCF parent_func_name
3 parent_func_id_1
0 parent_func_id_2
0 parent_func_id_3

3-540 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

COMMAND REJECTED
Wrong LCF type, display MTL LCF type to verify.

References

Related information

The reassign command does not free the RTF associated with the BUSY-UNLOCKED DRI. The
RTF remains associated with the DRI after reassignment to another GPROC. In circumstances
where the reassignment fails due to catastrophic events, such as hardware failure, the RTF is
freed, one transceiver is available and another is found. Where no standby DRIs are available
and a BCCH RTF is free, a search is made for a DRI which is assigned to the GPROC, which has
the least number of BCCH carrier-implementing DRIs assigned to it.

The main reasons for failure to reassign a DRI:

The destination BTP, BTF, or DHP has reached the maximum number of supportable DRIs.

The DRI or GPROC type is not present or it is in an invalid state.

The DRI is not in the same cage as the destination BTP, BTF, or DHP.

The DRI is not configured due to catastrophic hardware failure.

Related commands

disp_equipment on page equip on page 3-445 modify_value on page 3-507

3-315
disp_processor on page 3-407

68P02901W23-T 3-541
Jan 2010
reattempt_pl Chapter 3: Device/function related commands

reattempt_pl

Description

The reattempt_pl command causes the GCLK to reattempt phase lock. This is permitted only if
the GCLK has previously failed to phase lock.

Security level 3
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.

Format

Syntax

reattempt_pl <location> <gclk_id1>

Input parameters

location

Specifies the location of the GPROC from which control of a DRI is to be moved:

0 or bsc BSC
1 - 140 BTS

gclk_id

The GCLK identifier. The valid values are 0 or 1.

Example

In this example, the GCLK 0 is forced to attempt phase lock.

reattempt_pl bsc 0

Where: is:
bsc location
0 gclk_id

3-542 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

COMMAND ACCEPTED

References

Related command

chg_element on page 3-112.

68P02901W23-T 3-543
Jan 2010
reset_device Chapter 3: Device/function related commands

reset_device

Description

The reset_device command brings a device into service by locking and then unlocking the
device. Additionally, a hard reset is performed if the device supports it.

The following devices support soft resets:

ABSS AXCDR CAB CAGE CBL CIC

COMB CSFP DPROC EAS GBL GCLK
GSL MMS MTL OML OPL PATH
PCU RSL SITE XBL TDM

NOTE
The reset_device command supports the resetting of extension cabinets of type
TCU_2, TCU_6, and HORIZONMACRO_EXT. No other extension cabinet types are
supported.

The following devices support hard reset:

BBU BSP BTP DHP DRI GPROC KSW MSI

{34371G}

NOTE
When a KSW is reset, all calls currently in progress are dropped. Normal call
processing resumes when the KSW is brought back into service.

When this command is entered where an MSI or MMS has an OML, a warning, and a verification
request is presented.

When this command is entered for an ABSS or AXCDR, a warning, and a verification request is
presented.

If the reset_device command is applied to an active GCLK, and the standby GCLK is phase
locked, the system displays an additional warning message.

The system also displays a warning message if the reset_device command is applied to the
GCLK. This action swaps the GCLKs and can cause alarms on other devices. If the reset_site
command is attempted while the system is initializing, the system displays a COMMAND REJECTED:
System still initializing message.

The BSS SW at a BSS enables enhanced capacity mode through reset_device command if the
detected hardware contains only the master and redundant DSW2/DSWXs and not KSW/KSWX.

3-544 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

For remote transcoding BSC sites, CICs are not reset on a per-MMS basis when the BSC is
operating in the dynamic allocation mode.

Security level 2
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites This command is invoked irrespective of whether the
device is locked or unlocked.
Operator actions Respond to the verification prompt that is presented if this
command is used to reset an MSI or MMS with an OML.

Format

General syntax

reset_device <location> <device_name> <device_id1> <device_id2> <device_id3>

Input parameters

location

Specifies the location of the device to have a hard reset performed or toggled to the locked state:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

device_name

Literal that uniquely identifies the device.

device_id1

First device identifier. This definition varies with each device.

device_id2

Second device identifier. This definition varies with each device.

device_id3

Third device identifier. This definition varies with each device.

68P02901W23-T 3-545
Jan 2010
Format Chapter 3: Device/function related commands

CIC syntax

A form of syntax is available for each method of specifying a CIC.

The following CIC syntax applies to local transcoding:

reset_device <location> CIC <cic_num1>

reset_device <location> CIC <cic_num1> TO <cic_num2>

reset_device <location> CIC <mms_id1> <mms_id2>

reset_device <location> CIC <mms_id1> <mms_id2> <timeslot1>

reset_device <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2>

The following CIC syntax applies to remote transcoding:

reset_device <location> CIC <cic_num1>

reset_device <location> CIC <cic_num1> TO <cic_num2>

reset_device <location> CIC <mms_id1> <mms_id2>

reset_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group>

reset_device <location> CIC <mms_id1> <mms_id2> <timeslot1> *

reset_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO

<timeslot2> <group2>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS

CIC

Literal that uniquely identifies the CIC device.

cic_num1

First CIC device number.

cic_num2

Last CIC device number in a range.

mms_id1

First MMS identifier.

3-546 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

mms_id2

Second MMS identifier, or last in a range if TO is used.

timeslot1

First timeslot.

timeslot2

Second timeslot, or last in a range if TO is used.

group1

First group.

group2

Second group.

Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

Examples

Example 1

In this example, the MSI device is locked before the command is invoked. When the
reset_device command is invoked, a hard reset of an MSI device with ID=1 at the BSC is
performed.

reset_device bsc MSI 1

Where: is:
bsc location
MSI device_name
1 dev_id

System response

COMMAND ACCEPTED

68P02901W23-T 3-547
Jan 2010
Examples Chapter 3: Device/function related commands

Example 2

In this example, the GCLK is being reset. This example shows the warning message and the
prompt the system displays whenever the GCLK is reset.

reset_device 0 gclk 0

Where: is:
0 location
gclk device_name
0 dev_id

System Response

This command will cause a swap of the GCLKs.

This may cause alarms on other devices.
Are you sure (y=yes,n=no)? y
COMMAND ACCEPTED

Example 3

This example resets a range of CICs devices, specifying them by their MMS, TS, and group.

reset_device bsc cic 2 1 3 1 TO 5 1

Where: is:
BSC location
CIC CIC (device_name)
2 mms_ id1
1 mms_ id2
3 timeslot 3
1 group 1
5 timeslot 5
1 group 1

System response

COMMAND ACCEPTED

3-548 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 4

This example enables enhanced capacity mode if the master and redundant DSW2/DSWXs
are present.

reset_device 0 TDM 1 0 0

Where: is:
0 location
TDM device_name
1 dev_id1
0 dev_id2
0 dev_id3

System response

COMMAND ACCEPTED

Example 5

This example attempts to enable the enhanced capacity mode if the master and redundant
DSW/DSWX are present.

reset_device 0 TDM

Where: is:
0 location
TDM device_name

System response

COMMAND ACCEPTED

Example 6

This example attempts to enable the enhanced capacity mode if the KSW/KSWX is present.

reset_device 0 TDM

Where: is:
0 location
TDM device_name

68P02901W23-T 3-549
Jan 2010
Examples Chapter 3: Device/function related commands

System response

COMMAND REJECTED: Wrong Hardware configuration detected in the site.

Example 7

{34371G}

This example attempts to reset the standby BTP 1 0 0 and there is a BBU attached to the BTP.

reset_device 23 btp 1 0 0

Where: is:
23 location
btp device_name
1 dev_id1
0 dev_id2
0 dev_id3

System response

WARNING: Associated BBU and DRIs are affected by this command

Are you sure (y=yes,n=no)?y

COMMAND ACCEPTED

Example 8

{34371G}

This example attempts to reset BBU 0 0 0.

reset_device 23 bbu 0 0 0

Where: is:
23 location
bbu device_name
0 dev_id1
0 dev_id2
0 dev_id3

3-550 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

WARNING: Associated DRIs and potential another BBU are affected by this command
Are you sure (y=yes,n=no)?y

COMMAND ACCEPTED

Example 9

{34371G}

This example attempts to reset (R)CTU4 DRI 0 0 0 operating on 4(2+2) density mode.

reset_device 23 DRI 0 0 0

Where: is:
23 location
DRI device_name
0 dev_func_id1
0 dev_func_id2
0 dev_func_id3

System response

WARNING: Associated DRI device is affected by this command

Are you sure (y=yes,n=no)?y

COMMAND ACCEPTED

Example 5

This example attempts to reset a cage and display a confirmed command. A warning about
the cage reset_device is displayed.

reset_device bsc cage 1 0

Where: is:
bsc location
cage device_name
1 dev_id1
0 dev_id2

68P02901W23-T 3-551
Jan 2010
References Chapter 3: Device/function related commands

System response

CAGE 1 This will affect all devices in this CAGE and any associated
Extension CAGEs.
Are you sure (y=yes,n=no)? yes
COMMAND ACCEPTED

References

Related commands

ins_device on page 3-471 lock_device on page 3-478 unlock_device on page 3-645

3-552 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference reset_site

reset_site

Description

The reset_site command selectively reboots available sites without rlogin. Typical scenarios
for selective rebooting include the following:
All sites including BSC.

All sites excluding BSC.

Multiple sites.

Single site.

NOTE
The all_sites, all_bts, and list of site options are only allowed at the BSC and
outside SYSGEN ON mode.

If a site other than the BSC is reset, the terminal being used to enter the command must be
attached to that site GPROC to view the outputs generated during a reset. The reset occurs
even if the terminal is not connected to the affected site.

CAUTION
Commands must be entered within 10 minutes after the MMI-RAM -> prompt displays.
If a command is not entered, the system resets.

Security level 3
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites None
Operator actions Place the system in the SYSGEN ON mode before entering
this command.
The system does not permit resetting all_sites, all_bts or a
list of site options in SYSGEN ON mode.

Format

Syntax

reset_site [<location>]

68P02901W23-T 3-553
Jan 2010
Examples Chapter 3: Device/function related commands

Input parameter

location

Specifies the sites to be reset. Valid values are:

all_sites all sites including BSC

all_bts all sites excluding BSC
bsc BSC (site 0)
bsc, 1 - 100 BSC and multiple sites (1 to 100).
The bsc string must be entered as the first item in a list of
sites. If bsc is included but is not the first item, the command
is rejected.
1 - 140 BTS

pcu or pcu_0 PCU

NOTE
When in SYSGEN ON mode, only the local site is reset.

The command is rejected if 0 is entered for a BSC.

Verification messages

One of the following verification messages issues before execution. The specific message
depends on the value of the location parameter.

WARNING: Command will REBOOT the entire BSS. Are you sure (y=yes, n=no)?
WARNING: Command will REBOOT all BTS sites. Are you sure (y=yes, n=no)?
WARNING: Command will REBOOT the following site(s):18 21 24
Are you sure (y=yes, n=no)?
WARNING: Command will REBOOT site 0 (BSC or RXCDR)
Are you sure (y=yes, n=no)?

Examples

Example 1

In this example, a single site is reset:

reset_site 2

3-554 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Where: is:
2 location

System response

WARNING: Command will REBOOT the following site(s): 2

Are you sure (y=yes, n=no)? y
COMMAND ACCEPTED: WARNING REBOOT SITE: site 2 will reboot now!!

Example 2

In this example, all active BTS sites are reset:

reset_site all_bts

Where: is:
all_bts location

System response

WARNING: Command will REBOOT all BTS sites.

Are you sure (y=yes, n=no)?y
SITE REBOOT STATUS
---- ------ ------
5 OUT OF SERVICE: reset_site request is discarded
7 RESET REQUEST IS IN PROGRESS
9 RESET REQUEST IS IN PROGRESS
10 OUT OF SERVICE: reset_site request is discarded
11 OUT OF SERVICE: reset_site request is discarded
15 OUT OF SERVICE: reset_site request is discarded
20 RESET REQUEST IS IN PROGRESS
25 RESET REQUEST IS IN PROGRESS
30 RESET REQUEST IS IN PROGRESS
40 RESET REQUEST IS IN PROGRESS

68P02901W23-T 3-555
Jan 2010
References Chapter 3: Device/function related commands

References

Related information

If the operator is logged in to a non-BSC site and attempts to reset other sites, the command
aborts and the following error message displays:

COMMAND REJECTED: current site is not authorized to reboot other site(s). Log-in
to BSC.

The following command examples show various command entry formats and the location from
where the commands must be entered:

Command syntax Site

reset_site all_sites BSC
reset_site all_bts BSC
reset_site bsc BSC
reset_site 15 5 25 0 2 BSC
reset_site 15, 5, 25, 0, 2 BSC
reset_site 1 BSC or site 1
reset_site bsc,21,17,3,0 BSC
reset_site BSC or local site

The MMI TTY displays, on success, one of the following statuses for each site requested:
BSC (20 seconds) TIMEOUT: while waiting to receive ACK message from this site

OUT OF SERVICE: reset_site request is discarded

NOT EQUIPPED: reset_site request is discarded

RESET REQUEST IS IN PROGRESS

OUT OF RANGE: currently this site is not supported by CM Database

Related command

sysgen_mode on page 3-603

3-556 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference set_full_power

set_full_power

Description

The set_full_power command turns the Full Power mode on or off for a single cell or all
cells in a site.

The Full Power mode directs a specified cell or all cells at a site to operate at the system's
maximum power for a specified length of time.

If a site is specified when the set_full_power command is entered, a status listing of all of the
cells affected by the command are displayed.

Security level 4
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

set_full_power [<cell_desc>] on <minutes>

set_full_power [<cell_desc>] off

set_full_power <location> on <minutes>

set_full_power <location> off

Input parameters

cell_desc

The GSM cell ID of the cell at which full power is to be set preceded by cell_number=.

The format for the GSM cell ID depends on:

The system being used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

68P02901W23-T 3-557
Jan 2010
Examples Chapter 3: Device/function related commands

The name of the cell created using the cell_name command is entered in place of the
cell_number. When the cell name is entered, it must be preceded by cell_name= and be placed
inside double quotation marks.

location

Specifies the location.

0 or bsc BSC
1 - 140 BTS

on/off

Select turning on and off Full Power mode.

minutes

The length of time for the specified cell or location to operate at full power. The valid range is
1 to 1440.

Examples

Example 1

The following example turns on the Full Power mode for GSM cell ID 5 4 3 2 1 31967 45988 for
45 minutes. The ID number is in the seven parameter format.

set_full_power cell_number=5 4 3 2 1 31967 45988 on 45

Where: is:
5 4 3 2 1 31967 45988 cell_number
on turn Full Power mode on.
45 length of time Full Power mode is turned on.

The example below shows the same cell number in four parameter format:

set_full_power cell_number=543 21 31967 45988 on 45

Where: is:
543 21 31967 45988 cell_number
on turn Full Power mode on.
45 length of time Full Power mode is turned on.

System response

COMMAND ACCEPTED

3-558 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 2

The following example turns off the Full Power mode for GSM cell ID 5 4 3 2 1 31967 45988:

set_full_power cell_number=5 4 3 2 1 31967 45988 off

Where: is:
5 4 3 2 1 31967 45988 cell_number.
off turn Full Power mode off.

System response

COMMAND ACCEPTED

Example 3

The following example turns on the Full Power mode for all cells at site 5 for 45 minutes:

set_full_power 5 on 45

Where: is:
5 location.
on turn Full Power mode on.
45 length of time the Full Power mode is turned on.

System response

Full Power mode set ON for CELL ID = 5 4 3 2 1 31987 45977

Full Power mode set ON for CELL ID = 5 4 3 2 1 31987 45978

Example 4

The following example turns off the Full Power mode for all cells at site 5.

set_full_power 5 off

Where: is:
5 location
off turn Full Power mode off.

68P02901W23-T 3-559
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Full Power mode set OFF for CELL ID = 5 4 3 2 1 31987 45977

Full Power mode set OFF for CELL ID = 5 4 3 2 1 31987 45978

Example 5

In this example, the affected cell is identified using the cell_name london-south:

set_full_power cell_name=london-south on 45

Where: is:
london-south cell_name
on turn Full Power mode on.
45 length of time Full Power mode is turned on.

System response

COMMAND ACCEPTED

3-560 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference set_relay_contact

set_relay_contact

Description

The set_relay_contact command specifies the relay state for an EAS device when the device is
Busy-Unlocked.

When equipping an EAS device, the physical wiring of each relay must be specified. These
specifications describe whether the relay is open or closed when the relay is deactivated.

All relays are deactivated on site initialization. Once the EAS device is Busy-Unlocked, the relay
state can be controlled by use of the set_relay_contact command.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The EAS device must be equipped.
The physical EAS switches must be manually set to match
the software settings specified.

Format

Syntax

set_relay_contact <location> <device_id> <relay_number> <contact_setting>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS

device_id

Specifies the device ID of the specific PIX card associated with an EAS device:

0 to 7 InCell sites
0 to 15 M-Cell sites

68P02901W23-T 3-561
Jan 2010
Examples Chapter 3: Device/function related commands

relay_number

Specifies the physical relay number to be set (1 to 4).

contact_setting

open or 0 open the relay

closed or 1 close the relay

Examples

Example 1

For EAS 0 located at the BSC, set relay 4 to be closed circuit:

set_relay_contact bsc 0 4 closed

Where: is:
bsc location
0 device_id
4 relay_number
closed contact_setting

Example 2

For EAS 0 located at the BSC, set relay 2 to be open circuit:

set_relay_contact bsc 0 2 0

Where: is:
bsc location
0 device_id
2 relay_number
0 contact_setting

References

Related command

equip on page 3-445.

3-562 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference shutdown_device

shutdown_device

Description

The shutdown_device command non-intrusively locks a specific device from further use.

The following devices can be shut down with this command:

CIC DRI MPRT MTL

The effect of this command is different for each type of specified device:
For DRIs, the device is locked when the specified time expires.

If there are no active calls on the DRI, the shutdown_device command locks the DRI
immediately.

If there are active calls, no new calls are allowed on the DRI, but no calls are handed off
until the shutdown timer expires. At this time, the resource is freed, and calls are forced
to move to another carrier in the same cell only. If there are no free carriers in the cell,
the call is dropped.

For MTLs, the time parameter is ignored and the device is locked immediately.

For remote transcoding BSC sites, CICs are not shutdown on a per-MMS basis when the
BSC is operating in the dynamic allocation mode.

Security level 3
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites This command is not allowed while in SYSGEN ON mode.
This command is only valid when the device is in the
UNLOCKED state. This command has no effect on an
already locked device.
Operator actions Unlock the device to be shut down before entering this
command.

Format

General syntax

shutdown_device <location> <device_name> <device_id1> <device_id2>

<device_id3><seconds> [wait <seconds>]

68P02901W23-T 3-563
Jan 2010
Format Chapter 3: Device/function related commands

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS

device_name

Literal that uniquely identifies the device.

device_id1

First device identifier. This parameter is device-dependent.

device_id2

Second device identifier. This parameter is device-dependent.

device_id3

Third device identifier. This parameter is device-dependent.

seconds

The time limit on the transition in seconds. This parameter is device-dependent. The maximum
time limit cannot exceed 900 seconds (15 minutes).

wait

The period the system should wait before blocking a busy device.

NOTE
The wait parameter is optional for all devices except the CIC. It is required for the
CIC device.

CIC syntax

A form of syntax is available for each method of specifying a CIC.

The following CIC syntax applies to local transcoding:

shutdown_device <location> CIC <cic_num1> wait <seconds>

shutdown_device <location> CIC <cic_num1> TO <cic_num2> wait <seconds>

shutdown_device <location> CIC <mms_id1> <mms_id2> wait <seconds>

shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> wait <seconds>

shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2>wait

<seconds>

3-564 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

The following CIC syntax applies to remote transcoding:

shutdown_device <location> CIC <cic_num1> wait <seconds>

shutdown_device <location> CIC <cic_num1> TO <cic_num2> wait <seconds>

shutdown_device <location> CIC <mms_id1> <mms_id2> wait <seconds>

shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> wait

<seconds>

shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> * wait <seconds>

shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO

<timeslot2> <group2> wait <seconds>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS

CIC

Literal that uniquely identifies the CIC device.

cic_num1

First CIC device number.

cic_num2

Last CIC device number in a range.

mms_id1

First MMS identifier.

mms_id2

Second MMS identifier, or last in a range if TO is used.

timeslot1

First timeslot.

timeslot2

Second timeslot, or last in a range if TO is used.

group1

First group.

group2

Second group.

68P02901W23-T 3-565
Jan 2010
Examples Chapter 3: Device/function related commands

Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

wait

The period the system should wait before blocking a busy device.

NOTE
The wait parameter is always required for the CIC device.

Examples

Example 1

The following example locks a DRI with the IDs 1 2 at site 3 with a time limit of 20 seconds:

shutdown_device 3 dri 1 2 0 20

Where: is:
3 location
dri device_name
1 device_id1
2 device_id2
0 device_id3
20 seconds

System response

COMMAND ACCEPTED

3-566 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 2

This example shuts down a range of CICs (remote transcoding), specifying them by their MMS,
TS, and group, and waiting 5 seconds before blocking a busy device.

shutdown_device bsc cic 2 1 3 1 TO 5 1 wait 5

Where: is:
BSC location
CIC device_name
2 First MMS id
1 Second MMS id
3 Timeslot 3
1 Group 1
5 Timeslot 5
1 Group 1
wait Mandatory for CIC
5 wait period

System response

COMMAND ACCEPTED

References

Related commands

disp_equipment on page equip on page 3-445 lock_device on page 3-478

3-315
state on page 3-576 state on page 3-576 unlock_device on page 3-645

68P02901W23-T 3-567
Jan 2010
site_audit Chapter 3: Device/function related commands

site_audit

Description

The site_audit command initiates all audits for all devices at the customer site. It also allows
the suspension or resumption of all audits at a specific site.

If the GPRS feature is unrestricted, this command supports a GPRS PCU.

Using the site_audit off command suspends all audits. Using the site_audit on command
resumes all audits.

There are only two possible System Responses to a site_audit command:

The display of results.

ERROR.

The ERROR response is followed by a display of the error description from the following list:

Audit not available, audits turned off for site.

Audits already turned on for this site.

Audits already turned off for this site.

SAP internal error.

NOTE
The error messages listed are specific to a SITE. Devices listed within the SITE can
also generate messages specific to the device. For a list of these messages, see
device_audit. Only one audit is run at a time.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites An operator at the OMC-R must rlogin to a site before an
audit can be performed.
This command is not allowed while in SYSGEN ON mode.

Format

Syntax

site_audit <location> [<control>]

3-568 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Input parameters

location

Specifies the audit location:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

control

Audit status

on Resumes all audits at a specific site.

off Suspends all audits at a specific site.

Examples

Example 1

The following example executes audits for all devices at the BSC:
site_audit 0

Where: is:
0 location

System response

Device: KSW Device id: 0 0 0

Year: 1994 Month: 11 Day: 12 Hour: 1 Min: 22 Sec: 55 MSec: 10
Audit Type: SAFE Result: AUDIT NOT SUPPORTED/AVAILABLE
Device: KSW Device id: 0 0 0,
Year: 1994 Month: 11 Day: 12 Hour: 1 Min: 22 Sec: 55 MSec: 30
Audit Type: INT_LPBK Result: AUDIT NOT SUPPORTED/AVAILABLE
Device: MSI Device id: 1 0 0

68P02901W23-T 3-569
Jan 2010
Examples Chapter 3: Device/function related commands

Year: 1994 Month: 11 Day: 12 Hour: 1 Min: 22 Sec: 55 MSec: 40

Audit Type: SAFE Result: PASS
Device: DRI Device id: 0 1 0
Year: 1994 Month: 11 Day: 12 Hour: 1 Min: 22 Sec: 55 MSec: 40
Audit Type: SAFE Result: PASS
Device: DRI Device id: 0 0 0
Year: 1994 Month: 11 Day: 12 Hour: 1 Min: 22 Sec:55 MSec: 100
Audit Type: SAFE Result: PASS
Device: GCLK Device id: 0 0 0
Year: 1994 Month: 11 Day: 12 Hour: 1 Min: 22 Sec: 55 MSec: 100
Audit Type: SAFE Result: PASS
Device: GPROC Device id: 0 0 0
Year: 1994 Month: 11 Day: 12 Hour: 1 Min: 22 Sec: 55 MSec: 280
Audit Type: SAFE Result: PASS
Device: GPROC Device id: 1 0 0
Year: 1994 Month: 11 Day: 12 Hour: 1 Min: 22 Sec: 55 MSec: 420
Audit Type: SAFE Result: ERROR
ERROR: Audit not available for this device.

Example 2

The following example resumes all of the audits at site 0:

site_audit 0 on

Where: is:
0 location
on control

System response

COMMAND ACCEPTED

Example 3

The following example suspends all of the audits at site 0:

site_audit 0 off

Where: is:
0 location
off control

3-570 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

COMMAND ACCEPTED

References

Related information

The KSW internal loopback test interrupts calls. It should be run only during periods of low
traffic. Calls interrupted by this command must be re-established after the audits are completed.

Related commands

cage_audit on page 3-58 chg_audit_sched on page 3-76 device_audit on page 3-230

query_audits on page 3-532

68P02901W23-T 3-571
Jan 2010
soft_reset Chapter 3: Device/function related commands

soft_reset

Description

The soft_reset command restarts the processes at one or more sites.

An operator logged in to a BTS can restart only the local site. Only an operator logged in to the
BSC can restart sites other than the local site.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites Sites must be installed to enter this command. The
command is abandoned if any response other than y or Y is
received.
Operator actions Respond to the verification prompt that is presented. This
format is used to reset the local site only.

Format

Syntax

The following format is used to reset the local site:

soft_reset

The following format is used to restart processes at a specified PCU site:

soft_reset pcu_n

The following format is used to reset all of the sites from the BSC:
soft_reset all

The following format is used to reset one or more sites identified by site_id. Each site to be
reset is separated by a space:
soft_reset <site_id site_id site_id... site_id>

NOTE
After entering one of the commands, the operator is prompted with a warning and
must enter y or Y (for yes) for the command to execute.

3-572 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Input parameters

pcu_n

This parameter specifies a PCU for reset:

Where: is:
pcu or pcu_0 PCU site 0 (or the only PCU) at the BSC.

all

This parameter specifies all of the sites at the BSC.

site_id

This parameter specifies the site to be reset. The range of values is 0 to 100.

NOTE
Specifying 0 causes the BSC to reset.

Verification prompts

When the command is entered to reset multiple sites, the system displays one of the following
verification prompts:

Are you sure (y=yes, n=no)?

WARNING: Command will RESTART all processes at all BTS sites.
WARNING: Command will RESTART all processes at the following sites:
<a listing of sites will follow>
Are you sure (y=yes, n=no)?

When the command is entered to reset a single site, the system displays the following
verification prompt:

WARNING: Command will RESTART all processes at site <site_id>

Are you sure (y=yes, n=no)?

If y is entered and the command is accepted for a single site, the following warning message
displays:

COMMAND ACCEPTED: WARNING REBOOT SITE: site (site_id) will reboot now!!!

68P02901W23-T 3-573
Jan 2010
Examples Chapter 3: Device/function related commands

Status displays

One of the following statuses display for each requested site:

Reboot status Description

TIMEOUT The request timed out while waiting to receive ACK
message from this site.
OUT OF SERVICE The site is OOS. The reset_site request is discarded.
NOT EQUIPPED The site is not equipped. The reset_site request is
discarded.
RESET REQUEST IN The site_reset request is in progress.
PROGRESS

Examples

Example 1

In the following example, all of the sites are reset from the BSC:

soft_reset all

Where: is:
all all sites in the BSS are specified.

System response

WARNING: Command will RESTART all processes at all BTS sites.

Are you sure (y=yes, n=no)? y
1 OUT OF SERVICE
2 RESET REQUEST IN PROGRESS
3 RESET REQUEST IN PROGRESS
4 NOT M-CELL

Example 2

In the following example sites 1, 4, and 9 are reset:

soft_reset 1 4 9

Where: is:
149 sites to be reset.

3-574 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

WARNING: Command will RESTART all processes at the following sites: 1 4 9

Are you sure (y=yes, n=no)? y
1 RESET REQUEST IN PROGRESS
4 NOT EQUIPPED
9 TIMEOUT

68P02901W23-T 3-575
Jan 2010
state Chapter 3: Device/function related commands

state

Description

The state command displays the current status of devices or functions in the system, including
when it last changed states. The length of time a device has been in its current state is also
displayed.

The state command can display specific devices or functions at one or all of the locations in the
system based on operating states and identifiers. It can also display all the devices at all of the
locations in the system by entering the state all or state all all command.

NOTE
The state command does not display the IAS device.

The following devices can be investigated with this command:

ABSS AXCDR {34371G} BBU BSP BTP

CAB CAGE CBL CELL CBUS
CIC COMB CSFP DHP DRI
EAS ETH GCLK GDS GPROC
KSW LAN MMS MSI MTL
OML PATH PBUS PCHN PSI
PPROC RSL RXCDR SBUS SITE
TBUS TDM XBL

The following GPRS only devices can be investigated with this command if the GPRS feature
is unrestricted:

DPROC GBL GDS

GSL PCU PSP

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites Not available on an RXCDR.
This command is not available while in SYSGEN ON mode.

3-576 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Format

Syntax

state <location> [<filter>] [<dev/func_name> <dev/func id> <dev/func id>

<dev/func id>] [<option1>] [option2]

Input parameters

location

Specifies the location:

0 or bsc BSC
1 - 140 BTS
all Specifies all sites
pcu or pcu_0 PCU

filter

Optional text string used to select devices or functions in a specific state. Valid values are:

busy e_u
ins locked
oos unlocked

NOTE
For a CIC or range of CICs, filter is not available.

dev/func name

Literal that uniquely identifies the device or function. all is entered to specify all devices and
functions. In a GPRS system, * is used instead of all.

dev/func id

First device/function identifier. This definition varies with each device or function. This value
is not valid when all is specified for the dev/func argument.

dev/func id

Second device/function identifier. This definition varies with each device or function. This value
is not valid when all is specified for the dev/func argument.

dev/func id

Third device/function identifier. This definition varies with each device or function. This value
is not valid when all is specified for the dev/func argument.

option1 option2

68P02901W23-T 3-577
Jan 2010
Format Chapter 3: Device/function related commands

The option parameter displays the configuration tags and the device subtypes for the specified
devices or functions.

There are two options:

Enter tags to display the configuration tags. Configuration tags are described in OMC-R
Online Help, Network Operations.

Enter subtypes to display the device subtypes.

The character string for the option can be entered in upper, lower, or mixed case letters. If both
parameters are entered together, separate them with a space.

When the tags option is entered and multiple devices or functions are specified, the displayed
Related Function or Related Device column is replaced with the Config Tag (hex) column.

CIC syntax

A form of syntax is available for each method of specifying a CIC.

The following CIC syntax applies to local transcoding:

state <location> CIC <cic_num1>

state <location> CIC <cic_num1> TO <cic_num2>

NOTE
The following three state commands are valid only in BC mode.

state <location> CIC <mms_id1> <mms_id2>

state <location> CIC <mms_id1> <mms_id2> <timeslot1>

state <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2>

NOTE
For remote transcoding BSC sites, the state command cannot be used for CICs when
the BSC is operating in the dynamic allocation mode.

The following CIC syntax applies to remote transcoding:

state <location> CIC <cic_num1>

state <location> CIC <cic_num1> TO <cic_num2>

3-578 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS

CIC

Literal that uniquely identifies the CIC device.

cic_num1

First CIC device number.

cic_num2

Last CIC device number in a range.

NOTE
mms_id1, mms_id2, timeslot1, group1, and group2 are valid only in BC mode.

mms_id1

First MMS identifier.

mms_id2

Second MMS identifier, or last in a range if TO is used.

timeslot1

First timeslot.

timeslot2

Second timeslot, or last in a range if TO is used.

group1

First group.

group2

Second group.

Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

NOTE
For a CIC or range of CICs, neither filter nor option are available.

68P02901W23-T 3-579
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

In this example, the status of the CAB device is displayed:

state 7 cab 0

Where: is:
7 location
cab dev/func name
0 dev/func ID

System response

STATUS INFORMATION:
Device: CAB 0 0 0
Administration state: UNLOCKED
Operational State: BUSY
Reason code: NO REASON
Time of last transition: Fri Apr 8 00:01:39 1994
Related Device/Function: None
END OF STATUS REPORT

Example 2

In this example, the status of all of the KSW devices at the BSC is displayed using wildcards
and the tags option:

state bsc ksw * * * tags

Where: is:
bsc location
ksw dev/func name
* dev/func ID
* dev/func ID
* dev/func ID
tags tags option

3-580 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

DEVICE STATUS INFORMATION FOR LOCATION 0:

OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown
Last Transition Config
Device State Reason dd/mm hh:mm:ss Tag (hex)
------------ ----- ------ ---------------- ---------
KSW 0 0 0 B-U None 14/01 10:36:57 00000004

Example 3

In this example, the status of all of the KSW devices at the BSC is displayed using wildcards:

state bsc ksw * * *

Where: is:
bsc location
ksw dev/func name
* dev/func ID
* dev/func ID
* dev/func ID

System response

DEVICE STATUS INFORMATION FOR LOCATION 0:

OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown
Last Transition Related
Device State Reason dd/mm hh:mm:ss Function
--------- ----- --------------- ---------------- ---------
KSW 0 0 0 B-U NO REASON 14/01 10:36:57 None
KSW 1 0 0 B-U NO REASON 14/01 08:02:31 None

68P02901W23-T 3-581
Jan 2010
Examples Chapter 3: Device/function related commands

Example 4

In this example, the status of all devices and functions at location 7 are displayed:

state 7

Where: is:
7 location

System response

DEVICE STATUS INFORMATION FOR LOCATION 7:

OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown
Last Transition Related
Device State Reason dd/mm hh:mm:ss Function
---------- ----- -------------- ---------------- ---------
CSFP 0 0 0 B-U NO REASON 14/01 10:36:57 None
BTP 0 0 0 B-U NO REASON 14/01 08:02:31 None
DRI 0 0 0 B-U NO REASON 14/01 08:03:55 RTF 0 0 0
MSI 1 0 0 B-U NO REASON 14/01 08:02:49 None
MMS 1 0 0 B-U NO REASON 14/01 08:06:30 None
RSL 0 0 0 D-U RAM LINK 16/01 08:46:52 None
...
...
...
TBUS 0 0 0 D-U NO REASON 14/01 08:02:50 None
CAGE 0 0 0 B-U NO REASON 14/01 08:02:21 None
CAB 0 0 0 B-U NO REASON 14/01 08:02:23 None
SITE 0 0 0 B-U NO REASON 14/01 08:04:51 None
PATH 0 0 0 D-U NO REASON 14/01 08:46:51 None
PATH 0 0 0 B-U NO REASON 14/01 08:55:18 None
FUNCTION STATUS INFORMATION FOR LOCATION 7:
OPER STATES: E:Enabled B:Busy ADMIN STATES: E:Equipped
Last Transition Related
Function State Reason dd/mm hh:mm:ss Device
--------- ----- --------------- ---------------- ----------
RTF 0 0 0 B-E None 14/01 08:03:43 GPROC 0 0 0

3-582 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 5

In this example, the status information for a single MSI, including device subtypes and
configuration tags are displayed:

state 0 msi 3 subtypes tags

Where: is:
0 location
msi dev/func name
3 dev/func ID
subtypes option1
tags option2

System response

STATUS INFORMATION:
Device: MSI 3 0 0 (MSI)
Administration state: LOCKED
Operational state: ENABLED
Reason code: NO REASON
time of last transition: SAT JAN 5 12:55:18 1980
Related Device/Function: None
Config Tag (hex): 00000006
END OF STATUS REPORT

Example 6

In this example, the status information for all MSIs at site 0, including device subtypes, are
displayed:

state 0 msi * subtypes

Where: is:
0 location
msi dev/func name
* wildcard character for dev/func ID
subtypes option1

68P02901W23-T 3-583
Jan 2010
Examples Chapter 3: Device/function related commands

System response

DEVICE STATUS INFORMATION FOR LOCATION 0:

OPER STATES: D:Disabled E:Enabled B:Busy

ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown
Last Transition Related
Device State Reason dd/mm hh:mm:ss Function
------------ ------ ------------------------ --------------- --------
MSI 0 0 0 B-U NO REASON 05/01 12:44:16 None
(MSI)
MSI 1 0 0 B-U NO REASON 05/01 12:44:23 None
(XCDR)
MSI 2 0 0 B-U NO REASON 05/01 12:44:16 None
(MSI)
MSI 3 0 0 E-L NO REASON 05/01 12:55:18 None
(MSI)
END OF STATUS REPORT

Example 7

In this example, the status information for an MMS at site 2 is displayed; there is a failed
HDSL modem:

state 2 mms * * *

Where: is:
2 location
mms dev/func name
* wildcard character for dev/func ID
* option1
* option2

3-584 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

DEVICE STATUS INFORMATION FOR LOCATION 2:

OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown
Last Transition Related
Device State Reason dd/mm hh:mm:ss Function
----------- ------ -------------------------- ---------------- --------
MMS 0 0 0 D-U HDSL Modem bad or missing 13/01 17:18:03 None
MMS 0 1 0 B-U No Reason 13/01 17:18:03 None
END OF STATUS REPORT

Example 8

This command displays the status of the CAGE device at PCU site 0:

state pcu_0 cage 0

Where: is:
pcu_0 location
cage dev/func name
0 CAGE identifier

System response

STATUS INFORMATION:
Device: CAGE 0 0 0
Administration state: UNLOCKED
Operational state: BUSY
Reason code: NO REASON
Time of last transition: Tue Jan 3 05:00:30 1999
Related Device/Function: None
END OF STATUS REPORT

68P02901W23-T 3-585
Jan 2010
Examples Chapter 3: Device/function related commands

Example 9

This command displays the status of PCU site 1 at BSC 0:

state 0 pcu 1

Where: is:
0 location
pcu device name
1 PCU identifier

System response

STATUS INFORMATION:
Device: PCU 1 0 0
Administration state: UNLOCKED
Operational state: BUSY
Reason code: NO REASON
Time of last transition: Sun Jan 6 01:37:49 2002
Related device/Function: None
END OF STATUS REPORT

Example 10

Displays the status of all MSIs at PCU site 0.

state PCU_0 MSI *

Where: is:
PCU_0 location
MSI device name
* all MSIs

System response

DEVICE STATUS INFORMATION FOR LOCATION PCU site 0:

OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown
Last Transition Related
Device State Reason dd/mm hh:mm:ss Function
MSI 1 0 0 B-U NO REASON 03/01 05:00:30 None
MSI 2 0 0 B-U NO REASON 03/01 06:00:00 None
END OF STATUS REPORT

3-586 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 11

Displays the status of all DPROC devices.

state PCU DPROC *

Where: is:
PCU location
DPROC device name
* all DPROCs

System response

DEVICE STATUS INFORMATION FOR LOCATION 0:

OPER STATES: D:Disabled E:Enabled B:Busy

ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related

Device State Reason dd/mm hh:mm:ss Function
------------- ----- --------- ----- -------- --------
DPROC 1 0 0 B-U NO REASON 08/01 06:59:17 None
DPROC 2 0 0 B-U NO REASON 08/01 07:00:04 None
DPROC 3 0 0 B-U NO REASON 08/01 07:00:04 None

END OF STATUS REPORT

Example 12

{34371G}

This example displays a BBU status on site 23.

state 23 bbu 0

Where: is:
23 location
bbu device name
0 bbu identifier

68P02901W23-T 3-587
Jan 2010
Examples Chapter 3: Device/function related commands

System response

STATUS INFORMATION:
Device: BBU 0 0 0
Administration state: UNLOCKED
Operational state: BUSY
Reason code: NO REASON
Time of last transition: Mon Jul 3 03:38:28 2008
Related Device/Function: None
END OF STATUS REPORT

Example 13

{34371G}

This example displays the device status at site 23, which contains (R)CTU4 DRI in 4(2 +2)
density where max_tx_bts is set to 0. These DRIs in (R)CTU4 cannot be brought into service
as Cell Transmit Power cannot be achieved.

state 23 DRI * *

Where: is:
23 location
DRI device name
* dev/func ID
* dev/func ID

3-588 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

DEVICE STATUS INFORMATION FOR LOCATION 12:

OPER STATES: D:Disabled E:Enabled B:Busy

ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related

Device State Reason dd/mm hh:mm:ss Function
------- ----- ------- ----- --------- ---------
DRI 0 0 0 D-U Cell TX PWR unachievable 02/05 11:37:09 None
DRI 0 1 0 D-U Cell TX PWR unachievable 02/05 11:38:18 None
DRI 0 2 0 D-U Cell TX PWR unachievable 02/05 11:38:08 None
DRI 0 3 0 D-U Cell TX PWR unachievable 03/05 11:27:52 None
DRI 0 4 0 B-U NO REASON 02/05 11:39:38 RTF 0 0 0
DRI 0 5 0 B-U NO REASON 03/05 12:08:41 RTF 0 1 0

END OF STATUS REPORT

Example 13

Displays the status information of the cage device.

state bsc cage 1

Where: is:
bsc location
cage device name
1 CAGE identifier

System response

STATUS INFORMATION:
Device: CAGE 1 0 0
Administration state: UNLOCKED
Operational state: BUSY
Reason code: NO REASON
Time of last transition: Wed May 7 16:42:03 1980
Related Device/Function: None
END OF STATUS REPORT

68P02901W23-T 3-589
Jan 2010
References Chapter 3: Device/function related commands

References

Transference of device status

When a GPROC card is equipped as a DHP, BSP, or BTP, all references to the state of the GPROC
card should use the equipped name (such as DHP, BSP, or BTP).

Table 3-33 lists the operational states.

Table 3-33 Operational states

Operational Description
states
Disabled FM has found the device unserviceable and has taken it out of service.
Enabled FM has made the device available for use but it is not carrying traffic.
Busy Device is available for use and is carrying traffic.

Table 3-34 lists the administrative states.

Table 3-34 Administrative states

Admin state Description

Locked The operator has taken the device out of service.
Unlocked The operator has made the device available for service.
Equipped The device exists in the system.

Table 3-35 lists the device states.

Table 3-35 Device states

Device state Description

Not Equipped The device does not exist in the system.
Disabled Locked FM and the operator find the device unserviceable.
Enabled Locked FM finds the device serviceable but the operator does not want it in
service.
Disabled FM finds the device unserviceable but the operator wants it in service.
Unlocked The system can periodically audit the device (the operator can force
audits) to determine if the device is UNLOCKED.
Enabled Unlocked FM finds the device serviceable and the operator wants it in service.
Busy Unlocked The device is in use.
Shutting Down The device is between the LOCKED and UNLOCKED states. The system
is waiting until all processes using the device have terminated before
putting the device into the LOCKED state.

NOTE
The remaining states LOCKED and NOT EQUIPPED in Table 3-35 cannot exist with
any operational component.

3-590 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 3-36 lists the reason codes.

Table 3-36 Reason codes

Reason Codes Value Explanation

Applicable to any device
NO_REASON 0 No reason.
NO_INIT 1 The device is not initialized.
PARENT_OOS 2 The parent device is out of service.
FAIL_ACT 3 The device failed to activate.
BAD_DB_CONFIG 4 The device is incorrectly configured in the
database.
NO_GPROC 5 There is no available GPROC to assign the
device.
INHIBITED 6 The device is inhibited from being used.
WAIT 7 The device is waiting for an event.
FREED_FUNCTION 8 The function has been removed from the device.
Indicate progress made by BSC initializing a remote site
NO_LINK 9 The RSL link to the BTS has not been
established.
ROM_TO_RAM 10 The default link to BTS is active. BTS is in ROM.
RAM_LINK 11 The BTS jumped to RAM without problems.
ROM_LINK 12 The site informs RSL it is a ROM link.
Applicable to combiners
COMBINER_CONTROLLER 14 Indicates which transceiver is controlling a
particular combiner.

Related commands

disp_equipment on page equip on page 3-445 lock_device on page 3-478

3-315
unlock_device on page 3-645 shutdown_device on page
3-563

68P02901W23-T 3-591
Jan 2010
status_mode Chapter 3: Device/function related commands

status_mode

Description

The status_mode command turns the state change notification on or off for the devices at a site
that can be equipped. When the status mode is turned on, a notification containing both the old
and the new status for a device displays immediately when a state change occurs. The status
notification occurs only at the local MMI at which the command was invoked. Only the BSC can
display status notification for remote sites. If the status mode is turned off, no notification is
provided when a device experiences a state change.

This command permits efficient adjustment of the current system configuration where necessary.

If no mode is entered, the current alarm status mode displays.

If the status_mode command is entered, the current status is displayed. One of the following
status messages is displayed:
Status notification is ON.

Status notification is OFF.

Site unequipped.

Site unavailable.

Status notification is already ON.

Status notification is already OFF.

Multiple sites are disabled using the same command line by entering the site IDs separated by a
space. All sites can be disabled by entering all for the location.

NOTE
Location all is only allowed at the BSC.

Security level 3
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites To display the status mode for the PCU, the GPRS feature
must be unrestricted.

3-592 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Format

Syntax

status_mode <location> [<location> ...<location>] [<mode>]

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU
all All sites

mode

Specifies the state change notification condition:

on state change notification on

off state change notification off

Examples

Example 1

This example turns on the CA device state-change notification at the BSC. When a device is
locked, note the output due to the state change that has occurred.

status_mode 0 on

Where: is:
0 location
on mode

System response

SITE STATUS
---- ----------------
0 Status notification turned ON

68P02901W23-T 3-593
Jan 2010
Examples Chapter 3: Device/function related commands

Example 2

This example shows the command string required to display the status mode for an entire BSC.

status_mode all

Where: is:
all all sites in the BSC.

System response

Site Status
---- ----------------
0 Status mode is OFF
4 Status mode is ON
5 Status mode is ON

Example 3

This example turns off the CA device state change notification at location 6.

status_mode 6 off

Where: is:
6 location
off mode

System response

SITE STATUS
---- ----------------
0 Status notification turned OFF

3-594 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 4

This example shows the effect of the status mode being turned on when the state of a device
changes. In this example, the msi 1 0 0 is being locked.

lock_device bsc msi 1 0 0

Where: is:
bsc location
msi device_name
1 device_id1
0 device_id2
0 device_id3

System response

* STATUS NOTIFICATION -- Tag(hex): <config_tag)

* <entity type & ID> (<subtype>) Site: <site> Time: <time>

* -- Old State: <op state> ,<admin state> , <reason>

* -- New State: <op state> , <admin state> , <reason>

* -- Transition Number: <sequence #>

This output occurs due to the state change of the device.

References

Related information

Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for a
description of the displayed alarm message.

68P02901W23-T 3-595
Jan 2010
store_cal_data Chapter 3: Device/function related commands

store_cal_data

Description

The store_cal_data command enables storing of the transceiver calibration data of a BTS.
Transceiver calibration data storage for all sites in the current BSS can be enabled by using
all for the location value.

NOTE
This command only works for DRIs that are in busy_unlocked state. Make sure
that all DRIs are unlocked before using the store_cal_data command to store the
transceiver calibration data.

Security level 3
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.

NOTE
Enter this command at the BSC only. This command is unavailable at a BTS site.
Contact the OMC-R for help.

Format

Syntax

store_cal_data <location>

3-596 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Input parameter

location

Specifies the site for storing transceiver calibration data:

1 - 140 BTS
all All sites in the current BSS.

Examples

Example 1

The following example stores transceiver calibration data at the BSC:

store_cal_data 0

Where: is:
0 location

System response

SITE CALIBRATION STATUS

---- ------------------
0 RCU CALIBRATION REQUEST IS IN PROGRESS

Example 2

The following example enables transceiver calibration at all sites in the current BSS:

store_cal_data all

Where: is:
all location

System response

SITE CALIBRATION STATUS

---- ------------------
0 RCU CALIBRATION REQUEST IS IN PROGRESS
22 NOT EQUIPPED: RCU Calibration request is discarded
28 OUT OF SERVICE: Please retry command later
33 TIMEOUT: Please retry command later

68P02901W23-T 3-597
Jan 2010
References Chapter 3: Device/function related commands

References

Related commands

clear_cal_data on page 3-189 disp_cal_data on page 3-253

3-598 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference swap_devices

swap_devices

Description

The swap_devices command swaps the specified standby device with the specified active
device. The following devices can be swapped by this command:

BTP COMB GCLK LAN TDM

{36039G} RSL

NOTE
Swapping a BTP device causes a site reset.

The following restrictions apply:

The standby and active devices must be the same type.

The standby device must be in the UNLOCKED state.

The CIC device cannot be locked by location when the BSS is operating in dynamic mode.
In the dynamic mode, a CIC can be locked by specifying the CIC ID only.

For a COMB device, this command swaps the active links and the controlling DRIs.

The system does not permit swapping between two GCLKs that are phase locking.

{36039G} The command can be only accepted when:

The Abis auto swap feature is unrestricted and enabled.

The target site is the BTS, not the BSC.

At least one RSL has been configured to the target Abis bearing mode to support
the swap.

If the manual swap command is still processing, the new command is rejected.

Based on these conditions, the command is accepted with a warning for the swap
action or when the target site is OOS.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites This command is not allowed while in SYSGEN ON mode.
Operator actions Unlock the standby device to be swapped.

68P02901W23-T 3-599
Jan 2010
Format Chapter 3: Device/function related commands

Format

Syntax

swap_devices <location> <active_device_name> [<std_device_id1>]

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS

active_device_name

Literal that identifies the active device.

std_device_id1

Standby device identifier; required only for the COMB.

Examples

Example 1

This example swaps the active comb with the standby comb 0 at BTS site 1.

swap_devices 1 comb 0

Where: is:
1 location
comb active_device_name
0 standby_device_id1

System response

COMMAND ACCEPTED

3-600 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 2

This example swaps the active lan with the standby lan at BTS site 0.

swap_devices 0 lan

Where: is:
0 location
lan active_device_name

System response

COMMAND ACCEPTED

Example 3

{36039G}

This example swaps the link from satellite to terrestrial when the feature is unrestricted and
enabled, and at least 1 RSL has been configured to the satellite mode.

swap_devices 1 rsl

Where: is:
0 location
rsl active_device_name

System response

WARNING: Currently the abis link works on Satellite mode, Change it to

Terrestrial mode.
Are you sure (y=yes, n=no)? Y
COMMAND ACCEPTED

68P02901W23-T 3-601
Jan 2010
References Chapter 3: Device/function related commands

Example 4

{36039G}

This example swaps the link from terrestrial to satellite mode when the feature is restricted.

swap_devices 1 rsl

Where: is:
0 location
rsl active_device_name

System response

COMMAND REJECTED: Received a request to modify a restricted optional feature.

References

Related commands

disp_equipment on page equip on page 3-445 lock_device on page 3-478

3-315
state on page 3-576 unequip on page 3-633 unlock_device on page 3-645

3-602 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sysgen_mode

sysgen_mode

Description

The sysgen_mode command places the system in the SYSGEN ON or SYSGEN OFF mode. This
command also displays the current mode of operation.

NOTE
This command is not intended for general use at the OMC-R.

The current SYSGEN mode and the SYSGEN mode after the next restart can be displayed by
entering the sysgen_mode command without input parameters.

The system is placed in the SYSGEN ON mode from the SYSGEN OFF mode by entering the
sysgen_mode on command string then resetting the site.

The system is placed in the SYSGEN OFF mode from the SYSGEN ON mode by entering the
sysgen_mode off command string then resetting the site.

The sysgen_mode off command is rejected if:

An EGPRS RTF has a valid FHI in baseband hopping and the master cabinet at the site is
not a Horizon II macro.

An EGPRS RTF has the same FHI as a non-EGPRS RTF in a baseband hopping system.

Sysgen_mode off performs a check on GSM HR capability. An attempt to exit Sysgen with
GSM Half Rate enabled but with CIC validation disabled for an AXCDR generates a warning
indicating that AXCDR CIC validation must be enabled for AMR/GSM HR.

SYSGEN OFF mode

When the system is in the SYSGEN OFF mode, the database is verified each time a change is
made. The checksum is then calculated, and the database is broadcast to the other sites. When
the sysgen_mode off command is entered, the security level resets to Level 1 for all operators.

68P02901W23-T 3-603
Jan 2010
Format Chapter 3: Device/function related commands

SYSGEN ON mode

When the system is in the SYSGEN ON mode, the database is not checked when a change is
made. The checksum is not recalculated and the database is not broadcast to the other sites.
When the sysgen_mode on command is entered, the site must be reinitialized to place the
system in the SYSGEN ON mode. Refer to the reset_site command. Command execution can
occur without system delays. There is no interaction with other processes.

CAUTION
After a system reset a command must be entered within 10 minutes after the
MMI-RAM-> prompt is presented. If a command is not entered, the system resets.

Initial SYSGEN mode

The system can be placed in the initial SYSGEN mode by placing the system in the SYSGEN ON
mode after the database has been deleted using the clear_database command.

Security level 4
Supported by OMC-R GUI No
Command type B (operator actions required)
Prerequisites None
Operator actions Reset the system to change the SYSGEN mode after
entering this command.

Format

Syntax

sysgen_mode [<value>]

Input parameter

value

Specifies the status of SYSGEN:

on Places the system in the SYSGEN ON mode.

off Places the system in the SYSGEN OFF mode.

3-604 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

In this example, the system is placed in the SYSGEN OFF mode of operation:

sysgen_mode off

Where: is:
off the SYSGEN mode in which the system is placed after the
next reinitialization.

System response

******* VERIFYING DATABASE BEFORE COMPLETING SYSGEN *******

Frequency hopping verification in progress.
SITE 0 Verification.
DB Verification passed.
COMMAND ACCEPTED.

Example 2

In this example, the system is placed in the SYSGEN ON mode of operation:

sysgen_mode on

Where: is:
on the SYSGEN mode in which the system is placed after the
next reinitialization.

System response

COMMAND ACCEPTED: You must re-init the site to start SYSGEN

Example 3

In the following example, the current SYSGEN mode is displayed and the mode into which
the system is placed after the next restart.

sysgen_mode

68P02901W23-T 3-605
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Current Sysgen mode: ON

Sysgen mode upon next restart: OFF

Example 4

This example attempts to turn off SYSGEN mode with GSM Half Rate enabled but with CIC
validation disabled for an AXCDR.

sysgen_mode off

System response

WARNING: AXCDR CIC validation must be enabled for AMR or GSM HR.

Example 5

In this example SYSGEN mode is turned off when PCU 0 does not have enough GDS resources,
and PCU 1 does not have enough PMC resources for res_gprs_pdchs and switch_gprs_pdchs.

sysgen_mode off

System response

********** VERIFYING DATABASE BEFORE COMPLETING SYSGEN **********

PCU 0:
-----------------------------------------------------------------------
WARNING: Insufficient GDS resources available for all PDTCHs on the PCU.
PCU 1:
-----------------------------------------------------------------------
WARNING: Insufficient PMC resources available for all PDTCHs on the PCU.
Sysgen OFF warnings were detected.
If accepted, this database may cause some loss of service.
Still leave sysgen mode?
Are you sure (y=yes,n=no)? y

Example 6

In this example SYSGEN mode is turned off when PCU 0 does not have enough GDS
resources and PCU 1 does not have enough PMC resources for res_ts_less_one_carrier and
sw_ts_less_one_carrier.

sysgen_mode off

3-606 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Database errors

System response

********** VERIFYING DATABASE BEFORE COMPLETING SYSGEN **********

PCU 0:
-----------------------------------------------------------------------
WARNING: Insufficient GDS resources avail for all PDs on the PCU
(less one carrier).
PCU 1:
-----------------------------------------------------------------------
WARNING: Insufficient PMC resources avail for all PDs on the PCU
(less one carrier).
Sysgen OFF warnings were detected.
If accepted, this database may cause some loss of service.
Still leave sysgen mode?
Are you sure (y=yes,n=no)? y

Database errors

A database error causes the sysgen_mode off command to be rejected and a database is not
created; an error message displays. All error messages are preceded with the DB VERIFY
ERROR: string.

General database errors

The BSC MUST have an OMF equipped if bsc_type is 2.

bsc_type MUST be zero for site type RXCDR.
At least one LCF MUST be equipped at site 0 when bsc_type is not 0.
At least one LCF MUST have max_mtls greater than zero for this site type.
The BSC MUST have at least one BSP equipped.
Site <site_id> does note have a BTP equipped.
Site <site_id> does not have a GCLK equipped.
RRSM Timer,8 value at site <site_id> must be less than SSM Timer,10.
No slots available on BSP.
No BSP found in CM database.
Requested bsc_type not supported.
No slots available on LCF.
No LCF found in CM database.
There is no default RSL equipped to BTS site <site_id> on any PATH.
INVALID DATA IN BIN <bin>: decision_1_dl_rxqual_av_h error in cell id

68P02901W23-T 3-607
Jan 2010
Database errors Chapter 3: Device/function related commands

<cell_number>
INVALID DATA IN BIN <bin>: decision_1_dl_rxlev_av_h error in cell id
<cell_number>
INVALID DATA IN BIN <bin>: decision_1_dl_rxlev_av_ih in cell id <cell_number>
INVALID DATA IN BIN <bin>: decision_1_p_bgt_rxlev_av_h in cell id <cell_number>
(rxlev_dl_ho)
INVALID DATA IN BIN <bin>: decision_1_p_bgt_rxlev_av_h in cell id <cell_number>
(surround_cell)
INVALID DATA IN BIN <bin>: decision_1_dl_rxqual_av_p in cell id <cell_number>
INVALID DATA IN BIN <bin>: decision_1_dl_rxlev_av_p in cell id <cell_number>
INVALID DATA IN BIN <bin>: decision_1_ncell_rxlev_av_h_calc in cell id
<cell_number>
INVALID DATA IN BIN <bin>: decision_1_tim_adv_av_alg in cell id <cell_number>
INVALID DATA IN BIN <bin>: decision_1_ul_rxqual_av_h in cell id <cell_number>
INVALID DATA IN BIN <bin>: decision_1_ul_rxlev_av_h in cell id <cell_number>
INVALID DATA IN BIN <bin>: decision_1_ul_rxlev_av_ih in cell id <cell_number>
INVALID DATA IN BIN <bin>: decision_1_ul_rxqual_av_p in cell id <cell_number>
INVALID DATA IN BIN <bin>: decision_1_ul_rxlev_av_p in cell id <cell_number>

General hopping errors

Can't have baseband and synthesizer hopping_support values at same site.

BCCH frequency cannot have BCCH timeslots which hop.
cell = <cell_number> frequency = <frequency> timeslot = <timeslot>
Too many frequencies were defined for the frequency range
Unable to format cell-channel description with this many frequencies
Cell: <cell_number> Number Freqs defined: <number of frequencies
defined> Max Freqs allowed: <maximum number of frequencies allowed>
Timeslot: <timeslot> for fhi: <fhi> doesn't hop. Thus, arfcn: <arfcn>
can't appear in the MA for the same TS for arfcn: <arfcn>
FHI: <fhi> of carrier: <carrier> and FHI: <fhi> of
carrier: <carrier number> in timeslot: <timeslot>
in cell: <cell_number> have intersecting frequencies in its
mobile allocation. (frequency: <frequency>)
The NON-BCCH carrier with arfcn: <arfcn> in cell: <cell_number> has
the BCCH frequency in its mobile allocation for FHI timeslot: <timeslot>.
site: <site_id> cell: <cell_number> hopping_support: <hopping_support>
site: <site_id> cell: <cell_number> hopping_support: <hopping_support>
...

3-608 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Database warnings

Synthesizer hopping errors

The BCCH carrier isn't in any MA. Hopping timeslots exist in

cell <cell_number> but not on the BCCH carrier.
All timeslots for BCCH carrier (frequency): <bcch_freq> set to non-hopping (255)
NON-BCCH TS's on BCCH carrier must have same FHI as NON-BCCH
TS's when hopping through BCCH frequency. bcch_freq: <bcch_freq> fhi_ts: <fhi_ts>
FHI values must be identical within the BCCH carrier timeslots.
For Cell: <cell_number> Timeslot: <timeslot> with FHI: <fhi > mismatches
Timeslot:<timeslot> with FHI: <fhi>
There are fewer frequencies than carriers for fhi: <fhi> in timeslot:<timeslot>.
The number of frequencies is: <number of frequencies>.
The number of carriers is: <number of carriers>.

Baseband hopping errors

arfcn: <arfcn> should be in the mobile allocation for fhi: <fhi> timeslot:
<timeslot> EGPRS and non-EGPRS carriers cannot have the same FHI
Within a cell, all carriers having their arfcns in the same MA
must have identical fhi values for the same timeslot.
Mismatch between carrier arfcn: <arfcn> ts: <timeslot> fhi_value:<fhi>
and carrier arfcn: <arfcn> ts: <timeslot> fhi_value:<fhi>
The arfcn: <arfcn> in the MA of carrier: <carrier number> has not been assigned
to any carrier. ts: <timeslot> fhi: <fhi>
The arfcn of the carrier must be part of the MA for its FHI.
carrier arfcn: <arfcn> timeslot: <timeslot> fhi: <fhi> cell: <cell_number>
Master cabinet must be Horizonmacro2 for EGPRS to hop in baseband hopping

Database warnings

A database warning causes the sysgen_mode off command to be rejected and a database is
not created; a warning message is displayed. All warning messages are preceded with the DB
VERIFY WARNING: string.

68P02901W23-T 3-609
Jan 2010
References Chapter 3: Device/function related commands

General database warnings

Maximum MTLs should be the same value for all BSPs.

sd_load is zero for all carriers in local cell <cell number>.
max_dris of Primary and Redundant BTPs do not match at site <site number>.
Site <site number> is bts_type 1 but does not have a DHP equipped.
Number of functions exceeds number of POOL GPROCs at site <site number>.
This will cause one or more LCFs or OMFs to not come in service.

References

Related information

When exiting the SYSGEN mode or completion of a database using the SYSGEN or DATAGEN
tools, the database is verified for sanity.

If errors are detected, a database error or database warning is generated.

Related commands

chg_level on page 3-160 disp_level on page 3-361 reset_site on page 3-553

3-610 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference time_stamp

time_stamp

Description

The time_stamp command enables or disables the time-stamping function. This function adds a
time and date before the MMI command prompt.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

time_stamp <value>

Input parameter

value

Specifies the status of time_stamp:

on Turns time_stamp on.

off Turns time_stamp off.

Examples

Example 1

In this example, the time stamp is turned on:

time_stamp on

System response

[11/12/93 01:03:30] MMI-RAM 0115->

68P02901W23-T 3-611
Jan 2010
References Chapter 3: Device/function related commands

Example 2

In this example, the time stamp is turned off:

time_stamp off

System response

MMI-RAM 0115->

References

Related commands

chg_time on page 3-178 chg_throttle on page 3-176

3-612 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference trace_call

trace_call

Description

The trace_call command creates a Call/GPRS Trace instance in the BSS. An instance is a set of
criteria that defines a trace. A maximum of 16 instances can exist on a BSS.

The number of call trace instances that can be created using the trace_call command is
affected by the percentage of traces reserved exclusively for MSC initiated traces. This
percentage is specified using the call_trace_options parameter. For example, if 50% of the
traces are reserved for initiation from the MSC, a maximum of eight instances can be created
using the trace_call command.

The trace_call command is primarily intended for tracing calls and GPRS data transfer with
unspecified subscriber and equipment IDs. With limitations, it can trace subscribers and
equipment. Due to GSM architectural restraints, however, the BSS does not have complete
knowledge of subscriber or equipment IDs. Therefore, this command cannot reliably trace by
subscriber or equipment. For the exact restraints, refer to the Notes for the call selector
prompt in the Related Information subsection.

Maximum number of traces

Traces can be initiated from the MSC or when a call meets the criteria specified in an instance
on the BSS. The maximum number of traces that can be run simultaneously is 16 per LCF,
including MSC initiated traces.

MSC initiated traces are run immediately because the trace is for a call that is already in
progress. An MSC initiated trace affects the capacity of the LCF where the call originated. This
is because the same LCF controls a call for the duration of the call even if the call is handed
over to a cell controlled by another LCF.

For example, if there are 15 traces currently running on an LCF and the MSC initiates a trace
for a call that originated on the same LCF, no additional traces could run on that LCF even if the
call is handed over to a cell controlled by another LCF.

Call trace data

A basic set of call trace data is included in the reports generated by this command. Any
combination of Abis, BSSMAP, DTAP, MS_POWER_CONTROL, RR, SS GSM call data types and
LCC, BSSG, RLC_MAC, PC&CS, PMRs, RLC_MAC_PDAKs, GPRS data transfer types can also
be specified for inclusion in the basic call trace data. The GPRS Trace optional feature must
be unrestricted to trace GPRS call criteria.

68P02901W23-T 3-613
Jan 2010
Format Chapter 3: Device/function related commands

OMC-R reporting

Each set of call trace criteria created using the trace_call command is reported to the OMC-R.
This permits the OMC-R to determine when the maximum number of traces has been reached
in the BSS.

Use of the trace_call command impacts OML, BSS, or OMC-R performance. If a large
number of call traces are initiated on multiple BSSs connected to a single OMC-R, the OML
traffic increases. This increase, together with normal OML traffic (such as alarms and
uploads/downloads), can cause some call trace data for the OMC-R to be lost.

The trace_call command creates a set of trace call criteria in the BSS that can trigger traces
on calls.

Reports generated by this command include a set of basic call trace data. Any combination of
GSM and GPRS data can also be specified for inclusion in the basic call trace data.

After the command is entered, the system displays a series of prompts. The prompted
parameters are described under Related information at the end of this section.

Implementing trace_call increases the amount of data passing over the OML. This feature
impacts OML, BSS, or OMC-R performance.

For example, a large number of call traces initiated on multiple BSSs connected to a single
OMC-R can increase the OML traffic. This increase, together with normal OML traffic (such as
alarms and uploads/downloads), can cause some call_trace data to be lost. Call Trace Flow
Control reduces, and can eliminate, this from occurring. Refer to the ct_flow_control_hi_level
and ct_flow_control_lo_level parameters for more information.

Security level 3
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed in SYSGEN mode.
GPRS Trace feature must be unrestricted to trace GPRS
data transfer.

Format

Syntax

trace_call <location> [rtf <id1> <id2> <id3>]

trace_call <cell_desc>

trace_call all

3-614 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Input parameters

location

The location of the equipment:

1 - 140 BTS
all all locations

NOTE
If the location = all, do not use rtf in the command syntax.

rtf

The name for the radio transmit function. This is the only valid input.

id1

The first function identifier.

id2

The second function identifier.

id3

The third function identifier.

cell_desc

GSM cell ID of the cell to be traced, preceded by cell_number=.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900)

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command can be entered in place of the
cell_number. When the cell name is entered, it must be placed inside double quotation marks,
and be preceded by cell_name=.

NOTE
The system accepts only one of the following inputs: location, cell_number or
cell_name. Do not combine these parameters in a single command.

68P02901W23-T 3-615
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Refer to the Related information subsection for a description of the prompts displayed in the
following examples.

Example 1

This example shows a BSS-wide trace to capture multiple data record types, including BASIC,
BSSMAP, DTAP, and Abis data, where:
Any trigger event can start a trace, including a call already in progress.

The system traces any call identified by SCCP number 747B6C (hexadecimal).

Only one call is traced.

Output is directed to the MMI.

trace_call all

Where: is:
all location

System response

Enter trigger event: all

Enter additional data types (Basic is always included): bssmap, dtap, abis
Collect during handover only?: no
Enter call selector type and value: sccp=747B6Ch
Trigger enabled time:
Enter total number of calls to be traced per LCF/PRP: 1
Enter destination for trace data: mmi

COMMAND ACCEPTED

NOTE
If the response to the Enter additional data types prompt includes more than
one data type, each type must be separated by a comma and a space, as shown in
Example 1.

3-616 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 2

This example shows a trace on a specified MS whenever it hands over into the specified cell,
where:
The tracing continues until stopped by an operator.

This trace collects BASIC data only.

The system traces any call involving the mobile unit identified by a specific IMEISV number.

Tracing discontinues if the call leaves the scope.

Output is directed to the MMI and the OMC-R.

trace_call cell_name=Trafalgar_Square

Where: is:
Trafalgar_Square cell_name

System response

Enter trigger event: handover

Enter additional data types (Basic is always included):
Enter call selector type and value: imeisv=0010167890123021
Trigger enabled time:
Enter total number of calls to be traced per LCF/PRP:
Trace calls beyond scope?: no
Enter destination for trace data: both

COMMAND ACCEPTED

Example 3

This example shows a trace on BTS location 2, RTF 0 0, where:

Any trigger event can start a trace, including a call already in progress.

This trace collects BASIC and MS_POWER data only.

The system traces every fourth call.

No more that two calls are traced simultaneously.

The tracing continues until eleven calls have been traced.

Tracing discontinues if the call leaves the scope.

Output is directed to the OMC-R.

68P02901W23-T 3-617
Jan 2010
Examples Chapter 3: Device/function related commands

trace_call 2 rtf 0 0

Where: is:
2 BTS location
rtf rtf
0 id1
0 id2

System response

Enter trigger event: all

Enter additional data types (Basic is always included): ms_power
Enter call selector type and value: nth=4
Enter maximum simultaneous calls traced per LCF: 2
Trigger enabled time:
Enter total number of calls to be traced per LCF/PRP: 11
Trace calls beyond scope?:
Enter destination for trace data: omc

COMMAND ACCEPTED

Example 4

This example shows a trace on RTF 0 1 at BTS site 4, where:

Any trigger event can start a trace, including a call already in progress.

This trace collects BASIC and RSS data only.

Once a call triggers a trace, all trace data of the specified types is collected.

The RSS reports Measurement Report data every eight intervals (one interval = 480 ms).

The system traces every seventh call.

No more that four calls are traced simultaneously.

Tracing is enabled at 9:00 pm.

Tracing is disabled at 10:00 pm.

Tracing continues if the call leaves the scope.

Output is directed to the MMI by default.

3-618 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

trace_call 4 rtf 0 1

Where: is:
4 BTS location
rtf rtf
0 id1
1 id2

System response

Enter trigger event: all

Enter additional data types (Basic is always included): rss
Collect during handover only?: no
Enter Measurement Report interval (X480ms): 8
Enter call selector type and value: nth=7
Enter maximum simultaneous calls traced per LCF: 4
Trigger enabled time: 21 00
Trigger disabled time: 22 00
Enter total number of calls to be traced per LCF/PRP:
Trace calls beyond scope?: yes
Enter destination for trace data:

COMMAND ACCEPTED

NOTE
The Enter Measurement Report interval (X480ms) prompt displays only if the
operator enters no to the previous prompt.

Example 5

In this example, a BSS-wide trace is set on the specified IMSI for GPRS Data Transfer or GSM
calls capturing all types of data. The trace can only be triggered between 8:00 pm to 10:00 pm
each day, and continues until deleted by the operator. There is no limit on the number of calls
that are traced. Calls are not traced beyond scope. Trace reports are sent to OMC-R.

trace call

68P02901W23-T 3-619
Jan 2010
Examples Chapter 3: Device/function related commands

System response

Enter trigger event: combined_all

Enter additional data types(Basic is included): combined_all
Collect during handover only?: no
Enter Measurement Report interval (x480ms): 20
Enter call selector type and value: imsi=001010000000911
Trigger enabled time: 20 00
Trigger disable time: 22 00
Enter total number of traces to be traced per LCF/PRP:
Trace calls beyond scope?:
Enter destination for trace data: omc

COMMAND ACCEPTED

Example 6

This example attempts to create a GPRS trace when GPRS Trace option is restricted.

trace_call

System response

Enter trigger event: handover gprs

Enter additional data types(Basic is included): combined_all
Collect during handover only?: no
Enter Measurement Report interval (x480ms): 20
Enter call selector type and value: imsi=001010000000911
Trigger enabled time: 20 00
Trigger disable time: 22 00
Enter total number of traces to be traced per LCF/PRP:
Trace calls beyond scope?:
Enter destination for trace data: omc

COMMAND REJECTED: Received a request to modify a restricted optional feature.

3-620 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related information

Prompts preceded by an asterisk (*) Table 3-37 are only displayed under the conditions
described in the Notes column.

Table 3-37 trace_call prompts and values for a GSM Trace and GPRS Trace.

Valid range or
Prompt Default Notes
values
Enter trigger event: setup all If the trigger event is specified as:
handover
all all, it refers to a GSM Trace
gprs (handover and setup).
combined_all
gprs, it refers to a GPRS Data
Transfer.

combined_all, it refers to
GPRS and GSM Trace.
Any or all of the trigger event types
can be selected.
Enter additional Abis, Only basic If the trigger_event is specified
data types (Basic BSSMAP, data is as setup, handover or all, the
is included): DTAP, sent valid values for data types are
MS_power, DTAP, BSSMAP, Abis, RR, RSS,
RR, MS_power and all.
RSS, If nothing is entered then the
all, record type is basic.
LLC, If trigger_event is specified as gprs
BSSGP, the valid values for data type are
RLC_MAC, LLC, BSSGP, RLC_MAC, PMRs,
PMRs, RLC_MAC_PDAKs, PC&CS and
RLC_MAC_PDAKs, GPRS_all.
GPRS_all, The Combined_all data type
PC&CS, can only be specified if the
Combined_all. trigger_event is Combined_all or
gprs with setup, handover or all.
If RSS is entered as a data type, the
system prompts for an additional
parameter, the Measurement
Report Interval.
The RSS Data displays Reported
3G Neighbor Info when it is
available.

Continued

68P02901W23-T 3-621
Jan 2010
References Chapter 3: Device/function related commands

Table 3-37 trace_call prompts and values for a GSM Trace and GPRS Trace.
(Continued)
Valid range or
Prompt Default Notes
values
* Collect during yes (1) No The prompt is displayed only if the
handover only?: no (0) RSS, Abis and/or MS_Power data
Not applicable types are specified, and the trigger
for GPRS Trace event is setup, handover, all or
criteria. combined_all.
no or 0 means that once a call
triggers a trace, all trace data of
the specified types is collected.
yes or 1 means that the RSS, Abis,
and/or MS power data, if specified,
is collected immediately before and
after a handover has occurred.
The number of messages
collected is determined by
trace_msgs_before_ho and
trace_msgs_after_ho data base
parameters.

* Enter Measurement Any value 10 (4.8 This parameter specifies the

Report interval between 1 and seconds) number of 480 ms periods to
(x480ms): 255 wait before collecting another
measurement report.
The prompt is displayed if the data
type specified is:

RSS and the operator did

not specify collect during
handover only.

PC&CS. (The report

interval applies to UL/DL
Measurement Data.)

PMRs. Specifies roughly the

rate at which the network
requests PMRs from a mobile
in NC1 mode. The specified
rate is mapped to the valid
reporting period rate as
defined in 3GPP 44.060 [2]

Continued

3-622 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 3-37 trace_call prompts and values for a GSM Trace and GPRS Trace.
(Continued)
Valid range or
Prompt Default Notes
values
Enter call selector IMSI=msid None Mobile station identifier (msid) is
type and value: TMSI=msid a number that identifies a specific
IMEI=msid mobile unit or subscriber. It must
IMEISV=msid be enclosed in double quotation
SCCP=0 to marks.
FAFFFFh If Nth call or NthGPRSmobile is
Nth= 1 to 255 specified, the operator is prompted
TLLI= 02h to for the maximum simultaneous
0FFFFFFFFh calls traced.
or 2 to If trigger_event is only gprs, the
4294967295 call selector can be IMSI, TLLI or
NthGPRSmobile=1 NthGPRSMobile.
to 255 If trigger_event is gprs and setup
or handover, or combined_all,
the call selector can only be IMSI.
If trigger_event is not gprs, then
call selector can be IMSI, TMSI,
IMEI, IMEISV, SCCP or Nth.
* Enter maximum Any value 1 This is displayed only if the
simultaneous calls between 1 call selector type is Nth or
traced per LCF/PRP: through 16 NthGPRSmobile.
If call selector is NthGPRSmobile
only values 1-6 are valid for this
prompt.
Trigger enabled time: A time between Immediate If no time is specified, the trace
Midnight (00 start begins immediately and no trace
00) and 23 59. period is used.
(Enter the time Once enabled, the trace must
without using still be triggered according to the
a colon. For specified trigger event before data
example, 8 25 is collected.
is 20 25). Time is the time of day, using a 24
hour clock.
* Trigger disabled A time between None The prompt is displayed only if a
time Midnight (00 trigger enabled time is specified. A
00) and 23 59. valid value is required.
(Enter the time The trace is not deleted at
without using the trigger disabled time, it
a colon. For is suspended until the trigger
example, 8 25 enabled time the following day. To
pm is 20 25). delete the trace, the operator must
either specify a total number of
calls to trace, or delete the trace
manually.

Continued

68P02901W23-T 3-623
Jan 2010
References Chapter 3: Device/function related commands

Table 3-37 trace_call prompts and values for a GSM Trace and GPRS Trace.
(Continued)
Valid range or
Prompt Default Notes
values
Enter total number Any value None - If no value is specified there is no
of calls to be traced between 1 trace until limit, and the trace exists until the
per LCF/PRP: through 255 deleted trace is deleted manually by an
manually operator.
If a value is specified, the trace
is deleted automatically after the
specified number of calls have been
traced.
* Trace calls beyond yes (1) or no no The prompt is not displayed if the
scope: (0) trigger_event is specified as only
gprs.
No or 0 means that trace data is no
longer collected if the call hands
out of the specified scope.
Yes or 1 means that once a call
triggers a trace, it is traced until
the call is completed, or until it
leaves the current BSS.
The value entered for this prompt
does not apply to GPRS data
transfer when trigger event is a
combination of Call trace and GPRS
Data transfer.
* Enter destination mmi mmi Trace reports are directed to the
for trace data: omc MMI, the OMC, or both.
both The prompt is not displayed if the
trigger_event is specified as only
gprs.
GPRS Trace records go to the OMC
only.
The value entered for this prompt
does not apply to GPRS data
transfer when trigger event is a
combination of Call trace and GPRS
Data transfer.

Related commands

disp_trace_call on page 3-432 trace_stop on page 3-627

3-624 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference trace_connection

trace_connection

Description

The trace_connection command displays the timeslot connectivity information for a specified
device. The information includes the Site ID, MMS ID, MMS timeslot numbers for all sites, and
the MMSs through which the connectivity path passes.

If the requested trace is for an MMS, the operator is prompted to enter the MMS timeslot
number.

Security level 3
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed in SYSGEN mode.

Format

Syntax

trace_connection <location> <device/function> <id1> [<id2> <id3>]

Input parameters

location

bsc or 0

device/function

The following devices and functions can be specified:

MMS OML OPL

RSL GSL MTL

XBL

68P02901W23-T 3-625
Jan 2010
Example Chapter 3: Device/function related commands

NOTE
When the MMS is specified, the operator is prompted for the MMS timeslot.

<id1><id2><id3>

Device identifiers

Example

This example displays the connectivity information for timeslot 1 of MMS 2 0.

trace_connection 0 mms 2 0

Where: is:
0 the location (the BSC)
mms 2 0 the device

System response

Enter the timeslot: 1

Start of Report
Timeslot Usage: 16 K_RSL 1 0
Path Id: 1 0
Site MMS Timeslot(s)
BSC downlink 2 0 1
BTS 1 uplink 0 0 1
End of Report

3-626 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference trace_stop

trace_stop

Description

The trace_stop command deletes existing trace criteria, stops triggering new traces on existing
criteria, or stops traces on specified calls.

Security level 3
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites This command is not allowed in SYSGEN mode.

Format

Syntax

trace_stop <type>[=<value>] [<extent>]

Input parameters

type

The reference type for the trace. One of:

sccp SCCP number. This input requires a <value>.

ref Trace reference number. This input requires a <value>.
TLLI The temporary logical link identity. This input requires a <value>.
all All traces. This input does not require or allow a <value>.

value

The hexadecimal value for the sccp or reference number.

If the type is... Then the valid range is...

sccp between 0 and FAFFFFh
ref between 0 and FFFFFFFFh
TLLI between 2 and FFFFFFFFh

68P02901W23-T 3-627
Jan 2010
Examples Chapter 3: Device/function related commands

NOTE
The hexadecimal number input requires a 0 prefix and an h suffix.

extent

The extent to which traces should stop. extent is not valid when type is set to sccp. One of:

all All traces are stopped and the specified instance deleted
immediately.
If no extent is set, the system defaults to all.
new No new traces are to be started, and the specified instance is
deleted once all previously triggered traces are completed.
none Prevents the system defaulting to all.

Examples

Example 1

This example stops tracing a call with SCCP = 047BC6h.

trace_stop sccp=047BC6h

Where: is:
sccp type
047BC6h value

System response

COMMAND ACCEPTED

Example 2

This example deactivates the trace for reference number hex C027010A and stops tracing
any calls triggered by this instance.

trace_stop ref=0C027010Ah all

Where: is:
ref type
0C027010Ah value
all extent

3-628 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

COMMAND ACCEPTED

Example 3

This example disables the triggers for the trace with reference number hex 80270001, while
continuing any current call traces. When the current traces are completed, the trace instance is
deleted from the database.

trace_stop ref=080270001h new

Where: is:
ref type
080270001h value
new extent

System response

COMMAND ACCEPTED

Example 4

This example stops triggering on all call trace criteria.

trace_stop all new

Where: is:
all new extent

System response

COMMAND ACCEPTED

Example 5

This example deletes all call trace criteria.

trace_stop all

Where: is:
all type

68P02901W23-T 3-629
Jan 2010
Examples Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED

3-630 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference unconfigure_csfp

unconfigure_csfp

Description

The unconfigure_csfp command unconfigures CSFP devices from sites in the BSS network.
This command returns the CSFP device back to a BSP, BTP, or pooled GPROC device depending
on the original acquired device.

Security Level 4
Supported by OMC-R GUI Yes
Command Type B (operator actions required)
Prerequisites The system must be in SYSGEN mode to execute this
command.
Operator actions Put the system into SYSGEN mode.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

unconfigure_csfp

Input parameters

There are no input parameters associated with this command.

Example

In this example, all of the CSFP devices in the network are non configured.

unconfigure_csfp

68P02901W23-T 3-631
Jan 2010
References Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED

References

Related commands

chg_csfp on page 3-101 configure_csfp on page 3-195 disp_csfp on page 3-284

3-632 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference unequip

unequip

Description

The unequip command deletes a device or function from the FM portion of the CM database.

The unequip command is rejected if any child dependencies exist for the specified device or
function. Also the command is rejected for an RTF or SITE if any Trace criteria exists with
scope as the specified RTF or SITE.

Security level 4
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites The unequip command is only allowed for a locked
device or function. No child dependencies exist for the
specified device or function to be unequipped. If a
dependency is detected, the unequip command is rejected.
See SYSGEN states below for further information.
All Trace Criteria with scope as the specified RTF or SITE
must be deleted before an RTF or SITE can be unequipped.
Operator actions Lock the device or function to be unequipped.
Place the system in the SYSGEN ON mode if a CBL, MTL,
OMF or OML is to be unequipped using this command.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

SYSGEN states

Place the system in the SYSGEN ON mode using the sysgen_mode on command. To leave the
SYSGEN ON mode, use the sysgen_mode off command.

68P02901W23-T 3-633
Jan 2010
SYSGEN states Chapter 3: Device/function related commands

In or out of SYSGEN

The following devices and functions can be unequipped using the unequip command with the
system in or out of the SYSGEN ON mode.
CAB

CBL

CIC

NOTE
For remote transcoding BSC sites, CICs must be equipped on a pre-MMS basis
when the BSC operates in the dynamic allocation mode.

COMB (not M-Cellmicro)

NOTE
All affected COMB devices must be OOS before using the unequip command.

CSFP (InCell)

DHP (InCell)

NOTE
The unequip command is not available for DHP devices at a Horizonmicro.

DRI

DPROC

NOTE
DPROC performed at site PCU.

3-634 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference SYSGEN states

DYNET

NOTE
A DYNET cannot be unequipped if:

It is the last DYNET containing a site using dynamic allocation and that site
still has equipped RTFs or,
It causes the total terrestrial backing resources for a BTS network to be
less than the total reserved cell capacity.

The total terrestrial backing resources for a BTS network is the sum of the terrestrial
backing resources reserved on the DYNETs for the BTS network.

EAS (not M-Cellmicro)

GBL

GCLK (InCell)

GDS

NOTE
When an attempt is made to unequip a TRAU GDS, and the requested PDTCHs
exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and
issues a warning to indicate that GDS or PMC resource are not available.

GPROC (InCell)

GSL

NOTE
To bring the GSL out of service, lock it at either the OMC-R or at the MMI
prompt.

The GSL is performed at site PCU.

KSW (InCell)

LCF

MSI

NOTE
An RF_Unit MSI cannot be unequipped if DRIs are equipped that use LTU
connectors controlled by the RF_Unit MSI. An MSI cannot be unequipped if the
device is referenced in the BSS-RXCDR connectivity table.

68P02901W23-T 3-635
Jan 2010
SYSGEN states Chapter 3: Device/function related commands

MTL

OML

PATH

PCU

RTF

NOTE
An RTF cannot be unequipped if both the following conditions are true:

The cell is baseband hopping.

One or more of the FHIs associated with the RTF are enabled.

A warning message is generated if an attempt is made to unequip an RTF with a

non-zero sd_load value.

An RTF cannot be unequipped if the resulting reduced number of available

timeslots or carriers is not sufficient to maintain current or one less than the
current GPRS configurations.

An RTF cannot be unequipped if there exist Trace Criteria with scope as the
specified RTF.

RSL

NOTE
The unequip command does not allow unequipping an RSL from a 16 kbit/s site
using dynamic allocation if it causes the reserved cell capacity to exceed the
total terrestrial backing resources for the BTS network. The unequip command
automatically unequips the additional 16 K RSL when a 16 K RSL is being
unequipped as part of a closed loop DYNET.

SITE

NOTE
The unequip command for a SITE device at a Horizonmicro BTS automatically
unequips any DHP devices that exist at that BTS site.

A SITE cannot be unequipped if Trace Criteria with scope as the specified

SITE exists.

XBL

AXCDR

ABSS

3-636 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Standby devices

The following devices or functions can only be unequipped using the unequip command if
they are standby devices. These devices can be unequipped with the system in or out of the
SYSGEN ON mode.
BSP

BTP

When unequipping BTPs from M-Cell sites, BTP 0 must be the last BTP unequipped.

The BTP device (a processor card within a BTS site) manages the auto-unequip (and auto-equip)
of the MSI device 0 0 0 (with six associated MMS devices) at a BTS site with a Horizon II
controlling cabinet.

SYSGEN on mode

The following devices or functions can only be unequipped using the unequip command when
the system is in the SYSGEN ON mode:
OMF (BSC only)

The LCF can be unequipped using the unequip command if no sites exist on the LCF. The LCF is
unequipped with the system in or out of the SYSGEN mode. The system does not have to be
locked when the LCF is unequipped outside the SYSGEN ON mode.

The last KSW in a system cannot be unequipped using the unequip command. The SITE must be
unequipped using the unequip command to remove the last KSW from the database.

Format

Syntax

unequip <location> <dev/func_name> <id1> <id2> <id3>

Input parameters

location

Specifies the location of the device or function:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

dev/func_name

Literal that uniquely identifies the device or function.

68P02901W23-T 3-637
Jan 2010
Format Chapter 3: Device/function related commands

The following devices and functions are entered:

AXCDR CSFP GDS OML

ABSS DHP GPROC PATH
BSP DPROC GSL PCU
BTP DRI KSW RSL
CAB DYNET LCF RTF
CBL EAS MSI SITE
CIC GBL MTL XBL
COMB GCLK OMF PSI
OPL

NOTE
The unequip command supports the unequipping of extension cabinets of type
TCU_2, TCU_6, HORIZONMACRO_EXT, and Horizon II macro provided the cabinet
is locked and no DRIs or EASs are equipped to the cabinet. No other cabinet types
are supported.

The following GPRS devices can be used with this command:

DPROC GDS PCU

GBL GSL

NOTE
The PCU location must be specified when unequipping the GPRS devices, except
for the PCU itself. To unequip the PCU, specify the BSC for the location. Child
dependency can exist when unequipping the PCU, except for GDS and GSL; that is,
GBL, DPROC, MSI, and NSVC can exist when the PCU is unequipped.

id1

First identifier. This definition varies with each device or function.

When unequipping an EAS, only the first identifier is required. The following ranges of values
are entered:

0 to 7 InCell sites
0 to 15 M-Cell sites

id2

Second identifier. This definition varies with each device or function.

When unequipping a PATH, the range varies depending on whether the BTS uses dynamic
allocation. The following ranges of values are entered:

3-638 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

0 to 9 valid values if the terminating BTS does not use dynamic allocation
6 to 9 valid values if the terminating BTS uses dynamic allocation

id3

Third identifier. This definition varies with each device or function.

CIC syntax

A form of syntax is available for each method of specifying a CIC.

The following CIC syntax applies to local transcoding:

unequip <location> CIC <cic_num1>

unequip <location> CIC <cic_num1> TO <cic_num2>

unequip <location> CIC <mms_id1> <mms_id2>

unequip <location> CIC <mms_id1> <mms_id2> <timeslot1>

unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2>

The following CIC syntax applies to remote transcoding:

unequip <location> CIC <cic_num1>

unequip <location> CIC <cic_num1> TO <cic_num2>

unequip <location> CIC <mms_id1> <mms_id2>

unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> <group>

unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> *

unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2>

<group2>

CIC

Literal that uniquely identifies the CIC device.

cic_num1

First CIC device number.

cic_num2

Last CIC device number in a range.

mms_id1

First MMS identifier.

mms_id2

Second MMS identifier, or last in a range if TO is used.

timeslot1

First timeslot.

timeslot2

68P02901W23-T 3-639
Jan 2010
Examples Chapter 3: Device/function related commands

Second timeslot, or last in a range if TO is used.

group1

First group.

group2

Second group.

Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

Examples

Example 1

In this example, an MSI is deleted from the CM database:

unequip 2 msi 2 0 0

Where: is:
2 location
msi dev/func_name
2 id1
0 id2
0 id3

System response

COMMAND ACCEPTED

Example 2

This example unequips PCU 0 from a BSC.

unequip 0 pcu 0

Where: is:
0 location
pcu device_name
0 id1

3-640 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

COMMAND ACCEPTED

Example 3

This example unequips a GDS with a warning that there are not enough GDS resources to
handle PDTCHs.

unequip pcu GDS 1

Where: is:
pcu location
GDS device_name
1 id1

System response

COMMAND ACCEPTED
WARNING: Insufficient GDS resources available for all PDTCHs on the PCU.

Example 4

This example unequips a PSI device.

NOTE
The PSI device has to be locked before unequipping.

Unequip the GDS device associated with the PSI before unequipping the PSI device.

unequip bsc psi 1

Where: is:
bsc location
psi device_name
1 id1

System response

COMMAND ACCEPTED

68P02901W23-T 3-641
Jan 2010
Examples Chapter 3: Device/function related commands

Example 5

In this example, the operator attempts to unequip Horizon II micro extension cabinet 15 0
0 which is unlocked.

unequip 5 CAB 15 0 0

Where: is:
5 location
CAB device_name
15 id1
0 id2
0 id3

System response

COMMAND REJECTED: Device is not locked and cannot be unequipped

Example 6

This example unequips RTF with ext_pdchs >0, when gprs_enabled = 1 in the cell.

unequip 62 rtf 2 0

Where: is:
62 location
rtf device_name
2 id1
0 id2

System response

COMMAND REJECTED: gprs_enabled shall be disabled before unequip RTF with

ext_pdchs >0.

3-642 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 7

{26638}

This example unequips the GBL 0, GBL is locked, but the related ETH is unlocked.

unequip pcu gbl 0

Where: is:
pcu location
gbl device_name
0 id1

System response

COMMAND REJECTED: Related ETH should be locked before unequip GBL.

Example 8

{34371G}

This example attempts to unequip the standby BTP with a BBU attached.

unequip 23 btp 1

Where: is:
23 location
btp device_name
1 id1

System response

WARNING: Associated BBU will be auto-unequipped by this command

Are you sure (y=yes,n=no)?y

COMMAND ACCEPTED

68P02901W23-T 3-643
Jan 2010
References Chapter 3: Device/function related commands

Example 9

{34371G}

This example unequips an (R)CTU4 DRI on site 23 where all associated DRI devices in (R)CTU4
are locked.

unequip 23 DRI 0 3 0

Where: is:
23 location
DRI device_name
0 id1
3 id2
0 id3

System response

COMMAND ACCEPTED

References

Related commands

disp_equipment on page equip on page 3-445 lock_device on page 3-478

3-315
shutdown_device on page state on page 3-576 unlock_device on page 3-645
3-563

3-644 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference unlock_device

unlock_device

Description

The unlock_device command unlocks a specified device to free it for use.

Security level 2
Supported by OMC-R GUI Yes
Command type B (operator actions required)
Prerequisites This command is not allowed while in SYSGEN ON mode.
This command is only valid when the device is in the
LOCKED state. The location must be bsc or 0 when
specifying the device, or pcu if unlocking a GPRS device.
Operator actions Lock the device before entering this command. To unlock a
PCU device, the GPRS feature must be unrestricted. Also
the PCU device identifier must be specified.

Format

Syntax

unlock_device <location> <device_name> <device_id1> <device_id2> <device_id3>

Input parameters

location

Specifies the location of the device:

0 or bsc BSC
1 - 140 BTS
pcu or pcu_0 PCU

device_name

Literal that uniquely identifies the device.

68P02901W23-T 3-645
Jan 2010
Format Chapter 3: Device/function related commands

The following devices can be unlocked using this command:

ABSS AXCDR {34371G} BBU BSP BTP

CAB CAGE CBL CIC COMB
CSFP DHP DPROC DRI EAS
GBL GCLK GDS GPROC GSL
KSW MMS MSI MTL OML
OPL PATH PCU RSL SBUS
SITE XBL

NOTE
The unlock command supports the unlocking of extension cabinets of type TCU_2,
TCU_6, and HORIZONMACRO_EXT. No other cabinet types are supported.

The following GPRS only devices can be unlocked at the PCU using this command:

DPROC GBL GDS GSL PCU

device_id1

First device identifier. This definition varies with each device.

device_id2

Second device identifier. This definition varies with each device.

device_id3

Third device identifier. This definition varies with each device.

CIC syntax

A form of syntax is available for each method of specifying a CIC.

The following CIC syntax applies to local transcoding:

unlock_device <location> CIC <cic_num1>

unlock_device <location> CIC <cic_num1> TO <cic_num2>

unlock_device <location> CIC <mms_id1> <mms_id2>

unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1>

unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2>

The following CIC syntax applies to remote transcoding:

unlock_device <location> CIC <cic_num1>

unlock_device <location> CIC <cic_num1> TO <cic_num2>

unlock_device <location> CIC <mms_id1> <mms_id2>

3-646 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group>

unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> *

unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO

<timeslot2> <group2>

CIC

Literal that uniquely identifies the CIC device.

cic_num1

First CIC device number.

cic_num2

Last CIC device number in a range.

mms_id1

First MMS identifier.

mms_id2

Second MMS identifier, or last in a range if TO is used.

timeslot1

First timeslot.

timeslot2

Second timeslot, or last in a range if TO is used.

group1

First group.

group2

Second group.

Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

68P02901W23-T 3-647
Jan 2010
Examples Chapter 3: Device/function related commands

Examples

Example 1

In this example, an MMS with the ID 0 at the BSC is unlocked:

unlock_device bsc mms 0 0 0

Where: is:
bsc location
mms device_name
0 device_id1
0 device_id2
0 device_id3

System response

COMMAND ACCEPTED

Example 2

This example unlocks a range of CICs (remote transcoder) specifying them by their MMS,
TS, and group.

unlock_device bsc cic 2 1 3 1 TO 5 1

Where: is:
BSC location
CIC device_name
2 first MMS ID
1 second MMS ID
3 timeslot 3
1 group 1
5 timeslot 5
1 group 1

System response

COMMAND ACCEPTED

3-648 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 3

This example unlocks a GPRS PICP MSI at the first PCU.

unlock_device pcu_0 msi 3

Where: is:
pcu_0 location
MSI device_name
3 first MSI ID

System response

COMMAND ACCEPTED

Example 4

This example unlocks the ETH device.

unlock_device pcu_0 eth 2 0 0

Where: is:
pcu_0 location
ETH device_name
2 first ETH ID
0 second ETH ID
0 third ETH ID

System response

COMMAND ACCEPTED

Example 5

This example unlocks a cage. No warning is displayed.

unlock_device bsc cage 2 0

Where: is:
bsc location
cage device_name
2 device_id1
0 device_id2

68P02901W23-T 3-649
Jan 2010
Examples Chapter 3: Device/function related commands

System response

COMMAND ACCEPTED

Example 6

{34371G}

This example attempts to unlock the standby BTP 1 0 0 and there is a BBU attached to the BTP.

unlock_device 23 btp 1 0 0

Where: is:
23 location
btp device_name
1 device_id1
0 device_id2
0 device_id3

System response

COMMAND ACCEPTED

Example 7

{34371G}

This example attempts to unlock BBU 0 0 0.

unlock_device 23 bbu 0 0 0

Where: is:
23 location
bbu device_name
0 device_id1
0 device_id2
0 device_id3

System response

COMMAND ACCEPTED

3-650 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related commands

disp_equipment on page equip on page 3-445 lock_device on page 3-478

3-315
state on page 3-576 unequip on page 3-633

68P02901W23-T 3-651
Jan 2010
_bss_data,6 Chapter 3: Device/function related commands

_bss_data,6

Description

The new per BSS element, _bss_data,6 indicates whether the system information 2quater for
TD-SCDMA neighbors are built in standard or workaround mode.

This parameter may be changed inside and outside SYSGEN mode without warning.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter is modified only when the TD-SCDMA
interworking feature is unrestricted (tdOpt) and disabled
(td_enabled = 0).

Syntax

Change command string

chg_element _bss_data,6 <value> <location>

Display command string

disp_element _bss_data,6 <location>

Values

Value type Boolean

Valid range 0 to 1
0 Using standard TD-SCDMA SI2quater message
1 Using workaround TD-SCDMA SI2quater message
Default value 0

3-652 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference _bss_data,10

_bss_data,10

Description

The _bss_data,10 parameter enables and disables the function of the cage management
feature. This parameter can be accessed and updated both in and out of SYSGEN mode.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element _bss_data,10 <value> <location>

Display command string

disp_element _bss_data,10 <location>

Values

Value type Boolean

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 3-653
Jan 2010
Values Chapter 3: Device/function related commands

3-654 68P02901W23-T
Jan 2010
 Chapter

UNIX commands

Selected UNIX commands provide a useful addition to MMI commands.

This chapter describes several UNIX commands that may be used from the MMI.

The following UNIX commands are described:

alias

help

history

man

unalias

Each UNIX command is described separately using the following command reference layout:

Command title - the actual command reference.

Description - providing a description of the command operation, including information on the

command security level, whether supported by OMC-R GUI, the type of command, and the
prerequisites for the command that the system accepts.

Format - giving the command line syntax and descriptions of the command parameters.

Examples - providing specific examples of command input and the resulting system response.

References - giving any related commands.

68P02901W23-T 4-1
Jan 2010
alias Chapter 4: UNIX commands

alias

Description

The alias command creates an alias for an MMI command. If no parameters are entered, a
list of active aliases is displayed.

The maximum length which can be entered is 256 characters. These characters include the
command name (alias) and the alias name.

The alias applies only to the GPROC for which it is set. A login to a different GPROC does not
recognize the alias.

Security level Any

Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

alias [<alias_name>'<alias_text>']

Input parameters

alias_name

Name of the alias.

alias_text

Any valid MMI command which can be just the command name or a command and parameters.
Enclose the alias_text in single quotes.

4-2 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Example

Example

This example creates an alias called list which executes the command string.disp_equipment
bsc:

alias list 'disp_equipment bsc'

Where: is:
list alias_name
disp_equipment bsc alias_text

System response:

COMMAND ACCEPTED

References

Related commands

unalias on page 4-10.

68P02901W23-T 4-3
Jan 2010
help Chapter 4: UNIX commands

help

Description

The help command displays help information about the specified command. If no command is
specified, a list of all available commands is displayed.

Additional online information may be displayed by using the man command.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

help [<command>]

Input parameter

command

String specifying an MMI command.

Example

This example displays help for the chg_level command.

help chg_level

Where: is:
chg_level command

System response

chg_level: Changes the current security level

4-4 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related command

man on page 4-8.

68P02901W23-T 4-5
Jan 2010
history Chapter 4: UNIX commands

history

Description

The history command displays a numbered list of previously entered MMI commands.

This command may also be used to repeat one of the commands displayed in the listing.

Security level Any

Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

history [<num_commands>]

or
!<num_commands>

or
!!

Input parameter

num_commands

The number of previously entered commands to display. The default is 23. If this parameter is
not entered, the last 23 commands are displayed.

4-6 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Examples

Example 1

This example lists the last three commands that were entered.

history 3

Where: is:
3 number of commands.

System response

11 disp_level

12 shg_level

13 disp_dte

Example 2

Using the output of the history command from the previous example, the following command
string executes the statement contained in command number 13 shown in the command
history list:
!13

In this case, it is the disp_dte command.

The command string

!!

executes the last command again.

68P02901W23-T 4-7
Jan 2010
man Chapter 4: UNIX commands

man

Description

The man command is used to display detailed help information about the specified command.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

man <command>

Input parameter

command

String specifying an MMI command.

Example

This example shows the manual text presented with the alias command.

man alias

Where: is:
alias command

4-8 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

Command: alias [<alias_name> '<alias_text>']

Security Level: Can be executed from any security level.

Function: Create an alias for an MMI command. If no

parameters are entered, a list of active

aliases are displayed.

<alias_name> The name of the alias.

<alias_text> Any valid MMI command. This can be just the

command name, or a command and parameters.

This MUST be enclosed in single quotes.

Example 1: Create an alias called list which

executes disp_equipment bsc:

alias list 'disp_equipment bsc'

Example 2: List all active aliases:

alias

References

Related command

help on page 4-4.

68P02901W23-T 4-9
Jan 2010
unalias Chapter 4: UNIX commands

unalias

Description

The unalias command removes the alias <alias_name> from the specific GPROC at which
it was set.

Security level Any

Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites None

Format

Syntax

unalias <alias_name>

Input parameter

alias_name

Remove the name of the alias.

Example

This example removes the alias named list.

unalias list

Where: is:
list alias_name

System response

COMMAND ACCEPTED

4-10 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related command

alias on page 4-2.

68P02901W23-T 4-11
Jan 2010
References Chapter 4: UNIX commands

4-12 68P02901W23-T
Jan 2010
 Chapter

Statistics commands

Statistics commands are MMI commands used to perform statistical operations and obtain
statistical information.

This chapter describes the statistical operations and different types of statistical information
that can be obtained using MMI statistics commands, and provides reference information
for each MMI statistical command.

The statistics commands are described separately in alphabetical order using the following
command reference layout:

Command title - the actual command reference.

Description - providing a description of the command operation, including information on the

command security level, whether supported by OMC-R GUI, the type of command, and the
prerequisites for the system to accept the command.

Format - giving the command line syntax and descriptions of the command parameters.

Examples - providing specific examples of command input and the resulting system response.

References - giving any related information or related commands.

NOTE
Descriptions of individual statistics are described in the Maintenance Information:
GSM Statistics Application (68P02901W56) manual.

68P02901W23-T 5-1
Jan 2010
Statistical operations and information Chapter 5: Statistics commands

Statistical operations and information

The following MMI commands are used to obtain statistical information and perform statistical
operations:
chg_stat_prop (see chg_stat_prop on page 5-5).

disp_enable_stat (see disp_enable_stat on page 5-14).

disp_interval (see disp_interval on page 5-24).

disp_stat_prop (see disp_stat_prop on page 5-26).

disp_stats (see disp_stats on page 5-39).

stat_mode (see stat_mode on page 5-56).

Statistical operations

The statistical commands perform the following statistical operations:

Enable/disable statistics.

Display/modify statistics for devices or cells.

Monitor system statistics over specified time intervals.

Monitor active (enabled) system statistics.

Report statistical data.

Statistical information

The system generates the statistical information. The system operators use the information for:
Monitoring the quality of service.

Fault finding.

Optimize system performance.

Network planning.

System installation and commissioning.

5-2 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Counter statistics

Statistical information is gathered in the form of:

Counter statistics.

Duration statistics.

Gauge statistics.

Distribution statistics.

Counter statistics

Counter statistics represent the number of occurrences of an event. The monitored event is
specified as the database parameter in the chg_element command. Counter statistics may only
be enabled and disabled.

Certain counter statistics have associated alarms. If a threshold is reached, an alarm is sent
to the OMC-R.

Duration statistics

Duration (or total time) statistics involve the use of a timer to collect a cumulative time value.
The timer starts when an event begins and stops when it ceases. The event data are recorded
for statistical analysis. The resulting statistics express the total amount of time a particular
event occurred, as well as minimum, maximum, and mean durations (in milliseconds). Duration
statistics may only be enabled and disabled.

Gauge statistics

Gauge statistics report the maximum and mean values of a statistic for an interval. The
IDLE_TCH_INTF_BAND0 statistic is an example of a gauge statistic.

While a gauge statistic may result in the report of a reported negative value, the cumulative
value may not be a negative value. A check is performed before calculating the mean value, and
if the result is a negative number, the mean value is set to zero.

Threshold event reporting

An alarm threshold may be specified for gauge statistics.

If a threshold is reached, the alarm is reported to the OMC-R.

Interval expiry

Interval expiry is the end of a statistic interval. The mean and maximum gauge statistic values
at the interval expiry are saved and reset to 0 at the interval expiry.

68P02901W23-T 5-3
Jan 2010
Distribution statistics Chapter 5: Statistics commands

Distribution statistics

Two types of distribution statistics, normal and weighted, are used to record all events or state
changes reported by some application processes.

Normal distribution statistics represent the number of times the value of an event or state
change occurs within the range of a specific bin. The size of the upper and lower bins in which
the data is collected determines the range of a bin. For example, if the range of a bin is 10 to 20,
and the application process reports a value of 15 three times, the statistical value is 3.

Weighted distribution statistics record the length of time (in milliseconds) that an element is at
a specific value. The statistical value displayed is the cumulative time of the events occurring
within that range of a bin. For example, if the range of a bin is 10 to 20, and the application
process reports six events with a value of 15 lasting 12 milliseconds each, the statistical value
is 72.

Statistics descriptions

Refer to the Maintenance Information: GSM Statistics Application (68P02901W56) for detailed
information on each statistical parameter.

5-4 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference chg_stat_prop

chg_stat_prop

Description

The chg_stat_prop command changes the properties of statistics. The specific properties that
may be changed depend on the statistic type.
If an alarm is associated with the statistic, the alarm threshold may be changed for counter,
counter array, and gauge statistics.

Bin ranges may be changed for normal and weighted statistics.

Properties may not be changed for duration (total time) statistics.

When the chg_stat_prop command is entered the system displays a series of prompts. The
specific prompts depend on the statistic type. Refer to References/Related information for
explanations of the prompts associated with each statistic.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The GPRS feature must be unrestricted to display PCU
statistics. The EGPRS feature must be unrestricted to
display EGPRS associated statistics.

NOTE
Enter this command only at the BSC. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

chg_stat_prop <meas_type> [location] [<cell_desc>]

chg_stat_prop <meas_type> all

68P02901W23-T 5-5
Jan 2010
Examples Chapter 5: Statistics commands

Input parameters

meas_type

Specifies the name of the statistic.

location

Specifies the site location:

0 or bsc BSC
1 - 140 BTS
all All sites

cell_desc

The GSM cell ID of the cell for which statistics properties are to be modified, preceded by
cell_number=.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command may be entered in place of the
cell_number. When the cell name is entered, place it inside double quotation marks and
precede by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

The value all is also a valid input for the cell_desc. If entered, the mode for the statistic
changes for all cells at the specified site.

Examples

Example 1

This example changes the alarm threshold for the RF_LOSSES_TCH statistic for cell number 5 4
3 2 1 61698 34776 at site 1.

chg_stat_prop rf_losses_tch 1 cell_number= 5 4 3 2 1 61698 34776

Where: is:
rf_losses_tch meas_type
1 location
5 4 3 2 1 61698 34776 cell_desc

5-6 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Enter the threshold for total value: 2

COMMAND ACCEPTED

Example 2

This example changes minimum and maximum values for two bins of the BUSY_TCH statistic
for all cells at site 1.

chg_stat_prop busy_tch 1 all

Where: is:
busy_tch meas_type
1 location
all all cells at the specified site.

System response

Enter the bin number(s): 0,1

Enter the min value for bin 0: 0
Enter the max value for bin 0: 5
Enter the min value for bin 1: carriage return
Enter the max value for bin 1: 7

COMMAND ACCEPTED

Example 3

This example changes the alarm threshold for the RF_LOSSES_TCH statistic for PCS1900
cell number 543 721 61698 34776 at site 1.

chg_stat_prop rf_losses_tch 1 cell_number= 543 721 61698 34776

Where: is:
rf_losses_tch meas_type
1 location
543 721 61698 34776 cell_desc

68P02901W23-T 5-7
Jan 2010
Examples Chapter 5: Statistics commands

System response

Enter the threshold for total value: 2

COMMAND ACCEPTED

Example 4

This example changes the threshold of MTP_SL_ERROR_RATE_HSP BSS statistics.

chg_stat_prop MTP_SL_ERROR_RATE_HSP

System response

Enter the threshold for total value: 2

COMMAND ACCEPTED

Example 5

This example changes the properties of the link statistic RSL_TX_OCTETS.

chg_stat_prop RSL_TX_OCTETS

System response

COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

Example 6

This example changes the properties of the cell statistic UL_RLC_STALLED_BLKS when the
GPRS feature is unrestricted/restricted.

chg_stat_prop UL_RLC_STALLED_BLKS cell 0 0 1 0 1 1 1

Where: is:
UL_RLC_STALLED_BLKS meas_type
0010111 cell_desc

System response

COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

5-8 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 7

This example changes the properties of the cell statistic: EXT_UL_USF_USAGE or

EXT_UL_EXITS when Extended Uplink TBF feature is unrestricted.

chg_stat_prop EXT_UL_USF_USAGE cell 0 0 1 0 1 1 1

Where: is:
EXT_UL_USF_USAGE meas_type
0010111 cell_desc

System response

COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

Example 8

This example changes the properties of the cell statistic IA_IAR_MSGS_PER_AGCH.

chg_stat_prop IA_IAR_MSGS_PER_AGCH cell_number= 0 0 1 0 1 1 1

Where: is:
IA_IAR_MSGS_PER_AGCH meas_type
0010111 cell_desc

System response

COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

Example 9

This example changes the properties of the cell statistic CS_PAGING_MSGS_FROM_MSC.

chg_stat_prop CS_PAGING_MSGS_FROM_MSC cell_number= 0 0 1 0 1 1 1

Where: is:
CS_PAGING_MSGS_FROM_MSC meas_type
0010111 cell_desc

System response

COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

68P02901W23-T 5-9
Jan 2010
Examples Chapter 5: Statistics commands

Example 10

This example changes the properties of the cell statistic UL_LLC_TRANS_TIME when GPRS
feature is unrestricted or restricted.

chg_stat_prop UL_LLC_TRANS_TIME cell 0 0 1 0 1 1 1

Where: is:
UL_LLC_TRANS_TIME meas_type
0010111 cell_desc

System response

COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

Example 11

{34371G}

This example changes the properties of the statistic CPU_USAGE.

chg_stat_prop cpu_usage

Where: is:
cpu_usage meas_type

System response

Enter the bin number(s): 0

Enter the min value for bin 0: 0
Enter the max value for bin 0: 10

COMMAND ACCEPTED

5-10 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 12

{34371G}

This example changes the properties of the statistic DSP_USAGE.

NOTE
The bin range properties are modified depending on the normal distribution statistic
type.

chg_stat_prop dsp_usage

Where: is:
dsp_usage meas_type

System response

Enter the bin number(s): 0

Enter the min value for bin 0: 0
Enter the max value for bin 0: 10

COMMAND ACCEPTED

Example 13

This example attempts to modify the properties of the cell statistic DL_RADIO_BLKS_5_TS_SIN-
GLE.

chg_stat_prop DL_RADIO_BLKS_5_TS_SINGLE cell 0 0 1 0 1 1 1

Where: is:
DL_RADIO_BLKS_5_TS_SINGLE meas_type
0010111 cell_desc

System response

COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

68P02901W23-T 5-11
Jan 2010
References Chapter 5: Statistics commands

References

Related information

Table 5-1 lists the counter and gauge statistic type prompts for changing the alarm threshold.

Table 5-1 Counter and gauge statistic type prompts

Prompt Valid range Description

Enter the alarm 0 to 2147483647 If a <carriage return> is entered in
threshold response to this prompt, the current
value does not change.
If an alarm is not associated with
the specified statistic, the command
is rejected and this prompt is not
presented.

Table 5-2 lists the normal and weighted distribution statistic type prompts for changing bin
value.

Table 5-2 Normal and weighted distribution statistic type prompts

Prompt Valid range Description

Enter the bin 0 to 9 Multiple bin numbers may be entered
number(s): by separating each bin number with
a space or comma.
Enter the min value for The minimum value that This prompt repeats for each bin
bin n: may be entered is 0 number (n) entered in response to
the first prompt.
If a <carriage return> is entered
in response to the first prompt, the
current value is not changed.
Enter the max value for The maximum value This prompt repeats for each bin
bin n: that may be entered is number (n) entered in response to
2147483647 the first prompt.
If a <carriage return> is entered
in response to the first prompt the
current value is not changed.

NOTE
The system rejects the command if the minimum bin value is greater than the
maximum bin value for a distribution statistic.

5-12 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Related commands

disp_element on page 3-294

disp_enable_stat on page 5-14

disp_interval on page 5-24

disp_stats on page 5-39

68P02901W23-T 5-13
Jan 2010
disp_enable_stat Chapter 5: Statistics commands

disp_enable_stat

Description

The disp_enable_stat command displays the status of statistics. Specific listings generated by
this command depend on the argument entered with the command.

This command displays enabled statistics by cell, location, or all statistics in the system.

If no arguments are entered with the command, a listing showing all the enabled statistics is
displayed.

If a Cell ID (or name) is entered with the command, a listing of enabled statistics at the specified
cell is displayed.

If bss is entered with the command, a listing of the enabled statistics in the BSS is displayed.

A specific statistic may be entered as the meas_type. When the name of a BSS-wide statistic is
entered, the command displays the state of the statistic. When the name of a per-cell statistic is
entered, the command displays the GSM cell ID of the cells which have the statistic enabled.

If a Location ID is entered with the command, a listing of the enabled statistics at the specified
location is displayed.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_enable_stat

disp_enable_stat <bss>

disp_enable_stat <location>

disp_enable_stat <meas_type>

disp_enable_stat [<cell_desc>]

5-14 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Input parameters

cell_desc

The GSM cell ID of the cell for which the enabled statistics are displayed, preceded by
cell_number=. A cell_desc is specified only for per cell, per neighbor cell, and per timeslot
statistics.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command may be entered in place of the
cell_number. When the cell name is entered, place inside double quotation marks and precede
by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

bss

Specifies the BSS.

location

Specifies the site location:

0 or bsc BSC
1 - 140 BTS

meas_type

Specifies the name of the statistic.

Examples

Example 1

In this example, an abbreviated list of all the enabled statistics is displayed when the
disp_enable_stat command is entered with no arguments. Actual output from the system
shows all statistics. The output includes all non-cell and individual cell statistics.

disp_enable_stat

NOTE
The text that follows shows part of a typical display. Such a display continues until all
the enabled statistics have been displayed.

68P02901W23-T 5-15
Jan 2010
Examples Chapter 5: Statistics commands

System response

Enabled Non-Cell Statistics

ma_req_from_msc_fail

page_req_from_msc_fail

ho_req_msc_proto

mtp_sl_fail

mtp_sl_fibr

mtp_sl_ack

...

...

mtp_msu_tx

mtp_msu_rx

sl_congestion

sl_stop_congestion

msu_disgarded

congestion_lost_msu

sif_sio_rx_opc

sif_sio_tx_dpc

sif_sio_type

routing_syntax

routing_unknown

sccp_msgs

sccp_msgs_tx

sccp_msgs_rx

invalid_frames_rx

i_frames_rx

i_frames_tx

sabm_tx_frmr

n2_expiry

mtp_link_ins

mtp_unavailable

mtp_local_mgt

mtp_remote_mgt

5-16 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

mtp_linkfail

mtp_remote_proc

mtp_local_busy

mtp_congestion

cpu_usage

...

...

PRP_PD_DEMAND

GCI_FOR_16 KPD_DEMAND

GCI_FOR_32 KPD_DEMAND

GCI_FOR_64 KPD_DEMAND

TOTAL_GCI_FOR_PD_DEMAND

...

...

EnabledStatistics for Cell 0 0 1 0 1 1 2

egprs_avail_pdtch

rf_losses_tch

rf_losses_sd

intra_cell_ho

in_inter_ho

out_inter_ho

intra_bss_ho

access_per_rach

...

...

ACCESS_PER_PCH

ALLOC_SDCCH

...

NUM_CELL_RESEL_CELL

NUM_CELL_RESEL_CELL_PCCN

NUM_CELL_RESEL_CELL_SUCC

NUM_CELL_RESEL_NEI

NUM_CELL_RESEL_NEI_PCCN

68P02901W23-T 5-17
Jan 2010
Examples Chapter 5: Statistics commands

NUM_CELL_RESEL_NEI_SUCC

...

RF_LOSSES_SD

RF_LOSSES_TCH

TCH_Q_REMOVED

...

...

PACKET_SYSINFO_REQ

PACKET_SYSINFO_RESP

...

...

SDCCH HO (see NOTE)

SMS_INIT_ON_SDCCH_HO_OUT

...

...

tch_delay

intf_on_idle

busy_tch

busy_sdcch

ber

Example 2

This example displays the sites and related cells for which the CELL statistic total calls
is enabled.

disp_enable_stat total_calls

5-18 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

Statistic total_calls enabled for the following cells at site 18

----------------------------------------------------------------
543 21 F333h 028Ah
543 21 F333h 028Bh
54321 F333h 028Ch
Statistic total_calls enabled for the following cells at site 30
----------------------------------------------------------------
543 21 F333h 2128h
Statistic total_calls enabled for the following cells at site 31
----------------------------------------------------------------
543 21 F333h 0031h
Statistic total_calls enabled for the following cells at site 32
----------------------------------------------------------------
543 21 F333h 2127h
Statistic total_calls enabled for the following cells at site 36
----------------------------------------------------------------
543 21 F333h 2124h
543 21 F333h 2125h
543 21 F333h 2126h

Example 3

This example shows that the GPRS_CELL_CONGESTION statistic is enabled.

disp_enable_stat GPRS_CELL_CONGESTION

System response

Statistic gprs_cell_congestion is enabled.

Example 4

This example displays the enabled SS7 link MTP_SL_ERROR_RATE_HSP statistics.

disp_enable_stat MTP_SL_ERROR_RATE_HSP

System response

Statistic mtp_sl_error_rate_hsp is enabled.

68P02901W23-T 5-19
Jan 2010
Examples Chapter 5: Statistics commands

Example 5

This example displays all statistics enabled under BSS.

disp_enable_stat BSS

System response

RSL_RX_OCTETS
RSL_TX_OCTETS
RSL_LINK_INS
.
.

Example 6

This example displays all the enabled statistics for all the cells at site 1.

disp_enable_stat 1

System response

Enabled statistics for Cell 0 0 1 01 0001h 0001h

...
UL_RLC_STALLED_BLKS
UL_RLC_NACK_BLKS
...

Example 7

This example displays all the enabled statistics for all the cells at site 1.

disp_enable_stat 1

5-20 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

.
.
Enabled Statistics for Cell 0 0 1 0 1 1 2
rf_losses_tch
rf_losses_sd
rf_losses_tch_hr
intra_cell_ho
in_inter_ho
out_inter_ho
intra_bss_ho
access_per_rach
IA_IAR_MSGS_PER_AGCH
.
.
.

Example 8

This example displays all the enabled statistics for all the cells at site 1.

disp_enable_stat 1

System response

.
.
Enabled Statistics for Cell 0 0 1 0 1 1 2
rf_losses_tch
rf_losses_sd
rf_losses_tch_hr
intra_cell_ho
in_inter_ho
out_inter_ho
intra_bss_ho
access_per_rach
cs_paging_msgs_from_msc
.
.
.

68P02901W23-T 5-21
Jan 2010
Examples Chapter 5: Statistics commands

Example 9

This example displays all the enabled statistics for all the cells at site 1.

disp_enable_stat 1

System response

Enabled statistics for Cell 0 0 1 01 0001h 0001h

.
.
.
UL_LLC_DATA_VOLUME
DL_LLC_DATA_VOLUME
UL_LLC_TRANS_TIME
DL_LLC_TRANS_TIME
.
.
.

Example 10

{34371G}

This example displays all the enabled statistics.

disp_enable_stat CPU_USAGE

System response

Statistic cpu_usage is enabled.

Example 11

{34371G}

This example displays all the enabled statistics.

disp_enable_stat DSP_USAGE

System response

Statistic dsp_usage is enabled.

5-22 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Example 12

This example displays all the enabled statistics for all the cells at site 1.

disp_enable_stat 1

System response

Enabled statistics for Cell 0 0 1 01 0001h 0001h

.
.
.
DL_RADIO_BLKS_5_TS_SINGLE
.
.
.

References

Related commands

disp_element on page 3-294

stat_mode on page 5-56

disp_interval on page 5-24

disp_stats on page 5-39

68P02901W23-T 5-23
Jan 2010
disp_interval Chapter 5: Statistics commands

disp_interval

Description

The disp_interval command displays the start times associated with each of the system
statistics intervals.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites This command is not allowed in SYSGEN ON mode.

Format

Syntax

disp_interval

Input parameters

There are no input parameters associated with this command.

Example

This example shows a sample of the display the system produces when the disp_interval
command is entered.

disp_interval

5-24 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

Interval Start Time (HH:MM:SS)

-------- ---------------------

0 09:08:48

1 09:29:59

2 10:00:00

3 10:30:00

4 11:00:00

5 11:30:00

6 12:00:00

7 12:30:00

8 13:00:00

9 13:30:00

10 14:00:00

11 14:30:00

References

Related commands

disp_element on page 3-294

disp_enable_stat on page 5-14

chg_element on page 3-112

disp_stats on page 5-39

68P02901W23-T 5-25
Jan 2010
disp_stat_prop Chapter 5: Statistics commands

disp_stat_prop

Description

The disp_stat_prop command displays the following properties associated with a statistic:
Mode (enabled/disabled).

Type (per link, per timeslot, per cell, and so on).

Object type.

The statistic type determines the additional information displayed using the disp_stat_prop
command:
Alarm severity and threshold values display for counter and gauge statistics.

Bin ranges display for normal and weighted distribution statistics.

The statistical basis display for percent statistics.

Duration values for duration statistics.

If the output generated by this command is large, it is paginated.

Security level 1
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites None

Format

Syntax

disp_stat_prop <meas_type>

disp_stat_prop <meas_type> [<cell_desc>]

disp_stat_prop <meas_type> <location> [<cell_desc>]

disp_stat_prop <meas_type> <location> all

5-26 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Input parameters

meas_type

The name of the statistic.

location

Specifies the site location:

1 - 140 BTS
all All sites

cell_desc

The GSM cell ID of the cell for which statistics properties are displayed, preceded by
cell_number=.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command may be entered in place of the
cell_number . When the cell name is entered, place inside double quotation marks and precede
by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

The value all is also a valid input for the cell_desc. If entered, the mode for the statistic
changes for all cells at the specified site.

Examples

Example 1

This example displays the properties of the gauge statistic PRP_PD_DEMAND.

disp_stat_prop PRP_PD_DEMAND

Where: is:
PRP_PD_DEMAND meas_type

68P02901W23-T 5-27
Jan 2010
Examples Chapter 5: Statistics commands

System response

STATISTIC: PRP_PD_DEMAND SITE: 0

TYPE: PER DPROC OBJECT: GAUGE
ALARM ALARM
CELL# MODE SEVERITY THRESHOLD
------------------------------------- ---------- ---------- ---------
N/A ENABLED NO ALARM N/A

Example 2

This example displays the properties associated with the TOTAL_CALLS counter statistic for
cell number 5 4 3 2 1 61698 34776 at site 1.

disp_stat_prop total_calls cell_number= 5 4 3 2 1 61698 34776

Where: is:
total_calls meas_type
5 4 3 2 1 61698 34776 cell_desc

System response

STATISTIC: TOTAL_CALLS SITE: 1

TYPE: PER CELL OBJECT: COUNTER
ALARM ALARM
CELL# MODE SEVERITY THRESHOLD
------------------------------------- ---------- ---------- ---------
543 21 61698 (f102h) 34776 (87d8h) ENABLED NO ALARM N/A

Example 3

This example shows the properties associated with the ROUTING_UNKNOWN counter statistic
for site 1.

disp_stat_prop routing_unknown 1

Where: is:
routing_unknown meas_type
1 location

5-28 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

STATISTIC: ROUTING_UNKNOWN SITE: 1

N/A ENABLED WARNING 2147836
SITE: 0 CELL #: LAC = f222h CI = 8880h
MEAS_TYPE: CHANNELS_DISABLED
Gauge Value: 5 Max.: 5
TYPE: OTHER OBJECT: COUNTER
ALARM ALARM
CELL# MODE SEVERITY THRESHOLD
------------------------------------- ---------- ---------- ---------

Example 4

This example displays the properties associated with the TOTAL_CALLS counter statistic for all
cells at site 1.

disp_stat_prop total_calls 1 all

Where: is:

total_calls meas_type

1 location

all all cells at the specified location.

System response

STATISTIC: TOTAL_CALLS SITE: 1

TYPE: PER CELL OBJECT: COUNTER
ALARM ALARM
CELL# MODE SEVERITY THRESHOLD
------------------------------------- ---------- ---------- ---------
543 21 61698 (f102h) 34776 (87d8h) ENABLED NO ALARM N/A
543 21 61698 (f102h) 34777 (87d9h) ENABLED NO ALARM N/A
543 21 61698 (f102h) 34778 (87dah) ENABLED NO ALARM N/A
543 21 61698 (f102h) 34779 (87dbh) ENABLED NO ALARM N/A
543 21 61698 (f102h) 34780 (87dch) ENABLED NO ALARM N/A

68P02901W23-T 5-29
Jan 2010
Examples Chapter 5: Statistics commands

Example 5

This example displays the properties of the GPRS_CELL_CONGESTION counter array statistic.

disp_stat_prop GPRS_CELL_CONGESTION cell 0 0 1 0 0 1 1

Where: is:
GPRS_CELL_CONGESTION meas_type
0010011 cell_desc

System response

STATISTIC: GPRS_CELL_CONGESTION SITE: 1

TYPE: PER CELL OBJECT: COUNTER ARRAY
BIN# CAUSE
---- ------
0 >=0, <25%
1 >=25, <30%
2 >=30%, <35%
3 >=35, <40%
4 >=40, <45%
5 >=45%, <50%
6 >=50, <55%
7 >=55, <60%
8 >=60%, <65%
9 >=65, <70%
10 >=70, <75%
11 >=75%, <80%
12 >=80, <85%
13 >=85, <90%
14 >=90%, <95%
15 >=95%, <=100%
CELL# MODE ALARM SEVERITY ALARM THRESHOLD
------------------------------------------------------------------------
0 0 1 0 0 1 1 DISABLED NO ALARM N/A

Example 6

This example displays the properties of the BSS MTP_SL_ERROR_RATE_HSP statistics.

disp_stat_prop MTP_SL_ERROR_RATE_HSP

5-30 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

STATISTIC: MTP_SL_ERROR_RATE_HSP SITE: 0

TYPE: PER Link OBJECT: COUNTER

CELL# MODE ALARM ALARM

SEVERITY THRESHOLD

-------------------------------------------------------------

N/A ENABLED MAJOR 50

Example 7

This example displays the properties of the link statistic: RSL_TX_OCTETS.

disp_stat_prop RSL_TX_OCTETS

System response

STATISTIC: RSL_TX_OCTETS SITE: 0

TYPE: PER Link OBJECT: COUNTER

CELL# MODE ALARM ALARM

SEVERITY THRESHOLD

-------------------------------------------------------------

N/A ENABLED NO ALARM N/A

Example 8

This example displays the properties of the timeslot statistic.

disp_stat_prop RF_LOSSES_TCH 10 cell_number=0 0 1 0 1 1 1

Where: is:
rf_losses_tch stat_name
10 location
0010111 cell_desc

68P02901W23-T 5-31
Jan 2010
Examples Chapter 5: Statistics commands

System response

STATISTIC: RF_LOSSES_TCH SITE: 1

SITE: 11 CELL #: LAC=0001h CI=000Bh
RTF ID: 0 0
SITE: 11 CELL #: LAC=0001h CI=000Bh
TIMESLOT: 0 RTF ID = 0 0
MEAS_TYPE: RF_LOSSES_TCH
Total Count: 0
RX quality in uplink direction : 0
RX quality in downlink direction : 0
RX level in uplink direction : 0
RX level in downlink direction : 0
Timing Advance : 0
Sharp decrease of signal level : 0
Other : 0

Example 9

This example displays the properties of the UL_TBF_TIME_8PSK_3_TS cell statistic.

disp_stat_prop UL_TBF_TIME_8PSK_3_TS cell 0 0 1 0 1 1 1

Where: is:
UL_TBF_TIME_8PSK_3_TS meas_type
0010111 cell_desc

System response

STATISTIC: UL_TBF_TIME_8PSK_3_TS SITE: 1

TYPE: PER CELL OBJECT: COUNTER

CELL# MODE ALARM ALARM

SEVERITY THRESHOLD

-----------------------------------------------------------------

001 01 1 (0001h) 1 (0001h) ENABLED NO ALARM N/A

5-32 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 10

This examples displays the properties of the cell statistic: EXT_UL_USF_USAGE.

disp_stat_prop EXT_UL_USF_USAGE cell 0 0 1 0 1 1 1

Where: is:
ext_ul_usf_usage stat_name
0010111 cell_desc

System response

STATISTIC: EXT_UL_USF_USAGE SITE: 1

TYPE: PER CELL OBJECT: SMALL COUNTER ARRAY

CELL# MODE ALARM ALARM

SEVERITY THRESHOLD

-------------------------------------------------------------------

001 01 1 (0001h) 1 (0001h) ENABLED NO ALARM N/A

Example 11

This example displays the properties of the cell statistic IA_IAR_MSGS_PER_AGCH.

disp_stat_prop IA_IAR_MSGS_PER_AGCH cell 0 0 1 0 1 1 1

Where: is:
IA_IAR_MSGS_PER_AGCH meas_type
0010111 cell_desc

68P02901W23-T 5-33
Jan 2010
Examples Chapter 5: Statistics commands

System response

STATISTIC: IA_IAR_MSGS_PER_AGCH SITE: 1

TYPE: PER CELL OBJECT: COUNTER ARRAY
BIN# CAUSE
------------------------------------------------------------------------------
0 IA CS messages sent over CCCH
1 IA PS messages sent over CCCH
2 IAR CS messages sent over CCCH
3 IAR PS messages sent over CCCH
4 IA CS messages discarded
5 IA PS messages discarded
6 IAR CS messages discarded
7 IAR PS messages discarded

CELL# MODE ALARM ALARM

SEVERITY THRESHOLD

------------------------------------------------------------------------------

001 01 1(0001h) 1(0001h) DISABLED NO ALARM N/A

Example 12

This example displays the properties of the cell statistic CS_PAGING_MSGS_FROM_MSC.

disp_stat_prop CS_PAGING_MSGS_FROM_MSC cell 0 0 1 0 1 1 1

Where: is:
CS_PAGING_MSGS_FROM_MSC meas_type
0010111 cell_desc

5-34 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

STATISTIC: CS_PAGING_MSGS_FROM_MSC SITE: 1

TYPE: PER CELL OBJECT: COUNTER ARRAY
BIN# CAUSE

0 Received paging messages on SCCP_Pre MTL-LCF
1 Received paging messages on SCCP_Pre RSL-LCF
2 Received paging messages on RRSM
3 Received paging messages on RSS Abis
4 Received paging messages on RSS L1
5 Discarded paging messages on SCCP_Pre RSL-LCF due to Cell OOS
6 Discarded paging messages exceed max_pagenum_per_sec
CELL# MODE ALARM ALARM ALARM
BIN SEVERITY THRESHOLD
----- ----- ----- ----- -----
001 01 1 (0001h) 1 (0001h) ENABLED N/A N/A N/A

Example 13

{34371G}

This example displays the properties of site 0 statistic CPU_USAGE.

disp_stat_prop cpu_usage

Where: is:
cpu_usage meas_type

68P02901W23-T 5-35
Jan 2010
Examples Chapter 5: Statistics commands

System response

STATISTIC: CPU_USAGE SITE: All

TYPE: OTHER OBJECT: DISTRIB
CELL# MODE BIN# MIN MAX
------------------------- ----- ----- -------
NA ENABLED 0 0 10
1 11 20
2 21 30
3 31 40
4 41 50
5 51 60
6 61 70
7 71 80
8 81 80
9 91 100

Example 14

{34371G}

This example displays the properties of the statistic DSP_USAGE.

disp_stat_prop dsp_usage

Where: is:
dsp_usage meas_type

5-36 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

STATISTIC: dsp_usage SITE: All

TYPE: OTHER OBJECT: DISTRIB
CELL# MODE BIN# MIN MAX
------------------------- ----- ----- -------
NA ENABLED 0 0 10
1 11 20
2 21 30
3 31 40
4 41 50
5 51 60
6 61 70
7 71 80
8 81 80
9 91 100

Example 15

This example displays the properties of the cell statistic DL_TBF_TIME_5_TS_SINGLE.

disp_stat_prop DL_TBF_TIME_5_TS_SINGLE cell 0 0 1 0 1 1 1

Where: is:
DL_TBF_TIME_5_TS_SINGLE meas_type
0010111 cell_desc

System response

STATISTIC: DL_TBF_TIME_5_TS_SINGLE SITE: 1

TYPE: PER CELL OBJECT: COUNTER
CELL# MODE ALARM ALARM
SEVERITY THRESHOLD
----- ----- ----- -----
001 01 1 (0001h) 1 (0001h) ENABLED NO ALARM N/A

68P02901W23-T 5-37
Jan 2010
References Chapter 5: Statistics commands

References

Related commands

disp_element on page 3-294

stat_mode on page 5-56

disp_enable_stat on page 5-14

disp_interval on page 5-24

disp_stats on page 5-39

5-38 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference disp_stats

disp_stats

Description

The disp_stats command displays statistics associated with an individual cell or board for
a valid interval.

Security level 1
Supported by OMC-R GUI No
Command type A (no operator actions)
Prerequisites This command is not allowed while in SYSGEN ON mode.
The GPRS feature must be unrestricted to display PCU
statistics. The EGPRS feature must be unrestricted to
display EGPRS associated statistics.

Format

Syntax

disp_stats <meas_type>

disp_stats <interval> <meas_type> [<cell_desc>]

disp_stats <interval> <meas_type> [board_id=<board_id>]

Input parameters

interval

This value must be a completed statistical interval. The current interval may not be entered for
this parameter.

Statistical intervals are time periods measured from the system startup. Statistical intervals
are numbered sequentially from 0 to 11. The interval length is changed using the chg_element
command and displayed using the disp_element command. The first interval at start-up is 0
with a default length of 30 minutes.

The disp_interval command displays the completed and current intervals.

meas_type

Specifies the name of the statistic.

68P02901W23-T 5-39
Jan 2010
Examples Chapter 5: Statistics commands

cell_desc

The GSM cell ID indicating from which cell to display statistics, preceded by cell_number=. The
cell_desc is specified only for a per cell, per timeslot, or per neighbor cell statistic.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command may be entered in place of the
cell_number. When the cell name is entered, place inside double quotation marks and precede
by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

board_id

Specifies the GPROC for statistics collection. The board_id is specified only for a per link
statistic.

When using disp_stats to display a per link statistic, the output generated reports all links
for a specified board.

Examples

Example 1

The following example shows the display of a counter array statistic for a cell number in
seven parameter format:

disp_stats 5 out_ho_cause_atmpt cell_number= 5 4 3 2 1 61986 34944

Where: is:
5 interval
out_ho_cause_atmpt meas_type
5 4 3 2 1 61986 34944 cell_desc

The following example shows the same cell number in four parameter format:

disp_stats 5 out_ho_cause_atmpt 543 21 61986 34944

5-40 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

SITE: 0 CELL #: LAC = f222h CI = 8880h

MEAS_TYPE : OUT_HO_CAUSE_ATMPT
Total: 110
Uplink Quality : 10
Uplink Level : 20
Downlink Quality : 10
Downlink Level : 10
Distance : 10
Uplink Interference : 10
Downlink Interference : 10
Power Budget : 10
Congestion : 10
Adjacent Channel Interference : 10
Band Re-assignment : 0

Example 2

The following example displays the EGPRS_64K_NOT_AVAIL counter statistic that requires a
cell_desc:

disp_stats 1 egprs_64k_not_avail cell_number= 5 4 3 2 1 61986 34944

Where: is:
1 interval
egprs_64k_not_avail meas_type
5 4 3 2 1 61986 34944 cell_desc

System response

SITE: 1 CELL #: LAC = f222h CI = 8880h

MEAS_TYPE : EGPRS_64 K_NOT_AVAIL
Counter : 100

68P02901W23-T 5-41
Jan 2010
Examples Chapter 5: Statistics commands

Example 3

The following example displays a weighted distribution statistic that requires a cell_desc:

disp_stats 1 busy_tch cell_number= 5 4 3 2 1 61986 34944

Where: is:
1 interval
busy_tch meas_type
5 4 3 2 1 61986 34944 cell_desc

Values represented in the bins are time values expressed in milliseconds

System response

SITE: 0 CELL #: LAC = f222h CI = 8880h

MEAS_TYPE : BUSY_TCH
Distribution Mean : 0
Distribution Max : 1
Distribution Min : 0
Bin : 82260 217730 0 0 0 0 0 0 0 0

Example 4

The following example displays the AVAILABLE_TCH gauge statistic that requires a cell_desc:

disp_stats 4 available_tch cell_number= 5 4 3 2 1 61986 34944

Where: is:
4 interval
available_tch meas_type
5 4 3 2 1 61986 34944 cell_desc

System response

SITE: 0 CELL #: LAC = f222h CI = 8880h

MEAS_TYPE : AVAILABLE_TCH
Gauge Value : 5 Max. : 5

5-42 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 5

The following example displays a normal distribution statistic that requires a cell_desc because
it is a timeslot statistic:

disp_stats 0 ber cell_number= 0 0 1 0 1 1 6

Where: is:
0 interval
ber meas_type
0010116 cell_desc

The output for all time slots in all the existing carriers is displayed (in ascending order) in
the system response:

System response

SITE:1 CELL #:LAC = 0001h CI = 0006h Distribution Min : 0

RTF ID: 1 1
SITE:1 CELL #:LAC = 0001h CI = 0006h
TIMESLOT: 1 RTF ID = 1 1
MEAS_TYPE : BER
Distribution Mean : 0
Distribution Max : 0
Distribution Min : 0
Bin : 0 0 0 0 0 0 0 0 0 0
SITE:1 CELL #:LAC = 0001h CI = 0006h
TIMESLOT: 5 RTF ID = 1 1
MEAS_TYPE: BER
Distribution Mean : 0
Distribution Max : 0
Bin : 0 0 0 0 0 0 0 0 0 0

Example 6

The following example displays a related statistic when CS-3, CS-4, and 32 kbit/s GPRS TRAU
are enabled:

disp_stats 1 gprs_32k_channels_switched cell_number= 1 2 3 4 5 6 7

Where: is:
1 interval
gprs_32k_channels_switched meas_type
1234567 cell_desc

68P02901W23-T 5-43
Jan 2010
Examples Chapter 5: Statistics commands

System response

SITE: 5 CELL #: LAC = 6 CI= 7

MEAS_TYPE: GPRS_32 K_CHANNELS_SWITCHED
GPRS_CHANNELS_SWITCHED: 13

Example 7

This example displays statistics for PRP_LOAD for all PCUs equipped at the BSC.

disp_stats 3 prp_load

Where: is:
3 interval
prp_load meas_type

System response

PCU: 0 DPROC Board #: 4356 (ox1104)

MEAS_TYPE: PRP_LOAD
Distribution Mean : 0
Distribution Max : 0
Distribution Min : 0
Bin : 0 0 0 0 0 0 0 0 0 0
PCU: 1 DPROC Board #: 4356 (ox1104)
MEAS_TYPE: PRP_LOAD
Distribution Mean : 0
Distribution Max : 0
Distribution Min : 0
Bin : 0 0 0 0 0 0 0 0 0 0
PCU : 2 DPROC Board #: 4356 (ox1104)
MEAS_TYPE: PRP_LOAD
Distribution Mean : 0
Distribution Max : 0
Distribution Min : 0
Bin : 0 0 0 0 0 0 0 0 0 0

5-44 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 8

This example displays the PDU_DISCARD_FR counter statistic for the PCU 0 GBL link.

disp_stat PDU_DISCARD_FR

Where: is:
PDU_DISCARD_FR meas_type

System response

PCU: 0 GBL Link #: 0

MEAS_TYPE: PDU_DISCARD_FR
Counter: 0

Example 9

This example displays PFC_ADMISSION_OTHER statistics for the first interval after system
start up at a cell.

disp_stats 0 PFC_ADMISSION_OTHER cell 0 0 1 0 1 1 1

Where: is:
0 interval
PFC_ADMISSION_OTHER meas_type
0010111 cell_desc

System response

SITE: 1
CELL #: LAC=0001h CI=0001h
MEAS_TYPE: PFC_ADMISSION_OTHER
Total Count: 6
Admission successful SMS : 1
Admission successful Signaling : 2
Admission successful PFC_unaware : 3

68P02901W23-T 5-45
Jan 2010
Examples Chapter 5: Statistics commands

Example 10

This example displays the PACKET_SYSINFO_REQ statistics for the second interval after system
start at a cell.

disp_stats 1 PACKET_SYSINFO_REQ cell 0 0 1 0 1 1 1

Where: is:
1 interval
PACKET_SYSINFO_REQ meas_type
0010111 cell_desc

System response

SITE: 1
CELL #: LAC-0001h CI-0001h
MEAS TYPE: PACKET_SYSINFO_REQ
Total Count: 9
Valid Request Normal Request for Sys Info: 8
Invalid/Unexpected Request for System Information: 0
Request for System Information Discarded Resource Limit: 0
Valid Request Request for Sys Info Change Marks: 1

Example 11

This example displays the PRP_PD_DEMAND statistics for sixth interval after system startup.

disp_stats 5 PRP_PD_DEMAND

Where: is:
5 interval
PRP_PD_DEMAND meas_type

5-46 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

PCU : 0 DPROC Board # : 4355 (0x1103)

MEAS_TYPE : PRP_PD_DEMAND
Gauge Mean : 80
Gauge Max. : 118
PCU : 0 DPROC Board # : 4356 (0x1104)
MEAS_TYPE : PRP_PD_DEMAND
Gauge Mean : 67
Gauge Max. : 110
PCU : 1 DPROC Board # : 4356 (0x1104)
MEAS_TYPE : PRP_PD_DEMAND
Gauge Mean : 80
Gauge Max. : 111

Example 12

The following example displays the value of the BSS MTP_SL_ERROR_RATE_HSP statistic.

disp_stats 6 mtp_sl_error_rate_hsp board_id 0113h

Where: is:
6 interval
mtp_sl_error_rate_hsp meas_type
0113h board description

System response

SITE:0 GPROC Board # : 275 (0x0113)

SITE:0 MTL Link # : 1
MEAS_TYPE: MTP_SL_ERROR_RATE_HSP
Counter: 0

68P02901W23-T 5-47
Jan 2010
Examples Chapter 5: Statistics commands

Example 13

The following example displays the value of the BSS: PSI_TRAU_FILL_FRAME_TX statistic.

disp_stats 0 PSI_TRAU_FILL_FRAME_TX

Where: is:
0 interval
psi_trau_fill_frame_tx meas_type

System response

SITE: 0 PSI Board #: 0107

ETH Port #: 0
MEAS TYPE: PSI_TRAU_FILL_FRAME_TX
Counter: 145

Example 14

The following example displays the link statistic: RSL_TX_OCTETS.

disp_stats 0 RSL_TX_OCTETS board_id=0118h

Where: is:
0 interval
rsl_tx_octets meas_type
0118h board_id

System response

SITE: 0 GPROC Board#: 280 (0x0118)

SITE: 62 RSL Link # :0
MEAS TYPE: RSL_TX_OCTETS
Counter: 100

5-48 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 15

The following example displays the UL_TBF_TIME_GMSK_3_TS cell statistics.

disp_stats 1 UL_TBF_TIME_GMSK_3_TS cell 0 0 1 0 1 1 1

Where: is:
1 interval
ul_tbf_time_gmsk_3_ts meas_type
0010111 cell_desc

System response

SITE: 1 CELL #: LAC=0001h CI=0001h

MEAS TYPE: UL_TBF_TIME_GMSK_3_TS
Counter: 100

Example 16

This example displays the properties of the UL_RADIO_BLKS_GMSK_3_TS cell statistics.

disp_stats 1 UL_RADIO_BLKS_GMSK_3_TS 0 0 1 0 1 1 1

Where: is:
1 interval
ul_radio_blks_gmsk_3_ts meas_type
0010111 cell_desc

System response

SITE: 1 CELL #: LAC=0001h CI=0001h

MEAS TYPE: UL_RADIO_BLKS_GMSK_3_TS
Total count: 3175
GPRS coding scheme 1 :0
GPRS coding scheme 2 :2
GPRS coding scheme 3 :1
GPRS coding scheme 4 :3172
EGPRS modulation and coding scheme 1 :0
EGPRS modulation and coding scheme 2 :0
EGPRS modulation and coding scheme 3 :0
EGPRS modulation and coding scheme 4 :0

68P02901W23-T 5-49
Jan 2010
Examples Chapter 5: Statistics commands

Example 17

The following example displays the cell statistic IA_IAR_MSGS_PER_AGCH.

disp_stats 1 IA_IAR_MSGS_PER_AGCH cell_number= 0 0 1 0 1 1 1

Where: is:
1 interval
IA_IAR_MSGS_PER_AGCH meas_type
0010111 cell_desc

System response

SITE: 1 CELL #: LAC-0001h CI-0001h

MEAS TYPE: IA_IAR_MSGS_PER_AGCH
Total counter: 8

BIN# Cause Sub-Counter

Value

0 IA CS messages sent over CCCH 1

1 IA PS messages sent over CCCH 1

2 IAR CS messages sent over CCCH 1

3 IAR PS messages sent over CCCH 1

4 IA CS messages discarded 1

5 IA PS messages discarded 1

6 IAR CS messages discarded 1

7 IAR PS messages discarded 1

Example 18

The following example displays the cell statistic CS_PAGING_MSGS_FROM_MSC.

disp_stats 1 CS_PAGING_MSGS_FROM_MSC cell_number= 0 0 1 0 1 1 1

Where: is:
1 interval
CS_PAGING_MSGS_FROM_MSC meas_type
0010111 cell_desc

5-50 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

SITE: 0 CELL #: LAC-0001h CI-0001h

MEAS TYPE: CS_PAGING_MSGS_FROM_MSC
Total counter: 7

BIN# Cause Sub-Counter

Value

0 received paging messages on SCCP_Pre MTL-LCF 1

1 received paging messages on SCCP_Pre RSL-LCF 1

2 received paging messages on RRSM 1

3 received paging messages on RSS Abis 1

4 received paging messages on RSS L1 1

5 discarded paging messages on SCCP_Pre RSL-LCF due 1

to Cell OOS

6 discarded paging messages exceeds max_pagenum_per_sec 1

Example 19

{34371G}

This example displays the per-board statistic CPU_USAGE.

NOTE
Add the new BBU CPU_USAGE statistic where the BBU Board # is 4015 and 4019.

disp_stats 0 cpu_usage 81

Where: is:
0 interval
cpu_usage meas_type
81 site

68P02901W23-T 5-51
Jan 2010
Examples Chapter 5: Statistics commands

System response

SITE: 81 BBU Board # : 16405 (0x4015)

MEAS_TYPE: CPU_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0

SITE: 81 BBU Board # : 16409 (0x4019)

MEAS_TYPE: CPU_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0

Example 20

{34371G}

This example displays the BBU statistic DSP_USAGE.

NOTE
The BBU Board # format is displayed as 0x5abc, where

a is BBU id from 0 to 1.
b is DSP id from 0 to 5.
c is core id from 0 to 2.

BTS can auto equip 2 BBUs and each BBU has 6 DSPs. Each DSP is equipped with 3
processors (1 CCU core and 2 EQUs core). Totally there are 18 (3*6=18) DSP core
loads per BBU and 36 (18*2=36) core loads per BTS when BBU is in BU status.

disp_stats 0 dsp_usage 81

Where: is:
0 interval
dsp_usage meas_type
81 site

5-52 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

SITE: 81 BBU Board # : 20480 (0x5000)

MEAS_TYPE: DSP_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0

SITE: 81 BBU Board # : 20481 (0x5001)

MEAS_TYPE: DSP_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0

SITE: 81 BBU Board # : 20482 (0x5002)

MEAS_TYPE: DSP_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0

SITE: 81 BBU Board # : 20496 (0x5010)

MEAS_TYPE: DSP_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0

SITE: 81 BBU Board # : 20497 (0x5011)

MEAS_TYPE: DSP_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0

SITE: 81 BBU Board # : 20498 (0x5012)

MEAS_TYPE: DSP_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0

68P02901W23-T 5-53
Jan 2010
Examples Chapter 5: Statistics commands

Bin: 0 0 0 0 0 0 0 0 0 0

SITE: 81 BBU Board # : 20512 (0x5020)

MEAS_TYPE: DSP_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0

SITE: 81 BBU Board # : 20513 (0x5021)

MEAS_TYPE: DSP_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0

SITE: 81 BBU Board # : 20514 (0x5022)

MEAS_TYPE: DSP_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0
.
.
SITE: 81 BBU Board # : 20818 (0x5152)
MEAS_TYPE: DSP_USAGE
Distribution Mean: 0
Distribution Max.: 0
Distribution Min.: 0
Bin: 0 0 0 0 0 0 0 0 0 0

Example 21

This example displays the cell statistic DL_TBF_TIME_5_TS_SINGLE.

disp_stats 1 DL_TBF_TIME_5_TS_SINGLE cell 0 0 1 0 1 1 1

Where: is:
1 interval
DL_TBF_TIME_5_TS_SINGLE meas_type
0010111 cell_desc

5-54 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

System response

SITE: 1 CELL #: LAC=0001h CI=0001h

MEAS_TYPE: DL_TBF_TIME_5_TS_SINGLE
Counter: 100

References

Related commands

disp_element on page 3-294

stat_mode on page 5-56

disp_enable_stat on page 5-14

disp_interval on page 5-24

68P02901W23-T 5-55
Jan 2010
stat_mode Chapter 5: Statistics commands

stat_mode

Description

The stat_mode command enables or disables individual statistics in the CM database.

The statistical applications of the stat_mode command permit multiple interactions with the
same database element to define the statistical data. This permits flexibility in the definition of
the parameters.

NOTE
The stat_mode command replaces the chg_element command for enabling or
disabling statistics. The chg_stat_prop command replaces the chg_element for
modifying a statistic.

Security level 4
Supported by OMC-R GUI Yes
Command type A (no operator actions)
Prerequisites The GPRS feature must be unrestricted to enable GPRS
associated statistics.
The EGPRS feature must be unrestricted to enable EGPRS
associated statistics.

NOTE
Enter this command at the BSC only. This command does not work at a BTS site.
Contact the OMC-R for help.

Format

Syntax

stat_mode <meas_type> <mode> [<location>] [<cell_desc>]

stat_mode <meas_type> <mode> [<cell_desc>]

stat_mode <meas_type> <mode> all

stat_mode <meas_type> <mode> <location> all

5-56 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Format

Input parameters

meas_type

Specifies the name of the statistic.

mode

Specifies the mode of the statistic:

on Enable
off Disable

location

Specifies the site location:

0 or bsc BSC
1 - 140 BTS
all All sites

cell_desc

The GSM cell ID of the cell to be modified, preceded by cell_number=.

The format for the GSM cell ID depends on:

The system used (PGSM, EGSM, DCS1800, PCS1900).

Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID
format has been enabled.

The name of the cell created using the cell_name command may be entered in place of the
cell_number. When the cell name is entered, place inside double quotation marks and precede
by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of
either the cell_number or the cell_name without further definition.

The value all is also a valid input for the cell_desc. If entered, the mode for the statistic
changes for all cells at the specified site.

68P02901W23-T 5-57
Jan 2010
Examples Chapter 5: Statistics commands

Examples

Example 1

This example enables the TBF_SESSIONS statistic.

stat_mode TBF_SESSIONS on

Where: is:
TBF_SESSIONS meas_type
on mode

System response

COMMAND ACCEPTED

Example 2

This example enables the TIMER_EXP_PAP_CONV statistic for cell 0 0 1 0 1 1 1.

stat_mode TIMER_EXP_PAP_CONV on cell 0 0 1 0 1 1 1

Where: is:
TIMER_EXP_PAP_CONV meas_type
on mode
0010111 cell_desc

System response

COMMAND ACCEPTED

Example 3

This example enables the TOTAL_CALLS statistic for cell number 5 4 3 2 1 61698 34776 at site 1.

stat_mode total_calls on 1 cell_number= 5 4 3 2 1 61698 34776

Where: is:
total_calls meas_type
on mode
1 location
5 4 3 2 1 61698 34776 cell_desc

5-58 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

COMMAND ACCEPTED

Example 4

This example enables all CELL statistic for all cells except NCELL stats at site 1.

stat_mode all on 1 all

Where: is:
all meas_type

on mode

1 location

all cell_desc

System response

COMMAND ACCEPTED

Example 5

This example enables all BSS statistic.

stat_mode all on

Where: is:
all meas_type
on mode

System response

COMMAND ACCEPTED

68P02901W23-T 5-59
Jan 2010
Examples Chapter 5: Statistics commands

Example 6

This example disables the TOTAL_CALLS statistic for all cells at site 1.

stat_mode total_calls off 1 all

Where: is:
total_calls meas_type
off mode
1 location
all all cells at the specified site

System response

COMMAND ACCEPTED

Example 7

This example enables the GPRS_32K_CHANNELS_SWITCHED statistic for all cells at site 1.

stat_mode gprs_32k_channels_switched on 1 all

Where: is:
gprs_32k_channels_switched meas_type
on mode
1 location
all cell_desc

System response

COMMAND ACCEPTED

Example 8

This example disables the SS7 link MTP_SL_ERROR_RATE_HSP statistic.

stat_mode MTP_SL_ERROR_RATE_HSP off

Where: is:
mtp_sl_error_rate_hsp meas_type
off mode

5-60 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

System response

COMMAND ACCEPTED

Example 9

This example enables the BSS PSI_TRAU_FILL_FRAME_TX statistic.

stat_mode PSI_TRAU_FILL_FRAME_TX on

Where: is:
psi_trau_fill_frame_tx meas_type
on mode

System response

COMMAND ACCEPTED

Example 10

This example enables or disables individual statistics.

stat_mode RSL_TX_OCTETS on/off

Where: is:
rsl_tx_octets meas_type
on/off mode

System response

COMMAND ACCEPTED

Example 11

This example enables the timeslot statistic RF_LOSSES_TCH.

stat_mode RF_LOSSES_TCH on 1 cell_number=0 0 1 0 1 1 1

Where: is:
rf_losses_tch meas_type
on mode
1 location
0010111 cell_desc

68P02901W23-T 5-61
Jan 2010
Examples Chapter 5: Statistics commands

System response

COMMAND ACCEPTED

Example 12

This example enables the statistics for cell 0 0 1 0 1 1 1 when QoS feature is unrestricted.

stat_mode PFC_ADMISSION_TRAFFIC_CLASS on cell 0 0 1 0 1 1 1

Where: is:
PFC_ADMISSION_TRAFFIC_CLASS meas_type
on mode
0010111 cell_desc

System response

COMMAND ACCEPTED

Example 13

This example enables the CELL statistic UL_RLC_STALLED_BLKS when GPRS features are
unrestricted.

stat_mode UL_RLC_STALLED_BLKS on cell 0 0 1 0 1 1 1

Where: is:
UL_RLC_STALLED_BLKS meas_type
on mode
0010111 cell_desc

System response

COMMAND ACCEPTED

5-62 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Examples

Example 14

This example enables the cell statistic UL_RADIO_BLKS_8PSK_3_TS when EDA and EGPRS
feature is unrestricted.

stat_mode UL_RADIO_BLKS_8PSK_3_TS on cell 0 0 1 0 1 1 1

Where: is:
ul_radio_blks_8psk_3_ts meas_type
on mode
0010111 cell_desc

System response

COMMAND ACCEPTED

Example 15

This example enables the BSS statistic IA_IAR_MSGS_PER_AGCH.

stat_mode IA_IAR_MSGS_PER_AGCH on 1 cell_number=0 0 1 0 1 1 1

Where: is:
IA_IAR_MSGS_PER_AGCH meas_type
on mode
1 location
0010111 cell_desc

System response

COMMAND ACCEPTED

Example 16

This example enables the cell statistic CS_PAGING_MSGS_FROM_MSC.

stat_mode CS_PAGING_MSGS_FROM_MSC on cell_number=0 0 1 0 1 1 1

Where: is:
CS_PAGING_MSGS_FROM_MSC meas_type
on mode
0010111 cell_desc

68P02901W23-T 5-63
Jan 2010
Examples Chapter 5: Statistics commands

System response

COMMAND ACCEPTED

Example 17

This example enables the cell statistic UL_LLC_DATA_VOLUME when GPRS features are
unrestricted.

stat_mode UL_LLC_DATA_VOLUME on cell 0 0 1 0 1 1 1

Where: is:
UL_LLC_DATA_VOLUME meas_type
on mode
0010111 cell_desc

System response

COMMAND ACCEPTED

Example 18

This example enables the CELL statistic DL_RADIO_BLKS_5_TS_SINGLE.

stat_mode DL_RADIO_BLKS_5_TS_SINGLE on cell 0 0 1 0 1 1 1

Where: is:
DL_RADIO_BLKS_5_TS_SINGLE meas_type
on mode
0010111 cell_desc

System response

COMMAND ACCEPTED

5-64 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Related commands

disp_element on page 3-294

disp_enable_stat on page 5-14

disp_interval on page 5-24

disp_stats on page 5-39

68P02901W23-T 5-65
Jan 2010
References Chapter 5: Statistics commands

5-66 68P02901W23-T
Jan 2010
 Chapter

CM database parameters

Configuration Management (CM) database parameters are BSS parameters that can be
displayed and modified using MMI commands.

This chapter provides a description of each CM database parameter, and indicates the command
syntax used to change or display the parameter. The chapter begins with an explanation of the
presentation layout used for each parameter reference.

The CM database parameters are presented in alphabetical order as listed in the Contents
section of this manual.

68P02901W23-T 6-1
Jan 2010
CM database parameters presentation Chapter 6: CM database parameters

CM database parameters presentation

The layout of the CM database parameters reference information is explained in the following
section.

Parameter reference

The actual CM database parameter reference appears at the head of the page, and is reproduced
in the contents and the index of this manual.

Description

The function of the CM database parameter is described briefly. Dependencies on other

database elements and system functions are included in the description.

Type

CM database parameters are classified as Type A or Type B where:

Type A parameters do not require additional operator actions when the parameter value is
changed.

Type B parameters require additional operator actions when the parameter value is
changed. The specific action required is described in the Operator actions field.

OMC-R GUI support

Indicates if a database parameter can be changed using the OMC-R GUI (Graphics User
Interface). If a value is not supported through the OMC-R GUI, it can be changed by performing
a remote login (rlogin) from the OMC-R or at the site using a PC connected to the master GPROC.

Cell description required

Indicates whether the CM database parameter affects specific cells and requires the GSM cell
ID numbers to be included in the command syntax when the parameter is displayed or changed.

Dependencies

Describes any database internal or external dependencies which may affect value assignments of
the database parameter. Consider these dependencies when changes are made to the parameter.

6-2 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

Operator actions

The specific actions required when changing Type B parameters are listed, including any
precautions that are appropriate.

Syntax

Add/change command strings

The command syntax used to assign or change values to a parameter is provided to assist
the operator in entering the command. The command name, the parameter name, indices (if
required), the new element value, and the location affected are included in the command syntax.

The add_name command is included where an element is initially assigned using the add_cell
command and modified using other commands. The individual add_cell command prompts are
listed in the description of the add_cell command.

Display command strings

The command syntax used to display the database element value is provided to assist the
operator in entering the command. The command name, the parameter name, indices (if
required), and the location are included in the command syntax.

Values

The value types and valid ranges for the database values are listed for each parameter. Values
for some elements are expressed as steps representing incremental values.

Default values

Default values are available for some parameters.

The add_cell command default values are selected by typing the parameter name and the equal
sign than pressing the return key in response to a parameter prompt.

Some parameters are assigned default values when the database is initially loaded. This
default value may only be displayed by using the disp_element command before the database
parameter is changed for the first time. The default value may be changed by using the
appropriate change command.

Invalid value

If an invalid value is entered while using the add_cell command, the MMI uses the default
value if there is one present. If there is no default value, the MMI displays an error message
then abandons the add_cell command.

If an invalid value is entered when using the chg_element command, the command is abandoned
and an error message presented. The original value of the parameter remains unchanged.

68P02901W23-T 6-3
Jan 2010
References Chapter 6: CM database parameters

References

The following information is given when required.

GSM parameter

Where a parameter is assigned a name that is different from the name assigned in the
GSM Technical Specifications, the name assigned to the parameter by the GSM Technical
Specifications is listed as a cross reference.

GSM technical specifications

The source GSM document used to define the parameter is listed as a reference.

6-4 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference _bss_data,2

_bss_data,2

Description

The _bss_data,2 parameter is used to enable the MMS Lock Persistency feature.

NOTE
The NVRAM MMS Lock data is always stored and updated. However, the data can be
used only when the MMS Lock Persistency feature is enabled using the _bss_data,2
parameter. If BSP/GPROC is pulled out from the site for several months and placed in
storage, then care should be taken with MMS Lock Persistency.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element _bss_data,2 <value> <location>

Display command string

disp_element _bss_data,2 <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-5
Jan 2010
_site_data, 5 Chapter 6: CM database parameters

_site_data, 5

Description

The _site_data, 5 parameter is used to enable or disable the Horizon I or Horizon II BTS to
connect to the Abis interface. For other BTS types, this element is always set to Abis_Disable.
This parameter may be changed outside SYSGEN mode.

Type B (operator actions required)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter can only be modified if the Dual Abis Aware
BTS feature is enabled.

Values

Value type Integer

Valid range 0 Minimum
2 Maximum
Default value 0

NOTE

0 = Abis_Disable
Disables the Abis connection to the BSC6.
1 = Abis_Enable_Conv
Enables the Abis connection control for the BTS.
2 = Abis_Enable_CSFP
Enables the Abis connection control for the BTS when the BTS has the CSFP
download the full Abis load from the BSC2.

6-6 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference abis_auto_swap_enabled

abis_auto_swap_enabled

{36039G}

Description

The abis_auto_swap_enabled parameter enables and disables the function of the Abis auto
swap feature.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies
This parameter can be modified only when the Abis
auto swap feature (abisautoswapOpt) is unrestricted.

The modification of the value to 0 (disabled) is

dependent on the condition that no Abis link is
working on the satellite mode. The working Abis
bearing mode should be changed to terrestrial mode
and the value then set to 0.

Syntax

Change command string

chg_element abis_auto_swap_enabled <value> <location>

Display command string

disp_element abis_auto_swap_enabled <location>

Values

Value type Boolean

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-7
Jan 2010
abis_state_element Chapter 6: CM database parameters

abis_state_element

Description

The parameter abis_state_element enables or disables the Horizon macro or Horizon II BTSs
from connecting to the Abis interface. For other BTS types, this element is always set to
Abis_Disable. This parameter may be changed outside SYSGEN mode.

Type B (operator actions required)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter can only be modified if the Dual Abis Aware
BTS feature is enabled.

Syntax

Change command string

chg_element abis_state_element <value> <location>

Display command string

disp_element abis_state_element <location>

Values

Value type Integer

Valid range 0 Minimum
2 Maximum
Default value 0

6-8 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

NOTE

0 = Abis_Disable
Disables the Abis connection to the BSC6.
1 = Abis_Enable_Conv
Enables the Abis connection control for the BTS.
2 = Abis_Enable_CSFP
Enables the Abis connection control for the BTS when the BTS has the CSFP
download the full Abis load from the BSC2.

68P02901W23-T 6-9
Jan 2010
aci_error_clr_thresh Chapter 6: CM database parameters

aci_error_clr_thresh

Description

The aci_error_clr_thresh parameter specifies the error count threshold (equal to or less than)
for an alarm to be cleared for an ATER Channel Identifier (ACI).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The ECERM feature must be enabled.
Two successful calls are required to clear an alarm within
this threshold. (One call can be too short for the Channel
Coder Unit (CCU) to send an error indication, thus clearing
the alarm prematurely.)
This parameter can be set only at a BSC.
If the threshold is increased during operation, any existing
counts between the new and the old threshold do not clear
an alarm until another successful call is made on the ACI.
(aci_error_gen_thresh - aci_error_clr_threshold) >= 2

Syntax

Change command string

chg_element aci_error_clr_thresh <value> 0

Display command string

disp_element aci_error_clr_thresh 0

Values

Value type Integer

Valid range 0 to 253
Default value 0

6-10 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference aci_error_gen_thresh

aci_error_gen_thresh

Description

The aci_error_gen_thresh parameter specifies the error count threshold (equal to or greater
than) for an alarm to be generated for an ATER Channel Identifier (ACI).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The ECERM feature must be enabled.
This parameter can be set only at a BSC.
If the threshold is reduced during operation, any existing
counts between the new and the old threshold does not
cause an alarm.
(aci_error_gen_thresh - aci_error_clr_thresh) >= 2.

Syntax

Change command string

chg_element aci_error_gen_thresh <value> 0

Display command string

disp_element aci_error_gen_thresh 0

Values

Value type Integer

Valid range 2 to 255
Default value 6

68P02901W23-T 6-11
Jan 2010
aci_error_inc Chapter 6: CM database parameters

aci_error_inc

Description

The aci_error_inc parameter specifies the error count increment when the Enhanced Circuit
Error Rate Monitor (ECERM) feature is in use for ATER Channel Identifiers (ACIs) on a per
BSC basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The ECERM feature must be enabled.
This parameter applies only to the BSC.

Syntax

Change command string

chg_element aci_error_inc <value> 0

Display command string

disp_element aci_error_inc 0

Values

Value type Integer

Valid range 0 ACI alarms not raised.
1 to 255 ACI alarms raised.
Default value 0 If ECERM feature is disabled.
1 If ECERM feature is enabled.

6-12 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference adap_ho_alt_trigger_rxqual

adap_ho_alt_trigger_rxqual

Description

The adap_ho_alt_trigger_rxqual parameter specifies whether the system uses alternative

trigger values for adaptive quality handovers for a cell that is frequency hopping.

If adaptive handovers are enabled for rxqual, this parameter enables the use of the hopping
thresholds for calls that are frequency hopping.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element adap_ho_alt_trigger_rxqual <value> <location> <cell_desc>

chg_cell_element adap_ho_alt_trigger_rxqual <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element adap_ho_alt_trigger_rxqual <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Do not use hopping specific thresholds.
1 Use hopping specific thresholds.
Default value 0

68P02901W23-T 6-13
Jan 2010
adap_ho_pbgt Chapter 6: CM database parameters

adap_ho_pbgt

Description

The adap_ho_pbgt parameter specifies whether the system allows adaptive power budget
handovers. The cumulative area for the adaptive power budget handovers can be defined as
per cell or per neighbor.

At each measurement report, the cumulative area are updated and compared to a cumulative
trigger. If the area is greater than the cumulative power budget trigger (pbgt), a need for
a handover is recognized.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element adap_ho_pbgt <value> <location> <cell_desc>

chg_cell_element adap_ho_pbgt <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element adap_ho_pbgt <location> <cell_desc>

6-14 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 2
0 Disables adaptive power budget handovers at the location.
1 Enables adaptive power budget handovers at the location
using per cell cumulative area.
2 Enables adaptive power budget handovers at the location
using per neighbor cumulative area.
Default value 0

68P02901W23-T 6-15
Jan 2010
adap_ho_rxlev Chapter 6: CM database parameters

adap_ho_rxlev

Description

The adap_ho_rxlev parameter specifies whether the system allows adaptive receive level
handovers.

At each measurement report the cumulative area is updated and compared to a cumulative
trigger. If the area is greater than the cumulative power adaptive receive level (rxlev) trigger, a
need for a handover is recognized.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element adap_ho_rxlev <value> <location> <cell_desc>

chg_cell_element adap_ho_rxlev <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element adap_ho_rxlev <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disables adaptive receive level handovers at the location.
1 Enables adaptive receive level handovers at the location.
Default value 0

6-16 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference adap_ho_rxqual

adap_ho_rxqual

Description

The adap_ho_rx_qual parameter specifies whether the system allows adaptive quality
handovers.

At each measurement report the cumulative area is updated and compared to a cumulative
trigger. If the area is greater than the cumulative power adaptive quality (rxqual) trigger a
need for a handover is recognized.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element adap_ho_rxqual <value> <location> <cell_desc>

chg_cell_element adap_ho_rxqual <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element adap_ho_rxqual <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disables adaptive quality handovers at the location.
1 Enables adaptive quality handovers at the location.
Default value 0

68P02901W23-T 6-17
Jan 2010
adap_trigger_hop_rxqual_dl Chapter 6: CM database parameters

adap_trigger_hop_rxqual_dl

Description

The adap_trigger_hop_rxqual_dl parameter specifies the trigger threshold for downlink

rxqual for calls that are frequency hopping.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element adap_trigger_hop_rxqual_dl <value> <location> <cell_desc>

chg_cell_element adap_trigger_hop_rxqual_dl <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element adap_trigger_hop_rxqual_dl <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 65535
Default value 0

6-18 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference adap_trigger_hop_rxqual_ul

adap_trigger_hop_rxqual_ul

Description

The adap_trigger_hop_rxqual_ul parameter specifies the trigger threshold for uplink rxqual
for calls that are frequency hopping.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element adap_trigger_hop_rxqual_ul <value> <location> <cell_desc>

chg_cell_element adap_trigger_hop_rxqual_ul <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element adap_trigger_hop_rxqual_ul <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 65535
Default value 0

68P02901W23-T 6-19
Jan 2010
adap_trigger_pbgt Chapter 6: CM database parameters

adap_trigger_pbgt

Description

The adap_trigger_pbgt parameter specifies the cumulative trigger level for adaptive power
budget handovers.

When the threshold set by adap_trigger_pbgt is exceeded, the system triggers a handover
to a better cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element adap_trigger_pbgt <value> <location> <cell_desc>

chg_cell_element adap_trigger_pbgt <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element adap_trigger_pbgt <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 255
Default value 0

6-20 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference adap_trigger_pbgt_nbr

adap_trigger_pbgt_nbr

Description

The adap_trigger_pbgt_nbr parameter specifies the cumulative trigger level for the adaptive
handover power budget algorithm.

When the threshold set by adap_trigger_pbgt_nbr is exceeded, the system triggers a handover
to a better cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is invalid when ba_type is ba_bcch or
ba_gprs.

Syntax

Change command string

modify_neighbor <src_cell_id> <neighbor_cell_id> adap_trigger_pbgt_nbr <value>

Display command string

disp_neighbor <src_cell_id> [<neighbor_cell_id>|all]

Values

Value type Integer

Valid range 0 to 255
Default value 40 (the value of 40 corresponds to an hreqave of 8 and a handover
margin of 5)

68P02901W23-T 6-21
Jan 2010
adap_trigger_rxlev_dl Chapter 6: CM database parameters

adap_trigger_rxlev_dl

Description

The adap_trigger_rxqual_dl parameter specifies the cumulative trigger level for adaptive
receive level downlink handovers.

When the threshold set by this parameter is exceeded, the system performs a downlink strength
handover.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element adap_trigger_rxlev_dl <value> <location> <cell_desc>

chg_cell_element adap_trigger_rxlev_dl <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element adap_trigger_rxlev_dl <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 255
Default value 0

6-22 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference adap_trigger_rxlev_ul

adap_trigger_rxlev_ul

Description

The adap_trigger_rxlev_ul parameter specifies the cumulative trigger level for adaptive
receive level uplink handovers.

When the threshold set by this parameter is exceeded, the system performs an uplink strength
handover.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element adap_trigger_rxlev_ul <value> <location> <cell_desc>

chg_cell_element adap_trigger_rxlev_ul <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element adap_trigger_rxlev_ul <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 255
Default value 0

68P02901W23-T 6-23
Jan 2010
adap_trigger_rxqual_dl Chapter 6: CM database parameters

adap_trigger_rxqual_dl

Description

The adap_trigger_rxqual_dl parameter specifies the cumulative trigger level for adaptive
rxqual downlink handovers.

When the threshold set by this parameter is exceeded, the system performs a downlink quality
handover.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element adap_trigger_rxqual_dl <value> <location> <cell_desc>

chg_cell_element adap_trigger_rxqual_dl <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element adap_trigger_rxqual_dl <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 65535
Default value 0

6-24 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference agch_flow_control_mode

agch_flow_control_mode

Description

The agch_flow_control_mode parameter indicates whether the functionality of the AGCH

flow control is enabled. The parameter also indicates the triggers associated with IA or IAR
that can trigger AGCH overload. This parameter may be changed inside and outside SYSGEN
mode without warning.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element agch_flow_control_mode <element-value> <location>

Display command string

disp_element agch_flow_control_mode <location>

Values

Value type Integer

Valid range 0 to 2
0 AGCH flow control function is disabled.
1 AGCH flow control function is enabled, any one
of the triggers associated with IA and IAR can
trigger AGCH overload.

68P02901W23-T 6-25
Jan 2010
Values Chapter 6: CM database parameters

2 AGCH flow control function is enabled, while only

the trigger associated with IA can trigger AGCH
overload.
Default value 1

6-26 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference aggressive_rach

aggressive_rach

Description

The parameter aggressive_rach enables or disables the CTU2 / CTU2D equaliser to apply more
aggressive RACH qualification thresholds. This reduces the volume of phantom RACHs and
improves the SDCCH seizure success rate and the SDCCH RF loss rate.

When this parameter is enabled, all the B-U BCCH CTU2/CTU2D radios related with the cell
are notified and the change takes effect immediately without resetting the related BCCH
CTU2/CTU2D radios.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell numbers required Yes
Dependencies None

Syntax

Change command string

chg_cell_element aggressive_rach <value> <cell_desc_opt>

chg_element aggressive_rach <value> <cell_desc_opt>

Display command string

disp_element aggressive_rach <value> <cell_desc>

Values

Value type Integer

Value range 0 to 1 0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-27
Jan 2010
allow_8k_trau Chapter 6: CM database parameters

allow_8k_trau

Description

The allow_8k_trau parameter enables or disables 8 kbit/s backhaul.

A timeslot or smaller portions within a timeslot may represent a port on the switch. A port on
the KSW can be a minimum of two bits that equates to four independent 16 kbit/s portions
within each timeslot. The KSW can operate in a sub-rate switching mode where each timeslot
can independently switch a 16 kbit/s subgroup (one-quarter of a timeslot). The DSW can
operate in a sub-rate switching mode where each timeslot can independently switch an 8 kbit/s
sub-group (one-eighth of a timeslot).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The AMR Enhanced Capability feature and/or GSM Half
Rate feature must be enabled.
The half_rate_enabled parameter must be enabled.
The BTS must be AMR/GSM Half Rate capable.
The 7.95 kbit/s codec mode must not be part of the AMR
Half-Rate Active Codec Set.

Syntax

Change command string

equip <site_id> RTF

NOTE
After entering this command, the operator is prompted to enable or disable the
allow_8k_trau parameter (and other RTF parameters).

Display command string

disp_equipment

6-28 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range no or yes
no Disabled
yes Enabled
Default value yes

68P02901W23-T 6-29
Jan 2010
alt_qual_proc Chapter 6: CM database parameters

alt_qual_proc

Description

The alt_qual_proc parameter specifies whether receive quality processing is performed

using Bit Error Rate (BER) values or Quality Band (QBand) units. The value assigned to
the alt_qual_proc parameter determines the type of values and the range of values of six
parameters.

The alt_qual_proc parameter value is initially assigned using the add_cell command.

The alt_qual_proc parameter for a cell may be changed using the chg_cell_element command.
When the chg_cell_element command is used to change the value of the alt_qual_proc
parameter, additional prompts are presented for the dependent parameters. Default values may
be entered by pressing return at the prompt. If an invalid value is entered, the command
is abandoned.

The AMR/GSM Half Rate Rxqual Handover and Power Control (HDPC) specific parameters are
prompted for when changing the value of alt_qual_proc parameter when AMR and/or GSM
Half Rate are unrestricted. AMR Full Rate HDPC parameters are prompted for only when
AMR is unrestricted

The value that is entered for the alt_qual_proc parameter determines the type of values, range
of values, and default values for the dependent cell parameters.

If a value of 0 is entered for the alt_qual_proc parameter, the range of values and defaults for
the dependent cell parameters is listed in Table 6-1 .

Table 6-1 alt_qual_proc=0 parameter values

Dependent parameter Range Default

l_rxqual_ul_p 0 to 1810 226
l_rxqual_dl_p 0 to 1810 226
u_rxqual_ul_p 0 to 1810 28
u_rxqual_dl_p 0 to 1810 28
l_rxqual_ul_h 0 to 1810 453
l_rxqual_dl_h 0 to 1810 453
l_rxqual_dl_h_hopping 0 to 1810 0
l_rxqual_ul_h_hopping 0 to 1810 0
l_rxqual_dl_p_hopping 0 to 1810 0
l_rxqual_ul_p_hopping 0 to 1810 0
l_rxqual_dl_h_data 0 to 1810 0
l_rxqual_ul_h_data 0 to 1810 0

Continued

6-30 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Description

Table 6-1 alt_qual_proc=0 parameter values (Continued)

Dependent parameter Range Default
l_rxqual_dl_p_data 0 to 1810 0
l_rxqual_ul_p_data 0 to 1810 0
l_rxqual_ul_p_amr_fr 0 to 1810 226
l_rxqual_dl_p_amr_fr 0 to 1810 113
l_rxqual_ul_h_amr_fr 0 to 1810 453
l_rxqual_dl_h_amr_fr 0 to 1810 226
l_rxqual_dl_h_hopping_amr_fr 0 to 1810 0
l_rxqual_ul_h_hopping_amr_fr 0 to 1810 0
l_rxqual_dl_p_hopping_amr_fr 0 to 1810 0
l_rxqual_ul_p_hopping_amr_fr 0 to 1810 0
l_rxqual_ul_p_hr 0 to 1810 57
l_rxqual_dl_p_hr 0 to 1810 57
u_rxqual_ul_p_hr 0 to 1810 14
u_rxqual_dl_p_hr 0 to 1810 14
l_rxqual_ul_h_hr 0 to 1810 113
l_rxqual_dl_h_hr 0 to 1810 113
l_rxqual_dl_h_hopping_hr 0 to 1810 113
l_rxqual_ul_h_hopping_hr 0 to 1810 113
l_rxqual_dl_p_hopping_hr 0 to 1810 57
l_rxqual_ul_p_hopping_hr 0 to 1810 57

Table 6-2 lists the range of values and defaults for the dependent parameters if a value of 1
is entered for thealt_qual_proc parameter.

Table 6-2 alt_qual_proc=1 parameter values

Dependent parameter Range Default

l_rxqual_ul_p 0 to 7 4
l_rxqual_dl_p 0 to 7 4
u_rxqual_ul_p 0 to 7 1
u_rxqual_dl_p 0 to 7 1
l_rxqual_ul_h 0 to 7 5
l_rxqual_dl_h 0 to 7 5
l_rxqual_dl_h_hopping 0 to 7 4
l_rxqual_ul_h_hopping 0 to 7 4
l_rxqual_dl_p_hopping 0 to 7 4

Continued

68P02901W23-T 6-31
Jan 2010
Description Chapter 6: CM database parameters

Table 6-2 alt_qual_proc=1 parameter values (Continued)

Dependent parameter Range Default
l_rxqual_ul_p_hopping 0 to 7 4
l_rxqual_dl_h_data 0 to 7 4
l_rxqual_ul_h_data 0 to 7 4
l_rxqual_dl_p_data 0 to 7 4
l_rxqual_ul_p_data 0 to 7 4
l_rxqual_ul_p_amr_fr 0 to 7 4
l_rxqual_dl_p_amr_fr 0 to 7 3
l_rxqual_ul_h_amr_fr 0 to 7 5
l_rxqual_dl_h_amr_fr 0 to 7 4
l_rxqual_dl_h_hopping_amr_fr 0 to 7 5
l_rxqual_ul_h_hopping_amr_fr 0 to 7 6
l_rxqual_dl_p_hopping_amr_fr 0 to 7 4
l_rxqual_ul_p_hopping_amr_fr 0 to 7 5
l_rxqual_ul_p_hr 0 to 7 2
l_rxqual_dl_p_hr 0 to 7 2
u_rxqual_ul_p_hr 0 to 7 0
u_rxqual_dl_p_hr 0 to 7 0

l_rxqual_ul_h_hr 0 to 7 3
l_rxqual_dl_h_hr 0 to 7 3
l_rxqual_dl_h_hopping_hr 0 to 7 3
l_rxqual_ul_h_hopping_hr 0 to 7 3
l_rxqual_dl_p_hopping_hr 0 to 7 2
l_rxqual_ul_p_hopping_hr 0 to 7 2

Type B (operator actions required)

Supported by OMC-R GUI
Cell description required
Dependencies
Operator actions
Yes
Yes
The value that is entered for the alt_qual_proc parameter
determines the type of values, the range of values, and the
default values for the dependent parameters.
Respond to the parameters that are presented when the
chg_cell_element command is used to change the value of
the alt_qual_proc parameter.

6-32 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

Syntax

Change command strings

add_cell <gsm_cell_id> <location>

chg_cell_element alt_qual_proc <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element alt_qual_proc <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 BER units
1 Qb and units
Default value 0

68P02901W23-T 6-33
Jan 2010
amr_bss_half_rate_enabled Chapter 6: CM database parameters

amr_bss_half_rate_enabled

Description

The amr_bss_half_rate_enabled parameter enables or disables the Adaptive Multi-Rate (AMR)

Half Rate at the BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
In the case of remote transcoding, at least one AXCDR must
have CIC validation enabled.
The handover_required_sp_ver_used parameter must be
enabled.
This parameter applies only to the BSC.

Syntax

Add/Change command strings

chg_element amr_bss_half_rate_enabled <value> 0

Display command strings

disp_element amr_bss_half_rate_enabled 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-34 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference amr_bss_full_rate_enabled

amr_bss_full_rate_enabled

Description

The amr_bss_full_rate_enabled parameter enables or disables the Adaptive Multi-Rate (AMR)

Full Rate at the BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The AMR feature must be unrestricted.
In the case of remote transcoding, at least one AXCDR
must have CIC validation enabled.
The handover_required_sp_ver_used parameter must be
enabled.
This parameter applies only to the BSC.

Syntax

Add/Change command strings

chg_element amr_bss_full_rate_enabled <value> 0

Display command strings

disp_element amr_bss_full_rate_enabled 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-35
Jan 2010
amr_dl_la_mode_chg_min Chapter 6: CM database parameters

amr_dl_la_mode_chg_min

Description

The amr_dl_la_mode_chg_min parameter specifies the minimum network allowed time period
between consecutive changes in the downlink codec mode.

The downlink adaptation process possesses an inherent round-trip delay whose typical value
(negligible E1 transmission delay is assumed) is 10 to 12 speech frame periods (20 ms each).
This delay begins with the MS issuance of a new CMR to the network and terminates with the
MS reception of the matching CMI. Setting this parameter to any value less than the inherent
delay results in the same system behavior, namely an adaptation period equal to the inherent
delay. When the parameter is set to a value greater than the inherent delay, a wait period
is added to slow down the adaptation process, that is, the time between consecutive codec
changes to the period specified by the parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command strings

chg_element amr_dl_la_mode_chg_min <value> <location> <cell_desc>

Display command strings

disp_element amr_dl_la_mode_chg_min <location> <cell_desc>

Values

Value type Integer (number of 20 ms periods)

Valid range 0 to 63
Default value 5

6-36 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference amr_dl_thresh_adjust

amr_dl_thresh_adjust

Description

The amr_dl_thresh_adjust parameter specifies the compensation for the Carrier to

Interference (C/I) adaptation thresholds.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command strings

chg_element amr_dl_thresh_adjust <value> <location>

Display command strings

disp_element amr_dl_thresh_adjust <location>

Values

Value type dB
Valid range 1 to 7
Default value 3

68P02901W23-T 6-37
Jan 2010
amr_fr_dl_la_enabled Chapter 6: CM database parameters

amr_fr_dl_la_enabled

Description

The amr_fr_dl_la_enabled parameter enables or disables Full Rate Downlink Codec Mode
Adaptation on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command strings

chg_element amr_fr_dl_la_enabled <value> <location> <cell_desc>

chg_cell_element amr_fr_dl_la_enabled <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element amr_fr_dl_la_enabled <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

6-38 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference amr_fr_ul_la_enabled

amr_fr_ul_la_enabled

Description

The amr_fr_ul_la_enabled parameter enables or disables Full Rate Uplink Codec Mode
Adaptation on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command strings

chg_element amr_fr_ul_la_enabled <value> <location> <cell_desc>

chg_cell_element amr_fr_ul_la_enabled <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element amr_fr_ul_la_enabled <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

68P02901W23-T 6-39
Jan 2010
amr_full_rate_enabled Chapter 6: CM database parameters

amr_full_rate_enabled

Description

The amr_full_rate_enabled parameter enables or disables the AMR Full Rate at a cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
This parameter does not apply to a remote transcoder
(RXCDR).
This parameter does not apply to a standalone BSC site
(that is, a site without a collocated BTS).

Syntax

Change command strings

chg_element amr_full_rate_enabled <value> <location> <cell_desc>

chg_cell_element amr_full_rate_enabled <value> <cell_desc_opt>

NOTE
The chg_cell_element command cannot be used to change this parameter unless
the site is an AMR-capable BTS.

Display command strings

disp_cell <cell_id> [full]

disp_element amr_full_rate_enabled <location> <cell_desc>

NOTE
The copy_cell command sets this parameter to disabled.

6-40 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-41
Jan 2010
amr_half_rate_enabled Chapter 6: CM database parameters

amr_half_rate_enabled

Description

The amr_half_rate_enabled parameter enables or disables the AMR Half Rate at a cell.

The amr_half_rate_enabled cell element parameter can be modified using the chg_element or
chg_cell_element command, and displayed with the disp_cell full command.

NOTE
The amr_half_rate_enabled RTF element parameter has been renamed
half_rate_enabled (see half_rate_enabled on page 6-399).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
The amr_half_rate_enabled cell parameter can only be
modified or set at a BTS site comprised solely of M-Cell2/6
or Horizonmacro cabinets or a mixture of both. The
amr_half_rate_enabled cell parameter can be modified or
set at an M-Cell2/6 site only if the TCU-A/TCU-B optional
features are unrestricted.

Syntax

Add/Change command strings

chg_element amr_half_rate_enabled <value> <location> <cell_desc>

chg_cell_element amr_half_rate_enabled <value> <cell_desc_opt>

Display command strings

disp_element amr_half_rate_enabled <location> <cell_desc>

disp_cell <cell_id> full

NOTE
The copy_cell command sets the cell element parameter to disabled.

6-42 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-43
Jan 2010
amr_home_filter_enabled Chapter 6: CM database parameters

amr_home_filter_enabled

{34452}

Description

The amr_home_filter_enabled parameter specifies whether the AMR homing filter is enabled.
This parameter can be accessed and updated both in and out of sysgen mode without warning.

NOTE

This parameter is set to DISABLED by default. It is recommended to change

this parameter at midnight.
Do not enable and disable this parameter during the scheduled daily MSI audit
period.
Frequent toggling of the parameter within a few minutes may cause the MSI to
OOS and manual operation is required to recover the device.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only on the RXCDR or the
local transcoder BSC.

Syntax

Change command string

chg_element amr_home_filter_enabled <value> <location>

Display command string

disp_element amr_home_filter_enabled <location>

6-44 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1
0 Disables AMR homing filter.
1 Enables AMR homing filter.
Default value 0

68P02901W23-T 6-45
Jan 2010
amr_hr_dl_la_enabled Chapter 6: CM database parameters

amr_hr_dl_la_enabled

Description

The amr_hr_dl_la_enabled parameter enables or disables Half Rate Downlink Codec Mode
Adaptation on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command strings

chg_element amr_hr_dl_la_enabled <value> <location> <cell_desc>

chg_cell_element amr_hr_dl_la_enabled <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element amr_hr_dl_la_enabled <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

6-46 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference amr_hr_ul_la_enabled

amr_hr_ul_la_enabled

Description

The amr_hr_ul_la_enabled parameter enables or disables Half Rate Uplink Codec Mode
Adaptation on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command strings

chg_element amr_hr_ul_la_enabled <value> <location> <cell_desc>

chg_cell_element amr_hr_ul_la_enabled <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element amr_hr_ul_la_enabled <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

68P02901W23-T 6-47
Jan 2010
amr_ms_high_cmr Chapter 6: CM database parameters

amr_ms_high_cmr

Description

The amr_ms_high_cmr parameter specifies the percentages for monitoring AMR MSs
continually requesting the highest codec mode at a BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command string

chg_element amr_ms_high_cmr <value> <location>

Display command string

disp_element amr_ms_high_cmr <location>

Values

Value type Percentages

Valid range 50 to 100
Default value 95

6-48 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference amr_ms_high_rxqual

amr_ms_high_rxqual

Description

The amr_ms_high_rxqual parameter specifies the threshold for monitoring AMR MSs
continually requesting the highest codec mode at a BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command strings

chg_element amr_ms_high_rxqual <value> <location>

Display command strings

disp_element amr_ms_high_rxqual <location>

Values

Value type QBand units

Valid range 0 to 7
Default value 4 (2.5% BER or RXQUAL 4)

68P02901W23-T 6-49
Jan 2010
amr_ms_low_cmr Chapter 6: CM database parameters

amr_ms_low_cmr

Description

The amr_ms_high_cmr parameter specifies the percentages for monitoring AMR MSs
continually requesting the lowest codec mode at a BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command strings

chg_element amr_ms_low_cmr <value> <location>

Display command strings

disp_element amr_ms_low_cmr <location>

Values

Value type Percentages

Valid range 50 to 100
Default value 99

6-50 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference amr_ms_low_rxqual

amr_ms_low_rxqual

Description

The amr_ms_high_rxqual parameter specifies the threshold for monitoring MSs continually
requesting the lowest mode at a BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command strings

chg_element amr_ms_low_rxqual <value> <location>

Display command strings

disp_element amr_ms_low_rxqual <location>

Values

Value type QBand units

Valid range 0 to 7
Default value 2 0.5% BER or RXQUAL 2

68P02901W23-T 6-51
Jan 2010
amr_ms_monitor_period Chapter 6: CM database parameters

amr_ms_monitor_period

Description

The amr_ms_monitor_period parameter is used for detecting MSs continually requesting the
highest or lowest modes at a BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The AMR feature must be unrestricted.

Syntax

Add/Change command strings

chg_element amr_ms_monitor_period <value> <location>

Display command strings

disp_element amr_ms_monitor_period <location>

Values

Value type Integer (SACCH periods)

Valid range 10 to 120 SACCH periods
0 Disable parameter
Default value 40

6-52 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference arp_bg_1

arp_bg_1

Description

The arp_bg_1 parameter specifies the Allocation and Retention Priority (ARP) value of
background traffic class, precedence class 1. The system will interpret the decimal value into
decimal value of 4 parts, according to ARP IE structure:
qa

priority level/ arp value

pci

pvi

This ARP information is used during the admission control and retention of PFC when they can
not be derived from SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The arp_bg_1 parameter can only be modified if the Quality
of Service feature (qosOpt) is not restricted. The priority
level value of arp_bg_1 is less than or equal to those of
arp_bg_2 and arp_bg_3. The arp_bg_1 parameter may be
accessed/ updated both in and out of sysgen mode.

Syntax

Change command strings

chg_element arp_bg_1 <value> <location>

Display command strings

disp_element arp_bg_1 <location>

68P02901W23-T 6-53
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 4 to 59
68 to 123
Default value 49 (pci=0, priority level=12, pvi=0)

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 7 6 5 4 3 2 1
spare pci priority level qa pvi

NOTE
The value of qa bit is not used in GSR10.

6-54 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference arp_bg_2

arp_bg_2

Description

The arp_bg_2 parameter specifies the Allocation and Retention Priority (ARP) value of
background class, precedence class 2. The system will interpret the decimal value into decimal
value of 4 parts, according to ARP IE structure:
qa

priority level/ arp value

pci

pvi

This ARP information is used during the admission control and retention of PFC when they can
not be derived from SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes

Cell description required No

Dependencies The arp_bg_2 parameter can only be modified if the

Quality of Service feature (qosOpt) is not restricted. The
priority level value of arp_bg_2 is less than or equal to that
of arp_bg_3 and greater than or equal to that of arp_bg_1.
The arp_bg_2 parameter may be accessed/ updated both
in and out of sysgen mode.
Syntax

Change command strings

chg_element arp_bg_2 <value> <location>

Display command strings

disp_element arp_bg_2 <location>

68P02901W23-T 6-55
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 4 to 59
68 to 123
Default value 53 (pci=0, priority level=13, pvi=1)

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 7 6 5 4 3 2 1
spare pci priority level qa pvi

NOTE
The value of qa bit is not used in GSR10.

6-56 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference arp_bg_3

arp_bg_3

Description

The arp_bg_3 parameter specifies the Allocation and Retention Priority (ARP) value of
background class, precedence class 3. The system will interpret the decimal value into decimal
value of 4 parts, according to ARP IE structure:
qa

priority level/ arp value

pci

pvi

This ARP information is used during the admission control and retention of PFC when they can
not be derived from SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The priority level value of arp_bg_3 is greater than or
equal to those of arp_bg_1 and arp_bg_2. The arp_bg_3
parameter may be accessed/updated both in and out of
sysgen mode.

Syntax

Change command strings

chg_element arp_bg_3 <value> <location>

Display command strings

disp_element arp_bg_3 <location>

68P02901W23-T 6-57
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 4 to 59
68 to 123
Default value 57 (pci=0, priority level=14, pvi=1)

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 7 6 5 4 3 2 1
spare pci priority level qa pvi

NOTE
The value of qa bit is not used in GSR10.

6-58 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference arp_i_be_1

arp_i_be_1

Description

The arp_i_be_1 parameter specifies the Allocation and Retention Priority (ARP) value of
Interactive or Best Effort traffic class, precedence class 1. The system will interpret the decimal
value into decimal value of 4 parts, according to ARP IE structure:
qa

priority level/ arp value

pci

pvi

Type A (no operator actions)

Supported by OMC-R GUI Yes

Cell description required Yes
Dependencies The arp_i_be_1 parameter can only be modified if the
Quality of Service feature (qosOpt) is unrestricted. The
priority level value of arp_i_be_1 is less than or equal
to those of arp_i_be_2 and arp_i_be_3. The arp_i_be_1
parameter may be accessed/ updated both in and out of
sysgen mode.

Syntax

Change command strings

chg_element arp_i_be_1 BSC

Display command strings

disp_element arp_i_be_1 <location>

68P02901W23-T 6-59
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 4 to 59
68 to 123
Default value 93 (pci=1, priority level=7, pvi=1)

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 7 6 5 4 3 2 1
spare pci priority level qa pvi

NOTE
The value of qa bit is not used in GSR10.

6-60 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference arp_i_be_2

arp_i_be_2

Description

The arp_i_be_2 parameter specifies the Allocation and Retention Priority (ARP) value of
Interactive or Best Effort traffic class, precedence class 2. The system will interpret the decimal
value into decimal value of 4 parts, according to ARP IE structure:
qa

priority level/arp value

pci

pvi

This ARP information is used during the admission control and retention of PFC when they can
not be derived from SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The arp_i_be_2 parameter can only be modified if the
Quality of Service feature (qosOpt) is not restricted.
The priority level value of arp_i_be_2 is less than or
equal to that of arp_i_be_3 and greater than or equal to
that of arp_i_be_1. The arp_i_be_2 parameter may be
accessed/updated both in and out of sysgen mode.

Syntax

Change command strings

chg_element arp_i_be_2 BSC

Display command strings

disp_element arp_i_be_2 <location>

68P02901W23-T 6-61
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 4 to 59
68 to 123
Default value 97 (pci=1, priority level=8, pvi=1)

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 7 6 5 4 3 2 1

spare pci priority level qa pvi

NOTE
The value of qa bit is not used in GSR10.

6-62 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference arp_i_be_3

arp_i_be_3

Description

The arp_i_be_3 parameter specifies the Allocation and Retention Priority (ARP) value of
Interactive or Best Effort traffic class, precedence class 3. The system will interpret the decimal
value into decimal value of 4 parts, according to ARP IE structure:
qa

priority level/ arp value

pci

pvi

This ARP information is used during the admission control and retention of PFC when they can
not be derived from SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The arp_i_be_3 parameter can only be modified if the
Quality of Service feature (qosOpt) is not restricted.The
priority level value of arp_i_be_3 is greater than or equal
to those of arp_i_be_1 and arp_i_be_2. The arp_i_be_3
parameter may be accessed/updated both in and out of
sysgen mode.

Syntax

Change command strings

chg_element arp_i_be_3 BSC

Display command strings

disp_element arp_i_be_3 <location>

68P02901W23-T 6-63
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 4 to 59
68 to 123
Default value 101 (pci=1, priority level=9, pvi=1)

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 7 6 5 4 3 2 1
spare pci priority level qa pvi

NOTE
The value of qa bit is not used in GSR10.

6-64 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference arp_streaming_1

arp_streaming_1

Description

The arp_streaming_1 parameter specifies the Allocation and Retention Priority (ARP) value of
streaming traffic class, precedence class 1. The system will interpret the decimal value into
decimal value of 4 parts, according to ARP IE structure:
qa

priority level/ arp value

pci

pvi

This ARP information is used during the admission control and retention of PFC when they can
not be derived from SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The arp_streaming_1 parameter can be modified only if
the QoS Phase 2 feature (qosOpt) is unrestricted.

The priority level value of arp_streaming_1 is less than or

equal to those of arp_streaming_2 and arp_streaming_3.
The arp_streaming_1 parameter may be accessed/updated
both in and out of sysgen mode.

Syntax

Change command strings

chg_element arp_streaming_1 <value> <location>

Display command strings

disp_element arp_streaming_1 <location>

68P02901W23-T 6-65
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 4 to 123
68 to 123
Default value 68 (pci =1, priority level =1, pvi =0)

NOTE
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 7 6 5 4 3 2 1
spare pci priority level qa pvi

NOTE
The value of qa bit is not used in GSR10.

6-66 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference arp_streaming_2

arp_streaming_2

Description

The arp_streaming_2 parameter specifies the Allocation and Retention Priority (ARP) value of
streaming traffic class, precedence class 2. The system will interpret the decimal value into
decimal value of 4 parts, according to ARP IE structure:
qa

piority level/ arp value

pci

pvi

This ARP information is used during the admission control and retention of PFC when they can
not be derived from SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The arp_streaming_2 parameter can be modified only if
the QoS Phase 2 feature (qosOpt) is not restricted

The priority level value of arp_streaming_2 is less than

or equal to that of arp_streaming_3 and greater than or
equal to that of arp_streaming_1. The arp_streaming_2
parameter may be accessed/ updated both in and out of
sysgen mode.

Syntax

Change command strings

chg_element arp_streaming_2 <value> <location>

Display command strings

disp_element arp_streaming_2 <location>

68P02901W23-T 6-67
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 4 to 59
68 to 123
Default value 73 (pci=1, priority level=2, pvi=1)

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 7 6 5 4 3 2 1
spare pci priority level qa pvi

NOTE
The value of qa bit is not used in GSR10.

6-68 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference arp_streaming_3

arp_streaming_3

Description

The arp_streaming_3 parameter specifies the Allocation and Retention Priority (ARP) value of
streaming traffic class, precedence class 1. The system will interpret the decimal value into
decimal value of 4 parts, according to ARP IE structure:
qa

priority level/ arp value

pci

pvi

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The arp_streaming_3 parameter can be modified only if
the QoS Phase 2 feature (qosOpt) is not restricted.

The priority level value of arp_streaming_3 is greater

than or equal to those of arp_streaming_1 and
arp_streaming_2. The arp_streaming_3 parameter may
be accessed/ updated both in and out of sysgen mode.

Syntax

Change command strings

chg_element arp_streaming_3 <value> <location>

Display command strings

disp_element arp_streaming_3 <location>

68P02901W23-T 6-69
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 4 to 59
68 to 123
Default value 77 (pci=1, priority level=3, pvi=1)

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 7 6 5 4 3 2 1

spare pci priority level qa pvi

NOTE
The value of qa bit is not used in GSR10.

6-70 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference asym_edge_enabled

asym_edge_enabled

Description

The asym_edge_enabled element enables or disables support of asymmetric EGPRS for

CTU2-D on per SITE basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The asym_edge_enabled parameter is modified only if
CTU2-D asymmetric feature is unrestricted. It is enabled
at sites where the master SITE cabinet is a member of the
Horizon II family (Horizon II macro, Horizon II mini and
Horizon II micro).

Syntax

Change command strings

chg_element asym_edge_enabled <value> <location>

Display command strings

disp_element asym_edge_enabled <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-71
Jan 2010
attach_detach Chapter 6: CM database parameters

attach_detach

Description

The attach_detach parameter enables and disables the mandatory International Mobile
Subscriber Identity (IMSI) attach/detach for the MS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element attach_detach <value> <location> <cell_desc>

chg_cell_element attach_detach <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element attach_detach <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-72 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter ATT

GSM technical specification 4.08 - 4.4.3 - attach
4.08 - 4.3.4 - detach
4.08 - 10.5.2.8
4.08 - 9.1.31
12.20 - 5.2.8.8 config CCH - allow IMSI Attach Detach

68P02901W23-T 6-73
Jan 2010
auto_rf_loss_trace Chapter 6: CM database parameters

auto_rf_loss_trace

Description

The auto_rf_loss_trace parameter enables and disables automatic RF Loss tracing for a
cell. The destination for RF loss measurement reports is also specified when RF loss tracing
is enabled.

If the auto_rf_loss_trace parameter is enabled for a cell with the destination set for the MMI
and an RF loss occurs in the cell, a measurement report is sent to the MMI and is displayed
in the same format as the output for the trace_call command. An RLM cause for the RF
loss is included in the additional trace status field when the RF loss trace generates the
measurement report.

**** START OF RF LOSS REPORT ****

* Sequence Number 0

* SCCP Number 0018c0h

* Scope 001 01 1 (0001h) 1 (0001h)

* Carrier site=1 RTF 0 0

* Channel 0e 00 0a

* Trace Status RF Loss - Loss of uplink SACCH

* Time Stamp 01/03/1980 08:04:33.745

* Call Duration 00:00:48.690

* Mobile ID TMSI=00050603

* CIC 0002h

* Call Lost Yes

* RSS Data: Time: 01/03/1980 08:04:33.745

* 1b 37 19 03 00 00 1b 04 14 0a 10 04

* Measurement result info: 01 00 00 00 00 07 07

* Neighbor: 01 1e 10 00

* Timing Advance Info: c9 00 00

**** END OF RF LOSS REPORT ****

6-74 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

Type A (no operator action)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The auto_rf_loss_trace parameter is valid for any GPROC
except the CSFP.

Syntax

Change command strings

chg_element auto_rf_loss_trace <value> <location> <cell_desc>

chg_cell_element auto_rf_loss_trace <value> <cell_desc_opt>

Display command string

disp_element auto_rf_loss_trace <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 2
0 Automatic RF loss tracing disabled for this cell.
1 Automatic RF loss tracing enabled for this cell; send
measurement reports to MMI and OMC-R.
2 Automatic RF loss tracing enabled for this cell; send
measurement reports to OMC-R only.
Default value 0

References

GSM parameter None

GSM technical specification This is a Motorola parameter.

RLM cause values are defined in TS GSM 08.58, section

9.3.22

68P02901W23-T 6-75
Jan 2010
ba_alloc_proc Chapter 6: CM database parameters

ba_alloc_proc

Description

The ba_alloc_proc parameter enables and disables the reinitialization of the active block
following a change in the broadcast control channel allocation (BA) and the suspension of
subsequent measurements until the new BA is reported.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element ba_alloc_proc <value> <location> <cell_desc>

chg_cell_element ba_alloc_proc <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ba_alloc_proc <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Reinitialization disabled
1 Reinitialization enabled
Default value 0

6-76 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter None

GSM technical specification This is a Motorola parameter.

68P02901W23-T 6-77
Jan 2010
band_preference Chapter 6: CM database parameters

band_preference

Description

The band_preference parameter displays the frequency band that the cell prefers to use for
handovers and specifies the destination frequency band for inter-cell handovers.

Setting the value of band_preference to 16 (Dynamic) enables Intelligent Multi-layer Resource

Management (IMRM) within the cell only if the IMRM feature is unrestricted. When setting
this parameter to 16 the BSS prompts for the band weightings for PGSM, EGSM, DCS 1800,
and, if the 2G/3G feature is unrestricted, UMTS. Setting all supported IMRM band weights to
0 raises a Warning indicating that the BSS shall apply internal defaults in the IMRM band
selection algorithm. The change command is rejected if more than one IMRM weight is set to
the maximum value of 100.

Type A (No operator action)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Multiband Inter-cell handover feature must be enabled.
This parameter has no meaning if band_preference_mode
= 0 for this cell.
If BPM=1, then the BSS attempts to assign a Multiband
MS to the strongest preferred band neighbor that the MS
reported at the time of SDCCH to TCH assignment.
The IMRM feature must be unrestricted to support the
setting of this parameter to 16 (Dynamic).
The 2G/3G feature must be unrestricted to set the IMRM
weighing for UMTS.

Syntax

Change command strings

chg_cell_element band_preference <value> <cell_desc_opt>

Display command string

disp_element band_preference <location> <cell_desc>

6-78 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Select integer

Valid range
1 to 16
1 (PGSM)
2 (EGSM)
4 (DCS1800)
8 (PCS1900)
16 (DYNAMIC)
Default value The frequency type of the cell (as set by frequency_type).

References

GSM parameter None

GSM technical specification This is a Motorola parameter.

68P02901W23-T 6-79
Jan 2010
band_preference_mode Chapter 6: CM database parameters

band_preference_mode

Description

The band_preference_mode parameter specifies the method the system uses to program a
Multiband MS with the preferred frequency band for a given cell in the BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Multiband Inter-cell handover feature must be
unrestricted.

Syntax

Change command strings

chg_element band_preference_mode <value> <location> <cell_desc>

chg_cell_element band_preference_mode <value> <cell_desc_opt>

Display command string

disp_element band_preference_mode <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 6
0 The BSS attempts to hand a Multiband MS over to the
strongest neighbor that the MS reported when a handover
is required for normal radio resource reasons.

6-80 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

1 The BSS attempts to assign a multiband MS to the

preferred band within the cell at the time of SDCCH to
TCH assignment. If the preferred band is the secondary
band and no secondary resource is available within the
cell or the MS does not meet the inner zone criteria,
the BSS attempts to assign the MS to the strongest MS
reported neighbor with a BCCH in the preferred band or
non-preferred neighbor with a resource in the preferred
band. If that is not possible, a resource is assigned from
the serving cells non-preferred band. If the preferred band
is the primary band and no primary resource is available
within the cell, the call cannot be assigned.
2 The BSS attempts to handover a multiband MS to the
strongest MS reported neighbor with a BCCH in the
preferred band or non-preferred neighbor with resource in
the preferred band when a handover is required for normal
radio resource reasons. The BSS places preferred band
neighbors ahead of non-preferred band neighbors in order
to attempt to assign a channel from the preferred band
for the MS. At the time of SDCCH to TCH assignment,
if the preferred band is the secondary band and the MS
provides sufficient Measurement Reports, a resource is
provided from the cell inner zone. If the preferred band is
not the secondary band or the MS fails to provide enough
Measurement Reports, the resource is assigned from the
cell outer zone.
3 This value combines the functions of values 1 and 2.
The BSS attempts to assign a multiband MS to the
preferred band within the cell at the time of SDCCH to
TCH assignment. If the preferred band is the secondary
band and no secondary resource is available within the
cell or the MS does not meet the inner zone criteria,
the BSS attempts to assign the MS to the strongest MS
reported neighbor with a BCCH in the preferred band or
non-preferred neighbor with a resource in the preferred
band. If that is not possible, a resource is assigned from
the serving cells non-preferred band.
The BSS attempts to handover a multiband MS to the
strongest MS reported neighbor with a BCCH in the
preferred band or non-preferred neighbor with resource in
the preferred band when a handover is required for normal
radio resource reasons.
4 The BSS continually attempts to hand a Multiband MS
over to a preferred band TCH immediately after initial
assignment. The BSS does not attempt to allocate a
TCH in the preferred band for this MS at the time of
SDCCH-to-TCH assignment. The BSS enters a mode
of continually monitoring for qualified preferred-band
neighbors reported by the MS in order to hand the MS
over. The BSS stays in this mode until it finds a neighbor
TCH in the preferred band for the current serving cell.
Handovers for normal radio resource reasons may occur
during the monitoring mode, and these handovers will be to
the strongest preferred band neighbor reported by the MS.

68P02901W23-T 6-81
Jan 2010
References Chapter 6: CM database parameters

5 The BSS attempts to assign a Multiband MS to the

strongest preferred-band neighbor reported by the MS at
the time of SDCCH-to-TCH assignment.
If this assignment is not possible, the BSS enters a mode
of continually monitoring for qualified preferred-band
neighbors reported by the MS in order to handover the MS.
The BSS stays in this mode until it finds a neighbor TCH in
the preferred band. Handovers for normal radio resource
reasons may occur during the monitoring mode, and these
handovers will be to the strongest preferred band neighbor
reported by the MS.
This value combines the functions of values 1, 2, and 4.
6 The BSS attempts to assign a Multiband MS to the
strongest preferred band neighbor reported by the MS only
after a cell has become congested.
If this assignment is not possible, the BSS enters a mode
of continually monitoring for qualified preferred-band
neighbors reported by the MS in order to hand over the
MS. The BSS stays in this mode until it finds a neighbor
TCH in the preferred band. Handovers for normal radio
resource reasons may occur during the monitoring mode,
and these handovers will be to the strongest preferred
band neighbor reported by the MS.
This type should be used in order to activate the multiband
congestion threshold verification.
This value functions identically to value 5, except it is
triggered only when the cell is congested.
Default value 0

NOTE
In IMRM cells, band_preference_mode setting of 6, designed to limit multiband
activity based on utilization, is overridden and handled as for a band_preference_mode
setting of 5.

References

GSM parameter None

GSM technical specification This is a Motorola parameter.

6-82 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference base_ip_address

base_ip_address

Description

The base IP address is used for the PCU and PSI. For PCU, there must be 24 contiguous
addresses available after the IP address. For PSI, there must be 17 contiguous addresses
available after the IP address. The Base IP address is entered in dotted quad notation.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

modify_value

Values

Value type Integer

Valid range For PCU
1.0.0.1 (minimum)
223.255.255.231 (maximum)

For PSI
1.0.0.1 (minimum)
223.255.255.237 (maximum)
Default value For PCU
10.0.0.1

For PSI
None

68P02901W23-T 6-83
Jan 2010
Values Chapter 6: CM database parameters

NOTE
If the ePCU fails to boot up in the DD2 mode, there is a PCU base_ip_address
mismatch between the BSC database and the new MPROC default IP address
configured during the manufacture. Use the following EMON commands on the
master MPROC to check and modify:

cage_ip create: Creates a new config file. Every parameter value is set by
default.
cage_ip read: read base_ip, netmask and the router address.
cage_ip write <item> <value>: set base ip
netmask and the router address <item>: base_ip
netmask
router <value>: ip address value

The following examples show the usage of the commands:

PCU:emon_1107 % cage_ip create
Emon create BASE IP suc ! base_ip 0 .0 .0 .0 ,
subnet_mask 255 .255 .255 .0 ,router_addr 0 .0 .0 .0
PCU:emon_1107 % cage_ip read
Emon Got BASE IP suc ! base_ip 0 .0 .0 .0 ,
subnet_mask 255 .255 .255 .0 ,router_addr 0 .0 .0 .0
PCU:emon_1107 % cage_ip write base_ip "10.1.1.71"
Emon Set BASE IP suc ! base_ip 10 .1 .1 .71
PCU:emon_1107 % cage_ip write router "255.255.0.0"
Emon Set router suc ! router 255.255.0.0
PCU:emon_1107 % cage_ip read
Emon Got BASE IP suc ! base_ip 10 .1 .1 .71 ,
subnet_mask 255 .255 .255 .0 ,router_addr 255.255.0.0

6-84 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ber_loss_daily

ber_loss_daily

Description

The ber_loss_daily parameter specifies the daily Bit Error Rate (BER) alarm threshold. An
alarm is generated if the BER exceeds this threshold in a given 24 hour period.

This parameter represents the exponent of threshold BER. For example, 3 is the exponent
value of 103, indicating 1 bit error in 1000 bits.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element ber_loss_daily <value> <location>

Display command string

disp_element ber_loss_daily <location>

Values

Value type Integer

Valid range 3 to 6
Default value 5

References

GSM parameter None

GSM technical specification This is a Motorola parameter.

68P02901W23-T 6-85
Jan 2010
ber_loss_hourly Chapter 6: CM database parameters

ber_loss_hourly

Description

The ber_loss_hourly parameter specifies the hourly Bit Error Rate (BER) alarm threshold.

This parameter represents the exponent of threshold BER. For example, 3 is the exponent
value of 103, indicating 1 bit error in 1000 bits.

An alarm is generated if the BER exceeds this threshold in a given 60 minute period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element ber_loss_hourly <value> <location>

Display command string

disp_element ber_loss_hourly <location>

Values

Value type Integer

Valid range 3 to 6
Default value 4

References

GSM parameter None

GSM technical specification This is a Motorola parameter.

6-86 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference blind_search_preference

blind_search_preference

Description

The blind_search_preference parameter indicates preference for blind search in idle mode.
Blind search allows the BSS to just broadcast the FDD-ARFCN by itself without any cells
specified. This reduces the size of neighbor list broadcast to the MS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Enhanced 2G/3G Handover feature must be
unrestricted to modify this parameter.

Syntax

Change command string

chg_element blind_search_preference <value> <location>

chg_cell_element blind_search_preference <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> [full]

disp_element blind_search_preference <location>

Values

Value type Boolean

Valid range 0 to 1
0 No blind search in idle mode.
1 Blind search in idle mode.
Default value 0

68P02901W23-T 6-87
Jan 2010
bounce_protect_margin Chapter 6: CM database parameters

bounce_protect_margin

Description

The bounce_protect_margin parameter, in conjunction with the ho_margin_cell parameter,

specifies the level by which a target cell must exceed the serving cell.

This parameter prevents continuous handover bouncing between cells due to RXQUAL level and
congestion reasons.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies After an RXQUAL handover, the system applies the
bounce_protect_margin value for the number of SACCH
periods set by the bounce_protect_qual_tmr timer.
After a congestion handover, the system applies the
bounce_protect_margin value for the number of SACCH
periods set by the bounce_protect_cong_tmr timer.

Syntax

Change command strings

chg_element bounce_protect_margin <value> <location> <cell_desc>

chg_cell_element bounce_protect_margin <value> <cell_desc_opt>

Display command string

disp_element bounce_protect_margin <location> <cell_desc>

Values

Value type Integer (decibels)

Valid range 0 to 127
Default value 0

6-88 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bs_ag_blks_res

bs_ag_blks_res

Description

The bs_ag_blks_res parameter specifies the number of blocks reserved for access grant per
51-multiframes. The number of blocks reserved starting with (and including) block 0 are
broadcast in the BCCH. The number of blocks reserved for access grant messages reduces the
number of paging blocks available.

The ratio of MS-originated calls to MS-terminated calls determines the choice of value.

PCH and AGCH share the same TDMA mapping when combined onto a basic physical channel.
Channels are shared on a block by block basis.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies If no AGCH is reserved in a non-combined cell
(bs_ag_blks_res = 0) and ccch_conf is other than 1),
enabling of CBCH is not permitted (cbch_enabled = 1).
Operator actions Reset the site after changing the bs_ag_blks_res value.

Syntax

Add/Change command strings

chg_element bs_ag_blks_res <value> <location> <cell_desc>

chg_cell_element bs_ag_blks_res <value> <cell_desc_opt>

NOTE
A site reset is required when the value of bs_ag_blks_res is changed. Resetting the
site generates several alarms. However, the system blocks these alarms.

Display command strings

disp_element bs_ag_blks_res <location> <cell_desc>

68P02901W23-T 6-89
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range The range of values depends on the value of the ccch_conf parameter:
0 to 2 blocks reserved for ccch_conf = 1
0 to 7 blocks reserved for ccch_conf = 0
Default value 0

References

GSM parameter BS_AG_BLKS_RES

GSM technical specification
5.02 - 6.5, and section 7 table 5
4.08 - 10.5.2.8, figure 10.27, and table 10.21
4.08 - 3.3.2.1, 10.5.2.14: page mode information element
12.20 - 5.2.8.8 - config CCH - no of blocks for access grant
message

6-90 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bs_pa_mfrms

bs_pa_mfrms

Description

The bs_pa_mfrms parameter specifies the number of multiframes between transmissions of

paging messages to MSs of the same paging group. The number of paging blocks available (per
CCCH) are those available (on a specific CCCH) multiplied by (bs_pa_mfrms).

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The value chosen for this field depends on the size of the
location area and the ratio of mobile originated to mobile
terminated calls.
Operator actions Reset the site after changing the bs_pa_mfrms.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element bs_pa_mfrms <value> <location> <cell_desc>

chg_cell_element bs_pa_mfrms <value> <cell_desc_opt>

NOTE
A site reset is required when the value of bs_pa_mfrms is changed. Although
resetting the site generates several alarms, the system blocks these alarms.

Display command strings

disp_cell <cell_id> [full]

disp_element bs_pa_mfrms <location> <cell_desc>

68P02901W23-T 6-91
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (multiframes)

Valid range 0 to 7 Represents the multiframes period for the transmission of
PAGING REQUEST messages to the same paging group.
0 2 multiframes
1 3 multiframes
2 4 multiframes
3 5 multiframes
4 6 multiframes
5 7 multiframes
6 8 multiframes
7 9 multiframes
Default value 0

References

GSM parameter BS_PA_MFRMS

GSM technical specification 4.04 - 10.5.2.8, fig. 10.27, and table 10.21
5.02 - 6.5.1
5.02 - 7: table 5
5.08 - 6.5: downlink signaling failure
12.20 - 5.2.8.8 - configCCH

6-92 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bs_pag_blks_res

bs_pag_blks_res

Description

The bs_pag_blks_res specifies the number of Packet Access Grant Channel (PAGCH) blocks
per 52-frame multiframe on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.
The sum of the values set for this parameter and for
bs_pbcch_blks must be between 1 and 11.

Syntax

Add/Change command strings

chg_element bs_pag_blks_res <value> <location> <cell_desc>

chg_cell_element bs_pag_blks_res <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element bs_pag_blks_res <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 4 Number of PAGCH blocks per 52-frame multiframe.
Default value 2

NOTE
The sum of the values set for this parameter and for bs_pbcch_blks must be between
1 and 11.

68P02901W23-T 6-93
Jan 2010
bs_pbcch_blks Chapter 6: CM database parameters

bs_pbcch_blks

Description

The bs_pbcch_blks specifies the number of Packet Broadcast Control Channel (PBCCH) blocks
per 52-frame multiframe on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.
The sum of the values set for this parameter and for
bs_pag_blks_res must be between 1 and 11.
This parameter must not be set to 1 or 2 when
psi1_repeat_period is 1.

Syntax

Add/Change command strings

chg_element bs_pbcch_blks <value> <location> <cell_desc>

chg_cell_element bs_pbcch_blks <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element bs_pbcch_blks <location> <cell_desc>

Values

Value type Integer

Valid range 1 to 4 Number of PBCCH blocks per 52-frame multiframe.
Default value 2

NOTE
The sum of the values set for this parameter and for bs_pag_blks_res must be
between 1 and 11.

6-94 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bs_pcc_chans

bs_pcc_chans

Description

The bs_pcc_chans specifies the number of Packet Common Control Channel (PCCCH) timeslots
on a per cell basis.

The value indicates the number of physical channels carrying PCCCHs including the physical
channel carrying the PBCCH.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Add/Change command strings

chg_element bs_pcc_chans <value> <location> <cell_desc>

chg_cell_element bs_pcc_chans <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element bs_pcc_chans <location> <cell_desc>

Values

Value type Integer

Valid range 1 Number of physical channels with PCCCHs.
Default value 1

68P02901W23-T 6-95
Jan 2010
bs_prach_blks Chapter 6: CM database parameters

bs_prach_blks

Description

The bs_prach_blks specifies the number of Packet Random Access Channel (PRACH) blocks
per 52-frame multiframe on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Add/Change command strings

chg_element bs_prach_blks <value> <location> <cell_desc>

chg_cell_element bs_prach_blks <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element bs_prach_blks <location> <cell_desc>

Values

Value type Integer

Valid range 1 to 11 Number of PRACH blocks per 52-frame multiframe.
Default value 4

6-96 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bsc_type

bsc_type

Description

The bsc_type parameter specifies the BSC configuration type.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The value of this parameter can only be changed while in
the initial SYSGEN mode.
This command is only available for the BSC.
Operator actions Place the system in the initial SYSGEN mode then delete
the existing database using the clear_database command.

CAUTION
When the clear_database command is entered, the CM database is deleted. When
this occurs, the system does not process calls; calls in progress may be lost.

Syntax

Change command string

chg_element bsc_type <value> 0

Display command string

disp_element bsc_type 0

68P02901W23-T 6-97
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 3
0 Non Abis, Type 0
1 Non Abis, Type 1
2 Non Abis, Type 2
3 Abis, Type 0
Default value None

NOTE
Type 2 supports the upload of PCU GDBP data to OMC-R and implies that an OMF
GPROC must be present.

References

GSM parameter None

GSM technical specification This is a Motorola parameter.

6-98 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bsic

bsic

Description

The bsic parameter specifies the Base Station Identity Code (BSIC).

The BSIC is a local color code that allows an MS to distinguish between different neighboring
base stations. The BSIC is encoded on the Synchronization Channel.

The size of the BSIC is one octet made up of two values:

Network Color Code (NCC). The NCC is three bits and is the same as the Public land
mobile network (PLMN) Color Code.

Base station Color Code (BCC). The BCC is also three bits.

The values for the NCC and BCC may range from 000 to 111.

The structure of the BSIC octet is _ _ N C C B C C, where _ _ are unused. The BSIC is calculated
using Table 6-3 and Table 6-4 in this description.

A BSIC for a PLMN may have one of eight values. A BSIC may be reused, but it is important that
neighbor cells do not share the same BSIC and the same BCCH RF carrier.

NOTE
The chg_element command can change the BSIC within an operational site. There is
no requirement to unequip the RTF before making this change.

Subsystem/Process MULT
Type B (operator actions required)
Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None
Operator actions Respond to the warning prompt which are displayed after
the chg_cell_element or chg_element command is used to
modify this parameter. The warning prompt says:

WARNING: Changing this element will reset all

DRIs associated with this cell
Are you sure (y=yes, n=no)?

68P02901W23-T 6-99
Jan 2010
Syntax Chapter 6: CM database parameters

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

add_neighbor <src_gsm_cell_id> <neighbor_gsm_cell_id> <placement> [<list_type>]

chg_element bsic <value> <location> <cell_desc>

chg_cell_element bsic <value> <cell_desc_opt>

NOTE
Changing the bsic value may cause the system to take a carrier out of service. Calls
on this carrier may be lost, depending on the availability of other carriers and
timeslots not affected by the out-of-service carrier. If the carrier is baseband hopping
the system removes it from the active hopping system until the next site reset. The
system displays the following warning:

WARNING: Changing this element will reset all DRIs associated with this
cell. Are you sure (y=yes, n=no)?

A Y answer resets all the DRIs.

Display command strings

disp_cell <cell_id> [full]

disp_element bsic <location> <cell_desc>

disp_neighbor <src_gsm_cell_id>

Values

Value type Integer

Valid range Hex = 00h to 3Fh (See Table 6-3)
Decimal = 0 to 63 (See Table 6-4)
Default value None

Table 6-3 lists the hexadecimal values for the base station identity codes.

6-100 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 6-3 Base Station Identity Code - Hexadecimal Values

BCC
NCC
0 1 2 3 4 5 6 7
0 0 1 2 3 4 5 6 7
1 8 9 A B C D E F
2 10 11 12 13 14 15 16 17
3 18 19 1A 1B 1C 1D 1E 1F
4 20 21 22 23 24 25 26 27
5 28 29 2A 2B 2C 2D 2E 2F
6 30 31 32 33 34 35 36 37
7 38 39 3A 3B 3C 3D 3E 3F

Table 6-4 lists the decimal values for the base station identity codes.

Table 6-4 Base Station Identity Code - Decimal Values

BCC
NCC
0 1 2 3 4 5 6 7
0 0 1 2 3 4 5 6 7
1 8 9 10 11 12 13 14 15
2 16 17 18 19 20 21 22 23
3 24 25 26 27 28 29 30 31
4 32 33 34 35 36 37 38 39
5 40 41 42 43 44 45 46 47
6 48 49 50 51 52 53 54 55
7 56 57 58 59 60 61 62 63

References

GSM parameter BSIC, BSIC_NC(n)

GSM technical specification 3.03 - 4.2.2
3.03 - Annex A
12.20 - 5.2.8.2
12.20 - 5.2.8.7

68P02901W23-T 6-101
Jan 2010
bsp_overload_protection Chapter 6: CM database parameters

bsp_overload_protection

Description

The BSS element bsp_overload_protection specifies whether the BSP CPU overload protection
is enabled. This parameter may be changed inside and outside SYSGEN mode.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bsp_overload_protection <value> <location>

Display command string

disp_element bsp_overload_protection <location>

Values

Value type Boolean

Valid range 0 Disabled
1 Enabled
Default value 0

6-102 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bss_egsm_alm_allowed

bss_egsm_alm_allowed

Description

The bss_egsm_alm_allowed parameter enables and disables Advanced Load Management for
the EGSM feature on a per BSS basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is valid only at a BSC.
The EGSM feature must be unrestricted.
This parameter is allowed only at password level 3.

Syntax

Change command string

chg_element bss_egsm_alm_allowed <value> 0

Display command string

disp_element bss_egsm_alm_allowed 0

Values

Value type Boolean

Valid range 0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-103
Jan 2010
bss_msc_overload_allowed Chapter 6: CM database parameters

bss_msc_overload_allowed

Description

The bss_msc_overload_allowed parameter determines whether an MSC overload is allowed.

When this parameter is enabled, the BSS bars one access class at a time if it receives an
OVERLOAD message.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bss_msc_overload_allowed <value>

Display command string

disp_element bss_msc_overload_allowed

Values

Value type Boolean

Valid range 0 Disabled
1 Enabled
Default value 0

6-104 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bssgp_block_retries

bssgp_block_retries

Description

The bssgp_block_retries parameter specifies the number of retries generated by the BSS for
cell block messages to the SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be used only if the GPRS feature is
unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change
is made.

Syntax

Change command string

chg_element bssgp_block_retries <value> <location>

Display command string

disp_element bssgp_block_retries <location>

Values

Value type Integer (retries)

Valid range 1 to 3
Default value 3

68P02901W23-T 6-105
Jan 2010
bssgp_cbl_bit Chapter 6: CM database parameters

bssgp_cbl_bit

Description

The bssgp_cbl_bit parameter specifies whether the CBL (Current Bucket Level) feature is
available at the PCU or not, that is, whether the CBL bit is set or not.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be used only if the GPRS feature is
unrestricted.
This parameter can be set in or out of SYSGEN mode.
Operator actions: None

NOTE
BSS software processes using this parameter are notified immediately the change
is made.

Syntax

Change command string

chg_element bssgp_cbl_bit <value> <location>

Display command string

disp_element bssgp_cbl_bit <location>

6-106 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or CBL procedures not supported (CBL bit not set).
1 CBL procedures supported (CBL bit set).
Default value 0

68P02901W23-T 6-107
Jan 2010
bssgp_dwnld_retry Chapter 6: CM database parameters

bssgp_dwnld_retry

Description

The bssgp_dwnld_retry parameter indicates the maximum number of retries for PFC Download.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The QoS feature must be unrestricted.
Operator actions None

Syntax

Change command string

chg_element bssgp_dwnld_retry <value> <location>

Display command string

disp_element bssgp_dwnld_retry <location>

Values

Value type Integer

Valid range 1 to 3
Default value 3

6-108 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bssgp_pfc_bit

bssgp_pfc_bit

Description

The bssgp_pfc_bit parameter specifies if Packet Flow Management (PFM) procedures are
enabled.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The QoS feature must be unrestricted.
The NACC feature must be enabled.
Operator actions None

NOTE
BSS software processes using this parameter are not notified when the change
is made.

Syntax

Change command string

chg_element bssgp_pfc_bit <value> <location>

Display command string

disp_element bssgp_pfc_bit <location>

68P02901W23-T 6-109
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0

6-110 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bssgp_racap_retries

bssgp_racap_retries

Description

The bssgp_racap_retries parameter specifies the number of retries generated by the BSS for
RA-Capability-Update messages to the SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.
Operator actions None

NOTE
BSS software processes using this parameter are not notified when the change
is made.

Syntax

Change command string

chg_element bssgp_racap_retries <value> <location>

Display command string

disp_element bssgp_racap_retries <location>

Values

Value type Integer (retries)

Valid range 1 to 3
Default value 3

68P02901W23-T 6-111
Jan 2010
bssgp_reset_retries Chapter 6: CM database parameters

bssgp_reset_retries

Description

The bssgp_reset_retries parameter specifies the number of retries generated by the BSS
for Reset messages to the SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.
Operator actions None

NOTE
BSS software processes using this parameter are not notified when the change
is made.

Syntax

Change command string

chg_element bssgp_reset_retries <value> <location>

Display command string

disp_element bssgp_reset_retries <location>

Values

Value type Integer (retries)

Valid range 1 to 3
Default value 3

6-112 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bssgp_unblock_retries

bssgp_unblock_retries

Description

The bssgp_unblock_retries parameter specifies the number of retries generated by the BSS
for cell Unblock messages to the SGSN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.
Operator actions None

NOTE
BSS software processes using this parameter are not notified when the change
is made.

Syntax

Change command string

chg_element bssgp_unblock_retries <value> <location>

Display command string

disp_element bssgp_unblock_retries <location>

Values

Value type Integer (retries)

Valid range 1 to 3
Default value 3

68P02901W23-T 6-113
Jan 2010
bts_p_con_ack Chapter 6: CM database parameters

bts_p_con_ack

Description

The bts_p_con_ack parameter specifies the maximum amount of time to wait for RF power
change acknowledgments to the BSS. This allows a repeat of the BTS power control message if
the BTS power has not been confirmed. This is effective only if the decision_alg_num equals 1.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies decision_alg_type = 1

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element bts_p_con_ack <value> <location> <cell_desc>

chg_cell_element bts_p_con_ack <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element bts_p_con_ack <location> <cell_desc>

Values

Value type Integer (1 Step = 2 multiframes)

Valid range 0 to 31
0 0 SACCH multiframes
1 2 SACCH multiframes
2 4 SACCH multiframes
... ...
31 62 SACCH multiframes
Default value 1 (equals 2 SACCH multiframes)

6-114 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter P_CON_ACK

GSM technical specification None

68P02901W23-T 6-115
Jan 2010
bts_p_con_interval Chapter 6: CM database parameters

bts_p_con_interval

Description

The bts_p_con_interval parameter specifies the minimum amount of time in multiples of two
SACCH multiframes between successive RF power change orders to the BSS.

The time period is greater than or equal to (nx - px + 1) hreqave / 2

Where:
x equals
1 (lower threshold of RXLEV),

2 (upper threshold of RXLEV),

3 (lower threshold of RXQUAL), or

4 (upper threshold of RXQUAL).

n equals the values assigned for decision_1_ny where y is a value from 1 to 4.

p equals the values assigned for decision_1_py where y is a value from 1 to 4.

hreqave is the number of measurements from the MS that are used in calculating one
average.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter does not work if the specified location is
the BSC (location = 0).
hreqave
bts_p_con_ack
decision_1_n1 through decision_1_n4
decision_1_p1 through decision_1_p4

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element bts_p_con_interval <value> <location> <cell_desc>

chg_cell_element bts_p_con_interval <value> <cell_desc_opt>

6-116 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command strings

disp_cell <cell_id> [full]

disp_element bts_p_con_interval <location> <cell_desc>

Values

Value type Integer (1 Step = 2 multiframes)

Valid range 0 to 31
0 0 SACCH multiframes
1 2 SACCH multiframes
2 4 SACCH multiframes
... ...
31 62 SACCH multiframes
Default value 2 (equals 4 SACCH multiframes)

References

GSM parameter P_CON_INTERVAL

GSM technical specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-117
Jan 2010
bts_power_control_allowed Chapter 6: CM database parameters

bts_power_control_allowed

Description

The bts_power_control_allowed parameter enables or disables the downlink RF power control

for the BSS. When enabled, the BSS uses up to 15 power control levels.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element bts_power_control_allowed <value> <location> <cell_desc>

chg_cell_element bts_power_control_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element bts_power_control_allowed <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 BTS power control disabled.
1 BTS power control enabled.
Default value 0

NOTE
The value 0 is the only valid value at M-Cellcity sites; both 0 and 1 values are
permitted at Horizonmicro2 and Horizoncompact2 sites.

6-118 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter EN_BS_PC

GSM technical specification 5.05 - 4.1.2

68P02901W23-T 6-119
Jan 2010
bts_txpwr_max_inner Chapter 6: CM database parameters

bts_txpwr_max_inner

Description

The bts_txpwr_max_inner parameter specifies the maximum transmit power BTS inner zone
for Dual Band cells.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter may be modified only when the Dual Band
Cells feature is unrestricted (inner_zone_alg set to 3).

Syntax

Change command strings

chg_element bts_txpwr_max_inner <value> <location> <cell_desc>

chg_cell_element bts_txpwr_max_inner <value> <cell_desc_opt>

Display command string

disp_element bts_txpwr_max_inner <location> <cell_desc>

Values

Value type Integer (1 step = 2 dBm) Same as those for max_tx_bts except
based on secondary_freq_type, not frequency_type.
Valid range -1 to 21 for PGSM, EGSM, and DCS1800.
0 to 6 for M-Cellmicro, M-Cellaccess, and M-Cellcompact sites
Default value 0

NOTE
Refer to Table 6-5, Table 6-24, Table 6-7, Table 6-8, Table 6-9, and Table 6-10 for
additional information about the values for this parameter.

Table 6-5 lists the values for CTU2 (SD-SCM, DD-DCM). The values represent the calibrated
output power at the top of the cabinet with one stage of combining.

6-120 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Table 6-5 CTU2 values

Valid Input CTU2 values

-1 44 dBm
0 42 dBm
1 40 dBm
2 38 dBm
3 36 dBm
4 34 dBm
5 32 dBm
6 30 dBm
7 28 dBm
8 26 dBm
9 24 dBm
10 22 dBm
11 20 dBm
12 18 dBm
13 16 dBm
14 14 dBm
15 12 dBm
16 10 dBm
17 8 dBm
18 6 dBm
19 4 dBm
20 2 dBm
21 0 dBm

NOTE
Value -1 is only valid for single density CTU2 DRI.

Table 6-24 lists the values for the (R)CTU4. The values represent the calibrated output power
at the top of the cabinet without any stage of external combining in single density or values
without external combining in double density mode.

NOTE
The (R)CTU4 values represent the calibrated output power after reducing the
combining loss of 0 dB, 3 dB, and 6 dB without any stage of combining. This is when
the maximum densities of two transmission paths are working at (0+1 or 1+1 mode),
or (0+2 or 1+2, or 2+2 mode), or (0+3 or 1+3, or 2+3, or 3+3 mode) accordingly.

68P02901W23-T 6-121
Jan 2010
Values Chapter 6: CM database parameters

If the (R)CTU4 is working at 1+0, 1+1 carrier mode, the max_tx_bts is the same,
for example, at the radio output: max_tx_bts 0->46dBm, 1->44dBm, 2->42dBm.
If the (R)CTU4 is working at 2+0, 2+1, 2+2 carrier mode, the (R)CTU4 has
extra 3dB attenuation. For example, at the radio output: max_tx_bts 0->43dBm,
1->41dBm, 2->39dBm.
If the (R)CTU4 is working at 3+0, 3+1, 3+2, 3+3 carrier mode, the (R)CTU4 has
extra 6dB attenuation. For example, at the radio output: max_tx_bts 0->40dBm,
1->38dBm, 2->36dBm.

Table 6-6 (R)CTU4 output values without any stage of combining

(R)CTU4 working at 0+1 (R)CTU4 working at 0+2 (R)CTU4 working at 0+3 or

Valid input or 1+1 mode or 1+2, or 2+2 mode 1+3, or 2+3, or 3+3 mode
1800 Mhz 900 Mhz 1800 Mhz 900 Mhz 1800 Mhz 900 Mhz
0 45 dBm 46 dBm 42 dBm 43 dBm 39 dBm 40 dBm
1 43 dBm 44 dBm 40 dBm 41 dBm 37 dBm 38 dBm
2 41 dBm 42 dBm 38 dBm 39 dBm 35 dBm 36 dBm
3 39 dBm 40 dBm 36 dBm 37 dBm 33 dBm 34 dBm
4 37 dBm 38 dBm 34 dBm 35 dBm 31 dBm 32 dBm
5 35 dBm 36 dBm 32 dBm 33 dBm 29 dBm 30 dBm
6 33 dBm 34 dBm 30 dBm 31 dBm 27 dBm 28 dBm
7 31 dBm 32 dBm 28 dBm 29 dBm 25 dBm 26 dBm
8 29 dBm 30 dBm 26 dBm 27 dBm 23 dBm 24 dBm
9 27 dBm 28 dBm 24 dBm 25 dBm 21 dBm 22 dBm
10 25 dBm 26 dBm 22 dBm 23 dBm 19 dBm 20 dBm
11 23 dBm 24 dBm 20 dBm 21 dBm 17 dBm 18 dBm
12 21 dBm 22 dBm 18 dBm 19 dBm 15 dBm 16 dBm
13 19 dBm 20 dBm 16 dBm 17 dBm 13 dBm 14 dBm
14 17 dBm 18 dBm 14 dBm 15 dBm 11 dBm 12 dBm
15 15 dBm 16 dBm 12 dBm 13 dBm 9 dBm 10 dBm
16 13 dBm 14 dBm 10 dBm 11 dBm 7 dBm 8 dBm
17 11 dBm 12 dBm 8 dBm 9 dBm 5 dBm 6 dBm
18 9 dBm 10 dBm 6 dBm 7 dBm 3 dBm 4 dBm
19 7 dBm 8 dBm 4 dBm 5 dBm 1 dBm 2 dBm
20 5 dBm 6 dBm 2 dBm 3 dBm -1 dBm 0 dBm
21 3 dBm 4 dBm 0 dBm 1 dBm -3 dBm -2 dBm

NOTE
Set the same value for the (R)CTU4 maximum densities of two transmission paths in
one cell to ensure the same output power for carriers in one cell.

6-122 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Table 6-7 identifies the transmit power capabilities of the different XCVR types in specific
frequency bands and cabinet types. The power specified is the cabinet antenna connector
maximum output power. All figures are 2 dB.

Table 6-7 also specifies the types of combing in used: none, external, internal, and both internal
and external. The combining types are defined as follows:
None: The output power of the XCVR is connected directly to the antenna. This is not
applicable for a DDM as it always uses a single stage of internal combining within the
XCVR itself.

External (to the XCVR): The output of the XCVR is connected through a single stage of
external hybrid combining to the antenna. For example, a two-carrier sector is required
from two SDX or two CTU2-SD.

Internal (to the XCVR): When a CTU2 is configured in Double Density mode the two
outputs from the two XCVR devices on the CTU2 are combined before leaving the XCVR.
Hence the power figure for internal combining represents two carriers at this transmit
power for a CTU2 in DD-DCM. Ensure that the internal combining is still present when the
CTU2 is used in DD-SCM.

Internal and external: External hybrid combining is used on a CTU2 in DDM. For example,
this allows two CTU2 in DD-DCM to be combined to create a four-carrier sector.

Table 6-7 Cabinet antenna connector maximum output power (Watts)

Horizonmacro Horizon II
XCVR Type Combining EGSM900 DCS1800 EGSM900 DCS1800
CTU None 40 32 N/A N/A
External 20 16 N/A N/A
CTU2 None 40 32 63 50
SD-SCM
External 20 16 28 22
CTU2 Internal 10 10 20 16
DD-DCM
Internal and 4.5 4.5 9 7
external

Table 6-8 lists the values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro, M-Cellcity,
M-Cellarena and M-Cellarenamacro sites.

Table 6-8 Values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro sites

PGSM and EGSM DCS1800 and PCS1900

Valid Input M-Cellarenamacrovalues
M-Cellmicro values M-Cellmicro values
0 31 dBm 30 dBm 40 dBm
1 29 dBm 28 dBm 38 dBm
2 27 dBm 26 dBm 36 dBm
3 25 dBm 24 dBm 34 dBm
4 23 dBm 22 dBm 32 dBm
5 21 dBm 20 dBm 30 dBm
6 19 dBm 18 dBm 28 dBm

68P02901W23-T 6-123
Jan 2010
Values Chapter 6: CM database parameters

Table 6-9 lists the values for DCS1800 and M-Cellaccess sites.

Table 6-9 Values for DCS1800 and M-Cellaccess, sites

Valid Input PGSM, EGSM and M-Cellaccess values DCS1800 M-Cellaccess values
0 12 dBm 17 dBm
1 10 dBm 15 dBm
2 8 dBm 13 dBm
3 6 dBm 11 dBm
4 4 dBm 9 dBm
5 2 dBm 7 dBm
6 0 dBm 5 dBm

The actual output power of a cabinet depends on the type of combining that is used. Table 6-10
lists sample output power, measured at the top of the cabinet, of some Motorola cabinets with
different combinations of RCUs and combiners.

Table 6-10 Sample output power

Type of combining Number of radios Output power (as calibrated)

ExCell 4
hybrid 2 20 W [Symbol_approximate]
43.01 dBm
cavity (1 cabinet) 4 25 W [Symbol_approximate]
43.98 dBm
BTS4, BTS5, BTS6
hybrid 2 20 W [Symbol_approximate]
43.01 dBm
cavity (1 cabinet) 5 25 W [Symbol_approximate]
43.98 dBm
cavity (2 neighboring 10 13 W [Symbol_approximate]
cabinets) 41.14 dBm
M-CellII or M-CellVI
hybrid 2 17.5 W [Symbol_approximate]
43.01 dBm
cavity (1 cabinet) 6 19 W [Symbol_approximate]
42.79 dBm
duplexer 4 13.5 W [Symbol_approximate]
41.30 dBm

6-124 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

NOTE

The listed power is valid for 600 kHz minimum channel distance, and for 800
kHz minimum channel distance with cavity combining.
The chg_element command does not allow a power level greater than 36 dBm
for any carrier for the cell that has an ARFCN on a PCS block edge frequency.

68P02901W23-T 6-125
Jan 2010
bts_type Chapter 6: CM database parameters

bts_type

Description

The bts_type parameter specifies the BTS configuration type. It is valid only for sites 1 to 10.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter may not be changed to 0 if DHPs exist at
the site, or if max_dris is set to 0.
This parameter must be set to 0 for M-CellII,
M-CellVI, M-Cellcity, Horizonmicro, Horizoncompact2,
Horizonmacro, Horizon II macro, and Horizon II mini
cabinets.

Syntax

Change command string

chg_element bts_type <value> <location>

Display command string

disp_element bts_type <location>

Values

Value type Boolean

Valid range 0 or 1
0 BTP
1 BTP and DHP
Default value None

6-126 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter None

GSM technical specification This is a Motorola parameter.

68P02901W23-T 6-127
Jan 2010
bvci Chapter 6: CM database parameters

bvci

Description

The bvci parameter specifies a BSSGP Virtual Connection Identifier (BVCI). There must be
one BVCI per cell and one signaling BVCI per BSS. BVCIs are automatically generated by the
BSS on creation of a cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter can be used only if the GPRS feature is
unrestricted.
A BVCI cannot be modified if gprs_enabled is set for the
cell.
Restrictions All BVCIs must be unique.
Only one BVCI can be mapped to a single cell, and one
BVCI must be allocated as the BSSGP signaling BVCI.

NOTE
BSS software processes using this parameter are not notified when the change is
made. That is, this parameter can be modified without a reset to a particular device
or function.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element bvci <value> <location> <cell_desc>

chg_cell_element bvci <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element bvci <location> <cell_desc>

6-128 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 2 to 65535
Default value None

68P02901W23-T 6-129
Jan 2010
cage_manage_enabled Chapter 6: CM database parameters

cage_manage_enabled

{34452}

Description

The cage_manage_enabled parameter enables or disables the cage management feature. This
parameter can be accessed and updated both in and out of sysgen mode.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element cage_manage_enabled <value> <location>

Display command string

disp_element cage_manage_enabled <location>

Values

Value type Integer

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 1

6-130 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference call_trace_options

call_trace_options

Description

The call_trace_options parameter enables or disables MSC initiated traces. It also specifies
the percentage of traces exclusively reserved for MSC initiated call traces.

The percentage of traces reserved exclusively for MSC initiated traces affects the number of call
trace instances that may be created. This percentage is specified using the call_trace_options
element. For example, if 50% of the traces are reserved for initiation from the MSC, a maximum
of eight instances may be created using the trace_call command.

If the call_trace_options element is set to 0, no traces are exclusively reserved for MSC
initiated traces. MSC initiated traces are still allowed. This permits a maximum of 16 instances
to be created using the trace_call command.

If the call_trace_options element is set to 255, the system ignores call trace requests from the
MSC. This permits a maximum of 16 instances to be created using the trace_call command.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element call_trace_options <value> <location>

Display command string

disp_element call_trace_options <location>

68P02901W23-T 6-131
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 100, and 255
0 to 100 The percentage of traces reserved for MSC initiated traces
on a per LCF basis.
255 MSC invoked call traces disabled.
Default value 0

6-132 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference called_pci

called_pci

Description

The called_pci parameter specifies whether point code is included in the called party address in
the SCCP messages.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is valid only at the BSC.

Syntax

Change command string

chg_element called_pci <value> 0

Display command string

disp_element called_pci 0

Values

Value type Boolean

Valid range 0 or 1
0 Point code is not included.
1 Point code is included.
Default value None

References

GSM specification CCITT Q.713

This is a Motorola defined parameter.

68P02901W23-T 6-133
Jan 2010
calling_pci Chapter 6: CM database parameters

calling_pci

Description

The calling_pci parameter enables or disables point code inclusion for the calling party address
in the SCCP messages.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is valid only at the BSC.

Syntax

Change command string

chg_element calling_pci <value> 0

Display command string

disp_element calling_pci 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None

References

GSM specification CCITT Q.713

This is a Motorola defined parameter.

6-134 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference carrier_disable_time

carrier_disable_time

Description

The carrier_disable_time parameter specifies the time delay between putting individual
carriers into battery conservation mode after a main power failure is reported.

For example, when a main power failure is first reported the system waits for the period of time
specified by the carrier_disable_time parameter before placing the first carrier into battery
conservation mode. Then the system waits for the same period of time before placing the
next carrier into battery conservation mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element carrier_disable_time <value> <location>

Display command string

disp_element carrier_disable_time <location>

Values

Value type Integer (seconds)

Valid range 120 to 65535
Default value 120

68P02901W23-T 6-135
Jan 2010
carriers_ins_pwr_fail Chapter 6: CM database parameters

carriers_ins_pwr_fail

Description

The carriers_ins_pwr_fail parameter specifies the number of carriers left up in the maintenance
power state when emergency battery power starts (that is, during a main power failure).

When the value of 0 is selected, all of the carriers are taken out of service in turn on the expiry
of the specified carriers_ins_pwr_fail parameter (see carrier_disable_time on page 6-135).
Non BCCH carriers are taken out of service before the BCCH carrier.

NOTE
The BCCH carrier continues to transmit after the battery conservation feature has
taken the carrier out of service.

Although the BCCH carrier is disabled, it continues to transmit since it is the carrier resources
that are disabled and not the physical carriers. This enables quick recovery of all carriers
when the main power is restored.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element carriers_ins_pwr_fail <value> <location>

Display command string

disp_element carriers_ins_pwr_fail <location>

6-136 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 30
0 All carriers are taken out of service.
Default value 30

68P02901W23-T 6-137
Jan 2010
cbc_fast_select Chapter 6: CM database parameters

cbc_fast_select

Description

The cbc_fast_select parameter enables and disables the fast connect function for the BSC.
The fast connect function supports X.25 networks that do not support user data in connect
and disconnect requests.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is valid only for the BSC.

Syntax

Change command strings

chg_element cbc_fast_select <value> 0

NOTE
A site reset is required when the value of cbc_fast_select is changed. Resetting the
site generates several alarms. However, the system blocks these alarms.

Display command strings

disp_element cbc_fast_select 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-138 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM specification 03.4103.49

This is a Motorola defined parameter.

68P02901W23-T 6-139
Jan 2010
cbc_intface_vers Chapter 6: CM database parameters

cbc_intface_vers

Description

The cbc_intface_vers parameter selects the interface for each BSC site.

The available interfaces are either the standard interface or the interface with the repetition
rate interpretation and CBCH loading fields.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is only valid for the BSC.

Syntax

Change command strings

chg_element cbc_intface_vers <value> 0

Display command strings

disp_element cbc_intface_vers 0

Values

Value type Boolean

Valid range 0 or 1
0 Standard interface
1 Interface with the repetition rate interpretation and CBCH
loading fields.
Default value 0

6-140 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cbc_vbind_cntr

cbc_vbind_cntr

Description

The cbc_vbind_cntr parameter sets the number of successful VBINDs sent by the BSS to the
CBC before a negotiate must take place within the next VBIND sent.

This parameter is effective on a per BSC basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is only valid for the BSC.

Syntax

Change command strings

chg_element cbc_vbind_cntr <value> 0

Display command strings

disp_element cbc_vbind_cntr 0

Values

Value type Integer (number of VBINDs)

Valid range 0 to 255
Default value 0

68P02901W23-T 6-141
Jan 2010
cbch_enabled Chapter 6: CM database parameters

cbch_enabled

Description

The cbch_enabled parameter enables the Cell Broadcast Channel (CBCH) option in a cell.

The CBCH is used with the Short Message Service (SMS) Cell Broadcast feature. An operator
defined message or set of background messages may be transmitted on the CBCH when the
cbch_enabled parameter is enabled.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Enabling of CBCH is not permitted if no AGCH is reserved
in a non-combined cell (bs_ag_blks_res = 0 and ccch_conf
is other than 1).

Syntax

Change command strings

chg_element cbch_enabled <value> <location> <cell_desc>

chg_cell_element cbch_enabled <value> <cell_desc_opt>

Display command string

disp_element cbch_enabled <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None

6-142 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cbs_outage_cntr

cbs_outage_cntr

Description

The cbs_outage_cntr parameter introduces a delay between an outage occurring and the CBS
halting transmission of CBC originated messages.

This parameter is effective on a per BTS site basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is only valid for a BTS site.

Syntax

Change command string

chg_element cbs_outage_cntr <value> <location>

Display command string

disp_element cbs_outage_cntr <location>

Values

Value type Integer (number of broadcast slots)

Valid range 0 to 255
Default value 0

68P02901W23-T 6-143
Jan 2010
ccch_conf Chapter 6: CM database parameters

ccch_conf

Description

The ccch_conf parameter specifies the organization of the Common Control Channels (CCCH)
on the BCCH. This field defines whether the CCCHs are combined with SDCCH and SACCH
onto the same basic physical channel. The value depends on the size of the cell and on the
number of access attempts expected on the cell.

NOTE
When an attempt is made to change ccch_conf, and the requested PDTCHs exceed
the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a
warning to indicate that there is not enough GDS or PMC resource available.

If the chg_cell_element command is used to change the value of this parameter and the change
allows hopping on a BCCH timeslot, the system rejects the command.

The system rejects this command if it is attempted for all sites.

Type B (operator actions required)

Supported by OMC-R GUI Yes

Cell description required Yes

Dependencies If ccch_conf = 0, 2, 4, or 6, values for the following
parameters must meet specific criteria:

number_sdcchs_preferred must be in multiples of 8

starting at 8 with no offset (that is 8, 16, 24...128)

The minimum number of sdcchs must be divisible by 8.

max_number_of_sdcchs must be divisible by 8.

bs_ag_blks_res = 0 to 7
If ccch_conf = 1, values for the following parameters must
meet specific criteria:

number_sdcchs_preferred must be in multiples of 8,

with an offset of 4 (that is 4, 12, 20...128)

The minimum number of sdcchs must be a multiple of

8 (+4).

6-144 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

max_number_of_sdcchs must be a multiple of 8 (+4).

bs_ag_blks_res = 0 to 2
Enabling of CBCH is not permitted (cbch-enabled = 1) if no
AGCH is reserved in a non-combined cell (bs-ag-blks-res = 0
and ccch-conf is other than 1).

This parameter can be used with the GPRS feature

unrestricted as follows:

Set to 0, seven PDCHs are supported for a BCCH carrier.

Set to 1, seven PDCHs are supported for a BCCH carrier.

Set to 2, six PDCHs are supported for a BCCH carrier.

Set to 4, five PDCHs are supported for a BCCH carrier.

Set to 6, four PDCHs are supported for a BCCH carrier.

The GPRS timeslots on the GPRS carrier must have the same
FHI.
GPRS channels must have the same training sequence codes.
If GPRS is unrestricted for a cell, attempts to modify
ccch_conf are rejected if the required timeslots are
configured as GPRS timeslots.
Because the PBCCH/PCCCH timeslots are configured on the
BCCH carrier, any attempt to change ccch_conf, with the
PBCCH/PCCCH optional feature unrestricted, results in a
warning to the operator when pccch_enabled is set to 1.
Operator actions Respond to the prompts presented after entering the
chg_cell_element command.

Syntax

Add/Change command string

The system rejects this command if it is attempted when location = all.

chg_cell_element ccch_conf <value> <cell_desc_opt>

NOTE
A site reset is required when the value of ccch_conf is changed. Resetting the site
generates several alarms. However, the system blocks these alarms.

Display command strings

disp_element ccch_conf <location> <cell_desc>

68P02901W23-T 6-145
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (CCH timeslots used; combined or non-combined)

Valid range 0, 1, 2, 4, and 6
0 0 Non-combined
1 0 Combined
2 0, 2 Non-combined
4 0, 2, 4 Non-combined
6 0, 2, 4, 6 Non-combined

Default value 0 (0 CCH timeslots used; non-combined)

References

GSM parameters CCCH_CONF, CCCH_SDCCH_COMB

GSM specifications
5.02 - 3.3.2: organization of common control channels
5.02 - 6.4: allowable channel configurations
4.03 - 5.1 and 6.2: organization of common control channels
5.02 - 6.5.1: BS_CC_CHANS, BS_CCCH_SDCCH_COMB
5.02 - 7: table 5
4.08 - 6.4: BS_CCCH_SDCCH_COMB

6-146 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ccch_load_period

ccch_load_period

Description

The ccch_load_period parameter specifies the number of TDMA multiframes between

successive calculations of the RACH load during overload conditions.

NOTE
Other parameters can affect flow control. Refer to rach_load_period,
rach_overload_threshold, ssm_normal_overload_threshold, ssm_critical_over-
load_threshold or tch_flow_control.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter must be greater than or equal to the
rach_load_period.

Syntax

Change command string

chg_element ccch_load_period <value> <location> <cell_desc>

chg_cell_element ccch_load_period <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ccch_load_period <location> <cell_desc>

68P02901W23-T 6-147
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (1 Step = 1 TDMA multiframe)

Valid range 1 to 1020
Default value 40

References

GSM parameter CCCH_LOAD_IND_PERIOD

GSM specification 5.08.1.1 - 5.2.3

6-148 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cell_bar_access_class

cell_bar_access_class

Description

The cell_bar_access_class parameter specifies access classes that are barred (or not barred)
access to the PLMN. A channel request is initiated only when the access class of a mobile is
not barred. The list of authorized access classes is broadcast on the BCCH by way of SYSTEM
INFORMATION messages. Also broadcast are the classes that have access to emergency calls.

There are 16 cell access classes, divided into four groups, as illustrated in the following diagram.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Z Y X W

0 = unbarred

1 = barred

The value of Z (0 - Fh) controls access classes 15 through 12.

The value of Y (0 - Fh) controls access classes 11 though 8.

The value of X (0 - Fh) controls access classes 7 though 4.

The value of W (0 - Fh) controls access classes 3 through 0.

The hexadecimal value for cell_bar_access_class can be determined from the following
diagram.

For example, if access classes 2, 3, 7 and 9 were to be barred, the following are true:

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 0 0 0 0 0 1 0 1 0 0 0 1 1 0 0
Z Y X W

Z = 0000 (0h)

Y = 0010 (2h)

X = 1000 (8h)

W = 1100 (Ch)

To bar access classes 2, 3 7 and 9, the set cell_bar_access_class=028Ch

Access Class 10 (emergency access) cannot be barred. Setting bit 10 in this field does not bar
the emergency access class. See also the emergency_class_switch parameter.

Table 6-11 lists the values for barring classes.

68P02901W23-T 6-149
Jan 2010
Description Chapter 6: CM database parameters

Table 6-11 Values for barring classes

Hexadecimal
Z Y X W
value
0 No barring No barring No barring No barring
1 bar class 12 bar class 8 bar class 4 bar class 0
2 bar class 13 bar class 9 bar class 5 bar class 1
3 bar classes 12 bar classes 8 bar classes 4 bar classes 0
and 13 and 9 and 5 and 1
4 bar class 14 bar class 10 bar class 6 bar class 2
5 bar classes 12 bar classes 8 bar classes 4 bar classes 0
and 14 and 10 and 6 and 2
6 bar classes 13 bar classes 9 bar classes 5 bar classes 1
and 14 and 10 and 6 and 2
7 bar classes 12, bar classes 8, bar classes 4, bar classes 0,
13 and 14 9 and 10 5 and 6 1 and 2
8 bar class 15 bar class 11 bar class 7 bar class 3
9 bar classes 12 bar classes 8 bar classes 4 bar classes 0
and 15 and 11 and 7 and 3
a bar classes 13 bar classes 9 bar classes 5 bar classes 1
and 15 and 11 and 7 and 3
b bar classes 12, bar classes 8, bar classes 4, bar classes 0,
13 and 15 9 and 11 5 and 7 1 and 3
c bar classes 14 bar classes 10 bar classes 6 bar classes 2
and 15 and 11 and 7 and 3
d bar classes 12, bar classes 8, bar classes 4, bar classes 0,
14 and 15 10 and 11 6 and 7 2 and 3
e bar classes 13, bar classes 9, bar classes 5, bar classes 1,2
14 and 15 10 and 11 6 and 7 and 3
f bar classes 12, bar classes 8, 9 bar classes 4, 5 bar classes 0,
13, 14 and 15 10 and 11 6, and 7 1, 2 and 3

NOTE
When entering a hexadecimal value, the suffix h is required.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies cell_bar_access_switch

6-150 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element cell_bar_access_class <value> <location> <cell_desc>

chg_cell_element cell_bar_access_class <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element cell_bar_access_class <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 65535
Default value 0

References

GSM parameter AC_CN

GSM specification 4.08 - 3.3.1.
4.08 - 3.3.1.1

68P02901W23-T 6-151
Jan 2010
cell_bar_access_switch Chapter 6: CM database parameters

cell_bar_access_switch

Description

The cell_bar_access_switch parameter specifies whether subscribers are barred access to

a cell in idle mode.

Emergency calls (user class 10) are not, and cannot be, barred.

An MS decodes the BCCH data to determine if it is allowed access to the system. BCCH data
includes information which indicates that the cell transmitting the data is part of the selected
PLMN (unbarred) or not (barred).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element cell_bar_access_switch <value> <location> <cell_desc>

chg_cell_element cell_bar_access_switch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element cell_bar_access_switch <location> <cell_desc>

6-152 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Cell is not barred.
1 Cell is barred.
Default value 0

References

GSM parameter CELL_BAR_ACCESS

GSM specifications
4.08 - 10.5.2.17, figure. 10.36, table 10.30
5.08 - 6.2
5.08 - 6.4: C1 equation
12.20 - 5.2.8.7: - cell description - cell bar access
03.22 - 3.5.1

68P02901W23-T 6-153
Jan 2010
cell_bar_qualify Chapter 6: CM database parameters

cell_bar_qualify

Description

The network uses the cell_bar_qualify parameter to control MS cell selection.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter cannot be changed if the
cell_reselect_param_ind parameter does not
equal 1.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element cell_bar_qualify <value> <location> <cell_desc>

chg_cell_element cell_bar_qualify <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element cell_bar_qualify <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Normal priority cell
1 Low priority cell
Default value 0

6-154 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM specification 3.22

4.08 Table 10.32 in section 10.5.2.35
5.08 Table 1a in section 9.
This is a Motorola defined parameter.

68P02901W23-T 6-155
Jan 2010
cell_barred_delay Chapter 6: CM database parameters

cell_barred_delay

Description

The cell_barred_delay parameter specifies the period the BSS delays sending
SystemInformationUpdate message for SI 1, 2, 2bis to the MS during global reset procedure.
This parameter can be updated both in and out of sysgen mode.

Device/Function BSS
Type A (no operator actions)
Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element cell_barred_delay <new_value> 0

Display command strings

disp_element cell_barred_delay <location>

Values

Value type Integer (seconds)

Valid range 0 to 180
Default value 0

6-156 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cell_reselect_hysteresis

cell_reselect_hysteresis

Description

The cell_reselect_hysteresis parameter specifies the hysteresis level for cell reselection into
a different location area. The new cell is selected only if the path loss criterion parameter
(C1) on the new cell exceeds C1 on the old cell by a minimum of value assigned to the
cell_reselect_hysteresis parameter.

Differences in received signal levels from 0 dB to 14 dB (in 2 dB increments) are used for
cell reselection.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies C1 (path loss criterion)

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element cell_reselect_hysteresis <value> <location> <cell_desc>

chg_cell_element cell_reselect_hysteresis <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element cell_reselect_hysteresis <location> <cell_desc>

68P02901W23-T 6-157
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 7
Represents the signal level differences as shown below:
0 0 dB
1 2 dB
2 4 dB
3 6 dB
4 8 dB
5 10 dB
6 12 dB
7 14 dB
Default value None

References

GSM parameter CE_RE_HYS

GSM specifications 5.08 - 6.6.2
4.08 - 10.5.2.4, figure 10.23, and table 10.17
12.20 - 5.2.8.12 - radio link ctl dl - cell reselect hysteresis

6-158 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cell_reselect_offset

cell_reselect_offset

Description

The cell_reselect_offset parameter specifies a C2 offset value for the MS. C2 is the reselection
priority assigned to a cell which can be broadcast on the BCCH of each cell. When more than
one cell is available for reselection, the MS reselects the cell with the highest C2 value.

Lower C2 values discourage fast moving MSs from selecting a specific cell. Higher values
encourage MSs to reselect a specific cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter may not be changed if the
cell_reselect_parm_ind parameter is not equal to
1.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element cell_reselect_offset <value> <location> <cell_desc>

chg_cell_element cell_reselect_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element cell_reselect_offset <location> <cell_desc>

68P02901W23-T 6-159
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (1 Step = 2 dB)

Valid range 0 to 63
0 0 dB
1 2 dB
2 4 dB
.
.
.
63 126 dB
Default value 0

References

GSM parameter CELL_RESELECT_OFFSET

GSM specifications 3.22
4.08 table 10.32a in section 10.5.2.35
5.08

6-160 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cell_reselect_param_ind

cell_reselect_param_ind

Description

The cell_reselect_parameter_ind parameter specifies whether the C2 parameters

(cell_bar_qualify, cell_reselect_offset, temporary_offset, and penalty_time) are broadcast
to the MS by the network in the system information messages.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element cell_reselect_param_ind <value> <location> <cell_desc>

chg_cell_element cell_reselect_param_ind <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element cell_reselect_param_ind <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Do not broadcast C2 cell reselection parameters on the
BCCH of the cell.
1 Broadcast C2 cell reselection parameters on the BCCH
of the cell.
Default value 0

68P02901W23-T 6-161
Jan 2010
References Chapter 6: CM database parameters

References

GSM parameter CELL_RESELECT_PARAM_IND

GSM specifications 4.08 table 10.32a in section 10.5.2.355.08
This parameter is not used at the present time. C2
parameters are not used at the present time since they are
dependent on this parameter being enabled.

6-162 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference channel_reconfiguration_switch

channel_reconfiguration_switch

Description

The channel_reconfiguration_switch parameter enables and disables dynamic channel

reconfiguration (reassignment) of traffic channels to Standalone Dedicated Control Channels
(SDCCHs).

The Cell Resource Manager (CRM) may attempt to reconfigure an idle TCH into an SDCCH
if a high proportion of SDCCHs is in use and additional SDCCH requests are received.
The reconfiguration process continues until the number of idle SDCCHs reaches the
sdcch_need_high_water_mark value.

The reconfiguration process stops when the number of idle TCHs goes below the
tch_full_need_low_water_mark value or when the total number of SDCCHs configured
reaches the max_number_of_sdcchs value.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element channel_reconfiguration_switch <value> <location> <cell_desc>

chg_cell_element channel_reconfiguration_switch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element channel_reconfiguration_switch <location> <cell_desc>

68P02901W23-T 6-163
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification Figure 3 5.02 - 6.4: permitted channel combinations of

logical channels
This is a Motorola defined parameter.

6-164 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cic_error_clr_thresh

cic_error_clr_thresh

Description

The cic_error_clr_thresh parameter specifies the error count threshold (equal to or less than)
for an alarm to be cleared for a Circuit Identity Code (CIC).

Type A (no operator actions)

Supported by OMC-R GUI Yes

Cell description required No
Dependencies Two successful calls are required on a resource before
an alarm can be cleared within this threshold. (One
successful call may be too short for the Channel Coder Unit
(CCU) to send an error indication, thus clearing the alarm
prematurely.)
This parameter can be set only at a BSC.
If the threshold is increased during operation, any existing
counts between the new and the old threshold does not
clear an alarm until another successful call is made on the
CIC.

Syntax

Change command strings

chg_element cic_error_clr_thresh <value> 0

Display command strings

disp_element cic_error_clr_thresh 0

Values

Value type Integer

Valid range 0 to 253
Default value 0

68P02901W23-T 6-165
Jan 2010
cic_error_gen_thresh Chapter 6: CM database parameters

cic_error_gen_thresh

Description

The cic_error_gen_thresh parameter specifies the error count threshold (equal to or greater
than) for an alarm to be generated for a Circuit Identity Code (CIC).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be set only at a BSC.
If the threshold is changed during operation, no immediate
alarm occurs. The new threshold takes effect only when
the CIC error count changes.

Syntax

Change command strings

chg_element cic_error_gen_thresh <value> 0

Display command strings

disp_element cic_error_gen_thresh 0

Values

Value type Integer

Valid range 2 to 255
Default value 6

6-166 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cic_error_inc

cic_error_inc

Description

The cic_error_inc parameter specifies the error count increment when the Circuit Error Rate
Monitor (CERM) feature is in use for Circuit Identity Codes (CICs) on a per BSC basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be set only at a BSC.

Syntax

Change command strings

chg_element cic_error_inc <value> 0

Display command string

disp_element cic_error_inc 0

Values

Value type Integer

Valid range 0 CIC alarms not raised.
1 to 255 CIC alarms raised.
Default value 1

68P02901W23-T 6-167
Jan 2010
cic_validation Chapter 6: CM database parameters

cic_validation

Description

The cic_validation parameter enables or disables the Circuit Identity Code (CIC) validation
for an RXCDR.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The cic_validation parameter should be enabled or
disabled by one of the following methods:
(1) In Sysgen mode (by updating the database through
DataGen or by using the sysgen_on command at the MMI).
(2) After executing the modify_value command, cycle
(reset) the BSC to re-initialize all BSC mapping.

Syntax

Change command string

modify_value <location> cic_validation <value> AXCDR <axcdr_id>

Display command string

disp_equipment <location> AXCDR <axcdr_id>

Values

Value type Boolean

Valid range No or Yes
No Disabled
Yes Enabled
Default value None

6-168 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ciph_mode_rej_allowed

ciph_mode_rej_allowed

Description

The ciph_mode_rej_allowed parameter enables or disables the Cipher Mode Reject message to
be sent to the MSC. This message generates when the Cipher Mode Command message from
the MSC specifies ciphering that the BSS or MS cannot perform.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.

Syntax

Change command string

chg_element ciph_mode_rej_allowed <value> 0

Display command string

disp_element ciph_mode_rej_allowed 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification TS GSM 08.08

This is a Motorola defined parameter.

68P02901W23-T 6-169
Jan 2010
clk_src_fail_reset_period Chapter 6: CM database parameters

clk_src_fail_reset_period

Description

The clk_src_fail_reset_period parameter specifies the length of time for which the OOS count
is kept for the MMSs at a site. At the end of the reset period, all of the MMS OOS counts
are reset to zero.

The OOS counts are used in the selection process for an MMS as a reference clock for GCLK
synchronization. If several MMSs have the same value assigned to the mms_priority parameter,
the MMS with the lowest OOS count is selected.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element clk_src_fail_reset_period <value> <location>

Display command string

disp_element clk_src_fail_reset_period <location>

Values

Value type Integer (hours)

Valid range 1 to 255
Default value 24

6-170 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference coincident_cell

coincident_cell

Description

The coincident_cell parameter specifies the cell that is coincident to the cell specified in the
chg_cell_element coincident_mb prompt or the disp_cell command.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter may only be changed if the Coincident
MultiBand Handover option is unrestricted.
If coincident_mb is set to 1 or 2, both cells must be
SACCH neighbors of each other.
If coincident_mb is set to 2, both cells must be at the
same site, the cells must be neighbors of each other, and
the bsic settings must be the same.
A cell cannot be coincident to itself.

NOTE
If all is entered for the del_neighbor command for a BTS at which the Coincident
MultiBand Handover option is enabled and contains any coincident cells, the
command is rejected.

Syntax

Change command string

chg_cell_element coincident_cell <value> <cell_desc_opt>

The system prompts for the cell number for the coincident_cell.

Display command strings

disp_cell <cell_id> [full]

disp_element coincident_cell <location> <cell_desc>

68P02901W23-T 6-171
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range The GSM cell ID number.
Default value None

6-172 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference coincident_offset

coincident_offset

Description

The coincident_offset parameter enables and disables the configuration of an additional

offset to the ho_margin value between a cell and its coincident cell. The system uses the
coincident_offset value when a handover from a MultiBand MS is based on the receive level
for the serving cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter may only be changed if the Coincident
MultiBand Handover option is enabled.

Syntax

Change command strings

chg_element coincident_offset <value> <location> <cell_desc>

chg_cell_element coincident_offset <value> <cell_desc_opt>

The system prompts for:

The cell number for the coincident cell.

The low signal threshold. See Prompt field values in the description of chg_cell_element
on page 3-84.

Display command string

disp_element coincident_offset <location> <cell_desc>

Values

Value type Integer (dB)

Valid range -63 to 63
Default value 0

68P02901W23-T 6-173
Jan 2010
coincident_mb Chapter 6: CM database parameters

coincident_mb

Description

The coincident_mb parameter specifies the ability of a BTS to execute the Coincident
MultiBand Handover option.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter may only be changed if the Coincident
MultiBand Handover option is enabled.
If coincident_mb is set to 1 or 2, both cells must be
SACCH neighbors of each other.
If coincident_mb is set to 2, both cells must be at the
same site, the cells must be neighbors of each other, and
the bsic settings must be the same.
If a coincident cell has not been selected, the value of
coincident_mb must equal 0.
A cell cannot be coincident to itself.
This parameter must be disabled when inner_zone_alg is
set to indicate Dual Band Cells.
The copy_cell command sets the coincident cell to an
invalid value, and the coincident_mb to 0 at the new cell.
The delete_cell command is rejected if the cell specified
for deletion is a coincident cell of any other cell at a site that
has the Coincident Multiband Handover option enabled.
If all is entered for the del_neighbor command for a BTS
at which the Coincident MultiBand Handover option is
enabled, and contains any coincident cells, the command is
rejected.

Syntax

Change command string

chg_cell_element coincident_mb <value> <cell_desc_opt>

The system prompts for the cell number for the coincident_cell.

6-174 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command strings

disp_cell <cell_id> [full]

disp_element coincident_mb <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 3
0 Coincident Multiband is disabled at the 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 when
coincident_mb=2, but for inter BSC handovers the call is
targeted at the primary cell.
Default value 0

68P02901W23-T 6-175
Jan 2010
confusion_msg_allowed Chapter 6: CM database parameters

confusion_msg_allowed

Description

The confusion_msg_allowed parameter enables and disables the BSS to send Confusion
messages over the A-interface when an erroneous message is received from the MSC. If this
parameter is not enabled, the system generates an alarm instead of sending a message to
the MSC.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter does not apply to RXCDR sites.
This parameter only applies to the BSC.

Syntax

Change command string

chg_element confusion_msg_allowed <value> 0

Display command string

disp_element confusion_msg_allowed 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification TS GSM 8.08

This is a Motorola defined parameter.

6-176 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference congest_at_source

congest_at_source

Description

The congest_at_source parameter specifies how a specified source cell treats target cells when
trying to find candidates for an imperative handover.

The specified source cell may be enabled to: (a) treat all target cells equally or (b) immediately
retry target cells which were in the process of congestion relief.

NOTE
Target cells that are in the process of Congestion Relief may become available for
handovers more quickly than those that are not.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell number required Yes
Dependencies The parameter can be set only if the Congestion Relief
feature is unrestricted.

Syntax

Change command strings

chg_element congest_at_source <value> <location> <cell_desc>

chg_cell_element congest_at_source <value> <cell_desc_opt>

Display command string

disp_element congest_at_source <location> <cell_desc>

68P02901W23-T 6-177
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 The source cell treats all target cells equally as candidates
for imperative handovers.
1 The source cell immediately retries target cells which were
in the process of congestion relief.
Default value 0

NOTE
Refer to the congest_at_target parameter to see when a target cell performs
congestion relief procedures.

6-178 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference congest_at_target

congest_at_target

Description

The congest_at_target parameter specifies how a specified cell behaves if it rejects a handover
request.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell number required Yes
Dependencies The parameter can be set only if the Congestion Relief
feature is unrestricted.

Syntax

Change command strings

chg_element congest_at_target <value> <location> <cell_desc>

chg_cell_element congest_at_target <value> <cell_desc_opt>

Display command string

disp_element congest_at_target <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 The system takes no action if the Cell rejects a handover
request.
1 The system invokes Congestion Relief procedures if this
Cell rejects a handover request.
Default value 0

68P02901W23-T 6-179
Jan 2010
congest_ho_margin Chapter 6: CM database parameters

congest_ho_margin

Description

The congest_ho_margin parameter specifies the margin of a congestion handover. To make it

easier to hand over to this neighbor in the case of congestion in the current cell, this parameter
value should be less that the value of the handover margin.

To disable congestion handovers to this neighbor, set the congestion handover margin to the
maximum value.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can only be modified if:

either the Directed Retry or Alternate Congestion

Relief options are available,
and

the neighbor is placed on the SACCH list.

Syntax

Change command string

modify_neighbor <source_cell_id> <neighbor_cell_id> congest_ho_margin <value>

Display command string

disp_neighbor <src_cell_id> [<neighbor_cell_id>|all]

disp_neighbor <source cell_name> [<internal neighbor cell_name>]

disp_neighbor <src_cell_id> ["test" <test neighbor_cell_id>]]

Values

Value type Integer (each step equals 1 dB)

Valid range -63 to 63
Default value None

6-180 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference congest_pd_expand_enabled

congest_pd_expand_enabled

{34452}

Description

The congest_pd_expand_enabled parameter specifies whether the functionality of use idle

TCH for burst packet traffic is enabled. This parameter can be accessed and updated both
in and out of sysgen mode without warning.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the EGPRS
feature is enabled.

Syntax

Change command string

chg_element congest_pd_expand_enabled <value> <location>

Display command string

disp_element congest_pd_expand_enabled <location>

Values

Value type Integer

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-181
Jan 2010
cp_option_reset_ckt Chapter 6: CM database parameters

cp_option_reset_ckt

Description

The cp_option_reset_ckt parameter enables and disables the reset circuit feature.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element cp_option_reset_ckt <value> <location>

Display command string

disp_element cp_option_reset_ckt <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-182 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cp_option_rr_status

cp_option_rr_status

Description

The cp_option_rr_status parameter enables and disables the radio resource status.

If radio resource status is enabled, the BSS can generate the 4.08 radio resource status
message to the MS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element cp_option_rr_status <value> <location>

Display command string

disp_element cp_option_rr_status <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-183
Jan 2010
cr_calling Chapter 6: CM database parameters

cr_calling

Description

The cr_calling parameter enables or disables the calling party address being included in the
SCCP message Connection Request.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.

Syntax

Change command string

chg_element cr_calling <value> 0

Display command string

disp_element cr_calling 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-184 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cstats_bss_enabled

cstats_bss_enabled

{34452}

Description

The cstats_bss_enabled parameter enables or disables the function of critical statistics

uploading at 5 minute intervals. This parameter can be accessed and updated both in and
out of sysgen mode.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element cstats_bss_enabled <value> <location>

Display command string

disp_element cstats_bss_enabled <location>

Values

Value type Integer

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-185
Jan 2010
cstats_cell_enabled Chapter 6: CM database parameters

cstats_cell_enabled

{34452}

Description

The cstats_cell_enabled parameter is used to indicate whether the functionality statistics

uploading at five-minute intervals for the cell is enabled. This parameter can be accessed
and updated both in and out of sysgen mode.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command string

chg_cell_element cstats_cell_enabled <value> <cell_desc>

chg_element cstats_cell_enabled <value> <location> <cell_desc>

Display command string

disp_element cstats_cell_enabled <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0

6-186 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ct_flow_control_hi_level

ct_flow_control_hi_level

Description

The ct_flow_control_hi_level parameter specifies the percentage of call trace OML buffer space
that may be used before flow control is enabled. When this limit is reached, the BSS parameter
ct_flow_control_bss_enabled is set to 1. (This level is not used to disable flow control.)

Setting this parameter to 100 disables flow control.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies ct_flow_control_hi_level must be greater
than ct_flow_control_lo_level plus 20.

Syntax

Change command string

chg_element ct_flow_control_hi_level <value> <location>

Display command string

disp_element ct_flow_control_hi_level <location>

Values

Value type Integer

Valid range 20 to 100
Default value 60

68P02901W23-T 6-187
Jan 2010
ct_flow_control_lo_level Chapter 6: CM database parameters

ct_flow_control_lo_level

Description

The ct_flow_control_lo_level parameter specifies the percentage of call trace OML buffer space
that may be used before flow control is enabled. When this limit is reached, the BSS parameter
ct_flow_control_bss_enabled is set to 0. (This level is not used to disable flow control.)

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies ct_flow_control_lo_level must be less than
ct_flow_control_hi_level minus 20.

Syntax

Change command string

chg_element ct_flow_control_lo_level <value> <location>

Display command string

disp_element ct_flow_control_lo_level <location>

Values

Value type Integer

Valid range 0 to 80
Default value 20

6-188 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ct_flow_control_msc_trace

ct_flow_control_msc_trace

Description

The ct_flow_control_msc_trace parameter specifies whether MSC traces are allowed when
flow control is enabled.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element ct_flow_control_msc_trace <value> <location>

Display command string

disp_element ct_flow_control_msc_trace <location>

Values

Value type Boolean

Valid range 0 or 1
0 MSC traces are allowed while flow is restricted.
1 MSC traces are not allowed while flow is restricted.
Default value 0

68P02901W23-T 6-189
Jan 2010
ctu2d_asym_opt Chapter 6: CM database parameters

ctu2d_asym_opt

Description

The ctu2d_asym_Opt parameter indicates whether the CTU2-D asymmetric feature

functionality is restricted or unrestricted in the BSS software.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The CTU2-D asymmetric feature requires EGPRS and
Capacity to be unrestricted.

Syntax

Display command strings

disp_options all

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value N/A

6-190 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ctu2d_cap_opt

ctu2d_cap_opt

Description

The ctu2d_cap_Opt parameter indicates whether the CTU2-D capacity feature functionality is
restricted or unrestricted in the BSS software.

Type A (No operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The CTU2-D capacity feature requires the EGPRS
feature to be unrestricted.

Syntax

Display command string

disp_options all

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value N/A

68P02901W23-T 6-191
Jan 2010
CTU8Opt Chapter 6: CM database parameters

CTU8Opt

{35200G}

Description

The CTU8Opt parameter indicates whether the (R)CTU4 Radio can support the operation of up
to 4 carriers per Tx lineup port in one (R)CTU4 Radio in the BSS software.

NOTE
The (R)CTU4 Radio configured to support 3 or 4 carriers per Tx lineup port is
designed to meet the 3GPP R8 Multi-Carrier BTS Class 2 performance specification.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies CTU8Opt can be unrestricted only if the MCBTSR8Opt
parameter is unrestricted. If CTU8Opt is unrestricted and
MCBTSR8Opt is restricted, then the options object can
not be created. The tool used to create the options object
for the BSS will be modified to handle this dependency.
If the CTU8Opt is unrestricted, the (R)CTU4 radio can
additionally operate in 4 (0 per Tx port 1 + 4 per Tx port
2), 5 (1 per Tx port 1 + 4 per Tx port 2), 6 (2 per Tx port 1
+ 4 per Tx port 2), 7 (3 per Tx port 1 + 4 per Tx port 2) and
8 (4 per Tx port 1 + 4 per Tx port 2) carriers per Radio.

Syntax

Display command strings

disp_options

6-192 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Does not support (R)CTU4 in 4 carriers per Tx port.
1 Supports (R)CTU4 in 4 carriers per Tx port.
Default value N/A

68P02901W23-T 6-193
Jan 2010
c31_hyst Chapter 6: CM database parameters

c31_hyst

Description

The c31_hyst parameter is a flag specifying whether hysteresis is applied to C31.

Type A (No operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

NOTE
BSS software processes using this parameter are immediately notified when the
change is made.

Syntax

Change command string

chg_cell_element c31_hyst <value> <cell_desc_opt>

chg_cell_element <location> c31_hyst <value> all

chg_element c31_hyst <value> <location> <cell_desc>

Display command string

disp_cell <cell_id> full

disp_element c31_hyst <location> <cell-desc>

disp_element c31_hyst <location> all

6-194 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Hysteresis not applied.
1 Hysteresis applied.
Default value 0

68P02901W23-T 6-195
Jan 2010
c32_qual Chapter 6: CM database parameters

c32_qual

Description

The c32_qual parameter is a flag specifying whether the exception rule is allowed with the
gprs_reselect_offset parameter at a cell.

Type A (No operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

NOTE
BSS software processes using this parameter are immediately notified when the
change is made.

Syntax

Change command string

chg_cell_element c32_qual <value> <cell_desc_opt>

chg_cell_element <location> c32_qual <value> all

chg_element c32_qual <value> <location> <cell_desc>

Display command string

disp_cell <cell_id> full

disp_element c32_qual <location> <cell-desc>

disp_element c32_qual <location> all

6-196 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Exception not allowed.
1 Exception allowed.
Default value 0

68P02901W23-T 6-197
Jan 2010
dat_weight Chapter 6: CM database parameters

dat_weight

{26638}

Description

The parameter dat_weight is an IP based NSVC parameter and it identifies the data weight
associated with the remote IP end point. NSVC is recycled when dat_weight is changed.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the Gb over IP
feature is unrestricted and the Gb mode is set to static IP
mode.

Syntax

Add command strings

add_nsvc <location> <NS_VCI> <GBL_ID> if gb_mode is in the static IP mode.

add_nsvc <location> <NS_VCI> <GBL_ID> <DLCI> if gb_mode is in the frame relay mode.

Display command strings

disp_nsvc <NS_VCI> <nsvci_value>

disp_nsvc <location> <GBL> <gbl_value>

Modify command strings

mod_nsvc <location> <NS_VCI>

Delete command strings

del_nsvc <location> <nsvci_value>

6-198 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 255
0 Minimum
255 Maximum
Default value N/A

68P02901W23-T 6-199
Jan 2010
data_qual_enabled Chapter 6: CM database parameters

data_qual_enabled

Description

The data_qual_enabled parameter enables or disables the use of specific rxqual thresholds for
data call handovers.

A data call is one that involves the transmission of computer data, such as a modem-to-modem
call. These types of calls are sensitive to bit errors. Therefore, specific rxqual thresholds may
be configured to trigger data call handovers.

If the data_qual_enabled parameter is enabled and a data call is in progress, the system uses
the rxqual data parameters set with the chg_cell_element command, as listed in Syntax,
instead of the normal rxqual values set with the add_cell command.

NOTE
If both the data_qual_enabled and the hop_qual_enabled parameters are ON, the
data_qual_enabled parameter takes precedence in conditions where both apply, that
is, data transmission in a hopping call.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc

Syntax

Change command strings

chg_cell_element data_qual_enabled <value> <cell_desc_opt>

If the value is 1 (enabled) the system prompts for the data threshold values as the following
parameters:
l_rxqual_dl_h on page 6-498.

l_rxqual_dl_p on page 6-510.

l_rxqual_ul_h on page 6-524.

l_rxqual_ul_p on page 6-536.

6-200 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command strings

disp_cell <cell_id> [full]

disp_element data_qual_enabled <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-201
Jan 2010
ddtr_ctrl_enabled Chapter 6: CM database parameters

ddtr_ctrl_enabled

Description

The ddtr_ctrl_enabled parameter is used to enable and disable the delayed downlink
Temporary Block Flow (TBF) release duration and extended uplink TBF duration, as a function
of cell availability.

The ddtr_ctrl_enabled parameter is configurable on a per BSS basis.

Type A
Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS and increased PRP capacity features must be
unrestricted.
Operator actions None

Syntax

Add/Change command strings

chg_element ddtr_ctrl_enabled <value> <location>

Display command strings

disp_element ddtr_ctrl_enabled <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0 (Disabled)

6-202 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference decision_1_ncell_rxlev_av_h_calc

decision_1_ncell_rxlev_av_h_calc

Description

The decision_1_ncell_rxlev_av_h_calc parameter specifies which bin is used in the

surround_cell parameter for the purposes of candidate ordering. Therefore, it also specifies
the hreqave value to use.

This parameter may not be changed to a bin which does not contain valid handover data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies surround_cell

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_ncell_rxlev_av_h_calc <value> <location> <cell_desc>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_ncell_rxlev_av_h_calc <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
Default value 0

68P02901W23-T 6-203
Jan 2010
decision_1_dl_rxlev_av_ih Chapter 6: CM database parameters

decision_1_dl_rxlev_av_ih

Description

The decision_1_dl_rxlev_av_ihparameter specifies the bin number containing the measurement

averaging algorithm data used to make handover decisions for downlink signal interference.

This parameter may not be changed to a bin which does not contain valid handover data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies rxlev_dl_ho

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_dl_rxlev_av_ih <value> <location> <cell_desc>

chg_cell_element decision_1_dl_rxlev_av_ih <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_dl_rxlev_av_ih <location> <cell_desc>

Values

Value type Boolean

Valid range 0 to 1
Default value 0

6-204 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference decision_1_dl_rxqual_av_h

decision_1_dl_rxqual_av_h

Description

The decision_1_dl_rxqual_av_h parameter specifies the bin number containing the

measurement averaging algorithm data used to generate handover decisions due to downlink
receive quality (rxqual).

This parameter may not be changed to a bin which does not contain valid handover data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies rxqual_dl_ho

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_dl_rxqual_av_h <value> <location> <cell_desc>

chg_cell_element decision_1_dl_rxqual_av_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_dl_rxqual_av_h <location> <cell_desc>

Values

Value type Boolean

Valid range 0 to 1
Default value 0

68P02901W23-T 6-205
Jan 2010
decision_1_dl_rxlev_av_p Chapter 6: CM database parameters

decision_1_dl_rxlev_av_p

Description

The decision_1_dl_rxlev_av_p parameter specifies the bin number containing the measurement
averaging algorithm data used to generate power control changes due to downlink signal
strength.

This parameter may not be changed to a bin which does not contain valid power control data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies rxlev_dl_pc

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_dl_rxlev_av_p <value> <location> <cell_desc>

chg_cell_element decision_1_dl_rxlev_av_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_dl_rxlev_av_p <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
Default value 0

6-206 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference decision_1_dl_rxqual_av_p

decision_1_dl_rxqual_av_p

Description

The decision_1_dl_rxqual_av_p parameter specifies the bin number containing the

measurement averaging algorithm data used to generate power control changes due to
downlink receive quality (rxqual).

This parameter may not be changed to a bin which does not contain valid power control data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies rxqual_dl_pc

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_dl_rxqual_av_p <value> <location> <cell_desc>

chg_cell_element decision_1_rxqual_av_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_dl_rxqual_av_p <location> <cell_desc>

Values

Value type Boolean

Valid range 0 to 1
Default value 0

68P02901W23-T 6-207
Jan 2010
decision_1_n1/decision_1_p1 Chapter 6: CM database parameters

decision_1_n1/decision_1_p1

Description

These parameters specify N1 and P1 in the decision algorithm used in the BSS.

N1 is the number of samples in the threshold comparison process used in decisions to increase
uplink and downlink power. P1 is the number of samples in the processed measurement
(process) relative to the (averaging) algorithm in place. If a least P1 averages out of N1 averages
are lower than RSS handover threshold l_rxlev_ul_p (uplink) or RSS handover threshold
l_rxlev_dl_p (downlink), the corresponding uplink or downlink power is increased.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies N1 must be greater than or equal to P1. N1 must
be less than or equal to the hreqt value set using
chg_act_alg_data command for rxlev_dl_pc and
rxlev_ul_pc.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_n1 <value> <location> <cell_desc>

chg_cell_element decision_1_n1 <value> <cell_desc_opt>

chg_cell_element decision_1_p1 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_n1 <location> <cell_desc>

disp_element decision_1_p1 <location> <cell_desc>

6-208 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 peg)

Valid range 1 to 31
Default value 1

References

GSM parameter N1, P1

GSM specification 5.08 - Appendix A - 3.2, and Table 1
12.20 - 5.2.8.26: Signal Strength Serving Cell

68P02901W23-T 6-209
Jan 2010
decision_1_n2/decision_1_p2 Chapter 6: CM database parameters

decision_1_n2/decision_1_p2

Description

These parameters specify N2 and P2 in the decision algorithm used in the BSS.

N2 is the number of samples in the threshold comparison process used in decisions to decrease
uplink and downlink power. P2 is the number of samples in the processed measurement
(process) relative to the (averaging) algorithm in place. If at least P2 averages out of N2
averages are greater than RSS handover threshold u_rxlev_ul_p (uplink) or RSS handover
threshold u_rxlev_dl_p (downlink), the corresponding uplink or downlink transmit power
(txpwr) is decreased.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies N2 must be greater than or equal to P2. N2 must
be less than or equal to the hreqt value set using
chg_act_alg_data command for rxlev_dl_pc and
rxlev_ul_pc.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_n2 <value> <location> <cell_desc>

chg_cell_element decision_1_n2 <value> <cell_desc_opt>

chg_cell_element decision_1_p2 <value> <cell_desc_opt>

chg_element decision_1_p2 <value> <location> <cell_desc>

chg_cell_element decision_1_p2 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_n2 <location> <cell_desc>

disp_element decision_1_p2 <location> <cell_desc>

6-210 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 peg)

Valid range 1 to 31
Default value 1

References

GSM parameter N2, P2

GSM specification 5.08 - Appendix A - 3.2, and Table 1
12.20 - 5.2.8.26: Signal Strength Serving Cell

68P02901W23-T 6-211
Jan 2010
decision_1_n3/decision_1_p3 Chapter 6: CM database parameters

decision_1_n3/decision_1_p3

Description

These parameters specify N3 and P3 in the decision algorithm used in the BSS.

N3 is the number of samples in the threshold comparison process used in decisions to increase
uplink and downlink power. P3 is the number of samples in the processed measurement
(process) relative to the (averaging) algorithm in place. If at least P3 averages out of N3
averages are greater (worse quality) than RSS handover threshold l_rxqual_ul_p (uplink)
or RSS handover threshold l_rxqual_dl_p (downlink), the corresponding uplink or downlink
transmit power (txpwr) is increased.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies N3 must be greater than or equal to P3. N3 must
be less than or equal to the hreqt value set using
chg_act_alg_data command for rxqual_dl_pc and
rxqual_ul_pc.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_n3 <value> <location> <cell_desc>

chg_cell_element decision_1_n3 <value> <cell_desc_opt>

chg_element decision_1_p3 <value> <location> <cell_desc>

chg_cell_element decision_1_p3 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_n3 <location> <cell_desc>

disp_element decision_1_p3 <location> <cell_desc>

6-212 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 peg)

Valid range 1 to 31
Default value 1

References

GSM parameter N3, P3

GSM specification 5.08 - Appendix A - 3.2, and Table 1
12.20 - 5.2.8.25: Signal Quality Serving Cell

68P02901W23-T 6-213
Jan 2010
decision_1_n4/decision_1_p4 Chapter 6: CM database parameters

decision_1_n4/decision_1_p4

Description

These parameters specify N4 and P4 in the decision algorithm used in the BSS.

N4 is the number of samples in the threshold comparison process used in decisions to decrease
uplink and downlink power. P4 is the number of samples in the processed measurement
(process) relative to the (averaging) algorithm in place. If at least P4 averages out of N4
averages are lower (better quality) than RSS handover threshold u_rxqual_ul_p (uplink) or RSS
handover threshold u_rxqual_dl_p (downlink), the corresponding uplink or downlink transmit
power (txpwr) is decreased.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies N4 must be greater than or equal to P4. N4 must
be less than or equal to the hreqt value set using
chg_act_alg_data command for rxqual_dl_pc and
rxqual_ul_pc.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_n4 <value> <location> <cell_desc>

chg_cell_element decision_1_n4 <value> <cell_desc_opt>

chg_element decision_1_p4 <value> <location> <cell_desc>

chg_cell_element decision_1_p4 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_n4 <location> <cell_desc>

disp_element decision_1_p4 <location> <cell_desc>

6-214 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 peg)

Valid range 1 to 31
Default value 1

References

GSM parameter N4, P4

GSM specification 5.08 - Appendix A - 3.2, and Table 1
12.20 - 5.2.8.25: Signal Quality Serving Cell

68P02901W23-T 6-215
Jan 2010
decision_1_n5/decision_1_p5 Chapter 6: CM database parameters

decision_1_n5/decision_1_p5

Description

These parameters specify N5 and P5 in the decision algorithm used in the BSS.

N5 is the number of samples in the threshold comparison process used in handover decisions.
P5 is the number of samples in the processed measurement (process) relative to the (averaging)
algorithm in place. If at least P5 averages out of N5 averages are lower than RSS handover
threshold l_rxlev_ul_h (uplink) or RSS handover threshold l_rxlev_dl_h (downlink), a handover
may be required.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies N5 must be greater than or equal to P5. N5 must
be less than or equal to the hreqt value set using
chg_act_alg_data command for rxlev_dl_ho and
rxlev_ul_ho.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_n5 <value> <location> <cell_desc>

chg_cell_element decision_1_n5 <value> <cell_desc_opt>

chg_cell_element decision_1_p5 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_n5 <location> <cell_desc>

disp_element decision_1_p5 <location> <cell_desc>

6-216 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 peg)

Valid range 1 to 31
Default value 1

References

GSM parameter N5, P5

GSM specification 5.08 - Appendix A - 3.2, and Table 1
12.20 - 5.2.8.19: Handover Control Thresholds

68P02901W23-T 6-217
Jan 2010
decision_1_n6/decision_1_p6 Chapter 6: CM database parameters

decision_1_n6/decision_1_p6

Description

These parameters specify N6 and P6 in the decision algorithm used in the BSS.

N6 is the number of samples in the threshold comparison process used in handover decisions.
P6 is the number of samples in the processed measurement (process) relative to the (averaging)
algorithm in place. If at least P6 averages out of N6 averages are greater (worse quality) than
RSS handover threshold l_rxqual_ul_h (uplink) or RSS handover threshold l_rxqual_dl_h
(downlink), a handover may be needed.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies N6 must be greater than or equal to P6. N6 must
be less than or equal to the hreqt value set using
chg_act_alg_data command for rxqual_dl_ho and
rxqual_ul_ho.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_n6 <value> <location> <cell_desc>

chg_cell_element decision_1_n6 <value> <cell_desc_opt>

chg_element decision_1_p6 <value> <location> <cell_desc>

chg_cell_element decision_1_p6 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_n6 <location> <cell_desc>

disp_element decision_1_p6 <location> <cell_desc>

6-218 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 peg)

Valid range 1 to 31
Default value 1

References

GSM parameter N6, P6

GSM specification 5.08 - Appendix A - 3.2, and Table 1
12.20 - 5.2.8.19: Handover Control Thresholds

68P02901W23-T 6-219
Jan 2010
decision_1_n7/decision_1_p7 Chapter 6: CM database parameters

decision_1_n7/decision_1_p7

Description

These parameters specify N7 and P7 in the decision algorithm used in the BSS.

N7 is the number of samples in the threshold comparison process. P7 is the number of samples
in the processed measurement (process) relative to the (averaging) algorithm in place.

If at least P7 averages out of N7 averages are greater than RSS handover threshold
u_rxlev_ul_ih (uplink) or RSS handover threshold u_rxlev_dl_ih (downlink), an internal
handover may be required if rxqual_ul/dl is also greater than l_rxqual_ul/dl_h.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies N7 must be greater than or equal to P7. N7 must
be less than or equal to the hreqt value set using
chg_act_alg_data command for rxlev_dl_ho and
rxlev_ul_ho.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_n7 <value> <location> <cell_desc>

chg_cell_element decision_1_n7 <value> <cell_desc_opt>

chg_element decision_1_p7 <value> <location> <cell_desc>

chg_cell_element decision_1_p7 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_n7 <location> <cell_desc>

disp_element decision_1_p7 <location> <cell_desc>

6-220 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 peg)

Valid range 1 to 31
Default value 1

References

GSM parameter N7, P7

GSM specification 5.08 - Appendix A - 3.2, and Table 1
12.20 - 5.2.8.19: Handover Control Thresholds

68P02901W23-T 6-221
Jan 2010
decision_1_n8/decision_1_p8 Chapter 6: CM database parameters

decision_1_n8/decision_1_p8

Description

These parameters specify N8 and P8 in the decision algorithm used in the BSS.

N8 is the number of samples in the threshold comparison process. P8 is the number of samples
in the processed measurement (process) relative to the (averaging) algorithm in place.

If at least P8 averages out of N8 averages are greater than RSS handover threshold
ms_range_max, a handover may be required due to distance.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies N8 must be greater than or equal to P8.
N8 must be less than or equal to the Hreqt value set for
rel_tim_adv.
P8 must be greater than 1 if the value of N8 is greater than
1.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_n8 <value> <location> <cell_desc>

chg_cell_element decision_1_n8 <value> <cell_desc_opt>

chg_element decision_1_p8 <value> <location> <cell_desc>

chg_cell_element decision_1_p8 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_n8 <location> <cell_desc>

disp_element decision_1_p8 <location> <cell_desc>

6-222 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 peg)

Valid range 1 to 31
Default value 1

References

GSM parameter N8, P8

GSM specification 5.08 - Appendix A - 3.2, and Table 1
12.20 - 5.2.8.21: ms Distance Average

68P02901W23-T 6-223
Jan 2010
decision_1_p_bgt_rxlev_av_h Chapter 6: CM database parameters

decision_1_p_bgt_rxlev_av_h

Description

The decision_1_p_bgt_rxlev_av_h parameter specifies which bin is used for the rxlev_dl_ho
and surround_cell parameters for the purposes of making a Better Cell power budget (pbgt)
handover decision.

This parameter may not be changed to a bin which does not contain valid power control data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_p_bgt_rxlev_av_h <value> <location> <cell_desc>

chg_cell_element decision_1_p_bgt_rxlev_av_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_p_bgt_rxlev_av_h <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
Default value 0

6-224 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference decision_1_tim_adv_av_alg

decision_1_tim_adv_av_alg

Description

The decision_1_tim_adv_av_alg parameter specifies the bin number containing the

measurement averaging algorithm data used to make handover decisions due to distance.

This parameter may not be changed to a bin which does not contain valid handover data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies rel_tim_adv

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_tim_adv_av_alg <value> <location> <cell_desc>

chg_cell_element decision_1_tim_adv_av_alg <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_tim_adv_av_alg <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
Default value 0

68P02901W23-T 6-225
Jan 2010
decision_1_ul_rxlev_av_h Chapter 6: CM database parameters

decision_1_ul_rxlev_av_h

Description

The decision_1_ul_rxlev_av_h parameter specifies the bin number containing the measurement
averaging algorithm data used to make handover decisions due to uplink signal strength.

This parameter may not be changed to a bin which does not contain valid handover data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies rxlev_ul_ho

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_ul_rxlev_av_h <value> <location> <cell_desc>

chg_cell_element decision_1_ul_rxlev_av_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_ul_rxlev_av_h <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
Default value 0

6-226 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference decision_1_ul_rxlev_av_ih

decision_1_ul_rxlev_av_ih

Description

The decision_1_ul_rxlev_av_ih parameter specifies the bin number containing the

measurement averaging algorithm data used to make handover decisions due to uplink signal
interference.

This parameter may not be changed to a bin which does not contain valid handover data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies rxlev_ul_ho

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_ul_rxlev_av_ih <value> <location> <cell_desc>

chg_cell_element decision_1_ul_rxlev_av_ih <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_ul_rxlev_av_ih <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
Default value 0

68P02901W23-T 6-227
Jan 2010
decision_1_ul_rxlev_av_p Chapter 6: CM database parameters

decision_1_ul_rxlev_av_p

Description

The decision_1_ul_rxlev_av_p parameter specifies the bin number containing the measurement
averaging algorithm data used to generate power control changes due to uplink signal strength.

This parameter may not be changed to a bin which does not contain valid power control data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies rxlev_ul_pc

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_ul_rxlev_av_p <value> <location> <cell_desc>

chg_cell_element decision_1_ul_rxlev_av_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_ul_rxlev_av_p <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
Default value 0

6-228 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference decision_1_ul_rxqual_av_h

decision_1_ul_rxqual_av_h

Description

The decision_1_ul_rxqual_av_h parameter specifies the bin number containing the

measurement averaging algorithm data used to generate handover decisions due to uplink
signal quality.

This parameter may not be changed to a bin which does not contain valid handover data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies rxqual_ul_ho

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_ul_rxqual_av_h <value> <location> <cell_desc>

chg_cell_element decision_1_ul_rxqual_av_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_ul_rxqual_av_h <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
Default value 0

68P02901W23-T 6-229
Jan 2010
decision_1_ul_rxqual_av_p Chapter 6: CM database parameters

decision_1_ul_rxqual_av_p

Description

The decision_1_ul_rxqual_av_p parameter specifies the bin number containing the

measurement averaging algorithm data used to generate power control changes due to the
uplink receive quality.

This parameter may not be changed to a bin which does not contain valid power control data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies rxqual_ul_pc

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_1_ul_rxqual_av_p <value> <location> <cell_desc>

chg_cell_element decision_1_ul_rxqual_av_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_1_ul_rxqual_av_p <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
Default value 0

6-230 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference decision_alg_type

decision_alg_type

Description

The decision_alg_type parameter specifies the current power control algorithm.

Disabling the decision_alg_type type parameter uses the bts_p_con_interval and

ms_p_con_interval parameters. This setting does not allow use of the bts_p_con_ack and
ms_p_con_ack timers.

Enabling decision_alg_type uses the bts_p_con_ack and ms_p_con_ack timers.

Enabling the decision_alg_type parameter allows a power decision based on quality to increase
the power. This results in a rxlev above the upper rxlev thresholds set in u_rxlev_dl_pc and
u_rxlev_ul_pc.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element decision_alg_type <value> <location> <cell_desc>

chg_cell_element decision_alg_type <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element decision_alg_type <location> <cell_desc>

68P02901W23-T 6-231
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean (algorithms)

Valid range 0 or 1
0 Power control algorithm number 1.
1 Power control algorithm number 2 (enables the use of
p_con_ack timers).
Default value 0

6-232 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference direct_inner_zone_threshold

direct_inner_zone_threshold

Description

The direct_inner_zone_threshold parameter specifies the rxlev threshold that must be

exceeded by the MS reported rxlev for the call to qualify for accelerated allocation of an inner
zone resource.

Type A (no operator action)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Concentric Cells feature must be enabled in order to
set this parameter.
Operator actions None

Syntax

Change command strings

chg_element direct_inner_zone_threshold <value> <location> <cell_desc>

chg_cell_element direct_inner_zone_threshold <value> <cell_desc_opt>

Display command string

disp_element direct_inner_zone_threshold <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 63
Default value 63

68P02901W23-T 6-233
Jan 2010
disuse_cnt_hreqave Chapter 6: CM database parameters

disuse_cnt_hreqave

Description

The disuse_cnt_hreqave determines the maximum disuse count for neighbor cells to be valid
candidates for handover.

Disuse count is the number of consecutive measurement reports a previously reported neighbor
is not reported by the mobile station. If the neighbor is reported before the maximum disuse
count is reached, the disuse count is reset to 0 and the neighbor remains a valid candidate.

When the disuse_cnt_hreqave parameter is enabled, the surrounding cell hreqave defines the
maximum disuse count (this can be different for each neighbor). Neighbor cells with a disuse
count less than or equal to the maximum disuse count are still valid candidates for handovers.

When the disuse_cnt_hreqave parameter is disabled, the maximum disuse count is set to 8.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element disuse_cnt_hreqave <value> <location> <cell_desc>

chg_cell_element disuse_cnt_hreqave <value> <location> <cell_desc_opt>

Display command string

disp_element disuse_cnt_hreqave <location> <cell_desc>

6-234 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled Maximum disuse count is set to 8.
1 Enabled Maximum disuse count is defined by the surrounding
cell hreqave.
Default value 0

68P02901W23-T 6-235
Jan 2010
dl_audio_lev_offset Chapter 6: CM database parameters

dl_audio_lev_offset

Description

The dl_audio_lev_offset parameter specifies the downlink volume control offset on a per BSS
basis. The offset is in 1 dB steps with a maximum increase or decrease of 30 dB (between
-15 dB and 15 dB).

The audio level parameters affect background and comfort noise. The audio level parameters do
not affect data.

NOTE
Changes to this parameter take effect immediately. This includes active calls.

NOTE
For the BSC side, turn the parameter on with a chg_ele command.

chg_ele ul/dl_audio_lev_offset <value> = 0 where <value> is the audio level

offset +15 to -15 in steps of 1dB.

To change these values at the RXCDR, use the modify_values command on the
ABSS device.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The volume_control_type parameter controls the
dl_audio_lev_offset application. If volume_control_type
= 1, then the dl_audio_lev_offset parameter only applies
to sites equipped with GDP boards. The GDP firmware
controls the volume level by converting the audio level bits
for the entered offset.

6-236 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

Syntax

Change command string

chg_element dl_audi_lev_offset <value> <location>

Display command string

disp_element dl_audio_lev_offset 0

Values

Value type Integer (1 Step = 1 dB)

Valid range -15 to +15
Default value 0

68P02901W23-T 6-237
Jan 2010
dl_dtx_voice_data Chapter 6: CM database parameters

dl_dtx_voice_data

Description

The dl_dtx_voice_data parameter specifies the option for downlink discontinuous transmission
(DTX) for speech and voice.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The dl_dtx_voice_data parameter affects speech only if
dnlk_vad_dtx is enabled.

Syntax

Change command strings

chg_element dl_dtx_voice_data <value> <location> <cell_desc>

chg_cell_element dl_dtx_voice_data <value> <cell_desc_opt>

Display command string

disp_element dl_dtx_voice_data <location> <cell_desc>

Values

Value type Integer

Value range 0 to 3
0 DTX enabled for speech / disabled for non-transparent data.
1 DTX disabled for speech / disabled for non-transparent data.
2 DTX disabled for speech / enabled for non-transparent data.
3 DTX enabled for speech / enabled for non-transparent data.

Default value 0

6-238 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dl_rxlev_ho_allowed

dl_rxlev_ho_allowed

Description

The dl_rxlev_ho_allowed parameter enables or disables a handover due to downlink receive

level (rxlev).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element dl_rxlev_ho_allowed <value> <location> <cell_desc>

chg_cell_element dl_rxlev_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element dl_rxlev_ho_allowed <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

68P02901W23-T 6-239
Jan 2010
References Chapter 6: CM database parameters

References

Internal name EN_RXLEV_HO

This is a Motorola parameter.

6-240 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dl_rxqual_ho_allowed

dl_rxqual_ho_allowed

Description

The dl_rxqual_ho_allowed parameter enables or disables a handover due to downlink receive

quality (rxqual).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element dl_rxqual_ho_allowed <value> <location> <cell_desc>

chg_cell_element dl_rxqual_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element dl_rxqual_ho_allowed <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

68P02901W23-T 6-241
Jan 2010
References Chapter 6: CM database parameters

References

Internal name EN_RXQUAL_HO

This is a Motorola parameter.

6-242 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dnlk_vad_dtx

dnlk_vad_dtx

Description

The dnlk_vad_dtx parameter enables or disables downlink Voice Activated

Detection/Discontinuous Transmission (VAD/DTX) at the RXCDR or at the local transcoding BSC.

If VAD is disabled, no silence/voice detection takes place and no DTX is possible for speech calls,
regardless of the value of dl_dtx_voice_data.

The downlink DTX is supported only on the non-BCCH carrier.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies Must be executed in SYSGEN mode.
This parameter can be displayed or changed only at sites
where transcoding is enabled (RXCDR or local transcoding
BSC).
When enabled, the dnlk_vad_dtx parameter makes the
dl_dtx_voice_data parameter alive.

Syntax

Change command string

chg_element dnlk_vad_dtx <value> <location>

Display command string

disp_element dnlk_vad_dtx <location>

Values

Value type Boolean

Valid range 0 or 1
0 Enabled
1 Disabled
Default value None

68P02901W23-T 6-243
Jan 2010
dpc Chapter 6: CM database parameters

dpc

Description

The dpc parameter specifies the Destination Point Code (DPC). The range of values depends on
the setting of the parameter.

The system checks the value of the opc (see opc on page 6-666) and ss7_mode (see ss7_mode
on page 6-871) variables and compares them to the value for ss7_mode. If the ranges are not
compatible, the system rejects the changes and displays the following message:

COMMAND ACCEPTED: WARNING: When opc equals dpc, communication with MSC is impossible.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is only valid at the BSC.

Syntax

Change command string

chg_element dpc <value> <location>

Display command string

disp_element dpc <location>

Values

Value type Integer

Valid range 0 to 16383 If ss7_mode = 0 (CCITT)
0 to If ss7_mode =1 (Bellcore)
16777215
Default value None

6-244 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter DPC

GSM specification CCITT Q.708

68P02901W23-T 6-245
Jan 2010
dproc_id Chapter 6: CM database parameters

dproc_id

{26638}

Description

The dproc_id parameter identifies a unique id for the PXP DPROC that is connected to the
Ethernet GBL.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is valid only when the Gb over IP feature is
unrestricted and the Gb mode is set to static IP mode.

Syntax

Equip command strings

equip <location> gbl

Unequip command strings

unequip <location> gbl <gbl id>

Display command strings

disp_equipment <location> gbl <gbl id>

Values

Value type Integer

Valid range 1 to 6 and 11 to 16
1 to 6 Minimum
11 to 16 Maximum
Default value N/A

6-246 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dr_allowed

dr_allowed

Description

The dr_allowed parameter enables or disables the Directed Retry feature.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only if all the following
conditions are met:

the Directed Retry feature is available,

the neighbor is placed on the SACCH list, and

the neighbor is external.

Syntax

Change command strings

modify_neighbor <src_cell_id> <neighbor_cell_id> dr_allowed <value>

Display command string

disp_neighbor <src_cell_id> all

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None

68P02901W23-T 6-247
Jan 2010
dr_chan_mode_modify Chapter 6: CM database parameters

dr_chan_mode_modify

Description

The dr_chan_mode_modify parameter determines if the channel mode modify procedure

follows a successful handover of a Phase 1 MS in which the channel mode changed to full rate
speech. The BSS reads this parameter only in the case of a successful handover in which the
channel mode changed, the MS is Phase 1, and the new channel mode is full rate speech.

Changing the channel mode during a handover occurs only during a Directed Retry procedure.
For this to occur, either an external Directed Retry handover has successfully completed to this
BSS or an intra-BSS Directed Retry handover has successfully completed and either the database
parameter dr_standard_congest or dr_ho_during_assign is enabled in the source cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Directed Retry feature must be unrestricted.
This parameter can be changed only at the BSC.

Syntax

Change command string

chg_element dr_chan_mode_modify <value> 0

Display command string

disp_element dr_chan_mode_modify 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-248 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM specification TS GSM 08.08 ETR 09.94

This is a Motorola defined parameter.

68P02901W23-T 6-249
Jan 2010
dr_ho_during_assign Chapter 6: CM database parameters

dr_ho_during_assign

Description

The dr_ho_during_assign parameter determines if a handover is handled during an assignment

procedure.

This parameter can only be changed at the BSC.

This parameter is copied if the copy_cell command is used.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The MSC may need to increase the timer waiting for the
Assignment Complete message from the BSS when this
database parameter is enabled.
The BSS does not initiate an external handover due to
the Directed Retry procedure if the msc_preference
parameter indicates that directed retry is supported only
within the BSS (not across the A-interface) when the
dr_standard_congest parameter is enabled.
The Directed Retry feature must be unrestricted.
This parameter requires that dr_preference be enabled.

Syntax

Change command strings

chg_element dr_ho_during_assign <value> <location> <cell_desc>

chg_cell_element dr_ho_during_assign <value> <cell_desc_opt>

Display command string

disp_element dr_ho_during_assign <location> <cell_desc>

6-250 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Ignore the need of a handover until the assignment
procedure is complete.
1 Act on the need for a handover during the assignment
procedure.
Default value 0

References

GSM specification TS GSM 08.08

This is a Motorola defined parameter.

68P02901W23-T 6-251
Jan 2010
dr_preference Chapter 6: CM database parameters

dr_preference

Description

The dr_preference parameter enables or disables the Directed Retry procedures.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies dr_standard_congest
dr_ho_during_assign
The Directed Retry feature must be unrestricted.
This parameter can only be changed at the BSC.

Syntax

Change command string

chg_element dr_preference <value> 0

Display command string

disp_element dr_preference 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification TS GSM 08.08

This is a Motorola defined parameter.

6-252 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dr_standard_congest

dr_standard_congest

Description

The dr_standard_congest parameter enables or disables the standard Directed Retry

congestion procedure in a cell. The procedure initiates a handover if possible for a call needing
a TCH in the case of congestion.

This parameter is copied if the copy_cell command is used.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Directed Retry feature must be unrestricted.
The dr_preference parameter must not be set to zero.
The MSC may need to increase the timer waiting for the
Assignment Complete message from the BSS when this
database parameter is enabled.
The BSS does not initiate an external handover due to
the Directed Retry procedure if the msc_preference
parameter indicates that directed retry is supported
within the BSS (not across the A-interface) when the
dr_standard_congest parameter is enabled.

Syntax

Change command strings

chg_element dr_standard_congest <value> <location> <cell_desc>

chg_cell_element dr_standard_congest <value> <cell_desc_opt>

Display command string

disp_element dr_standard_congest <location> <cell_desc>

68P02901W23-T 6-253
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification TS GSM 08.08

This is a Motorola defined parameter.

6-254 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dri_density

dri_density

Description

The dri_density parameter specifies the density mode (single, double or double density
capacity).

The range of this parameter is extended to a third allowed value: Capacity (double density
without timeslot blanking on the non-EDGE carrier).

Type A (no operator actions)

Supported by OMC-R GUI Yes

Cell description required No
Dependencies A number of existing parameters that can be modified
under the DRI device are affected by the double
density DRI devices. Modifications of tcu_port and
antenna_select are propagated to the associated DRI
device if the DRI being modified is in double density
mode. The parameter combining_type is not valid to be
modified for double density DRI devices.
The extended range for this attribute is valid only when:

The configured DRI is in a Horizon II family cabinet

(Horizon II macro, Horizon II mini and Horizon II
micro including extension cabinets).

The master SITE cabinet is a Horizon II family

cabinet (Horizon II macro, Horizon II mini and
Horizon II micro).

CTU2-D capacity feature (ctu2dcapOpt) is Enabled

at the BSS.
To enable 4 Branch Receive Diversity, the DRIs should be
equipped in a single band Horizon II macro cabinet and
the DRI is modified to single density mode.

Syntax

Modify/Change command strings

equip <location> dri

modify_value <location> dri_density <value> dri <dev_fun_id1> <dev_fun_id2>

<dev_fun_id3>

68P02901W23-T 6-255
Jan 2010
Values Chapter 6: CM database parameters

Display command strings

disp_equipment <location> dri <id1> <id2> <id3>

Values

Value type Integer

Valid range 1 to 3
1 Single density mode
2 Double density mode
3 Double density capacity
Default value None

6-256 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dsp_error_clr_thresh

dsp_error_clr_thresh

Description

The dsp_error_clr_thres parameter identifies the value for which the error count must be equal
or less than for an alarm to be cleared for a DSP.

Always satisfy the condition (dsp_error_gen_thresh - dsp_error_clr_thresh) >=2.

Type A (no operator actions)

Supported by OMC-R GUI Yes

Cell description required No
Dependencies The dsp_error_clr_thresh parameter is restricted by
the Enhanced Circuit Error Rate Monitor restrictable
feature.
The parameter is restricted so that at least two GPRS
Alarm Increment Time Periods can pass without a sync
loss error occurring on a resource before an alarm is
cleared. It is necessary to look for sufficient successes
to avoid clearing the alarm on one or more successful
GPRS Alarm Increment Time Period that had too short
a duration for the CCU to time out and send an error
indication.

Syntax

Modify/Change command strings

chg_element dsp_error_clr_thres <value> <location>

Display command strings

disp_element dsp_error_clr_thres <location>

Values

Value type Integer

Valid range 0 to 253
Default value 0

68P02901W23-T 6-257
Jan 2010
dsp_error_gen_thresh Chapter 6: CM database parameters

dsp_error_gen_thresh

Description

The dsp_error_gen_thresh parameter identifies the value where the error count must be equal
to or greater than for an alarm to be generated for a DSP.

Always satisfy the condition (dsp_error_gen_thresh - dsp_error_clr_thresh) >=2.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The dsp_error_gen_thresh parameter is restricted by
the Enhanced Circuit Error Rate Monitor restrictable
feature.
The parameter is restricted so that at least two GPRS
Alarm Increment/Decrement Time Periods can pass
without a sync loss error occurring on a resource before
an alarm can be cleared. It is necessary to look for
sufficient successes to avoid clearing the alarm on one
or more successful GPRS Alarm Increment/Decrement
Time Period that had too short a duration for the CCU to
time out and send an error indication.

Syntax

Modify/Change command strings

chg_element dsp_error_gen_thresh <value> <location>

Display command strings

disp_element dsp_error_gen_thresh <location>

Values

Value type Integer

Valid range 2 to 255
Default value 6

6-258 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dsp_error_inc

dsp_error_inc

Description

The dsp_error_inc parameter identifies the value by which the error count is incremented if an
error indication is received for a DSP during a GPRS Alarm Increment Time Period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The dsp_error_inc parameter is restricted by the
Enhanced Circuit Error Rate Monitor restrictable
feature.
When the dsp_error_inc parameter is set to 0 outside
the sysgen mode, the operator is warned that the DSP
alarms may be prevented from being generated.

Syntax

Modify/Change command strings

chg_element dsp_error_inc <value> <location>

Display command strings

disp_element dsp_error_inc <location>

Values

Value type Integer

Valid range 0 to 255
Default value 1 This parameter is defaulted to 1 when the ECERM feature
is unrestricted.
0 This parameter is defaulted to 0 (feature turned off) if the
ECERM feature is restricted.

68P02901W23-T 6-259
Jan 2010
dtx_required Chapter 6: CM database parameters

dtx_required

Description

The dtx_required parameter specifies the MS capability to use discontinuous transmission

(DTX). Enabling this feature helps to reduce interference and prolong battery life.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element dtx_required <value> <location> <cell_desc>

chg_cell_element dtx_required <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element dtx_required <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 2
0 Permitted (MS may use DTX)
1 Required (MS must use DTX)
2 Disallowed (MS must not use DTX)
Default value 2

6-260 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter DTX

GSM specification 4.08 - 10.5.2.3, figure 10.22, table 10.16

68P02901W23-T 6-261
Jan 2010
dual_band_offset Chapter 6: CM database parameters

dual_band_offset

Description

The dual_band_offset parameter estimates the effects of the power level differences that occur
when comparing signal strengths from different zones. The dual_band_offset is applied to
power budget handover calculations from the inner zone to cells of any frequency type. Plus, it
is used to evaluate the criteria for the inter zone handovers within a cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter may be modified only when the Dual Band
Cells feature is unrestricted.

Syntax

Change command string

chg_cell_element <location> dual_band_offset <value>

Display command string

disp_element dual_band_offset <location> <cell_desc>

Values

Value type Integer

Valid range -63 to 63
Default value 0

6-262 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dyn_step_adj

dyn_step_adj

Description

The dyn_step_adj parameter enables or disables the uplink and downlink dynamic step
adjustment algorithm for the step size. When enabled, the calculation of step size can include or
exclude dynamic power reduction caused by the level being above the upper level threshold.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

add_cell <gsm_cell_id> <location>

chg_element dyn_step_adj <value> <location> <cell_desc>

chg_cell_element dyn_step_adj <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element dyn_step_adj <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 2
0 Disabled
1 Enabled (excludes power reduction)
2 Enabled (includes power reduction)
Default value 0

68P02901W23-T 6-263
Jan 2010
dyn_step_adj_fmpr Chapter 6: CM database parameters

dyn_step_adj_fmpr

Description

The dyn_step_adj_fmpr parameter specifies the percentage power reduction used in the
dynamic power reduction calculation.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

add_cell <gsm_cell_id> <location>

chg_element dyn_step_adj_fmpr <value> <location> <cell_desc>

chg_cell_element dyn_step_adj_fmpr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element dyn_step_adj_fmpr <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 10
Default value 10

6-264 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dynet_tchs_reserved

dynet_tchs_reserved

Description

The dynet_tchs_reserved parameter specifies the amount of terrestrial backing resources

reserved for a changing cell when dynamic allocation is enabled for the site containing the cell.

The system rejects this parameter if the new value causes the total terrestrial backing resources
for a BTS network to be less than the total reserved cell capacity.
The total terrestrial backing resources for a BTS network is the sum of the terrestrial
backing resources reserved on the DYNETs for the BTS network.

The total reserved cell capacity for a site is the sum of the reserved capacity for all of the
cells at the site minus the dedicated resources for the site. If this total is less than zero, it
is set at zero. The total reserved cell capacity for a BTS networks is then the sum of the
total reserved cell capacity of the dynamic allocation BTSs in the BTS network.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter is not available unless the containing site is
configured to support dynamic allocation.
The parameter is invalid for the BSC (location 0).
The system rejects the command if the cell_desc equals
all.
The Dynamic Allocation feature must be in operation.

Syntax

Change command string

chg_element dynet_tchs_reserved <value> <location> <cell_desc>

Display command string

disp_element dynet_tchs_reserved <location> <cell_desc>

68P02901W23-T 6-265
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (representing the number of reserved TCHs)

Valid range 0 to 32
Default value 0

6-266 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference early_classmark_sending

early_classmark_sending

Description

The early_classmark_sending parameter specifies the following:

Whether the BSS suppresses the early sending of the Classmark Update message to the
MSC.

Whether an MS is allowed to send an early Classmark Change message.

If this parameter is changed to 0 or 1, and inter_rat_enabled is equal to 4, 5, 6 or 7 for any cell

in that BSS, the BSS issues the following warning:

Warning: early_classmark_sending must be enabled on Air Interface for Enhanced

2G/3G.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Multiband Inter-cell Handover feature must be
enabled.
If the Location Services feature is enabled and the operator
attempts to change the early_classmark_sending element
to a value which does not support early classmark sending
on both the A-interface and the Air-interface, the command
is rejected.
This dependency is also checked during database
verification (see lcs_mode section).
This parameter can only be changed at the BSC, but it can
be viewed at any site within a specified BSS.

Syntax

Change command string

chg_element early_classmark_sending <value> 0

Display command string

disp_element early_classmark_sending 0

68P02901W23-T 6-267
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 3
0 Disabled across both the A-interface and the Air-interface.
1 Enabled on A-interface, disabled on Air-interface.
2 Disabled on A-interface, enabled on Air-interface.
3 Enabled across both the A-interface and the Air-interface.
Default value 0

When early_classmark_sending is set to 2, the BSS does not forward classmark update
messages to the MSC. This means that the MSC does not obtain any information about the
MS capabilities.

However, the MSC can still make solicited requests for classmark updates by sending a
Classmark Request message to the BSS. If this is not done, the frequency capabilities of the
MS are based on the target cell frequency when multiband handovers are being performed.
Therefore, after an external handover, the BSS reports the neighbors to the MS as follows:

Hand over from GSM900 to GSM900 - only the GSM900 neighbors

Hand over from GSM900 to GSM1800 - only the GSM1800 neighbors

Hand over from GSM1800 to GSM900 - only the GSM900 neighbors

Hand over from GSM1800 to GSM1800 - only the GSM1800 neighbors.

External multiband capabilities are limited, and subsequent handovers to GSM1800 cells are
therefore not possible.

References

GSM specification TS GSM 04.08, section 10.5.2.34

This is a Motorola defined parameter.

6-268 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference eas_alarm

eas_alarm

Description

The eas_alarm parameter is the text component of the EAS (External Alarm System) alarm
table. The EAS alarm table consists of 34 indexed pairs consisting of a text component and a
severity level. The text component and severity level are assigned when the EAS alarm table is
initialized using the chg_eas_alarm command. The text component of an indexed pair may only
be changed using the chg_eas_alarm command.

The index number uniquely identifies each text and severity pair in the EAS alarm table.

Index numbers are required to specify which of the 34 pairs to display. Index values are 0 to 33.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_eas_alarm <alarm_table_index> <alarm_severity_level> <eas_alarm_text>

Display command string

disp_element eas_alarm,<index> <location>

Values

Value type Text

Valid range Up to 24 alphanumeric characters (including spaces).
Default value None

68P02901W23-T 6-269
Jan 2010
eas_alarm_type Chapter 6: CM database parameters

eas_alarm_type

Description

The eas_alarm_type parameter specifies one of the EAS (External Alarm System) alarm table
elements to one of eight optocouplers of an addressed PIX card. The eas_alarm_type value
corresponds to the index number identifying the location of a text and severity level pair.

Index numbers are required to specify which of the 34 pairs to display. Index values are 0 to 33.

The disp_element command displays the optocouplers and indexed alarm text and severity
pairs assigned with the map_eas_opto command.

The output of the disp_element command appears in the form:

eas_alarm_type = x y x y x y x y x y

where each x corresponds to an opto # and each y corresponds to an alarm text and severity pair.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Add/Change command strings

equip <location> eas

map_eas_opto <location> <device_id> [<opt_#1> <alarm_table_index>]

...[<opt_#8><alarm_table_index>]

Display command string

disp_element eas_alarm_type,<index> <location>

6-270 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 33
Default value None

68P02901W23-T 6-271
Jan 2010
eas_report_opto Chapter 6: CM database parameters

eas_report_opto

Description

The eas_report_opto parameter specifies whether each of the eight optocouplers (optos)
on a specific PIX card reports state changes.

Index numbers are required. Index numbers are used to identify the desired EAS device. Index
values are assigned during installation.

The output of the disp_element command appears in the form:

eas_report_opto = 1 = ON 2 = ON 3 = OFF 4 = ON 5 = OFF 6 = ON 7 = ON 8 = ON

where 1, 2, 4, 6, 7, and 8 report state changes but 3 and 5 do not.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_eas_report <location> <device_id> [ on = [<opto_#1>]...[<opto_#n>] ] [ off

= [opto_#1>]...[<opto_#n>] ]

Display command string

disp_element eas_report_opto,<index> <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None

6-272 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference eas_severity

eas_severity

Description

The eas_severity parameter specifies the severity level component of the EAS (External Alarm
System) alarm table.

The index number uniquely identifies each text and severity pair in the EAS alarm table. The
EAS alarm table consists of 34 indexed pairs consisting of a text component and a severity level.
The text component and severity level are assigned when the EAS alarm table is initialized
using the chg_eas_alarm command. The severity component may be changed using either
the chg_element or the chg_eas_alarm command. If the chg_eas_alarm command is used, it
permits the alarm text to be changed at the same time.

Clear is a valid alarm condition, but it is not a valid alarm severity setting. All alarms of
severity levels 0 to 4 can receive a clear indication for the original pegging of an alarm when
a system is running.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command strings

chg_eas_alarm <alarm_table_index> <alarm_severity_level> <new_alarm_string>

chg_element eas_severity,<index> <value> <location>

Display command string

disp_element eas_severity,<index> <location>

68P02901W23-T 6-273
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 4
0 Investigate
1 Critical
2 Major
3 Minor
4 Warning
Default value None

6-274 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference edge_asym_mismatch_cita

edge_asym_mismatch_cita

{34452}

Description

The edge_asym_mismatch_cita parameter sets the weight factor between the EDGE capable
mobiles and UL GMSK restricted carriers. The reason is that the EDGE capable mobiles are
biased towards the UL GMSK restricted carriers over the GPRS carriers. This parameter can be
accessed and updated both in and out of sysgen mode.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter can be modified only when the CTU2-D
asymmetric feature and the GPRS feature are unrestricted,
and the asym_edge_enabled parameter is enabled.

Syntax

Change command string

chg_cell_element edge_asym_mismatch_cita <value> <cell_desc>

chg_element edge_asym_mismatch_cita <value> <location> <cell_desc>

Display command string

disp_element edge_asym_mismatch_cita <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 100
0 Minimum
100 Maximum
Default value 30

68P02901W23-T 6-275
Jan 2010
efr_enabled Chapter 6: CM database parameters

efr_enabled

Description

The efr_enabled parameter enables or disables the Enhanced Full Rate (EFR).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The EFR feature must be unrestricted.
This parameter cannot be enabled if the
handover_required_sp_ver_used parameter is
disabled.
This parameter is only valid at a BSC location.

Syntax

Change command string

chg_element efr_enabled <value> 0

Display command string

disp_element efr_enabled 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-276 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM specification TS GSM 04.08 [2], TS GSM 08.08 [3],

TS GSM 08.058 [4]
This is a Motorola defined parameter.

68P02901W23-T 6-277
Jan 2010
egprs_init_dl_cs Chapter 6: CM database parameters

egprs_init_dl_cs

Description

The egprs_init_dl_cs parameter specifies the initial downlink coding scheme to be used for
an EGPRS TBF in a cell. This parameter is also used for Quality of Service (QoS) capacity
determination.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The EGPRS feature must be unrestricted.
The value of this parameter cannot be changed when
gprs_enabled equals 1.

Syntax

Change command strings

chg_element egprs_init_dl_cs <value> <location> <cell_desc>

chg_cell_element egprs_init_dl_cs <value> <cell_desc>

Display command strings

disp_cell <cell_desc> ["full"]

disp_element egprs_init_dl_cs <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 8
0 MCS1 is applied to start on downlink TBF for this cell.
1 MCS2 is applied to start on downlink TBF for this cell.
2 MCS3 is applied to start on downlink TBF for this cell.
3 MCS4 is applied to start on downlink TBF for this cell.
4 MCS5 is applied to start on downlink TBF for this cell.
5 MCS6 is applied to start on downlink TBF for this cell.

6-278 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

6 MCS7 is applied to start on downlink TBF for this cell.

7 MCS8 is applied to start on downlink TBF for this cell.
8 MCS9 is applied to start on downlink TBF for this cell.
Default value 2 The default value is 2 because MCS3 is considered to be
safe to start the downlink transfer for all mobiles, when
there is no prior information of a mobiles RF channel
quality, regardless of where they are in the cell.

68P02901W23-T 6-279
Jan 2010
egprs_init_ul_cs Chapter 6: CM database parameters

egprs_init_ul_cs

Description

The egprs_init_ul_cs parameter specifies the initial uplink coding scheme to be used for an
EGPRS TBF in the cell. This parameter is also used for Quality of Service (QoS) capacity
determination.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The EGPRS feature must be unrestricted.
The value of this parameter cannot be changed when
gprs_enabled equals 1.

Syntax

Change command strings

chg_element egprs_init_ul_cs <value> <location> <cell_desc>

chg_cell_element egprs_init_ul_cs <value> <cell_desc>

Display command strings

disp_cell <cell_desc> ["full"]

disp_element egprs_init_ul_cs <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 8
0 MCS1 is applied to start on uplink TBF for this cell.
1 MCS2 is applied to start on uplink TBF for this cell.
2 MCS3 is applied to start on uplink TBF for this cell.

6-280 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

3 MCS4 is applied to start on uplink TBF for this cell.

4 MCS5 is applied to start on uplink TBF for this cell.
5 MCS6 is applied to start on uplink TBF for this cell.
6 MCS7 is applied to start on uplink TBF for this cell.
7 MCS8 is applied to start on uplink TBF for this cell.
8 MCS9 is applied to start on uplink TBF for this cell.
Default value 2 The default value is 2 because MCS3 is considered to
be safe to use for uplink data packets after contention
resolution for all mobiles, when there is no prior information
of a mobiles RF channel quality, regardless of where they
are in the cell.

68P02901W23-T 6-281
Jan 2010
egsm_bcch_sd Chapter 6: CM database parameters

egsm_bcch_sd

Description

The egsm_bcch_sd parameter specifies whether the cell is configured for both BCCH carriers
and the placement of SDCCH channels for the Extended GSM (EGSM) cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The egsm_bcch_sd parameter can be disabled only if:

The BCCH carrier is not in the GSM Extension band.

The sd_load parameter is 0 for all carriers in the Cell.

The hopping systems do not contain a combination of

PGSM and GSM extension band frequencies.

The neighbor BCCH frequencies are not in the GSM

extension band.
The egsm_bcch_sd parameter can be enabled only if the
cell is an EGSM frequency cell.

Syntax

Change command strings

chg_element egsm_bcch_sd <value> <location> <cell_desc>

chg_cell_element egsm_bcch_sd <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element egsm_bcch_sd <location> <cell_desc>

6-282 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-283
Jan 2010
egsm_handover_threshold Chapter 6: CM database parameters

egsm_handover_threshold

Description

The egsm_handover_threshold parameter specifies the range of interference bands allowed

for handing over an extended GSM MS using a primary resource which is needed by a primary
MS. Allowed interference bands are those above or meeting a specified threshold, which are
considered best quality resources. Forced handovers may be disallowed by disabling the
egsm_handover_threshold parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter may only be changed on EGSM systems.

Syntax

Change command strings

chg_element egsm_handover_threshold <value> <location> <cell_desc>

chg_cell_element egsm_handover_threshold <value> <cell_desc_opt>

Display command string

disp_element egsm_handover_threshold <location> <cell_desc>

6-284 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 5
0 Forced handovers are not allowed.
1 Forced handovers to interference band 1 extended resource
are allowed.
2 Forced handovers to interference bands 1 to 2 extended
resource are allowed.

3 Forced handovers to interference bands 1 to 3 extended

resource are allowed.
4 Forced handovers to interference bands 1 to 4 extended
resource are allowed.
5 Forced handovers to interference bands 1 to 5 extended
resource are allowed.
Default value 0

68P02901W23-T 6-285
Jan 2010
emergency_class_switch Chapter 6: CM database parameters

emergency_class_switch

Description

The emergency_class_switch parameter enables or disables emergency calls by access class.

When disabled, all emergency calls are allowed.

When enabled, only emergency calls from classes 11 to 15 are allowed.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies cell_bar_access_class

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element emergency_class_switch <value> <location> <cell_desc>

chg_cell_element emergency_class_switch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element emergency_class_switch <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-286 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter EC
GSM specifications 4.08 - 3.3.1: radio resource connection establishment
initiated by the MS
4.08 - 5.2.1.2: emergency call establishment
4.08 - 10.5.2.17, and table 10.30
12.20 - 5.2.8.7 - Cell Description - Emergency Call Not
Allowed
2.11 - 4: access class definitions

68P02901W23-T 6-287
Jan 2010
emergency_group_priority Chapter 6: CM database parameters

emergency_group_priority

Description

The emergency_group_priority attribute defines a priority level threshold for calls. Any
call with priority level value less than or equal to the value of emergency_group_priority is
exempted from certain BSS congestion mechanisms when the eMLPP feature is unrestricted.

The highest priority level value is 1. Less than means numerically lower, that is, 2 is less than 3
but is a higher priority. Thus, for example, when emergency_group_priority is set to 3, calls
with priority levels 1 to 3 are exempt from the congestion mechanisms.

Setting emergency_group_priority to a value of 0 disables this functionality.

The exempted BSS congestion mechanisms are:

FR to HR congestion handovers.

Standard congestion handovers.

Multi-band congestion handovers.

Multi-band congestion handovers on assignment.

Direct assignment to inner zone in dual band cells.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The eMLPP feature must be unrestricted

Syntax

Add/Change command strings

chg_element emergency_group_priority <value> <location>

Display command strings

disp_element emergency_group_priority <location>

6-288 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 14
0 No calls are exempted from congestion mechanisms.
14 All calls are considered in the congestion mechanisms.
Default value 0

68P02901W23-T 6-289
Jan 2010
en_incom_ho Chapter 6: CM database parameters

en_incom_ho

Description

The en_incom_ho parameter enables or disables incoming handovers based on whether the
cell is barred.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element en_incom_ho <value> <location> <cell_desc>

chg_cell_element en_incom_ho <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element en_incom_ho <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-290 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM specification GSM TS 03.22 section 3.5.1

This is a Motorola defined parameter.

68P02901W23-T 6-291
Jan 2010
enhanced_relief Chapter 6: CM database parameters

enhanced_relief

Description

The enhanced_relief parameter enables or disables the Intelligent Congestion Relief feature.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Congestion Relief feature must be unrestricted.

Syntax

Change command string

chg_element enhanced_relief <value> <location> <cell_desc>

Display command string

disp_element enhanced_relief <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-292 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference eop_enabled

eop_enabled

Description

The eop_enabled parameter enables or disables the Enhanced One Phase Access feature.

The system issues the following warning if eop_enabled is changed outside Sysgen when the
QoS feature is unrestricted and bssgp_pfc_bit equals 1:

WARNING: Changes to this element are overridden while QoS is enabled.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies To enable Enhanced One Phase Access, this feature must
be unrestricted.
When QoS feature is enabled, this parameter is set to 0
(disabled) for a PCU.

NOTE
If QoS is enabled, the PCU overrides the database value of eop_enabled with an
internal value of 0; that is, EOP functionality is disabled for that PCU.

Syntax

Change command string

chg_element eop_enabled <value> <location>

Display command string

disp_element eop_enabled <location>

68P02901W23-T 6-293
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 EOP disabled
1 EOP enabled
Default value 0

6-294 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ercgprsOpt

ercgprsOpt

Description

The ercgprsOpt parameter indicates whether the Extended Range Cell support for the data
feature functionality is unrestricted in the BSS software.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies If the ercgprsOpt flag indicates that the extended range
for the data feature is restricted, attempts to change the
Extended Range Cell for data specific database parameters
is rejected.

Only if both the GPRS feature (gprsOpt) and ERC feature

(ercOpt) are unrestricted, can Extended Range Cell
for the data feature be unrestricted. If this parameter
indicates that Extended Range Cell for the data feature
is unrestricted, and if either the GPRS optional features
(gprsOpt) or ERC optional features (ercOpt) are restricted,
then the options object for the Extended Range Cell for
Data feature cannot be created. The tool used to create the
options object for the BSS handles this dependency.

Values

Value type Boolean

Valid range 0 or 1
0 Restricted
1 Unrestricted
Default value N/A

68P02901W23-T 6-295
Jan 2010
erc_ta_priority Chapter 6: CM database parameters

erc_ta_priority

Description

The erc_ta_priority parameter specifies the priority threshold for extended range cell neighbor.
If the absolute timing advance is greater than the priority threshold, the ERC neighbors are
placed at the top of the list of sorted handover candidates. Otherwise, the ERC neighbors are
appended to the end of the list of candidates.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command string

chg_element erc_ta_priority <value> <location> <cell_desc>

Display command string

disp_element erc_ta_priority <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 63
Default value 50

6-296 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference erroneous_lapdm_discard_enabled

erroneous_lapdm_discard_enabled

Description

The err_lapdm_discard_enabled parameter is used to enable and disable the function for
discarding the erroneous I/RR/SABM message in LAPDm. This parameter can be changed in
and out of sysgen mode. The RRSM processes have to be notified of the change in this mode.

NOTE
The erroneous_lapdm_discard_enabled parameter is not prompted and set to
default value zero when adding a new cell or copying a cell, which has no impact to
the MMI Commands add_cell and copy_cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element erroneous_lapdm_discard_enabled <value> <location> <cell_desc>

chg_cell_element erroneous_lapdm_discard_enabled <value> <cell_desc_opt>

Display command strings

disp_element erroneous_lapdm_discard_enabled <location> <cell_desc>

disp_cell <cell_id> ["full"]

Values

Value type Boolean

Valid range 0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-297
Jan 2010
eth_rx_errors_threshold Chapter 6: CM database parameters

eth_rx_errors_threshold

Description

The eth_rx_errors_threshold parameter specifies the maximum allowable percentage of

Ethernet frames received in error of all frames received.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element eth_rx_errors_threshold <value> <location>

Display command string

disp_element eth_rx_errors_threshold <location>

Values

Value type Integer

Valid range 0 to 100
Default value 10

6-298 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference eth_tx_errors_threshold

eth_tx_errors_threshold

Description

The eth_tx_errors_threshold parameter specifies the maximum allowable percentage of

Ethernet transmit errors of all frames transmitted.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element eth_tx_errors_threshold <value> <location>

Display command string

disp_element eth_tx_errors_threshold <location>

Values

Value type Integer

Valid range 0 to 100
Default value 10

68P02901W23-T 6-299
Jan 2010
ext_range_cell Chapter 6: CM database parameters

ext_range_cell

Description

The ext_range_cell parameter enables or disables the Extended Range Cell feature at a Cell.

Type B (Operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The ext_range_cell parameter cannot be changed if the
Extended Range Cells feature is restricted.
This parameter cannot be set to a non-zero value when
pccch_enabled is 1.
The number of extended range timeslots on the BCCH RTF
must support the BCCH, CCCH, and SDCCH channels as
these channels are always extended.
ms_max_range must be less than or equal to 63 for a
normal range cell. If ext_range_cell is enabled, the
maximum value of ms_max_range increases to 219.
max_number_sdcchs must be less than or equal to 20
when Extended Range is enabled.
Baseband hopping systems can only be configured among
timeslots of the same type, such as extended or normal.
This parameter is not available at M-Cellcity, Horizonmicro
or Horizoncompact sites.
If frequency hopping systems is enabled in an Extended
Range Cell, all frequency hopping indicators for the
timeslots in the BCCH carrier should be set to 255 (in
hexadecimal, 0xff).
Operator actions Lock the associated DRIs to change this parameter.

Syntax

Change command string

chg_cell_element ext_range_cell <value> <cell_desc_opt>

The system displays the following prompt:

Enter handover threshold mobile max range:

Display command string

disp_element ext_range_cell <location> <cell_desc>

6-300 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 2
0 Extended Range disabled for the cell.
1 Extended Range is enabled as a boundary cell.
2 Extended Range is enabled as an isolated cell (rural area).
Default value 0

68P02901W23-T 6-301
Jan 2010
ext_ul_dur Chapter 6: CM database parameters

ext_ul_dur

Description

The new per BSS element ext_ul_dur (Extended Uplink Duration) is the maximum duration
in block periods for which the uplink TBF operates in an extended mode without getting any
new real RLC data block.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies Modification of ext_ul_dur is allowed only when the
Extended Uplink feature is unrestricted.

Syntax

Change command string

chg_element ext_ul_dur <value> <location>

Display command string

disp_element ext_ul_dur <location>

Values

Value type Integer

Valid range 0 or 24 - 250
0 Extended uplink feature is disabled.
24 - 250 Extended uplink feature is enabled.
Default value 0

NOTE
The values are in block periods (1 bp = 20 millisecond).

6-302 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ext_utbf_nodata

ext_utbf_nodata

Description

The ext_utbf_nodata parameter indicates to the mobile station during the extended uplink TBF
mode whether to send any PACKET UPLINK DUMMY CONTROL BLOCK message, when there is no
other RLC/MAC block ready to send for this TBF. This parameter is broadcasted to the MS
in (PACKET) SYSTEM INFORMATION message.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Modification of this element is not allowed when Extended
Uplink TBF feature is restricted.

Syntax

Change command string

chg_element ext_utbf_nodata <value> <location> <cell_desc>

chg_cell_element ext_utbf_nodata <value> <cell_desc_opt>

Display command string

disp_cell ext_utbf_nodata <cell_id> [full]

disp_element ext_utbf_nodata <location> <cell_desc>

Copy command strings

copy_cell <source_cell_id> <dest_gsm_cell_id> <dest_location> <dest_bsic>

[cell_name]

68P02901W23-T 6-303
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 The mobile station sends a PACKET UPLINK DUMMY
CONTROL BLOCK during extended uplink mode.
1 The mobile station refrains sending a PACKET UPLINK
DUMMY CONTROL BLOCK during extended uplink mode.
Default value 0

6-304 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference extended_paging_active

extended_paging_active

Description

The extended_paging_active parameter enables or disables extended paging.

When enabled, the BTS sends pages to an MS in its extended page group when all pages could
not be transmitted in the designated page group for the MS. The MS must receive and analyze
messages for its paging group and the group two paging blocks later.

When disabled, extended page is not allowed.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element extended_paging_active <value> <location> <cell_desc>

chg_cell_element extended_paging_active <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element extended_paging_active <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-305
Jan 2010
References Chapter 6: CM database parameters

References

GSM specifications 4.08 - 3.3.2.1; 10.5.2.26

5.02 - 3.3.2a, b, c: ccch_conf, bs_cc_chans, bs_ccch_comb
5.02 - 6.5.1 (iii) to (vi): ccch groups, paging groups
5.02 - 6.5.2, 6.5.3: determination of ccch_group,
paging_group, paging multiframe, paging block index
5.02 - Figure 8, example of TDMA frame mapping for
control channels.
This is a Motorola defined parameter.

6-306 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference extuplinkOpt

extuplinkOpt

Description

The extuplinkOpt parameter indicates whether the Extended Uplink TBF feature functionality
is unrestricted in the BSS software.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The extuplinkOpt flag is unrestricted only if GPRS is
unrestricted.

NOTE
The extuplinkOpt parameter is a flag, and so is read-only and cannot be modified.

Values

Value type Boolean

Valid range 0 or 1
0 Restricted
1 Unrestricted

Default value N/A

68P02901W23-T 6-307
Jan 2010
fdd_multirat_reporting Chapter 6: CM database parameters

fdd_multirat_reporting

Description

The fdd_multirat_reporting parameter specifies the number of UTRAN Frequency Division

Duplex (FDD) cells that is included in the list of strongest cells in the measurement report.
The fdd_multirat_reporting parameter is sent to a mobile in the Measurement Information
message.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Enhanced 2G/3G Handover feature must be
unrestricted to modify this parameter.

Syntax

Change command strings

chg_element fdd_multirat_reporting <value> <location> <cell_desc>

chg_cell_element fdd_multirat_reporting <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element fdd_multirat_reporting <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 3
Default value 1

6-308 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference fdd_gprs_qoffset

fdd_gprs_qoffset

Description

The fdd_gprs_qoffset parameter specifies an offset to RLA_P for cell reselection to access
technology/mode FDD.

The fdd_gprs _qoffset parameter is configurable on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH feature must be unrestricted.
If the local_maintenance flag is disabled the MMI is
prevented from changing this item

Syntax

Change command strings

chg_element fdd_gprs_qoffset <value> <location> <cell_desc>

chg_cell_element fdd_gprs_qoffset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element fdd_gprs_qoffset <location> <cell_desc>

68P02901W23-T 6-309
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (1 step =4 dB)

Valid range 0 to 15
0 infinity (always select a cell if acceptable)
1 28 dB
... ...
8 0 dB
... ...
15 28 dB
Default value 8

6-310 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference fdd_qmin

fdd_qmin

Description

The fdd_qmin parameter is used in the cell reselection algorithm that is implemented by the
multi-RAT MS in Inter-RAT (Inter-Radio Access Technology) handovers.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The BSS Inter-RAT feature must be unrestricted.

Syntax

Change command strings

chg_element fdd_qmin <value> <location> <cell_desc>

chg_cell_element fdd_qmin <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element fdd_qmin <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 7
Default value 7

68P02901W23-T 6-311
Jan 2010
fdd_qoffset Chapter 6: CM database parameters

fdd_qoffset

Description

The fdd_qoffset parameter is followed by the multi-RAT MS in the cell reselection algorithm
that it follows.

The fdd_qoffset parameter is configurable on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The BSS Inter-RAT feature must be unrestricted.

Syntax

Change command strings

chg_element fdd_qoffset <value> <location> <cell_desc>

chg_cell_element fdd_qoffset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element fdd_qoffset <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 15
Default value 8

6-312 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference fdd_rep_quant

fdd_rep_quant

Description

The fdd_rep_quant parameter defines the reporting quantity of the UTRAN Frequency Division
Duplex (FDD) neighbor in the uplink measurement report. The fdd_rep_quant parameter is
sent to a mobile in the Measurement Information message.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Enhanced 2G/3G Handover feature must be
unrestricted to modify this parameter.

Syntax

Change command strings

chg_element fdd_rep_quant <value> <location> <cell_desc>

chg_cell_element fdd_rep_quant <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element fdd_rep_quant <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 RSCP (Received Signal Code Power)
1 Ec/No (Ratio of Chip Energy to Power Spectral
Density)
Default value 1

68P02901W23-T 6-313
Jan 2010
fer_meas_period Chapter 6: CM database parameters

fer_meas_period

Description

The fer_meas_period parameter allows the customer to configure the FER measuring period
parameter. The value indicates the multiple of 24 speech frames that is used as the measuring
period of FER family statistics.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command strings

chg_element fer_meas_period <value> <location>

Display command strings

disp_element fer_meas_period <location>

Values

Value type Integer

Valid range 0 to 255 0 To disable the feature, use 24 speech frames as
the measuring period of FER family statistics.

1~255 Multiple of 24 speech frames used as the

measuring period of FER family statistics.
Default value 0

6-314 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference fieldeng_always _enabled

fieldeng_always _enabled

Description

The fieldeng_always_enabled parameter specifies whether the field engineering accounts can
be used when the OML link is up and down or only when the OML link is down. Essentially it
indicates if field engineering accounts can be used for login when the OML link is up.

This element can be accessed and updated both in and out of sysgen mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Add/Change command string

chg_element fieldeng_always_enabled <value> 0

Display command string

disp_element fieldeng_always_enabled 0

Values

Value type Boolean

Valid range 0 or 1
0 fieldengX accounts can be used only when the OML link is
down.
1 fieldengX accounts can be used when the OML link is up
or down.
Default value 1

68P02901W23-T 6-315
Jan 2010
force_hr_usage Chapter 6: CM database parameters

force_hr_usage

Description

The force_hr_usage parameter enables or disables the capacity to override MSC provided
preference and force Half Rate usage for all Half Rate capable calls within a BSS. This covers
both initial setup and handover.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The AMR feature and/or the GSM Half Rate feature must
be unrestricted.

Syntax

Add/Change command string

chg_element force_hr_usage <value> <location>

Display command string

disp_element force_hr_usage <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-316 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference free_run_enabled

free_run_enabled

Description

The free_run_enabled parameter enables or disables the hardware configuration Free Run
Mode.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies No
Operator actions All the DRI's in this site are affected when the
free_run_enabled parameter is enabled.
This parameter cannot be displayed and changed on
RXCDR site.

Syntax

Add/Change command string

chg_element free_run_enabled <value> <location>

Display command string

disp_element free_run_enabled <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

NOTE
Manually reset the DRIs to disable Free Run Mode.

68P02901W23-T 6-317
Jan 2010
frequency_type Chapter 6: CM database parameters

frequency_type

Description

The frequency_type parameter specifies the frequency type of a cell.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies If the Infrastructure Sharing Homogeneous Cabinet feature
is not enabled, the frequency_type for every cabinet and
cell at a site must be the same.
If the Infrastructure Sharing Homogeneous Cabinet feature
is enabled, but the Infrastructure Sharing Heterogeneous
feature is disabled, the cells at a site must have the same
single frequency type as the cabinet they correlate to.
However, the cabinets at the site may be of different
frequency types.
If both the Infrastructure Sharing Homogeneous Cabinet
feature and the Infrastructure Sharing Heterogeneous
feature are enabled, the cells at a site may have different
frequency types and cabinets may support multiple
frequency types. However, the cell frequency must be
supported by the cabinet the cell is correlated to.
If inner_zone_alg is set to indicate Dual Band Cells, the
following two dependencies are enforced:
(1) if secondary_freq_type is set to EGSM or PGSM, the
frequency_type may be set only to DCS1800;
(2) if secondary_freq_type is DCS1800, frequency_type
may be set only to PGSM or EGSM.
Cell and cabinet frequency types must be allowed at the
BSS as per the freq_types_allowed command.
The frequency_type of a cell may be changed to PCS1900
inside Sysgen mode.
If the value of tx_power_cap is set to 0 (indicating a low
power cell), and radios have already been associated with
the cell, a warning message is issued to the operator.
The cabinet frequency_type database parameter must
specify a single band for the 4 branch receive density
feature.
The BSS rejects an attempt to leave Sysgen mode when the
value of the tx_power_cap parameter is 0 for cells residing
on a Horizonmacro or Horizonmacro extension cabinet
which have a frequency type of PCS1900 and have no radio
resources allocated to the cell.
Operator actions Put the system into SYSGEN mode to change the
frequency_type parameter.

6-318 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

Syntax

Add/Change command strings

add_cell <gsm_cell_desc> <location

The add_cell command accepts either numeric values or text strings for frequency_type.

chg_cell_element frequency_type <value> <cell_desc_opt>

The chg_cell_element command accepts only numeric values for frequency_type.

Display command strings

disp_cell <cell_id> [full]

disp_element frequency_type <location> <cell_desc>

Values

Value type Integer Text

Valid range 1 pgsm
2 egsm
4 dcs1800
8 pcs1900
Default value None

NOTE
Horizon II and Horizon II extension cabinets support frequency types 1, 2, 4 and 6.

68P02901W23-T 6-319
Jan 2010
full_pwr_rfloss Chapter 6: CM database parameters

full_pwr_rfloss

Description

The full_pwr_rfloss parameter enables or disables the ability of the BSS power control to fully
power up the MS and BTS at the point where the RF connection appears to be lost.

When enabled, the transition to full power occurs when the threshold set by link_about_to_fail
is reached in the link_fail procedure.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id>

chg_element full_pwr_rfloss <value> <location> <cell_desc>

chg_cell_element full_pwr_rfloss <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element full_pwr_rfloss <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-320 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gateway

gateway

{26638}

Description

The gateway parameter identifies the default gateway for the PCU Ethernet GBL.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the Gb over IP
feature is unrestricted and the Gb mode is set to static IP
mode.

Syntax

Equip command strings

equip <location> gbl

Unequip command strings

unequip <location> gbl <gbl id>

Display command strings

disp_equipment <location> gbl <gbl id>

Modify command strings

modify_value pcu gateway <value> gbl <gbl id>

68P02901W23-T 6-321
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0.0.0.0 to 223.255.255.255
128.0.0.0 to Minimum
223.255.255.255
0 to 126.255.255.255 Maximum
Default value N/A

NOTE

The address 0.0.0.0 means no default gateway is in use.

The gateway and the ip_address should be in the same subnet, (defined by
the subnet_mask).
The gateway address should not be the same as the ip_address.

6-322 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gb_mode

gb_mode

{26638}

Description

The gb_mode parameter indicates whether the Gb over IP feature is enabled. This parameter
may be changed inside and outside SYSGEN mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified if the Gb over IP feature is
unrestricted and no GBL objects exist.

Syntax

Change command string

chg_element gb_mode <value> 0

Display command string

disp_element gb_mode 0

Values

Value type Boolean

Valid range 0 Frame relay mode.
1 Static IP mode.
Default value 0

68P02901W23-T 6-323
Jan 2010
GboIPOpt Chapter 6: CM database parameters

GboIPOpt

{26638}

Description

The GboIPOpt parameter indicates whether the Gb over IP feature is unrestricted in the BSS
software.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Display command string

disp_options

Values

Value type Boolean

Valid range 0
1
Default value N/A

6-324 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gci_error_clr_thresh

gci_error_clr_thresh

Description

The gci_error_clr_thresh parameter specifies the error count threshold (equal to or less than)
for an alarm to be cleared for a GPRS Circuit Identifier (GCI).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS and ECERM features must be unrestricted.
Two successful GPRS alarm increment time periods must
elapse without a sync loss error to clear an alarm within
this threshold. (One successful GPRS alarm increment
time period may be too short for the Channel Coder Unit
(CCU) to send an error indication, thus clearing the alarm
prematurely.)
This parameter can be set only at a BSC.
If the threshold is increased during operation, any existing
counts between the new and the old threshold does not
clear an alarm until the next successful time period occurs.

Syntax

Change command string

chg_element gci_error_clr_thresh <value> 0

Display command string

disp_element gci_error_clr_thresh 0

Values

Value type Integer

Valid range 0 to 253
Default value 0

68P02901W23-T 6-325
Jan 2010
gci_error_gen_thresh Chapter 6: CM database parameters

gci_error_gen_thresh

Description

The gci_error_gen_thresh parameter specifies the error count threshold (equal to or greater
than) for an alarm to be generated for a GPRS Circuit Identifier (GCI).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS and ECERM features must be unrestricted.
This parameter can be set only at a BSC.
If the threshold is changed during operation, no immediate
alarm occurs. The new threshold takes effect only when
the GCI error count changes.

Syntax

Change command string

chg_element gci_error_gen_thresh <value> 0

Display command string

disp_element gci_error_gen_thresh 0

Values

Value type Integer

Valid range 2 to 255
Default value 6

6-326 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gci_error_inc

gci_error_inc

Description

The gci_error_inc parameter specifies the error count increment when the Enhanced Circuit
Error Rate Monitor (ECERM) feature is in use for GPRS Circuit Identifiers (GCIs) on a per
BSC basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS and ECERM features must be unrestricted.
This parameter can be set only at a BSC.

Syntax

Change command string

chg_element gci_error_inc <value> 0

Display command string

disp_element gci_error_inc 0

Values

Value type Integer

Valid range 0 GCI alarms not raised.
1 to 255 GCI alarms raised.
Default value 0 If ECERM feature is restricted.
1 If ECERM feature is not restricted.

68P02901W23-T 6-327
Jan 2010
gclk_24_alarm_enable Chapter 6: CM database parameters

gclk_24_alarm_enable

Description

The gclk_24_alarm_enable parameter indicates whether the GCLK [24] alarm in the BSC
and RXCDR is enabled or disabled. The parameter can be accessed only from the BSS (BSC
and RXCDR), OMC, and DATAGEN.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element gclk_24_alarm_enable <change value> 0

Display command string

disp_element gclk_24_alarm_enable 0

Values

Value type Boolean

Valid range 0 or 1
0 Disable GCLK [24] alarm
1 Enable GCLK [24] alarm
Default value 1

6-328 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gclk_24_high_threshold

gclk_24_high_threshold

Description

The gclk_24_high_threshold parameter indicates the upper threshold of the DAC register
value. If the DAC register value is out of the configurable threshold (that is, if the
gclk_24_low_threshold is the lower threshold and the gclk_24_high_threshold is the upper
threshold) in one hour, the GCLK 24 alarm is reported. This parameter is supported on the
BSC and RXCDR.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The parameter is applicable only at Site 0.

Syntax

Change command string

chg_element gclk_24_high_threshold <value> 0

Display command string

disp_element gclk_24_high_threshold 0

Values

Value type Integer

Valid range 128 to 255
Default value 200

68P02901W23-T 6-329
Jan 2010
gclk_24_low_threshold Chapter 6: CM database parameters

gclk_24_low_threshold

Description

The gclk_24_low_threshold parameter indicates the lower threshold of the DAC register
value. If the DAC register value is out of the configurable threshold (that is, if the
gclk_24_low_threshold is the lower threshold and the gclk_24_high_threshold is the upper
threshold) in one hour, the GCLK 24 alarm is reported. This parameter is supported on the
BSC and RXCDR.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The parameter is applicable only at Site 0.

Syntax

Change command string

chg_element gclk_24_low_threshold <value> 0

Display command string

disp_element gclk_24_low_threshold 0

Values

Value type Integer

Valid range 0 to 127
Default value 56

6-330 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gclk_qwarm_flag

gclk_qwarm_flag

Description

The gclk_qwarm_flag parameter specifies the amount of time required by the active GCLK to
warm up. It has no effect on the standby GCLK.

If this parameter is disabled, the active GCLK requires 30 minutes.

If this parameter is enabled and the active GCLK is of version 9 or later, the software overrides
the hardware timer on the active GCLK and brings it into services after 15 minutes. This time
period begins when the site is initialized.

This parameter is only valid for GCLK boards.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Fast GCLK Warmup feature must be unrestricted.
The GCLK version must be V9 or later.

Syntax

Change command string

chg_element gclk_qwarm_flag <value> <location>

Display command string

disp_element gclk_qwarm_flag <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-331
Jan 2010
global_reset_repetitions Chapter 6: CM database parameters

global_reset_repetitions

Description

The global_reset_repetitions parameter allows the Reset message to be sent indefinitely

if Reset Ack is not received, or stops sending the Reset message after a fixed number of
repetitions. The global reset procedure repeats is only if the MSC fails to acknowledge the BSS.
After the fixed number of repetitions, an alarm is generated.

If the value is set to 0, the global reset message repeats continuously until a Reset Ack is
received.

If the value is set to a value greater than 0, the global reset message repeats the number of
times entered and the alarm: No MSC Acknowledgment for Global Reset is generated.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter does not apply to RXCDR sites.
This parameter applies to only BSC sites.

Syntax

Change command string

chg_element global_reset_repetitions <value> 0

Display command string

disp_element global_reset_repetitions 0

Values

Value type Integer (number of repetitions)

Valid range 0 to 255
Default value 0

6-332 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM specification TS GSM 8.08

This is a Motorola defined parameter.

68P02901W23-T 6-333
Jan 2010
gmsk_capability_mode Chapter 6: CM database parameters

gmsk_capability_mode

{34452}

Description

The gmsk_capability_mode parameter is used for configuration of the PRM detect mode
for the GMSK block. This parameter can be accessed and updated both in and out of sysgen
mode without warning.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the EGPRS
feature is enabled.

Syntax

Change command string

chg_element gmsk_capability_mode <value> <location>

Display command string

disp_element gmsk_capability_mode <location>

Values

Value type Integer

Valid range 0 to 2
0 The PRM assumes that all the GPRS mobiles are capable
of decoding the GMSK blocks in the download direction,
and sends the USF to all the GPRS mobiles.
1 The PRM assumes that all the GPRS mobiles are incapable
of decoding GMSK blocks, and does not send USFs to the
GPRS mobiles on GMSK blocks.

6-334 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

2 The PRM applies the detection mechanism and detects the

existence of faulty GPRS mobiles in the network. When
faulty GPRS mobiles are interleaved with EGPRS mobiles
on the downlink direction, the PRM does not send USFs to
the faulty mobiles on GMSK blocks.
Default value 0

68P02901W23-T 6-335
Jan 2010
gproc_slots Chapter 6: CM database parameters

gproc_slots

Description

The gproc_slots parameter specifies the number of timeslots to be allocated to all GPROCs for
the TDM highway. It is possible to configure different functions on each of the 32 channels. The
system supports 16 or 32 timeslots for assignment to the TDM highway.

The BSS supports a value of 24 for this parameter on the BSC. If set to 24, at least one GPROC
is equipped after all the MSIs are equipped, so that 12 MSIs and 8 GPROCs can be brought
into service.

This parameter is not allowed at M-Cell sites.

Type B (operator actions required)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter may not be modified if any BSP, BTP, DHP,
GPROC, or MSI is equipped.
Operator actions This parameter may only be modified in initial SYSGEN
mode.

Syntax

Change command string

chg_element gproc_slots <value> <location>

Display command string

disp_element gproc_slots <location>

6-336 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 16, 24 or 32
16 16 TDM timeslots
24 24 TDM timeslots (BSC only)
32 32 TDM timeslots (only valid with GPROC2 and GPROC3
boards)
Default value 16

NOTE
If gproc_slots is greater than 16, the system displays the following warning:
COMMAND ACCEPTED: WARNING: Specified value requires GPROC2 or GPROC3
boards.

68P02901W23-T 6-337
Jan 2010
gprs_alarm_time Chapter 6: CM database parameters

gprs_alarm_time

Description

The gprs_alarm_time parameter identifies the time period in which error counters are
either: incremented if an error indication is received for a GPRS Circuit Identifier (GCI), or
decremented if no error indication is received.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS and ECERM features must be unrestricted.
This parameter applies to only BSC sites.

Syntax

Change command string

chg_element gprs_alarm_time <value> 0

Display command string

disp_element gprs_alarm_time 0

Values

Value type Integer

Valid ranges 0 If GPRS or ECERM is restricted (effectively equivalent to
gprs_alarm_time parameter turned off).
5 to 240 If GPRS and ECERM features are unrestricted.
Default values 0 If GPRS or ECERM are restricted.
60 If GPRS and ECERM features are unrestricted.

6-338 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_asym_mismatch_delta

gprs_asym_mismatch_delta

{34452}

Description

The gprs_asym_mismatch_delta parameter sets the weight factor between the GPRS only
mobile and the GMSK UL restricted carrier. This makes the GPRS only capable mobile prefer
the GMSK UL restricted carrier over the fully EDGE capable carrier. As a result, the full EDGE
carrier is reserved for the EDGE capable mobile. This parameter can be accessed and updated
both in and out of sysgen mode.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter can be modified only when the CTU2-D
asymmetric feature and the GPRS feature are unrestricted,
and the asym_edge_enabled parameter is enabled.

Syntax

Change command string

chg_cell_element gprs_asym_mismatch_delta <value> <cell_desc>

chg_element gprs_asym_mismatch_delta <value> <location> <cell_desc>

Display command string

disp_element gprs_asym_mismatch_delta <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 100
0 Minimum
100 Maximum
Default value 10

68P02901W23-T 6-339
Jan 2010
gprs_bs_cv_max Chapter 6: CM database parameters

gprs_bs_cv_max

Description

The gprs_bs_cv_max specifies the maximum count down value a mobile can use for uplink
RLC data transfer. The MS sends a count down value in each uplink RLC data block starting
gprs_bs_cv_max blocks from the last block. The value sent is decremented by one in each
subsequent block. This allows the network to identify the last RLC block in the uplink TBF.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_bs_cv_max <value> <location> <cell_desc>

chg_cell_element gprs_bs_cv_max <value> <cell_desc_opt>

Display command string

disp_element gprs_bs_cv_max <location> <cell_desc>

Values

Value type Integer (blocks)

Valid range 0 to 15
Default value 8

6-340 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_cell_reselect_hysteresis

gprs_cell_reselect_hysteresis

Description

The gprs_cell_reselect_hysteresis parameter specifies the additional hysteresis level that

applies in the ready state for cells in the same Routing Area (RA).

Differences in received signal levels from 0 dB to 14 dB (in 2 dB increments) are used for
cell reselection.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Add/Change command strings

chg_element gprs_cell_reselect_hysteresis <value> <location> <cell_desc>

chg_cell_element gprs_cell_reselect_hysteresis <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_cell_reselect_hysteresis <location> <cell_desc>

68P02901W23-T 6-341
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 7 Represents the signal level differences:
0 0 dB
1 2 dB
2 4 dB
3 6 dB

4 8 dB
5 10 dB
6 12 dB
7 14 dB
Default value 0 (0 dB)

6-342 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_com_ms_class

gprs_com_ms_class

Description

The gprs_com_ms_class parameter specifies the Most Common Multislot Class of GPRS
mobiles. The four possible values represent the following:

1 - multislot class 1.

2 - multislot class 2, 3, 5.

4 - multislot class 4, 6, 7.

8 - multislot class 8 to 29.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

Syntax

Change command strings

chg_element gprs_com_ms_class <value> <location>

Display command strings

disp_element gprs_com_ms_class <location>

Values

Value type Integer

Valid range 1, 2, 4 and 8
Default value 8

68P02901W23-T 6-343
Jan 2010
gprs_cr_margin Chapter 6: CM database parameters

gprs_cr_margin

Description

The gprs_cr_margin parameter specifies the threshold at which a Packet Measurement Report
(PMR) received from the MS is considered as bad by the network. A bad PMR is one in which
the difference between the serving cells rxlev and the serving cells value of rxlev_access_min
is less than the gprs_cr_margin.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Network Controlled Cell Reselection (NCCR) feature
must be unrestricted.
The parameter can be changed in or out of SYSGEN mode.
Settings are copied by the copy_cell command.

NOTE
PCU software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command string

chg_element gprs_cr_margin <value> <location> <cell_desc>

chg_cell_element gprs_cr_margin <value> <cell_desc_opt>

Display command string

disp_element gprs_cr_margin <location> [<cell_id>]

disp_cell <cell_id> full

6-344 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid ranges 5 to 40 dB
Default values 30 dB

References

GSM parameter None

This is a Motorola defined parameter.

68P02901W23-T 6-345
Jan 2010
gprs_dl_pwr_mode Chapter 6: CM database parameters

gprs_dl_pwr_mode

Description

The gprs_dl_pwr_mode parameter specifies the downlink power control mode that the PCUs
use to broadcast data blocks to the MS. It is a per BSC parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.
This parameter can be set to a value of 1 (mode A).
This parameter cannot be set to 2 (mode B) when
gprs_mac_mode is set to 1 (dynamic mode).

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_dl_pwr_mode <value> bsc

Display command string

disp_element gprs_dl_pwr_mode bsc

6-346 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 2
0 No power mode
1 Mode A
2 Mode B
Default value 1

68P02901W23-T 6-347
Jan 2010
gprs_drx_timer_max Chapter 6: CM database parameters

gprs_drx_timer_max

Description

The gprs_drx_timer_max parameter specifies the maximum timer value allowed for the MS to
request for non-DRX mode after packet transfer mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_drx_timer_max <value> <location> <cell_desc>

chg_cell_element gprs_drx_timer_max <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_drx_timer_max <location> <cell_desc>

Values

Value type Integer (seconds)

Valid range 0 to 3
Default value 0

6-348 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_edge_mismatch_sigma

gprs_edge_mismatch_sigma

{34452}

Description

The gprs_edge_mismatch_sigma parameter sets the weight factor which indicates the
possibility of the EDGE mobile to be allocated on the GPRS carrier, or the GPRS mobile to
be allocated on the EDGE carrier. This parameter can be accessed and updated both in and
out of sysgen mode.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter can be modified only when the GPRS
feature is enabled.

Syntax

Change command string

chg_cell_element gprs_edge_mismatch_sigma <value> <cell_desc>

chg_element gprs_edge_mismatch_sigma <value> <location> <cell_desc>

Display command string

disp_element gprs_edge_mismatch_sigma <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 100
0 Minimum
100 Maximum
Default value 60

68P02901W23-T 6-349
Jan 2010
Values Chapter 6: CM database parameters

NOTE
A larger value indicates that the GPRS carrier is preferred to the EDGE mobile, and
the EDGE carrier is preferred to the GPRS mobile.

6-350 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_enabled

gprs_enabled

Description

The gprs_enabled parameter specifies whether GPRS is unrestricted at a cell.

The gprs_supported broadcast parameter describes the GPRS configuration of a cell. The BSS
implements this as two cell elements: gprs_enabled and pcch_alloc.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.
At least one PCU must be equipped. A prompt requests the
primary PCU ID.
max_gprs_pdch must be set to a non-zero-value.
At least one nsvc must be associated with a GBL.
The nsei parameter must be configured by the operator.
A PSP and the default GSL must be equipped at the PCU/s.
A routing area color must have been configured for the
cell; see the ra_color parameter in ra_color on page
6-754 description.
The RAC parameter must be set.
If pccch_enabled is set to 1 (enabled) and the operator
attempts to set gprs_enabled to 1, the command is
rejected if there is no reserved Packet Data Channel
(PDCH) timeslot in the same cell. There must be at least
one.
Operator actions Before this parameter can be set, the operator must have
set gprs_sig_bvci parameter (see gprs_sig_bvci on page
6-382) using the chg_element command.

NOTE

BSS software processes using this parameter are immediately notified when the
change is made.
When an attempt is made to change gprs_enabled, and the requested PDTCHs
exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and
issues a warning to indicate that there is not enough GDS or PMC resource
available.

68P02901W23-T 6-351
Jan 2010
Syntax Chapter 6: CM database parameters

Syntax

Change command string

chg_cell_element gprs_enabled <value> <cell-desc_opt>

chg_cell_element <location> gprs_enabled <value> all

Display command string

disp_element gprs_enabled <location> <cell-desc>

disp_element gprs_enabled <location> all

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-352 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_intraho_allwd

gprs_intraho_allwd

Description

The gprs_intraho_allwd parameter specifies whether the BSS performs intra-cell handovers
to free GPRS timeslots currently in use for circuit traffic. Such handovers recover PDTCHs
which have been switched to TCHs.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.
An intra-cell handover is performed only if the
number of idle TCHs (including circuit switch and
switchable TCHs) is greater than the value set for the
gprs_reconfig_thresh_idle_tch parameter.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_intraho_allwd <value> <location> <cell_desc>

chg_cell_element gprs_intraho_allwd <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element gprs_intraho_allwd <location> <cell_desc>

68P02901W23-T 6-353
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

6-354 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_mac_mode

gprs_mac_mode

Description

The gprs_mac_mode parameter specifies the medium access mode to be used by the PCUs.

Only the dynamic access mode is available.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_mac_mode <value> bsc

Display command string

disp_element gprs_mac_mode bsc

Values

Value type Boolean

Valid range 1 Dynamic mode
2 Extended dynamic allocation
Default 1

68P02901W23-T 6-355
Jan 2010
gprs_min_prr_blks Chapter 6: CM database parameters

gprs_min_prr_blks

Description

The gprs_min_prr_blks parameter specifies the minimum number of dynamic PRR blocks
created per cell and measured over four multiframes.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Modification of gprs_min_prr_blks has no effect for cells
that have the pccch_enabled parameter enabled.
GPRS must be unrestricted.

Syntax

Change command strings

chg_element gprs_min_prr_blks <value> <location> <cell_desc>

chg_cell_element gprs_min_prr_blks <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_min_prr_blks <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 24
Default value 0

6-356 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_ms_pan_dec

gprs_ms_pan_dec

Description

The gprs_ms_pan_dec parameter specifies the amount by which to decrement the MS counter
n3102. The MS counter n3102 counts the number of uplink acks/nacks received by the MS.
When an uplink ack/nack is received, n3102 is incremented by gprs_ms_pan_inc. n3102 never
exceeds gprs_ms_pan_max. Each time the preset internal timer T3182 expires, n3102 is
decremented by gprs_ms_pan_dec. T3182 defines how long the mobile waits for an uplink
ack/nack. If n3102 decrements to zero, then the MS performs an abnormal cell reselection
procedure as defined in the GSM standard referred to in this description.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_ms_pan_dec <value> <location> <cell_desc>

chg_cell_element gprs_ms_pan_dec <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_ms_pan_dec <location> <cell_desc>

68P02901W23-T 6-357
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 7
Default value 1

References

GSM parameter None

This is a Motorola defined parameter.
GSM technical specification 04.60

6-358 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_ms_pan_inc

gprs_ms_pan_inc

Description

The gprs_ms_pan_inc parameter specifies the amount by which to increment the MS counter
n3102. The MS counter n3102 counts the number of uplink acks/nacks received by the MS.
When an uplink ack/nack is received, n3102 is incremented by gprs_ms_pan_inc. n3102 never
exceeds gprs_ms_pan_max. Each time the preset internal timer T3182 expires, n3102 is
decremented by gprs_ms_pan_dec. T3182 defines how long the mobile waits for an uplink
ack/nack. If n3102 decrements to zero, then the MS performs an abnormal cell reselection
procedure as defined in the GSM standard referred to in this description.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_ms_pan_inc <value> <location> <cell_desc>

chg_cell_element gprs_ms_pan_inc <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_ms_pan_inc <location> <cell_desc>

68P02901W23-T 6-359
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 7
Default value 1

References

GSM parameter None

This is a Motorola defined parameter.
GSM specification 04.60

6-360 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_ms_pan_max

gprs_ms_pan_max

Description

The gprs_ms_pan_max parameter specifies the maximum value of the MS counter n3102.
The MS counter n3102 counts the number of uplink acks/nacks received by the MS. When an
uplink ack/nack is received, n3102 is incremented by gprs_ms_pan_inc. n3102 never exceeds
gprs_ms_pan_max. Each time the preset internal timer T3182 expires, n3102 is decremented
by gprs_ms_pan_dec. T3182 defines how long the mobile waits for an uplink ack/nack. If
n3102 decrements to zero, then the MS performs an abnormal cell reselection procedure as
defined in the GSM standard referred to in this description.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_ms_pan_max <value> <location> <cell_desc>

chg_cell_element gprs_ms_pan_max <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_ms_pan_max <location> <cell_desc>

68P02901W23-T 6-361
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 7
Default value 3

References

GSM parameter None

This is a Motorola defined parameter.
GSM technical specification 04.60

6-362 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_ms_txpwr_max_cch

gprs_ms_txpwr_max_cch

Description

The gprs_ms_txpwr_max_cch parameter specifies the maximum random access power

available for an MS on a packet control channel (pccch or pbcch) in a cell. This parameter is
expressed as a power level value.

Before accessing a cell on the PRACH and before receiving the first power command during a
communication on a BCCH (or TCH), the MS uses one of two possible power levels.

The MS uses the lower power level of the two available: either the gprs_ms_txpwr_max_cch
broadcast on the BCCH or the maximum transmit power as defined by the power class of the MS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The cell frequency_type.
The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Add/Change command strings

chg_element gprs_ms_txpwr_max_cch <value> <location> <cell_desc>

chg_cell_element gprs_ms_txpwr_max_cch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_ms_txpwr_max_cch <location> <cell_desc>

68P02901W23-T 6-363
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 31 For PGSM, EGSM and GSM850 cells in 2 dBm steps as
shown in Table 6-12:
2 to 28 For DCS1800 cells in 2 dBm steps as shown in Table 6-13:
0 to 15, 30 For PCS1900 cells as shown in Table 6-14:
and 31
Default value 2 (For PGSM, EGSM and GSM850 cells).
0 (For DCS1800 cells).
30 (For PCS1900 cells).

Table 6-12 Maximum mobile power level for PGSM, EGSM and GSM850 cells

Value Power level Value Power level

0 to 2 39 dBm 11 21 dBm
3 37 dBm 12 19 dBm
4 35 dBm 13 17 dBm
5 33 dBm 14 15 dBm
6 31 dBm 15 13 dBm
7 29 dBm 16 11 dBm
8 27 dBm 17 9 dBm
9 25 dBm 18 7 dBm
10 23 dBm 19 to 31 5 dBm

Table 6-13 Maximum mobile power level for DCS1800 cells

Value Power level Value Power level

0 30 dBm 8 14 dBm
1 28 dBm 9 12 dBm
2 26 dBm 10 10 dBm
3 24 dBm 11 8 dBm
4 22 dBm 12 6 dBm
5 20 dBm 13 4 dBm
6 18 dBm 14 2 dBm
7 16 dBm 15 to 28 0 dBm

6-364 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Table 6-14 Maximum mobile power level for PCS1900 cells

Value Power level Value Power level

30 33 dBm 7 16 dBm
31 32 dBm 8 14 dBm
0 30 dBm 9 12 dBm
1 28 dBm 10 10 dBm
2 26 dBm 11 8 dBm
3 24 dBm 12 6 dBm
4 22 dBm 13 4 dBm
5 20 dBm 14 2 dBm
6 18 dBm 15 0 dBm

68P02901W23-T 6-365
Jan 2010
gprs_network_operation_mode Chapter 6: CM database parameters

gprs_network_operation_mode

Description

The gprs_network_operation_mode parameter specifies whether a GPRS is present between

the MSC and the SGSN. It is a per BSC parameter. Table 6-15 shows the two permissible modes.

Table 6-15 Modes for gprs_network_operation_mode

Mode Description
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. This means that the MS
need only monitor one paging channel and that it receives CS pages on a
PDTCH when it is in transfer mode.
3 The network sends CS pages for a GPRS attached MS on the CCCH and PS
pages of the PCCCH, if allocated. This means that an MS must monitor both
the CCH for CS pages and PCCH for PS pages. No paging coordination is done
by the network.

NOTE
The gprs_network_operation_mode can be set to either 1 or 3. When set to 3,
the actual value of corresponding SYS13 (PSYS13) field depends on PCCCH being
enabled or not. If not, the system broadcasts Network Mode Operation 2.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately the change
is made.

6-366 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

Syntax

Change command string

chg_element gprs_ network_operation_mode <value> bsc

Display command string

disp_element gprs_network_operation_mode bsc

Values

Value type Integer

Valid range 1 or 3
1 Mode 1
3 Mode 3
Default value 3

68P02901W23-T 6-367
Jan 2010
gprs_num_pmrs Chapter 6: CM database parameters

gprs_num_pmrs

Description

The gprs_num_pmrs parameter specifies the number of bad Packet Measurement Reports
(PMRs) from the MS at which the PCU performs network controlled cell reselection.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Network Controlled Cell Reselection (NCCR) feature
must be unrestricted.
The parameter can be changed in or out of SYSGEN mode.
Settings are copied by the copy_cell command.

NOTE
PCU software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command string

chg_element gprs_num_pmrs <value> <location> <cell_desc>

chg_cell_element gprs_num_pmrs <value> <cell_desc_opt>

Display command string

disp_element gprs_num_pmrs <location> [<cell_id>]

disp_cell gprs_num_pmrs <cell_id> full

6-368 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid ranges 1 to 10 Number of bad PMRs.
Default values 3

References

GSM parameter None

This is a Motorola defined parameter.

68P02901W23-T 6-369
Jan 2010
gprs_par_wait_ind Chapter 6: CM database parameters

gprs_par_wait_ind

Description

The gprs_par_wait_ind parameter specifies the GPRS Packet Access Reject (PAR) period of a
cell, that is, how long the mobile needs to wait before re-RACHing into the cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS must be unrestricted.

NOTE
PCU software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_par_wait_ind <value> <location> <cell_desc>

chg_cell_element gprs_par_wait_ind <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_par_wait_ind <location> <cell_desc>

Values

Value type Integer (20ms block period)

Valid range 100 to 750
Default value 150

6-370 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_pb

gprs_pb

Description

The gprs_pb parameter specifies the power reduction used by the BTS on the BCCH blocks.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_pb <value> <location> <cell_desc>

chg_cell_element gprs_pb <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_pb <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 16
Default value 1

68P02901W23-T 6-371
Jan 2010
gprs_pc_alpha Chapter 6: CM database parameters

gprs_pc_alpha

Description

The gprs_pc_alpha is the system parameter broadcast on the BCCH. It is used as a multiplier
of the power offset in power control calculations. The actual multiplying factor is one-tenth of
the value set in this parameter; that is, if N is the value of this parameter, the multiplying
factor is N/10.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_pc_alpha <value> <location> <cell_desc>

chg_cell_element gprs_pc_alpha <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_pc_alpha <location> <cell_desc>

Values

Value type Integer (Power offset is multiplied by one tenth of this value)
Valid range 0 to 10
Default value 0

6-372 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_pc_meas_chan

gprs_pc_meas_chan

Description

The gprs_pc_meas_chan parameter specifies whether the MS measures the received power
level on the downlink BCCH or PDCH to control the uplink power.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_pc_meas_chan <value> <location> <cell_desc>

chg_cell_element gprs_pc_meas_chan <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_pc_meas_chan <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 BCCH
1 PDCH
Default value 0

68P02901W23-T 6-373
Jan 2010
gprs_reconfig_thresh_idle_tch Chapter 6: CM database parameters

gprs_reconfig_thresh_idle_tch

Description

The gprs_reconfig_thresh_idle_tch parameter specifies the number of idle circuit switched

resources on the GPRS cell that must be exceeded before a timeslot is configured as a
Switchable Packet Data Traffic Channel (PDTCH).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE

BSS software processes using this parameter are notified immediately after the
change is made.
When returning an EGPRS timeslot on a double density CTU2 back
to PDCH, the BTS Cell Resource Manager [CRM] ensures that the
gprs_reconfig_thresh_idle_tch parameter specification is met and the respective
TCHs on carrier A and B are idle, provided the Improved Timeslot Sharing
feature is unrestricted and enabled.

Syntax

Change command strings

chg_element gprs_reconfig_thresh_idle_tch <value> <location> <cell_desc>

chg_cell_element gprs_reconfig_thresh_idle_tch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_reconfig_thresh_idle_tch <location> <cell_desc>

6-374 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 5
Default value 1

68P02901W23-T 6-375
Jan 2010
gprs_reselect_offset Chapter 6: CM database parameters

gprs_reselect_offset

Description

The gprs_reselect_offset parameter specifies a positive or negative offset with hysteresis to

the GPRS cell reselection criterion, for use by the MS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH feature must be unrestricted.

Syntax

Add/Change command strings

chg_element gprs_reselect_offset <value> <location> <cell_desc>

chg_cell_element gprs_reselect_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_reselect_offset <location> <cell_desc>

6-376 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 31 Represents dB values shown below:
0 -52 dB
1 -48 dB
... ...
11 -8 dB
12 -4 dB
... ...

16 0 dB
... ...
20 +4 dB
21 +8 dB
... ...
31 +48 dB
Default value 16 (0 dB)

68P02901W23-T 6-377
Jan 2010
gprs_rxlev_access_min Chapter 6: CM database parameters

gprs_rxlev_access_min

Description

The gprs_rxlev_access_min parameter specifies the minimum received signal level (dBm)
required for an MS to access the system.

The range -110 dBm to -47 dBm is used to set the minimum received signal level which in turn is
used in path loss criterion parameter, C1. This should be set to a value corresponding to a signal
level at which a call can be maintained in a particular environment.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Add/Change command strings

chg_element gprs_rxlev_access_min <value> <location> <cell_desc>

chg_cell_element gprs_rxlev_access_min <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_rxlev_access_min <location> <cell_desc>

6-378 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 dBm)

Valid range 0 to 63 Represents dBm as shown below:
0 -110 dBm and lower
1 -109 dBm
2 -108 dBm
... ...
63 -47 dBm and higher
Default value 0

68P02901W23-T 6-379
Jan 2010
gprs_sched_beta Chapter 6: CM database parameters

gprs_sched_beta

Description

The gprs_sched_betaparameter sets the scheduling beta algorithm at the BSS when the GPRS
feature is unrestricted.

A range error is displayed if an attempt is made to change this parameter to anything other
than 1

Type A (no operator actions)

Supported by OMC-R GUI Yes (Read-Write)
Cell description required No
Dependencies This parameter can only be set to a value of 1.

Syntax

Change command string

chg_element gprs_sched_beta 1 0

Display command string

disp_element gprs_sched_beta 0

6-380 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Value

Value

Value type Integer

Valid range 0 to 2
0 Each MS throughput in bit/s is the same (see NOTE below).
1 THP weighted distribution of overall bandwidth after all
interleaving mobiles have met their MTBR.

NOTE
MTBR is 0 when QoS is disabled.
2 MS with higher coding scheme is preferred (see NOTE
below).
Default value 1

68P02901W23-T 6-381
Jan 2010
gprs_sig_bvci Chapter 6: CM database parameters

gprs_sig_bvci

Description

The gprs_sig_bvci parameter specifies the BVCI of the signaling source used with GBLs.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command string

chg_element gprs_sig_bvci <value> pcu

Display command string

disp_element gprs_sig_bvci pcu

Values

Value type Integer

Valid range 0 to 65535
Default value 0

6-382 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_temporary_offset

gprs_temporary_offset

Description

The gprs_temporary_offset parameter specifies a value used by the MS as part of its

calculation of C32 for the cell reselection process. It is used to apply a negative offset to C32 for
the duration of the gprs_penalty_time parameter.

C32 is the reselection priority assigned to a cell which can be broadcast on the BCCH of each
cell. When more than one cell is available for reselection, the MS reselects the cell with the
highest C32 value.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Add/Change command strings

chg_element gprs_temporary_offset <value> <location> <cell_desc>

chg_cell_element gprs_temporary_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_temporary_offset <location> <cell_desc>

68P02901W23-T 6-383
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 7
0 0 dB
1 10 dB
2 20 dB
3 30 dB
4 40 dB
5 50 dB
6 60 dB
7 Infinity
Default value 0

6-384 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_type5_alg

gprs_type5_alg

Description

The gprs_type5_alg parameter indicates whether the GPRS type-5 microcellular algorithm
is turned on or not.

The following error is displayed and the command rejected if an attempt is made to enable this
parameter when nccr_enabled is disabled:

ERROR: nccr_enabled must be set to 1 before enabling gprs_type5_alg.

COMMAND REJECTED

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies Modification is only allowed when all of the following
conditions are satisfied:

NACC Optional feature is unrestricted

NCCR optional feature is unrestricted

Microcellular optional feature is unrestricted

gprs_type5_alg cannot be set to 1 (enabled) when
nccr_enabled is 0 (disabled).

NOTE
PCU software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gprs_type5_alg <value> <location>

68P02901W23-T 6-385
Jan 2010
Values Chapter 6: CM database parameters

Display command strings

disp_element gprs_type5_alg <location>

Values

Value type Boolean

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0

6-386 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_ts_config_alg

gprs_ts_config_alg

Description

The gprs_ts_config_alg parameter specifies the algorithm used to allocate switchable and
reserved GPRS timeslots. There are two options:
PCU performance algorithm - GPRS resources configured for performance by the PCU.

Customer specified algorithm - operator can configure GPRS resources on a per cell basis.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

When an attempt is made to change gprs_ts_config_alg, and the requested PDTCHs

exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues
a warning to indicate that there is not enough GDS or PMC resource available.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.
Enough timeslots must be available on all of the GPRS cell
carriers.
This parameter can be changed only when GPRS is either
disabled or changed from disabled to enabled.

NOTE
To set this parameter at the OMC-R GUI, GPRS
must first be disabled and then enabled.
To set this parameter at a TTY terminal, GPRS
must first be disabled.

68P02901W23-T 6-387
Jan 2010
Syntax Chapter 6: CM database parameters

Syntax

Change command strings

chg_element gprs_ts_config_alg <value> <location> <cell_desc>

chg_cell_element gprs_ts_config_alg <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gprs_ts_config_alg <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 PCU performance algorithm
1 Customer specified algorithm
Default value 0

6-388 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_ul_dl_bias

gprs_ul_dl_bias

Description

The gprs_ul_dl_bias parameter enables a second uplink to be allocated to mobiles initially with
multislot class 6 or 10 and any multislot class that maps to class 6 or 10.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies GPRS must be unrestricted.

Syntax

Change command strings

chg_element gprs_ul_dl_bias <value> <location>

Display command strings

disp_element gprs_ul_dl_bias <location>

Values

Value type Boolean

Valid range 0 to 1
0 UL bias
1 DL bias
Default value 1

68P02901W23-T 6-389
Jan 2010
group_block_unblock_allowed Chapter 6: CM database parameters

group_block_unblock_allowed

Description

The group_block_unblock_allowed parameter allows the operator to make the A-interface

more efficient, by enabling support of the group blocking/unblocking procedure, if MSC
supports circuit group block and unblock messages.

If this parameter is enabled, the following group block' messages are sent to the MSC:
Circuit Group Block

Circuit Group Unblock

If this parameter is disabled, the following single circuit block' messages are sent to the MSC:
Block

Unblock

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is only valid at the BSC. This parameter
does not apply to RXCDR sites.

Syntax

Change command string

chg_element group_block_unblock_allowed <value> 0

Display command string

disp_element group_block_unblock_allowed 0

6-390 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled - BSS sends only single circuit block/unblock'
messages to the MSC.
1 Enabled - BSS sends only group block/unblock' messages
to the MSC.
Default value None

References

GSM specification TS GSM 8.08

This is a Motorola defined parameter.

68P02901W23-T 6-391
Jan 2010
gsl_lcf_mapping Chapter 6: CM database parameters

gsl_lcf_mapping

Description

The gsl_lcf_mapping parameter provides an operator with the option of automatic or manual
modes for equipage of GSLs inside SYSGEN mode. In automatic mode, the system distributes
the equipped GSLs to usable LCFs. In manual mode, the operator is prompted to specify the
LCF during equipage of a GSL.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.
The system must be in SYSGEN mode.

NOTE
BSS software processes using this parameter are notified immediately after the
change is made.

Syntax

Change command strings

chg_element gsl_lcf_mapping <value> bsc

Display command string

disp_element gsl_lcf_mapping bsc

6-392 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Manual mode
1 Auto mode
Default value 1 Inside SYSGEN (Auto mode - 0 cannot be set)
0 Outside SYSGEN (Manual mode)

68P02901W23-T 6-393
Jan 2010
gsm_bss_half_rate_enabled Chapter 6: CM database parameters

gsm_bss_half_rate_enabled

Description

The gsm_bss_half_rate_enabled parameter enables or disables the GSM Half Rate feature
at the BSS.

A warning is displayed if an attempt is made to enable GSM HR outside Sysgen mode when
there is no AXCDR device with CIC validation enabled.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GSM Half Rate feature must be unrestricted.
handover_required_sp_ver_used must be enabled.

Syntax

Add/Change command strings

chg_element gsm_bss_half_rate_enabled <value> <location>

NOTE
The following warning is displayed if an attempt is made to disable
gsm_bss_half_rate_enabled when either CIC validation or eac_mode is enabled for the
AXCDR:

WARNING: AXCDR CIC validation and/or enhanced auto connect mode are
currently enabled.

The following warning is displayed if an attempt is made to disable CIC validation for
the AXCDR when GSM HR is enabled:

WARNING: The AXCDR will not support AMR/GSM HR when CIC Validation is
disabled.

Display command strings

disp_element gsm_bss_half_rate_enabled <location>

6-394 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0 Disabled

68P02901W23-T 6-395
Jan 2010
gsm_cell_id_format Chapter 6: CM database parameters

gsm_cell_id_format

Description

The gsm_cell_id_format parameter specifies the format of the GSM cell Identification sent by
the Call Processor (CP) to the switch.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be set only at the BSC.

Syntax

Change command string

chg_element gsm_cell_id_format <value> 0

Display command string

disp_element gsm_cell_id_format 0

Values

Value type Integer

Valid range 0 to 2
0 Whole Cell Global Identification (CGI)
1 Location Area Code (LAC), and Cell Identity (CI)
2 Cell Identity (CI)
Default value 1

6-396 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference UTRAN Cell Identifier

UTRAN Cell Identifier

It is possible to hand over calls to 3G UTRAN cells. This is set up using the neighbor commands:
add_neighbor, modify_neighbor, anddel_neighbor disp_neighbor. UTRAN Cell IDs are
required parameter entries for these commands. The UTRAN cell ID format consists of five
fields:
MCC - Mobile Country Code.

MNC - Mobile Network Code.

LAC - Location Area Code.

RNC - Radio Network Controller Identity.

CI - Cell Identity.

UTRAN cell IDs are typically displayed in the following format:

543 21 61986 (F222h) 34944 (8880h) 4011

Where: is:
543 MCC
21 MNC
61986 LAC
349444011 RNCICI

References

GSM specification GSM TS 8.08 - 3.2.2.27

This is a Motorola defined parameter.

68P02901W23-T 6-397
Jan 2010
gsm_half_rate_enabled Chapter 6: CM database parameters

gsm_half_rate_enabled

Description

The gsm_half_rate_enabled parameter enables or disables the GSM Half Rate (HR) feature
at a cell.

Executing the copy_cell command sets this parameter to the default value in the new cell and
displays a warning indicating that the parameter has been modified.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GSM Half Rate feature must be unrestricted.
The BTS site for the cell must be solely comprised of
Horizonmacro family of cabinets, M-Cell2 or M-Cell6
cabinets, or a mixture of Horizonmacro and M-Cell2/6
cabinets.

Syntax

Add/Change command strings

chg_element gsm_half_rate_enabled <value> <location> <cell_desc>

chg_cell_element gsm_half_rate_enabled <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element gsm_half_rate_enabled <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0 Disabled

6-398 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference half_rate_enabled

half_rate_enabled

Description

The half_rate_enabled parameter enables or disables Half Rate at an RTF.

The half_rate_enabled RTF parameter can only be modified by unequipping and re-equipping
the RTF. This RTF parameter cannot be set for a sub-equipped RTF. The RTF parameter is
displayed using the disp_equipment command.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The AMR feature and/or GSM Half Rate feature must be
unrestricted.
The half_rate_enabled parameter is only applicable at
a BTS site comprised solely of Horizonmacro cabinets,
M-Cell2 or M-Cell6 cabinets, or a mixture of Horizonmacro,
Horizon IImacroand M-Cell6 cabinets.
The half_rate_enabled RTF parameter is only prompted
for during the equipage of an RTF.

Syntax

Add/Change command strings

equip <location> rtf

Display command strings

disp_equipment <location> rtf <rtf_id1> <rtf_id2>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-399
Jan 2010
handover_power_level Chapter 6: CM database parameters

handover_power_level

Description

The handover_power_level parameter defines the power control level to be used by an MS

during a handover to a different cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The maximum value for a PGSM or EGSM system is 19.
The maximum value for a DCS1800 system is 15.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element handover_power_level <value> <location> <cell_desc>

chg_cell_element <location> handover_power_level <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element handover_power_level <location> <cell_desc>

Values

Value type Integer

Valid ranges See Table 6-16, Table 6-17 nd Table 6-18.

6-400 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Table 6-16 lists the maximum MS power level for PGSM and EGSM cells.

Table 6-16 Max MS power level for PGSM and EGSM

Value Power level Value Power level

2 39 dBm 11 21 dBm
3 37 dBm 12 19 dBm
4 35 dBm 13 17 dBm
5 33 dBm 14 15 dBm
6 31 dBm 15 13 dBm
7 29 dBm 16 11 dBm
8 27 dBm 17 9 dBm
9 25 dBm 18 7 dBm
10 23 dBm 19 5 dBm

Table 6-17 lists the maximum mobile power level for DCS1800 and PCS1900 cells.

Table 6-17 Max MS power level for DCS1800 and PCS1900 cells

Value Power level Value Power level

0 30 dBm 8 14 dBm
1 28 dBm 9 12 dBm
2 26 dBm 10 10 dBm
3 24 dBm 11 8 dBm
4 22 dBm 12 6 dBm
5 20 dBm 13 4 dBm
6 18 dBm 14 2 dBm
7 16 dBm 15 0 dBm

Table 6-18 lists the maximum mobile power level for DCS1800 and PCS1900 cells for class
3 mobiles.

Table 6-18 Max MS power level for class 3 mobiles

Value Power level Value Power level

29 36 dBm 31 32 dBm
30 34 dBm

Default value 2

68P02901W23-T 6-401
Jan 2010
References Chapter 6: CM database parameters

References

GSM specification 5.05 - 4.1.1

This is a Motorola defined parameter.

6-402 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference handover_required_curr_ch

handover_required_curr_ch

Description

The handover_required_curr_ch parameter specifies whether the optional message element

current channel is included in the Handover Required message to the MSC.

This parameter should conform to the MSC capabilities.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.

Syntax

Change command string

chg_element handover_required_curr_ch <value> 0

Display command string

disp_element handover_required_curr_ch 0

Values

Value type Boolean

Valid range 0 or 1
0 Not included
1 Included
Default value 1

References

GSM specification TS GSM 08.08

This is a Motorola defined parameter.

68P02901W23-T 6-403
Jan 2010
handover_required_reject_switch Chapter 6: CM database parameters

handover_required_reject_switch

Description

The handover_required_reject_switch parameter 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.

If the handover_required_reject_switch is enabled (set to 1), the BSS expects to receive a

Handover Required Reject message from the switch. Any internal cells that are candidates for
the handover are not included in the Handover Required message. On receipt of the Handover
Required Reject message, the BSS performs an internal handover if there are valid candidates.

If the handover_required_reject_switch is disabled (set to 0), the BSS does not expect to
receive a Handover Required Reject message from the switch and includes internal candidates
in the Handover Required message.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.

Syntax

Change command string

chg_element handover_required_reject_switch <value> 0

Display command string

disp_element handover_required_reject_switch 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled (reject message not required)
1 Enabled (reject message required)
Default value 1

6-404 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter HAND_REQ_REJECT

GSM specification 8.08 - 3.1.5.1.1: Response request in a HANDOVER
REQUIRED.
8.08 - Figures 4 and 5.
12.20 - 5.2.7.5: Hand Req Reject

68P02901W23-T 6-405
Jan 2010
handover_required_sp_ver_used Chapter 6: CM database parameters

handover_required_sp_ver_used

Description

The handover_required_sp_ver_used parameter determines whether the optional element

speech_version_used can be built into the Handover Required message.

An attempt to disable (0) handover_required_sp_ver_used is rejected if GSM Half Rate is

enabled in the BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The handover_required_sp_ver_used parameter
cannot be disabled (0) if either efr_enabled or
gsm_bss_half_rate_enabled is enabled (1).

Syntax

Change command string

chg_element handover_required_sp_ver_used <value> 0

Display command string

disp_element handover_required_sp_ver_used 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled (no speech version)
1 Enabled (built in speech version)
Default value 0

6-406 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM specification TS GSM 8.08

This is a Motorola defined parameter.

68P02901W23-T 6-407
Jan 2010
hcs_thr Chapter 6: CM database parameters

hcs_thr

Description

The hcs_thr parameter specifies the Hierarchical Cell Structure (HCS) signal strength threshold
for a cell. The signal strength threshold can be changed in 2 dBm steps.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH feature must be unrestricted.
If the local_maintenance flag is disabled, the MMI is
prevented from changing this item.

Syntax

Add/Change command strings

chg_element hcs_thr <value> <location> <cell_desc>

chg_cell_element hcs_thr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element hcs_thr <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 31 Represents signal strength threshold in 2 dBm steps:
0 -110 dBm
1 -108 dBm
... ...
31 -48 dBm
Default value 0

6-408 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference hdsl_losw_oos

hdsl_losw_oos

Description

The hdsl_losw_oos parameter specifies the HDSL Loss of Sync Word (LOSW) out of service
(OOS) alarm period. The system takes the HDSL link out of service if the sync word is not
received for the hdsl_losw_oos period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter may only be changed if the HDSL feature is
unrestricted.
This parameter may only be changed at an M-Cellcity,
Horizonmicro or Horizoncompact site.
Changing this parameter affects all master modems
equipped as msi_type niu_hdsl at the local M-Cell site.
All slave modem alarm thresholds are identical to the
master modem alarm thresholds.

Syntax

Change command string

chg_element hdsl_losw_oos <value> <location>

Display command string

disp_element hdsl_losw_oos <location>

Values

Value type Integer (seconds)

Valid range 0 to 3598
Default value 6

68P02901W23-T 6-409
Jan 2010
hdsl_losw_restore Chapter 6: CM database parameters

hdsl_losw_restore

Description

The hdsl_losw_restore parameter defines the HDSL Loss of Sync Word (LOSW) restoration
period. If the sync word is received for the hdsl_losw_restore_period, the system restores the
HDSL link back into service (INS).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter may only be changed if the HDSL option is
unrestricted.
This parameter may only be changed at an M-Cellcity,
Horizonmicro or Horizoncompact site.
Changing this parameter affects all master modems
equipped as msi_type niu_hdsl at the local M-Cell site.
All slave modem alarm thresholds are identical to the
master modem alarm thresholds.

Syntax

Change command string

chg_element hdsl_losw_restore <value> <location>

Display command string

disp_element hdsl_losw_restore <location>

Values

Value type Integer (seconds)

Valid range 0 to 65534
Default value 6

6-410 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference hdsl_snr_daily

hdsl_snr_daily

Description

The hdsl_snr_daily parameter defines the HDSL Signal to Noise Ratio (SNR) daily alarm level.
If the SNR alarm level drops below the hdsl_snr_daily threshold for an accumulated period of
hdsl_snr_daily_mon_period within a given 24 hour period, a daily alarm is generated.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter may only be changed if the HDSL option is
unrestricted.
This parameter may only be changed at an M-Cellcity,
Horizonmicro or Horizoncompact site.
Changing this parameter affects all master modems
equipped as msi_type niu_hdsl at the local M-Cell site.
All slave modem alarm thresholds are identical to the
master modem alarm thresholds.

Syntax

Change command string

chg_element hdsl_snr_daily <value> <location>

Display command string

disp_element hdsl_snr_daily <location>

68P02901W23-T 6-411
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (representing 0.5 dB steps)

Valid range 6 to 44 Represents 3 dB to 22 dB, as shown below:

6 3 dB
7 3.5 dB
8 4 dB
... ...
... ...
... ...
44 22 dB

Default value 16 (8 dB)

6-412 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference hdsl_snr_daily_mon_period

hdsl_snr_daily_mon_period

Description

The hdsl_snr_daily_mon_period parameter sets the threshold period for the daily signal to
noise ratio (SNR). If the SNR level drops below the hdsl_snr_daily threshold for an accumulated
period of hdsl_snr_daily_mon_period within a given 24 hour period, a daily alarm is generated.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter may only be changed if the HDSL option is
unrestricted.
This parameter may only be changed at an M-Cellcity,
Horizonmicro or Horizoncompact site.
Changing this parameter affects all master modems
equipped as msi_type niu_hdsl at the local M-Cell site.
All slave modem alarm thresholds are identical to the
master modem alarm thresholds.

Syntax

Change command string

chg_element hdsl_snr_daily_mon_period <value> <location>

Display command string

disp_element hdsl_snr_daily_mon_period <location>

Values

Value type Integer (seconds)

Valid range 0 to 65534
Default value 20

68P02901W23-T 6-413
Jan 2010
hdsl_snr_hourly Chapter 6: CM database parameters

hdsl_snr_hourly

Description

The hdsl_snr_hourly parameter sets the threshold period for the hourly signal to noise ratio
(SNR). If the SNR level drops below the hdsl_snr_hourly threshold for an accumulated period
of hdsl_snr_hourly_mon_period within a given 60 minute period, an hourly alarm is generated.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter may only be changed if the HDSL option is
unrestricted.
This parameter may only be changed at an M-Cellcity,
Horizonmicro or Horizoncompact site.
Changing this parameter affects all master modems
equipped as msi_type niu_hdsl at the local M-Cell site.
All slave modem alarm thresholds are identical to the
master modem alarm thresholds.

Syntax

Change command string

chg_element hdsl_snr_hourly <value> <location>

Display command string

disp_element hdsl_snr_hourly <location>

6-414 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (representing 0.5 dB steps)

Valid range 8 to 44 Represents 4 dB to 22 dB, as shown below:
8 4 dB
9 4.5 dB
10 5 dB
... ...
... ...
... ...
44 22 dB
Default value 18 (9 dB)

68P02901W23-T 6-415
Jan 2010
hdsl_snr_hourly_mon_period Chapter 6: CM database parameters

hdsl_snr_hourly_mon_period

Description

The hdsl_snr_hourly_mon_period parameter sets the threshold period for the hourly signal
to noise ratio (SNR). If the SNR level drops below the hdsl_snr_hourly threshold for an
accumulated period of hdsl_snr_hourly_mon_period within a given 60 seconds period, an
hourly alarm is generated.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter may only be changed if the HDSL option is
unrestricted.
This parameter may only be changed at an M-Cellcity,
Horizonmicro or Horizoncompact site.
Changing this parameter affects all master modems
equipped as msi_type niu_hdsl at the local M-Cellcity or
Horizonmicro site.
All slave modem alarm thresholds are identical to the
master modem alarm thresholds.

Syntax

Change command string

chg_element hdsl_snr_hourly_mon_period <value> <location>

Display command string

disp_element hdsl_snr_hourly_mon_period <location>

Values

Value type Integer (seconds)

Valid range 0 to 3598
Default value 20

6-416 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference hdsl_snr_oos

hdsl_snr_oos

Description

The hdsl_snr_oos parameter specifies the SNR threshold level for the HDSL Signal to Noise
Ratio (SNR). The system continuously monitors the SNL level. If the SNR level drops below
the hdsl_snr_oos threshold for more than hdsl_oos_mon_period, the HDSL link is taken
Out Of Service (OOS).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter may be changed only if the HDSL option is
unrestricted.
This parameter may be changed only at an M-Cellcity,
Horizonmicro or Horizoncompact site.
Changing this parameter affects all master modems
equipped as msi_type niu_hdsl at the local M-Cell site.
All slave modem alarm thresholds are identical to the
master modem alarm thresholds.
The hdsl_snr_oos threshold must be lower than the
hdsl_snr_restore threshold.

Syntax

Change command string

chg_element hdsl_snr_oos <value> <location>

Display command string

disp_element hdsl_snr_oos <location>

68P02901W23-T 6-417
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (0.5dB steps)

Valid range 6 to 44 Represents 3 dB to 22 dB, as shown below:

6 3 dB
7 3.5 dB
8 4 dB
... ...
... ...
... ...
44 22 dB
Default value 14 (7 dB)

6-418 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference hdsl_snr_restore

hdsl_snr_restore

Description

The hdsl_snr_restore parameter specifies the SNR threshold level for the HDSL Signal to
Noise Ratio (SNR). The system continuously monitors the SNL level. If the SNR level rises
above the hdsl_snr_restore threshold for more than hdsl_oos_mon_period, the HDSL link is
restored to service.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter may only be changed if the HDSL option is
unrestricted.
This parameter may be changed only at an M-Cellcity,
Horizonmicro or Horizoncompact site.
Changing this parameter affects all master modems
equipped as msi_type niu_hdsl at the local M-Cell site.
All slave modem alarm thresholds are identical to the
master modem alarm thresholds.
The hdsl_snr_oos threshold must be lower than the
hdsl_snr_restore threshold.

Syntax

Change command string

chg_element hdsl_snr_restore <value> <location>

Display command string

disp_element hdsl_snr_restore <location>

68P02901W23-T 6-419
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (0.5 dB steps)

Valid range 6 to 44 Represents 3 dB to 22 dB, as shown below:

6 3 dB
7 3.5 dB
8 4 dB
... ...
... ...
... ...
44 22 dB

Default value 16 (8 dB)

6-420 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ho_exist_congest

ho_exist_congest

Description

The ho_exist_congest parameter specifies how to handle existing calls on a TCH when an MS
needs a TCH and none are available in that cell.

The available options are:

Attempt to hand over as many calls as the number of queued assignment requests.

Attempt to hand over as many calls as meet the congestion handover criteria.

No handover attempts (for this condition).

This parameter is copied if the copy_cell command is used.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Congestion Relief feature is required.
The MSC may need to increase the timer waiting for the
Assignment Complete message from the BSS when this
database parameter is enabled.

Syntax

Change command strings

chg_element ho_exist_congest <value> <location> <cell_desc>

chg_cell_element ho_exist_congest <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element ho_exist_congest <location> <cell_desc>

68P02901W23-T 6-421
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 2
0 No hand over attempts (for this condition).
1 Attempt to hand over as many calls as the number of
queued assignment requests.
2 Attempt to hand over as many calls as meet the congestion
handover criteria.
Default value 0

References

GSM specification TS GSM 08.08

This is a Motorola defined parameter.

6-422 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ho_margin_def

ho_margin_def

Description

The ho_margin_def parameter sets the default value for the neighbor handover margin
(ho_margin_cell) attribute of the source cell. The neighbor handover margin is set using the
add_neighbor command and changed using the modify_neighbor command.

The handover margin is the amount by which the neighboring cell received signal strength must
exceed the source cell received signal to request a handover.

In the context of the power budget process, the following equation must be true: IfPBGT(n) >
ho_margin(n) then a handover may be required.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element ho_margin_def <value> <location> <cell_desc>

chg_cell_element ho_margin_def <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ho_margin_def <location> <cell_desc>

Values

Value type Integer (dB)

Valid range -63 to +63
Default value 8

68P02901W23-T 6-423
Jan 2010
References Chapter 6: CM database parameters

References

GSM parameter HO_MARGIN_DEF

GSM specification 5.08 - Appendix A, 3.1f: PBGT(n), and section 3.2.2e.
5.08 - Appendix A - Table 1
12.20 - 5.2.8.4 adjacent Cell Handover - ho Margin Default
12.20 - 5.2.8.4 adjacent Cell Handover - ho Margin Cell
12.20 - 5.2.8.2

6-424 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ho_margin_type5

ho_margin_type5

Description

The ho_margin_type5 parameter sets the power budget type 5 handover margin.

Type A (no operator action)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command string

modify_neighbor <src_cell_id> <neighbor_cell_id> ho_margin_type5 <value>

Display command strings

disp_neighbor <src_cell_desc> [<neighbor_cell_id>|all]

disp_neighbor <source cell_name> [<internal neighbor cell_name>]

disp_neighbor <src_cell_desc> [TEST <test neighbor_cell_id>]

Values

Value type Integer (dBm)

Valid range -63 to +63
Default value 63

68P02901W23-T 6-425
Jan 2010
ho_margin_usage_flag Chapter 6: CM database parameters

ho_margin_usage_flag

Description

The ho_margin_usage_flag parameter determines which sorting algorithm the system uses to
sort the neighbor list.

If ho_margin_usage_flag is disabled, handover candidates are always sorted using

ho_margin_cell.

If ho_margin_usage_flag is enabled:
Handover candidates for RXLEV handovers are sorted using ho_margin_rxlev [n].

Handover candidates for RXQUAL handovers are sorted using ho_margin_rxqual [n].

All other handover causes that have neighbors are sorted using ho_margin_cell value.

Type A (no operator action)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

chg_element ho_margin_usage_flag <value> <location> <cell_desc>

chg_cell_element ho_margin_usage_flag <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element ho_margin_usage_flag <location> <cell_desc>

6-426 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-427
Jan 2010
ho_only_max_pwr Chapter 6: CM database parameters

ho_only_max_pwr

Description

The ho_only_max_pwr parameter specifies whether the MS or the BTS must be at full power
before a rxlev or rxqual handover can take place.

If this option is enabled:

The MS must be at full power for an uplink handover.

The BTS must be at full power for a downlink handover.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies To use the ho_only_max_pwr parameter, the
decision_alg_type parameter must equal 1, to allow the
MS or BTS to reach full power.

Syntax

Change command strings

chg_element ho_only_max_pwr <value> <location> <cell_desc>

chg_cell_element ho_only_max_pwr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element ho_only_max_pwr <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-428 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ho_pwr_level_inner

ho_pwr_level_inner

Description

The ho_pwr_level_inner parameter specifies the handover power level for the inner zone of a
Dual Band cell for an inter-cell handover. The valid range for this parameter depends on the
frequency of the inner zone.

Type A (no operator action)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Dual Band Cells feature must be unrestricted.

NOTE
The element handover_power_level does not apply to intra-cell handovers.

Syntax

Change command strings

chg_element ho_pwr_level_inner <value> <location> <cell_desc>

chg_cell_element ho_pwr_level_inner <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element ho_pwr_level_inner <location> <cell_desc>

Values

Value type Integer

Valid ranges See Table 6-19, Table 6-20 and Table 6-21.

68P02901W23-T 6-429
Jan 2010
Values Chapter 6: CM database parameters

Table 6-19 lists the maximum MS power level for PGSM and EGSM cells.

Table 6-19 Max MS power level for PGSM and EGSM cells

Value Power level Value Power level

2 39 dBm 11 21 dBm
3 37 dBm 12 19 dBm
4 35 dBm 13 17 dBm
5 33 dBm 14 15 dBm
6 31 dBm 15 13 dBm
7 29 dBm 16 11 dBm
8 27 dBm 17 9 dBm
9 25 dBm 18 7 dBm
10 23 dBm 19 5 dBm

Table 6-20 the maximum mobile power level for DCS1800 and PCS1900 cells.

Table 6-20 Max MS power level for DCS1800 and PCS1900 cells

Value Power level Value Power level

0 30 dBm 8 14 dBm
1 28 dBm 9 12 dBm
2 26 dBm 10 10 dBm
3 24 dBm 11 8 dBm
4 22 dBm 12 6 dBm
5 20 dBm 13 4 dBm
6 18 dBm 14 2 dBm
7 16 dBm 15 0 dBm

Table 6-21 lists the maximum mobile power level for DCS1800 and PCS1900 cells for class
3 mobiles.

Table 6-21 Max MS level for class 3 mobiles

Value Power level Value Power level

29 36 dBm 31 32 dBm
30 34 dBm

Default value 2

6-430 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference hop_count

hop_count

Description

The hop_count parameter, combined with the hop_count_timer parameter, limits the number
of intra-cell interference handovers for a call.

The hop_count parameter sets the number of handovers. If the number of handovers defined
by the hop_count parameter occur within the time set by the hop_count_timer, the system
escalates the handover to an RXQUAL handover to another cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element hop_count <value> <location> <cell_desc>

chg_cell_element hop_count <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element hop_count <location> <cell_desc>

Values

Value type Integer (quantity of intra-cell interference handovers)

Valid range 0 to 255 (0 disables intra-cell interference handovers)
Default value 255

68P02901W23-T 6-431
Jan 2010
hop_qual_enabled Chapter 6: CM database parameters

hop_qual_enabled

Description

The hop_qual_enabled parameter enables or disables the use of specific rxqual thresholds
for hopping call handovers.

Trials have shown that non-hopping calls can show poor quality of service when the reported
rxqual value is around 5, whereas hopping calls can provide the same quality of service with
the reported rxqual value at 6 or 7.

If hop_qual_enabled is enabled and a hopping call is in progress, the system uses the rxqual
values set with the chg_cell_element command (see Syntax).

If hop_qual_enabled is disabled, the normal rxqual values set with the add_cell command
are used.

NOTE
If both hop_qual_enabled and data_qual_enabled are enabled, data_qual_enabled
takes precedence for data transmission in a hopping call.

Type A (no operator action required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc

Syntax

Change command string

chg_cell_element hop_qual_enabled <value> <cell_desc_opt>

If the value is 1 (enabled), the system prompts for the hopping threshold values of the following
parameters:
l_rxqual_dl_h_hopping on page 6-503

l_rxqual_ul_p_hopping on page 6-542

6-432 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

l_rxqual_dl_p_hopping on page 6-516

l_rxqual_ul_h_hopping on page 6-529

If Half Rate is enabled, l_rxqual_dl_h_hopping_hr on page 6-507

If Half Rate is enabled, l_rxqual_ul_p_hopping_hr on page 6-546

Display command strings

disp_cell <cell_id> full

disp_element hop_qual_enabled <location> <cell_desc>

Values

Value type Boolean

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-433
Jan 2010
hopping_support Chapter 6: CM database parameters

hopping_support

Description

The hopping_support parameter defines the frequency hopping in a cell. Two methods of
achieving frequency hopping are available.

Synthesizer Frequency Hopping

This is accomplished by the high speed switching of the transmit and receive frequency
synthesizers of the individual transceivers. As a result of the dynamic nature of the transmit
frequency, broadband (hybrid) combining of the transmitters is necessary. The combination
losses associated with this technique must be acceptable.

Baseband Frequency Hopping

This is accomplished by routing the traffic channel data through fixed frequency transceivers
through the TDM highway on a timeslot basis. In this case, the transceiver would have fixed
tuned transmitters combined either in low loss tuned combiners, or hybrid combiners. The
frequency hopping set (mobile allocation, MA) is limited to the number of transceivers equipped
at a specific site.

The frequency hopping technique employed is dependent upon the losses, specific cells can
tolerate in their transmit paths, and the number of transceivers associated with specific cells.

BTS restricts the baseband hopping capabilities on double density CTU2 DRIs, of which carrier A
is EGPRS capable. Carrier A and carrier B are the two DD CTU2 radios on the Horizon II cabinet.

Type B (operator action required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None
Operator actions Place the system in the SYSGEN ON mode before using the
chg_element or chg_cell_element commands to change
this parameter.
Using the chg_hop_params (see chg_hop_params on page
3-145) command to change the hopping system does not
require SYSGEN ON.

6-434 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

Syntax

Change command strings

chg_element hopping_support <value> <location> <cell_desc>

chg_cell_element hopping_support <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element hopping_support <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 2
0 No hopping in this cell
1 Synthesizer hopping
2 Baseband hopping
Default value 0

References

GSM specification Motorola GSM B1 document - 4.2.1

5.01 - 6
This is a Motorola defined parameter.

68P02901W23-T 6-435
Jan 2010
hopping_systems_enabled Chapter 6: CM database parameters

hopping_systems_enabled

Description

The hopping_systems_enabled parameter enables or disables a frequency hopping system.

An index number (fhi) is required. The frequency hopping indicator (fhi) value specifies which
hopping system is affected. The range of values, entered as <index> is 0 to 3.

Type B (operator action required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None
Operator actions The system must be in SYSGEN ON mode to
change this parameter with the chg_element or
chg_cell_element commands. Using the chg_hop_params
(see chg_hop_params on page 3-145) command to
change the hopping system does not require SYSGEN ON.

Syntax

Change command strings

chg_element hopping_systems_enabled,<index> <value> <location> <cell_desc>

chg_cell_element hopping_systems_enabled,<index> <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_cell <cell_id> <full>disp_element

hopping_systems_enabled,<index><location> <cell_desc>

disp_hopping <cell_desc> [<fhi> | active]

6-436 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None

References

GSM specification 5.01 - 6

This is a Motorola defined parameter.

68P02901W23-T 6-437
Jan 2010
hopping_systems_hsn Chapter 6: CM database parameters

hopping_systems_hsn

Description

The hopping_systems_hsn parameter specifies the hopping sequence (generator) number

(HSN) to be used by the frequency hopping system. HSN is one of seven parameters that
defines a particular physical channel in a BTS.

An index number (fhi) is required. The frequency hopping indicator (fhi) value specifies which
hopping system is affected. The range of values, entered as <index> is 0 to 3.

Type B (operator action required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None
Operator actions Respond to the SITE reset prompt which will be displayed
after the chg_element command is entered to modify this
parameter.

Syntax

Change command strings

chg_element hopping_systems_hsn,<index> <value> <location> <cell_desc>

chg_cell_element hopping_systems_hsn <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element hopping_systems_hsn,<index> <location> <cell_desc>

disp_hopping <cell_desc> [<fhi> | active]

6-438 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 63
0 Cyclic hopping. The MA is hopped through lowest to
highest magnitude, and then the cycle repeats.
1 to 63 Random hopping. HSN and MA are entries to the algorithm
table 6 of GSM Rec. 5.02.
Default value None

References

GSM parameter HSN

GSM specification 5.02 - 5.6.3, 6.2.2, 6.2.3
5.02 - table 6: hopping algorithm
5.01 - 6

68P02901W23-T 6-439
Jan 2010
hopping_systems_mobile_alloc Chapter 6: CM database parameters

hopping_systems_mobile_alloc

Description

The hopping_systems_mobile_alloc parameter allocates the Absolute Radio Frequency

Channel Number (ARFCN) frequencies for hopping (either baseband hopping or synthesizer
hopping).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Not required for chg_hop_params command. Required for
disp_cell and disp_element commands.
Dependencies Refer to the descriptions for the chg_hop_params command
(see chg_hop_params on page 3-145) for restrictions on
changing the hopping parameters.
The system does not check for errors when changes are
made in SYSGEN ON mode. When SYSGEN is turned off,
however, the system does check for errors, and may reject
the command.

Syntax

Change command strings

chg_hop_params <location>

chg_hop_params <cell_desc>

NOTE
chg_hop_params can be used in SYSGEN or out of SYSGEN. chg_hopping must be
executed in SYSGEN_ON mode.

6-440 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command strings

disp_cell <cell_id> full

disp_element hopping_systems_mobile_alloc,<index1>,<index2> <location>

<cell_desc>

disp_hopping <site> [active]

disp_hopping <cell_desc> [<fhi> | active]

Values

Value type Integer

Valid range Variable ARFCN depends on the frequency type for the cell.
For PGSM, the range is 1 through 124.
For EGSM, the range is either: 1 to 124, 975 to 1023, or 0.
For DCS1800, the range is 512 to 885.
For PCS1900 the range is 512 to 810.
Default value None

References

GSM specification 5.01 - 6

This is a Motorola defined parameter.

68P02901W23-T 6-441
Jan 2010
hr_fr_hop_count Chapter 6: CM database parameters

hr_fr_hop_count

Description

The hr_fr_hop_count parameter specifies the number of Intra-Cell quality handovers from
half-rate channels to full rate channels for a call on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must
be unrestricted.
The value of this parameter must not exceed the value of
hop_count.

Syntax

Add/Change command strings

chg_element hr_fr_hop_count <value> <location> <cell_desc>

chg_cell_element hr_fr_hop_count <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element hr_fr_hop_count <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 255
Default value 1

6-442 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference hr_intracell_ho_allowed

hr_intracell_ho_allowed

Description

The parameter enables or disables the support for Intra-Cell quality handovers for half-rate
channels within a cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must
be unrestricted.

Syntax

Add/Change command strings

chg_element hr_intracell_ho_allowed <value> <location> <cell_desc>

chg_cell_element hr_intracell_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element hr_intracell_ho_allowed <location> <cell_desc>

68P02901W23-T 6-443
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 3
0 Half-rate intra-cell quality handovers are not initiated by
the BSS. Handover Required is sent to MSC.
1 Half-rate intra-cell quality handovers are disabled.
Handover Required is not sent to MSC.
2 Half-rate intra-cell quality handovers are enabled.
Full-rate only is allowed.
3 Half-rate intra-cell quality handovers are enabled.
Half-rate and Full-rate are allowed for interference based
handover, full rate only for quality based handover.
Default value 3

6-444 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference hr_res_ts

hr_res_ts

Description

The hr_res_ts parameter specifies the maximum number of half-rate capable timeslots to be
reserved within each zone of the cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must
be unrestricted.

Syntax

Add/Change command strings

chg_element hr_res_ts <value> <location> <cell_desc>

chg_cell_element hr_res_ts <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element hr_res_ts <location> <cell_desc>

Values

Value type Integer (timeslot)

Valid range 0 to 255 In steps of 1 timeslot
Default value 2

68P02901W23-T 6-445
Jan 2010
illegal_circuit_id Chapter 6: CM database parameters

illegal_circuit_id

Description

The illegal_circuit_id parameter is used as an internal place holder in call processing to show
that no circuit has been assigned to a call. The value may be changed to permit a customer
to specify the circuit ID to be used as the illegal_circuit_id. If the value is not changed, a
Motorola specified illegal_circuit_id is assigned.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.

Syntax

Change command string

chg_element illegal_circuit_id <value> 0

Display command string

disp_element illegal_circuit_id 0

Values

Value type Integer

Valid range 0 to 65535
Default value 0

6-446 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Improve_ts_enabled

Improve_ts_enabled

Description

The Improve_ts_enabled parameter specifies the enable or disable status of the improved
timeslot sharing feature at the BSS. This parameter can be changed inside and outside SYSGEN
mode.

Type A (No operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Improved timeslot sharing optional feature is
unrestricted.

Syntax

Display command strings

disp_element improve_ts_enabled <location>

Change command strings

chg_element improve_ts_enabled <value> <location>

Input parameters

location

Indicates the site location.

0 or bsc BSC

68P02901W23-T 6-447
Jan 2010
Example Chapter 6: CM database parameters

Example

Example 1

chg_element improve_ts_enabled 1 bsc

Where: is:
1 specifies the enable status of the improved timeslot
sharing feature.
bsc location of the processors.

System response

WARNING: B-U DD CTU2 DRIs must be cycled to activate

ITS at specific sites or reset BTS site

COMMAND ACCEPTED

Example 2

chg_element improve_ts_enabled 0 bsc

Where: is:
0 specifies the disable status of the improved timeslot
sharing feature.
bsc location of the processors.

System response

WARNING: B-U DD CTU2 DRIs must be cycled to deactivate

ITS at specific sites or reset BTS site

COMMAND ACCEPTED

Example 3

chg_element improve_ts_enabled 2 bsc

System response

ERROR: Range Error, parameter number: 2.

6-448 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-449
Jan 2010
imrm_dcs1800_weight Chapter 6: CM database parameters

imrm_dcs1800_weight

Description

The imrm_dcs1800_weight parameter specifies the weighting for the dcs1800 frequency.

A value of 0 specifies no support; a value of 100 specifies most preferred. The BSS rejects an
attempt to modify this parameter to 100 if any of the other supported band weights have a
setting of 100.

Type A (No operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element imrm_dcs1800_weight <value> <location> <cell_desc>

chg_cell_element imrm_dcs1800_weight <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element imrm_dcs1800_weight <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 100
Default value 0

6-450 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference imrm_egsm_weight

imrm_egsm_weight

Description

The imrm_egsm_weight parameter specifies the weighting for the EGSM frequency.

A value of 0 specifies no support; a value of 100 specifies most preferred. The BSS rejects an
attempt to modify this parameter to 100 if any of the other supported band weights have a
setting of 100.

Type A (No operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element imrm_egsm_weight <value> <location> <cell_desc>

chg_cell_element imrm_egsm_weight <value> <cell_desc>

NOTE
All IMRM weighting for a cell can be modified by specifying the numerical value 16
when issuing the following command and responding to the prompts:
chg_cell_element band_preference 16 <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element imrm_egsm_weight <location> <cell_desc>

68P02901W23-T 6-451
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 100
Default value 0

6-452 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference imrm_force_recalc

imrm_force_recalc

Description

Theimrm_force_recalc parameter when enabled, forces the recalculation of the preferred band
for a call after handover to the specified cell. This occurs for handovers from source neighbor
cells supporting IMRM. Handovers from source neighbor cells not supporting IMRM do not have
a preferred band defined, so one is calculated automatically after completion of the handover.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element imrm_force_recalc <value> <location> <cell_desc>

chg_cell_element imrm_force_recalc <value> <cell_desc>

NOTE
All IMRM weighting for a cell can be modified by specifying the numerical value 16
when issuing the following command and responding to the prompts:
chg_cell_element band_preference 16 <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element imrm_force_recalc <location> <cell_desc>

68P02901W23-T 6-453
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0

6-454 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference imrm_pgsm_weight

imrm_pgsm_weight

Description

The imrm_pgsm_weight parameter specifies the weighting for the PGSM frequency.

A value of 0 specifies no support; a value of 100 specifies most preferred. The BSS rejects an
attempt to modify this parameter to 100 if any of the other supported band weights have a
setting of 100.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element imrm_pgsm_weight <value> <location> <cell_desc>

chg_cell_element imrm_pgsm_weight <value> <cell_desc>

NOTE
All IMRM weighting for a cell can be modified by specifying the numerical value 16
when issuing the following command and responding to the prompts:
chg_cell_element band_preference 16 <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element imrm_pgsm_weight <location> <cell_desc>

68P02901W23-T 6-455
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 100
Default value 0

6-456 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference imrm_umts_weight

imrm_umts_weight

Description

The imrm_umts_weight parameter specifies the weighting for the UMTS frequency band.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The 2G/3G Handover feature must be unrestricted.

Syntax

Change command strings

chg_element imrm_umts_weight <value> <location> <cell_desc>

chg_cell_element imrm_umts_weight <value> <cell_desc>

NOTE
All IMRM weighting for a cell can be modified by specifying the numerical value 16
when issuing the following command and responding to the prompts:
chg_cell_element band_preference 16 <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element imrm_umts_weight <location> <cell_desc>

68P02901W23-T 6-457
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 100
Default value 0

6-458 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference IncellOpt

IncellOpt

Description

The IncellOpt parameter indicates whether the Incell Support feature functionality is
unrestricted in the BSS software.

Command Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies If the IncellOpt flag indicates that Incell Support is
restricted, attempts to change Incell Support specific
database parameter is rejected.

Syntax

Change command strings

chg_element IncellOpt <value> <location>

Display command strings

disp_element IncellOpt <location>

disp_options

Values

Value type Boolean

Valid range 0 or 1
0 restricted
1 unrestricted
Default value N/A

68P02901W23-T 6-459
Jan 2010
inc_prp_cap_ena Chapter 6: CM database parameters

inc_prp_cap_ena

Description

The inc_prp_cap_ena parameter enables or disables Increase Packet Resource Processor

(PRP) Capacity.

When disabled, the BSS does not support the Increase PRP Capacity feature.

When enabled, the BSS does not support the Increase PRP Capacity feature.

NOTE
This parameter is retained for future development.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Increase PRP Capacity feature must be unrestricted.

NOTE
inc_prp_cap_ena is permanently disabled even though the PRP Capacity feature is
unrestricted.

Syntax

Change command strings

chg_element inc_prp_cap_ena <value> <location>

Display command strings

disp_element inc_prp_cap_ena <location>

6-460 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-461
Jan 2010
init_dl_cs Chapter 6: CM database parameters

init_dl_cs

Description

The init_dl_cs parameter is used to specify the initial downlink Coding Scheme (CS)
configuration information for a cell.

The init_dl_cs parameter is configurable on a per cell basis.

This parameter is used for GPRS and cannot be used for EGPRS (see egprs_init_dl_cs).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies EGPRS must be restricted.
GPRS must be unrestricted.

Syntax

Add/Change command strings

chg_element init_dl_cs <value> <location> <cell_desc>

chg_cell_element init_dl_cs <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element init_dl_cs <location> <cell_desc>

6-462 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 3
0 Downlink TBF starts with CS1.
1 Downlink TBF starts with CS2.
2 Downlink TBF starts with CS3.
3 Downlink TBF starts with CS4.
Default value 1

68P02901W23-T 6-463
Jan 2010
init_ul_cs Chapter 6: CM database parameters

init_ul_cs

Description

The init_ul_cs parameter is used to specify the initial uplink Coding Scheme (CS) configuration
information for a cell.

The init_ul_cs parameter is configurable on a per cell basis.

This parameter is used for GPRS and cannot be used for EGPRS (see egprs_init_ul_cs).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies EGPRS must be restricted.
GPRS must be unrestricted.

Syntax

Add/Change command strings

chg_element init_ul_cs <value> <location> <cell_desc>

chg_cell_element init_ul_cs <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element init_ul_cs <location> <cell_desc>

6-464 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Valid range 0 to 3
0 Downlink TBF starts with CS1.
1 Downlink TBF starts with CS2.
2 Downlink TBF starts with CS3.
3 Downlink TBF starts with CS4.
Default value 1

68P02901W23-T 6-465
Jan 2010
inner_amr_hr_usage_thres Chapter 6: CM database parameters

inner_amr_hr_usage_thres

{34452}

Description

The inner_amr_hr_usage_thres parameter is used to define the congestion threshold to

indicate at what congestion level the BSS software allows:
Reconfiguration of half-rate capable full rate calls with AMR HR as the first permitted HR
speech version to AMR half-rate calls in the inner zone.

Assignment of new half-rate capable calls with AMR HR as the first permitted HR speech
version on half-rate channels establishing in the inner zone.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies
This parameter can only be modified if the
AMR feature is enabled. Also, the value of the
inner_amr_hr_usage_thres parameter must be
less than or equal to the inner_hr_usage_thres
parameter unless the threshold is disabled.

This element can be modified inside and outside

SYSGEN mode. When AMR HR is not enabled at the
BSS level or at the cell level, the BSS SW ignores
the threshold.

Syntax

Change command string

chg_cell_element inner_amr_hr_usage_thres <value> <cell_desc>

chg_ele inner_amr_hr_usage_thres <value> <location> <cell_desc>

Display command string

disp_element inner_amr_hr_usage_thres <location>

6-466 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 101
0 Minimum
101 Maximum
Setting the value to 101 disables the congestion
mechanism.
Default value 101

68P02901W23-T 6-467
Jan 2010
inner_hr_usage_thres Chapter 6: CM database parameters

inner_hr_usage_thres

Description

The inner_hr_usage_thres parameter specifies the congestion threshold for the following:
Reconfiguration of half-rate capable full rate calls to AMR/GSM half-rate calls to the inner
zone.

The assignment of new calls on half-rate channels establishing in the inner zone.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must
be unrestricted.

Syntax

Add/Change command strings

chg_element inner_hr_usage_thres <value> <location> <cell_desc>

chg_cell_element inner_hr_usage_thres <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element inner_hr_usage_thres <location> <cell_desc>

Values

Value type Integer (percentage)

Valid range 0 to 101
Default value 101

6-468 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference inner_zone_alg

inner_zone_alg

Description

The inner_zone_alg parameter specifies the use algorithm and the associated parameters for
the inner zone of the cell.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Concentric Cells feature must be unrestricted to use
the inner_zone_alg parameter.
Cannot set this parameter to dual band cells for PCS1900
cells.
Before this parameter can be set to Dual Band (3) the
following dependencies must be met:
The Dual Band Cells feature must be unrestricted in order
to set inner_zone_alg to 3.
The Coincident Multiband feature and the Dual Band
Cells feature must not be set at the same time, so
coincident_mb must be 0.
RTFs must not be equipped for the inner zone.
The Multiband Inter-Cell Handover feature must be
enabled to change inner_zone_alg to 3 (mb_preference
parameter must not be 0).
Operator actions Change the security level to 2 or more before using this
parameter.

Syntax

Change command string

chg_cell_element inner_zone_alg <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element inner_zone_alg <location> <cell_desc>

68P02901W23-T 6-469
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 3
0 Disable inner zone.
1 Power based use algorithm.
The system displays prompts for:

ms_txpwr_max_inner
Valid range:
PGSM and EGSM:
5 to 39 dBm (odd values only; value must be less
than or equal to max_tx_ms)
Default value: max_tx ms

DCS1800 and PCS1900:

0 to 30 dBm (even values only; value must be less
than or equal to max_tx_ms)
Default value: max_tx ms

zone_ho_hyst,
Valid range: 0 to 30
Default value: 0

rxlev_dl_zone
Valid range: 0 to 63
Default value: 63

rxlev_ul_zone
Valid range: 0 to 63
Default value: 63
2 Interference based use algorithm.
The system prompts for:

neighbor_report_timer
Valid range: 0 to 255 SACCH periods
Default value: 10
3 Dual Band Cell use.
The system displays prompts as shown
in Table 6-22.
Default value 0

Table 6-22 shows the prompted parameters when 3 is entered for inner_zone_alg.

6-470 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Table 6-22 Prompted parameters for Dual Band Cell use

Prompt Parameter name Notes Range

Enter secondary frequency secondary_freq_type Required. PGSM, EGSM or
type: Inner zone DCS1800
frequency
type for
dual band
cell. If cell
primary
frequency
is PGSM
or EGSM,
must be
DCS1800.
If cell
primary
frequency
is
DCS1800,
can be
PGSM or
EGSM.
Enter maximum base bts_txpwr_max_inner Optional. As defined for
transmit power for the max_tx_bts
inner zone: Default: 0.
Enter maximum MS transmit ms_txpwr_max_inner Required. As defined for
power for the inner zone: max_tx_ms, based
on secondary
frequency type.
Enter handover power ho_pwr_level_inner Optional. As defined for
level for the inner zone: handover_power_level,
based on secondary
frequency type.
Default: 2.
Enter inner zone zone_ho_hyst Optional. -63 to +63
handover hysteresis: Default: 0.
Enter downlink receive rxlev_dl_zone Optional. 0 to 63
level threshold for the Default: 63.
inner zone:
Enter uplink receive rxlev_ul_zone Optional. 0 to 63
level threshold for the Default: 63.
inner zone:
Enter dual band offset: dual_band_offset Optional. -63 to +63
Default: 0.

68P02901W23-T 6-471
Jan 2010
intave Chapter 6: CM database parameters

intave

Description

The intave parameter specifies the algorithm data needed for performing interference band
averaging and classification during idle channel interference processing.

CAUTION
The valid range of values for intave is 1 to 31. If a value greater then 31 is entered,
undetermined results may occur affecting service.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element intave <value> <location> <cell_desc>

chg_cell_element intave <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element intave <location> <cell_desc>

6-472 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 2 SACCH multiframes)

Valid range 1 to 31
1 2 SACCH multiframes
2 4 SACCH multiframes
... ...
... ...
... ...
31 62 SACCH multiframes
Default value 8

References

GSM specification Used to specify the Intave parameter as described in 5.08

This is a Motorola defined parameter.

68P02901W23-T 6-473
Jan 2010
inter_cell_handover_allowed Chapter 6: CM database parameters

inter_cell_handover_allowed

Description

The inter_cell_handover_allowed parameter specifies how internal and external inter-cell

handovers are managed at the BSC.

Internal inter-cell handovers are defined as handovers between cells in the same BSS.

External inter-cell handovers are defined as handovers between cells in different BSSs.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

achg_element inter_cell_handover_allowed <value> <location> <cell_desc>

chg_cell_element inter_cell_handover_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element inter_cell_handover_allowed <location> <cell_desc>

6-474 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 3
0 Outgoing Inter-cell handover is not enabled. The Handover
Required message is sent to the MSC.
1 Outgoing Inter-cell handover is enabled.
2 Outgoing internal Inter-cell handover is disabled. The
Handover Required message is not sent to the MSC.
3 Outgoing internal and external handovers are disabled and
the Handover Required message is not sent to the MSC.
Default value 1

References

GSM parameter EN_INTER_HO

GSM specification 8.08 - 3.1.7
8.08 - 5: handover definitions
12.20 - 5.2.8.18 enable BSS Handover Control - enable
Intercell Handover

68P02901W23-T 6-475
Jan 2010
inter_rat_enabled Chapter 6: CM database parameters

inter_rat_enabled

Description

The inter_rat_enabled parameter selects the mode for the BSS Inter-RAT handover feature.
Three modes are available on a per cell basis:
Idle.

Dedicated.

Combination of Idle and Dedicated.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The BSS Inter-RAT feature must be unrestricted.
Values 4 7 are only allowed when Enhanced 2G/3G
Handover feature is unrestricted.
early_classmark_sending must be set to 2 or 3.
phase2_classmark_allowed must be set to 2.

Syntax

Add/Change command strings

chg_element inter_rat_enabled <value> <location> <cell_desc>

chg_cell_element inter_rat_enabled <value> <cell_desc_opt>

NOTE
When changing this parameter to 4, 5, 6 or 7, a warning is issued if
early_classmark_sending is set to 0 or 1, or phase2_classmark_allowed is not
equal to 2.

6-476 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command strings

disp_cell <cell_id> [full]

disp_element inter_rat_enabled <location> <cell_desc>

copy_cell inter_rat_enabled

Values

Value type Integer

Valid range 0 to 7
0 Off
1 2G-3G idle
2 3G-2G dedicated
3 2G-3G idle and 3G-2G dedicated
4 2G-3G dedicated
5 2G-3G idle and 2G-3G dedicated.
6 3G-2G dedicated and 2G-3G dedicated
7 Idle and bi-directional dedicated
Default value 0

68P02901W23-T 6-477
Jan 2010
interband_ho_allowed Chapter 6: CM database parameters

interband_ho_allowed

Description

The interband_ho_allowed parameter specifies the handover frequencies for a cell.

Type A (no operator action required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter is not available unless the Multiband
Inter-cell Handover feature is enabled.
This parameter must include, at a minimum, the
frequency type for the cell. For example, if the cell has a
frequency_type of pgsm, then the interband_ho_allowed
parameter must include pgsm as a possible destination
frequency band for handovers.

Syntax

Change command string

chg_element interband_ho_allowed <value> <location> <cell_desc>

chg_cell_element interband_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element interband_ho_allowed <location> <cell_desc>

6-478 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 1 to 11
1 PGSM
2 EGSM
3 PGSM and EGSM
4 DCS1800
5 PGSM and DCS1800
6 EGSM and DCS1800
7 PGSM, EGSM, and DCS1800
8 PCS1900
9 PGSM and PCS1900
10 EGSM and PCS1900
11 PGSM, EGSM, and PCS1900
Default value If the Multiband Inter-cell Handover feature is enabled:
3 for PGSM and EGSM cells
4 for DCS1800 cells
8 for PCS1900 cells

68P02901W23-T 6-479
Jan 2010
interfer_bands Chapter 6: CM database parameters

interfer_bands

Description

The interfer_bands parameter specifies the limits for the interference categories (bands)
whose limit 0 to X5 is adjusted by Operations and Maintenance (O & M). The bands are:

Band 1 0 to X1
Band 2 X1 to X2
Band 3 X2 to X3
Band 4 X3 to X4
Band 5 X4 to X5

The BSS averages the interference level in unallocated timeslots as defined by the intave
parameter. The averaged results are then mapped into five interference categories whose
limits are adjusted.

An index number is required. Index values 0 to 4 correspond to bands X1 to X5.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies interfer_bands,0 must be less than or equal to
interfer_bands,1
interfer_bands,1 must be less than or equal to
interfer_bands,2
interfer_bands,2 must be less than or equal to
interfer_bands,3
interfer_bands,3 must be less than or equal to
interfer_bands,4

Syntax

Change command strings

chg_element interfer_bands,<index> <value> <location> <cell_desc>

chg_cell_element interfer_bands,<index> <value> <cell_desc>

6-480 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command strings

disp_cell <cell_id> full

disp_element interfer_bands,<index> <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 63 Represents -110 dBm to -47 dBm, as shown below:
0 -110 dBm
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm
Default value 63

NOTE
The system displays a warning message if interfer_bands,4 is changed to a value
less than 63.

References

GSM parameter INT_BOUND_X1, INT_BOUND_X2, INT_BOUND_X3,

INT_BOUND_X4, INT_BOUND_X5
GSM specification 5.08 - Appendix A
5.08 - 0-X5
12.20 - 5.2.8.10 - Interference Averaging Process -
thresholds
8.08

68P02901W23-T 6-481
Jan 2010
interfer_ho_allowed Chapter 6: CM database parameters

interfer_ho_allowed

Description

The interfer_ho_allowed parameter disables or enables handovers due to interference.

Type A (no operator action required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command string

add_cell <gsm_cell_id> <location>

chg_element interfer_ho_allowed <value> <location> <cell_desc>
chg_cell_element interfer_ho_allowed <value><cell_desc>

Display command strings

disp_cell <cell_id> [full]

disp_element interfer_ho_allowed <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

6-482 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference intra_cell_handover_allowed

intra_cell_handover_allowed

Description

This parameter disables or enables intra-cell handovers under two conditions: to begin the
handover or to begin the handover when co-channel interference is suspected. Intra-cell
handovers are defined as handovers within the same cell.

BSS support is optional. If the BSS does not support an internal intra-cell handover, it is initiated
by sending a Handover Required message.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element intra_cell_handover_allowed <value> <location> <cell_desc>

chg_cell_element intra_cell_handover_allowed <value> <cell_desc>

Display command strings

disp_cell <cell_id> [full]

disp_element intra_cell_handover_allowed <location> <cell_desc>

68P02901W23-T 6-483
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 2
0 Intra-cell handovers are performed by the BSS. These
calls are included as target cells in a Handover Required
message to the MSC.
1 The BSS performs Intra-cell handovers. The MSC is notified
with a Handover Performed message.
2 Intra-cell handovers are disabled and the Handover
Required message is not sent to the MSC.
Default value 1

References

GSM parameter EN_INTRA_HO, EN_INCOM_HO

GSM specification
5.08 - Appendix A - 4.1 and 4.2
8.08 - 3.1.6
8.08 - 5: handover definitions
12.20 - 5.2.8.18 enable BSS Handover Control - enable
Intracell Handover

6-484 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ip_address

ip_address

{26638}

Description

The ip_address parameter identifies the valid class A/B/C network IP Address for the PCU
Ethernet GBL.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the Gb over IP
feature is unrestricted and the Gb mode is set to static IP
mode.

Syntax

Equip command strings

equip <location> gbl

Unequip command strings

unequip <location> gbl <gbl id>

Display command strings

disp_equipment <location> gbl <gbl id>

Modify command strings

modify_value pcu ip_address <value> gbl <gbl id>

68P02901W23-T 6-485
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 128.0.0.0 to 223.255.255.255 and 0 to 126.255.255.255
128.0.0.0 to Minimum
223.255.255.255
0 to 126.255.255.255 Maximum
Default value N/A

6-486 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference isp_enabled

isp_enabled

{34452}

Description

The isp_enabled parameter indicates whether the functionality of Intelligent Selective Paging
is enabled. This parameter can be accessed and updated both in and out of sysgen mode
without warning.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This element can only be modified if the Intelligent
Selective Paging feature is unrestricted.

Syntax

Change command string

chg_cell_element isp_enabled <value> <cell_desc>

chg_element isp_enabled <value> <location> <cell_desc>

Display command string

disp_element isp_enabled <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-487
Jan 2010
ksw_config Chapter 6: CM database parameters

ksw_config

Description

The ksw_config parameter specifies the timeslot portion (1024 timeslots) of the dual redundant
TDM highway controlled by a KSW pair. The switch fabric can be extended in 1024 timeslot
increments to a maximum of 4096 timeslots by adding KSW pairs. To provide 4096 timeslots
requires four KSW pairs with each KSW pair handling a 1024 timeslot portion of the TDM
highway.

Index numbers are used to specify the four highway portions. The index values are set when
the system is installed. The range of index values is 0 to 3.

CAUTION
Do not change the values for this parameter unless a KSW is added or removed.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies Changing this parameter is not allowed at M-Cell sites.

Syntax

Change command string

chg_ksw_config <location> <ksw_pair> <highway1> <highway2> <highway3> <highway4>

Display command string

disp_element ksw_config,<index> <location>

NOTE
For more information, refer to the chg_ksw_config descriptions and examples in
Chapter 3 Device/function related commands.

6-488 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (Index number)

Valid range 0 to 3
0 Highway portion 0 (0-1023 timeslots)
1 Highway portion 1 (1024-2047 timeslots)
2 Highway portion 2 (2048-3071 timeslots)
3 Highway portion 3 (3072-4095 timeslots)
Default value None

68P02901W23-T 6-489
Jan 2010
l_rxlev_dl_h Chapter 6: CM database parameters

l_rxlev_dl_h

Description

The l_rxlev_dl_h parameter specifies the handover thresholds for the lower receive level (rxlev)
downlink. This threshold is checked to determine if a handover condition exists.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element l_rxlev_dl_h <value> <location> <cell_desc>

chg_cell_element l_rxlev_dl_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxlev_dl_h <location> <cell_desc>

6-490 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 dBm)

Valid range 0 to 63 Represents -110 dBm to -47 dBm, as shown below:
0 -110 dBm and lower
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm and higher
Default value 10

References

GSM parameter L_RXLEV_DL_H

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-491
Jan 2010
l_rxlev_dl_p Chapter 6: CM database parameters

l_rxlev_dl_p

Description

The l_rxlev_dl_p parameter specifies the lower downlink limit for the signal strength of the
serving cell. This threshold is checked to determine if BTS power should be increased.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Must be less than u_rxlev_dl_p

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element l_rxlev_dl_p <value> <location> <cell_desc>

chg_cell_element l_rxlev_dl_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxlev_dl_p <location> <cell_desc>

6-492 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 dBm)

Valid range 0 to 63 Represents -110 dBm to -47 dBm, as shown below:
0 -110 dBm and lower
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm and higher
Default value 30

References

GSM parameter L_RXLEV_DL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-493
Jan 2010
l_rxlev_ul_h Chapter 6: CM database parameters

l_rxlev_ul_h

Description

The l_rxlev_ul_h parameter specifies the handover threshold for the lower receive level (rxlev)
uplink. This threshold is checked to determine if a handover condition exists.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element l_rxlev_ul_h <value> <location> <cell_desc>

chg_cell_element l_rxlev_ul_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxlev_ul_h <location> <cell_desc>

6-494 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 dBm)

Valid range 0 to 63 Represents -110 dBm to -47 dBm, as shown below:
0 -110 dBm and lower
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm and higher
Default value 10

References

GSM parameter L_RXLEV_UL_H

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-495
Jan 2010
l_rxlev_ul_p Chapter 6: CM database parameters

l_rxlev_ul_p

Description

The l_rxlev_ul_p parameter specifies the lower uplink limit for the signal strength of the mobile.
Check this threshold to determine if increase in MS power is required.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes

Dependencies Must be less than u_rxlev_ul_p

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element l_rxlev_ul_p <value> <location> <cell_desc>

chg_cell_element l_rxlev_ul_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxlev_ul_p <location> <cell_desc>

6-496 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 1 dBm)

Valid range 0 to 63 Represents -110 dBm to -47 dBm, as shown below:
0 -110 dBm and lower
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm and higher
Default value 30

References

GSM parameter L_RXLEV_UL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-497
Jan 2010
l_rxqual_dl_h Chapter 6: CM database parameters

l_rxqual_dl_h

Description

The l_rxqual_dl_h parameter specifies the handover control threshold for the lower Received
(Rx) quality downlink. This threshold is checked to determine if a handover condition exists.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc.
See also data_qual_enabled, hop_qual_enabled.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element l_rxqual_dl_h <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_dl_h <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0
0 to 7 QBand units If alt_qual_proc = 1
Default value 453 453 BER if alt_qual_proc = 0
5 5 QBand units if alt_qual_proc = 1

6-498 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter L_RXQUAL_DL_H

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-499
Jan 2010
l_rxqual_dl_h_amr_fr Chapter 6: CM database parameters

l_rxqual_dl_h_amr_fr

Description

The l_rxqual_dl_h_amr_fr parameter specifies the handover control threshold for the full-rate
lower received quality (rxqual) downlink. This threshold is checked to determine if a handover
condition exists.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
This parameter can be changed only at an AMR-capable
BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_dl_h_amr_fr <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_h_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_dl_h_amr_fr <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 226 226 BER if alt_qual_proc = 0
4 4 QBand units if alt_qual_proc = 1

6-500 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference l_rxqual_dl_h_data

l_rxqual_dl_h_data

Description

The l_rxqual_dl_h_data parameter specifies the handover control threshold for the lower
Received (Rx) quality downlink, for data transmissions only (for example modem-to-modem
calls). This threshold is checked to determine if a handover condition exists. This threshold is
enabled and set to be used when data is being transmitted, by use of the data_qual_enabled
parameter in a chg_cell_element command. In this situation it is used instead of the
l_rxqual_dl_h threshold value, as set in the add_cell command.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc

Syntax

Change command strings

chg_element l_rxqual_dl_h_data <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_h_data <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_dl_h_data <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0
0 to 7 QBand units If alt_qual_proc = 1

Continued

68P02901W23-T 6-501
Jan 2010
References Chapter 6: CM database parameters

Default value 0 0 BER if alt_qual_proc = 0

4 4 QBand units if alt_qual_proc = 1

References

GSM parameter L_RXQUAL_DL_H

GSM specification 5.08 - Appendix A - Table 1

6-502 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference l_rxqual_dl_h_hopping

l_rxqual_dl_h_hopping

Description

The l_rxqual_dl_h_hopping parameter specifies the handover control threshold for the lower
Received (Rx) quality downlink, for hopping calls only. This threshold is checked to determine if
a handover condition exists. This threshold is enabled and set to be used for hopping calls, by
use of the hop_qual_enabled parameter in a chg_cell_element command. In this situation it is
used instead of the l_rxqual_dl_h threshold value, as set in the add_cell command.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc

Syntax

Change command strings

chg_element l_rxqual_dl_h_hopping <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_h_hopping <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_dl_h_hopping <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0
0 to 7 QBand units If alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
4 4 QBand units if alt_qual_proc = 1

68P02901W23-T 6-503
Jan 2010
References Chapter 6: CM database parameters

References

GSM parameter L_RXQUAL_DL_H

GSM specification 5.08 - Appendix A - Table 1

6-504 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference l_rxqual_dl_h_hopping_amr_fr

l_rxqual_dl_h_hopping_amr_fr

Description

The l_rxqual_dl_h_hopping_amr_fr parameter specifies the handover control threshold for

the lower Received (Rx) quality downlink, for hopping calls only. This threshold is checked
to determine if a handover condition exists.

NOTE
This threshold is enabled and set to be used for hopping calls with the
chg_cell_element command and the hop_qual_enabled parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
This parameter can be changed only at an AMR-capable
BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_dl_h_hopping_amr_fr <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_h_hopping_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_dl_h_hopping_amr_fr <location> <cell_desc>

68P02901W23-T 6-505
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
0 0 QBand units if alt_qual_proc = 1

6-506 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference l_rxqual_dl_h_hopping_hr

l_rxqual_dl_h_hopping_hr

Description

The l_rxqual_dl_h_hopping_hr parameter specifies the handover control threshold for the
lower Received (Rx) quality downlink, for hopping calls only. This threshold is checked to
determine if a handover condition exists.

NOTE
This threshold is enabled and set to be used for hopping calls with the
chg_cell_element command and the hop_qual_enabled parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must
be unrestricted.
This parameter can be changed at any AMR/GSM HR
capable BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_dl_h_hopping_hr <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_h_hopping_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element l_rxqual_dl_h_hopping_hr <location> <cell_desc>

68P02901W23-T 6-507
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 113 BER if alt_qual_proc = 0
3 QBand units if alt_qual_proc = 1

6-508 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference l_rxqual_dl_h_hr

l_rxqual_dl_h_hr

Description

The l_rxqual_dl_h_hr parameter specifies the handover control threshold for the half-rate
lower received quality (rxqual) downlink. This threshold is checked to determine if a handover
condition exists.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must be
unrestricted.
This parameter can be changed at any AMR/GSM HR
capable BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_dl_h_hr <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_h_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element l_rxqual_dl_h_hr <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 113 BER if alt_qual_proc = 0
3 QBand units if alt_qual_proc = 1

68P02901W23-T 6-509
Jan 2010
l_rxqual_dl_p Chapter 6: CM database parameters

l_rxqual_dl_p

Description

The l_rxqual_dl_p parameter specifies the lower downlink limit for the signal quality of the
serving cell. This threshold is checked to determine if BTS power should be increased.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc
Must be greater than u_rxqual_dl_p
See also data_qual_enabled, hop_qual_enabled

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element l_rxqual_ul_p <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_p <value> <cell_desc>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_dl_p <location> <cell_desc>

6-510 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0
0 to 7 QBand units If alt_qual_proc = 1
Default value 256 256 BER if alt_qual_proc = 0
4 4 QBand units if alt_qual_proc = 1

NOTE
Dependencies affect the actual range , thus range is never set to 0.

References

GSM parameter L_RXQUAL_DL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-511
Jan 2010
l_rxqual_dl_p_amr_fr Chapter 6: CM database parameters

l_rxqual_dl_p_amr_fr

Description

The l_rxqual_dl_p_amr_fr parameter specifies the lower downlink limit for the signal quality of
the serving cell. This threshold is checked to determine if the BTS power should be increased.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
This parameter can be changed only at an AMR-capable
BTS site.
This parameter is prompted when alt_qual_proc is
changed.
This parameter must be greater than u_rxqual_dl_p.

Syntax

Add/Change command strings

chg_element l_rxqual_dl_p_amr_fr <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_p_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_dl_p_amr_fr <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 113 113 BER if alt_qual_proc = 0
3 3 QBand units if alt_qual_proc = 1

6-512 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

NOTE
Dependencies affect the actual range , thus range is never set to 0.

68P02901W23-T 6-513
Jan 2010
l_rxqual_dl_p_data Chapter 6: CM database parameters

l_rxqual_dl_p_data

Description

The l_rxqual_dl_p_data parameter specifies the lower downlink limit for the signal quality
of the serving cell, for data transmissions only (for example modem-to-modem calls). This
threshold is checked to determine if BTS power should be increased. This threshold is enabled
and set to be used when data is being transmitted, by use of the data_qual_enabled parameter
in a chg_cell_element command. In this situation it is used instead of the l_rxqual_dl_p
threshold value, as set in the add_cell command.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc

Syntax

Change command strings

chg_element l_rxqual_dl_p_data <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_p_data <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_dl_p_data <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0
0 to 7 QBand units If alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
4 4 QBand units if alt_qual_proc = 1

6-514 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter L_RXQUAL_DL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-515
Jan 2010
l_rxqual_dl_p_hopping Chapter 6: CM database parameters

l_rxqual_dl_p_hopping

Description

The l_rxqual_dl_p_hopping parameter specifies the lower downlink limit for the signal quality
of the serving cell, for hopping calls only. This threshold is checked to determine if BTS power
should be increased. This threshold is enabled and set to be used for hopping calls, by use of the
hop_qual_enabled parameter in a chg_cell_element command. In this situation it is used
instead of the l_rxqual_dl_p threshold value, as set in the add_cell command.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc

Syntax

Change command strings

chg_element l_rxqual_dl_p_hopping <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_p_hopping <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_dl_p_hopping <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0
0 to 7 QBand units If alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
4 4 QBand units if alt_qual_proc = 1

6-516 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter L_RXQUAL_DL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-517
Jan 2010
l_rxqual_dl_p_hopping_amr_fr Chapter 6: CM database parameters

l_rxqual_dl_p_hopping_amr_fr

Description

The l_rxqual_dl_p_hopping_amr_fr parameter specifies the lower downlink limit for the signal
quality of the serving cell, for hopping cells only. This threshold is checked to determine if BTS
power should be increased.

NOTE
This threshold is enabled and set to be used for hopping calls with the
chg_cell_element command and the hop_qual_enabled parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
This parameter can be changed only at an AMR-capable
BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_dl_p_hopping_amr_fr <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_p_hopping_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_dl_p_hopping_amr_fr <location> <cell_desc>

6-518 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
0 0 QBand units if alt_qual_proc = 1

68P02901W23-T 6-519
Jan 2010
l_rxqual_dl_p_hopping_hr Chapter 6: CM database parameters

l_rxqual_dl_p_hopping_hr

Description

The l_rxqual_dl_p_hopping_hr parameter specifies the lower downlink limit for the signal
quality of the serving cell, for hopping cells only. This threshold is checked to determine if BTS
power should be increased.

NOTE
This threshold is enabled and set to be used for hopping calls with the
chg_cell_element command and the hop_qual_enabled parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must
be unrestricted.
This parameter can be changed at any AMR/GSM HR
capable BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_dl_p_hopping_hr <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_p_hopping_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element l_rxqual_dl_p_hopping_hr <location> <cell_desc>

6-520 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 57 BER if alt_qual_proc = 0
2 QBand units if alt_qual_proc = 1

68P02901W23-T 6-521
Jan 2010
l_rxqual_dl_p_hr Chapter 6: CM database parameters

l_rxqual_dl_p_hr

Description

The l_rxqual_dl_p_hr parameter specifies the lower downlink limit for the signal quality of the
serving cell. This threshold is checked to determine if the BTS power should be increased.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must be
unrestricted.
This parameter can be changed at any AMR/GSM HR
capable BTS site.
This parameter is prompted when alt_qual_proc is
changed.
This parameter must be greater than u_rxqual_dl_p_hr.

Syntax

Add/Change command strings

chg_element l_rxqual_dl_p_hr <value> <location> <cell_desc>

chg_cell_element l_rxqual_dl_p_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element l_rxqual_dl_p_hr <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 57 BER if alt_qual_proc = 0
2 QBand units if alt_qual_proc = 1

6-522 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

NOTE
Dependencies affect the actual range, thus range is never set to 0.

68P02901W23-T 6-523
Jan 2010
l_rxqual_ul_h Chapter 6: CM database parameters

l_rxqual_ul_h

Description

The l_rxqual_ul_h parameter specifies the handover control threshold for the receive (Rx)
quality uplink. This threshold is checked to determine if a handover condition exists.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc
See also: data_qual_enabled, hop_qual_enabled

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element l_rxqual_ul_h <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_ul_h <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0
0 to 7 QBand units If alt_qual_proc = 1
Default value 453 453 BER if alt_qual_proc = 0
5 5 QBand units if alt_qual_proc = 1

6-524 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter L_RXQUAL_UL_H

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-525
Jan 2010
l_rxqual_ul_h_amr_fr Chapter 6: CM database parameters

l_rxqual_ul_h_amr_fr

Description

The l_rxqual_ul_h_amr_fr parameter specifies the handover control threshold for the receive
quality (rxqual) uplink. This threshold is checked to determine if a handover condition exists.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
This parameter can be changed only at an AMR-capable
BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_ul_h_amr_fr <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_h_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_ul_h_amr_fr <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 453 453 BER if alt_qual_proc = 0
5 5 QBand units if alt_qual_proc = 1

6-526 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference l_rxqual_ul_h_data

l_rxqual_ul_h_data

Description

The l_rxqual_ul_h_data parameter specifies the handover control threshold for the lower
received quality (rxqual) uplink, for data transmissions only (for example modem-to-modem
calls). This threshold is checked to determine if a handover condition exists. This threshold is
enabled and set to be used when data is being transmitted, by use of the data_qual_enabled
parameter in a chg_cell_element command. In this situation it is used instead of the
l_rxqual_ul_h threshold value, as set in the add_cell command.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc

Syntax

Change command strings

chg_element l_rxqual_ul_h_data <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_h_data <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_ul_h_data <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0
0 to 7 QBand units If alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
5 5 QBand units if alt_qual_proc = 1

68P02901W23-T 6-527
Jan 2010
References Chapter 6: CM database parameters

References

GSM parameter L_RXQUAL_UL_H

GSM specification 5.08 - Appendix A - Table 1

6-528 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference l_rxqual_ul_h_hopping

l_rxqual_ul_h_hopping

Description

The l_rxqual_ul_h_hopping parameter specifies the handover control threshold for the lower
received quality (rxqual) uplink, for hopping calls only. This threshold is checked to determine if
a handover condition exists. This threshold is enabled and set to be used for hopping calls, by
use of the hop_qual_enabled parameter in a chg_cell_element command. In this situation it is
used instead of the l_rxqual_ul_h threshold value, as set in the add_cell command.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc

Syntax

Change command string

chg_element l_rxqual_ul_h_hopping <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_h_hopping <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_ul_h_hopping <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
5 5 QBand units if alt_qual_proc = 1

68P02901W23-T 6-529
Jan 2010
References Chapter 6: CM database parameters

References

GSM parameter L_RXQUAL_UL_H

GSM specification 5.08 - Appendix A - Table 1

6-530 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference l_rxqual_ul_h_hopping_amr_fr

l_rxqual_ul_h_hopping_amr_fr

Description

The l_rxqual_ul_h_hopping_amr_fr parameter specifies the handover control threshold for

the lower received quality (rxqual) uplink, for hopping calls only. This threshold is checked
to determine if a handover condition exists.

NOTE
This threshold is enabled and set to be used for hopping calls with the
chg_cell_element command and the hop_qual_enabled parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
This parameter can be changed only at an AMR-capable
BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_ul_h_hopping_amr_fr <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_h_hopping_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_ul_h_hopping_amr_fr <location> <cell_desc>

68P02901W23-T 6-531
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
0 0 QBand units if alt_qual_proc = 1

6-532 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference l_rxqual_ul_h_hopping_hr

l_rxqual_ul_h_hopping_hr

Description

The l_rxqual_ul_h_hopping_hr parameter specifies the handover control threshold for the
lower received quality (rxqual) uplink, for hopping calls only. This threshold is checked to
determine if a handover condition exists.

NOTE
This threshold is enabled and set to be used for hopping calls with the
chg_cell_element command and the hop_qual_enabled parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must be
unrestricted.
This parameter can be changed at any AMR/GSM HR
capable BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_ul_h_hopping_hr <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_h_hopping_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element l_rxqual_ul_h_hopping_hr <location> <cell_desc>

68P02901W23-T 6-533
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 113 BER if alt_qual_proc = 0
3 Band units if alt_qual_proc = 1

6-534 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference l_rxqual_ul_h_hr

l_rxqual_ul_h_hr

Description

The l_rxqual_ul_h_hr parameter specifies the handover control threshold for the lower Received
(Rx) quality uplink. This threshold is checked to determine if a handover condition exists.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must
be unrestricted.
This parameter can be changed at any AMR/GSM HR
capable BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_ul_h_hr <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_h_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element l_rxqual_ul_h_hr <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 113 BER if alt_qual_proc = 0
3 QBand units if alt_qual_proc = 1

68P02901W23-T 6-535
Jan 2010
l_rxqual_ul_p Chapter 6: CM database parameters

l_rxqual_ul_p

Description

The l_rxqual_ul_p parameter specifies the lower uplink limit of the signal quality of the MS.
Check this threshold to determine if increase in MS power is required.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc
Must be greater than u_rxqual_ul_p
See also data_qual_enabled, hop_qual_enabled

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element l_rxqual_ul_p <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_p <value> <cell_desc>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_ul_p <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 226 226 BER if alt_qual_proc = 0
4 4 QBand units if alt_qual_proc = 1

6-536 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

NOTE
Dependencies affect the actual range, thus range is never set to 0.

References

GSM parameter L_RXQUAL_UL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-537
Jan 2010
l_rxqual_ul_p_amr_fr Chapter 6: CM database parameters

l_rxqual_ul_p_amr_fr

Description

The l_rxqual_ul_p_amr_fr parameter specifies the lower uplink limit of the signal quality of the
MS. Check this threshold to determine if increase in MS power is required.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
This parameter can be changed only at an AMR-capable
BTS site.
This parameter is prompted when alt_qual_proc is
changed.
This parameter must be greater than u_rxqual_ul_p.

Syntax

Add/Change command strings

chg_element l_rxqual_ul_p_amr_fr <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_p_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_ul_p_amr_fr <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1

Default value 226 226 BER if alt_qual_proc = 0

4 4 QBand units if alt_qual_proc = 1

6-538 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

NOTE
Dependencies affect the actual range, thus range is never set to 0.

68P02901W23-T 6-539
Jan 2010
l_rxqual_ul_p_data Chapter 6: CM database parameters

l_rxqual_ul_p_data

Description

The l_rxqual_ul_p_data parameter specifies the lower uplink limit for the signal quality of the
serving cell, for data transmissions only (for example modem-to-modem calls). Check this
threshold to determine if increase in MS power is required. This threshold is enabled and set
to be used when data is being transmitted, by use of the data_qual_enabled parameter in a
chg_cell_element command. In this situation it is used instead of the l_rxqual_ul_p threshold
value, as set in the add_cell command.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc

Syntax

Change command strings

chg_element l_rxqual_ul_p_data <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_p_data <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_ul_p_data <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
5 5 QBand units if alt_qual_proc = 1

6-540 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter L_RXQUAL_UL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-541
Jan 2010
l_rxqual_ul_p_hopping Chapter 6: CM database parameters

l_rxqual_ul_p_hopping

Description

The l_rxqual_ul_p_hopping parameter specifies the lower uplink limit for the signal quality
of the serving cell, for hopping calls only. Check this threshold to determine if increase in MS
power is required. This threshold is enabled and set to be used for hopping calls, by use of the
hop_qual_enabled parameter in a chg_cell_element command. In this situation it is used
instead of the l_rxqual_dl_p threshold value, as set in the add_cell command.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc

Syntax

Change command strings

chg_element l_rxqual_ul_p_hopping <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_p_hopping <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_ul_p_hopping <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
5 5 QBand units if alt_qual_proc = 1

6-542 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter L_RXQUAL_UL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-543
Jan 2010
l_rxqual_ul_p_hopping_amr_fr Chapter 6: CM database parameters

l_rxqual_ul_p_hopping_amr_fr

Description

The l_rxqual_ul_p_hopping_amr_fr parameter specifies the lower uplink limit for the signal
quality of the serving cell, for hopping calls only. This threshold is checked to determine if BTS
power should be increased.

NOTE
This threshold is enabled and set to be used for hopping calls with the
chg_cell_element command and the hop_qual_enabled parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature must be unrestricted.
This parameter can be changed only at an AMR-capable
BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_ul_p_hopping_amr_fr <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_p_hopping_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element l_rxqual_ul_p_hopping_amr_fr <location> <cell_desc>

6-544 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 0 0 BER if alt_qual_proc = 0
0 0 QBand units if alt_qual_proc = 1

68P02901W23-T 6-545
Jan 2010
l_rxqual_ul_p_hopping_hr Chapter 6: CM database parameters

l_rxqual_ul_p_hopping_hr

Description

The l_rxqual_ul_p_hopping_hr parameter specifies the lower uplink limit for the signal quality
of the serving cell, for hopping calls only. This threshold is checked to determine if BTS power
should be increased.

NOTE
This threshold is enabled and set to be used for hopping calls with the
chg_cell_element command and the hop_qual_enabled parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must
be unrestricted.
This parameter can be changed at any AMR/GSM HR
capable BTS site.
This parameter is prompted when alt_qual_proc is
changed.

Syntax

Add/Change command strings

chg_element l_rxqual_ul_p_hopping_hr <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_p_hopping_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

6-546 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 57 BER if alt_qual_proc = 0
2 QBand units if alt_qual_proc = 1

68P02901W23-T 6-547
Jan 2010
l_rxqual_ul_p_hr Chapter 6: CM database parameters

l_rxqual_ul_p_hr

Description

The l_rxqual_ul_p_hr parameter specifies the lower uplink limit of the signal quality of the MS.
Check this threshold to determine if increase in MS power is required.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must be
unrestricted.
This parameter can be changed at any AMR/GSM HR
capable BTS site.
This parameter is prompted for when alt_qual_proc is
changed.
This parameter must be greater than u_rxqual_ul_p_hr.

Syntax

Add/Change command strings

chg_element l_rxqual_ul_p_hr <value> <location> <cell_desc>

chg_cell_element l_rxqual_ul_p_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element l_rxqual_ul_p_hr <location> <cell_desc>

6-548 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0
0 to 7 QBand units if alt_qual_proc = 1
Default value 57 BER if alt_qual_proc = 0
2 QBand units if alt_qual_proc = 1

NOTE
Dependencies affect the actual range, thus range is never set to 0.

68P02901W23-T 6-549
Jan 2010
land_layer1_mode Chapter 6: CM database parameters

land_layer1_mode

Description

The land_layer1_mode parameter specifies the layer 1 mode of the land network TELCO
connection type. Only the 2.048 Mbit/s - CEPT format is currently supported. All BTS site values
are set to the BSC value.

This parameter may be set only while in the initial SYSGEN mode. All BTS site values are set to
BSC (site 0) value when the database is loaded initially.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The value of this parameter may be specified for the BSC
(site 0) only while in the initial SYSGEN mode.
The value of this parameter may not be changed if any
MSIs or BTS sites are equipped. If the GPRS feature is
unrestricted and a PCU is equipped, this parameter must
be set to 0 (E1).
Operator actions Place the system in the initial SYSGEN ON mode and clear
the database before using the chg_element command to
change this parameter.

Syntax

Change command string

chg_element land_layer1_mode <value> <location>

Display command string

disp_element land_layer1_mode <location>

Values

Value type Boolean

Valid range 0 or 1
0 2.048 Mbit/s - CEPT format (E1)
Default value 0

6-550 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference last_rsl_alarm_persistency

last_rsl_alarm_persistency

Description

The parameter last_rsl_alarm_persistency indicates whether the functionality of the last

RSL alarm persistency is enabled or disabled.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell numbers required No
Dependencies This element can be modified inside and outside of SYSGEN
mode.

Syntax

Change command string

chg_element last_rsl_alarm_persistency <value> <location>

Values

Value type Integer

Valid range 0 to 1 0 Disable Disables the functionality of Last RSL
alarm Persistency.
1 Enable Enables the functionality of Last RSL
alarm Persistency.
Default value 0

68P02901W23-T 6-551
Jan 2010
layer_number Chapter 6: CM database parameters

layer_number

Description

The layer_number parameter specifies the serving cell as being a macrocell, microcell, or
picocell.

When an RXQUAL handover condition exists, the system attempts to hand over a call in the
microcell layer to another cell in the microcell layer.

This parameter specifies the layer for a cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter is unavailable if the Microcellular option
has not been purchased.

Syntax

Change command strings

chg_element layer_number <value> <location> <cell_desc>

chg_cell_element layer_number <value> <cell_desc_opt>

Display command string

disp_element layer_number <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 2
0 Macrocell
1 Microcell
2 Picocell
Default value 0

6-552 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_called_pci

lb_int_called_pci

Description

The lb_int_called_pci (Lb-interface PC included called party) flag specifies if the point code is
included in the called party address in the SCCP messages that travel over the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_called_pci <value> <location>

Display command string

disp_element lb_int_called_pci <location>

Values

Value type Boolean

Valid range 0 or 1
0 DCP not included
1 DCP included
Default value None

68P02901W23-T 6-553
Jan 2010
lb_int_calling_pci Chapter 6: CM database parameters

lb_int_calling_pci

Description

The lb_int_calling_pci (Lb-interface PC included calling party) flag specifies if the point code is
included in the calling party address in the SCCP messages that travel over the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_calling_pci <value> <location>

Display command string

disp_element lb_int_calling_pci <location>

Values

Value type Boolean

Valid range 0 or 1
0 Point code not included
1 Point code included
Default value None

6-554 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_cr_calling

lb_int_cr_calling

Description

The lb_int_cr_calling parameter specifies if the calling party address is included in the SCCP
connection request messages that travel over the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_cr_calling <value> <location>

Display command string

disp_element lb_int_cr_calling <location>

Values

Value type Boolean (milliseconds)

Valid range 0 or 1
0 Not included
1 Included
Default value 0

68P02901W23-T 6-555
Jan 2010
lb_int_dpc Chapter 6: CM database parameters

lb_int_dpc

Description

The lb_int_dpc (Lb-interface DPC) is the point code of a BSS-based SMLC.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.
For a live system, the lb_int_dpc must not be the same
value as the opc.
For the ss7_mode element to be modified from ANSI to
CCITT, the lb_int_dpc parameter must be within range for
the CCITT ss7_mode setting.
The valid values for this element are dependent upon the
value of the ss7_mode element.

Syntax

Change command string

chg_element lb_int_dpc <value> <location>

Display command string

disp_element lb_int_dpc <location>

Values

Value type Integer

Valid range ss7_mode = 0: 0 to 16383 ss7_mode = 1: 0 to 16777215
Default value None

6-556 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_global_reset_repetitions

lb_int_global_reset_repetitions

Description

The lb_int_global_reset_repetitions parameter specifies the number of times the global reset
procedure on the Lb-interface is allowed to repeat before an alarm is generated.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_global_reset_repetitions <value> <location>

Display command string

disp_element lb_int_global_reset_repetitions <location>

Values

Value type Integer

Valid range 0 to 255
Default value 0

References

GSM specification TS GSM 8.08

68P02901W23-T 6-557
Jan 2010
lcs_mode Chapter 6: CM database parameters

lcs_mode

Description

The lcs_mode parameter specifies the Location Services mode of the BSS.

NOTE
This parameter can be modified only when the system is in the SYSGEN ON mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies See Dependencies checked during database
verification list and Dependencies checked during
lcs_mode modification list for the dependencies of this
parameter.
Dependencies checked
during database verification

If database verification determines that the location services feature is enabled and
early_classmark_sending is not enabled across both the A-interface and the Air-interface,
the database is not created, and the following error message is displayed:

ERROR: LCS requires early_classmark_sending to be enabled across both the

A and Air Interfaces.

Errors were found in the database.

REJECTING SYSGEN_OFF REQUEST.

If database verification determines that the location services feature is enabled and
phase2_classmark_allowed is not configured to support multiband, the database is not
created, and the following error message is displayed:

ERROR: LCS requires phase2_classmark_allowed to be configured to support

multiband.

Errors were found in the database.

REJECTING SYSGEN_OFF REQUEST.

6-558 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Description

If database verification determines that the BSS is not configured to support a BSS-based
SMLC and one or more LMTL devices are equipped, the database is not created, and
the following error message is displayed:

ERROR: For setups with no BSS-based SMLC support, LMTLs cannot exist and LCFs
cannot manage LMTLs.

Errors were found in the database.

REJECTING SYSGEN_OFF REQUEST.

If database verification determines that the BSS is not configured to support a BSS-based
SMLC and one or more LCFs are configured to manage LMTL devices, the database is not
created, and the following error message is displayed:

ERROR: For setups with no BSS based SMLC support, LMTLs cannot exist and LCFs
cannot manage LMTLs.

Errors were found in the database.

REJECTING SYSGEN_OFF REQUEST.

If database verification determines that the location services feature is restricted and the
LCS mode element indicates that the location services feature is enabled, the database is
not created, and the following error message is displayed:

ERROR: When LCS is restricted lcs_mode must be 0.

Errors were found in the database.

REJECTING SYSGEN_OFF REQUEST.

Dependencies checked
during lcs_mode modification

68P02901W23-T 6-559
Jan 2010
Syntax Chapter 6: CM database parameters

If the operator attempts to change the LCS mode element from a BSS-based SMLC
configuration to either an NSS-based SMLC configuration or an LCS-disabled configuration,
and one or more LMTLs are equipped, the command is rejected, and the following error
message is displayed:

ERROR: For setups with no BSS-based SMLC support, LMTLs cannot exist and LCFs
cannot manage LMTLs.

COMMAND REJECTED

If an operator attempts to change the LCS mode element from a BSS-based SMLC
configuration to either an NSS-based SMLC configuration or an LCS disabled configuration,
and one or more LCFs are configured to manage LMTLs, the command is rejected, and
the following error message is displayed:

ERROR: For setups with no BSS-based SMLC support, LMTLs cannot exist and LCFs
cannot manage LMTLs.

COMMAND REJECTED

If an operator attempts to change the LCS mode element to an LCS enabled setting, 1
or 2, and the location services feature is restricted, the command is rejected, and the
following message is displayed:

ERROR: When LCS is restricted lcs_mode must be 0.

COMMAND REJECTED

Syntax

Change command string

chg_element lcs_mode <value> <location>

Display command string

disp_element lcs_mode <location>

Values

Value type Integer

Valid range 0 Location services disabled; SMLC not supported.
1 Location services enabled; BSC supports an NSS-based
SMLC.
2 Location services enabled; BSC supports an BSS-based
SMLC.
Default value 0

6-560 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference link_about_to_fail

link_about_to_fail

Description

The link_about_to_fail parameter specifies the number of undecoded SACCH frames before
the BSS and MS are increased to full power. The number of SACCH frames is calculated by
subtracting the number of undecoded SACCH frames represented by the value entered for
this parameter from the number of undecoded SACCH frames represented by the link_fail
parameter.

For example, if link_fail is set to 5 (24 SACCH frames) and link_about_to_fail is set to 1 (4
SACCH frames), the BSS and MS are increased to full power when 20 undecoded SACCH
frames are received.

Full power is specified by the max_tx_bts parameter for the downlink power; and max_tx_ms
or max power capability of the MS for uplink power.

This provides a method for improving the quality of a call by increasing the power of the signal
transmitted by the BSS to an MS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies link_about_to_fail must be less than link_fail

Syntax

Change command strings

chg_element link_about_to_fail <value> <location> <cell_desc>

chg_cell_element link_about_to_fail <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element link_about_to_fail <location> <cell_desc>

68P02901W23-T 6-561
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (1 step = 4 SACCH frames)

Valid range 0 to 15 Represents the number of SACCH frames as shown below:
0 0 SACCH frames
1 4 SACCH frames
2 8 SACCH frames
... ...
... ...
... ...
15 60 SACCH frames
Default value 2

References

Internal name THRES_PC_RLF

This is a Motorola defined parameter.

6-562 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference link_fail

link_fail

Description

The link_fail parameter specifies the number of lost SACCH multiframes before a loss of
SACCH is reported to Abis.

This parameter is also known as the T100_TIMER.

The radio link failure criterion is based on the radio link counter S. S is set to the value specified
for link_fail. If the BSS is unable to decode a SACCH message, the count in S is decremented
by 1. When the BSS successfully decodes a SACCH message, the count in S is incremented by
2 up to the value of the link_fail parameter.

A radio link failure occurs when S equals 0. The BSS continues transmitting on the downlink
until S reaches 0.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies link_fail must be greater than or equal to
link_about_to_fail

Syntax

Change command strings

chg_element link_fail <value> <location> <cell_desc>

chg_cell_element link_fail <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element link_fail <location> <cell_desc>

68P02901W23-T 6-563
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (1 step = 4 SACCH multiframes)

Valid range 0 to 15 Represents the number of SACCH multiframes as shown
below:
0 4 SACCH frames
1 8 SACCH frames
2 12 SACCH frames
... ...
... ...
... ...
15 64 SACCH frames
Default value 4 (20 SACCH frames)

References

Internal name RADIO_LINK_TIMEOUT(BS)

This is a Motorola defined parameter.

6-564 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lmtl_loadshare_granularity

lmtl_loadshare_granularity

Description

The lmtl_loadshare_granularity parameter specifies the level of granularity for LMTL load
sharing.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies If this parameter is modified outside SYSGEN mode,
all LMTLs must be in the locked state in order for the
modification to take effect.
This parameter cannot be modified or displayed at a RXCDR
site.
Operator actions Set element state

Syntax

Change command string

chg_element lmtl_loadshare_granularity <value> <location>

Display command string

disp_element lmtl_loadshare_granularity <location>

Values

Value type Integer

Valid range 0 Corresponds to granularity of 16.
1 Corresponds to granularity of 64.
Default value 0

68P02901W23-T 6-565
Jan 2010
local_maintenance Chapter 6: CM database parameters

local_maintenance

Description

The local_maintenance parameter specifies whether database elements that can be configured
through the OMC-R interface, can be modified from a local maintenance terminal or from
a rlogin. This is used to synchronize the database in the BSS and the data modeled in the
OMC-R MIB.

When this parameter is disabled, the BSS blocks attempts to modify database elements that are
configurable through the OMC-R interface at a local maintenance terminal or from a rlogin.
When this parameter is enabled, the BSS allows modification of database elements that are
configurable through the OMC-R interface at a local maintenance terminal or from a rlogin.

The local_maintenance parameter is also used to determine whether BSS commands supported
through the OMC-R interface may be entered from a local maintenance terminal or from a rlogin.

If the local_maintenance flag is disabled, the MMI is prevented from creating, modifying or
deleting the TD-SCDMA neighbor.

The OMC-R GUI supports the following commands or functionalities and may be entered from
the local maintenance terminal or rlogin regardless of the value of the local_maintenance
parameter:

cage_audit disp_enable_stat disp_xbl_options

chg_dte disp_equipment ins_device
chg_throttle disp_flash lock_device
configure_csfp disp_hdlc query_audits
copy_cell disp_hopping reassign
device_audit disp_level reset_device
disp_a5_alg_pr disp_neighbor reset_site
disp_cbch_state disp_options shutdown_device
disp_cell disp_processor site_audit
disp_cell_status disp_rcu_id soft_reset
disp_csfp disp_rtf_path state
disp_csfp_status disp_rxcdr_gbu status_mode
disp_dte disp_throttle swap_devices
disp_element disp_version unlock_device

6-566 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Description

The OMC-R GUI supports the following commands or functionalities and may not be entered
from the local maintenance terminal or a rlogin when the local_maintenance parameter
is set to 0:

add_cell chg_csfp del_cell

add_neighbor chg_eas_alarm del_neighbor
add_rtf_path chg_element del_rtf_path
add_conn chg_hop_params del_smscb_msg
cell_name chg_ksw_config del_conn
chg_a5_alg_pr chg_rtf_freq equip
chg_acs_params chg_smscb_msg modify_neighbor
chg_audit_sched copy_cell modify_value
chg_cell_element copy_path unequip
chg_cell_id

The OMC-R GUI does not support the following commands or functionalities and may be entered
from the local maintenance terminal or rlogin regardless of the value of the local_maintenance
parameter:

add_channel disp_bss disp_trace_call

add_rxcdr_link disp_cal_data disp_traffic
alias disp_channel enable_alarm
chg_level disp_gclk_avgs gclk_cal_mode
chg_time disp_gclk_cal help
chg_ts_usage disp_gsm_cells history
clear_cal_data disp_level man

clear_database disp_link_usage reattempt_pl

clear_gclk_avgs disp_links set_full_power
del_act_alarm disp_mms_ts_usage store_cal_data
del_channel disp_mobile_optimize swfm_enable
del_link disp_rtf_calls sysgen_mode
disable_alarm disp_rtf_channel time_stamp
disp_act_alarm disp_site trace_call
disp_alarm_sites disp_throttle unalias

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None
Operator actions Place the system in the SYSGEN ON mode before using the
chg_element command to change this parameter.

68P02901W23-T 6-567
Jan 2010
Syntax Chapter 6: CM database parameters

Syntax

Change command string

chg_element local_maintenance <value> <location>

Display command string

disp_element local_maintenance <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

6-568 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference low_sig_thresh

low_sig_thresh

Description

The low_sig_thresh parameter specifies the minimum receive level for redirected handovers.
When a call, using a MultiBand MS, is on any cell, and a handover is triggered to a cell with a
coincident cell, the handover takes place to the coincident cell, if the measured receive level
from the target cell exceeds this parameter value.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element low_sig_thresh <value> <location> <cell_desc>

chg_cell_element low_sig_thresh <value> <cell_desc_opt>

Display command string

disp_element low_sig_thresh <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 63
Default value 0

68P02901W23-T 6-569
Jan 2010
lta_alarm_range Chapter 6: CM database parameters

lta_alarm_range

Description

The lta_alarm_range parameter specifies the alarm range on the allowed Long Term Average
(LTA) variation. Temperature changes can cause the frequency generated by the VCXO (Voltage
Controlled Crystal Oscillator) to vary. The default range (7) is sufficient to compensate for
normal day to day variations in temperature. This value should not be changed unless it is
known that the MMS or uplink clock is faulty.

The LTA is a rolling average of the values read from the clock frequency register (CLKFREQ) of
each GCLK once every half hour after synchronization if the GCLK is phase locked. Up to 48
clock frequency readings are stored. These stored readings are used to calculate the LTA. An
alarm is generated if 25% or more of the stored readings differ from the calculated LTA by more
than the value that is specified by the lta_alarm_range parameter.

The CLKFREQ register is used to maintain the correct frequency generated by the VCXO
(Voltage Controlled Crystal Oscillator). The register center value is 80 h.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is not valid at an M-Cell site.

Syntax

Change command string

chg_element lta_alarm_range <value> <location>

Display command string

disp_element lta_alarm_range <location>

Values

Value type Integer

Valid range 1 to 255
Default value 7

6-570 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference max_gprs_ts_per_carrier

max_gprs_ts_per_carrier

Description

The max_gprs_ts_per_carrier parameter specifies the maximum number of timeslots

(switchable and reserved) that the BSS should allocate to an RTF.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted and the
gprs_ts_config_alg must be set to 1.
Enough timeslots must be available on all of the GPRS
cell carriers.

NOTE
When an attempt is made to change max_gprs_ts_per_carrier and the requested
PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request
and issues a warning to indicate that there is not enough GDS or PMC resource
available.

Syntax

Change command strings

chg_element max_gprs_ts_per_carrier <value> <location> <cell_desc>

chg_cell_element max_gprs_ts_per_carrier <value> <cell_desc_opt>

Display command string

disp_element max_gprs_ts_per_carrier <location> <cell_desc>

68P02901W23-T 6-571
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 1 to 8
Default value 8

6-572 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference max_ms_dl_buffer

max_ms_dl_buffer

Description

The max_ms_dl_buffer parameter specifies the maximum size of the downlink buffer allocated
to every MS in the cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are notified immediately the change
is made.

Syntax

Change command strings

chg_element max_ms_dl_buffer <value> <location> <cell_desc>

chg_cell_element max_ms_dl_buffer <value> <cell_desc_opt>

Display command string

disp_element max_ms_dl_buffer <location> [<cell_desc>]

68P02901W23-T 6-573
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (bytes.)

Valid range 5120 to
64000
5120 bytes
... ...
... ...
... ...
64000 bytes
Default value 38400 bytes

6-574 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference max_ms_dl_rate

max_ms_dl_rate

Description

The max_ms_dl_rate parameter specifies the maximum rate initially at which the SGSN
transmits downlink data to any MS in the cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

Syntax

Change command strings

chg_element max_ms_dl_rate <value> <location> <cell_desc>

chg_cell_element max_ms_dl_rate <value> <cell_desc_opt>

Display command string

disp_element max_ms_dl_rate <location> <cell_desc>

Values

Value type Integer (100 bits per second)

Valid range 1 to 900
Default value 900 (equivalent to 90000 bits per second)

NOTE
The units for this parameter are 100 bits per second. The equivalent range in bits per
second is 100 to 90000.

68P02901W23-T 6-575
Jan 2010
max_number_of_sdcchs Chapter 6: CM database parameters

max_number_of_sdcchs

Description

The max_number_of_sdcchs parameter specifies the maximum number (limit) of SDCCHs that
may be reached with the reconfiguration process. It determines the maximum limit of the
SDCCHs that the CRM maintains.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies For combined channel configurations, the values can be 12,
20, 28 SDs.
For non-combined channel configurations, the values can
be 16, 24, 32 SDs.
Valid values for this parameter depend on the value of
ccch_conf.

Syntax

Change command string

chg_element max_number_of_sdcchs <value> <location> <cell_desc>

Display command strings

disp_cell <cell_id> [full]

6-576 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range If feature SDCCH increase is unrestricted, then
12 to 124 If ccch_conf = 1.
16 to 128 If ccch_conf = 0.
If feature SDCCH increase is restricted, then
12 to 44 If ccch_conf = 1.
16 to 48 If ccch_conf = 0.
Default value None

References

GSM specification 5.02 - 6.4

This is a Motorola defined parameter.

68P02901W23-T 6-577
Jan 2010
max_pagenum_per_sec Chapter 6: CM database parameters

max_pagenum_per_sec

Description

The max_pagenum_per_sec parameter defines the maximum number of Page messages from
the BSC to each BTS allowed in one second.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Add/Change command strings

chg_element max_pagenum_per_sec <value> bsc

Display command strings

disp_element max_pagenum_per_sec bsc

Values

Value type Integer (number of Page messages)

Valid range 70 to 65535
Default value 65535

6-578 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference max_q_length_channel

max_q_length_channel

Description

The max_q_length_channel parameter specifies the maximum number of MSs that may wait
in queue for a full rate channel assignment.

If an idle traffic channel is not available at the channel assignment instant, the network may
place the traffic channel request in queue.

If the queue length is 0, queuing is not allowed.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The sum of max_q_length_channel and
max_q_length_sdcch must be less than or equal
to queue_management_information.

Syntax

Change command strings

chg_element max_q_length_channel <value> <location> <cell_desc>

chg_cell_element max_q_length_channel <value> <cell_desc_opt>

Display command string

disp_element max_q_length_channel <location> <cell_desc>

68P02901W23-T 6-579
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (representing the number of MSs in the queue)

Valid range 0 to 50
Default value 0

References

GSM specification 4.08 - 5.2.1.1.10

3.01: conditions to apply call queuing
This is a Motorola defined parameter.

6-580 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference max_q_length_sdcch

max_q_length_sdcch

Description

The max_q_length_sdcch parameter specifies the maximum length of the queue for
Stand-alone Dedicated Control Channel (SDCCH) requests.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The sum of max_q_length_channel and
max_q_length_sdcch must be less than or equal
to queue_management_information.

Syntax

Change command string

chg_element max_q_length_sdcch <value> <location> <cell_desc>

chg_cell_element max_q_length_sdcch <value> <cell_desc_opt>

Display command string

disp_element max_q_length_sdcch <location> <cell_desc>

Values

Value type Integer (represents the number of requests)

Valid range 0 to 50
Default value None

68P02901W23-T 6-581
Jan 2010
max_retran Chapter 6: CM database parameters

max_retran

Description

The max_retran parameter specifies the maximum channel request retransmission value for
MSs.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element max_retran <value> <location> <cell_desc>

chg_cell_element max_retran <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element max_retran <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 3
0 Maximum [1] retransmission
1 Maximum [2] retransmissions
2 Maximum [4] retransmissions
3 Maximum [7] retransmissions
Default value 0

6-582 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter MAX_RETRANS

GSM specification
4.08 - 3.3.1.1: request for resources by the MS
4.08 - 10.5.2.17, fig. 10.36, table 10.30
5.08 - 6.6.2: cell reselection
12.20 - 5.2.8.7 cell Description - max Number
Retransmission

68P02901W23-T 6-583
Jan 2010
max_rst_ckt_timer_exps Chapter 6: CM database parameters

max_rst_ckt_timer_exps

Description

The max_rst_ckt_timer_exps parameter specifies the number of times that the Reset Circuit
message is repeated if there is no answer from the MSC.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.

Syntax

Change command string

chg_element max_rst_ckt_timer_exps <value> 0

Display command string

disp_element max_rst_ckt_timer_exps 0

Values

Value type Integer (represents the number of repeats)

Valid range 0 to 100
The value 0 means the system keeps sending the Reset Circuit message
indefinitely.
Default value 1

6-584 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference max_sum_timeslot

max_sum_timeslot

Description

The max_sum_timeslot parameter indicates whether the support for allocations with sum 6
timeslots on a single carrier is enabled in the BSS software.

NOTE
This element determines whether mobiles capable of 5:1, 4:2, 3:3, and 2:4 [DL:UL
timeslots], that is, multi-slot class 30 to 33 have their true capabilities supported or
whether they are mapped to a lower multi-slot class.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command strings

chg_element max_sum_timeslot <value> <location>

Display command strings

disp_element max_sum_timeslot <location>

Values

Value type Boolean

Valid range 0 Disable
1 Enable
Default value 0

68P02901W23-T 6-585
Jan 2010
max_tx_bts Chapter 6: CM database parameters

max_tx_bts

Description

The max_tx_bts parameter specifies the maximum output power for a cell in 2 dB steps of
attenuation from the calibrated cell site power of the radios in the cell.

For macro BTS platforms, max_tx_bts supports a range of 23 steps of 2 dB giving a range
of 46 dB.

For micro BTS platforms, max_tx_bts supports a range of 7 steps giving a range of 14 dB.

NOTE
The true transmit power of the cell is dependent on the value of the cell site power
selected for the cell with the max_tx_bts parameter.

For example:
Consider an EGSM 900 cell calibrated for 20 Watts (43 dBm) at the top of the cabinet with
max_tx_bts equal to 2 (4 dB of attenuation).

Calibrated power at the top of the cabinet = 43 dBm

Attenuation applied by max_tx_bts = 4 dB

Actual cell maximum output power = 43 dBm - 4 dB = 39 dBm (8 Watts)

Consider an EGSM 900 cell calibrated for 40 W (46 dBm) at the top of the cabinet with
max_tx_bts equal to 3 (6 dB of attenuation). This would be equivalent to a CTU using a
TDF RF block or a CTU2 in single density mode.

Calibrated power at the top of the cabinet = 46 dBm

Attenuation applied by max_tx_bts = 6 dB

Actual cell maximum output power = 40 dBm - 6 dB = 40 dBm (10 Watts)

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies frequency_type

6-586 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

Syntax

Change command strings

chg_element max_tx_bts <value> <location> <cell_desc>

chg_cell_element max_tx_bts <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element max_tx_bts <location> <cell_desc>

Values

Value type Integer (1 step = 2 dBm)

Valid range -1 to 21 For PGSM, EGSM, and DCS1800.
0 to 6 For M-Cellmicro, M-Cellaccess and Horizoncompact.
Default value None

NOTE
Refer to Table 6-23, Table 6-24, Table 6-25, and Table 6-26 for additional information
about the values for this parameter.

Table 6-23 lists the values used in the BSS software for the CTU2 when using this parameter
for the purposes of calculating path balance. The values assumed represent the calibrated
output power at the top of the cabinet with one stage of combining as this is the most common
configuration.

NOTE

The true actual power of the cell is dependent on the physical combining used
and the calibrated cell site power. Care should be taken when evaluating path
balance results for non standard cell combining configurations.
The CTU2 values for 900 MHz represent the calibrated output power after
reducing the combining loss of 3 dB due to single stage of combining. The BSS
software always assumes a single stage of combining even when there is no
combining physically present.
For example, for the valid input -1 for 900 MHz, the calibrated output power
with one stage of combining = 48 dBm - 3 dB = 45 dBm.
This assumes that the single density CTU2 will be combined externally with
another radio therefore bringing the actual top of the cabinet output power
down by 3 dB.

68P02901W23-T 6-587
Jan 2010
Values Chapter 6: CM database parameters

Table 6-23 CTU2 values

Valid Input 1800 Mhz 900 Mhz

-1 44 dBm 45 dBm
0 42 dBm 43 dBm
1 40 dBm 41 dBm
2 38 dBm 39 dBm
3 36 dBm 37 dBm
4 34 dBm 35 dBm
5 32 dBm 33 dBm
6 30 dBm 31 dBm
7 28 dBm 29 dBm
8 26 dBm 27 dBm
9 24 dBm 25 dBm
10 22 dBm 23 dBm
11 20 dBm 21 dBm
12 18 dBm 19 dBm
13 16 dBm 17 dBm
14 14 dBm 15 dBm
15 12 dBm 13 dBm
16 10 dBm 11 dBm
17 8 dBm 9 dBm
18 6 dBm 7 dBm
19 4 dBm 5 dBm
20 2 dBm 3 dBm
21 0 dBm 1 dBm

NOTE
Value -1 is only valid for single density CTU2 DRI.

Table 6-24 lists the values for the (R)CTU4. The values represent the calibrated output power
at the top of the cabinet without any stage of external combining in single density or values
without external combining in double density mode.

6-588 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

NOTE
The (R)CTU4 values represent the calibrated output power after reducing the
combining loss of 0 dB, 3 dB, and 6 dB without any stage of combining. This is when
the maximum densities of two transmission paths are working at (0+1 or 1+1 mode),
or (0+2 or 1+2, or 2+2 mode), or (0+3 or 1+3, or 2+3, or 3+3 mode) accordingly.

If the (R)CTU4 is working at 1+0, 1+1 carrier mode, the max_tx_bts is the same,
for example, at the radio output: max_tx_bts 0->46dBm, 1->44dBm, 2->42dBm.
If the (R)CTU4 is working at 2+0, 2+1, 2+2 carrier mode, the (R)CTU4 has
extra 3dB attenuation. For example, at the radio output: max_tx_bts 0->43dBm,
1->41dBm, 2->39dBm.
If the (R)CTU4 is working at 3+0, 3+1, 3+2, 3+3 carrier mode, the (R)CTU4 has
extra 6dB attenuation. For example, at the radio output: max_tx_bts 0->40dBm,
1->38dBm, 2->36dBm.

Table 6-24 (R)CTU4 output values without any stage of combining

(R)CTU4 working at 0+1 (R)CTU4 working at 0+2 (R)CTU4 working at 0+3 or

Valid input or 1+1 mode or 1+2, or 2+2 mode 1+3, or 2+3, or 3+3 mode
1800 Mhz 900 Mhz 1800 Mhz 900 Mhz 1800 Mhz 900 Mhz
0 45 dBm 46 dBm 42 dBm 43 dBm 39 dBm 40 dBm
1 43 dBm 44 dBm 40 dBm 41 dBm 37 dBm 38 dBm
2 41 dBm 42 dBm 38 dBm 39 dBm 35 dBm 36 dBm
3 39 dBm 40 dBm 36 dBm 37 dBm 33 dBm 34 dBm
4 37 dBm 38 dBm 34 dBm 35 dBm 31 dBm 32 dBm
5 35 dBm 36 dBm 32 dBm 33 dBm 29 dBm 30 dBm
6 33 dBm 34 dBm 30 dBm 31 dBm 27 dBm 28 dBm
7 31 dBm 32 dBm 28 dBm 29 dBm 25 dBm 26 dBm
8 29 dBm 30 dBm 26 dBm 27 dBm 23 dBm 24 dBm
9 27 dBm 28 dBm 24 dBm 25 dBm 21 dBm 22 dBm
10 25 dBm 26 dBm 22 dBm 23 dBm 19 dBm 20 dBm
11 23 dBm 24 dBm 20 dBm 21 dBm 17 dBm 18 dBm
12 21 dBm 22 dBm 18 dBm 19 dBm 15 dBm 16 dBm
13 19 dBm 20 dBm 16 dBm 17 dBm 13 dBm 14 dBm
14 17 dBm 18 dBm 14 dBm 15 dBm 11 dBm 12 dBm
15 15 dBm 16 dBm 12 dBm 13 dBm 9 dBm 10 dBm
16 13 dBm 14 dBm 10 dBm 11 dBm 7 dBm 8 dBm
17 11 dBm 12 dBm 8 dBm 9 dBm 5 dBm 6 dBm
18 9 dBm 10 dBm 6 dBm 7 dBm 3 dBm 4 dBm
19 7 dBm 8 dBm 4 dBm 5 dBm 1 dBm 2 dBm

Continued

68P02901W23-T 6-589
Jan 2010
Values Chapter 6: CM database parameters

Table 6-24 (R)CTU4 output values without any stage of combining (Continued)
(R)CTU4 working at 0+1 (R)CTU4 working at 0+2 (R)CTU4 working at 0+3 or
Valid input or 1+1 mode or 1+2, or 2+2 mode 1+3, or 2+3, or 3+3 mode
1800 Mhz 900 Mhz 1800 Mhz 900 Mhz 1800 Mhz 900 Mhz
20 5 dBm 6 dBm 2 dBm 3 dBm -1 dBm 0 dBm
21 3 dBm 4 dBm 0 dBm 1 dBm -3 dBm -2 dBm

NOTE
Set the same value for the (R)CTU4 maximum densities of two transmission paths in
one cell to ensure the same output power for carriers in one cell.

Table 6-25 identifies the transmit power capabilities of the different XCVR types in specific
frequency bands and cabinet types. The power specified is the cabinet antenna connector
maximum output power. All figures are 2 dB.

Table 6-25 also specifies the types of combing used: none, external, internal, and both internal
and external. The combining types are defined as follows:
None: The output power of the XCVR is connected directly to the antenna. This is not
applicable for a DDM as it always uses a single stage of internal combining within the
XCVR itself.

External (to the XCVR): The output of the XCVR is connected through a single stage of
external hybrid combining to the antenna. For example, a two-carrier sector is required
from two SDX or two CTU2-SD.

Internal (to the XCVR): When a CTU2 is configured in Double Density mode the two outputs
from the two XCVR devices on the CTU2 are combined before leaving the XCVR. Hence
the power figure internal combining represents two carriers at this transmit power for
a CTU2 in DD-DCM. Ensure that the internal combining is still present when the CTU2
is used in DD-SCM.

Internal and external: External hybrid combining is used on a CTU2 in DDM. For example,
this allows two CTU2 in DD-DCM to be combined to create a four-carrier sector.

Table 6-25 Cabinet antenna connector maximum output power (Watts)

Horizonmacro Horizon II macro

XCVR Type Combining
EGSM900 DCS1800 EGSM900 DCS1800
CTU None 40 32 N/A N/A
External 20 16 N/A N/A
CTU2 None 40 32 63 50
SD-SCM
External 20 16 28 22
CTU2 Internal 10 10 20 16
DD-DCM
Internal and 4.5 4.5 9 7
external

6-590 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Table 6-26 lists the values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro, M-Cellcity,
Horizonmicro (M-Cellarena) and Horizoncompact (M-Cellarenamacro) sites.

Table 6-26 Values for PGSM, EGSM, DCS1800 and PCS1900 sites

PGSM and EGSM DCS1800 and PCS1900 Horizoncompact

Valid Input
M-Cellmicro values M-Cellmicro values (M-Cellarenamacro) values
0 31 dBm 30 dBm 40 dBm
1 29 dBm 28 dBm 38 dBm
2 27 dBm 26 dBm 36 dBm
3 25 dBm 24 dBm 34 dBm
4 23 dBm 22 dBm 32 dBm
5 21 dBm 20 dBm 30 dBm
6 19 dBm 18 dBm 28 dBm

References

GSM parameter BS_TXPWR_RED

GSM specification For MAX see GSM Rec. 5.05 - 4.1.2
Rec. 5.08-BS_TXPWR_MAX,
12.20 - 5.2.8.23 - power Ctrl BTS - BS Tx Pwr Max
12.20 - 5.2.8.2 - Tx power

68P02901W23-T 6-591
Jan 2010
max_tx_bts_standby Chapter 6: CM database parameters

max_tx_bts_standby

{36039G}

Description

The max_tx_bts_standby parameter stores the max tx bts value for the standby Abis bearing
mode usage. For example, if currently the Abis is working on the terrestrial link, this parameter
will store the value for satellite usage. If the Abis has been swapped to the satellite link then
the parameter will store the value for terrestrial link usage.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies This parameter can be modified only when the Abis auto
swap feature (abisautoswapOpt) is enabled and the target
cell resides in a Horizon II macro BTS site.

Syntax

Change command string

chg_element max_tx_bts_standby <value> <location> <cell_desc>

Display command string

disp_element max_tx_bts_standby <location> <cell_desc>

Values

Value type Integer

Valid range -1 to 21
-1 Minimum
21 Maximum
Default value 0

6-592 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference max_tx_ms

max_tx_ms

Description

The max_tx_ms parameter specifies the maximum MS (Mobile Station) output power.
Regardless of the power class of the MS, the MS is not told to use a higher output power.

Select the value to balance the up and down links in a cell.

This parameter is also used in the power budget calculation.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The range and default values of ms_txpwr_max_inner
depends on this parameter. If the range or default value of
max_tx_ms changes, mstxpwr_max_inner must also be
updated, to a value less than or equal to max_tx_ms.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element max_tx_ms <value> <location> <cell_desc>

chg_cell_element max_tx_ms <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element max_tx_ms <location> <cell_desc>

68P02901W23-T 6-593
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (dBm)

Valid range 5 to 39 PGSM and EGSM (Odd values only)
0 to 36 DCS1800 (Even values only)
0 to 32,33 PCS1900 (Even values only and value 33)
Default value Highest allowed value

References

GSM parameter MS_TXPWR_MAX

GSM specification 5.08 - 4.3
5.05 - 4.1

6-594 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference mb_preference

mb_preference

Description

The mb_preference parameter enables or disables the Multiband Inter-cell Handover feature.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is unavailable if the Multiband Inter-Cell
Handover feature is restricted.
This parameter may not be disabled when inner_zone_alg
is set to indicate Dual Band Cells for any cell in the BSS.

Syntax

Change command string

chg_element mb_preference <value> <location>

Display command string

disp_element mb_preference <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-595
Jan 2010
mb_tch_congest_thres Chapter 6: CM database parameters

mb_tch_congest_thres

Description

The mb_tch_congest_thres parameter specifies the level of overall TCH utilization by any
MS in a given Cell, at which a MultiBand MS is redirected to the preferred band (as set by
band_preference). The parameter is expressed as a percentage.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell number required Yes
Dependencies The parameter can be set only if

the Congestion Relief feature is unrestricted

(ho_exist_congest element must be enabled).

mb_preference element must be enabled.

band_preference_modemust be set to 6 (the mode

which triggers when a Cell is congested).

mb_tch_congest_thres must be less than or equal to

tch_congest_prevent_thres.

Syntax

Change command string

chg_element mb_tch_congest_thres <value> <location> <cell_desc>

Display command string

disp_element mb_tch_congest_thres <location> <cell_desc>

Values

Value type Integer (representing a percentage.)

Valid range 1 to 101 The value 101 indicates there are no resources left to
allocate).
Default value 100 The value 100 indicates an attempt to use the last resource.

6-596 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference MCBTSR8Opt

MCBTSR8Opt

{34371G}

Description

The BSC supports the MCBTSR8Opt parameter which indicates whether the (R)CTU4 Radio
can support the operation of 3 carriers per Tx lineup port in one (R)CTU4 Radio in the BSS
software.

NOTE
The (R)CTU4 Radio configured to support 3 carriers per Tx port is designed to meet
the 3GPP R8 Multi-Carrier BTS Class 2 performance specification

For 2 carriers per TX port, the (R)CTU4 Radio can operate within the 3GPP R8
Multi-Carrier BTS Class 1 performance specification.
For 1 carrier per TX port, the (R)CTU4 Radio can operate within the 3GPP
Standard R8 BTS Class performance specification.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies If the MCBTSR8Opt flag indicates that the (R)CTU4 works
in 3 carriers per RF transmission port mode is restricted,
the (R)CTU4 radio can operate in 1, 2, 3 (1 per Tx port 1+
2 per Tx port 2) and 4 carriers (2 per Tx port 1+ 2 per Tx
port 2) per Radio.
If the MCBTSR8Opt flag indicates that the (R)CTU4 works
in 3 carriers per RF transmission port mode is unrestricted,
the (R)CTU4 radio can additionally operate in 3 (0 per Tx
port 1 + 3 per Tx port 2), 4 (1 per Tx port 1 + 3 per Tx port
2), {35200G} 5 (2 per Tx port 1 + 3 per Tx port 2) and 6 (3
per Tx port 1 + 3 per Tx port 2) carriers per Radio.

Syntax

Display command strings

disp_options

68P02901W23-T 6-597
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 Does not support (R)CTU4 in 3 carriers per Tx port.
1 Supports (R)CTU4 in 3 carriers per Tx port.
Default value N/A

6-598 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference missing_rpt

missing_rpt

Description

The missing_rpt parameter enables or disables the suspension of the storing, averaging, and
processing of downlink power control and handovers.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

chg_element missing_rpt <value> <location> <cell_desc>

chg_cell_element missing_rpt <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element missing_rpt <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None

68P02901W23-T 6-599
Jan 2010
mmi_cell_id_format Chapter 6: CM database parameters

mmi_cell_id_format

Description

The mmi_cell_id_format parameter specifies the format that the MMI command line accepts
for the GSM cell Identification number. The formats available are: 4-parameter and 7-parameter.

Type B (operator actions required)

Supported by OMC-R GUI No
Cell description required No
Dependencies The system must be in SYSGEN ON mode to modify this
parameter.
PCS1900 systems accept only the 4-parameter cell number
format.
This parameter is valid only at the BSC.
Operator actions Place the system in SYSGEN ON mode

Syntax

Change command string

chg_element mmi_cell_id_format <value> 0

Display command string

disp_element mmi_cell_id_format 0

Values

Value type Boolean

Valid range 0 or 1
0 7-parameter format
1 4-parameter format
Default value 0

6-600 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference mms_cat_enable

mms_cat_enable

Description

The mms_cat_enable parameter enables or disables the MMS Critical Alarm Threshold (CAT)
for MMS stability testing.

When mms_cat_enable is enabled, the system monitors how often an MMS goes Out Of Service
(OOS) and then back into service due to an alarm (such as Synchronization Loss OOS Timer
Expired) occurring and clearing in the last 10 minutes. When this happens 10 times in 10
minutes, after the tenth clear the MMS stays OOS even though the alarm is cleared, and the
Critical Alarm Threshold Exceeded alarm is reported against the MMS device. This action is
taken because the MMS is showing signs of instability. The system continues to monitor how
many times alarms and clears have occurred in the latest 10 minute period. As soon as the
number is less than 10, the MMS is brought back into service automatically, and the Critical
alarm Threshold Exceeded alarm is cleared.

A lock/unlock of the MMS overrides this periodic auditing and brings the MMS into service
immediately.

When mms_cat_enable is disabled, the MMS remains in service even if the MMS CAT is met or
exceeded.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element mms_cat_enable <value> <location>

Display command string

disp_element mms_cat_enable <location>

68P02901W23-T 6-601
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-602 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference mms_config_type

mms_config_type

Description

The mms_config_type parameter specifies the signaling type for all MMSs. The signaling type
depends on the carrier type being used, E1.

All BTS site or PCU values are set to the value assigned to the BSC (site 0) or PCU (pcu) when
the database is initially loaded.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The value of the land_layer1_mode parameter, where:
For E1 systems (land_layer1_mode =0), the value of this
parameter can be changed at any time for any site. If
executed outside SYSGEN mode, a warning message saying
the MMSs must be reset to have the change take effect at
that site will display. The value of mms_config_type must
be the same at the BSC and the PCU sites.
Operator actions For E1 systems, reset the MSIs for a change to this
parameter to take effect.

Syntax

Change command string

chg_element mms_config_type <value> <location>

NOTE
The value can be changed using the chg_cell_element command but the incorrect
value is used until the MSI or BSI is reset and the change becomes active.

Display command string

disp_element mms_config_type <location>

68P02901W23-T 6-603
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
If land_layer1_mode = 0 (2.048 Mbit/s E1 link) then:
0 CRC-4
1 No CRC-4
Default value 0

6-604 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ms_distance_allowed

ms_distance_allowed

Description

The ms_distance_allowed parameter disables or enables the distance comparison process

for handovers.

When enabled, the distance comparison process can cause a handover if the distance between
the MS and the BSS is greater than the ms_max_range. If this parameter is enabled, the value
chosen for ms_max_range needs careful optimization.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies ms_max_range

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element ms_distance_allowed <value> <location> <cell_desc>

chg_cell_element ms_distance_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ms_distance_allowed <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-605
Jan 2010
References Chapter 6: CM database parameters

References

GSM specification 5.08 - Appendix A, 3.1 (f): PBGT(n); 3.2.2d; 3d

12.20 - 5.2.8.18 - enable BSS Handover Control - enable MS
Distance Process
This is a Motorola defined parameter.

6-606 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ms_flow_control_enabled

ms_flow_control_enabled

{34452}

Description

The ms_flow_control_enabled parameter enables or disables the function of mobile flow

control for PS call. This parameter can be accessed and updated both in and out of sysgen mode.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the GPRS
feature is enabled.

Syntax

Change command string

chg_element ms_flow_control_enabled <value> <location>

Display command string

disp_element ms_flow_control_enabled <location>

Values

Value type Integer

Valid range 0 to 1
0 Disables MS flow control for PS call.
1 Enables MS flow control for PS call.
Default value 1

68P02901W23-T 6-607
Jan 2010
ms_max_range Chapter 6: CM database parameters

ms_max_range

Description

The ms_max_range parameter specifies the MS maximum range for the handover algorithm.

Program this parameter in terms of timing advance bits. The following equation shows the
relationship between distance and timing advance:

(timing advance) (bit period) (propagation velocity) = 2 (distance from MS to BSS)

Value 0 corresponds to no timing advance. Values 1 to 63 represent the bit periods that the
MS transmission (to the BSS) are delayed.

If The Extended Range Feature is unrestricted and Extended Range is enabled in the cell, the
maximum value of ms_max_range increases to 219.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The range for the ms_max_range parameter depends on
whether the Extended Range feature is enabled or disabled.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

add_cell <gsm_cell_id> <location>chg_element ms_max_range <value>

<location><cell_desc>

chg_cell_element ms_max_range <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ms_max_range <location> <cell_desc>

6-608 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 63 for normal cells (see ).
0 to 219 for Extended Range cells (see Table 6-28).
Default value 63

Table 6-27 ms_max_range values for normal cells

Timing advance bits Bit periods delayed Distance of MS to BSS

(kilometer)
0 468.75 0
1 467.75 0.554
2 466.75 1.108
3 465.75 1.662
4 464.75 2.215
... ... ...
... ... ...
62 406.75 34.338
63 405.75 34.892

If the Extended Range Feature is unrestricted and Extended Range is

enabled in the cell, the maximum value of ms_max_range increases to
219.

Table 6-28 ms_max_range values for Extended Range cells

Timing advance bits Bit periods delayed Distance of MS to BSS (km)

0 468.75 0
1 467.75 0.554
2 466.75 1.108
3 465.75 1.662
4 464.75 2.215
... ... ...
... ... ...
218 250.75 120.772
219 249.75 121.326

References

GSM parameter MS_RANGE_MAX

GSM specification 5.08 - Appendix A - Table 1: MS_RANGE_MAX
5.10 - 5.8

68P02901W23-T 6-609
Jan 2010
ms_p_con_ack Chapter 6: CM database parameters

ms_p_con_ack

Description

The ms_p_con_ack parameter specifies the time for which power control can be resumed if
power change acknowledgment is not received from the MS. This parameter is effective only if
the decision_alg_num equals 1.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies decision_alg_num = 1

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element ms_p_con_ack <value> <location> <cell_desc>

chg_cell_element ms_p_con_ack <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ms_p_con_ack <location> <cell_desc>

6-610 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 2 SACCH multiframes)

Valid range 0 to 31
0 0 SACCH multiframes
1 2 SACCH multiframes
2 4 SACCH multiframes
... ...
... ...
... ...
31 62 SACCH multiframes

Default value 2

References

Internal name P_CON_ACK

This is a Motorola defined parameter.

68P02901W23-T 6-611
Jan 2010
ms_p_con_interval Chapter 6: CM database parameters

ms_p_con_interval

Description

The ms_p_con_interval parameter specifies the minimum amount of time in multiples of two
SACCH multiframes between successive RF power change orders to the MS.

This value depends on the value for the decision_alg_num parameter.

If decision_alg_num = 1, then the recommended value for ms_p_con_interval equals
hreqave divided by 2 (hreqave/2).

If decision_alg_num = 0, then the minimum recommended value for ms_p_con_interval

equals 2 plus hreqave divided by 2 (2+hreqave/2).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies hreqave

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element ms_p_con_interval <value> <location> <cell_desc>

chg_cell_element ms_p_con_interval <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ms_p_con_interval <location> <cell_desc>

6-612 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 step = 2 SACCH multiframes)

Valid range 0 to 31
0 0 SACCH multiframes
1 2 SACCH multiframes
2 4 SACCH multiframes
... ...
... ...
31 62 SACCH multiframes

Default value 2

References

Internal name P_CON_INTERVAL

This is a Motorola defined parameter.

68P02901W23-T 6-613
Jan 2010
ms_power_control_allowed Chapter 6: CM database parameters

ms_power_control_allowed

Description

The ms_power_control_allowed parameter enables or disables MS power control. Enabling

this feature helps to reduce interference.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element ms_power_control_allowed <value> <location> <cell_desc>

chg_cell_element ms_power_control_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ms_power_control_allowed <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

6-614 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Internal name EN_MS_PC

This is a Motorola defined parameter.

68P02901W23-T 6-615
Jan 2010
ms_power_offset Chapter 6: CM database parameters

ms_power_offset

Description

The ms_power_offset parameter specifies the power offset value sent out in the BCCH
system information which utilizes the additional power capabilities of a class 3 DCS1800 MS
that is accessing on the RACH. The value is a positive power offset from the value set by
ms_txpwr_max_cch.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies If the cell is not a type 3 MS cell, 0 is the only value allowed.

Syntax

Change command strings

chg_element ms_power_offset <value> <location> <cell_desc>

chg_cell_element ms_power_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ms_power_offset <location> <cell_desc>

Values

Value type Integer (1 step = 2 dB)

Valid range 0 to 3
0 0 dB
1 2 dB
2 4 dB
3 6 dB

Default value 0

6-616 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ms_txpwr_max_cch

ms_txpwr_max_cch

Description

The ms_txpwr_max_cch parameter specifies the maximum random access power available for
an MS on a control channel (CCCH) in a cell. This parameter is expressed as a power level value.

Before accessing a cell on the RACH and before receiving the first power command during a
communication on a DCCH (or TCH), the MS uses one of two possible power levels.

The MS uses the lower power level of the two available: either the ms_txpwr_max_cch
broadcast on the BCCH or the maximum transmit power as defined by the power class of the MS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies frequency_type

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element ms_txpwr_max_cch <value> <location> <cell_desc>

chg_cell_element ms_txpwr_max_cch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ms_txpwr_max_cch <location> <cell_desc>

Values

Value type

Integer (1 step = 2 dBm)

68P02901W23-T 6-617
Jan 2010
Values Chapter 6: CM database parameters

Valid range (2 to 19 for PGSM and EGSM cells)

Table 6-29 lists the maximum mobile power level for PGSM and EGSM cells.

Table 6-29 Maximum mobile power level for PGSM and EGSM cells

Value Range Value Range

2 39 dBm 11 21 dBm
3 37 dBm 12 19 dBm
4 35 dBm 13 17 dBm
5 33 dBm 14 15 dBm
6 31 dBm 15 13 dBm
7 29 dBm 16 11 dBm
8 27 dBm 17 9 dBm
9 25 dBm 18 7 dBm
10 23 dBm 19 5 dBm

Valid range (0 to 15, 29, 30, 31 for DCS1800 cells)

Table 6-30 lists the maximum mobile power level for DCS1800 cells.

Table 6-30 Maximum mobile power level for DCS1800 cells

Value Range Value Range

29 36 dBm 7 16 dBm
30 34 dBm 8 14 dBm
31 32 dBm 9 12 dBm
0 30 dBm 10 10 dBm
1 28 dBm 11 8 dBm
2 26 dBm 12 6 dBm
3 24 dBm 13 4 dBm
4 22 dBm 14 2 dBm
5 20 dBm 15 0 dBm
6 18 dBm

6-618 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

Valid range (0 to 15, 30, 31 for PCS1900 cells)

Table 6-31 lists the maximum mobile power level for PCS1900 cells.

Table 6-31 Maximum mobile power level for PCS1900 cells

Value Range Value Range

30 33 dBm 7 16 dBm
31 32 dBm 8 14 dBm
0 30 dBm 9 12 dBm
1 28 dBm 10 10 dBm
2 26 dBm 11 8 dBm
3 24 dBm 12 6 dBm
4 22 dBm 13 4 dBm
5 20 dBm 14 2 dBm
6 18 dBm 15 0 dBm

Default value 2

References

GSM parameter MS_TXPWR_MAX_CCH

GSM specification 5.08 - 4.2: ms_txpwr_max_cch
5.08 - 6.4: ms_txpwr_max_cch

68P02901W23-T 6-619
Jan 2010
ms_txpwr_max_cell Chapter 6: CM database parameters

ms_txpwr_max_cell

Description

The ms_txpwr_max_cell parameter specifies the maximum MS transmit power in each

neighbor cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies ms_txpwr_max_def

Syntax

Add/Change command strings

disp_cell <cell_id> [full]

disp_element ms_txpwr_max_cch <location> <cell_desc>

Display command strings

disp_neighbor <src_gsm_cell_id>

Values

Value type Integer (dBm)

Valid range 5 to 39 (Odd values only) PGSM and EGSM
0 to 36 (Even values only) DCS1800

0 to 32, 33 (Even values only and value 33) PCS1900

Default value None

6-620 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter MS_TXPWR_MAX(n)

GSM specification 5.08 - Appendix A, 3.1f: PBGT(n), and section 3.2.2e.
5.08 - Appendix A - Table 1

68P02901W23-T 6-621
Jan 2010
ms_txpwr_max_def Chapter 6: CM database parameters

ms_txpwr_max_def

Description

The ms_txpwr_max_def parameter specifies 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.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies ms_txpwr_max_cell

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

achg_element ms_txpwr_max_def <value> <location> <cell_desc>

chg_cell_element ms_txpwr_max_def <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ms_txpwr_max_def <location> <cell_desc>

Values

Value type Integer (dBm)

Valid range 5 to 39 (Odd values only) PGSM and EGSM
0 to 36 (Even values only) DCS1800
0 to 32, 33 (Even values only and value 33) PCS1900
Default value None

6-622 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter MS_TXPWR_MAX_DEF

GSM specification 5.08 - Appendix A, 3.1f: PBGT(n), and section 3.2.2e.
5.08 - Appendix A - Table 1

68P02901W23-T 6-623
Jan 2010
ms_txpwr_max_inner Chapter 6: CM database parameters

ms_txpwr_max_inner

Description

The ms_txpwr_max_inner parameter specifies the maximum power an MS can use in the inner
zone of a concentric cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies ms_txpwr_max_inner must be less than or equal to
max_tx_ms if the value for inner_zone_alg equals 3 (Dual
Band Cells).

Syntax

Change command strings

chg_element ms_txpwr_max_inner <value> <location> <cell_desc>

chg_cell_element ms_txpwr_max_inner <value> <cell_desc_opt>

Display command string

disp_element ms_txpwr_max_inner <location> <cell_desc>

Values

Value type Integer (dBm)

Valid range Depends on the system:
5 to 39 (odd values only) PGSM/EGSM
0 to 36 (even values only) DCS1800
0 to 32, 33 (even values only and value 33) PCS1900
Default value Same value as max_tx_ms

6-624 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference msc_bss_overload_allowed

msc_bss_overload_allowed

Description

The msc_bss_overload_allowed parameter is an RSL Congestion Control (RCC) element which

enables or disables the BSC to send BSS Overload messages to the MSC during RSL congestion.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Add/Change command strings

chg_element msc_bss_overload_allowed <value> bsc

Display command strings

disp_element msc_bss_overload_allowed bsc

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-625
Jan 2010
msc_preference Chapter 6: CM database parameters

msc_preference

Description

The msc_preference parameter specifies A-interface messaging if an external handover

is needed during an assignment procedure. This parameter should align with the MSC
implementation which may depend on whether queuing is enabled in the cell. The cause value
sent to the MSC can be set according to whether directed retry is supported by the MSC.

This parameter is copied if the copy_cell command is used.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Directed Retry or Multiband Inter-cell Handover
feature must be unrestricted.

Syntax

Change command strings

chg_element msc_preference <value> <location> <cell_desc>

chg_cell_element msc_preference <value> <cell_desc_opt>

Display command string

disp_element msc_preference <location> <cell_desc>

6-626 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 7
0 Directed Retry is supported within the BSS, but not across
the A-interface.
1 Directed Retry is supported within the BSS. The only
A-interface impact is the Assignment Complete message,
which contains the optional Cell ID if the Cell ID changes
during the assignment.
2 The BSS sends the Handover Required message with the
cause directed retry to the MSC.
3 The BSS sends the Handover Required message with the
cause of the handover to the MSC (for example, Better Cell).
4 The BSS sends an Assignment Failure message with the
cause directed retry and then sends a Handover Required
message with cause directed retry to the MSC.
5 The BSS sends an Assignment Failure message with the
cause directed retry and then sends a Handover Required
message with the cause of the handover to the MSC (for
example, Better Cell).
6 The BSS sends a Handover Required message with cause
directed retry and then sends an Assignment Failure
message with cause directed retry to the MSC.
7 The BSS sends a Handover Required message with the cause
of the handover (for example, Better Cell) and then sends
an Assignment Failure message with cause directed retry
to the MSC.
Default value 0

References

GSM specification TS GSM 08.08

This is a Motorola defined parameter.

68P02901W23-T 6-627
Jan 2010
msc_qt Chapter 6: CM database parameters

msc_qt

Description

The msc_qt parameter specifies a defined idle bit pattern for use by the Transcoder Rate
Adaptation Unit (TRAU) and the MSC.

The idle pattern is defined in the GSM specification as:

The idle pattern must be transmitted on every timeslot that is not assigned to a channel,
and on every timeslot of a channel that is not allocated to a call. The idle pattern should
be 01010100.

The binary pattern 01010100 corresponds to decimal 84 which is the default value of this
parameter.

This parameter must correspond to the MSC value for an idle PCM sample on the A-interface.
When the XCDR receives this value from the MSC in all PCM samples in its 20 ms frame, it
outputs a TRAU idle speech frame. In the uplink, this parameter sets the value of PCM that the
XCDR outputs to the MSC before the XCDR has achieved TRAU sync with the CCU in the DRI.

Once this value has been set to match the MSC idle pattern, it does not require any further
changes.

NOTE
This parameter is not related to DTX.

Type B (operator actions required)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter only applies to the XCDR (location = 0).
Operator actions Place the system in SYSGEN ON mode

Syntax

Change command strings

chg_element msc_qt <value> 0

chg_element msc_qt <value> xcdr

6-628 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command strings

disp_element msc_qt 0

disp_element msc_qt xcdr

Values

Value type Integer (decimal)

Valid range 0 to 255 (representing bit patterns 00000000 to 11111111)
Default value 84 (representing bit pattern 01010100)

68P02901W23-T 6-629
Jan 2010
msc_release Chapter 6: CM database parameters

msc_release

Description

The msc_release parameter enables an operator to display and configure the release of the
MSC to which that BSS is connected.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element msc_release <value> <location>

Display command string

disp_element msc_release <location>

Values

Value type Boolean

Valid range 0 or 1
0 MSC is a Release 1998 or older.
1 MSC is a Release 1999 or newer.
Default value 0

6-630 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference mspwr_alg

mspwr_alg

Description

The mspwr_alg parameter enables or disables the enhanced power control algorithm.

The enhanced power control algorithm is used to prevent oscillation for MS power control
where power is reduced for RXQUAL reasons and later increased for RXLEV reasons.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

achg_element mspwr_alg <value> <location> <cell_desc>

chg_cell_element mspwr_alg <value> <cell_desc_opt>

Display command strings

disp_cell mspwr_alg <cell_id> [full]

disp_element mspwr_alg <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-631
Jan 2010
mtbr_downgrade_enabled Chapter 6: CM database parameters

mtbr_downgrade_enabled

Description

The mtbr_downgrade_enabled parameter enables or disables negotiating the MTBR of an

admitted PFC during future retention procedures to a lower value than initially committed.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The mtbr_downgrade_enabled is modified only if Qos is
enabled or unrestricted at the OMC.

Syntax

Change command strings

chg_element mtbr_downgrade_enabled <value> <location>

Display command strings

disp_element mtbr_downgrade_enabled <location>

Values

Value type Integer

Valid range 0 or 1
0 Not allowed to set MTBR to a lower value than committed.
1 Allowed to set the MTBR to a lower value than committed.
Default value 1

6-632 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference mtl_loadshare_granularity

mtl_loadshare_granularity

Description

The mtl_loadshare_granularity parameter sets the loadshare granularity across MTL links.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies If the element is changed in SYSGEN ON mode, the change
takes effect immediately.

NOTE
Changes take effect only when all MTLs are locked.

Syntax

Change command string

chg_element mtl_loadshare_granularity <value> 0

Display command string

disp_element mtl_loadshare_granularity 0

Values

Value type Boolean

Valid range 0 or 1
0 16 virtual circuits (regular granularity)
1 64 virtual circuits (enhanced granularity)
Default value 0

68P02901W23-T 6-633
Jan 2010
multiband_reporting Chapter 6: CM database parameters

multiband_reporting

Description

The multiband_reporting parameter specifies the number of cells of each supported band the
system includes in the MS Measurement Report.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Multiband Inter-cell Handover feature must be enabled.

Syntax

Change command strings

chg_element multiband_reporting <value> <location> <cell_desc>

chg_cell_element multiband_reporting <value> <cell_desc_opt>

Display command string

disp_element multiband_reporting <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 3
0 Normal reporting of the six strongest neighbor cells with
known and allowed NCC part of the BSIC, irrespective of
the band used.

6-634 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

1 Report the strongest neighbor cell, with known and allowed

NCC part of BSIC, in each of the frequency bands in the
neighbor cell list, excluding the frequency band of the
serving cell. The remaining positions in the measurement
report shall be used for reporting Cells in the band of the
serving Cell. Any still remaining positions will be used to
report the next strongest identified neighbors in other bands
irrespective of the band used.
2 Report the two strongest cells, with known and allowed NCC
part of BSIC, in each of the frequency bands in the neighbor
cell list, excluding the frequency band of the serving cell.
The remaining positions in the measurement report shall
be used for reporting Cells in the band of the serving Cell.
Any still remaining positions will be used to report the next
strongest identified neighbors in other bands irrespective
of the band used.
3 Report the three strongest cells, with known and allowed
NCC part of BSIC, in each of the frequency bands in the
neighbor cell list, excluding the frequency band of the
serving cell. The remaining positions in the measurement
report shall be used for reporting Cells in the band of the
serving Cell. Any still remaining positions will be used to
report the next strongest identified neighbors in other bands
irrespective of the band used.
Default value 0

References

GSM specification TS GSM 04.08 section 10.5.2.22

This is a Motorola defined parameter.

68P02901W23-T 6-635
Jan 2010
nacc_enabled Chapter 6: CM database parameters

nacc_enabled

Description

The nacc_enabled parameter indicates whether the Change Cell Notification (CNN) is enabled
or not.

Type A (No operator actions)

Supported by OMC-R GUI Yes
Cell number required No
Dependencies The Network Assisted Cell Change (NACC) feature must be
unrestricted
nacc_enabled cannot be set to 0 (disabled) if the QoS
feature is enabled.

Syntax

Add/Change command strings

chg_element nacc_enabled <value> <location>

Display command strings

disp_element nacc_enabled <location>

Values

Value type Integer

Valid range 0 to 1
0 NACC is off
1 NACC is on
Default value 0

6-636 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference n_avg_i

n_avg_i

Description

The n_avg_i parameter specifies the number of signal strength measurements that is made for
each filtered interference signal strength sample. n_avg_i is the number of radio blocks that
the signal strength is computed on over a period of t_avg_t when in Packet Transfer mode,
and t_avg_w when in Packet Wait (idle) mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter can be used only if the GPRS feature is
unrestricted.

NOTE
BSS software processes using this parameter are notified immediately the change
is made.

Syntax

Change command strings

chg_element n_avg_i <value> <location> <cell_desc>

chg_cell_element n_avg_i <value> <cell_desc_opt>

Display command string

disp_element n_avg_i <location> <cell_desc>

Values

Value type Integer (number of radio blocks)

Valid range 0 to 15
Default value 2

68P02901W23-T 6-637
Jan 2010
ncc_of_plmn_allowed Chapter 6: CM database parameters

ncc_of_plmn_allowed

Description

The ncc_of_plmn_allowed parameter is a bit mapped value which specifies which Network
Color Codes (NCCs) are allowed on specific broadcast control channels (BCCH carriers).

In border areas where two PLMN operators provide overlapping service, a bilateral agreement
is required to determine the NCC values to be broadcast. The selected values are specified by
entering a value that can bit map to the desired NCC.

For example, PLMN operators serving a border area may agree to use NCCs of 0 and 4. A value
of 17 is entered for the ncc_of_plmn_allowed which bit maps as: 00010001

The first and fifth bits are set which allow the NCC value of 0 and 4 to be broadcast on BCCH
carriers.

Two or more NCCs may be assigned in non border areas by specifying ncc_of_plmn_allowed
values that bit maps to the desired NCCs.

For example, the ncc_of_plmn_allowed value of 51 bit maps as: 00110011

The first, second, fifth, and sixth bits are set which allows NCC values of 0, 1, 4, and 5 to be
broadcast on BCCH carriers.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element ncc_of_plmn_allowed <value> <location> <cell_desc>

chg_cell_element ncc_of_plmn_allowed <value> <cell_desc_opt>

6-638 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command strings

disp_cell <cell_id> [full]

disp_element ncc_of_plmn_allowed <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 255 (or 0 to FFh in Hex)

Default 255

Table 6-32 is a representation of the bit mapping of the ncc_of_plmn_allowed parameter. When
a bit is set to 1, the corresponding NCC is allowed. When a bit is set to 0, the corresponding
NCC is not allowed.

Table 6-32 Bit mapping of ncc_of_plmn_allowed

Bit position 128 64 32 16 8 4 2 1

NCC values 7 6 5 4 3 2 1 0

References

GSM parameter PLMN_PERMITTED, NCC

GSM specification 3.03-Annex A, NCCs per country
12.20-5.2.8.7 cell Description-plmn-permitting
4.08-10.5.2.15, figure 10.34 and table 10.28
5.08-9: PLMN_PERMITTED

68P02901W23-T 6-639
Jan 2010
nccr_enabled Chapter 6: CM database parameters

nccr_enabled

Description

The nccr_enabled parameter specifies whether Network Controlled Cell Reselection (NCCR)
is enabled at a BSS.

The following error message is displayed and the command rejected if an attempt is made to
disable this parameter when gprs_type5_alg is enabled:

ERROR: gprs_type5_alg must be disabled before disabling nccr_enabled.

COMMAND REJECTED

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS and NCCR features must be unrestricted.
The PCU must be equipped.
When nccr_enabled parameter is set to 0 (disabled),
gprs_type5_alg cannot be set to 1 (enabled).
gprs_type5_alg must be set to 0 (disabled) before the
nccr_enabled parameter can be set to 0 (disabled).

Syntax

Change command string

chg_element nccr_enabled 1 0

Display command string

disp_element nccr_enabled 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-640 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference nccrOpt

nccrOpt

Description

The nccrOpt parameter indicates whether the Network Controlled Cell Reselection (NCCR)
option is unrestricted in the BSS software.

If restricted, any attempt to access the other NCCR parameters is rejected.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS and NCCR features must be unrestricted to
provide their associated functionality.

Syntax

Display command string

disp_options

Values

Value type Boolean

Valid range 0 or 1
0 Restricted
1 Unrestricted
Default value None

68P02901W23-T 6-641
Jan 2010
neighbor_journal Chapter 6: CM database parameters

neighbor_journal

Description

The neighbor_journal parameter enables or disables neighbor journaling.

If journaling is enabled:
There is no warm-up period for neighbors. All neighbor information is padded with 0's.
Averaging and power budget calculations begin immediately.

If a previously reported neighbor is missing in the measurement report, a 0 rxlev is used

for the neighbor.

If journaling is disabled:
There is a warm-up period of the surround cell hreqave before power budget calculations
begin.

The last received rxlev for the unreported neighbor is used.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element neighbor_journal <value> <location> <cell_desc>

chg_cell_element neighbor_journal <value> <cell_desc_opt>

Display command string

disp_element neighbor_journal <location> <cell_desc>

6-642 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-643
Jan 2010
network_control_order Chapter 6: CM database parameters

network_control_order

Description

The network_control_order parameter specifies the GPRS Cell Reselection order. Table 6-33
list the available configurations.

Table 6-33 Configurations for network_control_order

Responsible
Mode Functionality
element
NC0 MS control Normal GPRS mobile control.
NC1 MS control GPRS mobile control with measurement reports.
MS sends measurement reports to BSS.
MS performs autonomous cell re-selection
NC2 Network control Network control.
GPRS MS sends measurement reports to BSS.
BSS sends cell reselection commands and instructs mobile
to perform cell reselection
Enhanced MS control All functionality in NC0 mode.
NC0 BSS sends reselection commands to GPRS.
MS to change cell reselection mode
Enhanced MS Control All functionality in NC1 mode.
NC1 BSS sends cell reselection command to GPRS mobile to
change cell reselection mode

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes

Dependencies The GPRS and NCCR features must be unrestricted.

The PCU must be equipped.

Syntax

Change command strings

chg_element network_control_order <value> <location> <cell_desc>

chg_cell_element network_control_order <value> <cell_desc_opt>

6-644 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command string

disp_element network_control_order <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 4 (mode values)
0 NC0
1 NC1
2 NC2
3 Enhanced NC0
4 Enhanced NC1
Default value 0

68P02901W23-T 6-645
Jan 2010
new_calls_amr_hr Chapter 6: CM database parameters

new_calls_amr_hr

{34452}

Description

The new_calls_amr_hr parameter is used to define the congestion threshold to indicate at

which congestion level, the new half-rate capable calls with AMR HR as the first permitted HR
speech version are assigned as AMR half-rate calls.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies
This parameter can only be modified if the AMR
feature is unrestricted. Also, the value of the
new_calls_amr_hr parameter must be less than or
equal to the new_calls_hr parameter unless the
threshold is disabled.

This element can be modified inside and outside

SYSGEN mode. When AMR HR is not enabled at the
BSS level or at the cell level, the BSS SW ignores
the threshold.

Syntax

Change command string

chg_cell_element new_calls_amr_hr <value> <cell_desc>

chg_element new_calls_amr_hr <value> <location> <cell_desc>

Display command string

disp_element new_calls_amr_hr <location> <cell_desc>

6-646 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 101
0 Minimum
101 Maximum
Setting the value to 101 disables the congestion
mechanism.
Default value 101

68P02901W23-T 6-647
Jan 2010
new_calls_hr Chapter 6: CM database parameters

new_calls_hr

Description

The new_calls_hr parameter specifies the congestion threshold to indicate at what congestion
level the BSS should start assigning new half-rate capable calls as AMR/GSM half-rate calls.
A limitation exists based on the number of idle half-rate channels and free generic traffic
channels in the cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or GSM Half Rate feature must be
unrestricted.
The new_calls_hr congestion threshold is ignored if the
AMR/GSM HR mode is not enabled at the BSS level or at
the Cell level.

Syntax

Add/Change command strings

chg_element new_calls_hr <value> <location> <cell_desc>

chg_cell_element new_calls_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element new_calls_hr <location> <cell_desc>

Values

Value type Integer (in steps of 1%)

Valid range 0 to 101
Default value 101 101 disables this parameter.

6-648 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ni

ni

Description

The ni parameter specifies the Network Indicator (NI) that establishes a method of
differentiation between international and national messages.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.
Operator actions The MTL must be locked then unlocked for the change to
take effect.

Syntax

Change command string

chg_element ni <value> 0

Display command string

disp_element ni 0

Values

Value type Integer

Valid range 0 to 3
0 International Network
1 Spare (for international use only)
2 National Network
3 Reserved for national use
Default value None

68P02901W23-T 6-649
Jan 2010
References Chapter 6: CM database parameters

References

GSM specification ITU - TSS Q.708

This is a Motorola defined parameter.

6-650 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ns_alive_retries

ns_alive_retries

Description

The ns_alive_retries parameter specifies the number of retries generated to establish if an

NSVC is alive.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when this parameter is
changed.

Syntax

Change command string

chg_element ns_alive_retries <value> <location>

Display command string

disp_element ns_alive_retries <location>

Values

Value type Integer (number of retries)

Valid range 1 to 10
Default value 3

68P02901W23-T 6-651
Jan 2010
ns_block_retries Chapter 6: CM database parameters

ns_block_retries

Description

The ns_block_retries parameter specifies the number of retries generated to block an NSVC.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when this parameter is
changed.

Syntax

Change command string

chg_element ns_block_retries <value> <location>

Display command string

disp_element ns_block_retries <location>

Values

Value type Integer (number of retries)

Valid range 1 to 3
Default value 3

6-652 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ns_unblock_retries

ns_unblock_retries

Description

The ns_unblock_retires parameter specifies the number of retries generated to unblock an

NSVC.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when this parameter is
changed.

Syntax

Change command string

chg_element ns_unblock_retries <value> <location>

Display command string

disp_element ns_unblock_retries <location>

Values

Value type Integer (number of retries)

Valid range 1 to 3
Default value 3

68P02901W23-T 6-653
Jan 2010
nsei Chapter 6: CM database parameters

nsei

Description

The nsei parameter specifies the Network Service Entity Identifier (NSEI) used by the PCUs
over the Gb interface. There can be only one NSEI associated with each PCU.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.
Sysgen mode cannot be left until the nsei parameter has
been configured by the operator.
The nsei parameter cannot be modified until all GBLs have
been locked.
Operator actions The operator must lock all GBLs in the BSS before this
element is changed.

Syntax

Change command string

chg_element nsei <value> <pcu_n>

Display command string

disp_element nsei <pcu_n>

Values

Value type Integer

Valid range 0 to 65535
Default value None

6-654 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference num_audit_retries

num_audit_retries

Description

The num_audit_retries parameter specifies the number of times CP processes audit each other
with regard to a particular connection. If an audit fails, it repeats up to the value specified by
num_audit_retries, before the auditing process clears a particular call.

This parameter provides a means of differentiating between glitches on a link and a complete
link failure.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element num_audit_retries <value> <location>

Display command string

disp_element num_audit_retries <location>

Values

Value type Integer (represents the number of repeat audits)

Valid range 0 to 5
Default value 1

68P02901W23-T 6-655
Jan 2010
num_emerg_access Chapter 6: CM database parameters

num_emerg_access

Description

The num_emerg_access parameter enables or disables the collection of statistics in relation

to the number of active TCH calls terminated to allow an emergency call to take the specified
GSM cell.

Use an index value of 0 for this element.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies None

Syntax

Change command string

stat_mode num_emerg_access <value> <cell_desc>

Display command strings

disp_stat_prop num_emerg_access <cell_desc>

Values

Value type Boolean

Valid range off or on
off Disabled
on Enabled
Default value off

6-656 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference num_emerg_rejected

num_emerg_rejected

Description

The num_emerg_rejected parameter enables or disables the collection of statistics in relation

to the number of emergency calls rejected because of a lack of resources for the selected
GSM cell.

Use an index value of 0 for this element.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies None

Syntax

Change command string

stat_mode num_emerg_rejected <value> <cell_desc>

Display command strings

disp_stat_prop num_emerg_rejected <cell_desc>

Values

Value type Boolean

Valid range off or on
off Disabled
on Enabled
Default value off

68P02901W23-T 6-657
Jan 2010
num_emerg_tch_kill Chapter 6: CM database parameters

num_emerg_tch_kill

Description

The num_emerg_tch_kill parameter enables or disables the collection of statistics in relation

to the number of active TCH calls terminated to allow an emergency call to the channel on the
specified GSM cell.

Use an index value of 0 for this element.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies None

Syntax

Change command string

stat_mode num_emerg_tch_kill <value> <cell_desc>

Display command strings

disp_stat_prop num_emerg_tch_kill <cell_desc>

Values

Value type Boolean

Valid range off or on
off Disabled
on Enabled
Default value off

6-658 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference num_emerg_term_sdcch

num_emerg_term_sdcch

Description

The num_emerg_term_sdcch parameter enables or disables the collection of statistics in

relation to the number of emergency calls that are terminated after being allocated an SDCCH
but could not be allocated a TCH for the specified GSM cell.

Use an index value of 0 for this element.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies None

Syntax

Change command string

stat_prop num_emerg_term_sdcch <value> <cell_desc>

Display command string

disp_stat_prop num_emerg_term_sdcch <cell_desc>

Values

Value type Boolean

Valid range off or on
off Disabled
on Enabled
Default value off

68P02901W23-T 6-659
Jan 2010
num_gbl_dl_thrput_samples Chapter 6: CM database parameters

num_gbl_dl_thrput_samples

Description

The num_gbl_dl_thrput_samples parameter specifies the number of samples used to compute

the gbl_dl_data_thrput statistic.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change
is made.

Syntax

Change command string

chg_element gbl_dl_thrput_samples <value> <location> <cell_desc>

Display command string

disp_element gbl_dl_thrput_samples <location> <cell_desc>

Values

Value type Integer (number of samples)

Valid range 1 to 10
Default value 10

6-660 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference num_gbl_ul_thrput_samples

num_gbl_ul_thrput_samples

Description

The num_gbl_ul_thrput_samples parameter specifies the number of samples used to compute

the gbl_ul_data_thrput statistic.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change
is made.

Syntax

Change command string

chg_element gbl_ul_thrput_samples <value> <location> <cell_desc>

Display command string

disp_element gbl_ul_thrput_samples <location> <cell_desc>

Values

Value type Integer (number of samples)

Valid range 1 to 10
Default value 10

68P02901W23-T 6-661
Jan 2010
number_of_preferred_cells Chapter 6: CM database parameters

number_of_preferred_cells

Description

The number_of_preferred_cells parameter specifies the maximum number of target cells to be

included in a Handover Required message.

The preferred list of target cells is a mandatory BSS field. The number of preferred cells is
given in order of predicted best performance.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element number_of_preferred_cells <value> <location> <cell_desc>

chg_cell_element number_of_preferred_cells <value> <cell_desc_opt>

Display command strings

disp_cell <cell_desc> [full]

disp_element number_of_preferred_cells <location> <cell_desc>

Values

Value type Integer (represents preferred cells)

Valid range 1 to 16
Default value 16

6-662 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM specification 8.08 - 3.1.5.1.1

This is a Motorola defined parameter.

68P02901W23-T 6-663
Jan 2010
number_sdcchs_preferred Chapter 6: CM database parameters

number_sdcchs_preferred

Description

The number_sdcchs_preferred parameter specifies the preferred number of Standalone

Dedicated Control Channels (SDCCHs) that the reconfiguration algorithm tries to maintain.

When channel reconfiguration is enabled, the CRM attempts to maintain the preferred number
of SDCCHs for Immediate Assignments.

The reconfiguration either of consist idle TCHs being converted to SDCCHs or free SDCCHs
being converted to TCHs.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The valid range for this parameter depends on ccch_conf.
The value must be less than or equal to the
max_number_of_sdcchs.

NOTE
To maximize the PDCHs configuration on the carrier A, the BTS Cell Resource
Manager (CRM) avoids configuring SDCCHs to the double density CTU2 EGPRS
carrier A and its paired carrier B.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element number_sdcchs_preferred <value> <location> <cell_desc>

chg_cell_element number_sdcchs_preferred <value> <cell_desc_opt>

6-664 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command strings

disp_cell <cell_id> [full]

disp_element number_sdcchs_preferred <location> <cell_desc>

Values

Value type Integer (number of SDCCHs)

Valid range If feature SDCCH increase is unrestricted, then
4 to 124 If ccch_conf = 1.
8 to 128 If ccch_conf = 0.
If feature SDCCH increase is restricted, then
4 to 44 If ccch_conf = 1.
8 to 48 If ccch_conf = 0.
Default value 12 if ccch_conf = 1,
16 if ccch_conf is not equal to 1

References

GSM specification 5.02 - 6.4

This is a Motorola defined parameter.

68P02901W23-T 6-665
Jan 2010
opc Chapter 6: CM database parameters

opc

Description

The opc parameter specifies the Originating Point Code (OPC). The values for the OPC are
stored as a 14-bit binary code for non-ANSI and 24-bit binary code for ANSI.

If the opc parameter is set to equal the dpc, but not equal to lb_int_dpc, the system issues a
warning:

COMMAND ACCEPTED: WARNING: When opc equals dpc, communication with MSC is impossible.

If the opc parameter is set to equal the lb_int_dpc and lcs_mode is 2, but not equal to dpc, the
system issues a warning:

COMMAND ACCEPTED: WARNING: When lb_int_dpc is equal to the opc, communication

with the BSS-based SMLC is impossible.

If the opc parameter is set to equal the lb_int_dpc and equal to dpc, and lcs_mode is 2, the
system issues a warning:

COMMAND ACCEPTED: WARNING: dpc and lb_int_dpc should not be equal to opc.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The range of opc depends on the values for the ss7_mode
on page 6-871.
This parameter only applies to the BSC.

Syntax

Change command string

chg_element opc <value> 0

Display command string

disp_element opc 0

6-666 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 16383 If ss7_mode = 0 (ITU-TSS)
0 to If ss7_mode = 1 (ANSI)
16777215
Default value None

References

GSM specification ITU-TSS Q.708

This is a Motorola defined parameter.

68P02901W23-T 6-667
Jan 2010
option_alg_a5_1 Chapter 6: CM database parameters

option_alg_a5_1

Description

The option_alg_a5_1 parameter enables or disables the encryption algorithm A5/1.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter applies only to the BSC.
The A5/1 feature must be unrestricted.

Syntax

Change command string

chg_element option_alg_a5_1 <value> 0

Display command string

disp_element option_alg_a5_1 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification 8.08

This is a Motorola defined parameter.

6-668 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference option_alg_a5_2

option_alg_a5_2

Description

The option_alg_a5_2 parameter enables or disables the encryption algorithm A5/2.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.
The A5/2 feature must be unrestricted.

Syntax

Change command string

chg_element option_alg_a5_2 <value> 0

Display command string

disp_element option_alg_a5_2 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification 8.08

This is a Motorola defined parameter.

68P02901W23-T 6-669
Jan 2010
option_alg_a5_3 Chapter 6: CM database parameters

option_alg_a5_3

Description

The option_alg_a5_3 parameter enables or disables the encryption algorithm A5/3.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.
The A5/3 feature must be unrestricted.

Syntax

Add/Change command string

chg_element option_alg_a5_3 <value> 0

Display command string

disp_element option_alg_a5_3 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification 8.08

This is a Motorola defined parameter.

6-670 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference option_alg_a5_4

option_alg_a5_4

Description

The option_alg_a5_4 parameter enables or disables the encryption algorithm A5/4.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.
The A5/4 feature must be unrestricted.

Syntax

Add/Change command string

chg_element option_alg_a5_4 <value> 0

Display command string

disp_element option_alg_a5_4 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification 8.08

This is a Motorola defined parameter.

68P02901W23-T 6-671
Jan 2010
option_alg_a5_5 Chapter 6: CM database parameters

option_alg_a5_5

Description

The option_alg_a5_5 parameter enables or disables the encryption algorithm A5/5.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.
The A5/5 feature must be unrestricted.

Syntax

Add/Change command string

chg_element option_alg_a5_5 <value> 0

Display command string

disp_element option_alg_a5_5 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification 8.08

This is a Motorola defined parameter.

6-672 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference option_alg_a5_6

option_alg_a5_6

Description

The option_alg_a5_6 parameter enables or disables the encryption algorithm A5/6.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.
The A5/6 feature must be unrestricted.

Syntax

Add/Change command string

chg_element option_alg_a5_6 <value> 0

Display command string

disp_element option_alg_a5_6 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification 8.08

This is a Motorola defined parameter.

68P02901W23-T 6-673
Jan 2010
option_alg_a5_7 Chapter 6: CM database parameters

option_alg_a5_7

Description

The option_alg_a5_7 parameter enables or disables the encryption algorithm A5/7.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.
The A5/7 feature must be unrestricted.

Syntax

Add/Change command string

chg_element option_alg_a5_7 <value> 0

Display command string

disp_element option_alg_a5_7 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification 8.08

This is a Motorola defined parameter.

6-674 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference option_preempt

option_preempt

Description

The option_preempt parameter enables or disables the Emergency Call Preemption (ECP)
feature and/or the Enhanced Multi-level Precedence and Preemption (eMLPP) feature.

NOTE
This renamed parameter was formerly named option_emergency_preempt.

The ECP feature enables the BSS to provide access for emergency calls regardless of other
traffic currently on the BSS. An emergency call is identified in the RACH burst from the MS, or
the service type is Emergency call establishment in the CM Service Request message.

The eMLPP feature allows calls to be allocated a precedence depending on their function.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter applies only at the BSC.
The eMLPP feature must be unrestricted for values 0 to 3,
otherwise the range is 0 to 1.

Syntax

Change command string

chg_element option_preempt <value> 0

Display command string

disp_element option_preempt 0

68P02901W23-T 6-675
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range
0 to 3
0 ECP and eMLPP are both disabled.
1 ECP enabled.
2 eMLPP enabled.
3 ECP and eMLPP are both enabled.
Default value 0

References

GSM specification 02.11, Service Accessibility, version 4.5.0 [3]

04.08, Mobile Radio Interface Layer 3 Specification, version
4.8.0[1]
03.22, functions related to MS in idle Mode, version 4.5.0[7]
This is a Motorola defined parameter.

6-676 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference outer_zone_usage_level

outer_zone_usage_level

Description

The outer_zone_usage_level parameter specifies the percentage level of outer cell traffic
channel (TCH) usage.

If this parameter is set to 0, channels in the inner zone are used whenever an MS is qualified to
use those resources.

If this parameter is set to any other value, the inner zone resources are allocated only when an
MS is qualified and at least the specified percentage of outer zone TCHs is in use.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Concentric Cells feature must be enabled.

Syntax

Change command strings

chg_element outer_zone_usage_level <value> <location> <cell_desc>

chg_cell_element outer_zone_usage_level <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element outer_zone_usage_level <location> <cell_desc>

Values

Value type Integer (indicating the percentage of outer zone TCH usage)
Valid range 0 to 100
Default value 0

68P02901W23-T 6-677
Jan 2010
override_intra_bss_pre_transfer Chapter 6: CM database parameters

override_intra_bss_pre_transfer

Description

The override_intra_bss_pre_transfer parameter specifies whether a pre-transfer request is

sent to SM (Switch Manager) when the handover allocation message is received during an
inter-cell handover.

This parameter only applies to intra-BSS inter-cell handovers.

Call processing sends the pre-transfer request to the switch manager, to make a connection in
the downlink direction from the active CIC to the new radio channel at the time of the new radio
channel assignment. This puts voice traffic on the new radio channel that the mobile is being
handed off to earlier than when the pre-transfer function is disabled.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter applies only to the BSC or RXCDR.

Syntax

Change command string

chg_element override_intra_bss_pre_transfer <value> 0

Display command string

disp_element override_intra_bss_pre_transfer 0

Values

Value type Boolean

Valid range 0 or 1
0 Send pre-transfer request to SM.

1 Do not send pre-transfer request to SM.

Default value 0

6-678 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference pbgt_mode

pbgt_mode

Description

The pbgt_mode parameter enables the operator to select the preferred method of compensating
for a mismatch in frequency types between the serving channel and the neighbor cell BCCH
when calculating power budget.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Dual Band Cells feature must be unrestricted.
Changing this parameter to 1 adds this cell to its own
neighbor list. This autocreated neighbor cannot be deleted
by the operator and it can only be deleted by changing this
parameter back to 0.

Syntax

Change command strings

chg_element pbgt_mode <value> <location> <cell_desc>

chg_cell_element pbgt_mode <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element pbgt_mode <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
1 Enabled A new neighbor is auto-equipped with BCCH
frequency set to that of the serving cell.
0 Disabled An equipped neighbor is unequipped.
Default value 0

68P02901W23-T 6-679
Jan 2010
pccch_enabled Chapter 6: CM database parameters

pccch_enabled

Description

The pccch_enabled parameter specifies whether the PBCCH/PCCCH optional feature is

unrestricted at a cell. This feature supports GPRS Network Operation Modes I and III for
normal range cell.

Type B (Operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.
gprs_enabled must be set to 0.
The BSS must have configured the BCCH carrier of the cell
to non-hopping.
The cell must be a normal range cell.

Operator actions In order to enable PBCCH/PCCCH for a cell,

gprs_enabled must be set to 0 - disable
pccch_enabled must be set to 1 - enable
gprs_enabled must be set to 1 - enable.

Syntax

Change command string

chg_element pccch_enabled <value> <location> <cell_desc>

chg_cell_element pccch_enabled <value> <cell-desc_opt>

chg_cell_element <location> pccch_enabled <value> all

Display command string

disp_cell <cell_id> full

disp_element pccch_enabled <location> <cell-desc>

disp_element pccch_enabled <location> all

6-680 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-681
Jan 2010
pccchOpt Chapter 6: CM database parameters

pccchOpt

Description

The pccchOpt parameter indicates whether the Packet Broadcast Control Channel/Packet
Common Control Channel (PBCCH/PCCCH) feature option is unrestricted in the BSS software.

If restricted, any attempt to access the other PBCCH/PCCCH parameters is rejected.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The PBCCH/PCCCH features must be unrestricted to
provide their associated functionality.

Syntax

Display command string

disp_options

Values

Value type Boolean

Valid range 0 or 1
0 Restricted
1 Unrestricted
Default value None

6-682 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference pch_queue_length_ctr

pch_queue_length_ctr

{34452}

Description

The pch_queue_length_ctr parameter sets the PCH queue length to 648 or 2*648. This
parameter can be accessed and updated both in and out of sysgen mode.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command string

chg_cell_element pch_queue_length_ctr <value> <cell_desc>

chg_element pch_queue_length_ctr <value> <location> <cell_desc>

Display command string

disp_element pch_queue_length_ctr <location> <cell_desc>

Values

Value type Integer

Valid range 1 to 2
1 Sets the PCH queue length to 648.
2 Sets the PCH queue length to 2*648.
Default value 2

68P02901W23-T 6-683
Jan 2010
pcr_enable Chapter 6: CM database parameters

pcr_enable

Description

The pcr_enable parameter enables or disables the Preventative Cyclic Retransmission (PCR)
error correction method. This method is used when transferring messages between the MSC
and the BSC (through the A-interface).

If PCR is enabled, then:

ss7_l2_t7 > 800 milliseconds.

ss7_l3_t2 > 1400 milliseconds.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.
You must reset the BSC when changing this parameter for
the change to take effect.

Syntax

Change command string

chg_element pcr_enable <value> 0

Display command string

disp_element pcr_enable 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-684 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference pcr_n1

pcr_n1

Description

The pcr_n1 parameter specifies the maximum number of message signal units to be retained for
retransmission for the PCR Error Correction method.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.

Syntax

Change command string

chg_element pcr_n1 <value> 0

Display command string

disp_element pcr_n1 0

Values

Value type Integer (message signal units)

Valid range 32 to 127
Default value 127

68P02901W23-T 6-685
Jan 2010
pcr_n2 Chapter 6: CM database parameters

pcr_n2

Description

The pcr_n2 parameter specifies the maximum number of message signal unit octets to be
retained for retransmission for the PCR Error Correction method.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter only applies to the BSC.

Syntax

Change command string

chg_element pcr_n2 <value> 0

Display command string

disp_element pcr_n2 0

Values

Value type Integer (message octets)

Valid range 950 to 3750
Default value 3750

6-686 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference pcu_redundancy

pcu_redundancy

Description

The pcu_redundancy parameter specifies whether the BSS supports PCU redundancy or
not. If entered to support redundancy, six more parameters are then prompted to specify the
mapping order.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter applies only to the BSC (location = 0).
When only one PCU is equipped, pcu_redundancy does
not prompt for redundant PCU.

Syntax

Change command string

chg_element pcu_redundancy <value> bsc

Display command string

disp_element pcu_redundancy bsc

Values

Value type Boolean

Valid range 0 PCU redundancy Off
1 PCU redundancy On
Default value 0

68P02901W23-T 6-687
Jan 2010
Prompts Chapter 6: CM database parameters

Prompts

If the value is set to 1 (PCU redundancy On) the following prompts are displayed:

Please specify first redundant for PCU 0: <pcu_red_map_01>

Please specify second redundant for PCU 0: <pcu_red_map_02>

Please specify first redundant for PCU 1: <pcu_red_map_11>

Please specify second redundant for PCU 1: <pcu_red_map_12>

Please specify first redundant for PCU 2: <pcu_red_map_21>

Please specify second redundant for PCU 2: <pcu_red_map_22>

The following table shows the possible entries and their meanings:

Parameter Valid Input Default

<pcu_red_map_01> 0, 1 or 2 No redundancy
<pcu_red_map_02> 0, 1 or 2 No redundancy
<pcu_red_map_11> 0, 1 or 2 No redundancy
<pcu_red_map_12> 0, 1 or 2 No redundancy
<pcu_red_map_21> 0, 1 or 2 No redundancy
<pcu_red_map_22> 0, 1 or 2 No redundancy

If the parameter pcu_redundancy value is set to 1 (True or On), redundancy can be set to any
of the available PCUs, including the current PCU itself, in answer to the prompts. If the prompts
are not answered, default is no redundancy.

Example display

An example of pcu_redundancy follows:

disp_element pcu_redundancy bsc

pcu_redundancy =TRUE
PCU id 1st redundant 2nd redundant
------ ------------- -------------
0 1 NA
1 2 NA
2 NA NA

6-688 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference percent_traf_cs

percent_traf_cs

Description

The percent_traf_cs parameter specifies the percentage of RSL Reserved for CS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

Syntax

Change command string

chg_element percent_traf_cs <value> <location>

Display command string

disp_element percent_traf_cs <location>

Values

Value type Integer

Valid range 0 to 90
Default value 55

68P02901W23-T 6-689
Jan 2010
persistence_level Chapter 6: CM database parameters

persistence_level

Description

The persistence_level parameter specifies values for the access persistence level for each radio
priority on a per cell basis. This parameter is always attached with a radio priority (i) of 0 to 3.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Change command string

chg_element persistence_level,i <value> <location> <cell_desc>

chg_cell_element persistence_level,i <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> full

disp_element persistence_level,i <location> <cell_desc>

6-690 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 15 representing the access persistence level:
0 persistence level 0
1 persistence level 1
2 persistence level 2
3 persistence level 3
4 persistence level 4
5 persistence level 5
6 persistence level 6
7 persistence level 7
8 persistence level 8
9 persistence level 9
10 persistence level 10
11 persistence level 11
12 persistence level 12
13 persistence level 13
14 persistence level 14
15 persistence level 16

Default value 4

68P02901W23-T 6-691
Jan 2010
pfm_sig_enabled Chapter 6: CM database parameters

pfm_sig_enabled

Description

The pfm_sig_enabled parameter enables or disables support of PFC modification signaling to

C-SGSN when there is downgrade or upgrade for non-real time PFC on a per BSS basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The pfm_sig_enabled attribute is modified only if Qos is
enabled or unrestricted at the OMC.

Syntax

Change command string

chg_element pfm_sig_enabled <value> <location>

Display command string

disp_element pfm_sig_enabled <location>

Values

Value type Boolean

Valid range 0 or 1
0 No PFC modification message sent to C-SGSN
when there is an upgrade or downgrade for non
realtime PFC.
1 PFC modification message will be sent to SGSN
when there is an upgrade or downgrade for non
realtime PFC.
Default value 1

NOTE
pfm_sig_enabled parameter is not checked when Max SDU size is re-negotiated.

6-692 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference phase_lock_gclk

phase_lock_gclk

Description

The phase_lock_gclk parameter enables or disables phase locking for the GCLK board at a site.

Phase locking means the GCLK board is synchronized with the clock of the MMS selected
as determined by the mms_priority value. The mms_priority value is specified using the
modify_value command.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element phase_lock_gclk <value> <location>

Display command string

disp_element phase_lock_gclk <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-693
Jan 2010
phase_lock_retry Chapter 6: CM database parameters

phase_lock_retry

Description

The phase_lock_retry parameter specifies the time in minutes during which phase locking is
automatically retried after failure.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element phase_lock_retry <value> <location>

Display command string

disp_element phase_lock_retry <location>

Values

Value type Integer (minutes)

Valid range 0 to 255
0 Immediate phase_lock_retry.
1 to 254 Time period for retrying phase locking.
255 No phase_lock_retry.
Default value 255

6-694 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference phase2_classmark_allowed

phase2_classmark_allowed

Description

The phase2_classmark_allowed parameter defines the format of the classmark parameter

sent to the MSC based on GSM phases.

If this parameter is changed from 2 to any other value, and inter_rat_enabled is equal to 4, 5, 6
or 7 for any cell in that BSS, the BSS issues the following warning:

Warning: phase2_classmark_allowed must support multiband for Enhanced 2G/3G.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter applies only to BSC sites.
This parameter does not apply to RXCDR sites.
If the Location Services feature is enabled and the operator
attempts to change the phase2_classmark_allowed
parameter to a value which does not support multiband,
the command is rejected.
This dependency is also checked during database
verification (see the lcs_mode section).

Syntax

Change command string

chg_element phase2_classmark_allowed <value> 0

Display command string

disp_element phase2_classmark_allowed 0

68P02901W23-T 6-695
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 2
0 Formatted for Phase 1
1 Formatted for Phase 2
2 Formatted for Phase 2 with Multiband
Default value 0

6-696 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference phase2_resource_ind_allowed

phase2_resource_ind_allowed

Description

The phase2_resource_ind_allowed parameter specifies the GSM Phase format the BSS uses to
send Resource Request messages to the MSC.

If this parameter is set to 0, the BSS sends the messages in the GSM Phase 1 format.

If this parameter is set to 1, the BSS sends the messages in the GSM Phase 2 format.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter applies only to BSC sites.
This parameter does not apply to RXCDR sites.

Syntax

Change command string

chg_element phase2_resource_ind_allowed <value> 0

Display command string

disp_element phase2_resource_ind_allowed 0

Values

Value type Boolean

Valid range 0 or 1
0 GSM Phase 1 format
1 GSM Phase 2 format
Default value 0

68P02901W23-T 6-697
Jan 2010
pic_error_clr_thresh Chapter 6: CM database parameters

pic_error_clr_thresh

Description

The pic_error_clr_thresh parameter specifies the error count threshold (equal to or less than)
for an alarm to be cleared for a Path Identity Code (PIC).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The ECERM feature must be unrestricted.
Two successful calls are required to clear an alarm within
this threshold. (One call may be too short for the Channel
Coder Unit (CCU) to send an error indication, thus clearing
the alarm prematurely.)
This parameter can be set only at a BSC.
If the threshold is increased during operation, any existing
counts between the new and the old threshold does not
clear an alarm until another successful call is made or the
next successful GPRS time period occurs on the PIC.
With the ECERM feature unrestricted,
(pic_error_gen_thresh - pic_error_clr_thresh) must be
greater than or equal to 2.

Syntax

Change command string

chg_element pic_error_clr_thresh <value> 0

Display command string

disp_element pic_error_clr_thresh 0

Values

Value type Integer

Valid range 0 to 253
Default value 0

6-698 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference pic_error_gen_thresh

pic_error_gen_thresh

Description

The pic_error_gen_thresh parameter specifies the error count threshold (equal to or greater
than) for an alarm to be generated for a Path Identity Code (PIC).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The ECERM feature must be unrestricted.
This parameter can be set only at a BSC.
If the threshold is reduced during operation, any existing
counts between the new and the old threshold will not
cause an alarm.
With the ECERM feature unrestricted,
(pic_error_gen_thresh - pic_error_clr_thresh) must be
greater than or equal to 2.

Syntax

Change command string

chg_element pic_error_gen_thresh <value> 0

Display command string

disp_element pic_error_gen_thresh 0

Values

Value type Integer

Valid range 2 to 255
Default value 6

68P02901W23-T 6-699
Jan 2010
pic_error_inc Chapter 6: CM database parameters

pic_error_inc

Description

The pic_error_inc parameter specifies the error count increment when the Enhanced Circuit
Error Rate Monitor (ECERM) feature is in use for Path Identity Codes (PICs) on a per BSC basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The ECERM feature must be unrestricted.
This parameter can be set only at a BSC.

Syntax

Change command string

chg_element pic_error_inc <value> 0

Display command string

disp_element pic_error_inc 0

Values

Value type Integer

Valid range 0 PIC alarms not raised.
1 to 255 PIC alarms raised.
Default value 0 If ECERM feature is restricted.
1 If ECERM feature is not restricted

6-700 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference pool_gproc_preemption

pool_gproc_preemption

Description

The pool_gproc_preemption parameter specifies what type of preemption to use for pool
GPROCs.

When a pool GPROC running a function goes OOS and there are no available pool GPROCs, the
INS pool GPROCs can be searched for a lower priority function. If such a function is found, it
is bumped from its GPROC by the higher priority function.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be set only at a BSC.
This parameter cannot be set at an RXCDR

Syntax

Change command string

chg_element pool_gproc_preemption <value> 0

Display command string

disp_element pool_gproc_preemption 0

Values

Value type Integer

Valid range 0 to 2
0 No replacement
1 Replacement based on function priority
2 Replacement based on function and intra-function priorities
Default value 1

68P02901W23-T 6-701
Jan 2010
poor_initial_assignment Chapter 6: CM database parameters

poor_initial_assignment

Description

The poor_initial_assignment parameter enables or disables checking the timing advance on a

Random Access Channel (RACH). If the RACH is greater than ms_max_range, this indicates
that there has been a poor initial assignment, and therefore the RACH is discarded.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies ms_max_range

Syntax

Change command string

chg_element poor_initial_assignment <value> <location>

Display command string

disp_element poor_initial_assignment <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-702 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference pow_inc_step_size_dl

pow_inc_step_size_dl

Description

The pow_inc_step_size_dl parameter specifies the step sizes for power increases from the
BTS to the MS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter must be greater than or equal to
pow_red_step_size_dl.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element pow_inc_step_size_dl <value> <location> <cell_desc>

chg_cell_element pow_inc_step_size_dl <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element pow_inc_step_size_dl <location> <cell_desc>

Values

Value type Integer (dB)

Valid range 2, 4, 6, 8, 10, 12 or 14
Default value 2

68P02901W23-T 6-703
Jan 2010
References Chapter 6: CM database parameters

References

GSM parameter POW_INC_STEP_SIZE_DL

GSM specification 12.20 - 5.2.8.23 - power Ctrl BTS - pow Incr Step Size

6-704 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference pow_inc_step_size_ul

pow_inc_step_size_ul

Description

The pow_inc_step_size_ul parameter specifies the step size for power increases from the
MS to the BTS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter must be greater than or equal to
pow_red_step_size_ul.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element pow_inc_step_size_ul <value> <location> <cell_desc>

chg_cell_element pow_inc_step_size_ul <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element pow_inc_step_size_ul <location> <cell_desc>

Values

Value type Integer (dB)

Valid range 2, 4, 6, 8, 10 12 or 14
Default value 2

68P02901W23-T 6-705
Jan 2010
References Chapter 6: CM database parameters

References

GSM parameter POW_INC_STEP_SIZE_UL

GSM specification 12.20 - 5.2.8.23 - power Ctrl BTS - pow Incr Step Size

6-706 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference pow_red_step_size_dl

pow_red_step_size_dl

Description

The pow_red_step_size_dl parameter specifies the step size for power decreases from the
BTS to the MS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter must be less than or equal to
pow_inc_step_size_dl.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element pow_red_step_size_dl <value> <location> <cell_desc>

chg_cell_element pow_red_step_size_dl <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element pow_red_step_size_dl <location> <cell_desc>

Values

Value type Integer (dB)

Valid range 2 or 4
Default value 2

68P02901W23-T 6-707
Jan 2010
References Chapter 6: CM database parameters

References

GSM parameter POW_RED_STEP_SIZE_DL

GSM specification 12.20 - 5.2.8.23 - power Ctrl BTS - pow Red Step Size

6-708 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference pow_red_step_size_ul

pow_red_step_size_ul

Description

The pow_red_step_size_ul parameter specifies the step size for power decreases from the
MS to the BTS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Must be less than or equal to pow_inc_step_size_ul.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element pow_red_step_size_ul <value> <location> <cell_desc>

chg_cell_element pow_red_step_size_ul <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element pow_red_step_size_ul <location> <cell_desc>

Values

Value type Integer (dB)

Valid range 2 or 4
Default value 2

References

GSM parameter POW_RED_STEP_SIZE_UL

GSM specification 12.20 - 5.2.8.23 - power Ctrl BTS - pow Red Step Size

68P02901W23-T 6-709
Jan 2010
power_save_enable Chapter 6: CM database parameters

power_save_enable

Description

The power_save_enable parameter enables or disables SW enabler for PA bias switch on/off on
CTU2D feature and Using PA bias feature in mixed radio Horizon II sites on a per SITE basis.
This parameter can be accessed and updated both in and out of sysgen mode.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies {34416}

The value of this parameter can be set to 1 only if SW

enabler for PA bias switch on/off on CTU2D feature
is unrestricted.

The value of this parameter can be set to 2 only if SW

enabler for PA bias switch on/off on CTU2D feature
and Using PA bias feature in mixed radio Horizon II
sites are unrestricted.

The value of this parameter can be set to 1 or 2 only

in Horizon II sites.

Syntax

Change command string

chg_element power_save_enable <value> <location>

Display command strings

disp_element power_save_enable <location>

6-710 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

{34416}

Value type Integer

Valid range 0 to 2
0 SW enabler for PA bias switch on/off on CTU2D feature and
Using PA bias feature in mixed radio Horizon II sites are
disabled.
1 SW enabler for PA bias switch on/off on CTU2D feature is
enabled and Using PA bias feature in mixed radio Horizon II
sites is disabled.
2 SW enabler for PA bias switch on/off on CTU2D feature
and Using PA bias feature in mixed radio Horizon II sites
are enabled
Default value 0

68P02901W23-T 6-711
Jan 2010
prach_max_retran Chapter 6: CM database parameters

prach_max_retran

Description

The prach_max_retran parameter specifies the maximum number of retransmissions allowed

for each radio priority level (i) on a per cell basis. This parameter is always attached with a
radio priority (i) of 0 to 3.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Change command string

chg_element prach_max_retran,i <value> <location> <cell_desc>

chg_cell_element prach_max_retran,i <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> full

disp_element prach_max_retran,i <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 3 Representing the number of retransmissions:
0 1 retransmission
1 2 retransmissions
2 4 retransmissions
3 7 retransmissions
Default value 2 (4 retransmissions)

6-712 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference prach_s

prach_s

Description

The prach_s parameter specifies the minimum number of frames between two successive
Packet Channel request messages. It is actually the number of slots between two successive
Packet Channel request messages on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Change command string

chg_element prach_s <value> <location> <cell_desc>

chg_cell_element prach_s <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> full

disp_element prach_s <location>

68P02901W23-T 6-713
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (number of frames)

Valid range 0 to 9 representing the number of slots S:
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
Valid range 8 (S =163)

6-714 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference prach_tx_int

prach_tx_int

Description

The prach_tx_int parameter specifies the number of frame slots to spread the transmission of
the random access.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Change command string

chg_element prach_tx_int <value> <location> <cell_desc>

chg_cell_element prach_tx_int <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> full

disp_element prach_tx_int <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 15 number of frame slots (see Table 6-34)
Default value 14 (32 slots)

68P02901W23-T 6-715
Jan 2010
Values Chapter 6: CM database parameters

Table 6-34 Values for prach_tx_int representing number of frame slots

Value Number of slots Value Number of slots

0 2 slots 8 10 slots
1 3 slots 9 12 slots
2 4 slots 10 14 slots
3 5 slots 11 16 slots
4 6 slots 12 20 slots
5 7 slots 13 25 slots
6 8 slots 14 32 slots
7 9 slots 15 50 slots

6-716 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference primary_pcu

primary_pcu

Description

The primary_pcu parameter maps a cell to a specific PCU, which then becomes the primary
PCU, when more than one PCU is equipped at the BSC.

If the primary PCU for a cell goes Out Of Service, the cell is assigned to the next redundant PCU
(see pcu_redundancy parameter). If the primary PCU for a cell then returns In Service, the cell
is remapped to the primary PCU.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

NOTE
When an attempt is made to change primary_pcu, and the requested PDTCHs exceed
the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a
warning to indicate that there is not enough GDS or PMC resource available.

Syntax

Change command strings

chg_cell_element <location> primary_pcu <value> <cell_desc_opt>

chg_element primary_pcu <value> location [<cell_desc>]

Display command strings

disp_element primary_pcu <location> <cell_desc>

68P02901W23-T 6-717
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range -1or 0
-1 No primary PCU
0 PCU_0 is the cell primary PCU
Default value -1

6-718 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference prioritize_microcell

prioritize_microcell

Description

The prioritize_microcell parameter specifies whether the level (micro or macro) of the serving
cell affects the sorting of the candidate list.

If prioritize_microcell is set to 0, the Handovers (HO) level of the service cell does not affect
sorting of the candidate list.

If prioritize_microcell is set to 1, the level of the serving cell affects the sorting of the
candidate list.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Microcell feature must be unrestricted.

Syntax

Change command strings

chg_element prioritize_microcell <value> <location> <cell_desc>

chg_cell_element prioritize_microcell <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element prioritize_microcell <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 No impact on sorting
1 Impact on sorting
Default value 1

68P02901W23-T 6-719
Jan 2010
priority_class Chapter 6: CM database parameters

priority_class

Description

The priority_class specifies the Hierarchical Cell Structure (HCS) for a cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Add/Change command strings

chg_element priority_class <value> <location> <cell_desc>

chg_cell_element priority_class <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element priority_class <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 7
0 lowest priority
7 highest priority
Default value 0

6-720 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference protect_last_ts

protect_last_ts

Description

The protect_last_ts parameter specifies the switchability of PDTCH when there is one (and
only one) switchable PDTCH on a carrier and none are reserved.

When protect_last_ts is set to 1, the PDTCH may not be allocated to a voice call unless there is
no data flowing or queued for that timeslot. Incoming handover may not be allocated to this
timeslot. However, new calls may be allocated to the timeslot provided no data flow exists.

When protect_last_ts is set to 0, there is no restriction and the last remaining switchable
PDTCH can be taken for a voice call.

The last timeslot available cannot be occupied by a CS call which is being handed-over to the cell
when the cell has protect_last_ts enabled. For a CS handover to the last non-reserved PDTCH,
there is a hand shake between CS and PS which takes too long for the handover to complete. It
still works for non-handover usage. This is only an issue when there are no reserved PDTCHs.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted. Queuing must
be enabled and the priority sent from the MSC in the
assignment request must be a value between 1 and 14;
if this is not done, the last timeslot acts like a reserved
timeslot.

Syntax

Change command strings

chg_element protect_last_ts <value> <location> <cell_desc>

chg_cell_element protect_last_ts <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element protect_last_ts <location> <cell_desc>

68P02901W23-T 6-721
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 Last timeslot is not protected.
1 Last timeslot is protected.
Default value 0

6-722 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference prp_capacity_opt

prp_capacity_opt

Description

The prp_capacity_opt parameter indicates whether the Packet Resource Processor (PRP)
capacity is unrestricted in the BSS software.

If restricted, any attempt to access the other Enhanced Scheduling parameters is rejected.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

Syntax

Display command string

disp_options

Values

Value type Boolean

Valid range 0 or 1
0 Restricted
1 Unrestricted
Default value None

68P02901W23-T 6-723
Jan 2010
prp_fanout_mode Chapter 6: CM database parameters

prp_fanout_mode

Description

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.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies Increase the Throughput of PRP with PCU optional feature
must be unrestricted.

Syntax

Change command strings

chg_element prp_fanout_mode <value> <location>

Display command strings

disp_element prp_fanout_mode <location>

Values

Value type Integer

Valid range 1 or 2
1 The rolling blackout mechanism is enabled on PCU. The PRP
throughput increase feature is deactivated.
2 The rolling blackout mechanism is disabled on PCU. The PRP
throughput increase feature is activated.
Default value 1

6-724 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference prpThptOpt

prpThptOpt

Description

The prpThptOpt parameter indicates whether the Increase PRP Throughput with PCU feature
is unrestricted or not in the BSS software.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies If the prpThptOpt flag indicates that Increase the
Throughput of PRP with PCU is restricted, attempts to
change this feature specific database parameters will be
rejected.

Syntax

Display command strings

disp_options

Values

Value type Integer

Valid range 0 to 1
Default value N/A

68P02901W23-T 6-725
Jan 2010
prr_aggr_factor Chapter 6: CM database parameters

prr_aggr_factor

Description

The prr_aggr_factor parameter represents a coefficient for a linear function to dynamically

allocate or deallocate reserved PRR blocks. The aggressive factor of 0 specifies that each cell in
the BSS system has gprs_min_prr_blks number of PRR blocks allocated.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies Modification of prr_aggr_factor has no effect for cells that
have the pccch_enabled parameter enabled.

Syntax

Change command strings

chg_element prr_aggr_factor <value> <location>

Display command strings

disp_element prr_aggr_factor <location>

Values

Value type Integer

Valid range 0 to 4
Default value 3

6-726 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference psi_trau_fill_frames_threshold

psi_trau_fill_frames_threshold

Description

The new per BSS element psi_trau_fill_frames_threshold specifies the maximum allowable
percentage of all TRAU frames transmitted that can be fill frames.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command strings

chg_element psi_trau_fill_frames_threshold <value> <location>

Display command strings

disp_element psi_trau_fill_frames_threshold <location>

Values

Value type Integer

Valid range 0 to 100
Default value 10

68P02901W23-T 6-727
Jan 2010
puak_compress_mode Chapter 6: CM database parameters

puak_compress_mode

{34452}

Description

The puak_compress_mode parameter specifies the PUAK working modes, and includes the
following modes:
Flexible PUAK mode

Forced compressed PUAK mode

Forced uncompressed PUAK mode

This parameter can be accessed and updated both in and out of sysgen mode without warning.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the EGPRS
feature is enabled.

Syntax

Change command string

chg_element puak_compress_mode <value> <location>

Display command string

disp_element puak_compress_mode <location>

Values

Value type Integer

Valid range 0 to 2
0 Flexible PUAK mode.
1 Forced compressed PUAK mode.
2 Forced uncompressed PUAK mode.
Default value 0

6-728 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Pw_Save_SwitchOpt

Pw_Save_SwitchOpt

Description

The Pw_Save_SwitchOpt parameter indicates whether the SW enabler for PA bias switch on/off
on CTU2D and Using PA bias feature in mixed radio Horizon II sites features are disabled or
enabled at the BSS.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Display command strings

disp_options

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value N/A

68P02901W23-T 6-729
Jan 2010
pwr_handover_allowed Chapter 6: CM database parameters

pwr_handover_allowed

Description

The pwr_handover_allowed parameter enables or disables the power budget assessment

for handovers.

When enabled, a handover to cell n may be required if: PBGT(n) - ho_margin(n) > 0.

This comparison ensures that the MS is always linked to the cell with the minimum path loss
even though the quality and level thresholds may not have been exceeded.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element pwr_handover_allowed <value> <location> <cell_desc>

chg_cell_element pwr_handover_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element pwr_handover_allowed <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

6-730 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter EN_PBGT_HO

GSM specification 5.08 - Appendix A, 3.1f: PBGT(N)
12.20 - 5.2.8.18 - enable BSS Handover Control - enable
Pwr Budget Handover

68P02901W23-T 6-731
Jan 2010
pwrc Chapter 6: CM database parameters

pwrc

Description

The pwrc parameter specifies whether the Broadcast Control Channels (BCCH) measurement
are included in the averaged value of hopping frequencies.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element pwrc <value> <location> <cell_desc>

chg_cell_element pwrc <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element pwrc <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Include BCCH measurement
1 Do not include BCCH measurement
Default value 1

6-732 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM parameter PWRC

GSM specification GSM 4.08
5.08

68P02901W23-T 6-733
Jan 2010
qosP2Opt Chapter 6: CM database parameters

qosP2Opt

Description

The qosP2Opt parameter indicates whether the Qos Phase 2 feature is Enabled/Disabled
in the BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS Phase 2 feature requires the QoS feature to be
enabled.

Syntax

Display command strings

disp_options [all]

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value N/A

6-734 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference qos_mbr_enabled

qos_mbr_enabled

Description

The qos_mbr_enabled parameter enables or disables support of Max Bit Rate or Peak Bit Rate
enforcement on a per BSS basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The qos_mbr_enabled attribute is modified only if Qos
Phase II is enabled/unrestricted at the OMC.

Syntax

Change command strings

chg_element qos_mbr_enabled <value> <location>

Display command strings

disp_element qos_mbr_enabled <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-735
Jan 2010
qos_mtbr_be_dl Chapter 6: CM database parameters

qos_mtbr_be_dl

Description

The qos_mtbr_be_dl parameter specifies the downlink Minimum Throughput Budget

Requirement (in kbit/s) ranging from 2 to 6 for the Best Effort traffic class.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.

Syntax

Change command strings

chg_element qos_mtbr_be_dl <location> <cell_desc>

chg_cell_element qos_mtbr_be_dl <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element qos_mtbr_be_dl <location> <cell_desc>

Values

Value type Integer

Valid range 2 to 6
Default value 2

6-736 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference qos_mtbr_be_ul

qos_mtbr_be_ul

Description

The qos_mtbr_be_ul parameter the uplink Minimum Throughput Budget Requirement (in
kbit/s) ranging from 2 to 6 for the Best Effort traffic class.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.

Syntax

Change command strings

chg_element qos_mtbr_be_ul <location> <cell_desc>

chg_cell_element qos_mtbr_be_ul <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element qos_mtbr_be_ul <location> <cell_desc>

Values

Value type Integer

Valid range 2 to 6
Default value 2

68P02901W23-T 6-737
Jan 2010
qos_mtbr_bg_dl Chapter 6: CM database parameters

qos_mtbr_bg_dl

Description

The qos_mtbr_bg_dl parameter the downlink Minimum Throughput Budget Requirement (in
kbit/s) ranging from 2 to 6 for the Background traffic class.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.

Syntax

Change command strings

chg_element qos_mtbr_bg_dl <location> <cell_desc>

chg_cell_element qos_mtbr_bg_dl <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element qos_mtbr_bg_dl <location> <cell_desc>

Values

Value type Integer

Valid range 2 to 6
Default value 2

6-738 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference qos_mtbr_bg_ul

qos_mtbr_bg_ul

Description

The qos_mtbr_bg_ul parameter the uplink Minimum Throughput Budget Requirement (in
kbit/s) ranging from 2-6 for the Background traffic class.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.

Syntax

Change command strings

chg_element qos_mtbr_bg_ul <location> <cell_desc>

chg_cell_element qos_mtbr_bg_ul <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element qos_mtbr_bg_ul <location> <cell_desc>

Values

Value type Integer

Valid range 2 to 6
Default value 2

68P02901W23-T 6-739
Jan 2010
qos_mtbr_i1_dl Chapter 6: CM database parameters

qos_mtbr_i1_dl

Description

The qos_mtbr_i1_dl parameter specifies the downlink Minimum Throughput Budget

Requirement (in kbit/s) ranges from 2 to 24 for Interactive traffic class, traffic handling priority
1.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.
The value of qos_mtbr_i1_dl must be greater than or equal
to qos_mtbr_i2_dl.

Syntax

Change command strings

chg_element qos_mtbr_i1_dl <location> <cell_desc>

chg_cell_element qos_mtbr_i1_dl <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element qos_mtbr_i1_dl <location> <cell_desc>

Values

Value type Integer

Valid range 2 to 24
Default value 2

6-740 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference qos_mtbr_i1_ul

qos_mtbr_i1_ul

Description

The qos_mtbr_i1_ul parameter specifies the uplink Minimum Throughput Budget Requirement
(in kbit/s) ranges from 2 to 6 for Interactive traffic class, traffic handling priority 1.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.
The value of qos_mtbr_i1_ul must be greater than or equal
to qos_mtbr_i2_ul.

Syntax

Change command strings

chg_element qos_mtbr_i1_ul <location> <cell_desc>

chg_cell_element qos_mtbr_i1_ul <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element qos_mtbr_i1_ul <location> <cell_desc>

Values

Value type Integer

Valid range 2 to 6
Default value 2

68P02901W23-T 6-741
Jan 2010
qos_mtbr_i2_dl Chapter 6: CM database parameters

qos_mtbr_i2_dl

Description

The qos_mtbr_i2_dl parameter specifies the downlink Minimum Throughput Budget

Requirement (in kbit/s) ranges from 2 to 24 for Interactive traffic class, traffic handling priority
2.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.
The value of qos_mtbr_i2_dl must be less than or equal to
the value of qos_mtbr_i1_dl for the same cell.
The value of qos_mtbr_i2_dl must be greater than or equal
to the value of qos_mtbr_i3_dl.

Syntax

Change command strings

chg_element qos_mtbr_i2_dl <location> <cell_desc>

chg_cell_element qos_mtbr_i2_dl <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element qos_mtbr_i2_dl <location> <cell_desc>

Values

Value type Integer

Valid range 2 to 24
Default value 2

6-742 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference qos_mtbr_i2_ul

qos_mtbr_i2_ul

Description

The qos_mtbr_i2_ul parameter specifies the uplink Minimum Throughput Budget Requirement
(in kbit/s) ranges from 2 to 6 for Interactive traffic class, traffic handling priority 2.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.
The value of qos_mtbr_i2_ul must be less than or equal to
the value of qos_mtbr_i1_ul for the same cell.
The value of qos_mtbr_i2_ul must be greater than or equal
to the value of qos_mtbr_i3_ul.

Syntax

Change command strings

chg_element qos_mtbr_i2_ul <location> <cell_desc>

chg_cell_element qos_mtbr_i2_ul <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element qos_mtbr_i2_ul <location> <cell_desc>

Values

Value type Integer

Valid range 2 to 6
Default value 2

68P02901W23-T 6-743
Jan 2010
qos_mtbr_i3_dl Chapter 6: CM database parameters

qos_mtbr_i3_dl

Description

The qos_mtbr_i3_dl parameter specifies the downlink Minimum Throughput Budget

Requirement (in kbit/s) ranges from 2 to 6 for Interactive traffic class, traffic handling priority 3.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.
The value of qos_mtbr_i3_dl must be less than or equal to
the value of qos_mtbr_i2_dl for the same cell.

Syntax

Change command strings

chg_element qos_mtbr_i3_dl <location> <cell_desc>

chg_cell_element qos_mtbr_i3_dl <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element qos_mtbr_i3_dl <location> <cell_desc>

Values

Value type Integer

Valid range 2 to 6
Default value 2

6-744 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference qos_mtbr_i3_ul

qos_mtbr_i3_ul

Description

The qos_mtbr_i3_ul parameter specifies the uplink Minimum Throughput Budget Requirement
(in kbit/s) ranges from 2 to 6 for Interactive traffic class, traffic handling priority 3.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.
The value of qos_mtbr_i3_ul must be less than or equal to
the value of qos_mtbr_i2_ul for the same cell.

Syntax

Change command strings

chg_element qos_mtbr_i3_ul <location> <cell_desc>

chg_cell_element qos_mtbr_i3_ul <location> <cell_desc_opt>

Display command strings

disp_cell qos_mtbr_i3_ul <cell_id> <full>

disp_element qos_mtbr_i3_ul <location> <cell_desc>

Values

Value type Integer

Valid range 2 to 6
Default value 2

68P02901W23-T 6-745
Jan 2010
qsearch_c Chapter 6: CM database parameters

qsearch_c

Description

The qsearch_c is like qsearch_i in idle mode. It defines a threshold and also indicates whether
the MS shall measure a 3G neighbor cell or not when RXLEV of the serving GSM cell is below
or above this threshold. The qsearch_c parameter is sent to a mobile in the Measurement
Information message.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Enhanced 2G/3G Handover feature must be
unrestricted.

Syntax

Change command strings

chg_element qsearch_c <value> <location> <cell_desc>

chg_cell_element qsearch_c <value> <cell_desc_opt>

copy_cell qsearch_c

Display command strings

disp_cell <cell_id> [full]

disp_element qsearch_c <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 15
Default value 15

6-746 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference qsearch_c_initial

qsearch_c_initial

Description

The qsearch_c_initial parameter is broadcast on the BCCH using the SYSTEM INFORMATION
TYPE 2 quarter message to control the multi-RAT MS behavior in circuit switched dedicated
mode.

The parameter specifies whether qsearch_i is used by the MS in dedicated mode after a
certain number of Measurement Information messages are received, or whether the MS should
always search.

The qsearch_c_initial parameter is configurable on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes

Cell description required Yes
Dependencies The BSS Inter-RAT feature or TD-SCDMA and GSM
interworking feature must be unrestricted.

Syntax

Change command strings

chg_element qsearch_c_initial <value> <location> <cell_desc>

chg_cell_element qsearch_c_initial <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element qsearch_c_initial <location> <cell_desc>

68P02901W23-T 6-747
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 The MS uses qsearch_i until qsearch_c is reached.

1 The MS always searches irrespective of qsearch_i (MS

always measures the strength of the neighbor cells)
Default value 0

6-748 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference qsearch_i

qsearch_i

Description

The multi-RAT MS uses the qsearch_i parameter to decide when to start measurement of a
UTRAN neighbor cell.

Measurement of a UTRAN neighbor cell starts when the received RF signal level of the serving
GSM cell BCCH carrier is above or below the threshold defined by qsearch_i.

The qsearch_i parameter is configurable on a per cell basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The BSS Inter-RAT feature or TD-SCDMA and GSM
interworking feature must be unrestricted.

Syntax

Change command strings

chg_element qsearch_i <value> <location> <cell_desc>

chg_cell_element qsearch_i <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element qsearch_i <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 15 Search for 3G cells
if signal level is
below (0 7) or above (8 15) threshold
0 = - 98 dBm
1 = - 94 dBm
...
Continued

68P02901W23-T 6-749
Jan 2010
Values Chapter 6: CM database parameters

...
6 = - 74 dBm
7 = (always)
8 = - 78 dBm
9 = - 74 dBm

...
...
14 = - 54 dBm
15 = (never)
Default value 15

6-750 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference qsearch_p

qsearch_p

Description

The qsearch_p parameter specifies the threshold below which a multi-RAT MS searches for 3G
cells.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Add/Change command strings

chg_element qsearch_p <value> <location> <cell_desc>

chg_cell_element qsearch_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element qsearch_p <location> <cell_desc>

Values

Value type Integer (1 step = 4 dBm)

Valid range 0 to 7 For signal strengths below the threshold see Table 6-35
8 to 15 For signal strengths above the threshold see Table 6-36
Default value 0

68P02901W23-T 6-751
Jan 2010
Values Chapter 6: CM database parameters

Table 6-35 qsearch_p attribute values below threshold

Value Range
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)

Table 6-36 qsearch_p attribute values above threshold

Value Range
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)

6-752 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference queue_management_information

queue_management_information

Description

The queue_management_information parameter specifies the maximum number of MSs that

may wait in a queue for channel assignment. A value of 0 indicates that queuing is not allowed.

Type A (no operation action)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The sum of (max_q_length_channel +
max_q_length_sdcch) must be less than or equal to
queue_management_information.

Syntax

Change command strings

chg_element queue_management_information <value> <location> <cell_desc>

chg_cell_element queue_management_information <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element queue_management_information <location> <cell_desc>

Values

Value type Integer (representing the maximum number of MSs)

Valid range 0 to 50
Default value 50

References

Internal name EN_Q_ALLOWED

This is a Motorola parameter.

68P02901W23-T 6-753
Jan 2010
ra_color Chapter 6: CM database parameters

ra_color

Description

The ra_color parameter specifies the routing area color used in System Information messages
for a specific cell and, therefore, indicates that GPRS is supported in the cell.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted. The ra_color
parameter applies only to GPRS cells.
If the local_maintenance flag is disabled, this parameter
cannot be changed through the MMI.
Operator actions This parameter cannot be displayed until its value has been
set. Once the value of ra_color has been set, it cannot be
unset.

NOTE
BSS software processes using this parameter are not notified when the change is
made. That is, this parameter can be modified without a reset to a particular device
or function.

Syntax

Change command strings

chg_element ra_color <value> <location> <cell_desc>

chg_cell_element ra_color <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element ra_color <location> <cell_desc>

6-754 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (routing area color for a cell)

Valid range 0 to 7
Default value None

68P02901W23-T 6-755
Jan 2010
ra_reselect_hysteresis Chapter 6: CM database parameters

ra_reselect_hysteresis

Description

The ra_reselect_hysteresis parameter specifies the additional hysteresis that applies when
selecting a cell in a new Routing Area (RA).

Differences in received signal levels from 0 dB to 14 dB (in 2 dB increments) are used for
cell reselection.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH optional feature must be unrestricted.

Syntax

Add/Change command strings

chg_element ra_reselect_hysteresis <value> <location> <cell_desc>

chg_cell_element ra_reselect_hysteresis <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element ra_reselect_hysteresis <location> <cell_desc>

6-756 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 7 Represents the signal level differences:
0 0 dB
1 2 dB
2 4 dB
3 6 dB
4 8 dB
5 10 dB
6 12 dB
7 14 dB
Default value None

68P02901W23-T 6-757
Jan 2010
rac Chapter 6: CM database parameters

rac

Description

The rac parameter specifies the routing area code (RAC) which is part of the cell identifier
for GPRS cells.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter applies only to GPRS cells.
The GPRS feature must be unrestricted.
Operator actions This parameter cannot be displayed until value has been
set. Once this value has been set, it cannot be unset.

NOTE
BSS software processes using this parameter are not notified when the change is
made. That is, this parameter can be modified without a reset to a particular device
or function.

Syntax

Change command strings

chg_element rac <value> <location> <cell_desc>

chg_cell_element rac <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rac <location> <cell_desc>

NOTE
The RAC cannot be displayed if the operator has not previously configured or
modified the value .

6-758 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (RAC for a cell)

Valid range 0 to 255 Null = unmodified
Default value None

68P02901W23-T 6-759
Jan 2010
rach_load_period Chapter 6: CM database parameters

rach_load_period

Description

The rach_load_period parameter indicates how often to check for the RACH overload condition
when the cell is not in RACH overload.

NOTE
Other parameters can affect flow control. Refer to ccch_load_period,
rach_overload_threshold, ssm_normal_overload_threshold, ssm_normal_over-
load_threshold or tch_flow_control.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter must be less than or equal to
ccch_load_period.

Syntax

Change command strings

chg_element rach_load_period <value> <location> <cell_desc>

chg_cell_element rach_load_period <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rach_load_period <location> <cell_desc>

6-760 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 1 to 1020
Default value 16

References

Internal name RACH_MEAS_PERIOD

This is a Motorola parameter.

68P02901W23-T 6-761
Jan 2010
rach_load_threshold Chapter 6: CM database parameters

rach_load_threshold

Description

The rach_load_threshold parameter specifies the threshold for RACH load. If the calculated
RACH load exceeds this threshold, an overload condition is signaled and an access class is
barred at the cell where the overload is occurring.

If the RACH load exceeds rach_load_threshold, an overload indication is sent to Call

Processing which may result in an access class being barred. The RACH load may be calculated
in one of two ways based on the value of the rach_load_type parameter.

RACH loading is expressed as the ratio of correct RACH accesses to the number of possible
RACH accesses. Let T_SD_CHANNEL be the number of available traffic and standalone control
(SDCCH) channels. The cell configuration determines this number. Let MAX_RACH be the
number of possible RACH accesses per load period. MAX_RACH has a value of 204 for pure
RACH (non-combined), and 108 for combined RACH channels. The number of correct RACH
accesses can exceed the number of calls the cell can handle (T_SD_CHANNELS). In the case
the RACH load threshold is set to a number higher than T_SD_CHANNELS/MAX_RACH, MSs
are not barred until the RACH load threshold is met, but in the mean time attempted calls get
rejected, once the cell runs out of available traffic channels. If the RACH load threshold is set to
a value in the neighborhood of T_SD_CHANNELS/MAX_RACH, the system gradually prevents
subscribers from entering the system as soon as the cell runs out of free traffic and standalone
control channels. In both cases, the net effect is that calls are not completed.

Table 6-37 lists example cell configurations and their corresponding rach_load_threshold
values.

Table 6-37 Example cell configurations for rach_load_threshold

Conf Carriers SDCCH TCH CCCH Combined T_SDM_R

A 3 16 21 1 No 18.1%
B 1 4 7 1 Yes 10.18%
C 3 16 20 2 No 08.8%

NOTE
Other parameters can affect flow control. Refer to ccch_load_period, rach_load_pe-
riod, ssm_normal_overload_threshold, ssm_normal_overload_threshold or
tch_flow_control.

6-762 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Syntax

Type A (no operator actions)

Supported by OMC-R GUI
Cell description required
Dependencies
Yes
Yes
If rach_load_type is 1, then the units for this parameter
are (# correct RACH access/# incorrect RACH accesses).
If rach_load_type is 0, then the units for this parameter
are (# correct RACH access/# possible RACH accesses).

Syntax

Change command strings

chg_element rach_load_threshold <value> <location> <cell_desc>

chg_cell_element rach_load_threshold <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rach_load_threshold <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 1000
Default value 1000 (Disables flow control)

References

Internal name RACH_BUSY_THRES

This is a Motorola parameter.

68P02901W23-T 6-763
Jan 2010
rach_load_type Chapter 6: CM database parameters

rach_load_type

Description

The rach_load_type parameter specifies the RACH loading calculation method.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element rach_load_type <value> <location>

Display command string

disp_element rach_load_type <location>

Values

Value type Boolean

Valid range 0 or 1
0 Percentage of RACH opportunities used
1 Percentage of total RACHs which are incorrect (collisions)
Default value None

6-764 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference radio_link_timeout

radio_link_timeout

Description

The radio_link_timeout parameter specifies the threshold (limit) for the radio downlink failure
on the Slow Associated Control Channel (SACCH). The channel should only be held for as long
as an operator could reasonably be expected to hold while experiencing loss of audio.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <cell_desc> <location>

chg_element radio_link_timeout <value> <location> <cell_desc>

chg_cell_element radio_link_timeout <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element radio_link_timeout <location> <cell_desc>

68P02901W23-T 6-765
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (1 step = 4 SACCH frames)

Valid range 0 to 15
Represents the number of SACCH frames as shown below:
0 4 SACCH frames
1 8 SACCH frames
2 12 SACCH frames
... ...
... ...
... ...
15 64 SACCH frames

Default value 4

References

GSM parameter RADIO_LINK_TIMEOUT(MS)

GSM specification 3.5.2 to 3.5.2.2: radio link failure, mobile side and network
side
4.08 - 10.5.2.3 - fig. 10.22, table 10.16

6-766 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rapid_pwr_down

rapid_pwr_down

Description

The rapid_pwr_down parameter enables or disables the rapid power down procedure. The
rapid power down procedure bypasses the pow_red_step_size values set in the database in an
effort to bring the power of the MS to an acceptable level quickly.

Detected MS power levels are averaged over the number of SACCH periods specified by the
rpd_period parameter. This average is compared to the value specified for the rpd_trigger
value. The rapid power down procedure is initiated when the calculated value is greater than
the value specified for the rpd_trigger parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <cell_desc> <location>

chg_element rapid_pwr_down <value> <location> <cell_desc>

chg_cell_element rapid_pwr_down <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element rapid_pwr_down <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-767
Jan 2010
rci_error_clr_thresh Chapter 6: CM database parameters

rci_error_clr_thresh

Description

The rci_error_clr_thresh parameter specifies the error count threshold (equal to or less than)
for an alarm to be cleared for a Radio Channel Identifier (RCI).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies Two successful calls are required on a resource before an
alarm can be cleared within this threshold. One successful
call may be too short for the Channel Coder Unit (CCU)
to send an error indication, thus clearing the alarm
prematurely.
This parameter can be set only at a BSC.
If the threshold is increased during operation, any existing
counts between the new and the old threshold does not
clear an alarm until another successful call is made or the
next successful time period occurs on the CIC.
(rci_error_gen_thresh - rci_error_clr_thresh) must be
greater than or equal to 2.

Syntax

Change command string

chg_element rci_error_clr_thresh <value> 0

Display command string

disp_element rci_error_clr_thresh 0

Values

Value type Integer

Valid range 0 to 253
Default value 0

6-768 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rci_error_gen_thresh

rci_error_gen_thresh

Description

The rci_error_gen_thresh parameter specifies the error count threshold (equal to or greater
than) for an alarm to be generated for a Radio Channel Identifier (RCI).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be set only at a BSC.
If the threshold is changed during operation, no immediate
alarm occurs. The new threshold takes effect only when
the RCI error count changes.
(rci_error_gen_thresh - rci_error_clr_thresh) must be
greater than or equal to 2.

Syntax

Change command string

chg_element rci_error_gen_thresh <value> 0

Display command string

disp_element rci_error_gen_thresh 0

Values

Value type Integer

Valid range 2 to 255
Default value 6

NOTE
The BSS system is designed to accept values less than 6 for the rci_error_gen_thresh
parameter for debug purposes only. It is not recommended to set thresholds lower
than 6 during the normal operation.

68P02901W23-T 6-769
Jan 2010
rci_error_inc Chapter 6: CM database parameters

rci_error_inc

Description

The rci_error_inc parameter specifies the error count increment when the Enhanced Circuit
Error Rate Monitor (ECERM) feature is in use for Radio Channel Identifiers (RCIs) on a per
BSC basis.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The ECERM feature must be unrestricted.
This parameter applies only to the BSC.

Syntax

Change command string

chg_element rci_error_inc <value> 0

Display command string

disp_element rci_error_inc 0

Values

Value type Integer

Valid range 0 RCI alarms not raised
1 to 255 RCI alarms raised
Default value 0 If ECERM feature is restricted
1 If ECERM feature is not restricted

6-770 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference reconfig_fr_to_amr_hr

reconfig_fr_to_amr_hr

{34452}

Description

The reconfig_fr_to_amr_hr parameter indicates that if the congestion levels in the target cell
exceed the threshold, then any existing Half Rate Capable Full-Rate calls with AMR as the first
permitted HR speech version are reassigned to half-rate traffic channels. A prerequisite is that
there should be idle half-rate channels and free generic traffic channels in the cell.

Type A (no operator actions required)

Supported by OMC-R GUI Yes

Cell description required Yes
Dependencies
This parameter can only be modified if the AMR
feature is unrestricted. Also, the value of the
reconfig_fr_to_amr_hr parameter must be less than
or equal to the reconfig_fr_to_hr parameter unless
the threshold is disabled.

This element can be modified inside and outside

SYSGEN mode. When AMR HR is not enabled at the
BSS level or at the cell level, the BSS SW ignores
the threshold.

Syntax

Change command string

chg_cell_element reconfig_fr_to_amr_hr <value> <cell_desc>

chg_element reconfig_fr_to_amr_hr <value> <location> <cell_desc>

Display command string

disp_element reconfig_fr_to_amr_hr <location> <cell_desc>

68P02901W23-T 6-771
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 101
0 Minimum
101 Maximum
Setting the value to 101 disables the congestion
mechanism.
Default value 101

6-772 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference reconfig_fr_to_hr

reconfig_fr_to_hr

Description

The reconfig_fr_to_hr parameter specifies the congestion level threshold. If this level is
exceeded at the serving cell, then any existing half-rate capable Full-Rate calls are reassigned
to Half-Rate traffic channels. Idle half-rate channels and free generic traffic channels in the
cell must be available.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or GSM Half Rate feature must be
unrestricted.

Syntax

Add/Change command strings

chg_element reconfig_fr_to_hr <value> <location> <cell_desc>

chg_cell_element reconfig_fr_to_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element reconfig_fr_to_hr <location> <cell_desc>

Values

Value type Percentage

Valid range 0 to 101
101 Disables this parameter
Default value 101

68P02901W23-T 6-773
Jan 2010
red_loss_daily Chapter 6: CM database parameters

red_loss_daily

Description

The red_loss_daily parameter specifies the synchronization loss, daily alarm level count on
a T1 link. An alarm generates if the synchronization loss meets or exceeds the threshold in a
given 24 hour period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element red_loss_daily <value> <location>

Display command string

disp_element red_loss_daily <location>

Values

Value type Integer (number of alarms)

Valid range 0 to 65535
Default value 16

6-774 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference red_loss_oos

red_loss_oos

Description

The red_loss_oos parameter specifies the synchronization loss, Out Of Service (OOS) daily
alarm level count for a T1 circuit. The T1 circuit is to be taken OOS if the synchronization loss
meets or exceeds this threshold during a given red_time_loss period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element red_loss_oos <value> <location>

Display command string

disp_element red_loss_oos <location>

Values

Value type Integer (number of alarms)

Valid range 0 to 65535
Default value 511

68P02901W23-T 6-775
Jan 2010
red_loss_hourly Chapter 6: CM database parameters

red_loss_hourly

Description

The red_loss_hourly parameter specifies the synchronization loss, hourly alarm level count
on a T1 link. An alarm generates if the synchronization loss meets or exceeds the threshold in
a given 60 minute period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element red_loss_hourly <value> <location>

Display command string

disp_element red_loss_hourly <location>

Values

Value type Integer (number of alarms)

Valid range 0 to 65535
Default value 20

6-776 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference red_time_oos

red_time_oos

Description

The red_time_oos parameter specifies the synchronization loss time for a T1 circuit. If
synchronization is lost for this period of time, the T1 circuit is taken Out Of Service (OOS).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element red_time_oos <value> <location>

Display command string

disp_element red_time_oos <location>

Values

Valid type Integer (1 step = 100 milliseconds)

Valid range 0 to 65535
0 0 seconds 0 milliseconds
1 0.1 seconds 100 milliseconds
2 0.2 seconds 200 milliseconds
... ...
25 2.5 seconds 2500 milliseconds
... ...
65535 6553.5 seconds 6553500 milliseconds
Default value 25

68P02901W23-T 6-777
Jan 2010
red_loss_restore Chapter 6: CM database parameters

red_loss_restore

Description

The red_loss_restore parameter specifies the synchronization loss, restorable time limit for
a T1 circuit. If a synchronization loss error does not occur within this period of time, the T1
circuit is brought back in service. The synchronization loss is controlled by the value assigned
to the red_loss_oos parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element red_loss_restore <value> <location>

Display command string

disp_element red_loss_restore <location>

Values

Valid type Integer (1 step = 100 milliseconds)

Valid range 0 to 65535
0 0 seconds 0 milliseconds
1 0.1 seconds 100 milliseconds
2 0.2 seconds 200 milliseconds
... ...
6000 600 seconds 600000 milliseconds
... ...
65535 6553.5 seconds 6553500 milliseconds
Default value 600

6-778 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference reestablish_allowed

reestablish_allowed

Description

The reestablish_allowed parameter enables or disables call establishment.

If a BTS detects that an MS has not sent up any measurement reports for n number of SACCH
periods (where n is defined by the parameter radio_link_timeout), a radio link failure occurs.

When enabled, the MS executes the GSM call re-establishment algorithm to determine which
cell to use for the attempt to re-establish the call.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <cell_desc> <location>

chg_element reestablish_allowed <value> <location> <cell_desc>

chg_cell_element reestablish_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element reestablish_allowed <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Enabled
1 Disabled
Default value 0

68P02901W23-T 6-779
Jan 2010
References Chapter 6: CM database parameters

References

GSM parameter RE
GSM specification 5.08 - 6.7.2: Call re-establishment algorithm.
408 - 3.5.2 to 3.5.2.2: radio link failure, mobile side and
network side.
4.08 - 10.5.2.17, fig. 10.36, and 12.20 - 5.2.8.7, table
10.30: cell description - call reestablishment allowed

6-780 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rel_tim_adv

rel_tim_adv

Description

The rel_tim_adv parameter is the relative timing advance value used in HDPC averaging
processing.

A bin_num must be specified with this command to indicate the location of the parameters to
be modified. Only 0 or 1 may be specified for the bin_num.

A alg_num must be also specified to indicate the averaging algorithm as unweighted (0). If a
value of 255 is entered for the alg_num, the bin is considered to contain invalid data.

After entering the chg_cell_element command for this parameter, the following prompts
are displayed and values must be entered:

Enter hreqave:
Enter hreqt:

When entering disp_element rel_tim_adv, a bin_num must be specified to identify the

location of the parameters to be displayed.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies When alg_num is set to 255, bin_num cannot be set equal
to decision_1_tim_adv_av_alg
Operator actions Respond to the prompts after entering this command.

Syntax

Change command string

chg_cell_element rel_tim_adv, <bin_num> <alg_num> <cell_desc_opt>

Display command string

disp_cell <cell_id> <full>

disp_element rel_tim_adv,<bin_num> <location> <cell_desc>

68P02901W23-T 6-781
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range alg_num value depends on different attributes:
Attribute Permissible Default value
range
Hreqave 1 to 32 4
Hreqt 1 to 32 1

References

GSM specification 5.08

This is a Motorola defined parameter.

6-782 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference remote_ip

remote_ip

{26638}

Description

The remote_ip parameter is an IP based NSVC parameter and identifies the valid value of
the remote ip.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the Gb over IP
feature is unrestricted and the Gb mode is set to static IP
mode.

Syntax

Add command strings

add_nsvc <location> <NS_VCI> <GBL_ID> if gb_mode is in the static IP mode.

add_nsvc <location> <NS_VCI> <GBL_ID> <DLCI> if gb_mode is in the frame relay mode.

Modify command strings

mod_nsvc <location> <NS_VCI>

Display command strings

disp_nsvc <NS_VCI> <nsvci_value>

disp_nsvc <location> <GBL> <gbl_value>

Delete command strings

del_nsvc <location> <nsvci_value>

68P02901W23-T 6-783
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0.0.0.0 to 223.255.255.255
127.x.x.x Exception
128.0.0.0 to Minimum
223.255.255.255
0 to 126.255.255.255 Maximum
Default value N/A

6-784 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference remote_loss_daily

remote_loss_daily

Description

The remote_loss_daily parameter specifies the threshold for the daily count of remote alarms.

An alarm generates if this threshold is met or exceeded during a 24 hour period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies remote_loss_daily should be always less than
remote_loss_hourly.

Syntax

Change command string

chg_element remote_loss_daily <value> <location>

Display command string

disp_element remote_loss_daily <location>

Values

Value type Integer (represents the number of alarms)

Valid range 0 to 65535
Default value 16

68P02901W23-T 6-785
Jan 2010
remote_loss_hourly Chapter 6: CM database parameters

remote_loss_hourly

Description

The remote_loss_hourly parameter specifies the threshold for the hourly count of remote
alarms.

An alarm generates if this threshold is met or exceeded during a 60 minute period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies remote_loss_daily should be always less than
remote_loss_hourly.

Syntax

Change command string

chg_element remote_loss_hourly <value> <location>

Display command string

disp_element remote_loss_hourly <location>

Values

Value type Integer (represents the number of alarms)

Valid range 0 to 65535
Default value 20

6-786 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference remote_loss_oos

remote_loss_oos

Description

The remote_loss_oos parameter specifies the Out Of Service (OOS) threshold for the remote
alarm.

When this threshold is met or exceeded, the 2 Mbit/s circuit is taken OOS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element remote_loss_oos <value> <location>

Display command string

disp_element remote_loss_oos <location>

Values

Value type Integer (represents the number of alarms)

Valid range 0 to 65535
Default value 511

68P02901W23-T 6-787
Jan 2010
remote_loss_restore Chapter 6: CM database parameters

remote_loss_restore

Description

The remote_loss_restore parameter specifies the wait time for restoring the 2 Mbit/s circuit
to service.

If no remote alarm indication errors are detected during this wait time, the 2 Mbit/s circuit
returns to service.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element remote_loss_restore <value> <location>

Display command string

disp_element remote_loss_restore <location>

Values

Valid type Integer (1 step = 100 milliseconds)

Valid range 0 to 65535
0 0 seconds 0 milliseconds
1 0.1 seconds 100 milliseconds
2 0.2 seconds 200 milliseconds
... ...
600 60 seconds 60000 milliseconds
... ...
65535 6553.5 seconds 6553500 milliseconds
Default value 600

6-788 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference remote_time_oos

remote_time_oos

Description

The remote_time_oos parameter specifies the remote alarm time period. If a remote alarm
exists for this amount of time, the 2 Mbit/s circuit is taken Out Of Service (OOS).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element remote_time_oos <value> <location>

Display command string

disp_element remote_time_oos <location>

Values

Valid type Integer (1 step = 100 milliseconds)

Valid range 0 to 65535
0 0 seconds 0 milliseconds
1 0.1 seconds 100 milliseconds
2 0.2 seconds 200 milliseconds
... ...
25 2.5 seconds 2500 milliseconds
... ...
65535 6553.5 seconds 6553500 milliseconds
Default value 25

68P02901W23-T 6-789
Jan 2010
red_time_restore Chapter 6: CM database parameters

red_time_restore

Description

The red_time_restore parameter specifies the synchronization loss restart time for a T1 link. If
synchronization loss does not occur within this period of time, the T1 link returns to service.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element red_time_restore <value> <location>

Display command string

disp_element red_time_restore <location>

Values

Valid type Integer (1 step = 100 milliseconds)

Valid range 0 to 65535
0 0 seconds 0 milliseconds
1 0.1 seconds 100 milliseconds
2 0.2 seconds 200 milliseconds
... ...
600 60 seconds 60000 milliseconds
... ...
65535 6553.5 seconds 6553500 milliseconds
Default value 600

6-790 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference report_resource_tch_f_high_water_mark

report_resource_tch_f_high_water_mark

Description

The report_resource_tch_f_high_water_mark parameter specifies the high need threshold of

a full rate traffic channel (TCH) for the resource indication procedure. When the number of
available (idle) full rate TCHs falls below this threshold, the internal resource indication timer
starts and the resource indication message is sent to the MSC. That is, the Resource Request
message received from the MSC is indicating a spontaneous mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Must be less than
report_resource_tch_f_low_water_mark

Syntax

Add/Change command strings

add_cell <cell_desc> <location>

chg_element report_resource_tch_f_high_water_mark <value> <location> <cell_desc>

chg_cell_element report_resource_tch_f_high_water_mark <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element report_resource_tch_f_high_water_mark <location> <cell_desc>

Values

Value type Integer (represents the number of TCHs)

Valid range 0 to 254
Default value 2

68P02901W23-T 6-791
Jan 2010
References Chapter 6: CM database parameters

References

GSM specification 8.08 - 3.2.2.4: reported message format

This is a Motorola parameter.

6-792 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference report_resource_tch_f_low_water_mark

report_resource_tch_f_low_water_mark

Description

The report_resource_tch_f_low_water_mark parameter specifies the low need threshold

of a full rate traffic channel (TCH) for the resource indication procedure. When the number
of available (idle) full rate TCHs rises above this threshold, the internal resource indication
timer stops (if it is running). That is, the Resource Request message received from the MSC
is indicating a spontaneous mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Must be greater than
report_resource_tch_f_high_water_mark

Syntax

Add/Change command strings

add_cell <cell_desc> <location>

chg_element report_resource_tch_f_low_water_mark <value> <location> <cell_desc>

chg_cell_element report_resource_tch_f_low_water_mark <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element report_resource_tch_f_low_water_mark <location> <cell_desc>

Values

Value type Integer (number of TCHs)

Valid range 1 to 255
Default value 12

68P02901W23-T 6-793
Jan 2010
References Chapter 6: CM database parameters

References

GSM specification 8.08 - 3.2.2.4: reported message format

This is a Motorola parameter.

6-794 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference res_gprs_pdchs

res_gprs_pdchs

Description

The res_gprs_pdchs parameter specifies the number of PDCH timeslots reserved in a cell.

NOTE
The equip RTF parameter with the same name is now obsolete.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.
The value of the res_gprs_pdchs parameter cannot be
higher than the total number of timeslots available in the
cell.
The sum of the res_gprs_pdchs and switch_gprs_pdchs
parameters must be greater than or equal to 0 and less
than or equal to 30, and cannot be higher than the total
number of timeslots in the cell.
The primary PCU must be specified.

NOTE
When an attempt is made to change res_gprs_pdchs, and the requested PDTCHs
exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues
a warning to indicate that there is not enough GDS or PMC resource available.

Syntax

Change command strings

chg_element res_gprs_pdchs <value> <location> <cell_desc>

chg_cell_element res_gprs_pdchs <value> <cell_desc_opt>

68P02901W23-T 6-795
Jan 2010
Values Chapter 6: CM database parameters

Display command strings

disp_cell <cell_id> <full>

disp_element res_gprs_pdchs <location> <cell_desc>

Values

Value type Integer (represents the number of PDCHs)

Valid range 0 to 30
Default value 0

6-796 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference res_ts_less_one_carrier

res_ts_less_one_carrier

Description

The res_ts_less_one_carrier parameter specifies the maximum number of timeslots that the
BSS can allocate as reserved Packet Data Channels (PDCHs) in a cell when one of the GPRS
carriers in the cell goes Out Of Service.

The value of (res_gprs_pdchs minus res_ts_less_one_carrier) is subtracted from

res_ts_less_one_carrier for each additional carrier that is lost.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.
RTFs must be equipped in the database.
The BSS verifies whether there are enough carriers
equipped in the database to support the value set by this
parameter and the sw_ts_less_one_carrier parameter, and
that the combined total does not exceed 30.
The primary PCU must be specified.

NOTE

BSS software processes using this parameter are notified immediately after the
change is made.
When an attempt is made to change res_ts_less_one_carrier, and the requested
PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the
request and issues a warning to indicate that there is not enough GDS or PMC
resource available.

Syntax

Change command strings

chg_element res_ts_less_one_carrier <value> <location> <cell_desc>

chg_cell_element res_ts_less_one_carrier <value> <cell_desc_opt>

68P02901W23-T 6-797
Jan 2010
Values Chapter 6: CM database parameters

Display command strings

disp_cell <cell_id> <full>

disp_element res_ts_less_one_carrier <location> <cell_desc>

Values

Value type Integer (timeslots)

Valid range 0 to 30
Default value Until set, assumes the value of res_gprs_pdchs

6-798 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rf_res_ind_period

rf_res_ind_period

Description

The rf_res_ind_period parameter specifies the RF resource indication period. During this
period, the idle channel is categorized. The idle channel categories are reported to the CRM by
the RSS. The idle channel categories are: X1, X2, X3, X4, and X5.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element rf_res_ind_period <value> <location>

Display command string

disp_element rf_res_ind_period <location>

Values

Value type Integer (1 Step = 1 SACCH multiframe)

Valid range 1 to 127
Default value 10

References

Internal name RF_RES_IND_PERIOD

This is a Motorola parameter.

68P02901W23-T 6-799
Jan 2010
rpd_offset Chapter 6: CM database parameters

rpd_offset

Description

The rpd_offset parameter specifies the offset value used when calculating the receive uplink
level for an MS when the rapid power down procedure initiates.

The receive uplink level is equal to rpd_trigger minus rpd_offset.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter must be less than rpd_trigger. The
parameter rapid_pwr_down must be
enabled.

Syntax

Add/Change command strings

add_cell <cell_desc> <location>

chg_element rpd_offset <value> <location> <cell_desc>

chg_cell_element rpd_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element rpd_offset <location> <cell_desc>

Values

Value type Integer (1 dBm)

Valid range 0 to 63
Default value 8

6-800 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rpd_period

rpd_period

Description

The rpd_period parameter specifies the number of SACCH frames used to calculate a rolling
average of uplink rxlev values.

Detected MS power levels are averaged over the number of SACCH periods specified by the
rpd_period parameter. This average is compared to the value specified for the rpd_trigger
value. The rapid power down procedure initiates when the calculated value is greater than the
value specified for the rpd_trigger parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The parameter rapid_pwr_down must be enabled.

Syntax

Add/Change command strings

add_cell <cell_desc> <location>

chg_element rpd_period <value> <location> <cell_desc>

chg_cell_element rpd_period <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element rpd_period <location> <cell_desc>

Values

Value type Integer (SACCH periods)

Valid range 1 to 32
Default value 2

68P02901W23-T 6-801
Jan 2010
rpd_trigger Chapter 6: CM database parameters

rpd_trigger

Description

The rpd_trigger parameter specifies the threshold used to initiate the rapid power down
procedure.

Detected MS power levels are averaged over the number of SACCH periods specified by the
rpd_period parameter. This average is compared to the value specified for the rpd_trigger
value. The rapid power down procedure initiates when the calculated value is greater than the
value specified for the rpd_trigger parameter.

The receive uplink power level is equal to rpd_trigger minus rpd_offset.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter must be greater than l_rxlev_ul_p.
This parameter must be greater than rpd_offset.
The parameter rapid_pwr_down must be enabled.

Syntax

Add/Change command strings

add_cell <cell_desc> <location>

chg_element rpd_trigger <value> <location> <cell_desc>

chg_cell_element rpd_trigger <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element rpd_trigger <location> <cell_desc>

6-802 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 63
Each step represents an increase of 1 dBm, from -110 dBm to -47 dBm,
as shown below:
0 -110 dBm and lower
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm and higher
Default value 45 (- 65 dBm)

68P02901W23-T 6-803
Jan 2010
rpt_bad_qual_no_mr Chapter 6: CM database parameters

rpt_bad_qual_no_mr

Description

The rpt_bad_qual_no_mr parameter specifies how to signify the RXQUAL measurement when
the rxqual measurement report is lost in the measurement report from the BSS.

When rpt_bad_qual_no_mr is set to 0, the missed RXQUAL measurement report is left blank
and it is not used to signify the RXQUAL measurement.

When rpt_bad_qual_no_mr is set to 1, the worst quality value, RXQUAL 7, is used to signify the
RXQUAL measurement if the rxqual measurement is lost in the measurement report from the
BSS.

When rpt_bad_qual_no_mr is set to 2, the previous value of RXQUAL is used to signify the
RXQUAL measurement if the rxqual measurement is lost in the measurement report from the
BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element rpt_bad_qual_no_mr <value> <location> <cell_desc>

chg_cell_element rpt_bad_qual_no_mr <value> <cell_desc_opt>

Display command strings

disp_cell <desc_id> <full>

disp_element rpt_bad_qual_no_mr <location> <cell_desc>

6-804 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 2
0 The missed RXQUAL measurement report is left blank and
it is not used to signify the RXQUAL measurement.
1 The worst quality value, RXQUAL 7, is used to signify the
RXQUAL measurement if the rxqual measurement is lost in
the measurement report from the BSS.
2 The previous value of RXQUAL is used to signify the
RXQUAL measurement if the rxqual measurement is lost in
the measurement report from the BSS
Default value 0

68P02901W23-T 6-805
Jan 2010
rsl_lcf_congestion_thi Chapter 6: CM database parameters

rsl_lcf_congestion_thi

Description

The rsl_lcf_congestion_thi parameter specifies the RSL Congestion Control (RCC) high
congestion threshold at which an RSL-LCF board is in congestion status, so that MTL-LCF can
stop sending paging message to the board.

The RCC high congestion threshold represents a percentage of the total number of RSLs that
the RSL-LCF board services. The board is in congestion status when it detects the percentage
number of congested RSLs is more than or equal to the high congestion threshold value.

The system responds with an error message and rejects the value of rsl_lcf_congestion_thi
if set to a value which is less than the current value of rsl_lcf_congestion_tlow parameter
(see rsl_lcf_congestion_tlow on page 6-807).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The rsl_lcf_congestion_thi parameter must be greater
than rsl_lcf_congestion_tlow parameter.

Syntax

Add/Change command strings

chg_element rsl_lcf_congestion_thi <value> bsc

Display command strings

disp_element rsl_lcf_congestion_thi bsc

Values

Value type Integer (in steps of 1%)

Valid range
1 to 100
Default value 60

6-806 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rsl_lcf_congestion_tlow

rsl_lcf_congestion_tlow

Description

The rsl_lcf_congestion_tlow parameter specifies the RSL Congestion Control (RCC) low
congestion threshold at which an RSL-LCF board is out of congestion status, so that MTL-LCF
can resume sending paging message to the board.

The RCC low congestion threshold represents a percentage of the total number of RSLs that the
RSL-LCF board services. The board is out of congestion status when it detects the percentage
number of congested RSLs is less than or equal to the low congestion threshold value.

The system responds with an error message and rejects any value of rsl_lcf_congestion_tlow
parameter if set to a value which is equal to or greater than the current value of
rsl_lcf_congestion_thi parameter (see rsl_lcf_congestion_thi on page 6-806).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The rsl_lcf_congestion_tlow parameter must be less than
rsl_lcf_congestion_thi parameter.

Syntax

Add/Change command strings

chg_element rsl_lcf_congestion_tlow <value> bsc

Display command strings

disp_element rsl_lcf_congestion_tlow bsc

Values

Value type Integer (in steps of 1%)

Valid range 0 to 99
Default value 25

68P02901W23-T 6-807
Jan 2010
rtf_path_enable Chapter 6: CM database parameters

rtf_path_enable

Description

The rtf_path_enable parameter enables or disables the RTF Fault Containment feature.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The RTF Fault Containment feature must be unrestricted.
This parameter can be used only at the BSC.
Operator actions Put the system into SYSGEN ON mode.

Syntax

Change command string

chg_element rtf_path_enable <value> 0

Display command string

disp_element rtf_path_enable 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-808 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rxlev_access_min

rxlev_access_min

Description

The rxlev_access_min parameter specifies the minimum received signal level (dBm) required
for an MS to access the system.

The range -110 dBm to -47 dBm is used to set the minimum received signal level which in turn
is used in path loss criterion parameter, C1. Set to a value corresponding to a signal level at
which a call can be maintained in a particular environment.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <cell_desc> <location>

chg_element rxlev_access_min <value> <location> <cell_desc>

chg_cell_element rxlev_access_min <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element rxlev_access_min <location> <cell_desc>

68P02901W23-T 6-809
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 63 Each step represents an increase of 1 dBm, from -110 dBm
to -47 dBm, as shown below:
0 -110 dBm and lower
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm and higher
Default value 0 (- 110 dBm)

References

GSM parameter RXLEV_ACCESS_MIN

GSM specification
4.08 - 10.5.2.4, fig. 10.23, table 10.17
5.08 - 6.2: conditions for MS camping on a cell
5.08 - 6.4: C1 equation
12.20 - 5.2.8.12 - radio Link Ctl DL - rx Lev Access Min
12.20 - 5.2.8.2

6-810 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rxlev_dl_ho

rxlev_dl_ho

Description

The rxlev_dl_ho parameter specifies the averaging algorithm data for making handover
decisions for the downlink receive signal level.

Specify a bin_num with this command to indicate the location of the parameters to be modified.

Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is
entered for the alg_num, the bin is considered to contain invalid data.

After entering the chg_cell_element command for this parameter, the following prompts
are displayed and values must be entered:

Enter hreqave:
Enter hreqt:

A bin_num is used with the disp_element rxlev_dl_ho command to identify the location
of the parameters to be displayed.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies When alg_num is set to 255, bin_num cannot
be set to equal one of the following parameters:
decision_1_dl_rxlev_av_h
decision_1_dl_rxlev_av_ih
decision_1_p_bgt_rxlev_av_h
Operator actions Respond to the prompts after entering this command.

Syntax

Change command string

chg_cell_element rxlev_dl_ho, <bin_num> <alg_num> <cell_desc_opt>

Display command strings

dis_cell <cell_desc> <full>

disp_element rxlev_dl_ho,<bin_num> <location> <cell_desc>

68P02901W23-T 6-811
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range alg_num value depends on different attributes:
Attribute Permissible Default value
range
Hreqave 1 to 32 4
Hreqt 1 to 32 1

References

GSM parameter A_LEV_HO, A_PBGT_HO

GSM specification 5.08

6-812 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rxlev_dl_pc

rxlev_dl_pc

Description

The rxlev_dl_pc parameter specifies the averaging parameters for making power control
decisions for the downlink receive signal level.

Specify a bin_num with this command to indicate the location of the parameters to be modified.

Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is
entered for the alg_num, the bin is considered to contain invalid data.

After entering the chg_cell_element command for this parameter, the following prompts
are displayed and values must be entered:

Enter hreqave:
Enter hreqt:

When entering disp_element rxlev_dl_pc, specify bin_num to identify the location of the
parameters to be displayed.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies When alg_num is set to 255, bin_num cannot be set equal
to decision_1_dl_rxlev_av_p.
Operator actions Respond to the prompts after entering this command.

Syntax

Change command string

chg_cell_element rxlev_dl_pc, <bin_num> <alg_num> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rxlev_dl_pc,<bin_num> <location> <cell_desc>

68P02901W23-T 6-813
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range alg_num value depends on different attributes:
Attribute Permissible Default value
range
Hreqave 1 to 32 4
Hreqt 1 to 32 1

References

GSM parameter A_LEV_PC

GSM specification 5.08

6-814 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rxlev_dl_zone

rxlev_dl_zone

Description

The rxlev_dl_zone parameter specifies the downlink receive level threshold that must be
crossed for a handover to take place between the outer zone and the inner zone.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Concentric Cells feature must be enabled and the
inner_zone_alg type must be set to 1.

Syntax

Change command strings

chg_element rxlev_dl_zone <value> <location> <cell_desc>

chg_cell_element rxlev_dl_zone <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rxlev_dl_zone <location> <cell_desc>

68P02901W23-T 6-815
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 63
Each step represents an increase of 1 dBm, from -110 dBm to -47 dBm,
as shown below:
0 -110 dBm and lower
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm and higher
Default value 63 (- 47 dBm)

6-816 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rxlev_min_def

rxlev_min_def

Description

The rxlev_min_def parameter specifies the default value for rxlev_min_cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <cell_desc> <location>

chg_element rxlev_min_def <value> <location> <cell_desc>

chg_cell_element rxlev_min_def <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element rxlev_min_def <location> <cell_desc>

68P02901W23-T 6-817
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 63
Each step represents an increase of 1 dBm, from -110 dBm to -47 dBm,
as shown below:
0 -110 dBm and lower
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm and higher
Default value 15 (-95 dBm)

References

GSM specification 5.08 - Appendix A - Table 1

This is a Motorola defined parameter.

6-818 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rxlev_ul_ho

rxlev_ul_ho

Description

The rxlev_ul_ho parameter specifies the averaging parameters for making handover decisions
for the uplink receive signal level.

Specify a bin_num with this command to indicate the location of the parameters to be modified.

Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is
entered for the alg_num, the bin is considered to contain invalid data.

After entering the chg_cell_element command for this parameter, the following prompts
are displayed and values must be entered:

Enter hreqave:
Enter hreqt:

When entering disp_element rxlev_ul_ho, specify bin_num to identify the location of the
parameters to be displayed.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies When alg_num is set to 255, bin_num cannot be set equal to
decision_1_ul_rxlev_av_h or decision_1_ul_rxlev_av_ih.
Operator actions Respond to the prompts after entering this command.

Syntax

Change command string

chg_cell_element rxlev_ul_ho, <bin_num> <alg_num> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rxlev_ul_ho,<bin_num> <location> <cell_desc>

68P02901W23-T 6-819
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range alg_num value depends on different attributes:
Attribute Permissible Default value
range
Hreqave 1 to 32 4
Hreqt 1 to 32 1
The range of the product of hreqave and hreqt is 1 to 32.

References

GSM parameter A_LEV_HO

GSM specification 5.08

6-820 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference rxlev_ul_pc

rxlev_ul_pc

Description

The rxlev_ul_pc parameter specifies the averaging parameters for making power control
decisions for the uplink receive signal level.

Specify a bin_num with this command to indicate the location of the parameters to be modified.

Specify an alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is
entered for the alg_num, the bin is considered to contain invalid data.

After entering the chg_cell_element command for this parameter, the following prompts
are displayed and values must be entered:

Enter hreqave:
Enter hreqt:

When entering disp_element rxlev_ul_pc, specify bin_num to identify the location of the
parameters to be displayed.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies When alg_num is set to 255, bin_num cannot be set equal
to decision_1_ul_rxlev_av_p.
Operator actions Respond to the prompts after entering this command.

Syntax

Change command string

chg_cell_element rxlev_ul_pc, <bin_num> <alg_num> <cell_desc>

Display command strings

disp_cell <cell_desc> <full>

disp_element rxlev_ul_pc,<bin_num> <location> <cell_desc>

68P02901W23-T 6-821
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range alg_num value depends on different attributes:
Attribute Permissible Default value
range
Hreqave 1 to 32 4
Hreqt 1 to 32 1

References

GSM parameter A_LEV_PC

GSM specification 5.08

6-822 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference remote_time_restore

remote_time_restore

Description

The remote_time_restore parameter sets the remote alarm restorable time. If the remote
alarm ceases for this period of time, the 2 Mbit/s circuit returns to service.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element remote_time_restore <value> <location>

Display command string

disp_element remote_time_restore <location>

Values

Valid type Integer (1 step = 100 milliseconds)

Valid range 0 to 65535
0 0 seconds 0 milliseconds
1 0.1 seconds 100 milliseconds
2 0.2 seconds 200 milliseconds
... ...
600 60 seconds 60000 milliseconds
... ...
65535 6553.5 seconds 6553500 milliseconds
Default value 600

68P02901W23-T 6-823
Jan 2010
rxlev_ul_zone Chapter 6: CM database parameters

rxlev_ul_zone

Description

The rxlev_ul_zone parameter specifies the uplink receive level threshold that must be crossed
for a handover to take place between the inner zone and the outer zone.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Concentric Cells Option must be enabled and the
inner_zone_alg parameter must be set to 1.

Syntax

Change command strings

chg_element rxlev_ul_zone <value> <location> <cell_desc>

chg_cell_element rxlev_ul_zone <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rxlev_ul_zone <location> <cell_desc>

6-824 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 63
Each step represents an increase of 1 dBm, from -110 dBm to -47 dBm,
as shown below:
0 -110 dBm and lower
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm and higher
Default value 63 (-47 dBm)

68P02901W23-T 6-825
Jan 2010
rxqual_dl_ho Chapter 6: CM database parameters

rxqual_dl_ho

Description

The rxqual_dl_ho parameter specifies the averaging parameters for making handover decisions
for the downlink receive signal quality.

Specify a bin_num with this command to indicate the location of the parameters to be modified.

Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is
entered for the alg_num, the bin is considered to contain invalid data.

After entering the chg_cell_element command for this parameter, the following prompts
are displayed and values must be entered:

Enter hreqave:
Enter hreqt:
Enter w_qual:

When entering disp_element rxqual_dl_ho, specify bin_num to identify the location of the
parameters to be displayed.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies When alg_num is set to 255, bin_num cannot be set equal
to decision_1_dl_rxqual_av_h.
Operator actions Respond to the prompts after entering this command.

Syntax

Change command string

chg_cell_element rxqual_dl_ho, <bin_num> <alg_num> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rxqual_dl_ho,<bin_num> <location> <cell_desc>

6-826 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range alg_num value depends on different attributes:
Attribute Permissible Default value
range
Hreqave 1 to 32 4

Hreqt 1 to 32 1
Qual_weight 0 to 255 1

References

GSM parameter A_QUAL_HO

GSM specification 5.08

68P02901W23-T 6-827
Jan 2010
rxqual_dl_pc Chapter 6: CM database parameters

rxqual_dl_pc

Description

The rxqual_dl_pc parameter specifies the averaging parameters for making power control
decisions with respect to the downlink receive signal quality.

Specify a bin_num with this command to indicate the location of the parameters to be modified.

Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is
entered for the alg_num, the bin is considered to contain invalid data.

After entering the chg_cell_element command for this parameter, the following prompts
are displayed and values must be entered:

Enter hreqave:
Enter hreqt:
Enter w_qual:

When entering disp_element rxqual_dl_pc, specify bin_num to identify the location of the
parameters to be displayed.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies When alg_num is set to 255, bin_num cannot be set equal
to decision_1_dl_rxqual_av_p
Operator actions Respond to the prompts after entering this command.

Syntax

Change command string

chg_cell_element rxqual_dl_pc, <bin_num> <alg_num> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rxqual_dl_pc,<bin_num> <location> <cell_desc>

6-828 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range alg_num value depends on different attributes:
Attribute Permissible Default value
range
Hreqave 1 to 32 4
Hreqt 1 to 32 1
Qual_weight 0 to 255 1

References

GSM specification 5.08

This is a Motorola defined parameter.

68P02901W23-T 6-829
Jan 2010
rxqual_ul_ho Chapter 6: CM database parameters

rxqual_ul_ho

Description

The rxqual_ul_ho parameter specifies the averaging parameters for making handover decisions
with respect to the uplink receive signal quality.

Specify a bin_num with this command to indicate the location of the parameters to be modified.

Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is
entered for the alg_num, the bin is considered to contain invalid data.

After entering the chg_cell_element command for this parameter, the following prompts
are displayed and values must be entered:

Enter hreqave:
Enter hreqt:
Enter w_qual:

When entering disp_element rxqual_ul_ho, specify bin_num to identify the location of the
parameters to be displayed.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies When alg_num is set to 255, bin_num cannot be set equal
to decision_1_ul_rxqual_av_h.
Operator actions Respond to the prompts after entering this command.

Syntax

Change command string

chg_cell_element rxqual_ul_ho, <bin_num> <alg_num> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rxqual_ul_ho,<bin_num> <location> <cell_desc>

6-830 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range alg_num value depends on different attributes:
Attribute Permissible Default value
range
Hreqave 1 to 32 4
Hreqt 1 to 32 1
Qual_weight 0 to 255 1

References

GSM parameter A_QUAL_HO

GSM specification 5.08

68P02901W23-T 6-831
Jan 2010
rxqual_ul_pc Chapter 6: CM database parameters

rxqual_ul_pc

Description

The rxqual_ul_pc parameter specifies the averaging parameters for making power control
decisions for the uplink receive signal quality.

Specify a bin_num with this command to indicate the location of the parameters to be modified.

Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is
entered for the alg_num, the bin is considered to contain invalid data.

After entering the chg_cell_element command for this parameter, the following prompts
are displayed and values must be entered:

Enter hreqave:
Enter hreqt:
Enter w_qual:

When entering disp_element rxqual_ul_pc, specify bin_num to identify the location of the
parameters to be displayed.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies When alg_num is set to 255, bin_num cannot be set equal
to decision_1_ul_rxqual_av_p.
Operator actions Respond to the prompts after entering this command.

Syntax

Change command string

chg_cell_element rxqual_ul_pc, <bin_num> <alg_num> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full>

disp_element rxqual_ul_pc,<bin_num> <location> <cell_desc>

6-832 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range alg_num value depends on different attributes:
Attribute Permissible Default value
range
Hreqave 1 to 32 4
Hreqt 1 to 32 1
Qual_weight 0 to 255 1

References

GSM parameter A_QUAL_PC

GSM specification 5.08

68P02901W23-T 6-833
Jan 2010
sap_audit_type Chapter 6: CM database parameters

sap_audit_type

Description

The sap_audit_type parameter specifies the type of audit to be run on a device at a specific site.

When this parameter is displayed using the disp_element command, a numeric value
is presented which corresponds to the values shown in the Valid range field (such as
sap_audit_type = 0). The device is specified as an index value when entering the disp_element
command. The index values available for use are described under Indices on page 1-37.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

This parameter cannot be modified from the MMI.

Display command string

disp_element sap_audit_type,<index> <location>

Values

Value type Integer

Valid range 0 to 2, 255
0 Safe (Safe Tests)
1 int_lpbk (Internal Loopback Tests)
2 Self test
255 No audit
Default value 255

6-834 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sap_device_type

sap_device_type

Description

The sap_device_type parameter specifies the type of device on which an audit runs at a
specific site.

When this parameter is displayed using the disp_element command, the device type is
displayed as an alphabetic character string (such as sap_device_type = DRI). The device
is specified as an index value when entering the disp_element command. The index values
available for use are described under Indices on page 1-37.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command strings

This parameter cannot be modified from the MMI.

Display command string

disp_element sap_device_type,<index> <location>

Values

Value type Text

Valid range N/A
Default value None

68P02901W23-T 6-835
Jan 2010
sap_end_time Chapter 6: CM database parameters

sap_end_time

Description

The sap_end_time parameter specifies the ending time for a device audit.

When this parameter is displayed using the disp_element command, the time is presented in
military standard time or GMT (such as sap_end_time = 13:45).

The device is specified as an index value when entering the disp_element command. The index
values available for use are described under Indices on page 1-37.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command strings

chg_audit_sched <location> <device_name> <audit_type> <start_time_hour>

<start_time_min><end_time_hour> <end_time_min> <interval_hour> <interval_min>

Display command string

disp_element sap_end_time,<index> <location>

Values

Value type Integer

Valid range Hours 0 to 23
Minutes 0 to 59
Default value None

6-836 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sap_interval

sap_interval

Description

The sap_interval parameter specifies the interval for a device audit.

When this parameter is displayed using the disp_element command, the time is presented in
military standard time or GMT (such as sap_interval = 13:45).

The device is specified as an index value when entering the disp_element command. The index
values available for use are described under Indices on page 1-37.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command strings

chg_audit_sched <location> <device_name> <audit_type> <start_time_hour>

<start_time_min><end_time_hour> <end_time_min> <interval_hour> <interval_min>

Display command string

disp_element sap_interval,<index> <location>

NOTE
sap_interval = interval_hour:interval_min

Values

Value type Integer

Valid range Hours 0 to 23
Minutes 0 to 59
Default value None

68P02901W23-T 6-837
Jan 2010
sap_start_time Chapter 6: CM database parameters

sap_start_time

Description

The sap_start_time parameter specifies the start time for a device audit.

When this parameter is displayed using the disp_element command, the time is presented in
military standard time or GMT (such as sap_end_time = 13:45).

The device is specified as an index value when entering the disp_element command. The index
values available for use are described under Indices on page 1-37.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command strings

chg_audit_sched <location> <device_name> <audit_type> <start_time_hour>

<start_time_min><end_time_hour> <end_time_min> <interval_hour> <interval_min>

Display command string

disp_element sap_start_time,<index> <location>

NOTE
sap_interval = interval_hour:interval_min

Values

Value type Integer

Valid range Hours 0 to 23
Minutes 0 to 59
Default value None

6-838 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sccp_bssap_mgt

sccp_bssap_mgt

Description

The sccp_bssap_mgt parameter enables or disables ITU-TSS SCCP Management.

When enabled, the BSS detects Signaling Point Inaccessible and loss of BSSAP subsystem. The
BSS also handles the following messages: User Part Unavailable (UPU), Subsystem prohibited
(SSP), Subsystem Allowed (SSA), and Subsystem Test (SST). (Use with Ericsson MSC).

When disabled, the BSS always responds to an SST with an SSA message. Set this flag only if
the MSC does ITU-TSS SCCP Management.

All BTS site values are set to the same value assigned to site 0.

Type B (operator actions required)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter applies only to the BSC.
Operator actions Place the system in the SYSGEN ON mode before using the
chg_element command to change this parameter.

Syntax

Change command string

chg_element sccp_bssap_mgt <value> 0

Display command string

disp_element sccp_bssap_mgt 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

68P02901W23-T 6-839
Jan 2010
scr_enabled Chapter 6: CM database parameters

scr_enabled

Description

The scr_enabled parameter specifies whether the Seamless Cell Reselection feature is enabled
at a BSC, or not.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Seamless Cell Reselection feature must be available
before it can be enabled with this parameter.
This parameter can be set in or out of SYSGEN mode.
Operator actions: None

NOTE
BSS software processes using this parameter are notified immediately the change
is made.

Syntax

Change command string

chg_element scr_enabled <value> <location>

Display command string

disp_element scr_enabled <location>

Values

Value type Boolean

Valid range 0 or 1
0 Seamless cell reselection is not enabled (off)
1 Seamless cell reselection is enabled (on)
Default value 0

6-840 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference score_mcs_thres_a

score_mcs_thres_a

Description

The score_mcs_thres_a parameter allows the user to set the Score MCS Threshold A in the
Coding Scheme Selection. Score MCS Threshold A is the threshold for score to prohibit MCS
promotions in the Coding Scheme Selection Algorithms.

This element is an attribute of PCU. This parameter can be accessed and updated both in
and out of SYSGEN mode.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies
This parameter can not be modified if the EGPRS
feature is restricted.

The value of score_mcs_thres_a for Score MCS

Threshold A must be less than or equal to the value of
score_mcs_thres_b for Score MCS Threshold B.

Syntax

Change command string

chg_element score_mcs_thres_a <value> pcu

Display command string

disp_element score_mcs_thres_a pcu

Values

Value type Integer

Valid range 0 to 100 In the range of 0~100, with step size of 1
0 Minimum
100 Maximum
Default value 20

68P02901W23-T 6-841
Jan 2010
score_mcs_thres_b Chapter 6: CM database parameters

score_mcs_thres_b

Description

The score_mcs_thres_b parameter allows the user to set the Score MCS Threshold B in the
Coding Scheme Selection. Score MCS Threshold B is the threshold for the score to trigger the
MCS demotion in the Coding Scheme Selection Algorithms.

This parameter can be accessed and updated both in and out of SYSGEN mode.
score_mcs_thres_b is an attribute of PCU.

Type A (no operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies
This element is not allowed if the EGPRS feature is
restricted.

The value of score_mcs_thres_b for Score MCS

Threshold B must be greater than or equal to
the value of score_mcs_thres_a for Score MCS
Threshold A.

Syntax

Change command string

chg_element score_mcs_thres_b <value> pcu

Display command string

disp_element score_mcs_thres_b pcu

Values

Value type Integer

Valid range 0 to 100 In the range of 0~100, with step size of 1
0 Minimum
100 Maximum
Default value 48

6-842 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sdcch_ho

sdcch_ho

Description

The sdcch_ho parameter enables or disables handovers on the SDCCH.

When enabled, handovers are not allowed until at least (sdcch_timer_ho * 2) measurement
report periods have elapsed.

To allow handovers on the SDCCH with a minimum delay, the sdcch_ho parameter must be
enabled and the sdcch_timer_ho parameter set to its minimum value of 1.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies External SDCCH handover must be enabled at and
supported by the MSC
The handover_required_curr_ch parameter must be
set to 1 so as to include the information element in the
handover required message to the MSC.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element sdcch_ho <value> <location> <cell_desc>

chg_cell_element sdcch_ho <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element sdcch_ho <location> <cell_desc>

68P02901W23-T 6-843
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

References

Internal name EN_SDCCH_HO

6-844 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sdcch_need_high_water_mark

sdcch_need_high_water_mark

Description

The sdcch_need_high_water_mark parameter specifies the number of idle SDCCHs to trigger

reconfiguration of traffic channels to SDCCHs.

If dynamic reconfiguration is enabled and the total number of idle SDCCHs is less than the value
of the sdcch_need_high_water_mark, the CRM tries to reconfigure TCHs to make more
SDCCHs. The total number of SDCCHs cannot exceed the value of the max_number_of_sdcchs
parameter.

NOTE
For stable operation of the channel reconfiguration process, the difference between
the values for sdcch_need_high_water_mark and sdcch_need_low_water_mark
must be greater than or equal to 9.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes

Syntax

Change command strings

chg_element sdcch_need_high_water_mark <value> <location> <cell_desc>

chg_cell_element sdcch_need_high_water_mark <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element sdcch_need_high_water_mark <location> <cell_desc>

68P02901W23-T 6-845
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (representing the number of idle SDCCHs)

Valid range 1 to 119
Default value 2

References

GSM specification 5.02 - 6.4

This is a Motorola defined parameter.

6-846 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sdcch_need_low_water_mark

sdcch_need_low_water_mark

Description

The sdcch_need_low_water_mark parameter specifies the number of idle SDCCHs to trigger

reconfiguration of SDCCHs (from previous TCH to SDCCH reconfigurations) back to TCHs.
When dynamic channel reconfiguration is enabled, and when the number of idle SDCCHs
available goes above the sdcch_need_low_water_mark value, reconfiguration of SDCCHs to
TCHs is triggered as long as the total number of SDCCHs after reconfiguration stays above the
number_sdcchs_preferred value.

Ensure that the low water mark is checked only when an SDCCH is released. Once the
number of idle SDCCHs is greater than the low water mark, SDCCH to TCH reconfiguration is
triggered. If CRM is reconfiguring an SDCCH to TCH and the low water mark is passed again,
reconfiguration is not triggered. It is triggered when the first reconfiguration is complete
and an SDCCH is released.

NOTE
For stable operation of the channel reconfiguration process, the difference between
the values for sdcch_need_high_water_mark and sdcch_need_low_water_mark
must be greater than or equal to 9.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes

Syntax

Change command strings

chg_element sdcch_need_low_water_mark <value> <location> <cell_desc>

chg_cell_element sdcch_need_low_water_mark <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element sdcch_need_low_water_mark <location> <cell_desc>

68P02901W23-T 6-847
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (number of SDCCHs)

Valid range 10 to 128
Default value 12

References

GSM specification 5.02 - 6.4

This is a Motorola defined parameter.

6-848 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sdcch_tch_band_reassign_delay

sdcch_tch_band_reassign_delay

Description

The sdcch_tch_band_reassign_delay parameter specifies the number of measurement report

periods that the RSS waits before responding to CRM if the MS does not report any preferred
band neighbor.

This parameter applies to multiband MSs only.

Use of this parameter may cause a delay in call setup of up to two seconds.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Multiband Inter-cell Handover feature must be
unrestricted.

Syntax

Change command strings

chg_element sdcch_tch_band_reassign_delay <value> <location> <cell_desc>

chg_cell_element sdcch_tch_band_reassign_delay <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element sdcch_tch_band_reassign_delay <location> <cell_desc>

Values

Value type Integer (number of measurement report periods)

Valid range 0 to 4
Default value 0

68P02901W23-T 6-849
Jan 2010
sdcch_timer_ho Chapter 6: CM database parameters

sdcch_timer_ho

Description

The sdcch_timer_ho parameter specifies the wait time (measured in SACCH multiframes)
before a handover on the SDCCH may occur.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The sdcch_ho parameter must be enabled. (This is not
monitored by the system.)

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element sdcch_timer_ho <value> <location> <cell_desc>

chg_cell_element sdcch_timer_ho <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element sdcch_timer_ho <location> <cell_desc>

6-850 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 Step = 2 SACCH multiframes)

Valid range 1 to 31
1 2 SACCH multiframes
2 4 SACCH multiframes
3 6 SACCH multiframes
... ...
... ...
... ...
31 62 SACCH multiframes
Default value 1

References

GSM parameter T_SDCCH_HO_ALLOWED

This is a Motorola parameter.

68P02901W23-T 6-851
Jan 2010
search_prio_3g Chapter 6: CM database parameters

search_prio_3g

Description

The search_prio_3g parameter specifies whether 3G cells are searched when BSIC coding is
required.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCCH feature must be unrestricted for this
parameter to change.

Syntax

Add/Change command strings

chg_element search_prio_3g <value> <location> <cell_desc>

chg_cell_element search_prio_3g <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element search_prio_3g <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 3G cells are not searched when BSIC coding is required.
1 3G cells are searched when BSIC coding is required.
Default value 1

6-852 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference second_asgnmnt

second_asgnmnt

Description

The second_asgnmnt parameter enables or disables the Second Assignment procedure. With
this parameter enabled, the RRSM initiates a second assignment procedure if it receives
an assignment failure from the MS for the first assignment. In situations where first TCH
assignment fails and the MS successfully recovers to the SDCCH, this parameter enables a
second TCH assignment attempt.

The purpose of this parameter is to improve overall TCH assignment success and call set-up
success.

To ensure that the true cause of initial assignment is not masked, a second attempt failure
results in an unsuccessful assignment message being sent to the SSM. Even if the second
assignment failure is a result of a lack of resources or equipment failure, rather than RF failure,
the cause values are not used.

The following lists the impacts when this parameter is enabled:

Enabled on a per BSS basis.

Initiated only for MSC assignments (not for intra-cell handovers).

Increased SDCCH utilization for those call set-ups which fail first assignment.

MSC Assignment Complete Timer.

Additional statistics pegging on analysis software.

The BSS does not preempt a call during the second assignment attempt for an emergency
call when there are no resources available.

The BSS does not trigger Directed Retry procedures if the cell is congested (that is, no
resources are available) when a second assignment is initiated for a call.

The BSS attempts to assign a TCH from a different carrier, starting from the outer most
zone, until an available channel is found. However, assignments from the zone's interior
are not made to the qualified zone of the MS.

The BSS attempts to assign a different TCH within the requested band on the same carrier
if a TCH from a different carrier is not available.

An extended range TCH from a different carrier is assigned to an extended range MS

during the second assignment.

68P02901W23-T 6-853
Jan 2010
Syntax Chapter 6: CM database parameters

An extended range TCH from a different carrier is assigned to a normal range MS if there
are no normal range channels available. This assignment starts from the outer most zone.

The BSS does not attempt a multiband handover during the second assignment if the
MS is multiband capable.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command strings

chg_element second_asgnmnt <value> 0

Display command strings

disp_element second_asgnmnt 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-854 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference secondary_freq_type

secondary_freq_type

Description

The secondary_freq_type parameter specifies the frequency type of the inner zone band
of a Dual Band cell. This parameter is set as the primary frequency type when a cell is not
configured as a Dual Band cell.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies
This parameter may be modified only when changing
inner_zone_alg to 3 with the chg_cell_element command.
At Dual Band Cells:

When the Cell frequency type is set to PGSM

or EGSM, the secondary_freq_type can only be set
to DCS1800.

When the Cell frequency is set to DCS1800, the

secondary_freq_type can only be set to PGSM or
EGSM.
At non-Dual Band cells, the secondary_freq_type is set to
the primary frequency type.

Syntax

Change command string

chg_cell_element =secondary_freq_type <value> <location>

Display command string

disp_element secondary_freq_type <location>

68P02901W23-T 6-855
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 1 to 8 binary values as shown below:
1 PGSM
2 EGSM
4 DCS1800
8 PCS 1900
Default value None

6-856 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference serving_band_reporting

serving_band_reporting

Description

The serving_band_reporting parameter indicates the number of cells report from the
frequency band to which the serving GSM cell belongs. The serving_band_reporting
parameter is sent to a mobile in the Measurement Information message.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Enhanced 2G/3G Handover feature must be
unrestricted to modify this parameter.

Syntax

Change command string

chg_element serving_band_reporting <location> <cell_desc>

chg_cell_element serving_band_reporting <location> <cell_desc_opt>

Display command string

disp_cell <cell_id> [full]

disp_element serving_band_reporting <location> <cell_desc>

Values

Value type Integer

Valid range 0 to 3
Default value 3

68P02901W23-T 6-857
Jan 2010
sgsn_release Chapter 6: CM database parameters

sgsn_release

Description

The sgsn_release parameter specifies whether the release version (year of release) of the
Serving GPRS Support Node (SGSN) for the BSS, is 1999 or later.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS optional feature must be unrestricted.

Syntax

Change command string

chg_element sgsn_release <value> 0

Display command string

disp_element sgsn_release 0

Values

Value type Integer (number of frames)

Valid range 0 to 2
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.
Default value 0

6-858 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sig_lnk_tst_allow

sig_lnk_tst_allow

Description

The sig_lnk_tst_allow parameter specifies whether a Signaling Link Test Message (SLTM) is
allowed to be sent to the remote MTP L3. When this parameter is enabled, the BSS sends the
SLTM to the remote MTP L3 if the MTL initial alignment procedure is successful.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element sig_lnk_tst_allow <value> <location>

Display command string

disp_element sig_lnk_tst_allow <location>

Values

Value type Boolean

Valid range 0 or 1
Default value 1

68P02901W23-T 6-859
Jan 2010
sig_weight Chapter 6: CM database parameters

sig_weight

{26638}

Description

The sig_weight parameter is an IP based NSVC parameter and identifies the signaling weight
associated with the remote IP end point.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the Gb over IP
feature is unrestricted and the Gb mode is set to static IP
mode.

Syntax

Add command strings

add_nsvc <location> <NS_VCI> <GBL_ID> if gb_mode is in the static IP mode.

add_nsvc <location> <NS_VCI> <GBL_ID> <DLCI> if gb_mode is in the frame relay mode.

Modify command strings

mod_nsvc <location> <NS_VCI>

Display command strings

disp_nsvc <NS_VCI> <nsvci_value>

disp_nsvc <location> <GBL> <gbl_value>

Delete command strings

del_nsvc <location> <nsvci_value>

6-860 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 255
0 Minimum
255 Maximum
Default value N/A

68P02901W23-T 6-861
Jan 2010
slip_loss_daily Chapter 6: CM database parameters

slip_loss_daily

Description

The slip_loss_daily parameter specifies the threshold for the frame slip daily alarm count. An
alarm generates if the count of frame slips meets or exceeds this threshold in a 24 hour period.

Consider slip_loss_daily as the first level of notification of slip loss, and slip_loss_hourly alarm
as a higher level indicating a more serious problem.

For example, if slip_loss_daily is set to 20 and slip_loss_hourly to 25, and 20 slip loss problems
occur during the day, the daily alarm triggers. The hourly alarm triggers only if 25 alarms occur
within the hour, which indicates a much more serious problem.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter must be less than slip_loss_hourly.

Syntax

Change command string

chg_element slip_loss_daily <value> <location>

Display command string

disp_element slip_loss_daily <location>

Values

Value type Integer

Valid range 0 to 65534
Default value 4

6-862 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference slip_loss_hourly

slip_loss_hourly

Description

The slip_loss_hourly parameter specifies the threshold for the frame slip hourly alarm level
count. An alarm generated if the count of frame slips exceeds this threshold in a 60 minute
period.

Consider slip_loss_daily as the first level of notification of slip loss, and slip_loss_hourly alarm
as a higher level indicating a more serious problem.

For example, if slip_loss_daily is set to 20 and slip_loss_hourly to 25, and 20 slip loss problems
occur during the day, the daily alarm triggers. The hourly alarm triggers only if 25 alarms occur
within the hour, which indicates a much more serious problem.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter must be greater than slip_loss_daily.

Syntax

Change command string

chg_element slip_loss_hourly <value> <location>

Display command string

disp_element slip_loss_hourly <location>

Values

Value type Integer

Valid range 1 to 65535
Default value 10

NOTE
MSI-2 boards default to a value of 20 on power-up. However, when MSI-2 boards are
brought in-service they default to whatever value is set in the database.

68P02901W23-T 6-863
Jan 2010
slip_loss_oos Chapter 6: CM database parameters

slip_loss_oos

Description

The slip_loss_oos parameter specifies the threshold for the frame slip out of service (OOS)
alarm level count. The 2 Mbit/s circuit is taken out of service if the number of frame slips
exceeds this threshold during a 24 hour period.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element slip_loss_oos <value> <location>

Display command string

disp_element slip_loss_oos <location>

Values

Value type Integers

Valid range 0 to 65535
Default value 255

6-864 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference slip_loss_restore

slip_loss_restore

Description

The slip_loss_restore parameter specifies the frame slip restorable time period. If no errors
occur during this period, the 2 Mbit/s circuit is brought back into service.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element slip_loss_restore <value> <location> <cell_desc>

Display command string

disp_element slip_loss_restore <location> <cell_desc>

Values

Value type Integer (1 step = 100 milliseconds

Valid range 0 to 65535
0 0 seconds 0 milliseconds
1 0.1 seconds 100 milliseconds
2 0.2 seconds 200 milliseconds
... ...
600 60 seconds 60000 milliseconds
... ...
65535 6553.5 seconds 6553500 milliseconds
Default value 600 60 seconds 60000 milliseconds

68P02901W23-T 6-865
Jan 2010
smg_gb_vers Chapter 6: CM database parameters

smg_gb_vers

Description

The smg_gb_vers parameter specifies the SMG version being adopted by the BSS over the Gb
interface.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.
Operator actions The PCU must be locked.

Syntax

Change command string

chg_element smg_gb_vers <value> 0

Display command string

disp_element smg_gb_vers <value> 0

Values

Value type Integer

Valid range 24 to 31
Default value 31

6-866 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sms_dl_allowed

sms_dl_allowed

Description

The sms_dl_allowed parameter enables or disables downlink (MS terminated) Short Message
Service (SMS).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The SMS Point to Point feature must be unrestricted.

Syntax

Change command string

chg_element sms_dl_allowed <value> <location>

Display command string

disp_element sms_dl_allowed <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification 3.04

This is a Motorola defined parameter.

68P02901W23-T 6-867
Jan 2010
sms_tch_chan Chapter 6: CM database parameters

sms_tch_chan

Description

The sms_tch_chan parameter specifies the logical radio channel for the Short Message
Service (SMS) transfer in the event of a call being present on a traffic channel. The FACCH
is tried first, and if this fails, the SACCH is used. If the current radio channel is an SDCCH,
the SDCCH is used.

Choosing to provide an SMS on the FACCH provides more opportunity to deliver the message.
The timing constraints on the SACCH allow a block to be transferred every 208 frames, while the
FACCH allows a block to be delivered every 8 frames. The disadvantage of the FACCH channel
is that frames are stolen, with injurious effects on the audio quality or data transmission.
Stealing frames on the FACCH is more noticeable as the size of the short message increases, but
using the SACCH for larger short messages means longer delivery times.

NOTE
SMS on the FACCH is not covered in the GSM specifications and may not be
supported by mobile stations.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies The SMS Point to Point feature must be unrestricted.

Syntax

Change command string

chg_element sms_tch_chan <value> <location>

Display command string

disp_element sms_tch_chan <location>

6-868 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 2
0 BSS_ALGORITHM
1 FACCH always used
2 SACCH always used
Default value 2

References

GSM specification 3.04

This is a Motorola defined parameter.

68P02901W23-T 6-869
Jan 2010
sms_ul_allowed Chapter 6: CM database parameters

sms_ul_allowed

Description

The sms_ul_allowed parameter enables or disables uplink (MS originated) Short Message
Service (SMS).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The SMS Point to Point feature must be unrestricted.

Syntax

Change command string

chg_element sms_ul_allowed <value> <location>

Display command string

disp_element sms_ul_allowed <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

References

GSM specification 3.04

This is a Motorola defined parameter.

6-870 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ss7_mode

ss7_mode

Description

The ss7_mode parameter specifies the type of SS7 for the BSC. This parameter permits the
ITU or ANSI version to be selected.

The ITU C7 version is consistent with the GSM specifications. The ANSI version is used to
support PCS1900 applications in the United States.

This parameter can be changed only when the operator is in SYSGEN ON mode. It can only be
changed for site 0. All BTS site values are set to the same value assigned to site 0.

When the ss7_mode parameter is changed, the system compares the value to the settings for
dpc and opc. If the three variables are not compatible, the system rejects the change and
displays an error message.

The error message displays only if lcs_mode is 2 and lb_int_dpc is in range, or if lcs_mode is
not 2.

Type B (operator actions required)

Supported by OMC-R GUI No
Cell description required No
Dependencies The system checks the values of the opc (see opc on page
6-666) and dpc (see dpc on page 6-244) variables and
compares them to the value of ss7_mode. If the ranges
are not compatible, the system rejects the changes. This
parameter requires a location value of 0 or bsc.
If the operator attempts to change the SS7 mode element
to a value which causes the Lb-interface DPC to be out of
range, the command is rejected.
If the operator attempts to change the SS7 mode element
to a value which causes the Lb-interface DPC and either
the dpc, opc, or both, to be out of range, the command is
rejected.
Operator actions Place the system in the SYSGEN ON mode to change this
parameter.

Syntax

Change command strings

chg_element ss7_mode <value> <location>

68P02901W23-T 6-871
Jan 2010
Values Chapter 6: CM database parameters

Display command strings

disp_element ss7_mode <location>

Values

Value type Boolean

Valid range 0 or 1
0 ITU version
1 ANSI version
Default value 0

6-872 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ssm_critical_overload_threshold

ssm_critical_overload_threshold

Description

The ssm_critical_overload_threshold parameter specifies 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 (which is {34282} 1620 for GPROC3/GPROC3-2 and 800 for GPROC2). After this
threshold has been met or exceeded, no MS originated calls are allowed. The remaining SSM
resources are used to accommodate handover of existing calls. Every time the usage meets or
exceeds this threshold, two access classes are barred. This number has to be greater than the
ssm_normal_overload_threshold parameter.

NOTE
Other parameters can affect flow control. Refer to ccch_load_period,
rach_load_period, rach_load_threshold, ssm_normal_overload_threshold or
tch_flow_control.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies Must be greater than the
ssm_normal_overload_threshold parameter.
This parameter applies only to the BSC.

Syntax

Change command string

chg_element ssm_critical_overload_threshold <value> 0

Display command string

disp_element ssm_critical_overload_threshold 0

68P02901W23-T 6-873
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (percent of call information blocks in use)

Valid range 0 to 100
Default value 80

6-874 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ssm_normal_overload_threshold

ssm_normal_overload_threshold

Description

The ssm_normal_overload_threshold parameter specifies 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 (which is {34282} 1620 for GPROC3/GPROC3-2 and 800 for GPROC2). Every time
the usage equals or exceeds this threshold, one access class is barred.

NOTE
Other parameters can affect flow control. Refer to ccch_load_period,
rach_load_period, rach_load_threshold, ssm_critical_overload_threshold or
tch_flow_control.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies Must be less than the ssm_critical_overload_threshold
parameter.
This parameter applies only to the BSC.

Syntax

Change command string

chg_element ssm_normal_overload_threshold <value> 0

Display command string

disp_element ssm_normal_overload_threshold 0

Values

Value type Integer (percent of call information blocks in use)

Valid range 0 to 100
Default value 70

68P02901W23-T 6-875
Jan 2010
ssp_burst_delay Chapter 6: CM database parameters

ssp_burst_delay

Description

The ssp_burst_delay parameter specifies the length of time between the bursts of data. The
ssp_burst_limit parameter specifies the number of messages in each burst.

Statistical information is forwarded from the Site Statistics Process (SSP) to the Central
Statistics Process (CSP) in bursts.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element ssp_burst_delay <value> <location>

Display command string

disp_element ssp_burst_delay <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 2500
Default value 200

6-876 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ssp_burst_limit

ssp_burst_limit

Description

The ssp_burst_limit parameter specifies the number of messages included in each burst. The
ssp_burst_delay parameter specifies the length of time between bursts.

Statistical information is forwarded from the Site Statistical Process (SSP) to the Central
Statistical Process (CSP) in bursts.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element ssp_burst_limit <value> <location>

Display command string

disp_element ssp_burst_limit <location>

Values

Value type Integer (number of messages)

Valid range 1 to 65535
Default value 10

68P02901W23-T 6-877
Jan 2010
stat_interval Chapter 6: CM database parameters

stat_interval

Description

The stat_interval parameter sets the time, in minutes, that the statistics file is reported
to the OMC-R.

If the operator fails to reset the interval to 30 minutes, the OMC-R calculations of the Key
Statistics and Health Indicators are interrupted for the entire period until the interval is reset.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies Must be set to 30 or 60 minutes to align with the OMC-R.

Syntax

Change command string

chg_element stat_interval <value> 0

Display command string

disp_element stat_interval 0

Values

Value type Integer (minutes)

Valid range 5 to 60
Default value 30

NOTE
Any value between 5 minutes and 60 minutes is valid, the OMC-R only parses
uploaded statistics files if this attribute is set to 30 minutes or 60 minutes.

6-878 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference stop_dri_tx_enable

stop_dri_tx_enable

Description

The stop_dri_tx_enable parameter enables/disables the Stop Tx when CELL OOS feature that
allows the operator the option to adjust the period of time between a CELL going OOS, and the
radios to stop transmitting. The operator can adjust this value at any time, but changes do not
have effect for any Cell transitioning at that time.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Security level 3
Cell description required No
Dependencies This parameter is only valid at the BSC.
Operator actions None

Syntax

Change command string

chg_element stop_dri_tx_enable <value> 0

Display command string

disp_element stop_dri_tx_enable <location>

Values

Value type Boolean

Valid range 0 to 1
0 If set to No (0), the DRIs do not stop transmitting when
the cell goes OOS.
1 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.
Default value 0

68P02901W23-T 6-879
Jan 2010
stp_pc Chapter 6: CM database parameters

stp_pc

Description

The stp_pc parameter is the point code of the adjacent signaling point (STP).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The existing element dpc should be set to the point code
of the MSC.

Syntax

Change command strings

chg_ele stp_pc <value> 0

Display command strings

disp_ele stp_pc 0

Values

Value type Integer

Valid range 0 to 16383
Default value 0

6-880 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference stp_pc_enabled

stp_pc_enabled

Description

The stp_pc_enabled parameter enables the BSS to connect MTL through STP.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command strings

chg_ele stp_pc_enabled <value> 0

Display command strings

disp_ele stp_pc_enabled 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-881
Jan 2010
stream_downgrade_enabled Chapter 6: CM database parameters

stream_downgrade_enabled

Description

The stream_downgrade_enabled parameter enables or disables the downgrading of GBR and

Transfer Delay of an admitted PFC during future retention procedures to a lower value than the
initially committed.

stream_downgrade_enabled controls negotiation of GBR, TD, MaxSDUsize, besides RT-nRT

downgrade.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This attribute can only be modified only if Qos Phase II is
enabled or unrestricted at the OMC

Syntax

Change command strings

chg_element stream_downgrade_enabled <value> <location>

Display command strings

disp_element stream_downgrade_enabled <location>

Values

Value type Boolean

Valid range 0 or 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
Default value 1

6-882 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference streaming_enabled

streaming_enabled

Description

The streaming_enabled parameter provides streaming support per BSS when enabled and if
the operator disables the attribute, then the support for all streaming traffic class, all existing
streaming or conversational PFCs are deleted by the BSS.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This attribute can only be modified only if Qos Phase II is
enabled or unrestricted at the OMC

Syntax

Change command strings

chg_element streaming_enabled <value> <location>

Display command strings

disp_element streaming_enabled <location>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-883
Jan 2010
subnet_mask Chapter 6: CM database parameters

subnet_mask

{26638}

Description

The subnet_mask parameter identifies the PCU Ethernet GBL subnet mask.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the Gb over IP
feature is unrestricted and the Gb mode is set to static IP
mode.

Syntax

Equip command strings

equip <location> gbl

Unequip command strings

unequip <location> gbl <gbl id>

Display command strings

disp_equipment <location> gbl <gbl id>

Modify command strings

modify_value pcu subnet_mask <value> gbl <gbl id>

6-884 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 128.0.0.0 to 225.255.255.255
128.0.0.0 Minimum
225.255.255.255 Maximum
Default value N/A

NOTE
Most significant bit is 1 and the least significant bit is 0.

68P02901W23-T 6-885
Jan 2010
super_bts_indicator Chapter 6: CM database parameters

super_bts_indicator

{36039G}

Description

The super_bts_indicator parameter indicates whether there is any MMS being configured as
satellite mode in the BTS or BSC.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Display command string

disp_element super_bts_indicator <location>disp_element super_bts_indicator

<location> all

Values

Value type Boolean

Valid range 0 to 1
0 Non-super BTS or BSC without MMS in satellite mode.
1 Super BTS or BSC with MMS in satellite mode.
Default value 0

6-886 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference surround_cell

surround_cell

Description

The surround_cell parameter specifies the averaging parameter for a serving cell's neighbor
cells. The system uses this parameter to determine which neighbor cell to hand off to.

Specify a bin_num with this command to indicate the location of the parameters to be modified.

Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is
entered for the alg_num, the bin is considered to contain invalid data.

After entering the chg_cell_element command for this parameter, the following prompts
are displayed and values must be entered:

Enter hreqave:
Enter hreqt:

When entering disp_element surround_cell, specify bin_num to identify the location of the
parameters to be displayed.

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies When alg_num is set to 255, bin_num cannot be set equal
to decision_1_pbgt_rxlev_av_h.
Operator actions Respond to the prompts after entering this command.

Syntax

Change command string

chg_cell_element surround_cell, <bin_num> <alg_num> <cell_desc_opt>

Display command string

disp_cell <cell_id> <full>

disp_element surround_cell,<bin_num> <location> <cell_desc>

68P02901W23-T 6-887
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 255
Default value None

References

GSM parameter A_PBGT_HO

GSM specification 5.08

6-888 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sw_pdtch_priority

sw_pdtch_priority

Description

The sw_pdtch_priority defines the priority level of switchable PDTCH resources. This prevents
calls with priority level greater than the PDTCH priority level from stealing PDTCH resources
when the eMLPP feature is unrestricted.

The highest priority is 1. Greater than means numerically greater, that is, 4 is greater than 3
but is a lower priority. Therefore, calls with priority 4 to 14 cannot steal switchable PDTCH
when sw_pdtch_priority is set to 3.

Setting sw_pdtch_priority to 14 disables priority protection and allows all calls to allocate
switchable PDTCH resources.

Type A (No operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The eMLPP feature must be unrestricted.

Syntax

Change command string

chg_element sw_pdtch_priority <value> 0

Display command string

disp_element sw_pdtch_priority <location>

Values

Value type Integer

Valid range 1 to 14
Default value 14

68P02901W23-T 6-889
Jan 2010
sw_ts_less_one_carrier Chapter 6: CM database parameters

sw_ts_less_one_carrier

Description

The sw_ts_less_one_carrier parameter specifies the number of timeslots that the BSS should
allocate as switchable between (Traffic) TCH and (Packet Data) PDCH in a cell when one of the
carriers in the cell goes Out Of Service (OOS).

The value of (switch_gprs_pdchs minus sw_ts_less_one_carrier) is subtracted from

sw_ts_less_one carrier for each additional carrier that is lost.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.
RTFs must be equipped in the database.
The BSS verifies whether there are enough carriers
equipped in the database to support the value set by this
parameter and the res_ts_less_one_carrier parameter and
that the combined total does not exceed 30.
The primary PCU must be specified.

NOTE

BSS software processes using this parameter are notified immediately after the
change is made.
When an attempt is made to change sw_ts_less_one_carrier, and the requested
PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the
request and issues a warning to indicate that there is not enough GDS or PMC
resource available.

Syntax

Change command strings

chg_element sw_ts_less_one_carrier <value> <location> <cell_desc>

chg_cell_element sw_ts_less_one_carrier <value> <cell_desc_opt>

6-890 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Display command strings

disp_element sw_ts_less_one_carrier <location> <cell_desc>

Values

Value type Integer (number of timeslots)

Valid range 0 to 30
Default value Until set, assumes the value of switch_gprs_pdchs

68P02901W23-T 6-891
Jan 2010
swfm_enable Chapter 6: CM database parameters

swfm_enable

Description

The swfm_enable parameter enables or disables Software Fault Management (SWFM) alarm
messages to be reported to all local MMI terminals that have alarm reporting enabled.

This parameter affects the entire BSS.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter applies only to a BSC.

Syntax

Change command string

chg_element swfm_enable <value> 0

Display command string

disp_element swfm_enable 0

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

6-892 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference switch_gprs_pdchs

switch_gprs_pdchs

Description

The switch_gprs_pdchs parameter specifies the number of timeslots that the BSS should
allocate as switchable (Traffic) TCH and (Packet Data) PDCH in the cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.
Enough timeslots must be available on all of the GPRS cell
carriers.
The number of idle circuit switched resources on the
GPRS cell specified by gprs_reconfig_thresh_idle_tch
parameter (see gprs_reconfig_thresh_idle_tch on page
6-374, must be exceeded.
The primary PCU must be specified.

NOTE

BSS software processes using this parameter are notified immediately after the
change is made.
When an attempt is made to change switch_gprs_pdchs, and the requested
PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the
request and issues a warning to indicate that there is not enough GDS or PMC
resource available.

Syntax

Change command strings

chg_element switch_gprs_pdchs <value> <location> <cell_desc>

chg_cell_element switch_gprs_pdchs <value> <cell_desc_opt>

Display command string

disp_element switch_gprs_pdchs <location> <cell_desc>

68P02901W23-T 6-893
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer (number of timeslots)

Valid range 0 to 30
Default value 0

6-894 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sync_loss_daily

sync_loss_daily

Description

The sync_loss_daily parameter specifies the threshold for the synchronization loss daily alarm
level count. An alarm generates if the number of synchronization loss alarms meets or exceeds
this threshold during a 24 hour period.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter must be less than sync_loss_hourly.

Syntax

Change command string

chg_element sync_loss_daily <value> <location>

Display command string

disp_element sync_loss_daily <location>

Values

Value type Integer

Valid range 0 to 65535
Default value 16

68P02901W23-T 6-895
Jan 2010
sync_loss_hourly Chapter 6: CM database parameters

sync_loss_hourly

Description

The sync_loss_hourly parameter specifies the threshold for the synchronization loss hourly
alarm level count. An alarm generates if the number of sync loss alarms meets or exceeds this
threshold during a 60 minute period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter must be greater than sync_loss_daily.

Syntax

Change command string

chg_element sync_loss_hourly <value> <location>

Display command string

disp_element sync_loss_hourly <location>

Values

Value type Integer

Valid range 0 to 65535
Default value 20

6-896 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sync_loss_oos

sync_loss_oos

Description

The sync_loss_oos parameter specifies the threshold for the synchronization loss, Out Of
Service (OOS) daily alarm level count. The 2 Mbit/s circuit is taken out of service if the number
of sync loss alarms meets or exceeds this threshold during a 24 hour period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element sync_loss_oos <value> <location>

Display command string

disp_element sync_loss_oos <location>

Values

Value type Integer

Valid range 0 to 65535
Default value 511

68P02901W23-T 6-897
Jan 2010
sync_loss_restore Chapter 6: CM database parameters

sync_loss_restore

Description

The sync_loss_restore parameter specifies the synchronization loss restorable time period for
a sync_loss_oos_alarm. If a synchronization loss alarm does not occur within this period, the
2 Mbit/s circuit is brought back in service.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element sync_loss_restore <value> <location>

Display command string

disp_element sync_loss_restore <location>

Values

Value type Integer (1 step = 100 milliseconds)

Valid range 0 to 65535
0 0 seconds 0 milliseconds
1 0.1 second 100 milliseconds
.. . .. . .. .

25 2.5 seconds 2500 milliseconds

.. . .. . .. .
65535 6553.5 seconds 6553500 milliseconds
Default value 600 60 seconds 60000 milliseconds

6-898 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference sync_time_oos

sync_time_oos

Description

The sync_time_oos parameter specifies the synchronization loss time period. If synchronization
is lost for this period, the 2 Mbit/s circuit is taken Out Of Service (OOS).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element sync_time_oos <value> <location>

Display command string

disp_element sync_time_oos <location>

Values

Value type Integer (1 step = 100 milliseconds)

Valid range 0 to 65535
0 0 seconds 0 milliseconds
1 0.1 second 100 milliseconds
.. . .. . .. .

25 2.5 seconds 2500 milliseconds

.. . .. . .. .
65535 6553.5 seconds 6553500 milliseconds
Default value 25 2.5 seconds 2500 milliseconds

68P02901W23-T 6-899
Jan 2010
sync_time_restore Chapter 6: CM database parameters

sync_time_restore

Description

The sync_time_restore parameter specifies the synchronization loss restorable time period. If
synchronization returns for this period, the 2 Mbit/s circuit is brought back in service.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element sync_time_restore <value> <location>

Display command string

disp_element sync_time_restore <location>

Values

Value type Integer (1 step = 100 milliseconds)

Valid range 00 to 65535
0 0 seconds 0 milliseconds
1 0.1 seconds 100 milliseconds
2 0.2 seconds 200 milliseconds
... ...
600 60 seconds 60000 milliseconds
... ...
65535 6553.5 seconds 6553500 milliseconds

Default value 600 60 seconds 60000 milliseconds

6-900 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference t_avg_t

t_avg_t

Description

The t_avg_t parameter specifies the number of multiframes for C averaging in the Packet
Transfer mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.
Operator actions None

NOTE
BSS software processes using this parameter are notified immediately the change
is made.

Syntax

Change command strings

chg_element t_avg_t <value> <location> <cell_desc>

chg_cell_element t_avg_t <value> <cell_desc_opt>

Display command string

disp_element t_avg_t <location> <cell_desc>

Values

Value type Integer (multiframes)

Valid range 0 to 25
Default value 10

68P02901W23-T 6-901
Jan 2010
t_avg_w Chapter 6: CM database parameters

t_avg_w

Description

The t_avg_w parameter specifies the number of multiframes for C averaging in the Packet
Wait mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.
Operator actions: None

NOTE
BSS software processes using this parameter are notified immediately the change
is made.

Syntax

Change command strings

chg_element t_avg_w <value> <location> <cell_desc>

chg_cell_element t_avg_w <value> <cell_desc_opt>

Display command string

disp_element t_avg_w <location> <cell_desc>

6-902 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (multiframes)

Valid range 0 to 25
Default value 10

NOTE
Values greater than 25 are interpreted as 25 by the mobile station (MS).

68P02901W23-T 6-903
Jan 2010
t_terrestrial_fail Chapter 6: CM database parameters

t_terrestrial_fail

{36039G}

Description

The t_terrestrial_fail parameter sets the tolerable time for event when all the RSL on the
terrestrial links fail.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter can be modified only when the Abis auto
swap feature (abisautoswapOpt) is enabled.

Syntax

Change command string

chg_element t_terrestrial_fail <value> <location>

Display command string

disp_element t_terrestrial_fail <location>

Values

Value type Integer

Valid range 6 to 30
6 Minimum
30 Maximum
Default value 6

6-904 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference tch_busy_critical_threshold

tch_busy_critical_threshold

Description

The tch_busy_critical_threshold parameter specifies the threshold for initiating the flow
control procedure barring two of the access classes 0 to 9 from making calls due to TCH
congestion.

The two classes that are barred are selected randomly.

The flow control procedure initiates when the percentage of busy TCHs is equal to or greater
than the value entered for this parameter.

This parameter is expressed as a percentage.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter must be greater than or equal to
tch_busy_norm_threshold.

Syntax

Change command string

chg_element tch_busy_critical_threshold <value> <location>

Display command string

disp_element tch_busy_critical_threshold <location>

Values

Value type Integer (percent of busy TCHs)

Valid range 81 to 100
Default value 100

68P02901W23-T 6-905
Jan 2010
tch_busy_norm_threshold Chapter 6: CM database parameters

tch_busy_norm_threshold

Description

The tch_busy_norm_threshold parameter specifies the threshold for initiating the flow control
procedure to bar a single access class 0 through 9 from making a call due to TCH congestion.
The class that is barred is selected randomly. The flow control procedure initiates when the
percentage of busy TCHs is equal to or greater than the value entered for this parameter.

This parameter is expressed as a percentage.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter must be less than or equal to
tch_busy_critical_threshold.

Syntax

Change command string

chg_element tch_busy_norm_threshold <value> <location>

Display command string

disp_element tch_busy_norm_threshold <location>

Values

Value type Integer (percent of busy TCHs)

Valid range 0 to 100
Default value 100

6-906 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference tch_congest_prevent_thres

tch_congest_prevent_thres

Description

The tch_congest_prevent_thres parameter specifies the level of overall TCH utilization by any
MS in a given Cell, at which the Congestion Relief procedure is initiated.

This parameter is expressed as a percentage.

Type A (no operation actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Congestion Relief feature must be enabled.
This parameter must be greater than or equal to
mb_tch_congest_thres.

Syntax

Change command string

chg_element tch_congest_prevent_thres <value> <location> <cell_desc>

Display command string

disp_element tch_congest_prevent_thres <location> <cell_desc>

Values

Value type Integer (percent)

Valid range 1 to 101 (The value 101 indicates there are no resources left to allocate).
Default value 100 (The value 100 indicates an attempt to use the last resource).

68P02901W23-T 6-907
Jan 2010
tch_flow_control Chapter 6: CM database parameters

tch_flow_control

Description

The tch_flow_control parameter enable or disables the TCH flow control option.

The flow control procedure tries to reduce the load on the system when the TCH
usage goes above thresholds determined by the tch_busy_norm_threshold and
tch_busy_critical_threshold parameters. The reduction in traffic is achieved by barring access
classes and manipulating the tx_integer and max_retran parameters.

NOTE
Other parameters can affect flow control. Refer to ccch_load_period,
rach_load_period, rach_load_threshold, ssm_critical_overload_threshold, or
ssm_normal_overload_threshold.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element tch_flow_control <value> <location> <cell_desc>

chg_cell_element tch_flow_control <value> <cell_desc_opt>

Display command string

disp_element tch_flow_control <location> <cell_desc>

6-908 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-909
Jan 2010
tch_full_need_low_water_mark Chapter 6: CM database parameters

tch_full_need_low_water_mark

Description

The tch_full_need_low_water_mark parameter specifies the low need water mark used by
the Cell Resource Manager (CRM) to determine the need for reconfiguration of full rate traffic
channels (TCHs) to SDCCHs.

This parameter specifies the minimum number of TCHs the system attempts to maintain when
dynamic reconfiguration is enabled.

If the total number of idle SDCCHs falls below the value of the sdcch_need_high_water_mark,
the CRM tries to reconfigure TCHs to make more SDCCHs. To reconfigure a TCH, the number
of TCHs must be greater than the value of the tch_full_need_low_water_mark parameter.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies channel_reconfiguration_switch feature must be
enabled.

Syntax

Change command strings

chg_element tch_full_need_low_water_mark <value> <location> <cell_desc>

chg_cell_element tch_full_need_low_water_mark <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element tch_full_need_low_water_mark <location> <cell_desc>

Values

Value type Integer (number of channels)

Valid range 0 to 255
Default value 255

6-910 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference tch_usage_threshold

tch_usage_threshold

Description

The tch_usage_threshold parameter specifies or denotes the threshold for Traffic Channel
(TCH) usage on the BCCH band, beyond which the Fast Call feature is disabled so that cell and
non-emergency voice calls are assigned to an SDCCH.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Modification oftch_usage_threshold is not allowed if the
Fast Call feature is restricted.

Syntax

Change command strings

chg_element tch_usage_threshold <value> <location> <cell_desc>

chg_cell_element tch_usage_threshold <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element tch_usage_threshold <location> <cell_desc>

Values

Value type Integer (percent)

Valid range 0 to 100
Default value 0 Disables the Fast Call feature

68P02901W23-T 6-911
Jan 2010
tdd_qoffset Chapter 6: CM database parameters

tdd_qoffset

Description

The tdd_qoffset CELL element is used in the cell reselection algorithm followed by the MS for
UMTS TDD neighbor cell.

This parameter is set to the default if the copy_cell command is used.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Modification of this element is allowed only when the
TD-SCDMA inter-working feature is unrestricted.

Syntax

Add/Change command strings

chg_element tdd_qoffset <value> <location> <cell_desc>

chg_cell_element tdd_qoffset <value> <cell_desc>

Display command strings

disp_element tdd_qoffset <location> <cell_desc>

disp_cell <cell_desc> [full]

Values

Value type Integer

Valid range 0 - 15
Default value 8

6-912 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference td_enabled

td_enabled

Description

The td_enabled BSS element specifies whether TD-SCDMA inter-working function is enabled or
disabled.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies Modification of td_enabled is allowed only when
TD-SCDMA inter-working feature (tdOpt) is unrestricted.
Modification of td_enabled from 0 to 1 is allowed only
when Inter-RAT handover feature is restricted.
If the local_maintenance flag is disabled, the MMI
is prevented from switching TD-SCDMA inter-working
function on or off.

Syntax

Add/Change command strings

chg_element td_enabled <value> <location>

Display command string

disp_element td_enabled <location>

Values

Value type Boolean

Valid range 0 TD-SCDMA inter-working is off.
1 TD-SCDMA inter-working is on.
Default value 0

68P02901W23-T 6-913
Jan 2010
tdm_switch Chapter 6: CM database parameters

tdm_switch

Description

The tdm_switch parameter specifies if the TDM availability enhancements function is enabled.

This parameter may be changed inside and outside SYSGEN mode. There is no warning when
it is changed inside SYSGEN. Outside sysgen, the warning is only printed when tdm_switch
is changed to 0.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

chg_element tdm_switch <value> <location>

Display command strings

disp_element tdm_switch <location>

Values

Value type Binary

Valid range 0 Switch is closed
1 Switch is open
Default value 0

6-914 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference tdm_ts_blocks

tdm_ts_blocks

Description

The tdm_ts_blocks parameter identifies the number of TDM 32-timeslot blocks reserved for
the PSI.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

modify_value

Values

Value type Integer

Valid range 2 to 10
Default value 2

68P02901W23-T 6-915
Jan 2010
temporary_offset Chapter 6: CM database parameters

temporary_offset

Description

The temporary_offset parameter specifies a value used by the MS as part of its calculation of
C2 for the cell reselection process described in TSGSM 5.08. It is used to apply a negative offset
to C2 for the duration of the penalty_time timer parameter.

C2 is the reselection priority assigned to a cell which can be broadcast on the BCCH of each
cell. When more than one cell is available for reselection, the MS reselects the cell with the
highest C2 value.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The cell_reselect_param_ind parameter must be enabled.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element temporary_offset <value> <location> <cell_desc>

chg_cell_element temporary_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element temporary_offset <location> <cell_desc>

6-916 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (1 Step = 10 dB)

Valid range 0 to 7
Default value 0

References

GSM parameter C2
GSM specification TS GSM 4.08 Table 10.32a section 10.5.2.35
TS GSM 5.08

68P02901W23-T 6-917
Jan 2010
terr_or_sate Chapter 6: CM database parameters

terr_or_sate

{36039G}

Description

The BSC shall support a new equipment attribute terr_or_sate to indicate the Abis bearing
attribute of the MMS.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies
The two commands can only be allowed when the Abis
auto swap feature (abisautoswapOpt) is unrestricted.

This attribute can be modified:

When the MMS has been configured to a PATH.

When the BTS type is Horizon II macro (if the

target site is BTS).

All the MMSs configured to the terrestrial link by

default (that is, MMS 00, 01 and 02) cannot be
configured to the satellite link.

Syntax

Change command string

modify_value <location> terr_or_sate <value> mms <mms_id1> <mms_id2>

Display command string

disp_equipment <location> mms <mms_id1> <mms_id2>

6-918 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 to 1
0 Terrestrial link
1 Satellite link
Default value 0

68P02901W23-T 6-919
Jan 2010
thp_be_weight Chapter 6: CM database parameters

thp_be_weight

Description

The thp_be_weight parameter specifies the Traffic Handling Priority (THP) weight of Best
Effort class. THP controls relative throughput of Packet Flow Contexts (PFCs) by assigning a
weighting factor for Best Effort class.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of thp_be_weight cannot be changed if
bssgp_pfc_bit is set to 1.
The value of thp_bg_weight and thp_be_weight must be
less than or equal to thp_i3_weight.

Syntax

Change command strings

chg_element thp_be_weight <value> <location>

Display command strings

disp_element thp_be_weight <location>

Values

Value type Integer (weighting factor)

Valid range 0 to 40
Default value 40

6-920 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference thp_bg_weight

thp_bg_weight

Description

The thp_bg_weight parameter specifies the Traffic Handling Priority (THP) weight of
Background class. THP controls relative throughput of Packet Flow Contexts (PFCs) by
assigning a weighting factor for Background class.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of thp_be_weight cannot be changed if
bssgp_pfc_bit is set to 1.
The value of thp_bg_weight and thp_be_weight must be
less than or equal to thp_i3_weight.

Syntax

Change command strings

chg_element thp_bg_weight <value> <location>

Display command strings

disp_element thp_bg_weight <location>

Values

Value type Integer (weighting factor)

Valid range 10 to 40
Default value 40

68P02901W23-T 6-921
Jan 2010
thp_i2_weight Chapter 6: CM database parameters

thp_i2_weight

Description

The thp_i2_weight parameter specifies the Traffic Handling Priority (THP) weight of Interactive
2 class. THP controls relative throughput of PFCs by assigning a weighting factor for
interactive 2 class.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of thp_i2_weight cannot be changed if
bssgp_pfc_bit is set to 1.
The value of thp_i2_weight must be greater than or equal
to the value of thp_i3_weight

Syntax

Change command strings

chg_element thp_i2_weight <value> <location>

Display command strings

disp_element thp_i2_weight <location>

Values

Value type Integer (weighting factor)

Valid range 10 to 40
Default value 40

6-922 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference thp_i3_weight

thp_i3_weight

Description

The thp_i3_weight parameter specifies the Traffic Handling Priority (THP) weight of Interactive
3 class. THP controls relative throughput of Packet Flow Contexts (PFCs) by assigning a
weighting factor for interactive 2 class.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of thp_i3_weight cannot be changed if
bssgp_pfc_bit is set to 1.
The value of thp_bg_weight and thp_be_weight must be
less than or equal to thp_i3_weight.
The value of thp_i3_weight must be less than or equal to
the value of thp_i2_weight.

Syntax

Change command strings

chg_element thp_i3_weight <value> <location>

Display command strings

disp_element thp_i3_weight <location>

Values

Value type Integer

Valid range 10 to 40
Default value 40

68P02901W23-T 6-923
Jan 2010
thp_stream_weight Chapter 6: CM database parameters

thp_stream_weight

Description

The thp_stream_weight parameter specifies the THP weight of the streaming traffic class.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies 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.

Syntax

Change command strings

chg_element thp_stream_weight <value> <location>

Display command strings

disp_element thp_stream_weight <location>

Values

Value type Integer

Valid range 10 to 40 All values within the range of 10 to 40 are valid, the higher
the value, the greater the precedence.
Default value 40

6-924 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference threshold

threshold

Description

The threshold parameter specifies the number of times that the Cell Resource Manager (CRM)
attempts to assign a Signaling Connection Control Part (SCCP) number before rejecting the
request.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element threshold <value> <location> <cell_desc>

chg_cell_element threshold <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element threshold <location> <cell_desc>

Values

Value type Integer (number of assign attempts.)

Valid range 0 to 255
Default value 7

68P02901W23-T 6-925
Jan 2010
timing_advance_period Chapter 6: CM database parameters

timing_advance_period

Description

The timing_advance_period parameter specifies the interval between timing advance changes.

The interval should be greater than or equal to hreqavex * decision_1_n8.

Where:
hreqave is the number of measurements from the MS that are used in calculating one
average.

x equals:
1 (lower threshold of RXLEV),

2 (upper threshold of RXLEV),

3 (lower threshold of RXQUAL), or

4 (upper threshold of RXQUAL).

decision_1_n8 is the number of samples in the threshold comparison process.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies hreqave, decision_1_n8.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element timing_advance_period <value> <location> <cell_desc>

chg_cell_element timing_advance_period <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element timing_advance_period <location> <cell_desc>

6-926 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 31 Mapped to SACCH multiframes:
0 0 SACCH multiframes
1 2 SACCH multiframes
2 4 SACCH multiframes
... ...
... ...
... ...
31 62 SACCH multiframes
Default value 4 8 SACCH multiframes

68P02901W23-T 6-927
Jan 2010
tlli_blk_coding Chapter 6: CM database parameters

tlli_blk_coding

Description

The tlli_blk_coding parameter is used to request the mobile station to use the coding scheme
commanded for the Temporary Block Flow (TBF) even for RLC blocks containing the contention
resolution Temporary Logical Link Identifier (TLLI).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

Syntax

Change command strings

chg_element tlli_blk_coding <value> <location> <cell_desc>

chg_cell_element tlli_blk_coding <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element <location> <cell_desc>

Values

Value type Boolean

Valid range 0 Always use CS1 for GPRS TBFs for TLLI blocks, and MCS1
for EGPRS TBFs for TLLI blocks.
1 Use the commanded coding scheme for all blocks.
Default value 0 The default is 0 because commanding the mobile to use the
lowest coding scheme (CS1 or MCS1) during contention
resolution increases the probability of establishing the
uplink TBF successfully in all RF conditions in the cell.

6-928 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference trace_msgs_after_ho

trace_msgs_after_ho

Description

The trace_msgs_after_ho parameter specifies the number of messages that the system collects
immediately after a handover occurs.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is used only when handover records are
requested and RSS, Abis and/or MS Power control data are
specified.
This parameter applies only to the BSC.

Syntax

Change command strings

chg_element trace_msgs_after_ho <value> 0

Display command string

disp_element trace_msgs_after_ho 0

Values

Value type Integer (number of messages to be collected after a handover)

Valid range 0 to 8
Default value 5

68P02901W23-T 6-929
Jan 2010
trace_msgs_before_ho Chapter 6: CM database parameters

trace_msgs_before_ho

Description

The trace_msgs_before_ho parameter specifies the number of messages that the system
collects immediately before a handover occurs.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is used only when handover records are
requested and RSS, Abis and/or MS Power control data are
specified.
This parameter applies only to the BSC.

Syntax

Change command strings

chg_element trace_msgs_before_ho <value> 0

Display command string

disp_element trace_msgs_before_ho 0

Values

Value type Integer (number of messages to be collected before a handover)

Valid range 0 to 8
Default value 5

6-930 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference trunk_critical_threshold

trunk_critical_threshold

Description

The trunk_critical_threshold parameter specifies the severity assignment of certain alarms.

The value of this parameter is a percentage of total trunk capacity.

A critical alarm is assigned when the percentage of trunk capacity loss exceeds the
trunk_critical_threshold parameter value. A major alarm is assigned when the percentage of
trunk capacity loss is greater than or equal to the trunk_major_threshold parameter value but
is less than the trunk_critical_threshold parameter value.

A trunk_critical_threshold value of 0 insures that Critical is always the severity assignment if

there is any capacity loss.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter must be greater than the value assigned to
the trunk_major_threshold parameter unless both values
are set to 0.
This parameter applies only to the BSC.

Syntax

Change command string

chg_element trunk_critical_threshold <value> 0

Display command string

disp_element trunk_critical_threshold 0

Values

Value type Integer (percent of trunk capacity)

Valid range 0 to 100
Default value 50

68P02901W23-T 6-931
Jan 2010
trunk_major_threshold Chapter 6: CM database parameters

trunk_major_threshold

Description

The trunk_major_threshold parameter specifies the severity assignment of certain alarms.

The value of this parameter is a percentage of total trunk capacity.

A major alarm is assigned when the percentage of trunk capacity loss exceeds the
trunk_major_threshold parameter value but is less than the trunk_critical_threshold
parameter value.

A minor alarm is assigned when the percentage of trunk capacity loss is less than the
trunk_major_threshold parameter value.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter must be less than the value assigned to the
trunk_critical_threshold parameter unless both values
are set to 0.
This parameter applies only to the BSC.

Syntax

Change command string

chg_element trunk_major_threshold <value> 0

Display command string

disp_element trunk_major_threshold 0

Values

Value type Integer (percent of trunk capacity)

Valid range 0 to 99
Default value 10

6-932 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ts_alloc_flag

ts_alloc_flag

Description

The ts_alloc_flag parameter alters the E1 timeslot allocation on links that are adjacent to
a ts_switch (pseudo site).

This parameter is only used when RSL or RTF devices are equipped.

Changing this parameter does not alter the timeslot mapping of RSLs and RTFs that are already
equipped; it affects the way timeslots are allocated for later equipped devices.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter cannot be altered unless the Aggregate Abis
feature is enabled.
This parameter applies only to the BSC.

Syntax

Change command string

chg_element ts_alloc_flag <value> 0

Whenever the ts_alloc_flag is modified the system displays this message:

COMMAND ACCEPTED: WARNING: This element only has effect on links to a TS_SWITCH

Display command string

disp_element ts_alloc_flag 0

68P02901W23-T 6-933
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Boolean

Valid range 0 or 1
0 Use existing algorithm
1 Use new algorithm
Default value 0

6-934 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ts_in_usf_active

ts_in_usf_active

Description

The ts_in_usf_active parameter specifies the maximum number of non-BCCH timeslots that
broadcast continuously at full power even when no MS is active on that timeslot.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The EOP feature must be unrestricted.
The number of non-BCCH timeslots that broadcasts
continuously at full power even when no mobile is active
on that timeslot.

Syntax

Change command strings

chg_element ts_in_usf_active <value> <location> <cell_desc>

chg_cell_element ts_in_usf_active <value> <cell_desc_opt>

Display command strings

disp_element ts_in_usf_active <location> <cell_desc>

Values

Value type Integer (number of non-BCCH timeslots)

Valid range 0 to 3
Default value 1

68P02901W23-T 6-935
Jan 2010
tsc_update_method Chapter 6: CM database parameters

tsc_update_method

Description

The tsc_update_method parameter specifies the method for updating timeslots when the
BSIC is changed. The available methods are:
Update the BCCH/CCCH timeslots.

Update all timeslots on the BCCH carrier.

Update all timeslots on all carriers of cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies No RTS are equipped (tsc_update_method must first be
set before RTFs can be equipped in the script). Equip RTF
verifies the TSC values based on this setting.
This parameter applies only to the BSC.

Syntax

Change command string

chg_element tsc_update_method <value> 0

Display command string

disp_element tsc_update_method 0

6-936 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 2
0 Update the BCCH/CCCH timeslots
1 Update all timeslots on the BCCH carrier
2 Update all timeslots on all carriers of cell
Default value 0

68P02901W23-T 6-937
Jan 2010
tx_integer Chapter 6: CM database parameters

tx_integer

Description

The tx_integer parameter specifies the number of Random Access Channel (RACH) slots
between the access retry transmission on the RACH.

Timer T3126 is used when an MS sends a Channel Request message.

From 3 to 50 RACH slots are used to spread the transmission.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element tx_integer <value> <location> <cell_desc>

chg_cell_element tx_integer <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element tx_integer <location> <cell_desc>

6-938 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 15
Represents RACH slots as shown below:

0 3 RACH 8 11 RACH
1 4 RACH 9 12 RACH
2 5 RACH 10 14 RACH
3 6 RACH 11 16 RACH
4 7 RACH 12 20 RACH
5 8 RACH 13 25 RACH
6 9 RACH 14 32 RACH
7 10 RACH 15 50 RACH

Default value 4

References

GSM parameter TX_INTEGER

GSM specification 4.08 - 3.3.1.1: request for resources by the MS
4.08 - 10.5.2.17 - fig. 10.36, and table 10.30
12.20 - 5.2.8.7 cell description - number of slots spread
trans

68P02901W23-T 6-939
Jan 2010
tx_power_cap Chapter 6: CM database parameters

tx_power_cap

Description

The tx_power_cap parameter specifies all cells within a site to be either low transmitting power
capable or high transmitting power capable. This parameter is valid only at DCS1800 and
PCS1900 sites, it is not valid for micro sites (although it is valid at Horizon II micro sites).

This parameter can be set when the primary outer zone frequency type of the cell is PGSM,
EGSM, DCS1800, and PCS1900 if the cell is a Dual Band Cell. If the cell is not, the frequency
must be DCS1800, or PCS1900 to change tx_power_cap.

For a PCS 1900 cell residing on a Horizonmacro or Horizonmacro extension cabinet, there
can be no DRIs equipped for that cell. If a DRI has already been equipped, any change of
that element is disallowed.

All DCS1800 DRI devices in Horizonmacro, Horizon II macro, Horizon II mini and Horizon II
micro master or extension cabinets are forced to operate in high power-capable mode (32 watts).

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter is valid only if the transceivers at the site
are inactive.
The system does not accept this parameter if the associated
DRIs are unlocked.
Operator actions Lock the associated DRIs before attempting to change this
parameter.

Syntax

Change command strings

chg_element tx_power_cap <value> <location> <cell_desc>

chg_cell_element tx_power_cap <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element tx_power_cap <location> <cell_desc>

6-940 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Boolean

Valid range 0 or 1
0 Low power
1 High power
Default value 0

68P02901W23-T 6-941
Jan 2010
udp_port Chapter 6: CM database parameters

udp_port

{26638}

Description

The udp_port parameter is an IP based NSVC parameter and identifies the UDP port of the
remote IP end point.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter can be modified only when the Gb over IP
feature is unrestricted and the Gb mode is set to static IP
mode.

Syntax

Add command strings

add_nsvc <location> <NS_VCI> <GBL_ID> if gb_mode is in the static IP mode.

add_nsvc <location> <NS_VCI> <GBL_ID> if gb_mode is in the frame relay mode.

Modify command strings

mod_nsvc <location> <NS_VCI>

Display command strings

disp_nsvc <NS_VCI> <nsvci_value>

disp_nsvc <location> <GBL> <gbl_value>

Delete command strings

del_nsvc <location> <nsvci_value>

6-942 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 65535
0 Minimum
65535 Maximum
Default value N/A

68P02901W23-T 6-943
Jan 2010
u_rxlev_dl_ih Chapter 6: CM database parameters

u_rxlev_dl_ih

Description

The u_rxlev_dl_ih parameter specifies the intra-cell control thresholds for the Receive (Rx)
level downlink. This parameter is evaluated in conjunction with the l_rxqual_dl_h to determine
whether an inter-cell or intra-cell is being requested.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter is used by the BSS only when
interfer_ho_allowed = 1.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element u_rxlev_dl_ih <value> <location> <cell_desc>

chg_cell_element u_rxlev_dl_ih <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element u_rxlev_dl_ih <location> <cell_desc>

Values

Value type Integer (1 step = 1 dBm)

Valid range 0 to 63 Represents -110 dBm to -47 dBm, as shown below:
0 -110 dBm
1 -109 dBm
2 -108 dBm
... ...
... ...

6-944 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

... ...
63 -47 dBm
Default value 45 -65 dBm

References

GSM parameter RXLEV_DL_IH

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-945
Jan 2010
u_rxlev_dl_p Chapter 6: CM database parameters

u_rxlev_dl_p

Description

The u_rxlev_dl_p parameter specifies the signal strength for the upper downlink limit of the
serving cell.

BTS transmit power may be reduced if the MS signal strength is greater than this value.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element u_rxlev_dl_p <value> <location> <cell_desc>

chg_cell_element u_rxlev_dl_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element u_rxlev_dl_p <location> <cell_desc>

Values

Value type Integer (1 step = 1 dBm)

Valid range 0 to 63 Represents -110 dBm to -47 dBm, as shown below:
0 -110 dBm or lower
1 -109 dBm
2 -108 dBm
... ...
... ...

6-946 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

... ...
63 -47 dBm or higher
Default value 40 -70 dBm

References

GSM parameter U_RXLEV_DL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-947
Jan 2010
u_rxlev_ul_ih Chapter 6: CM database parameters

u_rxlev_ul_ih

Description

The u_rxlev_ul_ih parameter specifies the intra-cell control thresholds for the upper Receive
(Rx) level uplink. This parameter is evaluated in conjunction with the l_rxqual_ul_h to
determine whether an inter-cell or intra-cell is being requested.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies This parameter is used by the BSS only when
interfer_ho_allowed is 1.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element u_rxlev_ul_ih <value> <location> <cell_desc>

chg_cell_element u_rxlev_ul_ih <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element u_rxlev_ul_ih <location> <cell_desc>

Values

Value type Integer (1 step = 1 dBm)

Valid range 0 to 63 Represents -110 dBm to -47 dBm, as shown below:
0 -110 dBm or lower
1 -109 dBm
2 -108 dBm
... ...
... ...

6-948 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

... ...
63 -47 dBm or higher
Default value 45 -65 dBm

References

GSM parameter RXLEV_UL_IH

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-949
Jan 2010
u_rxlev_ul_p Chapter 6: CM database parameters

u_rxlev_ul_p

Description

This parameter specifies the signal strength for the upper uplink limit of the serving cell.

Mobile transmit power may be reduced if the MS transmit signal strength is greater than
this value.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element u_rxlev_ul_p <value> <location> <cell_desc>

chg_cell_element u_rxlev_ul_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element u_rxlev_ul_p <location> <cell_desc>

Values

Value type Integer (1 step = 1 dBm)

Valid range 0 to 63 Represents -110 dBm to -47 dBm, as shown below:
0 -110 dBm or lower
1 -109 dBm
2 -108 dBm
... ...
... ...

6-950 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

... ...
63 -47 dBm or higher
Default value 40 -70 dBm

References

GSM parameter U_RXLEV_UL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-951
Jan 2010
u_rxqual_dl_p Chapter 6: CM database parameters

u_rxqual_dl_p

Description

The u_rxqual_dl_p parameter specifies the power control threshold for the best allowed
downlink receive quality (rxqual). The valid range and default values for this parameter are
dependent on the type of unit that is selected.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

An Rxqual value better (lower BER rate) than what is specified by the u_rxqual_ul_p parameter
may result the reduction of downlink power.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc
Since better rxqual corresponds to a lower bit error rate,
u_rxqual_dl_p should be less than l_rxqual_dl_p.
u_rxqual_dl_p must be less than l_rxqual_dl_p_amr_fr.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element u_rxqual_dl_p <value> <location> <cell_desc>

chg_cell_element u_rxqual_dl_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element u_rxqual_dl_p <location> <cell_desc>

6-952 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1810 BER If alt_qual_proc = 0
(1 step = 0.01% bit error
rate)
0 to 7 QBand units If alt_qual_proc = 1
Default value 28 BER If alt_qual_proc = 0
1 QBand units If alt_qual_proc = 1

NOTE
Dependencies affect the actual range, thus range is never set to 1810 BER (or 7
QBand).

References

GSM parameter U_RXQUAL_DL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-953
Jan 2010
u_rxqual_dl_p_hr Chapter 6: CM database parameters

u_rxqual_dl_p_hr

Description

The u_rxqual_dl_p_hr parameter specifies the power control threshold for the best allowed
downlink received quality (rxqual).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must be
unrestricted.
This parameter can be changed at any AMR/GSM HR
capable BTS site.
This parameter is prompted when alt_qual_proc is
changed.
This parameter must be greater than u_rxqual_dl_p_hr.

Syntax

Add/Change command strings

chg_element u_rxqual_dl_p_hr <value> <location> <cell_desc>

chg_cell_element u_rxqual_dl_p_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element u_rxqual_dl_p_hr <location> <cell_desc>

6-954 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate). If alt_qual_proc = 0
0 to 7 QBand units. If alt_qual_proc = 1
Default value 14 BER. If alt_qual_proc = 0
0 QBand units. If alt_qual_proc = 1

NOTE
Dependencies affect the actual range, thus range is never set to 1810 BER (or 7
QBand).

68P02901W23-T 6-955
Jan 2010
u_rxqual_ul_p Chapter 6: CM database parameters

u_rxqual_ul_p

Description

The u_rxqual_ul_p parameter sets the power control threshold for the best allowed uplink
receive quality (rxqual). The valid range and default values for this parameter are dependent
on the type of unit that is selected.

Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band
(QBand) units. The alt_qual_proc parameter specifies the type of unit.

An Rxqual value better (lower BER rate) than what is specified by the u_rxqual_ul_p parameter
may result the reduction of MS power.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies alt_qual_proc
Since better rxqual corresponds to a lower bit error rate,
u_rxqual_ul_p must be less than l_rxqual_ul_p.
u_rxqual_ul_p must be less than l_rxqual_ul_p_amr_fr.

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element u_rxqual_ul_p <value> <location> <cell_desc>

chg_cell_element u_rxqual_ul_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element u_rxqual_ul_p <location> <cell_desc>

6-956 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1810 BER If alt_qual_proc = 0
(1 step = 0.01% bit error
rate)
0 to 7 QBand units If alt_qual_proc = 1
Default value 28 BER If alt_qual_proc = 0
1 QBand units If alt_qual_proc = 1

NOTE
Dependencies affect the actual range, thus range is never set to 1810 BER (or 7
QBand).

References

GSM parameter U_RXQUAL_UL_P

GSM specification 5.08 - Appendix A - Table 1

68P02901W23-T 6-957
Jan 2010
u_rxqual_ul_p_hr Chapter 6: CM database parameters

u_rxqual_ul_p_hr

Description

The u_rxqual_ul_p_hr parameter specifies the power control threshold for the best allowed
uplink received quality (rxqual).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The AMR feature and/or the GSM Half Rate feature must
be unrestricted.
This parameter can be changed at any AMR/GSM HR
capable BTS site.
This parameter is prompted when alt_qual_proc is
changed.
This parameter must be less than u_rxqual_ul_p_hr.

Syntax

Add/Change command strings

chg_element u_rxqual_ul_p_hr <value> <location> <cell_desc>

chg_cell_element u_rxqual_ul_p_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

disp_element u_rxqual_ul_p_hr <location> <cell_desc>

6-958 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer

Valid range 0 to 1810 BER (1 step = 0.01% bit error rate). If alt_qual_proc = 0
0 to 7 QBand units. If alt_qual_proc = 1
Default value 14 BER. If alt_qual_proc = 0
0 QBand units. If alt_qual_proc = 1

NOTE
Dependencies affect the actual range, thus range is never set to 1810 BER (or 7
QBand).

68P02901W23-T 6-959
Jan 2010
ul_audio_lev_offset Chapter 6: CM database parameters

ul_audio_lev_offset

Description

The ul_audio_lev_offset parameter specifies the uplink volume control offset on a per BSS
basis. The offset is in 1 dB steps with a maximum increase or decrease of 30 dB (between
-15 dB and 15 dB).

Changes take effect immediately (including active calls).

The audio level parameters affect background and comfort noise. The audio level parameters do
not affect data.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The volume_control_type parameter controls the
ul_audio_lev_offset application. If volume_control_type
= 1, then the ul_audio_lev_offset parameter only applies
to sites equipped with GDP boards. The GDP firmware
controls the volume level by converting the audio level bits
for the entered offset.
This parameter applies only to the BSC.

Syntax

Change command string

chg_element ul_audio_lev_offset <value> 0

Display command strings

disp_element ul_audio_lev_offset 0

Values

Value type Integer (1 Step = 1 dB)

Valid range -15 to +15
Default value 0

6-960 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ul_rxlev_ho_allowed

ul_rxlev_ho_allowed

Description

The ul_rxlev_ho_allowed parameter enables or disables handovers due to the uplink receive
level (rxlev).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element ul_rxlev_ho_allowed <value> <location> <cell_desc>

chg_cell_element ul_rxlev_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ul_rxlev_ho_allowed <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

68P02901W23-T 6-961
Jan 2010
References Chapter 6: CM database parameters

References

Internal name EN_RXLEV_HO

This is a Motorola parameter.

6-962 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ul_rxqual_ho_allowed

ul_rxqual_ho_allowed

Description

The ul_rxqual_ho_allowed parameter enables or disables handovers due to the uplink receive
quality (rxqual).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element ul_rxqual_ho_allowed <value> <location> <cell_desc>

chg_cell_element ul_rxqual_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ul_rxqual_ho_allowed <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1

68P02901W23-T 6-963
Jan 2010
References Chapter 6: CM database parameters

References

Internal name EN_RXQUAL_HO

This is a Motorola parameter.

6-964 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference umts_band_preferred

umts_band_preferred

Description

The umts_band_preferred parameter indicates whether hand over to UTRAN band is preferred
or not. When set to 1, UTRAN band is preferred over any GSM band for the handover. When set
to 0, GSM band is preferred over any UTRAN band for the handover.

Type A (No operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Enhanced 2G/3G Handover feature must be
unrestricted to modify this parameter.

Syntax

Add/Change command strings

chg_element umts_band_preferred <value> <location> <cell_desc>

chg_cell_element umts_band_preferred <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element umts_band_preferred <location> <cell_desc>

Values

Value type Boolean

Valid range 0 to 1
0 GSM band preferred
1 UMTS band preferred
Default value 0

68P02901W23-T 6-965
Jan 2010
umts_cpich_ec_no_min Chapter 6: CM database parameters

umts_cpich_ec_no_min

Description

The umts_cpich_ec_no_min parameter is a threshold parameter used by the handover

algorithm when the fdd_rep_quant parameter is set to Ratio of Chip Energy to Power Spectral
Density (Ec/No).

Type A (No operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Enhanced 2G/3G Handover feature must be
unrestricted to modify this parameter.
The fdd_rep_quant parameter must be set to 1 (Ec/No).

Syntax

Add/Change command strings

chg_element umts_cpich_ec_no_min <value> <location> <cell_desc>

chg_cell_element umts_cpich_ec_no_min <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element umts_cpich_ec_no_min <location> <cell_desc>

Values

Value type Integer (dBm)

Valid range -20 to 0
Default value -15

6-966 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference umts_cpich_rscp_min

umts_cpich_rscp_min

Description

The umts_cpich_rscp_min parameter is a threshold parameter that is used by the handover

algorithm when the fdd_rep_quant parameter is set to Received Signal Code Power (RSCP).

Type A (No operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Enhanced 2G/3G Handover feature must be
unrestricted to modify this parameter.
The fdd_rep_quant parameter must be set to 0 (RSCP).

Syntax

Add/Change command strings

chg_element umts_cpich_rscp_min <value> <location> <cell_desc>

chg_cell_element umts_cpich_rscp_min <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element umts_cpich_rscp_min <location> <cell_desc>

Values

Value type Integer (dBm)

Valid range -115 to -53
Default value -90

68P02901W23-T 6-967
Jan 2010
unequipped_circuit_allowed Chapter 6: CM database parameters

unequipped_circuit_allowed

Description

The unequipped_circuit_allowed parameter specifies the system response when a terrestrial

circuit becomes unequipped. The options are:
Sending an alarm to the OMC-R.

Sending an unequipped circuit message to the MSC.

Sending both an alarm to the OMC-R and an unequipped circuit message to the MSC.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter does not apply to RXCDR sites.
The Phase 2 feature must be unrestricted.

Syntax

Change command string

chg_element unequipped_circuit_allowed <value> 0

Display command string

disp_element unequipped_circuit_allowed 0

Values

Value type Integer

Valid range 0 to 2
0 Send alarm to the OMC-R
1 Send unequipped circuit message to the MSC
2 Send alarm to the OMC-R and send unequipped circuit
message to the MSC
Default value 0

6-968 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM specification TS GSM 8.08

This is a Motorola defined parameter.

68P02901W23-T 6-969
Jan 2010
use_bcch_for_gprs Chapter 6: CM database parameters

use_bcch_for_gprs

Description

The use_bcch_for_gprs parameter specifies whether reserved and switchable GPRS timeslots
are allocated on a BCCH carrier.

The system prompts for this parameter when the gprs_enabled per-cell parameter is changed
to 1.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

Syntax

Change command string

chg_cell_element use_bcch_for_gprs <value> <cell_desc_opt>

Display command string

disp_element use_bcch_for_gprs <cell_desc>

Values

Value type Boolean

Valid range 0 to 1
0 Use BCCH Carrier for PDs as the last priority.
1 Use BCCH Carrier for PDs as the first priority.
Default value 1

6-970 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference use_derived_ho_power

use_derived_ho_power

Description

The use_derived_ho_power parameter specifies how the system manages the derived handover
power level for internal inter-cell handovers.

When kbit/s, these handovers use the power level in the database.

When enabled, these handovers use a power level derived from the rxlev reported by the MS for
the target cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element use_derived_ho_power <value> <location> <cell_desc>

chg_cell_element use_derived_ho_power <value> <cell_desc_opt>

Display command string

disp_element use_derived_ho_power <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0

68P02901W23-T 6-971
Jan 2010
use_neighbor_pbgt_hreqave Chapter 6: CM database parameters

use_neighbor_pbgt_hreqave

Description

The use_neighbor_pbgt_hreqave parameter indicates whether the per cell or per neighbor
hreqave is used for the pbgt>ho_margin trigger assignment.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element use_neighbor_pbgt_hreqave <value> <location> <cell_desc>

chg_cell_element use_neighbor_pbgt_hreqave <value> <cell_desc_opt>

Display command string

disp_element use_neighbor_pbgt_hreqave <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Per cell hreqave is used
1 Per neighbor hreqave is used
Default value 0

6-972 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference volume_control_type

volume_control_type

Description

The volume_control_type parameter enables or disables uplink and downlink Volume Control.
The volume can be changed at either an RXCDR or at a BSC. The effect depends on the
equipment configuration (GDPs or DRIs equipped), and the value of volume_control_type
to use DRIs (0) or GDP volume control (1).

Type B (operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Generic DSP Processor (GDP) Volume Control feature
must be available.
If volume_control_type is set to 1, the BSS must be
equipped with GDP boards, unless remote transcoding,
when RXCDR must contain a GDP board to serve the
BSS. CCDSP (Channel Coding Digital Signal Processor)
volume control cannot be directly initiated from an RXCDR.
(There are no DRIs at the RXCDR). However, by setting the
parameter to 0 at the BSC and at the RXCDR, CCDSP (DRI)
volume control is used in this BSS.
The parameters ul_audio_lev_offset
and dl_audio_lev_offset must be set to 0 before changing
volume_control_type.
This parameter applies only to the BSC.
Operator actions It is the responsibility of the network operator to
synchronize the values of
volume_control_type between the RXCDR and the BSC
for the desired control.

NOTE
For the BSC side, turn the parameter on with a chg_ele command.

chg_ele volume_control_type <value> = 0 where <value> is used to select CCDSP

volume control = 0 or GDP Volume control = 1.

To change these values at the RXCDR, use the modify_values command on the
ABSS device.

68P02901W23-T 6-973
Jan 2010
Syntax Chapter 6: CM database parameters

Syntax

Change command string

chg_element volume_control_type <value> 0

Display command string

disp_element volume_control_type 0

NOTE
The bss_id parameter is required in both the commands only at the RXCDR.

Values

Value type Boolean

Valid range 0 or 1
0 CCDSP Volume Control
1 GDP Volume Control
Default value 0

6-974 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference wait_for_reselection

wait_for_reselection

Description

The wait_for_reselection parameter specifies the length of time before choosing an MMS for
clock extraction after a GCLK has had a CLKX reference failure alarm. If the MMS providing
clock extraction is INS after the time period has expired, it is left as the clock extraction source.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element wait_for_reselection <value> <location>

Display command string

disp_element wait_for_reselection <location> <location>

Values

Value type Integer (seconds)

Valid range 0 to 86400
Default value 10

68P02901W23-T 6-975
Jan 2010
wait_indication_parameters Chapter 6: CM database parameters

wait_indication_parameters

Description

The wait_indication_parameters parameter specifies the MS timer (T3122).

For an MS origination with no channel available, the MS is sent an IMMEDIATE ASSIGNMENT

REJECT message in an unacknowledged mode on the CCCH. The message contains the request
reference and a wait indication. The MS does not make a new request in the same cell until the
timer expires.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Add/Change command strings

add_cell <gsm_cell_id> <location>

chg_element wait_indication_parameters <value> <location> <cell_desc>

chg_cell_element wait_indication_parameters <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element wait_indication_parameters <location> <cell_desc>

Values

Value type Integer (seconds)

Valid range 0 to 255
Default value 5

6-976 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

GSM specification 4.08 - 3.3.1.2.2: assignment rejection

4.08, - 10.5.2.24, figure 10.43, and table 10.37
4.08 - 11.1.1:
12.20 - 5.2.7.7 - Wait Indication
This is a Motorola defined parameter.

68P02901W23-T 6-977
Jan 2010
worse_neighbor_ho Chapter 6: CM database parameters

worse_neighbor_ho

Description

The worse_neighbor_ho parameter specifies whether a call can be handed over to a neighbor
cell due to the downlink receive level even when the neighbor cell receive level is lower than the
serving cell receive level.

This parameter affects only handovers due to downlink receive level.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element worse_neighbor_ho <value> <location> <cell_desc>

chg_cell_element worse_neighbor_ho <value> <cell_desc_opt>

Display command string

disp_element worse_neighbor_ho <location> <cell_desc>

Values

Value type Boolean

Valid range 0 or 1
0 Handover disabled
1 Handover enabled
Default value 0

6-978 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference zone_ho_hyst

zone_ho_hyst

Description

The zone_ho_hyst parameter specifies the margin for the inner zone handover hysteresis. The
system uses this value to determine whether an outer-zone to inner-zone handover should
take place.

A handover initiates when both the uplink and the downlink receive level averages are greater
than the sum of the respective uplink or downlink threshold defined for the inner zone plus
the per cell hysteresis for inter-zone handover plus the difference between the current
uplink/downlink transmit power and the maximum uplink/downlink transmit power of the inner
zone carrier:

RXLEV_DL > RXLEV_DL_ZONE + ZONE_HO_HYST + (BS_TXPWR - BS_TXPWR_MAX_INNER)

or

(RXLEV_UL > RXLEV_UL_ZONE + ZONE_HO_HYST + (MS_TXPWR - MS_TXPWR_MAX_IN-

NER)).

Type A (No operator actions required)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The Concentric Cells feature must be unrestricted.
The range depends on the value of inner_zone_alg:

Dual Band Cell: -63 to 63.

Not Dual Band: 0 to 30.

Syntax

Change command strings

chg_element zone_ho_hyst <value> <location> <cell_desc>

chg_cell_element zone_ho_hyst <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element zone_ho_hyst <location> <cell_desc>

68P02901W23-T 6-979
Jan 2010
Values Chapter 6: CM database parameters

Values

Value type Integer

Valid range 0 to 30 (Not Dual Band Cell)
-63 to 63 (Dual Band Cell)
Default value 0

6-980 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference zone_pingpong_count

zone_pingpong_count

Description

The zone_pingpong_count parameter counts the number of times that a zone

ping-pong handover is allowed during the continuous execution time window set by the
zone_pingpong_enable_win parameter (see zone_pingpong_enable_win on page 7-212).

This parameter can be changed when the operator is in RAM or Sysgen mode.

This parameter can only be modified at the BSC.

Type A (No operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command strings

chg_element zone_pingpong_count <value> 0

Display command strings

disp_element zone_pingpong_count 0

Values

Value type Integer (insteps of 1)

Valid range 0 to 255
Default value 3

68P02901W23-T 6-981
Jan 2010
zone_pingpong_preferred_zone Chapter 6: CM database parameters

zone_pingpong_preferred_zone

Description

The zone_pingpong_preferred_zone parameter indicates which zone is preferred as a hop

target zone.

This parameter can be changed when the operator is in RAM or Sysgen mode.

This parameter can only be modified at the BSC.

Type A (No operator actions required)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command strings

chg_element zone_pingpong_preferred_zone <value> 0

Display command strings

disp_element zone_pingpong_preferred_zone 0

Values

Value type Integer

Valid range 0, 1 or 255
0 Outer zone preferred
1 Inner zone preferred
255 Current zone (no preferred zone)
Default value 255

6-982 68P02901W23-T
Jan 2010
 Chapter

Timer parameters

Timer parameters are BSS parameters that can be displayed and changed using MMI
commands. The timers are used to monitor and set timer guards for the various software
processes in the BSS.

This chapter contains descriptions of the timer parameters used in the BSS, and indicates
the command syntax used to modify or display the parameter. The timer descriptions are in
alphabetical order as listed in the Contents section of this manual.

Each timer parameter is described separately using the following presentation layout:

Parameter reference - showing the timer parameter reference title.

Description - providing a description of the timer operation, and including information on the
parameter type, whether supported by OMC-R GUI, whether cell numbers are required, and
listing any dependencies affecting the timer.

Syntax - giving the change command and display command strings using the particular timer
parameter.

Values - giving the value type, valid range, and the default value for the particular timer
parameter.

References - giving any related information such as internal name, GSM name, and ITU/GSM
specification.

For more information about BSS timers, refer to the Maintenance Information: BSS Timers
(68P02901W58) manual.

68P02901W23-T 7-1
Jan 2010
add_access_class Chapter 7: Timer parameters

add_access_class

Description

The add_access_class timer specifies the guard time period between individual mobile access
classes to come into service. This permits MSs to access the system gradually.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element add_access_class <value> <location>

Display command string

disp_element add_access_class <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 60000

References

Internal name MTCRM_ADD_ACC_CLASS

This is a Motorola defined timer.

7-2 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference assign_successful

assign_successful

Description

The assign_successful timer causes a Clear Request message to be sent to the MSC when
it expires.

This timer starts when the BSC sends an assignment command to the BTS.

The bssmap_t1 timer controls how long a call remains queued when waiting for a resource. In
all cases, the bssmap_t1 timer must be less than the assign_successful timer. The reason for
this is that the assignment procedure fails when the assign_successful timer expires.

If this timer expires, the call terminates.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Change command string

chg_element assign_successful <value> <location>

Display command string

disp_element assign_successful <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

68P02901W23-T 7-3
Jan 2010
References Chapter 7: Timer parameters

References

Internal name SSM_MTN

This is a Motorola defined timer.

7-4 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference auto_dl_dur

auto_dl_dur

Description

The auto_dl_dur auto downlink duration BSS parameter sets the number of block periods for
which the network delays the release of a live downlink TBF. This TBF is created through the
auto downlink mechanism which is waiting for new downlink data to arrive.

One block period equals 20 ms.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

Syntax

Change command string

chg_element auto_dl_dur <value> <location>

Display command string

disp_element auto_dl_dur <location>

Values

Value type Integer (20 ms block periods)

Valid range 15 to 250
Default value 50

68P02901W23-T 7-5
Jan 2010
bcch_info Chapter 7: Timer parameters

bcch_info

Description

The bcch_info timer specifies the wait time for the Radio Subsystem (RSS) to hold an
information message for the BCCH System Information Messages from Call Processing (CP)
before sending the information message to the channel coders.

The information message is sent immediately if all necessary BCCH system information
messages are received depending on the mode being used.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bcch_info <value> <location>

Display command string

disp_element bcch_info <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 10000
Default value 2000

References

Internal name TM_BCCH_INFO

GSM specification TS GSM 04.08 - section 9.1.34.
This is a Motorola defined timer.

7-6 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bep_period

bep_period

Description

The bep_period parameter is used in an EGPRS cell to indicate the BEP (Bit Error Probability)
filter averaging period used for filtering channel quality measurements by the mobile.

NOTE
A BSS software process is notified whenever the bep_period element value is
changed.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The EGPRS feature must be unrestricted.

Syntax

Change command strings

chg_element bep_period <value> <location> <cell_desc>

chg_cell_element bep_period <value> <cel_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element bep_period <location> <cell_desc>

Values

Value type Integer (BEP filter averaging period)

Valid range 0 to 10
Default value 0 Eliminates forgetting factor 'e' from channel quality measurement
algorithms executed by the MS.

68P02901W23-T 7-7
Jan 2010
bep_period2 Chapter 7: Timer parameters

bep_period2

Description

The bep_period2 parameter is optionally used in an EGPRS cell to further indicate the BEP
(Bit Error Probability) filter averaging period used for filtering channel quality measurements
by the mobile.

The bep_period2 parameter is a forgetting factor for the mobile station to use when filtering
the Bit Error Probability. If this parameter is sent, the mobile station in the cell uses it, until
the mobile station in the same cell receives a new bep_period2, or the mobile station leaves
the cell or the MS enters packet idle mode.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The EGPRS feature must be unrestricted.

Syntax

Change command strings

chg_element bep_period2 <value> <location> <cell_desc>

chg_cell_element bep_period2 <value> <cel_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element bep_period2 <location> <cell_desc>

Values

Value type Integer (Secondary BEP filter averaging period)

Valid range 0 to 15
Default value 15 Allows normal filtering

7-8 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bounce_protect_cong_tmr

bounce_protect_cong_tmr

Description

The bounce_protect_cong_tmr timer specifies the number of SACCH periods after a

congestion handover that the system applies the bounce_protect_margin value.

This timer helps to prevent continuous handover bouncing between cells due to congestion.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element bounce_protect_cong_tmr <value> <location>

<cell_desc>chg_cell_element

bounce_protect_cong_tmr <value> <cell_desc>

Display command string

disp_element bounce_protect_cong_tmr <location> <cell_desc>

Values

Value type Integer (SACCH periods)

Valid range 0 to 255
0 Disabled
1 to 255 SACCH periods
Default value 0

68P02901W23-T 7-9
Jan 2010
bounce_protect_qual_tmr Chapter 7: Timer parameters

bounce_protect_qual_tmr

Description

The bounce_protect_qual_tmr timer specifies the number of SACCH periods after an RXQUAL
handover. The system applies the bounce_protect_margin value.

This timer helps to prevent continuous handover bouncing between cells due to RXQUAL
reasons.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element bounce_protect_qual_tmr <value> <location> <cell_desc>

chg_cell_element bounce_protect_qual_tmr <value> <cell_desc_opt>

Display command string

disp_element bounce_protect_qual_tmr <location> <cell_desc>

Values

Value type Integer (representing SACCH periods)

Valid range 0 to 127
0 Disabled
1 to 127 SACCH periods
Default value 0

7-10 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bsc_audit

bsc_audit

Description

The bsc_audit timer specifies how long the activity is monitored on a dedicated channel.

This timer starts when the call is not performing any connection-related processes at the BSC.

If this timer expires, the BSC sends an audit message to the BTS.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies Must be greater than bts_audit

Syntax

Change command string

chg_element bsc_audit <value> <location>

Display command string

disp_element bsc_audit <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 120000

References

Internal name SSM_MTV

This is a Motorola defined parameter.

68P02901W23-T 7-11
Jan 2010
bsc_audit_response Chapter 7: Timer parameters

bsc_audit_response

Description

The bsc_audit_response timer specifies the wait time for audit ssm call response from RRSM
timer.

This timer starts when the BSC sends an audit message to the BTS.

If the bsc_audit_response timer expires a specified number of times in a row without receiving
a response from the BTS, the BSC clears the call. The num_audit_retries parameter specifies
the number of timer expirations.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bsc_audit_response <value> <location>

Display command string

disp_element bsc_audit_response <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name SSMAUDIT_TIMER

This is a Motorola defined parameter.

7-12 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bss_overload_control

bss_overload_control

Description

The bss_overload_control parameter is an RSL Congestion Control (RCC) timer which defines
the BSS Overload message interval

It is recommended that this timer is set less than bssmap_t6 and greater than bssmap_t5at
the MSC.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies None

Syntax

Add/Change command strings

chg_element bss_overload_control <value> bsc

Display command strings

disp_element bss_overload_control bsc

Values

Value type Integer (milliseconds)

Valid range 1000 to
1000000
Default value 12500

68P02901W23-T 7-13
Jan 2010
bssgp_fc_period_c Chapter 7: Timer parameters

bssgp_fc_period_c

Description

The bssgp_fc_period_c timer specifies the rate at which the BSS is allowed to send flow control
messages for a given BVC or MS. The BSS may send a new Flow Control PDU every C seconds,
where C is a value which is predefined and common to the BSS SGSN.

The timer starts when the BSS sends a Flow Control PDU for a BVC or MS to the SGSN. When
the timer expires, the BSS may send another Flow Control PDU if the condition which caused
the sending of the PDU still exists.

If the BSS detects a missing FLOW-CONTROL-ACK from the SGSN and the condition which
causes the sending of FLOW-CONTROL PDU may be retransmitted immediately. In this case,
the BSS may violate the repetition rate defined by the C value.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is
made. That is, this parameter can be modified without a reset to a particular device
or function.

Syntax

Change command string

chg_element bssgp_fc_period_c <value> <location>

Display command string

disp_element bssgp_fc_period_c <location>

7-14 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (tenths of a second)

Valid range 10 to 100

10 1 second 1000 milliseconds

100 10 seconds 10000 milliseconds

Default value 10 (1 second)

References

GSM specification TS GSM 08.18 - Section 8.2.3.4

This is a Motorola defined timer.

68P02901W23-T 7-15
Jan 2010
bssgp_t1_timer Chapter 7: Timer parameters

bssgp_t1_timer

Description

The bssgp_t1_timer guards the BVC Blocking and Unblocking procedures between the BSS
and SGSN.

This timer is set when the BSS sends a BVC-BLOCK or BVC-UNBLOCK PDU to the SGSN.
This timer is cleared when the BSS receives the BVC-BLOCK or BVC-UNBLOCK-ACK PDU
from the SGSN.

If a BVC-BLOCK-ACK PDU is not received for a BVC-BLOCK PDU within bssgp_t1_timer

seconds, then the BVC-BLOCK PDU procedure is repeated a maximum of bssgp_block_retries
attempts. After the maximum attempts fail, the status of the BVC remains blocked, the
procedure is stopped, and GPRS status BVCI goes OOS.

If a BVC-UNBLOCK-ACK PDU is not received for a BVC-UNBLOCK PDU within

bssgp_t1_timer seconds, then the BVC-UNBLOCK PDU procedure is repeated a maximum of
bssgp_unblock_retries attempts. After the maximum attempts fail, the status of the BVC
remains blocked, the procedure is stopped, and GPRS status BVCI goes OOS.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is
made. That is, this parameter can be modified without a reset to a particular device
or function.

Syntax

Change command string

chg_element bssgp_t1_timer <value> <location>

Display command string

disp_element bssgp_t1_timer <location>

7-16 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (seconds)

Valid range 1 to 120
Default value 3

References

Internal name BSSGP T1

GSM specification TS GSM 08.18 - Section 8.3
This is a Motorola defined timer.

68P02901W23-T 7-17
Jan 2010
bssgp_t2_timer Chapter 7: Timer parameters

bssgp_t2_timer

Description

The bssgp_t2_timer guards the BVC Reset procedures between the BSS and SGSN.

This timer is set when the BSS sends a BVC-RESET to the SGSN. This timer is cleared when
the BSS receives the BVC-RESET-ACK from the SGSN. If the timer expires before an ACK is
received, the BVC Reset procedure is repeated a maximum number of bssgp_reset_retries
attempts. After the maximum attempts fail, the BVC remains blocked.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is
made. That is, this parameter can be modified without a reset to a particular device
or function.

Syntax

Change command string

chg_element bssgp_t2_timer <value> <location>

Display command string

disp_element bssgp_t2_timer <location>

7-18 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (seconds)

Valid range 1 to 120
Default value 60

References

GSM specification TS GSM 08.18 - Section 8.4

This is a Motorola defined timer.

68P02901W23-T 7-19
Jan 2010
bssgp_t4_timer Chapter 7: Timer parameters

bssgp_t4_timer

Description

The bssgp_t4_timer parameter guards the GPRS SUSPEND and RESUME procedures.

This timer is set when the RESUME PDU or SUSPEND PDU is sent out to SGSN. The timer is
cleared when the PCU receives RESUME ACK/NACK PDU or SUSPEND ACK/NACK PDU from
SGSN.

Type A (no operator actions)

Supported by OMC-R Yes

GUI
Cell description No
required
Dependencies The GPRS optional feature
must be unrestricted.

Syntax

Change command string

chg_element bssgp_t4_timer <value> <location>

Display command string

disp_element bssgp_t4_timer <location>

Values

Value type Integer (milliseconds)

Valid range 100 to 10000
Default value 800

7-20 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

3GPP specifications In Motorola BSS, bssgp_t4_timer is used for both

Suspend and Resume procedure.
In 3GPP TS 48.018 section 7.4 and 7.5, corresponding
timer is T3 and T4.

68P02901W23-T 7-21
Jan 2010
bssgp_t5_timer Chapter 7: Timer parameters

bssgp_t5_timer

Description

The bssgp_t5_timer guards the RA-CAPABILTY-UPDATE procedure.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

Syntax

Change command string

chg_element bssgp_t5_timer <value> <location>

Display command string

disp_element bssgp_t5_timer <location>

Values

Value type Integer

Valid range 1000 to 30000
Default value 3000

7-22 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bssgp_t6_timer

bssgp_t6_timer

Description

The bssgp_t6_timer guards the DOWNLOAD-BSS-PFC procedure.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.

Syntax

Change command string

chg_element bssgp_t6_timer <value> <location>

Display command string

disp_element bssgp_t6_timer <location>

Values

Value type Integer

Valid range 100 to 10000
Default value 3000

68P02901W23-T 7-23
Jan 2010
bssgp_t8_timer Chapter 7: Timer parameters

bssgp_t8_timer

Description

The bssgp_t8_timer is a PCU timer that guards the MODIFY-BSS-PFC procedure.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The QoS feature must be unrestricted.
The value of this parameter cannot be changed when
bssgp_pfc_bit equals 1.

Syntax

Change command string

chg_element bssgp_t8_timer <value> <location>

Display command string

disp_element bssgp_t8_timer <location>

Values

Value type Integer

Valid range 100 to 10000
Default value 3000

7-24 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bssmap_t1

bssmap_t1

Description

The bssmap_t1 timer specifies the wait time for a Blocking Acknowledge or Unblocking
Acknowledge from the MSC. The value set must allow enough time for the MSC to respond to
a Block/Unblock, even if the MSC is not in a state to respond immediately. A typical value
for this timer is 1000 milliseconds.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bssmap_t1 <value> <location>

Display command string

disp_element bssmap_t1 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name CLM_T1

GSM name T1
GSM specification 8.08 - 3.1.2
8.08 - 3.2.3: BSSMAP timers

68P02901W23-T 7-25
Jan 2010
bssmap_t4 Chapter 7: Timer parameters

bssmap_t4

Description

The bssmap_t4 timer specifies the wait time for return of the Reset Acknowledgment from
MSC. Set this timer to allow enough time for the BSS to recover from a global reset. A typical
value for this timer is 1000 milliseconds.

If this timer expires, it sends a Circuit Reset message and restarts the timer based on a
database parameter value.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bssmap_t4 <value> <location>

Display command string

disp_element bssmap_t4 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 50000

7-26 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Internal name CLM_T4

GSM name T4
GSM specification 8.08 - 3.2.3: BSSMAP timers
8.08 - 3.1.4.1.3.1: T4

68P02901W23-T 7-27
Jan 2010
bssmap_t7 Chapter 7: Timer parameters

bssmap_t7

Description

In an inter-BSS (external) handover, the BSC (SSM) timer bssmap_t7 guards against something
going wrong at the MSC with the handover that the BSC has triggered. The BSC responds to
the MSC and sets the timer to guard against non-receipt of the MSC approval to proceed with
the handover. If the timer expires before the HANDOVER COMMAND message is received from
the MSC, the result depends on the setting of the handover_recognized_period parameter.

The relationship between this parameter and the handover_recognized_period parameter is

described in Maintenance Information: BSS Timers (68P02901W58).

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bssmap_t7 <value> <location>

Display command string

disp_element bssmap_t7 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

7-28 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Internal name SSM_T7

GSM name T7
GSM specification 8.08 - 3.2.3: all BSSMAP timers
8.08 - 3.1.5, 3.1.5.1.1: T7

68P02901W23-T 7-29
Jan 2010
bssmap_t8 Chapter 7: Timer parameters

bssmap_t8

Description

The bssmap_t8 timer specifies the wait time for the receipt of a successful handover. This is
the sum of the time required for all messages to be sent to the mobile plus the time it takes to
access a target and come back, if necessary.

This timer starts at the source BTS when it is informed of an inter-cell handover.

If this timer expires, the BTS deallocates the old channel at the source cell.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bssmap_t8 <value> <location>

Display command string

disp_element bssmap_t8 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 28000

7-30 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Internal name RRSM_T8

GSM name T8
GSM specification 12.20 - 5.2.7.2 bss Map Timer In Bsc - bss Map T8: 4.08 -
Section 11
8.08 - 3.2.3: all RRSM timers

68P02901W23-T 7-31
Jan 2010
bssmap_t10 Chapter 7: Timer parameters

bssmap_t10

Description

The bssmap_t10 timer specifies the wait time for return assignment complete MS. Because the
bssmap_t10 timer is used twice in the system, it is considered to be a timer in cascade. Its
value corresponds to the lowest assigned value.

This timer starts when the BTS sends an Assignment Command to the MS.

If this timer expires, the call is terminated.

The recommended value is 13000 milliseconds.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bssmap_t10 <value> <location>

Display command string

disp_element bssmap_t10 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 28000

7-32 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Internal name RRSM_T10

GSM name T10
GSM specification 4.08 - Section 11
8.08 - 3.2.3: all RRSM timers.
Motorola implementation of RRSM_T10 is aligned with the
implementation of T3107 as specified in TS GSM 04.08,
section 3.4.3.3.

68P02901W23-T 7-33
Jan 2010
bssmap_t11 Chapter 7: Timer parameters

bssmap_t11

Description

The bssmap_t11 timer specifies the wait time for a queued resource request.

This timer starts when the BTS attempts to queue an Assignment Request.

This timer must be less than the assign_successful timer. A Clear Request message is sent to
the MSC when the assign_successful timer expires.

If this timer is greater than the assign_successful timer, the call queues for the length of time
specified by the assign_successful timer.

If this timer expires, the call terminates.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies Should be less than assign_successful

Syntax

Change command string

chg_element bssmap_t11 <value> <location>

Display command string

disp_element bssmap_t11 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 28000
Valid location BTS

7-34 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Internal name RRSM_T11

GSM name T11
GSM specification 4.08 - Section 11
8.08 - 3.2.3: all RRSM timers

68P02901W23-T 7-35
Jan 2010
bssmap_t13 Chapter 7: Timer parameters

bssmap_t13

Description

The bssmap_t13 timer specifies the wait time for the reset guard period at the BSS.

This timer starts when the Reset message from the MSC is received at the BSS.

Set this timer long enough to allow the BSS to clear all active processes after receiving a
reset from the MSC but not too long as to slow down recovery time. A typical value for this
timer is 1000 milliseconds.

If this timer expires, the BSS responds to the MSC with a Reset Acknowledgment.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bssmap_t13 <value> <location>

Display command string

disp_element bssmap_t13 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 40000

7-36 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference References

References

Internal name CLM_T13

GSM parameter T13
GSM specification 8.08 - 3.2.3: BSSMAP timers

68P02901W23-T 7-37
Jan 2010
bssmap_t19 Chapter 7: Timer parameters

bssmap_t19

Description

The bssmap_t19 timer specifies the wait time for a Reset Circuit Acknowledge from the MSC.
The value must allow the MSC enough time to respond to a BSC initiated Reset Circuit. A
typical value for this timer is 1000 milliseconds.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bssmap_t19 <value> <location>

Display command string

disp_element bssmap_t19 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name CLM_T19

GSM name T19
GSM specification GSM 8.08

7-38 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bssmap_t20

bssmap_t20

Description

The bssmap_t20 timer specifies the wait time for Circuit Group Blocking Ack or Circuit Group
Unblocking Ack from MSC. A typical value for this timer is 1000 milliseconds.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bssmap_t20 <value> <location>

Display command string

disp_element bssmap_t20 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name CLM_T20

GSM name T20
GSM specification GSM 8.08

68P02901W23-T 7-39
Jan 2010
bssmap_tqho Chapter 7: Timer parameters

bssmap_tqho

Description

The bssmap_tqho timer specifies the maximum allowed queuing time for a handover request.

This timer starts when the BSC queues the Handover Request.

If this timer expires, the system starts the MTB1 timer to wait for another handover request.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bssmap_tqho <value> <location>

Display command string

disp_element bssmap_tqho <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name SSM_TQHO

GSM name T_qho
GSM technical specification GSM 8.008

7-40 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bts_audit

bts_audit

Description

The bts_audit timer specifies the wait time for the audit timer for the state on dedicated
channel.

This timer starts when the call is not performing any connection-related processes at the BTS.

If this timer expires, the BTS initiates the audit.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies This parameter must be less than bsc_audit.

Syntax

Change command string

chg_element bts_audit <value> <location>

Display command string

disp_element bts_audit <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value The lesser value of 60000 or the bsc_audit timer minus 1

References

Internal name RRSM_MTW

GSM specification 4.08 - Section 11
8.08 - 3.2.3: all RRSM timers
This is a Motorola defined timer.

68P02901W23-T 7-41
Jan 2010
bts_audit_response Chapter 7: Timer parameters

bts_audit_response

Description

The bts_audit_response timer specifies the wait time for audit Radio Resource State Machine
(RRSM) call response from the SCCP State Machine (SSM).

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element bts_audit_response <value> <location>

Display command string

disp_element bts_audit_response <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 100000
Default value 30000

References

Internal name RRSM_AUDIT_TIMER

GSM specification 4.08 - Section 11
8.08 - 3.2.3: all RRSM timers
8.08 - 3.1
This is a Motorola defined parameter.

7-42 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference bts_escalation

bts_escalation

Description

The bts_escalation timer specifies how long the BTS can be out of communication with the
BSC before resetting.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies The parameter is only valid for a remote BTS site.

Syntax

Change command string

chg_element bts_escalation <value> <location>

Display command string

disp_element bts_escalation <location>

Values

Value type Integer (minutes)

Valid range 0, and 30 to 360 (0 indicates that the BTS does not reset due to loss of
communication with the BSC)
Default value 60

68P02901W23-T 7-43
Jan 2010
carrier_free_immediate Chapter 7: Timer parameters

carrier_free_immediate

Description

The carrier_free_immediate timer specifies the time allowed to free all channels on a carrier
when the channels must be freed immediately (regardless of state). This value should be eight
times greater than the value required to free a single timeslot.

This timer starts when the BTS attempts to deactivate a carrier. The timer stops when carrier
deactivation is completed.

If the timer expires, the BTS deallocates the carrier.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element carrier_free_immediate <value> <location>

Display command string

disp_element carrier_free_immediate <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 120000

References

Internal name MTCRM_CARRIER_FREE_IMMEDIATE

This is a Motorola defined timer.

7-44 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cbch_1

cbch_1

Description

The cbch_1 timer specifies the wait time for sending BCCH information for the newly activated
CBCH channel to the deactivation of the old CBCH.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element cbch_1 <value> <location>

Display command string

disp_element cbch_1 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name MTCRM_CBT1

This is a Motorola defined timer.

68P02901W23-T 7-45
Jan 2010
cbch_2 Chapter 7: Timer parameters

cbch_2

Description

The cbch_2 timer specifies the wait time for updating the CBCH response from RSS.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element cbch_2 <value> <location>

Display command string

disp_element cbch_2 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name MTCRM_CBT2

This is a Motorola defined timer.

7-46 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference cbch_3

cbch_3

Description

The cbch_3 timer specifies the wait time for the CBCH activation acknowledgment from RCI.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element cbch_3 <value> <location>

Display command string

disp_element cbch_3 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 35000

References

Internal name MTCRM_CBT3

This is a Motorola defined timer.

68P02901W23-T 7-47
Jan 2010
channel_act Chapter 7: Timer parameters

channel_act

Description

The channel_act timer specifies how long the Radio Subsystem (RSS) waits for a confirmation
from the channel coder after sending a CHAN_ACTIVATE request to the channel coders. This
request is sent to the channel coders to activate a channel.

A typical channel activation can take up to 5 seconds, depending on the activity at a BTS.

If this timer expires for a TCH the channel coder is taken out of service when it receives the
CHANNEL_ACTIVATION_ACK message from RSS.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element channel_act <value> <location>

Display command string

disp_element channel_act <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 10000
Default value 10000

References

Internal name TM_CHANNEL_ACT

This is a Motorola defined parameter.

7-48 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference channel_teardown

channel_teardown

Description

The channel_teardown timer specifies the wait time for channel teardown.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element channel_teardown <value> <location>

Display command string

disp_element channel_teardown <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 28000

References

Internal name RRSM_MTQ

GSM technical specification 4.08 - Section 11
8.08 - 3.2.3: all RRSM timers.

This is a Motorola defined parameter.

68P02901W23-T 7-49
Jan 2010
cipher_comp_ms Chapter 7: Timer parameters

cipher_comp_ms

Description

The cipher_comp_ms (and the ciphering_successful) parameters are guard timers that are
used to verify that expected messages are received. If an expected message is not received
within the specified time, the resources associated with the call are released.

This timer starts when the BTS is informed that the MSC is requesting a ciphering procedure.

When the MSC sends the cipher mode command to the BSC, it is sent to the SSM. The SSM
picks the encryption algorithm and sends it in a ciphering request to the RRSM. It then starts
the ciphering_successful timer.

When the RRSM receives the ciphering request, it sends a cipher mode command to the MS.
It then starts the cipher_comp_ms timer.

When the MS returns the Ciphering Mode Complete message to the RRSM, the
cipher_comp_ms timer is stopped and a ciphering successful message is sent to the SSM.

When the SSM receives the ciphering successful message, it stops the ciphering_successful
timer and sends the Cipher Mode Complete message to the MSC.

If the timer expires, however, the call terminates.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies The ciphering_successful parameter value must be
greater than the cipher_comp_ms parameter value.

Syntax

Change command string

chg_element cipher_comp_ms <value> <location>

Display command string

disp_element cipher_comp_ms <location>

7-50 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 28000

References

Internal name RRSM_MTA

GSM technical specification 4.08 - Section 11
8.08 - 3.2.3: all RRSM timers.

This is a Motorola defined parameter.

68P02901W23-T 7-51
Jan 2010
ciphering_successful Chapter 7: Timer parameters

ciphering_successful

Description

The ciphering_successful (and the ciphering_comp_ms) parameters are guard timers that
are used to verify that expected messages are received. If an expected message is not received
within the specified time, the resources associated with the call are released.

When the MSC sends the cipher mode command to the BSC, it is sent to the SSM. The SSM
picks the encryption algorithm and sends it in a ciphering request to the RRSM. It then starts
the ciphering_successful timer.

When the RRSM receives the ciphering request, it sends a ciphering mode command to the
MS. It then starts the cipher_comp_ms timer.

When the MS returns the Ciphering Mode Complete message to the RRSM, the
cipher_comp_ms timer is stopped and a ciphering successful message is sent to the SSM.

When the SSM receives the ciphering successful message, it stops the ciphering_successful
timer and sends the Cipher Mode Complete message to the MSC.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies The ciphering_successful parameter value must be
greater than the cipher_comp_ms parameter value.

Syntax

Change command string

chg_element ciphering_successful <value> <location>

Display command string

disp_element ciphering_successful <location>

7-52 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name SSM_MTI

This is a Motorola defined parameter.

68P02901W23-T 7-53
Jan 2010
circuit_reset_ack Chapter 7: Timer parameters

circuit_reset_ack

Description

The circuit_reset_ack timer specifies the wait time for the circuit reset acknowledgment from
internal subsystems. A typical value for this timer is 1000 milliseconds.

This is not a BSSAP timer.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element circuit_reset_ack <value> <location>

Display command string

disp_element circuit_reset_ack <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 70000

References

Internal name CLM_MTA1

This is a Motorola defined timer.

7-54 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference clear_cmd_ext_ho

clear_cmd_ext_ho

Description

The clear_cmd_ext_ho timer specifies the wait time for the clear command from the MSC
when the MSC sends a Handover command.

In an external (inter-BSS) handover, the BSC (SSM) timer clear_cmd_ext_ho guards for the
original channel being released by the MSC after a successful handover, or a lost MS during
handover.

Set the clear_cmd_ext_ho timer long enough to ensure that the MS has enough time in the
worst case to receive the handover command, attempt to access the target cell, and in failure,
to recover back to the source cell.

Also set the clear_cmd_ext_ho timer long enough to hold the original channel at the source
cell such that in failure to access the target channel, the MS can recover to the old channel
(longer than bssmap_t8).

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This timer is valid only for the BSC.

Syntax

Change command string

chg_element clear_cmd_ext_ho <value> 0

Display command string

disp_element clear_cmd_ext_ho 0

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

68P02901W23-T 7-55
Jan 2010
clear_command Chapter 7: Timer parameters

clear_command

Description

The clear_command timer specifies the wait time for the clear command from the MSC.

This timer starts when the BSC sends the Clear request.

If the timer expires, the call terminates.

Since the introduction of the clear_cmd_ext_ho timer, the clear_command timer has no
relationship with the bssmap_t8 timer.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element clear_command <value> <location>

Display command string

disp_element clear_command <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name SSM_MTG

This is a Motorola defined parameter.

7-56 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference dealloc_inact

dealloc_inact

Description

The dealloc_inact timer specifies the wait time for the deallocation of a channel for which a
fatal error indication has been received from the BSS. The channel is held for the specified
time in case the connection recovers.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element dealloc_inact <value> <location> <cell_desc>

chg_cell_element dealloc_inact <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element dealloc_inact <location> <cell_desc>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value None

References

Internal name MTCRM_DEALLOC_INACT

This is a Motorola defined timer.

68P02901W23-T 7-57
Jan 2010
delay_dl_rel_dur Chapter 7: Timer parameters

delay_dl_rel_dur

Description

The delayed downlink Temporary Block Flow (TBF) release duration BSS parameter,
delay_dl_rel_dur, sets the number of block periods for which the network delays the release of
a downlink TBF.

One block period equals 20 ms.

Type A (no operator actions)

Supported by OMC-R GUI Yes (Read-Write)
Cell description required No
Dependencies The GPRS feature must be unrestricted.

Syntax

Change command strings

chg_element delay_dl_rel_dur <value> <location>

Display command strings

disp_element delay_dl_rel_dur <location>

Values

Value type Integer (20 ms block periods)

Valid range 15 to 600 Number of block periods in which the network delays
the release of a downlink TBF.
Default value 50 (1000 ms)

7-58 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference delay_ul_rel_dur

delay_ul_rel_dur

Description

The delay_ul_rel_dur parameter is used to configure the delayed uplink Temporary Block
Flow (TBF) release duration.

The delay_ul_rel_dur parameter is configurable on a per BSS basis.

Type A
Supported by OMC-R GUI Yes
Cell description required No
Dependencies GPRS must be unrestricted.
Operator actions None

Syntax

Add/Change command strings

chg_element delay_ul_rel_dur <value> <location>

Display command strings

disp_element delay_ul_rel_dur <location>

Values

Value type Integer (20 ms block period)

Valid range 0 to 50 Number of block periods in which the network delays the
release of an uplink TBF.
Default value 18 (360 ms).

68P02901W23-T 7-59
Jan 2010
downlink_sync_timer Chapter 7: Timer parameters

downlink_sync_timer

Description

The downlink_sync_timer parameter specifies the wait time a Channel Coder Unit (CCU)
allows for the downlink TRAU Sync to be lost during a call before generating an error indication.

The loss of downlink TRAU Sync in this case should not be due to receiving the idle pattern or
the urgent alarm pattern

The BSS allows the values of the initial_sync_timer, downlink_sync_timer,

uplink_sync_timer and static_sync_timer to be modified so that only one site reset is required
for all to be changed.

The GPRS feature restricts the modifications of the gprs_alarm_time period, gci_error_inc,
gci_error_gen_threshold, gci_error_clr_threshold and static sync timer parameters.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This parameter is not allowed at a stand-alone BSC or a
stand-alone RXCDR. It can be used at a BTS.

Syntax

Change command string

chg_element downlink_sync_timer <value> <location>

NOTE
A site reset occurs when the value of downlink_sync_timer changes and the system
is in SYSGEN OFF mode. Resetting the site generates several alarms. However,
the system blocks these alarms.

Display command string

disp_element downlink_sync_timer <location>

7-60 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (milliseconds)

Valid range 1000 to 3000
Default value 1000

68P02901W23-T 7-61
Jan 2010
dynet_retry_time Chapter 7: Timer parameters

dynet_retry_time

Description

The dynet_retry_time timer specifies the amount of time that the BTS waits for a response from
the BSC when the BTS requests a terrestrial backing source. The value for this timer depends
on whether satellites are used to connect the BSC to the BTS.
Systems that do not use satellites should use the minimum retry value of 150 milliseconds.

Satellite systems should use a value 1.2 seconds greater, such as 1.35 seconds. Satellites
provide a one-way delay of 600 milliseconds.

The retry value affects call setup and handover times. The BTS makes three requests for a
terrestrial backing resource. Hence, a setting of 1.35 seconds for the retry time requires 4.05
seconds before the BTS stops attempting to allocate resources. At that point, the BTS cannot
allocate a TCH due to the lack of a terrestrial backing resource.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies This parameter is not available unless the containing site is
configured to support Dynamic Allocation and this option is
in operation.
The parameter is invalid for the BSC (location 0).

Syntax

Change command string

chg_element dynet_retry_time <value> <location> <cell_desc>

Display command string

disp_element dynet_retry_time <location> <cell_desc>

7-62 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference Values

Values

Value type Integer (milliseconds)

Valid range 150 to 3000
Default value 150

68P02901W23-T 7-63
Jan 2010
early_classmark_delay Chapter 7: Timer parameters

early_classmark_delay

Description

The early_classmark_delay timer specifies how long the BSS delays sending the Classmark
Update message to the MSC during Early Classmark sending.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Multiband Inter-cell Handover feature must be enabled.
This parameter can only be viewed at the BSC.

Syntax

Change command string

chg_element early_classmark_delay <value> 0

Display command string

disp_element early_classmark_delay 0

Values

Value type Integer (milliseconds)

Valid range 0 to 100000
Default value 0

References

GSM specification GSM TS 8.08 Section 3.1.13.

This is a Motorola defined parameter

7-64 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference emerg_reserved

emerg_reserved

Description

The emerg_reserved timer specifies how long a TCH is reserved for an emergency call access.
The TCH becomes reserved after an existing call is torn down due to the lack of TCHs at the
time of an emergency call access.

If emergency call preemption is enabled, traffic channels are reserved for emergency calls
waiting on SDCCHs. If idle channels are not available, existing normal calls may be torn down
to make TCHs available for the emergency calls.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element emerg_reserved <value> <location>

Display command string

disp_element emerg_reserved <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 120000

References

Internal name MTCRM_EMERG_RESERVED

This is a Motorola defined timer.

68P02901W23-T 7-65
Jan 2010
ext_ho_allocation Chapter 7: Timer parameters

ext_ho_allocation

Description

The ext_ho_allocation timer specifies the wait time for handover allocation.

This timer starts when the MSC sends a Handover Request to the BSC.

If this timer expires, the handover terminates.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element ext_ho_allocation <value> <location>

Display command string

disp_element ext_ho_allocation <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name SSM_MTC1

This is a Motorola defined parameter.

7-66 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ext_rtry_cand_prd

ext_rtry_cand_prd

Description

The ext_rtry_cand_prd timer specifies the time between successive attempts for a given source
cell to attempt an inter-BSS handover to a target cell which had previously rejected a handover
attempt because of congestion.

When a handover is rejected because of congestion, the source BSS does not attempt to
perform an imperative handover to that particular cell during the length of time specified by
ext_rtry_cand_prd.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies The Congestion Relief feature must be enabled.
The inter_cell_handover_allowed parameter must be
enabled for ECR functionality to work properly.

Syntax

Change command strings

chg_element ext_rtry_cand_prd <value> <location> <cell_desc>

chg_cell_element ext_rtry_cand_prd <value> <cell_desc_opt>

Display command string

disp_element ext_rtry_cand_prd <location> <cell_desc>

Values

Value type Integer (milliseconds)

Valid range 1 to 1000000
Default value 4000

68P02901W23-T 7-67
Jan 2010
flow_control_t1 Chapter 7: Timer parameters

flow_control_t1

Description

The flow_control_t1 timer specifies the wait time before the Flow Control mechanism considers
new overload messages.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies The flow_control_t1 value must be at least 1000
milliseconds less than the flow_control_t2 value.

Syntax

Change command strings

chg_element flow_control_t1 <value> <location> <cell_desc>

chg_cell_element flow_control_t1 <value> <cell_desc_opt>

Display command string

disp_element flow_control_t1 <location> <cell_desc>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 20000

References

Internal name MTCRM_FC_T1

GSM name FC_T1
GSM specification 8.58 - 6.3

7-68 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference flow_control_t2

flow_control_t2

Description

The flow_control_t2 timer specifies the wait time before a previously flow control barred
access class is brought back in service.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required Yes
Dependencies The flow_control_t1 value must be at least 1000
milliseconds less than the flow_control_t2 value.

Syntax

Change command strings

chg_element flow_control_t2 <value> <location> <cell_desc>

chg_cell_element flow_control_t2 <value> <cell_desc_opt>

Display command string

disp_element flow_control_t2 <location> <cell_desc>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name MTCRM_FC_T2

GSM name FC_T2
GSM specification 8.58 - 6.3

68P02901W23-T 7-69
Jan 2010
gbl_thrput_period Chapter 7: Timer parameters

gbl_thrput_period

Description

The gbl_thrput_period timer specifies the time period to compute the statistics
GBL_UL_DATA_THRPUT and GBL_DL_DATA_THRPUT. These statistics indicate the throughput
of a GBL uplink and downlink.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is
made. That is, this parameter can be modified without a reset to a particular device
or function.

Syntax

Change command string

chg_element gbl_thrput_period <value> PCU

Display command string

disp_element gbl_thrput_period PCU

Values

Value type Integer (tenths of a second)

Valid range 1 to 255
Default value 50

7-70 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_penalty_time

gprs_penalty_time

Description

The gprs_penalty_time timer specifies the length of time for which the parameter
gprs_temporary_offset is active for a cell.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The PBCCH/PCCH feature must be unrestricted.

Syntax

Change command strings

chg_cell_element gprs_penalty_time <value> <location> <cell_desc_opt>

chg_element gprs_penalty_time <value> <cell_desc>

Display command strings

disp_cell <cell_id> full

disp_element gprs_penalty_time <cell_desc>

Values

Value type Integer

Valid range 0 to 31
0 10 seconds
1 20 seconds
2 30 seconds
... ...
29 300 seconds
30 310 seconds
31 320 seconds
Default value 0 10 seconds

68P02901W23-T 7-71
Jan 2010
gprs_smg30_t3192 Chapter 7: Timer parameters

gprs_smg30_t3192

Description

The gprs_smg30_t3192 timer specifies the MS timers used by the BTS on the BCCH blocks. It
specifies the time that the MS continues the assigned PDCHs after receiving its last data block
and before it returns to monitoring its paging groups.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.
If the parameter smg_gb_vers is less than or equal to 30,
then it is used. Otherwise, gprs_t3192 is used.

Syntax

Change command strings

chg_element gprs_smg30_t3192 <value> <location> <cell_desc>

chg_cell_element gprs_smg30_t3192 <value> <cell_desc_opt>

Display command string

disp_cell_element gprs_smg30_t3192 <cell_desc>

Values

Value type Select integer (milliseconds)

Valid range 500, 1000, 2000, and 4000
Default value 500

7-72 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference gprs_t3168

gprs_t3168

Description

The gprs_t3168 timer specifies the MS timers used by the BTS on the BCCH blocks. This
parameter specifies the wait time for the MS waits to get a Packet Uplink Assignment after
sending a Packet Resource Request.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

Syntax

Change command strings

chg_element gprs_t3168 <value> <location> <cell_desc>

chg_cell_element gprs_t3168 <value> <cell_desc_opt>

Display command string

disp_element gprs_t3168 <location> <cell_desc>

Values

Value type Select integer (milliseconds)

Valid range 500, 1000, 2000, and 4000
Default value 4000

68P02901W23-T 7-73
Jan 2010
gprs_t3192 Chapter 7: Timer parameters

gprs_t3192

Description

The gprs_t3192 timer specifies the MS timers used by the BTS on BCCH blocks. This
parameter specifies the time that the MS continues the assigned PDCHs after receiving its last
data block and before it returns to monitoring its paging groups.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies The GPRS feature must be unrestricted.

Syntax

Change command strings

chg_element gprs_t3192 <value> <location> cell_desc>

chg_cell_element gprs_t3192 <value> <cell_desc_opt>

Display command string

disp_element gprs_t3192 <location> <cell_desc>

Values

Value type Select integer (milliseconds)

Valid range 0, 80, 120, 160, 200, 500, 1000, and 1500
Default value 500

7-74 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference handover_recognized_period

handover_recognized_period

Description

In an inter-BSS (external) handover, the handover_recognized_period parameter specifies

the per cell periodicity timer that gives the minimum period between handover attempts for
a BTS queuing for handover. It sets the minimum period between internal BTS handover
messages being generated and that result in a HANDOVER REQUIRED message being sent
from the BSS to the MSC.

To set this threshold, enable call queuing and the following equation must be true: h_interval
less than handover_recognized_period (T_hand_rqd at the MSC). The MSC parameter
h_interval specifies how long a handover request message remains queued by the MSC. The
MSC timer T_hand_rqd has the same function as handover_recognized_period.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies Call queuing must be enabled.
MSC h_interval < handover_recognized_period

Syntax

Add/Change command strings

add_cell <gsm_cell_desc> <location>

chg_element handover_recognized_period <value> <location> <cell_desc>

chg_cell_element handover_recognized_period <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element handover_recognized_period <location> <cell_desc>

68P02901W23-T 7-75
Jan 2010
Values Chapter 7: Timer parameters

Values

Value type Integer (SACCH multiframes)

Valid range 2 to 64 (even values only)
Default value 2

References

GSM parameter T_HAND_RQD

GSM specification 5.08 - Appendix A - 6
8.08 - 3.1.17.2, and 3.2.3: Tqho
12.20 - 5.2.8.4 - Adjacent Cell Handover - t_hand_rqd.

7-76 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ho_ack

ho_ack

Description

In an intra-cell handover, the ho_ack timer specifies the wait time for the BTS/BSC assignment
of the target handover channel. If this timer expires before this assignment, the handover
attempt fails, the newly assigned channel is freed, and a new handover procedure has to start.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element ho_ack <value> <location> <cell_desc>

chg_cell_element ho_ack <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full]

disp_element ho_ack <location> <cell_desc>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 5000

References

Internal name MTCRM_HANDOVER_ACK

This is a Motorola defined timer.

68P02901W23-T 7-77
Jan 2010
ho_allocation Chapter 7: Timer parameters

ho_allocation

Description

The ho_allocation timer specifies the wait time for handover allocation from destination cell
RRSM.

The system starts this timer when the BSC requests a resource from the BTS to perform an
intra-BSS handover.

If this timer expires, the handover terminates.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element ho_allocation <value> <location>

Display command string

disp_element ho_allocation <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name SSM_MTK

This is a Motorola defined timer.

7-78 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ho_complete

ho_complete

Description

The ho_complete timer specifies the wait time for handover complete from an MS on the
target cell.

This timer starts when the BTS attempts to assign a channel for a handover. If this timer
expires, the handover terminates.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element ho_complete <value> <location>

Display command string

disp_element ho_complete <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 28000

References

Internal name RRSM_MTD

GSM specification 4.08 - Section 11
8.08 - 3.2.3: all RRSM timers
This is a Motorola defined timer.

68P02901W23-T 7-79
Jan 2010
ho_request Chapter 7: Timer parameters

ho_request

Description

The ho_request timer specifies the wait time for handover request from the MSC after the
SCCP connection is established.

This timer starts when the MSC sends an empty CR to the BTS and the BTS informs the BSC. If
this timer expires, the handover terminates.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element ho_request <value> <location>

Display command string

disp_element ho_request <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name SSM_MTB1

This is a Motorola defined timer.

7-80 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference ho_successful

ho_successful

Description

The ho_successful parameter specifies the wait time for handover complete from target cell
Radio Resource State Machine (RRSM).

The system starts this timer when the handover_request_ack message is sent to the MSC. If
this timer expires, the call terminates.

Type A (no operator actions)

Supported by OMC-R GUI No
Cell description required No
Dependencies None

Syntax

Change command string

chg_element ho_successful <value> <location>

Display command string

disp_element ho_successful <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

Internal name SSM_MTJ

This is a Motorola defined timer.

68P02901W23-T 7-81
Jan 2010
hop_count_timer Chapter 7: Timer parameters

hop_count_timer

Description

The hop_count _timer specifies the number of SACCH periods for which intra-cell interference
handovers are counted.

The hop_count_timer works with both the hop_count and the hr_fr_hop_count parameters to
limit the number of intra-cell interference handovers. If the number of handovers defined by the
hop_count parameter occur within the time set by the hop_count_timer, the system escalates
the handover to an RXQUAL handover to another cell. If the number of quality/interference
handovers from Half Rate (HR) to Full Rate (FR) defined by the hr_fr_hop_count parameter
occur within the time set by hop_count_timer, the system keeps the mobile on the FR channel
if it is a candidate for FR to HR reconfiguration due to congestion.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required Yes
Dependencies None

Syntax

Change command strings

chg_element hop_count_timer <value> <cell_desc>

chg_cell_element hop_count_timer <value> <cell_desc_opt>

Display command string

disp_element hop_count_timer <cell_desc>

Values

Value type Integer (SACCH periods)

Valid range 0 to 255 A value of 0 disables this feature.
Default value 0

7-82 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference initial_sync_timer

initial_sync_timer

Description

The initial_sync_timer specifies the wait time for a Channel Coder Unit (CCU) to receive
the initial downlink Transcoding and Rate Adaption Unit (TRAU) frame before generating
an error indication.

The BSS allows the values of the initial_sync_timer, downlink_sync_timer,

uplink_sync_timer and static_sync_timer to be modified so that only one site reset is required
for all to be changed.

The GPRS feature restricts the modifications of the gprs_alarm_time period, gci_error_inc,
gci_error_gen_threshold, gci_error_clr_threshold and static sync timer parameters.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies This timer is not allowed at a stand-alone BSC or RXCDR. It
can be used at a BTS.
The initial_sync_timer is valid only at BTS sites.

NOTE
A site reset occurs when the value of initial_sync_timer is changed in SYSGEN OFF
mode. Resetting the site generates several alarms. However, the system blocks
these alarms.

Syntax

Change command string

chg_element initial_sync_timer <value> <location>

Display command string

disp_element initial_sync_timer <location>

68P02901W23-T 7-83
Jan 2010
Values Chapter 7: Timer parameters

Values

Value type Integer (1 step = 1 millisecond)

Valid range 1500 to 7000
Default value 4000 (4 seconds)

7-84 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_bssmap_t4

lb_int_bssmap_t4

Description

The lb_int_bssmap_t4 (Lb-interface BSSMAP T4) timer guards the time allowed for the
BSS-based SMLC to respond to a RESET message with a RESET ACKNOWLEDGE message.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_bssmap_t4 <value> <location>

Display command string

disp_element lb_int_bssmap_t4 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 50000

68P02901W23-T 7-85
Jan 2010
lb_int_bssmap_t13 Chapter 7: Timer parameters

lb_int_bssmap_t13

Description

The lb_int_bssmap_t13 (Lb-interface BSSMAP T13) timer is the reset guard timer. The system
starts this timer when the reset message from the BSS-based SMLC is received at the BSS.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_bssmap_t13 <value> <location>

Display command string

disp_element lb_int_bssmap_t13 <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 40000

References

GSM specification GSM 8.08-3.2.3

7-86 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_clear_command

lb_int_clear_command

Description

The lb_int_clear_command (Lb-interface clear command) timer is the wait for clear
command from the BSS-based SMLC timer.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_clear_command <value> <location>

Display command string

disp_element lb_int_clear_command <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

68P02901W23-T 7-87
Jan 2010
lb_int_sccp_released Chapter 7: Timer parameters

lb_int_sccp_released

Description

The lb_int_sccp_released (Lb-interface SCCP released) timer is the wait for SCCP released
message from BSS-based SMLC timer.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change timer

chg_element lb_int_sccp_released <value> <location>

Display timer

disp_element lb_int_sccp_released <location>

Values

Value type Integer (millisecond)

Valid range 0 to 1000000
Default value 30000

7-88 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_sccp_tconn_est

lb_int_sccp_tconn_est

Description

The lb_int_sccp_tconn_est timer specifies the amount of time to wait for the SCCP connection
confirmation from the BSS-based SMLC.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_sccp_tconn_est <value> <location>

Display command string

disp_element lb_int_sccp_tconn_est <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

68P02901W23-T 7-89
Jan 2010
lb_int_sccp_tiar Chapter 7: Timer parameters

lb_int_sccp_tiar

Description

The lb_int_sccp_tiar timer is the receive inactivity control timer for the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.
The value of this parameter should be greater than the
lb_int_sccp_tias parameter value.
The value of this parameter should be greater than the
value of the sccp_tiar at the BSS-based SMLC

Syntax

Change command string

chg_element lb_int_sccp_tiar <value> <location>

Display command string

disp_element lb_int_sccp_tiar <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

GSM specification GSM 8.08-3.23

7-90 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_sccp_tias

lb_int_sccp_tias

Description

The lb_int_sccp_tias timer is the send activity control timer for the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.
The value of this parameter should be less than the
lb_int_sccp_tiar parameter value.

Syntax

Change command string

chg_element lb_int_sccp_tias <value> <location>

Display command string

disp_element lb_int_sccp_tias <location>

Values

Value type Integer (milliseconds)

Valid range 0 to 1000000
Default value 30000

References

GSM specification GSM 8.08-3.23

68P02901W23-T 7-91
Jan 2010
lb_int_sccp_trel Chapter 7: Timer parameters

lb_int_sccp_trel

Description

The lb_int_sccp_trel timer is the wait for SCCP release complete timer for the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_sccp_trel <value> <location>

Display command string

disp_element lb_int_sccp_trel <location>

Values

Value type Integer (milliseconds)

Valid range 4000 to 15000
Default value 10000

References

GSM specification This is a Motorola defined timer.

7-92 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_spi

lb_int_spi

Description

The lb_int_spi timer specifies the amount of time the BSS must wait before initiating an internal
reset after either SubSystem Prohibited (SSP) or SPI has occurred over the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_spi <value> <location>

Display command string

disp_element lb_int_spi <location>

Values

Value type Integer (milliseconds)

Valid range 10000 to 1000000
Default value 60000

References

GSM specification GSM 8.08 - 3.1.15

This is a Motorola defined timer.

68P02901W23-T 7-93
Jan 2010
lb_int_ss7_l2_t1 Chapter 7: Timer parameters

lb_int_ss7_l2_t1

Description

The lb_int_ss7_l2_t1 (Lb-interface MTP layer 2 T1) timer is the alignment ready timer
associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.
The valid ranges for this element are dependent upon the
value of the ss7_mode.

Syntax

Change command string

chg_element lb_int_ss7_l2_t1 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t1 <location>

Values

Value type Integer (milliseconds)

Valid range ss7_mode = 0: 40000 to 50000
ss7_mode = 1: 13000 to 30000
Default value ss7_mode = 0: 50000
ss7_mode =1: 13000

References

ITU specification CCITT Q.703

7-94 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_ss7_l2_t2

lb_int_ss7_l2_t2

Description

The lb_int_ss7_l2_t2 (Lb-interface MTP layer 2 T2) timer is the not aligned timer associated
with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.
The valid ranges for this element are dependent upon the
value of the ss7_mode.

Syntax

Change command string

chg_element lb_int_ss7_l2_t2 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t2 <location>

Values

Value type Integer (millisecond)

Valid range ss7_mode = 0: 5000 to 150000
ss7_mode = 1: 5000 to 30000
Default value ss7_mode = 0: 25000
ss7_mode =1: 23000

References

ITU specification CCITT Q.703

68P02901W23-T 7-95
Jan 2010
lb_int_ss7_l2_t3 Chapter 7: Timer parameters

lb_int_ss7_l2_t3

Description

The lb_int_ss7_l2_t3 (Lb-interface MTP layer 2 T3) timer is the aligned timer associated
with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.
The valid ranges for this element are dependent upon the
value of the ss7_mode.

Syntax

Change command string

chg_element lb_int_ss7_l2_t3 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t3 <location>

Values

Value type Integer (milliseconds)

Valid range ss7_mode = 0: 1000 to 1500
ss7_mode = 1: 5000 to 14000
Default value ss7_mode = 0: 1400
ss7_mode =1: 11500

References

ITU specification CCITT Q.703

7-96 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_ss7_l2_t4

lb_int_ss7_l2_t4

Description

The lb_int_ss7_l2_t4 (Lb-interface MTP layer 2 T4) timer is the emergency proving period
timer associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_ss7_l2_t4 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t4 <location>

Values

Value type Integer (milliseconds)

Valid range 400 to 600
Default value 600

References

ITU specification CCITT Q.703

68P02901W23-T 7-97
Jan 2010
lb_int_ss7_l2_t5 Chapter 7: Timer parameters

lb_int_ss7_l2_t5

Description

The lb_int_ss7_l2_t5 (Lb-interface MTP layer 2 T5) timer is the sending SIB timer associated
with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_ss7_l2_t5 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t5 <location>

Values

Value type Integer (milliseconds)

Valid range 80 to 120
Default value 100

References

ITU specification CCITT Q.703

7-98 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_ss7_l2_t6

lb_int_ss7_l2_t6

Description

The lb_int_ss7_l2_t6 (Lb-interface MTP layer 2 T6) timer is the remote congestion timer
associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.
The valid ranges for this element are dependent upon the
value of the ss7_mode.

Syntax

Change command string

chg_element lb_int_ss7_l2_t6 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t6 <location>

Values

Value type Integer (millisecond)

Valid range ss7_mode = 0: 3000 to 6000ss7_mode = 1: 1000 to 6000
Default value ss7_mode = 0: 5000ss7_mode =1: 5000

References

ITU specification ITU Q.703

68P02901W23-T 7-99
Jan 2010
lb_int_ss7_l2_t7 Chapter 7: Timer parameters

lb_int_ss7_l2_t7

Description

The lb_int_ss7_l2_t7 (Lb-interface MTP layer 2 T7) timer is the excessive delay of
acknowledgment timer associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.
The valid ranges for this element are dependent upon the
value of the ss7_mode.

Syntax

Change command string

chg_element lb_int_ss7_l2_t7 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t7 <location>

Values

Value type Integer (milliseconds)

Valid range 500 to 2000
Default value 1000

References

ITU specification CCITT Q.703

7-100 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_ss7_l3_t1

lb_int_ss7_l3_t1

Description

The lb_int_ss7_l3_t1 (Lb-interface MTP layer 3 T1) timer is the delay to avoid mis-sequencing
on changeover timer associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_ss7_l3_t1 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t1 <location>

Values

Value type Integer (milliseconds)

Valid range 500 to 1200
Default value 850

References

ITU specification CCITT Q.704

68P02901W23-T 7-101
Jan 2010
lb_int_ss7_l3_t2 Chapter 7: Timer parameters

lb_int_ss7_l3_t2

Description

The lb_int_ss7_l3_t2 (Lb-interface MTP layer 3 T2) timer is the waiting for changeover
acknowledgment timer associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_ss7_l3_t2 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t2 <location>

Values

Value type Integer (milliseconds)

Valid range 700 to 2000
Default value 1400

References

ITU specification CCITT Q.704

7-102 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_ss7_l3_t4

lb_int_ss7_l3_t4

Description

The lb_int_ss7_l3_t4 (Lb-interface MTP layer 3 T4) timer is the waiting for changeback
acknowledgment (first attempt) timer associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_ss7_l3_t4 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t4 <location>

Values

Value type Integer (milliseconds)

Valid range 500 to 1200
Default value 850

References

ITU specification CCITT Q.704

68P02901W23-T 7-103
Jan 2010
lb_int_ss7_l3_t5 Chapter 7: Timer parameters

lb_int_ss7_l3_t5

Description

The lb_int_ss7_l3_t5 (Lb-interface MTP layer 3 T5) timer is the waiting for changeback
acknowledgment (second attempt) timer associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_ss7_l3_t5 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t5 <location>

Values

Value type Integer (milliseconds)

Valid range 500 to 1200
Default value 850

References

ITU specification CCITT Q.704

7-104 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_ss7_l3_t12

lb_int_ss7_l3_t12

Description

The lb_int_ss7_l3_t12 (Lb-interface MTP layer 3 T12) timer is the waiting for uninhibit
acknowledgment timer associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_ss7_l3_t12 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t12 <location>

Values

Value type Integer (milliseconds)

Valid range 800 to 1500
Default value 1150

References

ITU specification CCITT Q.704

68P02901W23-T 7-105
Jan 2010
lb_int_ss7_l3_t13 Chapter 7: Timer parameters

lb_int_ss7_l3_t13

Description

The lb_int_ss7_l3_t13 (Lb-interface MTP layer 3 T13) timer is the waiting for force uninhibit
timer associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_ss7_l3_t13 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t13 <location>

Values

Value type Integer (milliseconds)

Valid range 800 to 1500
Default value 1150

References

ITU specification CCITT Q.704

7-106 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_ss7_l3_t14

lb_int_ss7_l3_t14

Description

The lb_int_ss7_l3_t14 (Lb-interface MTP layer 3 T14) timer is the waiting for inhibition
acknowledgment timer associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_ss7_l3_t14 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t14 <location>

Values

Value type Integer (milliseconds)

Valid range 2000 to 3000
Default value 2500

References

ITU specification CCITT Q.704

68P02901W23-T 7-107
Jan 2010
lb_int_ss7_l3_t17 Chapter 7: Timer parameters

lb_int_ss7_l3_t17

Description

The lb_int_ss7_l3_t17 (Lb-interface MTP layer 3 T17) timer is the delay to avoid oscillation
of initial alignment failure and link restart timer associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.

Syntax

Change command string

chg_element lb_int_ss7_l3_t17 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t17 <location>

Values

Value type Integer (milliseconds)

Valid range 800 to 1500
Default value 1150

References

ITU specification CCITT Q.704

7-108 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_ss7_l3_t22

lb_int_ss7_l3_t22

Description

The lb_int_ss7_l3_t22 (Lb-interface MTP layer 3 T22) timer is the local inhibit test timer
associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes
Cell description required No
Dependencies The Location Services feature must be unrestricted.
The ss7_mode dependent parameters are set to the
appropriate defaults when the ss7_mode is changed.
The valid values for this element are dependent upon the
value of the ss7_mode element.

Syntax

Change command string

chg_element lb_int_ss7_l3_t22 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t22 <location>

Values

Value type Integer (milliseconds)

Valid range ss7_mode = 0: 180000 to 360000
ss7_mode = 1: 90000 to 120000
Default value ss7_mode = 0: 270000
ss7_mode =1: 90000

NOTE
The ss7_mode dependent parameters are set to the appropriate defaults when the
ss7_mode is changed.

68P02901W23-T 7-109
Jan 2010
References Chapter 7: Timer parameters

References

ITU specification CCITT Q.704

7-110 68P02901W23-T
Jan 2010
Technical Description: BSS Command Reference lb_int_ss7_l3_t23

lb_int_ss7_l3_t23

Description

The lb_int_ss7_l3_t23 (Lb-interface MTP layer 3 T23) timer is the remote inhibit test timer
associated with the Lb-interface.

Type A (no operator actions)

Supported by OMC-R GUI Yes