Parameter Manual Motorola GSR7

Technical Description: BSS Command
Reference
© 1994 - 2004 Motorola, Inc. 68P02901W23-Q
All Rights Reserved CONTROLLED INTRODUCTION 24 May 2004

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media.
Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to
copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products
described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patent
applications of Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in
accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part of
the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language,
in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions
in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products described herein to improve
reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to
notify any person of revisions or changes. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein;
neither does it convey license under its patent rights of others.
Trademarks
Motorola and the Motorola logo are registered trademarks of Motorola Inc.
Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
CONTROLLED INTRODUCTION 24 May 2004

Table
of
Contents
Contents
Technical Description: BSS Command Reference

Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 1: Introduction to commands

BSS MMI functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Command/database parameter security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Command/database parameter types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Commands to be used with caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Parameters to be used with caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Entering MMI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
MMI command availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
GSM cell ID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Indices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
SYSGEN mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Chapter 2: Device/function related commands

Command reference presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Device related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Device identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Function related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Function identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
equip/unequip command matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Alarm devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
add_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
add_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
add_neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
add_nsvc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
add_rtf_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
alarm_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
assess. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
68P02901W23-Q i
24 May 2004 CONTROLLED INTRODUCTION
Contents
cage_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
cell_name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
chg_acs_params. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61
chg_a5_alg_pr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
chg_audit_sched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72
chg_cell_element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77
chg_cell_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-81
chg_csfp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-85
chg_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88
chg_eas_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92
chg_element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-95
chg_hop_params . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
chg_ksw_config. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-111
chg_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-115
chg_password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-117
chg_rtf_freq. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
chg_severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-125
chg_smscb_msg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-127
chg_throttle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-133
chg_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-135
chg_ts_usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-138
chg_x25config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-144
clear_cal_data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-147
clear_database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-149
clear_gclk_avgs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-151
configure_csfp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-153
connection_code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-155
copy_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-157
copy_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-163
del_act_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-166
del_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-169
del_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-172
del_neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-174
del_nsvc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-178
del_rtf_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-180
del_smscb_msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-182
device_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-185
diagnose_device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-190
disp_a5_alg_pr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-192
disp_acs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-194
disp_act_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-196
disp_bss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-199
disp_cal_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-201
disp_cbch_state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-203
disp_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-206
disp_cell_map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-211
disp_cell_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-214
disp_conn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-224
disp_csfp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-226
disp_csfp_status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-228
disp_dte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-230
disp_element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-232
disp_equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-235
disp_exp_config. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-245
disp_flash. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-247
ii 68P02901W23-Q
Technical Description: BSS Command Reference Contents
disp_gclk_avgs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-249
disp_gclk_cal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-251
disp_gsm_cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-254
disp_hdlc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-257
disp_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-260
disp_level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-265
disp_link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-266
disp_link_usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-268
disp_mms_ts_usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-270
disp_neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-282
disp_nsvc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-288
disp_options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-291
disp_processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-295
disp_relay_contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-299
disp_rtf_channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-301
disp_rtf_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-308
disp_severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-311
disp_site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-313
disp_throttle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-314
disp_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-316
disp_trace_call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-318
disp_traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-321
disp_transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-324
disp_version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-326
disp_x25config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-327
equip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-329
freq_types_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-378
gclk_cal_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-381
ins_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-382
lock_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-387
mod_conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-392
mod_nsvc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-395
modify_neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-397
modify_value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-404
page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-409
query_audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-411
reassign. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-415
reattempt_pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-418
reset_device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-420
reset_site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-425
set_full_power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-430
set_relay_contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-434
shutdown_device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-436
site_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-441
soft_reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-445
state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-448
status_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-460
store_cal_data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-464
swap_devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-466
sysgen_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-469
time_stamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-475
trace_call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-477
trace_connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-486
trace_stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-489
unconfigure_csfp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-492
68P02901W23-Q iii
Contents
unequip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-494
unlock_device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-504
Chapter 3: UNIX commands

alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
man . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
unalias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Chapter 4: Statistics commands

Statistical operations and information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
chg_stat_prop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
disp_enable_stat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
disp_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
disp_stat_prop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
disp_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
stat_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Chapter 5: CM database parameters

CM database parameters presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
aci_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
aci_error_gen_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
aci_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
adap_ho_alt_trigger_rxqual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
adap_ho_pbgt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
adap_ho_rxlev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
adap_ho_rxqual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
adap_trigger_hop_rxqual_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
adap_trigger_hop_rxqual_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
adap_trigger_pbgt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
adap_trigger_pbgt_nbr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
adap_trigger_rxlev_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
adap_trigger_rxlev_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
adap_trigger_rxqual_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
adap_trigger_rxqual_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
allow_8k_trau. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
alt_qual_proc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
amr_bss_full_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
amr_bss_half_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
amr_dl_la_mode_chg_min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
amr_dl_thresh_adjust . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
amr_fr_dl_la_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
amr_fr_ul_la_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
amr_full_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
amr_hr_dl_la_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
amr_hr_ul_la_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
amr_ms_high_cmr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
amr_ms_high_rxqual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
amr_ms_low_cmr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
amr_ms_low_rxqual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
amr_ms_monitor_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
attach_detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
iv 68P02901W23-Q
auto_rf_loss_trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
ba_alloc_proc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
band_preference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
band_preference_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
ber_loss_daily. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
ber_loss_hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
bounce_protect_margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
bs_ag_blks_res . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
bs_pa_mfrms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
bs_pag_blks_res. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
bs_pbcch_blks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
bs_pcc_chans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
bs_prach_blks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
bsc_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
bsic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
bss_egsm_alm_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
bss_msc_overload_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72
bssgp_block_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
bssgp_cbl_bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
bssgp_racap_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
bssgp_reset_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
bssgp_unblock_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77
bts_p_con_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
bts_p_con_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80
bts_power_control_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
bts_txpwr_max_inner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-84
bts_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-89
bvci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-91
call_trace_options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-93
called_pci. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-95
calling_pci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-96
carrier_disable_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-97
carriers_ins_pwr_fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98
cbc_fast_select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-100
cbc_intface_vers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-102
cbc_vbind_cntr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103
cbch_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-104
cbs_outage_cntr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105
ccch_conf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-106
ccch_load_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-109
cell_bar_access_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-111
cell_bar_access_switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-114
cell_bar_qualify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-116
cell_reselect_hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-118
cell_reselect_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-120
cell_reselect_param_ind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-122
chan_alloc_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-124
channel_reconfiguration_switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125
cic_block_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-127
cic_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-129
cic_error_gen_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-130
cic_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-131
cic_unblock_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-132
cic_validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-134
ciph_mode_rej_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-135
68P02901W23-Q v
Contents
clk_src_fail_reset_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-136
coincident_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-137
coincident_mb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-139
coincident_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-141
confusion_msg_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-142
congest_at_source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-144
congest_at_target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-146
congest_ho_margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-147
cp_option_reset_ckt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-148
cp_option_rr_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-149
cr_calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-150
ct_flow_control_hi_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-151
ct_flow_control_lo_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-152
ct_flow_control_msc_trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-153
c31_hyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-154
c32_qual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-156
data_qual_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-158
ddtr_ctrl_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-160
decision_1_dl_rxlev_av_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-161
decision_1_dl_rxlev_av_ih. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-162
decision_1_dl_rxqual_av_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-163
decision_1_dl_rxqual_av_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-164
decision_1_dl_rxqual_av_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-165
decision_1_n1/decision_1_p1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-166
decision_1_ncell_rxlev_av_h_calc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-182
decision_1_p_bgt_rxlev_av_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-183
decision_1_tim_adv_av_alg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-184
decision_1_ul_rxlev_av_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-185
decision_1_ul_rxlev_av_ih. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-186
decision_1_ul_rxlev_av_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-187
decision_1_ul_rxqual_av_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-188
decision_1_ul_rxqual_av_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-189
decision_alg_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-190
delay_ul_rel_dur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-192
direct_inner_zone_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-193
disuse_cnt_hreqave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-194
dl_audio_lev_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195
dl_dtx_voice_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-197
dl_rxlev_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-198
dl_rxqual_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-200
dnlk_vad_dtx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-202
dpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-204
dr_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-206
dr_chan_mode_modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-207
dr_ho_during_assign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-209
dr_preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-211
dr_standard_congest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-213
dtx_required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-215
vi 68P02901W23-Q
dual_band_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-217
dyn_step_adj . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-218
dyn_step_adj_fmpr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-219
dynet_tchs_reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-220
eac_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-222
early_classmark_sending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-224
eas_alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-226
eas_alarm_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-227
eas_report_opto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-228
eas_severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-229
efr_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-231
egprs_init_dl_cs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-233
egprs_init_ul_cs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-235
egsm_bcch_sd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-237
egsm_handover_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-239
emergency_class_switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-241
en_incom_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-243
enhanced_relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-245
eop_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-246
erc_ta_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-247
ext_range_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-248
extended_paging_active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-250
fdd_qmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-252
fdd_qoffset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-253
force_hr_usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-254
frequency_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-255
full_pwr_rfloss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-257
gci_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-258
gci_error_gen_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-259
gci_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-260
gclk_qwarm_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-261
global_reset_repetitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-262
gproc_slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-264
gprs_alarm_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-266
gprs_bs_cv_max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-267
gprs_cell_cgt_thr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-268
gprs_cell_reselect_hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-270
gprs_com_ms_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-272
gprs_cr_margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-273
gprs_dl_pwr_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-275
gprs_drx_timer_max. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-277
gprs_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-279
gprs_intraho_allwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-281
gprs_mac_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-283
gprs_max_ul_ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-284
gprs_min_prr_blks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-285
gprs_ms_pan_dec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-286
gprs_ms_pan_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-288
gprs_ms_pan_max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-290
gprs_ms_txpwr_max_cch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-292
gprs_network_operation_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-295
gprs_num_pmrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-297
gprs_pb. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-299
gprs_pc_alpha. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-300
gprs_pc_meas_chan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-301
68P02901W23-Q vii
Contents
gprs_reconfig_thresh_idle_tch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-303
gprs_reselect_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-304
gprs_rxlev_access_min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-306
gprs_sched_beta. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-308
gprs_sig_bvci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-309
gprs_temporary_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-310
gprs_ts_config_alg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-312
gprs_ul_dl_bias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-314
group_block_unblock_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-315
gsl_lcf_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-317
gsm_bss_half_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-319
gsm_cell_id_format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-321
gsm_half_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-323
half_rate_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-325
handover_power_level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-327
handover_required_curr_ch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-330
handover_required_reject_switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-332
handover_required_sp_ver_used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-334
hcs_thr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-336
hdsl_losw_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-337
hdsl_losw_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-338
hdsl_snr_daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-339
hdsl_snr_daily_mon_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-341
hdsl_snr_hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-342
hdsl_snr_hourly_mon_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-344
hdsl_snr_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-345
hdsl_snr_restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-347
ho_exist_congest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-349
ho_margin_def . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-351
ho_margin_type5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-353
ho_margin_usage_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-354
ho_only_max_pwr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-356
ho_pwr_level_inner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-358
hop_count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-360
hop_qual_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-361
hopping_support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-363
hopping_systems_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-365
hopping_systems_hsn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-367
hopping_systems_mobile_alloc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-369
hr_fr_hop_count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-371
hr_intracell_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-372
hr_res_ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-374
illegal_circuit_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-375
immediate_assign_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-376
inc_prp_cap_ena . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-378
init_dl_cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-380
init_ul_cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-382
inner_hr_usage_thres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-384
inner_zone_alg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-385
intave. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-388
inter_cell_handover_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-390
inter_rat_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-392
interband_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-394
interfer_bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-396
intra_cell_handover_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-398
viii 68P02901W23-Q
ksw_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-400
l_rxlev_dl_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-402
l_rxlev_dl_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-404
l_rxlev_ul_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-406
l_rxlev_ul_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-408
l_rxqual_dl_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-410
l_rxqual_dl_h_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-412
l_rxqual_dl_h_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-413
l_rxqual_dl_h_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-415
l_rxqual_dl_h_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-417
l_rxqual_dl_h_hopping_amr_fr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-419
l_rxqual_dl_h_hopping_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-421
l_rxqual_dl_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-423
l_rxqual_dl_p_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-425
l_rxqual_dl_p_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-426
l_rxqual_dl_p_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-428
l_rxqual_dl_p_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-430
l_rxqual_dl_p_hopping_amr_fr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-432
l_rxqual_dl_p_hopping_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-434
l_rxqual_ul_h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-436
l_rxqual_ul_h_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-438
l_rxqual_ul_h_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-439
l_rxqual_ul_h_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-441
l_rxqual_ul_h_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-443
l_rxqual_ul_h_hopping_amr_fr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-445
l_rxqual_ul_h_hopping_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-447
l_rxqual_ul_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-449
l_rxqual_ul_p_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-451
l_rxqual_ul_p_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-452
l_rxqual_ul_p_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-454
l_rxqual_ul_p_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-456
l_rxqual_ul_p_hopping_amr_fr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-458
l_rxqual_ul_p_hopping_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-460
land_layer1_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-462
layer_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-464
lb_int_called_pci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-465
lb_int_calling_pci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-466
lb_int_cr_calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-467
lb_int_dpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-468
lb_int_global_reset_repetitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-469
lcs_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-470
link_about_to_fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-473
link_fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-475
lmtl_loadshare_granularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-477
local_maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-478
low_sig_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-481
lta_alarm_range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-482
max_gprs_ts_per_carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-483
max_ms_dl_buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-484
max_ms_dl_rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-486
max_mtls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-487
max_number_of_sdcchs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-489
max_pagenum_per_sec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-491
max_q_length_channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-492
max_q_length_sdcch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-494
68P02901W23-Q ix
Contents
max_retran . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-495
max_rst_ckt_timer_exps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-497
max_tx_bts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-498
max_tx_ms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-504
mb_preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-506
mb_tch_congest_thres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-507
missing_rpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-508
mmi_cell_id_format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-509
mms_cat_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-510
mms_config_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-512
ms_distance_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-514
ms_max_range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-516
ms_p_con_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-518
ms_p_con_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-520
ms_power_control_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-522
ms_power_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-524
ms_txpwr_max_cch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-525
ms_txpwr_max_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-528
ms_txpwr_max_def . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-530
ms_txpwr_max_inner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-532
msc_bss_overload_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-533
msc_preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-534
msc_qt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-536
msc_release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-538
mspwr_alg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-539
mtl_loadshare_granularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-540
multiband_reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-541
n_avg_i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-543
ncc_of_plmn_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-544
nccr_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-546
nccrOpt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-547
neighbor_journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-548
network_control_order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-550
new_calls_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-552
ni . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-553
ns_alive_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-555
ns_block_retries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-556
ns_unblock_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-557
nsei . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-558
num_audit_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-559
num_emerg_access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-560
num_emerg_rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-561
num_emerg_tch_kill. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-562
num_emerg_term_sdcch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-563
num_gbl_dl_thrput_samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-564
num_gbl_ul_thrput_samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-565
number_of_preferred_cells. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-566
number_sdcchs_preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-568
opc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-570
option_alg_a5_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-572
option_alg_a5_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-573
option_alg_a5_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-574
option_alg_a5_4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-575
option_alg_a5_5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-576
option_alg_a5_6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-577
x 68P02901W23-Q
option_alg_a5_7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-578
option_emergency_preempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-579
outer_zone_usage_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-581
override_intra_bss_pre_transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-582
pbgt_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-583
pccch_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-584
pccchOpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-586
pcr_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-587
pcr_n1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-588
pcr_n2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-589
pcu_redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-590
percent_traf_cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-592
persistence_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-593
phase_lock_gclk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-595
phase_lock_retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-596
phase2_classmark_allowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-597
phase2_resource_ind_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-598
pic_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-599
pic_error_gen_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-600
pic_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-601
pkt_radio_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-602
pool_gproc_preemption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-606
poor_initial_assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-607
pow_inc_step_size_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-608
pow_inc_step_size_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-610
pow_red_step_size_dl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-612
pow_red_step_size_ul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-614
prach_max_retran . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-616
prach_s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-617
prach_tx_int . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-619
primary_pcu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-621
prioritize_microcell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-622
priority_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-623
protect_last_ts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-624
prp_capacity_opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-626
prr_aggr_factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-627
pwr_handover_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-628
pwrc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-630
queue_management_information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-632
qsearch_c_initial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-634
qsearch_i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-635
qsearch_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-636
ra_colour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-638
ra_reselect_hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-640
rac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-642
rach_load_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-644
rach_load_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-646
rach_load_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-648
radio_link_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-649
rapid_pwr_down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-651
rci_error_clr_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-653
rci_error_gen_thresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-654
rci_error_inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-655
reconfig_fr_to_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-656
red_loss_daily. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-657
68P02901W23-Q xi
Contents
red_loss_hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-658
red_loss_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-659
red_loss_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-660
red_time_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-661
red_time_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-662
reestablish_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-663
rel_tim_adv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-665
remote_loss_daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-667
remote_loss_hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-668
remote_loss_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-669
remote_loss_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-670
remote_time_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-671
remote_time_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-672
report_resource_tch_f_high_water_mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-673
report_resource_tch_f_low_water_mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-675
res_gprs_pdchs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-677
res_ts_less_one_carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-679
rf_res_ind_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-681
rpd_offset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-682
rpd_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-683
rpd_trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-684
rpt_bad_qual_no_mr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-686
rsl_congestion_control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-688
rsl_lcf_congestion_thi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-689
rsl_lcf_congestion_tlow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-691
rtf_path_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-692
rxlev_access_min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-693
rxlev_dl_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-695
rxlev_dl_pc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-697
rxlev_dl_zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-699
rxlev_min_def . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-701
rxlev_ul_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-703
rxlev_ul_pc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-705
rxlev_ul_zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-707
rxqual_dl_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-709
rxqual_dl_pc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-711
rxqual_ul_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-713
rxqual_ul_pc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-715
sap_audit_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-717
sap_device_type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-718
sap_end_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-719
sap_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-720
sap_start_time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-722
sccp_bssap_mgt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-724
scr_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-726
sdcch_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-728
sdcch_need_high_water_mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-730
sdcch_need_low_water_mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-732
sdcch_tch_band_reassign_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-734
sdcch_timer_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-735
search_prio_3g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-737
second_asgnmnt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-738
secondary_freq_type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-740
sgsn_release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-742
slip_loss_daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-743
xii 68P02901W23-Q
slip_loss_hourly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-744
slip_loss_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-746
slip_loss_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-747
smg_gb_vers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-748
sms_dl_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-749
sms_tch_chan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-750
sms_ul_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-752
ss7_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-753
ssm_critical_overload_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-755
ssm_normal_overload_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-757
ssp_burst_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-758
ssp_burst_limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-759
stat_interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-760
surround_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-761
sw_ts_less_one_carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-763
swfm_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-765
switch_gprs_pdchs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-766
sync_loss_daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-768
sync_loss_hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-769
sync_loss_oos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-770
sync_loss_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-771
sync_time_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-772
sync_time_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-773
t_avg_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-774
t_avg_w . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-775
tch_busy_critical_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-776
tch_busy_norm_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-777
tch_congest_prevent_thres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-778
tch_flow_control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-779
tch_full_need_low_water_mark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-781
temporary_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-783
threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-785
timing_advance_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-786
tlli_blk_coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-788
trace_msgs_after_ho. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-789
trace_msgs_before_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-790
trans_capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-791
trunk_critical_threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-793
trunk_major_threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-794
ts_alloc_flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-795
ts_in_usf_active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-796
tsc_update_method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-797
tx_integer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-799
tx_power_cap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-801
u_rxlev_dl_ih . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-803
u_rxlev_dl_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-805
u_rxlev_ul_ih . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-807
u_rxlev_ul_p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-809
u_rxqual_dl_p. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-811
u_rxqual_dl_p_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-813
u_rxqual_ul_p. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-815
u_rxqual_ul_p_hr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-817
ul_audio_lev_offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-819
ul_rxlev_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-820
ul_rxqual_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-822
68P02901W23-Q xiii
Contents
unequipped_circuit_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-824
use_derived_ho_power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-826
use_neighbor_pbgt_hreqave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-827
volume_control_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-828
wait_for_reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-830
wait_indication_parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-831
worse_neighbor_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-833
zone_ho_hyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-834
zone_pingpong_count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-836
zone_pingpong_preferred_zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-837
Chapter 6: Timer parameters

add_access_class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
assign_successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
auto_dl_dur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
bcch_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
bep_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
bep_period2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
bounce_protect_cong_tmr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
bounce_protect_qual_tmr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
bsc_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
bsc_audit_response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
bss_overload_control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
bssgp_fc_period_c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
bssgp_t1_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
bssgp_t2_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
bssmap_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
bssmap_t10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
bssmap_t11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
bssmap_t13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
bssmap_t19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
bssmap_t20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
bssmap_t4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
bssmap_t7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32
bssmap_t8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
bssmap_tqho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36
bts_audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
bts_audit_response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40
bts_escalation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41
carrier_free_immediate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
cbch_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44
cbch_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45
cbch_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
channel_act . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47
channel_teardown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-49
cipher_comp_ms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
ciphering_successful. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
circuit_reset_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54
clear_cmd_ext_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-55
clear_command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
dealloc_inact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-58
delay_dl_rel_dur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-60
downlink_sync_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
dynet_retry_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63
xiv 68P02901W23-Q
early_classmark_delay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65
emerg_reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66
ext_ho_allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-68
ext_rtry_cand_prd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69
flow_control_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-70
flow_control_t2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-72
gbl_thrput_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74
gprs_penalty_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-75
gprs_smg30_t3192 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77
gprs_t3168 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-78
gprs_t3192 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-79
handover_recognized_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80
ho_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82
ho_allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84
ho_complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85
ho_request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-87
ho_successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-88
hop_count_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89
initial_sync_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-90
lb_int_bssmap_t13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-92
lb_int_bssmap_t4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-93
lb_int_clear_command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-94
lb_int_sccp_released. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95
lb_int_sccp_tconn_est . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96
lb_int_sccp_tiar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-97
lb_int_sccp_tias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-98
lb_int_sccp_trel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-99
lb_int_spi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-100
lb_int_ss7_l2_t1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-101
lb_int_ss7_l2_t2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-102
lb_int_ss7_l2_t3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-103
lb_int_ss7_l2_t4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-104
lb_int_ss7_l2_t5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-105
lb_int_ss7_l2_t6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106
lb_int_ss7_l2_t7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-107
lb_int_ss7_l3_t1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-108
lb_int_ss7_l3_t12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-109
lb_int_ss7_l3_t13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-110
lb_int_ss7_l3_t14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-111
lb_int_ss7_l3_t17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-112
lb_int_ss7_l3_t2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-113
lb_int_ss7_l3_t22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-114
lb_int_ss7_l3_t23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116
lb_int_ss7_l3_t4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-118
lb_int_ss7_l3_t5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-119
lb_int_ss7_slt_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-120
lb_int_t_stat_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-121
lcs_perf_location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-122
lcs_segmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-123
lcs_supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-124
mode_modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-125
mode_rr_modify_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-127
ms_sapi3_est . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-129
nc_non_drx_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-131
nc_reporting_period_i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-133
68P02901W23-Q xv
Contents
nc_reporting_period_t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-134
neighbor_report_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136
ns_alive_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-137
ns_block_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-138
ns_reset_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-139
ns_reset_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-140
ns_test_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-141
pccch_drx_timer_max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-142
penalty_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-144
phase_lock_duration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-146
psi1_repeat_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-147
radio_chan_released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-149
red_psp_audit_tmr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-151
register_exp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-152
rf_chan_rel_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-153
rr_ny1_rep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-155
rr_t3101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-157
rr_t3103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-159
rr_t3105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-161
rr_t3109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-163
rr_t3111_sd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-165
rr_t3111_tch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-167
rr_t3212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-169
rsl_congestion_alarm_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-171
rtry_cand_prd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-172
sacch_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-174
sccp_released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-176
sccp_tconn_est . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-177
sccp_tiar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-178
sccp_tias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-180
sccp_trel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-182
sm_audit_response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-183
spi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-184
ss7_l2_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-186
ss7_l2_t2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-188
ss7_l2_t3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-190
ss7_l2_t4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-192
ss7_l2_t5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-193
ss7_l2_t6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-194
ss7_l2_t7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-196
ss7_l3_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-197
ss7_l3_t12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-198
ss7_l3_t13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-199
ss7_l3_t14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-200
ss7_l3_t17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-201
ss7_l3_t2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-202
ss7_l3_t22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-203
ss7_l3_t23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-205
ss7_l3_t4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-207
ss7_l3_t5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-208
ss7_slt_t1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-209
start_ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-210
static_sync_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-211
t_stat_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-213
uplink_sync_timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-214
xvi 68P02901W23-Q
valid_candidate_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-216
zone_pingpong_disable_win . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-217
zone_pingpong_enable_win . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-218
Chapter 7: Device/function parameters

Device and function database parameters presentation . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
antenna_select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
ber_oos_mon_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
ber_restore_mon_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
bsc_cbc_operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
cabinet_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
cavity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
cbc_operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
cell_zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
chan_alloc_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
cic_validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
clkx0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
clkx1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
clkx2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
combiner_address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
combiner_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
combining_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
dri_density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
ext_timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
fm_cell_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
frequency_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
hdsl_modem_setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
hdsl_oos_mon_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
hdsl_restore_mon_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
ias_connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
int_antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
int_hdsl_modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
lapd_k . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
lapd_n200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
lapd_t200_timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51
max_cbls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53
max_dris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54
max_gsls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56
max_mtls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57
mms_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59
msc_mms_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61
msi_type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62
n391 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
n392 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
n393 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
nbit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
ne_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
opto_reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69
pref_rtf_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-71
rsl_rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72
sd_load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
sd_priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75
shared_timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77
slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78
68P02901W23-Q xvii
Contents
start_ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79
t391 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
t392 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82
tcu_port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-83
transcoding_capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-85
tru_id. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-86
trx_pwr_red. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-87
xviii 68P02901W23-Q
List
of
Figures
List of Figures
Figure 2-1: Remote Transcoder (RXCDR) devices and functions . . . . . . . . . . . . . . . . . . . . . 2-334

Figure 2-2: BSC and InCell BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-335
Figure 2-3: In-Cell and Horizonmacro equipage hierarchy chart . . . . . . . . . . . . . . . . . . . . . 2-336
Figure 2-4: GPRS PCU devices and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-337
68P02901W23-Q xix
List of Figures
This page intentionally left blank.
xx 68P02901W23-Q
List
of
Tables
List of Tables
Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 2: Service requests resolved in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 1-1: MMI command availability by location . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Table 1-2: MMI command availability by SYSGEN mode . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Table 1-3: Device Indices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Table 1-4: Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Table 2-1: Device literals and descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Table 2-2: Device and command relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Table 2-3: Device ID requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Table 2-4: Function related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Table 2-5: Function ID requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Table 2-6: Valid slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Table 2-7: Equip/Unequip command matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Table 2-8: Alarm devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Table 2-9: add_cell command prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Table 2-10: add_conn valid ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34
Table 2-11: Neighbour Frequency and number with EGSM source cell . . . . . . . . . . . . . . . . . . 2-35
Table 2-12: Neighbour Frequency and number with DCS1800 source cell . . . . . . . . . . . . . . . . . 2-36
Table 2-13: add_neighbor command prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Table 2-14: Codec Mode Values / Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
Table 2-15: Full Rate attribute values for chg_acs_params command. . . . . . . . . . . . . . . . . . . 2-63
Table 2-16: Half Rate attribute values for chg_acs_params command . . . . . . . . . . . . . . . . . . 2-63
Table 2-17: Full Rate prompts for the chg_acs_params command . . . . . . . . . . . . . . . . . . . . 2-65
Table 2-18: Half Rate prompts for chg_acs_params command . . . . . . . . . . . . . . . . . . . . . . 2-66
Table 2-19: Device scheduling defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74
Table 2-20: RXCDR default DTE addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88
Table 2-21: BSC default DTE addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88
Table 2-22: EAS default alarm strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-93
Table 2-23: Baseband and Synthesizer frequency hopping restrictions. . . . . . . . . . . . . . . . . . . 2-105
Table 2-24: chg_hop_params prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-108
Table 2-25: Cell frequencies/mobile allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-109
Table 2-26: Restrictions on related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-109
Table 2-27: SMS special characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-132
Table 2-28: copy_path command prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-164
Table 2-29: mod_conn valid ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-393
Table 2-30: Operational states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-457
Table 2-31: Administrative states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-457
Table 2-32: Device states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-458
Table 2-33: Reason codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-458
Table 2-34: trace_call prompts and values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-483
Table 4-1: Counter and gauge statistic type prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Table 4-2: Normal and weighted distribution statistic type prompts . . . . . . . . . . . . . . . . . . . . 4-9
68P02901W23-Q xxi
List of Tables
Table 5-1: alt_qual_proc=0 parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Table 5-2: alt_qual_proc=1 parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Table 5-3: Base Station Identity Code - Hexadecimal Values . . . . . . . . . . . . . . . . . . . . . . . 5-70
Table 5-4: Base Station Identity Code - Decimal Values . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
Table 5-5: CTU2 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85
Table 5-6: Cabinet antenna connector maximum output power (Watts) . . . . . . . . . . . . . . . . . . 5-86
Table 5-7: Values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro,etc. sites . . . . . . . . . . . 5-86
Table 5-8: Values for DCS1800 and M-Cellaccess, sites . . . . . . . . . . . . . . . . . . . . . . . . . 5-87
Table 5-9: Sample output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-87
Table 5-10: Values for barring classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-112
Table 5-11: Maximum mobile power level for PGSM, EGSM and GSM850 cells . . . . . . . . . . . . . 5-293
Table 5-12: Maximum mobile power level for DCS1800 cells . . . . . . . . . . . . . . . . . . . . . . 5-293
Table 5-13: Maximum mobile power level for PCS1900 cells . . . . . . . . . . . . . . . . . . . . . . 5-293
Table 5-14: Modes for gprs_network_operation_mode . . . . . . . . . . . . . . . . . . . . . . . . . 5-295
Table 5-15: Max MS power level for PGSM and EGSM . . . . . . . . . . . . . . . . . . . . . . . . . 5-328
Table 5-16: Max MS power level for DCS1800 and PCS1900 cells . . . . . . . . . . . . . . . . . . . . 5-328
Table 5-17: Max MS power level for class 3 mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . 5-328
Table 5-18: Max MS power level for PGSM and EGSM cells . . . . . . . . . . . . . . . . . . . . . . 5-359
Table 5-19: Max MS power level for DCS1800 and PCS1900 cells . . . . . . . . . . . . . . . . . . . . 5-359
Table 5-20: Max MS level for class 3 mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-359
Table 5-21: Prompted parameters for Dual Band Cell use . . . . . . . . . . . . . . . . . . . . . . . . 5-387
Table 5-22: CTU2 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-499
Table 5-23: Cabinet antenna connector maximum output power (Watts) . . . . . . . . . . . . . . . . . . 5-500
Table 5-24: Values for PGSM, EGSM, DCS1800 and PCS1900, etc. sites . . . . . . . . . . . . . . . . . 5-500
Table 5-25: Values for DCS1800 and M-Cellaccess sites . . . . . . . . . . . . . . . . . . . . . . . . . 5-501
Table 5-26: Sample output power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-501
Table 5-27: Value interpolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-502
Table 5-28: ms_max_range values for normal cells . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-517
Table 5-29: ms_max_range values for Extended Range cells. . . . . . . . . . . . . . . . . . . . . . . 5-517
Table 5-30: Maximum mobile power level for PGSM and EGSM cells . . . . . . . . . . . . . . . . . . 5-526
Table 5-31: Maximum mobile power level for DCS1800 cells . . . . . . . . . . . . . . . . . . . . . . 5-526
Table 5-32: Maximum mobile power level for PCS1900 cells . . . . . . . . . . . . . . . . . . . . . . 5-527
Table 5-33: Bit mapping of ncc_of_plmn_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-545
Table 5-34: Configurations for network_control_order . . . . . . . . . . . . . . . . . . . . . . . . . 5-550
Table 5-35: EGPRS backport and backfill guideline . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-603
Table 5-36: pkt_radio_type translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-603
Table 5-37: Values for prach_tx_int representing number of frame slots . . . . . . . . . . . . . . . . . 5-620
Table 5-38: qsearch_p attribute values below threshold . . . . . . . . . . . . . . . . . . . . . . . . . 5-637
Table 5-39: qsearch_p attribute values above threshold . . . . . . . . . . . . . . . . . . . . . . . . . 5-637
Table 5-40: Example cell configurations for rach_load_threshold . . . . . . . . . . . . . . . . . . . . 5-646
Table 6-1: Impermissible combinations of psi1_repeat_period and bs_pbcch_blks . . . . . . . . . . . . 6-148
Table 7-1: Cabinets/Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Table 7-2: Values for PGSM, EGSM and PCS 1900 sites . . . . . . . . . . . . . . . . . . . . . . . . . 7-88
Table 7-3: Values for DCS 1800 sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88
Table 7-4: Values for PGSM and EGSM M-Cellmicro sites. . . . . . . . . . . . . . . . . . . . . . . . 7-89
Table 7-5: Values for DCS 1800 and PCS 1900 M-Cellmicro sites . . . . . . . . . . . . . . . . . . . . 7-89
xxii 68P02901W23-Q
About
This
Manual
Technical Description: BSS Command

Reference
What is Covered In This Manual?

The 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 equipments: BTS4, BTS5, BTS6,
BSSC, BSSC2, ExCell 4, ExCell 6, TopCell, M-CellTM2, M-Cell6, M-Cellmicro, M-Cellcity,
Horizonmicro, Horizoncompact, M-Cellaccess, Horizonmacro, Horizon II macro, Horizonmicro2,
Horizoncompact2, and Packet Control Unit (PCU).
Helpful Background Information

This BSS Command Reference manual is presented in two volumes:
• Volume 1 contains Chapters 1 to 4 providing descriptions of BSS Commands.
• Volume 2 contains Chapters 5 to 7 providing descriptions of associated

parameters used with the BSS Commands.
Each volume has a full Contents list and an Index for the whole of the manual.
68P02901W23-Q 1
Issue status of this manual
The following shows the issue status of this manual since it was first released.
Version information
The following table lists the versions of this manual in order of issue:
Table 1 Manual version history
Manual
Date of issue Remarks
issue
O 03 Oct 1994 Original issue - Software release 1.2.2.x
A 30 Dec 1994 Issue A - Software release 1.2.3.x
B 01 Sep 1995 Issue B - Software release 1.3.0.x
C 31 May 1996 Issue C - Software release 1.4.0.x
D 28 Mar 1997 Issue D - Software release 1.4.1.x
E 29 Aug 1997 Issue E - GSM Software Release 2
F 27 Apr 1998 Issue F - GSM Software Release 3
G 12 Mar 1999 Issue G - GSM Software Release 4
H 14 Jul 2000 Issue H - GSM Software Release 4.1
J 31 Jul 2001 Issue J - GSM Software Release 5
K 31 May 2002 Issue K - GSM Software Release 5.1
L 30 Nov 2002 Issue L - GSM Software Release 6
M 02 May 2003 Issue M - GSM Software Release 6 (Horizon II)
P 13 Nov 2003 Issue P - GSM Software Release 7
Q 24 May 2004 Issue Q - GSM Software Release 7 Half Rate
(Controlled Introduction)
2 68P02901W23-Q
Resolution of Service Requests
The following Service Requests are now resolved in this manual:
Table 2 Service requests resolved in this manual
Service GMR
Remarks
Request Number
SR1053871 N/A Added note to ho_pwr_level_inner parameter.
SR1057867 N/A Added text to value range to clarify settings for
max_ms_dl_buffer parameter.
SR1060133 N/A Deleted confusing paragraph in description of
ho_only_max_pwr parameter.
SR1064153 GMR 01 Amended MSI default value to 1 minute in Device
Scheduling Defaults table of the chg_audit_sched command
description.
SR1065717 GMR 01 Added four new zone_pingpong parameters. (This is a
partial fix for BSC MMI only)
SR1065717 N/A (Full fix) Allows the zone_pingpong parameters to be
supported by OMC-R GUI.
SR1067024 N/A Changes to qsearch_c_initial parameter settings.
SR1068094 N/A Added text and note to carriers_ins_pwr_fail parameter.
SR1068095 N/A Corrections to nccr_enabled and max_gprs_ts_per_carrier
parameters, and additions to res_gprs_pdchs parameter.
SR1068401 N/A Added text to switch_gprs_pdchs parameter.
SR1071678 N/A Added umts_fdd option to placement field of input
parameters for add_neighbor command.
SR1076057 N/A Corrections to syntax and prompts for add_neighbor
command.
SR1076336 N/A Inserted missing unit (seconds) for the gprs_drx_timer_max
parameter value.
SR1076337 N/A Added “as the BCCH carrier.” to dependencies of
use_bcch_for_gprs parameter.
GMR 01 NOTE: Functionality of use_bcch_for_gprs parameter
replaced by pkt_radio_type.
SR1076927 N/A Changed value range for bounce_protect_cong_tmr
parameter.
SR1077335 N/A Corrected value descriptions in valid range of pbgt_mode
parameter.
SR1077801 N/A Deleted unsupported Codec Mode Value 7 from table in
chg_acs_params parameter description.
SR1081742 GMR 01 Added note to dependencies of gprs_ts_config_alg
parameter.
68P02901W23-Q 3
Table 2 Service requests resolved in this manual (Continued)

Service GMR
Remarks
Request Number
SR1085768 GMR 01 Amended description for n_avg_i parameter.
SR1086837 GMR 01 Amended CTU2 output values for a –1 valid input, of the
max_tx_bts parameter.
SR1091037 GMR 01 Amended bss_msc_overload_allowed parameter
description.
SR1100491 N/A Changed default value from 2 to 3 for gprs_network_oper-
ation_mode parameter.
Version updates
MMI commands and parameters that are new, modified or renamed as a result of the introduction
of software release GSR7 Half Rate, are listed below as:
• New commands and parameters shown in bold emphasis print.
• Modified commands and parameters shown in normal print, with the old parameter name
shown in parenthesis where an existing parameter has been renamed.
New and modified commands introduced by GSR7 Half Rate
copy_cell disp_rtf_channel
chg_cell_element equip
disp_cell_status modify_value
disp_options sysgen_mode
New and modified/renamed database parameters introduced by GSR7 Half Rate

alt_qual_proc l_rxqual_dl_p_hopping_hr
(l_rxqual_dl_p_hopping_amr_hr)
bss_overload_control l_rxqual_ul_h_hr
(l_rxqual_ul_h_amr_hr)
eac_mode l_rxqual_ul_h_hopping_hr
(l_rxqual_ul_h_hopping_amr_hr)
force_hr_usage (amr_force_hr_usage) l_rxqual_ul_p_hr
(l_rxqual_ul_p_amr_hr)
gsm_bss_half_rate_enabled l_rxqual_ul_p_hopping_hr
(l_rxqual_ul_p_hopping_amr_hr)
half_rate_enabled reconfig_fr_to_hr
(amr half_rate_enabled) (reconfig_fr_to_amr_hr)
handover_required_sp_ver_used red_psp_audit_tmr
hr_fr_hop_count rsl_congestion_alarm_timer
(amr_hop_count)
4 68P02901W23-Q
hr_intracell_ho_allowed rsl_congestion_control
(amr_hr_intracell_ho_allowed)
hr_rs_ts rsl_lcf_congestion_thi
(amr_hr_rs_ts)
inner_hr_usage_thres rsl_lcf_congestion_tlow
(amr_inner_hr_usage_thres)
msc_bss_overload_allowed u_rxqual_dl_p_hr
(u_rxqual_dl_p_amr_hr)
max_pagenum_per_sec u_rxqual_ul_p_hr
(u_rxqual_ul_p_amr_hr)
new_calls_hr zone_pingpong_count
(amr_new_calls_hr)
l_rxqual_dl_h_hr zone_pingpong_disable_win
(l_rxqual_dl_h_amr_hr)
l_rxqual_dl_h_hopping_hr zone_pingpong_enable_win
(l_rxqual_dl_h_hopping_amr_hr)
l_rxqual_dl_p_hr zone_pingpong_preferred_zone
(l_rxqual_dl_p_amr_hr)
68P02901W23-Q 5
General information
General information
• Motorola disclaims all liability whatsoever, implied or express, for any risk of damage,
loss or reduction in system performance arising directly or indirectly out of the failure
of the customer, or any one acting on the customers behalf, to abide by the instructions,
system parameters or recommendations made in this manual
• If this manual was obtained when attending a Motorola training course, it will not be updated
or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied
under normal operational circumstances, to support a major software release, then corrections
will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel in the operation,
installation and maintenance of the Motorola cellular infrastructure equipment and ancillary devices. It is
recommended that all personnel engaged in such activities be properly trained by Motorola.
Failure to comply with Motorola’s operation, installation and maintenance

instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by Motorola, although
they can be used to supplement and enhance the knowledge gained through such training.
Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features
released at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In
these manuals, new and amended features are tagged to help users to assess the impact on installed
networks. The tags are the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and
Development Prioritization (RDP) numbers. The tags include index references which are listed in the
manual Index. The Index includes the entry feature which is followed by a list of the RDB or RDP
numbers for the released features, with page references and hot links in electronic copy.
6 68P02901W23-Q
General information
The tags have the format: {nnnn} or {nnnnn}

Where: is:
{nnnn} the RDB number
{nnnnn} the RDP number
The tags are positioned in text as follows:
New and amended feature information Tag position in text

New sentence/s or new or amended text. Immediately before the affected text.
Complete new blocks of text as follows: Immediately after the headings as follows:
• Full sections under a main heading • Main heading
• Full paragraphs under subheadings • Subheading

New or amended complete Figures and Tables After the Figure or Table number and before
the title text.
Warning, Caution and Note boxes. Immediately before the affected text in the box.
General command syntax, operator input or On a separate line immediately above the
displays (in special fonts). affected item.
For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this
software release, refer to the manualSystem Information: GSM Overview (68P02901W01), or to
the manual System Information: GPRS Overview (68P02903W01).
Cross references
Throughout this manual, references are made to external publications, chapter numbers and
section names. The references to external publications are shown in italics, chapter and
section name cross references are emphasised blue in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top of
each page, and are listed in the table of contents.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and
GPRS network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels as individually standardised, or may not be present
at all in some parts of the network in which it is normally implemented. The manual set, of which
this manual is a part, covers encryption as if fully implemented. Because the rules differ in individual
countries, limitations on the encryption included in the particular software being delivered, are covered
in the Release Notes that accompany the individual software release.
68P02901W23-Q 7
General information
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to represent
keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows:
CTRL-c Press the Control and c keys at the same time.

ALT-f Press the Alt and f keys at the same time.
¦ Press the pipe symbol key.
CR or RETURN Press the Return key.
8 68P02901W23-Q
Reporting safety issues
Reporting safety issues
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure
that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
Procedure 1 Safety issue reporting
1 Make the equipment concerned safe, for example by removing power.

2 Make no further attempt to adjust or rectify the equipment.
3 Report the problem directly to the Customer Network Resolution Centre, Swindon +44
(0)1793 565444 or China +86 10 88417733 (telephone) and follow up with a written
report by fax, Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax).
4 Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.
68P02901W23-Q 9
Warnings and cautions
The following describes how warnings and cautions are used in this manual and in
all manuals of this Motorola manual set.
Warnings
A definition and example follow below:
Definition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical
injury, or ill health. This includes hazards introduced during maintenance, for example, the use of
adhesives and solvents, as well as those inherent in the equipment.
Example and format
Do not look directly into fibre optic cables or data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated
fibre optic cables connected to data in/out connectors.
Failure to comply with warnings
Observe all warnings during all phases of operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these warnings, or with specific
warnings elsewhere in the Motorola manuals, or on the equipment itself, violates safety
standards of design, manufacture and intended use of the equipment. Motorola assumes no
liability for the customer’s failure to comply with these requirements.
Cautions
A definition and example follow below:
10 68P02901W23-Q
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of
equipment within a system. However, this presents no danger to personnel.
Example and format
Do not use test equipment that is beyond its due calibration date;
arrange for calibration to be carried out.
68P02901W23-Q 11
General warnings
General warnings
Observe the following specific warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola manuals:
• Potentially hazardous voltage.
• Electric shock.
• RF radiation.
• Laser radiation.
• Heavy equipment.
• Parts substitution.
• Battery supplies.
• Lithium batteries.
Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals,
violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes
no liability for the customer’s failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working
with or operating Motorola equipment must comply with any warning labels fitted to the equipment.
Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will be
incorporated into procedures as applicable.
These must be observed by all personnel at all times when working with the equipment, as must
any other warnings given in text, in the illustrations and on the equipment.
12 68P02901W23-Q
General warnings
Potentially hazardous voltage
This equipment operates from a potentially hazardous voltage of 230 V a.c. single
phase or 415 V a.c. three phase supply. To achieve isolation of the equipment
from the a.c. supply, the a.c. input isolator must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989
(UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
Motorola GSM equipment does not utilise high voltages.
Electric shock
Do not touch the victim with your bare hands until the electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry insulating material
and pull or push the victim clear of the conductor.
ALWAYS send for trained first aid or medical assistance IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries and even
death, may result. Direct electrical contact can stun a casualty causing breathing, and even the heart,
to stop. It can also cause skin burns at the points of entry and exit of the current.
In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS
send for trained first aid or medical assistance IMMEDIATELY.
If the casualty is also suffering from burns, flood the affected area with cold water to cool,
until trained first aid or medical assistance arrives.
RF radiation
High RF potentials and electromagnetic fields are present in this equipment

when in operation. Ensure that all transmitters are switched off when
any antenna connections have to be changed. Do not key transmitters
connected to unterminated cavities or feeders.
68P02901W23-Q 13
General warnings
Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are:
• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz
• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields

High Frequency (10 kHz to 300 GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors.
Laser radiation can come from either the data in/out connectors or unterminated
fibre optic cables connected to data in/out connectors.
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, a

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

equipment, because of the danger of introducing additional hazards. Contact
Motorola if in doubt to ensure that safety features are maintained.
14 68P02901W23-Q
General warnings
Battery supplies
Do not wear earth straps when working with stand-by battery

supplies. Use only insulated tools.
Lithium batteries
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective

lithium batteries must not be removed or replaced. Any boards containing
defective lithium batteries must be returned to Motorola for repair.
Contact your local Motorola office for how to return defective lithium batteries.
68P02901W23-Q 15
General cautions
General cautions
Observe the following cautions during operation, installation and maintenance of the equipment
described in the Motorola manuals. Failure to comply with these cautions or with specific cautions
elsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes no
liability for the customer’s failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to
the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual.
These must be observed by all personnel at all times when working with the equipment, as must
any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices. These metal oxide semiconductor

(MOS) devices are susceptible to damage from electrostatic charge. See the section
Devices sensitive to static in the preface of this manual for further information.
16 68P02901W23-Q
Devices sensitive to static
Devices sensitive to static
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied to
the leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into high
insulation packing material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads short circuited together,
for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic
foam. Provided the leads are short circuited it is safe to handle the device.
Special handling techniques
In the event of one of these devices having to be replaced, observe the following
precautions when handling the replacement:
• Always wear an earth strap which must be connected to the electrostatic

point (ESP) on the equipment.
• Leave the short circuit on the leads until the last moment. It may be necessary to replace
the conductive foam by a piece of wire to enable the device to be fitted.
• Do not wear outer clothing made of nylon or similar man made material.
A cotton overall is preferable.
• If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic
work surfaces with an anti-static cloth before starting the operation.
• All metal tools should be used and when not in use they should be placed on an earthed surface.
• Take care when removing components connected to electrostatic sensitive devices.

These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to
electrostatic damage. However PCBs should be handled with care, preferably by their edges and
not by their tracks and pins, they should be transferred directly from their packing to the equipment
(or the other way around) and never left exposed on the workbench.
68P02901W23-Q 17
Motorola manual set
Motorola manual set
The Motorola manual sets provide the information needed to operate, install and maintain the Motorola
equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media:
• Printed hard copy.
• Electronic, as fully navigable PDF files on:

The Motorola customer support web site at:
(https://mynetworksupport.motorola.com/index.asp).
CD-ROM produced in support of a major system software release.
Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software
release, together with current versions of appropriate hardware manuals, and has additional
navigation facilities. A snapshot copy of on-line documentation is also included, though it
will not be updated in line with subsequent point releases.
The CD-ROM does not include Release Notes or documentation supporting specialist
products such as MARS or COP.
Ordering manuals and CD-ROMs
Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs.
All orders must be placed with your Motorola Local Office or Representative.
18 68P02901W23-Q
GMR amendment
GMR amendment
Changes to a manual that occur after the printing date are incorporated into the manual using
General Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals as and when
required. A GMR has the same identity as the target manual. Each GMR is identified by a
number in a sequence that starts at 01 for each manual at each issue.
GMR availability
GMRs are published as follows:
• Printed hard copy - Complete replacement content or loose leaf pages with amendment list.
Remove and replace pages in this manual, as detailed on the GMR instruction sheet.
• Motorola service web - Updated at the same time as hard copies.
• CD-ROM - Updated periodically as required.
GMR instructions
When a GMR is inserted in this manual, the amendment record below is completed to
record the GMR. Retain the instruction sheet that accompanies each GMR and insert it in
a suitable place in this manual for future reference.
68P02901W23-Q 19
GMR amendment
GMR amendment record
Record the insertion of GMRs in this manual in the following table:
GMR number Incorporated by (signature) Date

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
20 68P02901W23-Q
Chapter
1
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:
• Overview of BSS MMI functions.
• Description of command/database access security levels.
• Description of command/database parameter classification.
• List of commands that cause a device to cycle and must be used with caution.
• List of parameters that cause a device to cycle and must be used with caution.
• Guidelines on entering MMI commands and use of the correct syntax.
• Lists of MMI command availability by location and by SYSGEN mode.
• Description of the two types of GSM cell ID format.
• Descriptions of indices for devices, including data array location, bin numbers,
alarm thresholds and EAS alarm table.
• Description of SYSGEN modes of working.
68P02901W23-Q 1-1
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 such as:
Network Management
Operations & Performance Management
System Change Control
Security Management
Administration
Maintenance
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) may load code from three sources:
• GPROC.
• Operation and Maintenance Centre (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.
1-2 68P02901W23-Q
Technical Description: BSS Command Reference BSS MMI functions
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 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.
A password may be changed in accordance with the parameters shown in the chg_level
and chg_password command descriptions.
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.
68P02901W23-Q 1-3
BSS MMI functions Chapter 1: Introduction to commands
Call processing
Call processing commands are used to trace the progress of a specified call, via 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.
Miscellaneous commands
Miscellaneous commands are those that 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-4 68P02901W23-Q
Technical Description: BSS Command Reference Command/database parameter security levels
Command/database parameter security levels
Three 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 of 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 may not 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.
68P02901W23-Q 1-5
Command/database parameter types Chapter 1: Introduction to commands
Command/database parameter types
MMI commands and database parameters are classified on the basis of whether or not a user action is
required to enter the command or change the value of the database parameter.
Type A 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 may be 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-6 68P02901W23-Q
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. The user is first prompted and must
acknowledge the prompt before the device is cycled.
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-Q 1-7
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. The user is first prompted and must
acknowledge the prompt before the device is cycled.
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-8 68P02901W23-Q
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
in which the string is replaced by a specific variable (value or character string). For
example:<start_time_hour> is entered as an hour between00 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 may not be entered as mixed upper
and lower case characters in a command string. Where there are exceptions
to this rule, this is 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
The following demonstrates how MMI command examples are represented in this manual:
chg_element bsic 1 0 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
68P02901W23-Q 1-9
Entering MMI commands Chapter 1: Introduction to commands
System response
COMMAND ACCEPTED
Timeouts
If a response is not entered within 60 seconds, 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-10 68P02901W23-Q
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-1 indicates the sites at which commands can be entered; not the location
string availability for command execution.
Table 1-1 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_password X X
chg_rtf_freq X
chg_severity X X
chg_smscb_msg X
68P02901W23-Q 1-11
MMI command availability Chapter 1: Introduction to commands
Table 1-1 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_cal_data X X
disp_cbch_state X X
disp_cell X X
disp_cell_map{4040} 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
disp_enable_stat X X X
1-12 68P02901W23-Q

Locations Allowed
Command MMI ROM
BSC BTS RXCDR
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
history X X X
68P02901W23-Q 1-13

Locations Allowed
Command MMI ROM
BSC BTS RXCDR
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
unalias X X X
unconfigure_csfp X X
unequip X X
1-14 68P02901W23-Q

Locations Allowed
Command MMI ROM
BSC BTS RXCDR
unlock_device X X X
1. 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.
2. These commands are only available for MMI ROM processes running on GPROC boards.
Command availability by SYSGEN mode
Table 1-2 shows the availability of commands in the various SYSGEN modes.
Table 1-2 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
chg_element X X
chg_hop_params X X
chg_ksw_config X X
chg_level X X X X
68P02901W23-Q 1-15
Table 1-2 MMI command availability by SYSGEN mode (Continued)

Command
chg_password 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_conn X X X
disp_cal_data X
disp_cbch_state X X
disp_cell X X X
disp_cell_status X
1-16 68P02901W23-Q

Command
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
disp_time X X X
disp_trace_call X
disp_traffic X X
disp_version X
68P02901W23-Q 1-17

Command
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
swap_devices X
swfm_enable X X
sysgen_mode X X X X
time_stamp X X X
1-18 68P02901W23-Q

Command
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-Q 1-19
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.
GSM cell IDs are typically displayed in the following format:

543 021 61986 (F222h) 34944 (8880h)
Where: is:
543 MCC
021 MNC
61986 LAC
34944 CI
The LAC and CI values may also be 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.
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
1-20 68P02901W23-Q
Technical Description: BSS Command Reference GSM cell ID format
Where: is:
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 may be used
for PGSM, EGSM and DCS 1800 systems.
If the first and/or second digit of the MCC is a zero, it may be omitted from the input. The
system recognizes both of the following examples as valid format:
001 011 98765 54321
1 011 98765 54321
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 would be incorrect.
68P02901W23-Q 1-21
GSM cell ID format Chapter 1: Introduction to commands
Cell name
Each GSM cell may also be assigned a cell name using the cell_name command. The cell_name may be
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-22 68P02901W23-Q
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-3 lists the device types and associated indices.
Table 1-3 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.
Data array location
An index is used to identify the location of information in a data array.
68P02901W23-Q 1-23
Indices Chapter 1: Introduction to commands
Single index number

A single index number may identify the column in a single row array where a data element is located.
The following example shows the command string that would be 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 may be referred to as a bin. When 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 would be 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
bin_num index
The following example shows the command string that would be used to display the contents of a
bin. The index value used with the disp_element command is the bin number that was 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
Thresholds
Gauge and some counter statistics may 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 may 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
1-24 68P02901W23-Q
Technical Description: BSS Command Reference Indices
Table 1-4 lists the alarm severities.
Table 1-4 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 may be modified independently using the chg_element eas_severity command.
68P02901W23-Q 1-25
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 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.
*******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. When the system is in the SYSGEN ON mode, changes may be entered into the database
without being checked until the system is returned to its normal mode of operation.
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
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:
1-26 68P02901W23-Q
Technical Description: BSS Command Reference SYSGEN mode
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. A copy of the BSC database is stored at the OMC-R.
When a difference is detected between the database load in the OMC-R and the BSC, 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, enter the commands or make the changes to the
database as necessary.
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. This is done at the OMC-R.
7 Re-enable downloads for network elements at the OMC-R.
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.
68P02901W23-Q 1-27
SYSGEN mode Chapter 1: Introduction to commands
The clear_database command should only be used by personnel who

are fully aware of the consequences.
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. This 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. When this occurs,
the script has to be corrected and reloaded before the system is able to return 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.
It is recommended that the initial SYSGEN mode be entered 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, the initial SYSGEN
mode should be entered from the master slot of an RXCDR (011ah). If the script to be loaded is for a
BSS, the initial SYSGEN mode should be entered from the master slot of a BSC (0115h).
Safety timer
While the system is in the SYSGEN ON mode, a timer is used to insure 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-28 68P02901W23-Q
Chapter
2
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.
Statistical commands are described in Chapter 4: Statistics commands.
68P02901W23-Q 2-1
Command reference presentation Chapter 2: 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 or not 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.
2-2 68P02901W23-Q
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 2-1 lists the device literals and their descriptions.
Table 2-1 Device literals and descriptions
Literal Description
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
EAS External Alarm System
GBL Gb Link (GPRS)
GCLK Generic Clock
GDS GPRS Data Stream (GPRS)
GPROC Generic Processor
GPROC2 Generic Processor 2
GPROC3 Generic Processor 3
GSL GPRS Signalling Link (GPRS)
KSW Kilo-port Switch
LAN Local Area Network
68P02901W23-Q 2-3
Device related commands Chapter 2: Device/function related commands
Table 2-1 Device literals and descriptions (Continued)

Literal Description
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
PATH Path
PBUS Processor (MCAP) Bus
PCHN Physical Channel
PCU PCU Device (GPRS)
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 2-2 lists the specific commands as relevant to the devices.
Table 2-2 Device and command relationship
Device Commands Affected Notes

BSP equip, unequip, unlock_device, state, disp_equipment, disp_equipment includes
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, disp_equipment includes
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
2-4 68P02901W23-Q
Table 2-2 Device and command relationship (Continued)

CAGE equip, state, disp_equipment, device_audit, cage_audit Valid for GPRS only
(PCU)
CBL equip, unequip, lock_device, unlock_device, state, Valid for BSC only
disp_equipment, ins_device, reset_device
CBUS state Valid for BSC and InCell
BTS
CELL state
CIC equip, unequip, lock_device, unlock_device, state, Valid for BSC only
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, ins_device, Valid for BSC and InCell
reset_device BTS
DHP equip, unequip, lock_device, unlock_device, state, Valid for BSC and InCell
disp_equipment, ins_device, reset_device, device_audit BTS
disp_equipment includes
HVN
DPROC equip, unequip, lock_device, unlock_device, state, Valid for GPRS only
disp_equipment, ins_device, reset_device, device_audit
DRI equip, unequip, lock_device, unlock_device, state, disp_equipment includes
disp_equipment, ins_device, reset_device, device_audit, HVN
shutdown_device
DYNET equip Valid for BSC and InCell
BTS
unequip, disp_equipment Valid for BSC only
EAS equip, unequip, lock_device, unlock_device, state,
GBL equip, unequip, lock_device, unlock_device, state, Valid for GPRS only
GCLK equip, unequip, lock_device, unlock_device, state, Valid for BSC and InCell
disp_equipment, ins_device, reset_device, swap_devices, BTS.
device_audit disp_equipment includes
HVN
GDS equip, unequip, lock_device, unlock_device, state, Valid for GPRS only
68P02901W23-Q 2-5
Device related commands Chapter 2: Device/function related commands

GPROC equip, unequip, unlock_device, state, disp_equipment, Valid for BSC and InCell
device_audit BTS.
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, disp_equipment, Valid for BSC and InCell
device_audit BTS.
HVN
BTS.
device.
GPROC3 equip, unequip, unlock_device, state, disp_equipment, Valid for BSC and InCell
device_audit BTS.
HVN
BTS.
device.
GSL equip, unequip, lock_device, unlock_device, state, GPRS only
KSW equip, unequip, unlock_device, state, disp_equipment, Valid for BSC and InCell
device_audit, ins_device BTS.
HVN
lock_device, reset_device Valid for BSC and InCell
BTS.
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, state, disp_equipment includes
disp_equipment, ins_device, device_audit HVN
reset_device Causes a hard reset of the
device.
2-6 68P02901W23-Q

MTL equip, unequip, lock_device, unlock_device, state, Valid for BSC only
disp_equipment, ins_device, reset_device, shutdown_device
OML equip, unequip, lock_device, unlock_device, state, Valid for BSC only
PATH equip, unequip, lock_device, unlock_device, state, Valid for BSC only
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, state, Valid for GPRS only
disp_equipment, ins_device, reset_device site_audit
PSP equip, state, disp_equipment, device_audit, unequip Valid for GPRS only
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, state, Valid for BSC only
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, state, Valid for BSC only
68P02901W23-Q 2-7
Device identifiers Chapter 2: Device/function related commands
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, zero(s) must be entered
for the remaining device identifier parameter(s) as place holders.
Device ID requirements
Table 2-3 lists and defines the device ID requirements.
Table 2-3 Device ID requirements
Device
Range Definition
Names/IDs
ABSS Associated Base Station Processor
device ID 1 0 to 128 Corresponds to the BSS network entity that this device represents
device ID 2 0 Serves as place holder
AXCDR Associated XCDR
device ID 1 0 to 128 Corresponds to the RXCDR network entity that this device represents
BCUP BSS Controller Unit Power Supply per cage
device ID 1 0 to 15 Identifies the cage number
device ID 2 0 to 2 Identifies which power supply (of the three possible per cage)
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)
BSS Base Station System
device ID 1 0 to 50 Identifies BSS
BTP Base Transceiver Processor, BTS
2-8 68P02901W23-Q
Technical Description: BSS Command Reference Device identifiers
Table 2-3 Device ID requirements (Continued)

Device
Range Definition
Names/IDs
device ID 1 1 Identifies which BTP board is active and which is redundant (standby)
(None at a BSC or RXCDR)
CAB CABinet
device ID 1 0 to 20 Identifies cabinet number
CAGE CAGE
device ID 1 0 to 15 Identifies the value at which the LANX card, dial is set.
device ID 1 0 Optional entry (None at a BTS or RXCDR)
CBUS Clock BUS
device ID 1 0 to 15 Identifies the cage where a specific GCLK is located
device ID 2 0 or 1 Identifies the GCLK
COMB COMBiner
device ID 1 0 to 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)
CSFP Code Storage Facility Processor
device ID 1 10 CSFP identifier (Only at a BSC) - not M-CellM-cell, automatically
equipped/unequipped.
DHP Digital radio Host Processor, BTS
device ID 1 0 to 5 Identifies a digital module shelf (cage number) in a specific cabinet. (None
at an RXCDR)
device ID 2 0 to 7 Identifies which DHP board is active and which is redundant (standby)
68P02901W23-Q 2-9

Device
Range Definition
Names/IDs
DPROC Digital Processor (GPRS)
device ID 1 1 to 6 or Identifies a specific DPROC Board
11 to 16
device ID 1 0 to 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 to 11 Identifies a specific DRI board
DYNET Dynamic Network of BTSs
device ID 1 0 to 19 Identifies the DYNET group (None at a BTS or RXCDR)
device ID 2 0 to 2 The unique device within the DYNET group
device ID 1 0 to 7 Identifies a specific PIX card at a site - not M-Cell
0 to 15 M-Cell
GBL Gb Link (GPRS)
device ID 1 0 to 11 Identifies a specific GBL link
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
M-cell, automatically equipped/unequipped.
0
GDS GPRS Data Stream (GPRS)
device ID 1 0 to 37 Identifies a specific GPRS data stream
2-10 68P02901W23-Q

Device
Range Definition
Names/IDs
GPROC Generic PROCessor, device used for functions
device ID 1 0 to 111 Identifies a specific GPROC board
GSL GPRS Signalling Link (GPRS)
device ID 1 0 to 11 Identifies a specific GPRS signalling link
KSW Kiloport SWitch
device ID 1 0 to 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; 1 is slot 1)
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).
MMS The E1/T1 Mbit/s line on a Multiple Serial Interface board
device ID 1 0 to 55 Matches the first id of the host MSI with which it is associated (BSC or
RXCDR)
9 BTS only: not M-Cell
3 BTS only: M-Cell6
1 BTS only: M-Cell2
0 BTS only: M-Cellmicro
device ID 2 0 or 1 Identifies a specific MMS
MSI Multiple Serial Interface board
device ID 1 Identifies a specific MSI board:
0 to 55 BSC
0 to 71 RXCDR
9 BTS only: not M-Cell
3 BTS only: M-Cell6
1 BTS only: M-Cell2
0 BTS only: M-Cellmicro
68P02901W23-Q 2-11

Device
Range Definition
Names/IDs
MTL Message Transfer Link
device ID 1 0 to 15 Identifies a specific MTP link (per ITU-TSS spec.)
OML Operations and Maintenance Link
device ID 1 0 to 3 Identifies a specific connection (link) between the BSC and the OMC-R
(BSC or RXCDR)
PATH
device ID 1 1 to 100 Identifies the terminating site (BSC only)
device ID 2 0 to 9 Identifies a unique PATH ID
PBUS Processor (MCAP) BUS
device ID 1 0 to 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)
RSL Radio System Link
device ID 1 1 to 100 Identifies the site to which the RSL is connecting (BSC only)
device ID 2 0 to 7 Identifies a specific link set (not M-Cell)
5 M-Cell2 and M-Cell6
1 M-Cellmicro
RTF Receive Transmit Function
device ID 1 0 to 5 Identifies the cell group
device ID 2 0 to 11 Identifies a unique function within the cell group
RXCDR Remote transcoder
device ID 1 0 to 128
SITE BTS SITE
device ID 1 0 to 100 Identifies the site for which commands are being executed
2-12 68P02901W23-Q

Device
Range Definition
Names/IDs
SBUS Serial BUS
device ID 2 0 or 1 Identifies which SBUS ( A side or B side) is active and which is redundant
(standby)
TBUS TDM BUS
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)
XBL RXCDR to BSC Fault Management Link
device ID 1 0 to 9 Identifies a specific connection (link) between the RXCDR and the BSC
68P02901W23-Q 2-13
Function related commands Chapter 2: Device/function related commands
Function related commands
Table 2-4 lists the functions that can be affected by function-related commands.
• 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 2-4 Function related commands
Device name / Commands

Literal
description unequip equip state disp_equipment
DYNET DYnamic NETwork X X X X
of BTSs
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
2-14 68P02901W23-Q
Technical Description: BSS Command Reference Function identifiers
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, zero(s) must be
entered for the remaining function identifier(s) as place holders.
Function ID requirements
Table 2-5 lists and defines the Function ID requirements.
Table 2-5 Function ID requirements
Device
Range Definition
Names / IDs
BTF Base Transceiver Function (BTS only)
function ID 1 0 to 2 Identifies maximum number of DRIs supported by this BTF (not M-Cell)
1 M-Cell only
function ID 2 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)
LCF Link Control Function (BSC only)
function ID 1 0 to 24 Identifies specific control links to the MSC and/or the BTS
RTF Receive Transmit Function (BSC and BTS only)
function ID 1 0 to 29 Identifies the RTF group to which the RTF belongs
function ID 2 0 to 24 Identifies a specific RTF function
68P02901W23-Q 2-15
Slots Chapter 2: Device/function related commands
Slots
Cage slots are allocated to devices dependent on the site function.
Valid slots table
Table 2-6 lists the cage slots that are valid for the software supported devices.
Table 2-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 to 25 18 to 25 18 to 25 25 or 26
cage 0 to 13 cage 0 to 13 cage 2 to 15 cage 0 to 13
DHP 18 to 25 N/A 18 to 25 N/A
cage 0 to 13 cage 2 - 15
DRI 7, 9, 11, 13, 15, 17 N/A 7, 9, 11, 13, 15, 17 N/A
EAS 15 to 18 15 to 18 15 to 18 15 to 18
(daughter slots) (daughter slots) (daughter slots) (daughter slots)
GCLK device_id1 = 0 device_id = 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 to 25 18 to 25 18 to 25 25 or 26
cage 0 to 13 cage 0 to 13 cage 2 to 15 cage 0 to 13
MSI 6 to 17 6 to 17 MSI type = 0 MSI type = 0
slot = 6 to 17 slot = 6 to 10
or or
MSI type = 1, 255 MSI type = 1, 255
(slot = N/A) slot = 6 to 24
2-16 68P02901W23-Q
Technical Description: BSS Command Reference equip/unequip command matrix
equip/unequip command matrix
Table 2-7 is a matrix showing which devices and functions can be equipped and unequipped
inside and outside of the SYSGEN ON mode.
Table 2-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 this is
the standby device
BTP Supported Supported Supported Supported only if this is
the standby device
CAB Supported Type B command: lock Unsupported Unsupported
the site before entering
the equip or unequip
commands
CAGE Supported Type B command: lock Unsupported Unsupported
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
DYNET 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: MSIs of type NIU2 (that is, a MSI at a Horizon II site) are not supported by the equip/unequip
commands.
MTL Supported Unsupported Supported Supported
OMF Supported Supported Supported Unsupported
OML Supported Unsupported Supported Supported
PATH Supported Supported Supported Supported
68P02901W23-Q 2-17
equip/unequip command matrix Chapter 2: Device/function related commands
Table 2-7 Equip/Unequip command matrix (Continued)

Device/ Equip in Equip outside Unequip in Unequip outside
Function SYSGEN SYSGEN SYSGEN SYSGEN
RSL Supported Supported Supported Supported
RTF Supported Supported Supported Supported
SITE Supported Supported Supported Supported
XBL Supported Supported Supported Supported
2-18 68P02901W23-Q
Technical Description: BSS Command Reference Alarm devices
Alarm devices
Table 2-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 2-8 Alarm devices
Device Name Valid Alarm Reporting Device Valid Alarm Throttle Device
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
DYNET YES NO
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
PATH YES NO
PBUS YES NO
68P02901W23-Q 2-19
Alarm devices Chapter 2: Device/function related commands
Table 2-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
2-20 68P02901W23-Q
Technical Description: BSS Command Reference add_cell
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_id parameters. After the command is entered, a series of prompts to define the cell are
displayed. The prompted parameters are described in the Related Information at the end of this section.
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 already 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 already 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 of the parameter valid range is typed, the default value is used by the system.
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 2
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.
Enter this command at the BSC only. This command will not work at a BTS
site. Contact the OMC-R for help.
Format
Syntax
add_cell <gsm_cell_id> <location> [cell_name]
68P02901W23-Q 2-21
add_cell Chapter 2: Device/function related commands
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.
2-22 68P02901W23-Q
A cell_name as defined by the cell_name command is not valid in add_cell commands.

location
Specifies the location of the cell:
1 to 120 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 may be from one to 31 alphanumeric characters. The dash character may be used
as a separator. The underscore character may not be used as part of the name or as a separator.
Double quotation marks may not be used as part of a cell name.
Cell names may 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, 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.
68P02901W23-Q 2-23
add_cell 5 4 3 2 1 61986 34944 5
Where: is:
5 4 3 2 1 61986 34944 GSM cell ID
5 location
System response
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
References
Related information
Table 2-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 add_cell
command prompts table exactly as presented, where x is the parameter value. For example, a CRM wait
indication parameter value of 5 may 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 may 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 responses 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.
2-24 68P02901W23-Q
The copy_cell command description includes two alphabetical listings of which parameters
are included for that command and which are not included.
Table 2-9 add_cell command prompts
Prompt Input Range Default
Enter base station bsic=x 0 to 63 None

identity code:
Enter the Frequency frequency_type=x 1 (pgsm) None
Type: 2 (egsm)
4 (dcs1800)
8 (pcs1900)
16 (gsm850)
Use numeric values
or text string.
Enter wait indication wait_indication_parameters=x 0 to 255 5
parameters:
Enter common control ccch_conf=x 0, 1, 2, 4, or 6 0
channel configuration:
Enter blocks reserved bs_ag_blks_res=x 0 to 7 0
for access grant:
Enter multiframes bs_pa_mfrms=x 0 to 7 0
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 to 44 8
preferred: (if ccch_conf=1).
8 to 48
(if ccch_conf1)
Enter enable incoming en_incom_ho=x 0 or 1 1
handover:
Enter intra cell intra_cell_handover_allowed=x 0 to 2 1
handover allowed:
Enter inter cell inter_cell_handover_allowed=x 0 to 3 1
handover allowed:
Enter number of number_of_preferred_cells=x 1 to 16 16
preferred cells:
Enter handover margin ho_margin_def=x -63 to 63 8
default:
Enter handover handover_recognized_period=x 2 to 64 2
recognized period:
68P02901W23-Q 2-25
Table 2-9 add_cell command prompts (Continued)
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 sdcch_ho=x 0 or 1 1
for SDCCH handover:
Enter alternate SDCCH sdcch_timer_ho=x 1 to 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 ms_distance_allowed=x 0 or 1 0
allowed:
Enter alternate flag mspwr_alg=x 0 or 1 0
for MS power control
processing:
Enter handover power handover_power_level=x 2 to 19 None
level:
Enter power control pwrc=x 0 or 1 1
indicator for hopping
through BCCH:
Enter interference intave=x 1 to 31 8
measurement averaging
period (intave):
Enter timing advance timing_advance_period=x 1 to 31 4
period:
Enter MS power control ms_p_con_interval=x 0 to 31 2
period:
Enter MS timeout for ms_p_con_ack=x 0 to 31 2
MS power control:
Enter MS power control ms_power_control_allowed=x 0 or 1 1
allowed:
Enter BTS power bts_p_con_interval=x 0 to 31 2
control interval:
Enter BTS timeout for bts_p_con_ack=x 0 to 31 1
BTS power control:
Enter BTS power bts_power_control_allowed=x 0 or 1 0
control allowed: (0 for M-Cellmicro)
2-26 68P02901W23-Q
Enter power increment pow_inc_step_size_ul=x 2 to 14 EVEN 2

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

n1:
n2:
n3:
n4:
n5:
Enter RSS decision alg decision_1_n6=x 1 to 31 1
1 n6:
1 n7:
1 n8:
Enter decision alg decision_1_ncell_rxlev_av_h_ 0 to 3 0
1 ncell rxlev avg h calc=x
calc:
Enter decision alg 1 decision_1_p1=x 1 to 31 1
p1:
p2:
p3:
p4:
p5:
p6:
p7:
p8:
Enter decision alg 1 decision_1_p_bgt_rxlev_av_h=x 0 to 3 0
power budget rxlev:
Enter decision alg 1 decision_1_tim_adv_av_alg=x 0 to 3 0
timing advance alg:
Enter decision alg 1 decision_1_ul_rxlev_av_h=x 0 to 3 0
ul rxlev avg h:
Enter decision alg 1 decision_1_ul_rxlev_av_ih=x 0 to 3 0
ul rxlev avg ih:
2-28 68P02901W23-Q
Enter decision alg 1 decision_1_ul_rxlev_av_p=x 0 to 3 0

ul rxlev avg p:
Enter decision alg 1 decision_1_ul_rxqual_av_h=x 0 to 3 0
ul rxqual avg h:
Enter decision alg 1 decision_1_ul_rxqual_av_p=x 0 to 3 0
ul rxqual avg p:
Enter quality band alt_qual_proc=x 0 or 1 0
processing allowed:
Enter power con- l_rxqual_ul_p=x If alt_qual_proc = 0, 226 BER
trol threshold 0 to 1810. or
l_rxqual_ul_p: If alt_qual_proc = 1, 4 QBand
0 to 7.
Enter power con- l_rxqual_dl_p=x If alt_qual_proc = 0, 226 BER
l_rxqual_dl_p: If alt_qual_proc = 1, 4 QBand
0 to 7.
Enter power con- u_rxqual_ul_p=x If alt_qual_proc = 0, 28 BER
u_rxqual_ul_p: If alt_qual_proc = 1, 1 QBand
0 to 7.
Enter power con- u_rxqual_dl_p=x If alt_qual_proc = 0, 28 BER
u_rxqual_dl_p: If alt_qual_proc = 1, 1 QBand
0 to 7.
Enter handover thresh- l_rxqual_ul_h=x If alt_qual_proc = 0, 453 BER
old l_rxqual_ul_h: 0 to 1810. or
If alt_qual_proc = 1, 5 QBand
0 to 7.
Enter handover thresh- l_rxqual_dl_h=x If alt_qual_proc = 0, 453 BER
old l_rxqual_dl_h: 0 to 1810. or
If alt_qual_proc = 1, 5 QBand
0 to 7.
Enter handover thresh- l_rxlev_ul_h=x 0 to 63 10
old l_rxlev_ul_h:
Enter handover thresh- l_rxlev_dl_h=x 0 to 63 1
old l_rxlev_dl_h:
Enter handover thresh- u_rxlev_ul_ih=x 0 to 63 45
old u_rxlev_ul_ih:
Enter handover thresh- u_rxlev_dl_ih=x 0 to 63 45
old u_rxlev_dl_ih:
68P02901W23-Q 2-29
Enter handover ms_max_range=x 0 to 63 (only if None

threshold mobile max ext_range_cell=0)
range: 0 to 219 (if
ext_range_cell=1)
Enter power con- l_rxlev_ul_p=x 0 to 63 30
trol threshold
l_rxlev_ul_p:
Enter power con- l_rxlev_dl_p=x 0 to 63 30
trol threshold
l_rxlev_dl_p:
Enter power con- u_rxlev_ul_p=x 0 to 63 40
trol threshold
u_rxlev_ul_p:
Enter power con- u_rxlev_dl_p=x 0 to 63 40
trol threshold
u_rxlev_dl_p:
Enter Alternate flag missing_rpt=x 0 or 1 0
for missing report:
Enter Alternate flag ba_alloc_proc=x 0 or 1 0
for BA allocating
process:
Enter RSS link fail: link_fail=x 0 to 15 4
Enter link about to link_about_to_fail=x 0 to 15 2
fail:
Enter Alternate flag full_pwr_rfloss=x 0 or 1 0
for 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 to 65535 0
class:
Enter emergency class emergency_class_switch=x 0 or 1 0
switch:
Enter report resource report_resource_tch_f_high_ 0 to 255 2
TCH full high water water_mark=x
mark:
Enter report resource report_resource_tch_f_low_ 0 to 255 12
TCH full low water water_mark=x
mark:
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. The system rejects the add_cell command if the
report_resource_tch_f_high_ water_mark is greater than the report_resource_tch_f_low_water_mark.
Enter receive level rxlev_access_min=x 0 to 63 None
access minimum:
2-30 68P02901W23-Q
Enter uplink dtx dtx_required=x 0 to 2 2

preference:
Enter IMSI attach attach_detach=x 0 or 1 0
detach:
Enter NCC of PLMN ncc_of_plmn_allowed=x 0 to 255 255
allowed:
Enter maximum max_retran=x 0 to 3 0
retransmissions on
RACH:
Enter maximum mobile ms_txpwr_max_cch=x 5 to 39 odd only 2
transmit power on (PGSM and EGSM)
CCCH: 0 to 36 even only
(DCS1800)
33 (PCS1900)
Enter tx_integer tx_integer=x 0 to 15 4
for RACH retransmit
spacing:
Enter radio link radio_link_timeout=x 0 to 15 4
timeout:
Enter MS reestablish reestablish_allowed=x 0 or 1 0
allowed:
Enter cell reselect cell_reselect_hysteresis=x 0 to 7 None
hysteresis:
Enter C2 cell cell_reselect_param_ind=x 0 or 1 0
reselection parameter
indicator:
Enter C2 cell bar cell_bar_qualify=x 0 or 1 0
qualify:
Enter C2 cell cell_reselect_offset=x 0 to 63 0
reselection offset:
Enter C2 temporary temporary_offset=x 0 to 7 0
offset:
Enter C2 penalty time: penalty_time=x 0 to 31 0
Enter rapid power down rapid_pwr_down=x 0 or 1 0
procedure active:
Enter rapid power down rpd_trigger=x 0 to 63 45
trigger threshold:
Enter rapid power down rpd_offset=x 0 to 63 8
level offset:
Enter rapid power down rpd_period=x 1 to 32 2
averaging period:
68P02901W23-Q 2-31
Related commands
"copy_cell" on page 2-157, "del_cell" on page 2-169, "disp_cell" on page 2-206, "disp_gsm_cells"
on page 2-254, "freq_types_allowed" on page 2-378.
2-32 68P02901W23-Q
Technical Description: BSS Command Reference add_conn
add_conn
Description
The add_conn command adds MMS connectivity between the RXCDR and the BSS.
Connectivity may be added for a maximum of 21 MMSs at a BSC or RXCDR regardless
of how many RXCDRs or BSSs are connected.
This command allows the operator to specify the E1/T1 connectivity information identifying which RXCDR
is associated with the E1/T1 link and the device identity within the RXCDR to which the E1/T1 link is
connected. This connectivity information must be specified for each E1/T1 link connecting to an RXCDR.
Security level 2
Supported by OMC-C 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.
remote_mms_id_2
68P02901W23-Q 2-33
add_conn Chapter 2: Device/function related commands
Second identifier of the MMS at the remote site.

The add_conn command can be executed from either the BSC or RXCDR. Table 2-10 shows the ranges
for several input parameters dependant on where the command is executed.
Table 2-10 add_conn valid ranges
Execution location
Inputparameter
BSC RXCDR
local_mms_id_1 0 to 55 0 to 123
local_mms_id_2 0 or 1 0 or 1
network_entity_id 1 to 254 1 to 128
remote_mms_id_1 0 to 123 0 to 55
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, which is represented by 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 2-172, "disp_conn" on page 2-224, "mod_conn" on page 2-392
2-34 68P02901W23-Q
Technical Description: BSS Command Reference add_neighbor
add_neighbor
Description
The add_neighbor command adds a cell to an existing cell Neighbour Cell List.
A maximum of 64 neighbours can be added to a cell. A maximum of 32 neighbours
may be added to the BA_SACCH list.
The exception to this rule is when the element egsm_bcch_sd is enabled and the source
cell frequency is either EGSM or DCS1800:
• If the element egsm_bcch_sd is enabled and the source cell frequency is EGSM,
see Table 2-11 for the limitations on the maximum neighbours that can be added
to the EGSM frequency type source cell.
• If the element egsm_bcch_sd is enabled and the source cell frequency is DCS1800,
see Table 2-12 for the limitations on the maximum neighbours that can be added
to the DCS1800 frequency type source cell.
The neighbour frequency can change from one range to another (with respect to Table 2-11 and Table 2-12)
when adding or deleting a neighbour for a particular source cell. Hence the maximum number of neighbours
that can be added to a source cell may change depending upon the frequency range of the neighbour cells:
• If the source frequency type is DCS1800, a neighbour may not have a frequency
type of PCS1900.If the source frequency type is PCS1900, a neighbour may
not have a frequency type of DCS1800.
• If a DCS1800 neighbour exists in a neighbour list, no PCS1900 neighbours may be added.
• If a PCS1900 neighbour exists in a neighbour list, no DCS1800 neighbours may be added.
Table 2-11 lists the frequency range and maximum number of neighbours for an EGSM source cell.
Table 2-11 Neighbour Frequency and number with EGSM source cell
Neighbour frequency
Maximum number of neighbours
range
1 to 124 64
975 to 1023 49
0,1 to 124 64
0, 975 to 1023 50 if source frequency is in the EGSM frequency, that is: 0, 975-1023
17 if source frequency is in the PGSM frequency, that is: 1-124
1 to 124, 975 to 1023 64 if source frequency is not zero;
64 - e if source frequency is 0; where e (the number of EGSM frequencies) is
less than or equal to 16.
68P02901W23-Q 2-35
add_neighbor Chapter 2: Device/function related commands
Table 2-11 Neighbour Frequency and number with EGSM source cell (Continued)
Neighbour frequency
Maximum number of neighbours
range
0, 975 to 1023 64 - e if source frequency is in the EGSM frequency range, where e (the
number of EGSM frequencies) is less than or equal to 16.
1 to 124 64 - e if source frequency is in the PGSM frequency range, where e (the
number of PGSM frequencies) is less than or equal to 17.
Table 2-12 lists the frequency range and maximum number of neighbours for a DCS 1800 source cell.
Table 2-12 Neighbour Frequency and number with DCS1800 source cell
Neighbour frequency range Maximum number of neighbours

1 to 124 64
975 to 1023 49
0, 1 to 124 17
0, 975 to 1023 17
1 to 124 and 975 to 1023 16
0, 1 to 124 and 975 to 1023 17
The BA_SACCH list can have up to 32 neighbours. A total of 64 neighbours can be created
but a maximum of 32 can be on the BA_BCCH list only.
After the command is entered, a series of prompts are presented where parameters defining the neighbour cell
are entered. The prompted parameters are described in the Related Information at the end of this section.
The required input parameters depend on whether or not the neighbour cell is internal
to the BSS or external to the BSS.
This command permits neighbour BCCH frequencies in the GSM Extension band provided
the egsm_bcch_sd parameter is enabled.
If the Inter_RAT (Radio Access Technology) handover feature is unrestricted, this command
supports the UMTS UTRAN cell identity format.
Security level 2
2-36 68P02901W23-Q
Prerequisites To be on the Neighbour Cell List, a cell must be the destination of

handovers from the Neighbour List owner.
Synchronized handovers are allowed only between cells that are at
the same site.
For a PGSM or EGSM site, only external neighbour cells with
BCCH ARFCNs in the range 1 to 124 may be added.
For a GSM 850 site, only external neighbour cells with BCCH
ARFCNs in the following ranges may be added: 0 to 124, 128 to
251, 512 to 885, and 975 to 1023.
For handovers to UMTS UTRAN cells, the Inter-RAT handover
option must be unrestricted.
Operator action Reply to prompts as displayed, directly or in a script.
Enter this command at the BSC only. This command does not work at a BTS
Format
Syntax
add_neighbor <source_cell_id> <neighbor_cell_id> <placement>
The cell_name can be used for the neighbour when the neighbour is internal.
Input parameters
source_cell_id
GSM Cell ID of the cell to to which a neighbour cell is to be assigned.
• The system being used (PGSM, EGSM, DCS1800, PCS1900, GSM 850)
GSM cell id format has been enabled.
• Whether the cell is a UMTS UTRAN cell.
The name of the cell created using the cell_name command may be entered in place of the cell_id.
When the cell name is entered, it must be placed inside 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 neighbour cell.
68P02901W23-Q 2-37
When the cell name is entered, it must be placed inside double quotation marks. The cell_name may
only be entered in place of the neighbor_cell_id for internal neighbour cells.
Only PCS1900 and GSM 850 systems can use a three digit MNC.
The string test <num> may be entered for this field where <num> is a value from 1 to 64. This permits test
neighbours to be added to the BA_SACCH and/or BA_BCCH lists. When a test neighbour 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 neighbour 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
5-68 and "ncc_of_plmn_allowed" on page 5-544 for more information.
placement
internal The neighbour cell to be added is inside the BSS
external The neighbour cell to be added is outside of the BSS
umts_fdd The neighbour cell is a UMTS UTRAN cell.
Examples
Example 1
In this example, a cell with ID 5 4 3 2 1 61986 34945 is added to the Neighbour Cell List of a cell
with ID 5 4 3 2 1 61986 34944. The example demonstrates adding a cell to the Neighbour Cell List
that is internal to that neighbour 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
System response
COMMAND ACCEPTED
After verification of the command, the MMI prompts for the required parameters to describe
the neighbour cell being added (see Related information).
Example 2
In this example, a cell with ID 5 4 3 2 1 61986 34944 is added to the Neighbour Cell List of a cell
with ID 5 4 3 2 1 71543 12444. The example demonstrates adding a cell to the Neighbour Cell List
that is external to that neighbour 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.
2-38 68P02901W23-Q
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
Example 3
In this example, a cell with ID 5 4 3 2 1 61986 34945 is added to the internal Neighbour
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
Example 4
In this example, a PCS1900 cell with ID 543 721 61986 34945 is added to the internal
Neighbour 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
68P02901W23-Q 2-39
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 2-13 lists the command prompts for the add_neighbor command.
Table 2-13 add_neighbor command prompts
Prompt Range Default Notes

Add neighbor to the BA yes yes These three prompts
BCCH list (yes/no)? no appear only if the
Network Controlled
Add neighbor to the BA yes yes
SACCH list (yes/no)? Cell Reselection feature
no
(NCCR) is unrestricted.
Add neighbor to the BAGPRS yes yes
list (yes/no)? no
Enter the neighbor cell pgsmegsmdcs None N/A for internal
frequency type: 1800pcs 1900gsm neighbours.
850
Enable synchronization: 1 (Yes) 0 N/A for external
0 (No) neighbours
Enter the BCCH frequency 1 to 124 for PGSM None. A value N/A for internal
number: 0, 1 to 124, 975 to MUST be neighbours
1023 for EGSM entered at this EGSM BCCH frequencies
512 to 885 for prompt. 0, 975 to 1023 are
DCS1800 not available when the
512 to 810 for egsm_bcch_sd parameter
PCS1900 is disabled.
Enter base station 0 to 63 None. A value N/A for internal
identity code (bsic): MUST be neighbours
entered at this
prompt.
Enter MS transmit power 5 to 39 (odd values 39 for PGSM N/A for internal
maximum: only) for PGSM and and EGSM neighbours
EGSM 36 for
0 to 36 (even values DCS180033
only) for DCS1800 for PCS1900
0 to 32 (even values
only) and 33, for
PCS1900
Enter neighbor receive 0 to 63 rxlev_min_def Required for external
level minimum: of neighbour neighbours
cell
2-40 68P02901W23-Q
Table 2-13 add_neighbor command prompts (Continued)

Enter neighbor handover -63 to 63 ho_mar- Required for external
margin: gin_def of neighbours
neighbour cell Refer to the description
of the ho_margin_def
parameter.
Enter the power budget 1 to 31 8
surrounding cell hreqave:
Enable adjacent channel 1 (Yes) 0 (No) NA if Microcell is not
interference avoidance 0 (No) purchased
test?:
Enter rxlev difference -63 to 63 0 NA if Microcell is not
for adjacent channel purchased
interference avoidance This prompt only applies if
test:
the previous answer was 1
Enter the power budget 1 to 7 1 N/A if Microcell is not
algorithm type: purchased
Enter the adjacent channel -63 to 63 ho_mar- This prompt only appears
interference detection gin_cell if pbgt_alg_type=7.
handover margin:
Enter the uplink receive 0 to 255 None. A value N/A if Microcell is not
level threshold of the MUST be purchased and
serving cell: entered at this pbgt_alg_type 0 3
prompt.
Enter the downlink receive 0 to 255 None N/A if Microcell is not
level threshold of the purchased and
serving cell: pbgt_alg_type 0 3
Enter the qualifying time 0 to 255 0 SACCH N/A if Microcell is not
threshold: periods purchased and
pbgt_alg_type 0 4
Enter the qualifying delay 0 to 255 0 SACCH N/A if Microcell is not
time: periods purchased and
pbgt_alg_type 0 5
Enter the neighbor cell 0 to 63 None. A value N/A if Microcell is not
receive level threshold: MUST be purchased and
entered at this pbgt_alg_type 0 5
prompt.
Enter the delay time: 0 to 255 0 SACCH N/A if Microcell is not
periods purchased and
pbgt_alg_type 0 6
Enter the handover static 0 to 127 0 N/A if Microcell is not
offset: purchased and
pbgt_alg_type 0 6
Enter the handover dynamic 0 to 127 0 N/A if Microcell is not
offset: purchased and
pbgt_alg_type 0 6
68P02901W23-Q 2-41
Table 2-13 add_neighbor command prompts (Continued)

Enter neighbor congestion -63 to 63To disable ho_mar- Value should be less
handover margin: congestion handovers gin_cell of than or equal to the
to this neighbour, set neighbour cell ho_margin_cell of the
the value to 63 neighbour cell.
This prompt is only
presented if directed retry
or congestion relief is
purchased.
Is directed retry allowed 1 (Yes) 1 N/A when adding internal
at this external neighbor 0 (No) neighbours
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 neighbour is being
added to the SACCH list
Enter the threshold for 0 to 63 0 Only prompted if “Does
inner zone handover: the neighbor have a
carrier with an interfering
frequency?" = 1 (yes).
Enter the margin for inner 0 to 63 0 Only prompted if “Does
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.
Related commands
"add_cell" on page 2-21, "copy_cell" on page 2-157, "del_cell" on page 2-169, "del_neighbor"
on page 2-174, "disp_cell" on page 2-206, "disp_gsm_cells" on page 2-254, "disp_neighbor"
on page 2-282, "modify_neighbor" on page 2-397.
2-42 68P02901W23-Q
Technical Description: BSS Command Reference add_nsvc
add_nsvc
Description
The add_nsvc command enables the user to map a Network Service-Virtual Connection Identifier
(NSVCI) and Data Link Connection Identifier (DLCI) to a specific GBL.
Security level 2
Prerequisites The GPRS feature must be unrestricted.
Format
Syntax
add_nsvc <pcu_n> <ns_vci> <gbl_id> <dlci>
Input parameters
pcu_n pcu, pcu_0 to pcu_2 The PCU at which the NSVCI or DLCI are to be mapped
to the specific GBL.
ns_vci 0 to 65535 The virtual connection on a GLB:
Unique identifier of the NSVCI mapping, and identifier of
the object.
gbl_id 0 to 3 Object identifier of the GBL
dlci 16 to 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:
Example
The following example adds NSVCI 10 to GBL 0 with a DLCI of 50 on PCU 1:
68P02901W23-Q 2-43
add_nsvc Chapter 2: Device/function related commands
add_nsvc pcu_1 10 0 50
Where: is:
pcu_1 PCU 1
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
References
Related commands
"del_nsvc" on page 2-178, "mod_nsvc" on page 2-395.
2-44 68P02901W23-Q
Technical Description: BSS Command Reference add_rtf_path
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 16K 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. PATHs
for such sites are defined by the equip DYNET command. RTFs automatically use the PATH(s) defined
for these types of sites. RTFs do not use PATH(s) equipped by the operator for these types of sites.
Security level 2
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.
Format
Syntax
add_rtf_path <location> <1st_RTF_identifier> <2nd_RTF_identi-
fier> <unique_PATH_identifier>
Input parameters
location
Indicates the number of the BTS where the RTF is located. The range of values is 1 to 120.
68P02901W23-Q 2-45
add_rtf_path Chapter 2: Device/function related commands
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 2-163, "del_rtf_path" on page 2-180, "disp_rtf_path" on page
2-308, "disp_traffic" on page 2-321.
2-46 68P02901W23-Q
Technical Description: BSS Command Reference alarm_mode
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
Prerequisites The GPRS must be unrestricted in order to assess a PCU site.
Format
Syntax
alarm_mode <location>[,<location>,<location>...] [<mode>]
Input parameters
location
Specifies the site location:
0 or bsc BSC
1 to 120 BTS
pcu, pcu_0 to pcu_2 PCU
mode
on alarm reporting activated
off alarm reporting deactivated
Example 1
Specifies alarm mode as On for BSC 0:
alarm_mode 0 on
68P02901W23-Q 2-47
alarm_mode Chapter 2: Device/function related commands
System response
SITE MODE
----- -----------------------
0 Alarm reporting enabled
Example 2
Specifies alarm mode as Off for PCU site 0 and PCU site 1:
alarm_mode pcu_0 pcu_1 off
System response
SITE MODE
----- ------------------------
pcu_0 Alarm reporting disabled
pcu_1 Alarm reporting disabled
2-48 68P02901W23-Q
Technical Description: BSS Command Reference assess
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 should 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 may 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: (a) one or more alarms active against it; or (b) one or more devices still OOS;
or (c) both active alarms and OOS devices. Only one report is displayed if wild cards are used and
all devices that match the wild cards went 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 should be
assigned to the appropriate devices and cease to impact 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:
The Alarm Device is the primary alarm for the reconfiguration. The alarm is displayed even
though it may have cleared already. An alarm and the alarm device is not displayed for a
reconfiguration that does not have an active alarm yet has OOS devices, but instead the message
No Primary Alarm for this Reconfiguration is displayed.
A Functional Unit (and its status) is displayed for each FU which was impacted by the
reconfiguration and had a non-CLEAR status at the end of the reconfiguration.
68P02901W23-Q 2-49
assess Chapter 2: Device/function related commands
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.
The line No devices remain OOS as a result of this configuration, displays instead
of the previous line if the FU no longer has any OOS devices impacting it.
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
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
0 or bsc BSC
1 to 120 BTS
all All active sites
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.
2-50 68P02901W23-Q
Examples
Example 1
In the following example, BSC has just been initialized. The operator wishes to
see if there are any problems at the BSC:
MMI-RAM 0115 -> 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:
MMI-RAM 0115 -> assess 0 oml 0
Where: is:
0 location
oml device name
0 device ID
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
OML 0 0 0 DISABLED UNLOCKED MMS Not In Service
OML 1 0 0 DISABLED UNLOCKED MMS Not In Service
68P02901W23-Q 2-51
assess Chapter 2: Device/function related commands

-- 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
DRI 1 4 0 DISABLED UNLOCKED DRI Not Detected
ASSESS REPORT COMPLETE
Example 3
In the following example, the operator is concerned about the RSLs which are impacting SITE 3.
In this case, two separate reconfigurations affect the FU status for SITE 3:
MMI-RAM 0115 -> assess 0 rsl 3 0
Where: is:
0
rsl device name
3 1st device identifier
0 2nd device identifier
System response
ASSESS REPORT BEGIN

Alarm Device: RSL 3 0 0
LOCK of RSL: 3 0 0
Cause: OMC REQUEST Outcome: Alarm

RSL 3 0 0 DISABLED UNLOCKED NO REASON

Alarm Device: RSL 3 1 0
LOCK of RSL: 3 1 0

RSL 3 1 0 DISABLED UNLOCKED NO REASON
No Primary Alarm for this Reconfiguration

UNLOCK of RSL 3 1

RSL 3 1 0 DISABLED UNLOCKED No Link
2-52 68P02901W23-Q
ASSESS REPORT COMPLETE
Example 4
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
Example 5
The following example shows an assess display for a PSP at the second PCU:
assess pcu_1 psp 0 0
Where: is:
pcu_1 location
psp device name
0 1st device identifier
0 2nd device identifier
System response
COMMAND ACCEPTED: All devices/functions are in service.
68P02901W23-Q 2-53
cage_audit Chapter 2: Device/function related commands
cage_audit
Description
The cage_audit command performs two different functions. The first allows the execution
of safe tests or all audits for all devices within a specific cage. The second permits the
suspension/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 and is followed by a display of the error description.
Devices listed within the CAGE can also generate messages specific to the device.
Security level 2
Command type A (no operator actions)
Prerequisites None
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>
Input parameters
location
2-54 68P02901W23-Q
Technical Description: BSS Command Reference cage_audit
Specifies the audit location:

0 or bsc BSC
1 to 120 BTS
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 to 13 for a BSC
2 to 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
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
Year: 1994 Month: 11 Day: 12 Hour: 0 in: 26 Sec: 27 MSec: 860
68P02901W23-Q 2-55
cage_audit Chapter 2: Device/function related commands
Audit Type: INT LPBK Result: PASS

Device: MSI Device id: 3 0 0
Device: DRI Device id: 0 1 0
Device: GPROC Device id: 1 0 0
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
Example 3
This example executes safe audits for all devices for cage 0 at site 0:
cage_audit 0 safe 0
Where: is:
0 location
safe audit_type
0 cage_number
System response
Device: CAGE Device id: 0 0 0
ERROR: Audit not available, audits turned off for cage.
Example 4
This example executes safe audits for all devices for cage 0 at the PCU (GPRS):
2-56 68P02901W23-Q
Technical Description: BSS Command Reference cage_audit
cage_audit pcu safe 0
Where: is:
pcu location
safe audit_type
0 cage_number
System response
COMMAND ACCEPTED
Device: PSP
Device id: 0 0 0
Year: 1998 Month: 1 Day: 12 Hour: 16 Min: 22 Sec: 26 MSec:495
Device: DPROC Device id: 2 0 0
Device: DPROC Device id: 7 0 0
Example 5
This example suspends cage audits at PCU site 1 (GPRS):
cage_audit pcu_1 off 0
Where: is:
pcu_1 location
off suspend audits
0 cage_number
System response
COMMAND ACCEPTED
References
Related commands
"chg_audit_sched" on page 2-72, "device_audit" on page 2-185, "query_audits" on
page 2-411, "site_audit" on page 2-441.
68P02901W23-Q 2-57
cell_name Chapter 2: 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 may 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 2
Prerequisites A security level of 2 is required to create or modify a cell name.
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.
cell_name
The name to be assigned to the Cell ID. The cell name must be entered inside double quotation marks.
2-58 68P02901W23-Q
Technical Description: BSS Command Reference cell_name
The cell name may be from one to 31 alphanumeric characters. The dash character may be used
as a separator. The underscore character may not be used as part of the name or as a separator.
Double quotation marks may not be used as part of a cell name.
Cell names may 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 assign 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
System response
GSM Cell [ 5 4 3 2 1 61986 (f222h) 34944 (8880h) ] = "london-west"
If there is no cell name, the system response is: “No textual name exists for this cell.
68P02901W23-Q 2-59
cell_name Chapter 2: Device/function related commands
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
2-60 68P02901W23-Q
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 ACS is configured by the operator 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 may
operate at various combinations of speech and channel coding (codec mode) bit-rate for each channel mode.
Security level 3
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 AMR is enabled in the cell.
This allows performance to be epitomized for calls subsequently
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 2-17 and Table 2-18).
68P02901W23-Q 2-61
chg_acs_params Chapter 2: Device/function related commands
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 is the GSM Cell ID of the cell to be changed.
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 2-14:
Table 2-14 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 2-15, and
the Half Rate attribute values are listed in Table 2-16
2-62 68P02901W23-Q
Table 2-15 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 (if valid).
amr_fr_uplink_threshold3 0 to 63 20 Lower Full Rate uplink
amr_fr_uplink_threshold2 0 to 63 14 decision threshold for
amr_fr_uplink_threshold1 0 to 63 9 switching from one mode to
another.
amr_fr_uplink_hysteresis3 0 to 15 1 The sum of the associated
amr_fr_uplink_hysteresis2 0 to 15 1 threshold and hysteresis is
amr_fr_uplink_hysteresis1 0 to 15 1 used as the upper decision
threshold for switching the
codec mode.
amr_fr_downlink_threshold3 0 to 63 30 Lower Full Rate downlink
amr_fr_downlink_threshold2 0 to 63 24 decision threshold for
amr_fr_downlink_threshold1 0 to 63 19 switching from one mode to
another.
amr_fr_downlink_threshold3 0 to 15 1 The sum of the associated
amr_fr_downlink_threshold2 0 to 15 1 threshold and hysteresis is
amr_fr_downlink_threshold1 0 to 15 1 used as the upper decision
codec mode.
amr_fr_uplink_threshold3_hopping 0 to 63 16 Uplink switching thresholds
amr_fr_uplink_threshold2_hopping 0 to 63 11 applied to frequency hopping
amr_fr_uplink_threshold1_hopping 0 to 63 4 channels.
amr_fr_uplink_hysteresis3_hopping 0 to 15 1 Uplink hysteresis applied to
amr_fr_uplink_hysteresis2_hopping 0 to 15 1 frequency hopping channels.
amr_fr_uplink_hysteresis1_hopping 0 to 15 1
amr_fr_downlink_threshold3_hopping 0 to 63 26 Downlink switching
amr_fr_downlink_threshold2_hopping 0 to 63 21 thresholds applied to
amr_fr_downlink_threshold1_hopping 0 to 63 14 frequency hopping channels.
amr_fr_downlink_hysteresis3_hopping 0 to 15 1 Downlink hysteresis applied
amr_fr_downlink_hysteresis2_hopping 0 to 15 1 to frequency hopping
amr_fr_downlink_hysteresis1_hopping 0 to 15 1 channels.
Table 2-16 Half Rate attribute values for chg_acs_params command
68P02901W23-Q 2-63
Attribute Range Default Notes

amr_hr_acs 2, 3, 4, 5, 6 4, 5, 6 Up to four AMR codec
modes which can be used
for any given voice call
in the uplink or downlink
direction.
amr_hr_initial_codec_mode 2, 3, 4, 5, 6 4 Codec mode used at the
beginning of a call. If one
mode is entered for the Half
Rate ACS, then the Half
Rate Initial Codec Mode
defaults to this (if valid).
amr_hr_uplink_threshold3 0 to 63 28 Lower Half Rate uplink
amr_hr_uplink_threshold2 0 to 63 22 decision threshold for
amr_hr_uplink_threshold1 0 to 63 switching from one mode to
another.
amr_hr_uplink_hysteresis3 0 to 15 11 The sum of the associated
amr_hr_uplink_hysteresis2 0 to 15 threshold and hysteresis is
amr_hr_uplink_hysteresis1 0 to 15 used as the upper decision
codec mode.
amr_hr_downlink_threshold3 0 to 63 30 Lower Half Rate downlink
amr_hr_downlink_threshold2 0 to 63 24 decision threshold for
amr_hr_downlink_threshold1 0 to 63 switching from one mode to
another.
amr_hr_downlink_threshold3 0 to 15 11 The sum of the associated
amr_hr_downlink_threshold2 0 to 15 threshold and hysteresis is
amr_hr_downlink_threshold1 0 to 15 used as the upper decision
codec mode.
amr_hr_uplink_threshold3_hopping 0 to 63 28 Uplink switching thresholds
amr_hr_uplink_threshold2_hopping 0 to 63 21 applied to frequency hopping
amr_hr_uplink_threshold1_hopping 0 to 63 channels.
amr_hr_uplink_hysteresis3_hopping 0 to 15 11 Uplink hysteresis applied to
amr_hr_uplink_hysteresis2_hopping 0 to 15 frequency hopping channels.
amr_hr_uplink_hysteresis1_hopping 0 to 15
amr_hr_downlink_threshold3_hopping 0 to 63 30 Downlink switching
amr_hr_downlink_threshold2_hopping 0 to 63 23 thresholds applied to
amr_hr_downlink_threshold1_hopping 0 to 63 frequency hopping channels.
amr_hr_downlink_hysteresis3_hopping 0 to 15 11 Downlink hysteresis applied
amr_hr_downlink_hysteresis2_hopping 0 to 15 to frequency hopping
amr_hr_downlink_hysteresis1_hopping 0 to 15 channels.
2-64 68P02901W23-Q
Full Rate prompts for the chg_acs_params command are listed in Table 2-17, and the
Half Rate prompts are listed in Table 2-18
Table 2-17 Full Rate prompts for the chg_acs_params command
Prompt Required Value Definition Conditions

Enter AMR Full Yes Up to four codec mode values Prompt displays if the AMR
Rate active codec (codec rates) are entered in feature is unrestricted, the BTS
set: order of descending bit-rate type is AMR-capable, and the
(ascending field value 0 to 7; mode specified is 0 or 2.
see Table 2-14).
Enter AMR Full Yes The value must be one of the Prompt displays if the ACS
Rate initial codec rates included in the Active contains more than one codec
mode: Codec Set. mode.
Enter AMR Full Yes Enter up to three uplink Prompt displays if the ACS
Rate uplink threshold values in order of contains more than one codec
adaptation descending C/I estimation. mode.
thresholds:
One uplink value for each
adjacent pair of codec modes
in ACS.
Enter AMR Full Yes Enter up to three uplink Prompt displays if the ACS
Rate uplink hysteresis values. contains more than one codec
adaptation mode.
hysteresis:
in ACS.
Enter AMR Full Yes Enter up to three downlink Prompt displays if the ACS
Rate downlink threshold values in order of contains more than one codec
thresholds:
One downlink value for each
in ACS.
Enter AMR Full Yes Enter up to three downlink Prompt displays if the ACS
Rate downlink hysteresis values. contains more than one codec
adaptation mode.
hysteresis:
in ACS.
Enter AMR Full Yes Enter up to three values. Prompt displays if the ACS
Rate uplink contains more than one codec
adaptation mode.
thresholds for
One value for each adjacent
frequency hopping:
pair of codec modes in ACS.
adaptation mode.
hysteresis for
frequency hopping:
68P02901W23-Q 2-65
Table 2-17 Full Rate prompts for the chg_acs_params command (Continued)
Rate downlink contains more than one codec
adaptation mode.
thresholds for
frequency hopping:
adaptation mode.
hysteresis for
frequency hopping:
Table 2-18 Half Rate prompts for chg_acs_params command

Enter AMR Half Yes Up to four codec mode values Prompt displays if the AMR
Rate active codec (codec rates) are entered in feature is unrestricted, the BTS
set: order of descending bit-rate type is AMR-capable, and the
(ascending field value 0 to 7. mode specified is 0 or 2.
see Table 2-14)
Enter AMR Half Yes The value must be one of the Prompt displays if the ACS
Rate initial codec rates included in the Active contains more than one codec
mode: Codec Set. mode.
Enter AMR Half Yes Enter up to three uplink Prompt displays if the ACS
Rate uplink threshold values in order of contains more than one codec
thresholds:
in ACS.
Enter AMR Half Yes Enter up to three uplink Prompt displays if the ACS
Rate uplink hysteresis values. contains more than one codec
adaptation mode.
hysteresis:
in ACS.
Enter AMR Half Yes Enter up to three downlink Prompt displays if the ACS
Rate downlink threshold values in order of contains more than one codec
thresholds:
in ACS.
Enter AMR Half Yes Enter up to three downlink Prompt displays if the ACS
Rate downlink hysteresis values. contains more than one codec
adaptation mode.
hysteresis:
in ACS.
2-66 68P02901W23-Q
Table 2-18 Half Rate prompts for chg_acs_params command (Continued)

Enter AMR Half Yes Enter up to three values. Prompt displays if the ACS
adaptation mode.
thresholds for
frequency hopping:
adaptation mode.
hysteresis for
frequency hopping:
adaptation mode.
thresholds for
frequency hopping:
adaptation mode.
hysteresis for
frequency hopping:
Examples
Example 1
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 intial 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
68P02901W23-Q 2-67
Enter AMR Half Rate active codec set: 4
COMMAND ACCEPTED
References
Related commands
"disp_acs" on page 2-194.
2-68 68P02901W23-Q
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 they are to be used by the BSS.
Security level 2
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.
Format
Syntax
chg_a5_alg_pr <first_alg> [<second_alg>] [<third_alg>] [<fourth_alg>]
[<fifth_alg>] [<sixth_alg>] [<seventh_alg>] [<eighth_alg>]
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
68P02901W23-Q 2-69
chg_a5_alg_pr Chapter 2: Device/function related commands
Value GSM Algorithm

4 A5/4
5 A5/5
6 A/5/6
7 A5/7
first_alg
first algorithm choice (0 to 7)
second_alg
second algorithm choice (0 to 7)
Only the first and second algorithm choices are used by the system. Values entered
for the remaining parameters are ignored.
third_alg
third algorithm choice (0 to 7)
fourth_alg
fourth algorithm choice (0 to 7)
fifth_alg
fifth algorithm choice (0 to 7)
sixth_alg
sixth algorithm choice (0 to 7)
seventh_alg
seventh algorithm choice (0 to 7)
eighth_alg
eighth algorithm choice (0 to 7)
Examples
Example 1
In this example, the algorithms ordered as follows: A5/1, A5/2:
2-70 68P02901W23-Q
Technical Description: BSS Command Reference chg_a5_alg_pr
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 will be used:
chg_a5_alg_pr 0
Where: is:
0 No encryption
System response
COMMAND ACCEPTED
References
Related commands
"disp_a5_alg_pr" on page 2-192, "chg_element" on page 2-95.
68P02901W23-Q 2-71
chg_audit_sched Chapter 2: Device/function related commands
chg_audit_sched
Description
The chg_audit_sched command schedules audits of selected devices at specified

sites on a device type and audit type basis.
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 would 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 the audits off.

Security level 2
Prerequisites A user at the OMC-R must rlogin to a site before an audit can be
scheduled.
Only one audit may be run at a time. If a log exists from a previous
audit, it is overwritten with the log created by the current audit.
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>
Input parameters
location
2-72 68P02901W23-Q
Technical Description: BSS Command Reference chg_audit_sched

0 or bsc BSC
1 to 120 BTS
device_name
Name that uniquely identifies the device.
The following devices may be audited at InCell sites using this command:
BSP BTP DHP DRI GCLK
GPROC KSW MSI SITE TDM
The following devices may be audited at M-Cell sites using this command:
BTP DRI MSI SITE
The following devices may be audited at a PCU using this command:

DPROC MSI PSP
audit_type
Type of audit Tests Available Locations

safe Safe tests BSC, BTS, and PCU
int_lpbk Internal loopback KSW
self_test RXCDR at a remote transcoding BSC
all All BSC and BTS only
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
The interval hour (00 to 23)
interval_min
The interval minutes (00 to 59)
68P02901W23-Q 2-73
Scheduling types
There are three scheduling types:
Continuous Scheduling The system schedules continuous audits if:
• The start_time and end_time both have a value of 00:00, and
• The interval value is not 00:00.

Range Scheduling The system schedules range audits if the end_time is greater than
start_time.
Once-Per-Day Scheduling The system schedules range audits if:
• The start_time equals the end_time, and
• The interval has a value of 00:00.

The start_time and end_time must not have a value of 00:00.
Device scheduling defaults

Table 2-19 lists the device scheduling defaults.
Table 2-19 Device scheduling defaults
Device Default schedule

KSW safe test audit continuously every hour
KSW internal loopback audit from 2:00 am to 4:00 am every 15 minutes
GCLK safe test audit continuously every hour
GPROC safe test audit
continuously every 10 minutes
DHP safe test audit
TDM safe test audit once a day at 1:00 am
BSP safe test audit
BTP safe test audit
MSI safe test audit continuously every 1 minute
DRI safe test audit continuously every 30 minutes
SITE safe test audit
AXCDR safe test audit
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 below.
2-74 68P02901W23-Q
Technical Description: BSS Command Reference chg_audit_sched
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.
Examples
Example 1
In this example, 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; this is an example of range scheduling:
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
68P02901W23-Q 2-75
Example 2
In this example, the audit schedule is changed so that the PICP MSI 0 is audited for safe tests every
45 minutes from 9am until 5:30pm. This is an example of GPRS range scheduling:
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
References
Related commands
"cage_audit" on page 2-54, "device_audit" on page 2-185, "query_audits" on page
2-411, "site_audit" on page 2-441.
2-76 68P02901W23-Q
Technical Description: BSS Command Reference chg_cell_element
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 2
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.
Format
Syntax
chg_cell_element [<location>] <element> [,<index>] <value> <cell_desc>
chg_cell_element <location> <element> [,<index>] <value> all
Input parameters
location
The location can also be entered as all. This then changes the value of the specified
element for all available cells in the system.
element
The cell parameter to be changed
68P02901W23-Q 2-77
chg_cell_element Chapter 2: Device/function related commands
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
The GSM Cell ID of the affected cell. This can optionally be preceded by cell_number=.

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. This can optionally be preceded by cell_name=.
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 may be entered. If this is used <location> or all must also
be used for the site. See the individual parameter descriptions.
Examples
Example 1
{22064}.
In this example, the alt_qual_proc parameter is changed to 0 for a cell {22064} with
AMR and/or GSM Half Rate feature unrestricted:
2-78 68P02901W23-Q
Technical Description: BSS Command Reference chg_cell_element
chg_cell_element alt_qual_proc 0 cell 0 0 1 0 1 98 75
Where: is:
alt_qual_proc cell element being changed
0 new value for alt_qual_proc
0 0 1 0 1 98 75 cell_desc
System response
{22064}
Enter RSS handover threshold l_rxqual_ul_p: 200

Enter RSS handover threshold l_rxqual_dl_p: 200
Enter RSS handover threshold u_rxqual_ul_p: 100
Enter RSS handover threshold u_rxqual_dl_p: 100
Enter RSS handover threshold l_rxqual_ul_h: 250
Enter RSS handover threshold l_rxqual_dl_h: 250
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_dl_h_data: 250
Enter RSS handover threshold l_rxqual_ul_h_data: 250
Enter RSS handover threshold l_rxqual_dl_p_data: 200
Enter RSS handover threshold l_rxqual_ul_p_data: 200
Enter RSS handover threshold l_rxqual_ul_p_hr: 200
Enter RSS handover threshold l_rxqual_ul_h_hr: 200
Enter RSS handover threshold u_rxqual_ul_p_hr: 100
Enter RSS handover threshold l_rxqual_dl_p_hr: 100
Enter RSS handover threshold l_rxqual_dl_h_hr: 250
Enter RSS handover threshold u_rxqual_dl_p_hr: 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
The following AMR Full Rate HDPC parameters are only prompted for if AMR is unrestricted.
Enter RSS handover threshold l_rxqual_ul_p_amr_fr: 200
Enter RSS handover threshold l_rxqual_ul_h_amr_fr: 200
Enter RSS handover threshold l_rxqual_dl_p_amr_fr: 100
Enter RSS handover threshold l_rxqual_dl_h_amr_fr: 250
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:
68P02901W23-Q 2-79
chg_cell_element Chapter 2: Device/function related commands
Example 2
{22064}.
In this example, the hop_qual_enabled parameter is changed to 1 for a cell {22064}
with GSM Half Rate enabled:
chg_cell_element hop_qual_enabled 0 cell 0 0 1 0 1 98 75
Where: is:
hop_qual_enabled cell element being changed
1 new value for hop_qual_enabled
0 0 1 0 1 98 75 cell_desc
System response
{22064}
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
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:
2-80 68P02901W23-Q
Technical Description: BSS Command Reference chg_cell_id
chg_cell_id
Description
The chg_cell_id command changes the GSM Cell ID of a specified cell.

• The system used (PGSM, EGSM, DCS1800, PCS1900)

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 systemsThis digit only
applies to PCS1900 systems. EGSM, PGSM
and DCS1800 systems still use the 2 digit
MNC, beginning with d, below.
d either:
• the second digit of the PCS1900 MNC
• the first digit of the PGSM, EGSM or

DCS1800 MNC
e either:
• the third digit of the MNC
• the third digit of the PCS1900 MNC
• the second digit of the PGSM, EGSM or

DCS1800 MNC
Only PCS1900 systems use a three digit
MNC.
68P02901W23-Q 2-81
chg_cell_id Chapter 2: Device/function related commands
Where: is:
f the LAC (Local Area Code)
g the CI (Cell Identity)
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 2
Prerequisites None
Format
Syntax
chg_cell_id <old_cell_desc> <new_cell_desc>
Input parameters
old_cell_desc
Original Cell ID of the cell.
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.
2-82 68P02901W23-Q
Technical Description: BSS Command Reference chg_cell_id
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
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
System response
COMMAND ACCEPTED
68P02901W23-Q 2-83
chg_cell_id Chapter 2: Device/function related commands
References
Related commands
"add_cell" on page 2-21, "cell_name" on page 2-58, "copy_cell" on page 2-157, "del_cell"
on page 2-169, "disp_cell" on page 2-206.
2-84 68P02901W23-Q
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
via the configure_csfp command or via 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 may use.
A value of 100 does not mean the link will be 100% utilized during the download, only that
CSFP downloads can proceed at the maximum throughput rate.
Security level 2
Supported by OMC GUI Yes
Prerequisites None
Format
Syntax
chg_csfp <element> <value> <location>
Input parameters
element
Two selections are available:
algorithm Selects the CSFP algorithm method. The location values that may be entered for
this element are 0 (or bsc) to 120.
flow_control Selects the CSFP flow control value. The location values that may be entered for
this element are 1 to 120.
68P02901W23-Q 2-85
chg_csfp Chapter 2: Device/function related commands
value
Either an algorithm or a flow control value may be entered but not both. The value that
may be used is dependent upon the selected element:
algorithm none No CSFP device is to be configured at this site

stby Select only standby BSP/BTP GPROCs
pool Select only pool GPROCs
any Select POOL GPROCs first followed by STBY GPROCs. This is the
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 to 120 BTS
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
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
2-86 68P02901W23-Q
Technical Description: BSS Command Reference chg_csfp
System response
COMMAND ACCEPTED
References
Related command
"disp_csfp" on page 2-226
68P02901W23-Q 2-87
chg_dte Chapter 2: 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 2-20 for the RXCDR and in Table 2-21 for the BSC.
Table 2-20 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 2-21 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 2
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.
2-88 68P02901W23-Q
Technical Description: BSS Command Reference chg_dte
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 range of values is determined by the link location type:
0 to 3 bsc
0 to 7 omcr
0 bsc_cbc or cbc. A link_num is required for cbc and bsc_cbc if the address_length
is 0.
address_length
The number of valid address bytes that are added to the list. The range of values is 0 to14.
address_byte
The value of a particular address byte. The range of values is 0 to 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.
Examples
Example 1
In this example, the DTE address of the 3rd BSC is changed to 12345:
68P02901W23-Q 2-89
chg_dte Chapter 2: Device/function related commands
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
COMMAND ACCEPTED
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 #3: 122876465567
Address #4: 2301
Address #5: 6811570001
2-90 68P02901W23-Q
Technical Description: BSS Command Reference chg_dte

COMMAND ACCEPTED
References
Related command
"disp_dte" on page 2-230.
68P02901W23-Q 2-91
chg_eas_alarm Chapter 2: 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 2
Prerequisites The EAS device must be equipped before a severity level and text
characters can be assigned.
Format
Syntax
chg_eas_alarm <alarm_table_index> <alarm_severity_level>
"<new_alarm_string>"
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 to 33.
alarm_severity_level
Specifies the alarm level for a specific alarm string. Valid values are:
0 investigate
1 critical
2-92 68P02901W23-Q
Technical Description: BSS Command Reference chg_eas_alarm
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
may 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
References
Related information
Table 2-22 lists the EAS default alarm strings.
Table 2-22 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
68P02901W23-Q 2-93
chg_eas_alarm Chapter 2: Device/function related commands
Table 2-22 EAS default alarm strings (Continued)

alarm_table_index Default alarm string
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
27 TDU Over Temperature
28 TDU Door Open
29 TDU Circuit Breaker
30 TDU Battery
31 TDU Customer Defined 1
Related commands
"chg_element" on page 2-95, "disp_element" on page 2-232.
2-94 68P02901W23-Q
Technical Description: BSS Command Reference chg_element
chg_element
Description
The chg_element command modifies database parameters in the CM database.

Security level 2
Command type Dependent on the database parameter being changed.
Prerequisites None
Operator actions Operator actions depend on the database parameter being changed.
Details are given in the "CM database parameters presentation"
on page 5-2.
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
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.
68P02901W23-Q 2-95
chg_element Chapter 2: Device/function related commands
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 may only be used
with statistical database parameter names. Normal and Weighted Distribution statistical database
parameter names require the use of index2. No other parameters require it.
value
New value for the element_name.
location
0 or bsc BSC
1 to 120 BTS
all Specifies all sites.
Restrictions on the use of all locations are:
• Allowed outside of SYSGEN mode only for type A elements.
• Not allowed outside of 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 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, it must be placed inside double quotation marks, and be preceded by cell_name=.
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.
2-96 68P02901W23-Q
• Not allowed outside of 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 may 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 0, 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_desc
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 2
In the next example, the maximum number of retransmissions (max_retran) value is changed
to 3 for site number 0, cell_number=5 4 3 2 1 61986 34944:
chg_element max_retran 3 1 cell_number=5 4 3 2 1 61986 34944
Where: is:
max_retran element_name
3 value
1 location
5 4 3 2 1 61986 34944 cell_number
68P02901W23-Q 2-97
System response
COMMAND ACCEPTED
Example 3
In this example, the database parameter transcoder_location is changed to a value of 1 for site number 2:
chg_element transcoder_location 1 0
Where: is:
transcoder_location element_name
1 value
0 location
System response
COMMAND ACCEPTED
The above example works only at site 0 in SYSGEN ON mode.
Example 4
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
Example 5
In this example, the GCLK at site 0 is phase lock disabled:
chg_element phase_lock_gclk 0 0
Where: is:
phase_lock_gclk element_name
2-98 68P02901W23-Q
Where: is:
0 value
0 location
System response
COMMAND ACCEPTED
Example 6
In this example, the Preventive Cyclic Retransmission (PCR) error correction method is enabled:
chg_element pcr_enable 1 bsc
Where: is:
pcr_enable element_name
1 value
bsc location
System response
If the command is used outside the SYSGEN ON mode, the BSC
must be reset to initiate the change. The following text is displayed:
WARNING: The previous value will be used until the BSC is reset
COMMAND ACCEPTED
If the command is used inside the SYSGEN ON mode, the following text is displayed:
COMMAND ACCEPTED
Example 7
In this example, the maximum number of message units to be retained for the PCR
error correction method is defined as 64:
chg_element pcr_n1 64 bsc
Where: is:
pcr_n1 element_name
64 value
bsc location
System response
COMMAND ACCEPTED
68P02901W23-Q 2-99
Example 8
In this example, the maximum number of message unit octets to be retained for the PCR
error correction method is defined as 1850:
chg_element pcr_n2 1850 0
Where: is:
pcr_n2 element_name
1850 value
0 location
System response
COMMAND ACCEPTED
Example 9
In this example, the local_maintenance parameter is enabled to permit local interaction with the BSS. When
the local_maintenance parameter is disabled, interaction with the system is available only from the OMC.
The system must be in the SYSGEN ON mode to change the local_maintenance parameter.
chg_element local_maintenance 1 0
Where: is:
local_maintenance element_name
1 value
0 location
System response
COMMAND ACCEPTED
Example 10
chg_element bsic 1 1 cell "london-north"
Where: is:
bsic element_name
1 value
1 location
london-north cell_name
2-100 68P02901W23-Q
System response
COMMAND ACCEPTED

Example 11
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 543 721 61986 34944
Where: is:
bsic element_name
1 value
1 location
543 721 61986 34944 cell_desc
System response
COMMAND ACCEPTED

References
Related information
Details of the database parameters that may be changed using this command are given in the
relevant parameter descriptions in Chapter 5 of this manual.
Related command
"disp_element" on page 2-232.
68P02901W23-Q 2-101
chg_hop_params Chapter 2: Device/function related commands
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 of 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 that the
site will reset if the system operator has enabled, disabled or changed an enabled hopping system which is
synthesizer hopping through the BCCH RTF. The operator can abort the command to prevent a site reset.
The operator can change hopping support from no hopping to baseband hopping, or from no hopping
to synthesizer hopping, or vice versa, provided that all FHIs for the cell are disabled.
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.
A warning message is presented if duplicated frequencies are entered. The system ignores the duplicated
frequencies. If this warning message occurs, the command must be re-entered without the duplication.
Hopping verification is run by this command on all cells in the specified site, even if the
cells in the site are not specifically modified.
An EGPRS RTF cannot baseband hop in the same FHIs as non-EGPRS RTFs.
Security level 2
2-102 68P02901W23-Q
Technical Description: BSS Command Reference chg_hop_params

Prerequisites If hopping_systems verification fails the system rejects this
command outside of 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.
• 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 the BCCH carrier timeslots set
to “0xffh" (255).
Synthesizer hopping is not allowed in a cell if a Remotely
Tuneable Combiner is equipped at the 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 to 251.
The master cabinet at the site must be a Horizon II macro in order

for an EGPRS RTF to baseband hop.
This command can be entered only at the BSC. To change multiple hopping parameters
at a BTS site, contact the OMC-R for help.
68P02901W23-Q 2-103
Format
Syntax
chg_hop_params [<location>]
chg_hop_params [<cell_desc>]
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 will be assumed.
location
0 or bsc BSC
1 to 120 BTS
cell_desc
The GSM Cell ID of the affected cell. This can optionally be preceded by cell_number=.
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. This can optionally be preceded by cell_name=.
Table 2-23 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.
2-104 68P02901W23-Q
Table 2-23 Baseband and Synthesizer frequency hopping restrictions
Snythesizer SFH through BCCH

FHI state Baseband
Frequency (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.
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 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 2 3 1 12
68P02901W23-Q 2-105
"cellname1" (RETURN=no change for this cell):

(RETURN=no change for this cell): 2 0
Hopping support: 2
FHI 0 status (enable/disable): 1
HSN for FHI 0: 1
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) ?"
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 0 0 1 0 1 1 21
System response
“cellname3" (RETURN=no change for this cell): 2 0
Hopping support: 2
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) ?
Example 3
In this example, changes to the hopping systems are rejected by the system because FHI 0
must be disabled before the hopping support could change:
chg_hop_params 2
This causes the system to display an error message.
System response
(0x0001) 3 (0x0003) (RETURN=no change for this cell):0
Hopping support:0
HSN for FHI 0:
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) ?
HOPPING VERIFICATION RESULTS
2-106 68P02901W23-Q
============================
Site 2: GSM Cell: 0 0 1 0 1 1 (0x0001) 3 (0x0003)

--------------------------------------------------
ERROR: FHI 0 may not be enabled while hopping_support is disabled.
COMMAND REJECTED
Example 4
In this example, an attempt to modify the hopping parameters outside of Sysgen mode for an EGPRS
RTF to baseband hop when the master cabinet at the site is not a HorizonIImacro, is rejected:
chg_hop_params 2
System response
Hopping systems (FHIs) to be modified in cell 001 01
1 (0001h) 3 (0003h) (RETURN=no change for this cell):1
Hopping support: 2
HSN for FHI 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

============================
Site 2: GSM Cell: 0 0 1 0 1 1 (0001h) 3 (0003h)

--------------------------------------------------
ERROR: Master cabinet must be Horizonmacro2
for EGPRS RTFs to hop in baseband hopping.
COMMAND REJECTED
Example 5
In this example, an attempt to modify the hopping parameters outside of Sysgen mode for an EGPRS
RTF to baseband hop in the same FHIs as non-EGPRS RTFs , is rejected:
chg_hop_params cell 0 0 1 0 1 1 1021
System response
(0001h) 1021 (03FDh) (RETURN=no change for this cell):1 2
Hopping support: 2
FHI 1 status (enable/disable): enable
HSN for FHI 1:
FHI 2status (enable/disable): enable
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.
68P02901W23-Q 2-107

============================
Site 1: GSM Cell: 001 01 1 (0001h) 1021 (03FDh)

--------------------------------------------------
ERROR: EGPRS and non-EGPRS carriers cannot have the same FHI.
COMMAND REJECTED
References
Related information
Table 2-24 lists the prompts for the chg_hop_params command; “x" indicates a value supplied by the system.
Table 2-24 chg_hop_params prompts
Prompt Range Default

Hopping support: 0 to 2 0
where:
0 = No hopping in this cell
1 = Synthesizer hopping
2 = Baseband hopping
See Note below.
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 cell. Current value
(ARFCNs) for FHI x: If the cell is PGSM the range is 1 to 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 to 124) or the higher range (975 to
1023, 0).
If the cell is DCS1800, the range is 512 to 885.
If the cell is PCS1900 the range is 512 to 810.
For GSM850, the ARFCN range is 128 to 251.
HSN for FHI x: 0 to 63 Current value
where:
0 is cyclic, and
1 to 63 is random
2-108 68P02901W23-Q
Hopping support may not be 0 if any FHIs are enabled.

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 2-25 lists the maximum number of frequencies in the mobile allocation given the
frequency range of the cell (which may include 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 2-25 Cell frequencies/mobile allocation
Frequencies of the cell Maximum number of frequencies in the

(ARFCNs used) mobile allocation
1 to 124 64
975 to 1023 49
1 to 124, 975 to 1023 16
0, 1 to 124 17
0, 957 to 1023 17
0, 1 to 124, 975 to 1023 17
Related command
"disp_hopping" on page 2-260.
Table 2-26 lists the restrictions on related commands.
Table 2-26 Restrictions on related commands
68P02901W23-Q 2-109
Current chg_hop_params command

hopping change
support and change
disable FHI enable FHI change MA hopping
FHI status HSN
support
Baseband hopping Command Command Command Command Command
FHI is enabled allowed allowed rejected; allowed. rejected.
cannot change FHI must be
MA of an disabled before
enabled FHI. changing hopping
Disable the support
FHI and equip
the RTF before
changing the
MA
Baseband hopping Command Command Command Command Command
FHI is disabled allowed allowed. allowed allowed allowed
Synthesizer Command Command Command Command Command
hopping FHI is allowed allowed allowed. allowed rejected.
enabled MA can FHI must be
change so long disabled before
as the new MA changing hopping
contains all the support
ARFCNs of
the equipped
RTFs in
the hopping
system.
hopping FHI is allowed allowed allowed allowed allowed
disabled
through BCCH allowed; will allowed allowed; will allowed; will rejected.
hopping FHI is reset the site reset the site reset the site FHI must be
enabled disabled before
changing hopping
support
through BCCH allowed allowed; will allowed allowed allowed
hopping FHI is reset the site
disabled
2-110 68P02901W23-Q
Technical Description: BSS Command Reference chg_ksw_config
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 may consist of up to four portions. Each portion is handled
by a different KSW pair. 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 to 1023 handled by KSW pair 0.
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 may be interconnected to form
TDM 0. KSW 0 1, KSW 1 1, KSW 2 1, and KSW 3 1 may 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 fibre 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
fibre 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.
The command may only be issued for InCell sites. The command does not apply to M-Cell sites.
Security level 2
Prerequisites See the Service Manual BSC/RXCDR (68P02901W38) for
information regarding the hardware layout of the KSW pairs.
68P02901W23-Q 2-111
chg_ksw_config Chapter 2: Device/function related commands
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 may be 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 to 120 BTS
ksw_pair
The KSW pair being configured. The range of values is 0 to 3:
0 KSW pair 0 corresponds to KSW 0 0 and KSW 0 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 to 3.
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).
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 to 3.
2-112 68P02901W23-Q
Technical Description: BSS Command Reference chg_ksw_config
pairs 2 and 3 are not equipped. Valid values are 0 to 3.
pair 3 is not equipped. Valid values are 0 to 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
CAGE 1:
KSW 1 0 and KSW 1 1 (KSW pair 1) are equipped in CAGE 1
CAGE 2:
CAGE 3:
68P02901W23-Q 2-113
chg_ksw_config Chapter 2: Device/function related commands

The commands for configuring the expansion are:
chg_ksw_config 0 0 0 1 2 3
For example, in the command chg_ksw_config 0 2 1 2 0 3 for KSW pair 2 above:
location 0 indicates that this is the BSC.
ksw_pair 2 indicates that this is for KSW pair 2 which is in cage 2.
kswx_connected_to_hwy_0 1 indicates that the KSWXs in slot U21 and U9 in the cage
with KSW pair 2 connect to the cage with KSW pair 0.
kswx_connected_to_hwy_2 0 indicates that the highway number is the same as the
KSW pair number.
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.
References
Related command
"disp_element" on page 2-232.
2-114 68P02901W23-Q
Technical Description: BSS Command Reference chg_level
chg_level
Description
The chg_level command changes the current security level. Security level passwords are case
sensitive and require 4 to 16 characters. Any password longer than 16 characters is truncated at
the 16th character. The password is not displayed when entered.
A security level 2 password is not assigned when the system is initially loaded. A level 2 password
may be assigned to limit access to security level 2 commands.
Security level 1
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 changed from
level 1 to level 2. The password is not displayed when entered:
chg_level
System response
Enter password for security level you wish to access: <cor-
rect level 2 password>
Current security level is 2.
68P02901W23-Q 2-115
chg_level Chapter 2: Device/function related commands
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: <cor-
rect level 2 password>
Example 3
In the following example, the security level is changed from level
1 to level 3. The passwords are not displayed when entered:
chg_level
System response
Enter password for security level you wish
to access: <first level 3 password>
Enter password for security level you wish to access:
<second level 3 password>
References
Related command
"disp_level" on page 2-265.
2-116 68P02901W23-Q
Technical Description: BSS Command Reference chg_password
chg_password
Description
The chg_password command changes the password for a specific security level. Passwords are case
sensitive and may be 1 to 16 characters in length. Passwords that are entered with more than 16 characters
will be truncated at the 16th character. The password is not displayed when entered.
To change a password, an operator must enter the password associated with the security level to be changed.
The new password must be significantly different than the old password. This is determined by first
comparing the lengths of the two passwords. If the new password is four or more characters longer or shorter
than the old password, it is considered significantly different and is accepted immediately.
A second test, if required, examines each character in the two passwords. The new password
must contain four or more characters that are different from the ones in the old password. For
example, if both passwords are four characters in length, no characters may be common to both
passwords for the new password to be considered significantly different.
If the Optional Level 3 Password feature is unrestricted, the chg_password command
may be used to change the level 3 passwords.
Security level 2 or 3
Prerequisites None
Format
Syntax
chg_password <level>
Input parameter
level
The level for which the password is to be changed must be entered. The value for this parameter is 2 or 3.
After the command is entered, prompts to change the password display.
68P02901W23-Q 2-117
chg_password Chapter 2: Device/function related commands
Examples
Example 1
In the following example, the password is changed. The old and new passwords are shown in this example
for information purposes only. The passwords would not actually be displayed when entered.
chg_password 2
System response
Enter password: thirteen
Enter new password: one
Verify new password: one
COMMAND ACCEPTED
Example 2
In the following example, the level 3 passwords are changed. This requires the purchase and implementation
of the Level 3 Password feature. The old and new passwords in this example are for information
purposes only. The passwords would not actually be displayed when entered.
chg_password 3
System response
Enter first password for level 3: thirteen
Enter second password for level 3: sailing*
Enter new level 3 first password: Q65tix
Enter new level 3 second password: lt9wwd
Verify new level 3 first password: Q65tix
Verify new level 3 second password: lt9wwd
COMMAND ACCEPTED
Example 3
In the following example, the password is not changed because the verification password was
entered incorrectly. The old and new passwords are shown in this example for information purposes
only. The passwords would not actually be displayed when entered.
chg_password
System response
Enter password: ninety
Enter new password: forty
Verify new password: fourthly
New password and verification password not equal
2-118 68P02901W23-Q
Technical Description: BSS Command Reference chg_password
If the verification password in the example had been entered correctly, the new password
would have been accepted because there is a difference of four characters between the old
password and the new password. If the new password had been “seventy", there would have
only been a difference of three characters and the command would have failed.
References
Related commands
"chg_level" on page 2-115, "disp_level" on page 2-265.
68P02901W23-Q 2-119
chg_rtf_freq Chapter 2: 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 may cause a carrier to be taken out of service. Calls may be lost if no other carrier is available.
A long warning prompt is presented when this command is invoked. The operator
may abort the command at the warning.
Security level 2
2-120 68P02901W23-Q
Technical Description: BSS Command Reference chg_rtf_freq
Prerequisites In a synthesizer hopping system:
• When hopping is enabled, a new frequency may be added if the

frequency is already defined as hopping in all the RTF hopping
systems. This is true for non-BCCH RTF only.
• It is not allowed for BCCH RTFs if FHIs are enabled.
• The new frequency may be 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.
• 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 ARFCN range for an inner zone RTF is
determined by the frequency type as defined by the secondary
band.
• 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 primary and secondary band frequency types must be

allowed by the cabinet(s) to which the DRI(s) in each zone
are equipped.
68P02901W23-Q 2-121
Dependencies In PCS 1900 systems, the frequency entered may be limited by the
the maximum transmit power (max_tx_bts). 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), and 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.
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 to 224 (PGSM)
0, 1 to 224, 975 to 1023 (EGSM)
512 to 885 (DCS1800)
512 to 810 (PCS1900)
128 to 251 (GSM850)
2-122 68P02901W23-Q
Technical Description: BSS Command Reference chg_rtf_freq
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 to 120 BTS
rtf_id1
First device identifier. The range of values is 0 to 5.
rtf_id2
Second device identifier. The range of values is 0 to 11.
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.

COMMAND ACCEPTED
Example 2
This example changes the frequency channel to 3 for RTF 0 1 at the BSC:
68P02901W23-Q 2-123
chg_rtf_freq 3 bsc 0 1
Where: is:
3 frequency
bsc location
0 rtf_id1
1 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.

COMMAND ACCEPTED
References
Related information
The range of values for GSM Phase 2 is:
PGSM RTF_BCCH 1 to 124
RTF_NON_BCCH 1 to 124
EGSM RTF_BCCH 1 to 124
RTF_NON_BCCH 1 to 124 or
0, 975 to 1023
DCS1800 RTF_BCCH 512 to 885
PCS1900 RTF_BCCH 512 to 810
Related commands
"add_rtf_path" on page 2-45, "copy_path" on page 2-163, "del_rtf_path" on page
2-180, "disp_rtf_path" on page 2-308.
2-124 68P02901W23-Q
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 2
Prerequisites None
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 2-19 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.
severity
68P02901W23-Q 2-125
chg_severity Chapter 2: Device/function related commands
The desired severity for the alarm. The available values are:
investigate
critical
major
minor
warning
Example
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
References
Related command
"disp_severity" on page 2-311.
2-126 68P02901W23-Q
Technical Description: BSS Command Reference chg_smscb_msg
chg_smscb_msg
Description
The chg_smscb_msg command changes a selected CBCH background message and the language in
which it is presented. Background messages are uniquely identified by message number.
The background message in all cells at all sites connected to the BSC may 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 & 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. Note that the \ must not separate a
hexadecimal character otherwise the two parts will be read as two separate ASCII characters.
The message created using this command may be displayed using the disp_cbch_state command.
Security level 2
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 may
be successfully used.
68P02901W23-Q 2-127
chg_smscb_msg Chapter 2: Device/function related commands
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_num-

ber> <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 to 3.
message_id
The ITU standard identifier for the background message. The range of values is 0 to 65535.
gs
Geographical scope. This indicates the area over which the message is unique. The
range of values is 0 to 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 to 1023.
update_number
This is the number of an update to an existing message. The range of values is 0 to 15. This
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, it might be required to use the same
update of a message in a new cell as is being used in existing cells.
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
2-128 68P02901W23-Q
4 - Spanish 11 - Greek
5 - Dutch 12 - Turkish
6 - Swedish 13 - Hungarian
The values of 15 to 31 and 33 to 255 are unspecified for the data_coding_scheme.

Only the languages listed above 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=.
GSM Cell ID format is enabled.
the cell name is entered, it must be placed inside double quotation marks and be preceded by cell_name=.
The value all is a valid input for cell_desc; this value changes the specified message(s) for all cells at the BSS.
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
68P02901W23-Q 2-129
Where: is:
2 geographical_scope
0 message_code
0 update_number
1 data_coding_scheme
cell_number=5 4 3 2 1 cell_desc
61986 34944
System response
Enter the Message:
<This is the first line of the message.
. . . .
This is the last line of the message.>
COMMAND ACCEPTED
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
0 message_code
0 update_number
all cell_desc; indicates changes to all cells
System response
Enter the Message:
<This is the only line of the message.>
COMMAND ACCEPTED
Example 3
chg_smscb_msg 1 1234 1 546 1 1 cell_name="london-north"
Where: is:
1 message_number
1234 message_id
2-130 68P02901W23-Q
Where: is:
546 message_code
1 update_number
cell_name="london-north" cell_desc
System response
Enter the Message:
. . .
COMMAND ACCEPTED
Example 4
This example changes the CBCH background message for PCS1900 cell_desc=543 721 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=543 721 61986 34944
Where: is:
0 message_number
1234 message_id
0 message_code
0 update_number
cell_number=543 721 61986 34944 cell_desc
System response
Enter the Message:
. . .

COMMAND ACCEPTED
68P02901W23-Q 2-131
References
Related information
Table 2-27 lists SMS special characters. Alphabetical characters that cannot be directly entered from the
keyboard may be 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 Köln could be included in a message by entering K\7Cln.
Table 2-27 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
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 Feed * : J Z j z
B Ø Not Used + ; K Ä k ä
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 2-182, "disp_cbch_state" on page 2-203.
2-132 68P02901W23-Q
Technical Description: BSS Command Reference chg_throttle
chg_throttle
Description
The chg_throttle command changes the throttle period for an intermittent alarm.
Security level 2
Prerequisites None
Format
Syntax
chg_throttle <device_name> <alarm_code> <throttle_count>
Input parameters
device_name
alarm_code
Identifies the alarm to be throttled; the range is 0 to 254.
throttle_count
Specifies the new throttle count in minutes. A value of 0 means throttling is disabled.
The range of values is 0 to 1440.
68P02901W23-Q 2-133
chg_throttle Chapter 2: Device/function related commands
Examples
Example 1
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 2-314.
2-134 68P02901W23-Q
Technical Description: BSS Command Reference chg_time
chg_time
Description
The chg_time command sets the real-time system clock. The clock may 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 2
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 to 2100.
month
Value identifying the month. The range of values is 1 to 12.
day
Value identifying the day of the month. The range of values is 1 to 31.
<+/->
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 to 23. This value can also be used to specify
the number of hours to be added or subtracted to the current system time.
68P02901W23-Q 2-135
chg_time Chapter 2: Device/function related commands
minute
Value identifying the minute. The range of values is 0 to 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 to 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
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
2-136 68P02901W23-Q
Technical Description: BSS Command Reference chg_time
References
Related commands
"disp_time" on page 2-316, "time_stamp" on page 2-475.
68P02901W23-Q 2-137
chg_ts_usage Chapter 2: Device/function related commands
chg_ts_usage
Description
The chg_ts_usage command does the following:

• Reserves timeslots.
• Nails timeslots.
• Frees reserved timeslots.
• Frees nailed timeslots.
The following operations are supported by the chg_ts_usage command:

RESERVE This operation reserves timeslots. A timeslot can not be used for any connections
when it is reserved.
FREE This operation frees timeslots that have been reserved or nailed using the 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 is 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 to 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.
2-138 68P02901W23-Q
Technical Description: BSS Command Reference chg_ts_usage
As of software release GSR5, the add_link and delete_link commands are

removed. The functionality of these commands to nail and free timeslots is
provided by the chg_ts_usage command.
Security level 2
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.
Format
Syntax
The following format is used to perform the FREE or RESERVE operations:
chg_ts_usage <operation> <site> <mms1_id1> <mms1_id2> <start_ts> <num_ts>

The following format is used to perform the NAIL operation:
chg_ts_usage <operation> <site> <mms1_id1> <mms1_id2> <mms1_ts>

<mms2_id1> <mms2_id2> <mms2_ts> <num_ts>
The following format is used to perform the NAIL_PATH or FREE_PATH operations:
chg_ts_usage <operation> <path_id1> <path_id2> <site_1>

<mms1_id1> <mms1_id2> <site_1_ts> <site_2> <mms2_id1>
<mms2_id2> <site_2_ts> <num_ts>
Input parameters
The parameters used with this command are dependent upon the specified operation. Refer
to the parameter descriptions for function and valid values.
68P02901W23-Q 2-139
operation
The type of action to be performed. This field may be entered as upper or lower case characters.
reserve Reserve timeslots.
free Free timeslots that have been reserved or nailed using the 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.
site
Specifies the location of the MMS at one end of the T1/E1 Mbit/s link for FREE,
RESERVE, and NAIL operations only. Values are:
0 or bsc BSC
1 to 120 BTS
mms1_id1
First identity of the MMS at one end of the T1/E1 link. Values are:
0 to 55 BSC
0 to 71 RXCDR
0 to 9 BTS
mms1_id2
Second identity of the MMS at one end of the T1/E1 link. Values are 0 or 1.
mms1_ts
The timeslot number to be nailed at MMS1 using the NAIL operation only. Values are:
1 to 24 Timeslot values for T1
1 to 31 Timeslot values for E1
mms2_id1
First identity of the MMS at the other end of the T1/E1 link. Values are:
0 to 55 BSC
0 to 71 RXCDR
0 to 9 BTS
mms1_id2
Second identity of the MMS at the other end of the T1/E1 link. Values are 0 or 1.
2-140 68P02901W23-Q
mms2_ts
The timeslot number to be nailed at MMS2 using the NAIL operation only. Values are:
1 to 24 Timeslot values for T1
1 to 31 Timeslot values for E1
start_ts
First of the contiguous timeslots to be reserved or freed using the RESERVE or
FREE operations only. Values are:
1 to 24 For 1.544 Mbit/s T1 Links
1 to 31 For 2.048 Mbit/s E1 Links, including a 32/16 timeslot HDSL link
site_1_ts
Start timeslot number for MMS1 used with the NAIL_PATH or FREE_PATH operations only. Values are:
1 to 31 For 2.048 Mbit/s E1 Links
site_2_ts
Start timeslot number for MMS2 used with the NAIL_PATH or FREE_PATH operations only. Values are:
site_1
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
site_2
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
path_id1
The PATH to be nailed or freed using the NAIL_PATH or FREE_PATH operations only. path_id1
represents the terminating site of the path. Values are:
0 to 100 BSC or BTS
path_id2
The PATH to be nailed or freed using the NAIL_PATH or FREE_PATH operations only. path_id2 represents
the unique path among paths that are sharing the same terminating site. Values are:
0 to 9 Unique path number at shared Remote BTS or BSC
68P02901W23-Q 2-141
num_ts
The number of contiguous timeslots to be nailed using the NAIL or NAIL_PATH operations
or freed using the FREE_PATH operation. Values are:
end_ts
The last 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
Examples
Example 1
In this example, the contiguous timeslots between 16 and 31 at BTS 26 for MMS 1 0 are reserved:
chg_ts_usage
Enter action: RESERVE

Enter Site Identifier: 26
Enter MMS Identifiers: 1 0
Enter Starting Timeslot: 16
Enter Number of Timeslots Requested: 16
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
Enter Action: NAIL

Enter Site Identifier: 26
Enter MMS 1 Identifiers: 1 0
Enter Starting Timeslot for MMS 1: 5
Example 3
In this example, the PATH identifier is 2 0 and timeslot 5 of site 0 is nailed to timeslot 7 of site 2:
chg_ts_usage
2-142 68P02901W23-Q
Enter action: NAIL_PATH

Enter Path Identifiers: 1
Enter Start Site: 1
Enter End Site: 3
References
Related command
"disp_mms_ts_usage" on page 2-270.
68P02901W23-Q 2-143
chg_x25config Chapter 2: Device/function related commands
chg_x25config
Description
The chg_x25config command changes the X.25 link parameters.

Security level 2
Prerequisites None
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
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.
2-144 68P02901W23-Q
Technical Description: BSS Command Reference chg_x25config
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 to 7
Examples
Example 1
The following example changes the X.25 settings for all BSS OMLs:
MMI-RAM 0115 -> 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:
MMI-RAM 0115 -> chg_x25 cbl packet_size 256
Where: is:
cbl link type
packet_size x25_parameter
256 value
System response
COMMAND ACCEPTED
68P02901W23-Q 2-145
chg_x25config Chapter 2: Device/function related commands
References
Related command
"disp_x25config" on page 2-327.
2-146 68P02901W23-Q
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 that the calibration data for the specified
transceiver will be cleared displays.
Security level 2
Command type B (operator action required)
Prerequisites This command is not available while in SYSGEN ON mode.
This command may not be entered at a BT
S.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 to 5.
dev_id
The second device identifier. The range is 0 to 11.
dev_id
The third device identifier. This value defaults to 0 if no value is entered.
68P02901W23-Q 2-147
clear_cal_data Chapter 2: Device/function related commands
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
COMMAND ACCEPTED
References
Related commands
"disp_cal_data" on page 2-201, "store_cal_data" on page 2-464.
2-148 68P02901W23-Q
Technical Description: BSS Command Reference clear_database
clear_database
Description
The clear_database command deletes the contents of the CM database.
This command should be used only by personnel who are fully

aware of the consequences.
The system is placed in the initial SYSGEN mode when this command is entered.
Refer to "SYSGEN mode" on page 1-26.
Security level 2
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.
Format
Syntax
clear_database
Input parameters
There are no input parameters associated with this command.
68P02901W23-Q 2-149
clear_database Chapter 2: Device/function related commands
Examples
Example 1
In this example, the CM database is cleared:
clear_database
System response
COMMAND ACCEPTED
Example 2
In this example, an attempt is made to clear the CM database outside of SYSGEN ON mode:
clear_database
System response
COMMAND REJECTED: Command not allowed outside of SYSGEN: 0
2-150 68P02901W23-Q
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 80h 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 a MMS ID displays.
The LTA values may need to be cleared under the following circumstances:
• The GCLK is replaced.
• The GCLK is recalibrated.
• The uplink site does not provide a stable clock source.
Security level 2
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 to 120 BTS
68P02901W23-Q 2-151
clear_gclk_avgs Chapter 2: Device/function related commands
Examples
Example 1
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
Example 2
In this example, the LTA values for GCLK at InCell SITE 1 are cleared:
clear_gclk_avgs 1
Where: is:
1 location
System response
Enter the mms_id: 0 0
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 is defined by the lta_alarm_range parameter.
Related commands
"disp_gclk_avgs" on page 2-249, "disp_gclk_cal" on page 2-251.
2-152 68P02901W23-Q
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 2
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.
site. Refer to the OMC-R for help.NOTE
Format
Syntax
configure_csfp
Input parameters
Example
This example shows the input required to configure the CSFP devices to sites in the BSS network.
configure_csfp
68P02901W23-Q 2-153
configure_csfp Chapter 2: 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 will be 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.
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 2-85, "disp_csfp" on page 2-226, "unconfigure_csfp" on page 2-492.
2-154 68P02901W23-Q
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 1 (to view);

2 (to change)
Command type A (no operator action required)
Prerequisites The GPRS must be unrestricted in order 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:
68P02901W23-Q 2-155
connection_code Chapter 2: Device/function related commands
connection_code "123456"
Where: is:
123456 the operator-defined code
System response
COMMAND ACCEPTED
Example 2
The following example turns the Call Connectivity Trace feature off:
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
If there is no connection code, the system response is: “No Connection code exists".
2-156 68P02901W23-Q
Technical Description: BSS Command Reference copy_cell
copy_cell
Description
The copy_cell command creates a new cell by copying the information in an existing cell.
This command can not copy a cell source or neighbour 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 already 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 2
Prerequisites None
Operator actions Respond to the warning prompt presented when this command is
entered.
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-Q 2-157
copy_cell Chapter 2: Device/function related commands
Input parameters
source_cell_id
GSM Cell ID of the existing cell being copied.
• The system used (PGSM, EGSM, DCS1800, PCS1900 or GSM850).
The cell name created using the cell_name command may be entered in place of the source_cell_id.
dest_gsm_cell_id
GSM Cell ID of the new cell to be created. A cell name may not be entered for the destination Cell ID.
dest_location
Specifies the location of the new cell. Values are:
0 or bsc BSC
1 to 120 BTS
dest_bsic
Specifies the BSIC of the new cell. The range of values for the bsic is 0 to 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 dtx_required max_ts_ms
attach_detach dyn_step_adj missing_rpt
ba_alloc_proc dyn_step_adj_fmpr ms_distance_allowed
bs_ag_blks_res egprs_init_dl_cs ms_p_con_ack
bs_pa_mfrms egprs_init_ul_cs ms_p_con_interval
bep_period emergency_class_switch ms_power_control_allowed
bep_period2 en_incom_ho ms_txpwr_max_cch
2-158 68P02901W23-Q
bsic extended_paging_active ms_txpwr_max_def

bts_p_con_ack frequency_type mspwr_alg
bts_p_con_interval full_pwr_rfloss ncc_of_plmn_allowed
bts_power_control_allowed handover_power_level {22064}new_calls_hr
ccch_conf handover_recognized_period number_of_preferred_cells
cell_bar_access_class ho_margin_def number_sdcchs_preferred
cell_bar_access_switch {22064}hr_fr_hop_count penalty_time
cell_bar_qualify {22064}hr_intracell_ho_allowed pow_inc_step_size_dl
cell_reselect_hysteresis {22064}hr_res_ts pow_red_step_size_dl
cell_reselect_offset {22064}inner_hr_usage_thres pow_inc_step_size_ul
cell_reselect_param_ind intave pow_red_step_size_ul
decision_1_dl_rxlev_av_h inter_cell_handover_allowed pwr_handover_allowed
decision_1_dl_rxlev_av_ih interfer_ho_allowed pwrc
decision_1_dl_rxlev_av_p intr_cell_handover_allowed radio_link_timeout
decision_1_dl_rxqual_av_h l_rxlev_dl_h rapid_pwr_down
decision_1_dl_rxqual_av_p l_rxlev_dl_p {22064}reconfig_fr_to_hr
decision_1_n1 l_rxlev_ul_h reestablish_allowed
decision_1_n2 l_rxlev_ul_p report_resource_tch_f_high_
water_mark
decision_1_n3 l_rxqual_dl_h report_resource_tch_f_low_
water_mark
decision_1_n4 {22064}l_rxqual_dl_h_hop- rpd_offset
ping_hr
decision_1_n5 {22064}l_rxqual_dl_h_hr rpd_period
decision_1_n6 l_rxqual_dl_p rpd_trigger
decision_1_n7 {22064}l_rxqual_dl_p_hop- rxlev_access_min
ping_hr
decision_1_n8 {22064}l_rxqual_dl_p_hr rxlev_min_def
decision_1_ncell_rxlev_ l_rxqual_ul_h sdcch_ho
av_h_calc
decision_1_p_bgt_rxlev_av_h {22064}l_rxqual_ul_h_hop- sdcch_timer_ho
ping_hr
decision_1_p1 {22064}l_rxqual_ul_h_hr temporary_offset
decision_1_p2 l_rxqual_ul_p timing_advance_period
decision_1_p3 {22064}l_rxqual_ul_p_hop- tlli_blk_coding
ping_hr
decision_1_p4 {22064}l_rxqual_ul_p_hr tx_integer
decision_1_p5 l_rxqual_ul_p_amr_fr u_rxlev_dl_ih
decision_1_p6 l_rxqual_dl_p_amr_fr u_rxlev_dl_p
68P02901W23-Q 2-159
decision_1_p7 l_rxqual_ul_h_amr_fr ul_rxlev_ho_allowed

decision_1_p8 l_rxqual_dl_h_amr_fr u_rxlev_ul_ih
decision_1_tim_adv_av_alg l_rxqual_dl_h_hopping_amr_fr u_rxlev_ul_p
decision_1_ul_rxlev_av_h l_rxqual_ul_h_hopping_amr_fr u_rxqual_dl_p
decision_1_ul_rxlev_av_ih l_rxqual_dl_p_hopping_amr_fr ul_rxqual_ho_allowed
decision_1_ul_rxlev_av_p l_rxqual_ul_p_hopping_amr_fr u_rxqual_ul_p
decision_1_ul_rxqual_av_h link_about_to_fail {22064}u_rxqual_dl_p_hr
decision_1_ul_rxqual_av_p link_fail {22064}u_rxqual_ul_p_hr
dl_rxlev_ho_allowed max_retran wait_indication_parameters
dl_rxqual_ho_allowed max_tx_bts
If the Inter-RAT handover option is unrestricted, and UMTS UTRAN cells are copied
with copy_cell, the following parameters will be defaulted in the new cell: fdd_qmin,
fdd_qoffset, qsearch_c_initial, qsearch_i, and inter_rat_enabled.
Exceptions
The following is a list of parameters that are not copied (default values are used)
when the copy_cell command is executed:
bsic hopping_support
bcch_frequency inner_zone_alg
cbch_enabled inter_rat_enable
cell_name ms_max_range
coincident_index multiband_reporting
coincident_mb res_ts_less_one_carrier
dynet_tchs_reserved source_cells
equipment_share_table_pointer sw_ts_less_one_carrier
ext_range_cell switch_gprs_pdchs
freq_share_table_pointer thresholds
gsm_cell_id tx_power_cap
{22064}gsm_half_rate_enabled trx_pwr_carriers.num_carriers
Note that neighbor definitions also are not copied.
2-160 68P02901W23-Q
If the GPRS feature is unrestricted, the GPRS elements at a cell are copied by the
copy_cell command, 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 new 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
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
Example 3
In this example, information from a PCS1900 cell with cell_number=543 721 61986 34944 is copied to create
a new cell with cell_number=543 721 61986 34945 at site 0, with the cell name of “paris":
68P02901W23-Q 2-161
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
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 2-21, "del_cell" on page 2-169, "disp_cell" on page 2-206.
2-162 68P02901W23-Q
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; and 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 2
Prerequisites None
Format
Syntax
copy_path
Input parameters
There are no input parameters since this command is interactive. Table 2-28 lists the
prompts and values that must be entered.
68P02901W23-Q 2-163
copy_path Chapter 2: Device/function related commands
Table 2-28 copy_path command prompts
Prompt Range Default

Enter the terminating SITE id to be copied: 1 to 120 none
Enter the Unique PATH id to be copied: 0 to 9 none
6 to 9
(see Note, below)
Note: If the terminating BTS uses dynamic allocation, the range is 6 to 9; if the terminating BTS does
not use dynamic allocation, the range is 0 to 9.
Enter the new terminating site id: 1 to 120 none
Enter the unique PATH id: 0 to 9 none
Enter the downstream MSI identifier: 0 to 9 none
Enter the downstream MMS identifier: 0 or 1 none
Enter the upstream MSI identifier: 0 to 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
References
Related information
The figure below illustrates that “downstream" always refers to the direction from the BSC to the BTS,
while “upstream" always describes the direction from the BTS to the BSC.
2-164 68P02901W23-Q
Technical Description: BSS Command Reference copy_path
Site 5 Site 0 Site 6

UPSTREAM UPSTREAM
BTS BSC BTS

DOWNSTREAM DOWNSTREAM
MMS 30 MMS 31 MMS 27
Related commands
"add_rtf_path" on page 2-45, "chg_rtf_freq" on page 2-120, "del_rtf_path" on page
2-180, "disp_rtf_path" on page 2-308.
68P02901W23-Q 2-165
del_act_alarm Chapter 2: Device/function related commands
del_act_alarm
Description
The del_act_alarm command deletes an active operator clearable alarm.
The disp_act_alarm command displays the alarms that can be deleted by the
operator. See "disp_act_alarm" on page 2-196
Security level 2
Prerequisites None.
Format
Syntax
del_act_alarm <location> <device_name>
<dev_id1> <dev_id2> <dev_id3> <alarm_code>
disp_act_alarm <location>
Input parameters
location
Specifies the alarm location:
0 or bsc BSC
1 to 120 BTS
device_name
Device name that uniquely identifies the device.
dev_id1
2-166 68P02901W23-Q
Technical Description: BSS Command Reference del_act_alarm

dev_id2
dev_id3
Third device identifier. The range of values is 0 to 99.
alarm_code
Alarm to be deleted. The range of values is 0 to 254.
Example 1
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
Example 2
This example deletes an active alarm for PSP 0, alarm code 1, at PCU site 1:
del_act_alarm PCU_1 PSP 0 0 0 1
Where: is:
PCU-1 location
PSP device_name
0 dev_id1
0 dev_id2
0 dev_id3
1 alarm_code
68P02901W23-Q 2-167
del_act_alarm Chapter 2: Device/function related commands
System response
COMMAND ACCEPTED
References
Related commands
"disp_act_alarm" on page 2-196.
2-168 68P02901W23-Q
Technical Description: BSS Command Reference del_cell
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.
Security level 2
Prerequisites A cell may not be removed if it is currently in a DRI descriptor. To
remove a cell that is included in a DRI descriptor, the DRI must
be unequipped first.
Format
Syntax
del_cell <cell_id>
Input parameter
cell_id
GSM Cell ID of the cell to be deleted.
• The system being used (PGSM, EGSM, DCS1800, PCS1900)
68P02901W23-Q 2-169
del_cell Chapter 2: Device/function related commands
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:
System response
COMMAND ACCEPTED
2-170 68P02901W23-Q
Technical Description: BSS Command Reference del_cell
References
Related commands
"add_cell" on page 2-21, "copy_cell" on page 2-157, "disp_cell" on page 2-206,
"disp_gsm_cells" on page 2-254.
68P02901W23-Q 2-171
del_conn Chapter 2: Device/function related commands
del_conn
Description
The del_conn command updates the BSS database to delete a particular connection between
a MMS at the BSC and a MMS at the RXCDR.
Connectivity may not be removed for an MMS pair if the BSC is operating in static mode and CICs are
statically assigned to that MMS pair. This only applies to remote transcoding BSC and RXCDR sites.
Security level 2
Prerequisites All CICs and XBLs must be unequipped before deleting MMS
connectivity information.
This command may 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 being entered. The range of values is 0 to 55 when this command is executed from
a BSC. The range is 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.
Examples
Example 1
This example shows connectivity information deleted for MMS 4 0 at the BSC:
2-172 68P02901W23-Q
Technical Description: BSS Command Reference del_conn
del_conn 4 0
Where: is:
4 local_mms_id_1
0 local_mms_id_2
System response
COMMAND ACCEPTED
Example 2
This example shows connectivity information deleted for MMS 3 0 at the RXCDR:
del_conn 3 0
Where: is:
3 local_mms_id_1
0 local_mms_id_2
System response
COMMAND ACCEPTED
References
Related commands
"add_conn" on page 2-33, "disp_conn" on page 2-224, "mod_conn" on page 2-392.
68P02901W23-Q 2-173
del_neighbor Chapter 2: Device/function related commands
del_neighbor
Description
The del_neighbor command deletes neighbour cells from a cell neighbour list. If two Cell IDs are
entered, the second Cell ID is removed from the first cell neighbour list.
If all is entered in place of the second cell ID, then every neighbour in the specified cell’s neighbour list is
deleted. If all is entered in place of the first Cell ID, then the cell is deleted from all associated neighbour lists.
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 2
Prerequisites To be on a Neighbour Cell List, a cell must be the destination of
handovers from the Neighbour List owner.
For handovers to UMTS UTRAN cells, the Inter-RAT handover
option must be unrestricted.
2-174 68P02901W23-Q
Technical Description: BSS Command Reference del_neighbor
Format
Syntax
del_neighbor <source_cell_id> <neighbor_cell_id>
del_neighbor <source_cell_id> all
del_neighbor all <neighbor_cell_id>
Input parameters
source_cell_id
GSM or UTRAN Cell ID of the Neighbour List owner.
GSM Cell ID of the Neighbour List owner.
• Whether the seven parameter GSM cell id format or the four parameter GSM
Cell ID format has been enabled.
neighbor_cell_id
GSM or UTRAN Cell ID of the cell specified to be removed from the Neighbour List.
GSM Cell ID of the cell specified to be removed from the Neighbour List.
• Whether the seven parameter GSM cell id format or the four parameter GSM
Cell ID format has been enabled.
The string test <num> may be entered for this field where <num> is a value from 1 to 64. This permits
test neighbours to be removed from the BA_SACCH and/or BA_BCCH lists.
<source_cell_id> all
This syntax removes all neighbour cells from the source cell neighbour list.
all <neighbor_cell_id>
This syntax removes the neighbour cell from all source cell neighbour lists.
68P02901W23-Q 2-175
del_neighbor Chapter 2: Device/function related commands
Examples
Example 1
In this example, cell_id 5 4 3 2 1 61986 34945 is removed from the neighbour 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 neighbour cells are removed from the neighbour 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
System response
COMMAND ACCEPTED
Example 3
In this example, cell_id 5 4 3 2 1 61986 34944 is removed from all neighbour 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 neighbour lists:
2-176 68P02901W23-Q
Technical Description: BSS Command Reference del_neighbor
del_neighbor all 987 654 12345 34567
Where: is:
all source_cell_id
987 654 12345 34567 neighbor_cell_id
System response
COMMAND ACCEPTED
References
Related commands
"add_cell" on page 2-21, "add_neighbor" on page 2-35, "copy_cell" on page 2-157, "del_cell" on page 2-169,
"disp_cell" on page 2-206, "disp_gsm_cells" on page 2-254, "disp_neighbor" on page 2-282.
68P02901W23-Q 2-177
del_nsvc Chapter 2: Device/function related commands
del_nsvc
Description
The del_nsvc command enables the user 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.
Security level 2
Format
Syntax
del_nsvc <pcu_id> <ns_vci_1> [<ns_vci_2> ... <ns_vci_8>]
Input parameter(s):
pcu_id
Specifies the specific PCU, as pcu, pcu_0, pcu_1 or pcu_2.
ns_vci_1
Specifies the unique identifier of the first NSVCI mapping and identifier of the object; range = 0 to 65535.
ns_vci_2 ... ns_vci_8
Specifies the unique identifiers of subsequent NSVCI mapping and the objects (up to 8); range = 0 to 65535.
Example
The following example deletes NSVCI 580 at the first equipped PCU.
2-178 68P02901W23-Q
Technical Description: BSS Command Reference del_nsvc
del_nsvc pcu_0 580
Where: is:
pcu_0 PCU identifier (first equipped)
580 NSVC identifier
System response:
COMMAND ACCEPTED
References
Related commands
"add_nsvc" on page 2-43, "mod_nsvc" on page 2-395.
68P02901W23-Q 2-179
del_rtf_path Chapter 2: 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. PATHs
for such sites are defined by the equip DYNET command. RTFs automatically use the PATH(s) defined
for these types of sites. RTFs do not use PATH(s) equipped by the operator for these types of sites.
Security level 2
Prerequisites None
Format
Syntax
del_rtf_path <location> <1st_RTF_identifier> <2nd_RTF_identi-
fier> <unique_PATH_identifier>
Input parameters
location
The number of the BTS where the RTF is located. The range of values is 1 to 120.
1st_RTF_identifier
The 1st RTF identifier from which the path will be removed. The range of values is 0 to 5.
2nd_RTF_identifier
The 2nd RTF identifier from which the path will be removed. The range of values is 0 to 11.
2-180 68P02901W23-Q
Technical Description: BSS Command Reference del_rtf_path
The unique PATH to be removed. The range of values is 0 to 9.
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 2-45, "chg_rtf_freq" on page 2-120, "disp_rtf_path" on page
2-308, "copy_path" on page 2-163.
68P02901W23-Q 2-181
del_smscb_msg Chapter 2: Device/function related commands
del_smscb_msg
Description
The del_smscb_msg command deletes the CBCH background message.

This command may be 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 2
Prerequisites None
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 cell(s).
cell_desc
2-182 68P02901W23-Q
Technical Description: BSS Command Reference del_smscb_msg
This parameter is the GSM Cell ID of the cell at which messages are to be deleted,
preceded by cell_number=.
The value all is also a valid input for the cell_desc, to delete the specified message(s) 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
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)
68P02901W23-Q 2-183
del_smscb_msg Chapter 2: Device/function related commands
System response
COMMAND ACCEPTED
Example 3
del_smscb_msg 3 cell_name="london-south"
Where: is:
3 msg_num
cell_name=“london-south" cell_desc
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
References
Related commands
"chg_smscb_msg" on page 2-127, "disp_cbch_state" on page 2-203.
2-184 68P02901W23-Q
Technical Description: BSS Command Reference device_audit
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.
When this command is used to execute an audit at the BSC for a RXCDR that is in the
BUSY-UNLOCKED state, the BSC performs an audit.
Security level 2
Prerequisites This command is not allowed while in SYSGEN ON mode.
A user at the OMC-R must rlogin to a site before an audit can be
performed.
Format
Syntax
device_audit <location> <control> <device_name>
<device_id1> <device_id2> <device_id3>
device_audit <location> <audit type> <device_name>

<device_id1> <device_id2> <device_id3>
Input parameters
location
0 or bsc BSC
1 to 120 BTS
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.
68P02901W23-Q 2-185
device_audit Chapter 2: Device/function related commands
audit_type
Type of audit:
safe Initiates safe tests.
self Initiates self tests.
all Initiates all audits.
Multiple devices can be audited if all is entered as the control parameter value. The format
for each of the additional devices is the same as it is for the first device.
device_name
Not all devices can be audited at all site types. It is only possible to audit the device that are actually equipped
at the site. Given these conditions, the following devices may be audited with this command:
BSP GPROC SBUS
BTP KSW TDM
DHP MSI AXCDR
DRI RXCDR
The following devices may be audited at M-Cell sites using this command:
BTP DRI MSI
The following devices may be audited at PCU using this command:

MSI DPROC PSP
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.
2-186 68P02901W23-Q
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
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 are 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:
68P02901W23-Q 2-187
device_audit Chapter 2: Device/function related commands
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
Example 4
The following example executes, suspends or resumes audits on the GPRS PICP MSI device:
device_audit PCU_0 safe MSI 2
Where: is:
PCU_0 location
safe control
MSI device_name
2 device_id1
Example 5
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
Year:1999 Month:1 Day:22 Hour:17 Min:56 Sec:12 MSec:470
2-188 68P02901W23-Q
References
Related commands
"cage_audit" on page 2-54, "chg_audit_sched" on page 2-72, "query_audits" on page
68P02901W23-Q 2-189
diagnose_device Chapter 2: Device/function related commands
diagnose_device
Description
The diagnose_device command performs the specified diagnostic on the specified device.
Security level 2
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 to 120 BTS
device
Specifies the ASCII device name. The only available device is the DRI.
id0
Specifies the first identifier. The range is 0 to 255.
id1
Specifies the second identifier. The range is 0 to 255.
id2
Specifies the third identifier. The range is 0 to 255.
2-190 68P02901W23-Q
Technical Description: BSS Command Reference diagnose_device
Prompted parameter
After specifying the input parameters listed above, 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
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
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
RCU Output Loopback: NOT RUN
RCU Output Loopback RXLEV (Branch 1): N/A
RCU Output Loopback RXLEV (Branch 2): N/A
END OF REPORT
68P02901W23-Q 2-191
disp_a5_alg_pr Chapter 2: 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 Any
Prerequisites None
Format
Syntax
disp_a5_alg_pr
Input parameters
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
2-192 68P02901W23-Q
Technical Description: BSS Command Reference disp_a5_alg_pr
System response
Ciphering Algorithms are prioritized as follows: 0
References
Related commands
"chg_a5_alg_pr" on page 2-69, "page" on page 2-409.
68P02901W23-Q 2-193
disp_acs Chapter 2: Device/function related commands
disp_acs
Description
The disp_acs command displays the Active Codec Set and associated parameters.
Security level 1
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 name of the cell created using the cell_name command may be entered in place of the Cell ID.
The Cell ID or the “cell_name" must be entered directly without any preceding qualifier.
2-194 68P02901W23-Q
Technical Description: BSS Command Reference disp_acs
Example
Example 1
This example displays the codec modes for a given cell:
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 4
AMR Full Rate intial codec mode: 1
AMR Full Rate uplink adaptation thresholds: 40 30 20
AMR Full Rate uplink adaptation hysteresis: 1 1 2
AMR Full Rate downlink adaptation thresholds: 45 35 25
AMR Full Rate downlink adaptation hysteresis: 1 1 2
AMR Full Rate uplink adaptation thresholds for frequency hopping: 16 11 4
AMR Full Rate uplink adaptation hysteresis for frequency hopping: 1 1 1
AMR Full Rate downlink adaptation thresholds for frequency hopping: 27 22 14
AMR Full Rate downlink adaptation hysteresis for frequency hopping: 1 1 1
AMR Half Rate active codec set: 3 4 5
AMR Half Rate intial codec mode: 3
AMR Half Rate uplink adaptation thresholds: 30 20
AMR Half Rate uplink adaptation hysteresis: 1 1
AMR Half Rate downlink adaptation thresholds: 31 21
AMR Half Rate downlink adaptation hysteresis: 1 1
AMR Half Rate uplink adaptation thresholds for frequency hopping: 28 21
AMR Half Rate uplink adaptation hysteresis for frequency hopping: 1 1
AMR 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 2-61
68P02901W23-Q 2-195
disp_act_alarm Chapter 2: 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. This does not affect the number of alarms displayed after entering
disp_act_alarm <location>. The output of this command displays up to 200 alarms for each device in the site.
Security level 1
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 to 120 BTS
device_name
dev_id1
2-196 68P02901W23-Q
Technical Description: BSS Command Reference disp_act_alarm
dev_id2
dev_id3
Examples
Example 1
This example displays all active Operator Initiated Clear, and Fault Management alarms for DRI 1 0 0 at
the BSC. The command does not show all active alarms, since any uncleared intermittent alarm would be
considered an active alarm, but it would not appear on any list using the disp_act_alarm command:
disp_act_alarm bsc dri 1 0 0
Where: is:
bsc location
dri device_name
1 dev_id1
0 dev_id2
0 dev_id3
System response
COMMAND ACCEPTED
Site: BSC
Alarm Clear
Device Code Type Tag(hex) Date/Time Description
(Subtype)
---------------------------------------------------------------------
MMS 0 0 0 12 N Bit Error Daily
(XCDR) Threshold Exceeded
DRI 1 0 0 5 Y MPH Error: Counter
(DRIM) Mismatch: Uplink
DRI 1 0 0 1 N Bad Host Message
(DRIM)
Example 2
This example displays the output when there are no active alarms at site 2:
disp_act_alarm 2
Where: is:
2 location
68P02901W23-Q 2-197
disp_act_alarm Chapter 2: Device/function related commands
System response
There are no active alarms at site 2.
Example 3
This example displays the active alarms at PCU site 1 for MMS 0 0:
disp_act_alarm pcu_1 mms 0 0
Where: is:
pcu_1 location
mms device_name
0 dev_id1
0 dev_id2
System response
COMMAND ACCEPTED
ACTIVE ALARM INFORMATION FOR LOCATION PCU 1
Alarm Clear Config

Device Code Type Tag(hex) Date/Time Description
(Subtype)
--------------------------------------------------------------------
GBL 0 0 0 0 N Bit Error Daily
Threshold Exceeded
References
Related information
The following responses may be 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:
There are no active alarms at the PCU.
2-198 68P02901W23-Q
Technical Description: BSS Command Reference disp_bss
disp_bss
Description
The disp_bss command displays specific status information for all sites in a BSS or a
Remote Transcoder (RXCDR) site. The BSS or RXCDR device identifier where the
command is entered will be included in the output.
The status information shows the following:
• Sites that are equipped and their status.
• Number of sectors, or 1 if site is OMNI.
• GSM Cell IDs that are 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 below, 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 PCUs, if any have been equipped, and values of the RAC and BVCI associated with each cell.
Security level 1
Format
Syntax
disp_bss
68P02901W23-Q 2-199
disp_bss Chapter 2: Device/function related commands
Input parameters
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 22:

SITE FUNCTIONAL # OF GSM CELL ID FREQ BCCH
SITE STATE UNIT STATUS MCC MNC LAC CI RAC TYPE FREQ
---- ----- ----------- ---------------------------- --- ---- ----
0 B-U CRITICAL
CRITICAL 496 01 1 (0001h) 4 (0004h) 2 PGSM 40
CRITICAL 496 01 1 (0001h) 2 (0002h) 5 PGSM 60
PCU_0 B-U CRITICAL
PCU_1 B-U CRITICAL
1 D-U UNAVAILABLE
UNAVAILABLE 496 01 1 (0001h) 1 (0001h) 19 PGSM 87
UNAVAILABLE 496 01 1 (0001h) 6 (0006h) NA PGSM 75
References
Related command
"assess" on page 2-49.
2-200 68P02901W23-Q
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
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 to 120 BTS
dri
The DRI is the only device permitted for this command.
dev_id1
The first device identifier.
dev_id2
The second device identifier.
dev_id3
The third device identifier. This value defaults to 0 if no value is entered.
68P02901W23-Q 2-201
disp_cal_data Chapter 2: Device/function related commands
Example
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
Calibration data (All values in Hex):
Transmit Power Offset = 77
Receive System Data:
Antenna Number 1 2 3 4 5 6
--------------------------------------------------
73, 77, 74, 7E, 70, 81,
77, 81, 71, 76, 6D, 74,
74, 6F, 68, 69, 70, 83,
6D, 55, 56, 57, 55, 68,
67, 65, 66, 56, 80, 77,
66, 6C, 5F, 66, 78, 54,
67, 66, 56, 5F, 6C, 6D,
77, 5F, 66, 87, 9D, 56,
66, 66, 65, 64, 62, 44,
54, 5A, 5D, 5F, 60, 55,
55, 43, 44, 4D, 4E, 44,
65, 6F, 6D, 67, 77, 81,
66, 45, 4F, 4D, 44, 4A,
61, 60, 64, 66, 6D, 64,
54, 5D, 55, 5F, 60, 5B,
5D, 55, 5A, 67, 6F, 60,
Note that the second line of the system response indicates whether the data is read from the transceiver
or the database. In the example above the information is read from the transceiver.
References
Related commands
"clear_cal_data" on page 2-147, "store_cal_data" on page 2-464.
2-202 68P02901W23-Q
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
Prerequisites The background message feature must be purchased, installed, and
activated for this command to be successfully executed.
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 to be displayed, preceded by cell_number=.
68P02901W23-Q 2-203
disp_cbch_state Chapter 2: Device/function related commands
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
2-204 68P02901W23-Q
Technical Description: BSS Command Reference disp_cbch_state
Example 3
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)
Example 4
disp_cbch_state 3 cell_name="london-south"
Where: is:
3 msg_num
System response
References
Related commands
"chg_smscb_msg" on page 2-127, "del_smscb_msg" on page 2-182.
68P02901W23-Q 2-205
disp_cell Chapter 2: Device/function related commands
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 the add_cell command.
Security level 1
Prerequisites None
Format
Syntax
disp_cell <cell_desc> ["full"]
Input parameters
cell_desc
GSM Cell number of the cell to be displayed.
The name of the cell created using the cell_name command may be entered in place of the
cell_desc preceded by cell_number=. When the cell name is entered, it must be placed
inside double quotation marks and preceded by cell_name=.
2-206 68P02901W23-Q
Technical Description: BSS Command Reference disp_cell
“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.
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_desc
Example 2
In this example, the cell is identified using the cell_name “london-south":
disp_cell "london-south"
Where: is:
london-south cell_desc
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_desc
Example 4
In this example, the cell is identified in the four parameter format, using the cell_number 543 721 62259 08736:
68P02901W23-Q 2-207
disp_cell 543 721 62259 08736
Where: is:
543 721 62259 08736 cell_desc
System response
In every case, if the disp_cell command is entered correctly, the system displays the cell information. This
information differs from cell to cell. If the parameter “full” is included, all cell elements are displayed.
A typical example of the system display follows:
disp_cell 0 0 1 0 1 1 2
frequency_type = PGSM [1]

bsic = 16
wait_indication_parameters = 20
ccch_conf = 0
bs_ag_blks_res = 3
bs_pa_mfrms = 2
extended_paging_active = 0
number_sdcchs_preferred = 8
en_incom_ho = 1
intra_cell_handover_allowed = 1
inter_cell_handover_allowed = 1
number_of_preferred_cells = 6
ho_margin_def = 8
handover_recognized_period = 6
ul_rxqual_ho_allowed = 0
dl_rxqual_ho_allowed = 1
ul_rxlev_ho_allowed = 0
dl_rxlev_ho_allowed = 1
sdcch_ho = 0
sdcch_timer_ho = 1
interfer_ho_allowed = 0
pwr_handover_allowed = 1
ms_distance_allowed = 1
mspwr_alg = 0
handover_power_level = 2
pwrc = 1
intave = 8
timing_advance_period = 6
ms_p_con_interval = 6
ms_p_con_ack = 1
ms_power_control_allowed = 1
bts_p_con_interval = 2
bts_p_con_ack = 1
bts_power_control_allowed = 1
pow_inc_step_size_ul = 2
pow_inc_step_size_dl = 2
pow_red_step_size_ul = 2
pow_red_step_size_dl = 2
dyn_step_adj = 0
dyn_step_adj_fmpr = 10
max_tx_bts = 20
max_tx_ms = 37
rxlev_min_def = 15
ms_txpwr_max_def = 31
2-208 68P02901W23-Q
Technical Description: BSS Command Reference disp_cell
decision_alg_type = 0
decision_1_dl_rxlev_av_h = 0
decision_1_dl_rxlev_av_ih = 0
decision_1_dl_rxlev_av_p = 0
decision_1_dl_rxqual_av_h = 0
decision_1_dl_rxqual_av_p = 0
decision_1_n1 = 6
decision_1_n2 = 6
decision_1_n3 = 6
decision_1_n4 = 6
decision_1_n5 = 6
decision_1_n6 = 6
decision_1_n7 = 6
decision_1_n8 = 6
decision_1_ncell_rxlev_av_h_calc = 0
decision_1_p1 = 4
decision_1_p2 = 4
decision_1_p3 = 4
decision_1_p4 = 4
decision_1_p5 = 4
decision_1_p6 = 4
decision_1_p7 = 4
decision_1_p8 = 4
decision_1_p_bgt_rxlev_av_h = 0
decision_1_tim_adv_av_alg = 0
decision_1_ul_rxlev_av_h = 0
decision_1_ul_rxlev_av_ih = 0
decision_1_ul_rxlev_av_p = 0
decision_1_ul_rxqual_av_h = 0
decision_1_ul_rxqual_av_p = 0
alt_qual_proc = 0
l_rxqual_ul_p = 1600
l_rxqual_dl_p = 1600
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 1000
l_rxqual_dl_h = 1000
l_rxlev_ul_h = 12
l_rxlev_dl_h = 12
u_rxlev_ul_ih = 14
u_rxlev_dl_ih = 14
ms_max_range = 63
l_rxlev_ul_p = 50
l_rxlev_dl_p = 50
u_rxlev_ul_p = 60
u_rxlev_dl_p = 60
missing_rpt = 0
ba_alloc_proc = 0
link_fail = 10
link_about_to_fail = 8
full_pwr_rfloss = 0
cell_bar_access_switch = 0
cell_bar_access_class = 0000h
emergency_class_switch = 0
report_resource_tch_f_high_water_mark = 2
report_resource_tch_f_low_water_mark = 8
rxlev_access_min = 5£££ dtx_required = 2
attach_detach = 0
ncc_of_plmn_allowed = 4
max_retran = 0
ms_txpwr_max_cch = 3
68P02901W23-Q 2-209
tx_integer = 3
radio_link_timeout = 4
reestablish_allowed = 1
cell_reselect_hysteresis = 1
cell_reselect_param_ind = 0
cell_bar_qualify = 0
cell_reselect_offset = 0
temporary_offset = 0
penalty_time = 0
rapid_pwr_down = 0
rpd_trigger = 51
rpd_offset = 8
rpd_period = 2
References
Related commands
"add_cell" on page 2-21, "copy_cell" on page 2-157, "del_cell" on page 2-169, "disp_gsm_cells" on page 2-254.
2-210 68P02901W23-Q
Technical Description: BSS Command Reference disp_cell_map
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.
The disp_cell_status command shows the status details of the PCU that is currently serving a cell.
Security level 1
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.
Examples
Example 1
Display cell mapping at PCUs 1 and 2:
disp_cell_map pcu_1 pcu_2
68P02901W23-Q 2-211
disp_cell_map Chapter 2: Device/function related commands
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
System response
Current PCU site: PCU_1
Example 3
Display cell mapping at all PCUs:
disp_cell_map all
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
2-212 68P02901W23-Q
Technical Description: BSS Command Reference disp_cell_map
Example 4
This example displays cell mapping at a PCU when EGPRS feature is unrestricted:
disp_cell_map pcu
System response
PCU Site 0:
CELL ID GPRS STATUS

---------------------------- --------------------
001 01 666 (029Ah) 3 (0003h) GSM cell OOS
001 01 666 (029Ah) 30 (001Eh) GPRS Disabled
001 01 666 (029Ah) 40 (0028h) Barred
001 01 666 (029Ah) 41 (0029h) Unbarred, EGPRS Avail
001 01 666 (029Ah) 1 (0001h) Unbarred, EGPRS Unavail
END OF REPORT
68P02901W23-Q 2-213
disp_cell_status Chapter 2: Device/function related commands
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, then a prompt to continue. The cell_name is not
included when all of the cells at a site are to be displayed.
The system displays an error message if the BTF is not in service for any reason.
{22064}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
Format
Syntax
disp_cell_status <cell_desc>
disp_cell_status <location>
Input parameters
cell_desc
The GSM Cell ID of the cell to be displayed, preceded by cell_number=.
2-214 68P02901W23-Q
Technical Description: BSS Command Reference disp_cell_status
• The system being used (PGSM, EGSM, DCS1800, PCS1900 or GSM850)
location
Specifies the element location:
0 or bsc BSC
1 to 120 BTS
Output fields
RAC
This field shows the Routing Area Code (part of the cell identifier for GPRS cells).
Status
• Barred - A MS may not access the cell.
• Unbarred - A MS may access the cell.
GPRS Status
This field shows the status of a GPRS cell (barred/unbarred) and (when unbarred) whether EGPRS is available.
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 (Signalling 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
68P02901W23-Q 2-215
• Yes - The BSS BSSAP (Base Station System Application Part) Prohibited flag is set to
true. The cell will be barred while the BSS BSSAP Prohibited flag is true.
• No - The BSS BSSAP Prohibited flag is not set to true.
• NA - 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.
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.
AccCLASS Bar
This field specifies the access class(es) 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 will contain NA. If the
cell is unbarred, this field contains Nonewhen 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.
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 does not include entire carriers which are out of service.
2-216 68P02901W23-Q
Norm Outer TCH/F: FREE; INUSE; UNAVL

These fields specify the number of Full Rate Traffic Channels (TCH/H) in the outer zone
Norm Inner TCH/F: FREE; INUSE; UNAVL
These fields specify the number of Full Rate Traffic Channels (TCH/F) in the inner zone
Ext Outer TCH/F: FREE; INUSE; UNAVL
These fields specify the number of Full Rate Traffic Channels (TCH/F) in the extended outer
Norm Inner TCH/H: FREE; INUSE; UNAVL
These fields specify the number of Half Rate Traffic Channels (TCH/H) in the inner zone
Norm Outer TCH/G: FREE; INUSE; UNAVL
These fields specify the number of Generic Traffic Channels (TCH/G) in the outer zone
Norm Inner TCH/G: FREE; INUSE; UNAVL
These fields specify the number of Generic Traffic Channels (TCH/G) in the inner zone
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.
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
The example below shows the same cell number in four parameter format:
disp_cell_status 543 21 61986 34944
Where: is:
543 21 61986 34944 cell_number
68P02901W23-Q 2-217
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
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:
System response
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
FREE INUSE UNAVL

----- ----- -----
2-218 68P02901W23-Q
SDCCH 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:
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
FREE INUSE UNAVL

----- ----- -----
SDCCH 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
68P02901W23-Q 2-219
System response
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
------------------------------------------------------------
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.
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
2-220 68P02901W23-Q
System response
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
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 Cell ID 4 9 6 0 1 1 1 with the cell parameter
{22064}gsm_half_rate_enabled set to enabled.
disp_cell_status cell_number=4 9 6 0 1 1 1
Where: is:
4960111 cell_number
68P02901W23-Q 2-221
System response
GSM CELL ID
MCC 496
MNC 01
LAC 1 (0001h)
CI 4 (0004h)
RAC 4 (0004h)
---------------------------------------
Primary Freq Type PGSM
Secondary Freq Type N/A
BCCH Frequency 43
---------------------------------------
Status Barred
GPRS Status Barred
Reset in Prog No
GPRS Reset in Prog No
SPI in Prog No
BSS BSSAP Prhb NA
MSC BSSAP Prhb NA
SPI/MSC SCCP Prhb NA
AccClass Bar NA
GPRS AccClass Bar NA
Full Power Mode OFF
Ext Range Mode OFF
FREE INUSE UNAVL

----- ----- -----
SDCCH 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 NA NA NA
End of Report
Example 7
This example displays the status of an in-service cell capable of EGPRS and GPRS:
disp_cell_status 3
System response
GSM CELL ID
MCC 001
MNC 01
LAC 1 (0001h)
CI 40 (0028h)
RAC NA
----------------------------------------
Primary Freq Type EGSM
Secondary Freq Type N/A
BCCH Frequency 14
----------------------------------------
2-222 68P02901W23-Q
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 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/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.
68P02901W23-Q 2-223
disp_conn Chapter 2: 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 2
Prerequisites This command is only available at a BSC or RXCDR site.
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 range is 1 to 123 when this command is executed
from a BSC. The range is 1 to 55 when executed from an RXCDR.
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
2-224 68P02901W23-Q
Technical Description: BSS Command Reference disp_conn
System response
The BSS to RXCDR connectivity is as follows :
BSS MMS id 0 1 is connected to RXCDR 4 - MMS id 9 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
System response
The BSS to RXCDR connectivity is as follows :

Finished displaying BSS to RXCDR connectivity
68P02901W23-Q 2-225
disp_csfp Chapter 2: Device/function related commands
disp_csfp
Description
The disp_csfp command displays the per site CSFP algorithm or flow control values.
Security level 1
Prerequisites None
Format
disp_csfp <location> [<element>]
Input parameters
location
Specifies the element location:
0 or bsc BSC
1 to 120 BTS
element
algorithm Selects the CSFP algorithm method

flow_control Selects the flow control value
Examples
Example 1
This example shows the inputs required to display the CSFP algorithm at the BSC:
2-226 68P02901W23-Q
Technical Description: BSS Command Reference disp_csfp
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
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
References
Related command
"chg_csfp" on page 2-85.
68P02901W23-Q 2-227
disp_csfp_status Chapter 2: Device/function related commands
disp_csfp_status
Description
The disp_csfp_status command displays the status of all CSFPs equipped in the BSS network.
The output generated by this command is a three column listing with the following information:
SITE ID The site number
CSFP EQUIP Equipped indicator (YES or NO)
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
Format
Syntax
disp_csfp_status
2-228 68P02901W23-Q
Technical Description: BSS Command Reference disp_csfp_status
Input parameters
There are no input parameters with this command.
Examples
Example 1
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
System response
SITE,ID CSFP EQUIP STATUS
0,0 YES CODE LOADED
Example 2
This example shows the input required to display the status of the CSFP devices in the BSS
network and the output when no CSFP device is equipped.
disp_csfp_status
System response
SITE,ID CSFP EQUIP STATUS
0,0 NO *
References
Related command
"chg_csfp" on page 2-85.
68P02901W23-Q 2-229
disp_dte Chapter 2: Device/function related commands
disp_dte
Description
The disp_dte command displays DTE addresses. This command is primarily for
use by field technicians or installers.
Security level 1
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 Centre (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
2-230 68P02901W23-Q
Technical Description: BSS Command Reference disp_dte
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
References
Related command
"chg_dte" on page 2-88.
68P02901W23-Q 2-231
disp_element Chapter 2: Device/function related commands
disp_element
Description
The disp_element command displays the value of a database parameter in the CM database.
The syntax required to display each of the CM database parameters is included

in the parameter description in Chapter 5.
Security level 1
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 may
not 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.
2-232 68P02901W23-Q
Technical Description: BSS Command Reference disp_element
location
0 or bsc BSC
1 to 120 BTS
cell_desc
GSM Cell ID of the cell to be displayed, preceded by cell_number=.
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-Q 2-233
disp_element Chapter 2: 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
cell_number=5 4 3 2 1 61986 cell_desc
34944
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
References
Related information
For detailed information on database parameters, refer to "CM database param-
eters presentation" on page 5-2.
Related commands
"chg_element" on page 2-95.
2-234 68P02901W23-Q
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.
Equipment configurations typically vary by location, therefore, the devices and functions available
for display will vary from site to site. This command may be 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 may represent 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 will be displayed in place of an 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 may
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 last
TEST revision to the printed circuit board.
68P02901W23-Q 2-235
disp_equipment Chapter 2: Device/function related commands
The hvns for half size boards are not reported by the disp_equipment command.
Security level 1
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 to 120 BTS
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 may be used to display the hardware specific information for a device in
addition to the configuration information entered when the device is equipped. When this option is used to
display all of the equipment at a site, the output is a table which includes kit and serial numbers.
The full option is not allowed while in SYSGEN ON mode.
2-236 68P02901W23-Q
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>
disp_equipment <location> CIC <mms_id1> <mms_id2> <timeslot1>

Valid for remote transcoding:
disp_equipment <location> CIC <cic_num1>
Input parameters
location
0 or bsc BSC
1 to 120 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.
*
Indicates all CICs on the MMSs specified in the timeslot, regardless of group.
68P02901W23-Q 2-237
Examples
Example 1
In the following example, all equipments 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
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
2-238 68P02901W23-Q
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
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
32kbps GPRS TRAU allowed: yes
Example 4
This example shows the values entered when GCLK 0 0 0 at location 0 was equipped
and the associated hardware information:
disp_equipment 0 gclk 0 0 0 full
Where: is:
0 location
gclk device/func name
0 First identifier
0 Second identifier
68P02901W23-Q 2-239
Where: is:
0 Third identifier
full Full option is selected.
System response
Device identifier for the GCLK: 0
Cage number: 0
Slot number: 5
Is CLKX 0 (slot U4) present: NO
Is CLKX 1 (slot U3) present: YES
Is CLKX 2 (slot U2) present: YES
Hardware Information:
FRU: GCLK
Kit Number: hvn = 3
Serial Number: Not Applicable
Example 5
This example shows the values when the 16 kbit/s XBL option is enabled, the data rate is 16
kbit/s, and the XBL appears in MMS 00, timeslot 8, group 3.
The device displayed in the first line of the system response depends on where the
disp_equipment command is entered.
disp_equipment 0 xbl 1 0 0
Where: is:
0 location
xbl device/func name
1 AXCDR or ABSS device identifier
0 Second identifier for the XBL
System response
AXCDR device identifier for the XBL: 1
Device ID for the XBL: 2
Data rate for the XBL (Kbit/s): 16
First MMS identifier for this device: 0
Second MMS identifier for this device: 0
Timeslot on MMS where this device appears: 8
Group of MMS timeslot where this device appears: 3
LAPD T200 Timer value for this device is: 2500
LAPD N200 value for this device is: 3
LAPD K value for this device is: 7
The system does not display the upstream MSI id, the MMS id, the Downstream MMS id
or the downstream MSI id for disp_equipment PATH if the site is a TS_switch.
2-240 68P02901W23-Q
Example 6
This example shows the values when the XBL option is enabled, the data rate is 64 kbit/s,
and the XBL appears in MMS 00, timeslot 9.
The device displayed in the first line of the system response depends on where the
disp_equipment command is entered.
disp_equipment 0 xbl 2 0 0
Where: is:
0 location
xbl device/func name
1 AXCDR or ABSS device identifier
0 Second identifier for the XBL
System response
AXCDR device identifier for the XBL: 2
Device ID for the XBL: 0
Data rate for the XBL (Kbit/s): 64
First MMS identifier for this device: 0
Second MMS identifier for this device: 0
Timeslot on MMS where this device appears: 9
LAPD T200 Timer value for this device is: 2500
LAPD N200 value for this device is: 3
LAPD K value for this device is: 7
Example 7
This example displays DYNET the information about BTS network with five BTSs which loop back
to the BSC. The DYNET has twenty timeslots reserved for dynamic allocation.
disp_equipment 0 dynet 1 0
Where: is:
0 location
dynet device/func name
1 First identifier
0 Second identifier
System response
DYNET identifiers are: 1 0
Number of timeslots reserved for DYNET usage is: 20
BSC MMS identifiers are: 0 0
SITE identifier is: 1
Upstream MMS identifiers are: 0 0
Downstream MMS identifiers are: 0 1
68P02901W23-Q 2-241

SITE identifier is: BSC
Example 8
This example displays whether a site uses the dynamic allocation feature. The system
only displays this if the feature is unrestricted.
The information is displayed in the Share Terrestrial Backing Resources field:
• “Yes" means the site supports dynamic allocation.
• “No" means the site does not support dynamic allocation.

disp_equipment 0 site 1
Where: is:
0 location
site device/func name
1 First identifier
System response
SITE identifier: 1
Function ID for the LCF: 0
RSL rate: 64K
Share Terrestrial Backing Resources: Yes
Example 9
This example shows the equipment of CIC 1000 (local transcoding):
disp_equipment 0 cic 1000
Where: is:
0 location
cic device/func name
1000 First identifier
System response
CIC 1000 resides on MMS: 1 0, TS: 20, Group 3
Example 10
This example shows a display of DPROC 1 with the full option:
2-242 68P02901W23-Q
disp_equipment pcu dproc 1 full
Where: is:
pcu location
dproc device/func name
1 DPROC identifier
full Full details
System response
DPROC identifier:1
PCU slot number: 3
PCI Vendor ID: 1223
PCI Device ID: 231
PCI Revision ID: 17
Example 11
This example shows a display of DPROC 1 with the full option:
disp_equipment pcu dproc 1 full
Where: is:
pcu location
dproc device/func name
1 DPROC identifier
full Full details
System response
DPROC identifier:1
PCU slot number: 3
PCI Vendor ID: 1223
PCI Device ID: 231
PCI Revision ID: 17
Example 12
This example shows a PSP information, including the IP address, subnet mask, and router address:
disp_equipment pcu psp 0
Where: is:
pcu location
psp device/func name
0 PSP identifier
68P02901W23-Q 2-243
System response
PSP identifier: 0
PCU slot number: 8
IP Address: 121.49.0.252
Subnet Mask: 255.255.0.0
Router Address: 77.1.3.231
Example 13
This example shows the display of PCU site 0 at the BSC:
disp_equipment 0 pcu 0
Where: is:
0 location (BSC)
pcu device/func name
0 PCU identifier
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: 5
Primary Cells:
001 01 1 7
001 01 1 8
References
Related information
The hardware requirements and revision levels are given in Release Notes specific to each software release.
Related commands
"equip" on page 2-329, "modify_value" on page 2-404.
2-244 68P02901W23-Q
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 2
Prerequisites None
Format
Syntax
disp_exp_config <location>
Input parameters
location
Specifies the location of the site. Values are:
0 or bsc BSC
1 to 120 BTS
Example
The following example displays the TDM highway configuration of the BSC:
disp_exp_config 0
Where: is:
0 the location
68P02901W23-Q 2-245
disp_exp_config Chapter 2: Device/function related commands
System response
Highway 0 (CAGE 0)
-----------------
Connected to highway 1 by EXP 0 (U21 U9)
Highway 1 (CAGE 1)
-----------------
Highway 2 (CAGE 2)
-----------------
Highway 3 (CAGE 3)
-----------------
2-246 68P02901W23-Q
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
Prerequisites None
Format
Syntax
disp_flash
Input parameters
Example
The following example shows the version information of the flash EEPROM:
disp_flash
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.
68P02901W23-Q 2-247
disp_flash Chapter 2: Device/function related commands
Where: is:
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.
2-248 68P02901W23-Q
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
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 to 120 BTS
gclk_id
Identifier for GCLK. Values are 0 or 1.
Examples
Example 1
In this example, the LTA values for GCLK 1 at BSC 0 are displayed:
68P02901W23-Q 2-249
disp_gclk_avgs Chapter 2: Device/function related commands
disp_gclk_avgs 0 1
Where: is:
0 location
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.
Example 2
In this example, the LTA values for GCLK 1 at BSC 0 are not valid:
disp_gclk_avgs 0 1
Where: is:
0 location
1 gclk_id
System response
GCLK 1 0 0 Frequency Register values for site 0 are:
References
Related information
An alarm will be 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 2-151.
2-250 68P02901W23-Q
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 above or below 80 indicates the degree the
GCLK calibration has drifted. As the GCLK ages the value shown in the clock frequency register
will drift 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 a estimate of how far the GCLK has drifted from
its original calibration and how long it will be 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
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>
Input parameters
location
68P02901W23-Q 2-251
disp_gclk_cal Chapter 2: Device/function related commands
Specifies the location of the GCLK:

0 or bsc BSC
1 to 120 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
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).
2-252 68P02901W23-Q
Technical Description: BSS Command Reference disp_gclk_cal
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 2-151, "disp_gclk_avgs" on page 2-249.
68P02901W23-Q 2-253
disp_gsm_cells Chapter 2: Device/function related commands
disp_gsm_cells
Description
The disp_gsm_cells command displays the GSM cell(s) 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
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 to 120 BTS
Examples
Example 1
In this example, no GSM cells are associated with the BSC:
disp_gsm_cells 0
Where: is:
0 location
2-254 68P02901W23-Q
Technical Description: BSS Command Reference disp_gsm_cells
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 Local Type Cell Name
--- --- --------------- -------------- ----- ------- -------------
543 21 61713 (0xF111h) 4368 (0x1110h) 0 EGSM london-south
543 21 61713 (0xF111h) 8736 (0x2220h) 1 EGSM london-north
543 21 61713 (0xF111h) 13114 (ox222Ah) 2 EGSM bexley-west
Number of Sectors: 3
Example 3
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-Q 2-255
disp_gsm_cells Chapter 2: Device/function related commands
References
Related commands
"add_cell" on page 2-21, "copy_cell" on page 2-157, "del_cell" on page 2-169, "disp_cell" on page 2-206.
2-256 68P02901W23-Q
Technical Description: BSS Command Reference disp_hdlc
disp_hdlc
Description
The disp_hdlc command displays the HDLC channel assignment types of an in-ser-
vice 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
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
0 or bsc BSC
1 to 120 BTS
all All sites
dev/func name
68P02901W23-Q 2-257
disp_hdlc Chapter 2: Device/function related commands
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.
Examples
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 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
Example 2
This example shows how to display the HDLC channel assignments for LCF 0 0 0 at the BSC:
2-258 68P02901W23-Q
Technical Description: BSS Command Reference disp_hdlc
disp_hdlc bsc LCF 0 0 0
Where: is:
bsc location
LCF device / function ID
System response
Device: GPROC 0 0 0 (CPU ID: 0x0114)
Function: LCF 0 0 0
Number of LAPD Static Links (RSLs/XBLs) allocated to current board: 4

Legend: G/RSL - Free channel configured for a GSL or RSL
Range 0 1 2 3
------------ -----------------------------------------------------
00-03 Test Free MTL 0 0 0 RSL 32 0 0 RSL Free
Example 3
This example shows how to display the HDLC channel assignments for GPROC 0 0 0 at site 0:
disp_hdlc 0 GPROC 0 0 0
Where: is:
0 location
GPROC device / function ID
System response
Device: GPROC 0 0 0 (CPU ID: 0x0114)
Function: LCF 0 0 0
Number of LAPD Links (RSLs/XBLs) allocated to current board: 4

Range 0 1 2 3
------------ ------------------------------------------------------
00-03 Test Free MTL 0 0 0 RSL 32 0 0 RSL Free
68P02901W23-Q 2-259
disp_hopping Chapter 2: 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 will be 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 will be 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 will be displayed:
• Active hopping systems on a carrier and timeslot basis.
• Frequency hopping indicators (FHIs).
• Hopping sequence numbers (HSNs) for each FHI.
• Mobile allocations.
Security level 1
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.
2-260 68P02901W23-Q
Technical Description: BSS Command Reference disp_hopping
Format
Syntax
disp_hopping <site> [active]
disp_hopping <cell_desc> [<fhi> | active]
Input parameters
site
Specifies the location:
0 or bsc BSC
1 to 120 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=.
fhi
Frequency hopping indicator.
active
The active option displays the currently active hopping systems.
68P02901W23-Q 2-261
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
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
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, there are no associated hopping systems.
2-262 68P02901W23-Q
Technical Description: BSS Command Reference disp_hopping
disp_hopping cell 0 0 1 0 8 1 21
Where: is:
0 0 1 0 8 1 21 cell_desc
System response
GSM CELL: 001 08 (0001h) 21 (0015h)
-----------------------------------
No Hopping
FHI: 0 (Disabled) HSN: 0 MA:
Example 4
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)
Example 5
In this example, the affected cell is identified using the cell name “london-south".
disp_hopping cell_name="london-south"
Where: is:
cell_name=“london-south" cell_desc
System response
No Associated Hopping Systems.
68P02901W23-Q 2-263
References
Related command
2-264 68P02901W23-Q
Technical Description: BSS Command Reference disp_level
disp_level
Description
The disp_level command displays the current security level.

Security level 1
Prerequisites None
Format
Syntax
disp_level
Input parameters
Examples
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 2-115, "sysgen_mode" on page 2-469.
68P02901W23-Q 2-265
disp_link Chapter 2: 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 Centre, when an RXCDR is being used.
Security level 1
Prerequisites This command is only available on an RXCDR.
Format
Syntax
disp_link
Input parameters
Examples
In this example, the RXCDR OML and RXCDR MTL links between the BSC and the MSC are displayed:
disp_link
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
2-266 68P02901W23-Q
Technical Description: BSS Command Reference disp_link
Finished displaying all nailed connections
68P02901W23-Q 2-267
disp_link_usage Chapter 2: 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
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

1 to 120 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 55 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.
2-268 68P02901W23-Q
Technical Description: BSS Command Reference disp_link_usage
Examples
Example 1
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:
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
End of Report
Example 2
This example displays the output when no paths exist 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
No PATHs assigned
68P02901W23-Q 2-269
disp_mms_ts_usage Chapter 2: 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 for DYNET (DYNET)
• Reserved for DYNET (16K_DYN_RSL)
16K_DYN_RSL always falls under a 16K RSL timeslot as the first group. It
indicates that 3 extra timeslots are reserved for dynamic allocation.
• Reserved (RESERVED)
• Nailed (NAILED)
• Nailed on a path (NAILED PATH Timeslot Usage)
It also displays the timeslots that are reserved for dynamic allocation.
2-270 68P02901W23-Q
Technical Description: BSS Command Reference disp_mms_ts_usage
The display includes the device or function identifiers and the site where the device or function is equipped.
Security level Any
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
0 or bsc BSC
1 to 120 BTS
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
• If the MMS is viewed from a BTS, the header looks like this:
TS Group Usage Device ID Type Site TS
68P02901W23-Q 2-271
• 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.
Using this command with the Integrated MCell HDSL feature enabled,
disp_mms_ts_usage will indicate 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 Usage Device ID Type

Size Site CIC State
RTF Site RTF TS
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
2-272 68P02901W23-Q
6-7 Ater IDLE

4 64K_XBL 128 0 0 64K 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
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
18 MTL 0 0 0 0
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.
End of Report.
Example 2
This example displays the output on a RXCDR MMS showing the status of Ater channels, the
Ater channel status, and CICs assigned to the Ater channels:
Where: is:
0 location
System response
Start of Report:
Site: 0 MMS: 0 0
Timeslot Group Usage State CIC MMS Timeslot Group
0 0 Ater STATIC 58 1 0 9
1 MISMATCH 60 1 0 10
2 INUSE 62 1 0 11
3 IDLE 70 1 0 12
68P02901W23-Q 2-273
1 0 Ater IDLE 71 1 0 13
1 IDLE 72 1 0 14
2 IDLE 73 1 0 15
3 IDLE 74 1 0 17
End of Report.
Example 3
This example displays a BSC MMS for an RTF at a dynamic site:
Where: is:
0 location
System response
Start of Report:
Site: 0 MMS: 0 0
TS Usage Device ID Type Site CIC Group CIC State TS

Group RTF Site RTF TS
0 UNAVAILABLE
4 UNUSED
5 UNUSED
6 UNUSED
7 UNUSED
8 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
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.
2-274 68P02901W23-Q
Example 4
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.
Where: is:
0 location
System response:
Site: 0 MMS: 0 0
0 UNAVAILABLE
1 CIC 60 0 IDLE
CIC 61 1 IDLE
CIC 62 2 IDLE
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
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
68P02901W23-Q 2-275
30 UNUSED
31 UNUSED
Example 5
The following example displays the timeslot utilization on MMS 0 0 at the BSC, showing
a DYNET with a 16K RSL timeslot as the first group.
Where: is:
0 location
Start of Report:
Site: 0 MMS: 0 0

0 UNAVAILABLE
1 RSL 0 0 0 16K 1
16K DYN RES 0 0 0 1 1 0 0 0 2
2 None
3 1 0 0 0 4
2 UNUSED
3 RSL 0 3 0 16K 1
16K DYN RES 0 2 0 1 1 0 0 0 5
2 None
3 1 0 0 0 7
4 UNUSED
5 UNUSED
6 UNUSED
7 UNUSED
8 UNUSED
9 UNUSED
10 UNUSED
11 UNUSED
12 UNUSED
13 UNUSED
14 UNUSED
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 RSL 0 0 0 64K 3
28 DYNET 0 0 0 0 None
2-276 68P02901W23-Q
1 None
2 None
3 None
29 RSL 0 0 0 64K 2
30 RTF 0 0 0 FULL 2
31 RTF 0 0 0 FULL 2
End of Report.
Example 6
This example displays a BSC MMS for an RTF at a dynamic site:
disp_mms_ts_usage pcu 6 0
Where: is:
pcu location
System response
Start of Report:
Site: PCU_0 MMS: 6 0


0 UNAVAILABLE
1 GSL 0 0 0 PCU_0
5 UNUSED
6 UNUSED
4 UNUSED
5 UNUSED
6 UNUSED
7 UNUSED
8 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
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
68P02901W23-Q 2-277
31 UNUSED
Remote Transcoder Timeslot Usage:

Timeslot Group Usage MMS Timeslot Group
1 0 ADD_CHANNEL 1 0 9
1 1 0 10
2 1 0 11
3 1 0 12
1 1 0 14
2 1 0 15
3 1 0 17
1 1 0 21
2 1 0 22
16 RXCDR LINK 1 0 16
End of Report.
Example 7
This example displays the timeslot usage for an E1/T1 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
System response
Start of Report:
Site: PCU_0 MMS: 6 0

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
15 UNUSED
16 UNUSED
17 UNUSED
2-278 68P02901W23-Q
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.
Example 8
This example displays a timeslot usage on a span at site 3, MMS 1 0 where RTF 0 2 0 is a Half-Rate carrier.
Where: is:
3 location
System Response
Start of Report:
Site: 3 MMS: 1 0

0 UNAVAILABLE
1 64K_RSL 0 0 0 64K 3
2 UNUSED
3 UNUSED
4 UNUSED
5 UNUSED
6 UNUSED
7 UNUSED
8 UNUSED
9 UNUSED
10 NAILED 3 0 0 7
11 NAILED 3 0 0 8
12 NAILED 3 0 0 9
13 NAILED 3 0 0 10
14 NAILED 3 0 0 11
15 NAILED 3 0 0 12
16 NAILED 3 0 0 13
17 UNUSED
18 UNUSED
20 UNUSED
21 UNUSED
22 UNUSED
68P02901W23-Q 2-279
23 UNUSED
24 RTF 0 3 0 FULL 3
25 RTF 0 3 0 FULL 3
26 RTF 0 2 0 FULL 3
27 RTF 0 2 0 FULL 3
28 RTF 0 2 0 FULL 3
29 RTF 0 2 0 FULL 3
30 RTF 0 1 0 FULL 3
31 RTF 0 1 0 FULL 3
End of Report
Example 9
This example displays a timeslot usage of MMS 0.0 at site 1, where non-BCCH RTF 0 0 has 64k channels
allocated, RTF 1 0 has 16k channels allocated, and RTF 2 0 has 32k channels allocated:
Where: is:
1 location
System Response
Start of Report:
Site: 1 MMS: 0 0

0 UNAVAILABLE
1 64K_RSL 1 0 0 64K 1
2 UNUSED
3 UNUSED
4 UNUSED
5 UNUSED
6 UNUSED
7 UNUSED
8 UNUSED
9 UNUSED
10 UNUSED
11 UNUSED
12 UNUSED
13 UNUSED
14 UNUSED
15 UNUSED
16 UNUSED
17 UNUSED
18 RTF 2 0 0 FULL 1
19 RTF 2 0 0 FULL 1
20 RTF 2 0 0 FULL 1
21 RTF 2 0 0 FULL 1
22 RTF 1 0 0 FULL 1
23 RTF 1 0 0 FULL 1
24 RTF 0 0 0 FULL 1
25 RTF 0 0 0 FULL 1
2-280 68P02901W23-Q
26 RTF 0 0 0 FULL 1
27 RTF 0 0 0 FULL 1
28 RTF 0 0 0 FULL 1
29 RTF 0 0 0 FULL 1
30 RTF 0 0 0 FULL 1
31 RTF 0 0 0 FULL 1
End of Report
References
Related information
The timeslots states display as UNKNOWN due to SM not running.
A state of UNEQUIPPED indicates no circuits are equipped on the timeslot.
Related command
"chg_ts_usage" on page 2-138.
68P02901W23-Q 2-281
disp_neighbor Chapter 2: Device/function related commands
disp_neighbor
Description
The disp_neighbor command displays information of a specific neighbour cell or all neighbour cells.
A neighbour cell may be internal or external. An internal neighbour cell is inside the BSS in which the source
cell is located. An external neighbour cell is outside of the BSS in which the source cell is located.
The cell_name created using the cell_name command may be used to specify the source cell in place of
the src_gsm_cell_id. A cell_name may also be used to specify an internal neighbour cell in place of the
neighbor_cell_id. A cell_name may not be used to specify an external neighbour cell.
When the all option is used, the cell_name for each of the internal neighbour cells will be displayed
immediately after the neighbor_cell_id. If a cell_name has not been assigned to a neighbor_cell_id, No Name
Defined will be presented in the Neighbour cell name field. The cell_name for an external neighbour cell will
not be displayed. If a neighbour cell is an external cell, N/A. will be presented in the Neighbour cell name field.
Security level 1
Prerequisites For handovers to UMTS UTRAN cells, the Inter-RAT 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>]
Input parameters
src_cell_desc
GSM Cell ID of the neighbour list owner cell to be displayed.
GSM or UTRAN Cell ID of the neighbour list owner cell to be displayed.
2-282 68P02901W23-Q
Technical Description: BSS Command Reference disp_neighbor
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.
neighbor_cell_desc
GSM Cell ID of a neighbour cell.
The name of the cell created using the cell_name command may be entered in place of the cell_number.
test neighbor_cell_desc
A test cell may 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 (*) may be used in
place of a test cell number to indicate all test neighbours.
Examples
The examples below are possible displays. If the pbgt_alg_type for a cell is any number between 3 and 7 or
or the adj_chan_intf_test for a cell equals “yes" or 1, the system will present additional prompts. Refer to
the description of the add_neighbor command for the prompted power budget parameter values.
Example 1
In this example, a cell has no neighbour 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 neighbour 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 neighbour cells
68P02901W23-Q 2-283
System response
There are no associated neighbor cells
Example 2
In this example, the information describing a neighbour 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: 001 01 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)
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 neighbour cells displays. 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 neighbour cells
2-284 68P02901W23-Q
System response
Neighbor cell id: 5 4 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
Base station identity code (bsic): 16
Adjacent channel intf detection ho margin: -5
Neighbor congestion handover margin: -8

Neighbor cell name: No Name Defined
Placement: Internal
Synchronization enabled: 1
Neighbor congestion handover margin: -8

Placement: External
Synchronization enabled: N/A
Example 4
This example displays the information for all test cells.
68P02901W23-Q 2-285
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
GSM CELL ID BA BA BCCH
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
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:
0010112 neighbor_cell_desc
System response
Neighbor cell id: 001 01 1 (0001h) 2 (0002h)
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)
Base station identity code: 16
Receive quality handover margin: -63
Receive level handover margin: -63
Neighbor type 5 handover margin: 63
Neighbor adaptive handover pbgt trigger: 40
Neighbor congestion handover margin: 8
Range of the neighbor cell: Normal
Example 6
This example displays the information for all neighbour cells associated with a cell when the
Network Controlled cell reselection feature is enabled.
2-286 68P02901W23-Q
disp_neighbor 0 0 1 0 1 1 1
Where: is:
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
References
Related commands
"add_cell" on page 2-21, "add_neighbor" on page 2-35, "copy_cell" on page 2-157, "del_cell" on
page 2-169, "disp_cell" on page 2-206, "disp_gsm_cells" on page 2-254.
68P02901W23-Q 2-287
disp_nsvc Chapter 2: Device/function related commands
disp_nsvc
Description
The disp_nsvc command displays the requested NSVCs and their configurations.
Security level 1
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, pcu_0, pcu_1 or pcu_2 at which the GBL is defined.
GBL
Specifies the GBL as defined by value.
value
Varies according to the option chosen above.
Examples
Example 1
The following example displays NSVCI 68:
2-288 68P02901W23-Q
Technical Description: BSS Command Reference disp_nsvc
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 NSVCI 68 where GBL 0 at PCU site 0 is OOS:
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 GBL OOS 22 0 64 64
68 16 1 0 Unblocked 22 0 64 64
End of Report.
Example 3
The following example displays all the NSVCIs associated with GBL 0 at PCU site 1 during SYSGEN:
disp_nsvc pcu_1 GBL 0
Where: is:
pcu_1 PCU (second equipped)
GBL GBL
0 GBL 0
68P02901W23-Q 2-289
disp_nsvc Chapter 2: Device/function related commands
System response
Start of Report:
Site: PCU_1
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.
References
Related commands
"add_nsvc" on page 2-43, "del_nsvc" on page 2-178.
2-290 68P02901W23-Q
Technical Description: BSS Command Reference disp_options
disp_options
Description
The disp_options command displays the unrestricted and restricted optional features.
Security level 1
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:
---------------------------------------------------------------------
2 Daisy Chaining
3 Encryption Multiple Encryption
4 Frequency Hopping Baseband
5 Frequency Hopping Synthesizer
6 Receiver Spatial Diversity
68P02901W23-Q 2-291
disp_options Chapter 2: Device/function related commands
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 16Kbps LAPD RSL
28 16Kbps 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 Horizonmicro2 / Horizoncompact2
43 Enhanced Circuit Error Rate Monitor
44 Network Controlled Cell Reselection
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
56 TCU-A Support for AMR
57 TCU-B Support for AMR
58 Prp Capacity
59 Enhanced General Packet Radio Service
60 {22064} GSM Half Rate
Example 2
In this example, both the unrestricted and restricted options are displayed.
2-292 68P02901W23-Q
Technical Description: BSS Command Reference disp_options
disp_options all
Where: is:
all all options
System response
--------------------------------------------------------------------
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 16Kbps LAPD RSL
28 16Kbps 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 Horizonmicro2 / Horizoncompact2
44 Network Controlled Cell Reselection
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
68P02901W23-Q 2-293
disp_options Chapter 2: Device/function related commands
52 AMR Using Enhanced GDP

53 PBCCH/PCCCH
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
The following optional features have restricted use:

---------------------------------------------------------------------
46 ALM for EGSM carriers
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

---------------------------------------------------------------------
...
...
...
60 {22064}GSM Half Rate
---------------------------------------------------------------------
Example 4
In this example, the operator performs the disp_options command when no features are restricted.
disp_options all
Where: is:
all all options

---------------------------------------------------------------------
...
...
...
...

---------------------------------------------------------------------
2-294 68P02901W23-Q
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
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 processor(s) are located.
0 or bsc BSC
1 to 120 BTS
all All locations
68P02901W23-Q 2-295
disp_processor Chapter 2: 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:
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

Related Related
---- --------------------- ----- ----------------- --------- --------
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
END OF STATUS REPORT
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
System response
ADMIN STATES: L:Locked U:Unlocked E:Equipped NE: Not Equipped
Related Related
2-296 68P02901W23-Q
Technical Description: BSS Command Reference disp_processor

---------------------------------------------------------------------
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
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
Example 3
In this example, the statuses of the GPRS PCU processor boards are displayed.
Up to six TRAU GDS devices can be listed under a single DPROC (PICP).
disp_processor pcu_0
Where: is:
pcu_0 the first equipped PCU.
System response
MMI-RAM 0115 -> disp_proc pcu_0
PROCESSOR STATUS INFORMATION FOR LOCATION PCU 0:
NC: Not Connected
CPU# Processor Name State Reason Related Related

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
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
68P02901W23-Q 2-297
disp_processor Chapter 2: Device/function related commands
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
GDS 3 0 N/A
MSI 15 0 N/A
GDS 12 0 N/A
GDS 4 0 N/A
MSI 16 0 N/A
GDS 13 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
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
GDS 10 0 N/A
MSI 22 0 N/A
GDS 19 0 N/A
2-298 68P02901W23-Q
Technical Description: BSS Command Reference disp_relay_contact
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
Prerequisites The EAS device must be equipped and the EAS device parameters
established using the equip eas command. See"equip" on page
2-329.
Format
Syntax
disp_relay_contact <location> <device_id>
Input parameters
location
0 or bsc BSC
1 to 120 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
Example
This example displays the relay contacts for all EAS devices:
68P02901W23-Q 2-299
disp_relay_contact Chapter 2: Device/function related commands
disp_relay_contact
System response
Relay 1: Closed
Relay 2: Open
Relay 3: Open
Relay 4: Closed
References
Related command
"equip" on page 2-329
2-300 68P02901W23-Q
Technical Description: BSS Command Reference disp_rtf_channel
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 or not the RTF is equipped for GPRS and EGPRS, and if capable of supporting EGPRS
{22064}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
Format
Syntax
disp_rtf_channel <location> <rtf_id_1> <rtf_id_2> [<timeslot_number>]
Input parameter
location
0 or bsc BSC
1 to 120 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.
68P02901W23-Q 2-301
disp_rtf_channel Chapter 2: Device/function related commands
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.
• 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
System response
Start of report for RTF 0 2 at location 1:
TIMESLOT SUB-CHAN STATE
-------------------------------------------------------
2-302 68P02901W23-Q
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):
Where: is:
1 location
0 rtf_id_1
0 rtf_id_2
System response
Packet Radio Capabilities: 64k
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 (64k PDTCH) Switchable 0 N/A
4 (64k PDTCH) Reserved 0 N/A
Example 3
This example displays the status of RTF 0 2 at Site 1 when the RTF is equipped to support EGPRS,
but the RTF is currently assigned to a DRI unable to support EGPRS:
Where: is:
1 location
0 rtf_id_1
2 rtf_id_2
System response
RTF currently capable of supporting EGPRS?: NO
68P02901W23-Q 2-303

----------------------------------------------------------------
Example 4
This example displays the status of RTF 0 2 at Site 1 when EGPRS is restricted and GPRS is unrestricted:
Where: is:
1 location
0 rtf_id_1
2 rtf_id_2
System response
Packet Radio Capabilities: none
----------------------------------------------------------------
Example 5
This example displays the status of RTF 0 1at site 1, when the RTF is not configured for EGPRS.
Where: is:
1 location
0 rtf_id_1
1 rtf_id_2
System response
Packet Radio Capabilities: none
RTF currently capable of supporting EGPRS?: NO
2-304 68P02901W23-Q
----------------------------------------------------------------
0 (TCH/F) N/A 0 IDLE
End of Report.
Example 6
This example displays the status of RTF 1 0 at BTS location 12:
Where: is:
12 location
1 rtf_id_1
0 rtf_id_2
System response
----------------------------------------------------------------
0 (BCCH + SDCCH/4) N/A BCCH ACTIVE
0 IDLE
1 IDLE
2 IDLE
3 IDLE
4 (16K PDTCH) SWITCHABLE 0 IDLE
5 (16K PDTCH) SWITCHABLE 0 ACTIVE
6 (16K PDTCH) RESERVED 0 IDLE
7 (16K PDTCH) RESERVED 0 INTRANS
End of Report.
Example 7
{22064}
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
68P02901W23-Q 2-305
Where: is:
0 rtf_id_2
5 timeslot
System response
-------------------------------------
5 (TCH/G) 0 IDLE
End of Report.
Example 8
{22064}
This example displays the carrier states of RTF 1 0, timeslot 6 (a Full Rate traffic channel) at
site 1 with half_rate_enabled element set to 1 (enabled):
Where: is:
1 location
1 rtf_id_1
0 rtf_id_2
6 timeslot
System response
-------------------------------------
6 (TCH/F) 0 ACTIVE
End of Report.
Example 9
{22064}
This example displays the carrier states of RTF 1 0, timeslot 7 (a Half Rate traffic channel)
at site 1 with half_rate_enabled element set to 1 (enabled):
Where: is:
1 location
1 rtf_id_1
0 rtf_id_2
7 timeslot
2-306 68P02901W23-Q
System response
-------------------------------------
7 (TCH/H) 0 ACTIVE
1 ACTIVE
End of Report.
68P02901W23-Q 2-307
disp_rtf_path Chapter 2: 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. For closed loop daisy chain configurations, redundant PATHs exist for each DYNET equipped.
Security level 1
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 1 to 120.
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.
2-308 68P02901W23-Q
Technical Description: BSS Command Reference disp_rtf_path
Examples
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
Example
This example displays the PATH devices assigned to RTF 0 0 at BTS 1, when the BTS uses dynamic allocation:
disp_rtf_path 1 0 0
Where: is:
1 location
0 rtf_id_1
0 rtf_id_2
System response
Start of Report:
SITE ID : 1
1st RTF Identifier : 0
2nd RTF Identifier : 0
PATH 1 0 0 Status : SHARED CONNECTED Busy Unlocked
PATH 1 1 0 Status : SHARED REDUNDANT Busy Unlocked
PATH 1 2 0 Status : SHARED REDUNDANT Disabled Unlocked
68P02901W23-Q 2-309
disp_rtf_path Chapter 2: Device/function related commands
PATH 1 5 0 Status : SHARED REDUNDANT Busy Unlocked
End of Report
References
Related commands
"add_rtf_path" on page 2-45, "chg_rtf_freq" on page 2-120, "copy_path" on page
2-163, "del_rtf_path" on page 2-180.
2-310 68P02901W23-Q
Technical Description: BSS Command Reference disp_severity
disp_severity
Description
Use the disp_severity command to view the current severity level for device alarms
and non-reconfiguration alarms.
Security level 1
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 is defined by all valid numeric values in the range 0 to 254.
• Refer to "Alarm devices" on page 2-19 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.
Example
This example shows how to display the severity of GPROC alarm code 8.
68P02901W23-Q 2-311
disp_severity Chapter 2: Device/function related commands
disp_severity gproc 8
Where: is:
gproc device_name
8 alarm_code
System response
GPROC Alarm code 8 severity: Investigate
2-312 68P02901W23-Q
Technical Description: BSS Command Reference disp_site
disp_site
Description
The disp_site command displays the site, BSC or BTS, with which the operator is interacting.
Security level 1
Prerequisites None
Format
Syntax
disp_site
Input parameters
Example
This example displays the current site:

disp_site
System response
Current site number is 6
References
Related command
"equip" on page 2-329.
68P02901W23-Q 2-313
disp_throttle Chapter 2: Device/function related commands
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
Prerequisites None
Format
Syntax
disp_throttle [<device_name> <alarm_code>]
Input parameters
device_name
alarm_code
Identifies the alarm to be throttled. The range of values for the alarm_code is 0 to 254.
Examples
Example 1
This example displays the throttle period for device DRI, alarm code 66:
2-314 68P02901W23-Q
Technical Description: BSS Command Reference disp_throttle
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
....
References
Related command
"chg_throttle" on page 2-133.
68P02901W23-Q 2-315
disp_time Chapter 2: 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
Prerequisites None
Format
Syntax
disp_time
Input parameters
Example
In this example, the system time is displayed.

disp_time
2-316 68P02901W23-Q
Technical Description: BSS Command Reference disp_time
System response
Fri Nov 12 14:13:48 2002
References
Related commands
"chg_time" on page 2-135, "time_stamp" on page 2-475.
68P02901W23-Q 2-317
disp_trace_call Chapter 2: Device/function related commands
disp_trace_call
Description
The disp_trace_call command displays the mode, value, and trace data currently enabled
in the BSS and the destination of the trace report.
Security level 1
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 shows the input required to display all instances that exist in the system.
disp_trace_call
System response
Start of Trace Report
Trace Reference: c0270002h

Scope: site=2 RTF 0 1
Trigger Event: All (call origination, handover, or any call)
Trace Data: Basic, RSS
Data during handover only: No
2-318 68P02901W23-Q
Technical Description: BSS Command Reference disp_trace_call
Interval (x480ms): 8
Mode: Nth call=7
Max simultaneous: 4
Trigger enabled time: 10:23 to 11:00
Total calls to be traced: Not specified
Trace beyond scope: Yes
Destination of trace data: MMI
Triggering enabled: No
Total calls currently traced

----------------------------
Trace Reference Count
--------------- -------
c0270002h 0
Call Trace Flow Control Status

------------------------------
Automatic Flow Control: Halted for this BSS.
Automatic Flow Control: Activated by BSS.
Automatic Flow Control: Activated by OMC.
End of Report
Example 2
The following is an example of the specified call trace instance currently active in the BSS.
disp_trace_call 2Fh
System response
Start of Trace Report
Trace Reference: 2fh

Scope: BSS wide
Trigger Event: All (call origination, handover, or any call)
Trace Data: Event: Basic, RSS, DTAP
Data during handover only: No
Interval (x480ms): 2
Mode: Nth call=4
Max. simultaneous: 5
Total calls to be traced: 20
Trace beyond scope: No
Destination of trace data: MMI, OMC
Triggering enabled: Yes
Number of calls
--------------
Trace Reference Currently tracing Total calls traced
--------------- ----------------- ------------------
2fh 2 10
Automatic Flow Control: Not Halted for this BSS.

Automatic Flow Control: Activated bu BSS.
Automatic Flow Control: De-Activated by OMC.
End of Report
68P02901W23-Q 2-319
disp_trace_call Chapter 2: Device/function related commands
References
Related commands
"trace_call" on page 2-477, "trace_stop" on page 2-489.
2-320 68P02901W23-Q
Technical Description: BSS Command Reference disp_traffic
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
Prerequisites The GPRS feature must be unrestricted to display PCU data.
Format
Syntax
disp_traffic <location> <unique_PATH_identifier>
Input parameters
location
pcu PCU
1 to 120 BTS
Specifies the unique PATH to a particular BTS. The range of values is 0 to 11.
Examples
Example 1
This example displays the RSL devices and RTF functions equipped on unique PATH 3 at site 1:
disp_traffic 1 3
68P02901W23-Q 2-321
disp_traffic Chapter 2: Device/function related commands
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
System response
Start of Report:
SITE ID: PCU

Unique GDS ID: 0
GPRS
End of Report
Example 3
This example displays the PCU data when both TRAU and signalling present:
disp_traffic pcu 0
System response
Start of Report:
SITE ID: PCU

Unique GDS ID: 0
GSL 1 0 0
GSL 2 0 0
GSL 3 0 0
GPRS DATA
End of Report
2-322 68P02901W23-Q
Technical Description: BSS Command Reference disp_traffic
References
Related command
"add_rtf_path" on page 2-45.
68P02901W23-Q 2-323
disp_transcoding Chapter 2: Device/function related commands
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
Prerequisites The enhanced GDP provisioning feature must be unrestricted.
Format
Syntax
disp_transcoding
Input parameters
There are no parameters for this command.
Example
Example 1
This example displays the transcoding data:
disp_transcoding
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 <
-------
2-324 68P02901W23-Q
Technical Description: BSS Command Reference disp_transcoding
n/a : not applicable

N-E : not equipped
68P02901W23-Q 2-325
disp_version Chapter 2: Device/function related commands
disp_version
Description
The disp_version command displays the version and revision numbers of the current software load.
Security level 1
Format
Syntax
disp_version
Input parameters
Example
To display the version and revision information:

disp_version
System response
BSP Code Version: 5.0.0.8
BSP Database Level Number: 35F2
CSFP Code Version: 5.0.0.8
CSFP Database Level Number: 35E5
2-326 68P02901W23-Q
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
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
System response:
X.25 Packet Size: 128
X.25 Window Size: 2
68P02901W23-Q 2-327
disp_x25config Chapter 2: Device/function related commands
References
Related command
"chg_x25config" on page 2-144.
2-328 68P02901W23-Q
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 for each.
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 the Related Information section
of this command reference. Charts showing equipage hierarchy are also included.)
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, 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.
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.
Security level 2
Prerequisites Some devices and functions can be equipped only after other
device(s) have been equipped.
To equip or modify some devices, the system must be in the
SYSGEN ON mod
e.Some devices require the site to be loc
ked.To equip a device or function with a frequency, it first must be
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.
Operator actions Refer to the instructions included with each device or function for
specific actions to be taken when using this command.
68P02901W23-Q 2-329
equip Chapter 2: Device/function related commands
Format
Syntax
equip <location> <dev/func_name>
Input parameters
location
0 or bsc BSC
1 to 120 BTS
A BSC of type 0 must equip remote sites with a BSP. A BSC of type 1 or 2
must equip remote sites with an LCF.
No more than three PCUs may be equipped per BSC.
dev/func_name
Identifies the device or function being equipped; 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 PATH PCU PSP RSL
SITE XBL
The following functions can be equipped with this command:

LCF OMF RTF
Examples
Example 1
In this example, a CAGE is being equipped at the BSC:
2-330 68P02901W23-Q
equip bsc cage
Where: is:
bsc location
cage device being equipped
System response
A series of prompts associated with the CAGE device are presented. Refer to the description
of the CAGE prompts in the Related information section.
Example 2
In this example, a path with two links is equipped. All of the prompts that define
the path are included in this example:
equip 0 path
Where: is:
0 The location.
path The device being equipped.
Enter the terminating SITE id: 2
Where: is:
2 The site where the path terminates.
Enter the Unique PATH identifier: 0
Where: is:
0 The unique path identifier.
Enter the BSC MSI identifier: 0

Enter the BSC MMS identifier: 0
Where: is:
0,0 The uplink MSI and MMS identifiers from the BSC to the
next site in the path (BTS 1).
Enter the SITE identifier: 1
Where: is:
1 The site ID of the site (BTS 1) linked to the BSC.
68P02901W23-Q 2-331
Where: is:
2,0 The downlink MSI and MMS identifiers from BTS 1 to
the BSC.
Enter the downstream MSI identifier: 2

Enter the downstream MMS identifier: 1
Where: is:
2,1 The uplink MSI and MMS identifiers from the BTS 1 to
the next site in the path (BTS 2).
Enter the SITE identifier: 2
Where: is:
2 The site ID of the site (BTS 2) linked to the BTS 1.
The site identifier equals the terminating site identifier.
Prompts for downstream MSI and MMS identifiers are
not presented.

Where: is:
2,1 The downlink MSI and MMS identifiers from BTS 2 to
the BTS 1.
System response
COMMAND ACCEPTED
References
Related commands
"disp_equipment" on page 2-235; "lock_device" on page 2-387; "modify_value" on page 2-404;
"reassign" on page 2-415; "state" on page 2-448; "unequip" on page 2-494; "unlock_device" on page
2-504; "freq_types_allowed" on page 2-378; "shutdown_device" on page 2-436.
Related information
The following related information covers the order and conditions in which devices and functions can be
equipped, and lists the prompts that are generated during the execution of the equip command.
2-332 68P02901W23-Q
Equipage hierarchy
Some devices and functions can only be equipped after other device(s) have been equipped. For
example, a CAGE must be equipped before an BTP can be equipped.
Other devices are automatically equipped. For example, a MMS is equipped au-
tomatically when equipping a MSI.
Equipage hierarchy charts show the order in which devices and functions are equipped in the following systems:
• RXCDR.
• InCell.
• M-Cell and Horizonmacro.
• GPRS.
68P02901W23-Q 2-333
RXCDR
Figure 2-1 shows the device and function hierarchy for RXCDR devices and functions. A
MMS is automatically equipped when a MSI is equipped.
Figure 2-1 Remote Transcoder (RXCDR) devices and functions
RXCDR
CAB ABSS
Conn_Link
CAGE
KSW GCLK BSP MSI
MMS *
(See Note
below)
OML CBL CIC

XBL
NOTE: * indicates an automatically equipped device
2-334 68P02901W23-Q
InCell
Figure 2-2 shows the device and function hierarchy for InCell systems. A MMS is
automatically equipped when a MSI is equipped.
Figure 2-2 BSC and InCell BTS
BSS SITE (BSC)
CAB PCU DYNET AXCDR
Conn_Link
CAGE
KSW GCLK BSP GPROC CSFP EAS MSI
LCF OMF
MMS *
(See Note
below)
RF_Unit
GSL MTL OML CIC

LMTL CBL XBL
NOTE: * indicates an automatically equipped device
68P02901W23-Q 2-335
M-Cell and Horizonmacro equipage hierarchy chart

Figure 2-3 shows the device and equipment hierarchy for M-Cell and Horizonmacro systems. GCLK and
CSFP functionality are built into a MCU and are automatically equipped when a BTP is equipped.
Figure 2-3 In-Cell and Horizonmacro equipage hierarchy chart
2-336 68P02901W23-Q
GPRS
Figure 2-4 shows the device and function hierarchy for the PCU device in a GPRS system. CAB and CAGE are
automatically equipped when a PCU is equipped. A MMS is automatically equipped when a MSI is equipped.
Figure 2-4 GPRS PCU devices and functions
68P02901W23-Q 2-337
Equipping devices
This section references conditional information for the rules on equipping the various devices,
and the lists the equip command prompts that occur with each device.
ABSS
The Associated Base Station Subsystem (ABSS) may be equipped with the system in SYSGEN
ON mode. 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.
This device may 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 a RXCDR site. The maximum number of ABBSs
that can be equipped at an RXCDR site is 10.
An ABSS device may not be unequipped if it is specifically referenced in the BSS-RXCDR connectivity table.
The BSS-RXCDR connectivity table is created using the add_conn command.
Prompt Optional Range Default Comments

Enter the ABSS device N 1 to 128 none This value corresponds to the
id: BSS network entity that this
device represents.
AXCDR
The Associated RXCDR (AXCDR) may be equipped with the system in SYSGEN ON mode.
This device also may be equipped when the system is outside the SYSGEN ON
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 may not be unequipped if it is specifically referenced in the BSS-RXCDR connectivity table.

Enter the AXCDR device N 1 to 128 none This value corresponds to the
id: RXCDR network entity that this
device represents.
Perform CIC valida- N yes or no none CIC validation must be enabled
tion?: to 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 {22064}and/or
the GSM Half Rate feature is
unrestricted
2-338 68P02901W23-Q

Enter the CIC blocking N 0 to 245 0 A prompt for this value is
threshhold: presented only if the eac_mode
is enabled.
Enter the CIC N 1 to 225 0 A prompt for this value is
unblocking threshold: presented only if the eac_mode
is enabled.
BSP
The Base Station Processor (BSP) may be equipped with the system in SYSGEN ON mode.
The BSP may also be equipped when the system is outside the SYSGEN ON mode
and it is to be the standby device.

Enter the BSP N 0 or 1 none
identifier:
Enter the cage number: N 0 or 1 none BSPs may be only GPROCs
with the following Cage and Slot
Enter the slot number: N 20, 24, none
restrictions based on site type:
25, 26
BSC and BSS sites:
- cage 0, slots 20, 24
-cage1, slot 20
RXCDR sites:
- cage 0, slots 25, 26
- cage 1, slot 25
BTS sites: not allowed
Enter maximum MTLs this N 0 or 1 none This prompt is not presented if
BSP may manage: the equip command is entered at
an RXCDR.
BSS
The Base Station Subsystem (BSS) should be the first device equipped by the operator
during SYSGEN mode at a BSS site.

Enter the BSS N 1 to 128 none
identifier:
Is local transcoding N yes or no none
performed at the BSC
(yes/no):
BTP
The Base Transceiver Processor (BTP) may be equipped with the system in SYSGEN ON mode.
When equipping BTPs to M-Cell sites, BTP 0 must be the first BTP equipped.
68P02901W23-Q 2-339
This device may be equipped only at a BTS site.

For a bts_type of 0, no more than two radios should 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 six associated MMS devices) at the BTS site.
The following prompts do not display for all installations. Some devices set certain parameters
automatically. The system does not prompt for values set automatically.

Enter BTP identifier: N 0 or 1 none For M-Cell2 and M-Cell6 sites,
this prompt has the following
meaning:
0 = card frame 0
1 = card frame 1
Enter the cage number: N 14 or 15 none BTPs may only be GPROCs
with the following Cage and Slot
Enter the slot number: N 20 or 24 none
restrictions based on site type:
BSC, BSS and RXCDR sites: not
allowed
BTS sites:
age 15, slots 20, 24
cage 14, slot 20
Enter maximum DRIs N 0 to 6 none If the BTS type is 0, the maximum
supported by this BTP: number of DRIs may not be 0.
CAB
The cabinet (CAB) may be equipped with the system in SYSGEN ON mode.
The system rejects the equip CAB command if the CAB is equipped for GPRS. The CAB
is automatically equipped when the PCU is equipped.
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.

Enter the N 0 to 15 none
CABINET
identifier:
2-340 68P02901W23-Q

Enter the N 0 to 25 none M-Cell and transceiver cabinets cannot be
cabinet type: equipped at an InCell site.
InCell cabinets cannot be equipped at an
M-Cell site.
The system rejects the command if:
• The bts_type not = 0, and
• The cabinet_type = 10, 11, 14, 15, 16 or

20.
68P02901W23-Q 2-341

This value may be entered by number or as a
string:
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
17 N/A N/A
18 horizonmacro Horizonmacro
master cabinet
19 horizon- Horizonmacro
macro_ext extention cabinet
20 m_cel- M-Cellarena
larena_macro macro BTS
(Horizoncompact)
22 horizonmicro2 Horizonmicro2 BTS
23 horizoncom- horizoncompact2
pact2 BTS
24 horizonmacro2 HorizonIImacro
cabinet
25 horizon- HorizonIImacro
macro2_ext extention cabinet
2-342 68P02901W23-Q

Enter the N 1 to 15 none This value may 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 may also be
entered:
• Numbers and strings may be combined in

a single command.
• A comma must separate different

frequency types, like this: pgsm, 2, 4
Is an Y yes or no none This prompt is only displayed if the site type is
internal M-Cellcity, Horizonmicro or Horizoncompact
HDSL modem
present?:
Is an Y yes or no none This prompt is only displayed if the site type
internal is M-Cellcity or Horizonmicro
integrated
antenna
present?:
CAGE
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 1 for BSS, BSC, or RXCDR type sites
and cage 14 and/or 15 must be equipped at BTS type sites.
This device may be equipped with the system in SYSGEN ON mode.
68P02901W23-Q 2-343
The system rejects the equip CAGE command if the cage is equipped for GPRS. The cage
is automatically equipped when the PCU is equipped.
At M-Cell sites, the CAGE cannot be equipped. The cage is automatically equipped
when the first BTP at a site is equipped.

Enter the device N 0 to 15 none The cage number (ID) must be
identification for the equal to the setting on the LANX
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 that N 0 to 3 none
manages the cage:
Enter the KSWX Y 0 to 4 none
connecting cage to KSW
for TDM 0:
Enter KSWX connecting Y 0 to 4 none
cage to KSW for TDM 1:
Enter the cabinet to N 0 to 23 none
which the cage belongs:
Is an IAS connected?: Y yes or no yes
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 would occupy a slot that is already occupied.
CBL
The Cell Broadcast Link (CBL) may be equipped with the system in either the
SYSGEN ON or SYSGEN OFF mode.
The CBL may not be equipped at an RXCDR site.
The CBL may be equipped only at a BSC (site 0).
The CBL may not be equipped on an HDSL link.

Enter the device ID Y 0 0
for the CBL:
2-344 68P02901W23-Q

Enter the first MMS N 0 to 55 none
identifier for this
device:
Enter the second MMS N 0 or 1 none
identifier for this
device:
Enter the timeslot on N 1 to 24 for none
MMS where this device T1 links,
appears: 1 to 31 for
E1 links
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
The Circuit Identity Code (CIC) may be equipped with the system in either SYSGEN
ON or SYSGEN OFF mode.
A single CIC or a range of unique CICs may be equipped for each MMS.
When equipping a range of CICs, the equip CIC command is accepted if all CICs in the range can be
equipped. 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.
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 may be equipped only at a BSC or RXCDR (site 0).
The CIC may not 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 also is prompted for a static MMS timeslot to the RXCDR. This is not required if
the BSC is operating in static mode. 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.
68P02901W23-Q 2-345
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
not need to be equipped to GDP just because efr_enabled is enabled.
Equipping CICs at a 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. This is not required if the
BSC is operating in static mode. In this case, the CIC is blocked.
A CIC equipped at an RXCDR may be used for multiple BSSs.

Enter the CIC(s): N 0 to 65535 none No more than 128 CICs may be
equipped at a time (for remote
transcoding). For RXCDR and
local transcoder BSS, only 30
CICs may be equipped.
Multiple CICs may be entered
using the format: CIC# to CIC#
(for example, 255 to 286).
resource(s): N 1 to 128 none This prompt only appears for
Which RXCDR is remote transcoding BSC sites
providing the TRAU only.
Which BSS is managing N 1 to 128 none This prompt only appears for
the CIC(s): RXCDR sites only.
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 to 24 none This prompt appears only if a
timeslot: (T1 links), MMS ID is specified.
1 to 31 (E1
links)
Enter starting N 0 to 3 none This prompt appears only if
subgroup: there is remote transcoding and
an MMS is specified.
2-346 68P02901W23-Q

Enter the MMS ID to N 1 to 24 (T1 none This prompt appears for RXCDR
MSC: links) sites and local transcodings only.
Enter starting N 0 to 31 (E1 none This prompt appears for RXCDR
timeslot: links) sites and local transcodings only.
COMB
The Combiner (COMB) may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode.

Enter the first COMBiner N 0 to 13 none
identifier:
Enter the COMBiner N 0 to 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
The Code Storage Facility Processor (CSFP) may be equipped with the system in either
the SYSGEN ON or SYSGEN OFF mode.
At an M-Cell site, the CSFP cannot be explicitly equipped by the user; instead the CSFP is
automatically equipped when the first BTP at a site is equipped.

Enter the CSFP N 0 or 1 none This prompt only appears at a
identifier: BSC.
Enter the cage number N See none BSS sites: cages 0 to 13, slots 18
: Comments to 25
BSC sites: cages 0 to 13, slots
18 to 25
BTS sites: cages 2 to15, slots 18
to 25
RXCDR sites: cages 0 to13,
slots 25 and 26
Enter the slot number: N See none BSS sites: cages 0 to 13, slots 18
Comments to 25
BSC sites: cages 0 to 13, slots
18 to 25
BTS sites: cages 2 to15, slots 18
to 25
RXCDR sites: cages 0 to 13,
slots 25 and 26
DHP
The Digital Radio Host Processor (DHP) may be equipped with the system in either
the SYSGEN ON or SYSGEN OFF mode.
68P02901W23-Q 2-347
The DHP may be equipped only at a BSS or a BTS site.

The DHP may not be equipped at an M-Cell site.
The underlying GPROC may not have to be equipped to equip a DHP.

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

maximum number of DRIs supported by a DHP.
DPROC
The Data Processor (DPROC) may be equipped with the system in either the SYS-
GEN ON or SYSGEN OFF mode.
The DPROC can be equipped only if the GPRS feature is unrestricted.
The DPROC may 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) or a Packet Resource Processor (PRP).
At least one PRP and one PICP DPROC are required per PCU.
A PICP DPROC can support from 0–2 LAPD GDS devices.
A PRP DPROC can support from 0–4 TRAU GDS devices.
There can be a maximum of 10 PRP DPROCs equipped per PCU
DPROCs are not redundant.
2-348 68P02901W23-Q
A DPROC can be equipped only if the PCU is equipped.
Prompt Optional Range Default

Enter the DPROC id: N 1 to 6 or none
11 to 16
Enter the DPROC type: N PICP or none
PRP
DRI (InCell sites)

The Digital Radio Interface (DRI) for a InCell site may only be equipped at a BSS or a BTS site.
The DRI may 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 being added to an existing group (same first identifier), the GSM Cell ID of the new DRI must be
the same as the other DRIs in the group. The equip DRI command is rejected if the Cell IDs are different.
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.

Enter the 1st and 2nd N 1st: 0 to 5, none This identifier indicates a
DRI id: 2nd: 0 to 11 user-defined redundancy 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 to 15 none If the cabinet ID does not exist in
identifier: the database the system rejects
the command.
Enter the DRI board N drim or 0 none
type:
Enter the cage N 0 to 15 none This prompt is presented only if
number: the entered board type is DRIM.
Enter the slot N 7 to 17 none This prompt is presented only if
number: the entered board type is DRIM.
Odd values only.
Enter the TRU Y 0 to 6 0 This prompt is presented only if
identifier: the entered board type is DRIM.
No entry or a zero entered for this
field represents a non-Top Cell
Radio Unit (TRU).
68P02901W23-Q 2-349

Enter the 1st and 2nd Y 0 to 5, none The RTF entered in this field
RTF id: 0 to 11 must be equipped.
The RTF cannot be preferred by
more than one DRI. If the RTF is
already preferred by another DRI,
the system rejects the command.
Enter the GSM cell N GSM cell none The cell number may be in either
ID where the DRI ID or seven parameter format or four
appears: cell_name parameter format.
Enter antenna select N 1 to 6 none
number for this cell:
Enter COMB 1st and Y 0 to 13, none COMB must be separately
2nd id: 0 or 1 equipped.
Enter cavity number: Y 0 to 5 This prompt is displayed only
if COMB ID is entered for the
previous prompt.
Enter the diversity N 0 or 1 none
flag for this DRI:
Does this DRI use Y yes or no yes
tuneable combining:
Enter the tuneable 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 to 13 none Prompted only when DRI uses
identifier: tuneable combining
Enter the cavity N 0 to 5 none Prompted only when DRI uses
number for this COMB: tuneable combining
Enter the fm cell N 0 to 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 Horizonmacro sites)

The Digital Radio Interface (DRI) for an M-Cell or an Horizonmacro site may be
equipped only at a BSS or a BTS site.
The DRI may 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 being added to an existing group (same first identifier), the GSM Cell ID of the new DRI must be
the same as the other DRIs in the group. The equip command is rejected if the Cell IDs are different.
2-350 68P02901W23-Q
Two DRI devices can be associated with each other (double density). Neither DRI has a
higher precedence than the other in the DRI pair.

Enter the 1st and N 0 to 5, none This identifier is used to identify
2nd DRI id: 0 to 11 a user-defined redundancy 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 density N 1 (single) or 2 1 (single) When double density is specified,
of this DRI: (double) the user is not prompted for
tuneable combining.
Enter the 2nd Y 0 to 11 none This parameter specifies the
DRI id of the DRI identifier to be used for the
associated DRI: auto-equipped DRI in a DRI pair.
Enter the cabinet N 0 to 15 none The system rejects attempts
identifier: to equip a DRI in DCS1800
Horizonmacro cabinet if
tx_power_cap= 0
Enter the type of N 0 or fox none This value may be entered as a
connection to the (0 or master for number or its associated character
BTP: Horizonmacro string.
master cabinets) An FMUX can be used only if
1 or fmux0 the BTP resides in an M-Cell6
2 or fmux1 cabinet.
3 or fmux2
4 or direct
Enter the Port to N 0 to 5 none The maximum value is 1 if the
which the TCU is entry to the previous prompt is 4
connected: or “direct."
{24513} If cabinet type is
Horizonmacro II, a check is
made for valid Dual Band DRI
configuration.
Enter the 1st and Y 0 to 5, none The RTF entered in this field
2nd RTF id: 0 to 11 must be equipped.
Enter the GSM cell N GSM Cell ID or none The cell number may be in either
id where the DRI cell_name seven parameter format or four
appears: parameter format.
68P02901W23-Q 2-351

Enter antenna N 1 to 3 none This number configures the
select number for Integrated Antenna Distribution
this cell: Unit (IADU)
If the receive antenna is
connected to DLNB 0 in
the cabinet supporting the
transceiver, set the antenna_select
number to 1.
connected to DLNB 1, set the
antenna_select to 2.
connected to DLNB 2, set the
antenna_select to 3.
If the antenna_select number is
entered incorrectly, the wrong
receive antenna will be connected
to the transceiver.
For the Horizonmacro: This
number configures the 1800
Sectorized Universal Receive
Filter (SURF).
connected to the Rx ANT 0A/0B
in the cabinet supporting the
CTU, set the antenna_select
number to 1.
number to 2
number to 3.
connected to the Rx ANT 900
0A/0B in the cabinet supporting
the CTU, set the antenna_select
number to 2. (Note this is the
default value and will not work
with any other selection.)
Enter COMB 1st and Y 0 to 13, none COMB must be separately
2nd id: 0 or 1 equipped.
Enter cavity Y 0 to 5 This prompt displays only if
number: COMB ID is entered for the
previous prompt.
2-352 68P02901W23-Q

Does this DRI Y yes or no none
use tuneable
combining:
Enter the tuneable Y 0 or 1 none 0 = none
combining type: 1 = non-controlling
2 = controlling
Enter the COMB N 0 to 13 none
identifier:
Enter the cavity N 0 to 5 none
number for this
COMB:
Enter the N 0 or 1 none
diversity flag for
this DRI:
Enter the fm cell N 0 to 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
DYNET
The DYNET is a dynamic network of BTSs that share terrestrial backing resources. The
network may include timeslot switching sites.
All DYNETs that share the same first identifier must have exactly the same BTSs or timeslot
switching sites in the same order. Also, these DYNETs must have different E1/T1 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 may 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.

Enter 1st and N 1st identifier: none If the ID already exists in
2nd unique DYNET 0 to 19, the database, the command is
identifiers: 2nd identifier: rejected.
0 to 2
68P02901W23-Q 2-353
Enter BSC MMS N 0 to 890 or 1 none This prompt requires two

identifier: values:
• The first value is the MSI

at the BSC where the
MMS resides.
• The second value is the

MMS for the BSC network
definition.
Enter SITE N 0 - 100. none The TS site number, timeslot
identifier: ts_switch, switching site, or the BSC
BSC
Enter the upstream N For BTS4, none This prompt requires two
MMS identifiers: BTS5, BTS6, values:
TopCell
and ExCell: • The first value is the MSI
0 to 9, at the BTS where the
0 or 1. MMS resides.
For M-Cell2:
0 to 1, • The second value is the
0 to 1. MMS for the BTS network
For M-Cell6: definition.
0 to 3,
0 to 1.
Enter the Y For BTS4, none This prompt requires two
downstream MMS BTS5, BTS6, values:
identifiers: TopCell
and ExCell: • The first value is the MSI
0 to 9, at the BTS where the
0 or 1. MMS resides.
For M-Cell2:
0 to 1, • The second value is the
0 to 1. MMS for the BTS network
For M-Cell6: definition.
0 to 3, This prompt can be left blank.
0 to 1.
EAS (InCell sites)

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

Enter the first device N 0 to 7 none If the ID already exists in
ID for the EAS: the database the command is
rejected.
Enter the cage where the N 0 to 15 none
PIX is connected:
Enter the daughter N 15 to 18 none
slot where the PIX is
located:
2-354 68P02901W23-Q

Enter the initial N 0 or 1 none Enter four values, each separated
setting of the 4 relays: by a space.
Enter the no alarm N 0 or 1 none Enter eight values, each separated
condition for the 8 by a space.
optos (0 - closed, 1 -
open):
Enter each opto whose N 1 to 8 none Enter eight values, each separated
state changes are to be by a space.
reported:
Enter the user defined N 0 to 33 none Enter eight values, each separated
alarm index for the 8 by a space.
optos: Enter the string “mpf" in place
of one of the integers to indicate
which opto is used for the EAS
Mail Power Failure alarm.
Enter each opto whose Y 1 to 8 none Operator may enter up to 8
state changes are to be for InCell values for an InCell site and up
reported: sites. to 16 values for an M-Cell site;
1 to separate values with either a
16 for space or a comma.
M-Cell If no value is entered in the range
sites. prompt, then no state changes
are reported for any optocoupler.
The values may be entered in any
order.
The operator also has the option
of entering “all" and of entering
a range of optos.
Enter the user defined Y 0 to 33 none The operator must enter one
alarm index for opto n: and 128 value indicating the index of the
user defined alarm string for the
optocoupler 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 optocoupler
specified in the previous prompt.
EAS (M-Cell sites)

The External Alarm System (EAS) for M-Cell sites may 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.
68P02901W23-Q 2-355
All relays are deactivated during site initialization. Once the EAS is Busy-Unlocked, the relay
state can be controlled by use of the set_relay_contact command.

Enter the first device N 0 to 15 none Cabinet identifier.
ID (Cabinet ID) for the
EAS:
Enter the initial N 0 or 1 none 0 = deactivate the relay
setting of the 4 relays: 1 = activate the relay
Enter four values, each separated
by a space.
Enter the no alarm N 0 or 1 none Enter 16 values, each separated
condition for the 16 by a space.
optos (0 - closed, 1 -
open):
Enter each opto whose N 1 to 16 none Enter 16 values, each separated
state changes are to be by a space.
reported:
Enter the user defined N 0 to 33 none Enter 16 values, each separated
alarm index for the 16 by a space.
optos: Enter the string “mpf" in place
of one of the integers to indicate
which opto is used for the EAS
Mail Power Failure alarm.
GBL
The Gb Link (GBL) is the communication link between the PCU cabinet and the SGSN.
The GBL can be equipped only if the GPRS feature is unrestricted. This device may be equipped
with the system in either SYSGEN ON or SYSGEN OFF mode.
To support EGPRS the GBL bandwidth between the PCU and the SGSN has been increased. The amount of
bandwidth necessary for a maximally configured PCU is 12 E1s of GBL and for a maximally configured BSS is
20 E1s. This maximum number of GBLs can be configured independent of whether EGPRS is restricted or not.

Enter the GBL N 0 to 11 none Unique identifier of the GBL.
identifier:
Enter the 1st and 2nd N 0 to 23, none A GBL must be equipped on a
MMS identifier: 0 to 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 to 31 none Element name start_ts. First
timeslot: GBL timeslot on the span.
Enter the ending N 1 to 31 none Element name end_ts. Last GBL
timeslot: timeslot on the span.
2-356 68P02901W23-Q

Enter the t391 timer: Y 5 to 29 10 Element name t391. Value of
the Frame Relay default Link
Integrity Verification Polling
Timer in seconds.
Enter the t392 timer: Y 6 to 30 15 Element name t392. Value of
the Frame Relay default Polling
Verification Timer in seconds.
Enter the n391 counter: Y 1 to 255 6 Element name n391. Frame
Relay default Full Status Polling
Counter, as number of polling
cycles.
Relay default value for Error
Threshold Counter, as number
of errors.
Relay default value for
Monitored Events Counter,
as number of events.
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.
GCLK
The Generic Clock (GCLK) may be equipped with the system in either the SYSGEN
The GCLK may not be explicitly equipped at M-Cell sites. This device is automatically
equipped when a BTP is equipped.
Some devices do not require all of the prompts. Therefore, the system may not
always display all of the prompts below.

Enter the device N 0 or 1 none The GCLK slot is assigned based
identification for the on the device ID:
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 number: N 0 to 15 none
Is CLKX 0 (slot U7) Y yes or no no The slot number displayed in the
present? prompt depends on the GCLK ID.
68P02901W23-Q 2-357

GDS
The GPRS Data Stream (GDS) can be equipped only if the GPRS feature is unrestricted.
This device may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode.
A GDS must not be unequipped until all GSLs on that GDS have been unequipped.
The BSS rejects an attempt to equip a GDS to a MMS at the BSC where the mms_pri-
ority 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 and
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.
Prompt Optional Range Default Notes

Enter the GDS N 0 to 37 none Unique identifer of the GDS
identifier:
Enter the BSC MMS N 0 to 55, none
identifier: 0 to 1.
Enter the PCU MMS N 0 to 23, none
identifier: 0 to 1.
Enter the GDS type: N 0 to 1, none
TRAU-
LAPD
BSC MMSs which are equipped to GDS devices cannot be selected as clock sources.
2-358 68P02901W23-Q
GPROC
The Generic Processor (GPROC) may be equipped with the system in either the
This device may not be equipped at M-Cell sites.

Enter the GPROC N 1 to 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 dependent
number: Comments on the site:
BSC, BSS and BTS sites: slots
18 to 25
RXCDR sites: slots 25 to 26
GSL
The GPRS Signalling Link (GSL) can be equipped only if the GPRS feature is unrestricted. The GSL
may 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.
To bring the GSL in service, unlock the GSL at either the OMC-R or MMI prompt.
The equip GSL command fails if the total max_gsls for all LCFs becomes less
than the total number of equipped GSLs.
Prompt Optional Range Default Notes

Enter the GSL N 0 to 29 none
identifier:
Enter the unique GDS N 0 to 19 none
identifier:
68P02901W23-Q 2-359
KSW
The Kiloport Switch (KSW) may be equipped with the system in either the SYSGEN
The KSW may not be equipped at M-Cell sites.
Enter Portion of N 0 to 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 identifier N 0 or 1 none The KSW slot is assigned based
(identifier 2): on the second device ID;
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 number: N 0 to 15 none
Are DRIs allowed on N Y or N none
highway managed by this
KSW:
LMTL
The LMTL device applies only to the BSC (location 0).
The Location Services feature must be unrestricted.
For LMTLs to be equipped, the BSC must be configured to support a BSS-based SMLC.

Enter the device N 0 to 15 none Location Services must be
identification for this unrestricted.
LMTL:
Enter the first MMS N 0 or 55 none
identifier for this
device:
Enter the second MMS N 0 to 1 none
identifier for this
device:
Enter the timeslot on N 31 (E1) none
MMS where this device 24 (T1)
appears:
2-360 68P02901W23-Q
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.
MSI (InCell sites)

The Multiport Serial Interface (MSI) for sites that are InCell sites may be equipped with the
system in either the SYSGEN ON or SYSGEN OFF mode.
A MSI with msi_type of msi_ext_hdsl may not be equipped with the protocol types of both
MMSs entered as E1 at a BSC or an InCell BTS site.

Enter the device N BSC: 0 to 55. none
identification for RXCDR:
the MSI: 0 to 123.
BTS: 0 to
9 (InCell).
Enter the cage number: N 0 to 15 none Prompt appears only if the
Integrated MCell HDSL feature
is enabled, and the msi_type
is niu_hdsl, niu_ext_hdsl, or
msi_ext_hdsl.
MSI types xcdr or gdp are
only allowed at sites where
transcoding occurs.
Enter the slot number: N BSS & none Valid slot numbers are based on
BSC sites: site type and MSI type
All MSI
types slots
6 to17.
BTS sites:
MSI type 0
slot 6 to17,
MSI type
1 or 2 not
allowed.
RXCDR
sites
MSI type 0
slots 6 to10,
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_ext_hdsl,
12 or
RF_unit,
20 or gdp2.
68P02901W23-Q 2-361

Enter MMS0 protocol Y E1 or HDSL HDSL Prompt appears only if the
type: Integrated MCell HDSL feature
is enabled, and the msi_type
msi_ext_hdsl.
Enter the number of Y 16 or 32 32 Prompt appears only if the
timeslots supported on Integrated MCell HDSL feature
MMS0: is enabled, and the MSI type
msi_ext_hdsl, and the protocol
type is HDSL
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
msi_ext_hdsl.
Enter the number of Y 16 or 32 32 Prompt appears only if the
timeslots supported on Integrated MCell HDSL feature
MMS1: 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.
Y BSC: 0 to 55. Value of MSI identifier of GDP with
Enter the MSI ID to RXCDR: 0 GDPs MMS available for routing
the MSC: to 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 of MSC MMS always zero because
GDPs MSIs cannot provide MSC
own 2nd MMSs. Read-Write (can only
ID be set when the MSI device is
created).
Prompt appears only if MSI type
entered as 2 or gdp
Enter the transcoding N 0 or Basic, none Prompt appears only if MSI type
capability: 1 or entered as 2 or gdp, or as 20 or
Enhanced, gdp2.
2 or
GDP_2E1.
2-362 68P02901W23-Q
The default values in the table above apply only if nothing is entered at the prompts.
MSI (M-Cell sites)

The Multiport Serial Interface (MSI) for M-Cell sites may be equipped with the system in
either the SYSGEN ON or SYSGEN OFF mode.
M-Cell sites do not use MSI boards. The MSI function is performed by the Network Interface Unit (NIU)
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 will be issued if the protocol types of both MMSs of a 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 may not 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 may 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_restore_mon_period durations will default to known software values.
The default values in the following table apply only if nothing is entered at the prompts.

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

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 Only appears if the Integrated
protocol type: MCell HDSL feature is
enabled, and the msi_type is
niu_hdsl or niu_ext_hdsl.
Enter the number of Y 16 or 32 32 Only appears if the Integrated
timeslots supported on MCell HDSL feature is
MMS0: enabled, and the msi_type is
niu_hdsl or niu_ext_hdsl, with
a protocol type of HDSL for
this MMS.
Enter MMS0 modem Y master or master Only appears if the Integrated
setting: slave MCell HDSL feature is
niu_hdsl with a protocol type
of HDSL for this MMS.
Enter the MMS1 Y E1 or HDSL HDSL Only appears if the Integrated
protocol type: MCell HDSL feature is
niu_hdsl, or niu_ext_hdsl.
Enter the number of Y 16 or 32 32 Only appears if the Integrated
timeslots supported on MCell HDSL feature is
MMS1: enabled, and the msi_type is
niu_hdsl or niu_ext_hdsl with
a protocol type of HDSL for
this MMS.
Enter MMS1 modem Y master or slave Only appears if the Integrated
setting: slave MCell HDSL feature is
niu_hdsl with a protocol type
of HDSL for this MMS.
MSI (PCU only)

The Multiport Serial Interface (MSI) may be equipped with the system in SYSGEN ON mode.
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.
This device may also be equipped when the system is outside the SYSGEN ON mode. The site does
not have to be locked when this device is equipped outside SYSGEN ON mode.
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.
2-364 68P02901W23-Q
The BSS supports equipage of a GDS at the PCU.

The BSS supports equipage of a GDS to a 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 a MSI.
The BSS supports equipage of up to two MSIs per DPROC board.
A DPROC board must be equipped before a MSI may 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.
An MSI must be equipped in PMC socket 1 of a DPROC in either slot 1 or slot 2.

Enter the MSI N 0 to 23 none The MSI identifier.
identifier:
Enter the DPROC id: N 1 or 6 none The identifier of the DPROC in
11 to 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 socket: N 1 or 2 none PMC module identifier on the
DPROC board to which the MSI
is being equipped.
MTL
The Message Transfer Links (MTL) is not allowed at a RXCDR site and may be equipped only at site 0.
The MTL cannot be equipped on an HDSL link.
The MTL can equipped only at the BSC.

Enter the device identification for this N 0 to 15 none
MTL:
Enter the first MMS description for this N 0 to 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 to 31 (E1) none
appears: 1 to 24 (T1)
If an MMS has another timeslot that conflicts when equip-

ping an MTL, the system generates the following warning:
68P02901W23-Q 2-365
COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display times-

lot usage to verify.
Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another
connected to a different type of device (that is, RXCDR, OML, and so on).
OML
The Operations and Maintenance Link (OML) cannot be equipped on an HDSL link.
The OML may be equipped only at site 0.

Enter the device id for the OML: N 0 to 3 none
Enter the first MMS description for this N BSC: 0 to 55 none
device: RXCDR:
0 to 123
Enter the second MMS description for this N 0 or 1 none
device:
Enter timeslot on MMS where this device N E1: 1 to 31 none
appears: T1: 1 to 24
If an MMS has another timeslot that conflict when equipping an OML, the system
generates the following warning:
PATH
Prompts to equip a path are presented for each link in the path.
The PATH may be equipped when the system is in either the SYSGEN ON or SYSGEN OFF mode.
The system rejects the equip path command if one of the MSIs is msi_type RF_Unit.
A path for an HDSL link must have 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.

Enter terminating N 1 to 120 none
SITE id:
Enter the Unique N See Comments none The availability of a PATH
PATH identifier: identifier depends on whether
or not the terminating site uses
dynamic allocation:
- no dynamic allocation: 0 to
9
- dynamic allocation: 6 to 9
2-366 68P02901W23-Q

Enter the BSC MMS N 0 to 55 (MSI), none Type two values, separated by
identifier: 0 or 1 (MMS). a space; the first value is the
MSI ID; the second value is
the MMS ID.
Enter SITE N 1 to 120, or none If the Aggregate Abis feature
identifier: ts_switch is enabled the system accepts
(see Comments) ts_switch as the site ID.
If ts_switch is used, the
system will not prompt for
upstream MSI, upstream
MMS, downstream MSI and
downstream MMS identifiers.
Enter the upstream N BSC: 0 to 55, none The upstream MMS identifier
MMS identifier: BTS: may not correspond to an
0 to 9 (In-Cell), RF_Unit MSI.
0 to 3 (M-Cell6), MMS id 2 is 0 to 1.
0 to 1 (M-Cell2).
The following sequence of prompts repeats until the specified site identifier matches the
terminating site (maximum of nine sequences):

Enter the N BSC: 0 to 55, none
downstream MMS BTS:
identifier: 0 to 9 (InCell),
0 to 3 (M-Cell6),
0 to 1 (M-Cell2).
Enter the SITE N 1 to 120, or none If the Aggregate Abis feature
identifier: ts_switch is enabled the system accepts
(see Comments) 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 to 55, none The range for the MMS id 2
MMS identifier: BTS: is 0 to 1.
0 to 9 (InCell),
0 to 3 (M-Cell6),
0 to 1 (M-Cell2).
If an MMS has another timeslot that conflicts when equipping

a PATH, the system generates the following warning:

Conflicting usage is when at least one timeslot provides connectivity to a BTS and
another type of device (such as, an RXCDR).
68P02901W23-Q 2-367
The upstream MMS ID may not correspond to an RF_Unit MSI.
PCU
Up to three Packet Control Units (PCUs) can be equipped at a BSS to provide the
functionality for the GPRS feature.
A PCU may be equipped with the system in SYSGEN ON mode.
When a PCU is equipped, a corresponding cabinet and cage are automatically equipped.
A PCU may also be equipped when the system is in the SYSGEN OFF mode and it is to be the standby device.
A PCU can be equipped only if parameter land_layer1_mode is set to E1.
Any PCU prompt for which a response is not made will use the default value. The system Configuration
Management (CM) software will allocate default IP addresses to the PCUs as follows:
PCU_0 1509949442 (90.0.0.2)
PCU_1 1509949442 (90.0.0.2)
PCU_2 1509949442 (90.0.0.2)

Enter the PCU Y 0-2 0 Up to three PCUs per BSC
identifier:
Enter the PCU IP Y 90.0.0.2
address:
Enter the PCU subnet Y 255.255.255.0
mask:
Enter the PCU router IP Y 90.0.0.1
address:
Enter the NSEI value: N 0 - 65535 none
Example
Equip PCU site 1 at the BSC:
equip 0 PCU
Enter the PCU identifier (default 0): 1

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
2-368 68P02901W23-Q
The COMMAND ACCEPTED message wiil be replaced by an error message if a PCU with the same
id already exists at the BSC, or the IP address entered is already assigned to another PCU.
PSP
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 does not have to 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 user is not prompted.
RSL
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.

Enter the 1st device ID N 1 to 120 none
for the RSL:
Enter the 2nd device ID N 0 to 7 none The range depends on the
for the RSL: See Comments site type:
InCell: 0 to 7.
M-Cell 2/6 BTS: 0 to 5.
Enter the Unique PATH N 0 to 9 none
id:
Enter LAPD T200 Timer Y 1400 to 5000 2500 Values must be in multiples
value: of 50.
Enter LAPD N200 value: Y 1 to 5 3
Enter LAPD K value: Y 1 to 10 7
The equip RSL command automatically equips an additional 16K RSL when a 16K
RSL is equipped to an auto-equipped PATH that is part of a closed loop DYNET.
The equip command will not allow an RSL to be equipped to a PATH that is not
automatically created at a site that supports dynamic allocation.
RXCDR
The Remote Transcoder (RXCDR) must be the first device equipped by the operator in
the SYSGEN ON mode at a RXCDR site.
68P02901W23-Q 2-369
If a RXCDR device is equipped at a BSS site, it is actually an Associate RXCDR device.

Enter the RXCDR id: N 1 to 128 none
SITE
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).

Enter the device N 0 to 120 none 0 is the only valid value for a
identifier for the RXCDR site type.
site:
Enter the type of BSP N BSP or none This prompt only appears
or LCF: LCF if equipping a Remote BTS
(RBTS).
Enter the function N 0 or 1 none This prompt only appears
identifier for the LCF: (BSP) if equipping a Remote BTS
0 to 24 (RBTS).
(LCF)
Enter the RSL type: N 16 or 64 none The system displays this prompt
only if the site is remote and the
16K RSL option is enabled.
Does the site use N Y or N none This prompt only appears if:the
dynamic allocation Dynamic Allocation feature
of terrestrial backing is unrestricted;the site being
resources?:
equipped is a BTS.
XBL
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.

Enter the ABSS device N 1 to 128 none This prompt is displayed only at
id for the XBL: an RXCDR site.
This value is valid for XBLs
equipped at an RXCDR.
This value specifies the ABSS
device with which this XBL will
be communicating.
Enter the AXCDR device N 1 to 128 none This prompt is only displayed at
id for the XBL: a BSC site.
This value is valid for XBLs
equipped at a BSS..
This value specifies the RXCDR
device with which the XBL will
be communicating.
2-370 68P02901W23-Q

Enter the device ID for N 0 to 9 none XBLs may not be equipped at
the XBL: BTS sites or at BSC transcoding
sites.
Enter the second device N 0 to 9 none The is the value for the XBL
id for the XBL: device.
Enter the data rate for Y 16 or 64 Prompted only if the 16kbit/s
the XBL (16/64kbps): option is unrestricted.
Enter the first MMS N BSC: none This prompt appears only if the
description for this 0 to 55 XBL data rate is set to 16.
device: RXCDR:
0 to 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 to 31
appears: T1:
1 to 24
Enter the group of the Y 0 to 3 Prompted only if the 16kbit/s
timeslot where this option is unrestricted and the
device appears: XBL data rate is set to 16kbit/s.
Enter LAPD T200 time Y 1400 to 2500 Values must be in multiples of
value for the device: 5000 50.
Enter LAPD N200 value: Y 1 to 5 3
Enter LAPD K value: Y 1 to 127 7
If an MMS has another timeslot that conflict when equip-

ping an XBL, the system generates the following warning:

Equipping functions
This section provides conditional information for the rules on equipping the various functions, and
lists the equip command prompts that occur with each function.
LCF
The Link Control Function (LCF) may 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.
68P02901W23-Q 2-371
The sum of all GSLs (GPRS) specified by the equipped LCFs must be greater than or
equal to the total number of equipped GSLs.

Enter the function N 0 to 24 none
indentifier for the
LCF:
Enter the number of MTLs N 0 to 2 none
the LCF can manage:
Enter the number of N 0 to 2 none
LMTLs the LCF can
manage:
Enter the number of CBLs N 0 or 1 none
the LCF can manage:
Enter the number of GSLs N 0 to 6 none Prompted only when the GPRS
the LCF can manage: feature is unrestricted.
An LCF cannot simultaneously manage both MTLs and LMTLs.
OMF
No parameter prompts are displayed when equipping the Operations and Maintenance Facility (OMF).
OMFs may only be equipped at BSC or BSS site types where the BSC type is set to 2.
This function may be equipped with the system in SYSGEN ON mode or outside the SYSGEN ON mode.
The site does not have to be locked when this function is equipped outside SYSGEN ON mode.
RTF
The Radio Transceiver Function (RTF) may be equipped with the system in either
When equipping the RTF, the system enforces the following dependencies:
• An RTF cannot be equipped in SYSGEN OFF mode if:
All of the RTF timeslots 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 timeslots 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 that another RTF uses the other FHI.
• An RTF may not be equipped to a site using dynamic allocation if the site is not in a DYNET.
2-372 68P02901W23-Q
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). The channel numbers at the block edges are:
512 610 687 735
585 612 710 737
587 685 712 810
This does 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 valid range for the ARFCN of an RTF configured
for the inner zone is defined by frequency type of the secondary band.
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 may 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 timeslots. For a complete description of this parameter, refer to Chapter 5.
The following warning message displays if a frequency is specified that is already in use at the site:
COMMAND ACCEPTED: WARNING: Specified ARFCN already 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 already exists in this cell.
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.
68P02901W23-Q 2-373
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.
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 should be BUSY_UNLOCKED.
The following error messages will occur when attempting to equip a RTF for EGPRS:
• When a site has no Horizonmacro or Horizon II macrofamily of cabinets equipped.
COMMAND REJECTED: Horizonmacro or Horizon II macro family of cab-

inets required for EGPRS.
• Either with 32 kbit/s packet radio capabilities when the Coding Scheme 3&4 feature is
restricted, or 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 sub-equipped:
COMMAND REJECTED: 32kbps/64kbps TRAU rate is not allowed for sub-equipped RTFs
• With an associated RSL:
COMMAND REJECTED: Multiplexed RSL is not allowed with 64K RTFs
• At a site that supports dynamic allocation:

COMMAND REJECTED: 32kbps/64kbps TRAU rate is not allowed at sites
using dynamic allocation.
• If a non-zero value of extended range timeslots is en-

tered for an RTF with 64 kbit/s packet radio capabilities:
COMMAND REJECTED: Extended range timeslots are not allowed for EGPRS carriers.
• With a valid FHI, outside of Sysgen mode, if the RTF is at a site whose master cabinet is not
a Horizon II macro and the hopping system is set to baseband hopping:
COMMAND REJECTED: Master cabinet must be Horizonmacro2 for EGPRS

RTFs to hop in baseband hoppping.
2-374 68P02901W23-Q
• 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.

Enter capacity of N FULL or This prompt will not display
carrier: SUB - if the RTF is equipped to a
BTS using dynamic allocation;
- if the sub-equipped RTF
feature is not available.
Enter type of carrier: N bcch or none
non_bcch
Enter the 1st and 2nd N Valid first none
RTF id:Enter the 1st RTF IDs:
and 2nd RTF id: 0 to 5
Valid second
RTF IDs:
0 to 11
0 to 1 for
M-Cell
Enter the primary N 0 to 9 none This prompt is only provided
Unique PATH id: for RTFs at remote BTS sites.
If the BTS type is 16k RSL,
the system displays the
next prompt. Otherwise,
proceed with the Enter
the optional secondary
Unique Path id prompt.
This prompt will not display if
the RTF is equipped to a BTS
Enter the 2nd N Micro: 0 to 1 none This prompt does not display if
identifier for the MCell: 0 to 5 the RTF is equipped to a BTS
associated RSL: InCell: 0 to 7 using dynamic allocation.
Enter the optional Y 0 to 9 none This prompt is provided for
secondary Unique Path only RTFs at remote BTS sites.
id: This prompt does not display if
the RTF is equipped to a BTS
Enter the optional Y Micro: 0 to 1 none This prompt does not display if
2nd identifier for the MCell: 0 to 5 the RTF is equipped to a BTS
associated RSL: InCell: 0 to 7 using dynamic allocation.
Enter the GSM cell to N GSM Cell ID none The cell number may be in
which this carrier is or cell_name either seven parameter format
assigned: or four parameter format.
68P02901W23-Q 2-375

Enter carrier absolute N See none The first channel from which to
radio freq. channel: Comments. 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.PGSMBCCH (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
Enter the 8 carrier N 0 to 3 and 255 255 The 8 frequency hopping
frequency hopping indicators are entered on a
indicators: single line with one space
separating each value. The
input for this value must
include all 8 values or no
values.
A value of 255 means no
hopping.
A value of 255 is required for
all M-Cellcity sites.
Enter the 8 carrier N 0 to 7 none The 8 carrier training sequence
training sequence codes are entered on a single
codes: line with one space separating
each value.
Enter KSW pair that N 0 to 3 none This prompt does not appear
manages this carrier: when equipping the RTF to an
M-Cell site.
Enter cell zone: 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.
Enter TRX transmit Y same value as Only prompted when
power reduction: max_tx_bts Concentric Cells feature is
enabled. Only prompted for
inner zone carriers.
2-376 68P02901W23-Q

Enter the number Y 0 to 4 Only prompted for outer zone
of extended range carriers. Only prompted when
timeslots allowed: the Extended Range Cell
feature is unrestricted.
Enter SDCCH load Y 0 to 2 The system displays this
prompt for outer zone carriers
(cell_zone = 0) only.
Enter SDCCH placement Y 0 to 250 The system displays this prompt
priority: if:
for outer zone carriers
(cell_zone = 0) only, and
sdcch_load is not set to 0 ( 0).
Enter channel Y 0 to 250
allocation priority:
Enter the packet radio N 0 to 3, or 0 (none) This prompt only occurs if the
capability: none, 16k, GPRS feature is unrestricted
32k, 64k and if it is an outer zone carrier.
For a complete description of
this parameter, refer to Chapter
5.
{22064} 0 or 1 0 This prompt only occurs
Enter the value for at Half Rate capable BTSs
Half Rate enabled: such as M-Cell2, M-Cell6,
Horizonmacro and Horizon II
macro, {22064} if AMR and/or
GSM HR are/is unrestricted.
Is 8kbps TRAU allowed Y Y or N Y This prompt only occurs
(yes/no): at Half Rate capable BTSs
such as M-Cell2, M-Cell6,
Horizonmacro and Horizon
II macro {22064} when
half_rate_enabled is set to 1.
68P02901W23-Q 2-377
freq_types_allowed Chapter 2: Device/function related commands
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 1 (for displaying the frequency types allowed)

2 (for modifying the frequency types)
Prerequisites None
Dependencies The frequency types of extended neighbour 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
being 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.
2-378 68P02901W23-Q
Technical Description: BSS Command Reference freq_types_allowed
Format
Syntax
freq_types_allowed [<types>]
Input parameter
types
Specifies the frequency types available to the BSS . The value may be 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.
Prompted parameters
The prompt for PCS 1900 frequency blocks appear only if “all" , “pcs1900" or the number 8 is specified
in the command line. At least one frequency block must be entered if the prompt appears.
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
68P02901W23-Q 2-379
freq_types_allowed Chapter 2: Device/function related commands
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
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 (see
typestable).
System response:
Enter PCS 1900 frequency blocks: a,c,d,f
COMMAND ACCEPTED
2-380 68P02901W23-Q
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
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
Example
In this example, the GCLK calibration at the local site is started:

gclk_cal_mode
System response
Site <local site number> starting GCLK CALIBRATION MODE. If this a
single MCU site, the site will be down until calibration is complete.
If this is a two MCU site, the site will be down until the redundant
MCU takes over.
Are you sure (y=yes,n=no)?
68P02901W23-Q 2-381
ins_device Chapter 2: Device/function related commands
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 BSP BTP CAB
CBL CIC COMB CSFP DHP
DRI EAS GCLK GPROC KSW
MMS MSI MTL OML PATH
PCHN RSL SITE XBL
The ins_device command supports extension cabinets only 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.
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:
DPROC GBL GSL PCU PSP
If the ins_device command is applied to an active PSP, the command is rejected. Only a
standby PSP can be brought into service using this command.
The following device may be brought into service at a PCU using this command:
MSI
A hard reset executes when this command is entered for the following devices:
BSP BTP DHP GPROC
Security level 2
2-382 68P02901W23-Q
Technical Description: BSS Command Reference ins_device

This command may be entered 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> <de-
vice_id2> <device_id3>
Input parameters
location
0 or bsc BSC
1 to 120 BTS
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.
CIC syntax
A form of syntax is available for each method of specifying a CIC.
The following CIC syntax apply 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>
68P02901W23-Q 2-383
The following CIC syntax apply to remote transcoding:
For remote transcoding BSC sites, the ins_device command may not be used for CICs devices
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
0 or bsc BSC
1 to 120 BTS
CIC
cic_num1
cic_num2
mms_id1
mms_id2
timeslot1
First timeslot.
timeslot2
group1
First group.
2-384 68P02901W23-Q
Technical Description: BSS Command Reference ins_device
group2
Second group.
*
Example 1
This example brings a 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
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 device_name
2 First MMS ID
1 Second MMS ID
3 Timeslot 3
1 Group 1
5 Timeslot 5
1 Group 1
68P02901W23-Q 2-385
System response
COMMAND ACCEPTED
Example 3
This example brings the PICP MSI (GPRS) into service at the third equipped PCU:
ins_device pcu_2 msi 1 0
Where: is:
pcu_2 location (third equipped PCU)
msi device_name
1 First MSI ID
0 Second MSI ID
System response
COMMAND ACCEPTED
References
Related commands
"lock_device" on page 2-387, "reset_device" on page 2-420, "unlock_device" on page 2-504.
2-386 68P02901W23-Q
Technical Description: BSS Command Reference lock_device
lock_device
Description
The lock_device command locks a specified device.

Security level 2
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> <de-
vice_id2> [<device_id3>]
Input parameters
location
0 or bsc BSC
1 to 120 BTS
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 as a location.
device_name
The following devices can be locked using this command:
ABSS AXCDR BSP BTP CAB CBL CIC COMB
CSFP DHP DRI DPROC EAS GBL GCLK GDS
GPROC GSL KSW MMS MSI MTL OML PATH
PCHN PCU RSL SITE XBL
68P02901W23-Q 2-387
lock_device Chapter 2: Device/function related commands
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 will not lock any OMLs or MTLs that are carried on its associated 2
Mbit/s link. Any traffic circuits carried on this 2 Mbit/s link will be blocked, however. 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 will cause 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 will 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 will go OOS; the XBL on the second link will block the circuits.
If the lock_device command is applied to an active GCLK, and the standby GCLK is phase
locking, 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 may not be locked on a per-MMS basis when the
BSC is operating in the dynamic allocation mode.
The lock_device command supports the locking of extension cabinets only of type TCU_2,
TCU_6, and HORIZONMACRO_EXT. DRIs and EASs equipped to the cabinet are
disabled. No other cabinet types are supported.
A hard reset executes 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.
CIC syntax
2-388 68P02901W23-Q
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>
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>
Input parameters
location
0 or bsc BSC
1 to 120 BTS
CIC
cic_num1
cic_num2
mms_id1
mms_id2
timeslot1
First timeslot.
timeslot2
group1
First group.
group2
Second group.
68P02901W23-Q 2-389
lock_device Chapter 2: Device/function related commands
*
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
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 First MMS ID
1 Second MMS ID
3 Timeslot 3
1 Group 1
5 Timeslot 5
1 Group 1
System response
COMMAND ACCEPTED
2-390 68P02901W23-Q
Example 3
This example locks the first PCU as a device at BSC 0:
lock_device 0 pcu 0
System response
WARNING: This command may cause GPRS service to be lost in cells
which are served by links connected to this device.
Are you sure (y=yes, n=no)? y
COMMAND ACCEPTED
Example 4
This example locks MSI 2 at the first PCU as a location:
lock_device pcu_0 msi 2
System response
WARNING: This command may cause GPRS service to be lost in cells
which are served by links connected to this device.
COMMAND ACCEPTED
References
Related commands
"disp_equipment" on page 2-235, "equip" on page 2-329, "reset_device" on page 2-420, "shutdown_device"
on page 2-436, "state" on page 2-448, "unequip" on page 2-494, "unlock_device" on page 2-504.
68P02901W23-Q 2-391
mod_conn Chapter 2: Device/function related commands
mod_conn
Description
The mod_conn command modifies MMS connectivity between the RXCDR and the BSS.
This command allows the operator to change the E1/T1 connectivity information identifying which RXCDR
is associated with the E1/T1 link and the device identity within the RXCDR to which the E1/T1 link is
connected. This connectivity information must be specified for each E1/T1 link connecting to an RXCDR.
Security level 2
Prerequisites The AXCDR or ABSS device specified in the command must be
equipped in the BSS database.
No XBL devices may 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 may be
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.
network_entity_id
The AXCDR or ABSS device identifier that represents the actual RXCDR or BSS
with which this MMS is communicating.
2-392 68P02901W23-Q
Technical Description: BSS Command Reference mod_conn
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 RXCDR. The ranges for several
input parameters depends on where the command is executed, as shown in Table 2-29.
Table 2-29 mod_conn valid ranges
Execution location
Inputparameter
BSC RXCDR
local_mms_id_1 0 to 55 0 to 123
local_mms_id_2 0 or 1 0 or 1
network_entity_id 1 to 254 1 to 128
remote_mms_id_1 0 to 123 0 to 55
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-Q 2-393
mod_conn Chapter 2: Device/function related commands
References
Related commands
"add_conn" on page 2-33, "del_conn" on page 2-172, "disp_conn" on page 2-224
2-394 68P02901W23-Q
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.
Security level 2
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_0, pcu_1 or pcu_2.
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.
The third specifies the frame relay burst excess ns_burst_excess (0 to 1984). There is no default.
68P02901W23-Q 2-395
mod_nsvc Chapter 2: Device/function related commands
ns_burst_size and ns_burst_excess must not both be 0.If either ns_commit_info_rate

or ns_burst_size is 0, both must be 0.
Example
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
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.

COMMAND ACCEPTED
References
Related commands
"del_nsvc" on page 2-178, "add_nsvc" on page 2-43.
2-396 68P02901W23-Q
Technical Description: BSS Command Reference modify_neighbor
modify_neighbor
Description
The modify_neighbor command modifies the value of a neighbour cell parameter. The
neighbor_cell_id may be a test cell neighbour.
The changing of the ba_bcch parameter is only allowed for test neighbours which are on the
BA_SACCH list of the cell. To add a neighbour to the BA_BCCH list without adding to the
BA_SACCH list, use the add_neighbor command. To remove a neighbour 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 neighbour is auto-equipped with its BCCH frequency set to the BCCH
frequency of the serving cell. This neighbour cell may not be modified by the modify_neighbor command.
If the Inter-RAT handover feature is unrestricted, handovers can be to UMTS UTRAN cells.
Security level 2
Prerequisites The changing of the synchronized parameter is only allowed for
neighbours at the site of the source cell.
If the neighbour is a UMTS UTRAN cell, the Inter-RAT handover
Format
Syntax
modify_neighbor <source_cell_id> <neighbor_cell_id> <parameter> <value>
Input parameters
source_cell_id
Cell identity of the source cell.
68P02901W23-Q 2-397
modify_neighbor Chapter 2: Device/function related commands

• The system used (PGSM, EGSM, DCS1800, PCS1900 or GSM850)
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.
neighbor_cell_id
Cell identity of the neighbour cell whose parameter value is being changed.
• The system used (PGSM, EGSM, DCS1800, PCS1900 or GSM850)
For an internal neighbour cell only, the cell_id can also be a cell name created using the cell_name
command. A cell_name may not be used to specify an external neighbour cell. When the cell
name is entered, it must be placed inside double quotation marks.
parameter
Neighbour cell parameter to be changed:
Parameter Action
adap_trig- Specifies the cumulative area for the adaptive handover power budget
ger_pbgt_nbr algorithm; valid only for SACCH and SACCH/BCCH neighbours
adj_chan_intf_test Turns adjacent channel interference on or off
ba_bcch Adds or deletes a neighbour cell from the BA_BCCH list.
ba_gprs Adds or deletes a neighbour cell from the BA_GPRS list.
congest_ho_margin Determines the hand over margin to be used in the event of congestion.
This value may only be changed when either the Directed Retry or alternate
congestion relief feature is enabled. This attribute is only valid for SACCH
neighbours.
If the directed retry feature is not enabled, the value defaults to the value of
the ho_margin_cell of the neighbour.
The system does not prompt for the congest_ho_margin value if the
Directed Retry option was not purchased.
dr_allowed Allows a directed retry to an external neighbour during the assignment
procedure. An external handover may only be initiated if either the
dr_standard_congest or dr_ho_during_assign parameter is enabled.
This attribute is only valid for SACCH neighbours.
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 neighbour cell.
2-398 68P02901W23-Q
Parameter Action
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 neighbour 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 neighbour 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
neighbour.
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.
Hitting 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 neighbour cell.
neighboring_range Changes which range the neighbour 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 neighbour cell.
synchronized Allows synchronized handovers for neighbour cells.
fdd_arfcn Indicates the frequency of a UMTS UTRAN cell.
scr_code Indicates the primary scrambling code of a UMTS UTRAN cell.
diversity_enabled Indicates whether diversity is applied in a UMTS UTRAN cell.
68P02901W23-Q 2-399
value
The new value of the selected neighbour 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 a 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)
neighboring_range normal (neighbour is a normal range cell)
extended (neighbour 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
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.
2-400 68P02901W23-Q
Examples
Example 1
This example adds the frequency of neighbour cell 5 4 3 2 1 4344 9755 to the BA_BCCH list of
src 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 parameter to be modified
add parameter value
The example below shows the same cell numbers in four parameter format:
modify_neighbor ba_bcch 543 21 676 8645 543 21 4344 9755 add
Where: is:
543 21 676 8645 src_cell_id
543 21 4344 9755 neighbor_cell_id
System response
COMMAND ACCEPTED
Example 2
This example changes the power budget algorithm to 3 for neighbour cell 5 4 3 2 1 344 975
of src_cell 5 4 3 2 1 667 865. Additional prompts display.
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 parameter to be modified
3 parameter value
68P02901W23-Q 2-401
System response
Enter the uplink receive level threshold of the serving cell: 25
Enter the downlink receive level threshold of the serving cell: 25
COMMAND ACCEPTED
Example 3
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 parameter to be modified
1 parameter value
System response
Enter the threshold for inner zone handover:1
Enter the margin for inner zone handover: 1
COMMAND ACCEPTED
Example 4
This example modifies the scr_code element of UMTS UTRAN neighbour cell 4 9 6 2 3 1 1 1
1 to a value of 5 as a neighbour 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 parameter to be modified
5 parameter value
System response
COMMAND ACCEPTED
2-402 68P02901W23-Q
References
Related commands
"add_cell" on page 2-21, "add_neighbor" on page 2-35, "copy_cell" on page 2-157, "del_cell"
on page 2-169, "del_neighbor" on page 2-174, "disp_cell" on page 2-206, "disp_gsm_cells"
on page 2-254, "disp_neighbor" on page 2-282
68P02901W23-Q 2-403
modify_value Chapter 2: Device/function related commands
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.
{24513} This command is rejected if a dual band Horizonmacro II cabinet would
contain an invalid HII Dual Band DRI setup
Security level 2
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.
Refer to the descriptions of individual parameters for additional operator

actions that may be required.
Format
Syntax
modify_value <location> <value_name> <new_value> <dev_func>
<dev_func_id1> <dev_func_id2> <dev_func_id3>
2-404 68P02901W23-Q
Technical Description: BSS Command Reference modify_value
Input parameters
location
Specifies the location of the device. Values are:
0 or bsc BSC
1 to 120 BTS
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 all 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
7 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 7 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 7.
dev_func_id1
Values are dependent on the device/function type.
dev_func_id2
dev_func_id3
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.
68P02901W23-Q 2-405
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
{22064}
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
Example 3
{22064}
2-406 68P02901W23-Q
Technical Description: BSS Command Reference modify_value
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
{22064}
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
System response
WARNING: AMR and GSM Half Rate is currently disabled at this BSC.
COMMAND ACCEPTED
68P02901W23-Q 2-407
References
Related commands
"disp_equipment" on page 2-235, "equip" on page 2-329,"reassign" on page 2-415.
2-408 68P02901W23-Q
Technical Description: BSS Command Reference page
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.
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
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 number Any numeric value between 20 and 255.
of lines displayed per page
none Displays current page setting Not applicable
68P02901W23-Q 2-409
page Chapter 2: Device/function related commands
Examples
Example 1
This example shows that pagination has been enabled, and displays will display 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 2-49,"disp_act_alarm" on page 2-196, "disp_bss" on page 2-199, "disp_cal_data"
on page 2-201, "disp_cbch_state" on page 2-203, "disp_cell" on page 2-206, "disp_cell_status" on
page 2-214,"disp_csfp" on page 2-226, "disp_csfp_status" on page 2-228, "disp_dte" on page 2-230,
"disp_enable_stat" on page 4-10, "disp_equipment" on page 2-235, "disp_gsm_cells" on page 2-254,
"disp_hdlc" on page 2-257, "disp_hopping" on page 2-260, "disp_link" on page 2-266, "disp_link_usage"
on page 2-268, "disp_mms_ts_usage" on page 2-270, "disp_neighbor" on page 2-282, "disp_options"
on page 2-291, "disp_processor" on page 2-295, "disp_rtf_channel" on page 2-301, "disp_rtf_path"
on page 2-308, "disp_stats" on page 4-21, "disp_stat_prop" on page 4-16, "disp_throttle" on page
2-314, "disp_trace_call" on page 2-318, "disp_traffic" on page 2-321, "man" on page 3-8, "site_audit"
on page 2-441, "state" on page 2-448, "status_mode" on page 2-460.
2-410 68P02901W23-Q
Technical Description: BSS Command Reference query_audits
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 “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:
• 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
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>
Input parameters
location
68P02901W23-Q 2-411
query_audits Chapter 2: Device/function related commands

0 or bsc BSC
1 to 120 BTS
audit_type
Specifies the amount of information required.
short Displays all the audits in progress for a specific device at a customer site.
long Displays all the information for all the audits for a specific device at the customer
site.
device_name
The name that uniquely identifies the device. The valid device names are:
BSP DRI KSW
BTP GCLK MSI
DHP GPROC TDM
The following device may be audited at a PCU site using this command:
DPROC MSI PSP
device_id1
device_id2
device_id3
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
2-412 68P02901W23-Q
Technical Description: BSS Command Reference query_audits
Where: is:
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
Audit Type: INT_LPBK Idle/Active State: IDLE
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
System response
Audit Type: SAFE Idle/Active State: IDLE
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
68P02901W23-Q 2-413
query_audits Chapter 2: Device/function related commands
System response
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 2-54, "chg_audit_sched" on page 2-72, "device_audit" on page
2-414 68P02901W23-Q
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 2
Prerequisites DRIs can only be assigned to GPROCs in the same cage as the DRI.
A site device may 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 to 120 BTS
68P02901W23-Q 2-415
reassign Chapter 2: Device/function related commands
child_name
Literal that uniquely identifies the device. Current values are:
CBL DRI GSL MTL SITE
child_dev_id_1
The first chlid 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 may 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: CBLGSLMTLSITE
parent_func_id_1
Values are dependent on the device or function type.
parent_func_id_2
parent_func_id_3
Example
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
2-416 68P02901W23-Q
Technical Description: BSS Command Reference reassign
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:
COMMAND ACCEPTED
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 will be freed, and
should one be available, another transceiver will be found. Where no standby DRIs are available
and a BCCH RTF is free, a search will be 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 may not be present or may be in an invalid state.
• The DRI is not in the same cage as the destination BTP, BTF, or DHP.
• The DRI cannot be configured due to catastrophic hardware failure.
Related commands
"disp_equipment" on page 2-235, "equip" on page 2-329, "modify_value" on page
2-404, "disp_processor" on page 2-295.
68P02901W23-Q 2-417
reattempt_pl Chapter 2: 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 1
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 to 120 BTS
gclk_id
The GCLK identifier. The valid values are 0 or 1.
Example
In this example, the GCLK 0 will be forced to attempt phase lock.
2-418 68P02901W23-Q
Technical Description: BSS Command Reference reattempt_pl
reattempt_pl bsc 0
Where: is:
bsc location
0 gclk_id
System response
COMMAND ACCEPTED
References
Related command
68P02901W23-Q 2-419
reset_device Chapter 2: Device/function related commands
reset_device
Description
The reset_device command brings a device into service by locking then unlocking the device.
Additionally, a hard reset is performed if the device supports a hard reset.
The following devices support soft resets:
ABSS AXCDR CAB CBL CIC COMB
CSFP DPROC EAS GBL GCLK GSL
MMS MTL OML PATH PCU
RSL SITE XBL
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 resets:
BSP BTP DHP DRI GPROC KSW MSI
When a KSW is reset, all calls currently in progress will be dropped. Normal call
processing will resume when the KSW is brought back into service.
The following exceptions apply to the reset_device command:
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
locking, the system will display 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.
2-420 68P02901W23-Q
Technical Description: BSS Command Reference reset_device
For remote transcoding BSC sites, CICs may not be reset on a per-MMS basis when the
BSC is operating in the dynamic allocation mode.
Security level 2
Prerequisites This command may be invoked 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> <de-
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 to 120 BTS
device_name
device_id1
device_id2
device_id3
CIC syntax
68P02901W23-Q 2-421
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>
<timeslot1> TO <timeslot2>
reset_device <location> CIC <cic_num1>
reset_device <location> CIC <cic_num1> TO <cic_num2>
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>
Input parameters
location
0 or bsc BSC
1 to 120 BTS
CIC
cic_num1
cic_num2
mms_id1
mms_id2
timeslot1
First timeslot.
timeslot2
group1
First group.
group2
Second group.
2-422 68P02901W23-Q
Technical Description: BSS Command Reference reset_device
*
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
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.
COMMAND ACCEPTED
Example 3
This example resets a range of CICs devices, specifying them by their MMS, TS and group.
68P02901W23-Q 2-423
reset_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
References
Related commands
"ins_device" on page 2-382, "lock_device" on page 2-387, "unlock_device" on page 2-504.
2-424 68P02901W23-Q
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.
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.
Commands must be entered within 10 minutes after the MMI-RAM -> prompt
displays. If a command is not entered, the system resets.
Security level 2
Prerequisites None
Operator actions Place the system in the SYSGEN ON mode before entering this
command.
Note that the system does not permit resetting all_sites, all_bts, or
a list of site options in SYSGEN ON mode.
68P02901W23-Q 2-425
reset_site Chapter 2: Device/function related commands
Format
Syntax
reset_site [<location>]
Input parameter
location
Specifies the site(s) to be reset. Valid values are:
all_sites all sites including BSC

all_bts all sites excluding BSC
bsc BSC (site 0)
bsc, 1 to 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 to 120 BTS
pcu_0 to pcu_2 PCU (Note that pcu or PCU entered without a number will result in
a syntax error.)
When in SYSGEN ON mode, only the local site is reset.
Verification messages
One of the following verification messages issues prior to 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)

2-426 68P02901W23-Q
Examples
Example 1
In this example, a single site is reset:
reset_site 2
Where: is:
2 location
System response
WARNING: Command will REBOOT the following site(s): 2
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
Example 3
In this example, an attempt is made to reset the BSC (site) using the 0 option:
68P02901W23-Q 2-427
reset_site Chapter 2: Device/function related commands
reset_site 0
Where: is:
0 location
System response
COMMAND REJECTED: The “0" option is not allowed while resetting
BSC, you should enter “bsc".
References
Related information
If the user is logged in to a non-BSC site and attempts to reset other
site(s), 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 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
2-428 68P02901W23-Q
Related command
"sysgen_mode" on page 2-469
68P02901W23-Q 2-429
set_full_power Chapter 2: Device/function related commands
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 2
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 system being used (PGSM, EGSM, DCS1800, PCS1900).
2-430 68P02901W23-Q
Technical Description: BSS Command Reference set_full_power
location
Specifies the location.
0 or bsc BSC
1 to 120 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 will be
turned on
set_full_power cell_number=543 21 31967 45988 on 45
Where: is:
543 21 31967 45988 cell_number
turned on
System response
COMMAND ACCEPTED
Example 2
The following example turns off the Full Power mode for GSM Cell ID 5 4 3 2 1 31967 45988:
68P02901W23-Q 2-431
set_full_power Chapter 2: Device/function related commands
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
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
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":
2-432 68P02901W23-Q
Technical Description: BSS Command Reference set_full_power
set_full_power cell_name="london-south" on 45
Where: is:
turned on
System response
COMMAND ACCEPTED
68P02901W23-Q 2-433
set_relay_contact Chapter 2: Device/function related commands
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 2
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
0 or bsc BSC
1 to 120 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
relay_number
Specifies the physical relay number to be set (1 to 4).
2-434 68P02901W23-Q
Technical Description: BSS Command Reference set_relay_contact
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 2-329.
68P02901W23-Q 2-435
shutdown_device Chapter 2: Device/function related commands
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 may not be shutdown on a per-MMS basis
when the BSC is operating in the dynamic allocation mode.
Security level 2
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 shutdown before entering this command.
Format
General syntax
shutdown_device <location> <device_name> <device_id1> <device_id2><de-
vice_id3> <seconds> [wait <seconds>]
Input parameters
location
2-436 68P02901W23-Q
Technical Description: BSS Command Reference shutdown_device

0 or bsc BSC
1 to 120 BTS
device_name
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.
The wait parameter is optional for all devices except the CIC. It is required for the CIC device.
CIC syntax
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>
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>
<mms_id2> <timeslot1> <group> wait <seconds>
68P02901W23-Q 2-437
<mms_id2> <timeslot1> * wait <seconds>

shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1>
<group1> TO <timeslot2> <group2> wait <seconds>
Input parameters
location
0 or bsc BSC
1 to 120 BTS
CIC
cic_num1
cic_num2
mms_id1
mms_id2
timeslot1
First timeslot.
timeslot2
group1
First group.
group2
Second group.
*
wait
The period the system should wait before blocking a busy device.
2-438 68P02901W23-Q
Technical Description: BSS Command Reference shutdown_device
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
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 Mandatary for CIC
5 wait period
68P02901W23-Q 2-439
System response
COMMAND ACCEPTED
References
Related commands
"disp_equipment" on page 2-235, "equip" on page 2-329, "lock_device" on page 2-387, "state" on
page 2-448, "state" on page 2-448, "unlock_device" on page 2-504.
2-440 68P02901W23-Q
Technical Description: BSS Command Reference site_audit
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:
• 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.
The error messages listed above are those 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 may be run at a time.
Security level 2
performed.
This command is not allowed while in SYSGEN ON mode.
68P02901W23-Q 2-441
site_audit Chapter 2: Device/function related commands
Format
Syntax
site_audit <location> [<control>]
Input parameters
location
0 or bsc BSC
1 to 120 BTS
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
Audit Type: SAFE Result: AUDIT NOT SUPPORTED/AVAILABLE
Audit Type: INT_LPBK Result: AUDIT NOT SUPPORTED/AVAILABLE
2-442 68P02901W23-Q
Technical Description: BSS Command Reference site_audit

Device: GCLK Device id: 0 0 0
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
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 audit(s) are completed.
68P02901W23-Q 2-443
site_audit Chapter 2: Device/function related commands
Related commands
"cage_audit" on page 2-54, "chg_audit_sched" on page 2-72, "device_audit" on page
2-185, "query_audits" on page 2-411.
2-444 68P02901W23-Q
Technical Description: BSS Command Reference soft_reset
soft_reset
Description
The soft_reset command restarts the processes at one or more sites.

A user logged in to a BTS can only restart the local site. Only a user logged in to the
BSC can restart sites other than the local site.
Security level 2
Prerequisites Site(s) 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>
After entering one of the above commands, the user is prompted with a warning and
must enter “y" or “Y" (for yes) for the command to execute.
68P02901W23-Q 2-445
soft_reset Chapter 2: Device/function related commands
Input parameters
pcu-n
This parameter specifies a PCU for reset:
Where: is:
pcu_0 PCU site 0 (or the only PCU) at the BSC
pcu_1 PCU site 1 at the BSC
pcu_2 PCU site 2 at the BSC
The setting pcu or PCU without a number will result in rejection of the command.
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 1 to 120.
Verification prompts
When the command is entered to reset multiple sites, the
system displays one of the following verification prompts:
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>
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>

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!!!
2-446 68P02901W23-Q
Technical Description: BSS Command Reference soft_reset
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 IS 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.
1 OUT OF SERVICE
2 RESET REQUEST IN PROGRESS
4 NOT M-CELL
Example 2
In the following example, site 1, 4, and 9 are reset:
soft_reset 1 4 9
Where: is:
149 Sites to be reset.
System response
WARNING: Command will RESTART all processes at the following sites:
1 4 9
4 NOT EQUIPPED
9 TIMEOUT
68P02901W23-Q 2-447
state Chapter 2: 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 of the devices at all of the
locations in the system by entering the state all or state all all command.
The following devices can be investigated with this command:
CAGE CBL CELL CBUS CIC
COMB CSFP DHP DRI DYNET
EAS GCLK GPROC KSW LAN
MMS MSI MTL OML PATH
PBUS PCHN RSL SBUS SITE
TBUS TDM XBL RXCDR
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
Prerequisites Not available on an RXCDR.
This command is not available while in SYSGEN ON mode.
Format
Syntax
state <location> [<filter>] [<dev/func_name> <dev/func id> <dev/func
id> <dev/func id>] [<option1>] [option2]
2-448 68P02901W23-Q
Technical Description: BSS Command Reference state
Input parameters
location
0 or bsc BSC
1 to 120 BTS
all Specifies all sites
filter
Optional text string used to select devices or functions in a specific state. Valid values are:
busy enabled-unlocked
ins locked
oos unlocked
For a CIC or range of CICs, filter is not available.

dev/func name
Literal that uniquely identifies the device or function. all maybe 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
The option parameter displays the configuration tag(s) and the device subtypes for
the specified device(s) or function(s).
There are two options:
• Enter tags to display the configuration tags. Configuration tags are described in
Operating Information: GSM System Operation (68P02901W14).
• Enter subtypes to display the device subtypes.
68P02901W23-Q 2-449
The character string for the option may 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
state <location> CIC <cic_num1>
state <location> CIC <cic_num1> TO <cic_num2>
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>
For remote transcoding BSC sites, the state command may not be used for CICs devices
when the BSC is operating in the dynamic allocation mode.
state <location> CIC <cic_num1>
state <location> CIC <cic_num1> TO <cic_num2>
The following four state commands are valid only in BC mode.
state <location> CIC <mms_id1> <mms_id2>

state <location> CIC <mms_id1> <mms_id2> <timeslot1> <group>
state <location> CIC <mms_id1> <mms_id2> <timeslot1> *
state <location> CIC <mms_id1> <mms_id2> <timeslot1>
2-450 68P02901W23-Q
Input parameters
location
0 or bsc BSC
1 to 120 BTS
CIC
cic_num1
cic_num2
mms_id1, mms_id2, timeslot1, group1, and group2 are valid only in BC mode.
mms_id1
mms_id2
timeslot1
First timeslot.
timeslot2
group1
First group.
group2
Second group.
*
68P02901W23-Q 2-451
For a CIC or range of CICs, neither filter nor option are available.
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
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
DEVICE STATUS INFORMATION FOR LOCATION 0:

ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown
Last Transition Config
2-452 68P02901W23-Q
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
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
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

---------- ----- -------------- -------------------------
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
68P02901W23-Q 2-453
...
...
...
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
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
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
time of last transition: SAT JAN 5 12:55:18 1980
Config Tag (hex): 00000006
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
2-454 68P02901W23-Q
Where: is:
* wildcard character for dev/func ID
subtypes option1
System response
------------ ------ ------------------------ --------------- --------
(MSI)
(XCDR)
(MSI)
MSI 3 0 0 E-L NO REASON 05/01 12:55:18 None
(MSI)
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
* option 2
System response
----------- ------ -------------------------- --------------- --------
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
68P02901W23-Q 2-455
Example 8
This command displays the status of the CAGE device at PCU site 1:
state pcu_1 cage 0
Where: is:
pcu_1 location
cage dev/func name
0 CAGE identifier
System response
STATUS INFORMATION:
Device: CAGE 0 0 0
Operational state: BUSY
Time of last transition: Tue Jan 3 05:00:30 1999
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
Operational state: BUSY
Time of last transition: Sun Jan 6 01:37:49 2002
Related device/Function: None
Example 10
Displays the status of all MSIs at PCU site 1.
2-456 68P02901W23-Q
state PCU_1 MSI *
Where: is:
PCU_1 location
MSI device name
* all MSIs
System response
DEVICE STATUS INFORMATION FOR LOCATION PCU site 1:
----------- ----- ----------------------- -----------------------
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 2-30 lists the operational states.
Table 2-30 Operational states
Op state Description
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 2-31 lists the administrative states.
Table 2-31 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 2-32 lists the device states.
68P02901W23-Q 2-457
Table 2-32 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 Unlocked FM finds the device unserviceable but the operator wants it in service. The system
may periodically audit the device (the operator can force audits) to determine if the
device may be 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.
The remaining states LOCKED and NOT EQUIPPED in Table 2-32 cannot
exist with any operational component.
Table 2-33 lists the reason codes.
Table 2-33 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.
2-458 68P02901W23-Q
Table 2-33 Reason codes (Continued)

Reason Codes Value Explanation
Applicable to combiners
COMBINER_CONTROLLER 14 Indicates which transceiver is controlling a particular
combiner.
Related commands
page 2-448, "unlock_device" on page 2-504, "shutdown_device" on page 2-436.
68P02901W23-Q 2-459
status_mode Chapter 2: 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 displays:
• Status notification is ON
• Status notification is OFF
• Site unequipped
• Site unavailable
• Status notification is already ON
• Status notification is already OFF
Multiple sites may be disabled using the same command line by entering the site IDs separated
by a space. All sites may be disabled by entering all for the location.
Location all is only allowed at the BSC.

Security level 1
Prerequisites To display the status mode for the PCU, the GPRS feature must
be unrestricted.
2-460 68P02901W23-Q
Technical Description: BSS Command Reference status_mode
Format
Syntax
status_mode <location> [<location> ...<location>] [<mode>]
Input parameters
location
0 or bsc BSC
1 to 120 BTS
pcu, pcu1 to pcu2 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 the CA device state-change notification on 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
Example 2
This example shows the command string required to display the status mode for an entire BSC.
68P02901W23-Q 2-461
status_mode Chapter 2: Device/function related commands
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 the CA device state change notification off at location 6:
status_mode 6 off
Where: is:
6 location
off mode
System response
SITE STATUS
---- ----------------
0 Status notification turned OFF
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 #>
2-462 68P02901W23-Q
Technical Description: BSS Command Reference status_mode
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-Q 2-463
store_cal_data Chapter 2: 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 may be enabled by using all for the location value.
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 2
Enter this command at the BSC only. This command is unavailable at a BTS
Format
Syntax
store_cal_data <location>
Input parameter
location
Specifies the site for storing transceiver calibration data:
1 to 120 BTS
all All sites in the current BSS
2-464 68P02901W23-Q
Technical Description: BSS Command Reference store_cal_data
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
References
Related commands
"clear_cal_data" on page 2-147, "disp_cal_data" on page 2-201.
68P02901W23-Q 2-465
swap_devices Chapter 2: Device/function related commands
swap_devices
Description
The swap_devices command swaps the specified standby device with the specified active device.
The following devices may be swapped by this command:
BTP COMB GCLK LAN TDM
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 can not 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.
Security level 2
Operator actions Unlock the standby device to be swapped.
Format
Syntax
swap_devices <location> <active_device_name> [<std_device_id1>]
2-466 68P02901W23-Q
Technical Description: BSS Command Reference swap_devices
Input parameters
location
0 or bsc BSC
1 to 120 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
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
68P02901W23-Q 2-467
swap_devices Chapter 2: Device/function related commands
Example 3
This example swaps the active gclk with the standby gclk at BTS site 1:
swap_devices 1 gclk
Where: is:
1 location
gclk active_device_name
System response
COMMAND ACCEPTED
Example 4
This example swaps the active btp with the standby btp at BTS site 1:
swap_devices 1 btp
Where: is:
1 location
btp active_device_name
System response
COMMAND ACCEPTED
References
Related commands
page 2-448, "unequip" on page 2-494, "unlock_device" on page 2-504
2-468 68P02901W23-Q
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.
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.
{22064}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 users.
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.
68P02901W23-Q 2-469
sysgen_mode Chapter 2: Device/function related commands
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 may 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 1
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.
Examples
Example 1
In this example, the system is placed in the SYSGEN OFF mode of operation:
2-470 68P02901W23-Q
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.
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 will be
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
System response
Current Sysgen mode: ON
Sysgen mode upon next restart: OFF
Example 4
This example attempts to turn SYSGEN mode off when an EGPRS RTF and a non-EGPRS
RTF share the same FHI in a baseband hopping system:
sysgen_mode off
System response
********** VERIFYING DATABASE BEFORE COMPLETING SYSGEN **********
Frequency hopping verification in progress...
Site 1: GSM Cell: 001 01 1 (0001h) 1 (0001h)
---------------------------------------------------------
ERROR: EGPRS and non-EGPRS carriers cannot
have the same FHI. SITE 0 Verification.
68P02901W23-Q 2-471
Errors were found in the database.
REJECTING SYSGEN_OFF REQUEST
Example 5
This example attempts to turn SYSGEN mode off when an EGPRS RTF has valid FHI in baseband
hopping and the master cabinet at the site is not Horizonmacro2:
sysgen_mode off
********** VERIFYING DATABASE BEFORE COMPLETING SYSGEN **********
Frequency hopping verification in progress...
Site 1: GSM Cell: 001 01 1 (0001h) 1 (0001h)
---------------------------------------------------------
ERROR: Master cabinet must be Horizonmacro2
for EGPRS RTFs to hop in baseband hoppping.
REJECTING SYSGEN_OFF REQUEST
Example 6
{22064}
This example attempts to turn SYSGEN mode off with GSM Half Rate enabled but
with CIC validation disabled for an AXCDR:
sysgen_mode off
WARNING: AXCDR CIC validation must be enabled for AMR or GSM HR.
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 <cell_number>
2-472 68P02901W23-Q
INVALID DATA IN BIN <bin>: decision_1_dl_rxlev_av_h error in

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
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.
site: <site_id> cell: <cell_number> hopping_support: <hopping_support>
site: <site_id> cell: <cell_number> hopping_support: <hopping_support>
...
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>.
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 > mis-
matches 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>
68P02901W23-Q 2-473
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
EGPRS and non-EGPRS carriers cannot have the same FHI
Database warnings
A database warning causes the sysgen_mode off command to be rejected and a database is not created; a
warning message displays. All warning messages are preceded with the DB VERIFY WARNING: string.
General database warnings

Maximum MTLs should be the same value for all BSPs.
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.
sd_load is zero for all carriers in local cell <cell number>.
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 may be generated.
Related commands
"chg_level" on page 2-115, "disp_level" on page 2-265,"reset_site" on page 2-425.
2-474 68P02901W23-Q
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
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-Q 2-475
time_stamp Chapter 2: 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 2-135, "disp_time" on page 2-316.
2-476 68P02901W23-Q
Technical Description: BSS Command Reference trace_call
trace_call
Description
The trace_call command creates a call trace instance in the BSS. An instance is a set of criteria
that defines a trace. A maximum of 16 instances may exist on a BSS.
The number of call trace instances that may 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 may be created using the trace_call command.
The trace_call command is primarily intended for tracing calls 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 can not 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 may 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 may 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 and RSS data may
also be specified for inclusion in the basic call trace data.
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 may impact 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 may
increase. This increase, together with “normal" OML traffic (such as alarms and uploads/downloads),
may 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.
68P02901W23-Q 2-477
trace_call Chapter 2: Device/function related commands
Reports generated by this command include a set of basic call trace data. Any combination
of Abis, BSSMAP, DTAP, MS_POWER_CONTROL, RR and RSS data may 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
may impact OML, BSS, or OMC-R performance.
For example, a large number of call traces initiated on multiple BSSs connected to a single
OMC-R may increase the OML traffic. This increase, together with “normal" OML traffic (such
as alarms and uploads/downloads), may cause some call_trace data to be lost. Call Trace Flow
Control reduces, and may eliminate, this from occuring. Refer to the ct_flow_control_hi_level
and ct_flow_control_lo_level parameters for more information.
Security level 2
Prerequisites This command is not allowed in SYSGEN mode.
Format
Syntax
trace_call <location> [rtf <id1> <id2> <id3>]
trace_call <cell_desc>
trace_call all
Input parameters
location
The location of the equipment:
0 or bsc BSC
1 to 120 BTS
all all locations
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.
2-478 68P02901W23-Q
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 system accepts only one of the following inputs: location, cell_number or cell_name.
Do not combine these parameters in a single command.
Examples
Refer to the Related information subsection for a description of the prompts dis-
played 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.
• Any trigger events may 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.
68P02901W23-Q 2-479
• 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: 1
Enter destination for trace data: mmi
COMMAND ACCEPTED
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, above.
Example 2
This example shows a trace on a specified MS whenever it hands over into the specified cell.
• 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"
Enter total number of calls to be traced:
Trace calls beyond scope?: no
Enter destination for trace data: both
2-480 68P02901W23-Q
COMMAND ACCEPTED
Example 3
This example shows a trace on BTS location 2, RTF 0 0.
• Any trigger event may 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 will be 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.

trace_call 2 rtf 0 0
Where: is:
2 BTS location
rtf rtf
0 id1
0 id2
System response
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
Enter total number of calls to be traced: 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.
• Any trigger event may 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 = 480ms).
• The system traces every seventh call.
• No more that four calls can be traced simultaneously.
68P02901W23-Q 2-481
• 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.

trace_call 4 rtf 0 1
Where: is:
4 BTS location
rtf rtf
0 id1
1 id2
System response
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:
Trace calls beyond scope?: yes
Enter destination for trace data:
COMMAND ACCEPTED
The “Enter Measurement Report interval (X480ms)" prompt displays only if the
operator enters “no" to the previous prompt.
References
Related information
Prompts preceded by an * in Table 2-34 are only displayed under the conditions described in the Notes column.
2-482 68P02901W23-Q
Table 2-34 trace_call prompts and values
Valid range
Prompt Default Notes
or values
Enter trigger event: setup all If a particular mobile or SCCP number has
handover been specified, all includes tracing calls that
all are already in progress, upon criteria created
on entering of any daily triggering period.
Enter additional abis Basic Basic data is always sent. Multiple data
data types (Basic bssmap record types can also be listed. If multiple
is included): dtap data types are used, separate them with a
ms_power comma and space, like this: dtap, rss
rr
rss If RSS is entered as a data type, the system
all prompts for an additional parameter, the
“Measurement Report Interval."
Collect during yes No The system only prompts for this parameter
handover only?: no if the RSS, Abis and/or MS_Power data
1 types are specified.
0 0 or no means that the system collects all of
the specified types of trace data when they
are available.
1 or yes means the system will collect RSS,
Abis and/or MS_Power call trace data, only
if specified, and only before and after a
handover has occurred.
The number of messages collected is
determined by the trace_msgs_before_ho
and trace_msgs_after_ho data base
parameters.
* Enter Measurement Any value 10 (4.8 The system displays this prompt if the
Report interval between 1 seconds) RSS data type is specified in the preceding
(X480ms): and 255 prompt and the user did not specify data
only during handovers. If the user specifies
data only during handovers, then this
parameter defaults to one. Measurement
reports are produced every 480 ms. The
user need not collect all measurement
reports.
This parameter specifies the number of
480ms periods to wait before collecting
another measurement report.
Using a value of 3 or less can overload the
OML with measurement data. Motorola
recommends using larger values.
68P02901W23-Q 2-483
Table 2-34 trace_call prompts and values (Continued)

Valid range
or values
Enter call selector IMSI=“msid" None Mobile station identifier (“msid") is a
type and value: TMSI=“msid" number that identifies a specific mobile unit
IMEI=“msid" or subscriber. It must be enclosed in double
IMEISV=“msid" quotation marks.
SCCP=0 to The signalling connection control part
FAFFFFh (SCCP) number identifies a particular call.
Nth= 1 to 255 Do not put quotation marks around a SCCP
number or an Nth call number.
If Nth call is specified, the system prompts
for the “maximum simultaneous calls traced
per LCF."
Results of tracing by IMEI or IMEISV may
not be reliable because the BSS is rarely
informed of the IMEI or IMEISV of an MS.
Instead use the MSC to trace more reliably
by IMEI or IMEISV. Also, reliable IMSI
tracing requires the MSC to page by IMSI
instead of TMSI.
* Enter maximum Any value 1 The system displays this prompt if the call
simultaneous calls between 1 selector type is Nth call.
traced per LCF: through 16 16 is the maximum number of simultaneous
traces per LCF.
The larger the value set, the more it will
overload the OML, depending also on
how broad the scope, and the setting of
the measurement report interval (above).
Motorola recommends using smaller values.
Triggered enabled A time Immediate If no time is specified, the trace begins
time: between start immediately and no trace period is used.
Midnight (00 If a time is specified, the system prompts
00) and 23 59. for the “trigger disable time."
Enter the time “Time" is the time of day, using a 24 hour
without using clock.
a colon. For Once enabled, the trace must still be
example, 8 25 triggered according to the specified trigger
PM would be: event before data will be collected.
20 25
* Trigger disabled A time None The system displays this prompt if a trigger
time between enabled time is specified. A valid value is
Midnight (00 required.
00) and 23 59. The trace is not deleted at the trigger
Enter the time disabled time, it is suspended until the
without using trigger enabled time the following day. To
a colon. For delete the trace, the operator must either:
example, 8 25
PM would be: • specify a total number of calls to trace,
20 25 or
• delete the trace manually.
2-484 68P02901W23-Q
Table 2-34 trace_call prompts and values (Continued)

Valid range
or values
Enter total number of Any value None - trace If no value is specified there is no limit, and
calls to be traced: between 1 until deleted the trace will exist until the trace is deleted
through 255 manually manually by an operator.
If a value is specified, the trace will be
deleted automatically after the specified
number of calls have been traced.
Trace calls beyond yes or no no No or 0 means trace data is no longer
scope? 1 or 0 collected if the call hands out of the
specified scope.
Yes or 1 means that once a call triggers a
trace, it will be traced beyond the scope
until the call is completed, or until it leaves
the current BSS.
Enter destination for mmi mmi Trace reports may be directed to the MMI,
trace data: omc the OMC-R, or both.
both
Related commands
"disp_trace_call" on page 2-318, "trace_stop" on page 2-489.
68P02901W23-Q 2-485
trace_connection Chapter 2: Device/function related commands
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 user is prompted to enter the MMS timeslot number.
Security level 2
Prerequisites
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
RSL XBL
GSL MTL
When the MMS is specified, the user is prompted for the MMS timeslot.
<id1><id2><id3>
2-486 68P02901W23-Q
Technical Description: BSS Command Reference trace_connection
Device identifiers
Examples
Example 1
This example displays the connectivity information for timeslot 1 of MMS 2 0:
trace_conn 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: 16K_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
Example 2
This example displays the connectivity information of RSL 4 1:
trace_conn 0 rsl 4 1
Where: is:
rsl 4 1 the device
System response
Start of Report
Path Id: 4 1
BSC downlink 2 0 16
BTS 1 uplink 0 0 16
downlink 1 1 2
BTS 4 uplink 0 1 2
End of Report
Example 3
This example displays the connectivity information for timeslot 3 of MMS 2 0 when
there is a TS_SWITCH in the call path:
68P02901W23-Q 2-487
trace_connection Chapter 2: Device/function related commands
trace_conn 0 mms 2 0
Where: is:
mms 2 0 the device
System response
Enter the timeslot: 3
Start of Report
Timeslot Usage: RSL 0 0
BSC downlink 2 0 16
TS_SWITCH N/A N/A
BTS 4 uplink 0 0 16
End of Report
2-488 68P02901W23-Q
Technical Description: BSS Command Reference trace_stop
trace_stop
Description
The trace_stop command deletes an existing trace or stops tracing a specified call.
Security level 2
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.
sccp SCCP number. This input requires a <value>.

ref Trace reference number. 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 0FAFFFFh
ref between 0 and 0FFFFFFFFh
The hexadecimal number input requires a 0 prefix and an h suffix.
68P02901W23-Q 2-489
trace_stop Chapter 2: Device/function related commands
extent
The extent to which traces should stop. extent is not valid when type is set to sccp.
all All traces should be stopped and the specified instance should be deleted
immediately.
If no extent is set, the system defaults to all.
new No new traces are to be started, and the specified instance should be deleted once all
previously triggered traces are completed.
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
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 will be deleted from the database.
2-490 68P02901W23-Q
Technical Description: BSS Command Reference trace_stop
trace_stop ref=080270001h new
Where: is:
ref type
080270001h value
new extent
System response
COMMAND ACCEPTED
68P02901W23-Q 2-491
unconfigure_csfp Chapter 2: Device/function related commands
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 2
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.
Format
Syntax
unconfigure_csfp
Input parameters
Example
In this example, all of the CSFP devices in the network are unconfigured.
unconfigure_csfp
2-492 68P02901W23-Q
Technical Description: BSS Command Reference unconfigure_csfp
System response
COMMAND ACCEPTED
References
Related commands
"chg_csfp" on page 2-85, "configure_csfp" on page 2-153, "disp_csfp" on page 2-226.
68P02901W23-Q 2-493
unequip Chapter 2: Device/function related commands
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.
Security level 2
Prerequisites The unequip command is only allowed for a locked device or
function.
No child dependencies may exist for the
specified device or function to be unequipped. If a dependency is
detected, the unequip command will be rejected.
See SYSGEN states below for further information
Operator actions Lock the device or function to be unequipped.
Place the system in the SYSGEN ON mode if an CBL, MTL, OMF,
or OML is to be unequipped using this command.
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.
2-494 68P02901W23-Q
Technical Description: BSS Command Reference unequip
In or out of SYSGEN
The following devices and functions may be unequipped using the unequip command with
the system in or out of the SYSGEN ON mode.
• CBL
• CIC
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)
All affected COMB devices must be OOS before using the unequip command.
• CSFP (InCell)
• DHP (InCell)
The unequip command is not available for DHP devices at a Horizonmicro.
• DRI
• DPROC
DPROC performed at site PCU.
68P02901W23-Q 2-495
• DYNET
A DYNET cannot be unequipped if: (1) It is the last DYNET containing a site using
dynamic allocation and that site still has equipped RTFs, or (2) 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
• GPROC (InCell)
• GSL
To bring the GSL out of service, lock it at either the OMC-R or at the MMI prompt.
GSL performed at site PCU
• KSW (InCell)
• LCF
• MSI
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.
• MTL
• OML
• PATH
2-496 68P02901W23-Q
• PCU
Up to three PCUs can be equipped, and therefore unequipped as

PCU_0, PCU_1 and PCU_2.
• RTF
An RTF cannot be unequipped if both of the following

conditions are true: (1) The cell is baseband hopping, and (2)
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 times-
lots or carriers is not sufficient to maintain current or less-one GPRS configurations.
• RSL
The unequip command does not allow unequipping an RSL from a 16kbit/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 will automatically unequip the additional 16K RSL when a 16K
RSL is being unequipped as part of a closed loop DYNET.
• SITE
The unequip command for a SITE device at a Horizonmicro BTS automatically

unequips any DGP devices that exist at that BTS site.
• XBL
• AXCDR
• ABSS
68P02901W23-Q 2-497
Standby devices
The following devices or functions may only be unequipped using the unequip command if they are standby
devices. These devices may 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 may only be unequipped using the unequip command
when the system is in the SYSGEN ON mode:
• OMF (BSC only)
The LCF may be unequipped using the unequip command if no sites exist on the LCF. The LCF
may be 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 may not 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 to 120 BTS
dev/func_name
Literal that uniquely identifies the device or function. The following devices and functions may be entered:
bsp dri omf
btp dynet oml
cab eas path
2-498 68P02901W23-Q
cbi gclk pcu
cic gproc rsl
comb ksw rtf
csfp lcf site
dhp msi xbl
mtl gsl
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
The PCU location must be specifed when unequipping the GPRS devices, except for the
PCU itself. To unequip the PCU, specify the BSC for the location. Child dependency
may exist when unequipping the PCU, except for GDS and GSL; that is, GBL, DPROC,
MSI, and NSVC may 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 may be 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 an PATH, the range varies depending on whether the BTS uses dynamic
allocation. The following ranges of values may be entered:
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
68P02901W23-Q 2-499
id3
Third identifier. This definition varies with each device or function.
CIC syntax
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>
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>
CIC
cic_num1
cic_num2
mms_id1
mms_id2
timeslot1
First timeslot.
timeslot2
group1
First group.
group2
Second group.
2-500 68P02901W23-Q
*
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
In this example, the RTF function located at the BTS is deleted from the CM database:
unequip 2 rtf 5 1 0
Where: is:
2 location
rtf dev/func_name
5 id1
1 id2
0 id3
System response
COMMAND ACCEPTED
Example
In this example, the system blocks unequipping the RSL because the reserved cell capacity would
exceed the total terrestrial backing resources for the BTS network:
68P02901W23-Q 2-501
unequip 0 rsl 1 0
Where: is:
0 location
rsl dev/func_name
1 id1
0 id2
System response
COMMAND REJECTED: Unequipage of RSL causes insufficient resources
for reserved cell needs.
Example 4
This example unequips a range of CICs, specifying them by their MMS, TS and group.
unequip 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
Example 5
This example unequips an extension cabinet of type TCU_2, TCU_6, or HORIZONMACRO_EXT
with the cabinet locked and no DRIs or EASs equipped to the cabinet.
unequip 50 cab 1 0 0
Where: is:
50 location
cab device_name
1 id1
0 id2
0 id3
System response
COMMAND ACCEPTED
2-502 68P02901W23-Q
Example 6
This example unequips PCU 0 from a BSC.
unequip 0 pcu 0
Where: is:
0 location
pcu device_name
0 id1
References
Related commands
"disp_equipment" on page 2-235, "equip" on page 2-329, "lock_device" on page 2-387, "shutdown_device"
on page 2-436, "state" on page 2-448, "unlock_device" on page 2-504
68P02901W23-Q 2-503
unlock_device Chapter 2: Device/function related commands
unlock_device
Description
The unlock_device command unlocks a specified device to free it for use.

Security level 2
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> <de-
Input parameters
location
0 or bsc BSC
1 to 120 BTS
device_name
The following devices can be unlocked using this command:
CBL CIC COMB CSFP DHP
2-504 68P02901W23-Q
Technical Description: BSS Command Reference unlock_device
DPROC DRI EAS GBL GCLK

GDS GPROC GSL KSW MMS
MSI MTL OML PATH PCU
RSL SBUS SITE XBL
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 may be unlocked at the PCU using this command:
DPROC GBL GDS GSL PCU
device_id1
device_id2
device_id3
CIC syntax
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>
<timeslot1> TO <timeslot2>
unlock_device <location> CIC <cic_num1>
unlock_device <location> CIC <cic_num1> TO <cic_num2>
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>
CIC
cic_num1
68P02901W23-Q 2-505

cic_num2
mms_id1
mms_id2
timeslot1
First timeslot.
timeslot2
group1
First group.
group2
Second group.
*
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
2-506 68P02901W23-Q
Technical Description: BSS Command Reference unlock_device
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
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
References
Related commands
"disp_equipment" on page 2-235, "equip" on page 2-329, "lock_device" on page 2-387,
"state" on page 2-448, "unequip" on page 2-494.
68P02901W23-Q 2-507
2-508 68P02901W23-Q
Chapter
3
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, and including information on
the command security level, whether supported by OMC-R GUI, the type of command, and the
prerequisites for the command to be accepted by the system.
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-Q 3-1
alias Chapter 3: UNIX commands
alias
Description
The alias command creates an alias for an MMI command. If no parameters are
entered, a list of active aliases are displayed.
The maximum length which can be entered is 256 characters. This includes 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 will not recognise the alias.
Security level Any
Prerequisites None
Format
Syntax
alias [<alias_name>’<alias_text>’]
Input parameters
alias_name
Name of the alias.
alias_text
Any valid MMI command. This can be just the command name or a command and parameters.
The alias_text must be enclosed in single quotes.
Example
This example creates an alias called “list" which executes the command string disp_equipment bsc:
3-2 68P02901W23-Q
Technical Description: BSS Command Reference alias
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 3-10.
68P02901W23-Q 3-3
help Chapter 3: 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 Any
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
3-4 68P02901W23-Q
Technical Description: BSS Command Reference help
References
Related command
"man" on page 3-8.
68P02901W23-Q 3-5
history Chapter 3: 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
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.
Examples
Example 1
This example lists the last three commands that were entered:
3-6 68P02901W23-Q
Technical Description: BSS Command Reference history
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 will
execute 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-Q 3-7
man Chapter 3: UNIX commands
man
Description
The man command is used to display detailed help information about the specified command.
Security level Any
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
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.
3-8 68P02901W23-Q
Technical Description: BSS Command Reference man
<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 3-4.
68P02901W23-Q 3-9
unalias Chapter 3: UNIX commands
unalias
Description
The unalias command removes the alias <alias_name> from the specific GPROC at which it was set.
Security level Any
Prerequisites None
Format
Syntax
unalias <alias_name>
Input parameter
alias_name
The name of the alias to be removed.
Example
This example removes the alias named “list".

unalias list
Where: is:
list alias_name
System response
COMMAND ACCEPTED
3-10 68P02901W23-Q
Technical Description: BSS Command Reference unalias
References
Related command
"alias" on page 3-2.
68P02901W23-Q 3-11
unalias Chapter 3: UNIX commands
3-12 68P02901W23-Q
Chapter
4
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, and including information on
the command security level, whether supported by OMC-R GUI, the type of command, and the
prerequisites for the command to be accepted by the system.
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.
Descriptions of individual statistics are described in the Maintenance Information:

GSM Statistics Application (68P02901W56) manual.
68P02901W23-Q 4-1
Statistical operations and information Chapter 4: 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 4-5).
• disp_enable_stat (see "disp_enable_stat" on page 4-10).
• disp_interval (see "disp_interval" on page 4-14).
• disp_stat_prop (see "disp_stat_prop" on page 4-16).
• disp_stats.(see "disp_stats" on page 4-21).
• stat_mode (see "stat_mode" on page 4-27).
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
Statistical information is generated by the system and can be used by system operators for:
• Monitoring the quality of service.
• Fault finding.
• Optimize system performance.
• Network planning.
• System installation and commissioning.
Statistical information is gathered in the form of:

• Counter statistics.
• Duration statistics.
4-2 68P02901W23-Q
Technical Description: BSS Command Reference Statistical operations and information
• Gauge statistics.
• Distribution statistics.
Counter statistics
Counter statistics represent the number of occurrences of an event. The event to be monitored 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.
Distribution statistics
Two types of distribution statistics, normal and weighted, are used to record all events or
state changes reported by some application processes.
68P02901W23-Q 4-3
Statistical operations and information Chapter 4: Statistics commands
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 range of a bin is determined by the size of the upper
and lower bins in which the data is collected. 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.
4-4 68P02901W23-Q
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.
• The alarm threshold may be changed for counter, counter array, and gauge statistics
if an alarm is associated with the statistic.
• 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 2
Prerequisites The GPRS feature must be unrestricted to display PCU statistics.
The EGPRS feature must be unrestricted to display EGPRS
associated statistics.
Enter this command only at the BSC. This command does not work at a BTS
Format
Syntax
chg_stat_prop <meas_type> [location] [<cell_desc>]
chg_stat_prop <meas_type> all
Input parameters
meas_type
68P02901W23-Q 4-5
chg_stat_prop Chapter 4: Statistics commands
Specifies the name of the statistic.

location
0 or bsc BSC
1 to 120 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 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 cell_number= 1 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
System response
Enter the alarm threshold: 500
4-6 68P02901W23-Q
COMMAND ACCEPTED
Example 2
This example shows the response if a counter or gauge statistic is specified that does
not have a corresponding alarm:
chg_stat_prop total_calls cell_number= 1 5 4 3 2 1 61698 34776
Where: is:
total_calls meas_type
1 location
5 4 3 2 1 61698 34776 cell_desc
System response
COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.
Example 3
This example changes minimum and maximum values for two bins for 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 4
This example shows the response if an attempt is made to modify a counter array statistic:
chg_stat_prop out_ho_cause_atmpt 1 all
Where: is:
out_ho_cause_atmpt meas_type
1 location
68P02901W23-Q 4-7
chg_stat_prop Chapter 4: Statistics commands
System response
COMMAND REJECTED: There are no properties of counter array statistics to modify.
Example 5
This example shows the response if an attempt is made to modify a total time statistic.
chg_stat_prop tch_congestion 1 all
Where: is:
tch_congestion meas_type
1 location
System response
COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.
Example 6
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
System response
Enter the alarm threshold: 500
COMMAND ACCEPTED
Example 7
This example attempts to change the properties for the EGPRS cell statistic EGPRS_DL_ASGN_PCCCH
when EGPRS is restricted:
chg_stat_prop egprs_dl_asgn_pccch cell_number= 543 721 61698 34776
Where: is:
egprs_dl_asgn_pccch meas_type
543 721 61698 34776 cell_desc
System response
COMMAND REJECTED: Received a request to modify a restricted optional parameter.
4-8 68P02901W23-Q
References
Related information
Table 4-1 lists the counter and gauge statistic type prompts.
Table 4-1 Counter and gauge statistic type prompts
Prompt Valid range Description

Enter the alarm 0 to 2147483647 If a <carriage return> is entered in response
threshold 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 4-2 lists the normal and weighted distribution statistic type prompts.
Table 4-2 Normal and weighted distribution statistic type prompts
Prompt Valid range Description

Enter the bin 0 to 9 Multiple bin numbers may be entered by
number(s): separating each bin number with a space
or comma.
Enter the min value for The minimum value that This prompt repeats for each bin number
bin n: may be entered is 0 (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 number
bin n: that may be entered is (n) entered in response to the first prompt.
2147483647 If a <carriage return> is entered in response
to the first prompt the current value is not
changed.
The system rejects the command if the minimum bin value is greater than the
maximum bin value for a distribution statistic.
Related commands
"disp_element" on page 2-232, "disp_enable_stat" on page 4-10, "disp_interval" on
page 4-14, "disp_stats" on page 4-21.
68P02901W23-Q 4-9
disp_enable_stat Chapter 4: 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.
If no arguments are entered with the command, a listing showing all of the enabled statistics displays.
If a Cell ID (or name) is entered with the command, a listing of enabled statistics at the specified cell displays.
If “bss" is entered with the command, a listing of the enabled statistics in the BSS displays.
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 displays.
Security level 1
Prerequisites None
Format
Syntax
disp_enable_stat
disp_enable_stat <cell_desc>
disp_enable_stat <bss>
disp_enable_stat <meas_type>
disp_enable_stat <location>
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 neighbour cell, and per timeslot statistics.
4-10 68P02901W23-Q
Technical Description: BSS Command Reference disp_enable_stat

bss
Specifies the BSS.
location
0 or bsc BSC
1 to 120 BTS
meas_type
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
The text that follows shows part of a typical display. Such a display continues until
all of the enabled statistics have been displayed.
68P02901W23-Q 4-11
disp_enable_stat Chapter 4: 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
mtp_linkfail
mtp_remote_proc
mtp_local_busy
mtp_congestion
cpu_usage
...
...
...
Enabled Statistics 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
...
...
...
tch_delay
intf_on_idle
busy_tch
busy_sdcch
ber
4-12 68P02901W23-Q
Technical Description: BSS Command Reference disp_enable_stat
Example 2
This example shows the disp_enable_stat display:
disp_enable_stat total_calls
System response
Statistic total_calls enabled for the following cells at site 18
----------------------------------------------------------------
543 21 F333h 028Ah
543 21 F333h 028Bh
543 21 F333h 028Ch

----------------------------------------------------------------
543 21 F333h 2128h

----------------------------------------------------------------
543 21 F333h 0031h

----------------------------------------------------------------
543 21 F333h 2127h

----------------------------------------------------------------
543 21 F333h 2124h
543 21 F333h 2125h
543 21 F333h 2126h
Example 3
This example shows which associated statistics are displayed when the CS3, CS4,
and 32 kbps GPRS TRAU are enabled:
disp_enable_stat gprs_32k_channels_switched
System response
Statistic gprs_32k_channels_enabled for the following cells at site 9
---------------------------------------------------------------------
123 45 6h 7h
References
Related commands
"disp_element" on page 2-232, "stat_mode" on page 4-27, "disp_interval" on page
4-14, "disp_stats" on page 4-21.
68P02901W23-Q 4-13
disp_interval Chapter 4: Statistics commands
disp_interval
Description
The disp_interval command displays the start times associated with each of the system statistics intervals.
Security level 1
Prerequisites This command is not allowed in SYSGEN ON mode.
Format
Syntax
disp_interval
Input parameters
Example
This example shows a sample of the display the system produces when the disp_interval command is entered:
disp_interval
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
4-14 68P02901W23-Q
Technical Description: BSS Command Reference disp_interval
9 13:30:00
10 14:00:00
11 14:30:00
References
Related commands
"disp_element" on page 2-232, "disp_enable_stat" on page 4-10, "stat_mode" on
68P02901W23-Q 4-15
disp_stat_prop Chapter 4: 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.
Additional information displayed using the disp_stat_prop command is determined by the statistic type:
• 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
Prerequisites None
Format
Syntax
disp_stat_prop <meas_type> <location> [<cell_desc>]
disp_stat_prop <meas_type> <location> all
Input parameters
meas_type
The name of the statistic.
location
4-16 68P02901W23-Q
Technical Description: BSS Command Reference disp_stat_prop
1 to 120 BTS
all All sites
cell_desc
The GSM Cell ID of the cell for which statistics properties are to be displayed, preceded by cell_number=.
Examples
Example 1
This example displays the properties associated with the TOTAL_CALLS 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:
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
68P02901W23-Q 4-17
Example 2
This example displays the properties associated with the TOTAL_CALLS statistic for all cells at site 1:
disp_stat_prop total_calls 1 all
Where: is:
1 location
all all cells at the specified location.
System response
STATISTIC: TOTAL_CALLS SITE: 1
ALARM ALARM
------------------------------------- ---------- ---------- ---------

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
Example 3
This example shows the properties associated with the ROUTING_UNKNOWN statistic for site 1:
disp_stat_prop routing_unknown 1
Where: is:
routing_unknown meas_type
1 location
System response
STATISTIC: ROUTING_UNKNOWN SITE: 1
TYPE: OTHER OBJECT: COUNTER
ALARM ALARM
------------------------------------- ---------- ---------- ---------
N/A ENABLED WARNING 2147836

SITE: 0 CELL #: LAC = f222h CI = 8880h
MEAS_TYPE : CHANNELS_DISABLED
Gauge Value: 5 Max.: 5
Example 4
This example displays the properties associated with the BUSY_TCH statistic for
cell number 5 4 3 2 1 61698 34776.
4-18 68P02901W23-Q
Technical Description: BSS Command Reference disp_stat_prop
disp_stat_prop busy_tch cell_number= 5 4 3 2 1 61698 34776
Where: is:
busy_tch meas_type
5 4 3 2 1 61698 34776 cell_desc
System response
STATISTIC: BUSY_TCH SITE: 1
TYPE: PER CELL OBJECT: DISTRIB
CELL# MODE BIN# MIN MAX

----------------------------------- -------- ---- ---------- -----------
543 21 61698 (f10h) 34776 (87d8h) ENABLED 0 0 1

1 2 3
2 4 5
3 6 7
4 8 9
5 10 11
6 12 13
7 14 15
8 16 147174832
9 214174833 2141749879
Example 5
This example displays the properties associated with the TCH_CONGESTION statistic for
cell number 5 4 3 2 1 61698 34776 at site 1:
disp_stat_prop tch_congestion cell_number= 5 4 3 2 1 61698 34776
Where: is:
tch_congestion meas_type
5 4 3 2 1 61698 34776 cell_desc
System response
STATISTIC: TCH_CONGESTION SITE: 1
TYPE: PER CELL OBJECT: TOTAL TIME
CELL # MODE
---------------------------------------- -------
5 4 3 2 1 61698 (f10h) 34776 (87d8h) ENABLED
Example 6
This example displays the properties associated with the OUT_HO_CAUSE_ATMPT
statistic for cell number 5 4 3 2 1 61698 34776:
68P02901W23-Q 4-19
disp_stat_prop out_ho_cause_atmpt cell_number= 1 5 4 3 2 1 61698 34776
Where: is:
5 4 3 2 1 61698 34776 cell_desc
System response
STATISTIC: OUT_HO_CAUSE_ATMPT SITE: 1
BIN# CAUSE
----- ------
0 Uplink Quality
1 Uplink Level
2 Downlink Quality
3 Downlink Level
4 Distance
5 Uplink Interference
6 Downlink Interference
7 Power Budget
8 Congestion
9 Other Cause
CELL# MODE
--------------------------- -------
61698 (f102h) 34776 (87d8h) ENABLED
61698 (f102h) 34777 (87d9h) ENABLED
61698 (f102h) 34778 (87dah) ENABLED
61698 (f102h) 34779 (87dbh) ENABLED
61698 (f102h) 34780 (87dch) ENABLED
References
Related commands
"disp_element" on page 2-232, "stat_mode" on page 4-27, "disp_enable_stat" on page 4-10,
"disp_interval" on page 4-14, "disp_stats" on page 4-21.
4-20 68P02901W23-Q
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
The GPRS feature must be unrestricted to display PCU statistics.
The EGPRS feature must be unrestricted to display EGPRS
Format
Syntax
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
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 neighbour cell statistic.
68P02901W23-Q 4-21
disp_stats Chapter 4: Statistics commands
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 in seven parameter format:
disp_stats 5 out_ho_cause_atmpt cell_number= 5 4 3 2 1 61986 34944
Where: is:
5 interval
5 4 3 2 1 61986 34944 cell_desc
disp_cell_status 543 21 61986 34944
System response
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
4-22 68P02901W23-Q
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
MEAS_TYPE : EGPRS_64K_NOT_AVAIL
Counter : 100
Example 3
The following example is a weighted distribution statistic that requires a cell_desc. Values
represented in the bins are time values expressed in milliseconds:
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
System response
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
68P02901W23-Q 4-23
Where: is:
available_tch meas_type
5 4 3 2 1 61986 34944 cell_desc
System response
MEAS_TYPE : AVAILABLE_TCH
Gauge Value : 5 Max. : 5
Example 5
The following example is a normal distribution statistic that requires a cell_desc
because it is a per 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 timeslots in all the existing carriers is displayed (in ascending order) in the system response:
System response
SITE:1 CELL #:LAC = 0001h CI = 0006h
RTF ID: 1 1

TIMESLOT: 1 RTF ID = 1 1
MEAS_TYPE : BER
Bin : 0 0 0 0 0 0 0 0 0 0

TIMESLOT: 5 RTF ID = 1 1
MEAS_TYPE : BER
Bin : 0 0 0 0 0 0 0 0 0 0
Example 6
The following example displays the MS_ACCESS_BY_TYPE counter array statistic when
the BSS does not support the PCS1900 frequency type:
4-24 68P02901W23-Q
disp_stats 1 ms_access_by_type cell_number= 5 4 3 2 1 61986 34944
Where: is:
1 interval
ms_access_by_type meas_type
5 4 3 2 1 61986 34944 cell_desc
System response
SITE :0 CELL #:LAC=0001h CI=0004h
MEAS_TYPE : MS_ACCESS_BY_TYPE
Total Count : 0
PGSM only : 0
DCS1800 only : 0
PCS1900 only : 0
PGSM and EGSM : 0
PGSM and DCS1800 : 0
PGSM, EGSM, and DCS1800 : 0
PGSM and PCS1900 : 0
PGSM, EGSM, and PCS1900 : 0
The system does not display the lines that contain “PCS1900" if these frequencies
are not allowed at the BSS.
Example 7
The following example displays a related statistic when CS-3, CS-4, and 32 kbit/s GPRS TRAU are enabled:
disp_stats 5 gprs_32k_channels_switched cell_number= 1 2 3 4 5 6 7
Where: is:
1 interval
gprs_32k_chan- meas_type
nels_switched
1234567 cell_desc
System response
SITE : 5 CELL #: LAC = 6 CI = 7
MEAS_TYPE : GPRS_32K_CHANNELS_SWITCHED
GPRS_CHANNELS_SWITCHED: 13
Example 8
Displaying statistics for PRP_LOAD also displays the statistics information from
the two other PCUs equipped at the BSC:
68P02901W23-Q 4-25
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
Bin : 0 0 0 0 0 0 0 0 0 0

Bin : 0 0 0 0 0 0 0 0 0 0

Bin : 0 0 0 0 0 0 0 0 0 0
References
Related commands
"disp_element" on page 2-232, "stat_mode" on page 4-27, "disp_enable_stat" on
page 4-10, "disp_interval" on page 4-14.
4-26 68P02901W23-Q
Technical Description: BSS Command Reference stat_mode
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.
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 2
Prerequisites The GPRS feature must be unrestricted to enable GPRS associated
statistics.
The EGPRS feature must be unrestricted to enable EGPRS
Format
Syntax
stat_mode <meas_type> <mode> [<location>] [<cell_desc>]
stat_mode <meas_type> <mode> all
stat_mode <meas_type> <mode> <location> all
68P02901W23-Q 4-27
stat_mode Chapter 4: Statistics commands
Input parameters
meas_type
mode
Specifies the mode of the statistic:
on Enable
off Disable
location
0 or bsc BSC
1 to 120 BTS
all All sites
cell_desc
The GSM Cell ID of the cell to be modified, preceded by cell_number=.
Examples
Example 1
This example enables the TOTAL_CALLS statistic for cell number 5 4 3 2 1 61698 34776 at site 1:
4-28 68P02901W23-Q
Technical Description: BSS Command Reference stat_mode
stat_mode total_calls on 1 cell_number= 5 4 3 2 1 61698 34776
Where: is:
on set the enable type
1 location
5 4 3 2 1 61698 34776 cell_desc
System response
COMMAND ACCEPTED
Example 2
This example disables the TOTAL_CALLS statistic for all cells at site 1:
stat_mode total_calls off 1 all
Where: is:
off set the enable type
1 location
System response
COMMAND ACCEPTED
Example 3
This example enables the GPRS_32K_CHANNELS_SWITCHED statistic for the cell at site 1:
stat_mode gprs_32k_channels_switched on 1 cell_number=1 2 3 4 5 6 7
Where: is:
gprs_32k_channels_switched meas_type
1 location
1234567 cell_desc
System response
COMMAND ACCEPTED
Example 4
This example attempts to enable the EGPRS_DL_ASGN_PCCCH statistic for the cell
at site 1 when EGPRS is restricted:
68P02901W23-Q 4-29
stat_mode Chapter 4: Statistics commands
stat_mode egprs_dl_asgn_pccch on 1 cell_number=1 2 3 4 5 6 7
Where: is:
egprs_dl_asgn_pccch meas_type
1 location
1234567 cell_desc
System response
COMMAND REJECTED: Received a request to modify a restricted optional feature.
References
Related commands
"disp_element" on page 2-232, "disp_enable_stat" on page 4-10, "disp_interval" on
4-30 68P02901W23-Q
Chapter
5
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-Q 5-1
CM database parameters presentation Chapter 5: CM database parameters
CM database parameters presentation
The layout of the CM database parameters reference information is explained below.
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 via the OMC-R GUI (Graphics User Interface). If a
value is not supported via 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 numbers 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. These dependencies must be considered when changes are made to the parameter.
Operator actions
The specific actions required when changing Type B parameters are listed, including
any precautions that are appropriate.
5-2 68P02901W23-Q
Technical Description: BSS Command Reference CM database parameters presentation
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_cell 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 then 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.
References
The following information is given when required.
68P02901W23-Q 5-3
CM database parameters presentation Chapter 5: CM database parameters
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.
5-4 68P02901W23-Q
Technical Description: BSS Command Reference aci_error_clr_thresh
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)
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 might 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
68P02901W23-Q 5-5
aci_error_gen_thresh Chapter 5: CM database parameters
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).
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

chg_element aci_error_gen_thresh <value> 0

disp_element aci_error_gen_thresh 0
Values
Value type Integer

Default value 6
5-6 68P02901W23-Q
Technical Description: BSS Command Reference aci_error_inc
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.
This parameter applies only to the BSC.
Syntax

chg_element aci_error_inc <value> 0

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 restricted
1 If ECERM feature is not restricted
68P02901W23-Q 5-7
adap_ho_alt_trigger_rxqual Chapter 5: CM database parameters
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.
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>

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
5-8 68P02901W23-Q
Technical Description: BSS Command Reference adap_ho_pbgt
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 neighbour".
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.
Dependencies None
Syntax

chg_element adap_ho_pbgt <value> <location> <cell_desc>
chg_cell_element adap_ho_pbgt <value> <cell_desc>

disp_element adap_ho_pbgt <location> <cell_desc>
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.
68P02901W23-Q 5-9
adap_ho_pbgt Chapter 5: CM database parameters
2 Enables adaptive power budget handovers at the location using

per neighbor cumulative area.
Default value 0
5-10 68P02901W23-Q
Technical Description: BSS Command Reference adap_ho_rxlev
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.
Dependencies None
Syntax

chg_element adap_ho_rxlev <value> <location> <cell_desc>
chg_cell_element adap_ho_rxlev <value> <cell_desc>

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
68P02901W23-Q 5-11
adap_ho_rxqual Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_element adap_ho_rxqual <value> <location> <cell_desc>
chg_cell_element adap_ho_rxqual <value> <cell_desc>

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
5-12 68P02901W23-Q
Technical Description: BSS Command Reference adap_trigger_hop_rxqual_dl
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.
Dependencies None
Syntax

chg_element adap_trigger_hop_rxqual_dl <value> <location> <cell_desc>
chg_cell_element adap_trigger_hop_rxqual_dl <value> <cell_desc>

disp_element adap_trigger_hop_rxqual_dl <location> <cell_desc>
Values
Value type Integer

Default value 0
68P02901W23-Q 5-13
adap_trigger_hop_rxqual_ul Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_element adap_trigger_hop_rxqual_ul <value> <location> <cell_desc>
chg_cell_element adap_trigger_hop_rxqual_ul <value> <cell_desc>

disp_element adap_trigger_hop_rxqual_ul <location> <cell_desc>
Values
Value type Integer

Default value 0
5-14 68P02901W23-Q
Technical Description: BSS Command Reference adap_trigger_pbgt
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.
Dependencies None
Syntax

chg_element adap_trigger_pbgt <value> <location> <cell_desc>
chg_cell_element adap_trigger_pbgt <value> <cell_desc>

disp_element adap_trigger_pbgt <location> <cell_desc>
Values
Value type Integer

Default value 0
68P02901W23-Q 5-15
adap_trigger_pbgt_nbr Chapter 5: CM database parameters
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 is set by adap_trigger_pbgt_nbr is exceeded, the system
triggers a handover to a better cell.
Dependencies This parameter is invalid when ba_type is ba_bcch or ba_gprs.
Syntax

modify_neighbor <src_cell_id> <neighbor_cell_id> adap_trig-
ger_pbgt_nbr <value>

disp_neighbor <src_cell_id> [<neighbor_cell_id>|all]
Values
Value type Integer

Default value 40 (the value of 40 corresponds to a hreqave of 8 and a handover margin of 5)
5-16 68P02901W23-Q
Technical Description: BSS Command Reference adap_trigger_rxlev_dl
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.
Dependencies None
Syntax

chg_element adap_trigger_rxlev_dl <value> <location> <cell_desc>
chg_cell_element adap_trigger_rxlev_dl <value> <cell_desc>

disp_element adap_trigger_rxlev_dl <location> <cell_desc>
Values
Value type Integer

Default value 0
68P02901W23-Q 5-17
adap_trigger_rxlev_ul Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_element adap_trigger_rxlev_ul <value> <location> <cell_desc>
chg_cell_element adap_trigger_rxlev_ul <value> <cell_desc>

disp_element adap_trigger_rxlev_ul <location> <cell_desc>
Values
Value type Integer

Default value 0
5-18 68P02901W23-Q
Technical Description: BSS Command Reference adap_trigger_rxqual_dl
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.
Dependencies None
Syntax

chg_element adap_trigger_rxqual_dl <value> <location> <cell_desc>
chg_cell_element adap_trigger_rxqual_dl <value> <cell_desc>

disp_element adap_trigger_rxqual_dl <location> <cell_desc>
Values
Value type Integer

Default value 0
68P02901W23-Q 5-19
adap_trigger_rxqual_ul Chapter 5: CM database parameters
adap_trigger_rxqual_ul
Description
The adap_trigger_rxqual_ul parameter specifies the cumulative trigger level for

adaptive rxqual uplink handovers.
When the threshold set by this parameter is exceeded, the system performs an uplink quality handover.
Dependencies None
Syntax

chg_element adap_trigger_rxqual_ul <value> <location> <cell_desc>
chg_cell_element adap_trigger_rxqual_ul <value> <cell_desc>

disp_element adap_trigger_rxqual_ul <location> <cell_desc>
Values
Value type Integer

Default value 0
5-20 68P02901W23-Q
Technical Description: BSS Command Reference allow_8k_trau
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).
Dependencies The AMR Enhanced Capability feature {22064) and/or GSM Half
Rate feature must be unrestricted.
The half_rate_enabled parameter must be enabled.
The BTS must be AMR/GSM Half Rate capable.
For a TCU-A or TCU-B radio platform, the {22064} AMR
Enhanced Capacity feature and TCU-A/TCU-B feature must be
unrestricted.
The 7.95 kbit/s codec mode must not be part of the AMR Half-Rate
Active Codec Set.
Syntax

equip <site_id> RTF
After entering this command, the user is prompted to enable or disable the
allow_8k_trau parameter (and other RTF parameters).

disp_equipment
68P02901W23-Q 5-21
allow_8k_trau Chapter 5: CM database parameters
Values
Value type Boolean

Valid range no or yes
no Disabled
yes Enabled
Default value yes
5-22 68P02901W23-Q
Technical Description: BSS Command Reference alt_qual_proc
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 type of values and the range of values of six
parameters are determined by the value assigned to the alt_qual_proc parameter.
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. The command is abandoned if an invalid value is entered.
{22064}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.
Table 5-1 lists the range of values and defaults for the dependent cell parameters if a value
of 0 is entered for the alt_qual_proc parameter.
Table 5-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
l_rxqual_dl_p_data 0 to 1810 0
l_rxqual_ul_p_data 0 to 1810 0
68P02901W23-Q 5-23
alt_qual_proc Chapter 5: CM database parameters
Table 5-1 alt_qual_proc=0 parameter values (Continued)

{22064}
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
{22064}
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 5-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 5-2 alt_qual_proc=1 parameter values

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
5-24 68P02901W23-Q
Technical Description: BSS Command Reference alt_qual_proc
Table 5-2 alt_qual_proc=1 parameter values (Continued)

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
{22064}
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 0
l_rxqual_ul_h_hopping_amr_fr 0 to 7 0
l_rxqual_dl_p_hopping_amr_fr 0 to 7 0
l_rxqual_ul_p_hopping_amr_fr 0 to 7 0
{22064}
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)

Cell numbers required Yes
Dependencies 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.
Operator actions 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.
68P02901W23-Q 5-25
alt_qual_proc Chapter 5: CM database parameters
Syntax

add_cell <gsm_cell_id> <location>
chg_cell_element alt_qual_proc <value> <cell_desc>

disp_cell <cell_desc> full
disp_element alt_qual_proc <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 BER units
1 Qband units
Default value 0
5-26 68P02901W23-Q
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.
Cell numbers 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.
Syntax
Add/Change command strings

chg_element amr_bss_full_rate_enabled <value> 0

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-Q 5-27
amr_bss_half_rate_enabled Chapter 5: 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.
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.
Syntax

chg_element amr_bss_half_rate_enabled <value> 0

disp_element amr_bss_half_rate_enabled 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-28 68P02901W23-Q
Technical Description: BSS Command Reference amr_dl_la_mode_chg_min
amr_dl_la_mode_chg_min
Description
The amr_dl_la_mode_chg_min parameter specifies the minimum time periods between initiating
changes in the downlink codec mode. When the parameter is set to a value greater than the inherent
delay in the adaptation process, a wait period is added to slow down the adaptation.
Syntax

chg_element amr_dl_la_mode_chg_min <value> <location> <cell_desc>

disp_element amr_dl_la_mode_chg_min <location> <cell_desc>
Values
Value type Integer (ms)

Default value 100
68P02901W23-Q 5-29
amr_dl_thresh_adjust Chapter 5: CM database parameters
amr_dl_thresh_adjust
Description
The amr_dl_thresh_adjust parameter specifies the compensation for the Carrier

to Interference (C/I) adaptation thresholds.
Syntax

chg_element amr_dl_thresh_adjust <value> <location>

disp_element amr_dl_thresh_adjust <location>
Values
Value type dB
Valid range 1 to 7
Default value 3
5-30 68P02901W23-Q
Technical Description: BSS Command Reference amr_fr_dl_la_enabled
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.
Syntax

chg_element amr_fr_dl_la_enabled <value> <location> <cell_desc>
chg_cell_element amr_fr_dl_la_enabled <value> <cell_desc>

disp_cell <cell_desc> "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
68P02901W23-Q 5-31
amr_fr_ul_la_enabled Chapter 5: CM database parameters
amr_fr_ul_la_enabled
Description
The amr_fr_ul_la_enabled parameter enables or disables Full Rate Uplink Codec

Syntax

chg_element amr_fr_ul_la_enabled <value> <location> <cell_desc>
chg_cell_element amr_fr_ul_la_enabled <value> <cell_desc>

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
5-32 68P02901W23-Q
Technical Description: BSS Command Reference amr_full_rate_enabled
amr_full_rate_enabled
Description
The amr_full_rate_enabled parameter enables or disables the AMR Full Rate at a cell.
This parameter does not apply to a remote transcorder (RXCDR).
This parameter does not apply to a standalone BSC site (that is, a
site without a colocated BTS).
Syntax

chg_element amr_full_rate_enabled <value> <location> <cell_desc>
chg_cell_element amr_full_rate_enabled <value> <cell_desc>
The chg_cell_element command can not be used to change this parameter

unless the site is an AMR-capable BTS.

disp_element amr_full_rate_enabled <location> <cell_desc>
The copy_cell command sets this parameter to disabled.
68P02901W23-Q 5-33
amr_full_rate_enabled Chapter 5: CM database parameters
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-34 68P02901W23-Q
Technical Description: BSS Command Reference amr_hr_dl_la_enabled
amr_hr_dl_la_enabled
Description
The amr_hr_dl_la_enabled parameter enables or disables Half Rate Downlink Codec

Syntax

chg_element amr_hr_dl_la_enabled <value> <location> <cell_desc>
chg_cell_element amr_hr_dl_la_enabled <value> <cell_desc>

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
68P02901W23-Q 5-35
amr_hr_ul_la_enabled Chapter 5: CM database parameters
amr_hr_ul_la_enabled
Description
The amr_hr_ul_la_enabled parameter enables or disables Half Rate Uplink Codec

Syntax

chg_element amr_hr_ul_la_enabled <value> <location> <cell_desc>
chg_cell_element amr_hr_ul_la_enabled <value> <cell_desc>

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
5-36 68P02901W23-Q
Technical Description: BSS Command Reference amr_ms_high_cmr
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.
Syntax
Add/Change command string

chg_element amr_ms_high_cmr <value> <location>

disp_element amr_ms_high_cmr <location>
Values
Value type Percentages

Default value 95
68P02901W23-Q 5-37
amr_ms_high_rxqual Chapter 5: CM database parameters
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.
Syntax

chg_element amr_ms_high_rxqual <value> <location>

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)
5-38 68P02901W23-Q
Technical Description: BSS Command Reference amr_ms_low_cmr
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.
Syntax

chg_element amr_ms_low_cmr <value> <location>

disp_element amr_ms_low_cmr <location>
Values
Value type Percentages

Default value 99
68P02901W23-Q 5-39
amr_ms_low_rxqual Chapter 5: CM database parameters
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.
Syntax

chg_element amr_ms_low_rxqual <value> <location>

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
5-40 68P02901W23-Q
Technical Description: BSS Command Reference amr_ms_monitor_period
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.
Syntax

chg_element amr_ms_monitor_period <value> <location>

disp_element amr_ms_monitor_period <location>
Values
Value type SACCH periods

Valid range 10 to 1200 Disable parameter
Default value 40
68P02901W23-Q 5-41
attach_detach Chapter 5: 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.
Dependencies None
Syntax

chg_element attach_detach <value> <location> <cell_desc>
chg_cell_element attach_detach <value> <cell_desc>

disp_cell <cell_desc> ["full]
disp_element attach_detach <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-42 68P02901W23-Q
Technical Description: BSS Command Reference attach_detach
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-Q 5-43
auto_rf_loss_trace Chapter 5: 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 measurement report is generated by the RF loss trace.
**** 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 ****
Type A (no operator action)

Dependencies The auto_rf_loss_trace parameter is valid for any GPROC except
the CSFP.
5-44 68P02901W23-Q
Technical Description: BSS Command Reference auto_rf_loss_trace
Syntax

chg_element auto_rf_loss_trace <value> <location> <cell_desc>
chg_cell_element auto_rf_loss_trace <value> <cell_desc>

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-Q 5-45
ba_alloc_proc Chapter 5: 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.
Dependencies None
Syntax

chg_element ba_alloc_proc <value> <location> <cell_desc>
chg_cell_element ba_alloc_proc <value> <cell_desc>

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
5-46 68P02901W23-Q
Technical Description: BSS Command Reference ba_alloc_proc
References
GSM parameter None

68P02901W23-Q 5-47
band_preference Chapter 5: CM database parameters
band_preference
Description
The band_preference parameter displays the frequency bands that the cell prefers to use for handovers
and specifies the destination frequency band for inter-cell handovers.
Type A (No operator action)
Dependencies The Multiband Inter-cell handover feature must be enabled.
This parameter has no meaning if band_preference_mode = 0 for
this cell.
Syntax

chg_element band_preference <value> <location> <cell_desc>
chg_cell_element band_preference <value> <cell_desc>

disp_element band_preference <location> <cell_desc>
Values
Value type Select integer

Valid range 1 (PGSM)
2 (EGSM)
4 (DCS1800)
8 (PCS1900)
Default value The frequency type of the cell (as set by frequency_type).
5-48 68P02901W23-Q
Technical Description: BSS Command Reference band_preference
References
GSM parameter None

68P02901W23-Q 5-49
band_preference_mode Chapter 5: 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.
Dependencies The Multiband Inter-cell handover feature must be unrestricted.
Syntax

chg_element band_preference_mode <value> <location> <cell_desc>
chg_cell_element band_preference_mode <value> <cell_desc>

disp_element band_preference_mode <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 6 The BSS attempts to hand a Multiband MS over to the strongest
neighbour that the MS reported when a handover is required for
normal radio resource reasons.
5-50 68P02901W23-Q
Technical Description: BSS Command Reference band_preference_mode
1 The BSS attempts to assign a Multiband MS to the strongest

preferred band neighbour that the MS reported at the time of
SDCCH to TCH assignment.
If the BSS cannot assign a preferred band TCH the BSS will not try
to direct this MS to the preferred band for the life of the current call
connection. The BSS always hands the MS over to the strongest
MS-reported neighbour when a handover is required for normal
radio resource reasons.
Mode 1 is restricted to mobiles that are fast enough to provide
guilty measurement reports.
2 The BSS attempts to hand a Multiband MS over to the strongest
preferred band neighbour that the MS reported when a handover is
required for normal radio resource reasons.
The BSS places preferred band neighbours ahead of non-preferred
band neighbours in order to attempt to assign a channel from the
preferred band for the MS.
preferred-band neighbour that the MS reported at the time of
SDCCH to TCH assignment, as well as attempt to hand the MS
over to the strongest preferred-band neighbour that the MS reported
when a handover is required for normal radio resource reasons.
This value combines the functions of values 1 and 2.
4 The BSS continually attempts to hand a Multiband MS over to a
preferred band TCH immediately after initial assignment.
The BSS will not attempt to allocate a TCH in the preferred band
for this MS at the time of SDCCH-to-TCH assignment. The
BSS will enter a mode of continually monitoring for qualified
preferred-band neighbours reported by the MS in order to hand the
MS over. The BSS will stay in this mode until it finds a neighbour
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
neighbour reported by the MS.
preferred-band neighbour 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 neighbours
reported by the MS in order to hand over the MS. The BSS will stay
in this mode until it finds a neighbour 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 neighbour reported by the MS.
This value combines the functions of values 1, 2, and 4.
68P02901W23-Q 5-51
band_preference_mode Chapter 5: CM database parameters

preferred band neighbour 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 neighbours
reported by the MS in order to hand over the MS. The BSS will stay
in this mode until it finds a neighbour 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 neighbour 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 only
triggered when the cell is congested.
Default value 0
References
GSM parameter None

5-52 68P02901W23-Q
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 would be the
exponent value of 103, indicating 1 bit error in 1000 bits.
Dependencies None
Syntax

chg_element ber_loss_daily <value> <location>

disp_element ber_loss_daily <location>
Values
Value type Integer

Valid range 3 to 6
Default value 5
References
GSM parameter None

68P02901W23-Q 5-53
ber_loss_hourly Chapter 5: 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 would be 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.
Dependencies None
Syntax

chg_element ber_loss_hourly <value> <location>

disp_element ber_loss_hourly <location>
Values
Value type Integer

Valid range 3 to 6
Default value 4
References
GSM parameter None

5-54 68P02901W23-Q
Technical Description: BSS Command Reference bounce_protect_margin
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.
Dependencies After a 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

chg_element bounce_protect_margin <value> <location> <cell_desc>
chg_cell_element bounce_protect_margin <value> <cell_desc>

disp_element bounce_protect_margin <location> <cell_desc>
Values
Value type Integer (decibels)

Default value 0
68P02901W23-Q 5-55
bs_ag_blks_res Chapter 5: CM database parameters
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 paging blocks available are reduced by the number of blocks reserved for access grant messages.
The choice of value is determined by the ratio of MS-originated calls to MS-terminated calls.
PCH and AGCH share the same TDMA mapping when combined onto a basic physical
channel. Channels are shared on a block by block basis.
Dependencies ccch_conf
Operator actions Reset the site after changing the bs_ag_blks_res value.
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).
Syntax

chg_element bs_ag_blks_res <value> <location> <cell_desc>
chg_cell_element bs_ag_blks_res <value> <cell_desc>
A site reset is required when the value of bs_ag_blks_res is changed. Resetting the site
generates several alarms. However, these alarms are blocked by the system.
5-56 68P02901W23-Q
Technical Description: BSS Command Reference bs_ag_blks_res

disp_element bs_ag_blks_res <location> <cell_desc>
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 01
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
68P02901W23-Q 5-57
bs_pa_mfrms Chapter 5: CM database parameters
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).
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

chg_element bs_pa_mfrms <value> <location> <cell_desc>
chg_cell_element bs_pa_mfrms <value> <cell_desc>
A site reset is required when the value of bs_pa_mfrms is changed. Although resetting the
site generates several alarms, these alarms are blocked by the system.

disp_element bs_pa_mfrms <location> <cell_desc>
5-58 68P02901W23-Q
Technical Description: BSS Command Reference bs_pa_mfrms
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 signalling failure
12.20 - 5.2.8.8 - configCCH
68P02901W23-Q 5-59
bs_pag_blks_res Chapter 5: CM database parameters
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.
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

chg_element bs_pag_blks_res <value> <location> <cell_desc>
chg_cell_element bs_pag_blks_res <value> <cell_desc>

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
5-60 68P02901W23-Q
Technical Description: BSS Command Reference bs_pag_blks_res
The sum of the values set for this parameter and for bs_pbcch_blks must be between 1 and 11.
68P02901W23-Q 5-61
bs_pbcch_blks Chapter 5: CM database parameters
bs_pbcch_blks
Description
The bs_pbcch_blks specifies the number of Packet Broadcast Control Channel (PBCCH)
The sum of the values set for this parameter and for
bs_pag_blks_res must be between 1 and 11.
This parameter must be set to 1 or 2 when psi1_repeat_period is 1.
Syntax

chg_element bs_pbcch_blks <value> <location> <cell_desc>
chg_cell_element bs_pbcch_blks <value> <cell_desc>

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
5-62 68P02901W23-Q
Technical Description: BSS Command Reference bs_pbcch_blks
The sum of the values set for this parameter and for bs_pag_blks_res must be between 1 and 11.
68P02901W23-Q 5-63
bs_pcc_chans Chapter 5: CM database parameters
bs_pcc_chans
Description
The bs_pcc_chans specifies the number of Packet Common Control Channel (PC-
CCH) timeslots on a per cell basis.
The value indicates the number of physical channels carrying PCCCHs including
the physical channel carrying the PBCCH.
Syntax

chg_element bs_pcc_chans <value> <location> <cell_desc>
chg_cell_element bs_pcc_chans <value> <cell_desc>

disp_element bs_pcc_chans <location> <cell_desc>
Values
Value type Integer

Valid range 1 Number of physical channels with PCCCHs
Default value 1
5-64 68P02901W23-Q
Technical Description: BSS Command Reference bs_prach_blks
bs_prach_blks
Description
The bs_prach_blks specifies the number of Packet Random Access Channel (PRACH)
Syntax

chg_element bs_prach_blks <value> <location> <cell_desc>
chg_cell_element bs_prach_blks <value> <cell_desc>

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
68P02901W23-Q 5-65
bsc_type Chapter 5: CM database parameters
bsc_type
Description
The bsc_type parameter specifies the BSC configuration type.

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

chg_element bsc_type <value> 0

disp_element bsc_type 0
Values
Value type Integer

Valid range 0 to 3
5-66 68P02901W23-Q
Technical Description: BSS Command Reference bsc_type
0 Non Abis, Type 0

1 Non Abis, Type 1
2 Non Abis, Type 2
3 Abis, Type 0
Default value None
References
GSM parameter None

68P02901W23-Q 5-67
bsic Chapter 5: CM database parameters
bsic
Description
The bsic parameter specifies the Base Station Identity Code (BSIC).
The BSIC is a local colour code that allows an MS to distinguish between different neighbouring
base stations. The BSIC is encoded on the Synchronization Channel.
The size of the BSIC is one octet made up of two values:
• Network Colour Code (NCC). The NCC is three bits and is the same as the
Public land mobile network (PLMN) Colour Code.
• Base station Colour 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 5-3 and Table 5-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
neighbour cells do not share the same BSIC and the same BCCH RF carrier.
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
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)?
5-68 68P02901W23-Q
Technical Description: BSS Command Reference bsic
Syntax

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>
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 as-
sociated with this cell. Are you sure (y=yes, n=no)?
A “Y" answer resets all the DRIs.

disp_element bsic <location> <cell_desc>
disp_neighbor <src_gsm_cell_id>
Values
Value type Integer

Valid range Hex = 00h to 3Fh (See Table 5-3)
Decimal = 0 to 63 (See Table 5-4)
Default value None
Table 5-3 lists the hexadecimal values for the base station identity codes.
68P02901W23-Q 5-69
bsic Chapter 5: CM database parameters
Table 5-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 5-4 lists the decimal values for the base station identity codes.
Table 5-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
5-70 68P02901W23-Q
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.
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

chg_element bss_egsm_alm_allowed <value> 0

disp_element bss_egsm_alm_allowed 0
Values
Value type Boolean

Valid range 0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-71
bss_msc_overload_allowed Chapter 5: CM database parameters
bss_msc_overload_allowed
Description
The bss_msc_overload_allowed parameter determines whether or not a MSC overload is allowed. When this
parameter is enabled, the BSS bars one access class at a time if it receives an OVERLOAD message.
Dependencies None
Syntax

chg_element bss_msc_overload_allowed <value>

disp_element bss_msc_overload_allowed
Values
Value type Boolean

Valid range 0 Disabled
1 Enabled
Default value 0
5-72 68P02901W23-Q
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.
Dependencies This parameter can be used only if the GPRS feature is unrestricted.
BSS software processes using this parameter are not notified when the change is made.
Syntax

chg_element bssgp_block_retries <value> <location>

disp_element bssgp_block_retries <location>
Values
Value type Integer (retries)

Valid range 1 to 3
Default value 3
68P02901W23-Q 5-73
bssgp_cbl_bit Chapter 5: 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.
This parameter can be set in or out of SYSGEN mode.
Operator actions: None
This is a Motorola proprietary parameter.

BSS software processes using this parameter are notified immediately the change is made.
Syntax

chg_element bssgp_cbl_bit <value> <location>

disp_element bssgp_cbl_bit <location>
Values
Value type Boolean

Valid range 0 or CBL procedures not supported (CBL bit not set)
101 CBL procedures supported (CBL bit set)
Default value 0
5-74 68P02901W23-Q
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.
Dependencies The GPRS feature must be unrestricted.
Operator actions None
Syntax

chg_element bssgp_racap_retries <value> <location>

disp_element bssgp_racap_retries <location>
Values

Valid range 1 to 3
Default value 3
68P02901W23-Q 5-75
bssgp_reset_retries Chapter 5: 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.
Syntax

chg_element bssgp_reset_retries <value> <location>

disp_element bssgp_reset_retries <location>
Values

Valid range 1 to 3
Default value 3
5-76 68P02901W23-Q
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.
Syntax

chg_element bssgp_unblock_retries <value> <location>

disp_element bssgp_unblock_retries <location>
Values

Valid range 1 to 3
Default value 3
68P02901W23-Q 5-77
bts_p_con_ack Chapter 5: 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
acknowledgements 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.
Dependencies decision_alg_type = 1
Syntax

chg_element bts_p_con_ack <value> <location> <cell_desc>
chg_cell_element bts_p_con_ack <value> <cell_desc>

disp_element bts_p_con_ack <location> <cell_desc>
Values
Value type Integer (1 Step = 2 multiframes)

Valid range 0 to 31
5-78 68P02901W23-Q
Technical Description: BSS Command Reference bts_p_con_ack
0 0 SACCH multiframes
... ...
Default value 1 (equals 2 SACCH multiframes)
References
GSM parameter P_CON_ACK

GSM technical specification None
68P02901W23-Q 5-79
bts_p_con_interval Chapter 5: 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.

Dependencies This parameter will 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
5-80 68P02901W23-Q
Technical Description: BSS Command Reference bts_p_con_interval
Syntax

chg_element bts_p_con_interval <value> <location> <cell_desc>
chg_cell_element bts_p_con_interval <value> <cell_desc>

disp_element bts_p_con_interval <location> <cell_desc>
Values
Value type Integer (1 Step = 2 multiframes)

Valid range 0 to 31
... ...
Default value 2 (equals 4 SACCH multiframes)
References
GSM parameter P_CON_INTERVAL

GSM technical specification 5.08 - Appendix A - Table 1
68P02901W23-Q 5-81
bts_power_control_allowed Chapter 5: 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.
Dependencies None
Syntax

chg_element bts_power_control_allowed <value> <location> <cell_desc>
chg_cell_element bts_power_control_allowed <value> <cell_desc>

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
5-82 68P02901W23-Q
Technical Description: BSS Command Reference bts_power_control_allowed
The value 0 is the only valid value at M-Cellcity sites; both 0 and 1 values are
permitted at Horizonmicro2 and Horizoncompact2 sites.
References
GSM parameter EN_BS_PC

GSM technical specification 5.05 - 4.1.2
68P02901W23-Q 5-83
bts_txpwr_max_inner Chapter 5: 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.
Dependencies This parameter may be modified only when the Dual Band Cells
feature is unrestricted (inner_zone_alg set to 3).
Syntax

chg_element bts_txpwr_max_inner <value> <location> <cell_desc>
chg_cell_element bts_txpwr_max_inner <value> <cell_desc>

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
5-84 68P02901W23-Q
Technical Description: BSS Command Reference bts_txpwr_max_inner
Refer to Table 5-5, Table 5-6, Table 5-7, Table 5-8, and Table 5-9 for additional
information about the values for this parameter.
Table 5-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.
Table 5-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
Table 5-6 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 5-6 also specifies the types of combing in used: none, external, internal, and both internal
and external. The combining types are defined as follows:
68P02901W23-Q 5-85
• 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 via 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 prior to leaving the XCVR. Hence the
power figure for internal combining represents two carriers at this transmit power for a CTU2 in
DD-DCM. Note 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 would allow two CTU2 in DD-DCM to be combined to create a four-carrier sector.
Table 5-6 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 5-7 lists the values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro,
M-Cellcity, M-Cellarena and M-Cellarenamacro sites.
Table 5-7 Values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro,etc. sites
PGSM and EGSM DCS1800 and PCS1900

Valid Input M-Cellarenamacrovalues
M-Cellmicro values M-Cellmicro values
0 31 dBm 30 dBm 40 dBm
Table 5-8 lists the values for DCS1800 and M-Cellaccess sites.
5-86 68P02901W23-Q
Technical Description: BSS Command Reference bts_txpwr_max_inner
Table 5-8 Values for DCS1800 and M-Cellaccess, sites
PGSM, EGSM and M-Cellaccess

Valid Input DCS1800 M-Cellaccess values
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 5-9
lists sample output power, measured at the top of the cabinet, of some Motorola cabinets
with different combinations of RCUs and combiners.
Table 5-9 Sample output power
Type of combining Number of radios Output power (as calibrated)

ExCell 4
hybrid 2 20W [Symbol_approximate]
43.01 dBm
cavity (1 cabinet) 4 25W [Symbol_approximate]
43.98 dBm
BTS4, BTS5, BTS6
43.01 dBm
43.98 dBm
cavity (2 neighbouring cabinets) 10 13W [Symbol_approximate]
41.14 dBm
M-Cell2 or M-Cell6 6
hybrid 2 17.5W [Symbol_approximate]
43.01 dBm
42.79 dBm
duplexer 4 13.5W [Symbol_approximate]
41.30 dBm
68P02901W23-Q 5-87
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.
5-88 68P02901W23-Q
Technical Description: BSS Command Reference bts_type
bts_type
Description
The bts_type parameter specifies the BTS configuration type. It is valid only for sites 1 to 120.
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-Cell
2, M-Cell6, M-Cellcity, Horizonmicro, Horizoncompact and
Horizonmacro cabinets.
Syntax

chg_element bts_type <value> <location>

disp_element bts_type <location>
Values
Value type Integer

Valid range 0 or 1
0 BTP
1 BTP and DHP
Default value None
68P02901W23-Q 5-89
bts_type Chapter 5: CM database parameters
References
GSM parameter None

5-90 68P02901W23-Q
Technical Description: BSS Command Reference bvci
bvci
Description
The bvci parameter specifies a BSSGP Virtual Connection Identifier (BVCI). There must be one BVCI per
cell and one signalling BVCI per BSS. BVCIs are automatically generated by the BSS on creation of a cell.
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 signalling BVCI.
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

chg_element bvci <value> <location> <cell_desc>
chg_cell_element bvci <value> <cell_desc>

disp_element bvci <location> <cell_desc>
68P02901W23-Q 5-91
bvci Chapter 5: CM database parameters
Values
Value type Integer

Default value None
5-92 68P02901W23-Q
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 number of call trace instances that may be created is affected by the percentage of traces reserved
exclusively for MSC initiated traces. 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 would permit 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.
Dependencies None
Syntax

chg_element call_trace_options <value> <location>

disp_element call_trace_options <location>
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.
68P02901W23-Q 5-93
call_trace_options Chapter 5: CM database parameters
255 MSC invoked call traces disabled.

Default value 0
5-94 68P02901W23-Q
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.
Dependencies This parameter is valid only at the BSC.
Syntax

chg_element called_pci <value> 0

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.713This is a Motorola defined parameter.
68P02901W23-Q 5-95
calling_pci Chapter 5: 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.
Dependencies This parameter is valid only at the BSC.
Syntax

chg_element calling_pci <value> 0

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.
5-96 68P02901W23-Q
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.
Dependencies None
Syntax

chg_element carrier_disable_time <value> <location>

disp_element carrier_disable_time <location>
Values
Value type Integer (seconds)

Default value 120
68P02901W23-Q 5-97
carriers_ins_pwr_fail Chapter 5: 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 5-97). Non
BCCH carriers are taken out of service before the BCCH carrier.
The BCCH carrier will continue 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.
Dependencies None
Syntax

chg_element carriers_ins_pwr_fail <value> <location>

disp_element carriers_ins_pwr_fail <location>
5-98 68P02901W23-Q
Technical Description: BSS Command Reference carriers_ins_pwr_fail
Values
Value type Integer

Valid range 0 to 30
0 All carriers are taken out of service.
Default value 30
68P02901W23-Q 5-99
cbc_fast_select Chapter 5: 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.
Dependencies This parameter is valid only for the BSC.
Syntax

chg_element cbc_fast_select <value> 0
A site reset is required when the value of cbc_fast_select is changed. Resetting the site
generates several alarms. However, these alarms are blocked by the system.

disp_element cbc_fast_select 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-100 68P02901W23-Q
Technical Description: BSS Command Reference cbc_fast_select
References
GSM specification 03.4103.49

68P02901W23-Q 5-101
cbc_intface_vers Chapter 5: 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.
Dependencies This parameter is only valid for the BSC.
Syntax

chg_element cbc_intface_vers <value> 0

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
5-102 68P02901W23-Q
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.
Dependencies This parameter is only valid for the BSC.
Syntax

chg_element cbc_vbind_cntr <value> 0

disp_element cbc_vbind_cntr 0
Values
Value type Integer (number of VBINDs)

Default value 0
68P02901W23-Q 5-103
cbch_enabled Chapter 5: 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.
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

chg_element cbch_enabled <value> <location> <cell_desc>
chg_cell_element cbch_enabled <value> <cell_desc>

disp_element cbch_enabled <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None
5-104 68P02901W23-Q
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.
Dependencies This parameter is only valid for a BTS site.
Syntax

chg_element cbs_outage_cntr <value> <location>

disp_element cbs_outage_cntr <location>
Values
Value type Integer (number of broadcast slots)

Default value 0
68P02901W23-Q 5-105
ccch_conf Chapter 5: 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.
When the value of this parameter is changed, the bs_ag_blks_res,

number_sdcch_preferred, min_number_of_sdcchs, and max_number_of_sdcchs
parameters may also need to be changed. If this is not done, the site may
not boot properly and will never reach the busy state.
When the chg_cell_element command is used to change the value of

this parameter, a warning is presented followed by a series of prompts:
WARNING: This command will cause an RTF to be temporarily

unequipped and then re-equipped. This has the following effects:
If baseband hopping, all calls on an in-service carrier will be lost and
hopping for this carrier will be disabled until the site is reset.
If synthesizer hopping, all calls on an in-service carrier will be lost.
Enter CRM maximum number of SDCCHs:

Enter CRM SDCCH low water mark:
Enter CRM SDCCH high water mark:
Enter number of SDCCHs preferred:
Enter RSS blocks reserved for access grant:
If the chg_cell_element command is used to change the value of this parameter and the change would allow
hopping on a BCCH timeslot, the system rejects the command and displays the following error message:
WARNING: This operation may cause a carrier to be taken out of service

and calls affected by this carrier may be lost. Loss of calls depends
on the availability of other carriers.
The system rejects this command if it is attempted for all sites.

Type B (operation actions required)
5-106 68P02901W23-Q
Technical Description: BSS Command Reference ccch_conf
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 with no

offset (divisible by 8) (that is, 0, 8, 16,...,48)
• number_sdcchs_preferred must be less than or equal to

sdcch_need_low_water_mark.
• The minimum number of sdcchs must be divisible by 8.
• max_number_of_sdcchs must be divisible by 8.
• 0 v bs_ag_blks_res v 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, 0,4,12,...,44 )
• The minimum number of sdcchs must be a multiple of 8 (+4).
• max_number_of_sdcchs must be a multiple of 8 (+4).
• 0 v bs_ag_blks_res v 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.
68P02901W23-Q 5-107
ccch_conf Chapter 5: CM database parameters
Syntax

The system rejects this command if it is attempted when location = all.
chg_cell_element ccch_conf <value> <cell_desc>
A site reset is required when the value of ccch_conf is changed. Resetting the site generates
several alarms. However, these alarms are blocked by the system.

disp_cell <cell_number>
disp_element ccch_conf <location> <cell_desc>
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: organisation of common control channels
5.02 - 6.4: allowable channel configurations
4.03 - 5.1 and 6.2: organisation 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
5-108 68P02901W23-Q
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.
Other parameters can affect flow control. Refer to rach_load_period, rach_overload_threshold,

ssm_normal_overload_threshold, ssm_critical_overload_threshold or tch_flow_control.
Dependencies This parameter must be greater than or equal to the
rach_load_period.
Syntax

chg_element ccch_load_period <value> <location> <cell_desc>
chg_cell_element ccch_load_period <value> <cell_desc>

disp_element ccch_load_period <location> <cell_desc>
68P02901W23-Q 5-109
ccch_load_period Chapter 5: CM database parameters
Values
Value type Integer (1 Step = 1 TDMA multiframe)

Default value 40
References
GSM parameter CCCH_LOAD_IND_PERIOD

GSM specification 5.08.1.1 - 5.2.3
5-110 68P02901W23-Q
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 diagram below.
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 diagram below.
For example, if access classes 2, 3, 7 and 9 were to be barred, the following would be 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 5-10 lists the values for barring classes.
68P02901W23-Q 5-111
cell_bar_access_class Chapter 5: CM database parameters
Table 5-10 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
3 bar classes 12 bar classes 8 and 9 bar classes 4 and 5 bar classes 0 and 1
and 13
and 14
and 14
7 bar classes 12, 13 bar classes 8, 9 bar classes 4, 5 and 6 bar classes 0, 1 and 2
and 14 and 10
and 15
a bar classes 13 bar classes 9 and 11 bar classes 5 and 7 bar classes 1 and 3
and 15
b bar classes 12, 13 bar classes 8, 9 bar classes 4, 5 and 7 bar classes 0, 1 and 3
and 15 and 11
c bar classes 14 bar classes 10 and 11 bar classes 6 and 7 bar classes 2 and 3
and 15
d bar classes 12, 14 bar classes 8, 10 bar classes 4, 6 and 7 bar classes 0, 2 and 3
and 15 and 11
e bar classes 13, 14 bar classes 9, 10 bar classes 5, 6 and 7 bar classes 1,2 and 3
and 15 and 11
f bar classes 12, 13, bar classes 8, 9 bar classes 4, 5 bar classes 0, 1,
14 and 15 10 and 11 6, and 7 2 and 3
When entering a hexadecimal value, the suffix “h" is required.

Dependencies cell_bar_access_switch
5-112 68P02901W23-Q
Technical Description: BSS Command Reference cell_bar_access_class
Syntax

chg_element cell_bar_access_class <value> <location> <cell_desc>
chg_cell_element cell_bar_access_class <value> <cell_desc>

disp_element cell_bar_access_class <location> <cell_desc>
Values
Value type Integer

Default value 0
References
GSM parameter AC_CN

GSM specification 4.08 - 3.3.1.
4.08 - 3.3.1.1
68P02901W23-Q 5-113
cell_bar_access_switch Chapter 5: CM database parameters
cell_bar_access_switch
Description
The cell_bar_access_switch parameter specifies whether or not subscribers are barred

access to a cell in idle mode.
Emergency calls (user class 10) are not, and cannot be, barred.
A 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).
Dependencies None
Syntax

chg_element cell_bar_access_switch <value> <location> <cell_desc>
chg_cell_element cell_bar_access_switch <value> <cell_desc>

disp_element cell_bar_access_switch <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Cell is not barred
5-114 68P02901W23-Q
Technical Description: BSS Command Reference cell_bar_access_switch
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-Q 5-115
cell_bar_qualify Chapter 5: CM database parameters
cell_bar_qualify
Description
The cell_bar_qualify parameter is used by the network to control MS cell selection.

Dependencies This parameter cannot be changed if the cell_reselect_param_ind
parameter does not equal 1.
Syntax

chg_element cell_bar_qualify <value> <location> <cell_desc>
chg_cell_element cell_bar_qualify <value> <cell_desc>

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
5-116 68P02901W23-Q
Technical Description: BSS Command Reference cell_bar_qualify
References
GSM specification 3.22

4.08 Table 10.32 in section 10.5.2.35
5.08 Table 1a in section 9.
68P02901W23-Q 5-117
cell_reselect_hysteresis Chapter 5: CM database parameters
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 to 14 dB (in 2 dB increments) are used for cell reselection.
Dependencies C1 (path loss criterion)
Syntax

chg_element cell_reselect_hysteresis <value> <location> <cell_desc>
chg_cell_element cell_reselect_hysteresis <value> <cell_desc>

disp_element cell_reselect_hysteresis <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 7
Represents the signal level differences as shown below:
0 0 dB
1 2 dB
5-118 68P02901W23-Q
Technical Description: BSS Command Reference cell_reselect_hysteresis
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
68P02901W23-Q 5-119
cell_reselect_offset Chapter 5: CM database parameters
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.
Dependencies This parameter may not be changed if the cell_reselect_parm_ind
parameter is not equal to 1.
Syntax

chg_element cell_reselect_offset <value> <location> <cell_desc>
chg_cell_element cell_reselect_offset <value> <cell_desc>

disp_element cell_reselect_offset <location> <cell_desc>
Values
Value type Integer (1 Step = 2 dB)

Valid range 0 to 63
0 0 dB
1 2 dB
5-120 68P02901W23-Q
Technical Description: BSS Command Reference cell_reselect_offset
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
68P02901W23-Q 5-121
cell_reselect_param_ind Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_element cell_reselect_param_ind <value> <location> <cell_desc>
chg_cell_element cell_reselect_param_ind <value> <cell_desc>

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
5-122 68P02901W23-Q
Technical Description: BSS Command Reference cell_reselect_param_ind
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.
68P02901W23-Q 5-123
chan_alloc_priority Chapter 5: CM database parameters
chan_alloc_priority
Description
The chan_alloc_priority parameter specifies the channel allocation priority of an in-service carrier.
The interference band of a channel is still the first criterion in the channel allocation algorithms. A channel
from the highest priority carrier matching the requested interference band is allocated to a channel request.
Dependencies None
Syntax

equip <location> rtf
modify_value <location> chan_alloc_priority <new_value>

rtf <rtf_id1> <rtf_id2> <rtf_id3>

disp_equipment <location> rtf <rtf_id1> <rtf_id2> <rtf_id3>
Values
Value type Integer (representing the channel allocation for an RTF)

0 Highest priority
250 Lowest priority
Default value 0
5-124 68P02901W23-Q
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 are in use and additional SDCCH requests are received. The reconfiguration process
continues until the number of idle SDCCHs reaches the sdcch_need_high_water_mark value.
The reconfiguration process stops when the number of idle TCHs goes below the
tch_full_need_low_water_mark value or when the total number of SDCCHs configured
reaches the max_number_of_sdcchs value.
Dependencies None
Syntax

chg_element channel_reconfiguration_switch <value> <location> <cell_desc>
chg_cell_element channel_reconfiguration_switch <value> <cell_desc>

disp_element channel_reconfiguration_switch <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
68P02901W23-Q 5-125
channel_reconfiguration_switch Chapter 5: CM database parameters
1 Enabled
Default value 0
References
GSM specification Figure 3 5.02 - 6.4: permitted channel combinations of logical

channels
5-126 68P02901W23-Q
Technical Description: BSS Command Reference cic_block_thresh
cic_block_thresh
Description
The cic_block_thresh parameter specifies the threshold for blocking Circuit Identity Codes
(CICs) according to the availability of idle Aters.
Dependencies This parameter can be modified inside and outside Sysgen mode.
The AMR Enhanced Capacity {22064} and/or GSM Half Rate
An AXCDR device cannot be in Enhanced Auto-Connect mode if
CIC validation is disabled.
The eac_mode parameter must be enabled.
The cic_block_thresh parameter must be less than the
cic_unblock_thresh parameter except when both parameters are 0.
Syntax

modify_value 0 cic_block_thresh <value> AXCDR <axcdr_id>
equip 0 AXCDR
68P02901W23-Q 5-127
cic_block_thresh Chapter 5: CM database parameters
After entering the equip AXCDR command, the user is prompted for following parameters:
• device ID.
• CIC validation.
• EAC mode.
When eac_mode is enabled, the user is prompted for the following parameters:
• CIC blocking threshold.
• CIC unblocking threshold.

disp_equipment 0 AXCDR <axcdr_id>
Values
Value type Integer

Default value 0
5-128 68P02901W23-Q
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).

Dependencies Two successful calls are required on a resource before an alarm can
be cleared within this threshold. (One successful call might be too
short for the Channel Coder Unit (CCU) to send an error indication,
thus clearing the alarm prematurely.)
between the new and the old threshold does not clear an alarm until
another successful call is made on the CIC.
Syntax

chg_element cic_error_clr_thresh <value> 0

disp_element cic_error_clr_thresh 0
Values
Value type Integer

Default value 0
68P02901W23-Q 5-129
cic_error_gen_thresh Chapter 5: 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).
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

chg_element cic_error_gen_thresh <value> 0

disp_element cic_error_gen_thresh 0
Values
Value type Integer

Default value 6
5-130 68P02901W23-Q
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.
Syntax

chg_element cic_error_inc <value> 0

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-Q 5-131
cic_unblock_thresh Chapter 5: CM database parameters
cic_unblock_thresh
Description
The cic_unblock_thresh parameter specifies the threshold for unblocking Circuit Identity
Codes (CICs) according to the availability of idle Aters.
Dependencies This parameter can be modified inside and outside sysgen mode.
The AMR Enhanced Capacity {22064} and/or GSM Half Rate
An AXCDR device cannot be in enhanced auto-connect mode if
CIC validation is disabled.
The eac_mode parameter must be enabled.
cic_unblock_thresh parameter except when both parameters are 0.
Syntax

modify_value 0 cic_unblock_thresh <value> AXCDR <axcdr_id>
equip 0 AXCDR
5-132 68P02901W23-Q
Technical Description: BSS Command Reference cic_unblock_thresh
• device ID.
• CIC validation.
• EAC mode.

Values
Value type Integer

Default value 0 Disables this parameter.
68P02901W23-Q 5-133
cic_validation Chapter 5: CM database parameters
cic_validation
Description
The cic_validation parameter enables or disables the Circuit Identity Code (CIC) validation for an RXCDR.
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

modify_value <location> cic_validation <value> AXCDR <axcdr_id>

disp_equipment <location> AXCDR <axcdr_id>
Values
Value type Boolean

Valid range no or yes
no Disabled
yes Enabled
Default value None
5-134 68P02901W23-Q
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.
Dependencies This parameter only applies to the BSC.
Syntax

chg_element ciph_mode_rej_allowed <value> 0

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

68P02901W23-Q 5-135
clk_src_fail_reset_period Chapter 5: 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.
Dependencies None
Syntax

chg_element clk_src_fail_reset_period <value> <location>

disp_element clk_src_fail_reset_period <location>
Values
Value type Integer (hours)

Default value 24
5-136 68P02901W23-Q
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.
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
neighbours of each other.
If coincident_mb is set to 2, both cells must be at the same site, the
cells must be neighbours of each other, and the bsic settings must
be the same.
A cell cannot be coincident to itself.
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

chg_cell_element coincident_cell <value> <cell_desc>
The system prompts for the cell number for the coincident_cell.

disp_element coincident_cell <location> <cell_desc>
68P02901W23-Q 5-137
coincident_cell Chapter 5: CM database parameters
Values
Value type Integer

Valid range The GSM Cell ID number
Default value None
5-138 68P02901W23-Q
Technical Description: BSS Command Reference coincident_mb
coincident_mb
Description
The coincident_mb parameter specifies the ability of a BTS to execute the Coin-
cident MultiBand Handover option.
Handover option is enabled.
If coincident_mb is set to 1 or 2, both cells must be SACCH
neighbours of each other.
If coincident_mb is set to 2, both cells must be at the same site, the
cells must be neighbours 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
chg_cell_element coincident_mb <value> <cell_desc>

The system prompts for the cell number for the coincident_cell.
68P02901W23-Q 5-139
coincident_mb Chapter 5: CM database parameters

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
5-140 68P02901W23-Q
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.
Handover option is enabled.
Syntax

chg_element coincident_offset <value> <location> <cell_desc>
chg_cell_element coincident_offset <value> <cell_desc>

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 2-77.

disp_element coincident_offset <location> <cell_desc>
Values
Value type Integer (dB)

Valid range -63 to 63
Default value 0
68P02901W23-Q 5-141
confusion_msg_allowed Chapter 5: 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.
Dependencies This parameter does not apply to RXCDR sites.
This parameter only applies to the BSC.
Syntax

chg_element confusion_msg_allowed <value> 0

disp_element confusion_msg_allowed 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-142 68P02901W23-Q
Technical Description: BSS Command Reference confusion_msg_allowed
References

68P02901W23-Q 5-143
congest_at_source Chapter 5: CM database parameters
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.
Target cells that are in the process of Congestion Relief may become available for
handovers more quickly than those that are not.
Cell number required Yes
Dependencies The parameter can be set only if the Congestion Relief feature is
unrestricted.
Syntax

chg_element congest_at_source <value> <location> <cell_desc>
chg_cell_element congest_at_source <value> <cell_desc>

disp_element congest_at_source <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
5-144 68P02901W23-Q
Technical Description: BSS Command Reference congest_at_source
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
Refer to the congest_at_target parameter to see when a target cell performs

congestion relief procedures.
68P02901W23-Q 5-145
congest_at_target Chapter 5: CM database parameters
congest_at_target
Description
The congest_at_target parameter specifies how a specified cell behaves if it rejects a handover request.
Dependencies The parameter can be set only if the Congestion Relief feature is
unrestricted.
Syntax

chg_element congest_at_target <value> <location> <cell_desc>
chg_cell_element congest_at_target <value> <cell_desc>

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
5-146 68P02901W23-Q
Technical Description: BSS Command Reference congest_ho_margin
congest_ho_margin
Description
The congest_ho_margin parameter specifies the margin of a congestion handover. To make it

easier to handover to this neighbour in the case of congestion in the current cell, this parameter
value should be less that the value of the handover margin(s).
To disable congestion handovers to this neighbour, set the congestion handover margin to the maximum value.
Dependencies This parameter can only be modified if:
• either the Directed Retry or Alternate Congestion Relief

options are available,
and
• the neighbour is placed on the SACCH list.
Syntax

modify_neighbor <source_cell_id> <neighbor_cell_id> con-
gest_ho_margin <value>

disp_neighbor congest_ho_margin
Values
Value type Integer (each step equals 1 dB)

Default value None
68P02901W23-Q 5-147
cp_option_reset_ckt Chapter 5: CM database parameters
cp_option_reset_ckt
Description
The cp_option_reset_ckt parameter enables and disables the reset circuit feature.
Dependencies None
Syntax

chg_element cp_option_reset_ckt <value> <location>

disp_element cp_option_reset_ckt <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-148 68P02901W23-Q
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 this is enabled, the BSS can generate the 4.08 radio resource status message to the MS.
Dependencies None
Syntax

chg_element cp_option_rr_status <value> <location>

disp_element cp_option_rr_status <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-149
cr_calling Chapter 5: 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.
Syntax

chg_element cr_calling <value> 0

disp_element cr_calling 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-150 68P02901W23-Q
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.
Dependencies ct_flow_control_hi_level must be greater than
ct_flow_control_lo_level plus 20.
Syntax

chg_element ct_flow_control_hi_level <value> <location>

disp_element ct_flow_control_hi_level <location>
Values
Value type Integer

Default value 60
68P02901W23-Q 5-151
ct_flow_control_lo_level Chapter 5: 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.)
Dependencies ct_flow_control_lo_level must be less than ct_flow_con-
trol_hi_level minus 20.
Syntax

chg_element ct_flow_control_lo_level <value> <location>

disp_element ct_flow_control_lo_level <location>
Values
Value type Integer

Valid range 0 to 80
Default value 20
5-152 68P02901W23-Q
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.
Dependencies None
Syntax

chg_element ct_flow_control_msc_trace <value> <location>

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-Q 5-153
c31_hyst Chapter 5: CM database parameters
c31_hyst
Description
The c31_hyst parameter is a flag specifying whether or not hysteresis is applied to C31.
Type A (No operator actions required)
BSS software processes using this parameter are immediately notified when the change is made.
Syntax

chg_cell_element c31_hyst <value> <cell-desc>
chg_cell_element <location> c31_hyst <value> all
chg_element c31_hyst <value> <location> <cell_desc>

disp_element c31_hyst <location> <cell-desc>
disp_element c31_hyst <location> all
Values
Value type Boolean

Valid range 0 or 1
5-154 68P02901W23-Q
Technical Description: BSS Command Reference c31_hyst
0 Hysteresis not applied

1 Hysteresis applied
Default value 0
68P02901W23-Q 5-155
c32_qual Chapter 5: 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.
Syntax

chg_cell_element c32_qual <value> <cell-desc>
chg_cell_element <location> c32_qual <value> all
chg_element c32_qual <value> <location> <cell_desc>

disp_element c32_qual <location> <cell-desc>
disp_element c32_qual <location> all
5-156 68P02901W23-Q
Technical Description: BSS Command Reference c32_qual
Values
Value type Boolean

Valid range 0 or 1
0 Exception not allowed
1 Exception allowed
Default value 0
68P02901W23-Q 5-157
data_qual_enabled Chapter 5: 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 very 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 below,
instead of the normal rxqual values set with the add_cell command.
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.
Dependencies alt_qual_proc
Syntax

chg_cell_element data_qual_enabled <value> <cell_desc>
If the value is 1 (enabled) the system prompts for the data threshold values as the following parameters:
• "l_rxqual_dl_h" on page 5-410.
• "l_rxqual_ul_h" on page 5-436.
• "l_rxqual_dl_p" on page 5-423.
• "l_rxqual_ul_p" on page 5-449.
5-158 68P02901W23-Q
Technical Description: BSS Command Reference data_qual_enabled

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-Q 5-159
ddtr_ctrl_enabled Chapter 5: 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 as a function of cell availability.
The ddtr_ctrl_enabled parameter is configurable on a per BSS basis.
Type A
Dependencies None
Operator actions None.
Syntax

chg_element ddtr_ctrl_enabled <value> <location>

disp_element ddtr_ctrl_enabled <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0 (disabled)
5-160 68P02901W23-Q
Technical Description: BSS Command Reference decision_1_dl_rxlev_av_h
decision_1_dl_rxlev_av_h
Description
The decision_1_dl_rxlev_av_h parameter specifies the bin number containing the measurement averaging
algorithm data used to make the handover decisions for downlink signal strength.
This parameter may not be changed to a bin which does not contain valid handover algorithm data.
Dependencies rxlev_dl_ho
Syntax

chg_element decision_1_dl_rxlev_av_h <value> <location> <cell_desc>
chg_cell_element decision_1_dl_rxlev_av_h <value> <cell_desc>

disp_element decision_1_dl_rxlev_av_h <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
Default value 0
68P02901W23-Q 5-161
decision_1_dl_rxlev_av_ih Chapter 5: CM database parameters
decision_1_dl_rxlev_av_ih
Description
The decision_1_dl_rxlev_av_ih parameter 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.
Dependencies rxlev_dl_ho
Syntax

chg_element decision_1_dl_rxlev_av_ih <value> <location> <cell_desc>
chg_cell_element decision_1_dl_rxlev_av_ih <value> <cell_desc>

disp_element decision_1_dl_rxlev_av_ih <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 1
Default value 0
5-162 68P02901W23-Q
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.
Dependencies rxqual_dl_pc
Syntax

chg_element decision_1_dl_rxqual_av_p <value> <location> <cell_desc>
chg_cell_element decision_1_rxqual_av_p <value> <cell_desc>

disp_element decision_1_dl_rxqual_av_p <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 1
Default value 0
68P02901W23-Q 5-163
decision_1_dl_rxqual_av_h Chapter 5: CM database parameters
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).
Dependencies rxqual_dl_ho
Syntax

chg_element decision_1_dl_rxqual_av_h <value> <location> <cell_desc>
chg_cell_element decision_1_dl_rxqual_av_h <value> <cell_desc>

disp_element decision_1_dl_rxqual_av_h <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 1
Default value 0
5-164 68P02901W23-Q
Technical Description: BSS Command Reference 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).
Dependencies rxqual_dl_pc
Syntax

chg_element decision_1_dl_rxqual_av_p <value> <location> <cell_desc>
chg_cell_element decision_1_rxqual_av_p <value> <cell_desc>

disp_element decision_1_dl_rxqual_av_p <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 1
Default value 0
68P02901W23-Q 5-165
decision_1_n1/decision_1_p1 Chapter 5: 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 must be increased.
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

chg_element decision_1_n1 <value> <location> <cell_desc>
chg_cell_element decision_1_n1 <value> <cell_desc>
chg_cell_element decision_1_p1 <value> <cell_desc>

disp_element decision_1_n1 <location> <cell_desc>
disp_element decision_1_p1 <location> <cell_desc>
5-166 68P02901W23-Q
Technical Description: BSS Command Reference decision_1_n1/decision_1_p1
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-Q 5-167
Description
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) must be decreased.
rxlev_dl_pc and rxlev_ul_pc.
Syntax

chg_element decision_1_p2 <value> <location> <cell_desc>

5-168 68P02901W23-Q
Values

Valid range 1 to 31
Default value 1
References

12.20 - 5.2.8.26: Signal Strength Serving Cell
68P02901W23-Q 5-169
Description
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) must be increased.
rxqual_dl_pc and rxqual_ul_pc.
Syntax


5-170 68P02901W23-Q
Values

Valid range 1 to 31
Default value 1
References

12.20 - 5.2.8.25: Signal Quality Serving Cell
68P02901W23-Q 5-171
Description
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) must be decreased.
rxqual_dl_pc and rxqual_ul_pc.
Syntax


5-172 68P02901W23-Q
Values

Valid range 1 to 31
Default value 1
References

12.20 - 5.2.8.25: Signal Quality Serving Cell
68P02901W23-Q 5-173
Description
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 might be required.
rxlev_dl_ho and rxlev_ul_ho.
Syntax


5-174 68P02901W23-Q
Values

Valid range 1 to 31
Default value 1
References

12.20 - 5.2.8.19: Handover Control Thresholds
68P02901W23-Q 5-175
Description
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.
rxqual_dl_ho and rxqual_ul_ho.
Syntax


5-176 68P02901W23-Q
Values

Valid range 1 to 31
Default value 1
References

68P02901W23-Q 5-177
Description
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 might be
required if rxqual_ul/dl is also greater than l_rxqual_ul/dl_h.
rxlev_dl_ho and rxlev_ul_ho.
Syntax


5-178 68P02901W23-Q
Values

Valid range 1 to 31
Default value 1
References

68P02901W23-Q 5-179
Description
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 might be required due to distance.
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.
Syntax


5-180 68P02901W23-Q
Values

Valid range 1 to 31
Default value 1
References

12.20 - 5.2.8.21: ms Distance Average
68P02901W23-Q 5-181
decision_1_ncell_rxlev_av_h_calc Chapter 5: CM database parameters
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.
Dependencies surround_cell
Syntax

chg_element decision_1_ncell_rxlev_av_h_calc
<value> <location> <cell_desc>
chg_cell_element decision_1_ncell_rxlev_av_h_calc <value> <cell_desc>

disp_element decision_1_ncell_rxlev_av_h_calc <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
Default value 0
5-182 68P02901W23-Q
Technical Description: BSS Command Reference decision_1_p_bgt_rxlev_av_h
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.
Dependencies None
Syntax

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>

disp_element decision_1_p_bgt_rxlev_av_h <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
Default value 0
68P02901W23-Q 5-183
decision_1_tim_adv_av_alg Chapter 5: CM database parameters
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.
Dependencies rel_tim_adv
Syntax

chg_element decision_1_tim_adv_av_alg <value> <location> <cell_desc>
chg_cell_element decision_1_tim_adv_av_alg <value> <cell_desc>

disp_element decision_1_tim_adv_av_alg <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
Default value 0
5-184 68P02901W23-Q
Technical Description: BSS Command Reference decision_1_ul_rxlev_av_h
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.
Dependencies rxlev_ul_ho
Syntax

chg_element decision_1_ul_rxlev_av_h <value> <location> <cell_desc>
chg_cell_element decision_1_ul_rxlev_av_h <value> <cell_desc>

disp_element decision_1_ul_rxlev_av_h <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
Default value 0
68P02901W23-Q 5-185
decision_1_ul_rxlev_av_ih Chapter 5: CM database parameters
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.
Dependencies rxlev_ul_ho
Syntax

chg_element decision_1_ul_rxlev_av_ih <value> <location> <cell_desc>
chg_cell_element decision_1_ul_rxlev_av_ih <value> <cell_desc>

disp_element decision_1_ul_rxlev_av_ih <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
Default value 0
5-186 68P02901W23-Q
Technical Description: BSS Command Reference decision_1_ul_rxlev_av_p
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.
Dependencies rxlev_ul_pc
Syntax

chg_element decision_1_ul_rxlev_av_p <value> <location> <cell_desc>
chg_cell_element decision_1_ul_rxlev_av_p <value> <cell_desc>

disp_element decision_1_ul_rxlev_av_p <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
Default value 0
68P02901W23-Q 5-187
decision_1_ul_rxqual_av_h Chapter 5: CM database parameters
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.
Dependencies rxqual_ul_ho
Syntax

chg_element decision_1_ul_rxqual_av_h <value> <location> <cell_desc>
chg_cell_element decision_1_ul_rxqual_av_h <value> <cell_desc>

disp_element decision_1_ul_rxqual_av_h <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
Default value 0
5-188 68P02901W23-Q
Technical Description: BSS Command Reference decision_1_ul_rxqual_av_p
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 uplink receive quality.
Dependencies rxqual_ul_pc
Syntax

chg_element decision_1_ul_rxqual_av_p <value> <location> <cell_desc>
chg_cell_element decision_1_ul_rxqual_av_p <value> <cell_desc>

disp_element decision_1_ul_rxqual_av_p <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
Default value 0
68P02901W23-Q 5-189
decision_alg_type Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_element decision_alg_type <value> <location> <cell_desc>
chg_cell_element decision_alg_type <value> <cell_desc>

disp_element decision_alg_type <location> <cell_desc>
Values
Value type Integer (algorithms)

Valid range 0 or 1
0 Power control algorithm number 1
5-190 68P02901W23-Q
Technical Description: BSS Command Reference decision_alg_type
1 Power control algorithm number 2 (enables the use of p_con_ack

timers)
Default value 0
68P02901W23-Q 5-191
delay_ul_rel_dur Chapter 5: CM database parameters
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
Dependencies GPRS must be unrestricted.
Syntax

chg_element delay_ul_rel_dur <value> <location>

disp_element delay_ul_rel_dur <location>
Values
Value type Integer

Valid range 10 to 50 Number of block periods (1 block period = 20 ms) in which the
network delays the release of an uplink TBF.
Default value 18 (360 ms).
5-192 68P02901W23-Q
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.
Dependencies The Concentric Cells feature must be enabled in order to set this
parameter.
Syntax

chg_element direct_inner_zone_threshold <value> <location> <cell_desc>
chg_cell_element direct_inner_zone_threshold <value> <cell_desc>

disp_element direct_inner_zone_threshold <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 63
Default value 63
68P02901W23-Q 5-193
disuse_cnt_hreqave Chapter 5: CM database parameters
disuse_cnt_hreqave
Description
If the disuse_cnt_hreqave parameter is enabled, neighbour cells with a disuse count less than or
equal to the maximum disuse count are still valid candidates for handovers.
Disuse count is the number of consecutive measurement reports a previously reported neighbour
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.
If enabled, the maximum disuse count is defined by the surrounding cell hreqave.
Dependencies None
Syntax

chg_element disuse_cnt_hreqave <value> <location> <cell_desc>
chg_cell_element disuse_cnt_hreqave <value> <location> <cell_desc>

disp_element disuse_cnt_hreqave <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-194 68P02901W23-Q
Technical Description: BSS Command Reference dl_audio_lev_offset
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.
Changes to this parameter take effect immediately. This includes active calls.
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.
Syntax

chg_element dl_audi_lev_offset <value> <location>

disp_element dl_audio_lev_offset 0
68P02901W23-Q 5-195
dl_audio_lev_offset Chapter 5: CM database parameters
Values

Valid range -15 to +15
Default value 0
5-196 68P02901W23-Q
Technical Description: BSS Command Reference dl_dtx_voice_data
dl_dtx_voice_data
Description
The dl_dtx_voice_data parameter specifies the option for downlink discontinuous

transmission (DTX) for speech and voice.
Dependencies The dl_dtx_voice_data parameter affects speech only if
dnlk_vad_dtx is enabled.
Syntax

chg_element dl_dtx_voice_data <value> <location> <cell_desc>
chg_cell_element dl_dtx_voice_data <value> <cell_desc>

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
68P02901W23-Q 5-197
dl_rxlev_ho_allowed Chapter 5: CM database parameters
dl_rxlev_ho_allowed
Description
The dl_rxlev_ho_allowed parameter enables or disables a handover due to downlink receive level (rxlev).
Dependencies None
Syntax

chg_element dl_rxlev_ho_allowed <value> <location> <cell_desc>
chg_cell_element dl_rxlev_ho_allowed <value> <cell_desc>

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
5-198 68P02901W23-Q
Technical Description: BSS Command Reference dl_rxlev_ho_allowed
References
Internal name EN_RXLEV_HO

This is a Motorola parameter.
68P02901W23-Q 5-199
dl_rxqual_ho_allowed Chapter 5: CM database parameters
dl_rxqual_ho_allowed
Description
The dl_rxqual_ho_allowed parameter enables or disables a handover due to downlink receive quality (rxqual).
Dependencies None
Syntax

chg_element dl_rxqual_ho_allowed <value> <location> <cell_desc>
chg_cell_element dl_rxqual_ho_allowed <value> <cell_desc>

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
5-200 68P02901W23-Q
Technical Description: BSS Command Reference dl_rxqual_ho_allowed
References
Internal name EN_RXQUAL_HO

68P02901W23-Q 5-201
dnlk_vad_dtx Chapter 5: CM database parameters
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.
This parameter replaces the xcdr_d_vad_dtx command.
As of GSR5.1, the downlink DTX is supported only on the non-BCCH carrier.
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

chg_element dnlk_vad_dtx <value> <location>

disp_element dnlk_vad_dtx <location>
Values
Value type Boolean

Valid range 0 or 1
0 Enabled
5-202 68P02901W23-Q
Technical Description: BSS Command Reference dnlk_vad_dtx
1 Disabled
Default value None
68P02901W23-Q 5-203
dpc Chapter 5: 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 5-570) and ss7_mode (see "ss7_mode"
on page 5-753) 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.

Dependencies This parameter is only valid at the BSC.
Syntax

chg_element dpc <value> <location>

disp_element dpc <location>
Values
Value type Integer

Valid range 0 to 16383 If ss7_mode = 0 (CCITT)
0 to 16777215 If ss7_mode =1 (Bellcore)
Default value None
5-204 68P02901W23-Q
Technical Description: BSS Command Reference dpc
References
GSM parameter DPC

GSM specification CCITT Q.708
68P02901W23-Q 5-205
dr_allowed Chapter 5: CM database parameters
dr_allowed
Description
The dr_allowed parameter enables or disables the Directed Retry feature.

Dependencies This parameter can be modified only if all the following conditions
are met:
• the Directed Retry feature is available,
• the neighbour is placed on the SACCH list, and
• the neighbour is external.
Syntax

modify_neighbor <src_cell_id> <neighbor_cell_id> dr_allowed <value>

disp_neighbor <src_cell_id> all
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None
5-206 68P02901W23-Q
Technical Description: BSS Command Reference dr_chan_mode_modify
dr_chan_mode_modify
Description
The dr_chan_mode_modify parameter determines if the channel mode modify procedure will follow
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.
Dependencies The Directed Retry feature must be unrestricted.
This parameter can be changed only at the BSC.
Syntax

chg_element dr_chan_mode_modify <value> 0

disp_element dr_chan_mode_modify 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-207
dr_chan_mode_modify Chapter 5: CM database parameters
References
GSM specification TS GSM 08.08 ETR 09.94

5-208 68P02901W23-Q
Technical Description: BSS Command Reference dr_ho_during_assign
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 will be copied if the copy_cell command is used.
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

chg_element dr_ho_during_assign <value> <location> <cell_desc>
chg_cell_element dr_ho_during_assign <value> <cell_desc>

disp_element dr_ho_during_assign <location> <cell_desc>
68P02901W23-Q 5-209
dr_ho_during_assign Chapter 5: CM database parameters
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

5-210 68P02901W23-Q
Technical Description: BSS Command Reference dr_preference
dr_preference
Description
The dr_preference parameter enables or disables the Directed Retry procedures.

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

chg_element dr_preference <value> 0

disp_element dr_preference 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-211
dr_preference Chapter 5: CM database parameters
References
GSM specification TS GSM 08.08 This is a Motorola defined parameter.
5-212 68P02901W23-Q
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.
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
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

chg_element dr_standard_congest <value> <location> <cell_desc>
chg_cell_element dr_standard_congest <value> <cell_desc>

disp_element dr_standard_congest <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
68P02901W23-Q 5-213
dr_standard_congest Chapter 5: CM database parameters
1 Enabled
Default value 0
References

5-214 68P02901W23-Q
Technical Description: BSS Command Reference dtx_required
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.
Dependencies None
Syntax

chg_element dtx_required <value> <location> <cell_desc>
chg_cell_element dtx_required <value> <cell_desc>

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
68P02901W23-Q 5-215
dtx_required Chapter 5: CM database parameters
References
GSM parameter DTX

GSM specification 4.08 - 10.5.2.3, figure 10.22, table 10.16
5-216 68P02901W23-Q
Technical Description: BSS Command Reference dual_band_offset
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.
Dependencies This parameter may be modified only when the Dual Band Cells
feature is unrestricted.
Syntax

chg_cell_element <location> dual_band_offset <value>

disp_element dual_band_offset <location> <cell_desc>
Values
Value type Integer

Default value 0
68P02901W23-Q 5-217
dyn_step_adj Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_element dyn_step_adj <value> <location> <cell_desc>
chg_cell_element dyn_step_adj <value> <cell_desc>

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
5-218 68P02901W23-Q
Technical Description: BSS Command Reference dyn_step_adj_fmpr
dyn_step_adj_fmpr
Description
The dyn_step_adj_fmpr parameter specifies the percentage power reduction used in

the dynamic power reduction calculation.
Dependencies None
Syntax

chg_element dyn_step_adj_fmpr <value> <location> <cell_desc>
chg_cell_element dyn_step_adj_fmpr <value> <cell_desc>

disp_element dyn_step_adj_fmpr <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 10
Default value 10
68P02901W23-Q 5-219
dynet_tchs_reserved Chapter 5: CM database parameters
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 then 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.

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 will reject the command if the cell_desc equals all.
The Dynamic Allocation feature must be in operation.
Syntax

chg_element dynet_tchs_reserved <value> <location> <cell_desc>

disp_element dynet_tchs_reserved <location> <cell_desc>
5-220 68P02901W23-Q
Technical Description: BSS Command Reference dynet_tchs_reserved
Values
Value type Integer (representing the number of reserved TCHs)

Valid range 0 to 32
Default value 0
68P02901W23-Q 5-221
eac_mode Chapter 5: CM database parameters
eac_mode
Description
The eac_mode parameter enables or disables the Enhanced Auto-Connect (EAC) mode. When this mode
is enabled, the BSC-RXCDR interface allocates 8 kbit/s Aters where appropriate.
Dependencies The AMR Enhanced Capacity {22064} and/or GSM Half Rate
This parameter can be modified inside and outside sysgen mode.
An AXCDR device cannot be in EAC mode if CIC validation is
disabled.
An AXCDR device cannot be in EAC mode if any KSW is in B-U
state in the RXCDR or BSC.
cic_unblock_thresh parameter by a value of not less than 10,
except when both thresholds are set to 0 (disabled).
Syntax

modify_value 0 eac_mode <value> AXCDR <axcdr_id>
equip 0 AXCDR
5-222 68P02901W23-Q
Technical Description: BSS Command Reference eac_mode
• device ID.
• CIC validation.
• EAC mode.

Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-223
early_classmark_sending Chapter 5: CM database parameters
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.

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

chg_element early_classmark_sending <value> 0

disp_element early_classmark_sending 0
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
5-224 68P02901W23-Q
Technical Description: BSS Command Reference early_classmark_sending
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, neighbours are reported by the BSS to the MS as follows:
Handover from GSM900 to GSM900 - only the GSM900 neighbours
Handover from GSM1800 to GSM1800 - only the GSM1800 neighbours.
External multiband capabilities will be limited, and subsequent handovers to GSM1800
cells are therefore not possible.
References
GSM specification TS GSM 04.08, section 10.5.2.34

68P02901W23-Q 5-225
eas_alarm Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_eas_alarm <alarm_table_index> <alarm_severity_level>
"<eas_alarm_text>"

disp_element eas_alarm,<index> <location>
Values
Value type Text

Valid range Up to 24 alphanumeric characters (including spaces)
Default value None
5-226 68P02901W23-Q
Technical Description: BSS Command Reference eas_alarm_type
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.
Dependencies None
Syntax

equip <location> eas
map_eas_opto <location> <device_id> [<opt_#1> <alarm_table_index>]
...[<opt_#8> <alarm_table_index>]

disp_element eas_alarm_type,<index> <location>
Values
Value type Integer

Valid range 0 to 33
Default value None
68P02901W23-Q 5-227
eas_report_opto Chapter 5: CM database parameters
eas_report_opto
Description
The eas_report_opto parameter specifies whether or not each of the eight optocouplers
(optos) on a specific PIX card will report 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.
Dependencies None
Syntax

chg_eas_report <location> <device_id> [ on = [<opto_#1>]...[<opto_#n>]
] [ off = [opto_#1>]...[<opto_#n>] ]

disp_element eas_report_opto,<index> <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None
5-228 68P02901W23-Q
Technical Description: BSS Command Reference eas_severity
eas_severity
Description
The eas_severity parameter specifies the severity level component of the EAS (Ex-
ternal 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.
Dependencies None
Syntax

chg_eas_alarm <alarm_table_index>
<alarm_severity_level> "<new_alarm_string>"
chg_element eas_severity,<index> <value> <location>

disp_element eas_severity,<index> <location>
Values
Value type Integer

Valid range 0 to 4
0 Investigate
68P02901W23-Q 5-229
eas_severity Chapter 5: CM database parameters
1 Critical
2 Major
3 Minor
4 Warning
Default value None
5-230 68P02901W23-Q
Technical Description: BSS Command Reference efr_enabled
efr_enabled
Description
The efr_enabled parameter enables or disables the Enhanced Full Rate (EFR).
Dependencies The EFR feature must be unrestricted.
This parameter cannot be enabled if the handover_re-
quired_sp_ver_used parameter is disabled.
This parameter is only valid at a BSC location.
Syntax

modify_value efr_enabled <value> 0

disp_element efr_enabled 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-231
efr_enabled Chapter 5: CM database parameters
References
GSM specification TS GSM 04.08 [2], TS GSM 08.08 [3],

TS GSM 08.058 [4]
5-232 68P02901W23-Q
Technical Description: BSS Command Reference egprs_init_dl_cs
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.
Dependencies The EGPRS feature must be unrestricted.
Syntax

chg_element egprs_init_dl_cs <value> <location> <cell_desc>
chg_cell_element egprs_init_dl_cs <value> <cell_desc>

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
68P02901W23-Q 5-233
egprs_init_dl_cs Chapter 5: CM database parameters

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.
5-234 68P02901W23-Q
Technical Description: BSS Command Reference egprs_init_ul_cs
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
Syntax

chg_element egprs_init_ul_cs <value> <location> <cell_desc>
chg_cell_element egprs_init_ul_cs <value> <cell_desc>

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
68P02901W23-Q 5-235
egprs_init_ul_cs Chapter 5: CM database parameters

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.
5-236 68P02901W23-Q
Technical Description: BSS Command Reference egsm_bcch_sd
egsm_bcch_sd
Description
The egsm_bcch_sd parameter specifies whether or not the cell is configured for both BCCH carriers
and the placement of SDCCH channels for the Extended GSM (EGSM) cell.
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 neighbour 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

chg_element egsm_bcch_sd <value> <location> <cell_desc>
chg_cell_element egsm_bcch_sd <value> <cell_desc>

disp_element egsm_bcch_sd <location> <cell_desc>
68P02901W23-Q 5-237
egsm_bcch_sd Chapter 5: CM database parameters
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-238 68P02901W23-Q
Technical Description: BSS Command Reference egsm_handover_threshold
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.
Dependencies This parameter may only be changed on EGSM systems.
Syntax

chg_element egsm_handover_threshold <value> <location> <cell_desc>
chg_cell_element egsm_handover_threshold <value> <cell_desc>

disp_element egsm_handover_threshold <location> <cell_desc>
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.
are allowed.
68P02901W23-Q 5-239
egsm_handover_threshold Chapter 5: CM database parameters

are allowed.
are allowed.
Default value 0
5-240 68P02901W23-Q
Technical Description: BSS Command Reference emergency_class_switch
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.
Dependencies cell_bar_access_class
Syntax

chg_element emergency_class_switch <value> <location> <cell_desc>
chg_cell_element emergency_class_switch <value> <cell_desc>

disp_element emergency_class_switch <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-241
emergency_class_switch Chapter 5: CM database parameters
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
5-242 68P02901W23-Q
Technical Description: BSS Command Reference en_incom_ho
en_incom_ho
Description
The en_incom_ho parameter enables or disables incoming handovers based on whether or not the cell is barred.
Dependencies None
Syntax

chg_element en_incom_ho <value> <location> <cell_desc>
chg_cell_element en_incom_ho <value> <cell_desc>

disp_element en_incom_ho <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-243
en_incom_ho Chapter 5: CM database parameters
References
GSM specification GSM TS 03.22 section 3.5.1

5-244 68P02901W23-Q
Technical Description: BSS Command Reference enhanced_relief
enhanced_relief
Description
The enhanced_relief parameter enables or disables the Intelligent Congestion Relief feature.
Dependencies The Congestion Relief feature must be unrestricted.
Syntax

chg_element enhanced_relief <value> <location> <cell_desc>

disp_element enhanced_relief <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-245
eop_enabled Chapter 5: CM database parameters
eop_enabled
Description
The eop_enabled parameter enables or disables the One Phase Access feature.
Dependencies To enable One Phase Access, this feature must be unrestricted.
Syntax

chg_element eop_enabled <value> <location>

disp_element eop_enabled <location>
Values
Value type Boolean

Valid range 0 or 1
0 EOP disabled
1 EOP enabled
Default value 0
5-246 68P02901W23-Q
Technical Description: BSS Command Reference erc_ta_priority
erc_ta_priority
Description
The erc_ta_priority parameter specifies the priority threshold for extended range cell neighbour. If the absolute
timing advance is greater than the priority threshold, the ERC neighbours are placed at the top of the list of
sorted handover candidates. Otherwise, the ERC neighbours are appended to the end of the list of candidates.
Dependencies None
Syntax

chg_element erc_ta_priority <value> <location> <cell_desc>

disp_element erc_ta_priority <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 63
Default value 50
68P02901W23-Q 5-247
ext_range_cell Chapter 5: 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)
Dependencies The ext_range_cell parameter cannot be changed if the Extended

Range Cells feature is restricted.This parameter can not 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

chg_cell_element ext_range_cell <value> <cell_desc>
The system displays the following prompt:
Enter handover threshold mobile max range:

disp_element ext_range_cell <location> <cell_desc>
5-248 68P02901W23-Q
Technical Description: BSS Command Reference ext_range_cell
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-Q 5-249
extended_paging_active Chapter 5: CM database parameters
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 analyse
messages for its paging group and the group two paging blocks later.
When disabled, extended page is not allowed.
Dependencies None
Syntax

chg_element extended_paging_active <value> <location> <cell_desc>
chg_cell_element extended_paging_active <value> <cell_desc>

disp_element extended_paging_active <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
5-250 68P02901W23-Q
Technical Description: BSS Command Reference extended_paging_active
1 Enabled
Default value 0
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.
68P02901W23-Q 5-251
fdd_qmin Chapter 5: CM database parameters
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.
Dependencies The BSS Inter-RAT feature must be unrestricted.
Syntax

chg_element fdd_qmin <value> <location> <cell_desc>
chg_cell_element fdd_qmin <value> <cell_desc>

disp_element fdd_qmin <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 7
Default value 0
5-252 68P02901W23-Q
Technical Description: BSS Command Reference fdd_qoffset
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.
Syntax

chg_element fdd_qoffset <value> <location> <cell_desc>
chg_cell_element fdd_qoffset <value> <cell_desc>

disp_element fdd_qoffset <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 15
Default value 8
68P02901W23-Q 5-253
force_hr_usage Chapter 5: CM database parameters
force_hr_usage
Description
The {22064}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.
Dependencies The AMR feature {22064} and/or the GSM Half Rate feature must
be unrestricted.
Syntax

{22064}
chg_element force_hr_usage <value> <location>

{22064}
disp_element force_hr_usage <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-254 68P02901W23-Q
Technical Description: BSS Command Reference frequency_type
frequency_type
Description
The frequency_type parameter specifies the frequency type of a cell.

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 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.
68P02901W23-Q 5-255
frequency_type Chapter 5: CM database parameters
Syntax

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>
The chg_cell_element command accepts only numeric values for frequency_type.

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
5-256 68P02901W23-Q
Technical Description: BSS Command Reference full_pwr_rfloss
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.
Dependencies None
Syntax

add_cell <gsm_cell_id>
chg_element full_pwr_rfloss <value> <location> <cell_desc>
chg_cell_element full_pwr_rfloss <value> <cell_desc>

disp_element full_pwr_rfloss <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-257
gci_error_clr_thresh Chapter 5: CM database parameters
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).
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 might be too
thus clearing the alarm prematurely.)
the next successful time period occurs.
Syntax

chg_element gci_error_clr_thresh <value> 0

disp_element gci_error_clr_thresh 0
Values
Value type Integer

Default value 0
5-258 68P02901W23-Q
Technical Description: BSS Command Reference gci_error_gen_thresh
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).
occurs. The new threshold takes effect only when the GCI error
count changes.
Syntax

chg_element gci_error_gen_thresh <value> 0

disp_element gci_error_gen_thresh 0
Values
Value type Integer

Default value 6
68P02901W23-Q 5-259
gci_error_inc Chapter 5: CM database parameters
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.
Syntax

chg_element gci_error_inc <value> 0

disp_element gci_error_inc 0
Values
Value type Integer

Valid range 0 GCI alarms not raised
1 to 255 GCI alarms raised
5-260 68P02901W23-Q
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.
Dependencies The Fast GCLK Warmup feature must be unrestricted.
The GCLK version must be V9 or later.
Syntax

chg_element gclk_qwarm_flag <value> <location>

disp_element gclk_qwarm_flag <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-261
global_reset_repetitions Chapter 5: 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 Acknowledgement for Global Reset is generated.
This parameter applies to only BSC sites.
Syntax

chg_element global_reset_repetitions <value> 0

disp_element global_reset_repetitions 0
Values
Value type Integer (number of repetitions)

Default value 0
5-262 68P02901W23-Q
Technical Description: BSS Command Reference global_reset_repetitions
References

68P02901W23-Q 5-263
gproc_slots Chapter 5: 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 should be
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.
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

chg_element gproc_slots <value> <location>

disp_element gproc_slots <location>
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
5-264 68P02901W23-Q
Technical Description: BSS Command Reference gproc_slots
If gproc_slots is greater than 16, the system displays the following warning: “COMMAND
ACCEPTED: WARNING: Specified value requires GPROC2 or GPROC3 boards."
68P02901W23-Q 5-265
gprs_alarm_time Chapter 5: 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.
This parameter applies to only BSC sites.
Syntax

chg_element gprs_alarm_time <value> 0

disp_element gprs_alarm_time 0
Values
Value type Integer

Valid ranges 0 If GPRS or ECERM are 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.
5-266 68P02901W23-Q
Technical Description: BSS Command Reference gprs_bs_cv_max
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.
BSS software processes using this parameter are notified immediately after the change is made.
Syntax

chg_element gprs_bs_cv_max <value> <location> <cell_desc>
chg_cell_element gprs_bs_cv_max <value> <cell_desc>

disp_element gprs_bs_cv_max <location> <cell_desc>
Values
Value type Integer (blocks)

Valid range 0 to 15
Default value 6
68P02901W23-Q 5-267
gprs_cell_cgt_thr Chapter 5: CM database parameters
gprs_cell_cgt_thr
Description
The gprs_cell_cgt_thr parameter specifies the threshold at which the PCU attempts congestion
relief for a cell, as a number of MSs per timeslot in the cell.
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.
PCU software processes using this parameter are notified immediately after the change is made.
Syntax

chg_element gprs_cell_cgt_thr <value> <location> <cell_id>
chg_cell_element gprs_cell_cgt_thr <value> <cell_id>

disp_element gprs_cell_cgt_thr <location> [<cell_id>]
disp_cell <cell_id> "full"
5-268 68P02901W23-Q
Technical Description: BSS Command Reference gprs_cell_cgt_thr
Values
Value type Integer

Valid ranges 1 to 4 MS(s) per timeslot in the cell.
Default values 2
References
GSM parameter None.

68P02901W23-Q 5-269
gprs_cell_reselect_hysteresis Chapter 5: CM database parameters
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).
Syntax

chg_element gprs_cell_reselect_hysteresis <value> <location> <cell_desc>
chg_cell_element gprs_cell_reselect_hysteresis <value> <cell_desc>

disp_cell <cell_number> “full"
disp_element gprs_cell_reselect_hysteresis <location> <cell_desc>
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-270 68P02901W23-Q
Technical Description: BSS Command Reference gprs_cell_reselect_hysteresis
5 10 dB
6 12 dB
7 14 dB
Default value 0 (0 dB)
68P02901W23-Q 5-271
gprs_com_ms_class Chapter 5: CM database parameters
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.
Syntax

chg_element gprs_com_ms_class <value> <location>

disp_element gprs_com_ms_class <location>
Values
Value type Integer

Valid range 1, 2, 4, 8
Default value 8
5-272 68P02901W23-Q
Technical Description: BSS Command Reference gprs_cr_margin
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 cell’s rxlev and the serving cell’s value of rxlev_access_min is less than the gprs_cr_margin.
unrestricted.
Syntax

chg_element gprs_cr_margin <value> <location> <cell_id>
chg_cell_element gprs_cr_margin <value> <cell_id>

disp_element gprs_cr_margin <location> [<cell_id>]
disp_cell <cell_id> "full"
68P02901W23-Q 5-273
gprs_cr_margin Chapter 5: CM database parameters
Values
Value type Integer

Valid ranges 5 to 40 dB
Default values 30 dB
References
GSM parameter None.

5-274 68P02901W23-Q
Technical Description: BSS Command Reference gprs_dl_pwr_mode
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.
This parameter can be set to a value of 1 (mode A) or a value of 2
(mode B) only when gprs_pc_meas_chan is set to 0 (BCCH).
This parameter cannot be set to 2 (mode B) when gprs_mac_mode
is set to 1 (dynamic mode).
Syntax

chg_element gprs_dl_pwr_mode <value> bsc

disp_element gprs_dl_pwr_mode bsc
Values
Value type Integer

Valid range 0 to 2
0 No power mode
1 Mode A
68P02901W23-Q 5-275
gprs_dl_pwr_mode Chapter 5: CM database parameters
2 Mode B
Default value 1
5-276 68P02901W23-Q
Technical Description: BSS Command Reference gprs_drx_timer_max
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.
Syntax

chg_element gprs_drx_timer_max <value> <location> <cell_desc>
chg_cell_element gprs_drx_timer_max <value> <cell_desc>

disp_element gprs_drx_timer_max <location> <cell_desc>
68P02901W23-Q 5-277
gprs_drx_timer_max Chapter 5: CM database parameters
Values

Valid range 0 to 3
Default value 0
5-278 68P02901W23-Q
Technical Description: BSS Command Reference gprs_enabled
gprs_enabled
Description
The gprs_enabled parameter specifies whether or not 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.
At least one PCU must be equipped. A prompt will request 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 colour must have been configured for the cell; see
the ra_colour parameter in"ra_colour" on page 5-638 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 will be 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 5-309)
using the chg_element command.
68P02901W23-Q 5-279
gprs_enabled Chapter 5: CM database parameters
Syntax

chg_cell_element gprs_enabled <value> <cell-desc>
chg_cell_element <location> gprs_enabled <value> all

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
5-280 68P02901W23-Q
Technical Description: BSS Command Reference gprs_intraho_allwd
gprs_intraho_allwd
Description
The gprs_intraho_allwd parameter specifies whether or not 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.
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.
Syntax

chg_element gprs_intraho_allwd <value> <location> <cell_desc>
chg_cell_element gprs_intraho_allwd <value> <cell_desc>

disp_cell <cell_desc> <"full">
disp_element gprs_intraho_allwd <location> <cell_desc>
68P02901W23-Q 5-281
gprs_intraho_allwd Chapter 5: CM database parameters
Values
Value type Integer

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1
5-282 68P02901W23-Q
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.
Syntax

chg_element gprs_mac_mode <value> bsc

disp_element gprs_mac_mode bsc
Values
Value type Boolean

Valid range 1 Dynamic mode
68P02901W23-Q 5-283
gprs_max_ul_ts Chapter 5: CM database parameters
gprs_max_ul_ts
Description
The gprs_max_ul_ts parameter enables the operator to configure the maximum number of
uplink timeslots supported for each mobile on a BSS basis.
Syntax

chg_element gprs_max_ul_ts <value> <location>

disp_element gprs_max_ul_ts <location>
Values
Value type Integer

Valid range 1 to 2
Default value 2
5-284 68P02901W23-Q
Technical Description: BSS Command Reference gprs_min_prr_blks
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.
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>

disp_element gprs_min_prr_blks <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 24
Default value 0
68P02901W23-Q 5-285
gprs_ms_pan_dec Chapter 5: CM database parameters
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.
Syntax

chg_element gprs_ms_pan_dec <value> <location> <cell_desc>
chg_cell_element gprs_ms_pan_dec <value> <cell_desc>

disp_element gprs_ms_pan_dec <location> <cell_desc>
5-286 68P02901W23-Q
Technical Description: BSS Command Reference gprs_ms_pan_dec
Values
Value type Integer

Valid range 0 to 7
Default value 1
References
GSM parameter None.

GSM technical specification 04.60
68P02901W23-Q 5-287
gprs_ms_pan_inc Chapter 5: CM database parameters
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.
Syntax

chg_element gprs_ms_pan_inc <value> <location> <cell_desc>
chg_cell_element gprs_ms_pan_inc <value> <cell_desc>

disp_element gprs_ms_pan_inc <location> <cell_desc>
5-288 68P02901W23-Q
Technical Description: BSS Command Reference gprs_ms_pan_inc
Values
Value type Integer

Valid range 0 to 7
Default value 1
References
GSM parameter None.

68P02901W23-Q 5-289
gprs_ms_pan_max Chapter 5: CM database parameters
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.
Syntax

chg_element gprs_ms_pan_max <value> <location> <cell_desc>
chg_cell_element gprs_ms_pan_max <value> <cell_desc>

disp_element gprs_ms_pan_max <location> <cell_desc>
5-290 68P02901W23-Q
Technical Description: BSS Command Reference gprs_ms_pan_max
Values
Value type Integer

Valid range 0 to 7
Default value 3
References
GSM parameter None.

GSM technical specification 04.60
68P02901W23-Q 5-291
gprs_ms_txpwr_max_cch Chapter 5: CM database parameters
gprs_ms_txpwr_max_cch
Description
The gprs_ms_txpwr_max_cch parameter specifies the maximum random access power available for a 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.
Dependencies The cell frequency_type.
The PBCCH/PCCCH optional feature must be unrestricted.
Syntax

chg_element gprs_ms_txpwr_max_cch <value> <location> <cell_desc>
chg_cell_element gprs_ms_txpwr_max_cch <value> <cell_desc>

disp_cell <cell_desc> “full"
disp_element gprs_ms_txpwr_max_cch <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 31 For PGSM, EGSM and GSM850 cells in 2 dBm steps as shown
in Table 5-11:
2 to 28 For DCS1800 cells in 2 dBm steps as shown in Table 5-12:
5-292 68P02901W23-Q
Technical Description: BSS Command Reference gprs_ms_txpwr_max_cch
0 to 15, 30, For PCS1900 cells as shown in Table 5-13:

31
Default value 2 (For PGSM, EGSM and GSM850 cells).
0 (For DCS1800 cells).
30 (For PCS1900 cells).
Table 5-11 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 5-12 Maximum mobile power level for DCS1800 cells

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
Table 5-13 Maximum mobile power level for PCS1900 cells

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
68P02901W23-Q 5-293
gprs_ms_txpwr_max_cch Chapter 5: CM database parameters
Table 5-13 Maximum mobile power level for PCS1900 cells (Continued)
3 24 dBm 12 6 dBm
4 22 dBm 13 4 dBm
5 20 dBm 14 2 dBm
6 18 dBm 15 0 dBm
5-294 68P02901W23-Q
Technical Description: BSS Command Reference gprs_network_operation_mode
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 5-14 shows the two permissible modes.
Table 5-14 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 a MS must monitor both the CCH for CS pages and
PCCH for PS pages. No paging coordination is done by the network.
Network Operation Mode 2 is not supported by the BSS.

Syntax

chg_element gprs_ network_operation_mode <value> bsc
68P02901W23-Q 5-295
gprs_network_operation_mode Chapter 5: CM database parameters

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
5-296 68P02901W23-Q
Technical Description: BSS Command Reference gprs_num_pmrs
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.
unrestricted.
Syntax

chg_element gprs_num_pmrs <value> <location> <cell_id>
chg_cell_element gprs_num_pmrs <value> <cell_id>

disp_element gprs_num_pmrs <location> [<cell_id>]
disp_cell gprs_num_pmrs <cell_id> "full"
68P02901W23-Q 5-297
gprs_num_pmrs Chapter 5: CM database parameters
Values
Value type Integer

Valid ranges 1 to 10 Number of bad PMRs.
Default values 3
References
GSM parameter None.

5-298 68P02901W23-Q
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.
Syntax

chg_element gprs_pb <value> <location> <cell_desc>
chg_cell_element gprs_pb <value> <cell_desc>

disp_element gprs_pb <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 16
Default value 1
68P02901W23-Q 5-299
gprs_pc_alpha Chapter 5: 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.
Syntax

chg_element gprs_pc_alpha <value> <location> <cell_desc>
chg_cell_element gprs_pc_alpha <value> <cell_desc>

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
5-300 68P02901W23-Q
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 in order to control the uplink power.
Syntax

chg_element gprs_pc_meas_chan <value> <location> <cell_desc>
chg_cell_element gprs_pc_meas_chan <value> <cell_desc>

disp_element gprs_pc_meas_chan <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
0 BCCH
68P02901W23-Q 5-301
gprs_pc_meas_chan Chapter 5: CM database parameters
1 PDCH
Default value 0
5-302 68P02901W23-Q
Technical Description: BSS Command Reference gprs_reconfig_thresh_idle_tch
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 switchable timeslot is reconfigured
as a Packet Data Traffic Channel (PDTCH).
Syntax

chg_element gprs_reconfig_thresh_idle_tch <value> <location> <cell_desc>
chg_cell_element gprs_reconfig_thresh_idle_tch <value> <cell_desc>

disp_element gprs_reconfig_thresh_idle_tch <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 5
Default value 1
68P02901W23-Q 5-303
gprs_reselect_offset Chapter 5: 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.
Dependencies The PBCCH/PCCCH feature must be unrestricted.
Syntax

chg_element gprs_reselect_offset <value> <location> <cell_desc>
chg_cell_element gprs_reselect_offset <value> <cell_desc>

disp_element gprs_reselect_offset <location> <cell_desc>
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
... ...
5-304 68P02901W23-Q
Technical Description: BSS Command Reference gprs_reselect_offset
16 0 dB
... ...
20 +4 dB
21 +8 dB
... ...
31 +48 dB
68P02901W23-Q 5-305
gprs_rxlev_access_min Chapter 5: 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.
Syntax

chg_element gprs_rxlev_access_min <value> <location> <cell_desc>
chg_cell_element gprs_rxlev_access_min <value> <cell_desc>

disp_element gprs_rxlev_access_min <location> <cell_desc>
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
... ...
5-306 68P02901W23-Q
Technical Description: BSS Command Reference gprs_rxlev_access_min
63 -47 dBm and higher

Default value 0
68P02901W23-Q 5-307
gprs_sched_beta Chapter 5: CM database parameters
gprs_sched_beta
Description
The gprs_sched_beta parameter sets the scheduling beta algorithm at the BSS. The possible algorithms are:
0 - Each MS throughput in bits per second (bit/s) is the same
1 - Each MS transfers the same number of blocks as every other mobile.
2 - A MS with a higher coding scheme is preferred.
Supported by OMC-R GUI Yes (Read-Write)
This parameter is only available at the BSC.
Syntax

chg_element gprs_sched_beta <value> 0

disp_element gprs_sched_beta 0
Value
Value type Integer

Valid range 0 to 2
0 Each MS throughput in bit/s is the same.
1 Each MS transfers the same number of blocks as every other mobile.
2 MS with higher coding scheme is preferred.
Default value 1
5-308 68P02901W23-Q
Technical Description: BSS Command Reference gprs_sig_bvci
gprs_sig_bvci
Description
The gprs_sig_bvci parameter specifies the BVCI of the signalling source used with GBLs.
Syntax

chg_element gprs_sig_bvci <value> pcu

disp_element gprs_sig_bvci pcu
Values
Value type Integer

Default value 0
68P02901W23-Q 5-309
gprs_temporary_offset Chapter 5: CM database parameters
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.
Syntax

chg_element gprs_temporary_offset <value> <location> <cell_desc>
chg_cell_element gprs_temporary_offset <value> <cell_desc>

disp_element gprs_temporary_offset <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 7
0 0 dB
1 10 dB
2 20 dB
3 30 dB
5-310 68P02901W23-Q
Technical Description: BSS Command Reference gprs_temporary_offset
4 40 dB
5 50 dB
6 60 dB
7 Infinity
Default value 0
68P02901W23-Q 5-311
gprs_ts_config_alg Chapter 5: CM database parameters
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.
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.
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.
BSS software processes using this parameter are notified immediately

after the change is made.
Syntax

chg_element gprs_ts_config_alg <value> <location> <cell_desc>
chg_cell_element gprs_ts_config_alg <value> <cell_desc>
5-312 68P02901W23-Q
Technical Description: BSS Command Reference gprs_ts_config_alg

disp_element gprs_ts_config_alg <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
0 PCU performance algorithm
1 Customer specified algorithm
Default value 0
68P02901W23-Q 5-313
gprs_ul_dl_bias Chapter 5: CM database parameters
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.
Syntax

chg_element gprs_ul_dl_bias <value> <location>

disp_element gprs_ul_dl_bias <location>
Values
Value type Integer

Valid range 0 to 1
0 UL bias
1 DL bias
Default value 1
5-314 68P02901W23-Q
Technical Description: BSS Command Reference group_block_unblock_allowed
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

Dependencies This parameter is only valid at the BSC. This parameter does not
apply to RXCDR sites.
Syntax

chg_element group_block_unblock_allowed <value> 0

disp_element group_block_unblock_allowed 0
Values
Value type Boolean

Valid range 0 or 1
68P02901W23-Q 5-315
group_block_unblock_allowed Chapter 5: CM database parameters
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

5-316 68P02901W23-Q
Technical Description: BSS Command Reference gsl_lcf_mapping
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.
The system must be in SYSGEN mode.
Syntax

chg_element gsl_lcf_mapping <value> bsc

disp_element gsl_lcf_mapping bsc
Values
Value type Boolean

Valid range 0 or 1
0 Manual mode
1 Auto mode
68P02901W23-Q 5-317
gsl_lcf_mapping Chapter 5: CM database parameters
Default value 1 Inside SYSGEN (Auto mode - 0 cannot be set)

0 Outside SYSGEN (Manual mode)
5-318 68P02901W23-Q
Technical Description: BSS Command Reference gsm_bss_half_rate_enabled
gsm_bss_half_rate_enabled
{22064}
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 of Sysgen mode
when there is no AXCDR device with CIC validation enabled.
Dependencies The GSM Half Rate feature must be unrestricted.
handover_required_sp_ver_used must be enabled.
Syntax

chg_element gsm_bss_half_rate_enabled <value> <location>
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.
disp_element gsm_bss_half_rate_enabled <location>
68P02901W23-Q 5-319
gsm_bss_half_rate_enabled Chapter 5: CM database parameters
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0 Disabled
5-320 68P02901W23-Q
Technical Description: BSS Command Reference gsm_cell_id_format
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.
Dependencies This parameter can be set only at the BSC.
Syntax

chg_element gsm_cell_id_format <value> 0

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
68P02901W23-Q 5-321
gsm_cell_id_format Chapter 5: CM database parameters
UTRAN Cell Identifier
It is possible to hand over calls to 3G UMTS UTRAN cells. This is set up using the neighbour commands:
add_neighbor, modify_neighbor, del_neighbor and 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

5-322 68P02901W23-Q
Technical Description: BSS Command Reference gsm_half_rate_enabled
gsm_half_rate_enabled
{22064}
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.
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

chg_element gsm_half_rate_enabled <value> <location> <cell_desc>
chg_cell_element gsm_half_rate_enabled <value> <cell_desc>

disp_element gsm_half_rate_enabled <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
68P02901W23-Q 5-323
gsm_half_rate_enabled Chapter 5: CM database parameters
0 Disabled
1 Enabled
Default value 0 Disabled
5-324 68P02901W23-Q
Technical Description: BSS Command Reference half_rate_enabled
half_rate_enabled
Description
{22064}
The half_rate_enabled parameter enables or disables Half Rate at a 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.
Cell numbers required {22064} No
Dependencies The AMR feature {22064}and/or GSM Half Rate feature must be
unrestricted.
{22064}
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, Horizonmacro2 and
M-Cell6 cabinets.
The half_rate_enabled RTF parameter is only prompted for during
the equipage of an RTF.
Syntax

{22064}

{22064}
disp_equipment <location> rtf <rtf_id1> <rtf_id2>
68P02901W23-Q 5-325
half_rate_enabled Chapter 5: CM database parameters
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-326 68P02901W23-Q
Technical Description: BSS Command Reference handover_power_level
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.
Dependencies The maximum value for a PGSM or EGSM system is 19.
The maximum value for a DCS1800 system is 15.
Syntax

chg_element handover_power_level <value> <location> <cell_desc>
chg_cell_element <location> handover_power_level <value> <cell_desc>

disp_element handover_power_level <location> <cell_desc>
Values
Value type Integer

Valid ranges
Table 5-15 lists the maximum MS power level for PGSM and EGSM cells.
68P02901W23-Q 5-327
handover_power_level Chapter 5: CM database parameters
Table 5-15 Max MS power level for PGSM and EGSM
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 5-16 lists the maximum mobile power level for DCS1800 and PCS1900 cells.
Table 5-16 Max MS power level for DCS1800 and PCS1900 cells

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 5-17 lists the maximum mobile power level for DCS1800 and PCS1900 cells for class 3 mobiles.
Table 5-17 Max MS power level for class 3 mobiles

29 36 dBm 31 32 dBm
30 34 dBm
Default value 2
5-328 68P02901W23-Q
Technical Description: BSS Command Reference handover_power_level
References
GSM specification 5.05 - 4.1.1

68P02901W23-Q 5-329
handover_required_curr_ch Chapter 5: CM database parameters
handover_required_curr_ch
Description
The handover_required_curr_ch parameter specifies whether or not the optional message element
current channel is included in the Handover Required message to the MSC.
This parameter should conform to the MSC capabilities.
Syntax

chg_element handover_required_curr_ch <value> 0

disp_element handover_required_curr_ch 0
Values
Value type Boolean

Valid range 0 or 1
0 Not included
1 Included
Default value 1
5-330 68P02901W23-Q
Technical Description: BSS Command Reference handover_required_curr_ch
References

68P02901W23-Q 5-331
handover_required_reject_switch Chapter 5: 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 will
not be included in the Handover Required message. On receipt of the Handover Required Reject
message the BSS will perform an internal handover if there are valid candidates.
If the handover_required_reject_switch is disabled (set to 0), the BSS will not expect
to receive a Handover Required Reject message from the switch and will include internal
candidates in the Handover Required message.
Syntax

chg_element handover_required_reject_switch <value> 0

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 0
5-332 68P02901W23-Q
Technical Description: BSS Command Reference handover_required_reject_switch
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-Q 5-333
handover_required_sp_ver_used Chapter 5: CM database parameters
handover_required_sp_ver_used
Description
The handover_required_sp_ver_used parameter determines whether or not the optional element

speech_version_used can be built into the Handover Required message.
{22064} An attempt to disable (0) handover_required_sp_ver_used is rejected
if GSM Half Rate is enabled in the BSS.
Dependencies The handover_required_sp_ver_used parameter cannot
be disabled (0) if either efr_enabled {22064} or
gsm_bss_half_rate_enabled is enabled (1).
Syntax

chg_element handover_required_sp_ver_used <value> 0

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
5-334 68P02901W23-Q
Technical Description: BSS Command Reference handover_required_sp_ver_used
References

68P02901W23-Q 5-335
hcs_thr Chapter 5: 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.
Dependencies The PBCCH/PCCCH feature must be unrestricted.
If the local_maintenance flag is disabled, the MMI is prevented
from changing this item.
Syntax

chg_element hcs_thr <value> <location> <cell_desc>
chg_cell_element hcs_thr <value> <cell_desc>

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
5-336 68P02901W23-Q
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.
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

chg_element hdsl_losw_oos <value> <location>

disp_element hdsl_losw_oos <location>
Values

Default value 6
68P02901W23-Q 5-337
hdsl_losw_restore Chapter 5: 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).
Dependencies This parameter may only be changed if the HDSL option is
unrestricted.
Syntax

chg_element hdsl_losw_restore <value> <location>

disp_element hdsl_losw_restore <location>
Values

Default value 6
5-338 68P02901W23-Q
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.
unrestricted.
Syntax

chg_element hdsl_snr_daily <value> <location>

disp_element hdsl_snr_daily <location>
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
68P02901W23-Q 5-339
hdsl_snr_daily Chapter 5: CM database parameters
... ...
... ...
... ...
44 22 dB
5-340 68P02901W23-Q
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.
unrestricted.
Syntax

chg_element hdsl_snr_daily_mon_period <value> <location>

disp_element hdsl_snr_daily_mon_period <location>
Values

Default value 20
68P02901W23-Q 5-341
hdsl_snr_hourly Chapter 5: 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.
unrestricted.
All slave modem alarm thresholds are identical to the master modem
alarm thresholds.
Syntax

chg_element hdsl_snr_hourly <value> <location>

disp_element hdsl_snr_hourly <location>
Values
Value type Integer (representing 0.5dB steps)

8 4 dB
9 4.5 dB
10 5 dB
5-342 68P02901W23-Q
Technical Description: BSS Command Reference hdsl_snr_hourly
... ...
... ...
... ...
44 22 dB
68P02901W23-Q 5-343
hdsl_snr_hourly_mon_period Chapter 5: 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.
unrestricted.
msi_type niu_hdsl at the local M-Cellcity or Horizonmicro site.
Syntax

chg_element hdsl_snr_hourly_mon_period <value> <location>

disp_element hdsl_snr_hourly_mon_period <location>
Values

Default value 20
5-344 68P02901W23-Q
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 SNL level is continuously monitored by the system. 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).
Dependencies This parameter may be changed only if the HDSL option is
unrestricted.
This parameter may be changed only at an M-Cellcity, Horizonmicro
The hdsl_snr_oos threshold must be lower than the
hdsl_snr_restore threshold.
Syntax

chg_element hdsl_snr_oos <value> <location>

disp_element hdsl_snr_oos <location>
68P02901W23-Q 5-345
hdsl_snr_oos Chapter 5: CM database parameters
Values
Value type Integer (0.5dB steps)

6 3 dB
7 3.5 dB
8 4 dB
... ...
... ...
... ...
44 22 dB
5-346 68P02901W23-Q
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 SNL level is continuously monitored by the system. 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.
unrestricted.
This parameter may be changed only at an M-Cellcity, Horizonmicro
The hdsl_snr_oos threshold must be lower than the
hdsl_snr_restore threshold.
Syntax

chg_element hdsl_snr_restore <value> <location>

disp_element hdsl_snr_restore <location>
68P02901W23-Q 5-347
hdsl_snr_restore Chapter 5: CM database parameters
Values
Value type Integer (0.5dB steps)

6 3 dB
7 3.5 dB
8 4 dB
... ...
... ...
... ...
44 22 dB
5-348 68P02901W23-Q
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 handover as many calls as the number of queued assignment requests.
• Attempt to handover as many calls as meet the congestion handover criteria.
• No handover attempts (for this condition).
This parameter will be copied if the copy_cell command is used.

Dependencies Congestion Relief feature is required.
The MSC may need to increase the timer waiting for the Assignment
enabled.
Syntax

chg_element ho_exist_congest <value> <location> <cell_desc>
chg_cell_element ho_exist_congest <value> <cell_desc>

disp_element ho_exist_congest <location> <cell_desc>
68P02901W23-Q 5-349
ho_exist_congest Chapter 5: CM database parameters
Values
Value type Integer

Valid range 0 to 2
0 No handover attempts (for this condition)
1 Attempt to handover as many calls as the number of queued
assignment requests
2 Attempt to handover as many calls as meet the congestion handover
criteria
Default value 0
References

5-350 68P02901W23-Q
Technical Description: BSS Command Reference ho_margin_def
ho_margin_def
Description
The ho_margin_def parameter sets the default value for the neighbour handover margin (ho_margin_cell)
attribute of the source cell. The neighbour 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 neighbouring 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: If PBGT(n)
> ho_margin(n) then a handover may be required.
Dependencies None
Syntax

chg_element ho_margin_def <value> <location> <cell_desc>
chg_cell_element ho_margin_def <value> <cell_desc>

disp_element ho_margin_def <location> <cell_desc>
Values

Default value 8
68P02901W23-Q 5-351
ho_margin_def Chapter 5: 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 Celln
12.20 - 5.2.8.2
5-352 68P02901W23-Q
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.
Dependencies None
Syntax

modify_neighbor <src_cell_id> <neighbor_cell_id> ho_margin_type5 <value>

disp_neighbor <src_cell_desc> [<neighbor_cell_id>|“all"]
disp_neighbor "<source cell_name>" ["<internal neighbour cell_name>"]
disp_neighbor <src_cell_desc> [TEST <test neighbor_cell_id>]
Values
Value type Integer (dBm)

Default value 63
68P02901W23-Q 5-353
ho_margin_usage_flag Chapter 5: CM database parameters
ho_margin_usage_flag
Description
The ho_margin_usage_flag parameter determines which sorting algorithm the system

uses to sort the neighbour 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 neighbours are sorted using ho_margin_cell value.

Dependencies None
Syntax

chg_element ho_margin_usage_flag <value> <location> <cell_desc>
chg_cell_element ho_margin_usage_flag <value> <cell_desc>

disp_element ho_margin_usage_flag <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
5-354 68P02901W23-Q
Technical Description: BSS Command Reference ho_margin_usage_flag
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-355
ho_only_max_pwr Chapter 5: 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 an 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.

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

chg_element ho_only_max_pwr <value> <location> <cell_desc>
chg_cell_element ho_only_max_pwr <value> <cell_desc>

disp_element ho_only_max_pwr <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
5-356 68P02901W23-Q
Technical Description: BSS Command Reference ho_only_max_pwr
1 Enabled
Default value 0
68P02901W23-Q 5-357
ho_pwr_level_inner Chapter 5: CM database parameters
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.
Dependencies The Dual Band Cells feature must be unrestricted.
The element handover_power_level does not apply to intra-cell handovers.
Syntax

chg_element ho_pwr_level_inner <value> <location> <cell_desc>
chg_cell_element ho_pwr_level_inner <value> <cell_desc>

disp_element ho_pwr_level_inner <location> <cell_desc>
Values
Value type Integer

Valid ranges
Table 5-18 lists the maximum MS power level for PGSM and EGSM cells.
5-358 68P02901W23-Q
Technical Description: BSS Command Reference ho_pwr_level_inner
Table 5-18 Max MS power level for PGSM and EGSM cells

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 5-19 the maximum mobile power level for DCS1800 and PCS1900 cells.
Table 5-19 Max MS power level for DCS1800 and PCS1900 cells

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 5-20 lists the maximum mobile power level for DCS1800 and PCS1900 cells for class 3 mobiles.
Table 5-20 Max MS level for class 3 mobiles

29 36 dBm 31 32 dBm
30 34 dBm
Default value 2
68P02901W23-Q 5-359
hop_count Chapter 5: CM database parameters
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 a RXQUAL handover to another cell.
Dependencies None
Syntax

chg_element hop_count <value> <location> <cell_desc>
chg_cell_element hop_count <value> <cell_desc>

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
5-360 68P02901W23-Q
Technical Description: BSS Command Reference hop_qual_enabled
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 below).
If hop_qual_enabled is disabled, the normal rxqual values set with the add_cell command are used.
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)
Syntax

chg_cell_element hop_qual_enabled <value> <cell_desc>
If the value is 1 (enabled) the system prompts for the hopping threshold values as the following parameters:
• "l_rxqual_dl_h" on page 5-410
• "l_rxqual_ul_h" on page 5-436
• "l_rxqual_dl_p" on page 5-423
• "l_rxqual_ul_p" on page 5-449
68P02901W23-Q 5-361
hop_qual_enabled Chapter 5: CM database parameters

disp_element hop_qual_enabled <location> <cell_desc>
Values
Value type Boolean

Valid range 0 to 1
0 Disabled
1 Enabled
Default value 0
5-362 68P02901W23-Q
Technical Description: BSS Command Reference hopping_support
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 via 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.
Type B (operator action required)
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
2-102) command to change the hopping system does not require
SYSGEN ON.
Syntax

chg_element hopping_support <value> <location> <cell_desc>
chg_cell_element hopping_support <value> <cell_desc>
68P02901W23-Q 5-363
hopping_support Chapter 5: CM database parameters

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
5-364 68P02901W23-Q
Technical Description: BSS Command Reference hopping_systems_enabled
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.
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 2-102)
command to change the hopping system does not require SYSGEN
ON.
Syntax

chg_element hopping_systems_enabled,<index>
chg_cell_element hopping_systems_enabled,<index> <value> <cell_desc>

disp_element hopping_systems_enabled,<index> <location> <cell_desc>
disp_hopping <cell_desc> [<fhi> | "active"]
68P02901W23-Q 5-365
hopping_systems_enabled Chapter 5: CM database parameters
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None
References
GSM specification 5.01 - 6

5-366 68P02901W23-Q
Technical Description: BSS Command Reference hopping_systems_hsn
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.
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

chg_element hopping_systems_hsn,<index> <value> <location> <cell_desc>
chg_cell_element hopping_systems_hsn <value> <cell_desc>

disp_element hopping_systems_hsn,<index> <location> <cell_desc>
disp_hopping <cell_desc> [<fhi> | "active"]
Values
Value type Integer

Valid range 0 to 63
68P02901W23-Q 5-367
hopping_systems_hsn Chapter 5: CM database parameters
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
5-368 68P02901W23-Q
Technical Description: BSS Command Reference hopping_systems_mobile_alloc
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).
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 2-102) 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

chg_hop_params <location>
chg_hop_params <cell_desc>
chg_hop_params can be used in SYSGEN or out of SYSGEN. chg_hopping

must be executed in SYSGEN_ON mode.

disp_element hopping_systems_mobile_alloc,<index1>,<index2>
<location> <cell_desc>
68P02901W23-Q 5-369
hopping_systems_mobile_alloc Chapter 5: CM database parameters
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

5-370 68P02901W23-Q
Technical Description: BSS Command Reference hr_fr_hop_count
hr_fr_hop_count
Description
The {22064}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.
Dependencies The AMR feature {22064}and/or the GSM Half Rate feature must
be unrestricted.
The value of this parameter must not exceed the value of hop_count.
Syntax

{22064}
chg_element hr_fr_hop_count <value> <location> <cell_desc>
chg_cell_element hr_fr_hop_count <value> <cell_desc>

{22064}
disp_element hr_fr_hop_count <location> <cell_desc>
Values
Value type Integer

Default value 1
68P02901W23-Q 5-371
hr_intracell_ho_allowed Chapter 5: CM database parameters
hr_intracell_ho_allowed
Description
The {22064}hr_intracell_ho_allowed parameter enables or disables the support for Intra-Cell

quality handovers for half-rate channels within a cell.
be unrestricted.
Syntax

{22064}
chg_element hr_intracell_ho_allowed <value> <location> <cell_desc>
chg_cell_element hr_intracell_ho_allowed <value> <cell_desc>

{22064}
disp_element hr_intracell_ho_allowed <location> <cell_desc>
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.
5-372 68P02901W23-Q
Technical Description: BSS Command Reference hr_intracell_ho_allowed
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.
Default value 3
68P02901W23-Q 5-373
hr_res_ts Chapter 5: CM database parameters
hr_res_ts
Description
The {22064}hr_res_ts parameter specifies the maximum number of half-rate capable

timeslots to be reserved within each zone of the cell.
be unrestricted.
Syntax

{22064}
chg_element hr_res_ts <value> <location> <cell_desc>
chg_cell_element hr_res_ts <value> <cell_desc>

{22064}
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
5-374 68P02901W23-Q
Technical Description: BSS Command Reference illegal_circuit_id
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.
Syntax

chg_element illegal_circuit_id <value> 0

disp_element illegal_circuit_id 0
Values
Value type Integer

Default value 0
68P02901W23-Q 5-375
immediate_assign_mode Chapter 5: CM database parameters
immediate_assign_mode
Description
The immediate_assign_mode parameter specifies how the system responds when no Standalone
Dedicated Control Channels (SDCCHs) are available. This parameter also determines the type of
channel that is assigned to immediate channel requests for emergency calls.
If this parameter is set to disabled, immediate channel requests are either rejected or discarded if
there is no SDCCH available for both normal and emergency calls.
If this parameter is enabled, idle TCH is searched and allocated for immediate channel requests
after all SDCCHs are busy for normal calls. For emergency calls, a TCH is allocated if one is idle.
If all TCHs are busy, an SDCCH is allocated for the emergency call.
If this parameter is set to 1, TSCs are allocated for any reason.
If this parameter is set to 2, TSCs are not allocated for a location update.
Dependencies None
Syntax

chg_element immediate_assign_mode <value> <location> <cell_desc>
chg_cell_element immediate_assign_mode <value> <cell_desc>

disp_element immediate_assign_mode <location> <cell_desc>
5-376 68P02901W23-Q
Technical Description: BSS Command Reference immediate_assign_mode
Values
Value type Integer

0 Disabled
1 Allocate TSC for any reason
2 Do not allocate TCH for location update
Default value 0
68P02901W23-Q 5-377
inc_prp_cap_ena Chapter 5: 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.
This parameter is retained for future development.

Dependencies The Increase PRP Capacity feature must be unrestricted.
inc_prp_cap_ena is permanently disabled even though the PRP Capacity feature is unrestricted.
Syntax

chg_element inc_prp_cap_ena <value> <location>

disp_element inc_prp_cap_ena <location>
5-378 68P02901W23-Q
Technical Description: BSS Command Reference inc_prp_cap_ena
Values
Value type Integer

Valid range 0 or 1
0 Disabled
1 Disabled (BSS supports GSR6.0 functionality according to
requirement 4253–001–6 [6])
Default value 0
68P02901W23-Q 5-379
init_dl_cs Chapter 5: 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 can not be used for EGPRS (see egprs_init_dl_cs).
Dependencies EGPRS must be restricted.
To use coding scheme 3 and 4, 32 kbit/s TRAU must be enabled for
at least one RTF in a given cell.
Syntax

chg_element init_dl_cs <value> <location> <cell_desc>
chg_cell_element init_dl_cs <value> <cell_desc>

disp_element init_dl_cs <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 3
0 Downlink TBF starts with CS1.
5-380 68P02901W23-Q
Technical Description: BSS Command Reference init_dl_cs

Default value 1
68P02901W23-Q 5-381
init_ul_cs Chapter 5: 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 can not used for EGPRS (see egprs_init_ul_cs).
Dependencies EGPRS must be restricted.
To use coding scheme 3 and 4, 32 kbit/s TRAU must be enabled for
at least one RTF in a given cell.
Syntax

chg_element init_ul_cs <value> <location> <cell_desc>
chg_cell_element init_ul_cs <value> <cell_desc>

disp_element init_ul_cs <location> <cell_desc>
Values
Valid range 0 to 3
5-382 68P02901W23-Q
Technical Description: BSS Command Reference init_ul_cs

Default value 1
68P02901W23-Q 5-383
inner_hr_usage_thres Chapter 5: CM database parameters
inner_hr_usage_thres
Description
The {22064}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.

Dependencies The AMR feature {22064}and/ or the GSM Half Rate feature must
be unrestricted.
Syntax

{22064}
chg_element inner_hr_usage_thres <value> <location> <cell_desc>
chg_cell_element inner_hr_usage_thres <value> <cell_desc>

{22064}
disp_element inner_hr_usage_thres <location> <cell_desc>
Values
Value type Integer (percentage)

Default value 101
5-384 68P02901W23-Q
Technical Description: BSS Command Reference inner_zone_alg
inner_zone_alg
Description
The inner_zone_alg parameter specifies the use algorithm and the associated param-
eters for the inner zone of the cell.
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 above before using this parameter.
Syntax

chg_cell_element inner_zone_alg <value> <cell_desc>

disp_element inner_zone_alg <location> <cell_desc>
68P02901W23-Q 5-385
inner_zone_alg Chapter 5: 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
Default value: 63
• rxlev_ul_zone
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 5-21.
Default value 0
Table 5-21 shows the prompted parameters when 3 is entered for inner_zone_alg.
5-386 68P02901W23-Q
Technical Description: BSS Command Reference inner_zone_alg
Table 5-21 Prompted parameters for Dual Band Cell use
Prompt Parameter name Notes Range

Enter secondary secondary_freq_type Required. PGSM, EGSM or
frequency type: Inner zone frequency DCS1800
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 max_tx_bts
the inner zone: .Default: 0.
Enter maximum MS ms_txpwr_max_inner Required. As defined for
transmit power for max_tx_ms, based
the inner zone: on secondary frequency
type.
Enter handover ho_pwr_level_inner Optional. As defined for
power level for handover_power_level,
the inner zone: based on secondary
frequency type.
Default: 2.
Enter inner zone zone_ho_hyst Optional. -63 to +63
handover Default: 0.
hysteresis:
Enter downlink rxlev_dl_zone Optional. 0 to 63
receive level Default: 63.
threshold for the
inner zone:
Enter uplink rxlev_ul_zone Optional. 0 to 63
receive level Default: 63.
threshold for the
inner zone:
Enter dual band dual_band_offset Optional. -63 to +63
offset: Default: 0.
68P02901W23-Q 5-387
intave Chapter 5: 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.
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.

Dependencies None
Syntax

chg_element intave <value> <location> <cell_desc>
chg_cell_element intave <value> <cell_desc>

disp_element intave <location> <cell_desc>
5-388 68P02901W23-Q
Technical Description: BSS Command Reference intave
Values
Value type Integer (1 step = 2 SACCH multiframes)

Valid range 1 to 31
... ...
... ...
... ...
Default value 8
References
GSM specification Used to specify the Intave parameter as described in 5.08

68P02901W23-Q 5-389
inter_cell_handover_allowed Chapter 5: 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.
Dependencies None
Syntax

chg_element inter_cell_handover_allowed <value> <location> <cell_desc>
chg_cell_element inter_cell_handover_allowed <value> <cell_desc>

disp_element inter_cell_handover_allowed <location> <cell_desc>
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.
5-390 68P02901W23-Q
Technical Description: BSS Command Reference inter_cell_handover_allowed
2 Outgoing internal Inter-cell handover is disabled. The Handover

Required message is not sent to the MSC.
3 Outgoing Inter-cell 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

8.08 - 5: handover definitions
12.20 - 5.2.8.18 enable BSS Handover Control - enable Intercell
Handover
68P02901W23-Q 5-391
inter_rat_enabled Chapter 5: 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:
• Enabled.
• Disabled.
• Combined.

If pccch_enabled is set to 1 - Enabled, and the network_con-
trol_order parameter is set to any of the values 1, 2, 3 or 4, an
attempt to set inter_rat_enabled to 1 - Idle will be rejected.
Syntax

chg_element inter_rat_enabled <value> <location> <cell_desc>
chg_cell_element inter_rat_enabled <value> <cell_desc>

disp_element inter_rat_enabled <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 3
5-392 68P02901W23-Q
Technical Description: BSS Command Reference inter_rat_enabled
0 Off
1 2-3G idle
2 3-2G dedicated
3 2-3G idle / 3-2G dedicated
Default value 0
68P02901W23-Q 5-393
interband_ho_allowed Chapter 5: 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)
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

chg_element interband_ho_allowed <value> <location> <cell_desc>
chg_cell_element interband_ho_allowed <value> <cell_desc>

disp_element interband_ho_allowed <location> <cell_desc>
Values
Value type Integer

Valid range 1 to 11
5-394 68P02901W23-Q
Technical Description: BSS Command Reference interband_ho_allowed
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-Q 5-395
interfer_bands Chapter 5: 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.
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
Syntax

chg_element interfer_bands,<index> <value> <location> <cell_desc>
chg_cell_element interfer_bands,<index> <value> <cell_desc>

disp_element interfer_bands,<index> <location> <cell_desc>
5-396 68P02901W23-Q
Technical Description: BSS Command Reference interfer_bands
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
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-Q 5-397
intra_cell_handover_allowed Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_element intra_cell_handover_allowed <value> <location> <cell_desc>
chg_cell_element intra_cell_handover_allowed <value> <cell_desc>

disp_element intra_cell_handover_allowed <location> <cell_desc>
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.
5-398 68P02901W23-Q
Technical Description: BSS Command Reference intra_cell_handover_allowed
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
68P02901W23-Q 5-399
ksw_config Chapter 5: CM database parameters
ksw_config
Description
The ksw_config parameter specifies the order in which the timeslots are borrowed from
neighbouring cages. Each KSW pair provides 1024 timeslots. When there are no more timeslots
available, the system borrows timeslots from neighbouring cages.
Index numbers specify which highway is used when the amount of necessary timeslots exceeds the TDM
limit. The index values are set when the system is installed. The range of index values is 0 to 3.
Do not change the values for this parameter unless a KSW is added or removed.

Dependencies Changing this parameter is not allowed at M-Cell sites.
Syntax

chg_ksw_config <location> <ksw_pair> <highway1> <highway2>
<highway3> <highway4>

disp_element ksw_config,<index> <location>
For more information, refer to the chg_ksw_config descriptions and examples in Chapter 2.
5-400 68P02901W23-Q
Technical Description: BSS Command Reference ksw_config
Values
Value type Integer

Valid range 0 to 3
Default value None
68P02901W23-Q 5-401
l_rxlev_dl_h Chapter 5: 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.
Dependencies None
Syntax

chg_element l_rxlev_dl_h <value> <location> <cell_desc>
chg_cell_element l_rxlev_dl_h <value> <cell_desc>

disp_element l_rxlev_dl_h <location> <cell_desc>
Values

1 -109 dBm
2 -108 dBm
... ...
... ...
5-402 68P02901W23-Q
Technical Description: BSS Command Reference l_rxlev_dl_h
... ...
Default value 10
References
GSM parameter L_RXLEV_DL_H

GSM specification 5.08 - Appendix A - Table 1
68P02901W23-Q 5-403
l_rxlev_dl_p Chapter 5: 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.
Dependencies Must be less than u_rxlev_dl_p
Syntax

chg_element l_rxlev_dl_p <value> <location> <cell_desc>
chg_cell_element l_rxlev_dl_p <value> <cell_desc>

disp_element l_rxlev_dl_p <location> <cell_desc>
Values

1 -109 dBm
2 -108 dBm
... ...
... ...
5-404 68P02901W23-Q
Technical Description: BSS Command Reference l_rxlev_dl_p
... ...
Default value 30
References
GSM parameter L_RXLEV_DL_P

68P02901W23-Q 5-405
l_rxlev_ul_h Chapter 5: 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.
Dependencies None
Syntax

chg_element l_rxlev_ul_h <value> <location> <cell_desc>
chg_cell_element l_rxlev_ul_h <value> <cell_desc>

disp_element l_rxlev_ul_h <location> <cell_desc>
Values

1 -109 dBm
2 -108 dBm
... ...
... ...
5-406 68P02901W23-Q
Technical Description: BSS Command Reference l_rxlev_ul_h
... ...
Default value 10
References
GSM parameter L_RXLEV_UL_H

68P02901W23-Q 5-407
l_rxlev_ul_p Chapter 5: 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.
This threshold is checked to determine if MS power should be increased.
Dependencies Must be less than u_rxlev_ul_p
Syntax

chg_element l_rxlev_ul_p <value> <location> <cell_desc>
chg_cell_element l_rxlev_ul_p <value> <cell_desc>

disp_element l_rxlev_ul_p <location> <cell_desc>
Values

1 -109 dBm
2 -108 dBm
5-408 68P02901W23-Q
Technical Description: BSS Command Reference l_rxlev_ul_p
... ...
... ...
... ...
Default value 30
References
GSM parameter L_RXLEV_UL_P

68P02901W23-Q 5-409
l_rxqual_dl_h Chapter 5: 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 type of unit is specified by the alt_qual_proc parameter.
Dependencies alt_qual_proc.See also data_qual_enabled, hop_qual
_enabled.
Syntax

chg_element l_rxqual_dl_h <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_h <value> <cell_desc>

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
5-410 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_dl_h
Default value 453 453 BER if alt_qual_proc = 0

5 5 QBand units if alt_qual_proc = 1
References
GSM parameter L_RXQUAL_DL_H

68P02901W23-Q 5-411
l_rxqual_dl_h_amr_fr Chapter 5: 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.
This parameter can be changed only at an AMR-capable BTS site.
This parameter is prompted when alt_qual_proc is changed.
Syntax

chg_element l_rxqual_dl_h_amr_fr <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_h_amr_fr <value> <cell_desc>

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
5-412 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_dl_h_hr
l_rxqual_dl_h_hr
Description
The {22064}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.
be unrestricted.
This parameter can be changed [22064] at any AMR/GSM HR
capable BTS site.
Syntax

{22064}
chg_element l_rxqual_dl_h_hr <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_h_hr <value> <cell_desc>

{22064}
disp_element l_rxqual_dl_h_hr <location> <cell_desc>
Values
Value type Integer

68P02901W23-Q 5-413
l_rxqual_dl_h_hr Chapter 5: CM database parameters
Default value 113 BER if alt_qual_proc = 0

3 QBand units if alt_qual_proc = 1
5-414 68P02901W23-Q
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.
Syntax

chg_element l_rxqual_dl_h_data <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_h_data <value> <cell_desc>

disp_element l_rxqual_dl_h_data <location> <cell_desc>
Values
Value type Integer

68P02901W23-Q 5-415
l_rxqual_dl_h_data Chapter 5: CM database parameters

References

5-416 68P02901W23-Q
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.
Syntax

chg_element l_rxqual_dl_h_hopping <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_h_hopping <value> <cell_desc>

disp_element l_rxqual_dl_h_hopping <location> <cell_desc>
Values
Value type Integer

68P02901W23-Q 5-417
l_rxqual_dl_h_hopping Chapter 5: CM database parameters

References

5-418 68P02901W23-Q
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.
This threshold is enabled and set to be used for hopping calls with the chg_cell_element
command and the hop_qual_enabled parameter.
Syntax

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>

disp_element l_rxqual_dl_h_hopping_amr_fr <location> <cell_desc>
68P02901W23-Q 5-419
l_rxqual_dl_h_hopping_amr_fr Chapter 5: CM database parameters
Values
Value type Integer

5-420 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_dl_h_hopping_hr
l_rxqual_dl_h_hopping_hr
Description
The {22064}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
be unrestricted.
capable BTS site.
Syntax

{22064}
chg_element l_rxqual_dl_h_hopping_hr <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_h_hopping_hr <value> <cell_desc>

{22064}
disp_element l_rxqual_dl_h_hopping_hr <location> <cell_desc>
68P02901W23-Q 5-421
l_rxqual_dl_h_hopping_hr Chapter 5: CM database parameters
Values
Value type Integer

5-422 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_dl_p
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.
Dependencies alt_qual_procMust be greater than u_rxqual_dl_pSee also
data_qual_enabled, hop_qual_enabled
Syntax

chg_element l_rxqual_dl_p <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_p <value> <cell_desc>

disp_element l_rxqual_dl_p <location> <cell_desc>
Values
Value type Integer

68P02901W23-Q 5-423
l_rxqual_dl_p Chapter 5: CM database parameters

References
GSM parameter L_RXQUAL_DL_P

5-424 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_dl_p_amr_fr
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.
This parameter must be greater than u_rxqual_dl_p.
Syntax

chg_element l_rxqual_dl_p_amr_fr <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_p_amr_fr <value> <cell_desc>

disp_element l_rxqual_dl_p_amr_fr <location> <cell_desc>
Values
Value type Integer

68P02901W23-Q 5-425
l_rxqual_dl_p_hr Chapter 5: CM database parameters
l_rxqual_dl_p_hr
Description
The {22064}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.
be unrestricted.
This parameter can be changed {22064} at any AMR/GSM HR
capable BTS site.
This parameter must be greater than {22064}u_rxqual_dl_p_hr.
Syntax

{22064}
chg_element l_rxqual_dl_p_hr <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_p_hr <value> <cell_desc>

{22064}
disp_element l_rxqual_dl_p_hr <location> <cell_desc>
Values
Value type Integer

5-426 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_dl_p_hr

68P02901W23-Q 5-427
l_rxqual_dl_p_data Chapter 5: 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
situation it is used instead of the l_rxqual_dl_p threshold value, as set in the add_cell command.
Syntax

chg_element l_rxqual_dl_p_data <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_p_data <value> <cell_desc>

disp_element l_rxqual_dl_p_data <location> <cell_desc>
Values
Value type Integer

5-428 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_dl_p_data

References

68P02901W23-Q 5-429
l_rxqual_dl_p_hopping Chapter 5: 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.
Syntax

chg_element l_rxqual_dl_p_hopping <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_p_hopping <value> <cell_desc>

disp_element l_rxqual_dl_p_hopping <location> <cell_desc>
Values
Value type Integer

5-430 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_dl_p_hopping

References

68P02901W23-Q 5-431
l_rxqual_dl_p_hopping_amr_fr Chapter 5: 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.
Syntax

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>

disp_element l_rxqual_dl_p_hopping_amr_fr <location> <cell_desc>
5-432 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_dl_p_hopping_amr_fr
Values
Value type Integer

68P02901W23-Q 5-433
l_rxqual_dl_p_hopping_hr Chapter 5: CM database parameters
l_rxqual_dl_p_hopping_hr
Description
The {22064}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.
be unrestricted.
capable BTS site.
Syntax

{22064}
chg_element l_rxqual_dl_p_hopping_hr <value> <location> <cell_desc>
chg_cell_element l_rxqual_dl_p_hopping_hr <value> <cell_desc>

{22064}
disp_element l_rxqual_dl_p_hopping_hr <location> <cell_desc>
5-434 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_dl_p_hopping_hr
Values
Value type Integer

68P02901W23-Q 5-435
l_rxqual_ul_h Chapter 5: 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.
See also: data_qual_enabled, hop_qual_enabled
Syntax

chg_element l_rxqual_ul_h <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_h <value> <cell_desc>

disp_element l_rxqual_ul_h <location> <cell_desc>
Values
Value type Integer

5-436 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_ul_h

References
GSM parameter L_RXQUAL_UL_H

68P02901W23-Q 5-437
l_rxqual_ul_h_amr_fr Chapter 5: 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.
Syntax

chg_element l_rxqual_ul_h_amr_fr <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_h_amr_fr <value> <cell_desc>

disp_element l_rxqual_ul_h_amr_fr <location> <cell_desc>
Values
Value type Integer

5-438 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_ul_h_hr
l_rxqual_ul_h_hr
Description
The {22064}l_rxqual_ul_h_hr parameter specifies the handover control threshold for the lower Received
(Rx) quality downlink. This threshold is checked to determine if a handover condition exists.
be unrestricted.
capable BTS site.
Syntax

{22064}
chg_element l_rxqual_ul_h_hr <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_h_hr <value> <cell_desc>

{22064}
disp_element l_rxqual_ul_h_hr <location> <cell_desc>
Values
Value type Integer

68P02901W23-Q 5-439
l_rxqual_ul_h_hr Chapter 5: CM database parameters

5-440 68P02901W23-Q
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
situation it is used instead of the l_rxqual_ul_h threshold value, as set in the add_cell command.
Syntax

chg_element l_rxqual_ul_h_data <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_h_data <value> <cell_desc>

disp_element l_rxqual_ul_h_data <location> <cell_desc>
Values
Value type Integer

68P02901W23-Q 5-441
l_rxqual_ul_h_data Chapter 5: CM database parameters

References

5-442 68P02901W23-Q
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) 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_ul_h threshold value, as set in the add_cell command.
Syntax

chg_element l_rxqual_ul_h_hopping <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_h_hopping <value> <cell_desc>

disp_element l_rxqual_ul_h_hopping <location> <cell_desc>
Values
Value type Integer

68P02901W23-Q 5-443
l_rxqual_ul_h_hopping Chapter 5: CM database parameters

References

5-444 68P02901W23-Q
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) downlink, for hopping calls only. This threshold is
Syntax

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>

disp_element l_rxqual_ul_h_hopping_amr_fr <location> <cell_desc>
68P02901W23-Q 5-445
l_rxqual_ul_h_hopping_amr_fr Chapter 5: CM database parameters
Values
Value type Integer

5-446 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_ul_h_hopping_hr
l_rxqual_ul_h_hopping_hr
Description
The {22064}l_rxqual_ul_h_hopping_hr parameter specifies the handover control threshold

for the lower received quality (rxqual) downlink, for hopping calls only. This threshold is
be unrestricted.
This parameter can be changed at [22064] any AMR/GSM HR
capable BTS site.
Syntax

{22064}
chg_element l_rxqual_ul_h_hopping_hr <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_h_hopping_hr <value> <cell_desc>

{22064}
disp_element l_rxqual_ul_h_hopping_hr <location> <cell_desc>
68P02901W23-Q 5-447
l_rxqual_ul_h_hopping_hr Chapter 5: CM database parameters
Values
Value type Integer

3 Band units if alt_qual_proc = 1
5-448 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_ul_p
l_rxqual_ul_p
Description
The l_rxqual_ul_p parameter specifies the lower uplink limit of the signal quality of the MS. This
threshold is checked to determine if MS power should be increased.
Dependencies alt_qual_procMust be greater than u_rxqual_ul_pSee also
data_qual_enabled, hop_qual_enabled
Syntax

chg_element l_rxqual_ul_p <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_p <value> <cell_desc>

disp_element l_rxqual_ul_p <location> <cell_desc>
Values
Value type Integer

68P02901W23-Q 5-449
l_rxqual_ul_p Chapter 5: CM database parameters

References
GSM parameter L_RXQUAL_UL_P

5-450 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_ul_p_amr_fr
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. This threshold is checked to determine if MS power should be increased.
This parameter must be greater than u_rxqual_ul_p.
Syntax

chg_element l_rxqual_ul_p_amr_fr <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_p_amr_fr <value> <cell_desc>

disp_element l_rxqual_ul_p_amr_fr <location> <cell_desc>
Values
Value type Integer

68P02901W23-Q 5-451
l_rxqual_ul_p_hr Chapter 5: CM database parameters
l_rxqual_ul_p_hr
Description
The {22064}l_rxqual_ul_p_hr parameter specifies the lower uplink limit of the signal quality of the
MS. This threshold is checked to determine if MS power should be increased.
be unrestricted.
capable BTS site.
This parameter is prompted for when alt_qual_proc is changed.
This parameter must be greater than {22064}u_rxqual_ul_p_hr.
Syntax

{22064}
chg_element l_rxqual_ul_p_hr <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_p_hr <value> <cell_desc>

{22064}
disp_element l_rxqual_ul_p_hr <location> <cell_desc>
Values
Value type Integer

5-452 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_ul_p_hr

68P02901W23-Q 5-453
l_rxqual_ul_p_data Chapter 5: 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). This threshold is checked to
determine if MS power should be increased. This threshold is enabled and set to be used when data is
situation it is used instead of the l_rxqual_ul_p threshold value, as set in the add_cell command.
Syntax

chg_element l_rxqual_ul_p_data <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_p_data <value> <cell_desc>

disp_element l_rxqual_ul_p_data <location> <cell_desc>
Values
Value type Integer

5-454 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_ul_p_data

References

68P02901W23-Q 5-455
l_rxqual_ul_p_hopping Chapter 5: 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. This threshold is checked to determine if MS 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.
Syntax

chg_element l_rxqual_ul_p_hopping <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_p_hopping <value> <cell_desc>

disp_element l_rxqual_ul_p_hopping <location> <cell_desc>
Values
Value type Integer

5-456 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_ul_p_hopping

References

68P02901W23-Q 5-457
l_rxqual_ul_p_hopping_amr_fr Chapter 5: 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.
Syntax

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>

disp_element l_rxqual_ul_p_hopping_amr_fr <location> <cell_desc>
5-458 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_ul_p_hopping_amr_fr
Values
Value type Integer

68P02901W23-Q 5-459
l_rxqual_ul_p_hopping_hr Chapter 5: CM database parameters
l_rxqual_ul_p_hopping_hr
Description
The {22064}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.
be unrestricted.
capable BTS site.
Syntax

{22064}
chg_element l_rxqual_ul_p_hopping_hr <value> <location> <cell_desc>
chg_cell_element l_rxqual_ul_p_hopping_hr <value> <cell_desc>

{22064}
disp_element l_rxqual_ul_p_hopping_hr <location> <cell_desc>
5-460 68P02901W23-Q
Technical Description: BSS Command Reference l_rxqual_ul_p_hopping_hr
Values
Value type Integer

68P02901W23-Q 5-461
land_layer1_mode Chapter 5: 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.
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.land_layer1_mode cannot be changed to 1 (T1)
unless mms_config_type = 0.
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

chg_element land_layer1_mode <value> <location>

disp_element land_layer1_mode <location>
Values
Value type Boolean

Valid range 0 or 1
0 2.048 Mbit/s - CEPT format (E1)
5-462 68P02901W23-Q
Technical Description: BSS Command Reference land_layer1_mode
1 1.544 Mbit/s - T1 link

Default value 0
68P02901W23-Q 5-463
layer_number Chapter 5: 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 handover a call in the
microcell layer to another cell in the microcell layer.
This parameter specifies the layer for a cell.
Dependencies This parameter is unavailable if the Microcellular option has not
been purchased.
Syntax

chg_element layer_number <value> <location> <cell_desc>
chg_cell_element layer_number <value> <cell_desc>

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
5-464 68P02901W23-Q
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.
Dependencies The Location Services feature must be unrestricted.
Syntax

chg_element lb_int_called_pci <value> <location>

disp_element lb_int_called_pci <location>
Values
Value type Integer

Valid range 0 or 1
0 DCP not included.
1 DCP included
Default value None
68P02901W23-Q 5-465
lb_int_calling_pci Chapter 5: 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.
Syntax

chg_element lb_int_calling_pci <value> <location>

disp_element lb_int_calling_pci <location>
Values
Value type Integer

Valid range 0 or 1
0 Point code not included.
1 Point code included.
Default value None
5-466 68P02901W23-Q
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 to be included in the
SCCP connection request messages that travel over the Lb-interface.
Syntax

chg_element lb_int_cr_calling <value> <location>

disp_element lb_int_cr_calling <location>
Values
Value type Integer (milliseconds)

Valid range 0 or 1
0 Not included.
1 Included.
Default value 0
68P02901W23-Q 5-467
lb_int_dpc Chapter 5: CM database parameters
lb_int_dpc
Description
The lb_int_dpc (Lb-interface DPC) is the point code of a BSS-based SMLC.

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
chg_element lb_int_dpc <value> <location>

disp_element lb_int_dpc <location>
Values
Value type Integer

Valid range ss7_mode = 0: 0 to 16383ss7_mode = 1: 0 to 16777215
Default value None
5-468 68P02901W23-Q
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.
Syntax

chg_element lb_int_global_reset_repetitions <value> <location>

disp_element lb_int_global_reset_repetitions <location>
Values
Value type Integer

Default value 0
References
68P02901W23-Q 5-469
lcs_mode Chapter 5: CM database parameters
lcs_mode
Description
The lcs_mode parameter specifies the Location Services mode of the BSS.
This parameter can be modified only when the system is in the SYSGEN ON mode.
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
1. 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.
REJECTING SYSGEN_OFF REQUEST.
2. 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.
3. 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.
5-470 68P02901W23-Q
Technical Description: BSS Command Reference lcs_mode
4. 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,
5. 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.
Dependencies checked during

lcs_mode modification
1. 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:
COMMAND REJECTED
2. 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:
COMMAND REJECTED
3. 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

chg_element lcs_mode <value> <location>

disp_element lcs_mode <location>
68P02901W23-Q 5-471
lcs_mode Chapter 5: CM database parameters
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
5-472 68P02901W23-Q
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.
Dependencies link_about_to_fail must be less than link_fail
Syntax

chg_element link_about_to_fail <value> <location> <cell_desc>
chg_cell_element link_about_to_fail <value> <cell_desc>

disp_element link_about_to_fail <location> <cell_desc>
68P02901W23-Q 5-473
link_about_to_fail Chapter 5: 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

5-474 68P02901W23-Q
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.
Dependencies link_fail must be greater than or equal to link_about_to_fail
Syntax

chg_element link_fail <value> <location> <cell_desc>
chg_cell_element link_fail <value> <cell_desc>

disp_element link_fail <location> <cell_desc>
68P02901W23-Q 5-475
link_fail Chapter 5: CM database parameters
Values
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)

5-476 68P02901W23-Q
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.
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

chg_element lmtl_loadshare_granularity <value> <location>

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-Q 5-477
local_maintenance Chapter 5: CM database parameters
local_maintenance
Description
The local_maintenance parameter specifies whether or not database elements that can be configured via
the OMC-R interface can be modified from a local maintenance terminal or from an rlogin. This is used
to synchronize the database in the BSS and the data modelled in the OMC-R MIB.
When this parameter is disabled, the BSS blocks attempts to modify database elements that are
configurable via the OMC-R interface at a local maintenance terminal or from an rlogin. When this
parameter is enabled, the BSS allows modification of database elements that are configurable via
the OMC-R interface at a local maintenance terminal or from an rlogin.
The local_maintenance parameter is also used to determine whether or not BSS commands supported
via the OMC-R interface may be entered from a local maintenance terminal or from a rlogin.
The following commands or functionalities are supported by the OMC-R GUI 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
The following commands or functionalities are supported by the OMC-R GUI 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
5-478 68P02901W23-Q
Technical Description: BSS Command Reference local_maintenance
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 following commands or functionalities are not supported by the OMC-R GUI 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_password disp_gclk_cal help
chg_time disp_gsm_cells history
chg_ts_usage disp_level man
clear_cal_data disp_link_usage reattempt_pl
clear_database disp_links set_full_power
clear_gclk_avgs disp_mms_ts_usage store_cal_data
del_act_alarm disp_mobile_optimize swfm_enable
del_channel disp_rtf_calls sysgen_mode
del_link disp_rtf_channel time_stamp
disable_alarm disp_site trace_call
disp_act_alarm disp_throttle unalias
disp_alarm_sites

Dependencies None
chg_element command to change this parameter.
Syntax

chg_element local_maintenance <value> <location>
68P02901W23-Q 5-479
local_maintenance Chapter 5: CM database parameters

disp_element local_maintenance <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1
5-480 68P02901W23-Q
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.
Dependencies None
Syntax

chg_element low_sig_thresh <value> <location> <cell_desc>
chg_cell_element low_sig_thresh <value> <cell_desc>

disp_element low_sig_thresh <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 63
Default value 0
68P02901W23-Q 5-481
lta_alarm_range Chapter 5: 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 will be 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 centre value is 80h.
Dependencies This parameter is not valid at an M-Cell site.
Syntax

chg_element lta_alarm_range <value> <location>

disp_element lta_alarm_range <location>
Values
Value type Integer

Default value 7
5-482 68P02901W23-Q
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.
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.
Syntax
Change comma
nd strings
chg_element max_gprs_ts_per_carrier <value> <location> <cell_desc>
chg_cell_element max_gprs_ts_per_carrier <value> <cell_desc>

disp_element max_gprs_ts_per_carrier <location> <cell_desc>
Values
Value type Integer

Valid range 1 to 8
Default value 8
68P02901W23-Q 5-483
max_ms_dl_buffer Chapter 5: CM database parameters
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.
Syntax

chg_element max_ms_dl_buffer <value> <location> <cell_desc>
chg_cell_element max_ms_dl_buffer <value> <cell_desc>

disp_element max_ms_dl_buffer <location> [<cell_desc>]
Values
Value type Integer (one step = 3.2 bytes.)

5-484 68P02901W23-Q
Technical Description: BSS Command Reference max_ms_dl_buffer
1600 5120 bytes

... ...
... ...
... ...
20000 64000 bytes
Default value 12000 (equivalent to 38400 bytes)
Each step adds 3.2 bytes of buffer length with fractions of bytes being ignored. For example,
setting max_ml_dl_buffer to 1603 defines a buffer size of 5129 bytes.
68P02901W23-Q 5-485
max_ms_dl_rate Chapter 5: CM database parameters
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.
Syntax

chg_element max_ms_dl_rate <value> <location> <cell_desc>
chg_cell_element max_ms_dl_rate <value> <cell_desc>

disp_element max_ms_dl_rate <location> <cell_desc>
Values
Value type Integer (100 bits per second)

Default value 900 (equivalent to 90000 bits per second)
The units for this parameter is 100 bits per second. The equivalent range in
bits per second is 100 to 90000.
5-486 68P02901W23-Q
Technical Description: BSS Command Reference max_mtls
max_mtls
Description
The max_mtls parameter specifies the maximum number of MTLs supported by a BSP or LCF.
This parameter must be set to 1 for all BSPs on a bsc_type 0, non-RXCDR system.
This parameter must be set to 1 for at least one LCF on a BSC site where the BSC type is not zero.
Set this parameter to 2 for GPROC2 and GPROC3 boards. When the value is set to 2, the
system displays a warning message and accepts the command.
Device/Function BSP, LCF
Type B (no operator actions)
Dependencies Change the security level to 2 to modify this parameter.
Use of all locations option No
Syntax

modify_value <location> max_mtls <value> bsp
<dev_fun_id1> <dev_fun_id2> <dev_fun_id3>
modify_value <location> max_mtls <value> lcf

equip <location> bsp
equip <location> lcf

disp_equipment <location> bsp <id1> <id2> <id3>
disp_equipment <location> lcf <id1> <id2> <id3>
68P02901W23-Q 5-487
max_mtls Chapter 5: CM database parameters
Values
Value type Integer

Valid range 0 to 2
Default value None
5-488 68P02901W23-Q
Technical Description: BSS Command Reference max_number_of_sdcchs
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 will maintain.
Dependencies For combined channel configurations, the values can be 4, 12, 20,
28 SDs.
For non-combined channel configurations, the values can be 8, 16,
24, 32 SDs.
Syntax

chg_element max_number_of_sdcchs <value> <location> <cell_desc>

disp_element max_number_of_sdcchs <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 48
Valid values depend on the value of ccch_conf:
If ccch_conf = 1, the values must be in multiples of 8 with an offset of 4 (such as 0, 4,
12,...,44).
If ccch_conf 1, the values must be in multiples of 8 with an offset of 0 (such as
0, 8, 16,...48).
Default value None
68P02901W23-Q 5-489
max_number_of_sdcchs Chapter 5: CM database parameters
References
GSM specification 5.02 - 6.4

5-490 68P02901W23-Q
Technical Description: BSS Command Reference max_pagenum_per_sec
max_pagenum_per_sec
{24660, 24661}
Description
The max_pagenum_per_sec parameter defines the maximum number of Page messages

from the BSC to one BTS allowed in one second.
Dependencies None
Syntax

chg_element max_pagenum_per_sec <value> bsc

disp_element max_pagenum_per_sec bsc
Values
Value type Integer (number of Page messages)

Default value 0
68P02901W23-Q 5-491
max_q_length_channel Chapter 5: CM database parameters
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.
Before GSR7, this parameter was named max_q_length_full_rate_channel.

Dependencies The sum of max_q_length_channel + max_q_length_sdcch must
be less than or equal to queue_management_information.
Syntax

chg_element max_q_length_channel <value> <location> <cell_desc>
chg_cell_element max_q_length_channel <value> <cell_desc>

disp_element max_q_length_channel <location> <cell_desc>
5-492 68P02901W23-Q
Technical Description: BSS Command Reference max_q_length_channel
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
68P02901W23-Q 5-493
max_q_length_sdcch Chapter 5: CM database parameters
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.
Dependencies The sum of max_q_length_full_rate_channel +
max_q_length_sdcch must be less than or equal to
queue_management_information.
Syntax

chg_element max_q_length_sdcch <value> <location> <cell_desc>
chg_cell_element max_q_length_sdcch <value> <cell_desc>

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
5-494 68P02901W23-Q
Technical Description: BSS Command Reference max_retran
max_retran
Description
The max_retran parameter specifies the maximum channel request retransmission value for MSs.
Dependencies None
Syntax

chg_element max_retran <value> <location> <cell_desc>chg_cell_element

max_retran <value> <cell_desc>

disp_element max_retran <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 3
0 Maximum [1] retransmission
1 Maximum [2] retransmissions
Default value 0
68P02901W23-Q 5-495
max_retran Chapter 5: CM database parameters
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
5-496 68P02901W23-Q
Technical Description: BSS Command Reference max_rst_ckt_timer_exps
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.
Syntax

chg_element max_rst_ckt_timer_exps <value> 0

disp_element max_rst_ckt_timer_exps 0
Values
Value type Integer (represents the number of repeats)

The value 0 means the system keeps sending the “Reset Circuit" message indefinitely.
Default value 1
68P02901W23-Q 5-497
max_tx_bts Chapter 5: CM database parameters
max_tx_bts
Description
The max_tx_bts parameter specifies the maximum output power for a BTS within its power
class. This can be used to establish a cell boundary.
A BTS is capable of reducing its power in a range of 23 steps of 2 dBm per step
for PGSM, EGSM, and DCS1800.
The range is 7 steps of 2 dBm per step for M-Cellmicro, M-Cellaccess and Horizoncompact.
Dependencies frequency_type
Syntax

chg_element max_tx_bts <value> <location> <cell_desc>
chg_cell_element max_tx_bts <value> <cell_desc>

disp_element max_tx_bts <location> <cell_desc>
Values

Valid range -1 to 21 For PGSM, EGSM, and DCS1800.
0 to 6 For M-Cellmicro, M-Cellaccess and Horizoncompact.
Default value None
5-498 68P02901W23-Q
Technical Description: BSS Command Reference max_tx_bts
Refer to Table 5-22, Table 5-23, Table 5-24, Table 5-25, and Table 5-26 for additional
information about the values for this parameter.
Table 5-22 lists the values for the CTU2. The values represent the calibrated output power
at the top of the cabinet with one stage of combining.
Table 5-22 CTU2 values
Valid Input 1800 Mhz 900 Mhz

-1 47 dBm 48 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
Table 5-23 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 5-23 also specifies the types of combing used: none, external, internal, and both internal
and external. The combining types are defined as follows:
68P02901W23-Q 5-499
• 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 via 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 prior to leaving the XCVR. Hence the
power firgure internal combining represents two carriers at this transmit power for a CTU2 in
DD-DCM. Note 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 would allow two CTU2 in DD-DCM to be combined to create a four-carrier sector.
Table 5-23 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
Table 5-24 lists the values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro, M-Cellcity,
Horizonmicro (M-Cellarena) and Horizoncompact (M-Cellarenamacro) sites.
Table 5-24 Values for PGSM, EGSM, DCS1800 and PCS1900, etc. sites
Horizoncompact
PGSM and EGSM DCS1800 and PCS1900
Valid Input (M-Cellarenamacro)
M-Cellmicro values M-Cellmicro values
values
Table 5-25 lists the values for DCS1800, and M-Cellaccess sites.
5-500 68P02901W23-Q
Table 5-25 Values for DCS1800 and M-Cellaccess sites
PGSM, EGSM, and M-Cellaccess

Valid Input DCS1800 M-Cellaccess values
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 5-26
lists sample output power, measured at the top of the cabinet, of some Motorola cabinets
with different combinations of radios and combiners.
Table 5-26 Sample output power
Type of combining Number of radios Output power (as calibrated)

BTS4, BTS5, BTS6 6
43.01 dBm
43.98 dBm
cavity (2 neighbouring cabinets) 10 13W [Symbol_approximate]
41.14 dBm
M-Cell2 or M-Cell6 6
hybrid 2 17.5W [Symbol_approximate]
43.01 dBm
42.79 dBm
duplexer 4 13.5W [Symbol_approximate]
41.30 dBm
The listed power is valid for 600 kHz minimum channel distance, and for 800 kHz
minimum channel distance with cavity combining.
68P02901W23-Q 5-501
Interpolation table
Table 5-27 can be used to interpolate the values between the specified settings.
Table 5-27 Value interpolation
max_tx_bts Maximum output power of a BTS in relation to the com-

input bining configuration
–1 45 dBm 44 dBm 43 dBm 42 dBm 41 dBm
0 44 dBm 43 dBm 42 dBm 41 dBm 40 dBm
21 2 dBm 1 dBm 0 dBm -1 dBm -2 dBm
Default value 0
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.
5-502 68P02901W23-Q
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-Q 5-503
max_tx_ms Chapter 5: CM database parameters
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.
The value should be chosen to balance the up and down links in a cell.
This parameter is also used in the power budget calculation.
Dependencies The range and default values of ms_txpwr_max_inner depends on
this parameter. If the range or default value of max_ts_ms changes,
mstxpwr_max_inner must also be updated, to a value less than
or equal to max_ts_ms.
Syntax

chg_element max_tx_ms <value> <location> <cell_desc>
chg_cell_element max_tx_ms <value> <cell_desc>

disp_element max_tx_ms <location> <cell_desc>
Values

Valid range 5 to 39 PGSM and EGSM (Odd values only)
0 to 36 DCS1800 (Even values only)
5-504 68P02901W23-Q
Technical Description: BSS Command Reference max_tx_ms
0 to 32,33 PCS1900 (Even values only and value 33)

Default value Highest allowed value
References
GSM parameter MS_TXPWR_MAX

5.05 - 4.1
68P02901W23-Q 5-505
mb_preference Chapter 5: CM database parameters
mb_preference
Description
The mb_preference parameter enables or disables the Multiband Inter-cell Handover feature.
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

chg_element mb_preference <value> <location>

disp_element mb_preference <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-506 68P02901W23-Q
Technical Description: BSS Command Reference mb_tch_congest_thres
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.
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_mode must 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

chg_element mb_tch_congest_thres <value> <location> <cell_desc>

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.
68P02901W23-Q 5-507
missing_rpt Chapter 5: CM database parameters
missing_rpt
Description
The missing_rpt parameter enables or disables the suspension of the storing, averaging, and
processing of downlink power control and handovers.
Dependencies None
Syntax

chg_element missing_rpt <value> <location> <cell_desc>
chg_cell_element missing_rpt <value> <cell_desc>

disp_element missing_rpt <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value None
5-508 68P02901W23-Q
Technical Description: BSS Command Reference mmi_cell_id_format
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.
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

chg_element mmi_cell_id_format <value> 0

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
68P02901W23-Q 5-509
mms_cat_enable Chapter 5: CM database parameters
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 10th 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.
Dependencies None
Syntax

chg_element mms_cat_enable <value> <location>

disp_element mms_cat_enable <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
5-510 68P02901W23-Q
Technical Description: BSS Command Reference mms_cat_enable
1 Enabled
Default value 0
68P02901W23-Q 5-511
mms_config_type Chapter 5: CM database parameters
mms_config_type
Description
The mms_config_type parameter specifies the signalling type for all MMSs. The signalling
type depends on the carrier type being used, E1 or T1.
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.
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.
• mms_config_type cannot be changed to 1 if land_layer1_mode

= 1 (T1).
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.
For T1 systems, delete the existing database using the
clear_database command then place the system in the initial
SYSGEN mode.
Syntax

chg_element mms_config_type <value> <location>
5-512 68P02901W23-Q
Technical Description: BSS Command Reference mms_config_type
The value can be changed using the chg_cell_element command but the incorrect value
will be used until the MSI or BSI is reset and the change becomes active.

disp_element mms_config_type <location>
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
If land_layer1_mode = 1 (1.544 Mbit/s T1 link) then:
0 ESF
Default value 0
68P02901W23-Q 5-513
ms_distance_allowed Chapter 5: CM database parameters
ms_distance_allowed
Description
The ms_distance_allowed parameter disables or enables the distance comparison process for handovers.
When enabled, the distance comparison process might 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.
Dependencies ms_max_range
Syntax

chg_element ms_distance_allowed <value> <location> <cell_desc>
chg_cell_element ms_distance_allowed <value> <cell_desc>

disp_element ms_distance_allowed <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-514 68P02901W23-Q
Technical Description: BSS Command Reference ms_distance_allowed
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
68P02901W23-Q 5-515
ms_max_range Chapter 5: CM database parameters
ms_max_range
Description
The ms_max_range parameter specifies the MS maximum range for the handover algorithm.
This parameter must be programmed 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.
Dependencies The range for the ms_max_range parameter depends on whether
the Extended Range feature is enabled or disabled.
Syntax

chg_element ms_max_range <value> <location> <cell_desc>
chg_cell_element ms_max_range <value> <cell_desc>

disp_element ms_max_range <location> <cell_desc>
5-516 68P02901W23-Q
Technical Description: BSS Command Reference ms_max_range
Values
Value type Integer

Valid range 0 to 63 for normal cells (see Table 5-28).
0 to 219 for Extended Range cells (see Table 5-29).
Default value 63
Table 5-28 ms_max_range values for normal 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
... ... ...
... ... ...
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 5-29 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-Q 5-517
ms_p_con_ack Chapter 5: 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 acknowledgement is not received from the MS. This parameter is
effective only if the decision_alg_num equals 1.
Dependencies decision_alg_num = 1
Syntax

chg_element ms_p_con_ack <value> <location> <cell_desc>
chg_cell_element ms_p_con_ack <value> <cell_desc>

disp_element ms_p_con_ack <location> <cell_desc>
Values

Valid range 0 to 31
... ...
5-518 68P02901W23-Q
Technical Description: BSS Command Reference ms_p_con_ack
... ...
... ...
Default value 2
References
Internal name P_CON_ACK

68P02901W23-Q 5-519
ms_p_con_interval Chapter 5: 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).

Dependencies hreqave
Syntax

chg_element ms_p_con_interval <value> <location> <cell_desc>
chg_cell_element ms_p_con_interval <value> <cell_desc>

disp_element ms_p_con_interval <location> <cell_desc>
Values

Valid range 0 to 31
5-520 68P02901W23-Q
Technical Description: BSS Command Reference ms_p_con_interval
... ...
... ...
Default value 2
References
Internal name P_CON_INTERVAL

68P02901W23-Q 5-521
ms_power_control_allowed Chapter 5: 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.
Dependencies None
Syntax

chg_element ms_power_control_allowed <value> <location> <cell_desc>
chg_cell_element ms_power_control_allowed <value> <cell_desc>

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
5-522 68P02901W23-Q
Technical Description: BSS Command Reference ms_power_control_allowed
References
Internal name EN_MS_PC

68P02901W23-Q 5-523
ms_power_offset Chapter 5: 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 will utilize 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.
Dependencies If the cell is not a type 3 MS cell, 0 is the only value allowed.
Syntax

chg_element ms_power_offset <value> <location> <cell_desc>
chg_cell_element ms_power_offset <value> <cell_desc>

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
5-524 68P02901W23-Q
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 a 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.
Dependencies frequency_type
Syntax

chg_element ms_txpwr_max_cch <value> <location> <cell_desc>
chg_cell_element ms_txpwr_max_cch <value> <cell_desc>

disp_element ms_txpwr_max_cch <location> <cell_desc>
Values
Value type
Integer (1 step = 2 dBm)
68P02901W23-Q 5-525
ms_txpwr_max_cch Chapter 5: CM database parameters
Valid range (2 to 19 for PGSM and EGSM cells)

Table 5-30 lists the maximum mobile power level for PGSM and EGSM cells.
Table 5-30 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 5-31 lists the maximum mobile power level for DCS1800 cells.
Table 5-31 Maximum mobile power level for DCS1800 cells

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
5-526 68P02901W23-Q
Technical Description: BSS Command Reference ms_txpwr_max_cch
Valid range (0 to 15, 30, 31 for PCS1900 cells)

Table 5-32 lists the maximum mobile power level for PCS1900 cells.
Table 5-32 Maximum mobile power level for PCS1900 cells

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-Q 5-527
ms_txpwr_max_cell Chapter 5: CM database parameters
ms_txpwr_max_cell
Description
The ms_txpwr_max_cell parameter specifies the maximum MS transmit power in each neighbour cell.
Dependencies ms_txpwr_max_def
Syntax

add_neighbor <src_gsm_cell_id>
<neighbor_gsm_cell_id> <placement> [<list_type>]
modify_neighbor <src_cell_id> <neighbor_cell_id>

ms_txpwr_max_cell <value>

disp_neighbor <src_gsm_cell_id>
Values

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
5-528 68P02901W23-Q
Technical Description: BSS Command Reference ms_txpwr_max_cell
References
GSM parameter MS_TXPWR_MAX(n)

68P02901W23-Q 5-529
ms_txpwr_max_def Chapter 5: CM database parameters
ms_txpwr_max_def
Description
The ms_txpwr_max_def parameter specifies the default value to be used for a neighbour cell when
the neighbour ms_txpwr_max_cell is not defined in an underlying neighbour instance.
Dependencies ms_txpwr_max_cell
Syntax

chg_element ms_txpwr_max_def <value> <location> <cell_desc>
chg_cell_element ms_txpwr_max_def <value> <cell_desc>

disp_element ms_txpwr_max_def <location> <cell_desc>
Values

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
5-530 68P02901W23-Q
Technical Description: BSS Command Reference ms_txpwr_max_def
References
GSM parameter MS_TXPWR_MAX_DEF

68P02901W23-Q 5-531
ms_txpwr_max_inner Chapter 5: 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.
Dependencies ms_txpwr_max_inner must be less than or equal to max_tx_ms if
the value for inner_zone_alg equals 1 (Dual Band Cells).
Syntax

chg_element ms_txpwr_max_inner <value> <location> <cell_desc>
chg_cell_element ms_txpwr_max_inner <value> <cell_desc>

disp_element ms_txpwr_max_inner <location> <cell_desc>
Values

Valid range Depends on the system:
5 to 39 (odd values only) PGSM/EGSM
0 to 30 (even values only) DCS1800
0 to 30 (even values only) PCS1900
Default value Same value as max_ts_ms
5-532 68P02901W23-Q
Technical Description: BSS Command Reference msc_bss_overload_allowed
msc_bss_overload_allowed
{24660, 24661}
Description
The msc_bss_overload_allowed parameter is a RSL Congestion Control (RCC) element which enables
or disables the BSC to send BSS Overload message to the MSC during RSL congestion.
Dependencies None
Syntax

chg_element msc_bss_overload_allowed <value> bsc

disp_element msc_bss_overload_allowed bsc
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1
68P02901W23-Q 5-533
msc_preference Chapter 5: 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.
Dependencies The Directed Retry or Multiband Inter-cell Handover feature must
be unrestricted.
Syntax

chg_element msc_preference <value> <location> <cell_desc>
chg_cell_element msc_preference <value> <cell_desc>

disp_element msc_preference <location> <cell_desc>
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.
5-534 68P02901W23-Q
Technical Description: BSS Command Reference msc_preference
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

68P02901W23-Q 5-535
msc_qt Chapter 5: 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.
This parameter is not related to DTX.

Dependencies This parameter only applies to the XCDR (location = 0).
Operator actions Place the system in SYSGEN ON mode
Syntax

chg_element msc_qt <value> 0
chg_element msc_qt <value> xcdr
5-536 68P02901W23-Q
Technical Description: BSS Command Reference msc_qt

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-Q 5-537
msc_release Chapter 5: 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.
Dependencies None
Syntax

chg_element msc_release <value> <location>

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
5-538 68P02901W23-Q
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 subsequently increased for RXLEV reasons.
Dependencies None
Syntax

chg_element mspwr_alg <value> <location> <cell_desc>
chg_cell_element mspwr_alg <value> <cell_desc>

disp_element mspwr_alg <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-539
mtl_loadshare_granularity Chapter 5: CM database parameters
mtl_loadshare_granularity
Description
The mtl_loadshare_granularity parameter sets the loadshare granularity across MTL links.
Dependencies If the element is changed in SYSGEN ON mode, the change takes
effect immediately.
Changes take effect only when all MTLs are locked.
Syntax

chg_element mtl_loadshare_granularity <value> 0

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
5-540 68P02901W23-Q
Technical Description: BSS Command Reference multiband_reporting
multiband_reporting
Description
The multiband_reporting parameter specifies the number of cells of each supported band
the system includes in the MS Measurement Report.
Syntax

chg_element multiband_reporting <value> <location> <cell_desc>
chg_cell_element multiband_reporting <value> <cell_desc>

disp_element multiband_reporting <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 3
0 Normal reporting of the six strongest neighbour cells with known
and allowed NCC part of the BSIC, irrespective of the band used.
1 Report the strongest neighbour cell, with known and allowed NCC
part of BSIC, in each of the frequency bands in the neighbour 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 neighbours in other bands
irrespective of the band used.
68P02901W23-Q 5-541
multiband_reporting Chapter 5: CM database parameters
2 Report the two strongest cells, with known and allowed NCC part
of BSIC, in each of the frequency bands in the neighbour cell list,
excluding the frequency band of the serving cell. The remaining
3 Report the three strongest cells, with known and allowed NCC part
of BSIC, in each of the frequency bands in the neighbour cell list,
excluding the frequency band of the serving cell. The remaining
Default value 0
References
GSM specification TS GSM 04.08 section 10.5.2.22

5-542 68P02901W23-Q
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 must be
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.
Syntax

chg_element n_avg_i <value> <location> <cell_desc>
chg_cell_element n_avg_i <value> <cell_desc>

disp_element n_avg_i <location> <cell_desc>
Values
Value type Integer (number of radio blocks)

Valid range 1 to 15
Default value 2
68P02901W23-Q 5-543
ncc_of_plmn_allowed Chapter 5: CM database parameters
ncc_of_plmn_allowed
Description
The ncc_of_plmn_allowed parameter is a bit mapped value which specifies which Network Colour
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 would be specified
by entering a value that would 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 would be entered for the ncc_of_plmn_allowed which would bit map 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 nonborder areas by specifying ncc_of_plmn_allowed
values that will bit map to the desired NCCs.
For example, the ncc_of_plmn_allowed value of 51 would bit map as: 00110011
The first, second, fifth, and sixth bits are set which would allow NCC values of 0, 1,
5, and 6 to be broadcast on BCCH carriers.
Dependencies None
Syntax

chg_element ncc_of_plmn_allowed <value> <location> <cell_desc>
chg_cell_element ncc_of_plmn_allowed <value> <cell_desc>

disp_element ncc_of_plmn_allowed <location> <cell_desc>
5-544 68P02901W23-Q
Technical Description: BSS Command Reference ncc_of_plmn_allowed
Values
Value type Integer

Valid range 0 to 255 (or 0 to FFh in Hex)
Default 255
Table 5-33 is a representation of the bit mapping of the ncc_of_plmn_allowed parameter. When a bit is set to
1, the corresponding NCC will be allowed. When a bit is set to 0, the corresponding NCC will not be allowed.
Table 5-33 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-Q 5-545
nccr_enabled Chapter 5: CM database parameters
nccr_enabled
Description
The nccr_enabled parameter specifies whether Network Controlled Cell Reselection

(NCCR) is enabled at a BSS.
Dependencies The GPRS and NCCR features must be unrestricted.
The PCU must be equipped.
Syntax

chg_element nccr_enabled 1 0

disp_element nccr_enabled 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-546 68P02901W23-Q
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 as delivered from Motorola.
If restricted, any attempt to access the other NCCR parameters is rejected.
Dependencies The GPRS and NCCR features must be unrestricted to provide their
associated functionality.
Syntax

disp_options
Values
Value type Boolean

Valid range 0 or 1
0 Restricted
1 Unrestricted
Default value None
68P02901W23-Q 5-547
neighbor_journal Chapter 5: CM database parameters
neighbor_journal
Description
The neighbor_journal parameter enables or disables neighbour journaling.

If journaling is enabled:
• There is no warm up period for neighbours. All neighbor information is padded with
0’s. Averaging and power budget calculations will begin immediately.
• If a previously reported neighbor is missing in the measurement report, a

0 rxlev is used for the neighbor.
• Disuse count must reach the cell list HREQAVE before being removed fro
the list of cell candidates for handover.
If journaling is disabled:
• There is a warmup period of the surround cell hreqave before power budget calculations begin.
• The last received rxlev for the unreported neighbor is used.
• Disuse count must reach 8 before being removed from the list of cell candidates for handover.

Dependencies None
Syntax

chg_element neighbor_journal <value> <location> <cell_desc>
chg_cell_element neighbor_journal <value> <cell_desc>

disp_element neighbor_journal <location> <cell_desc>
5-548 68P02901W23-Q
Technical Description: BSS Command Reference neighbor_journal
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-549
network_control_order Chapter 5: CM database parameters
network_control_order
Description
The network_control_order parameter specifies the GPRS Cell Reselection order.

Table 5-34 list the available configurations.
Table 5-34 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 MS 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 Network control All functionality in NC1 mode.
NC1 BSS sends cell reselection command to GPRS mobile to change
cell reselection mode


If inter_rat_enabled is set to 1 - Idle, and pccch_enabled is set to 1
- Enabled, any attempt to set the network_control_order parameter
to any of the values 1, 2, 3 or 4, will be rejected.
5-550 68P02901W23-Q
Technical Description: BSS Command Reference network_control_order
Syntax

chg_element network_control_order <value> <location> <cell_desc>
chg_cell_element network_control_order <value> <cell_desc>

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-Q 5-551
new_calls_hr Chapter 5: CM database parameters
new_calls_hr
Description
The {22064}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.
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

{22064}
chg_element new_calls_hr <value> <location> <cell_desc>
chg_cell_element new_calls_hr <value> <cell_desc>

{22064}
disp_element new_calls_hr <location> <cell_desc>
Values
Value type Integer (in steps of 1%)

Default value 101 101 disables this parameter
5-552 68P02901W23-Q
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.
Operator actions The MTL must be locked then unlocked for the change to take
effect.
Syntax

chg_element ni <value> 0

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-Q 5-553
ni Chapter 5: CM database parameters
References
GSM specification ITU - TSS Q.708

5-554 68P02901W23-Q
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 a NSVC is alive.
BSS software processes using this parameter are not notified when this parameter is changed.
Syntax

chg_element ns_alive_retries <value> <location>

disp_element ns_alive_retries <location>
Values
Value type Integer (number of retries)

Valid range 1 to 10
Default value 3
68P02901W23-Q 5-555
ns_block_retries Chapter 5: CM database parameters
ns_block_retries
Description
The ns_block_retries parameter specifies the number of retries generated to block a NSVC.
Syntax

chg_element ns_block_retries <value> <location>

disp_element ns_block_retries <location>
Values

Valid range 1 to 3
Default value 3
5-556 68P02901W23-Q
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 a NSVC.
Syntax

chg_element ns_unblock_retries <value> <location>

disp_element ns_unblock_retries <location>
Values

Valid range 1 to 3
Default value 3
68P02901W23-Q 5-557
nsei Chapter 5: 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.
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

chg_element nsei <value> <pcu_n>

disp_element nsei <pcu_n>
Values
Value type Integer

Default value none
5-558 68P02901W23-Q
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 a particular call is cleared by the auditing process.
This parameter provides a means of differentiating between glitches on a link and a complete link failure.
Dependencies None
Syntax

chg_element num_audit_retries <value> <location>

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-Q 5-559
num_emerg_access Chapter 5: 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.
An index value of 0 must be used for this element.
Dependencies None
Syntax

stat_mode num_emerg_access <value> <cell_desc>

disp_stat_prop num_emerg_access <cell_desc>
Values
Value type Boolean

Valid range off or on
off Disabled
on Enabled
Default value off
5-560 68P02901W23-Q
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.
Dependencies None
Syntax

stat_mode num_emerg_rejected <value> <cell_desc>

disp_stat_prop num_emerg_rejected <cell_desc>
Values
Value type Boolean

off Disabled
on Enabled
Default value off
68P02901W23-Q 5-561
num_emerg_tch_kill Chapter 5: 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.
Dependencies None
Syntax

stat_mode num_emerg_tch_kill <value> <cell_desc>

disp_stat_prop num_emerg_tch_kill <cell_desc>
Values
Value type Boolean

off Disabled
on Enabled
Default value off
5-562 68P02901W23-Q
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 a SDCCH
but could not be allocated a TCH for the specified GSM cell.
Dependencies None
Syntax

stat_prop num_emerg_term_sdcch <value> <cell_desc>

disp_stat_prop num_emerg_term_sdcch <cell_desc>
Values
Value type Boolean

off Disabled
on Enabled
Default value off
68P02901W23-Q 5-563
num_gbl_dl_thrput_samples Chapter 5: 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.
Syntax

chg_element gbl_dl_thrput_samples <value> <location> <cell_desc>

disp_element gbl_dl_thrput_samples <location> <cell_desc>
Values
Value type Integer (number of samples)

Valid range 1 to 10
Default value 10
5-564 68P02901W23-Q
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.
Syntax

chg_element gbl_ul_thrput_samples <value> <location> <cell_desc>

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-Q 5-565
number_of_preferred_cells Chapter 5: 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.
Dependencies None
Syntax

chg_element number_of_preferred_cells <value> <location> <cell_desc>
chg_cell_element number_of_preferred_cells <value> <cell_desc>

disp_element number_of_preferred_cells <location> <cell_desc>
Values
Value type Integer (represents preferred cells)

Valid range 1 to 16
Default value 16
5-566 68P02901W23-Q
Technical Description: BSS Command Reference number_of_preferred_cells
References
GSM specification 8.08 - 3.1.5.1.1

68P02901W23-Q 5-567
number_sdcchs_preferred Chapter 5: 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.
Dependencies This valid range for this parameter depends on ccch_conf.
This value must be less than or equal to the max_number_of_sdcchs.
Syntax

chg_element number_sdcchs_preferred <value> <location> <cell_desc>
chg_cell_element number_sdcchs_preferred <value> <cell_desc>

disp_element number_sdcchs_preferred <location> <cell_desc>
5-568 68P02901W23-Q
Technical Description: BSS Command Reference number_sdcchs_preferred
Values
Value type Integer (SDCCHs)

Valid range 4 to 44 If ccch_conf = 1, the values must be in multiples of 8 with an offset
of 4 (such as 4, 12, 20, ...,44)
8 to 48 If ccch_conf = 0, the values must be in multiples of 8 with an offset
of 0 (such as 8, 16, 24,...48).
Default value 4 if ccch_conf = 1, 8 if ccch_conf is not equal to 1
References

68P02901W23-Q 5-569
opc Chapter 5: 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-ASNI and 24-bit binary code for ASNI.
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.

Dependencies The range of opc depends on the values for the "ss7_mode" on
page 5-753.
This parameter only applies to the BSC.
Syntax

chg_element opc <value> 0

disp_element opc 0
5-570 68P02901W23-Q
Technical Description: BSS Command Reference opc
Values
Value type Integer

Valid range 0 to 16383 If ss7_mode = 0 (ITU-TSS)
0 to 16777215 If ss7_mode = 1 (ANSI)
Default value None
References
GSM specification ITU-TSS Q.708

68P02901W23-Q 5-571
option_alg_a5_1 Chapter 5: CM database parameters
option_alg_a5_1
Description
The option_alg_a5_1 parameter enables or disables the encryption algorithm A5/1.

Dependencies This parameter applies only to the BSC or RXCDR.
The Multiple Encryption feature must be unrestricted.
Syntax

chg_element option_alg_a5_1 <value> 0

disp_element option_alg_a5_1 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
References

5-572 68P02901W23-Q
Technical Description: BSS Command Reference option_alg_a5_2
option_alg_a5_2
Description

Dependencies This parameter only applies to the BSC or RXCDR.
Syntax


Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
References

68P02901W23-Q 5-573
option_alg_a5_3
Description

Dependencies This parameter only applies to the BSC or the RXCDR.
Syntax


Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
References

5-574 68P02901W23-Q
option_alg_a5_4
Description

Syntax


Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
References

68P02901W23-Q 5-575
option_alg_a5_5
Description

Syntax


Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
References

5-576 68P02901W23-Q
option_alg_a5_6
Description

Syntax


Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
References

68P02901W23-Q 5-577
option_alg_a5_7
Description

Syntax


Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
References

5-578 68P02901W23-Q
Technical Description: BSS Command Reference option_emergency_preempt
option_emergency_preempt
Description
The option_emergency_preempt parameter enables or disables the emergency call preemption option. The
emergency call preemption 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.
Syntax

chg_element option_emergency_preempt <value> 0

disp_element option_emergency_preempt 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-579
option_emergency_preempt Chapter 5: CM database parameters
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]
5-580 68P02901W23-Q
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.
Dependencies The Concentric Cells feature must be enabled.
Syntax

chg_element outer_zone_usage_level <value> <location> <cell_desc>
chg_cell_element outer_zone_usage_level <value> <cell_desc>

disp_element outer_zone_usage_level <location> <cell_desc>
Values
Value type Integer (indicating the percentage of outer zone TCH usage)
Default value 0
68P02901W23-Q 5-581
override_intra_bss_pre_transfer Chapter 5: CM database parameters
override_intra_bss_pre_transfer
Description
The override_intra_bss_pre_transfer parameter specifies whether or not 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.
This parameter also determines which method of audio connection is used for the BTS
concentration resource optimization for the handovers feature.
Syntax

chg_element override_intra_bss_pre_transfer <value> 0

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
5-582 68P02901W23-Q
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 neighbour cell BCCH when calculating power budget.
Dependencies The Dual Band Cells feature must be unrestricted.
Changing this parameter to 1 adds this cell to its own neighbour list.
This autocreated neighbour can not be deleted by the user and it can
only be deleted by changing this parameter back to 0.
Syntax

chg_element pbgt_mode <value> <location> <cell_desc>
chg_cell_element pbgt_mode <value> <cell_desc>

disp_element pbgt_mode <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
1 Enabled – A new neighbour is auto-equipped with BCCH frequency
set to that of the serving cell.
0 Disabled – A neighbour equipped as above is unequipped.
Default value 0
68P02901W23-Q 5-583
pccch_enabled Chapter 5: CM database parameters
pccch_enabled
Description
The pccch_enabled parameter specifies whether or not 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)
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.
ts_sharing must be set to 0 at the same cell site.
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

chg_element pccch_enabled <value> <location> <cell_desc>
chg_cell_element pccch_enabled <value> <cell-desc>
chg_cell_element <location> pccch_enabled <value> all

disp_element pccch_enabled <location> <cell-desc>
disp_element pccch_enabled <location> all
5-584 68P02901W23-Q
Technical Description: BSS Command Reference pccch_enabled
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-585
pccchOpt Chapter 5: 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 as delivered from Motorola.
If restricted, any attempt to access the other PBCCH/PCCCH parameters is rejected.
Dependencies The PBCCH/PCCCH features must be unrestricted to provide their
associated functionality.
Syntax

disp_options
Values
Value type Boolean

Valid range 0 or 1
0 Restricted
1 Unrestricted
Default value None
5-586 68P02901W23-Q
Technical Description: BSS Command Reference pcr_enable
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 (via the A interface).
If PCR is enabled, then:
• ss7_l2_t7 > 800 milliseconds.
• ss7_l3_t2 > 1400 milliseconds.

You must reset the BSC when changing this parameter
for the change to take effect.
Syntax

chg_element pcr_enable <value> 0

disp_element pcr_enable 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-587
pcr_n1 Chapter 5: CM database parameters
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.
Syntax

chg_element pcr_n1 <value> 0

disp_element pcr_n1 0
Values
Value type Integer (message signal units)

Default value 127
5-588 68P02901W23-Q
Technical Description: BSS Command Reference pcr_n2
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.
Syntax

chg_element pcr_n2 <value> 0

disp_element pcr_n2 0
Values
Value type Integer (message octets)

Default value 3750
68P02901W23-Q 5-589
pcu_redundancy Chapter 5: CM database parameters
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.
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

chg_element pcu_redundancy <value> bsc

disp_element pcu_redundancy bsc
Values
Value type Boolean

Valid range 0 PCU redundancy Off
1 PCU redundancy On
Default value 1
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>
5-590 68P02901W23-Q
Technical Description: BSS Command Reference pcu_redundancy
Please specify second redundant for PCU 0: <pcu_red_map_02>

The table below shows the possible entries and their meanings:
Parameter Valid Input Default

<pcu_red_map_01> 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
68P02901W23-Q 5-591
percent_traf_cs Chapter 5: CM database parameters
percent_traf_cs
Description
The percent_traf_cs parameter specifies the percentage of RSL Reserved for CS.
Syntax

chg_element percent_traf_cs <value> <location>

disp_element percent_traf_cs <location>
Values
Value type Integer

Valid range 0 to 90
Default value 55
5-592 68P02901W23-Q
Technical Description: BSS Command Reference persistence_level
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 4.
Syntax

chg_element persistence_level,i <value> <location> <cell_desc>
chg_cell_element persistence_level,i <value> <cell_desc>

disp_element persistence_level,i <location> <cell_desc>
68P02901W23-Q 5-593
persistence_level Chapter 5: CM database parameters
Values
Value type Integer

Valid range 0 to 15 representing the access persistence level:
0 persistence level 0
Default value 4
5-594 68P02901W23-Q
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.
Dependencies None
Syntax

chg_element phase_lock_gclk <value> <location>

disp_element phase_lock_gclk <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-595
phase_lock_retry Chapter 5: 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.
Dependencies None
Syntax

chg_element phase_lock_retry <value> <location>

disp_element phase_lock_retry <location>
Values
Value type Integer (minutes)

0 Immediate phase_lock_retry
1 to 254 Time period for retrying phase locking
255 No phase_lock_retry
Default value 255
5-596 68P02901W23-Q
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.
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

chg_element phase2_classmark_allowed <value> 0

disp_element phase2_classmark_allowed 0
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
68P02901W23-Q 5-597
phase2_resource_ind_allowed Chapter 5: CM database parameters
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.
Dependencies This parameter applies only to BSC sites.
This parameter does not apply to RXCDR sites.
Syntax

chg_element phase2_resource_ind_allowed <value> 0

disp_element phase2_resource_ind_allowed 0
Values
Value type Integer

Valid range 0 or 1
0 GSM Phase 1 format
1 GSM Phase 2 format
Default value 0
5-598 68P02901W23-Q
Technical Description: BSS Command Reference pic_error_clr_thresh
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).
Two successful calls are required to clear an alarm within this
threshold. (One call might be too short for the Channel Coder
Unit (CCU) to send an error indication, thus clearing the alarm
prematurely.)
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

chg_element pic_error_clr_thresh <value> 0

disp_element pic_error_clr_thresh 0
Values
Value type Integer

Default value 0
68P02901W23-Q 5-599
pic_error_gen_thresh Chapter 5: CM database parameters
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).
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

chg_element pic_error_gen_thresh <value> 0

disp_element pic_error_gen_thresh 0
Values
Value type Integer

Default value 6
5-600 68P02901W23-Q
Technical Description: BSS Command Reference pic_error_inc
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.
Syntax

chg_element pic_error_inc <value> 0

disp_element pic_error_inc 0
Values
Value type Integer

Valid range 0 PIC alarms not raised
1 to 255 PIC alarms raised
68P02901W23-Q 5-601
pkt_radio_type Chapter 5: CM database parameters
pkt_radio_type
Description
The pkt_radio_type parameter specifies the terrestrial resource capability of an RTF. The mutually
exclusive options are: none, 16 kbit/s, 32 kbit/s, and 64 kbit/s.
A BSS software process is notified whenever the pkt_radio_type element value is changed.
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 timeslots.
EGPRS RTFs can be equipped only if the Horizonmacro family of cabinets exists at the site
EGPRS RTFs and GPRS RTFs can be equipped in the same cell.
For baseband hopping only, the equipage of an RTF with Packet Radio Capability set to 64K and a
hopping system which is shared with any other RTF that is not a 64K RTF is not supported. Any
attempt to configure the system in this manner will be rejected.
EGPRS TRFs can baseband hop only if the master cabinet at the site is an Horizon II.
EGPRS RTFs with associated RSLs can not be equipped.
Sub-equipped EGPRS RTFs can not be equipped.
The pkt_radio_type parameter replaces and enhances the allow_32k_trau parameter
which is no longer supported.
The use_bcch_for_gprs parameter is not supported for EGPRS. The pkt_radio_type parameter provides
the ability to specify whether or not a BCCH RTF should be used for data.
Table 5-35 provides a guideline to backport and backfill the EGPRS database element, pkt_radio_type,
based on the pre-GSR7 parameters use_bcch_for_gprs (for the BCCH RTF) and allow_32k_trau.
5-602 68P02901W23-Q
Technical Description: BSS Command Reference pkt_radio_type
Table 5-35 EGPRS backport and backfill guideline
allow_32k_trau pkt_radio_type for

(original GSR7 non-BCCH RTF (GSR7 Meaning Coding schemes
element) EGPRS element)
0 0 - If GPRS restricted or RTF in No packet radio possible NA
inner zone on this RTF
1 - GPRS unrestricted and RTF 16 kbit/s packet radio CS1 and CS2
in outer zone possible on this RTF
1 2 32 kbit/s packet radio CS1 to CS4
possible on this RTF
NA 3 64 kbit/s packet radio MCS1 to MCS9 and
possible on this RTF CS1 to CS4
Table 5-36 shows the translation of use_bcch_for_gprs and allow_32k_trau pair of

parameters for the BCCH RTF to the new pkt_radio_type parameter. The translation from
GSR7 to GSR7 EGPRS is provided by the software.
EGPRS-capable RTFs must be explicitly equipped.
Table 5-36 pkt_radio_type translation
GSR7 EGPRS
Original GSR7 parameters
parameter Coding
Meaning
use_bcch_ allow_32k pkt_radio_type schemes
for_gprs _trau for BCCH RTF
0 don’t care No packet radio possible on this RTF 0 NA
1 0 16 kbit/s packet radio possible on 0 if GPRS CS1 and CS2
BCCH restricted;
1 if GPRS
unrestricted
1 1 If any 32K packet radio is configured 2 CS1 to CS4
in the cell, then 32 kbit/s packet radio
must be configured on the BCCH
RTF.
2 0 16 kbit/s packet radio possible on 1 CS1 and CS2
BCCH
2 1 If any 32K packet radio is configured 2 CS1 to CS4
in the cell, then 32 kbit/s packet radio
must be configured on the BCCH
RTF.
68P02901W23-Q 5-603
pkt_radio_type Chapter 5: CM database parameters

Dependencies An RTF can not be equipped with 64 kbit/s packet radio type if the
EGPRS feature is restricted.
To equip 64 kbit/s RTF requires a single density CTU2, and the
Coding Schemes 3 and 4 (CS3/4) feature and GPRS feature also
to be unrestricted.
An RTF can not be equipped with 16 kbit/s packet radio type if
the GPRS feature is restricted.
An RTF can not be equipped with 32 kbit/s packet radio type if the
Coding Schemes 3 and 4 feature is restricted.
64 kbit/s and 32 kbit/s can not be equipped at a BTS concentration
site.
A sub-equipped RTF can not be equipped with 64 kbit/s or 32 kbit/s
packet radio type.
there are no Horizonmacro or Horizon II macro family of cabinets
at the site.
An RTF can not be equipped with a non-zero packet radio type in
the inner zone of a cell.
extended range timeslots are configured.
there is an associated RSL.
An RTF can not be equipped when sharing a baseband hopping
system with a non-EGPRS RTF.
EGPRS RTFs can baseband hop only if the master cabinet at the
site is a Horizon II.
The BSS rejects the equippage of an RTF if the number of terrestrial
timeslots required by the RTF between BSC and the BTS exceeds
the number of free terrestrial timeslots between the BSC and the
BTS.
5-604 68P02901W23-Q
Technical Description: BSS Command Reference pkt_radio_type
Syntax
Changing this parameter causes the RTF to go out of service

and then back into service.
modify_value <location> pkt_radio_type <value>

rtf <dev_func_id1> <dev_func_id2>
Use the equip command to initiate this functional-

ity. Use the modify_value command to change its value.
When changing the pkt_radio_type element value a warning is displayed
indicating that the RTF will be cycled.

disp_equipment <location> rtf <dev_func_id1> <dev_func_id2>
Values
Value type Numeric Text

Valid range 0 to 3 none, 16k,
32k, and 64k
0 none No packet radio support
1 16k 16 kbit/s packet radio (CS1/2)
2 32k 32 kbit/s packet radio (CS3/4)
3 64k 64 kbit/s packet radio (EGPRS)
Default value 0 If GPRS is restricted or the RTF is in the inner zone.
1 If GPRS is unrestricted and the RTF is in the outer zone.
68P02901W23-Q 5-605
pool_gproc_preemption Chapter 5: CM database parameters
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.
This parameter can not be set at an RXCDR
Syntax

chg_element pool_gproc_preemption <value> 0

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
5-606 68P02901W23-Q
Technical Description: BSS Command Reference poor_initial_assignment
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 too far away, this indicates that there has been
a poor initial assignment, and therefore the RACH is discarded.
Dependencies None
Syntax

chg_element poor_initial_assignment <value> <location>

disp_element poor_initial_assignment <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-607
pow_inc_step_size_dl Chapter 5: CM database parameters
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.
Dependencies This parameter must be greater than or equal to
pow_red_step_size_dl.
Syntax

chg_element pow_inc_step_size_dl <value> <location> <cell_desc>
chg_cell_element pow_inc_step_size_dl <value> <cell_desc>

disp_element pow_inc_step_size_dl <location> <cell_desc>
Values

Valid range 2, 4, 6, 8, 10, 12 or 14
Default value 2
5-608 68P02901W23-Q
Technical Description: BSS Command Reference pow_inc_step_size_dl
References
GSM parameter POW_INC_STEP_SIZE_DL

GSM specification 12.20 - 5.2.8.23 - power Ctrl BTS - pow Incr Step Size
68P02901W23-Q 5-609
pow_inc_step_size_ul Chapter 5: CM database parameters
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.
pow_red_step_size_ul.
Syntax

chg_element pow_inc_step_size_ul <value> <location> <cell_desc>
chg_cell_element pow_inc_step_size_ul <value> <cell_desc>

disp_element pow_inc_step_size_ul <location> <cell_desc>
Values

Valid range 2, 4, 6 , 8, 10 12 or 14
Default value 2
5-610 68P02901W23-Q
Technical Description: BSS Command Reference pow_inc_step_size_ul
References
GSM parameter POW_INC_STEP_SIZE_UL

GSM specification 12.20 - 5.2.8.23 - power Ctrl BTS - pow Incr Step Size
68P02901W23-Q 5-611
pow_red_step_size_dl Chapter 5: CM database parameters
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.
Dependencies This parameter must be less than or equal to pow_inc_step_size_dl.
Syntax

chg_element pow_red_step_size_dl <value> <location> <cell_desc>
chg_cell_element pow_red_step_size_dl <value> <cell_desc>

disp_element pow_red_step_size_dl <location> <cell_desc>
Values

Valid range 2 or 4
Default value 2
5-612 68P02901W23-Q
Technical Description: BSS Command Reference pow_red_step_size_dl
References
GSM parameter POW_RED_STEP_SIZE_DL

GSM specification 12.20 - 5.2.8.23 - power Ctrl BTS - pow Red Step Size
68P02901W23-Q 5-613
pow_red_step_size_ul Chapter 5: CM database parameters
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.
Dependencies Must be less than or equal to pow_inc_step_size_ul.
Syntax

chg_element pow_red_step_size_ul <value> <location> <cell_desc>
chg_cell_element pow_red_step_size_ul <value> <cell_desc>

disp_element pow_red_step_size_ul <location> <cell_desc>
Values

Valid range 2 or 4
Default value 2
5-614 68P02901W23-Q
Technical Description: BSS Command Reference pow_red_step_size_ul
References
GSM parameter POW_RED_STEP_SIZE_UL

GSM specification 12.20 - 5.2.8.23 - power Ctrl BTS - pow Red Step Size
68P02901W23-Q 5-615
prach_max_retran Chapter 5: 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 4.
Syntax

chg_element prach_max_retran,i <value> <location> <cell_desc>
chg_cell_element prach_max_retran,i <value> <cell_desc>

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)
5-616 68P02901W23-Q
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.
Syntax

chg_element prach_s <value> <location> <cell_desc>
chg_cell_element prach_s <value> <cell_desc>

disp_element prach_s <location>
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
68P02901W23-Q 5-617
prach_s Chapter 5: CM database parameters
5 S = 55
6 S = 76
7 S = 109
8 S = 163
9 S = 217
Valid range 8 (S =163)
5-618 68P02901W23-Q
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.
Syntax

chg_element prach_tx_int <value> <location> <cell_desc>
chg_cell_element prach_tx_int <value> <cell_desc>

disp_element prach_tx_int <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 15 number of frame slots (see Table 5-37)
Default value 14 (32 slots)
68P02901W23-Q 5-619
prach_tx_int Chapter 5: CM database parameters
Table 5-37 Values for prach_tx_int representing number of frame slots
Value Number of slots Value Number of slots

0 2 slots 8 10 slots
5-620 68P02901W23-Q
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.
Syntax

chg_cell_element <location> primary_pcu <value> <cell_desc>
chg_element primary_pcu <value> location [<cell_desc>]

disp_element primary_pcu <location> <cell_desc>
Values
Value type Integer

Valid range -1, 0, 1 or 2
-1 No primary PCU
0 PCU_0
1 PCU_1
2 PCU_2
Default value -1
68P02901W23-Q 5-621
prioritize_microcell Chapter 5: CM database parameters
prioritize_microcell
Description
The prioritize_microcell parameter specifies whether or not the level (micro or macro) of
the serving cell impacts the sorting of the candidate list.
If prioritize_microcell is set to 0, the Handovers (HO) level of the service cell does
not impact sorting of the candidate list.
if prioritize_microcell is set to 1, the level of the serving cell impacts the sorting of the candidate list.
Dependencies The Microcell feature must be unrestricted
Syntax

chg_element prioritize_microcell <value> <location> <cell_desc>
chg_cell_element prioritize_microcell <value> <cell_desc>

disp_element prioritize_microcell <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
0 No impact on sorting
1 Impact on sorting
Default value 1
5-622 68P02901W23-Q
Technical Description: BSS Command Reference priority_class
priority_class
Description
The priority_class specifies the Hierarchical Cell Structure (HCS) for a cell.
Syntax

chg_element priority_class <value> <location> <cell_desc>
chg_cell_element priority_class <value> <cell_desc>

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
68P02901W23-Q 5-623
protect_last_ts Chapter 5: CM database parameters
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.
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.
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

chg_element protect_last_ts <value> <location> <cell_desc>
chg_cell_element protect_last_ts <value> <cell_desc>

disp_element protect_last_ts <location> <cell_desc>
Values
Value type Integer

Valid range 0 or 1
0 Last timeslot is not protected.
5-624 68P02901W23-Q
Technical Description: BSS Command Reference protect_last_ts
1 Last timeslot is protected.

Default value 0
68P02901W23-Q 5-625
prp_capacity_opt Chapter 5: CM database parameters
prp_capacity_opt
Description
The prp_capacity_opt parameter indicates whether the Packet Resource Processor (PRP) capacity
is unrestricted in the BSS software as delivered from Motorola.
If restricted, any attempt to access the other Enhanced Scheduling parameters is rejected.
Syntax

disp_options
Values
Value type Integer

Valid range 0 or 1
0 Restricted
1 Unrestricted
Default value None
5-626 68P02901W23-Q
Technical Description: BSS Command Reference prr_aggr_factor
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.
Dependencies Modification of prr_aggr_factor has no effect for cells that have
the pccch_enabled parameter enabled.
Syntax

chg_element prr_aggr_factor <value> <location>

disp_element prr_aggr_factor <location>
Values
Value type Integer

Valid range 0 to 4
Default value 3
68P02901W23-Q 5-627
pwr_handover_allowed Chapter 5: 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" might 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.
Dependencies None
Syntax

chg_element pwr_handover_allowed <value> <location> <cell_desc>
chg_cell_element pwr_handover_allowed <value> <cell_desc>

disp_element pwr_handover_allowed <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1
5-628 68P02901W23-Q
Technical Description: BSS Command Reference pwr_handover_allowed
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-Q 5-629
pwrc Chapter 5: CM database parameters
pwrc
Description
The pwrc parameter specifies whether or not the Broadcast Control Channels (BCCH) measurement
are included in the averaged value of hopping frequencies.
Dependencies None
Syntax

chg_element pwrc <value> <location> <cell_desc>
chg_cell_element pwrc <value> <cell_desc>

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
5-630 68P02901W23-Q
Technical Description: BSS Command Reference pwrc
References
GSM parameter PWRC

GSM specification GSM 4.08
5.08
68P02901W23-Q 5-631
queue_management_information Chapter 5: CM database parameters
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)
Dependencies The sum of (max_q_length_full_rate_channel +
max_q_length_sdcch) must be less than or equal to
queue_management_information.
Syntax

chg_element queue_management_information <value> <location> <cell_desc>
chg_cell_element queue_management_information <value> <cell_desc>

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
5-632 68P02901W23-Q
Technical Description: BSS Command Reference queue_management_information
References
Internal name EN_Q_ALLOWED

68P02901W23-Q 5-633
qsearch_c_initial Chapter 5: CM database parameters
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 behaviour 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.
Syntax

chg_element qsearch_c_initial <value> <location> <cell_desc>
chg_cell_element qsearch_c_initial <value> <cell_desc>

disp_element qsearch_c_initial <location> <cell_desc>
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 neighbour cells)
Default value 0
5-634 68P02901W23-Q
Technical Description: BSS Command Reference qsearch_i
qsearch_i
Description
The multi-RAT MS uses the qsearch_i parameter to decide when to start measure-
ment of a UTRAN neighbour cell.
Measurement of a UTRAN neighbour 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.
Syntax

chg_element qsearch_i <value> <location> <cell_desc>
chg_cell_element qsearch_i <value> <cell_desc>

disp_element qsearch_i <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 15
Default value 15
68P02901W23-Q 5-635
qsearch_p Chapter 5: CM database parameters
qsearch_p
Description
The qsearch_p parameter specifies the threshold below which a multi-RAT MS searches for 3G cells.
Syntax

chg_element qsearch_p <value> <location> <cell_desc>
chg_cell_element qsearch_p <value> <cell_desc>

disp_element qsearch_p <location> <cell_desc>
Values

Valid range 0 to 7 for signal strengths below the threshold see Table 5-38
8 to 15 for signal strengths above the threshold see Table 5-39
Default value 0
5-636 68P02901W23-Q
Technical Description: BSS Command Reference qsearch_p
Table 5-38 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 5-39 qsearch_p attribute values above threshold
Value Range
8 -78 dBm
9 -74dBm
10 -70 dBm
11 -66 dBm
12 -62 dBm
13 -58 dBm
14 -54 dBm
15 Infinity (never search for 3G cells)
68P02901W23-Q 5-637
ra_colour Chapter 5: CM database parameters
ra_colour
Description
The ra_colour parameter specifies the routing area colour used in System Information messages for
a specific cell and, therefore, indicates that GPRS is supported in the cell.
Dependencies The GPRS feature must be unrestricted. The ra_colour 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 can not be displayed until its value has been set.
Once the value of ra_colour has been set, it can not be unset.
Syntax

chg_element ra_colour <value> <location> <cell_desc>
chg_cell_element ra_colour <value> <cell_desc>

disp_element ra_colour <location> <cell_desc>
5-638 68P02901W23-Q
Technical Description: BSS Command Reference ra_colour
Values
Value type Integer (routing area colour for a cell)

Valid range 0 to 7
Default value None
68P02901W23-Q 5-639
ra_reselect_hysteresis Chapter 5: 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).
Syntax

chg_element ra_reselect_hysteresis <value> <location> <cell_desc>
chg_cell_element ra_reselect_hysteresis <value> <cell_desc>

disp_element ra_reselect_hysteresis <location> <cell_desc>
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-640 68P02901W23-Q
Technical Description: BSS Command Reference ra_reselect_hysteresis
5 10 dB
6 12 dB
7 14 dB
Default value None
68P02901W23-Q 5-641
rac Chapter 5: CM database parameters
rac
Description
The rac parameter specifies the routing area code (RAC) which is part of the cell identifier for GPRS cells.
Dependencies This parameter applies only to GPRS cells.
The GPRS feature must be unrestricted.
Operator actions This parameter can not be displayed until value has been set. Once
this value has been set, it can not be unset.
Syntax

chg_element rac <value> <location> <cell_desc>
chg_cell_element rac <value> <cell_desc>

disp_element rac <location> <cell_desc>
The RAC cannot be displayed if the value has not been previously configured
or modified by the operator.
5-642 68P02901W23-Q
Technical Description: BSS Command Reference rac
Values
Value type Integer (RAC for a cell)

Valid range 0 to 255 Null = unmodified
Default value None
68P02901W23-Q 5-643
rach_load_period Chapter 5: 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.
Other parameters can affect flow control. Refer to ccch_load_period, rach_overload_threshold,

ssm_normal_overload_threshold, ssm_normal_overload_threshold or tch_flow_control.
Dependencies This parameter must be less than or equal to ccch_load_period.
Syntax

chg_element rach_load_period <value> <location> <cell_desc>
chg_cell_element rach_load_period <value> <cell_desc>

disp_element rach_load_period <location> <cell_desc>
Values
Value type Integer

Default value 16
5-644 68P02901W23-Q
Technical Description: BSS Command Reference rach_load_period
References
Internal name RACH_MEAS_PERIOD

68P02901W23-Q 5-645
rach_load_threshold Chapter 5: 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 signalled 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. This
number is determined by the cell configuration. 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 will not be barred until the RACH load threshold is met, but in
the mean time attempted calls will get rejected, once the cell runs out of available traffic channels. If the
RACH load threshold is set to a value in the neighbourhood of T_SD_CHANNELS/MAX_RACH, the
system will gradually prevent 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 5-40 lists example cell configurations and their corresponding rach_load_threshold values.
Table 5-40 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%
Other parameters can affect flow control. Refer to ccch_load_period, rach_load_period,

ssm_normal_overload_threshold, ssm_normal_overload_threshold or tch_flow_control.
5-646 68P02901W23-Q
Technical Description: BSS Command Reference rach_load_threshold

Dependencies 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

chg_element rach_load_threshold <value> <location> <cell_desc>
chg_cell_element rach_load_threshold <value> <cell_desc>

disp_element rach_load_threshold <location> <cell_desc>
Values
Value type Integer

Default value 1000 (Disables flow control)
References
Internal name RACH_BUSY_THRES

68P02901W23-Q 5-647
rach_load_type Chapter 5: CM database parameters
rach_load_type
Description
The rach_load_type parameter specifies the RACH loading calculation method.

Dependencies None
Syntax

chg_element rach_load_type <value> <location>

disp_element rach_load_type <location>
Values
Value type Integer

Valid range 0 or 1
0 Percentage of RACH opportunities used
1 Percentage of total RACHs which are incorrect (collisions)
Default value None
5-648 68P02901W23-Q
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 a
user could reasonably be expected to hold while experiencing loss of audio.
Dependencies None
Syntax

add_cell <cell_desc> <location>
chg_element radio_link_timeout <value> <location> <cell_desc>
chg_cell_element radio_link_timeout <value> <cell_desc>

disp_element radio_link_timeout <location> <cell_desc>
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
68P02901W23-Q 5-649
radio_link_timeout Chapter 5: CM database parameters
... ...
... ...
... ...
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
5-650 68P02901W23-Q
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 will be initiated when the calculated value is greater
than the value specified for the rpd_trigger parameter.
Dependencies None
Syntax

chg_element rapid_pwr_down <value> <location> <cell_desc>
chg_cell_element rapid_pwr_down <value> <cell_desc>

disp_element rapid_pwr_down <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
68P02901W23-Q 5-651
rapid_pwr_down Chapter 5: CM database parameters
1 Enabled
Default value 0
5-652 68P02901W23-Q
Technical Description: BSS Command Reference rci_error_clr_thresh
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).
Dependencies Two successful calls are required on a resource before an alarm can
be cleared within this threshold. One successful call might be too
thus clearing the alarm prematurely.
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

chg_element rci_error_clr_thresh <value> 0

disp_element rci_error_clr_thresh 0
Values
Value type Integer

Default value 0
68P02901W23-Q 5-653
rci_error_gen_thresh Chapter 5: CM database parameters
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).
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

chg_element rci_error_gen_thresh <value> 0

disp_element rci_error_gen_thresh 0
Values
Value type Integer

Default value 6
5-654 68P02901W23-Q
Technical Description: BSS Command Reference rci_error_inc
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.
Syntax

chg_element rci_error_inc <value> 0

disp_element rci_error_inc 0
Values
Value type Integer

Valid range 0 RCI alarms not raised
1 to 255 RCI alarms raised
68P02901W23-Q 5-655
reconfig_fr_to_hr Chapter 5: CM database parameters
reconfig_fr_to_hr
Description
The {22064}reconfig_fr_to_hr parameter specifies the congestion level threshold. If this level is exceeded
at the target 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.
unrestricted.
Syntax

{22064}
chg_element reconfig_fr_to_hr <value> <location> <cell_desc>
chg_cell_element reconfig_fr_to_hr <value> <cell_desc>

{22064}
disp_element reconfig_fr_to_hr <location> <cell_desc>
Values
Value type Percentage

101 Disables this parameter
Default value 101
5-656 68P02901W23-Q
Technical Description: BSS Command Reference red_loss_daily
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.
Dependencies None
Syntax

chg_element red_loss_daily <value> <location>

disp_element red_loss_daily <location>
Values
Value type Integer (number of alarms)

Default value 16
68P02901W23-Q 5-657
red_loss_hourly Chapter 5: 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.
Dependencies None
Syntax

chg_element red_loss_hourly <value> <location>

disp_element red_loss_hourly <location>
Values

Default value 20
5-658 68P02901W23-Q
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 be taken OOS if the synchronization loss meets
or exceeds this threshold during a given red_time_loss period.
Dependencies None
Syntax

chg_element red_loss_oos <value> <location>

disp_element red_loss_oos <location>
Values

Default value 511
68P02901W23-Q 5-659
red_loss_restore Chapter 5: 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.
Dependencies None
Syntax

chg_element red_loss_restore <value> <location>

disp_element red_loss_restore <location>
Values
Valid type Integer (1 step = 100 milliseconds)

0 0 seconds 0 milliseconds
1 0.1 seconds 100 milliseconds
... ...
... ...
Default value 6000
5-660 68P02901W23-Q
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).
Dependencies None
Syntax

chg_element red_time_oos <value> <location>

disp_element red_time_oos <location>
Values

... ...
... ...
Default value 25
68P02901W23-Q 5-661
red_time_restore Chapter 5: 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.
Dependencies None
Syntax

chg_element red_time_restore <value> <location>

disp_element red_time_restore <location>
Values

... ...
... ...
Default value 600
5-662 68P02901W23-Q
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 reestablishment algorithm to determine which
cell to use for the attempt to reestablish the call.
Dependencies None
Syntax

chg_element reestablish_allowed <value> <location> <cell_desc>
chg_cell_element reestablish_allowed <value> <cell_desc>

disp_element reestablish_allowed <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
0 Enabled
68P02901W23-Q 5-663
reestablish_allowed Chapter 5: CM database parameters
1 Disabled
Default value 0
References
GSM parameter RE
GSM specification 5.08 - 6.7.2: Call reestablishment 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
5-664 68P02901W23-Q
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.
Dependencies When alg_num is set to 255, bin_num can not be set equal to
decision_1_tim_adv_av_alg
Operator actions Respond to the prompts after entering this command.
Syntax

chg_cell_element rel_tim_adv, <bin_num> <alg_num> <cell_desc>

disp_element rel_tim_adv,<bin_num> <location> <cell_desc>
68P02901W23-Q 5-665
rel_tim_adv Chapter 5: CM database parameters
Values
Value type Integer

Valid range alg_num value depends on different attributes:
Attribute Permissible range Default value
Hreqave 1 to 31 4
Hreqt 1 to 31 1
References

5-666 68P02901W23-Q
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.
Dependencies remote_loss_daily should be always less than remote_loss_hourly.
Syntax

chg_element remote_loss_daily <value> <location>

disp_element remote_loss_daily <location>
Values
Value type Integer (represents the number of alarms)

Default value 16
68P02901W23-Q 5-667
remote_loss_hourly Chapter 5: 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.
Dependencies remote_loss_daily should be always less than remote_loss_hourly.
Syntax

chg_element remote_loss_hourly <value> <location>

disp_element remote_loss_hourly <location>
Values

Default value 20
5-668 68P02901W23-Q
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.
Dependencies None
Syntax

chg_element remote_loss_oos <value> <location>

disp_element remote_loss_oos <location>
Values

Default value 511
68P02901W23-Q 5-669
remote_loss_restore Chapter 5: 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.
Dependencies None
Syntax

chg_element remote_loss_restore <value> <location>

disp_element remote_loss_restore <location>
Values

... ...
... ...
Default value 600
5-670 68P02901W23-Q
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).
Dependencies None
Syntax

chg_element remote_time_oos <value> <location>

disp_element remote_time_oos <location>
Values

... ...
... ...
Default value 25
68P02901W23-Q 5-671
remote_time_restore Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_element remote_time_restore <value> <location>

disp_element remote_time_restore <location>
Values

... ...
... ...
Default value 600
5-672 68P02901W23-Q
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.
Dependencies Must be less than report_resource_tch_f_low_water_mark
Syntax

chg_element report_resource_tch_f_high_water_mark
chg_cell_element report_resource_tch_f_high_water_mark
<value> <cell_desc>

disp_element report_resource_tch_f_high_water_mark <location> <cell_desc>
Values
Value type Integer (represents the number of TCHs)

Default value 2
68P02901W23-Q 5-673
report_resource_tch_f_high_water_mark Chapter 5: CM database parameters
References
GSM specification 8.08 - 3.2.2.4: reported message format

5-674 68P02901W23-Q
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.
Dependencies Must be greater than report_resource_tch_f_high_water_mark
Syntax

chg_element report_resource_tch_f_low_water_mark
chg_cell_element report_resource_tch_f_low_water_mark <value> <cell_desc>

disp_element report_resource_tch_f_low_water_mark <location> <cell_desc>
Values
Value type Integer (number of TCHs)

Default value 12
68P02901W23-Q 5-675
report_resource_tch_f_low_water_mark Chapter 5: CM database parameters
References
GSM specification 8.08 - 3.2.2.4: reported message format

5-676 68P02901W23-Q
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.
The equip RTF parameter with the same name is now obsolete.
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.
Syntax

chg_element res_gprs_pdchs <value> <location> <cell_desc>
chg_cell_element res_gprs_pdchs <value> <cell_desc>

disp_element res_gprs_pdchs <location> <cell_desc>
68P02901W23-Q 5-677
res_gprs_pdchs Chapter 5: CM database parameters
Values
Value type Integer (represents the number of PDCHs)

Valid range 0 to 30
Default value 0
5-678 68P02901W23-Q
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.
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.
Syntax

chg_element res_ts_less_one_carrier <value> <location> <cell_desc>
chg_cell_element res_ts_less_one_carrier <value> <cell_desc>

disp_element res_ts_less_one_carrier <location> <cell_desc>
68P02901W23-Q 5-679
res_ts_less_one_carrier Chapter 5: CM database parameters
Values
Value type Integer (timeslots)

Valid range 0 to 30
Default value Until set, assumes the value of res_gprs_pdchs
5-680 68P02901W23-Q
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.
Dependencies None
Syntax

chg_element rf_res_ind_period <value> <location>

disp_element rf_res_ind_period <location>
Values
Value type Integer (1 Step = 1 SACCH multiframe)

Default value 10
References
Internal name RF_RES_IND_PERIOD

68P02901W23-Q 5-681
rpd_offset Chapter 5: 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.
Dependencies This parameter must be less than rpd_trigger.The parameter
rapid_pwr_down must be
enabled.
Syntax

chg_element rpd_offset <value> <location> <cell_desc>
chg_cell_element rpd_offset <value> <cell_desc>

disp_element rpd_offset <location> <cell_desc>
Values
Value type Integer (1 dBm)

Valid range 0 to 63
Default value 8
5-682 68P02901W23-Q
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.
Dependencies The parameter rapid_pwr_down must be enabled.
Syntax

chg_element rpd_period <value> <location> <cell_desc>
chg_cell_element rpd_period <value> <cell_desc>

disp_element rpd_period <location> <cell_desc>
Values
Value type Integer (SACCH periods)

Valid range 1 to 32
Default value 2
68P02901W23-Q 5-683
rpd_trigger Chapter 5: 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.
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

chg_element rpd_trigger <value> <location> <cell_desc>
chg_cell_element rpd_trigger <value> <cell_desc>

disp_element rpd_trigger <location> <cell_desc>
5-684 68P02901W23-Q
Technical Description: BSS Command Reference rpd_trigger
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:
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
Default value 45 (- 65 dBm)
68P02901W23-Q 5-685
rpt_bad_qual_no_mr Chapter 5: 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 (as in GSR4).
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.
Dependencies None
Syntax

chg_element rpt_bad_qual_no_mr <value> <location> <cell_desc>
chg_cell_element rpt_bad_qual_no_mr <value> <cell_desc>

disp_cell <desc_cell> <"full">
disp_element rpt_bad_qual_no_mr <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 2
5-686 68P02901W23-Q
Technical Description: BSS Command Reference rpt_bad_qual_no_mr
0 The missed RXQUAL measurement report is left blank and it is not

used to signify the RXQUAL measurement (as in GSR4).
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-Q 5-687
rsl_congestion_control Chapter 5: CM database parameters
rsl_congestion_control
{24660, 24661}
Description
The rsl_congestion_control parameter is a BSS element that enables or disables

the RSL Congestion Control (RCC) feature.
Dependencies None
Syntax

chg_element rsl_congestion_control <value> bsc

disp_element rsl_congestion_control bsc
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1
5-688 68P02901W23-Q
Technical Description: BSS Command Reference rsl_lcf_congestion_thi
rsl_lcf_congestion_thi
{24660, 24661}
Description
The rsl_lcf_congestion_thi parameter specifies the RSL Congestion Control

(RCC) high congestion threshold at which an RSL-LTF board is in conges-
tion 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 (other than 0) which is less than the current value of rsl_lcf_congestion_tlow
parameter (see "rsl_lcf_congestion_tlow" on page 5-691).
A value of 0 represents that the RSL-LCF is disabled to send out XOFF information to the MTL-LCF board.
Dependencies The rsl_lcf_congestion_thi parameter must be greater than
rsl_lcf_congestion_tlow parameter, or set to 0.
When rsl_lcf_congestion_thi is set to 0, the RSL-LCF board stops
sending XON/XOFF messages to the MTL-LCF board.
Syntax

chg_element rsl_lcf_congestion_thi <value> bsc

disp_element rsl_lcf_congestion_thi bsc
68P02901W23-Q 5-689
rsl_lcf_congestion_thi Chapter 5: CM database parameters
Values

Default value 60
5-690 68P02901W23-Q
Technical Description: BSS Command Reference rsl_lcf_congestion_tlow
rsl_lcf_congestion_tlow
{24660, 24661}
Description
The rsl_lcf_congestion_tlow parameter specifies the RSL Congestion Control

(RCC) low congestion threshold at which an RSL-LTF board is out of conges-
tion 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 5-689).
Dependencies The rsl_lcf_congestion_tlow parameter must be less than
rsl_lcf_congestion_thi parameter..
Syntax

chg_element rsl_lcf_congestion_tlow <value> bsc

disp_element rsl_lcf_congestion_tlow bsc
Values

Valid range 0 to 99
Default value 25
68P02901W23-Q 5-691
rtf_path_enable Chapter 5: CM database parameters
rtf_path_enable
Description
The rtf_path_enable parameter enables or disables the RTF Fault Containment feature.
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

chg_element rtf_path_enable <value> 0

disp_element rtf_path_enable 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
5-692 68P02901W23-Q
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. This should be set to a value corresponding to a signal
level at which a call can be maintained in a particular environment.
Dependencies None
Syntax

chg_element rxlev_access_min <value> <location> <cell_desc>
chg_cell_element rxlev_access_min <value> <cell_desc>

disp_element rxlev_access_min <location> <cell_desc>
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:
1 -109 dBm
68P02901W23-Q 5-693
rxlev_access_min Chapter 5: CM database parameters
2 -108 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
5-694 68P02901W23-Q
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.
A bin_num must be specified with this command to indicate the location of the parameters to be modified.
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

Dependencies When alg_num is set to 255, bin_num can not 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
Syntax

chg_cell_element rxlev_dl_ho, <bin_num> <alg_num> <cell_desc>

dis_cell <cell_desc> <"full">
disp_element rxlev_dl_ho,<bin_num> <location> <cell_desc>
68P02901W23-Q 5-695
rxlev_dl_ho Chapter 5: CM database parameters
Values
Value type Integer

Hreqave 1 to 31 4
Hreqt 1 to 31 1
References
GSM parameter A_LEV_HO, A_PBGT_HO

5-696 68P02901W23-Q
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.
Enter hreqave:
Enter hreqt:
When entering disp_element rxlev_dl_pc, a bin_num must be specified to identify the

decision_1_dl_rxlev_av_p.
Syntax

chg_cell_element rxlev_dl_pc, <bin_num> <alg_num> <cell_desc>

disp_element rxlev_dl_pc,<bin_num> <location> <cell_desc>
68P02901W23-Q 5-697
rxlev_dl_pc Chapter 5: CM database parameters
Values
Value type Integer

Hreqave 1 to 31 4
Hreqt 1 to 31 1
References
GSM parameter A_LEV_PC

5-698 68P02901W23-Q
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.
Dependencies The Concentric Cells feature must be enabled and the
inner_zone_alg type must be set to 1.
Syntax

chg_element rxlev_dl_zone <value> <location> <cell_desc>
chg_cell_element rxlev_dl_zone <value> <cell_desc>

disp_element rxlev_dl_zone <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 63
below:
1 -109 dBm
2 -108 dBm
... ...
68P02901W23-Q 5-699
rxlev_dl_zone Chapter 5: CM database parameters
... ...
... ...
5-700 68P02901W23-Q
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.

Dependencies None
Syntax

chg_element rxlev_min_def <value> <location> <cell_desc>
chg_cell_element rxlev_min_def <value> <cell_desc>

disp_element rxlev_min_def <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 63
below:
1 -109 dBm
2 -108 dBm
... ...
68P02901W23-Q 5-701
rxlev_min_def Chapter 5: CM database parameters
... ...
... ...
Default value 15 (-95 dBm)
References

5-702 68P02901W23-Q
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.
Enter hreqave:
Enter hreqt:
When entering disp_element rxlev_ul_ho, a bin_num must be specified to identify the

decision_1_ul_rxlev_av_h or decision_1_ul_rxlev_av_ih.
Syntax

chg_cell_element rxlev_ul_ho, <bin_num> <alg_num> <cell_desc>

disp_element rxlev_ul_ho,<bin_num> <location> <cell_desc>
68P02901W23-Q 5-703
rxlev_ul_ho Chapter 5: CM database parameters
Values
Value type Integer

Hreqave 1 to 31 4
Hreqt 1 to 31 1
References
GSM parameter A_LEV_HO

5-704 68P02901W23-Q
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.
Enter hreqave:
Enter hreqt:
When entering disp_element rxlev_ul_pc, a bin_num must be specified to identify the

decision_1_ul_rxlev_av_p.
Syntax

chg_cell_element rxlev_ul_pc, <bin_num> <alg_num> <cell_desc>

disp_element rxlev_ul_pc,<bin_num> <location> <cell_desc>
68P02901W23-Q 5-705
rxlev_ul_pc Chapter 5: CM database parameters
Values
Value type Integer

Hreqave 1 to 31 4
Hreqt 1 to 31 1
References
GSM parameter A_LEV_PC

5-706 68P02901W23-Q
Technical Description: BSS Command Reference rxlev_ul_zone
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.
Dependencies The Concentric Cells Option must be enabled and the
inner_zone_alg parameter must be set to 1.
Syntax

chg_element rxlev_ul_zone <value> <location> <cell_desc>
chg_cell_element rxlev_ul_zone <value> <cell_desc>

disp_element rxlev_ul_zone <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 63
below:
1 -109 dBm
2 -108 dBm
... ...
68P02901W23-Q 5-707
rxlev_ul_zone Chapter 5: CM database parameters
... ...
... ...
Default value 63 (-47 dBm)
5-708 68P02901W23-Q
Technical Description: BSS Command Reference rxqual_dl_ho
rxqual_dl_ho
Description
The rxqual_dl_ho parameter specifies the averaging parameters for making handover
decisions for the downlink receive signal quality.
Enter hreqave:
Enter hreqt:
Enter w_qual:
When entering disp_element rxqual_dl_ho, a bin_num must be specified to identify

the location of the parameters to be displayed.
decision_1_dl_rxqual_av_h.
Syntax

chg_cell_element rxqual_dl_ho, <bin_num> <alg_num> <cell_desc>

disp_element rxqual_dl_ho,<bin_num> <location> <cell_desc>
68P02901W23-Q 5-709
rxqual_dl_ho Chapter 5: CM database parameters
Values
Value type Integer

Hreqave 1 to 31 4
Hreqt 1 to 31 1
Qual_weight 0 to 255 1
References
GSM parameter A_QUAL_HO

5-710 68P02901W23-Q
Technical Description: BSS Command Reference rxqual_dl_pc
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.
Enter hreqave:
Enter hreqt:
Enter w_qual:
When entering disp_element rxqual_dl_pc, a bin_num must be specified to identify

Syntax

chg_cell_element rxqual_dl_pc, <bin_num> <alg_num> <cell_desc>

disp_element rxqual_dl_pc,<bin_num> <location> <cell_desc>
68P02901W23-Q 5-711
rxqual_dl_pc Chapter 5: CM database parameters
Values
Value type Integer

Hreqave 1 to 31 4
Hreqt 1 to 31 1
References

5-712 68P02901W23-Q
Technical Description: BSS Command Reference rxqual_ul_ho
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.
Enter hreqave:
Enter hreqt:
Enter w_qual:
When entering disp_element rxqual_ul_ho, a bin_num must be specified to identify

decision_1_ul_rxqual_av_h.
Syntax

chg_cell_element rxqual_ul_ho, <bin_num> <alg_num> <cell_desc>

disp_element rxqual_ul_ho,<bin_num> <location> <cell_desc>
68P02901W23-Q 5-713
rxqual_ul_ho Chapter 5: CM database parameters
Values
Value type Integer

Hreqave 1 to 31 4
Hreqt 1 to 31 1
References
GSM parameter A_QUAL_HO

5-714 68P02901W23-Q
Technical Description: BSS Command Reference rxqual_ul_pc
rxqual_ul_pc
Description
The rxqual_ul_pc parameter specifies the averaging parameters for making power control
decisions for the uplink receive signal quality.
Enter hreqave:
Enter hreqt:
Enter w_qual:
When entering disp_element rxqual_ul_pc, a bin_num must be specified to identify

decision_1_ul_rxqual_av_p.
Syntax

chg_cell_element rxqual_ul_pc, <bin_num> <alg_num> <cell_desc>

disp_element rxqual_ul_pc,<bin_num> <location> <cell_desc>
68P02901W23-Q 5-715
rxqual_ul_pc Chapter 5: CM database parameters
Values
Value type Integer

Hreqave 1 to 31 4
Hreqt 1 to 31 1
References
GSM parameter A_QUAL_PC

5-716 68P02901W23-Q
Technical Description: BSS Command Reference sap_audit_type
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-23.
Dependencies None
Syntax

This parameter can not be modified from the MMI.

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
68P02901W23-Q 5-717
sap_device_type Chapter 5: CM database parameters
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-23.
Dependencies None
Syntax

This parameter can not be modified from the MMI.

disp_element sap_device_type,<index> <location>
Values
Value type Text

Valid range N/A
Default value None
5-718 68P02901W23-Q
Technical Description: BSS Command Reference sap_end_time
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).
Dependencies None
Syntax


disp_element sap_end_time,<index> <location>
Values
Value type Integer

Valid range Hours 0 to 23
Minutes 0 to 59
Default value None
68P02901W23-Q 5-719
sap_interval Chapter 5: CM database parameters
sap_interval
Description
The sap_interval parameter specifies the interval for a device audit.

military standard time or GMT (such as sap_interval = 13:45).
Dependencies None
Syntax


disp_element sap_interval,<index> <location>
sap_interval = interval_hour:interval_min
Values
Value type Integer

5-720 68P02901W23-Q
Technical Description: BSS Command Reference sap_interval
Minutes 0 to 59
Default value None
68P02901W23-Q 5-721
sap_start_time Chapter 5: CM database parameters
sap_start_time
Description
The sap_start_time parameter specifies the start time for a device audit.
military standard time or GMT (such as sap_end_time = 13:45).
Dependencies None
Syntax


disp_element sap_start_time,<index> <location>
sap_interval = interval_hour:interval_min
Values
Value type Integer

5-722 68P02901W23-Q
Technical Description: BSS Command Reference sap_start_time
Minutes 0 to 59
Default value None
68P02901W23-Q 5-723
sccp_bssap_mgt Chapter 5: CM database parameters
sccp_bssap_mgt
Description
The sccp_bssap_mgt parameter enables or disables ITU-TSS SCCP Management.

When enabled, the BSS detects Signalling 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. This flag should
be set only if the MSC does ITU-TSS SCCP Management.
All BTS site values are set to the same value assigned to site 0.
Dependencies This parameter applies only to the BSC.
chg_element command to change this parameter.
Syntax

chg_element sccp_bssap_mgt <value> 0

disp_element sccp_bssap_mgt 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
5-724 68P02901W23-Q
Technical Description: BSS Command Reference sccp_bssap_mgt
1 Enabled
Default value 1
68P02901W23-Q 5-725
scr_enabled Chapter 5: CM database parameters
scr_enabled
Description
The scr_enabled parameter specifies whether the Seamless Cell Reselection feature is enabled at a BSC, or not.
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.
This is a Motorola proprietary parameter.

Syntax

chg_element scr_enabled <value> <location>

disp_element scr_enabled <location>
Values
Value type Boolean

Valid range 0 or 1
0 Seamless cell reselection is not enabled (off)
5-726 68P02901W23-Q
Technical Description: BSS Command Reference scr_enabled
1 Seamless cell reselection is enabled (on)

Default value 0
68P02901W23-Q 5-727
sdcch_ho Chapter 5: CM database parameters
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) mea-
surement 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.
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

chg_element sdcch_ho <value> <location> <cell_desc>
chg_cell_element sdcch_ho <value> <cell_desc>

disp_element sdcch_ho <location> <cell_desc>
5-728 68P02901W23-Q
Technical Description: BSS Command Reference sdcch_ho
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 1
References
Internal name EN_SDCCH_HO
68P02901W23-Q 5-729
sdcch_need_high_water_mark Chapter 5: CM database parameters
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 in order to make more SDCCHs. The
total number of SDCCHs can not exceed the value of the max_number_of_sdcchs parameter.
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.
Syntax

chg_element sdcch_need_high_water_mark <value> <location> <cell_desc>
chg_cell_element sdcch_need_high_water_mark <value> <cell_desc>

disp_element sdcch_need_high_water_mark <location> <cell_desc>
5-730 68P02901W23-Q
Technical Description: BSS Command Reference sdcch_need_high_water_mark
Values
Value type Integer (representing the number of idle SDCCHs)

Valid range 1 to 39
Default value 2
References

68P02901W23-Q 5-731
sdcch_need_low_water_mark Chapter 5: CM database parameters
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 would stay above the number_sdcchs_preferred value.
Note 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.
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.
Syntax

chg_element sdcch_need_low_water_mark <value> <location> <cell_desc>
chg_cell_element sdcch_need_low_water_mark <value> <cell_desc>

disp_element sdcch_need_low_water_mark <location> <cell_desc>
5-732 68P02901W23-Q
Technical Description: BSS Command Reference sdcch_need_low_water_mark
Values
Value type Integer (number SDCCHs)

Default value 12
References

68P02901W23-Q 5-733
sdcch_tch_band_reassign_delay Chapter 5: CM database parameters
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 neighbour.
This parameter applies to multiband MSs only.
Use of this parameter may cause a delay in call setup of up to two seconds.
Dependencies The Multiband Inter-cell Handover feature must be unrestricted.
Syntax

chg_element sdcch_tch_band_reassign_delay <value> <location> <cell_desc>
chg_cell_element sdcch_tch_band_reassign_delay <value> <cell_desc>

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
5-734 68P02901W23-Q
Technical Description: BSS Command Reference sdcch_timer_ho
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.
Dependencies The sdcch_ho parameter must be enabled. (This is not monitored
by the system.)
Syntax

chg_element sdcch_timer_ho <value> <location> <cell_desc>
chg_cell_element sdcch_timer_ho <value> <cell_desc>

disp_element sdcch_timer_ho <location> <cell_desc>
Values
Value type Integer (1 Step = 2 SACCH multiframes)

Valid range 1 to 31
... ...
68P02901W23-Q 5-735
sdcch_timer_ho Chapter 5: CM database parameters
... ...
... ...
Default value 1
References
GSM parameter T_SDCCH_HO_ALLOWED

5-736 68P02901W23-Q
Technical Description: BSS Command Reference search_prio_3g
search_prio_3g
Description
The search_prio_3g parameter specifies whether 3G cells are searched when BSIC coding is required.
Dependencies The PBCCH/PCCCH feature must be unrestricted for this parameter
to change.
Syntax

chg_element search_prio_3g <value> <location> <cell_desc>
chg_cell_element search_prio_3g <value> <cell_desc>

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
68P02901W23-Q 5-737
second_asgnmnt Chapter 5: CM database parameters
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 pre-empt 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.
• 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.
5-738 68P02901W23-Q
Technical Description: BSS Command Reference second_asgnmnt
• The BSS does not attempt a multiband handover during the second assignment
if the MS is multiband capable.
Dependencies None
Syntax

chg_element second_asgnmnt <value> 0

disp_element second_asgnmnt 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-739
secondary_freq_type Chapter 5: CM database parameters
secondary_freq_type
Description
The secondary_freq_type parameter specifies the frequency type of the inner zone band of a Dual Band cell.
Dependencies This parameter is set to the primary frequency type when a cell is
not configured as a Dual Band cell.
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

chg_cell_element <location> secondary_freq_type <value> <location>

disp_element secondary_freq_type <location>
Values
Value type Integer

Valid range 1 to 8 binary values as shown below:
1 PGSM
5-740 68P02901W23-Q
Technical Description: BSS Command Reference secondary_freq_type
2 EGSM
4 DCS1800
8 PCS 1900
Default value None
68P02901W23-Q 5-741
sgsn_release Chapter 5: 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.
Syntax

chg_element sgsn_release <value> 0

disp_element sgsn_release 0
Values
Value type Integer (number of frames)

Valid range 0 or 1
0 SGSN is compliant with 3GPP Release 1998 or older.
1 SGSN is compliant with 3GPP Release 1999 or newer.
Default value 0
5-742 68P02901W23-Q
Technical Description: BSS Command Reference slip_loss_daily
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 would indicate a much more serious problem.
Dependencies This parameter must be less than slip_loss_hourly.
Syntax

chg_element slip_loss_daily <value> <location>

disp_element slip_loss_daily <location>
Values
Value type Integer

Default value 4
68P02901W23-Q 5-743
slip_loss_hourly Chapter 5: CM database parameters
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 would indicate a much more serious problem.
Dependencies This parameter must be greater than slip_loss_daily.
Syntax

chg_element slip_loss_hourly <value> <location>

disp_element slip_loss_hourly <location>
Values
Value type Integer

Default value 10
5-744 68P02901W23-Q
Technical Description: BSS Command Reference slip_loss_hourly
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-Q 5-745
slip_loss_oos Chapter 5: 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.
Dependencies None
Syntax

chg_element slip_loss_oos <value> <location>

disp_element slip_loss_oos <location>
Values
Value type Integers

Default value 255
5-746 68P02901W23-Q
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.
Dependencies None
Syntax

chg_element slip_loss_restore <value> <location> <cell_desc>

disp_element slip_loss_restore <location> <cell_desc>
Values
Value type Integer (1 step = 100 milliseconds

... ...
... ...
Default value 600 60 seconds 60000 milliseconds
68P02901W23-Q 5-747
smg_gb_vers Chapter 5: 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.
Operator actions The PCU must be locked.
Syntax

chg_element smg_gb_vers <value> 0

disp_element smg_gb_vers <value> 0
Values
Value type Integer

Default value 31
5-748 68P02901W23-Q
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).
Dependencies The SMS Point to Point feature must be unrestricted.
Syntax

chg_element sms_dl_allowed <value> <location>

disp_element sms_dl_allowed <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
References

68P02901W23-Q 5-749
sms_tch_chan Chapter 5: 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 will be 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 would be more noticeable as the size of the short message increases, but
using the SACCH for larger short messages means longer delivery times.
SMS on the FACCH is not covered in the GSM specifications and may not
be supported by mobile stations.
Syntax

chg_element sms_tch_chan <value> <location>

disp_element sms_tch_chan <location>
5-750 68P02901W23-Q
Technical Description: BSS Command Reference sms_tch_chan
Values
Value type Integer

Valid range 0 to 2
0 BSS_ALGORITHM
1 FACCH always used
2 SACCH always used
Default value 2
References

68P02901W23-Q 5-751
sms_ul_allowed Chapter 5: CM database parameters
sms_ul_allowed
Description
The sms_ul_allowed parameter enables or disables uplink (MS originated) Short Message Service (SMS).
Syntax

chg_element sms_ul_allowed <value> <location>

disp_element sms_ul_allowed <location>
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
References

5-752 68P02901W23-Q
Technical Description: BSS Command Reference ss7_mode
ss7_mode
Description
The ss7_mode parameter specifies the type of SS#7 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 user 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.
Dependencies The system checks the values of the opc (see "opc" on page 5-570)
and dpc (see "dpc" on page 5-204) 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 would cause 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 would cause 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

chg_element ss7_mode <value> <location>

disp_element ss7_mode <location>
68P02901W23-Q 5-753
ss7_mode Chapter 5: CM database parameters
Values
Value type Boolean

Valid range 0 or 1
0 ITU version
1 ANSI version
Default value 0
5-754 68P02901W23-Q
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 (400). 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.

rach_load_threshold, ssm_normal_overload_threshold or tch_flow_control.
Dependencies Must be greater than the ssm_normal_overload_threshold
parameter.
Syntax

chg_element ssm_critical_overload_threshold <value> 0

disp_element ssm_critical_overload_threshold 0
68P02901W23-Q 5-755
ssm_critical_overload_threshold Chapter 5: CM database parameters
Values
Value type Integer (percent of call information blocks in use)

Default value 80
5-756 68P02901W23-Q
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.
Every time the usage equals or exceeds this threshold, one access class will be barred.

rach_load_threshold, ssm_critical_overload_threshold or tch_flow_control.
Dependencies Must be less than the ssm_critical_overload_threshold parameter.
Syntax

chg_element ssm_normal_overload_threshold <value> 0

disp_element ssm_normal_overload_threshold 0
Values
Value type Integer (percent of call information blocks in use)

Default value 70
68P02901W23-Q 5-757
ssp_burst_delay Chapter 5: CM database parameters
ssp_burst_delay
Description
The ssp_burst_delay parameter specifies the length of time between the bursts of data. The number
of messages in each burst are specified by the ssp_burst_limit parameter.
Statistical information is forwarded from the Site Statistics Process (SSP) to the
Central Statistics Process (CSP) in bursts.
Dependencies None
Syntax

chg_element ssp_burst_delay <value> <location>

disp_element ssp_burst_delay <location>
Values

Default value 200
5-758 68P02901W23-Q
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 length
of time between bursts is specified by the ssp_burst_delay parameter.
Statistical information is forwarded from the Site Statistical Process (SSP) to the
Central Statistical Process (CSP) in bursts.
Dependencies None
Syntax

chg_element ssp_burst_limit <value> <location>

disp_element ssp_burst_limit <location>
Values
Value type Integer (number of messages)

Default value 10
68P02901W23-Q 5-759
stat_interval Chapter 5: 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.
Dependencies Must be set to 30 or 60 minutes to align with the OMC-R.
Syntax

chg_element stat_interval <value> 0

disp_element stat_interval 0
Values

Valid range 5 to 60
Default value 30
Although any value between 5 and 60 minutes is valid, the OMC-R only parses uploaded
statistics files if this attribute is set to 30 or 60 minutes.
5-760 68P02901W23-Q
Technical Description: BSS Command Reference surround_cell
surround_cell
Description
The surround_cell parameter specifies the averaging parameter for a serving cell’s neighbour cells.
The system uses this parameter to determine which neighbour cell to hand off to.
Enter hreqave:
Enter hreqt:
When entering disp_element surround_cell, a bin_num must be specified to identify

decision_1_pbgt_rxlev_av_h.
Syntax

chg_cell_element surround_cell, <bin_num> <alg_num> <cell_desc>

disp_element surround_cell,<bin_num> <location> <cell_desc>
68P02901W23-Q 5-761
surround_cell Chapter 5: CM database parameters
Values
Value type Integer

Default value None
References
GSM parameter A_PBGT_HO

5-762 68P02901W23-Q
Technical Description: BSS Command Reference sw_ts_less_one_carrier
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.
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.
Syntax

chg_element sw_ts_less_one_carrier <value> <location> <cell_desc>
chg_cell_element sw_ts_less_one_carrier <value> <cell_desc>

disp_element sw_ts_less_one_carrier <location> <cell_desc>
68P02901W23-Q 5-763
sw_ts_less_one_carrier Chapter 5: CM database parameters
Values
Value type Integer (number of timeslots)

Valid range 0 to 30
Default value Until set, assumes the value of switch_gprs_pdchs
5-764 68P02901W23-Q
Technical Description: BSS Command Reference swfm_enable
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.
Dependencies This parameter applies only to a BSC.
Syntax

chg_element swfm_enable <value> 0

disp_element swfm_enable 0
Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 5-765
switch_gprs_pdchs Chapter 5: CM database parameters
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.
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 5-303, must be
exceeded.
Syntax

chg_element switch_gprs_pdchs <value> <location> <cell_desc>
chg_cell_element switch_gprs_pdchs <value> <cell_desc>

disp_element switch_gprs_pdchs <location> <cell_desc>
5-766 68P02901W23-Q
Technical Description: BSS Command Reference switch_gprs_pdchs
Values
Value type Integer (number of timeslots)

Valid range 0 to 30
Default value 0
68P02901W23-Q 5-767
sync_loss_daily Chapter 5: CM database parameters
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.
Dependencies This parameter must be less than sync_loss_hourly.
Syntax

chg_element sync_loss_daily <value> <location>

disp_element sync_loss_daily <location>
Values
Value type Integer

Default value 16
5-768 68P02901W23-Q
Technical Description: BSS Command Reference sync_loss_hourly
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.
Dependencies This parameter must be greater than sync_loss_daily.
Syntax

chg_element sync_loss_hourly <value> <location>

disp_element sync_loss_hourly <location>
Values
Value type Integer

Default value 20
68P02901W23-Q 5-769
sync_loss_oos Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_element sync_loss_oos <value> <location>

disp_element sync_loss_oos <location>
Values
Value type Integer

Default value 511
5-770 68P02901W23-Q
Technical Description: BSS Command Reference sync_loss_restore
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.
Dependencies None
Syntax

chg_element sync_loss_restore <value> <location>

disp_element sync_loss_restore <location>
Values
Value type Integer (1 step = 100 milliseconds)

1 0.1 second 100 milliseconds
.. . .. . .. .

.. . .. . .. .
68P02901W23-Q 5-771
sync_time_oos Chapter 5: CM database parameters
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).
Dependencies None
Syntax

chg_element sync_time_oos <value> <location>

disp_element sync_time_oos <location>
Values

1 0.1 second 100 milliseconds
.. . .. . .. .

.. . .. . .. .
Default value 25 2.5 seconds 2500 milliseconds
5-772 68P02901W23-Q
Technical Description: BSS Command Reference sync_time_restore
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.
Dependencies None
Syntax

chg_element sync_time_restore <value> <location>

disp_element sync_time_restore <location>
Values

... ...
... ...
68P02901W23-Q 5-773
t_avg_t Chapter 5: CM database parameters
t_avg_t
Description
The t_avg_t parameter specifies the number of multiframes for C averaging in the Transfer state.
(TAVG_W is the number of multiframes for C averaging in the Wait state).
Syntax

chg_element t_avg_t <value> <location> <cell_desc>
chg_cell_element t_avg_t <value> <cell_desc>

disp_element t_avg_t <location> <cell_desc>
Values

Valid range 0 to 25
Default value 10
5-774 68P02901W23-Q
Technical Description: BSS Command Reference t_avg_w
t_avg_w
Description
The t_avg_w parameter specifies the number of multiframes for C averaging in the Wait state. (TAVG_T
is the number of multiframes for C averaging in the Transfer state).
Syntax

chg_element t_avg_w <value> <location> <cell_desc>
chg_cell_element t_avg_w <value> <cell_desc>

disp_element t_avg_w <location> <cell_desc>
Values

Valid range 0 to 25
Default value 10
68P02901W23-Q 5-775
tch_busy_critical_threshold Chapter 5: CM database parameters
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.
tch_busy_norm_threshold.
Syntax

chg_element tch_busy_critical_threshold <value> <location>

disp_element tch_busy_critical_threshold <location>
Values
Value type Integer (percent of busy TCHs)

Default value 100
5-776 68P02901W23-Q
Technical Description: BSS Command Reference tch_busy_norm_threshold
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.
Dependencies This parameter must be less than or equal to tch_busy_criti-
cal_threshold.
Syntax

chg_element tch_busy_norm_threshold <value> <location>

disp_element tch_busy_norm_threshold <location>
Values
Value type Integer (percent of busy TCHs)

Default value 100
68P02901W23-Q 5-777
tch_congest_prevent_thres Chapter 5: CM database parameters
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.
Type A (no operation actions)
Dependencies The Congestion Relief feature must be enabled.
This parameter must be greater than or equal to mb_tch_con-
gest_thres.
Syntax

chg_element tch_congest_prevent_thres <value> <location> <cell_desc>

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).
5-778 68P02901W23-Q
Technical Description: BSS Command Reference tch_flow_control
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.

rach_load_threshold, ssm_critical_overload_threshold, or ssm_normal_overload_threshold.
Dependencies None
Syntax

chg_element tch_flow_control <value> <location> <cell_desc>
chg_cell_element tch_flow_control <value> <cell_desc>

disp_element tch_flow_control <location> <cell_desc>
Values
Value type Boolean

Valid range 0 or 1
68P02901W23-Q 5-779
tch_flow_control Chapter 5: CM database parameters
0 Disabled
1 Enabled
Default value 0
5-780 68P02901W23-Q
Technical Description: BSS Command Reference tch_full_need_low_water_mark
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_low_water_mark, the CRM
tries to reconfigure TCHs in order to make more SDCCHs. For a TCH to be reconfigured, the number
of TCHs must be greater than the value of the tch_full_need_low_water_mark parameter.
Dependencies channel_reconfiguration_switch feature must be enabled.
Syntax

chg_element tch_full_need_low_water_mark <value> <location> <cell_desc>
chg_cell_element tch_full_need_low_water_mark <value> <cell_desc>

disp_element tch_full_need_low_water_mark <location> <cell_desc>
68P02901W23-Q 5-781
tch_full_need_low_water_mark Chapter 5: CM database parameters
Values
Value type Integer (number of channels)

Default value 255
5-782 68P02901W23-Q
Technical Description: BSS Command Reference temporary_offset
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.
Dependencies The cell_reselect_param_ind parameter must be enabled.
Syntax

chg_element temporary_offset <value> <location> <cell_desc>
chg_cell_element temporary_offset <value> <cell_desc>

disp_element temporary_offset <location> <cell_desc>
Values

Valid range 0 to 7
Default value 0
68P02901W23-Q 5-783
temporary_offset Chapter 5: CM database parameters
References
GSM parameter C2
GSM specification TS GSM 4.08 Table 10.32a section 10.5.2.35
TS GSM 5.08
5-784 68P02901W23-Q
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 Signalling Connection Control Part (SCCP) number before rejecting the request.
Dependencies None
Syntax

chg_element threshold <value> <location> <cell_desc>
chg_cell_element threshold <value> <cell_desc>

disp_element threshold <location> <cell_desc>
Values
Value type Integer (number of assign attempts.)

Default value 7
68P02901W23-Q 5-785
timing_advance_period Chapter 5: 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 (n8 - p8 + 1) x hreqavex/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.
Dependencies hreqave, n8, p8
Syntax

chg_element timing_advance_period <value> <location> <cell_desc>
chg_cell_element timing_advance_period <value> <cell_desc>
5-786 68P02901W23-Q
Technical Description: BSS Command Reference timing_advance_period

disp_element timing_advance_period <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 31 Mapped to SACCH multiframes:
... ...
... ...
... ...
Default value 4 8 SACCH multiframes
68P02901W23-Q 5-787
tlli_blk_coding Chapter 5: 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).
Syntax

chg_element tlli_blk_coding <value> <location> <cell_desc>
chg_cell_element tlli_blk_coding <value> <cell_desc>

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.
5-788 68P02901W23-Q
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.
Dependencies This parameter is used only when handover records are requested
and RSS, Abis and/or MS Power control data are specified.
Syntax

chg_element trace_msgs_after_ho <value> 0

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-Q 5-789
trace_msgs_before_ho Chapter 5: 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.
Dependencies This parameter is used only when handover records are requested
and RSS, Abis and/or MS Power control data are specified.
Syntax

chg_element trace_msgs_before_ho <value> 0

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
5-790 68P02901W23-Q
Technical Description: BSS Command Reference trans_capability
trans_capability
Description
The trans_capability parameter specifies the transcoding capability of an MSI type GDP or GDP2.
When equipping an MSI GDP, the user is prompted to equip it as either basic or enhanced.
When equipping an MSI GDP2, the user also has the option of equipping it as GDP_2E1. A
GDP2 with transcoding capability of GDP_2E1 has two MMS.
Dependencies A GDP2 is required for the transcoding capability of GDP_2E1.
Syntax

modify_value 0 trans_capability <value> MSI <msi_id>
equip 0 MSI
After entering the equip MSI command, the user is prompted for the following parameters:
• First MSI identifier.
• Cage number.
• Slot number.
• MSI type.
• MSI ID to the MSC.
• Transcoding capability.

disp_equipment 0 MSI <msi_id>
68P02901W23-Q 5-791
trans_capability Chapter 5: CM database parameters
Values
Value type Integer

Valid range 0 to 2
0 Basic
1 Enhanced
2 GDP-2E1
Default value None
5-792 68P02901W23-Q
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.
Dependencies This parameter must be greater than the value assigned to the
trunk_major_threshold parameter unless both values are set to 0.
Syntax

chg_element trunk_critical_threshold <value> 0

disp_element trunk_critical_threshold 0
Values
Value type Integer (percent of trunk capacity)

Default value 50
68P02901W23-Q 5-793
trunk_major_threshold Chapter 5: 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.
Dependencies This parameter must be less than the value assigned to the
trunk_critical_threshold parameter unless both values are set to 0.
Syntax

chg_element trunk_major_threshold <value> 0

disp_element trunk_major_threshold 0
Values
Value type Integer (percent of trunk capacity)

Valid range 0 to 99
Default value 10
5-794 68P02901W23-Q
Technical Description: BSS Command Reference ts_alloc_flag
ts_alloc_flag
Description
The ts_alloc_flag parameter alters the E1/T1 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 subsequently equipped devices.
Dependencies This parameter cannot be altered unless the Aggregate Abis feature
is enabled.
Syntax

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

disp_element ts_alloc_flag 0
Values
Value type Boolean

Valid range 0 or 1
0 Use existing algorithm
1 Use new algorithm
Default value 0
68P02901W23-Q 5-795
ts_in_usf_active Chapter 5: CM database parameters
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.
Dependencies The EOP feature must be unrestricted.
The number of non-BCCH timeslots that will broadcast continuously
at full power even when no mobile is active on that timeslot.
Syntax

chg_element ts_in_usf_active <value> <location> <cell_desc>
chg_cell_element ts_in_usf_active <value> <cell_desc>

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
5-796 68P02901W23-Q
Technical Description: BSS Command Reference tsc_update_method
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.

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

chg_element tsc_update_method <value> 0

disp_element tsc_update_method 0
Values
Value type Integer

Valid range 0 to 2
0 Update the BCCH/CCCH timeslots
1 Update all timeslots on the BCCH carrier
68P02901W23-Q 5-797
tsc_update_method Chapter 5: CM database parameters
2 Update all timeslots on all carriers of cell

Default value 0
5-798 68P02901W23-Q
Technical Description: BSS Command Reference tx_integer
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.
Dependencies None
Syntax

chg_element tx_integer <value> <location> <cell_desc>
chg_cell_element tx_integer <value> <cell_desc>

disp_element tx_integer <location> <cell_desc>
68P02901W23-Q 5-799
tx_integer Chapter 5: CM database parameters
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
5-800 68P02901W23-Q
Technical Description: BSS Command Reference tx_power_cap
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. This parameter is not valid for micro sites.
This parameter can be set when the primary outer zone frequency type of the cell is PGSM,
EGSM, DCS1800, and PCS1900 provided that 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 Horizon II macro or Horizon II macro extension cabinets are
forced to operate in high power mode (32 watts).
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

chg_element tx_power_cap <value> <location> <cell_desc>
chg_cell_element tx_power_cap <value> <cell_desc>

disp_element tx_power_cap <location> <cell_desc>
68P02901W23-Q 5-801
tx_power_cap Chapter 5: CM database parameters
Values
Value type Boolean

Valid range 0 or 1
0 Low power
1 High power
Default value 0
5-802 68P02901W23-Q
Technical Description: BSS Command Reference u_rxlev_dl_ih
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.
Dependencies This parameter is used by the BSS only when interfer_ho_allowed
= 1.
Syntax

chg_element u_rxlev_dl_ih <value> <location> <cell_desc>
chg_cell_element u_rxlev_dl_ih <value> <cell_desc>

disp_element u_rxlev_dl_ih <location> <cell_desc>
Values

68P02901W23-Q 5-803
u_rxlev_dl_ih Chapter 5: CM database parameters
0 -110 dBm
1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm
Default value 45 -65 dBm
References
GSM parameter RXLEV_DL_IH

5-804 68P02901W23-Q
Technical Description: BSS Command Reference u_rxlev_dl_p
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.
Dependencies None
Syntax

chg_element u_rxlev_dl_p <value> <location> <cell_desc>
chg_cell_element u_rxlev_dl_p <value> <cell_desc>

disp_element u_rxlev_dl_p <location> <cell_desc>
Values

68P02901W23-Q 5-805
u_rxlev_dl_p Chapter 5: CM database parameters
0 -110 dBm or lower

1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
63 -47 dBm or higher
References
GSM parameter U_RXLEV_DL_P

5-806 68P02901W23-Q
Technical Description: BSS Command Reference u_rxlev_ul_ih
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.
Dependencies This parameter is used by the BSS only when interfer_ho_allowed
is 1.
Syntax

chg_element u_rxlev_ul_ih <value> <location> <cell_desc>
chg_cell_element u_rxlev_ul_ih <value> <cell_desc>

disp_element u_rxlev_ul_ih <location> <cell_desc>
Values

68P02901W23-Q 5-807
u_rxlev_ul_ih Chapter 5: CM database parameters
0 -110 dBm or lower

1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
References
GSM parameter RXLEV_UL_IH

5-808 68P02901W23-Q
Technical Description: BSS Command Reference u_rxlev_ul_p
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.
Dependencies None
Syntax

chg_element u_rxlev_ul_p <value> <location> <cell_desc>
chg_cell_element u_rxlev_ul_p <value> <cell_desc>

disp_element u_rxlev_ul_p <location> <cell_desc>
Values

68P02901W23-Q 5-809
u_rxlev_ul_p Chapter 5: CM database parameters
0 -110 dBm or lower

1 -109 dBm
2 -108 dBm
... ...
... ...
... ...
References
GSM parameter U_RXLEV_UL_P

5-810 68P02901W23-Q
Technical Description: BSS Command Reference u_rxqual_dl_p
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.
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.
Dependencies alt_qual_procSince better rxqual corresponds to a lower bit error
rate, u_rxqual_dl_p should be less than l_rxqual_dl_p.
Syntax

chg_element u_rxqual_dl_p <value> <location> <cell_desc>
chg_cell_element u_rxqual_dl_p <value> <cell_desc>

disp_element u_rxqual_dl_p <location> <cell_desc>
68P02901W23-Q 5-811
u_rxqual_dl_p Chapter 5: CM database parameters
Values
Value type Integer

Valid range 0 to 1810 BER If alt_qual_proc = 0
(1 step = 0.01% bit error rate)
Default value 28 BER If alt_qual_proc = 0
1 QBand units If alt_qual_proc = 1
References
GSM parameter U_RXQUAL_DL_P

5-812 68P02901W23-Q
Technical Description: BSS Command Reference u_rxqual_dl_p_hr
u_rxqual_dl_p_hr
Description
The {22064}u_rxqual_dl_p_hr parameter specifies the power control threshold for the
best allowed downlink received quality (rxqual).
be unrestricted.
capable BTS site.
Syntax

{22064}
chg_element u_rxqual_dl_p_hr <value> <location> <cell_desc>
chg_cell_element u_rxqual_dl_p_hr <value> <cell_desc>

{22064}
disp_element u_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
68P02901W23-Q 5-813
u_rxqual_dl_p_hr Chapter 5: CM database parameters
Default value 14 BER. If alt_qual_proc = 0

0 QBand units. If alt_qual_proc = 1
5-814 68P02901W23-Q
Technical Description: BSS Command Reference u_rxqual_ul_p
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.
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.
Dependencies alt_qual_procSince better rxqual corresponds to a lower bit error
rate, u_rxqual_ul_p must be less than l_rxqual_ul_p.
Syntax

chg_element u_rxqual_ul_p <value> <location> <cell_desc>
chg_cell_element u_rxqual_ul_p <value> <cell_desc>

disp_element u_rxqual_ul_p <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 1810 BER If alt_qual_proc = 0
(1 step = 0.01% bit error rate)
68P02901W23-Q 5-815
u_rxqual_ul_p Chapter 5: CM database parameters

Default value 28 BER If alt_qual_proc = 0
1 QBand units If alt_qual_proc = 1
References
GSM parameter U_RXQUAL_UL_P

5-816 68P02901W23-Q
Technical Description: BSS Command Reference u_rxqual_ul_p_hr
u_rxqual_ul_p_hr
Description
The {22064}u_rxqual_ul_p_hr parameter specifies the power control threshold for the
best allowed uplink received quality (rxqual).
be unrestricted.
capable BTS site.
Syntax

{22064}
chg_element u_rxqual_ul_p_hr <value> <location> <cell_desc>
chg_cell_element u_rxqual_ul_p_hr <value> <cell_desc>

{22064}
disp_element u_rxqual_ul_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
68P02901W23-Q 5-817
u_rxqual_ul_p_hr Chapter 5: CM database parameters
Default value 14 BER. If alt_qual_proc = 0

0 QBand units. If alt_qual_proc = 1
5-818 68P02901W23-Q
Technical Description: BSS Command Reference ul_audio_lev_offset
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.
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.
Syntax

chg_element ul_audio_lev_offset <value> 0

disp_element ul_audio_lev_offset 0
Values

Default value 0
68P02901W23-Q 5-819
ul_rxlev_ho_allowed Chapter 5: CM database parameters
ul_rxlev_ho_allowed
Description
The ul_rxlev_ho_allowed parameter enables or disables handovers due to uplink receive level (rxlev).
Dependencies None
Syntax

chg_element ul_rxlev_ho_allowed <value> <location> <cell_desc>
chg_cell_element ul_rxlev_ho_allowed <value> <cell_desc>

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
5-820 68P02901W23-Q
Technical Description: BSS Command Reference ul_rxlev_ho_allowed
References
Internal name EN_RXLEV_HO

68P02901W23-Q 5-821
ul_rxqual_ho_allowed Chapter 5: CM database parameters
ul_rxqual_ho_allowed
Description
The ul_rxqual_ho_allowed parameter enables or disables handovers due to the uplink receive quality (rxqual).
Dependencies None
Syntax

chg_element ul_rxqual_ho_allowed <value> <location> <cell_desc>
chg_cell_element ul_rxqual_ho_allowed <value> <cell_desc>

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
5-822 68P02901W23-Q
Technical Description: BSS Command Reference ul_rxqual_ho_allowed
References
Internal name EN_RXQUAL_HO

68P02901W23-Q 5-823
unequipped_circuit_allowed Chapter 5: 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.
The Phase 2 feature must be unrestricted.
Syntax

chg_element unequipped_circuit_allowed <value> 0

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
5-824 68P02901W23-Q
Technical Description: BSS Command Reference unequipped_circuit_allowed
References

68P02901W23-Q 5-825
use_derived_ho_power Chapter 5: CM database parameters
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 disabled, 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.
Dependencies None
Syntax

chg_element use_derived_ho_power <value> <location> <cell_desc>
chg_cell_element use_derived_ho_power <value> <cell_desc>

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
5-826 68P02901W23-Q
Technical Description: BSS Command Reference use_neighbor_pbgt_hreqave
use_neighbor_pbgt_hreqave
Description
The use_neighbor_pbgt_hreqave parameter indicates whether the per cell or per neighbour
hreqave is used for the pbgt>ho_margin trigger assignment.
Dependencies None
Syntax

chg_element use_neighbor_pbgt_hreqave <value> <location> <cell_desc>
chg_cell_element use_neighbor_pbgt_hreqave <value> <cell_desc>

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 neighbour hreqave is used
Default value 0
68P02901W23-Q 5-827
volume_control_type Chapter 5: CM database parameters
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).
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.
Operator actions It is the responsibility of the network operator to synchronise the
values of
volume_control_type between the RXCDR and the BSC for the
desired control.
Syntax

chg_element volume_control_type <value> 0

disp_element volume_control_type 0
5-828 68P02901W23-Q
Technical Description: BSS Command Reference volume_control_type
The bss_id parameter is required in both the above 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
68P02901W23-Q 5-829
wait_for_reselection Chapter 5: CM database parameters
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.
Dependencies None
Syntax

chg_element wait_for_reselection <value> <location>

disp_element wait_for_reselection <location> <location>
Values

Default value 10
5-830 68P02901W23-Q
Technical Description: BSS Command Reference wait_indication_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.
Dependencies None
Syntax

chg_element wait_indication_parameters <value> <location> <cell_desc>
chg_cell_element wait_indication_parameters <value> <cell_desc>

disp_element wait_indication_parameters <location> <cell_desc>
Values

Default value 5
68P02901W23-Q 5-831
wait_indication_parameters Chapter 5: CM database parameters
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
5-832 68P02901W23-Q
Technical Description: BSS Command Reference worse_neighbor_ho
worse_neighbor_ho
Description
The worse_neighbor_ho parameter specifies whether or not 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.
Dependencies None
Syntax

chg_element worse_neighbor_ho <value> <location> <cell_desc>
chg_cell_element worse_neighbor_ho <value> <cell_desc>

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
68P02901W23-Q 5-833
zone_ho_hyst Chapter 5: CM database parameters
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_INNER)).
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

chg_element zone_ho_hyst <value> <location> <cell_desc>
chg_cell_element <location> zone_ho_hyst <value> <cell_desc>

disp_element zone_ho_hyst <location> <cell_desc>
5-834 68P02901W23-Q
Technical Description: BSS Command Reference zone_ho_hyst
Values
Value type Integer

Valid range 0 to 30 (Not Dual Band Cell)
-63 to 63 (Dual Band Cell)
Default value 0
68P02901W23-Q 5-835
zone_pingpong_count Chapter 5: CM database parameters
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_ping-
pong_enable_win parameter (see "zone_pingpong_enable_win" on page 6-218).
This parameter can be changed when the user is in RAM or Sysgen mode.
This parameter can only be modified at the BSC.
Dependencies None
Syntax

chg_element zone_pingpong_count <value> 0

disp_element zone_pingpong_count 0
Values
Value type Integer (insteps of 1)

Default value 3
5-836 68P02901W23-Q
Technical Description: BSS Command Reference zone_pingpong_preferred_zone
zone_pingpong_preferred_zone
Description
The zone_pingpong_preferred_zone parameter indicates which zone is preferred as a hop target zone.
Dependencies None
Syntax

chg_element zone_pingpong_preferred_zone <value> 0

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
68P02901W23-Q 5-837
zone_pingpong_preferred_zone Chapter 5: CM database parameters
5-838 68P02901W23-Q
Chapter
6
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 syntaax 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 where applicable.
For more information about BSS timers, refer to the Maintenance Information: BSS
Timers (68P02901W58) manual.
68P02901W23-Q 6-1
add_access_class Chapter 6: 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.
Dependencies None
Syntax

chg_element add_access_class <value> <location>

disp_element add_access_class <location>
Values

Default value 60000
References
Internal name MTCRM_ADD_ACC_CLASS

This is a Motorola defined timer.
6-2 68P02901W23-Q
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_t11 timer controls how long a call remains queued when waiting for a resource. In all
cases, the bssmap_t11 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.
Dependencies None
Syntax

chg_element assign_successful <value> <location>

disp_element assign_successful <location>
Values

Default value 30000
68P02901W23-Q 6-3
assign_successful Chapter 6: Timer parameters
References
Internal name SSM_MTN

This is a Mororola defined timer.
6-4 68P02901W23-Q
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.
Syntax

chg_element auto_dl_dur <value> <location>

disp_element auto_dl_dur <location>
Values
Value type Integer (20 ms block periods)

Default value 50
68P02901W23-Q 6-5
bcch_info Chapter 6: 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.
Dependencies None
Syntax

chg_element bcch_info <value> <location>

disp_element bcch_info <location>
Values

Default value 2000
6-6 68P02901W23-Q
Technical Description: BSS Command Reference bcch_info
References
Internal name TM_BCCH_INFO

GSM specification TS GSM 04.08 - section 9.1.34
.
This is a Motorola defined timer
68P02901W23-Q 6-7
bep_period Chapter 6: Timer parameters
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.
A BSS software process is notified whenever the bep_period element value is changed.
Syntax

chg_element bep_period <value> <location> <cell_desc>
chg_cell_element bep_period <value> <cel_desc>

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.
6-8 68P02901W23-Q
Technical Description: BSS Command Reference bep_period2
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. This parameter, if sent, is used by the mobile station in the cell, until a new bep_period2 is received
by the mobile station in the same cell, or the mobile station leaves the cell or the MS enters packet idle mode.
Syntax

chg_element bep_period2 <value> <location> <cell_desc>
chg_cell_element bep_period2 <value> <cel_desc>

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
68P02901W23-Q 6-9
bounce_protect_cong_tmr Chapter 6: Timer parameters
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.
Dependencies None
Syntax

chg_element bounce_protect_cong_tmr <value>
<location> <cell_desc>chg_cell_element
bounce_protect_cong_tmr <value> <cell_desc>

disp_element bounce_protect_cong_tmr <location> <cell_desc>
Values

0 Disabled
1 to 255 SACCH periods
Default value 0
6-10 68P02901W23-Q
Technical Description: BSS Command Reference bounce_protect_qual_tmr
bounce_protect_qual_tmr
Description
The bounce_protect_qual_tmr timer specifies the number of SACCH periods after a RXQUAL
handover the system applies the bounce_protect_margin value.
This timer helps to prevent continuous handover bouncing between cells due to RXQUAL reasons.
Dependencies None
Syntax

chg_element bounce_protect_qual_tmr <value> <location> <cell_desc>
chg_cell_element bounce_protect_qual_tmr <value> <cell_desc>

disp_element bounce_protect_qual_tmr <location> <cell_desc>
Values
Value type Integer (representing SACCH periods)

0 disabled
1 to 127 SACCH periods
Default value 0
68P02901W23-Q 6-11
bsc_audit Chapter 6: Timer parameters
bsc_audit
Description
The bsc_audit timer specifies how long 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.
Dependencies Must be greater than bts_audit
Syntax

chg_element bsc_audit <value> <location>

disp_element bsc_audit <location>
Values

Default value 120000
References
Internal name SSM_MTV

6-12 68P02901W23-Q
Technical Description: BSS Command Reference bsc_audit_response
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.
Dependencies None
Syntax

chg_element bsc_audit_response <value> <location>

disp_element bsc_audit_response <location>
Values

Default value 30000
References
Internal name SSMAUDIT_TIMER

68P02901W23-Q 6-13
bss_overload_control Chapter 6: Timer parameters
bss_overload_control
{24660, 24661}
Description
The bss_overload_control parameter is a RSL Congestion Control (RCC) timer which

defines the BSS Overload message interval
It is recommended that this timer is set less than or equal to bssmap_t7 at the MSC.
Dependencies None
Syntax

chg_element bss_overload_control <value> bsc

disp_element bss_overload_control bsc
Values

Default value 12500
6-14 68P02901W23-Q
Technical Description: BSS Command Reference bssgp_fc_period_c
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.
Syntax

chg_element bssgp_fc_period_c <value> <location>

disp_element bssgp_fc_period_c <location>
68P02901W23-Q 6-15
bssgp_fc_period_c Chapter 6: Timer parameters
Values
Value type Integer (tenths of a second)


10 1 second 1000 milliseconds
Default value 10 (1 second)
References
GSM specification TS GSM 08.18 - Section 8.2.3.4

6-16 68P02901W23-Q
Technical Description: BSS Command Reference bssgp_t1_timer
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 BVC-BLOCK or BVC-UNBLOCK-ACK PDU is received by the BSS from the SGSN. If the
timer expires before an ACK is received, the BVC Blocking or Unblocking procedure is repeated a maximum
number of bssgp_block_retries attempts. After the maximum attempts fail, the BVC remains unblocked.
Syntax

chg_element bssgp_t1_timer <value> <location>

disp_element bssgp_t1_timer <location>
Values

Default value 3
68P02901W23-Q 6-17
bssgp_t1_timer Chapter 6: Timer parameters
References
Internal name BSSGP T1

GSM specification TS GSM 08.18 - Section 8.3
6-18 68P02901W23-Q
Technical Description: BSS Command Reference bssgp_t2_timer
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
BVC-RESET-ACK is received by the BSS 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.
Syntax

chg_element bssgp_t2_timer <value> <location>

disp_element bssgp_t2_timer <location>
Values

Default value 60
68P02901W23-Q 6-19
bssgp_t2_timer Chapter 6: Timer parameters
References
GSM specification TS GSM 08.18 - Section 8.4

6-20 68P02901W23-Q
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.
Dependencies None
Syntax

chg_element bssmap_t1 <value> <location>

disp_element bssmap_t1 <location>
Values

Default value 30000
References
Internal name CLM_T1

GSM name T1
8.08 - 3.2.3: BSSMAP timers
68P02901W23-Q 6-21
bssmap_t10 Chapter 6: 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
and 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.
Dependencies None
Syntax


Values

Default value 28000
6-22 68P02901W23-Q
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-Q 6-23
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.
Dependencies Should be less than assign_successful
Syntax


Values

Default value 28000
6-24 68P02901W23-Q
References

GSM name T11
8.08 - 3.2.3: all RRSM timers
68P02901W23-Q 6-25
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.
This timer must be set 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 Acknowledgement.
Dependencies None
Syntax


Values

Default value 40000
6-26 68P02901W23-Q
References

GSM parameter T13
GSM specification 8.08 - 3.2.3: BSSMAP timers
68P02901W23-Q 6-27
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.
Dependencies None
Syntax


Values

Default value 30000
References

GSM name T19
6-28 68P02901W23-Q
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.
Dependencies None
Syntax


Values

Default value 30000
References

GSM name T20
68P02901W23-Q 6-29
bssmap_t4
Description
The bssmap_t4 timer specifies the wait time for return of the Reset Acknowledgement from
MSC. This timer must be set 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.
Dependencies None
Syntax


Values

Default value 50000
6-30 68P02901W23-Q
References

GSM name T4
GSM specification 8.08 - 3.2.3: BSSMAP timers
8.08 - 3.1.4.1.3.1: T4
68P02901W23-Q 6-31
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).
Dependencies None
Syntax


Values

Default value 30000
6-32 68P02901W23-Q
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-Q 6-33
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.
Dependencies None
Syntax


Values

Default value 28000
6-34 68P02901W23-Q
References

GSM name T8
GSM specification 12.20 - 5.2.7.2 bss Map Timer In Bsc - bss Map T8: 4.08 - Section 11
68P02901W23-Q 6-35
bssmap_tqho Chapter 6: 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.
Dependencies None
Syntax

chg_element bssmap_tqho <value> <location>

disp_element bssmap_tqho <location>
Values

Default value 30000
6-36 68P02901W23-Q
Technical Description: BSS Command Reference bssmap_tqho
References
Internal name SSM_TQHO

GSM name T_qho
GSM technical specification GSM 8.008
68P02901W23-Q 6-37
bts_audit Chapter 6: Timer parameters
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.
Dependencies This parameter must be less than bsc_audit.
Syntax

chg_element bts_audit <value> <location>

disp_element bts_audit <location>
Values

Default value The lesser value of 60000 or the bsc_audit timer minus 1
6-38 68P02901W23-Q
Technical Description: BSS Command Reference bts_audit
References
Internal name RRSM_MTW

68P02901W23-Q 6-39
bts_audit_response Chapter 6: 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).
Dependencies None
Syntax

chg_element bts_audit_response <value> <location>

disp_element bts_audit_response <location>
Values

Default value 30000
References
Internal name RRSM_AUDIT_TIMER

8.08 - 3.1
6-40 68P02901W23-Q
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.
Dependencies The parameter is only valid for a remote BTS site.
Syntax

chg_element bts_escalation <value> <location>

disp_element bts_escalation <location>
Values

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-Q 6-41
carrier_free_immediate Chapter 6: 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 needed 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.
Dependencies None
Syntax

chg_element carrier_free_immediate <value> <location>

disp_element carrier_free_immediate <location>
Values

6-42 68P02901W23-Q
Technical Description: BSS Command Reference carrier_free_immediate
References
Internal name MTCRM_CARRIER_FREE_IMMEDIATE

68P02901W23-Q 6-43
cbch_1 Chapter 6: Timer parameters
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.
Dependencies None
Syntax

chg_element cbch_1 <value> <location>

disp_element cbch_1 <location>
Values

Default value 30000
References
Internal name MTCRM_CBT1

6-44 68P02901W23-Q
Technical Description: BSS Command Reference cbch_2
cbch_2
Description
The cbch_2 timer specifies the wait time for updating the CBCH response from RSS.
Dependencies None
Syntax


Values

Default value 30000
References

68P02901W23-Q 6-45
cbch_3 Chapter 6: Timer parameters
cbch_3
Description
The cbch_3 timer specifies the wait time for the CBCH activation acknowledgement from RCI.
Dependencies None
Syntax


Values

Default value 35000
References

6-46 68P02901W23-Q
Technical Description: BSS Command Reference channel_act
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 take out of service when it receives the
CHANNEL_ACTIVATION_ACK message from RSS.
Dependencies None
Syntax

chg_element channel_act <value> <location>

disp_element channel_act <location>
Values

Default value 10000
68P02901W23-Q 6-47
channel_act Chapter 6: Timer parameters
References
Internal name TM_CHANNEL_ACT

6-48 68P02901W23-Q
Technical Description: BSS Command Reference channel_teardown
channel_teardown
Description
The channel_teardown timer specifies the wait time for channel teardown.
Dependencies None
Syntax

chg_element channel_teardown <value> <location>

disp_element channel_teardown <location>
Values

Default value 28000
References
Internal name RRSM_MTQ

GSM technical specification 4.08 - Section 11
.
68P02901W23-Q 6-49
cipher_comp_ms Chapter 6: 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.
Dependencies The ciphering_successful parameter value must be greater than the
cipher_comp_ms parameter value.
Syntax

chg_element cipher_comp_ms <value> <location>

disp_element cipher_comp_ms <location>
6-50 68P02901W23-Q
Technical Description: BSS Command Reference cipher_comp_ms
Values

Default value 28000
References
Internal name RRSM_MTA

.
68P02901W23-Q 6-51
ciphering_successful Chapter 6: 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.
Dependencies The ciphering_successful parameter value must be greater than the
cipher_comp_ms parameter value.
Syntax

chg_element ciphering_successful <value> <location>

disp_element ciphering_successful <location>
6-52 68P02901W23-Q
Technical Description: BSS Command Reference ciphering_successful
Values

Default value 30000
References
Internal name SSM_MTI

68P02901W23-Q 6-53
circuit_reset_ack Chapter 6: Timer parameters
circuit_reset_ack
Description
The circuit_reset_ack timer specifies the wait time for the “circuit reset" acknowledgement from
internal subsystems. A typical value for this timer is 1000 milliseconds.
This is not a BSSAP timer.
Dependencies None
Syntax

chg_element circuit_reset_ack <value> <location>

disp_element circuit_reset_ack <location>
Values

Default value 70000
References
Internal name CLM_MTA1

6-54 68P02901W23-Q
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.
The clear_cmd_ext_ho timer must be set 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.
The clear_cmd_ext_ho timer must also be set 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).
Dependencies This timer is valid only for the BSC.
Syntax

chg_element clear_cmd_ext_ho <value> 0

disp_element clear_cmd_ext_ho 0
Values

Default value 30000
68P02901W23-Q 6-55
clear_command Chapter 6: 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.
Dependencies None
Syntax

chg_element clear_command <value> <location>

disp_element clear_command <location>
Values

Default value 30000
6-56 68P02901W23-Q
Technical Description: BSS Command Reference clear_command
References
Internal name SSM_MTG

68P02901W23-Q 6-57
dealloc_inact Chapter 6: Timer parameters
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.
Dependencies None
Syntax

chg_element dealloc_inact <value> <location> <cell_desc>
chg_cell_element dealloc_inact <value> <cell_desc>

disp_element dealloc_inact <location> <cell_desc>
Values

Default value None
6-58 68P02901W23-Q
Technical Description: BSS Command Reference dealloc_inact
References
Internal name MTCRM_DEALLOC_INACT

68P02901W23-Q 6-59
delay_dl_rel_dur Chapter 6: Timer parameters
delay_dl_rel_dur
Description
The delayed downlink 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.
Supported by OMC-R GUI Yes (Read-Write)
Syntax

chg_element delay_dl_rel_dur <value> <location>

disp_element delay_dl_rel_dur <location>
Values
Value type Integer (20ms block periods)

15 Min
600 Max
Default value 50
6-60 68P02901W23-Q
Technical Description: BSS Command Reference downlink_sync_timer
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.
Dependencies This parameter is not allowed at a stand-alone BSC or a stand-alone
RXCDR. It can be used at a BTS.
Syntax

chg_element downlink_sync_timer <value> <location>
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, these alarms are blocked by the system.

disp_element downlink_sync_timer <location>
68P02901W23-Q 6-61
downlink_sync_timer Chapter 6: Timer parameters
Values

Default value 1000
6-62 68P02901W23-Q
Technical Description: BSS Command Reference dynet_retry_time
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 introduce 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.
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

chg_element dynet_retry_time <value> <location> <cell_desc>

disp_element dynet_retry_time <location> <cell_desc>
68P02901W23-Q 6-63
dynet_retry_time Chapter 6: Timer parameters
Values

Default value 150
6-64 68P02901W23-Q
Technical Description: BSS Command Reference early_classmark_delay
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.
This parameter can only be viewed at the BSC.
Syntax

chg_element early_classmark_delay <value> 0

disp_element early_classmark_delay 0
Values

Default value 0
References
GSM specification GSM TS 8.08 Section 3.1.13.

.
This is a Motorola defined parameter
68P02901W23-Q 6-65
emerg_reserved Chapter 6: Timer parameters
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.
Dependencies None
Syntax

chg_element emerg_reserved <value> <location>

disp_element emerg_reserved <location>
Values

6-66 68P02901W23-Q
Technical Description: BSS Command Reference emerg_reserved
References
Internal name MTCRM_EMERG_RESERVED

68P02901W23-Q 6-67
ext_ho_allocation Chapter 6: 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.
Dependencies None
Syntax

chg_element ext_ho_allocation <value> <location>

disp_element ext_ho_allocation <location>
Values

Default value 30000
References
Internal name SSM_MTC1

6-68 68P02901W23-Q
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.
Dependencies The Congestion Relief feature must be enabled.
The inter_cell_handover_allowed parameter must be enabled for
ECR functionality to work properly.
Syntax

chg_element ext_rtry_cand_prd <value> <location> <cell_desc>
chg_cell_element ext_rtry_cand_prd <value> <cell_desc>

disp_element ext_rtry_cand_prd <location> <cell_desc>
Values

Default value 4000
68P02901W23-Q 6-69
flow_control_t1 Chapter 6: Timer parameters
flow_control_t1
Description
The flow_control_t1 timer specifies the wait time before the Flow Control mechanism
considers new overload messages.
Dependencies The flow_control_t1 value must be at least 1000 milliseconds less
than the flow_control_t2 value.
Syntax

chg_element flow_control_t1 <value> <location> <cell_desc>
chg_cell_element flow_control_t1 <value> <cell_desc>

disp_element flow_control_t1 <location> <cell_desc>
Values

Default value 20000
6-70 68P02901W23-Q
Technical Description: BSS Command Reference flow_control_t1
References
Internal name MTCRM_FC_T1

GSM name FC_T1
68P02901W23-Q 6-71
flow_control_t2 Chapter 6: Timer parameters
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.
Dependencies The flow_control_t1 value must be at least 1000 milliseconds less
than the flow_control_t2 value.
Syntax

chg_element flow_control_t2 <value> <location> <cell_desc>
chg_cell_element flow_control_t2 <value> <cell_desc>

disp_element flow_control_t2 <location> <cell_desc>
Values

Default value 30000
6-72 68P02901W23-Q
Technical Description: BSS Command Reference flow_control_t2
References
Internal name MTCRM_FC_T2

GSM name FC_T2
68P02901W23-Q 6-73
gbl_thrput_period Chapter 6: 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.
Syntax

chg_element gbl_thrput_period <value> PCU

disp_element gbl_thrput_period PCU
Values
Value type Integer (tenths of a second)

Default value 50
6-74 68P02901W23-Q
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.
Dependencies The PBCCH/PCCH feature must be unrestricted.
Syntax

chg_cell_element gprs_penalty_time <value> <location> <cell_desc>
chg_element gprs_penalty_time <value> <cell_desc>

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
68P02901W23-Q 6-75
gprs_penalty_time Chapter 6: Timer parameters
31 320 seconds
Default value 0 10 seconds
6-76 68P02901W23-Q
Technical Description: BSS Command Reference gprs_smg30_t3192
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.
If the parameter smg_gb_vers is less than or equal to 30, then it is
used. Otherwise, gprs_t3192 is used.
Syntax

chg_element gprs_smg30_t3192 <value> <location> <cell_desc>
chg_cell_element gprs_smg30_t3192 <value> <cell_desc>

disp_cell_element gprs_smg30_t3192 <cell_desc>
Values
Value type Select integer (milliseconds)

Valid range 500, 1000, 2000, and 4000
Default value 500
68P02901W23-Q 6-77
gprs_t3168 Chapter 6: Timer parameters
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.
Syntax

chg_element gprs_t3168 <value> <location> <cell_desc>
chg_cell_element gprs_t3168 <value> <cell_desc>

disp_element gprs_t3168 <location> <cell_desc>
Values

Valid range 500, 1000, 2000, and 4000
Default value 4000
6-78 68P02901W23-Q
Technical Description: BSS Command Reference gprs_t3192
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.
Syntax

chg_element gprs_t3192 <value> <location> cell_desc>
chg_cell_element gprs_t3192 <value> <cell_desc>

disp_element gprs_t3192 <location> <cell_desc>
Values

Valid range 0, 80, 120, 160, 200, 500, 1000, and 1500
Default value 500
68P02901W23-Q 6-79
handover_recognized_period Chapter 6: Timer parameters
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 queueing 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, call queuing must be enabled 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.
Dependencies Call queueing must be enabled.
MSC h_interval < handover_recognized_period
Syntax

add_cell <gsm_cell_desc> <location>
chg_element handover_recognized_period <value> <location> <cell_desc>
chg_cell_element handover_recognized_period <value> <cell_desc>

disp_element handover_recognized_period <location> <cell_desc>
6-80 68P02901W23-Q
Technical Description: BSS Command Reference handover_recognized_period
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.
68P02901W23-Q 6-81
ho_ack Chapter 6: Timer parameters
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.
Dependencies None
Syntax

chg_element ho_ack <value> <location> <cell_desc>
chg_cell_element ho_ack <value> <cell_desc>

disp_element ho_ack <location> <cell_desc>
Values

Default value 5000
6-82 68P02901W23-Q
Technical Description: BSS Command Reference ho_ack
References
Internal name MTCRM_HANDOVER_ACK

68P02901W23-Q 6-83
ho_allocation Chapter 6: 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 when the BSC requests a resource from the BTS
to perform an intra-BSS handover.
If this timer expires, the handover terminates.
Dependencies None
Syntax

chg_element ho_allocation <value> <location>

disp_element ho_allocation <location>
Values

Default value 30000
References
Internal name SSM_MTK

6-84 68P02901W23-Q
Technical Description: BSS Command Reference ho_complete
ho_complete
Description
The ho_complete timer specifies the wait time for handover complete from a 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.
Dependencies None
Syntax

chg_element ho_complete <value> <location>

disp_element ho_complete <location>
Values

Default value 28000
68P02901W23-Q 6-85
ho_complete Chapter 6: Timer parameters
References
Internal name RRSM_MTD

6-86 68P02901W23-Q
Technical Description: BSS Command Reference ho_request
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.
Dependencies None
Syntax

chg_element ho_request <value> <location>

disp_element ho_request <location>
Values

Default value 30000
References
Internal name SSM_MTB1

68P02901W23-Q 6-87
ho_successful Chapter 6: Timer parameters
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.
Dependencies None
Syntax

chg_element ho_successful <value> <location>

disp_element ho_successful <location>
Values

Default value 30000
References
Internal name SSM_MTJ

6-88 68P02901W23-Q
Technical Description: BSS Command Reference hop_count_timer
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 amr_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 a RXQUAL handover
to another cell. If the number of quality/interference handovers from Half Rate (HR) to Full Rate (FR) defined
by the amr_hop_count parameter occur within the time set by hop_count_timer, the system will keep the
mobile on the FR channel if it is a candidate for FR to HR reconfiguration due to congestion.
Dependencies None
Syntax

chg_element hop_count_timer <value> <cell_desc>
chg_cell_element hop_count_timer <value> <cell_desc>

disp_element hop_count_timer <cell_desc>
Values

Valid range 0 to 255 A value of 0 disables this feature.
Default value 0
68P02901W23-Q 6-89
initial_sync_timer Chapter 6: Timer parameters
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.
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.
A site reset occurs when the value of initial_sync_timer is changed in SYSGEN OFF mode.
Resetting the site generates several alarms. However, these alarms are blocked by the system.
Syntax

chg_element initial_sync_timer <value> <location>

disp_element initial_sync_timer <location>
6-90 68P02901W23-Q
Technical Description: BSS Command Reference initial_sync_timer
Values
Value type Integer (1 step = 1 millisecond)

Default value 4000 (4 seconds)
68P02901W23-Q 6-91
lb_int_bssmap_t13 Chapter 6: 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.
Syntax

chg_element lb_int_bssmap_t13 <value> <location>

disp_element lb_int_bssmap_t13 <location>
Values

Default value 40000
References
GSM specification GSM 8.08-3.2.3
6-92 68P02901W23-Q
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.
Syntax

chg_element lb_int_bssmap_t4 <value> <location>

disp_element lb_int_bssmap_t4 <location>
Values

Default value 50000
68P02901W23-Q 6-93
lb_int_clear_command Chapter 6: Timer parameters
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.
Syntax

chg_element lb_int_clear_command <value> <location>

disp_element lb_int_clear_command <location>
Values

Default value 30000
6-94 68P02901W23-Q
Technical Description: BSS Command Reference lb_int_sccp_released
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.
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)

Default value 30000
68P02901W23-Q 6-95
lb_int_sccp_tconn_est Chapter 6: Timer parameters
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.
Syntax

chg_element lb_int_sccp_tconn_est <value> <location>

disp_element lb_int_sccp_tconn_est <location>
Values

Default value 30000
6-96 68P02901W23-Q
Technical Description: BSS Command Reference lb_int_sccp_tiar
lb_int_sccp_tiar
Description
The lb_int_sccp_tiar timer is the receive inactivity control timer for the Lb-interface.
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

chg_element lb_int_sccp_tiar <value> <location>

disp_element lb_int_sccp_tiar <location>
Values

Default value 30000
References
GSM specification GSM 8.08-3.23
68P02901W23-Q 6-97
lb_int_sccp_tias Chapter 6: Timer parameters
lb_int_sccp_tias
Description
The lb_int_sccp_tias timer is the send activity control timer for the Lb-interface.
The value of this parameter should be less than the lb_int_sccp_tiar
parameter value.
Syntax

chg_element lb_int_sccp_tias <value> <location>

disp_element lb_int_sccp_tias <location>
Values

Default value 30000
References
GSM specification GSM 8.08-3.23
6-98 68P02901W23-Q
Technical Description: BSS Command Reference lb_int_sccp_trel
lb_int_sccp_trel
Description
The lb_int_sccp_trel timer is the wait for SCCP release complete timer for the Lb-interface.
Syntax

chg_element lb_int_sccp_trel <value> <location>

disp_element lb_int_sccp_trel <location>
Values

Default value 10000
References
GSM specification This is a Motorola defined timer.
68P02901W23-Q 6-99
lb_int_spi Chapter 6: Timer parameters
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.
Syntax

chg_element lb_int_spi <value> <location>

disp_element lb_int_spi <location>
Values

Default value 60000
References
GSM specification GSM 8.08 - 3.1.15

6-100 68P02901W23-Q
Technical Description: BSS Command Reference lb_int_ss7_l2_t1
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.
The valid ranges for this element are dependent upon the value of
the ss7_mode.
Syntax

chg_element lb_int_ss7_l2_t1 <value> <location>

disp_element lb_int_ss7_l2_t1 <location>
Values

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
68P02901W23-Q 6-101
lb_int_ss7_l2_t2 Chapter 6: Timer parameters
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.
the ss7_mode.
Syntax


Values

ss7_mode = 1: 5000 to 30000
ss7_mode =1: 23000
References
6-102 68P02901W23-Q
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.
the ss7_mode.
Syntax


Values

ss7_mode = 1: 5000 to 14000
ss7_mode =1: 11500
References
68P02901W23-Q 6-103
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.
Syntax


Values

Default value 600
References
6-104 68P02901W23-Q
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.
Syntax


Values

Default value 100
References
68P02901W23-Q 6-105
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.
the ss7_mode.
Syntax


Values

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
6-106 68P02901W23-Q
lb_int_ss7_l2_t7
Description
The lb_int_ss7_l2_t7 (Lb-interface MTP layer 2 T7) timer is the excessive delay of
acknowledgement timer associated with the Lb-interface.
the ss7_mode.
Syntax


Values

Default value 1000
References
68P02901W23-Q 6-107
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.
Syntax


Values

Default value 850
References
6-108 68P02901W23-Q
lb_int_ss7_l3_t12
Description
The lb_int_ss7_l3_t12 (Lb-interface MTP layer 3 T12) timer is the waiting for uninhibit
Syntax


Values

Default value 1150
References
68P02901W23-Q 6-109
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.
Syntax


Values

Default value 1150
References
6-110 68P02901W23-Q
lb_int_ss7_l3_t14
Description
The lb_int_ss7_l3_t14 (Lb-interface MTP layer 3 T14) timer is the waiting for inhibition
Syntax


Values

Default value 2500
References
68P02901W23-Q 6-111
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.
Syntax


Values

Default value 1150
References
6-112 68P02901W23-Q
lb_int_ss7_l3_t2
Description
The lb_int_ss7_l3_t2 (Lb-interface MTP layer 3 T2) timer is the waiting for changeover
Syntax


Values

Default value 1400
References
68P02901W23-Q 6-113
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.
The ss7_mode dependent parameters are set to the appropriate
defaults when the ss7_mode is changed.
Syntax


Values

ss7_mode = 1: 90000 to 120000
ss7_mode =1: 90000
6-114 68P02901W23-Q
The ss7_mode dependent parameters are set to the appropriate defaults

when the ss7_mode is changed.
References
68P02901W23-Q 6-115
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.
This parameter is automatically changed to the appropriate default
value if the ss7_mode element is changed.
Syntax


Values

ss7_mode = 1: 90000 to 120000
ss7_mode =1: 90000
6-116 68P02901W23-Q
References
68P02901W23-Q 6-117
lb_int_ss7_l3_t4
Description
The lb_int_ss7_l3_t4 (Lb-interface MTP layer 3 T4) timer is the waiting for changeback
acknowledgement (first attempt) timer associated with the Lb-interface.
Syntax


Values

Default value 850
References
6-118 68P02901W23-Q
lb_int_ss7_l3_t5
Description
The lb_int_ss7_l3_t5 (Lb-interface MTP layer 3 T5) timer is the waiting for changeback
acknowledgement (second attempt) timer associated with the Lb-interface.
Syntax


Values

Default value 850
References
68P02901W23-Q 6-119
lb_int_ss7_slt_t1 Chapter 6: Timer parameters
lb_int_ss7_slt_t1
Description
The lb_int_ss7_slt_t1 (Lb-interface SS7 Signalling Link Test (SLT) T1) timer is the supervision timer
for signalling link test acknowledgement message timer associated with the Lb-interface.
Syntax

chg_element lb_int_ss7_slt_t1 <value> <location>

disp_element lb_int_ss7_slt_t1 <location>
Values

Default value 8000
References
6-120 68P02901W23-Q
Technical Description: BSS Command Reference lb_int_t_stat_info
lb_int_t_stat_info
Description
The lb_int_t_stat_info timer specifies the amount of time between sending Subsystem
Status Test (SST) messages to the BSS-based SMLC.
Syntax

chg_element lb_int_t_stat_info <value> <location>

disp_element lb_int_t_stat_info <location>
Values

Default value 90000
68P02901W23-Q 6-121
lcs_perf_location Chapter 6: Timer parameters
lcs_perf_location
Description
The lcs_perf_location timer guards the receipt of a BSSMAP-LE perform location

response from a BSS-based SMLC.
Syntax

chg_element lcs_perf_location <value> <location>

disp_element lcs_perf_location <location>
Values

6-122 68P02901W23-Q
Technical Description: BSS Command Reference lcs_segmentation
lcs_segmentation
Description
The lcs_segmentation timer is used for supervising a Location Services segmentation operation.
The value of this parameter should be less than the value of the
lcs_supervision timer.
Syntax

chg_element lcs_segmentation <value> <location>

disp_element lcs_segmentation <location>
Values

Default value 10000
68P02901W23-Q 6-123
lcs_supervision Chapter 6: Timer parameters
lcs_supervision
Description
The lcs_supervision timer is used for supervising the overall operation of a location request.
The value of this parameter must be less than the value of the
lcs_perf_location timer.
Syntax

chg_element lcs_supervision <value> <location>

disp_element lcs_supervision <location>
Values

Default value 30000
6-124 68P02901W23-Q
Technical Description: BSS Command Reference mode_modify
mode_modify
Description
The mode_modify timer specifies the wait time for the MODE MODIFY message
to be sent from Abis to Physical Layer 1.
If this timer expires before the MODE MODIFY message arrives, the MODE MODIFY
ACKNOWLEDGE message is sent in response to Call Processing (CP) and RSS generates
a MODE_MODIFY_ACK message to CP.
Dependencies The value of the mode_modify_ack CP timer must be greater than
or equal to the RSS timers + 10 ms.
Syntax

chg_element mode_modify <value> <location>

disp_element mode_modify <location>
Values

Default value 10000
68P02901W23-Q 6-125
mode_modify Chapter 6: Timer parameters
References
Internal name TM_MODE_MODIFY

6-126 68P02901W23-Q
Technical Description: BSS Command Reference mode_rr_modify_ack
mode_rr_modify_ack
Description
The mode_rr_modify_ack timer specifies the wait time for the MODE MODIFY
ACKNOWLEDGE message from the MS.
This timer starts when the BTS receives confirmation on modification of the channel mode.
When this timer expires, the BTS aborts the mode modification.
Dependencies None
Syntax

chg_element mode_rr_modify_ack <value> <location>

disp_element mode_rr_modify_ack <location>
Values

Default value 28000
68P02901W23-Q 6-127
mode_rr_modify_ack Chapter 6: Timer parameters
References
Internal name RRSM_MTY

6-128 68P02901W23-Q
Technical Description: BSS Command Reference ms_sapi3_est
ms_sapi3_est
Description
The ms_sapi3_est timer specifies the wait time for SAPI 3 SMS establishment from the MS.
This is an internal timer dealing with SAPI3 connection procedures.
Dependencies None
Syntax

chg_element ms_sapi3_est <value> <location>

disp_element ms_sapi3_est <location>
Values

Default value 28000
68P02901W23-Q 6-129
ms_sapi3_est Chapter 6: Timer parameters
References
Internal name RRSM_MTE1

GSM specification 12.20 - 5.2.7.2 BSS Map Timer In BSC -
4.08 - Section 11
8.08 - 3.1 .
6-130 68P02901W23-Q
Technical Description: BSS Command Reference nc_non_drx_period
nc_non_drx_period
Description
The nc_non_drx_period parameter specifies the time interval that the BSS allows for the MS to read
the paging channel (CCCH) for a Packet Cell Change Order (PCCO) control message.
Syntax

chg_element nc_non_drx_period <value> <location>

disp_element nc_non_drx_period <location>
Values
Value type Integer

Valid range 0 to 7
0 No non_drx_period set
1 0.24 seconds
2 0.48 seconds
3 0.72 seconds
68P02901W23-Q 6-131
nc_non_drx_period Chapter 6: Timer parameters
4 0.96 seconds
5 1.20 seconds
6 1.44 seconds
7 1.96 seconds
Default value 2 (0.48 seconds)
6-132 68P02901W23-Q
Technical Description: BSS Command Reference nc_reporting_period_i
nc_reporting_period_i
Description
The nc_reporting_period_i parameter specifies the time interval between successive

measurement reports from a GPRS MS in idle mode.
Syntax

chg_element nc_reporting_period_i <value> <location>

disp_element nc_reporting_period_i <location>
Values
Value type Integer

Valid range 4 to 6
4 15.36 seconds
5 30.72 seconds
6 61.44 seconds
Default value 6
68P02901W23-Q 6-133
nc_reporting_period_t Chapter 6: Timer parameters
nc_reporting_period_t
Description
The nc_reporting_period_t parameter specifies the time interval between successive measurement
reports from a GPRS MS while transferring packet data.
Syntax

chg_element nc_reporting_period_t <value> <location>

disp_element nc_reporting_period_t <location>
Values
Value type Integer

Valid range 0 or 6
0 0.96 seconds
1 1.92 seconds
2 3.84 seconds
3 7.68 seconds
6-134 68P02901W23-Q
Technical Description: BSS Command Reference nc_reporting_period_t
4 15.36 seconds
5 30.72 seconds
6 61.44 seconds
Default value 2
68P02901W23-Q 6-135
neighbor_report_timer Chapter 6: Timer parameters
neighbor_report_timer
Description
The neighbor_report_timer specifies the wait time for the MS for a handover to decode the
BSIC and report on potentially interfering neighbours.
Dependencies The Concentric Cells feature must be unrestricted the
inner_zone_alg element must be set to 2.
Syntax

chg_element neighbor_report_timer <value> <location> <cell_desc>
chg_cell_element neighbor_report_timer <value> <cell_desc>

disp_element neighbor_report_timer <location> <cell_desc>
Values

Default value 10
6-136 68P02901W23-Q
Technical Description: BSS Command Reference ns_alive_timer
ns_alive_timer
Description
The ns_alive_timer guards the NS Test Procedure between the BSS and the SGSN.
This timer is set when the BSS sends an NS-ALIVE-ACK PDU to the SGSN. This timer is cleared when the
NS-ALIVE-ACK is received by the BSS from the SGSN. If the timer expires before teh ACK is received, the
NS Test Procedure is repeated a maximum of ns_alive_retries attempts. After the maximum number of
attempts fail, the NS Test Procedure is stopped and the NSVC is marked dead and blocked.
Syntax

chg_element ns_alive_timer <value> <location>

disp_element ns_alive_timer <location>
Values

Valid range 1 to 30
Default value 3
68P02901W23-Q 6-137
ns_block_timer Chapter 6: Timer parameters
ns_block_timer
Description
The ns_block_timer gurads the NS Blocking and Unblocking Procedures between the BSS and SGSN.
This timer is set when the BSS sends an NS-BLOCK or NS-UNBLOCK PDU to the SGSN. This timer is
cleared when the NS-BLOCK-ACK or NS-UNBLOCK-ACK PDU is received by the BSS from the SGSN.
If the timer expires before an ACK is received, the NS Blocking or Unblocking procedure is repeated a
maximum of ns_block_retries attempts. After the maximum attempts fail, the NSVC remains unblocked.
Syntax

chg_element ns_block_timer <value> <location>

disp_element ns_block_timer <location>
Values

Valid range 1 to 30
Default value 3
6-138 68P02901W23-Q
Technical Description: BSS Command Reference ns_reset_period
ns_reset_period
Description
The ns_reset_period timer specifies the period for which the BSS attempts to reset
an NSVC using the NS Reset Procedure.
This timer is set when the BSS initiates the NS Reset Procedure. If the NS-RESET-ACK is not returned
before ns_reset_timer expires, then the NS Reset Procedure is repeated for the ns_reset_period. If the NS
Reset Procedure is not successful before the ns_reseet_period expires, the NSVC remains unblocked.
Syntax

chg_element ns_reset_period <value> <location>

disp_element ns_reset_period <location>
Values

Default value 125
68P02901W23-Q 6-139
ns_reset_timer Chapter 6: Timer parameters
ns_reset_timer
Description
The ns_reset_timer guards the NS Reset Procedure between the BSS and the SGSN.
This timer is set when the BSS sends an NS-RESET to the SGSN. This timer is cleared when the
NS-RESET-ACK is received by the BSS from the SGSN. If the timer expires before the ACK is received,
the NS Reset Procedure is repeated until the ns_reset_period expires. If the NS Reset Procedure is
not successful before the ns_reset_period expires, the NSVC remains blocked.
Syntax

chg_element ns_reset_timer <value> <location>

disp_element ns_reset_timer <location>
Values

Default value 40
6-140 68P02901W23-Q
Technical Description: BSS Command Reference ns_test_timer
ns_test_timer
Description
The ns_test_timer specifies the periodicity for the NSVC Test Procedure. The NSVC
is tested every ns_test_timer seconds
This timer is set upon successful completion of the NS Test Procedure. Upon expiry of the timer,
the BSS initiates the NS Test Procedure. Upon successful completion of the NS Test Procedure, the
timer is started again. The procedure is repeated each time the timer expires.
Syntax

chg_element ns_test_timer <value> <location>

disp_element ns_test_timer <location>
Values

Valid range 1 to 60
Default value 30
68P02901W23-Q 6-141
pccch_drx_timer_max Chapter 6: Timer parameters
pccch_drx_timer_max
Description
The pccch_drx_timer_max timer specifies the duration of the transfer non-Discontinuous Reception
(DRX) mode period on the Packet Common Control Channel (PCCCH).
The value of this parameter is the binary representation of the standard parameter DRX_TIMER_MAX. It is
given as two taken to the power of the binary value minus one (2 (bv-1)) in units of one second.
Dependencies The PCCCH/PBCCH feature must be unrestricted.
Syntax

chg_element pccch_drx_timer_max <value> <location>
chg_cell_element pccch_drx_timer_max <value> <cell-desc>
chg_cell_element <location> pccch_drx_timer_max <value> all

disp_element pccch_drx_timer_max <location> <cell-desc>
disp_element pccch_drx_timer_max <location> all
6-142 68P02901W23-Q
Technical Description: BSS Command Reference pccch_drx_timer_max
Values
Value type Integer

Valid range 0 to 7
0 0 seconds
1 1 second
2 2 seconds
3 4 seconds
4 8 seconds
5 16 seconds
6 32 seconds
7 64 seconds
Default value 3 (4 seconds)
68P02901W23-Q 6-143
penalty_time Chapter 6: Timer parameters
penalty_time
Description
The penalty_time timer specifies how long the value specified by the field temporary_offset is valid.
This timer starts when the MS places the cell on the list of strongest cells for reselection.
For the duration of this timer, the C2 parameter is given a negative value. This discourages
fast moving MSs from selecting the cell.
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.
This timer resets when the cell is taken off the list.
Dependencies temporary_offset
Syntax

chg_element penalty_time <value> <location> <cell_desc>
chg_cell_element penalty_time <value> <cell_desc>

disp_element penalty_time <location> <cell_desc>
6-144 68P02901W23-Q
Technical Description: BSS Command Reference penalty_time
Values
Value type Integer (1 Step = 20 seconds)

Valid range 0 to 31
0 20 seconds
1 40 seconds
2 60 seconds
... ...
30 620 seconds
Default value 0
A value of 31 is reserved to indicate that cell_reselect_offset is subtracted from

C2 and temporary_offset is ignored.
References
GSM parameter PENALTY_TIME

GSM specification TSGSM 4.08 Table 10.32a Section 10.5.2.35
TSGSM 5.08
TSGSM 3.22
68P02901W23-Q 6-145
phase_lock_duration Chapter 6: Timer parameters
phase_lock_duration
Description
The phase_lock_duration parameter extends the minimum length of time a GCLK must hold
synchronization with an MMS before the GCLK is considered synchronized.
Dependencies This parameter cannot be modified for a GPRS PCU MMS.
Syntax

modify_value <location> phase_lock_duration <new_value> mms

disp_equipment <location> mms <id1> <id2> <id3>
Values

Default value 0
50 (M-Cell only)
6-146 68P02901W23-Q
Technical Description: BSS Command Reference psi1_repeat_period
psi1_repeat_period
Description
The psi1_repeat_period timer specifies the time interval between consecutive Packet System
Information (PSI) type 1 messages in 52-frame multiframes for a cell.
Dependencies The PBCCH/PCCCH otional feature must be unrestricted.
Syntax

chg_element psi1_repeat_period <value> <location> <cell_desc>
chg_cell_element psi1_repeat_period <value> <cell_desc>

disp_element psi1_repeat_period <location> <cell_desc>
Values
Value type Integer

Valid range 0 to 16
68P02901W23-Q 6-147
psi1_repeat_period Chapter 6: Timer parameters
0 Period calculated by algorithm (based on bs_pbcch_blks and

number of PSI instances in low repetition rate group).
1 to 16 Frequency of PSI1 in a 52-frame multiframe
Default value 5 Five PSI1s in a 52-frame multiframe
Table 6-1 shows the combinations of psi1_repeat_period and bs_pbcch_blks that are not permitted.
Table 6-1 Impermissible combinations of psi1_repeat_period and bs_pbcch_blks
bs_pbcch_blks psi1_repeat_period Allowed

1 1 No
2 1 No
6-148 68P02901W23-Q
Technical Description: BSS Command Reference radio_chan_released
radio_chan_released
Description
The radio_chan_released timer specifies how long the BSC waits for the BTS to release a
call. This timer starts when one of the following occurs:
• The BSC sends the Clear Request to the MSC.
• The MSC sends the Clear command to the BSC.

Dependencies None
Syntax

chg_element radio_chan_released <value> <location>

disp_element radio_chan_released <location>
Values

Default value 30000
68P02901W23-Q 6-149
radio_chan_released Chapter 6: Timer parameters
References
Internal name SSM_MTH

6-150 68P02901W23-Q
Technical Description: BSS Command Reference red_psp_audit_tmr
red_psp_audit_tmr
{22064}
Description
Thered_psp_audit_tmr timer specifies the audit interval for checking the health
of the redundant PSP (MPROC).
Dependencies GPRS must be unrestricted
Syntax

chg_element red_psp_audit_tmr <value> <location>

disp_element red_psp_audit_tmr <location>
Values
Value type Integer

Valid range 0 to 24
Default value 24
References
68P02901W23-Q 6-151
register_exp Chapter 6: Timer parameters
register_exp
Description
The register_exp timer specifies the wait time for the CRM to initiate registration with the BSC.
Dependencies None
Syntax

chg_element register_exp <value> <location>

disp_element register_exp <location>
Values

References
Internal name MTCRM_REGISTER_EXP

6-152 68P02901W23-Q
Technical Description: BSS Command Reference rf_chan_rel_ack
rf_chan_rel_ack
Description
The rf_chan_rel_ack timer specifies the wait time an RF channel release (acknowledgement)
message from the Radio Subsystem (RSS).
Dependencies None
Syntax

chg_element rf_chan_rel_ack <value> <location> <cell_desc>
chg_cell_element rf_chan_rel_ack <value> <cell_desc>

disp_element rf_chan_rel_ack <location> <cell_desc>
Values

Default value 5000
68P02901W23-Q 6-153
rf_chan_rel_ack Chapter 6: Timer parameters
References
Internal name MTCRM_RF_CHAN_REL_ACK

6-154 68P02901W23-Q
Technical Description: BSS Command Reference rr_ny1_rep
rr_ny1_rep
Description
The rr_ny1_rep parameter specifies the threshold for the maximum number of repetitions for the PHYSICAL
INFORMATION message during a handover. This parameter is used by RSS Layer 1 process.
Dependencies rr_t3105
Syntax

chg_element rr_ny1_rep <value> <location> <cell_desc>
chg_cell_element rr_ny1_rep <value> <cell_desc>

disp_element rr_ny1_rep <location> <cell_desc>
Values
Value type Integer (the amount of repetitions)

Default value 20
68P02901W23-Q 6-155
rr_ny1_rep Chapter 6: Timer parameters
References
Internal name TM_HO_NY1_REP

GSM specification 4.08 - 3.4.4.2
4.08 - 3.4.4.2.2: NY1
12.20 - 5.3.8.11: NY1.
6-156 68P02901W23-Q
Technical Description: BSS Command Reference rr_t3101
rr_t3101
Description
The rr_t3101 timer specifies how long the BSS waits for the MS to establish on a Standalone Dedicated
Control Channel (SDCCH) after sending an immediate assignment message.
Dependencies The rr_t3101 value must be greater than the maximum length of
time it takes for a Layer 2 establishment attempt.
Syntax

chg_element rr_t3101 <value> <location> <cell_desc>
chg_cell_element rr_t3101 <value> <cell_desc>

disp_element rr_t3101 <location> <cell_desc>
Values

Default value 5000 (add_cell default)
68P02901W23-Q 6-157
rr_t3101 Chapter 6: Timer parameters
References
GSM name T3101

GSM specification 4.08.
6-158 68P02901W23-Q
rr_t3103
Description
The rr_t3103 timer specifies how long the BSS waits for an internal handover to complete.
The purpose is to keep the old channels long enough for the MS to retain the ability to return to the
old channels when necessary and to release the channels if the call is dropped.
The rr_t3103 wait time must have a longer duration than the combined wait time for a handover command to
be sent plus the maximum time it takes to attempt to establish a data link with a multiframe mode.
Dependencies None
Syntax


Values

Default value 30000
68P02901W23-Q 6-159
References
GSM name T3103

4.08 - 11.1.2
6-160 68P02901W23-Q
rr_t3105
Description
The rr_t3105 parameter specifies the repetition between transmissions of the Physical
Information messages during the handover procedure. The RSS uses this value to calculate
the number of blocks to skip. This value is sent to the DRI.
Values for this parameter should be entered in increments of 20 milliseconds. Although the system accepts any
value between 0 and 200, only multiples of 20 are significant. If a value is entered that is not a 20 millisecond
increment, the BSS rounds the entered value to the nearest multiple of 20 that is less than the value entered.
Dependencies None
Syntax


Values
Value type Select integer (milliseconds in 20 millisecond increments)

Default value 60
68P02901W23-Q 6-161
References
Internal name TM_HO_T3105

GSM name T3105
GSM specification 4.08 - 3.4.4.2
12.20 - 5.2.8.5: T3105
6-162 68P02901W23-Q
rr_t3109
Description
The rr_t3109 timer is used during the channel release procedure in case of a radio link timeout.
When the timer expires, the CRM sends an RF channel release message to the RSS.
The rr_t3109 timer must be set to a higher value than the CRM radio_link_timeout parameter (T100).
To ensure that the network does not put two MSs on the same dedicated channel, the network must
hold onto a channel that has lost radio link long enough for the MS to release it.
The recommended rr_t3109 value is four 96-SACCH blocks (1.5 times the
radio_link_timeout parameter value).
Dependencies The rr_t3109 value must be greater than the rr_t3111_sd and the
rr_t3111_tch values.
Syntax

chg_element rr_t3109 <value> <location>
chg_cell_element rr_t3109 <value>

68P02901W23-Q 6-163
Values

Default value 14400
References
GSM name T3109

GSM specification 4.08 - 3.5 : T3109,
4.08 - 11.1.2, 11.2
12.20 - 5.2.8.5 bts air timer - air int BTS T4: T3109
6-164 68P02901W23-Q
Technical Description: BSS Command Reference rr_t3111_sd
rr_t3111_sd
Description:
The rr_t3111_sd timer specifies the delay for the deactivation of an SDCCH channel after the
disconnection of the main signalling link. The purpose is to allow some time for the possible
repetition of the disconnection of the main signalling link.
This timer starts whenever the BTS attempts to configure a hopping timeslot. This
timer stops when the procedure completes.
The rr_t3111_sd timer causes the BSS to wait before the channel in question is allocated to
another connection. The rr_t3111_sd value must be set equal to the value of T3110 (a timer
in the MS that is hard coded by the MS manufacturer).
The rr_t3111_sd and rr_t3111_tch timers replace the rr_t3111 timer beginning in GRS4.
Dependencies The rr_t3111_sd value must be less than the rr_t3109 value.
The rr_t3111_sd value must be set equal to the value of T3110.
Syntax

chg_element rr_t3111_sd <value> <location> <cell_desc>
chg_cell_element rr_t3111_sd <value> <cell_desc>

disp_element rr_t3111_sd <location> <cell_desc>
68P02901W23-Q 6-165
rr_t3111_sd Chapter 6: Timer parameters
Values

Default value 1500
References
GSM name T3111

GSM specification 4.08 - 3.5 : T3111
4.08 - 11.1.2, 11.2
6-166 68P02901W23-Q
Technical Description: BSS Command Reference rr_t3111_tch
rr_t3111_tch
Description:
Th rr_t311_tch timer specifies the delay for the deactivation of a traffic channel (TCH) after the
disconnection of the main signalling link. The purpose is to allow some time for the possible
repetition of the disconnection of the main signalling link.
This timer starts whenever the BTS attempts to configure a hopping timeslot. This
timer stops when the procedure completes.
The rr_t3111_tch timer causes the BSS to wait before the channel in question is allocated another
connection. The rr_t3111_tch parameter value must be set to a value equal to the value of T3110
(a timer in the MS that is hard coded by the MS manufacturer).
The rr_t3111_sd and rr_t3111_tch timers replace the rr_t3111 timer beginning in GRS4.
Dependencies The rr_t3111_tch value must be less than the rr_t3109 value.
The rr_t3111_tch value must be set equal to the value of T3110.
Syntax

chg_element rr_t3111_tch <value> <location> <cell_desc>
chg_cell_element rr_t3111_tch <value> <cell_desc>

disp_element rr_t3111_tch <location> <cell_desc>
68P02901W23-Q 6-167
rr_t3111_tch Chapter 6: Timer parameters
Values

Default value 1500
References
GSM parameter T3111

GSM technical specification 4.08 - 3.5 : T3111
4.08 - 11.1.2, 11.2
6-168 68P02901W23-Q
rr_t3212
Description
The rr_t3212 timer governs the MS periodic location update procedure. This timer is part
of the control channel description information parameter.
This timer starts when mobility management service or mobility management signalling terminates.
The timeout value is broadcast in a SYSTEM INFORMATION message. A value of 0 indicates an infinite
timeout value. The rr_3212 timer value should give a reasonable time between periodic location updates.
This timer stops when mobility management service or signalling initiates.
Subsystem/Process CRM
Dependencies None
Syntax


Values
Value type Integer (1 step = 6 minutes)

68P02901W23-Q 6-169
0 0 minutes
1 6 minutes
2 12 minutes
... ...
... ...
255 1530 minutes (25.5 hours)
Default value 10
References
GSM parameter T3212

GSM technical specification 4.08 - 10.5.2.8, and table 10.21: T3212
4.08 - 11.1.2, 11.2
12.20 - 5.2.8.8 config CCH - timer periodic update MS: T3212
6-170 68P02901W23-Q
Technical Description: BSS Command Reference rsl_congestion_alarm_timer
rsl_congestion_alarm_timer
{24660, 24661}
Description
The rsl_congestion_alarm_timer parameter is a RSL Congestion Control (RCC) alarm

timer which defines the minimum interval between reporting and clearing RSL congestion
alarms to the OMC-R on a per RSL-LCF basis.
Dependencies None
Syntax

chg_element rsl_congestion_alarm_timer <value> bsc

disp_element rsl_congestion_alarm_timer bsc
Values

Valid range 1000 to
600000
68P02901W23-Q 6-171
rtry_cand_prd Chapter 6: Timer parameters
rtry_cand_prd
Description
The rtry_cand_prd timer specifies how long a cell can be marked as congested and can not accept
incoming non-imperative handovers. This timer is started if either of the following occurs:
• The congestion relief procedure is started in this cell.
• The cell rejects an incoming handover due to congestion.
This timer only affects non-imperative types of handovers, such as Congestion Relief,
Band Reassignment, and Band Handovers.
This timer does not affect any imperative handover retries. Imperative handovers are allowed to take
place regardless of such timers because these handovers are needed to keep the call active.
When a handover resource is not available, the value of rtry_cand_prd for the target cell is
used (default 4 seconds). This allows different timer values for different neighbours, which
could vary in congestion levels. Using the source cell value for all its neighbours would not
give this flexibility. This applies only to internal neighbours.
Dependencies The Congestion Relief feature must be unrestricted.
(ho_exist_congest element must be enabled).
If the Congestion Relief feature is restricted, the parameter can be
set; however, it will have no effect on the system.
Syntax

chg_element rtry_cand_prd <timer length> <location> <cell_desc>
chg_cell_element rtry_cand_prd <timer length> <cell_desc>

disp_element rtry_cand_prd <location> <cell_desc>
6-172 68P02901W23-Q
Technical Description: BSS Command Reference rtry_cand_prd
Values

Default value 4000
68P02901W23-Q 6-173
sacch_info Chapter 6: Timer parameters
sacch_info
Description
The sacch_info timer specifies how long the Radio Subsystem (RSS) must hold system information messages
for the SACCH from Call Processing (CP) before it can send the system information it has down to the channel
coders. The information is sent immediately if both of the SACCH information messages are received.
If the timer expires and the RSS has not received all the SYS INFOs it is expecting, the system generates
an SWFM and sends the available system information down from the RSS.
Dependencies None
Syntax

chg_element sacch_info <value> <location>

disp_element sacch_info <location>
Values

Default value 2000
6-174 68P02901W23-Q
Technical Description: BSS Command Reference sacch_info
References
Internal name TM_SACCH_INFO

GSM specification 08.58 - 4.12 and 8.4.20
68P02901W23-Q 6-175
sccp_released Chapter 6: Timer parameters
sccp_released
Description
The sccp_released timer specifies the wait time for SCCP Released from MSC. This timer controls
the duration that the BSC waits for the SCCP connection to be released.
This timer starts when the BSC sends the Clear Complete message to the MSC.
If the timer expires, the call terminates.
Dependencies None
Syntax

chg_element sccp_released <value> <location>

disp_element sccp_released <location>
Values

Default value 30000
References
Internal name SSM_MTL

6-176 68P02901W23-Q
Technical Description: BSS Command Reference sccp_tconn_est
sccp_tconn_est
Description
The sccp_tconn_est timer specifies the wait time for the SCCP connection confirmation from the MSC.
This timer starts when the BSC sends the Connection Request to the MSC.
If this timer expires, the system terminates the call.
Dependencies None
Syntax

chg_element sccp_tconn_est <value> <location>

disp_element sccp_tconn_est <location>
Values

Default value 30000
References
Internal name TCONN_EST

68P02901W23-Q 6-177
sccp_tiar Chapter 6: Timer parameters
sccp_tiar
Description
The sccp_tiar timer specifies the receive inactivity control timer.

This timer starts when the call establishes.
Dependencies The sccp_tiar timer parameter must be greater than the sccp_tias
timer parameter.
The sccp_tiar at the BSS must be greater than the sccp_tiar at the
MSC.
Syntax

chg_element sccp_tiar <value> <location>

disp_element sccp_tiar <location>
Values

Default value 30000
6-178 68P02901W23-Q
Technical Description: BSS Command Reference sccp_tiar
References
Internal name SSM_TIAR

ITU-TSS (blue book) Q.714: TIAS, TIAR
68P02901W23-Q 6-179
sccp_tias Chapter 6: Timer parameters
sccp_tias
Description
The sccp_tias timer specifies the send activity control timer.

This timer starts when the call establishes.
If the timer expires, the BSC sends an inactivity test message to the MSC.
Dependencies The sccp_tias timer value must be less than the sccp_tiar timer
value.
Syntax

chg_element sccp_tias <value> <location>

disp_element sccp_tias <location>
Values

Default value 30000
6-180 68P02901W23-Q
Technical Description: BSS Command Reference sccp_tias
References
Internal name SSM_TIAS

ITU-TSS (blue book) Q.714: TIAS, TIAR.
68P02901W23-Q 6-181
sccp_trel Chapter 6: Timer parameters
sccp_trel
Description
The sccp_trel timer specifies the wait time for SCCP Release complete.
This timer starts when the ho_request timer expires.
Dependencies None
Syntax

chg_element sccp_trel <value> <location>

disp_element sccp_trel <location>
Values

Default value 10000
References
GSM parameter TREL

6-182 68P02901W23-Q
Technical Description: BSS Command Reference sm_audit_response
sm_audit_response
Description
The sm_audit_response timer specifies the wait time for audit response from switch manager.
This timer starts when the BSC performs an internal CIC-RCI audit.
Dependencies None
Syntax

chg_element sm_audit_response <value> <location>

disp_element sm_audit_response <location>
Values

Default value 30000
References
Internal name SSM_MTX

68P02901W23-Q 6-183
spi Chapter 6: Timer parameters
spi
Description
The spi timer specifies the wait time before initiating an internal reset after either Subsystem
Prohibited (SSP) or Signalling Point Inaccessible (SPI) occurs.
This timer may also start under the following conditions:
• At the receipt of User Part Unavailable (UPU).
• When BSS BSSAP subsystem goes down (last cell goes out of service).
If the MSC connection is lost, the system maintains all calls for this period of time. It must be long
enough to avoid causing a BSS reset but short enough not to hang the system.
Dependencies None
Syntax

chg_element spi <value> <location>

disp_element spi <location>
Values

Default value 60000
6-184 68P02901W23-Q
Technical Description: BSS Command Reference spi
References
Internal name CLM_SPI_TIMER

GSM name SPI
GSM specification 8.08 section 3.1.15
68P02901W23-Q 6-185
ss7_l2_t1 Chapter 6: Timer parameters
ss7_l2_t1
Description
The ss7_l2_t1 timer specifies the alignment ready timer.

Dependencies ss7_mode
Syntax

chg_element ss7_l2_t1 <value> <location>

disp_element ss7_l2_t1 <location>
Values

Valid range The range of values is dependent upon the value of the ss7_mode parameter
40000 to If ss7_mode = 0 (ITU)
50000
13000 to If ss7_mode = 1 (ANSI)
30000
Default value The default value is dependent upon the value of the ss7_mode parameter.
50000 If ss7_mode = 0 (ITU)
13000 If ss7_mode = 1 (ANSI)
6-186 68P02901W23-Q
Technical Description: BSS Command Reference ss7_l2_t1
The default value is set when the ss7_mode parameter value is changed.
References
Internal name T1 (ITU)

GSM name T1
GSM specification ITU (blue book) Q.703 pg 72.
68P02901W23-Q 6-187
ss7_l2_t2
Description
The ss7_l2_t2 timer specifies the not aligned timer.

Syntax


Values

150000
30000
6-188 68P02901W23-Q
References

GSM name T2
GSM specification ITU (blue book) Q.703 pg 72.
68P02901W23-Q 6-189
ss7_l2_t3
Description
The ss7_l2_t3 timer specifies the aligned timer.

Syntax


Values

1000 to 1500 If ss7_mode = 0 (ITU)
14000
6-190 68P02901W23-Q
References

GSM parameter T3
GSM technical specification ITU (blue book) Q.703 pg 72
68P02901W23-Q 6-191
ss7_l2_t4
Description
The ss7_l2_t4 timer specifies the emergency proving period timer.

Dependencies None
Syntax


Values
Value type Integer (milliseconds in increments of 5 milliseconds)

Default value 600
References

GSM parameter T4
GSM technical specification ITU (blue book) Q.703 pg 72.
6-192 68P02901W23-Q
ss7_l2_t5
Description
The ss7_l2_t5 timer specifies the sending SIB timer.

Dependencies None
Syntax


Values
Value type Integer (milliseconds in increments of 5 milliseconds)

Default value 100
References

GSM name T5
68P02901W23-Q 6-193
ss7_l2_t6
Description
The ss7_l2_t6 timer specifies the remote congestion timer.

Syntax


Values

3000 to 6000 If ss7_mode = 0 (ITU)
1000 to 6000 If ss7_mode = 1 (ANSI)
6-194 68P02901W23-Q
References

GSM parameter T6
68P02901W23-Q 6-195
ss7_l2_t7
Description
The ss7_l2_t7 timer specifies the excessive delay of acknowledgement timer. If the error correction
method is set to PCR, the minimum value for this parameter is 0.8 seconds.
Dependencies If pcr_enable is “on", ss7_l2_t7 must be greater than or equal to
800 milliseconds.
Syntax


Values

Default value 1000
References

GSM parameter T7
6-196 68P02901W23-Q
ss7_l3_t1
Description
The ss7_l3_t3 timer specifies the delay to avoid mis-sequencing on changeover timer.
Dependencies None
Syntax


Values
Value type Integer (milliseconds in 5 millisecond increments)

Valid range 500 to1200
Default value 850
References
GSM parameter T1_TIMER

GSM technical specification ITU (blue book) Q.704 pgs 196-197
ITU (blue book) Q.707 pg 349: supervision timers T1, T2 ( SLT_T1,
SLT_T2 )
68P02901W23-Q 6-197
ss7_l3_t12
Description
The ss7_l3_t12 timer specifies the uninhibit acknowledgement timer.

Dependencies None
Syntax


Values

Default value 1150
References
Internal name T12_TIMER (ITU)

GSM parameter T12
ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1,
SLT_T2 )
6-198 68P02901W23-Q
ss7_l3_t13
Description
The ss7_l3_t13 timer specifies the force uninhibit timer.

Dependencies None
Syntax


Values

Default value 1150
References
Internal name T13_timer (ITU)

GSM parameter T13
SLT_T2 )
68P02901W23-Q 6-199
ss7_l3_t14
Description
The ss7_l3_t14 timer sets the inhibition acknowledgement timer.

Dependencies None
Syntax


Values

Default value 2500
References
Internal name T14_TIMER (ITU)

GSM name T14
SLT_T2 )
6-200 68P02901W23-Q
ss7_l3_t17
Description
The ss7_l3_t17 timer specifies the time to wait to avoid oscillation of initial align-
ment failure and link restart timer.
Dependencies None
Syntax


Values

Default value 1150
References
Internal name T17_TIMER

GSM parameter T17
SLT_T2 )
68P02901W23-Q 6-201
ss7_l3_t2
Description
The ss7_l3_t2 timer specifies the wait time for changeover acknowledgement timer.
Dependencies If pcr_enable is “on", ss7_l3_t2 must be greater than or equal to
1400 milliseconds.
Syntax


Values

Default value 1400
References

GSM name T2
SLT_T2 )
6-202 68P02901W23-Q
ss7_l3_t22
Description
The ss7_l3_t22 timer specifies the local inhibit test timer.

Syntax


Values

Valid range The range of values is dependent upon the value of the ss7_mode parameter.
360000
120000
270000 If ss7_mode = 0 (ITU)
68P02901W23-Q 6-203
References

GSM name T22
SLT_T2 )
6-204 68P02901W23-Q
ss7_l3_t23
Description
The ss7_l3_t23 timer specifies the remote inhibit test timer.

Syntax


Values

Valid range The range of values is dependent upon the value of the ss7_mode parameter.
360000
120000
270000 If ss7_mode = 0 (ITU)
68P02901W23-Q 6-205
References

GSM parameter T23
GSM technical specification ITU (blue book) Q.704 pgs 196 -197
SLT_T2 )
6-206 68P02901W23-Q
ss7_l3_t4
Description
The ss7_l3_t4 timer specifies the waiting for changeback acknowledgement (first attempt) timer.
Dependencies None
Syntax


Values

Default value 850
References

GSM name T4
SLT_T2 )
68P02901W23-Q 6-207
ss7_l3_t5
Description
The ss7_l3_t5 timer specifies the waiting for changeback acknowledgement (second attempt) timer.
Dependencies None
Syntax


Values
Value type Integer (milliseconds in 5 millisecond increment)

Default value 850
References

GSM parameter T5
SLT_T2 )
6-208 68P02901W23-Q
Technical Description: BSS Command Reference ss7_slt_t1
ss7_slt_t1
Description
The ss7_slt_t1 parameter specifies the supervision timer for signalling link test acknowledgement.
Dependencies None
Syntax

chg_element ss7_slt_t1 <value> <location>

disp_element ss7_slt_t1 <location>
Values

Default value 8000
References
Internal name SLT_T1_TIMER

GSM name T1
SLT_T2 )
68P02901W23-Q 6-209
start_ack Chapter 6: Timer parameters
start_ack
Description
The start_ack parameter specifies the BSC wait time for the starting acknowledgement of
a single registered BTS during configuration time.
The value selected must give the CRM enough time to answer a request from the CLM when the system
is coming out of reset. The typical value for this timer is 1000 milliseconds.
Dependencies None
Syntax

chg_element start_ack <value> <location>

disp_element start_ack <location>
Values

Default value 30000
References
Internal name CLM_MTJ1

6-210 68P02901W23-Q
Technical Description: BSS Command Reference static_sync_timer
static_sync_timer
Description
This static_sync_timer specifies the maximum amount of time that is allowed for the channel
coder to transition from initial time alignment to static time alignment. Static time alignment
is necessary before the channel coder can process data.
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 one site reset is required for all to be changed.
The GPRS feature restricts the modifications of the GPRS Alarm Increment/Decrement
Time Period, GCI error increment, GCI error generation threshold, GCI error clear
threshold and Static Sync Timer parameters.
Syntax

chg_element static_sync_timer <value> <location>

disp_element static_sync_timer <location>
68P02901W23-Q 6-211
static_sync_timer Chapter 6: Timer parameters
Values

1 0.001 second 1 millisecond
... ...
... ...
Default value 12000
6-212 68P02901W23-Q
Technical Description: BSS Command Reference t_stat_info
t_stat_info
Description
The t_stat_info timer specifies the interval between Subsystem Status Test (SST) messages to the MSC.
This timer is also known as clm_t_stat_info in some Motorola documentation.
Supported by OMC-R GUI
Dependencies None
Syntax

chg_element t_stat_info <value> <location>

disp_element t_stat_info <location>
Values

References
GSM specification Q.714, Section 5.3.4.2.
68P02901W23-Q 6-213
uplink_sync_timer Chapter 6: Timer parameters
uplink_sync_timer
Description
The uplink_sync_timer specifies how long a Channel Coder Unit (CCU) waits for the urgent
alarm pattern to be received before generating an error indication.
The uplink_sync_timer is also the wait time for an uplink frame error (UFE) bit of the downlink transcoding
and rate adoption unit (TRAU) frame to remain reset during a call before generating an error indication.
Dependencies This parameter is not allowed at a stand-alone BSC or RXCDR.
It can be used at a BTS.
Syntax

chg_element uplink_sync_timer <value> <location>
A site reset occurs when the value of uplink_sync_timer is changed in SYSGEN OFF mode.
Resetting the site generates several alarms. However, these alarms are blocked by the system.

disp_element uplink_sync_timer <location>
This parameter can be used at a BTS.
6-214 68P02901W23-Q
Technical Description: BSS Command Reference uplink_sync_timer
Values

Default value 1000
68P02901W23-Q 6-215
valid_candidate_period Chapter 6: Timer parameters
valid_candidate_period
Description
The valid_candidate_period timer specifies how long candidates for handovers due to
congestion are valid before querying for new ones.
This timer is copied by the copy_cell command.
Dependencies The ho_exist_congest parameter must be enabled.
Syntax

chg_element valid_candidate_period <value> <location> <cell_desc>
chg_cell_element valid_candidate_period <value> <cell_desc>

disp_element valid_candidate_period <location> <cell_desc>
Values

Default value 4000
6-216 68P02901W23-Q
Technical Description: BSS Command Reference zone_pingpong_disable_win
zone_pingpong_disable_win
Description
The zone_pingpong_disable_win parameter is an interzone timer that sets the

time window in which ping-pong handovers between zones are not allowed.
Dependencies None
Syntax

chg_element zone_pingpong_disable_win <value> 0

disp_element zone_pingpong_disable_win 0
Values
Value type Integer (1 second steps)

Default value 30
68P02901W23-Q 6-217
zone_pingpong_enable_win Chapter 6: Timer parameters
zone_pingpong_enable_win
Description
The zone_pingpong_enable_win parameter is an interzone timer that sets the time window
in which ping-pong handovers between zones are continuously allowed as regulated
by the zone_pingpong_count parameter (see "zone_pingpong_count" on page 5-836).
Dependencies None
Syntax

chg_element zone_pingpong_enable_win <value> 0

disp_element zone_pingpong_enable_win 0
Values
Value type Integer (1 second steps)

Default value 30
6-218 68P02901W23-Q
Chapter
7
Device/function parameters
Device and function database parameters are BSS parameters, associated with equipped
devices and functions, that can be modified.
The modify_value command is used to modify parameters on devices and functions that
have been equipped using the equip command.
For detailed information on the modify_value command, refer to the command description
under "modify_value" on page 2-404 .
In this chapter the device/function database parameters are described in alphabetical order,
using the presentation layout as detailed in the Device and function database parameters
presentation section at the start of this chapter.
68P02901W23-Q 7-1
Device and function database parameters presentation Chapter 7: Device/function parameters
Device and function database parameters

presentation
The layout of the device/function parameter reference information is explained below.
Parameter reference
The actual parameter reference appears at the head of the page containing the reference information,
and is reproduced in the contents and the index of this manual.
Description
This section of the reference presentation describes the parameter function in detail. Dependencies on
other database elements and system functions are included in the parameter description.
Device/Function
This sub-section indicates the devices or functions from the following list, for which the
parameter of the modify_value command may be modified:
AXCDR Associated XCDR
BSP Base Site control Processor
BSS Base Station Subsystem
BTP Base Transceiver Processor
CAB Cabinet
CAGE Cage
COMB COMBiner
DHP Digital Host Processor
DYNET Dynamic Network
GBL Gb Link
GCLK Generic CLocK board
LCF Link Control Function
MMS Multiple serial interface link
7-2 68P02901W23-Q
Technical Description: BSS Command Reference Device and function database parameters presentation
MSI Multiple Serial Interface board

PCU Packet Control Unit
RSL Radio Signalling Link
RTF Receive Transmit Function
SITE BSC or BTS
XBL Transcoder to BSS Link
Type
This sub-section indicates the classification of the database parameter 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

This sub-section indicates whether the database element value may be changed via the OMC-R GUI (Graphics
User Interface). If a value is not supported via 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 numbers required

This sub-section indicates whether the database parameter affects specific cells and requires the GSM cell
numbers to be included in the command syntax when the parameter is displayed or changed.
Dependencies
This sub-section describes any database internal or external dependencies which may affect value assignments
of the database parameter. These dependencies must be considered when changes are made to the parameter.
Operator actions
This sub-section lists specific actions required when changing Type B parameters, and
includes any precautions that are appropriate.
Use of all location option

This sub-section indicates whether the all location option of the modify_value command is
or is not permitted when changing the parameter value.
Syntax
This section provides the syntax of the change and display command strings for the
particular device/function database parameter.
68P02901W23-Q 7-3
Device and function database parameters presentation Chapter 7: Device/function parameters

This sub-section contains the:
• modify_value command syntax used to 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.
• equip command syntax which is included where an element is initially assigned using the
equip command and modified using the modify_value command. The individual equip
command prompts are listed in the equip command description "equip" on page 2-329.

This sub-section contains the disp_equipment command syntax used to display the database
element value. The command name, the parameter name, indices (if required), and the
location are included in the command syntax.
Values
This section lists the value types and valid ranges for the database values for the particular parameter.
Value type
This sub-section indicates whether the parameter database value is an integer, Boolean, text or
alphanumeric and, if required, what the value represents.
Value range
This sub-section indicates the range of the parameter database value. Values for some elements
are expressed as steps representing incremental values.
Default values
This sub-section indicates the default database value if available for the parameter.
Some parameters are assigned default values when the database is initially loaded. This default value may
only be displayed by using the disp_equipment command before the database parameter is changed for the
first time. The default value may be changed by using the appropriate modify_value command.
If an invalid value is entered when using the modify_value command, the command is abandoned and
an error message presented. The original value of the parameter remains unchanged.
7-4 68P02901W23-Q
Technical Description: BSS Command Reference antenna_select
antenna_select
Description
The antenna_select parameter specifies the first antenna attached to a transceiver.

Device/Function DRI
Dependencies The transceiver must be locked when modifying this parameter.
Operator actions Lock the transceiver before modifying this parameter.
Syntax

modify_value <location> antenna_select <value>
dri <dev_fun_id1> <dev_fun_id2> <dev_fun_id3>
equip <location> dri

disp_equipment <location> dri <id1> <id2> <id3>
Values
Value type Integer

Valid range 1 to 6
Default value None
68P02901W23-Q 7-5
antenna_select Chapter 7: Device/function parameters
This parameter must be set to a value of 2 for a secondary frequency in a

multiband Horizonmacro site.
7-6 68P02901W23-Q
Technical Description: BSS Command Reference ber_oos_mon_period
ber_oos_mon_period
Description
The ber_oos_mon_period parameter specifies the length of time that an in service MMS must be above
a specified Bit Error Rate (BER) before it is taken Out Of Service (OOS). The default value for this
parameter is assigned when MMSs are equipped automatically on the equipping of an MSI.
This parameter is available for MMSs equipped from GPRS PMC MSIs.
Device/Function MMS
Dependencies None
Use of all locations option Yes
Syntax

modify_value <location> ber_oos_mon_period <value> mms <dev_fun_id1>
<dev_fun_id2> <dev_fun_id3>

An additional check is performed while displaying an MMS. If the MSI type of the
MMS is RF_UNIT, ber_oos_mon_period is not displayed.
68P02901W23-Q 7-7
ber_oos_mon_period Chapter 7: Device/function parameters
Values

Valid range 1 to 60
Default value 8
7-8 68P02901W23-Q
Technical Description: BSS Command Reference ber_restore_mon_period
ber_restore_mon_period
Description
The ber_restore_mon_period parameter specifies the length of time that an out of service MMS must
be at a 0.000001 Bit Error Rate (BER) before it is put in service. The default value for this parameter
is assigned when MMSs are equipped automatically on the equipping of an MSI.
Device/Function MMS
Dependencies None
Syntax

modify_value <location> ber_restore_mon_period <value> mms

An additional check is performed while displaying an MMS. If the MSI type of the
MMS is RF_UNIT, ber_restore_mon_period is not displayed.
68P02901W23-Q 7-9
ber_restore_mon_period Chapter 7: Device/function parameters
Values
Value type Integer (100 milliseconds)

Default value 600
7-10 68P02901W23-Q
Technical Description: BSS Command Reference bsc_cbc_operator
bsc_cbc_operator
Description
The bsc_cbc_operator parameter specifies the BSC CBC operator.

Device/Function CBL
Syntax

modify_value 0 bsc_cbc_operator "<value>" cbl
equip <location> cbl

disp_equipment 0 cbl <id1> <id2> <id3>
Values
Value type Text

Valid range Up to 20 alphanumeric characters
Default value None
The alphanumeric characters for value must be entered within quotation marks.
68P02901W23-Q 7-11
cabinet_type Chapter 7: Device/function parameters
cabinet_type
Description
The cabinet_type parameter specifies the cabinet type.

Table 7-1 lists the cabinet types and associated groups.
Table 7-1 Cabinets/Groups
Cabinets Group
0 to 9 GPROC
10 to 11 MCU
12 to 13 TCU
14 to 16 MICRO
17 not supported
18 Horizonmacro master
19 Horizonmacro extension
20 Horizoncompact BTS ()
22 Horizonmicro2 BTS
23 Horizoncompact2 BTS
24 Horizon II macro
25 Horizon II macro extension
Device/Function CAB
Dependencies When changing the cabinet type, the new cabinet type must be in
the same cabinet group as the old cabinet type.
The cabinet type may not be modified from Horizonmicro
(M-Cellarena), Horizoncompact (M-Cellarenamacro), to M-Cellcity
or M-Cellmicro if frequency hopping is enabled at the site.
The system rejects an attempt to alter the cabinet type from
M-Cellcity, Horizonmicro (M-Cellarena) or Horizoncompact
(M-Cellarenamacro) to M-Cellmicro if any MSIs of type niu_hdsl
are equipped at the M-Cellcity, Horizonmicro (M-Cellarena) or
Horizoncompact (M-Cellarenamacro) sites.
7-12 68P02901W23-Q
Technical Description: BSS Command Reference cabinet_type
The cabinet type may not be modified to M-Cell2 if there are any
MSI devices equipped in slots other than 0, or if there are any MSI
devices with a first device id greater than 1.
The system rejects the modify_value cabinet_type command if the
change is from TCU_6 to TCU_2, and the cabinet has at least one
DRI equipped via the FMUX. A DRI that uses an FMUX as the
TCU connection type cannot be equipped to a TCU_2 cabinet.
If a modify_value command from M-Cellcity, Horizonmicro
(M-Cellarena) or Horizoncompact (M-Cellarenamacro) to
M-Cellmicro is accepted, all the hdsl parameters initially set by the
chg_element command are set to their defaults.
If a cabinet type of Horizonmicro (M-Cellarena) or Horizoncompact
(M-Cellarenamacro) is entered during CAB device equipage, then
the CAB ID entered must be 0 if CAB device 0 does not yet exist.
The bts_type per SITE element is set to 1 upon equipage of a slave
Horizonmicro or Horizoncompact CAB device.
The valid CAB ID range at a Horizonmicro BTS site is 0 to 2.
When modifying this parameter ensure that the cabinet_type is
compatible with the hardware board type. A mismatch during a
hard reset causes the BTS to remain OOS.
Syntax

equip <location> cab
modify_value <location> cabinet_type <value> cab


disp_equipment <location> cab <id1> <id2> <id3>
Values
Value type Integer or alphanumeric (entered as an alphanumeric string, without any delimiters)
Valid range 0 to 25
0 bts4d_48v
1 bts4d_27v
2 bssc_48v
3 bssc_27v
68P02901W23-Q 7-13
cabinet_type Chapter 7: Device/function parameters
4 bts_dab
5 bssc_dab
6 excell_4
7 excell_6
8 topcell
9 bts_5
10 m_cell_2
11 m_cell_6
12 tcu_2
13 tcu_6
14 m_cell_micro
15 m_cellcity
16 m_cellarena
17 not supported
18 horizonmacro
19 horizonmacro_ext
20 m_cellarena_macro
22 horizonmicro2
23 horizoncompact2
24 horizonmacro2
25 horizonmacro2_ext
Default value None
7-14 68P02901W23-Q
Technical Description: BSS Command Reference cavity
cavity
Description
The cavity parameter specifies the cavity number within the COMB device that will be used by the DRI.
Device/Function DRI
Dependencies If the combining_type is 0, the combiner_id and cavity values are
considered invalid and no modifications are allowed.
If the combining_type is 1 or 2, the combiner_id and cavity
number are required and will be prompted. If these values have
already been specified, the existing values can be used as defaults.
All affected devices must be locked.
Syntax

modify_value <location> cavity <value> dri <dev_fun_id1> <dev_fun_id2>
disp_equipment <location> dri <id1> <id2>
Values
Value type Integer

Valid range 0 to 5
Default value None
68P02901W23-Q 7-15
cbc_operator Chapter 7: Device/function parameters
cbc_operator
Description
The cbc_operator parameter specifies the CBC operator.

Device/Function CBL
Syntax

modify_value 0 cbc_operator "<value>" cbl
equip 0 cbl

disp_equipment 0 cbl <id1> <id2> <id3>
Values
Value type Text

Valid range Up to 20 alphanumeric characters
Default value None
The alphanumeric characters for value must be entered within quotation marks.
7-16 68P02901W23-Q
Technical Description: BSS Command Reference cell_zone
cell_zone
Description
The cell_zone parameter specifies the zone to which an RTF belongs in a concentric cell environment.
If the GPRS feature is in use, GPRS carriers must be in the outer zone of a concentric cell.
Device/Function RTF
Dependencies The Concentric Cells feature must be enabled and inner_zone_alg
must be set to other than 0.
Only non-BCCH carriers can be configured in the inner zone.
Syntax

modify_value <location> cell_zone <value> rtf
The system displays a warning message if the cell_zone value for an RTF is changed in SYSGEN
OFF mode. The RTF cycles if the change is made in SYSGEN OFF mode.
If the inner_zone_alg is disabled in a cell and a carrier is equipped in the inner zone, or
changed to the inner zone, the system displays a warning message.

disp_equipment <location> rtf <id1> <id2> <id3>
68P02901W23-Q 7-17
cell_zone Chapter 7: Device/function parameters
Values
Value type Boolean

Valid range 0 or 1
0 Outer zone
1 Inner zone
Default value 0
7-18 68P02901W23-Q
Technical Description: BSS Command Reference chan_alloc_priority
chan_alloc_priority
Description
The chan_alloc_priority parameter specifies the channel allocation priority of an in-service carrier.
The interference band of a channel is still the first criterion in the channel allocation algorithms. A channel
from the highest priority carrier matching the requested interference band is allocated to a channel request.
Device/Function RTF
Dependencies None
Syntax

modify_value <location> chan_alloc_priority <value>
rtf <dev_fun_id1> <dev_fun_id2> <dev_fun_id3>

Values
Value type Integer

0 Highest priority
250 Lowest priority
Default value 0
68P02901W23-Q 7-19
cic_validation Chapter 7: Device/function parameters
cic_validation
Description
The cic_validation parameter enables or disables CIC validation.

Device/Function AXCDR
Dependencies None
Syntax

modify_value <location> cic_validation <value> AXCDR <axcdr_id>
equip <location> axcdr

disp_equipment <location> axcdr <cic_id>
Values
Value type Text

Valid range yes or no
yes Enabled
no Disabled
Default value no
7-20 68P02901W23-Q
Technical Description: BSS Command Reference clkx0
clkx0
Description
The clkx0 parameter specifies whether or not a CLKX (Clock Extender) half-size board is
present for this GCLK (Generic Clock) board. For GCLK 0, the CLKX board should be in
slot U7. For GCLK 1, the CLKX board should be in slot U4.
Device/Function GCLK
Dependencies None
Slots U2 through U7 can contain CLKX cards or KSWX cards. The system checks
the contents of these slots every 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 would occupy a slot that is already occupied.
Syntax

modify_value <location> clkx0 <value> gclk <gclk_id>
equip <location> gclk

disp_equipment <location> gclk <id1>
68P02901W23-Q 7-21
clkx0 Chapter 7: Device/function parameters
Values
Value type Text

yes Present
no Not present
Default value no
7-22 68P02901W23-Q
clkx1
Description
Dependencies None
Syntax

modify_value <location> clkx1 <value> gclk gclk_id>

68P02901W23-Q 7-23
Values
Value type Text

yes Present
no Not present
Default value no
7-24 68P02901W23-Q
clkx2
Description
Dependencies None
Syntax

modify_value <location> clkx2 <value> gclk <gclk_id>

68P02901W23-Q 7-25
Values
Value type Text

yes Present
no Not present
Default value no
7-26 68P02901W23-Q
Technical Description: BSS Command Reference combiner_address
combiner_address
Description
The combiner_address parameter specifies the message routing address for the Combiner (COMB).
Device/Function COMB
Dependencies The address must be unique within a site.
Syntax

modify_value <location> combiner_address
<value> comb <dev_fun_id1> <dev_fun_id2>
equip <location> comb

disp_equipment <location> comb <id1> <id2>
Values
Value type Integer

Default value None
68P02901W23-Q 7-27
combiner_id Chapter 7: Device/function parameters
combiner_id
Description
The combiner_id parameter specifies the identity of the COMB device the DRI uses for combining.
Device/Function DRI
Syntax

modify_value <location> combiner_id
<value> dri <dev_fun_id1> <dev_fun_id2>

Values
Value type Integer

Valid range 0 to 13
Default value None
7-28 68P02901W23-Q
Technical Description: BSS Command Reference combining_type
combining_type
Description
The combining_type parameter specifies what type of combining is associated with each DRI.
Device/Function DRI
Syntax

modify_value <location> combining_type
<value> dri <dev_fun_id1> <dev_fun_id2>

Values
Value type Integer

Valid range 0 to 2
0 None
1 Non-controlling
68P02901W23-Q 7-29
combining_type Chapter 7: Device/function parameters
2 Controlling
Default value 0
7-30 68P02901W23-Q
Technical Description: BSS Command Reference dri_density
dri_density
Description
The dri_density parameter specifies the density mode (single or double).

Device/Function DRI
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 DR devices.
Syntax

modify_value <location> dri_density <value> dri


Values
Value type Integer or text

Valid range 1 or 2, “single" or “double"
1 or “single" single density mode
2 or “double" double density mode
Default value None
68P02901W23-Q 7-31
ext_timeslots Chapter 7: Device/function parameters
ext_timeslots
Description
The ext_timeslots parameter specifies the number of extended range timeslots for an RTF.
Device/Function RTF
Dependencies The number of extended range timeslots can be changed only if the
Extended Range Cells feature is unrestricted.
The number of extended range timeslots cannot be modified for
inner-zone carriers.
An RTF having one or more extended range timeslots configured
cannot have the cell_zone changed to inner.
If the Extended Range Cell feature is enabled, the number of
extended range timeslots for the BCCH RTF must support the
number of configured BCCH, CCCH, and SDCCH channels.
Syntax

modify_value 0 ext_timeslots <value> rtf <id1> <id2> [<id3>]
equip <location> RTF
The system displays a warning message whenever the value for the ext_timeslots parameter is
changed. The RTF cycles when the ext_timeslots value is modified in SYSGEN OFF mode
.

disp_equipment <location> rtf <id1> <id2> [<id3>]
7-32 68P02901W23-Q
Technical Description: BSS Command Reference ext_timeslots
Values
Value type Integer

Valid range 0 to 4
Default value 0
68P02901W23-Q 7-33
fm_cell_type Chapter 7: Device/function parameters
fm_cell_type
Description
The fm_cell_type parameter specifies the type of cell structure supported at the BTS
in which a specific DRI is equipped.
Device/Function DRI
Dependencies Setting of this parameter depends on the setting of diversity_flag .
See the table of values below.
Operator actions Lock the DRI/RCU before modifying this parameter.
Syntax

modify_value <location> fm_cell_type <value>
dri <dev_fun_id1> <dev_fun_id2> <dev_fun_id3>

Values
Value type Integer

Valid range 0 to 4 (depends on diversity_flag) as follows:
diversity_flag fm_cell_type Result
0 0 Non-diversity (RCUs only)
0 1 Use branch 1 of a DRCU in a non-diversity mode
7-34 68P02901W23-Q
Technical Description: BSS Command Reference fm_cell_type
0 2 Use branch 2 of a DRCU in a non-diversity mode

1 3 Shared diversity
1 4 Full diversity
Default value None
68P02901W23-Q 7-35
frequency_type Chapter 7: Device/function parameters
frequency_type
Description
The frequency_type parameter specifies the frequencies allowed for a cabinet.

Device/Function CAB
Type A (but see Operator actions below)
Dependencies If any of the frequency types specified are not valid at the BSS, the
system rejects the modify_value command. Valid frequency types
at a BSS can be modified or displayed by the freq_types_allowed
command.
• Frequency_types can be added and deleted in SYSGEN ON

mode.
• Frequencies can be added but not deleted in SYSGEN OFF

mode.
Operator actions To delete a frequency type, the system must first be put in SYSGEN
ON mode.
Syntax

modify_value <location> frequency_type <freq_type> cab
<id1> [<id2>] [<id3>]

disp_equipment <location> cab <id1> [<id2>] [<id3>]
7-36 68P02901W23-Q
Technical Description: BSS Command Reference frequency_type
Values
Value type Integer representing one or more frequency types, as follows:

Valid range 1 to 15
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
12 DCS1800 and PCS1900
13 PGSM, DCS1800 and PCS1900
14 EGSM, DCS1800 and PCS1900
15 PGSM, EGSM, DCS1800 and PCS1900
Default value None
68P02901W23-Q 7-37
hdsl_modem_setting Chapter 7: Device/function parameters
hdsl_modem_setting
Description
The hdsl_modem_setting parameter specifies the setting of an integrated HDSL modem.

The possible settings are slave and master.
Changing this parameter updates the MCU FLASH memory values.
Device/Function MMS
unrestricted.
This parameter may only be changed on MMS devices with a
protocol type of HDSL equipped as msi_type of niu_hdsl.
The hdsl_modem_setting value cannot be modified when the
MMS is in a PATH. To alter the values would require unequipping
all the PATH devices using this MMS, altering the values, then
equipping the PATH devices.
The hdsl_modem_setting value cannot be modified for a GPRS
PCU MMS.
Operator actions MMS must be locked.
Syntax

modify_value <location> hdsl_modem_setting
<value> mms <mms_id1> <mms_id2>
equip <location> msi

disp_equipment <location> mms <mms_id1> <mms_id2>
7-38 68P02901W23-Q
Technical Description: BSS Command Reference hdsl_modem_setting
Values
Value type Text

Valid range slave or master
Default value master
68P02901W23-Q 7-39
hdsl_oos_mon_period Chapter 7: Device/function parameters
hdsl_oos_mon_period
Description
An in-service HDSL link is continuously monitored for the Signal to Noise Ratio (SNR) level defined
by hdsl_snr_oos. If the SNR level falls below this threshold for more than the period specified by
the hdsl_oos_mon_period device parameter, the HDSL link is taken out of service.
The default value for this parameter is automatically assigned when the MSI is equipped.
Device/Function MMS
unrestricted.
protocol type of HDSL, a modem setting of master, and equipped
on an msi_type of niu_hdsl.
The hdsl_oos_mon_period value cannot be modified for a GPRS
PCU MMS.
Use of all locations opt No
ion
Syntax

modify_value <location> hdsl_oos_mon_period <value> mms <dev_fun_id1>

7-40 68P02901W23-Q
Technical Description: BSS Command Reference hdsl_oos_mon_period
Values

Default value 20
68P02901W23-Q 7-41
hdsl_restore_mon_period Chapter 7: Device/function parameters
hdsl_restore_mon_period
Description
An Out Of Service (OOS) HDSL link is continuously monitored for the Signal to Noise Ratio (SNR) level
defined by hdsl_snr_restore. If the SNR level is maintained above this threshold for more than the period
specified by the hdsl_restore_mon_period device parameter, the HDSL link is brought back into service.
The default value for this parameter is automatically assigned when the MSI is equipped.
Device/Function MMS
unrestricted.
protocol type of HDSL, a modem setting of master, and equipped on
an msi_type of niu_hdsl.
All slave modem alarm thresholds are identical to the master modem
alarm thresholds.
The hdsl_restore_mon_period value cannot be modified for a
GPRS PCU MMS.
Use of all locations No
option
Syntax

modify_value <location> hdsl_restore_mon_period <value> mms

7-42 68P02901W23-Q
Technical Description: BSS Command Reference hdsl_restore_mon_period
Values

Default value 20
68P02901W23-Q 7-43
ias_connected Chapter 7: Device/function parameters
ias_connected
Description
The ias_connected parameter enables or disables internal alarms system (IAS).

Device/Function CAGE
Dependencies None
Syntax

modify_value <location> ias_connected <value> cage <id1>
equip <location> cage

disp_equipment <location> cage <id1> <id2> <id3>
Values
Value type Text

yes Enabled
no Disabled
Default value None
7-44 68P02901W23-Q
Technical Description: BSS Command Reference int_antenna
int_antenna
Description
The int_antenna parameter specifies whether or not the cabinet contains an internal integrated antenna.
Device/Function CAB
Dependencies This parameter is only allowed for M-Cellcity M-Cellarena, and
Horizonmicro cabinets.
Syntax

modify_value <location> int_antenna <value>
cab <dev_fun_id1> <dev_fun_id2> <dev_fun_id3>

Values
Value type Text

yes Internal antenna is present and should be used.
no Internal antenna is not present.
Default value None
68P02901W23-Q 7-45
int_hdsl_modem Chapter 7: Device/function parameters
int_hdsl_modem
Description
The int_hdsl_modem parameter indicates whether or not an internal HDSL modem is present in the cabinet.
Device/Function CAB
Dependencies This parameter is only allowed for M-Cellcity, M-Cellarena,
Horizonmicro and Horizoncompact cabinets.
Syntax

modify_value <location> int_hdsl_modem <value>
cab <dev_fun_id1> <dev_fun_id2> <dev_fun_id3>

Values
Value type Text

yes Present
no Not present
Default value None
7-46 68P02901W23-Q
Technical Description: BSS Command Reference lapd_k
lapd_k
Description
The lapd_k parameter specifies the maximum number of unacknowledged LAPD information frames.
Both ends of the link reinitialize when this value is modified for RSL.
Device/Function RSL, XBL
Dependencies None
Operator actions The operator needs to cycle (lock and then unlock) the device for the
change to take effect.
Syntax

modify_value <location> lapd_k <value> rsl
modify_value <location> lapd_k <value> xbl

equip <location> rsl
equip <location> xbl

disp_equipment <location> rsl <id1> <id2> <id3>
disp_equipment <location> xbl <id1> <id2> <id3>
68P02901W23-Q 7-47
lapd_k Chapter 7: Device/function parameters
Values
Value type Integer

Valid range 1 to 10
Default value 7
7-48 68P02901W23-Q
Technical Description: BSS Command Reference lapd_n200
lapd_n200
Description
The lapd_n200 parameter specifies the maximum number of retransmissions of a frame.

Dependencies None
Operator actions The operator needs to cycle (lock and then unlock) the device for
the change to take effect.
Syntax

modify_value <location> lapd_n200 <value> rsl
modify_value <location> lapd_n200 <value> xbl


68P02901W23-Q 7-49
lapd_n200 Chapter 7: Device/function parameters
Values
Value type Integer

Valid range 1 to 5
Default value 3
7-50 68P02901W23-Q
Technical Description: BSS Command Reference lapd_t200_timer
lapd_t200_timer
Description
The lapd_t200_timer parameter specifies the LAPD T200 timer. The LAPD T200 timer is
used to time the acknowledgement of a transmitted frame.
Dependencies The minimum value for this parameter should be 800 milliseconds
when using satellite links.
Operator actions The operator needs to cycle (lock and then unlock) the device for
the change to take effect.
Syntax

modify_value <location> lapd_t200_timer <value>
rsl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3>
modify_value <location> lapd_t200_timer <value>

xbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3>

68P02901W23-Q 7-51
lapd_t200_timer Chapter 7: Device/function parameters
Values

Valid range 1400 to 5000 (in 50 millisecond increments)
Default value 2500
7-52 68P02901W23-Q
Technical Description: BSS Command Reference max_cbls
max_cbls
Description
The max_cbls parameter specifies the the maximum number of CBLs that may be supported by an LCF.
The all location option of the modify_value command is not permitted when changing this parameter.
Device/Function LCF
Dependencies None
Syntax

modify_value <location> max_cbls <value> lcf

Values
Value type Boolean

Valid range 0 or 1
Default value None
68P02901W23-Q 7-53
max_dris Chapter 7: Device/function parameters
max_dris
Description
This max_dris parameter specifies the maximum number of DRIs supported by the specified
GPROC device or function (BTP or DHP).
The new value is not effective until the DRI is brought back into service. DRIs that are already
in service are not affected while they are still in service.
A value of 0 may not be specified for this parameter if the BTS type is 0.
DRIs can be reassigned to other GPROCs within a cage, to bring the number of
DRIs below the modified threshold.
There is no automatic redistribution of DRIs from the specified GPROC, should the modified
threshold fall below the number of DRIs already assigned. However, if a DRI assigned to the
GPROC is taken Out Of Service (OOS), it cannot be brought back into service until the number
of DRIs assigned to the GPROC is less than the value of max_dris.
If the new threshold is greater than the number of DRIs already assigned to the
GPROC, the value is immediately used.
max_dris cannot be modified for a BTP equipped to an M-Cell site (MCU).

Device/Function BTP, DHP
Dependencies None
Syntax

modify_value <location> max_dris <value> btp
7-54 68P02901W23-Q
Technical Description: BSS Command Reference max_dris
modify_value <location> max_dris <value> dhp

equip <location> btp
equip <location> dhp

disp_equipment <location> btp <id1> <id2> <id3>
disp_equipment <location> dhp <id1> <id2> <id3>
Values
Value type Integer

Valid range 0 to 6 for BTP
1 to 6 for DHP
Default value None
68P02901W23-Q 7-55
max_gsls Chapter 7: Device/function parameters
max_gsls
Description
The max_gsls parameter specifies the maximum number of GSLs that can be configured on the LCF.
Device/Function LCF
The sum of all max_gsls specified by the equipped LCFs must be
greater than or equal to the total number of GSLs equipped.
The value for max_gsls must not exceed the available LCF HDLC
channel capacity.
Syntax

modify_value <location> max_gsls <value>
<dev_func> <dev_fun_id1> <dev_fun_id2>

disp_equipment <location> lcf <id1> <id2>
Values
Value type Integer

Valid range 0 to 6
Default value 0
7-56 68P02901W23-Q
Technical Description: BSS Command Reference max_mtls
max_mtls
Description
The max_mtls parameter specifies the maximum number of MTLs supported by a BSP or LCF.
This parameter must be set to 1 for all BSPs on a bsc_type 0, non-RXCDR system.
This parameter must be set to 1 for at least one LCF on a BSC site where the BSC type is not zero.
Set this parameter to 2 for GPROC-2 boards. When the value is set to 2, the system displays
a warning message and accepts the command.
Device/Function BSP, LCF
Type B (no operator actions)
Dependencies Change the security level to 2 to modify this parameter.
Syntax

modify_value <location> max_mtls <value> bsp
modify_value <location> max_mtls <value> lcf

equip <location> bsp

disp_equipment <location> bsp <id1> <id2> <id3>
68P02901W23-Q 7-57
max_mtls Chapter 7: Device/function parameters
Values
Value type Integer

Valid range 0 to 2
Default value None
7-58 68P02901W23-Q
Technical Description: BSS Command Reference mms_priority
mms_priority
Description
The mms_priority parameter sets the priority rating for an MMS. It determines its possible use as a
reference source to which the GCLK may phase lock. The higher the priority value, the more likely the
MMS is to be used as a reference source to which the GCLK device will frequency lock.
If the priority ratings for all MMs are set 0, the GCLK is placed in the set frequency mode.
In a GPRS system, a non-zero value for mms_priority is not permitted for a PCU
MMS or an MMS which is part of a GDS.
Device/Function MMS
Dependencies None
Syntax

modify_value <location> mms_priority <value> mms <mms_id1>
<mms_id2> <mms_id3>

disp_equipment <location> mms <mms_id1> <mms_id2> <mms_id3>
Values
Value type Integer

0 MMS is not used as a clock extraction source.
1 Lowest priority
68P02901W23-Q 7-59
mms_priority Chapter 7: Device/function parameters
255 Highest priority

Default value None
7-60 68P02901W23-Q
Technical Description: BSS Command Reference msc_mms_id
msc_mms_id
Description
The MSC MMS specifies the E1/T1 link to be used to route data for the transcoding
circuits from a GDP towards the MSC.
The MSC MMS consists of two identifiers: msc_msi_id and msc_mms_id.
The msc_msi_id parameter is the MSI identifier of a GDP whose MMS is available for routing
the transcoding circuits of a secondary GDP towards the MSC.
The msc_mms_id parameter is always zero because MSIs are not allowed to be used to provide MSC MMSs.
Device/Function MSI
Dependencies This parameter may be modified only when the MSI type is GDP.
Syntax

modify_value <location> msc_mms_id <value> msi [<msi_id1>]
[<msi_id2>] [<msi_id3>]

disp_equipment <location> msi [<msi_id1>] [<msi_id2>] [<msi_id3>]
Values
Value Integer
Valid range 0
Default value 0
68P02901W23-Q 7-61
msi_type Chapter 7: Device/function parameters
msi_type
Description
The msi_type parameter specifies a database value for a single equipped device or function at a site
for all equipped devices or functions of the type specified in the command.
The msi_type parameter also specifies modification between transcoder (XCDR) boards and
Generic Digital Processor (GDP) boards and GDP Version 2 (GDP2) and Multiple Serial
Interface (MSI) boards and secondary GDP boards.
Device/Function MSI
Dependencies The MSI type cannot be changed from GDP to XCDR when an
enhanced full rate (EFR) or GDP control is enabled.
The MSI type cannot be modified for a PICP MSI.
The MSI type cannot be changed from GDP or GDP2 to XCDR
when the trans_capability is Enhanced or GDP_2E1.
Operator actions Change to security level 2 to change this parameter.
Syntax

modify_value <location> msi_type <value> msi
[<dev_fun_id1>] [<dev_fun_id2>] [<dev_fun_id3>]
equip <location> msi

disp_equipment <location> msi [<dev_fun_id1>] [<dev_fun_id2>]
[<dev_fun_id3>]
7-62 68P02901W23-Q
Technical Description: BSS Command Reference msi_type
Values
Value type Integer (text)

Valid range 0 (msi)
1 (xcdr)
2 (gdp)
3 (niu)
7 (msi_ext_hdsl)
8 (niu_hdsl)
9 (niu_ext_hdsl)
12 (RF_unit)
14 (E1_pmc)
20 (gdp2)
21 (H2sc_niu2)
Default value None
68P02901W23-Q 7-63
n391 Chapter 7: Device/function parameters
n391
Description
The n391 parameter specifies the value for the frame relay default full status polling counter.
Device/Function GBL
Syntax

modify_value pcu n391 <value> gbl
equip pcu gbl

disp_equipment pcu gbl <id1> <id2> <id3>
Values
Value type Integer (number of polling cycles)

Default value 6
7-64 68P02901W23-Q
Technical Description: BSS Command Reference n392
n392
Description
The n392 parameter specifies the frame relay default value for error threshold counter.
Device/Function GBL
Dependencies The GPRS feature must be unrestricted. This parameter must be less
than or equal to the value of n393.
Syntax

equip pcu gbl

Values
Value type Integer (number of errors)

Valid range 1 to 10
Default value 3
68P02901W23-Q 7-65
n393 Chapter 7: Device/function parameters
n393
Description
The n393 parameter specifies the frame relay default value for monitored events counter.
Device/Function GBL
Dependencies The GPRS feature must be unrestricted. The value of this parameter
must be greater than or equal to the value of n392 .
Syntax

equip pcu gbl

Values
Value type Integer (number of events)

Valid range 1 to 10
Default value 4
7-66 68P02901W23-Q
Technical Description: BSS Command Reference nbit
nbit
Description
The nbit parameter enables and disables the second remote alarm bit (nbit). The default value for
this parameter is automatically assigned when the MSI is equipped.
Device/Function MMS
Dependencies The MMS must be locked when modifying this parameter.
Operator actions Lock the MMS before modifying this parameter
Syntax

modify_value <location> nbit <value> mms <dev_fun_id1>

Values
Value type Boolean

Valid range 0 or 1
0 Disabled
1 Enabled
Default value 0
68P02901W23-Q 7-67
ne_id Chapter 7: Device/function parameters
ne_id
Description
The ne_id parameter specifies the network identity.

Device/Function BSS, RXCDR
Dependencies Changing the ne_id causes all AXCDR or ABSS devices to be
cycled, resulting in the loss of all active calls managed by the
associated device.
Syntax

modify_value 0 ne_id <value> bss|rxcdr <id1>

To list the IDs for the bss/rxcdrs in the database, enter the following command:
disp_equipment 0 bss|rxcdr *
To display information about a specific bss/rxcdr, enter the following command:
disp_equipment 0 bss|rxcdr <id1>
Values
Value type Integer

Default value None
7-68 68P02901W23-Q
Technical Description: BSS Command Reference opto_reporting
opto_reporting
Description
The opto_reporting parameter allows the operator to modify the reporting status and external
alarm string mapping for DRI and EAS optocouplers.
When enabling opto_reporting for a DRI, the operator is prompted for the index of the user defined
alarm string for the optocoupler. The range of values is 0 to 33; there is no default value.
When enabling opto_reporting for an EAS, the operator is first prompted for the optocoupler(s) whose
state should be reported. Up to eight values (separated by a comma or a space) may be entered for an
EAS at an InCell site; up to 16 values may be entered for an M-Cell site. The values may be entered
in any order. The value “all" may be specified. A range of values may be specified.
When enabling opto_reporting for an EAS, the operator is also prompted for the user defined
alarm index. The operator must enter one value indicating the index of the alarm string for each
optocoupler specified in the previous prompt. The range of values is 0 to 33 and 128; there is no
default value. (The text string “mpf" is equivalent to a value of 128.)
When disabling opto_reporting for an EAS, the operator may enter up to eight values (separated by a comma
or a space) for an EAS at an InCell site; up to 16 values may be entered for an M-Cell site. The values may be
entered in any order. The value “all" may be specified. A range of values may be specified.
Device/Function DRI/EAS
Type A (No operator actions)
Dependencies None
The affected device must be locked.
Syntax

modify_value <location> opto_reporting <value> <device> <id1> <id2> <id3>
68P02901W23-Q 7-69
opto_reporting Chapter 7: Device/function parameters
After this command string is entered, additional prompts are displayed, depending on
the device specified. (See description above for details.)

disp_equipment <location> <device> <id1> <id2> <id3>
Values
Value type Boolean

off Disabled
on Enabled
Default value None
7-70 68P02901W23-Q
Technical Description: BSS Command Reference pref_rtf_id
pref_rtf_id
Description
The pref_rtf_id specifies a preferred RTF identifier. This allows at least one carrier unit
per cabinet that is able to provide GPRS feature service.
This parameter must be an RTF unique identifier or “null" for resetting to no preferred RTF.
The value may be entered as a string or an integer.
The user is prompted for each opto that is enabled.
Device/Function DRI
Type A (No operator actions)
Dependencies This parameter must be an RTF unique identifier or “null" for
resetting to no preferred RTF.
Syntax

modify_value <location> pref_rtf_id <value> dri <id1> <id2>

Values
Value type Integer or string

Valid range 0 to 11, or “null"
Default value None
68P02901W23-Q 7-71
rsl_rate Chapter 7: Device/function parameters
rsl_rate
Description
The rsl_rate parameter specifies the signalling and control information rate of the Radio Signal Link (RSL).
Device/Function SITE
Dependencies The 16 kbit/s RSL option must be available.
The RSL cannot be changed if RSLs are already equipped for this
site.
The RSL rate cannot be changed for the BSC (site 0).
The RSL cannot be changed if the site uses dynamic allocation.
Syntax

modify_value 0 rsl_rate <value> site <site number>

disp_equipment 0 site <id1> <id2> <id3>
Values
Value type Integer (rate in kbit/s)

Valid range 1664
Default value None
7-72 68P02901W23-Q
Technical Description: BSS Command Reference sd_load
sd_load
Description
The sd_load parameter specifies the maximum number of timeslots to be configured as SDCCHs on an RTF.
The BSS configures the SDCCHs on the carriers with the highest priority, up to their SDCCH load.
Changing the sd_load parameter may cause a channel reconfiguration to make the new values
effective. The reconfiguration occurs as channels become idle.
Device/Function RTF
Dependencies None
Syntax

modify_value <location> sd_load <value> rtf <rtf_id1> <rtf_id2>

Values
Value type Integer

Valid range 0 to 2
0 BCCH EGSM extension band carrier when egsm_bcch_sd is 0 (off)
0 to 2 BCCH EGSM extension band carrier when egsm_bcch_sd is 1 (on)
2 BCCH extended range cell
n/a BCCH inner zone carrier
68P02901W23-Q 7-73
sd_load Chapter 7: Device/function parameters
2 All other types of BCCH carrier

0 Non-BCCH EGSM extension band carrier
0 Non-BCCH extended range cell
0 Non-BCCH inner zone carrier
2 All other types of non-BCCH carrier
Default value None
7-74 68P02901W23-Q
Technical Description: BSS Command Reference sd_priority
sd_priority
Description
The sd_priority parameter specifies the SDCCH placement priority for an RTF. The BSS configures
the SDCCHs on the carriers with the highest priority, up to their SDCCH load.
Changing the sd_load parameter may cause a channel reconfiguration to make the new values
effective. The reconfiguration occurs as channels become idle.
Device/Function RTF
Dependencies The sd_priority element cannot be changed for an EGSM, Extended
Range Cell, or inner zone carrier.
Syntax

modify_value <location> sd_priority <valid range> rtf <id1> <id2>

disp_equipment <location> rtf <id1> <id2>
Values
Value type Integer

0 highest priority
68P02901W23-Q 7-75
sd_priority Chapter 7: Device/function parameters
250 lowest priority

Default value Non-BCCH default = 0
BCCH default = 0
7-76 68P02901W23-Q
Technical Description: BSS Command Reference shared_timeslots
shared_timeslots
Description
The shared_timeslots parameter reserves timeslots for use when a DYNET device has
been equipped for dynamic allocation of BTSs.
Device/Function DYNET
Supported by OMC GUI No
Dependencies DYNET must be equipped.
The site must be a BSC (Location = 0).
Syntax

modify_value <location> shared_timeslots <value> dynet <id1> <id2>
equip <location> dynet

disp_equipment <location> dynet <id1> <id2>
Values
Value type Integer

Valid range 0 to 31
0 to 31 E1 link
0 to 23 T1 link
Default value 0 (no timeslots reserved)
68P02901W23-Q 7-77
slot Chapter 7: Device/function parameters
slot
Description
The slot parameter specifies the slot in which the DRI device is fitted.
When the slot parameter is modified outside SYSGEN mode, a warning message is displayed
that the specified DRI is about to be cycled (locked then unlocked). A prompt is included that
enables the operator to choose to continue or abort the change.
Device/Function DRI
Dependencies None
Syntax

modify_value <location> slot <value> dri

Values
Value type Integer

Valid range 7 to 17 (odd values only)
Default value None
7-78 68P02901W23-Q
Technical Description: BSS Command Reference start_ts
start_ts
Description
The start_ts parameter specifies the first GBL timeslot on the E1/T1 link.
Device/Function GBL
Syntax

modify_value pcu start_ts <value> gbl
equip pcu gbl

Values
Value type Integer (first GBL timeslot)

Valid range 1 to 31
Default value None
68P02901W23-Q 7-79
t391 Chapter 7: Device/function parameters
t391
Description
The t391 parameter specifies the frame relay default link integrity verification polling timer.
In GSR6, a new timer is added to improve the speed of getting GBL B-U. This timer
attempts to bring the GBL B-U after t391 plus 1 second. If not, it waits for the expiry
of the original t391 * n391 timer value and re-attempts to connect the GBL. If this is
also unsuccessful, then the GBL notifies pCA of the status.
Device/Function GBL
Syntax

modify_value pcu t391 <value> gbl
equip pcu gbl

7-80 68P02901W23-Q
Technical Description: BSS Command Reference t391
Values

Valid range 5 to 29
Default value 10
68P02901W23-Q 7-81
t392 Chapter 7: Device/function parameters
t392
Description
The t392 parameter is the frame relay default polling verification timer.
Device/Function GBL
Syntax

modify_value pcu t392 <value> gbl
equip pcu gbl

Values

Valid range 6 to 30
Default value 15
7-82 68P02901W23-Q
Technical Description: BSS Command Reference tcu_port
tcu_port
Description
The tcu_port parameter specifies the port to which a TCU is connected.

When the tcu_port parameter is modified outside SYSGEN mode, a warning message is displayed
enables the operator to chose to continue or abort the change.
Device/Function DRI
Dependencies None
Syntax

modify_value <location> tcu_port <value> dri

Values
Value type Integer

Valid range 0 to 5
Default value None
68P02901W23-Q 7-83
tcu_port Chapter 7: Device/function parameters
The range for this parameter is limited to 0 or 1 if the FOX/FMUX connection

parameter is specified as direct when the TCU is equipped.
7-84 68P02901W23-Q
Technical Description: BSS Command Reference transcoding_capability
transcoding_capability
Description
The transcoding_capability parameter specifies the functionality provided by a GDP

board. Basic and enhanced functionality are available.
Device/Function MSI
Dependencies None
Syntax

modify_value <location> transcoding_capability <value> msi
[<msi_id1>] [<msi_id2>] [<msi_id3>]

disp_equipment <location> msi [<msi_id1>] [<msi_id2>] [<msi_id3>]
Values
Value type Boolean

Valid range 0 Basic GDP function
1 Enhanced GDP function
Default value 0
68P02901W23-Q 7-85
tru_id Chapter 7: Device/function parameters
tru_id
Description
The tru_id parameter specifies up to six TRUs (TopCell Radio Units) in a TopCell site.
A value of 0 indicates this is a non-TopCell site.
When the tru_id parameter is modified outside SYSGEN mode, a warning message is displayed
enables the operator to chose to continue or abort the change.
Device/Function DRI
Dependencies None
Syntax

modify_value <location> tru_id <value> dri <dev_fun_id1>

Values
Value type Integer

Valid range 0 to 6
0 Non-TopCell unit
1 to 6 TopCell ID
Default value None
7-86 68P02901W23-Q
Technical Description: BSS Command Reference trx_pwr_red
trx_pwr_red
Description
The trx_pwr_red parameter specifies the TRX transmit power reduction value.
Device/Function RTF
Dependencies This parameter is used only if the cell_zone parameter is set to 1
(inner zone) and the inner_zone_alg parameter is set to 1 (power
based use algorithm).trx_pwr_red can be modified for an RTF that
is equipped in the inner_zone of a cell only.
The value of this parameter must be greater than or equal to the
value of max_tx_bts if inner_zone_alg is set to 1 (power based use
algorithm).
The Concentric Cells option must be unrestricted.
Syntax

modify_value <location> trx_pwr_red <value> rtf <id1> <id2> <id3>

disp_equipment <location> rtf [<id1> [<id2>] [<id3>]] [full]
68P02901W23-Q 7-87
trx_pwr_red Chapter 7: Device/function parameters
Values

Valid range -1 to 21 for PGSM, EGSM, and DCS1800
0 to 6 for M-Cellmicro sites
Default value None
Refer to Table 7-2, Table 7-3, Table 7-4, and Table 7-5 for additional information
about the values for this parameter.
Table 7-2 lists values for PGSM, EGSM and PCS 1900 sites.
Table 7-2 Values for PGSM, EGSM and PCS 1900 sites
Value Power Value Power

-1 45 dBm 10 23 dBm
0 43 dBm 11 21 dBm
1 41 dBm 12 19 dBm
2 39 dBm 13 17 dBm
3 37 dBm 14 15 dBm
4 35 dBm 15 13 dBm
5 33 dBm 16 11 dBm
6 31 dBm 17 9 dBm
7 29 dBm 18 7 dBm
8 27 dBm 19 5 dBm
9 25 dBm 20 3 dBm
21 1 dBm
Table 7-3 lists values for DCS 1800 sites.
Table 7-3 Values for DCS 1800 sites

-1 44 dBm 10 19 dBm
0 39 dBm 11 17 dBm
1 37 dBm 12 15 dBm
2 35 dBm 13 13 dBm
7-88 68P02901W23-Q
Technical Description: BSS Command Reference trx_pwr_red
Table 7-3 Values for DCS 1800 sites (Continued)

3 33 dBm 14 11 dBm
4 31 dBm 15 9 dBm
5 29 dBm 16 7 dBm
6 27 dBm 17 5 dBm
7 25 dBm 18 3 dBm
8 23 dBm 19 1 dBm
9 21 dBm 20 -1 dBm
21 -3 dBm
Table 7-4 lists values for PGSM and EGSM M-Cellmicro sites.
Table 7-4 Values for PGSM and EGSM M-Cellmicro sites

0 34 dBm 4 26 dBm
1 32 dBm 5 24 dBm
2 30 dBm 6 22 dBm
3 28 dBm
Table 7-5 lists values for DCS 1800 and PCS 1900 M-Cellmicro sites.
Table 7-5 Values for DCS 1800 and PCS 1900 M-Cellmicro sites

0 30 dBm 4 22 dBm
1 28 dBm 5 20 dBm
2 26 dBm 6 18 dBm
3 24 dBm
68P02901W23-Q 7-89
trx_pwr_red Chapter 7: Device/function parameters
7-90 68P02901W23-Q
Index
Index
A_LEV_HO . . . . . . . . . . . . . . 5-696, 5-704 alarm devices . . . . . . . . . . . . . . . . . 2-19

A_LEV_PC . . . . . . . . . . . . . . 5-698, 5-706 alarm_mode . . . . . . . . . . . . . . . . . . 2-47
A_PBGT_HO . . . . . . . . . . . . . 5-696, 5-762 alias . . . . . . . . . . . . . . . . . . . . . . 3-2
A_QUAL_HO . . . . . . . . . . . . . 5-710, 5-714 allow_8k_trau . . . . . . . . . . . . . . . . . 5-21
A_QUAL_PC . . . . . . . . . . . . . . . . 5-716 alt_qual_proc . . . . . . . . . . . . . . . . . 5-23
AC_CN . . . . . . . . . . . . . . . . . . . 5-113 ambiguous command response . . . . . . . . . 1-10
aci_error_clr_thresh . . . . . . . . . . . . . . 5-5 amr_bss_full_rate_enabled . . . . . . . . . . . 5-27
aci_error_gen_thresh . . . . . . . . . . . . . . 5-6 amr_bss_half_rate_enabled . . . . . . . . . . . 5-28
aci_error_inc . . . . . . . . . . . . . . . . . . 5-7 amr_dl_la_mode_chg_min . . . . . . . . . . . 5-29
adap_ho_alt_trigger_rxqual . . . . . . . . . . . 5-8 amr_dl_thresh_adjust . . . . . . . . . . . . . . 5-30
adap_ho_pbgt . . . . . . . . . . . . . . . . . 5-9 amr_fr_dl_la_enabled. . . . . . . . . . . . . . 5-31
adap_ho_rxlev . . . . . . . . . . . . . . . . . 5-11 amr_fr_ul_la_enabled. . . . . . . . . . . . . . 5-32
adap_ho_rxqual . . . . . . . . . . . . . . . . 5-12 amr_full_rate_enabled . . . . . . . . . . . . . 5-33
adap_trigger_hop_rxqual_dl. . . . . . . . . . . 5-13 amr_hr_dl_la_enabled . . . . . . . . . . . . . 5-35
adap_trigger_hop_rxqual_ul. . . . . . . . . . . 5-14 amr_hr_ul_la_enabled . . . . . . . . . . . . . 5-36
adap_trigger_pbgt . . . . . . . . . . . . . . . 5-15 amr_ms_high_cmr . . . . . . . . . . . . . . . 5-37
adap_trigger_pbgt_nbr . . . . . . . . . 2-398, 5-16 amr_ms_high_rxqual . . . . . . . . . . . . . . 5-38
adap_trigger_rxlev_dl . . . . . . . . . . . . . 5-17 amr_ms_low_cmr . . . . . . . . . . . . . . . 5-39
adap_trigger_rxlev_ul . . . . . . . . . . . . . 5-18 amr_ms_low_rxqual . . . . . . . . . . . . . . 5-40
adap_trigger_rxqual_dl . . . . . . . . . . . . . 5-19 amr_ms_monitor_period . . . . . . . . . . . . 5-41
adap_trigger_rxqual_ul . . . . . . . . . . . . . 5-20 antenna_select . . . . . . . . . . . . . . . . . 7-5
add_access_class . . . . . . . . . . . . . . . . 6-2 assess . . . . . . . . . . . . . . . . . . . . . 2-49
add_cell . . . . . . . . . . . . . . . . . . . . 2-21 assign_successful. . . . . . . . . . . . . . . . 6-3
add_conn . . . . . . . . . . . . . . . . . . . 2-33 ATT . . . . . . . . . . . . . . . . . . . . . . 5-43
add_neighbor . . . . . . . . . . . . . . . . . 2-35 attach_detach . . . . . . . . . . . . . . . . . 5-42
add_nsvc . . . . . . . . . . . . . . . . . . . 2-43 auto_dl_dur . . . . . . . . . . . . . . . . . . 6-5
add_rtf_path . . . . . . . . . . . . . . . . . . 2-45 auto_rf_loss_trace . . . . . . . . . . . . . . . 5-44
adj_chan_intf_test . . . . . . . . . . . . . . 2-398
ba_alloc_proc . . . . . . . . . . . . . . . . . 5-46 ber_oos_mon_period . . . . . . . . . . . . . . 7-7

ba_bcch . . . . . . . . . . . . . . . . . . . 2-398 ber_restore_mon_period . . . . . . . . . . . . 7-9
ba_gprs . . . . . . . . . . . . . . . . . . . 2-398 bounce_protect_cong_tmr. . . . . . . . . . . . 6-10
band_preference . . . . . . . . . . . . . . . . 5-48 bounce_protect_margin . . . . . . . . . . . . . 5-55
band_preference_mode . . . . . . . . . . . . . 5-50 bounce_protect_qual_tmr . . . . . . . . . . . . 6-11
bcch_info . . . . . . . . . . . . . . . . . . . 6-6 bs_ag_blks_res . . . . . . . . . . . . . . . . . 5-56
bep_period . . . . . . . . . . . . . . . . . . . 6-8 BS_AG_BLKS_RES . . . . . . . . . . . . . . 5-57
bep_period2 . . . . . . . . . . . . . . . . . . 6-9 bs_pa_mfrms. . . . . . . . . . . . . . . . . . 5-58
ber_loss_daily . . . . . . . . . . . . . . . . . 5-53 BS_PA_MFRMS . . . . . . . . . . . . . . . . 5-59
ber_loss_hourly . . . . . . . . . . . . . . . . 5-54 bs_pag_blks_res . . . . . . . . . . . . . . . . 5-60
68P02901W23-Q IX-1
Index
bs_pbcch_blks . . . . . . . . . . . . . . . . . 5-62 bssgp_reset_retries . . . . . . . . . . . . . . . 5-76

bs_pcc_chans . . . . . . . . . . . . . . . . . 5-64 bssgp_t1_timer . . . . . . . . . . . . . . . . . 6-17
bs_prach_blks . . . . . . . . . . . . . . . . . 5-65 bssgp_t2_timer . . . . . . . . . . . . . . . . . 6-19
BS_TXPWR_RED . . . . . . . . . . . . . . 5-503 bssgp_unblock_retries . . . . . . . . . . . . . 5-77
bsc_audit . . . . . . . . . . . . . . . . . . . 6-12 bssmap_t1 . . . . . . . . . . . . . . . . . . . 6-21
bsc_audit_response . . . . . . . . . . . . . . . 6-13 bssmap_t10 . . . . . . . . . . . . . . . . . . 6-22
bsc_cbc_operator . . . . . . . . . . . . . . . . 7-11 bssmap_t11 . . . . . . . . . . . . . . . . . . 6-24
bsc_type . . . . . . . . . . . . . . . . . . . . 5-66 bssmap_t13 . . . . . . . . . . . . . . . . . . 6-26
bsic . . . . . . . . . . . . . . . . . . . . . . 5-68 bssmap_t19 . . . . . . . . . . . . . . . . . . 6-28
BSIC . . . . . . . . . . . . . . . . . . . . . 5-70 bssmap_t20 . . . . . . . . . . . . . . . . . . 6-29
BSIC_NC(n) . . . . . . . . . . . . . . . . . . 5-70 bssmap_t4 . . . . . . . . . . . . . . . . . . . 6-30
BSP bssmap_t7 . . . . . . . . . . . . . . . . . . . 6-32
max_mtls . . . . . . . . . . . . . . 5-487, 7-57 bssmap_t8 . . . . . . . . . . . . . . . . . . . 6-34
BSS bssmap_tqh0 . . . . . . . . . . . . . . . . . . 6-36
ne_id . . . . . . . . . . . . . . . . . . . . 7-68 BTP
BSS Initialization Process max_dris . . . . . . . . . . . . . . . . . . 7-54
about . . . . . . . . . . . . . . . . . . . . 1-2 bts_audit. . . . . . . . . . . . . . . . . . . . 6-38
bss_egsm_alm_allowed . . . . . . . . . . . . . 5-71 bts_audit_response . . . . . . . . . . . . . . . 6-40
bss_msc_overload_allowed . . . . . . . . . . . 5-72 bts_escalation . . . . . . . . . . . . . . . . . 6-41
bss_overload_control . . . . . . . . . . . . . . 6-14 bts_p_con_ack . . . . . . . . . . . . . . . . . 5-78
BSSGP T1 . . . . . . . . . . . . . . . . . . . 6-18 bts_p_con_interval . . . . . . . . . . . . . . . 5-80
bssgp_block_retries. . . . . . . . . . . . . . . 5-73 bts_power_control_allowed . . . . . . . . . . . 5-82
bssgp_cbl_bit . . . . . . . . . . . . . . . . . 5-74 bts_txpwr_max_inner. . . . . . . . . . 5-84, 5-387
bssgp_fc_period_c . . . . . . . . . . . . . . . 6-15 bts_type . . . . . . . . . . . . . . . . . . . . 5-89
bssgp_racap_retries. . . . . . . . . . . . . . . 5-75 bvci . . . . . . . . . . . . . . . . . . . . . . 5-91
C2. . . . . . . . . . . . . . . . . . . . . . 5-784 cbch_1. . . . . . . . . . . . . . . . . . . . . 6-44

c31_hyst . . . . . . . . . . . . . . . . . . . 5-154 cbch_2. . . . . . . . . . . . . . . . . . . . . 6-45
c32_qual. . . . . . . . . . . . . . . . . . . 5-156 cbch_3. . . . . . . . . . . . . . . . . . . . . 6-46
cab . . . . . . . . . . . . . . . . . . . . . . 7-12 cbch_enabled . . . . . . . . . . . . . . . . 5-104
int_antenna . . . . . . . . . . . . . . . . . 7-45 CBL
int_hdsl_modem . . . . . . . . . . . . . . . 7-46 bsc_cbc_operator . . . . . . . . . . . . . . 7-11
cabinet_type . . . . . . . . . . . . . . . . . . 7-12 cbc_operator. . . . . . . . . . . . . . . . . 7-16
cage_audit . . . . . . . . . . . . . . . . . . . 2-54 cbs_outage_cntr . . . . . . . . . . . . . . . 5-105
Call Processing ccch_conf . . . . . . . . . . . . . . . . . . 5-106
about . . . . . . . . . . . . . . . . . . . . 1-4 bs_ag_blks_res dependency. . . . . . . . . . 5-56
call_trace_options . . . . . . . . . . . . . . . 5-93 CCCH_CONF . . . . . . . . . . . . . . . . 5-108
called_pci . . . . . . . . . . . . . . . . . . . 5-95 CCCH_LOAD_IND_PERIOD . . . . . . . . 5-110
calling_pci . . . . . . . . . . . . . . . . . . . 5-96 ccch_load_period. . . . . . . . . . . . . . . 5-109
carrier_disable_time . . . . . . . . . . . . . . 5-97 CCCH_SDCCH_COMB . . . . . . . . . . . 5-108
carrier_free_immediate . . . . . . . . . . . . . 6-42 CCITT Q.713 . . . . . . . . . . . . . . . . . 5-95
carriers_ins_pwr_fail . . . . . . . . . . . . . . 5-98 CE_RE_HYS . . . . . . . . . . . . . . . . 5-119
Caution, commands cell identity
Commands to be used with caution . . . . . . 1-7 UTRAN . . . . . . . . . . . . . . . . . . 5-322
Caution, parameters CELL_BAR_ACCESS . . . . . . . . . . . . 5-115
Parameters to be used with caution . . . . . . 1-8 cell_bar_access_class . . . . . . . . . . . . . 5-111
cavity . . . . . . . . . . . . . . . . . . . . . 7-15 cell_bar_access_switch . . . . . . . . . . . . 5-114
cbc_fast_select . . . . . . . . . . . . . . . . 5-100 cell_bar_qualify . . . . . . . . . . . . . . . 5-116
cbc_intface_vers . . . . . . . . . . . . . . . 5-102 cell_name . . . . . . . . . . . . . . . . . . . 2-58
cbc_operator . . . . . . . . . . . . . . . . . . 7-16 cell_reselect_hysteresis . . . . . . . . . 5-118, 5-270
cbc_vbind_cntr. . . . . . . . . . . . . . . . 5-103
IX-2 68P02901W23-Q
Technical Description: BSS Command Reference Index
cell_reselect_offset . . . . . . . . . . . . . . 5-120 clkx0 . . . . . . . . . . . . . . . . . . . . . 7-21

CELL_RESELECT_OFFSET . . . . . . . . . 5-121 clkx1 . . . . . . . . . . . . . . . . . . . . . 7-23
cell_reselect_param_ind . . . . . . . . . . . 5-122 clkx2 . . . . . . . . . . . . . . . . . . . . . 7-25
CELL_RESELECT_PARAM_IND . . . . . . 5-123 CLM_MTA1 . . . . . . . . . . . . . . . . . . 6-54
cell_zone . . . . . . . . . . . . . . . . . . . 7-17 CLM_MTJ1 . . . . . . . . . . . . . . . . . 6-210
chan_alloc_priority . . . . . . . . . . . 5-124, 7-19 CLM_SPI_TIMER . . . . . . . . . . . . . . 6-185
channel_ack . . . . . . . . . . . . . . . . . . 6-47 clm_t_stat_info. . . . . . . . . . . . . . . . 6-213
channel_reconfiguration_switch . . . . . . . . 5-125 CLM_T1 . . . . . . . . . . . . . . . . . . . 6-21
channel_teardown . . . . . . . . . . . . . . . 6-49 CLM_T13 . . . . . . . . . . . . . . . . . . . 6-27
chg_a5_alg_pr . . . . . . . . . . . . . . . . . 2-69 CLM_T19 . . . . . . . . . . . . . . . . . . . 6-28
chg_acs_params . . . . . . . . . . . . . . . . 2-61 CLM_T20 . . . . . . . . . . . . . . . . . . . 6-29
chg_audit_sched . . . . . . . . . . . . . . . . 2-72 CLM_T4 . . . . . . . . . . . . . . . . . . . 6-31
chg_cell_element. . . . . . . . . . . . . . . . 2-77 coincident_cell . . . . . . . . . . . . . 5-137, 5-139
chg_cell_id . . . . . . . . . . . . . . . . . . 2-81 coincident_mb . . . . . . . . . . . . . . . . 5-139
chg_csfp . . . . . . . . . . . . . . . . . . . . 2-85 coincident_offset . . . . . . . . . . . . . . . 5-141
chg_dte . . . . . . . . . . . . . . . . . . . . 2-88 combiner_address . . . . . . . . . . . . . . . 7-27
chg_eas_alarm . . . . . . . . . . . . . . . . . 2-92 combiner_id . . . . . . . . . . . . . . . . . . 7-28
chg_element . . . . . . . . . . . . . . . . . . 2-95 combining_type . . . . . . . . . . . . . . . . 7-29
chg_element (statistics application) . . . . . . . 4-27 command response
chg_hop_params . . . . . . . . . . . . . . . 2-102 ambiguous. . . . . . . . . . . . . . . . . . 1-10
chg_ksw_config . . . . . . . . . . . . . . . 2-111 Command Security Levels . . . . . . . . . . . 1-5
chg_level . . . . . . . . . . . . . . . . . . 2-115 command types . . . . . . . . . . . . . . . . 1-6
chg_password . . . . . . . . . . . . . . . . 2-117 concentric cells
chg_rtf_freq . . . . . . . . . . . . . . . . . 2-120 inner_zone_alg . . . . . . . . . . . . . . 5-385
chg_severity . . . . . . . . . . . . . . . . . 2-125 config_packet_size
chg_smscb_msg . . . . . . . . . . . . . . . 2-127 in BSS View at OMC GUI . . . . . . . . . 2-144
data_coding_scheme . . . . . . . . . . . . 2-128 config_window_size
chg_stat_prop . . . . . . . . . . . . . . . . . 4-5 in BSS View at OMC GUI . . . . . . . . . 2-144
chg_throttle . . . . . . . . . . . . . . . . . 2-133 configure_csfp . . . . . . . . . . . . . . . . 2-153
chg_time. . . . . . . . . . . . . . . . . . . 2-135 confusion_msg_allowed . . . . . . . . . . . 5-142
chg_ts_usage. . . . . . . . . . . . . . . . . 2-138 congest_at_source . . . . . . . . . . . . . . 5-144
chg_x25config . . . . . . . . . . . . . . . . 2-144 congest_at_target . . . . . . . . . . . . . . . 5-146
cic_block_thresh . . . . . . . . . . . . . . . 5-127 congest_ho_margin . . . . . . . . . . . 2-398, 5-147
cic_error_clr_thresh . . . . . . . . . . . . . 5-129 connection_code . . . . . . . . . . . . . . . 2-155
cic_error_gen_thresh . . . . . . . . . . . . . 5-130 copy_cell . . . . . . . . . . . . . . . . . . 2-157
cic_error_inc . . . . . . . . . . . . . . . . . 5-131 copy_path . . . . . . . . . . . . . . . . . . 2-163
cic_unblock_thresh . . . . . . . . . . . . . . 5-132 Counter statistics . . . . . . . . . . . . . . . . 4-3
cic_validation . . . . . . . . . . . . . . . . 5-134 cp_option_reset_ckt . . . . . . . . . . . . . 5-148
ciph_mode_rej_allowed. . . . . . . . . . . . 5-135 cp_option_rr_status. . . . . . . . . . . . . . 5-149
cipher_comp_ms . . . . . . . . . . . . . . . . 6-50 cr_calling . . . . . . . . . . . . . . . . . . 5-150
ciphering_successful . . . . . . . . . . . . . . 6-52 CRM
circuit_reset_ack . . . . . . . . . . . . . . . . 6-54 rr_t3111_sd . . . . . . . . . . . . . . . . 6-165
clear_cal_data . . . . . . . . . . . . . . . . 2-147 rr_t3212 . . . . . . . . . . . . . . . . . . 6-169
clear_command . . . . . . . . . . . . . . . . 6-56 ct_flow_control_hi_level . . . . . . . . . . . 5-151
clear_database . . . . . . . . . . . . . . . . 2-149 ct_flow_control_lo_level . . . . . . . . . . . 5-152
clear_gclk_avgs . . . . . . . . . . . . . . . 2-151 ct_flow_control_msc_trace . . . . . . . . . . 5-153
clk_src_fail_reset_period . . . . . . . . . . . 5-136
data_coding_scheme . . . . . . . . . . . . . 2-128 dealloc_inact . . . . . . . . . . . . . . . . . . 6-58

data_qual_enabled . . . . . . . . . . . . . . 5-158 decision_1_dl_rxlev_av_h . . . . . . . . . . 5-161
database parameter types . . . . . . . . . . . . 1-6 decision_1_dl_rxlev_av_ih . . . . . . . . . . 5-162
68P02901W23-Q IX-3
Index
decision_1_dl_rxqual_av_h . . . . . . . . . . 5-164 disp_csfp_status . . . . . . . . . . . . . . . 2-228

decision_1_dl_rxqual_av_p . . . . . . . 5-163, 5-165 disp_dte . . . . . . . . . . . . . . . . . . . 2-230
decision_1_n1 . . . . . . . . . . . . . . . . 5-166 disp_element . . . . . . . . . . . . . . . . . 2-232
decision_1_n2 . . . . . . . . . . . . . . . . 5-168 disp_enable_stat . . . . . . . . . . . . . . . . 4-10
decision_1_n3 . . . . . . . . . . . . . . . . 5-170 disp_equipment . . . . . . . . . . . . . . . 2-235
decision_1_n4 . . . . . . . . . . . . . . . . 5-172 disp_exp_config . . . . . . . . . . . . . . . 2-245
decision_1_n5 . . . . . . . . . . . . . . . . 5-174 disp_flash . . . . . . . . . . . . . . . . . . 2-247
decision_1_n6 . . . . . . . . . . . . . . . . 5-176 disp_gclk_avgs. . . . . . . . . . . . . . . . 2-249
decision_1_n7 . . . . . . . . . . . . . . . . 5-178 disp_gclk_cal . . . . . . . . . . . . . . . . 2-251
decision_1_n8 . . . . . . . . . . . . . . . . 5-180 disp_gsm_cells . . . . . . . . . . . . . . . . 2-254
decision_1_ncell_rxlev_av_h_calc. . . . . . . 5-182 disp_hdlc . . . . . . . . . . . . . . . . . . 2-257
decision_1_p_bgt_rxlev_av_h . . . . . . . . . 5-183 disp_hopping. . . . . . . . . . . . . . . . . 2-260
decision_1_p1 . . . . . . . . . . . . . . . . 5-166 disp_interval . . . . . . . . . . . . . . . . . . 4-14
decision_1_p2 . . . . . . . . . . . . . . . . 5-168 disp_level . . . . . . . . . . . . . . . . . . 2-265
decision_1_p3 . . . . . . . . . . . . . . . . 5-170 disp_link. . . . . . . . . . . . . . . . . . . 2-266
decision_1_p4 . . . . . . . . . . . . . . . . 5-172 disp_link_usage . . . . . . . . . . . . . . . 2-268
decision_1_p5 . . . . . . . . . . . . . . . . 5-174 disp_mms_ts_usage . . . . . . . . . . . . . 2-270
decision_1_p6 . . . . . . . . . . . . . . . . 5-176 disp_neighbor . . . . . . . . . . . . . . . . 2-282
decision_1_p7 . . . . . . . . . . . . . . . . 5-178 disp_nsvc . . . . . . . . . . . . . . . . . . 2-288
decision_1_p8 . . . . . . . . . . . . . . . . 5-180 disp_options . . . . . . . . . . . . . . . . . 2-291
decision_1_tim_adv_av_alg . . . . . . . . . . 5-184 disp_processor . . . . . . . . . . . . . . . . 2-295
decision_1_ul_rxlev_av_h . . . . . . . . . . 5-185 disp_relay_contact . . . . . . . . . . . . . . 2-299
decision_1_ul_rxlev_av_ih . . . . . . . . . . 5-186 disp_rtf_channel . . . . . . . . . . . . . . . 2-301
decision_1_ul_rxlev_av_p . . . . . . . . . . 5-187 disp_rtf_path . . . . . . . . . . . . . . . . . 2-308
decision_1_ul_rxqual_av_h . . . . . . . . . . 5-188 disp_severity . . . . . . . . . . . . . . . . . 2-311
decision_1_ul_rxqual_av_p . . . . . . . . . . 5-189 disp_site . . . . . . . . . . . . . . . . . . . 2-313
decision_alg_type . . . . . . . . . . . . . . 5-190 disp_stat_prop . . . . . . . . . . . . . . . . . 4-16
del_act_alarm . . . . . . . . . . . . . . . . 2-166 disp_stats . . . . . . . . . . . . . . . . . . . 4-21
del_cell . . . . . . . . . . . . . . . . . . . 2-169 disp_throttle . . . . . . . . . . . . . . . . . 2-314
del_conn. . . . . . . . . . . . . . . . . . . 2-172 disp_time . . . . . . . . . . . . . . . . . . 2-316
del_neighbor . . . . . . . . . . . . . . . . . 2-174 disp_trace_call . . . . . . . . . . . . . . . . 2-318
del_nsvc . . . . . . . . . . . . . . . . . . . 2-178 disp_traffic. . . . . . . . . . . . . . . . . . 2-321
del_rtf_path . . . . . . . . . . . . . . . . . 2-180 disp_transcoding . . . . . . . . . . . . . . . 2-324
del_smscb_msg . . . . . . . . . . . . . . . 2-182 disp_version . . . . . . . . . . . . . . . . . 2-326
delay_dl_rel_dur . . . . . . . . . . . . . . . . 6-60 disp_x25config. . . . . . . . . . . . . . . . 2-327
device IDs . . . . . . . . . . . . . . . . . . . 2-8 Distribution statistics . . . . . . . . . . . . . . 4-3
device indices . . . . . . . . . . . . . . . . . 1-23 disuse_cnt_hreqave . . . . . . . . . . . . . . 5-194
device related commands . . . . . . . . . . . . 2-3 dl_audio_lev_offset. . . . . . . . . . . . . . 5-195
device_audit . . . . . . . . . . . . . . . . . 2-185 dl_dtx_voice_data . . . . . . . . . . . . . . 5-197
DHP dl_rxlev_ho_allowed . . . . . . . . . . . . . 5-198
max_dris . . . . . . . . . . . . . . . . . . 7-54 dl_rxqual_ho_allowed . . . . . . . . . . . . 5-200
diagnose_device . . . . . . . . . . . . . . . 2-190 dnlk_vad_dtx . . . . . . . . . . . . . . . . 5-202
direct_inner_zone_threshold . . . . . . . . . 5-193 downlink_sync_timer . . . . . . . . . . . . . . 6-61
disp_a5_alg_pr . . . . . . . . . . . . . . . . 2-192 dpc . . . . . . . . . . . . . . . . . . . . . 5-204
disp_acs . . . . . . . . . . . . . . . . . . . 2-194 DPC . . . . . . . . . . . . . . . . . . . . . 5-205
disp_act_alarm . . . . . . . . . . . . . . . . 2-196 dr_allowed . . . . . . . . . . . . . . . 2-398, 5-206
disp_bss . . . . . . . . . . . . . . . . . . . 2-199 dr_chan_mode_modify . . . . . . . . . . . . 5-207
disp_cal_data . . . . . . . . . . . . . . . . 2-201 dr_ho_during_assign . . . . . . . . . . . . . 5-209
disp_cbch_state . . . . . . . . . . . . . . . 2-203 dr_preference . . . . . . . . . . . . . . . . 5-211
disp_cell . . . . . . . . . . . . . . . . . . . 2-206 dr_standard_congest . . . . . . . . . . . . . 5-213
disp_cell_map . . . . . . . . . . . . . . . . 2-211 DRI
disp_cell_status . . . . . . . . . . . . . . . 2-214 antenna_select . . . . . . . . . . . . . . 7-5, 7-29
disp_conn . . . . . . . . . . . . . . . . . . 2-224 cab . . . . . . . . . . . . 7-12, 7-31, 7-45 to 7-46
disp_csfp . . . . . . . . . . . . . . . . . . 2-226 cavity . . . . . . . . . . . . . . . . . . . . 7-15
IX-4 68P02901W23-Q
DRI (contd.) Dual Band Cells feature. . . . . . . . . . . . 2-373

fm_cell_type. . . . . . . . . . . . . . . . . 7-34 dual_band_offset . . . . . . . . . . . . . . . 5-217
opto_reporting . . . . . . . . . . . . . 7-69, 7-71 Duration statistics . . . . . . . . . . . . . . . 4-3
slot . . . . . . . . . . . . . . . . . . . . . 7-78 dyn_step_adj . . . . . . . . . . . . . . . . . 5-218
tcu_port . . . . . . . . . . . . . . . . . . . 7-83 dyn_step_adj_fmpr . . . . . . . . . . . . . . 5-219
tru_id . . . . . . . . . . . . . . . . . . . . 7-86 DYNET
dri_density . . . . . . . . . . . . . . . . . . . 7-31 shared_timeslots . . . . . . . . . . . . . . . 7-77
DTX . . . . . . . . . . . . . . . . . . . . 5-216 dynet_retry_time . . . . . . . . . . . . . . . . 6-63
dtx_required . . . . . . . . . . . . . . . . . 5-215 dynet_tchs_reserved . . . . . . . . . . . . . 5-220
eac_mode . . . . . . . . . . . . . . . . . . 5-222 equip (contd.)

Early MMI interaction . . . . . . . . . . . . . 1-3 CAGE. . . . . . . . . . . . . . . . . . . 2-343
early_classmark_delay . . . . . . . . . . . . . 6-65 CBL . . . . . . . . . . . . . . . . . . . 2-344
early_classmark_sending . . . . . . . . . . . 5-224 CIC . . . . . . . . . . . . . . . . . . . . 2-345
EAS COMB . . . . . . . . . . . . . . . . . . 2-347
disp_relay_contact . . . . . . . . . . . . . 2-299 CSFP . . . . . . . . . . . . . . . . . . . 2-347
opto_reporting . . . . . . . . . . . . . . . . 7-69 Devices . . . . . . . . . . . . . . . . . . 2-338
eas_alarm . . . . . . . . . . . . . . . . . . 5-226 DHP . . . . . . . . . . . . . . . . . . . 2-347
eas_alarm_type. . . . . . . . . . . . . . . . 5-227 DPROC . . . . . . . . . . . . . . . . . . 2-348
eas_report_opto . . . . . . . . . . . . . . . 5-228 DRI (InCell sites) . . . . . . . . . . . . . 2-349
eas_severity . . . . . . . . . . . . . . . . . 5-229 DRI (M-Cell and Horizonmacro sites) . . . . 2-350
EC . . . . . . . . . . . . . . . . . . . . . 5-242 DYNET . . . . . . . . . . . . . . . . . . 2-353
efr_enabled . . . . . . . . . . . . . . . . . 5-231 EAS (InCell sites) . . . . . . . . . . . . . 2-354
egprs_init_dl_cs . . . . . . . . . . . . . . . 5-233 EAS (M-Cell sites) . . . . . . . . . . . . . 2-355
egprs_init_ul_cs . . . . . . . . . . . . . . . 5-235 equipage hierachy charts . . . . . . . . . . 2-333
egsm_bcch_sd . . . . . . . . . . . . . . . . 5-237 Functions . . . . . . . . . . . . . . . . . 2-371
egsm_handover_threshold . . . . . . . . . . 5-239 GBL . . . . . . . . . . . . . . . . . . . 2-356
emerg_reserved . . . . . . . . . . . . . . . . 6-66 GCLK. . . . . . . . . . . . . . . . . . . 2-357
emergency_class_switch . . . . . . . . . . . 5-241 GDS . . . . . . . . . . . . . . . . . . . 2-358
EN_BS_PC . . . . . . . . . . . . . . . . . . 5-83 GPROC . . . . . . . . . . . . . . . . . . 2-359
en_incom_ho. . . . . . . . . . . . . . . . . 5-243 GPRS equipage chart. . . . . . . . . . . . 2-337
EN_INCOM_HO. . . . . . . . . . . . . . . 5-399 GSL. . . . . . . . . . . . . . . . . . . . 2-359
EN_INTER_HO . . . . . . . . . . . . . . . 5-391 InCell equipage chart. . . . . . . . . . . . 2-335
EN_INTRA_HO . . . . . . . . . . . . . . . 5-399 KSW . . . . . . . . . . . . . . . . . . . 2-360
EN_MS_PC . . . . . . . . . . . . . . . . . 5-523 LCF. . . . . . . . . . . . . . . . . . . . 2-371
EN_PBGT_HO . . . . . . . . . . . . . . . 5-629 LMTL. . . . . . . . . . . . . . . . . . . 2-360
EN_Q_OWED . . . . . . . . . . . . . . . . 5-633 M-Cell and Horizonmacro equipage chart . . 2-336
EN_RXLEV_HO. . . . . . . . . . . . 5-199, 5-821 MSI . . . . . . . . . . . . . . . . . 2-361, 2-363
EN_RXQUAL_HO. . . . . . . . . . . 5-201, 5-823 MSI (M-Cell Sites Only) . . . . . . . . . . 2-363
EN_SDCCH_HO. . . . . . . . . . . . . . . 5-729 MSI (PCU only) . . . . . . . . . . . . . . 2-364
enhanced_relief . . . . . . . . . . . . . . . 5-245 MTL . . . . . . . . . . . . . . . . . . . 2-365
entering hexadecimal values OMF . . . . . . . . . . . . . . . . . . . 2-372
ambiguous. . . . . . . . . . . . . . . . . . 1-10 OML . . . . . . . . . . . . . . . . . . . 2-366
eop_enabled . . . . . . . . . . . . . . . . . 5-246 PATH . . . . . . . . . . . . . . . . . . . 2-366
equip . . . . . . . . . . . . . . . . . . . . 2-329 PCU . . . . . . . . . . . . . . . . . . . 2-368
ABSS . . . . . . . . . . . . . . . . . . . 2-338 PSP . . . . . . . . . . . . . . . . . . . . 2-369
AXCDR . . . . . . . . . . . . . . . . . . 2-338 RSL. . . . . . . . . . . . . . . . . . . . 2-369
BSP . . . . . . . . . . . . . . . . . . . . 2-339 RTF . . . . . . . . . . . . . . . . . . . . 2-372
BSS . . . . . . . . . . . . . . . . . . . . 2-339 RXCDR . . . . . . . . . . . . . . . 2-334, 2-369
BTP. . . . . . . . . . . . . . . . . . . . 2-339 SITE . . . . . . . . . . . . . . . . . . . 2-370
CAB . . . . . . . . . . . . . . . . . . . 2-340
68P02901W23-Q IX-5
Index
XBL . . . . . . . . . . . . . . . . . . . 2-370
equip/unequip matrix . . . . . . . . . . . . . . 2-17
erc_ta_priority . . . . . . . . . . . . . . . . 5-247
ext_ho_allocation . . . . . . . . . . . . . . . 6-68
ext_range_cell . . . . . . . . . . . . . . . . 5-248
ext_rtry_cand_prd . . . . . . . . . . . . . . . 6-69
ext_timeslots . . . . . . . . . . . . . . . . . . 7-32
extended_paging_active . . . . . . . . . . . 5-250
FC_T1. . . . . . . . . . . . . . . . . . . . . 6-71 frequency_type, cabinet. . . . . . . . . . . . . 7-36

FC_T2. . . . . . . . . . . . . . . . . . . . . 6-73 frequency_type, cell . . . . . . . . . . . . . 5-255
fdd_arfcn . . . . . . . . . . . . . . . . . . 2-399 frequency_types_allowed . . . . . . . . . . . 2-378
fdd_qmin . . . . . . . . . . . 5-252, 5-380, 5-382 full_pwr_rfloss . . . . . . . . . . . . . . . . 5-257
fdd_qoffset. . . . . . . . . . . . . . . 5-160, 5-253 function ids requirements . . . . . . . . . . . . 2-15
feature function related commands . . . . . . . . . . . 2-14
22064 . . 2-78, 2-80, 2-159 to 2-160, 2-214, 2-221,
2-301, 2-305 to 2-306, 2-338, 2-377, 2-406 to 2-407,
2-472, 5-21, 5-24 to 5-25, 5-127, 5-132, 5-222, 5-254,
5-319, 5-323, 5-325, 5-334, 5-371 to 5-372, 5-374,
5-384, 5-413, 5-421, 5-426, 5-434, 5-439, 5-447,
5-452, 5-460, 5-552, 5-656, 5-813, 5-817
24513 . . . . . . . . . . . . . . . . . . . 2-404
24660, 24661 . . . . . . . . . . . 5-491, 5-533,
5-688 to 5-689, 5-691, 6-14, 6-171
flow_control_t1 . . . . . . . . . . . . . . . . 6-70
flow_control_t2 . . . . . . . . . . . . . . . . 6-72
FM
ts_alloc_flag . . . . . . . . . . . . . . . . 5-795
fm_cell_type . . . . . . . . . . . . . . . . . . 7-34
force_hr_usage . . . . . . . . . . . . . . . . 5-254
Gauge statistics . . . . . . . . . . . . . . . . 4-3 gprs_access_min . . . . . . . . . . . . . . . 5-306

Interval expiry . . . . . . . . . . . . . . . . 4-3 gprs_alarm_time . . . . . . . . . . . . . . . 5-266
Threshold event reporting. . . . . . . . . . . 4-3 gprs_bs_cv_max . . . . . . . . . . . . . . . 5-267
GBL gprs_cell_cgt_thr . . . . . . . . . . . . . . . 5-268
n391 . . . . . . . . . . . . . . . . . . . . 7-64 gprs_com_ms_class . . . . . . . . . . . . . 5-272
start_ts . . . . . . . . . . . . . . . . . . . 7-79 gprs_cr_margin . . . . . . . . . . . . . . . 5-273
t391 . . . . . . . . . . . . . . . . . . . . . 7-80 gprs_dl_pwr_mode . . . . . . . . . . . . . . 5-275
t392 . . . . . . . . . . . . . . . . . . 7-65, 7-82 gprs_drx_timer_max . . . . . . . . . . . . . 5-277
t393 . . . . . . . . . . . . . . . . . . . . . 7-66 gprs_enabled . . . . . . . . . . . . . . 5-279, 5-584
gbl_thrput_period . . . . . . . . . . . . . . . 6-74 gprs_intra_ho_allowed . . . . . . . . . . . . 5-281
gci_error_clr_thresh . . . . . . . . . . . . . 5-258 gprs_mac_mode . . . . . . . . . . . . . . . 5-283
gci_error_gen_thresh . . . . . . . . . . . . . 5-259 gprs_max_ul_ts . . . . . . . . . . . . . . . 5-284
gci_error_inc. . . . . . . . . . . . . . . . . 5-260 gprs_min_prr_blks . . . . . . . . . . . . . . 5-285
gclk_cal_mode . . . . . . . . . . . . . . . . 2-381 gprs_ms_pan_dec . . . . . . . . . . . . . . 5-286
gclk_qwarm_flag . . . . . . . . . . . . . . . 5-261 gprs_ms_pan_inc. . . . . . . . . . . . . . . 5-288
global_reset_repetitions. . . . . . . . . . . . 5-262 gprs_ms_pan_max . . . . . . . . . . . . . . 5-290
gproc_slots . . . . . . . . . . . . . . . . . 5-264 gprs_ms_txpwr_max_cch . . . . . . . . . . . 5-292
IX-6 68P02901W23-Q
gprs_network_operation_mode . . . . . . . . 5-295 gprs_t3192 . . . . . . . . . . . . . . . . . . . 6-79

gprs_num_pmrs . . . . . . . . . . . . . . . 5-297 gprs_ts_config_alg . . . . . . . . . . . . . . 5-312
gprs_pb . . . . . . . . . . . . . . . . . . . 5-299 gprs_ul_dl_bias . . . . . . . . . . . . . . . 5-314
gprs_pc_alpha . . . . . . . . . . . . . . . . 5-300 group_block_unblock_allowed . . . . . . . . 5-315
gprs_pc_meas_chan . . . . . . . . . . . . . 5-301 gsl_lcf_mapping . . . . . . . . . . . . . . . 5-317
gprs_penalty_time . . . . . . . . . . . . . . . 6-75 gsm cell id . . . . . . . . . . . . . . . . 2-22, 2-81
gprs_reconfig_thresh_idle_tch. . . . . . . . . 5-303 GSM Parameter
gprs_reselect_offset . . . . . . . . . . . . . 5-304 MS_TXPWR_MAX(n) . . . . . . . . . . . 5-529
gprs_sched_beta . . . . . . . . . . . . . . . 5-308 gsm_bss_half_rate_enabled . . . . . . . . . . 5-319
gprs_sig_bvci . . . . . . . . . . . . . . . . 5-309 gsm_cell_id_format . . . . . . . . . . . . . 5-321
gprs_smg30_t3192 . . . . . . . . . . . . . . . 6-77 gsm_half_rate_enabled . . . . . . . . . . . . 5-323
gprs_t3168 . . . . . . . . . . . . . . . . . . . 6-78
half_rate_enabled . . . . . . . . . . . . . . 5-325 hexadecimal values . . . . . . . . . . . . . . . 1-10

HAND_REQ_REJECT . . . . . . . . . . . . 5-333 history . . . . . . . . . . . . . . . . . . . . . 3-6
handover_power_level . . . . . . . . . . . . 5-327 ho_ack. . . . . . . . . . . . . . . . . . . . . 6-82
handover_recognized_period . . . . . . . . . . 6-80 ho_allocation. . . . . . . . . . . . . . . . . . 6-84
handover_required_current_ch . . . . . . . . 5-330 ho_complete . . . . . . . . . . . . . . . . . . 6-85
handover_required_reject_switch . . . . . . . 5-332 ho_exist_congest . . . . . . . . . . . . . . . 5-349
handover_required_sp_ver_used ho_margin_cell. . . . . . . . . . . . . . . . 2-398
22064 . . . . . . . . . . . . . . . . . . . 5-334 ho_margin_def . . . . . . . . . . . . . . . . 5-351
hcs_thr . . . . . . . . . . . . . . . . . . . 5-336 HO_MARGIN_DEF . . . . . . . . . . . . . 5-352
HDPC ho_margin_rxlev . . . . . . . . . . . . . . . 2-399
bounce_protect_cong_tmr . . . . . . . . . . 6-10 ho_margin_rxqual . . . . . . . . . . . . . . 2-399
bounce_protect_margin. . . . . . . . . . . . 5-55 ho_margin_type5 . . . . . . . . . . . . . . . 5-353
bounce_protect_qual_tmr . . . . . . . . . . . 6-11 ho_margin_usage_flag . . . . . . . . . . . . 5-354
hop_count_timer . . . . . . . . . . . . . . . 6-89 ho_only_max_pwr . . . . . . . . . . . . . . 5-356
layer_number . . . . . . . . . . . . . . . 5-464 ho_pwr_level_inner . . . . . . . . . . 5-358, 5-387
prioritize_microcell . . . . . . . . . . . . 5-622 ho_request . . . . . . . . . . . . . . . . . . . 6-87
protect_last_ts . . . . . . . . . . . . . . . 5-624 ho_successful . . . . . . . . . . . . . . . . . 6-88
hdsl_losw_restore . . . . . . . . . . . . . . 5-338 hop_count . . . . . . . . . . . . . . . . . . 5-360
hdsl_modem_setting . . . . . . . . . . . . . . 7-38 hop_count_timer . . . . . . . . . . . . . . . . 6-89
hdsl_oos_mon_period . . . . . . . . . . . . . 7-40 hop_qual_enabled . . . . . . . . . . . . . . 5-361
hdsl_restore_mon_period . . . . . . . . . . . . 7-42 hopping_support . . . . . . . . . . . . . . . 5-363
hdsl_snr_daily . . . . . . . . . . . . . . . . 5-339 hopping_systems_enabled . . . . . . . . . . 5-365
hdsl_snr_daily_mon_period . . . . . . . . . . 5-341 hopping_systems_hsn. . . . . . . . . . . . . 5-367
hdsl_snr_hourly . . . . . . . . . . . . . . . 5-342 hopping_systems_mobile_alloc . . . . . . . . 5-369
hdsl_snr_hourly_mon_period . . . . . . . . . 5-344 hr_fr_hop_count . . . . . . . . . . . . . . . 5-371
hdsl_snr_losw . . . . . . . . . . . . . . . . 5-337 hr_intracell_ho_allowed . . . . . . . . . . . 5-372
hdsl_snr_oos . . . . . . . . . . . . . . . . . 5-345 hr_res_ts. . . . . . . . . . . . . . . . . . . 5-374
hdsl_snr_restore . . . . . . . . . . . . . . . 5-347 HSN. . . . . . . . . . . . . . . . . . . . . 5-368
help . . . . . . . . . . . . . . . . . . . . . . 3-4
68P02901W23-Q IX-7
Index
ias_connected . . . . . . . . . . . . . . . . . 7-44 intra_cell_handover_allowed . . . . . . . . . 5-398

illegal_circuit_id . . . . . . . . . . . . . . . 5-375
immediate_assign_mode . . . . . . . . . . . 5-376
inc_prp_cap_ena . . . . . . . . . . . . . . . 5-378
index1 . . . . . . . . . . . . . . . . . . . . . 2-95
index2 . . . . . . . . . . . . . . . . . . . . . 2-96
Initial SYSGEN mode . . . . . . . . . . . . . 1-27
initial_sync_timer . . . . . . . . . . . . . . . 6-90
inner_hr_usage_thres . . . . . . . . . . . . . 5-384
inner_zone_alg . . . . . . . . . . . . . . . . 5-385
ins_device . . . . . . . . . . . . . . . . . . 2-382
int_antenna . . . . . . . . . . . . . . . . . . 7-45
INT_BOUND_X1 . . . . . . . . . . . . . . 5-397
INT_BOUND_X2 . . . . . . . . . . . . . . 5-397
INT_BOUND_X3 . . . . . . . . . . . . . . 5-397
INT_BOUND_X4 . . . . . . . . . . . . . . 5-397
INT_BOUND_X5 . . . . . . . . . . . . . . 5-397
int_hdsl_modem . . . . . . . . . . . . . . . . 7-46
intave . . . . . . . . . . . . . . . . . . . . 5-388
inter_cell_handover_allowed . . . . . . . . . 5-390
inter_rat_enabled
4225 . . . . . . . . . . . . . . . . . . . 5-392
interband_ho_allowed . . . . . . . . . . . . 5-394
interfer_bands . . . . . . . . . . . . . . . . 5-396
interference based use algorithm. . . . . . . . 5-386
interfering_nbr . . . . . . . . . . . . . . . . 2-399
ksw_config . . . . . . . . . . . . . . . . . 5-400
l_rxlev_dl_h . . . . . . . . . . . . . . . . . 5-402 l_rxqual_dl_h_hr . . . . . . . . . . . . . . . 5-413

L_RXLEV_DL_H . . . . . . . . . . . . . . 5-403 l_rxqual_dl_p . . . . . . . . . . . . . . . . 5-423
l_rxlev_dl_p . . . . . . . . . . . . . . . . . 5-404 L_RXQUAL_DL_P . . . . . . 5-424, 5-429, 5-431
L_RXLEV_DL_P . . . . . . . . . . . . . . 5-405 l_rxqual_dl_p_amr_fr. . . . . . . . . . . . . 5-425
l_rxlev_ul_h . . . . . . . . . . . . . . . . . 5-406 l_rxqual_dl_p_data . . . . . . . . . . . . . . 5-428
L_RXLEV_UL_H . . . . . . . . . . . . . . 5-407 l_rxqual_dl_p_hopping . . . . . . . . . . . . 5-430
l_rxlev_ul_p . . . . . . . . . . . . . . . . . 5-408 l_rxqual_dl_p_hopping_amr_fr . . . . . . . . 5-432
L_RXLEV_UL_P . . . . . . . . . . . . . . 5-409 l_rxqual_dl_p_hopping_hr . . . . . . . . . . 5-434
l_rxqual_dl_h . . . . . . . . . . . . . . . . 5-410 l_rxqual_dl_p_hr . . . . . . . . . . . . . . . 5-426
L_RXQUAL_DL_H . . . 5-411, 5-416, 5-418, 5-444 l_rxqual_ul_h . . . . . . . . . . . . . . . . 5-436
l_rxqual_dl_h_amr_hr . . . . . . . . . . . . 5-412 L_RXQUAL_UL_H . . . . . . . . . . 5-437, 5-442
l_rxqual_dl_h_data . . . . . . . . . . . . . . 5-415 l_rxqual_ul_h_amr_fr. . . . . . . . . . . . . 5-438
l_rxqual_dl_h_hopping . . . . . . . . . . . . 5-417 l_rxqual_ul_h_data . . . . . . . . . . . . . . 5-441
l_rxqual_dl_h_hopping_amr_fr . . . . . . . . 5-419 l_rxqual_ul_h_hopping . . . . . . . . . . . . 5-443
l_rxqual_dl_h_hopping_hr . . . . . . . . . . 5-421 l_rxqual_ul_h_hopping_amr_fr . . . . . . . . 5-445
IX-8 68P02901W23-Q
l_rxqual_ul_h_hopping_hr . . . . . . . . . . 5-447 lb_int_ss7_l2_t3 . . . . . . . . . . . . . . . 6-103

l_rxqual_ul_h_hr . . . . . . . . . . . . . . . 5-439 lb_int_ss7_l2_t4 . . . . . . . . . . . . . . . 6-104
l_rxqual_ul_p . . . . . . . . . . . . . . . . 5-449 lb_int_ss7_l2_t5 . . . . . . . . . . . . . . . 6-105
L_RXQUAL_UL_P . . . . . . 5-450, 5-455, 5-457 lb_int_ss7_l2_t6 . . . . . . . . . . . . . . . 6-106
l_rxqual_ul_p_amr_fr. . . . . . . . . . . . . 5-451 lb_int_ss7_l2_t7 . . . . . . . . . . . . . . . 6-107
l_rxqual_ul_p_data . . . . . . . . . . . . . . 5-454 lb_int_ss7_l3_t1 . . . . . . . . . . . . . . . 6-108
l_rxqual_ul_p_hopping . . . . . . . . . . . . 5-456 lb_int_ss7_l3_t12 . . . . . . . . . . . . . . 6-109
l_rxqual_ul_p_hopping_amr_fr . . . . . . . . 5-458 lb_int_ss7_l3_t13 . . . . . . . . . . . . . . 6-110
l_rxqual_ul_p_hopping_hr . . . . . . . . . . 5-460 lb_int_ss7_l3_t14 . . . . . . . . . . . . . . 6-111
l_rxqual_ul_p_hr . . . . . . . . . . . . . . . 5-452 lb_int_ss7_l3_t17 . . . . . . . . . . . . . . 6-112
land_layer1_mode . . . . . . . . . . . . . . 5-462 lb_int_ss7_l3_t2 . . . . . . . . . . . . . . . 6-113
language_id lb_int_ss7_l3_t22 . . . . . . . . . . . . . . 6-114
see: data_coding_scheme . . . . . . . . . . 2-128 lb_int_ss7_l3_t23 . . . . . . . . . . . . . . 6-116
lapd_k . . . . . . . . . . . . . . . . . . . . . 7-47 lb_int_ss7_l3_t4 . . . . . . . . . . . . . . . 6-118
lapd_n200 . . . . . . . . . . . . . . . . . . . 7-49 lb_int_ss7_l3_t5 . . . . . . . . . . . . . . . 6-119
lapd_t200_timer . . . . . . . . . . . . . . . . 7-51 lb_int_ss7_slt_t1 . . . . . . . . . . . . . . . 6-120
layer_number . . . . . . . . . . . . . . . . 5-464 lb_int_t_stat_info. . . . . . . . . . . . . . . 6-121
lb_int_bssmap_t13 . . . . . . . . . . . . . . . 6-92 LCF
lb_int_bssmap_t4. . . . . . . . . . . . . . . . 6-93 max_cbls . . . . . . . . . . . . . . . . . . 7-53
lb_int_called_pci . . . . . . . . . . . . . . . 5-465 max_gsla . . . . . . . . . . . . . . . . . . 7-56
lb_int_calling_pci . . . . . . . . . . . . . . 5-466 max_mtls . . . . . . . . . . . . . . 5-487, 7-57
lb_int_clear_command . . . . . . . . . . . . . 6-94 lcs_mode . . . . . . . . . . . . . . . . . . 5-470
lb_int_cr_calling . . . . . . . . . . . . . . . 5-467 lcs_perf_location . . . . . . . . . . . . . . . 6-122
lb_int_dpc . . . . . . . . . . . . . . . . . . 5-468 lcs_segmentation . . . . . . . . . . . . . . . 6-123
lb_int_global_reset_repetitions . . . . . . . . 5-469 lcs_supervision. . . . . . . . . . . . . . . . 6-124
lb_int_sccp_released . . . . . . . . . . . . . . 6-95 link_about_to_fail . . . . . . . . . . . . . . 5-473
lb_int_sccp_tconn_est . . . . . . . . . . . . . 6-96 link_fail . . . . . . . . . . . . . . . . . . . 5-475
lb_int_sccp_tiar . . . . . . . . . . . . . . . . 6-97 List of MMI commands . . . . . . . . . . . . . 1-11
lb_int_sccp_tias . . . . . . . . . . . . . . . . 6-98 lmtl_loadshare_granularity . . . . . . . . . . 5-477
lb_int_sccp_trel . . . . . . . . . . . . . . . . 6-99 local_maintenance . . . . . . . . . . . . . . 5-478
lb_int_spi . . . . . . . . . . . . . . . . . . 6-100 lock_device . . . . . . . . . . . . . . . . . 2-387
lb_int_ss7_l2_t1 . . . . . . . . . . . . . . . 6-101 low_sig_thresh . . . . . . . . . . . . . . . . 5-481
lb_int_ss7_l2_t2 . . . . . . . . . . . . . . . 6-102 lta_alarm_range . . . . . . . . . . . . . . . 5-482
Maintenance (Fault Management) max_rst_ckt_timer_exps . . . . . . . . . . . 5-497

about . . . . . . . . . . . . . . . . . . . . 1-3 max_tx_bts . . . . . . . . . . . . . . . . . 5-498
man . . . . . . . . . . . . . . . . . . . . . . 3-8 max_tx_ms . . . . . . . . . . . . . . . . . 5-504
max_cbls . . . . . . . . . . . . . . . . . . . 7-53 mb_preference . . . . . . . . . . . . . . . . 5-506
max_dris. . . . . . . . . . . . . . . . . . . . 7-54 mb_tch_congest_thres . . . . . . . . . . . . 5-507
max_gprs_ts_per_carrier . . . . . . . . . . . 5-483 Miscellaneous Commands
max_gsls . . . . . . . . . . . . . . . . . . . 7-56 about . . . . . . . . . . . . . . . . . . . . 1-4
max_ms_dl_buffer . . . . . . . . . . . . . . 5-484 missing_rpt . . . . . . . . . . . . . . . . . 5-508
max_ms_dl_rate . . . . . . . . . . . . . . . 5-486 MMI command list . . . . . . . . . . . . . . . 1-11
max_mtls . . . . . . . . . . . . . . . 5-487, 7-57 MMI commands
max_number_of_sdcchs . . . . . . . . . . . 5-489 availability by location . . . . . . . . . . . . 1-11
max_pagenum_per_sec . . . . . . . . . . . . 5-491 availability by SYSGEN mode . . . . . . . . 1-15
max_q_length_channel . . . . . . . . . . . . 5-492 conventions . . . . . . . . . . . . . . . . . 1-9
max_q_length_sdcch . . . . . . . . . . . . . 5-494 mmi_cell_id_format . . . . . . . . . . . . . 5-509
max_retran. . . . . . . . . . . . . . . . . . 5-495 MMS
MAX_RETRANS . . . . . . . . . . . . . . 5-496 ber_oos_mon_period . . . . . . . . . . . 7-7, 7-9
68P02901W23-Q IX-9
Index
MMS (contd.) MS_RANGE_MAX . . . . . . . . . . . . . 5-517

mms_priority . . . . . . . . . . . . . . . . 7-59 ms_sapi3_est. . . . . . . . . . . . . . . . . 6-129
nbit . . . . . . . . . . . . . . . . . . . . . 7-67 ms_txpwr_max. . . . . . . . . . . . . . . . 2-399
mms_cat_enable . . . . . . . . . . . . . . . 5-510 MS_TXPWR_MAX . . . . . . . . . . . . . 5-505
mms_config_type . . . . . . . . . . . . . . 5-512 ms_txpwr_max_cch . . . . . . . . . . . . . 5-525
mms_priority. . . . . . . . . . . . . . . . . . 7-59 MS_TXPWR_MAX_CCH . . . . . . . . . . 5-527
mod_conn . . . . . . . . . . . . . . . . . . 2-392 ms_txpwr_max_cell . . . . . . . . . . . . . 5-528
mod_nsvc . . . . . . . . . . . . . . . . . . 2-395 ms_txpwr_max_def. . . . . . . . . . . . . . 5-530
mode_modify . . . . . . . . . . . . . . . . 6-125 MS_TXPWR_MAX_DEF . . . . . . . . . . 5-531
mode_rr_modify_ack . . . . . . . . . . . . . 6-127 ms_txpwr_max_inner. . . . . . . . . . 5-387, 5-532
modify_neighbor . . . . . . . . . . . . . . . 2-397 msc_bss_overload_allowed . . . . . . . . . . 5-533
adap_trigger_pbgt_nbr . . . . . . . . . . . 2-398 msc_mms_id . . . . . . . . . . . . . . . . . . 7-61
adj_chan_intf_test . . . . . . . . . . . . . 2-398 msc_preference . . . . . . . . . . . . . . . 5-534
ba_bcch . . . . . . . . . . . . . . . . . . 2-398 msc_qt. . . . . . . . . . . . . . . . . . . . 5-536
ba_gprs . . . . . . . . . . . . . . . . . . 2-398 msc_release . . . . . . . . . . . . . . . . . 5-538
congest_ho_margin . . . . . . . . . . . . 2-398 MSI
diversity_enabled . . . . . . . . . . . . . 2-399 msc_mms_id . . . . . . . . . . . . . . . . 7-61
dr_allowed . . . . . . . . . . . . . . . . 2-398 msi_type . . . . . . . . . . . . . . . . . . 7-62
fdd_arfcn . . . . . . . . . . . . . . . . . 2-399 transcoding-capability . . . . . . . . . . . . 7-85
ho_margin_cell . . . . . . . . . . . . . . 2-398 msi_type. . . . . . . . . . . . . . . . . . . . 7-62
ho_margin_rxlev . . . . . . . . . . . . . . 2-399 mspwr_alg . . . . . . . . . . . . . . . . . . 5-539
ho_margin_rxqual . . . . . . . . . . . . . 2-399 MTCRM_ADD_ACC_CLASS . . . . . . . . . 6-2
interfering_nbr . . . . . . . . . . . . . . . 2-399 MTCRM_CARRIER_FREE_IMMEDIATE . . . 6-43
ms_txpwr_max . . . . . . . . . . . . . . 2-399 MTCRM_CBT1 . . . . . . . . . . . . . . . . 6-44
neighboring_range . . . . . . . . . . . . . 2-399 MTCRM_CBT2 . . . . . . . . . . . . . . . . 6-45
pbgt_alg_type . . . . . . . . . . . . . . . 2-399 MTCRM_CBT3 . . . . . . . . . . . . . . . . 6-46
pbgt_hreqave . . . . . . . . . . . . . . . 2-399 MTCRM_DEOC_INTACT . . . . . . . . . . . 6-59
rxlev_min_cell. . . . . . . . . . . . . . . 2-399 MTCRM_EMERG_RESERVED . . . . . . . . 6-67
scr_code. . . . . . . . . . . . . . . . . . 2-399 MTCRM_FC_T1 . . . . . . . . . . . . . . . . 6-71
synchronized . . . . . . . . . . . . . . . 2-399 MTCRM_FC_T2 . . . . . . . . . . . . . . . . 6-73
modify_value . . . . . . . . . . . . . . . . 2-404 MTCRM_HANDOVER_ACK . . . . . . . . . 6-83
ms_distance_allowed . . . . . . . . . . . . . 5-514 MTCRM_REGISTER_EXP. . . . . . . . . . 6-152
ms_max_range . . . . . . . . . . . . . . . . 5-516 MTCRM_RF_CHAN_REL_ACK . . . . . . . 6-154
ms_p_con_ack . . . . . . . . . . . . . . . . 5-518 mtl_loadshare_granularity . . . . . . . . . . 5-540
ms_p_con_interval . . . . . . . . . . . . . . 5-520 MULT
ms_power_control_allowed . . . . . . . . . . 5-522 bsic . . . . . . . . . . . . . . . . . . . . . 5-68
ms_power_offset . . . . . . . . . . . . . . . 5-524 multiband_reporting . . . . . . . . . . . . . 5-541
n_avg_i . . . . . . . . . . . . . . . . . . . 5-543 nc_non_drx_period . . . . . . . . . . . . . . 6-131

N1 . . . . . . . . . . . . . . . . . . . . . 5-167 nc_reporting_period_i . . . . . . . . . . . . 6-133
N2 . . . . . . . . . . . . . . . . . . . . . 5-169 nc_reporting_period_t . . . . . . . . . . . . 6-134
N3 . . . . . . . . . . . . . . . . . . . . . 5-171 NCC . . . . . . . . . . . . . . . . . . . . 5-545
n391. . . . . . . . . . . . . . . . . . . . . . 7-64 ncc_of_plmn_allowed . . . . . . . . . . . . 5-544
n392. . . . . . . . . . . . . . . . . . . . . . 7-65 nccr_enabled . . . . . . . . . . . . . . . . . 5-546
n393. . . . . . . . . . . . . . . . . . . . . . 7-66 nccrOpt . . . . . . . . . . . . . . . . 5-547, 5-586
N4 . . . . . . . . . . . . . . . . . . . . . 5-173 ne_id . . . . . . . . . . . . . . . . . . . . . 7-68
N5 . . . . . . . . . . . . . . . . . . . . . 5-175 neighbor_journal . . . . . . . . . . . . . . . 5-548
N6 . . . . . . . . . . . . . . . . . . . . . 5-177 neighbor_report_timer . . . . . . . . . . . . 6-136
N7 . . . . . . . . . . . . . . . . . . . . . 5-179 neighboring_range . . . . . . . . . . . . . . 2-399
N8 . . . . . . . . . . . . . . . . . . . . . 5-181 network_control_order . . . . . . . . . . . . 5-550
nbit . . . . . . . . . . . . . . . . . . . . . . 7-67
IX-10 68P02901W23-Q
new_calls_hr . . . . . . . . . . 5-491, 5-533, 5-552, number_sdcchs_preferred . . . . . . . . . . . 5-568

5-688 to 5-689, 5-691, 6-14, 6-171
ni . . . . . . . . . . . . . . . . . . . . . . 5-553
NIU
equip command . . . . . . . . . . . . . . 2-363
ns_alive_retries . . . . . . . . . . . . . . . 5-555
ns_alive_timer . . . . . . . . . . . . . . . . 6-137
ns_block_retries . . . . . . . . . . . . . . . 5-556
ns_block_timer. . . . . . . . . . . . . . . . 6-138
ns_burst_excess
mod_nsvc command . . . . . . . . . . . . 2-395
ns_burst_size
mod_nsvc command . . . . . . . . . . . . 2-395
ns_commit_info_rate
mod_nsvc command . . . . . . . . . . . . 2-395
ns_reset_period . . . . . . . . . . . . . . . 6-139
ns_reset_timer . . . . . . . . . . . . . . . . 6-140
ns_test_timer. . . . . . . . . . . . . . . . . 6-141
ns_unblock_retries . . . . . . . . . . . . . . 5-557
nsei . . . . . . . . . . . . . . . . . . . . . 5-558
num_audit_retires . . . . . . . . . . . . . . 5-559
num_emerg_access . . . . . . . . . . . . . . 5-560
num_emerg_rejected . . . . . . . . . . . . . 5-561
num_emerg_tch_kill . . . . . . . . . . . . . 5-562
num_emerg_term_sdcch . . . . . . . . . . . 5-563
num_gbl_dl_thrput_samples . . . . . . . . . 5-564
num_gbl_ul_thrput_samples . . . . . . . . . 5-565
number_of_preferred_cells . . . . . . . . . . 5-566
opc . . . . . . . . . . . . . . . . . . . . . 5-570 override_intra_bss_pre_transfer . . . . . . . . 5-582

option_alg_a5_1 . . . . . . . . . . . . . . . 5-572
option_alg_a5_2 . . . . . . . . . . . . . . . 5-573
option_alg_a5_3 . . . . . . . . . . . . . . . 5-574
option_alg_a5_4 . . . . . . . . . . . . . . . 5-575
option_alg_a5_5 . . . . . . . . . . . . . . . 5-576
option_alg_a5_6 . . . . . . . . . . . . . . . 5-577
option_alg_a5_7 . . . . . . . . . . . . . . . 5-578
option_emergency_preempt . . . . . . . . . . 5-579
opto_reporting . . . . . . . . . . . . . . . . . 7-69
outer_zone_usage_level. . . . . . . . . . . . 5-581
P_CON_ACK . . . . . . . . . . . . . 5-79, 5-519 P6 . . . . . . . . . . . . . . . . . . . . . . 5-177

P_CON_INTERVAL . . . . . . . . . . 5-81, 5-521 P7 . . . . . . . . . . . . . . . . . . . . . . 5-179
P1 . . . . . . . . . . . . . . . . . . . . . . 5-167 P8 . . . . . . . . . . . . . . . . . . . . . . 5-181
P2 . . . . . . . . . . . . . . . . . . . . . . 5-169 packet_size . . . . . . . . . . . . . . . . . 2-144
P3 . . . . . . . . . . . . . . . . . . . . . . 5-171 page . . . . . . . . . . . . . . . . . . . . . 2-409
P4 . . . . . . . . . . . . . . . . . . . . . . 5-173 parameter defaults . . . . . . . . . . . . . . . 2-24
P5 . . . . . . . . . . . . . . . . . . . . . . 5-175 passwords . . . . . . . . . . . . . . . . . . . 1-3
68P02901W23-Q IX-11
Index
pbgt_alg_type . . . . . . . . . . . . . . . . 2-399 pkt_radio_type . . . . . . . . . . . . . . . . 5-602

pbgt_hreqave. . . . . . . . . . . . . . . . . 2-399 PLMN . . . . . . . . . . . . . . . . . . . . . 5-68
pbgt_mode. . . . . . . . . . . . . . . . . . 5-583 PLMN_PERMITTED . . . . . . . . . . . . 5-545
pccch_drx_timer_max . . . . . . . . . . . . 6-142 pool_gproc_preemption. . . . . . . . . . . . 5-606
pcr_enable . . . . . . . . . . . . . . . . . . 5-587 poor_initial_assignment. . . . . . . . . . . . 5-607
pcr_n1 . . . . . . . . . . . . . . . . . . . . 5-588 POW_INC_STEP_SIZE . . . . . . . . 5-609, 5-611
pcr_n2 . . . . . . . . . . . . . . . . . . . . 5-589 pow_inc_step_size_dl . . . . . . . . . . . . 5-608
pcu_red_map_01 . . . . . . . . . . . . . . . 5-590 pow_inc_step_size_ul . . . . . . . . . . . . 5-610
pcu_red_map_02 . . . . . . . . . . . . . . . 5-591 POW_RED_STEP_SIZE . . . . . . . . 5-613, 5-615
pcu_red_map_11 . . . . . . . . . . . . . . . 5-591 pow_red_step_size_dl . . . . . . . . . . . . 5-612
pcu_red_map_12 . . . . . . . . . . . . . . . 5-591 pow_red_step_size_ul . . . . . . . . . . . . 5-614
pcu_red_map_21 . . . . . . . . . . . . . . . 5-591 power based use algorithm . . . . . . . . . . 5-386
pcu_red_map_22 . . . . . . . . . . . . . . . 5-591 prach_max_retran . . . . . . . . . . . . . . 5-616
pcu_redundancy . . . . . . . . . . . . . . . 5-590 prach_s . . . . . . . . . . . . . . . . . . . 5-617
penalty_time . . . . . . . . . . . . . . . . . 6-144 prach_tx_int . . . . . . . . . . . . . . . . . 5-619
PENALTY_TIME . . . . . . . . . . . . . . 6-145 pref_rtf_id . . . . . . . . . . . . . . . . . . . 7-71
percent_traf_cs . . . . . . . . . . . . . . . . 5-592 primary_pcu . . . . . . . . . . . . . . . . . 5-621
persistence_level . . . . . . . . . . . . . . . 5-593 prioritize_microcell. . . . . . . . . . . . . . 5-622
phase_lock_duration . . . . . . . . . . . . . 6-146 priority_class. . . . . . . . . . . . . . . . . 5-623
phase_lock_gclk . . . . . . . . . . . . . . . 5-595 protect_last_ts . . . . . . . . . . . . . . . . 5-624
phase_lock_retry . . . . . . . . . . . . . . . 5-596 prp_capacity_opt
phase2_classmark_allowed . . . . . . . . . . 5-597 feature . . . . . . . . . . . . . . . . . . 5-626
phase2_resource_ind_allowed . . . . . . . . . 5-598 prr_aggr_factor. . . . . . . . . . . . . . . . 5-627
pic_error_clr_thresh . . . . . . . . . . . . . 5-599 psi1_repeat_period . . . . . . . . . . . . . . 6-147
pic_error_gen_thresh . . . . . . . . . . . . . 5-600 pwr_handover_allowed . . . . . . . . . . . . 5-628
pic_error_inc. . . . . . . . . . . . . . 5-601, 5-655 pwrc. . . . . . . . . . . . . . . . . . . . . 5-630
PICP PWRC. . . . . . . . . . . . . . . . . . . . 5-631
equip command . . . . . . . . . . . . . . 2-364
qsearch_c_initial . . . . . . . . . . . . . . . 5-634 query_audits . . . . . . . . . . . . . . . . . 2-411

qsearch_i . . . . . . . . . . . . . . . . . . 5-635 queue_management_information . . . . . . . 5-632
qsearch_p . . . . . . . . . . . . . . . . . . 5-636
IX-12 68P02901W23-Q
ra_colour . . . . . . . . . . . . . . . . . . 5-638 rr_ny1_rep . . . . . . . . . . . . . . . . . . 6-155

ra_reselect_hysteresis. . . . . . . . . . . . . 5-640 rr_t3101 . . . . . . . . . . . . . . . . . . . 6-157
RAC . . . . . . . . . . . . . . . . . . . . 5-642 rr_t3103 . . . . . . . . . . . . . . . . . . . 6-159
rac parameter . . . . . . . . . . . . . . . . 5-642 rr_t3105 . . . . . . . . . . . . . . . . . . . 6-161
RACH_BUSY_THRES. . . . . . . . . . . . 5-647 rr_t3109 . . . . . . . . . . . . . . . . . . . 6-163
rach_load_period . . . . . . . . . . . . 5-109, 5-644 rr_t3111_sd . . . . . . . . . . . . . . . . . 6-165
rach_load_threshold . . . . . . . . . . . . . 5-646 rr_t3111_tch . . . . . . . . . . . . . . . . . 6-167
rach_load_type . . . . . . . . . . . . . . . . 5-648 rr_t3212 . . . . . . . . . . . . . . . . . . . 6-169
RACH_MEAS_PERIOD . . . . . . . . . . . 5-645 RRSM_AUDIT_TIMER . . . . . . . . . . . . 6-40
radio_chan_released . . . . . . . . . . . . . 6-149 RRSM_MTA. . . . . . . . . . . . . . . . . . 6-51
radio_link_timeout . . . . . . . . . . . . . . 5-649 RRSM_MTD . . . . . . . . . . . . . . . . . 6-86
RADIO_LINK_TIMEOUT(BS) . . . . . . . . 5-476 RRSM_MTE1 . . . . . . . . . . . . . . . . 6-130
RADIO_LINK_TIMEOUT(MS) . . . . . . . 5-650 RRSM_MTQ . . . . . . . . . . . . . . . . . 6-49
rapid_pwr_down . . . . . . . . . . . . . . . 5-651 RRSM_MTW . . . . . . . . . . . . . . . . . 6-39
rci_error_clr_thresh. . . . . . . . . . . . . . 5-653 RRSM_MTY . . . . . . . . . . . . . . . . 6-128
rci_error_gen_thresh . . . . . . . . . . . . . 5-654 RRSM_T10 . . . . . . . . . . . . . . . . . . 6-23
RE RRSM_T11 . . . . . . . . . . . . . . . . . . 6-25
reestablish allowed . . . . . . . . . . . . . 5-664 RRSM_T8 . . . . . . . . . . . . . . . . . . . 6-35
reassign . . . . . . . . . . . . . . . . . . . 2-415 RSL
reattempt_pl . . . . . . . . . . . . . . . . . 2-418 lapd_k. . . . . . . . . . . . . . . . . . . . 7-47
reconfig_fr_to_hr. . . . . . . . . . . . . . . 5-656 lapd_n200 . . . . . . . . . . . . . . . . . . 7-49
red_loss_daily . . . . . . . . . . . . . . . . 5-657 lapd_t200_timer . . . . . . . . . . . . . . . 7-51
red_loss_hourly . . . . . . . . . . . . . . . 5-658 rsl_congestion_alarm_timer . . . . . . . . . . 6-171
red_loss_oos . . . . . . . . . . . . . . . . . 5-659 rsl_congestion_control . . . . . . . . . . . . 5-688
red_loss_restore . . . . . . . . . . . . . . . 5-660 rsl_lcf_congestion_thi . . . . . . . . . . . . 5-689
red_psp_audit_tmr . . . . . . . . . . . . . . 6-151 rsl_lcf_congestion_tlow. . . . . . . . . . . . 5-691
red_time_oos. . . . . . . . . . . . . . . . . 5-661 rsl_rate . . . . . . . . . . . . . . . . . . . . 7-72
red_time_restore . . . . . . . . . . . . . . . 5-662 RTF
reestablish_allowed. . . . . . . . . . . . . . 5-663 sd_load . . . . . . . . . . . . . . . . . . . 7-73
register_exp . . . . . . . . . . . . . . . . . 6-152 sd_priority. . . . . . . . . . . . . . . . . . 7-75
rel_tim_adv . . . . . . . . . . . . . . . . . 5-665 trx_pwr_red . . . . . . . . . . . . . . . . . 7-87
remote_loss_daily . . . . . . . . . . . . . . 5-667 rtf_path_enable. . . . . . . . . . . . . . . . 5-692
remote_loss_hourly. . . . . . . . . . . . . . 5-668 rtry_cand_prd . . . . . . . . . . . . . . . . 6-172
remote_loss_oos . . . . . . . . . . . . . . . 5-669 RXCDR
remote_loss_restore . . . . . . . . . . . . . 5-670 ne_id . . . . . . . . . . . . . . . . . . . . 7-68
remote_time_oos . . . . . . . . . . . . . . . 5-671 rxlev_access_min . . . . . . . . . . . . . . 5-693
remote_time_restore . . . . . . . . . . . . . 5-672 RXLEV_ACCESS_MIN . . . . . . . . . . . 5-694
report_resource_tch_f_high_water_mark . . . . 5-673 rxlev_dl_ho . . . . . . . . . . . . . . . . . 5-695
report_resource_tch_f_low_water_mark . . . . 5-675 RXLEV_DL_IH . . . . . . . . . . . . . . . 5-804
res_gprs_pdchs. . . . . . . . . . . . . . . . 5-677 rxlev_dl_pc . . . . . . . . . . . . . . . . . 5-697
res_ts_less_one_carrier . . . . . . . . . . . . 5-679 rxlev_dl_zone . . . . . . . . . . . . . 5-387, 5-699
reset_device . . . . . . . . . . . . . . . . . 2-420 rxlev_min_cell . . . . . . . . . . . . . . . . 2-399
reset_site . . . . . . . . . . . . . . . . . . 2-425 rxlev_min_def . . . . . . . . . . . . . . . . 5-701
retry_candidate_period . . . . . . . . . . . . 6-172 rxlev_ul_ho . . . . . . . . . . . . . . . . . 5-703
rf_chan_rel_ack . . . . . . . . . . . . . . . 6-153 RXLEV_UL_IH . . . . . . . . . . . . . . . 5-808
rf_res_ind_period . . . . . . . . . . . . . . 5-681 rxlev_ul_pc . . . . . . . . . . . . . . . . . 5-705
RF_RES_IND_PERIOD . . . . . . . . . . . 5-681 rxlev_ul_zone . . . . . . . . . . . . . 5-387, 5-707
rpd_offset . . . . . . . . . . . . . . . . . . 5-682 rxqual_dl_ho . . . . . . . . . . . . . . . . . 5-709
rpd_period . . . . . . . . . . . . . . . . . . 5-683 rxqual_dl_pc . . . . . . . . . . . . . . . . . 5-711
rpd_trigger . . . . . . . . . . . . . . . . . . 5-684 rxqual_ul_ho . . . . . . . . . . . . . . . . . 5-713
rpt_bad_qual_no_mr . . . . . . . . . . . . . 5-686 rxqual_ul_pc . . . . . . . . . . . . . . . . . 5-715
68P02901W23-Q IX-13
Index
sacch_info . . . . . . . . . . . . . . . . . . 6-174 ss7_l2_t6 . . . . . . . . . . . . . . . . . . 6-194

sap_audit_type . . . . . . . . . . . . . . . . 5-717 ss7_l2_t7 . . . . . . . . . . . . . . . . . . 6-196
sap_device_type . . . . . . . . . . . . . . . 5-718 ss7_l3_t1 . . . . . . . . . . . . . . . . . . 6-197
sap_end_time . . . . . . . . . . . . . . . . 5-719 ss7_l3_t12 . . . . . . . . . . . . . . . . . . 6-198
sap_interval . . . . . . . . . . . . . . . . . 5-720 ss7_l3_t13 . . . . . . . . . . . . . . . . . . 6-199
sap_start_time . . . . . . . . . . . . . . . . 5-722 ss7_l3_t14 . . . . . . . . . . . . . . . . . . 6-200
sccp_bssap_mgt . . . . . . . . . . . . . . . 5-724 ss7_l3_t17 . . . . . . . . . . . . . . . . . . 6-201
sccp_released . . . . . . . . . . . . . . . . 6-176 ss7_l3_t2 . . . . . . . . . . . . . . . . . . 6-202
sccp_tconn_est . . . . . . . . . . . . . . . . 6-177 ss7_l3_t22 . . . . . . . . . . . . . . . . . . 6-203
sccp_tiar . . . . . . . . . . . . . . . . . . . 6-178 ss7_l3_t23 . . . . . . . . . . . . . . . . . . 6-205
sccp_tias. . . . . . . . . . . . . . . . . . . 6-180 ss7_l3_t4 . . . . . . . . . . . . . . . . . . 6-207
sccp_trel . . . . . . . . . . . . . . . . . . . 6-182 ss7_l3_t5 . . . . . . . . . . . . . . . . . . 6-208
scr_enabled . . . . . . . . . . . . . . . . . 5-726 ss7_mode . . . . . . . . . . . . . . . . . . 5-753
sd_load . . . . . . . . . . . . . . . . . . . . 7-73 ss7_slt_t1 . . . . . . . . . . . . . . . . . . 6-209
sd_priority . . . . . . . . . . . . . . . . . . . 7-75 ssm_critical_overload_threshold. . . . . . . . 5-755
sdcch_ho . . . . . . . . . . . . . . . . . . 5-728 SSM_MTB1 . . . . . . . . . . . . . . . . . . 6-87
sdcch_need_high_water_mark. . . . . . . . . 5-730 SSM_MTC . . . . . . . . . . . . . . . . . . 6-68
sdcch_need_low_water_mark . . . . . . . . . 5-732 SSM_MTG . . . . . . . . . . . . . . . . . . 6-57
sdcch_tch_band_reassign_delay . . . . . . . . 5-734 SSM_MTH . . . . . . . . . . . . . . . . . 6-150
sdcch_timer_ho . . . . . . . . . . . . . . . 5-735 SSM_MTI . . . . . . . . . . . . . . . . . . . 6-53
search_prio_3g . . . . . . . . . . . . . . . . 5-737 SSM_MTJ . . . . . . . . . . . . . . . . . . . 6-88
second_asgnmnt . . . . . . . . . . . . . . . 5-738 SSM_MTK . . . . . . . . . . . . . . . . . . 6-84
secondary_freq_type . . . . . . . . . . 5-387, 5-740 SSM_MTL . . . . . . . . . . . . . . . . . 6-176
Security Management SSM_MTN . . . . . . . . . . . . . . . . . . 6-4
about . . . . . . . . . . . . . . . . . . . . 1-3 SSM_MTV . . . . . . . . . . . . . . . . . . 6-12
set_full_power . . . . . . . . . . . . . . . . 2-430 SSM_MTX . . . . . . . . . . . . . . . . . 6-183
set_relay_contact . . . . . . . . . . . . . . . 2-434 ssm_normal_overload_threshold . . . . . . . 5-757
sgsn_release . . . . . . . . . . . . . . . . . 5-742 SSM_T7 . . . . . . . . . . . . . . . . . . . . 6-33
shared_timeslots . . . . . . . . . . . . . . . . 7-77 SSM_TIAR . . . . . . . . . . . . . . . . . 6-179
shutdown_device . . . . . . . . . . . . . . . 2-436 SSM_TIAS . . . . . . . . . . . . . . . . . 6-181
SITE ssm_timer_value,10 . . . . . . . . . . . . . . 6-12
rsl_rate . . . . . . . . . . . . . . . . . . . 7-72 SSM_TQHO . . . . . . . . . . . . . . . . . . 6-37
site_audit . . . . . . . . . . . . . . . . . . 2-441 SSMAUDIT_TIMER . . . . . . . . . . . . . . 6-13
slip_loss_daily . . . . . . . . . . . . . . . . 5-743 ssp_burst_delay . . . . . . . . . . . . . . . 5-758
slip_loss_hourly . . . . . . . . . . . . . . . 5-744 ssp_burst_limit . . . . . . . . . . . . . . . . 5-759
slip_loss_oos. . . . . . . . . . . . . . . . . 5-746 start_ack . . . . . . . . . . . . . . . . . . . 6-210
slip_loss_restore . . . . . . . . . . . . . . . 5-747 start_ts. . . . . . . . . . . . . . . . . . . . . 7-79
slot . . . . . . . . . . . . . . . . . . . . . . 7-78 stat_interval . . . . . . . . . . . . . . . . . 5-760
SLT_T1_TIMER . . . . . . . . . . . . . . . 6-209 stat_mode . . . . . . . . . . . . . . . . . . . 4-27
sm_audit_response . . . . . . . . . . . . . . 6-183 state . . . . . . . . . . . . . . . . . . . . . 2-448
smg_gb_vers . . . . . . . . . . . . . . . . . 5-748 static_sync_timer . . . . . . . . . . . . . . . 6-211
sms_dl_allowed . . . . . . . . . . . . . . . 5-749 Statistical applications
sms_tch_chan . . . . . . . . . . . . . . . . 5-750 Counter statistics. . . . . . . . . . . . . . . 4-3
sms_ul_allowed . . . . . . . . . . . . . . . 5-752 Distribution statistics . . . . . . . . . . . . . 4-3
soft_reset . . . . . . . . . . . . . . . . . . 2-445 Duration statistics . . . . . . . . . . . . . . 4-3
spi. . . . . . . . . . . . . . . . . . . . . . 6-184 Gauge statistics . . . . . . . . . . . . . . . 4-3
SPI . . . . . . . . . . . . . . . . . . . . . 6-185 Statistics
ss7_l2_t1 . . . . . . . . . . . . . . . . . . 6-186 about . . . . . . . . . . . . . . . . . . . . 1-4
ss7_l2_t2 . . . . . . . . . . . . . . . . . . 6-188 status_mode . . . . . . . . . . . . . . . . . 2-460
ss7_l2_t3 . . . . . . . . . . . . . . . . . . 6-190 store_cal_data . . . . . . . . . . . . . . . . 2-464
ss7_l2_t4 . . . . . . . . . . . . . . . . . . 6-192 surround_cell . . . . . . . . . . . . . . . . 5-761
ss7_l2_t5 . . . . . . . . . . . . . . . . . . 6-193
IX-14 68P02901W23-Q
sw_ts_less_one_carrier . . . . . . . . . . . . 5-763 synchronized . . . . . . . . . . . . . . . . . 2-399

swap_devices . . . . . . . . . . . . . . . . 2-466 Syntax
swfm_enable . . . . . . . . . . . . . . . . . 5-765 command syntax . . . . . . . . . . . . . . . 1-9
switch_gprs_pdchs . . . . . . . . . . . . . . 5-766 SYSGEN OFF mode . . . . . . . . . . . . . . 1-26
sync_loss_daily . . . . . . . . . . . . . . . 5-768 SYSGEN ON mode . . . . . . . . . . . . . . 1-26
sync_loss_hourly . . . . . . . . . . . . . . . 5-769 sysgen_mode. . . . . . . . . . . . . . . . . 2-469
sync_loss_oos . . . . . . . . . . . . . . . . 5-770 sysgen_mode off . . . . . . . . . . . . . . . . 1-27
sync_loss_restore. . . . . . . . . . . . . . . 5-771 sysgen_mode on . . . . . . . . . . . . . . . . 1-27
sync_time_oos . . . . . . . . . . . . . . . . 5-772 System Change Control (Configuration Management)
sync_time_restore . . . . . . . . . . . . . . 5-773 about . . . . . . . . . . . . . . . . . . . . 1-3
t_avg_t . . . . . . . . . . . . . . . . . . . 5-774 temporary_offset . . . . . . . . . . . . 5-310, 5-783

t_avg_w . . . . . . . . . . . . . . . . . . . 5-775 THRES_PC_RLF . . . . . . . . . . . . . . 5-474
T_HAND_RQD . . . . . . . . . . . . . . . . 6-81 threshold. . . . . . . . . . . . . . . . . . . 5-785
T_SDCCH_HO_OWED . . . . . . . . . . . 5-736 time_stamp . . . . . . . . . . . . . . . . . 2-475
t_stat_info . . . . . . . . . . . . . . . . . . 6-213 timeouts . . . . . . . . . . . . . . . . . . . . 1-10
T1 (CCITT) . . . . . . . . . . . . . . . . . 6-187 Timers . . . . . . . . . . . . . . . . . . . . . 6-1
T1_TIMER . . . . . . . . . . . . . . . . . 6-197 timing_advance_period . . . . . . . . . . . . 5-786
T12_TIMER . . . . . . . . . . . . . . . . . 6-198 tlli_blk_coding . . . . . . . . . . . . . . . . 5-788
T13_TIMER . . . . . . . . . . . . . . . . . 6-199 TM_CHANNEL_ACT . . . . . . . . . . . . . 6-48
T14_TIMER . . . . . . . . . . . . . . . . . 6-200 TM_HO_NY1_REP . . . . . . . . . . . . . 6-156
T17_TIMER . . . . . . . . . . . . . . . . . 6-201 TM_HO_T3105 . . . . . . . . . . . . . . . 6-162
T2 (CCITT) . . . . . . . . . . . . . . . . . 6-189 TM_MODE_MODIFY . . . . . . . . . . . . 6-126
T2_TIMER . . . . . . . . . . . . . . . . . 6-202 TM_SAACH_INFO . . . . . . . . . . . . . 6-175
T22_TIMER . . . . . . . . . . . . . . . . . 6-204 Tqho . . . . . . . . . . . . . . . . . . . . . 6-37
T23_TIMER . . . . . . . . . . . . . . . . . 6-206 trace
T3. . . . . . . . . . . . . . . . . . . . . . 6-191 call_trace_options . . . . . . . . . . . . . . 5-93
T3101 . . . . . . . . . . . . . . . . . . . . 6-158 trace_call command . . . . . . . . . . . . . 2-477
T3103 . . . . . . . . . . . . . . . . . . . . 6-160 trace_connection . . . . . . . . . . . . . . . 2-486
T3105 . . . . . . . . . . . . . . . . . . . . 6-162 trace_msgs_after_ho . . . . . . . . . . . . . 5-789
T3109 . . . . . . . . . . . . . . . . . . . . 6-164 trace_msgs_before_ho . . . . . . . . . . . . 5-790
T3111 . . . . . . . . . . . . . . . . . 6-166, 6-168 trace_stop . . . . . . . . . . . . . . . . . . 2-489
T3212 . . . . . . . . . . . . . . . . . . . . 6-170 trans_capability . . . . . . . . . . . . . . . 5-791
t391 . . . . . . . . . . . . . . . . . . . . . . 7-80 transcoding_capability . . . . . . . . . . . . . 7-85
t392 . . . . . . . . . . . . . . . . . . . . . . 7-82 TREL . . . . . . . . . . . . . . . . . . . . 6-182
T4 (CCITT) . . . . . . . . . . . . . . . . . 6-192 tru_id . . . . . . . . . . . . . . . . . . . . . 7-86
T4_TIMER . . . . . . . . . . . . . . . . . 6-207 trunk_critical_threshold. . . . . . . . . . . . 5-793
T5 (CCITT) . . . . . . . . . . . . . . . . . 6-193 trunk_major_threshold . . . . . . . . . . . . 5-794
T5_TIMER . . . . . . . . . . . . . . . . . 6-208 trx_pwr_red . . . . . . . . . . . . . . . . . . 7-87
T6 (CCITT) . . . . . . . . . . . . . . . . . 6-195 ts_alloc_flag . . . . . . . . . . . . . . . . . 5-795
T7 (CCITT) . . . . . . . . . . . . . . . . . 6-196 ts_in_usf_active . . . . . . . . . . . . . . . 5-796
tch_busy_critical_threshold . . . . . . . . . . 5-776 tsc_update_method . . . . . . . . . . . . . . 5-797
tch_busy_norm_threshold . . . . . . . . . . . 5-777 tx_integer . . . . . . . . . . . . . . . . . . 5-799
tch_congest_prevent_thres . . . . . . . . . . 5-778 TX_INTEGER . . . . . . . . . . . . . . . . 5-800
tch_flow_control . . . . . . . . . . . . . . . 5-779 tx_power_cap . . . . . . . . . . . . . . . . 5-801
tch_full_need_low_water_mark . . . . . . . . 5-781 Type A commands and parameters. . . . . . . . 1-6
TCONN_EST . . . . . . . . . . . . . . . . 6-177 Type B commands and parameters . . . . . . . . 1-6
tcu_port . . . . . . . . . . . . . . . . . . . . 7-83
68P02901W23-Q IX-15
Index
u_rxlev_dl_ih . . . . . . . . . . . . . . . . 5-803 ul_audio_lev_offset. . . . . . . . . . . . . . 5-819

u_rxlev_dl_p . . . . . . . . . . . . . . . . . 5-805 ul_rxlev_ho_allowed . . . . . . . . . . . . . 5-820
U_RXLEV_DL_P . . . . . . . . . . . . . . 5-806 ul_rxqual_ho_allowed . . . . . . . . . . . . 5-822
u_rxlev_ul_h . . . . . . . . . . . . . . . . . 5-807 UMTS UTRAN Cell ID. . . . . . . . . . . . 5-322
u_rxlev_ul_p . . . . . . . . . . . . . . . . . 5-809 unalias. . . . . . . . . . . . . . . . . . . . . 3-10
U_RXLEV_UL_P . . . . . . . . . . . . . . 5-810 unconfigure_csfp . . . . . . . . . . . . . . . 2-492
u_rxqual_dl_p . . . . . . . . . . . . . . . . 5-811 unequip . . . . . . . . . . . . . . . . . . . 2-494
U_RXQUAL_DL_P . . . . . . . . . . . . . 5-812 unequipped_circuit_allowed. . . . . . . . . . 5-824
u_rxqual_dl_p_hr . . . . . . . . . . . . . . 5-813 unlock_device . . . . . . . . . . . . . . . . 2-504
u_rxqual_ul_p . . . . . . . . . . . . . . . . 5-815 uplink_sync_timer . . . . . . . . . . . . . . 6-214
U_RXQUAL_UL_P . . . . . . . . . . . . . 5-816 use_derived_ho_power . . . . . . . . . . . . 5-826
u_rxqual_ul_p_hr . . . . . . . . . . . . . . 5-817 use_neighbor_pbgt_hreqave. . . . . . . . . . 5-827
valid card slots . . . . . . . . . . . . . . . . . 2-16 volume_control_type . . . . . . . . . . . . . 5-828

valid_candidate_period . . . . . . . . . . . . 6-216
wait_for_reselection . . . . . . . . . . . . . 5-830 window_size . . . . . . . . . . . . . . . . . 2-144

wait_indication_parameters . . . . . . . . . . 5-831 worse_neighbor_ho. . . . . . . . . . . . . . 5-833
XBL XBL (contd.)

lapd_k. . . . . . . . . . . . . . . . . . . . 7-47 lapd_t200_timer . . . . . . . . . . . . . . . 7-51
lapd_n200 . . . . . . . . . . . . . . . . . . 7-49 xcdr_d_vad_dtx . . . . . . . . . . . . . . . 5-202
zone_ho_hyst . . . . . . . . . . . . . 5-387, 5-834 zone_pingpong_enable_win . . . . . . . . . . 6-218

zone_pingpong_count . . . . . . . . . . . . 5-836 zone_pingpong_preferred_zone . . . . . . . . 5-837
zone_pingpong_disable_win . . . . . . . . . 6-217
IX-16 68P02901W23-Q

Parameter Manual Motorola GSR7

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Parameter Manual Motorola GSR7

Uploaded by

Copyright:

Available Formats

Technical Description: BSS Command

© 1994 - 2004 Motorola, Inc. 68P02901W23-Q

All Rights Reserved CONTROLLED INTRODUCTION 24 May 2004

CONTROLLED INTRODUCTION 24 May 2004

Technical Description: BSS Command Reference

Chapter 1: Introduction to commands

Chapter 2: Device/function related commands

Chapter 3: UNIX commands

Chapter 4: Statistics commands

Chapter 5: CM database parameters

Chapter 6: Timer parameters

Chapter 7: Device/function parameters

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

This page intentionally left blank.

Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 5-1: alt_qual_proc=0 parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Technical Description: BSS Command

What is Covered In This Manual?

Helpful Background Information

• Volume 2 contains Chapters 5 to 7 providing descriptions of associated

Issue status of this manual

Table 1 Manual version history

Resolution of Service Requests

The following Service Requests are now resolved in this manual:

Table 2 Service requests resolved in this manual

Table 2 Service requests resolved in this manual (Continued)

New and modified commands introduced by GSR7 Half Rate

New and modified/renamed database parameters introduced by GSR7 Half Rate

Failure to comply with Motorola’s operation, installation and maintenance

The tags have the format: {nnnn} or {nnnnn}

The tags are positioned in text as follows:

New and amended feature information Tag position in text

• Full sections under a main heading • Main heading

• Full paragraphs under subheadings • Subheading

Special key sequences

CTRL-c Press the Control and c keys at the same time.

Reporting safety issues

Whenever a safety issue arises:

Procedure 1 Safety issue reporting

1 Make the equipment concerned safe, for example by removing power.

Warnings and cautions

A definition and example follow below:

Example and format

Failure to comply with warnings

A definition and example follow below:

Example and format

• Potentially hazardous voltage.

Potentially hazardous voltage

Motorola GSM equipment does not utilise high voltages.

High RF potentials and electromagnetic fields are present in this equipment

• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields

When dismantling heavy assemblies, or removing or replacing equipment, a

Do not install substitute parts or perform any unauthorized modification of

Do not wear earth straps when working with stand-by battery

Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective

Motorola equipment contains CMOS devices. These metal oxide semiconductor

Devices sensitive to static

Special handling techniques

• Always wear an earth strap which must be connected to the electrostatic

• Take care when removing components connected to electrostatic sensitive devices.

Motorola manual set

• Electronic, as fully navigable PDF files on: